ZANUS AI FOR ENERGY & UTILITIES — GRID DOCUMENTS

Grid knowledge that outlives retirement.

One-line diagrams, as-builts, relay settings memos, equipment manuals, pole inspection records, easement files — loaded into curated libraries the AI reads from. Ask in plain language; get the answer with the source document cited, scoped to whoever asks.

Get started

Private tenant or your own server · unlimited users · critical-infrastructure-conscious architecture

Grid document libraries with priority order

Libraries: current as-builts outrank superseded drawings, issued settings outrank study drafts — you set the order.

What it does

Any format, including drawings and scans

PDFs, scanned as-builts, settings sheets, photos from the field, decades-old typewritten memos — the ingestion pipeline turns what the utility holds into queryable knowledge.

Answers with the source

No source in your library, no claim: the AI cites the drawing, the memo, the manual — or says it cannot answer. On a grid, a guessed setting is not an option.

Permission-shaped answers

A CSR asks about a rebate program; a relay tech asks about settings history: each gets answers scoped to their role, enforced server-side, redacted at the field level.

“Why is feeder 14 configured that way?”

The answer lives in a 2004 memo written by an engineer who retired in 2019. Loaded into the libraries, that memo now answers the question in seconds — with the document attached — for every operator who will ever wonder again.

Plain-language questions across decades of records
Sources attached to every answer
Priority order: current documents rule, superseded ones outranked

Precision vector store answering from grid documents

Utility software is procured in multi-year cycles, priced per module and per operator seat — while the control room still calls the one retired engineer who remembers why feeder 14 is configured that way. Zanus AI: customer notices AND the operations back office, unlimited users at one flat price — in an isolated private tenant or air-gapped inside your own perimeter.

Questions, answered

Who can see the operational drawings?

Only roles you authorize. Permissions reach the field level and the server redacts what a user cannot see — contractors get their scope, not the network.

Do our documents train outside models?

Never. Your tenant is isolated; your grid documentation is yours alone — and the air-gapped on-premises option keeps it physically inside your perimeter.

Grid knowledge that outlives retirement.

What it does

“Why is feeder 14 configured that way?”

Questions, answered

See it working on YOUR utility — the demo IS the product.