Spreadsheets rebuilt as web apps
We rebuild the spreadsheet workflows your plant depends on as governed web apps.
- An audit trail
- Permissions by role
- Rules you approve before anything is rebuilt
A sample plant dashboard
Click through a plant dashboard before you talk to anyone.
We connect PLCs, HMIs, Kepware or OPC and the spreadsheets around them into one live view of the floor. The sample shows what that looks like. If it fits how your plant runs, ask for one on your own lines.
The sample dashboard runs on representative sample data. It is not a customer's plant.
Floor status board
Sample plant, second shift
Press 01Running1,284parts
Press 02Running1,302parts
Brake 03Down846parts
CNC 04Running412parts
CNC 05Idle377parts
Lathe 06Running598parts
Weld 07Running233parts
Weld 08Down190parts
Saw 09Idle655parts
Mold 10Running2,040parts
Paint 11Running318parts
Pack 12Running1,127parts
Before you talk to us
What to look for in the sample
Open the sample dashboard in another tab and look for these four things. Each is a view we build from numbers your machines already produce.
1
Status by work center
Look for running, idle or down on every machine. The state of the floor reads without walking it.
2
Counts and run rates
Look for part counts by line and shift, with the run rate next to the ideal. A slow machine stands out even while it runs.
3
Downtime with a reason
Look for how long each stop lasted and why. That is the difference between knowing a line was down and knowing what to fix.
4
OEE and the trend
Look for OEE and how it moves over days and weeks. Scrap sits alongside it where the data carries it.
From sample to your floor
What changes when it's your plant
The views keep their shape. What feeds them comes from your machines and your office.
In the sample
Sample tags
Made-up tag names standing in for a typical mix of presses, CNCs and weld cells.
On your lines
Your tags
Read from your PLCs, HMIs and Kepware or OPC server, then mapped to the names your team uses on the floor.
In the sample
Sample shift calendar
A generic shift pattern, so availability has something to count against.
On your lines
Your shift calendar
Your planned shifts, breaks and down days, usually from ERP or a planning sheet rather than the controls.
In the sample
Sample stop reasons
A short, generic list of the kind any plant might keep.
On your lines
Your stop reasons
The words your operators and supervisors already use, attached to the stops the machines record.
In the sample
Sample part numbers
Placeholder parts with placeholder cycle times.
On your lines
Your part numbers
Your parts and ideal cycle times from your standards, so run rate and OEE compare against the right target.
About OEE. The controls give us machine status and counts. Shift calendars and ideal cycle times usually come from ERP or your standards, not from the controls. We bring them in from there instead of guessing.
Getting started
What we need from you
Four things put a first line of yours on the board. Write access to your controls is not one of them.
Read-only. We read tags and logs. There is no write path to the controls.
Yours to keep. It runs inside your environment. You own the code, the data and the systems.
Support if you want it. Ongoing support is optional, not a licence.
- Access set up with your IT teamA read-only connection your IT and controls people approve and can check for themselves.
- The tag list or controls projectA Kepware export, a PLC program or a tag spreadsheet shows us what already exists.
- Time with a supervisor who knows the lineSomeone who can say what a stop really was and which numbers matter first.
- Your shift calendar and standardsPlanned hours and ideal cycle times, which usually live in ERP or your standards.
Capabilities
The dashboard is one of the things we build
One team covers controls and PLC work, including Allen-Bradley, data architecture and integration, backend and frontend development, and ERP advisory. We bring 20+ years building systems inside operations-heavy businesses.
Automation and integration
We connect the systems that don't talk to each other, so every tool reads the same numbers.
- Workflow automation
- System integrations
- A structured data layer with APIs
Reports, tools and support
We build the reports and internal tools the people who run the floor reach for every day.
- Reporting that assembles itself
- Custom internal tools
- Ongoing support, if you want it
Seen the sample? Put your own lines on it.
Tell us which line and which numbers you'd want first. If it isn't a fit for your floor, we'll say so.