Ordered Route

This feature is no longer part of ProcessModel

The Ordered route is no longer a route type in ProcessModel. It held an entity on the route until an order signal released it, a signal-based way to control just-in-time flow.

For demand-driven flow in ProcessModel 7.0, use a Pull route, where the destination pulls entities from its sources as it has capacity.

LegacyHow this worked in the previous version

An ordered routing causes the routing entity to wait until an order signal is received (see Order Signals). Entities will wait in the output queue of the activity (or in the storage) from which the Ordered routing is connected until the Order Signal is received. If you want to continue processing entities behind the entity waiting for an order signal, make sure the capacity of the output queue or storage is sufficient.

Usage

Just-in-time systems require that production inventory is controlled. The Ordered route in conjunction with the Order Signal allow the control of when and how much is ordered from an upstream activity.

Move Time Time to move to the next activity or storage. Any expression is valid.

Routing Types

The following routing types are available:

• Alternate
• Attach
• Conditional
• Create
• Detach
• Else
• Ordered
• Percentage
• Pickup
• Renege