18 factories keep running locally while a cloud ERP syncs in the background
factories rolled out in 14 months
A multi-site manufacturer moving to a new cloud ERP needed every plant to keep running if the cloud or network failed. Plantformance built a dedicated container on FactoryBrain servers and rolled out on-premises Ignition to 18 factories in 14 months. Operators now run 100% locally while ERP synchronization and updates happen in the background.
Key results
- 18 factories rolled out in 14 months
- 100% of operations run locally
The problem
The business chose a new ERP and went through a major transformation across 18+ factories. The ERP came with an Ignition-connected application that ran only in the cloud. That worked on paper, but it gave no guarantee of operations for local staff in plants that run around the clock. Maintenance windows, network problems or a cloud outage could stop the shop floor. The client wanted a firm guarantee: each factory must be able to keep operating locally, no matter what happens in the cloud or on the network.
What it looked like before
The Ignition MES application connected to the ERP ran only in the cloud. It was exposed to maintenance downtime, network issues and cloud availability problems.
How Plantformance solved it
Plantformance built a dedicated container that runs all the plumbing the ERP requires, close to the line. We then designed a repeatable rollout method for connecting each site to the cloud. With that method in place, we rolled out Ignition to 18+ sites, each on a Plantformance FactoryBrain server running the purpose-built container. Operators work against the local system. Synchronization with the cloud ERP and updates run in the background, so a cloud or network incident no longer reaches the operator's screen.
What changed
Operators now work 100% locally while all synchronization and updates happen in the background. The factory cannot even tell whether the cloud ERP is connected.
Results
- 18 factories rolled out in 14 months
- Production orders flow in the background
- Plants keep operating locally through cloud or network incidents
Plantformance products and services used
FactoryBrain, Professional Services
Frequently asked questions
How long did the Ignition rollout take?
Plantformance rolled out Ignition to 18 factories in 14 months. A repeatable rollout method for connecting each site to the cloud made that pace possible, with every site running a Plantformance FactoryBrain server and a purpose-built container close to the line.
How does Plantformance keep plants running if the cloud is down?
Operators work against a local Ignition system on a Plantformance FactoryBrain server. Synchronization with the cloud ERP and updates run in the background, so a cloud or network incident no longer reaches the operator's screen. The factory cannot even tell whether the cloud ERP is connected.
Related Ignition case studies
- Isolated development servers with no change in operating costs
- Ignition live in a large factory 5 days after the order
- Managing 200+ Ignition servers in one click, 99% faster
Planning a similar project? Talk to a Plantformance Ignition engineer or browse all 37 Ignition case studies.
Planning a similar Ignition project?
Tell us about your plants and your Ignition setup. A Plantformance engineer will show you how a project like this would work for you.