Please share any documentation that you may have regarding benefits and costs of ITS.
Contribute now!
View Selected
Be prepared to face the opportunities and challenges posed by political timetables, project deadlines, as well as pricing-equity issues for road pricing procurement and implementation.(12/01/2010)Experience from road pricing programs in Europe and Asia
Do not expect to see significant operations staff reductions due to implementing ITS technologies, but do expect service improvements using the same staff levels.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
For a comprehensive transit ITS deployment program, select an agency project manager with skills in planning, information technology, and communications.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
Understand that the contractor’s availability to remain on site after the deployment of a comprehensive transit ITS is important, so is the contractor’s ability to work with the original equipment manufacturer.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
Designate the agency project manager as the single point of contact with the contractor and evaluate track record of contractor’s project management.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
Ensure proper sequencing of ITS deployments with careful consideration to dependencies among projects and utilize a data warehouse to lessen complexity in ITS integration.(November 2009)Chattanooga Area Regional Transportation Authority's experience in deploying transit ITS
Consider using virtual servers and ensure that all applications use a single database engine in order to reduce time and human capital required to maintain the additional IT infrastructure warranted for ITS.(November 2009)Chattanooga Area Regional Transportation Authority's experience in deploying transit ITS
Proactively establish working relationships with all partner stakeholder groups. (October, 2008)A Utah Department of Transportation Experience from the expansion of the CommuterLink intelligent transportation system.
Anticipate project delays and allocate sufficient time and funding to address key project variables.(1 August 2007)Experience from the smart parking field test at the Rockridge, Oakland BART station.
When considering the use of camera phones in managing incidents, be aware of the challenges associated with technology interoperability among agencies and first responder priorities.(April 2007)Washington, D.C., metro area's experience with using camera phones
Recognize that deployment delays can lead to a ripple effect of challenges that affect project deployment progress.( 2 March 2007)Great Lakes ITS project management experience with deployment delays associated with the Airport ITS Integration Project.
Develop a project champion succession plan within participating organizations to avoid orphaning a project.( 2 March 2007)The Great Lakes ITS project management experience from a change in political leadership.
Coordinate extensively with agency staff and vendors when integrating a Transportation Management Center with Computer Aided Dispatch Systems.(July 2006)Utah's experience with integrating a Transportation Management Center with Computer Aided Dispatch systems.
Divide large-scale ITS projects into smaller, individual task orders to enhance project management capabilities.(June 2006)A Colorado DOT experience in deploying the I-70 ITS Integration project
Anticipate, understand, address and manage the risks associated with fare card technologies and the vendor relationship.(4/14/2006)Experience of seven partner public transportation agencies in the Central Puget Sound region of Washington in setting up a regional fare card program.
Understand the issues, strategies and trade-offs that motivate agencies to join in a regional partnership and provide appropriate support.(4/14/2006)Experience of seven partner public transportation agencies in the Central Puget Sound region of Washington in setting up a regional fare card program.
Plan for greater time and project complexity than expected.(4/14/2006)Experience of seven partner public transportation agencies in the Central Puget Sound region of Washington in setting up a regional fare card program.
Consider a consensus organizational model to help assure support and participation of partners in a regional fare card project.(4/14/2006)Experience of seven partner public transportation agencies in the Central Puget Sound region of Washington in setting up a regional fare card program.
Examine the contextual factors and carefully manage the associated issues that will determine the success or failure of a regional fare card project.(4/14/2006)Experience of seven partner public transportation agencies in the Central Puget Sound region of Washington in setting up a regional fare card program.
Consider the value of implementing a limited fare pass system initially to serve as an interim experience base for a comprehensive region-wide electronic fare card system.(4/14/2006)Experience of seven partner public transportation agencies in the Central Puget Sound region of Washington in setting up a regional fare card program.
Conduct systems engineering process improvement reviews in order to identify, prioritize, and refine systems engineering processes.(4/1/2006)Florida DOT's experience in performing systems engineering process improvement reviews.
Recognize staffing and communication needs for Advanced Traveler Information Systems (ATIS) projects.(April 2006)Experience from the Pennsylvania Turnpike Commission.
Use a flexible approach and accepted techniques for project management.(12/2/2005)Maryland, New York, and Connecticut's experience with electronic toll collection and electronic screening.
Develop a Concept of Operations (ConOps) to help project partners stay focused on the true needs of an ITS deployment.(11/1/2005)The City of Lincoln, Nebraska’s experience in using systems engineering practices to define needs for an Automated Vehicle Location (AVL) project.
Define a process within your organization for the consistent application of systems engineering methods(3/1/2005)Florida DOT’s experience in adopting a systems engineering process.
Foster efficiency and joint commitment by promoting an open and cooperative relationship among all parties involved in the project.(January 2005)Virginia DOT’s experience integrating data from public works and public safety agencies.
Establish a clear leader and command structure when working on a major, interagency project. (1/1/2005)Boston, Massachusetts’s experience with transportation planning for special events.
Anticipate last minute technical glitches when integrating computer aided dispatch (CAD) and transportation management center (TMC) systems and plan accordingly from the start of the project.(January 2005)Virginia DOT’s experience integrating data from public works and public safety agencies.
Anticipate the need for additional training during the initial post-deployment period to help ensure that system operators are familiar with all new features and procedures.(January 2005)Virginia DOT’s experience integrating data from public works and public safety agencies.
Take advantage of special events opportunities to inspire interagency cooperation and deployment of advanced transportation management technologies.(1/1/2005)Boston, Massachusetts' experience with transportation planning for special events.
Keep the public informed with current accurate information to promote knowledgeable travel decisions. (1/1/2005)Boston, Massachusetts’s experience with transportation planning for special events.
Develop early deployment and rapid prototyping strategies to improve the project development process.(January 2005)Virginia DOT’s experience integrating data from public works and public safety agencies.
Plan sufficient time for facilitating and accommodating interagency relationship-building for major events. (1/1/2005)Boston, Massachusetts’s experience with transportation planning for special events.
Maintain owner control and consistent oversight when using a System Integrator for project implementation to keep project on time and on budget.(12/29/2004)A Colorado DOT experience in deploying a large multi-jurisdictional ITS project
Consider dividing a large ITS project into manageable task orders.(12/29/2004)A Colorado DOT experience in deploying a large multi-jurisdictional ITS project
Apply systems engineering principles for improved project management.(12/29/2004)A Colorado DOT experience in deploying a large multi-jurisdictional ITS project
Ensure active oversight by knowledgeable state government staff of any complex ITS integration work that involves multiple contractors working simultaneously.(9/1/2004)A State of Connecticut experience with deployment of CVISN.
Minimize technical issues encountered with integrating ITS components by planning for issues and developing solutions prior to project implementation.(4/1/2004)TriMet’s experience with the deployment of Transit Tracker in Portland Oregon.
Recognize the value of other agencies' experiences when planning an ITS project.(4/1/2004)TriMet's experience with the deployment of Transit Tracker in Portland Oregon.
Recognize potential institutional issues when deploying an ITS system.(4/1/2004)TriMet’s experience with the deployment of Transit Tracker in Portland Oregon.
Coordinate extensively with other stakeholder agencies.(1/1/2004)New Mexico’s experience planning, deployment and operating a work zone traffic and incident management system.
Deliver a successful project by satisfying expectations of key stakeholders and managing resources efficiently.(2004)Washoe County, Nevada's experience with transit ITS implementation.
Ensure initial and ongoing success of ITS deployments by providing sufficient start-up time, maintaining flexibility, and performing maintenance needs in-house.(1/1/2004)New Mexico’s experience with planning, deployment and operating a work zone traffic and incident management system.
Establish an effective relationship between agency and vendor, and collaboratively focus on the success of the project.(2004)Washoe County, Nevada's experience with transit ITS implementation.
Build public awareness of large-scale construction projects and keep the public informed of work zone schedules to help minimize the associated travel impacts.(1/1/2004)New Mexico’s experience planning, deployment and operating a work zone traffic and incident management system.
Allocate adequate staff time for planning and management oversight to monitor progress and address issues.(12/30/2003)Montana Department of Transportation's experience in human resource and personnel management during implementation of the statewide 511 traveler information system.
Anticipate and plan for potential institutional barriers, especially in multi-agency deployments.(12/1/2003)Alaska DOT&PF’s experience integrating a common technology into its ITS and IT plans.
Adopt adequate and thorough procurement processes which cover purchases of both standardized commodity type equipment and highly complex integrated ITS components.(9/23/2003)Silicon Valley Smart Corridor’s experience with procuring equipment for the development of an integrated freeway, arterial and incident management system.
Execute thorough configuration management from the start of an ITS project to help prioritize implementation activities.(4/1/2003)A Utah experience in technical integration.
Create a strong System Manager role to focus accountability and clarify roles and responsibilities with multiple contractors.(4/1/2003)Utah DOT’s experience managing the development and deployment of arterial and freeway management systems.
Recognize that institutional and organizational issues will require considerable attention throughout the ITS project deployment process.(March 2003)Five rural transit agencies' experiences in applying ITS to rural transit.
Establish the fundamental technical nature of the ITS project, and be realistic about the participants' associated technical capabilities and limitations.(12/1/2002)A Washington State Department of Transportation implementation of a regional ATMS.
Structure software development ITS projects as a series of phased, smaller tasks with specific, incremental deliverables and associated acceptance testing.(12/1/2002)A Washington State Department of Transportation implementation of a regional ATMS.
Establish a strong acceptance testing program, with independent code reviews, for ITS projects with software product deliveries.(12/1/2002)A Washington State Department of Transportation implementation of a regional ATMS.
Establish a clear, specific vision of the products and functional objectives of the ITS project, and communicate that vision throughout the project.(12/1/2002)A Washington State Department of Transportation implementation of a regional ATMS.
Address critical issues early in the ITS work zone management system development and deployment processes, and allow sufficient start-up time.(November 2002)The experiences of four state DOTs using ITS in work zones.
Use a systems engineering approach for technical integration of ITS.(10/1/2002)Nationwide experience with ITS integration.
Recognize that rapid technological advances are taking place in the ITS industry when selecting specific ITS technologies.(7/1/2002)National experience selecting specific ITS technologies for regional and rural application.
Plan for ongoing logistical support, including the designation of a project champion.(4/1/2002)Virginia's experience implementing a pilot automatic vehicle location (AVL) system in an urban winter maintenance operations setting.
When deploying ITS for transit service, perform a technology assessment during the planning phase, gather technology operator input, and designate a project manager with adequate decision-making authority.(1/5/2002)Experience deploying ITS for transit service in a suburban area
Develop a database to better evaluate ITS application implementation.(1/1/2002)Nationwide experience with assisting transit system managers in deploying ITS.
Identify financial resources and expected costs to conduct a cost/benefit analysis.(1/1/2002)Nationwide experience with assisting transit system managers in deploying ITS.
Identify and then become familiar with available ITS technologies to be able to assess which ones are suitable and affordable for the organization. (1/1/2002)Nationwide experience with assisting transit system managers in deploying ITS.
Use a three level approach to identify the needs of the transit system: assess, analyze, and predict.(1/1/2002)Nationwide experience with assisting transit system managers in deploying ITS.
Coordinate across jurisdictions/regions and share resources to reduce future costs and delays.(5/1/2001)Major metropolitan areas' experiences with formalized incident management programs.
Establish the roles and responsibilities for overall management of the project at the onset, and alter the field operation test (FOT) process if needed.(January 2001)Irvine, California's experience in managing a field operational test of an integrated Advanced Transportation Management System.
Choose proven technology and avoid changes to specifications.(January 2001)Irvine, California's experience in implementing a field operational test of an integrated Advanced Transportation Management System.
Follow a modular approach when deploying complex projects in locations with a shortened construction season.(April 2000)Experience from the Integrated Corridor Traffic Management Project in Minnesota
Carefully select a project manager to be responsible for deployment and testing of new ITS technology.(3/1/1999)A Washington State Department of Transportation (WSDOT) experience with testing of new variable speed limit technology to reduce winter crashes on a mountain pass.
Define roles and responsibilities clearly in a public/private project to reduce delays.(10/19/1998)Institutional lessons from a test of a wide-area network to communicate traffic conditions in the Seattle area.
Make use of different approaches and techniques to manage software acquisitions.(July 1998)A national experience in acquiring software for ITS projects.
Develop a strong collaborative process for software acquisition.(July 1998)A national experience in acquiring software for ITS projects.
Recognize that the Smart InfraRed Inspection System has promise for increasing productivity of inspection personnel but not yet ready for national deployment due to lack of accuracy in flagging commercial vehicles with potential defects.(06/01/2011)Experience from a field operations test for commercial vehicle inspection enforcement.
Install message signs at strategic locations to provide commuters en route with real-time information of the parking availability status at a major transit station.(December 2010)Experience of Montgomery County Department of Transportation
Use business and functional requirements to guide technology selection for a road pricing program and understand that the technology selected initially evolves over time.(12/01/2010)Experience from road pricing programs in Europe and Asia
Provide at least the recommended minimum distance between a GPS antenna and a radio antenna on a transit vehicle.(December 2010)A rural ITS demonstration in Poinciana, Florida.
When developing transit signal priority (TSP) systems, consider using traffic simulation models as a cost-effective means of comparing the impacts of different TSP strategies on transit and non-transit vehicle travel time.(July 2010)Guidance emerging from a TSP literature review and from an evaluation of TSP in Burlington, Vermont.
Identify functional boundaries and needs for cross jurisdictional control required to implement adaptive signal control and transit signal priority systems.(30 June 2010)Smart Corridor experience in Atlanta, Georgia
Develop requirements using widely accepted standards, preferably the open source compatible ones if available, and review those requirements immediately before requesting proposals from contractors.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
To avoid project implementation delays and unanticipated costs, perform a thorough review of the existing technologies during the planning phase of a comprehensive transit ITS deployment.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
Commit to testing the new systems thoroughly, develop an acceptance matrix to document status of testing, and perform verification and validation before introducing them to support agency’s transportation operations.(November 2009)Chattanooga Area Regional Transportation Authority's experience in deploying transit ITS
Consider user acceptance of driver fatigue detection systems to be dependent on ease of use, ease of learning, perceived value, driver behavior, and advocacy. (6/2009)Nationwide experience with driver fatigue detection measures and technologies
Ensure that experienced staff oversee the development of a complex software system and thoroughly follow systems engineering process. (01/30/2009)Experience from iFlorida Model Deployment
Beware that software development for ITS projects can be utterly complex, which demands avoiding pitfalls by following a rigorous systems engineering process. (01/30/2009)Experience from iFlorida Model Deployment
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.(01/30/2009)Experience from iFlorida Model Deployment
Ensure compatibility of data format of the field-weather monitoring sensors with the central software in the transportation management center.(01/30/2009)Statewide systems implementation experience from iFlorida Model Deployment
Design traffic video transmission systems around the constraints of bandwidth limitations and provide provisions for remote configuration of video compression hardware.(01/30/2009)Statewide systems implementation experience from iFlorida Model Deployment
Deploy a variable speed limit system only after the software systems required to support it are mature and reliable. (01/30/2009)Experience from iFlorida Model Deployment
Define a vision for software operations upfront and follow sound systems engineering practices for successfully deploying a complex software system. (01/30/2009)Experience from iFlorida Model Deployment
Develop an accurate, map-based fiber network inventory and engage ITS team in the construction approval process.(01/30/2009)Experience from iFlorida Model Deployment
Deploy side object detection systems for transit buses that have proven effectiveness in transit operating environments and been accepted by transit operators.(December 15 2008)Experiences from the installation of Side Object Detection Systems on transit buses in Ohio, Utah and Washington, D.C.
Consider deploying ITS in a work zone to improve traffic safety and mobility during construction.(October 2008)Arkansas' experience using ITS in work zones.
Plan your system to accommodate future expansion.(October, 2008)A Utah Department of Transportation Experience from the expansion of the CommuterLink intelligent transportation system.
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.(June 2008)Columbus, Ohio's experience in the electronic freight management system deployment test.
Select measures of effectiveness (MOEs) that are measurable based on what is happening in the supply chain operations as well as in the deployment test. (June 2008)Columbus, Ohio's experience in the electronic freight management system deployment test.
Incorporate contractual provisions to conduct on-site traffic signal hardware and software demonstration testing and provide sufficient project oversight to ensure vendors meet agency requirements.(24 June 2008)Experience implementing an ATMS in Fort Collins, Colorado.
Be aware that integration of advanced transportation management systems, regardless of size, creates challenges throughout project deployment.(24 June 2008)Experience implementing an ATMS is Fort Collins, Colorado.
Implement smart parking systems at sites that experience high parking demand, are located close to a major freeway or arterial, and are configured to accommodate parking sensors at entrances and exits to promote accurate parking counts.(June 2008)Experience with smart parking in Oakland, California
Consider the long-term operations and maintenance responsibilities and costs when selecting project components. (9 May 2008)The Chicago, Illinois and Montgomery County, Maryland experience in operating and maintaining advanced parking information system.
Study the surrounding area for topographical encumbrances and radio interference when deploying wireless communication projects for traffic and parking management. (9 May 2008)The Chicago, Illinois experience in implementing advanced parking information systems to increase customer satisfaction and improve traffic operations.
Expect non-custom hardware and software to have technology limitations that may affect operational capabilities. (9 May 2008)The Chicago, Illinois and Montgomery County, Maryland experience in procuring and developing advanced parking information system hardware and software.
Ensure that new technology deployed in a weigh station to detect high-risk heavy trucks is in alignment with state organizational goals and inspection priorities.(31 January 2008)Evaluation of an Integrated Safety and Security Enforcement System (ISSES) in a weigh station on I-75 in Kentucky installed to detect high-risk heavy trucks
Plan for cellular communications to evolve and transition to new communication technologies every few years.(2008)A synthesis of transit agency experience with bus AVL systems
Consider and evaluate user needs when designing communication infrastructure.(1 August 2007)Experience from the smart parking field test at the Rockridge, Oakland BART station.
Keep technical solutions open-ended in the early stages of an ITS research project, and follow a research oriented contract vehicle.(May 16, 2007)Experience from the New York Advanced Traveler Information System (ATIS) Implementation and Integration Project
Examine route-specific opportunities and constraints, and assess corridor market potential for transit services prior to implementing BRT running way improvements.(2007)National experience developing BRT
Improve overall usefulness of a closed-circuit television (CCTV) camera by expanding the coverage, color-vision features, and operational availability of the camera. (August 2006)Monroe County, New York's experience in ITS camera deployment and system integration.
Anticipate ongoing modifications to transit communication systems when integrating a Transportation Management Center with Computer Aided Dispatch systems.(July 2006)Utah's experience with integrating a Transportation Management Center with Computer Aided Dispatch systems.
Prepare traveler information Web sites for high usage under emergency or disaster conditions.(6/1/2006)Experience from the nation's top traffic and transit information Web sites.
Focus on usability when designing traffic information Web sites.(6/1/2006)Experience from the nation's top traffic and transit information Web sites.
Assess what users want when developing a traffic information Web site.(6/1/2006)The experience of several of the nation’s top traffic and transit information Web site developers.
Integrate traveler information Web site development with existing systems and other organizations.(6/1/2006)The experience of several of the nation's top traffic and transit information Web site developers.
Collect high quality data with committed workers to help ensure reliable and consistent 511 services for tourism. (May 2006)Kentucky's experience offering tourism related services through its 511 Travel System.
Ensure users have easy access to 511 operators and tourism information.(May 2006)Kentucky's experience offering tourism related services through its 511 Travel System.
Be aware of technology and training issues when pioneering new transit technologies.(4/14/2006)Experience from the Lake Tahoe Coordinated Transit System.
Understand user and usability issues surrounding the development and deployment of kiosks and Interactive Voice Response (IVR) systems.(4/14/2006)Experience from the Lake Tahoe Coordinated Transit System.
Consider the implications of ITS transit technologies on operational efficiencies.(4/14/2006)Experience from the Lake Tahoe Coordinated Transit System.
Incorporate proven technologies and false alarm reduction strategies in the design of future Automotive Collision Avoidance Systems (ACAS).(April 2006)Experience from a Field Operational Test (FOT) in Michigan to evaluate an Automotive Rear-End Collision Avoidance System.
Assess needs and communication infrastructure capabilities for the design of an Advanced Traveler Information System (ATIS).(April 2006)Experience from the Pennsylvania Turnpike Commission.
Be aware of the challenges of disseminating travel information during disasters in rural areas.(28 March 2006)Experiences of a panel of experts in disaster information dissemination.
Closely coordinate the content and delivery of travel information messages to the public during disasters.(28 March 2006)Experiences of a panel of experts in disaster information dissemination.
Adequately plan for the ATIS operational needs for communicating with the public during disasters.(28 March 2006)Experiences of a panel of experts in disaster information dissemination.
Include driver age, time of day, and intersection characteristics in the design of red light violation algorithms and warning systems, and their field operational tests.(March 2006)Knowledge gained from an analysis of four years of red light violation data gathered from 11 signalized intersections in Sacramento, California
Integrate various types of road weather information to promote utilization by the public.(2/2/2006)An Idaho Transportation Department experience in Road-Weather Information System integration.
Conduct rigorous testing prior to deployment of an emergency preemption system to avoid potential problems and negative system impacts.(January 2006)The experience of multiple agencies with emergency vehicle preemption systems.
Apply process re-engineering techniques to increase the likelihood of successful ITS deployment.(12/2/2005)Maryland, New York, and Connecticut's experience with electronic toll collection and electronic screening.
Consider requirements definition and system design Issues for Archived Data Management Systems.(December 2005)Experience from six Archived Data Management Systems case studies.
Install an electronic transit card system to enhance rural transit agency performance and coordinate human service transportation between agencies to achieve more efficient services.(9/1/2005)New Mexico's experience with the implementation of Intelligent Coordinated Transit Smart Card Technology
Anticipate challenges in planning and deploying smart card technology in a rural environment.(9/1/2005)New Mexico's experience with the implementation of Intelligent Coordinated Transit Smart Card Technology.
Involve and collaborate with a broad range of users during software design, development, testing, and deployment to increase the return on investment.(7/29/2005)New Mexico Department of Transportation's experience in designing and deploying a web-based software application to simplify the increasing complexity of coordinating rural transit funding.
Make traveler information systems at tourist attractions more useful by targeting tourists in marketing and promotion efforts and orienting user interfaces to tourists.(7/1/2005)Experience nationwide with traveler information systems in tourism areas
Develop a user-oriented system for displaying travel time messages on dynamic messages signs. (May, 2005)Four American Cities' experiences with Travel Time Messaging on Dynamic Message Signs.
Treat system operators as the client and consider their perspectives during ATIS project development.(5/1/2005)Washington's experience in deploying five Advanced Traveler Information System (ATIS) projects and developing a standardized approach for evaluating ATIS projects.
Implement ATIS technology in a way that supports the maintenance staff.(5/1/2005)Washington's experience in deploying five Advanced Traveler Information System (ATIS) projects and developing a standardized approach for evaluating ATIS projects.
Consider that ATIS deployment in rural and/or remote areas presents special challenges.(5/1/2005)Washington's experience in deploying five Advanced Traveler Information System (ATIS) projects and developing a standardized approach for evaluating ATIS projects.
Beware of the likely trade-off between a decrease in the frequency of right-angle crashes and an increase in the frequency of rear-end crashes when considering installation of red-light-cameras.(April 2005)Experience from a national evaluation of red-light cameras
Use transit intelligent transportation systems (ITS) technologies in rural areas to save agency staff time and create a more user-friendly system.(2/1/2005)The experience of several states in the implementation of ITS to rural transit.
Balance project goals against the constraints and capabilities of project partners.(January 2005)Virginia DOT’s experience integrating data from public works and public safety agencies.
Develop a detailed cardholder recruitment plan in the planning phase of the project, to provide guidance on processes to set pricing, and to ensure high user involvement and loyalty.(8/1/2004)Orlando, Florida's experience with a Field Operational Test (FOT) on using a single smart card for transportation payments at facilities operated by multiple regional agencies.
Consider the appropriateness of different lane management strategies.(November, 2004)The experience of managed lanes projects in California, Texas and New Jersey.
Use dynamic lane merge systems to improve operations in long term construction zones.(October 2004)Michigan Department of Transportation's experience with a dynamic lane merge system (DLM)
Consider using real time traffic control system to overcome mobility and safety obstacles in a work zone.(October 2004)An Illinois Department of Transportation experience using ITS in work zones.
Assure success by involving all the relevant state agencies and the motor carrier industry early in the CVISN development process.(9/1/2004)A State of Connecticut experience with CVISN deployment.
Assure accurate late train arrival forecasts in support of a Connection Protection system.(5/12/2004)Experience of the Utah Transit Authority in implementing a Connection Protection program for rail-to-bus passenger transfers in Salt Lake City.
Incorporate real-time bus and train location information in the Connection Protection algorithm.(5/12/2004)Experience of the Utah Transit Authority in implementing a Connection Protection program for rail-to-bus passenger transfers in Salt Lake City.
Adjust bus schedules to assure adequate time to accomplish rail-to-bus connections, given the risk of late train arrivals at connecting stations.(5/12/2004)Experience of the Utah Transit Authority in implementing a Connection Protection program for rail-to-bus passenger transfers in Salt Lake City.
Ensure redundancy of critical components in transportation support systems to be used in case of an emergency.(May 2004)Experience nationwide with responding to catastrophic events
Use ITS to implement a reliable communications system in work zones.(1/1/2004)New Mexico’s experience in planning, deploying and operating a work zone traffic and incident management system.
Provide accurate and timely road condition and weather forecast information to rural travelers in cold weather regions.(12/30/2003)Montana Department of Transportation’s experience in designing and deploying the statewide 511 traveler information system.
Identify innovative solutions for deploying Information Stations that report real-time data for weather and traffic monitoring in the event of a hurricane.(11/1/2003)Experience from nine transportation management projects on hurricane evacuation preparedness.
Develop partnerships for a cost-effective approach to deploy remote traffic count stations that will provide real-time traffic data during a hurricane evacuation.(11/1/2003)Experience from nine transportation management projects on hurricane evacuation preparedness.
Monitor emerging security requirements and legislation that may impact commercial vehicle business processes.(10/1/2003)The IMTC ITS CVO – Border Crossing Deployment stakeholders experience with changes in security policies in Washington State and British Columbia.
Protect data privacy by implementing user authorization levels for sensitive information.(10/1/2003)The Washington State and British Columbia experience in developing a fully operational and bi-national electronic commercial vehicle operations (CVO) border crossing system.
Use an interoperable transponder to assure maximum benefits to both the private and public sector.(10/1/2003)The Washington State and British Columbia experience in using transponders as part of the IMTC ITS CVO – Border Crossing Deployment.
Ensure that ITS field operations tests use technologies and applications that are proven to be deployment ready.(26 September 2003)Experience with a Field Operational Test for the Intelligent Vehicle Initiative in Minnesota
Design the 511 system to handle the surge in call volume during major events.(9/3/2003)A national experience with the development and deployment of 511 Systems.
Perform before-research to determine what customers want from 511 services and continue to evaluate the system after implementation.(9/3/2003)A national experience with the development and deployment of 511 Systems.
Make sure 511 Systems are customer and market driven to help ensure they are utilized by travelers.(9/3/2003)A national experience with the development and deployment of 511 Systems.
Understand that deployment costs of 511 systems will vary based on system capabilities and anticipate the challenges of identifying these costs early in the process.(9/3/2003)A national experience with the development and deployment of 511 Systems.
Recognize that interoperability is becoming an important issue in achieving the vision of a nationwide 511 system.(9/3/2003)A national experience with the development and deployment of 511 Systems.
Implement infrastructure-based collision avoidance technology to mitigate risks at crash prone intersections.(September 2003)A research project based on literature reviews and working with Virginia, California, and Minnesota.
Maximize Field Operational Test (FOT) success by creating a sound experimental design and data acquisition plan.(September 2003)Experience from a Field Operational Test (FOT) in Michigan to evaluate a Roll Advisor and Control (RA&C) system for commercial vehicles.
Standardize the system environment.(4/1/2003)Utah DOT’s experience using configuration management.
Consider potential system enhancements to meet heavy demand.(4/1/2003)Utah DOT’s experience managing the development and deployment of arterial and freeway management systems
Define your agency's expectations of a new system and a robust set of system requirements and then choose the software that meets your requirements.(4/1/2003)Utah DOT's experience using configuration management.
Involve agency staff in the software development process by co-locating them with the development team.(4/1/2003)Utah DOT’s experience using configuration management.
Consider various technical applications and processes, such as using GIS, evaluating systems compatibility and the facility for upgrades, when deploying ITS.(March 2003)Five rural transit agencies' experiences in applying ITS to rural transit.
Adequately invest and plan for the deployment of an Advanced Public Transportation System (APTS).(January 2003)Experience from the Cape Cod Advanced Public Transit System.
Recognize the data requirements of an Advanced Public Transportation System (APTS).(January 2003)Experience from the Cape Cod Advanced Public Transit System.
Develop a long term vision for an Advanced Public Transportation System (APTS).(January 2003)Experience from the Cape Cod Advanced Public Transit System.
Expect that new technology will require modifications before it is useable.(12/1/2002)A Washington State experience with testing of electronic container door seals (E-seal) through a freight supply chain.
Design the system to withstand the demands of the physical environment in which it will be deployed.(4/1/2002)Virginia's experience implementing a pilot automatic vehicle location (AVL) system in an urban winter maintenance operations setting.
Design and tailor system technology to deliver information of useful quality and quantity, that the user can reasonably absorb.(4/1/2002)Virginia's experience implementing a pilot automatic vehicle location (AVL) system in an urban winter maintenance operations setting
Implement 511 using the Guidelines issued by the 511 Deployment Coalition.(April 2002)The Florida Department of Transportation's experience with implementing a regional ATIS program in the Miami tri-county region
Be sure to identify and take into account features unique to each state when designing and deploying ITS technology projects across multiple states.(3/29/2002)Experience from technical integration of commercial vehicle safety and fitness data in the eastern United States.
Plan for system redundancies to ensure appropriate incident response activities and continuity of operations during emergency situations.(March 2002)The National Capital Region's experiences in emergency response after September 11, 2001.
Use speed warning signs on dangerous curves to reduce speeds of trucks.(November 2001)Colorado DOT utilizes low cost system to reduce truck speeds on mountain passes.
Use non-proprietary software for ITS projects to ensure compatibility with other ITS components(2001)Experience with the ITS integration effort in the Metropolitan Model Deployment Initiative (MMDI)
Identify methods to distribute automated vehicle identification tags to improve market penetration when collecting arterial travel speed information.(October 2000)San Antonio's experience with automated vehicle identification tags.
Consider key elements of procurement and contracting when outsourcing telecommunications support services.(2000)Experiences from the Departments of Transportation (DOTS) of multiple states in selecting telecommunications options.
Consider the strengths and weaknesses of distributed versus centralized ITS telecommunications systems.(2000)Experiences from the Departments of Transportation (DOTS) of multiple states in selecting telecommunications options.
Consider the financial and technical implications of a lease versus own decision for ITS telecommunications systems.(2000)Experiences from the Departments of Transportation (DOTS) of multiple states in selecting telecommunications options.
Consider the technology selected for an ITS telecommunications system carefully, as it will impact the cost and the performance of the system.(2000)Experiences from the Departments of Transportation (DOTS) of multiple states in selecting telecommunications options.
Conduct a Requirements Analysis to determine the most appropriate ITS telecommunications solution.(2000)Experiences from the Departments of Transportation (DOTS) of multiple states in selecting telecommunications options.
Consider procurement and contracting issues for leased versus owned ITS telecommunications systems.(2000)Experiences from the Departments of Transportation (DOTS) of multiple states in selecting telecommunications options.
Develop a regional ITS Architecture and a telecommunications ITS architecture as part of a needs assessment for developing the most appropriate telecommunications solution.(2000)Experiences from the Departments of Transportation (DOTS) of multiple states in selecting telecommunications options.
Consider the implications of choosing a Competetive Access Provider (CAP) for telecommunications services.(2000)Experiences from the Departments of Transportation (DOTS) of multiple states in selecting telecommunications options.
Select Transportation Management Center (TMC) design and location based on individual TMC needs and traffic realities.(10/1/1999)Eight states' experiences with design and location considerations for TMCs.
Anticipate challenges with the ITS technology being tested, including problems with software modification and adaptation of previously developed technology.(3/1/1999)A Washington State Department of Transportation’s experience with testing of new variable speed limit technology to reduce winter accidents on a mountain pass.
Select appropriate technologies to enable emergency notification and response systems to complement traditional 9-1-1 service.(9/1/1998)Colorado and Washington’s experience with emergency notification and response systems.
Do not build if you can buy existing software products.(July 1998)A national experience in acquiring software for ITS projects.
Provide consistent and high-quality information to influence traveler behavior.(6/1/1998)National experience with evaluating user response to freeway management systems.
Consider cost-saving strategies and long term needs when making communications investments.(6/1/1998)National experience with making communications investments for incident management.
Design a trip planning website to capture and convey real-world factors such as gas prices and congestion information.(May 2011 )Evaluation of a Multimodal Trip Planning System (MMTPS) in Northeastern Illinois
Employ sensors that can account for a range of parking lot vehicle movements.(1 August 2007)Experience from the smart parking field test at the Rockridge, Oakland BART station.
Ensure electronic toll collection systems are interoperable with neighboring toll facilities.(September, 2006)The Washington State Department of Transportation’s experience with planning for tolling implementation.
Establish a centralized database for all winter maintenance-related weather information.(2/2/2006)An Idaho Transportation Department experience in Road-Weather Information System integration.
Treat maintenance staff as the client and encourage their participation in the ATIS planning and deployment processes.(5/1/2005)Washington's experience in deploying five Advanced Traveler Information System (ATIS) projects and developing a standardized approach for evaluating ATIS projects.
Evaluate and upgrade TOC maintenance programs on an on-going basis. (January 2005)A New Jersey Department of Transportation experience with ITS operations and maintenance in Transportation Operations Centers (TOCs).
Include significant planning and development time in the overall project schedule to accommodate identifying and addressing the various compatibility issues, to integrate existing legacy system equipment across multiple agencies.(8/1/2004)Orlando, Florida's experience with a Field Operational Test (FOT) on using a single smart card for transportation payments at facilities operated by multiple regional agencies.
Implement compatible Electronic Toll Collection systems in every state.(October, 2004)A retrospective of what's been learned since the first ITS Strategic Plan developed in 1992.
Implement a commercial vehicle e-credentialing program in order to make administration and roadside inspections more efficient, keep vehicles moving on the state's roads, and expedite registration.(9/1/2004)Washington State’s experience with deploying Commercial Vehicle Information Systems and Networks (CVISN) Electronic Credentialing.
Consider the risk that draft ITS standards will not remain stable through further development when deciding whether to use them in an ITS deployment.(10/1/2001)Hampton Roads, Virginia's experience with immature data-exchange standards for its Advanced Traveler Information System
Use ITS Standards to achieve interchangeability and interoperability for Dynamic Message Signs.(Spring 2001)Experience of nine agencies using Dynamic Message Signs built to NTCIP specifications.
Use public sector workshops to increase awareness of ITS standards.(5/1/2000)Minnesota DOT’s experiences with a public sector workshop on ITS standards.
Understand system standards and protocols to save time during the development of an Advanced Traveler Information System (ATIS).(10/19/1998)Institutional lessons from a test of a wide-area network to communicate traffic conditions in the Seattle area.
Pursue technology based, high risk policies incrementally to better manage likely organizational and technological challenges.(August 2011)San Francisco Municipal Transportation Agency's experience in implementing advanced parking management (Interim Results).
Be sure to conduct a detailed evaluation prior to installing an Adaptive Traffic Control System (ATCS), and be aware that conducting a public education campaign on ATCS risks building expectations too high.(2010)Experience acquired from multiple agencies in the United States and Canada.
Prepare agency staff for implementation of new ITS technologies and involve maintenance and information technology (IT) staff in the installation process.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
Weigh in the advantages of procuring new information technology (IT) assets, and maintain an asset management system that details new IT inventory.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
In deploying a comprehensive transit ITS program, develop strategies and requirements for planning, procurement, implementation, and ongoing operations.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
Define clear goals for a comprehensive transit ITS deployment program and track the achievement of those goals to evaluate program's success.(May 2010)Washoe County’s experience implementing a comprehensive transit ITS program.
Develop a long-term ITS vision and use systems engineering processes to successfully manage ITS deployments.(November 2009)Chattanooga Area Regional Transportation Authority's experience in deploying transit ITS
Consider developing a data warehouse early on to simplify the integration of subsequent ITS deployments and to efficiently manage operations of interdependent applications.(November 2009)Chattanooga Area Regional Transportation Authority's experience in deploying transit ITS
Tailor the standard systems engineering process model to suit an agency’s ITS deployment scale and needs.(November 2009)Chattanooga Area Regional Transportation Authority's experience in deploying transit ITS
Reach out to a broad range of stakeholders and deploy early the projects that demonstrate easy-to-see benefits to build momentum for agency’s ITS program.(November 2009)Chattanooga Area Regional Transportation Authority's experience in deploying transit ITS
Perform adequate analyses and tests to design, calibrate and validate the capabilities of a bridge security monitoring system in order to reduce false alarms.(01/30/2009)Experience from iFlorida Model Deployment
Beware of the limitations of using toll tags in order to calculate travel time on limited access roadways and arterials. (01/30/2009)Experience from iFlorida Model Deployment
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. (01/30/2009)Statewide systems implementation experience from iFlorida Model Deployment
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.(01/30/2009)Experience from iFlorida Model Deployment
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.(01/30/2009)Statewide systems implementation experience from iFlorida Model Deployment
Use simple menu choices for 511 traveler information and realize that the majority of callers are seeking en route information while already encountering congestion.(01/30/2009)Experience from iFlorida Model Deployment
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.(01/30/2009)Statewide systems implementation experience from iFlorida Model Deployment
When implementing traveler information systems that promote voluntary changes in travel behavior, incorporate functions for feedback, advice, and action-planning.(16-20 November 2008.)Experience with Mobility Management in Japan.
Maintain ownership of the work zone ITS system and monitor vendor's work diligently to assure proper system operation.(October 2008)North Carolina's experience implementing ITS solutions in work zones.
Coordinate the schedules for ITS deployment and roadway construction to maximize use and benefits of the system.(October 2008)North Carolina's experience implementing ITS solutions in work zones.
Beware that modeling may not be a suitable substitute for before-after studies of ITS integration projects.(14 May 2008)Experience from Minnesota's Traveler Information Guidance and Emergency Routing (TIGER) Project.
Plan for logistical and operational issues prior to project implementation.(December 2007)Wisconsin Department of Transportation’s experience implementing ITS support equipment and technologies.
Consider the impact fees have on parking behavior.(1 August 2007)Experience from the smart parking field test at the Rockridge, Oakland BART station.
Consider dynamic natural conditions and surrounding landscapes when selecting technologies for animal detection system deployments.(August 2006)Montana and Pennsylvania’s experience with deploying animal detection systems.
Recognize issues in deploying ITS technologies for coordinating and improving Human Services Transportation.(August 2006)Experiences from six agencies.
Anticipate and address challenges to consistently operating a transit signal priority (TSP) system.(4/14/2006)Experience from a cooperative project between Sacramento County and the Sacramento Regional Transit District in deploying a transit signal priority system.
Pursue a vigorous 511 marketing program, especially to promote new types of information targeted to specific user groups.(30 September 2005)An Arizona Department of Transportation experience in 511 implementation.
Expect to spend time and effort in testing and refining the voice recognition features of a 511 system.(30 September 2005)An Arizona Department of Transportation experience in 511 implementation.
Incorporate mechanisms for capturing user feedback for system evaluation, including the ability to intercept incoming 511 calls for survey or focus group recruitment.(30 September 2005)An Arizona Department of Transportation experience in 511 implementation.
Optimize travel time messaging operations by improving the way in which data is collected, analyzed, and displayed. (May, 2005)Four American Cities' experiences with Travel Time Messaging on Dynamic Message Signs.
Provide drivers with sufficient managed lane information that can be easily disseminated and understood. (2005)A guidance provided by the Texas Transportation Institute on providing user information in managed lanes facilities.
Consider changeable message sign (CMS) positioning, data archive requirements, and traffic demand when considering deployment of a dynamic late merge system.(28 December 2004)Experience of the Minnesota Department of Transportation in deploying a dynamic late merge system.
Seek assurances from your suppliers and sub-contractors, that their production and manufacturing schedules will meet your project schedule and inventory requirements throughout the lifecycle of the project.(8/1/2004)Orlando, Florida's experience with a Field Operational Test (FOT) on using a single smart card for transportation payments at facilities operated by multiple regional agencies.
Establish a clear understanding among all partners on the level of technical support to be provided by suppliers and integrators, as equipment provided in-kind or at a reduced cost is often provided with minimal technical support.(8/1/2004)Orlando, Florida's experience with a Field Operational Test (FOT) on using a single smart card for transportation payments at facilities operated by multiple regional agencies.
Maintain frequent and open communications with other states and the federal government when developing and deploying new, complex ITS technologies.(9/1/2004)A State of Washington experience with CVISN deployment.
Work with the trucking industry to assure success in deploying an electronic credentialing system for commercial vehicles.(9/1/2004)A State of Washington experience with CIVISN deployment.
Anticipate and plan for delays in deployment related to weather and the physical environment.(12/1/2003)Alaska DOT&PF’s experience integrating a common technology into ITS and IT plans.
Include sufficient safeguards to ensure the integrity of the fiber-optic communications infrastructure for ITS.(9/23/2003)Silicon Valley Smart Corridor's experience with safeguards and monitoring of integrated freeway, arterial and incident management systems and impact on deployment delays.
Realize that stakeholder policies, priorities, and personnel training are critical to ensure consistency and schedule adherence in deploying integrated systems.(9/23/2003)Silicon Valley Smart Corridor's stakeholder experience in the deployment of an integrated freeway, arterial and incident management systems and the impact on deployment delays.
Develop ways to raise awareness among businesses to promote advanced traveler information sources to their customers.(June 2003)An Acadia National Park experience in ITS deployment.
Develop a thorough installation and implementation process as part of the ITS deployment.(March 2003)Five rural transit agencies' experiences in applying ITS to rural transit.
Create a successful public-private agency partnership based on good communications, flexibility, and minimal impact to partners' customers to deploy new technology.(12/1/2002)A Washington State experience with testing of electronic container door seals through a freight supply chain.
Include certain components to make the Regional ITS Strategic Plan useful in implementation.(7/1/2002)National experience developing Regional ITS Strategic Plans to guide implementation.
Identify all transportation, incident management, and emergency response entities and strive to resolve issues with semantics and terminology among different agencies.(March 2002)The experiences in multi-agency coordination, emergency response, and transportation operations within the National Capital Region on September 11, 2001.
Make system maintenance response time and local presence a priority when selecting a systems integrator.(9/1/2001)Ventura County’s experience with an transit fare collection system integration.
Involve the private sector in the implementation of multiple advanced traveler information technologies.(30 May 2000)Institutional lessons from a partnership to implement emerging ITS technologies in the Seattle metropolitan area.
Allocate sufficient resources for technology deployment and operator training to improve incident detection and verification.(April 2000)Experience of transportation professionals nationwide in developing successful incident management programs.
Understand the market during the development of an Advanced Travel Information System (ATIS) to reduce project development uncertainty and produce a more functional end product.(10/19/1998)Institutional lessons from a test of a wide-area network to communicate traffic conditions in the Seattle area.
Ensure good data quality to successfully integrate weather alert system based upon Road Weather Information Systems.(August 2010)Caltrans District 3 experience in implementing a weather alert notification system in a Regional Transportation Management Center
Beware of accuracy and privacy issues in using truck transponder data for developing real-time traveler information applications.(August 2009)An Oregon Department of Transportation Experience
Incorporate diagnostic tools to identify and verify problems in the transmission of video in a transit bus security system.(01/30/2009)Experience from iFlorida Model Deployment
Thoroughly test, evaluate, and maintain animal detections systems.(August 2006)Montana and Pennsylvania's experience with deploying animal detection systems.
Recognize integration issues in Advanced Traveler Information Systems (ATIS) Projects, and follow the systems engineering approach to establish a project's foundation.(April 2006)Experience from the Pennsylvania Turnpike Commission.
Provide reliable travel time information to increase user satisfaction with ITS applications.(October, 2004)A retrospective of what's been learned since the first ITS Strategic Plan developed in 1992.
Use Analysis, Modeling, and Simulation (AMS) to identify gaps, determine constraints, and invest in the best combination of Integrated Corridor Management (ICM) strategies.(September 2008)Experience with the AMS framework on the ICM Test Corridor, San Francisco.
Develop best and worst case scenarios in order to be prepared in dealing with their consequences.(12/1/1999)California's experience with a regional travel information system launched by a public-private alliance.
Select map displays, computers, and software for transportation management centers (TMCs) that minimize cost and decrease complexity.(10/1/1999)Eight states' experiences with map displays, computers, and software for TMCs.
We’ve added a new multi-select feature to the filter boxes to make searches more efficient. Let us know what you think by clicking "Help Us Improve" under the Help menu on the left of the page.
