SearchGrid Operations & Outage Management

Control Room Shift Log

Control room shift handover with every earth, permit and changed setting on the brief — and twelve years of logs to ask

No abnormal condition lost at shift change.

See one case, screen by screen ↓
target0earths, permits or changed settings missed at handover — every one on the brief and read back by name
demo2itemsin the night's log but not in the outgoing note — earths on at KW-7 and auto-reclose left off on a 132 kV line — added to the brief in amber
target30minoff restoration on a repeat event, because how it was handled last time is found in seconds
demo186,240entriesof log history since 2014 searched in 2.8 s for “Last time T3 tripped on Buchholz?” — 4 similar events, with the operator's steps then
The problem

Why abnormal conditions get lost at shift change

At 07:00 and 19:00 a grid control room hands the network to a new crew. What the incoming operator must know — open faults, the parts of the network not in their normal state, permits and earths in force, protection or auto-reclose settings changed for work, what to watch this shift — sits in twelve hours of free-text log entries, hundreds of SCADA alarms, the permit system and the abnormal-network register. On Lumina Utilities' desk 2 at Halden, one night held 47 log entries in operators' shorthand, 312 alarms, 6 permits and sanctions, 3 sets of earths and a 9-line register.

The outgoing operator writes the handover from memory in the last half hour of a twelve-hour shift, and the incoming operator has to trust it. An earth left on, a section believed dead that is back-fed, auto-reclose switched out for live-line work and never restored: these are the items that hurt people when they are missed. Handover has been named as a cause in major accidents since Piper Alpha. And because the log is free text, nobody can ask how the last Buchholz trip on the same transformer was handled — that memory lives with operators who are retiring.

typical167deathson Piper Alpha (1988), where the status of a permit was not handed over at shift change (Cullen inquiry)
typical21%of water-utility staff eligible to retire within five years — and the memory of how rare events were handled goes with them (AWWA 2025 benchmarking)
Where a handover's minutes goestimated
By hand80 days
With the solution18 days
  • Writing the handover note from memory at the end of the shift25 → 5 d
  • Checking permits, sanctions and earths against the permit system8 → 2 d
  • Checking the abnormal-network register against the log7 → 2 d
  • Reading back the handover with the incoming operator10 → 7 d
  • Working out a repeat event without the last time's log30 → 2 d

Estimated split for one 07:00 handover on a 33 kV and 11 kV desk, in minutes, by hand and with the solution. The last row applies only when a repeat event comes up.

How it works

How a shift is handed over

Six specialist agents read the log, alarms, permits and register into a cited brief and find past events; the incoming operator reads it back and the supervisor countersigns.

What comes in
The night in5 sources · log, alarms, permits, register, forecast
Agents at work
Log readershorthand expanded
Then
Alarm summariser
Permit and earth reconciler
Network-state checker
Then
Handover writerone page, cited
Then
Precedent finderhas this happened before?
A person decides
Incoming operatorreads back and takes the shift
What comes out
Signed handover
Open items, cited
Past events found
One case, step by step

How shift handover works: one night, from the log to a countersigned brief

