U.S. DOT FY 2025 Phase I Pre-Solicitation Q&A

1/31/25 Update: The Pre-solicitation is now closed. Topic questions are no longer being accepted. * * *

This U.S. DOT Small Business Innovation Research (SBIR) Pre-solicitation Q&A Forum provides small businesses an opportunity to submit clarifying questions on the topics published in the U.S. DOT Fiscal Year (FY) 2025 Phase I Pre-Solicitation. Questions will be answered by the Technical Experts/Topic Authors at the U.S. DOT Operating Administrations during this period. Questions shall be limited to improving the understanding of a particular topic's requirements and should not share proposal ideas nor proprietary information.

The U.S. DOT’s FY 2025 Pre-Solicitation period is January 3, 2025, through January 31, 2025, at 5:00 pm Eastern Time (ET). Only questions posted within this period will be responded to.

How to Use the SBIR Pre-solicitation Q&A Forum:

Register : Anyone can view questions but registration is required if you wish to post a question and receive a notification when it is responded to.

To create a new account or to sign in with an existing account please click on “sign in” located at the top right of the page
A new pop-up window will open to make a selection, you can use an existing Google or Facebook account to access the site or you might select to create a new account.
If you choose to access UserVoice with an existing Google or Microsoft account, you will be required to enter your login credentials for Google or Microsoft and agree to terms of service
If you need to create a new account, click "Create an Account" underneath the password box
In the next screen, type in the e-mail and click "Verify E-mail".
Navigate to your inbox and click the link within the e-mail to verify. The link will be generated by noreply@trymagic.com
That link will be live for 20 minutes. Once that time elapses, you will have to request another one
Navigate back to UserVoice, and you will need to provide your name, a password, and agree to terms of service and storage permissions. Click "Create Account".

Search: Browse the existing questions by category to find the topic you are interested in and to see if your question has already been addressed. If you see a question, you are also interested in, you can add a vote to the question, or leave a comment.

Post: If your question has not already been posted, use the “Type your technical question” box at the bottom of the page to enter your question.

Select the research topic your question is related to from the drop-down menu that appears when you begin typing.
You may add more detail in the Description box (optional). Do NOT attach any files. The U.S. DOT shall not consider any submitted materials other than questions.
Enter your e-mail address and password.
When finished, select “Post idea.” If you registered, you will be able to track responses to your post. Please include only one question or comment per post to help us keep the forum organized.

Please note, all comments will be public information. Potential offerors shall not include in the question(s) or comment(s) any information that they do not wish to be made public. Telephone inquiries or meeting requests will not be addressed and may be removed. The U.S. DOT shall not respond to requests for advice or guidance on any offeror’s solution to any SBIR topic and shall not consider any submitted materials other than questions.

Thanks for joining our SBIR Pre-solicitation Q&A Forum.

If you experience technical difficulties, please contact us at DOTSBIR@dot.gov.

The Pre-solicitation is now closed.

Topic questions are no longer being accepted

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

List of existing tools in use, and potential access before technical content writing?

1) Can you provide current standard set of tools common across most law enforcement agencies that are currently in use ranging from software on the MDT, phone apps, weather sensors, dashcam footage databases?

2) Can we gain access to said tools prior to writing the technical content for the SBIR?

3 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Is it feasible to integrate third-party software solutions, such as AWS for voice recognition, into the proposed system?

We'll integrate geolocation, OCR, speech-to-text transcription data and conduct AI-based data validation. The system will automatically populate reports with MIRE and FARS data, ensuring accuracy and uniformity, while reducing manual input and officer exposure.

3 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Enhancing existing data collection methods vs. new data collection techniques?

Is the focus of this topic new tools (such as natural language tools) for accelerating on-site completion of reports using existing data collection methods, or new data collection methods, or both?

2 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Does the scope of this project include automated processing of historical crash data, and historical exposure data (turning volumes, etc.)?

