BS EN IEC 61968-100:2022 – TC
$280.87
Tracked Changes. 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 | 634 |
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 |
|---|---|
| 1 | 30457541 |
| 381 | A-30428836 |
| 382 | undefined |
| 385 | Annex ZA (normative)Normative references to international publicationswith their corresponding European publications |
| 388 | English CONTENTS |
| 400 | FOREWORD |
| 402 | INTRODUCTION |
| 403 | 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 |
| 404 | 2 Normative references 3 Terms, definitions and abbreviated terms 3.1 Terms and definitions |
| 405 | 3.2 Abbreviated terms 4 Overview 4.1 General 4.2 Message format |
| 406 | 4.3 Profiles 4.4 Message archetypes 4.5 Header verb and noun |
| 407 | 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 |
| 408 | 4.7.4 Consequential event message exchange pattern 4.8 Basic request/response message types |
| 409 | 5 Message archetypes 5.1 General 5.2 Request message 5.2.1 General 5.2.2 Root element 5.2.3 Structure |
| 410 | 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 |
| 411 | 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 |
| 412 | 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 |
| 413 | 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 |
| 414 | 6.2.2 Response messages Figure 5 โ Request/response message exchange pattern |
| 415 | 6.3 Unsolicited event message exchange pattern 6.4 Consequential event message exchange pattern Figure 6 โ Unsolicited event message exchange pattern |
| 416 | 6.5 Simple acknowledgement message exchange patterns 6.5.1 General Figure 7 โ Consequential event message exchange pattern |
| 417 | 6.5.2 Request/response message exchange pattern with simple acknowledgement messages Figure 8 โ Request/response message exchange patternwith simple acknowledgement messages |
| 418 | 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 |
| 419 | 7 Message details 7.1 General Figure 10 โ Consequential event message exchange pattern with simple acknowledgement messages |
| 420 | 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 |
| 421 | Figure 11 โ Structure of the element Figure 12 โ Structure of the element Figure 13 โ Structure of the element |
| 422 | Figure 14 โ Structure of the element Figure 15 โ Structure of the element Figure 16 โ Structure of the element |
| 423 | 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 |
| 424 | Figure 19 โ Structure of the element Figure 20 โ Structure of the element Figure 21 โ Structure of the element |
| 425 | 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 |
| 426 | Figure 25 โ Structure of the element Figure 26 โ Structure of the element Table 3 โ List of top-level root elements in event messages |
| 427 | Figure 27 โ Structure of the element Figure 28 โ Structure of the element Figure 29 โ Structure of the element |
| 428 | 7.5 The 7.5.1 General 7.5.2 Message header subelements Figure 30 โ Structure of the element Table 4 โ Elements in the Message |
| 430 | 7.5.3 Message header for request messages |
| 431 | Figure 31 โ Structure of the Table 5 โ Verbs used in request messages |
| 432 | 7.5.4 Message header for response messages |
| 433 | Figure 32 โ Structure of the |
| 434 | 7.5.5 Message header for event messages |
| 435 | Figure 33 โ Structure of the Table 6 โ Verbs used in event messages |
| 436 | 7.6 The element 7.6.1 General |
| 437 | 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 |
| 438 | Figure 35 โ Structure of the element |
| 439 | Table 8 โ Subelements within the element |
| 440 | Table 9 โ Values of the element Table 10 โ Normative values for the element |
| 444 | 7.6.5 Combining the , , and elements Figure 36 โ Example of error indications in a element |
| 445 | 7.6.6 The element 7.7 The element 7.7.1 General 7.7.2 Payload subelements |
| 446 | 7.7.3 The element Table 11 โ Subelements within the element |
| 447 | Figure 37 โ Structure of the element for request messages Table 12 โ Subelements within the element |
| 448 | Figure 38 โ Structure of the elementfor response messages Figure 39 โ Structure of the element for event messages |
| 449 | Table 13 โ Subelements within the element |
| 450 | Figure 40 โ Structure of the elementfor request messages |
| 451 | Figure 41 โ Structure of the elementfor response messages |
| 452 | 7.7.4 The element Figure 42 โ Structure of the elementfor event messages |
| 453 | Figure 43 โ Structure of the element Table 14 โ Subelements within the element |
| 454 | 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 |
| 455 | 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 |
| 456 | 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 |
| 457 | 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 |
| 458 | 8.3.2 Create request message 8.3.3 Change request message |
| 459 | 8.3.4 Delete request message 8.3.5 Update request message |
| 460 | 8.3.6 Object management notifications 8.4 Get requests 8.4.1 Making a get request |
| 461 | 8.4.2 Specifying multiple constraints in a request message |
| 462 | 8.4.3 Responding to a get request 8.5 Cancelling transactions 8.5.1 General 8.5.2 Message exchange pattern |
| 463 | 8.5.3 Transactions IDs Figure 46 โ Message Exchange Pattern for a Cancellation Request |
| 464 | 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 |
| 465 | 8.6.2 Rules for object identification 8.6.3 Identifying objects using an element 8.6.4 Identifying objects using a element |
| 466 | 8.6.5 Referencing objects Figure 47 โ General Naming Scheme Figure 48 โ Structure of an element |
| 467 | 8.7 The ObjectIdentificationRevisionSets profile 8.7.1 General 8.7.2 Structure Table 19 โ Subelements within an element |
| 468 | Figure 49 โ ObjectIdentificationRevisionSets profile |
| 469 | 8.7.3 Using the ObjectIdentificationRevisionSets profile 8.7.4 Adding one or more new identifiers Table 20 โ Elements of an ObjectIdentificationRevisionSets profile |
| 470 | 8.7.5 Removing one or more identifiers 8.7.6 Possible Errors Pertaining To ObjectIdentificationRevisionSets Requests 9 Transporting messages 9.1 General |
| 471 | 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 |
| 472 | 9.2.5 WSDL files Table 21 โ Generic WSDL template variable names |
| 473 | 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 |
| 474 | 9.3.2 Message exchange patterns 9.3.3 Application-level acknowledgement messages 9.3.4 JMS headers |
| 476 | Annex A (normative)XSD files A.1 General A.2 The Message.xsd file |
| 488 | A.3 The AbstractPayloadType.xsd file Figure A.1 โ Contents of Message.xsd file Figure A.2 โ Contents of AbstractPayloadType.xsd file |
| 489 | A.4 The LegacyObjectIdentificationRevisionSets.xsd File |
| 494 | A.5 The RDF.xsd file Figure A.3 โ Contents of LegacyObjectIdentificationRevisionSets.xsd file |
| 495 | Figure A.4 โ Contents of the RDF.xsd file |
| 496 | Annex B (normative)Template files B.1 General B.2 The GenericMessageWsdlTemplate.txt file |
| 501 | Figure B.1 โ Contents of GenericMessageXsdTemplate.txt file |
| 502 | B.3 The StrongMessageXsdTemplate.txt file |
| 514 | B.4 The StrongMessageWsdlTemplate.txt file Figure B.2 โ Contents of StrongMessageXsdTemplate.txt file |
| 520 | Figure B.3 โ Contents of StrongMessageWsdlTemplate.txt file |
| 521 | Annex C (informative)Example XSD profiles inheriting from AbstractPayloadType C.1 GetMeterReadings profile |
| 522 | C.2 BinaryData profile Figure C.1 โ Example XSD profile illustrating inheritance from AbstractPayloadType |
| 523 | Figure C.2 โ Example XSD profile suitable for the transmission of binary data |
| 524 | 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 |
| 525 | D.2.3 Meter instantiation request (request message) Figure D.1 โ Example sequence diagram for a meter instantiation request |
| 527 | 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) |
| 528 | 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 |
| 532 | 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) |
| 533 | 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 |
| 534 | 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) |
| 535 | 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) |
| 536 | D.5.3 Using an operationset to enforce transactional integrity (request message) Figure D.11 โ Example sequence diagram for an OperationSet request |
| 539 | 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) |
| 540 | D.6.3 Publication of meter readings (event message) Figure D.14 โ Example sequence diagram for the publication of meter readings |
| 541 | D.6.4 Publication of meter readings (simple acknowledgement message) Figure D.15 โ Example publication of routine meter readings (event message) |
| 542 | 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) |
| 543 | D.7.3 On-demand meter reading message (request message) Figure D.17 โ Example sequence diagram for the retrieval of on-demand meter readings |
| 544 | D.7.4 On-demand meter reading message (response message) Figure D.18 โ Example on-demand meter readings request message |
| 545 | 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 |
| 546 | 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 |
| 547 | D.8.4 Request for an on-demand meter ping (response message 1) Figure D.21 โ Example on-demand meter ping request (request message) |
| 548 | D.8.5 Request for an on-demand meter ping (response message 2) Figure D.22 โ Example on-demand meter ping request (response message) |
| 549 | 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) |
| 550 | 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) |
| 551 | 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) |
| 552 | D.9.3 Historical meter read (request message) Figure D.27 โ Example sequence diagram for the retrieval of historical meter readings |
| 553 | D.9.4 Historical meter read (response message) Figure D.28 โ Example historical meter read request (request message) |
| 554 | 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) |
| 555 | 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) |
| 556 | D.10.4 Historical meter read (response message 3 of 4) Figure D.31 โ Example historical meter read request (response message 2 of 4) |
| 557 | D.10.5 Historical meter read (response message 4 of 4) Figure D.32 โ Example historical meter read request (response message 3 of 4) |
| 558 | 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) |
| 559 | D.11.2 Sequence diagram Figure D.34 โ Example sequence diagram for the retrieval of historical meter readings (request message) |
| 560 | D.11.3 Historical meter read (response message) Figure D.35 โ Example historical meter read request, mixedsuccess and failure cases (request message) |
| 562 | 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) |
| 563 | D.12.3 Request for a meter connect (request message) Figure D.37 โ Example sequence diagram for the requesting a meter connect |
| 564 | D.12.4 Request for a meter connect (response message) Figure D.38 โ Example meter connect (request message) |
| 565 | D.12.5 Request for a meter connect (event message) Figure D.39 โ Example meter connect (response message) |
| 566 | 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) |
| 567 | D.13.2 Using two OperationSets to read two meters before disconnecting them (request message) |
| 568 | 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) |
| 569 | Figure D.43 โ Using two OperationSets to Read two meters before disconnecting them (response message) |
| 570 | 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 |
| 571 | 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) |
| 572 | D.15.2 Response message containing a single transaction id Figure D.47 โ Example create(EndDeviceControls) request message |
| 573 | 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 |
| 574 | 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 |
| 575 | D.16.2 Cancellation request (request message) Figure D.51 โ Example response message containing several transaction IDs |
| 576 | 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 |
| 577 | 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) |
| 578 | 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) |
| 579 | D.18.3 Message that is malformed (response message) Figure D.57 โ Example malformed message (response message) |
| 580 | Annex E (informative)Example IEC 61968-100:2021 messages for updating objects E.1 General E.2 CreateMeterConfig.xml |
| 581 | E.3 ModifyFormNumber.xml Figure E.1 โ CreateMeterConfig.xml |
| 582 | E.4 RemoveFormNumber.xml E.5 AddMeterMultiplier.xml Figure E.2 โ ModifyFormNumber.xml Figure E.3 โ RemoveFormNumber.xml |
| 583 | E.6 ModifyMeterMultiplierKind.xml Figure E.4 โ AddMeterMultiplier.xml |
| 584 | E.7 ModifyMeterMultiplierValue.xml Figure E.5 โ ModifyMeterMultiplierKind.xml |
| 585 | E.8 RemoveMeterMultiplierValue.xml Figure E.6 โ ModifyMeterMultiplierValue.xml |
| 586 | E.9 RemoveMeterMultiplier.xml Figure E.7 โ RemoveMeterMultiplierValue.xml Figure E.8 โ RemoveMeterMultiplier.xml |
| 587 | E.10 AddMeterSeal.xml E.11 AddMeterSealKind.xml Figure E.9 โ AddMeterSeal.xml |
| 588 | E.12 ModifyMeterSealCondition.xml Figure E.10 โ AddMeterSealKind.xml |
| 589 | E.13 RemoveMeterSealCondition.xml Figure E.11 โ ModifyMeterSealCondition.xml |
| 590 | E.14 RemoveMeterSeal.xml Figure E.12 โ RemoveMeterDealCondition.xml Figure E.13 โ RemoveMeterSeal.xml |
| 591 | E.15 ModifyProgramId.xml E.16 RemoveProgramId.xml Figure E.14 โ ModifyProgramId.xml |
| 592 | E.17 AddChannel.xml Figure E.15 โ RemoveProgramId.xml |
| 593 | E.18 ModifyChannelReadingType.xml Figure E.16 โ AddChannelId.xml |
| 594 | E.19 RemoveChannel.xml Figure E.17 โ ModifyChannelReadingType.xml |
| 595 | E.20 AddConnectDisconnectFunction.xml Figure E.18 โ RemoveChannel.xml |
| 596 | E.21 RemoveConnectDisconnectFunction.xml Figure E.19 โ AddConnectDisconnectFunction.xml |
| 597 | E.22 DeleteMeterConfig.xml E.23 DeleteMeterConfig.xml Figure E.20 โ RemoveConnectDisconnectFunction.xml Figure E.21 โ DeleteMeterConfig.xml |
| 598 | E.24 CreateMeterConfigs.xml Figure E.22 โ DeleteMeterConfig.xml |
| 600 | E.25 MultipleObjectChanges.xml Figure E.23 โ CreateMeterConfigs.xml |
| 602 | E.26 MultipleObjectChangesWithOperationSet.xml Figure E.24 โ MultipleObjectChanges.xml |
| 605 | Figure E.25 โ MultipleObjectChangesWithOperationSet.xml |
| 606 | 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 |
| 607 | Figure F.1 โ Add an mRID for the Meter Object Table F.3 โ Add an mRID for the meter object |
| 608 | F.3 Modify name two of the meter object Table F.4 โ Modify name two of the meter object |
| 609 | F.4 Add name three of the meter object Figure F.2 โ Modify name two of the meter object |
| 610 | Figure F.3 โ Add name three of the meter object Table F.5 โ Add name three of the meter object |
| 611 | F.5 Remove Name One of the Meter Object Table F.6 โ Remove name one of the meter object |
| 612 | F.6 Modify the mRID of the meter object Figure F.4 โ Remove name one of the meter object |
| 613 | Figure F.5 โ Modify the mRID of the meter object Table F.7 โ Modify the mRID of the meter object |
| 614 | 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 |
| 615 | 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 |
| 616 | 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 |
| 617 | Table F.10 โ Modify name two of the meter object Table F.11 โ Add name one of the customer object |
| 618 | Figure F.8 โ Add name one of the customer object and modify name two of the meter object |
| 619 | 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 |
| 620 | Figure F.9 โ Add name two of the customer object to carry a new IdentifiedObject.name |
| 621 | 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 |
| 622 | G.4 Specifying a combination of logical “AND” and “OR” operations Figure G.2 โ Example get(MeterReadings) request illustrating a logical “AND” operation |
| 623 | G.5 Example of multiple AbstractPayloadType profiles in a single message Figure G.3 โ Example request message illustrating combined logical “AND” and “OR” operations |
| 624 | Figure G.4 โ Example of multiple AbstractPayloadType profiles in a single message |
| 625 | Annex H (informative)Validation of received messages H.1 General H.2 Example message validation using Altova XMLSpy |
| 626 | 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 |
| 627 | Annex I (informative)Significant changes between IEC 61968-100:2013 and IEC 61968-100:2021 |
| 628 | Table I.1 โ Significant changes introduced in IEC 61968-100:2021 since IEC 61968-100:2013 |
| 629 | Table I.2 โ Detailed changes introduced from IEC 61968-100:2013 to IEC 61968-100:2021 |
| 630 | Table I.3 โ Elements removed from IEC 61968-100:2013 |
| 633 | Bibliography |
