ONR - Open Topic for Low-Cost Heads Up Displays (HUDs) for Virtual & Augmented Reality (VR/AR)

Navy CSO Open Topic: DON27BX01-NP001
Pre-release Oct 7, 2026   Opens to accept proposals Oct 28, 2026   Closes Nov 25, 2026 12:00pm ET       [ View Q&A ]

DON27BX01-NP001 TITLE: ONR - Open Topic for Low-Cost Heads Up Displays (HUDs) for Virtual & Augmented Reality (VR/AR)

COMPONENT TECHNOLOGY PRIORITY AREA(S): Human-Machine Interfaces;Integrated Sensing and Cyber

PROJECTED CMMC LEVEL REQUIREMENT: Level 2 (Self)

OBJECTIVE: Develop a commercial technology to address Navy and USMC gaps regarding low-cost, NDAA-compliant heads-up displays (HUDs) with on-board 6 degrees-of-freedom (6DOF) tracking.

DESCRIPTION: ONR requests proposals for existing technology demonstration platforms, prototypes, and commercial products that provide domestically-sourced, low-cost HUDs) for first-person view (FPV) drone pilots, and augmented reality (AR) capabilities for Forward Observers (FOs) and Joint Terminal Air Controllers (JTACs). For Phase I awardees, ONR will provide operational context and technical thresholds against which technologies will be assessed and provide feedback and guidance on enhancements to align with warfighting objectives.

The proposing small business should have an existing hardware solution that meets one or both technical areas listed below:

- HUD for FPV pilot operations including integrated display, signal inputs, and locations for mounting organic FPV equipment including antennas, transmitters, and power supplies

- Integrated HUD with native 6DOF tracking, using on-board sensors and modalities (cameras, Inertial Measurement or Measuring Units [IMUs], magnetometers), compute, and power (battery)

PHASE I: The DON is planning to issue multiple Phase I awards for this topic but reserves the right to issue no awards. Each Phase I proposal must include a Base and Option period of performance. The Phase I Base must have a period of performance of six (6) months at a cost not to exceed $200,000. The Phase I Option must have a period of performance of six (6) months at a cost not to exceed $115,000. Phase I feasibility will describe the existing proposed technology, existing DON system(s) to improve/replace, expected improvements to existing capabilities, and a transition approach to both the DON system and commercial sector. Phase I results will be detailed in a final technical report (Final Report) and presented during the project outbrief one month prior to Final Report submission.

Phase I deliverables include:

- Kick-Off Briefing, due 15 days from start of Base award

- Progress Report, due 90 days from start of Base award

- Final Report, due 180 days from start of Base award

- Quad Chart, due 180 days from start of Base award

- Initial Phase II Proposal, due 180 days from start of Base award

The Phase I Option, if exercised, will include the initial design specifications and capabilities description to build and deliver a prototype solution in Phase II.

PHASE II: All Phase I awardees may submit an Initial Phase II proposal for evaluation and selection. The evaluation criteria for Phase II are the same as Phase I (as stated in this CSO). The Phase I Final Report and Initial Phase II Proposal will be used to evaluate the small business’s potential to fill a capability gap, improve performance, or modernize an existing capability for DON and transition the technology to Phase III. Details on the due date, content, and submission requirements of the Initial Phase II Proposal will be provided by the awarding SYSCOM either in the Phase I contract or by subsequent notification.

The scope of the Phase II effort will be specific to each project but is generally expected to include development of a functional prototype to demonstrate the capability, development of a transition plan addressing production and the fielding approach (including updated logistics and safety consideration) and further commercialization (non-DoW).

PHASE III DUAL USE APPLICATIONS: Support incorporation of low-cost HUDs into the Fires programs of record within the USMC for FOs, JTACs, and FPV drone attack operators.

Since the Navy is seeking commercial technologies (e.g., FPV), these technologies already have existing commercial applications.

