Recommended Action: ___Accept as requested



1. RECOMMENDED ACTION: EFFECT OF EC VOTE TO ACCEPT RECOMMENDED ACTION:

X Accept as requested X Change to Existing Practice

Accept as modified below Status Quo

Decline

2. TYPE OF MAINTENANCE

Per Request: Per Recommendation:

Initiation Initiation

X Modification X Modification

Interpretation Interpretation

Withdrawal Withdrawal

Principle (x.1.z) Principle (x.1.z)

Definition (x.2.z) Definition (x.2.z)

Business Practice Standard (x.3.z) Business Practice Standard (x.3.z)

Document (x.4.z) Document (x.4.z)

X Data Element (x.4.z) X Data Element (x.4.z)

Code Value (x.4.z) Code Value (x.4.z)

X12 Implementation Guide X X12 Implementation Guide

Business Process Documentation X Business Process Documentation

3. RECOMMENDATION

Note – This request recommendation should be processed sequentially after the recommendation for R00012/R00013.

SUMMARY:

• Modify the usage of the data element “Releaser” from Mandatory to Conditional in NAESB WGQ 5.4.18 – Bid Upload

• Modify the 8th paragraph of the Technical Implementation of Business Practices (TIBP) in NAESB WGQ 5.4.18 – Bid Upload

DATA DICTIONARY (for new documents and addition, modification or deletion of data elements)

Document Name and No.: NAESB WGQ Std. No. 5.4.18 Bid Upload

|Business Name (Abbreviation) |Definition |EBB Usage |EDI/FF Usage|Condition |

|Releaser Data |The legal entity which signed the contract | | | |

| |with the transportation service provider. | | | |

|Releaser * 4 | |MC |MC |Mandatory when present in the Offer |

|(Releaser) | | | |Download. |

|Releaser Name | |MC |nu |For EBB, mandatory when present in the|

|(Releaser Name) | | | |Offer Download. |

|Releaser Proprietary Code | |C |C |Mandatory when present in the Offer |

|(Releaser Prop) | | | |Download and the Releaser is not |

| | | | |present. |

* Indicates Common Code

BUSINESS PROCESS DOCUMENTATION (for addition, modification or deletion of business process documentation language)

Standards Book: NAESB WGQ Capacity Release Related Standards:

NAESB WGQ 5.4.18 Bid Upload

|Language: Modify the eighth paragraph as follows: |

| |

|The Bid Upload contains the entity common code numbers for all parties involved in the transaction: the transportation service provider, |

|the bidder, and, when present in the Offer Download, the releasing shipperreleaser. Parties should mutually agree to use the Transportation|

|Service Provider's proprietary entity code when the D-U-N-S® Number is not available. |

TECHNICAL CHANGE LOG (all instructions to accomplish the recommendation)

Document Name and No.: NAESB WGQ Standard No. 5.4.18 Bid Upload

|Bid Upload, 5.4.18 |

|Data Element Xref to X12 |

|Header N1: Modify the Usage of the “Releaser/Releaser Proprietary Code” as follows: |

| |

|N1 C Releaser/Releaser Proprietary Code |

|Transaction Set Tables |

|REF Segments (Heading) table: For the “Releaser/Releaser Proprietary Code” row, modify the usage from “M” to “C1”. Under the table and |

|before the “Notes:” section, add a “Usage:” section as follows: |

| |

|Usage: |

| |

|C1 Mandatory when present in the Offer Download. |

4. SUPPORTING DOCUMENTATION

a. Description of Request:

b. Description of Recommendation:

Business Practices Subcommittee

See meeting minutes for Business Practices Subcommittee as follows:

• March 29, 2001

• April 12, 2001

Motion:

BPS instructs the Information Requirements Subcommittee to modify the usage of the data element Releaser Company Code in the Bid Upload (5.4.18) from mandatory to conditional, based upon whether the data is provided in the Offer Download (5.4.1).

|Vote | | | |Balanced |Balanced |Balanced |

| |For |Against |Total |For |Against |Total |

|End Users |1 |0 |1 |1.00 |0.00 |1 |

|LDCs |1 |0 |1 |1.00 |0.00 |1 |

|Pipelines |6 |0 |6 |2.00 |0.00 |2 |

|Producers |0 |0 |0 |0.00 |0.00 |0 |

|Services |0 |0 |0 |0.00 |0.00 |0 |

| |8 |0 |8 |4.00 |0.00 |4 |

Motion Passes

Information Requirements Subcommittee

See meeting minutes for Information Requirements Subcommittee as follows:

• March 17, 2005

Motion:

• Modify NAESB WGQ Std. 5.4.18 – Bid Upload as follows:

|Business Name (Abbreviation) |Definition |EBB Usage |EDI/FF |Condition |

| | | |Usage | |

|Releaser Data |The legal entity which signed the | | | |

| |contract with the transportation | | | |

| |service provider. | | | |

|Releaser * 4 | |MC |MC |Mandatory when present in the |

|(Releaser) | | | |Offer Download. |

|Releaser Name | |MC |nu |For EBB, mandatory when present |

|(Releaser Name) | | | |in the Offer Download. |

|Releaser Proprietary Code | |C |C |Mandatory when present in the |

|(Releaser Prop) | | | |Offer Download and the Releaser |

| | | | |is not present. |

• Modify the 8th paragraph of the TIBP as follows:

The Bid Upload contains the entity common code numbers for all parties involved in the transaction: the transportation service provider, the bidder, and, when present in the Offer Download, the releasing shipperreleaser. Parties should mutually agree to use the Transportation Service Provider's proprietary entity code when the D-U-N-S® Number is not available.

|Vote | | | |Balanced |Balanced |Balanced |

| |For |Against |Total |For |Against |Total |

|End Users |0 |0 |0 |0.00 |0.00 |0 |

|LDCs |0 |0 |0 |0.00 |0.00 |0 |

|Pipelines |8 |0 |8 |2.00 |0.00 |2 |

|Producers |0 |0 |0 |0.00 |0.00 |0 |

|Services |0 |0 |0 |0.00 |0.00 |0 |

| |8 |0 |8 |2.00 |0.00 |2 |

Motion Passes

Technical Subcommittee

See meeting minutes for Information Requirements Subcommittee as follows:

• January 17-18, 2006

Motion:

|Segments |Vote For |Balanced For |Vote Against |Balanced Against |

|End Users |0 |0 |0 |0 |

|LDCs |0 |0 |0 |0 |

|Services |0 |0 |0 |0 |

|Pipelines |7 |2 |0 |0 |

|Producers |0 |0 |0 |0 |

|Totals |7 |2 |0 |0 |

Motion passes

c. Business Purpose:

d. Commentary/Rationale of Subcommittee(s)/Task Force(s):

-----------------------

[pic]

................
................

In order to avoid copyright disputes, this page is only a partial summary.

Google Online Preview   Download