P2000 and Metasys System Integration

Transcription

1 P2000 and Metasys System Integration Product Bulletin Code No. LIT Software Release 3.14 SP1 Issued June 23, 2017 The Johnson Controls P2000 Security Management System supports the integration with the Metasys Building Management System to increase energy efficiency and aid a P2000 operator in alarm verification. The Metasys system uses web-based technology to monitor and supervise facility controls such as HVAC, lighting, and fire control systems. This high-level integration gives Metasys operators the ability to access certain key security management features of the P2000 from the Metasys web-based user interface. See Figure 4 on page 3. The Metasys operator can use the interface to view P2000 Host and Panel () objects, view alarms and messages, send access control commands, and create interlock events. Interlocks enable the Metasys system to react to an event from the P2000 system, such as an intrusion alarm triggering the lights in that area to turn on for better visibility. In Metasys Release 6.5 or later, P2000 systems are able to receive alarm messages from selected objects in the Metasys system. This allows a P2000 operator to react to issues with facility controls where there is no permanent facilities operator or after hours. Table 1: Features and Benefits (Part 1 of 2) Features Benefits Metasys Alarm Monitoring Building Control and Security Management Integration Integrated User Interface Alarm Management Door Control Refer to the QuickLIT website for the most up-to-date version of this document. Figure 1: View P2000 Objects from the Metasys Interface Allows the P2000 system to receive alarm messages from selected objects in the Metasys system with the use of P2000 SNMP Trap Receiver. This enables a P2000 operator to react to issues with facility controls where there is no permanent facilities operator or after hours. Provides significant savings. Facility costs can be reduced by increasing energy efficiency (for example, presenting a valid badge at an access control entry point triggers lighting and temperature controls in the room). When an area of the building is unoccupied, lights and temperature control can be turned off, saving the company money on electricity costs. Allows a single user to monitor both the HVAC and lighting system and security system, eliminating the need for two separate users at certain non-prime hours. Enables Metasys operators to receive, acknowledge, snooze, and discard alarms for registered P2000 devices. See Figure 11 on page 8. Enables Metasys operators to issue P2000 door commands from the Metasys user interface (see Figure 8 on page 6). The operator can choose to lock or unlock a single door or all doors, as necessary, managing the accessibility through specified access points without having to find and log on to a P2000 workstation. For example, Metasys operators can send a command to lock or unlock doors during a security breach or threat. P2000 and Metasys System Integration 1

2 Table 1: Features and Benefits (Part 2 of 2) Features (Continued) Benefits Interlocks Status Monitoring Output Point Control Event Monitoring and Message Forwarding Offer customized event trigger and action sequences (cause and effect) between the Metasys and P2000 systems (see Figure 2 on page 2). Interlocks are events generated on the P2000 resulting in actions on Metasys objects. For example, a motion detection input triggered in the P2000 system can turn on a light controlled by the Metasys system, giving guards the visibility to track a potential intruder. Interlocks can only be configured on the P2000, and are unidirectional from the P2000 to the Metasys system. Allows Metasys operators to monitor the status of P2000 controllers, doors, input points, and output points using the Metasys web interface, enabling them to take action (see Figure 10 on page 7). Door status changes can indicate a possible breach, and device status changes can indicate a possible hardware or software issue that may require immediate attention. Allows Metasys operators to control P2000 output points using the Metasys web interface. See Figure 9 on page 7. Provide Metasys operators with forwarded P2000 filtered history transaction (see Figure 3) and alarm events through the Metasys event repository, allowing Metasys operators to view P2000 Real Time messages. For example, operators can track cardholder access through the building using the Metasys interface, as each access grant event message indicates the cardholder, access point, and time when the P2000 system granted access. Figure 3: Filter Messages for Metasys Operators Figure 2: Create P2000/Metasys Interlock Events 2 P2000 and Metasys System Integration

3 Metasys Workstation Site Director MONITOR Metasys and P2000 Systems Communicate Alarms and Events Between Systems Metasys and P2000 Operators Can Send Commands From Their Native Workstations Between Systems P2000 Workstation CONTROL P2000 Server Integration Overview Figure 4: P2000 and Metasys System Integration In a Metasys environment, registered devices and objects can be accessed using Metasys Web Services. The P2000 must first be enabled with Web Services to be used by the Metasys system. Once correctly installed, available P2000 functions are visible, and the Metasys operator is able to read or change object attributes, or send commands to the objects. The P2000 folder in the Metasys Site Management Portal contains a subset of P2000 objects. The Panels folder contains configured portals (or readers), inputs, and outputs. See Figure 5. P2000 and Metasys System Integration 3

