Make the Fifth Fix Faster than the First
Build a plant application once, then roll it out to every site

Most plants can build the application their line needs. The expense shows up at the second site, which builds its own version, and at the third, which builds another. Five sites later you are supporting five versions of the same fix, and none of their numbers can be compared.
One fix, every site
Walter Tools had this problem across its production units. A seven-person IT team was maintaining five separate connectivity and dashboarding tools, and some units had none at all. Today they copy proven flows from one unit to the next, and a new production unit is connected in hours rather than months.
In this session, Kristopher walks through the approach behind that result, the same one FlowFuse uses with manufacturers in the Foundation Partnership.
What you'll learn
- How to choose the first problem. Look for a loss you can put a number on, someone on the floor who owns it, and data your equipment already produces.
- How to build on what you already run. Connect the PLCs, historian, MES, ERP and CMMS already in the plant through Node-RED, without adding another system.
- How to turn it into a blueprint. Decide what every site shares and what each site changes, then deploy it to the next site through FlowFuse pipelines, with an engineer approving each change.
Live demos
- OEE on a packaging line. Short stops appear as they happen, while the shift can still act on them.
- Pump health. When a bearing reading starts trending up, the board raises a maintenance work request for a planner to approve.
The last part of the hour is open Q&A. Bring your integration and rollout questions.
Who it's for
Operations leaders, controls engineers and digital transformation teams who have an application working at one site and need it running at the others.
Already have a problem in mind?
We build the first solution with your team, then help you take it to every site. Talk to us about your first fix