EnergyTech Podcast

Energy Innovation meets Industrial Technology: There is finally a podcast that balances technical depth with real-world applicability for field teams, operations groups, and senior leaders who want to see a real return on technology , IiOT, and AI Investments

Listen on:

  • Apple Podcasts
  • Podbean App
  • Spotify

Episodes

5 hours ago

In Episode 5 of the Energy Tech Podcast Control Room Management (CRM) mini-series, Mike Flores and Daniel Nieto (VP of Regulatory & Compliance at OpSite Energy) break down one of the most overlooked requirements in PHMSA Control Room Management regulations — providing controllers with adequate information and tools.Many operators assume this requirement only refers to SCADA screens, but the reality is much broader. Adequate information includes HMI displays, procedures, safety-related points, alarm identification, maps, contact lists, and operational tools that controllers rely on to safely operate a pipeline.In this episode we discuss:• What adequate information and tools means under 49 CFR 192 & 195 Control Room Management rules• How auditors evaluate Section C compliance during inspections• Why safety-related points must be clearly identified in SCADA and procedures• Common gaps operators face (outdated procedures, missing valve visibility, information overload)• Real-world audit scenarios where missing data becomes a contributing factor to incidents• Practical steps control room leaders can take to improve compliance and operational safetyDaniel also shares lessons learned from dozens of PHMSA CRM audits, explaining what inspectors typically look for during control room observations.If you manage or work in a pipeline control room, SCADA environment, or regulatory compliance role, this episode will help you better understand how to ensure controllers have the tools they need to safely operate pipeline systems.This episode is part of the Energy Tech Podcast CRM Mini-Series, presented by OpSite Energy from the OpSite Energy Control Center in Canonsburg, Pennsylvania.📩 Have a control room scenario or question?Drop it in the comments or contact us at info@opsiteenergy.com👍 Like, Subscribe, and Share with another control room operator or compliance professional.00:00 – Introduction to CRM Episode 500:55 – What “Adequate Information & Tools” Means in Control Rooms02:15 – PHMSA CRM Regulatory Context (49 CFR 192 & 195)04:30 – Why Adequate Information Is Critical for Pipeline Safety06:30 – The Three Pillars of Adequate Information09:00 – Understanding Safety-Related Points in SCADA12:00 – Real-World Examples from Control Room Audits15:15 – Leak Detection and Data Reliability18:00 – What Inspectors Look for During CRM Inspections21:10 – Real Scenario: Missing Valve Status on SCADA25:10 – Contributing Factors vs Human Error28:10 – Common Control Room Gaps Operators Face31:30 – Information Overload in SCADA Displays34:00 – Implementation Framework for Operators37:20 – Mapping Controller Tasks and Tools40:00 – Documenting Safety Related Points42:10 – Misconceptions About CRM Compliance44:30 – Does Adequate Information Look the Same for Everyone?47:00 – Backup Control Rooms and System Differences49:30 – Top 3 Action Items for Control Room Leaders52:00 – Episode Summary53:20 – Preview of Episode 6 (SCADA & HMI Displays)

5 hours ago

