Scenario 5: MWM + WAM/ODM v2.1.x
In this scenario, the integration product coordinates processing between:
• Oracle Utilities Mobile Workforce Management
• Oracle Utilities Work and Asset Management/Oracle Utilities Operational Device Management v2.1.x
You must complete the following steps in Oracle Utilities Work and Asset Management/Oracle Utilities Operational Device Management v2.1.x to configure the integration:.
1. Configure the admin data to support the integration:
• Service Area
• Asset Location Type
• Storage Location Type
• Manufacturer
• TimeZone
• Activity Type
• Service History Type
2. Configure Master Data.
3. Configure Extendable Lookups.
4. Configure message senders to pass messages with the integration layer.
Configure Administration Data
This section describes unique setup issues related to configuring your system for the integration.
Configure Service Area
The codes defined here must exactly match values in the DVM for Dispatch Group Code indicated.
• Navigation: Admin Menu > Service Area > Add
• Corresponding DVM: FS_Order_DispatchGroup
• Guideline: Create the Service Area required by your business.
Configure Asset Location Type (Service Point Type)
The codes defined here must exactly match values in the DVM for Service Point Type Code indicated.
• Navigation: Admin Menu > Asset Location Type > Add
• Corresponding DVM: FS_Order_ServicePointTypeCode
• Guideline: Create the Asset Location Type required by your business.
Configure Manufacturer
The codes defined here must exactly match values in the DVM for Manufacturer Type Code indicated.
• Navigation: Menu > Asset Management > Manufacturer > Add
• Corresponding DVM: FS_Order_ManufacturerCode
• Guideline: Create the Manufacturer Codes required by your business.
Configure Storage Location Type
This storage location type is required to be configured in Oracle Utilities Work and Asset Management to later specify the Storage Location that is mapped to edge application.
Note: Separate Stock Location Types need to be created for Stock Location and Vehicles in Oracle Utilities Work and Asset Management.
• Navigation: Admin Menu > Storage Location Type > Add
• Guideline: Create the Storage Location Type required by your business for storage location and for Vehicles
Configure Time Zone
The codes defined here must exactly match values in the DVM for Time Zone Code indicated.
• Navigation: Admin Menu > Time Zone > Add
• Corresponding DVM: FS_Order_TimeZone
• Guideline: Create the Time Zone required by your business.
Configure Activity Types
The codes defined here must exactly match values in the DVM for Order Type indicated. Refer to the section on FA Type for information on supported activity types..
Note: For the item install, item exchange activity types, Oracle Utilities Work and Asset Management does not force passing existing device details. This is because the recorded asset/device data in Oracle Utilities Work and Asset Management may or may not be accurate as it relates to what is in Oracle Utilities Mobile Workforce Management.
If a message that does not contain the badge number of the existing device is sent to Oracle Utilities Mobile Workforce Management to pass device details, the message will fail. This is caused because base package activity and assignment business objects being used for remove or exchange activity types have business rules that require the badge number of the existing device to be passed in.
In order for the integration to work properly end to end, it is important to pass in the existing asset information from WAM to MWM, otherwise MWM will respond with a negative Acknowledgment ("Badge Number is required") for such an activity.
• Navigation: Admin Menu > Activity Type > Add
• Corresponding DVM: FS_Order_TypeCode.
• Guideline: Create the activity types required by your business and populate the necessary information to define your set of activity types required for your business.
The activity types in this section are used to create activities to send distributed work to Oracle Utilities Mobile Workforce Management. After Oracle Utilities Mobile Workforce Management completes the work, they send activity completion detail message back to Oracle Utilities Work and Asset Management. The message contains information for new/existing item depending on what work was requested/done. It may also contain information about the device’s manufacturer/model and SP details. Completion event types on the activity types are used to process this information and update Oracle Utilities Work and Asset Management database with work completed in the field.
Notes About MWM Activity Completion Messages
• The activity completion message from Oracle Utilities Mobile Workforce Management will contain information for the item.
• Device Manufacturer and Device Model for new item will only be populated if the crew populates them in the field.
• Existing item details (manufacturer and model) will only be populated if different than what Oracle Utilities Work and Asset Management had sent to Oracle Utilities Mobile Workforce Management.
Note: You should configure each activity type with an outbound message type for each usage (Add, Update, Cancel) and external system as specified in the
Setting up the Field Work Process Integration Pack section.
Item Install Activity Type
This activity type is used for item installs. Oracle Utilities Work and Asset Management receives an Oracle Utilities Mobile Workforce Management activity completion message containing:
• New item details + reading
• Optional: Item manufacturer and model of the new item, only if the crew populates them
• Optional: Service Point Details if different from what Oracle Utilities Work and Asset Management sent Oracle Utilities Mobile Workforce Management
• Optional: Attachments of item could be sent from Oracle Utilities Mobile Workforce Management to Oracle Utilities Work and Asset Management
• Optional: Attachments of location could be sent from Oracle Utilities Mobile Workforce Management to Oracle Utilities Work and Asset Management. This would be processed only if asset attachment is not sent to Oracle Utilities Work and Asset Management
Note: Install always assumes there is no existing item otherwise it is an exchange. Crew would cancel the activity and request for an item exchange activity.
Main
Completion Event Types
Item Remove Activity Type
This activity type is used for item remove. Oracle Utilities Work and Asset Management receives Oracle Utilities Mobile Workforce Management activity completion message containing:
• Existing item details + reading before remove
• Optional: Updates to existing item manufacturer and model
• Optional: Service Point Details if different from what Oracle Utilities Work and Asset Management sent Oracle Utilities Mobile Workforce Management
• Optional: Attachments of item could be sent from Oracle Utilities Mobile Workforce Management to Oracle Utilities Work and Asset Management.
• Optional: Attachments of location could be sent from Oracle Utilities Mobile Workforce Management to Oracle Utilities Work and Asset Management. This would be processed only if asset attachment is not sent to Oracle Utilities Work and Asset Management.
Main
Completion Event Types
Item Exchange Activity Type
This activity type is used for item exchanges. An item exchange is like an item remove + item install. Oracle Utilities Work and Asset Management receives Oracle Utilities Mobile Workforce Management activity completion message containing:
• Existing item details + reading before remove
• Optional: Updates to existing item manufacturer and model
• New item details + reading
• Optional: Item manufacturer and model of the new item, only if the crew populates them
• Optional: Service Point Details if different from what Oracle Utilities Work and Asset Management sent Oracle Utilities Mobile Workforce Management.
• Optional: Attachments of item could be sent from Oracle Utilities Mobile Workforce Management to Oracle Utilities Work and Asset Management. The attachments for asset would be created in the following priority, priority increases as we go down:
• Existing Item/Meter
• New Item/Meter
• Optional: Attachments of location could be sent from Oracle Utilities Mobile Workforce Management to Oracle Utilities Work and Asset Management. This would be processed only if asset attachment is not sent to Oracle Utilities Work and Asset Management.
Main
Completion Event Types
Inspection Activity Type
This inspection activity type is used to send a questionnaire to Oracle Utilities Mobile Workforce Management and process questions/answers received back from Oracle Utilities Mobile Workforce Management.
Main
Completion Event Types
Service History Type
Your implementation may require that Oracle Utilities Work and Asset Management sends Questionnaires to Oracle Utilities Mobile Workforce Management. A questionnaire is a set of questions for the crew to fill out and optionally the crew may send attachments along with filled questionnaire in their completion information to Oracle Utilities Work and Asset Management. The question may be in a form of a check box, text input or radio buttons. Answering of questions is all optional. For example, questions may be about the asset, environment, where the work is being done, etc.
A questionnaire may be sent out alone or may be a part of the distributed work to Oracle Utilities Mobile Workforce Management. When an integration activity maintenance outbound message is created in an activity's sent state, it will be populated with questions and if applicable, possible answers to choose from (e.g. radio buttons). These questions/answers are taken from Questionnaire Service History Type configured on the activity type of the activity.
Configure a service history type with a set of questions and answers as specified below.
To send this questionnaire to Oracle Utilities Mobile Workforce Management in the Oracle Utilities Work and Asset Management integration Activity Maintenance Outbound Message, there are two recommended options:
Option 1 (preferred): Send Questionnaire Only
• Transition the activity to send state if not already automatically transitioned upon saving.
Option 2: Send Questionnaire as Part of Distributed Work
• Configure the service history type on any of the device activity types.
• Include a product owned create questionnaire completion event type on the activity type.
• Create an activity using the activity type.
• Transition the activity to send state.
Note: Option 2 requires additional setup in Oracle Utilities Mobile Workforce Management.
Oracle Utilities Mobile Workforce Management can receive a questionnaire as part of distributed work, but must be set up accordingly. In Oracle Utilities Mobile Workforce Management, questionnaires are designed as a separate set of data areas so that they can be included in other business objects. However, but not all customers that use the other business objects work with such questionnaires. Given this, the questionnaire is delivered on its own standalone activity business object. Your implementation has the option to extend base business objects and include this as needed.
When the activity is transitioned to the send state, a Fieldwork integration Activity Maintenance Outbound Message is created. The outbound message business object has a pre-processing script, populate questionnaire, to fill out the questionnaire group in the outbound message.
Main
Questions
Questions need to be set up in the system prior to adding them onto service history type. Create questions relevant to information needed/desired to be collected in the field. Questions can be in the form of:
• A question with check box answer
• A question with text input answer
• A question with multiple radio button answers
When adding questions onto service history type, each question can be marked as repeatable if desired.
Cost Center
This cost center is required to be configured in Oracle Utilities Work and Asset Management’s CCB Integration Master Configuration as a default cost center.
• Navigate to Admin Menu > Cost Center > Add.
• Create the Cost Center required by your business defaulting in the Item Service Point sync from Oracle Utilities Customer Care and Billing to Oracle Utilities Work and Asset Management.
Configure Master Data
Storage Location (Stock Location)
A storage location is a physical or logical location at which assets are stored while they are not installed at a service point. The Storage location should be created using the Storage Location types created using details specified in the Admin data setup above.
The codes defined here must exactly match values in the AIA configuration file for the Item and/or Meter Stock Location Codes indicated.
• Navigation: Menu > Location> Storage Location > Add
• DVM: FS_ItemStockLocationCode
• Guideline: Define storage location codes.
Vehicle (Completed By Crew)
When Oracle Utilities Mobile Workforce Management removes an item/meter/ERT from a SP, they can optionally populate stock location. (Stock Location is equivalent to Storage Location in Oracle Utilities Work and Asset Management.) Oracle Utilities Work and Asset Management uses the stock location to remove the asset to, but if it’s not populated, then completedByCrew is used instead. This field is always populated on Oracle Utilities Mobile Workforce Management side by the crew performing the work. The Crew is tied to the vehicle in Oracle Utilities Work and Asset Management via identifier.
The Storage location should be created using the Storage Location types created using details specified in the Admin data setup above.
• Navigation: Menu > Location> Storage Location > Add
• Corresponding DVMFF: FS_Order_Worker
• Guideline: Define storage location codes for vehicle and specify the Crew Contact
Configure Extendable Lookups
This section describes extendable lookups that can be configured for your implementation.
Note the term in parenthesis indicates the Oracle Utilities Work and Asset Management terminology where the first indicates the Oracle Utilities Mobile Workforce Management term.
Service Instructions (SP Instructions)
Service Instructions to be sent to other applications.
• Navigation: Admin Menu > Extendable Lookup > W2-ServicePointInstruction
• Corresponding DVM: CodeFS_Order_ServiceInstructionsCode
• Guideline: Define your service point instruction.
Service Warnings (SP Warnings)
Service Warnings to be sent to other applications.
• Navigation: Admin Menu > Extendable Lookup > W2-ServicePointWarning
• Corresponding DVM: CodeFS_Order_ServiceWarningsCode
• Guideline: Define your service point warning.
Configure Outbound Services
The following sections identify settings required to communicate using outbound services.
Create the Activity Maintenance Outbound Message Type
This outbound message type will be used to send the activity maintenance message. Add details for distributed work to the integration. Create a new Outbound Message Type which maps to the appropriate business object.
1. Navigate to Admin, Outbound Message Type, and select Add.
2. Enter a unique Outbound Message Type and Description.
Example: CM- ACTMAINTADD
3. Populate values as follows:
• Business Object = W1-FldwrkPIPActMaintOutMsg (Fieldwork PIP Act Maintenance Outbound Msg)
• Priority = 50. You can set this to any other value as needed.
Create the Activity Update Outbound Message Type
Used to Send Activity Maintenance Message - Update Details for Distributed Work to the integration.
Create a new outbound message type which maps to the appropriate business object.:
1. Navigate to Admin, Outbound Message Type, and select Add.
2. Enter a unique Outbound Message Type and Description.
Example: CM-ACTMAINTUPD
3. Populate values as follows:
• Business Object = W1-FldwrkPIPActMaintOutMsg
Fieldwork PIP Act Maintenance Outbound Msg
• Priority = 50. You can set this to any other value.
Create the Activity Completion Outbound Message Type
Used to Send Activity Maintenance Message - Completion Details for Distributed Work to the integration.
Create a new outbound message type which maps to the appropriate business object.:
1. Navigate to Admin, Outbound Message Type, and select Add.
2. Enter a unique Outbound Message Type and Description.
Example: CM-ACTMAINTCOM
3. Populate values as follows:
• Business Object = W1-FldwrkPIPActMaintOutMsg
Fieldwork PIP Act Maintenance Outbound Msg
• Priority = 50. You can set this to any other value.
Create the Send Activity Final Details for Distributed Work Outbound Message Type
Create a new outbound message type which maps to the appropriate business object. This is used to send the cancellation of the activity for distributed work to the integration layer.
1. Navigate to Admin, Outbound Message Type, and select Add.
2. Enter a unique Outbound Message Type and Description.
Example: CM- ACTFINAL
3. Populate values as follows:
• Business Object = W1-FldwrkPIPActFinalOutMsg (Fieldwork PIP Act Final Outbound Msg)
• Priority = You can set this to any other value.
Create the SP Sync Acknowledgment Outbound Message Type
Create a new outbound message type which maps to the appropriate business object. This is used to send the response of SP Sync to the integration layer.
1. Navigate to Admin, Outbound Message Type, and select Add.
2. Enter a unique Outbound Message Type and Description.
3. Populate values as follows:
• Business Object = W1-OutboundAcknowledgeMessage (Outbound Acknowledgment Message)
• Priority = You can set this to any other value.
Create an HTTP Sender for Activity Maintenance –Create/Update Message
Create a new Message sender which points to the Oracle Utilities Work and Asset Management Create/Update Requester ABCS for the Create/Update Field Order integration point.
1. Navigate to Admin, Message Sender, Add.
2. Enter a unique Message Sender and Description.
3. Populate values as follows:
• Invocation Type = Real-time
• Message Class = RTHTTPSNDR.
This is the class for real-time sender to route messages using HTTP.MSG Encoding = UTF-8 message encoding.
4. Select the Active check box.
5. Select the Context tab and set values for the following context types:
• Character Encoding – UTF-8
• HTTP Login User – User ID for the url to be accessed
• HTTP Login Password – Password for the url to be accessed
• HTTP Header – SOAPAction: "ProcessWAMWorkOrder"
• HTTP Method (POST/GET) – POST
• HTTP Transport Method – SendReceive
• HTTP Timeout: 60 (in seconds)
• HTTP URL 1 – Set the URL to be accessed. If the URL value does not fit, use the additional HTTP URL types to set the complete URL.
This should point to the Order Create Update Requester ABCS.
Example: http://[soa server: port]/services/default/ProcessWorkOrderCreateUpdateOUWAMUtilitiesReqABCSImplV2/ProcessWorkOrderCreateUpdateOUWAMUtilitiesReqABCSImplV2
Create an HTTP Sender for Activity Final Message
Create a new Message sender which points to the Oracle Utilities Work and Asset Management Cancel Requester ABCS for the Cancel/Complete Field Order integration point.
1. Navigate to Admin, Message Sender, Add.
2. Enter a unique Message Sender and Description.
3. Populate values as follows:
• Invocation Type = Real-time
• Message Class = RTHTTPSNDR
This is the class for real-time sender to route messages using HTTP.MSG Encoding = UTF-8 message encoding.
4. Select the Active check box.
5. Select the Context tab and set values for the following context types:
• Character Encoding: UTF-8
• HTTP Login User: User ID for the url to be accessed
• HTTP Login Password: Password for the url to be accessed
• HTTP Header: SOAPAction: "W1-FldwrkPIPActFinalOutMsg"
• HTTP Method (POST/GET): POST
• HTTP Transport Method: SendReceive
• HTTP Timeout: 60 (in seconds)
• HTTP URL 1: Set the URL to be accessed. If the URL value does not fit, use the additional HTTP URL types to set the complete URL.
This should point to the Order Cancel Requester ABCS.
Example: http://[soa-server: port]/services/default/ProcessWorkOrderCancelCompleteOUWAMUtilitiesReqABCSImplV2/ProcessWorkOrderCancelCompleteOUWAMUtilitiesReqABCSImplV2
Create an External System
Create a new External System for the integration layer.
1. Navigate to Admin, External System, Add.
2. Enter a unique External System and Description.
3. Set Our Name in Their System to WAM.
4. Add the four outbound message types created above.
• Activity Maintenance Message: Add Outbound Message Type (created above)
• Processing method: Real-time
• Message Sender: new Message Sender for Activity Maintenance Message created above
• Date/Time Format: XSD
• Message XSL: W1-AddSOAPEnvMessage.xsl
• Response XSL: W1-FldwrkPIPActResponse.xsl
• Activity Maintenance Message: Update Outbound Message Type (created above)
• Processing method: Real-time
• Message Sender: new Message Sender for Activity Maintenance Message created above
• Date/Time Format: XSD
• Message XSL: W1-AddSOAPEnvMessage.xsl
• Response XSL: W1-FldwrkPIPActResponse.xsl
• Activity Final Message - Outbound Message Type (created above)
• Processing method: Real-time
• Message Sender: new Message Sender for Activity Final Message (created above)
• Date/Time Format: XSD
• Message XSL: W1-AddSOAPEnvMessage.xsl
• Response XSL: W1-FldwrkPIPActResponse.xsl