Draft SOW SmartPhone app Feasibility (693JJ921RQ001063).pdf

REQUEST FOR PROPOSAL

Older Driver Research Feasibility Study

Draft 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 with the goal of preventing tragedies and reducing economic costs associated with vehicle use and highway travel.

NHTSA has been directed by Congress to explore the efficacy of smart phone 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, based on findings from Older Driver Support System Field Operational Test (Libby, D., Morris, N. L., & Craig, C. M., 2019)1 that tested effects of the app on a sample of 28 participants with an average age of 69.5. 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 setting for hard braking and stop sign running were too sensitive. While RoadCoach may prove beneficial to older drivers, NHTSA is concerned that an app that provides in-vehicle assistance could pose a distraction to the oldest drivers and that the behaviors the app addresses are not well matched to the behaviors that contribute to crashes among the oldest drivers.

This project will document the way that the RoadCoach system used by Libby et al., as well as similar smart phone apps (including those under development at universities), provide support to drivers, including how they determine when to alert the driver to a potentially risky behavior, the information provided to the driver, and the way the information is provided (e.g., visual, auditory). The project will also involve conducting a literature review that explores the kinds of errors most likely to result in crashes among two groups of drivers: those 18-25 (young adult) and those 75 older (older adult). The literature review will be accompanied by an analysis of NHTSA’s Crash Report Sampling System (CRSS) data to determine specific driving errors associated with crash contribution among young adult and older adult drivers. These activities will inform a final report that maps RoadCoach’s and the other apps’ features on to the errors associated with crashes among young adult and older adult drivers.

C.2 OBJECTIVE

The objective of this project is to provide a thorough description of the RoadCoach app's functions, specifically how the system detects and alerts drivers to risky behaviors, identify and describe other driver support smart phone apps (including those under development at universities), conduct a literature review and crash data analysis to identify driving behaviors commonly associated with crashes among young adult, and older adults drivers, and report the findings in a report that discusses the likelihood that each identified system would be effective in reducing risky driving behaviors among these cohorts of drivers.

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 https://rosap.ntl.bts.gov/view/dot/42705

Because the app was initially developed to reduce risk for teen drivers, the study will also include similar research on teen and young adult drivers.

C.3 GENERAL REQUIREMENTS

The Contractor shall:

1. Document RoadCoach’s functions through describing specific conditions that trigger the sensors, the information the system provides to the driver, and how the system provides this information in terms of feedback timing and modality. This description shall include the relationship between the conditions that trigger RoadCoach and the behaviors RoadCoach is designed to reduce.

2. Conduct a scan to identify other smart phone apps (including those under development at universities) that claim to improve driver safety. Describe these other smart phone apps, including their functionality and the behaviors they aim to change, and compare and contrast these apps with RoadCoach.

3. Conduct a systematic literature review to explore the kinds of driving errors associated with crashes, particularly crash contribution, among young adult and older adult drivers. Also explore issues related to driver feedback effectiveness based on timing and modality for young adult and older adult drivers. Highlight research literature that explicitly includes studies that sampled participants of different races and ethnicities and socioeconomic status to explore opportunities to increase safety of historically excluded groups.

4. Conduct a crash data analysis of the kinds of driving errors associated with crashes among young adult and older adult drivers.

5. Produce a final report describing findings from the smart phone app scan and review, the literature review, and the crash data analysis. This report shall discuss the extent to which RoadCoach’s and other apps’ designs, including feedback timing and modality, are optimal for each driver age group, and how they could be expected to change drivers’ behavior under conditions associated with elevated crash risk for each age group. This report shall explain whether RoadCoach could be expected to reduce crash risk for young adult and older adult drivers and whether any of the other apps could be expected to reduce crash risk for these two groups.

C.4 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.5.

C.4.1 ACRONYMS

The following is a list of key acronyms used throughout the Statement of Work (SOW). This list may not be exhaustive.

ACOR (TO) Alternate Contracting Officer’s Representative (Task Order) CO Contracting Officer

