Resources |
◎ COVESA Events |
Join/Sign Up |
◎ Join COVESA |
AMM 202510 Technical Track Session Proposals
Session Proposals
This is for Technical Session Presentation Proposals for the Fall AMM in Ann Arbor, MI, October 22 - 23. This list is for those who participate and contribute actively to COVESA Groups and Projects.
Submission Deadline
Deadline for proposals is August 31, 2025
Proposed Session Title | Description | Requested Duration (default is 25 minutes) | Requested Day (Wednesday or Thursday) | Speaker(s) | Comments |
|
|---|---|---|---|---|---|---|
EXAMPLE:
Learning VSS: A Deeper Dive | Taking the next steps with your understanding of VSS. Learn from the pros as they walk through some how-tos. Get your questions answered and learn how to get involved. | 40 | Wednesday | @Sebastian.Schildt @adnan.bekan@bmwgroup.com @Erik.Jaegervall@se.bosch.com | What worked well last time? What could be better? |
|
Optimizing VSS data storage with NoSQL document databases | As connected vehicles generate an ever-growing volume of data, structuring and managing this information efficiently becomes critical. VSS provides a standardized way to define vehicle data, but how should it be stored in a database to ensure scalability, reliability, and optimal performance? This session explores design patterns for storing VSS data in NoSQL document databases, focusing on real-world use cases such as fleet management systems. By analyzing access patterns and read/write frequencies within the VSS model, we can optimize storage efficiency and query performance. By the end of this session, attendees will gain practical insights into data storage strategies for VSS data. | 40 | Wednesday | Proposal sent to @sschmitt on July 30th 2025 |
| |
VISS and VISSR Status Update | Key points in the latest development of the VISS specification and its reference implementation VISSR are reported. | 25 |
| @Ulf Bjorkengren | Speaker will be remote. |
|
VAPI – a connectivity agnostic API for signal and service access | VAPI abstracts the details of the underlying connectivity solution, allowing for implementations of the API that uses different connectivity solutions. | 40 |
| @Ulf Bjorkengren | Speaker will be remote |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
—