Why should manufacturers build data infrastructure first rather than committing to specific AI platforms and tools?
Answered at 18:09 in The Factory Brain: Remus Pop on Connectivity, Knowledge Graphs, and the Next Era of Operational Intelligence · Ignited: Striking Industrial Automation Conversations
Why should manufacturers build data infrastructure first rather than committing to specific AI platforms and tools?
The software landscape is being completely transformed by AI, and new foundational models from companies like Anthropic, OpenAI, or Google can kill 500 different SaaS offerings overnight. By abstracting the platform away from infrastructure, manufacturers protect their investment and avoid situations where they invested time and money in a pilot only to have a new model emerge that makes their entire investment a complete waste. The approach is to plug data into infrastructure, not into applications.
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
The software landscape is being completely transformed by AI, and new foundational models from companies like Anthropic, OpenAI, or Google can kill 500 different SaaS offerings overnight.
Remus Pop, Driving force behind Concept Reply's industrial AI practice at Concept Reply · The Factory Brain: Remus Pop on Connectivity, Knowledge Graphs, and the Next Era of Operational Intelligence · Ignited: Striking Industrial Automation Conversations · answer at 18:09
Key takeaways
- The software landscape is being completely transformed by AI, and new foundational models from companies like Anthropic, OpenAI, or Google can kill 500 different SaaS offerings overnight.
Quote to remember
“What the brain starts to do is it starts to answer the questions that we didn't even know we need to ask. It moves us from analytics to intelligence.”
— Remus Pop
The full answer · about 3 min
The software landscape is being completely transformed by AI, and new foundational models from companies like Anthropic, OpenAI, or Google can kill 500 different SaaS offerings overnight. By abstracting the platform away from infrastructure, manufacturers protect their investment and avoid situations where they invested time and money in a pilot only to have a new model emerge that makes their entire investment a complete waste. The approach is to plug data into infrastructure, not into applications.
Key facts
- Remus Pop spent eight years as a controls engineer launching automotive assembly lines throughout the Detroit area
- He deployed Ignition for 12 years without ever deploying it as a SCADA system
- He spent two years living in China deploying an MES system in 2014-2016
- Dana deployment rolled Ignition out to 100+ factories
- Remus Pop attended 18 days of consecutive Ignition training in Folsom (Ignition boot camp, ICC, and MES training combined)
People, companies and topics mentioned
More answers from this episode
- 3:24What was Remus Pop's experience deploying Ignition across Dana's manufacturing footprint?
- 5:54What is Factory Brain and how does it differ from traditional unified namespace implementations in manufacturing?
- 12:30How does the concept of the nervous system apply to Ignition in factory automation architecture?
- 17:36How does knowledge graph prevent staleness and maintain real-time relationships in manufacturing systems?
- 20:34How does the Model Context Protocol enable AI agents to automate manufacturing operations beyond predictive alerts?