Texas Nodal NMMS Overview - UCAIugcimug.ucaiug.org/Meetings/NA2014/NA 2014 Presentations...Delivery of model for promotion UML CIM RDF XML Focus on Standards OK, we have a “Vision”,

<Manual Date> – <Manual Filename> 1 Texas Nodal

Texas Nodal

NMMS Overview

By John Moseley, P.E. Principal Model Architecture and Integration,

Network Model Administration

Presentation Outline

• Overview

• Historical Model Management

• Vision for the Future

• Implementation

• Use of CIM

• Current Process

• Where to go next

• Results so far


ERCOT Overview

Electric Reliability Council of Texas (ERCOT) is the independent system operator responsible for managing the flow of electric power to 22 million Texas customers and 75 percent of the Texas land area.

• 85% of Texas load

• 40,530 circuit miles of high-voltage transmission:

– 9,249 miles of 345 kV and 19,565 miles of 138 kV

• ≈550 generating units

• 84,000 megawatts (MW) total capacity:

– 64,000 MW operational capacity

– 9,700 MW wind generation

– 4,400 MW net available private generation

– 3,000 MW switchable resources

– 3,000 MW mothballed resources

• Capacity available on peak: 73,600 MW

– Includes 8.7 percent of wind capacity

• Reserve margin: 13.86%

• Record peak demand: 68,379 MW (Aug.3, 2011) Jan of 2012

Process Overview (What do we do?)

Network Model Data

Management

In the simplest terms, ERCOT requires data for

grid management, and our job is to gather,

validate and deliver the data used by the

systems that are used to operate and monitor the

Texas electric grid.

How do we do this?



• Overview



• Implementation

• Use of CIM

• Current Process


• Results so far


ERCOT Zonal Market Model Release Process

Real-Time and

Future Analysis

ERCOT

Operations

Model

Database

Non-Temporal

ERCOT

Market and

Registration

Database

SERVICE

REQUEST

Problems with the Old Process

• Single Operations Model only valid for 2 weeks in advance. Planning

Models were for following year, leaving a study gap.

• Market Information not integrated in Operations Model.

• Contingency files and One-lines not available to support future

studies.

• Model database and Outage Scheduler had no dynamic link resulting in

“broken” outages and no ability to outage future equipment.

• Differences in Planning and Operation Model topologies, element

attributes, and naming conventions.

• Dynamic cases built from Planning Cases, but used to support

decisions made in real-time.

• Market Participants had no access to the Model Database.

How big was this problem?

EMS

Topological Grid Data

MMS

Market Grid Data

Planning

Future Grid Data

Dynamics Data

4-sec Telemetry Data

Short-Circuit Data

Syncrophaser Data

Registration Data 15-Min Meter Data

Settlements DataMetering Data Generator Testing Data

9ERCOT Public

11/12/2014

NMMS: The time had come.

• In 2004, ERCOT began a complete system redesign to migrate from a zone-based market model to a node-based market model.

• This redesign necessitated changing both applications and business processes for a number of ERCOT systems:

• Energy Management

• Market Management

• System Planning

• Outage Scheduling

• Congestion Revenue Rights Auctions

Due to experiences in the zonal system, emphasis was focused on the concepts of data consistency, transparency, and accuracy.


• Overview



• Implementation

• Use of CIM

• Current Process


• Results so far


NMMS Vision


One system manages all model data

The Network Model Management System (NMMS)

Concepts

• Single Point of Data Entry/

Centralized repository

• Temporal Modeling

• Data Validation Process

• CIM Standards


The Network Model Management System

Centralized repository for storing ALL Network Model information

Process Overview (Temporal Based Modeling)


Time-Based Modeling

Base Model

Jul 20, 2012

1:00 pm

Jul 20, 2012

2:00 pm

Sep 1, 2012

8:00 am

Sep 1, 2012

9:00 am

Sep 1, 2012

10:00 am

Sep 30, 2012

9:00 am

Nov 8, 2012

8:00 am

Base Model

Selected Change

