Appendix 1.3 IGC Data Feed Requirements.pdf

HTC711-22-R-C001

PWS Appendix 1.3

1 October 2022

APPENDIX 1.3

GLOBAL HEAVYWEIGHT SERVICE (GHS) 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. 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.

3. 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. ASC X12 standards facilitate transactions by establishing a common, uniform business language for computers to communicate. With more than 275 transaction sets, ASC X12 standards can be used to electronically conduct nearly every facet of business-to-business operations.

4. 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.

5. Department of Defense (DoD) EDI transportation status records are generated and populated from the Defense Transportation Electronic Business (DTEB) and the 214A Motor Carrier Shipment Status is one of the many transactions that DTEB maintains.

6. DTEB 214A transactions are sent to the government value added network (VAN) where they are mapped and forwarded to government VAN data subscribers.

7. The government VAN 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 for set-up at edi@dla.mil and the DLA Help Desk (daashelp@dla.mil) or (614) 692-6672. When calling the Help Desk please select option 2 (ITOC Transaction Service Center) let them know that you are calling concerning DAAS EDI setup. Please include the contract number with the government when requesting a new setup.

8. To view the latest version of the Defense Transportation Electronic Business (DTEB) 214A IC, visit the DTEB website at https:// www.ustranscom.mil/cmd/associated/dteb/ or download the current DTEB 214A IC at https://www.ustranscom.mil/cmd/associated/dteb/dod-transportation.cfm.

HTC711-22-R-C001

PWS Appendix 1.3

1 October 2022

9. All records will require the following reference number information (in multiple loops) to identify GHS shipments. The prime contractor must ensure each record contains the following to complete the link between DTEB 214A transactions and Global Freight Management (GFM).

a. BOL. Provide this in the B1002 element. The BOL should be the only data present in

B1002. The BOL is provided by the shipper.

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

c. 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.

d. TCN. Provide this in the L1101 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.

e. Contract number. Provide this in the L1101 element in an L11 segment with a CT qualifier in the L1102 element. The identifier for all GHS shipments is: HTC711-

XX-X-XXXX.

f. 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)

g. Party Who Signed Delivery Receipt. Provide the last name of the person who signed for delivery receipt using the N102 element with a “N5” qualifier in the N101.

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

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)

Note: X4 and P1 represent an overnight stop at a secure intermediate location.

Normally, a fenced, guarded yard. This is not to be confused with a Pick-up or Delivery location.

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