Saint-Gobain Glass covers every factory with zero interface prerequisites
factories covered by default
Saint-Gobain Glass built an edge management app on Ignition that needed heavy data exchange with MicroStrategy, MS Planner and other systems. Plantformance built a central middleware layer that abstracts 5 interfaces per factory, so all 18 factories are covered by default with zero data interconnection prerequisites and nothing to set up.
Key results
- 18 factories covered by default
- 5 interfaces per factory abstracted centrally
The problem
Saint-Gobain Glass wanted a local management application running at the edge on local data, with heavy data exchange with MicroStrategy, MS Planner and other systems. The application was designed by 2Gi, an Ignition integrator, and Saint-Gobain Glass asked Plantformance to handle all the interfaces. It quickly became clear that with 18 factories and 5 interfaces per factory, IT security requirements would stretch implementation into years. The MicroStrategy data needs would also have failed on call volume, data size and backend latency.
What it looked like before
A very good Ignition application that would have faced a very long rollout. Its data exchanges would also have hurt the performance of the Ignition gateway.
How Plantformance solved it
Plantformance built a central middleware processing layer that abstracts every interface the local application needs. For MicroStrategy, we built a dedicated layer: each factory sends a catalog of requests in one query, the central layer runs all the actions until everything is done, and it pushes one compressed data packet back to the site with all the requested data. Interfaces to MS Planner and the other systems are abstracted the same way. Plantformance also provides Ignition scripting APIs that the integrator uses in the application.
What changed
2Gi keeps developing and upgrading the application using the Ignition scripting APIs built by Plantformance. Plantformance manages all data flows and the central middleware, and the solution is extremely reliable.
Results
- A rollout that would have taken months per site is now implicit
- All factories are covered by default, with nothing to do to get the solution working
- Saint-Gobain Glass and 2Gi decide when to roll out each factory
- Zero data interconnection prerequisites per factory
Plantformance products and services used
Frequently asked questions
How did Plantformance handle MicroStrategy data volumes?
Plantformance built a dedicated MicroStrategy layer. Each factory sends a catalog of requests in one query, the central layer runs all the actions until everything is done, and it pushes one compressed data packet back to the site. This avoids failures on call volume, data size and backend latency.
Who maintains the Ignition application?
2Gi, the Ignition integrator, keeps developing and upgrading the application using Ignition scripting APIs built by Plantformance. Plantformance manages all data flows and the central middleware, and Saint-Gobain Glass and 2Gi decide when to roll out each factory.
Related Ignition case studies
- One laminated glass MES template instead of a custom version per plant
- One standard Ignition server for every Saint-Gobain factory
- Closing Ignition Vision security gaps across 3000+ Saint-Gobain apps
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.