Episodes

Monday Mar 16, 2026
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
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
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
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
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

Monday Feb 09, 2026
Monday Feb 09, 2026
Cybersecurity isn’t just growing—spend and complexity are rising fast, and OT teams are being asked to do more with the same (or fewer) resources. In this episode of the Energy Tech Podcast (presented by OpSite Energy), Jeff and Mike Flores continue the Neeve series with Bill Bane and Jerry Reeves, focusing on what OT security needs going into 2026.We break down why SASE (Secure Access Service Edge) and Zero Trust are shifting from enterprise IT into OT operations—and why the old model of cobbling together tools around the Purdue model is getting replaced by foundational security.You’ll hear practical discussion on:- Continuous updates as a core requirement of SASE- Edge security catching up to edge compute- Encrypted operating systems, secure boot, TPM concepts- Certificate-based trust (X.509) and encrypted sessions- SSO + MFA + least privilege as identity-first controls- Cloud agility + multi-cloud connectivity without forcing data through a vendor cloud- Where real cost reduction shows up: fewer agents/tools, lower labor, less sprawl, and better bandwidth efficiency- Why AI-ready data starts with secure, unified access and clean architectureThis is episode 2 of a series: drop your toughest OT security questions in the comments and we’ll hit them in the next installment.Guests: Bill Bane & Jerry Reeves (Neeve)Hosts: Jeff + Mike Flores (Energy Tech Podcast / OpSite Energy)0:00 Intro — Future of industrial automation operations (Neeve series)0:35 Live from OpSite Energy Control Center (Canonsburg, PA)1:02 Why cybersecurity spend is rising + 2026 drivers (AI, cloud-native, identity)2:06 Why OT cybersecurity matters going into 20262:20 SASE recap: enterprise IT security brought into OT3:16 Security becomes foundational (no “bolt-on” protections)3:29 SASE requires continuous updates + continuous scrutiny4:14 The 4 pillars: security, edge compute, encrypted data, cost reduction5:12 Series recap + why this episode leans into cyber5:50 Edge-to-cloud OT ecosystem overview6:01 “Walled-off” operational plane + invisible from the internet6:21 Unified platform = efficiency + security7:13 Flip the ratio: less time worrying about cyber, more time on ops7:39 “Walk-around” qualifications + why validation matters8:05 Fighter pilot analogy + “walk-around” checklist8:26 Battle-tested + certifications/compliance claims9:15 Foundational = reduced human error9:35 Hardened OS + edge security catching up to edge compute11:16 Industrial edge node + outbound 443 + encrypted OS + TPM + secure boot12:23 Why edge nodes are now critical infrastructure13:14 “Secure tunnel” isn’t VPN—session security + encrypted traffic13:45 AES-256 + certificate-based trust (X.509)14:28 Bidirectional management for orchestration + updates15:50 Remote access still matters, but security is primary16:15 Zero Trust + SSO + MFA; eliminating VPN agent sprawl17:13 Data lineage approach (edge → access → cloud)17:40 Optional managed hosting (e.g., SCADA), data goes where you want18:05 Cloud agility + multi-cloud + OT mesh vs hub-and-spoke19:13 Data doesn’t have to go through the vendor cloud19:38 “Pay-cloud” example (fleet compression) + data ownership21:33 Cost reduction discussion starts22:14 Where savings show up: VPN agents, insurance, labor, fewer tools23:57 Cutting cloud data engineering costs (contextualize earlier)25:17 Edge compute reduces bandwidth + ongoing upkeep26:16 Data + power efficiency benefits27:52 Vendor sprawl + field hardware sprawl (Palo Alto example)30:11 Real-world savings example (7-figure annual reduction claim)31:22 “Top 3 things” for OT leaders bridging IT/OT32:43 Continuous updates explained (dynamic vs static)34:49 Security through simplicity + orchestration via familiar UI38:41 AI-ready data + Neeve.ai + agent discussion44:48 Wrap-up + like/subscribe + next episodeMusic: Uygar Duzgun / “Fast Life” / courtesy of www.epidemicsound.com

