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 Guest

Dylan DuFresne is an architect at Abelara specializing in Ignition, MQTT / Unified Namespace, and enterprise data systems.

Key Topics Covered

• Tag gateway pattern: separating tag providers from front-end / back-end DevOps
• Ignition 8.3 improvements and Gateway Area Network updates
• Historian integration: Timebase direct from tag gateway vs collectors
• Flow Software for contextualization, KPIs, and bidirectional flow
• Blue namespace vs red namespace: site flexibility vs enterprise standards
• HiveMQ cloud bridging to Snowflake, BigQuery, Azure
• Fuuz as an MES layer replacing ETL between ERP and site systems
• Phased implementation: SCADA → UNS → historian → analytics → AI

Key Takeaways

• Use 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 workshops

Links

Abelara: https://abelara.com
Ignition: https://inductiveautomation.com
Flow Software: https://flowsoftware.com
Timebase: https://timebased.io
HiveMQ: https://hivemq.com
Fuuz: https://fuuz.com
Litmus: https://litmus.io
Axilon: https://axilon.com