Request Summary
WRAP Tag Contract and MISC Info Identifier on e-Tags designated for WRAP
Co-sponsors
Description Of Issue
WRAP related energy transfers are not currently identified on e-Tags using a standardized contract type or miscellaneous token/value. As a result, WRAP transactions may be operationally indistinguishable from bilateral or market-based energy schedules.
This lack of clear identification reduces real-time operational visibility for Balancing Authorities (BA), Reliability Coordinators (RC) and real time 24/7 trading desks, and increases reliance on manual interpretation, particularly during system stress events. It also creates challenges for emerging organized markets, such as EDAM and Markets +, which can rely on structured e-tag attributes to validate, and process scheduled energy e-Tags.
Proposed Solution
Establish a WRAP specific e-Tag identifier through either:
- A distinct contract type
- A standardized miscellaneous token/value indicating a WRAP transaction.
This identifier would be applied consistently across all WRAP participants and used exclusively for WRAP related energy transfers, similar to the existing identification approach used for NWPP Sharing Reserves transactions.
For Example:
Contract = “NWPP RS” (Suggestion: “WRAP RS“)
MISC Token Info = WECC_Reserve_Responsible_Entity = “SCL”
MISC Token Info = WECC_Reserve_Responsible_Entity_Type = “BA”
Uploaded e-Tag for example
Specific Document And Language
No specific language that City Light can point to change currently but would suggest any applicable WPP documents that include WRAP implementation guidance and any WPP e-Tagging or scheduling documentation (WRAP Operational documentation) that defines required or recommended tagging attributes for program-related transactions.
Suggested Language Update
City Light would suggest adding language requiring that all WRAP-related energy transfers be identified on e-Tags using a WRAP specific contract type and/or a standardized miscellaneous token/value, clearly indicating the transaction as a WRAP obligation.
The language should specify that this identifier is required for all WRAP transactions and is intended to provide clear operational visibility, support consistent treatment by BA and RC, and enable proper recognition by organized markets such as EDAM and Markets +.
Benefits
Implementing a WRAP specific e-Tag identifier will improve operational clarity and consistency across the Western Interconnection. Balancing Authorities and Reliability Coordinators will be able to quickly and reliably identify WRAP related energy transfers and distinguish them from bilateral or markets-based schedules. This would reduce reliance on manual interpretation during real-time operations and system stress events.
This change will also support integration with organized markets such as EDAM and Markets +. Clear identification of WRAP transactions will allow markets systems to properly recognize and process WRAP energy, reducing the risk of misclassification, settlement errors, or unintended overlap with market-clearing energy.
In addition, standardized tagging will improve transparency for compliance monitoring, post-event review, and audit purposes, supporting consistent treatment of WRAP obligations as the program continues to mature.
Data Or Information
WRAP transactions are expected to occur primarily during periods of system stress, when operational clarity is most critical. During these events, operators rely on standardized e-Tag attributes to quickly understand the purpose of schedule energy transfers.
Unlike NWPP Sharing Reserves transactions, which are clearly identified through a defined contract type and miscellaneous token/value, WRAP e-Tags currently lack a comparable standardized identifier. As WRAP obligations increase under a binding program structure and organized markets such as EDAM and Markets + are implemented, the absence of clear WRAP identification increase the risk of misclassification or inconsistent treatment of WRAP energy schedules.
Although WRAP transactions may be infrequent under normal conditions, their importance is high given their role in maintaining system reliability during extreme events.