Reference · built on requestConnectorIndustrial & building protocols

SIA DC-09

Alarm and supervision events from intrusion panels and communicators, received over IP as ANSI/SIA DC-09 messages.

Request accessPricing ↗

About

ANSI/SIA DC-09 is the Security Industry Association's standard for reporting events from premises equipment to a central station receiver over Internet Protocol. It builds on the SIA Receiver-to-Computer Interface Protocol and carries the older signaling formats as payloads: Contact ID as ADM-CID and the SIA format as SIA-DCS, which every compliant receiver must accept. Each message carries a sequence number that the receiver echoes in its acknowledgement, and optional AES encryption with 128- or 256-bit keys. The SIA Intrusion Subcommittee maintains the standard. The 2026 revision adds autocommissioning and encryption key rotation while keeping the legacy formats.

Through Fibric, a receiver endpoint takes the events your panels or communicators are pointed at, acknowledges them, and hands each alarm, trouble, or test signal to an operator, who proposes what happens next for your approval.

This is a reference listing. It documents what Fibric would read from SIA DC-09 and what it could propose, based on the vendor's published interfaces. Fibric builds it under a managed deployment when you request it; selecting it here installs nothing.

Inputs

  • Alarm and other events from premises equipment, carried as ADM-CID (Contact ID) or SIA-DCS payloads
  • The account number, the account prefix (L), and the optional receiver number (R) that identify the reporting panel
  • The sequence number on every message, so a repeated or missing report is visible
  • Whether a message arrived encrypted, shown by the asterisk token such as *SIA-DCS
  • Supervision of each panel's connection, since DC-09 provides a supervised link between the alarm system and the receiver

Proposed actions

Read-only. Actions need a separate connector.

Proposed actions are target capabilities. Every action runs propose-first and needs a validated deployment and the appropriate permissions.

What you can build

  • Triage the alarm with context

    Receive the ADM-CID event, look up the site, and propose the response path: call the keyholder, dispatch, or log it as a known test, for your approval.

    With Alarm Triage, Duress Response

  • Catch the panel that went silent

    Track supervision per account. When a panel misses its expected reports, propose a trouble ticket before the next arming.

    With Alarm Triage, After-Hours Audit

  • Verify with video before dispatch

    Match an alarm event to the camera covering that zone through the ONVIF connector, and propose dispatch with the recording window attached.

    With Alarm Triage, Incident Draft

Requirements

  • Panels or communicators that implement ANSI/SIA DC-09 and can be pointed at a second receiver address and port
  • A reachable IP address and port for the receiver endpoint
  • Account numbers and, where used, receiver and line prefixes for every panel, so each event maps to a site
  • A licensed copy of DC-09-2026 from SIA if you need the full message tables; SIA sells the standard
Authentication
A shared AES key per panel, 128- or 256-bit, configured on the premises equipment and on the receiver. The 2026 revision adds key rotation. Unencrypted reporting is allowed by the standard but not recommended here.

Limits

  • DC-09 carries events one way. The receiver acknowledges; it does not arm, disarm, or bypass a panel
  • Encryption is optional in the standard. Panels configured without it send account data and events in the clear
  • A receiver must accept at least ADM-CID and SIA-DCS; any other token depends on what your panel sends
  • Pointing a panel at a second receiver is a panel configuration change that your monitoring provider may need to approve

Access and pricing

Reference listing. Fibric builds the connector under a managed deployment when you request it. Your quote covers the build, capabilities, usage, and support.

Request SIA DC-09 ↗

Questions and answers

Which message formats does DC-09 carry?
At least two. A compliant central station receiver must support the SIA-DCS and ADM-CID tokens. ADM-CID carries Ademco Contact ID as defined in SIA DC-05; SIA-DCS carries the SIA format. Encrypted messages insert an asterisk, so an encrypted SIA packet uses the token *SIA-DCS.
What changed in DC-09-2026?
SIA announced the revision on March 3, 2026. It carries ANSI approval, adds autocommissioning to simplify deployment and encryption key rotation, includes more use cases and visual examples, and stays backward compatible with legacy formats.
Can this connector control the panel?
No. DC-09 reports events from premises equipment to a receiver. The receiver replies with acknowledgements that echo the message sequence number. Arming, disarming, and bypass stay with the panel and the systems your monitoring provider uses.
Ask about SIA DC-09

Ask about the capabilities and requirements in this listing.

For project-specific requirements, contact Fibric.

This connector listing is developed, published, and supported by Fibric. It describes integration with SIA DC-09 through published interfaces. Third-party names and logos identify the systems an integration connects to; they are the property of their respective owners, who are not affiliated with Fibric and do not sponsor or endorse this listing. Trademark policy