How LYT-X fits together
Existing subsystems keep running as they are. LYT-X normalises their events into a single model, applies rules and standard operating procedures, and presents one operating picture to the control room, the field and management.
Subsystems in, one operating picture out
Connected subsystems
- CCTV, VMS, DVR / NVR
- Access control & IAM
- Fire, intrusion, sensors
- Video analytics & AI
- Network & IT infrastructure
- Cybersecurity tools
- Building management (BMS)
- GIS, GPS & mobile assets
LYT-X core platform
- Protocol & API connectors
- Event normalisation & correlation
- Rule engine & alarm prioritisation
- Incident management & SOP
- E-Map, GIS & virtual matrix
- Logging, reporting & analytics
- User management & audit trail
- High availability & redundancy
Operations
- Control room workstations
- Video wall & decoders
- Guided SOP response
- Multi-agency coordination
- Mobile & remote access
- Management dashboards
- Compliance & audit reporting
- Field team notification
How an event travels through the platform
Collect
Devices, analytics and IT systems report events over their native protocol or API.
Normalise
Every event is converted to one common model and enriched with location and device context.
Decide
Rules correlate related events, filter false alarms and set the priority of the incident.
Act
The SOP opens with map, video and contacts; every action is logged for reporting and audit.
Six screens the operator works in
Representative interface layouts. Every screen shown here is assembled from the modules on this page — one event list, one map, one incident record, one audit trail.
From detection to resolution
Every alarm becomes a tracked incident record. Four statuses show where each case stands, and nothing is closed without a documented resolution.
ToDo
New events, prioritized by time and severity, waiting to be picked up.
Doing
Incidents actively being resolved under the SOP for that incident type.
Block
Held while awaiting external assistance from another agency or team.
Done
Completed and documented, with the summary form and evidence retained.
What the operator gets when an incident opens
Location on the E-Map
The incident and the devices around it, with alarm symbols and camera fields of view.
Video from the nearest camera
Live and playback at the time of the event, with export for evidence.
The SOP for that incident type
Step-by-step actions, true or false alarm confirmation and the resolution form.
Related events
Access records, sensor readings and system events correlated to the same case.
Contacts and channels
Who to notify and how: email, SMS, mobile app, intercom or public address.
A complete audit trail
Every action, timestamp and operator recorded for reporting and investigation.
One map, every device, every level
Interactive, layered maps in JPG floor plan, GIS, Google Maps, Mapbox, OpenStreetMap and GIS Offline formats — with alarm symbols, camera fields of view and real-time location tracking.
Multiple map formats
JPG floor plans, GIS, Google Maps, Mapbox, OpenStreetMap and GIS Offline in the same interface.
Layered, multi-level mapping
Layer devices by subsystem and move between building levels and city zones.
Device alert symbols
Alarm state is shown on the map itself, with customizable device positioning.
Camera field of view
See what each camera actually covers before dispatching or requesting footage.
Real-time location tracking
GPS-tracked mobile assets and field teams on the same operating picture.
Interactive control from the map
Live and playback video, I/O control, Telnet and SSH switch control, and API interaction.