Specifications
Table Of Contents
- 1.0 System Overview
- 2.0 Product Description
- 2.1 Application Software
- 2.2 Custom Software Development
- 2.2.1 SITECONFIG-SVC - SiteScan Configuration Service Agreement
- Additional Benefits
- HIGRAPHIC - Create a Graphic
- HIGRAPHICM - Modify a Graphic
- HIGRAPHICUP - Upgrade SS2000W Graphic to SSWeb Java-Based Graphic (1)
- HIGRAPHICUP-5 - Upgrade SS2000W Graphics to SSWeb Java-Based Graphics (2-5)
- TEXTMOD - Customized Modifications
- MODCONFIG-4 - Modbus Configuration
- MODCONFIG-12 - Modbus Configuration
- BACCONFIG-4 - BACnet Configuration
- BACCONFIG-12 - BACnet Configuration
- 2.2.1 SITECONFIG-SVC - SiteScan Configuration Service Agreement
- 2.3 Gateway Modules
- 2.4 SiteLink Modules
- 2.5 Site I/O Modules
- 2.6 Stand-Alone Monitoring Modules
- 2.7 Module Accessories
- 2.8 ARCnet Communication Enhancement Devices
- 2.8.1 ARC156-KIT - ARCnet Kit
- 2.8.2 Other ARCnet Parts
- ARCDIAG485 - ARCnet156 Diagnostics Board
- ARCDIAG485WO - ARCnet156 Diagnostics Board Without Enclosure
- ARCPROT485 - ARCnet156 Surge Protection Board
- ARCPROT485WO - ARCnet156 Surge Protection Board Without Enclosure
- ARCREP485 - ARCnet156 Repeater Board (Signal Booster)
- ARCREP485WO - ARCnet156 Repeater Board Without Enclosure
- 2.9 Third-Party Interfaces
- 3.0 Application and Configuration
- 4.0 Upgrading SiteScan 2000 Systems to SiteScan Web
- 5.0 Third-Party and Building Management Interfaces
- 5.1 SiteScan Web and BACnet/IP to BMS
- 5.2 BACnet/IP to BMS Without a SiteScan Web Front-End
- 5.3 BMS Front-End Interfacing to Liebert Equipment by EIA-485 Modbus
- 5.4 SiteTPI-E with OpenComms NIC (or OpenComms 485)
- 5.5 Basic SiteTPI-E with Third-Party Equipment
- 5.6 SiteTPI-E and Third-Party Equipment with Different Modbus Protocol
- 6.0 ARCnet156
- 7.0 Wiring Guidelines
- Appendix A - Terminology

Application and Configuration
16
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:
• Data centers are in two separate buildings.
• Customer wants to have both sites managed by redundant servers.
• If one server goes down, the customer must have access to both sites.
• Each location manages both sites.
3.5.2 Description
Install two copies of the SiteScan Web server software, one in each location. Only one set of custom-
ized data files is created and is then loaded at both sites. Set up the servers to manage each site.
Both SiteGate-E modules will send alarm information to both servers. The customer will be able to
navigate and monitor both locations’ event alarms. Since the gateway modules can send trend infor-
mation to only one server, the system has been configured for each gateway to send trend data to its
local server.
3.5.3 Bill of Materials
Figure 5 Redundant SiteScan Web servers
Table 6 Bill of materials: Redundant SiteScan Web servers
Qty. Mktg. P/N Description
2 SSWEB SiteScan Web Software
2 SITEGATE-E 32-bit Ethernet-ready gateway module
2 SITELINK-12 SiteScan interface module to 12 Liebert units
2 ARC156-KIT PROT485, DIAG485 and terminating resistors with enclosure
Note: The bill of materials does not include LGS startup part numbers. Most LGS startup part numbers
are added automatically when ordering.
10.1.1.1
10.1.1.2 11.1.1.3
11.1.1.4
City Location A
Network - Ethernet - Fiber
City Location B
Network - Ethernet - Fiber
Legend
Alarm events
Trend data
Notifications
(E-mail, page, etc.)