Parsing PSIM’s Advantages and Complexities

Physical security information management (PSIM) promises many client benefits – with proper planning.

If PSIM is the best option, there are some things to watch out for during the scoping and deployment phases. Having a detailed scope or statement of work (SOW) is key. This will help set proper expectations and ensure all major players are on the same page. In turn, this will help establish guardrails to contain scope creep. The process of creating this document should be an iterative one involving all stakeholders and requires a deep dive into the customer’s security operations and protocols.

The enhanced GUI and functionality may also breathe new life into legacy systems, extending their usefulness and reducing costs, compared to a rip-and-replace.

Another area to pay close attention to in the early stages is which systems will be integrated into the PSIM, as well as the methods of integration and the functionality exposed within those methods. For example, if multiple video systems are being implemented, each will have its own software development kit (SDK) to facilitate the integration. One SDK may only allow for the display of live video, while another may allow for live video, re-corded video and alarm events. Understanding the limitations imposed by the various subsystems is imperative for an accurate scope.

RELATED: Physical Security Market Projected to Be Worth $88B by 2019

Ongoing System Maintenance, Upgrades Required

Once the PSIM is deployed and operational, the work and planning don’t stop. The customer will inevitably discover some areas to tweak, and perhaps identify new areas and situations where the PSIM can provide additional value through operator efficiency and process standardization. Planning is especially critical when upgrading not only the PSIM, but the underlying subsystems. For example, the customer may want to upgrade its VMS to gain some new functionality, support a new IP camera or engage the latest PC operating system. Beforehand, the integration method between the PSIM and the VMS should be evaluated to ensure compatibility. Is the new VMS software backward compatible, or will the PSIM integration piece need to be updated as well? This could require extensive software development and regression testing and should be factored into any schedules and potential costs.

Understanding your customer’s needs and existing systems are the first steps to designing the right PSIM solution. By keeping in mind and planning for some of complexities that PSIM brings, integrators can ensure a successful deployment.

 

If you enjoyed this article and want to receive more valuable industry content like this, click here to sign up for our FREE digital newsletters!

About the Author

Contact:

Bob Stockwell pens Security Sales & Integration’s “IT Intelligence” column, which covers network security. He is Chief Technology Officer for Stanley Security.

Security Is Our Business, Too

For professionals who recommend, buy and install all types of electronic security equipment, a free subscription to Commercial Integrator + Security Sales & Integration is like having a consultant on call. You’ll find an ideal balance of technology and business coverage, with installation tips and techniques for products and updates on how to add to your bottom line.

A FREE subscription to the top resource for security and integration industry will prove to be invaluable.

Subscribe Today!

Get Our Newsletters