COR (TO) Contracting Officer’s Representative (Task Order) CS Contract Specialist DOT U.S. Department of Transportation NHTSA National Highway Traffic Safety Administration SOW Statement of Work

C.5 SPECIFIC REQUIREMENTS

C.5.1 Kick-Off Meeting

Within one (1) month of contract award, the Contractor shall attend a virtual Kick-Off Meeting with the NHTSA COR (TO), 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 goal, objective, scope, and anticipated challenges for the effort. The meeting will serve to identify any potential problems and their solutions to ensure successful completion of the project.

This shall also be a working meeting for the Contractor and NHTSA, allowing up to 4 hours for the meeting. The NHTSA COR (TO) will take the lead in the discussions and provide the background for the project. The Contractor shall then discuss the firm’s approach.

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

• Understanding of project objectives and design.

• Schedule of project activities.

• Understanding of deliverable requirements and specifications.

The Contractor shall work with the NHTSA COR (TO) prior to the meeting to prepare appropriate briefing materials on their proposed approach. Materials for the Kick-Off Meeting shall be completed and submitted to the COR (TO) for review and approval at least one (1) week prior to the Kick-Off Meeting. The COR (TO) will send feedback to the Contractor on Kick-Off Meeting materials within 3 days of receipt. The Contractor shall submit revised Kick-Off Meeting Materials at least one (1) day before Kickoff Meeting.

C.5.2 Chapter Topics Plan

The objective of this task is to develop, refine, and finalize the chapters for the Draft Final Report (C.5.7);

the remaining tasks shall follow from decisions made in this one. The Chapter Topics Plan shall contain detailed information about the content, scope, and organization of each chapter.

Each chapter shall present a summary and synthesis of the findings relevant to that chapter. Each chapter shall address similarities and differences between findings for young and older adult drivers. When writing each chapter, the Contractor shall be aware that it is not useful to have the chapter be, at one extreme, essentially a list of findings (e.g., a list of abstracts or an annotated bibliography). On the other hand, it is not useful to only present a set of conclusions about chapter topics that are too abstracted or go beyond what the body of research supports.

Below is a list of chapters and topics that shall be included in the report. However, the Contractor shall propose the nature and organization of topics within each chapter and shall suggest any additional chapters or topics they believe are critical for covering the breadth or depth of the topic. Note that each chapter should, to some extent, inform the next.

Chapters within the final report shall include, but are not limited to:

1. Smart Phone Driver Support Apps Scan. This first chapter shall explain the reason for the study in terms of crash risk for young and older adult drivers. It shall describe how smart phone apps can influence driver behaviors. Topics shall include, but are not limited to:

a. Discussion of the behaviors that smart phone apps have the potential to change. Discuss mechanisms the apps employ to detect potentially risky driver behaviors or situations and the way they alert drivers to those behaviors.

b. A description of smart phone apps (other than RoadCoach, including those under development at universities) available to the public that are advertised to enhance driver safety, and a brief description based on marketing materials of how these apps detect and alert drivers to potentially risky behaviors, and any information about their effects on driver behaviors including unintended consequences (e.g., driver distraction).

c. A description of RoadCoach’s sensors, and of behaviors or conditions that trigger the app. Discuss how sensitive RoadCoach is to various driver behaviors (e.g., hard braking), and how those sensitivity levels were selected, and how these characteristics compare to those of other apps identified in 1(b).

d. An explanation of the quantity and type of information RoadCoach provides to the driver, including any delay between an event/behavior and system feedback as well as feedback modality and how this was selected; discuss how this compares to information provided by other apps identified in 1(b).

e. A discussion of how the conditions that trigger smart phone driver support apps relate to behaviors RoadCoach is designed to change.

