HORIZON-MISS-2026-03-OCEAN-04: Towards a European Network of Ocean Technology Testing Sites (2026 call, closed)

HORIZON-MISS-2026-03-OCEAN-04: Towards a European Network of Ocean Technology Testing Sites (2026 call, closed)

What this opportunity is

This archived opportunity records the 2026 topic under the EU mission Restore our Ocean and Waters. It was designed to support a coordinated European network of ocean technology testing facilities, improving access to real marine test environments and helping technologies move from laboratory concepts toward market-ready solutions. The value proposition was network coordination: applicants were expected to connect sites and services so testing did not remain isolated in disconnected pilots.

The topic was published under the Horizon Europe Framework Programme (HORIZON) on 04 February 2026. The European Commission lists its deadline as 23 September 2026, 17:00 CEST, and its current status as Closed. Applications for this cycle are no longer being accepted. The Commission’s Mission page says the five 2026 topics have closed and invites readers to watch for further information about topics under the 2027 Work Programme. It does not announce a successor round for this specific topic. Treat this page as a historical reference; do not rely on the old submission instructions as an open call.

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 official topic page directs applicants to General Annex B for eligibility conditions; it does not replace those rules with a simple checklist of organisation types. It lists a broad set of countries associated with the opportunity and identifies the Atlantic and Arctic, Mediterranean, and Baltic and North Sea basins as Mission Lighthouse areas. Those geographic listings should not be read as a guarantee that every entity in every listed jurisdiction could participate in every role. For any later Horizon Europe topic, check the live call text and annexes for the exact country, consortium, funding, and third-country rules in force for that call.

For the closed 2026 topic, the page 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 and present status

The 2026 submission window has ended. The official topic record is marked Closed, so there is no live application route for this topic now. The Commission’s update says to watch for information about topics under the 2027 Work Programme, but does not announce a successor cycle for this specific topic. During the 2026 call, applicants used the Funding & Tenders Portal submission route linked from the topic record. That record also linked the Commission’s Online Manual, FAQs, Research Enquiry Service, National Contact Points (NCPs), Enterprise Europe Network, IT Helpdesk, European IP Helpdesk, and partner search services. These were support resources for applicants during the call, not evidence that the opportunity remains open.

For historical context, an applicant preparing a proposal for the 2026 cycle would have needed to use the topic’s Funding & Tenders Portal route and satisfy the published call documents. The topic page directs eligibility checks to General Annex B and states the Copernicus and/or Galileo/EGNOS condition for projects using the specified satellite data and services. A consortium would then have needed to:

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 around clear use cases, explaining how the network can adapt and replicate shared standards across sites and basins. The official topic does not set a minimum number of use cases.
6. Define a reviewable plan for SMEs/start-ups: where they apply, how they get support, how they reduce time-to-validation.
7. Confirm role assignments, budget assumptions, partner eligibility, and portal requirements against the call documents.

Teams working on a future call can reuse these preparation lessons, but must not assume that its scope, eligibility, dates, templates, or submission portal settings will match the 2026 topic. If organisations span different legal systems, clarify the governance and responsibilities early. The Commission’s support links remain useful for general Horizon Europe questions, while the relevant future call page must control any application decision.

Timeline and what can be concluded

The official topic record gives a publication date of 04 February 2026, a deadline of 23 September 2026 at 17:00 CEST, and a typical project duration of 3 to 4 years. It also says the project was expected to start in early 2026 after grant agreement preparation. That estimate conflicts with the same record’s September 2026 deadline: a project selected from this call could not begin after grant preparation in early 2026 if proposals were still due in September. Treat the start statement as an inconsistent planning note, not evidence of an award or actual start. The call is closed, and the official pages checked for this refresh do not identify an award result, a confirmed project start, or a new application date for this topic.

The duration and proposed work phases below describe how an applicant might have planned a project under the call; they do not establish the timetable of a selected consortium:

• 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.

Reusable preparation checklist for related future calls

This checklist is retained as planning context only. It does not indicate that the 2026 topic is open. For any future opportunity, first locate its official live call page and replace every assumption with that call’s published rules. A network proposal of this kind would benefit from teams that:

1. Map partner activities to the outcomes in the applicable work programme.
2. Confirm whether the proposed site footprint covers relevant basins and whether local authorities can support deployment.
3. Assign clear ownership for governance, environmental compliance, IP and data security, and SME outreach.
4. Include budget logic for harmonisation tasks such as templates, digital coordination, and shared access procedures.
5. Define a real-world testing workflow and measurable user benefit if the next call asks for comparable work.

Questions a proposal for this topic needed to answer

For the closed 2026 cycle, a coherent proposal needed to explain:

• 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?

These questions reflect the 2026 call’s network, access, environmental, and sustainability priorities. A future topic may set different expectations, so applicants should use its published text.

Official links and archive note

The European Commission’s Directorate-General for Research and Innovation manages the official topic page, which records the 2026 call’s scope, closed deadline, amount, listed countries and basins, expected outcomes, and linked support services. The separate Mission update confirms that all five 2026 topics are closed and points readers to further information about topics under the 2027 Work Programme. It does not confirm that this particular topic will return or provide a new application date. Follow the Commission’s programme and Funding & Tenders Portal announcements for verified future opportunities; do not use this archived page as an application notice.

Official links:

• Official 2026 topic page
• Commission update: 2026 Mission calls are closed
• Horizon Europe Work Programme 2026–2027 Missions (official context)
• Funding & Tenders Portal, Online Manual, FAQ, Research Enquiry Service, National Contact Points, IT Helpdesk, European IP Helpdesk, Enterprise Europe Network, and partner search services (official support links from the topic page)

The 2026 opportunity is closed. The Commission has not announced a successor cycle for this specific topic in the checked official update. This page preserves the 2026 call facts as a historical reference.