• Bosch Intrusion integration protocols are OS agnostic: they can be used with any operating system; even embedded systems, providing the flexibility to integrate Bosch control panels with nearly any partner.
• Connections to third party integrations do not prevent the Bosch Intrusion Panel from an additional connection to a central station. Simultaneous connection to both the third party integration and central station allow a customer to maintain the same level of security while increasing their system’s capabilities.
• Bosch Intrusion Integration Tools include support for TLS (transport layer security) encryption. TLS and its predecessor SSL are designed to provide communications security. This prevents data delivered over the Bosch Intrusion Integration Protocol from being tampered with or inspected by a third party.
• The use of Bosch Intrusion Integration Tools is not open to everyone and requires Authentication. This Authentication requirement allows users to more effectively manage and maintain third party integrations.
• Traditionally, anytime another system needed access to data from a device, a custom interface, or driver, needed to be written. Because of the OPC standard, every OPC Client knows how to communicate with every OPC Server automatically. The OPC Server converts Bosch’s Intrusion Integration Protocol (Mode 2) into a method that an OPC Client knows how to work with. This eliminates the need for a custom interface.
• Getting started on your integration is simple because Bosch Intrusion Integration Tools use a TCP connection. TCP provides reliable, ordered, and error-checked delivery of data between applications.
• Integrations remain stable across panel firmware revisions. This backwards compatibility preserves investments made into initial integrations by preventing rework when new firmware is released.