Scan our QR code for more exciting content from ICD!

Common Security System Implementation Mistakes

 

In this post, we look at some of the most common security system implementation mistakes observed by ICD during more than a decade of project management experience.

 

MISTAKE 1: Not adding the security scope at the beginning of the project

Even though security systems are a crucial part of any construction project, project management tends to focus on security last, after decoration work is completed. This can create significant challenges and higher costs later on, particularly if more conduit work and cabling is required for the security system.

 

HOW TO AVOID IT: Start planning for security straight away and involve the security vendor at the start.

The sooner end user companies accommodate security into the overall project plan, the easier it is to avoid problems down the road. Involving a security integrator partner at the beginning of the process can also help end user companies plan security implementation more effectively. It can also significantly lower the cost of a project’s security component.

 

MISTAKE 2: Not checking for specific building requirements with the landlord

Many end user companies forget to check with the facility landlord to see if there are any requirements related to door elevation or layout. These are most commonly affected by the installation of cameras and access control doors. Any design that doesn’t follow the requirements of the property landlord may require extensive revisions consume valuable time.

 

HOW TO AVOID IT: The security team should take responsibility to deal with any building requirement issues in advance.

End user companies should make sure that they have permission from landlords to implement all aspects of the security design in advance, especially camera and door installations. It is also useful for end user companies to approach their security partner for advice during this stage.

 

MISTAKE 3: Failing to reach an agreement between the security team and the end users on the security scope

This problem often occurs because security management teams are often centralized and dedicated security personnel are not present on each site. If security teams are unable to agree on security requirements with end users, this can result in changes in the security scope while implementation is taking place. This often means significant delays to completing the project, as well as increased costs.

 

HOW TO AVOID IT: Establish clear security standards and confirm requirements before starting project implementation

Security teams therefore need to take responsibility for improving internal communication and making sure the relevant personnel on each site are onboard with security requirements before the project begins. This can be achieved by establishing clear security standards that are fully understood by site end users

 


These are just a few of the common security system implementation mistakes that end user companies often make. Though there are more examples out there, companies can achieve significant cost savings and increased efficiency just by addressing these three issues.

 

For more tips on security, follow ICD on our LinkedIn Company Page.

 

Click the button below to share this article: