IoT changed the cost of sensing but not the cost of sense making. Sensors, connectivity, cloud storage, dashboards & analytics, are all cheap and distributed. A mid-sized operator now has data volumes that used to justify a full operations room. But the place where data turns into understanding never got the same treatment.
There is an argument here that IoT got too cool for school. A rerun of those early Mac v PC ads. Stodgy process industries have already done the heavy lifting. The upsell was: “You can do everything from your phone,” complemented with a slick demo and a fast talking sales guy. A phone and a control room do different jobs.
Systems and scale
Control rooms in refineries, power plants and transport have formal design standards, and almost none of that knowledge has filtered down into IoT. IoT designs dashboards the way you’d design any consumer app…single users are fine with an app. In between sits a large group (a regional water company, a fleet of a few hundred vehicles, a greenhouse cluster, a mid-size factory) with control room sized data and phone sized tools.
The phone is personal, interruptive and glanceable. It is built to tell one person that one thing needs attention and then let them act on it. The control room is shared, persistent and contextual. Many assets at once, history alongside the live picture, one view a whole team can discuss. A slow-building awareness that something is drifting sideways, before any single alarm fires off.
Start from the work, not the screens.
The ergonomic standard for control centers, ISO 11064, treats the operator’s tasks as the starting point. User requirements are a central theme. Processes are built around those. In practice; what decisions does this room exist to make? Who makes them? How are they made? The screens follow from that. The standard covers all types of control centers, including process industries, transport systems and emergency services dispatch, so it’s a general concept.
Overview first, detail on demand.
Good control systems use a layered display structure, with a four-tier display hierarchy in the HMI standard ISA-101: the whole operation at a glance, then an area, then a unit, then diagnostics. The video wall shows the top layer, the desk drills down. Most IoT dashboards are stuck at the detail level, with lots of charts and no overview.
Calm by default, so trouble stands out.
This is the counterintuitive one. High-performance design calls for neutral, low-contrast grey backgrounds and flat elements, reserving bright saturated colors strictly for abnormal conditions and prioritized alarms. The reason: when the normal screen is already colorful, a real alarm blends into the background visual noise. A well-designed control room looks boring when things are fine. That’s the opposite of what sells in a demo.
Routing to the right people.
Once noise is removed, the issue becomes routing alarms proportionally to the appropriate level of staffing. This is where the phone re-enters the picture, as the end of an escalation chain, rather than the whole system.
The alarm standard ISA-18.2 defines an alarm as a way of indicating an equipment malfunction, process deviation or abnormal condition requiring a response. The key word is response: if nobody needs to act, it isn’t an alarm. It even sets targets, around one alarm per 10 minutes on average per operator. The process starts with a written alarm philosophy, the first step in the lifecycle. Its international counterpart, IEC 62682, is adopted as EN 62682 in the EU, which matters for anyone selling in Europe.
The room itself.
Layout, sightlines to the shared wall, lighting, noise and comfort over long shifts are all covered. ISO 11064-6 deals with environmental requirements for control rooms and the supporting areas. Add to that something the standards address less directly but every operator knows; shift handover. The room has to make it easy to pass on “what’s going on” to the next person.
It’s never finished. The ISA-101 lifecycle runs through planning, analysis, design, implementation, operation, and maintenance, with a formal process for modifying approved content. If we compress it into one sentence: A good control room is designed around attention, with calm screens, few (but meaningful) alarms, a shared overview, and clear rules for who acts on what.


