A highlight's color, sound, and persistence should map to severity by rule, not by who built the screen

What it is

Salience–priority mapping requires visual style, sound, and how long a cue persists to hold a stable, predictable relationship with consequence and response urgency — not to be decided ad hoc by whichever color or icon style a screen happened to adopt.

Why it happens

Attention capture is a finite resource. If low-priority states also flash and sound at full intensity, the highest priority loses its relative advantage — attention gets spread evenly instead of directed at the event with the largest consequence. When channels disagree — an event colored red but not paired with the most urgent sound, say — the operator has to decode the conflicting cues and judge which one actually wins before deciding what to act on first, and that decoding step costs time and is error-prone under pressure.

Whether the mapping works also depends on matching the number of priority tiers to how many salience steps people can reliably discriminate. Color depth and flash rate are continuous variables that could in principle be sliced into many levels, but under time pressure the number of steps people can hold apart reliably is much smaller than that. A system with five or six priority tiers, distinguished only by shade or blink rate, collapses in practice during a busy period — operators cannot tell the middle tiers apart, so more tiers make the mapping less reliable, not more. This is part of why EEMUA 191 and ISA-18.2, the two alarm-management references most commonly cited on this point, both recommend compressing priority to roughly three or four tiers: the limit is discriminability, not configuration convenience.

Equipment provenance is another condition that can invert the mapping. Skid-mounted third-party packages often arrive with their own factory color convention — green meaning the skid itself is running, red meaning only that the skid itself has tripped. Wired into the main control system without remapping, the same color carries a different urgency depending on where it came from, and operators applying the convention they learned on the primary system will misread it — usually by treating something non-urgent as urgent, or the reverse.

Studying it

Vary how consistent the assigned priority is with the cue's salience, and in mixed-priority scenarios measure ranking accuracy, first-response time to the highest-priority event, and the distraction cost imposed by lower-priority cues that also demand a glance. Test auditory cues against realistic plant-floor background noise — discriminable steps in a quiet lab are not guaranteed to survive real ambient noise or overlapping alarm sounds — and include color-vision-deficient participants, since red–green coding can fail for them entirely.

Where it stops holding

Severity and urgency are different dimensions and should not be collapsed into one. A severe but slow-developing condition with a response window of hours — a slow trending excursion, for instance — does not necessarily deserve the most intrusive cue; treating "high consequence" as automatically meaning "use the strongest cue" pulls attention away from fast events that genuinely need it first. Regulation or sector convention may already fix part of the coding, such as colors tied to safety-interlock states, and those conventions take precedence over a custom scheme. Specific saturation and sound-pressure levels do not transfer across environments either — the same palette is not equally discriminable in a bright control room and a dim one.

Applying it

Define consequence tier, allowable response window, and ownership first, then build a small set of visual and auditory levels on top of it — typically three to four tiers, since more become hard to hold apart reliably — and keep the same tier's appearance consistent across screens and vendors, remapping any third-party skid's factory colors rather than passing them through unchanged. How to check: fire a sequence of mixed-tier events and verify operators can name the most urgent one from the cue alone, without reading text labels; then rerun the same test under real color-vision screening, ambient noise, and night-shift brightness conditions to confirm the mapping has not collapsed into indistinguishable tiers.

Related

• Same group: Y1.06.1 Spatially localized anomaly highlighting · Y1.06.3 Salience competition during multiple anomalies · Y1.06.4 Persistence of unresolved anomaly cues
• Nearby: Y2.03 Alarm priority classification · Y3.03 Color and safety coding
• Search terms: alarm priority coding · visual salience hierarchy · ISA-18.2