People Analytics Toolbox

Ask about this role

grounded in this role's JobFrame record + structure

Download this job's description (markdown) → derived live from this record.

Key statistics

The identity block — every fact is canon, none is generated.

2 of 8

Track

Individual contributor

Family rungs priced

P1 · P2 · P3 · P4 · P5 · P6

—

industrial_energy_operations

Coordinates

2 / 4 spaces

pay@2 · 2026-07

What this role is

Monitors and operates control systems for energy or mining sites under routine supervision, building proficiency in daily operational procedures. At the Developing Professional (P2) level, the role owns defined deliverables / small features, applies established patterns, and drives own and immediate-team deliverables. May guide interns.

What this level does

Independently monitor and operate utility systems across a shift, interpreting SCADA data and taking conventional corrective actions within established procedures
Dispatch and coordinate field crews for both routine work and first-line disruptions, updating outage and work-management records
Respond to alarms and abnormal conditions using defined response procedures, and hand off unresolved or novel situations with a clear operational summary
Perform routine tuning of control setpoints (pumps, valves, load points) to keep systems within operating limits and maintain redundancy
Assist in exercising emergency plans and call trees, and provide informal guidance to newly-hired operators on panel operation

Knowledge applied: Applies working knowledge of SCADA monitoring and conventional control actions across utility systems; operates independently within defined procedures.
Complexity & problem solving: Exercises judgment in familiar abnormal conditions, applying defined response procedures and escalating novel events.
Collaboration & interaction: Coordinates with field crews and fellow operators; may guide newly-hired operators on panel operation.
Typical experience: 2+ years in control-room or utility operations.

Skills at this level

SCADA operation: — Uses Supervisory Control and Data Acquisition systems to monitor and control utility networks in real time, acting on telemetry to adjust setpoints, switch equipment, and maintain system state.
EMS advanced application configuration: — Configures and supports advanced Energy Management System tools such as State Estimator, defining modeling assumptions and running network contingency analysis on the transmission system.
ADMS/OMS outage coordination: — Uses Advanced Distribution Management and Outage Management Systems to plan, track, and restore utility disruptions, sequencing switching and crew dispatch during outage events.
Control-panel and device operation: — Operates utility control panels, switches, valves, and control devices to deliver water, electricity, gas, and wastewater services safely within operating limits.
Load balancing and plant optimization: — Tunes control strategies using BAS/SCADA and energy-management data to balance loads, minimize fuel usage, and maintain redundancy across utility systems.
Contingency analysis: — Performs forward-looking evaluation of electrical transmission operation to anticipate credible failure scenarios and pre-position for reliable system response.
Outage and emergency response planning: — Develops and exercises emergency plans, call trees, and restoration procedures, then directs crew dispatch and switching during real-time disruptions.
Root-cause analysis of system failures: — Investigates recurring utility-system alarm and equipment failures to identify underlying causes and drive corrective setpoint or procedural changes to closure.
NERC/IEEE compliance knowledge: — Applies reliability standards such as NERC and IEEE to control-room operations, ensuring switching, documentation, and restoration practices meet regulatory requirements.
Crew dispatch and coordination: — Directs field crews to work orders and disruptions via 2-way radio console and work-management systems, coordinating with fellow operators and law enforcement to ensure safety.
Telemetry interpretation and situational awareness: — Reads data from monitoring devices to maintain continuous awareness of system state, distinguishing routine variation from conditions requiring corrective action.
Operator training and mentorship: — Guides operators on SCADA operation, alarm handling, and restoration procedures, building shift-team capability and readiness for advanced contingency handling.

Model-authored from 18 retrieved sources, then adversarially reviewed by an independent judge panel and held to a minimum-evidence floor before publication. Distinct from corpus-extracted content, which is labelled as such.

Pay across the ladder

Control Operations — median with , by . Real canon data.

National-base pricing — this family's function differential is pending review, so dollar levels are not function-adjusted (level-over-level % is unaffected).

Pay figures are modeled estimates from our market equation — level-differentiated, with honest-wide bands. They refresh as new leveling evidence lands; treat per-role dollars as directional.

Demand — is the field growing, or just turning over?

Employment growth 2019–2024, BLS OEWSobserved

+23.2%Plant and System Operators, All Other · United States

12,950 → 15,950 jobs

1,600 openings / year, split into:

replacement / exits 1,574

Growth — new jobs (2%)Exits — backfill (98%)

2% of hiring here is genuine expansion; the rest backfills people who move on.

Projected growth 2024–34 expanding: +1.6%
Growth share of hiring: 2%
Exit / retention pressure high: 98%
Openings / year: 1,600

Two quantities, kept apart: observed = employment growth differenced from two BLS OEWS vintages (what already happened); projected = BLS Employment Projections 2024–34, openings decomposed into growth + exits (growth derived from projected employment change). Neither is a pay figure.

Where this role sits — growth vs. pay

level P2 held

Demand axis is projected growth (not raw openings — that just measures churn). A curated, de-duplicated set of recognizable occupations held at this level; this role is highlighted.

Where it pays — by metro

OEWS metro median

San Jose-Sunnyvale-Santa Clara, CA$118k

San Francisco-Oakland-Fremont, CA$105k

Washington-Arlington-Alexandria, DC-VA-MD-WV$98k

