HORIZON-JU-Chips-2024-1-IA-T3

Topic 3 Focus topic on “Service Oriented Framework for the Software Defined Vehicle of the future” -

About the connections

The graph above was generated based on the following links

Call text (as on F&T portal)

View on F&T portal
Scope:

Proposals need to particularly address the following aspects:

The open architectures and building blocks of the Software-define vehicle middleware and API framework developed under this project shall aim at exposing the vehicle's features and functionalities in the form of standard modular services and APIs, simplifying the development and certification of in-vehicle and edge-cloud applications, simplifying the access to vehicle data, functions and resources, making vehicle upgrades easier, simplifying the adoption of existing and new regulations, verification, validation and certification, and adding agility and speed to automotive engineering.

Layer-based solutions introducing a level of abstraction which allows the SDV middleware and API Layer framework to be independent from the automotive SDV Virtualization, OS and Hardware Abstraction Layer. The concept of hardware abstraction layers interface (HALI), which facilitates the integration and the decoupling of vehicle hardware from software, represents the foundation on which these solutions should be based. The reuse of results from the project focusing on building blocks around the HAL from the call HORIZON-KDT-JU-2023-2-RIA Topic 2 is envisioned.

Modular platforms based on the concept of standardised, interoperable and non-differentiating “building blocks”, based on open source components as far as appropriate, enabling in-vehicle and cloud-based applications and ensuring the integration and support of existing frameworks such as ECPLISE SDV, AUTOSAR Adaptive, COVESA, SOAFEE, digital.auto, etc. Modularity is fundamental to promote the evolution of a European platform for the SDV Vehicle of the Future.

Support the evolution towards domain- or vehicle-centralised E/E architectures, consolidating vehicle functions at domain-level (e.g., powertrain, autonomous driving, cockpit, body, OTA update, maintenance, …) with dedicated domain controllers, and simplifying the evolution toward zone- and vehicle-centralisation, with central control unit(s) running functions or services in and across different SW domains in a vehicle.

Ensure the coverage of safety and security, including secure access to on-board (and off-board) resources, features and services, and data provision, exploiting for example an increased use of virtualisation, software building blocks isolation, and defined (and possible also standardised) interfaces.

Building on the SDV Virtualization, OS and Hardware Abstraction Layer building blocks developed in related projects, development of reference implementations of the SDV Middleware and API framework for the SDV Vehicle of the Future in different scenarios of OEMs and TIERs. Reference implementations shall allow the concrete evaluation of the SDV platform with demonstrators.

Highly-automated engineering methods, tools and tool-chains using existing or developing missing engineering building blocks for toolsets, supporting the DEVOPS continuous approach and virtual engineering, including design, development, test, validation solutions to improve the efficiency, productivity, quality and trustability of the engineering process and keep it in the temporal constraints of the time to market of ADAS, AD, infotainment, sensing and control systems. Engineering process support should rely on existing solutions wherever possible, extended and/or complemented by newly developed methods, toolchains, and tools, when required (e.g. phases of the engineering process not covered, missing tools, improvement of existing tools, etc.). Building blocks are encouraged to be open-source wherever adequate.

The consortium should be coordinated by a leading European industrial actor of the automotive industry (OEM, tier-1), or by a neutral organisation well established in the automotive software sector. The consortium must include: 

a large and representative number of European OEMs of motorised vehicles (passenger cars, trucks, buses, motor cycles, off-road) with headquarters in several Member States of the European Union and/or its associated countries; 

a large and representative number of European tier-1 automotive suppliers and technology companies, including semiconductor companies and software engineering experts;

a representative number of tool providers specialized on the described engineering toolchains above;  

innovative SMEs across the value chain; 

leading universities and research and technology organisations bringing the newest advances in relevant digital and other technologies and/or acting act as neutral mediators. 

actors from across a significant number of Participating States of the Chips-JU program with a strong focus on the automotive sector.

Proposals are encouraged:

To allocate tasks to cohesion activities with the projects selected under the call HORIZON-KDT-JU-2023-3-CSA Topic 3 on Coordination of the European software-defined vehicle platform on and the call HORIZON-KDT-JU-2023-2-RIA Topic 2 on Hardware abstraction layer for a European Vehicle Operating System.

To allocate tasks to cohesion activities with the [call 2024 automotive HW?].

To allocate tasks to cohesion activities with the [related CCAM and 2ZERO projects].

To allocate tasks to cohesion activities with the [related national SDV projects]

News flashes

2024-03-20

Amendment to the WP

