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 Itron OpenWay 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 Itron OpenWay 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 |
D8-AddMeterDefinitions |
Commission |
|
Device Decommission |
Device Removal |
D8-DeregisterMeter |
Decommission |
|
Device Status Check |
Device Status Check |
D8-PingByEndpoints |
Device Status Check |
|
Load Check* |
Load Check |
D8-DetectLoadSideVoltageByMtr |
Detect Load Side Voltage by Meter |
|
Multi-Devie Status Check |
Multi-Devie Status Check |
D8-PingByEndpointsMultiDevice |
Read Disconnect State By Meters |
|
On-Demand Read (Scalar) |
On-Demand Read (Scalar) |
D8-ReadScalar |
On Demand Read — Scalar |
|
Remote Connect |
Remote Connect |
D8-ReconnectMeter |
Connect |
|
Remote Disconnect |
Remote Disconnect |
D8-DisconnectMeter |
Disconnect |
* The Load Check processing method can be used to ensure that it is safe to connect a meter. The load check processing method is executed during the Connection Ready state of the Remote Connect activity and can be configured to detect the possibility of a load side voltage at the meter, or to check the disconnect meter switch on the meter.
If the Read Disconnect State business object is used as the processing method, you should configure the disconnect switch state values that indicate the state of the switch. These values are defined on the D8-DisconnectSwitchStateLookup extendable lookup, and are then added in the Disconnect Switch State Error Values section of the Itron - Read Disconnect State Result Inbound communication type. See Itron OpenWay Disconnect Switch State Lookup for more information.