Transcript IOP Status-CIMug Charolotte

The Standards Based Integration
Company
Systems Integration Specialists Company, Inc.
IOP Status Report
CIMug Meeting
Margaret Goodrich, SISCO Inc
Charlotte, NC
November 11, 2009
© Copyright 2009 SISCO, Inc.
General Topics
2

Dynamics Project IOP

CDPSM IOP

Part 9 IOP
© Copyright 2009 SISCO, Inc.
Dynamics Project IOP
Project Introduction
 Test Participants
 Test Contents
 Use of Profiles
 Test Witnesses and Logistics

3
© Copyright 2009 SISCO, Inc.
Dynamics Project Introduction
EPRI Sponsored Project
 Terry Saxton and Margaret Goodrich are CoDirectors of the Project
 Project participants include Vendors and Utilities
 Goal is to define and validate extensions to CIM
for Dynamic Model Exchange and Dynamic
Studies.
 The Dynamics and Static model Profiles must
contain sufficient information to allow Dynamic
Study Analysis to be performed.

4
© Copyright 2009 SISCO, Inc.
Dynamics Project Introduction

Project includes:
 Definition of new UML modeling methods
 Definition of the CIM Extensions for Standard
Dynamic Models
 Definition of User Defined Dynamic Models
 Planning and Execution of an IOP test to Validate the
extensions
5
© Copyright 2009 SISCO, Inc.
Dynamics IOP Test Participants
(Products)
6

DigSilent (PowerFactory)

GE Energy (PSLF)

RTE/Tractebel (Eurostag)

Siemens PTI (PSS/E)
© Copyright 2009 SISCO, Inc.
Dynamics IOP Test Contents
Full Model Exchange of Static Model (import
and export)
 Power Flow Solutions
 Interoperation of full test models between two or
more vendors
 Exchange of Solution Files
 Exchange of Dynamic Profiles
 Dynamics Studies

7
© Copyright 2009 SISCO, Inc.
Dynamics IOP Test Contents – Model
Exchange
Participant
A
XML
Import/
Export
CIM
XML
Schema
Participant
B
XML
Import/
Export
UCTE
Test Case
5.x
Browser
8
XSL
Style
Sheet
XML
Tools
© Copyright 2009 SISCO, Inc.
Dynamics IOP Test Contents – Solution
Exchange
9
© Copyright 2009 SISCO, Inc.
Dynamics IOP – Use of Profiles

IOP will use 4 Profiles
 Equipment
 Topology
 State Variables
 Dynamics for both Standard and User Defined
Models

10
Equipment, Topology and State Variables
Profiles will be the same as was used in the
UCTE IOP last March.
© Copyright 2009 SISCO, Inc.
Dynamics IOP – UCTE Profiles
State Variables
SvVoltage
SvPowerFlow
SvShuntCompensatorSections
SvTapStep
TSO Topology
TopologicalNode
TopologicalIsland
Terminal (about)
TSO Equipment Model
GeographicalRegion
SubGeographicalRegion
EnergyConsumer
Substation
PowerTransformer
VoltageLevel
RatioTapChanger
ReactiveCapabilityCurve
ControlArea
ControlAreaGeneratingUnit
TieFlow
ShuntCompensator
Switch
11
Terminal
MutualCoupling
ACLineSegment
CurveData
SeriesCompensator
TransformerWinding
UCTE Common Objects
CurrentLimit
VoltageLimit
RegulatingControl
SynchronousMachine
LoadResponseCharacteristic
OperationalLimitSet
PhaseTapChanger
BaseVoltage
FossilFuel
GeneratingUnit
NuclearGeneratingUnit
HydroGeneratingUnit
ThermalGeneratingUnit
WindGeneratingUnit
HydroPump
OperationalLimitType
© Copyright 2009 SISCO, Inc.
Dynamics IOP – Test Witnesses and Logistics

Test Witnesses
 David Bogen, Oncor
 Pamela McClean, AESO
 Chavdar Ivanov, ENTSO-E
 Margaret Goodrich, SISCO

Logistics
 Location – EPRI Offices, Dallas, TX
 Dates – Nov. 16 through Nov. 19
12
© Copyright 2009 SISCO, Inc.
Part 13 CDPSM IOP
Participants
 Profiles Used
 Tests Contents
 Test Witnesses
 Logistics

13
© Copyright 2009 SISCO, Inc.
CDPSM IOP Test Participants
EDF
 GE
 EPRI (OpenDSS) by Tom McDermott
 Current Group (by Rod Frowd)
 SISCO

14
© Copyright 2009 SISCO, Inc.
CDPSM IOP Profiles

Three Profiles – All Full Model Single Profile
Documents
 CDPSM for Balanced Network Model
 CDPSM for Unbalanced Network Model
 GIS Connectivity Network Model
