WTI

Automated Safety Warning System Controller

Primary Investigator Contact Information

External Project Contact(s)

Report(s)

There are no reports associated with this project.

Project Objective

WTI will conduct research to develop an “Automated Safety Warning System Controller” that will interface with roadside sensors and signs. The controller will collect automated data and apply best practice algorithms to analyze sensor data and actuate related warning messages and signals.

Project Abstract

California has several automated warning systems on the state highways; however, all the systems to date are unique implementations using one-of-a-kind software for system control with the controller being a custom device only used with that particular project’s physical and electrical layout. Currently there is no standardized automated warning system controller which controls field elements in a rural environment. The WTI project team will design and build an automated warning system controller that can be easily configured to acquire sensor data from Roadside Weather Information Systems (RWIS), detection loops, Remote Traffic Microwave Sensors (RTMS) and video detection systems. The controller will include hardware and software interfaces for remote management and data acquisition. In addition, the controller will include extensible programming/scripting capability, allowing for programmed logic implementing the best practice algorithms for condition analysis and identification and corresponding warning signal/message actuation.

Task Descriptions

1. Project Management
   1. In conjunction with the kickoff meeting, Caltrans will deliver and install field element simulation hardware and software in WTI lab facilities. The project team will communicate regularly with the Caltrans project champion and project manager through all phases of the project to ensure that Caltrans’ needs are fully understood and addressed.
2. System Testing
   1. Formal and informal testing throughout the project will validate system performance and conformance to the design and requirements specifications. The system will be first tested within the lab with the simulated field elements, then with actual field elements using a remote data connection (dialup), and finally in the field with the field elements. Testing will be tightly coupled with development, design and requirements by following a “test, analyze, and fix” methodology. Deployment system testing will be conducted in conjunction with system evaluation.
3. System Evaluation
   1. In conjunction with Deployment System testing, the project team will conduct a system evaluation. This evaluation will not only assess the developed prototype system, but will assist Caltrans in determining next steps, including how to proceed with prospective deployment. Evaluation will be traced to the requirements specification and the logical system designed document.
4. Testing and Development Lab Setup
   1. The project team will set up a testing and development lab to simulate field elements such as CMS, RWIS, HAR Flasher, EMS, TMS, and RTMS. The lab will be used from the beginning of the project to create and test device interfaces and drivers, and later to test subsystems, modules, and the entire system.
5. System Design
   1. The project team will develop an initial high-level “Logical System Design” to document the proposed system. This document will serve as a blueprint for development and as a milestone for approval by the project champion and the project manager prior to full system development. The logical system design will cover both hardware and software aspects of the system and will be verified against the requirement specification. Crucial hardware decisions regarding necessary device interfaces, communication interfaces, power and enclosure will be made and agreed upon at this point. Software decisions including the approach to developing field element device drivers/modules, software interfaces, programming/scripting capabilities, and communication interfaces and protocols will be incorporated as well.
6. System Requirements
   1. The project team will conduct a requirements analysis to formalize system requirements. The project team will also produce a requirements specification documenting system requirements. This document will be used throughout the project for traceability, verification and validation.
7. System Concept
   1. The project team will analyze current practice and produce an inventory of relevant field elements and associated communication infrastructure, including current, planned and prospective elements. A statement of need/business case will document the problems with the current situation, a simple statement of the proposed solution, as well as urgency, benefits, and general expected return on investment. A concept strawman will document components of the proposed system including hardware, software, and communication elements. A Linux/FreeBSD – based architecture has been identified by Caltrans as preferred for this project. The project team will investigate the validity of using such an architecture for the proposed system. A search will be conducted for applications of Linux/FreeBSD in other ITS applications, as well as in other embedded systems and control systems. Prospective hardware and software will be identified and investigated for suitability.
8. System Development
   1. The project team will conduct development in two phases: Development System and Deployment System. During the Development System Phase, an in-lab system will be developed using standard off-the-shelf equipment allowing for rapid development in a reliable and flexible environment. During the Deployment System Phase, hardware and software will be integrated into a stand-alone system that can be deployed for testing purposes.

Milestones, Dates, Schedule

Student Involvement

True

Relationship to Other Research Projects

True

Technology Transfer Activities

True

Transportation Research Board Keywords

Control System, Intelligent Transportation Systems, Rural Transportation

Partners

Caltrans