Appearance
Resource Capacity Overview
Resource Capacity helps teams plan and monitor the availability of operational resources. A resource can represent a person, vehicle, room, machine, station, asset, or any other constrained item used by the business.
It is a shared scheduling primitive. Service modules such as Production, Driving, Events, Inspections, or Agriculture may open resource flows in narrower context, but they should not create separate resource ledgers.
What Resource Capacity Helps Manage
Use Resource Capacity to manage:
- Resource types and categories.
- Operational resources such as people, vehicles, rooms, machines, work centers, production lines, and service points.
- Shared operational locations and capacity units.
- Capacity slots or availability windows.
- Resource bookings.
- Utilization review.
- Availability conflicts and over-capacity risks.
Main Areas
Setup defines resource types and resources.
Operations manages capacity slots, bookings, and utilization.
Workspace Reference
| Workspace | How Users Reach It | What Users Usually Do There |
|---|---|---|
| Resource Types | Resource Capacity -> Setup -> Resource Types | Define resource classes, category, unit, and scheduling behavior. |
| Resources | Resource Capacity -> Setup -> Resources | Register people, vehicles, rooms, machines, stations, or other constrained resources. |
| Capacity Slots | Resource Capacity -> Operations -> Capacity Slots | Create or review availability windows and blocked periods. |
| Bookings | Resource Capacity -> Operations -> Bookings | Reserve or confirm resources for operational work. |
| Utilization | Resource Capacity -> Operations -> Utilization | Review load, conflicts, availability, and over-capacity risk. |
Operating Model
A typical resource capacity flow is:
- Define resource types and the default capacity unit.
- Register resources with status, location, capacity, cost rate, and currency.
- Create capacity slots or availability windows for resources.
- Book resources for operational work.
- Monitor utilization and conflicts.
- Adjust schedules when demand or availability changes.
- Use linked events, documents, inspections, production, or project work as follow-up evidence where needed.
Where It Fits
Resource Capacity can support driving lessons, service events, production stations, inspection teams, asset usage, room bookings, field visits, and other scheduled operations.
It should use shared operational locations and UOMs so that capacity planning stays aligned with assets, inventory, production, events, inspections, and reporting.
Production also exposes contextual Resource Capacity screens under Production -> Setup and Production -> Operations. Those screens use the same primitive but automatically filter resource types, resources, slots, bookings, and utilization to the PRODUCTION domain, so work centers, production lines, machines, tools, and labor pools are managed from Production without duplicating the resource model.
The same rule applies elsewhere: service context may narrow what users see, but the underlying resource types, resources, slots, bookings, and utilization truth remain in Resource Capacity.
Core Statuses
Resource statuses include Available, Unavailable, Maintenance, and Retired.
Slot statuses include Open, Blocked, and Closed.
Booking statuses include Draft, Reserved, Confirmed, In Progress, Completed, Cancelled, and No Show.
Users should distinguish resource status from slot status and booking status. A resource may be available overall but have a closed slot for a specific time, or a confirmed booking may still be blocked if the selected resource becomes unavailable.
