OFS accelerator helps to set up initial Utility specific layer of configurations required for the integration with NMS. The details provided here apply to Oracle Field Service 21C.

It includes an extract with OFS configuration data such as properties, user types and custom plug-in's. It is used in addition and in conjunction with OIC flows to provide a complete end-to-end setup for the integration. OIC flows required to enable this integration are released in MOS as Oracle Utilities Network Management System (NMS) Integration to Oracle Field Service (OFS).

FPRC accelerator helps to set up initial Utility specific layer of configurations required for the integration with WACS. The details provided here apply to Oracle Fusion Procurement Cloud 21A or higher.

It includes an extract with FPRC configuration which will be used in addition and in conjunction with OIC flows to provide a complete end-to-end setup for the integration. OIC flows required to enable this integration are released in MOS as Integrating Oracle Utilities Work and Asset Cloud Service Integration (WACS) to Oracle Fusion Procurement Cloud (FPRC).

OFSC accelerator helps to set up initial Utility specific layer of configurations required for the integration with OUWACS. The details provided here apply to Oracle Field Service Cloud 21A or higher.

It includes an extract with OFSC configuration data such as properties, Glossary, user types and custom plug-ins. It is used in addition and in conjunction with OIC flows to provide a complete end-to-end setup for the integration. OIC flows required to enable this integration are released in MOS as Integrating Oracle Utilities Work and Asset Cloud Service (OUWACS) with Oracle Field Service Cloud (OFSC).

HCM accelerator helps to set up initial Utility specific layer of configurations required for the integration with OUWACS. The details provided here apply to Oracle ERP HCM Cloud 20D or higher.

It includes HCM configuration data objects and extracts to be applied before using this solution. It is used in addition and in conjunction with OIC flows to provide a complete end-to-end setup for the integration. OIC flows required to enable this integration are released in MOS as Oracle ERP HCM Cloud Integration to Oracle Work and Asset Cloud Service.

ERP accelerator helps to set up initial Utility specific layer of configurations required for the integration with OUWACS. The details provided here apply to Oracle ERP Financial Cloud 20D or higher.

It includes an ERP configuration data to be applied before using this solution. It is used in addition and in conjunction with OIC flows to provide a complete end-to-end setup for the integration. OIC flows required to enable this integration are released in MOS as Oracle Utilities Work and Asset Cloud Service Integration to Oracle ERP Financial Cloud.

This accelerator provides an ability to load customer data from C2M/CCB into Eloqua. This data is used by Eloqua for segmentation in marketing campaigns.

Eloqua sends back to C2M/CCB marketing activities that are creating Customer Contacts.

OFSC accelerator helps to set up initial Utility specific layer of configurations required for the integration with OUCCS. The details provided here apply to Oracle Field Service Cloud 21A or higher.

It includes an extract with OFSC configuration data such as properties, custom plug-ins, and user type. It is used in addition and in conjunction with OIC flows to provide a complete end-to-end setup for the integration. OIC flows required to enable this integration are released in MOS as Integrating Oracle Utilities Customer Cloud Service (OUCCS) with Oracle Field Service Cloud (OFSC).

The same package is applicable to Oracle Utilities Customer To Meter (OUC2M).

OFSC accelerator helps to set up initial Utility specific layer of configurations required for the integration with CCB. The details provided here apply to Oracle Field Service Cloud 21C.

It includes an extract with OFSC configuration data such as properties, user types and custom plug-ins. It is used in addition and in conjunction with OIC flows to provide a complete end-to-end setup for the integration. OIC flows required to enable this integration are released in MOS as Integrating Oracle Utilities Customer Care and Billing (CCB) with Oracle Field Service Cloud (OFSC).

This package provides empty, generic and demo CSV files to use with the Online Loader to load Administrative and non-Administrative data for both the WAM and ODM applications. The package also includes an Online Loader Training Guide as well as an Excel spreadsheet detailing the data setup sequence and other relevant hints for a successful data load.

The Online Loader is supported starting with WAM/ODM v2.2.0.2.

This package provides the 11 User Groups, their associated Application Services and Access Modes that would make up the base of any security plan.

As per the Instructions: Please note that the package contains 2 CMA files:

1. CMA_21A_23000_User_Groups: use this CMA file if you are importing into a WACS 21A or WAM 2.3.0.0.0 instance.
2. CMA_21C_User_Groups: Use this CMA file if you are importing into a WACS 21C instance.

If you happen to be importing into a WACS 21B instance, the CMA_21A_23000_User_Groups file is also appropriate. The CMA_21C_User_Groups file has some new Application Services that were created in WACS 21C and will not successfully load into any instance other than a WACS 21C instance.

The package also includes information about the configuration and use of the User Groups as well as a Word document detailing the steps to follow for the CMA process.

This package contains the objects required to support Fleet Work Orders and their Activities as well as a new Extendable Lookup to store the VMRS Codes commonly used in Fleet Work Orders and a new search option which allows Users to search for Fleet Activities by VMRS Codes.

The package includes a Fields and Lookups Bundle, a Fleet Work Order Bundle and instructions on the loading order of the Bundles and configurations required after the Bundles are applied.

This package contains white paper and sample scripts to illustrate the data conversion process from V1 to V2.