Oracle Field Service Resources, Capacity, and Routing
Resources, Capacity, and Routing
This domain tests how Oracle Field Service models the workforce and decides who gets which activity. Know resource records, buckets, work zones, work skills, shifts, capacity, routing plans, routing profiles, and the difference between daily and immediate routing.
Core rules
- A resource is a technician or crew. Resources belong to a bucket in the resource tree; buckets aggregate capacity and can carry work zones and skills.
- Work zones describe geography; work skills describe capability. Routing matches activity requirements to resource attributes.
- Capacity is consumed by activity duration plus travel; capacity categories and time slots define when work can fit. Shifts and calendars define availability.
- A routing plan contains a routing profile that sets matching keys (bucket, work zone, skill, time slot), priority, and travel rules. Daily routing builds a plan for a day; immediate routing assigns urgent work.
- Routing statistics show why candidates were included or excluded.
Worked example
Two HVAC technicians sit in bucket North, work zone Boston, skill HVAC, with eight-hour shifts. A four-hour job has a 08:00-12:00 service window and 30 minutes travel. The routing plan matches bucket North and skill HVAC, checks the time slot and remaining capacity, and ranks the resource with the least travel. If one technician already has six hours booked, only the other fits. The reasoning: bucket and skill are hard filters; capacity and time window are feasibility checks; travel is a ranking factor.
Traps
Treating bucket capacity as an individual's capacity; putting a resource in the wrong work zone; omitting a mandatory skill; ignoring time zones; assuming a routing plan overrides a shift or calendar; not publishing resource changes.