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




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

002-4.3.11.3.4 CSV Response Header Records
Finally, OASIS implementations may include additional Data Elements identified by unique column headers appended after the fixed audit and standard Template Data Elements. These additional Data Elements may be used to convey implementation specific information maintained in the OASIS database in association with the data being audited.
002-4.3.11.4 HTML Output
Specification of the Query Variable OUTPUT_FORMAT=HTML shall minimally result in an audit report formatted identically to the CSV Format (OUTPUT_FORMAT=DATA) with the exception that the response shall be returned using the HTTP header "Content-type: text/plain" specification. This will result in the CSV Data Records being rendered in simple text within the user's web-browser. More sophisticated HTML formatted responses to audit queries may be provided by the TSIPs at their discretion.
002-4.3.11.5 Special Audit Template Considerations
Transoffering
The transoffering Template is used to convey information on transmission services offered for sale as well as the availability of transmission capability (TTC/ATC). The proposed audit reporting scheme may prove inadequate to generate audits of both the commercial aspects of offers posted on OASIS (i.e., price, etc.) and the reliability aspects associated with those offers (i.e., ATC) depending on how these two different types of information are represented internally by each OASIS node.
For those OASIS implementations that handle TTC/ATC information separately from the posting of commercial offers of service, audit reports generated by the transofferingaudit Template may be limited to only reporting changes to the Data Elements associated with the commercial aspects of the offer (e.g., OFFER_PRICE, OFFER_START_TIME, etc.), and may return a null value for the CAPACITY Data Element. These nodes shall use the systemdataaudit Template audit reporting facility to allow for the full auditing of changes made to TTC and ATC postings as required under Federal Regulations.
Scheduledetail
The scheduledetail Template combines information from one or more transmission reservations and transmission security event postings (e.g., TLRs) with information posted on actual scheduled use of the transmission system.Audit information related to changes made to a given transmission reservation shall be auditable using the transstatusaudit Template. Audit information related to the posting of transmission security events that led to a curtailment or interruption of service, or the denial of a request to schedule service shall be auditable using the securityaudit Template. Therefore, the scheduledetailaudit Template shall only be required to report changes to the following Data Elements associated with the scheduledetail Template:
TRANSACTION_ID

START_TIME

STOP_TIME

SCHEDULE_REQUESTED

SCHEDULE_GRANTED

ASSIGNMENT_REF

PROVIDER_ACTION

SCHEDULE_LIMIT

CURTAILMENT_OPTIONS

SECURITY_REF


002-4.4 FILE REQUEST AND FILE DOWNLOAD EXAMPLES
See the OASIS Implementation Guide WEQ 011.

In the examples, the end-of-line (eol) character is represented by the character,"  ". This symbol may appear different on displays or printouts.


002-4.4.1 File Example for Hourly Offering
Example of the request to Primary Provider, aaa, and response for Seller, wxyz, for PATH_NAME "W/AAAA/PATH-ABC//" for April 10, 1996 from 8 a.m. to 3 p.m. (Note that the PATH_NAME consists of a REGION_CODE, PRIMARY_PROVIDER_CODE, PATH_CODE, and an OPTIONAL_CODE, separated with a slash, "/".)
The VERSION for this release is 1.4. The request is in the form of a URL query string and the response is an ASCII delimited file.


  1. Query

http://(OASIS Node name)/OASIS/aaa/data/transoffering? ver=1.2&templ=transoffering& fmt=data&pprov=AAAA &pprovduns=123456789& path=W/AAA/ABC// &seller=WXYZAA &sellerduns=987654321& POR=aaa& POD=bbb& servincre=hourly& TSCLASS1=firm &TSCLASS2=non-firm&tz=PD&stime=19960410080000PD&sptime= 19960410150000PD




  1. Response Data

REQUEST-STATUS=200 (Successful)

TIME_STAMP=19960409113526PD 

VERSION=1.4

TEMPLATE=transoffering

OUTPUT_FORMAT=DATA 


PRIMARY_PROVIDER_CODE=AAAA

PRIMARY_PROVIDER_DUNS=123456789

DATA_ROWS=14

