AnsweredAssumed Answered

Using ePDM to Track "Checklists"

Question asked by Kevin Stickels on Mar 7, 2013
Latest reply on Mar 7, 2013 by Tim Webb

We are well on our way to implementing ePDM but, as Murphy's Law persists, questions have arisen. The change process is a bit more complex than I would like but the company is moving from Agile/ Product Center to ePDM and, as much as is feasible, wants them to act the same. My question is regarding what we term the CN (Change Notification/ Release) phase of changes. The Change Order is processed and approved, changes are made ot the models, assemblies, and drawings and the whole metadata is ported through an "adapter" (xml file) to our MRP system. Management has asked that I try to incorporate a checklist that used to be emailed with released changes into ePDM.

   At first, it was nothing more than name and date fields for each department to sign off that they had updated/ reviewed/ verified the data transferred to the MRP system. Now I have been asked to create checklists in the ECO data card where the various manager "checks off" each table he/she has to review. When all the checks are completed, the workflow state changes to the next department. The issue I have is that I was handed the Excel sheet that traveled with the "released" ECO and there are 188 separate checkboxes listed. Add to that each box will need another checkbox for "Not Required" and a name and date variable and the process gets completely ludicrous (188*4 = 752+ variables - Oh My!). Has anyone out there had any similar experiences and suggestions?  While I would love to eliminate or embed the checklist, it doesn't seem logical. Any input would be greatly appreciated. Thanks