Business Practices for Open Access Same-Time Information Systems (oasis) Standards & Communication Protocols Business Practices Requirements




старонка5/11
Дата канвертавання24.04.2016
Памер0.7 Mb.
1   2   3   4   5   6   7   8   9   10   11

002-4.2.13.4 Secondary Sales – Off OASIS
The sale or assignment of rights from one Transmission Customer to another does not have to be conducted on OASIS. However, the Transmission Customer acting as a Secondary Transmission Provider is obligated to notify the Primary Transmission Provider of all sales or assignments of transmission rights to a third party. The transassign Template shall be used by the Secondary Transmission Provider to convey this sale/assignment information to the Primary Provider. The transassign Template allows the Secondary Transmission Provider to submit all information related to the secondary market sale. The REQUEST_TYPE of "RESALE" is directly implied by use of the transassign Template. The REASSIGNED_REF, REASSIGNED_CAPACITY, REASSIGNED_START_TIME and REASSIGNED_STOP_TIME Data Elements identify the transmission reservation(s) currently held by the Secondary Transmission Provider, and the amount of capacity over time from each such reservation to be transferred to the secondary market Customer. The aggregation of all REASSIGNED_xxx Data Elements must match the capacity and time frame of the secondary transmission request as specified in the CAPACITY_GRANTED, START_TIME and STOP_TIME Data Elements of the "RESALE" transaction. The IMPACTED attributed will be incremented for each reservations referenced by the REASSIGNED_REF Data Elements.
002-4.2.13.5 Renewal
Requests by the Transmission Customer to renew their transmission reservation, subject to the terms of the Provider's Tariff, should be submitted using the REQUEST_TYPE of "RENEWAL" and specify the ASSIGNMENT_REF of the request to be renewed in the new request's RELATED_REF Data Element. This unique REQUEST_TYPE and association with the original request more clearly communicates, over OASIS, the intent of the Transmission Customer, and distinguishes requests for renewal of service from new requests by the same TC for additional service.
002-4.2.13.6 Displacement – No Right of First Refusal
Confirmed transmission reservations may be subject to displacement in the event competing, higher priority requests are received by the Primary Transmission Provider. If the original Customer does not have the right of first refusal and all capacity from the original, confirmed reservation is required to accommodate the higher priority request, the Primary Transmission Provider shall set the original reservation's STATUS to DISPLACED. The STATUS of DISPLACED indicates that the original reservation has been displaced in its entirety. A reference to the competing request that forced the displacement should be entered in the SELLER_COMMENTS field of the original reservation. If only a portion of the original, confirmed reservation's capacity is required to accommodate the higher priority request, the Primary Transmission Provider shall document the "recall" of reserved capacity from the lower priority, confirmed reservation by incrementing the IMPACTED counter on that reservation and posting on OASIS the amount and time frames over which the original reservation's capacity was reduced. The Transmission Customer may view all impacts to existing transmission reservations (e.g., partial displacements, secondary sales, etc.) using the reduction Template. A reference to the competing request that forced the displacement should be entered in the SELLER_COMMENTS field of the original reservation.
002-4.2.13.7 Displacement – With Right of First Refusal
Confirmed transmission reservations may be subject to displacement in the event competing, higher priority requests are received by the Primary Transmission Provider. If the Primary Provider's Tariff obligates, or the Primary Provider elects to grant the original Customer the right of first refusal, the original Customer shall be notified of the competing request. The Primary Provider shall set the original request's COMPETING_REQUEST_FLAG to Y and update the SELLER_COMMENTS with a reference to the competing requests ASSIGNMENT_REF. These changes will initiate electronic notification, provided the Customer has elected to receive such notification. If the original Customer elects to meet or exceed the terms and conditions of the competing request, that Customer shall submit a new reservation request using the transrequest Template specifying 1) the terms of the new request, 2) "MATCHING" for REQUEST_TYPE, and 3) the ASSIGNMENT_REF of their original reservation in RELATED_REF. If the Primary Provider accepts the MATCHING request, the Primary Provider shall set the STATUS of the competing request to "REFUSED" and set the STATUS of the original, confirmed reservation to "DISPLACED". The STATUS of DISPLACED indicates that the original reservation has been displaced in its entirety. If the original Customer does not elect to meet the terms of the competing request, the Primary Transmission Provider shall displace the original reservation, in whole or in part, in the same manner described for reservations that are not extended a right of first refusal. Once the disposition of the original reservation and the competing request is finalized, the COMPETING_REQUEST_FLAG shall be reset to "N" in the original reservation.
002-4.2.13.8 Deferral of Start of Service
The commencement of service for certain transmission reservations may be deferred by the Customer as provided by the Primary Provider's Tariff. Such deferrals of the start of service are to be treated as new requests. The Customer shall submit a new transmission reservation specifying 1) the new term of service being requested, 2) "DEFERRAL" for REQUEST_TYPE and 3) the ASSIGNMENT_REF of their original reservation in RELATED_REF. On approval of the request to defer the start of service, the original reserved capacity may be subject to "recall" by the Primary Provider. If the Primary Provider recalls all or a portion of the reserved MWs associated with the original request, the Primary Provider shall increment the IMPACTED counter in the original reservation and document the reduction in service via an appropriate OASIS posting viewable to the Customer with the reduction Template.
002-4.2.13.9 Alternate POR/POD
Transmission Customers may have the right to move to alternate points of receipt and/or delivery under the terms of the Primary Provider’s tariff. Customers holding confirmed transmission reservations may request the use of alternate points of receipt and/or delivery by a new transmission reservation using the transrequest Template. The new request shall specify 1) the terms of the new service requested, 2) "REDIRECT" for the REQUEST_TYPE and 3) the ASSIGNMENT_REF of their original reservation in RELATED_REF. On approval and confirmation of this new reservation, the Customer's rights to schedule transmission service under their original reservation may be reduced. If transmission rights under the original reservation are reduced, the Primary Provider shall increment the IMPACTED counter in the original reservation and document the reduction in service via an appropriate OASIS posting viewable to the Customer with the reduction Template.
002-4.2.13.10 Provider Recall
There are cases in implementing provisions of the Primary Provider's Tariff that the capacity reserved by a Transmission Customer may be reduced in whole or in part. The particular reasons for these reductions are Tariff specific. The Primary Provider shall provide a mechanism to post on OASIS any such reductions or "recalls" in reserved capacity. The Customer shall be notified of any and all such reductions in reserved capacity by the incrementing of the IMPACTED counter in association with those reservations that are reduced; the IMPACTED flag is viewable with the transstatus Template. Specific information regarding the exact nature of each reduction in the reserved capacity under a given transmission reservation shall be posted and viewable with the reduction Template. A specific example of a Primary Provider initiated recall of reserved capacity is the implementation of a partial displacement of a transmission reservation. In this instance, the Customer has not elected (or was not required to be offered) to match the terms of a higher priority, competing request. The Primary Provider "recalls" that capacity necessary to accommodate the higher priority request from the original, lower priority request. The IMPACTED counter of the original request is incremented, and a query using the reduction Template for that original reservation would show the Customer the amount and time-frame that the Customer's reserved capacity was recalled by the Primary Provider. (See sections 4.2.13.6 and 4.2.13.7.) Interruption of transmission service, where that interruption directly impacts the rights of the Customer to schedule any service under that reservation, is another example of an impact to reserved capacity that would be posted as a Primary Provider initiated recall of reserved capacity. Secondary market sales of transmission rights are not examples of a Provider initiated recall of reserved capacity, but the impact of any such sales shall also be returned in response to execution of the reduction Template.
002-4.3 TEMPLATE DESCRIPTIONS
The following OASIS Templates define the Data Elements in fixed number and sequence which must be provided for all data transfers to and from the OASIS Nodes. The definitions of the Data Elements are listed in the Data Element Dictionary in Appendix A. TSIPs must provide a more detailed supplemental definition of the list of Sellers, Paths, Point of Receipt (POR), Point of Delivery (POD), Capacity Types, Ancillary Service Types and Templates online, clarifying how the terms are being used (see LIST Template). If POR and POD are not used, then Path Name must include directionality. Many of the Templates represent query-response interactions between the User and the OASIS Node. These interactions are indicated by the "Query" and "Response" section respectively of each Template. Some, as noted in their descriptions, are Input information, sent from the User to the OASIS Node. The Response is generally a mirror of the Input, although in some Templates, the TSIP must add some information.
002-4.3.1 Template Summary
The following table provides a summary of the process areas, and Templates to be used by Users to query information that will be downloaded or to upload information to the Primary Providers. These processes define the functions that must be supported by an OASIS Node.


