DCI stands for Distributed Control Instrumentation.
The Series 3000 / 3800 system was retired in about 1982 and all new systems where then DCI.
In 1979, the DCU had a default module mix that provided good continuous control._ This
software and hardware combination was called an Analog Control Unit._ So in 1979 someone could
say they have a DCU1000 or they could say they have an ACU. _ Both were equivalent.
Then in 1980 Fischer & Porter developed newer modules that would do Batch control and other discrete control logic._ They
called this hardware / software combination a Multifunction Control Unit or MCU since it could
do continuous control as well as batch control._ So they had a DCU1000 that
could be an ACU flavor or an MCU flavor.
Also to come out in the DCI-4000 product line was two types of boxes that would sit between the DCU1000
and the CTBs. They would allow for manual control of the plant. Basically they were just switches and potentiometers (pots).
The one for analog control was called a ABU (Analog Backup Unit) and the one for Descrete (on/off) Control was called a Contact Backup Unit (CBU).
Review:
The operator Screen was called a Local Operator's Panel (LOP)(pronounced "el oh pee")._ Lets look at all of these words one at
a time._ The word Local means that the LOP was connected directly to the DCU1000 using a serial port._
The word Operator means that this was primarily used for controlling and monitoring the plant. (versus Configuring the system)._ And the
word Panel is important too, because this CRT was to replace the old traditional panel in the control room._ This meant
that instead of seeing individual controllers on the wall, the operator would see graphical representations of those controllers on the screen.
How did one configure the modules in a DCU?_ Answer:They used a silver box with a keypad and
a reel to reel digital tape. The box was silver metal on the outside and it had a handle. It was
like a small suitcase or large briefcase. This box (also known as the "silver bullet") connected
to a port on the LOP and was able to configure the DCU1000.
This is all probably more information about DCI-4000 than you want to know, but there were a few
more products.
The printer that was used was an Anadex model. This connected directly to the LOP. It printed
out Alarms that came from the DCU and Logs / reports that came from a special DCU Controlware Module called a LOG module.
The early I/O wiring connections used a Customer Termination Board or CTB. The field wiring
came into the cabinet and was attached to screw terminations on the CTB. Then, special amp connectors
were used to route 8 inputs / outputs at a time to the back plane of the DCU, where the internal
wiring of the backplane would route the signal to the appropriate I/O board in the DCU.
Also during this time period, there was a need for getting data to the outside world (even as today!).
So, about 1982/1983 a machine was designed based on a DEC 11/23 computer to store and forward information
from the DCI-4000 system to "any" other computer. But mostly data would be sent to a Third-party VAX computer.
This machine/product was called a Store and Forward Teminal or SFT.
It was never a very popular product becuase it would hang sometimes and not send data.
The very first few DCU2000 units were 1A highway compatible. In this way, an existing customer who had a DCU1000
could upgrade to a DCU2000 with not one other change.
In 1986 a super new version of the LOC came out called LOC2000. In fact, the LOC2000 had three
versions: LOC2000, LOC2500 and LOC2800. Also, a new board for the DCU2000 came out called
an ICOM/X board. This board could communicate to PLCs and Micro-DCI. In other words, more changes
were comming.
It was a nice little product line at the time.
One of the major problems with this arrangement, however, was that the LOC was configured
completely differently than the DOC. That meant different graphic tools, different log tools,
different everything.
But in reality, the product line was getting old. Controlware had only changed once since 1979 (and
that change was very minor -- having to do with the way DCU2000 addressed I/O boards versus
the way DCU1000s addressed I/O boards.
The Early DCI System Six had these products:
Note that the system was only Unix based. (It used a MIPS computer). Also it was compatible
with the older DCU2000's if the DCU2000's had the new "G" card installed.
In 1993 - 1994 Silicon Graphics Inc (SGI) bought out MIPS Inc. That force F&P to make a decision. Do they
stay with the new SGI platform or go with someone else (like SUN)? They decided to ride the ride and stay with
SGI. F&P Also decided on a different and better product model. Instead of having two different
platforms both based on the same machine but really only different in the software, they chose to
have one platform with various software options.
1994 Hardware Options:
1994 Software Options:
Late 1994 Software Products
At this point the DCI Produt line was now truely open in the platform area since any Pentium PC
could be used to run the plant.
NOTE:
Industrial IT
Industrial IT is what ABB is calling their next generation DCS.
Our company has delayed the implementation of AC800M controllers until next year -- 2004.
ABB is telling DCI users that they can use s800 IO as a replacement for remote IO using the new profibus card. We purchased a P-BUS card and had CTK (you need CTK for the P-BUS card) however the documentation is scant on the P-BUS configuration.
Click on the icon to give me feedback about this site! -- Thanks.
This page presents a history of DCI-4000, DCI-5000, DCI-System, and DCI System Six.
_ Some Fischer & Porter and some Bailey Controls history is also included.
In the beginning
Fischer & Porter came up with the name Distributed Control Instrumentation and put
a number next to it i.e. 4000 to make DCI-4000. _ Why did they use 4000
instead of 3000 or 2000 or 1000? Well because they already had a Series 1000, Series 2000
Series 3000 and even a Series 3800 computer system based on a Sperry Univac machine. _ In
Fact, in 1979 when DCI-4000 first came out, F&P was still selling the Series 3800 system. This Series 3800 System
was a monolithic control system in that all of the inputs and outputs came into one computer.
(Yes, they did have remote muxes that allowed them to group I/O into areas and then feed all of those
signals in to the computer system, but it was still monolithic.)
DCI-4000
The controller for this product line is called a DCU (Distributed Control Unit). _ Since they
like numbers, and since this was the first Distributed Control Unit, they named it DCU-1000.
The software that ran in the DCU1000 was called Controlware. _ Controlware
is the code that runs the algorithms that do the control._ For example Proportional Integral and
Derivative control._ The software blocks that make up Controlware are called Software
Modules or just Modules._ There is a mixture of different types of modules
in any DCU1000._ For Example there may be 5 Analog Input Modules, 5 Control Modules, and
5 Analog Output Modules._ Whereas in another DCU1000 there may
be 6 of these three Modules._ So one DCU has one Module mixture or Module Mix and
the other has a different Module Mix.
DCU1000: Distributed Control Unit 1000
ACU: Analog Control Unit
MCU: Multifunction Control Unit
Controlware: The software that did the actual control using software blocks called modules.
ABU: Analog Backup Unit
CBU: Contact Backup Unit
In Living Color
The LOP was ok but it was Black & White and the screen was only 9 inches. Also, there were a few
features that were obviously lackling. It soon became obvious that a color console was needed.
Also, The local aspect of the LOP was holding back the product line.
In 1981 two major changes in the product line occured.
One was that a new data highway was developed, and two, a new highway based operator console
was developed. Not much technically is known about the original highway except that it used
a twinaxial cable (two conductors surrounded by a shield) and was propietary. Fischer & Porter
called it the 1A highway.
The highway based operator station was called the Central Operator's Panel or COP. (Actually pronounced like "cop"
not like "see oh pee".
The COP was based on a DEC 11/44 machine and used two RL02 Disk Drives. Each 11/44 could drive two
Color CRTs. Some of the features included in the COP were: Graphics, Historical Trends, and Logs/Reports. The system
could have highway based consoles as well as local ones.
In Living Color II
So, in 1981 a customer could pick from two versions of operator station. There was growing demand
however for a color version of the LOP. In 1982, the pressure was so great, that Fischer & Porter Canada
developed their own Local Color Terminal or LCT. The LCT development was completely independent from
the DCI-4000 development in Warminster, PA. Only a few were sold in the US but it made a mess out
of the marketplace for DCI-4000 customers. Now they had a choice of LOP, LCT, or COP. The Engineering group in Warminster
finally developed a local color operator's console in 1983. This was called the LOC or Local Operator's Center. It was a great machine.
The LOC was very reliable and soon the LCT sales stopped and the LCT was retired from the Canadian lineup.
Time Marches On
1984 was a boring year -- nothing much changed in the product line.
1985 Was a huge year for changes.
First, the DCU was updated and changed completely. So a new name was added to the DCI-4000 world: DCU2000.
The DCU2000 was better for a lot of reasons than the DCU1000. It had more memory, faster processor, and more I/O capability. The
I/O was no longer required to be in special slots so in a lot of cases, the footprint was smaller. The I/O system stayed almost
the same which meant that most of the DCU1000 I/O boards would work in the DCU2000. The DCU2000 used CTBs also.
The DCU2000 was made up of modular boxes versus the "one box holds everything" theory of DCU1000.
These modular boxes were: PCU (Process Control Unit) which held the processor, memory, highway boards. and the
PIU (Process Interface Unit) which held the input and output (I/O) boards. To this day, some people
still refer to the DCU2000 as a PCU. Of course a DCU2000 is actually a PCU plus a PIU.
Also in 1985, the COP was changed to a newer processor and the Distributed Operator's Console (DOC) (Pronounced "doc") was born.
The DOC was ETHERNET based which meant that the DCU2000 had to be upgraded to ETHERNET also. This was done, and only a handful
of DCU2000 1A Highway compatible units ever shipped. They were all upgraded to ETHERNET versions.
1995 DCI-System
At this point, the product line was still called DCI-4000. This wasn't good because some people
thought they should change the name since there were so many changes in the products. Other
people inside F&P thought that if they change the name, then they would be stuck with obsolete
products. So they compromised and named the new product line the DCI-System. F&P Thought
that would solve all of their problems forever since the name would never have to be changed.
However...
The person who came up with DCI-SYSTEM either was swayed or left because around this time the
product name was changed again to DCI-5000.
DCI-5000
DCI-5000 was made up of the following:
Product Name Communication Method Function
DCU2000 Ethernet (XNS) to DOC
Serial to LOCController. Also Communicates
to PLCs via ICOM/X board
LOC2000 Serial Basic Operating Functions including graphics
LOC2500 Basic plus Historical Trends
LOC2800 Basic + Historical+ Communication to a PC
DOC1000 Ethernet (XNS) Full Featured Operator Station
The good part was that the LOC was a very robust machine. It hardly ever failed. Also it could
be connected to a DCU1000 or a DCU2000 seamlessly!
The DOC could only be connected to a DCU2000 running Ethernet.
As far as the Store & Forward Terminal (SFT) was concerned it was dead as a machine and was transformed
into a circuit board that would fit into a VAX computer. The SFT board did the same function as an SFT machine
but of course it was smaller and somewhat less expensive. Again though not too many sites had this product.
Time Marches On Again
1986,1986,1987,1988,1989,1990,1991: There were changes to the product line all through
these years. But they were mostly cosmetic. The DCU eproms were update a number of times,
The LOC software went through many upgrades, and the DOC was changed physically to become
a DOC2000. The DOC software also was upgraded many times throughout this period. In Fact,
some people at F&P thought the DOC had changed so much that they renamed it the Command Center1000.
A new product line was on the way...
DCI SYSTEM SIX
1992 brought DCI SYSTEM SIX. This was a revolution of a system. The DCU changed, the Operator's Consoles changed, and even
Controlware (the software in the DCU) changed. Even the way the product name looked changed.
They went from a number (5000) to a word (Six).
It was a totally new system that would work with the old system!
It was based on the newest technology and used a graphic rendering system from Sherrill-Lubinski.
called the Sherrill-Lubinski Graphic Modelling System or SL-GMS for short.
Product Communication Method Function Compatible with
DCU3200 Ethernet (TCP/IP protocol) Full Featured Controller
Including Batch
Talked to XDC and DMC
XDC
X-Window Display CenterEthernet (TCP/IP) Full Featured Unix based Operator Console
Supporting 5 screens
Talked to DCU3200
and DCU2000G
DMC
Data Management CenterEthernet (TCP/IP) Full Featured Unix based Operator Console
5 Screens PLUS
Third Party Unix ProgramsTalked to DCU3200
and DCU2000G
G Card Ethernet (XNS and TCP/IP) Card to make the DCU2000
TCP/IP compatible and become a DCU2000Gtalked to XDC,DMC and older DOCs
So all in all, it was a well thought out system. There were no longer any tool conflicts because
there was only one set of tools for each system wide feature. The Store & Forward Terminal (SFT) funtion
was integrated into the DMC.
Product Communiction Operating System
AP6400
The new SGI Unix box
AP=Application Platform.Ethernet TCP/IP Unix
DCU3200 Ethernet TCP/IP F&P VOS
G Card Ethernet TCP/IP and XNS F&P VOS
Product Function Platform
XDC Operating Screens
(graphics, trends, etc.)AP6400
DMC Same as the XDC software
but also had ability to
run 3rd party programsAP6400
SPC Statistical Process Control AP6400 running DMC software
Progress Relational Database AP6400 running DMC software
Controlware II Control Software to run continuous
and batch algorithmsDCU3200
Times, They Are A-Change'n
In 1994 Elsag Bailey purchased Fischer & Porter Company. Nothing Changed in the product line
because of this fact.
Also in 1994, the DCI product group of Elsag Bailey released a new product platform (that they had
been working on for years in Warminster, Pennsylvania) based on a PC running
Windows NT 3.51. It was called a Personal Work Center or PWC3200. Here are the new charts:
Late 1994 Hardware List
Product Communiction Operating System
AP6400
The new SGI Unix box
AP=Application Platform.Ethernet TCP/IP Unix
(any PC) Ethernet TCP/IP
using 3rd party cardWindows NT 3.51
DCU3200 Ethernet TCP/IP F&P VOS
G Card Ethernet TCP/IP and XNS F&P VOS
Product Function Platform
XDC Operating Screens
(graphics, trends, etc.)AP6400
DMC Same as the XDC software
but also had ability to
run 3rd party programsAP6400
PWC3200 Same as the XDC softare
AND can run any Windows NT
compatible Program(any PC)
SPC Statistical Process Control AP6400 running DMC software
Progress Relational Database AP6400 running DMC software
Controlware II Control Software to run continuous
and batch algorithmsDCU3200
To Some, this Section is Titled: Life Is Stranger Than Fiction
To Others, this Section is Titled: The Bailey Way
Since Elsag Bailey now owned the technology for the PWC3200 (Which by the way was pretty neat), they decided
to use it to improve the Infi-90 (also known as Infi-90 Open) product line.
Elsag Bailey sent the core software to Elsag Bailey Canada and had them design a tag database for it. Voila!
In 1996 Elsag Bailey released the PWC90. It was exactly like the PWC3200 except that it had a tag database. Anyone
reading this page would know that the Tag database in DCI is in Controlware in the DCU.
Anyway...
Also at this time Elsag Bailey was trying to come up with the next generation Distributed Control System. They could see that
with just some minor effort, the PWC3200 was transfered into the Infi-90 world.
1996: Elsag Bailey purchases Hartman & Braun, a German based company that had a Unix based Control
system. BUT the really amazing thing about the H&B system was that it was based on Sherrill-Lubinski Graphic Modelling System
or SL-GMS -- The very same way that DCI System Six was based.
Now it appeared Elsag Bailey had their answer: Combine all three of their major systems (
DCI SYSTEM SIX, Infi-90 Open, and Hartman & Braun's ContronicS) into a new system called Symphony.
Today, the new Symphony System screens look exactly like the 1992 DCI SYSTEM SIX screens except for
the new nifty Symphony logo. The DCU3200 has had one major change in the processor board and many
changes in software. The PWC3200 software has been upgraded and now
runs on Windows NT 4.0. Also the whole product line has been integrated into Symphony.
This means that the DCU3200 is now called the Harmony DCU. The PWC3200 is now called Conductor NT,
and the AP6400 platform is called the Conductor UX. Now that ABB has bought Elsag Bailey, who knows what fun is in store!
As of May 2002, the Conductor UX (a.k.a. XDC) is now in what ABB calls CLASSIC MODE. This means that it is not ACTIVELY for sale but it is still for sale. Confused? You can still purchase it for the next 7 years. However ABB says that they have a replacement for it. They say that the replacement is the Conductor NT (a.k.a. PWC). You may or may not agree with this. ABB is trying to get new customers to not purchase a UNIX machine, but to go directly to an NT / 2000 Machine. (DCI SYSTEM SIX is not yet ready to run on XP). Other products that also are in CLASSIC MODE include: the DCU2000 "G" Card, and the DIO board. The "G" card does not have a direct replacement however everyone who had DCU2000's and who have not upgraded to DCU3200 should do it now. The DCU2000 is a 1985 vintage product and has no business controlling any process today. The DIO (Distributed I/O) board controls the REMOTE I/O subsystem. This system is being phased out in favor of a PROFIBUS solution. The replacement card for the DIO is called a PBUS (Profibus) card. The unusual thing about this card is that there is no need for an ITB (Instrument Termination Board). The Profibus cable plugs directly into the PBUS Card. The latest software level for DCI is SR5 (Software Release 5), released in April 2002.
And the Future?
Someone wrote on 27 January 1999:
"You mentioned a printer used with the Old LOP as Anaxter was it Anadex???
what about SFT's 'PCU's PUI'S etc..Loaded lots of BETA software
Remember when it took 2 days to sygen a system. Good history"
He/she is correct ... it was Anadex. I corrected it in the body.
Also, I added SFT's, PCU's and PIU's (I think you meant PIU and not PUI).
Yes! I remember when we had to sysgen a system. I forgot all about that.
Someone wrote on 6 March 1999:
"The Conductor has also been adapted for Micro-DCI to succeed the
Supervisor-PC. It is now at rev. 2.0 which includes graphical Micro-Tools. It
works nicely with Micro-DCI controllers building a tag database automaticaly
without messing around with instrument and database addresses.
Support of the Conductor-NT for the H&B Freelance 2000 (former Digimatik) is
planned."
Yes, The Conductor (latest verion of PWC3200) is available for Micro-DCI. The unfortunate
thing is that this product line (Micro-DCI) has be exiled to the Fischer & Porter (instrumentation)
part of the business. By doing this, Bailey has been slowly strangling the product line
into exitinction. Maybe ABB will wake this great product line up and get it synchronized
with the rest of Symphony (or whatever ABB will call it).
The Hartmann & Braun Digimatik product line was brought into the Bailey world when
Bailey purchased Hartmann & Braun. They renamed it Freelance because they thought
digimatik sounded too much like something that was sold on late-night UHF TV. Freelance
has its own operator console software. However if you would want a Symphony (System Six)
look and feel to it, one can put a Conductor "on top" of the Freelance controller.
When this option first came out it was called Symphony Solo. However since then Bailey
made an update to the Conductor product (Conductor NT 2.2) that will allow the conductor
to be connected to System Six DCUs, and / or Infi-90 MFPs, and / or Freelance 2000 controllers
at the same time! Also it will allow for a connection to any OPC product like PLCs.
Thanks for the comment and brining back memories!