2 votes

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Does NHTSA recommend or suggest that we collaborate with other small businesses or universities?

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
What specific system requirements do law enforcement agencies have that we must explore in our feasibility study to achieve optimum success?

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Does NHTSA have a set of standards and API specifications for sharing data with CRSS?

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
"This funding opportunity is specific to automated crash reporting software."
Hello! We noticed the following statement in a response provided to another posted question:

"Thank you for your question. This funding opportunity is specific to automated crash reporting software."

This response sparked some additional questions to us. We would love to ask for additional explanation about the government's desired mechanics and movement of data. Here is some elaboration:

ACN (Automated Crash Notification) data are contained within NEMSIS and other data systems.

However, they are not USER-mediated (indeed, they are called "automated"). Rather, the data are generated by a signal from the vehicle (i.e., OnStar) or in more recent variants, by a phone or similar (i.e., Android or iPhone crash notification, Cambridge Mobile Telematics, Samsara "harsh event notification," etc.).

By contrast, as we asked elsewhere, the topic states that one of its goals is to reduce documentation burden on Responders (specifically indicated as LEAs, but we assume that the same safety consideration applies to Fire and EMS providers):

"Completing the forms may take a significant portion of the officer’s time, which may lead to poor quality data as the officer may rush or not have enough time to complete their task. NHTSA is mindful of officer roadway exposure to secondary crashes and inaccuracies in data collection and looks for ways to reduce risk while improving data quality." (Page 26)

In older vehicles where ACN data must be collected via OBDII port or similar physical connection, there is no reasonable way for an LEA to collect such data in real-time on the road; doing so requires cables and computers. In newer vehicles, such data can "burst" from the vehicle and be captured within, for example, a NEMSIS v3 electronic patient care report using an app or other software.

THEREFORE: We wish to understand the government's goal with regards to capturing ACN and other data and using them together with (or distinct from) existing data sets like MMUCC, NEMSIS, NFIRS/NERIS, FARS, FIRST, etc.:

-- A. Is the goal to create a NEW dataset that is separate from the other data system mentioned above, and adds some additional dimension(s) of insight that they do not provide?

A2. If yes, then what insights does the government feel are MISSING from the existing data sets, such that an entirely new one is required?

--

B. Is the goal to create an integration engine that can ingest data in any/all of the formats listed mentioned, align them, provide a cross-walk for decision-making, then be able to pushing data back out to software systems that use one of the existing data standards?

--