Process Area

Process Name

Template(s)

4.3.2 Query/Response of Posted Services Being Offered

Query/Response Transmission Capacity Offerings

transoffering




Query/Response Ancillary Service Offerings

ancoffering










4.3.3 Query/Response of Services Information

Query/Response Transmission Services

transserv




Query/Response Ancillary Services

ancserv










4.3.4 Query/Response of Schedule details and Curtailments, Security Events, Reductions, and System Data

Query/Response Transmission Schedules and Curtailments

scheduledetail




Query/Response Security Events

security




Query/Response Reductions to Reserved Capacity

reduction




Query/Response Transmission System Data

systemdata










4.3.5 Query/Response of Lists of Information

Query/Response List of Sellers, Paths, PORs, PODs, Capacity Types, Ancillary Service Types, Templates

list










4.3.6 Purchase Transmission Services

Request Purchase of Transmission Services (Input)

transrequest




Query/Response Status of Transmission Service Request

transstatus




Seller Approves Purchase (Input)

transsell




Customer Confirm/Withdraw Purchase of Transmission Service (Input)

transcust




Seller Reassign Rights (Input)

transassign










4.3.7 Seller Posting of Transmission Service

Seller Post Transmission Service for Sale (Input)

transpost




Seller Modify (Remove) Transmission Service for Sale (Input)

