MONITORING SITESCAN WEB SOLUTIONS GUIDE
TABLE OF CONTENTS 1.0 SYSTEM OVERVIEW . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1 1.1 What’s in This Manual. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 1.2 Typical SiteScan Web System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.0 PRODUCT DESCRIPTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
3.0 APPLICATION AND CONFIGURATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12 3.1 Single-Site - SiteScan Web System Not on Customer’s Ethernet . . . . . . . . . . . . . . . . . . . . . 12 3.1.1 3.1.2 3.1.3 3.2 Multiple Data Centers in the Same Building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 3.2.1 3.2.2 3.2.3 3.3 Target Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
.0 THIRD-PARTY AND BUILDING MANAGEMENT INTERFACES . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.1 SiteScan Web and BACnet/IP to BMS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 5.1.1 5.1.2 5.1.3 5.2 BACnet/IP to BMS Without a SiteScan Web Front-End . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 5.2.1 5.2.2 5.2.3 5.3 25 26 26 27 Target Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
FIGURES Figure 1 Figure 2 Figure 3 Figure 4 Figure 5 Figure 6 Figure 7 Figure 8 Figure 9 Figure 10 Figure 11 Figure 12 Figure 13 Figure 14 Figure 15 Figure 16 Figure 17 Figure 18 Figure 19 Figure 20 Figure 21 Figure 22 Figure 23 Single-site - SiteScan Web system not on customer’s Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple data centers in the same building . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Multiple sites using customer’s intranet .
System Overview 1.0 SYSTEM OVERVIEW SiteScan Web uses a network of microprocessor-based control modules to monitor and control Liebert air, power, UPS and other critical equipment. SiteScan Web enables the user to monitor and control equipment in a single building, an entire campus or a network of facilities around the globe.
System Overview 1.2 Typical SiteScan Web System A typical SiteScan Web system may include the components shown in the figure below. Server Software and Client License (see 2.1 - Application Software) • SiteScan Web Server - A dedicated computer running SiteScan Web server software, including a database that stores system configuration, custom graphics and equipment interfaces. For hardware and operating requirements, see Table 1.
Product Description 2.0 PRODUCT DESCRIPTION 2.1 Application Software SiteScan Web is based on server/thin-client architecture, designed around the open standards of Web technology. The SiteScan Web Server communicates using ASHRAE’s BACnet/IP protocol and is accessed using a Web browser over the owner’s intranet or external through the Internet. The intent of the thin-client architecture is to provide operators complete access to the system via a standard Web browser.
Product Description 2.2 Custom Software Development Determine the number of graphics necessary for the customer. By default, SiteScan Web includes a generic, top-level graphic, showing the Liebert SiteScan Web logo and the company name as a starting point for the system. Customized graphics—available in two- and three-dimensional (2D and 3D) versions—may represent buildings, floor plans, one-line schematics or maps to help customers pinpoint monitored equipment. 2.2.
Product Description 2.3 Gateway Modules In SiteScan Web, Liebert gateways route BACnet over IP traffic between Liebert gateways and the Web server. The gateway receives BACnet over ARCnet from the Liebert control modules and converts it to BACnet over IP for communication to the SSWEB server. • At least one gateway is required for SiteScan Web to operate. • Usually one gateway is applied to each facility or location that is being monitored. NOTE The maximum numbers of modules per gateway is 50.
Product Description 2.4 SiteLink Modules A SiteLink module receives IGM protocol from Liebert environmental and power equipment and converts it to BACnet over ARCnet for communication to a Liebert gateway. In this section you will have to determine the type of SiteLink needed to monitor the Liebert equipment. To do this, determine how many Liebert units you have and where are they located.
Product Description 2.5 Site I/O Modules A Site I/O module is used to interface to dry contacts or sensors, the types of connections required to monitor generators, fire systems, doors, temperature, humidity and pressure. Site I/O modules provide monitoring for contact closures and analog sensors: • • • • Dry contacts Thermistors 4-20mA transducers 0-5VDC transducers NOTE Each Site I/O unit requires a separate 24VAC power supply; use XFMR24 for U.S. installations (see 2.7.3 - XFMR24 - 24V Transformer).
Product Description 2.6 Stand-Alone Monitoring Modules The Liebert stand-alone monitoring modules include the RPMP, Universal Monitor and Liqui-tect Monitoring System. The following remote monitoring modules communicate with a SiteLink using the IGM protocol, the RS-422 media access type and a two-screw terminal connection type. 2.6.
Product Description 2.7 Module Accessories 2.7.1 GXEXP - Expander Cable The Site I/O Expander Cable is an 18-inch long or 24-inch long expander cable used between the Site I/O X8/0 modules. Because expander modules plug directly into the side of the adjoining module, the grouping tends to become very long in the horizontal direction. Use only one (1) GXEXP cable to break up this horizontal length. 2.7.
Product Description 2.8 ARCnet Communication Enhancement Devices In SiteScan Web systems, ARCnet, or ARC156, is the standard for module-to-module communications. Formerly, this was termed CMnet in SiteScan 2000/2W systems. The main difference is the control module network now operates at a faster baud rate (156K baud with ARCnet vs. 9600 or 38.4K baud with CMnet). The increase in speed requires a low impedance / low capacitance wiring.
Product Description 2.9 Third-Party Interfaces The SiteTPI-E is designed to communicate with third-party equipment that uses Modbus or BACnet. Use a SiteTPI to interface with third-party equipment such as generators, fire suppression systems or competitive gear. NOTE Each SiteTPI-E unit requires a separate 24VAC power supply; use XFMR24 for U.S. installations (see 2.7.3 - XFMR24 - 24V Transformer). 2.9.
Application and Configuration 3.0 APPLICATION AND CONFIGURATION 3.1 Single-Site - SiteScan Web System Not on Customer’s Ethernet 3.1.1 Target Application In a typical application, a customer wants to monitor just a few Liebert units from a single computer, but does not want to put the SiteScan Web System on the company’s Ethernet backbone. The main features are: • • • • 3.1.
Application and Configuration 3.2 Multiple Data Centers in the Same Building 3.2.1 Target Application In a typical application, a customer wants to monitor two data centers in the same building but on two different floors. The building does not easily accommodate wiring between floors. The main features are: • Multiple data centers in the same building • Liebert units in all data centers • Intranet that connects the customer’s total enterprise 3.2.
Application and Configuration 3.3 Multiple Sites Using Customer’s Intranet 3.3.1 Target Application In a typical application, a customer has multiple data centers in different parts of the world and wants to monitor three facilities from one centralized system. The main features are: • Users should be able to access their own facility to manage their own equipment. Each data center should have a floor plan with the equipment layout.
Application and Configuration 3.4 Hierarchical Servers - SiteScan Web with WebCTRL 3.4.1 Target Application In a typical application, a customer has a WebCTRL BMS system that controls the overall functions of the facility, but now wants to monitor the data center and send notifications of event alarms to the BMS. The main features are: • Customer has a WebCTRL BMS system. • Data center needs to be monitored specifically. • BMS should receive specific alarms from the monitoring system.
Application and Configuration 3.5 Redundant SiteScan Web Servers 3.5.1 Target Application In a typical application, a customer wants to monitor two facilities using two servers that manage both locations, providing server redundancy. If a server goes off-line, the other still collects alarms from both locations. The main features are: • • • • 3.5.2 Data centers are in two separate buildings. Customer wants to have both sites managed by redundant servers.
Application and Configuration 3.6 SiteScan Web and Rack Monitoring 3.6.1 Target Application In a typical application, a customer has a data center that contains multiple racks and wants to manage “hot spots” within the racks. Event alarms should be reported on High Temperature. The main features are: • Data center has Liebert Foundation racks. • Heat load within the racks needs to be monitored and managed. 3.6.
Upgrading SiteScan 2000 Systems to SiteScan Web 4.0 UPGRADING SITESCAN 2000 SYSTEMS TO SITESCAN WEB A SiteScan Web upgrade allows an existing SS2000 or SS2W system to communicate with SiteScan Web. Since SiteScan Web requires an Ethernet-ready gateway module, the SiteGate-232 or DCLan must be replaced during the upgrade. Since the SiteScan Web upgrade requires a platform change from a Windows 16-bit application to a 32-bit Java application, some features may not be available. See Table 8 for details.
Upgrading SiteScan 2000 Systems to SiteScan Web 4.1 Upgrade Overview SiteScan Web Upgrade comes with all the same basic functionality as SiteScan Web. SS2000 or 2W serial numbers must be retired for a customer to qualify for upgrade pricing.
Upgrading SiteScan 2000 Systems to SiteScan Web 4.2 Upgrading SS2W A SiteScan Web upgrade of an existing SiteScan 2W system requires replacing each DCLan or SiteGate-232 module with a SiteGate-E module. 4.2.1 Target Application A typical application for this upgrade might be: • Customer wants to upgrade a SiteScan 2W system. • Existing system uses a SiteGate-232 module. 4.2.2 Description To upgrade a SS2W system that currently uses a SiteGate-232, replace the SiteGate-232 with a SiteGate-E.
Upgrading SiteScan 2000 Systems to SiteScan Web 4.3 Upgrading SS2000W While Maintaining Existing Wiring A SiteScan Web upgrade of an existing SiteScan 2000W system requires replacing each DCLan or SiteGate-232 module with a SiteGate-E module. All graphics must be upgraded. 4.3.1 Target Application A typical application for this upgrade might be: • • • • 4.3.2 Customer wants to upgrade a SiteScan 2000W system. Existing system uses a DCLan. System has five graphics.
Upgrading SiteScan 2000 Systems to SiteScan Web 4.4 Upgrading SS2000W to Full SiteScan Web A full SiteScan Web upgrade of an existing SiteScan 2000W system permits the customer to take full advantage of the SiteScan Web system. This upgrade requires replacing each DCLan or SiteGate-232 module with a SiteGate-E module. All graphics must be upgraded. 4.4.1 Target Application A typical application for this upgrade might be: • • • • 4.4.2 Customer wants to upgrade a SiteScan 2000W system.
Third-Party and Building Management Interfaces 5.0 THIRD-PARTY AND BUILDING MANAGEMENT INTERFACES SiteScan Web monitoring products can provide multiple paths for integrating to and with third-party equipment and software. Through BACnet over IP, SiteScan Web software allows you to interface with more than one building management system (BMS) at a time. The SiteLink hardware is designed to communicate concurrently with SiteScan Web and a BMS using Modbus over EIA-232 or EIA-485. 5.
Third-Party and Building Management Interfaces 5.2 BACnet/IP to BMS Without a SiteScan Web Front-End 5.2.1 Target Application A typical application might be: • Customer has a BMS front-end and does not want a SiteScan Web front-end. • Two new computer rooms need to be monitored by BMS. • Each computer room will have the following: • 3 Liebert environmental units • 1 STS2/PDU • 2 NPower UPSs • 4 analog sensors • 2 strobe lights for alarm conditions • One local user is allowed. 5.2.
Third-Party and Building Management Interfaces 5.3 BMS Front-End Interfacing to Liebert Equipment by EIA-485 Modbus Modbus is an industry standard means of communicating between systems from different vendors. A SiteScan Web system using Modbus allows a Third Party to request information from a SiteLink, With SiteScan Web, single or multiple SiteLinks can communicate to other systems using Modbus on either Port A or Port B. Both ports send out Modbus information.
Third-Party and Building Management Interfaces 5.3.2 Port A—RS-232 to RS-485 Modbus If the third-party device communicates using RS-232 point-to-point, but the configuration requires multiple SiteLinks, use a REPOPT to convert RS-232 to RS-485. The RS-232 can be either DB-9 or two-wire screw terminal connection types. Table 15 Bill of materials: Port A—RS-232 to RS-485 Modbus Qty. Mktg.
Third-Party and Building Management Interfaces 5.3.4 Combining SSWEB and Modbus It is possible to have a Modbus system communicating to a SiteScan Web system with a server, gateway and SiteLink. Table 17 Bill of materials: Combining SSWEB and Modbus Qty. Mktg.
Third-Party and Building Management Interfaces 5.4 SiteTPI-E with OpenComms NIC (or OpenComms 485) Customer has installed OpenComms NIC cards in Liebert environmental and power precision equipment and wants to monitor the equipment with SiteScan Web. The following configuration also applies to Liebert units with OpenComms 485 cards. 5.4.
Third-Party and Building Management Interfaces 5.5 Basic SiteTPI-E with Third-Party Equipment Customer wants to monitor third-party equipment with SiteScan Web. 5.5.1 Target Application A typical application might be: • Basic SiteTPI with third-party equipment • Existing system is SiteScan Web 5.5.
Third-Party and Building Management Interfaces 5.6 SiteTPI-E and Third-Party Equipment with Different Modbus Protocol Customer wants to monitor third-party equipment with SiteScan Web. The third-party equipment supports Modbus, but each type supports a different Modbus interface. The Modbus protocol on the UPS supports 2-wire interface; the air equipment supports 4-wire Modbus interface. 5.6.1 Target Application A typical application might be: • • • • 5.6.
ARCnet156 6.0 ARCNET156 6.1 ARCnet156 CMnet Components The SSWEB-Liebert gateways and control modules communicate using ARCnet156, a token-passing protocol running at 156 Kbps. ARCnet156 requires network boards to properly terminate, bias, protect and repeat data transmitted over the twisted pair EIA-485 segment. An ARC156-Kit should be used for every gateway module. The kit filters out some signal noise and provides diagnostic information about the ARCnet156 network.
ARCnet156 6.3 Terminations At 156 Kbps, a signal reaching the end of an unterminated cable can echo, or reflect back, creating a distortion in the signal and degrading the quality of the communications. To prevent this, every segment on the ARC 156 network must have a 120 ohm terminator placed at each end of the segment. To insert the 120 ohm terminator, make sure the module’s power is turned off and attach the terminator to the CMnet positive and negative terminals.
ARCnet156 6.5 Cable Shields Connect the shields as shown in Figure 23. The shields should be connected at each module’s shield connection terminal. Do not ground the shield to earth ground or to the module’s power ground. The PROT485 and the individual modules allow the shield to float a limited amount so that there are no ground loops.
ARCnet156 6.7 Upgrading to ARC156 Before upgrading a legacy CMnet to ARC156, you must: • Ensure adequate wiring. See 6.4 - Wiring Recommendations for details. • Verify the network configuration is acceptable. See 6.2 - Segment Requirements. • Use the appropriate network accessories—for example, 120 Ohm terminators and REP485 repeaters. • Make sure all modules are capable of using Exec 6.0 or later. Refer to the Technical Instructions for each module or to the Technical Handbook to determine this.
Wiring Guidelines 7.0 WIRING GUIDELINES Table 22 Standard SiteScan Web wiring Application ARC156 CMnet Max. Cable Length Cable Recommendation 2000 ft. (610m) Magnum A3-ARC-156 Magnum A3-ARC-156-2 RS-422 - IGMnet UTP Non Plenum Belden 8442 (22 AWG) STP Non Plenum 1000 ft. (305m) UTP Plenum STP Plenum Table 23 Belden 9461 (22 AWG) Belden 88442 (22 AWG) Belden 88761 (22 AWG) Third-party wiring Application RS-232 - Modbus Max. Cable Length Cable Recommendation 50 ft.
Wiring Guidelines NOTES 36
Terminology APPENDIX A - TERMINOLOGY ARCnet The protocol used for communications between the Liebert gateway and the Liebert control modules. This is a token-passing protocol where each module transmits information to the gateway in turn based on its physical address. BACnet Data communication protocol for Building Automation and Control Networks (BACnet).
Terminology Liebert Gateway Also referred to as a router, the Liebert gateway routes information between the Web server and the Liebert control modules. It uses an Ethernet network and the TCP/IP and BACnet protocols, also referred to as BACnet over IP. Half Router A function of a Liebert gateway.
Terminology Router A device that forwards data packets from one local area network (LAN) or wide area network (WAN) to another. Based on routing tables and routing protocols, routers read the network address in each transmitted frame and send it based on the most expedient route. In SSWEB, the Liebert gateways route BACnet over IP traffic from one segment to another. SNMP Simple Network Management Protocol; a protocol to manage devices. SNMP sends traps that signify alarm conditions within a device.
Terminology NOTES 40
MONITORING SITESCAN WEB SOLUTIONS GUIDE The Company Behind the Products With over a million installations around the globe, Liebert is the world leader in computer protection systems.
