Recommended Action: ___Accept As Requested s4

RECOMMENDATION AS APPROVED BY THE NAESB WGQ EXECUTIVE COMMITTEE ON OCTOBER 25, 2012 Minor Correction / Clarification

Requester: Williams Gas Pipeline Request No.: MC12038

1. RECOMMENDED ACTION: EFFECT OF EC VOTE TO ACCEPT RECOMMENDED ACTION: X Accept as requested Change to Existing Practice Accept as modified below Status Quo Decline X Correction

2. TYPE OF DEVELOPMENT/MAINTENANCE Per Request: Per Recommendation: Initiation Initiation Modification 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) Data Element (x.4.z) Data Element (x.4.z) X Code Value (x.4.z) X Code Value (x.4.z) X X12 Implementation Guide X X12 Implementation Guide Business Process Documentation Business Process Documentation

3. RECOMMENDATION

SUMMARY: Correct / Update the recommendation for R05027 (adopted by the EC 8/23/12, ratified 9/28/12):

 Correct the Code Values Log for data element Validation Code (Sub-detail) in the following data set: Pre-determined Allocation Quick Response NAESB WGQ Standard No. 2.4.2

 Correct the references to the data element ‘Imbalance Period’ in the Data Element Cross Reference, Transaction set tables and/ or EDI x12 Mapping guidelines for the following data sets: Pre-determined Allocation Quick Response NAESB WGQ Standard No. 2.4.2 Shipper Imbalance NAESB WGQ Standard No. 2.4.4 Transportation / Sales Invoice NAESB WGQ Standard No. 3.4.1

 Update the Comment Note numbers in the PDA Transaction Type Matrix and Allocation Transaction Type Matrix in the following data sets, respectively: Pre-determined Allocation Quick Response NAESB WGQ Standard No. 2.4.1 Allocation ` NAESB WGQ Standard No. 2.4.3

CODE VALUES LOG (for addition, modification or deletion of code values) (Corrections highlighted)

Document Name and No.: Nominations Quick Response NAESB WGQ Standard No. 1.4.2 Pre-determined Quick Response NAESB WGQ Standard No. 2.4.2

Data Element: Validation Code (Sub-detail)

Code Value Code Value Description Code Value Definition WNMQR546 Imbalance Period not processed [no definition necessary] WNMQR548 Route not processed [no definition necessary] ENMQR599 Invalid Imbalance Period [no definition necessary] ENMQR601 Invalid Route [no definition necessary] ENMQR600 Missing Imbalance Period [no definition necessary] WNMQR547 Missing Imbalance Period [no definition necessary] ENMQR602 Missing Route [no definition necessary] WNMQR549 Missing Route [no definition necessary]

Document Name and No.: Pre-determined Quick Response NAESB WGQ Standard No. 2.4.2

Data Element: Validation Code (Sub-detail)

Code Value Code Value Description Code Value Definition EPDQR544 Invalid Imbalance Period [no definition necessary] EPDQR545 Missing Imbalance Period [no definition necessary] EPDQR546 Invalid Route [no definition necessary] EPDQR547 Missing Route [no definition necessary] WPDQR523 Imbalance Period not processed [no definition necessary] WPDQR524 Missing Imbalance Period [no definition necessary] WPDQR525 Route not processed [no definition necessary] WPDQR526 Missing Route [no definition necessary]

Description of Change: Pre-determined Allocation Quick Response (2.4.2) Transaction Set Tables Errors and Warnings (Sub-detail) table: For the data element “Validation Code”, insert code values “EPDQR544”, “EPDQR545”, “EPDQR546”, “EPDQR547”, “WPDQR523”, “WPDQR524”, “WPDQR525”, “WPDQR526”, “WPDQR549” and their descriptions in alphabetic/numeric order by code value as follows:

Validation Code (III02) Code Value Description EPDQR544 Invalid Imbalance Month Period EPDQR545 Missing Imbalance Month Period EPDQR546 Invalid Route EPDQR547 Missing Route WPDQR523 Imbalance Month Period not processed WPDQR524 Missing Imbalance Month Period WPDQR525 Route not processed WPDQR526 Missing Route

Description of Change: Shipper Imbalance (2.4.4) Data Element Cross Reference to ASC X12 Sub-Detail DTM Following the REF segment, insert one blank line and then one new DTM row for data element ‘Imbalance MonthPeriod’ with usages of before the LQ ‘ Capacity Type Indicator’ data element row so the end result is as follows

REF SO SO SO SO Zone Identifier REF MA MA MA MA Package ID REF MA MA MA MA Service Provider’s Activity Code DTM C C C C Imbalance MonthPeriod LQ MA MA MA nu Capacity Type Indicator LQ MA MA MA MA Export Declaration

ASC X12 Mapping Guidelines Add DTM segment as position 7850: Add segment level note: ‘For NAESB WGQ, this segment is conditional’ Mark all data elements as not used Mark DTM01 as used Mark code value ‘IMB’ as used Mark DTM05 as used Mark code value ‘CM’ as used Mark DTM06 as used Add data element level note ‘Imbalance MonthPeriod’

Description of Change: Transportation / Sales Invoice (3.4.1) Data Element Cross Reference to ASC X12 Sub-Detail DTM Following the REF segment, insert one blank line and then one new DTM row for data element ‘Imbalance MonthPeriod’ with usages of before the LQ ‘ Capacity Type Indicator’ data element row so the end result is as follows:

REF MA Downstream Contract Identifier REF MA Package ID REF MA Replacement Release Code REF MA Upstream Contract Identifier DTM C Imbalance Month Period LQ M Charge Indicator LQ M Location Indicator LQ M Service Code LQ M Transaction Type

ASC X12 Mapping Guidelines Add DTM segment as position 7850: Add segment level note: ‘For NAESB WGQ, this segment is conditional’ Mark all data elements as not used Mark DTM01 as used Mark code value ‘IMB’ as used Mark DTM05 as used Mark code value ‘CM’ as used Mark DTM06 as used Add data element level note ‘Imbalance MonthPeriod’

PDA Transaction Type Matrix

The following matrix shows the data elements that are dependent on the PDA transaction type code. A blank cell indicates that the data element is not used for the specified PDA transaction type code.

Reflects changes from R05027 as corrected

Usage when PDA transaction type code is: Data Element 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 n1 Imbalance Period C12 C12 C12 C12 C12 C10 C10 C10 C10 C10

Route C13 C13 C13 C13 C13 C11 C11 C11 C11 C11

NOTES: n1 No dependent data elements for this PDA transaction type.

USAGE: C12 C10 Business conditional when present and processed in the original nomination. Used when the Transportation Service Provider offers the ability for service requesters to identify the month to which the imbalance payback nomination applies, and the Transaction Type indicates that it is an imbalance payback. C13 C11 Business conditional when present and processed in the original nomination. Used when the Transportation Service Provider offers the ability for service requesters to identify a specific route for a nominated transaction.

Allocation Transaction Type Matrix

The following matrix shows the data elements that are dependent on the allocation transaction type code. A blank cell indicates that the data element is not used for the specified allocation transaction type code.

Reflects changes from R05027 as corrected

Usage when allocation transaction type code is: Data Element 1 2 3R 3D 4R 4D 5R 5D 6R 6D 7R 7D 8R 8D 9R 9D 10R 10D 11R 11D 12R 12D 13 14R 14D 15R 15D

Imbalance Period C16 C16 C16 C16 C16 C16 C16 C16 C16 C16 C16 C14 C14 C14 C14 C14 C14 C14 C14 C14 C14 C14

Route C17 C17 C17 C17 C17 C17 C17 C17 C17 C17 C17 C15 C15 C15 C15 C15 C15 C15 C15 C15 C15 C15

USAGE: C16 C14 Mandatory when present and processed in either the nomination or the pre-determined allocation. Used when the Transportation Service Provider offers the ability for service requesters to identify the month to which the imbalance payback nomination applies, and the Transaction Type indicates that it is an imbalance payback. C17 C15 Mandatory when present and processed in either the nomination or the pre-determined allocation. Used when the Transportation Service Provider offers the ability for service requesters to identify a specific route for a nominated transaction .

4. SUPPORTING DOCUMENTATION a. Description of Request:

Minor Corrections to recommendation R05027:  Correct the Code Values Log for data element Validation Code (Sub-detail) in the following data set: Pre-determined Allocation Quick Response NAESB WGQ Standard No. 2.4.2

 Correct the references to the data element ‘Imbalance Period’ in the Data Element Cross Reference, Transaction set tables and/ or EDI x12 Mapping guidelines for the following data sets: Pre-determined Allocation Quick Response NAESB WGQ Standard No. 2.4.2 Shipper Imbalance NAESB WGQ Standard No. 2.4.4 Transportation / Sales Invoice NAESB WGQ Standard No. 3.4.1

 Update the Comment Note numbers in the PDA Transaction Type Matrix and Allocation Transaction Type Matrix in the following data sets, respectively: Pre-determined Allocation Quick Response NAESB WGQ Standard No. 2.4.1 Allocation ` NAESB WGQ Standard No. 2.4.3

