Appearance
Resource Capacity Operations
Resource Capacity operations help users manage availability, bookings, and utilization.
These are shared operational records. If a service such as Production or Events launches users into a filtered booking or utilization flow, the resulting slots, bookings, and utilization history still belong to the shared Resource Capacity primitive.
Open Resource Capacity -> Operations.
Workspace Reference
| Workspace | Open From | Main Action | Main Record |
|---|---|---|---|
| Capacity Slots | Resource Capacity -> Operations -> Capacity Slots | Create, edit, block, close, or review slot | Availability window for a resource. |
| Bookings | Resource Capacity -> Operations -> Bookings | Create, confirm, update, cancel, or complete booking | Reservation of a resource for operational work. |
| Utilization | Resource Capacity -> Operations -> Utilization | Review utilization | Resource usage, availability, bottlenecks, and no-show/cancellation patterns. |
Capacity Slots
Capacity slots define when a resource is available or planned for use. Slots may represent working hours, lesson periods, production capacity, inspection windows, or other scheduling blocks.
Important slot fields include:
| Field | Required | Meaning |
|---|---|---|
| Resource | Yes | Operational resource the slot belongs to. |
| Status | Yes | Open, blocked, or closed. |
| Start and End | Yes | Availability window. |
| Capacity Quantity | Recommended | Quantity available in that window. |
| Reason Code | Recommended for blocked or closed slots | Why a slot is blocked, closed, or specially classified. |
| Notes | No | Operational context. |
Use open slots for bookable availability. Use blocked slots for maintenance, downtime, leave, service interruption, reserved capacity, or another planned restriction. Use closed slots when the window is no longer usable.
Bookings
Bookings reserve a resource for a specific operational need. Users should confirm the resource, time, linked activity, owner, and booking status.
Bookings should be kept current so that other users do not rely on outdated availability.
Important booking fields include:
| Field | Required | Meaning |
|---|---|---|
| Capacity Slot | Optional | Selected availability window where slot planning is used. |
| Resource | Yes | Resource being reserved. |
| Resolved Business Unit | Informational | Business unit inherited from the selected resource where available. |
| Resolved Location | Informational | Location inherited from the selected resource where available. |
| Status | Yes | Draft, reserved, confirmed, in progress, completed, cancelled, or no show. |
| Start and End | Yes | Booking time window. |
| Booked Quantity | Recommended | Capacity consumed. |
| Priority | No | Ordering or conflict importance. |
| Notes | No | Context for the booking. |
Use Reserved when the booking is held but not fully confirmed. Use Confirmed when operations should rely on the booking. Use In Progress while the work is happening. Use Completed, Cancelled, or No Show to close the operational outcome.
Utilization
Utilization views help managers understand how resources are being used. High utilization may indicate a bottleneck, while low utilization may indicate underused capacity or poor scheduling.
Review utilization by resource type, resource, location, business unit, date range, status, and linked activity where the view supports it.
Useful questions include:
- Which resources are overused or underused?
- Which time windows are creating bottlenecks?
- Are no-shows or cancellations wasting capacity?
- Are maintenance or blocked slots reducing availability?
- Is demand exceeding the available resource pool?
- Do bookings align with production, lessons, events, inspections, or service demand?
Conflict Management
When a resource is double-booked, unavailable, or over capacity, users should resolve the conflict before the operational activity starts.
Common conflicts include:
- booking outside an open slot;
- booking a retired or unavailable resource;
- booking more quantity than the slot allows;
- overlapping confirmed bookings;
- resource under maintenance;
- location or business unit mismatch;
- stale draft reservations that should be cancelled or confirmed.
Conflict resolution options include changing the time, changing the resource, reducing quantity, cancelling stale bookings, opening additional capacity, or escalating to a manager when the conflict is intentional.
Cross-Module Follow-Up
Resource bookings often connect to operational work:
- driving lessons and instructor or vehicle availability;
- production stations and production lines;
- inspection teams and quality windows;
- service events and room or technician capacity;
- asset usage and custody;
- project or field work scheduling.
Keep linked events, documents, inspections, and production records updated so utilization reports explain not only that capacity was consumed, but why it was consumed.
Do not create service-owned copies of bookings or slot ledgers to explain the same capacity usage. Let the service provide context and let Resource Capacity remain the scheduling source of truth.