G
gfreely
We recently ran into a situation at my work and I have scoured the Cove but found no direct help.
We use Travelers for units which are embarking on the Realisation Process. Sometimes, there will be so many revision changes on the part design, or sequences of the job added/removed to the point that the traveller looks like the old map in the glove box from a '68 Bug.
We can print out a "new" and updated copy, yet the original signatures are on the OLD router for work completed thus far.
Our procedure states that "major revisions or multiple sequence additions/deletions shall require a new process routing to be generated"...but no guidance (in the procedure or in any WI) as to how to go about capturing the original information (signatures/dates) from the old copy.
I am tasking myself with looking for a way to standardize and document this process to avoid everybody performing this task the way that works best for THEM.
Any suggestions? How does anyone else handle this?
Thanks!
We use Travelers for units which are embarking on the Realisation Process. Sometimes, there will be so many revision changes on the part design, or sequences of the job added/removed to the point that the traveller looks like the old map in the glove box from a '68 Bug.
We can print out a "new" and updated copy, yet the original signatures are on the OLD router for work completed thus far.
Our procedure states that "major revisions or multiple sequence additions/deletions shall require a new process routing to be generated"...but no guidance (in the procedure or in any WI) as to how to go about capturing the original information (signatures/dates) from the old copy.
I am tasking myself with looking for a way to standardize and document this process to avoid everybody performing this task the way that works best for THEM.
Any suggestions? How does anyone else handle this?
Thanks!