1 / 15

Interchange Distribution Calculator Working Group (IDCWG) Update

The IDCWG February update covers meetings, education/testing sessions, data submission improvements, CO updates, and outstanding items related to energy distribution. Stay informed on the latest developments and proposed changes.

eddiehoward
Download Presentation

Interchange Distribution Calculator Working Group (IDCWG) Update

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Interchange Distribution Calculator Working Group(IDCWG)Update NAESB BPS Yasser Bahbaz – IDCWG Chair February 15th, 2012

  2. IDCWG Update • Meetings/Conference Calls • IDC Change Order Updates • Other IDCWG Items • GTL Update

  3. Meetings/Conf Calls • January 31st, February 1st ,Redwood CA (OATI) • March, CO 283 Education/Testing– Not a formal IDCWG meeting – OATI Offices • March 21 – 22nd Charlotte, NC (DUKE) • May 16 – 17th Atlanta GA (NERC) - BPS Joint Meeting

  4. Implemented • CO 329: Load Adjustments at the time of TLR 5 Issuance • CO 337: PJM Request to Access and Use IDC Data • SDX CO 09: Addition of De-rate Validation to WebSDX

  5. Development/Testing • CO 322: PFV Generation Priority Submissions * • Will be moved to development once a final methodology is reached at BPS. • CO 330: Authorization of OATI Use of IDC Data for DOE Studies • CO 331: IDC Interface to NAESB Web Registry • CO 333: Include MF and NNL on TLR Event History Display • CO 336: Changes to IDC Factor Calculation Timing * • Will be moved to development once PARs (ONT – MI) are operational

  6. Development/Testing • CO 338: Default Timing for TLR Levels 1 and 0 • CO 340: Effective Date on Market Coordinated Flowgates • CO 341: MISO and PJM ED6/7FN Transfer to IDC • SDX CO 08: Remaining GUI Changes

  7. DRAFT/Evaluation • CO 326: PFV Metrics * • Maybe revised after a final methodology is reached at BPS. • CO 328: Intra Hour Tag Curtailment • This change is involved. • CO 332: Changes to Manitoba EAR Tag in IDC • ORS approved the CO during last week’s meeting. • BOF CO 16 -New PSSE version format change (From PSSe Version 30 to Version 32)

  8. Other Items • CO 283 Summary Write-up is complete and submitted to NAESB BPS for reference use. • A Request for Initiation of a NAESB BP Standard regarding TLR 5B re-allocation is submitted to NAESB and is being reviewed. • Increasing number of data request type from RCs to IDCWG and OATI. IDCWG will propose adding the capability to query data report directly from IDC.

  9. IDCWG Update GTL Update

  10. IDCWG Update GTL Data Submission

  11. IDCWG Update • Most entities are now submitting close to full set of data for generation and load. • Calculation testing may take place with this data. • Entities will be able to submit data every 15 minutes at minimum. • OATI may interpolate data for those who can’t submit data every 5 minutes.

  12. IDCWG Update Change Order 283 Status

  13. IDCWG Update • During the upcoming March session, OATI will provide an educational session on GTL. We plan to perform calculation testing during this session. • Calculation testing may now take place with the submitted data. • Comparison of Real Time flowgate flow versus calculated impact on the flowgate by GTL. • Comparison of GTL calculated Market GTL impacts versus those Market Flows calculated by the market entities. • CO 322 (Generation Priority Submission) is evaluated and will be developed once a BPS solution is finalized.

  14. IDCWG /BPS Outstanding Items • BPS to categorize its audience for the purpose of viewing reliability metrics (CO 326) • With all the real time data being used for curtailments, is there a discussion about making TLR process run more than just once an hour? • On CO 322 (Generation Priority Submission), it is assumed that only RC or BA will submit the priorities. Is there a need to design the registration process on more granular level (TO, GO, etc…)?

  15. IDCWG Update ?

More Related