Appendix_6.5 _IGC_Data_Feed_Requirements.pdf

Appendix 6.5

APPENDIX 6.5

IGC DATA FEED REQUIREMENTS

Electronic Instructions:

1. Electronic Data Interchange (EDI) is the computer-to-computer exchange of business data in machine-readable language using strictly defined public standards.

2. An EDI Implementation Convention (IC) defines the rules for filling in or "populating" an EDI transaction. Following the agreed upon convention, or version of the standard ensures that EDI partners will encounter fewer data quality problems during development and maintenance of their EDI systems.

3. ANSI ASC X12 is the American National Standards Institute (ANSI) who charters the Accredited Standards Committee (ASC) X12 to develop uniform standards for inter-industry electronic interchange of business transactions -- electronic data interchange (EDI).

4. Accredited Standards Committee X12 develops, maintains, interprets, publishes and promotes the proper use of American National and UN/EDIFACT International EDI Standards. The ASC X12 body meets periodically to develop and maintain EDI standards. Its main objective is to develop standards to facilitate electronic interchange relating to business transactions. X12 standards facilitate transactions by establishing a common, uniform business language for computers to communicate. With more than 275 transaction sets, X12 standards can be used to electronically conduct nearly every facet of business-to-business operations.

5. EDI status records are generated and populated from the ANSI ASC 214A transactions. Transactions are sent to the government value added network where they are mapped and forwarded to IDE/GTN Global Convergence (IGC) (formerly Global Transportation Network (GTN).

6. Global Exchange Service (GEX) is an EDI-based Defense Information Systems Agency (DISA) system which provides EDI messages to United States Transportation Command (USTRANSCOM) and other Department of Defense (DOD) agencies.

7. To get the latest version of the DOD 214 A, Implementation Convention, visit the DTEB website at http://www.transcom.mil/dteb/files/transportationics/dt214a41.pdf . For information on how to establish an interface with the GEX, contact the GEX at (614) 692-5344 or by email at Cols-EDI@csd.disa.mil Monday through Friday, Between 8 am and 5 pm Eastern Time; afterhours, or during weekends or holidays, the GEX can be reached at 1-866-618-5988 or by email at gex_admin@csd.disa.mil.

8. All records will require the Transportation Control Number (TCN) or Bill of Lading (BOL) shipment identification (ID) number to complete the link between IGC and Global Freight Management (GFM).

9. All records will require the following reference number information (in multiple loops) to identify TDS shipments.

a. Transportation Control Number (TCN) (if provided by shipper) or Bill of Lading (BOL). Provide this in the B1002 element.

b. Contract number. Provide this in the L1101 element in an L11 segment with a CT qualifier in the L1102 element.

c. Carrier SCAC. Provide this in the B1003 element.

d. Billed shipment weight. Provide this in the AT803 element with a “B” qualifier in the AT801. Also provide the unit of measure in the AT802 (L for pounds, K for Kilograms).

10. The following are the minimum events to be sent for each shipment (AT701 of the 214A EDI message):

AF - Carrier Departed Pick-up Location with Shipment (mandatory) X4 – Arrived at Terminal Location (if it occurs) P1 – Departed Terminal Location (if it occurs) K1 – Arrived at Customs (if it occurs) X1 – Arrived at delivery location (mandatory)

D1 – Completed Unloading At Delivery Location (mandatory)

11. The contractor shall accomplish status reporting within (4) four hours of an event, or the same amount of time provided to their commercial customers, whichever is sooner.