Business Practices Subcommittee
Proposed Modified to NAESB WGQ Standards
Work Paper
08/11/2011
Proposed NAESB WGQ Standard No. 0.3.z1 [formerly part of NAESB WGQ Standard No. 4.3.56]
The industry should use codes assigned by the Transportation Service Provider for locations and common codes for legal entities when communicating via EDI/EDM, EBB/EDM, and/or FF/EDM. The corresponding code name should also be used in EBB/EDM.
Proposed NAESB WGQ Standard No. 0.3.z2
For NAESB WGQ,codes for locations are identifiers assigned by the Transportation Service Provider. There are no industry common codes for locations.
Proposed NAESB WGQ Standard No. 0.3.z3
The Transportation Service Provider (TSP) should provide on its Informational Postings Web Site location information, pursuant to NAESB WGQ Standard No. [0.4.z1]. At a minimum, at all pipeline-to-pipeline (interstate and intrastate) interconnecting locations, the TSP should identify the name, entity code, and point location code of the interconnecting entity. The location information should be made available prior to a location’s initial use for NAESB WGQ reporting and transactional business purposes.
Proposed NAESB WGQ Standard No. 0.3.z4
Data provided pursuant to NAESB WGQ Standard No. [0.3.z3] should be provided in a comma separated value (CSV) downloadable file to be described by the Transportation Service Provider. The format of this file should comply with NAESB WGQ Standard Nos. 4.3.80 and 4.3.81.
Proposed NAESB WGQ Standard No. 0.3.z5 [formerly part of NAESB WGQ Standard No. 4.3.51]
Codes assigned by the Transportation Service Provider for locations should be available for data validation or selection (viewing) on a Customer Activities Web site.
Proposed Modified NAESB WGQ Standard No. 0.3.z6 [formerly part of NAESB WGQ Standard No. 4.3.51]
Common codes for entities should be available for data validation or selection (viewing) on a Customer Activities Web site and in a standardized downloadable format for use by customers and third party service providers. Cross-references to proprietary codes for entities may be provided on a mutually agreeable basis.
Proposed Modified NAESB WGQ Standard No. 1.3.55
The Content Area of the nominations browser display should provide access to aquery or listing of receipt and delivery point location codes/names/common codes fromwhich to pick, in order to populate this data during transaction entry or selection.
Proposed Modified NAESB WGQ Standard No. 1.3.73
Where a Transportation Service Provider (TSP) has decided to offer TitleTransfer Tracking (TTT) service by means of an arrangement (including anagreement) with a party which will act as the TSP's designated party, andregardless of communication methodology between Account Holders and suchdesignated party, the TSP should, upon request, identify the Title TransferTracking Service Provider(s) (TTTSPs) at a location which have establishedactive TTT arrangements with the TSP. The relevant information to be providedshould include the name of each TTTSP, the ID code for each TTTSP used bythe TSP, the contract number for each TTTSP assigned by the TSP (whereapplicable), the location code(s) for each TTTSP assigned by the TSP (whereapplicable), and the location code(s) nominatable to the TSP for transportationservice to or from the location associated with each TTTSP. If, in the future, thecommon code for locations central repository includes listing of TTTSPs bylocation, the requirements of this standard may be met.
Proposed Deleted NAESB WGQ Standard No. 3.3.1
Electronic invoicing functions should use common codes as identified by theNAESB WGQ Common Codes Task Force.
Proposed Deleted NAESB WGQ Standard No. 4.3.51
NAESB WGQ Common Codes for entity and location should be available for data validation or selection (viewing) on a Customer Activities Web site and in a standardized downloadable format for use by customers and third party service providers. Cross-references to proprietary codes may be provided on a mutually agreeable basis.
Proposed Deleted NAESB WGQ Standard No. 4.3.56
The industry should use common codes for location points and legal entities when communicating via EDI/EDM, EBB/EDM and/or FF/EDM. The corresponding common code name should also be used in EBB/EDM.