Showing only the current reading with no target hides whether control is actually working at all

What it is

Hiding the setpoint turns process value into an isolated reading with no frame of reference: the operator can see "what it is now" but not "what it should be," and so cannot judge whether the control target is met, how large the error is, or whether the last command actually took effect. Being inside a normal absolute range is not the same as control doing what it is supposed to do — normal range is a safety judgment, control effectiveness is a target judgment, and the two are not interchangeable.

Why it happens

The same process value can mean two opposite things under different setpoints: tight tracking, or severe deviation. When a controller quietly changes its internal target — a recipe switch, an optimizer decision — and the interface still shows only the process value, a particularly deceptive misjudgment follows: the operator sees the value change and reads it as drift or a fault, when it is actually the controller responding correctly to a new target. The reverse is also possible — an unchanging process value can mean the controller failed to catch up with a target that already moved, not that everything is fine. Reading either case correctly needs more than the process value; target provenance and activation time are themselves diagnostic information, not a nice-to-have.

Where it stops holding

Some safety-related targets are generated dynamically by constraint bands or an optimizer and have no single stable "setpoint" to display; presenting one instantaneous internal value as the setpoint can mislead operators into treating it as fixed. That is not a reason to show nothing — even a dynamic target must be expressed as an understandable current range, its bounding conditions, and the automation's intent, in a form that matches its dynamic nature rather than being flattened into one static number.

Applying it

Label the currently active target, its source (recipe, optimizer, or manual entry), current mode, and activation time beside every controlled variable, with an error trend, so that "the target moved" and "the process moved" can be told apart visually.

• How to check: stage an implicit target change — triggered automatically by a recipe or optimizer without operator confirmation — and measure how long it takes an operator to notice the target has changed and correctly judge whether the current response is appropriate. If a correct response gets misread as a fault and manually corrected, target visibility has failed.

Related

• Same group: Y3.08.1 Co-displayed setpoint and process value · Y3.08.2 Deviation-band indication · Y3.08.3 Obsolete setpoint diagnosis
• Nearby: Y3.02 Automation mode confusion · Y1.05 Representing the normal state
• Search terms: Hidden control target · process control display · industrial human factors