CCTV & security

Connect Security Events With Facility Incident Management

A camera that records an incident nobody responds to has documented a failure. Integration is about turning detection into an owned response.

Request a Demo See Security & Safety

The business problem

Footage after the fact

CCTV is typically used retrospectively: something happens, footage is exported, and a report is written days later. Access events sit in a controller log with a different clock. There is rarely a single incident record showing detection, response and outcome together.

Cameras used retrospectively rather than operationallyAccess and video events on separate systems and clocksNo single incident record across sourcesResponse not evidenced at the time

The IntelliGrid approach

Security events as owned operational incidents

Where the security platform supports it, events and analytics detections are surfaced in IntelliGrid as incidents with an owner, a procedure and an escalation path. Related access events appear on the same timeline, and evidence is retained with the record.

Events surfaced as owned incidents with proceduresAccess and video events on one timelineResponse actions and timings recorded as they happenEvidence retained against the incident record

Privacy and compliance

Video and biometric capability is deployed only where lawful

Video analytics and any biometric or facial recognition capability are implemented subject to applicable privacy law, including PDPA obligations, and only where the building owner has established a lawful basis, notice and retention policy. Scope, retention and access rights are agreed contractually before such capability is enabled. Enquiries: privacy@intelligrid.asia.

Capabilities

Integration scope

Capability depends on the camera, VMS and analytics platform in use. No assumption is made that all brands or models are supported — scope is confirmed per site.

CCTV events

Camera and VMS events surfaced where the platform exposes them.

Video analytics

Detections from supported analytics platforms raised as incidents.

Incident creation

Events converted into owned incidents with defined procedures.

Response tracking

Actions, responders and timings recorded during the incident.

Evidence retention

References and exported evidence held with the incident record.

Camera health

Offline and faulty cameras raised as maintenance work.

Audit trail

Every action on a security incident attributable.

Workflow

Detection to review

STEP 1

Detect

Camera event, analytic detection or alarm.

STEP 2

Verify

Assessment against video, access and sensor evidence.

STEP 3

Respond

Owned incident with procedure and escalation.

STEP 4

Record

Actions, timings and evidence retained.

STEP 5

Review

Post-incident analysis and procedural change.

Business benefits

Detection producing an owned, procedural response One timeline across video, access and alarm sources Response evidenced at the time rather than reconstructed Camera faults treated as maintenance work Clear governance around sensitive capability