Interchange Distribution Calculator Working Group (IDCWG) Update NAESB BPS Yasser Bahbaz – IDCWG Chair September 13 th, 2012

IDCWG Update Meetings/Conference Calls IDC Change Order Updates Other Items GTL Update Action Items

Meetings/Conf Calls May 16 – 17 th Atlanta GA (NERC) - BPS Joint Meeting August 15 th – 16 th (MISO, St Paul) September 24 th – Conference Call October 16 th (8 – 5) – 17 th (8 – 12), Las Vega, NV BPS Joint Meeting October 16 th, 1 – 5 pm

Implemented CO 346: TLR Auto Acknowledgment IDC will be modified in such a way that each sink impacted Reliability Coordinator can set up to automatically acknowledge the TLR actions based on configurable time intervals after a new TLR instance CO 347: IDC TLR Data Request for New York Transmission Owners CO 348: Changes to IDC webData Interface CO 349 TLR Acknowledgement/Curtailment Archival

Development/Testing CO 322: PFV Generation Priority Submissions Will be moved to development once a final methodology is reached at BPS. Will be revised as needed. CO 328: Intra Hour Tag Curtailment IDCWG has proposed and approved for evaluation a different solution than previously drafted and evaluated. CO 330: Authorization of OATI Use of IDC Data for DOE Studies

DRAFT/Evaluation CO 326: PFV Metrics Will be revised after a final methodology is reached at BPS. CO 350: Increase the Initial Limit for NNL Relief Provided During TLR Issuance CO 351: Update the Flowgate GLDF Display to Show PJM Historic Control Areas CO 352: Various Enhancements to the NNL Re-Dispatch Worksheet CO 353: PSEC-SOCO Dynamic Tags CO 354: Sending IDC TLR ID to SPP Via webData Interface CO 355: Make Information Flowgates Selectable in Study TLR Mode

Other Items IDCWG discussed the impact of the swing bus location (in TVA) within the IDC model. The working group is evaluating moving the swing bus to an area that is less reliant on IDC TLRs to manage congestion. IDCWG discussed and supports TVAs request of creating pseudo BAs to enhance impact calculation of IPPs serving load within TVA. IDCWG supports and recommends the retirement of the Flowgate Administration, the Parallel Flow Calculation Procedures and the Reliability Coordinator Reference Documents. These documents content are covered in the SDX and IDC user manuals.

IDCWG Update GTL Update

IDCWG Update Action Items

Metrics Available to BPS Due to the sensitivity of the data that we foresee involved in the Reliability Metrics, IDCWG/ORS is not in position to share the data with the BPS. IDCWG recommends that metrics be prepared for commercial purposes to be used by the BPS.

Metrics Available to BPS In general data can be provided with flowgate owners and flowgate IDs masked. Sources and Sinks of transfers will also be masked. Data will be shown in statistical format, percentage changes and ratios – no actual magnitude of data would be shown. Some of the metrics that can be shared are but not limited to, Load metric performance per BA or Load Zone. This would be shown in % and would be comparison of forecast to actual. Flowgate Component in percentage by a given anonymous flowgate Total GTL native oBy Firm and Non Firm Total GTL Transfer oBy Firm and Non Firm Total Tags oBy Firm and Non Firm Curtailment difference % between IDC and GTL (Native and Transfer) and firmness. Mask the flowgate Show difference between IDC and GTL for each flowgate by component. When CO 326 is re-opened for changes to accommodate the latest PFV methodology, consideration for these features will be added.

Handling of One Offs EAR like modeling This will be handled on a case by case basis. IDCWG will make a decision on each exception and grant the use of the exception as they come. Pseudo Tied Resources There is a logic to manage these types of resources in the PFV methodology as drafted by BPS. Market Area External Gens This is handled within the models. – CO 283 this. DC Ties CO 283 considers the flow and the status of each DC Tie. Par Taps and VFT CO 283 considers the flow and the status of these equipments. IDCWG intends on drafting a guideline of how to model these exceptions in IDC and consequently PFV logic. Any other exception will need to be brought up to the IDCWG to come up with best approach to model and manage the exception.

Generator Modeling It is expected that all resources modeled in the EMS be included in the IDC model. The calculation and benchmarking actual vs. calculated will assume that EMS and IDC models are consistent with each other.

IDCWG Update