How did Polaris Automation help PPG Industries move away from Excel-based scheduling?
Answered at 23:26 in Batch, Built Right: How Open Platforms Are Rewriting the Rules of Manufacturing Execution · Ignited: Striking Industrial Automation Conversations
How did Polaris Automation help PPG Industries move away from Excel-based scheduling?
Polaris built a Core Data scheduling module within Ignition that replicated the same functionality as PPG's Excel-based scheduling that was fed from their ERP exports. After iteratively adding more capability as requested, PPG officially went off Excel completely two weeks before the podcast was recorded and now utilizes the scheduler purely within the platform. This transformation took approximately five years in the making with a cross-functional team approach.
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
Polaris built a Core Data scheduling module within Ignition that replicated the same functionality as PPG's Excel-based scheduling that was fed from their ERP exports.
Scott Cook, Chairman and CEO at Polaris Automation · Batch, Built Right: How Open Platforms Are Rewriting the Rules of Manufacturing Execution · Ignited: Striking Industrial Automation Conversations · answer at 23:26
Key takeaways
- Polaris built a Core Data scheduling module within Ignition that replicated the same functionality as PPG's Excel-based scheduling that was fed from their ERP exports.
Quote to remember
“Proprietary systems create proprietary data silos. We want to make sure that the information created from our batch system gets published into a standard format so that people can act on issues quicker in real time.”
— Scott Cook
The full answer · about 1 min
Polaris built a Core Data scheduling module within Ignition that replicated the same functionality as PPG's Excel-based scheduling that was fed from their ERP exports. After iteratively adding more capability as requested, PPG officially went off Excel completely two weeks before the podcast was recorded and now utilizes the scheduler purely within the platform. This transformation took approximately five years in the making with a cross-functional team approach.
Key facts
- Polaris Automation founded in 1984 by Scott Cook's father
- Scott Cook started with the business in 1987
- 2019: Polaris Automation transitioned to ESOP (employee-owned organization)
- Mark Marino spent 26 years doing batch control systems and MES applications for construction materials industry before joining Polaris
- Mark Marino has been with Polaris for 10 years
People, companies and topics mentioned
More answers from this episode
- 5:28What is batch processing in manufacturing and why is getting it wrong so costly?
- 7:23How does an open platform approach built on Ignition differ from proprietary batch and MES systems?
- 8:52Why did Polaris Automation transition from project-based transactional relationships to long-term strategic partnerships with manufacturers?
- 17:43What is ISA-88 and how does it apply to batch control systems?
- 24:23What is the tier board operations approach and how does PPG use it for Kaizen?