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




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

Response

TIME_OF_LAST_UPDATE

SELLER_CODE

SELLER_DUNS

CONTROL_AREA

OFFER_START_TIME

OFFER_STOP_TIME

START_TIME

STOP_TIME

CAPACITY


SERVICE_INCREMENT

AS_TYPE


SALE_REF

POSTING_REF

CEILING_PRICE

OFFER_PRICE

PRICE_UNITS

SERVICE_DESCRIPTION (if blank, then look at ancserv)

SELLER_NAME

SELLER_PHONE

SELLER_FAX

SELLER_EMAIL

SELLER_COMMENTS
002-4.3.3 Query/Response of Services Information
002-4.3.3.1 Transmission Services (transserv)
Transmission Services (transserv) is used to provide additional information regarding the transmission services SERVICE_INCREMENT, TS_CLASS, TS_TYPE, TS_PERIOD, TS_SUBCLASS, TS_WINDOW, NERC_CURTAILMENT_PRIORITY, and OTHER_CURTAILMENT_PRIORITY that are available for sale by a Provider in the Templates in Section 4.3.2. This Template is used to summarize Provider tariff information for the convenience of the User. The Provider also sets PRICE_UNITS with this Template.
Template: transserv


  1. Query

TIME_OF_LAST_UPDATE




  1. Response

TIME_OF_LAST_UPDATE

SERVICE_INCREMENT

TS_CLASS


TS_TYPE

TS_PERIOD

TS_WINDOW

TS_SUBCLASS

CEILING_PRICE

PRICE_UNITS

SERVICE_DESCRIPTION

NERC_CURTAILMENT_PRIORITY

OTHER_CURTAILMENT_PRIORITY

TARIFF_REFERENCE


002-4.3.3.2 Ancillary Services (ancserv)
Ancillary Services (ancserv) is used to provide additional information regarding the ancillary services that are available for sale by a Provider in the Templates in Section 4.3.2. This Template is used to summarize Provider tariff information for the convenience of the User. The Provider also sets PRICE_UNITS with this Template.

Template: ancserv




  1. Query

TIME_OF_LAST_UPDATE




  1. Response

TIME_OF_LAST_UPDATE

SERVICE_INCREMENT

AS_TYPE


CEILING_PRICE

PRICE_UNITS

SERVICE_DESCRIPTION

TARIFF_REFERENCE


002-4.3.4 Query/Response of Schedules and Curtailments, Security Events, Reductions, and System Data
002-4.3.4.1 Transaction Schedule (scheduledetail)
Transaction Schedule (scheduledetail) provides information on the scheduled uses of the Provider’s transmission system and any curtailments or interruption thereof. Posting of transmission service schedule information shall be in accordance with regulatory requirements, and reflect scheduled uses of reserved capacity to a level of detail that such schedules are subject to a Provider’s application of transmission security procedures and policies regarding curtailment and interruptions. There is no restriction on the number of transaction schedule records that may refer to a given transmission reservation at a given point in time.
The Query Variables ASSIGNMENT_REF, SELLER_CODE, SELLER_DUNS, CUSTOMER_CODE, CUSTOMER_DUNS, SERVICE_INCREMENT, TS_CLASS, TS_TYPE, and TS_PERIOD act to select those transmission reservations for which all applicable transaction schedule information is to be returned. The PATH_NAME, POINT_OF_RECEIPT, POINT_OF_DELIVERY Query Variables select all applicable interchange transaction schedule records that use the specified path, point of receipt, and/or point of delivery. The TIME_OF_LAST_UPDATE, START_TIME, and STOP_TIME Query Variables select those particular interchange transaction schedule records updated and/or effective: 1) on or after a particular point in time (START_TIME alone), 2) before a particular point in time (STOP_TIME alone), or 3) between particular points in time (START_TIME and STOP_TIME). The TRANSACTION_ID Query Variable selects all applicable schedule information records associated with that particular schedule. Note that the format of TRANSACTION_ID may be Transmission Provider specific.
Each scheduledetail Template record returned in response to a query shall include information associated with:

  1. information specifically related to the scheduled transaction,

  2. information from all applicable OASIS transmission reservations used to support the scheduled interchange transaction, and

  1. information related to any curtailment or interruption of service (if applicable), including a Transmission Provider’s refusal to accept or begin a Customer’s proposed interchange transaction for reliability or economic reasons (as allowed by the Provider’s Tariff).

