http://nodal.ercot.com 1

1
Registration Data CollectionJune Window

• Kick Off Meeting

May 22, 2009
2
Antitrust Admonition
ANTITRUST ADMONITION ERCOT strictly
prohibits Market Participants and their employees
who are participating in ERCOT activities from
using their participation in ERCOT activities as
a forum for engaging in practices or
communications that violate the antitrust laws.
The ERCOT Board has approved guidelines for
members of ERCOT Committees, Subcommittees and
Working Groups to be reviewed and followed by
each Market Participant attending ERCOT meetings.
If you have not received a copy of these
Guidelines, copies are available at the Client
Relations desk. Please remember your ongoing
obligation to comply with all applicable laws,
including the antitrust laws. DISCLAIMER All
presentations and materials submitted by Market
Participants or any other Entity to ERCOT staff
for this meeting are received and posted with the
acknowledgement that the information will be
considered public in accordance with the ERCOT
Websites Content Management Operating Procedure.
http//nodal.ercot.com 2
3
Agenda

• Objective and Scope
• Project Logistics
• Approach / Schedule
• RARF Screening Process / Reference Materials
• Data Collection Details
• Transmission Data
• Transmission Data Tabs Background
• Pre-populated RARFs
• Inventory of Transmission Asset Forms
• Planning and Protection Data
• Sub Synchronous Data
• Load Resource Registration Changes
• Next Steps
• June window specific date
• September window target dates
• MP-10
• QA / Open Forum

4
Objective and Scope

• Objective is to finalize the Nodal Resource
  Entity Registration Data Collection effort prior
  to Market Trials
• Scope of the remaining data collection
• Resource Entity Owned Transmission Data
• Private Use Networks window completed on 5/19
• June window will include Non-PUN, Non-Wind Sites
• Planning and Protection Data
• June Window will include Non-Wind Sites
• Load Resource Registration Changes
• Changes Reviewed Today
• Each Load Resource Entity will be contacted
  individually to review minor changes to the
  registration data set

5
Project Logistics - Approach / Schedule
2009
MAR APR MAY JUN
JUL AUG SEP
OCT NOV DEC
Private Use Network Transmission Data Collection
85 Prod Quality
95 Prod Quality
98 Prod Quality
Private Use Network Planning and Protection Data
Collection
June Window - Non-Wind Transmission / Planning /
Protection Data Collection
Kick Off Market Call
85 Prod Quality
95 Prod Quality
98 Prod Quality
September Window - Wind / All Remaining Sites
Transmission / Planning / Protection Data
Collection
Kick Off Market Call
85 Prod Quality
95 Prod Quality
98 Prod Quality
SEMGO-LIVE 8/31
EIS 1.19to EDS 8/10
MP-10 Phase 2 Final Validation
6
Project Logistics - Approach / Schedule

• Window Assignments by Resource Type
• Each Non-PUN / Non-Wind Site will sign-up for
  the June or September Window via
  nodalmarkettransition_at_ercot.com email by 6/8/09
  for submittal of Transmission and Planning /
  Protection data
• Private Use Networks will submit Planning /
  Protection Data during the June Window
• Wind resources will submit Transmission and
  Planning / Protection data during the September
  window
• Approach for this phase will be similar to the
  resource data collection in 2008
• Each Window will be broken up into 3 iterations
  each with increasing goals of production quality
• Iteration 1 85 production quality
• Iteration 2 95 production quality
• Iteration 3 98 production quality
• Iteration 1 will begin with ERCOT sending each RE
  assigned to that iteration a pre-populated RARF
  and an audit report
• Audit reports will detail each error in the RARF
  and the violated business rules
• ERCOT will provide pre-populated RARFs
  containing data previously submitted through
  various artifacts (transmission data slides will
  discuss in greater detail)
• This pre-populated RARF must be used going
  forward for all changes
• Each REs Account Manager will schedule a formal
  conference call to discuss errors on the audit
  report

7
Project Logistics - Approach / Schedule

• Approach for this phase will be similar to the
  resource data collection in 2008 (continued)
• Iteration 2 and 3 will include interim audit
  reports as revisions are submitted by REs
• Account Managers will schedule conference calls
  in iteration 2 and 3 on an as-needed basis
