Alarm Management System

What Alarm Management System Does

When an alarm triggers in GCXONE, you don't want to wait. The Alarm Management System connects GCXONE directly to your Central Monitoring Station or alarm platform, so alarms reach your team the moment they happen, automatically. GCXONE supports two integration methods: the industry-standard SIA DC-09 protocol for CMS receivers (Amwin, Lisa, Immix, and other DC-09-compatible systems), and a separate REST API integration built specifically for Evalink Talos — Talos does not use DC-09.

Why It Matters

Monitoring centres live and die by speed. When alarms have to be forwarded manually, delays creep in, and delays mean missed incidents. The Alarm Management System takes that risk off the table entirely. The moment an alarm triggers in GCXONE, it's on its way to your CMS or Talos account. No manual steps, no gaps.

How It Works

Both integration methods are configured from Marketplace → Alarm Management System, but they use different connection details since they're different protocols.

DC-09 CMS Integration

SIA DC-09 is the industry-standard protocol for transmitting alarm signals over IP networks, and virtually every major CMS platform speaks it — including Amwin, Lisa, Immix, and any other SIA DC-09 compatible receiver. GCXONE extends each DC-09 signal with a secure event link, so when an operator opens it, they see pre-event footage, the live feed, and the full alarm context right away.

To configure the DC-09 integration:

Step 1. Go to Marketplace from the left navigation, then click the Alarm Management System tab to filter the available integrations.

Figure 1: Marketplace Navigation - Filter to Alarm Management System to see all supported CMS receivers.

Step 2. Click Explore on the CMS you want to connect. Take a moment to review the connection scope and required fields before clicking Configure.

Figure 2: Integration Status

Figure 3: Integration Detail

Step 3. Enter two values to establish the DC-09 connection:

• DC09 Receiver IP Address — the IP address of your CMS server
• DC09 Receiver Port — the TCP port the CMS server is listening on

Figure 4: Connection Setup - Enter the IP address and port to route GCXONE alarms to your CMS.

If your system isn't listed, use Other CMS System to connect any SIA DC-09 compatible receiver.

Figure 5: Custom CMS Setup - Connect any SIA DC-09 compatible receiver not listed in the Marketplace.

Step 4. Once submitted, GCXONE establishes the TCP connection automatically. The card updates to Configured and alarms start forwarding right away.

Step 5. Each device's Overview tab in Configuration shows a SIA Details panel (Account Number, Encryption Key, Receiver IP, Receiver Port) reflecting that device's DC-09 mapping status.

Figure 6: SIA Details panel on the device's Overview tab — Account Number, Encryption Key, Receiver IP, and Receiver Port for that device's DC-09 mapping.

Step 6. The two fields that matter:

• Account Number — must exactly match the CMS string (case-sensitive)
• Encryption Key — an optional shared secret for encrypted DC-09 communication. Leave this blank if encryption isn't required.

Once mapped, GCXONE forwards alarms via DC-09, each one carrying a secure event link that CMS operators can open to review the full alarm context.

Evalink Talos Integration

Evalink Talos is a cloud-native platform for modern monitoring centres. Unlike the DC-09 receivers above, Talos does not use SIA DC-09 — GCXONE connects to it through a REST API instead, authenticating with an API Key and Company ID from your Talos account. No firewall configuration or per-site mapping is required.

For the full Talos configuration steps, see DC09 Alarm Management System Integration.

Real-World Use Cases

• A DC-09 monitoring center routes alarms from Amwin, Lisa, Immix, or any SIA DC-09 receiver directly from GCXONE, without touching a secondary tool.
• An Evalink Talos user connects once with API credentials and gets every site syncing automatically, with no per-site mapping.
• A multi-site service provider maps hundreds of sites to their DC-09 CMS accounts, with each site forwarding alarms independently.

Best Practices

• Test before going live. After setup, verify that alarms are actually reaching your CMS or Talos account before you rely on it in production.
• Keep DC-09 identifiers consistent. The Account Number must match the CMS string exactly. Even a small mismatch will silently block alarm delivery.
• Use encryption where it counts. For DC-09 deployments handling sensitive alarm data, always set an encryption key. Leave it blank only for internal or low-risk environments.
• Check your device SIA Details regularly. A device missing its Receiver IP/Port or Account Number won't forward alarms yet.

Additional Details

Everything is configured directly inside GCXONE. No manual protocol setup, no external tools needed.

DC-09 CMS receivers (Amwin, Lisa, Immix, Other CMS System) and Evalink Talos use different underlying protocols — SIA DC-09 over TCP for the CMS receivers, a REST API for Talos — so their setup steps differ accordingly. See DC09 Alarm Management System Integration for the complete configuration walkthrough and a side-by-side comparison of both methods.

For support or configuration help, reach out to NXGEN Technology AG through the GCXONE support channel.