-
min
Industrial Systems Have Outgrown the Legacy Model
For decades, industrial control systems were built around a stable core: a central SCADA server, a historian, some operator HMIs, and a network of PLCs. Architectures changed slowly. Software was installed directly on machines. Updates were rare and often risky. The assumption was simple: fewer moving parts meant fewer opportunities for failure.
Today, that world has disappeared.
Modern industrial operations rely on enormous volumes of data. Factories, utilities, energy systems, and logistics networks depend on high-resolution time series, contextual metadata, quality records, machine health metrics, and traceability information. These data streams fuel analytics, predictive maintenance, energy optimization, and enterprise-wide decision-making. A system that once logged a handful of values per minute now ingests thousands per second.
At the same time, artificial intelligence has moved from research labs to the factory floor. Predictive models run on edges. Machine-learning inference engines validate quality in real time. Computer vision systems detect anomalies. AI-based operator assistants help technicians troubleshoot. None of these workloads tolerate latency or downtime, which pushes them to the edge—close to the machine, inside industrial PCs, or on dedicated inference devices.
This proliferation of data and AI has fundamentally changed OT infrastructure. Plants now rely on dozens or hundreds of distributed edge nodes: protocol gateways, HMI stations, UNS brokers, SCADA instances, buffering systems, and AI nodes. The volume of systems to install, manage, monitor, update, and secure has exploded.
This complexity forces OT teams to manage Linux hosts, containers, certificates, networking policies, and cybersecurity mechanisms — tasks that OT was never historically designed to handle with its legacy tools.
In short: the complexity has increased. The tooling has not kept pace.
Ignition as the Software Building Block of Modern OT
Ignition has long been an innovative platform capable of replacing the rigid and monolithic SCADA systems of the past. Its modularity and cross-platform design make it a natural fit for modern OT. But its greatest contribution to the future of industrial automation lies in a key architectural decision: Ignition runs as a containerized application.
Containerization marks a break from traditional industrial software deployment. It gives Ignition portability, letting it run across industrial PCs, VMs, edge gateways, and cloud instances. It ensures consistency, because every deployment originates from the same master image. It accelerates installation, turning multi-hour on-site setups into operations that complete within seconds. And because modern Ignition configurations are stored in structured JSON, they can be deployed programmatically, templatized, version-controlled, and reproduced with absolute precision.
In the container era, Ignition becomes more than SCADA or MES—it becomes a distributed software component that can be orchestrated across an entire industrial estate.
However, containerization alone isn’t enough. To run Ignition across hundreds or thousands of nodes, organizations need a higher layer of control — one that manages deployment, health, updates, access, and resilience.
This is where Barbara enters the story.
Barbara: The Orchestration Layer That Makes Scale Possible
Barbara is designed for a simple but ambitious purpose: to make distributed industrial computing operable at scale. It gives OT teams the same advantages cloud engineering teams enjoy, but in a form suitable for industrial realities — where networks can be unreliable, hardware heterogeneous, and uptime non-negotiable.
Barbara is not just a deployment tool. It is an edge orchestration platform built specifically for OT environments. It replaces manual configuration with automated workflows, replaces local interventions with secure remote execution, and replaces individual machine management with centralized fleet control.
With Barbara, every edge device becomes part of a larger software-defined fabric. It can be monitored, updated, redeployed, and secured from a single interface. And because the platform was designed for OT, it uses workflows and guidelines that operators, engineers, and automation experts intuitively understand — without requiring deep IT or DevOps experience.
Where Ignition provides the logic of industrial systems, Barbara provides the operational muscle.
A New Kind of Deployment Workflow
Consider how Ignition has traditionally been deployed: an engineer arrives at the site, connects to an industrial PC or server, copies installers, configures dependencies, adjusts file paths, loads projects, and performs initial tests. The process is hands-on, time-consuming, and highly dependent on the skill of the person performing it.
With Barbara, deployment becomes a software-driven workflow.
The edge device is first registered in Barbara’s central control plane. Once connected, it appears alongside every other node in the fleet, independent of geography. Ignition is available in Barbara’s application library as a pre-configured package that includes the container image, environment variables, persistent storage settings, exposed ports, and health checks. Deploying it onto an edge node is a matter of selecting the device, adjusting parameters like credentials and memory limits, and confirming.
Moments later, Ignition starts running on the device. No field visit. No VPN. No SSH. No manual installations. And because Barbara ensures that environments remain consistent, deployments perform reliably across every site.
Updating becomes just as seamless. Barbara detects available versions, alerts operators, and presents each update as a safe and reversible action. Updating one device works the same way as updating hundreds, and because persistent volumes store Ignition’s data and configuration, the system restarts exactly as it was — only upgraded.
This is orchestration: the transformation of deployment from a manual operation to an automated, managed, and scalable process.
The New Demands of Industrial Software
OT environments that once relied on a single SCADA server and isolated HMIs now run on distributed compute layers made up of dozens or hundreds of edge devices. This transition is driven by three major pressures.
Modern organizations depend on high-volume, high-resolution data for operational analytics, predictive maintenance, energy optimization, and enterprise integration. Where SCADA once stored only selected values, today’s systems collect machine health metrics, contextual production data, vision outputs, and energy signals—much of which must be processed at the edge before reaching cloud or enterprise systems.
Artificial intelligence has also moved from experimentation to production. Predictive models, anomaly detection engines, AI-assisted operators, and vision-based quality control all run close to machines to eliminate latency and reduce bandwidth requirements. These workloads demand distributed edge compute power.
Meanwhile, edge infrastructures are multiplying. A plant with one SCADA server a decade ago may now have dozens of industrial PCs, gateways, vision units, or dedicated inference devices. Each requires software installation, patching, monitoring, and security—tasks that quickly overwhelm manual workflows.
OT teams must now manage Linux hosts, certificates, networking, containers, and cybersecurity. The traditional approach simply cannot scale.
Ignition: Built for Modern Scale
Ignition has become the platform of choice for next-generation SCADA, IIoT, and MES implementations because of its modularity and flexibility. But what makes it especially well-suited for today’s distributed industrial environments is its shift to containerized deployment.
Running Ignition as a container unlocks a set of capabilities once reserved for cloud-native systems. It becomes portable across hardware, operating systems, and compute layers. Deployment becomes consistent because every instance uses the same image. Installation time shrinks dramatically, and updates are reduced to swapping an image tag. Configuration is externalized and structured in JSON, enabling automation, templating, and version control.
In essence, Ignition becomes a deployable software service rather than a machine-bound installation.
But while containerization makes Ignition portable, it doesn’t solve the challenge of managing thousands of distributed deployments. Orchestration does.
Barbara: The Orchestration Layer Built for Industrial Reality
Barbara is an edge orchestration platform designed to bring automation, security, and operational discipline to distributed industrial systems. It offers the power of cloud-native orchestration but without the complexity of Kubernetes, Helm charts, or DevOps pipelines—making it suitable for OT teams who require industrial-grade reliability and simplicity.
Barbara Core runs on each edge node, turning it into a managed asset. These nodes connect to a central control plane where engineers can deploy, monitor, and update workloads like Ignition from one interface. Instead of SSH connections, VPN tunnels, or local installations, teams work through a unified platform built specifically for industrial workflows.
Ignition is available in Barbara’s marketplace as a prepackaged, ready-to-deploy application. Deployment becomes a guided process that takes seconds, and updates are handled by the orchestrator without interfering with persistent data. Every instance remains consistent, and every update predictable.
Barbara turns Ignition from an application that must be installed into a fleet-wide service that can be orchestrated.
High Availability: A Core Capability, Not an Add-On
Industrial operations cannot tolerate downtime. Equipment failures, OS patches, network issues, or scheduled maintenance can interrupt local SCADA, disrupt data pipelines, or disable AI inference systems. Historically, achieving high availability required expensive redundant servers and complex custom failover logic.
Barbara introduces a fundamentally different model: cluster-based high availability designed from the ground up for distributed industrial systems.
Multiple edge nodes form a cluster where workloads like Ignition can move dynamically based on hardware health or operational needs. Persistent volumes keep data synchronized across nodes. A floating virtual IP ensures users and systems always access Ignition through the same endpoint, regardless of which node is active. If a node fails, Barbara automatically redeploys Ignition on another node and attaches the synchronized data.
This provides infrastructure-level resilience without specialized networking or duplicated hardware.
For mission-critical environments, Barbara also works with Ignition Redundancy, ensuring primary and backup gateways run on separate nodes and automatically route traffic through an integrated reverse proxy. The combination of infrastructure HA and application redundancy delivers industrial-grade continuous operation.
Conclusion: The Future of OT Is Orchestrated
Industrial operations are becoming more distributed, more data-centric, and more software-heavy. The next decade of OT will be defined not by equipment upgrades but by the ability to manage industrial software at scale. Ignition provides the application platform for that evolution. Barbara provides the orchestration, automation, and high-availability foundation that makes it sustainable in real environments.
Together, they shift industrial automation from manual deployment to software-defined operations. From isolated devices to coordinated fleets. From fragile architectures to resilient ones. From reactive maintenance to automated continuity.
This is the model that will define the future of OT — distributed, orchestrated, intelligent, and ready for the AI-powered industrial era ahead.
