NOFO 693JJ924R000025 SEDC.pdf

Notice of Funding Opportunity (NOFO)

Federal Agency United States Department of Transportation (U.S. DOT) National Highway Traffic Safety Administration (NHTSA)

Funding Opportunity Title State Electronic Data Collection (SEDC) Grant

NHTSA NOFO Number

693JJ924R000025

Assistance Listing Program Number (formerly CFDA)

20.614 - National Highway Traffic Safety Administration (NHTSA) Discretionary Safety Grants

Key Dates NOFO Posted Date: January 31, 2024 NOFO Questions Due Date: March 1, 2024 Application Due Date: May 1, 2024

NHTSA Notice of Funding Opportunity (NOFO) No. 693JJ924R000025

Notice of Funding Opportunity for the State Electronic Data Collection (SEDC)

TABLE OF CONTENTS

PROGRAM SUMMARY INFORMATION

SECTION A. PROGRAM DESCRIPTION

A.1. BACKGROUND, PURPOSE, AND OBJECTIVE

A.2. PROGRAM AUTHORITY

A.3. ADMINISTRATION PRIORITIES

A.4. DEFINITIONS

SECTION B. FEDERAL AWARD INFORMATION

B.1. AWARDING AGENCY

B.2. FUNDING AND TYPE OF AWARD

B.3. APPLICATION PERIOD

B.4. PERIOD OF PERFORMANCE

B.5. MILESTONES (M) AND DELIVERABLES (D)

B.6. PLACE OF DELIVERY

B.7. STATE GRANT REQUIREMENTS

B.8. PUBLIC ACCESSIBILITY OF STATE CRASH DATA

SECTION C. ELIGIBILITY INFORMATION

C.1. ELIGIBLE APPLICANTS

C.2. COST SHARING OR MATCHING

C.3. ELIGIBLE ACTIVITIES AND COSTS

SECTION D. APPLICATION AND SUBMISSION INFORMATION

D.1. ADDRESS TO REQUEST APPLICATION PACKAGE

D.2. CONTENT AND FORM OF APPLICATION SUBMISSION

A) TECHNICAL APPLICATION

B) BUDGET EXECUTION PLAN

D.3. UNIQUE ENTITY IDENTIFIER AND SYSTEM FOR AWARD MANAGEMENT (SAM)

D.4. SUBMISSION DATES AND TIMES

D.5. FUNDING RESTRICTIONS

D.6. OTHER SUBMISSION REQUIREMENTS

SECTION E. APPLICATION REVIEW INFORMATION

E.1. EVALUATION CRITERIA

A) TECHNICAL EVALUATION

EVALUATION FACTOR 1: TECHNICAL APPROACH

EVALUATION FACTOR 2: PROJECT MANAGEMENT

EVALUATION FACTOR 3: ALIGNMENT TO MMUCC

EVALUATION FACTOR 4: DATA QUALITY

EVALUATION FACTOR 5: CRASH DATA SYSTEM COORDINATION

B) COST EVALUATION

E.2. REVIEW AND SELECTION PROCESS

E.3. SYSTEM FOR ACQUISITION MANAGEMENT REVIEW

E.4. ANTICIPATED ANNOUNCEMENT AND FEDERAL AWARD DATES

SECTION F. FEDERAL AWARD ADMINISTRATION INFORMATION

F.1. FEDERAL AWARD NOTICES

F.2. ADMINISTRATIVE AND NATIONAL POLICY REQUIREMENTS

F.3. REPORTING

QUARTERLY PROGRESS AND FINANCIAL REPORTS

FINAL REPORT

ANNUAL FINANCIAL STATUS REPORTS

SECTION G. FEDERAL AWARDING AGENCY CONTACTS

G.1. NOFO POINT OF CONTACT

G.2. GRANTS.GOV APPLICANT SUPPORT

SECTION H. OTHER INFORMATION

H.1. DISCLOSURE OF INFORMATION

H.2. LIMITED USE OF DATA

H.3. PAYMENT FOR UNAUTHORIZED WORK

H.4. PLACE OF PERFORMANCE

H.5. SEAT BELT USE POLICIES AND PROGRAMS

H.6. PROTECTION OF HUMAN SUBJECTS

H.7. ENCOURAGING POLICIES TO BAN TEXT MESSAGING WHILE DRIVING

H.8. NHTSA REVIEW OF ANNOUNCEMENTS OR PUBLICATIONS

H.9. CONFLICT OF INTEREST

H.10. RURAL OPPORTUNITIES

APPENDIX A. CERTIFICATION

APPENDIX B. MMUCC SIXTH EDITION DATA ELEMENTS AND ATTRIBUTES WITH

SEDC-REQUIRED AND SEDC-RECOMMENDED ELEMENTS AND ATTRIBUTES

PROGRAM SUMMARY INFORMATION

Notice of Funding Opportunity for the State Electronic Data Collection (SEDC) Discretionary Grant

FEDERAL AGENCY NAME

U.S. Department of Transportation (DOT) National Highway Traffic Safety Administration (NHTSA)

FUNDING OPPORTUNITY TITLE

SEDC Grant

ANNOUNCEMENT TYPE

Initial Announcement

FUNDING OPPORTUNITY NUMBER

693JJ924R000025

ASSISTANCE LISTING PROGRAM NUMBER (formerly CFDA)

20.614 - National Highway Traffic Safety Administration (NHTSA) Discretionary Safety Grants

KEY DATES

