GCXONE · Features

GCX ServiceCenter

Configuration, Forensics and Platform Operations

The Business of Running the Platform.

GCX ServiceCenter is where the business of running the platform happens: configuring the hierarchy and its devices, raising and tracking service requests, reviewing recorded evidence forensically, and operating the DC-09 alarm interfaces that connect GCX One to a monitoring centre. It is the administrator and service-desk half of the platform, as distinct from the operator workspace.

Datasheet · v1.0 · verified 15 September 2026

How GCX ServiceCenter works. Step 1, Structure: Provider, customer, site, device, sensor. Step 2, Connect: DC-09 receiver and per-device account numbers, or Talos. Step 3, Verify: Transmission test before go-live, not after. Step 4, Operate: Service requests, forensic review, SIP audio.

Key capabilities

Configuration across the full hierarchy, from service provider settings to an individual sensor
Service requests raised, categorised and tracked to a status, with a full history per request
Forensic review of recorded video by timeline, with masking and export for evidence
DC-09 alarm interface operation, including per-device account mapping and transmission diagnostics
SIP audio service configuration for talk-down and announcements on the sites that carry speakers

Primary use cases

A service provider administering many customers from one console without touching each site
Investigations that need a defensible export rather than a screen recording
Commissioning and go-live, where the work is configuration rather than monitoring
Diagnosing why a CMS is not receiving alarms it should be receiving

At a glance

Hierarchy levels configured here

DC-09 fields per device

CMS transport mechanisms

Immutable audit log

Connecting a monitoring centre

Receiver	Mechanism	What you configure
Amwin / Lisa / Immix	SIA DC-09 over TCP	Receiver IP, receiver port, per-device Account Number
Any DC-09 receiver	SIA DC-09 over TCP	The same, through the generic Other CMS option
Evalink Talos	REST	API Key and Company ID, no per-site mapping

Architecture

The administration surface. GCX ServiceCenter connects Hierarchy, Devices, Credentials to Monitoring centre, Site speakers, Audit and export.

Technical specifications

Hierarchy: Service Provider, Customer, Site, Device, Sensor — every configuration, access and routing decision is made somewhere in this structure
Service Provider Settings: Organization name and logo used in reports, regional locale and timezone, SOC contact variables injected into alert templates, the tenant-wide alarm receiver configuration
Cascading Subscriptions: A subscription at the customer level applies to every site and device onboarded later, with no further action
Properties: A Properties tab at every level for per-entity configuration, including custom properties used by device integrations
Export: Structured export of data at multiple hierarchy levels
Model: Each request carries a category and sub-category, a structured set of fields, a status, and the account that raised it
Status: Tracked per request with the full list of states available to it
Scope: Raised and listed per user, within the service provider they belong to
Playback: Recorded footage navigated by timeline, with jump back from 15 seconds to 1 day
Alarm Context: Pre-alarm, alarm and post-alarm frames alongside the recorded clip
Masking: Temporary or permanent masking of a region, applied without interrupting live monitoring or recording
Audit: Every review action recorded in the immutable audit log with the account and timestamp
DC-09: Receiver IP and TCP port per integration; Account Number and optional encryption key per device, shown on that device Overview tab as SIA Details
Supported Receivers: Amwin, Lisa, Immix, and any other SIA DC-09 compatible receiver through the generic option
Evalink Talos: REST integration authenticated with an API Key and Company ID
Diagnostics: A transmission test sequence confirming packets are acknowledged by the receiver
SIP: Genesis Audio devices registered per site, providing operator talk-down, announcements and conference mode to SIP speakers
Credentials: Username, password and SIP domain issued per device and entered into the speaker own web client, with TCP transport
Most Common Failure: An Account Number mismatch between GCX One and the CMS. The receiver discards the packet silently, so the platform reports the alarm as sent and the CMS never shows it. Copy the value from the CMS rather than retyping it
Separation Of Duties: ServiceCenter configures and diagnoses. It does not handle alarms; that is the operator workspace, and the split is deliberate
Access: Every screen here is role-gated. An operator role reaches none of it

Getting started

Included in the GCX One base platform, reached by an administrator role. Most of the work is done once, at commissioning.

01Set the service providerOrganization name, logo, locale, timezone and SOC contact details, before any customer is created
02Build the hierarchyCreate customers, then sites with their coordinates and timezone, then devices and sensors
03Connect the CMSConfigure the receiver, map each device account, and run the transmission diagnostics
04Subscribe at the topEnable HealthCheck and the analytics you want at customer level so later hardware inherits them