HORIZON-MISS-2026-03-OCEAN-04: Towards a European Network of Ocean Technology Testing Sites

HORIZON-MISS-2026-03-OCEAN-04: Towards a European Network of Ocean Technology Testing Sites

What this opportunity is

This topic, under the EU mission Restore our Ocean and Waters, funds activity to build an integrated European network of ocean technology testing facilities. The official page describes it as a call to strengthen the pathway from concept to market by improving access to real marine test environments. The key logic is simple and important: Europe is stronger when ocean technology builders can test at sea in coordinated, predictable ways instead of isolated pilots.

The call is published under the Horizon Europe Framework Programme (HORIZON) and is currently open, with a published date of 04 February 2026 and a deadline of 23 September 2026, 17:00 CEST. The title indicates this is topic HORIZON-MISS-2026-03-OCEAN-04.

The call page states that selected outcomes should include harmonised approaches to access across participating sites, faster innovation cycles, and reduced costs and risks of marine testing. It also expects outcomes that support SMEs and start-ups and strengthen European leadership in marine technologies through a coordinated ecosystem.

Key details at a glance

What the project is expected to deliver

The call text gives specific expected outcomes and applicant tasks, which helps shape proposal design:

• develop harmonised approaches for access across selected testing sites;
• accelerate technology innovation cycles and cut validation risk/time-to-market;
• provide cost-effective access to testing and expertise so teams avoid building parallel in-house marine validation stacks;
• build coordinated network elements including access policy alignment, data security procedures, and IP frameworks;
• increase collaboration across academia, industry, regulators, and investors;
• support inclusion of less-developed coastal regions and outermost regions.

A notable requirement is integration with broader digital and data strategies. The text explicitly references digital twin-based testing and highlights links to the EU Digital Twin Ocean ecosystem where relevant.

From a practical perspective, this means the project is less about one standalone demonstration and more about network design + governance + operational alignment. If your concept is only a single technology with no replication/scale plan, it may not map cleanly to a network topic. The strongest proposals will make the argument that one harmonised system reduces fragmentation for an entire subsector.

Who this is good for (and who may struggle)

This call fits several profiles particularly well:

• companies (especially SMEs) building maritime robotics, sensors, autonomous systems, corrosion-resistant materials, offshore monitoring tools, renewable marine platforms, or operational data systems;
• universities and research organisations that already run marine labs or have access agreements in coastal regions;
• innovation clusters and test-site operators already managing trial environments;
• coastal authorities, infrastructure operators, and ecosystem intermediaries that can help route testing demand into real-world environments.

Applicants with only internal test environments and no external collaboration footprint will likely be less competitive. The call design strongly rewards consortium capability to integrate multiple sites and organisations.

Also, the objective to serve SMEs/start-ups is explicit. Teams dominated by established incumbents with little ecosystem planning may still apply, but they should avoid turning the proposal into a procurement-style showcase. The program has a public-interest value in network effects.

A common interpretation error is to assume this is mainly grant money for laboratory R&D only. While technical development is important, the call text repeatedly emphasises:

1. mapping existing sites,
2. harmonising access rules,
3. coordinating data and IP governance,
4. identifying investment opportunities to build long-term sustainability.

That means governance architecture and user-facing service design are as important as hardware specs.

Funding mechanics and budget reading

The page gives a clear budget picture:

• total indicative budget: EUR 2.90 million;
• one project to be funded under the topic;
• Commission notes that EU contribution may range from EUR 2.50 to 2.90 million depending on proposal needs.

Because this is a network-focused mission topic, budget should usually support:

• mapping and benchmarking of current test assets;
• operational workstreams to connect sites;
• shared workflows, digital support, and harmonisation tools;
• engagement and coordination mechanisms across regions and user communities;
• dissemination and uptake support.

This is not a large engineering build program by itself. Proposals that attempt to spend the entire budget on procurement-heavy technical hardware without clear network integration, data-sharing architecture, and policy alignment are likely to appear misaligned.

Applicants should think in terms of cost categories and narrative consistency:

• Each activity should be linked to mission outcomes;
• budget lines should demonstrate shared benefit beyond one partner;
• expected outputs should include reusable access products or frameworks, not just one prototype;
• measurable outputs should align with the three mission objective clusters in the call page: ecosystems and biodiversity, pollution prevention/elimination, and carbon-neutral/circular blue economy.

Eligibility and legal/participation constraints

The call page provides explicit geographic scope references (listing many member and associated countries) and associated regions. In practical terms:

1. Confirm each beneficiary’s legal and administrative status.
2. Ensure partner organisations can operate within the mission and fund management requirements.
3. Ensure any satellite testing footprint and data flows can meet environmental and security constraints.

The page states that conditions are based on the common Horizon Europe Annex B framework and makes one explicit technical condition:

• when projects use satellite-based Earth observation, positioning, navigation and related timing data, the call explicitly expects use of Copernicus and/or Galileo/EGNOS (additional data sources may be combined).

Even if your proposal does not use those services directly, this is a useful signal that data quality, interoperability, and compliance are expected to follow EU space-data and geospatial standards.

Given the maritime scope, teams should also pre-plan environmental sensitivity constraints around each site. The call expects user needs and marine ecosystem constraints to be considered alongside technical ambition.

Application process: how to prepare without guessing

The official page does not replace the full proposal workflow, but it links directly to the EC support stack: Funding and Tenders Portal, manual pages, FAQs, Research Enquiry Service, National Contact Points (NCPs), IP help, EEN, and support service links. Use those as your process backbone.

A practical preparation sequence:

