The Water Research Foundation (WRF) has published a suite of deliverables to help water and wastewater utilities utilize...
Comparing SCADA and DAS to help determine which is best for you
A supervisory control and data acquisition (SCADA) system can be utilized for remote data acquisition, but because it is primarily a real-time control system, the user must make significant compromises to use it for this purpose. These compromises include cost, data integrity, flexibility, convenience and control of the task.
A substantial portion of a utility’s operation is in the distribution or collection system: pipes, pumps, valves, tanks, meters, etc. Utilities have an operational need to know how things are working throughout their system in order to manage it properly. In addition to customer usage billing, operational efficiency and maintenance concerns, utilities are being driven by tough government regulations and customer demand for improved quality, safety and security. These factors exert pressure on utilities to better understand and document the operation of their networks.
Most utilities employ a SCADA system or a distributed control system (DCS) to operate and monitor their process plants. It seems logical and almost obvious that extending the SCADA network into the field is the appropriate method if new investment in remote monitoring is required.
A SCADA system requires a huge up-front investment in centralized computer equipment, software, training and personnel time resources. Once the utility has spent this money, expansion of the system per point is relatively inexpensive, providing additional justification for the initial investment.
Furthermore, the SCADA system manager and operators are reluctant to add alternative systems, particularly if they do not seamlessly integrate with the SCADA system they have operating at the plants. SCADA is a safe investment for management reviewing the options—personnel are trained in its use, the utility has committed substantially to its implementation and it is not something new.
The SCADA argument is compelling, and for many remote sites—particularly sites that need to be remotely controlled or where real-time mission-critical data is required on the big screen in the operations center—it is the best solution. For most other remote sites where only data acquisition is required, a data acquisition system (DAS) offers superior cost savings, reliability and versatility.
Consider first that data acquisition and SCADA systems are architecturally different types of systems. SCADA is a real-time polling system; it requires a continuous channel of communications between the host computer and each remote terminal unit (RTU). In data-acquisition applications, the RTU responds to requests for real-time measurements from the host computer. If it is important to monitor a field parameter—such as flow or pressure—once every five seconds, the host computer sends a request for these parameters every five seconds.
SCADA systems operate in this fashion because when performing their primary function, which is control, decisions are made at the host based on real-time data collected from all sensors. However, when a SCADA system is used for data acquisition only (particularly for remote monitoring applications), this approach is not optimal or even practical because of system complexity, cost and data reliability exposure.
A remote DAS, however, is optimized for remote monitoring. A DAS recording telemetry unit (RTU) may be independently configured to sample each sensor or instrument at the optimum rate for that parameter. For a flowmeter, this might be once every second; for sanitary sewer overflow (SSO) level, perhaps once every 15 seconds. The RTU then performs data reduction on these samples to produce information that has value to the user; this might include the total flow at 15-minute intervals; the amplitude and time stamp of water hammer events; or the severity, time of day and duration of a SSO event.
The remote DAS system may then upload the resultant information to the host on a programmable schedule and/or on exception, as specified by the user. The total amount of data transferred by a DAS compared to a SCADA system is typically smaller by two orders of magnitude. The communications link is active only occasionally and for short periods—for example, once per day for 30 seconds.
Data Integrity refers to the assurance that the data transmitted from the remote site to the host is not corrupted or lost. A SCADA system can provide perfect data integrity only if the host computer is running and the communications channel is functional.
Reality demonstrates that computers crash and remote communication networks fail. For the period of time when this happens, remote site data sourced by SCADA will be lost forever.
A DAS utilizing RTUs that are data recorders maintains its measured data at the remote site, typically for many months, even when data is being transferred frequently to the host. If the communication channel goes down or the host computer crashes, remote data collection continues and is automatically recovered when the computer or network problems are fixed.
The typical SCADA system approach to improving data integrity for remote monitoring is redundancy. The thinking is that by adding redundant communication channels, computers and fault-tolerant computer drives, system reliability is improved. This is true, but instead of buying one expensive data acquisition system, the user ends up purchasing two.
Push not pull
SCADA systems poll remote sensors, typically at the highest rate necessary to facilitate control loop dynamics or capture upset events that occasionally occur in the process. This might be a sample rate of every few seconds. Although necessary for the plant floor environment—where events occur quickly and sensor power and networking access is convenient—real-time information is not often necessary or even appropriate for remotely deployed sensors and instruments.
In most remote monitoring applications, it is desirable to upload information to the host computer at a rate that is useful to the user; this might be every 15 minutes, once per day or on exception. For example, it is only necessary to upload data from a remote rain gauge when it is actually raining or a CSO overflow event when it is overflowing. The pressure history of a remote water main might be useful information to collect daily unless pressure goes out of range, in which case real-time alarms may be desired.
Consider, for example, monitoring the level and flow of wastewater under the streets of a major city. Plumbing power into a sewer to service a SCADA RTU is an expensive ordeal. Deployment of antennas for a real-time radio communication system is also a challenge.
Alternatively, a battery-powered remote DAS RTU utilizing cellular packet communication can be deployed underground, in the sewer with the sensors. In Push mode, the RTU decides when to initiate the data call. This permits shutting down the radio modem between calls, allowing DAS RTUs to be battery powered.
Pushing data also allows the RTU to transmit data optimally for the application—for example, when it is raining or when the sensors are dynamically changing. This generally reduces data traffic at the host by one or two orders of magnitude, reducing computer resources and communication costs.
For a host of reasons, SCADA systems for remote monitoring are quite costly when compared to a DAS approach. A remotely installed SCADA RTU may range in cost from $6,500 to $20,000. Much of this has to do with the fact that SCADA RTUs are designed to be installed on the shop floor, where the climate is predictable, power is available, communication is a simple plug-in and installation is easy. Installing this same RTU in an underground vault is a bit more daunting: The climate is hostile, the vault might occasionally flood, the closest utility power is up a pole hundreds of yards away and there is no Ethernet cable or phone line connection anywhere at the site.
A DAS RTU is designed for this environment. For example, the Telog Ru-33 RTU is supplied with a 6-VDC lantern battery, which can operate the RTU for many months, including making regular though infrequent data calls to the host via the cellular infrastructure. It is supplied in an enclosure that anticipates the worst possible site conditions, such as a sewer containing corrosive gases that floods from time to time.
The typical installed cost of the Telog RTU—including burial cellular antenna—is less than $3,000, and it takes an experienced crew less than an hour per site to install one.
DAS and SCADA
DAS is superior to SCADA for remote monitoring applications and, in some cases, is the only practical option. It is often desirable that remote data be integrated into the user’s SCADA/HMI platform. This provides system operators and management a complete view of their systems.
Moving data from the host computer DAS application to the SCADA/HMI application is a simple IT task, particularly if both systems are employing industry-standard data protocols (such as relational databases). This methodology provides the user the best of all data worlds: The cost, versatility and reliability of a remote DAS system, and all plant and field data on a common platform.