15
© Copyright 2009 SISCO, Inc.
CDPSM IOP Test Contents

Tests Include:
 Full Model Exchange between two DMS systems
 Full Model Exchange from a GIS System to a DMS
 Interoperation of full test models between two or
more vendors
 Incremental Model Exchange between two DMS
systems
 Incremental Model Exchange between a GIS and a
DMS
 Power Flow Solution for Balanced and Unbalanced
Network Models.
16
© Copyright 2009 SISCO, Inc.
CDPSM IOP Test Contents
Data Exchange Test Cases – GIS Focus
61968-13 – CDPSM exchange, GIS focus in 2009
17
© Copyright 2009 SISCO, Inc.
CDPSM IOP Test Contents
Data Exchange Test Cases – DMS Model
Exchange Focus
Exchange of CDPSM* (similar to today’s CPSM inter-op tests)
CIM XML
Doc 1
CIM XML
Doc 2
4
3
CIM XML
Validator
5
1
2
CIM XML
Export
CIM XML
Import
1,4
Model
Maint
System
2
CIM XML
Import
5
1,4
5
Participant
A
Model
Maint
System
Participant
B
*Common Distribution Power System Model (CDPSM) – IEC 61968-13 standard
18
© Copyright 2009 SISCO, Inc.
CDPSM IOP Test Witnesses & Logistics

Test Witnesses
 David Bogen, Oncor
 Margaret Goodrich, SISCO

Logistics
 Location – Oncor, Dallas, TX
 Dates – Nov. 30 through Dec. 3rd
19
© Copyright 2009 SISCO, Inc.
Part 9 IOP





Introduction
Testing Infrastructure Overview
Test Participants
Test Contents
Test Issues
 Controls and Events
 Metering Systems
 Asynchronous Replies



20
Enumerations
Test Witness GUI Slides
Test Schedule
© Copyright 2009 SISCO, Inc.
Introduction
Test is Sponsored by EPRI
 Scott Neumann and Margaret Goodrich are CoDirectors
 First IOP for WG14
 First Messaging Test
 First Test using ESB
 First Test Remotely

21
© Copyright 2009 SISCO, Inc.
Testing Infrastructure Overview



UISOL test bus is
based upon EPRI TR
1018795 and IEC
61968-1
Participant products
remotely connect to
bus using internet as
clients, servers and/or
listeners
Test witnesses monitor
tests using web
browser
Slide Courtesy of UISOL
22
© Copyright 2009 SISCO, Inc.
Test Participants








23
Ecologic
EDF
Elster
GE
Grid Net
Itron
L&G
Telvent
© Copyright 2009 SISCO, Inc.
Test Contents - Messages






24
MeterReading
EndDeviceEvents
EndDeviceControls
EndDeviceAssets
CustomerMeterDataSet
MeterReadSchedule
© Copyright 2009 SISCO, Inc.
Test Contents
Requests
Events
upda
te
delet
e
canc
el
clos
e
upd
ate
d
get
create
MeterReadings
X-X-X-X-X
-X
X-X-X-X
-X
EndDeviceEvents
X-X
X-X-X-X
X
X
X
X-X-X-X-X
-X
EndDeviceControls
X
X-X-X
X
X
X-XX
X-X
EndDeviceAssets
X
X
X-X
CustomerMeterDataSet
X-X
X
X
MeterReadSchedule
X-X-X-X
X-X-X-X
Green = Elster
25
Red = L&G
Blue = Ecologic
created
delet
ed
cancele
d
closed
X-X-X-X-X
-X
X
X
X-XX
Mauve - GE
X-X
X-X-X
Orange - Itron
X-X
Brown - Grid Net
Black - EDF
© Copyright 2009 SISCO, Inc.
Controls and Events
26
Slide Courtesy of UISOL
© Copyright 2009 SISCO, Inc.
Controls and Events
1.
2.
3.
4.
5.
6.
Client process issues request to MS as ‘create EndDeviceControls’,
where each EndDeviceControl has a unique mRID (using a GUID)
MS replies to client synchronous, as ‘reply EndDeviceControls’
Event published ‘created EndDeviceControls’ to notify potentially
interested clients that a control has been requested or scheduled
MS processes control request issuing messages to end devices as
needed (the messaging and processing sequences here are outside
the scope of 61968-9)
Consequences of controls may be reported to metering system from
end devices
Events published ‘created EndDeviceEvents’ to notify potentially
interested clients, where if possible, the mRID for each
EndDeviceEvent should use the mRID from the corresponding
EndDeviceControl
Slide Courtesy of UISOL
27
© Copyright 2009 SISCO, Inc.
Metering Systems
28
Slide Courtesy of UISOL
© Copyright 2009 SISCO, Inc.
Metering Systems
1.
2.
3.
Meter readings are collected by metering system
Metering system publishes messages using ‘created
MeterReadings’ to potentially interested clients
Some of the information collected from meters may
be events, or may cause events to be inferenced
and reported using ‘created EndDeviceEvents’
Slide Courtesy of UISOL
29
© Copyright 2009 SISCO, Inc.
Asynchronous Replies
30
Slide Courtesy of UISOL
© Copyright 2009 SISCO, Inc.
Asynchronous Replies
1.
2.
3.
4.
5.
Client (e.g. MDM) may request meter readings from metering
system using ‘get MeterReadings’
Metering system replies to client synchronously using ‘reply
MeterReadings’ with whatever data is available that is relevant
to the request if it chooses
Meters may later return the desired data to metering system
Metering system replies asynchronously to client using ‘reply
MeterReadings’ to specified reply topic/queue and correlation
ID used on initial request
Metering system may also publish data using ‘created
MeterReadings’ to any potentially interested client
Slide Courtesy of UISOL
31
© Copyright 2009 SISCO, Inc.
More on Asynchronous Replies