Tuesday 13 October 2026, Network Control Centre, Halden, desk 2 — 33 kV and 11 kV. Owen Pryce has run the night shift: one transformer trip, one cable fault. Nadia Rahman takes the desk at 07:00 and Farid Haddad countersigns. Here is what happens, screen by screen, in the working solution.

  1. 0106:46 · 14 min to go

    The night on one strip, the handover on one page

    Nadia Rahman · Senior system operator

    Across the top, the night shift from 19:00 to 07:00 is one band: every trip, switching operation, permit, earth and changed setting is a tick, with alarms per half hour below — 44 in the half hour before midnight, 88 between 04:00 and 04:30. Below it sits the brief: 14 items in five sections — open faults, network not in its normal state, permits and earths in force, temporary settings and watch this shift — each with its log lines in the margin and an acknowledge box.

    “Built from the shift log, SCADA alarms, the permit system and the abnormal-network register · every line cited”

  2. 02Built at 06:16 in 38 s

    Two items the note left out

    Log reader, Alarm summariser, Handover writer

    The log reader read 47 entries and expanded the shorthand (AR, FPI, NOP, PSR). The alarm summariser turned 312 alarms into 9 events, 61 still standing. The handover writer wrote 14 items with 31 citations, then compared them with the note Owen typed at 06:31: it covers 12 of 14. Two were in the log but not in the note, and carry an amber mark — earths EA-26-3391 on at KW-7, and Ridgeway 132 kV line 2 auto-reclose still off at both ends.

    “Switched out at 22:10 for PTW-26-1187 and left out when the work stopped at 22:50. Switch back in only when the permit is cancelled.”

  3. 03The register

    The abnormal-network register, checked against the log

    Network-state checker

    Nine register lines, five raised tonight: the Marrow Hill 33 kV bus section closed, normal open point KW-9 closed so F22 feeds KW-7 to KW-12, KW-6 and KW-7 open, T3 out and isolated, auto-reclose out on Ridgeway line 2. Each one agrees with its log entry but one: R-0597, Harbour Road 33 kV circuit 1 on hand control. The log says it ended on 3 Oct; the register was never updated.

    Farid Haddad owns the register; the network-state checker only flags where the two disagree.

  4. 04Permits and earths

    Every permit and every set of earths, matched to the log

    Permit and earth reconciler

    Permits to work, a sanction for test, limitations of access and three sets of earths, each with its holder, dates, state and the log entries that recorded it. EA-26-3391 at KW-7 shows “On · not in the handover note”. Below, the permits cancelled in the last 7 days stay listed, because a precedent may need them: PTW-26-1162, Marrow Hill T3 cooler pump P1 replaced, cancelled Saturday 10 Oct at 16:40.

    “The permit system stays the record; nothing here issues or cancels a permit.”

  5. 052.8 seconds

    “Last time T3 tripped on Buchholz?”

    Precedent finder

    T3 tripped on its Buchholz relay at 04:12, 25 minutes after a stage 1 gas alarm. Nadia asks the history. Across 186,240 entries from 2014 to tonight the precedent finder finds 4 similar events and opens the best match, 94 %: 14 Aug 2019, Marrow Hill T3, the entry Rolf Lindqvist wrote at 05:52, as written. Then what the operator did, minute by minute — protection engineer called at 06:05, gas colourless and not flammable at 08:40, relay bled at 11:10, T3 back on load at 12:58: out 7 h 06 min, air trapped after the cooler-pump change.

    Then and now: “Cooler pump P2 changed 2 days before” in 2019 · “Cooler pump P1 changed 3 days before” tonight.

  6. 06The case that ended differently

    Not every Buchholz trip is air

    Precedent finder

    The precedent finder always shows the closest match that ended differently. On 21 Nov 2017 Marrow Hill T2 tripped on Buchholz and differential, with no work before it and no stage 1 alarm. The gas was flammable, the oil showed acetylene at 48 ppm — a winding fault — and T2 was out for 113 days and replaced. So the precedent changes the watch list, not the decision.

    “It does not say what to do tonight. Returning T3 to service is Grace Okafor’s release under OP-TX-07, after the gas result.”

  7. 07One click

    A watch item from the precedent

    Nadia Rahman · Senior system operator

    Nadia adds it to the brief as W3: “T3: gas test result before any re-energising” — 2019 was air after cooler-pump work and T3 was back in 7 h 06 min; 2017 (T2) was flammable gas, a winding fault; T3's cooler pump P1 was replaced on Saturday under PTW-26-1162. It is cited to both old entries and the permit, and marked as added by her. The brief goes to 15 items.

    “Added to the brief as W3 · 15 items”

  8. 0806:52 to 06:55

    Read back, item by item

    Owen Pryce and Nadia Rahman

    Owen reads each item and Nadia confirms it. Every acknowledgement is stamped with her name and the time, from 06:52 to 06:55, on all 15 items — the two amber ones and her own W3 included. The incoming operator cannot accept the shift until every item is acknowledged.

    “The incoming operator cannot sign until every item is acknowledged”

  9. 0907:01 · Countersigned

    Signed, accepted, countersigned

    Farid Haddad · Shift supervisor

    Owen signs as outgoing operator at 06:57. Nadia accepts the shift at 06:58 with 15 items acknowledged. Farid countersigns at 07:01. The handover is filed read-only and the shift's entries join the searchable log history.

    “Farid Haddad countersigned · handover filed and searchable”

  10. 10Every month

    Handover quality, shift by shift

    Lars Brenner · Control-room manager

    The handover record shows every signed handover since the brief went live on 18 August: 112 shifts on a calendar, each coloured by how many items the brief added that the outgoing note had left out. 41 items were added; 15 of them were earths, permits or temporary settings. The median time to acknowledge a brief is 7 minutes.

    “15 of the 41 were earths, permits or changed settings: the items that hurt people when they are missed.”

