Systems Integration Specialists Company, Inc. The Standards Based Integration Company © Copyright 2009 SISCO, Inc. IOP Status Report CIMug Meeting Margaret

Systems Integration Specialists Company, Inc.

The Standards Based Integration Company

© Copyright 2009 SISCO, Inc.

IOP Status Report CIMug Meeting

Margaret Goodrich, SISCO IncCharlotte, NCNovember 11, 2009

© Copyright 2009 SISCO, Inc.2

General Topics

Dynamics Project IOP

CDPSM IOP

Part 9 IOP


Dynamics Project IOP

Project Introduction Test Participants Test Contents Use of Profiles Test Witnesses and Logistics


Dynamics Project Introduction

EPRI Sponsored Project Terry Saxton and Margaret Goodrich are Co-

Directors 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.


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


Dynamics IOP Test Participants (Products)

DigSilent (PowerFactory)

GE Energy (PSLF)

RTE/Tractebel (Eurostag)

Siemens PTI (PSS/E)


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


Dynamics IOP Test Contents – Model Exchange

Participant

A XML

Import/ Export

UCTE

Test Case

5.x Browser

XML Tools XSL

Style Sheet

CIM XML

Schema XML Import/ Export

Participant

B


Dynamics IOP Test Contents – Solution Exchange


Dynamics IOP – Use of Profiles

IOP will use 4 ProfilesEquipment

Topology

State Variables

Dynamics for both Standard and User Defined Models

Equipment, Topology and State Variables Profiles will be the same as was used in the UCTE IOP last March.


Dynamics IOP – UCTE ProfilesState Variables

TSO Topology

TSO Equipment Model

ACLineSegment

ControlArea

CurrentLimit

CurveData

EnergyConsumer

FossilFuel

GeneratingUnit

GeographicalRegion

HydroGeneratingUnit

HydroPump

MutualCoupling

NuclearGeneratingUnit

OperationalLimitSet

PhaseTapChanger

PowerTransformer

RatioTapChanger

ReactiveCapabilityCurve

RegulatingControl

SeriesCompensator

ShuntCompensator

SubGeographicalRegion

Substation

SvPowerFlow SvShuntCompensatorSections SvTapStepSvVoltage

Switch

SynchronousMachine

Terminal

Terminal (about)

ThermalGeneratingUnit

TieFlow

TopologicalIsland

TopologicalNode

TransformerWinding

VoltageLevel

VoltageLimit

WindGeneratingUnit

UCTE Common Objects BaseVoltage OperationalLimitType

ControlAreaGeneratingUnit

LoadResponseCharacteristic


Dynamics IOP – Test Witnesses and Logistics

Test WitnessesDavid Bogen, Oncor

Pamela McClean, AESO

Chavdar Ivanov, ENTSO-E

Margaret Goodrich, SISCO Logistics

Location – EPRI Offices, Dallas, TX

Dates – Nov. 16 through Nov. 19


Part 13 CDPSM IOP

Participants Profiles Used Tests Contents Test Witnesses Logistics


CDPSM IOP Test Participants

EDF GE EPRI (OpenDSS) by Tom McDermott Current Group (by Rod Frowd) SISCO


CDPSM IOP Profiles

Three Profiles – All Full Model Single Profile DocumentsCDPSM for Balanced Network Model

CDPSM for Unbalanced Network Model

GIS Connectivity Network Model


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.


CDPSM IOP Test Contents Data Exchange Test Cases – GIS Focus61968-13 – CDPSM exchange, GIS focus in 2009


CDPSM IOP Test Contents Data Exchange Test Cases – DMS Model Exchange FocusExchange of CDPSM* (similar to today’s CPSM inter-op tests)

*Common Distribution Power System Model (CDPSM) – IEC 61968-13 standard

ParticipantA

ParticipantB

CIM XMLImport

CIM XMLDoc 1

ModelMaint

System

CIM XMLImport

ModelMaint

System

CIM XMLExport

CIM XMLDoc 2

CIM XMLValidator

1

1,4 2

2

3

5

5

4

1,4 5


CDPSM IOP Test Witnesses & Logistics

Test WitnessesDavid Bogen, Oncor

Margaret Goodrich, SISCO Logistics

Location – Oncor, Dallas, TX

Dates – Nov. 30 through Dec. 3rd


Part 9 IOP

Introduction Testing Infrastructure Overview Test Participants Test Contents Test Issues

Controls and Events

Metering Systems

Asynchronous Replies Enumerations Test Witness GUI Slides Test Schedule


Introduction

Test is Sponsored by EPRI Scott Neumann and Margaret Goodrich are Co-

Directors First IOP for WG14 First Messaging Test First Test using ESB First Test Remotely


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


Test Participants

Ecologic EDF Elster GE Grid Net Itron L&G Telvent


Test Contents - Messages

MeterReading EndDeviceEvents EndDeviceControls EndDeviceAssets CustomerMeterDataSet MeterReadSchedule


Test Contents

Requests Events

get createupdate

delete

cancel

close created

updated

deleted

canceled closed

MeterReadingsX - X - X - X - X - X

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 XX - X - X X - X X - X

EndDeviceAssets X X X - X

CustomerMeterDataSet X - X X X

MeterReadSchedule X - X - X - X X - X - X - X X XX - X - X X - X - X X - X

Green = Elster

Red = L&G Blue = Ecologic

Mauve - GE Orange - Itron

Brown - Grid Net

Black - EDF


Controls and Events



Controls and Events

1. Client process issues request to MS as ‘create EndDeviceControls’, where each EndDeviceControl has a unique mRID (using a GUID)

2. MS replies to client synchronous, as ‘reply EndDeviceControls’3. Event published ‘created EndDeviceControls’ to notify potentially

interested clients that a control has been requested or scheduled4. MS processes control request issuing messages to end devices as

needed (the messaging and processing sequences here are outside the scope of 61968-9)

5. Consequences of controls may be reported to metering system from end devices

6. 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



Metering Systems



Metering Systems

1. Meter readings are collected by metering system2. Metering system publishes messages using ‘created

MeterReadings’ to potentially interested clients3. Some of the information collected from meters may

be events, or may cause events to be inferenced and reported using ‘created EndDeviceEvents’



Asynchronous Replies



Asynchronous Replies

1. Client (e.g. MDM) may request meter readings from metering system using ‘get MeterReadings’

2. Metering system replies to client synchronously using ‘reply MeterReadings’ with whatever data is available that is relevant to the request if it chooses

3. Meters may later return the desired data to metering system4. Metering system replies asynchronously to client using ‘reply

MeterReadings’ to specified reply topic/queue and correlation ID used on initial request

5. Metering system may also publish data using ‘created MeterReadings’ to any potentially interested client



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



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 structure is optional

mRID Description

2.6.7.1.0.12.0.0.0.3.72 15-minute Incremental IntervalDataForward Energy (kWh)

4.6.4.0.2.8.0.0.0.0.111 24-hour Incremental DeltaDataIEEE1366MomentaryInterruption

(Count)

7.6.7.1.0.12.0.0.0.3.72 60-minute Incremental IntervalDataForward 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)



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



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



Control Types

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 remoteconnect/disconnect

switch

3.31.6.66 Disable RCD Switch

3.31.6.68 Open remote connect/disconnectswitch

3.31.6.76 Enable RCD switch

3.34.6.201 Price signal



Test Witness GUI Slides

37




38






Test Schedule

All Connectivity testing between Vendor and ESB by November

Dry Run Test – Dec. 15-16, 2009 Actual Test – Jan 5-6, 2010


Questions

??????