3. Technical coordination fundamentals
In automotive product development, a CAE team rarely fails because its solvers are inaccurate. It fails because its results arrive at the wrong time, in the wrong format, or against the wrong question. Technical coordination is the discipline that prevents this. Its central mechanism is the alignment of CAE deliverables with the vehicle development milestones and gate reviews that govern the program. A CAE manager who understands this alignment can convert simulation from a late-stage verification activity into a decision-support function that shapes the vehicle before tooling is committed.
Milestones, Gates, and the Decision They Encode
A vehicle program is structured as a sequence of phases separated by gate reviews. Although naming conventions differ between OEMs, the underlying logic is stable. A typical passenger-car program moves through a concept or target-setting phase, a concept freeze, a detailed design phase, a design freeze, a validation phase, and a production launch. Each gate is not a progress report; it is a decision point where a defined set of evidence must exist before the program is authorized to spend the next tranche of money.
The critical insight for a CAE lead is that gates are funded decisions, not technical reviews. At a design freeze gate, the program is effectively deciding to release CAD for tooling. Once that decision is made, a body-in-white (BIW) stiffness shortfall or a crash-pulse violation becomes a change order with tooling cost, not a simulation iteration. Therefore, the CAE deliverable that matters at a gate is the one that answers the gate's specific question with enough confidence to release the next phase.
| Program phase | Typical gate | Gate decision | CAE evidence expected |
|---|---|---|---|
| Concept / target setting | Concept gate | Approve architecture and targets | Concept-level CAE: global bending/torsion stiffness, frontal crash pulse estimate, mass breakdown |
| Detailed design | Design freeze | Release CAD for tooling | Full-vehicle crash (frontal, side, rear), BIW modes, durability load cases, thermal |
| Validation | Validation gate | Confirm compliance and sign-off | Correlation to physical test, final CAE sign-off report, regulatory evidence |
| Launch | Launch gate | Authorize production | Change-impact assessments, open-issue closure, as-built model status |
The table above is a representative structure, not a universal standard. The essential coordination task is to map the CAE team's internal model maturity against these gates. A common failure mode is a mismatch of maturity: the program expects a full-vehicle crash result at design freeze, but the CAE team is still building the BIW mesh. Coordination means negotiating that expectation early, not discovering the gap two weeks before the gate.
The Deliverable Maturity Ladder
CAE deliverables are not binary. They progress through a maturity ladder, and each rung supports a different level of decision. A useful coordination framework distinguishes four levels:
- Level 1 — Directional: coarse mesh, simplified load paths, used to compare concepts and set targets. Suitable for concept gates.
- Level 2 — Design-support: detailed mesh, representative boundary conditions, used to guide geometry and gauge selection. Suitable for design iterations before freeze.
- Level 3 — Verification: production-intent mesh, validated material cards and boundary conditions, used to demonstrate compliance. Required at design freeze and validation gates.
- Level 4 — Correlation: model updated against physical test data, used for sign-off and for future program carryover. Required at validation gate.
When a CAE lead presents a Level 2 result at a gate that requires Level 3, the gate decision is made on insufficient evidence. The coordination discipline is to state the maturity level explicitly in every deliverable and to refuse to let a gate proceed on a lower level than its decision requires. This is a technical-integrity position, not a bureaucratic one.
Coordination rule of thumb: the maturity level of the CAE evidence must be at least the maturity level of the decision the gate is making. A tooling-release decision requires Level 3 evidence. A concept-selection decision requires only Level 1.
Building the CAE Milestone Plan
The practical instrument of alignment is the CAE milestone plan, sometimes called the simulation timing plan. It is a backward-scheduled document: it starts from the gate date and works backward through the CAE workflow to determine when each input must be frozen.
Consider a design freeze gate scheduled for week 40 of the program. A full-vehicle frontal crash model requires a frozen BIW geometry, a finalized restraint system, and validated material cards. Working backward:
- Gate review and sign-off report: week 40.
- Final CAE result review with the program: week 38.
- Crash simulation run and post-processing: weeks 35–37 (allowing for one re-run).
- Model build and quality check (free-free modes, mass, penetrations): weeks 32–34.
- Geometry and restraint data freeze: week 31.
- Material card validation and boundary-condition sign-off: week 30.
This backward schedule reveals the true critical path. If the BIW geometry is not frozen by week 31, the crash result cannot be delivered at the gate. The CAE lead's job is to make that dependency visible to the program manager in week 20, not week 32. Coordination is largely the management of these upstream dependencies.
Gate Review Participation: What the CAE Lead Actually Does
At the gate review itself, the CAE lead's role is not to present every result. It is to answer three questions the gate decision depends on:
- Compliance: Does the current design meet the regulatory and internal targets for the load cases relevant to this gate? State the margin, not just pass/fail.
- Confidence: What is the maturity level of the evidence, and what are the known model limitations? A result with 5% margin and an unvalidated material card is not the same as a result with 5% margin and a correlated model.
- Risk: What open issues could invalidate the result before the next gate, and what is the mitigation plan?
A common coordination failure is presenting a large result deck that answers none of these three questions directly. The gate committee needs a one-page summary: target, result, margin, maturity level, open risks. The detailed deck supports the summary but does not replace it.
Practical technique: maintain a gate-readiness tracker that lists every required CAE deliverable, its maturity level, its owner, and its status (not started / in progress / complete / at risk). Review it weekly with the CAE team and biweekly with the program. The tracker converts coordination from a series of surprises into a managed process.
Handling Change and Late Inputs
Vehicle programs change. A styling surface is revised, a supplier changes a material, or a regulation is updated. Each change propagates into the CAE model and threatens the milestone plan. The coordination response is a change-impact assessment: for each change, determine which CAE deliverables are affected, whether the maturity level can still be achieved by the gate, and what the schedule impact is.
For example, if a BIW gauge change is proposed in week 33 for a design freeze gate in week 40, the crash model must be rebuilt and re-run. If the change is localized and the model is parametric, the re-run may fit within the existing window. If the change affects the front structure and requires a new mesh, the gate date is at risk. The CAE lead's job is to quantify that risk and present options: accept the change and slip the gate, defer the change to post-freeze with a change order, or run a reduced-scope assessment at a lower maturity level with explicit caveats.
This is where technical coordination becomes a leadership function. The CAE lead is not merely reporting simulation results; they are translating simulation maturity into program risk and helping the program make an informed decision. The alignment of CAE deliverables with milestones and gates is, in the end, the mechanism by which simulation earns its seat at the decision table.