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 using the industry-standard SIA DC-09 protocol — including Evalink Talos and every other supported CMS vendor — so alarms reach your team the moment they happen, automatically.

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. No manual steps, no gaps.

How It Works

Every CMS integration — including Evalink Talos — connects to GCXONE using the same SIA DC-09 protocol. Evalink Talos has a quick-start below; for Amwin, Lisa, Immix, or any other DC-09 receiver, follow the general steps in the next section.

1. Evalink Talos Integration

Evalink Talos is a cloud-native platform for modern monitoring centres. Like every other CMS integration in GCXONE, it uses the SIA DC-09 protocol for alarm delivery.

Step 1. In the Marketplace, click Explore on the Evalink Talos card. Review the connection scope.

Step 2. Click Configure and enter the DC09 Receiver IP Address and DC09 Receiver Port — the same two fields used for every CMS integration in GCXONE.

Figure 1: Evalink Talos Card - A green badge confirms the integration is active and forwarding alarms.

Figure 2: Integration Detail

DC09 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. GCXONE goes a step further. It 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 3: 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 4: Integration Status

Figure 5: 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 6: 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 7: 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 8: 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.

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 consolidates all GCXONE alarm data into a single source of truth across every monitored site.
• A multi-site service provider maps hundreds of sites to their CMS accounts, with each site forwarding alarms independently.

Best Practices

• Test before going live. After the initial DC-09 setup, verify that alarms are actually reaching the CMS before you rely on it in production.
• Keep Account Numbers 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 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.

Evalink Talos and every other supported CMS (Amwin, Lisa, Immix, or Other CMS System) connect to GCXONE through the identical SIA DC-09 channel — same Receiver IP/Port setup, same secure event-link payload. The only difference is which vendor card you configure in Marketplace → Alarm Management System.

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