All posts
dashboardsmonitoringiiot

Industrial IoT Dashboards: How to Design One People Use

How to design an industrial IoT dashboard people check every day: who it is for, how many indicators, colours that call for action and how to build it.

Close-up of an industrial screen on an articulated arm next to a press with a green stack light: a clean dashboard with six tiles, one amber, and a trend below its limit; behind it, out of focus, a screen crowded with charts

An industrial dashboard that gets used answers one specific person’s question in a few seconds: what’s stopped, what’s heading out of its range or what it’s costing. You design it starting from who looks at it and what they decide with it, with few indicators, colours that say whether to act and the time span that person needs. The tool matters less than that.

Why does nobody look at so many industrial dashboards?

Almost always for one of these reasons:

  • It was designed to impress: forty KPIs¹ on one screen look good in the presentation, but whoever has to act doesn’t know where to look.
  • It answers no question: every available signal went in, not the ones someone needed.
  • The data arrives late: if someone types it into a spreadsheet at the end of the shift, by the time it’s seen nothing can be done.
  • It has no owner: nobody reviews it, and when one figure is wrong, people stop trusting the whole dashboard.

The difference between a dashboard opened every morning and a forgotten one isn’t the technology; it’s how it was designed and for whom.

Who will look at it, and what do they decide with it?

Each person in the plant looks at different things, over a different time span and in a different place. So there isn’t one dashboard for everyone, but one view for each:

WhoTheir questionWhat they need to seeTime spanWhere they look
Shift supervisorWhat’s stopped now, and why?Each machine’s state, stoppages, parts this shiftLast minutes and the shiftLarge screen on the shop floor
MaintenanceWhat’s going to fail?Alarms, temperature and vibration trends, running hoursDays and weeksPC and phone
QualityWhy are rejects going up?Rejects by shift and part number, process parametersShift and weekPC
Plant managerHow are we doing against target?OEE², output, cost per partDay, week and monthPC and phone
Energy or managementHow much do we use, and where?Consumption by line, peaks, use while not producingWeek and monthPC and monthly report

Trying to make one screen serve all five is the shortest route to a dashboard that serves nobody.

How many indicators should an industrial dashboard have?

Few. As a guideline, five to seven in the main view. For each one, ask: can the person looking at it do something about this? If not, it comes out of the main view.

The rest doesn’t disappear: it’s one click away. It works well to order it like the plant itself, from the overview to the detail:

  1. Overview: which lines are doing well and which aren’t.
  2. Line: which machine is holding the line back.
  3. Machine: its signals, its alarms and its history.

For that, the data has to be organised the same way as the plant (Plant › Line 2 › Press 3), not as a list of loose signals.

How do you design it so it leads to action?

A good dashboard doesn’t just tell you how you’re doing: it tells you whether you need to do something.

  • Colours with one meaning each: green, everything within range; amber, something is nearing its limit and is worth watching; red, act now. If someone has to read numbers to know whether things are fine, the dashboard isn’t well designed.
  • Every figure against its reference: “812 parts” says nothing; “812 of the 900 planned by now” does.
  • Trends, not just the current value: a motor that usually runs at about 60 °C and alarms at 80 °C can read 70, 71, 72 and 73 °C on consecutive days without anything going off. On the chart, with the limit drawn in, you see it coming; a predictive maintenance system can alert you before the breakdown. The figures are an illustrative example. How to set up those alerts is in real-time industrial IoT monitoring.
  • In the unit of whoever decides: the shift supervisor thinks in parts and minutes; management, in euros. The same consumption can show in kWh for maintenance and in euros per part in the monthly report.
  • Always in the same place: every indicator where people expect it. On the shop-floor screen, few numbers and large ones, readable from a distance.