Selected Change

Selected Change

Future Model

NOMCR Data Flow Diagram (Validation and Model Testing)

Start Saved

Submitted

Deleted

Received

RejectedApproved

For

Testing

Incomplete

Withdrawn

Additional

Data Required

Approved for

ProductionIn Production

Closed

T13

T14

Archived

T22

T20

T21

T25

T1

T2

T4

T3

T15

T5

T6

T7 T8

Resubmitted

T9

T16T19

Market Test

Complete

T11

T12

T23

T27

T26

T24

T28

T18

T17

T10

T30

T29

T31

T32

T33

T34

Validation Testing

Starts Here

Model Testing Starts Here

Delivery of model for promotion

UML CIM RDF XML

Focus on Standards

OK, we have a “Vision”, now what?


• Overview



• Implementation

• Use of CIM

• Current Process


• Results so far


How were we going to do this?

1. Language to describe

the electrical system

2. Data Repository

3. Method of Updating

Base Model

Jul 20, 2012

1:00 pm

Jul 20, 2012

2:00 pm

Sep 1, 2012

8:00 am

Sep 1, 2012

9:00 am

Sep 1, 2012

10:00 am

Sep 30, 2012

9:00 am

Nov 8, 2012

8:00 am

CIM-based schema Temporal change tracking

Good news: Bulk of the

work was done for us.

Common Information Model

(CIM)

What is NMMS


The Network Model Management System (NMMS) is a umbrella of applications used used to manage, manipulate, prepare, validate, test, and provide consistent models to the all model-driven ERCOT operational, market and planning systems.

Utilizes Common Information Model (CIM) standards for integration.

Build around the Siemens EMA Information Model Manager (IMM) and Siemens PTI Model on Demand (MOD)

Uses temporal based changes methodologies to track with time changes to the network models data and to project future conditions.

NMMS serves as the single point of entry and maintenance for the network model topology used by external ERCOT market participants.

What Does NMMS Do?

What Can NMMS Deliver?

NMMS can

• Accommodate Time Based Changes

• Generate models in Future or Past

• Create models in the future (up to 1yr)

• Generate historical models

• Incremental and Full Models (posted on

MIS in XML format)

• Ownership assigned to every piece of

equipment

• Equipment owners own the data

• Uses CIM classes, attributes and

associations

Finally – NMMS will also

• Supply Outage Scheduler with

equipment lists daily

NMMS Applications

NMMS Applications that handle Operations Data:

• Project Tracker & Coordinator (PTC)

• Information Model Manager (IMM)

NMMS Applications that handle Planning Data:

• Model On Demand (MOD)

Introduction : Slide 23

Overview

Information Model Manager (IMM)

• Tool used to model changes

• Common access point to ERCOT Model data

• Job management features

– Maintains time based jobs

– Multiple jobs can modify the same instance –no interlocking

– Stacks up changes over time

• Multiple modeling approaches

• Creates job change logs

• Validation functionality

Module 2 : Slide 24


• Overview



• Implementation

• Use of CIM

• Current Process


• Results so far


26ERCOT Public

11/12/2014

CIM describes the model

class Example

Building

- GPScoordinates

ApartmentComplex

- numberofApartmentUnits

Stadium

- seatingcapacity

InheritedObject

- name

WallLightFixture

Street

0..* 0..1 1..*1

0..*

0..*

Class

Inheritance

Association

Attribute

27ERCOT Public

11/12/2014

ERCOT CIM Combine Cycle Plant Model

class CCP

PowerSystemResource

ERCOT.26.3::CombinedCyclePlant

+ blockLoadTransfer: Bool {bag}

+ combCyclePlantRating: Float {bag}

+ commercialOperationsDate: Date {bag}

+ GstTpspiMax: Float {bag}

+ GstTpspiMin: Float {bag}

+ GtMax: Float {bag}

+ GtMin: Float {bag}

+ LogicalResourceNodeName: String {bag}

+ qualificationStatus: Bool {bag}

+ resourceCategory: String {bag}

