ࡱ> ^`]` bjbj mH $* P>!Z!*;!!""""""****AX*D2D:K<h>:#""##:"":X@&@&@&#X""*@&#*@&@&r'T ("! 0 2 H$|'(M;H;'?$$? (? (|"LL"6@&","B"""::%X""";####*** *** ***  As a customer service for those choosing to do business via EDI/EDM (Electronic Data Interchange/Electronic Delivery Mechanism) ASC (Accredited Standards Committee) X-12 data exchange with Williams Gas Pipeline-Transco and Pine Needle(WGP-Transco, WGP-Pine Needle ), we have created a specific guide to assist integration with our 1Line system. This guide is written for programmers to use when writing code and configuring the translator for ASC X-12 data to communicate with WGP-Transco via an encrypted file. Our implementation guides are based on the NAESB WGQ Implementation Guide Version 1.7, dated December 31, 2003. The intent of this guide is to explain how non-mandatory data elements in this particular data dictionary (specified in the title of this document) are used. The complete series of manuals are available from the NAESB office with more detail, usage instructions and thorough descriptions for all data elements. There are four usage types that NAESB uses for data elements; M- Mandatory, MA- Mutually Agreed, BC- Business Conditional and, SO- Senders Option. Please see the NAESB Implementation Guides for details on the definitions of the above. The only elements that we will be discussing in detail in this document are the MA, BC and SO. The mandatory data elements are incorporated automatically in this guide as they are mapped to the ASC X-12 data structure in the example/sample. Again, mandatory data elements are not individually highlighted as this can be done using the NAESB WGQ version 1.7 implementation guides available directly from NAESB. These implementation guides are WGP-Transco specific. If you have any questions please call: Diama Cortez (713) 215-4611 Data DictionaryWhen sending the Allocation dataset, WGP uses the NAESB WGQ Data Dictionary as published; no additional data elements are utilized by WGP. SYNOPSIS OF MA AND SO DATA ELEMENTS Data Element Name NAESB WGQ Usage WGP Usage Ending Imbalance Quantity MA Not Used Ending Imbalance Value MA Not Used Operational Quantity SO Not Used Penalty Variance Quantity SO Not Used A NOTE ON DATA AVAILABILITY AND CONTENT WGP will make daily allocation information available during the month. This data will reflect a Statement Basis of Estimated and will be available by approximately 8am for all previous days in the month to date. WGP will make allocation information for the entire month available after the month closes. This data will reflect a Statement Basis of Actual and will be available approximately 6 working days after a month ends. The Actual information will not change unless a Prior Period Adjustment (PPA) is made, in which case WGP will send the corrected volume reflecting a Statement Basis of Revision. EDI SEGMENTS HEADER ST 01 865 02 transaction set control number BCA 01 00 03 number assigned by the allocation statement document originator 06 issue date PER 01 IC 02 Contact Person (Name) 03 TE 04 Contact Person (Phone) DTM 01 102 06 DT (CCYYMMDDHHMM) 07 Statement Date/Time DTM 01 582 06 CM (CCYYMM) 07 Accounting Period N1 01 P1 03 1 (D-U-N-S) or SV (Service Provider Number) 04 Preparer ID /Preparer ID Proprietary Code N1 01 ZD 03 1 (D-U-N-S) or SV (Service Provider Number) 04 Statement Recipient ID /Statement Recipient ID Proprietary Code DETAIL--CONTRACT LEVEL POC 01 assigned identification 02 OA 08 TP Allocation Transaction Type Code--see table below Allocation Transaction Type Code Table Values Used  When Used9DFor all delivery allocations9RFor all receipt allocations13XFor all bi-directional allocations SI 01 AP 02 SB 03 Statement Basis 04 DF 05 Direction of Flow 06 AT 07 Adjustment Type DTM 01 211 06 RD8 (CCYYMMDD-CCYYMMDD) RDT (CCYYMMDDHHMM-CCYYMMDDHHMM) 07 Beginning Flow Date, Beginning Flow Time, Ending Flow Date, Ending Flow Time N1 01 RL 03 29 (DRN), or ZY (Transportation Service Providers proprietary code 04 Location Code / Location Proprietary Code SUBDETAIL--LINE LEVEL SLN 01 assigned identification 03 I 04 Allocated Quantity 05 BZ (million BTUsequivalent to dekatherms) 09 CR 10 Service Requester Contract SI 01 AP 02 see table of values below . . 17 SI Segment (Sub-detail)--Table of Values Element Name Usage Element 1000 Element 234 Upstream Contract Identifier C UK Upstream Contract Identifier Downstream Contract Identifier C DK Downstream Contract Identifier Package ID C PG Package ID Transaction Type  C TT Transaction Type  Note that the data element 1000/234 pairs above can be sent in any order, and that only the applicable pairs will be sent. Thus, if a transaction uses only the Upstream Contract Identifier and the Package ID from the above list, then only the first two data element 1000/234 pairs in the segment will be used. PO3 01 Z1 06 Scheduled Quantity 07 BZ (million BTUsequivalent to dekatherms) N1 01 US 03 1 (D-U-N-S) or SV (Transportation Service Providers proprietary code) 04 Upstream Identifier Code / Upstream Identifier Proprietary Code N1 01 DW 03 1 (D-U-N-S) or SV (Transportation Service Providers proprietary code) 04 Downstream Identifier Code / Downstream Identifier Proprietary Code N1 01 78 03 1 (D-U-N-S) or SV (Transportation Service Providers proprietary code) 04 Service Requester ID / Service Requester Proprietary Code N1 01 MQ 03 29 (DRN) or ZY (Transportation Service Providers proprietary code) 04 Delivery Location / Delivery Location Proprietary Code N1 01 M2 03 29 (DRN) or ZY (Transportation Service Providers proprietary code) 04 Receipt Location / Receipt Location Proprietary Code SUMMARY CTT 01 the number of POC segments SE 01 the number of included segments transaction set control number     Williams Gas Pipeline (WGP) EDI Implementation Guide AllocationSent by WGP NAESB WGQ 2.4.3 ------------------------------------------------------------------------------------------------------------------ April 22, 2005 Page  PAGE 1 of 5  ] a mRyzWX^23BCJ!*Oy"%;#$/0꽹hh*hvghOhzv h* h*\h*hV<huh:$If d$IfkkdH$$Ifx\ r$ 4 xax >?@_`bcfg}uuu:$If  !:$If d$Ifkkd$$Ifx\ r$ 4 xax :$If d$Ifkkd$$Ifx\ r$ 4 xax :$If d$Ifkkd=$$Ifx\ r$ 4 xax 3abmQ$`a$$a$kkd$$Ifx\ r$ 4 xax,-8G EFGOqr$^`a$gd!$`a$$a$$`a$#$%d$a$$a$I$ & FEƀ+qa$"#h?@_`bcfg3abmQ,-8G EFGOqr#$%0h0000000000000000000000000000000000000000000000000000000000000000 00000 00 0 0 0 0 0 0 0 0 0 0 0000000000000000000000000000000000000000000 000 00 000 0 00 00 00 00 0 00 00 00 00 0 00 00 00 00 0 00 00 00 00 0 0000000000000000000000000000000000 00I00y00I00y00I00y00I00y00@0@0@0I00@0@0I00y00x jj         #A H> !"!tGQF:#HQF,!IQFl!JQFKQF`hhqjj8*urn:schemas-microsoft-com:office:smarttagsdateV*urn:schemas-microsoft-com:office:smarttagsplacehttp://www.5iantlavalamp.com/B*urn:schemas-microsoft-com:office:smarttagscountry-region `Y12200331DayMonthYear[_ ! 333m #$OPGGYY !""drNft#VkQirEDy~ 0^`0o(0^`0o( 0^`0o(hh^h`.#VDy~Qidrl u!'/\3Lf>@:S2a m?_bf@hp officejet 7100 seriesNe01:winspoolhp officejet 7100 serieshp officejet 7100 series!@h߀,LdDrvConvertBe@RLd Beںں\\GHOUT50053492\hp officejet 7100 series,LocalOnly,DrvConverthp officejet 7100 series!@h߀,LdDrvConvertBe@RLd Beںں\\GHOUT50053492\hp officejet 7100 series,LocalOnly,DrvConvert@@UnknownWILLIAMS COMPANIES, INC.TranamcGz Times New Roman5Symbol3& z Arial" hr&Z&ʔ&dV )dV )! d2A HP? 2=General--Transco uses the GISB Implementation Guide Version 1IsbajekWILLIAMS COMPANIES, INC.    Oh+'0 @L l x  @General--Transco uses the GISB Implementation Guide Version 1Isbajek Normal.dotWILLIAMS COMPANIES, INC.14Microsoft Office Word@L@]I@@p@2dV՜.+,04 hp  Williams-Transco)  >General--Transco uses the GISB Implementation Guide Version 1 Title  !"#$&'()*+,./0123456789:;<=>?@ABCDEFGHIJKLNOPQRSTVWXYZ[\_Root Entry F& 2aData %1Table-?WordDocumentmHSummaryInformation(MDocumentSummaryInformation8UCompObjq  FMicrosoft Office Word Document MSWordDocWord.Document.89q