Operations · Guide
Right number, wrong dimension: give AI a unit contract
A fictional purchasing drill checks source units, conversion direction and destination fields before AI fills an order.
Right number, wrong dimension: give AI a unit contract
Original AAHouse explanatory video. AI-assisted conceptual visuals and neural narration; original music.
English transcript · Simplified Chinese Mandarin transcript · Taiwan Mandarin transcript · Hong Kong Cantonese transcript · Macao Cantonese transcript
A purchasing drill: how long is 18?
Imagine a U.S. sign shop receiving a request for a panel “18 inches wide.” An AI assistant copies 18 into a purchasing form whose width field expects millimeters. The digits are correct; the meaning is not. This is a hypothetical tabletop exercise, not a reported customer incident. Before enabling automatic form filling, ask where each unit comes from and who confirms the converted result.
Explanatory diagram redrawn from the approved article.
Round one: capture four separate fields
Preserve the original wording, numeric value, unit, and measured property, such as “panel width: 18 inches.” NIST’s conventions connect a quantity value with its unit; 18 alone is not a complete dimension.[1] Our recommendation is to retain the document location and destination field definition too. Do not infer inches from a customer’s U.S. address or discard the unit because a database accepts only numbers.
Explanatory diagram redrawn from the approved article.
Round two: check the conversion direction
NIST defines one inch as exactly 25.4 millimeters. Therefore, the example’s 18 inches converts to 457.2 millimeters.[2] Use deterministic code and a reviewed rule for the calculation; let AI extract and explain rather than choose its own factor. If the receiving system already converts the value, multiplying again is an error. Record the source unit, destination unit, and conversion-rule version.
Explanatory diagram redrawn from the approved article.
Round three: agree on machine-readable units
For system-to-system exchange, consider an agreed, controlled unit vocabulary. UCUM is designed for unambiguous electronic communication of quantities together with their units.[3] That does not mean every supplier supports it or that every company must adopt it. Define accepted codes, letter case, and aliases at the interface. Route unknown units for human review instead of asking a model to improvise a plausible mapping.
Explanatory diagram redrawn from the approved article.
Round four: conversion does not improve measurement
The practical distinction is between calculation and measurement: an exact conversion factor cannot make the original measurement more precise. Here, 457.2 is a mathematical conversion, not a claim that the panel was measured to a tenth of a millimeter. Record dimensional tolerances, display rounding, and downstream precision requirements separately. Do not turn a rounded display value into a production instruction without the responsible person’s confirmation.
Explanatory diagram redrawn from the approved article.
Finish with tests that can stop the workflow
Proposed acceptance cases use four fictional orders: 18 inches maps to 457.2 millimeters; 18 millimeters remains 18; a missing unit pauses processing; an area unit supplied to a length field is rejected. These are recommended tests, not results from a customer system. Enable automatic filling only after the purchasing owner confirms destination fields and exception handling. Actual ordering remains subject to the existing approval process.
Explanatory diagram redrawn from the approved article.