Monday Feb 02, 2026
Monday Feb 02, 2026
Welcome to Part I of the Energy Tech Podcast Control Room Management (CRM) mini-series. In this kickoff episode, Mike Flores and Daniel Nieto (Regulatory Compliance VP at OpSite Energy) break down the scope and applicability of PHMSA Control Room Management—so you can answer the most important first question:- Does CRM apply to your operation?- This episode lays the foundation for your entire CRM program, including:- What PHMSA considers a “control room” (it’s not always a dedicated room)- The definition of a “controller” and why qualification/OQ matters- The “litmus test”: remote monitoring + control of pipeline facilities- The difference between gas vs hazardous liquid applicability (and why liquids have no exceptions)- How limited scope works for certain gas operations and what you still must comply with- Why compliance is room-level, not console-level (one fully regulated desk can pull the whole room into full scope)- Why documentation is everything (audits, turnover, acquisitions, asset changes)If you’re in pipeline operations, SCADA/OT, control room leadership, regulatory compliance, or building a new control room—this episode helps you avoid the most common early mistake: getting applicability wrong.00:00 – Welcome to the Energy Tech Podcast00:16 – Introducing the Control Room Management Mini-Series00:38 – Meet the Hosts: Mike Flores & Daniel Netto01:13 – Setting the Stage: Why CRM Scope & Applicability Matters02:06 – Why CRM Often Gets Missed Until an Audit02:43 – Regulatory Foundation: What Triggers CRM Applicability03:21 – Gas vs Hazardous Liquid: Key Regulatory Differences04:27 – What Actually Defines a Control Room?05:18 – What Is a Controller? Roles, Authority, and Responsibility06:02 – PHMSA Regulations: 49 CFR 192 vs 195 Explained07:09 – The CRM “Litmus Test” for Applicability08:39 – Documenting Applicability Decisions for Audits09:32 – Why CRM Scope Must Be Written and Communicated10:36 – Controller Qualification & Training Requirements11:58 – Authority Beyond SCADA: Field Direction Counts13:32 – When Does the CRM Rule Officially Apply?14:47 – Regulated vs Non-Regulated Assets Explained16:18 – When CRM Does *Not* Apply17:36 – Formalizing Applicability & Written Justification18:02 – Using API RP 1168 as a CRM Framework19:02 – Limited Scope CRM: What Still Applies20:40 – Fatigue Mitigation, Compliance & Deviations22:03 – Real-World Example: Limited Scope CRM Audit23:27 – Why Applicability Must Be Front-and-Center in the CRM Plan25:06 – The Room-Level Rule Explained26:58 – Multiple Consoles, One Control Room28:19 – Hazardous Liquid: No CRM Exceptions29:16 – Key Action Items for Operators & Managers31:17 – Episode Takeaways & What’s Next in the Series32:44 – Preview: Roles, Authority & Awareness (Episode 2)33:01 – Like, Subscribe & Final Wrap-UpMusic: Uygar Duzgun / “Fast Life” / courtesy of www.epidemicsound.com

Monday Jan 26, 2026
Monday Jan 26, 2026
Industrial OT is evolving fast: more sensors, more data, more edge compute, and far more pressure to do remote work securely. In this episode of the Energy Tech Podcast, Mike Flores sits down in the OpSite Energy Control Center (Canonsburg, PA) with Bill Bane and Jerry Reeves from Neeve to unpack why the traditional VPN-based remote access model is breaking and what replaces it.We dive into how SASE (Secure Access Service Edge) and Zero Trust are moving from enterprise IT into OT operations without adding complexity for OT teams. Bill and Jerry explain how Neeve delivers a unified encrypted edge-to-cloud data plane, browser-based single sign-on, industrial-grade edge hardware, and an app marketplace / container platform that allows OT teams to deploy tools like Ignition Edge, Autosol, Naomi, and Node-RED with minimal friction.The conversation also covers real-world OT challenges:legacy equipment, protocol gaps, edge reliability, “shadow IT,” and why multi-cloud architectures (AWS, Azure, GCP, plus on-prem) are becoming the default—not the exception.If you’re building modern OT architectures around secure remote access, edge compute, UNS/MQTT, and data-driven operations, this is a must-watch episode.Guests: Bill Bane & Jerry Reeves (Neeve)Host: Mike Flores (Energy Tech Podcast / OpSite Energy)👍 Like, subscribe, and drop questions—this is a series, and we’re just getting started.0:00 Intro — Live from the OpSite Energy Control Center0:30 Meet Neeve: Bill Bane & Jerry Reeves1:10 Why Neeve, why now3:10 OT’s shift toward edge compute and data value4:40 What Neeve really is (and what it isn’t)6:20 IT/OT convergence: uptime, security, and data10:10 SASE explained for industrial OT12:40 Is this the end of VPNs in OT?14:20 Zero Trust without OT complexity16:45 Browser-based access + device-level security19:10 CIO / CISO buy-in and enterprise alignment20:45 UNS, MQTT, and edge data architectures22:00 Neeve’s industrial edge hardware + encrypted OS23:05 One-click apps: Ignition Edge, Autosol, Nomi, Node-RED25:40 Simple deployment: outbound 443 only27:10 Small operators vs enterprise scale29:10 Supporting legacy OT without rip-and-replace31:15 Container orchestration inside Neeve33:40 App marketplace and future expansion37:30 Multi-cloud OT and secure mesh networking39:20 The “why” behind Neeve41:20 Wrap-up and what’s nextMusic: Uygar Duzgun / “Fast Life” / courtesy of www.epidemicsound.com