+ wfrmcr: Bool {bag}

GeneratingUnit

ERCOT.26.3::

ThermalGeneratingUnit

ERCOT.26.3::

PseudoTerminal

IdentifiedObject

ERCOT.26.3::Terminal

Equipment

ERCOT.26.3::

GenericEquipment

IdentifiedObject

ERCOT.26.3::AncillaryQualification

+ blackStart: Bool {bag}

+ blackStartEffectiveDate: Date {bag}

+ blackStartEndDate: Date {bag}

+ ccEffectiveDate: Date {bag}

+ ccEndDate: Date {bag}

+ condensorCapable: Bool {bag}

+ dynamicSched: Bool {bag}

+ dynamicSchedEffectiveDate: Date {bag}

+ dynamicSchedEndDate: Date {bag}

+ emergencyQse: Bool {bag}

+ emergencyQseEffectiveDate: Date {bag}

+ emergencyQseEndDate: Date {bag}

+ nonSpin: Bool {bag}

+ nonSpinEffectiveDate: Date {bag}

+ nonSpinEndDate: Date {bag}

+ regDown: Bool {bag}

+ regDownEffectiveDate: Date {bag}

+ regDownEndDate: Date {bag}

+ regUp: Bool {bag}

+ regUpEffectiveDate: Date {bag}

+ regUpEndDate: Date {bag}

+ rmr: Bool {bag}

+ rmrEffectiveDate: Date {bag}

+ rmrEndDate: Date {bag}

+ rrs: Bool {bag}

+ rrsUpEffectiveDate: Date {bag}

+ rrsUpEndDate: Date {bag}

+ ufr: Bool {bag}

+ ufrEffectiveDate: Date {bag}

+ ufrEndDate: Date {bag}

+ virtualQse: Bool {bag}

+ virtualQseEffectiveDate: Date {bag}

+ virtualQseEndDate: Date {bag}

IdentifiedObject

ERCOT.26.3::

LogicalConfiguration

EquipmentContainer

ERCOT.26.3::ResourceController

+ externalJointUnit: Bool {bag}

+ frequencyBias: Float {bag}

+ gross: Bool {bag}

+ jointUnit: Bool {bag}

+ physical: Bool {bag}

IdentifiedObject

ERCOT.26.3::Configuration

+ coldStartTime: Float {bag}

+ highReasonabilityLimit: Float {bag}

+ highReasonabilityRampRateLimit: Float {bag}

+ hotintTime: Float {bag}

+ hotStartTime: Float {bag}

+ intColdTime: Float {bag}

+ intStartTime: Float {bag}

+ lowReasonabilityLimit: Float {bag}

+ lowReasonabilityRampRateLimit: Float {bag}

+ maxDailyStarts: Float {bag}

+ maxONTime: Float {bag}

+ maxWeeklyEnergy: Float {bag}

+ maxWeeklyStarts: Float {bag}

+ minOFFTime: Float {bag}

+ minONTime: Float {bag}

+ primaryConfiguration: Bool {bag}

+ qualificationStatus: Bool {bag}

+ seasonalMaxEmergencyRating: Float {bag}

+ seasonalMaxSustainableRating: Float {bag}

+ seasonalMinEmergencyRating: Float {bag}

+ seasonalMinSustainableRating: Float {bag}

+ ShutdownFlag: Bool {bag}

+ StartupFlag: Bool {bag} Curve

ERCOT.26.3::RampRateCurv e

+ Emergency: Bool {bag}

+ rampRateCurveId: String {bag}

IdentifiedObject

ERCOT.26.3::TransState

+ upTransition: Bool {bag}

0..1RampRateCurveMemberOfConfiguration 0..*

1..1

TransStateToConfigConfiguration

0..*

1..1

TransStateFromConfigConfiguration

0..*

1..1

CombinedCyclePlantReferencesResourceController

0..*

0..1

ConfigurationHasALogicalConfiguration

1..*

0..1

PseudoTerminalForGenericEquipment

0..1

0..1

