1. Interoperability Test Enumerations for IEC 61968-9
Scott Neumann
December 14, 2009

2. Introduction
The purpose of this presentation is to describe enumerations to be used for IEC interoperability tests
Key reference is (obviously) FDIS for IEC
This was revised to reflect input from 8/31/2009 conference call
Revised to describe uses of ISO 8601 and add more quality codes 9/3/2009

3. Note
The enumerations defined here are purposely not defined as restrictions in any XSD
If an implementation encounters an unknown enumeration, it may be flagged as an error, but it should otherwise not ‘break’ the implementation

4. Reading Types 61968-9 Annex C Needed for MeterReadings message
Populated as the value for the ‘ref’ attribute in ReadingType structure
Population of the ReadingTypes list in the MeterReadings stucture is optional
mRID
Description
15-minute Incremental IntervalData
Forward Energy (kWh)
24-hour Incremental DeltaData
IEEE1366MomentaryInterruption (Count)
60-minute Incremental IntervalData
Energization status
Indicating Voltage (V)
BulkQuantity Forward Energy (kWh)

5. Quality Codes
mRID
Description
Null
Assumed valid
1.0.0
Data valid
1.4.5
Test data
2.3.4
Reverse rotation
Error code
1.4.4
Skipped interval
3.0.0
Validated
3.6.0
Failed validation
Known missing read
3.7.0
Manually edited
3.8.0
Generic estimated
3.10.0
Indeterminate
3.10.1
Manually accepted
3.11.0
Derived - general
3.11.1
Derived - inferred
Annex D
Used to populate ‘quality’ element in ReadingQualities structure
Readings are assumed to be valid unless reading quality is specified
Created new category 11 for ‘derived’ values

6. Event Types
category
Description
Power off alarm
Power on
Low voltage
Low voltage cleared
High voltage
High voltage cleared
Unauthorized Access attempt
Tamper detection
Battery failed
Demand reset
Armed for closure
Disconnected
Reconnected
Annex E
Used to populate ‘category’ of EndDeviceEvent structure
Important not to confuse event codes with reply codes

7. Control Types
type
Description
Demand reset
Load control started
Load control stopped
Close remote
connect/disconnect
switch
Disable RCD Switch
Open remote connect/disconnect
Enable RCD switch
Price signal
Annex F
Used to populate ‘type’ in EndDeviceControl structure

8. Time Stamps All timestamps must conform to ISO 8601
Timestamps MUST provide time zone offset or ‘Z’ for absolute time
Precision to seconds is recommended but not required, as to not overstate the precision of the end device
There is currently no use case requiring milliseconds
ISO 8601 allows for as many decimals of accuracy as needed, so long as partners agree

9. TimeSchedules Use ISO 8610 where appropriate
See sections 5.6 and B.5 of ISO 8601 for recurring time intervals
Examples for TimeSchedule/recurrencePattern:
Monthly: R/P1M
Daily: R/P1D
Hourly: R/PT1H
15 minutes: R/PT15M
Reading windows can be supported using intervals, e.g. TimeSchedule/TimePoints/absoluteTime = T04:10:00/PT1H17M12S
TimeSchedule/scheduleInterval/end should be set to a time in the far future if no end is desired

10. EndDeviceAssets
Need to identify a set of mRIDs for EndDeviceAssets for each metering system
Allocations:
ESB test objects: 1-10
Elster:
Landis&Gyr:
Itron:
Other: …

11. Landis+Gyr Enumerations
EndDeviceAssets mRIDs M M M M M M M M M M
LGRF100000
LGRF100001
LGRF100002
LGRF100003
LGRF100004
LGRF100005
EndDeviceEvent.category values
Power On Event
Power Off Event
Register Reading Types
 = kwh
= Present Max kW
= Instantaneous Active Demand
Interval Reading Types L+G will support/send
 = 15-minute Incremental IntervalData Forward Energy (kWh)
EndDeviceControl.type values L+G will support/receive (tentative)

12. Other EndDeviceAsset mRIDs
Ecologic:
EA001
EA002
EA003
EA004
EA005
UISOL: 1 2 3 4 5 6 7 8 9 10

13. Error Codes Used to populate message ReplyCode element
type
Description
0.0
No errors
1.1
Noun element(s) not found in payload
1.3
Verb not found
2.4
Invalid meter number(s)
2.5
Invalid noun
2.6
Invalid ReadingTypeID
2.9
Invalid verb or revision number
2.10
Unable to process the request, ReadingTypeID not supported by the system
2.11
Payload mismatch
4.1
Request timed out
5.2
Unable to process the request. Transaction not attempted
5.3
Unable to process the request. Transaction attempted and failed
Used to populate message ReplyCode element
From IEC table B.2
Many more error codes are possible

14. More Information UISOL web site: http://uisol.com
EPRI Technical Report: ESB Implementation Profile Using IEC 61968
ISO 8601