Aligning structure > Aligning the structure internally > Aligning parts and designs
Checking design maturity level
As a design changes over time, more than one revision of the design may be associated with a part. One of these revisions must always be the primary, that is, the source of visualization data in the part structure. The primary revision cannot be configured but is determined by a maturity level, for example, if a release status is attached and (if so) its type.
Note The name of the release status used in the workflow should already be defined in the Business Modeler IDE. Use the real name of the release status in the workflow, not the display name. The decision on whether a design revision is considered mature depends on your business processes. You can define the appropriate maturity level by setting the AutoRevise constant or ReviseAndRelateToLatest action on deep copy rules in the Business Modeler IDE. Alternatively, you can customize the USER_is_item_rev_mature user exit. Teamcenter can automatically change the primary design representation as the design evolves, so that the new design revisions are associated with a part revision. When you associate a design revision to a part revision, Teamcenter compares it with the existing primary design representation by maturity level and latest revision. If one of the design revisions is mature, it is made the primary representation, otherwise the latest is used. For example, Part1/A is represented by mature Design1/A and you then associate a new working revision Design1/B with Part1/A. Teamcenter compares the maturity levels of Design1/A and Design1/B. As Design1/A is mature, it remains the primary representation and Design1/B is associated with Part1/A. If Design1/B is subsequently released, it becomes mature and is eligible to become the primary representation. The user can then manually make Design1/B the primary representation. Alternatively, you can use Workflow to initiate the setting of the primary design representation. If the approval of a design revision makes it mature, use the approval status to initiate the PS-make-mature-design-primary Workflow handler. This action automatically makes the design revision the primary representation of the part revision that was approved.
Source: https://docs.sw.siemens.com/documentation/external/PL20251212545240207/en-US/tc_help/pse/wgd1737253422064/jcp1737253422163/pzm1737253422259/checking_desmaturity.html · retrieved Sat Jul 11 2026 00:00:00 GMT+0000 (Coordinated Universal Time)