Information to be supplied in each scheduledetail Template’s response records related to the scheduled interchange are, SCHEDULE_REF, TRANSACTION_ID, PATH_NAME, POINT_OF_RECEIPT, POINT_OF_DELIVERY, GCA_CODE, LCA_CODE, SOURCE, SINK, SCHEDULE_PRIORITY, START_TIME, STOP_TIME, SCHEDULE_REQUESTED, and SCHEDULE_GRANTED.
The posting and availability of schedule and curtailment information on OASIS shall be in accordance with FERC Policy.
SCHEDULE_REF uniquely identifies a particular posting of schedule information. SCHEDULE_REF would vary with each record of data returned in response to a schedule query. TRANSACTION_ID, if applicable/available, contains a unique identifier associated with an interchange transaction that may span multiple SCHEDULE_REF records. When available or applicable, the TRANSACTION_ID Data Element should reflect any industry-recognized transaction identifier rather than a Provider specific internal identifier (e.g., the NERC electronic tagging “tag-id”). PATH_NAME, POINT_OF_RECEIPT, and POINT_OF_DELIVERY identify the Transmission Provider’s specific transmission resources used by the scheduled transaction, and would typically be identical to the corresponding Data Elements associated with the OASIS transmission reservation used to support the schedule. When known, the GCA_CODE and LCA_CODE identify the NERC registered Control Area acronyms associated with the ultimate generation and load control areas respectively. When known or required to more specifically identify the ultimate points of generation and load, the SOURCE and SINK elements identify service points within the generation and load Control Areas respectively. SCHEDULE_PRIORITY identifies the relative priority of this particular interchange transaction as compared to all other scheduled transactions with respect to the application of curtailments or interruptions. SCHEDULE_PRIORITY would typically reflect the curtailment priority Data Elements associated with the OASIS transmission reservation used to support the schedule (i.e., NERC_CURTAILMENT_PRIORITY or OTHER_CURTAILMENT_PRIORITY). START_TIME and STOP_TIME designate the particular time interval represented by this record associated with the scheduled transaction. Note that multiple response records may be returned for a given scheduled transaction when information associated with the schedule vary over time (e.g., SCHEDULE_REQUESTED, SCHEDULE_GRANTED, SCHEDULE_LIMIT, etc.), but that scheduledetail Template response records for a given scheduled transaction should never overlap in time. SCHEDULE_REQUESTED reflects the MW value requested to be scheduled by the Customer during the hour, and SCHEDULE_GRANTED reflects the MW value actually scheduled by the Transmission Provider at either the point of receipt or delivery, whichever is larger, over the START_TIME/STOP_TIME time interval. When SCHEDULE_REQUESTED exceeds SCHEDULE_GRANTED, a curtailment or interruption is in effect and additional information shall be returned in the record.
Information in each scheduledetail Template’s response record related to the OASIS transmission reservation(s) supporting the scheduled transaction includes ASSIGNMENT_REF, SELLER_CODE, SELLER_DUNS, CUSTOMER_CODE, CUSTOMER_DUNS, AFFILIATE_FLAG, SERVICE_INCREMENT, TS_CLASS, TS_TYPE, TS_PERIOD, TS_WINDOW, TS_SUBCLASS, NERC_CURTAILMENT_PRIORITY, OTHER_CURTAILMENT_PRIORITY, and CAPACITY_USED. Transaction schedules that are supported by the use of multiple OASIS transmission reservations return the information attributable to each individual transmission reservation using continuation records (i.e., records beginning with CONTINUATION_FLAG = ‘Y’). Each continuation record shall also include the SCHEDULE_REF identifier from the first (CONTINUATION_FLAG = ‘N’) record. CAPACITY_USED reflects the peak MW amount of the reservation used to support the scheduled transaction; the sum of CAPACITY_USED over all continuation records (if applicable) should equal the SCHEDULE_GRANTED.
Transaction schedules that were either “denied or interrupted” (ref. 18 CFR 37.6(a)(4)) shall include information in the scheduledetail Template’s response related to the reason the transaction could not be started or continued at the requested MW amount. The information returned shall include: PROVIDER_ACTION, SCHEDULE_LIMIT, CURTAILMENT_OPTIONS, SECURITY_REF, INITIATING_PARTY, RESPONSIBLE_PARTY, PROCEDURE_NAME, PROCEDURE_LEVEL, FACILITY_LOCATION, FACILITY_NAME, FACILITY_CLASS, and FACILITY_LIMIT_TYPE. If there are no restrictions to the scheduled transaction, these Data Elements shall all be returned as null.
PROVIDER_ACTION indicates the particular action taken by the Transmission Provider with respect to the scheduled transaction; specific values to be returned are, DENIED if the schedule was not started as requested, CURTAILED if the scheduled MW was limited for reliability reasons, or INTERRUPTED if the scheduled MW was limited for economic reasons. SCHEDULE_LIMIT reflects the maximum MW value over the START_TIME/STOP_TIME interval that the Provider has determined can be scheduled. CURTAILMENT_OPTIONS defines any options the Customer may exercise to reinstate all or part of the proposed schedule. SECURITY_REF, INITIATING_PARTY, RESPONSIBLE_PARTY, PROCEDURE_NAME, PROCEDURE_LEVEL, FACILITY_NAME, FACILITY_CLASS, and FACILITY_LIMIT_TYPE provide information related to the specific transmission security event that prompted the Transmission Provider’s denial, curtailment or interruption of the proposed scheduled transaction (see security Template).
Template: scheduledetail


  1. Query

