NATO’s five-year warning. The timing decisions that cannot wait.
“Russia could be ready to use military force against NATO within five years.”
More than a year of that window has already passed.
For organisations delivering defence infrastructure, the remaining time must accommodate design, procurement, integration and testing. Decisions made today will shape what can be relied upon as 2030 approaches.
Rutte’s warning described a potential capability, rather than a prediction of conflict or a universal procurement deadline. It nevertheless gives defence planning a clear sense of urgency — including the infrastructure dependencies that can be overlooked until something fails.
An essential capability, in NATO’s own words
NATO’s overarching Space Policy states:
“Positioning, navigation and timing is essential in all NATO missions.”
The policy explains that positioning, navigation and timing (PNT) enables precise positioning and the synchronisation of effort across military operations.
For those responsible for defence networks and infrastructure, our recommendation is to make that dependency explicit during design. Identify which systems require accurate time, where it comes from and what happens if the source becomes unavailable or unreliable.
For example, a communications project should establish its timing requirements alongside network architecture and power provision. Introducing them after equipment has been selected can constrain how resilience is delivered.
Test for the conditions that matter
The NATO Communications and Information Agency has participated in navigation warfare trials testing Global Navigation Satellite Systems (GNSS), including GPS, under realistic jamming conditions. Its reporting also highlights the essential timing synchronisation those systems provide.
That provides a practical example of assessing capability under disruption.
For timing infrastructure, we recommend testing against defined operational requirements: how much timing error is acceptable, how long systems must continue without their primary reference and how recovery will be managed.
A useful test should establish what connected applications actually experience during a failure. Monitoring and ongoing validation can then help maintain visibility after deployment — activities that can be incorporated into a Timing as a Service (TaaS) arrangement.
Explore how edgeTime brings timing delivery, monitoring and lifecycle management together.
The infrastructure behind the operation
NATO’s 2026 Resilience Baseline Requirements call for:
“Continued availability of reliable, resilient and secure civil communications services.”
They also address dependencies between services and the potential for disruption to spread across sectors.
For a defence estate or infrastructure programme, our interpretation is that timing should form part of this wider resilience assessment. The source of time, its distribution and the systems consuming it may sit under different contracts or responsibilities.
Consider a programme involving an estate operator, a network provider and several equipment suppliers. Someone needs to establish the timing requirement across those boundaries and ensure that each part contributes to the intended outcome.
This is where early specialist involvement can help connect the operational requirement with the design, delivery and ongoing management.
See examples of edgeTime’s timing and synchronisation work across critical infrastructure.
Responsibility continues after installation
NATO also asks Allies to:
“Consider the availability of critical supply chains and managed services in a situation of crisis or conflict.”
For procurement teams, that makes the delivery arrangements as relevant as the equipment specification. Who monitors performance? Who responds to a fault? How are replacement equipment, maintenance and recovery organised?
At edgeTime, these are questions we address when shaping a timing service. Our TaaS models range from fully managed delivery to shared arrangements that work with customer-owned infrastructure, allowing responsibilities to reflect the organisation’s requirements.
For example, an organisation may retain its existing timing estate while adding specialist monitoring and assurance. Another may need a managed service covering design, deployment and ongoing operation. The appropriate model depends on the environment, security requirements and level of control needed.
Three years leaves little room for late decisions
As of October 2026, the start of 2030 is just over three years away.
Within a defence infrastructure programme, that period needs to accommodate requirements, funding, procurement, installation and validation. Leaving timing until the later stages reduces the opportunity to identify shared dependencies and test recovery before systems enter service.
Our recommendation is to start with a focused assessment of the existing environment. Establish what operations depend on, identify gaps and agree which improvements should be prioritised. From there, dedicated infrastructure, managed services or a combination of both can be evaluated against clear requirements.
NATO has stated the importance of PNT. The practical task is to turn that recognised dependency into infrastructure that is understood, tested and maintained.
Discuss your timing requirements with edgeTime and start planning your next steps.
Leave a Reply