Additive Manufacturing¶
Cost impact for upgrades to aPriori Professional 2021 R1
Cost Model Version Summary¶
The following table shows the cost model version numbers for the last three major releases:
| Release | Cost Model Version | Status |
|---|---|---|
| aPriori 2021 R1 | 90 | New with this release |
| aPriori2020 R1 | 70 (20.1.0) / (20.1.1) 80 | From a prior release |
| aPriori 2019 R2 | 50 (19.2.0) / (19.2.1) 60 | From a prior release |
Summary of Platform Changes¶
The table below indicates whether there were geometry and/or cost engine changes for this process group. Such changes could impact costing results for configured Digital Factories.
| Platform Area | Was there a Change? |
|---|---|
| Geometry | Yes |
| Cost Engine | No |
Change Summary by Area¶
The table below indicates whether there were geometry and/or cost engine changes for this process group. Such changes could impact costing results for configured Digital Factories. For the first type of change (geometry or cost engine changes), the table indicates the impact level (High, Medium, Low, or No).
| Area | Impact? |
|---|---|
| Geometry or cost engine changes that could impact configured Digital Factories | LOW (can be disabled) |
| Bug fixes or small improvements to prior cost model versions that could Impact configured Digital Factories | NO |
| Cost model changes that do not affect configured Digital Factories | NO |
Details: Geometry or Cost Engine Changes that Could Impact Configured Digital Factories¶
The following changes might impact costing, even for Digital Factories that use earlier cost model versions.
-
RingedHole Extraction: In this release, for a given internal volume that is symmetric about a turning axis, the GCDs that represent it might change compared to the previous release. aPriori uses one of the following methods to represent such a feature:
- Explicit RingedHole method: feature is represented by a SimpleHole, a Ring, or a RingedHole whose children are a central SimpleHole and one or more surrounding Rings (which represent enlargements of the hole).
- Implicit ringed hole method: feature is represented by a central SimpleHole and zero or more surrounding Rings. No parent RingedHole GCD is created.
-
MultiStepHole method: feature is represented by one or more SimpleHoles and/or one or more MultiStepHoles and/or one or more Rings if necessary. In the previous release, aPriori used the explicit RingedHole method if the site variable createRingedHole was set to GCD or MCD. It used the implicit ringed hole method if the site variable createRingedHole was set to None. In this release, by default, aPriori uses the explicit RingedHole method if the current routing is a turning routing. It uses the MultiStepHole method, by default, if the current routing is a milling routing. RingedHole extraction behavior is controlled by the site variable createRingedHoleMCD in the Machining process group. The site variable createRingedHole (introduced in Release 20.1.0) is now deprecated. The site variable createRingedHoleMCD has the following possible values:
-
All: This is the default. With turning routings, use the explicit RingedHole method. With milling routings, use the MultiStepHole method. This applies to all process groups that support RingedHoles.
- None: regardless of routing type, use the implicit ringed hole approach. This applies to all process groups that support RingedHoles.
- Net Shape Only: For net shape process groups (Additive Manufacturing, casting process groups, Forging, and Powder Metal), use the RingedHole method with turning routings and the MultiStepHole method for milling routings. For all other process groups that support RingedHoles (2-Model Machining, Bar & Tube Fab, and Stock Machining), use the implicit ringed hole method.
If you are upgrading from a release earlier than Release 20.1.0, you can generally restore the previous behavior by setting the site variable createRingedHoleMCD to its previous setting. If you used Net Shape Only previously, some behaviors may be different.
Details: Bug Fixes or Small Improvements to Prior Cost Model Versions¶
The following changes might impact costing for Digital Factories that use earlier cost model versions.
- NO IMPACT
Details: Cost Model Changes that Do Not Affect Configured Digital Factories¶
The following changes do not affect costings with Digital Factories that use earlier cost model versions. The changes are available only in the latest cost model version.
- NO IMPACT