1 / 9

SEWG Nodal Load Aggregation

SEWG Nodal Load Aggregation. Calvin Opheim February 16, 2009. Outline. Zonal LSEGUNADJ Bill Determinant Nodal LSEGUNADJ Bill Determinant Data Aggregation Rewrite Adding a new attribute to LSEGUNADJ Adding a new attribute to other Load Bill Determinants. LSEGUNADJ - Zonal.

sawyer
Download Presentation

SEWG Nodal Load Aggregation

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. SEWG Nodal Load Aggregation Calvin Opheim February 16, 2009

  2. Outline • Zonal LSEGUNADJ Bill Determinant • Nodal LSEGUNADJ Bill Determinant • Data Aggregation Rewrite • Adding a new attribute to LSEGUNADJ • Adding a new attribute to other Load Bill Determinants

  3. LSEGUNADJ - Zonal For Zonal Settlements LSEGUNADJ is saved in the form of: LSEGUNADJ_<REP>_<QSE>_<Profile ID>_<DLFC>_<UFE>_<CM>_<TDSP>_<SUBUFE> Where: DLFC – Distribution Loss Factor Code UFE – Settlement UFE Zone CM – Congestion Management Zone SUBUFE – UFE Analysis zone

  4. LSEGUNADJ - Nodal For Nodal Settlements Per previous discussion with SDAWG, the SUBUFE attribute will be eliminated from all nodal generation and load billing determinants meaning LSEGUNADJ is saved in the form of: LSEGUNADJ_<REP>_<QSE>_<Profile ID>_<DLFC>_<UFE>_<CM>_<TDSP> Where: DLFC – Distribution Loss Factor Code UFE – Settlement UFE Zone CM – Congestion Management Zone

  5. Data Aggregation Rewrite System Performance Improvements The existing zonal data aggregation processes have been rewritten in order to improve performance necessary to handle the increased demands of nodal settlement and the increased volume of 15-minute settlement interval data from Advanced Meters. An outcome of this effort is that a new attribute is available to the LSEGUNADJ cut called Method. The Method attribute is used to determine if the LSEGUNADJ cut is based on: • Usage data spanning the Operating Day (Method = UH) • Historical usage (no usage for the Operating Day but usage within 365 days prior to the Operating Day) (Method = EH) • No usage data for the Operating Day and no usage data within 365 days prior to the Operating Day (Method = ENH)

  6. Add Method Attribute to LSEGUNADJ Should Method Attribute be added to LSEGUNADJ? • Pros: • This involves no coding changes for ERCOT • Should make shadowing ERCOT’s calculations easier since the three usage types (actual, estimated, or default) are calculated and stored in separate LSEGUNADJ cuts • Cons: • Would result in additional LSEGUNADJ data cuts since the existing zonal calculation is performed for all usage types combined to create a single LSEGUNADJ cut • Initial settlements would have a 50-60% increase in LSEGUNADJ cuts • Fairly small increase (<5%) in LSEGUNADJ cuts for all other settlements (Final, Resettlement, and True-up)

  7. Add Method Attribute to Other Load Billing Determinants To LSEGDL, LSEGTL, LSEGUFE, LUFE, and NBLOAD? • Pros: • This involves no coding changes for ERCOT • Could track the usage from the underlying LSEGUNADJ cuts to each of these cuts • Cons: • Would result in additional load data cuts since the existing zonal calculations are performed for all usage types combined • Initial settlements would have a 50-60% increase in these load cuts • Fairly small increase (<5%) in these load cuts for all other settlements (Final, Resettlement, and True-up) Does this add value or should these bill determinants be saved without the Method attribute?

  8. Example LSEGUNADJ with Method attributes: LSEGUNADJ_<UH> 1.1111, 2.2222, 3.3333 LSEGUNADJ_<EH> 4.4444, 4.6666, 6.1111 LSEGUNADJ_<ENH> 0.3333, 0.4444, 0.5555 LSEGDL with Method attributes: LSEGDL_<UH> 1.2109, 2.4321, 3.6543 LSEGDL_<EH> 4.8765, 5.0987, 6.7654 LSEGDL_<ENH> 0.3654, 0.4876, 0.6001 LSEGDL with no Method attribute: LSEGDL 6.4528, 8.0184, 11.0198

  9. Questions? ON OFF

More Related