transupdate










4.3.8 Purchase of Ancillary Service

Request Purchase of Ancillary Service (Input)

ancrequest




Query/Response Status of Ancillary Service Request

ancstatus




Seller Approves Purchase of Ancillary Service (Input)

ancsell




Customer Accept/Withdraw Purchase of Ancillary Service (Input)

anccust




Seller Reassign Rights (Input)

ancassign










4.3.9 Seller Post Ancillary Service

Seller Post Ancillary Service (Input)

ancpost




Seller Modify (Remove) Ancillary Service for Sale (Input)

ancupdate













4.3.10 Informal Messages

Post Want Ads (Input)




messagepost




Query/Response Want Ads

message




Delete Want Ad (Input)

messagedelete




Personnel Transfers

personnel




Discretion

discretion




Standards of Conduct

stdconduct










4.3.11 Audit Log

Query/Response Audit Log

(various)


002-4.3.2 Query/Response of Posted Services Being Offered
The following Templates define the information to be posted on services offered for sale. All discounts for service negotiated by a Customer and Primary Provider (as Seller) at a price less than the currently posted offering price shall be posted on OASIS Nodes in such a manner as to be viewed using these Templates. All secondary market and/or third-party posting and Primary Provider offerings for like services shall also be viewed using these Templates. The Query must start with the standard header Query Variable Data Elements, listed in Section 4.2.6.2, and may include any valid combination of the remaining Query Variables, shown below in the Templates. START_TIME and STOP_TIME is the requested time interval for the Response to show all offerings which intersect that interval (see Section 4.2.6.6). TIME_OF_LAST_UPDATE can be used to specify all services updated since a specific point in time. Query variable listed with an asterisk (*) can have at least 4 multiple instances defined by the user in making the query. In the Response, OFFER_START_TIME and OFFER_STOP_TIME indicate the "request time window" within which a customer must request a service in order to get the posted OFFER_PRICE. START_TIME and STOP_TIME indicate the time frame that the service is being offered for. The SERVICE_DESCRIPTION Data Element shall define any attributes and/or special terms and conditions applicable to the offering that are not listed under the standard SERVICE_DESCRIPTION associated with the product definition supplied in the transserv or ancserv Templates. SERVICE_DESCRIPTION shall be null if there are no unique attributes or terms associated with the offering.
002-4.3.2.1 Transmission Capacity Offerings Available for Purchase (transoffering)
Transmission Services Offerings Available for Purchase (transoffering) is used to view transmission services posted for sale by the Primary Provider or Resellers. At a minimum this Template must be used to view each increment and type of service required to be offered under applicable regulations and the Primary Provider's tariffs. The POSTING_REF is set by the TSIP when an offering is posted and can be used in transrequest to refer to a particular offering. A User may query information about services available from all sellers for the time frame specified by the SERVICE_INCREMENT Data Element, namely, hourly, daily, weekly, monthly, or yearly.
Template: transoffering


  1. Query