REFERENCES:

  1. Song, Yan, et al. "A Review of Intelligent Vision Enhancement Technology for Battlefield." Computational Intelligence and Neuroscience, vol. 2022, 2022, pp. 1-15. ProQuest, doi:10.1155/2022/6071477
  2. "Motion-Tracking for Augmented and Mixed Reality: How Good is Good Enough?" Proceedings of SPIE, vol. 12125, 2022, pp. 121250D. SPIE Digital Library, doi:10.1117/12.2616864

KEYWORDS: Heads Up Display, Augmented Reality, Human-Machine Interface, First Person Drone, Virtual Reality, Mixed Reality

end of topic -->

Topic Q & A

11/4/26  Q. What level of 6DOF is required? Are you looking for a solution that provides head pose only (3DOF accel + 3DOF gyro) or is a camera-based solution required?
   A. Based on prior testing, solutions that leverage camera-based 6DOF with an accuracy of approximately 1m is preferred. 3DOF + 3DOF gyroscopic based solutions have historically underperformed for the intended use-cases.
11/3/26  Q. 1. Is the 6DOF capability required at time of submission, or would a proposed approach that achieves 6DOF during the Phase I period of performance be acceptable?

2. Is a monocular or binocular display configuration desired (i.e., augmented overlay presented in one eye versus both eyes) or are both configurations acceptable?
   A. 1. A basic 6DOF capability should already exist for demonstration purposes at the time of proposal, with the expectation that additional development work will need to occur to configure and tune performance for specific USMC use cases.

2. Bi-ocular configurations (displays in both eyes) are the primary intent for development, specifically a glasses / head-worn glasses / head-worn frame with lenses that does not require the hands to operate.
11/2/26  Q. I have one question: does the topic envision, or require, a mapping and navigation capability as part of the solution (i.e., on-board 3D mapping / localization beyond 6DOF head tracking)?

I ask because, in our experience, without such a capability AR/VR headsets are of limited use for most operational use cases — a display with 6DOF tracking alone cannot place information in the real environment, support navigation, or share spatial context between users.
   A. The 6DOF solution should be capable of doing both localized tracking, as well as global referencing using geo-registration with approved terrain datasets. Approved geospatial datasets will be provided to awardees upon commencement.
10/30/26  Q. Request for Clarification — DON27BX01-NP001
We would appreciate ONR's clarification of the following requirements to assist prospective offerors in preparing responsive Phase I proposals.
1. Existing Hardware Requirement for Phase I
The solicitation requires an existing hardware solution and describes Phase I as a feasibility assessment.
Does ONR require the complete proposed HUD system to be fully integrated and operational at the time of Phase I proposal submission, or may Phase I begin with existing functional hardware that requires additional integration and development to meet the intended DON operational requirements?

2. Phase I Base, Phase I Option, and Phase II Development Requirements
a) Phase I Base — 6 Months ($200,000)
Does ONR expect the Phase I Base to focus primarily on establishing technical feasibility using existing functional HUD hardware, identifying applicable DON systems, evaluating expected performance improvements, and developing a preliminary transition strategy?
Are hardware integration, testing, or prototype demonstrations required during the Base period, or may these activities be addressed during subsequent development periods?
b) Phase I Option — 6 Months ($115,000)
What additional technical objectives, milestones, and deliverables does ONR expect during the Phase I Option beyond those completed during the Base period?
Specifically, does ONR expect additional hardware integration, testing, or prototype demonstrations, or may the Option focus on further feasibility validation and refinement of the proposed technical approach? c) Phase II — Subsequent Development
Would ONR consider completion of an integrated AR HUD prototype, including additional imaging capabilities, full system integration, performance testing, and operational demonstrations, appropriate Phase II activities following successful completion of Phase I?

3. Existing DON Systems
Are there particular Navy or Marine Corps FPV, Forward Observer, or JTAC display systems that ONR recommends proposers consider as potential candidates for improvement or replacement when developing the required Phase I feasibility and transition assessment?