• At the close of each iteration a formal
  production quality metric will be published to
  the readiness center
• A dashboard with the status of each RE will be
  published weekly
• The June Window will officially begin 6/15/09
• REs will receive their pre-populated RARFs the
  week of 6/8
• ERCOT Account Managers will schedule calls to
  start the week of 6/15
• Further schedule details discussed in the Whats
  Next? section

8
Project Logistics - RARF Screening Process /
Reference Materials
Registration Audit Process
9
Project Logistics - RARF Screening Process /
Reference Materials

• Business rules used in the audit report will be
  published in the Resource Registration Guide
• Currently these have been added for the
  transmission data sections
• Planning and Protection data changes will be
  published by 6/8/09
• Each section contains a short narrative regarding
  that section
• Each also section contains all screening business
  rules that will be applied to each field in the
  RARF
• ERCOT will also be working to make these
  modifications to the resource data sections in
  the guide as well (data elements filled out last
  year). This will be completed at a later date.
• The Resource Registration Guide URL (last
  document under Key Documents section)http//noda
  l.ercot.com/readiness/rq/documents/index.html

10
Data Collection Details - Transmission Data

• Transmission Data Tabs Background
• These are derived from 2 artifacts
• TDF (Transmission Data Form) used in zonal and
  MP-10
• GSU Transformer and Transmission Assets tabs
  revamped from the original RARF
• These artifacts were then integrated into the
  RARF at the request of TPTF(reviewed by TPTF in
  September 2008)
• Some fields were added / removed based on ERCOT
  data requirements
• Resource Entities have provided much of this data
  in previous activities
• This effort will focus on closing gaps and
  validating data already provided
• Audit Reports will detail only errors or
  warnings. REs should review all pre-populated
  data to ensure accuracy in previous submittals

11
Data Collection Details - Transmission Data

• Process of Pre-populating RARFs
• Initial population baselines data from the zonal
  model, including updates made through the MP-10
  process
• The process then updates this baseline with data
  submitted via the old GSU Transformer and the
  Transmission Assets tabs
• In short, ERCOT will provide all data we have on
  file to Resource Entities in a pre-populated
  RARF.
• Common issues encountered during preliminary
  transmission data reviews
• Device names (lines, breaker, transformers, etc)
  do not match the ERCOT Mnemonic
• In these cases, ERCOT cannot update data
  submitted via RARF
• We will have to work with Resource Entities
  individually to resolve these
• One-lines do not agree with registered assets
  (resources, transmission data, etc)
• In some cases it was not possible to distinguish
  between TSP and RE owned assets
• In these cases, REs are asked to simply remove
  them from their RARF
• Most commonly these are lines going from a Gen
  Site to a TSP substation

12
Data Collection Details - Transmission Data

• Inventory of Transmission Data Forms (high level
  lists)
• Lines
• Breakers and Switches
• Capacitors and Reactors
• Transformers
• Static Var Compensators
• Series Devices
• Load Data (non-puns will provide Aux / Site
  Service Load)
• PUN Load 168 hr Profiles (private use networks
  only)

13
Data Collection Details - Planning and Protection
Data

• Planning and Protection data was originally
  targeted for later this year / early 2010
• Schedule accelerated in order to minimize
  iterations with Resource Entities
• Schedule accelerated also to avoid conflicts with
  other activities such as re-qualification of
  QSEs and Market Trials
• The following changes made to the planning and
  protection data
• Planning
• Several data elements removed from generator
  details
• Generator Auxiliary Load is now optional except
  for Combined Cycle Units
• PSSE Model files
• Method of submittal will now be a zip file
  accompanied by the RARF submittal in the SR (or
  alternative email process)
• Some files are noted in the RARF as optional
  based on the details of that site
• Note that the PSSE templates are located at
  http//www.ercot.com/gridinfo/generation/
• Protection
• Only change is adding a 4th time point to each
  section (Underfrequency, Overfrequency,
  Overvoltage, Undervoltage)
• Note that all changes will be included in the
  pre-populated RARF sent to all REs at the start
  of either the June Window or September Window

14
Data Collection Details - Planning and Protection
Data

• Business Rules for Planning and Protection
• ERCOT team is in the process of adding these to
  the Resource Registration Guide
