1

SMUD Model Data Requirements & Reporting Procedures

MOD-032-1 VERSION 1.2

NOVEMBER 10, 2015

1

TABLE OF CONTENTS

INTRODUCTION ........................................................................................................ 2

1.1 Purpose ........................................................................................................................ 2

1.2 Audience ...................................................................................................................... 3

1.3 Process Overview ........................................................................................................ 3

Figure 1-1: Generic MOD-032 Modeling Process Overview ............................................ 3

1.4 Responsible Entities ..................................................................................................... 4

1.5 Data Submittal Delegation Options ............................................................................. 4

DATA SUBMISSION REQUIREMENT ...................................................................... 5

2.1 Load Serving Entity ................................................................................................5

Table 2-1: Typical data to be submitted by the LSE ......................................................... 5

2.2 Generator Owner ....................................................................................................5

Table 2-2: Typical data to be submitted by the GO ........................................................... 5

2.3 Transmission Owner ..............................................................................................6

Table 2-3: Typical data to be submitted by the TO ........................................................... 6

POWERFLOW MODEL DEVELOPMENT ................................................................. 7

3.1 Data Format .............................................................................................................7

3.2 Level of Detail ..........................................................................................................7

3.3 Case Types / Scenarios.........................................................................................7

3.4 Schedules for Data Submission ...........................................................................8

3.5 Distribution or Data Posting Requirements ........................................................8

3.6 MOD-032-1 Requirements and Effective Dates ...................................................8

3.7 Demand Forecast and Load Allocation ...............................................................9

3.8 Steady-State, Dynamic, and Short Circuit Model Development .....................9

MOD-032-1 – ATTACHMENT 1 ............................................................................... 10

REVISION HISTORY ............................................................................................... 13

2

INTRODUCTION

1.1 Purpose

North American Electric Reliability Corporation’s (NERC) Reliability Standard MOD-032-1 pertains to system-level modeling and validation to establish consistent modeling data requirements and reporting procedures for development of planning horizon cases necessary to support analysis of the reliability of the interconnected transmission system.

Reliability Standard MOD-032-1 is a consolidation and replacement of existing MOD-010-0, MOD-011-0, MOD-012-0, MOD-013-1, MOD-014-0, and MOD-015-0.1, and it requires data submission by applicable data owners to their respective Transmission Planners and Planning Coordinators to support the Interconnection-wide case building process in their Interconnection.

This procedure provides guidance for SMUD, as a registered Planning Coordinator, with respect to data for power system modeling and analysis. The Western Electricity Coordinating Council (WECC) is SMUD’s designated Electric Reliability Organization (ERO) and develops a series of power flow and dynamics simulation models which are then used by SMUD and other WECC members for performing reliability/powerflow and economic planning studies. These studies are needed to fulfill various NERC standards and WECC compliance requirements.

The purpose of this document is to outline these data reporting procedures needed to support the development of steady state powerflow and dynamics simulation base case models. These models are required to realistically simulate steady state and dynamic behavior of the transmission system while being compliant with MOD-032-1.

Currently, Pacific Gas and Electric (PG&E) is the Area Coordinator, and is the entity currently responsible for collecting and submitting SMUD’s data to WECC. The Area Coordinator function will soon be replaced by the Planning Coordinator (PC) function per MOD 032-1. WECC had been developing a new system with Siemens called Model on Demand (MOD) software as part of WECC’s Base Case Coordination System (BCCS). The BCCS website and MOD software did not work right and were full of software bugs. The Technical Studies Subcommittee and Planning Coordination Committee recommended terminating the software development. As such, SMUD will continue to submit base case modeling data to the Area Coordinator (PG&E) as part of the base case development process.

SMUD is the NERC registered Planning Coordinator for SMUD’s transmission footprint. Currently, SMUD submits modeling data to PG&E per requirements of the WECC Data Preparation Manual (DPM). The DPM was developed and is maintained by the System Review Working Group (SRWG) and provides guidance and procedures for submitting data for building powerflow basecases. Similarly, SMUD has established a set of common procedures for submitting data needed for developing planning models as described in this document. The procedures have been established pursuant to requirement R1 of MOD-032-1 and also intend to parallel and compliment requirements in the WECC DPM.

3

