1. Field Service Integration to Oracle Real-Time Scheduler Implementation Guide
  2. Data Flows That This Integration Supports

Data Flows That This Integration Supports

The following illustrates data flows that this integration supports.

Data Flows That This Integration Supports: This image is described in the surrounding text.

Explanation of Callouts

This integration supports the following data flows:

  1. Service region data transfer. Transfers employees and activities associated with a service region from Siebel CRM to Oracle Real-Time Scheduler (ORS). If you currently use Siebel Scheduler, then you can use Service Region Data Transfer flow to do the following:

    • Perform a phased migration of service regions from the Siebel Scheduler to Oracle Real-Time Scheduler.

    • Migrate new service regions from Siebel CRM to Oracle Real-Time Scheduler.

  2. Service region rollback. Inactivates all crews and cancels activities for the chosen service region in Oracle Real-Time Scheduler. Siebel Scheduler then schedules activities for this service region.

    Siebel Scheduler refers to the existing Scheduling module in Siebel CRM that uses the iLog engine. For more information, see Siebel Field Service Guide.

  3. POU, shift, break, and activity synchronization. Synchronizes activity, shift, break, and POU data from Oracle Real-Time Scheduler to Siebel CRM.

  4. Multiple address geocoding. Retrieves geocodes for multiple Siebel addresses and writes geocodes directly back to the Siebel database.

In this integration, a service region is a defined grouping of service engineers and the activities that they perform. For more information, see Siebel Field Service Guide.

A service region data transfer is a process that transfers employee and activity data for a service region from Siebel CRM to Oracle Real-Time Scheduler. This capability provides a way for the Oracle Real-Time Scheduler engine to schedule the service region instead of the Siebel Scheduler.