NOFO Posted Date: January 31, 2024 NOFO Questions Due Date: March 1, 2024 Application Due Date: May 1, 2024

SUPPLEMENTARY INFORMATION

Each section of this notice contains information and instructions relevant to the application process for the SEDC Grant, and all Applicants should read this notice in its entirety so that they have the information needed to submit eligible and competitive applications.

Section A (Program Description) describes the Department’s goals and purpose in making awards;

Section B (Federal Award Information) contains important information about the SEDC grant including grant requirements, performance period, milestone and deliverables, etc.; Section C (Eligibility Information) describes eligible applicants, eligibility activities and cost, and cost sharing;

Section D (Application and Submission Information) describes the information and content that should be included in the submission; Section E (Application Review Information) describes how the Department will select from eligible applications; Section F (Federal Award Administration Information) describes the administrative requirements and information for the SEDC grant including reporting requirements; Section G (Federal Awarding Agency Contacts) describes the contact information for the grant; Section H (Other Information) describes all other information for this federal grant. To support Applicants through the process, the Department will provide technical assistance and resources to apply for a grant including, but not limited to, the Model Minimum Uniform Crash Criteria (MMUCC) Sixth Edition data elements and attributes, webinars, and guidance to establish the Information Exchange Package Documentation (IEPD).

There will be one webinar regarding the SEDC program. Please check grants.gov for more information.

SECTION A. PROGRAM DESCRIPTION

A.1. BACKGROUND, PURPOSE, AND OBJECTIVE

On November 15, 2021, Congress enacted the Infrastructure Investment and Jobs Act (IIJA) P.L.

117-58, also referred to as the Bipartisan Infrastructure Law (BIL). Pursuant to BIL, section 24108(d), Congress mandated that NHTSA establish the State Electronic Data Collection (SEDC) program to provide grants to States to upgrade and standardize state crash data systems to enable full electronic data transfer to NHTSA, which includes enabling electronic data collection, intrastate data sharing, and electronic data transfer to NHTSA to increase the accuracy, timeliness, and accessibility of the data, including data relating to fatalities involving vulnerable road users. This program implements the BIL SEDC grant program.

NHTSA is an operating administration of the U.S. Department of Transportation (DOT) with a mission to save lives, prevent injuries, and reduce economic costs due to road traffic crashes, through education, research, safety standards, and enforcement. NHTSA is authorized by 49 U.S.C. § 30182 and 23 U.S.C. § 403 to collect data on motor vehicle traffic crashes to conduct research, aid in the identification of safety issues and the development, implementation, and evaluation of motor vehicle and highway safety countermeasures and traffic safety programs that will reduce the severity of injury and property damage caused by motor vehicle crashes. NHTSA uses crash data to identify crash trends and characteristics, potential causes, and injury outcomes to develop strategies and countermeasures to prevent motor vehicle crashes and mitigate injuries due to motor vehicle crashes.

Through the SEDC grant program, DOT expects the expanded availability, timeliness, and accessibility of reportable crash data will create a system that will more rapidly and comprehensively identify recent changes, expand the number of insights derived from the data, and better enable analysis to inform policy and decision making. Once States have fully implemented the activities funded through this NOFO, NHTSA expects to publish crash data collected through grant recipients for public use.

NHTSA’s National Center for Statistics and Analysis (NCSA) collects and analyzes data to support NHTSA’s mission to identify traffic safety issues, support data-driven decisions and to disseminate traffic safety information to the public. NCSA manages several data collections that support agency activities such as the Fatality Analysis Reporting System (FARS), the Crash Reporting Sampling System (CRSS), the Crash Investigation Sampling System (CISS), and Non-Traffic Surveillance (NTS). NHTSA’s NCSA is the office responsible for implementing the SEDC grant program. The goal of SEDC program is to collect timely, standardized, State motor vehicle crash data electronically and produce publicly available national traffic safety information to better identify, analyze, and address traffic safety issues.

BIL Section 24108(d) established the SEDC grant program to modernize State crash data collection systems to enable electronic data collection, intrastate data sharing and electronic data transfers to NHTSA. See Section 24108(d)(3)(A). Under this program, a State is eligible to receive a grant if the State submits an application containing such information as NHTSA may require and includes a plan to implement full electronic data transfer to NHTSA by not later than five (5) years after the date on which the grant is provided. See Section 24108(d)(3)(B). A State may only use the funds provided under this grant for the costs of 1) equipment to upgrade a statewide crash data repository; 2) adoption of electronic crash reporting by law enforcement agencies; and 3) increasing alignment of State crash data with the latest Model Minimum Uniform Crash Criteria (MMUCC)1. See Section 24108(d)(3)(C).

Consistent with Section 24108, NHTSA intends to award SEDC grants to States that submit a plan that meets the requirements outlined in this NOFO, and details how it will modernize and standardize its statewide crash data collection system to enable full electronic data transfer of all crash data from a single statewide crash data repository to NHTSA. NHTSA envisions that a State participating in SEDC will have crash data collected electronically in the field by all law enforcement agencies and jurisdictions and transferred to a single, statewide crash database using a uniform, efficient approach (e.g., question or scenario-based software) that aligns, or increases alignment over a period of time, with the MMUCC Sixth Edition and the statewide database's validation rules. A State SEDC program will ensure that in addition to the data collected at the scene, the State must include data elements and attributes from the statewide crash data repository, including narratives, diagrams, and all linked and derived data. While the purpose of the SEDC program is to support electronic collection and transmission of state crash data, an acceptable state program will include the electronic transfer of all the crash data from a State’s statewide crash data repository regardless of whether the crashes are electronically reported to the statewide crash data repository. The State may also choose to transmit non-police reported crashes to NHTSA if those records are included in the statewide crash data repository, but the State must identify which records are police-reported and which are not.

