Gulf States Transmission Corporation

Original Volume No. 1

 Contents / Previous / Next / Main Tariff Index

 

 

Effective Date: 10/01/2002, Docket: RP02-431-000, Status: Effective

Second Revised Sheet No. 71 Second Revised Sheet No. 71 : Effective

Superseding: First Revised Sheet No. 71

 

 

TRADING PARTNER AGREEMENT

for the Electronic Data Interchange

of Information Over the Public Internet (continued)

 

 

Section 2. Transmissions.

 

2.1. Proper Receipt. Documents shall not be deemed to have been properly

received until accessible to the receiving party at such party's Receipt

Computer (designated in the Appendix by Uniform Resource Locator ("URL

code")), as evidenced by the receipt of the sending party of the hyper-

text transfer protocol ("HTTP") response initiated by the receiving party

indicating successful receipt of the Document in accordance with NAESB

standards. No Document shall have any effect where an HTTP response is

not received by the sending party or where an HTTP response has indicated

that an error has occurred.

 

2.2. Verification.

 

2.2.1. Upon Proper Receipt of any Document, the receiving party shall

verify the legitimacy of the Document, process the decryption

of the Document as necessary, and translate the Document in

accordance with the Standards to determine whether the Document

contains all of the required data in proper syntactical form.

If the Document is legitimate and successfully decoded, the

receiving party shall transmit either a Functional

Acknowledgment or a Response Document to the sending party by

the Acknowledgment Deadline, all as set forth in the Appendix.

A Functional Acknowledgment means an ASC X12 transaction set

997, which confirms (in the format specified thereby) whether

or not all required portions of the Document are complete and

syntactically correct, but which does not address or otherwise

confirm the substantive content of the Document. A Response

Document is a transaction set in substitution of the ASC X12

Functional Acknowledgment transaction set 997. For purposes of

this Agreement, a Response Document confirms (in the format

specified thereby) whether or not the substantive content of

the corresponding Document contains data that is sufficiently

accurate to effectuate the communication, confirms whether or

not all required portions of the Document are complete and

syntactically correct and may contain data sent by the

receiving party to the sending party in response to the

substantive content of the related Document.

 

2.2.2. If there has not been a Proper Receipt by the sending party of

a Functional Acknowledgment or Response Document (as

applicable) to a Document for any reason, or there has been a

Proper Receipt by the sending party of a Response Document or

Functional Acknowledgment indicating error, the Document shall

not be relied upon by either party as an effective Document for

any purpose and the sending party, within the Retransmission

Timeframe (as set forth in the Appendix), may elect to

retransmit the Document.

 

2.2.3. A Functional Acknowledgment, or a Response Document (that has

been designated in the Appendix as a substitute for a

functional acknowledgment) with Proper Receipt that does not

indicate error shall constitute conclusive evidence a Document

has been received.