Operations & commissioning
The electrical sequence of operation, and how to write one that survives commissioning
Every switchboard schedule says what the plant is. The sequence of operation says what it does — event by event, device by device. It is the document the integrated systems test is written from, and the one most often produced last, by hand, from a drawing that has since moved on.
What the document is for
Three different readers need it, and they need the same facts for different reasons.
| Reader | What they take from it |
|---|---|
| The commissioning agent | The test script. Each case becomes a witnessed test with a pass criterion that was agreed before anyone arrived on site. |
| The operations team | What is supposed to happen at 03:00, so an operator can tell a correct automatic response from a fault in progress. |
| The client’s reviewer | Evidence that the topology on the single line actually delivers what the design brief claimed, under the events the brief named. |
The four things each case has to state
A case that leaves any of these out cannot be tested, which means it cannot be argued about before the test either.
- The cause. One event, stated plainly: utility A lost, transformer TR-1 faulted, Q-A1 opened for maintenance, EPO pressed. Not two at once unless the case is deliberately a double contingency, in which case say so.
- The state of every device afterwards. Not only the ones that move. A sheet that lists five breakers out of sixty is silent about the other fifty-five, and silence is where disagreements live. Four states cover it: ON, OFF, FAULT, ISOLATION.
- The time the plant takes to settle. A generator reaches rated speed and voltage in roughly ten seconds; a UPS carries the load meanwhile. A case judged at t = 0 and a case judged at t = 900 s are different cases. State the settle time.
- The redundancy left afterwards. The load being carried is the minimum bar, not the result. What matters commercially is whether the facility is still concurrently maintainable with one source gone — or whether it is now one event from going dark.
A case, written out
A 2N facility, 400 kW of IT load on two cords, two utilities, two generator sets and a normally open tie. The case is the loss of utility A.
| Field | Entry |
|---|---|
| Case | 03 — Loss of utility A |
| Cause | Incoming supply A lost at the MV intake |
| Expected action | MSB-A loses its source; UPS-A rides on battery; GEN-A starts on load demand and takes MSB-A through Q-G1 |
| Settle time | 900 s |
| Q-A1 (utility A incomer) | OFF |
| Q-G1 (GEN-A set breaker) | ON — closed at t ≈ 12 s |
| Q-T1 (bus tie) | OFF — remains open; the tie is not the design’s answer to this event |
| Q-B1 (utility B incomer) | ON — unchanged |
| UPS-A | On battery 0–12 s, then mains, recharging |
| Result | IT load 400 kW carried throughout; no load on battery at settle |
| Residual redundancy | Side A on generator, side B on utility. Still concurrently maintainable; fault tolerance reduced while GEN-A carries A. |
Written like that, the case is testable. The commissioning agent can witness Q-G1 closing, time it, and read the UPS log for the battery discharge. Nothing is left to interpretation on the day.
The case list: what to include
A list of forty cases that all test the same path is worse than a list of twelve that each test a different one. Build the list from the plant, not from habit.
- Loss of each incoming supply, separately.
- Loss of each generator set while it is carrying load, and failure of one set to start.
- Each UPS to internal and to external maintenance bypass, and back.
- Each transformer and each main breaker out for maintenance — one at a time, which is the whole meaning of concurrent maintainability.
- Each distribution board isolated at its incomer.
- Loss of a cooling source: one chiller, one pump, one room unit — and the chilled-water pumps on the uninterruptible supply, if continuous cooling is claimed.
- EPO, and restoration after it.
- The double contingencies the brief actually names, labelled as such.
Four ways the document goes wrong
- It is written from the drawing by hand, once. The single line is then revised four times before issue. Nothing in the process forces the sheet to follow.
- Device designations do not match the drawing. The sheet says “generator breaker”; the drawing says Q-G1; the panel label says something else again. On site this costs hours.
- No settle time. The reader cannot tell whether “UPS on battery” is the expected intermediate state or the final one.
- The residual state is asserted, not derived. “Tier III maintained” appears under every case, including the ones where it is not true.
How to check a sheet you have been handed
Take three cases from the middle of the list and trace each one on the single line yourself, naming every device. If the devices in the sheet are not the devices on the drawing, or if two cases that start differently somehow end identically, the sheet was written from an idea of the plant rather than from the plant.
Play the sheet instead of writing it
Data Center Simulator holds the sequence of operation as cases against the design you drew. Name the cause, set which devices open and which components fail, and the engine plays the case over time: every Q device ends ON, OFF, FAULT or ISOLATION, the load is followed cord by cord, and the residual redundancy is reported against your target Tier. The sheet prints with the device designations from the drawing, because it is the drawing.
Download the free trial How the engine is checked