Wednesday, June 3rd
10:00 – 11:00 CET (Berlin) / 4:00AM EST (Detroit) / 13:30 IST (Bangalore) / 16:00 CST (Beijing)
15:00 – 16:00 CET (Berlin) / 09:00AM EST (Detroit) / 18:30 IST (Bangalore) / 21:00 CST (Beijing)
AI is entering automotive software development in waves – from chat assistants on the engineer’s desk, to AI agents that orchestrate verification, to AI-generated production code, and finally to machine-learning models running inside the vehicle itself. Four very different problems share the same label – and the verification question is different at every level.
Building on our previous sessions on Generative AI-powered test authoring and MCP integration, Leif Driebold and Markus Gros are back to give you the bigger picture. Together they will walk through the four levels of AI adoption in the automotive engineering process – Co-Pilot, Process Automator, Code Generator, and In Vehicle – and explore what each level demands from verification, where BTC EmbeddedPlatform fits in, and why a single verification toolkit can serve all four.
What you’ll learn: The four levels of AI adoption in automotive software development – and why “AI” means something different at each one
- Level 1 – Co-Pilot: where generative AI actually pays off in daily engineering work today
- Level 2 – Process Automator: what changes when AI moves from generating text to calling tools – and the role MCP plays
- Level 3 – Code Generator: AI writes the production code – so where does the trust to ship it come from?
- Level 4 – In Vehicle: machine-learning models inside the product (not LLMs) – how do you verify what cannot be fully predicted?
Join us for a live walk-through of all four levels in BTC EmbeddedPlatform – and a concrete view of where AI in automotive engineering is heading.