Bogus CAN/ULC-S537-04 Fire Alarm Verification Appendix "C" posted by Frank Kurz on Scribd
When you simply replace a conventionally wired control panel (without any upgrades or modifications to the field wiring or devices), it’s pretty well a given that you have to make the new system work the same way the original was designed, unless the local jurisdictional authority insists that the system be updated to current Building Code and CAN/ULC-S524 requirements. At the very least, when you’re upgrading to an addressable system you are required (without exception) to employ isolators within the various floor areas in order to ensure the entire system isn’t compromised by a single “short circuit” fault (you can also achieve the required level of performance by employing separate loop controllers for each area). As a matter of fact, the Installation Standard is very clear on this (reference the Clauses which are provided in the aforementioned article). Since there are NO ISOLATORS installed in the referenced system (and none mentioned on the Verification Appendix “C” report), if you impose a short across any of the data loops (which a conventional heat detector wired directly to one would do when activated), you will essentially take down the loop controller and all the devices associated with it. In a worst case scenario, if your system employs only one such controller (a single addressable loop), you’re essentially rendering the entire fire alarm system non-functional.
When you add to this the failure to mention any pertinent information relating to all of the installed supporting field devices (the addressable modules that are a part of this system), and the absence of the documentation actually required by the Standard which is supposed to support a properly conducted Fire Alarm Verification, you have a Life Safety System with highly questionable performance even in the best of conditions. I shudder to think what’s going to happen during an actual fire emergency when occupant notification becomes even more critical and an absolute necessity.
I am going to outline all of the deficiencies I identified in a brief site visit I made and my examination of the pertinent documentation:
1. The fire alarm Verification report does NOT comply with the acceptable format for a CAN/ULC-S537-04 Appendix “C” required by NBC 2005 (in effect at the time of the installation). The form employed in this instance utilizes a Vancouver version Appendix “C1” first page and incorporates five (5) attached individual device test record sheets (the subject system documented by this bogus Verification is located in the eastern part of British Columbia). The referenced Standard details the minimum acceptable Appendix “C” report in Clauses 3.2.1 through 3.2.7, which must consist of Sections “C1” through “C6.3” as follows:
C1. FIRE ALARM SYSTEM VERIFICATION REPORT (Subsections A through K) - Formatted for a different jurisdiction
C2. DOCUMENTATION (Subsections A through G) - MISSING
C3. FIELD DEVICES AND RELATED CIRCUITS - TEST AND INSPECTION (Subsections A through H) - MISSING
C4. DATA COMMUNICATION LINK TEST (Subsections A through F) - MISSING
C5.1 CONTROL UNIT OR TRANSPONDER TEST (Subsections A through JJ) - MISSING
C5.2 VOICE COMMUNICATION TEST (Subsection A through P) - Not Applicable but must still be included
C5.3 REQUIRED SYSTEM RESPONSE TIMES (Subsections A through F) - MISSING
C5.4 CONTROL UNIT OR TRANSPONDER INSPECTION (Subsections A through P) - MISSING
C5.5 LARGE SCALE NETWORK SYSTEMS (Subsections A through E) - Not Applicable but must still be included
C5.6 POWER SUPPLY INSPECTION (Subsections A through G) - MISSING
C5.7 EMERGENCY POWER SUPPLY TEST AND INSPECTION (Subsection A through U) - MISSING
C5.8 ANNUNCIATOR AND REMOTE TROUBLE SIGNAL UNIT TEST AND INSPECTION (Subsection A through N) - Not Applicable but must still be included
C5.9 ANNUNCIATORS OR SEQUENTIAL DISPLAYS (Subsection A through K) - Not Applicable but must still be included
C5.10 REMOTE TROUBLE SIGNAL UNIT TEST AND INSPECTION (Subsection A through D) - Not Applicable but must still be included
C6.1 FIELD DEVICE TESTING - LEGEND AND NOTES - MISSING
C6.2 INDIVIDUAL DEVICE RECORD - Incomplete
C6.3 SIGNALLING DEVICE SOUND LEVEL MEASUREMENT - MISSING
2. The “installed correctly” columns on the individual device test records are marked “YES”, when in fact there are a number of field devices installed INCORRECTLY (i.e. spacing requirements for heat detectors do not comply with CAN/ULC-S524-01).
3. System is identified as a two stage system. There are no two stage manual stations installed and no documentation that might suggest this may be an approved design or that the system’s upgrade received a formal review and approval by the local jurisdictional authority. The test report does not document testing of the GA loop, required automatic transfer functions, or manual acknowledge/cancel.
4. There are a number of initiating modules (supporting field devices) installed on the data communication loop (DCL) serving the sleeping rooms and common area conventional field devices. These consist of single and dual input modules. There is no C6.1 “Device Testing - Legend and Notes” and consequently no reference to model number, type, or wiring method. In addition all field devices (supporting and active) must be individually identified, and VERIFIED (this includes testing for supervisory, ground-fault, correct annunciation and operation).
5. There are a number of relay modules (supporting field devices) installed on the data communication loop (DCL) serving the various floors of the building. There is no Appendix C6.1 “Device Testing - Legend and Notes” and consequently no reference to model number, type, or wiring method. All fire alarm field devices (supporting and active) must be individually identified, and VERIFIED (see item 4).
6. There are no sensitivity readings recorded on the individual device test record sheets for any of the smoke detectors.
7. The function of a dedicated water flow relay (for offsite notification of a sprinkler trip) is not listed (or mentioned) on the test report (it was never supplied). This requirement is articulated in Sentence 184.108.40.206.(2) of NBC 2005.
8. The DSC PC-2525 security panel utilized to transmit fire alarm signals to the fire signal receiving centre IS NOT ULC Listed for use as a fire alarm communicator as is indicated on the C1 form.
9. There is inadequate protection of Data Communication Link circuit (not a single DCL isolator was found to be installed).
10. There are two (2) conventional heat detectors installed on the Data Communications Link circuit without benefit of a connection to a supporting field device. Activation of these detectors imposes a dead short across the DCL circuit which compromised the loop controller and, in the absence of the required isolation, resulted in a total communications loss with all the terminated field devices.
11. Audibility levels have not been documented (and likely not performed).
12. There are no power supply or emergency power supply (battery) test results (likely not even performed).
14. Specific test and inspection sections that must document the wiring for the project, as well as system response times, and specific testing of the Data Communication Links are missing. We have grave reservations these were even conducted.
Section 15 of ASTTBC’s Practice Guideline provides some good insight into the issue of responsibility, and which every building life safety systems service professional should consider adopting:
“The first duty of care of an ASTTBC Registrant is the protection of the public interest. Effective application of the ASTTBC Code of Ethics requires information regarding unethical practices and is to be reported to the ASTTBC Practice Review Board (and the local jurisdictional authority). This requires the combined efforts of FPTs, Owners and Fire Departments. It is through full vigilance by all those involved that violations of the ASTTBC Act and Regulations, Code of Ethics and Practice Standards can be addressed and the public interest served.”
Note: Underlined phrase is added here for clarification. “CFAA” and “ASTTBC” can easily be interchanged for those Canadian jurisdictions outside of British Columbia (and where a specific ASTTBC Bylaw has not yet been adopted for jurisdictions INSIDE British Columbia).
It is extremely important for any jurisdictional authority to not only understand the technical requirements involved in ensuring a fire alarm system is installed and functions in accordance with the design and CAN/ULC-S524, but to also be able to recognize a properly formatted Verification Appendix “C” report. In light of the requirements now stipulated in our National Building Code for the Commissioning (Integrated Testing) of a building’s life safety system, it behooves all parties involved to ensure that the documentation attesting to a properly conducted Verification is complete and presents an accurate reflection of this most crucial test a fire alarm system will ever undergo in its lifetime.
The role of an accredited Verifier (recognized by the AHJ) has never been more important at any other time in our industry’s history. Let’s get down to the business of addressing this. Let’s not put Public Safety into the hands of companies like Trunk Slammer Safety, Inc.
You can read more concerning technician practices, testing methods, etc. by clicking on:
Our Special Report on ASTTBC’s Fire Protection Technician Certification Program
Our Editorial EXTRA! (April 2015) - The Wolf on the Board!
Our Open Letter to ASTTBC (March 2014 Editorial)
Our September 2014 Editorial
Our August 2014 Editorial
More comments concerning ASTTBC technicians are in in our May 2012 Editorial
ASTTBC Complaint Outcomes (This actually makes for some pretty scary reading.)
CAN/ULC-S536 DO’S AND DON’T’S - Special Reports
AHJ Training Courses are being offered by two (2) National Associations:
The Canadian Fire Alarm Association (CFAA - Please visit their website for information on one being held in your area.
You can also visit our own Training Centre for available AHJ Course dates and cities!
INTERESTED IN COMMENTING ON THIS ARTICLE? QUESTIONS? GOT A STORY? SOMETHING OF INTEREST AND/OR NOTE-WORTHY?