In our company QA is required to approve the master routing for parts. In current software system, we might have 1-3 different master routings for the same part (depending on method) and they each link back to same part/part revision, but since they are separate master routings, they each have their own routing revision and QA approval date of routing. The QA Approval person/date also populates onto the job traveler when a job is released.
We are having trouble thinking of how to replicate this in E10.
We have been looking into using the engineering workbench and utilizing task sets. The con to this is that someone can accidentally check in and approve the part without having all tasks completed.
I am also having difficulty understanding how to capture different master routing revisions and different QA Approvals for those different routings. It seems that if one routing is changed, the task set applies to all routings under that part. Therefore the QA Approval would apply to all routings.
We also thought about maybe putting this information on the Part Maintenance screen instead, however I think this option would only work if we only ever had one master router per part. Since we have multiple each with their own revision, not sure how we could handle that.
Does anyone have any ideas how to accomplish this in E10?
You will have to use Alternate methods. That might be able to do what you are looking for.
Vinay Kamboj
Thank you for your reply.
Another problem with using alternate methods in engineering workbench is if I apply a task set (for purpose of grabbing QA Approval), since it is tied to ECO Group, it applies to all of the methods of that part. Correct me if I am wrong. Therefore each method would not have its own QA Approval. Every time one method is changed we would need to review and approve all 2-3 methods to be able to honestly check off QA Approval task.
Am I understanding wrong? Or is there a way to attach some sort of task set/approval to each method?
The APPROVED checkbox in Revision -> Detail screen of eng. workbench is intended for engineer but perhaps we could put a UD field checkbox for QA method approval, would then just have to figure out a trigger for the QA approval
What you are trying to do could be accomplished by task sets.
Another approach is to use a Checkbox and Date field that is locked by by security to be updated only by Security Group QA.
When the traveler is printed, water mark the traveler - “not Approved” - until QA has approved it.
I have done this for First Article required - while the part is in prototype stage - when it goes to production - QA signs off the Checkbox and dates it.
This will require
- Customization of the PartRev tab in Part Entry
- Adding security control on the fields added
- Updating Job Traveler, BPM to prevent releasing a job, etc. based on the checkbox status.