Columbia Gulf Transmission Company
Second Revised Volume No. 1
Contents / Previous / Next / Main Tariff Index
Effective Date: 06/01/1997, Docket: RP97-166-005, Status: Effective
Original Sheet No. 411 Original Sheet No. 411 : Effective
TRADING PARTNER AGREEMENT
ELECTRONIC DATA INTERCHANGE (Cont'd)
1.3. System Operations. Each party, at its own expense, shall provide and maintain the equipment, software,
services and testing necessary to effectively and reliably transmit and receive Documents.
1.4. Security Procedures. Each party shall properly use those security procedures, including those specified
in the Appendix, if any, which are reasonably sufficient to ensure that all transmissions of Documents are
authorized and to protect its business records and data from improper access.
1.5. Signatures. Each party shall adopt as its signature an electronic identification consisting of symbol(s)
or code(s) which are to be affixed to or contained, where required, in the Document transmitted by such party
("Signature Code(s)"). Such Signature Code(s) shall be specified in the Appendix. In such cases where a
Signature Code(s) is required for one or more Transaction Set(s), the requirement shall be specified in the
Appendix applicable to such Transaction Set(s). Each party agrees that the Signature Code(s) of such party
affixed to or contained in any transmitted Document shall be sufficient to verify such party originated such
Document(s). No party shall disclose to any unauthorized person the Signature Code(s) of any other party.
Section 2. Transmissions.
2.1. Proper Receipt. 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 Appendix. Where the parties employ the services of Providers to transmit and receive
Documents, the Receipt Computer shall be defined in the Appendix as the Computer provided by the receiving
party's Provider, for Transmission.
2.2.1. Upon proper receipt of any Document, the receiving party shall promptly and properly transmit a
functional acknowledgment in return, unless otherwise specified in the Appendix.
2.2.2. For the purposes of this Agreement, a "functional acknowledgment" means an ASC X12 Transaction Set
997, which confirms a Document (in the format specified by such acknowledgment) has been received and whether
all required portions of the Document are syntactically correct, but which does not confirm the substantive
content(s) of the related Document.
2.2.3. By mutual agreement, the parties may designate in the Appendix a "response document" as a substitute
for or in addition to an ASC X12 Transaction Set 997. A "response document" confirms that a Document (in the
format specified by such acknowledgment) 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. If the parties designate a response document as a substitute
for a functional acknowledgment, the time requirements in the Appendix applicable to functional acknowledgments
shall apply to such response documents.
2.2.4. A functional acknowledgment, or a response document that has been designated in the Appendix as a
substitute for a functional acknowledgment, shall constitute conclusive evidence a Document has been properly
2.2.5. Except as to conditions governed under Section 2.4, in the event the receiving party fails to promptly
and properly transmit a functional acknowledgment or response document in return for a properly received
Document, where required, the originating party's records of the contents of the Document shall control.