AI-assisted inspection can record a dimension accurately and still lead a manufacturer to the wrong conclusion. If a part is checked against an obsolete drawing revision, the instrument, software and report may all be internally consistent while the decision is invalid. Behavioral scientist Gleb Tsipursky argues that this failure mode becomes more consequential as measurement data travels through connected systems, and that manufacturers should attach a “version passport” to every consequential measurement.
The mismatch that correct arithmetic can hide
Tsipursky uses a simple example: an instrument faithfully records a dimension, the software produces a polished report, and the organization receives the wrong answer quickly. The problem is not measurement precision but the reference against which the result is judged. In connected metrology, that reference can move across product definitions, inspection plans and result records. Quality Information Framework data can preserve the identity of a measured characteristic across those stages, but traceability alone does not ensure that each decision follows the correct version of the requirement.
What the passport would carry
The proposed passport need not be a new software platform. It can begin as a set of fields that travel with a measurement: the approved drawing or model revision, the characteristic identifier, the inspection-plan revision, the instrument or method used, the result timestamp, and the identity of the person or system that approved the disposition. The aim is to make the origin and applicable conditions of a result visible to the next decision-maker.
Why AI needs version context
AI can summarize an inspection report, point to an apparent deviation or recommend which cases need review. But a tool that receives results without version context may compare an observation with the wrong specification. The arithmetic can be correct while the conclusion is invalid. Tsipursky notes that the National Institute of Standards and Technology’s 2026 smart-manufacturing roadmap identifies integration of heterogeneous data and trustworthy operation as continuing challenges for industrial AI. A version passport addresses a specific part of that problem by tying a measurement to its governing definition and conditions.
A small test before platform integration
Quality teams can test the idea before adopting a new platform. Tsipursky recommends selecting a small set of completed inspection records that includes one legitimate out-of-tolerance result, one conforming part and one example with mismatched revisions. An AI assistant should be asked to summarize the evidence, identify the applicable revision and flag missing provenance. Its responses should then be compared with an experienced quality engineer’s determination.
He advises against judging the assistant only by how often it labels a part good or bad. More revealing questions are whether it catches a revision mismatch, whether it invents an unstated tolerance, and whether it can point to the approved source behind a conclusion. Those are the errors that digital handoffs often conceal, he says.
Ownership and escalation
Records will sometimes disagree, so ownership should be clear. A quality engineer may determine whether a measurement is valid; design engineering confirms the governing definition; manufacturing determines whether production can continue. The escalation route should be settled before an alert appears, rather than negotiated during a shipment dispute.
Tsipursky also cautions that more AI-versus-human comparisons are not enough. Even perfect agreement between human and automated inspectors can reinforce the wrong decision if both were given an obsolete specification. The reference itself needs scrutiny. Automation can make measurement data travel farther and faster, but a reliable chain of custody must keep the drawing, feature, method and result together when the decision is made.