PATH_NAME*

SELLER_CODE*

SELLER_DUNS*

CUSTOMER_CODE*

CUSTOMER_DUNS*

POINT_OF_RECEIPT*

POINT_OF_DELIVERY*

SERVICE_INCREMENT*

TS_CLASS*

TS_TYPE*

TS_PERIOD*

TS_WINDOW*

TS_SUBCLASS*

START_TIME

STOP_TIME

TIME_OF_LAST_UPDATE

ASSIGNMENT_REF

TRANSACTION_ID


  1. Response

CONTINUATION_FLAG

TIME_OF_LAST_UPDATE

SCHEDULE_REF

TRANSACTION_ID

PATH_NAME

POINT_OF_RECEIPT

POINT_OF_DELIVERY

GCA_CODE

LCA_CODE


SOURCE

SINK


SCHEDULE_PRIORITY

START_TIME

STOP_TIME

SCHEDULE_REQUESTED

SCHEDULE_GRANTED

ASSIGNMENT_REF

SELLER_CODE

SELLER_DUNS

CUSTOMER_CODE

CUSTOMER_DUNS

AFFILIATE_FLAG

SERVICE_INCREMENT

TS_CLASS

TS_TYPE


TS_PERIOD

TS_WINDOW

TS_SUBCLASS

NERC_CURTAILMENT_PRIORITY

OTHER_CURTAILMENT_PRIORITY

CAPACITY_USED

(if the transaction is subject to curtailment:)

PROVIDER_ACTION

SCHEDULE_LIMIT

CURTAILMENT_OPTIONS

SECURITY_REF

INITIATING_PARTY (e.g, CA/TP code)

RESPONSIBLE_PARTY (e.g., SC code)

PROCEDURE_NAME (e.g., "NERC TLR", or registered)

PROCEDURE_LEVEL (e.g., "2a", "3")

FACILITY_LOCATION (e.g, "INTERNAL" or

"EXTERNAL")

FACILITY_NAME

FACILITY_CLASS (e.g., transformer, etc.)

FACILITY_LIMIT_TYPE (e.g, thermal, stability, etc.)


