1、BSI Standards PublicationApplication integration at electric utilities System interfaces for distribution managementPart 900: Guidance for implementation of IEC 61968-9PD IEC/TR 61968-900:2015National forewordThis Published Document is the UK implementation of IEC/TR61968-900:2015. The UK participat
2、ion in its preparation was entrusted to TechnicalCommittee PEL/57, Power systems management and associated information exchange.A list of organizations represented on this committee can be obtained onrequest to its secretary.This publication does not purport to include all the necessary provisions o
3、fa contract. Users are responsible for its correct application. The British Standards Institution 2015.Published by BSI Standards Limited 2015ISBN 978 0 580 90615 2ICS 33.200Compliance with a British Standard cannot confer immunity fromlegal obligations.This Published Document was published under th
4、e authority of theStandards Policy and Strategy Committee on 31 December 2015.Amendments/corrigenda issued since publicationDate Text affectedPUBLISHED DOCUMENTPD IEC/TR 61968-900:2015IEC TR 61968-900 Edition 1.0 2015-10 TECHNICAL REPORT Application integration at electric utilities System interface
5、s for distribution management Part 900: Guidance for implementation of IEC 61968-9 INTERNATIONAL ELECTROTECHNICAL COMMISSION ICS 33.200 ISBN 978-2-8322-2950-7 Registered trademark of the International Electrotechnical Commission Warning! Make sure that you obtained this publication from an authorize
6、d distributor. colourinsidePD IEC/TR 61968-900:2015 2 IEC TR 61968-900:2015 IEC 2015 CONTENTS FOREWORD . 8 INTRODUCTION . 10 1 Scope 13 2 Normative references. 13 3 IEC 61968-100 basics 13 3.1 General . 13 3.2 IEC 61968-100 message exchange patterns 14 3.3 IEC 61968-100 message types 14 3.3.1 Genera
7、l . 14 3.3.2 Request messages . 15 3.3.3 Response messages 17 3.3.4 Unsolicited event messages . 18 3.4 IEC 61968-100 message content . 19 3.4.1 General . 19 3.4.2 Verb and noun elements in the message header . 20 3.4.3 Get requests 20 3.4.4 Other requests . 21 3.4.5 The CorrelationID element . 21 3
8、.4.6 Other elements in the message header . 21 3.4.7 The Message.xsd XSD schema definition file 22 4 Request and response messages in detail 23 4.1 General . 23 4.2 Several potential response messages for each request message . 23 4.3 Response messages contain a status indication . 24 4.4 Response m
9、essages containing data and error notifications . 24 4.5 Specific error indications in the response messages 24 4.6 Implicit indication of success . 27 4.7 General error indications in the response messages 28 4.7.1 General . 28 4.7.2 Setting the element . 28 4.7.3 Multiple response messages 29 4.8
10、Multiple , and elements . 29 4.9 Implementation-specific messages 30 5 The naming of objects 30 5.1 General . 30 5.2 Naming meters 30 5.3 EndDeviceGroups, UsagePoints and UsagePointGroups 32 5.4 Naming of other objects. 33 5.5 Provisioning and interrogating a system . 33 6 Meter read requests and re
11、sponses . 33 6.1 General . 33 6.2 Message exchange patterns 34 6.2.1 General . 34 6.2.2 Request message with a single response message . 34 6.2.3 Request message with multiple response messages . 35 6.3 GetMeterReadings request 37 PD IEC/TR 61968-900:2015IEC TR 61968-900:2015 IEC 2015 3 6.3.1 Genera
12、l . 37 6.3.2 Naming of meters . 39 6.3.3 The ReadingType element 39 6.3.4 The ReadingQuality element 41 6.3.5 The TimeSchedule element 42 6.3.6 Specifying multiple constraints in a request message 43 6.3.7 Coincident meter reads 46 6.4 On-demand meter reads 47 6.4.1 General . 47 6.4.2 Pinging a mete
13、r 49 6.5 MeterReadings response . 49 6.5.1 General . 49 6.5.2 The element 51 6.5.3 The element . 52 6.5.4 The element . 53 6.5.5 The element . 53 6.5.6 The elements 53 6.5.7 The EndDeviceType, ReadingQualityType and ReadingType elements 53 6.6 Unsolicited meter reads . 56 6.6.1 General . 56 6.6.2 Me
14、ssage exchange pattern . 56 6.6.3 Missing reads 58 6.6.4 Unsolicited MeterReads together with EndDeviceEvents . 59 6.7 More about timestamps and interval data . 60 6.7.1 General . 60 6.7.2 Interval data . 61 6.7.3 The interval block . 62 6.7.4 Raw data . 62 7 Meter control requests and responses 63
15、7.1 General . 63 7.2 Message exchange pattern 64 7.3 Create(EndDeviceControls) message 65 7.3.1 General . 65 7.3.2 EndDeviceControls element . 66 7.4 Reply(EndDeviceControls) message 70 7.5 Created(EndDeviceEvents) message . 71 7.5.1 General . 71 7.5.2 EndDeviceEvents element 71 7.6 Unsolicited EndD
16、eviceEvents Messages 74 7.6.1 General . 74 7.6.2 Message exchange pattern . 75 7.7 Premises area networks 75 7.7.1 General . 75 7.7.2 Message exchange pattern . 75 7.7.3 Pairing the Meter and PAN device 76 8 Configuration and provisioning . 76 8.1 General . 76 8.2 Message exchange pattern 77 PD IEC/
17、TR 61968-900:2015 4 IEC TR 61968-900:2015 IEC 2015 8.3 Meter configuration . 78 8.3.1 General . 78 8.3.2 Create(MeterConfig) message 79 8.3.3 Reply(MeterConfig) message, success case . 81 8.3.4 Reply(MeterConfig) message, failure case 81 8.4 Master data linkage . 81 8.4.1 General . 81 8.4.2 Create(M
18、asterDataLinkage) message . 82 8.5 OperationSets . 83 8.5.1 General . 83 8.5.2 OperationSet request message 84 8.5.3 OperationSet Response Message . 86 9 Scheduling actions for future execution 87 9.1 General . 87 9.2 Scheduling a meter read . 87 9.2.1 General . 87 9.2.2 Message exchange pattern . 8
19、8 9.2.3 MeterReadSchedule element 89 9.3 Create(MeterReadSchedule) message . 92 9.3.1 General . 92 9.3.2 Reply(MeterReadSchedule) message . 93 9.4 Cancelling a request . 94 9.4.1 General . 94 9.4.2 Cancel(MeterReadSchedule) request . 94 10 Transporting IEC 61968-9 messages 95 10.1 General . 95 10.2
20、Transporting over SOAP 95 10.2.1 General . 95 10.2.2 Generic WSDL . 96 10.2.3 Simple acknowledgement messages . 96 10.2.4 Example message flow . 97 10.3 Transporting over JMS 98 10.3.1 General . 98 10.3.2 Explicit acknowledgements . 99 10.3.3 JMS property details 99 10.3.4 Process details 99 10.3.5
21、Object details . 100 11 Summary of message fields . 100 11.1 General . 100 11.2 Meter read operations . 100 11.2.1 General . 100 11.2.2 Request message 100 11.2.3 Response message 102 11.2.4 Unsolicited meter read . 106 11.3 Meter control operations 106 11.3.1 General . 106 11.3.2 Request message el
22、ements 106 11.3.3 Initial response message 108 11.3.4 Subsequent consequential event messages 109 PD IEC/TR 61968-900:2015IEC TR 61968-900:2015 IEC 2015 5 11.3.5 Unsolicited meter event 111 11.4 Configuration and provisioning 111 11.4.1 General . 111 11.4.2 Provisioning a meter 111 11.4.3 Creation o
23、f a ComModule . 113 11.4.4 ServiceLocation . 114 11.4.5 ServiceCategoryConfig. 116 11.4.6 Service supplier . 116 11.4.7 UsagePoint location . 118 11.4.8 Usage point . 120 11.4.9 Customer . 122 11.4.10 Customer account 124 11.4.11 Customer Agreement . 126 11.4.12 Pricing Structure 128 11.4.13 MasterD
24、ataLinkage 129 11.4.14 OperationSet . 132 11.4.15 Adding, changing or deleting an object identifier . 137 Figure 1 Example message for a simple meter read request . 16 Figure 2 Example response message to a simple meter read request 17 Figure 3 Example unsolicited event message . 18 Figure 4 Request
25、Message definition according to Message.xsd 19 Figure 5 ResponseMessage definition according to Message.xsd 19 Figure 6 EventMessage definition according to Message.xsd 20 Figure 7 Subelements allowed inside a element 23 Figure 8 Example of a success indication in a Reply element 24 Figure 9 Example
26、 of error indications in a Reply element (incomplete) 25 Figure 10 Subelements allowed inside a element 26 Figure 11 Subelements allowed inside a element 27 Figure 12 Example of overall indication of success in a Reply element 28 Figure 13 Example of error indications in a Reply element (corrected)
27、. 28 Figure 14 EndDevice definition . 31 Figure 15 Example of a Meter Read Request with NameType and NameTypeAuthority 32 Figure 16 Message exchange pattern for a meter read request with a single response message . 35 Figure 17 Message exchange pattern for a meter read request with multiple response
28、 messages . 37 Figure 18 GetMeterReadings definition according to GetMeterReadings.xsd . 39 Figure 19 definition 41 Figure 20 definition 42 Figure 21 definition 43 Figure 22 Example of a request message for two ReadingType codes over two meters 45 Figure 23 Example of a request message for two meter
29、/ReadingType combinations 46 Figure 24 Message exchange pattern for an on-demand meter read 48 PD IEC/TR 61968-900:2015 6 IEC TR 61968-900:2015 IEC 2015 Figure 25 Example of an on-demand meter read request message 49 Figure 26 Example of a response to a meter read request . 50 Figure 27 MeterReading
30、s definition according to MeterReadings.xsd 51 Figure 28 definition 52 Figure 29 definition 52 Figure 30 definition . 53 Figure 31 definition . 54 Figure 32 Example of a meter read response with named ReadingType and ReadingQuality elements 56 Figure 33 Message exchange pattern for a set of unsolict
31、ed meter reads 57 Figure 34 Example of an unsolicited meter read message . 57 Figure 35 Example of a missing reading in a published message 58 Figure 36 Example of a known missing reading in a published message 59 Figure 37 Example of a message showing both an event and a reading 60 Figure 38 Readin
32、g Timestamps 61 Figure 39 Example use of IntervalBlocks 63 Figure 40 Message exchange pattern for a meter control operation . 65 Figure 41 Example of a create(EndDeviceControls) message for one meter 66 Figure 42 Example of a create(EndDeviceControls) message for two meters . 66 Figure 43 EndDeviceC
33、ontrols definition 67 Figure 44 EndDeviceControl definition 69 Figure 45 EndDeviceControlType definition 70 Figure 46 Example of a reply(EndDeviceControls) message 70 Figure 47 Example of a created(EndDeviceEvents) message 71 Figure 48 EndDeviceEvents definition 71 Figure 49 EndDeviceEvent definitio
34、n 73 Figure 50 EndDeviceEventType definition . 74 Figure 51 Message exchange pattern for an unsolicted EndDevice event 75 Figure 52 Message exchange pattern for a create(MeterConfig) message . 78 Figure 53 MeterConfig definition . 79 Figure 54 Example of a create(MeterConfig) message 80 Figure 55 Ex
35、ample of a reply(MeterConfig) message, success case 81 Figure 56 Example of a reply(MeterConfig) message, failure case . 81 Figure 57 MasterDataLinkageConfig Relationships . 82 Figure 58 Example of a create(MasterDataLinkageConfig) message . 83 Figure 59 Example of an execute(OperationSet) message 8
36、5 Figure 60 Example of a reply(OperationSet) message, success case 86 Figure 61 Example of a reply(OperationSet) message, failure case . 87 Figure 62 Message exchange pattern for scheduling a set of meter reads . 89 Figure 63 MeterReadSchedule definition 90 Figure 64 MeterReadSchedule.TimeSchedule d
37、efinition 92 Figure 65 Example of a meter read schedule request 93 Figure 66 Example of a response to a meter read schedule request 93 PD IEC/TR 61968-900:2015IEC TR 61968-900:2015 IEC 2015 7 Figure 67 Example of a meter read schedule cancel message . 95 Figure 68 Example of a simple meter read requ
38、est imbedded in a SOAP message 95 Figure 69 Example of a simple acknowledgement message 97 Figure 70 Message exchange pattern showing the simple acknowledgement messages . 98 Table 1 Common EndDeviceControls and their corresponding EndDeviceEvent codes 64 Table 2 Common EndDeviceEvent codes for unso
39、licited messages . 75 Table 3 Config Profiles . 77 Table 4 JMS properties 99 Table 5 get(MeterReadings) fields 101 Table 6 reply(MeterReadings) fields . 103 Table 7 create(EndDeviceControls) fields . 107 Table 8 reply(EndDeviceControls) fields . 108 Table 9 created(EndDeviceEvents) fields . 109 Tabl
40、e 10 create(MeterConfig) fields 111 Table 11 create(ComModuleConfig) fields 113 Table 12 create(ServiceLocationConfig) fields 115 Table 13 create(ServiceCategoryConfig) fields . 116 Table 14 create(ServiceSupplierConfig) fields 117 Table 15 create(UsagePointLocationConfig) fields 119 Table 16 create
41、(UsagePointConfig) fields . 120 Table 17 create(CustomerConfig) fields 123 Table 18 create(CustomerAccountConfig) fields . 125 Table 19 create(CustomerAgreementConfig) fields . 126 Table 20 create(PricingStructureConfig) fields 128 Table 21 create(MasterDataLinkageConfig) fields, example 1 . 129 Tab
42、le 22 create(MasterDataLinkageConfig) fields, example 2 . 131 Table 23 execute(OperationSet) Header and Payload fields, example 1 132 Table 24 execute(OperationSet) Header and Payload fields, example 2 135 Table 25 execute(OperationSet) Header and Payload fields, example 3 139 PD IEC/TR 61968-900:20
43、15 8 IEC TR 61968-900:2015 IEC 2015 INTERNATIONAL ELECTROTECHNICAL COMMISSION _ APPLICATION INTEGRATION AT ELECTRIC UTILITIES SYSTEM INTERFACES FOR DISTRIBUTION MANAGEMENT Part 900: Guidance for implementation of IEC 61968-9 FOREWORD 1) The International Electrotechnical Commission (IEC) is a worldw
44、ide organization for standardization comprising all national electrotechnical committees (IEC National Committees). The object of IEC is to promote international co-operation on all questions concerning standardization in the electrical and electronic fields. To this end and in addition to other act
45、ivities, IEC publishes International Standards, Technical Specifications, Technical Reports, Publicly Available Specifications (PAS) and Guides (hereafter referred to as “IEC Publication(s)”). Their preparation is entrusted to technical committees; any IEC National Committee interested in the subjec
46、t dealt with may participate in this preparatory work. International, governmental and non-governmental organizations liaising with the IEC also participate in this preparation. IEC collaborates closely with the International Organization for Standardization (ISO) in accordance with conditions deter
47、mined by agreement between the two organizations. 2) The formal decisions or agreements of IEC on technical matters express, as nearly as possible, an international consensus of opinion on the relevant subjects since each technical committee has representation from all interested IEC National Commit
48、tees. 3) IEC Publications have the form of recommendations for international use and are accepted by IEC National Committees in that sense. While all reasonable efforts are made to ensure that the technical content of IEC Publications is accurate, IEC cannot be held responsible for the way in which
49、they are used or for any misinterpretation by any end user. 4) In order to promote international uniformity, IEC National Committees undertake to apply IEC Publications transparently to the maximum extent possible in their national and regional publications. Any divergence between any IEC Publication and the corresponding national or
