|
DeltaV History
Path from DCS to DeltaV
In the 60's, IBM created business computers, one of which was the IBM 1600. IBM quickly
learned that it was easier for their customers to train accountants to be programmers than it was
to train programmers to be accountants.
In 1961 Monsanto used an TRW Computer System to perform the first Digital Control System (DCS) to control a
chemical process. Monsanto too, learning from this experience over the years that it is easier to
train Process Control Engineers to be programmers than to train programmers to be Process Control Engineers.
In the 70's and 80's, it was the practice to train Process Control Engineers to be programmers, specifically
learning the language for DDC (Basic) and PRoVOX later. In the 90's this practice continued, teaching Process
Control Engineers to program DeltaV.
Emerson's predecessor, Fisher-Rosemount Systems learned this lesson in the late 80's when it partnered
with IBM to design and developed DeltaV. It was a failure. Bringing in "Duncan" to take over the design
and have people with process control experience design DeltaV was a success.
Coming back to today, the number of Process Control Engineers has been declining over the years and
the number of engineers who primarily want to be programmers has been increasing. The result, a
larger number of engineers now work as programmers for Emerson and the LBPs (Emerson's Impact Local Business Partners) who have no process
control experience. This is especially true for the off-shore Emerson programmers.
This is the "Skills GAP". Companies are having trouble finding and replacing process
control people who are retiring. Productivity in plant processes is taking place in the new digital
instruments and DeltaV controllers.
Today, you the customer have to work harder to get the control system you desire by overseeing and working close
with the DeltaV programmers. In most cases, the Emerson and LBP's end up designing the simple, straight forward system for
implementation. It is left up to the customer to implement the controls to make your system safe and efficient to
detecting problems when running normally, detecting potential problems during emergencies and insuring correct
downloads during "Cold ReStarts".
One means to offset this early in the design or migration process is to developed a FDS (Functional Design Specification)
or DDS (Detail Design Specification) document. Let us help you develop the correct documents for
implementation of a DeltaV System. And then let us implement the DeltaV System for you.
We will document your process and migrate to DeltaV as an Apple to Apple
comparison. We will create the migration with your desired "END" result in mind. Once migrated, DeltaV has many opportunities for creative
improvements: predictive control, optimizing control, enhancing performance and providing more information to the operators.
We can provide training to help your engineers acquire the "right skills". We can provide
training on DeltaV for the operators to adapt to the process on the DeltaV consoles.
Submit a confidentially agreement for us to sign, protecting your data. Submit the "cdv" files of the
project to migrate. We will protect your process design data contained in the "cdv" files. We will then generate
the data necessary for a proposal (Documentation or Documentation and Migration to DeltaV) and
provide examples of the data and documents we will provide.
|