Meter Data Migration
This section outlines the steps for migrating customer data to an Oracle Utilities Meter Solution Cloud Service implementation that includes Meter Data Management, and Operational Device Management functionality.
Legacy Meter Data Management Upgrading to Oracle Utilities Meter Solution Cloud Service
In this scenario a new customer using a legacy MDM application is upgrading to Oracle Utilities Meter Solution Cloud Service. The steps outlined below apply to Master data only.
Step
Description
Remarks
1
Transform legacy contacts, service points, and usage subscriptions to MDM contacts, service points, and usage subscriptions.
This step is performed outside of the cloud service.
2
Transform legacy devices, device configurations, measuring components to MDM devices, device configurations, and measuring components.
This step is performed outside of the cloud service.
3
Transform legacy install events to MDM install events.
This step is performed outside of the cloud service.
4
Extract master data files based on the MDM master entities (contacts, service points, usage subscriptions, device, device configuration, measuring components and install events)
 
5
Upload master data files into Oracle Cloud Object Storage
 
6
Run the SQL Loader batch process to load data from the master data files into the staging schema objects.
 
7
Generate Keys, perform Validations, and insert data into the production schema.
 
8
Perform validation in the production schema
 
9
Convert legacy meters to ODM assets.
The following steps only apply if ODM functionality is included.
10
Bind the MDM devices to ODM assets.
11
Bind the ODM assets to MDM devices.
12
Synchronize MDM service points to ODM service points.
 
13
Synchronize MDM install events to ODM asset dispositions.
 
Meter Data Management Upgrading to Oracle Utilities Meter Solution Cloud Service
In this scenario an existing customer using the MDM application is upgrading to Oracle Utilities Meter Solution Cloud Service. The steps outlined below apply to Master data only.
Step
Description
Remarks
1
Export MDM database to a single-instance database.
This step is performed outside of the cloud service.
2
Perform database upgrade to match your cloud service supported version.
This step is performed outside of the cloud service.
3
Extract master data files based on the MDM master entities (contacts, service points, usage subscriptions, device, device configuration, measuring components and install events).
 
4
Upload master data files into Oracle Cloud Object Storage
 
5
Run the SQL Loader batch process to load data from the master data files into the production schema objects.
 
6
Perform validation in the production schema
 
7
Convert MDM meters to ODM assets.
The following steps only apply if ODM functionality is included.
8
Create MDM device identifiers from ODM asset identifiers.
 
9
Synchronize MDM service point to ODM service point.
 
10
Synchronize MDM install event to ODM asset disposition.
 
Integrated Meter Data Management and Operational Device Management Upgrading to Oracle Utilities Meter Solution Cloud Service
In this scenario an existing customer using integrated MDM and ODM applications is upgrading to Oracle Utilities Meter Solution Cloud Service. The steps outlined below apply to Master data only.
Step
Description
Remarks
1
Export MDM database to a single-instance database.
This step is performed outside of the cloud service.
2
Perform database upgrade to match your cloud service supported version.
This step is performed outside of the cloud service.
3
Export ODM database to a single-instance database.
This step is performed outside of the cloud service.
4
Perform database upgrade to match your cloud service supported version.
This step is performed outside of the cloud service.
5
Extract master data files based on the MDM master entities (contacts, service points, usage subscriptions, device, device configuration, measuring components and install events).
 
6
Extract master data files based on the ODM master entities (Asset, Asset Node)
 
7
Upload master data files for MDM and ODM into Oracle Cloud Object Storage
 
8
Run the SQL Loader batch process to load data from the master data files for MDM and ODM into the production schema objects.
 
9
Perform validation in the production schema
 
Meter Conversion
The table below shows the logical sequence in running the meter conversion jobs implementing the framework conversion tools. This outline assumes that the legacy data has been loaded into the staging tables
 
Contact
Device
Device Configuration
Measuring Component
Service Point
Usage Subscription
Install Event
Insertion
Insert D1_ CONTACT
(D1CNT00I)
Insert D1_ DVC
(D1DVC00I)
Insert D1_ DVC_CFG
(D1DC000I)
Insert D1_ MEASR_ COMP
(D1MC000I)
Insert D1_SP (D1SP000I)
Insert D1_US (D1US000I)
Insert D1_ INSTALL_EVT
(D1IE000I)
Key Generation
Generate Keys for D1_ CONTACT
(D1CNT00K)
Generate Keys for D1_DVC (D1DVC00K)
 
Generate Keys for D1_DVC_ CFG
(D1DC000K)
Generate Keys for D1_ MEASR_ COMP
(D1MC000K)
Generate Keys for D1_SP (D1SP000K)
Generate Keys for D1_US (D1US000K)
Generate Keys for D1_ INSTALL_EVT
(D1IE000K)
Legacy Data Validation
Validate D1-CONTACT
(D1CNT00V)
Validate D1-DEVICE
(D1DVC00V)
Validate D1-DVCCONFIG
(D1DC000V)
Validate D1-MEASRCOMP
(D1MC000V)
Validate D1-SP
(D1SP000V)
Validate D1-US
(D1US000V)
Validate D1-INSTLEVT
(D1IE000V)
Production Data
Validation
Validate D1-CONTACT
(D1CNT00V)
 
