Hello,
I would like to ask some best practices related with Protocol Instance.
If there are several materials in a protocol instance:
- Set a root cause for each material. For now, I can set a root cause for this instance, but not for each material.
- If the disposition is executed, the material can split from the protocol instance and back to manufacturing ( no need to wait for other materials). For some large industrial equipment, it will be a long time for all the materials’ disposition executed.
Could you give me some suggestions? Thank you.
Regarding the first question, the root cause is for the protocol instance as a whole - it’s not possible to set it per material.
Hello Ariel
I already asked Siti Nor Asikin binti Kamalzaman and Pedro Teixeira to share here what they did in another project.
Meanwhile, I’m going to present you a Workaround for your first question:
1st) Let’s imagine you have 3 different protocols definition in your Environment
2nd) And at this point you have 5 instances still opened for the 3 protocol definitions
3rd) Let’s focus on the NCMR Protocol.
This instance of the protocol NCMR has 3 materials assigned to it
4th) One of the protocol State has a Checklist
This Checklist has 1 item to identify the material ID and the Root Cause
5th) EXECUTE the Protocol Instance. In the state where you must identify the Root Cause for each Material, Use the Checklist Parameters
Regarding your 2nd question, I’m not sure if I fully understood. But in any case, what do you intend? Or what would you like our MES to be capable of doing?
Thanks
Hi @Ariel_Luo ,
From my previous experience when I had a similar scenario in hands, the Team had to make a customization that created a Protocol Instance proxy whenever a split happens, associating the same to the new split, which enabled the material segregation from the remaining materials that were kept linked into the original Protocol Instance. On the other way around, whenever we would need to perform a merge between materials where each held a specific Protocol Instance was define business rules on a Generic Table that the system would follow in order to merge parameters and reach to a unique a common Protocol Instance.
