mystique

Mystique for critical infrastructure and utilities

The network keeps running.
The control room stays in charge.

Substations, pump stations, treatment works and every link between them, run as one system, with every operation on the record.

Briefed for critical infrastructure and utilities: assets, controllers, networks and what stays with the control room.

The problem

In your words.

Assets spread across a region.

Dozens of unmanned stations, a thin crew, and a truck roll for every question.

Alarms, not answers.

One event becomes fifty alarms. The one that matters is buried in the middle.

A bad command is worse than none.

The equipment is old, the consequences are public, and the control network is rightly kept apart.

Regulators want the record.

Not a summary: what was seen, what was decided, who decided it, and when.

The outcome

What changes.

Problems found before they trip.

Drift is caught days early, while it is still a work order and not an outage.

Fewer wasted truck rolls.

Crews go where they are needed, in the right order, with the fault and the history in hand.

One event, one alarm.

The control room sees what happened, not fifty symptoms of it.

An audit trail that writes itself.

Every reading, decision and action is recorded, ready for the regulator.

How it gets there

Sense, decide, act.

Built from the equipment and systems you already run. What Mystique cannot see, it will not touch.

01It would sense
  • Controllers, historians, meters and protection relays, read over the connections you already have.
  • Cameras and access control at unmanned stations.
  • Weather, demand and the state of the network around each asset.
  • Slow drift: the pump that takes a little longer each week.
02It would decide
  • Which alarms are one event, and what the event is.
  • What is drifting toward a trip, days before it does.
  • Which crew goes where, in what order.
  • What it may adjust within your approved limits, and what it must raise.
03It would do
  • Adjusts setpoints within the limits you approved, and logs each change.
  • Opens the work order with the fault and its history attached.
  • Dispatches the crew and briefs them on the way.
  • Keeps the record for the control room and the regulator.

What stays human

Consequence requires a person.

The system finds, tracks and recommends. These decisions are brought to a person, with the picture and the reason, and the system waits.

  • Switching and isolation.
  • Anything that touches a protection scheme or public safety.
  • Any setpoint outside your approved limits.
  • Spending beyond the limit you set.

Your constraints

What we build for.

Separated control networks.

It lives on the operational network, beside the equipment, with no dependency on the corporate side or the internet.

Remote assets with no link.

Each station keeps sensing, deciding and recording on its own when the wide-area link is down, and syncs when it returns.

Equipment from several decades.

Read where it stands. Nothing that works is replaced to make the system possible.

Audit.

The record is written for the person who reads it after an incident.

The full security and control position is on the core page.

An example

What it looks like.

Example · illustrative, not a client

A water utility with twenty unmanned pump stations. Mystique reads each station's controller and meters, tells a pump wearing out from a pump working hard, holds pressure within the approved limits on its own, and raises anything beyond them to the control room with the history. Valves are still operated from the control room, as before.

Built to order

What should
Mystique see?

The lab's agent arrives briefed for critical infrastructure and utilities. Talk by voice or text and it will write up the brief and book you in, or book the call directly.

DefenseInfrastructureManufacturingLogisticsCommerceAgricultureEnergy