693JJ925RQ000450 Draft SOW SmartPhone app Development.pdf

Developing a Smartphone App to Enhance Older Driver Safety Solicitation # 693JJ925R000450, Draft SOW

DRAFT STATEMENT OF WORK (SOW)

C.1 BACKGROUND

The National Highway Traffic Safety Administration (NHTSA) is an agency of the U.S. Department of Transportation (DOT). NHTSA’s mission is to save lives, prevent injuries, and reduce traffic-related health care and other economic costs. The agency develops, promotes, and implements educational, engineering, and enforcement programs aimed at preventing tragedies and reducing economic costs associated with vehicle use and highway travel.

NHTSA has been directed by Congress to explore the efficacy of smartphone applications (apps) as an intervention for older drivers. Congressional staff expressed a particular interest in Road Coach, a smart phone app originally developed to reduce risky driving in teens. This interest was based on findings from the Older Driver Support System Field Operational Test1, which tested the effects of the app on a sample of 28 participants with an average age of 69.5 years. Libby and colleagues reported that RoadCoach use resulted in reduced hard braking events and stop sign violations. Participants’ attitudes toward RoadCoach were generally positive, but some noted that the app's settings for detecting hard braking and stop sign violations were too sensitive.

In a recent study,2 Peterson and colleagues found that apps can reduce some risky driving behaviors, but that most of the apps were better suited to addressing behaviors common among young and middle-aged drivers’ crashes. The study produced a list of feasible app features that map to driving tasks that can be risky for older drivers. An app with features which could support older drivers by alerting them to upcoming elements of the driving environment (e.g., changes in speed limit, sharp curves, intersection details) or by providing routes that avoid complex driving tasks such as unprotected left turns, could reduce risk for these drivers.

C.2 OBJECTIVE

For this project, the Contractor shall design, develop, and pilot test an app that supports older drivers by reducing their cognitive workload. This app will assist older drivers in avoiding risky traffic situations— such as unprotected left turns—and alert them to upcoming changes in the driving environment, like speed limit changes or sharp curves. After developing the app, the Contractor shall design a field operational test (FOT) to document its effects on older adults’ driving habits and performance. The Contractor shall also provide a draft information collection request (ICR) with supporting documents, Federal Register Notices, and Privacy Threshold Assessment documents for the subsequent study design.

Final deliverables shall include the final version of the app and a final report that describes the app’s purpose, development process, the naturalistic driving study design, along with supporting documents.

1 Libby, D. A., Morris, N. L., & Craig, C. M. (2019). Older Driver Support System Field Operational Test. Final Report CTS 19-13. Roadway Safety Institute. https://rosap.ntl.bts.gov/view/dot/42705 2 Peterson, C. M., St. Louis, R. M., Eby, D. W., Molnar, L. J., Zanier, N., Zakrajsek, J. S., Sifrit, K. J., Flannagan, C.

A. (under review). Assessment of smartphone apps designed to improve safety for older drivers and teen drivers (Report No. DOT HS xxx xxx). National Highway Traffic Safety Administration.

https://rosap.ntl.bts.gov/view/dot/42705

The FOT would be carried out under a separate contract.

C.3 ACRONYMS

ACOR Alternate Contracting Officer’s Representative CO Contracting Officer COR Contracting Officer’s Representative CS Contract Specialist DAS Data Acquisition System DMP Data Management Plan DOT U. S. Department of Transportation FOT Field Operational Test ICR Information Collection Request IRB Institutional Review Board NDS Naturalistic Driving Study NHTSA National Highway Traffic Safety Administration PRA Paperwork Reduction Act SOW Statement of Work

C.4 GENERAL REQUIREMENTS

The Contractor shall:

1. Develop a draft application (app) design, including wireframe and user interface, for iOS and Android devices based on information in Assessment of Smartphone Apps Designed to Improve Safety for Older Drivers and Teen Drivers, targeted at users 65 and older.

2. Test the wireframe to ensure that it is easily comprehensible to older drivers.

3. Build a prototype of the app informed by the wireframe testing, conduct a pilot test of the prototype with up to nine older drivers, then revise the prototype based on their feedback.

4. Design an FOT to assess the app’s performance, usability, and effects on behaviors for a sample of older drivers (the FOT will be conducted under a different project). The FOT shall include a naturalistic driving element to demonstrate the effects of the app during real-world driving.

