Integrated Network Model Management Supplemental …incremental. model exchange . 2003 [CIM10]...

Pat Brown Senior Project Manager

IntelliGrid Program

July 10, 2012

Common Information Model (CIM) &

Network Model Management

Legal Notices

Please observe these Antitrust Compliance Guidelines:

Do not discuss pricing, production capacity, or cost information which is not publicly available; confidential market strategies or business plans; or other competitively sensitive information

Be accurate, objective, and factual in any discussion of goods and services offered in the market by others.

Do not agree with others to discriminate against or refuse to deal with a supplier; or to do business only on certain terms and conditions; or to divide markets, or allocate customers

Do not try to influence or advise others on their business decisions and do not discuss yours except to the extent that they are already public

Introduction

• Common Information Model & Network Model Management

• EPRI Work – Base-funded requirements project – Supplemental project – real-world, more detail, business

processes

• Context: Transmission – More mature product market spaces – Complexity of challenge

Agenda

• CIM Background – What it is, how it’s used – History - a focus on Network Model Management

• Network Model Management work at EPRI

– The issue and the vision – Base funded project

• Strategy • Initial observations

• Questions / Comments

Who’s On the Webcast?

• Organization – TSO? – ISO? – Neither?

• Work Area – Operations? – Planning? – IT? – Other?

• Experience with CIM – Have deployed it? – Am familiar with it? – Could spell it?

IntelliGrid Program

The IntelliGrid Program conducts research, development and demonstrations on the Information and Communications Technologies (ICT) that Enable Smart Grid applications

IntelliGrid • Transmission • Distribution • End-Use (AMI/DR)

CIM Background The Common Information Model Problem Space • Information exchange among applications or systems • Electric utility operations (not generic business domain) • Enterprise level (not device level) data sharing • The bigger world of the Smarter Grid

– More applications – More data – Increasing expectations for

seamless collaboration

CIM Background The Common Information Model Problem Space • Interfaces proliferate • Each is custom (and as time consuming as the last) • Need to understand and document many transformations

Application C

Application B

Application A

Application H

Application G

Application F

Application E

Application D

• One change breaks many interfaces Application

CIM Background The Solution • Arm’s length sharing via a common semantic model

Application C

Application B

Application A

Application H

Application G

Application F

Application E

Application D

CIM Background The Solution – a common model • The common semantic model

– Clearly describes meaning and relationships of shared data

– Also called “conceptual” or “cannonical” or “public” model

• Content of model defined by means of

data sharing use cases

• Independent of all internal application representations

CIM Background The Solution – a common model • Each application translates to/from its internal model

to the public model

Application C

Application B

Application A

Application H

Application G

Application F

Application E

Application D

Semantic /format translation

semantic/ format

translation

semantic/ format

translation

Semantic /format translation

CIM Background The Solution – a common model • The common semantic model

– Requires only one translation per application – Eases application replacement, facilitates application

addition

• Our common semantic model is the CIM

• Intentionally layered – Semantics (described in UML) – Syntax (many)

CIM Background Deep History in Network Modeling • EPRI Operator Training Simulator work (early 90s) • CCAPI Task Force (1993 – 1996)

– Initial goal: allow utilities to procure “best of breed” subsystems for their Energy Management Systems

– Operations perspective – Network model at core

• IEC standard (1996) – Initially: WG13 (Transmission) and WG14 (Distribution) – Over time: WG13 (network model, batch exchange) and

WG14 (assets/meters/work management, messaging) – Shift in vision: electric utility data model in “enterprise

application integration”

CIM Background InterOperability Tests Tell the Story

20 network model IOPs since 2000

2000 [CIM9a] • full model exchange (sample model)

2001 [CIM9b] • full model exchange (Duke, CAL ISO models)

2002 [CIM10] • full/incremental model exchange

2003 [CIM10] • full/incremental model exchange, messages

2004, 2005, 2006 [CIM10] • full/incremental model exchange, Distribution