C. If this project is LIMITED TO ACN -- as was stated in the aforementioned Q&A response -- yet ACN data already exists in NEMSIS, why are the NEMSIS data insufficient (particularly if they were to be aligned with MMUCC and others, as noted in #B above)?

--

D. IF THIS PROJECT IS LIMITED TO ACN TECHNOLOGY, then is it also geared toward firms (such as those listed above) which provide ACN software today but whose data do not currently interoperate with the other existing data standards? (Why do they not currently interoperate?)

--

E. Would it align with the topic for a company that specializes in NEMSIS data and interoperability -- and which therefore currently collects, aggregates, converts, aligns, and distributes ACN data on-demand (when available), but does not PRODUCE ACN data itself (because that is what the vehicle is responsible for generating) -- to propose to interoperate the existing data with MMUCC, FIRST, FARS, etc.?

Thank you so much!
Hello! We noticed the following statement in a response provided to another posted question:

"Thank you for your question. This funding opportunity is specific to automated crash reporting software."

This response sparked some additional questions to us. We would love to ask for additional explanation about the government's desired mechanics and movement of data. Here is some elaboration:

ACN (Automated Crash Notification) data are contained within NEMSIS and other data systems.

However, they are not USER-mediated (indeed, they are called "automated"). Rather, the data are generated by a signal from the vehicle (i.e., OnStar) or in more recent variants, by…
1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
What existing integration approaches are currently in use at NHTSA CRSS?

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
1. What are some significant data types that crash data collection and analysis may require to benefit modernized crash report sampling syst

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
What are some significant data types that crash data collection and analysis may require to benefit modernized crash report sampling syst

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Using / integrating existing standards into one place only -- or creating a new overarching "superset" that feeds into other systems?
The topic references myriad datasets and associated tools, including:

MMUCC

FIRST

FARS

NEMSIS (by reference, since it is contained within MMUCC)

Trauma registry (by reference, since it is contained within MMUCC)

NFIRS/NERIS (when fire services respond to crashes)

EMS UUID (by reference, since it is contained within MMUCC)

Is the goal of this topic to create a "master" dataset that can overarch all of the above (and possibly others), superseding them with the goal of "enabling LEAs to increase accuracy, timeliness, completeness, and uniformity of crash reports through the reduction of missing data and coding errors" -- presumably through fast and efficient charting in the field, at the crash scene? (The reference to speed and efficiency is drawn from the goal to "reduce police officer exposure to secondary crashes.") (PG. 26)

OR

Is the goal NOT to create a new dataset but to crosswalk and synthesize several EXISTING datasets, turning them into "one report that rules them all"?

Begging forgiveness for my Lord of the Rings reference (!!!): is the goal a landing point for data from several different data sets and systems that operate within separate spheres, so they can come together and form a single picture of the scene and situation?

OR

A single "master" software that can capture data that has a landing point within each of the other data sets, then distribute the approach data across those datasets to their respective landing points (e.g., to NEMSIS, or NERIS, or FARS, or FIRST, etc., however is appropriate)?

(Or both?)
The topic references myriad datasets and associated tools, including:

MMUCC

FIRST

FARS

NEMSIS (by reference, since it is contained within MMUCC)

Trauma registry (by reference, since it is contained within MMUCC)

NFIRS/NERIS (when fire services respond to crashes)

EMS UUID (by reference, since it is contained within MMUCC)

Is the goal of this topic to create a "master" dataset that can overarch all of the above (and possibly others), superseding them with the goal of "enabling LEAs to increase accuracy, timeliness, completeness, and uniformity of crash reports through the reduction of missing data and coding errors" -- presumably through fast…
1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
New data CREATION software vs. INTEGRATION software (that incorporates many existing datasets)?

In reviewing this topic area in detail, we have one key question: There is reference, both explicitly and implicitly, to several separate federal datasets.

(By implicit, we mean that -- for example -- the MMUCC 6th Edition guidelines specifically reference NEMSIS several times, so even though this topic does not reference NEMSIS, it is clearly a part of the process. In many communities, fire services also respond to roadway crashes, and the new US Fire Administration National Emergency Response Information System (NERIS) standard references NEMSIS as well, so there is a demonstrable overlap among the standards used by various responding agency types.)

There are references within the topic to "must collect and integrate...data elements at the crash, vehicle, and person level," etc. But in other places within the topic, it says "this project aims to develop software with automation features and capabilities that integrates into current crash report software."

In short, the topic acknowledges that there are SEVERAL different software systems currently used by LEAs -- and other Responders to crash scenes, including Fire and EMS, plus trauma registries, each of which uses separate software. There are concurrent / parallel federal initiatives ongoing now to integrate and cross-talk those software systems. The topic acknowledges this as well: "gather more robust data, crash reports should be accurate, complete, uniform, timely, accessible to users of data, and in a format that supports data integration with other data and systems."

That said, is the goal of this topic to create a data COLLECTION software (i.e., primary or new data that will be first entered into the software system that results from this topic) -- or is the goal to create INTEGRATION software that pulls together lots of existing data into a unified repository (for lack of a better term) where it can be cross-walked, collated and evaluated side-by-side for decision-making?

In reviewing this topic area in detail, we have one key question: There is reference, both explicitly and implicitly, to several separate federal datasets.

(By implicit, we mean that -- for example -- the MMUCC 6th Edition guidelines specifically reference NEMSIS several times, so even though this topic does not reference NEMSIS, it is clearly a part of the process. In many communities, fire services also respond to roadway crashes, and the new US Fire Administration National Emergency Response Information System (NERIS) standard references NEMSIS as well, so there is a demonstrable overlap among the standards used by various responding…

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Please clarify the meaning of the word "device" on Expected Outcome #3
For 25-NH1 (PAGE 28) -- Phase 1 Outcome #3 says: "Proof of Concept paper including a testing plan to determine, at a minimum, the device’s sensitivity, validity, and reliability with a sufficient sample size for meaningful analyses...." But this is the only reference to a "device" in 25-NH1. Throughout this topic area, there are references to "software." Can you please clarify if:

Is the word "device" actually a typo (i.e., should it say "software" instead) or is it intentional?

IF IT IS INTENTIONAL: Does this "device" refer to either computer hardware to run the software, or potentially associated hardware devices (such as license plate readers), cameras, GPS / geolocation devices, or something else?

Thank you!
For 25-NH1 (PAGE 28) -- Phase 1 Outcome #3 says: "Proof of Concept paper including a testing plan to determine, at a minimum, the device’s sensitivity, validity, and reliability with a sufficient sample size for meaningful analyses...." But this is the only reference to a "device" in 25-NH1. Throughout this topic area, there are references to "software." Can you please clarify if:

Is the word "device" actually a typo (i.e., should it say "software" instead) or is it intentional?

IF IT IS INTENTIONAL: Does this "device" refer to either computer hardware to run the software, or potentially associated hardware devices…
1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Who is this topic intended to support as an end user?

Is this to support police at the scene of a crash, or post-scene report generation, or all/other facets of crash scene documentation?

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Standards may be referenced for PII handling and application usage for this service development?

Personally Identifiable information (PII) and Public Health information (PHI) are to follow the same protocols as LEA applications.

As part of the LEA marketplace, shall we just reference with good intention the PHI standard or coding practice guidance?

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Will this opportunity fund AI and Traffic Managment Technology?

We are developing Solar Powered AI Traffic Lights, to reduce Energy Use DRAMATICALLY at all Nationwide (worldwide) USA Traffic Intersections and increase driver safety DRAMATICALLY. READY TO INSTALL, just need the orders and additional funding!:)

ROBERT MOORE
JOHNAVATAR.com
Email: JohnAvatar@JohnAvatar.com

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →
Will this opportunity fund AI and Traffic Managment Technology?

We are developing Solar Powered AI Traffic Lights, to reduce Energy Use DRAMATICALLY at all Nationwide (worldwide) USA Traffic Intersections and increase driver safety DRAMATICALLY. READY TO INSTALL, just need the orders and additional funding!:)

