Catching AUTOSAR compliance problems while the code is written
Read the full post on AWS BlogAutomotive software has a documentation problem before it has an AI problem. Developers document, review and test every code change against standards like AUTOSAR, and even a small update can touch hundreds of files. They usually find out whether they got it right at the very end, when the compliance tools run and send them back to fix things.
AUMOVIO, the company Continental's automotive technology business became, builds a development platform on AWS called vSDV Composer that replaces physical test hardware with virtual ECUs. We worked with them on the engineering assistant inside it. It runs on Amazon Bedrock, and AUMOVIO trained it on their own knowledge base, covering more than twenty years of embedded source code and process documentation.
What makes it useful is how narrow it is. A general coding assistant has no opinion about AUTOSAR, while this one flags likely compliance problems in the IDE, while a developer is still writing the code, instead of at the end of the pipeline. Moving that feedback earlier is the whole point, since the cost of a compliance error is mostly the round trip rather than the fix. AUMOVIO reports the platform accelerating development by more than 50%.
Where this is heading is agents coordinating across organizations rather than within one tool, so an ECU project could pull in validation agents from its suppliers over protocols like A2A. That is harder than it first sounds, because the interesting part isn't the message format. It's working out whose answer to trust.