2007 [CIM11] • full/incremental model exchange, Model Authority Sets

CIM Background InterOperability Tests Tell the Story

20 network model IOPs since 2000

2008 [CIM12/13] – full/incremental model exchange, Planning 2009 [CIM14] – full/incremental model exchange, State Variables 2010 [CIM14] – full/incremental model exchange, headers & merging 2011 [CIM15] – full/incremental model exchange, Diagram Layout,

balanced/unbalanced transformer 2012 [CIM16] – full/incremental model exchange, Dynamics, short circuit

CIM Background How the CIM is Expressed • Common Model – the whole puppy (1500+ classes)

– Unified Modeling Language (UML) – in Enterprise Architect software tool

• Profiles – one data exchange (1-50 classes) – constrains model and adds instantiation rules – standard and project / product specific – data profiles and technology-specific profiles – UML plus… – many tools

• Exchange Instances – technology specific (CIM XML with RDF Schema)

• Common Model – UML

CIM Background How the CIM is Expressed

• Profiles – UML plus rules

• Exchange Instances – CIM XML (flat file or messages)

CIM Background EPRI CIM Primer

• To learn more: Common Information Model Primer Product ID: 1024449 www.epri.com Search on Title or Product ID

CIM Background CIM as an IEC Standard • Actually 3 standards:

– 61970 (network model, XML file exchange) – 61968 (asset, meter, messaging) – 62325 (markets)

• 3 Working Groups – WG13 – 61970

Convener: Terry Saxton tsaxton@xtensible.net

– WG14 – 61968 Convener: Greg Robinson grobinson@xtensible.net

– WG16 – 62325 Convener: Jim Waight jim.waight@siemens.com

• IEC “owns” paper documents • CIMug “owns” UML

CIM Background CIM Users Group (CIMug)

• Community of users and implementers • www.cimug.org • One of several user organizations under UCAInternational

umbrella • Sponsors 2 Users Group meetings per year

– US in the fall (New Orleans – October 22-26, 2012)

– Europe in the spring

EPRI Network Model Management Project EPRI Work

• Why? – Why this work? Why the CIM? – Improve reliability – better network application results – Improve efficiency – engineers do engineering, not data

entry • How?

– Define real-world requirements -> understood product market space

– Progress the CIM standard – Vendor products

• Why now? – Convergence of standards readiness and utility need

EPRI Network Model Management Project EPRI Work

• Integrated Network Model Management – Base-funded requirements project – Supplemental project – real-world, more detail, business

processes

• One electrical grid • Multiple applications

requiring Transmission network model as input

The Current Situation …silo’d model maintenance

EMS/ Operations

Planning

Protection

Training Simulator

Transient Analysis

Development Planning

• This means – Independent manual updates to each model

• Duplicate effort • Synchronization / consistency issues

– Difficult to capture data from one application and apply it in another

– Lack of support for model history – No shared vision of model future – No clarity of thinking about what’s universal (network

configuration, operating guides, operating state)

The Current Situation …silo’d model maintenance

High expenditure of effort but less than high quality results

The Vision

EMS/ Operations

Planning

Protection

Training Simulator

Transient Analysis

The Vision …coordinated Transmission network model maintenance

EMS/ Operations

Planning Training Simulator

Protection

Transient Analysis

. . . . . .

. . . .

• Supports – As-built model history – Planned or proposed work managed cleanly, with

network configuration, operating guides, operating state model separately

• Features – Single source for each piece of data – Changes made only once – Timely, coordinated updates of model for each system

based on its needs

Less effort for much higher quality results

• Benefits – Confidence in data and application results – Ability to correlate information between applications – Timely answers – Reduce maintenance labor

• But there are challenges… – Requirements not fully understood – Model maintenance products are in their infancy – Have a good model basis in the Common Information

Model (CIM), but • Limited CIM interfaces on existing applications • Internal network model exchange is new territory