4. Night-Vision-Enhanced AR
Would ONR consider the integration of night-vision imaging into an existing AR HUD relevant to the intended operational applications, particularly where the combined system could support both daytime and nighttime operations?

5. Performance Evaluation Requirements

Are there established minimum technical requirements, preferred performance thresholds, or evaluation criteria for the following HUD characteristics that can be provided as targets ?
  • Field of view (FoV)
  • Optical transparency
  • Display resolution
  • Depth of field
  • Outdoor display brightness
  • 6DOF tracking accuracy
  • System latency
  • System weight
  • Power consumption
  • Operational battery endurance
If specific thresholds have not yet been established, should proposers identify and justify their own performance targets during Phase I feasibility assessments, with final operational requirements to be determined through build and ONR evaluation?

6. Form Factor
Is a “visor form factor” or “eyeglass form factor” acceptable or highly desired.
   A. 1. Vendors may Phase I begin with existing functional hardware that requires additional integration and development to meet the intended DON operational requirements. The intent is to gather details about the off-the-shelf hardware landscape to support native 6DOF tracking.

2. a. Yes.
  1. SBIR awardees should plan to provide evidence that demonstrates prototype solution capability to meet the desired functionality for the program, but do not need to plan travel to a test location to perform live demonstrations. Laboratory or bench top test results with video or virtual demonstrations will be sufficient.
  2. Vendors are able to propose appropriate development, testing, integration, and planning activities over a possible Phase I Option period that aligns with their technology capabilities and design objectives. ONR cannot provide blanket guidance for what activities would be appropriate for a potential Phase I option, but the listed activities would likely constitute an appropriate set of activities required to achieve the desired end state of performant 6DOF tracking with off-the-shelf components.
  3. Yes.

3. ONR does not wish to specify the specific technical solution for the topic.

4. This capability is not a requirement in the call, though may be included in a proposed solution.

5. There are no specific price, FoV, diopter, resolution, brightness, latency, weight, endurance, or tracking accuracy threshold performance criteria parameters required for topic call submission or consideration. As described in the topic call, operational context and technical thresholds will be provided for Phase I awardees. For accuracy, in ambient sunlit conditions, 1m local and global geopostioning accuracy, with drift <1m at >200m would be a good target. Generally, proposers are encouraged to identify and justify their own performance targets.

6. Eyeglass form factor is preferred for FO/JTAC community, however vendors are welcome to propose other form factors best matched to their technical solution.
10/26/26  Q. The topic says the firm should have an existing hardware solution. Does a self-contained HUD meet that expectation if the proposing small business builds it from commercially available modules, such as the compute module, display and sensors, inside its own housing and with its own electronics and software?
   A. Yes, a self-contained HUD that meets the described use-cases with vendor-developed software would meet the requirements for consideration under this SBIR program. The components should be all off-the-shelf available though.
10/12/26  Q. Form factor and optics:
1. Are monocular and binocular configurations both acceptable for technical area 1 and technical area 2? Is either configuration preferred in evaluation?
2. For technical area 2, is an optical see-through display required? Would a video pass-through display, or a monocular display that does not overlay the user’s direct view, be considered?
3. Is the HUD expected to be helmet-mounted and compatible with fielded helmets and night vision devices, or is a standalone head-mounted goggle acceptable?
4. Are there brightness requirements for daylight use, and is night vision compatibility expected?

AR software scope:
5. Is the offeror expected to provide AR application software (for example, geo-registered target or friendly-force symbology, or ATAK integration), or is the expected product a HUD platform that exposes display and 6DOF pose to Government software?
6. Does “on-board compute” require mission applications to run on the HUD, or is an architecture acceptable where tracking runs on the HUD and outputs pose to a tethered end user device running ATAK?
7. Is there a required or preferred operating system or software interface, such as Android to host ATAK?

Tracking:
8. Is the 6DOF requirement satisfied by local tracking (head pose relative to the user’s surroundings), or is geo-registration with absolute heading and position expected for FO and JTAC use? If geo-registration is expected, should GNSS be on the HUD or supplied by a connected device?
9. Is operation in GPS-denied or magnetically disturbed environments within scope?

