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 premise. • Adhoc characteristic type | Include Service Task | N/A |
Location State | • Characteristic used to identify the location state for an outage without a premise. • Adhoc characteristic type | Include Service Task | N/A |
Location 1 | • Characteristic used to identify a location used for an outage without a premise. (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 premise 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 premise 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 premise. • 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 premise. • 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 |
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 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. |
Navigation | Guideline | Corresponding DVM |
Admin > General > Service Type | Define your service types | OUC2M_OUNMS_AccountType |
Navigation | Guideline | Corresponding DVM |
Admin > Device > Device Type | Define your device types. | OUC2M_OUNMS_MeterType |
Batch | Description |
F1-SYNRQ | Sync Request Monitor Process |
Batch Parameters | Parameter Description | Value |
---|---|---|
maintenanceObject | Sync Request maintenance object | F1-SYNC REQ (The defaulted value.) |
isRestrictedByBatch Code | The value of true restricts processing to sync requests whose current state is linked to this batch code. | |
restrictToBusiness Object | Enter a business object code here to limit the process to sync requests linked to this business object. | D1-NMSSP CustomerSyncRequest (To run only the NMS customer sync request, populate this value) |
restrictToBOStatus | Enter a status code here to limit the process to sync requests in this state. | PENDING (To only process sync request, in Pending status, populate this value) |
Batch | Description |
D1-NMSSP | NMS SP Customer Sync Initial Load |
Batch Parameters | Parameter Description | Value |
---|---|---|
syncRequestMO | Maintenance Object | D1-SP (This is the defaulted value.) |
syncRequestBO | Enter a business object code here to limit the process to sync requests linked to this business object. | D1-NMSSPCustomerSync Request |
filterAlgorithm | Enter a filter algorithm here to limit the process to sync requests that should be sent to Oracle Utilities Network Management System. | D1-NMSSPCustomerSync Request (This algorithm filters for eligible service point types as defined in the NMS Sync Integration Master Configuration.) |
Algorithm Type | Description |
---|---|
D1-CUSCDCSP | This algorithm instantiates SP-based sync request whenever a change to the Contact MO is detected (updating a person record in C2M triggers an internal sync to the contact record, which in turn will trigger this audit algorithm). Define the D1-NMSSPCustomerSyncRequest sync request BO to be instantiated in the algorithm's parameters. |
D1-USCDCSP | This algorithm instantiates SP-based sync request whenever a change to the Usage Subscription MO is detected (updating a SA record in C2M triggers an internal sync to the usage subscription record, which in turn will trigger this audit algorithm). Define the D1-NMSSPCustomerSyncRequest sync request BO to be instantiated in the algorithm's parameters. |
D1-SPIE-CDCP | This algorithm instantiates SP-based sync request whenever a change to the Install Event MO is detected. Define the D1-NMSSPCustomerSyncRequest sync request BO to be instantiated in the algorithm's parameters. |
D1-SPDV-CDCP | This algorithm instantiates SP-based sync request whenever a change to the Device MO is detected. Define the D1-NMSSPCustomerSyncRequest sync request BO to be instantiated in the algorithm's parameters. |
Maintenance Objects | Description |
---|---|
D1-CONTACT | Specify the MO Audit algorithm configured in the previous section. |
D1-US | Specify the MO Audit algorithm configured in the previous section. |
D1-INSTLEVT | Specify the MO Audit algorithm configured in the previous section. |
D1-DEVICE | Specify the MO Audit algorithm configured in the previous section. |
D1-SP | Specify the generic MO Audit algorithm F1-GCHG-CDCP. Also, specify the D1-NMSSPCustomerSyncRequest BO in the Sync Request BO MO Option. |
Business Object | Description |
---|---|
D1-NMSSPCustomer SyncRequest | This business object defines the behavior of the outbound sync request for NMS. It contains the schema elements monitored and synchronized to NMS. The following must be configured and defined on the NMS Sync Integration master configuration as they are necessary to create the outbound sync request: • Outbound Message Type: This contains a reference to the outbound message BO to use. The base package includes BO D1-NMSSPCustomerSyncReqOutMsg for the NMS SP Sync. Refer to the Defining Outbound Message Types section in the user documentation for more information. • External System: This contains the reference to the outbound message type and its corresponding configuration for communicating with the external system. The base package includes the message D1-NMSSPCustomerSyncReqOutMsg.xsl. Refer to the External Systems section in the user documentation for more information. • Specify the pre-processing algorithm configured in the previous section. • Specify the time out algorithm as a monitor algorithm on the Awaiting Acknowledgement state for this BO. • Specify the To Do creation algorithm on the Error state for this BO Depending on the technology used to communicate the sync request to the external system, you may need to create your own enter algorithm and plug it into the Send Request state. |