In this episode of the Energy Tech Podcast, recorded live at ENTELEC 2026, we sit down with William Behn from Neeve to break down one of the most important shifts happening in industrial tech:👉 The collapse of the traditional OT architecture — and the rise of Industrial SASE.As IT/OT convergence accelerates, legacy models like Purdue are being challenged by modern needs for data mobility, security, and scalability.We dive into:Why 30 years of OT architecture is being torn downThe reality of IT vs OT convergence (it’s cultural, not technical)What Industrial SASE actually means for oil & gas and manufacturingHow to eliminate network sprawl (VPNs, jump boxes, unmanaged switches)The role of Unified Namespace (UNS) + MQTTWhy data needs to move freely — but securelyHow edge computing + zero trust are reshaping industrial systemsThe impact of AI agents on OT infrastructureThis is a must-watch for leaders trying to modernize operations without compromising security.🎧 If you're building the future of control rooms, SCADA, or industrial data platforms — this episode will change how you think.⏱️ Chapters00:00 – Intro: Live from ENTELEC 202600:40 – Meet William Behn (Neeve)01:30 – First Impressions of ENTELEC02:30 – The “Cyber Problem, No Solutions” Reality04:00 – Why Cybersecurity Feels Like “Vanilla Advice”05:30 – IT vs OT Convergence: What’s Really Happening06:30 – Cultural Shift Between IT and OT07:30 – The Pilot Analogy (C5 vs F16) Explained09:00 – OT = Availability, IT = Security10:30 – The Problem with IT Tools in OT11:30 – The End of OT “Sprawl” Architecture12:30 – Why Purdue Model Is Losing Its Grip13:30 – Introduction to Industrial SASE15:00 – How Enterprise IT Solved This 15 Years Ago16:00 – Bringing SASE to OT17:00 – UNS + SASE: How They Work Together18:00 – Data Flow: Edge → Broker → Business19:00 – Multi-Cloud, Security & Flexibility20:30 – Containerization & Edge Compute21:30 – Zero Trust (Including AI Agents)22:30 – Future-Proofing Industrial Systems24:00 – The “Tearing Down 30 Years” Moment25:00 – Outro & Final ThoughtsPresented by Opsite Energy: www.opsitenergy.comMusic: Uygar Duzgun / “Fast Life” courtesy of www.epidemicsound.com

5 days ago

In this episode of the Energy Tech Podcast, recorded live at ENTELEC 2026, we sit down with Dale Peterson, founder of S4 Events and one of the pioneers in ICS and SCADA cybersecurity.With over 25 years in industrial cybersecurity, Dale breaks down a hard truth:👉 Most OT systems are still insecure by design.We dive into:Why 80%+ of industrial systems remain vulnerableThe concept of “insecure by design” protocolsWhy OT cybersecurity progress has been so slowThe real meaning of risk vs cyber hygieneHow to think about AI, cloud, and security in OT environmentsWhy “doing everything” in cybersecurity often does nothingHow to prioritize real risk reduction over checklistsThis conversation challenges conventional thinking and gives operators, engineers, and leaders a practical framework for securing industrial environments.🎧 If you're responsible for SCADA, OT, or critical infrastructure — this is a must-watch.⏱️ Chapters00:00 – Intro: Live from ENTELEC 202600:40 – Meet Dale Peterson (S4 Events)01:10 – How Dale Got Into ICS Cybersecurity (By Accident)02:00 – The Origin of S4 Events & Building the ICS Security Community03:00 – The “Cyber Poor” Problem in OT04:00 – Why OT Cybersecurity Still Lags Behind05:20 – “Insecure by Design” Systems Explained06:30 – Why Nothing Has Changed (Yet)07:00 – What Will Finally Drive Change in OT Security08:30 – Keynote Breakdown: Connect, Consider, Consequence09:00 – AI & Connectivity: New Risks Emerging09:30 – Why Security Leaders Must PRIORITIZE (Not Do Everything)10:00 – Rethinking Risk: Reducing Consequences vs Preventing Attacks11:00 – Why CISOs Can’t Just Say “No” Anymore12:00 – The Reality of Limited Resources in OT13:00 – Why “Cyber Hygiene” Doesn’t Always Reduce Risk14:00 – What Actually Moves the Risk Needle15:30 – Purdue Model vs Unified Namespace Debate17:00 – AI in OT: Security vs Value18:30 – Protecting Data in the Age of AI20:00 – Real-World Example: Remote Control Risks in OT21:30 – Risk Management vs Blind Trust23:00 – Where to Find Dale & Closing ThoughtsPresented by Opsite Energy: www.opsitenergy.comMusic: Uygar Duzgun / “Fast Life” courtesy of www.epidemicsound.com

Monday Apr 13, 2026