NHTSA expects that a State SEDC program will run its crash data through a quality control process to confirm the accuracy of the crash data.

NHTSA’s NCSA has existing relationships with States that transfer certain crash data through NHTSA’s Electronic Data Transfer (EDT) program, which permits a State to transfer its crash data, typically from a single statewide crash data repository, directly to NHTSA. Generally, this transfer occurs on a nightly or weekly basis following State data quality control checks and acceptance by each State’s statewide crash data repository. NHTSA encourages the existing EDT States to apply

1 Please visit https://www.nhtsa.gov/traffic-records/model-minimum-uniform-crash-criteria for details about MMUCC and download a copy of MMUCC.

https://www.nhtsa.gov/traffic-records/model-minimum-uniform-crash-criteria for the SEDC grant to further improve timely data collection and standardization. Through the SEDC grant, NHTSA expects more States to send NHTSA timely electronic crash data. Specifically, NHTSA endeavors to receive all crashes from each participating State, receive more standardized data aligning to MMUCC Sixth Edition, and to publish crash data timelier to help identify traffic safety issues and support data-driven decisions.

A State shall detail in its plan how it will meet the criteria for an award and the requirement to implement full electronic data transfer to NHTSA not later than five (5) years after the date on which the grant is awarded.

BIL Section 24108(d) mandates that NHTSA shall manage and support State electronic data transfers by making State motor vehicle crash data available to the public. Accordingly, NHTSA will make the State crash data publicly available in manner that maintains the privacy of individuals consistent with Federal law.

States are encouraged to review NHTSA’s guidance and tools, to modernize a crash data collection system. The Guide to Updating State Crash Data Systems (DOT HS 813 217)2 was published to provide guidance and promote noteworthy practices to States. The Traffic Records Program Assessment Advisory, 2018 Edition (DOT HS 821 601)3 describes the ideal crash data records system. States can reference their most recent Traffic Records Program Assessment results as a reference. The Crash Data Improvement Program Guide (DOT HS 812 419)4 provides States with means to assess and measure the data quality of their crash databases. NHTSA provides technical assistance to States upon request through the Traffic Records Technical Assistance GO Teams program.

A.2. PROGRAM AUTHORITY

Infrastructure Investment and Jobs Act (IIJA) P.L. 117-58, also referred to as the Bipartisan Infrastructure Law, section 24108(d).

A.3. ADMINISTRATION PRIORITIES

Safety: The Department is committed to advancing safe, efficient transportation, including in the State Electronic Data Collection program. The National Roadway Safety Strategy (NRSS), issued January 27, 2022, commits the Department to respond to the current crisis in roadway fatalities by “taking substantial, comprehensive action to significantly reduce serious and fatal injuries on the

2 https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/813217 3 https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812601 4 https://crashstats.nhtsa.dot.gov/Api/Public/ViewPublication/812419