What types of industrial dashboards are there?

  • Production: each machine’s state, speed against nominal, good parts and rejects, stoppages and their reason, and the shift’s OEE. How to get it without spreadsheets is in how to calculate OEE in real time.
  • Energy: consumption by line and by machine, power peaks, consumption with the plant stopped and cost per part. The indicators worth measuring are in 5 energy KPIs to track in a plant.
  • Maintenance: active alarms, the ones that repeat most, trends of critical signals and running hours.
  • Quality: rejects by shift and part number, next to the process parameters at that moment, to see what causes them.

How do you build an industrial IoT dashboard, step by step?

  1. Choose the people and their questions: one or two to start with, not the whole company.
  2. Check where each piece of data comes from: the PLC³ usually has the states, counters and temperatures; the history usually isn’t in it, alarms with their time often stay on the HMI⁴, and consumption data only exists if there are meters. A gateway on the shop floor reads the PLC over OPC UA⁵ or Modbus⁶. In most cases the machine’s logic doesn’t change. At most, the PLC’s communication is enabled or configured, or a few signals are wired in the cabinet.
  3. Organise the data like the plant, so you can compare by line, by shift or between plants.
  4. Build a first version with the overview and the detail of one line.
  5. Review it with the people using it after two weeks: what they look at, what they don’t, what’s missing. What nobody looks at goes. The most useful dashboards are designed with the people who use them, not for them.

How we do it with coppioT

coppioT is engapplic’s no-code industrial IoT⁷ platform: it connects PLCs, sensors, energy analysers and other equipment of any brand to the cloud, in one data system and with no programming. Your charts and reports go in the tools you already know, Grafana or Power BI, with the data already organised like your plant.

  1. A short consultancy at a fixed price, with engapplic: who will look at the dashboard, what they decide with it and which signals are needed.
  2. A pilot on one or two machines: we connect them, build the first version of the dashboard and review it with the people using it.
  3. Scaling to the rest of the plant, or to other plants, with the same structure.

That’s what we did on the paint booth we have connected at a RACC-AXA car workshop in Barcelona, with the integrator Sinnek: the customer sees what the diesel or LPG⁸ and the electricity cost, and the cost per part and per hour.

All of that in days, not months: up to 90% faster than building it by hand.

Frequently asked questions

Which tool do you use for an industrial dashboard?

The most common are Grafana, for real-time dashboards and alerts, and Power BI, for reports and analysis. The tool matters less than it seems: what makes a dashboard useful is that the data arrives on its own, organised, and that it’s designed for whoever looks at it.

Can you do it with a spreadsheet?

For a weekly report, yes. To see what’s happening now, no: someone has to type the data in by hand, and it arrives late and with errors. A dashboard connected to the machines updates every few seconds and keeps the history.

Can you see energy consumption in real time?

Yes, if the plant has power analysers or meters that can be read. The dashboard shows consumption by line almost instantly and crosses it with output to get the cost per part.

Can you see it on a phone?

Yes. The same dashboard opens on the shop-floor screen, on a PC or on a phone, each with the view it needs and only for authorised people.

Want to see your plant on a real-time dashboard? Ask for a demo: fill in the form, tell us which machines and PLCs you have and we’ll show you how it would look.


Acronyms

¹ KPI (Key Performance Indicator): a figure that tells you whether a process is going well or badly.

² OEE (Overall Equipment Effectiveness): availability, performance and quality combined into a single percentage.

³ PLC (Programmable Logic Controller): the controller that runs the machine; for example, a Siemens S7 or a Beckhoff.

⁴ HMI (Human-Machine Interface): the machine’s touch screen, where the operator runs it and sees its alarms.

⁵ OPC UA (Open Platform Communications Unified Architecture): an industrial communication standard to read data from a PLC or other device securely, with its name and type.

⁶ Modbus: a simple, widespread industrial protocol (RTU over a serial line, TCP over Ethernet). Data is read from numbered registers, following the map the device maker provides.

⁷ IoT (Internet of Things): industrial IoT (IIoT) connects machines and plant equipment to collect their data and use it.

⁸ LPG (Liquefied Petroleum Gas): propane or butane, a common fuel for burners and paint booths.