In this episode of the Energy Tech Podcast, recorded live at ENTELEC 2026 in Galveston, we sit down with Lindi Sabloff, Founder & CEO, to discuss the reality of AI adoption in industrial sectors like oil & gas and manufacturing.While AI dominates headlines, Lindi breaks down a critical truth: most industrial companies are not ready for AI yet.We dive deep into:Why data quality and infrastructure must come before AIThe importance of edge computing vs cloud-first strategiesHow to empower OT teams instead of replacing themThe real challenges of digital transformation in brownfield environmentsWhy people—not technology—are the hardest part of transformationThis conversation is a must-watch for operators, engineers, and executives navigating the intersection of AI, SCADA, and industrial data strategy.👉 If you're responsible for operations, automation, or digital transformation — this episode will challenge how you think about AI readiness.🎧 Listen now and learn how to build the foundation before chasing AI hype.⏱️ Chapters00:00 – Intro: Live from ENTELEC 202600:40 – Meet Lindi Sabloff: From Wall Street to Industrial Tech02:30 – The “Aha Moment” That Changed Everything04:30 – Why Technology Must Fit People (Not the Other Way Around)05:30 – The Truth About AI Replacing Jobs06:30 – OT Workforce Challenges & Attrition07:30 – Why Industrial Companies Aren’t Ready for AI08:30 – Data Quality: The Biggest Problem in the Industry10:00 – Edge vs Cloud: Where AI Should Actually Live11:00 – The “6 Week AI” Myth (And Why It’s Wrong)12:30 – Data Lineage & Semantic Layers Explained14:00 – M&A, Data Standardization, and Scaling Operations15:00 – The People Problem in Digital Transformation17:00 – Brownfield Reality: Why You Can’t “Rip & Replace”19:00 – Real-Time vs Time-Series Data Strategy21:00 – Leadership, Mindset, and Building Technology Companies23:00 – Marrying Business Outcomes with Technology25:00 – How Lindi’s Company Delivers Value to OT Teams27:00 – Remote Operations, Fleet Updates & Cost Savings29:00 – Cybersecurity, Patch Management & OT Control30:30 – Edge Devices, Security Risks, and Future-Proofing31:30 – AI in the Next 1–2 Years: What Happens Next32:15 – Outro & Final ThoughtsPresented by Opsite Energy: www.opsitenergy.comMusic: Uygar Duzgun / “Fast Life” courtesy of www.epidemicsound.com

Tuesday Mar 31, 2026

In this episode of the Energy Tech Podcast, we sit down with Avadine to explore Ignition-native Pump-Off Control (IPO) — a modern approach to well optimization built on the Ignition SCADA platform.We dive into how IPO is transforming traditional pump-off control systems by eliminating data silos, reducing costs, and enabling real-time optimization across thousands of wells.This episode also explores how AI is being applied to dynamometer card analysis, helping operators identify issues, improve production, and reduce LOE without relying on expensive legacy systems.From field operations to enterprise data strategies, this conversation highlights what it really means to be AI-ready in oil & gas.Key Topics Covered:Ignition-based pump-off control (IPO)Replacing legacy SCADA and paywall systemsAI-driven dynamometer card analysisData ownership, UNS, and AI readinessRemote well control and optimizationReducing LOE and improving production efficiencyIf you're a production engineer, SCADA developer, or operations leader — this is a must-watch.👉 Learn how to modernize your well optimization strategy👉 Subscribe for more SCADA, OT, and control room insights00:00 – Introduction & Guest Overview01:30 – What is Avdine & IPO?04:30 – From Field Operator to SCADA Architect07:00 – Why Legacy SCADA Systems Are Failing10:00 – The Pump-Off Control Problem in Oil & Gas12:00 – Why IPO is Built on Ignition14:00 – Breaking Data Silos in Well Optimization16:00 – Legacy Platforms vs Modern SCADA18:00 – IPO Demo Overview24:00 – Protocols: Modbus, OPC, MQTT Explained27:30 – Real-Time Well Monitoring & Control29:30 – Dynamometer Cards in Ignition32:00 – AI for Card Analysis & Optimization35:00 – AI Recommendations in Action38:00 – AI in Oil & Gas: Hype vs Reality40:00 – Data Architecture: UDTs, JSON & AI Readiness43:00 – Zero-ETL & Enterprise Integration45:00 – Remote Control, Setpoints & Configuration47:00 – Disaster Recovery & Configuration Tracking49:00 – AI for Production Optimization50:30 – Reducing LOE & Increasing Runtime52:00 – How to Get Started (Pilot Strategy)54:30 – Final Thoughts & Call to Action