– Strategy implies significant business process changes

• Observations from utility experience – Merging/aligning models to arrive at single version of the

truth is a lot of work – Vendor products are not ready – Ongoing model validation processes are crucial – Have to make lots of instantiation assumptions – Getting business processes (and individual thought

processes) “CIM compliant” is the hardest task

Statnett quote in presentation at recent CIMug: “CIM v16 is the first version with the potential to fulfill

our requirements for practical use”

The Solution Framework …the Common Information Model (CIM)

• The value is there – Allow engineers do engineering – Reduced labor – Accurate and timely results – Compliance with NERC model requirements – Readiness for inter-utility exchange

• The timing is right to start

– CIM is ready for real-world exercising – Vendor products still being developed

Integrated Network Model Management …an idea whose time has come

• Phase I – Data Gathering – Visionary Utilities – Consuming Applications – Solution Tools

EPRI Network Model Management Project The Base-Funded Project

• Phase II – Generic use case

• Phase III - Requirements

EPRI Network Model Management Project Data Gathering – Utility Deployments

Between ISOs and their member TSOs – ERCOT – California ISO – ENTSO-E (Pan European Transmission Coordinator)

• Key CIM features – Operations / Planning – the Topology Package – TSO maintenance of subset - Model Authority Sets – Different names - Naming model – Exchange file size - Incremental updates

Challenge: Merging similar pieces of a model into a whole

Inside the utility – ERCOT – California ISO – ENTSO-E – Powerlink (Australia) – Elia (Belgium) – NYISO – Statnett (Norway) – RTE (France)

• Key CIM features – All needed for TSO/ ISO plus new ones

Challenge: Synthesizing different views of the same information

• As many scopes and solution strategies as there are utilities

• Wide variety of solution technologies

EPRI Network Model Management Project Data Gathering – Consuming Applications “Real-Time” / Operations / EMS • Functions

– Topology Processing – State Estimation – Contingency Analysis – Optimal Power Flow – Voltage Stability

• Vendors / Products – ABB – Network Manager – Alstom – eterraplatform – GE – XA/21 – OSI – monarch – Siemens – Spectrum Power 3 – Others?

EPRI Network Model Management Project Data Gathering – Consuming Applications

Planning • Functions

– Power Flow – Contingency Analysis – Optimal Power Flow – Security Constrained Optimal Power Flow – Available Transfer Capability – Voltage Stability – Sensitivity Analysis – Fault Analysis – Transient Stability Analysis – Small Signal Stability Analysis

Planning • Vendors / Products

– CESI – DigSilent – PowerFactory – GE – PSLF – NEPLAN – PowerWorld – Siemens – PSSE – Tractebel – Eurostag – Others?

Protection • Functions

– Protection Scheme Design – Short Circuit Analysis

• Vendors / Products – Aspen - OneLiner – electrocon - CAPE – Cooper – CYME family – DigSilent – StationWare, PowerFactory – Others?

Operator Training Simulator • EMS Vendors / Products

– ABB – Network Manager – Alstom – eterraplatform – GE – XA/21 – OSI – monarch – Siemens – Spectrum Power 3

• Standalone Vendors / Products – Powersmiths/PowerWorld – OPS-X – Incremental Systems – PowerSimulator – DSi – EPRI OTS – Others?

• Lots of products • Functions overlap, even in this mature product space

EPRI Network Model Management Project Data Gathering – Model Management Tools

Network Model Management • Vendors / Products

– Alstom – eTerrasource – Siemens PTI – ODMS – Others?

• Phase I – Data Gathering – Visionary Utilities – Consuming Applications – Solution Tools

• Phase II – Generic use case

• Phase III - Requirements

EPRI Network Model Management Project The Base-Funded Project

• Application Data – Types of data