COLUMN_HEADERS=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, SERVICE_INCREMENT, TS_CLASS, TS_TYPE, TS_PERIOD,

TS_SUBCLASS, SALE_REF, POSTING_REF, CEILING_PRICE, OFFER_PRICE, PRICE_UNITS,

SERVICE_DESCRIPTION,SELLER_NAME,SELLER_PHONE,SELLER_FAX, SELLEREMAIL,

SELLER_COMMENTS 

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

080000PD,19960410090000PD,300, HOURLY, FIRM, POINT_TO_POINT, OFF_PEAK, N/A, N/A, A001,

1.50,1.35,MW,N/A,N/A,N/A,N/A,N/A,10% DISCOUNT 

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

080000PD,19960410090000PD,300, HOURLY, NON-FIRM, POINT_TO_POINT, OFF_PEAK, N/A, N/A,A001,1.50,

1.35,MW,N/A,N/A,N/A,N/A,N/A, 10% DISCOUNT 

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

090000PD,1996041010000PD,300, HOURLY, FIRM, POINT_TO_POINT, OFF_PEAK, N/A,

N/A,A001,1.50,1.35,MW,N/A,N/A,N/A,N/A,N/A,10% DISCOUNT 

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

090000PD,19960410100000PD,300, HOURLY, NON-FIRM, POINT_TO_POINT, OFF_PEAK, N/A, N/A,A001,1.50,

1.35,MW,N/A,N/A,N/A,N/A,N/A, 10% DISCOUNT 

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

100000PD,19960410110000PD,300, HOURLY, FIRM, POINT_TO_POINT, OFF_PEAK, N/A,

N/A,A001,1.50,1.35,MW,N/A,N/A,N/A,N/A,N/A,10% DISCOUNT 

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

100000PD,19960410110000PD,300, HOURLY, NON-FIRM, POINT_TO_POINT, OFF_PEAK, N/A, N/A,A001,1.50,

1.35,MW,N/A,N/A,N/A,N/A,N/A, 10% DISCOUNT 

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

110000PD,19960410120000PD,300, HOURLY, FIRM, POINT_TO_POINT, OFF_PEAK, N/A,

N/A,A001,1.50,1.35,MW,N/A,N/A,N/A,N/A,N/A,10% DISCOUNT 

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

110000PD,19960410120000PD,300, HOURLY, NON-FIRM, POINT_TO_POINT, OFF_PEAK, N/A, N/A,A001,1.50,

1.35,MW,N/A,N/A,N/A,N/A,N/A, 10% DISCOUNT 

. . .

. . .

. . .

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

140000PD,19960410150000PD,300, HOURLY, FIRM, POINT_TO_POINT, OFF_PEAK, N/A,

N/A,A001,1.50,1.35,MW,N/A,N/A,N/A,N/A,N/A,10% DISCOUNT 

19960409030000PD,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,19960402080000PD,19960410080000PD,19960410

140000PD,19960410150000PD,300, HOURLY, NON-FIRM, POINT_TO_POINT, OFF_PEAK, N/A, N/A,A001,1.50,

1.35,MW,N/A,N/A,N/A,N/A,N/A, 10% DISCOUNT 
002-4.4.2 File Example for Hourly Schedule Data
This example shows a request for the hourly schedule data from Primary Provider, AAAA, related to the seller, WXYZ, for the period 10 a.m. to 3 p.m. on April 10, 2000.
There are two identical requests examples using two slightly different methods. The first request is using a HTTP URL request string through an HTML GET method. The second request is a similar example using fetch_http from a file using a POST method.


  1. Query

URL Request (HTTP method=GET)

http://(OASIS Node name)/OASIS/aaaa/data/scheduledetail? ver=1.4& pprov=AAAA& templ=scheduledetail& fmt=data &pprovduns=123456789 &path=W/AAA/ABC//& seller=WXYZ &por=BBB &pod=CCC& tz=PD& stime=20000410100000PD& sptime=20000410150000PD
URL Request (HTTP method=POST)

