Distributed control system

A distributed control system (DCS) refers to a control

system of a process plant and industrial process wherein
control elements are not only located in central location
(like the brain) but are also distributed throughout the sys-
temwith each component sub-systemcontrolled by one or
more controllers so the intelligence is distributed across
the sections of the plant. DCS follows hierarchy in its
control philosophy with various function spread across .
DCS (Distributed Control System) is a computerized
control system used to automate processes in various in-
dustries.
The entire systemof controllers is connected by networks
for communication and monitoring.
DCS is a very broad termused to monitor and control dis-
tributed equipments in process plants and industrial pro-
cesses .
Chemical plants
Petrochemical industries and reneries
Boiler controls and power plant systems
Nuclear power plants
Environmental control systems
Water management systems
Oil rening plants
Metallurgical process plants
Chemical plants
Pharmaceutical manufacturing
Sugar plants
Dry cargo and bulk oil carrier ships
1 Elements
A DCS typically uses custom designed processors as
controllers and uses both proprietary interconnections
and standard communications protocol for communica-
tion. Input and output modules form component parts
of the DCS. The processor receives information from in-
put modules and sends information to output modules.
The input modules receive information from input instru-
ments in the process (or eld) and the output modules
Computer
Center
Coordinating
Computer
Coordinating
Computer
Supervisory
Computers
Supervisory
Computers
Supervisory
Computers
Supervisory
Computers
C C C C C C C C
Plant Plant
Level 4
Production Scheduling
Level 3
Production Control
Level 2
Plant Supervisory
Level 1
Direct Control
Level 0
Field Level
Functional levels of a typical Distributed Control System.
transmit instructions to the output instruments in the eld.
The inputs and outputs can be either analog signal which
are continuously changing or discrete signals which are
2 state either on or o . Computer buses or electrical
buses connect the processor and modules through mul-
tiplexer or demultiplexers. Buses also connect the dis-
tributed controllers with the central controller and nally
to the Humanmachine interface (HMI) or control con-
soles. See Process automation system.
The elements of a DCS may connect directly to physi-
cal equipment such as switches, pumps and valves and to
Human Machine Interface (HMI) via SCADA. The dif-
ferences between a DCS and SCADA is often subtle, es-
pecially with advances in technology allowing the func-
tionality of each to overlap.
[1]
2 Applications
Distributed control systems (DCSs) are dedicated sys-
tems used to control manufacturing processes that are
continuous or batch-oriented, such as oil rening, petro-
chemicals, central station power generation, fertilizers,
pharmaceuticals, food and beverage manufacturing, ce-
ment production, steelmaking, and papermaking. DCSs
are connected to sensors and actuators and use setpoint
control to control the ow of material through the plant.
The most common example is a setpoint control loop
consisting of a pressure sensor, controller, and control
valve. Pressure or ow measurements are transmitted to
the controller, usually through the aid of a signal condi-
tioning input/output (I/O) device. When the measured
variable reaches a certain point, the controller instructs a
valve or actuation device to open or close until the u-
idic ow process reaches the desired setpoint. Large oil
reneries have many thousands of I/O points and employ
very large DCSs. Processes are not limited to uidic ow
1
2 3 HISTORY
through pipes, however, and can also include things like
paper machines and their associated quality controls (see
quality control system QCS), variable speed drives and
motor control centers, cement kilns, mining operations,
ore processing facilities, and many others.
A typical DCS consists of functionally and/or geograph-
ically distributed digital controllers capable of executing
from 1 to 256 or more regulatory control loops in one
control box. The input/output devices (I/O) can be inte-
gral with the controller or located remotely via a eld net-
work. Todays controllers have extensive computational
capabilities and, in addition to proportional, integral, and
derivative (PID) control, can generally perform logic and
sequential control. Modern DCSs also support neural net-
works and fuzzy application.
DCSs are usually designed with redundant processors to
enhance the reliability of the control system. Most sys-
tems come with displays and conguration software that
enable the end-user to congure the control system with-
out the need for performing low-level programming, al-
lowing the user also to better focus on the application
rather than the equipment. However, considerable sys-
tem knowledge and skill is required to properly deploy
the hardware, software, and applications. Many plants
have dedicated personnel who focus on these tasks, aug-
mented by vendor support that may include maintenance
support contracts.
DCSs may employ one or more workstations and can be
congured at the workstation or by an o-line personal
computer. Local communication is handled by a control
network with transmission over twisted -pair, coaxial, or
ber-optic cable. A server and/or applications processor
may be included in the system for extra computational,
data collection, and reporting capability.
3 History
Early minicomputers were used in the control of indus-
trial processes since the beginning of the 1960s. The IBM
1800, for example, was an early computer that had in-
put/output hardware to gather process signals in a plant
for conversion from eld contact levels (for digital points)
and analog signals to the digital domain.
The rst industrial control computer system was built
1959 at the Texaco Port Arthur, Texas, renery with an
RW-300 of the Ramo-Wooldridge Company
[2]
In 1975, both Honeywell and Japanese electrical engi-
neering rm Yokogawa introduced their own indepen-
dently produced DCSs at roughly the same time, with the
TDC 2000 and CENTUM
[3]
systems, respectively. US-
based Bristol also introduced their UCS 3000 universal
controller in 1975. In 1978 Metso(known as Valmet in
1978) introduced their own DCS system called Damatic
(latest generation named Metso DNA
[4]
). In 1980, Bai-
ley (now part of ABB
[5]
) introduced the NETWORK 90
system, Fisher Controls (now part of Emerson Electric)
introduced the PROVoX system, Fischer & Porter Com-
pany (now also part of ABB
[6]
) introduced DCI-4000
(DCI stands for Distributed Control Instrumentation).
The DCS largely came about due to the increased avail-
ability of microcomputers and the proliferation of mi-
croprocessors in the world of process control. Com-
puters had already been applied to process automation
for some time in the form of both direct digital control
(DDC) and set point control. In the early 1970s Taylor
Instrument Company, (now part of ABB) developed the
1010 system, Foxboro the FOX1 system, Fisher Con-
trols the DC
2
system and Bailey Controls the 1055 sys-
tems. All of these were DDC applications implemented
within minicomputers (DEC PDP-11, Varian Data Ma-
chines, MODCOMP etc.) and connected to proprietary
Input/Output hardware. Sophisticated (for the time) con-
tinuous as well as batch control was implemented in this
way. Amore conservative approach was set point control,
where process computers supervised clusters of analog
process controllers. A CRT-based workstation provided
visibility into the process using text and crude character
graphics. Availability of a fully functional graphical user
interface was a way away.
Central to the DCS model was the inclusion of control
function blocks. Function blocks evolved from early,
more primitive DDC concepts of Table Driven soft-
ware. One of the rst embodiments of object-oriented
software, function blocks were self-contained blocks
of code that emulated analog hardware control compo-
nents and performed tasks that were essential to process
control, such as execution of PID algorithms. Function
blocks continue to endure as the predominant method of
control for DCS suppliers, and are supported by key tech-
nologies such as Foundation Fieldbus
[7]
today.
Midac Systems, of Sydney, Australia, developed an
objected-oriented distributed direct digital control system
in 1982. The central systemran 11 microprocessors shar-
ing tasks and common memory and connected to a serial
communication network of distributed controllers each
running two Z80s. The system was installed at the Uni-
versity of Melbourne.
Digital communication between distributed controllers,
workstations and other computing elements (peer to peer
access) was one of the primary advantages of the DCS.
Attention was duly focused on the networks, which pro-
vided the all-important lines of communication that, for
process applications, had to incorporate specic functions
such as determinism and redundancy. As a result, many
suppliers embraced the IEEE 802.4 networking standard.
This decision set the stage for the wave of migrations nec-
essary when information technology moved into process
automation and IEEE 802.3 rather than IEEE 802.4 pre-
vailed as the control LAN.
3.2 The application-centric era of the 1990s 3
3.1 The Network Centric Era of the 1980s
In the 1980s, users began to look at DCSs as more than
just basic process control. A very early example of a
Direct Digital Control DCS was completed by the Aus-
tralian business Midac in 198182 using R-Tec Aus-
tralian designed hardware. The system installed at the
University of Melbourne used a serial communications
network, connecting campus buildings back to a control
room front end. Each remote unit ran two Z80 micro-
processors, while the front end ran eleven Z80s in a paral-
lel processing conguration with paged common memory
to share tasks and that could run up to 20,000 concurrent
control objects.
It was believed that if openness could be achieved and
greater amounts of data could be shared throughout the
enterprise that even greater things could be achieved. The
rst attempts to increase the openness of DCSs resulted in
the adoption of the predominant operating system of the
day: UNIX. UNIX and its companion networking tech-
nology TCP-IP were developed by the US Department
of Defense for openness, which was precisely the issue
the process industries were looking to resolve.
As a result suppliers also began to adopt Ethernet-based
networks with their own proprietary protocol layers. The
full TCP/IP standard was not implemented, but the use of
Ethernet made it possible to implement the rst instances
of object management and global data access technol-
ogy. The 1980s also witnessed the rst PLCs integrated
into the DCS infrastructure. Plant-wide historians also
emerged to capitalize on the extended reach of automa-
tion systems. The rst DCS supplier to adopt UNIX and
Ethernet networking technologies was Foxboro, who in-
troduced the I/A Series
[8]
system in 1987.
3.2 The application-centric era of the
1990s
The drive toward openness in the 1980s gained momen-
tum through the 1990s with the increased adoption of
commercial o-the-shelf (COTS) components and IT
standards. Probably the biggest transition undertaken
during this time was the move from the UNIX operating
system to the Windows environment. While the realm of
the real time operating system (RTOS) for control appli-
cations remains dominated by real time commercial vari-
ants of UNIX or proprietary operating systems, every-
thing above real-time control has made the transition to
Windows.
The introduction of Microsoft at the desktop and server
layers resulted in the development of technologies such
as OLE for process control (OPC), which is now a de
facto industry connectivity standard. Internet technol-
ogy also began to make its mark in automation and the
DCS world, with most DCS HMI supporting Internet
connectivity. The 1990s were also known for the Field-
bus Wars, where rival organizations competed to dene
what would become the IEC eldbus standard for digital
communication with eld instrumentation instead of 4
20 milliamp analog communications. The rst eldbus
installations occurred in the 1990s. Towards the end of
the decade, the technology began to develop signicant
momentum, with the market consolidated around Ether-
net I/P, Foundation Fieldbus and Probus PA for process
automation applications. Some suppliers built new sys-
tems from the ground up to maximize functionality with
eldbus, such as Rockwell PlantPAX System, Honeywell
with Experion & Plantscape SCADA systems, ABB with
System800xA,
[9]
Emerson Process Management
[10]
with
the Emerson Process Management DeltaV control sys-
tem, Siemens with the SPPA-T3000
[11]
or Simatic PCS
7,
[12]
Forbes Marshall
[13]
with the Microcon+ control sys-
tem and Azbil Corporation
[14]
with the Harmonas-DEO
system. Fieldbus technics have been used to integrate ma-
chine, drives, quality and condition monitoring applica-
tions to one DCS with Metso DNA system.
[4]
The impact of COTS, however, was most pronounced
at the hardware layer. For years, the primary business
of DCS suppliers had been the supply of large amounts
of hardware, particularly I/O and controllers. The initial
proliferation of DCSs required the installation of prodi-
gious amounts of this hardware, most of it manufactured
from the bottom up by DCS suppliers. Standard com-
puter components from manufacturers such as Intel and
Motorola, however, made it cost prohibitive for DCS sup-
pliers to continue making their own components, work-
stations, and networking hardware.
As the suppliers made the transition to COTS compo-
nents, they also discovered that the hardware market was
shrinking fast. COTS not only resulted in lower manu-
facturing costs for the supplier, but also steadily decreas-
ing prices for the end users, who were also becoming in-
creasingly vocal over what they perceived to be unduly
high hardware costs. Some suppliers that were previ-
ously stronger in the PLC business, such as Rockwell Au-
tomation and Siemens, were able to leverage their ex-
pertise in manufacturing control hardware to enter the
DCS marketplace with cost eective oerings, while the
stability/scalability/reliability and functionality of these
emerging systems are still improving. The traditional
DCS suppliers introduced new generation DCS System
based on the latest Communication and IEC Standards,
which resulting in a trend of combining the traditional
concepts/functionalities for PLC and DCS into a one for
all solutionnamed Process Automation System. The
gaps among the various systems remain at the areas such
as: the database integrity, pre-engineering functionality,
system maturity, communication transparency and relia-
bility. While it is expected the cost ratio is relatively the
same (the more powerful the systems are, the more ex-
pensive they will be), the reality of the automation busi-
ness is often operating strategically case by case. The
current next evolution step is called Collaborative Process
4 5 REFERENCES
Automation Systems.
To compound the issue, suppliers were also realizing that
the hardware market was becoming saturated. The life
cycle of hardware components such as I/O and wiring is
also typically in the range of 15 to over 20 years, making
for a challenging replacement market. Many of the older
systems that were installed in the 1970s and 1980s are
still in use today, and there is a considerable installed base
of systems in the market that are approaching the end of
their useful life. Developed industrial economies in North
America, Europe, and Japan already had many thousands
of DCSs installed, and with few if any new plants being
built, the market for new hardware was shifting rapidly to
smaller, albeit faster growing regions such as China, Latin
America, and Eastern Europe.
Because of the shrinking hardware business, suppliers be-
gan to make the challenging transition from a hardware-
based business model to one based on software and value-
added services. It is a transition that is still being made
today. The applications portfolio oered by suppliers ex-
panded considerably in the '90s to include areas such as
production management, model-based control, real-time
optimization, plant asset management (PAM), Real-time
performance management (RPM) tools, alarm manage-
ment, and many others. To obtain the true value from
these applications, however, often requires a considerable
service content, which the suppliers also provide.
3.3 New age systems of 2010 onwards
In the new world of distributed control system following
new technologies are emerging and taking roots :
1.>Wireless systems and protocols - Esp. ISA 100 and
Wireless HART 2.>Remote transmissions, logging and
data historian 3.>Mobile interfaces and controls 4.>Em-
bedded webservers
Increasingly and ironically distributed control systems
are getting centralised at plant level and are getting dis-
tributed in the ability to log in and access providing a su-
perior man machine interface esp. from remote access
and portability standpoint.
As wireless protocols are getting rened by the day its is
increasingly getting integrated into DCS . Controllers of
DCS are coming with embedded servers and provide on
the go web access. Most vendors have their HMI mo-
bile ready both for android and IOS . With these inter-
faces threat of breach of security hence danger to plant
and process control are now very real.
4 See also
OSIsoft
BAILEY DCS Expert
BNF Technology Inc.| ARIDES (DSC HMI)
Building Automation
Direct Digital Control
SCADA
PLC
Fieldbus
First-out alarm
Midac
Safety instrumented system, (SIS)
Industrial control systems
Industrial safety systems
Annunciator panel
EPICS
TANGO
5 References
[1] Introduction to Industrial Control Networks. IEEE
Communications Surveys and Tutorials. 2012.
[2] Stout, T. M. and Williams, T. J. (1995). Pioneering
Work in the Field of Computer Process Control. IEEE
Annals of the History of Computing 17 (1).
[3] CENTUM
[4] Metso DNA
[5] INFI 90
[6] DCI-4000
[7] Foundation Fieldbus
[8] Foxboro I/A Series Distributed Control System
[9] ABB System 800xA
[10] Emerson Process Management
[11] SPPA-T3000
[12] Simatic PCS 7
[13] Forbes Marshall
[14] Azbil Corporation
5
6 External links
DCS Selection MBA research program with many
Links
Example of DCS system: Mark VIe by General
Electric
An even better example of DCS system: Control
Design Platform by ICD
Proviewis probably the rst Open Source systemfor
process control and automation in the world.
FreeDCS is another Open Source Distributed Con-
trol System
INFI90/Bailey/ ABB DCS Engineer
6 7 TEXT AND IMAGE SOURCES, CONTRIBUTORS, AND LICENSES
7 Text and image sources, contributors, and licenses
7.1 Text
Distributed control systemSource: http://en.wikipedia.org/wiki/Distributed_control_system?oldid=629244570 Contributors: Mav, Pnm,
Smack, Mydogategodshat, Charles Matthews, Greenrd, Radiojon, Gepwiki, Vikasy, RedWolf, Auric, Hadal, Kevin Sa, Imjustmatthew,
Spalding, Billymac00, Alansohn, Wtshymanski, Rjwilmsi, Pjetter, Allen Moore, Imrehg, Roboto de Ajvol, The Rambling Man, Trini-
Triggs, Byron Vickers, SamMason, Welsh, Jpbowen, Tony1, Mkill, SmackBot, Elonka, Royalguard11, Bluebot, Sadads, SirLamer, A5b,
Jmuns, Kuru, Caim, Shrew, Mbeychok, M@sk, Iridescent, Heqs, Drinibot, EmersonsJimCahill, Corpx, Thijs!bot, AntiVandalBot, Psylli-
con, Pugges, Email4mobile, Ripogenus77, JaGa, Iy01, Lobrieniii, Mausy5043, Erkan Yilmaz, Russ84, Martin Hollender, Rembecki,
Krishnaeee, Supersteve04038, JudeFawley, Ctmt, SpecMode, Billinghurst, HiDrNick, SieBot, Euryalus, Qi78, FrancisControlDraw,
Hoorah83, Fratrep, Sfan00 IMG, ClueBot, WillemHazenberg, Shelldince, Mild Bill Hiccup, Niceguyedc, StigBot, Wdsanderson, Sun
Creator, Rajendu.choubisa, PotentialDanger, SoxBot III, Gardenparty, Benjamin.rankin, Dthomsen8, Addbot, Mikewings, Jelsova, Chzz,
Pjadot, Luckas-bot, Yobot, Ptbotgourou, Amirobot, KamikazeBot, AnomieBOT, Daniele Pugliesi, Materialscientist, Citation bot, Gjo-
ertz, Rainor, Srikanthpisipati, Miym, J04n, FrescoBot, Joe.dolivo, GWS EE, Citation bot 1, SchreyP, Overjive, Tbhotch, Owenpr, Ervast,
Nitinkirloskar, EmausBot, RA0808, K6ka, 15turnsm, ZroBot, Donner60, RoyKok, ChuispastonBot, Bbrandtpe, Pokbot, ClueBot NG,
Reclute, Widr, Helpful Pixie Bot, Cdeverille, Imranalnoor, Robpelu, Hallows AG, User48365, Textory, Rprogatto, Jimkalman, Arcandam,
Utsav91292, Anthony hairon, Graphium, Wateresque, JamesMoose, NimaMehrzad, Jeemys, Mvaidya and Anonymous: 161
7.2 Images
File:Factory.svg Source: http://upload.wikimedia.org/wikipedia/commons/a/a2/Factory.svg License: Public domain Contributors: Self-
made, taken from Image:1 9 2 9.svg Original artist: Howard Cheng
File:Functional_levels_of_a_Distributed_Control_System.svg Source: http://upload.wikimedia.org/wikipedia/commons/1/10/
Functional_levels_of_a_Distributed_Control_System.svg License: CC-BY-SA-3.0 Contributors: Own work Original artist: Daniele
Pugliesi
7.3 Content license
Creative Commons Attribution-Share Alike 3.0