Configuring Administrative Tables
This section describes unique setup issues specifically related to configuring your system for the integration.
Characteristic Types
The following characteristic types must be defined to facilitate the integration. For Oracle Utilities Customer Cloud Service and Oracle Utilities Meter Data Management (separate instance) implementations, the Critical Customer characteristic type is defined in Oracle Utilities Meter Data Management. The remaining characteristic types are defined in Oracle Utilities Customer Care and Billing.
 
Characteristic Type
Guideline
Characteristic Entity Collection
Corresponding DVM
Critical Customer
• Service Point characteristic used to define the critical customer for the service point.
• Pre-defined characteristic type.
• The critical customer pre-defined values listed here must be defined in the NMS Sync Integration master configuration, under the Critical Customer Types Characteristics Mapping section.
Include Service Point.
 
Location City
• Characteristic used to identify the location city for an outage without a premises.
• Adhoc characteristic type.
Include Service Task.
N/A
Location State
• Characteristic used to identify the location state for an outage without a premises.
• Adhoc characteristic type.
Include Service Task.
N/A
Location 1
• Characteristic used to identify a location used for an outage without a premises. (The location would be either a street name for location type street segment or intersection street1 for location type street intersection).
• Adhoc characteristic type.
Include Service Task.
N/A
Location 2
• Characteristic used to identify a location (intersection street2) used to for an outage without a premises if the location type is a street intersection.
• Adhoc characteristic type.
Include Service Task.
N/A
Block Number
• Characteristic used to identify a block number used for an outage without a premises if the location type is a street segment.
• Adhoc characteristic type.
• The Block Number adhoc value must be numeric.
Include Service Task.
N/A
Contact Name
• Characteristic used to identify a contact name used for an outage without a premises.
• Adhoc characteristic type.
Include Service Task.
N/A
Contact Number
• Characteristic used to identify a contact number used for an outage without a premise.
• Adhoc characteristic type.
Include Service Task.
N/A
Call Identifier
• Characteristic used to identify a call identifier used for an outage without a premises.
• Adhoc characteristic type.
Include Service Task.
N/A
Outage Codes 1 - N
• These characteristics are used to describe the outage problem.
• Create at least one and up to N pre-defined characteristic type. N being the number of outage codes needed by the implementation.
• For each characteristic type, define its list of valid values.
Include Service Task.
N/A
Feature Configuration
To create a new feature configuration, complete the following:
Schema Constants
To create a new feature configuration with Schema Constants:
1. Navigate to Admin > General > Feature Configuration.
2. Create new feature configuration with Schema Constants as the Feature Type or select a feature configuration with Schema Constants as the Feature Type if one already exists.
3. Enter the required option types and necessary values.
Option
Notes
Home Phone Type
The user defined home phone number type code. The Option Value must be set as a valid Phone Number Type defined in the Phone Type table.
Business Phone Type
The user defined business phone number type code. The Option Value must be set as a valid Phone Number Type defined in the Phone Type table.
Device Geographic Type
The user defined device ID geo type code. The Option Value must be set as a valid Geographic Type defined in the Geographic Type table.
Outage Call Contact Name Characteristic Type
The characteristic type code your implementation uses to capture a contact name on a trouble call. The Option Value must be set as a valid Characteristic Type defined in the Characteristic Type table.
Outage Call Contact Number Characteristic Type
The characteristic type code your implementation uses to capture a contact number on a trouble call. The Option Value must be set as a valid Characteristic Type defined in the Characteristic Type table.
Outage Call Identifier Characteristic Type
The characteristic type code your implementation uses to capture a call identifier on a trouble call. The Option Value must be set as a valid Characteristic Type defined in the Characteristic Type table.
Outage Call Street Name Characteristic Type
The characteristic type code your implementation uses to capture a street name on a trouble call. The Option Value must be set as a valid Characteristic Type defined in the Characteristic Type table.
Outage Call Street Name Characteristic Type
The characteristic type code your implementation uses to capture a street name on a trouble call. The Option Value must be set as a valid Characteristic Type defined in the Characteristic Type table.
Outage Call Cross Street Name Characteristic Type
The characteristic type code your implementation uses to capture a cross street name on a trouble call. The Option Value must be set as a valid Characteristic Type defined in the Characteristic Type table.
Outage Call Block Number Characteristic Type
The characteristic type code your implementation uses to capture a block number on a trouble call. The Option Value must be set as a valid Characteristic Type defined in the Characteristic Type table.
Outage Call City Characteristic Type
The characteristic type code your implementation uses to capture a city on a trouble call. The Option Value must be set as a valid Characteristic Type defined in the Characteristic Type table.
Outage Call State Characteristic Type
The characteristic type code your implementation uses to capture a state on a trouble call. The Option Value must be set as a valid Characteristic Type defined in the Characteristic Type table.
Master Configuration
To create a new master configuration with the Oracle Utilities Network Management System integration:
1. Navigate to Admin > General > Feature Configuration.
2. Create a new master configuration for the NMS Outage Integration Master Config or broadcast the master configuration if one already exists. Refer to the embedded help for more information.
For Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data Management (separate instance) implementations, this is configured in Oracle Utilities Customer Care and Billing.
3. Create a new master configuration for the NMS Sync Integration Master Config or broadcast the master configuration if one already exists. Refer to the embedded help for more information.
For Oracle Utilities Customer Care and Billing and Oracle Utilities Meter Data Management (separate instance) implementations, this is configured in Oracle Utilities Meter Data Management.
Service Type
Every service point type references a service type. The service type defines the type of service you provide to your customer (such as, electric, water, gas).
The code defined here must exactly match the values defined in the DVM specified in the table below.
Navigation
Guideline
Corresponding DVM
Admin > General > Service Type
Define your service types.
OUC2M_OUNMS_Account Type
Device Type
Every meter or item references a device type. The device type defines the type of service and common characteristics shared by its meters and items.
The code defined here must exactly match the values defined in the DVM specified in the table below.
Navigation
Guideline
Corresponding DVM
Admin > Device > Device Type
Define your device types.
OUC2M_OUNMS_MeterType