GCXONE · Features

GCX SenseView

Management for Camera-Free Sensors and IoT

The Half of the Site With No Lens.

GCX SenseView is the management layer for everything on a site that is not a camera: input and output ports driving gates, locks and sirens, PIR and environmental sensors, and the IoT devices that report a site condition rather than an image. The physical connections already exist in GCX One; SenseView is the concept for provisioning, telemetry and lifecycle management on top of them, and it is the one product in this set with a design decision still open.

Datasheet · v1.0 · verified 15 September 2026

How GCX SenseView works. Step 1, Sense: PIR, contacts, wireless detection, alarm hubs. Step 2, Port: Digital, analog, relay — typed, named, zoned. Step 3, Act: Gates, locks and sirens triggered from the map. Step 4, Manage: Provisioning and telemetry — the layer still to be decided.

Key capabilities

A single view of every configured input and output port across the estate, per hierarchy level
Input and output classification, with outputs triggered directly from the map
Per-port configuration: type, display name, IO URL, activation duration and zone
Sensor-driven alert rules that feed the same alarm workflow as a camera event
Export of the full port inventory for audit and handover

Primary use cases

Access control, where the response to an alarm is opening or closing something physical
Sites whose real signal is a contact, a PIR or an environmental threshold rather than a video feed
Handover and audit, where the question is which ports exist and what each of them does
Perimeter deployments combining wireless PIR detection with cameras on the same site

At a glance

Port classes, input and output

Teltonika I/O types

Open build-versus-buy decision

Live today

IO inventory and control

Every port on the estate in one table, configurable per port, placeable on the map, and triggerable from it.

Best for: gates, barriers, locks and sirens

Live today

Wireless detection

Reconeyez PIR detection cameras and AJAX hubs integrated for alarm reception, with battery and signal reported back.

Best for: perimeters with no power and no cabling

Concept

Sensor telemetry

Temperature, humidity, occupancy and actuator state ingested as first-class telemetry with threshold rules of their own.

Best for: sites where the condition matters more than the picture

Architecture

Non-camera devices, one inventory. GCX SenseView connects Wireless PIR, Alarm hubs and panels, Router I/O to GCX AlarmView, GCX GeoView, Operators.

Technical specifications

IO Inventory: Every configured port in one table, scoped to the level being viewed — service provider shows the platform, customer shows that customer
Columns: Id, date registered, device, name, site, type, whether shown on the map, whether shown in the operator view
Classification: Input, receiving a signal from an external source, or Output, sending a signal to trigger a physical action
Port Configuration: Type, name, display name, id, IO URL, activation duration, zone
Map Placement: Ports placed on the map in edit mode and triggered by clicking their icon
Local IO: Input and output operations available directly over a local device connection where the device supports it
Export: The full IO table exported for audit or handover
Wireless PIR: Reconeyez wireless PIR detection cameras, with battery level and LTE signal strength reported
Alarm Hubs: AJAX hubs carrying recorders, intrusion panels and other alarm-triggering objects, integrated for centralized alarm reception
Router I/O: Teltonika digital, analog, isolated and relay I/O with configurable alert states
Environmental And Power: Victron and EFOY telemetry, covered in detail by GCX EnergyGuard
Provisioning And Lifecycle: Bulk provisioning, firmware updates and fleet-wide telemetry dashboards for non-camera devices
Sensor Ingestion: Environmental measurements such as temperature and humidity, occupancy, and actuator state as first-class telemetry
Threshold Automation: Alert rules triggered from sensor thresholds, routed into the alarm workflow
Open Decision: Whether this is built natively or adopts an existing IoT device-management platform as the backend. The product structure deliberately leaves it unresolved
Status: This sheet describes a defined product concept with an existing hardware foundation, not a shipped module. The capabilities listed under what exists today are live; those under concept are not
Dependency: SenseView is the management layer over connections that already exist on the platform. It does not add hardware support of its own
Scope: Non-camera devices. Camera health belongs to GCX SystemView, and power to GCX EnergyGuard

Getting started

The IO and sensor capability described under what exists today is part of the platform and is configured per device.

01Add the deviceRegister the panel, router or detection device under its site
02Configure the portsSet each port type, display name, activation duration and zone
03Put them on the mapPlace outputs where operators will look for them, so response is one click
04Wire the rulesRoute port state changes into the alarm workflow with the response each one should trigger

Works with

Detection and IO hardware already integrated. reconeyez, ajax, teltonika, senstar.