Seeing the actual value without its target next to it hides how far off the process really is

What it is

Co-displaying setpoint and process value means the operator sees, in the same view at the same moment, what the control target is, what the measured state is, and how large the error between them is. A process value shown alone has no reference — 35°C is good or bad depending on whether the setpoint is 30°C or 40°C, and the number by itself cannot answer "is control actually working."

Why it happens

Subtraction is not hard; sustaining it under pressure while scanning many variables is. When setpoint sits on a recipe page and process value sits on a trend page, the operator must switch pages and hold both numbers in working memory long enough to subtract them — and working memory is small and easily flushed by an interruption, a phone call or an alarm resetting the count to zero. A shared view, scale, and time cursor downgrades this from arithmetic to perception: error becomes the visible spatial gap between two lines, read directly instead of computed. That is why a shared scale is not optional — if setpoint and process value each use their own axis, the two lines can overlap or cross without error actually being zero, and visual intuition then gives the wrong answer.

Where it stops holding

Not every loop has one stable setpoint to compare against. Trajectory-tracking control (a batch heating profile) has a target that changes continuously with time; constraint control and optimizers can hold several internal targets at once and switch which constraint is active, so labeling one number "the setpoint" hides the others still in force. The measured value itself can also lag, be filtered, or have degraded quality (a failing transmitter that has not yet alarmed) — in that case "process value tracking setpoint closely" looks fine while the basis for comparison is no longer trustworthy; co-display cannot itself verify data quality, which needs its own indicator.

Applying it

Deviation colour must map consistently to control semantics — the same colour cannot mean "above target" on one loop and "below target" on another, or operators will misapply cross-loop visual habits.

• Place setpoint, process value, numeric error, current mode (auto/manual/cascade), and a data-quality flag side by side in one widget, not scattered across panels.
• Mark every setpoint change as a vertical line on the trend, so it is immediately clear whether a growing gap comes from process disturbance or from a target that just moved.
• How to check: stage a setpoint step, a frozen sensor reading (quality degraded but value unchanged), and an auto-to-manual transfer; screen-record each and time how quickly an operator can say whether control is currently tracking. All three cases must be judged correctly within seconds.

Related

• Same group: Y3.08.2 Deviation-band indication · Y3.08.3 Obsolete setpoint diagnosis · Y3.08.4 Hidden control target
• Nearby: Y3.09 Manual–automatic transfer · Y1.03 Trends and rate of change
• Search terms: Co-displayed setpoint and process value · process control display · industrial human factors