$ fetch_http http://(OASIS Node name)/OASIS/aaaa/data/OASISdata -f c:/OASIS/wxyz/upload/infile. txt Where in-file.txt contains the following: ver=1.4& pprov=AAAA& templ=scheduledetail& fmt=data &pprovduns=123456789 &path=W/AAA/ABC//& seller=WXYZ &por=BBB &pod=CCC& tz=PD& stime=20000410100000PD& sptime=20000410150000PD




  1. Response Data

REQUEST_STATUS=200

ERROR_MESSAGE=No error. 

TIME_STAMP=20000410160523ES

VERSION=1.4

TEMPLATE=scheduledetail

OUTPUT_FORMAT=DATA

PRIMARY_PROVIDER_CODE=AAAA

PRIMARY_PROVIDER_DUNS=123456789

RETURN_TZ=PD

DATA_ROWS=3

COLUMN_HEADERS=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, PROVIDER_ACTION, SCHEDULE_LIMIT, CURTAILMENT_OPTIONS, SECURITY_REF, INITIATING_PARTY, RESPONSIBLE_PARTY, PROCEDURE_NAME, PROCEDURE_LEVEL, FACILITY_LOCATION, FACILITY_NAME, FACILITY_CLASS, FACILITY_LIMIT_TYPE

N, 20000409030000PD,12345,2233, W/AAA/ABC//, BBB, CCC,,,,,1, 20000410100000PD, 20000410110000PD,300,300,856743, wxyz,987654321, WXYZAA,987654322, Y, HOURLY, NON_FIRM, POINT_TO_POINT, OFF_PEAK, FIXED,,1,1,300,,,,,,,,,,,, 

N, 20000409030000PD,12346,2233, W/AAA/ABC//, BBB, CCC,,,,,1, 20000410130000PD, 20000410140000PD,300,300,856743,wxyz,987654321, WXYZAA,987654322, Y, HOURLY, NON_FIRM, POINT_TO_POINT, OFF_PEAK, FIXED,,1,1,300,,,,,,,,,,,, 

N, 20000409030000PD,12347,2233, W/AAA/ABC//, BBB, CCC,,,,,1, 20000410140000PD, 20000410150000PD,300,300,856743,wxyz,987654321, WXYZAA,987654322, Y, HOURLY, NON_FIRM, POINT_TO_POINT, OFF_PEAK, FIXED,,1,1,300,,,,,,,,,,,, 
002-4.4.3 Customer Posting a Transmission Service Offering
This example shows how a Customer would post for sale the transmission service that was purchased previously. The Seller would create a file and upload the file using the FETCH_HTTP program to send a file to the OASIS Node of the Primary Provider.


  1. Input:

VERSION=1.4

TEMPLATE=transpost

OUTPUT_FORMAT=DATA 

PRIMARY_PROVIDER_CODE=AAAA

PRIMARY_PROVIDER_DUNS=123456789

DATA_ROWS=1

COLUMN_HEADERS=PATH_NAME, POINT_OF_RECEIPT, POINT_OF_DELIVERY, INTERFACE_TYPE, CAPACITY, SERVICE_INCREMENT, TS_CLASS, TS_TYPE, TS_PERIOD, TS_SUBCLASS, START_TIME, STOP_TIME, OFFER_START_TIME, OFFER_STOP_TIME, SALE_REF, OFFER_PRICE, SERVICE_DESCRIPTION, SELLER_COMMENTPF

WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,150, HOURLY, FIRM, POINT_TO_POINT, OFF_PEAK, N/A,, 19960402080000PD,19960410080000PD, 19960410080000PD,19960410150000PD, A123,.90,N/A,"As Joe said, ""It is a good buy"""

FETCH_HTTP Command to send posting $ fetch_http http://(OASIS Node name)/OASIS/abcd/data/transrequest -f c:/OASIS/abcd/upload/post.txt




  1. Response Data

REQUEST-STATUS=200  (Successful)

TIME_STAMP=19960409113526PD 

VERSION=1.4

TEMPLATE=transpost

OUTPUT_FORMAT=DATA 

PRIMARY_PROVIDER_CODE=AAAA

PRIMARY_PROVIDER_DUNS=123456789

DATA_ROWS=1

