The question of when it’s most appropriate to use an RTU or a PLC has not faded with the continued rise of the PLC and the PAC (programmable automation controller). In fact, a member of the Automation & Control group on Facebook (the Facebook counterpart to Automation World’s LinkedIn group), recently asked this very question.
The most detailed response explained that: an RTU is a “microprocessor-controlled electronic device that interfaces objects in the physical world to a distributed control system or SCADA system by transmitting telemetry data to the system and/or altering the state of connected objects based on control messages received from the system”; and that a PLC is basically “a digital computer used for automation of electromechanical processes. Because the functions of RTUs and PLCs overlap, RTUs tend to be used more for wide geographic telemetry, while PLCs are best suited for local area control.”
Other members of the group claim that the communications abilities of current PLCs “more than equal RTUs and they're considerably more flexible and versatile” — even in applications requiring wide geographic use.
Thus, the debate rages on.
One of the better — and simpler — explanations I have seen over the years comes from Tetragenics (a supplier of SCADA systems and smart remote units). Basically the explanation says: If you need a stand-alone controller with power for your application, a PLC is likely your best choice. But be aware that some level of programming skills will be required. If you need a device to control multiple processes, without direct intervention from a controller or master, an RTU can provide many of the advanced control functions needed, as it is basically a direct interface between the field sensors, actuators and a central control unit.
Like most answers either/or questions, the answer always seems to be “it depends.”
Where do you come down on this issue? Weigh in with your answers below in the comment section.
Leaders relevant to this article: