Acceptance Testing

March 12, 2013
A new era of security technology means proving everything will work properly

The 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 enterprise-wide 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 gaining 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 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 if a fire alarm is activated, 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 normal usage parameters. For a door that is also monitored by a surveillance camera, part of the testing would 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 end-user has requested and is correctly labeled 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 end-user stating that every device has been tested and works properly. It is also important for the integrator to obtain an end-user’s approval on all systems tested and documentation provided once the testing process is complete. This limits liability once the system is turned over.

The Benefits

After the installation 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.

Once testing is complete, 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 as digital files. This full system documentation of the system ensures that the valuable information will not be lost if the end-user’s security executive or manager leaves the organization.

While acceptance testing can be a time-consuming process, it is obviously a valuable tool. It is estimated that at least 95 percent of integrated security systems today have been brought through the acceptance testing process. It protects the end-user’s investment from the beginning of the installation, ensuring that the systems integrators hired for the project is knowledgeable and provides quality work.

Tom Feilen is a member of the Tech-Net advisory group of Security-Net, an organization comprised of 19 independent systems integrators from throughout North America. He is also the Director of National Accounts for Koorsen Security Technology, a systems integration firm based in Indianapolis, Indiana. He can be reached at [email protected].

SIDEBAR: 10 Tips for the Testing Process

By Ray Bernard

Here are 10 items you should be sure your systems integrator is including in the acceptance testing process, from STE expert 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.
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 getting up-to-date as-built drawings.

Follow Ray's Twitter feed: @RayBernardRBCS.

About the Author

Ray Bernard, PSP, CHS-III

Ray Bernard, PSP CHS-III, is the principal consultant for Ray Bernard Consulting Services (, a firm that provides security consulting services for public and private facilities. He has been a frequent contributor to Security Business, SecurityInfoWatch and STE magazine for decades. He is the author of the Elsevier book Security Technology Convergence Insights, available on Amazon. Mr. Bernard is an active member of the ASIS member councils for Physical Security and IT Security, and is a member of the Subject Matter Expert Faculty of the Security Executive Council (

Follow him on LinkedIn:

Follow him on Twitter: @RayBernardRBCS.

About the Author

Tom Feilen

Tom Feilen is a member of the Tech-Net advisory group of Security-Net, an organization comprised of 19 independent systems integrators from throughout North America. He is also the Director of National Accounts for Koorsen Security Technology, a systems integration firm based in Indianapolis, Indiana. He can be reached at [email protected].