ThermalGeneratingUnitMemberOfCombinedCyclePlant

0..*

0..1PseudoTerminalForCombinedCyclePlant

0..1

0..1

LogicalConfigurationHasACombinedCyclePlant

0..* 0..1

AncillaryQualificationMemberOfCombinedCyclePlant

0..1

Class

Inheritance

Association

Attribute

<cim:CombinedCyclePlant rdf:ID="_{A9ACD42E-F270-4BA1-8FFA-91802D784146}">

<cim:IdentifiedObject.name>AMOCOOIL_CC2</cim:IdentifiedObject.name>

<etx:CombinedCyclePlant.blockLoadTransfer>false</etx:CombinedCyclePlant.blockLoadTransfer>

<cim:CombinedCyclePlant.combCyclePlantRating></cim:CombinedCyclePlant.combCyclePlantRating>

<etx:CombinedCyclePlant.commercialOperationsDate></etx:CombinedCyclePlant.commercialOperationsDate>

<etx:CombinedCyclePlant.GstTpspiMax></etx:CombinedCyclePlant.GstTpspiMax>

<etx:CombinedCyclePlant.GstTpspiMin></etx:CombinedCyclePlant.GstTpspiMin>

<etx:CombinedCyclePlant.GtMax></etx:CombinedCyclePlant.GtMax>

<etx:CombinedCyclePlant.GtMin></etx:CombinedCyclePlant.GtMin>

<etx:CombinedCyclePlant.LogicalResourceNodeName>AMOCOOIL_CC2</etx:CombinedCyclePlant.LogicalResourceNodeName>

<etx:CombinedCyclePlant.qualificationStatus>false</etx:CombinedCyclePlant.qualificationStatus>

<etx:CombinedCyclePlant.resourceCategory></etx:CombinedCyclePlant.resourceCategory>

<etx:CombinedCyclePlant.wfrmcr>false</etx:CombinedCyclePlant.wfrmcr>

<etx:PowerSystemResource.contingencyComponent>true</etx:PowerSystemResource.contingencyComponent>

<etx:PowerSystemResource.Latitude></etx:PowerSystemResource.Latitude>

<etx:PowerSystemResource.Longitude></etx:PowerSystemResource.Longitude>

<etx:PowerSystemResource.teid>131732</etx:PowerSystemResource.teid>

<cim:IdentifiedObject.aliasName>CC2</cim:IdentifiedObject.aliasName>

<cim:IdentifiedObject.description></cim:IdentifiedObject.description>

<cim:IdentifiedObject.localName></cim:IdentifiedObject.localName>

<cim:IdentifiedObject.mRID></cim:IdentifiedObject.mRID>

<cim:IdentifiedObject.pathName></cim:IdentifiedObject.pathName>

<etx:CombinedCyclePlant.ResourceController rdf:resource="#_{8486C560-AFEA-44C8-823A-319B62F8BD47}"/>

<etx:PowerSystemResource.Operatorship rdf:resource="#_{10D52C5A-605F-49C6-892A-97704168A6F8}"/>

<etx:PowerSystemResource.Operatorship rdf:resource="#_{0933FB75-2618-44F5-B0F2-5A39A7E18C1A}"/>

<spc:CombinedCyclePlant.NotUsed rdf:resource="#_{9D0A9713-AB1F-4CF2-8826-344EC04B69BB}"/>

<etx:PowerSystemResource.Ownership rdf:resource="#_{BDC27C61-0D25-4E09-BF63-845CA0E735C7}"/>

</cim:CombinedCyclePlant>

28ERCOT Public

11/12/2014

CIM describes the model

Class

Inheritance

Association

Attribute

29ERCOT Public

11/12/2014

ERCOT CIM Development

• ERCOT began building its Common Information Model with a CIM10 version 7 core schema and has over the past 6 years incrementally improved this schema through 23 full releases and numerous minor alterations last one occurring 8/28/2012.

• Original Population: The prevalent network model used to support the existing zonal market was translated into CIM and supplemented with additional information required to support the node-based market model.

