Secure Computing Continuum (IoT, Edge, Cloud, Data spaces)

Expected outcomes

• Projects may contribute to some of the expected outcomes; say which ones and why.
• For each outcome (EO1 to EO3), name who will use or adopt your results (a specific group, not “industry” or “society”), how they get them, and the indicator that shows the change, with baseline, target and date.
• Use the topic's own words for each outcome, so the evaluator can tick it off.

What the scope asks for

Evaluators check the proposal against these sentences of the scope. Answer each one visibly, in the call's own words.

• “Proposals should address critical challenges such as ensuring data integrity in highly distributed and dynamic environments, implementing robust zero-trust architectures to secure interconnected and heterogeneous systems, and enabling comprehensive protection for sensitive data and processes.”
• “Privacy should be considered a core element of these approaches, ensuring that data confidentiality is preserved throughout its lifecycle, in compliance with relevant data protection frameworks, such as GDPR.”
• “Solutions are expected to deliver tangible and measurable security improvements across all layers of the continuum, prioritizing scalability, interoperability, trustworthiness, security and resilience against emerging threats.”
• “Proposals are expected to address one or more of the following:.”

Conditions that shape the proposal

• Part B, sections 1–3: 45 pages (standard application form). Text beyond the limit is not read; tables and figures count.
• Lump sum: the budget is fixed per work package and paid when each work package is completed. Every work package needs activities and deliverables an evaluator can verify, and the effort must match the money.
• Innovation action: evaluators expect a plausible path to commercialisation and named first users or customers.
• Other Eligible Conditions: “In order to achieve the expected outcomes, and safeguard the Union’s strategic assets, interests, autonomy, and security, participation in this topic is limited to legal entities established in Member States and Associated Countries. In order to guarantee the protection of the strategic interests of the Union and its…”

Impact pathway and traps

• Keep outputs, outcomes and impacts apart: what you deliver, what changes when others use it, and the long-term effect.
• Link your outcomes to the destination's expected impacts in the Work Programme. Destination impacts are long-term effects, not project deliverables.
• Name the barriers outside the project (regulation, markets, user behaviour) that could block uptake, and what you will do if they do.
• Section 2.3 (the summary canvas) is optional on this call; the old split into scientific, economic and societal impact is no longer required.