Processing Methods
Processing methods define the format or means by which a service provider receives and/or sends data from and/or to the application, including as bill determinants, usage data, or device events. Processing methods are also used to define how to create information internal to the application such as initial measurement data and device events. Processing methods can also be used to define how command requests are sent to a given head-end system.
The following types of processing methods must be configured for the NES service provider. Refer to the Oracle Utilities Service and Measurement Data Foundation documentation for more information about configuring processing methods.
Initial Measurement Creation
Initial measurement creation processing methods define the business objects used to create initial measurements. The IMD Seeder inbound web service uses this processing method to determine which type of initial measurement business object to instantiate when receiving usage from a head-end system.
Device Event Mapping
Device event mapping processing methods define how head-end-specific device events are mapped to standard device event names. The Device Event Seeder inbound web service uses this processing method to determine which type of device event business object to instantiate when receiving device events from a head-end system.
UOM Translation
UOM mapping processing methods define how head-end-specific unit of measure (UOM) codes are mapped to standard UOM codes. This processing method is used to determine how to map head-end system UOM codes to standard UOM codes when receiving usage from the head-end system.
Commands
Command processing methods define how command requests are sent to a head-end system. More specifically, they define the type of outbound communication business object to create for each type of command, and the outbound message type to send to the head-end system.
The following types of command processing methods can be configured for the NES service provider, based on the requirements of each implementation using the “How to Create OB COMM/Send OB Message” processing method business object (D1–HowToCreateActivityOBComm).
| Command | Processing Role | Default Business Object | Default Outbound Message Type |
|---|---|---|---|
|
Device Commission |
Device Registration |
D4-SetATMConfiguration |
Set ATM Configuration |
|
Device Decommission |
Device Removal |
D4-DecommMeterRequest |
Decommission Meter Request |
|
On-Demand Read (Scalar) |
On-Demand Read (Scalar) |
D4-ReadBillingData |
Read Billing Data |
|
On-Demand Read (Interval) |
On-Demand Read (Interval) |
D4-ReadLoadProfile |
Read Load Profile |
|
Device Status Check |
Device Status Check |
D4-ReadLoadStatus |
Read Load Status |
|
Remote Connect |
Remote Connect |
D4-ConnectLoad |
Connect Load |
|
Remote Disconnect |
Remote Disconnect |
D4-DisconnectLoad |
Disconnect Load |
Other Processing Methods
This section outlines details for other processing methods used by the NES adapter.
| Processing Role | Default Business Object | Default Outbound Message Type |
|---|---|---|
|
NES Add Meter Request |
D4-AddMeterRequest |
Commission |
|
NES Retrieve Meter Identifier |
D4-RetrieveMeterIdentifier |
Commission Retrieve Meter Identifier |
|
NES Retrieve Meter Information |
D4-RetrieveMeterInfo |
Retrieve Meter Info |