Hi all,
I am struggling with setting up a 2 level (Major/minor) revision system in EPDM. I would appreciate some feedback on the proposal bellow.
We have narrowed our options to the following:
Option 1 - Major/minor revisions are tracked in meta data.
Minor revisions for: correcting drawing typos, and part changes that maintain interchangeability.
- i.e if a revised part can be intermingled in production inventory with previous iterations of that part without any negative effect then minor revision is appropriate.
Major revisions for: changes that render the parts non interchangeable.
Revision Scheme: Major- A, B,C,D Minor : 01, 02, 03, 04
Major and minor revisions will only show in meta Data and will not be included in part number.
Note: For both options both drawings and models will have the same PN and revision.
Option 2 - Major revisions change the PN, only minor revision are tracked in Meta data.
Minor revisions: same as in option 1 and tracked on data card.
Major revisions: Changes that render the parts non interchangeable will trigger a PN change.
The part number will be a change to a dash number (very last character in PN). e.g 300-12345A
300-12345B OR a complete change to a PN.
For option #2, Only minor revisions will be tracked in Meta data.
Questions to group:
- Are there any users out there who can report a successful workflow for tracking two types of revisions.
- Which of the above two systems is preferred?
Thanks
Joel T
Joel, we are using option 2. Our dash no. is an editable variable on the data card and automatically appends to the document number (we have it setup to be the same as the file name) to form the part number.
We are using the PDM to increment "revisions" in files, alpha for drawings and a numerical for the part/assembly files, but for the part and assembly files it does not relate in any way to the dash no. or the drawing revision. We don't even have it linked to a variable, on the data card we call it change level and it simply means the amount of times it has been transitioned into the released state. This is mainly to have the functionality to only allow certain users/groups to only see "revisions" and not "working versions" (versions that are not revisions).
We did look at using the PDM to handle the incrementing of dash numbers in files, but the workflows quickly became too complicated so we left it as a manual process.