Setting Up Oracle Utilities Meter Data Management

The D1-AddODMAlg and D1-ODMPreMcg business process analysis scripts aid in setting up Oracle Utilities Meter Data Management sync processing. Consequently, the setup effort by an implementation is greatly reduced.

These scripts insert Oracle Utilities Operational Device Management-specific algorithms to Sync Request business objects. They are intended to be executed only once prior to any customization(s) being made to any of the sync objects.

The details are as follows:

• D1-AddODMAlg - Inserts transformation algorithms specific to the Oracle Utilities Operational Device Management integration into the sync request business objects.

If your implementation needs to introduce additional transformation algorithms, insert them after running this script.

• D1-ODMPreMcg- Used to setup data in the following master configurations:

• Master Data Synchronization Configuration - Contains the foreign key reference information used by framework to validate and/or resolve foreign keys in the master data sync requests.

• Seeder Sync Request Master Configuration - Contains information needed by the sync request seeder business object to determine the actual business object to instantiate. The information is keyed to external system, maintenance object, and initial load indicator in the sync request.

To set up Oracle Utilities Meter Data Management for the integration, configure the admin data and system data tables, outbound messages, and catalog services.

The following sections provide details about how to configure these items:

• Configuring Admin Data Tables

• Configure System Data Tables

• Configuring Outbound Messages

• Managing Catalog Service

Note: Some configurations described may be required for general functionality and do not necessarily relate directly to the integration; however these are called out as particularly significant configuration items. The inclusion of such items does not mean that other general items that are not mentioned do not need to be configured.

For more information on configuring and working with Oracle Utilities Meter Data Management, refer to the Oracle Utilities Meter Data Management documentation.

Configuring Admin Data Tables

This section describes the unique setup issues specifically related to configuring the system for integration. For more information about configuring Oracle Utilities Meter Data Management, refer to the Oracle Utilities Meter Data Management User’s Guide.

To configure Admin Data Tables, define the following codes and types:

• Country

• Service Point Type

• Contact Type

• Device Type

• Master Configuration

Important: In the following sections, alphabetical menus are used to specify the navigation path. Alternatively, you can either navigate to the required entity using functional menus or search for a specific entity using the Search Menu.

Navigation using Alphabetical Menu

Navigation using Search Menu

Country

Create a country code in Oracle Utilities Meter Data Management.

The Main page is used to customize the fields and field descriptions that are displayed where addresses are used in the system. This ensures that all addresses conform to the customary address format and conventions of the particular country defined.

Country Code Details for Oracle Utilities Meter Data Management

Navigation	Guidelines	Corresponding DVM
Admin > C > Country	Create the Country codes	OUTL-BRT-ODM_MDM_Country

Service Point Type

Create the required Service Point Types. The codes defined here must exactly match values in the lookup indicated.

Service Point Type Code for Oracle Utilities Meter Data Management

Navigation	Guidelines	Corresponding DVM
Admin > S > Service Point Type	Create Service Point Types	OUTL-BRT-ODM_MDM_SPNodeType

Contact Type

Create the required Contact Types. The codes defined here must exactly match values in the lookup indicated.

Contact Type Code Details for Oracle Utilities Meter Data Management

Navigation	Guidelines	Corresponding DVM
Admin > C > Contact Type	Create Contact Types	OUTL-BRT-ODM_MDM_ContactType

Device Type

Create the required Device Types. The codes defined here must exactly match values in the lookup indicated.

Device Type Code Details for Oracle Utilities Meter Data Management

Navigation	Guidelines	Corresponding DVM
Admin > D > Device Type	Create Device Types	OUTL-BRT ODM_MDM_AssetDeviceType

Master Configuration

Two master configurations - Master Data Synchronization Configuration and Seeder Sync Request Master Configuration - have to be configured. A business process analysis script is provided to pre-populate these with the information necessary to support the base objects included in the sync. Execute W2-MDMPreMCf to accomplish this.

A third master configuration, Oracle Utilities Meter Data Management Integration Master Configuration, needs to be completed manually. The Oracle Utilities Operational Device Management URL, timeout threshold hours for outbound requests, and the maintenance object/Outbound Message Type combinations used by outbound requests are all defined here. The To Do Type to use for asset-location sync scenarios that require manual intervention is also defined here, as well as the time out number of hours used by the outbound sync.

Configure System Data Tables

To configure System Data Tables, the following are required:

• Business Objects

• Business Object Algorithms

• Maintenance Object

• Maintenance Object Algorithms

• Extendable Lookups

• Lookups

• Menus

• Batch Scheduling

Business Objects

This section describes unique setup issues specifically related to configuring your system for integration.

Business Objects Details

