timhok/hmi-design / hmi-design-full
hmi-design-full
VerifiedComprehensive ISA-101 design rules for Human Machine Interfaces in process automation, with detailed reference files covering color design, display hierarchy, navigation, alarms, human factors, performance, and lifecycle management. Use when designing, building, reviewing, or generating code for HMIs, control system displays, SCADA screens, or industrial control panels and comprehensive ISA-101 coverage is needed. Use when deep-diving into alarm design, color standards, navigation patterns, human factors, performance requirements, or HMI lifecycle management.
| File | Kind | Size |
|---|---|---|
| SKILL.md | skill md | 11.9 KB |
| alarm-design.md | markdown | 6.1 KB |
| color-and-visual-design.md | markdown | 5.7 KB |
| display-hierarchy-and-styles.md | markdown | 7.8 KB |
| lifecycle-and-management.md | markdown | 6.0 KB |
| navigation-and-interaction.md | markdown | 7.7 KB |
| performance-requirements.md | markdown | 4.2 KB |
| references/alarm-design.md | markdown | 6.1 KB |
| references/color-and-visual-design.md | markdown | 5.7 KB |
| references/display-hierarchy-and-styles.md | markdown | 7.8 KB |
| references/lifecycle-and-management.md | markdown | 6.0 KB |
| references/navigation-and-interaction.md | markdown | 7.7 KB |
| references/performance-requirements.md | markdown | 4.2 KB |
| references/situation-awareness-and-human-factors.md | markdown | 6.0 KB |
| situation-awareness-and-human-factors.md | markdown | 6.0 KB |
references/alarm-design.md
View on GitHub# HMI Alarm Design — Agent Instructions
When designing alarm presentation and management in HMI displays, follow these rules.
## Core Alarm Principles
1. **Alarms demand action.** An alarm indicates an equipment malfunction, process deviation, or abnormal condition requiring operator response.
2. **Alerts inform.** An alert indicates a condition requiring awareness but not immediate action. Alerts are presented separately from alarms.
3. **Alarm colors are sacred.** Colors designated for alarms must NEVER be used for any other purpose in the HMI.
## Visual Alarm Presentation
### Color Reservation
- Define specific colors for each alarm priority level in the alarm philosophy
- These colors are EXCLUSIVELY for alarms — no exceptions
- Common convention (facility-specific):
- Red: highest priority / critical safety
- Yellow/Amber: high priority / warning
- Other colors per facility philosophy
- Non-alarm elements must NEVER use alarm colors, even if they "look nice"
### Alarm State Indicators
| State | Visual Treatment |
|-------|-----------------|
| Unacknowledged alarm | BLINKING indicator (draws immediate attention) |
| Acknowledged, still active | STEADY indicator in alarm color |
| Returned to normal, unacknowledged | Blinking or distinct visual state |
| Cleared (acknowledged + returned to normal) | No alarm indication |
### Alarm Priority Indication
- Each priority level must have a unique combination of:
- Visual indication (color, shape, size, position)
- Audible indication (distinct tone/pattern per priority)
- Visual priority indication is MANDATORY
- Audible priority indication is strongly recommended
- In environments where audible is not used, visual priority must be sufficient alone
### Redundancy Rules
- Color must NOT be the sole alarm indicator
- Always pair alarm color with at least one of:
- Shape (e.g., triangle for high priority)
- Text label (alarm name and priority)
- Brightness/contrast difference
- Size difference
- Position (alarm bar, dedicated area)
- Blinking/flashing state
## Alarm Placement by Display Level
### Level 1 (Overview)
- Show ALL top-priority alarms
- Position alarms adjacent to associated equipment/area
- Show acknowledged/unacknowledged status
- Show alarm count or severity summary per area
- Direction of change indicators for alarming parameters
### Level 2 (Operating)
- Show all TOP and MIDDLE priority alarms for the area
- Clear navigation cues to non-displayed lower priority alarms
- Alarms integrated into the process view near associated equipment
### Level 3 (Detail)
- Show ALL alarm priorities for depicted equipment
- Full interlock and permissive status
- Detailed alarm information
### Level 4 (Diagnostic)
- Detailed alarm configuration
- Trip logic details
- Alarm history and statistics
## Alarm Summary Display
### Access Requirements
- Accessible in **1 click from ANY display** in the entire HMI
- Ideally on a permanently visible dedicated monitor or panel
- No navigating away from the current working display to see alarms
### Content Requirements
- List of all active alarms
- Sortable by: time, priority, area/unit, alarm name
- Show for each alarm:
- Alarm name/tag
- Description
- Priority
- Current value
- Alarm limit
- Time of alarm
- Acknowledged/unacknowledged status
- Area/unit association
### Related Alarm Lists
- Shelved alarms list (alarms temporarily removed from active display)
- Out-of-service alarm list
- Suppressed alarm list
- Recent alarm history
- These lists may be accessible in more clicks than the main summary but should still be easily reachable
## Auditory Alarm Design
### General Requirements
- Audible signals must be audible from the normal operator position
- Must not be so loud as to distract operators at other consoles
- Must not startle operators or add significantly to overall noise
- Must not prevent communication between operators
### Auditory Signal Design
- Each signal: clear, unambiguous meaning
- Distinct tones/patterns for different priorities
- Provide localization cues (direct operator toward the relevant console/area)
- Support operators with partial hearing impairment:
- Adjustable volume speakers
- Earpiece option
- Do not exceed hearing conservation limits
### Silencing
- Always provide a method to silence an audible alarm after acknowledgment
- If some signals must not be muted, implement appropriate control mechanisms
- Un-silenceable alarms should be rare and clearly justified
### Remote/Field Alarms
- If operator is not always at the console, provide alternate methods:
- Area speakers
- Pager/text notifications
- Remote alarm panels
- Mobile device notifications
## Alarm-Related Design Patterns
### Alarm Banner / Bar
A persistent strip (top or bottom of screen) showing most recent/highest priority alarms:
```
┌─────────────────────────────────────────────────────┐
│ [!] HIGH: TIC8700 > 986°F │ [!] MED: FIC770 < 50 │ → Alarm Summary
├─────────────────────────────────────────────────────┤
│ │
│ (Main display content) │
│ │
└─────────────────────────────────────────────────────┘
```
### Alarm Integration in Process Displays
- Show alarm state directly on the equipment/instrument symbol
- Color the relevant indicator, add blinking for unacknowledged
- Clicking an alarmed item should provide alarm detail (faceplate/popup)
### Alarm-Driven Navigation
- Clicking an alarm in the alarm summary should navigate to the relevant display
- The target display should be the most useful level for that alarm type:
- Process alarms → Level 2 or 3 display for that area
- Equipment alarms → Level 3 detail for that equipment
- Safety alarms → Level 3 or 4 with interlock detail
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 322k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 198k | Updated | Claude CodeCodex | Verified | Install |