SECURITY SYSTEMS INTEGRATION. Santiago Beron, RCDD, CTS TLC Engineering for Architecture

Transcription

1 SECURITY SYSTEMS INTEGRATION Santiago Beron, RCDD, CTS TLC Engineering for Architecture

2 Security System Integration The term integration is widely used in cut sheets, manuals and every day meetings. It s a broad concept that usually means different things for different people and is very project specific. This wide interpretation can create differences in the level of expectation among the project stakeholders (owner, consultant and contractor).

3 Definition of Integration Integration can be defined as a collection of unique features available to the user of a security system after two or more security subsystems have been allowed to share some of the information particular to each subsystem. Having many subsystems in one project does not mean the system is integrated. The list of unique features available in a system is the major source of discrepancy between stakeholders.

4 Integration Features Examples of features: Door Alarm to camera preset. Video analytic alarm to access control map GUI. The list of available features depends on: Type of subsystems available in the system. Quantity of subsystems. Brand name of each subsystem. Model number/ software release of each subsystem. Integration method used.

5 Integration Roadmap Establish early on in the project a list of integration features that are required for the project. This levels the expectation and creates a framework for bidding and testing the system. It is required to list not only what the system will be capable of doing, but what level of effort is required by the contractor doing the work. Hiring an integrator does not guarantee that the final system will be integrated. It just means there is a single point of contact/single point of responsibility (SPC/SPR).

6 Why integrate a system? Advantages Task Automation (i.e. conditional events) Unified Graphical User Interface (GUI) As a consequence of the first two, a faster response takes place (correlation between events). A dominating GUI needs to be selected for the system. This selection is critical to establish the list of features that will be available to the system.

7 HOW TO INTEGRATE There are 3 basic methods of integration: Relay integration Serial line integration Application integration All 3 methods can be present in a system or any combination of them. At least one method needs to be present.

8 RELAY INTEGRATION The status of one relay in one subsystem (NO/NC) signals a feature to another subsystem. This type of integration is unidirectional, point to point and does not allow for analog values. It is software independent and usually limited by the complexity of the map set by the installer/designer. The details of the relay map are the key to this type of integration.

9 RELAY MAP SUBSYSTEM A OUTPUT 1 (Door 101 in alarm) OUTPUT 2 (Door 108 in alarm) Input 1 (Video motion in lobby area) SUBSYSTEM B INPUT 1 (Camera 1 preset 1) INPUT 2 (Camera 1 preset 3) Output 1 (Encoder 1, relay 3 VM)

10 SERIAL LINE INTEGRATION An RS-232, RS-422 or RS-485 line that allows commands (or ASCII strings) to be sent from one subsystem to another. Each command represents a feature or an action to be taken by the other system. It is mostly unidirectional but could be bidirectional. Analog values can be sent. It is a point to point connection.

11 SERIAL LINE INTEGRATION SUBSYSTEM A SUBSYSTEM B CPU A SERIAL MONITOR 1 CAMERA 1 LINE PANEL CPU B CAMERA 2 STRING 1 (Select monitor 1): 1Ma STRING 3 (Select camera 2 in current monitor): 2#a STRING 5 (Select preset 3 in current camera): 3#a STRING 2 (Acknowledge): AKa STRING4 (Acknowledge): AKa STRING6 (Acknowledge): AKa

12 SERIAL LINE INTEGRATION Two types: Closed set Open set It is manufacturer dependant. New subsystems can be integrated if one of the subsystems is open set. Simplifies complexity of relay maps, but has some limitations.

13 APPLICATION INTEGRATION Two or more applications incorporate a set or rules and software routines (API) to exchange information. They will use a network connection (TCP/IP, Lonworks, Modbus, etc) to transport information. Having those connections do not guarantee integration. Similar to a closed set serial integration, an open set is not possible. New subsystems can be added only at the factory. It is bidirectional, but could be unidirectional. It could be point to multi-point.

14 APPLICATION INTEGRATION SOFTWARE A SOFTWARE B CPU A CPU B CAMERA 1 PANEL CAMERA 2 NETWORK SWITCH

15 APPLICATION INTEGRATION A subsystem having an open API does not mean it is already integrated with other subsystems. Changes in software (new releases) could affect the integration of subsystems. Business plans are sometimes the biggest obstacle in the application integration process. The manufacturer dependant integration approach is fading away and not usually the best value for the owner.

16 WHO INTEGRATES A SYSTEM? The goals and scope need to be set by owner and designer. The manufacturer prepares software platforms. Integrators make it happen in the field. Owner and designer needs to check for goals/scope after completion.

17 THE COST OF INTEGRATION Manufacturers might charge for adding an API. Software set up time by integrators has to be described in the scope. Selecting the dominating GUI limits competition. The tighter the integration the more selective it gets. Some features might not be cost effective.

18 INTEGRATION VERIFICATION Test every single feature. There are too many things that could go wrong. Get relay maps, master passwords and as-built information from integrator. Backup all subsystems settings right after successful testing, and after every change.