Skip to content

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

WorkspaceOpen FromMain ActionMain Record
Resource TypesResource Capacity -> Setup -> Resource TypesCreate or edit resource typeClassification for resources such as instructor, vehicle, machine, room, line, or service point.
ResourcesResource Capacity -> Setup -> ResourcesCreate or edit resourceActual 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:

FieldRequiredMeaning
NameYesUser-facing type name.
CategoryRecommendedHuman, equipment, machine, room, vehicle, work center, production line, service point, or other.
DomainRecommendedOperating area or business context.
Default CapacityNoTypical capacity quantity for this type.
Capacity UnitRecommendedUOM used to measure capacity, such as unit, hour, seat, batch, or another approved unit.
DescriptionNoGuidance for users selecting the type.
ActiveYesWhether 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:

FieldRequiredMeaning
Resource TypeYesApproved type this resource belongs to.
NameYesVisible resource name.
StatusYesAvailable, unavailable, maintenance, or retired.
CapacityRecommendedQuantity the resource can provide.
Capacity UnitRecommendedShared UOM for capacity.
Cost RateNoOptional planning or costing rate.
CurrencyRequired when cost rate is usedCurrency for the cost rate.
LocationRecommendedShared operational location.
Resolved Business UnitInformationalBusiness unit shown from the selected location or resource where available.
Resolved LocationInformationalLocation shown from the selected resource during booking where available.
Legacy/External Location LabelNoOptional external label only, not the main location reference.
Description and Active statusRecommendedUsage 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.

Pinkapple ERP by Stat Solutions Network