Skip to content
← Engineering notes

Cloud, apps and dashboards

Dashboards a plant team actually opens every morning

14 November 2026 · Shalaka engineering team

Most factory dashboards start from what the sensors can report. The result is a wall of live gauges, good in the demo, opened twice. The ones that stay in use answer a question somebody already asks at 8 a.m.

Start from the morning question

At the first meeting, ask the shift supervisor and the maintenance lead what they check first. It is usually short: what stopped overnight, which machine is behind, did anything run outside limits, is anything about to need attention. A good first screen answers them in ten seconds. No clicking.

That means a status list sorted by problem, not by machine number. Red items first, then amber, then the healthy machines collapsed into a single line such as “18 of 20 running”, so a normal morning takes a glance and a bad one shows where to walk first.

Show the exception, not the average

A trend of average temperature hides the one spike that spoiled a batch. Show the count of out-of-limit events, the longest stop and the last time each machine reported. Colour only what needs a decision, such as a stop longer than 10 minutes. If half the screen is red every day, people ignore red.

Set thresholds with the people who run the machine. A limit that fires fifty times a shift is noise. Noise ends the habit of looking.

Make staleness visible

The most dangerous number on a dashboard is one that stopped updating. Show the age of every reading, and grey out anything older than three missed reporting intervals. An offline device must look different from a machine running normally with a flat reading. Grey, not green.

Fit the places people really look

Plant staff read on a wall screen, on a phone on the floor, or in an emailed summary. So:

  • Large text, high contrast and no hover tooltips on the wall display, readable from about 5 metres.
  • A phone layout that works one-handed, with the exceptions on top.
  • A scheduled email or message at shift start with the same exceptions, for people who will never log in.
  • Local time, with the shift boundaries the plant uses.

Keep the numbers traceable

Every figure should open to the machine and the time range behind it. If an operator disputes a number and nobody can show where it came from, trust goes quickly. Show the unit, the sampling period and the formula for derived values such as OEE (overall equipment effectiveness) or kWh per unit.

What a dashboard does not fix

A dashboard shows a problem, it does not assign it. If nobody owns the red item, the screen is decoration, and the plant goes back to phone calls and WhatsApp groups. Decide who looks, at what time, and what they do next, before you build. Where the answer is a repeated manual check, a small purpose-built tool, such as a test station or a log entry form, often does more than another chart.


If you want a dashboard your team will open daily, book a discovery call, or see our cloud, apps and dashboards and micro-apps for electronics and manufacturing work.

Tell us what you are building.

A 30-minute discovery call with an engineer. We reply within 48 hours.

Book a discovery call