C O N N E CT I N G T H E WORLD S ASSETS The SCADA Connection: Moving Beyond Auto Dialers Auto dialers have long been used to report alarms in SCADA installations. While they are useful for notifying users of alarm states, most models do not provide insight into the status of equipment. This white paper explores how today s technology allows users to augment their SCADA monitoring and control and enjoy benefits never imagined with auto dialers. W H I T E PA P E R
Overview Auto dialers have a long history of providing notifications in remote SCADA (Supervisory Control and Data Acquisition) installations. Most auto dialers detect possible alarm conditions by using discrete digital and analog ports connected to sensors. Once a problem is detected, users are notified when the device calls one or more pre-defined phone numbers to report the alarm conditions. While in some cases auto dialers are an effective way to remotely monitor pumps, valves, motors and switches, the evolution of SCADA installations has resulted in more complex equipment on site that needs to be monitored and controlled. There is also a greater demand by SCADA users to optimize operations by automating functions that can be done remotely in order to eliminate the costs and time required to send a technician to verify the existence of a problem, diagnose the root cause and plan for remediation. In this white paper we will explore how SCADA installations can evolve from the use of auto dialers to a more comprehensive way of managing remote sites that increases visibility while reducing costs. SCADA Applications The Basics SCADA technology is used in a number of industries including the oil and gas, electricity, and water and waste water industries. It is used to monitor and control equipment of all sizes and complexities. SCADA systems gather information such as pump on/off events, liquid flow, water levels, pressure values, and temperature readings and send them to a central management system. Traditionally, SCADA system operators were looking for confirmation of basic functionality and notification when abnormal events occurred. Examples of events include: Levels above/below predetermined thresholds Pump/generator on/off events or excessive starts Intrusion detection Power loss Temperature readings or pressure values above/below thresholds These types of events are easily reported by simple auto dialers using conventional phone lines when values have crossed high or low set points. However, as SCADA systems have evolved and operators have increased their demand for information, some data cannot be communicated easily using auto dialers over analog phone landlines. Today s SCADA More Data, More Opportunities Wireless communication has enhanced the possibilities in SCADA monitoring. Operations managers are no longer restricted to relying on auto dialers connected to phone lines for communicating SCADA events. They now have more physical reach by being able to monitor, control and automate equipment located at remote sites spread over large geographical areas. It has also been part of the evolution that allowed customers to move away from closed, analog connections to digital and IP (Internet Protocol) based systems. As technology has evolved, SCADA remote monitoring and control equipment like PLCs (Programmable Logic Controllers) and RTUs (Remote Terminal Units) have also become more feature-rich (and complex). The increase in proliferation and functions of PLCs and RTUs means there is a greater depth of information available locally to operations managers. However, the challenge is to exchange information with the equipment in a timely manner and make it available to the SCADA master station and users for viewing, interpretation and driving business key performance indicators. SCADA Sites Designing And Retrofitting Whether you re building a new SCADA site or retrofitting an existing site, there are many points to consider so that you can extract more comprehensive information. Building (or upgrading) a successful SCADA network depends not only on understanding today s remote monitoring and control requirements but also on implementing a system that can scale up to tomorrow s needs. Beyond the master station, the architecture of the SCADA network comprises of three main components. These are: Controllers or data terminal equipment (DTE) at the remote sites Data communication equipment (DCE) Communication (telemetry) network Controllers Or Data Terminal Equipment Today s controllers, whether they are PLCs, RTUs or intelligent communication terminals, come in various sizes and capabilities to meet master station and remote THE SCADA CONNECTION: MOVING BEYOND AUTO DIALERS 2
station control needs. Here are 10 factors to consider when selecting this type of equipment: 1. Local intelligence and processing: is the unit programmable? What is the processing throughput? What is the data logging capacity of the unit? 2. Input/output (I/O) ports: what is the number of I/O ports and what is their accuracy? Do they meet the needs of the application? 3. Communications: what telemetry communication services are supported? Are there provisions for redundant communications for critical applications? Can data be sent and received at the frequency required by the application and the operation manager? 4. Protocols: does the unit support open standard industry protocols like Modbus and DNP3 on serial and TCP/IP ports? 5. Interfaces: what interfaces are required to connect to DCEs? 6. Power: what are the power requirements of the unit? Can the unit be operated on battery alone? What are the options for backup power? 7. Enhanced security: does the equipment support password-protected programming, authentication and IP firewall capabilities? 8. Durability and ruggedness: is the unit rated to handle the temperature, humidity, vibration and electrical conditions found at the remote sites? 9. Modularity: is the unit expandable as demand and needs change? 10. Space and installation: how much space is required by the controller and how will it be installed at the remote site? Data Equipment Terminals In some applications, ORBCOMM satellite devices are a very cost-effective way to add a controller with communication capability to a remote SCADA site. The IDP 600 series terminals feature four general input/ output ports for connecting analog and digital sensors. The terminals also have RS-232 and RS-485 ports for connecting devices that communicate via serial protocols like Modbus. The onboard processor allows customers to program logic into the device to react to events like send a notification when the water level is above the analog high threshold or close the valve when pressure reading is below low threshold. This edge analytics capability reduces the amount of data that is sent wirelessly, thereby decreasing reaction time to events as well as monthly airtime costs. Data Communication Equipment DCEs are responsible for the exchange of data between controllers/dtes and the master station. DCEs include auto dialers as well as radio, cellular and satellite modems and terminals. Here are 10 factors to keep in mind when considering DCEs for SCADA sites: 1. Availability: which communication networks are available at the remote sites? This will drive the selection of the DCE. Options include radio, private leased lines, cellular and satellite. 2. Redundancy: does the DCE have redundant communication options? 3. Data requirements: does the unit support the transmission of analog, digital and/or serial data? 4. Data communication rate: how much data needs to be sent to and from the remote site? Will there be demand to change the data as the site grows? Can data be sent and received as frequently as required? 5. Transmission modes: does the site need half-duplex or full-duplex capability? 6. Response time and latency: how much time does it take to relay information between the controllers and the master station? Does it meet the needs of the application? 7. Interfaces: what interfaces are required to connect to the controllers? 8. Standards and certification: what communication standards need to be complied with in order to operate in that region? 9. Power: how much power is required to operate the DCE? Can the unit revert to backup power in the advent of a failure on the main power line? 10. Durability and ruggedness: is the unit rated to handle the temperature, humidity, vibration and electrical conditions found at the remote sites? THE SCADA CONNECTION: MOVING BEYOND AUTO DIALERS 3
Building (or upgrading) a successful SCADA network depends not only on understanding today s remote monitoring and control requirements but also on implementing a system that can scale up to tomorrow s needs.
ORBCOMM Products as DCEs An integral part of ORBCOMM s IDP technology is the ability to provide cost effective satellite communications for remote sites requiring the ability to send notification of events and alarms as well as regular telemetry data. Customers who opt for these solutions have the ability to send and receive as much data as they want without being constrained to using time slots at specific times of day. They also receive the information in seconds rather than minutes or hours. The IDP 600 series satellite-only devices are rugged and compact. They are designed to be installed outside and are also available with C1D2 (Class 1, Division 2) certification for use in hazardous locations. The IDP 700 series satellite-cellular devices are equipped with more than 17 I/O ports and can send information via satellite, cellular or both, depending on need. Communication Telemetry Networks The communication network is the essential component for connecting remote sites to master stations. When selecting the primary and secondary communication systems, consider the following 10 factors: 1. Coverage: is the network available at the remote sites? 2. Uniformity: looking at the entire SCADA system, is it important to use the same communication networks across all the sites? Choosing different networks depending on local availability will increase the number of DCEs that need to be selected. 3. Infrastructure: is there a need to install infrastructure like towers and repeaters to support the communication network? What is the required infrastructure investment? Can infrastructure installation and maintenance costs be outsourced to a cellular or satellite communication provider? 4. Monthly costs: what are the recurring usage costs? 5. Total cost of ownership: how do initial infrastructure and recurring monthly costs fit into the company s financial policies? 6. Reliability: what is the reliability of the communication network at each remote site? Does it meet the mandated or desired service level agreement? 7. Data communication requirements: how much data needs to be sent to and from the remote site? Will the data demand change as the site grows or evolves? 8. Transmission modes: does the site need half-duplex or full-duplex capability? 9. Responsiveness and latency: how much time does it take to connect to the network and relay information between the controllers and the master station? Does it meet the needs of the application? How frequently can data be polled from remote sites? 10. Emergency management: does the communication network stand up to extreme weather like hurricanes, tornadoes and tsunamis? Benefits of increased visibility at remote sites Increased visibility of the status of equipment at remote SCADA sites and the ability to collect more data than was provided solely by alarms (as offered by auto dialers) has translated into significant cost and operational savings for managers. The benefits include: Reduced field visits, with lower labor and fuel costs. Ability to schedule maintenance on equipment based on need rather than time passed. Decreased mean time to repair with real-time alerts of issues. Plus, being able to poll more data from the sites means being able to diagnose problems before dispatching a technician. Minimized downtime by being alerted of degradation in performance of equipment To achieve these results it is important to spend time considering the architecture of your SCADA site including the DTE, DCE, communication telemetry network and how the solution can meet today s remote monitoring and control requirements but scale to tomorrow s needs. Products and Communication Networks Think satellite is expensive? Think again. ORBCOMM devices are ideal for applications that require cost-effective connectivity in remote areas where other communication services are unavailable or cost-prohibitive to implement. In some cases, customers who have chosen ORBCOMM solutions pay less than they would for cellular solutions. THE SCADA CONNECTION: MOVING BEYOND AUTO DIALERS 5
The SCADA Connection For more information about how ORBCOMM products can address your DTE, DCE and communication telemetry network needs, visit us at www.orbcomm.com. ORBCOMM Inc. (Nasdaq: ORBC) is a leading global provider of Machine-to-Machine (M2M) communication solutions and the only commercial satellite network dedicated to M2M. ORBCOMM s unique combination of global satellite, cellular and dual-mode network connectivity, hardware, web reporting applications and software is the M2M industry s most complete service offering. Our solutions are designed to remotely track, monitor, and control fixed and mobile assets in core vertical markets including transportation & distribution, heavy equipment, industrial fixed assets, oil & gas, maritime and government. R061516A