The Ignition Reference Architecture for Modern Manufacturing with Dylan DuFresne

Dylan DuFresne walks through Abelara’s reference architecture for modern industrial systems — from edge controllers through Ignition’s tag gateway pattern, UNS publishing, historian integration with Timebase, Flow Software for contextualization, and enterprise-scale deployment with HiveMQ cloud bridging and Fuuz as an MES layer. The episode covers how to phase these components in with zero technical debt and how Abelara helps enterprises cut through analysis paralysis.About the GuestDylan DuFresne is an architect at Abelara specializing in Ignition, MQTT / Unified Namespace, and enterprise data systems.Key Topics CoveredTag gateway pattern: separating tag providers from front-end / back-end DevOpsIgnition 8.3 improvements and Gateway Area Network updatesHistorian integration: Timebase direct from tag gateway vs collectorsFlow Software for contextualization, KPIs, and bidirectional flowBlue namespace vs red namespace: site flexibility vs enterprise standardsHiveMQ cloud bridging to Snowflake, BigQuery, AzureFuuz as an MES layer replacing ETL between ERP and site systemsPhased implementation: SCADA → UNS → historian → analytics → AIKey TakeawaysUse a dedicated tag gateway so front-end and back-end systems can run DevOps cycles without risking production tag state.Standards should get stricter as you move up the stack — fluid near controllers, rigid near ERP.Build additively with zero technical debt: SCADA, then UNS, historian, analytics, AI.Timestamps[00:00] Tag gateway pattern[02:42] Timebase historian[04:01] Flow Software[07:45] HiveMQ + cloud data lakes[13:04] Fuuz as enterprise MES[15:06] Zero technical debt roadmap[17:50] Abelara workshopsLinksAbelara: https://abelara.comIgnition: https://inductiveautomation.comFlow Software: https://flowsoftware.comTimebase: https://timebased.ioHiveMQ: https://hivemq.comFuuz: https://fuuz.comLitmus: https://litmus.ioAxilon: https://axilon.com