COLUMN_HEADERS=RECORD_STATUS, PATH_NAME, POINT_OF_RECEIPT, POINT_OF_DELIVERY, INTERFACE_TYPE, CAPACITY, SERVICE_INCREMENT, TS_CLASS, TS_TYPE, TS_PERIOD, TS_SUBCLASS, START_TIME, STOP_TIME, OFFER_START_TIME, OFFER_STOP_TIME, SALE_REF, OFFER_PRICE, SERVICE_DESCRIPTION, SELLER_COMMENTS, ERROR_MESSAGE

200,WXYZ,987654321,W/AAA/ABC//,N/A,N/A,E,150, HOURLY, FIRM, POINT_TO_POINT, OFF_PEAK, N/A, 19960402080000PD,19960410080000PD, 19960410080000PD,19960410150000PD, A123,.90,N/A, "As Joe said, ""It is a good buy""", No Error
002-4.4.4 Example of Re-aggregating Purchasing Services using Reassignment
The following examples do not show the complete Template information, but only show those elements of the Template of interest to the example.
a. Customer #1, "BestE" requests the purchase of 150 MW Firm ATC for 8 a.m. to 5 p.m. for $1.00 from a Primary Provider (transrequest).

TEMPLATE=transrequest

CUSTOMER_CODE=BestE

CAPACITY=150

TS_

START_TIME="1996050708000000PD"



STOP_TIME="1996050717000000PD"

BID_PRICE="$1.00"

The Information Provider assigns ASSIGNMENT_REF = 5000 on acknowledgment.
b. Customer #1 purchases 120 MW ATC Non-firm for 3 p.m. to 9 p.m. for $.90 (transrequest). The Information Provider assigns the ASSIGNMENT_REF=5001 when the request for purchase is made and is shown in the acknowledgment.

TEMPLATE="transrequest"

CUSTOMER_CODE="BestE"

CAPACITY=120

TS_

START_TIME="1996050715000000PD"



STOP_TIME="1996050721000000PD"

BID_PRICE="$1.05"


c. Customer #1 becomes Seller #1 and post the Transmission service of 100 MW ATC Non-firm capacity from 8 a.m. to 9 p.m. for resale at $.90/MW-hour.

TEMPLATE="transpost"

SELLER_CODE="BestE"

CAPACITY=100

TS_

START_TIME="1996050708000000PD"



STOP_TIME="1996050721000000PD"

SALE_REF="BEST100"

OFFER_PRICE=.90

SELLER_COMMENTS="aggregating two previous purchases"


d. Customer #2 then requests purchase of 100 MW Non-firm from Reseller #1 from 8 a.m. to 6 p.m. for $0.90/MW-hour (transrequest).

TEMPLATE="transrequest"

CUSTOMER_CODE="Whlsle"

SELLER_CODE="BestE"

CAPACITY=100

TS_


START_TIME="1996050708000000PD"

STOP_TIME="1996050721000000PD"

SALE_REF="BEST100"

DEAL_REF="WPC100"

BID_PRICE=.90

CUSTOMER_COMMENTS="Only need service until 6 p.m." 


The Information Provider provides the ASSIGNMENT_REF=5002 for this transaction.
e. Seller informs the Information Provider of the reassignment of the previous transmission rights when the seller accepts the customer purchase request (transsell).

TEMPLATE="transsell"

CUSTOMER_CODE="Whlsle"

SELLER_CODE="BestE"

ASSIGNMENT_REF=5002

STATUS="Accepted"

REASSIGNED_REF1=5000

REASSIGNED_CAPACITY1=100

REASSIGNED_START_TIME1="199605070800PD"

REASSIGNED_STOP_TIME1="199605071700PD"

REASSIGNED_REF2=5001

REASSIGNED_CAPACITY2=100

REASSIGNED_START_TIME2="199605071700PD"

REASSIGNED_STOP_TIME2="199605071800PD"