2. Systematic Literature Review. This chapter shall describe methods and findings from a systematic literature review exploring driving behaviors and errors associated with crashes, focusing on those related to behaviors that smart phone apps address, and on the effectiveness of apps designed to change driver behavior. This chapter shall not include research related to alcohol and/or drug impaired driving. Documents used in the review shall include peer-reviewed journals, conference proceedings, State and Federal Government reports (including NHTSA reports), and grey literature. Each topic in the chapter shall address findings on young adults and on older adults and shall discuss how young and older drivers’ experiences/responses are similar and how they differ, particularly in terms of behaviors that can be addressed by a smart phone app. This chapter shall highlight research literature that explicitly sampled participants of different races and ethnicities and socioeconomic status to explore opportunities to increase safety of historically excluded groups. Chapter topics shall include but are not limited to:

a. Systematic literature review methodology.

b. Findings regarding characteristics most often associated with crashes: What types of crashes (e.g., intersection crashes, loss of control, distracted driving) are more typical of young adult drivers, of older adult drivers, and common to both age groups?

c. Findings regarding driver feedback effectiveness: What factors (e.g., feedback timing and modality, feedback validity) are associated with effective driver feedback like that provided by smart phone apps, and do these factors differ for younger and older drivers?

What unintended consequences are likely to emerge?

d. Findings regarding driver acceptance of such systems: What system features are associated with higher user acceptance, and does this differ between younger and older users?

3. Data Analysis. This chapter shall describe CRSS crash data analysis to confirm the literature review findings identified in Chapter 2 regarding crash types that are common among young drivers, older drivers, and to both groups. The chapter shall discuss data selection and analysis methods and findings. Each topic within the chapter shall address driver behaviors and/or traffic situations associated with crashes in young adults and in older adults and shall discuss how young and older drivers’ experiences/responses are similar and how they differ. The analysis must use appropriate sample weights and hypothesis testing that considers the complex sample design.

Topics shall include but are not limited to:

a. Crash characteristics

i. Crash configuration (e.g., head-on, angle).

ii. Movement prior to critical event (e.g., passing, turning).

iii. Initial impact point (e.g., front/corner, left side).

b. Roadway characteristics

i. Speed limit.

ii. Number of traffic lanes.

iii. Junction/non-junction.

iv. Traffic control type.

4. Discussion and Conclusions. This chapter shall summarize findings from the smart phone driver support app scan (Chapter 1), the literature review (Chapter 2), and the crash data analysis (Chapter 3), highlighting areas where RoadCoach and other apps are well-matched to driver errors, and those where they are not, comparing and contrasting findings for young adult and older adult drivers. This chapter shall discuss the extent to which RoadCoach’s, and other app’s, designs, including feedback timing and modality, are optimal for each driver age group’s crash types, and how they could be expected to change drivers’ behavior under conditions associated with elevated crash risk for each age group. This chapter shall explain whether RoadCoach could be expected to reduce crash risk for young adult and older adult drivers and whether any of the other apps could be expected to reduce crash risk for these two groups

The Contractor is free to recommend and justify inclusion of other topics to be considered for inclusion.

The Chapter Topics Plan shall refine and finalize the above topics, including any proposed additional chapter topics. The plan shall provide detail about the topic for each chapter, as well as the sub-topics within each chapter that will contribute to the overall chapter topic. When developing the Chapter Topics Plan, the Contractor shall do an initial brief scan of the literature and the CRSS database to obtain the information necessary to refine and finalize the chapter topics.

The Contractor shall submit the Chapter Topics Plan within two (2) months of contract award; the COR (TO) will give feedback on the plan to the Contractor within two (2) weeks of receipt.

The Contractor shall submit the revised Chapter Topics Plan within three (3) months of contract award.

C.5.3 Smart Phone Driver Support Apps Scan

The objective of this task is to develop and then carry out a plan to collect and discuss information about driver support smart phone apps (including those under development at universities) and specifically about RoadCoach. The Plan shall provide details regarding how the scan will be conducted, how apps under development at universities will be identified, and the information synthesized to address each topic identified for this chapter under C.5.2.

Within four (4) months of contract award, the Contractor shall submit a Draft Smart Phone Driver Support Apps Plan documenting how the Contractor will address each topic listed in C.5.2. The COR (TO) shall review the Draft Final Report and submit comments within two (2) weeks of receipt.

