The next revolution in the security industry

It seems to me, and I’ll welcome all opposing or supporting observations, that the next revolution in the electronic security industry is forming on the horizon. I claim no special ability to foresee the future, as is evidenced by the fact that I still own TYCO stock that I purchased in the late 90s, but I’m certain that the next revolution in our industry will be in the prevalent use of SDKs and APIs for integration of disparate systems. Technological advances such as the .NET framework and Linux OS have opened the door for the integration of computer based systems in ways that we have just never seen before. If you’re an access control, CCTV, digital video, intercom, ID badging or other building systems manufacturer you are no longer operating in a closed environment and the proprietary systems of years gone past either have or will be replaced by systems that adhere to conventional standards and protocols. Even, and some would argue especially, if you are a security peripheral device manufacturer such as cards, readers, cameras, and sensors you will need to learn to live and prosper in an open protocol environment. This is good news for the manufacturer, the systems integrator or service provider, as well as the end user. This win-win-win scenario creates, in our industry, a momentum that simply can’t be denied.

Currently, in the traditional manufacturer-to-integrator-to-end user market channel, the two end players are providing the market pressure to comply to open standards and to provide a usable SDK for development with their products. The manufacturers are realizing the benefits of having multiple third-party subsystems seamlessly integrated with their core software and hardware offerings and the end users are realizing that if they choose the right integrator they can have a customized system that meets their exact needs. The more forward thinking integrators are now capitalizing on the end user’s new paradigm and they are hiring or training their staff to be able to provide customized software development using the SDKs and APIs available from the manufacturers.

If you’re a sophisticated security system end user you have probably already figured out that if you want a specific DVR or badging system, for example, to integrate with your access control system you need to choose an integrator with software development capabilities. If you do, you’re likely to get what you want. If you’re a system integrator you’ve probably run across opportunities to provide integrated systems that required high level software integration using a manufacturer’s SDK. And if you are a manufacturer you’re probably beginning to realize that in order to stay competitive and to provide all the features and flexibility that the end user wants, you will necessarily need to open up your system to third party developers. These forces in the market require that we all use open standards. I, for one, believe that it is coming and that it is a good thing for our industry.

Purpose of ElectronicSecuritySystems blogspace

The purpose of this blog space is to provide a forum to facilitate information exchange and networking for manufacturers, resellers, integrators, and end users of electronic security systems. All posts appropriate for those with an interest in electronic security are welcome; however, special emphasis on new technologies and disparate system integration using an SDK is encouraged.