Client responsibilities:
 CorrelationID in header must be used to allow client to correlate multiple
replies to an initial request
 AsyncReplyFlag in header should be set to true
 ReplyAddress should identify topic/queue to be used for asynchronous
replies

Server responsibilities:
 Server (e.g. metering system) must be will to dedicate a thread or
process to process the request asynchronously
 Server must send replies to the designated destination with the
appropriate correlationID as initially supplied by the client
 All but last reply should use ‘PARTIAL’ for the ReplyCode
 Last reply should use ‘OK’ for the ReplyCode
Slide Courtesy of UISOL
32
© Copyright 2009 SISCO, Inc.
Reading Types




33
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 structure
is optional
mRID
Description
2.6.7.1.0.12.0.0.0.3.72
15-minute Incremental IntervalData
Forward Energy (kWh)
4.6.4.0.2.8.0.0.0.0.111
24-hour Incremental DeltaData
IEEE1366MomentaryInterruption
(Count)
7.6.7.1.0.12.0.0.0.3.72
60-minute Incremental IntervalData
Forward Energy (kWh)
0.0.0.0.0.011.0.0.0.0.109
Energization status
0.0.6.0.0.54.0.0.0.0.29
Indicating Voltage (V)
0.0.1.1.0.12.0.0.0.3.72
BulkQuantity Forward Energy (kWh)
Slide Courtesy of UISOL
© Copyright 2009 SISCO, Inc.
Quality Codes



61968-9 Annex D
Used to populate
‘quality’ element in
ReadingQualities
structure
Readings are
assumed to be
valid unless
reading quality is
specified
mRID
Description
Null
Assumed valid
1.0.0
Data valid
1.4.5
Test data
2.3.4
Reverse rotation
1.5.257
Error code
1.4.4
Skipped interval
Slide Courtesy of UISOL
34
© Copyright 2009 SISCO, Inc.
Event Types



61968-9 Annex E
Used to populate
‘category’ of
EndDeviceEvent
structure
Important not to
confuse event codes
with reply codes
Category
Description
3.26.9.185
Power off alarm
3.26.9.216
Power on
6.38.1.150
Low voltage
6.38.9.150
Low voltage cleared
6.38.1.93
High voltage
6.38.9.93
High voltage cleared
7.1.1.2
Unauthorized Access attempt
3.33.1.257
Tamper detection
2.2.1.17
Battery failed
3.8.6.61
Demand reset
3.31.6.11
Armed for closure
3.31.6.68
Disconnected
3.31.6.42
Reconnected
Slide Courtesy of UISOL
35
© Copyright 2009 SISCO, Inc.
Control Types


36
61968-9 Annex F
Used to populate
‘type’ in
EndDeviceControl
structure
Type
Description
3.8.6.61
Demand reset
3.15.6.242.0
Load control started
3.15.6.243.1
Load control stopped
3.31.6.42
Close remote
connect/disconnect
switch
3.31.6.66
Disable RCD Switch
3.31.6.68
Open remote connect/disconnect
switch
3.31.6.76
Enable RCD switch
3.34.6.201
Price signal
Slide Courtesy of UISOL
© Copyright 2009 SISCO, Inc.
Test Witness GUI Slides
37
37
Slide Courtesy of UISOL
© Copyright 2009 SISCO, Inc.
Test Witness GUI Slides
38
38
Slide Courtesy of UISOL
© Copyright 2009 SISCO, Inc.
Test Witness GUI Slides
39
Slide Courtesy of UISOL
© Copyright 2009 SISCO, Inc.
Test Schedule
All Connectivity testing between Vendor and ESB
by November
 Dry Run Test – Dec. 15-16, 2009
 Actual Test – Jan 5-6, 2010

40
© Copyright 2009 SISCO, Inc.
Questions
??????
41
© Copyright 2009 SISCO, Inc.