CHAPTER 04 · TEAM VIEW
One System, a View Built for Each Role
What each role sees on day one. Same grid data, a different lens for each. Click a role to switch.
WHAT EACH ROLE SEES ON DAY ONE
WHAT AGENTS HANDLED FOR YOU TODAY
DATA VIEW7
Anomalies explained
6
Confirmations accepted
1
Escalations sent up
2
Shift-handoff notes carried forward
Anomalies used to take ten minutes to explain across three screens. Now the explanation is already there when the alarm fires.
2 items need your judgment
Unit 4 output deviation matches a compressor-fouling pattern seen before
Confirmation ready to accept or escalate
Unit 3 startup-cycle count trending above plan
Engineering review requested
WHAT AGENTS HANDLED FOR YOU TODAY
DATA VIEW7
Anomalies reviewed
1
Escalations handled
1
Compliance notes drafted
~8 min
Shift-handoff review time
You used to spend 30 minutes reconstructing the shift for the handoff. Now it's an 8-minute review of what the system already found.
1 item needs your sign-off
Unit 4 anomaly needs a compliance note before shift end
Draft ready, cites the NERC reporting template
WHAT AGENTS HANDLED FOR YOU TODAY
DATA VIEW3 / 3
Regions reporting
41
Anomalies explained this week
0
Compliance findings
91%
Anomaly-confirmation rate
The weekly compliance review used to start with 'let's reconstruct what happened.' Now it starts with the explanation already documented.
1 item needs your approval
Wave 2 scoping ready — dispatch prioritization
Budget and timeline for sign-off before kickoff
THE FULL REPORT
A Full Day's Report
We feed the agent your company's own goals and priorities — not just floor data — so the report reads like it was written by someone who knows what leadership cares about this quarter.
Grid Anomaly Monitoring & Explanation Report
Region 2 — Balancing Authority · Shift 2, Tuesday · Auto-generated 6:10 AM · Reviewed by Shift Supervisor 6:22 AM
Headline Metrics
The same core metrics on every report, every day.
Anomaly Response Time
90 sec
Target < 2 min
-40% vs. last week
Anomalies Explained
96%
Target 90%
+4 pts
Generation Availability
97.8%
Target 97%
On target
Compliance Findings
0
Target 0
Clean, 6 weeks running
Executive Summary
All three regions reported on time. Unit 4's output deviation and Unit 3's startup-cycle count are the two items that need a decision before shift end — everything else is inside normal range. Nothing here needs an escalation before the 7:00 AM handoff.
3 / 3
Regions reporting
2
Open items
0
Escalations
Clean
Compliance status
Aligned to Your Strategic Priorities
Protect grid reliability — the region's #1 mandate
Every item below is ranked by reliability impact, not just alarm severity.
Stay ahead of NERC compliance exposure
Every anomaly gets a documented explanation the moment it's confirmed, not reconstructed after the fact.
Close the two-person bottleneck on anomaly interpretation
Every operator on shift gets the same explanation quality the two most experienced people used to provide alone.
Floor Strategy
Every issue, broken the same way every time — what happened, why, and what to do about it.
Unit 4 — Output Deviation
SIGNAL
Output running 6.2% below the 30-day average, heat-rate drift +3.1% vs. commissioning spec.
INSIGHT
Matches a compressor-fouling pattern from 11 months of fleet history — not an immediate reliability risk, but worth inspecting before the next planned outage.
ASK
Schedule a borescope inspection before the next planned outage, not after.
Source: Unit 4 SCADA telemetry, trailing 30 days
Regional Anomaly — Balancing Authority 2
SIGNAL
Frequency deviation flagged at 2:14 AM, 90 seconds from ingest to explanation.
INSIGHT
Matches a known demand-ramp pattern tied to the region's morning industrial startup — not a grid-stability event.
ASK
Confirm the explanation before shift change so the pattern is logged for next week's forecast.
Source: Balancing Authority 2 EIA feed, 2:00–2:30 AM
Unit 3 — Startup-Cycle Count
SIGNAL
Startup-cycle count extracted at 71% confidence, below the 85% auto-log threshold.
INSIGHT
Low-confidence extractions are exactly the case the threshold exists for — auto-logging this one risks a mis-recorded maintenance interval.
ASK
Route to engineering for a manual check before adjusting the maintenance interval.
Source: Unit 3 SCADA log, page 1 of startup report
NERC Reporting — Region 2
SIGNAL
41 anomalies explained this week, 96% above the 85% auto-log confidence threshold.
INSIGHT
Explained-vs-flagged rate has climbed every week since go-live — the model is absorbing operator corrections, not just running static rules.
ASK
No action — cite this week's rate in the quarterly compliance review as evidence of the improvement trend.
Source: Region 2 anomaly log, trailing 7 days
Everything monitored, at a glance
Unit 2
Combined-cycle generation · Nominal
Unit 3
Startup-cycle tracking · +2 vs. plan
Unit 4
Output & heat-rate · -6.2% output
BA Region 2
Frequency deviation · 90 sec response
Front-Office Signals
The report doesn't stop at the floor — same daily cadence, further up the business.
Regulatory filing backlog
0 open items
Inside normal range.
Demand-response contract utilization
12% of capacity
Slightly below plan — flagged for the commercial team, not urgent.
Maintenance-budget variance
+1.4% vs. plan
Trending flat month over month.
How This Compares
| Metric | This operation | Peer benchmark | Source |
|---|---|---|---|
| Anomaly response time | 90 sec | 6.5 min | NERC regional reliability median |
| Generation availability | 97.8% | 95.2% | EIA fleet-wide benchmark |
Recommended Actions Today
Every line above cites its source — a specific feed, log, or benchmark table, not a summary of a summary. If we can't show where a number came from, we consider that a bug.
UP NEXT · RUN & IMPROVE