EPISODE · Apr 18, 2026 · 25 MIN
Digital Transformation isn't a product
from Abelara Ascent · host Abelara
Summary Zack Scriven sits down for an impromptu conversation with Dylan DuFresne (Lead Architect & Co-founder, Abelara) on three of the industry's most-abused terms: "digital transformation," "unified namespace," and "Industry 4.0." Dylan's core argument is that the terms themselves are buzzwords — vessels that vendors fill with whatever they're trying to sell. The only useful question is what problem are you actually solving, and the only useful follow-up is what is this vendor actually selling me.The conversation moves from meta-critique into practical territory in the second half: Dylan walks through what a UNS has actually meant for the industry over the last decade (short answer: education), whether greenfield and brownfield sites need different answers (yes), and which tools he'd pick today if he were starting from scratch. It closes with one of the cleanest vendor-selection frameworks you'll hear on a podcast — and a discovery-call CTA for anyone who wants to talk through their own architecture.Three takeaways "Digital transformation" is whatever the vendor needs it to be to close the sale. The term has meant ERP-to-cloud migration, workflow digitization, knowledge-base digitization, and now unified namespace. The throughline isn't technical — it's commercial. If you're buying "digital transformation," demand to know what product or service is actually being delivered, and whether you have a problem it solves.UNS is a tool, not an answer. The real value of the UNS movement was education. Over ~10 years, the UNS conversation did something no one argued against: it educated the market on the need to connect ERP to plant floor, and share data across layers that never shared it. But "I want a UNS" is still the wrong starting question. Greenfield deserves a UNS-shaped architecture. Brownfield with working historians usually does not.Pick tools by problem, pick vendors by partnership. Dylan's ideal greenfield stack: Ignition, HiveMQ, Flow Software, Solace — some combination gets you most of what you need. Broker market has commoditized; the differentiation is adjacent features and culture. When two vendors solve the same problem, pick the one who wants to grow with you — not the one with the nicer salesperson.Chapters00:00 — Cold open + intro 00:32 — What "digital transformation" actually means (and who benefits from the ambiguity) 03:56 — Why digital transformation is change management, not a product 05:08 — Unified namespace: what it is, what it became, what it's worth 08:30 — Greenfield vs. brownfield — and the real value of UNS 14:56 — Who actually benefited from the UNS movement 17:27 — The stack Dylan would build today (+ CoreFlux deep dive) 19:24 — How to pick vendors when products overlap 24:41 — Discovery calls + weekly architecture Q&A
What this episode covers
Summary Zack Scriven sits down for an impromptu conversation with Dylan DuFresne (Lead Architect & Co-founder, Abelara) on three of the industry's most-abused terms: "digital transformation," "unified namespace," and "Industry 4.0." Dylan's core argument is that the terms themselves are buzzwords — vessels that vendors fill with whatever they're trying to sell. The only useful question is what problem are you actually solving, and the only useful follow-up is what is this vendor actually selling me.The conversation moves from meta-critique into practical territory in the second half: Dylan walks through what a UNS has actually meant for the industry over the last decade (short answer: education), whether greenfield and brownfield sites need different answers (yes), and which tools he'd pick today if he were starting from scratch. It closes with one of the cleanest vendor-selection frameworks you'll hear on a podcast — and a discovery-call CTA for anyone who wants to talk through their own architecture.Three takeaways "Digital transformation" is whatever the vendor needs it to be to close the sale. The term has meant ERP-to-cloud migration, workflow digitization, knowledge-base digitization, and now unified namespace. The throughline isn't technical — it's commercial. If you're buying "digital transformation," demand to know what product or service is actually being delivered, and whether you have a problem it solves.UNS is a tool, not an answer. The real value of the UNS movement was education. Over ~10 years, the UNS conversation did something no one argued against: it educated the market on the need to connect ERP to plant floor, and share data across layers that never shared it. But "I want a UNS" is still the wrong starting question. Greenfield deserves a UNS-shaped architecture. Brownfield with working historians usually does not.Pick tools by problem, pick vendors by partnership. Dylan's ideal greenfield stack: Ignition, HiveMQ, Flow Software, Solace — some combination gets you most of what you need. Broker market has commoditized; the differentiation is adjacent features and culture. When two vendors solve the same problem, pick the one who wants to grow with you — not the one with the nicer salesperson.Chapters00:00 — Cold open + intro 00:32 — What "digital transformation" actually means (and who benefits from the ambiguity) 03:56 — Why digital transformation is change management, not a product 05:08 — Unified namespace: what it is, what it became, what it's worth 08:30 — Greenfield vs. brownfield — and the real value of UNS 14:56 — Who actually benefited from the UNS movement 17:27 — The stack Dylan would build today (+ CoreFlux deep dive) 19:24 — How to pick vendors when products overlap 24:41 — Discovery calls + weekly architecture Q&A
NOW PLAYING
Digital Transformation isn't a product
No transcript for this episode yet
Similar Episodes
Jul 14, 2026 ·82m
Jul 13, 2026 ·99m
Jul 13, 2026 ·68m
Jul 7, 2026 ·64m
Jul 7, 2026 ·61m