The Modeling Data Requirements & Reporting Procedures (MDRRP) manual is posted on the SMUD Oasis website at the following location (http://www.oasis.oati.com/smd1) per requirement R 1.3 of MOD-032-1.

1.2 Audience

The procedure is written by Transmission Planners (TP) for existing and future TPs, Planning Coordinators (PC), Generator Owners (GO), Load Serving Entities (LSE), Transmission Owners (TO), Resource Planners (RP), Transmission Service Providers (TSP), and Balancing Authorities (BA), for whom SMUD is the Planning Coordinator.

1.3 Process Overview

Figure 1-1 provides a high-level overview of the data modeling process.

Figure 1-1: Generic MOD-032 Modeling Process Overview

SMUD

• Coordinate data collection process (R1)

• Send data requests to data owners annually or as necessary for special projects

Data Owners (Internal SMUD Departments)

• Review data requests

• Provide new and updated data (R2)

• Respond to technical concerns from PC or TP (R3)

SMUD

• Incorporate data into models and update GE-PSLF base cases

• Send models to WECC via Data Representitive (R4). This refers to the existing process with SMUD's Area Coordinator (PG&E).

WECC

• Create Western Interconnection models.

• SMUD reviews the models as part of the SRWG process and provides updates as necessary

4

1.4 Responsible Entities

As per requirements in MOD-032-1 R2, data owners are responsible for providing the data necessary to model their assets to its TPs and PCs as described in this document. TPs may notify data owners that they do not want the data and that it should only be sent to the planning coordinators. Data owners and their respective data submission responsibilities are listed below.

o TOs are responsible for providing data for modeling existing and approved future transmission facilities

o LSEs are responsible for providing load related data such as load allocation for load models in power flow scenarios

o GOs are responsible for submitting modeling data for existing and future generation facilities with a signed interconnection agreement

o RPs are responsible for providing loads and resources data such demand forecasts

o TPSs and BAs currently do not own any facilities and thus do not have any data submittal requirements

1.5 Data Submittal Delegation Options

Load Serving Entities, Generator Owners

LSEs and GOs will coordinate with their interconnected TO and provide data and ensure their data is consistent with TO submitted topology. The LSE or GO may request assistance or delegate load modeling responsibilities to the TO or PC.

Unregistered Entities

TOs should submit best known data for unregistered entities in their footprint. This will allow for higher quality modeling and could improve the accuracy of powerflow studies.

5

DATA SUBMISSION REQUIREMENT

MOD-032-1 Attachment 1 lists the modeling data to be submitted and is summarized below. The attachment is also provided at the end of this document.

2.1 Load Serving Entity

The LSE shall provide the load forecast for varying scenarios being modeled. The LSE must use the bus numbers assigned to them by the Planning Coordinator. SMUD’s Distribution Planning department provides annual updates for load distribution to the Transmission Planning department (known as Grid Planning department at SMUD). The load allocation factors are then used by the transmission planning department to model load in the SMUD distribution system. Table 2-1 provides a summary of data required.

Table 2-1: Typical data to be submitted by the LSE

Steady-State Dynamics Short Circuit

Real and reactive power demands on the load buses

Load composition N/A

In-service status Protection relays N/A

Location of new expected loads N/A N/A

2.2 Generator Owner

The GO shall provide the data necessary to model their generator facilities. The GO shall use bus numbers assigned to them by the Planning Coordinator. Data for existing and planned generators with interconnection agreements should be submitted. Generator test data shall be provided to the Planning Coordinator (SMUD) so that base case models can be updated accordingly. SMUD’s Power Generation department should provide updates to generation data as necessary, and provide generator testing data when available. Table 2-2 provides a summary of data to be submitted by the GO.

Table 2-2: Typical data to be submitted by the GO

Steady-State Dynamics Short Circuit

Generator Generator For applicable steady-state items:

Generator step-up (GSU) transformer data

Excitation system Positive sequence data

Station service load Turbine / Governor Zero sequence data

Seasonal output capabilities Power system stabilizer Negative sequence data

Reactive shunt devices Protection relays N/A

6

In-service status N/A N/A

PV/Wind system N/A N/A

2.3 Transmission Owner

The TO shall provide the data necessary to model their transmission facilities. The TO shall use transmission line IDs and bus numbers assigned to them by the Planning Coordinator. Data for existing and planned transmission lines should be submitted. Line rating changes shall be provided to the Planning Coordinators so that base case models can be updated accordingly. Table 2-3 provides a summary of data to be submitted by the TO.

Table 2-3: Typical data to be submitted by the TO

Steady-State Dynamics Short Circuit

System topology Protection relays For applicable steady-state items:

Buses N/A Positive sequence data

AC transmission lines N/A Zero sequence data

HVDC transmission lines N/A Negative sequence data

Transformers N/A Mutual line impedance data

Reactive shunt devices N/A N/A

7

POWERFLOW MODEL DEVELOPMENT

3.1 Data Format

The powerflow modeling data is to be submitted to SMUD via email with data. Models are developed using General Electric’s Positive Sequence Load Flow (GE-PSLF) software application and need to adhere to WECC’s DPM in order to be implemented in GE-PSLF powerflow base cases. Data submitted should be compatible with GE-PSLF versions currently specified by WECC. Modeling data requests and notifications from WECC are sent to the Planning Coordinator and the PC will determine if updates or more data is required from the data submitters.

3.2 Level of Detail

SMUD maintains models with the following level of detail for base cases: o Generators are modeled down to the low-side of the generator step up

transformer with the exception of aggregated PV power plants such as SMUD’s Feed-In-Tariff solar power plants. These plants are currently modeled at the load bus.

o Loads are modeled as lump sum on the transmission buses at the 69 kV level or are modeled down to lower voltage levels as necessary. One example of this is the downtown Sacramento network where load is modeled down to 12kV level. Station service load is aggregated and modeled at the generator buses.

o All other equipment at 69kV level and above is modeled. This includes transmission lines, transformers, shunt capacitors, shunt reactors, as well as other equipment surpassing the 69 kV threshold.

o SMUD’s models are to be modeled in WECC DPM defined Area 30 and in Zone 322. DPM Defined SMUD owner number is 363.

3.3 Case Types / Scenarios

SMUD builds models to represent the powerflow conditions specified by WECC. WECC uses a document prepared by the SRWG called the Base Case Compilation Schedule. Typically, WECC builds several near term (year 0 to 5) and long term cases (year 5-10). These cases represent typical scenarios such as heavy or light load conditions during summer, winter, and spring. WECC also builds special cases as necessary and these cases can have their own specific set of requirements.

o Summer Peak Load (HS) – is defined as heavy summer peak load expected to be served per the WECC Base Case Compilation Schedule

o Summer Light Load (LS) – is defined as light summer load expected to be served per the WECC Base Case Compilation Schedule

o Winter Peak Load (HW) – is defined as heavy winter peak load expected to be served per the WECC Base Case Compilation Schedule

o Winter Light Load (LW) – is defined as light winter load expected to be served per the WECC Base Case Compilation Schedule

o Spring Peak Load (HSP) – is defined as heavy spring peak load expected to be served per the WECC Base Case Compilation Schedule

8

o Spring Light Load (LSP) – is defined as light spring peak load expected to be served per the WECC Base Case Compilation Schedule

3.4 Schedules for Data Submission

SMUD’s data submittal schedules and timelines are determined on a yearly basis by WECC as part of the Base Case Compilation Schedule. This document can sometimes be modified during SRWG meetings to accommodate pressing needs and is subject to change. WECC posts the Base Case Compilation on their website.

A link to the 2016 Base Case Compilation Schedule is pasted below: https://www.wecc.biz/Reliability/2016-Base-Case-Compilation-Schedule-PCC%20Approved.pdf

A link to the 2015 schedule is pasted below: https://www.wecc.biz/Reliability/2015_Base_Case_Compilation_Schedule-v4.doc

3.5 Distribution or Data Posting Requirements

The Modeling Data Requirements & Reporting Procedures (MDRRP) manual is posted on the SMUD Oasis website at the following location (http://www.oasis.oati.com/smd1 ). This document will also be emailed to contacts (SMUD Internal Departments) at BAs, TOs, GOs, LSEs, and TSPs within the SMUD footprint.

3.6 MOD-032-1 Requirements and Effective Dates

There are 4 requirements for MOD-032-1. The first requirement (R1) is effective on 07/01/2015. R2, R3, and R4 become effective on 07/01/2016.

o R1 requires each PC and TP to jointly develop steady-state, dynamics, and short circuit modeling data requirements and reporting procedures for the PC’s planning area. This is the basis for developing the MDRRP.

o R2 requires each BA, GO, LSE, RP, TO, and TSP to provide steady-state, dynamics, and short circuit modeling data to their TP(s) and/or PC(s) according to the modeling data requirements and reporting procedures developed by their TP(s) and/or PC(s).

o R3 deals with data quality and requires each BA, GO, LSE, RP, TO, and TSP to either provide updated data or a technical explanation for maintain current data within 90 days of receipt of written notification from its PC and/or TP.

o R4 requires each PC to provide models for its planning area reflecting data provided to it under R4 to the ERO to support creation of Interconnection-wide case(s) that includes the PC’s planning area.

9

3.7 Demand Forecast and Load Allocation

SMUD’s Resource Planning department provides a yearly demand forecast. Demand data from this report is used to build current year and future year cases. The demand data is then broken down into lump sum load components. Information for this is provided in the load allocation spreadsheet created by SMUD’s Distribution Planning department. The load allocation data is also provided annually.

3.8 Steady-State, Dynamic, and Short Circuit Model Development

SMUD develops these models as per the WECC DPM. The steady state models represent the normal operation of the power system and are time independent. The dynamic models are time dependent and are used for transient stability studies. Typical transient stability simulations are in the timeframe of 0 to 20 seconds. Short circuit data is required for generators, transformers, and transmission line. Short circuit data is provided by SMUD’s SPAC department.

10

MOD-032-1 – ATTACHMENT 1

Data Reporting Requirements

The table, below, indicates the information that is required to effectively model the interconnected transmission system for the Near-Term Transmission Planning Horizon and Long-Term Transmission Planning Horizon. Data must be shareable on an interconnection-wide basis to support use in the Interconnection-wide cases. A Planning Coordinator may specify additional information that includes specific information required for each item in the table below. Each functional entity1 responsible for reporting the respective data in the table is identified by brackets “[functional entity]” adjacent to and following each data item. The data reported shall be as identified by the bus number, name, and/or identifier that is assigned in conjunction with the PC, TO, or TP.

steady-state

(Items marked with an asterisk indicate data that vary with system operating state or conditions. Those items may have different data provided for different

modeling scenarios)

dynamics

(If a user-written model(s) is submitted in place of a

generic or library model, it must include the

characteristics of the model, including block diagrams, values and names for all model

parameters, and a list of all state variables)

short circuit

1. Each bus [TO] a. nominal voltage b. area, zone and owner

2. Aggregate Demand1 [LSE]

a. real and reactive power* b. in-service status*

3. Generating Units2 [GO, RP (for

future planned resources only)] a. real power capabilities -

gross maximum and minimum values

b. reactive power capabilities - maximum and minimum values at real power capabilities in 3a above

c. station service auxiliary load

1. Generator [GO, RP (for future planned resources only)]

2. Excitation System [GO, RP(for future planned resources only)]

3. Governor [GO, RP(for future planned resources only)]

4. Power System Stabilizer [GO, RP(for future planned resources only)]

5. Demand [LSE] 6. Wind Turbine Data [GO] 7. Photovoltaic systems [GO] 8. Static Var Systems and FACTS

[GO, TO, LSE] 9. DC system models [TO] 10. Other information requested by

1. Provide for all applicable elements in column “steady-state” [GO, RP, TO] a. Positive Sequence Data b. Negative Sequence Data c. Zero Sequence Data

2. Mutual Line Impedance Data [TO]

3. Other information requested by the Planning Coordinator or Transmission Planner necessary for modeling purposes. [BA, GO, LSE, TO, TSP]

1 For purposes of this attachment, the functional entity references are represented by abbreviations as follows: Balancing Authority (BA),

Generator Owner (GO), Load Serving Entity (LSE), Planning Coordinator (PC), Resource Planner (RP), Transmission Owner (TO),

Transmission Planner (TP), and Transmission Service Provider (TSP).

2 For purposes of this item, aggregate Demand is the Demand aggregated at each bus under item 1 that is identified by a Transmission Owner as a

load serving bus. An LSE is responsible for providing this information, generally through coordination with the Transmission Owner.

3 Including synchronous condensers and pumped storage.

11

for normal plant configuration (provide data in the same manner as that required for aggregate Demand under item 2, above).

d. regulated bus* and voltage set point* (as typically provided by the TOP)

e. machine MVA base f. generator step up

transformer data (provide same data as that required for transformer under item 6, below)

g. generator type (hydro, wind, fossil, solar, nuclear, etc.)

h. in-service status* 4. AC Transmission Line or Circuit

[TO] a. impedance parameters

(positive sequence) b. susceptance (line charging) c. ratings (normal and

emergency)* d. in-service status*

5. DC Transmission systems [TO] 6. Transformer (voltage and

phase-shifting) [TO] a. nominal voltages of

windings b. impedance(s) c. tap ratios (voltage or phase

angle)* d. minimum and maximum tap

position limits e. number of tap positions (for

both the ULTC and NLTC) f. regulated bus (for voltage

regulating transformers)* g. ratings (normal and

emergency)* h. in-service status*

7. Reactive compensation (shunt capacitors and reactors) [TO] a. admittances (MVars) of

each capacitor and reactor b. regulated voltage band

limits* (if mode of operation not fixed)

c. mode of operation (fixed, discrete, continuous, etc.)

d. regulated bus* (if mode of operation not fixed)

e. in-service status* 8. Static Var Systems [TO]

a. reactive limits b. voltage set point* c. fixed/switched shunt, if

applicable d. in-service status*

9. Other information requested by

the Planning Coordinator or Transmission Planner necessary for modeling purposes. [BA, GO, LSE, TO, TSP]

12

the Planning Coordinator or Transmission Planner necessary for modeling purposes. [BA, GO, LSE, TO, TSP]

13

REVISION HISTORY

Version Date By Summary of Changes

1.2 11/10/2015 Prabal Singh Modified document to reflect the cessation of using MOD software for

the BCCS process. SRWG confirmed this

recommendation from the TSS and PCC during the

SRWG meeting from 11/4/15 – 11/5/15.

1.1 07/10/2015 Prabal Singh Revisions and Clarifications

1.0 06/30/2015 Prabal Singh Initial Development