CSV over IP / CSV-IP
Use the configurable TCP delivery path for compatible receivers or local gateway workflows, including account, Area / Zone and acknowledgement handling.
MONITORING-STATION REPORTING
CSV/IP and SIA DC-09 reporting with delivery evidence.
AlarmForgeX can route qualified device, alarm and supported video-event conditions to configured monitoring receivers using CSV/IP or SIA DC-09 paths, while keeping queue, retry and acknowledgement state visible to the installer.
Persistent delivery queueTrack pending, sending, delivered and failed reporting work instead of losing events silently.
Account + Area / Zone mappingKeep receiver account and functional reporting addresses explicit across monitored sites.
Acknowledgement visibilityReview retries and receiver responses where the configured protocol provides them.
TWO DELIVERY OPTIONS
Use the receiver path that fits the monitoring environment.
AlarmForgeX is not a monitoring-station receiver. It creates and routes operational events from supported systems to a receiver or approved local gateway that you configure.
SIA DC-09 path
Use AlarmForgeX's configured SIA DC-09 reporting path where the receiving environment is set up for the protocol and site credentials.
Controlled offline path
Where required, Secure Offline Monitoring Mode can use an approved local T4000 or gateway target rather than exposing an unsupported destination.
EVENT DELIVERY
Follow a condition from field state to receiver response.
The reporting workspace keeps the delivery lifecycle visible so an installer can see whether an event was merely created or actually made it through the configured path.
Detect a state change
A supported device, alarm area/input or video analytic changes into a reportable condition.
Qualify and map it
AlarmForgeX applies site, arming and reporting configuration and maps the condition to its account and Area / Zone.
Queue and deliver
The event enters the persistent delivery queue and uses the configured CSV/IP or SIA DC-09 path.
Record the result
Delivery history keeps attempts, retries and available receiver acknowledgement evidence together.
OPERATIONAL CONTEXT
Reporting capacity follows the monitored estate.
Professional Reporting Paths are separate from Infrastructure Points and Video Detection Event Channels in AlarmForgeX licensing. Paid plans calculate Reporting as Infrastructure plus Video so configured monitored points can have corresponding receiver or gateway delivery capacity.
- Persistent queue with controlled retries and cooldown state
- Per-account heartbeat grouping for configured reporting accounts
- Functional Area / Zone allocation across device and event types
- Service Mode for commissioning without treating test work as live alarms
- Delivery history for troubleshooting receiver-path failures
PROVE THE DELIVERY PATH
Monitor locally. Report only what you configure.
Use AlarmForgeX to bring supported infrastructure into one Windows operations view, then enable professional reporting paths where the site requires them.