๐Ÿ”ฅ๐Ÿ”ฅ 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.

๐Ÿ”
BSI PD IEC/TR 61968-900:2015

BSI PD IEC/TR 61968-900:2015

$215.11

Application integration at electric utilities. System interfaces for distribution management – Guidance for implementation of IEC 61968-9

Published By Publication Date Number of Pages
BSI 2015 144
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]

This part of IEC 61968-9, which is a technical report, is a reference document and, as such, is not always suitable for someone new to the world of meter reading and control. In particular, it assumes significant domain knowledge.

This technical report is a companion document to the official standard. It is written from the viewpoint of a software developer or systems integrator who is tasked with implementing IEC 61968-9. It is not intended as a complete description of this standard. For full details, please refer to IEC 61968-9.

To get the most from this technical report, the user should have a good understanding of XML technologies, in particular of XML schema definitions and of web services.

This technical report contains informative recommendations which may be used to guide implementations of IEC 61968-9 and IEC 61968-100. It does not attempt to be exhaustive. In particular, it focuses on the most common IEC 61968-9 interfaces and assumes the user is using web services or JMS as the underlying transport mechanism. If the user is using other systems or the transport services are something other than web services or JMS, the recommendations in this technical report may be less relevant but perhaps still useful.

PDF Catalog

