Insights · Part 5 of the series
The Satellite Signal Dependency Register
Before an organisation can manage its reliance on satellite position and time, it needs a simple list of what depends on the signal and what happens when it goes wrong.
Over this series I have looked at jamming, spoofing, timing, shipping and the natural and accidental causes of interference. The common thread is simple: before an organisation can manage the risk, it needs to know what depends on the signal.
That is the first job: a dependency register. It need not be complicated. A spreadsheet will do, if it answers five questions for each system:
- What uses position, navigation or timing from satellites?
- Which of the three does it use? Don’t overlook timing just because the equipment never moves.
- Where does the data come from? A direct receiver, a supplier’s service or further down the supply chain?
- What happens after one minute, one hour, one day, one week and one month without it?
- What is the fallback, who owns it, and has anyone tested it?
The five time intervals come from the Royal Institute of Navigation’s guidance on resilient PNT, which also recommends an annual audit of reliance and asking key suppliers how they manage their own PNT risk. The UK Government’s 2023 PNT resilience framework reinforces the importance of backup arrangements at national level.
The exercise can expose dependencies that aren’t obvious: a clock inside a piece of equipment, a supplier’s tracking service, or a system that keeps producing plausible data when its input is wrong. A functioning screen is not proof of a trustworthy signal.
It also changes the conversation about interference. Alongside asking what caused the disruption, you can ask a more immediate operational question: what do we do in the first hour?
This series grew out of my work on SkyShield, where we are developing compact, passive antenna technology for more resilient navigation on platforms where size, weight, power and cost matter. That work is still under development. A dependency register needs no new technology at all, which is why it comes first.
This is the last piece in the series. If you do one thing this month, list what in your organisation would notice if the signal went wrong tomorrow. Then ask who would notice first, and what they would do.