Choosing a Configuration Scenario for your Business

This integration supports several business models. The configuration of the product and its integration points is slightly different for each business model. This section is intended to help you decide which business model is likely to work best for your organization and which technical configuration is best suited to your chosen business model.

Every configuration scenario uses the integration layer to manage business processes and the flow of data between the applications.

Step by step configuration for each scenario is described in following sections.

Note: Some items are required for the general configuration of the participating application, but are not specifically required for the integration. You may already have these items configured if you use the application separately from the integration. Set these items according to the needs of your business and then populate the corresponding DVM accordingly.

Scenario 1: CC&B + MWM + WAM v1.9.1.x

Scenario 1: Integration + 3 edge applications are used to automate order to completion and billing.

• WAM v1.9.1.x Service Requests

• CC&B Field Activities

• MWM Activities

Application Product	Managed Functions	Notes
Oracle Utilities Customer Care and Billing	Field activities are created or updated by customer request, customer service representative action, automated process within the application, or from receiving integrated orders originated by other applications. These orders are sent to, or received from, the integration product as required by the business process.	Also configure customer and asset data synchronization - send.
Oracle Utilities Work and Asset Management v1.9.1.x	Service requests are created, updated, and in some cases completed. These orders are sent to, or received from, the integration product as required by the business process.	Also configure customer and asset data synchronization - receive.
Oracle Utilities Work and Asset Management v2.1.x	Not used.
Oracle Utilities Mobile Workforce Management	Activities originating from other applications are updated and completed. Pickup orders, related to other orders, are created. These orders are sent to, or received from, the integration product as required by the business process.
Implementation Guide	Order information and actions are received from the requester application. The orders are routed to the provider application(s) involved in the business process, based on the type of order and the action required. Information is enriched and transformed as needed by the participating applications. Error information is logged and communicated.

Scenario 2: CC&B + MWM

Scenario 2: Integration + 2 edge applications are used to automate order to completion.

• CC&B Field Activities

• MWM Activities

Application Product	Managed Functions
Oracle Utilities Customer Care and Billing	Field activities are created or updated by customer request, customer service representative action, automated process within the application, or from receiving integrated orders originated by other applications. These orders are sent to, or received from, the integration product as required by the business process.
Oracle Utilities Mobile Workforce Management	Activities originating from other applications are updated and completed. ‘Pickup’ orders, related to other orders, are created. These orders are sent to, or received from, the integration product as required by the business process.
Oracle Utilities Work and Asset Management v1.9.1.x	Not used.
Oracle Utilities Work and Asset Management v2.1.x	Not used.
Implementation Guide	Order information and actions are received from the requester application. The orders are routed to the provider application(s) involved in the business process, based on the type of order and the action required. Information is enriched and transformed as needed by the participating applications. Error information is logged and communicated.

Scenario 3: MWM + WAM v1.9.1.x

Scenario 3: Integration + 2 edge applications are used to automate order to completion.

• MWM Activities

• WAMv1.9.1.x Service Requests

Application Product	Managed Functions
Oracle Utilities Customer Care and Billing	Not used.
Oracle Utilities Mobile Workforce Management	Activities originating from other applications are updated and completed. Pickup activities, related to other activities, are created. These orders are sent to, or received from, the integration product as required by the business process.
Oracle Utilities Work and Asset Management v1.9.1.x	Service requests are created, updated, and in some cases completed. These orders are sent to, or received from, the integration product as required by the business process.
Oracle Utilities Work and Asset Management v2.1.x	Not used.
Implementation Guide	Order information and actions are received from the requester application. The orders are routed to the provider application(s) involved in the business process, based on the type of order and the action required. Information is enriched and transformed as needed by the participating applications. Error information is logged and communicated.

Scenario 4: CC&B + WAM v1.9.1.x

Scenario 4: Integration + 2 edge applications are used to automate order to completion and billing:

• CC&B Field Activities

• WAM v1.9.1.x Service Requests