Boulder, CO$96k

Seattle-Tacoma-Bellevue, WA$96k

Boston-Cambridge-Newton, MA-NH$92k

Lexington Park, MD$90k

Trenton-Princeton, NJ$89k

Pay only — metro-level demand isn't in public data (it needs job postings). National median $71k; the demand-cube initiative will add growth-by-metro.

What changes across the ladder

Level-distinction canon isn't available for the adjacent levels of this profile yet.

Level differentiators

What separates P2 (P2 — Developing Professional) from the levels around it — this level only. Every word is real canon for this profile.

Scope: Defined deliverables / small features
Autonomy: General supervision; reviewed at milestones
Complexity: Some non-routine problems; applies established patterns
Impact: Own and immediate-team deliverables
Decision rights: Routine technical choices within guidance
Leadership: May guide interns

Full level-by-level matrix (side by side across the ladder) lives on the Ladder drill-down — not here.

Promotion

The next rung from P2 is P3.

Performance criteria for this profile render in the assessment kit →

People also watch

Nearest coordinate neighbors — same , same level. Each row's (confident / review / no match) comes from its — computed, not curated.

Profile	Key	Median	Δ structural
SVP, Control Operations	jf_control_operations::E2	$322,728†	confident0.06
Senior Supervisor, Control Operations	jf_control_operations::M2	$110,455†	confident0.06
Control Room Operator	jf_control_operations::S2	$42,923†	confident0.06
Associate Control Room Operator	jf_control_operations::P1	$61,862†	confident0.06

†National-base pricing — this family's function differential is pending review, so the dollar level is not function-adjusted.

Capability cluster

O*NET 51-8099

Core to this role. Click any element with an ⓘ for its O*NET definition. A job-specific capability model (SkillFrame) will sharpen this and add worked examples.

The Job Swatch

P2

jf_control_operations::P2

Control Room Operator

Control Operations

no content fingerprint

The swatch is JobFrame's core primitive: a hueset deterministically by the role's superfunction, the profileKey as its color code, the level ladder, and a content fingerprint. Two swatches that look alike are alike.

Because every role carries computable coordinates, similarity, leveling, and pricing become measurable instead of arguable— the whole point of "Pantone for jobs."

Structural

structural@1

Where it sits— position in the work taxonomy + level (weighted Gower, level > function > focus).

Track: P
Superfunction: industrial_energy_operations
Function: energy_utilities_business_operations
Family: control_operations
Universal level: 2 / 8

Content

content@2

What it's about— a fingerprint over the role's tasks & capabilities.

No content fingerprint for this profile.

Two roles can sit far apart structurally yet be close in content — that gap is itself a signal.

3-state matching

How any two swatches compare — a real distance in coordinate space, resolved to a calibrated verdict (never a fake "94% match").

Assets · P2review0.17

Emissions · P2review0.17

Energy Grid · P2review0.17

Energy Operations · P2review0.17

Land / Property · P2review0.17

Mining Operations · P2review0.17

Editions — frozen & versioned

structural@1live

Released 2026-06-17

content@2live

Released 2026-07-28

pay@2live

Released 2026-07-02

semantic@1live

Released 2026-07-02

Coordinates belong to a frozen, versioned edition — a coordinate computed today still means the same thing next quarter. Re-fitting issues a new edition, so comparisons are never silently redefined.

How to read this profile

Every number here is traceable — to a named source, a stated method, and an as-of date — and each value is labeled by how we know it: observed from data, computed by a model, projected forward, or governed canon. Nothing is a black box, and nothing is invented to fill a gap.

Where every number comes from

What	Source & method	Edition	State
Median pay + range	JobFrame pay equation (function base × family multiplier × level × focus differential)	pay@2	computed
Pay across the ladder	Same equation applied at each universal level	pay@2	computed
Demand — growth & openings	BLS Employment Projections; openings decomposed into growth + exits	EP 2024–34	projected
Pay by metro	BLS OEWS metropolitan medians	OEWS 2024	observed
Level distinctions	JobFrame universal-level canon (scope · autonomy · complexity · impact · decision rights · leadership)	canon	canon
Capability cluster	O*NET Knowledge / Skills / Abilities	O*NET 51-8099	computed
Coordinates	JobFrame coordinate system — structural (weighted Gower) + content fingerprint	structural@1 · content@2 · pay@2 · semantic@1	computed
Related roles	Nearest neighbors in the structural coordinate space	structural@1	computed

The principles behind the numbers

Ranges, not false precision

Pay is P10 · median · P90, never a single misleading number.

Three honest states, never a fake %

Role matches resolve to confident / review / no-match — a calibrated verdict, not a made-up percentage.

Provenance on every value

Each number carries whether it's observed, computed, projected, or canon — so you always know how much to lean on it.

Gaps shown as gaps

When a figure isn't available at the grain you need, we say so — we don't fabricate a number to fill the cell.

Frozen, versioned editions

Pay and coordinate editions are pinned, so a comparison you make today still means the same thing next quarter.

Privacy by min-N

Any aggregate over people is suppressed below a minimum count, so no individual is identifiable.

Freshness

As of2026-07-30Editioncanon-v2@2.1.0-completeSourcecanon-v2 cell + salary-benchmark (model)