Lesson

Use the FRATIS system to enable automated communications between multiple stakeholders and improve logistics in the event of traffic delays or changes to wait times at drayage facilities.

Experience from the Los Angeles-Gateway Freight Advanced Traveler Information System (FRATIS) project.


02/02/2015
Los Angeles; California; United States


Background (Show)

Lesson Learned

The lessons below were derived from the LA-Gateway FRATIS project:

Use the FRATIS system to enable automated communications between multiple stakeholders and improve logistics in the event of traffic delays or changes to drayage facility wait times. Prior to the deployment of the FRATIS system, PLG staff could check the status of containers on Web sites and make calls to see which containers have been made available and ready for pick up at a terminal. However, this approach placed additional burden on the back office staff and did not provide real-time updates in the event of changes to status, traffic, wait times, etc. This issue highlights the need for automated, real-time communication not just within individual stakeholder organizations but throughout the entire transportation network.

Integrate the FRATIS system with existing drayage operator order management systems to reduce operator work loads. During the system implementation with PLG, a key challenge was the need for the office operations staff to enter orders into both the FRATIS system as well as TMW, their order management system. This not only doubled the work load on the office staff, but also led to an increase in order entry errors. In order to fully resolve this issue, integration between the FRATIS system and the drayage company’s order management system would provide the best-fit solution. It would be possible in future efforts to utilize web services to fully automate the process and ensure that all relevant order data is exported to FRATIS from the order management system.

Implement effective and targeted user training and retraining during test periods. During the course of the pilot program, the team encountered some initial resistance to technology adoption amongst the participating dispatchers and drivers. Anecdotal evidence showed that drivers who received up front training and used the system for a few days at the beginning were most likely to keep using it in the long term, as it reduced the learning curve and allowed the drivers to realize the benefits of the system, particularly the real-time traffic information and the dynamic routing. Expanded deployments should build on this lesson and provide dispatchers and drivers with more interactive training materials and increased "on-demand" support materials to address questions/concerns.

Gain clear buy-in from the most influential stakeholders at the outset of a deployment (marine terminal operators, large beneficial cargo operators, large drayage operators) to maximize the benefits of a FRATIS deployment. Identifying test user groups that see the value in innovation, are invested in improving the operating environment are critical to the success not just of future FRATIS deployments but of any pilot programs relying on increased connectivity and communication. Some stakeholders were resistant to participate fully or change their business rules even it would ultimately provide a more efficient and effective operating environment. This demonstrated the need for gaining clear buy-in from the most influential stakeholders at the outset of a deployment (marine terminal operators, large beneficial cargo operators, large drayage operators).

Future generations of FRATIS should have a flexible software approach that can be easily integrated into dispatcher operations and should be designed with an architecture that is hardware independent. FRATIS should focus on flexible software and integration approaches and utilize web services, API connectivity and mobile applications. Such systems should also be designed with an architecture that is hardware independent (and not tied to specific vendor systems such as TomTom). For example, if FRATIS is to be expanded in the LA-Gateway region, system deployers cannot afford to tailor a back office software integration with each and every trucking company, and also must be able to integrate with whatever in-vehicle communications platform that the company uses—even cell phones, if that is how the company communicates with drivers.


Lesson Comments

No comments posted to date

Comment on this Lesson

To comment on this lesson, fill in the information below and click on submit. An asterisk (*) indicates a required field. Your name and email address, if provided, will not be posted, but are to contact you, if needed to clarify your comments.



Source

Los Angeles-Gateway Freight Advanced Traveler Information System Demonstration Team Final Report

Author: Jensen, Mark (Cambridge Systematics); Sam Fayez (Productivity Apex); and Susan DeSantis

Published By: USDOT Federal Highway Administration

Source Date: 02/02/2015

Other Reference Number: FHWA-JPO-14-197

URL: http://ntl.bts.gov/lib/54000/54800/54838/FHWA-JPO-14-197_la_dtfr.pdf

Lesson Contacts

No contact information available


Rating

Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)


Lesson ID: 2016-00736