Application Product	Managed Functions	Notes
Oracle Utilities Customer Care and Billing	Field activities are created or updated by customer request, customer service representative action, automated process within the application, or from receiving integrated orders originated by other applications. These orders are sent to, or received from, the integration product as required by the business process.	Also configure customer and asset data synchronization - send.
Oracle Utilities Mobile Workforce Management	Not used.
Oracle Utilities Work and Asset Management v1.9.1.x	Service requests are created, updated, and in some cases completed. These orders are sent to, or received from, the integration product as required by the business process.	Also configure customer and asset data synchronization - receive.
Oracle Utilities Work and Asset Management v2.1.x	Not used.
Implementation Guide	Order information and actions are received from the requester application. The orders are routed to the provider application(s) involved in the business process, based on the type of order and the action required. Information is enriched and transformed as needed by the participating applications. Error information is logged and communicated.

Scenario 5:MWM + WAM/ODM v2.1.x

Scenario 5: Integration + 2 edge applications are used to automate order to completion.

• MWM Activities

• WAM/ODM v2.1.x Activities

Application Product	Managed Functions
Oracle Utilities Customer Care and Billing	Not used.
Oracle Utilities Mobile Workforce Management	Activities originating from other applications are updated and completed. Pickup activities related to other Activities, are created. These orders are sent to, or received from, the integration product as required by the business process.
Oracle Utilities Work and Asset Management v1.9.1.x	Not used.
Oracle Utilities Work and Asset Management v2.1.x	Activities are created, updated, and in some cases completed for distributed work. These activities for distributed work are sent to, or received from, the integration product as required by the business process.
Implementation Guide	Order information and actions are received from the requester application. The orders are routed to the provider application(s) involved in the business process, based on the type of order and the action required. Information is enriched and transformed as needed by the participating applications. Error information is logged and communicated.

Scenario 6:CC&B + WAM/ODM v2.1.x

Scenario 6: Integration + 2 edge applications are used to automate order to completion.

• CC&B Activities

• WAM/ODM v2.1.x Activities

Application Product	Managed Functions	Notes
Oracle Utilities Customer Care and Billing	Field activities are created or updated by customer request, customer service representative action, automated process within the application, or from receiving integrated orders originated by other applications. These orders are sent to, or received from, the integration product as required by the business process.	Sp Synchronization available.
Oracle Utilities Mobile Workforce Management	Not used.
Oracle Utilities Work and Asset Management v1.9.1.x	Not used.
Oracle Utilities Work and Asset Management v2.1.x	Activities are created, updated, and in some cases completed for distributed work. These activities for distributed work are sent to, or received from, the integration product as required by the business process.
Implementation Guide	Order information and actions are received from the requester application. The orders are routed to the provider application(s) involved in the business process, based on the type of order and the action required. Information is enriched and transformed as needed by the participating applications. Error information is logged and communicated.

Scenario 7:CC&B + MWM + WAM/ODM v2.1.x

Scenario 7: Integration + 3 edge applications are used to automate order to completion.

• CC&B Activities

• MWM Activities

• WAM/ODM v2.1.x Activities

Application Product	Managed Functions	Notes
Oracle Utilities Customer Care and Billing	Field activities are created or updated by customer request, customer service representative action, automated process within the application, or from receiving integrated orders originated by other applications. These orders are sent to, or received from, the integration product as required by the business process.	Sp Synchronization available.
Oracle Utilities Mobile Workforce Management	Activities originating from other applications are updated and completed. Pickup activities related to other Activities, are created. These orders are sent to, or received from, the integration product as required by the business process.
Oracle Utilities Work and Asset Management v1.9.1.x	Not used.
Oracle Utilities Work and Asset Management v2.1.x	Activities are created, updated, and in some cases completed for distributed work. These activities for distributed work are sent to, or received from, the integration product as required by the business process.
Implementation Guide	Order information and actions are received from the requester application. The orders are routed to the provider application(s) involved in the business process, based on the type of order and the action required. Information is enriched and transformed as needed by the participating applications. Error information is logged and communicated.