Skip to content
Mesonify

Module

Dashboard

Dashboard is the KPI wall for the whole plant: OEE per line and shift, the stop reasons ranked by what they cost, and MTBF and MTTR beside them. Pick the widgets and put the wall on a second screen.

Request a demoAll modules
Dashboard OEE, line A, shift 278%Availability89%Between failures38dTime to repair3.4hOEE per day, line A50100MonTueWedThuFriSatWhere the shift went, line A450minRunning37283%Stops429%Slow cycles276%Scrap92%

What it does

OEE per line, machine and shift

One figure, and the availability, performance and quality behind it shown on their own, so you know which one to chase.

Losses ranked by cost

Stop reasons and event classifications as a Pareto by minutes and by money, with the cumulative curve that shows where the first fix pays.

Reliability KPIs

MTBF, MTTR, mean work time and mean idle time as tables and graphs, with configurable red limit lines.

Throughput and deadlines

Events created vs. completed, completion-time breakdowns and in-time vs. after-deadline totals.

Costs and rankings

Device downtime cost, day-by-day and cumulative procurement spend, and users and devices ranked by the events they created, completed or carried.

Your own KPI wall

Pick and order widgets per workstation, filter everything by date, group and location, pop any widget onto a second screen, and send the wall by e-mail on a schedule.

How it works

  1. Set the targets

    Ideal cycle time per product and machine, the planned shifts and breaks, and the red limit line on every KPI that supports one.

  2. Let the floor feed it

    Counts, scrap and stop reasons arrive from the Terminal, jobs and their times from Events, machine state from Rules and the API. Nobody fills in a sheet.

  3. Choose your widgets

    Pick which widgets a workstation shows and in what order, and filter them all at once: one date range, one set of locations and groups.

  4. Chase the loss

    Open the Pareto, click a reason and see the stops behind it, the machines they hit and what they cost. Any widget pops onto a second screen for the corridor.

Stop reasons

A loss you can name is a loss you can fix

OEE is only as good as the reasons behind the stops. The list is yours, and the Terminal makes naming a stop faster than ignoring it.

  • Your own list

    Tool change, material wait, setup, sensor fault, operator: the reasons your plant already talks about, grouped the way you group them.

  • Planned or unplanned

    Each reason is one or the other, so a break or a planned changeover lowers nothing and a jam lowers availability.

  • The machine names its own

    A stop that a Rule detected carries the sensor reading that triggered it, so the operator confirms rather than guesses.

  • Red lines on the wall

    Set a target per line and the board turns red the moment the shift falls under it.

Stops raised as faults become work orders in Events, so the minutes lost and the repair that ended them stay on the same device record.

Part of

MES, Manufacturing Execution

See the platform

Works with

Modules are switched on per customer. Start with the ones you need and add the rest when you are ready.

See Dashboard running on your own plant.

Ask for a demo with your own devices, parts and jobs.

Request a demoAll modules