1. Introduction Eaton Remote Monitoring Manual RevB.doc Eaton Remote Monitoring Manual This document describes the architecture and methodology for the Eaton Remote Monitoring (ERM) systems used throughout commercial and industrial facilities. The monitoring system is designed to intercept alarms that are initiated by Eaton devices. Some of the benefits of using the ERM system include: Data Storage - Long-term data storage and archiving for all enlisted Insulgard monitors in Oracle. Includes initial migration of historical data. Scheduled Polling - Fully automatic polling on a predetermined schedule, typically once-a-day. Exception Polling - Initiated by IRC or automatically by CRC upon receiving alarm notification. Heartbeat monitoring - keeping track of successful scheduled polls and reporting on exception. Automated Reports - Generated monthly, the report includes overall heath status of all monitored devices in a user friendly format. Cellular based solution does not require any LAN connection. Alternately, the software can be located on a stand-alone PC at the customer site and is linked to the customer system. There is no operator intervention as the process is constant and automatic and so fewer interactions are required to operate and monitor the performance of a condition monitoring system (CMS). Decrease service costs and disruption to the customer: Reduce inbound customer support and data gathering calls by service staff. Reduce reactive, unscheduled service visits. Page 1 of 10
2. ERM Operation The ERM system includes an Enterprise Server located behind the Eaton firewall and a Cellular Modem (Figure 1) or Industrial PC (IPC) (Figure 2) located at the customer site. See Figure 1 for the overall layout architecture. Upon change of state, the ERM will initiate a notification over the existing LAN. When the pending alarm is detected, an immediate notification is send via text message or email to Eaton personnel. All device initiated LAN traffic is isolated from the customer network and all Internet traffic is secured via SSL encryption on outbound port 443 (HTTPS). Remote Monitoring Layout, Cellular Based CUST Bank of Insulgards at customer site Cell Modem CAT 6e STP Customer contact Ethernet Device Server RS-485 2-Wire STP IG Software CRC Alarm notification EESS Customer database (triage sequence) 4 3 2 1 NT Service DB (Oracle) LAN EESS contact#1 EESS contact#2 EESS champion Initial text message First escalation Follow-up Figure 1 Page 2 of 10
Remote Monitoring Layout, IPC Based CUST Bank of Insulgards at customer site IPC Customer contact Ethernet Device Server Internet Alarm notification Enterprise Server EESS Customer database (triage sequence) 4 3 2 1 NT Service DB (Oracle) LAN EESS contact#1 EESS contact#2 EESS champion Initial text message First escalation Follow-up Figure 2 Page 3 of 10
2.1 Hardware Cellular Based A typical cellular based setup is shown in Figure 3. No software or security setup is required when using this method. The cellular antenna must be located in an area with good cell coverage and the modem must be located within 15 feet of the antenna. Figure 4 shows an alternate wiring configuration using direct Ethernet connections between the modem and the Insulgards. Figure 3 Figure 4 Page 4 of 10
2.1 Hardware IPC Based A typical remote setup is shown in Figure 5. The IPC is shipped with 2 Network Interface Cards (NIC) to isolate equipment traffic from the customer LAN. The customer LAN NIC is usually configured to use DHCP for the IP address assignment. The IPC may be connected directly to the devices via RS-485 or Ethernet dependent upon the distances between the IPC and the Insulgard relays (Figures 6 & 7). When using Ethernet, a COM port redirector will be installed on the IPC to redirect serial traffic to the adapter and the system will be assigned two non-routable static IP addresses, typically 192.168.1.10 for the NIC and 192.168.1.11 for the Gridnet adapter. Figure 5 IPC with Dual NIC cards Page 5 of 10
RS485 twisted pair network A B Red Black A B Red InsulGard Address #1 InsulGard Address #2 Black 115 VAC L G N IPC Power Supply + - 24 VDC + - 24V DC Black to Pin 1 Red to Pin 2 9 pin D to TB Ethernet CAT5 patch cables Embedded COM 1 Ethernet Card Industrial PC LAN Hub/Switch (Supplied by others) To customer's LAN Figure 6 IPC with direct serial connection Figure 7 IPC with direct Ethernet Page 6 of 10
2.2 Software & Security IPC Based Eaton Remote Monitoring Manual RevB.doc The IPC is shipped with the latest versions of: MS Windows XPe MS Windows Remote Desktop Protocol (RDP) Eaton Insulgard Software COM Port redirector software Filezilla FTP client _Watchdog service RealVNC Remote Control Software service Protect Mode Save - The Protect Mode Save feature prevents changes made to the IPC from being written directly to the C:\ drive. If any changes are made in the field to the IPC (IP addresses, database changes, etc.) then you must commit the changes by pressing the Commit button located in the epro manager program, which is located in the epro Tools folder. Failure to do this will result in the loss of all changes since the last commit. An XMPP based Remote Agent Processor (RAP) from Palantiri Systems Inc. is used to connect the device through ports 80 and 443 to the Eaton Enterprise Server. Inbound traffic is blocked by utilizing the Windows Firewall (Figure 8) to prevent any unauthorized access that does not originate from the local subnet. There is no need to open any ports on the customer firewall. Figure 8 Page 7 of 10
2.3 Connecting to the IPC There are multiple methods available for customers or maintenance personnel to connect to the IPC. The default Administrator password is ERM@tRucr34e 1. During the startup phase, connections to the IPC can be accomplished by connecting a USB keyboard, VGA monitor and USB mouse to the unit. See Figure 9 2. To use RDP locally, connect an Ethernet cable to the PCMCIA NIC. The NIC is set to 192.168.1.10 and is autosensing so you will not need a cross-over cable but you will need to modify the IP address of the connecting computer to 192.168.1.12. (See Appendix A). If you wish to connect from the customer LAN using RDP, the IP address or epro computer name of the embedded NIC in the IPC will need to be determined prior to connecting. The default computer name will be listed on the packing list for the epro unit. 3. If the customer wishes to install the IG software on another computer, then the RS-485 adapter will need to be connected to the customer LAN (Figure 5), a static IP address must be assigned to the adapter, and the COM port redirector software must be installed on the customer computer along with the Insulgard software. For support purposes, it is best to have this done while the Eaton startup person is at the site. Figure 9 Page 8 of 10
Appendix A - Changing computer IP address from DHCP to Static From Control Panel, select Network Connections then right click on the Local Area Connections and select properties. Scroll down until you see Internet Protocol (TCP/IP). Select the text then press properties. Select Use the following IP address and enter the desired IP address then select OK. You may need to reboot in order for the changes to be applied. Don t forget to change back to DHCP when you are finished with the job. Page 9 of 10
Appendix B - Using FileZilla to transfer files to the remote server Filezilla is a FTP client that is used if you need to transfer the latest IG database to Eaton. The operation has been simplified by storing the FTP site and password information within the Filezilla configuration file. To connect, click on the Filezilla icon on the desktop. From the top menus, select server, reconnect. Once the program connects, click and drag the desired file from the left panel to the right panel. Insure that the file is being placed in the /Insulgard FTP Upload folder. When complete, check the Successful Transfers tab at the bottom at the program screen. Page 10 of 10