Shop-floor dashboard
One live screen, read three ways over one shift.
The shift supervisor checks it first thing. Maintenance turns to it when a machine stops mid-morning. In the afternoon the plant manager reads the whole day from it, with no report to build. Vectis Works puts that screen together from your PLCs and HMIs, from Kepware or another OPC server, and from whatever spreadsheets sit alongside them.
- Shift supervisorWhich machines are up or down, and the counts the night shift finished on.
- MaintenanceThe machine that just stopped, how long it has been down and the reason given.
- Plant managerUptime, downtime by reason and OEE for the day, already added up.
The times are sample times, drawn for illustration.
The supervisor
Start of shift
The first look of the day, before anyone walks the floor.
A supervisor coming on shift needs a picture of the floor before making rounds. The screen lays one out: every machine marked running, idle or down, so the rounds can begin at the machine that needs attention instead of at whichever one is nearest the door.
Beside each machine's status sit its part count and run rate, carried over from the shift that just ended. A line that finished behind is visible straight away, and the start-of-shift meeting can open with the real figures rather than somebody's recollection of them.
Nobody types these in. The values come from the controls, and they are the same ones maintenance and the plant manager will be looking at later in the day.
Maintenance
When a machine stops
A stop reaches the screen as soon as the controls register it. The machine's status changes and its downtime starts counting, so maintenance knows which asset is down without waiting for a call over the radio or a walk across the building.
Once a reason is captured, whether the controls report it or an operator enters it at the panel, it shows next to the stop. Over the morning, stops and their reasons collect into a list by machine and by cause, which makes a problem that keeps coming back easier to see.
Open the sample dashboardIt runs on sample data, not on a real plant's numbers.
The plant manager
End of the day
By the afternoon the plant manager wants to know how the day went. That used to mean somebody pulling exports into a spreadsheet. Here the view is already assembled: uptime and downtime for each line, stops grouped by reason, part counts and run rates, scrap where the data exists, and OEE with its trend across days and weeks.
Because it is the same live data the supervisor opened the shift with and maintenance worked from mid-morning, the figures in the afternoon meeting match what the floor saw. Nobody has to reconcile three versions of one day.
What sits underneath
Three things hold the screen up, and each is something your own controls and IT people can check for themselves.
-
A connection that only reads
We take values from the PLCs, HMIs and OPC servers and send nothing back. There is no path from the dashboard to a setpoint or a command.
-
Tags matched to plain names
Raw tag addresses are mapped to machines, parts, shifts and stop reasons, so a number on the screen means the same thing to everyone who reads it.
-
Yours to own, with support if you want it
Code, data and systems stay in your environment and belong to you. Help after the build is there if you ask for it, and it never turns into a licence.
Other work on the same data
Once the plant's numbers are connected and named, other jobs get easier. The people doing them cover controls and PLC programming, Allen-Bradley included, how data is structured and joined up, the software behind a screen and the screen itself, and advice on ERP. Between them sit more than twenty years spent building systems for businesses where operations carry the load.
- Spreadsheet workflows turned into governed web apps
- Hand-offs automated, and systems integrated with each other
- A structured data layer with APIs other tools can call
- Reports that put themselves together
- Internal tools built around one job
- Ongoing support once the work is live
Tell us how a shift runs at your plant.
Who looks at the numbers first, who needs them when something stops, and who reports on the day. We'll say plainly whether a screen like this would change anything for those people, and if it wouldn't, we'll tell you that too.