GCXONE · Features

GCX AlarmView

Alarm Processing, AI Filtering and CMS Transport

Filtered. Verified. Delivered.

GCX AlarmView is the alarm backbone of GCX One. It receives every event a camera or sensor raises, classifies it, filters out what is not a threat, and transmits what remains to your monitoring platform. Its headline capability is NOVA99x, the AI filter that removes up to 99% of non-threatening activity before an operator sees it, with ZenMode organising and prioritising what is left. Transport is SIA DC-09 to any compatible receiver, or a REST integration for Evalink Talos.

Datasheet · v1.0 · verified 15 September 2026

How GCX AlarmView works. Step 1, Detect: Camera or sensor raises an event. Step 2, Classify: Real, false or technical, with the overflow guard. Step 3, Filter: NOVA99x removes up to 99% of non-threatening activity. Step 4, Prioritise: ZenMode orders what is left across sites and customers. Step 5, Transmit: SIA DC-09 or Talos, with a secure event link attached.

Key capabilities

Classifies every incoming event as a real alarm, a false alarm or a technical alarm before any human sees it
NOVA99x removes up to 99% of non-threatening activity, applied at service provider, customer, site, device or sensor level
ZenMode compiles what remains into one prioritised, reviewable view across sites and customers
SIA DC-09 transport to Amwin, Lisa, Immix or any compatible receiver, each signal carrying a secure event link
Event Overflow protection suspends a runaway device automatically rather than letting it flood the platform

Primary use cases

A monitoring centre losing operator attention to environmental false alarms
A service provider standardising noise control across every customer, with per-customer tolerances
Onboarding a large estate without the alarm volume destabilising the operation
Protecting SLA-backed response times when alarm volume is what puts them at risk

Performance at a glance

Up to 99%

Non-threats filtered by NOVA99x

Up to 60%

Low-priority alarms filtered by ZenMode

25 / 5 min

Overflow threshold per device

Levels filtering can apply at

The path of an event

Camera or sensor
Ingestion
NOVA99x classification
ZenMode prioritisation
DC-09 or Talos
Operator

Where noise is removed, and by what

Stage	What it removes	Where it runs
Camera analytics (IVS)	Environmental motion, before anything is sent	On the camera or NVR
NOVA99x	Non-threatening activity in the event itself	GCX AlarmView
Event Overflow	Everything from a device that has gone runaway	GCX AlarmView
ZenMode	Low-priority alarms, by demoting rather than discarding	Operator workspace

Architecture

The alarm backbone. GCX AlarmView connects Cameras and sensors, Recorders and panels, IoT and IO to Monitoring centre, Evalink Talos, Operators.

Measurable results

What reaches the operator. Non-threatening events reaching the queue: Without filtering 100, With NOVA99x As few as 1 — Up to 99%. Up to 60% Low-priority alarms demoted by ZenMode , Prioritised, not discarded. 25 / 5 min Event Overflow threshold per device , Adjustable per tenant. 5 Levels filtering applies at , Provider, customer, site, device, sensor.

Technical specifications

Event Types: Real Alarm, False Alarm, Tech. Alarm
Real Alarm: A genuine security event — motion, line crossing, intrusion — routed to the operator queue
False Alarm: Non-threatening activity, filtered out and retained for reporting and analytics
Tech. Alarm: A system-generated event such as camera offline, black screen, obstruction or low light, able to raise its own workflow
Detects: People and vehicles
Filters Out: Animal motion, vegetation, light and shadow changes, headlights, glare and reflections, camera vibration, spider webs, insects, lens smudging
Applies At: Service Provider, Customer, Site, Device or Sensor level
Optical Camera Requirements: Minimum 640x480, at least 10 lux or 30% average image intensity, a person occupying 300 px squared or more
Thermal Camera Requirements: Configured as Thermal, detected object 600 px squared or more, white-hot or black-cold palette only
Not Supported: Fisheye lenses; PTZ or dome cameras that move the scene; dual-sensor thermal/optical cameras, which must be set up per sensor; cameras that zoom onto moving objects
Licensing: Per camera stream, activated from the Marketplace
What It Does: Compiles alarms from a selected customer, site or device into one reviewable view, prioritised rather than chronological
Event Limit: 100 / 200 / 300 / 400 / 500 / 600 events per camera
Licensing: Included in the GCX One base package
DC-09: SIA DC-09 over TCP to Amwin, Lisa, Immix or any compatible receiver, configured with a receiver IP and port and mapped per device with an Account Number and an optional encryption key
Evalink Talos: REST integration authenticated with an API Key and Company ID; no firewall configuration and no per-site mapping
Event Link: Every DC-09 signal carries a secure link opening pre-event footage, the live feed and the full alarm context
Event Overflow: More than 25 alarms from one device inside a 5-minute window raises an event.overflow and suppresses that device for the rest of the window; re-checked each new window
Threshold Override: Adjustable per tenant through the style.overflow.threshold custom property, for sites whose volume is legitimately high
Site-Level Limit: The monitoring platform applies its own aggregate limit across all sensors on a site, reported there as Alarm Limit Exceeded
Redundancy Timer: Suppresses duplicate events from the same source inside a configured window
Isolation: A sensor can be suppressed deliberately from 5 minutes to 9 hours and resumes on its own when the window closes
Fail-Safe Handling: An alarm that cannot be verified inside the response time defined in your SLA is treated as real and sent to the operator
Detection Scope: Object detection and person re-identification only. No facial recognition and no biometric identification is performed at any stage
Edge Cases: People near the edge of a frame may not be reliably detected and can be filtered as non-threatening; analog feeds capped below 640x480 raise missed-detection risk in low light
What It Does Not Replace: Detection analytics on the camera, camera hardware, physical security measures, human judgement, live monitoring or compliance rules

Getting started

The classification pipeline and transport are part of the platform. NOVA99x is activated per camera stream from the Marketplace; ZenMode is included in the base package.

01Connect your CMSMarketplace, then Alarm Management System — enter the DC-09 receiver IP and port, or the Talos API key and company ID
02Map your devicesCopy each Account Number out of the CMS rather than retyping it; a mismatch is silently discarded by the receiver
03Activate filteringSubscribe NOVA99x, choose the level it applies at, then set camera type and detection confidence
04Verify end to endRun the diagnostics transmission test and confirm alarms are arriving before relying on it