Upon receipt of COR approval of the Draft Smart Phone Driver Support Apps Plan, the Contractor shall carry out the plan as described under C.5.2.

Within six (6) months of contract award, the Contractor shall submit the draft Smart Phone Driver Support App chapter. The COR (TO) will submit comments on the Chapter Draft within two (2) weeks of receipt.

Within seven (7) months of contract award, the Contractor shall submit the revised draft Smart Phone Driver Support App chapter that addresses all COR comments.

C.5.4 Systematic Literature Review

The objective of this task is to develop a plan to conduct the systematic literature review that will address the topics determined under C.5.2. The Systematic Literature Review Plan shall describe how the review will be conducted, as well as additional information that may be unique to a topic. The Contractor shall review original research studies or reviews of original research published between 2014 and the date of the review. The plan will also explain how the Contractor plans to extract the necessary information from and critically evaluate each study selected for inclusion in the literature review. While it is not necessary for the Contractor to evaluate study quality in a quantitative way, the Contractor shall, at a minimum, describe procedures for qualitatively, but systematically, assessing each study’s quality. For each topic, the Contractor shall identify commonalities or, where relevant, discrepancies in findings while simultaneously considering the quality of the information source.

The Systematic Literature Review Plan shall include, but is not limited to:

• A list of sources that will be searched to identify relevant studies, including studies published in peer-reviewed journals, conference proceedings, State and Federal Government reports (including NHTSA reports), grey literature, and any other sources the Contractor believes relevant. Sources may include, for example, Google Scholar, Web of Science, Transportation Research International Documentation (TRID), and PsycINFO.

• General criteria for inclusion/exclusion that will be applied to all topics (e.g., English language publication, date of publication).

• The overall procedure or method the Contractor shall use to identify and review relevant abstracts, including how any disagreements about study inclusion will be resolved. The Contractor shall also explain how existing reviews or meta-analyses on a chapter topic will be treated in the review.

• The specific search strings (including Boolean operators) that will be used to identify relevant studies for the chapter in the above databases or other sources; and

• Any inclusion/exclusion criteria specific to a topic.

• Procedures for extracting the relevant information from each study (e.g., methods, results, and conclusions) for later use in the narrative synthesis of results.

• Factors to be considered when evaluating study quality, including internal validity (e.g., in a case-control experimental design, the way in which controls were selected), external validity (e.g., the relevance of the outcome measure to crash risk), as well as any other risks to study quality identified by the Contractor (e.g., conflicts of interest among study authors).

• Procedures for evaluating study quality, for example, which staff will assess study quality, how conflicts between assessors regarding study quality will be resolved, and how assessments of study quality will be used in the narrative synthesis of results.

o To assist in identifying appropriate questions regarding study quality, the Contractor shall consult study quality scales such as the Newcastle-Ottawa Scale2 and the RTI Item Bank;3 the Contractor shall also be guided by similar procedures used in other high-quality systematic reviews.

Within seven (7) months of contract award, the Contractor shall submit to COR (TO) a draft Systematic Literature Review Plan. The COR (TO) will return comments on the documents within two (2) weeks of receipt.

Upon receipt of COR approval of the Systematic Literature Review Plan, the Contractor shall carry out the plan to address the topics described under C.5.2.

Within 9 (nine) months of contract award, the Contractor shall submit the draft Systematic Literature Review chapter. The COR (TO) will submit comments on the Chapter Draft within two (2) weeks of receipt.

2 Wells, G. A., O’Connell, D., Peterson, J., Welch, V., Losos, M., & Tugwell, P. (n.d.). The Newcastle-Ottawa Scale (NOS) for assessing the quality of nonrandomised studies in meta-analyses. Retrieved June 15, 2018, from http://www.ohri.ca/programs/clinical_epidemiology/oxford.asp 3 Viswanathan, M., & Berkman, N. D. (2012). Development of the RTI item bank on risk of bias and precision of observational studies. Journal of Clinical Epidemiology, 65(2), 163–178. https://doi.org/10.1016/j.jclinepi.2011.05.008

