🔥🔥 Don’t Miss Out on Our End of Autumn Sale. If you have any questions, feel free to click the bottom right corner to contact our customer service..

Concat us[email protected]
Shopping Cart

No products in the cart.

🔍
BS EN IEC 61968-100:2022

BS EN IEC 61968-100:2022

$215.11

Application integration at electric utilities. System interfaces for distribution management – IEC Implementation profiles for application integration

Published By Publication Date Number of Pages
BSI 2022 254
PDF Format Searchable Printable Preview Now
Guaranteed Safe Checkout
Category:

If you have any questions, feel free to reach out to our online customer service team by clicking on the bottom right corner. We’re here to assist you 24/7.
Email:[email protected]

1.1 General This International Standard is Part 100 of IEC 61968. It defines how messages may be exchanged between co-operating systems in order to facilitate the transfer of application-specific data. Such application-specific data include but are not limited to the message payloads defined in IEC 61968 (Parts 3-9 and Part 13), IEC 61970 and IEC 62325. 1.2 About This International Standard This International Standard provides normative definitions for: – a set of message archetypes (clause 5); – a set of message exchange patterns that both sending and receiving systems are expected to implement (clause 6); – the exact format of the messages that are to be transmitted over the various integration technologies including a precise description of the information that each message must contain (clause 7); – a set of constraints and conventions to which applications must adhere in order to facilitate message exchange using IEC 61968-100 (clause 8); – the details of how IEC 61968-100 messages should be implemented using various underlying transport mechanisms (clause 9). 1.3 What is not covered by this International Standard Security considerations lie outside the scope of IEC 61968-100. This document defers to the IEC 62351 series for definitions and practices relating to the secure transmission of messages. 1.4 Future Considerations 1.4.1 Choice of Encoding Mechanisms IEC 61968-100:2021 prescribes XML as the normative encoding mechanism for all messages defined by this International Standard. Future editions of IEC 61968-100 may specify additional normative encoding methods including support for IEC 62361-104. The latter defines encodings to facilitate the exchange of information in the form of JSON documents whose semantics are defined by the IEC CIM and whose syntax is defined by an IETF JSON schema. 1.4.2 Choice of Web Service Technologies IEC 61968-100:2021 provides normative definitions for the use of SOAP Web Services (clause 9.2) and Java Messaging Service (clause 9.3) for the transport of messages. Future editions of IEC 61968-100 may specify additional normative web service technologies such as REST.

PDF Catalog

