Define Characteristic Types
The following characteristic types must be defined to facilitate Outage integration:
Outage Group Code Characteristic Type
These characteristics are used to describe the outage problem.
- Create at least one pre-defined characteristic type
- For each characteristic type, define its list of valid values
- Include Service Task Type in the characteristic entity collection
Integration with Outage Management. The outage codes must be defined in both Oracle Utilities Customer Care and Billing and the outage management system. Refer to your Oracle Utilities Network Management System documentation for information about defining the outage codes there.
Contact Name Characteristic Type
This is used to link the contact name of the caller associated with an outage call as a characteristic on the outage call.
- Create an ad-hoc characteristic type
- Include Service Task Type in the characteristic entity collection
- Specify this characteristic type on the Schema Constants Feature Configuration using the Outage Call Contact Name Characteristic Type feature option
Contact Number Characteristic Type
This is used to link the contact number of the caller associated with an outage call as a characteristic on the outage call.
- Create an ad-hoc characteristic type
- Include Service Task Type in the characteristic entity collection
- Specify this characteristic type on the Schema Constants Feature Configuration using the Outage Call Contact Number Characteristic Type feature option
Call Identifier Characteristic Type
This is used to link the call identifier supplied by the caller associated with an outage call as a characteristic on the outage call.
- Create an ad-hoc characteristic type
- Include Service Task Type in the characteristic entity collection
- Specify this characteristic type on the Schema Constants Feature Configuration using the Outage Call Identifier Characteristic Type feature option
Street Name Characteristic Type
This is used to link location information supplied by the caller associated with a fuzzy trouble call as a characteristic on the outage call.
- Create an ad-hoc characteristic type
- Include Service Task Type in the characteristic entity collection
- Specify this characteristic type on the Schema Constants Feature Configuration using the Outage Call Street Name Characteristic Type feature option
Cross Street Name Characteristic Type
This is used to link location information supplied by the caller associated with a fuzzy trouble call as a characteristic on the outage call.
- Create an ad-hoc characteristic type
- Include Service Task Type in the characteristic entity collection
- Specify this characteristic type on the Schema Constants Feature Configuration using the Outage Call Cross Street Name Characteristic Type feature option
Block Number Characteristic Type
This is used to link location information supplied by the caller associated with a fuzzy trouble call as a characteristic on the outage call.
- Create an ad-hoc characteristic type
- Include Service Task Type in the characteristic entity collection
- Specify this characteristic type on the Schema Constants Feature Configuration using the Outage Call Block Number Characteristic Type feature option
City Characteristic Type
This is used to link location information supplied by the caller associated with a fuzzy trouble call as a characteristic on the outage call.
- Create an ad-hoc characteristic type
- Include Service Task Type in the characteristic entity collection
- Specify this characteristic type on theSchema Constants Feature Configuration using the Outage Call City Characteristic Type feature option
State Characteristic Type
This is used to link location information supplied by the caller associated with a fuzzy trouble call as a characteristic on the outage call.
- Create an ad-hoc characteristic type
- Include Service Task Type in the characteristic entity collection
- Specify this characteristic type on the Schema Constants Feature Configuration using the Outage Call State Characteristic Type feature option