Our process centers around video surveillance systems designed to meet your needs in a manner that takes into consideration your requirements, budget and environment. We then design a video surveillance system that solves your video surveillance problems, while fully integrating into your existing IT architecture. We start by gaining insights into the full spectrum of your video surveillance issues and help construct a video surveillance system designed for your needs and budget. We do this by using metric-based video surveillance comparisons and performance-based work statements.
Metric-Based Video Surveillance Comparisons
Under-specifying the video requirements can lead to a system which fails to meet expectations, while over-specifying can lead to unexpected increases in both implementation and total cost of ownership throughout the life of the system. The British government has developed common metrics for configuring and comparing video surveillance systems. We have adopted this system to help businesses, communities and educational facilities rationally decide between vendors and technology. The primary metric used is “identification by pixels per foot.” This system, when used in conjunction with the United States’ DCRI framework of detection, classification, recognition, and identification leads to a common language that can be used to describe and compare video surveillance systems.
About the DCRI Framework
The Detection, Classification, Recognition, Identification (DCRI) framework helps government security professionals define the purpose and image quality needed for their video security systems, but it can also be used to help design and understand your video surveillance system. Using this framework creates a common language that makes it easier to ensure the required level of imaging is fully understood by all parties involved in the system selection and installation process.
Performance-Based Work Statements
More government agencies are now requiring performance-based work statements (PBWS) instead of the traditional request for proposal (RFP) and we have fully adopted this way of doing business because we believe in delivering results-based proposals that focus on the end results, not just the technology. The PBWS will contain the goals of the project, the tasks to be undertaken by the vendor, and the scope of work. It will also contain the purpose of the contract, acronyms and definitions, a performance work statement (PWS), government-furnished resources (if applicable), skill or relevant experience requirements, and contract deliverables. Outlining the project in this way makes it more clear what is involved in the project and what the client is to get in return.