• Some of the key ERCOT extensions are in the following areas

– Market Operations

– SCADA & ICCP Modeling

– Planning & CRR Modeling

– Contingencies & RAS Modeling

– Operations Training Simulator

– Combine-Cycle Plant Modeling


• Overview



• Implementation

• Use of CIM

• Current Process


• Results so far


Current Model Release Process

Topology Processor

Topology Processor

Real-Time AnalysisTemporal Models

Future Case Analysis

Internally what is going on?


4 Levels of Testing prior to ITEST Release

Level 1

• Ran prior to “submission”

• Range Checks

• Association Checks

• Completeness Checks

Level 2

• Model Coordinator Visual checks

• Additional Programmatic Sanity Checks

Level 3

• Engineer Review

• Assessment for Power Flow

Level 4

• Power Flow test with NOMCR incorporated with all other NOMCRs for timeframe


• Overview



• Implementation

• Use of CIM

• Current Process


• Results so far


34ERCOT Public

11/12/2014

ERCOT CIM Development

• Currently we are attempting to align with CIM 16

• Big additions of the following areas

– Adding StateVariables package

– Adding OperationalLimits package

– Adding Equivalents Package

– Adding DiagramLayout Package

StateVariables package


class Phase_1_B


+ edgeVal: String {bag}

+ fromxoffset: LongInt {bag}

+ fromxperm: LongInt {bag}

+ fromyoffset: LongInt {bag}

+ fromyperm: LongInt {bag}

+ height: LongInt {bag}

+ label_height: LongInt {bag}

+ label_width: LongInt {bag}

+ label_xval: LongInt {bag}

+ label_yval: LongInt {bag}

+ near: Bool {bag}

+ PSSEBusName: String {bag}

+ PSSEBusNumber: LongInt {bag}

+ toxoffset: LongInt {bag}

+ toxperm: LongInt {bag}

+ toyoffset: LongInt {bag}

+ toyperm: LongInt {bag}

+ width: LongInt {bag}

+ xval: LongInt {bag}

+ yval: LongInt {bag}

Domain

ERCOT.26.3::StateVariable

ERCOT.26.3::Sv Injection

+ pNetInjection_value: Float {bag}

+ qNetInjection_value: Float {bag}

ERCOT.26.3::

Sv ShuntCompensatorSections

+ sections: Float {bag}

ERCOT.26.3::Sv TapStep

+ position: Float {bag}

ERCOT.26.3::Sv ShortCircuit

+ r0PerR: Float {bag}

+ sShortCircuit_value: Float {bag}

+ x0PerX: Float {bag}

+ xPerR: Float {bag}

ERCOT.26.3::Sv Voltage

+ angle_value: Float {bag}

+ v_value: Float {bag}

ERCOT.26.3::

Sv PowerFlow

+ p_value: Float {bag}

+ q_value: Float {bag}

ERCOT.26.3::Sv Status

+ inService: Bool {bag}

Equipment

ERCOT.26.3::

ConductingEquipment

ERCOT.26.3::TopologicalNode

+ energized: Bool {bag}

+ loadCarrying: Bool {bag}

+ netInjectionMVar: DoubleFloat {bag}

+ netInjectionMW: Float {bag}

+ observabilityFlag: Bool {bag}

+ phaseAngle: Float {bag}

+ psseid: ShortInt {bag}

+ voltage: Float {bag}

ERCOT.26.3::TapChanger

+ avrEnabled: Bool {bag}

+ awrEnabled: Bool {bag}

+ coupledToTransformer: Bool {bag}

+ flowSensitivity: Float {bag}

+ highStep: LongInt {bag}

+ initialDelay: Float {bag}

+ loadBasedRegulationEnabled: Bool {bag}

+ lowStep: LongInt {bag}

+ maximumkV: Float {bag}

+ minimumkV: Float {bag}

+ neutralAngle: Float {bag}

+ neutralKV: Float {bag}

+ neutralStep: LongInt {bag}

+ normalStep: LongInt {bag}

