UK Coast Guard Seeks New Data Center for LRIT
The MCA is calling for bids on a new data center to enhance maritime safety. Key details inside! #DataCenter #MaritimeSafety
Every six hours, every UK-flagged vessel anywhere on the planet broadcasts its identity and position to a satellite overhead. That signal eventually lands somewhere — a data center responsible for ingesting, storing, and making sense of a continuous feed of maritime location data. Right now, the UK's Maritime and Coastguard Agency (MCA) is looking for a new home for that function, and the clock is ticking.
The MCA has issued a formal tender for a provider "capable of providing and maintaining" a data center dedicated to Long Range Identification and Tracking — the global satellite-based system that underpins real-time awareness of ship movements worldwide. The contract is valued at approximately £1.5 million (around $1.98 million including VAT), with a hard operational deadline of July 1, 2026. Interested parties have until May 5, 2026, to apply.
That's a tight window. Roughly eight weeks to bid, then less than two months to stand up infrastructure that handles live maritime safety data.
What the LRIT System Actually Does — and Why It Matters
LRIT isn't optional, and it isn't obscure. It's a mandatory international requirement established under SOLAS — the Safety of Life at Sea convention — the same regulatory framework that emerged directly from the lessons of the Titanic disaster in 1912. More than a century later, the core obligation hasn't changed: nations must know where their ships are.
Under SOLAS, every ship subject to the convention must automatically transmit its identity, position, and the date and time of that position at six-hour intervals. The data flows through a national data center — in this case, the UK's — which serves as the collection and distribution point for flag-state vessels.
The stakes here aren't commercial in the traditional sense; they're legal and humanitarian. A failure in this infrastructure doesn't just create an operational headache — it puts the UK in breach of its international maritime obligations and, more concretely, degrades the situational awareness that coast guard responders rely on when ships go silent.
For anyone who's spent time around port operations or maritime search-and-rescue coordination, the value of continuous positional data is obvious. A vessel that goes off the grid between six-hour pings in a major shipping lane is a very different problem from one that disappears in the North Atlantic — and having reliable baseline tracking is what makes that distinction possible.
Technical Requirements: Not a Straightforward Colocation Play
This isn't a tender for a generic cloud migration or a standard colocation arrangement. The provider taking this on inherits a set of specific technical obligations that distinguish it from typical government IT infrastructure contracts.
The winning bidder will need to integrate position data as a GIS layer within the MCA's Maritime Domain Awareness Platform — which means the data center isn't just a storage and compute facility; it's an active component of the MCA's operational picture. GIS integration requires clean data pipelines, validated formats, and reliable latency. A ship's last known position that shows up late or malformed in an operational dashboard isn't useful.
Then there's the legacy migration requirement. The new provider will need to absorb historical position data from the previous LRIT data center — a task that sounds routine but carries real risk. Maritime positional records aren't just operational; they're used in accident investigations, insurance disputes, and compliance audits. Data integrity across the migration isn't negotiable.
The MCA hasn't publicly disclosed the geographic requirement for where the data center must be located, though the agency itself is headquartered in Southampton on the UK's south coast. For a system with sovereignty implications — this is national flag-state data — there's a reasonable expectation that the facility will need to sit on UK soil, though the tender documentation doesn't confirm this explicitly.
One detail worth noting from an infrastructure perspective: Telent, which operates the MCA's mission-critical communications network, connects 163 remote radio sites using a combination of full-fiber and microwave technology, with traffic flowing between what it describes as "the national data centers." The plural is notable. The MCA hasn't publicly detailed its current data center footprint, but this suggests the incoming LRIT provider won't be operating in isolation — they'll be plugging into an existing, distributed communications architecture.
What £1.5 Million Actually Buys
Let's be direct about the contract value: £1.5 million is modest by data center standards. This isn't a hyperscale deal or a multi-year cloud transformation contract. For context, a mid-sized colocation facility in the UK might charge that annually just for cabinet space and power in a well-connected facility.
That compression of budget against the criticality of the function is the central tension any serious bidder will need to resolve. The provider absorbing this contract is essentially accepting mission-critical uptime requirements — the kind associated with coast guard operations — on a budget that reflects a specialized, low-volume data workload.
That said, there are legitimate reasons a qualified provider might compete hard for this contract. Government maritime contracts carry institutional credibility. The MCA relationship opens doors in adjacent defense, port authority, and maritime agency markets across the UK and internationally. And once embedded in national maritime infrastructure — handling SOLAS-compliant data with GIS integration into a live operational platform — the switching costs for the agency are significant. Incumbency in government critical infrastructure tends to be sticky.
For specialist providers in the maritime technology or government data center space, the ROI calculus here is about positioning and portfolio as much as margin on this specific contract.
The Path Forward for Bidders
The application window closes May 5, 2026. The operational start date is July 1, 2026. That leaves essentially no runway between contract award and go-live — which means any credible bidder needs to be walking in with existing infrastructure, not a plan to build it.
The MCA hasn't published detailed scoring criteria, but for a contract of this nature — regulatory compliance, operational continuity, and GIS integration — expect evaluation to weight technical capability and relevant experience heavily over price. A low bid from an unproven provider in a sector where the prior system needs to migrate intact and the new system needs to be live in weeks is a liability, not an opportunity.
Providers with existing government security clearances, demonstrable experience handling sovereign or defense-adjacent data, and established GIS and maritime system competencies are best positioned. The migration of legacy positional data alone requires domain knowledge that generic IT outsourcers don't typically bring.
What this tender signals more broadly is worth paying attention to. As maritime situational awareness becomes increasingly integrated with digital platforms — the MCA's Maritime Domain Awareness Platform being a concrete example — the underlying data infrastructure becomes more strategically significant. The data center supporting LRIT today is a GIS layer feeding an operational dashboard. The logical next evolution is AI-assisted anomaly detection, predictive search-and-rescue positioning, and real-time integration with vessel traffic services. The provider that builds a solid foundation here is well-placed to grow alongside that ambition.
The tender is open. The deadline is firm. And somewhere out there is a vessel currently mid-Atlantic, broadcasting its position into the void — trusting that the infrastructure on the other end is ready to receive it.
Explore opportunities in the InfraSale Marketplace today!