Modular Open Architecture Assured Positioning, Navigation, and Timing (PNT) Hub

Navy SBIR 24.2 - Topic N242-084
NAVAIR - Naval Air Systems Command
Pre-release 4/17/24   Opened to accept proposals 5/15/24   Closes 6/12/24 12:00pm ET    [ View Q&A ]

N242-084 TITLE: Modular Open Architecture Assured Positioning, Navigation, and Timing (PNT) Hub

OUSD (R&E) CRITICAL TECHNOLOGY AREA(S): Advanced Computing and Software

The technology within this topic is restricted under the International Traffic in Arms Regulation (ITAR), 22 CFR Parts 120-130, which controls the export and import of defense-related material and services, including export of sensitive technical data, or the Export Administration Regulation (EAR), 15 CFR Parts 730-774, which controls dual use items. Offerors must disclose any proposed use of foreign nationals (FNs), their country(ies) of origin, the type of visa or work permit possessed, and the statement of work (SOW) tasks intended for accomplishment by the FN(s) in accordance with the Announcement. Offerors are advised foreign nationals proposed to perform on this topic may be restricted due to the technical data under US Export Control Laws.

OBJECTIVE: Develop a modular device that integrates non-GPS sources of position, velocity, attitude, and time to enable operations in GPS-denied environments. The device should align with Modular Open Systems Approach principles and support open architecture technologies (e.g., SOSA, OpenVPX, pntOS, ASPN, etc.)

DESCRIPTION: Assured PNT capability provides continuous access to position, velocity, attitude, and time (PVAT) information of confirmed integrity and of sufficient accuracy to complete the mission in the complete spectrum of GPS threats. Currently, there is no common scalable and reconfigurable solution that delivers continuous access to PVAT information in GPS denied environments. Developing a modular device to integrate non-GPS source PVAT information enables easy reconfiguration to platform specific needs, avoids unnecessary development cost by reusing the same device, and removes intellectual property limitations.

This SBIR topic seeks to leverage commercial off-the-shelf technologies, and government-owned or open interfaces to produce a device with the following capabilities:

1. Platform I/O:

Configurable hardware/software module(s) to interface with aircraft avionics interfaces such as MIL-STD-1553 [Ref 1], ARINC-429 []Ref 2], Ethernet, and so forth.

2. Sensor I/O:

Configurable hardware/software module(s) to interface with non-GPS sources of PVAT.

3. PNT Application Space:

A configurable software hosting environment and software development kit (SDK) using non-proprietary application programming interfaces (APIs) to deploy the following functionality:

* Input / output abstraction:

Conversion of platform/sensor specific data structures to a common application data structure (e.g., ASPN2023.)

* Integrity Module:

Logical or statistical input/output validity test of PVAT and time information. Depending on the non-GPS input modality, this module(s) should conduct fault detection, exclusion, and alerting.

* Sensor Fusion:

Configurable state estimation algorithms to compute GPS- and non-GPS-based navigation solutions (e.g., Extended Kalman Filter, Particle Filter, etc.).

* Logging:

Log of system status, system performance, and alerts for performance evaluation, system maintenance, and troubleshooting.

PHASE I: Develop, design, and demonstrate feasibility of a Functional Architecture design of the proposed approach. Deliver a Physical Architecture design of the proposed approach. For proposed non-GPS PNT sources:

deliver performance prediction via modeling and simulation. The Phase I effort will include prototype plans to be developed under Phase II.

PHASE II: Deliver a working device prototype with necessary operation documentation. Support technology demonstration. Conduct limited-scope environmental qualification tests.

PHASE III DUAL USE APPLICATIONS: Collaborate with other defense agencies and prime contractor to determine transition opportunity. Verify and validate the performance of the technology developed under Phase II to enhance its TRL.

This topic will benefit defense contractors and navigation-based platforms. This technology will align with SOSA principles and allow private sectors to interchangeably and interoperably integrate their technologies without intellectual property limitations.


  1. "MIL-STD-1553C: Military Standard: Aircraft internal time division: Command/response multiplex data bus. (21 September 1978)." Department of Defense, Aeronautical Systems Division.
  2. "ARINC 429 Tutorial." AIM GmbH, 2024. AIM.

KEYWORDS: SOSA; OpenVPX; pntOS; ASPN; GPS-denied; Kalman filter


The Navy Topic above is an "unofficial" copy from the Navy Topics in the DoD 24.2 SBIR BAA. Please see the official DoD Topic website at for any updates.

The DoD issued its Navy 24.2 SBIR Topics pre-release on April 17, 2024 which opens to receive proposals on May 15, 2024, and closes June 12, 2024 (12:00pm ET).

Direct Contact with Topic Authors: During the pre-release period (April 17, through May 14, 2024) proposing firms have an opportunity to directly contact the Technical Point of Contact (TPOC) to ask technical questions about the specific BAA topic. Once DoD begins accepting proposals on May 15, 2024 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.

SITIS Q&A System: After the pre-release period, until June 5, 2024, at 12:00 PM ET, proposers may submit written questions through SITIS (SBIR/STTR Interactive Topic Information System) at by logging in and following instructions. In SITIS, the questioner and respondent remain anonymous but all questions and answers are posted for general viewing.

Topics Search Engine: Visit the DoD Topic Search Tool at to find topics by keyword across all DoD 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 [email protected]

Topic Q & A

05/13/24  Q. Can you confirm that the desired outcome for this topic is to develop a platform that can integrate existing PVAT solitions rather than to provide integrated or new PVAT solutions?
   A. Yes, the objective is to develop a platform that can integrate existing PVAT solutions, but we are not limiting the company from being innovative.

[ Return ]