Please note that that the latest amendment of the Chips JU Work Programme 2023-2027 has been adopted. 

The following updates are introduced:

- Appendix 3 “Activities Launched in 2024 for the Non-Initiative Part.”

Ø  Section 2.3 “National Budgets for the call 2024”. The amount for some of the countries has been updated.

 

Ø  In-text Annex 4 to appendix 3: “Country specific eligibility rules” have been added for some countries and amended for a country.

The updated Appendix 3 v6 has already been published on the website, in the “Multiannual Programme 2023-2027   please check here : https://www.chips-ju.europa.eu/mawp/

2024-03-15

National Budget - CH

Please note for the Part C- National Budget,  Switzerland has requested the Swiss partners to fill out and submit the template provided by the Swiss funding authority (Chips JU Call 2024_Swiss Annex C)  with the proposals for the 2024 non-initiative Chips JU calls.

Any question related to the template needs to be addressed to the Swiss NFA.

 

You can find it in the Calls Document  here https://www.chips-ju.europa.eu/noninitiative/  

2024-02-20

Page limit:

Applications are subject to the page limits set out in the call conditions:

- The page limit for the chapter on EXCELLENCE is 60 pages for the PO Phase 

- The page limit for the chapter on IMPACT is 60 pages for the PO Phase 

- The page limit for the chapter on IMPLEMENTATION is 60 pages for the PO Phase 

All tables, figures, references and any other element pertaining to these sections must be included as an integral part of these sections and are thus counted against this page limit.

If you attempt to upload a proposal longer than the specified limit, the pages above the limit will not be taken into consideration for evaluation .

2024-02-06
The submission session is now available for: HORIZON-JU-Chips-2024-1-IA-T3(HORIZON-JU-IA), HORIZON-JU-Chips-2024-1-IA-T1(HORIZON-JU-IA), HORIZON-JU-Chips-2024-1-IA-T2(HORIZON-JU-IA)
call topic details
Call status: Closed
Opening date: 2024-02-06 (2 years ago)
Closing date: 2024-05-14 (1 year ago)
Procedure: two-stage

Budget: 20,000,000
Expected grants: 1
Contribution: 500,000 - 20,000,000
News flashes

This call topic has been appended 4 times by the EC with news.

  • 2024-03-20
    amendment to the wpplease note that that...
  • 2024-03-15
    national budget - chplease note for the...
  • 2024-02-20
    page limit: applications are subject to...
  • 2024-02-06
    the submission session is now available...
Call

HORIZON-JU-Chips-2024-1-IA

Call topics are often grouped together in a call. Sometimes this is for a thematic reason, but often it is also for practical reasons.

There are 2 other topics in this call:

Source information

Showing the latest information. Found 6 versions of this call topic in the F&T portal.

Information from

  • 2025-11-20_06-39-22
  • 2025-10-28_15-53-39
  • 2025-07-02_03-33-06
  • 2024-11-23_03-30-16
  • 2024-07-04_15-02-04
  • 2024-03-30_14-17-49

Check the differences between the versions.

Annotations

You must be logged in to add annotations
No annotations yet

Events

This is just a very first implementation, better visualisation coming

Events are added by the ideal-ist NCP community and are hand-picked. If you would like to suggest an event, please contact idealist@ffg.at.

Call topic timeline

What phase of the topic timeline are we in? This timeline contains some suggestions on what are realistic actions you should or could take at this moment. The timeline is based on the information provided by the call topic.
  1. Work programme available

    - 2 years ago

    The call topics are published first in the Work Programme, which is available a while before the call opens. By following up the Work Programme publications, you can get a headstart.

  2. Opening date

    - 2 years ago

    The call opened for submissions.

  3. Closing date

    - 1 year ago

    Deadline for submitting a project.

  4. Publication date

    - 1 year ago

    The call was first imported in TopicTree.

  5. Time to inform applicants Estimate

    - 1 year ago

    The maximum time to inform applicants (TTI) of the outcome of the evaluation is five months from the call closure date.

  6. Sign grant agreement Estimate

    - 1 year ago

    The maximum time to sign grant agreements (TTG) is three months from the date of informing applicants.

  7. Today

Funded Projects

Loading...

Project information comes from CORDIS (for Horizon 2020 and Horizon Europe) and will be sourced from F&T Portal (for Digital Europe projects)

Call document info

This section will come soon and contain the scraped information from the call document, such as the expected impact, scope, and other relevant sections. In the meantime, you can find this information in the call text section or directly on the F&T portal. View on F&T portal