Isolated development servers with no change in operating costs
factories previously shared 1 or 2 development servers
A multi-site industrial manufacturer, where 1 or 2 development servers covered 90 factories, wanted to separate Ignition development from production. Plantformance added a virtualization layer to the spare FactoryBrain node, so every 2-node site can run an isolated development instance. Operating costs did not change, and the emergency fallback stays in place.
Key results
- 90 factories previously shared 1 or 2 development servers
The problem
The client wanted to start separating Ignition designers from production, which meant giving factories their own development servers. Across dozens of factories, dedicated development hardware would have been very expensive. Software, operations, and maintenance would add even more. The client needed a way to give designers a safe place to work without multiplying servers and running costs at every site.
What it looked like before
1 or 2 development servers covered 90 factories.
How Plantformance solved it
A standard Plantformance FactoryBrain setup runs as a pair of 2 nodes. Node 1 runs production Ignition. Node 2 receives snapshots and backups and acts as a cold spare. Plantformance reviewed the architecture and added a virtualization layer used only for disaster recovery. That layer also made it possible to run a development instance on node 2, fully isolated from node 1. During an emergency, the development instance can be swapped for production almost instantly. The capability is now a standard FactoryBrain feature.
What changed
On a 2-server setup, a development server is a one-off software option. Teams work in both production and development, and the emergency fallback stays in place.
Results
- Every 2-node site can run its own isolated development instance
- Operating costs did not change, even with the added development server
- Emergency fallback to node 2 is still available
- Now a standard FactoryBrain feature for all clients
Plantformance products and services used
Frequently asked questions
How can you separate Ignition development from production without new hardware?
Plantformance used node 2 of a standard FactoryBrain pair, which already receives snapshots and backups as a cold spare. A virtualization layer lets it run a development instance fully isolated from production on node 1, with no change in operating costs.
What happens to the development server during an emergency?
Plantformance can swap the development instance on node 2 for production almost instantly. Teams work in both production and development, and the emergency fallback to node 2 stays in place for every site with a 2-server setup.
Is the isolated development instance available to other FactoryBrain clients?
Yes. The isolated development instance on node 2 is now a standard FactoryBrain feature for all clients. On a 2-server setup, Plantformance offers the development server as a one-off software option.
Related Ignition case studies
- 18 factories keep running locally while a cloud ERP syncs in the background
- 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.