Oracle Field Service Implementation Professional key terms

A person, crew, or piece of equipment that can be assigned work in Oracle Field Service. Each resource carries a calendar, skills, work zones, and capacity settings that determine which activities it can receive.

A configurable grouping of resources used for routing, reporting, and visibility. Activities are routed to buckets, and the routing engine then selects the best individual resource within that bucket.

A geographic area defined by coordinates, polygons, or postal codes. Work zones restrict which activities a resource can be assigned and are a primary filter in routing and capacity planning.

The amount of work a resource can absorb in a period, expressed through capacity categories, quotas, or maximum activity counts. Capacity drives whether the routing engine can add more activities to a resource's day.

A named unit of work (for example, installations or service calls) against which a resource's availability is measured. Each category has its own limit per time period, allowing mixed-skill resources to be constrained realistically.

A per-resource limit on how much of a capacity category can be consumed within a defined time window, such as a day or week. Quotas prevent overloading a resource even when time remains on the calendar.

A configurable interval of the working day used to measure and limit resource capacity. Capacity and quotas are evaluated against time slots, which also shape how arrival windows are offered to customers.

A configuration object that controls how activities are matched to resources: which buckets and work zones apply, which filters run, and in what order candidate resources are ranked.

A collection of routing settings attached to a routing plan, including travel estimation, activity duration handling, and optimization preferences. Profiles let one routing plan be reused with different behavior variants.

The routing engine's process of reordering and reassigning activities across a resource's day to reduce travel and improve schedule fit. It runs on demand or on a schedule and can be scoped to selected resources.

The estimated time to move between two locations, calculated from distance and speed assumptions or an external mapping service. Travel time is subtracted from available working time before activities are placed.

The record of a resource's working hours, shifts, breaks, and absences. Routing only places activities inside open calendar time, so calendar accuracy directly affects schedule feasibility.

A defined block of working time within a resource's calendar, with a start and end. Shifts can repeat on a pattern and are combined with breaks and exceptions to produce actual availability.

A capability or certification assigned to a resource that can be required by an activity. Routing matches required skills to resource skills, and missing skills make a resource ineligible for that activity.

The core unit of scheduled field work in Oracle Field Service, representing a task to be performed at a location during a time window. Activities carry status, duration, required skills, and links to work orders.

A business request for work, often originating in an external system, that is broken into one or more activities for field execution. Work orders carry customer, contract, and billing context above the activity level.

A configuration that defines the behavior of a category of activity, including duration rules, required skills, allowed statuses, and which fields appear. Activity types standardize how similar jobs are scheduled and executed.

The lifecycle state of an activity, such as pending, started, completed, or cancelled. Status transitions drive reporting, billing triggers, and outbound updates to integrated systems.

The time range promised to a customer during which an activity should occur, such as an arrival window. The routing engine must place the activity inside this window or flag it as at risk.

The expected time an activity takes from arrival to completion, used by routing to block calendar time. Duration can be fixed by activity type or calculated from configured formulas and field inputs.

Parts and materials an activity needs, declared on the activity or derived from its type. Inventory requirements affect whether a resource can complete the job and can trigger replenishment or transfer activities.

A dependency between two activities that constrains scheduling order, such as a prerequisite or a same-resource requirement. Links prevent routing from placing dependent work in an impossible sequence.

A set of resources who can share activities and assist each other during the day. Group membership lets a dispatcher move work between members without losing visibility of the team's total load.

The operational role that monitors routing results, resolves unscheduled activities, and manually reassigns work. Dispatchers use map and list views filtered by bucket, work zone, and status.

A configured rule that sends notifications to customers, resources, or systems when an activity reaches a defined state. Scenarios define trigger conditions, channels, and message templates.

The flow of data into Oracle Field Service from external systems such as CRM or ERP, typically creating or updating work orders and activities. It relies on defined message schemas and authentication.

The flow of data from Oracle Field Service to external systems, such as status changes, completion details, and inventory consumption. Outbound messages are queued and retried to protect delivery.

A programmatic interface for reading and writing Oracle Field Service data, used by integrations and custom applications. Access is controlled by credentials and permissions tied to the calling application.

The mechanism that verifies the identity of a user or integration before granting access. Oracle Field Service supports credential-based and token-based schemes, with permissions determining what each identity can do.

A configured role that bundles permissions and screen access for a class of users, such as dispatcher or field resource. User types are assigned to users and control what data and actions they can reach.

The set of settings that tailor Oracle Field Service behavior, covering activities, resources, routing, and integrations. Configuration is versioned and promoted between environments through migration tools.

A separate instance used to build and test configuration before it reaches production. Sandboxes let implementers validate routing, integrations, and permissions without affecting live operations.

An administrator-defined data field added to activities, resources, or other entities to capture business-specific information. Custom fields can be used in routing filters, message templates, and reports.

A condition applied during routing or in list views to include or exclude records based on field values. Filters narrow candidate resources or activities so the engine evaluates only relevant matches.

The ordered sequence of activities assigned to a resource for a period, including travel legs between stops. Routes are produced by routing and optimization and can be manually adjusted by dispatchers.

A message delivered to a customer, resource, or external endpoint in response to an event or schedule. Notifications are produced by message scenarios and can be sent by email, SMS, or integration call.

The process of loading existing master and transactional data, such as resources, customers, and open activities, into Oracle Field Service before go-live. It is usually performed through APIs or bulk import tools.