01
Test programme design
What gets tested, in what order, against which acceptance criteria. A run plan that survives a bad day and a wet track.
01 / OEM support
The makers who call us are not starting from nothing: they have prototypes running, a department at work and a launch date. What is missing is the piece that turns test sessions into decisions.
The point
Testing produces data. Data does not produce decisions on its own.
The gap is almost always between the session and the next change.
A development programme generates more data than anyone can read. Acquisition is rarely the problem: the problem is deciding what to look at, in what order, and what you are willing to make worse in order to make something else better.
Here the difference between racing and production is timing, not method. In competition the window between one test and the next is measured in hours, so a method for deciding quickly already exists and has been proven. That is what we bring into production programmes.
We do not replace the in-house department. We work next to the people who are already there, with their tools, and we leave the method where it belongs: inside the company.
What we do
On the programme, not beside it.
These combine. Almost no client takes just one.
02
Running the sessions
Our people trackside with yours. Decisions taken during the session, not in a meeting the following week.
03
Vehicle dynamics targets
The character the maker wants, translated into measurable quantities. Skip this step and every discussion is about taste.
04
Simulation, rig and track correlation
Multibody model, test rig and the real car brought to say the same thing. This is the work that makes everything else useful.
05
Benchmarking
Instrumented comparison against the reference cars in the segment. Not press impressions: channels, not adjectives.
06
Training the test group
Working alongside your engineers, plus written procedures, so the method stays when the programme ends.
Engagement
Three depths.
You can start at the first level and move up. It has never gone the other way.
| Level | When it makes sense | Typical duration | What the client keeps |
|---|---|---|---|
| Technical audit | There is a behaviour nobody can explain and an outside read is needed | 3–6 weeks | Technical report with priorities and proposed work |
| Embedded support | The department exists; trackside method and correlation are missing | 6–18 months | Procedures, correlated models, trained people |
| Programme responsibility | Vehicle dynamics development needs to be led from outside | 18 months and beyond | Car on target, full documentation |
How it starts
The first eight weeks.
NDA and material
Confidentiality first. Then existing data, test history and whatever targets are already written down.
Week 1Technical read
What the data you already have is saying. Often the first answer is in there and nobody went looking.
Weeks 2–3Joint session
A day at the track together, with a written plan and acceptance criteria agreed beforehand.
Weeks 4–6Programme plan
Priorities, timing, resources and what we need from you. From there you decide whether and how to continue.
Weeks 7–8A model that has never been correlated against the track is not a model: it is an illustration.
Working principle, on every programme
Questions
What people ask before signing.
Do you work with makers outside Europe?
Yes. In that case English is the working language and technical documentation is delivered in English as standard.
On distant programmes we concentrate trackside presence into blocks: fewer trips, longer and denser sessions. It works better than thin, continuous presence.
Do we need an in-house development department already?
No, but it changes the shape of the engagement. With a department in place the work is about method and correlation. Without one, the minimum structure gets built first: who acquires, who decides, who documents.
In both cases the stated goal is that the client can do the next round alone.
How do you handle confidentiality on an unannounced prototype?
NDA before any data, and before the first technical call if you want it that way. No images, no public reference, no names in our commercial material.
The references we publish are only ever the ones a client has authorised in writing.
Does this apply to electric cars?
Yes, and it is a growing part of the work. Vehicle dynamics does not change in nature: what changes is mass, distribution, torque management and the way traction limits what the motor could deliver.
The rest — kinematics, tyres, aerodynamics, correlation — is identical.
First step
Send us the data from your last session.
A technical read of existing material is the fastest way to find out whether we have anything to say. If we do not, we say so.