Mobile Bay Pipeline Company

Second Revised Volume No. 1

 Contents / Previous / Next / Main Tariff Index

 

 

Effective Date: 06/01/1997, Docket: RP97-155-003, Status: Effective

Original Sheet No. 362 Original Sheet No. 362 : Effective

 

 

ELECTRONIC DATA INTERCHANGE TRADING PARTNER AGREEMENT

(Continued)

 

Section 2. Transmissions.

 

2.1. Proper Receipt. There shall not be deemed to have been a "proper

receipt" of a Document until accessible to Receiver at such party's Receipt

Computer as evidenced by the receipt by Sender of the time-stamp response

initiated by Receiver indicating successful receipt of the Document in

accordance with the Standards. The method of time-stamp response to be

utilized by the parties shall be set forth in the Appendix. No Document shall

have any effect (a) for which a time-stamp response is not received by Sender

or (b) for which a time-stamp response indicating error is applicable.

 

2.2. Verification. Upon proper receipt of any Document, Receiver shall

verify that the Document originated from an authorized trading partner,

process the decryption of the Document, if 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 verified as from an authorized trading partner and Receiver's decryption of

the Document is successful, Receiver shall transmit a "Functional

Acknowledgment" to Sender. For purposes of this Agreement, a "Functional

Acknowledgment" means a transaction set 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. If (a) there has not been a

proper receipt by Sender of a Functional Acknowledgment to a Document for any

reason or (b) there has been a proper receipt by Sender of a Functional

Acknowledgment to a Document indicating error, in each case within the

"Functional Acknowledgment Deadline" indicated in the applicable EDI Exhibit

for such Document, the Document may not be relied upon by either party as an

effective Document for any purpose.

 

2.3. Response Document. By mutual agreement, the parties may designate in

the applicable EDI Exhibit a "Response Document" transaction set in addition

to a Functional Acknowledgment transaction set. A Response Document does not

include the time-stamp response specified in Section 2.1 hereof. 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 valid substantive data to effectuate the communication. If the

Response Document indicates valid substantive content, the communication set

forth in the applicable Document shall be deemed effectively completed under

the applicable transportation agreement between the parties or applicable

pooling agreement, balancing agreement, or storage agreement as indicated by

the service requester contract number stated in the EDI transaction. If the

Response Document does not indicate valid substantive content, the

communication set forth in the applicable Document shall be deemed not to have

been effectively completed under the applicable transportation agreement

between the parties, pooling agreement, balancing agreement, storage

agreement, or other applicable agreements.