Test Traceability for IATF 16949 with TofuPilot

IATF 16949 requires automotive suppliers to maintain complete test records for every production unit, track measurement system capability, and follow documented control plans. TofuPilot gives you the infrastructure to capture, store, and analyze all of that without building custom tooling.

What IATF 16949 Requires for Test Records

The standard builds on ISO 9001 and adds automotive-specific clauses that directly affect production testing.

Clause 8.5.2 (Identification and Traceability) requires you to identify each product throughout production and retain records that link a serial number to its full test history. Every DUT must be traceable from raw material through final test.

Clause 7.1.5 (Measurement System Analysis) mandates that you study the variation in your measurement systems. You need to demonstrate that your gauges, fixtures, and test equipment produce repeatable, reproducible results. This means tracking Cpk and GR&R across your measurement data over time.

Clause 8.5.1.1 (Control Plans) requires documented control plans that specify what you measure, how often, and what the acceptance criteria are. Your test infrastructure needs to enforce these limits consistently.

How TofuPilot Maps to IATF Requirements

Structuring Tests for Automotive Traceability

Your OpenHTF test should capture the serial number (DUT ID), station identity, operator, and every measurement with its acceptance limits. This gives TofuPilot everything it needs to build a complete traceability record.

import openhtf as htf
from openhtf.util import units
from tofupilot.openhtf import TofuPilot

@htf.measures(
    htf.Measurement("supply_voltage")
    .in_range(minimum=4.75, maximum=5.25)
    .with_units(units.VOLT),
    htf.Measurement("quiescent_current")
    .in_range(maximum=0.012)
    .with_units(units.AMPERE),
    htf.Measurement("output_signal_frequency")
    .in_range(minimum=999.5, maximum=1000.5)
    .with_units(units.HERTZ),
)
def power_and_signal_check(test):
    test.measurements.supply_voltage = 5.02
    test.measurements.quiescent_current = 0.0087
    test.measurements.output_signal_frequency = 1000.1

@htf.measures(
    htf.Measurement("can_bus_response_time")
    .in_range(maximum=10.0),
    htf.Measurement("can_message_checksum_valid")
    .equals(True),
)
def communication_check(test):
    test.measurements.can_bus_response_time = 4.3
    test.measurements.can_message_checksum_valid = True

def main():
    test = htf.Test(
        power_and_signal_check,
        communication_check,
    )

    with TofuPilot(test):
        test.execute(test_start=lambda: "ECU-SN-20260312-0047")

if __name__ == "__main__":
    main()

Every run recorded in TofuPilot links the serial number, station, measurements, limits, and pass/fail verdict into one traceable record.

Measurement System Analysis with TofuPilot

IATF 16949 requires you to prove your measurement systems are capable. TofuPilot tracks every measurement value with its limits across all runs, so you can monitor Cpk directly from the dashboard.

To support MSA, structure your tests so that each measurement name stays consistent across stations and over time. If you measure supply_voltage on Station A and Station B, use the same measurement name on both. TofuPilot's measurement analytics will then show you the distribution, Cpk, and control chart for that measurement across your entire fleet.

You don't need to write Python scripts to compute Cpk or build histograms. TofuPilot's dashboard shows process capability metrics, measurement histograms, and control charts for every measurement name you record.

Control Plan Enforcement

Your control plan defines what gets measured and the acceptance criteria. In OpenHTF, you encode these as measurement limits using .in_range(). TofuPilot stores both the measured value and the limits with every run.

This means an auditor can verify that every unit was tested against the documented limits. If limits change between production batches, TofuPilot's run history shows exactly which limits applied to which units.

Nonconforming Output and Failure Analysis

When a unit fails, IATF 16949 requires you to document what went wrong and prevent recurrence. TofuPilot's failure Pareto chart shows which measurements fail most often across your production. Filter by station, time range, or part number to isolate systemic issues.

Every failed run retains the exact measured values alongside the limits that were violated, giving you the raw data for 8D reports and corrective action records.

Audit Readiness

For IATF audits, you need to demonstrate that your test system captures complete records and that you monitor process capability. With TofuPilot, you can pull up any unit by serial number and show its full test history, measurements, limits, and verdict. The dashboard's FPY trends and Cpk charts provide the ongoing monitoring evidence auditors expect.