002-4.4.5 File Examples of the Use of Continuation Records
a. Basic Continuation Records
The first example of the use of Continuation Records is for the transrequest Template submitted by a Seller for purchase of a transmission reservation spanning 16 hours from 06:00 to 22:00 with "ramped" demand at beginning and end of time period. Two additional reservations appear prior to and following the profile to demonstrate the handling of ASSIGNMENT_REF by the OASIS Node.
Only the following fields may be redefined in a continuation record for the transrequest Template: CAPACITY_GRANTED, START_TIME, STOP_TIME. Specification of any values corresponding to COLUMN_HEADERs other than CAPACITY-GRANTED, START_TIME, and STOP_TIME will be ignored, however commas must be included to properly align the CAPACITY_GRANTED, START_TIME and STOP_TIME fields.
Input:
VERSION=1.4

TEMPLATE=transrequest

OUTPUT_FORMAT=DATA

PRIMARY_PROVIDER_CODE=AEP

PRIMARY_PROVIDER_DUNS=123456789

RETURN_TZ=ES

DATA_ROWS=7

COLUMN_HEADERS=CONTINUTATION_FLAG, SELLER_CODE,SELLER_DUNS, PATH_NAME, POINT_OF_RECEIPT, POINT_OF_DELIVERY, SOURCE, SINK,CAPACITY_REQUESTED, SERVICE_INCREMENT, TS_CLASS, TS_TYPE, TS_PERIOD, TS_WINDOW, TS_SUBCLASS, STATUS_NOTIFICATION,START_TIME,STOP_TIME,BID_PRICE, PRECONFIRMED, ANC_SVC_LNK, POSTING_REF, SALE_REF, REQUEST_REF, DEAL_REF, CUSTOMER_COMMENTS, REQUEST_TYPE,REASSIGNED_REF

N, AEP,123456789, ABC/XY, CE, MECS,,,35, DAILY, FIRM, POINT_TO_POINT, FULL_PERIOD, FIXED,, pub/AEP/incoming,20000423000000ES,20000424000000ES,24.5, Y, SC:(AEP:RQ);RV:(AEP:RQ);RF:(FT);EI:(FT);SP:(FT);SU:(FT);, P0123 , S123, R765, D123, Standard daily reservation, ORIGINAL, 

N, AEP,123456789, ABC/XY, CE, AMPO,,,5, HOURLY, NON-FIRM, POINT_TO_POINT, FULL_PERIOD, FIXED,, pub/AEP/incoming,20000423060000ES,20000423070000ES,2.5, Y, SC:(AEP:RQ);RV:(AEP:RQ);RF:(FT);EI:(FT);SP:(FT);SU:(FT);, P0123 , S123, R765, D123, First piece of profile spanning 5 records, ORIGINAL, 

Y,,,,,,,,10,,,,,,, ,20000423070000ES,20000423080000ES,,,,,,,, Second piece,, 

Y,,,,,,,,15,,,,,,, ,20000423080000ES,20000423200000ES,,,,,,,, Third piece,, 

Y,,,,,,,,10,,,,,,, ,20000423200000ES,20000423210000ES,,,,,,,, Fourth piece,, 

Y,,,,,,,,5,,,,,,, ,20000423210000ES,20000423220000ES,,,,,,,, Fifth piece,, 

N, AEP,123456789, ABC/XY, CE, MECS, , ,20, HOURLY, NON-FIRM, POINT_TO_POINT, FULL_PERIOD, FIXED,, pub/AEP/incoming,20000423040000ES,20000423160000ES,2, Y, SC:(AEP:RQ);RV:(AEP:RQ);RF:(FT);EI:(FT);SP:(FT);SU:(FT);, P0123 , S123, R765, D123, Standard hourly reservation after profiled reservation, ORIGINAL, 
Response:
REQUEST_STATUS=200

ERROR_MESSAGE=Successfully updated. 

TIME_STAMP=20000422160523ES

VERSION=1.4

TEMPLATE=transrequest

OUTPUT_FORMAT=DATA

PRIMARY_PROVIDER_CODE=AEP

PRIMARY_PROVIDER_DUNS=123456789

RETURN_TZ=ES

DATA_ROWS=7

