Impact Classification | Circumstances when this Impact will be marked YES | Upgrade Actions |
Geometry or Cost Engine Changes that Likely Impact Customer VPEs | This is marked YES under two main situations: (1) If the changes to aPriori's geometry are such that they redefine existing GCDs. The impact is that a VPE's results may not be the same as before, since the inputs to the VPE may be different. If test results show unsatisfactory behavior, you have three options: a) Rev the cost model version to take advantage of new cost model b) Edit the existing cost model c) Execute a combination of both These changes would take advantage of new types of GCDs, new GCD properties, and so forth. (2) If the cost engine changes are such that they redefine how the cost engine interprets CSL and Cost Model intent. This is a less frequent situation. If test results show unsatisfactory behavior, the cost model needs to be updated so that the cost engine can correctly interpret the logic as intended by the original design, and you have three options: a) Rev the cost model version to take advantage of new cost model b) Edit the existing cost model c) Execute a combination of both In these situations, the cost model needs to be rebuilt and/or recalibrated so that the VPE intent is maintained under the new geometry and cost engine schemes. | Testing required, potential config/calibration necessary. Please contact aPriori Support with questions, or your aPriori Account Manager to plan work if you require assistance |
Bug Fixes or Small Improvements to Shipping CMV that Could Impact Customer VPEs | This is marked YES under three main situations: (1) There are incremental improvements and updates to Geometry: These changes simply introduce more cases that now work better and improve the default behavior. (2) The cost model was not increased in the shipping baseline cost model version: If the customer VPE inherits any portion of the cost model from the Baselines against the same CMV, there will be cost changes. These are considered improvements to the previously shipped behavior. (3) The part uses the Baseline Machining model for Secondary Machining: Since the machining model has changed in aP 2019 R2, customer parts may use the Baseline machining model for secondary machining if no secondary machining is available in the customer VPE and machining analysis is invoked by the cost engine. This information is being presented here primarily since many customer databases do have parts that are costed against the baseline VPEs and when those parts are re-costed in aP 2019 R2, one may see cost variations due to these changes. | Testing required, potential config/calibration necessary. Please contact aPriori Support with questions, or your aPriori Account Manager to plan work if you require assistance. |
Changes to Baselines that do not affect Customer VPEs | This is marked YES if there are baseline VPE changes that will not impact customer VPEs. Typically, it involves changes done on a newer cost model version that is not available in the field. Changes in Geometry do not affect this functionality. | If you want to take advantage of these new capabilities, the VPE needs to be upgraded to the most recent CMV. Please contact your VPE Admin or aPriori Account Manager to plan work. |