Oktex Pipeline Company

Original Volume No. 1

 Contents / Previous / Next / Main Tariff Index

Effective Date: 02/01/2010, Docket: RP10-205-001, Status: Effective

First Revised Sheet No. 60G First Revised Sheet No. 60G

Superseding: Original Sheet No. 60G

FORM OF

ELECTRONIC DATA INTERCHANGE

TRADING PARTNER AGREEMENT

2.1.2 Documents shall not be deemed to have been properly received, and

no Document shall give rise to any obligation, until accessible to the

receiving party at such party's Receipt Computer designated in the TPW, as

evidenced by the receipt by sending party of the HTTP response initiated by

receiving party. The HTTP response shall specify the date and time of receipt

of a Document at the receiving Internet server (also called "time-c"). No

Document shall have any effect if the HTTP response is not received by sending

party, or if the HTTP response indicates an error.

2.2 Digital Signature Verification and Decryption. Upon proper receipt of

any Document, the receiving party shall attempt to decrypt the Document and

verify the digital signature of the sending party. If the Document is

verified and the decryption is successful, the receiving party shall transmit

a Functional Acknowledgment in return. If the Document is verified and the

decryption is unsuccessful, the receiving party shall send the applicable

error message to the sending party. The sending party shall attempt to

correct the error and promptly retransmit the Document or otherwise contact

the receiving party.

2.3 Functional Acknowledgement and Response Document

2.3.1 For the purposes of this Agreement and the TPW, a "Functional

Acknowledgment" means an ASC X12 Transaction Set 997 which confirms a Document

has been received and whether all required portions of the Document are

syntactically correct or not, but which does not confirm the substantive

content(s) of the related Document.

2.3.2 If the Functional Acknowledgment indicates an error, neither party

shall rely on the Document. The sending party shall attempt to correct the

error and promptly retransmit the Document or otherwise contact the receiving

party. If the Functional Acknowledgment does not indicate any error, the

Functional Acknowledgment shall constitute conclusive evidence a Document has

been received in syntactically correct form.

2.3.3 If there has been proper receipt pursuant to Section 2.1,

verification and successful decryption pursuant to Section 2.2, and if the

receiving party nevertheless fails to transmit a Functional Acknowledgement,

the sending party's records of the contents of the Document shall control,

unless the sending party has retransmitted a Document pursuant to Section

2.3.7.