Streaming factory data to Azure in one click across 31 factories
factories in scope
A multi-site abrasives manufacturer wanted local data from 31 factories in Azure without a new security approval per site. Plantformance built one central connection from a NiFi cluster to Azure Event Hubs and an Ignition module that lets developers stream tags with a click, sent every 5 seconds by default, up to 10k tags per batch.
Key results
- 31 factories in scope
- 5 s default send interval
- 10k tags per aggregated batch
The problem
The client wanted local factory data streamed to its Azure cloud for a scope of 31 factories. At the same time, it wanted local developers to stay free to choose what gets sent to the cloud. Nothing was forwarded yet, and adding interfaces was hard because of IT security requirements. A separate connection per plant would have meant a long approval cycle at every site.
What it looked like before
No data was forwarded to the cloud, in an environment where adding interfaces is difficult because of IT security requirements.
How Plantformance solved it
Plantformance created a single data connection from a central instance, a NiFi cluster, to Azure Event Hubs. With that in place, we built an Ignition module that adds a "Data streaming" section to the tag browser. Developers select one or many tags, edit the properties and turn streaming on. From then on, every change on those tags is aggregated, compressed and sent to the cloud at a regular interval, every 5 seconds by default. A single batch can carry up to 10k tags.
What changed
Any designer with editing rights can add or remove streamed tags with a click. Data arrives automatically in the enterprise Azure Event Hubs subscription.
Results
- One central cloud connection instead of one per factory
- Local developers choose which tags to stream, with no new interface work
- Data lands automatically in the enterprise Azure subscription
- The stream now feeds multiple data applications, from performance management to AI and ML studies
Plantformance products and services used
Frequently asked questions
How do developers choose which Ignition tags to stream?
The Plantformance Ignition module adds a "Data streaming" section to the tag browser. Developers select one or many tags, edit the properties and turn streaming on. Any designer with editing rights can add or remove streamed tags with a click, with no new interface work.
How often is factory data sent to Azure?
Every change on streamed tags is aggregated, compressed and sent at a regular interval, every 5 seconds by default. A single batch can carry up to 10k tags, and Plantformance routes it through one central NiFi cluster to the enterprise Azure Event Hubs subscription.
Related Ignition case studies
- Edge MySQL tables replicated to Azure with no maintenance
- New interfaces reach 20 factories in 2 weeks instead of years
- Full MES cuts customer complaint response time by 99%
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.