Resources |
◎ COVESA Events |
Join/Sign Up |
◎ Join COVESA |
CVIS Meeting Topics and Meeting Notes
This page intends to contain the agenda for next CVIS meeting (Mondays 16.00-17.00 CET) and notes from previous meeting. Below is a template for the agenda. General agenda points like discussion on PRs and issues may be skipped if discussion on prioritized topics takes too long time.
See COVESA Common Meeting Schedule for meeting link. The meeting is open to anyone.
Policies
It is expected that all meeting participants have read the compliance statement. Every meeting will start with a reminder.
Strive for making signal objects reusable by other signal specifications.
Specification development page
The writing of the signal specifications are done at https://github.com/COVESA/commercial-vehicle-information-specifications.
Welcome and Compliance statement
Welcome to the COVESA CVIS Meeting!
Antitrust
Before we begin, we would like to make clear that COVESA is committed to compliance with the antitrust laws in all of its activities, and that it expects all participants to similarly comply with the antitrust laws. We will not engage in--and members must refrain from--any discussion of, or understandings regarding competitively sensitive topics. If you have any doubts regarding whether a matter is appropriate for discussion, please consult with your antitrust counsel.
Open and Royalty-Free
Further, COVESA aspires to be an open and royalty-free organization. The discussions and contributions made during this session are governed by the COVESA Intellectual Property policy. If you are unfamiliar with that policy, please review it in detail prior to making any contribution that reads upon a patent.
Agenda Template
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
xxx
General topics:
Open Pull Requests CVIS
Issues CVIS
Discussions CVIS
Other
Prioritized topics for next meeting
Meeting notes 2025-11-17
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Presentation of the new tool vspecPreprocessor
Meeting notes 2025-11-3
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Multiple tree trailer example
From tree creation to data access using VISS demo
Trailer doman tree proposal by Volvo
How to increase the attendance of these meetings?
Meeting notes 2025-10-20
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Multiple tree trailer example
From tree creation to data access using VISS
Meeting notes 2025-10-6
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
CVIS trailer tree initialization, see Trailer feedback below.
Solution needs to be developed at som point whether it is for single or multiple tree solutions.
Single tree / multiple tree model?
Trailer data.
Will look at Volvo’s trailer tree proposal at next meeting to try to advance it.
FMS data.
Try to create a separate tree staying with FMS data definitions (of unit, datatype etc).
We will revisit the CVIS vehicle type agnostic tree model at next meeting.
Meeting notes 2025-09-22
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
CVIS trailer tree initialization, see Trailer feedback below.
FMS data representation.
Meeting notes 2025-09-08
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
CVIS trailer tree proposal continued
VAPI – A connectivity agnostic Vehicle API for access to signals and services
AMM - do we have anything relevant to present?
Ulf and Ted put something together, to be presented in the CV context.
Meeting notes 2025-08-25
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Meeting cancelled due to confusion on the new meeting time. It starts every other Monday at 15.00 CET (previously at 16.00).
Meeting notes 2025-08-11
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
CVIS trailer tree proposal
ACEA-COVESA MoU
VAPI – A connectivity agnostic Vehicle API for access to signals and services ← Will be presented at the next meeting
Ted: Moving the meeting one hour earlier, to 15-16 CET time?
Proposal to move it one hour earlier.
Wally: TMC
Meeting notes 2025-06-30
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Trailer proposal by Volvo Group
https://github.com/KAVeenashree/vehicle_signal_specification/tree/features/vehicle/trailerdata
The naming scheme for wheel positions was discussed, one model is shown here:
Summer recess?
Cancelling the next two meetings, July 14 and 28. Next meeting will be Aug 11.
Meeting notes 2025-06-16
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Truck specific data
Main branches in trailer tree?
Meeting notes 2025-06-02
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Truck specific data
Main branches in trailer tree?
Meeting clash with ACEA FMS. Meeting cancelled.
Meeting notes 2025-05-19
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
AMM reflections
Next steps
Focus on truck specific data
Propose via PRs to our Github repo
Get access to the Github repo
Github account
COVESA specific permission needed?
Meeting notes 2025-05-05
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
HIM configurator updates
Supports calling the vspec tool from both Linux and Windows
vspec tool overlays supported
overlays on instantiated nodes supported
Overlays creator tool added
Pick parts of tree from a YAML tree, apply to another tre using HIM configurator overlays.
VSS-core2 added. Uses overlays/instantiation overlays.
VSS-core uses Global / Local variation points.
AMM short f2f meeting?
Can we identify a suitable time?
We meet Wednesday 13.30 at the room where Ulf will present "An Automotive API and Data Model that caters to all types of vehicles" at 14.00.
Meeting notes 2025-04-23
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Traton presents ACEA PoC
Postponed for next meeting
HIM configurator update
Overlays support
Make file usage removed
Meeting notes 2025-04-07
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Continue the Truck tree analysis.
The discussion led to the understanding that any single signal is a potential candidate to be removed, and that there must be a practical solution to that. The VariationPoint feature can do it, but it is not a scalable solution if large numbers of signals needs to be removed.
Different options were discussed, both subtractive (removal from VSS-core) and additive (pick from VSS-core).
The discussion will continue, and hopefully different solutions will be proposed.
Overview HIM configurator features.
Review of the CVIS status AMM presentation (draft version).
Ted: Regulatory signals
Meeting notes 2025-03-24
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
HIM configurator generated Truck tree analysis
Participants asked to look into solutions for the different findings in the list from Volvo.
AMM presentations
"Status update of the Commercial Vehicle Information Specifications (CVIS) project" is scheduled 04:20 - 4:40pm on May 14
"An Automotive API and Data Model that caters to all types of vehicles" is scheduled 02:00 - 2:25pm on May 14
Paul: It is possible to have additional break-out meetings. Please consider the need for this until next meeting.
Overview HIM configurator features
Moved to next meeting.
HIM configurator syntax
Sergej proposed that the vspec2 syntax is extended to support Google template syntax, thus enabling logic operations.
Ulf proposed that this logic is implemented using any computer language in a tool that generates the JSON based input files to the HIM configurator, and keeps the "simpler" syntax in the vspec2 files.
Both proposals can exist in parallel, they will lead to the same end result - configured signal trees in the formats set by the used VSS-tools exporters.
Meeting notes 2025-03-10
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Him configurator on Windows
The setup solution from Traton is found in the Win-setup directory in the CVIS repo.
HIM configurator road map
AMM presentation
VSS-core - no compromises
The VSS-core tree is vehicle type agnostic. The HIM configurator configures it into a vehicle specific tree.
This concept is applicable to most vehicle types like Car, Truck, Bus, Van, etc.
Meeting notes 2025-02-24
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
VSS-core analysis
Look at the cvis.yaml file for ideas on what can be "pruned". Create a PR directly on Github, or a list that we can discuss at next meeting.
Meeting notes 2025-02-10
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Tree partition proposal
Meeting on Wednesday, link found at https://covesa.atlassian.net/wiki/display/WIK4/COVESA+Common+Meeting+Schedule
Decided to try out the idea of a VSS Core tree
AMM presentation: PoC possible?
Requires that any CVIS participant takes it on.
The VISSR tech stack supports a setup like shown in the presented PPT requiring minimal additions.
Paul: Links from FMS discussion with ACEA
Meeting notes 2025-01-27
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Continue the planning from meeting 241202
AMM presentation? Deadline for draft/abstract March 15.
Niklas: Will present some ideas on required signals: Commercial Vehicle data 20250127.pptx
Meeting notes 2025-01-13
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Continue the planning from last meeting
Revisited the presentation from last meeting.
Cut meeting short due to low participation.
Meeting notes 2024-12-02
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Retrospective and planning
Focus on one trailer type initially?
Align with existing trailer interface standards
Leverage existing J1939 VSS mapping
System design
Experimentation
Presentation of the above: CVIS-retrospect-design-experimentation.pptx
Discussion to be continued at next meeting in January.
Christmas recess
Dec16 and Dec 30, back Jan 13
Meeting notes 2024-11-18
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Meeting cut short due to low participation
Meeting notes 2024-11-04
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
VSS car tree vs CVIS truck tree.
Arguments for a separate truck tree
The HIM model supports to rename the root node so that selected parts of the tree can have identical paths with the VSS tree.
The objects branch in CVIS facilitates a structured model for sharing common branches.
Parts of the VSS tree does not relate well to Trucks, e.g. Axle/Wheel configuration.
The HIM configurator provides features not available in VSS-tools, such as the assymmetric matrix configuration.
Decision: We will continue the development of a separate Truck tree.
The scenario where an app developed for passenger cars should also be deployable on a truck will be supported.
Meeting notes 2024-10-21
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Future of the meeting
Volvo: sees interest in defining trees and also in using VISS. Still internal discussion.
GM going through reorg, currently monitoring this group.
Initial conclusion: We will continue the meeting series.
use vsspathlist.json to vet the content of the Truck tree.
Maybe not the right path forward, see question below.
Should a truck use the VSS tree (Vehicle tree) instead of defining a separate tree?
Trailer, Driver, etc. could be separate trees, but Truck should use the Vehicle tree (at least as much as is feasible).
How to resolve major differencies, e. g. the axle/tire location definitions?
Plan for how to create a first version Truck tree (trailer/bus?).
VISSR updated with VISSv3.0 features now supports multiple trees, e. g. Truck tree plus Trailer tree(s).
Meeting notes 2024-09-09
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
use vsspathlist.json to vet the content of the Truck tree.
Cargo location - to be continued.
Example scenario of a truck being loaded?
Next meeting sept 23 is cancelled as it is the same week as the AMM.
Todays meeting was cut short due to low participation.
Meeting notes 2024-08-26
Compliance statement
Welcome and agenda discussion - anything that needs to be added?
Prioritized Topics:
Clarification cargo type and cargo location.
Type: A proposal on howto differentiate between types of trucks (most other features common, but cargo type differs.)
Location: A discussion about how to create a common terminology for cargo location.
Data recorder/Driver data