Ozark Gas Transmission System
First Revised Volume No. 1
Contents / Previous / Next / Main Tariff Index
Effective Date: 06/01/1997, Docket: RP97-179-004, Status: Effective
Second Revised Sheet No. 41 Second Revised Sheet No. 41 : Superseded
Superseding: First Revised Sheet No. 41
GENERAL TERMS AND CONDITIONS
(Continued)
29. COMPLIANCE WITH GISB STANDARDS.
Transporter will comply with all GISB standards including,
but not limited to, the following:
Principle 1.1.4: Transporter will not require pre-nominations.
Principle 1.1.7: Transporter will neither require nor support
the use of activity codes.
Principle 1.1.8: Transporter and Customers shall use common
codes for location points and legal entities in all
communications.
Standard 1.3.27: The key should be composed of: service
requester (Service Agreement), transaction type, upstream party,
upstream contract (when applicable), receipt location (as
applicable), downstream party, (as applicable) downstream
contract (when applicable), delivery location (as applicable),
package ID, capacity type indicator (where mutually agreed),
service provider activity code (where mutually agreed). Upon
receipt by a service provider from service requester of a
transaction whose key elements match those previously received by
the service provider from the service requester, the service
provider should then process the begin date/time and end
date/time consistent with the intentions of the standard 1.3.7
and then process the rest of transaction's data elements
consistent with the applicable standards to determine the
business results. When data is not supplied (e.g. is not
applicable, is not supported or is not mutually agreed upon) the
pertinent portion of the key would be determined to be null.
Standard 1.3.28: For current in-kind fuel reimbursement
procedures, fuel rates should be made effective only at the
beginning of the month.
Principle 2.3.2: Two welded parties should agree on who submits a
predetermined allocation methodology and who allocates at the
point before gas flows.
Principle 4.1.1: The technology model and principles should be
followed in implementing GISB's business standards
electronically. The following schematic describes the EDM
technology model that should exist post 4/1/97, that as agreed
upon in the following standard is subject to validation:
4.3.1 By 4/1/97, all parties sending and receiving
data should accept a TCP/IP using PPP connection. At a
minimum, sending and receiving parties should designate
an internet address as a designated site for the
receipt and delivery of GISB standardized data sets
subject to the successful completion of pilot testing
by 1/1/97 to ensure that security, performance (within
GISB standard data transmission time), and reliability
are acceptable. The GISB data file format should be
utilized. The Future Technology Task Force should
determine the direction of outstanding issues such as
security, archiving, receipt notification, etc., by
7/1/96.