SCADA Control Room Interface Architecture Framework

Role: Principal Human Factors and Industrial UI Systems Designer with twenty years of experience in critical utility infrastructure.

Context

• Utility operations profile: {{utility_type}}
• Control room physical setup: {{operator_environment}}
• Priority alarm definitions: {{critical_alarm_classes}}
• Legacy interface constraints: {{existing_scada_system}}
• Human factors compliance guideline: {{regulatory_standard}}
• Hardware viewport specifications: {{display_form_factor}}

Task

Develop a comprehensive Human-Machine Interface (HMI) visual design framework that reduces operator cognitive load, enforces strict situational awareness standards, and eliminates visual noise across daily monitoring and emergency dispatch operations.

Method

1. Audit the operational parameters of {{utility_type}} against standard high-performance HMI principles.
2. Define a muted baseline color palette reserve high-saturation chromatic cues exclusively for dynamic state changes and {{critical_alarm_classes}}.
3. Formulate typographic scale and density rules suited for {{display_form_factor}} under {{operator_environment}} lighting conditions.
4. Design analog visual indicators (trend lines, moving scales, level indicators) that display operational context alongside raw telemetry.
5. Establish visual hierarchies for multi-tier screen navigation across {{existing_scada_system}} architecture.
6. Standardize alarm visual states (unacknowledged, acknowledged, cleared) compliant with {{regulatory_standard}}.
7. Detail layout grids for summary dashboards, subsystem overviews, and granular equipment diagnostics.
8. Construct failure-state visual patterns to prevent misinterpretation during degraded communications.

Constraints

• MUST adhere to color-blindness and contrast accessibility requirements defined in {{regulatory_standard}}.
• MUST NOT use decorative visual elements, skeuomorphic graphics, or non-functional animations.
• Visual emphasis MUST correlate directly to operational severity rather than equipment size.
• Provide concrete visual token values (hex codes, line weights, spatial grids).

Output format

1. Visual Semantics & Palette Matrix (table of functional roles, color values, luminance rationale)
2. Typography & Information Density Specs (hierarchy scale, line spacing, viewing distance rules)
3. Component Visual Behavior Guidelines (normal, abnormal, critical alarm visual specs)
4. Screen Layout Hierarchy Blueprint (wireframe layouts for level 1 overview through level 4 diagnostic views) Total output must be between 900 and 1400 words.

Self-review

• Are saturated colors strictly prohibited for steady-state operating elements?
• Does the framework explicitly accommodate viewing constraints of {{operator_environment}}?
• Are all alarm states mapped directly to the classes in {{critical_alarm_classes}}?