Part of the DoW SBIR/STTR FY27 Release 2 topic list. Browse all 83 topics by industry or service.
Topic DON27BZ02-NV006 from the DoW SBIR 2027 BAA, Release 2. Pre-release now; proposals due January 6, 2027, 12:00 PM ET.
Quick answer
DON27BZ02-NV006 is a Department of the Navy SBIR topic seeking a ruggedized, field-deployable device that rapidly and non-destructively extracts telematics and infotainment data from vehicles for Marine Corps and Joint tactical site exploitation. It follows a standard Phase I feasibility and Phase II prototype structure. Proposals are due January 6, 2027, 12:00 PM ET.
Solicitation at a glance
- Topic number: DON27BZ02-NV006
- Official title: Mobile Vehicle Forensics
- Agency: Department of the Navy
- Program: SBIR (DoW SBIR 2027 BAA, Release 2)
- Award type: Phase I (see topic text for Phase II)
- Award amount: Phase I base up to $200,000 plus an option up to $115,000. Source: Navy Release 2 instructions in DSIP.
- CMMC level: Level 2 (Self)
- ITAR: No
- Technology areas: None
- Pre-release (direct TPOC contact allowed): November 4 to December 2, 2026, 8:00 AM ET
- Opens in DSIP: December 2, 2026, 8:00 AM ET
- Proposals due: January 6, 2027, 12:00 PM ET
- Official source: DSIP Topics app (search DON27BZ02-NV006)
BW&CO's take
What the Department of the Navy wants
Modern vehicles store GPS track logs, navigation history, paired Bluetooth devices, Wi-Fi caches, and phone pairings, but current forensic tools are lab-oriented, limited to narrow manufacturer subsets, and often require dashboard disassembly. The Navy wants a low-SWaP, ruggedized, all-in-one device that connects through OBD-II or USB, automatically profiles the vehicle's make, model, year, and digital architecture, and runs an automated extraction that preserves forensic integrity. The threshold is extracting high-priority telematics and paired-device logs in under 15 minutes with verifiable accuracy; the objective is a pocket-sized plug-and-play device that extracts a comprehensive data set in under 5 minutes. Phase II delivers a field-ready prototype tested against representative vehicles.
Who is a good fit
- Existing vehicle or mobile device forensics tooling that extracts IVI, ECU, or telematics data
- Experience handling proprietary IVI and ECU software architectures and inconsistent file structures across multiple manufacturers
- Embedded hardware design for rugged, low-SWaP field devices using OBD-II or USB interfaces
- Forensic data integrity practices, such as validated extraction and comparison against independently collected test data
Watch-outs
- The approach must be non-invasive with no component disassembly, yet still cover a broad registry of makes, model years, and international manufacturers. Phase I explicitly prioritizes universal applicability and avoiding dependencies on specific hardware teardowns.
- Extraction speed and accuracy are explicit metrics: under 15 minutes threshold, under 5 minutes objective, with accuracy verified against separately collected test data.
- Phase II requires demonstration in an operationally relevant environment against representative vehicle targets, plus user manuals and a manufacturing and transition plan.
- The topic metadata lists CMMC Level 2 (Self). It is not marked ITAR-restricted in the topic metadata.
Think your company fits DON27BZ02-NV006? Talk with BW&CO before the January 6 deadline.
Plan Your DON27BZ02-NV006 Submission
Official topic text (verbatim from DSIP)
The text in this section is copied word for word from the official DSIP topic as published on November 4, 2026. DSIP is the official source and topics can be amended. Always confirm the current version at dodsbirsttr.mil before you submit. Our commentary above is BW&CO's interpretation, not Government guidance.
Title
Mobile Vehicle Forensics
Objective
Design, develop, and demonstrate a ruggedized, field-deployable vehicle forensics device capable of non-destructive, rapid data triage and extraction.
Description
Operational Need & Gap: During tactical site exploitation (TSE), Marine Corps and Joint operators require immediate, field-deployable hardware and software to recognize, preserve, and collect materials of forensic value. While multi-purpose forensic kits exist to process traditional materials, a critical intelligence gap remains regarding vehicle-derived data. Modern vehicles function as mobile data hubs featuring advanced navigation, localized track logs, and cached external device connections. Exploiting this telematics and informatics data is vital for generating actionable intelligence, mapping networks, and establishing identity dominance.
The Problem (Technological Fragmentation): The primary barrier to tactical vehicle exploitation is severe technological fragmentation. Current vehicle forensic solutions are often designed for controlled laboratory environments. Because In-Vehicle Infotainment (IVI) systems and Electronic Control Units (ECUs) rely on proprietary software architectures and inconsistent file structures, existing tools are often restricted to narrow manufacturer subsets. Consequently, field operators may be forced to perform invasive, time-consuming physical disassembly of the vehicle dashboard—a method that is untenable in many field environments.
Scope of Effort: This SBIR topic seeks innovative proposals to develop a low-SWaP (Size, Weight, and Power), ruggedized, all-in-one device that automates the forensic exploitation of vehicle data systems. The system must interface via standard external access points (e.g., On-Board Diagnostic [OBD-II] ports or Universal Serial Bus [USB]); automatically profile the vehicle’s make, model, year, and digital architecture; and execute an automated script to extract and structure data. Crucially, these features must be achieved through a non-invasive approach requiring no component disassembly, while maintaining strict forensic data integrity and verifiable accuracy.
The system must seamlessly interface with a broad registry of modern commercial and civilian vehicles across diverse model years, makes, and international manufacturers. Specifically, the device must extract and normalize data from disparate telematics systems (e.g., embedded GPS, localized track logs) and informatics modules (e.g., infotainment systems, paired Bluetooth logs, Wi-Fi cache, and cellular device pairings) without requiring laboratory-grade component disassembly.
Performance Goals:
- Threshold (Minimum): Demonstrate compatibility with representative samples of common vehicles; extract high-priority telematics (i.e., GPS, route history) and informatics (paired device logs) in under 15 minutes with verifiable accuracy (i.e., comparison with test data collected separately); packaged in a portable, field-ruggedized kit.
- Objective (Ideal): A pocket-sized, plug-and-play device that requires minimal operator training; demonstrates a modular path to broad vehicle compatibility; and extracts a comprehensive forensic data set in under 5 minutes via an intuitive, automated interface.
Phase I
Develop a technical approach and assess the feasibility of a mobile, software-intelligent vehicle forensics capability that enables rapid data extraction from vehicle telematics (e.g., GPS, navigation logs) and infotainment systems (e.g., paired Bluetooth devices, call histories) and prioritizes universal applicability across diverse vehicle head units, makes, and models, avoiding dependencies on specific hardware teardowns.
Required Phase I deliverables include:
- A comprehensive feasibility study and initial system design architecture.
- An assessment of projected data extraction speeds, performance metrics, and technical limitations.
- A detailed Phase II development plan mapping out performance goals, key technical milestones, and risk mitigation strategies.
Phase II
Develop, demonstrate, and validate a functional, field-ready prototype based on the feasibility concepts established in Phase I. Focus on expanding compatibility across a broader registry of vehicle makes, models, and head unit architectures, while increasing the depth and fidelity of extracted telematics and informatics data. Ensure that the prototype is ruggedized or packaged appropriately for expeditionary testing.
Required Phase II deliverables include:
- A fully functional prototype vehicle forensics tool (software, hardware, or hybrid) ready for Government evaluation.
- Demonstrations of the tool’s capability in an operationally relevant environment against representative vehicle targets.
- Complete technical documentation, including system architecture, user operating manuals, and finalized performance data metrics.
- A commercialization and transition plan detailing manufacturing viability and scaling strategies for military integration.
Phase III Dual Use Applications
Upon successful completion of Phase II, support technology transition into a Phase III acquisition pathway for integration into the Forensics Dominance System – Marine Corps (FDS-MC) tactical site exploitation kits. Given the Joint requirement, position this rapid field-extraction capability for immediate transition to U.S. Special Operations Command (USSOCOM) exploitation programs and other Department of War service forensic intelligence elements.
In the commercial sector, this software-intelligent tool has direct dual-use applicability for federal, state, and local civilian law enforcement agencies by significantly modernizing digital forensics units through enabling roadside or scene-of-crime vehicle data extraction, thus bypassing extensive laboratory backlogs. Additionally, the capability will serve private sector markets, including automotive insurance fraud investigators, crash reconstruction experts, and corporate cybersecurity firms analyzing fleet vehicle telematics breaches.
References
“iVe Vehicle and System Support.” Berla Corp., 2024. https://berla.co
“CAN Bus Explained - A Simple Intro.” CSS Electroinics, 2024. https://www.csselectronics.com/pages/can-bus-simple-intro-tutorial
“NIST Special Publication 800-101 Revision 1, Guidelines on Mobile Device Forensics.” National Institute of Standards and Technology, 2014. https://csrc.nist.gov/publications/detail/sp/800-101/rev-1/final
“Rusolut Vehicle Data Reconstructor.” Rusolut, 2024. https://rusolut.com/vehicle-data-recovery/ https://rusolut.com/vehicle-data-reconstructor/
“United States Special Operations Command (USSOCOM) Tactical Forensics Event (TFE) 21.1, 2025”.
https://www.vulcan-sof.com/login/ng2/collection/a1e8fd06-ac2a-4fc6-bfb8-b1fcbe101b1c
Keywords
Vehicle; forensics; information; collection; telematics; informatics
Frequently asked questions
What is DON27BZ02-NV006?
It is a Department of the Navy SBIR topic to design, develop, and demonstrate a ruggedized, field-deployable vehicle forensics device capable of non-destructive, rapid data triage and extraction from vehicle telematics and infotainment systems.
When is DON27BZ02-NV006 due?
Proposals are due January 6, 2027, 12:00 PM ET. DSIP pre-release began November 4, 2026, and direct contact with the topic authors is allowed only until the topic opens on December 2, 2026, 8:00 AM ET.
Is this a Phase I or Direct-to-Phase II topic?
The topic describes a Phase I effort covering a feasibility study, initial system architecture, projected extraction speeds, and a Phase II plan, followed by a Phase II field-ready prototype. It is not labeled Direct-to-Phase II.
What data does the device need to extract?
It must extract and normalize telematics data such as embedded GPS and localized track logs, and informatics data such as infotainment records, paired Bluetooth logs, Wi-Fi cache, and cellular device pairings, through standard access points like OBD-II or USB.