Supervision interfaces and integration options for fire suppression systems
AeroXSense offers several integration levels to connect electrical-equipment fire protection with building or industrial technical systems: status reporting, dry contacts, shutdown control, reporting to BMS, building control or fire-safety systems, and radio connectivity to a cloud platform depending on the version.
From self-contained protection to remote supervision
Each project can use the level actually required, without unnecessary complexity.
Self-contained protection
Local detection and activation without status reporting or third-party connection.
Status reporting
Transmission of a state or activation through a wired interface, generally a dry contact.
Safety control
Control of an external device: electrical shutdown, ventilation stop or a project-defined scenario.
Supervision and connectivity
Reporting to BMS, building control, fire-safety systems or a remote platform depending on interfaces and version.
Protection that integrates into the site’s technical ecosystem
The suppression device remains at the core of protection. Interfaces then transmit information or control external actions.
Which information can be transmitted?
The exact states depend on the product and wiring. The following functions may be considered depending on the project.
Control power shutdown after detection or activation
Fire suppression must not be confused with de-energisation. Depending on the project, an interface can control a contactor, motorised breaker or another external device.
Why shut down power?
- Limit continued electrical energy
- Reduce the risk of re-energising the fault
- Support safe intervention and isolation
- Coordinate suppression with the site safety scenario
Points to validate
- Type and power of the circuit
- External switching device and safety logic
- Behaviour during power loss
- Possible delay and action sequence
- Consequences for critical equipment
Report status to existing systems
AeroXSense interfaces can be included in an existing supervision architecture. The final protocol and intermediary equipment depend on the customer system and integrator.
BMS integration
Reporting to building management to display equipment status or create a technical alarm.
Building-control integration
Use of contacts or states in central supervision of several technical installations.
Fire-system integration
Possible connection within an engineered fire-safety architecture through selected compatible interfaces and equipment.
Industrial PLC
Reading a contact, initiating a machine scenario or reporting to production supervision.
Technical alarm
Simple reporting to an alarm device, transmitter or technical panel.
Multi-zone management
Identification of several cabinets or compartments depending on inputs and addressing logic.
Remote supervision of compatible equipment
Some versions can transmit information by radio to a gateway or directly to a remote service. Availability depends on the product, network coverage and selected service agreement.
Radio transmission
Communication without long-distance wiring, depending on the technology integrated into the version.
Cloud platform
Centralisation of available states and events for registered equipment.
Mobile notifications
Push notification or alert according to configured rules.
Multi-site management
View equipment distributed across several buildings or locations.
Event log
History of information reported by compatible devices.
Access management
Accounts, roles and permissions according to the customer organisation and service.
Which projects benefit from these interfaces?
Integration options are especially relevant where installations are critical, remote, multi-site or already supervised.
Electrical cabinets
Activation reporting, shutdown and connection to PLC or supervision.
Main switchboards
Zone identification, de-energisation control and status reporting.
Electrical rooms
Centralisation of several protection systems and connection to room systems.
Photovoltaic systems
Reporting to site supervision and circuit shutdown depending on architecture.
EV charging
Integration with charging-infrastructure management systems.
Industry
Connection to PLCs, production supervision and shutdown scenarios.
Telecommunications
Remote supervision of technical cabinets or isolated sites.
Marine and ports
Status reporting in distributed technical architectures.
Commercial buildings
Reporting to BMS and central technical alarms.
Multi-equipment sites
Management of several cabinets and event location.
Infrastructure
Distributed systems in logistics sites, tunnels and technical installations.
OEM and machinery
Integration into machine or equipment control logic.
Steps before defining the architecture
Frequently asked questions about status reporting, shutdown and supervision interfaces
What is status reporting?
It is the transmission of equipment state to another system, such as activation, fault or availability.
What is a dry contact used for?
A dry contact provides an isolated electrical indication without imposing AeroXSense system voltage. It can be read by a panel, PLC, BMS or compatible transmitter.
Can the system automatically shut down power?
An interface can control an external switching device, but the generator does not directly interrupt power. The contactor or motorised breaker must be sized and installed for the relevant circuit.
Can status be sent to a BMS?
Yes, generally through a dry contact or intermediary module compatible with the BMS. The integrator defines how the state is used and displayed.
Can the device be integrated with building control?
Yes, depending on available inputs, protocol and architecture defined with the integrator.
Is the system compatible with every fire-safety system?
Universal compatibility must not be assumed. Integration can be studied according to the fire system, interfaces, site requirements and selected intermediary equipment.
Which information can be sent to the cloud?
Depending on the version: states, activation, faults or available events. The exact list must be confirmed for the selected product and service.
Is an internet connection always required?
No for local functions and dry contacts. It may be required for a cloud platform depending on radio architecture and gateway.
Can several sites be supervised?
Yes with suitable versions and services, subject to network coverage, equipment registration and configured access rights.
Does connectivity replace self-contained protection?
No. Communication complements protection. Detection and activation must remain defined independently from the supervision channel.
Who should wire shutdown or reporting interfaces?
A qualified professional using an approved diagram and respecting electrical, fire-safety and operational rules.
What information is needed for a study?
Installation diagram, required states, devices to be controlled, available interfaces, supervision system and network constraints.
Let’s build your supervision architecture
Send us the protected equipment, required states, safety actions, BMS or fire system used and communication constraints. We will define the appropriate interfaces.
