University of Minnesota Driven to Discover
U of MNUniversity of Minnesota
Center for Transportation Studies

Rural Unsignalized Intersections

The Infrastructure Consortium: Intersection Decision Support

Overview | Project Components | Meetings & Presentations | Publications

Projects Components - Task D: System Requirements & Specification Definition

With the results of the enabling research and benefit/cost analysis tasks, the next appropriate step is to determine system requirements and specifications necessary to implement an effective, economical, deployable IDS. Both the surveillance and the driver-infrastructure interface are addressed. System Requirements and System Specifications will document the outcome of the entirety of Task B, enabling research, and will incorporate the findings of Task C to provide an optimal solution to the IRC intersection crash problem. This document will provide the foundation upon which IDS systems for rural intersection can be deployed.

SUBTASK D1: SYSTEM REQUIREMENTS.

From the surveillance system point of view, functional requirements for the IDS system will address the amount of sensor coverage required for a particular intersection geometry and anticipated traffic speeds, environmental concerns (i.e., all weather capability), and system robustness and reliability goals as well as failure modes. To meet state DOT safety standards, the IDS sensor suite must also meet particular functional requirements (distance from the roadway, break-away mounting structures, etc.). From the driver interface point of view, functional requirements include the content of information to be provided to the driver, and the timing in which that information is presented to the driver. Collaboration with Mn/DOT in the development of system functional requirements is the first step in the system deployment process.

Back to Top image

SUBTASK D2: SYSTEM SPECIFICATIONS.

In this task, functional requirements will be used to generate a full set of system specifications. The system specifications will dictate quantifiable design guidelines for the IDS sensor subsystems, communication subsystems, computational subsystems, and driver interface subsystems. Through the use of the experimental intersection to be constructed in Minnesota, the system specifications will be validated and correlated with system performance.

SUBTASK D3: MUTCD EXPERIMENTAL APPROVAL.

Complementing the documentation of System Requirements & Specification Definition will be an effort coordinated with MN/DOT and CH2MHILL to seek approval by the National Committee on Uniform Traffic Control Devices for the Driver-Infrastructure Interface design produced by this IDS Project. Timely approval of this interface will facilitate the execution of a Field Operational Test which will validate the effectiveness of this Rural IDS system.

Task D Deliverables: A report documenting system requirements and system specifications for both the surveillance and the driver interface subsystems. A formal request to the National Committee on Uniform Traffic Control Devices for approval to operationally deploy and test the prototype driver interface will be pursued to facilitate the deployment of this interface during the Field Operational Test portion of this project (see Task E below).

Task D Duration: 6 months

Link to state pooled fund: Pooled fund states will equip their intersections with surveillance equipment based on the design specifications developed via this task. The University of Minnesota will provide design and implementation guidance to the states choosing to instrument their intersections.

Back to Top image