The shared integration date pulls against proof that diagnostic access remains bounded after restart.
The OEM needs the legacy ECU connected on schedule, while the platform needs evidence that authorization survives the restart sequence.
Who you’d be doing this for
“I can show the service reconnecting, but nobody can tell me why that request got through.”
Rajesh Dutta · Vehicle Software Engineer
Integrates legacy ECU diagnostics with the vehicle software stack for an OEM production program.
What is at stake
An unauthorized diagnostic request succeeds after some legacy ECU restarts, despite passing clean-boot checks. You must weigh the scheduled integration against security evidence that is costly to reproduce.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- integration date vs. diagnostic access control
- automated findings vs. target-verified evidence
- shared platform reuse vs. configuration isolation
- recovery options vs. release-time assurance
Why Applied Intuition
Vehicle OS joins legacy ECUs to service-oriented software, making diagnostic boundaries part of the production platform promise.
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.