Monday Mar 16, 2026

In Episode 4 of the Energy Tech Podcast Control Room Management (CRM) mini-series, Mike Flores and Daniel Nieto (VP Regulatory & Compliance at OpSite Energy) break down one of the most misunderstood topics in pipeline operations:Authority to Supersede.Can a manager override a pipeline controller during an abnormal event?What does the PHMSA Control Room Management rule (49 CFR 192.631 & 195.446) actually require?And how should operators structure procedures to remain compliant during audits?In this episode we explain the regulatory intent behind superseding, common misconceptions, and how pipeline operators should document and train controllers so they can safely maintain operational authority during abnormal or emergency conditions.If you operate, manage, or audit a pipeline control room, this episode walks through real-world scenarios, compliance expectations, and cultural practices that inspectors look for during CRM audits.Topics covered include:• PHMSA CRM authority requirements (192.631 & 195.446)• Why non-qualified personnel cannot override controllers• Typical superseding scenarios in control rooms• Procedures pipeline operators should implement• How inspectors evaluate CRM compliance• Lessons learned and operational culture in pipeline control roomsThis discussion is part of the Energy Tech Podcast CRM Mini-Series, where we break down the practical side of pipeline control room compliance and operations.📍 Recorded at the OpSite Energy Control Center in Canonsburg, Pennsylvania00:00 Introduction to the CRM Mini-Series00:45 Why Control Room Operators Have Technical Authority02:10 PHMSA CRM Rule Overview (192.631 & 195.446)04:10 Qualified Controllers vs Non-Qualified Personnel06:30 What “Authority to Supersede” Actually Means09:10 Real-World Control Room Scenario (Manager Override Example)13:20 Why Superseding Creates Safety Risks16:00 Required Procedures for CRM Compliance19:30 Four-Step Framework for Control Room Authority23:10 Common Misconceptions About Superseding26:20 What Happens if the Controller Is Wrong?29:00 How PHMSA Inspectors Test CRM Compliance32:30 Culture vs Documentation in Control Room Management35:10 Three Action Items for Control Room Operators37:10 Key Takeaways on Authority to Supersede

Monday Mar 09, 2026

The Energy Tech Podcast will be live at ENTELEC 2026 in Galveston, Texas at the Galveston Island Convention Center from April 6–9 — and in this episode we break down what to expect from one of the most important conferences in industrial networking, SCADA, and operational technology (OT).Hosted by Jeff Perry and Mike Flores from OpSite Energy, this episode previews the major technical themes expected at the conference, including:- Private LTE & Private 5G networks- Industrial wireless infrastructure- Edge computing and AI at the industrial edge- Unified Namespace (UNS) and MQTT- OT cybersecurity and secure remote access- Industrial IoT sensors and field automation- Digital twins and modern SCADA architecturesWe also explain how Energy Tech Podcast will be recording live interviews at ENTELEC, inviting vendors, operators, and technology leaders to join us for 15–30 minute podcast segments directly from the conference floor.If you’re attending ENTELEC, stop by and share your insights from the conference.📍 Event: ENTELEC 2026📍 Location: Galveston Island Convention Center📅 Dates: April 6–9, 2026Topics covered throughout the week will include:- Industrial private networking architecture- OT security frameworks and remote access- Edge AI and field automation- Industrial data platforms and digital transformation- SCADA modernization- Industrial IoT deployments in energy and critical infrastructure🎙️ The Energy Tech Podcast, presented by OpSite Energy, explores the technologies shaping the future of industrial operations, automation, and energy infrastructure.If you’re attending ENTELEC and want to join the podcast, we’ll be recording episodes throughout the conference.

