Study: Rewards of wireless technology for fleets worth startup hassles

user-gravatar

According to a new study, 65 percent of fleets that implement new wireless systems find that integrating the technology with existing and back-office systems is the biggest obstacle.

“The Use of Wireless & Mobile Technology in Fleet Operations,” a free report from eyefortransport, identifies the primary drivers for deploying wireless technology, and the major problems encountered when doing so.

While wireless technology is an established tool to help improve fleet productivity, efficiency and security, deploying a new mobile or wireless system or upgrading an existing application remains a huge undertaking. But according to the report, the hurdles are worth overcoming, since the return on investment is high, particularly in respect of tracking/tracing applications and improved driver communications.

The survey reveals that, although the industry has embraced wireless technologies for certain functions, there are still emerging applications, such as proof of delivery and mobile imaging, which have yet to achieve widespread adoption. And almost two-thirds of the survey respondents felt that startup costs remain too high. However, while exactly half of the respondents had a problem convincing senior management of the merits of the technology, only a third had any difficulty in persuading their drivers. Also, 20 percent of fleet executives do not communicate at all with their drivers on the road.

More than 300 senior-level executives from trucking and delivery fleets responded to the survey, the results of which have been published and are available as a free download from www.eyefortransport.com/wirelesstruck06/report.shtml.

The decisive issues revealed by the survey will be examined in depth at the 4th eyefortransport Wireless & Mobile Technology for Trucking and Delivery Fleets conference, which takes place in Miami on Feb. 7-8, 2006. More details about the conference can be found at www.eyefortransport.com/wirelesstruck06/index.shtml.