In this video, we look at how revisions are enabled, and configured within the 3DEXPERIENCE platform, as well as how we revise our files within SOLIDWORKS:
Revisions in 3DEXPERIENCE
Revisions help us to track design changes, and store the history and evolution of our products. While revising files can be driven by change actions, which introduce approval stages, this video focuses instead on the tools available under Lifecycle and Collaboration.
Enable and Configure Revisions in 3DEXPERIENCE
Under the ‘Platform Management’ role, open the ‘Collaborative Spaces Control Centre’ app.
On the right hand side, select ‘Lifecycle and Collaboration’.
To specify the formatting of a revision, under ‘Revision Format’ we can specify ‘Primary’ or ‘Primary.Secondary’.
If a secondary component to the revision is enabled, this is incremented when a ‘New Revision’ is created when the file is not in the ‘Released’ State.
When a new revision is created for a file that is in the ‘Released’ state, the next primary revision is created, and the secondary component is reset.
While the secondary component will always be numerical, we can choose whether we want letters or numbers to denote the primary component of a revision.
Now under ‘Revision Naming Rules’ for Physical Products we can choose which naming convention to follow.
When selecting the alphabetical component a variation can be selected where uncommon letters such as I, O, Q, S. X, and Z are skipped.
Making a New Revision in SOLIDWORKS
While working on our part in SOLIDWORKS, we can use commands under the ‘Lifecycle’ tab to move the file through our maturity graph, and create new revisions for our file.
Using the ‘Maturity’ command, under the ‘Lifecycle’ tab lets us see our maturity graph and the routes available to us to move our file between the states. We’ll use this to release the file.
Once the file is released, we can start a new revision to implement a design change.
Using the ‘New Revision’ command will move us to the ‘In Work’ state, set the file to Revision B, and lock the file to us so we can implement our design change.
After modifications are complete, we want to save our changes, unlock the file and use the Maturity command again to release the file to Revision B.