Monday Mar 02, 2026

Welcome to Episode 3 of the Energy Tech Podcast’s Control Room Management (CRM) mini-series. Mike Flores and Daniel Nieto (Regulatory Compliance, OpSite Energy) cover what they call the lynchpin of control room management: shift change and handover.If information gets lost during turnover, pipeline safety suffers. In this episode, we break down how to build a formal handover procedure (guided by API Recommended Practice 1168) that protects operational continuity—whether you’re a PHMSA-regulated pipeline control room or a production/PSM control room applying best practices.You’ll learn what auditors expect to see: console coverage, shift overlap, clear accountability, and documentation that shows what was reviewed—especially during unscheduled handovers (breaks, training, drug tests, or fit-for-duty changes). We also cover why shift change must pause when urgent actions/commands hit the console so nothing gets “half-transferred.”00:00 – Episode 3 intro: shift change & handover00:24 – Why handover is the lynchpin of CRM01:07 – Episode overview + API RP 1168 industry guidance02:04 – Value even for non-regulated control rooms02:53 – Audit reality: human factor + preventing lost info03:44 – Console coverage & shift overlap: what auditors expect04:18 – Shift change procedure: accountability + no interruptions04:58 – Pause handover when an urgent action/command occurs05:21 – Shift change triggers beyond “end of shift”05:33 – Unplanned triggers: breaks, training, drug tests, deviations06:35 – Why overlap time exists + where the briefing happens (at console)07:48 – Accountability documentation: what auditors actually check08:19 – Audit focus: procedure-driven content, time, and reviewed material09:11 – What must be covered: AOCCs, maintenance, alarms, equipment status09:40 – Top handover categories: unresolved events, comms issues, procedural changes10:31 – Unattended console: short breaks and temporary step-away rules11:24 – Fit-for-duty/unplanned transfers: sick, emergency, no-show scenarios13:22 – Do not hand over mid-command: verify actions are complete14:35 – Compliance checklist recap: must-have handover elements16:40 – Common audit failures: wrong personnel, missing pending events18:55 – Actionable takeaways: formalize logs, drill unscheduled, check the list19:45 – Auditors want proof, not “checkboxes”20:44 – Audit trail: triggers, logins/logouts, timestamps21:14 – Closeout + Episode 4 preview (adequate information / Section C)✅ Next up (Episode 4): Fatigue MitigationPresented by Opsite Energy: www.opsitenergy.comMusic: Uygar Duzgun / “Fast Life” courtesy of www.epidemicsound.com

Monday Feb 23, 2026

Industrial automation can’t be run like it’s 2014. In this episode of the Energy Tech Podcast (presented by OpSite Energy), Jeff and Mike sit down with Bill Bane and Jerry Reeves from Neeve to explain why “the box” mindset is holding OT back and why a managed, continuously updated OT ecosystem is the path forward.We cover:- Why OT needs to move past static hardware and rip/replace cycles- “Ecosystem” thinking: compute, connections, apps, remote access — working together- Continuous updates for cyber and operations (not just security patches)- How this model benefits end users, systems integrators, and MSPs-The reality of service + support in critical infrastructure environments- Where to meet the team at ENTELEC 2026 (Galveston, April 6–9)If you’re operating or supporting critical infrastructure (oil & gas, midstream, water/wastewater, manufacturing, building automation, airports, data centers), this episode is for you.CTA: Like, subscribe, and drop your OT/cyber questions in the comments.0:00 Intro + Guests (Bill Bane, Jerry Reeves)0:54 Why we’re “stuck in the box” thinking2:06 Platform mindset: Roku analogy + “ecosystem” framing3:24 Managed platform: always refreshed, always alive5:51 Cyber + operational updates: threat vectors + software evolution8:17 Breaking the capex-only mentality (dynamic infrastructure)10:13 Why updates make it “a different box”13:05 CFO conversation: capex vs recurring + staying dynamic14:03 Big win for service providers, SIs, and MSPs16:25 Brand advantages: inheriting SOC2 readiness + zero trust posture17:01 “Setup made simple” + plug-in deployment19:07 Real support from real people (critical infrastructure mandate)24:35 ENTELEC 2026 shoutout + dates (Galveston, Apr 6–9)26:18 Trial offer + “unbox vs get out of the box”27:00 WrapMusic: Uygar Duzgun / “Fast Life” / courtesy of www.epidemicsound.com