Include draft submissions for IRB approval, a draft Information Collection Request, and draft Privacy Threat Assessment with the study design.

5. Produce a final report describing the app’s design and user interface, the iterative improvements made following wireframe testing, and the detailed results of the naturalistic driving study. This report shall also include a discussion of the specific changes made to the app following the naturalistic driving study. It shall also include a list of suggested app features that could be added in future design iterations.

C.5 SCOPE OF WORK

The Contractor shall furnish the necessary personnel, equipment, and facilities, and otherwise perform all things necessary for or incidental to the performance of work (the accomplishment of specific requirements) as set forth below in Section C.6.

C.6 SPECIFIC REQUIREMENTS

C.6.1 Conduct Kick-Off Meeting

At least one week prior to the Kick-Off Meeting, the Contractor shall submit Kickoff briefing materials. The COR will provide feedback within three (3) days of receipt.

At least one day prior to the Kick-Off Meeting, the Contractor shall submit revised Kick-Off briefing materials.

Within two (2) months of contract award, the Contractor shall take part in a virtual Kick-Off Meeting with the NHTSA COR, CO and/or CS, and any other interested NHTSA personnel. The purpose of this meeting is to discuss the administration of the Contract and the goals, objectives, scope, and anticipated challenges of the effort. The meeting will serve to identify any potential problems and their solutions to ensure successful completion of the project.

The Kick-Off Meeting shall also be a working session lasting up to two (2) hours. The Contractor will describe their approach and respond to questions in the first hour. During the second hour, the Contractor will discuss plans in more detail with the COR, ACOR, and other members of OBSR. The COR will take the lead in the discussions and provide the project background.

The Contractor’s description of their approach shall include the following:

• An understanding of project objectives and design.

• A schedule of project activities.

• An understanding of deliverable requirements and specifications.

Prior to the meeting, the Contractor shall work with the COR to prepare appropriate briefing materials on their proposed approach.

C.6.2 Submit Work Plan

Within three (3) months of contract award, the Contractor shall submit the Draft Work Plan. The COR will provide feedback on the plan to the Contractor within two (2) weeks of receipt.

Within five (5) months of contract award, the Contractor shall submit the revised Work Plan.