002-4.3.4.2 Security Event (security)
Security Event (security) provides information on transmission security/reliability events that may impact the Provider’s ability to schedule transactions. The TIME_OF_LAST_UPDATE, START_TIME, and STOP_TIME Query Variables select those particular security event postings updated and/or effective: 1) on or after a particular point in time (START_TIME alone), 2) before a particular point in time (STOP_TIME alone), or 3) between particular points in time (START_TIME and STOP_TIME).
The SECURITY_REF Data Element is a unique identifier assigned to each posting of security related information; SECURITY_REF would vary with each record of data returned in response to a security query. The EVENT_ID Data Element, when available, should reflect any regional or interconnection-wide recognized security event identifier for events that are of greater scope than those administered locally by the Provider (e.g., a NERC Security Coordinator assigned identifier corresponding to a particular implementation of the NERC TLR procedure). SECURITY_TYPE identifies the type of information posted for the event; restricted values are OUTAGE for postings reflecting the state of critical transmission facilities, and LIMIT for postings reflecting the implementation of security procedures to limit or reduce scheduled transactions. The INITIATING_PARTY identifies by Control Area, Security Coordinator or Transmission Provider code the entity calling for the “outage” or “limit”, and RESPONSIBLE_PARTY identifies the entity (Control Area, Transmission Provider, or Security Coordinator) responsible for administering any resulting security procedure that may be instituted.
PROCEDURE_NAME and PROCEDURE_LEVEL reflect the specific security procedure and, if applicable, the step, stage, or level within that procedure being implemented by RESPONSIBLE_PARTY (e.g., NERC TLR is a recognized security procedure, and level “2a” is a step within that procedure). FACILITY_NAME, FACILITY_CLASS, and FACILITY_LIMIT_TYPE provide specific information related to the impacted transmission facility. FACILITY_LOCATION identifies if the impacted facility is "INTERNAL" or "EXTERNAL" relative to the Transmission Provider’s scope of authority over the named facility.

START_TIME and STOP_TIME reflect the period of time encompassed by the particular security event posted. In cases where a security procedure is invoked and then progresses through various levels or stages, there shall be separate postings for each of those stages declared by RESPONSIBLE_PARTY with START_TIME and STOP_TIME reflecting the period of time each specific level of the procedure was in effect.


The use of the security Template to convey information related to major transmission facility outages (SECURITY_TYPE = OUTAGE) is at the discretion of the Provider. Its definition in this Template is intended to formalize the posting of facility outage information in an OASIS Template structure where such information prior to implementation of this Template had been posted in a free-form manner.
Template: security


  1. Query

START_TIME

STOP_TIME

TIME_OF_LAST_UPDATE

SECURITY_REF

EVENT_ID


SECURITY_TYPE

INITIATING_PARTY

RESPONSIBLE_PARTY

PROCEDURE_NAME

FACILITY_CLASS

FACILITY_LIMIT_TYPE

FACILITY_LOCATION


  1. Response

TIME_OF_LAST_UPDATE

SECURITY_REF

EVENT_ID


SECURITY_TYPE ("LIMIT" or "OUTAGE")

INITIATING_PARTY (e.g., CA/TP code)

RESPONSIBLE_PARTY (e.g., SC code)

PROCEDURE_NAME (e.g., "NERC TLR", or registered)

PROCEDURE_LEVEL (dependent on PROCEDURE_NAME)

FACILITY_CLASS (e.g., "FLOWGATE", "LINE", etc.)

FACILITY_LIMIT_TYPE (e.g., "THERMAL", "STABILITY", etc.)

FACILITY_LOCATION ("INTERNAL" or "EXTERNAL")

FACILITY_NAME (e.g., path or flowgate name)

START_TIME



