UsingCIMinEnterpriseModelManagement

VarunPerumallaEnterpriseInforma8onModelingEngineer

(USmemberofIECTC57WG13andWG16)

CaliforniaISO

CIMUserGroupMee8ng2016,Atlanta,GA

Welcome and Presentation Outline

•  Background

•  Objectives of Enterprise Model Management

•  What is Enterprise Model Management

–  Consolidation of Technologies

–  Business Process Improvements

–  Centralized Model Management

•  Use of CIM in Enterprise Model Management

•  Challenges and Lessons Learned

•  Future Road Map

Page 2

Background

California ISO (CAISO) established in 1998 CAISO is regulated by Federal Energy Regulatory Commission (FERC)

CAISO manages 80% flow of electricity in California and small part in Nevada

Major Milestones Market Redesign and Technology Upgrade (MRTU) – 2009 Energy Imbalance Market (EIM) – 2014

Page 3

Background What is Energy Imbalance Market (EIM)?

Ø  find low-cost generation to meet demand every 5 minutes

Ø  find low-cost renewable energy across state lines in real-time

EIM Benefits Since November 2014 Ø  cost benefits — $114.35 million Ø  carbon emissions — reduced more than 143,695 metric

tons

Portland General Electric and Idaho Power have agreed to participate beginning in 2017 and 2018

Potential EIM participants Ø  Mexican grid operator El Centro Nacional de Control de

Energía (CENACE) for Baja California Norte Ø  Sacramento Municipal Utility District (SMUD)

Page 4

Objectives of Enterprise Model Management

1.  Model Maintenance — centralized model management across the enterprise centralized model maintenance centralized deployment process

2.  Model Deployment — flexibility and efficiency in model update and

deployment cycle time based model maintenance bulk and Incremental payloads

3.  Adaptability to merge models from multiple balancing authorities

4.  Automation reducing the testing cycle of network model builds

Page 5

REFERENCE MODEL DATA SOURCES

Consolidation of Technologies

Network Model Market Models

SCADA Measurements Contingencies

Branch Groups / TCORs

Page 6

GDB Market Systems

Transmission Register

CSV Files / Spreadsheets

Master File

Enterprise Model Management System (EMMS)

One-Line Diagrams

Aggregations, Zones, Regions Resource Operating Characteristics PTO / SC Associations Seasonal Ratings Graphics Display Configurations

Business Process Improvements and Centralized Model Management

Page 7

PSLF TR

One Lines

MF

CSV’s

EIM Entities OTHER WECC PTO’s

GDB

EMS SCADA

IFM

OMS

RTCA SE

VSA DSA

IOOC

EMMS

INTERNAL VALIDATIONS PRIOR TO DEPLOYMENT

Coordinated Deployments

Other

SIBR

RIMS

Value for Coordinated Model Deployments from EMMS Interrelated model components are

–  validated with respect to one another prior to deployment –  deployed together (or deferred together, or reverted together)

Page 8

TR

One Lines

MF

CSV’s

GDB

All Model Consuming

Systems

Related Model Components are

Deployed Together

Ratings

Market Attributes

EMS Network Model

Market Network Model

EMS One-Lines Market One-Lines

Various Elements

EMMS

Related Model Components are Validated with Respect to One

Another

Model Build Process

Page 9

PTO’s OTHER EIM Projects: |A|B|…|J|

Time

EMMS

DB 79 DB 80

a

b

z

a1 a2 a3

Validate

MCR’s

Test

WECC

EMS

MKT

RTCA

OMS

OTHR

Stage

EMS

MKT

RTCA

OMS

OTHR

Production

EMS

MKT

RTCA

OMS

OTHR

CIM XML

03/01/2016 07/01/2016

T – 10 weeks T – 1 week T – 2 days

T

T – 10 weeks T – 1 week T – 2 days

Dynamic Build Process

Page 10

PTO’s OTHER EIM Projects: |A|B|…|J|

Time

EMMS

DB 79 DB 80

a

b

z

Validate

Test

WECC

EMS

MKT

RTCA

OMS

OTHR

Stage

EMS

MKT

RTCA

OMS

OTHR

Production

EMS

MKT

RTCA

OMS

OTHR

CIM XML

Dynamic Changes

03/01/2016 07/01/2016

EMMS SOA Architecture

Page 11

Enterprise Model Management System

(EMMS)

SCADA and AGC

Transmission Network

Applications (TNA)

Real Time Market (RTM)

Day Ahead Market (DAM)

Voltage Stability Analysis (VSA)

ESB

PI

Master File (MF)

Outage Management

System (OMS)

Interchange Transaction

System (ITS)

Automated Load Forecast

System (ALFS)

Market Quality System (MQS)

EngineeringDataFlow

Engineering&RuntimeDataFlow

XML

RDF

ParticpatingTransmissionOwners(PTO)PeakReliability(PEAKRC)

EnergyImbalanceMarket(EIM)

OtherInternalModelingChanges

XML

Inputs

Use of CIM in Enterprise Model Management CAISO has taken the approach of using CIM RDF XML for network model payloads and CIM XSD profiles for all other payloads CIM RDF XML Network Models

Ø  two network models — Grid reliability model and market model Ø  GE PSLF (bus branch) to simplified CIM (breaker node) Ø  model type — EMS only or market only or both Ø  IEC 61970 package Ø  Why CIM Converters??

§  CIM 10 to CIM 15 §  CIM 15 to CIM 10

•  CIM XSD Profiles Ø  IEC 61970, IEC 61968 and IEC 62325 packages Ø  contingency data Ø  dynamic network model data (like Branch Groups, etc.) Ø  future phase — market reference data, transmission registry data

Page 12

Use of CIM in Enterprise Model Management

Web Service Pattern o  request-response pattern for NERC CIP applications o  publish-subscribe pattern for all other applications

UML Model Maintenance o  tools used, Sparx EA, CIMTool and Data Modeler (vendor product) o  enterprise UML model comprises of 3 packages

§  IEC CIM packages §  CAISO extensions §  vendor extensions

o  utmost care has to been taken while creating extensions

Page 13

Challenges and Lessons Learned Seamless Integration

o  exchange of CIM RDF network model with EIM entities o  exchange of CIM XSD profiles with different vendors within CAISO

EMMS Challenges o  supporting both CIM 10 and CIM 15 network model files o  challenges & Issues during conversion process of CIM 10 to CIM 15 o  any change to EMMS will impact all downstream applications o  RDF XML to XSD XML conversions proving to be costly; limitation of the

product architecture

Enterprise Semantic Model Challenges o  maintaining CIM 10 and CIM 15 UML models o  exchange and co-ordination of enterprise UML model between CAISO

and prime vendor o  Data Dictionary and Service (or UDDI) Registry

Page 14

Future Road Map Network Model Builds Frequency

Quarterly — all changes to full network model Monthly — all changes to full network model with the exception of Tie, BAA, boundary changes and EIM data elements Weekly — all changes to full network model with the exception of Tie, BAA, boundary changes and EIM data elements in addition to topology (powerflow) changes Daily — modifications to ratings; attributes such as resistances, impedances, default switch positions, default tap positions, regulation voltages and statuses, MVAR capability curves, contingencies, nomograms, SCADA points, displays etc.

Reliability System Technology Upgrades (RSTU) program — an umbrella of projects that includes EMS replacement, EMMS upgrades (phase 3C), EMNA (RTCA, SE), ESB Sonic Replacement, Master File to SOA, etc. Model synchronization and activation (MSAA) — post RSTU program

Page 15

Thank you

Page 16