Project Charter

Weekly Meeting:  Wednesdays, 3-4pm CET (Zoom Link)(Subscribe to Community Calendar to stay up to date)

Slack Channel 

Github Repo

Project Leads:

• @sonia.biswas, Volvo Cars

• @Christina Rux, WirelessCar

• @Nils Lagerqvist , Volvo Cars

Important dates (from the EU Data Act):

• January 11, 2024: Entry Into Force
  The EU Data Act formally entered into force on this date, starting the countdown to its application and giving businesses time to prepare.

• September 12, 2025: General Application
  Most obligations of the Data Act become directly applicable across the EU. This is the main date when companies must begin compliance with data access, sharing, portability, contractual fairness, and other core provisions. The Act starts to impact connected products, digital services, cloud providers, and public sector data requests.

• September 12, 2026: Design Obligations for Connected Products
  From this date, manufacturers of connected products and related services must ensure their designs allow data access and sharing “by default.” New design and architecture requirements will apply for products introduced after this date.

• September 12, 2027: Unfair Contractual Terms
  Provisions concerning unfair contract terms apply to contracts concluded on or before September 12, 2025, if those contracts have indefinite duration or will expire at least ten years after January 11, 2024. This provides a transitional window for legacy long-term agreements.

• And finally, by September 12, 2028, the Commission shall carry out an evaluation of the Data Act and submit a report on its
  main findings to the European Parliament and to the Council, and to the European Economic and Social Committee. Among the areas to be studied will be the impact the Data Act will have on the use of data in the economy, including on data innovation, data monetization
  practices, as well as on data sharing within the common European data spaces.

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. Potential information regarding the European Commission workshop.

   2. Way forward

4. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. Current status was reported, suggestion to go into sleep mode and call for meetings when needed. However, decision to run next meeting according to schedule. We need to discuss the connection to the VDM project more and it turned out that some companies has been invited to answer a poll and participate in a workshop arranged by the European Commission. The subject is experiences and reflections of the implementation of EU Data act in the vehicle industry. We would love to get some feedback if other companies have received this invite.

   2. Way forward - continue with the meeting series for now.

4. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. Short information that the promotion text is ready. Asking all to read and feedback comments. The text is here: eu-data-act/arguments/covesa-specifications-for-eu-data-act.md at main · COVESA/eu-data-act · GitHub and please use our slack channel for feedback: #eu-data-act

   2. We will regard all comments that comes in by Wednesday, Dec 17, 2025. Relevant changes will be made and then the final version will be made available to our Github repo. We ask all to promote the final version via your preferred channels.

   3. Suggestion is that we then go into “sleep” mode and call for meetings when we have new information that needs sharing

4. Next meeting

   1. I suggest that we start next year with a meeting by the end of January just to see if there are any last things before sleep mode.

1. Compliance statement

2. Introduction

3. Status ongoing work

4. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. Next meeting

   1. Decision to change cadence to once a month. Next meeting to be held Nov 26, 2025

1. Presentation was held with an update of the project. This presentation was shared.

Open

1. Compliance statement

2. Introduction

3. Plan for working session in AMM meeting next week:

   1. present the objective of this project (Daniel Eriksson)

   2. Present the VSS examples created (Daniel Eriksson)

   3. Review the proposed text to be published as COVESA recommendation (Kristian Jaldemark, WirelessCar)

      1. feedback? changes needed? agreement?

      2. eu-data-act/arguments/VSS-as-schema-for-EU-Data-Act-promo.md at main · COVESA/eu-data-act

4. Next meeting: cancelled due to AMM at the same day. Paul will update meetings for daylight saving time differences in US and Europe.

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. work on argumentation for interface standards, see meeting notes Sept 17.

4. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. VSS example

      1. Stefan Sellschop will support Daniel Eriksson in finding contact person for the CLEPA example.

   2. EU commission interface repository work:

      1. no update

   3. Interpretations of EU Data act:

      1. Based on the documents shared last meeting (see below), we decided to start creating input to our recommendation to the ongoing work of an EU Repository of interface standards. We start with contributing shorter texts on Github GitHub - COVESA/eu-data-act: EU Data Act Project in the new folder eu-data-act/arguments at main · COVESA/eu-data-act

      2. If you lack access to the GitHub, please contact Paul Boyes from COVESA team. You can still create pull requests without access. Daniel Eriksson has created 3 new skeleton documents:

         1. Arguments for VISS: Ulf B will contribute

         2. Comparison VISS and ExVe (eg that VISS uses VSS, where ExVe has no data model but could potentially use VSS)

         3. Important criteria from the Data consumer perspective: Christina to ask Stefan Sellschop for input.

      3. Next steps: walkthrough of content in the next meeting, decision of what can be transferred to the document with the recommendation by us.