Nation’s roadways,” in pursuit of the goal of achieving zero roadway deaths through a Safe System Approach. (See https://www.transportation.gov/NRSS). The outcomes that are anticipated from the project funded from the State Electronic Data Collection project should align with the NRSS by improving the accuracy, timeliness, and accessibility of crash data used for decision making at the Federal, State, and local levels.

Equity: The Department seeks to award projects under the State Electronic Data Collection program that will create proportional impacts to all populations in a project area, remove transportation related disparities to all populations in a project area, and increase equitable access to project benefits, consistent with Executive Order 13985, Advancing Racial Equity and Support for Underserved Communities Through the Federal Government (86 FR 7009).

A.4. DEFINITIONS

For the purposes of this notice of funding opportunity, the following terms and definitions apply.

Term Definition

Crash Data

Crash data are the data required for the analysis and understanding of motor vehicle crashes. These data typically include the information collected on a police accident report (PAR)/police crash report (PCR) for the crash, vehicles, and persons, and may also include linked and derived data, such as driver information, roadway information, and commercial vehicle supplemental data.

Statewide Crash Data Repository

A single State electronic data repository that contains the crash data for all crashes reported by every law enforcement jurisdiction in the State.

Crash Data Quality Management Program

An official State program that applies methods or processes that determine whether crash data meet overall quality goals and defined quality criteria for individual values of each motor vehicle crash and overall crash data collection.

Electronic Crash Reporting by Law Enforcement Agencies

A method of submitting and storing crash data electronically as data elements and attributes with the ability to transfer the data to a relational database. A PDF crash report will not meet the definition of electronic crash reporting.

Full Electronic Data Transfer

The automated transfer of all crash data from a statewide crash data repository to the National Highway Traffic Safety Administration at a regular, recurring interval.

MMUCC

Alignment

A standardized measure of how a state’s crash data aligns to MMUCC at the crash data attribute level using State crash documentation to determine whether each MMUCC attribute has corresponding State attribute(s). Please refer to the methodology in the MMUCC Sixth Edition Chapter 12 “Aligning to

MMUCC.”

https://www.transportation.gov/NRSS

Information Exchange Package Documentation

(IEPD)

A collection of artifacts (e.g., documents, schemas, diagrams, sample XML, JSON) that describes from both a technical and functional perspective the requirements of a particular data exchange.

State

For the purposes of this NOFO, pursuant to P.L. 117-58§ 24108, “State” means

(i) each of the 50 States;

(ii) the District of Columbia;

(iii) the Commonwealth of Puerto Rico;

(iv) the United States Virgin Islands;

(v) Guam;

(vi) American Samoa;

(vii) the Commonwealth of the Northern Mariana Islands; and

(viii) the Secretary of the Interior, acting on behalf of an Indian Tribe.

Traffic Records Coordinating Committee

(TRCC)

State TRCCs include at least one member (including the member's home organization) that represents each of the following core safety databases: (1) crash, (2) citation or adjudication, (3) driver, (4) emergency medical services/injury surveillance system, (5) roadway, and (6) vehicle databases.

The State's TRCC should have a broad multidisciplinary membership that includes, among others, owners, operators, collectors and users of traffic records and public health and injury control data systems; highway safety, highway infrastructure, law enforcement or adjudication officials; and public health, emergency medical services (EMS), injury control, driver licensing and motor carrier agencies and organizations. This diverse membership should serve to ensure that the TRCC has the authority and ability to access and review any of the State's highway safety data and traffic records systems.

SECTION B. FEDERAL AWARD INFORMATION

B.1. AWARDING AGENCY

Department of Transportation (DOT)

National Highway Traffic Safety Administration (NHTSA)

B.2. FUNDING AND TYPE OF AWARD

Each State is eligible for one (1) award. A total of up to $350,000,000 is available to fund grants to States and is subject to the availability of funds. NHTSA will only accept one (1) application from each eligible applicant (see Section C.1, ELIGIBLE APPLICANTS). Submission of an application is not a guarantee of award. The Government’s obligations under the SEDC Grant are contingent upon the availability of appropriated funds from which payment for grant purposes can be made. No legal liability on the part of the Government for any payment may arise until funds are made available. All SEDC funds must be expended by not later than five (5) years after the date on which the grant is awarded and U.S. DOT obligates the funds.

The total number of awards and amount of funds provided to each Recipient will depend on the depth and quality of the plans submitted for consideration and the availabilities of fundings. NHTSA reserves the discretion to alter minimum and maximum award sizes upon receiving the full pool of applications and assessing the needs of the program in relation to the SEDC grant purpose and objectives described in Section A.1. This NOFO should not be construed as committing NHTSA to make any award and NHTSA reserves the right to issue a new notice of funding opportunity if necessary.

B.3. APPLICATION PERIOD

States will have a period of three (3) months to respond to the NOFO.

B.4. PERIOD OF PERFORMANCE

All work required hereunder including preparation, submission, review, and acceptance of the first transfer of data shall be completed within sixty (60) months of the effective date of the grant. An applicant may have a shorter period of performance that will depend on the work plan submitted with its application. NHTSA will review the application and determine the reasonable performance period accordingly.

B.5. MILESTONES (M) AND DELIVERABLES (D)

The following table contains Milestones and Deliverables that are general and applicable to all States.

Because the situation for each State varies, there will be State specific Milestones and Deliverables.

States should add State specific Milestones and Deliverables to the table in each State’s work plan.

All activities, milestones and deliverables in the work plan and Milestones and Deliverables table must be associated with one of the three eligible activities as specified in Section C.3 (i) to (iii).

Upon grant close-out, all deliverable items should have been submitted electronically to the Contracting Officer (CO), with an electronic copy sending to Contracting Officer’s Representative (COR) in accordance with the following schedule. Paper copies shall be submitted only upon request of the COR, Contracting Officer, or Contract Specialist.

Item

Milestones (M)/Deliverables (D): Due Date After Award

1. Kick-off Meeting (M) No later than thirty (30) days after the Effective Date of Award.

2. Quarterly Progress Report (D) Quarterly, 15th of the month following the end of the quarter

3. Quarterly Financial Report(D) Quarterly, 15th of the month following the end of the quarter

4. Annual Financial Reporting (D) Annual financial report shall be submitted using SF 425 form no later than ninety (90) days after October 1 of each year.

5. State Completion of MMUCC Alignment and Submission of Crash Data System Documents. (M & D)

Complete MMUCC alignment and submit final State crash data dictionary, crash report user manual and any other crash data user manual no later than ninety

(90) days before the Recipient starts implementation of the data elements and attributes in its system(s).

6. NHTSA Performs MMUCC Alignment Assessment (M)

NHTSA will perform MMUCC alignment assessment and provide results back to the Recipient within forty-five (45) days after item 5 above.

7. State Adjustments to Alignment Assessment (M)

The Recipient shall make necessary adjustments to ensure alignment to MMUCC as stated in its work plan based on NHTSA’s alignment assessment in item 6 above.

8. Electronic Data Transfer Testing and Transmission Plan (M & D)

The Recipient shall work with COR and NHTSA NCSA’s information technology division to develop a testing and transmission plan at least ninety (90) days before the planned implementation of full EDT.

9. Begin Electronic Data Transfer to NHTSA Adhering to the Criteria in the Work Plan (M & D).

Due on the date in the Work Plan or no later than five

(5) years after the grant is awarded, whichever is earlier.

10. Final Report (D) No later than forty-five (45) days before the end of the performance period stated in the Work Plan

11. COR reviews Final Report (M) NHTSA will review the Final Report and provide feedback no later than fifteen (15) days after receipt for the Recipient’s consideration.

12. Revised Final Report (D) If the Recipient revises the Final Report, the Recipient agrees to deliver the revised final report no later than fifteen (15) days after receiving feedback from COR.

B.6. PLACE OF DELIVERY

All deliverables shall be submitted to the following addresses specified below:

National Center for Statistics and Analysis

NSA-010

1200 New Jersey Avenue, SE Washington, DC 20590 Room: TBD Attn: TBD (COR) Email Address: TBD Telephone Number: TBD

The final report will be provided to the CO.

B.7. STATE GRANT REQUIREMENTS

As part of its work plan required in Section D, the State shall submit a plan that addresses the following requirements.

1. The State shall implement full electronic data transfer to NHTSA no later than five (5) years after the date on which the grant is awarded. In its plan, the State shall include, but is not limited to, the following:

a) Details on how the State will implement the full electronic data transfer to NHTSA on the agreed upon frequency that is no less than one (1) transfer per week. The plan shall include the intended date the transfer of crash data will commence.

b) Details on how the State will establish a statewide crash data repository if there is not one, or how the State will update the statewide crash data repository to modernize it to enable full electronic data transfer to NHTSA.

