Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA™ Manufacturing Execution System 2023 R2

Scenario 5

  • Last UpdatedMay 17, 2023
  • 1 minute read

Given the same conditions as in scenario 4, and assuming that production is reported from the job for operation 200-Dyn1 with a reason code of R1, the result is as follows. The fourth row of the dynamic routing usage table applies to this production.

This scenario illustrates the use of the dynamic routing parameter Use label in dynamic routing work order or operation IDs. If this parameter had been set to No, the system would be instantiating a second job with operation 200 as well as a second job for operation 210.

If the job for operation 200-Dyn2 was started and an attempt was made to report production from it using reason R1, you might expect the system to create dynamic routing jobs for operations 200-Dyn3 and 210-Dyn3. It would except that the dynamic routing parameter Max Dynamic Routes is set to 3 in the fourth row of the dynamic routing usage table. Since rework is being differentiated by item reason and work order ID, and this item reason has already been used three times to generate dynamic routing jobs for this work order, the production transaction would fail. The operator would need to choose a different reason (probably one that scrapped this production).

TitleResults for “How to create a CRG?”Also Available in