PDF Pages PDF Title
4 CONTENTS
10 FOREWORD
12 INTRODUCTION
15 1 Scope
2 Normative references
3 IEC 61968-100 basics
3.1 General
16 3.2 IEC 61968-100 message exchange patterns
3.3 IEC 61968-100 message types
3.3.1 General
17 3.3.2 Request messages
18 Figures
Figure 1 โ€“ Example message for a simple meter read request
19 3.3.3 Response messages
Figure 2 โ€“ Example response message to a simple meter read request
20 3.3.4 Unsolicited event messages
Figure 3 โ€“ Example unsolicited event message
21 3.4 IEC 61968-100 message content
3.4.1 General
Figure 4 โ€“ RequestMessage definition according to Message.xsd
Figure 5 โ€“ ResponseMessage definition according to Message.xsd
22 3.4.2 Verb and noun elements in the message header
3.4.3 Get requests
Figure 6 โ€“ EventMessage definition according to Message.xsd
23 3.4.4 Other requests
3.4.5 The CorrelationID element
3.4.6 Other elements in the message header
24 3.4.7 The Message.xsd XSD schema definition file
25 4 Request and response messages in detail
4.1 General
4.2 Several potential response messages for each request message
Figure 7 โ€“ Subelements allowed inside a
element
26 4.3 Response messages contain a status indication
4.4 Response messages containing data and error notifications
4.5 Specific error indications in the response messages
Figure 8 โ€“ Example of a success indication in a Reply element
27 Figure 9 โ€“ Example of error indications in a Reply element (incomplete)
28 Figure 10 โ€“ Subelements allowed inside a element
29 4.6 Implicit indication of success
Figure 11 โ€“ Subelements allowed inside a element
30 4.7 General error indications in the response messages
4.7.1 General
4.7.2 Setting the element
Figure 12 โ€“ Example of overall indication of success in a Reply element
Figure 13 โ€“ Example of error indications in a Reply element (corrected)
31 4.7.3 Multiple response messages
4.8 Multiple , and elements
32 4.9 Implementation-specific messages
5 The naming of objects
5.1 General
5.2 Naming meters
33 Figure 14 โ€“ EndDevice definition
34 5.3 EndDeviceGroups, UsagePoints and UsagePointGroups
Figure 15 โ€“ Example of a Meter Read Request with NameType and NameTypeAuthority
35 5.4 Naming of other objects
5.5 Provisioning and interrogating a system
6 Meter read requests and responses
6.1 General
36 6.2 Message exchange patterns
6.2.1 General
6.2.2 Request message with a single response message
37 6.2.3 Request message with multiple response messages
Figure 16 โ€“ Message exchange pattern for a meter read requestwith a single response message
39 6.3 GetMeterReadings request
6.3.1 General
Figure 17 โ€“ Message exchange pattern for a meter read requestwith multiple response messages
41 6.3.2 Naming of meters
6.3.3 The ReadingType element
Figure 18 โ€“ GetMeterReadings definition according to GetMeterReadings.xsd
43 6.3.4 The ReadingQuality element
Figure 19 โ€“ definition
44 6.3.5 The TimeSchedule element
Figure 20 โ€“ definition
45 6.3.6 Specifying multiple constraints in a request message
Figure 21 โ€“ definition
47 Figure 22 โ€“ Example of a request message for two ReadingType codes over two meters
48 6.3.7 Coincident meter reads
Figure 23 โ€“ Example of a request message for two meter/ReadingType combinations
49 6.4 On-demand meter reads
6.4.1 General
50 Figure 24 โ€“ Message exchange pattern for an on-demand meter read
51 6.4.2 Pinging a meter
6.5 MeterReadings response
6.5.1 General
Figure 25 โ€“ Example of an on-demand meter read request message
52 Figure 26 โ€“ Example of a response to a meter read request
53 6.5.2 The element
Figure 27 โ€“ MeterReadings definition according to MeterReadings.xsd
54 6.5.3 The element
Figure 28 โ€“ definition
Figure 29 โ€“ definition
55 6.5.4 The element
6.5.5 The element
6.5.6 The elements
6.5.7 The EndDeviceType, ReadingQualityType and ReadingType elements
Figure 30 โ€“ definition
56 Figure 31 โ€“ definition
58 6.6 Unsolicited meter reads
6.6.1 General
6.6.2 Message exchange pattern
Figure 32 โ€“ Example of a meter read response with namedReadingType and ReadingQuality elements
59 Figure 33 โ€“ Message exchange pattern for a set of unsolicted meter reads
Figure 34 โ€“ Example of an unsolicited meter read message
60 6.6.3 Missing reads
Figure 35 โ€“ Example of a missing reading in a published message
61 6.6.4 Unsolicited MeterReads together with EndDeviceEvents
Figure 36 โ€“ Example of a known missing reading in a published message
62 6.7 More about timestamps and interval data
6.7.1 General
Figure 37 โ€“ Example of a message showing both an event and a reading
63 6.7.2 Interval data
Figure 38 โ€“ Reading Timestamps
64 6.7.3 The interval block
6.7.4 Raw data
65 7 Meter control requests and responses
7.1 General
Figure 39 โ€“ Example use of IntervalBlocks
66 7.2 Message exchange pattern
Tables
Table 1 โ€“ Common EndDeviceControls and their corresponding EndDeviceEvent codes
67 7.3 Create(EndDeviceControls) message
7.3.1 General
Figure 40 โ€“ Message exchange pattern for a meter control operation
68 7.3.2 EndDeviceControls element
Figure 41 โ€“ Example of a create(EndDeviceControls) message for one meter
Figure 42 โ€“ Example of a create(EndDeviceControls) message for two meters
69 Figure 43 โ€“ EndDeviceControls definition
71 Figure 44 โ€“ EndDeviceControl definition
72 7.4 Reply(EndDeviceControls) message
Figure 45 โ€“ EndDeviceControlType definition
Figure 46 โ€“ Example of a reply(EndDeviceControls) message
73 7.5 Created(EndDeviceEvents) message
7.5.1 General
7.5.2 EndDeviceEvents element
Figure 47 โ€“ Example of a created(EndDeviceEvents) message
Figure 48 โ€“ EndDeviceEvents definition
75 Figure 49 โ€“ EndDeviceEvent definition
76 7.6 Unsolicited EndDeviceEvents Messages
7.6.1 General
Figure 50 โ€“ EndDeviceEventType definition
77 7.6.2 Message exchange pattern
7.7 Premises area networks
7.7.1 General
7.7.2 Message exchange pattern
Figure 51 โ€“ Message exchange pattern for an unsolicted EndDevice event
Table 2 โ€“ Common EndDeviceEvent codes for unsolicited messages
78 7.7.3 Pairing the Meter and PAN device
8 Configuration and provisioning
8.1 General
79 8.2 Message exchange pattern
Table 3 โ€“ Config Profiles
80 8.3 Meter configuration
8.3.1 General
Figure 52 โ€“ Message exchange pattern for a create(MeterConfig) message
81 8.3.2 Create(MeterConfig) message
Figure 53 โ€“ MeterConfig definition
82 Figure 54 โ€“ Example of a create(MeterConfig) message
83 8.3.3 Reply(MeterConfig) message, success case
8.3.4 Reply(MeterConfig) message, failure case
8.4 Master data linkage
8.4.1 General
Figure 55 โ€“ Example of a reply(MeterConfig) message, success case
Figure 56 โ€“ Example of a reply(MeterConfig) message, failure case
84 8.4.2 Create(MasterDataLinkage) message
Figure 57 โ€“ MasterDataLinkageConfig Relationships
85 8.5 OperationSets
8.5.1 General
Figure 58 โ€“ Example of a create(MasterDataLinkageConfig) message
86 8.5.2 OperationSet request message
87 Figure 59 โ€“ Example of an execute(OperationSet) message
88 8.5.3 OperationSet Response Message
Figure 60 โ€“ Example of a reply(OperationSet) message, success case
89 9 Scheduling actions for future execution
9.1 General
9.2 Scheduling a meter read
9.2.1 General
Figure 61 โ€“ Example of a reply(OperationSet) message, failure case
90 9.2.2 Message exchange pattern
91 9.2.3 MeterReadSchedule element
Figure 62 โ€“ Message exchange pattern for scheduling a set of meter reads
92 Figure 63 โ€“ MeterReadSchedule definition
94 9.3 Create(MeterReadSchedule) message
9.3.1 General
Figure 64 โ€“ MeterReadSchedule.TimeSchedule definition
95 9.3.2 Reply(MeterReadSchedule) message
Figure 65 โ€“ Example of a meter read schedule request
Figure 66 โ€“ Example of a response to a meter read schedule request
96 9.4 Cancelling a request
9.4.1 General
9.4.2 Cancel(MeterReadSchedule) request
97 10 Transporting IEC 61968-9 messages
10.1 General
10.2 Transporting over SOAP
10.2.1 General
Figure 67 โ€“ Example of a meter read schedule cancel message
Figure 68 โ€“ Example of a simple meter read request imbedded in a SOAP message
98 10.2.2 Generic WSDL
10.2.3 Simple acknowledgement messages
99 10.2.4 Example message flow
Figure 69 โ€“ Example of a simple acknowledgement message
100 10.3 Transporting over JMS
10.3.1 General
Figure 70 โ€“ Message exchange pattern showing the simple acknowledgement messages
101 10.3.2 Explicit acknowledgements
10.3.3 JMS property details
10.3.4 Process details
Table 4 โ€“ JMS properties
102 10.3.5 Object details
11 Summary of message fields
11.1 General
11.2 Meter read operations
11.2.1 General
11.2.2 Request message
103 Table 5 โ€“ get(MeterReadings) fields
104 11.2.3 Response message
105 Table 6 โ€“ reply(MeterReadings) fields
108 11.2.4 Unsolicited meter read
11.3 Meter control operations
11.3.1 General
11.3.2 Request message elements
109 Table 7 โ€“ create(EndDeviceControls) fields
110 11.3.3 Initial response message
Table 8 โ€“ reply(EndDeviceControls) fields
111 11.3.4 Subsequent consequential event messages
Table 9 โ€“ created(EndDeviceEvents) fields
113 11.3.5 Unsolicited meter event
11.4 Configuration and provisioning
11.4.1 General
11.4.2 Provisioning a meter
Table 10 โ€“ create(MeterConfig) fields
115 11.4.3 Creation of a ComModule
Table 11 โ€“ create(ComModuleConfig) fields
116 11.4.4 ServiceLocation
117 Table 12 โ€“ create(ServiceLocationConfig) fields
118 11.4.5 ServiceCategoryConfig
11.4.6 Service supplier
Table 13 โ€“ create(ServiceCategoryConfig) fields
119 Table 14 โ€“ create(ServiceSupplierConfig) fields
120 11.4.7 UsagePoint location
121 Table 15 โ€“ create(UsagePointLocationConfig) fields
122 11.4.8 Usage point
Table 16 โ€“ create(UsagePointConfig) fields
124 11.4.9 Customer
125 Table 17 โ€“ create(CustomerConfig) fields
126 11.4.10 Customer account
127 Table 18 โ€“ create(CustomerAccountConfig) fields
128 11.4.11 Customer Agreement
Table 19 โ€“ create(CustomerAgreementConfig) fields
130 11.4.12 Pricing Structure
Table 20 โ€“ create(PricingStructureConfig) fields
131 11.4.13 MasterDataLinkage
Table 21 โ€“ create(MasterDataLinkageConfig) fields, example 1
133 Table 22 โ€“ create(MasterDataLinkageConfig) fields, example 2
134 11.4.14 OperationSet
Table 23 โ€“ execute(OperationSet) Header and Payload fields, example 1
137 Table 24 โ€“ execute(OperationSet) Header and Payload fields, example 2
139 11.4.15 Adding, changing or deleting an object identifier
141 Table 25 โ€“ execute(OperationSet) Header and Payload fields, example 3

Related products

BSI PD IEC/TR 61968-900:2015
$215.11