{"id":254618,"date":"2024-10-19T16:49:31","date_gmt":"2024-10-19T16:49:31","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-61968-92009\/"},"modified":"2024-10-25T12:14:47","modified_gmt":"2024-10-25T12:14:47","slug":"bs-en-61968-92009","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-61968-92009\/","title":{"rendered":"BS EN 61968-9:2009"},"content":{"rendered":"
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.<\/p>\n
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.<\/p>\n
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.<\/p>\n
PDF Pages<\/th>\n | PDF Title<\/th>\n<\/tr>\n | ||||||
---|---|---|---|---|---|---|---|
7<\/td>\n | CONTENTS <\/td>\n<\/tr>\n | ||||||
12<\/td>\n | INTRODUCTION <\/td>\n<\/tr>\n | ||||||
14<\/td>\n | 1 Scope 2 Normative references <\/td>\n<\/tr>\n | ||||||
15<\/td>\n | 3 Terms, definitions and abbreviations 3.1 Terms and definitions <\/td>\n<\/tr>\n | ||||||
16<\/td>\n | 3.2 Abbreviations <\/td>\n<\/tr>\n | ||||||
17<\/td>\n | 4 Reference and information models 4.1 General approach to metering systems <\/td>\n<\/tr>\n | ||||||
18<\/td>\n | 4.2 Reference model <\/td>\n<\/tr>\n | ||||||
19<\/td>\n | Figures Figure 1 \u2013 Example of an end device with functions <\/td>\n<\/tr>\n | ||||||
20<\/td>\n | Figure 2 \u2013 IEC\u00a061968-9 reference model <\/td>\n<\/tr>\n | ||||||
21<\/td>\n | Figure 3 \u2013 IEC\u00a061968-9 reference model with customer information and billing system <\/td>\n<\/tr>\n | ||||||
24<\/td>\n | 4.3 Interface reference model <\/td>\n<\/tr>\n | ||||||
25<\/td>\n | 4.4 Meter reading and control functions and components <\/td>\n<\/tr>\n | ||||||
26<\/td>\n | 4.5 Static information model Tables Table 1 \u2013 Business functions and abstract components <\/td>\n<\/tr>\n | ||||||
28<\/td>\n | Table 2 \u2013 Classes for meter reading and control <\/td>\n<\/tr>\n | ||||||
32<\/td>\n | 5 Meter reading and control message types 5.1 General Table 3 \u2013 Classes related to meter reading and control <\/td>\n<\/tr>\n | ||||||
33<\/td>\n | 5.2 End device event messages <\/td>\n<\/tr>\n | ||||||
34<\/td>\n | Figure 4 \u2013 Outage detection, request\/reply message exchange, example 1 Figure 5 \u2013 Outage detection, request\/reply message exchange, example 2 <\/td>\n<\/tr>\n | ||||||
35<\/td>\n | Figure 6 \u2013 Outage detection, publish\/subscribe exchange, example 1 <\/td>\n<\/tr>\n | ||||||
36<\/td>\n | Figure 7 \u2013 Outage detection, publish\/subscribe exchange, example 2 Figure 8 \u2013 Meter health event exchange, example 1 <\/td>\n<\/tr>\n | ||||||
37<\/td>\n | Figure 9 \u2013 Meter health event exchange, example 2 <\/td>\n<\/tr>\n | ||||||
38<\/td>\n | Figure 10 \u2013 Power quality event exchange, example 1 Figure 11 \u2013 Power quality event exchange, example 2 <\/td>\n<\/tr>\n | ||||||
39<\/td>\n | Figure 12 \u2013 End device event message format <\/td>\n<\/tr>\n | ||||||
40<\/td>\n | 5.3 Synchronization between systems Figure 13 \u2013 Example of meter asset management subscriptions <\/td>\n<\/tr>\n | ||||||
41<\/td>\n | Figure\u00a014 \u2013 Example of meter asset management publications Figure 15 \u2013 Example of WM to MAM exchange \u2013 test results <\/td>\n<\/tr>\n | ||||||
42<\/td>\n | Figure 16 \u2013 Example of WM to MAM exchange \u2013 asset status update <\/td>\n<\/tr>\n | ||||||
43<\/td>\n | Figure 17 \u2013 Example of reciprocal subscriptions (with MDM present) <\/td>\n<\/tr>\n | ||||||
44<\/td>\n | Figure 18 \u2013 Example of synchronization exchanges <\/td>\n<\/tr>\n | ||||||
45<\/td>\n | Figure 19 \u2013 End device asset message format Figure 20 \u2013 Customer meter data set message format <\/td>\n<\/tr>\n | ||||||
46<\/td>\n | 5.4 Meter reading messages Figure 21 \u2013 Example use of meter read schedule to create subscription <\/td>\n<\/tr>\n | ||||||
47<\/td>\n | Figure 22 \u2013 Meter read schedule message format <\/td>\n<\/tr>\n | ||||||
48<\/td>\n | Figure 23 \u2013 Meter readings message format <\/td>\n<\/tr>\n | ||||||
50<\/td>\n | Figure 24 \u2013 Example manual meter reading exchange <\/td>\n<\/tr>\n | ||||||
51<\/td>\n | Figure 25 \u2013 Example on-request meter read exchange <\/td>\n<\/tr>\n | ||||||
52<\/td>\n | Figure 26 \u2013 HistoricalMeterData exchange <\/td>\n<\/tr>\n | ||||||
53<\/td>\n | Figure 27 \u2013 Example billing inquiry message exchange <\/td>\n<\/tr>\n | ||||||
54<\/td>\n | 5.5 End device control messages Figure 28 \u2013 Meter asset reading message format <\/td>\n<\/tr>\n | ||||||
55<\/td>\n | Figure 29 \u2013 Example load control message exchange <\/td>\n<\/tr>\n | ||||||
56<\/td>\n | Figure 30 \u2013 Example message exchange for LC unit installation <\/td>\n<\/tr>\n | ||||||
57<\/td>\n | Figure 31 \u2013 Example message exchange for change of customer program (meter reconfigured) <\/td>\n<\/tr>\n | ||||||
58<\/td>\n | Figure 32 \u2013 Example message exchange for meter reconfiguration due to change of customer program where there is no MDM <\/td>\n<\/tr>\n | ||||||
59<\/td>\n | Figure 33 \u2013 Example message exchange for change of customer program with meter changed out <\/td>\n<\/tr>\n | ||||||
60<\/td>\n | Figure 34 \u2013 Example message exchange for meter connect\/disconnect <\/td>\n<\/tr>\n | ||||||
61<\/td>\n | Figure 35 \u2013 Example message exchange for remote connect\/disconnect operation directly between a CIS and MS <\/td>\n<\/tr>\n | ||||||
62<\/td>\n | Figure 36 \u2013 Example message exchange for real-time price signal <\/td>\n<\/tr>\n | ||||||
63<\/td>\n | 5.6 Meter service requests Figure 37 \u2013 End device controls message format <\/td>\n<\/tr>\n | ||||||
64<\/td>\n | Figure 38 \u2013 Example meter installation and removal message exchange <\/td>\n<\/tr>\n | ||||||
65<\/td>\n | Figure 39 \u2013 Example end device event message exchange due to meter changeout <\/td>\n<\/tr>\n | ||||||
66<\/td>\n | Figure 40 \u2013 Example message exchange due to CIS alarms <\/td>\n<\/tr>\n | ||||||
67<\/td>\n | Figure 41 \u2013 Example message exchange when meter is changed out for recalibration <\/td>\n<\/tr>\n | ||||||
68<\/td>\n | 5.7 Metering system events Figure 42 \u2013 Meter service requests message format <\/td>\n<\/tr>\n | ||||||
69<\/td>\n | Figure 43 \u2013 Example of MeterSystemHealth message exchange <\/td>\n<\/tr>\n | ||||||
70<\/td>\n | Figure 44 \u2013 Example of firmware upgrade message exchange <\/td>\n<\/tr>\n | ||||||
71<\/td>\n | Figure 45 \u2013 Example of meter system event message format <\/td>\n<\/tr>\n | ||||||
72<\/td>\n | 5.8 Customer switching Figure 46 \u2013 End device firmware message format <\/td>\n<\/tr>\n | ||||||
73<\/td>\n | 5.9 Payment metering service messages Figure 47 \u2013 Example of customer switching message exchange <\/td>\n<\/tr>\n | ||||||
74<\/td>\n | Figure 48 \u2013 Message exchange for transferring supplier information <\/td>\n<\/tr>\n | ||||||
75<\/td>\n | Figure 49 \u2013 Supplier configuration message format <\/td>\n<\/tr>\n | ||||||
76<\/td>\n | Figure 50 \u2013 Message exchange for transferring customer information <\/td>\n<\/tr>\n | ||||||
77<\/td>\n | Figure 51 \u2013 Customer configuration message <\/td>\n<\/tr>\n | ||||||
78<\/td>\n | Figure 52 \u2013 Message exchange for transferring customer agreement information Figure 53 \u2013 Customer agreement configuration message <\/td>\n<\/tr>\n | ||||||
79<\/td>\n | Figure 54 \u2013 Message exchange for transferring customer account information <\/td>\n<\/tr>\n | ||||||
80<\/td>\n | Figure 55 \u2013 Customer account configuration message <\/td>\n<\/tr>\n | ||||||
81<\/td>\n | Figure 56 \u2013 Message exchange for transferring auxiliary agreement information <\/td>\n<\/tr>\n | ||||||
82<\/td>\n | Figure 57 \u2013 Auxiliary agreement configuration message format <\/td>\n<\/tr>\n | ||||||
83<\/td>\n | Figure 58 \u2013 Message exchange for transferring pricing structures <\/td>\n<\/tr>\n | ||||||
84<\/td>\n | Figure 59 \u2013 PricingStructureConfig message format <\/td>\n<\/tr>\n | ||||||
85<\/td>\n | Figure 60 \u2013 Message exchange for transferring service category information Figure 61 \u2013 ServiceCategoryConfig message format <\/td>\n<\/tr>\n | ||||||
86<\/td>\n | Figure 62 \u2013 Message exchange for transferring service delivery point information <\/td>\n<\/tr>\n | ||||||
87<\/td>\n | Figure 63 \u2013 ServiceDeliveryPointConfig message format <\/td>\n<\/tr>\n | ||||||
88<\/td>\n | Figure 64 \u2013 Message exchange for transferring meter information <\/td>\n<\/tr>\n | ||||||
89<\/td>\n | Figure 65 \u2013 Meter asset configuration message <\/td>\n<\/tr>\n | ||||||
90<\/td>\n | Figure 66 \u2013 Message exchange for transferring service delivery point location information <\/td>\n<\/tr>\n | ||||||
91<\/td>\n | Figure 67 \u2013 SDPLocationConfig message format <\/td>\n<\/tr>\n | ||||||
92<\/td>\n | Figure 68 \u2013 Message exchange for transferring service location information <\/td>\n<\/tr>\n | ||||||
93<\/td>\n | Figure 69 \u2013 ServiceLocationConfig message format <\/td>\n<\/tr>\n | ||||||
94<\/td>\n | Figure 70 \u2013 Message exchange for transferring receipt information <\/td>\n<\/tr>\n | ||||||
95<\/td>\n | Figure 71 \u2013 ReceiptRecord message format <\/td>\n<\/tr>\n | ||||||
96<\/td>\n | Figure 72 \u2013 Message exchange for transferring transaction information <\/td>\n<\/tr>\n | ||||||
97<\/td>\n | Figure 73 \u2013 TransactionRecord message format <\/td>\n<\/tr>\n | ||||||
98<\/td>\n | 6 Document conventions 6.1 UML diagrams 6.2 Message definitions <\/td>\n<\/tr>\n | ||||||
99<\/td>\n | Annex A (informative) Description of message type verbs Table A.1 \u2013 Commonly used verbs <\/td>\n<\/tr>\n | ||||||
102<\/td>\n | Annex B (informative) Recommended message structure Figure B.1 \u2013 Recommended message message-format <\/td>\n<\/tr>\n | ||||||
103<\/td>\n | Figure B.2 \u2013 Recommended.Header message format Figure B.3 \u2013 Recommended.RequestType message format <\/td>\n<\/tr>\n | ||||||
104<\/td>\n | Figure B.4 \u2013 Recommended.ReplyType message format Table B.1 \u2013 ReplyCode categories <\/td>\n<\/tr>\n | ||||||
105<\/td>\n | Table B.2 \u2013 ReplyCode enumerations <\/td>\n<\/tr>\n | ||||||
109<\/td>\n | Annex C (informative) Recommended procedure for the generation of a ReadingType <\/td>\n<\/tr>\n | ||||||
110<\/td>\n | Table C.1 \u2013 Time attribute enumerations <\/td>\n<\/tr>\n | ||||||
111<\/td>\n | Table C.2 \u2013 Data qualifier enumerations <\/td>\n<\/tr>\n | ||||||
112<\/td>\n | Table C.3 \u2013 Accumulation behaviour enumerations <\/td>\n<\/tr>\n | ||||||
113<\/td>\n | Table C.4 \u2013 Direction of flow enumerations <\/td>\n<\/tr>\n | ||||||
114<\/td>\n | Table C.5 \u2013 Unit of measure enumerations <\/td>\n<\/tr>\n | ||||||
117<\/td>\n | Table C.6 \u2013 Measurement categories Table C.7 \u2013 MeasurementCategory enumerations <\/td>\n<\/tr>\n | ||||||
119<\/td>\n | Table C.8 \u2013 Phase enumerations <\/td>\n<\/tr>\n | ||||||
120<\/td>\n | Table C.9 \u2013 Metric multiplier enumerations <\/td>\n<\/tr>\n | ||||||
121<\/td>\n | Table C.10 \u2013 Unit of measure enumerations <\/td>\n<\/tr>\n | ||||||
124<\/td>\n | Table C.11 \u2013 Example ReadingTypes <\/td>\n<\/tr>\n | ||||||
126<\/td>\n | Annex D (informative) Recommended quality code enumerations Table D.1 \u2013 Example System IdentifiersValue <\/td>\n<\/tr>\n | ||||||
127<\/td>\n | Table D.2 \u2013 Example quality code categories Table D.3 \u2013 Example categorized codes <\/td>\n<\/tr>\n | ||||||
129<\/td>\n | Table D.4 \u2013 Example quality codes <\/td>\n<\/tr>\n | ||||||
130<\/td>\n | Annex E (informative) Recommended EndDeviceEvent category enumerations Table E.1 \u2013 Example EndDeviceEvent domain codes <\/td>\n<\/tr>\n | ||||||
131<\/td>\n | Table E.2 \u2013 Example EndDeviceEvent domain part codes <\/td>\n<\/tr>\n | ||||||
132<\/td>\n | Table E.3 \u2013 Example EndDeviceEvent type codes Table E.4 \u2013 Example EndDeviceEvent indexes <\/td>\n<\/tr>\n | ||||||
139<\/td>\n | Table E.5 \u2013 Example EndDeviceEvent codes <\/td>\n<\/tr>\n | ||||||
151<\/td>\n | Table E.6 \u2013 Example EndDeviceEvent codes <\/td>\n<\/tr>\n | ||||||
152<\/td>\n | Annex F (informative) Recommended EndDeviceControl code enumerations Table F.1 \u2013 Comparison of example demand reset codes Table F.2 \u2013 Example EndDevice control codes <\/td>\n<\/tr>\n | ||||||
154<\/td>\n | Annex G (informative) Recommended procedure for maintaining relationships between objects Figure G.1 \u2013 Typical CIM naming object <\/td>\n<\/tr>\n | ||||||
156<\/td>\n | Table G.1 \u2013 Example meter relationships <\/td>\n<\/tr>\n | ||||||
157<\/td>\n | Annex H (normative) XML Schemas for message payloads <\/td>\n<\/tr>\n | ||||||
251<\/td>\n | Annex I (informative) Mappings to ebIX <\/td>\n<\/tr>\n | ||||||
252<\/td>\n | Figure I.1 \u2013 ebIX XML schema <\/td>\n<\/tr>\n | ||||||
254<\/td>\n | Figure I.2 \u2013 ebIX metered data as UML class diagram <\/td>\n<\/tr>\n | ||||||
255<\/td>\n | Table I.3 \u2013 Meter reading: Mapping ebIX metered data to IEC MeterReadings <\/td>\n<\/tr>\n | ||||||
257<\/td>\n | Annex J (informative) Request parameters Figure J.1 \u2013 Message request structure <\/td>\n<\/tr>\n | ||||||
258<\/td>\n | Figure J.2 \u2013 GetMeterReadings <\/td>\n<\/tr>\n | ||||||
259<\/td>\n | Figure J.3 \u2013 GetEndDeviceAssets <\/td>\n<\/tr>\n | ||||||
260<\/td>\n | Figure J.4 \u2013 GetCustomerMeterDataSet <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":" Application integration at electric utilities. System interfaces for distribution management – Interface for meter reading and control<\/b><\/p>\n |