STOP_TIME
002-4.3.4.3 Transmission Reservation Reduction (reduction)
The Transmission Reservation Reduction (reduction) Template provides information related to the reduction in the Transmission Customer’s rights to schedule use of all or a portion of capacity reserved for a given transmission reservation. Specific cases where such a reduction in reserved capacity would be returned in response to this query Template include: secondary market sales (as posted using the transassign or transsell Templates via the REASSIGNED_REF, etc., Data Elements), a Transmission Provider’s interruption of the reservation to accommodate higher priority reservations over the interruption interval (partial displacement), etc.
The ASSIGNMENT_REF Query Variable is required and specifies the transmission reservation whose reductions in reserved capacity (if any) are to be returned. The START_TIME and STOP_TIME Query Variables allow the user to select the specific time interval over which the reductions in reserved capacity are to be returned (e.g., return all reductions in June for a year long reservation); by default all reductions over the life of the reservation are returned.
In response to a reduction Template query, each primary record returned (CONTINUATION_FLAG = N) shall include the ASSIGNMENT_REF, CAPACITY_GRANTED and CAPACITY_AVAILABLE in MWs over the interval from START_TIME to STOP_TIME. CAPACITY_AVAILABLE is derived from the transmission reservation's CAPACITY_GRANTED less all reductions (if any) in reserved capacity over the interval from START_TIME to STOP_TIME as specified in the CAPACITY_REDUCED (as negative valued MWs) Data Element. The REDUCTION_TYPE, and REDUCTION_REASON Data Elements describe the circumstances and IMPACTING_REF references the associated transmission reservation (if applicable) that caused the reduction in capacity.
If no reductions in reserved capacity have been posted against the reservation, CAPACITY_AVAILABLE will equal CAPACITY_GRANTED and the REDUCTION_TYPE, REDUCTION_REASON, IMPACTING_REF and CAPACITY_REDUCED Data Elements will be null. This response information is equivalent to the CAPACITY_GRANTED, START_TIME, and STOP_TIME information that would be returned on execution of the transstatus Template.
If the CAPACITY_AVAILABLE over the interval from START_TIME to STOP_TIME is the result of more than one action reducing reserved capacity (e.g., multiple secondary market sales for the same time period), each action reducing capacity will be returned in continuation records (CONTINUATION_FLAG = Y) containing the ASSIGNMENT_REF, REDUCTION_TYPE, REDUCTION_REASON, IMPACTING_REF and CAPACITY_REDUCED Data Elements. If the action is another reservation (e.g. secondary market sale) the REASSIGNED_CAPACITY from that reservation will be shown as a negative value in CAPACITY_REDUCED.
Template: reduction


  1. Query

START_TIME

STOP_TIME

ASSIGNMENT_REF* (must be specified)




  1. Response

CONTINUATION_FLAG

ASSIGNMENT_REF

CAPACITY_GRANTED

CAPACITY_AVAILABLE

START_TIME

STOP_TIME

REDUCTION_TYPE (e.g., REDIRECT, INTERRUPTION, RESALE, DISPLACEMENT, etc.)

REDUCTION_REASON

IMPACTING_REF (if applicable)

CAPACITY_REDUCED
002-4.3.4.4 System Data (systemdata)
The System Data (systemdata) Template is used to query specific, time varying data that is posted on a PATH, POINT_OF_RECEIPT, and/or POINT_OF_DELIVERY basis. The SYSTEM_ATTRIBUTE Data Element defines the type of information returned in the Template response. The restricted values for SYSTEM_ATTRIBUTE are,


  • CBM – Capacity Benefit Margin

  • TRM – Transmission Reliability Margin

  • TTC – Total Transmission Capability

  • NATC – Non-recallable (Firm) Available Transmission Capability

  • RATC – Recallable (Non-firm) Available Transmission Capability

  • A {registered} – Provider specific registered name for the data posted

Transmission Providers obligated to post values for one or more of the defined SYSTEM_ATTRIBUTEs on specific transmission paths over time (e.g., hourly, then daily, etc.) as called forth in FERC regulations shall return these posted values via the systemdata Template. If SYSTEM_ATTRIBUTE is omitted in the query, then all attributes defined by the transmission provider are returned, subject to the other query attributes constraints.. A given SYSTEM_ATTRIBUTE may take on only one value at any given point in time. Note that TTC and ATC information may also be viewed using the transoffering Template at the Transmission Provider's discretion. Offers of service posted by Primary Providers as viewed with the transoffering Template should reflect the applicable ATC(s) posted via systemdata in the CAPACITY Data Element.


Template: systemdata


  1. Query

PATH_NAME*

POINT_OF_RECEIPT*

POINT_OF_DELIVERY*

SYSTEM_ATTRIBUTE*

START_TIME

STOP_TIME

TIME_OF_LAST_UPDATE




  1. Response (acknowledgment)

POSTING_REF

PATH_NAME

POINT_OF_RECEIPT

POINT_OF_DELIVERY

SYSTEM_ATTRIBUTE

START_TIME

STOP_TIME

ATTRIBUTE_VALUE

ATTRIBUTE_UNITS

