1 / 9

Electronic Scheduling Work Group

This meeting agenda covers FERC Order 771, questions for WECC on WIT checkmarks, WREGIS, and vendor-vendor testing for planned outages. It also proposes a change to WIT Tag Authority, discusses the meaning of checking a checkbox in WIT, and highlights the importance of confirming NSI and NAI values.

komala
Download Presentation

Electronic Scheduling Work Group

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. Electronic Scheduling Work Group Interchange Scheduling and Accounting Subcommittee January 16, 2013 John Schaffroth

  2. Agenda • FERC Order 771 • Questions for WECC on WIT checkmarks • WREGIS • Vendor-vendor testing for planned outages

  3. FERC Order 771 • FERC access to all e-tags • Propose a change to WIT Tag Authority to deny e-tags that do not include FERC on the Carbon Copy list.

  4. Questions to WECC about WIT checkmarks • What does it mean to check a checkbox in WIT? • Home scheduling system agrees with the WIT value. • INT-021-WECC-1 WR2 “….electronic confirmation process is the primary means to confirm NSI…” And WR3 states: “…electronic confirmation process as primary means to confirm NAI…” • Your value matches your neighbor’s value. • BAL-006 R4.1 states, “Each Balancing Authority, …, shall agree with the Adjacent Balancing Authority…” And INT-003 R1 states, “Each Receiving Balancing Authority shall confirm Interchange Schedules with the Sending Balancing Authority as received from the Interchange Authority…” • NAI specific; you have sent your values to WIT. • INT-021-WECC-1 WR4 states, “Each Balancing Authority shall provide hourly NAI data to the electronic confirmation tool for each of its’ adjacent Balancing Authorities…”

  5. Checkmark questions (cont.) • Current WIT functionality does not provide the option of checking out a 0mw value. How do you show compliance? • INT-003 R1 states, “Each Receiving [BA] shall confirm interchange schedules with the Sending [BA] as received from the Interchange Authority…” • INT-009 R1 states, “The Balancing Authority shall implement Confirmed Interchange as received from the Interchange Authority.” • BAL-006 R4.1 states, “Each [BA], by the end of the next business day, shall agree with its Adjacent [BA] to the hourly values of [NSI] and the hourly integrated megawatt-hour values of [NAI].” • INT-021-WECC-1 WR2 states, “Each [BA] shall use electronic confirmation process… a primary means to confirm NSI for preschedule day checkout…, next hour checkout…, current hour checkout upon change, past hour checkout in current day, and past day checkout.”

  6. Checkmark questions (cont.) • How do you show compliance if the NSI value does not change from preschedule to real-time, to after-the-fact? • INT-003 R1 states, “Each Receiving [BA] shall confirm interchange schedules with the Sending [BA] as received from the Interchange Authority…” • INT-009 R1 states, “The Balancing Authority shall implement Confirmed Interchange as received from the Interchange Authority.” • INT-021-WECC-1 WR2 states, “Each [BA] shall use electronic confirmation process… a primary means to confirm NSI for preschedule day checkout…, next hour checkout…, current hour checkout upon change, past hour checkout in current day, and past day checkout.”

  7. Used to track proof of energy delivery Query run to pull e-tags from WIT that contain the required token Awareness WREGIS

  8. Vendor-vendor testing • Incident where a non-OATI customer did not have the new webSAS URL • Vendor-vendor testing could prevent this • This affects all WECC BAs if a non-OATI customer can’t approve USFs

  9. End • Questions

More Related