How do you deliver demonstrable quality?
For high-quality security solutions, you choose reputable systems and a well-regarded system integrator.
But what determines that quality?
On the basis of the technical specifications, an initial assessment can be made about the quality of a solution.
However, quality is a subjective concept and depends on more factors, such as the requirements set.
These may be laid down in standards, but there may also be additional situation- or location-dependent requirements. We speak with Michiel de Graaf, Business Development Manager at Mactwin, about demonstrably delivering quality.
“When it comes to the quality of security solutions, assessing technical specifications alone is not enough,” says De Graaf.
It starts with the starting points
“Take camera surveillance and in particular the quality of the images. In the media, we regularly hear critical voices about the quality and usability of camera images after a crime. We don’t know whether that’s justified, and we can only judge when we know the starting points [see below, ed.].”
Examples of the starting points of the camera system:
- What is the purpose of the camera system?
Is it about (forensic) identification, recognition, observation or detection? - What specific circumstances should be taken into account?
Think of (back)light, weather conditions and day or night situations. - What are the functional requirements and wishes?
Type of housing, whether or not you can control the cameras, image storage, infrared lighting, image resolution, type of lens, etc.
“Whether cameras have the required functions and are suitable for the specific conditions can often be quickly assessed on the basis of the technical specifications,” says Michiel de Graaf.
“But that doesn’t automatically mean that the cameras deliver good or usable images. Only when the image quality is sufficient to achieve the predetermined goal – for example, identifying people or providing an overview – can you speak of a good picture.”
Standards and practice
The NEN-50132 describes the 4 possible objectives for camera surveillance and provides a guideline for each objective with regard to the extent to which faces must be recognizable.
Image resolution plays an important role in this.
De Graaf: “But lighting conditions and the positioning of the camera also influence the ability to portray people in a recognizable way. In order to be able to properly assess the image quality in relation to the objective, Mactwin uses, among other things, its own version of Rotakin (see next page). We also pay a lot of attention to configuring and testing the camera system. The latter, if necessary, in a day and night situation. And by technically monitoring the camera system (remotely), we and our customers know at any time whether the system is still providing good camera images.”
Opinions differ on what constitutes good image quality.
De Graaf: “It may sound crazy, but a distorted or slightly discoloured camera image can be fine as long as it meets the pre-formulated objective.”
Standards and guidelines have also been established for burglary and fire alarm systems.
“But here too, meeting the standards is no guarantee for a well-functioning system,” says de Graaf.
“Standards and guidelines provide guidance for claimants such as insurers. But is that enough? It is important to always have a clear understanding of the objectives of the system, regardless of the applicable standards and insurance requirements, and to take into account the specific wishes and circumstances. In the case of high-risk objects, more measures are sometimes required than the standard prescribes, such as extra delaying (structural) measures. If you want to be sure that a safety or security system meets the applicable requirements, a practical test is necessary.”
Self-developed quality tools
“At Mactwin, we are always looking for ways to improve the quality of our activities.
In the context of BIESS (Best practice for Implementing Effective Security Solutions), for example, we have developed all kinds of tools to guarantee the quality of the chosen and implemented security solution.
These tools are based on our many years of experience with security projects in all kinds of industries.
We analyzed successes and failures and identified the critical success factors.
And we have translated this not only into practical documents, templates and white papers, but also into effective solutions and a structured and standardized approach.
A good example is our Octagon Security Methodology. This is an instrument for dividing a building into security areas based on the valuable goods, information or processes present. Security measures can then be established for each area transition (e.g. from ‘public’ to ‘secure’). The Octagon Security Methodology results in coherent and balanced measures that allow organizations to be and remain in control of security. Within Octagon, we have developed best practices for different types of buildings.”
According to the standards, a Rotakin can be used to visually assess whether the camera images are suitable for identification or recognition purposes.
In the picture you can see a modified “Rotakin” that is used by Mactwin to adjust cameras.
Testing & Maintenance
“Finally,” says De Graaf, “we think it’s important to test the products we carry as much as possible.
At home or on location with, for example, a camera shoot-out.
Quality control does not stop after completion.
To ensure that security systems function properly over a longer period of time, maintenance is required, but also, for example, image quality checks. This can be done, for example, with a periodic remote health check, taking care of backups and software updates and by continuously monitoring technical malfunctions. In this way, we identify malfunctions preventively; as soon as the system is in danger of crashing. We can then quickly and often remotely avert an impending malfunction, so that the processes at our customers can continue unhindered and security remains at the desired level.”