+ parMaxMW: Float {bag}

+ parMinMW: Float {bag}

+ parOptimization: Bool {bag}

+ parRampRate: Float {bag}

+ stepPhaseShiftIncrement: Float {bag}

+ stepVoltageIncrement: DoubleFloat {bag}

+ subsequentDelay: Float {bag}

+ tculControlMode: TransformerControlMode {bag}

RegulatingCondEq

ERCOT.26.3::ShuntCompensator

+ aVRDelay: Float {bag}

+ ControlMode: EnumShuntCompensatorMode {bag}

+ impedance: Float {bag}

+ maximumkV: Float {bag}

+ maximumSections: LongInt {bag}

+ minimumkV: Float {bag}

+ mVArPerSection: DoubleFloat {bag}

+ nominalkV: Float {bag}

+ nominalMVAr: DoubleFloat {bag}

+ normalSections: LongInt {bag}

+ switchingPriority: LongInt {bag}

+ switchOnCount: LongInt {bag}

+ switchOnDate: DateTime {bag}

+ voltSensitivity: DoubleFloat {bag}

+ yPerSection: Float {bag}

TapChangerHasAMasterTapChanger

1..1

SvTapStepHasATapChanger

0..1

+TopologicalNode 1..1

SvVoltageHasATopologicalNode

+SvVoltage 0..1

+TopologicalNode

1..1

SvShortCircuitHasATopologicalNode+SvShortCircuit

0..1

1..1

SvInjectionHasATopologicalNode

0..1

0..1

TerminalExternalConnectionForConductingEquipment

0..*

1..1

SvPowerFlowHasATerminal

0..1

0..1

TapChangerRegulatesTerminal

+TapChanger

0..*

1..1

SvShtCompSectHasAShuntCompensator

0..1

1..1

SvStatusHasAConductingEquipment

0..1

OperationalLimits package


class Phase_1_C

«enumeration»

Enumeration_Package::

OperationalLimitDirectionKind

absoluteValue

deviation

high

low

ERCOT.26.3::

OperationalLimitSet

Domain

ERCOT.26.3::

IdentifiedObject

ERCOT.26.3::

OperationalLimit

ERCOT.26.3::

ApparentPowerLimit

+ value: Float {bag}

ERCOT.26.3::

Activ ePowerLimit


ERCOT.26.3::

CurrentLimit


ERCOT.26.3::OperationalLimitType

+ acceptableDuration: LongInt {bag}

+ direction: OperationalLimitDirectionKind {bag}

+ limitType: LimitType {bag}


+ edgeVal: String {bag}

+ fromxoffset: LongInt {bag}

+ fromxperm: LongInt {bag}

+ fromyoffset: LongInt {bag}

+ fromyperm: LongInt {bag}

+ height: LongInt {bag}

+ label_height: LongInt {bag}

+ label_width: LongInt {bag}

+ label_xval: LongInt {bag}

+ label_yval: LongInt {bag}

+ near: Bool {bag}

+ PSSEBusName: String {bag}

+ PSSEBusNumber: LongInt {bag}

+ toxoffset: LongInt {bag}

+ toxperm: LongInt {bag}

+ toyoffset: LongInt {bag}

+ toyperm: LongInt {bag}

+ width: LongInt {bag}

+ xval: LongInt {bag}

+ yval: LongInt {bag}

PowerSystemResource

ERCOT.26.3::

Equipment1..1

OperationalLimitSetHasAEquipment

0..*

0..1

OperationalLimitSetHasATerminal

0..*

0..1

OperationalLimitHasAOperationalLimitType

0..*

1..1

OperationalLimitPartOfOperationalLimitSet

0..*

Equivalents package


class Equiv alents_Package

ERCOT.26.3::

Connectiv ityNodeContainer

IdentifiedObject

ERCOT.26.3::

PowerSystemResource

ERCOT.26.3::

Equiv alentNetwork

ERCOT.26.3::

Equiv alentBranch

+ r_value: Float {bag}

