The state of the business on one screen, now, not in next month's report
Jobs, deadlines and the workload of people and machines, refreshed continuously from systems you already have. Managers see a problem before it becomes a delay.
From question to screen
We start with the decisions someone makes every day.
- 1DecisionsWe agree who looks at the screen and what they decide from it: moving a job, adding a shift, calling a client.
- 2DataWe combine data from the ERP, production, warehouse and calendars. Every metric has one definition.
- 3ScreenWe design a view for the office, the shop floor or a phone. The key numbers are readable from a distance.
- 4AlertsWhen a job runs late or a machine stops, the person responsible gets a notification.
Signs you need a dashboard
You learn the state from last month's report
The manager walks the floor
A magnetic board
Everyone counts workload differently
Where the dashboard gets its data
Data stays in the source systems; the dashboard reads it.
ERP
Production
Warehouse and transport
Calendars and rosters
Screens
Technology
How we check the results
Before rollout we count late jobs and the time from problem to response. Afterwards we compare.
- 1Late jobs
- 2Time from problem to response
- 3Reports built by hand
- 4Alerts handled on time
The dashboard keeps history, so you can see whether problems repeat.
Common questions
How is this different from Power BI?
Power BI is good at describing the past. An operational app shows the current state and lets you act on it straight away, for example by moving a job.
Does the data have to be perfect?
No. We show data gaps on screen and fix them along the way.
Will it work on a TV on the shop floor?
Yes. We design a separate view that's readable from several metres away.
How often does the data refresh?
As often as the source systems allow, usually every minute or on every change.
Tell us what you want to see in real time
Let us know who will look at the screen and what they decide from it. We reply within one business day.