Develop an OASIS process to coordinate a defined group of requests (linked requests) across multiple systems.  
Note: Task Force still needs to decide whether to recommend scenario 1 or scenario 3.  Once decision is made, changes will need to be incorporated into this document.

The NAESB Business Practices should establish an OASIS process for coordinating the reservation of transmission service across multiple transmission systems for a defined group of requests (e.g. “linked requests”).  The process shall:
1.	Require a customer to define the group of requests that are to be coordinated (“linked requests”)
2.	Accommodate any number of requests to be coordinated (single or multiple requests on one system linked with single or multiple requests on other systems)
3.	Unless otherwise prohibited, permit any combination of the following request types:
a.	Yearly Firm PTP
b.	Monthly Firm PTP
c.	Monthly Non-Firm PTP
d.	Firm Network Service
e.	Monthly Non-Designated (secondary) Network Service
4.	Require all short-term PTP requests be submitted pre-confirmed.
5.	Permit one or more of the requests to be a concomitant request.  (The procedure should not release the capacity for the undesignated DNR until the “coordinated” final state capacity is determined.)
6.	Permit a customer who is granted part of the requested capacity on a linked request to adjust capacity on any and all requests/reservations to values lower than requested, including nullification of all linked requests.  The customer may elect any combination of capacity values as long as the adjusted value of each does not exceed the capacity granted by the respective TPs.  (For example, if three requests were linked for 125 MW each, and two of the TPs granted 125 MW but the third counteroffered at 107 MW, the customer could rebid the 107 MW to 103 MW and adjust one of the other reservations to 100 MW and adjust the other to 103 MW.  Alternately, the customer could withdraw the counteroffered request and adjust the other two requests/reservations to zero.)
Permit a practice wherein if one TP denies all capacity for a request, each of the TPs will be deemed to deny the remaining components of a linked request.
8.	Permit regional alliances to establish a mechanism wherein a single request is processed for transmission service on multiple transmission providers.  Such an alliance must allow  linked requests that extend beyond the boundaries of the alliance.
9.	Coordination procedure will extend only for evaluation and processing of linked requests.  After initial coordination is completed (true up), each of the resulting reservations shall be treated as any other reservation.  
10.	The procedure shall include audit functionality.
11.	The process should permit coordinated studies, in accordance with the pro-forma OATT, but it should not require performance of coordinated studies and it should not define the study process itself. 
12.	No subsequent processing of confirmed linked requests until the link is broken (true up is completed):  
a.	 No release of parent firm capacity on a firm redirect
b.	No subsequent resales of linked requests
c.	No subsequent redirects of linked requests
d.	No release of DNR capacity of linked concomitant requests
e.	No tagging of linked requests until true up is completed
f.	No processing of renewal requests until true up is completed
13.	Linked transmission requests should not be denied due to time zone differences on stop/start times.  
•	With regard to time zone differences, the scope of work for this annual plan item shall be limited to addressing this item 13 and item 2 in NITS on OASIS below.
14.	Linked requests should not be denied due to megawatt differences
The process shall not:
1.	Require any transmission customer to reserve transmission service in excess of the lowest capacity granted by any transmission provider.
2.	Require transmission providers to query any other transmission provider’s OASIS.
3.	Require transmission providers to validate consistency of product names and attributes across linked requests.

Recommendation to OASIS subcommittee with respect to NITS on OASIS:

1.	DNR requests should not be denied due to time zone differences between network service request and the corresponding (required) request(s) on other TP’s system(s).  
2.	Subcommittee should establish TP and Customer response times for the network service product types, which may be included as linked requests.