PDF Pages PDF Title
2 undefined
5 Annex ZA (normative)Normative references to international publicationswith their corresponding European publications
8 English
CONTENTS
20 FOREWORD
22 INTRODUCTION
23 1 Scope
1.1 General
1.2 About this document
1.3 What is not covered by this document
1.4 Future considerations
1.4.1 Choice of Encoding Mechanisms
1.4.2 Choice of Web Service Technologies
24 2 Normative references
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions
25 3.2 Abbreviated terms
4 Overview
4.1 General
4.2 Message format
26 4.3 Profiles
4.4 Message archetypes
4.5 Header verb and noun
27 4.6 Example IEC 61968-100 messages
4.7 Message exchange patterns
4.7.1 General
4.7.2 Request/response message exchange pattern
4.7.3 Unsolicited event message exchange pattern
28 4.7.4 Consequential event message exchange pattern
4.8 Basic request/response message types
29 5 Message archetypes
5.1 General
5.2 Request message
5.2.1 General
5.2.2 Root element
5.2.3 Structure
30 5.2.4 Header element
5.2.5 Application-specific data
5.2.6 Side-effects of a request message
5.3 Response message
5.3.1 General
5.3.2 Root element
5.3.3 Structure
Figures
Figure 1 – Structure of a request message
31 5.3.4 Header element
5.3.5 Application-specific data and status notifications
5.3.6 Simple acknowledgement message
Figure 2 – Structure of a ResponseMessage
32 5.4 Event message
5.4.1 General
5.4.2 Root element
5.4.3 Structure
5.4.4 Header element
5.4.5 Application-specific data
Figure 3 – Structure of an EventMessage
33 5.5 Fault message
5.5.1 General
5.5.2 Root element
5.5.3 Structure
5.5.4 Reply element
6 Elementary message exchange patterns
6.1 General
6.2 Request/response message exchange pattern
6.2.1 General
Figure 4 – Structure of a FaultMessage
34 6.2.2 Response messages
Figure 5 – Request/response message exchange pattern
35 6.3 Unsolicited event message exchange pattern
6.4 Consequential event message exchange pattern
Figure 6 – Unsolicited event message exchange pattern
36 6.5 Simple acknowledgement message exchange patterns
6.5.1 General
Figure 7 – Consequential event message exchange pattern
37 6.5.2 Request/response message exchange pattern with simple acknowledgement messages
Figure 8 – Request/response message exchange patternwith simple acknowledgement messages
38 6.5.3 Unsolicited event message exchange pattern with simple acknowledgement message
6.5.4 Consequential event message exchange pattern with simple acknowledgement messages
Figure 9 – Unsolicited message exchange patternwith simple acknowledgement messages
39 7 Message details
7.1 General
Figure 10 – Consequential event message exchange pattern with simple acknowledgement messages
40 7.2 Message encoding
7.3 Schema definition and validation
7.4 Top-level structure
7.4.1 General
7.4.2 Structure of request messages
Tables
Table 1 – List of top-level root elements in request messages
41 Figure 11 – Structure of the element
Figure 12 – Structure of the element
Figure 13 – Structure of the element
42 Figure 14 – Structure of the element
Figure 15 – Structure of the element
Figure 16 – Structure of the element
43 7.4.3 Structure of response messages
Figure 17 – Structure of the element
Figure 18 – Structure of the element
Table 2 – List of top-level root elements in response messages
44 Figure 19 – Structure of the element
Figure 20 – Structure of the element
Figure 21 – Structure of the element
45 7.4.4 Structure of event messages
Figure 22 – Structure of the element
Figure 23 – Structure of the element
Figure 24 – Structure of the element
46 Figure 25 – Structure of the element
Figure 26 – Structure of the element
Table 3 – List of top-level root elements in event messages
47 Figure 27 – Structure of the element
Figure 28 – Structure of the element
Figure 29 – Structure of the element
48 7.5 The
element
7.5.1 General
7.5.2 Message header subelements
Figure 30 – Structure of the element
Table 4 – Elements in the Message
element
50 7.5.3 Message header for request messages
51 Figure 31 – Structure of the
element for request messages
Table 5 – Verbs used in request messages
52 7.5.4 Message header for response messages
53 Figure 32 – Structure of the
element for response messages
54 7.5.5 Message header for event messages
55 Figure 33 – Structure of the
element for event messages
Table 6 – Verbs used in event messages
56 7.6 The element
7.6.1 General
57 7.6.2 Structure
7.6.3 Reply subelements
7.6.4 The subelement
Figure 34 – Structure of the element
Table 7 – Subelements within the element
58 Figure 35 – Structure of the element
59 Table 8 – Subelements within the element
60 Table 9 – Values of the element
Table 10 – Normative values for the element
64 7.6.5 Combining the , , and elements
Figure 36 – Example of error indications in a element
65 7.6.6 The element
7.7 The element
7.7.1 General
7.7.2 Payload subelements
66 7.7.3 The element
Table 11 – Subelements within the element
67 Figure 37 – Structure of the element for request messages
Table 12 – Subelements within the element
68 Figure 38 – Structure of the elementfor response messages
Figure 39 – Structure of the element for event messages
69 Table 13 – Subelements within the element
70 Figure 40 – Structure of the elementfor request messages
71 Figure 41 – Structure of the elementfor response messages
72 7.7.4 The element
Figure 42 – Structure of the elementfor event messages
73 Figure 43 – Structure of the element
Table 14 – Subelements within the element
74 7.7.5 AbstractPayloadType data
7.7.6 Multiple abstract payloads
7.8 The element
7.8.1 General
7.8.2 Structure
Table 15 – Subelements within the element
75 7.8.3 CompressedPayload elements
7.8.4 The subelement
7.8.5 The subelement
7.9 The Transaction Type
Figure 44 – Structure of the element
Table 16 – Subelements within the element
Table 17 – Values of the element
76 8 Constraints and conventions
8.1 General
8.2 Application-specific data
8.2.1 General
Figure 45 – Structure of the TransactionType
Table 18 – Elements of a transaction type
77 8.2.2 The AbstractPayloadType
8.2.3 Application-specific customisation
8.2.4 RDF data
8.3 Object management requests and notifications
8.3.1 General
78 8.3.2 Create request message
8.3.3 Change request message
79 8.3.4 Delete request message
8.3.5 Update request message
80 8.3.6 Object management notifications
8.4 Get requests
8.4.1 Making a get request
81 8.4.2 Specifying multiple constraints in a request message
82 8.4.3 Responding to a get request
8.5 Cancelling transactions
8.5.1 General
8.5.2 Message exchange pattern
83 8.5.3 Transactions IDs
Figure 46 – Message Exchange Pattern for a Cancellation Request
84 8.5.4 Receiving a transaction ID
8.5.5 Sending a cancellation request message
8.5.6 Responding to a cancellation request message
8.6 Object identification
8.6.1 General
85 8.6.2 Rules for object identification
8.6.3 Identifying objects using an element
8.6.4 Identifying objects using a element
86 8.6.5 Referencing objects
Figure 47 – General Naming Scheme
Figure 48 – Structure of an element
87 8.7 The ObjectIdentificationRevisionSets profile
8.7.1 General
8.7.2 Structure
Table 19 – Subelements within an element
88 Figure 49 – ObjectIdentificationRevisionSets profile
89 8.7.3 Using the ObjectIdentificationRevisionSets profile
8.7.4 Adding one or more new identifiers
Table 20 – Elements of an ObjectIdentificationRevisionSets profile
90 8.7.5 Removing one or more identifiers
8.7.6 Possible Errors Pertaining To ObjectIdentificationRevisionSets Requests
9 Transporting messages
9.1 General
91 9.2 Transporting over SOAP web services
9.2.1 General
9.2.2 Encoding of IEC 61968-100 messages inside SOAP messages
9.2.3 Example SOAP message
9.2.4 Mapping of IEC 61968-100 messages to SOAP messages
Figure 50 – Example SOAP message
92 9.2.5 WSDL files
Table 21 – Generic WSDL template variable names
93 9.3 Transporting over JMS
9.3.1 General
Table 22 – Strongly-typed message XSD template variable names
Table 23 – Strongly-typed WSDL template variable names
94 9.3.2 Message exchange patterns
9.3.3 Application-level acknowledgement messages
9.3.4 JMS headers
96 Annex A (normative)XSD files
A.1 General
A.2 The Message.xsd file
108 A.3 The AbstractPayloadType.xsd file
Figure A.1 – Contents of Message.xsd file
Figure A.2 – Contents of AbstractPayloadType.xsd file
109 A.4 The LegacyObjectIdentificationRevisionSets.xsd File
114 A.5 The RDF.xsd file
Figure A.3 – Contents of LegacyObjectIdentificationRevisionSets.xsd file
115 Figure A.4 – Contents of the RDF.xsd file
116 Annex B (normative)Template files
B.1 General
B.2 The GenericMessageWsdlTemplate.txt file
121 Figure B.1 – Contents of GenericMessageXsdTemplate.txt file
122 B.3 The StrongMessageXsdTemplate.txt file
134 B.4 The StrongMessageWsdlTemplate.txt file
Figure B.2 – Contents of StrongMessageXsdTemplate.txt file
140 Figure B.3 – Contents of StrongMessageWsdlTemplate.txt file
141 Annex C (informative)Example XSD profiles inheriting from AbstractPayloadType
C.1 GetMeterReadings profile
142 C.2 BinaryData profile
Figure C.1 – Example XSD profile illustrating inheritance from AbstractPayloadType
143 Figure C.2 – Example XSD profile suitable for the transmission of binary data
144 Annex D (informative)Example IEC 61968-100:2021 messages
D.1 General
D.2 Messages dealing with object instantiation
D.2.1 General
D.2.2 Sequence diagram
145 D.2.3 Meter instantiation request (request message)
Figure D.1 – Example sequence diagram for a meter instantiation request
147 D.2.4 Meter instantiation response (step 4, success case)
D.2.5 Meter instantiation response (step 4, failure case)
Figure D.2 – Example meter instantiation request message
Figure D.3 – Example meter instantiation response message (success case)
Figure D.4 – Example meter instantiation response message (failure case)
148 D.3 Messages dealing with the event notification of object instantiation
D.3.1 General
D.3.2 Sequence diagram
D.3.3 Publication of a meter instantiation (event message)
Figure D.5 – Example sequence diagram for the publication of a meter instantiation
152 D.3.4 Publication of a meter instantiation (simple acknowledgement message)
D.4 Messages dealing with requests for information concerning an object instantiation
D.4.1 General
D.4.2 Sequence diagram
Figure D.6 – Example publication of a meter instantiation (event message)
Figure D.7 – Example publication of a meter instantiaion (simple acknowledgement message)
153 D.4.3 Request for information concerning a meter instantiation (request message)
Figure D.8 – Example sequence diagram for requests for information concerning an object instantiation
154 D.4.4 Request for information concerning a meter instantiation (response message)
Figure D.9 – Example request for information concerning a meter instantiation (request message)
155 D.5 Messages utilizing an operationset to enforce transactional integrity
D.5.1 General
D.5.2 Sequence diagram
Figure D.10 – Example request for information concerning a meter instantiation (response message)
156 D.5.3 Using an operationset to enforce transactional integrity (request message)
Figure D.11 – Example sequence diagram for an OperationSet request
159 D.5.4 Using an operationset to enforce transactional integrity (response message)
D.6 Messages dealing with the publication of data
D.6.1 General
D.6.2 Sequence diagram
Figure D.12 – Example OperationSet message to enforce transactional integrity (request message)
Figure D.13 – Example OperationSet message to enforce transactional integrity (response message)
160 D.6.3 Publication of meter readings (event message)
Figure D.14 – Example sequence diagram for the publication of meter readings
161 D.6.4 Publication of meter readings (simple acknowledgement message)
Figure D.15 – Example publication of routine meter readings (event message)
162 D.7 Messages dealing with an on-demand data request resulting in a single response
D.7.1 General
D.7.2 Sequence Diagram
Figure D.16 – Example publication of routine meter readings (simple acknowledgement message)
163 D.7.3 On-demand meter reading message (request message)
Figure D.17 – Example sequence diagram for the retrieval of on-demand meter readings
164 D.7.4 On-demand meter reading message (response message)
Figure D.18 – Example on-demand meter readings request message
165 D.8 Messages dealing with an on-demand data request resulting in multiple responses
D.8.1 General
D.8.2 Sequence diagram
Figure D.19 – Example on-demand meter readings response message
166 D.8.3 Request for an on-demand meter ping (request message)
Figure D.20 – Example sequence diagram for an on-demand meter ping request
167 D.8.4 Request for an on-demand meter ping (response message 1)
Figure D.21 – Example on-demand meter ping request (request message)
168 D.8.5 Request for an on-demand meter ping (response message 2)
Figure D.22 – Example on-demand meter ping request (response message)
169 D.8.6 Request for an on-demand meter ping (simple acknowledgement of message 2)
Figure D.23 – Example on-demand meter ping request (response message 2)
170 D.8.7 Request for an on-demand meter ping (response message 3)
Figure D.24 – Example on-demand meter ping request (simple acknowledgement message 2)
Figure D.25 – Example on-demand meter ping request (response message 3)
171 D.8.8 Request for an on-demand meter ping (simple acknowledgement of message 3)
D.9 Messages dealing with historical data request
D.9.1 General
D.9.2 Sequence diagram
Figure D.26 – Example on-demand meter ping request (simple acknowledgement message 3)
172 D.9.3 Historical meter read (request message)
Figure D.27 – Example sequence diagram for the retrieval of historical meter readings
173 D.9.4 Historical meter read (response message)
Figure D.28 – Example historical meter read request (request message)
174 D.10 Messages dealing with historical data request (responses spread over several messages)
D.10.1 General
Figure D.29 – Example historical meter read request (response message)
175 D.10.2 Historical meter read (response message 1 of 4)
D.10.3 Historical meter read (response message 2 of 4)
Figure D.30 – Example historical meter read request (response message 1 of 4)
176 D.10.4 Historical meter read (response message 3 of 4)
Figure D.31 – Example historical meter read request (response message 2 of 4)
177 D.10.5 Historical meter read (response message 4 of 4)
Figure D.32 – Example historical meter read request (response message 3 of 4)
178 D.11 Messages dealing with multiple statuses within a response
D.11.1 General
Figure D.33 – Example historical meter read request (response message 4 of 4)
179 D.11.2 Sequence diagram
Figure D.34 – Example sequence diagram for the retrieval of historical meter readings (request message)
180 D.11.3 Historical meter read (response message)
Figure D.35 – Example historical meter read request, mixedsuccess and failure cases (request message)
182 D.12 Messages dealing with a consequential event message
D.12.1 General
D.12.2 Sequence diagram
Figure D.36 – Example historical meter read request, mixed success and failure cases (response message)
183 D.12.3 Request for a meter connect (request message)
Figure D.37 – Example sequence diagram for the requesting a meter connect
184 D.12.4 Request for a meter connect (response message)
Figure D.38 – Example meter connect (request message)
185 D.12.5 Request for a meter connect (event message)
Figure D.39 – Example meter connect (response message)
186 D.12.6 Request for a meter connect (simple acknowledgement message)
D.13 Using two operationsets to sequence multiple operations with transactional integrity
D.13.1 General
Figure D.40 – Example meter connect (event message)
Figure D.41 – Example meter connect (simple acknowledgement message)
187 D.13.2 Using two OperationSets to read two meters before disconnecting them (request message)
188 D.13.3 Using two OperationSets to read two meters before disconnecting them (response message)
Figure D.42 – Using two OperationSets to read two meters before disconnecting them (request message)
189 Figure D.43 – Using two OperationSets to Read two meters before disconnecting them (response message)
190 D.14 Messages dealing with object deletion
D.14.1 General
D.14.2 Sequence diagram
Figure D.44 – Example sequence diagram for the deletion of a meter
191 D.14.3 Request to delete a meter (request message)
D.14.4 Request to delete a meter (response message)
D.15 Messages dealing with cancellation of a single transaction
D.15.1 Meter control request message
Figure D.45 – Example meter deletion (request message)
Figure D.46 – Example meter deletion (response message)
192 D.15.2 Response message containing a single transaction id
Figure D.47 – Example create(EndDeviceControls) request message
193 D.15.3 Cancellation request (request message)
D.15.4 Cancellation request (response message)
Figure D.48 – Example response message containing a single transaction ID
Figure D.49 – Example cancellation request message
194 D.16 Messages dealing with cancellation of multiple transactions
D.16.1 Response message containing multiple transaction IDs
Figure D.50 – Example response to a cancellation request message
195 D.16.2 Cancellation request (request message)
Figure D.51 – Example response message containing several transaction IDs
196 D.16.3 Cancellation request (response message)
D.17 Messages dealing with failed XSD validation
D.17.1 General
Figure D.52 – Example cancellation request message
Figure D.53 – Example response to a cancellation request message
197 D.17.2 Message that fails XSD validation (request message)
D.17.3 Message that fails XSD validation (response message)
Figure D.54 – Example message that fails XSD validation (request message)
198 D.18 Messages dealing with malformed requests
D.18.1 General
D.18.2 Message that is malformed (request message)
Figure D.55 – Example message that fails XSD validation (response message)
Figure D.56 – Example malformed message (request message)
199 D.18.3 Message that is malformed (response message)
Figure D.57 – Example malformed message (response message)
200 Annex E (informative)Example IEC 61968-100:2021 messages for updating objects
E.1 General
E.2 CreateMeterConfig.xml
201 E.3 ModifyFormNumber.xml
Figure E.1 – CreateMeterConfig.xml
202 E.4 RemoveFormNumber.xml
E.5 AddMeterMultiplier.xml
Figure E.2 – ModifyFormNumber.xml
Figure E.3 – RemoveFormNumber.xml
203 E.6 ModifyMeterMultiplierKind.xml
Figure E.4 – AddMeterMultiplier.xml
204 E.7 ModifyMeterMultiplierValue.xml
Figure E.5 – ModifyMeterMultiplierKind.xml
205 E.8 RemoveMeterMultiplierValue.xml
Figure E.6 – ModifyMeterMultiplierValue.xml
206 E.9 RemoveMeterMultiplier.xml
Figure E.7 – RemoveMeterMultiplierValue.xml
Figure E.8 – RemoveMeterMultiplier.xml
207 E.10 AddMeterSeal.xml
E.11 AddMeterSealKind.xml
Figure E.9 – AddMeterSeal.xml
208 E.12 ModifyMeterSealCondition.xml
Figure E.10 – AddMeterSealKind.xml
209 E.13 RemoveMeterSealCondition.xml
Figure E.11 – ModifyMeterSealCondition.xml
210 E.14 RemoveMeterSeal.xml
Figure E.12 – RemoveMeterDealCondition.xml
Figure E.13 – RemoveMeterSeal.xml
211 E.15 ModifyProgramId.xml
E.16 RemoveProgramId.xml
Figure E.14 – ModifyProgramId.xml
212 E.17 AddChannel.xml
Figure E.15 – RemoveProgramId.xml
213 E.18 ModifyChannelReadingType.xml
Figure E.16 – AddChannelId.xml
214 E.19 RemoveChannel.xml
Figure E.17 – ModifyChannelReadingType.xml
215 E.20 AddConnectDisconnectFunction.xml
Figure E.18 – RemoveChannel.xml
216 E.21 RemoveConnectDisconnectFunction.xml
Figure E.19 – AddConnectDisconnectFunction.xml
217 E.22 DeleteMeterConfig.xml
E.23 DeleteMeterConfig.xml
Figure E.20 – RemoveConnectDisconnectFunction.xml
Figure E.21 – DeleteMeterConfig.xml
218 E.24 CreateMeterConfigs.xml
Figure E.22 – DeleteMeterConfig.xml
220 E.25 MultipleObjectChanges.xml
Figure E.23 – CreateMeterConfigs.xml
222 E.26 MultipleObjectChangesWithOperationSet.xml
Figure E.24 – MultipleObjectChanges.xml
225 Figure E.25 – MultipleObjectChangesWithOperationSet.xml
226 Annex F (informative)Examples of ObjectIdentificationRevisionSets Messages
F.1 General
F.2 Add an mRID for the meter object
Table F.1 – Initial naming states of the example meter object
Table F.2 – Initial naming states of the example customer object
227 Figure F.1 – Add an mRID for the Meter Object
Table F.3 – Add an mRID for the meter object
228 F.3 Modify name two of the meter object
Table F.4 – Modify name two of the meter object
229 F.4 Add name three of the meter object
Figure F.2 – Modify name two of the meter object
230 Figure F.3 – Add name three of the meter object
Table F.5 – Add name three of the meter object
231 F.5 Remove Name One of the Meter Object
Table F.6 – Remove name one of the meter object
232 F.6 Modify the mRID of the meter object
Figure F.4 – Remove name one of the meter object
233 Figure F.5 – Modify the mRID of the meter object
Table F.7 – Modify the mRID of the meter object
234 F.7 Remove the mRID of the meter object
Figure F.6 – Remove the mRID of the meter object
Table F.8 – Remove the mRID of the meter object
235 F.8 Add an mRID and modify name two of the meter object
Table F.9 – Add an mRID and modify name two of the meter object
236 F.9 Modify name two of the meter object and add name one of the customer object
Figure F.7 – Add an mRID and modify name two of the meter object
237 Table F.10 – Modify name two of the meter object
Table F.11 – Add name one of the customer object
238 Figure F.8 – Add name one of the customer object and modify name two of the meter object
239 F.10 Add name two of the customer object to carry a new IdentifiedObject.name
Table F.12 – Add name two of the customer object to carry a new IdentifiedObject.name
240 Figure F.9 – Add name two of the customer object to carry a new IdentifiedObject.name
241 Annex G (informative)Example IEC 61968-100:2021 messages illustrating the cross-product rule
G.1 General
G.2 Specifying “OR” operations over the selection criteria
G.3 Specifying “AND” operations over the selection criteria
Figure G.1 – Example get(MeterConfig) request illustrating a logical “OR” operation
242 G.4 Specifying a combination of logical “AND” and “OR” operations
Figure G.2 – Example get(MeterReadings) request illustrating a logical “AND” operation
243 G.5 Example of multiple AbstractPayloadType profiles in a single message
Figure G.3 – Example request message illustrating combined logical “AND” and “OR” operations
244 Figure G.4 – Example of multiple AbstractPayloadType profiles in a single message
245 Annex H (informative)Validation of received messages
H.1 General
H.2 Example message validation using Altova XMLSpy
246 H.3 Example message validation using a Java validator
Figure H.1 – Example message suitably modified to specify the locations of the relevant XSD files
Figure H.2 – Example of local modifications made to the Message.xsd file
247 Annex I (informative)Significant changes between IEC 61968-100:2013 and IEC 61968-100:2021
248 Table I.1 – Significant changes introduced in IEC 61968-100:2021 since IEC 61968-100:2013
249 Table I.2 – Detailed changes introduced from IEC 61968-100:2013 to IEC 61968-100:2021
250 Table I.3 – Elements removed from IEC 61968-100:2013
253 Bibliography

Related products

BS EN IEC 61968-100:2022
$215.11