VERIFIEDSUBSTATION
Evidence infrastructure for utilities

Is this transformer decision decision-grade?

We install a read-only evidence layer beside your SCADA, historian, oil lab and maintenance systems — on your infrastructure, in your country. It takes copies; it never writes back.

Every value arrives in a signed batch, is answered with a receipt, and keeps its source, its timestamp and its quality for good. A corrected number never erases the old one.

So when you repair, replace or retire an asset, you can prove exactly which source data, which mapping and which named person produced that decision — to your own auditor, without us in the room.

Start with the six-week audit hello@verifiedsubstation.com
The three questions

Ask these about any single asset. Today the answers take days — and arrive as opinions.

1
Where did this number come from, and when?The record id, the source system, the extraction time and the signing key — not "the historian, I think."
2
Is this asset actually in trouble, or does it just look bad on one sensor?Every contributing value shows its quality — verified, stale, manual — before anyone acts on it.
3
Who decided to act on it, and who signed it off?A named person, in a role that permits it, with a different person acknowledging — recorded, not remembered.

The data already exists — in the historian, the lab, the monitors, the maintenance system, and in spreadsheets and phone messages. None of it carries its own proof, so every answer is reassembled by hand, by the one engineer who remembers.

One system, every utility

Built for utilities across the GCC — each one inside its own country.

Each utility is its own tenant: its own namespace, its own keys, its own ledger, on its own infrastructure. Nothing is shared between utilities, and nothing about one is visible to another.

United Arab Emirates DEMODemo Utility — UAE · 4 assets · 2 substationsAsia/Dubai · AED · DD/MM/YYYYOpen the demo tenant →
Sultanate of Oman DEMODemo Utility — Oman · 3 assets · 2 substationsAsia/Muscat · OMR · DD/MM/YYYYOpen the demo tenant →
State of Qatar DEMODemo Utility — Qatar · 3 assets · 2 substationsAsia/Qatar · QAR · DD/MM/YYYYOpen the demo tenant →

Evidence stays in-country. The only thing that leaves a utility is proof — receipts and hashes it chooses to hand over. This site publishes each tenant's public key — never a utility's reading. The demo exports are the one labelled exception, and they are synthetic.

Verify a record yourselfHow onboarding works
What we never do

Specific on purpose — this is what makes the rest credible.

No machine approves anythingThe approval endpoint refuses every machine — including ours — permanently and by design.
Nothing is written backRead-only toward SCADA, SAP and the protection path, on day one and forever. No control, no setpoints.
No AI health scoresWhere a value is derived, the rule that derived it is named and the calculation is replayable.
No cloud copy of your dataThe layer runs on infrastructure you control, in your country. The public internet never touches a live reading.

The first limit is enforced in code and covered by a test: the approval route answers every machine with 403. The second is a property of the code: it has no write path toward a source system. The last two are how the layer is deployed — on your infrastructure, in your country — and are written into the statement of work, not a policy document.

The words we use

A shared vocabulary, so a finding means the same thing to everyone.

DECISION-GRADEEvery input to a decision is present, attributed, in-date and of stated quality.
STALEA value past the freshness its own signal declares. It may still be shown — never silently trusted.
GAPAn input a decision needs that no system holds. Named, not papered over.
GATEThe pass/hold state computed from evidence — and the named human who may move it.
EVIDENCE ROIWhat one more test, sample or survey would add to decision-grade — priced before it is bought.

Start with the six-week audit.

One asset class · read-only · your own sample files · fixed fee. You keep the output — it is the requirements document for whatever comes next.

How the audit works →