Monday Feb 16, 2026

Welcome to Episode 2 of the Energy Tech Podcast’s Control Room Management (CRM) mini-series. In this episode, Mike Flores and Daniel Nieto (VP Regulatory, OpSite Energy) focus on one core objective:Eliminate confusion in the control room.PHMSA expects roles, authority, and responsibilities to be explicit—especially during abnormal operating conditions (AOCCs) and emergencies. This episode breaks down how strong written procedures and training create controller confidence, faster response, and safer pipeline operations.In this episode, you’ll learn:- Why PHMSA cares about roles + authority clarity (and where confusion shows up)- How written procedures must cover normal, abnormal, and emergency operations- What “controller authority” really means (span of control, shutdown limits, escalation paths)- Why operators get cited when they fail to explicitly grant independent shutdown authority - The controller’s physical domain of responsibility: maps, drawings, system knowledge, and asset coverage- Maintaining continuous pressure limit awareness: MAOP vs MOP, setpoints, and visibility- What auditors verify: access to procedures, MAOP/MOP, regulated segments, alarm/setpoint awareness- Handling the unexpected: SCADA/communications failures, unplanned events, and control room evacuation- How management of change and asset changes impact controller awareness and oversight✅ Episode 3 preview: shift change and handover—operational continuity, communication breakdowns, and transfer best practices.Presented by Opsite Energy: www.opsiteenergy.com00:00 – Episode 2 intro: roles, authority, and awareness00:24 – Why this series matters (regulated + unregulated control rooms)01:38 – What to expect: structure, responsibility, and “zero confusion”02:26 – Normal vs abnormal vs emergency operations (what must be defined)03:18 – Core mandate: written procedures + authority clarity04:20 – Setting controllers up for success (span of control + decision authority)05:06 – Qualification: OQ, covered tasks, and console-specific competency06:52 – Recognizing abnormal events + required response steps + timing08:34 – The “physical domain” of responsibility (geo/operational span)09:10 – What auditors ask: domain awareness + documentation + access09:44 – Defining the domain: assets, maps, drawings, system knowledge10:52 – Managing change: acquisitions, asset adds/removals, training updates12:13 – Abnormal & emergency actions: procedures + escalation + shutdown authority14:18 – Third-party risk: procedures vs CRM plan contradictions15:00 – Why companies get cited: missing “independent shutdown authority”15:49 – Common scenarios: comm loss, delivery points, leak detection alarms17:31 – Pressure limit responsibility: MAOP/MOP awareness + setpoints18:40 – Maintaining awareness during comm loss (field checks + internal comms)20:10 – What auditors verify: access to procedures, MAOP/MOP, setpoints21:22 – Handling the unexpected: SCADA failure, comm outage, evacuation23:23 – What auditors want: evidence you’re not “figuring it out live”24:49 – Recap: empower controllers, validate pressure awareness, plan for worst26:00 – Daniel’s summary: procedures, domain, pressure limits, unexpected events27:28 – Episode 3 preview: shift change & handover28:18 – Close: like/subscribe/comments + endMusic: Uygar Duzgun / “Fast Life” courtesy of www.epidemicsound.com

Copyright 2025 All rights reserved.

Podcast Powered By Podbean

Version: 20241125