4 Device P2000 HostEngine Panels Panel #1 Portals Portal #1... Portal #2 Portal #N Inputs Outputs... Input #1 Input #n... Output #1 Output #N 0 - N 0 - N Inputs Iterm #1... Iterm #2 Iterm #N Input #1... Input #N 0 - N Outputs Panel #2... Figure 5: P2000 Objects Visible in the Metasys System 4 P2000 and Metasys System Integration

5 Systems Integration Architecture Communications between the P2000 and Metasys systems occurs over an IP network. Figure 6 displays a possible integration configuration using Johnson Controls security products, such as the CK721-A and S321-IP controllers. Web Browser ADS/ADX Tower P2000 Server IP Network Wide Area Network (CKM-EP1501) (CK721-A) (S321-IP) (NAE) (NAE) Reader Module (RDR2SA) Lighting HVAC Reader Readers Readers Figure 6: Possible Integration Configuration (Johnson Controls Security Products) Supported Johnson Controls Security IP s CK721-A network controller S321-IP network controller CKM-EPxxxx network controllers Note: Johnson Controls legacy network and serial controllers are not supported in P2000 Version For more information on discontinued hardware, refer to the Discontinuation of Legacy Access Control Hardware and Accessories Notice (LIT ). Supported Third-Party IP Readers/s The P2000 also supports the monitoring and control through the Metasys system web interface of controllers, portals, inputs, and outputs associated with the third-party controllers/readers integrated with the P2000 system (see Figure 7 on page 6). Note: For information on specific controller/reader models supported, refer to the Third-Party IP Reader/ Integration Catalog Page (LIT ). Note: The P2000 and Metasys Integration supports limited monitoring and control of ASSA ABLOY locks. See Table 2 on page 6 and Table 3 on page 7 for details. P2000 and Metasys System Integration 5

6 Web Browser (NAE) ADS/ADX Tower P2000 Server IP Network Wide Area Network Stanley OMNILOCK Wireless Gateway HID Edge Reader (Wired) ASSA ABLOY Reader (Wired) ASSA ABLOY Reader (Wireless) OMNILOCK Reader (Wireless) Figure 7: Possible Integration Configuration (Integrated Third-Party Security Products) Supported Commands Metasys operators can send P2000 commands from the Metasys web interface. See Table 2. Table 2: Supported Commands Item Supported Commands Portals (Doors) 1 Unlock All Doors Lock All Doors Unlock selected door for n seconds or minutes according to the door s Access Time setting Unlock selected door for n minutes 2 (not associated with Access Time) Lock selected door until a unlock command is issued Outputs Reset Set 2. Not supported on wired ASSA ABLOY door locks. Figure 8: Send P2000 Door Commands from the Metasys Interface 1. The P2000 and Metasys Integration does not support door commands on wireless ASSA ABLOY door locks. 6 P2000 and Metasys System Integration

7 Figure 10: View Current State of Devices Figure 9: Send P2000 Output Point Commands from the Metasys Interface Status Monitoring Metasys operators can monitor the status of various devices. See Table 3. Table 3: Supported Status Values Item Supported Status Values s Normal Trouble Unreliable Offline Portals (Doors) Online Offline Unlocked 1 Locked 1 Lockout Disabled Overridden 1,2 Unknown Inputs Set Reset Open Short Secure Suppressed Unknown Outputs Set Reset Fault 1. Not supported on wireless ASSA ABLOY door locks. 2. Not supported on wired ASSA ABLOY door locks. Metasys Alarm Monitoring The P2000 system can receive Simple Network Management Protocol (SNMP) Traps from the Metasys system (Release 6.5 and later). Through the use of SNMP Traps, the P2000 system can receive Metasys alarms and associate them with P2000 alarm options, such as instruction texts and escalation rules. Alarms generated in the Metasys system can be processed like regular P2000 alarms and can be used with all P2000 alarm-related applications and features. However, alarm actions are not synchronized between the P2000 and the Metasys system. For example, when you acknowledge an alarm in the P2000 system, the alarm is not automatically acknowledged in the Metasys system. The integration with the Metasys system enables P2000 operators to: Browse and import selected Metasys objects. Receive Metasys alarm messages associated with the selected Metasys objects. Define P2000 alarm options for the imported Metasys objects, translating Metasys alarms into P2000 alarms, where they become subject to the standard P2000 rules and are processed like any other P2000 alarm. Limitations The P2000 system does not monitor the status of the integration device itself (ADX or ADS). Therefore, alarms and messages associated with the integration device being up or down are not supported. The Metasys integration generates alarm messages only. It does not generate transaction history messages. P2000 and Metasys System Integration 7

