Distracted Driving Detection System for Work Zones Systems Requirements December 2015
Acknowledgements This document was prepared for the Minnesota Department of Transportation (MnDOT) Systems Engineering for Work Zone Challenges project. Project Champion Rashmi Brewer is the MnDOT project champion for this effort. MnDOT stakeholders and a project management team were heavily involved in identifying the key challenges with using Intelligent Transportation Systems to address and enhance safety, operations, mobility and efficiency in work zones. This document covers the system requirements to address some of these challenges. Project Management Team (MnDOT) Ralph Adair Tiffany Dagon Ted Ulven Craig Mittelstadt Leigh Kriewall Dave Mavec Ken Johnson Rashmi Brewer
Table of Contents Introduction... 1 System Requirements... 1 ITS Architecture... 1 High-Level and Detailed System Requirements... 5
Introduction Some research has been performed has occurred at the university level and some luxury automakers have installed distracted driver detection technologies. To date, there does not appear to be any wide scale, ITS type deployments for this concept. Parts of the technology exist and are in need of customization, where other technologies are still emerging. The best applications are through the detection of a vehicle drifting repeatedly between lane lines and wayward, or unintentional, lane changes. Lane drifting can occur anywhere at any time on our roadway networks, but it can be assumed that unintentional lane changes can occur in areas with lane shifts and lane reduction tapers. These systems can improve upon the existing work zone layouts by providing additional information in advance to travelers about current traffic conditions. These warnings help alert motorists as they enter work zones and areas within work zones where the maintenance of traffic requires unexpected maneuvers. The Minnesota Department of Transportation Intelligent Work Zone (IWZ) Toolbox guidance document serves as a starting point for discussion within the project team for ways to improve safety and mobility for the public, workers, and constructability of a project. The concept of operations document articulates the fundamental needs and operational concepts of the detecting distracted drivers. Building on those needs, the model system requirements within this document will describe what detecting distracted drivers must do and set the basis for system design, procurement, installation and operation. Both the system requirements and concept of operations are intended to illustrate the basic needs and requirements surrounding detecting distracted drivers and serve as model documents that may be adapted to meet individual deployments. The materials do not mandate the deployment of such systems, nor do they limit the engineering judgment or policy discretion of the transportation agencies who may consider deploying detecting distracted drivers. The materials reflect stakeholder needs and they should be adapted as necessary to reflect any unique or additional needs and requirements driven by individual deployments. The remainder of this document presents model system requirements for detecting distracted drivers as they are driven by the previously developed concept of operations. System Requirements System requirements are verifiable details that define what a distracted driver warning system will do, how well it will perform or what conditions it must perform under. An important starting point for developing system requirements is to understand where the system fits within the ITS architecture. This section explains how detecting distracted drivers fits within the National ITS Architecture 7.1 and then presents a series of high level and detailed system requirements associated with detection, alerts, placement, operations and maintenance. ITS Architecture Detecting distracted drivers are considered part of the Maintenance and Construction Operations User Service in the National ITS Architecture. Systems within in this user service provide Work Zone Management Safety function, which provides support for the effectiveness, safety, and efficiency of Distracted Driver Detection System (DDDS) Page 1
Roadway Work Traffic Control Equipment Package roadway operations during all work zone activities. The service will provide information concerning work zone activities. Within the physical architecture of the National ITS Architecture, detecting distracted drivers are primarily addressed under the following: Roadway (Architecture Flow) o Roadway (Subsystem) Roadway Work Traffic Control (Equipment Package) o MC09-Work Zone Safety Monitoring (Service Package) ATMS06-Traffic Information Dissemination (Service Package) ATMS08-Traffic Incident Management System (Service Package) Maintenance and Construction Management. (Subsystem) MCM Work Zone Management (Equipment Package) ATMS21 Roadway Closure Management (Service Package) MC08 Work Zone Management (Service Package) Tables 1 and 2 present a series of high-level requirements as they are presented within the Roadway Work Zone Traffic Control and MCM Work Zone Management Equipment Package of the National ITS Architecture. The currently applicable requirements have been incorporated into the document. Table 1. Roadway Work Traffic Control Functional Requirements Functional Requirements 1. The field element shall include work zone intrusion detection devices that detect when crew workers have crossed the boundary between the work zone and vehicle traffic, under center control. 2. The field element shall include work zone intrusion detection devices that detect when crew workers have crossed the boundary between the work zone and vehicle traffic, under center control. 3. The field element shall include work zone intrusion alerting devices that alert crew workers of a work zone emergency or safety issue such as the intrusion of a vehicle into the work zone area or movement of field crew into the travel lanes. 4. The field element shall include work zone intrusion alerting devices that notify crew via maintenance vehicles of a work zone emergency or safety issue such as the intrusion of a vehicle into the work zone area or movement of field crew into the travel lanes. 5. The field element shall include work zone intrusion alerting devices that alert drivers that they have intruded upon the perimeter of the work zone, or are about to do so; may provide alerts to drivers directly or via in-vehicle signing. 6. The field element shall provide operational status for the work zone intrusion detection devices to the maintenance center. 7. The field element shall provide fault data for the work zone intrusion detection devices to the maintenance center for repair. 8. The field element shall provide operational status for the work zone intrusion alerting devices to the maintenance center. 9. The field element shall provide fault data for the work zone intrusion alerting devices to the maintenance center for repair. * Equipment Package from National ITS Architecture Distracted Driver Detection System (DDDS) Page 2
MCM Work Zone Management Equipment Package Table 2. Maintenance and Construction Management (MCM) Functional Requirements Functional Requirements 1. The center shall generate new work zone activity schedules for use by maintenance and construction vehicles, maintenance and construction operators, and for information coordination purposes. 2. The center shall control the collection of work zone status information including video images from cameras located in or near the work zone. 3. The center shall disseminate work zone information to other agencies and centers including traffic, transit, emergency management centers, other maintenance centers, traveler information providers, and the media. 4. The center shall control traffic in work zones by providing remote control of dynamic message signs, highway advisory radio systems, gates, and barriers located in or near the work zone. 5. The center shall exchange information with administrative systems to support the planning and scheduling of work zone activities. This information includes: equipment and consumables resupply purchase request status, personnel qualifications including training and special certifications, environmental regulations and rules that may impact maintenance activities, and requests and project requirements from contract administration. 6. The center shall collect real-time information on the state of the road network including current traffic and road conditions to support work zone scheduling and management. * Equipment Package from National ITS Architecture Further illustrating how detecting distracted drivers fit within the National ITS Architecture, Figure 2 shows the potential system components and interconnects within the MC09-Work Zone Safety Monitoring Service Package and Figure 3 illustrates Driver Safety Monitoring Figure 1 MC09-Work Zone Safety Monitoring Service Package Graphic Distracted Driver Detection System (DDDS) Page 3
Figure 2 AVSS02 Driver Safety Monitoring The information presented in this section should be reviewed, confirmed or modified within the context of any state or regional ITS architecture that may impact individual detecting distracted driver deployments. Distracted Driver Detection System (DDDS) Page 4
High-Level and Detailed System Requirements These system requirements are defined in direct relation to the needs identified in the concept of operations. They address operational aspects of the system and are noted in Table 3. The number references allow for traceability back to those needs and forward to the detailed system requirements. The first identification number references the stakeholder need as presented in the concept of operations. The second number is used to track high level requirements and the third reference number relates to detailed system requirements, where applicable. For many of these requirements, special considerations are noted to explain what details were considered as the requirement was developed or what additional details may need to be considered as the requirement is further refined for individual deployments. In some cases, the consideration may also note if a requirement is relevant to a specific type of detecting distracted drivers deployment. These consideration are intended to offer context a provide insight that might help support further tailoring the requirements to the individual deployment as needed. Distracted Driver Detection System (DDDS) Page 5
Table 3 Distracted Driver Detection System (DDDS) Requirements ID # Needs ID # High Level Requirements ID # Detailed System Requirements 1 Drivers in a work zone need an alert when their vehicle enters a restricted area. 1.1 DDDS shall provide an alert to the driver of an unauthorized vehicle when the driver crosses into a restricted area. 1.1.1 The alert shall be audible and/or visual. Considerations: The advancement of the connected vehicles in the coming years will provide more opportunities for the visual notifications to drivers via En-Route Driver Information. However a work zone protection system with flashing lights when a vehicle enters the restricted area may help reduce unintentional intrusions. DDDS shall provide a physical 1.1.2 notification when driver crosses into a restrictive area. Considerations: Temporary rumble strips or current vehicles lane detection system, may help reduce unintentional intrusions. displayed in a vehicle. 2 Drivers, Agencies, and Law Enforcement need alerts to be accurate, relevant, easily understood, and reinforced at appropriate intervals through a work zone. 1.2 DDDS deployment shall follow MN IWZT guidance on spacing before work space. 1.3 Warnings and alerts provided shall follow the existing standards to help aid in compliance and understanding. 2.1 Warnings and alerts provided shall follow the existing standards to help aid in compliance and understanding. 1.2.1 DDDS shall provide an adequate buffer area to allow for braking and exit before entering work space. Considerations: Ideal placement of signs and detectors will vary per roadway speed, braking distances, and the acceptable driver reaction time. 1.3.1 DDS messages in and approaching the work zone shall provide information that is compliant and consistent with applicable national standards. Considerations: The National ITS Architecture should be the starting point for how En-Route driver information messages are 2.1.1 Central System logic shall recommend standards-compliant messaging to display on all DMS in the system. Considerations: This need and requirement address the ability to enforce the DDDS advisories, and ensure that messages do not result in additional liability. 2.1.2 Central System logic shall recommend standards-compliant messaging to display on all DMS in the system. Considerations: The MUTCD should be the starting point for how messages are displayed and further requirements should meet requirements included in the MN MUTCD. 2.1.3 The DDDS messages integrated with connected vehicles shall provide information that is compliant and consistent with national standards. Considerations: The National ITS Architecture should be the starting point for user requirements for how information messages are displayed in a vehicle. Distracted Driver Detection System (DDDS) Page 6
Table 3 Distracted Driver Detection System (DDDS) Requirements (Continued) ID # Needs ID # High Level Requirements ID # Detailed System Requirements 3 Agency and Law Enforcement Officials responsible for the work zone need the system to aid enforcement by generating reports identifying locations where violations are occurring. 3.1 Field devices shall receive alerts from system of a violation. 3.1.1 The DDS shall provide an alert to the Central System. Considerations: Agency will need to determine how enforcement will be handled before requirements are established for how fast an alert to the central system must be generated. 3.1.2 Central System shall provide an alert to the Law Enforcement of violation. Considerations: System should have a reporting structure which allows for notifications of incidents and also the ability to 4 Agencies with DDDS need ability to communicate with devices at all times. record video after an intrusion is detected for review. 4.1 Agencies shall be able to communicate remotely with device and check equipment status. 4.1.1 The communication media used for the system and field devices shall have 99.9% uptime (excluding maintenance periods). Considerations: Agency should determine if one medium is preferred over another. 4.1.2 The Central System shall record when system power or communication is lost. 4.1.3 The Central System shall be able to send alerts via email, text, or phone when power or communications losses occur. 4.1.4 The DDDS field components shall be capable of being powered via either AC or DC power sources, with solar power as an option. Considerations: Agency need this type of information to aid in payment, as these systems provide no benefit to workers if there is a breakdown in detection, communication, or power. 5 Agencies monitoring work zones need access to reports and logs when requested. 5.1 The DDDS shall include a data and system archive and reporting function. 5.1.1 The system data archive and reporting function shall be remotely accessible. Considerations: Agency need this type of information to aid in payment, as these systems provide no benefit to workers if there is a breakdown in detection, communication, or power. 5.1.2 The data archive shall include system faults. Considerations: Agency need this type of information to evaluate the effectiveness of the system, as these systems provide no benefit to workers if there is a breakdown in detection, communication, or power. 5.1.3 The system shall allow for configuration and automated generation of system reports. 5.1.4 The system shall be capable of generating reports in a variety of file formats for ease of use. Considerations: The system needs to be able to summarize data in an applicable format for end use needs. 5.1.5 System shall be capable of distributing reports generated automatically. Distracted Driver Detection System (DDDS) Page 7