Monday Jan 19, 2026
Monday Jan 19, 2026
Welcome back to the Energy Tech Podcast — Jeff and Mike are in the OpSite Energy Control Room for a 2025 year-end review and a 2026 industrial technology outlook.We break down what changed in 2025 (and what actually mattered): the shift from “chatting with data” to acting on data, the rising reality of power + compute constraints, and why most AI projects stall when data governance, lineage, and trust aren’t engineered first.- Then we lay out our 2026 outlook across oil & gas, renewables, manufacturing, and data centers, including:- The move from chatbots → industrial agents (within guardrails) that can trigger work orders, manage routine workflows, and integrate third-party data- Why 2026 becomes the year we stop “trying AI” and start engineering trust (lineage, governance, semantics)- The rise of UNS (Unified Namespace) and DataOps layers as requirements (not buzzwords)- The growing collision of data center demand with grid constraints, off-grid projects, and energy delivery realities- Why liquid cooling becomes mandatory for high-density AI compute — and why “power compute efficiency” matters- Edge computing and small models: keeping critical operations resilient when cloud links drop- A prediction: cybersecurity becomes even more board-level and operationally central in 2026We also share what OpSite is building in 2026 — including a data center/colo sandbox, new edge product coverage, and a Control Room Management mini-series to break down compliance into usable, practical pieces.Drop your 2026 predictions in the comments — and don’t forget to like & subscribe.00:00 Intro — 2025 year-end review + 2026 outlook01:10 Theme: from “chatting with data” to acting on it02:35 2025 macro trends: grid congestion + power constraints03:40 Data centers: PA as a “dark horse,” off-grid momentum06:35 Data as commodity: edge centers, semantics, orchestration08:10 2025 trend: cybersecurity becomes program-level10:05 “Structural reality”: power + compute constraints11:10 AI reality check: trust, governance, data models13:20 2025 pillars: UNS, DataOps, augmentation17:20 Energy Tech Podcast 2025 recap (50 episodes, ICC)19:55 Favorite guests + why they stood out25:15 OpSite 2025 recap: control room build + growth30:20 2026 outlook framework: augmentation → automation35:10 Trend #1: chatbots → industrial agents (guardrails)38:10 Trend #2: SMRs + nuclear/data center convergence39:30 Trend #3: liquid cooling + power compute efficiency42:15 Trend #4: edge computing + cost control43:55 Trend #5: “decision engineer” roles emerge47:05 2026 thesis: stop playing with tech, start engineering trust48:00 OpSite 2026: data center/colo sandbox + new products56:10 Control Room Management mini-series announcement58:45 Quick oil price guess + 2026 cyber prediction1:00:35 Wrap-up + call to actionMusic: Uygar Duzgun / “Fast Life” / courtesy of www.epidemicsound.com

Monday Jan 12, 2026
Monday Jan 12, 2026
In this episode of the Energy Tech Podcast, we’re live from ICC 2025 in Sacramento with Matt Steel, Senior SCADA Engineer at Primoris Renewable Energy.Matt shares a practitioner’s view of how Ignition is becoming the de-facto SCADA platform for utility-scale solar and battery storage projects—and what Ignition 8.3 unlocks for scalability, DevOps, and long-term fleet operations.We dive into:- How EPCs and asset owners manage SCADA across dozens of renewable plants- Why nearly every utility-scale solar and storage project uses Ignition- What Ignition 8.3 changes for historians, flat-file configuration, and CI/CD- The challenge of integrating plant-level SCADA with fleet-wide O&M platforms- Using Ignition as middleware and IoT infrastructure, not just HMI- Standard data models, UDTs, and self-deploying Ignition projects- Where AI actually delivers value today in SCADA and controls engineering- Why community, not hype, is the real force behind Ignition’s growthIf you’re working in renewable energy, EPC engineering, SCADA architecture, or industrial DevOps, this episode is packed with real-world insight from the front lines.🎧 Recorded live at Inductive Automation ICC 202500:00 Intro – Energy Tech Podcast live at ICC 202501:05 Matt Steel’s role at Primoris Renewable Energy02:20 How EPCs approach SCADA in utility-scale solar & storage03:40 ICC 2025 “Level Up” theme & conference growth04:55 Ignition 8.3 release and why it matters06:30 Why nearly every renewable project uses Ignition08:00 Integrating plant SCADA with fleet-wide O&M platforms09:40 The need for standard data models in renewables11:30 Ignition as middleware, not just SCADA13:20 UDTs, self-deploying projects, and scaling engineering teams15:10 DevOps, CI/CD, and flat-file configuration in Ignition 8.317:00 Community, Prove-It, and real-world creativity at ICC18:20 AI hype vs. real value in industrial automation20:10 Where AI actually helps SCADA engineers today21:00 Closing thoughts from ICC 2025Music: Uygar Duzgun / “Fast Life” / courtesy of www.epidemicsound.com


