I'll figure it out myself. Thanks.
Wow. Honestly, don't try to fix what you have. Throw it out all together and start over. You need to think about what you need to get it done and not dwell on how bad it is now. If reviewing and approving everything at every single step is too much (it is) then figure out where you can combine reviews/approvals and leave out redundant work. Start simple. Keep it simple.
What I posted IS the condensed version. Keep in mind that our current PDM workflow is NOT what you see in my post. It's much worse than that. I wrote this up after extensively evaluating what absolutely needs to happen in our approval process and I've removed many of the redundant steps. This is pretty much as simplified as I can make it.
Why do we have EM and PM approvals happening at separate times? This lengthens the process a lot.
Revision works the exact same way.
My ISO controlled ECN workflow has been given acclaim by 2 different (unnamed) mil/aerospace players.
S. Casale wrote: Why do we have EM and PM approvals happening at separate times? This lengthens the process a lot.
S. Casale wrote:
This is just how it's always been done here. The EM reviews it before the PM does so they can catch the little stupid mistakes that make it onto the drawing and to catch issues that would cause construction problems. The PM then reviews for design intent and makes sure the customer needs are met. Sometimes the build team is even involved in the approval process which add another step to this. Then it goes out for customer review, and they have three options when they send it back (revise/resubmit, approved as noted, approved) and that determines how we move forward.
Do you have a workflow graphic you use that you're willing to share? I'll present it to see if it works for everyone here.
Too large process...
A company can't survive to this time of development.
Throw it out all together and start over again...as said Stephen Lapic
I stopped reading after step 2 .....
Step 4b seems especially dodgy. You have someone signing for someone else.
The main problem I see here is that you are driving the process with the PDF instead of the CAD files. Your approvers should be approving the CAD models/drawings. They can certainly review/mark up the PDF along with that but by approving the CAD files, you can get their approval data into the approval block automatically (with password authentication if desired). New PDFs should be generated *after* the approval step so that the approval info is already there. One key to making this easy is to have the model. drawing and PDF file names match. Another feature that can make this work really well is to have the PDF automatically generate and automatically transition to states corresponding to the drawing states.
For example, if the PM gets a notification that 12345.SLDDRW needs approval, he can (via a file name search) open 121345.PDF for review. The PDF should be in a state where it can be checked out if markup is required. After markup, the PM transitions 12345.SLDDRW to the appropriate state, which will create a new PDF (with the PM signature) if approved or everything goes back to WIP as-is (unsigned but marked up PDF).
Customer approval is trickier, but at a minimum, steps 6b and 6c are identical. If the customer is going to note changes, why not just call those noted changes a revision? Unless your customers have access to PDM (e.g. via the web interface), you may want to use a separate document to track their approval. This eliminates the step of saving over your PDF with an approved copy. A checkbox on the data card to indicated the customer has approved it would suffice to route it to the right workflow via a transition condition. The PM could 'Paste as Reference' the approval letter at the same time as ticking the check box. Or, this could be automated so that a transition triggered the checkbox to be ticked and the file gets attached.
I have found that when you don't automate the PDF process, you will inevitably have a situation where parts are made with the wrong PDF because someone forgot to perform a manual 'Save As'.
The only one who can approve CAD files is me. Everyone else in the approval chain ONLY wants to use the PDF file. They wouldn't know what they were looking at if they reviewed the CAD files anyway.
The drawing has to be both internally (company) and externally (customer) approved before a drawings is issued. Any changes that happen prior to the drawing being issued is not considered a revision. It's just part of the approval process. The only time we call something a revision is after the initial drawing was released.
Bill Lacey wrote: The only one who can approve CAD files is me. Everyone else in the approval chain ONLY wants to use the PDF file. They wouldn't know what they were looking at if they reviewed the CAD files anyway.
Bill Lacey wrote:
I didn't say they needed to review the CAD files. They would just be changing state on them so that the signature info goes in automatically.
I would then suggest a two part rev number. We use letters before the file is released and numbers after:
Did you delete your initial message context??
Yes, I took the hint. Too complex, and since no one was offering a workflow suggestion I felt it was pointless to keep it up.
Chill. As "Engineering Manager" I would have expected a little more diplomacy from you. This is second post which you've sort-of been a little, as the young kids are saying these days, "extra."
Bill Lacey - That's too bad -
Everyone always has their own evaluation of other peoples issues and ideas evolve, so the more incorrect answers or off the wall comments that are made, the more it makes you think and then when you go through the check off list of what not to do, you'd be surprised of the answer that is there... just my 2 little pennies Almost like telemarketers, there is a percentage of No's that equal a yes, and that is a lot how some of these topics go, the more incorrect comments you get, the closer you are to the correct solutions...
‘Even a negative result is a result’ I think I stole that from the Big Bang Theory.
Retrieving data ...