Forum Discussion
Thank you for the elaborate reply AngelaIp !
I think your statement about the Process Plan updates being part of an ECO is relatable. Therefore, I think an ECO should trigger an MCR so the MBOM and related routings are updated. But I am now thinking of going one level deeper as this effectively would result in the same challenge. So an ECO would trigger MCR (we call it M-ECN) which perhaps triggers another change container specifically for updating affected process plans and active process plan items (production files).
The synchronization of ERP v.s. PLM, including 'single source of truth' v.s. 'single source of change' is a heavy subject that could deserve a thread on its own.
Let's indeed hope others will recognize these challenges and are willing to share some ideas!
Daan
I agree to your MCR idea! I forgot, that our ECN serves also this purpose in some way.
Our ECN is created after the ECO is finished and tells people about the next steps (update MBOM, write PCN, update products in warehouse, etc.).
Basically the ECN is converted from the ECO.
In our case ECN will also track the MBOM change, but the ECN itself doesn´t create the new MPP revision like the Express ECO would do for Parts.
We often also have to update manufacturing equipment, test systems, etc. . So people most of the time has to do much more than just the MBOM.
But I have to admit, the revision update would fit into the process, just as you describe.[emoticon:5ce50ea3f9eb49809e861e8733750338]
I right now remember an 8 year old support ticket of mine, that might be relevant again! I asked the question if an finished ECO can automatically start another change process.
The issue was targeted to the client side aspect of the task. -> instantly open the window of the 2nd change process after ECO was finished.
Feel free to write Aras if you´re are interested too in this one:
--> IR-039815 Allow Client methods to run from a Workflow Process - 18.02.2016
I just realized that I am still waiting for the solution![emoticon:98f842990f454422aa6a04953955f9d9]
Angela