Episode 01
From vehicle concept to approval plan
Three markets, shared test vehicles, one market launch.
View episode 1Planning software for homologation
See early which approval puts your market launch at risk.
XORPunkt brings all tests, test vehicles and dates across your target markets into one plan. When something changes, it shows at once which market launch is slipping.
For homologation teams at manufacturers of passenger cars, commercial vehicles and L-category vehicles. We set up XORPunkt with you and run it.
How it works
One plan for all markets. It recalculates when something changes.
- 1
Your data
Market plan, test planning and dates come from your existing systems. Requirements come from your regulatory feed.
- 2
One plan
Which test when, on which test vehicle, at which technical service, and how much time is left until market launch. For every target market.
- 3
A change
A new software release, a test report, a moved test date: the plan recalculates the impact at once. Your team decides, and every decision stays traceable to its origin.
Numbers come from rules. Proposals come from AI. Your specialists decide. AI never changes data.
Example
XR 01: two events, three weeks less time.
XR 01 is our fictional test programme: a three-wheeled vehicle, three markets, EU market launch in October 2027. All figures on this page come from it.
- 4 weeks
Plan in place.
Time to spare before EU market launch.
- 3 weeks
New software release.
The emissions test needs it.
- 1 week
Noise test missed by one decibel.
Fix and repeat.
Neither event looked like a crisis. XORPunkt shows the impact with the finding, not in the next status meeting.
XR 01, episode by episode.
Episode 02
38 changes. Which one moves a date?
From a software revision to expert assessment and schedule impact.
View episode 2
Episode 03
Can one decibel stop homologation?
A failed noise test: three markets, three answers.
View episode 3Situations from the programme
What your team asks. What XORPunkt shows.
“The new software release is coming. Do we need to retest, and does the date hold?”
Trigger: a software release after the test scope was approved.
Instead of an email round through the specialist teams: every change item checked against the running tests, with reasoning.
38 change items, 2 touch a test, 1 moves a date: one week less time. The other 36 are listed with their reasoning.
View episode 2“Noise failed. Which markets depend on it?”
Trigger: a test report above the limit.
Instead of calls between test department and markets: every affected market at a glance.
81 dB(A), limit 80. EU and UK wait for the repeat test, US is not affected. Still open: whether the new damper touches the emissions test.
View episode 3“The authority has a question. On what basis did we decide this?”
Trigger: a request after submission.
Instead of searching emails and minutes: every decision in the history, with its origin.
The route was agreed with the technical service at Gate 2 and documented. Statement within three days.
“The technical service moved our test date. Does the vehicle now sit idle for three weeks?”
Trigger: a new date confirmation.
Instead of replanning by hand: the plan moves the dependent tests and proposes what fits into the waiting time.
Brakes, lighting and belt anchorages move into the waiting time. No effect on the approval.
Synthetic programme XR 01.
What XORPunkt does
We plan. Others interpret the regulations.
Requirement tools
From clause to requirement, from requirement to test, from test to evidence.
XORPunkt
From test to test vehicle, to slot, to date and to market launch.
Your requirements and tests are our input. Regulations stay in the regulatory feed, documents in the document system, submission in its own solution. XORPunkt shows status, origin and decisions, never document contents.
Why now
The plan doesn’t end at the approval.
Homologation used to be a milestone before market launch. It is becoming an obligation across the vehicle’s life.
Software after launch
Software updates after launch must be assessed against existing approvals. For passenger cars and commercial vehicles, UN R156 requires a process that checks every update for whether it affects the type approval. UN R155 covers cyber security.
Follow-up obligations
Approvals can come with conditions, for example a re-inspection after the first year in service. They need a date, an owner and evidence like any test.
Rulebooks per market
The EU and UNECE work with type approval, the UK with its own procedure, the US with self-certification by the manufacturer. One vehicle, several rulebooks, one plan.
The work now grows with every vehicle in the field and every software release, not only with every new type.
One programme. Eight weeks. Fixed price.
We take one of your running programmes and plan it in XORPunkt with your data. At the end, you decide on measured values.
- You provide
Exports from the market plan, test planning and dates. Two contacts from homologation, about two hours a week each.
- You get
Your programme as a running plan across all target markets. A weekly status with time left per market. The four measurements against your baseline.
- At the end
You decide on rollout, integration and operation. No obligation without proven value. We agree the fixed price before the start, based on the size of the programme.
What we measure against your baseline
- Time from a change to an updated plan
- How early a launch risk becomes visible
- Hours spent compiling status
- Number of status meetings
No savings figure before we know your baseline.
Who is behind it
You speak directly with the people responsible.
Lorant Zambori
Co-Founder and Managing DirectorEx-BCG. 20+ years in IT and digital product development. Automotive platforms, AI systems, regulated environments.
Andreas Lange
Chief Sales Officer25+ years in automotive and defense. OEM and Tier-1 background. Connected vehicle services, aftersales, diagnostic and programming solutions for dealers.
XOR Digital GmbH, Olching, Germany. We build and run XORPunkt ourselves. Member of Cluster Mobilität, Bayern Innovativ.
Which approval date is critical for your programme?
Let’s discuss your programme, the outstanding prerequisites and the workflow that takes most of your team’s time.
TÜV SÜD Fachtagung Homologation, 16 to 17 November 2026, Fürstenfeldbruck: meet us at the stand or book a call.
Book a call
30 minutes. We show XORPunkt with XR 01 and look at your next programme together.
or by email: hello@xordigital.de