Professional Documents
Culture Documents
I have a model that normally processes parts in the sequence Server1, Server2, Server3,
Inspect, Sink but based on the result of the inspection, it sometimes must be diverted to
Adjust and then restart at Server2.
Categories:
Add-On Process Logic, Sequence Tables
Key Concepts:
Sequence Table, By Sequence, Entity Destination Type, Add-On Process, SetRow Step
Assumptions:
The source produces one type of entity. The entity will follow a primary sequence of:
Source Server1 Server2 Server3 Inspect Sink.
But if it fails inspection (30% of the time), it will divert to an alternate sequence of:
Adjust
and then resume its normal sequence from Server2.
Technical Approach:
Separate Sequence Tables are created for the entity to follow its normal sequence and
sometimes divert to another route. We will create one main sequence table which is identical
to the first sequence specified above. We will create an additional sequence to switch to if the
entity fails and has to go to the Adjust server. In order to make decisions at the inspection,
add-on processes will be created.