{"id":402366,"date":"2024-10-20T05:00:51","date_gmt":"2024-10-20T05:00:51","guid":{"rendered":"https:\/\/pdfstandards.shop\/product\/uncategorized\/bs-en-iec-61968-1002022\/"},"modified":"2024-10-26T08:54:52","modified_gmt":"2024-10-26T08:54:52","slug":"bs-en-iec-61968-1002022","status":"publish","type":"product","link":"https:\/\/pdfstandards.shop\/product\/publishers\/bsi\/bs-en-iec-61968-1002022\/","title":{"rendered":"BS EN IEC 61968-100:2022"},"content":{"rendered":"

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.<\/p>\n

PDF Catalog<\/h4>\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n\n
PDF Pages<\/th>\nPDF Title<\/th>\n<\/tr>\n
2<\/td>\nundefined <\/td>\n<\/tr>\n
5<\/td>\nAnnex ZA (normative)Normative references to international publicationswith their corresponding European publications <\/td>\n<\/tr>\n
8<\/td>\nEnglish
CONTENTS <\/td>\n<\/tr>\n
20<\/td>\nFOREWORD <\/td>\n<\/tr>\n
22<\/td>\nINTRODUCTION <\/td>\n<\/tr>\n
23<\/td>\n1 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 <\/td>\n<\/tr>\n
24<\/td>\n2 Normative references
3 Terms, definitions and abbreviated terms
3.1 Terms and definitions <\/td>\n<\/tr>\n
25<\/td>\n3.2 Abbreviated terms
4 Overview
4.1 General
4.2 Message format <\/td>\n<\/tr>\n
26<\/td>\n4.3 Profiles
4.4 Message archetypes
4.5 Header verb and noun <\/td>\n<\/tr>\n
27<\/td>\n4.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 <\/td>\n<\/tr>\n
28<\/td>\n4.7.4 Consequential event message exchange pattern
4.8 Basic request\/response message types <\/td>\n<\/tr>\n
29<\/td>\n5 Message archetypes
5.1 General
5.2 Request message
5.2.1 General
5.2.2 Root element
5.2.3 Structure <\/td>\n<\/tr>\n
30<\/td>\n5.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 \u2013 Structure of a request message <\/td>\n<\/tr>\n
31<\/td>\n5.3.4 Header element
5.3.5 Application-specific data and status notifications
5.3.6 Simple acknowledgement message
Figure 2 \u2013 Structure of a ResponseMessage <\/td>\n<\/tr>\n
32<\/td>\n5.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 \u2013 Structure of an EventMessage <\/td>\n<\/tr>\n
33<\/td>\n5.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 \u2013 Structure of a FaultMessage <\/td>\n<\/tr>\n
34<\/td>\n6.2.2 Response messages
Figure 5 \u2013 Request\/response message exchange pattern <\/td>\n<\/tr>\n
35<\/td>\n6.3 Unsolicited event message exchange pattern
6.4 Consequential event message exchange pattern
Figure 6 \u2013 Unsolicited event message exchange pattern <\/td>\n<\/tr>\n
36<\/td>\n6.5 Simple acknowledgement message exchange patterns
6.5.1 General
Figure 7 \u2013 Consequential event message exchange pattern <\/td>\n<\/tr>\n
37<\/td>\n6.5.2 Request\/response message exchange pattern with simple acknowledgement messages
Figure 8 \u2013 Request\/response message exchange patternwith simple acknowledgement messages <\/td>\n<\/tr>\n
38<\/td>\n6.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 \u2013 Unsolicited message exchange patternwith simple acknowledgement messages <\/td>\n<\/tr>\n
39<\/td>\n7 Message details
7.1 General
Figure 10 \u2013 Consequential event message exchange pattern with simple acknowledgement messages <\/td>\n<\/tr>\n
40<\/td>\n7.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 \u2013 List of top-level root elements in request messages <\/td>\n<\/tr>\n
41<\/td>\nFigure 11 \u2013 Structure of the element
Figure 12 \u2013 Structure of the element
Figure 13 \u2013 Structure of the element <\/td>\n<\/tr>\n
42<\/td>\nFigure 14 \u2013 Structure of the element
Figure 15 \u2013 Structure of the element
Figure 16 \u2013 Structure of the element <\/td>\n<\/tr>\n
43<\/td>\n7.4.3 Structure of response messages
Figure 17 \u2013 Structure of the element
Figure 18 \u2013 Structure of the element
Table 2 \u2013 List of top-level root elements in response messages <\/td>\n<\/tr>\n
44<\/td>\nFigure 19 \u2013 Structure of the element
Figure 20 \u2013 Structure of the element
Figure 21 \u2013 Structure of the element <\/td>\n<\/tr>\n
45<\/td>\n7.4.4 Structure of event messages
Figure 22 \u2013 Structure of the element
Figure 23 \u2013 Structure of the element
Figure 24 \u2013 Structure of the element <\/td>\n<\/tr>\n
46<\/td>\nFigure 25 \u2013 Structure of the element
Figure 26 \u2013 Structure of the element
Table 3 \u2013 List of top-level root elements in event messages <\/td>\n<\/tr>\n
47<\/td>\nFigure 27 \u2013 Structure of the element
Figure 28 \u2013 Structure of the element
Figure 29 \u2013 Structure of the element <\/td>\n<\/tr>\n
48<\/td>\n7.5 The
element
7.5.1 General
7.5.2 Message header subelements
Figure 30 \u2013 Structure of the element
Table 4 \u2013 Elements in the Message
element <\/td>\n<\/tr>\n
50<\/td>\n7.5.3 Message header for request messages <\/td>\n<\/tr>\n
51<\/td>\nFigure 31 \u2013 Structure of the
element for request messages
Table 5 \u2013 Verbs used in request messages <\/td>\n<\/tr>\n
52<\/td>\n7.5.4 Message header for response messages <\/td>\n<\/tr>\n
53<\/td>\nFigure 32 \u2013 Structure of the
element for response messages <\/td>\n<\/tr>\n
54<\/td>\n7.5.5 Message header for event messages <\/td>\n<\/tr>\n
55<\/td>\nFigure 33 \u2013 Structure of the
element for event messages
Table 6 \u2013 Verbs used in event messages <\/td>\n<\/tr>\n
56<\/td>\n7.6 The element
7.6.1 General <\/td>\n<\/tr>\n
57<\/td>\n7.6.2 Structure
7.6.3 Reply subelements
7.6.4 The subelement
Figure 34 \u2013 Structure of the element
Table 7 \u2013 Subelements within the element <\/td>\n<\/tr>\n
58<\/td>\nFigure 35 \u2013 Structure of the element <\/td>\n<\/tr>\n
59<\/td>\nTable 8 \u2013 Subelements within the element <\/td>\n<\/tr>\n
60<\/td>\nTable 9 \u2013 Values of the element
Table 10 \u2013 Normative values for the element <\/td>\n<\/tr>\n
64<\/td>\n7.6.5 Combining the , , and elements
Figure 36 \u2013 Example of error indications in a element <\/td>\n<\/tr>\n
65<\/td>\n7.6.6 The element
7.7 The element
7.7.1 General
7.7.2 Payload subelements <\/td>\n<\/tr>\n
66<\/td>\n7.7.3 The element
Table 11 \u2013 Subelements within the element <\/td>\n<\/tr>\n
67<\/td>\nFigure 37 \u2013 Structure of the element for request messages
Table 12 \u2013 Subelements within the element <\/td>\n<\/tr>\n
68<\/td>\nFigure 38 \u2013 Structure of the elementfor response messages
Figure 39 \u2013 Structure of the element for event messages <\/td>\n<\/tr>\n
69<\/td>\nTable 13 \u2013 Subelements within the element <\/td>\n<\/tr>\n
70<\/td>\nFigure 40 \u2013 Structure of the elementfor request messages <\/td>\n<\/tr>\n
71<\/td>\nFigure 41 \u2013 Structure of the elementfor response messages <\/td>\n<\/tr>\n
72<\/td>\n7.7.4 The element
Figure 42 \u2013 Structure of the elementfor event messages <\/td>\n<\/tr>\n
73<\/td>\nFigure 43 \u2013 Structure of the element
Table 14 \u2013 Subelements within the element <\/td>\n<\/tr>\n
74<\/td>\n7.7.5 AbstractPayloadType data
7.7.6 Multiple abstract payloads
7.8 The element
7.8.1 General
7.8.2 Structure
Table 15 \u2013 Subelements within the element <\/td>\n<\/tr>\n
75<\/td>\n7.8.3 CompressedPayload elements
7.8.4 The subelement
7.8.5 The subelement
7.9 The Transaction Type
Figure 44 \u2013 Structure of the element
Table 16 \u2013 Subelements within the element
Table 17 \u2013 Values of the element <\/td>\n<\/tr>\n
76<\/td>\n8 Constraints and conventions
8.1 General
8.2 Application-specific data
8.2.1 General
Figure 45 \u2013 Structure of the TransactionType
Table 18 \u2013 Elements of a transaction type <\/td>\n<\/tr>\n
77<\/td>\n8.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 <\/td>\n<\/tr>\n
78<\/td>\n8.3.2 Create request message
8.3.3 Change request message <\/td>\n<\/tr>\n
79<\/td>\n8.3.4 Delete request message
8.3.5 Update request message <\/td>\n<\/tr>\n
80<\/td>\n8.3.6 Object management notifications
8.4 Get requests
8.4.1 Making a get request <\/td>\n<\/tr>\n
81<\/td>\n8.4.2 Specifying multiple constraints in a request message <\/td>\n<\/tr>\n
82<\/td>\n8.4.3 Responding to a get request
8.5 Cancelling transactions
8.5.1 General
8.5.2 Message exchange pattern <\/td>\n<\/tr>\n
83<\/td>\n8.5.3 Transactions IDs
Figure 46 \u2013 Message Exchange Pattern for a Cancellation Request <\/td>\n<\/tr>\n
84<\/td>\n8.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 <\/td>\n<\/tr>\n
85<\/td>\n8.6.2 Rules for object identification
8.6.3 Identifying objects using an element
8.6.4 Identifying objects using a element <\/td>\n<\/tr>\n
86<\/td>\n8.6.5 Referencing objects
Figure 47 \u2013 General Naming Scheme
Figure 48 \u2013 Structure of an element <\/td>\n<\/tr>\n
87<\/td>\n8.7 The ObjectIdentificationRevisionSets profile
8.7.1 General
8.7.2 Structure
Table 19 \u2013 Subelements within an element <\/td>\n<\/tr>\n
88<\/td>\nFigure 49 \u2013 ObjectIdentificationRevisionSets profile <\/td>\n<\/tr>\n
89<\/td>\n8.7.3 Using the ObjectIdentificationRevisionSets profile
8.7.4 Adding one or more new identifiers
Table 20 \u2013 Elements of an ObjectIdentificationRevisionSets profile <\/td>\n<\/tr>\n
90<\/td>\n8.7.5 Removing one or more identifiers
8.7.6 Possible Errors Pertaining To ObjectIdentificationRevisionSets Requests
9 Transporting messages
9.1 General <\/td>\n<\/tr>\n
91<\/td>\n9.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 \u2013 Example SOAP message <\/td>\n<\/tr>\n
92<\/td>\n9.2.5 WSDL files
Table 21 \u2013 Generic WSDL template variable names <\/td>\n<\/tr>\n
93<\/td>\n9.3 Transporting over JMS
9.3.1 General
Table 22 \u2013 Strongly-typed message XSD template variable names
Table 23 \u2013 Strongly-typed WSDL template variable names <\/td>\n<\/tr>\n
94<\/td>\n9.3.2 Message exchange patterns
9.3.3 Application-level acknowledgement messages
9.3.4 JMS headers <\/td>\n<\/tr>\n
96<\/td>\nAnnex A (normative)XSD files
A.1 General
A.2 The Message.xsd file <\/td>\n<\/tr>\n
108<\/td>\nA.3 The AbstractPayloadType.xsd file
Figure A.1 \u2013 Contents of Message.xsd file
Figure A.2 \u2013 Contents of AbstractPayloadType.xsd file <\/td>\n<\/tr>\n
109<\/td>\nA.4 The LegacyObjectIdentificationRevisionSets.xsd File <\/td>\n<\/tr>\n
114<\/td>\nA.5 The RDF.xsd file
Figure A.3 \u2013 Contents of LegacyObjectIdentificationRevisionSets.xsd file <\/td>\n<\/tr>\n
115<\/td>\nFigure A.4 \u2013 Contents of the RDF.xsd file <\/td>\n<\/tr>\n
116<\/td>\nAnnex B (normative)Template files
B.1 General
B.2 The GenericMessageWsdlTemplate.txt file <\/td>\n<\/tr>\n
121<\/td>\nFigure B.1 \u2013 Contents of GenericMessageXsdTemplate.txt file <\/td>\n<\/tr>\n
122<\/td>\nB.3 The StrongMessageXsdTemplate.txt file <\/td>\n<\/tr>\n
134<\/td>\nB.4 The StrongMessageWsdlTemplate.txt file
Figure B.2 \u2013 Contents of StrongMessageXsdTemplate.txt file <\/td>\n<\/tr>\n
140<\/td>\nFigure B.3 \u2013 Contents of StrongMessageWsdlTemplate.txt file <\/td>\n<\/tr>\n
141<\/td>\nAnnex C (informative)Example XSD profiles inheriting from AbstractPayloadType
C.1 GetMeterReadings profile <\/td>\n<\/tr>\n
142<\/td>\nC.2 BinaryData profile
Figure C.1 \u2013 Example XSD profile illustrating inheritance from AbstractPayloadType <\/td>\n<\/tr>\n
143<\/td>\nFigure C.2 \u2013 Example XSD profile suitable for the transmission of binary data <\/td>\n<\/tr>\n
144<\/td>\nAnnex 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 <\/td>\n<\/tr>\n
145<\/td>\nD.2.3 Meter instantiation request (request message)
Figure D.1 \u2013 Example sequence diagram for a meter instantiation request <\/td>\n<\/tr>\n
147<\/td>\nD.2.4 Meter instantiation response (step 4, success case)
D.2.5 Meter instantiation response (step 4, failure case)
Figure D.2 \u2013 Example meter instantiation request message
Figure D.3 \u2013 Example meter instantiation response message (success case)
Figure D.4 \u2013 Example meter instantiation response message (failure case) <\/td>\n<\/tr>\n
148<\/td>\nD.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 \u2013 Example sequence diagram for the publication of a meter instantiation <\/td>\n<\/tr>\n
152<\/td>\nD.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 \u2013 Example publication of a meter instantiation (event message)
Figure D.7 \u2013 Example publication of a meter instantiaion (simple acknowledgement message) <\/td>\n<\/tr>\n
153<\/td>\nD.4.3 Request for information concerning a meter instantiation (request message)
Figure D.8 \u2013 Example sequence diagram for requests for information concerning an object instantiation <\/td>\n<\/tr>\n
154<\/td>\nD.4.4 Request for information concerning a meter instantiation (response message)
Figure D.9 \u2013 Example request for information concerning a meter instantiation (request message) <\/td>\n<\/tr>\n
155<\/td>\nD.5 Messages utilizing an operationset to enforce transactional integrity
D.5.1 General
D.5.2 Sequence diagram
Figure D.10 \u2013 Example request for information concerning a meter instantiation (response message) <\/td>\n<\/tr>\n
156<\/td>\nD.5.3 Using an operationset to enforce transactional integrity (request message)
Figure D.11 \u2013 Example sequence diagram for an OperationSet request <\/td>\n<\/tr>\n
159<\/td>\nD.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 \u2013 Example OperationSet message to enforce transactional integrity (request message)
Figure D.13 \u2013 Example OperationSet message to enforce transactional integrity (response message) <\/td>\n<\/tr>\n
160<\/td>\nD.6.3 Publication of meter readings (event message)
Figure D.14 \u2013 Example sequence diagram for the publication of meter readings <\/td>\n<\/tr>\n
161<\/td>\nD.6.4 Publication of meter readings (simple acknowledgement message)
Figure D.15 \u2013 Example publication of routine meter readings (event message) <\/td>\n<\/tr>\n
162<\/td>\nD.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 \u2013 Example publication of routine meter readings (simple acknowledgement message) <\/td>\n<\/tr>\n
163<\/td>\nD.7.3 On-demand meter reading message (request message)
Figure D.17 \u2013 Example sequence diagram for the retrieval of on-demand meter readings <\/td>\n<\/tr>\n
164<\/td>\nD.7.4 On-demand meter reading message (response message)
Figure D.18 \u2013 Example on-demand meter readings request message <\/td>\n<\/tr>\n
165<\/td>\nD.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 \u2013 Example on-demand meter readings response message <\/td>\n<\/tr>\n
166<\/td>\nD.8.3 Request for an on-demand meter ping (request message)
Figure D.20 \u2013 Example sequence diagram for an on-demand meter ping request <\/td>\n<\/tr>\n
167<\/td>\nD.8.4 Request for an on-demand meter ping (response message 1)
Figure D.21 \u2013 Example on-demand meter ping request (request message) <\/td>\n<\/tr>\n
168<\/td>\nD.8.5 Request for an on-demand meter ping (response message 2)
Figure D.22 \u2013 Example on-demand meter ping request (response message) <\/td>\n<\/tr>\n
169<\/td>\nD.8.6 Request for an on-demand meter ping (simple acknowledgement of message 2)
Figure D.23 \u2013 Example on-demand meter ping request (response message 2) <\/td>\n<\/tr>\n
170<\/td>\nD.8.7 Request for an on-demand meter ping (response message 3)
Figure D.24 \u2013 Example on-demand meter ping request (simple acknowledgement message 2)
Figure D.25 \u2013 Example on-demand meter ping request (response message 3) <\/td>\n<\/tr>\n
171<\/td>\nD.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 \u2013 Example on-demand meter ping request (simple acknowledgement message 3) <\/td>\n<\/tr>\n
172<\/td>\nD.9.3 Historical meter read (request message)
Figure D.27 \u2013 Example sequence diagram for the retrieval of historical meter readings <\/td>\n<\/tr>\n
173<\/td>\nD.9.4 Historical meter read (response message)
Figure D.28 \u2013 Example historical meter read request (request message) <\/td>\n<\/tr>\n
174<\/td>\nD.10 Messages dealing with historical data request (responses spread over several messages)
D.10.1 General
Figure D.29 \u2013 Example historical meter read request (response message) <\/td>\n<\/tr>\n
175<\/td>\nD.10.2 Historical meter read (response message 1 of 4)
D.10.3 Historical meter read (response message 2 of 4)
Figure D.30 \u2013 Example historical meter read request (response message 1 of 4) <\/td>\n<\/tr>\n
176<\/td>\nD.10.4 Historical meter read (response message 3 of 4)
Figure D.31 \u2013 Example historical meter read request (response message 2 of 4) <\/td>\n<\/tr>\n
177<\/td>\nD.10.5 Historical meter read (response message 4 of 4)
Figure D.32 \u2013 Example historical meter read request (response message 3 of 4) <\/td>\n<\/tr>\n
178<\/td>\nD.11 Messages dealing with multiple statuses within a response
D.11.1 General
Figure D.33 \u2013 Example historical meter read request (response message 4 of 4) <\/td>\n<\/tr>\n
179<\/td>\nD.11.2 Sequence diagram
Figure D.34 \u2013 Example sequence diagram for the retrieval of historical meter readings (request message) <\/td>\n<\/tr>\n
180<\/td>\nD.11.3 Historical meter read (response message)
Figure D.35 \u2013 Example historical meter read request, mixedsuccess and failure cases (request message) <\/td>\n<\/tr>\n
182<\/td>\nD.12 Messages dealing with a consequential event message
D.12.1 General
D.12.2 Sequence diagram
Figure D.36 \u2013 Example historical meter read request, mixed success and failure cases (response message) <\/td>\n<\/tr>\n
183<\/td>\nD.12.3 Request for a meter connect (request message)
Figure D.37 \u2013 Example sequence diagram for the requesting a meter connect <\/td>\n<\/tr>\n
184<\/td>\nD.12.4 Request for a meter connect (response message)
Figure D.38 \u2013 Example meter connect (request message) <\/td>\n<\/tr>\n
185<\/td>\nD.12.5 Request for a meter connect (event message)
Figure D.39 \u2013 Example meter connect (response message) <\/td>\n<\/tr>\n
186<\/td>\nD.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 \u2013 Example meter connect (event message)
Figure D.41 \u2013 Example meter connect (simple acknowledgement message) <\/td>\n<\/tr>\n
187<\/td>\nD.13.2 Using two OperationSets to read two meters before disconnecting them (request message) <\/td>\n<\/tr>\n
188<\/td>\nD.13.3 Using two OperationSets to read two meters before disconnecting them (response message)
Figure D.42 \u2013 Using two OperationSets to read two meters before disconnecting them (request message) <\/td>\n<\/tr>\n
189<\/td>\nFigure D.43 \u2013 Using two OperationSets to Read two meters before disconnecting them (response message) <\/td>\n<\/tr>\n
190<\/td>\nD.14 Messages dealing with object deletion
D.14.1 General
D.14.2 Sequence diagram
Figure D.44 \u2013 Example sequence diagram for the deletion of a meter <\/td>\n<\/tr>\n
191<\/td>\nD.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 \u2013 Example meter deletion (request message)
Figure D.46 \u2013 Example meter deletion (response message) <\/td>\n<\/tr>\n
192<\/td>\nD.15.2 Response message containing a single transaction id
Figure D.47 \u2013 Example create(EndDeviceControls) request message <\/td>\n<\/tr>\n
193<\/td>\nD.15.3 Cancellation request (request message)
D.15.4 Cancellation request (response message)
Figure D.48 \u2013 Example response message containing a single transaction ID
Figure D.49 \u2013 Example cancellation request message <\/td>\n<\/tr>\n
194<\/td>\nD.16 Messages dealing with cancellation of multiple transactions
D.16.1 Response message containing multiple transaction IDs
Figure D.50 \u2013 Example response to a cancellation request message <\/td>\n<\/tr>\n
195<\/td>\nD.16.2 Cancellation request (request message)
Figure D.51 \u2013 Example response message containing several transaction IDs <\/td>\n<\/tr>\n
196<\/td>\nD.16.3 Cancellation request (response message)
D.17 Messages dealing with failed XSD validation
D.17.1 General
Figure D.52 \u2013 Example cancellation request message
Figure D.53 \u2013 Example response to a cancellation request message <\/td>\n<\/tr>\n
197<\/td>\nD.17.2 Message that fails XSD validation (request message)
D.17.3 Message that fails XSD validation (response message)
Figure D.54 \u2013 Example message that fails XSD validation (request message) <\/td>\n<\/tr>\n
198<\/td>\nD.18 Messages dealing with malformed requests
D.18.1 General
D.18.2 Message that is malformed (request message)
Figure D.55 \u2013 Example message that fails XSD validation (response message)
Figure D.56 \u2013 Example malformed message (request message) <\/td>\n<\/tr>\n
199<\/td>\nD.18.3 Message that is malformed (response message)
Figure D.57 \u2013 Example malformed message (response message) <\/td>\n<\/tr>\n
200<\/td>\nAnnex E (informative)Example IEC 61968-100:2021 messages for updating objects
E.1 General
E.2 CreateMeterConfig.xml <\/td>\n<\/tr>\n
201<\/td>\nE.3 ModifyFormNumber.xml
Figure E.1 \u2013 CreateMeterConfig.xml <\/td>\n<\/tr>\n
202<\/td>\nE.4 RemoveFormNumber.xml
E.5 AddMeterMultiplier.xml
Figure E.2 \u2013 ModifyFormNumber.xml
Figure E.3 \u2013 RemoveFormNumber.xml <\/td>\n<\/tr>\n
203<\/td>\nE.6 ModifyMeterMultiplierKind.xml
Figure E.4 \u2013 AddMeterMultiplier.xml <\/td>\n<\/tr>\n
204<\/td>\nE.7 ModifyMeterMultiplierValue.xml
Figure E.5 \u2013 ModifyMeterMultiplierKind.xml <\/td>\n<\/tr>\n
205<\/td>\nE.8 RemoveMeterMultiplierValue.xml
Figure E.6 \u2013 ModifyMeterMultiplierValue.xml <\/td>\n<\/tr>\n
206<\/td>\nE.9 RemoveMeterMultiplier.xml
Figure E.7 \u2013 RemoveMeterMultiplierValue.xml
Figure E.8 \u2013 RemoveMeterMultiplier.xml <\/td>\n<\/tr>\n
207<\/td>\nE.10 AddMeterSeal.xml
E.11 AddMeterSealKind.xml
Figure E.9 \u2013 AddMeterSeal.xml <\/td>\n<\/tr>\n
208<\/td>\nE.12 ModifyMeterSealCondition.xml
Figure E.10 \u2013 AddMeterSealKind.xml <\/td>\n<\/tr>\n
209<\/td>\nE.13 RemoveMeterSealCondition.xml
Figure E.11 \u2013 ModifyMeterSealCondition.xml <\/td>\n<\/tr>\n
210<\/td>\nE.14 RemoveMeterSeal.xml
Figure E.12 \u2013 RemoveMeterDealCondition.xml
Figure E.13 \u2013 RemoveMeterSeal.xml <\/td>\n<\/tr>\n
211<\/td>\nE.15 ModifyProgramId.xml
E.16 RemoveProgramId.xml
Figure E.14 \u2013 ModifyProgramId.xml <\/td>\n<\/tr>\n
212<\/td>\nE.17 AddChannel.xml
Figure E.15 \u2013 RemoveProgramId.xml <\/td>\n<\/tr>\n
213<\/td>\nE.18 ModifyChannelReadingType.xml
Figure E.16 \u2013 AddChannelId.xml <\/td>\n<\/tr>\n
214<\/td>\nE.19 RemoveChannel.xml
Figure E.17 \u2013 ModifyChannelReadingType.xml <\/td>\n<\/tr>\n
215<\/td>\nE.20 AddConnectDisconnectFunction.xml
Figure E.18 \u2013 RemoveChannel.xml <\/td>\n<\/tr>\n
216<\/td>\nE.21 RemoveConnectDisconnectFunction.xml
Figure E.19 \u2013 AddConnectDisconnectFunction.xml <\/td>\n<\/tr>\n
217<\/td>\nE.22 DeleteMeterConfig.xml
E.23 DeleteMeterConfig.xml
Figure E.20 \u2013 RemoveConnectDisconnectFunction.xml
Figure E.21 \u2013 DeleteMeterConfig.xml <\/td>\n<\/tr>\n
218<\/td>\nE.24 CreateMeterConfigs.xml
Figure E.22 \u2013 DeleteMeterConfig.xml <\/td>\n<\/tr>\n
220<\/td>\nE.25 MultipleObjectChanges.xml
Figure E.23 \u2013 CreateMeterConfigs.xml <\/td>\n<\/tr>\n
222<\/td>\nE.26 MultipleObjectChangesWithOperationSet.xml
Figure E.24 \u2013 MultipleObjectChanges.xml <\/td>\n<\/tr>\n
225<\/td>\nFigure E.25 \u2013 MultipleObjectChangesWithOperationSet.xml <\/td>\n<\/tr>\n
226<\/td>\nAnnex F (informative)Examples of ObjectIdentificationRevisionSets Messages
F.1 General
F.2 Add an mRID for the meter object
Table F.1 \u2013 Initial naming states of the example meter object
Table F.2 \u2013 Initial naming states of the example customer object <\/td>\n<\/tr>\n
227<\/td>\nFigure F.1 \u2013 Add an mRID for the Meter Object
Table F.3 \u2013 Add an mRID for the meter object <\/td>\n<\/tr>\n
228<\/td>\nF.3 Modify name two of the meter object
Table F.4 \u2013 Modify name two of the meter object <\/td>\n<\/tr>\n
229<\/td>\nF.4 Add name three of the meter object
Figure F.2 \u2013 Modify name two of the meter object <\/td>\n<\/tr>\n
230<\/td>\nFigure F.3 \u2013 Add name three of the meter object
Table F.5 \u2013 Add name three of the meter object <\/td>\n<\/tr>\n
231<\/td>\nF.5 Remove Name One of the Meter Object
Table F.6 \u2013 Remove name one of the meter object <\/td>\n<\/tr>\n
232<\/td>\nF.6 Modify the mRID of the meter object
Figure F.4 \u2013 Remove name one of the meter object <\/td>\n<\/tr>\n
233<\/td>\nFigure F.5 \u2013 Modify the mRID of the meter object
Table F.7 \u2013 Modify the mRID of the meter object <\/td>\n<\/tr>\n
234<\/td>\nF.7 Remove the mRID of the meter object
Figure F.6 \u2013 Remove the mRID of the meter object
Table F.8 \u2013 Remove the mRID of the meter object <\/td>\n<\/tr>\n
235<\/td>\nF.8 Add an mRID and modify name two of the meter object
Table F.9 \u2013 Add an mRID and modify name two of the meter object <\/td>\n<\/tr>\n
236<\/td>\nF.9 Modify name two of the meter object and add name one of the customer object
Figure F.7 \u2013 Add an mRID and modify name two of the meter object <\/td>\n<\/tr>\n
237<\/td>\nTable F.10 \u2013 Modify name two of the meter object
Table F.11 \u2013 Add name one of the customer object <\/td>\n<\/tr>\n
238<\/td>\nFigure F.8 \u2013 Add name one of the customer object and modify name two of the meter object <\/td>\n<\/tr>\n
239<\/td>\nF.10 Add name two of the customer object to carry a new IdentifiedObject.name
Table F.12 \u2013 Add name two of the customer object to carry a new IdentifiedObject.name <\/td>\n<\/tr>\n
240<\/td>\nFigure F.9 \u2013 Add name two of the customer object to carry a new IdentifiedObject.name <\/td>\n<\/tr>\n
241<\/td>\nAnnex 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 \u2013 Example get(MeterConfig) request illustrating a logical “OR” operation <\/td>\n<\/tr>\n
242<\/td>\nG.4 Specifying a combination of logical “AND” and “OR” operations
Figure G.2 \u2013 Example get(MeterReadings) request illustrating a logical “AND” operation <\/td>\n<\/tr>\n
243<\/td>\nG.5 Example of multiple AbstractPayloadType profiles in a single message
Figure G.3 \u2013 Example request message illustrating combined logical “AND” and “OR” operations <\/td>\n<\/tr>\n
244<\/td>\nFigure G.4 \u2013 Example of multiple AbstractPayloadType profiles in a single message <\/td>\n<\/tr>\n
245<\/td>\nAnnex H (informative)Validation of received messages
H.1 General
H.2 Example message validation using Altova XMLSpy <\/td>\n<\/tr>\n
246<\/td>\nH.3 Example message validation using a Java validator
Figure H.1 \u2013 Example message suitably modified to specify the locations of the relevant XSD files
Figure H.2 \u2013 Example of local modifications made to the Message.xsd file <\/td>\n<\/tr>\n
247<\/td>\nAnnex I (informative)Significant changes between IEC 61968-100:2013 and IEC 61968-100:2021 <\/td>\n<\/tr>\n
248<\/td>\nTable I.1 \u2013 Significant changes introduced in IEC 61968-100:2021 since IEC 61968-100:2013 <\/td>\n<\/tr>\n
249<\/td>\nTable I.2 \u2013 Detailed changes introduced from IEC 61968-100:2013 to IEC 61968-100:2021 <\/td>\n<\/tr>\n
250<\/td>\nTable I.3 \u2013 Elements removed from IEC 61968-100:2013 <\/td>\n<\/tr>\n
253<\/td>\nBibliography <\/td>\n<\/tr>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Application integration at electric utilities. System interfaces for distribution management – IEC Implementation profiles for application integration<\/b><\/p>\n\n\n\n\n
Published By<\/td>\nPublication Date<\/td>\nNumber of Pages<\/td>\n<\/tr>\n
BSI<\/b><\/a><\/td>\n2022<\/td>\n254<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"featured_media":402375,"template":"","meta":{"rank_math_lock_modified_date":false,"ep_exclude_from_search":false},"product_cat":[2641],"product_tag":[],"class_list":{"0":"post-402366","1":"product","2":"type-product","3":"status-publish","4":"has-post-thumbnail","6":"product_cat-bsi","8":"first","9":"instock","10":"sold-individually","11":"shipping-taxable","12":"purchasable","13":"product-type-simple"},"_links":{"self":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product\/402366","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product"}],"about":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/types\/product"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media\/402375"}],"wp:attachment":[{"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/media?parent=402366"}],"wp:term":[{"taxonomy":"product_cat","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_cat?post=402366"},{"taxonomy":"product_tag","embeddable":true,"href":"https:\/\/pdfstandards.shop\/wp-json\/wp\/v2\/product_tag?post=402366"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}