Professional Documents
Culture Documents
Single-loop Controllers
A single-loop controller (SLC) may be defined as a controlling device that solves control algorithms to
produce a single controlled output. SLCs often are microprocessor based and may be programmable or
have fixed functionality.
Size
Control Functions
Self – Tuning
Time Scheduling and Sequencing
Others (Auto/Manual, Multi-setpoint, Self-diagnostics, Memory)
Networking
Stand-alone programmer controller in a 1/8 DIN case [96 by 48mm(3.8 by 1.9 in.)]
features a dual light-emitting diode (LED) display, and seven dedicated LEDs areused to show
prompt legends during setup and the instrument status when a program is running.
(West Instruments.)
1
Data Communications and Networking Prepared by: CMMFesarit
Family of single-loop process controllers. These programmable controllers incorporate computational and control functions that can be
combined in the same manner as programming a pocket calculator.
(Johnson Yokogawa Corporation.)
Control system for several compressors by using a stand-alone programmable computing station. (Johnson
Yokogawa Corporation.)
2
Data Communications and Networking Prepared by: CMMFesarit
Definition of DCS
1. To distribute its functions into relatively small sets of semiautonomous subsystems, which are
interconnected via a high-speed communications network. These functions include:
data collection
process control
presentation of information
process analysis and supervision
storage and retrieval of archived information
presentation and reporting of information
The distribution of functions has several advantages over more classical process computer
architectures, including:
lower exposure to component or subsystem failure and better isolation to facilitate
maintenance and upgrades
better partitioning of application requirements for different process areas
improved modularity for application development
facilitation of geographical distribution, which reduces installation costs (reduced
wiring) and provides more localized operational supervision while offering global
access to information and control capabilities
3. The systems aspect of a DCS organizes the command structure and information flow among its
constituent parts so as to have it act as a single automation system unifying the various
subsystems, including:
process signal input and conditioning
process actuator signal output
regulatory, combinatorial, and sequence logic and procedural and supervisory control
human readable process displays of current values, alarms, trends, and calculations
human actions including setpoint changes, manual overrides and alarm handling
application subsystems such as process optimization and manufacturing support
information-storage subsystems
communications subsystems
3
Data Communications and Networking Prepared by: CMMFesarit
mid-1970s - Advances in microprocessor and software technology, coupled with the commercial
availability of process control and operations software, made process computers affordable and useful
tools for process control engineers.
4
Data Communications and Networking Prepared by: CMMFesarit
late 1970s to early 1980s - The second generation of distributed controllers greatly extended the use
of software links between functional control elements.
mid-1980s - Computer hardware and software technology had reached the point where DCSs could
address expanded issues concerning real-time information, and the emphasis shifted from automatic
control to constructing tools to facilitate the production process:
batch: product recipe management
production scheduling and dispatching
plantwide information collection, storage, retrieval, and reporting
statistical process control
manufacturing execution systems
process accounting, including material and energy flow reconciliation
process modeling and model reference control
expert systems
late 1980s and early 1990s - A hybrid offering would be created, supporting both traditional and
component-based subsystems with investment continuing to support the traditional design in all
aspects of the offering.
early 1990s - Most suppliers were repositioning their DCS offerings from panelboard replacement to
being the real-time component of a manufacturing enterprise system utilizing distributed computing
architectures.
mid-1990s - The market appetite for increasingly specialized application solutions for a widening
diversity of market niches began growing exponentially.
5
Data Communications and Networking Prepared by: CMMFesarit
INPUT OUTPUT
DCS vs PLC
• 10- 15 years ago, PLC is the KING of “Machine” controls while DCS dominates “Process” control
• High speed control = PLC
• Complex Control = DCS
• DCS performed hundreds of “Analog” measurements and controlled dozens of analog output,
using multi-variable Proportional Integral Derivative (PID) control
• PLC replaced conventional relay/solid-state logic in machine control. It dealt with contact IO
and Start/stop motors by performing “Boolean” logic
• Most DCS offer redundant controllers, network, and IOs. Most give you “built-in” redundancy
and diagnostic features with no need for user-written logic
• DCSs allow centralized configuration from the operator or engineering console in the control
room. You can change programming offline, and download without restarting the system for
the change to be effective.
• The controllers execute control strategies as independent tasks; thus, making changes to part
of the control logic has no impact on the rest.
• The typical DCS has integrated diagnostics and standard display templates that automatically
extend/update when your database changes. This database is central to the system-you don't
have different databases sitting in the controllers
6
Data Communications and Networking Prepared by: CMMFesarit
• DCSs have user-friendly configuration tools, including structured English, control block
libraries, SFC (sequential function chart).
• An important difference between DCSs and PLCs is how vendors market them. DCS vendors
typically sell a complete, working, integrated, and tested system; offering full application
implementation. They offer many services: training, installation, field service, and
integration with your (IT) systems. The DCS vendor tries to be your "one-stop shop."
• The PLC is more of a "do-it-yourself" device, which is sometimes simpler to execute.
• When PLCs were solely replacements for hard-wired relays, they had only digital I/O, with no
operator interface or communications.
• Simple operator interfaces appeared, then evolved into increasingly complex interfaces as PLCs
worked with increasingly complex automation problems. We went from a panel of buttons and
I/O-driven lamps to PLC full-color customized graphic displays that run on SCADA software
over a network.
• PLCs now have many DCS-like control functions (e.g., PID algorithms) and analog I/O. They've
moved past their birthplace: the digital world
• Typical PLC Relay Ladder Logic (RLL) languages include function blocks that can perform
complex control and math functions (e.g., PID algorithms).
• Complex multi-loop control functions (e.g., cascade management and loop initialization) are
not typical.
• The user-written logic is typically one big RLL program, which means you may have to take the
whole PLC off-line to make a change of any size. You also run into database synchronization
problems because of the separation of PLCs and the Man Machine Interface (MMI) software
packages, as opposed to the central databases of DCSs.
• PLC will run in a stand-alone configuration. A DCS controller normally expects an operator
interface and communications, so it can send alarms, messages, trend updates, and display
updates.
• Many PLC installations use interface software from third-party vendors for improved graphics
and various levels of alarming, trending, and reporting - SCADA.
• “PLC + SCADA” = “DCS”
• A PLC may have a third-party package for operator interfaces, LAN interface to PCs, PLC data
highway or bus, redundant controllers with local and distributed I/O. The PLC would have
redundant media support, BUT NOT the redundant communication hardware or I/O bus
hardware you'd find in a DCS.
• Decision between PLC and DCS often depends on “business issues” rather than “technical
features”; factors to consider are:
The internal expertise to execute the project,
Level of support available from a vendor/integrator,
Long-term maintainability, and
Life-cycle costs.
• When deciding between the two, know who will deliver and who will support your system,
and how they will do it.