A well-designed HMI doesn’t just look good—it communicates clearly, responds instantly, and reflects what’s really happening in the process. At the heart of all of that are tags, data mapping, and variables.
These three concepts form the data backbone of any HMI system. When they’re designed thoughtfully, your HMI is fast, reliable, and easy to maintain. When they’re not, you get sluggish screens, broken animations, and operators who don’t trust what they’re seeing.
Let’s break them down.
What Is a Tag in an HMI?
A tag is a named reference to a piece of data that the HMI reads from or writes to a controller, device, or internal memory location.
Think of a tag as:
A label that connects the HMI to a real-world value
Common tag types
- Motor status (Run / Stop)
- Pressure, temperature, flow values
- Setpoints
- Alarms and fault codes
- Operator commands (Start, Reset, Acknowledge)
A good tag name is descriptive, consistent, and readable—because humans will maintain this system long after it’s deployed.
Variables vs. Tags: What’s the Difference?
This is where many new HMI designers get tripped up.
Tags
- Linked to external data sources
- Represent real process values
- Update through communications (Ethernet/IP, Modbus, PROFINET, etc.)
Variables
- Exist inside the HMI only
- Used for logic, math, animation, or temporary values
- Not directly tied to a PLC unless you map them
When to use variables
- Screen navigation logic
- Animation scaling
- Runtime calculations (averages, conversions)
- User interface state tracking
Rule of thumb:
If the value must survive a power cycle or affect the process, it belongs in the PLC (tag).
If it’s purely visual or temporary, keep it in the HMI (variable).
What Is Data Mapping?
Data mapping is the process of linking an HMI tag to its actual data source.
That source could be:
- A PLC register
- A drive parameter
- An I/O point
- Another controller
- An internal HMI variable
If the mapping is wrong—even by one address—the HMI may:
- Display incorrect values
- Fail to update
- Write data to the wrong device (worst case)
One-to-One vs. Indirect Mapping
One-to-one mapping
- Each tag maps directly to one PLC address
- Simple, clear, easy to troubleshoot
- Preferred for most systems
Indirect (indexed) mapping
- Tag address changes dynamically using an index or pointer
- Reduces tag count
- Increases complexity and risk
Indirect mapping is powerful—but best reserved for advanced applications with strong documentation.
Why Good Tag Design Matters
Poor tag design leads to:
- Slow screen refresh
- Communication overload
- Difficult troubleshooting
- Risky future expansions
Good tag design enables:
- Faster development
- Easier maintenance
- Better alarm handling
- Cleaner screen logic
Best Practices for HMI Tags and Variables
- Use Consistent Naming Conventions
- Avoid Duplicating Logic
- Don’t recreate PLC logic in the HMI
- Let the PLC control the process
- Let the HMI visualize and command
- Limit High-Speed Polling
- Only update fast-changing tags when needed
- Group tags by update rate (fast, normal, slow)
- Separate Process Data from UI Logic
- Process values → PLC tags
- Screen states, animations → HMI variables
- Document Everything
Good documentation beats clever shortcuts every time.
Tags, Alarms, and Performance
Every tag consumes:
- Network bandwidth
- PLC scan time
- HMI processing power
Well-structured tag databases:
- Reduce network traffic
- Improve alarm response
- Keep screens responsive
This becomes critical in systems with:
- Hundreds of alarms
- Multiple HMIs
- Remote connections
Common HMI Data Design Mistakes
- Using the HMI as a “soft PLC”
- Poor or cryptic tag names
- Mapping unused tags
- Mixing UI logic and process control
- Ignoring update rates
These issues don’t always show up during commissioning—but they surface later during troubleshooting or expansion.
The Bottom Line
In HMI design:
- Tags connect your screens to the real world
- Data mapping ensures those connections are accurate
- Variables handle internal logic and visualization
Mastering these fundamentals leads to HMIs that are faster, clearer, and far easier to maintain—long after the original designer has moved on.