The PNT Standards Consortium
Part of the Open Architecture Field Guide.
The PNT Standards Consortium was established in June 2026 as an ISTO member program. It provides shared governance and continued development for navigation standards including ASPN and pntOS.
In this guide
Keeping a shared navigation interface consistent
A navigation-data standard becomes useful when several organizations implement the same meaning. A sensor producer supplies a measurement, an estimator consumes it, and an application coordinates the processing. If each participant resolves ambiguities independently, software that once shared an interface can gradually develop different expectations.
Maintaining the standard therefore requires continuing work. Someone must review proposed changes, clarify definitions, and identify which version an implementation follows. These activities connect the published specification to the systems that depend on it.
The PNT Standards Consortium was established in June 2026 as a member program of ISTO. Founded by Leidos, IS4S, and TRX Systems, it provides shared governance and development for open positioning, navigation, and timing standards, including ASPN and pntOS. Its formation announcement identifies long-term stewardship and a community process for evolving those standards as central purposes. [1]
Why ASPN and pntOS need coordinated maintenance
ASPN defines navigation information exchanged between components. pntOS defines software interfaces for building applications that process that information. A change to one can therefore affect implementations of the other. [2]
Consider a proposed extension for a new kind of measurement. The data model needs a description that tells consumers what the observation means. Processing software needs a way to relate that observation to its estimation task. Documentation and examples need to express the same interpretation so that separate teams can implement their parts consistently.
A shared maintenance process gives the affected teams a place to examine that relationship. Sensor developers can explain the information their equipment supplies. Estimation developers can identify the information needed by their calculations. Application developers can examine how the change interacts with existing software. The proposal can then be considered as an interface used by several participants.
Connecting standards work to an implementation
For a project adopting these standards, an identifiable release provides the starting point. The project can record which definitions its components implement and associate test results with that configuration. Later changes can be compared with the selected baseline instead of entering the application without a clear account of what changed.
The consortium's announced activities include developing future changes, improving documentation, and working on compliance and certification initiatives. These are supporting activities around the shared specifications; an individual program still selects the components and configuration used in its own navigation system. [1]
The practical connection is a two-way one. Implementations reveal unclear definitions and new requirements through actual engineering work. Standards maintenance turns those findings into changes that other implementations can understand and adopt. That process allows a common interface to improve as its community gains experience.