Order of Processing

As an entity moves through the model, ProcessModel handles each step in a set order. Knowing the order helps when you write action logic or read a trace.

At an activity

1. Batch, if the activity groups entities together.
2. Get the connected resources it needs.
3. Attach any child entities.
4. Run the activity’s action logic.
5. Spend the processing time.
6. Add the activity’s cost.
7. Detach child entities.
8. Free the resources, unless they are held for a later step.
9. Batch or unbatch, if that is set to happen after the activity.

On a route

1. Get the connected resources.
2. Run the route’s action logic.
3. Spend the move time.
4. Free the resources.
5. Add the route’s cost.

LegacyHow this worked in the previous version

The sequence of processing events as entities arrive at and leave activities, and route between activities is as following.

At an Activity

1. Any batching function before an activity
2. Get connected resources (Get or Get & Free)
3. Attach child entities
4. Perform action logic in the Action tab
5. Perform processing time in the General tab
6. Perform activity cost calculations
7. Detach child entities
8. Free connected resources (Free or Get & Free)
9. Any batching function after an activity

At a Routing

1. Get connected resources (Get or Get & Free)
2. Perform action logic in the Action tab
3. Perform routing move time in the General tab
4. Free connected resources (Free or Get & Free)
5. Perform routing cost calculations