Who should be the primary stakeholders when designing digital infrastructure for manufacturers?
Answered at 21:00 in Architecture First: Dylan DuFresne on Digital Infrastructure, UNS, and Building Transformation That Lasts · Ignited: Striking Industrial Automation Conversations
Who should be the primary stakeholders when designing digital infrastructure for manufacturers?
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. Rather than a purely top-down approach from IT or bottom-up from the plant floor, Dylan maintains that neither works at scale and a combination of both, meeting in the middle, is necessary. Starting from the IT director level, Abelera then extends conversations upward to the CEO, CFO, CTO, and Director of HR to understand full business strategy, and also coordinates with plant-floor operations teams to understand practical constraints and capabilities.
Full answer and detailsRead the whole answer, key facts and every other question from this episode
In short
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.
Dylan DuFresne, Co-founder and Chief Architect at Abelera · Architecture First: Dylan DuFresne on Digital Infrastructure, UNS, and Building Transformation That Lasts · Ignited: Striking Industrial Automation Conversations · answer at 21:00
Key takeaways
- 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.
Quote to remember
“The riskiest thing you can do right now for your business is to outsource ownership and outsource accountability.”
— Dylan DuFresne
The full answer · about 1 min
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. Rather than a purely top-down approach from IT or bottom-up from the plant floor, Dylan maintains that neither works at scale and a combination of both, meeting in the middle, is necessary. Starting from the IT director level, Abelera then extends conversations upward to the CEO, CFO, CTO, and Director of HR to understand full business strategy, and also coordinates with plant-floor operations teams to understand practical constraints and capabilities.
Key facts
- Dylan started learning Ignition around 2014 in a dog food plant feed-side project
- Dylan spent approximately 8-9 years at an electrical contractor integrator before co-founding Abelera
- Abelera has worked on Ignition systems with a million-plus tags on a single gateway, from which they learned to use multiple gateways
- Many organizations Abelera works with manage 40-50 vendors, creating significant management complexity
- Organizations pursuing UNS consolidation often have 50-100 platforms that are too decentralized or 1-2 platforms that are overly centralized
People, companies and topics mentioned
More answers from this episode
- 5:05What makes Ignition unique compared to other SCADA and HMI platforms in industrial automation?
- 7:00What is Abelera's philosophy for bridging IT strategy and OT execution in manufacturing?
- 10:30How should manufacturers approach digital transformation instead of chasing buzzwords like Industry 4.0 and UNS?
- 12:20What is Abelera's unique approach to Unified Namespace (UNS) implementation in manufacturing?
- 17:05Why is stepwise modernization and internal ownership better than full rip-and-replace digital transformation?