If I read it correctly, you are taking a document from a current process, restructuring it and using it to control a new process. Will your document system alow you to not save it as a revision but as a new document number?
This would mean you have 2 current documents, 1 for each porocess.
We are in a situation where we have two revisions of the same assembly ongoing. Our current systems tracks documents by our own internal numbering system so having multiple revisions is not a problem, the issue is human error and clarity.
Currently when we add a new rev in the software all other versions automatically show as obsolete. All obsolete docs are supposed to then move to a segregated file cabinet. The problem of course is that these documents are obsolete as far as the new assy is concerned, but not for the old (which are still ongoing).
Can someone suggest a effective way to deal with type situation?
Yes I can have unique ID numbers for the documents. The problem is one of confusion. I am making two different revisions of the same part.
Rev A goes on old parts being refurbished
Rev B goes on new assemblies
Rev A is "active" for refurbish work but "inactive" for new assemblies. Work instructions also have changed and have the same duel nature.
What's the best way to avoid confusion?
Maybe it won't work for you, but I had a client fighting a similar situation. They ended up using a color code system throughout their system. It seemed to work. ("Red" went one way, "green" the other...and instructions were coded to match).
I have a similar situation.. what we do is when we approve the newly revised procedure / part / process, we also disposition the old parts / procedure / etc. as "Purge". We then give these newly purged parts new part numbers (same part number but with a suffix of "f" meaning field use only).