• Equipment, including geo-spatial location • Connectivity • Flowgate definitions • Topology • One-line (graphic) layout of equipment /connectivity model • Seasonal ratings / limits • Measurement linkages • StateVariable (State Estimator) linkages • Load • Dynamic behavior models • Protection • Asset (nameplate information) linkages • Contingency definitions • Generator production/cost models • Documents or linkages to documents

EPRI Network Model Management Project Preliminary Requirements

• Application Data – Considerations

• Where is “biblical source”? • Which non-source data is important to store? • Is there a single tool for the Network Model Management environment or is the work shared?

• Tool Functionality – Model history – Projects (and subprojects) – Grouping of data – Model views – Data security / access control – One-line editing environment – CIM-based API – Model validation capability, including Load Flow – Support for derived or calculated data

• Which requirements imply CIM modifications?

“The CIM isn’t the best way to do anything…. …but it is the best way to do everything.”

- Jay Britton

EPRI Network Model Management Project

Comments? Questions?

Pat Brown Senior Project Manager IntelliGrid Program pbrown@epri.com (913) 449-0736

Together…Shaping the Future of Electricity

Integrated Network Model Management Supplemental …incremental. model exchange . 2003 [CIM10]...

Documents

Incremental Online Sparsi cation for Model Learning in

The Incremental Constriction Model for the Description of

Model Type1 Rotary Incremental Actuator - Moog Inc. · Model Type1 Rotary Incremental Actuator Rotary Incremental Actuator Dimensions Equipment described herein falls under the jurisdiction

Running head: LURIA MODEL INCREMENTAL VALIDITY 1 · PDF fileLURIA MODEL INCREMENTAL VALIDITY 3 Assessing the Incremental Value of KABC-II Luria Model Scores in Predicting Achievement:

System Development Process: The Incremental Commitment Model 1

Saturation-based Incremental LTL Model Checking with ...petridotnet.inf.mit.bme.hu/publications/TACAS2015_MolnarEtAl.pdfSaturation-based Incremental LTL Model Checking with Inductive

Incremental pattern matching in the VIATRA2 model transformation system

An Adaptation of the Incremental Logit Model for ...onlinepubs.trb.org/.../Tuesday/ModelEstimation/jsMiller.pdf · An Adaptation of the Incremental Logit Model for Forecasting Work

Refinements to Incremental Transistor Modelrmason/Teaching/283-c.pdf · Refinements to Incremental Transistor Model • This section presents modifications to the incremental models

Live model transformations driven by incremental pattern matching

MODEL 260 - INCREMENTAL ENCODER

Towards Declarative and Incremental Model Transformationceur-ws.org/Vol-1071/gholizadeh.pdf · Towards Declarative and Incremental Model Transformation Hamid Gholizadeh McMaster University,

A Formal Framework for Incremental Model Slicing · A Formal Framework for Incremental Model Slicing 5 This framework is based on graph-based models and model modiﬁcations and abstracts

Incremental Model Identification of Reaction Systems CPAC...Incremental Model Identification of Reaction Systems Julien Billeter Ecole Polytechnique Fédérale de Lausanne Laboratoire

Incremental Bidirectional Model Transformation with eMo on::IBeXceur-ws.org/Vol-2355/paper4.pdf · Incremental Bidirectional Model Transformation with eMo on::IBeX Nils Weidmann,

Incremental Model Selection for Detection and Tracking …bmvc10.dcs.aber.ac.uk/proc/conference/paper87/paper87.pdf · Incremental Model Selection for Detection and Tracking of Planar

A biomechanical model for a new incremental technique for

Incremental Model Synchronization with Triple …...Incremental Model Synchronization with Triple Graph Grammars? Holger Giese and Robert Wagner Software Engineering Group, Department

Model JI-820 Incremental Encoder Emulator User Manual

INCREMENTAL MODEL PREDICTIVE CONTROL SYSTEM …ufdcimages.uflib.ufl.edu/UF/E0/04/56/02/00001/LIN_X.pdf · incremental model predictive control system design and implementation using