The Work Plan shall provide a thorough description of the Contractor’s approach to each of the subsequent tasks as outlined in the proposal. The Work Plan shall be amended after consultation with the COR to address questions and comments that arise during the kickoff. The Work Plan shall include a DMP consistent with DOT’s public Access Plan (https://www.transportation.gov/mission/open/official-dot-public-access-plan-v11).

C.6.3 Submit Draft App Design

Within ten (10) months of contract award, the Contractor shall submit a draft of the app design; the COR will provide feedback on the draft within four (4) weeks of receipt.

The Contractor shall develop a draft app design that describes and justifies the proposed features to be incorporated into the smartphone app for older drivers (iOS and Android), informed by the Peterson et al., 202x. The features and user interface shall be specifically tailored to drivers aged 65 and older. The Contractor shall include a development plan that includes wireframe testing with up to nine older adult drivers who are proficient with smartphones.

The design shall prioritize user experience (UX) and user interface (UI) elements that cater specifically to older users such as large, easy-to-read fonts, high contrast displays, and simplified navigation. Real-time feedback features are to be tailored to help the driver navigate complex driving situations—like providing advance alerts of upcoming intersections, intersections atop/over a hill, or unprotected left turns. These features are to be designed to augment the driver’s situational awareness without causing additional distraction. Considerations may include, but are not limited to, voice command capabilities or customizable settings that allow users to adjust the interface to their comfort level. The design shall include a tutorial tailored to older drivers to help users become comfortable with the app’s functionality, increasing adoption and long-term use.

C.6.4 Conduct App Design Testing and Optimization

Upon COR approval of the Draft App Design, the Contractor shall begin wireframe development and testing.

Within eighteen (18) months of award the Contractor shall take part in a virtual briefing with the COR and other interested NHTSA staff to demonstrate the final wireframe.

Within twenty (20) months of contract award, the Contractor shall complete the app optimization and submit a final app design that includes a summary of all changes made based on testing and comments made during the virtual briefing. The COR will submit comments on the final app design within four (4) weeks of receipt.

The Contractor shall conduct iterative testing of the wireframe developed in accordance with Section C.6.3 with a sample of nine or fewer drivers aged 65 or older. The testing shall aim to refine usability and ensure the app works across iOS and Android platforms.

App optimization shall focus on fine-tuning features based on insights gained from wireframe testing.

This shall involve factors such as alert timing, personalization of feedback, and the sensitivity of behavioral detection algorithms (e.g., ensuring that alerts are not triggered by/for trivial events that do not pose a risk).

C.6.5 Build and Pilot Test App Prototype

Upon approval of wireframe by the COR , the Contractor shall begin building the prototype app.

Within thirty-two (32) months of award, the Contractor shall submit a letter report describing the app design as informed by wireframe testing and COR comments, and providing the protocol for pilot testing the app. The COR will provide comments on the letter report within two (2) weeks of receipt.

Within thirty-four (34) months of award, the Contractor shall participate in a virtual briefing with the COR and other interested NHTSA staff to demonstrate the app prototype and describe and justify the rationale for the pilot testing protocol.

Within thirty-five (35) months of award, the Contractor shall submit a Revised App Design and Pilot Test Protocol Letter Report that addresses any comments made during the briefing.

Upon approval of the prototype and Pilot Test Protocol by the COR, the Contractor shall begin pilot testing the app.

Within forty (40) months of award, the Contractor shall submit a Prototype App and Pilot Test Letter Report that describes and justifies the app features and the pilot testing process and outcomes.

The development phase shall involve building both the front- and back-end components of the prototype based on validated designs from C.6.4. Front-end development shall focus on creating an interface that is aesthetically pleasing and highly functional for the target audience as determined by wireframe testing.

Back-end development shall leverage technologies to process driving behavior in real time based on data from smartphone sensors, such as the GPS and gyroscopes, in order to trigger alerts to the driver regarding errors or potential hazards.

The Contractor shall conduct unit testing to ensure that each component functions correctly and user acceptance testing (UAT) with older drivers to ensure that the app performs effectively in real-world conditions for this population. UAT shall assess the app’s ability to provide timely and accurate feedback without overwhelming the older driver. Real-time feedback mechanisms shall strike a balance between being helpful and non-intrusive, ensuring that they support, rather than distract, the driver.

The Contractor shall conduct pilot testing with up to nine (9) drivers 65 and older. This task aims to test the app’s capacity to detect and alert the driver to risky behaviors common among older drivers. The Contractors shall ensure that the app’s interventions do not introduce an unacceptable level of distraction or frustration.

C.6.6 Submit Field Operational Test Design

Within forty-four (44) months of award, the Contractor shall submit the design for a FOT to test the app’s performance, usability, and effects on driver behaviors in a sample of older drivers. The COR will submit comments on the design draft within four (4) weeks of receipt.

Within forty-seven (47) months of award, the Contractor shall submit a revised FOT Design, addressing COR comments.

The FOT design shall include research questions focused on the effectiveness of the app in changing driving behaviors associated with older drivers’ crashes, its usability and user acceptance measures, and its effects on overall driver performance. The FOT shall include naturalistic driving to assess the effects of the app on driver performance during real-world driving. Performance metrics may include but are not limited to speed and lane position consistency, intersection navigation errors, crashes or near misses, and driver acceptance of feedback and of alerts to upcoming roadway features (e.g., sharp curves). The Contractor shall identify independent variables including, but not limited to, sex; age groups (65-74, 75- 84, 80+, etc.); and other relevant variables (i.e., prior smartphone usage or driving experience).

Dependent variables shall measure app performance and, effects on driver behaviors, and usability/user acceptance. The FOT design shall include:

• A table that maps each research question to independent variables, dependent variables, and analysis methods to ensure clarity in addressing each research question.

• A power analysis to determine the appropriate number of participants needed to support reliable analyses.

• A detailed list describing variables that the Data Acquisition System will collect, including data types, frequency of data collection, and data storage methods.

• A description of participant groups including inclusion/exclusion criteria to ensure balance across age, sex, and other independent variables.

• Consent forms and data collection questionnaires with justification for each item, ensuring they are tailored to the target demographic and comply with ethical standards.

• Data collection protocol, including participant training procedures on how to use the app, a schedule of data collection activities, and methods for monitoring compliance and data integrity.

• An outline of data security and privacy measures including how participant data will be protected through data encryption, secure storage solutions, and protocols for data access and sharing.

• A risk management plan identifying potential risks to participants (i.e., increased distraction, data privacy concerns) and describing strategies to mitigate these risks; potential risks are to be tailored to the approach rather than more general or unlikely risks (e.g., failure to obtain IRB approval).

• A data analysis plan detailing the statistical methods that will be used to clean, code, and analyze data, including how these data will address each research question.

• A description of participant incentives.

• An app deployment strategy detailing how the app will be installed on participants’ devices, including technical support and troubleshooting procedures.

• A timeline with a detailed schedule for each phase of the study.

• Drafts of the Information Collection Request and supporting documents, including draft Federal Register Notices, Privacy Threshold Assessment documents, and Institutional Review Board (IRB) request.

The Contractor shall ensure that all study materials and protocols are specifically tailored to drivers 65 and older. The design shall prioritize minimizing participant burden while maximizing data quality and relevance.

C.6.7 Submit Draft Final Report

Within Fifty (50) months of award, the Contractor shall submit the Draft Final Report. In preparing the Draft Final Report, the Contractor shall draw upon material developed in earlier phases of this project, namely, the Draft Introduction and Methods sections, making changes as necessary to reflect the current study design. The COR will provide feedback on the Draft Final Report within three (3) weeks of receipt.

Within fifty-two (52) months, the Contractor shall make the required revisions and submit to the COR the Revised Draft Final Report.

The Draft Final Report shall include the following sections:

• Executive Summary

• Introduction

• Methods

• Results

• Discussion

• References

• Appendices (if any)

The Draft Final Report shall adhere to standards detailed in the Publication Manual of the American Psychological Association (APA), 7th edition. According to the APA manual, “plagiarism is the act of presenting the words, ideas, or images of another as your own” (p. 254); the manual also notes that plagiarism can be “deliberate or unintentional” (p. 254). The Contractor shall ensure that the Draft Final Report is original and free from any form of plagiarism.3 Furthermore, the Contractor shall represent and warrant that the research work, including all written content, analyses, and findings, is original and does not infringe upon the intellectual property rights of any third party.

The Contractor shall ensure that the Draft Final Report is written using the NHTSA report template, which the COR will provide to the Contractor at award.

In the Discussion section, the Contractor shall clearly describe how the results address the research questions listed in Section C.2, any limitations of the study, and explain how study results can be translated to practice—particularly the implications for older drivers.

C.6.8 Conduct Final Briefing Meeting

3 See also: APA. (2021). 7th Edition Avoiding Plagiarism Guide. https://apastyle.apa.org/instructionalaids/ avoiding-plagiarism.pdf

At least one (1) week prior to the Final Briefing Meeting, the Contractor shall submit the Final Briefing materials to the COR for review and approval. The COR will provide feedback to the Contractor on the Final Briefing Meeting materials within 3 days of receipt.

At least one (1) day prior to the Final Briefing Meeting, the Contractor shall submit Revised Final Briefing Materials that incorporate COR comments.

Within fifty-five (55) months of contract award, the Contractor shall, in collaboration with the COR, develop and conduct a virtual Final Briefing for this contract. The Final Briefing shall consist of a 20- to 30-minute presentation of the project, including background, a description of specific tasks conducted, and findings, followed by a question-and-answer period.

The Contractor shall conduct collaboratively with the COR a Final Briefing Meeting virtually using teleconferencing software. The Final Briefing shall consist of a 30- to 45-minute presentation of the project given by the Contractor that includes the background and motivation for the project, the study’s design and hypotheses, the project’s results, and a discussion of the study’s results, particularly targeted at implications for older driver mobility and safety. The Contractor’s presentation shall be followed by a question-and-answer period. During the presentation, the Contractor shall present relevant methodological, statistical, and technical information in an accurate way that is also understandable to those without research backgrounds, as both researchers and non-researchers are likely to be in attendance.

C.6.9 Submit Revised Draft Final Report

Within one (1) month after the Final Briefing, the Contractor shall submit a Revised Draft Final Report incorporating comments from the Final Briefing and any available agency review. The COR will submit comments within three (3) weeks of receiving the Revised Draft Final Report.

C.6.10 Submit Final Report & Materials

Within sixty (60) months after the Final Briefing, the Contractor shall submit the Final Report incorporating COR comments. The Contractor shall also submit all materials developed during the project including data used during wireframe and pilot testing as well as the final version of the app.

(End of Section C)