Resources

In AnyLogic, a resource is a special type of agent that other agents use to model assets that are in limited supply, that is, their quantity is finite. It can be used to model equipment, personnel, and vehicles that are necessary to perform specific tasks within the model.

In each model, resources reside within the ResourcePool blocks. From there, they are recognized as resources by other blocks and can be assigned various tasks. Resources from these blocks can be used by multiple other blocks at once. ResourcePool blocks are a primary way to create resources: you cannot create resources as regular agents via the Source and similar blocks.

The most simple tasks taking advantage of resources can be implemented with the Service block. This block is basically a combination of three other blocks: it seizes a specified number of resource units (the Seize block), models an operation with it (the Delay block), then releases the units (the Release block).

To compose a more complex process involving resources, start by adding a Seize block on the flowchart. It captures a necessary number of resource units. Then, you can model the whole process with other blocks. After the tasks are done, free up the busy resource units by adding a Release block on the flowchart.

As a special type of agent, resources have their own API. To learn more about available functions, see the corresponding article.

The following Process Modeling Library blocks work with resources:

For information about how to create a custom resource type with its own flowchart, parameters, and animation shape, see Creating custom resource types.

A block that requires multiple varying resources can use resources from one or multiple ResourcePool blocks, depending on the concept you use in your model:

• When you need the block to use multiple resources of the same pool (for example, two workers, three nurses, and so on):
  1. Set the Seize resources property to units of the same pool.
  2. In Resource sets (or the corresponding Resource pool property of your block), select the ResourcePool you need using the drop-down list or by clicking and selecting the pool in the graphical editor.
  3. In the Number of units field, specify the number of resource units the task requires.

  

• When you need the block to use multiple different resource units (for example, a robot and a controller, workers with different skill sets, and so on):
  1. Set the Seize resources property to (alternative) resource sets.
  2. Click the button to select one of the existing ResourcePool blocks, or
     Click and select the pool in the graphical editor.
  3. Repeat the action while specifying another ResourcePool.
  4. Specify the number of required resource units in the right part of the list.

  

• When you need the block to consider multiple resource sets, with varying numbers of different resource units (for example, the task can be done with 2 robots and 1 controller, but if there is not enough free robots, a human assistant can replace the robot):
  1. Set the Seize resources property to (alternative) resource sets.
  2. Click the button to select one of the existing ResourcePool blocks, or
     Click and select the pool in the graphical editor.
  3. Repeat the action while specifying another ResourcePool.
  4. Specify the number of required resource units in the right part of the list.
  5. Create the second list of resources by clicking  Add list.
  6. Repeat steps 2–4 to complete the second list.
  7. Repeat these steps until you create the necessary resource lists.
     Do not add empty ResourcePool lists: it may cause issues.
  When the agents requiring resources enter the block, the first resource list is checked for availability. If there is not enough free resource units specified by the first list, the second given list is checked for availability, and so on.

  

The model below demonstrates various use cases for resources, including multiple sets of them. It contains a huge number of resources, assigned to different tasks within the Main agent. Most of the time, resources are used by the Service blocks, though there are cases when the work with the resource starts with the Seize block to model a more complex scenario.

Tasks are Java entities that the model and its parts use to manipulate resources. With tasks, AnyLogic decides which job to assign to the resource unit, when to free the unit up, and so on. This means that in most cases, if at some certain point in time, the resource unit does not have a task associated with it, then this resource unit does nothing.

Resource tasks are visible in the inspect window of the ResourcePool block during the model run.

There is a number of different task types. Some of them are:

• A service task is a basic task type assigned to the resource seized by some agent
• A wrap-up task commands the resource unit to stop its current action and go to its home location. It is created automatically by the Release block.
• An end-of-shift task commands the resource unit to stay at its home location and do nothing. For example, when the ResourcePool has its When capacity decreases property set to units are preserved, the “end-of-shift” task is what the resource units actually do.
• A custom task is what is created by the Downtime block. It models downtimes and custom tasks implemented by this block.

Each resource unit can be assigned a task from two queues:

• The first queue is the one generated by the ResourcePool the unit belongs to. It combines all the tasks associated with this particular ResourcePool and is managed by ResourcePool itself.
  In simple models, the queue of ResourcePool is the primary queue that operates resources. ResourcePool will simply assign resources in accordance with rules set in its properties. For more information, see the corresponding article.
• The second queue is the individual queue of the specific resource unit. This queue consists of tasks that only this particular resource unit can complete: for example, if this particular resource has an “end-of-shift” task associated with it, or the block requesting the resource has the Wait for original resource policy enabled.
  Additionally, some blocks may have additional rules for selecting resources (the Customize resource choice is enabled in properties and the Resource choice condition is set). For more information, refer to the documentation on a specific block.

A set of resources may have multiple tasks with different priorities and preemption policies.

• If all tasks have the same priority, they will be executed in the usual way following their occurrence schedule. If there are enough resource units available, tasks can be executed simultaneously. If two tasks have the same priority, but one of them was suspended for some reason, this suspended task will be picked¹.
• If you have configured no preemption policy for the tasks, these tasks will be executed one after another following their occurrence schedule. If there are enough resource units available, tasks can be executed simultaneously.
• The occurrence of one task does not reset the priorities for other tasks.

How can we improve this article?

Send