HALDENSECURE ENERGY INFRASTRUCTURE
Halden Virtual NOC
HALDEN

VIRTUAL NOC

HaldenSECURE ENERGY INFRASTRUCTURERouted. Answered.

Virtual NOC

Routed. Answered. An alarm arrives already carrying its context, and a rule decides who is called.

HIGH
raised [TIMESTAMP] · site time
INV04 · [DC bus undervoltage]
Routed to [OPERATIONS ROLE] · by rule: high → on-call, every time
PartINV04 · TX4 · PV inverter, 4,200 kW
Reading[U_dc] V against [limit] V
Historysame fault [n] times in [period]
Last resolution[what was done] · [DATE]
SUGGESTED RESOLUTION · ASSISTED, MAY BE WRONG
[The assistant's reading of the context and the history. The routing above never depends on it.]
AcknowledgeResolve
These act on the alarm, never on the plant. Nothing here writes to the site.
A RULE, OR ASSISTED
Severity decides who is called. The rest is help, and it says so.
RULES

Severity decides who an alarm reaches. Escalation after [n] minutes without acknowledgement. A fatal or high alarm reaches a person every time, whether or not anything else about it is understood.

ASSISTED

The context from the twin, the correlation across alarms and the suggested resolution. They may be wrong, the card says so, and the routing never depends on them.

As it runs

The first line as it runs: the fleet at a glance, and the alarm list with its context.

The Virtual NOC overview on the lite platform: sites, headline readings and open alarms, on a demo site, synthetic day.
The alarm list: each alarm with its part, severity and routing, acknowledged or open.

What it is bought for

Two numbers you already track.

01

Time to acknowledge

How long until a person has the alarm. Routing by rule, with the context attached, moves it.

02

Time to resolve

How long until it is closed. The part, its history and the last resolution beside the alarm move it.

03

A managed first line

A service, not a feature. It sits on Observe and the Twin, and the first line is ours; the plant stays yours.