By Robbin Laird
When I first visited the Ocius build facility, it was tucked inside the University of New South Wales, an enthusiastic team of smart young engineers clustered around Robert Dane’s vision of what an uncrewed maritime surface vessel could become. There was genuine energy and real technical imagination, but it had the character of a university lab: what I would call a mom-and-pop operation, where passion was the primary engine. I came away impressed by the people and the concept, somewhat less certain about the path to scale.
My recent visit to Ocius told a very different story. The company has moved into a proper industrial facility in a Sydney business park, and the contrast could not be more stark. This is no longer a university project. It is a production enterprise with real contracts, real customers, and a growth trajectory that reflects how rapidly the world’s navies are waking up to the operational value of uncrewed maritime systems.
I sat down with Robert Brezniak, Ocius’ Chief Growth and Market Development Officer, to understand where the company now stands and what the next phase of growth looks like. The conversation ranged from current contracts to the broader strategic logic of Australia’s maritime situation and why the so-called hull gap, so often treated as a source of national embarrassment, is better understood as one of the most significant strategic opportunities Australia has had in decades.
From Lab to Production Floor
The headline fact is this: Ocius has been awarded a major acquisition contract with the Royal Australian Navy for 40 vessels, to be delivered over five years from this year. Every one of those Bluebottles will be built in the Sydney facility where we spoke.[1],[2] That is not a prototype order. That is not a demonstration contract. That is a production commitment, and it represents a significant vote of confidence by the Royal Australian Navy in the Bluebottle’s capabilities, particularly for counter-undersea threat missions using towed line arrays.
Beyond the Navy contract, Ocius is operating vessels for Maritime Border Command, Australia’s coast guard equivalent, out of an operations center in the same Sydney building. Two vessels are in service with the Royal New Zealand Navy, with strong interest in expanding that relationship. In the United States, the company partners with Thayer Mahan, which operates six Bluebottles and is actively seeking more. Interest is building across Asia — North Asia, Southeast Asia — as well as Europe and the Southwest Pacific.
What has accelerated this international interest is, in part, the Royal Australian Navy contract itself. Other navies that had been watching the concept from a distance, uncertain whether autonomous undersea surveillance at scale was operationally credible, saw the RAN’s decision to commit at volume as a validation. As Brezniak described it: “Since the announcement by the Royal Australian Navy for 40 vessels, we’ve had a lot of interest from other navies who’ve been looking at it as maybe a concept and then realized that the Australian Navy’s backing Ocius to do that undersea surveillance at scale for them.”
The workforce has matured correspondingly. The early talent base from the University of New South Wales remains a source of pride, those were genuinely impressive young engineers, but the company has layered on substantial industry experience. A new head of production has just come aboard. Finance, contracting, business development, supply chain, human resources — all have been professionalized. As Brezniak put it, you have to reinvent the company as it grows because what works at one scale simply does not work at the next.
A Different Kind of Supply Chain
One dimension of the Ocius story that deserves more attention than it usually receives is the supply chain logic underpinning the Bluebottle. This is not a traditional military procurement supply chain — narrow, specialized, dependent on a small set of defence-specific contractors operating on long lead times and at correspondingly high costs.
The Bluebottle is built substantially around commercial off-the-shelf components, chosen for proven performance, ready availability, and cost-effectiveness. This gives Ocius a supply chain that is broader, more resilient, and easier to mobilize than what a capital ship builder deals with. It also reduces costs significantly and expands the pool of potential suppliers. When people talk about Australia’s industrial mobilization capacity or the ability to surge production rapidly in a crisis, this kind of supply chain architecture matters enormously. You are not dependent on a single specialized vendor for a critical component.
There are, of course, parts of the vessel that cannot come off a commercial shelf. The hull, the towed array, the rudder and flipper assembly — these require either in-house production or specialized subcontractors. On the array side, Ocius has worked with a notably diverse set of suppliers: Thayer Mahan, Thales, SEA and Opti11 from Holland. That diversity is itself a strategic asset, giving the company deep comparative knowledge of array performance across different use cases and price points, and positioning it, as Brezniak argued, as a world leader in array deployment on uncrewed surface vessels.
The conceptual point here is important. The Bluebottle is not a platform in the classic sense of a capital ship: a sealed, highly integrated system where the platform and its capabilities are inseparable. It is better understood as a payload delivery vehiclevehicle, and the payload drives the platform’s value, not the reverse. The Bluebottle you see today will look largely the same on the outside in five years. What will have changed — continuously — are the sensors, the arrays, the cameras, the communications architecture, and the software that ties it all together. Payloads that have platforms, as I put it to Brezniak, rather than platforms that have payloads.
Capability That Evolves in Service
This brings us to what I regard as the most analytically important aspect of the Ocius model: the relationship between the company and its operational customers, and how capability is developed and refined through that relationship.
The classic defence acquisition model works something like this: requirements are defined up front, a development program proceeds over years, a platform is eventually delivered, and then it is periodically upgraded on a slow cycle, often five to ten years between significant capability refreshes. The gap between requirement definition and operational deployment can be a decade or more, during which threat environments, technology options, and operational concepts all evolve in ways the original requirements did not anticipate.
Ocius works entirely differently. The 24/7 operations contract with Maritime Border Command has served as a continuous feedback loop between the company and the users of the data the Bluebottle generates. Mission duration has grown from 30 days to well over 100 days as standard. New sensors, new cameras, new radar configurations, aerial drones, all have been trialled in service, evaluated against real operational requirements, and either incorporated or rejected based on actual evidence rather than PowerPoint projections. The vessel and its payloads are being shaped, continuously, by the people who depend on the data they produce.
As Brezniak described it: “The feedback loop that we get from working with and talking to the users of the data — the users have the need — and feeding that back into the vessel is really important for both sides.”
I want to be precise about what this is and what it is not. It is not prototyping. Prototyping is a pre-operational activity aimed at demonstrating feasibility. What Ocius is doing is delivering operational capability today and evolving that capability within live operations, building for tomorrow inside the operations of today. The iteration happens at operational speed, not acquisition program speed. This is an entirely different model, and it is the right model for maritime autonomous systems, where unit costs are relatively low and the pace of technology change in sensors, software, and autonomy is rapid enough that a ten-year acquisition cycle is not just inefficient but operationally disqualifying.
The contrasting example is instructive. InSitu’s ScanEagle program with the U.S. Marine Corps was structured as a data services contract — InSitu provided data, not a platform, which left the company free to evolve the aircraft continuously as technology and mission requirements changed. When the U.S. Navy later sought to develop the Blackjack system under a platform ownership model, they found they could not iterate at the speed the system required. Blackjack never achieved operational status. The lesson, not widely understood, is that calling something a platform and managing it like a platform when it is fundamentally a data-delivery tool is a path to obsolescence before delivery.
Surveillance, Deception, and the Mesh Fleet Concept
Beyond the specific Bluebottle program, our conversation touched on what this class of systems makes possible operationally and the conceptual leap required to fully understand it.
Brezniak articulated the core value proposition clearly: “With a task force, if you lose a vessel, you’ve lost a huge capability, you’ve lost a lot of lives, a lot of money. If you lose a Bluebottle, you’ve lost a pixel on a screen. You’ve still got your other pixels. You’ve still got your data coming back from your other vessels. You’ve only lost one pixel. So the mission continues.”
This is not a marginal improvement over the existing model. It is a fundamentally different architecture for maritime surveillance. And it extends, as Brezniak noted, into the domain of deception as well as detection. A mesh of uncrewed surface vessels, operating as acoustic and electronic sensor platforms, can simultaneously surveil a large maritime area and, if configured appropriately, present an adversary with a confusing signature picture, multiple potential contacts to track, assess, and respond to, at a fraction of the cost of the crewed assets that would otherwise be needed to generate that kind of presence.
Surveillance and deception are, in this context, two sides of the same operational coin.
I spent considerable time during one visit to MARTAC studying imagery of multiple autonomous vessels operating together at sea. It took me several hours to understand what I was actually looking at. There was no epicenter. There was no single vessel whose destruction would collapse the capability. What I was looking at was a mesh and that is a genuinely different mental furniture for maritime operations. Destroying one node in a mesh does not destroy the mesh. This is not how anyone has historically thought about a surface task force, where the flagship or the capital ship at the center is both the source of command authority and the primary target.
The Hull Gap as Strategic Opportunity
I have been coming to Australia since 2014, and I have watched the evolution of its maritime capability with considerable attention. The current situation, a significant hull gap, an extended period in which Australia will not have anywhere near the number of crewed capital ships it will eventually require, is regularly framed as a national failure, a consequence of delayed decisions and inconsistent procurement strategy. There is something to that critique.
But I want to offer a different frame. The hull gap is also a strategic opportunity, perhaps one of the most significant Australia has had in a generation, to build the doctrinal, operational, and industrial foundation for a genuinely new kind of maritime force before the new hulls arrive.
The frigates and the AUKUS submarines are coming, eventually. When they do arrive, the question will be whether they enter a fleet that already knows how to think about hybrid operations — manned and unmanned, networked, mesh-structured, with payloads and data flows organized across multiple nodes — or whether they enter a fleet that is still operating with the mental furniture of the twentieth-century capital ship navy, and must learn the new model from scratch while simultaneously absorbing a major platform transition.
This decade is the window to answer that question correctly. Autonomous systems like the Bluebottle are available now. The operational experience is accumulating now. The concepts of operation for how mesh fleets connect with land-based assets, air assets, and crewed maritime platforms can be developed now, not in ten years when the new hulls are delivered, but in the years before, so that when the new hulls arrive, they enter an environment already organized to leverage what they bring.
My work on military transformation suggests it takes roughly five years after a new platform enters service to understand how to use it, and ten years to fully integrate it with the wider force. Starting that learning process now, with autonomous systems as the leading edge, gives Australia a running start on the transformation the new crewed fleet will require.
Brezniak put the practical dimension of this simply: “We can provide meaningful capability through uncrewed systems built with fiberglass that can be done more quickly and more cheaply and providing effect today.” That is not a consolation prize for the absence of capital ships. It is a genuine capability, available on a timeline measured in years, not decades and building industrial depth, supply chain resilience, and operational knowledge that will serve Australia well regardless of when the new hulls arrive.
The question is whether Australia’s defence establishment, its government, and its public discourse can make that conceptual shift: from treating the hull gap as a failure to be endured to treating it as an opportunity to be seized. Ocius, the Royal Australian Navy’s Maritime Autonomous Systems Unit, and the broader community of autonomous maritime developers are doing their part. The rest requires strategic imagination and institutional will.
[1] The Ocius Bluebottle USVs are named after the Bluebottle marine animal (known as a Portuguese Man of War in Northern Hemisphere) that lives at sea, uses its body as a sail and carries a sting in its tail.
[2] The Australian Minister for Defence Industry, the Hon Pat Conroy said of the “sting” (11MAR26): ‘Just as when you see at one of our beaches a bluebottle jellyfish, that’s a signal to get out of the ocean, I want potential adversaries to realise when they see one of these, it’s a signal to get out of our ocean’.