Introduction to Fire Alarm Control Panels

A Fire Alarm Control Panel (FACP) is the controlling component of a Fire Alarm System. The panel receives information from environmental flame sensors designed to detect changes associated with fire, monitors their operational integrity, provides for automatic control of equipment, and transmits information necessary to prepare the facility for fire based on a predetermined sequence.

Many FACPs are developed and manufactured by different companies, utilizing a variety of open and proprietary protocols such as Fike Cheetah and EST3. However, it is common to interface FACP information into the building automation system (BAS) to provide a building manager web access to monitor fire control ancillary information remotely.

Our Commitment to FACP

When integrators need to interface Fire Alarm Control Panels to the BAS,  they look to Sierra Monitor’s FieldServer protocol gateway, the industry’s clear leader in interfacing FACP products. FieldServer provides the ability to view the ancillary information and not interfere with the AHJ (Authority Having Jurisdiction) approved fire control system.

Facility managers, system installers, and FACP Original Equipment Manufacturers (OEMs) trust FieldServer protocol gateways to provide effective, efficient, and seamless interface to BAS. Working closely with every FACP manufacturer in the United States, we have developed comprehensive protocol drivers that work with all current and most legacy FACP. We maintain expert knowledge of protocol requirements and update drivers when manufacturer changes are released.

FACP Interoperability with BACnet, LonWorks, Modbus, KNX, SNMP, XML, etc.

Sierra Monitor’s FieldServer protocol gateways are configured with the FACP vendor’s proprietary protocol on one side with the required BACnet, LonWorks, KNX, Modbus, XML, or SNMP protocol on the other side. BACnet, LonWorks, or KNX may be used while interfacing the FACP to the BAS, whereas SNMP may be used if interfacing the FACP to a more IT-oriented Systems Manager (as in a data center), and XML may be used while interfacing the FACP products to the cloud.

Integrators and installers use our gateways for their flexibility, reliability, and ease-of-use, while OEMs often incorporate the FieldServer protocol gateway technology into their devices in lieu of doing their own protocol development.

Products

Sierra Monitor’s FieldServer protocol gateways are configured with the FACP vendor’s proprietary protocol on one side with the required BACnet, LonWorks, KNX, Modbus, XML, or SNMP protocol on the other side. Buyers usually order one of the hardware platforms below, select the vendor-specific FACP protocol, and specify the other drivers they want loaded on it.

FACP Converters and Gateways for Integrators

Integrators value the flexibility and ease-of-use offered by the FieldServer protocol gateways because it allows them to complete their integration projects quickly and with low risk. The following products are available to integrators:

FACP Converters and Gateways for OEMs

OEMs embed the FieldServer protocol gateways with their products as it enables them to present their native device as compatible with whatever standards based protocol is being used in the facility or the cloud provider (without increasing R&D costs).

Protocol Drivers

We have the industry's largest collection of FACP drivers. If you do not see a driver listed for a specific FACP vendor, please contact us at  support@sierramonitor.com

The gateway is also ordered with one or more of the following protocols depending on what type of device or network the FACP needs to connect to: