Vehicle architecture / 22 applications
Where AURIX sits in the car.
Functions consolidate into a few zone controllers wired to central compute. Fewer, larger nodes — which is what pulls the portfolio towards TC4x.
About this view
AURIX application (rank-1 fit)zone backbone
Best technical fit among eligible AURIX devices in this project's own scoring against public product pages — not market share.
Flagships are the devices Infineon puts forward for each domain on infineon.com — the vendor's positioning, not this tool's fit ranking. The dots on the car show rank-1 fit per application.
Schematic, not a teardown. Positions show where these functions typically sit in a generic vehicle — they are illustrative and are not taken from any specific car, platform or wiring diagram. The car is generated for this page; it is not any manufacturer’s vehicle.
Not drawn: Cockpit domain controller, Central vehicle compute node (10G backbone) — no public AURIX device qualifies (a portfolio gap, argued on /market).
Start here
One requirement, seven stages.
This screen is stage one: it says where a function sits and which device leads it today. The rest of the suite qualifies a specific customer requirement against that portfolio and writes the decision up so someone can sign it.
- 01Where it sits
Which vehicle function are we qualifying for?
Places the requirement on the car and names the leading device for that socket.
Architecture → - 02What was asked
What exactly did the customer require?
Extracts the RFQ into numbered requirements, each quoting the customer and carrying a must/should/nice priority.
Qualification → - 03What disqualifies
Which candidates fail a hard constraint?
Applies hard gates — a missing must-have interface or ASIL level is out at any score, never averaged away.
Qualification → - 04What fits best
Among the survivors, which scores highest, and why?
Scores every eligible device on weighted factors, each factor carrying its own reason.
Qualification → - 05What proves it
What public source backs each claim?
Attaches a cited source to every claim, and says verify — not a number — where the public data is silent.
Qualification → - 06The decision
What do we recommend, and what do we refuse to answer?
Emits the decision record — or 'no validated match' plus the exact gap that blocks one.
Qualification → - 07What it's worth
Why does the customer care, and who else is bidding?
Turns technical fit into customer value, names the competition, and sets the design-win action.
Market & GTM → - The shape of it
One requirement, seven stages: place it on the car, extract what was asked, disqualify what cannot work, score what is left, cite the source for every claim, translate the fit into customer value, and write the decision — including what it refuses to answer.
How it works →