8 Alarm Management Metasys operators can use the Metasys system web interface to manage P2000 alarms and take appropriate action. Supported alarm management features include: Viewing P2000 alarms Acknowledging P2000 alarms Discarding P2000 alarms Viewing a graphic reference associated with a P2000 alarm Figure 13: Bind Symbols to P2000 Objects Figure 11: View P2000 Alarms from the Metasys Interface Site Director Registration P2000 and Metasys systems integration requires the registration of the P2000 server with a Metasys Site Director. A Metasys Site Director can be one of the following: Application and Data Server (ADS) Extended Application and Data Server (ADX) Note: Network Automation Engine (NAE) s cannot be used as a Metasys Site Director with the P2000 and Metasys systems integration. P2000 enables you to create multiple registration definitions, so you can register the P2000 server with multiple Site Directors (see Figure 14). Site Directors Registered in P2000 ADS/ADX Tower ADS/ADX Tower Figure 12: Select P2000 Alarms to Discard Viewing P2000 Status Changes with a Metasys Graphic Metasys graphics can provide a visual representation of certain components of a P2000 system and enable Metasys operators to quickly check their status and recognize unusual P2000 system conditions. For example, operators can use a Metasys graphic to quickly view the status of a portal based on the color displayed by a dynamic symbol created in the Metasys system s User Graphics Tool (UGT). IP Network P2000 Server Metasys Client Wide Area Network Figure 14: Registering the P2000 Server with Multiple Site Directors In addition, operators may register certain partitions with a particular Site Director, so that only those P2000 objects associated with the selected partitions are visible from the Metasys system (see Figure 15). 8 P2000 and Metasys System Integration

9 Partitions enable the P2000 database to be divided into smaller sections, or partitions, that can be individually managed. These partitions define what data is available to an individual user or to a group of users. ADS/ADX 1 ADS/ADX 2 Partition A Partition B Partition C P2000 Server Figure 15: Using P2000 Partitions with Multiple Site Directors In the example in Figure 15: The P2000 objects associated with Partition A are only visible from ADS/ADX 1. The P2000 objects associated with Partition B are only visible from ADS/ADX 2. The P2000 objects associated with Partition C are only visible from ADS/ADX 2. Supported Metasys Software Versions P2000 Version 3.14 supports Metasys system software Release 4.1 and later. Note: The use of SNMP traps requires Metasys Release 6.5 and later. P2000 Software Requirements The P2000 and Metasys systems integration requires the following software be installed on the P2000 system: Operating system and database server as required for the P2000 system P2000 Prerequisites Version 3.14 Microsoft Internet Information Services (IIS) as required for the P2000 system P2000 Software Version 3.14, all editions Note: For all P2000 software installation requirements and supported platforms, refer to the P2000 Software Installation Manual (Part No ). Ordering Information The P2000 and Metasys systems integration cannot be ordered separately. It is included in the following P2000 software packages: Table 4: Ordering Information Product Code Description Number P2K-SW-EXP314 Entry-level P2000 system that supports a single user connection by using thin or thick clients, 10,000 cardholders, and 32 readers. Supports a single Metasys system connection. P2K-SW-PRO314 P2K-SW-COR314 Mid-range P2000 system that supports 5 concurrent user connections by using thin or thick clients, 25,000 cardholders, and up to 128 readers. Supports a single Metasys system connection. High-level P2000 system that includes 5 concurrent user connections (upgradable to 40) by using thin or thick clients, 25,000 cardholders (upgradable to 10 million), and up to 2,048 readers. Supports multiple Metasys systems. P2000 and Metasys System Integration 9

10 Related Documentation Table 5: Related Documentation Document Title Document Number P2000 Metasys System Integration Manual Part No P2000 Software User Manual Part No Building Efficiency 507 E. Michigan Street, Milwaukee, WI Metasys and Johnson Controls are registered trademarks of Johnson Controls, Inc. All other marks herein are the marks of their respective owners Johnson Controls, Inc. 10 P2000 and Metasys System Integration Published in U.S.A.