EVERY CURRENT UNDER LIMIT · NOTHING ALARMING
One of these sixteen panels is running badly out of balance — and because no single phase is anywhere near its limit, nothing has fired. Find the panel.
GRAYSPACE is the operations platform for facilities that can't go down — maintenance, rounds, incidents, procedures and live equipment data on one record.
Each of the next three is a shift that actually happens — an outage at 02:48, a hot hall at 06:15, a planned shutdown on a Tuesday. Play them. You do the operator's job, and you see exactly where the platform stands beside you.
The utility drops at 02:48. Everything downstream announces itself at once — generators running, UPS on battery, batteries discharging, cooling units restarting. Seventy-eight alarms in ninety seconds, and every single one of them is true.
Seventy-eight alarms land in ninety seconds. How many of them actually need you tonight?
One. Seventy-seven are the outage describing itself — expected, correct, and noisy. The seventy-eighth says a room has no generator behind it, and on screen it looks exactly like the other seventy-seven.
Every one of those alarms fired correctly. That is the problem: a queue can tell you what happened, but not which one ends the night.
A CRAC supply-air alarm comes in at 06:15. The operator acknowledges it — and gets pulled into something else. The alarm is now silent, handled, off the board. Nothing about the room changed.
Acknowledged at 06:15, investigated by nobody. How long was that hall actually above its limit?
One hour and twelve minutes — and the only reason anyone knows that number is that the data was still there when someone finally looked. Drag the scrubber below and watch the morning happen.
Acknowledging an alarm is not the same as answering it. The round caught what the acknowledgement closed — and the trend was still there to prove how long it had been true.
The annual PM on PDU-4 needs the unit dead. Eight breakers, similar labels, one of them feeding a live hall. This is where a good night turns into an outage report — so the procedure runs on the screen, not on paper in someone's back pocket.
Eight breakers, one correct. What actually stops the wrong one being opened at 09:00 on a Tuesday?
A procedure that names the breaker and will not advance past it. Try it below — open any breaker you like. The step will tell you exactly what you are holding.
No wrong breaker was opened, and not because everyone was careful. Opening one was never something a single person could do — and the attempt, the two signatures and the timestamps are on the work order in the morning.
Not every team starts with live equipment data. Some start with documents, or a calendar nobody trusts. Twelve more, same idea — jump to whichever one is your Tuesday.
Find what a threshold can't. Each of these is a real thing that happens on a real floor — and what the system does about it.
Twelve people were assigned this procedure. Eleven days after it changed, how many are still working from the old revision?
Four — and one of them is a contractor on site tonight, holding a revision that isolates the wrong panel. Assignment isn't acknowledgement, so the system tracks both.
Version control isn't real until you can name the person holding the old one.
An operator hears a belt at 23:10 and writes it down. Where has it got to by the morning handover?
It became an exception against the asset, was carried into the shift handover automatically, and left as WO-4488 with parts checked and an owner. Nothing was remembered or retyped.
Nothing was remembered, retyped, or lost between two people at six in the morning.
Eighteen filters on the shelf at this site. How many of them will fit the unit that just failed?
None. All eighteen are 24×24×2 — CRAC09 takes 24×24×4, and that line is at zero, below its reorder point of four. The count was right. The part was wrong.
A count is not availability until you ask whether it is the right part.
A P2 incident is raised and nobody acknowledges it. How long until the operations director is told?
Thirty minutes, then the on-call engineer at forty-five. Escalation runs on a clock whether or not anyone remembers it exists.
Escalation runs on a clock — whether or not anyone remembers it exists.
DC-1 and DC-2 each booked ABB for their annual UPS preventive maintenance. What is the problem?
ABB has one crew and both sites hold them for the same Tuesday. One of those visits is not happening — and normally you find that out when nobody turns up. Vendor commitments are visible across every site, not one calendar at a time.
Vendor commitments across the whole estate on one view — so a vendor double-booked across two sites shows up weeks before the day.
The same sentence, sent two ways at 23:48. Which one still exists on Monday morning?
Only the linked one. It attached to UPS-A permanently, raised WO-4491, and appears at handover.
anyone still on site? UPS A is acting up
23:41yeah I'm here, having a look now
23:44left the interlock bypassed on UPS A, will sort it monday 👍
23:48👍
23:49anyone still on site? UPS A is acting up
23:41yeah I'm here, having a look now
23:44Left the interlock bypassed on UPS-A · ASSET — raising it now.
23:48seen it on the asset, thanks
23:49A decision that isn't attached to the equipment didn't happen.
Certification expiry is checked at the moment of assignment — for your staff and for the contractor you were about to call.
Four people could take an HV switching job tonight. How many are actually allowed to?
Two. One technician's certification expired sixty-two days ago and the contractor's vendor cert has lapsed. Expiry is checked at the moment of assignment, not at audit time.
Scope is resolved on the server for every request — and it fails closed, never open.
They open the site list. What do they see?
Only their own. The other three are not greyed out or hidden behind a disabled button — they are never in the data that comes back. And if the scope is ever ambiguous the resolver returns an empty set rather than everything, so it fails closed.
Captured offline, queued on the device, and reconciled the moment signal returns — nothing retyped at a desk afterwards.
A technician works three floors down with no signal at all. What happens to what they captured?
Queued on the device and reconciled the moment signal returns — readings, photos, parts and sign-off. Nothing is retyped at a desk afterwards.
We show you both and flag the divergence rather than quietly picking a winner — the reconciliation is your call, on your numbers.
The project says $340,000 committed. The purchase orders total $412,400. Which number do we show you?
Both, with the $72,400 divergence marked not reconciled. We won't quietly pick a winner — deciding which is right is your call, on your numbers.
Percentages are measured against hours we actually have data for, not the calendar month — so a monitoring gap can never read as compliance.
The monthly report says 94.2% of hours in band. In band as a share of what?
The 612 hours we actually have data for, out of 744. The 132-hour gap is disclosed, not assumed — so a monitoring outage can never quietly read as compliance.
Scan the label on the unit and its entire life is there. That single record is the reason any of the previous twelve was possible.
Telemetry, maintenance, documents, parts, rounds and incidents. How many separate systems is that?
One. They all hang off the asset record — and that is the only reason any of the previous twelve was possible.
A reading, a work order, a part, a procedure and a message all point at the same asset. That is the only reason any of the above was possible.
Built portable from the start. Pick one and see exactly what sits where — and what, if anything, crosses your boundary.
Your sites, your assets, your procedures — configured with your team, live in about two weeks.
Already using GRAYSPACE? Sign in →