• This will be complete and published to the market
  by 6/8/09 to the readiness center
• Posted at http//nodal.ercot.com/readiness/rq/docu
  ments/index.html under Key Documents

15
Data Collection Details - Sub Synchronous Data

• Sub Synchronous data will be required of Resource
  Entities that have already collected this data
• For Resource Entities that do not have this data
  available, it will be required at a later time if
  their site is impacted by / included in a
  Reactive Management Study\
• Note that REs can follow current RFPs by
  reviewing the status updates provided to the
  Regional Planning Group (RPG)
• RFP for Study may define additional data from
  REs beyond that which is requested in the
  current RARF form
• There are no changes to this RARF tab

16
Data Collection Details - Load Resource
Registration Changes

• NPRR162 - Change the Sign Convention of Net Real
  Power Consumption, LPC and MPC of Load Resources
  (formerly titled Change the Sign Convention for
  Load Resources)
• Previously Load Resources Have submitted these
  values as negatives number to signify consumption
• ERCOT systems require that these be expressed as
  positive numbers
• ERCOT has temporarily changes this in the model.
  
• Load Resources need to officially make this
  modification to their Load RARF
• ERCOT requires that each Load Resource be mapped
  to a physical TSP load
• ERCOT will compile information it has available
  and contact each registered Load Resource Entity
  to confirm and update their Load RARF

17
Next Steps

• All non-PUN / Non-Wind sites must send an email
  to nodalmarkettransition_at_ercot.com signing up
  for either the June Submittal Window or the
  September Submittal Window by 6/8/09
• Current Sign-ups of Non-Pun / Non-Wind for June
  Window
• CITY OF GARLAND
• GEN TEX POWER CORP
• LOWER COLORADO RIVER AUTHORITY
• LUMINANT GENERATION COMPANY LLC
• OAK GROVE MANAGEMENT COMPANY LLC
• BIG BROWN POWER COMPANY LLC
• COLLIN POWER COMPANY LLC
• SANDOW POWER COMPANY LLC
• TRADINGHOUSE POWER COMPANY LLC
• VALLEY NG POWER COMPANY LLC

18
Whats Next - June Window Schedule

• Receive Audit Report and pre-populated RARF week
  of 6/8
• Conference call with Account Managers starting
  week of 6/15
• Iteration 1 corrections due 7/13/09 (20 business
  days)
• Iteration 2 corrections (if needed) due 8/12/09
  (15 business days)
• Iteration 3 corrections (if needed) due 9/1/09
  (10 business days)

19
Whats Next - September Window Schedule

• Kick off for September Window 8/28/09
• Receive Audit Report and pre-populated RARF
  9/1/09
• Conference call with Account Managers starting
  week of 9/8
• Iteration 1 corrections due 9/30/09 (20 business
  days)
• Iteration 2 corrections (if needed) due 10/27/09
  (15 business days)
• Iteration 3 corrections (if needed) due 11/16/09
  (10 business days)

20
Whats Next Remaining MP-10 Activities

• This will be further detailed at a future WebEx
• Background
• MP-10 began in 2008 with initial validation of
  one-lines, gen site topology and mapping to EPS
  meter(s) and resource node(s)
• REs were sent MP-10 and asked to respond with
  required changes
• Early 2009 ERCOT executed changes and in some
  cases identified re-work required by REs
• September 2009 (Post SEM Go Live) REs will be
  asked to
• Perform final verification on changes made by
  ERCOTltORgt
• Perform re-work so that ERCOT changes can be
  completed

21
Next Steps Updates and Communication

• ERCOT will be hosting a market call every 2 weeks
• Standing Agenda
• Project Updates
• Production quality metric
• Common issues / Frequently Asked Questions
• QA
• These meetings will be our primary means of
  communication
• These meetings will continue to be posted to the
  Registration and Qualification calendar at
  http//www.ercot.com/committees/nodal/rq/ The
  next Registration Market Call will occur on
  Friday 6/05/09
• All questions should be routed to
  nodalmarkettransition_at_ercot.com
• Questions sent directly to your Account Manager,
  should also copy nodalmarkettransition_at_ercot.com
  as well

22
QA / Open Forum

• QA / OPEN FORUM