Home
/
Case studies
/
New interfaces reach 20 factories in 2 weeks instead of years
Integration and data

New interfaces reach 20 factories in 2 weeks instead of years

Client
A multi-site manufacturing group
Industry
Multi-industry
2 weeks

from interface request to rollout

A multi-site manufacturing group running Ignition needed a security approval for every new connection at every plant. Plantformance built one reusable data communication layer with Apache NiFi, locally and centrally, with proxying and buffering. A new interface now goes from request to rollout across 20 factories in 2 weeks, including development and validation on 1 site.

Key results

  • 2 weeks from interface request to rollout
  • 20 factories per rollout

The problem

A large group was in the middle of a major Ignition rollout on Plantformance FactoryBrain servers. Its security environment was locked down: every port and every connection to Ignition needed approval. Connecting any new solution to all factories, such as cloud, ERP or streaming, meant a new approval document for each factory. Some solutions would clearly take years to deploy because of process alone, not technology.

What it looked like before

Each new connection request across several factories was a long, painful process. It involved local, central, business and security stakeholders, plus Plantformance and the service supplier.

How Plantformance solved it

Plantformance proposed a major project to fully abstract every non-factory interface. The idea was to build one data communication layer, once, and reuse it every time a new global interface is requested. This solved the approval problem. It also added a proxy layer, so Ignition never connects directly to outside services, and a buffering and reprocessing layer for guaranteed data delivery. We built it with Apache NiFi locally and centrally, on a high-availability cluster, with site-to-site connectivity and buffering.

What changed

Factories have no direct connection to any external system. Data is wrapped in its own protocol, yet Ignition developers keep it simple, for example one line of code to confirm a production order. Data is buffered locally and centrally in both directions, and monitoring gives a live view of every data flow with alerting.

Results

  • A new interface goes from request to rollout across 20 factories in 2 weeks, including development and validation on 1 site
  • Massive savings in deployment time
  • Complex solutions now roll out fast across all factories
  • Data exchanges ride through communication incidents thanks to local and central buffering

Plantformance products and services used

FactoryBrain, Professional Services

Frequently asked questions

Why did new factory interfaces take so long before?

Every port and every connection to Ignition needed approval, so each new solution, such as cloud, ERP or streaming, meant a new approval document per factory, involving local, central, business and security stakeholders. Some solutions would have taken years because of process alone, which Plantformance solved with one reusable layer.

What happens to factory data if communication fails?

Plantformance buffers data locally and centrally in both directions, with a reprocessing layer for guaranteed delivery, so data exchanges ride through communication incidents. Monitoring gives a live view of every data flow with alerting, and Ignition never connects directly to outside services.

Related Ignition case studies

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.