Within eleven (11) months of contract award, the Contractor shall submit the revised draft Systematic Literature Review chapter that addresses all COR comments.

C.5.5 Crash Data Acquisition and Analysis

The objective of this task is to develop a plan to conduct an analysis of CRSS data that will comprise the data analysis chapter of the report to address the topics determined under C.5.2.

Information from the literature review shall inform selection of CRSS variables to include in the analyses. For each crash type or driver behavior in the analysis, the chapter shall discuss whether it occured in similar proportions for young adult and older adult drivers, or whether one age group was over-represented compared to the other. The Crash Data Acquisition and Analysis Plan shall describe inclusion criteria, justification for each variable and describe how cases meeting those criteria will be coded, organized and analyzed.

The data analysis plan shall include, but is not limited to:

• Method to use in developing CRSS data files.

• Driver, crash, and roadway variables selected for inclusion.

• Planned data analyses to identify significant group differences. All estimates must use the sample weights, and testing of statistical significance using CRSS data must must use standard errors adjusted for the sample design and weights.

Within eleven (11) months of contract award, the Contractor shall submit to COR a draft Crash Data Acquisition and Analysis Plan. The COR (TO) will return comments on the documents within two (2) weeks of receipt.

Upon receipt of COR approval of the Crash Data Acquisition and Analysis Plan, the Contractor shall carry out the plan to address the topics described under C.5.2.

Within thirteen (13) months of contract award, the Contractor shall submit the draft Crash Data Acquisition and Analysis chapter. The COR (TO) will submit comments on the Chapter Draft within two

(2) weeks of receipt.

C.5.6 Discussion and Conclusions The objective of this task is to summarize findings from the previous chapters, and to discuss the extent to which the RoadCoach app, and other similar apps, would be expected to reduce young adult and older adult driver behaviors associated with crashes as described in the literature review and CRSS data analysis. The discussion shall also cover the extent to which the apps’ feedback timing and modality are optimal for each age group based on findings from the literature review. The discussion shall address the topics listed for this chapter under C.5.2.

Within fifteen (15) months of contract award, the Contractor shall submit the draft Discussion and Conclusions chapter.

The COR (TO) will submit comments on the Chapter Draft within two (2) weeks of receipt.

C.5.7 Prepare Draft Final Report

The objective of this task is to create a Draft Final Report that provides the results of the research activities that comprise each chapter. The Draft Final Report shall include: Technical Documentation page, Executive Summary, and each chapter identified in the Chapter Topics Plan (Section C.5.2). The Draft Final Report shall adhere to standards detailed in the 6th Edition, Publication Manual of the American Psychological Association (APA).

Individual chapters in the Draft Final Report must each present a summary and synthesis of the findings relevant to that chapter. When writing each chapter, the Contractor shall be aware that it is not useful to have the chapter be, at one extreme, an unconnected list of abstracts or data analyses. On the other hand, it is not useful to only present a set of conclusions about a chapter topic that are too abstracted from individual findings or go beyond what the chapter content supports.

Within eighteen (18) months of contract award, the Contractor shall submit a Draft Final Report that contains the findings relevant to each chapter. The COR (TO) shall review the Draft Final Report and submit comments within two (2) weeks of receipt.

Within twenty-one (21)months of contract award, the Contractor shall resubmit the Draft Final Report after making the necessary edits suggested by the COR (TO).

The COR (TO) shall be listed as an author if the COR (TO) contributes significantly to the writing of the report. Order of authorship shall reflect the relative contributions of the authors.

C.5.8 Final Briefing

