Plan the next repair from the machine's own stop record.
Your presses, mills and cells already note every time they stop, and often why. Vectis Works pulls that history out of the controls and lays it out per machine, so the maintenance planning meeting starts from what happened on the floor, not from what someone remembers.
Monday planning
The questions maintenance asks each week
Where the technicians' hours go next depends on four answers. Most shops piece them together from work orders, operator notes and whoever was on shift.
Which machine stopped the most?
Counted from the machine's own status, across every shift, including the stops nobody wrote up.
Which fault keeps coming back?
Grouped by the reason code the controller raised, so a recurring jam shows up as a pattern rather than a feeling.
How long was it down each time?
Ten short stops and one long one call for different repairs. Duration tells you which kind you have.
Is it getting worse or better?
This week set against the weeks before, so you can see whether last month's fix held.
Already on the controls
Your machines have been keeping the record all along
PLCs and HMIs track their own state to do their job. That same data answers the maintenance questions once someone reads it out and keeps it.
- Running or stopped. The status the controller already holds, with a time on every change.
- Fault and reason codes, where the machine has them. Newer equipment often names the fault; older equipment may give only a status light, which still yields stop counts and durations.
- Run hours, for planning service by actual use instead of by the calendar.
- Part counts, so a stop can be read against how much the machine was producing around it.
What each machine can report varies. We check that first, per machine, and tell you plainly what it can and cannot show.
What it looks like
A week of stop history, machine by machine
A table like this replaces the guesswork in the weekly planning meeting. The rows below are invented to show the layout.
| Machine | Stops | Minutes down | Most frequent fault | Against last week |
|---|---|---|---|---|
| Press 4 | 23 | 214 | Die jam | More stops |
| CNC mill 2 | 11 | 96 | Spindle alarm | About the same |
| Weld cell 1 | 41 | 137 | Wire feed | More stops |
| Band saw | 4 | 71 | Blade change | Fewer stops |
| Grinder 3 | 9 | 158 | Coolant low | Longer stops |
Safe for production
We only read from the controls
The connection pulls values out of your PLCs and HMIs. It writes nothing back: no setpoints, no recipes, no logic changes. Production runs exactly as it did before.
Your IT group and your controls people can inspect the connection themselves and confirm it is read-only before anything goes live. The data and everything we build on it stay yours.
Getting started
Begin with one cell, or the one machine that keeps calling you back
There is no plant-wide rollout to sign up for. Pick the equipment that costs your team the most hours and start there.
Name the machine
You tell us which one, or which cell. We look at what its controller holds and what it can report.
Read its history
We connect read-only, map its status and fault data, and build the per-machine stop view.
Decide from there
If the record changes how your team plans repairs, add the next machine. If it doesn't, you stop there.
Beyond maintenance
Other work we do on the same data
Once the machine data is flowing, the rest of the plant can use it too.
A full plant dashboard
Run rates, uptime, downtime with reasons and OEE for every line on one screen, live from the machines.
Spreadsheets turned into systems
The workbooks your shop depends on, rebuilt as proper tools that several people can rely on at once.
Custom software
Applications built around how your plant works, delivered with the code so you own what we build.
A structured data layer
Clean, named machine data behind an API, ready for reports and for other systems you add later.
Want to see the plant-wide version? Browse a sample plant dashboard.
Which machine does your team fix most often?
Tell us about it. We'll say honestly whether its controls hold a useful stop record, and what it would take to read it.