How to Recover Fire Alarm System Information
Content
June 24, 2015
How to Recover Fire Alarm System Information
Introduction
This bulletin is intended to assist in recovering information from a functioning EST fire
alarm control unit when the project database file is not available. This may occur when
an original installing dealer has gone out of business, when an owner has ended the
relationship with the service company, or when there are legal or other reasons that the
project database file cannot be made available.
NFPA Code requires involving the AHJ before modifying an existing Life Safety System.
The following is from the 2010 edition of NFPA 72:
10.18.1.1 The authority having jurisdiction shall be notified prior to installation or
alteration of equipment or wiring.
Project database files
Per NFPA code, the system installer is required to leave a copy of the system database
with the owner.
The following is from the NFPA 72 2010 edition:
10.18.2.3 Documentation Required. Every system shall include the following documentation,
which shall be delivered to the owner or the owner’s representative upon final acceptance of the
system:
(1)*An owner’s manual and manufacturer’s published instructions covering all system equipment
(2) Record drawings
(3) For software-based systems, record copy of the site-specific software
(Explanation from NFPA Handbook) The Code requires in 10.18.2.3(3) that a record copy of
the site-specific software be delivered to the owner or the owner’s representative upon final
acceptance of the system. Having a backup copy of the software will help facilitate reconfiguring
the system in situations where catastrophic failure has occurred due to lightning or other causes.
Refer to the definition of site-specific software in 3.3.255.2. The site-specific software is the
programming of the system for its specific application. It is not the executive software or the
source code used to develop the site-specific software.
1|P a g e
EST Sales Bulletin
The ideal method to work on a system that has been abandoned is to attempt to get a
copy of the latest system database file. If the former service company is still in
business, it is worth you or the building owner contacting them to request a copy of the
database file. If you have a good relationship with the Fire Marshall, it may be worth
getting him or her involved. A call from the FM to the former service company may
convince them to comply with the requirement to leave the project file with the facility
owner.
Retrieving point lists from addressable panels
All addressable panels will have some method of displaying and possibly printing
troubles and faults as they occur. The simplest procedure is to lift the communication
loop from one of the addressable loop controller modules and then write down or
capture this trouble report in some manner. When the loop finishes reporting all of the
troubles, replace the wires that were removed and wait for those troubles to clear, and
then continue with any additional loops. This process will normally provide a list of each
point address, the basic type of device, and any assigned user message for that point.
If the panel has hardwired NACs (Notification Appliance Circuits) or relay modules with
shutdowns, they should be disabled before lifting the addressable loop to prevent
unwanted alarms or preventable interruptions to normal building operations.
Once completed, you will have a list that should identify all detectors, pull stations,
waterflow switches, tampers and other input devices. It may also indicate any field
NACs, shutdowns or other functions.
Note that the EST2 and EST3X have a built-in RS-232 port which can be used with
HyperTerminal to capture the SIGA Loop information from the either a report or when
lifting the loop wires.
The EST3 requires the RS232 Card to be installed on the 3-CPU before the data can be
captured to HyperTerminal. If none of the panels on the network have an RS-232 card,
you could power the panel down and temporarily install one. This would allow you to
use HyperTerminal to capture the text.
Another source of information is the CMS point assignments. This may include zone or
other information that was included to provide critical data to dispatched responders.
Programming QuickStart and iO panels
These panels have the capability of retrieving the field devices, panel configuration and
program as stored in the system. Note that the program may not match exactly with the
way it was originally written as the CU may have optimized the programming before
downloading.
2|P a g e
EST Sales Bulletin
Retrieving Loop Data from EST2, 3X and EST3 panels
The SDU for these panels support retrieving the Signature device data while connected
to the panel. This is necessary to allow mapping and loop reconciliation but also
provides us with a method to populate the SDU with the actual installed devices in an
unknown system.
Once at the site, open the SDU program and create a startup SDU project with all of the
cabinets and panel modules as they exist at the site. Make sure to get all the modules
including plug in option cards on the back, any operator layers and note the voltage
settings of any amplifiers. You will also need to determine the existing panel node
addresses to make sure your new project matches the existing to prevent
communication issues. (Note: this bulletin assumes familiarity with the SDU
procedures for SIGA loop retrieval by EST certified technicians).
Once the map is uploaded, “Accept All” from the map screen and those devices will get
loaded into the loop configuration. Now the project will have the Device Type,
personality and address.
Programming EST2, 3X and EST3 panels
Only the loop data is able to be retrieved from these systems. This data does not
include programming rules or object labels. This is because the panels do not store the
rules and object labels as we understand them. The SDU requires that you compile the
project before downloading which interprets the rules and the objects affected by the
rules, and converts those into a code that the CPUs in the panels and loop controllers
can understand. This process results in the database files that are stored into the panel
memory during download.
Since the programming cannot be retrieved from these panels, there are two options:
1. Perform a complete test and inspection of the system to create a record of the
following outputs for each input or fire zone:
a. Notification appliances
b. Voice Messages or coded tones (if used)
c. Relays and other outputs
d. CMS reporting to monitoring services
e. Any other specific outputs that need to occur for this system
2. If the owner and the AHJ agree, the system can be evaluated as a new system.
This means having detailed discussions regarding the required sequence of
operation for the site. If the old service company was having problems
maintaining and programming the system, re-evaluating the required system
3|P a g e
EST Sales Bulletin
functionality may be the best method as there may be deficiencies in the existing
program.
This will require some planning with people or plans that show the same output
functions as discussed above – notification appliances, messages or codes,
relays, monitoring and anything else specific to this site.
Once the entire system operation has been recorded or developed new, the
programming of new object labels and rules can be done to create the desired
operation. The experience and skill of the programmer will greatly affect how efficient
the new project file will be. In most cases the object labels and rules can be very
effective at producing the desired functionality.
Caution: Before downloading, The AHJ should be consulted if they haven’t already
been part of this process up to this point. Once downloaded, the system will have a
new project database and the entire system must be 100% tested to verify that the new
database was properly configured. If the AHJ wants to witness the testing the same as
a new installation, code requires that a 100% pre-test be conducted.
Contact information
8985 Town Center Parkway
Bradenton FL, 34202
T (800) 655-4497
F (866) 226-2126
4|P a g e
How to Recover Fire Alarm System Information
Introduction
This bulletin is intended to assist in recovering information from a functioning EST fire
alarm control unit when the project database file is not available. This may occur when
an original installing dealer has gone out of business, when an owner has ended the
relationship with the service company, or when there are legal or other reasons that the
project database file cannot be made available.
NFPA Code requires involving the AHJ before modifying an existing Life Safety System.
The following is from the 2010 edition of NFPA 72:
10.18.1.1 The authority having jurisdiction shall be notified prior to installation or
alteration of equipment or wiring.
Project database files
Per NFPA code, the system installer is required to leave a copy of the system database
with the owner.
The following is from the NFPA 72 2010 edition:
10.18.2.3 Documentation Required. Every system shall include the following documentation,
which shall be delivered to the owner or the owner’s representative upon final acceptance of the
system:
(1)*An owner’s manual and manufacturer’s published instructions covering all system equipment
(2) Record drawings
(3) For software-based systems, record copy of the site-specific software
(Explanation from NFPA Handbook) The Code requires in 10.18.2.3(3) that a record copy of
the site-specific software be delivered to the owner or the owner’s representative upon final
acceptance of the system. Having a backup copy of the software will help facilitate reconfiguring
the system in situations where catastrophic failure has occurred due to lightning or other causes.
Refer to the definition of site-specific software in 3.3.255.2. The site-specific software is the
programming of the system for its specific application. It is not the executive software or the
source code used to develop the site-specific software.
1|P a g e
EST Sales Bulletin
The ideal method to work on a system that has been abandoned is to attempt to get a
copy of the latest system database file. If the former service company is still in
business, it is worth you or the building owner contacting them to request a copy of the
database file. If you have a good relationship with the Fire Marshall, it may be worth
getting him or her involved. A call from the FM to the former service company may
convince them to comply with the requirement to leave the project file with the facility
owner.
Retrieving point lists from addressable panels
All addressable panels will have some method of displaying and possibly printing
troubles and faults as they occur. The simplest procedure is to lift the communication
loop from one of the addressable loop controller modules and then write down or
capture this trouble report in some manner. When the loop finishes reporting all of the
troubles, replace the wires that were removed and wait for those troubles to clear, and
then continue with any additional loops. This process will normally provide a list of each
point address, the basic type of device, and any assigned user message for that point.
If the panel has hardwired NACs (Notification Appliance Circuits) or relay modules with
shutdowns, they should be disabled before lifting the addressable loop to prevent
unwanted alarms or preventable interruptions to normal building operations.
Once completed, you will have a list that should identify all detectors, pull stations,
waterflow switches, tampers and other input devices. It may also indicate any field
NACs, shutdowns or other functions.
Note that the EST2 and EST3X have a built-in RS-232 port which can be used with
HyperTerminal to capture the SIGA Loop information from the either a report or when
lifting the loop wires.
The EST3 requires the RS232 Card to be installed on the 3-CPU before the data can be
captured to HyperTerminal. If none of the panels on the network have an RS-232 card,
you could power the panel down and temporarily install one. This would allow you to
use HyperTerminal to capture the text.
Another source of information is the CMS point assignments. This may include zone or
other information that was included to provide critical data to dispatched responders.
Programming QuickStart and iO panels
These panels have the capability of retrieving the field devices, panel configuration and
program as stored in the system. Note that the program may not match exactly with the
way it was originally written as the CU may have optimized the programming before
downloading.
2|P a g e
EST Sales Bulletin
Retrieving Loop Data from EST2, 3X and EST3 panels
The SDU for these panels support retrieving the Signature device data while connected
to the panel. This is necessary to allow mapping and loop reconciliation but also
provides us with a method to populate the SDU with the actual installed devices in an
unknown system.
Once at the site, open the SDU program and create a startup SDU project with all of the
cabinets and panel modules as they exist at the site. Make sure to get all the modules
including plug in option cards on the back, any operator layers and note the voltage
settings of any amplifiers. You will also need to determine the existing panel node
addresses to make sure your new project matches the existing to prevent
communication issues. (Note: this bulletin assumes familiarity with the SDU
procedures for SIGA loop retrieval by EST certified technicians).
Once the map is uploaded, “Accept All” from the map screen and those devices will get
loaded into the loop configuration. Now the project will have the Device Type,
personality and address.
Programming EST2, 3X and EST3 panels
Only the loop data is able to be retrieved from these systems. This data does not
include programming rules or object labels. This is because the panels do not store the
rules and object labels as we understand them. The SDU requires that you compile the
project before downloading which interprets the rules and the objects affected by the
rules, and converts those into a code that the CPUs in the panels and loop controllers
can understand. This process results in the database files that are stored into the panel
memory during download.
Since the programming cannot be retrieved from these panels, there are two options:
1. Perform a complete test and inspection of the system to create a record of the
following outputs for each input or fire zone:
a. Notification appliances
b. Voice Messages or coded tones (if used)
c. Relays and other outputs
d. CMS reporting to monitoring services
e. Any other specific outputs that need to occur for this system
2. If the owner and the AHJ agree, the system can be evaluated as a new system.
This means having detailed discussions regarding the required sequence of
operation for the site. If the old service company was having problems
maintaining and programming the system, re-evaluating the required system
3|P a g e
EST Sales Bulletin
functionality may be the best method as there may be deficiencies in the existing
program.
This will require some planning with people or plans that show the same output
functions as discussed above – notification appliances, messages or codes,
relays, monitoring and anything else specific to this site.
Once the entire system operation has been recorded or developed new, the
programming of new object labels and rules can be done to create the desired
operation. The experience and skill of the programmer will greatly affect how efficient
the new project file will be. In most cases the object labels and rules can be very
effective at producing the desired functionality.
Caution: Before downloading, The AHJ should be consulted if they haven’t already
been part of this process up to this point. Once downloaded, the system will have a
new project database and the entire system must be 100% tested to verify that the new
database was properly configured. If the AHJ wants to witness the testing the same as
a new installation, code requires that a 100% pre-test be conducted.
Contact information
8985 Town Center Parkway
Bradenton FL, 34202
T (800) 655-4497
F (866) 226-2126
4|P a g e
