Scribd
Upload
2K views

DeltaV Training

The configuration engineer uses a top-down approach to develop the control strategy for a DeltaV system by making high-level decisions about the overall system and plant, logically dividing the system into areas, and identifying modules to control field devices within areas. Using templates and a library of existing modules provided in DeltaV Explorer and Control Studio, the engineer can develop over three-fourths of the control strategy before defining unique modules and moving to lower levels of detail. DeltaV software supports function blocks, sequential function charts, and structured text within a single control module.

Uploaded by

Victor Biacolo
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
2K views

DeltaV Training

The configuration engineer uses a top-down approach to develop the control strategy for a DeltaV system by making high-level decisions about the overall system and plant, logically dividing the system into areas, and identifying modules to control field devices within areas. Using templates and a library of existing modules provided in DeltaV Explorer and Control Studio, the engineer can develop over three-fourths of the control strategy before defining unique modules and moving to lower levels of detail. DeltaV software supports function blocks, sequential function charts, and structured text within a single control module.

Uploaded by

Victor Biacolo
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 2

Developing the Control Strategy

The configuration engineer uses a top-down engineering approach to develop the control strategy for a DeltaV
system. The DeltaV system is divided into levels so that the users can choose the level of detail at which they
want or need to work. The following figure shows the levels into which the DeltaV system is divided:

Control Strategy Diagram
Typically, the configuration engineer follows this sequence:
1. Makes high-level decisions that apply to the overall system and plant and uses the DeltaV Explorer to
define the system characteristics. (The configuration engineer does not need to be concerned with lower
details initially.)
2. Moves down a level in detail and decides how to logically divide system into areas. Areas are logical
divisions of a process control system. They can be physical plant locations or main processing
functions.
3. Progresses another level and identifies the modules that control the field devices within those areas.
The configuration engineer can use the existing modules in the library as starting points for the modules
required by the control strategy.
All of the previous steps can be done in the DeltaV Explorer. Using the library provided, more than three-
fourths of the control strategy can be developed by duplicating existing library modules in the DeltaV Explorer.
Then, the control strategy for the unique modules is defined using Control Studio. In Control Studio, engineers
can define and modify the control strategies, cut and paste a large portion of the configuration, and then fill in
the details.
Engineers can also decide when to move to the next level of detail. In each level, most of the structure and
characteristics for typical control strategies are already configured for the engineer, except for minor details.
For example, module templates are used as a starting point for modules. The templates can define everything
about the type of control, except for a few operating parameters. Using this type of general approach, the
engineers can lay out the control strategies at each level, cut and paste the major pieces, fill in details, and then
reveal the next level of detail.
DeltaV software supports three types of common control languages for configuration: function blocks, sequential
function charts, and structured text. Within a single control module, you can intermix these control languages.
For example, a single module can leverage function blocks for closed loop analog control and Sequential
Function Charts to perform interlocking.
All three languages execute within the controller in their native form. There is no translation from one language
to another prior to execution.
c

You might also like