Download presentation
Presentation is loading. Please wait.
1
Scott Neumann November 1, 2009
IEC Errata Scott Neumann November 1, 2009
2
Introduction The purpose of this presentation is to document errors discovered in the FDIS for IEC This should provide key input to the second edition IEC
3
Use of ‘Get’ for MeterReadings
Some sequence diagrams incorrectly use ‘create’ instead of ‘get’ for requesting meter readings Specific figures in error include: Section , figure 25 Section , figure 27 Section , figure 34 Section , figure 35 Section , figure 39 Section 5.8.1, figure 47 The following 6 slides provide the revised sequence diagrams correcting verb usage It is still important to note that these diagrams are examples and are not normative
4
Figure 25
5
Figure 27
6
Figure 34
7
Figure 35
8
Figure 39
9
Figure 47
10
EndDeviceAssets Profile
The following elements are needed, but are not consistent with stricter profile definition rules: MeterAsset.formNumber MeterAsset.kH MeterAsset.kR The profile will need to be revised to allow for a MeterAsset instead of a more generic EndDeviceAsset Seal.kind needs to be defined as an enumeration, not a reference This will impact future versions of the corresponding XSD in appendix H
11
CustomerMeterDataSet Profile
The following elements are needed, but are not consistent with stricter profile definition rules: MeterAsset.ServiceCategories The profile will need to be revised to allow for a MeterAsset instead of a more generic EndDeviceAsset This will impact future versions of the corresponding XSD in appendix H
12
MeterReadings Profile
Need to make Status a concrete type Need to note that ReadingTypes are optional, as in practice they do not need to be communicated Might potentially need to expand enumerations for units on ReadingTypes or remove them altogether
13
Notes on Profile Namespaces
These are notes, not errata … IEC uses the namespace Some legacy XSDs use a namespace that reflects 2007 The second edition of will use a 2010 or 2011 namespace as appropriate
14
CIM Issues Need to correct cardinality to make a DemandResponseProgram optional (i.e. 0:1|0:*)
15
Outside of In Message.xsd, Request.StartTime and EndTime are typed as a string, when they should be xsd:dateTime
16
More Information UISOL web site: http://uisol.com
EPRI Technical Report: ESB Implementation Profile Using IEC 61968
Similar presentations
© 2025 SlidePlayer.com. Inc.
All rights reserved.