Issue link: https://securitytechnologyexecutive.epubxp.com/i/118926
TECHNOLOGY FOCUS By Tom Feilen Acceptance Testing A new era of security technology means proving everything will work properly T he introduction of IP-based, enterprise-wide and integrated security solutions has opened the door to more sophisticated access control and surveillance systems than ever thought possible. Needless to say, deploying those security systems has become much more complicated. Today, for example, an end-user can view surveillance at eight different offices in eight different states from a single, central location; or, a security director can manage an enterprisewide access control system ��� including revoking or granting access control privileges ��� for 10,000 global employees from the comfort of his or her desk at the company���s headquarters in Chicago. The IP, enterprise and integrated technology trifecta, of sorts, is creating endless possibilities, leaving end-users to figure out how to both deploy and leverage their security systems. That increased level of system sophistication comes with an added level of complexity. In this environment, systems integrators are now expected to formally and contractually prove that a successfully installed system works as outlined in a project specification document. This formal checks-and-balances process is gain- 10 Tips for the Testing Process Here are 10 items you should be sure your systems integrator is including in the acceptance testing process, from STE expert consultant Ray Bernard: 1. Test features in the same way you intend to use them. 2. Have the people who will use the system perform the test actions. 3. Verify that all systems are getting accurate time data from the same source. 4. Use video recordings to evaluate performance in all indoor and outdoor lighting conditions. 5. Check automated PTZ actions such as tours and returning to home position. 42 SECURITY TECHNOLOGY EXECUTIVE ��� April 2013 ing momentum in the security industry. Known as acceptance testing, the step-by-step process 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. This process can vary depending on the size of the project, but for a larger-scale installation, 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. Inside the Acceptance Testing Process While the specific process can vary from integrator to integrator, many follow a similar process with the end-user to ensure the system works accurately, along with 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 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 By Ray Bernard 6. In advance of the final test, execute a written test plan to check scheduled automatic actions. 7. Make sure each system does its part in key operational scenarios such as evacuation, lock-down or visitor management. 8. Simulate an incident and then perform the intended cross-system investigation and reporting actions. 9. Be sure to capture a written punch list and retest completed/corrected items. 10. Always insist on up-to-date as-built drawings. Follow Ray���s Twitter feed: @RayBernardRBCS. www.SecurityInfoWatch.com