Validate D1-DEVICE
(D1DVC00V)
Validate D1-DVCCONFIG
(D1DC000V)
Validate D1-MEASRCOMP
(D1MC000V)
Validate D1-SP
(D1SP000V)
Validate D1-US
(D1US000V)
Validate D1-INSTLEVT
(D1IE000V)
XML Resolution
Resolve XML for D1-CONTACT
(D1CNT00R)
Resolve XML for D1-DEVICE
(D1DVC00R)
Resolve XML for D1-DVCCONFIG
(D1DC000R)
Resolve XML for D1-MEASRCOMP
(D1MC000R)
Resolve XML for D1-SP
(D1SP000R)
Resolve XML for D1-US
(D1US000R)
Resolve XML for D1-INSTLEVT
(D1IE000R)
 
Insert D1_CONTACT_IDENTIFIER
(D1CNTIDI)
Insert D1_DVC_IDENTIFIER
(D1DVCIDI)
Insert D1_DVC_CFG_CHAR
(D1DCCHRI)
Insert D1_MEASR_COMP_IDENTIFIER
(D1MCIDTI)
Insert D1_SP_IDENTIFIER
(D1SPIDTI)
Insert D1_US_IDENTIFIER
(D1USIDTI)
Insert D1_INSTALL_EVT_CHAR
(D1IECHRI)
 
Insert D1_ CONTACT_CHAR
(D1CNTCHI)
Insert D1_ DVC_CHAR
(D1DVCCHI)
 
Insert D1_ MEASR_COMP_CHAR
(D1MCCHRI)
Insert D1_SP_ CHAR
(D1SPCHRI)
 
Insert D1_US_ CHAR
(D1USCHRI)
 
 
 
Insert D1_ CONTACT_NAME
(D1CNTNMI)
 
 
Insert D1_ MEASR_COMP_REL
(D1MCRELI)
Insert D1_SP_ CONTACT
(D1SPCNTI)
Insert D1_US_ CONTACT
(D1USCNTI)
 
 
Insert D1_ CONTACT_ PHONE
(D1CNTPHI)
 
 
 
Insert D1_SP_ EQPMNT
(D1SPEQPI)
Insert D1_US_ SP
(D1USSP0I)
 
 
 
 
 
 
 
Insert D1_US_ SP_CHAR
(D1USSPCI)
 
Binding Meter Data Management Device IDs and Operational Device Management Asset IDs
This section describes the batch jobs used to populate the device identifier and asset identifier tables to bind device and asset IDs.
Device and Asset are Loaded with Converted Data
This section applies to data migration scenarios where both device and asset tables are loaded with legacy data from either a CIS application or existing CC&B application upgrading to Oracle Utilities Customer To Meter.
The following batch jobs must be run to populate the both Device Identifier and Asset Identifier tables to bind both converted device and asset IDs.
Batch Control
Description
Remarks
X1-LIDAD
Populate Asset Identifier with Device from Legacy Device
 
X1-LIDDA
Populate Device Identifier with Asset from Legacy Device
 
Asset Loaded with Converted Data
This section applies to the following data migration scenario:
• Existing separate instances of CC&B and MDM applications upgrading to Oracle Utilities Customer Cloud Service
• Existing MDM application upgrading to Oracle Utilities Meter Solution Cloud Service
The following batch job must be run to populate the Device Identifier table with an entry that binds the device ID with the converted asset ID.
Batch Control
Description
Remarks
X1-IDATD
Populate Device Identifier from Asset
 
Asset Conversion
Conversion Sequence
 
Node
Asset
Legacy Data Validation
Validate W1-NODE
(W1NOD00V)
Entity Validation for W1-ASSET
(W1AST00V)
Key Generation
Generate Keys for W1_NODE
(W1NOD00K)
Generate Keys for W1_ASSET
(W1AST00K)
XML Resolution
Resolve XML for W1-NODE
(W1NOD00R)
Resolve XML for W1_ASSET
(W1AST00R)
Insertion
Insert W1_NODE
(W1NOD00I)
Insert W1_ASSET
(W1AST00I)
 
Insert W1_NODE_CHAR
(W1NODCHI)
Insert W1_ASSET_IDENTIFIER
(W1ASTIDI)
 
Insert W1_NODE_IDENTIFIER
(W1NODIDI)
Insert W1_ASSET_NODE
(W1ASTNDI)
 
 
Insert W1_ASSET_CHAR
(W1ASTCHI)
Production Data Validation
Validate W1-NODE
(W1NOD00V)
Entity Validation for W1-ASSET
(W1AST00V)