The Road (So Far) to Nonproprietary Electronic Security Systems

Three experts discuss the advancements and struggles the electronic security industry has experienced in efforts to move toward open architecture security platforms.

It has been more than a decade since the intertwined topics of open systems, standards and convergence entered the physical security industry debate. But what does it all mean and how much progress are we making?

When we talk about systems as being open it is usually a matter of degrees. Products that are open are easy to integrate in order to build new or complex solutions. Generally, the more open, the easier it is to build solutions.

Standards are related to openness but one doesn’t have to adhere to a standard to be open. This is where the IP camera industry programming protocols are today: Most cameras have open protocols; they are published and often provided in the documentation that comes with the camera. But even though they’re open, the fact that each manufacturer invents its own protocol vastly increases the workload for video management system (VMS) software providers. This problem is solved by the adoption of standards.

Related Article: The Top 7 Video Surveilance Trends to Watch in 2011 

In theory, as camera protocol standards emerge, some of the R&D investment that VMS manufacturers make today will go into developing new features rather than supporting new cameras. This is exactly what happened among IT equipment makers. Once standards take hold, manufacturer compliance is not optional. In IT networking, vendors that supported industry-wide standards flourished, while the old-school proprietary network providers disappeared – a cautionary tale for our industry.

Related to the whole open/standards discussion is the concept of convergence. Convergence is about moving security data using the tools developed by the IT world. It is not possible to leverage an investment in IT infrastructure without abiding by the standards supported by that infrastructure, and so the security industry is adopting those standards. As a result, the world of IT data and security data are converging.

This convergence is painful for manufacturers that developed their product lines before the standards were drawn. Hence, they are faced with having to reinvest in those older product lines in order to evolve them to work in the new paradigm of converged data communication. That reinvestment is significant, requiring research, development and recertification of the result. Products developed after the standards had taken root do not suffer that cost.

But more than the manufacturers’ burdensome efforts to adapt old products to new technologies is that convergence weeds out inadequate or outdated products. In many cases, products remain on the market not because of their competitiveness, but because they are the only products that integrate with a manufacturer’s proprietary (read: closed) systems. Once the consumer has a choice, the need to buy the inadequate closed product disappears.

As a result, schools, universities and hospitals benefit and at least some manufacturers suffer, all of which creates a tension that forces progress while simultaneously resisting that progress. It’s all a very dynamic situation.

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

Leading in Turbulent Times: Effective Campus Public Safety Leadership for the 21st Century

This new webcast will discuss how campus public safety leaders can effectively incorporate Clery Act, Title IX, customer service, “helicopter” parents, emergency notification, town-gown relationships, brand management, Greek Life, student recruitment, faculty, and more into their roles and develop the necessary skills to successfully lead their departments. Register today to attend this free webcast!

Get Our Newsletters
Campus Safety Conference promo