DCS Process control
Elements of DCS process control
Elements of a DCS may directly connect to physical equipment such as switches, pumps and valves or can work through an intermediate system like a SCADA.
History of DCS process control
In 1975 Honeywell and Japanese electrical engineering introduced their own independently produced DCS's at about the same time.In 1980 Bailey introduced the NETWORK 90 system along with Fischer and Porter Company introducing DCI (Distributed Control Instrumentation) 4000.DCS came mostly due to the increased availability of microcomputers an dthe proliferation of microprocessors in the world of process control.
Central to the DCS model was the inclusion of control function blocks.They evolved from early, primitive DDC concepts of "Table Driven" software.On of the first object oriented software was a self contained "block" of code that emulated analog hardware control components and performed tasks that were essential to process control.Function blocks continue last as the predominant method of control for DCS suppliers.
Applications for DCS process control
A typical DCS consists of functionally and/ or geographically distributed digital controllers capable of executing from 1 to 256 or more regulatory control loops in one control box.They may employ one or several workstations and can be configured at the workstation by an offline personal computer.
Digital communication between distributed controllers, workstations and other computing elements is one of the major advantages of the DCS process control
A typical DCS consists of functionally and/or geographically 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 integral with the controller or located remotely via a field network. Today's controllers have extensive computational capabilities and, in addition to proportional, integral, and derivative (PID) control, can generally perform logic and sequential control.
DCSs may employ one or several workstations and can be configured at the workstation or by an off-line personal computer. Local communication is handled by a control network with transmission over twisted pair, coaxial, or fiber optic cable. A server and/or applications processor may be included in the system for extra computational, data collection, and reporting capability.
control components 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 technologies such as Foundation Fieldbus today.
Distributed control system
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 Australian business Midac in 1981-1982 using R-Tec Australian 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 2 Z80microprocessors whilst the front end ran 11 in a Parallel Processing configuration with paged common memory to share tasks and could run up to 20,000 concurrent controls 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 first 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 technology TCP-IP were developed by the 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 first instances of object management and global data access technology. The 1980s also witnessed the first PLCs integrated into the DCS infrastructure. Plant-wide historians also emerged to capitalize on the extended reach of automation systems. The first DCS supplier to adopt UNIX and Ethernet networking technologies was Foxboro, who introduced the I/A Series system in 1987.
The Application Centric Era of the 1990s
The invasion 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 technology also began to make its mark in automation and the DCS world, with most DCS HMI supporting Internet connectivity. The '90s were also known for the "Fieldbus Wars", where rival organizations competed to define what would become the IEC fieldbus standard for digital communication with field instrumentation instead of 4-20 milliamp analog communications. The first fieldbus installations occurred in the 1990s. Towards the end of the decade, the technology began to develop significant momentum, with the market consolidated around Foundation Fieldbus and Profibus PA for process automation applications. Some suppliers built new systems from the ground up to maximize functionality with fieldbus, such as ABB with System 800xA, Emerson Process Management with the DeltaV control system, Siemens with theSimatic PCS7 and azbil from Yamatake with the Harmonas-DEO system.
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 prodigious amounts of this hardware, most of it manufactured from the bottom up by DCS suppliers. Standard computer components from manufacturers such as Intel and Motorola, however, made it cost prohibitive for DCS suppliers to continue making their own components, workstations, and networking hardware.
As the suppliers made the transition to COTS components, they also discovered that the hardware market was shrinking fast. COTS not only resulted in lower manufacturing costs for the supplier, but also steadily decreasing prices for the end users, who were also becoming increasingly vocal over what they perceived to be unduly high hardware costs. Some suppliers that were previously stronger in the PLC business, such as Rockwell Automation, Schnieder and Siemens, were able to leverage their expertise in manufacturing control hardware to enter the DCS marketplace with cost effective offerings. 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 solution -- named "Process Automation System/Controller".
To compound the issue, suppliers were also realizing that the hardware market was becoming saturated. The lifecycle 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 began 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 offered by suppliers expanded 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 management, and many others. To obtain the true value from these applications, however, often requires a considerable service content, which the suppliers also provide. DCS supplier such as azbil known as Yamatake services have also expanded in scope to the point where many suppliers can act as Main Automation Contractors (MACs), providing a single point of responsibility for all automation-related facets of a project.
SIXNET specializes in high performance process control solutions that are based upon truly open standards. Using SIXNET modular, scalable controllers and I/O blocks with our remarkably easy to use configuration tools, gives you the benefits of a turnkey automation system without the big price tag. SIXNET's thirty year dedication to truly open systems and continuous innovation give you unique advantages.
Scalable Systems that will grow with your requirements (up to 50,000 I/O)
Truly open standards gives you freedom to choose suppliers and products
https://www.sixnetio.com/html_files/products_and_groups/scs.htmIntegrators Can Differentiate Their Solutions - The Linux open tools let you createunique capabilities
https://www.sixnetio.com/html_files/products_and_groups/scs.htmReliability Through Redundancy - Redundantprocessors, networks and I/O channels
https://www.sixnetio.com/html_files/products_and_groups/scs.htmhttps://www.sixnetio.com/html_files/products_and_groups/redundancy.htmBest Value Solutions - Big system performance for the price of just the components