Technical area 1 interfaces:
10. Should the HUD include an integrated video receiver, or provide signal inputs and mounting for the unit’s own receiver? Which video link types (analog, specific digital systems) should the inputs support?

Thresholds and cost:
11. Are there initial threshold or objective values for display resolution, field of view, brightness, tracking latency and drift, weight, and battery life that proposals should address, or will these be provided only after award?
12. Is there a unit cost target for “low-cost,” and at what production quantity?

Sourcing and compliance:

13. Does “domestically-sourced” require U.S.-made displays, sensors, and compute, or does it apply to U.S. final assembly using NDAA-compliant components from non-covered countries?
14. Which provisions or lists define NDAA compliance for this topic, for example Section 848 of the FY2020 NDAA or the Blue UAS Framework?
   A. Form factor and optics

1.Binoculars configurations are the primary intent for development, specifically a glasses / head-worn a glasses / head-worn form factor that does not require the hands to operate is preferred.
2. Optical see-through is not required, but is advantageous for some end-user communities based on prior government testing. Video see-through is an option if lag/latency are not issues, and resolution of objects at 2-3km is discernable by the human eye.
3. Either option is acceptable, but standalone HMD is more advantageous based on prior government testing.
4. As stated in the topic description, ONR will provide operational context and technical thresholds against which technologies will be assessed and provide feedback and guidance on enhancements to align with warfighting objectives for Phase I awardees. This is primarily intended for day operation.

AR software scope:

5. Yes, ONR will provide AR application software (XRTAK) to receive target and other entity information from the tactical handset that can be displayed in the AR glasses. However the focus and primary development is a hardware product and 6DOF pose information; however, vendors are allowed to include tracking software as a component of the proposal, but shouldn’t be the focus for proposed work.
6. Solutions may run tracking software for mission applications on a tethered device.
7. No required software is indicated for Phase I, but OpenXR/ XRTAK ATAK / Android integration provides value for proposed solutions.

Tracking:

8. Local 6DOF tracking is the primary requirement, though global geo-registered 6DOF would be an important component that allows users to move freely about their environment. The GPS can be on-board or supplied via a connected device (ie ATAK).
9. Yes

Technical area 1 interfaces:

10. HMD needs to be able to display digital full motion video via digital inputs from the ATAK device, as well as rendering of 2525 symbology overlaid the terrain

Thresholds and cost:

11. ONR will provide operational context and technical thresholds against which technologies will be assessed and provide feedback and guidance on enhancements to align with warfighting objectives for Phase I awardees.
12. Ideal solutions would conform to the order of magnitude for comparable COTS HUD solutions. We do expect that the proposal will provide a rough estimate for cost and as well as the production/manufacturing plan. Components should be NDAA-compliant, or be eligible for compliance. They need not be domestically sourced necessarily.

Sourcing and compliance:

13. Ideal solutions meet NDAA compliant component and assembly within an approved/approvable production pipeline. Sensors, components, and compute assets should conform to NDAA/TAA compliance definitions, or be eligible to become NDAA-compliant
14. The intent is to develop approvable hardware based on a compliant pipeline. Title VIII, Subtitles D and E of the NDAA FY26, and Blue UAS Framework are appropriate goals – however, based on potential development and transition pathways additional regulatory and policy considerations may be identified during the program. The Defense Contract Management Authority (DCMA) maintains the list of compliant parts, as well as the process for certifying those are currently not on the list, but are eligible.
10/12/26  Q. 1. What duration of operation are the batteries expected to support?

2. This is clearly a military intended system - at what level is MilSpec qualification anticipated while still meeting "low cost" and "commercial applications"? for example :Full Mil-Std-810H ? or IP67 only ?

3. What types of antennas/transmitters/power supplies are anticipated to support the intended frequency bands/distances/transmitted power?

4. Any sense of the IMU resolution requirement?

