Spreadsheet workflows, rebuilt as governed web apps
The workbook a process depends on becomes a web app that logs each change and controls who can edit what. Nothing gets rebuilt until you sign off on the rules.
Production reporting, from the machines
Take the manual steps out of production reporting.
Most numbers in a production report already live in your PLCs and HMIs. Vectis Works reads them straight from the machines, puts them on a live plant dashboard, and then takes the copying, typing and merging out of the reports around it.
Steps that go away
What people do today to get machine numbers into a report.
-
Copying counts off HMI screens
Instead: counts come straight from the controls as parts are made.
-
Typing stops into a spreadsheet
Instead: the controls time each stop, and your people add the reason.
-
Merging shift sheets
Instead: one record across shifts, lines and work centers.
-
Sending the morning report by hand
Instead: the report builds from the same data and goes out on its own.
The core offer
Start from the machine data
We connect your PLCs, HMIs, Kepware or other OPC servers, and the spreadsheets that sit around them, into one live plant dashboard. Every report after that reads from the same place.
What the dashboard shows
- Machine status by work center
- Parts made, and how fast each machine is running
- Uptime, and each stop with its length and reason
- Scrap, wherever the controls or quality records hold it
- OEE, and how every figure trends week over week
A straight answer on OEEThe controls give you counts and run time. The rest of the math, the shift calendar and each part's ideal cycle time, normally lives in ERP or in your written standards. We bring those in with your team instead of guessing.
First shift, whole plant
Sample data
- Uptime
- 91%
- Parts
- 6,412
- OEE
- 72%
Work centerPartsRate
Press 01Running1,28442/min
Press 02Down, die change9160/min
Weld cell 3Running2,17224/min
Paint lineIdle, no material2,0400/min
Uptime by day
2 stops waiting for a reason from the line
Read-only connection
We read tags and logs. Nothing we set up can send a value back to a PLC.
Yours to keep
Everything we build, and the data in it, sits in your environment and belongs to you.
Support if you want it
Ongoing support is an option we offer. It is not a licence you are tied to.
Beyond the dashboard
Then the work around it
Once the machine numbers arrive on their own, the spreadsheets, re-keying and reports built on top of them are next.
Integrations between systems
Machine data, your ERP and the other systems in the building pass records to each other, so nobody keys the same number twice.
Reports that assemble themselves
Shift, daily and weekly reports build from one structured data layer and arrive without anyone copying and pasting.
Also on the table: internal tools shaped around how your floor works, one structured data store your other software can reach through APIs, and ongoing support.
People and judgment
What stays with your people
Taking out the typing does not take out the people who know the line. The system does the copying. Two things stay where they belong.
What the system takes on
- Reading counts and run rates from the controls
- Timing every stop, start to finish
- Building and sending the report
Stays at the line
Stop reasons
The controls know a machine stopped and for how long. They rarely know why. Operators and supervisors confirm the reason while it is fresh, and the dashboard carries their answer, not a guess.
Stays with your team
The decisions
Which line to fix first, what to run next, who owns the follow-up. The numbers show up on their own. What to do about them is still your call.
Four steps
How a project runs
Staged work, one line and one report at a time, with your team checking the numbers along the way.
The people who scope it also build it. Between them they cover PLC and controls work (Allen-Bradley included), ERP advisory, integration and data architecture, and development on both backend and frontend. Their systems work spans 20+ years inside operations-heavy businesses.
-
Step 1
Walk the reporting
We sit with the people who build today's reports and list every manual step, from the HMI screen to the morning email.
-
Step 2
Connect read-only
We map the tags in your PLCs, HMIs and Kepware and set up a read-only connection your IT and controls people can check.
-
Step 3
Build the first views
The dashboard and the first report go up for one line. Your team checks the numbers against what they see on the floor.
-
Step 4
Retire the manual steps
Once the numbers hold up, the copying and typing stop. Then on to the next line, report or spreadsheet.
Which report still gets built by hand?
Tell us what gets copied, typed and merged around production today. You will hear from the people who would build it, and if it is not a fit, we will say so.
Ask about your reporting
Opens the Vectis Works contact form.