1. Introduction
The Resource Unavailability Register allows administrators and production planners to track periods during which a resource (Employee, Machine, or Tool) is unavailable for work. This module ensures accurate capacity planning, prevents scheduling conflicts, and provides essential data for KPI calculations related to resource utilization.

1.1 Resource Unavailability Register
This section is active when the resource master data is editable.
- Resource – Automatically populated from the Resource Master register; cannot be modified.
- Date – Specify the period when the resource is unavailable.
- Reason – Select from the downtime reason database. <br> – This field is editable: if the reason is not listed, it can be entered manually and saved for future use.
1.2 Rules
- The system monitors the dates:
- If within the specified period → status Closed (cannot be scheduled for work).
- If outside the period → status Open.
- If the “End Date” field is empty → resource is unavailable. Filling it is required to reactivate the resource.
- The table must indicate both Open and Closed statuses.
- The system must track the number of hours the resource was unavailable – required for KPI calculations.
- Calculations consider calendar settings:
- If no weekend work → only weekdays counted.
- If multiple shifts → multiply hours by the number of shifts.
Example: One day lost in a three-shift schedule = 3 × 8h = 24h unavailable.
1.3 Table Columns
| Column | Description |
|---|---|
| Reason ID | Database ID of the downtime reason. |
| Reason Name | Description of the downtime reason. |
| From (Date) | Start date of unavailability. |
| To (Date) | End date of unavailability. |
| Work Hours | Number of unavailable hours, calculated based on shifts and calendar settings. |