COLUMN_HEADERS=RECORD_STATUS, CONTINUTATION_FLAG, ASSIGNMENT_REF, SELLER_CODE,SELLER_DUNS, PATH_NAME, POINT_OF_RECEIPT, POINT_OF_DELIVERY, SOURCE, SINK,CAPACITY_REQUESTED, SERVICE_INCREMENT, TS_CLASS, TS_TYPE, TS_PERIOD, TS_WINDOW, TS_SUBCLASS, STATUS_NOTIFICATION,START_TIME,STOP_TIME,BID_PRICE, PRECONFIRMED, ANC_SVC_LNK, POSTING_REF, SALE_REF, REQUEST_REF, DEAL_REF, CUSTOMER_COMMENTS, REQUEST_TYPE,REASSIGNED_REF, ERROR_MESSAGE

200,N,8234, AEP,123456789, ABC/XY, CE, MECS,,,35, DAILY, FIRM, POINT_TO_POINT, FULL_PERIOD, FIXED,, pub/AEP/incoming,20000423000000ES,20000424000000ES,24.5, Y, SC:(AEP:RQ);RV:(AEP:RQ);RF:(FT);EI:(FT);SP:(FT);SU:(FT);, P0123 , S123, R765, D123, Standard daily reservation, ORIGINAL,, No error

200,N,8235, AEP,123456789, ABC/XY, CE, AMPO,,,5, HOURLY, NON-FIRM, POINT_TO_POINT, FULL_PERIOD, FIXED,, pub/AEP/incoming,20000423060000ES,20000423070000ES,2.5, Y, SC:(AEP:RQ);RV:(AEP:RQ);RF:(FT);EI:(FT);SP:(FT);SU:(FT);, P0123 , S123, R765, D123, First piece of profile spanning 5 records, ORIGINAL,, No error

200,Y,8235,,,,,,,,10,,,,,,,,20000423070000ES,20000423080000ES,,,,,,,, Second piece,,, No error

200,Y,8235,,,,,,,,15,,,,,,,,20000423080000ES,20000423200000ES,,,,,,,, Third piece,,, No error

200,Y,8235,,,,,,,,10,,,,,,,,20000423200000ES,20000423210000ES,,,,,,,, Fourth piece,,, No error

200,Y,8235,,,,,,,,5,,,,,,,,20000423210000ES,20000423220000ES,,,,,,,, Fifth piece,,, No error

200,N,8236, AEP,123456789, ABC/XY, CE, MECS,,,20, HOURLY, NON-FIRM, POINT_TO_POINT, FULL_PERIOD, FIXED,, pub/AEP/incoming,20000423040000ES,20000423160000ES,2, Y, SC:(AEP:RQ);RV:(AEP:RQ);RF:(FT);EI:(FT);SP:(FT);SU:(FT);, P0123 , S123, R765, D123, Standard hourly reservation after profiled reservation, ORIGINAL,, No error


b. Submission of Reassignment Information - Case 1:
In the prior example, a reservation request was submitted to "Rseler" for 20MW of Hourly Non-firm service from 04:00 to 16:00. Assume that Rseler has previously reserved service for the CE-VP path for Daily Firm in amount of 50 MW on 4/23 under ASSIGNMENT_REF=7019, and Hourly Non-Firm in amount of 10 MW from 08:00 to 20:00 on 4/23 under ASSIGNMENT_REF=7880. Rseler must designate which transmission service rights are to be reassigned to Cust to satisfy the 20MW from 04:00 to 16:00. This reassignment information is conveyed by Rseler using the transsell Template when the reservation request is ACCEPTED. At the SELLER's discretion, rights are assigned from the Non-firm reservation first (ASSIGNMENT_REF=7880) with the balance taken up by the Firm reservation (ASSIGNMENT_REF=7019).

The only fields allowed in "continuation" records for transsell Template are REASSIGNED_REF, REASSIGNED_CAPACITY, REASSIGNED_START_TIME, and REASSIGNED_STOP_TIME. Price may not be negotiated for each "segment" in a capacity profile.


Input:
VERSION=1.4

TEMPLATE=transsell

OUTPUT_FORMAT=DATA

PRIMARY_PROVIDER_CODE=AEP

PRIMARY_PROVIDER_DUNS=123456789

RETURN_TZ=ES

DATA_ROWS=3

