Appendix 5.5 EDI 214 IGE Requirements - 12.29.11 .pdf

PDF 17 KB Posted

Attached to
Theater Express II Federal contract opportunity
Solicitation number
HTC711-12-R-C003
Issued by
Department of Defense United States Transportation Command

About this file

Appendix 5.5 to RFP Attachment 1

View the file

Other files for this federal contract opportunity

Show all 21

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-12-R-C003

Appendix 5.5

EDI-214 IDE Requirements

29 Dec 2011 Page 1

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 214 transactions. Transactions are sent to the government value added network where they are mapped and forwarded to Integrated Data Environment Global Transportation Network (IGC).

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 view the latest version of the DOD 214A Implementation Convention, visit the DTEB website at http://www.transcom.mil/dteb/ or download the current 214A IC at http://www.transcom.mil/dteb/files/transportationics/dt214a41.pdf. For information on how to establish an interface with GEX, contract the GEX at (614) 692-5344 or by email at cols-edi@csd.disa.mil Monday through Friday between 8am and 5pm Eastern Time; after hours, 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 following reference number information (in multiple loops) to identify CENTCOM Theater Express shipments. "Contract number. Provide this in the L1101 element in an L11 segment with a CT qualifier in the L1102 element. Example Contract Number: HTC711-11-D-WXXX. (Actual contract numbers will be provided to carriers after contract is awarded). "

a. Transportation Control Number (TCN). Provide this in the B1002.

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

c. The words “Shipper Ref” along with the Pallet ID. Provide this in the K101 element.

d. ID code qualifier of “10” – Optional Element. Provide this in the N103 element.

e. ID code (shipper DODAAC) – Optional Element. Provide this in the N104 element.

f. City Name (shipper city name). Provide this in the N401 element.

g. ID code qualifier of “10” – Optional Element. Provide this in the N103 element.

h. ID code (ship to DODAAC) – Optional Element. Provide this in the N104 element.

HTC711-12-R-C003

Appendix 5.5

EDI-214 IDE Requirements

29 Dec 2011 Page 2

i. City Name (ship to city name). Provide this in the N401 element.

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

10. The following status updates are required to be reported in AT701 of the 214A EDI message within (4) four hours of an event for each shipment:

a. OO – Bid/tender award received. Note: AMD email notification.

b. AF – Carrier departed pick-up location (original pickup location to your hub if not directly dropped off)

c. X1 – Arrived at delivery location (final destination)

d. D1 – Completed unload at delivery location

File details come from the government source that posted it. Updated .