Industries
AUT · DACH
Automotive
Faster release,
same audit trail.
OEMs, tier 1 and tier 2 suppliers and the aftermarket. Margins under pressure, the shift to electric, and every customer asking for TISAX.
01 · Topics
What keeps
you busy.
The topics that come up first when AI meets this industry. If one sounds familiar, that is where we start.
- 01Margins shrink, requirements grow
Price-down clauses every year, while specifications, variants and documentation keep growing.
- 02Specifications nobody reads twice
Customer requirement documents run to hundreds of pages. Deviations are found late, sometimes at the audit.
- 03Security is a delivery condition
Without TISAX and a cybersecurity story for the vehicle, there is no nomination. AI tools have to fit into both.
02 · Examples
Where AI
earns its keep.
Input, action, result. The places we would look first, because the work is repetitive, the data exists and a person still signs off.
- 01Requirement analysis
Customer specification → requirements extracted and compared with your standard → the engineer reviews the list of deviations.
- 028D and complaint handling
Complaint and field data → similar past cases and root causes → a draft 8D report the quality team completes.
- 03Supplier risk monitoring
News, delivery data and financial signals → early warnings per supplier → purchasing decides, with the source attached.
- 04Engineering assistant
Standards, test reports and past projects → answers with document and page → faster onboarding for new engineers.
sample Illustrative examples, not client references.
03 · The rules
What applies,
and since when.
The rules we plan around in this industry. With the source, so your legal team can check our reading.
- 01Vehicle AI goes through type approval
For vehicles, the AI Act works through type-approval law: its high-risk requirements are built into the implementing acts under vehicle regulation.
Art. 2(2), Annex I Section B AI Actwith the vehicle acts - 02Cybersecurity and software updates
New vehicles need a certified cybersecurity management system and a software update management system. Suppliers deliver part of the evidence.
UNECE R155, R156since July 2024 - 03TISAX as a delivery condition
German OEMs typically require a TISAX label from suppliers who handle their information. AI tools that process that information are in scope.
VDA ISA, ENX TISAXby contract - 04NIS2 for vehicle manufacturers
Manufacturers of motor vehicles, trailers and parts above the size thresholds must register, manage cyber risk and report incidents.
NIS2UmsuCG, BSIGsince 6 December 2025
Not legal advice Our reading as of September 2026, not legal advice.
04 · Clients
Worked with.
Names from voidgap.com. Some clients cannot be named; their work appears as anonymised cases.
05 · Services
Where to
start.
Build, Secure, Comply, Enable: the four services we would start automotive projects with.
06 · Next steps
What happens
after you send it.
Four steps between your request and a decision. No step commits you to anything.
- 01 You send the requestThree questions about your situation, then your contact details. It takes a few minutes.
- 02 We read it and replyA person reads your answers and replies by email, with questions or a proposal for a first conversation.
- 03 First conversationYour use case, your data, the rules that apply. Afterwards you know whether and how to start.
- 04 Written proposalIf it fits: scope, approach and effort in writing. You decide.
07 · Download
Take it
with you.
For your team, as a PDF. Leave your email and we send it to you.
In preparation
Checklist: AI tools in a TISAX environment
The questions assessors and OEM customers ask when AI processes their data.
What is inside
- Which AI tools touch customer information
- What to document for the next assessment
- Where cloud models are acceptable and where not
The PDF is being prepared. Request it now and you get it as soon as it is ready.
08 · Request
Tell us
where it hurts.
Three short steps. Your answers help us prepare the first conversation for your case.
- 01Your situation
- 02Your project
- 03Contact
09 · Questions
Questions
from this industry.
Short answers. Anything else goes into your request.
Can we use cloud AI with OEM data?
That depends on the contract and the protection level. We check the requirements first, then choose between cloud, private cloud and on-premises models.
Our engineers use chatbots privately. Is that a problem?
It can be, if customer data goes in. A clear policy, an approved tool and short training usually do more than a ban.
How long until a first use case runs?
That depends on data access and approvals. We agree the scope and the criteria for going live before we start building.
Automotive
Your spec,
your void.
Tell us where it hurts. We check which rules apply before the first line of code.