COLUMN_HEADERS=CONTINUATION_FLAG,ASSIGNMENT_REF, START_TIME, STOP_TIME,OFFER_PRICE,CAPACITY_GRANTED, STATUS, STATUS_COMMENTS, ANC_SVC_LINK, ANC_SVC_REQ, NEGOTIATED_PRICE_FLAG, SELLER_REF, SELLER_COMMENTS, RESPONSE_TIME_LIMIT,REASSIGNED_REF,REASSIGNED_CAPACITY, REASSIGNED_START_TIME , REASSIGNED_STOP_TIME

N,8236, 20000423040000ES, 20000423160000ES,2.5,20, ACCEPTED, Status comments here, SC:(AEP:RQ);RV:(AEP:RQ);RF:(FT);EI:(FT);SP:(FT);SU:(FT);, SC:M;RV:M;RF:U;EI:U;SP:U;SU:U;,, S123, Seller comments here,,7019,20, 20000423040000ES, 20000423080000ES

Y,8236,,, ,, , , ,,,, ,,7880,10, 20000423080000ES, 20000423160000ES

Y,8236,,, ,, , , ,,,, ,,7019,10, 20000423080000ES, 20000423160000ES
Response:
REQUEST_STATUS=200

ERROR_MESSAGE=Successfully updated. 

TIME_STAMP=20000422160523ES

VERSION=1.4

TEMPLATE=transsell

OUTPUT_FORMAT=DATA

PRIMARY_PROVIDER_CODE=AEP

PRIMARY_PROVIDER_DUNS=123456789

RETURN_TZ=ES

DATA_ROWS=3

COLUMN_HEADERS=RECORD_STATUS,CONTINUATION_FLAG,ASSIGNMENT_REF, START_TIME, STOP_TIME,OFFER_PRICE,CAPACITY_GRANTED, STATUS, STATUS_COMMENTS, ANC_SVC_LINK, ANC_SVC_REQ, NEGOTIATED_PRICE_FLAG, SELLER_REF, SELLER_COMMENTS, RESPONSE_TIME_LIMIT,REASSIGNED_REF,REASSIGNED_CAPACITY, REASSIGNED_START_TIME , REASSIGNED_STOP_TIME, ERROR_MESSAGE

N,,8236, 20000423040000ES, 20000423160000ES,2.5,20, ACCEPTED, Status comments here, SC:(AEP:RQ);RV:(AEP:RQ);RF:(FT);EI:(FT);SP:(FT);SU:(FT);, SC:M;RV:M;RF:U;EI:U;SP:U;SU:U;,, S123, Seller comments here,,7019,20, 20000423040000ES, 20000423080000ES, No error

Y,,8236,,, ,, , , ,,,, ,,7880,10, 20000423080000ES, 20000423160000ES, No error

Y,,8236,,, ,, , , ,,,, ,,7019,10, 20000423080000ES, 20000423160000ES, No error


c. Submission of Reassignment Information - Case 2:
Primary provider, AEP, is notified of a sale/assignment of transmission service rights from "Resell" to "cust". The parameters of the new reservation are for 10MW on 4/23 for "off-peak" hours (00:00- 06:00 and 22:00-24:00) on POR/POD CE-VP. Rseler is assigning rights to 10MW from a prior reservation for the CE-VP path for Daily Firm in amount of 50 MW on 4/23 under ASSIGNMENT_REF=7019 to Cust. AEP would submit the following information using the transassign Template to post this (re)sale. The only fields allowed in "continuation" records for the transassign Template are CAPACITY, START_TIME , STOP_TIME, REASSIGNED_REF, REASSIGNED_CAPACITY, REASSIGNED_START_TIME, and REASSIGNED_STOP_TIME. Even though there is a one-to-one correspondence between the segments of the new reservations and the reassignment of service from a prior reservation, it is entirely possible that a reservation spanning a single contiguous period would require multiple continuation records to convey reassignment information, and vice versa.
Fields for CUSTOMER_NAME and SELLER_NAME were used to convey user names for subsequent resolution of contact information from user registration.
1   2   3   4   5   6   7   8   9   10   11


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

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