Capacity reservation rules
Capacity Reservations enable you to efficiently distribute the total work capacity among work order tasks based on their attributes, such as work type, location, and priority.
You can create multiple reservation rules to manage and prioritize work order tasks based on their attributes, such as priority and demand. Each rule assigns a percentage of the total capacity to a specific task type or condition. This helps distribute workloads efficiently and make the best use of available resources.
Reserve the workload capacity
Create reservation rules based on different types of work to reserve the workload capacity for work order tasks.
Before you begin
Role required: wm_admin, wm_manager, and wm_internal_contractor_manager
Procedure
| Field | Description |
|---|---|
| Name | Name of the reservation (e.g., "Daily Task Allocation"). |
| Description | Description of the reservation category (e.g., "Reservation for daily Install and Breakfix tasks"). |
| Table | wm_task table on which the condition applies. This field is read only. |
Create a reservation rule
Reservation rules help allocate a specific percentage of capacity for different attributes of work order tasks, such as work type, location, or priority. This confirms efficient task management and meets specific workload demands.
Before you begin
Role required: sn_fsm_tp.fsm_territory_manager, wm_manager, sn_fsm_capacity_mg.wm_capacity_write, sn_fsm_tp.fsm_territory_planner, wm_admin, wm_contractor_manager_int
Procedure
| Field | Description | Example |
|---|---|---|
| Name | Name of the reservation rule. | |
| Demand Channel | Select the demand channel for the reservation rule. For more information, see Create a demand channel. Note: Applies only if territory plugin is installed. |
Example: "Install" or "Breakfix". |
| Table | The default table is wm_task on which the rule applies. (This is read only.) | |
| Condition | Define conditions to filter the workload. Note: Applies only if territory plugin is not installed. |
Example: Reserve capacity for Install tasks: . |
| Percentage Allocated | The percentage of total capacity reserved for this rule. Sum of all percentage allocated should not exceed 100 of all the reservation rules within the reservation. | Example:
|
| Allow Overflow | Enable or disable overflow for tasks beyond the reserved percentage. When enabled, enables tasks to exceed their reserved percentage if there’s unused capacity. | Example: Two Reservation Rules are defined:
This means only 25% + 25% = 50% capacity is allocated via the defined reservation rules. Hence, there is 100% - 50% = 50% additional capacity that has not been allocated to any rule. When Allow Overflow is enabled and incoming work exceeds the predefined 25% allocation for either "Install" or "Breakfix," this excess will be taken from the remaining 50% unallocated capacity pool. |
| Maximum Overflow Percent | Define the maximum percentage that a reservation can exceed its allocation. | Example:
|
| Order | Determines the sequence in which rules are applied during task assignment. | Example:
|
Capacity allocation based on reservation rules
- Total capacity: 8 tasks
- Reservation Rules:
- Install: 25% (2 tasks reserved)
- Breakfix: 25% (2 tasks reserved)
Note:Unallocated Capacity: 50% (4 tasks)
- The Allow Overflow option is disabled for the "Breakfix" service.
- Scenario: "Breakfix" receives 3 incoming tasks.
- 2 tasks are assigned based on the reservation rules.
- Since Allow Overflow is disabled, no additional tasks are allocated from the unreserved capacity.
- The Allow Overflow option is enabled for the "Breakfix" service.
- The Maximum Overflow Percent is set to 50%.
- Scenario: "Breakfix" receives 3 incoming tasks.
- 2 tasks are assigned following the reservation rules.
- 1 additional task is allocated from the unreserved capacity (utilizing up to 50% overflow).
- The system makes room to accommodate 1 more task within the overflow threshold.