Why Maritime Operations Centers Need Fusion, Not Another Data Feed

At a Glance

• The Navy’s Maritime Operations Centers (MOCs) already receive more data than they can operationally use, with the constraint on decision advantage now sitting at the fusion layer rather than the data access layer.
• Adding another commercial feed to a MOC does not add another operational capability if the feed arrives as a stovepipe rather than fused into the existing common operational picture.
• Navy leadership has publicly named stovepiped data as a standing MOC challenge, with data standardization and cross-system integration cited as priorities for MOC modernization.
• Integration is not a downstream implementation problem — it is an architectural characteristic of the intelligence solution being procured, and it determines whether a commercial capability actually delivers decision advantage inside a MOC or arrives as one more feed the analyst has to sort through.
• The Defense Innovation Unit’s public work on multi-sensor data convergence reflects an emerging Navy expectation that commercial data has to fuse with space-based, shipboard, airborne, and unstructured sources inside existing common operational picture tools, not alongside them.
• The industry partnerships that will actually deliver operational value to MOCs are the ones built around integration and mission-specific analytical tradecraft, not around raw data volume or feed diversity.

The Constraint Isn’t Data, It’s Fusion

MOCs receive multi-sensor data at volumes the operational teams inside them cannot fully process, cross-reference, or turn into decision-relevant intelligence at the pace commanders require. The constraint on decision advantage is not the size of the incoming data pipeline. It is the fusion layer that turns that pipeline into an operational picture.

The Potomac Officers Club’s 2026 Navy Summit is running a dedicated panel on Integrating Commercial Capabilities Into the MOCs, which is a direct indicator of where Navy institutional thinking is heading on this question. The panel framing is not about adding more commercial data. It is about how commercial capabilities integrate into the MOC architecture in ways that produce operational value, not just additional inputs.

Offering another feed of AIS data or vessel tracking does not answer the question the MOC modernization conversation is actually asking. The question is not whether commercial data is available. It is whether commercial data can be integrated in a way that turns it into decision advantage inside the MOC’s existing workflows.

Why Another Feed Is Not Another Capability

The stovepipe problem in MOCs is not new. Navy leadership has been publicly discussing it for years. The core issue is that data arriving in a MOC through a channel not integrated with existing common operational picture tools does not add analytical value proportional to the data volume. It adds another tab, another feed, another queue that analysts have to work through separately from the picture they are already trying to build.

At a 2025 Sea Air Space symposium, senior Navy information warfare leadership described the problem in exactly these terms, calling out the need to standardize data coming into MOCs so commanders can make better decisions in the crisis-to-conflict transition. The panel framing emphasized fusion of data, sensors, and weapons, not the volume of any one of those streams.

The operational consequence of stovepiped data is that analytical work the tool should be doing gets pushed to the human analyst. Cross-referencing across feeds. Reconciling contradictory signals from different sources. Assessing whether a pattern visible in one feed also appears in another. Every one of these is work the fusion layer should be handling before the analyst sees the output. 

A new commercial data feed introduced without fusion into the existing MOC picture does not reduce this constraint. It adds to it. The analyst now has one more source to reconcile against the others. 

What Integration Actually Looks Like

Integration is not a marketing claim. It is a specific architectural characteristic of how a commercial capability connects to the MOC’s operational picture.

The Defense Innovation Unit’s public work on multi-sensor data convergence for MOCs captures the operational requirement clearly. MOCs need commercial data to converge with space-based, shipboard, airborne, and unstructured sources inside the common operational picture tools the service already runs. Not alongside them. Not through a parallel dashboard the analyst opens separately. Inside them.

That architectural requirement has several practical implications for how commercial data capabilities need to be built and delivered:

1. The capability has to be structured to output into existing common operational picture formats and standards, so the output can be consumed by the MOC’s downstream tools without a translation step.
2. The capability has to be able to cross-reference against other data sources the MOC is receiving, so its output arrives as fused analytical context rather than as a standalone feed. 
3. The capability has to fit into the operational workflows the MOC already runs, so adopting it does not require the service to stand up new training, new certifications, or new procedures to use it.

An industry partner that delivers on these architectural requirements is offering something structurally different from a partner delivering a data feed. The distinction is the difference between augmenting the MOC’s existing capability and adding another item to the analyst’s queue.

Fusion Runs Both Ways

Integration is not only about a commercial provider’s data flowing into the MOC. It is also about the MOC’s existing data assets flowing into the fusion layer.

The MOCs the Navy is standing up in 2026 already sit on top of significant existing data assets. Space-based sensors, shipboard sensors, airborne intelligence, unstructured intelligence products, and mission-specific data sources the service has built up over years of operational work. A commercial capability that requires the MOC to abandon or replicate any of that data is asking the service to give up existing analytical value in exchange for new data.

The architectural approach that avoids that trade-off is one where the fusion layer accepts data the customer already has and processes it alongside the commercial sources the vendor delivers. Bring-your-own-data is not a marketing feature. It is the architectural distinction between a fusion platform and a data feed. A vendor whose analytical layer can only process the data the vendor supplies is delivering a feed. A vendor whose analytical layer can process the customer’s existing data alongside its own is delivering a fusion capability.

For MOCs, this distinction determines whether the commercial capability adds to the existing analytical picture or displaces parts of it. The MOCs that build their intelligence architecture around fusion capabilities that accept existing data assets are the ones positioned to preserve years of prior analytical investment while gaining the value of new commercial sources.

Why Mission-Specific Tradecraft Matters More Than Data Volume

Beyond integration, the other characteristic that separates operationally valuable commercial capabilities from data feeds is the tradecraft embedded in the analytical layer.

A raw AIS feed delivered to a MOC is not the same capability as a fused, mission-tuned analytical output that draws on AIS alongside other sources. The tradecraft in the analytical layer is what turns raw data into decision-relevant intelligence. It is where the behavioral models are built, where the identity resolution work happens, where the anomaly detection is calibrated against operational baselines that match the mission the MOC is running.

The tradecraft is also where fusion actually occurs. Multi-sensor data convergence is not achieved by dumping AIS, satellite imagery, radio frequency, and behavioral data into the same output. It is achieved by an analytical layer that understands how to cross-reference those sources, weight them against their known reliability, and produce a coherent picture that is more analytically valuable than any single source alone.

Commercial data providers that deliver raw feeds without embedded tradecraft are effectively asking the MOC’s analysts to do the fusion and analytical work themselves. Commercial partners that deliver tradecraft-enabled outputs are contributing to the MOC’s operational capability directly.

For MOC procurement teams evaluating commercial capabilities, the question is not the size of the data pipeline the vendor can deliver. It is what the vendor’s analytical layer produces when the data is fused into a mission-specific picture.

Written by Maya Romi, Maritime Intelligence Content Specialist, Windward.