The SWC starts cleanly while its diagnostics service remains unavailable on the target ECU.
The release needs the existing RTE contract preserved, while target startup must expose the SOME/IP service reliably.
Who you’d be doing this for
“I’ve restarted the ECU twice just to get the status back, and validation is waiting on me.”
Kartini Hashim · Vehicle Software Engineer
Integrates supplier-delivered SWCs into the OEM's diagnostics ECU and needs a trustworthy target build for validation.
What is at stake
The diagnostics status service is missing after target startup, despite the SWC passing in SIL. You must weigh a fast lifecycle configuration change against preserving the customer’s existing RTE contract.
Why it isn’t already fixed
Every obvious fix costs something else. That’s the part you’d have to decide.
- customer contract stability vs startup service availability
- limited HIL time vs repeatable evidence
- fast workaround vs production-like behavior
Why Applied Intuition
Vehicle OS integration depends on customer SWCs behaving consistently from generated AUTOSAR RTE contracts through target ECU validation.
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.