c) Details on how the transfer to NHTSA shall include crash data for each crash reported by each law enforcement agency or police jurisdiction in the State. This portion of the state’s plan shall also address the State’s methodology to transfer all crash data elements from the statewide crash data repository.

d) Details on how the State will increase (if applicable) the percentage of electronic crash reporting by law enforcement to the State’s statewide crash data repository. States are encouraged to reach one hundred (100) percent electronic crash reporting by law enforcement no later than five (5) years after the award of a grant. The State shall include the current percentage of electronic crash reporting by law enforcement and the target percentage after the SEDC grant is completed.

e) Details on how the State will improve the timely data collection of all crashes, including crashes that involves fatal injuries, by collecting crash data electronically and establishing centralized statewide repository. The State shall include how it plans to measure and monitor the improvement in timeliness of reporting and the metrics used for the monitoring and measuring.

f) Explanation of any equipment purchase necessary to achieve the goals of the SEDC program, how the sub-grantees are selected for funding, and how to measure if the equipment will meet the program’s objectives.

g) Details on how the State will work with a multi-disciplinary group (i.e., State TRCC, crash data collectors, managers, users, and other stakeholders) and a description of processes that guide updates to the crash data system.

h) Details on how the State will work with a crash data user group to guide continual improvements, such as collection, management, and use of the crash data system.

i) Details on how the State will perform data governance (e.g., develop a crash data traffic records inventory consistent with the Traffic Records Program Assessment Advisory, 2018 Edition (DOT HS 821 601)) and how it will coordinate data governance with its Traffic Records Coordinating Committee and key stakeholders.

j) Details on how the State will provide training to law enforcement agencies for any changes to its crash reporting.

k) Details on the State’s data quality control plan and process, such as how to ensure data quality at each stage of the data collection, how to ensure data integrity when data is transferred from one database to another and when data are linked, etc.

l) Details on the State’s plan for intrastate data sharing.

m) Executed certifications from Appendix A. CERTIFICATIONS.

2. The State shall transfer motor vehicle crash data following NHTSA’s EDT process for a period of no less than five (5) full calendar years of crash dates following the implementation of full EDT. In its plan, the State shall address the following.

a) How the State prior to the implementation of EDT will coordinate with the COR and NCSA to develop a testing and transmission plan for the State to send data to NHTSA.

b) Describe how the State will use NHTSA’s IEPD5 and API to implement the EDT, using either XML or JSON, one crash per API call, and one unique crash identifier per crash.

c) The State’s frequency with which it plans to send data to NHTSA.

d) The State’s process to identify whether a previously reported crash has been amended, edited, or deleted, using the unique crash identifier for the record. States are encouraged to update crash data as soon as possible consistent with their quality control processes.

e) Describe the State’s record retention plan for crash records in its statewide crash data repository.

3. The State shall increase its alignment of State crash data to the MMUCC Sixth Edition to enable full electronic data transfer to NHTSA. At a minimum, the State shall align its crash data to the SEDC-required elements and attributes located in Appendix B. NHTSA encourages States to align its crash data one hundred (100) percent to the MMUCC Sixth Edition. NHTSA also includes a list of SEDC-recommended elements in Appendix B that NHTSA encourages the States to align to if one hundred (100) percent alignment to MMUCC Sixth Edition is hard to achieve. NHTSA will prioritize States that submit a plan that reaches full alignment to the MMUCC Sixth Edition or aligns to the SEDC-recommended elements or significantly increases its alignment beyond the minimum elements and attributes listed in the SEDC-required elements and attributes. For this requirement, the State’s plan shall address:

a) The process to align its crash data to the MMUCC Sixth Edition, including the steps it will take to coordinate with its Traffic Records Coordinating Committee and key stakeholders during its alignment process and the steps necessary to obtain approval to increase alignment to the MMUCC Sixth Edition.

b) The process to provide crash data elements and attributes to NHTSA for it to assess the State’s alignment to the MMUCC Sixth Edition. The assessment process shall account for the following steps: 1) The assessment must occur prior to the State

5 Please visit https://www.nhtsa.gov/traffic-records/model-minimum-uniform-crash-criteria for more information about NHTSA’s IEPD for MMUCC Sixth Edition.