5. Must the entire solution be self-contained, or can the solution be split into two functional entities ?
   A. 1. There are no specific price, FoV, diopter, resolution, brightness, latency, weight, endurance, or tracking accuracy threshold performance criteria parameters required for topic call submission or consideration. As described in the topic call, operational context and technical thresholds will be provided for Phase I awardees.

2. As this is an Office of Naval Research SBIR topic call, it is intended for military applications. As described in the topic call, the specific operational context and technical thresholds will be provided to Phase I awardees - however, for Phase I, no specific accreditation for environmental engineering requirements are required for consideration. In later phases, for transition, hardware devices are expected to meet the associated deployment requirements identified by the transition sponsor.

3. The intent for the Phase I device is to demonstrate a domestically-sourced HUD compatible with FPV, JTAC, FO, and related AR activities. Specific antenna and transmitter combinations will be specified after Phase I selection.

4. Ideal solutions would achieve 1 meter or better position estimation accuracy for global location entry and 6DOF estimation, however, there is no specific cutoff accuracy threshold required for proposal consideration.

5. HUD solutions must be self-contained (i.e., monolithic) hardware solutions for Phase I consideration.
10/9/26  Q. 1. What are targeted unit price, field of view, eye-relief, diopter, display resolution, brightness, latency, weight, battery endurance, or tracking accuracy?

2. Does an FPV-only submission satisfy the topic without native 6DOF tracking at entry?

3. What minimum integration level is expected of the existing hardware, and can a teamed hardware platform satisfy that expectation?

4. What cost basis and sourcing/compliance criteria should proposers use before ONR supplies the detailed thresholds?
   A. 1. There are no specific price, FoV, diopter, resolution, brightness, latency, weight, endurance, or tracking accuracy threshold performance criteria parameters required for topic call submission or consideration. Ideal solutions would conform to ‘commercial’ price point HUDs, however, the notional price point is acknowledged as an example, not a limit. As described in the topic call, operational context and technical thresholds will be provided for Phase I awardees. Candidate solutions will provide domestically-sourced HUDs compatible with a variety of forward-deployed military activities including FPV drone operations, JTACs, and FOs.

2. As described in the topic call, an FPV-only HUD submission without on-board 6DOF tracking would not satisfy the objective of the SBIR topic.

3. Phase I device proposals should provide real-time sensor feed publication and bi-directional message integration with external systems to enable visualization of situational awareness iconography, video feed (FPV drones), and other HUD overlays.

4. All cost threshhold information can be found in the DON instructions posted on https://www.dodsbirsttr.mil/.

** TOPIC NOTICE **

The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoW FY-27 Release 1 SBIR BAA. Please see the official DoW Topic website at www.dodsbirsttr.mil/submissions/solicitation-documents/active-solicitations for any updates.

The DoW issued its Navy FY-27 Release 1 SBIR Topics pre-release on October 7, 2026 which opens to receive proposals on October 28, 2026, and closes November 25, 202 (12:00pm ET).

Direct Contact with Topic Authors: During the pre-release period (October 7, through October 27, 2026) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic. The TPOC contact information is listed in each topic description. Once DoW begins accepting proposals on October 28, 2026 no further direct contact between proposers and topic authors is allowed unless the Topic Author is responding to a question submitted during the Pre-release period.

DoD On-line Q&A System: After the pre-release period, until November 11, 2026, at 12:00 PM ET, proposers may submit written questions through the DoW On-line Topic Q&A at https://www.dodsbirsttr.mil/submissions/login/ by logging in and following instructions. In the Topic Q&A system, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing.
NOTE: You must have registered in the DSIP system in order to ask an on-line topic question.

DoW Topics Search Tool: Visit the DoW Topic Search Tool at www.dodsbirsttr.mil/topics-app/ to find topics by keyword across all DoW Components participating in this BAA.

Help: If you have general questions about the DoD SBIR program, please contact the DoD SBIR Help Desk via email at DoDSBIRSupport@reisystems.com


[ Top  -  Return ]