Resources |
◎ COVESA Events |
Join/Sign Up |
◎ Join COVESA |
2026-02-16 GenAI WG Working Session
Working Session - February 16, 2026
Date: Monday, February 16, 2026
Time: 4:00 PM CET / 10:00 AM ET / 7:00 AM PT
Type: Working Session
Join Information
Zoom Meeting:
https://us06web.zoom.us/j/89994460240?pwd=DRNueiBANbsdgYqpndnS0h2gNBLs86.1&jst=2
Passcode: 118634
Agenda
Playground: discuss proposal from Chaitanya and Stephen
Use of GH Project
MCP Proposals
1. VSS MCP Server
The Vehicle Signal Specification (VSS) is a domain taxonomy for vehicle signals used to create a common understanding across the automotive industry. VSS is authored in .vspec files using a YAML-based format and processed by vss-tools to generate various output formats (JSON, GraphQL, Protobuf, etc.).
Use-Case Narratives
1. Onboarding New Contributors
As a new member contributing to COVESA VSS,
I want an AI assistant that understands VSS syntax and conventions,
So that I can quickly learn how to author valid signal specifications without extensive manual reading.
2. Format Conversion and Integration
As an integration engineer,
I want to convert VSS to/from my target format (DBC signals, Excel, Protobuf/GraphQL/DDS)
So that I can integrate contribute to VSS or convert to my domain format.
User Journeys
Journey 1: First-Time Contributor (Onboarding)
Step | User Action | AI/MCP Action | Expected Outcome |
|---|---|---|---|
1 | "I need to add a temperature sensor for the cabin air quality system" | Uses | Lists existing temperature sensors with examples |
2 | Reviews examples, asks "What's the correct structure?" | Uses | Explains datatype (float), unit requirements (celsius/fahrenheit), range guidelines |
3 | "Create the YAML for me" | Uses | Generates compliant YAML snippet |
4 | Copies YAML to file, asks "Is this valid?" | Uses | Validates and confirms compliance OR provides specific error messages |
5 | Commits code | - | Confident first contribution ✅ |
Proposed: vss_search_signals, vss_get_schema_rules, vss_generate_signal, vss_validate_file
Journey 2: Format Conversion (Integration)
Step | User Action | AI/MCP Action | Expected Outcome |
|---|---|---|---|
1 | "I need VSS signals in Protobuf format" | Uses | Shows available export formats |
2 | "How do I export to Protobuf?" | Uses | Explains protobuf exporter options |
3 | "Export cabin signals to protobuf" | Uses | Generates cabin.proto file |
4 | "Is the output valid?" | Uses | Confirms valid Protobuf syntax |
5 | "Show me how to use this in my code" | Provides integration snippet from knowledge | Example Protobuf usage code |
Proposed: vss_list_exporters, vss_get_exporter_info, vss_export_format, vss_validate_export_output
Meeting Attendees:
Yansong Chen, Georg Doll, Michael Nunnery, Chaitanya (Ford), John Stenlake (Microsoft), Josef Mleziva, Sri Palacharia (GM), Stephen Jiggins (Useblocks) Tim Welsch (Aptiv), Ragip Selcuk
Session Notes:
Reviewed proposed VSS use case - VSS tool is in GitHub (link below), next step write the MCP tool to connect.
Agent instructions for authoring.
mcp tool wrapper for vss-tools -
CAN DBC, gRPC protobuff, JSON files - Chaitanya