https://www.nhtsa.gov/traffic-records/model-minimum-uniform-crash-criteria implementing its changes to its crash reporting elements and attributes; 2) The State shall send the documentation to NHTSA no less than ninety (90) days before the State commences implementation of its new crash reporting elements and attributes; 3) NHTSA will provide the alignment assessment results back to the State within forty-five (45) days after receiving the documentations; and 4) The State shall adjust its data elements and attributes before implementation. The results from this assessment will be used to determine whether the State met its performance obligations under this grant.

c) The State’s process to increase crash data alignment to the MMUCC Sixth Edition. At a minimum, the State’s MMUCC alignment process shall include the identified list of SEDC-required elements and attributes in Appendix B.

d) The State’s process to integrate its statewide crash data repository with other traffic record data systems, such as roadway, driver, vehicle, citation and adjudication, and injury surveillance data systems, consistent with the MMUCC Sixth Edition, Chapter 10 “Traffic Records Data Integration”.

e) The State’s crash data alignment to MMUCC shall include data that it collects from the scene of a crash and/or through an interface with another traffic records system.

4. Administrative Requirements

a) Kick-Off Meeting

Within thirty (30) days of the grant award, the Recipient shall meet with NHTSA via video conference or similar video conference platform to introduce its project team, present its work plan, and review the milestones and deliverables. Recipients shall include its key project team members and be prepared to provide a 30–40-minute presentation describing the work plan. NHTSA COR (AA), CO, and other relevant staff will be present at the kick-off meeting.

b) Reporting

See Section F.3 REPORTING for requirements for Quarterly Progress and Financial Reports, Final Report and Annual Financial Status Reports.

B.8. PUBLIC ACCESSIBILITY OF STATE CRASH DATA

NHTSA is required to make State crash data submitted to it pursuant to the SEDC program accessible to the public. See Public Law 117–58, Section 24108(d)(4)(B). Consistent with Federal Law and U.S. Department of Transportation policy, NHTSA will withhold from public disclosure any information in State crash data that would lead to the identification of individuals involved in a motor vehicle crash (i.e., Personally Identifiable Information). All data transferred to NHTSA through full EDT shall be submitted without restrictions on its use.

SECTION C. ELIGIBILITY INFORMATION

C.1. ELIGIBLE APPLICANTS

Section 24108 of the Infrastructure Investment and Jobs Act (IIJA), also referred to as BIL, P.L. 117- 58 limits eligibility for an award to a State (see Program Summary Information, Definitions, for definition of State). Each State can submit only one (1) application. If there are multiple entities within a State that are major stakeholders or responsible for the statewide crash data repository, the State shall coordinate and appoint one (1) point of contact for the grant application. This point of contact of the State shall submit the grant application. NHTSA expects that each State will receive SEDC grant funding once.

Interested Applicants are advised that no fee or profit will be allowed under this grant program.

C.2. COST SHARING OR MATCHING

The Federal share of a SEDC grant may not exceed eighty (80) percent of total eligible activity costs.

Recipients are required to contribute a non-Federal matching share of no less than twenty (20) percent of eligible activity costs. See P.L. 117-58, Section 24108(d)(3)(D). To the extent permitted, NHTSA will accept in-kind matching as non-Federal contribution.

U.S. insular areas may not have to match funding or NHTSA may waive the match requirement depending on the amount of the Award. Pursuant to Public Law 96-205, title VI, section 601, as amended, NHTSA is required to waive any requirement for non-Federal matching funds under $200,000 for grants to four “insular areas” as defined by the statute as the U.S. Virgin Islands, Guam, American Samoa, and the Commonwealth of the Northern Mariana Islands. For non-Federal matching funds $200,000 and greater, agencies may waive the matching requirement for these four “insular areas.”

C.3. ELIGIBLE ACTIVITIES AND COSTS

As stated in BIL SEC. 24108 (d)(3), the Secretary shall provide grants to States to upgrade and standardize State crash data collection systems to enable electronic data collection, intrastate data sharing, and full electronic data transfers to the National Highway Traffic Safety Administration to increase the accuracy, timeliness, and accessibility of the data, including data relating to fatalities involving vulnerable road users. Eligible activity costs must comply with the cost principles set forth in with 2 CFR, Subpart E (i.e., 2 CFR § 200.400 to § 200.476). SEDC grant funds may be used for the costs of the following three areas:

(i) equipment to upgrade a statewide crash data repository;

(ii) adoption of electronic crash reporting by law enforcement agencies; and

(iii) increasing alignment of State crash data with the latest Model Minimum Uniform Crash

Criteria.

SECTION D. APPLICATION AND SUBMISSION INFORMATION

D.1. ADDRESS TO REQUEST APPLICATION PACKAGE

A copy of this NOFO, including all application forms, can be retrieved from www.grants.gov using the following basic search criteria:

• Keyword(s): State Electronic Data Collection

• Opportunity Number: 693JJ924R000025

• CFDA Number: 20.614

D.2. CONTENT AND FORM OF APPLICATION SUBMISSION

Each application package must include the following required OMB Standard Forms (SFs) with the required information filled in and certified assurances signed:

• Application for Federal Assistance (SF-424)

• Budget Information for Non-Construction Programs (SF-424A)

• Assurances for Non-Construction Programs (SF-424B)

• Disclosure of Lobbying Activities (SF-LLL)

These forms can be accessed by going to grants.gov/forms/forms-repository/.

In addition to the SFs above, the Applicant must provide additional information as supporting documents to the SFs.

- Technical Application: The SF-424 and its supporting documents are considered as the technical application. The SF-424 supporting document shall include the State’s plan required under Section B.7.

