C H A P T E R 2
The pros and cons of system integration
An integrated physical security platform is made up of connections. Systems integration has become a popular substitute for traditional interfacing as a result of advancements in technology and increased collaboration between manufacturers. Standard protocols and software development kits (SDK) are most often used to physically or functionally connect different systems and software applications.
Standard protocols are powerful and generally considered to be more effective than an SDK
They support a mix of operating systems and allow users to manage applications in real time. Standard protocols are popular for edge-device integrations, like IP cameras or door controllers, but are most commonly used between two software applications. However, as opposed to using an SDK, integrating two systems through a standard protocol is time consuming and may require a shared database between the systems.
An SDK, also referred to as an application programming interface (API), consists of a DLL package created and distributed by software manufacturers that allows other manufacturers to integrate with their systems. SDKs simplify the integration by hiding complex mechanisms from other software developers, including authentication, video decoding, and complex standard protocols.
Benefits of systems integration
Integrated systems can give you the tools you need to become more efficient. For example, an integrated access control and video management solution may display live or playback video associated with an access control event from the access control user interface.
Another benefit is that you don’t have to rely on a single manufacturer for an entire security system. Working with integrated solutions allows you to deal with multiple independent vendors, each with their own ecosystem of technology partners.
Problems with systems integration
While systems integration can achieve a deeper level of product integration, there are some drawbacks to this approach:
- requires you to use multiple systems as none of them independently offer the required functionalities in one user interface
- forces operators to move back and forth between systems
- prevents you from modernizing your processes gradually to overcome new threats, since advanced functionalities might be supported at the time of installation, but eventually new features won't
- increases maintenance time, with two or three independent systems to configure and keep synchronized
- affects the way integrations work and can even cause integrated systems to lose compatibility, especially when there are adjustments to the SDK or API
