BS EN 61968-9:2009:2010 Edition
$215.11
Application integration at electric utilities. System interfaces for distribution management – Interface for meter reading and control
Published By | Publication Date | Number of Pages |
BSI | 2010 | 262 |
This document is Part 9 of the IEC 61968 standard and specifies the information content of a set of message types that can be used to support many of the business functions related to meter reading and control. Typical uses of the message types include meter reading, meter control, meter events, customer data synchronization and customer switching. Although intended primarily for electrical distribution networks, IEC 61968-9 can be used for other metering applications, including non-electrical metered quantities necessary to support gas and water networks.
The purpose of this document is to defineastandard for the integration of metering systems (MS), which includes traditional manual systems, and (one or two-way) automated meter reading (AMR) systems, with other systems and business functions within the scope of IEC 61968. The scope of this International Standard is the exchange of information between a metering system and other systems within the utility enterprise. The specific details of communication protocols those systems employ are outside the scope of this standard. Instead, this standard will recognize and model the general capabilities that can be potentially provided by advanced and/or legacy meter infrastructures, including two-way communication capabilities such as load control, dynamic pricing, outage detection, distributed energy resource (DER) control signals and on-request read. In this way, this standard will not be impacted by the specification, development and/or deployment of next generation meter infrastructures either through the use of standards or proprietary means.
The capabilities and information provided by a meter reading system are important for a variety of purposes, including (but not limited to) interval data, time-based demand data, time-based energy data (usage and production), outage management, service interruption, service restoration, quality of service monitoring, distribution network analysis, distribution planning, demand reduction, customer billing and work management. This standard also extends the CIM (Common Information Model) to support the exchange of meter data.
PDF Catalog
PDF Pages | PDF Title |
---|---|
7 | CONTENTS |
12 | INTRODUCTION |
14 | 1 Scope 2 Normative references |
15 | 3 Terms, definitions and abbreviations 3.1 Terms and definitions |
16 | 3.2 Abbreviations |
17 | 4 Reference and information models 4.1 General approach to metering systems |
18 | 4.2 Reference model |
19 | Figures Figure 1 – Example of an end device with functions |
20 | Figure 2 – IEC 61968-9 reference model |
21 | Figure 3 – IEC 61968-9 reference model with customer information and billing system |
24 | 4.3 Interface reference model |
25 | 4.4 Meter reading and control functions and components |
26 | 4.5 Static information model Tables Table 1 – Business functions and abstract components |
28 | Table 2 – Classes for meter reading and control |
32 | 5 Meter reading and control message types 5.1 General Table 3 – Classes related to meter reading and control |
33 | 5.2 End device event messages |
34 | Figure 4 – Outage detection, request/reply message exchange, example 1 Figure 5 – Outage detection, request/reply message exchange, example 2 |
35 | Figure 6 – Outage detection, publish/subscribe exchange, example 1 |
36 | Figure 7 – Outage detection, publish/subscribe exchange, example 2 Figure 8 – Meter health event exchange, example 1 |
37 | Figure 9 – Meter health event exchange, example 2 |
38 | Figure 10 – Power quality event exchange, example 1 Figure 11 – Power quality event exchange, example 2 |
39 | Figure 12 – End device event message format |
40 | 5.3 Synchronization between systems Figure 13 – Example of meter asset management subscriptions |
41 | Figure 14 – Example of meter asset management publications Figure 15 – Example of WM to MAM exchange – test results |
42 | Figure 16 – Example of WM to MAM exchange – asset status update |
43 | Figure 17 – Example of reciprocal subscriptions (with MDM present) |
44 | Figure 18 – Example of synchronization exchanges |
45 | Figure 19 – End device asset message format Figure 20 – Customer meter data set message format |
46 | 5.4 Meter reading messages Figure 21 – Example use of meter read schedule to create subscription |
47 | Figure 22 – Meter read schedule message format |
48 | Figure 23 – Meter readings message format |
50 | Figure 24 – Example manual meter reading exchange |
51 | Figure 25 – Example on-request meter read exchange |
52 | Figure 26 – HistoricalMeterData exchange |
53 | Figure 27 – Example billing inquiry message exchange |
54 | 5.5 End device control messages Figure 28 – Meter asset reading message format |
55 | Figure 29 – Example load control message exchange |
56 | Figure 30 – Example message exchange for LC unit installation |
57 | Figure 31 – Example message exchange for change of customer program (meter reconfigured) |
58 | Figure 32 – Example message exchange for meter reconfiguration due to change of customer program where there is no MDM |
59 | Figure 33 – Example message exchange for change of customer program with meter changed out |
60 | Figure 34 – Example message exchange for meter connect/disconnect |
61 | Figure 35 – Example message exchange for remote connect/disconnect operation directly between a CIS and MS |
62 | Figure 36 – Example message exchange for real-time price signal |
63 | 5.6 Meter service requests Figure 37 – End device controls message format |
64 | Figure 38 – Example meter installation and removal message exchange |
65 | Figure 39 – Example end device event message exchange due to meter changeout |
66 | Figure 40 – Example message exchange due to CIS alarms |
67 | Figure 41 – Example message exchange when meter is changed out for recalibration |
68 | 5.7 Metering system events Figure 42 – Meter service requests message format |
69 | Figure 43 – Example of MeterSystemHealth message exchange |
70 | Figure 44 – Example of firmware upgrade message exchange |
71 | Figure 45 – Example of meter system event message format |
72 | 5.8 Customer switching Figure 46 – End device firmware message format |
73 | 5.9 Payment metering service messages Figure 47 – Example of customer switching message exchange |
74 | Figure 48 – Message exchange for transferring supplier information |
75 | Figure 49 – Supplier configuration message format |
76 | Figure 50 – Message exchange for transferring customer information |
77 | Figure 51 – Customer configuration message |
78 | Figure 52 – Message exchange for transferring customer agreement information Figure 53 – Customer agreement configuration message |
79 | Figure 54 – Message exchange for transferring customer account information |
80 | Figure 55 – Customer account configuration message |
81 | Figure 56 – Message exchange for transferring auxiliary agreement information |
82 | Figure 57 – Auxiliary agreement configuration message format |
83 | Figure 58 – Message exchange for transferring pricing structures |
84 | Figure 59 – PricingStructureConfig message format |
85 | Figure 60 – Message exchange for transferring service category information Figure 61 – ServiceCategoryConfig message format |
86 | Figure 62 – Message exchange for transferring service delivery point information |
87 | Figure 63 – ServiceDeliveryPointConfig message format |
88 | Figure 64 – Message exchange for transferring meter information |
89 | Figure 65 – Meter asset configuration message |
90 | Figure 66 – Message exchange for transferring service delivery point location information |
91 | Figure 67 – SDPLocationConfig message format |
92 | Figure 68 – Message exchange for transferring service location information |
93 | Figure 69 – ServiceLocationConfig message format |
94 | Figure 70 – Message exchange for transferring receipt information |
95 | Figure 71 – ReceiptRecord message format |
96 | Figure 72 – Message exchange for transferring transaction information |
97 | Figure 73 – TransactionRecord message format |
98 | 6 Document conventions 6.1 UML diagrams 6.2 Message definitions |
99 | Annex A (informative) Description of message type verbs Table A.1 – Commonly used verbs |
102 | Annex B (informative) Recommended message structure Figure B.1 – Recommended message message-format |
103 | Figure B.2 – Recommended.Header message format Figure B.3 – Recommended.RequestType message format |
104 | Figure B.4 – Recommended.ReplyType message format Table B.1 – ReplyCode categories |
105 | Table B.2 – ReplyCode enumerations |
109 | Annex C (informative) Recommended procedure for the generation of a ReadingType |
110 | Table C.1 – Time attribute enumerations |
111 | Table C.2 – Data qualifier enumerations |
112 | Table C.3 – Accumulation behaviour enumerations |
113 | Table C.4 – Direction of flow enumerations |
114 | Table C.5 – Unit of measure enumerations |
117 | Table C.6 – Measurement categories Table C.7 – MeasurementCategory enumerations |
119 | Table C.8 – Phase enumerations |
120 | Table C.9 – Metric multiplier enumerations |
121 | Table C.10 – Unit of measure enumerations |
124 | Table C.11 – Example ReadingTypes |
126 | Annex D (informative) Recommended quality code enumerations Table D.1 – Example System IdentifiersValue |
127 | Table D.2 – Example quality code categories Table D.3 – Example categorized codes |
129 | Table D.4 – Example quality codes |
130 | Annex E (informative) Recommended EndDeviceEvent category enumerations Table E.1 – Example EndDeviceEvent domain codes |
131 | Table E.2 – Example EndDeviceEvent domain part codes |
132 | Table E.3 – Example EndDeviceEvent type codes Table E.4 – Example EndDeviceEvent indexes |
139 | Table E.5 – Example EndDeviceEvent codes |
151 | Table E.6 – Example EndDeviceEvent codes |
152 | Annex F (informative) Recommended EndDeviceControl code enumerations Table F.1 – Comparison of example demand reset codes Table F.2 – Example EndDevice control codes |
154 | Annex G (informative) Recommended procedure for maintaining relationships between objects Figure G.1 – Typical CIM naming object |
156 | Table G.1 – Example meter relationships |
157 | Annex H (normative) XML Schemas for message payloads |
251 | Annex I (informative) Mappings to ebIX |
252 | Figure I.1 – ebIX XML schema |
254 | Figure I.2 – ebIX metered data as UML class diagram |
255 | Table I.3 – Meter reading: Mapping ebIX metered data to IEC MeterReadings |
257 | Annex J (informative) Request parameters Figure J.1 – Message request structure |
258 | Figure J.2 – GetMeterReadings |
259 | Figure J.3 – GetEndDeviceAssets |
260 | Figure J.4 – GetCustomerMeterDataSet |