Home » Magazine Archives » April 2008
Security Technology and Design
Most Read
Most Emailed
E-mail Article
Print Article
Operational Testing of Technology
Field tests can prove the effectiveness of security solutions
By Ray Bernard and James Connor
Operational testing is defined as the field testing, under realistic conditions, of an item, component or system to determine its effectiveness and suitability. By “operational testing” we do not mean the formal process known as Operational Test and Evaluation (OT&E) that is employed by the military services for testing of military systems and equipment — such as radar systems and helicopters. The subject of this article is a much less formal approach to operational testing that is appropriate for commercial off-the-shelf security technology.
Operational testing is different from acceptance testing, which is performed after purchase and installation of systems and equipment. Operational testing occurs prior to purchase, and is performed to ensure that the technology is suitable for the purpose and the environment intended. Manufacturers often provide equipment at no charge for such testing, unless the testing will result in wear and tear on (or partial destruction of) the equipment. Depending on the level of effort required to install the technology for testing, it may be appropriate to contract with a systems integrator to install and configure the technology for testing, and to develop a test plan if that is beyond the capabilities of in-house personnel.
The Full Spectrum of Testing
Operational testing is just one type of testing in the full spectrum of tests that should be applied to security technology. Currently, few systems integrators and security practitioners incorporate a phased acceptance test plan in the procurement of security systems. Years ago, when security technology was simpler and less integrated, acceptance testing basically consisted of a short demonstration, for which little preparation was required.
The complexity of today’s security products and systems warrants the full application of acceptance testing at appropriate points throughout the procurement cycle.
The Reason for Operational Testing
In recent years, information technology advancements have provided valuable features whose benefits call for immediate adoption. The traditional practice of waiting until a technology has been installed and field-proven for a few years postpones security benefits, and is also not warranted. Many, if not most of security industry technology advances are developments that have come from other fields, such as medical (vein recognition biometrics technology) or military applications (command-and-control software). In that sense, the technologies themselves are not new — their commercial security applications are new.
However, that does not mean that every technology will necessarily work in every desired security application. For example, video analytics for detection of objects on water may work well in one harbor but may not work in another, due to differences in wave characteristics.
Not all new security technology will require operational testing. For example, card reader technology is mature enough that a simple demonstration can usually provide evidence of its workability. However, a reader that is intended for outdoor deployment under harsh weather conditions should receive operational testing if it has not yet been deployed in such environments.
