Standard package · on subscription

Your machines are already telling you. We make it visible.

Live status, production counters, downtime, OEE and energy, straight from the controller. No retyping lists at the end of the shift. You subscribe to the modules you use; we manage and update them.

Ask about a pilot See the example first

Read onlyDoes not write to the controller, controls nothing
OPC UA · Modbus · MQTTOr an export file from your own system
Five modulesOn one base with login, roles and audit log
Per machineStart with one line, expand per machine

01 — Try the example

Modular

Switch a module on or off and see what happens to the screen.

Every module is a switch, not a new project. Click through the menu, open a machine or a downtime event, and add OEE and energy as soon as the data is there. The base is always there.

Example screen

Machine dashboard

Click through the menu on the left, open a machine, a downtime event or a shift, and switch modules on or off. Everything you see is made up.

Base

3 of 5 modules active

Collector hall 1 · connected · 4 machines

Fictional example

Hall 1 · shift 2

Tuesday 22 September · 14:00 to 22:00 · crew B

3 of 4Machines runningPacker is stopped

4,280Units line 1 this shiftTarget 6,000 · on schedule

75 minDowntime todayMain cause: changeover

77%OEE this weekLast week 74%

42 kWhPer 1,000 units, line 1Line 2: 47 kWh

In the hall now

Line 1Running · 62 per min
Line 2Running · 58 per min
PackerStopped · 12 min
OvenWarming up · 184 °C

Notifications

13:48Packer stopped · reason from controller: changeover
13:30Line 2 below target (5,100 of 6,000 expected)
11:05Sensor S4 fault, 22 min · operator: "cable loose"
10:00Line 2 uses 12% more per 1,000 units than line 1
06:00Collector connected · OPC UA 2 s · MQTT 5 s

Live status

Refreshed every 2 seconds · from the controller

Line 1Filling machine · PLC via OPC UA · last message 1 s ago

Running

62Units per minute

4,280Units this shift

0Rejects this shift

38 °CMotor temperature

6.1 barCompressed air pressure

2 sConnection heartbeat

Last 8 hours · units per hour

0607080910111213

Downtime

Today · 75 minutes · 6 events

Top causes today

Changeover38 min
Sensor fault22 min
Waiting for material15 min

Log

Packer · changeoverSince 13:48 · still running · reason from the controller

In progress

From: 250 g format
To: 500 g format
Planned: Yes · standard changeover time 30 min
Operator: No comment yet

Whether planned downtime counts towards OEE depends on your own definition. You set that yourself.

This week per day

MonTueWedThuFri

OEE

Week 39 · availability × performance × quality

86%Availability

91%Performance

98%Quality

77%OEE

Per machine · this week

Machine	A	P	Q	OEE
Line 1	90%	94%	99%	84%
Line 2	88%	90%	97%	77%
Packer	79%	89%	98%	69%
Oven	86%	92%	99%	78%

Where it leaks: for the packer it is availability, so downtime, not speed or quality.

Trend · last 8 weeks

3233343536373839

Your definitions

Planned time: 2 shifts of 8 hours, breaks excluded
Changeover: Counts as downtime
Standard speed: 65 per minute, adjustable per machine

Design principle: we connect to what the machine already offers, such as the controller (PLC) via OPC UA or Modbus, MQTT messages or an export file. The dashboard is designed to read only: it does not write to the controller and does not control any machines. The connection to the machine is set up securely for each situation.

All names and figures in this example are made up.

Ask about a pilot

02 — What each module does

Base plus five modules

What the controller already knows, on one screen for the whole hall.

The base handles the connection to your machines and who may log in. Every module on top of it shows one thing and works together with the rest.

Base
Connection, login and audit log

Always included, even if you start with one module.
- Reading via OPC UA, Modbus, MQTT or an export file
- One collection point at your site, outbound traffic only
- Login with two-step verification, roles per hall or line
- Audit log of settings and changes
- Large screen in the hall, phone for the team leader
01
Live status

Per machine: running, stopped, fault or maintenance, with the current speed.
- Statuses straight from the controller
- Last message and heartbeat per connection
- Alert if a machine is stopped for longer than agreed
- Overview per hall, detail per machine
02
Production

Counters per shift, against the target, per line and per crew.
- Units, metres or kilos, whatever the machine counts
- Target per shift and progress over time
- Comparison between lines and crews
- Daily totals without manual lists
03
Downtime

How often, how long and why a machine was stopped.
- Reasons from the controller, supplemented by the operator
- Top causes per day, week and month
- Changeover separate from faults and waiting
- Duration per stoppage, from the first to the last minute
04
OEE

Availability, performance and quality, per machine and per period.
- Calculated from status, counters and rejects
- Per day and per week, with trend
- The three factors separately, so you can see where it leaks
- Your own definitions of planned and unplanned time
05
Energy