Who it’s for

Built for everyone who hands over the network.

The same handover, seen by the five people who write it, take it, countersign it, act on it and answer for it — what their shift looked like, and what it looks like now.

NR
Nadia RahmanSenior system operator, day shift · desk 2, 33 kV and 11 kV
Senior system operator
Before
Takes the desk at 07:00 on a note typed at 06:31, at the end of a twelve-hour night, and works out a rare event from scratch. “Tell me what's not normal before I touch anything.”
Now
Reads a one-page brief with every line cited, asks “has this happened before?” in plain words, and accepts the shift item by item.
OP
Owen PryceSystem operator, night shift · ran the night of 12–13 October
System operator
Before
Writes the handover after twelve hours on the desk. “I wrote the handover at quarter to seven after twelve hours. Something always gets left off.”
Now
Signs a brief built from his own log, with the two items his note missed marked in amber before the read-back.
FH
Farid HaddadShift supervisor · countersigns every handover, owns the abnormal-network register
Shift supervisor
Before
Keeps the register true by hand. “If it's on the network, it's in the brief, or I want to know why.”
Now
Sees each register line checked against the log — and the one the log says ended on 3 Oct — then countersigns.
GO
Grace OkaforProtection engineer, on call · releases transformers after a protection trip
Protection engineer
Before
Called at 03:47 on the stage 1 alarm, and told at 04:20 that T3 has tripped. “Nobody puts T3 back on until I've seen the gas result.”
Now
Receives the precedent with its log entries — the 2019 trip that was air and the 2017 one that was a winding fault — and stays the one who releases T3.
LB
Lars BrennerControl-room manager · reviews handover quality monthly
Control-room manager
Before
Reports operational incidents and has no way to measure handovers. “Show me every shift where a permit went unmentioned.”
Now
Sees every shift since 18 August coloured by items the note left out, by kind, with the median time to acknowledge.
Built on the engine

6 agents. Each with one job, and hard limits.

Six specialist agents read the log, alarms, permits and register into a cited brief and find past events; the incoming operator reads it back and the supervisor countersigns.

Log reader

Reads every free-text log entry as it is written, expands operators' shorthand from the desk glossary, tags it — fault, switching, permit, earths, setting, alarm, load, customers, note, handover — and links it to the event it belongs to.

  • Never edits an entry; it is quoted as written
  • Asks when an abbreviation is not in the glossary
Alarm summariser

Turns the shift's SCADA alarm list into events — 312 alarms into 9 tonight — each with its first and last alarm and whether it is still standing, linked to the log entries that mention it.

  • Never drops a standing alarm
Permit and earth reconciler

Lists every permit to work, sanction for test, limitation of access and set of earths in force, finds the log entry that recorded each, flags any the outgoing note does not mention, and looks back 7 days for work on any plant that tripped.

  • Read only: never issues, changes or cancels a permit
  • An earth set is never left off the brief
Network-state checker

Compares the abnormal-network register with the log in both directions: a line the log says has ended, and a log change with no register line.

  • Never changes the register; flags only — the shift supervisor changes it
Handover writer

Writes the one-page brief in five sections — open faults, network not normal, permits and earths, temporary settings, watch this shift — one item per condition with its citations, and marks what the outgoing note left out.

  • A line without a source is removed
  • Never removes an item; only the outgoing operator can, with a reason
  • Ready 30 minutes before handover
Precedent finder

Answers “has this happened before?”: matches on asset, protection, the work done just before and the alarm sequence, quotes the old entry as written, rebuilds what the operator did that day with times, and lays then beside now.

  • Never recommends switching, isolating, earthing or re-energising
  • Always shows a match that ended differently
  • Every step quotes its log entry
Operators and supervisor

Read back, sign, countersign. The agents propose; a named person decides.

Ask in plain words

Ask the log history, in plain words

Ask about tonight's shift or twelve years of logs, or say what to add to the brief. It only answers with a source.

