Legacy SOME/IP services must move toward zonal compute without forcing every customer to rediscover the DDS bridge.
A reusable bridge pattern protects faster integration, while customer-specific architecture choices resist premature standardization.
Who you’d be doing this for
“Every service starts as a fresh mapping exercise, and my CI run tells me too late what I missed.”
Maung Ahmad · Vehicle Software Engineer
Maps legacy ECU services into the OEM’s new zonal controller environment.
What is at stake
OEM engineers spend two to five days mapping each legacy SOME/IP dependency into a zonal controller. You must weigh reusable defaults against the architecture choices each customer must keep.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- reusable defaults vs customer architecture control
- fast first integration vs durable deployment pattern
- DDS portability vs production-relevant configuration
Why Applied Intuition
Vehicle OS combines AUTOSAR Adaptive, SOME/IP, DDS, and code-first tooling where OEMs are bridging legacy ECUs to centralized compute.
Written with these in mind
Not your kind of problem? 65 more at Applied Intuition, or browse every organization.
This is the setup. The work is inside.
Running it puts you in the room: the full situation and its constraints, stakeholders who push back in their own words, and the decisions that are yours to make. What you produce becomes a Day One Plan — work you can show someone instead of describing.