Skip to main content

Locate every alert in 3D space

Real-time metric mapping, rule-based alerts, video and work-order linkage

We map key metrics to the model in real time, position threshold and rule alerts in 3D space, and link them to video, work orders and emergency plans. Where an alert list only says what went wrong, the twin shows where and what is around it, so response begins the moment an alert appears.

Our approach

One team scopes, executes and retests; conclusions are delivered as evidence, not checklists.

01

Every alarm rationalised to ISA-18.2

Each alarm is reviewed with site operators and documented with cause, consequence, operator action and allowed response time. Conditions without a defined action are not configured as alarms, so every alarm presented to an operator requires a response.

02

Linkage through existing systems

Video, work orders and emergency plans are triggered through interfaces to the client's existing systems, which are not rebuilt. Existing processes and permissions remain unchanged; the twin adds spatial location and relationships.

03

Video wall and workstation views designed separately

The command wall emphasises situation and anomalies; workstation views emphasise equipment detail and actions. Each purpose has its own interface: commanders maintain the overall picture, and operators go directly to the equipment they are responsible for.

Deliverables

01

Real-time monitoring views

3D monitoring interfaces for video wall and workstation, metric panels and layer configuration. End-to-end latency from collection to screen refresh is measured at acceptance against the targets agreed at requirements stage.

02

Alarm list and linkage configuration

A rationalised alarm list (cause, consequence, action, priority, response time), suppression and escalation rules, and interfaces to video, work orders and emergency plans.

03

Alarm performance baseline and operations manual

Trial-period alarm rates, flood periods, and frequent and standing alarms, recorded as the baseline for later tuning; plus documentation for rule maintenance, view configuration and linkage interfaces.

How we deliver

Four stages, each with defined inputs, outputs and a client sign-off.

01Weeks 1–2

Requirements and rules

Monitored objects, alert rules, linked systems and interfaces.

02Weeks 3–4

View and linkage design

Interface prototype review, interface design.

034–8 weeks

Development and integration

View development, rule configuration, linkage integration.

042–4 weeks

Trial operation

Parallel run with the site, rule tuning, go-live.

Frequently asked questions

Notes on scope, execution and delivery standards. Contact us for anything not covered here.

Collection to model refresh is typically seconds, depending on sampling rate and network. Key metrics can be sampled faster; targets are agreed per use case and measured at acceptance.

Start from where you stand

Security, data and AI each start with a review of where you stand. The report and its findings are yours, whether or not the engagement continues.