12.07.2015 Views

A Guide To Reducing The Number Of False alarms From fire

A Guide To Reducing The Number Of False alarms From fire

A Guide To Reducing The Number Of False alarms From fire

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

6 If you cannot find the detector that was triggered, call in themaintenance company as they should know where detectors arewithin the <strong>fire</strong>-detection system.7 If the control panel does not show where the relevant detector is, orif no detector was triggered, call in the maintenance company as theproblem may be due to faulty equipment.8 Accurately record all the information about the false alarm in the systemlog book. This is very important as you may need the information ata later date.9 If false <strong>alarms</strong> continue, and you cannot find the cause or action youtake is unsuccessful, analyse when the false <strong>alarms</strong> happen and wherethey come from. This will help you to see if there is any pattern thatmay help you to identify the cause (for example, cooking before mealtimes or a boiler switching on early in the morning).10 Your investigations should show you that the false <strong>alarms</strong> are theresult of faulty equipment, malicious acts, human error, or activitiesnear detectors.Equipment faultsIf you can’t identify the cause of the false alarm, or if there seems to be afault in the system, turn the alarm off but do not reset the control panel.(If you have to reset the control panel, make special arrangements withthe company that installed or maintains your system to collect as muchinformation as possible before the control panel is reset.) <strong>The</strong> informationon the panel will help you to find the problem. If your equipment seemsto be faulty, call in the company that installed or maintains your system sothey can take appropriate action.10

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!