Prioritization of Resources

Parent Previous Next

In Model 14's report page we found out, that the Project Manager has to wait for a Developer at activity Develop(internal) disproportionately long. This bases on the fact, that all the activities have the same resource priority assigned. The resource manager (internal feature of the simulation) allocates the process instances to the respective resource's queue. Unfortunately the resource manager does not provide a sophisticated way to improve this allocation. It simply checks the activity's resource priority, and then sorts the queue using this priority.

Furthermore, the resource manager inserts the lastly arrived process instance in the first place of the respective sorted sequence in the queue.


This procedure is repeatedly executed. So, every following PISC has to wait longer for a Developer that the previous one. This is the result of equal prioritization of all activities in reference to the resources. All activities have the same importance for the queue and they are worked off using the FIFO (first in, first out) principle.

To avoid the behavior from the previous example, you can set the Resource Priority in the Simulation Properties of an activity (Optional Simulation Properties, see the figure below). This property defines the priority of an activity for the resource queue. There are five different levels (lowest, low, medium, high and highest). These levels are used to sort the activities in the queues of a resource pool, i.e. the higher the level, the more an activity is sorted to the fore.

Figure 1: Simulation Properties of an activity -

Resource Priority property highlighted

Change Model 14's resource prioritization

Take Model 14 as an example and set the Resource Priority of the Develop(internal) activity to high. After simulating the model, you will discover a much better utilization of the Project Manager. See for yourself!