Use Electronic Freight Management (EFM) system as a supplement to existing systems and design the EFM system flexible enough to accept and provide data about any partner within the supply chain.
Columbus, Ohio's experience in the electronic freight management system deployment test.
Following are the lessons learned that were derived from the evaluation of CEFM system usefulness:
- Use EFM system as a supplement to existing systems, not a separate or replacement transportation management system. Users seemed to want transportation management system (TMS) capabilities from EFM, but by design, EFM is a data exchange system and not a TMS. Therefore, EFM is not as flexible in its analytical capabilities as one would find in a typical TMS. Except where EFM was integrated into an existing system, this mismatch in expectation limits perceived usefulness, but this is another reason why it is so important for EFM-type capabilities to be integrated with existing systems. Also, integrating EFM system capabilities into an existing system would reduce data entry and increase data quality. For future implementations, it is important for users to understand that EFM is a supplement to existing system, not a separate or replacement transportation management system.
- Make flexibility a design goal for the system. For the system to be truly effective and usable by the supply chain partners, it needs to be flexible enough to accept and provide data about any partner that may be involved in the supply chain.
- Design the Open Consignment Report (OCR) function properly to reduce the processing time for the OCR. The OCR function should be designed such that the Web Service would access only the database, which contained the most recent information, rather than polling all information. The properly designed OCR function reduced the processing time for the OCR to an acceptable 1.5 minutes per OCR that remained more or less constant even as the shipment volume increased during the test. Also the record from the test showed that the time involved in creating the OCR was not affected by the number of shipments included in the report.
- Implement a mechanism in EFM that can identify and correct or delete errors and illogical date. An important lesson learned is that future iterations of EFM software should have a means of identifying and correcting or deleting errors and illogical data. Future version of EFM/FIH needs to have logic that detects double flight arrivals or completely illogical dates for arrivals/departures, and flags such errors for users to investigate and correct as needed.
- Eliminate the numerical code and replace it with short status descriptions. CEFM used status, location, and similar codes for events, places, and characteristics that are related to Uniform Business Language (UBL). The deployment team noted that eliminating the numerical code and replacing it with short status descriptions would avoid the need for all parties to maintain a database of code translations. The Deployment Team also recommended the use of city name and state/providence abbreviation instead of a 3- or 4-character port code.
- Use precaution when using an open-source Software. While the open-source approach is the preferred approach to implement Web services in EFM, it needed precautions because many toolkits/add-ins are from different sources, and comparability and interoperability of different versions are a concern.
Author: K. Troup (North River), D. Newton (SAIC), M. Jensen (SAIC), C. Mitchell (SAIC), D. Stock (SAIC), M. Carter (SAIC), M. Wolfe (North River), and R. Schaefer (SAIC)
Published By: U.S. Department of Transportation, ITS Joint Program Office, Research and Innovative Technology Administration, 1200 Newe Jersey Ave. SE, Washington, D.C. 20590
See also, Public Roads Jan/Feb 2009 article by Randy Butler, http://www.tfhrc.gov/pubrds/ 09janfeb/06.htm "Electronic Freight Management"
Source Date: June 2008
EDL Number: 14442
Other Reference Number: DTFH61-02-C-00061URL: http://ntl.bts.gov/lib/31000/31500/31594/14442_files/14442.pdf
Average User Rating
Lesson of the Month for June, 2009 !