Consumption per machine and per thousand units, from meters or the controller.
- kWh per machine, per shift and per product
- Consumption during downtime shown separately
- Comparison between lines that make the same product
- Also gas, compressed air or water if there is a meter

03 — What we have already built

Anonymised

The building blocks come from these projects.

Three projects in which data from machines, sensors and the shop floor came live onto a screen, without customer names. What is in use is in use; what is a design, we call a design.

Machine building · cutting machines for steel

Machine fleet dashboard for a manufacturer of cutting machines

A clickable design for a machine builder who wants to give its customers a live view of their machine fleet. Built on what the controller, the robot and the plasma source actually deliver, not on what would look nice on a dashboard.
- Six machines with status, OEE and a fault log
- Trends from two hours to thirty days: arc voltage, cutting speed, coolant temperature, gas pressure
- Per machine the data sources, the protocol and the heartbeat of the connection
- Efficiency grade A+ to D per machine, like an energy label
DesignClickable, with fictional data
Horticulture · nursery with export customers

Temperature dashboard from shipment measurement reports

Data loggers in shipments deliver measurement reports as PDFs. We read the measurement series automatically and show per shipment the course, the peaks and the alarms, for the customer in their portal and for the quality team internally.
- Dozens of shipments per year, processed automatically
- Minimum and maximum per shipment, alarm when exceeded
- Click through to the full measurement series and the report
In useBy customer and quality team
Horticulture · greenhouses and warehouses

Stock movements on the shop floor, live on one shared screen

Staff record on their phone what is potted, moved or removed. The stock per greenhouse section is updated immediately for everyone, without anyone retyping lists at the end of the day.
- Dozens of sections across several greenhouses and warehouses
- Every movement recorded, stock calculated live
- Works on the staff member's phone in the greenhouse
In useEvery day, on the shop floor

We do not name customers on this site. In a conversation we show more, with the customer's permission.

04 — Principles

Read only

A dashboard should watch. Not control.

A connection to your machines is a connection to your production. These agreements apply to this package and are set out in the agreement.

The dashboard never writes
The package reads from the controller and sends nothing back. You change machine settings where you do so now.
One collection point at your site
A small system in your own network reads the machines and sends outbound only, to the dashboard. From outside there is no route to the machines.
Secured per situation
Which protocols, which network zone, which accounts: we agree that with your machine supplier or your own technical department before anything is connected.
Machines, not people
The package measures machines. Linking to an operator only if you want it, and then only per shift, never per action.
Your data remains yours
Hosted in the European Union or on your own infrastructure. You can take your measurement data with you at any time.
Your definitions
What counts as planned downtime, what counts as rejects and how OEE is calculated is up to you. We do not calculate with a standard that does not fit your hall.

05 — Works together with

One base

The same users, permissions and audit log for every package.

Packages work together because they sit on the same base. And whatever does not quite fit, we build to measure alongside.

06 — Practical

Subscription, pilot and connection

What you get, and what you arrange in advance.

Subscription: Per month, per package and per module, per machine. Management, updates, backups and hosting are included. The collection point at your site is part of it.
Pilot: We start with one machine or line. After a few weeks you see whether the data is correct and what it delivers; then you decide on expansion.
Connection: In advance we survey, per machine, which controller it has and what it can output. Sometimes that is OPC UA or Modbus, sometimes an export file. Without intervening in the machine.
Network: The collection point sits in your network and talks outbound only. We coordinate the set-up with your technical department or machine supplier.

Curious what your machines can already tell you?

In a half-hour conversation we walk through your machine fleet: which controllers, which data, and what you want to see first.

Ask about a pilot

Your machines are already telling you. We make it visible.

Switch a module on or off and see what happens to the screen.

Hall 1 · shift 2

In the hall now

Notifications

Live status

Last 8 hours · units per hour

Production

This shift · target 6,000 per line

Per hour · line 1

Shift 1 · 06:00 to 14:00 · crew A

Rejects shift 1

Week 39 · total per line

Per day · all lines

Downtime

Top causes today

Log

This week per day

OEE

Per machine · this week

Trend · last 8 weeks

Your definitions

Energy

kWh per 1,000 units

Per hour · line 2

Total today

Also measurable

Consumption during downtime · today

What the controller already knows, on one screen for the whole hall.

Connection, login and audit log

Live status

Production

Downtime

OEE

Energy

The building blocks come from these projects.

Machine fleet dashboard for a manufacturer of cutting machines

Temperature dashboard from shipment measurement reports

Stock movements on the shop floor, live on one shared screen

A dashboard should watch. Not control.

The dashboard never writes

One collection point at your site

Secured per situation

Machines, not people

Your data remains yours

Your definitions

The same users, permissions and audit log for every package.

Time tracking

CRM

Custom work alongside

What you get, and what you arrange in advance.

Curious what your machines can already tell you?