Articles by Tom Feilen
Significant technological advancements have created endless possibilities in how security is not only deployed, but also leveraged by the end user – the customer. For example, customers can now view surveillance at eight different offices in eight different states from a single, central location. A security director can manage an enterprise-wide access control system, including revoking or granting access control privileges, for 10,000 global employees from a company’s headquarters. However, with that increased level of system sophistication comes an added level of complexity. After successfully completing the installation of a security system, integrators are now expected to formally and contractually prove that the system works as outlined in the project specification document. Tom Feilen, Director of National Accounts for Koorsen Security Technology explains that this formal checks and balance process is gaining momentum in the security industry. The step-by-step process of Acceptance Testing is more commonly being written into bid specifications, especially for projects that require the expertise of an engineer and/or architect. Simply put, it is a way for the end user to make sure the system they paid for works properly and is delivered by the integrator as outlined in the project’s request for proposal. While Acceptance Testing can be a time consuming process, it is a valuable industry tool. It is estimated that at least 95 per cent of integrated security systems today have been brought through the Acceptance Testing process. Security systems have become more complicated in recent years. The introduction of IP-based, enterprise-wide and integrated solutions have all opened the door to more sophisticated access control and surveillance systems than ever thought possible. This process can vary depending upon the size of the project, but for a larger scale project, it is not uncommon for Acceptance Testing to take several weeks from start to finish. This timeline can be especially lengthy when the project involves hundreds of devices, such as access control readers, surveillance cameras, video recorders, intrusion sensors, and intercom systems. Most integrated security systems today have been brought through the Acceptance Testing process What is involved in the Acceptance Testing process? While the specific process can vary from integrator to integrator, many follow a similar process with their customer to ensure the system works accurately and that the customer has the proper certification documentation. The initial part of the process typically involves generating a report of each device installed as part of the system. This list enables the systems integrator to systematically test each device ensuring that individual devices are not specific points of failure for the overall system. For example, in a building equipped with a system that automatically releases the egress doors upon the fire alarm activation, it is important to make sure each door’s electro-magnetic locking system is operating properly. The systems integrator would not only test that a door releases when the fire alarm sounds, but also to make sure the access control system is notified if the door is propped open or held open longer than in normal usage parameters. For a door that is also monitored by a surveillance camera, part of the testing would also involve making sure that an image being transmitted to a video monitor is coming from the correct surveillance camera and that the actual angle of the image is what the customer has requested and is correctly labelled as such. If a device does not function as it should, it is then added to a punch list that would require the systems integrator to repair that device within a certain period of time. Once repairs are made, the system integrator would then submit a letter to the client stating that every device has been tested and works properly. It is also important for the integrator that once the testing process is complete to obtain a customer sign off (Certificate of Acceptance) on all systems tested and documentation provided. This limits liability once the system is turned over. From a safety perspective, Acceptance Testing is also used to verify that T-bars and safety chains are installed on cameras that are mounted in drop ceilings. It can confirm that panels are mounted in a room that is properly heated and cooled to avoid major temperature swings. Also, as part of the Acceptance Testing checklist, it can insure that power supplies that drive all the security systems are properly rated with the recommended batteries for back-up. And, that emergency exist devices or card readers are not mounted more than 48-inches above ground. An Acceptance Testing process serves to protect the end user's investment After the project is complete, Acceptance Testing protects both parties involved against liability issues. One example is if the building has a fire and the functionality of the life safety system comes into question. Acceptance Testing can be used to prove that the system was able to function as specified and dispel any concerns about its performance. At that time, all close out sheets are turned in, along with as-built drawings and a manual providing a complete listing of each device and system installed. Today, these manuals not only come in paper form as part of a large binder, but also digital files saved to a disc. The benefit of providing the customer with a binder or documentation of the system is that should the end user/customer replace the person who manages security at the company, valuable information will not leave with that former employee. While this checklist to close out a project may appear trivial at first, it is an important part of the security project process. By implementing an Acceptance Testing program, it serves to protect the end user’s investment, ensuring that the systems integrators hired for the project is knowledgeable and provides quality work. For the integrator, it helps towards the end goal of a satisfied customer.