Embedded Files
Version vs Revision: Which Should Be Used
Version vs Revision: Which Should Be Used
When to Use a Version:
After a major design review or approval.
Before making exploratory changes or trying a new direction in the design.
To preserve historical records of your document as the design evolves.
When to Use Revision:
To manage changes that impact production or require approval for release.
When you need to maintain a clear record of what was changed and why for a specific part or assembly.
To ensure the right version of a component is used in manufacturing or downstream processes.
You may still branch from any revision, allowing for an Engineering Change Request (ECR) process.
Key Features of a Version:
Key Features of a Version:
Comprehensive State: A version captures the full document, including all parts, assemblies, and configurations.
Design Milestones: Useful for marking progress, such as completing a concept phase, preparing for a design review, or creating a baseline before significant changes.
Comparison Tool: Versions enable you to compare the current design with previous iterations, helping you visualize changes and evaluate progress.
Image of an Onshape design on a DFM branch with two named versions created to track the milestones of the design.
A Practical Workflow
A Practical Workflow
Start with a version: As you iterate on your design, capture significant milestones using versions. For example, create a version after completing the initial design and another after incorporating feedback from a design review.
Manage changes with revisions: When a part or assembly is finalized and ready for production, create a revision. Use Onshape’s Release Management tools to approve the change and document its impact.
Iterate and combine: If changes are required, create a new version to capture the state of the document before making edits and branch from there. After updating specific components on that branch, move them through the revision process for controlled release and merge the changes into the main timeline. This shows the work and makes it easy to compare in the future for design reviews and ISO audits.
Report abuse