Three agents, a queue and a record.
CompliSight, the product behind GuardianEye, is organised the way a site is: rules grouped into agents, every detection into one ticket queue, every ticket into one record.
Where the rules live.
FacilityWatch
Fixed cameras on the floor. PPE Sentinel, ZoneLock, CraneShield, SlipGuard, SmokeAlert, UnloadSafe.
DriverGuard
Vehicles and the people operating them. SpeedWatch, BeltCheck, PhoneAlert, FatigueSense, GeoTrace, MotionTrack.
FSRGuard
The audit programme itself. TAPA FSR clause mapping, gap and drift detection, audit and SCAR tracking.
What the team opens every day.
AlertFlow
The ticket queue: ID, severity, status, assignee, location, module, incident evidence.
CompliReport
Audit reports from the record, not from a spreadsheet.
CompliAgent
Plain-language questions about your own site.
Escalation & roles
Notifications, auto-escalation by severity, and who is who.
Compliance certificates
Generated per site from the retained record.
The record
What is kept for every event, and why review is part of it.
The six rules most sites start with.
Deployment, briefly
The product analyses approved CCTV feeds already in place; inference runs on distributed nodes whose status the team can see under live monitoring. Users sign in through enterprise identity, sites are separated as tenants, and the record behind every ticket is held in CloudSeals’ Evidence Fabric. Where services run, who can see what and how long data is kept are agreed per engagement in a security review, not assumed here.
Start with one site.
A site assessment looks at the cameras you have, the rules that matter on your floor and how the evidence would reach your auditor. Twenty minutes to find out whether it fits.