SENSORLOGIX · OPERATIONS CONSOLE
One console for alerts, cameras and patrols
Built to what operators expect from a security operations or video management console: work the alert queue, watch the wall, run the incident and dispatch the patrol.
It works beside your sensors’ own consoles and supports your operators’ procedures, not in place of them. Use it where you have no console, or keep yours and take the same alerts into it.
THE CONSOLE
The alert, its map and its clip, side by side
Work a live alert queue by priority, with sound. Zones, sensors, boxes and tracks sit on a layered map, with the clip beside the alert.
NINE SCREENS
Each screen does one job
01
Operations console
Work a live alert queue: priority, sound, acknowledge, assign, snooze, escalate, note. See zones, sensors, boxes and tracks on a layered map, with the clip beside the alert.
02
Video wall
Watch 1, 4, 9 or 16 live tiles, page through saved layouts, follow alerts, hold a fixed camera for a short time, take snapshots, play back with alert markers.
03
Incidents
Group alerts, keep a timeline, notes and attachments, assign, dispatch a patrol through TAK or your dispatch system, track its state, export under your rules.
04
Zones
Draw the area, set the schedule and rules, see the sensors, test a rule against the last hour, run shadow mode.
05
Sensors and boxes
Keep the inventory: health, battery, firmware, location. Add and test a sensor; see a box’s streams, GPU, disk, link and events waiting.
06
Reports
Alerts by zone, class, hour and status; response times; false alarms per camera per day; sensor uptime; accuracy by class.
07
Notification rules
Decide who gets which alert, by zone, class and schedule, with escalation after a set time.
08
Shift tools
Saved views, keyboard shortcuts, handover notes, and an audit trail for each alert.
09
Recordings
Search clips across every box, and fetch footage from a box when you need it. Footage a box has already recorded over can’t be fetched, and the screen says so.
LARGE DEPLOYMENTS
Built for many sectors, teams and cameras
The screens stay usable as a deployment grows: you start on your own teams and widen the view when you need to.
- Teams and sectors. Real objects in the console. A scope control on every screen starts on your own teams, and shows what’s outside them when you ask.
- Lists that keep up. Every long list pages on the server, with saved views, bulk actions and export. Long pickers search.
- A map that stays readable. Marks cluster at any zoom, with roll-ups by sector.
- Floods, folded. A burst of alerts folds into groups, with a banner saying what’s driving them.
- A wall for each person. Up to 16 tiles, paged layouts and Follow alerts, with a cap on each person’s live tiles. Live video is sent only while someone watches.
- Footage on demand. Video stays on the boxes until an alert keeps a clip or someone asks for it in Recordings.
INCIDENTS
From the first alert to the closed incident
01
Group
Alerts about one event become one incident.
02
Record
A timeline, notes and attachments.
03
Assign
An owner, and a patrol.
04
Dispatch
Through TAK or your dispatch system.
05
Track
The patrol’s state, to closed.
06
Export
Under your rules, with its custody.
VIDEO WALL · 16 TILES · PAGE 1 OF 3
FOLLOW ALERTS: ON
ILLUSTRATION · HELD: MAST 3, UNTIL ITS OWN CONSOLE MOVES IT OR TIME RUNS OUT
VIDEO
Video stays on the box unless someone needs it
Live tiles stream while someone is watching. Otherwise video stays in the box’s rolling buffer, and only an alert’s clip is kept. On a thin link the box sends alerts first, and a live tile can be refused.
- Hold a camera from the wall. Take a fixed camera’s view for a short time, from its tile or from the alert. Its own console can take it back at any moment, and the hold ends by itself.
- Follow alerts. Turn it on, and the wall follows new alerts as they come in.
- Play back with markers. Each alert is marked on the timeline, and opens its clip.
- Snapshots with their record. A snapshot keeps its camera, time and alert.
- Saved layouts. A night layout, a gate layout, a layout per shift lead, paged when there are more cameras than tiles.
ONE HOLD PER CAMERAILLUSTRATION
Who comes first
- 1The camera’s own consoleAlways first. If it moves the camera, your hold ends at once.
- 2A console at the siteBefore any console at the rear.
- 3A rear consoleOnly if the site allows it, over a fast enough link.
HOLD · MAST 3 · 0:42 LEFT
It ends by itself when:
Time runs outYou leaveYour console stops answeringThe camera’s own console moves itONE API
Every screen is an API call
The console uses the same routes your developers get, so your own dispatch system or wall can do what it does.
Already run a video management system? Keep it: alerts reach it by webhook or through the alert stream, and the console serves the sites that have none.
SensorLogiX for developersSee your own zones on the console
Bring a site plan and the cameras on it; we’ll show the queue, the wall and an incident on them.