Last time T3 tripped on Buchholz?

Three Buchholz trips on Marrow Hill transformers since 2014. The closest is T3 on 14 Aug 2019: it tripped two days after a cooler-pump change, the gas was air, and T3 was back on load in 7 h 06 min. But T2 on 21 Nov 2017 tripped the same way and had a winding fault. T3's cooler pump P1 was changed on Saturday under PTW-26-1162. The gas result decides; Grace Okafor releases T3 under OP-TX-07.

Which earths are on the network right now?

Three sets. EA-26-3391 at KW-7, cable side, under PTW-26-1190: applied at 02:30 and not in Owen's note. EA-26-3386 and EA-26-3387 either side of Brook Street breaker 4, under PTW-26-1179.

What did Owen's note leave out?

Two items, both in the log: the earths at KW-7 and Ridgeway line 2 auto-reclose still off after the work stopped. With thunderstorms forecast from 15:00, a fault on line 2 would not reclose. Both are marked amber on the brief.

Auto-reclose left off after a permit was cancelled

Twice since 2014 auto-reclose stayed off after the work it was switched out for had finished. In February 2021 Ridgeway line 1 ran 26 hours without auto-reclose, and a lightning fault the next evening did not reclose: 2,140 customers off for 41 minutes. The handover gained a section for temporary settings after that; tonight's brief carries Ridgeway line 2 there (T1).

Every screen

The working solution, as it ships.

13 screens from the working solution, on its sample data. Pick one to see it large.

The handover briefThe night shift on one strip, the brief in five sections with every line cited, and the log history to ask beside it.
What the note left outItems in the log but not in the outgoing note, marked amber, and the note set against the log: 12 of 14 covered.
Network not in its normal stateTonight's switching on Marrow Hill and Kestrel Way, and every register line checked against the log.
Permits and earths in forcePermits, sanctions, limitations of access and every set of earths, with holder, state and the log entries behind each.
Has this happened before?Four similar events ranked by match, the 2019 entry as written, what the operator did then minute by minute, and then beside now.
The match that ended differentlyThe 2017 Buchholz trip that was a winding fault, shown so the precedent never stands in for the gas result.
A watch item from a precedentThe gas test added to the brief as W3, cited to the old entries and the permit, and marked as added by the incoming operator.
Read back item by itemEach item acknowledged with the incoming operator's name and the time.
Signed and countersignedOutgoing operator, incoming operator and shift supervisor; the handover filed read-only and searchable.
The shift logEvery entry as written, the shorthand expanded beneath it, tagged and linked to its event and its brief item.
Search the log historyA plain-words question over twelve years of logs, handovers, permits and registers, answered with the entries it rests on.
The handover recordEvery signed handover by shift, coloured by items the note left out, what was added by kind, and the latest handovers.
Your rulesSources, what the brief holds, how far back the history goes, and who signs.
Governance

Built for safety-critical handover: cited, read back, signed.

Every line cites its sourceA line without a log entry, alarm, permit or register line behind it never reaches the brief. Every answer from the log history quotes the entries it rests on.
The log is quoted, never editedEntries stay exactly as the operator wrote them, shorthand and all. The log reader expands and tags them alongside; nothing in an entry is ever changed.
No switching advice from any agentNo agent recommends switching, isolating, earthing or re-energising. The precedent finder names the approved procedure and the person who decides — after a Buchholz trip, the protection engineer's release under OP-TX-07.
Read back, signed, countersignedThe incoming operator acknowledges every item before accepting the shift; the outgoing operator signs and the shift supervisor countersigns. Only the outgoing operator can remove an item, with a reason.
Read-only on the systems of recordThe permit system stays the record: nothing here issues, changes or cancels a permit. The register is flagged, never changed — the shift supervisor changes it.
Every step on the audit trailEvery acknowledgement, signature, search and agent run is recorded with its time. Signed handovers are kept read-only and searchable for 7 years.
Configuration

Your control room's handover rules, not ours

What the brief reads, what it holds, how far back the history goes and who signs are settings, chosen by the control room.