- Budget Execution Plan: SF-424A and its supporting documents are considered as the budget execution plan.

The application package must adhere to the following requirements:

• The technical application shall not exceed twenty-five (25) pages (not including appendices).

• The application must be in English.

• No cost/price data shall be included in the Technical Application.

http://www.grants.gov/ https://www.grants.gov/forms/forms-repository/ https://www.grants.gov/forms/forms-repository/

• All supporting documents must be written in electronic format (e.g., using MS Office or PDF) using Times New Roman twelve (12) point font, with pages that have at least one (1) inch margins.

• Adhere to the style detailed in the 7th edition, Publication Manual of the American Psychological Association (APA).

• NHTSA cannot receive email messages containing a ZIP attachment. The file will be removed, as all ZIP files are blocked. Other file types (e.g., Word, PowerPoint, PDF, etc.)

can be received.

A) TECHNICAL APPLICATION

The SF-424 and its supporting documents are considered as the technical application. The SF-424 supporting document shall include the State’s plan required under B.7. The work plan shall include the details about how the State plans to meet the grant requirements as stated in Section B.7. STATE GRANT REQUIREMENTS. NHTSA’s expectation is for an application to provide a sound work plan to create and/or update the State’s statewide crash data repository to enable electronic crash reporting, standardize crash data by increasing alignment to the MMUCC Sixth Edition, and establish a full electronic data transfer of crash data to NHTSA.

The technical application must fully describe the scope of the project and detail the program activities and associated milestones and deliverables for which funding is being requested. The work plan must provide a detailed description of how the proposed project supports NHTSA’s vision for SEDC and how the project will be implemented and managed to fulfill the goals. All activities, milestones and deliverables in the work plan must be associated with one of the three eligibility activities as specified in Section C.3 (i) to (iii). The Applicant must provide information to demonstrate the Applicant’s ability to successfully execute and implement full electronic data transfer not later than five (5) years after the date on which the grant is awarded.

The work plan must be clearly written, complete, reasonable, and include a realistic timeframe for completing program activities.

The supplemental documents must include the following:

a) Key Information

b) Narrative/Work Plan

c) Certifications

While it is not required to conform to the recommended templates below, the Applicants are strongly encouraged to provide the information using the specific structure as listed below.

1. Key Information

The application shall provide the following key information:

• Table of Contents

• Lead agency

• Primary point of contact (name, agency, title, phone, email)

• If there are multiple agencies from the State collaborating on this grant, include all participating/supporting agencies, their roles and responsibilities, and key personnel from each agency

2. Narrative/Work Plan

The Narrative section is the State’s work plan and should not be more than twenty-five (25) pages excluding appendices. The application must describe the scope of the project, to include a work plan detailing the activities, milestones, and deliverables for which funding is being requested. All activities, milestones, and deliverables in the work plan must be associated with one of the three eligible activities specified in Section C.3 and meet the purpose and requirements in Section B.7. The activities, milestones, and deliverables shall be detailed to a level for tracking in the quarterly progress report of the project. Specifically, the project narrative shall contain the following components corresponding to each of the technical evaluation factor in Section E.2 Technical Evaluation:

a) Technical Approach

The Applicant must include a work plan detailing tasks and explaining how they will establish and/or improve electronic crash data collection with the goal of implementing full electronic data transfer not later than five (5) years after the date on which the grant is awarded, including all crash data in the statewide crash data repository to NHTSA using the IEPD published by NHTSA while increasing alignment to the MMUCC Guideline. The application must include the technical approach the State will use to improve electronic data collection and transfer data to NHTSA.

b) Project Management

The Applicant must provide information to demonstrate the Applicant’s ability to successfully execute and complete the full scope of work in the application by not later than five (5) years after the date on which the grant is awarded. The Applicant must provide a timeline of milestones and deliverables for which funding is being requested. State’s specific milestones and deliverables shall be incorporated into the Milestones and Deliverable Table from Section B.5.

c) Alignment to MMUCC

Using the Excel File provided in Appendix B, the Applicant must indicate the MMUCC Sixth Edition data elements and attributes that they will collect and send to NHTSA. This should include (1) all identified SEDC-required data elements and attributes, (2) any of the identified SEDC-recommended data elements and attributes. The Applicant is encouraged to describe how it will integrate with crash data through linkage with other traffic records data systems (i.e., Roadway, Driver, Vehicle, Citation and Adjudication, and Injury Surveillance data systems).

d) Data Quality

The Applicant must include a data quality assurance plan that outlines the quality assurance measures it will develop and implement to ensure the data accuracy and integrity within the State’s systems, the correct alignments to MMUCC, and the data accuracy and integrity while transferring data to NHTSA.

e) Crash Data System Coordination

The Applicant must provide details outlining how the State’s TRCC facilitates a comprehensive and inclusive process to coordinate activities in support of motor vehicle crash data improvements in the State, such as the data governance practice, how to increase adoption of electronic crash reporting by law enforcement and provide training to law enforcement officers for updates to PAR/PCR, how to develop and maintain a motor vehicle crash data traffic records inventory, etc.

f) Administration Priorities

i. Safety—The Applicant must address how its project provides substantial safety benefits. Prior to receiving funds, all projects are expected to, at a minimum, identify and mitigate to the extent practicable any significant safety risks that could result after the project completion. The Applicant should include how its project will not negatively impact the overall safety of the traveling public.

