Spectral Autonomy

pntOS: A framework for navigation sensor fusion

Part of the Open Architecture Field Guide.

pntOS defines an application framework and plugin interfaces for positioning, navigation, and timing systems. It allows sensor handling and estimation algorithms to be developed as separate components.

In this guide

Separating the parts of a navigation application

A navigation application estimates position, velocity, orientation, and related quantities from sensor observations. Together, those quantities form its state estimate. Sensor fusion combines information from several sources so that the estimate can use their complementary observations.

The application contains more than an estimation calculation. It receives and interprets measurements, manages configuration and time, and connects the processing components that use the data. If all of these responsibilities are tightly coupled, introducing a new sensor or trying another estimation method can require changes throughout the software.

pntOS provides application interfaces for dividing the estimation problem into plugins, software components connected through defined interfaces. The architecture allows parts of the fusion application to be developed and replaced separately. Its name refers to a navigation application framework operating within a host software environment. [1]

How a common measurement enters the application

The ASPN data model gives observations a common representation. It describes the navigation information being supplied, including the context needed to interpret a measurement. pntOS provides the software organization in which components can use those representations.

Consider adding a source of velocity measurements to an existing navigation application. The producer must describe what was measured, when it was measured, and the relevant coordinate frame. A processing component then relates the observation to the application's estimated state. The shared data representation and plugin boundary separate that work from unrelated parts of the application.

The framework connects these contributions into a running estimation process. Measurements become inputs to the configured components, and their calculations contribute to the navigation solution. The figure groups those responsibilities to show the relationship between incoming observations, estimation components, and the application that coordinates them.

A pntOS fusion application's responsibilitiesASPN measurements and estimation components are combined within a pntOS application to produce a navigation solution.estimated stateMeasurement inputsEstimation componentspntOS applicationNavigation solution

Scroll horizontally to inspect the diagram.

Figure 1. The application brings measurement inputs and estimation components together through defined interfaces. ASPN describes the measurements; the configured components perform the calculation that produces the navigation solution.

Changing one part of the calculation

The separation is useful during development because sensor data and estimation methods can change independently. A team can replay the same measurement sequence through alternative implementations and compare their estimates. Holding the observations fixed helps identify the effect of the changed calculation.

A different experiment can retain the estimator and introduce another measurement source. That examines the contribution of the new information. In both cases, the application interfaces give the experiment an explicit point of change, so the engineer can explain what was altered and what remained part of the existing configuration.

This also helps organize supplier work. One contributor can develop a component associated with a particular measurement or estimation function, while another develops the surrounding application. Their shared responsibility is the interface through which the component participates in the calculation.

An interface specification and its implementation

The pntOS architecture defines software relationships; an implementation turns those relationships into running code. Kauffman, Carson, and Raquet describe the architecture and a reference implementation used to demonstrate a modular navigation application. The implementation provides an example of how the interfaces can be used, while individual applications select the components and processing needed for their purpose. [1]

For an integration team, the useful record connects the selected interface definitions to the actual plugins and configuration. That record allows a navigation result to be related to the components that produced it. When a plugin changes, the team can repeat the relevant experiments and examine both the intended improvement and its effect on the rest of the solution.

Maintaining the shared interfaces

Interfaces used by several organizations need coordinated maintenance. A change to a measurement representation can affect both its producer and its consumers, while a plugin-interface change can affect applications that host existing components. These dependencies make continued maintenance part of the architecture's practical use.

The PNT Standards Consortium, established as an ISTO member program in June 2026, provides shared governance and development for pntOS and ASPN. Its role connects the technical interfaces to a community process through which they can evolve. [2]

References

  1. Kauffman, Carson, and Raquet, ASPN and pntOS: An Open-Source Ecosystem for Building Navigation Systems, ION GNSS+ 2026, pp. 3161–3185.
  2. ISTO, Formation of the PNT Standards Consortium, June 2, 2026.