Grid Control SCADA Interface Visual Specification
Author a complete visual hierarchy, color semantic, and layout specification for mission-critical power grid SCADA operator consoles.
Use this template when redesigning or standardizing high-voltage grid management HMI consoles to reduce operator cognitive fatigue. It establishes visual encoding standards and spatial constraints for emergency and continuous monitoring modes.
Role: Principal Industrial HMI Designer specializing in mission-critical power utility control rooms.
Context
- Operating Entity: {{utility_name}}
- System Scope: {{grid_asset_type}}
- Ambient Environment: {{operator_lighting_condition}}
- Alarm Hierarchy: {{critical_alert_thresholds}}
- Hardware Target: {{screen_resolution_standards}}
- Existing Issues: {{legacy_hmi_pain_points}}
Task
Draft a comprehensive HMI visual design specification that standardizes UI components, color-coded status semantics, spatial layouts, and typography for control room monitoring consoles to maximize situational awareness and eliminate visual noise during abnormal operating conditions.
Method
- Analyze {{legacy_hmi_pain_points}} to isolate root causes of cognitive overload during fault events.
- Establish visual baseline palettes optimized for {{operator_lighting_condition}} using high-performance, low-saturation backgrounds with high-contrast accent signals.
- Formulate strict color semantic mappings for {{critical_alert_thresholds}} ensuring ANSI/ISA-101 compliance.
- Design spatial zoning guidelines for {{screen_resolution_standards}}, prioritizing core single-line diagrams in the primary field of view.
- Define typographic hierarchy and numeric tabular data alignment rules for real-time telemetry rendering.
- Standardize visual component states (normal, warning, alarm, unacknowledged, suppressed, out-of-service) across all grid nodes.
- Detail responsive scaling and viewport density rules for {{grid_asset_type}} asset topologies.
Constraints
- Color MUST NOT be used as the sole indicator for alarm states; pairing with shape and redundant iconography is mandatory.
- Bright saturated colors MUST be reserved strictly for unacknowledged and critical alert states.
- Keep background contrast ratios within WCAG 2.1 AA standards for low-lux environments.
- Avoid decorative elements, drop shadows, or non-functional gradients.
Output format
Provide a technical UI specification document organized into:
- Executive Design Rationale
- Color Palette & Chromatic Semantic Token Table
- Typography & Numerical Data Rules
- Spatial Layout Grid & Display Zoning Spec
- Component State Definitions (Alarm, Nominal, Disabled)
- Single-Line Diagram Graphical Rendering Rules
Self-review
- Confirm all {{critical_alert_thresholds}} have distinct, non-conflicting visual tokens.
- Verify that the layout addresses each documented challenge in {{legacy_hmi_pain_points}}.
- Ensure ambient lighting considerations in {{operator_lighting_condition}} are explicitly reflected in the contrast ratios.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.