1. 6/21/2007 TPTF: Baselines 1&2 WP and CI Baselines 1 and 2 White Papers and Change Items Diran Obadina

2. 2 TPTF: Baselines 1&2 WP and CI 06/21/07 PURPOSE To seek TPTF concurrence that the White Papers and Change items are needed for go-live

3. 3 TPTF: Baselines 1&2 WP and CI 06/21/07 BASELINE 1 WHITE PAPERS AND CHANGE ITEMS IDA002 Time Standards DST IDA004 Power Flow Consistency Requirements IDA007 Load Rollover IDA008 State Estimator Maintenance IDA009 SPS and RAP Modeling IDA013 Seasonal Temperature Hydrogen CI 0057 Move Resource Parameters from Registration to MMS CI 0067 Non-Spin Deployment

4. 4 TPTF: Baselines 1&2 WP and CI 06/21/07 BASELINE 1 WHITE PAPERS IDA002 Time Standards DST Description: Standardize time zone (GMT) and time format representation within the ERCOT Nodal Project. Cost Drivers: 200+ displays and queries modification within MMS to support the time format representation IDA004 Power Flow Consistency Requirements Description: The purpose of this paper is to ensure all power flow applications have a set of consistent solution parameters and settings, such as convergence tolerances, starting tolerances, and shift factors based on distributed load reference. Cost Drivers: All vendors are able to meet the power flow settings and parameters requirements. Shift factors based on distributed load reference is not in the base product of EMS and MMS vendors.

5. 5 TPTF: Baselines 1&2 WP and CI 06/21/07 BASELINE 1 WHITE PAPERS IDA007 Load Rollover Description: This white paper standardizes, across all Nodal systems, the manner in which Load Rollover should be implemented. Cost Drivers: MMS vendor does not have load rollover in their base product.

6. 6 TPTF: Baselines 1&2 WP and CI 06/21/07 BASELINE 1 WHITE PAPERS IDA009 SPS and RAP Modeling Description: The purpose of this white paper is to describe the handling of Special Protection Scheme and Remedial Action Plan (SPS/RAP) in various Nodal systems. Cost Drivers: New Object type to be created in NMMS. MMS vendor does not have SPS/RAP handling in their base product (MMS will ignore the constraint violations for those with an associated SPS/RAP scheme) IDA013 Seasonal/Temperature/Hydrogen Pressure based Reactive Capability Curves Description: This paper describes the modeling of reactive capability curves. Cost Drivers: MMS vendor does not handle reactive capability curve in their base product, only a high and lower MVAR limit.

7. 7 TPTF: Baselines 1&2 WP and CI 06/21/07 Baseline 1 Change Items CI 0057 – Move Resource Parameters from Registration to MMS Description: Allow market participants to update certain resource parameters near real time. MMS will present a market facing interface for market participants to input resource parameter data. These updated parameters will be provided to other non-MMS applications within the Nodal System. Cost Drivers: MMS to provide interface to collect and validate market participants’ input resource parameters. EIP to provide interface between MMS and other Nodal Systems. CI 0067 Non-Spin Deployment Description: This change item describes the TAC approved process of non-spin deployment in Nodal. Cost Drivers: MMS to create new interface, data validation and processing for the non-spin deployment process. The partial deployment requires DAM clearing price for resources therefore it is better done in MMS. EMS does not have any cost impact (positive or negative) as NS deployment is in the base product and we are not proposing to remove it, just leave it disabled.

8. 8 TPTF: Baselines 1&2 WP and CI 06/21/07 Baseline 2 White Papers and Change Items IDA003 Combined Cycle Unit Modeling IDA015 NMMS Data Interfaces to Other Systems IDA021 Load Models IDA041 Split Generation Resource Modeling IDA045 LMP Accuracy Standards CI 081 MP ID Management

9. 9 TPTF: Baselines 1&2 WP and CI 06/21/07 Baseline 2 White Papers IDA003 – Combined Cycle Plants Description: Paper describes how Combined Cycle plants will be modeled in the various Nodal systems. Cost Drivers COMS – registration and settlements NMMS – linking physical and logical representations of CCUs (change CIM model), EMS, MMS – handle the same CCU modeled as physical and logical within the system (EMS - logical in LFC, physical everywhere else, MMS – physical in OS, logical everywhere else). EIP – Various interfaces

10. 10 TPTF: Baselines 1&2 WP and CI 06/21/07 IDA015 – NMMS Interfaces to other systems Description: This whitepaper describes NMMS interfaces to other systems and how those systems will manage multiple CIM models NMMS –> EMS, MMS: NMMS creates CIM models NMMS -> OS: A list of equipment and breakers that affect the status of that equipment OS -> NMMS: NMMS will be able to generate future bus/branch models (CRR/Planning) with approved outages NMMS -> CRR/Planning: NMMS generates future bus/branch models Cost Drivers (awaiting confirmation from Projects):

11. 11 TPTF: Baselines 1&2 WP and CI 06/21/07 Baseline 2 White Papers IDA021 – Load Models Description: Purpose of the white paper is to address load modeling issues identified during the State Estimator improvement project. Cost Drivers (awaiting confirmation from Projects): Non-conforming load – NMMS, EMS, and EIP SE Load adaptation logic – EMS Increase number of load schedules and hourly schedule for each load – no impact (may be performance implication on EMS)

12. 12 TPTF: Baselines 1&2 WP and CI 06/21/07 Baseline 2 White Papers IDA041 – Split Generation Resources Description: This paper describes how Split Generation Resources will be modeled in various Nodal systems. Cost Drivers (awaiting confirmation from Projects): NMMS – Represents the same generating resource in two ways: logical (split generation) and physical – CIM model change MMS – OS only (OS – physical, rest – logical) EMS – LFC – logical, rest physical COMS – Registration

13. 13 TPTF: Baselines 1&2 WP and CI 06/21/07 Baseline 2 White Papers IDA045 – LMP Accuracy Description: This paper describes various rules for LMP checking. The checking should be done automatically, no fewer than once daily. Report will be generated if any suspected conditions are found. Cost Drivers ERCOT personnel to take on this task due to better understanding of business requirements.

14. 14 TPTF: Baselines 1&2 WP and CI 06/21/07 Baseline 2 Change Items CI081 – Market Participant Identity Management (1 of 2) Description: Texas Nodal requires a level of sophistication in how it manages the identities of external users that goes beyond the current Zonal solution. Cost Drivers: In general managing user identities involves: Creating identities for each Market Participant’s users Defining policies that govern how Market Participant users access ERCOT content Guarding ERCOT’s content according to the access policies Providing identity information to the component Nodal applications

15. 15 TPTF: Baselines 1&2 WP and CI 06/21/07 CI081 – Market Participant Identity Management (2 of 2) Cost Drivers (con’t): The current external identity management solution is in operation without incident but the drivers for an enhanced Nodal solution are to: Address inefficiencies that exist in the current solution Incorporate substantial change needed to manage the volume and granularity of access necessary to support the Nodal systems. Align with changes planned to manage internal ERCOT identities (Single Enterprise Standard) Consolidate and automate User Security Administration tasks so that one group can manage all ERCOT identities Delegate User Security Administrators (USA) tasks related to Market Participant users to Market Participant USAs Extend access controls to web services Enhance the infrastructure components that guard ERCOT content and provide access to external users Essential for Go-live: Essential