SettingDefaultChoose from
Brief ready before handover30 min15 min · 30 min · 45 min before 07:00 and 19:00
Mark what the note left outOnOn · Off — amber “Added from the log” on items missing from the outgoing note
Removing an itemOutgoing operatorOutgoing operator · Supervisor — always with a reason
Years searched125 · 12 · All
Minimum match60 %50 % · 60 % · 70 % — matches below the score are hidden
Always show a different endingOnOn · Off — the closest match that ended differently
Work before the event7 days3 · 7 · 14 days of the permit system checked
Signatures2 + countersign2 + countersign · 2 — every item acknowledged before the incoming operator signs
Connections

Works with the records a control room already keeps

Network logoperator log entries on every desk, in the operators' own shorthand
SCADA alarm listalarms and alarm summaries, standing and cleared
Permit systempermits to work, sanctions for test, limitations of access and earths — read only
Abnormal-network registerevery part of the network not in its normal state, since when, by whom and under what
Load forecast and weather warningstransformer loading at the evening peak, storm warnings for the shift
Log historyyears of past log entries, signed handovers, permits and register lines
What it changes

The difference, in numbers.

Every figure is labelled: a target the solution is built to, an estimate, a typical published result, or a proven one.

target
0
earths, permits or changed settings missed at handover
15 of 15 read back
every item acknowledged by name
target
30min
off restoration on a repeat event: how it was handled last time, found in seconds
Worked out at 04:00from scratch
With the precedent2.8 s to find
target
12years
of control-room log memory searchable in plain words, as experienced operators retire

“demo” = seen in the working solution, on its sample control-room data · “target” = the design goal, measured in the live solution · “estimated” = our estimate · “typical” = published figures: Lord Cullen, The Public Inquiry into the Piper Alpha Disaster (1990) — 167 deaths, a permit's status not handed over at shift change; AWWA 2025 benchmarking — 21 % of water-utility staff eligible to retire within five years. Context: UK HSE and Energy Institute guidance on safety-critical communication and shift handover; NERC COM-002-4 (three-part communication for operating instructions). Lumina Utilities, its control centre, substations, circuits, permits, records and the people named on this page are fictional — characters and sample data in the working solution.

Questions

What control rooms ask about shift handover software.

What is control room shift log software?

Software that turns a control room's free-text operator log into a structured shift handover and a searchable history. Control Room Shift Log reads the night's log, SCADA alarms, permits, earths and the abnormal-network register into a one-page brief with every line cited, marks what the outgoing note left out, and answers questions over years of past logs.

How does the shift handover brief work?

Thirty minutes before 07:00 and 19:00, the agents read the shift's sources and the handover writer builds the brief in five sections: open faults, network not in its normal state, permits and earths in force, temporary settings and watch this shift. The outgoing operator reads it back, the incoming operator acknowledges each item, both sign and the shift supervisor countersigns.

How does “has this happened before?” search past control room logs?

The precedent finder matches on the asset, the protection that operated, the work done just before and the alarm sequence, across the log history — 186,240 entries since 2014 in the working solution. It quotes the old entry as written, replays what the operator did then with times, lays then beside now, and always shows the closest match that ended differently.

Does it tell operators what to switch or when to re-energise?

No. No agent recommends switching, isolating, earthing or re-energising. It shows what was done before and how it ended, and names the approved procedure and the person who decides — after a Buchholz trip, the protection engineer's release under OP-TX-07.

Does it replace our permit system or the network management system log?

No. It reads them. The permit system stays the record and nothing here issues, changes or cancels a permit; the register is flagged, never changed; and log entries are quoted as written, never edited.

Do operators stay in control of the handover?

Yes. The incoming operator cannot accept the shift until every item is acknowledged. Only the outgoing operator can remove an item, with a reason. Every acknowledgement, signature, search and agent run is on the audit trail, and signed handovers are kept read-only for 7 years.

Can we set our own handover rules?

Yes. Which sources the brief reads, how long before handover it is ready, whether missing items are marked, who may remove an item, how many years of logs are searched, the minimum match, the look-back for work before an event, the signatures and how long handovers are kept are all settings.

How long does it take to go live?

The Agentic Solution Engine builds and deploys it from your requirements and documents — your handover template, desk glossary, permit and register extracts and a sample of past logs — and it goes live once every quality gate has passed. We will walk you through it on your own shift logs first.

See it on
your shift logs.

We'll run Control Room Shift Log on a sample of your own logs, alarms, permits and register.