About Configured BOM in Development Mode

A configured part that has never been released (1st revision sequence and in the In Work state) is considered to be in development mode or work-in-progress mode (WIP) mode. If the part in development mode is an assembly, then the first level child parts under the parent part are also in development mode from a BOM applicability perspective.

See Also
About the Change Action with Applicability Release Process
Releasing a BOM Configuration in Development Mode

  • The engineering configured structure is used to store single/multiple model unit applicability for a configured part.
  • The configured part can have configured and unconfigured parts as child parts.
  • The top-most configured part is connected to a model and can have only one model connected to it. This configured part basically represents the product structure. Therefore, it can have only single unit applicability for level 1, e.g., ProductA[1:20].
  • The lower level (Level 2 and higher) configured structure is not connected to the Model and can have multiple product unit effectivities defined in its structure, e.g., ProductA[1:20] || ProductB[1:30].
  • The initial revision of the configured structure is considered the WIP BOM. In WIP mode, only the current applicability is defined for the structure. Pending applicability (proposed applicability) is not defined for a WIP part. In this mode a CA is not needed. If a CA is selected while creating the BOM, it is ignored. To apply the changes, a Current applicability value is required, along with other attributes like Find Number, Quantity and Reference Designator.
  • The configured part is moved to production mode when the initial revision is released using a CA. Once a configured part / assembly is released, subsequent changes (ADD/CUT) require a CA process and would create a pending applicability. The release of the CA enables the creation of the new revision of the parent assembly where pending applicability is transformed to current applicability.
  • Once a preliminary configured part is associated to a CA, it cannot be connected to another CA. There can be only one CA releasing a preliminary part. If the selected part has a CA for initial release, an error message is displayed.
  • Removing a child part from a preliminary configured part disconnects the child part altogether. The operation does not enforce a context change. If the parent part is released, a context change is required to perform a remove operation. In this case the child part will not be disconnected and is instead treated as a cut operation.