Within twenty-two (22) months of contract award, the Contractor shall develop and conduct collaboratively with the NHTSA COR (TO) a Final Briefing for this contract at NHTSA Headquarters in Washington, DC. The Final Briefing shall consist of a 20- to 30-minute presentation of the project that includes the background of the project, a description of the specific tasks conducted, and the study’s findings, followed by a question and answer period. Materials for the Final Briefing Meeting shall be completed and submitted to the COR (TO) for review and approval at least one (1) week prior to the Final Briefing Meeting. The COR (TO) will send feedback to the Contractor on Final Briefing Meeting materials within 3 days of receipt.

C.5.9 Revised Draft Final Report

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

C.5.9 Submit Final Report & Materials

Within twenty-four (24) months of contract award, the Contractor shall submit the Final Report, incorporating any remaining comments or edits generated from agency review, the Final Briefing, or the

COR (TO).

Along with the Final Report, the Contractor shall also submit all copies of journal articles or study publications included in the review, any databases that were used to manage references, CRSS analysis data set, and any other materials that were created and used during the project (e.g., forms used when extracting study results or evaluating study quality).

(End of Section C)

SECTION F – DELIVERIES OR PERFORMANCE

F.1 FAR 52.252-2 CLAUSES INCORPORATED BY REFERENCE (FEB 1998)

This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer (CO) will make their full text available. Also, the full text of a solicitation provision may be accessed electronically at this/these address:

www.acquisition.gov/far/.

Federal Acquisition Regulation (FAR) Clauses:

NOTE: Those clauses marked with an “X” are hereby incorporated by reference.

CLAUSE TITLE DATE

X 52.242-15 Stop Work Order AUG 1989 X 52.247-35 F.O.B. Destination, Within Consignee’s Premises APR 1984

F.2 PERIOD OF PERFORMANCE

All work required hereunder, including preparation, submission, review of any and all reports, shall be completed within the twenty-four (24) months from the effective date of the contract award.

F.3 PERFORMANCE MILESTONES (M) AND DELIVERABLES (D)

F.3.1 MILESTONES / DELIVERABLES SCHEDULE

http://www.acquisition.gov/far

The following milestone and deliverables apply to this Contract and are considered important to the successful completion of the project:

Item Task Deliverables (D) & Milestones (M) Due Date

1 C.5.1 Submit Kick-Off Meeting materials (D) At least 1 week prior to Kick- Off Meeting

2 C.5.1 COR submits feedback on Kick-Off Meeting materials (M)

Within 3 days of receipt

3 C.5.1 Submit Revised Kick-Off Meeting materials (D) At least 1 day prior to Kick- Off Meeting

4 C.5.1 Kick-Off Meeting (M) Within 1 month of contract award

5 C.5.2 Submit Chapter Topics Plan (D) Within 2 months of contract award

6 C.5.2 COR provides feedback on plan (M) Within 2 weeks of receipt

7 C.5.2 Submit revised Chapter Topics Plan (D) Within 3 months of contract award

8 C.5.3 Submit Smart Phone App Scan Plan (D) Within 4 months of contract award

9 C.5.3 COR provides feedback on plan (M) Within 2 weeks of receipt

10 C.5.3 Begin Smart Phone App Scan (M) Upon COR approval of plan

11 C.5.3 Submit Draft Smart Phone App Chapter (D) Within 6 months of contract award

12 C.5.3 COR provides feedback on chapter (M) Within 2 weeks of receipt

13 C.5.3 Submit Revised Smart Phone App Chapter (D) Within 7 months of contract award

14 C.5.4 Submit Literature Review Plan (D) Within 7 months of contract award

15 C.5.4 COR provides feedback on plan (M) Within 2 weeks of receipt

16 C.5.4 Begin Literature Review (M) Upon COR approval of plan

17 C.5.4 Submit Draft Literature Review Chapter (D) Within 9 months of contract award

18 C.5.4 COR provides feedback on chapter (M) Within 2 weeks of receipt

Item Task Deliverables (D) & Milestones (M) Due Date

19 C.5.4 Submit Revised Literature Review Chapter (D) Within 11 months of contract award

20 C.5.5 Submit Data Acquisition and Analysis Plan (D) Within 11 months of contract award

