Communication Flows

The table below lists the communications created for each NES command:


Command	Outbound Communication	Inbound Communication	Completion Event
Remote Connect	Retrieve Meter Information Read Load Status Read Billing Data On-Demand Connect Load	Read Load Status Notification Read Billing Data On-Demand Notification Connect Load Notification	Create IMD Connect Device
Remote Disconnect	Disconnect Load Read Billing Data On-Demand	Disconnect Load Notification Read Billing Data On-Demand Notification	Create IMD Disconnect Device
Device Commissioning	Add Meter Request Set ATM Configuration	Set ATM Configuration Notification	Device Commissioning
Device Decommissioning	Decommission Meter Request	Decommission Meter Notification	Device Decommissioning
On-Demand Read (Scalar)	Read Billing Data On-Demand	Read Billing Data On-Demand Notification	Create IMD
On-Demand Read (Interval)	Read Load Profile On Demand	Read Load Profile On-Demand Notification	Create IMD

Commissioning and Decommissioning Communications

Commissioning a previously decommissioned NES device requires a different process than commissioning a new device.

When you commission a device for the first time, a commissioning command is sent to BPEL to create the meter in NES using the DeviceManager.CreateMeter command. If Automatic Topology Management is selected then the DeviceManager.SetATMConfiguration command is also sent.

When you decommission a device, BPEL sends the DeviceManager.Move command to NES for the device. In NES you need to confirm that the device has been moved to a non-DC tree. You then need to manually delete the device from the non-DC tree. To permanently decommission the device you must delete it by using the DeviceManager.Delete command from the NES interface.

To recommission a device that has been previously decommissioned, you need to log into NES and manually move the meter from the non-DC tree to the DC tree that it belonged to previously. This will not be possible if the device has been deleted from within NES.