61968 – 9 Meter Reading and Control CIM University CESI/TERNA Milan, Italy June 15, 2010

1. 61968 – 9 Meter Reading and ControlCIM UniversityCESI/TERNAMilan, ItalyJune 15, 2010 Margaret Goodrich, Manager, Systems Engineering SISCO, Inc. 6605 19½ Mile Road Sterling Heights, MI 48314 USA Tel: +1-903-477-7176 Fax: +1-903-489-0063 E-Mail: margaret@sisconet.com

2. Introduction Scope/Purpose Reference Model Information Models Meter Reading and Control Messages

3. Scope/Purpose To Define the exchange of information between a Metering System and other systems within the Utility enterprise Specifies the information content of a set of message types that can be used to support many of the business functions related to Merter Reading and Control. Typical uses of the message types include: Meter Reading and Meter Control Meter Events Customer Data Synchronization and Customer Switching

4. Reference Model The Reference Model provides examples of the logical components and data flows related to this standard. The Meter is treated as an “end device” An End Device: Has a unique identity Is managed as a physical asset May issue events May receive control requests May collect and report measured values May participate in utility business processes The Reference Model describes the flows between the components.

5. Reference Model - Full

6. Reference Model - Partial

7. The reference architecture reflects fine main logical components related to metering: Metering System including data collection, control and reconfiguration functionality Meter Data Management Meter Maintenance Load Management including load control and load analysis functionality Meter Asset Management Meter Administration Functions, which may be a part of the Meter Data Management Reference Model

8. Reference Model

9. The Static Information Model that contains the metering classes, attributes and associations is defined in detail in IEC61968 Part 11 or in IEC61970 Part 301. Classes for Meter Reading and Control are contained in the following Packages: Asset classes are defined in Asset package in 61968-11 Customer classes are defined in the Customer package in 61968-11 Metering classes are defined in the Metering package in 61968-11 Prepayment classes are defined in the PaymentMetering package in 61968 Information Model

10. Message Types • The key message payload structures include: • CustomerMeterDataSet • MeterAsset • MeterAssetReading • EndDeviceControls • EndDeviceEvents • MeterReadings • MeterReadSchedule • MeterServiceRequest • MeterSystemEvents • EndDeviceFirmware

11. EndDeviceEvent Messages • EndDeviceEvent Messages Convey events related to: • Sustained Outage Detection • Momentary Outage Detection • Low Voltage Threshold Detection • High Voltage Threshold Detection • Distortion Meter Health • Tamper Detection • Revenue Event

12. EndDeviceAssets Message

13. CustomerMeterDataSet Message

14. MeterReadSchedule Message • Meter readings may be requested using one or more of the following parameters: • Specific meter, using the EndDeviceAsset mRID • Specific meter, using a serialNumber as known to the Metering System • EndDeviceGroups, where an EndDeviceGroup identifies a groupAddress used within the Metering System • As specified using a TimeSchedule • ReadingTypes can be specified to identify the desired reading types

15. MeterReadings Message • MeterReadings message allows for: • Readings from one or more meters • Reading values each have an associated reading type, timestamp and value • Many Quality values can be associated with each reading value • Readings can be supplied in the form of interval blocks if the common reading types are grouped together. • Event Histories are returned with meter readings.

16. MeterAssetReading Message • MeterAssetReading messages may contain many MeterService Work items. • Each MeterServiceWork item identifies a MeterAsset and Customer • There may be many Readings and EndDeviceEvents obtained from the MeterAsset.

17. EndDeviceControls Message • Specific Meters may be addresed by CustomerAgreement, EndDeviceAsset and/or EndDeviceGroup • At least one address and a typeControl attribute is required for this message • TypeControl element identifies the type of control to be performed

18. MeterServiceRequests Message • May include one or more MeterServiceWork items • Each item may refer to a max of two meters to provide a means to replace a meter. • Meter readings can be obtained as a part of the work.

19. MeterSystemEvent Message • Supports the reporting of activity within any type of end device (including meters), as well as within the MS communication infrastructure • Can be used to describe an event in the end device itself, or in the MS communication infrastructure

20. EndDeviceFirmware Message • Supports the naming of the affected device function, as well as additional parameter details that may be necessary in the report • This structure, together with the ActivityRecord can effectively describe the nature of the event, when the event occurred, and what has happened

21. ReceiptRecord Message • When MS receives a payment, a receipt is generated and the relevant information about the payment is typically recorded as a receipt record. • This information may be accessed by means of ReceiptRecord message payload.

22. TransactionRecord Message • Information about the sale of a prepaid token or the receipt of an account payment is typically recorded by MS in the form a financial transaction record

23. SupplierConfig Message • Information about the supplier (retailer or utility for example) of the service may be configured into MS by means of SupplierConfig message payload

24. Several Other Configuration Messages

25. Several Other Configuration Messages - Continued

26. Questions & Contacts Margaret Goodrich – Home Office: 903-489-1494 Cell: 903-477-7176 Email: margaret@sisconet.com