TIME_OF_LAST_UPDATE
002-4.3.5 Query/Response of Lists of Information
002-4.3.5.1 List (list)
List (list) is used to provide lists of valid names. The minimum set of lists is LIST, SELLER_CODE, PATH_NAME, POINT_OF_RECEIPT, POINT_OF_DELIVERY, SERVICE_INCREMENT, TS_CLASS, TS_TYPE, TS_PERIOD, TS_SUBCLASS, TS_WINDOW, NERC_CURTAILMENT_PRIORITY, REQUEST_TYPE, ANC_SERVICE_POINT, FACILITY_CLASS, FACILITY_LIMIT_TYPE, PROCEDURE_NAME, SYSTEM_ATTRIBUTE, SECURITY_TYPE, FACILITY_LOCATION, OTHER_CURTAILMENT_PRIORITY, AS_TYPE, CATEGORY, and TEMPLATE. The information returned by the list Template may be used as values for the associated OASIS Data Elements to query information, post or request services.
Template: list


  1. Query

LIST_NAME

TIME_OF_LAST_UPDATE


  1. Response

TIME_OF_LAST_UPDATE

LIST_NAME

LIST_ITEM



LIST_ITEM_DESCRIPTION
002-4.3.6 Purchase Transmission Services
The following Templates shall be used by Customers and Sellers to transact purchases of services.
002-4.3.6.1 Customer Capacity Purchase Request (transrequest)
The Customer Capacity Purchase Request (Input) (transrequest) is used by the Customer to request the purchase of transmission services or request changes to previously submitted reservations for transmission services. The response simply acknowledges that the Customer's request was received by the OASIS Node. It does not imply that the Seller has received the request. Inputting values into the reference Data Elements is optional.
CUSTOMER_CODE and CUSTOMER_DUNS shall be determined from the registered connection used to input the request.
Supporting "profiles" of service, which request different capacities (and optionally price) for different time periods within a single request, is at the discretion of the Primary Provider. Continuation records may be used to indicate requests for these service profiles; use of continuation records is only supported when using the CSV Format upload of Template data. Each segment of a profile is represented by the Data Elements CAPACITY_REQUESTED, START_TIME, and STOP_TIME, which define the intervals in time overwhich a non-zero MW demand is being requested. The initial segment of a profile is defined by the CAPACITY_REQUESTED, START_TIME and STOP_TIME Data Elements specified in the first/only record submitted; subsequent segments are specified in continuation records each containing the appropriate CAPACITY_REQUESTED, START_TIME and STOP_TIME values defining the segment. Provider's may optionally support price negotiation on segments of a profiled reservation request. In this case, the BID_PRICE Data Element is also included in each continuation record. If the BID_PRICE Data Element is not specified in the continuation records, the BID_PRICE specified in the first/only record submitted will be applied to the entire reservation request.
For requesting transmission services which include multiple paths, the following fields may be specified using continuation records: PATH_NAME, POINT_OF_RECEIPT, and POINT_OF_DELIVERY. Supporting multiple paths or multiple POINT_OF_RECEIPT and POINT_OF DELIVERY is at the discretion of the Provider.
The START_TIME and STOP_TIME indicate the requested period of service.
When the request is received at the OASIS Node, the TSIP assigns a unique ASSIGNMENT_REF value and queues the request with a time stamp. The STATUS for the request is QUEUED. The IMPACTED counter is initially set to 0. If the new request is not modifying an existing reservation (as indicated by a null value for the RELATED_REF Data Element) and the SELLER is the Primary Provider, REQUEST_TYPE must either be specified as "ORIGINAL" or be left null and OASIS will substitute the default value of "ORIGINAL". If the new request is not modifying an existing reservation and the SELLER is not the Primary Provider, REQUEST_TYPE must either be specified as "RESALE" or be left null and OASIS will substitute the default value of "RESALE".
If the new request is modifying an existing transmission reservation, the Data Elements REQUEST_TYPE and RELATED_REF must be entered. RELATED_REF contains the ASSIGNMENT_REF for the transmission reservation being modified, and REQUEST_TYPE must be one of MATCHING, REDIRECT, DEFERRAL, RENEWAL, or a Primary Provider registered value.
Specification of a value YES in the PRECONFIRMED field authorizes the TSIP to automatically change the STATUS field in the transstatus Template to CONFIRMED when that request is ACCEPTED by the Seller.
Template: transrequest

1   2   3   4   5   6   7   8   9   10   11


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

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