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 L+G 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 L+G 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
D3-AddMeterToInventoryMultiSp
Add Meter to Inventory
Device Commission
Device Installation
D3-MeterExNotificationMultiSp
Meter Exchange Notification
Device Decommission
Device Removal
D3-MtrRmvNotifMultiSpeak
Decommission
Meter Remove Notification
Device Deregistration
Device Deregistration
D3-MeterRetireNotification
Deregister Device
On-Demand Read (Scalar), Multispeak and CIM
On-Demand Read (Scalar)
MS: D3-InitiateMRByMtrNbr
CIM: D3-CIMMeterOnDemandRead
MS: Initiate Meter Read by Meter Number
CIM: CIM On Demand Read
On-Demand Read (Interval)
On-Demand Read (Interval)
D3-CIMGetLPData
CIM On Demand Read
Demand Reset
Demand Reset
D3-ScheduleDemandReset
Demand Reset
Device Status Check
Device Status Check
D3-CIMPing
Device Status Check
Remote Connect
Remote Connect
D3-InitiateConnectDisconnect
Connect Device
Remote Disconnect
Remote Disconnect
D3-InitiateConnectDisconnect
Disconnect Device