Mr. Jared Andrews, LMI, provided the group with an update on the fielding of a Concept of Operations (CONOPS) that LMI developed for OUSD (TP) in March 2008. The CONOPS detailed a method for integrating and automating the Report of Shipment (REPSHIP)1, transportation closure2, and Transportation Discrepancy Reporting (TDR)3 processes for AA&E shipments. Mr. Andrews reported that OUSD (TP) tasked LMI to develop the CONOPS because DoD shippers and receivers sometimes fail to execute these critical processes because they are manually intensive (e.g. faxes, phone calls, emails).
Mr. Andrews reported that the CONOPS relied heavily on the use of Electronic Data Interchange (EDI) messages and their ability to allow disparate information systems to communicate with each other. The CONOPS requires all DoD automated shipper systems to implement a standard Advance Ship Notice (ASN), specifically the X12 EDI 856A ASN. Prior to the actual movement, the shipper system will generate the 856A ASN and send it to the receiver, USTRANSCOM’s Global Transportation Network (GTN), and SDDC’s Intelligent Road/Rail Information System (IRRIS). After the shipment arrives at the receiving activity and is “in-checked” the receiving activity’s automated shipper system will generate an X12 EDI 315N Nodal Status message and send it to both GTN and IRRIS. After GTN and IRRIS receive the 315N Nodal Status message the shipment will be “closed out”.
Mr. Andrews noted that USTRANSCOM’s Corporate Data Office (CDO) issued an email on May 16, 2008 directing all DoD shipper systems to implement a capability for generating the 856A and 315N messages. The email directed the managers for each shipper system to provide estimated dates of when they can complete implementation using external funding, if it becomes available, and using internal funding. Mr. Andrews noted that some shipper systems, such as Air Force’s Cargo Movement Operations System (CMOS), have already begun implementing the EDI messages but some have not (e.g. JMC’s Munitions Transportation Management System).
The CONOPS also relied heavily on the use of EDI messages to support the TDR process. SDDC currently owns the TDR process and has developed a web based system that allows shippers and receivers to file the TDRs electronically. The system is called the Discrepancy Identification System (DIS). Mr. Andrews noted that the CONOPS recommended that the shipper systems be enhanced to allow shipment data to be exported electronically into DIS. This would reduce the time it takes to file TDRs because the shipment information would be pre-lodged in DIS. Mr. Andrews noted that SDDC has agreed to modify DIS to accept the electronic
1 A REPSHIP is an Advance Ship Notice (ASN) that is generated by the shipper and sent to the receiver to let them know a sensitive shipment is inbound to their facility.
2 Transportation closure is the process whereby a receiver reports back to the shipper and/or an oversight and monitoring agency, such as DTTS, that they received the sensitive shipment.
3 A Transportation Discrepancy Report (TDR) is generated by the receiving activity when the quantity received does not match what was reported to have been shipped. Receivers also file TDRs when shipments arrive damaged.
AA&E Interagency Coordination Group Minutes – June 3, 200810