EXPOSED
This is screen-based work — SCADA/EMS monitoring, load forecasting, logging switching orders — and the routine layer of it (state estimation, contingency analysis, alarm triage, load-flow calculation, shift log documentation) is already heavily software-driven and getting more so. What holds the job is that NERC reliability standards require a certified human system operator making real-time restoration and switching decisions under contingency, and that operator personally owns the call when a line trips or a storm cascades. Embodiment is low (you sit in a control room), and the trust relationship is with field crews and neighboring balancing authorities rather than paying customers, so the moats are licensure, judgment, and accountability — not physical presence.
Mixed — a routine tier and a judgment tier. State estimation, contingency screening, and load forecasts already run automatically every few minutes, and alarm suppression logic files half your nuisance alarms before you see them — but writing a switching order for an unplanned outage on a reconfigured feeder, coordinating clearances with a line crew who just found something the model doesn't show, and deciding load-shed order during a capacity emergency are still hand-built each time, which is what puts this at 12 rather than in the automatable band.
Some physical or field component. You work seated at a console for a 12-hour shift; the only physical elements are being bodily present in a hardened control room that cannot be staffed remotely under CIP requirements, and occasional relocation to a backup control center during drills or evacuations — no field work, so 5 rather than 0.
Licensed human required and personally liable. NERC certification as a Reliability Coordinator, Balancing, or Transmission Operator is a hard statutory prerequisite with continuing-education hours and exam renewal, and IRO/TOP standard violations attach to the certified operator's actions with penalties assessed against the entity — but you are an employee acting under an approved operating plan, not an independently licensed professional carrying your own exposure, which caps this at 14.
Some relationship component. Field crews and neighboring balancing authorities take your switching instructions partly because they know your voice and your track record on the tie-line, and the seniority order desk relationships matter during a storm — but end-use customers never know your name and your authority comes from the console you're sitting at, not from anyone choosing you.
Exists to be accountable for ambiguous calls. When a 345kV line trips and the next contingency would overload a parallel path, you have minutes to decide whether to redispatch, curtail firm load, or ride it out, with no procedure covering that exact system state — and the decision to shed load, or to delay shedding it, is logged in your name and reviewed in the post-event analysis.
Has AI actually changed your work?