If you are researching about remote monitoring and control, chances are that you came across the words "PID controller" and "RTU" a couple of times.
Especially if you need to deploy a brand new monitoring system for your network, and don't know yet which gear would fit better in your scenario, it's very important to know what each equipment type is and exactly what they can do so you can choose wisely.
Even though at DPS Telecom we specialize in offering custom monitoring devices, such as RTUs and master stations, we see ourselves as your partner in securing your network and we put your needs first. We don't want to leave you with a monitoring problem that's unsolved, even if it means that RTUs are not the best devices for you.
So, let's explore the main pros and cons with PID controllers and RTUs, as well as their main differences and the best practices to keep in mind when purchasing these devices.
A Proportional Integral Derivative - or simply PID - controller is a device used in industrial control applications to regulate Process Variables (PV). The PV is a parameter that needs to be controlled, such as temperature, flow, pressure, speed, etc.
PID controllers use a control loop feedback to control process variables and are the most accurate and stable controller. They're an efficient way of driving a system towards a target position or level, since they use an accurate and responsive correction to a control function.
For better understanding, imagine that you want the temperature in your office to be 77°F. That's your Setpoint (SP). The PID controller will look at your SP and compare it with the actual value of the (PV).
Back in your office, your HVAC system has a PID controller that looks at the value of the temperature sensor in the room and sees how close it is to 77°F. If the SP and PV are the same, then the controller doesn't have to do anything, and it'll set its output to zero.
But, if the SP and PV are different, then there is an error and corrective action is needed. In this case, it means that your HVAC will cool or heat your office, depending on the PV value (cooling if it's higher than the SP, or heating if it's lower than the SP).
Your PID controller will keep continue to heat or cool down your office until there's no error - your temperature is 77°F.
In telecom and IT industries, an RTU - Remote Terminal/Telemetry Unit - is a remote device that monitors and reports events occurring at a remote site. It allows you or the network operator to manage the network more effectively, keeping service flowing to your customers and protecting your revenue stream.
Some RTUs are also capable of remotely controlling remote site gear using control relay contacts or protocol-based commands.
Without this ability, an RTU can only report remote events to you. While this is valuable, you still must physically travel to the monitored location if a change must be made. So, an RTU that includes remote control capability reduces this potentially multi-hour travel to the site for a single mouse click (or even a fully automated response).
In a nutshell, an RTU is a device that gives you visibility over remote sites that are vital to your business. They're used in all sorts of business, from telecom to utilities to public safety and more.
PID controllers and RTUs are both electronic devices that can remotely control industrial processes, such as control of machinery on factory assembly lines. Even though they seem to perform the same job, there are important differences between them that you should know about.
Although PID controllers require inputs and outputs to receive information from the process and send signals back to control it, it contains specialist algorithms designed to control a process with one or multiple control loops - which RTUs don't have.
Adding new functionality on an RTU can be as simple as updating the firmware on an existing system when a new firmware version is released by the manufacturer.
However, in almost all cases for PID controllers, if you want that new released functionality, you'll have to do a complete hardware and firmware replacement. This is because normally, PID controllers' hardware and firmware are designed and released to fit together.
PID controllers' programmable aspect will offer you greater flexibility and freedom. However, unlike RTUs, this means that if you don't have a coder in your staff, you'll have to hire someone to perform this task. This also means that tech support is hard to obtain because simply each device will be different, and your manufacturer don't know your coding or what you are trying to achieve with it.
RTUs are best suited for wide geographic telemetry, while PID controllers normally can only handle local area control.
On the other hand, although PID controllers provide high-level algorithmic control for automation, they aren't scalable like RTUs, nor do they provide many sensors for information reporting.
The main function of an RTU is to transfer data remotely - which have more powerful communication capabilities than a controller - and not the control (even though most of the ones featuring control relays can operate as a controller).
So, which device is better for you? It all comes down to "it depends." You'll need to weight in the characteristics of each device and compare them with what you're trying to accomplish.
If you need a stand-alone controller for your application, a PID controller is most likely your best choice. Just be aware that some level of programming skills might be required.
If you need a device to control multiple processes, an RTU can provide advanced control functions as it is basically a direct interface between your remote sensors and your master station.
Whether you're better suited with a PID controller or with an RTU, it's important to know what to look for when investing your budget dollars.
Let's take a look at the best practices so you can make sure you're not buying just any device.
The best practice when choosing an efficient PID controller for your system is to take into consideration and analyze your whole network. Keep in mind the following points in order to purchase a controller that will integrate smoothly into your present system:
Type of input sensor and temperature range
Type of control output required (relay, voltage or current)
Control algorithm needed (on/off, proportional, PID)
Number and type of outputs (heat, cool, alarm, limit)
Programmable or non-programmable
When choosing the best in class control PID controller for your system, there are a couple of features that you should look for in your device:
With auto-tuning, the PID controller automatically goes through your sensors and makes changes to the parameters based on the sensor's feedback. This feature is especially helpful during the initial setup of your device.
After the initial setup of a PID controller, network operators will need to make some fine adjustments to their system parameters, this often leads to some frustration because a small change to one parameter can require adjustments to other parameters that were not needed before.
That's where the "stiffness variable" feature comes in. It'll automatically make adjustments to other parameters based on changes to one individual parameters. So, if an operator make tune adjustments that would cause the system to become unstable, this feature will bring the system back into stability and avoid future errors.
If you have long and complicated processes, auto-tuning alone is not always an efficient solution, because it'd only provide a starting point of initial parameters. The best practice is to have your system parameters changing accordingly with the changing conditions of the process.
The adaptive tuning feature is the solution to these demanding tuning requirements. As the conditions change throughout your process, having an automated system equipped with this feature will make adjustments to various parameters if the performance crosses a particular threshold to keep the system under control and achieve the best efficiency.
Selecting an RTU for your remote sites means finding the right balance of capacity, interface, and features.
First of all, you'll need to perform a complete survey of your current network and remote sites. This survey will document your existing alarm monitoring situation, this way you'll select an RTU that not only meets your current requirements but is also compatible with your existing network transport.
Here are some questions that will help you start your network monitoring inventory:
How many remote sites need to be monitored?
What is the protocol and transport of the RTUs you're currently using?
How many alarm points do you need to monitor at each site?
How much rack space do you currently have available?
What dedicated facilities do you already have in place to transport RTU data?
How many ASCII devices (such as switches and routers) will you monitor at your remote sites?
What type of power do you have at the master and remote sites?
You should also consider your RTUs long-term effect on your network monitoring strategy. An efficient device will both immediately improve your network visibility and support your overall upgrade plan to support your future monitoring goals.
The following questions will help you form your future network monitoring plans:
How many alarm points will your network alarm system monitor in the next 5-10 years?
What alarm monitoring features will you need (discrete alarms, analog alarms, controls, serial ports, local visibility)?
What kind of data transport do you want to use, now and in the future (overhead channels, terminal servers, LAN/WAN, etc.)?
What protocols will your remotes use? Are you planning to shift your monitoring to a standard protocol like SNMP?
How do you want to mount your RTUs (23" rack, 19" rack, wall, tabletop)?
What type of alarm termination will work best for you?
Do you want to receive alarm notifications via email or text messages?
Now that we have taken a look at some of the most important factors involved in deciding which RTU to choose, let's take a look at some essential features that any high-quality RTU should offer.
Email and text message notifications
Detailed alarm notifications
Alarm correction instructions
Nuisance alarm filtering
Custom combination alarms
Root cause analysis
History and trend analysis
Live analog monitoring
SNMP support and ping alarms
Alarm data can be sent over nearly any kind of data transport: Ethernet LAN/WAN, dial-up modem, dedicated circuit, overhead channel, WiFi, etc.
There are two things you should keep in mind about RTU alarm data transport:
As much as possible, work with transports that are already available in your network. Committing yourself to installing new network infrastructure can create added expenses. So, it's best to choose an RTU that is compatible with the transport you already have.
It's a good idea to have a secondary backup path for your alarm data in case your primary path fails. No transport is 100% reliable, and with a backup transport you won't lose alarm visibility of your revenue-generating network under any circumstances.
If you are researching about PID controllers and RTUs, chances are that you're on the path of selecting a SCADA (Supervisory Control and Data Acquisition) system for your company.
SCADA isn't just one technology. There are many different types, but they all share one thing: they give you the mission-critical data and control that you need to have in order to manage your operation.
So, if you've just been put in charge of selecting and/or recommending a new SCADA system for your company, you probably have many questions in mind. Where do I start? What equipment do I need? What features are essential?
Whether you decide to go with a PID controller or on an RTU, learning the basics about SCADA is critical so you can get the most out of your investment.
The SCADA Tutorial White Paper is a quick guide that will introduce you to SCADA and show you how to leverage it in your operations, this way you'll be able to answer the previous questions for yourself.
As experts in custom-made monitoring solutions, we won't tell you "Just buy this system and everything will be fine." We know that every network is different. You'll dive deeper into SCADA besides looking at the tip of the iceberg. Learn more about the different industries and their reasons for implementing SCADA. You'll see real world industries with real needs and real SCADA implementations.
After reading the SCADA Tutorial White Paper, you ultimately will be able to determine if SCADA is right for you.
There is no other network on the planet that is exactly like yours. For that reason, you need to build a monitoring system that's the right fit for you.
"Buying more than you need" and "buying less than you need" are real risks. You also have to think about training, tech support, and upgrade availability.
Send me a quick online message about what you're trying to accomplish. I'll work with you to build a custom PDF application diagram that's a perfect fit for your network.
Your network isn't off-the-shelf.
Your monitoring system shouldn't be, either.
We'll walk you through this with a customized monitoring diagram.
Just tell us what you're trying to accomplish with remote monitoring.Get a Custom Diagram