Venice Gathering System, L. L. C.
Original Volume No. 1
Contents / Previous / Next / Main Tariff Index
Effective Date: 09/01/2005, Docket: RP05-430-000, Status: Effective
Third Revised Sheet No. 178 Third Revised Sheet No. 178 : Effective
Superseding: Second Revised Sheet No. 178
GENERAL TERMS AND CONDITIONS
18. COMPLIANCE WITH NAESB STANDARDS
VGS will comply with all NAESB Standards adopted by
the Commission, including but not limited to the following:
Standard 0.3.1: Entity common codes should be "legal entities",
that is, Ultimate Location, Headquarters Location, and/or Single
Location (in Dun & Bradstreet Corporation ("D&B") terms).
However, in the following situations, a Branch Location (in D&B
terms) can also be an entity common code:
1. when the contracting party provides a D-U-N-S Number at
the Branch Location level; or
2. to accommodate accounting for an entity that is
identified at the Branch Location level.
Standard 0.3.2: Parties should mutually agree to use VGS'
proprietary entity code when the D-U-N-S Number is not available.
Principle 1.1.4: VGS will not require pre-nominations.
Principle 1.1.7: VGS will neither require nor support
Standard 1.3.27: The key will 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, upstream package ID (where mutually
agreed), downstream package ID (where mutually agreed), and
capacity type indicator (where mutually agreed). Upon receipt
by VGS from a Customer of a transaction whose key elements
match those previously received by VGS from the Customer,
VGS will process the begin date/time and end date/time as an
original nomination 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 will be null.
Standard 3.3.11: Information provided with (sales and
transportation) invoices will be consistent with information
previously provided by the billing party, as updated for
changes for settlement.