1. Read the page in full and copy all constraints into a one-page compliance register.
2. Draft a baseline consortium map: which organisations cover testing operations, governance, digital infrastructure, and commercialisation support.
3. Document existing test sites and their limitations (environmental, access windows, legal permissions, instrumentation range).
4. Write a harmonisation blueprint: common application process for users, consistent safety protocols, IP policy model, data handling model, and cost structure.
5. Build a pilot-to-scale execution route: prove at least two use cases that transfer across basins and show how you replicate standards.
6. Define a reviewable plan for SMEs/start-ups: where they apply, how they get support, how they reduce time-to-validation.
7. Pre-check all deadlines, expected durations, and role assignments.

If your consortium includes entities from different legal systems, add a legal appendix or annexed workstream early in drafting to show governance maturity. EU calls are often assessed for execution realism as much as scientific ambition.

Because this is a mission implementation topic with a strict close date, do not wait for perfect clarity before drafting. Use short iterations with consortium comments at weekly cadence, especially on the integration and governance sections. The final week should be reserved for final legal and formatting compliance checks.

Why the timeline matters and what to expect

The page shows a typical date pattern:

• publication: 04 February 2026,
• deadline: 23 September 2026,
• start: early 2026 after grant agreement preparation,
• duration: 3 to 4 years.

For many groups, that means there can be a gap between official publication and actual funded implementation windows while grant agreement is finalised. If your plan assumes immediate spend in week one, that usually creates risk in proposal design.

A strong team should therefore structure the budget across phases:

• year 1: mapping, baseline governance, and pilot harmonisation;
• year 2: interoperable access layer and first validated workflows;
• years 3–4: scaling, service uptake, and sustainability planning.

This structure mirrors the mission logic and should prevent overpromising while still presenting measurable milestones.

Common mistakes (and how to avoid them)

1) Treating this as a pure demo grant

Mistake: Proposing only a standalone prototype or single-site demo without regional network utility.

Fix: Include a network architecture and at least a clear scaling model across multiple sites with governance interoperability.

2) Ignoring existing infrastructures

Mistake: Failing to map existing facilities and duplication risks.

Fix: Start with an audit of current ocean testing assets and integrate improvements rather than rebuilding parallel infrastructure.

3) Weak SME onboarding logic

Mistake: Mentioning SMEs in text but giving no access pathway or affordable service model.

Fix: Add explicit modules for start-ups: access route, cost-sharing models, onboarding criteria, and technical support.

4) Weak data and security framing

Mistake: Leaving data-sharing architecture vague and omitting rights and security controls.

Fix: Specify data taxonomy, security baseline, and IP procedures for shared test datasets and performance outputs.

5) Missing basin-level inclusion

Mistake: Focusing only on one sea basin with no rationale for broader coverage.

Fix: Show deliberate inclusion of Atlantic/Arctic, Mediterranean, and Baltic/North Sea contexts, and explain portability across environmental regimes.

6) Overlooking Copernicus/Galileo expectations

Mistake: Using alternative geospatial/positioning paths without justified approach where EO/positioning is essential.

Fix: If using satellite positioning or EO, explicitly reference compliant data sources and explain data integration.

Strategic fit with the broader mission goals

This topic is tightly linked to the broader mission outputs in ecosystems and biodiversity, pollution prevention, and carbon-neutral/circular blue economy. The strongest proposals translate these objectives into specific testing-site services:

• for biodiversity, support nature-based and ecosystem-aware trials;
• for pollution prevention, build testing workflows that help validate cleanup, monitoring, or prevention systems;
• for blue economy circularity, create re-use, retrofit, and lifecycle-informed development routes.

Because maritime sectors are often fragmented by country, basin, and regulation, the strongest value is typically not in a single technology but in common service architecture. The proposal should therefore show clear value across participants who are not all co-located.

Preparation checklist before submission

1. Confirm the opportunity is still open on the portal at final submission date.
2. Build a one-page objective tree that maps every partner activity to expected outcomes.
3. Confirm whether your site footprint includes basin coverage and whether local authorities can support deployment periods.
4. Assign ownership for:
   • legal and governance model,
   • environmental compliance,
   • IP and data security,
   • SME outreach.
5. Include budget logic for harmonisation tasks (templates, digital coordination, shared access layers).
6. Prepare for at least one real-world testing workflow with measurable user benefit.

Questions you should answer in your narrative

Before you submit, make sure your text can answer these quickly:

• What specific access barriers are you removing?
• Which users are able to test technologies faster because of this network?
• How is your plan environmentally safe for sensitive marine ecosystems?
• How will the network sustain itself after initial EU funding?
• What measurable outputs show regional replication rather than one-off pilots?
• How will SMEs/start-ups reduce cost and time-to-market compared with independent in-house testing?

The call text already sets these expectations implicitly. Explicit answers are what differentiate a coherent proposal from an interesting idea.

Official links and next steps

Keep these links in your working list:

• Call page: HORIZON-MISS-2026-03-OCEAN-04 topic page (official)
• Horizon Europe Work Programme 2026–2027 Missions (official context and related mission logic)
• Funding & Tenders Portal (official submission process)
• EC Online Manual, Funding FAQ, Research Enquiry Service
• National Contact Points and Enterprise Europe Network for partnering support

For the official page, use this direct URL: https://projects.research-and-innovation.ec.europa.eu/en/funding/funding-opportunities/funding-programmes-and-open-calls/horizon-europe/eu-missions-horizon-europe/restore-our-ocean-and-waters/horizon-miss-2026-03-ocean-04-towards-european-network-ocean-technology-testing-sites

The opportunity is directly official, active for 2026–2027 mission funding, and suitable for teams with real cross-regional execution potential.