Embedded Files
Trust, but Verify: Why Your "Finished" Security System Might Not Be Ready
Date: February 14, 2026
Category: Project Management / Commissioning
You have just invested a significant budget into a new security upgrade. The cameras are mounted, the card readers are beeping, and the monitor wall in the control room looks impressive. The systems integrator hands you the keys and says, "It’s all working."
But is it?
In our experience auditing high-level security projects, there is a dangerous gap between a system that is installed and a system that is commissioned. Relying solely on the installer's word that "everything is fine" is a risk no facility manager or business owner should take.
Here is why true commissioning is the only way to ensure your technology actually works when a crisis hits, and how to choose the right architecture to make that success possible.
The Difference Between "Testing" and "Commissioning"
To the non-technical eye, these two words look the same. In the industry, they are worlds apart.
Testing is checking individual components. Does the camera turn on? Yes. Does the door unlock when I present a card? Yes.
Commissioning is a systematic process ensuring all those components talk to each other and function as a unified solution during real-world scenarios.
We often see projects where the cameras work and the alarms work, but they fail to work together. For example, we recently reviewed a site where motion sensors were installed to control lighting and security. The test passed (the sensors detected motion), but because the systems weren't integrated, the lights turned off while the security system failed to arm.
Running the Real-Life Scenarios
At Anderson Consulting Partners, we don't just check if the power light is green. We run Acceptance Testing, which involves simulating live events to verify the "cause and effect" logic of your system.
Here are three scenarios we verify that a standard installer might miss:
1. The "Lockdown" Stress Test It is easy to lock a door. It is much harder to lock 50 doors instantly while keeping emergency exits open for evacuation.
Our Test: We trigger a lockdown event. We don't just look at the screen; we physically walk the perimeter. Did the designated doors lock? Did the access fobs for general staff stop working? Did the Executive and Security fobs keep working? Did the CCTV system automatically pop up the relevant camera feeds on the operator’s main screen?
The Goal: We ensure the "logic" of the system matches your emergency protocol.
2. Fire Evacuation Integration When the fire alarm triggers, your access control system needs to release specific doors to allow safe egress.
Our Test: We simulate a fire alarm input. We verify that magnetic locks release immediately. Crucially, we check that the CCTV system bookmarks this event so you can instantly find the footage later to review how the evacuation flow looked.
3. AI and Analytics: The "Invisible Fence" Modern AI can detect a person entering a hazardous zone or a vehicle loitering at a loading dock. But if that alert is buried in a menu, it is useless.
Our Test: We stage a live breach. We walk into the zone. We verify that the camera detects the human, categorises them correctly (not as a stray dog or blowing leaves), and, most importantly, sends an audible and visual alert to the control room operator within seconds.
The Secret Sauce: Choosing "Open" Architecture
Why do some systems fail these commissioning tests while others pass with flying colours? It often comes down to the software architecture you choose.
Many security vendors try to sell "proprietary" systems, where the camera, the recorder, and the viewing software are all made by the same company. They claim this is safer, but it often traps you. If you want to add a specialised AI camera from a different brand later, the system rejects it.
We recommend Open Platform Systems.
Think of an Open Platform like a smartphone operating system. It doesn't care what brand of "app" (camera or sensor) you download; it just makes them work together smoothly.
User-Friendly Verification: In an open system, verifying an event is fast. You can drag and drop a camera, search for "Person, Red Shirt, Tuesday," and get results instantly. This makes commissioning, and daily use, incredibly simple.
Future-Proofing: If you need to upgrade your AI analytics in three years, an open system lets you update the software without ripping out the hardware.
Why Contact Anderson Consulting Partners?
The contract you sign with your integrator usually requires "Acceptance Testing" before the final payment is made. This is your only leverage. Once you pay that invoice, fixing "glitches" becomes expensive.
You need an independent advocate who speaks the language of the technical teams but represents your interests.
Anderson Consulting Partners specialises in:
System Selection: We help you choose open, flexible platforms that avoid vendor lock-in.
Independent Commissioning: We validate the system against your operational requirements, not just the manufacturer’s spec sheet.
Operator Training: We ensure your control room team understands the alerts they are seeing.
Don't leave your security to chance. Ensure your system is rigorous, integrated, and fully commissioned.
Our goal is to look beyond the hardware and collaborate to make the world a safer place together.
Please Note: The information provided in these articles is general in nature and intended for educational purposes. Every operational environment has unique vulnerabilities; therefore, it is recommended to seek site-specific expert advice for your specific needs.
Page updated
Report abuse