Podcast · Tech & Cybersécurité
Ignited: Striking Industrial Automation Conversations
By Travis Cox, Chief Technology Evangelist at Inductive Automation
Chief Technology Evangelist at Inductive Automation, leading the conversation around enterprise industrial platforms and modern architecture adoption across manufacturing and industrial sectors.
⏱ 6 min read · Readable by ChatGPT, Gemini, Claude
Answers from this podcast
30 questions answered · 5 episodes indexed
Architecture First: Dylan DuFresne on Digital Infrastructure, UNS, and Building Transformation That Lasts
Dylan highlights that Ignition's user-first design and ease of use set it apart. He explains that with Ignition, when he wanted to accomplish something, the platform provided direct solutions without requiring workarounds or hacks.
Dylan emphasizes starting with root cause analysis and the five whys framework before any technical implementation. He stresses that digital transformation means different things to different people, and the first step is understanding what business outcome the organization actually wants—whether that is optimizing…
Dylan explains that most customers pursuing UNS are actually seeking vendor consolidation, as many organizations work with 40 to 50 vendors and need to reduce point-to-point integrations.
Dylan warns that the riskiest thing for a business is outsourcing ownership and accountability to external parties, even well-meaning integrators. He argues that if an organization cannot maintain its systems, it cannot own them, and without ownership it cannot hold anyone accountable.
Dylan explains that Abelera bridges strategy and execution by working with IT leadership to understand broader business objectives first—asking questions like where the business is going, what the North Star is, and what the organization is optimizing for.
Dylan states that successful engagements typically begin with a VP or Director of IT, sometimes a CTO or CIO, and requires a two-directional approach.
Batch processing in industrial manufacturing works like a baking analogy: you follow a recipe with known quantities and process steps to turn raw materials into end product with automated process controls and digital recordation.
With an open platform like Ignition, solution providers can pick and choose the best technologies to deliver robust solutions and expand capability over time.
ISA-88 is the gold standard for batch control and is a key standard that allows manufacturers to create standardized approaches. The approach uses standard control modules built in PLC logic that tie through standard interfaces into HMI components and historians.
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.
Tier board operations are a true data empowerment technology where PPG operates across tier basis one through five, with operations gathered around tier boards that execute meetings conducted at the same day, time, starting on time and ending on time with the same flow every time.
Polaris recognized that historically systems from the 90s and 2000s were not set up to support what manufacturers need in the current day and future. Historically the business model was transactional: clients create scope, companies bid, win projects, execute, then support.
Built for the Operator: Julio Velasco on Design, Education, and a Career Shaped by Ignition
Steve Heckman, an integrator at CalMetrics, was frustrated that software licensing costs—for clients, tags, screens, and historical data—consumed 80 percent of project costs, leaving integrators only 20-30 percent profit from their engineering hours.
A brownfield is an existing factory that has been built and operating for decades with mixed legacy equipment like PLC5, Siemens, Mitsubishi, and Omron controllers.
During economic expansions, companies invest in automation to grow plants and add new product lines. During economic downturns, they automate to eliminate the most expensive cost—labor—and reduce downtime.
Many facilities hire new operations managers who call integrators to bolt sensors on machines and add a display screen showing production counts, claiming this achieves Industry 4.0 while the underlying machines still run on PLC5s and micrologics.
Julio starts with a comprehensive audit of both physical hardware and software asset management on a scalable basis—whether one line, one area, or the entire facility.
Moving from RS-485 serial communication (DH45) to Ethernet requires adding network infrastructure like switches and IDFs, involving electricians and network specialists to run Ethernet drops to edge devices.
How 4IR Runs Cloud-First Industrial Infrastructure Across Hundreds of Sites
FactoryStack manages infrastructure through a central management plane containing declarative code, telemetry, alerting and monitoring, connected to deployment pipelines across customer tenants or 4IR-hosted endpoints.
4IR uses Ignition Edge, store-and-forward capabilities, and MQTT Sparkplug specifically because of its ability to handle store-and-forward, ensuring data is not lost when Internet connection, SD-WAN or other infrastructure between cloud and facility experiences outages or issues.
4IR uses Kubernetes as a declarative infrastructure-as-code system to deploy and manage Ignition environments at scale. Spinning up new services, databases, or gateways involves making code changes and pushing them to the environment, allowing the infrastructure-as-code tool to match the definition to the system.
4IR captures hundreds of thousands of data points from operated systems and uses synthetic probes to check externally whether applications respond on expected ports, allowing identification of whether problems are infrastructure-related or network-related.
4IR implements different security models for production versus development systems, granting appropriate access while maintaining sandbox environments that give developers connectivity they need without affecting production.
In the last year and a half, 4IR built a full on-premises Kubernetes-based high availability deployment capability designed to mimic cloud capabilities including composable architectures, multi-node high availability, automated deployment pipelines, and automated telemetry and observability, with nodes running…
The Factory Brain: Remus Pop on Connectivity, Knowledge Graphs, and the Next Era of Operational Intelligence
Factory Brain applies a knowledge graph on top of the unified namespace to create relationships between data points. While the UNS gave us an analytics engine to answer questions we know we need to ask, the Factory Brain starts to answer questions we didn't even know we need to ask, moving us from analytics to…
MCP essentially gives the ability of a platform or tool access into very detailed information from source systems. Instead of creating point-to-point API integrations, you can now point MCP directly into systems like Ignition to build dashboards through natural language.
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.
Ignition functions as the nervous system of the factory, not just a connectivity or visualization tool. It must be an engine of data that flows information into an endpoint that drives intelligence.
Remus Pop's team won a Firebrand Award with Ignition at Dana, where his job was to roll Ignition out to all 100+ factories. This extensive deployment across multiple facilities gave him deep insight into IT-OT convergence and identified a market gap where there were integration specialists who understood the shop…
A knowledge graph can become stale because it represents a point-in-time snapshot when it was built, and manufacturing environments change daily. However, when you create MCP interactions with systems like Ignition, the knowledge graph doesn't become stale anymore because you can constantly be aware of what's…
What Ignited covers
Ignited presents in-depth conversations with end users, system integrators, ecosystem partners, and thought leaders about how the Ignition platform, open standards, and modern architectures solve tangible problems in industrial automation. The podcast moves beyond marketing claims to explore real deployments across every vertical—from batch manufacturing to cloud-scale edge autonomy—revealing the operational intelligence and connectivity frameworks that enable modern enterprises to integrate systems without proprietary constraints. Each episode demonstrates how platform foundations enable rapid application development, workforce preparation, and interoperability initiatives that reshape industrial practice.
Key facts
- Ignition platform connects data across enterprises and scales universal industrial applications without vendor lock-in constraints.
- Open standards and unified namespace protocols eliminate technical gridlock between legacy and modern systems in manufacturing environments.
- Operator-focused design and structured education programs are essential for successful adoption of modern industrial platforms across distributed teams.
- Cloud-first infrastructure and edge autonomy architectures enable organizations to manage hundreds of sites with consistent operational intelligence.
Explore all episodes of Ignited and hear from industry leaders shaping the future of industrial automation.
What this podcast really covers
Ignited bridges the gap between platform technology and real-world operational transformation. Rather than abstract discussions, each episode grounds itself in specific challenges: how connectivity frameworks move data reliably across enterprise systems, how knowledge graphs organize operational intelligence for faster decision-making, how batch manufacturing systems enforce compliance while scaling flexibility, and how cloud-first architectures manage distributed edge autonomy without sacrificing control. The podcast examines the infrastructure decisions that separate theory from practice—unified namespace protocols, interoperability standards, and architectural choices that either enable or constrain an organization's ability to build and adapt applications rapidly. Conversations reveal the technical debt and integration patterns that integrators encounter, the design principles that make platforms approachable for operators, and the educational frameworks organizations need to sustain adoption beyond initial deployment.
Who this podcast is essential for
Operations leaders evaluating next-generation platforms find actionable intelligence in how peer organizations have restructured automation stacks around open standards. System integrators discover patterns in how to architect solutions that scale across multiple clients without rebuilding custom logic for each deployment—and how unified protocols reduce both technical risk and project cost. Engineers designing industrial applications benefit from hearing experienced practitioners discuss trade-offs in real-time: when to prioritize cloud connectivity versus edge resilience, how to balance operator usability with advanced analytics, and which architectural decisions compound or resolve long-term maintenance challenges. Technology evangelists and architects gain perspective on emerging standards like MCP (Model Context Protocol) and CESMII frameworks, preparing teams for the next wave of automation infrastructure evolution.
What the episodes really reveal
Across episode titles—from "The Factory Brain" examining knowledge graphs to "Breaking the Gridlock" analyzing edge autonomy and "Built for the Operator" focusing on usability—a consistent narrative emerges: industrial automation is shifting from siloed, vendor-locked systems toward integrated, standards-based platforms. Episodes reveal that connectivity and data unification are now foundational requirements, not competitive advantages. Knowledge graph approaches transform raw operational data into decision-ready intelligence. Batch execution frameworks succeed when they balance strict compliance with operational flexibility. Cloud-first infrastructure proves viable at scale when edge autonomy is carefully architected. Workforce preparation determines adoption success more reliably than technical specification. Interoperability is no longer aspirational—organizations implementing CESMII principles and open protocols report faster deployment, lower switching costs, and more adaptive operations teams.
What this changes in practice
Organizations listening to Ignited discover that platform selection now hinges on openness, scalability, and operator alignment rather than feature breadth alone. Teams learn that unified namespace implementations require serious architectural investment but unlock integration flexibility that proprietary approaches cannot match. Integrators recognize that standardized approaches to batch manufacturing, cloud integration, and edge deployment reduce custom development and create repeatable solutions across verticals. Operations and engineering teams understand that modern platforms require operator-centric design and structured career development programs—not just technical training—to achieve sustained adoption and innovation. The podcast demonstrates that the true competitive advantage lies not in the platform itself but in how effectively an organization orchestrates connectivity, intelligence, and human capability around that foundation.
Industrial automation's future depends not on choosing between legacy and modern systems, but on building integration layers that treat data, standards, and operator capability as core architectural concerns—enabling enterprises to evolve without wholesale replacement.
Listen to Ignited to understand how leading organizations are restructuring automation around open platforms.
Start listening to Ignited now and discover how modern architectures solve real industrial challenges.
The podcast answers these questions
What is Ignition and how does it function as an enterprise platform?
Ignition is a universal industrial platform that connects data across enterprises, enables rapid development of industrial applications, and scales without limits. It serves as a foundation for enterprise integration that supports modern architectures and open standards across all verticals.
How do system integrators use modern platforms to solve manufacturing challenges?
System integrators leverage open platforms and modern architectures to address real operational problems including batch execution, connectivity, knowledge graph implementation, and edge autonomy. This approach eliminates proprietary constraints and enables organizations to build scalable solutions across multiple sites and business models.
What role does interoperability play in industrial automation today?
Interoperability is critical for smart manufacturing adoption. Open standards, unified namespace protocols, and cloud-first infrastructure allow organizations to integrate systems seamlessly across hundreds of sites, reduce technical gridlock, and empower operations teams to build sustainable solutions without vendor lock-in.
How can organizations prepare their workforce for modern industrial platforms?
Organizations must prioritize operator-focused design and technical education. Platforms that are built around operator needs, combined with structured learning paths and career development aligned to modern architectures, enable teams to adopt new tools effectively and sustain long-term operational excellence.
Discover Ignited: Striking Industrial Automation Conversations
Travis Cox · Inductive Automation
Listen to the podcast