1. Using Routing
  2. Route Maintenance Work Order Operations Using Routing Plans

Route Maintenance Work Order Operations Using Routing Plans

Oracle Fusion Field Service can schedule and assign Maintenance Work Order Operations directly through Bulk Routing plans.

When configured, routing evaluates Maintenance Work Order Operations from Maintenance Cloud and creates Oracle Field Service activities for operations that satisfy routing requirements and can be successfully scheduled.

After activity creation, the activities are managed as standard Oracle Field Service activities.

Before you begin

Ensure that the OIC Adapter is disabled or configured so that it does not automatically create activities from Maintenance Work Order Operations.

Configure Maintenance Work Order Routing

  1. Create or modify a Bulk Routing plan.
  2. Open the activity filter configuration.
  3. Open Update activities assignment rule parameters.
  4. Select Maintenance Work Order Assignment.
  5. Select an Activity Type for Maintenance Work Order Assignment.
  6. Configure routing filters as required.
  7. Save the routing plan.
    Note: For environments using Legacy assignment rules, Activity Type for Maintenance Work Order Assignment is available only for Non-scheduled activities in the routing bucket that should be scheduled and assigned.

Routing Process

When the routing plan runs:
  1. Maintenance Work Order Operations are evaluated within the routing plan period.
  2. Routing applies internal eligibility checks.
  3. Routing applies customer-configured filters.
  4. Eligible operations are submitted to the routing engine.
  5. If routing successfully schedules an operation:
    • An Oracle Field Service activity is created.
    • The activity is assigned to a field resource.
    • The resource route is updated.

Internal Eligibility Requirements

A Maintenance Work Order Operation is eligible for routing only when:
  • The Work Order system status is Released.
  • The Work Order planned start date is before or within the routing plan period.
  • Assignment or reassignment is allowed.
  • The operation is a count point operation.
  • The Work Order is a single-asset Work Order.
  • An activity has not been created previously, or the previous activity was deleted or canceled.
Additional behavior:
  • Optional operations are excluded from routing.
  • Auto transact operations are not assigned. When they occur between two count point operations, they are converted into route gaps.

Configure Routing Filters

Routing filters use standard routing filter functionality.

You can configure filters using supported:
  • Maintenance Work Order fields.
  • Maintenance Work Order Operation fields.
  • Asset fields
  • Descriptive Flexfields

Only operations that satisfy all configured filters are considered for routing.

Activity Type Behavior

The selected Activity Type for Maintenance Work Order Assignment determines how the created activity behaves.

The activity type controls:
  • Travel calculation
  • Segmentation behavior
  • Duration calculation

Work Skills and Work Zones

Maintenance Work Order Operations use standard routing compatibility logic. Work Skills and Work Zones are derived according to the customer configuration and supported Maintenance Work Order and Operation fields.

Routing assignments are based on:
  • Work Skills
  • Work Zones
  • Routing filters
  • Resource compatibility

Maintenance Resource information from Maintenance Cloud is not used during routing.

Duration Calculation

Duration is calculated using the following sequence:
  1. Duration Statistics, if enabled for the Activity Type.
  2. Required Usage values from Maintenance Work Order Operation resources.
  3. Default Activity Type duration.

If multiple resources are defined for the operation, required usage values are combined according to routing duration calculations.

If no duration information is available, the default Activity Type duration is used.

Segmentable Operations

A Maintenance Work Order Operation is segmentable only when segmentation is enabled for the selected Activity Type.

Standard segmentable activity rules apply.

All segments created for the same Maintenance Work Order Operation are assigned to the same field resource.

Travel Calculation

Travel time is calculated according to standard Oracle Fusion Field Service routing rules.

For Maintenance Work Order Operations, travel calculations use the asset address.

SLA Behavior

Maintenance Work Order planned start date is used as the SLA start.

If a forecast date exists for a maintenance program Work Order, the forecast date is used as the SLA end.

Routing applies standard SLA policies according to the routing plan configuration.

Operation Sequencing

Activities created from Maintenance Work Order Operations follow Maintenance Work Order operation sequence numbers. The resequencing flag is not considered.

Activity Recreation

One activity is created for each routed Maintenance Work Order Operation.

If the activity is later canceled or deleted while the operation remains active, the operation can be selected again during future routing runs.

To prevent recreation, cancel the operation in Maintenance Cloud.

Limitations

  • Supported only for Bulk Routing plans.
  • Not supported for Continuous Improvement routing plans.
  • Not supported for Immediate Routing plans.
  • Not supported for Urgent Routing plans.
  • One Oracle Fusion Field Service activity is created for each Maintenance Work Order Operation.
  • Maintenance Resource requirements are not used during routing.