Business Object	Business Object Description
D1-OngoingSyncRequestDevice	Defines the behavior of an ongoing sync request. The schema elements define information required to maintain the device master data in Oracle Utilities Meter Data Management. As part of sync request processing, an acknowledgment message is sent to the external system (either positive or negative). The "Outbound Message Type" business object option contains a reference to the outbound message business object to use for this purpose. The base package includes business object D1-OngoingSyncReqAckMsg to be used on the outbound message type configuration. The error states in the ongoing sync requests contain automatic To Do creation and automatic retry. The parameters relevant to these processes (To Do Retry Frequency and To Do Maximum Retries) are captured as business object status options. If your implementation needs to introduce your own values, simply add a higher sequenced row for the option you intend to modify. The algorithms will automatically use these values. The Create To Do algorithm (D1-TDCREATE) has been delivered to use the base package supplied To Do Type D1-SYNIN for this process. If your implementation needs to use a different To Do Type, you will need to configure your own algorithm and supply the value in its parameters. The monitor process on the initial states of these business objects may be removed by the implementation if immediate processing of the sync requests as they are received is desired.
D1-ODMContactSyncRequest D1-ODMSPSyncRequest D1-InstallEventSyncRequest	These business objects define the behavior of an outbound sync request. The schema elements define the information needed by Oracle Utilities Operational Device Management to maintain contact, SP, and asset-node master data. The business object and data area necessary to build the sync snapshot are defined as business object options on the sync request business object. The business objects D1-ContactODMBORead, D1-InstallEventBORead, and D1-ServicePointODMBORead as well as DAs D1-ODMContactBasedSnapshot, D1-ODMSPSnapshot, and D1-InstallEventSnapshot are included in the base for use with these options. If your implementation needs to use your own snapshot business object or DA, simply add a higher sequenced row for the relevant option. The Post Service Script for Extract option allows your implementation to perform additional manipulation of the data during the building of the snapshot. The Create To Do algorithm (D1-SRCRETODO) has been delivered to use the base package supplied To Do Type F1-SYNRQ for this process. If your implementation needs to use a different To Do Type, you will need to configure your own algorithm and supply the value in its parameters.

Business Object

Business Object Description

D1-OngoingSyncRequestDevice

Defines the behavior of an ongoing sync request. The schema elements define information required to maintain the device master data in Oracle Utilities Meter Data Management.

As part of sync request processing, an acknowledgment message is sent to the external system (either positive or negative). The "Outbound Message Type" business object option contains a reference to the outbound message business object to use for this purpose. The base package includes business object D1-OngoingSyncReqAckMsg to be used on the outbound message type configuration.

The error states in the ongoing sync requests contain automatic To Do creation and automatic retry. The parameters relevant to these processes (To Do Retry Frequency and To Do Maximum Retries) are captured as business object status options. If your implementation needs to introduce your own values, simply add a higher sequenced row for the option you intend to modify. The algorithms will automatically use these values.

The Create To Do algorithm (D1-TDCREATE) has been delivered to use the base package supplied To Do Type D1-SYNIN for this process. If your implementation needs to use a different To Do Type, you will need to configure your own algorithm and supply the value in its parameters.

The monitor process on the initial states of these business objects may be removed by the implementation if immediate processing of the sync requests as they are received is desired.

D1-ODMContactSyncRequest

D1-ODMSPSyncRequest

D1-InstallEventSyncRequest

These business objects define the behavior of an outbound sync request. The schema elements define the information needed by Oracle Utilities Operational Device Management to maintain contact, SP, and asset-node master data.

The business object and data area necessary to build the sync snapshot are defined as business object options on the sync request business object. The business objects D1-ContactODMBORead, D1-InstallEventBORead, and D1-ServicePointODMBORead as well as DAs D1-ODMContactBasedSnapshot, D1-ODMSPSnapshot, and D1-InstallEventSnapshot are included in the base for use with these options. If your implementation needs to use your own snapshot business object or DA, simply add a higher sequenced row for the relevant option. The Post Service Script for Extract option allows your implementation to perform additional manipulation of the data during the building of the snapshot.

The Create To Do algorithm (D1-SRCRETODO) has been delivered to use the base package supplied To Do Type F1-SYNRQ for this process. If your implementation needs to use a different To Do Type, you will need to configure your own algorithm and supply the value in its parameters.

For more information about the sync request process, the business objects, maintenance objects, and other components used for this process, refer to the Data Synchronization section in the Oracle Utilities Framework User Guide.

Business Object Algorithms

Oracle Utilities Operational Device Management-specific algorithms need to be plugged in on the sync request business objects. A business process analysis script is provided to plug-in these algorithms on to the sync business objects. This business process analysis script should be executed prior to any further customizations done on the sync business objects. It should only be executed once. Run D1-AddODMAlg Insert Oracle Utilities Operational Device Management-specific algorithms to Sync Request business objects (MDF) to accomplish this.

Maintenance Object

Configure the Maintenance Object algorithm type.