Reason for of Minor Correction/Clarification: The recommendation for R05027 (adopted by the EC 2/23/12, ratified 3/30/12) included modifications to the Code Values Log for data element Validation Code (Sub-detail) in the PDA Quick Response. The proposed modifications for this data element inadvertently reflected the code values from the Nomination Quick Response.

Additionally, the name of the data element ‘Imbalance Period’ is incorrectly referred to as ‘Imbalance Month’ in the following locations:  PDA Quick Response (NAESB WGQ Standard No. 2.4.2) Transaction Set Table  Shipper Imbalance (NAESB WGQ Standard No. 2.4.4) Data Element Cross Reference and ASC X12 Mapping Guidelines  Transportation / Sales Invoice (NAESB WGQ Standard No. 3.4.1) Data Element Cross Reference and ASC X12 Mapping Guidelines

Last, in the PDA Transaction Type Matrix and the Allocation Transaction Type Matrix, two additional notes were added. Subsequently in the recommendation for WGQ 2012 Annual Plan Item 8 – Location Codes, two of the data elements with notes were deleted, this requiring a renumbering of the two notes added in R05027.

The purpose of this minor correction is to correct this error.

b. Description of Recommendation:

Information Requirements / Technical Subcommittee See minutes for the following Joint Information Requirements / Technical Subcommittees meetings:  October 23-24, 2012

Motion: Adopt the proposed modifications for MC12038 as set forth in Attachment 3 to the meeting minutes of October 23-24, 2012.

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 6 0 6 2.00 0.00 2 Producers 0 0 0 0.00 0.00 0 Services 1 0 1 1.00 0.00 1 7 0 7 3.00 0.00 3

Motion Passes