Appendix_1.3_IGC_Data_Feed_Requirements.docx
DOCX document 23 KB Posted
- Attached to
- Global Heavyweight Service (GHS) Federal contract opportunity
- Solicitation number
- HTC711-18-R-C002
About this file
This document contains a presolicitation notice and performance work statement appendix for the Global Heavyweight Service contract opportunity. The United States Transportation Command is seeking to award multiple indefinite delivery, indefinite quantity contracts to provide international and domestic heavyweight door-to-door delivery services for the Department of Defense and cost reimbursable contractors. International shipments will weigh over 300 pounds to all locations including Alaska, Hawaii, and Puerto Rico, while domestic shipments will weigh over 150 pounds within the continental United States. Services will include pick-up, transportation, delivery, shipment tracking, customs clearance processing if applicable, and data reporting. The base period of performance is from February 1, 2019 through January 31, 2020 with two one-year option periods and a potential six-month extension. To receive an award, contractors must participate in the Civil Reserve Air Fleet program. The performance work statement appendix specifies requirements for electronic data interchange using ANSI X12 standards and details on events and data to be reported for each shipment.
Appendix 1.3 IGC Data Feed
View the file
Other files for this federal contract opportunity
Show all 44
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
HTC711-18-R-C002
PWS Appendix 1.3
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. 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 American National Standards Institute (ANSI) charters the Accredited Standards Committee (ASC) X12 to develop uniform standards for inter-industry electronic interchange of business transactions – electronic data interchange.
4. ASC X12 develops, maintains, interprets, publishes and promotes the proper use of American National and UN/EDIFACT International Electronic Data Integration (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. 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.
5. EDI status records are generated and populated from the ANSI ASC 214A transactions. Transactions are sent to the government value added network (VAN) where they are mapped and forwarded to government VAN data subscribers.
6. The government VAN is the Global Exchange Service (GEX). GEX is an EDI-based Business Transformation Agency (BTA) system which provides EDI messages to USTRANSCOM and other DOD agencies. GEX is administered by the Defense Logistics Agency (DLA).
7. To view the latest version of the DOD 214A Implementation Convention (IC), visit the DTEB website at https://www.ustranscom.mil/cmd/associated/dteb/ or download the current 214A IC at https://www.ustranscom.mil/cmd/associated/dteb/dod-transportation.cfm. For information on how to establish an interface with the GEX, contact DLA Transaction Services for set-up at edi@dla.mil or the Help Desk at (937) 656-3247. When calling the Help Desk please let them know that you are calling concerning EDI setup.
8. All records will require the Transportation Control Number (TCN) or Bill of Lading (BOL) shipment identification (ID) number to complete the link between EDI 214 data transactions and Global Freight Management (GFM).
9. All records will require the following reference number information (in multiple loops) to identify GHS shipments.
a. Transportation Control Number (TCN) or Bill of Lading (BOL). Provide this in the B1002 element. Reporting by the BOL applies that status to all of the TCNs on the shipment. Reporting by the TCN provides the status for only that TCN. If everything on the BOL is going to and from the same place, it is preferred to send by the BOL in the B1002.
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 GHS shipments are: HTC711-XX-XXXX
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).
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.
File details come from the government source that posted it. Updated .