It runs on your incumbent VMS
Displacing Genetec or Milestone isn't the sale — correlating across them is. Your existing camera investment stays exactly where it is.
Unified Threat Engine
The cameras are already there.
Nothing reads them together.
Most sites have more coverage than they can use. Every feed raises its own alarms into its own queue, so a pattern repeating across four buildings reads as four unrelated tickets nobody connected. What follows is one night at a single site, from first detection to a sealed case.
Sold standalone. No OmniusGrid deployment required.
Live Threat Assessment
The score the whole estate is read by, on the engine's own 0–1 scale.
Live Threat Assessment
MINIMAL
Overall Threat Score0.23
System Connection
Connected
Last Update11:02:51 PM
The product's own markup and stylesheet — not a picture of it.
02:00Detection
What the site is watching for
Thirteen detection layers,
switched on per site.
Before anything happens, the site decides what it looks for. Licence-plate recognition and vehicle make/model through to aggression, weapons, drone, crowd, intrusion, fire and smoke — each toggled for the site it runs at.
LPR
License Plate Recognition
VMMR
Vehicle Make Model
Aggression
Violent behavior detection
Weapons
Weapon identification
Drone
Unauthorized drone tracking
Crowd
Crowd density analysis
Person
Person tracking
Vehicle
Vehicle tracking
Loitering
Loitering detection
Suspicious
Suspicious activity
Intrusion
Perimeter breach
Fire
Fire/Flame detection
Smoke
Smoke detection
Every layer feeds one clock. Whatever any of these catch lands on the same timeline as everything else, rather than in thirteen separate queues.
02:14 → 07:00One clock
The night, as it happened
Four lanes,
one clock.
Audio, video and sensors on a single axis, and a fourth lane carrying what the engine fused out of them. The scrubber runs the night back: unauthorised entry at the substation yard at 03:38 and Transformer T2's partial-discharge rise at 03:49 sit eleven minutes apart on the same line, which is what makes them one story instead of two tickets.
02:0003:0004:0005:0006:0007:00
AudioAcousticTurbine 3 bearing whineAcousticFeedwater pump cavitationAcousticConveyor C-7 idler squeal
VideoVideoPPE breach — Line 3 guardingVideoUnauthorised entry — substation yardVideoFurnace 1 flame instabilityVideoTanker at loading gantryVideoPatrol pass — logged
SensorSensorSwitchgear arc-flash precursorSensorTransformer T2 partial dischargeSensorCNC Mill #1 spindle 7.8 mm/sSensorCooling tower fan imbalanceSensorCompressor discharge overtemp
UnifiedFusedSubstation intrusion + PD riseFusedBearing wear — asset-8
minimallow · 0.3medium · 0.6high · 0.8critical · 0.915 events · 3 modalities · fused into one
Fifteen events, three modalities, one fused lane. Click any blob for its confidence, model, latency and impact score. A single-site detection vendor shows you three lists and leaves the correlation to whoever is on shift.
03:41Action
What the site was allowed to do
Call-of-Action and Rules-of-Engagement,
as a working board.
The column a card lands in is derived from the UTS score, not chosen by hand. Each carries its phases, the person responsible for each action, and the rule of engagement that governs it — including the one action the rules refused.
Suggested2
Thermographic scan — Transformer T2
Partial-discharge trend correlated with acoustic rise.
›1 phases · 0 complete
Scan bushings and radiators · Reliability tech
ROE · No de-energisation without grid consent
Re-run PD trend against 90-day baseline
Confirm whether the rise is drift or a step change.
›1 phases · 0 complete
Pull historian trend · Condition monitoring
ROE · Baseline exports retained 30 days unless attached to a case
Pending2
Isolate switchgear bay 4
Arc-flash precursor detected; bay carries the substation yard feed.
›3 phases · 1 complete
Confirm load transfer path · Grid controller
Rack out bay 4 breaker · HV authorised person
Post danger notices · Safety officer
ROE · Switching above 11 kV requires two authorised persons
Pull loading-bay acoustic 03:15–03:25
Forced-fixture signature, +6 dB over ambient.
›2 phases · 0 complete
Export mic-01 segment · Audio analyst
Run tamper check · Audio analyst
ROE · Audio exports must be hash-chained before review
In Progress2
Dispatch technician to substation yard
Unauthorised entry validated across video and access control.
›3 phases · 1 complete
Dispatch nearest patrol · Guard 2
Secure yard gate · Guard 2
Log incident to case file · Night supervisor
ROE · Observe and report only — escalate above UTS 0.90
Progress60%
Derate CNC Mill #1 spindle
Vibration 7.8 mm/s against a 4.5 threshold.
›3 phases · 1 complete
Notify Line 3 supervisor · Ops lead
Apply 15% RPM derate · Controls engineer
Schedule bearing replacement · Planner
ROE · Derate requires ops-lead sign-off before shift change
Progress35%
Completed2
Lock substation perimeter gate
Executed 03:41, confirmed by the night supervisor.
›2 phases · 2 complete
Engage maglock · Guard 1
Confirm lock state in ACS · Security desk
ROE · Perimeter gates fail open on fire alarm
Progress100%
Notify shift engineer
Acknowledged at 03:39.
›2 phases · 2 complete
Send page · Automated
Record acknowledgement · Automated
ROE · Critical events page the on-duty engineer within 60 s
Progress100%
Rejected1
Estate-wide load shed
Declined — outside the rules of engagement for this tier.
›2 phases · 2 complete
Assess estate-wide risk · Grid manager
Decision: decline load shed · Grid manager
ROE · Requires UTS above 0.95 and executive sign-off
Estate-wide load shed was declined. Not forgotten, not quietly executed — refused on the record, because it needs UTS above 0.95 and executive sign-off. Open a card to see its actionables and the rules that govern them.
06:12The morning after
The part nobody demos
An incident becomes a case,
one step at a time.
The other half of the job is the case record. The Case Constructor builds it in the open — sector, category, the pipeline that category implies, the case details, the tools it will run with, and the evidence attached to it. Every pane below is that screen, isolated.
Every case starts with a sector.
Ten of them, each opening its own categories and investigation protocols. An operator hurt at a press is Industrial — manufacturing, chemical plants, refineries and mining.
0
Select Sector
Selected: Industrial
Manufacturing, chemical plants, refineries, and mining operations
1
Select Case Category
Select Case Category
4 Categories
1 Selected
Workplace Safety Incidents
Selected
OSHA violations, workplace accidents, injuries, and safety protocol failures.
Case Typologies:
2 Available
WSI-01: Workplace Safety Incident Investigation
4 Indicators
WSI-02: OSHA Violation Investigation
4 Indicators
Case Types:
8 Types
OSHA Violations
Workplace Accidents
Injury Incidents
Cross-links:
4 Links
OSHA
Workers Compensation
Equipment Failures & Malfunctions
Equipment breakdowns, production line failures, maintenance issues, and system malfunctions.
Case Typologies:
3 Available
EF-01: Equipment Breakdown Investigation
4 Indicators
EF-02: Production Line Failure Investigation
4 Indicators
Case Types:
8 Types
Equipment Breakdowns
Production Line Failures
Maintenance Failures
Cross-links:
4 Links
Maintenance Teams
Equipment Manufacturers
Environmental Incidents
Chemical spills, emissions violations, environmental compliance, and hazardous material incidents.
Case Typologies:
3 Available
EI-01: Chemical Spill Investigation
4 Indicators
EI-02: Air Emissions Violation Investigation
4 Indicators
Case Types:
8 Types
Chemical Spills
Emissions Violations
Waste Disposal Issues
Cross-links:
4 Links
EPA
Environmental Services
Quality Control & Product Issues
Defective products, recalls, quality failures, and manufacturing defects affecting product safety and compliance.
Case Typologies:
3 Available
QCI-01: Product Recall Investigation
4 Indicators
QCI-02: Manufacturing Defect Investigation
4 Indicators
Case Types:
8 Types
Defective Products
Product Recalls
Quality Control Failures
Cross-links:
4 Links
Quality Assurance
Customer Service
Subsystem Details
2 Typologies Available
Pipeline Active
Case Typologies
0 Applied
0 Running
2 Ready
WSI-01Workplace Safety Incident Investigation
Comprehensive investigation of workplace safety incidents including OSHA violations, accidents, injuries, and safety protocol failures.
▶ Ready
4 indicators
4 methods
4 evidence
Comprehensive investigation of workplace safety incidents including OSHA violations, accidents, injuries, and safety protocol failures.
WSI-02OSHA Violation Investigation
Investigation of OSHA regulatory violations including citation responses, compliance audits, and safety standard enforcement.
▶ Ready
4 indicators
4 methods
4 evidence
Investigation of OSHA regulatory violations including citation responses, compliance audits, and safety standard enforcement.
Investigation Pipeline Configuration
Configure the analysis pipeline for this investigation
0 Enabled
0 Configured
Pipeline Active
Data Sources
Select data sources for analysis
○ Pending
Analysis Methods
Configure analysis techniques
○ Pending
Evidence Containers
Configure evidence handling
○ Pending
2
Case Details
Provide the basic information for your investigation case.
Case Details
3
Investigation Tools
Select the tools and analysis methods you want to include in this case.
Investigation Tools
Vehicle Search
Search for vehicles by license plate, make, or color
Audio Analysis
FLAGSHIP Audio Intelligence Engine - G-Host and MAIA integration for comprehensive audio forensics, deepfake detection, and investigative analysis
V-Print (TM) Transcription
Load audio files and transcribe with V-Print (TM) AI
Behavior Analysis
Detect suspicious movements and behavioral patterns
Cross-Camera Analysis
Track movements across multiple camera feeds
Sensor Correlation
Correlate sensor data with audio/video events
Timeline Reconstruction
Build comprehensive event timelines
4
Evidence & Files
Upload evidence files, documents, or media related to this case.
Evidence Container
Evidence Items
0 items
No evidence items added yet
Click "Add Evidence" to get started
Evidence Items
1 items
Die-area CCTV — 14:07:22, light curtain muted
Video Evidence
pending
Add Evidence
Case Summary
Sector:Industrial
Category:Workplace Safety Incidents
Case Number:ACC-2026-114-007
Title:Press line 4 — operator injury at an unguarded intervention
Assigned To:R. Okafor · EHS lead
Priority:medium
Tools Selected:4
Nothing here is a mock-up. Each pane is the Case Constructor's own interface, captured from the dashboard with the wizard walked through end to end.
UnderneathConfiguration
How the engine is put together
The engine is a graph you can open,
not a sensitivity slider.
Collectors, processors and outputs are nodes on a canvas. Each reports its own throughput and latency, the processor fuses them, and the output node carries the score every other surface reads. Add a modality and you add a node.
5 nodes • 4 connections
Configuration:
Zoom:
100%
Awaiting telemetry
Awaiting telemetry
Awaiting telemetry
Awaiting telemetry
output
UTS Output
System:UNKNOWN
0.0%
Threat Score
MINIMAL
Connection:Disconnected
Total feeds0
Active0
Alert0
Error0
Intelligence Scores:
System Load:0%
Detections:0
Avg Confidence:0.0%
Correlations:0
Last: 12:41:54 AM
Routed Feeds0
No feeds connected
audio
Audio Source 1
Status:STANDBY
Throughput2.1 Mbps
Latency12 ms
Last: 12:41:50 AM
Net: no dataDetect: no data
video
Video Source 1
Status:STANDBY
Throughput24 Mbps
Latency38 ms
Last: 12:41:53 AM
Net: no dataDetect: no data
sensor
Sensor Source 1
Status:STANDBY
Throughput0.4 Mbps
Latency6 ms
Last: 12:41:49 AM
Net: no dataDetect: no data
processor
Processor 1
Status:STANDBY
Throughput26 Mbps
Latency44 ms
Last: 12:41:52 AM
Net: no dataDetect: no data
Eight source types in the library. Adding audio to a video-only platform is a rebuild; here it is a node.
Correlation resolves upward
Three tiers, each seeing further than the last.
The same feeds, read at three heights. Most vendors stop at the first one.
Tier 1
Smart detection, per feed
PPE compliance, safe human-machine interaction, restricted-zone and trespass monitoring, person and vehicle tracking, licence plate. Then aggression, weapon and crowd-surge detection on the same cameras.
200+ detection types750+ detection components<100 ms detect to responseDigital PTZ tracking, PID control
Tier 2
Site correlation
Every feed at one site resolved into a single incident rather than a queue of separate alarms — running over the VMS you already have, Genetec or Milestone, rather than replacing it.
Runs over Genetec / Milestone1,000+ concurrent sensorsLive video, HLS streamingMulti-protocol IoT intake
Tier 3
Estate correlation
The whole estate at once, so a pattern repeating across four buildings reads as one campaign rather than four tickets nobody connected. A single-site detection vendor cannot do this.
Self-healing event busPredictive & geospatial analyticsEstate-wide threat scoringAuto-scaling, heartbeat failover
ComplianceSOC 2 · GDPR · HIPAA
ArchitectureZero-trust
Scale1,000+ sensors, auto-scaling
ResponseSub-100 ms
The same discipline, different stakes
What carries over from the operations engine.
Evidence lineage, the causation guardrail, human approval and the hash-chained audit trail are properties of the engine itself, so this layer inherits all of them. In operations that discipline settles an argument. Here it is what lets a record survive a legal challenge, an insurance claim or a public-records request.
It feeds operations, if you run both
What the cameras and sensors resolve becomes part of the operational picture in OmniusGrid. Same building, same vendor, no second integration.
Unified Threat Engine
Bring us one night your team
had to reconstruct by hand.
An incident that took someone an afternoon of scrubbing four camera systems to piece together. That's the thing worth showing, and it's the fastest way to see whether correlating across your estate is worth a budget line.