4. Next meeting: October 1st

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. VSS example: Daniel Ericsson informed about ongoing research of which VSS version that CLEPA is using. He invited everybody to take a look at the repo and create pull requests

      1. Ulf Björkengren commented as these are examples, they do not have to be updated to the latest version.

         Decision: we will not update with new versions continuously, just mark with the version used.

   2. EU commission interface repository work:

      1. Christina Rux to Ask EU work group about status of ongoing work with the interface repository

      2. Christina Rux to ask Nils LAgerqvist to contact the workshop persons about status of ongoing work

   3. Interpretations of EU Data act:

      1. Ulf Björkengren shared material from CLEPA, ACEA, PFA et c about interpretation of EU Data Act https://pfa-auto.fr/wp-content/uploads/2024/10/Automotive-Sector-Guide-Data-Act-V4-23062025.pdf

      2. Also, there is a similar paper from VDA: publication-renderer

      3. We decided to read these through and discuss next week, how should these influence our recommendation?

4. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. What has happened during Summer

      1. Promotional text for using COVESA VSS and VISS in the scope of EU Data Act is under way (@Nils Lagerqvist ).

      2. Work has been done to add the CLEPA list to the repo (@daniel.eriksson.11 )

         1. Action: Verify which version of VSS is used in current CLEPA list (@daniel.eriksson.11

         2. Action: Verify that the CLEPA list is a good example of using VSS. (@daniel.eriksson.11 )

         3. Action: Complete the ACEA list using VSS. (@daniel.eriksson.11 )

   2. What is ahead?

      1. Continue the ongoing work.

      2. Action: Agree that the ambition of this initiative is to promote

         1. VSS naming

         2. VSS Structure

         3. VISS for API

         4. Suggest that a statement is written ensuring the three points are all in scope and bring it up in this meeting later this Autumn.

4. Next meeting

• Compliance statement

• Introduction

Status ongoing work: Update on example of VSS mapping (@daniel.eriksson.11 )

• Daniel Eriksson presented mapping of ACEA proposal of predefined data list (A1) to VSS that Sebastian Schildt has done based on an older initiative.

• About 70 % of the data points are now mapped to VSS. To cover the rest, Ulf Björkengren recommended to create overlays in our repository. "Make a best guess if you don't have all the domain expertise". 

• The list needs to be updated to the latest version of VSS (v5)

• Asking the audience to review the proposal.

https://docs.google.com/spreadsheets/d/1EaKbwqhCmw4V9lZH1kh_GU4n8iOVAn5bT1O86SpF5UQ/edit?gid=0#gid=0

https://github.com/COVESA/eu-data-act

• Other data point examples proposed by Geotab:

https://github.com/COVESA/eu-data-act/blob/main/examples/covesa-cv-insurance.tsv

https://github.com/COVESA/eu-data-act/blob/main/examples/covesa-cv-fleet.tsv

• Daniel Eriksson will include the CLEPA list, depending on its licences.

• We will also add a link to the ongoing work in the COVESA CVIS project: https://github.com/COVESA/commercial-vehicle-information-specifications

Other issues:

Ulf Björkengren will later today propose a work in COVESA project CDSP (Central data service playground) that should result in a demo for next spring AMM. A fleet mgmt use case, using VSS and VISS and MongoDB. https://github.com/COVESA/cdsp

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. Christina Rux's reflections from COVESA AMM

      1. Takes some time to explain the purpose of this project to new people  

      2. Daniel Eriksson and Ted Guild shared and explained the ongoing work of examples using VSS

      3. Asked for contact persons that are involved in the EU work of "harmonized interoperability standards", no new contacts yet. We would like to learn more about the ongoing work so if any OEM or other is involved in the workshops organized by the EU work group, please let us know.

      4. General reflection: there isn't so much activity in this project at the moment, we are slowly but surely working on our deliverables but it seems right at this moment to take it at this pace and just be prepared for more "buzz" around this topic when the EU Commission release their report on "mandatory standards for interoperability", date unknown. So we are basically intentionally keeping the lights on right now! 

   2. Ongoing work (contact us on slack if you want to contribute, see slack info at the top of this page)

      1. Writing a recommendation of use of VSS and VISS (on github) 

         1. Gather material with argumentation on why to use VSS from a regulation point of view

         2. Also include arguments that not only automotive but also other industries like insurance, fleet are benefiting from this since they use the data

         3. Arguments of other domains in automotive that point to the use of VSS (eg Autosar gateway)

      2. Build examples (github)

      3. Search for contact persons in the EU work group 

   3. Proposal of deadline: present results of the work on meeting at August 20 (or even later, depending on different stakeholders' vacation)

   4. Proposal to move this meeting to a fortnight schedule rather than weekly. Paul changed the meeting invitations accordingly.

4. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. @daniel.eriksson.11  to talk something on the setup of the Github repo. @Edward Guild - discuss some more on Fleet and insurance signals points of interest.

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. @daniel.eriksson.11  to talk something on the setup of the Github repo. @Edward Guild - discuss some more on Fleet and insurance signals points of interest.

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. Discussion on the content of the EU Data Act Panel @ COVESA AMM in Berlin, It was a really good discussion! 

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. TBA 

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. TBA 

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. Short update on current status, including text provided by Kai Hudalla. 

   2. The Github repo was published shortly after the meeting COVESA/eu-data-act: EU Data Act Project

4. TBA 

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. Ask to all: please try to find representatives in the ongoing EU commission investigations, so we can learn more about different viewpoints. 

      1. It would be great if you could investigate if your organisation has been invited to respond to "Interoperability of data processing services". EU commission sent out requests last September: "The European Commission’s Directorate-General for Communications Networks, Content and Technology (DG CNECT) has commissioned a study on “interoperability of data processing services”. A company called WIK-Consultant GmbH are doing the invitations and so on. We would like to know who from the automotive industry is involved in this to be able to understand different viewpoints better, so we make an informed proposal. We do not aim to unify the OEM's message, we just want to understand more. I assume this request could have ended up at the CIO/CDO/ legal/ compliance/ CISO or other department.

      2. Contact has been made with the leader of this study, hope to get more information to share with the team.

   2. Workshop on data points using VSS.

      1. The list will be published on GitHub. @daniel.eriksson.11 working on the ReadMe and license agreement clearing, and then it will be become public with the help of @Paul Boyes 

   3. We agreed on adding more signals, and their VSS equivalence, if existing (see added lists in the slack channel). Proposal that any required VSS updates should be discussed with Sebastian Schildt, who has previously driven this topic. 

   4. Discussion about the purpose of having a list of data points: 

      1. the purpose is not to demand or make data points mandatory, they only serve as examples

      2. the real benefit of VSS needs to highlighted, preferably in the text that is being written as proposal. Kai Hudalla to draft example and discuss with @Nils Lagerqvist what to bring into that deliverable

4. TBA 

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. Report out from the EC DG CNECT workshop:
      Decision to start with general "PaaS"-level standards like authentication etc. No Industry vertical-specific standards yet. Will use CAMSS for assessing standards CAMSS | Interoperable Europe Portal.
      Test run of assessing 114 standards within App Development, IAM, API Mgmt approved 17 standards related to cloud interop and 10 standards to be assessed against EU Data Act criteria.
      Intention seems to be that any approved standard will be a mandatory standard within given field.
      Both AWS and SAP did good interventions pointing at both good sides and bad sides and lack of description for the centralized repository

   2. Discussion on next step, Christina proposed to look at the 42 data-points from ACEA, this was approved and focus on this for next meeting.
      Connected to this Nils had been able to get his hands on a similar list from VDA dating back to 2023:  

4. TBA 

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. A list of deliveries was shown, please comment and propose changes or additional deliveries 

   2. Github repo up and running but structure etc not verified yet

   3. The workshop meeting regarding the EC DG CNECT on a central repository of harmonized standards for interoperability will be held during March 20. Report out next week.

   4. We (Nils, Christina, and Sonia) need to specify the workshop content for Day 2 of the COVESA AMM in May.

   5. Please, any ideas, contributions, comments in mail, slack, Github 

4. TBA 

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

4. TBA 

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. No specific work has been done during the past week. 

   2. EU Workshop wrt interoperability standards has been set to March 20 (Nils Lagerqvist to participate from Volvo Cars)

4. Introduction to VISS @Ulf Bjorkengren VISS-VISSR-overview.pptx

5. Next meeting

1. Compliance statement

2. Introduction

3. Status ongoing work

   1. Plan of next presentations: 

      1. ACEA representative: Ulf B has asked for more info. Thomas Spreckley (Volvo Cars)/ Ted Guild (Geotab)/ Achim Henkel (Bosch) to contact ACEA Fleet reps. Nils (Volvo Cars) to contact Volvo Cars Legal. The ACEA proposal (seems to go back to as early as 2022). This was discussed in the EC’s Motor Vehicle Working Group (MVWG), no source contact from ACEA available . Question: who can present ACEAs standpoint/ projects et c in this area in a Wednesday work meeting, 

      2. SAE/ ITC: Thomas S & Ted & Achim to present findings for commercial vehicles (add link): March 12

         1. https://www.sae-itc.com/

         2. https://docs.google.com/document/d/1OKjlefi6_gGIKYvbZIHdF8Syabj_7AvsiksKBXmT9mc/edit?tab=t.0

      3. @Christina Rux @Nils Lagerqvist contact Philippe Favreau from Ampere to ask about possibilities to do a presentation

4. Introduction to VSS @Sebastian.Schildt 

5. Next meeting

1. Compliance statement

2. Introduction

3. Additional feedback from information sessions

4. Plan the work

   1. Short-term

      1. Start writing COVESA statement about recommendation by OEMs to EU about interoperability standards

         1. who: project managers start writing, presenting updates in work meetings

         2. tooling: GitHub

   2. Plan presentations for next meetings (Wednesdays, 3-4 pm, CET)

      1. General intro to VSS: Feb 26th, ask Eric Jaegervall/ Adnan Bekan/ Sebastian Schildt about who can present

      2. General intro to VISS 3.0: March 5, Ulf Björkengren

      3. ACEA: Ongoing work in this area, promoting/ recommending VSS and interoperability standards? 

      4. French initiative PFA Platform Automobile

      5. Japanese initiative: Ouranos https://www.meti.go.jp/english/press/2023/0429_001.html