3.7 – Resource Assignments
Resource assignments define the use of one or more resources in performing an activity or moving an entity. For each entity that is processed or moved, each assigned resource is captured and held until it is freed via the resource connection or a FREE statement in Action logic. While the resource is captured, it is not available for use by other activities or routing connections. To be pulled away from a task the resource is performing, it must be interrupted by a resource assignment that has the Respond immediately box checked.
Resources may be captured for performing an activity or a move. They may also be freed or kept after the activity or move is completed. Multiple or alternative resources may be used for an activity or move.
A connected resource is always captured BEFORE any defined activity or move time and freed AFTER an activity or move time. If an input queue is defined for an activity, the connected resource is captured prior to the entity entering the activity. If no input queue is defined, the entity enters the activity and then captures the resource. Multiple resources required for an activity or routing are not captured until they are all available. To capture multiple resources as each becomes available, use a GET statement in the Action logic of the activity or routing.
Following is an explanation of each type of resource assignment and the information in its properties dialog.
• Get and Free
Using Multiple Resources
You may use multiple resources and mix the resource connection types. You can mix multiple and alternate resources. When defining multiple resource connections, remember that they are executed in the order in which they were defined. To change that order, disconnect the resource connections and reattach them in the order you desire.
Resource Priority Values
There are 10 levels of priority values: 0 – 99, 100 – 199, 200 – 299 . . . 900 – 999. 0 – 99 is the only non-preemptive level.
Preemption means that the current work being done by a resource will be interrupted in order for the resource to go to the location of the preemptive GET. After that higher priority work is complete, the resource will return to the interrupted location. Preemption will occur only when the value of the calling priority is at least one level higher than the resource’s current priority.
The calling priority is at least 100 higher than the resource’s current priority.
For example, if a resource is working at a priority of 50, then a priority call of 150 will be required to perform a preemption. The 150 GET will be completed before returning to the initial 50 GET.
Using a priority which is 300 or higher will bring a down (or off shift) resource back on-line (or on shift).
Resource Priority, Shifts, and Interrupt
The Resource priorities, interrupt, shifts, and ‘Interrupt current activity to go off shift or on break’ can be used in a model together, the following restrictions apply.
- A resource priority of more than 100 is an interrupt priority, meaning that if a resource is working on a task that has a lesser priority the resource will leave that task and start working on the priority that is 100 or more.
- If the resource priority is less than 100, but it is higher than the other task the resource is working on, the resource will not leave the task its working on, but will complete it and then come to work on the task with greater priority.
- If ‘Interrupt current activity to go off shift or on break’ is checked on shift of the resource, this will mean that the ‘Interrupt current activity to go off shift or on break’ has a priority of 299. The resource will leave any task its working on and go offline.
- An interrupt priority that is used to have the resource leave the task its working on, and start working on another task will work with ‘Interrupt current activity to go off shift or on break’ if the priority is set to less than 199.
- An interrupt priority of greater than 199 will keep a resource online, even if its scheduled to go offline and ‘Interrupt current activity to go off shift or on break’ is checked.
- An interrupt priority of greater than 599 will bring back an offline resource online, even if its offline and ‘Interrupt current activity to go off shift or on break’ is checked.