OEMs do not share one functional boundary for the same automation level

What it is

SAE J3016 is a taxonomy of control allocation, not a checklist each OEM must implement as the same feature set. Features all called Level 2 may require hands on the wheel and only follow-and-center in-lane, or may allow long hands-off stretches on selected roads, lane changes, and some signalized intersections. Conditional Level 3 is further bound to geofence, weather, and speed, and in user language may be indistinguishable from a neighbor’s “enhanced assist.” Across brands, model years, and even software versions of one brand, the same level name does not carry the same capability envelope. This entry is the inconsistency itself. It is not why mode confusion is the ceiling risk, and not the most common consequence once a person has already misread the mode.

Why it happens

A level name is a compressed label. What the compression drops is the operational design domain: which roads, how much speed, whether hands must stay on the wheel, whether the system will change lanes by itself, whether the person may legally look away at exit. OEMs compress again with trademarks (the various Pilots, Cruises, Assists). The trademark is easier to remember than an SAE number and carries even less envelope. People fill this car’s label with the last car’s experience: “that level changed lanes last time, so this one will.” An interface that only shows “assist on” or the same steering-wheel glyph helps them fill. Inconsistency is therefore not a PR problem. It is a mental model that cannot travel: the encoding looks the same, the envelope has already changed.

Studying it

Use scenario judgment or a simulator: people with different brand experience, the same interface encoding, judging whether the system will change lanes, whether hands may leave the wheel, whether it will stop at a light. Do not only ask whether they can recite SAE.

Independent variables: prior brand and feature name, whether the current UI states ODD limits, whether a level number appears with the trademark. Dependent variables: correctness on specific capabilities (lane change, hands-off, signals, urban roads), over-generalizations from one success to a general ability.

Training participants into SAE experts hides the trademark-inference path real users take. Cross-brand rental or shared cars expose inconsistency better than a long tenure in one vehicle. “Users cannot recite the textbook difference between Level 2 and Level 3” is almost always true and is not the finding; measure which envelope they transplanted onto this car.

Where it stops holding

For an owner who never leaves one brand and one feature, inconsistency shows up as a gap with ads and the manual, not as cross-car transfer. If a market requires a particular Level 3 mark and forbids a kind of hands-off at Level 2, the interface can lean on regulation to freeze the boundary—until the same vehicle is exported where that rule does not exist, and the trademark returns. Robot autonomy continua are another label set; they do not explain why two OEMs implement the same SAE digit as different envelopes. Unifying the names would not by itself end confusion—people can still misread whether it is on right now. Inconsistency is the extra, cross-car layer.

Applying it

• State capabilities as observable behavior (will it change lanes, may hands leave, on which roads), not only a level digit or a trademark.
• If a trademark’s ODD changes across model years, make the change something that must be seen on first use, rather than reusing the old glyph.
• On a shared or rental first trip, put what this vehicle will not do in a glanceable place; do not assume a person stepping out of another brand still carries the right envelope.
• Verify with people who have used another assist: looking only at this car’s UI, not the manual, list behaviors they think it will do that it will not. Each item is a level name that failed to bring its boundary along.

Related

• Within the group: K6.12.2 Misjudging the capability envelope is the most common outcome of mode confusion · K6.12.3 Multi-channel status cues prevent misjudgment better than a single cue · K6.12.4 Temporary capability degradation must be as salient as a full shutdown
• Adjacent: K6.09 Expressing Automation State · X3.02 Communicating Capability Boundaries · X4.01 Levels of Autonomy
• Search terms: SAE J3016 · operational design domain · OEM automation naming · capability envelope