Incorporate diagnostic tools to identify and verify problems in the transmission of video in a transit bus security system.

Experience from iFlorida Model Deployment

Orlando,Florida,United States

Background (Show)

Lesson Learned

The LYNX, the Central Florida Regional Transportation Authority, operates a public transportation system in Orlando. The FDOT viewed the LYNX Bus Security project, completed in 2005, as a technical proof of concept that would indicate the feasibility and cost of using a broadband wireless network to support transmission of surveillance video on mobile assets, such as a bus. One part of the iFlorida Model Deployment established network connectivity between the FDOT ITS network and the LYNX Command Center. This provided LYNX with network connectivity to roadside locations in many areas in which it operated buses. The LYNX Bus Security project took advantage of this connectivity by deploying a wireless network along a 14-mile stretch of I-4 between Orlando and the Disney World attractions. This wireless network bridged the gap between LYNX buses and this roadside network. Buses that used this portion of I-4 were then equipped with security cameras and wireless equipment for transmitting video from these cameras to FDOT and LYNX. Lessons learned include:
  • Incorporate diagnostic tools to identify and verify problems in the transmission of video in a transit bus security system. The deployment of the LYNX Bus Security System occurred with few surprises and was completed in the fall of 2005. RTMC operators reported receiving high-quality video images from buses while on the instrumented portion of I-4. However, they found it difficult to consistently verify that the system was operating correctly. Buses were on the instrumented portion of I-4 at regular but infrequent intervals. RTMC operators periodically checked the system to see if video was present as a method for gauging whether the system was working. Without knowledge of when the buses were present, the lack of video could be caused by either the system working incorrectly or the fact that no buses were present on the instrumented portion of I-4. As time went on, it became apparent that the system was not working reliably, and FDOT reported in May 2006 that the system had been out-of-service for several months. Also, the cost of the system was relatively high-about $640,000 for the initial deployment and for maintaining the system from its deployment date through May 2007. The result was a high-cost approach for providing network connectivity to a small number of buses.
  • Beware of rapid advances in video communications technologies while considering the deployment of a bus security system. The rapid advance of broadband communications technology has meant that this project, which was a cutting-edge application in 2003 when it was first considered, is no longer cutting-edge. A number of cities are now considering deploying broadband wireless networks on a much more extensive scale than that deployed in Orlando. Other approaches, such as cell modems, are being used to provide network connectivity to buses, and some of these approaches also provide sufficient bandwidth to support security video.
At the time the LYNX Bus Security System was deployed, few extensive broadband wireless networks had been deployed and it was not clear that a wireless network could successfully transmit video from a mobile vehicle. The system successfully demonstrated that such a network could be created and that it could be used to transmit real-time video from mobile vehicles. The FDOT also reported that the video transmission worked well, when the system was operational. However, the system was rarely operational, as reported in the project’s evaluation report, lacking the proper diagnostic and verification tools that would have enhanced the reliability of the system to attain the safety and security goals the system was meant to serve.

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.


iFlorida Model Deployment Final Evaluation Report

Author: Robert Haas (SAC); Mark Carter (SAIC); Eric Perry (SAIC); Jeff Trombly (SAIC); Elisabeth Bedsole (SAIC): Rich Margiotta (Cambridge Systematics)

Published By: United States Department of Transportation Federal Highway Administration 1200 New Jersey Avenue, SE Washington, DC 20590

Source Date: 01/30/2009

EDL Number: 14480

URL: https://rosap.ntl.bts.gov/view/dot/3977

Other Lessons From this Source

Lesson Contacts

Lesson Analyst:

Firoz Kabir


Average User Rating

0 ( ratings)

Rate this Lesson

(click stars to rate)

Lessons From This Source

Assess security risks, threats, vulnerabilities, and identify countermeasures to ensure operations of transportation management centers.

Be flexible to use data from various sources, such as the highway police patrol’s incident data, user feedback, and monitoring stations, to develop a statewide traveler information system.

Beware of challenges involved in developing an integrated statewide operations system for traffic monitoring, incident data capture, weather information, and traveler information—all seamlessly controlled by a central software system.

Beware of costs, utility, reliability, and maintenance issues in deploying a statewide transportation network monitoring system.

Beware of the limitations of using toll tags in order to calculate travel time on limited access roadways and arterials.

Beware that software development for ITS projects can be utterly complex, which demands avoiding pitfalls by following a rigorous systems engineering process.

Define a vision for software operations upfront and follow sound systems engineering practices for successfully deploying a complex software system.

Deploy a variable speed limit system only after the software systems required to support it are mature and reliable.

Design traffic video transmission systems around the constraints of bandwidth limitations and provide provisions for remote configuration of video compression hardware.

Develop an accurate, map-based fiber network inventory and engage ITS team in the construction approval process.

Develop an effective evacuation plan for special event that gathers a large audience and consider co-locating the responding agencies in a joint command center.

Ensure compatibility of data format of the field-weather monitoring sensors with the central software in the transportation management center.

Ensure that experienced staff oversee the development of a complex software system and thoroughly follow systems engineering process.

Ensure that Highway Patrol's CAD system operators enter key information needed by the transportation management center operators.

Establish a well defined process for monitoring and maintenance before expanding the base of field equipment.

Estimate life-cycle cost of ITS technologies as part of procurement estimates in order to assess the range of yearly maintenance costs.

In developing software for automated posting of messages on dynamic message signs, focus on the types of messages that are used often and changed frequently, and also include manual methods for posting.

Incorporate diagnostic tools to identify and verify problems in the transmission of video in a transit bus security system.

Perform adequate analyses and tests to design, calibrate and validate the capabilities of a bridge security monitoring system in order to reduce false alarms.

To support statewide traveler information services, design and implement reliable interface software processes to capture incident data from the local and highway patrol police’s computer aided dispatch systems.

Use simple menu choices for 511 traveler information and realize that the majority of callers are seeking en route information while already encountering congestion.

Lesson ID: 2010-00519