PHMSA Control Room Management Series - Part II : Roles, Authority, Awareness - Ep 059
from EnergyTech Podcast Hosted by Opsite Energy
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.com 00:00 – Episode 2 intro: roles, authority, and awareness 00: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 clarity 04:20 – Setting controllers up for success (span of control + decision authority) 05:06 – Qualification: OQ, covered tasks, and console-specific competency 06:52 – Recognizing abnormal events + required response steps + timing 08:34 – The “physical domain” of responsibility (geo/operational span) 09:10 – What auditors ask: domain awareness + documentation + access 09:44 – Defining the domain: assets, maps, drawings, system knowledge 10:52 – Managing change: acquisitions, asset adds/removals, training updates 12:13 – Abnormal & emergency actions: procedures + escalation + shutdown authority 14:18 – Third-party risk: procedures vs CRM plan contradictions 15:00 – Why companies get cited: missing “independent shutdown authority” 15:49 – Common scenarios: comm loss, delivery points, leak detection alarms 17:31 – Pressure limit responsibility: MAOP/MOP awareness + setpoints 18:40 – Maintaining awareness during comm loss (field checks + internal comms) 20:10 – What auditors verify: access to procedures, MAOP/MOP, setpoints 21:22 – Handling the unexpected: SCADA failure, comm outage, evacuation 23:23 – What auditors want: evidence you’re not “figuring it out live” 24:49 – Recap: empower controllers, validate pressure awareness, plan for worst 26:00 – Daniel’s summary: procedures, domain, pressure limits, unexpected events 27:28 – Episode 3 preview: shift change & handover 28:18 – Close: like/subscribe/comments + end Music: Uygar Duzgun / “Fast Life” courtesy of www.epidemicsound.com
Embed this episode
Chapters
- 0:00 Episode 2 intro: roles, authority, and awareness
- 0:24 Why this series matters (regulated + unregulated control rooms)
- 1:38 What to expect: structure, responsibility, and “zero confusion”
- 2:26 Normal vs abnormal vs emergency operations (what must be defined)
- 3:18 Core mandate: written procedures + authority clarity
- 4:20 Setting controllers up for success (span of control + decision authority)
- 5:06 Qualification: OQ, covered tasks, and console-specific competency
- 6:52 Recognizing abnormal events + required response steps + timing
- 8:34 The “physical domain” of responsibility (geo/operational span)
- 9:10 What auditors ask: domain awareness + documentation + access
- 9:44 Defining the domain: assets, maps, drawings, system knowledge
- 10:52 Managing change: acquisitions, asset adds/removals, training updates
- 12:13 Abnormal & emergency actions: procedures + escalation + shutdown authority
- 14:18 Third-party risk: procedures vs CRM plan contradictions
- 15:00 Why companies get cited: missing “independent shutdown authority”
- 15:49 Common scenarios: comm loss, delivery points, leak detection alarms
- 17:31 Pressure limit responsibility: MAOP/MOP awareness + setpoints
- 18:40 Maintaining awareness during comm loss (field checks + internal comms)
- 20:10 What auditors verify: access to procedures, MAOP/MOP, setpoints
- 21:22 Handling the unexpected: SCADA failure, comm outage, evacuation
- 23:23 What auditors want: evidence you’re not “figuring it out live”
- 24:49 Recap: empower controllers, validate pressure awareness, plan for worst
- 26:00 Daniel’s summary: procedures, domain, pressure limits, unexpected events
- 27:28 Episode 3 preview: shift change & handover
- 28:18 Close: like/subscribe/comments + end
No transcript yet.