PATH_NAME*

SELLER_CODE*

SELLER_DUNS*

POINT_OF_RECEIPT*

POINT_OF_DELIVERY*

SERVICE_INCREMENT*

TS_CLASS*

TS_TYPE*


TS_PERIOD*

TS_WINDOW*

TS_SUBCLASS*

START_TIME (of transmission services)

STOP_TIME (of transmission services)

POSTING_REF

TIME_OF_LAST_UPDATE


  1. Response

The response is one or more records showing the requested service information. Note that the Customer will receive as a series of records spanning all the SELLER_CODEs, PATH_NAMEs, PORs, PODs, TS_xxx, and the START_TIME/STOP_TIME specified in the query. The SALE_REF is a value provided by the SELLER to identify the transmission service product being sold. The ANC_SVC_REQ indicates all ancillary services required for the specified transmission services. All Template elements are defined in the Data Element Dictionary.


TIME_OF_LAST_UPDATE

SELLER_CODE

SELLER_DUNS

PATH_NAME

POINT_OF_RECEIPT

POINT_OF_DELIVERY

INTERFACE_TYPE

OFFER_START_TIME

OFFER_STOP_TIME

START_TIME

STOP_TIME

CAPACITY (If null, then look in seller comments for information .)

SERVICE_INCREMENT

TS_CLASS


TS_TYPE

TS_PERIOD

TS_WINDOW

TS_SUBCLASS

ANC_SVC_REQ

SALE_REF


POSTING_REF

CEILING_PRICE

OFFER_PRICE

PRICE_UNITS

SERVICE_DESCRIPTION (if null, then look at transserv)

NERC_CURTAILMENT_PRIORITY

OTHER_CURTAILMENT_PRIORITY

SELLER_NAME

SELLER_PHONE

SELLER_FAX

SELLER_EMAIL

SELLER_COMMENTS


002-4.3.2.2 Ancillary Services Available for Purchase (ancoffering)
Ancillary Services Available for Purchase (ancoffering) is used to provide information regarding the ancillary services that are available for sale by all sellers (both Primary Provider and Third Party Sellers).
Template: ancoffering


  1. Query

SELLER_CODE*

SELLER_DUNS*

CONTROL_AREA*

SERVICE_INCREMENT*

AS_TYPE*


START_TIME

STOP_TIME

POSTING_REF

TIME_OF_LAST_UPDATE



1   2   3   4   5   6   7   8   9   10   11


База данных защищена авторским правом ©shkola.of.by 2016
звярнуцца да адміністрацыі

    Галоўная старонка