How to handle Releasing objects (parts and Assemblies) in CAD (CAD/PDMLINK) before they are approved for use in manufacture?
Releasing an object in ERP is a manual operation controlled by the our manual ECN process.
Releasing an object in PDMLINK is controlled by a Promotion Request.
When an object is released in CAD a zip file (containing a PDF and STEP file) is manually created and stored in a Design Release folder (named by ECN no.). When the ECN is released the ERP is updated and the zip file is moved to a Production Release folder and any previous revision of zip file is moved to an archive folder.
Problem – CAD/PDMLINK
An object is Released at revision 1 in PDMLINK and ERP (zip file stored in Production Release folder).
A change is proposed and the object is revised to revision 2 at WIP for Release in PDMLINK.
The change is completed in CAD and the object is promoted to Released in PDMLINK.
The object is still Released at revision 1 in ERP until the object is approved for use at revision 2.
A new change is proposed and the object is revised from revision 2 to revision 3 at WIP for Release in PDMLINK.
The change is completed in CAD and the object promoted to Released in PDMLINK.
Revision 3 now incorporates revision 2 changes which have not been approved for use. The object is still Released at revision 1 in ERP.
One solution would be to not promote revision 2 to Released, but have an interim release level (say PPAP). So, revision 1 is Released in PDMLINK and ERP with revision 2 at PPAP release level in PDMLINK and zip file in design release folder.
Now when a new change is proposed the Released object at revision 1 can be revised to revision 3 at WIP for Release in PDMLINK. The change would then be completed in CAD and the object promoted to PPAP. object is still Released in PDMLINK and ERP at revision 1. So, revisions 2 & 3 will be at PPAP release with zip files in relevant design release folders.
Once object is approved for use in manufacture it can be promoted from PPAP to Released and new zip file created in Production release folder.
But now revision 3 could be promoted to Released before revision 2 in both PDMLINK and ERP!
Thought I would ask the same question again, in the hope that someone else has encountered the same problem or has any advice.
We have similar scenarios here where we make a design change and the factory is requesting another change before the previous is implemented. This ties back to your ERP Rev 1, with Rev 2 pending, with Rev 3 coming out of the gate next. We always rev roll from the latest version.
Now my factory wants to implement Rev 3 changes in ERP, but is not ready for Rev 2 changes yet. For our business, we flag the Item in ERP with a flash message that an Engineering Change is still outstanding. We can query these items that have flash messages enabled. We make a comment in the ERP Item Master indicating that "Rev 2 is pending implementation". To supplement this item flash message, we also have CN Task assignments showing open implementation tasks at the factory...reportable, and we have a manual log that tracks every open and outstanding change....metrics.
When we have a revision that gets 'stuck in the middle', for lack of a better term, we put high visibility on the item and really press the factory/suppliers to get the change implemented ASAP. It's not the most elegant solution. Its definitely not fool-proof. But its a solution the factory can live with and our change management team has easy visibility on the outstanding change.
May not be what you're looking for, but maybe something to get you thinking differently. Hope it helps.
Thanks. I will discuss your solution with others to see if, as you suggested, sparks any other ideas.