Understanding SOLIDWORKS CS and CC Maturity States
In 3DEXPERIENCE, lifecycle management is available out of the box, giving you more control over our data. Maturity States define who can find data or make changes. They also determine when revisions are created during a product’s lifecycle.
You can manage these maturity states through the Lifecycle and Collaboration app in a web browser, or directly from the Action Bar (shown below) in the 3DEXPERIENCE Add-in for SOLIDWORKS and SOLIDWORKS Design CC.
Note: The example used in this guide started the maturity state process after it was modeled and saved to the platform.
The 5 Maturity States
The five Maturity States shown above are the standard states included with SOLIDWORKS Cloud Services. The arrows between states represent transitions, which vary depending on the current state of the data.
The maturity states are defined as follows:
Private: Documents are accessible only to the owner and are not shared within the collaborative space.
In Work: Documents are initially saved in this state and are accessible in the collaborative space.
Frozen: Documents are locked to prevent modification, typically while under review.
Released: Documents are finalized for production. Released documents cannot be modified. A new revision must be started to modify, sending the file to In Work.
Obsolete: Documents are no longer in use and are set to this state.
1. Maturity State: Private
Documents in Private state are accessible only to their owner. Other users cannot view or interact with the file in the collaborative space. This state is typically used when working on a design before it is ready to be shared or reviewed. When ready, documents can be transitioned to the In Work state to allow access by other users.
2. Maturity State: In Work
In Work is the default lifecycle state when a model is first saved to the 3DEXPERIENCE platform. In this state:
- Users (with permission) can lock a file to take control and prevent others from making changes.
- The state ensures that the file in use is the latest version, making it the active state for design work.
Transitions:
- Private to lock the file and prevent anyone else from accessing it.
- Frozen to prevent modifications while the file is pending review/approval.
- Released if the design is accepted and approved for production.
Additional considerations:
- Multiple files can be transitioned to a new maturity state at once.
- Structural objects can be included in a transition.
- Rules can be applied to enforce dependencies, such as requiring all children (structural objects) in an assembly to reach the Released state before the parent can be released.
3. Maturity State: Frozen
The Frozen state is used to prevent modification once work is complete. This state is commonly applied during design reviews. While frozen, the file cannot be modified, ensuring the design version remains stable.
Transitions:
- Return the file to In Work if changes are required or if a review is rejected.
- Transition to Released if the design is accepted and approved for production.
4. Maturity State: Released
The Released state indicates that a design has been approved or is ready for production. Files in this state cannot be modified or transitioned to any other state except Obsolete. The Released state typically marks the end of the lifecycle for a given revision. If further changes are required, a new revision or branch must be created.
Note: Different revisions or the same file may exist at different maturity states as shown below.
Revision options:
- New Revision: Created a new revision of the selected object. Content from another object may also be used.
- New Revision From: Creates a new revision of the selected structure using content from another structure. In the dialog box, select the source (revision, duplicate, or branch), choose options for each child, and click Revise.
- New Branch: Creates a branch from the selected object. In the dialog box, assign credentials for the new branches. For a single object, enter a title. For multiple objects, enter a prefix. Optionally, add a revision comment.
5. Maturity State: Obsolete
The Obsolete state is used for files that are no longer active but must be retained for historical reference.
- Files can be transitioned to Obsolete after being Released, provided the user has permission.
- Obsolete files no longer move through the lifecycle and are clearly marked to indicate they should not be used.
- Obsolete files can also be hidden from other users if needed.
Conclusion
This guide provides an overview of the maturity states in 3DEXPERIENCE. Using these states, you can manage data access, control revisions, and ensure that your team is always working with the latest design information.
Technical Support
Get help from our team by Calling us at 800-364-1652. You can also get assistance by clicking the Technical Support button or the Email Our Experts button below.