UtiliSys™

Who it's for

Built for whoever answers for the operation.

The control-room operations and reliability lead comes first. Operations, technology, compliance, and OT security each query the same reconciled record for their own answer.

A technician in a hard hat checking wiring inside a relay control cabinet.

The seats

The question each seat actually asks. 

Different chairs, different first question. Each is answered from the same reconciled, sourced record.
Marcus HaleControl room · operations & reliability
When everything trips at once, can I trust what I'm seeing?
You live in SCADA and HMI and the systems around them, and during an event you hand-assemble the truth across the historian, GIS, and asset records. UtiliSys™ reconciles that into one sourced picture, so the shift is analysis, not assembly.
  • Sequence-of-events reconstruction in minutes, each step sourced
  • One resolved identity and timeline across SCADA, historian, GIS
  • Bi-temporal validity: a stale value never overrides a current one
Ken OyamaTechnology · CIO / CTO
Is this another AI pilot that never ships?
AI stalls in pilot when it runs on fragmented, unsourced, un-timed data. UtiliSys™ grounds the record first (identity, time, provenance), so models built on it survive production.
  • A provenanced, bi-temporal record under every model
  • Read-only, one way out of OT; no new write path
  • Vendor-neutral reconciliation across your existing stack
Erin WalshCompliance · regulatory
When the auditor asks, can we prove what was true, and when?
An audit or investigation lands and evidence is scattered across logs, spreadsheets, and email. UtiliSys™ holds a queryable, sourced trail tied to what was true at the time.
  • Provenance and timestamp on every fact
  • Bi-temporal history: superseded facts retained, not deleted
  • Evidence assembled by query, not weeks of manual export
Tom RiveraOT security · SCADA engineer
What new way into OT does this open?
You approve any new read path out of OT. UtiliSys™ ingests read-only from the historian at the DMZ, aligned with the data-diode and unidirectional-gateway pattern, so it adds no write path.
  • Read-only, one-way-from-OT ingestion at the DMZ
  • Aligned with the data-diode and unidirectional-gateway pattern
  • No control path; the Execute step is always a handoff

Industries

Grounded in the physics of your network. 

A generic tool treats a feeder and a regulator station as the same abstraction. UtiliSys™ carries the model, ontology, and regulatory context of each network it reads, all of it read-only.

Electricity · transmission and distribution

Electric utilities

Reliability, DER growth, and asset risk reconciled in one constraint-aware model, read-only.

Grid reliability

Rank the interventions that move SAIDI and SAIFI, weighted by customer consequence, then hand the ranked plan to the owner.

Load forecasting

Feeder-level load forecasts that take in weather, DER output, and electrification, each with a confidence score.

Asset monitoring

Transformer, breaker, and recloser health scored continuously from telemetry and work history.

Outage intelligence

Correlate alarms, AMI signals, and crew reports into one restoration picture, sourced end to end.

Gas · distribution

Gas utilities

Integrity management and predictive maintenance under strict regulatory obligation, evidenced continuously.

Pipeline integrity

Fuse inspection history, cathodic-protection data, and pressure behaviour into segment-level risk.

Predictive maintenance

Rank regulator-station and valve work by failure probability and consequence; a planner approves.

Leak survey

Target survey routes where risk-adjusted detection value is highest.

Compliance evidence

Assemble integrity-management documentation continuously, not at audit time.

Talk to us

Whichever seat is yours, it answers for it. 

Bring the question your chair asks first. We will show you what a sourced answer looks like. One working session, no commitment.