+ x_value: Float {bag}

ERCOT.26.3::Equiv alentEquipment

ERCOT.26.3::Equiv alentInjection

+ maxP_value: Float {bag}

+ minP_value: Float {bag}

+ regulationCapability: Bool {bag}

+ regulationStatus: Bool {bag}

+ regulationTarget_value: Float {bag}

ERCOT.26.3::

Equiv alentShunt

+ b_value: Float {bag}

+ g_value: Float {bag}

Equipment

ERCOT.26.3::

ConductingEquipment

1..1

EquivalentEquipmentPartOfEquivalentNetwork

0..*

DiagramLayout package


class Phase_1_B

ERCOT.26.3::

DiagramObjectStyle

Domain

ERCOT.26.3::DiagramObjectPoint

+ sequenceNumber: LongInt {bag}

+ xPosition: Float {bag}

+ yPosition: Float {bag}

+ zPosition: Float {bag}

Domain

ERCOT.26.3::

DiagramObjectGluePoint

ERCOT.26.3::DiagramObject

+ drawingOrder: LongInt {bag}

+ isPolygon: Bool {bag}

+ offsetX: Float {bag}

+ offsetY: Float {bag}

+ rotation: Float {bag}

+ sequenceNumber: LongInt {bag}

ERCOT.26.3::Diagram

+ orientation: OrientationKind {bag}

+ x1InitialView: Float {bag}

+ x2InitialView: Float {bag}

+ y1InitialView: Float {bag}

+ y2InitialView: Float {bag}

ERCOT.26.3::

TextDiagramObject

+ text: String {bag}

ERCOT.26.3::VisibilityLayer

+ drawingOrder: LongInt {bag}

Domain

ERCOT.26.3::

IdentifiedObject

0..*

DiagramObjectHasVisibil ityLayer

0..*

0..1

DiagramObjectHasStyle

0..*

0..1

DiagramElementsPartOfDiagram

0..*+DiagramObjects 0..*

IdentifiedObjectDiagramObject

+IdentifiedObject 0..1

0..1

DiagramObjectPointGluedTogether

1..*

0..*

DiagramObjectHasPoints

1..1

39ERCOT Public

11/12/2014

NMMS CIM Schema : Other Big Changes

Rotating Machine, Asynchronous Machine

class ERCOT_Machines_and_Gens

base::

AsynchronousMachine

base::

GeneratingUnit

base::

SynchronousMachine

base::

RotatingMachine

base::

RegulatingCondEq

base::

ConductingEquipment

base::Equipmentbase::

PowerSystemResource

Domain

base::

IdentifiedObject

base::

WindGeneratingUnit

base::

ThermalGeneratingUnit

base::

HydroGeneratingUnit

base::

NuclearGeneratingUnit

+MemberOf_GeneratingUnit 0..1

SynchronousMachineMemberOfGeneratingUnit

+Contains_SynchronousMachines 0..1

DYNAMICS DATA


• Overview



• Implementation

• Use of CIM

• Current Process


• Results so far


NMMS Facts

• Since 9/1/2009 NMMS is being used as the primary system to enternetwork model changes by ERCOT’s Market Participants and byERCOT.

– 25000+ change requests have been submitted into NMMS thus far.

– Weekly CIM models from NMMS have been delivered to downstreamtest environments.

• Since 6/1/2012 NMMS is being used as the source of record forplanning models and planning model changes by ERCOT’s MarketParticipants and by ERCOT staff to build future planning cases.

– Planners are now using NMMS to build base models for 5-year studies

• Quite a few tools leveraging the flat structure of CIM/XML have beendeveloped. Some notable ones include,

– Model topology tracer for Outage Scheduler,

– Contingency definition builder, and

– Station one-line editor/generator.


NMMS Development

Questions?

Documents

Texas Nodal NMMS Overview - UCAIugcimug.ucaiug.org/Meetings/NA2014/NA 2014 Presentations...Delivery of model for promotion UML CIM RDF XML Focus on Standards OK, we have a “Vision”,