Appearance
Resource Capacity Setup
Resource Capacity setup defines the resources that can be scheduled or measured.
This is shared setup. A service domain such as Production, Driving, Agriculture, or Inspections narrows business context, but it does not create a separate resource master.
Open Resource Capacity -> Setup.
Workspace Reference
| Workspace | Open From | Main Action | Main Record |
|---|---|---|---|
| Resource Types | Resource Capacity -> Setup -> Resource Types | Create or edit resource type | Classification for resources such as instructor, vehicle, machine, room, line, or service point. |
| Resources | Resource Capacity -> Setup -> Resources | Create or edit resource | Actual capacity unit that can be booked, scheduled, costed, or measured. |
Resource Types
Resource types classify resources. Examples include instructor, vehicle, machine, room, production line, field officer, or inspection team.
Resource types help users filter resources and apply consistent scheduling behavior.
Important fields include:
| Field | Required | Meaning |
|---|---|---|
| Name | Yes | User-facing type name. |
| Category | Recommended | Human, equipment, machine, room, vehicle, work center, production line, service point, or other. |
| Domain | Recommended | Operating area or business context. |
| Default Capacity | No | Typical capacity quantity for this type. |
| Capacity Unit | Recommended | UOM used to measure capacity, such as unit, hour, seat, batch, or another approved unit. |
| Description | No | Guidance for users selecting the type. |
| Active | Yes | Whether the type can be used. |
Use resource types to standardize scheduling. Do not create a new type for every individual resource.
Resources
Resources are the actual capacity units used in operations. A resource should include a clear name, type, status, location or service scope where applicable, and any relevant operational notes.
Important fields include:
| Field | Required | Meaning |
|---|---|---|
| Resource Type | Yes | Approved type this resource belongs to. |
| Name | Yes | Visible resource name. |
| Status | Yes | Available, unavailable, maintenance, or retired. |
| Capacity | Recommended | Quantity the resource can provide. |
| Capacity Unit | Recommended | Shared UOM for capacity. |
| Cost Rate | No | Optional planning or costing rate. |
| Currency | Required when cost rate is used | Currency for the cost rate. |
| Location | Recommended | Shared operational location. |
| Resolved Business Unit | Informational | Business unit shown from the selected location or resource where available. |
| Resolved Location | Informational | Location shown from the selected resource during booking where available. |
| Legacy/External Location Label | No | Optional external label only, not the main location reference. |
| Description and Active status | Recommended | Usage guidance and whether the resource is available for new scheduling. |
The selected operational location is the canonical location. Avoid using free-text location labels when the shared location exists.
Shared Setup Dependencies
Resource Capacity depends on several shared setup areas:
- Operational Locations for where resources exist or operate.
- Units of Measure for capacity units.
- Business Units for ownership and reporting scope.
- Workflow for approval behavior where configured.
- Events, Documents, Inspections, Production, and Project Control for follow-up work linked to resource usage.
When another service opens resource setup in context, use that context only to decide scope. The actual type, resource, slot, booking, and utilization records should still be maintained through the shared Resource Capacity primitive.
Setup Checklist
Before booking resources:
- Confirm resource types match how the business schedules work.
- Confirm inactive or unavailable resources are not offered for booking.
- Confirm resource names are clear to operators.
- Confirm capacity quantity and capacity unit are meaningful.
- Confirm shared locations are selected instead of only typing external labels.
- Confirm cost rate and currency are correct where utilization or costing depends on them.
- Confirm users know which resources are shared across services.