ii. Racial Equity and Barriers to Opportunity— The Applicant must address how its project will include an equity assessment which evaluates whether a project will create proportional impacts and remove transportation related disparities to all populations in a project area. The Applicant should demonstrate how meaningful public engagement will occur throughout a project’s life cycle.

iii. Civil Rights—The applicant should demonstrate that it has a plan for compliance with civil rights obligations and nondiscrimination laws, including Title VI of the Civil Rights Act of 1964 and implementing regulations (49 CFR § 21), the Americans with

Disabilities Act (ADA), and Section 504 of the Rehabilitation Act, and accompanying regulations. This may include, as applicable, providing a Title VI plan, community participation plan, and other information about the communities that will be benefited and impacted by the project.

Refer to Section E.2 Technical Evaluation for additional content to include in the application and considerations for each of the five technical evaluation factors. Applicants are not required to follow a specific format but shall clearly address each technical evaluation factor and promote a clear discussion that will assist evaluators.

3. Certification

The Applicant shall submit, with its application, an executed certification (See Appendix A).

B) BUDGET EXECUTION PLAN

SF-424A and its supporting documents are considered as the budget execution plan. The budget execution plan shall include cost breakdowns using the Object Class Categories in SF424A Section B for each activity in the work plan. All costs in the budget execution plan shall be associated with one of the three eligibility activities and costs as specified in Section C.3. Specifically, the ‘grant program function or activities’ in the SF424A shall be listed as (i) equipment to upgrade a statewide crash data repository; (ii) adoption of electronic crash reporting by law enforcement agencies; and

(iii) increasing alignment of State crash data with the latest Model Minimum Uniform Crash Criteria.

The Applicant must provide a detailed breakdown of the project scope, proposed costs, as well as any in-kind costs, by year. This cost breakdown shall not only identify cost categories but shall also identify specific sub-categories (and associated costs). For example, Labor Costs should include labor categories, associated levels of effort, and rates; Direct Materials costs should include itemized equipment and supplies costs; Travel and transportation costs should include projected trips and number of people traveling; Subcontractor/ Sub-Recipient costs with similar detail, if known; and overhead. The Applicant must also justify each proposed cost by explaining how each cost was calculated and determined to be fair and reasonable. Finally, the Applicant should also include copies of any supporting documentation it may have (i.e., indirect cost rate agreements, etc.) as part of the budget package. Costs must be in accordance with 2 CFR Part 200, Subpart E (Cost Principles).

The Federal share of a SEDC grant may not exceed eighty (80) percent of total eligible activity costs.

Recipients are required to contribute a local matching share of no less than twenty (20) percent of eligible activity costs. Insular areas may be exempt from the matching requirements. This budget should not include any previously incurred expenses or costs to be incurred before the time of award.

DOT requires Applicants use SF-424A to provide this information. If non-Federal share funds or in-kind contributions are from entities who are not the Applicant, include commitment letters or evidence of allocated cost share as a supporting document.

Since activities may be performed with a variety of financial resources, Applicants need to fully identify all project costs and funding sources in the proposed budget. The proposed budget must identify all funding sources in sufficient detail to demonstrate that the overall objectives of the project will be met.

Grant funds, sources, and uses of project funds: The project budget should specify other funding sources to be used for this grant and show how these different funding sources are intended to be applied to each activity and present those data in dollars and percentages. The budget should identify other Federal funds the applicant is applying for, has been awarded, or intends to use. Funding sources should be grouped into three (3) categories: non-Federal, SEDC, and Other Federal with specific amounts from each funding source.

Sharing of Application Information

NHTSA may share application information within the U.S. Department of Transportation or with other Federal agencies if NHTSA or the Department determines that sharing is relevant to the respective program’s objectives.

D.3. UNIQUE ENTITY IDENTIFIER AND SYSTEM FOR AWARD

MANAGEMENT (SAM)

Each Applicant is required to:

• Be registered in SAM before submitting its application;

• Provide a valid unique entity identifier in its application; and

• Continue to maintain an active SAM registration with current information at all times during which it has an active Federal award or an application or plan under consideration by

NHTSA.

NHTSA may not make a grant award to an Applicant until the Applicant has complied with all applicable unique entity identifier and SAM requirements. If an Applicant has not fully complied with the requirements by the time NHTSA is ready to make an award, NHTSA may determine that the Applicant is not qualified to receive an award and use that determination as a basis for making a grant award to another Applicant. NHTSA will review an Applicant’s registration status to make a responsibility determination and to ensure that the Applicant is responsible, current on all federal taxes, and is not on the list of parties excluded from federal awards.

D.4. SUBMISSION DATES AND TIMES

Application Due Date and Time

Applications must be submitted no later than May 1, 2024.

Only complete packages received on or before the published due date will be considered.

Applications received after the due date will not be evaluated for consideration. Facsimile submission of proposals will not be accepted. NHTSA will only accept one (1) application from each Applicant. NHTSA will provide acknowledgments of receipt of applications via email.

Questions Due Date and Time

General administrative and programmatic questions must be directed to Chris Clarke, Contract Specialist, at NHTSAOAM@dot.gov with a copy to Reba Dyer, Contract Officer, at reba.dyer@dot.gov. To allow for sufficient time to address questions appropriately, all questions must be submitted via email no later than March 1, 2024 (one (1) month after this NOFO is published).

D.5. FUNDING RESTRICTIONS

• Funds awarded under the Grant cannot be used for any activity intended to or designed to lobby Congress or a State legislative body, or to urge a U.S., State, or local legislator to favor or oppose the…