Assembly Association Strategy

You can use aP Connect to analyze native, multi-file assemblies. When there is more than one scenario for a component that is a child in an assembly, aPriori determines which child scenario to include in the assembly by applying algorithms that are called assembly association strategies. Unlike aP Design, in which users can select a preferred assembly association strategy that is applied when the CAD file for an assembly is imported, aP Generate, provides a single assembly association strategy that is applied when an assembly is being cost.

To prioritize the completeness of the included children scenario, the strategy that aP Generate applies identifies and includes the most recently modified public scenario for each component in the assembly. The strategy considers both previously cost public child scenarios and public child scenarios that are submitted in the same aP Generate job as the assembly. If aP Generate is not able to find one or more of the children of an assembly because they were neither submitted in the job nor previously costed and published, a missing scenario is created as a placeholder for each relevant child, and the status for the costing of the assembly scenario is designated as Incomplete.