NAESB OS Assignment

NAESB OS Clarification DRAFT Jan. 14, 2013

NAESB Annual Plan Item: 5.d. Create a new OASIS mechanism that allows for the merger of like reservations without the use of the resale mechanism (R09015).

R09015, “Request for Initiation of a NAESB Standard for Electronic Business Transactions”, refers to the proposal for NAESB to propose this feature in OASIS. This request was submitted by Puget Sound Energy in September 2009.

R09015 Request Summary: Transmission customers may from time to time have a portfolio of transmission service reservations from a single provider on a single path. For ease of tracking and efficiency, customers desire to combine or merge like reservations into a single reservation. Under existing OASIS business practice and protocols, customers must use the Resale mechanism to merge two or more “like” reservations under a single assignment reference (AREF) number. In other words, customers sell their reservations back to themselves. This is not desirable as (1) using the Resale function presents a false picture of what is happening, and (2) transmission providers must report all Resales and establish transmission reassignments agreements with the Assignees (recipient of the Resales, including resales to self). This request for a new OASIS mechanism (a combination of business practices and protocols) that allows for the merger of like reservations without the use of the resale mechanism and resulting additional contracting and administrative requirements (for additional details refer to FERC Order 890).

Current OASIS Feature for Resales - transassign OASIS Resale function allows transmission reservation holders to enable another OASIS customer to have temporary “scheduling rights” on another’s reservation. This function uses the transassign template, which creates a reservation request type of “Resale”. Resale is a secondary transmission market request submitted to a customer (Assignee) by the Reseller. Templates are what is used to query information that will be downloaded or to upload information to the TP’s OASIS. In addition to this, the transassign allows the transmission reservation holder to combine several like PTP reservations (type and path) into a single reservation, through a feature called “Add/Edit Reassign”. The purpose is to allow ease of resale (resale using one transaction instead of multiple). This “Add/Edit Reassign” (or “aggregation”) feature under transassign is used even when there is no associated resale to another party.

Proposed OASIS Feature – “transaggregate” In order to combine multiple like reservations into one reservation outside a resale, create a new OASIS function that allows transmission reservation holder to do so through a feature similar to “Add/Edit Reassign” of the transassign (Resale) template. Instead of using the transassign template, which identifies the request type as Resale (among other

1 things), the new template, perhaps called “transaggregate”, could identify the request type as “Aggregate”.

WesTTrans OASIS subcommittee: The following appear to be topics included in previously proposed requirements of reservations (TSR) of this subcommittee effort. 1. Same NERC priority. BPA allows resale of Firm only. How is NERC priority identified on TSRs? 2. Same TS_Class (i.e. Firm, Non-Firm). BPA allows resale of Firm only. 3. Service Increment (i.e. Hourly, Weekly, Daily, Monthly, Yearly). BPA allows short-term to be grouped with short-term; and long-term grouped with long-term. 4. Same POR and same POD for Short-term groupings, and same Source and same Sink for Long-term groupings. 5. TSRs being submitted for aggregation should have the same Start and Same Stop Time and Dates specified on the aggregation request. For BPA, allows for different Start and Stop Time and Dates, as long as the portions of each TSR to be grouped can accommodate the Start and Stop Time and Dates of the grouping. 6. Confirmed 7. Allow for profiling TSR(s) to be aggregated 8. Allow aggregated TSRs to retain original pricing structure 9. Allow partial capacity to be aggregated.

Some features of Aggregated TSRs: 1. No Rollover Rights 2. Each TSR in Aggregated TSR retains its original Service Increment. 3. Aggregated TSRs are not subject to competition 4. Aggregated TSR must have some identifier to original TSR (such as “Aggregated Ref” field which would accommodate multiple AREF references).