A resilient positioning, navigation and timing (PNT) architecture keeps essential position or time functions usable and trustworthy when a PNT source is disrupted or manipulated. It combines risk assessment, protected GNSS, integrity monitoring, independent cross-checks, defined degraded modes and tested recovery.
Start with the platform
The correct architecture is driven by mass, power, protected frequencies, interfaces, autonomy stack and the consequences of degraded navigation.
Avoid a single-number decision
Suppression depth, simultaneous null count, anti-spoof capability and environmental performance should be reviewed together.
Validate the complete signal chain
A representative acceptance plan should cover the antenna array, processing electronics, receiver output, host platform and operating environment.
Build resilience as a layered system
| Risk-management step | Architecture decision | Evidence to request |
|---|---|---|
| Identify dependencies | Map the functions, assets and interfaces that require position, navigation or time | System boundary, source inventory, continuity limits and integrity thresholds |
| Protect the GNSS path | Reduce interference reaching the receiver | Protected bands, null capacity, waveform, geometry and measured suppression conditions |
| Detect loss or manipulation | Monitor signal, receiver and cross-source consistency | Monitored observables, alert output, thresholds, latency and false-alarm handling |
| Respond in degraded mode | Use suitable independent inputs or restrict the host to an approved operating state | Source independence, fusion logic, fallback limits and host-controller actions |
| Recover and improve | Restore trusted PNT and retain evidence for review | Reacquisition criteria, transition behavior, logs and repeated test results |
The NIST Foundational PNT Profile frames responsible use as risk management across identification, protection, detection, response and recovery; it is guidance, not a product certification or compliance checklist. GPS.gov also recommends planning for signal loss and taking reasonable steps to verify or authenticate received data. Review the NIST PNT Profile and GPS.gov resilience resources.
Use the CRPA anti-jam guide to define the protected front end, the anti-spoofing comparison to separate integrity controls, and the testing framework to convert the complete architecture into measurable acceptance criteria. When the boundary is clear, send an OEM integration brief for configuration review.
Questions procurement teams ask
What is resilient PNT?
Resilient PNT is a risk-informed system capability that keeps required position, navigation or timing functions usable and trustworthy when one source is disrupted, degraded or manipulated. It combines protection, detection, independent checks, a defined response and tested recovery.
Is a CRPA antenna a complete resilient-PNT solution?
No. A CRPA can improve GNSS availability under interference, but resilience also depends on the receiver, integrity monitoring, complementary sensors or sources, the host system response and the validated operating concept.
How do anti-jam and anti-spoof controls differ?
Anti-jam processing reduces interference that threatens GNSS availability. Anti-spoof controls address false or manipulated signals and data that threaten integrity. A resilient architecture may need both, with separate acceptance evidence for each.
What does NOVA supply within a resilient-PNT architecture?
NOVA configurations can protect the GNSS front end and, for selected configurations, provide receiver or anti-spoof functions stated in the quotation. Independent sensors or references, fusion and integrity logic, degraded-mode control and host-system recovery remain separate integration responsibilities unless explicitly included.
What should an OEM define in a resilient-PNT RFQ?
Define the platform and mission, required continuity and integrity, protected constellations and bands, receiver and sensor interfaces, SWaP limits, expected disruptions, alert and degraded-mode behavior, recovery criteria and measurable acceptance evidence.
How should degraded operation and recovery be validated?
Agree on the disruption scenario, system boundary, monitored outputs, alert thresholds, host response, fallback duration, reacquisition criteria and pass or fail limits. Test them in an authorized controlled environment and then check representative-platform integration.