ROBERT MOORE
JOHNAVATAR.com
Email: JohnAvatar@JohnAvatar.com

1 vote

We're glad you're here
Please sign in to leave feedback

Signed in as (Sign out)

Close

Close

We’ll send you updates on this idea

1 comment · 25-NH1: Automated Police Crash Report Data Collection and Management Software · Delete… · Admin →

U.S. DOT FY 2025 Phase I Pre-Solicitation Q&A

The Pre-solicitation is now closed.

List of existing tools in use, and potential access before technical content writing?

Is it feasible to integrate third-party software solutions, such as AWS for voice recognition, into the proposed system?

Enhancing existing data collection methods vs. new data collection techniques?

Does the scope of this project include automated processing of historical crash data, and historical exposure data (turning volumes, etc.)?

Does NHTSA recommend or suggest that we collaborate with other small businesses or universities?

What specific system requirements do law enforcement agencies have that we must explore in our feasibility study to achieve optimum success?

Does NHTSA have a set of standards and API specifications for sharing data with CRSS?

"This funding opportunity is specific to automated crash reporting software."

What existing integration approaches are currently in use at NHTSA CRSS?

1. What are some significant data types that crash data collection and analysis may require to benefit modernized crash report sampling syst

What are some significant data types that crash data collection and analysis may require to benefit modernized crash report sampling syst

Using / integrating existing standards into one place only -- or creating a new overarching "superset" that feeds into other systems?

New data CREATION software vs. INTEGRATION software (that incorporates many existing datasets)?

Please clarify the meaning of the word "device" on Expected Outcome #3

Who is this topic intended to support as an end user?

Standards may be referenced for PII handling and application usage for this service development?

Will this opportunity fund AI and Traffic Managment Technology?

Will this opportunity fund AI and Traffic Managment Technology?

Feedback