HMI & CONTROL PANEL

HMI, SCADA or Panel — What You Are Actually Buying

These three get quoted against each other and are not the same thing. Getting the distinction right before you buy saves paying twice or, more often, buying one and needing another.

The practical rule: the HMI is what keeps the plant running when everything above it is unavailable. That is why it deserves proper engineering rather than being treated as a screen bolted to a door.

The Screen Is Part of the Safety System

An operator reads an HMI under pressure, at speed, at the end of a nine-hour shift, sometimes in poor light with wet hands. Screen design is not decoration — it is the interface through which someone decides whether to stop a process.

• Colour means state and nothing else. If red is used for a logo, a heading and a fault, red has stopped meaning fault. Calm screens where colour carries information beat colourful ones every time
• Abnormal must be obvious without reading. A supervisor walking past should see that something is wrong before understanding what
• Numbers with context, not bare digits. A value against its normal range and its direction of travel tells an operator something; 72.4 on its own does not
• Consistent placement across every screen — muscle memory is a safety feature, and inconsistency costs seconds exactly when seconds matter
• Touch targets sized for gloved hands, not for a designer’s mouse
• Confirmation on consequential actions, and no confirmation on routine ones — over-confirming trains people to tap through without reading

Screens in the Operator’s Language

This is routinely overlooked on Indian plants and it matters more than almost anything else on this page.

The engineer who commissions the plant reads English. The operator on the night shift at a district co-operative may not. When the screen says “Homogeniser discharge pressure low — check line strainer” and the operator cannot read it, the alarm has failed no matter how well it was configured.

• Multi-language screens — Hindi or Gujarati alongside English, switchable at the screen
• Alarm and prompt text translated properly, not machine-translated into something that reads as nonsense to a native speaker
• Icons and colour carrying meaning independently of text, so the screen works even for a reader who is struggling
• Training material in the language the training is delivered in

It costs very little at configuration time and is expensive to retrofit once several hundred alarm texts exist.

Navigation People Can Use Under Pressure

• A hierarchy, not a pile of screens — overview, then area, then equipment detail
• Any screen within two touches from the overview
• A fixed alarm banner visible on every screen, so an operator deep in a detail page still sees a new fault
• Direct navigation from an alarm to the equipment that raised it — this alone removes minutes from every response
• A home button that always works, from anywhere, including mid-dialogue

Recipes, Setpoints and Who May Change Them

The HMI is where the plant gets adjusted, which makes it where quality problems and disputes originate.

• Role-based access — operator, supervisor, engineer — with genuinely different rights, not a single shared password on a sticker
• Limits enforced by the system. If a temperature setpoint above a certain value would spoil product or breach a standard, the screen should refuse it rather than rely on discipline
• Changes logged — who, what, when, previous value. This settles arguments as often as it satisfies auditors
• Recipes selected, not typed. Free-entry of parameters that should be fixed is how a plant ends up making a product it did not intend
• A clear indication of which recipe is running, visible without navigating

Choosing the Hardware for the Environment

Dairy and food environments destroy equipment specified for an office. The selection is driven by where it lives, not by screen size preference.

Replacing an Obsolete Panel HMI

A common enquiry: the operator panel has failed, the model is discontinued, and the plant is running on one surviving unit.

• The project file may not exist. Screens frequently have to be rebuilt from photographs and operator knowledge — normal, and it is the reason a like-for-like swap is rarely as quick as it sounds
• Cutout and mounting rarely match between generations; panel modification is usually part of the job
• It is the right moment to fix the screens rather than faithfully reproduce twenty years of accumulated clutter
• Check what else is obsolete while the panel is open — a failing HMI is often the first visible symptom of a controller heading the same way. See Siemens PLC migration
• Back up the existing project first, if one can still be read out. Once the last working unit fails, that option is gone

How We Engineer HMI Applications

1. Sit with the operators — what they actually watch, what they ignore, where they currently go wrong
2. Screen hierarchy and navigation map agreed before any graphics are drawn
3. A style standard — colours, symbols, layout, fonts, alarm presentation — applied consistently across every screen
4. Build against the tag list, aligned with the PLC and SCADA naming so a value can be traced end to end
5. Alarm text written to be acted on, in the operator’s language, saying what to check
6. Test with operators before commissioning, not after
7. Revisit after a fortnight of live running, when the screens people avoid have become obvious

On Siemens we work with the SIMATIC HMI range, WinCC and WinCC Unified. Ongoing cover is available under an automation support contract.