2022.03.11 NGDS2 - Appendix 6.8, IGC Data Feed Requirements_Amd 0001.pdf

HTC711-22-R-C003

PWS Appendix 6.8

1 October 2022

Appendix 6.8 NGDS-2 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. The Accredited Standards Committee (ASC) X12 is a standards organization. Chartered by the American

National Standards Institute in 1979, it develops and maintains the X12 EDI along with XML schemas which drive business processes globally.

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 Convergence (IGC) (formerly Global Transportation Network (GTN).

6. All EDI 214A transactions shall be submitted to the government Value-Added Networks (VANS), which is the Global Exchange Service (GEX). GEX is an EDI-based system which provides EDI messages to United States Transportation Command (USTRANSCOM) and other DOD agencies. GEX is administered by the Defense Logistics Agency (DLA) Defense Automatic Addressing System (DAAS). For information on how to establish an interface with the GEX, contact DLA DAAS at agreements@dla.mil. For assistance with established accounts contact DAAS GEX at edi@dla.mil and include your agreement number or account name for identification and research. You can also contact the DISA Global Service Desk at (844) 347-2457.

7. To view the latest version of the DOD 214A, Implementation Convention, visit the Defense Transportation

Electronic Business (DTEB) website at https://www.ustranscom.mil/cmd/associated/dteb/. For information on how to establish an interface with the GEX, contact the DLA DAAS at agreement@dla.mil. For assistance with established accounts contact DAAS GEX at edi@dla.mil and include your agreement number or account name for identification and research. You can also contact the DISA Global Service Desk at (844) 347-2457.

8. All records will require the Transportation Control Number (TCN) and/or Carrier tracking data (Air Waybill) number to complete the link between IGC and Global Freight Management (GFM).

9. All records require the following information (in multiple loops) to identify NGDS shipments.

mailto:edi@dla.mil https://www.ustranscom.mil/cmd/associated/dteb/ mailto:agreement@dla.mil mailto:edi@dla.mil

a. TCN. Provide this in the L1101 B1002 element in an L11 segment with a TG qualifier in the L1102 element. The TCN is a 17- character number provided by the shipper on the BOL. The maximum count for TCNs on a single DTEB 214A is 299. When TCN cannot be provided by the shipper activity, the B1002 will contain "NONE" to indicate non-availability.

b. Contract number. Provide this in the L1101 element in an L11 segment with a CT qualifier in the L1102 element. The identifier for all NGDS shipments is: HTC711-XX-X-XXXX. (critical)

c. Standard Carrier Alpha Code (SCAC). Provide this in the B1003 element. (critical)

d. Billed package/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). (critical)

e. Carrier tracking data. Provide tracking data in the B1006 element with an Air Waybill (AW) qualifier in B1005. Motor carriers may report a PRO Number in the B1001. Either a B1001 or B1005/06 are used in the DTEB 214A, but not both. (critical)

f. Party who signed delivery receipt. When generating the D1 event, provide the last name of the person who signed for delivery receipt using the N102 element with a “N5” qualifier in the N101. (critical)

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

AF – Carrier Departed Pick-up Location with Package/Shipment (mandatory, critical) AG – Estimated Delivery (mandatory, critical) X4 – Arrived at Terminal Location (if it occurs) P1 – Departed Terminal Location (if it occurs) K1 – Arrived at Customs (if it occurs) CT – Customs Release (if it occurs) X1 – Arrived at Delivery Location (mandatory, critical) AH – Attempted Delivery (if it occurs) D1 – Completed Unloading at Delivery Location (mandatory, critical)

Figure 10.1

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.