Why VDA 6.3 is a maintenance problem, not just a quality one

VDA 6.3 evaluates the manufacturing process across the product lifecycle, and several of its question blocks land squarely on maintenance: equipment capability, tooling and equipment maintenance, and the handling of deviations. Auditors increasingly expect to see that maintenance is risk-based and evidence-backed, not calendar-driven habit.

The practical test is simple: an auditor points at a machine on your critical-to-quality list and asks to see its maintenance history, calibration status, and what happened the last time it drifted out of tolerance. If that takes you twenty minutes and three systems to answer, you have a finding waiting to happen.

Start with asset criticality

Map the equipment that can stop flow, create a quality escape, or create a safety risk. The audit pack should make it obvious why those assets receive tighter maintenance control than the rest of the floor.

A defensible criticality model considers at least these dimensions:

  • Quality impact: can a failure produce nonconforming product that could reach the customer?
  • Production impact: does failure stop a line or create a bottleneck?
  • Safety and environmental impact of failure.
  • Detectability: would the failure be caught before it matters?

Criticality is what justifies your PM frequencies and spare-parts decisions. Without it, every interval looks arbitrary to an auditor.

Tie PM evidence to the actual work

A blank checklist proves nothing. What holds up in a VDA 6.3 audit is the completed task tied to the asset record: who did it, when, the readings captured, the photos, any deviation raised, and the follow-up work that resulted.

For each critical asset, be ready to show the PM schedule and its basis, the last several completed PMs with timestamps and technician identity, the readings or measurements captured, and the current PM compliance rate. When that evidence is assembled as work is done, the audit pack is a byproduct rather than a fire drill.

Close deviations visibly

Deviation handling is where teams most often lose points. When a reading is out of tolerance or an inspection fails, the auditor wants to see the deviation captured, the containment, the corrective action, and verification that it worked, all linked in one chain.

The failure mode to avoid is a deviation logged in one place and the repair logged in another, with no link between them. Keep the deviation, the corrective work order, and the closeout evidence connected to the same asset so the loop is visibly closed.

Calibration traceability

Instruments that verify product or process quality need documented calibration: tolerances, certificates, due dates, and a clear status. An overdue calibration on a critical gauge is an easy, avoidable finding.

Be able to answer, per instrument: what is the tolerance, when was it last calibrated, against what standard, what is the certificate, and when is it next due.

Assemble the audit pack before you need it

The goal is to walk into the audit with the evidence already assembled by asset: maintenance history, PM compliance, calibration certificates, deviations closed, and the photos and readings that back them. A CMMS that captures this as work happens turns a multi-day scramble into a one-click export.