Reliant Energy Gas Transmission Company
Fifth Revised Volume No. 1
Contents / Previous / Next / Main Tariff Index
Effective Date: 09/20/1999, Docket: RP99-473-000, Status: Effective
First Revised Sheet No. 527 First Revised Sheet No. 527 : Effective
Superseding: Original Sheet No. 527
Section 2. Transmissions
2.1 Proper Receipt
2.1.1 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 Exhibit(s), 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.1.2 The "Receipt Computer" shall be defined in the Exhibit(s) as the receiving party's Uniform
Resource Locator ("URL"), which describes the protocols which are needed to access the resources and point to
the appropriate Internet locations. Where the parties employ the services of Providers to transmit and receive
Documents, the Receipt Computer shall be defined in the Exhibit(s) as the receiving party's URL provided by
the receiving party's Provider.
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 Acknowledgment and Response Document
2.3.1 For the purposes of this Agreement, 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 Acknowledgment,
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.
2.3.4 By mutual agreement, the parties may designate in the Exhibit(s) a "Response Document"
Transaction Set as a substitute for or in addition to an ASC X12 Transaction Set 997. A Response Document
confirms that a Document has been received, and whether all required portions of the Document are syntactically
correct, and contains data sent by the receiving party to the sending party in response to the substantive
content of the related Document.
2.3.5 If the Response Document indicates an error, neither party shall rely on the Document or
portion of the Document which is in error, if known. The sending party shall attempt to correct the errors and
promptly retransmit the Document or applicable portion or otherwise contact the receiving party. If the
Response Document does not indicate any error, the Response Document shall constitute conclusive evidence a
Document has been received in syntactically correct form.
2.3.6 If the parties have mutually agreed to the use of a Response Document, and 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 Response Document, 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.
2.3.7 Retransmissions. If the sending party of a Document has not received a corresponding
functional acknowledgment or response document within the time frame indicated in the Exhibit(s), the sending
party shall retransmit the Document and such Document shall be considered a new transmission for purposes of
Section 2.