21 C.5.5 Begin Data Acquisition and Analysis (M) Within 11 months of contract award

22 C.5.5 Submit Data Acquisition and Analysis Chapter (D) Within 2 weeks of receipt

23 C.5.5 COR provides feedback on chapter (M) Within 13 months of contract award

24 C.5.5 Submit Revised Data Acquisition and Analysis Chapter (D)

Within 2 weeks of receipt

25 C.5.5 Submit Draft Discussion and Conclusions Chapter (D)

Within 14 months of contract award

26 C.5.6 COR provides feedback on chapter (M) Within 15 months of contract award

27 C.5.5 Submit Draft Final Report (D) Within 2 weeks of receipt

28 C.5.6 COR provides feedback on Draft Final Report (M) Within 18 months of contract award

29 C.5.6 Resubmit Draft Final Report (D) Within 2 weeks of receipt

30 C.5.6 Submit Final Briefing Materials (D) Within 21 months of contract award

31 C.5.7 COR provides feedback on Final Briefing Materials (M)

At least one week before Final Briefing

32 C.5.7 Final Briefing (M) Within 3 days of receipt

33 C.5.7 Begin Data Acquisition and Analysis (M) Within 22 months of contract award

34 C.5.8 Submit Revised Draft Final Report (D) Within 1 month after final briefing

35 C.5.8 COR provides feedback on Revised Draft Final Report (M)

Within 2 weeks of receipt

36 C.5.9 Submit Final Report and Materials (D) Within 24 months of contract award

37 F.4.1 Submit Monthly Reports (D) Ongoing, on the 10th of each month

F.4 PLACE OF DELIVERY:

Unless otherwise specified, deliverables shall be furnished, electronically, to the following addresses:

Item No.

Address

1, 3, 5, 7, 8, 11, 13, 14, 17, 19, 20, 23, 25, 26, 28, 30-34, 36, 37

Department of Transportation National Highway Traffic Safety Administration (NPD-120) Attention: TBD at Contract Award 1200 New Jersey Avenue, SE, WXX-XXX Washington, DC 20590 Telephone: (202) 366-XXX E-mail: TBD@dot.gov

Department of Transportation National Highway Traffic Safety Administration Office of Acquisition Management Attention: [Contract Specialist] 1200 New Jersey Avenue, SE, WXX-XXX Washington, DC 20590 Telephone: (202) 366-xxxx E-mail: [TBD@dot.gov]

F.4.1 MONTHLY REPORTS

The contractor shall furnish the report electronically to the COR (TO) by the 15th of each month following the month being reported. At a minimum, the progress report shall include a narrative description of the following items:

• Accomplishments made during the reporting period

• Funds status by major cost element, month's obligations, cumulative obligations estimated cost to complete, and percent of cost expended versus percent of completion

• Plans for accomplishments in next reporting period

• Preliminary or interim results, conclusions, trends, or other items of information that the

Contractor believes are of interest to NHTSA problems or delays that the Contractor has experienced and possible solutions for remedying these problems or delays, and

• Specific action that the Contractor would like NHTSA to undertake to alleviate a problem, and

• Due dates for remaining deliverables.

F.5 COMPLIANCE WITH REHABILITATION ACT

mailto:TBD@dot.gov mailto:larry.bursey.ctr@dot.gov

The Contractor may be required to ensure that electronic documents it prepares will meet the requirements of Section 508 of the Rehabilitation Act. The Rehabilitation Act requires that all electronic products prepared for the Federal Government be accessible to persons with disabilities, including those with vision, hearing, cognitive, and mobility impairments. When an electronic document developed under this effort have been identified by NHTSA as necessary and required to meet the requirements of Section 508, it is understood that all reasonable costs incurred by the Contractor that are associated with meeting the requirements for Section 508 compliance with be fully reimbursed by the Government.

The Contractor should review Section 508 of the Rehabilitation Act https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section- 508-standards and the Federal IT Accessibility Initiative further information on these requirements.

(End of Section F) https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards/section-508-standards