Академический Документы
Профессиональный Документы
Культура Документы
Division 17 - Instrumentation
Title: DeltaV Configuration Standards
Revision: 1
Document #: CS17160
Revision Date: 02/21/2013
Page: 1 of 58
Effective Date: 04/29/2013
TABLE OF CONTENTS
1.
PURPOSE.............................................................................................................................................................................. 3
2.
SCOPE ................................................................................................................................................................................... 3
3.
4.
5.
INTERLOCKS...................................................................................................................................................................... 13
7.1.
7.2.
8.
EQUIPMENT MODULES................................................................................................................................................... 12
6.1.
6.2.
7.
6.
9.
9.2.1.
9.2.2.
9.2.3.
10.
Document #: CS17160
Revision Date: 02/21/2013
Page: 2 of 58
Effective Date: 04/29/2013
Security ............................................................................................................................................................... 17
Users ................................................................................................................................................................... 17
Additional Setup................................................................................................................................................. 18
ALARM MANAGEMENT............................................................................................................................................... 50
11.1.
11.2.
11.3.
12.
12.1.
12.2.
12.3.
13.
AMS .................................................................................................................................................................................. 54
14.
GLOSSARY..................................................................................................................................................................... 55
1.
Document #: CS17160
Revision Date: 02/21/2013
Page: 3 of 58
Effective Date: 04/29/2013
PURPOSE
The purpose of this specification is to outline configuration standards to be used for the DeltaV
Distributed Control System (DCS) at the Kankakee plant.
2.
SCOPE
These standards apply to anyone configuring the Kankakee plant DeltaV system (inside
engineers, outside contractors). Deviations from these standards must be approved by the plant
Process Control Engineer.
3.
Location
019-C-1
Area 19 Controller 1
097-C-1
Area 97 Controller 1
097-C-2
Area 97 Controller 2
Document #: CS17160
Revision Date: 02/21/2013
Page: 4 of 58
Effective Date: 04/29/2013
Corresponding P&IDs
019-R-1
Drawing 1
019-WFE-2
Drawing 2
090-DE-206
Drawing 3
Module Type
Document #: CS17160
Revision Date: 02/21/2013
DST Description
DST Tag*
Page: 5 of 58
Effective Date: 04/29/2013
Module Tag
Module
Description
082-P-100
R1 supply pump
021-XV-200
R2 outlet valve
019-EV-F101
F101 carriage
valve
044-HV-T3
T3 supply valve
090-XV-300
Out 1
Out 2
In
Out
In 1
In 2
082-HR-P100
082-HS-P100
082-HI-P100
021-SV-200
021-ZSC-200
021-ZSO-200
Out
019-SV-F101
In 1
In 2
Out
In 1
In 2
044-ZSC-T3
044-ZSO-T3
090-SV-300
090-ZSA-300
090-ZSB-300
Discrete Monitoring
In
072-XS-400
072-XI-400
Discrete Alarm
In
046-LSH-T4
046-LAH-T4
Discrete Output
Out
072-XO-500
072-XD-500
Analog Monitoring
In
060-FT-600
060-FI-600
Manual Loader
Out
019-SY-700
In
097-FT-800
Out
097-FY-800
Motor Control
Discrete Actuated
Valve Control
Discrete Electric
Valve (solenoid only)
Control
Discrete Valve
Monitoring
3-Way Discrete
Actuated Valve
Control*
Control Loop
019-SC-700
097-FIC-800
*Name the passive position first, then Active position for 3-Way Valve module descriptions. ZSA is the
passive position and ZSB is the active position.
A DST should be referenced only once by a control module (multiple references unnecessarily consume
licensing). Other required references to a DST should be done by external reference to the DST control
module.
3.6. Other Modules
A number of other types of modules are used in the Plant control system.
Interlock modules consolidate all input conditions that interlock control devices to the passive state. See
INTERLOCKS.
Equipment modules control more than one control module to perform an overall function. General Unit
Equipment Modules are used to perform simple functions within a Unit, such as 1) enable/disable module
alarms under certain conditions, and 2) open pump discharge valve every time a pump starts. These
equipment modules are named generically after the Unit. Complex equipment modules are named after the
specific function it performs. Examples of specific equipment modules are 1) charging a prescribed amount
of material to a tank or tank truck, and 2) treat wastewater by running the sequence fill, heat, strip, drain.
See EQUIPMENT MODULES.
Document #: CS17160
Revision Date: 02/21/2013
Page: 6 of 58
Effective Date: 04/29/2013
Phases are used in Batch Recipes. See BATCH MONITORING AND CONTROL.
Unit Failure modules monitor conditions associated with an equipment module or batch phase and capture
the first out cause of failure, displayed on its faceplate.
The following are example module names:
Module Type
Unit Interlock Conditions
Area Interlock Conditions
General Unit Equipment Module
Specific Function Equipment Module
Batch Phase
Unit Failure Module
Module Tag
082-UI-R2
A97_INT
046-EM-R2
072-MTO-XFR
RX_REACT
019-R2-FAIL
Description
082-R2 Unit Interlocks
Area 97 Interlocks
R2 Equipment Module
Area 72 MTO loading EM
Reactor Reaction
R2 Failure Module
Document #: CS17160
Revision Date: 02/21/2013
Page: 7 of 58
Effective Date: 04/29/2013
4.
Faceplate
ai_n_fp
ai_n_fp
ai_n_fp
tot_n_fp
tot_2_n_fp
pid_n_fp
pid_n_isel_fp
pid_n_fp
gap_n_fp
man_n_fp
Detail Display
ai_n_dt
ai_pseudo_n_dt
ai_calc_dt
tot_n_dt
tot_2_n_dt
pid_n_dt
pid_n_isel_dt
pid_n_dt
gap_n_dt
man_n_dt
Document #: CS17160
Revision Date: 02/21/2013
Page: 8 of 58
Effective Date: 04/29/2013
graphic dynamo) in the event of a HART failure. Without this option checked, a failed HART transmitter will
not display a FAIL alarm since HART limits the signal to about 3 mA.
4.2. Analog Input
Analog inputs access a single analog measurement value. This can be a standard 4-20mA-transmitter
signal, digital variable communicated from a HART or Foundation Fieldbus transmitter.
Analog input modules consist of either a standard AI or foundation Fieldbus AI function block.
Conditional alarming is enabled for all non-foundation Fieldbus AI function blocks.
The PV Bad alarm is active during an Input Failure/Bad PV or Simulate Active.
4.3. Pseudo/Calc Analog Input
Analog values not directly measured from an IO point (either externally referenced or calculated) are
displayed and alarmed via two classes, AI_PSEUDO and AI_CALC.
Both the AI_PSEUDO and AI_CALC classes use the standard Pseudo_AI Composite function block in
place of and analog input block. The AI_CALC class also uses a B_PV_CALC Composite to perform
calculations.
The PV Bad alarm is active during an Input Failure/Bad PV or Simulate Active.
4.4. Setpoint Totalizer
Totalizers allow integration of an analog value. The totalizer has outputs to indicate when a pre-trip setpoint
and final setpoint are reached. Totalizer control modules use the standard DeltaV INT function block with
the following added features.
Scaling Minimum, Maximum, and Engineer units may be provided for each input and the output.
The default totalizer uses only one (1) input, ENABLE_IN_2 on the INT function block is set to 0.
The default time unit for the input is Seconds, TIME_UNIT1 on the INT function block.
The INTEG_TYPE on the INT function block is set to 0 to SP demand reset and should not be
changed.
Mode Lock Mode lock hides the mode buttons on the totalizer faceplate.
Process Alarms A high and high-high limit are configured for totalizer process alarms.
Stack Totals The totalizer stores the previous three (3) totals. Totals are moved down then stack
each time the totalizer is reset.
Reset An operator may initiate a totalizer reset via the faceplate regardless of mode.
It is assumed that the inputs are referencing an AI configured in another module, thus no alarming for a
bad PV is done in the totalizer module.
The expression in condition block CND1 is used to freeze the totalized value. This can be used, for
example, to freeze the material charge amount between charges where the flow meter might not read
exactly zero when charging is not in operation.
A VAL1_DIVIDER parameter is available if the totalized value is in units larger than the input signal. For
instance, set VAL1_DIVIDER to 1000 to totalize in Mlb (thousand lb) if the PV units is lb/min.
Document #: CS17160
Revision Date: 02/21/2013
Page: 9 of 58
Effective Date: 04/29/2013
Document #: CS17160
Revision Date: 02/21/2013
Page: 10 of 58
Effective Date: 04/29/2013
Split Range control loops (CL_PID_SPLIT module class) are exactly the same with the addition of a
splitter (SPLTR) function block and another AO function block.
4.7. Gap DO Control Loop
The Gap control module utilizes a PID modules deviation limits to activate a discrete output. The discrete
output is often referenced to the EM_IN_D of a discrete control module. The PID algorithm is not utilized.
Mode Lock Mode lock hides the mode buttons on the PID faceplate.
Conditional alarms are enabled for all alarms on the PID function block.
SP Deviation The high SP Dev limit is used to turn a discrete output on and off. When the PV gets
above the higher end of the deviation limit, the discrete output is energized. When the PV gets below
the lower end of the deviation limit, the discrete output is de-energized.
When placed in Manual mode, ON and OFF buttons appear on the faceplate for manual control of the
discrete device.
Interlocks should not be configured in Gap DO Control Loops, but should be assigned instead to the
discrete device that the Gap DO Control Loop controls.
4.8. Manual Output Loader
The Manual output loader provides analog output channel processing and the ability to directly control the
position of the output. Manual output loaders use the standard MANLD function block wired to an Analog
Output Block with the following added features.
Interlock Up to four (4) separate conditions can comprise an interlock for the control loop. (More
conditions are available by using a different INTERLOCK composite) Each condition may be
individually bypassed.
An interlock position parameter is set to determine the output position when the interlock is active.
The MANLD OUT parameter is controlled by the AUTO_IN parameter by an operator through the
faceplate or the EM_IN parameter by an equipment module or the PHASE_IN parameter by a phase.
Default control options for the MANLD function block are the following and should not be changed:
Track Enabled.
Track in Manual.
The mode is created using the R_CAS parameter on the module as follows:
When R_CAS is 0, the mode is Auto
When R_CAS is 1, the mode is CAS
When R_CAS is 2, the mode is RCAS
Mode Lock Mode lock hides the mode buttons on the manual loader faceplate.
5.
Document #: CS17160
Revision Date: 02/21/2013
Page: 11 of 58
Effective Date: 04/29/2013
Faceplate
di_n_fp
dc_n_fp
dc_n_fp
dc_n_fp
dc_mtr_n_fp
dc_vfd_n_fp
dc_vfdf_n_fp
Detail Display
di_n_dt
dc_n_dt
dc_n_dt
dc_n_dt
dc_n_dt
dc_vfd_n_dt
dc_vfdf_n_dt
Document #: CS17160
Revision Date: 02/21/2013
Page: 12 of 58
Effective Date: 04/29/2013
3 Way valves require the configuration of parameters A, B, and C to define the path. Standard 3-way
valves use Active/Passive named sets. Custom named sets can also be configured with Plant
approval.
2 output motors include a composite that sets momentary start and stop signals based on the output of
the DC function block. The stop signal is latched on if the motor is interlocked to prevent the motor
being started in the field.
Motor control modules have additional buttons near the bottom of the faceplate to allow either Field (F)
or DCS (D) control of the module. DCS is the normal control mode. Field control can be selected if the
device is being started or stopped frequently from the field. With Field Control selected, the module
will not alarm when the device is started or stopped from the field. Note: this eliminates nuisance
alarms, but also prevents an alarm if the motor should fail.
6.
EQUIPMENT MODULES
All simple functions not performed in the class based modules for a Unit are performed in a
General Unit Equipment Module. This module is configured as a Function Block Diagram type of
Equipment Module. Since these modules contain a variety of programming, it is important to
segregate and clearly label with text each different function.
Complex Equipment Modules at the Kankakee facility consists of two command-driven equipment
modules with one embedded in the other. Use the Equipment module template EM_STANDARD
as the starting point for all equipment modules unless otherwise directed by the plant Process
Control Engineer.
6.1. Top Level
The top level equipment module handles the higher level states for the equipment module and always uses
the EM_STATES named set. This named set consists of the following states and usually performs the
following:
Activate Sets all discrete devices to CAS and control loops to RCAS or ROUT mode, sets devices to
a safe state, enables holds, and locks modes for discrete devices.
Deactivate Unlocks modes, disables hold, and disables any alarms that may have been enabled in a
run state.
Stop Sets devices to an end state. The equipment module goes to the Stop state when the running
mode (bottom level) completes.
Start Runs the selected run mode in the embedded (bottom level) equipment module.
Hold Sets Devices to a safe state, disables holds and unlocks modes. If an equipment module goes
to hold because a monitored device is held, all device holds must be reset before the equipment
module can be restarted.
Operating and tuning parameters in equipment modules are configured in the parameters window in the top
level equipment module. These parameters display on the equipment module detail faceplate: Operating
parameters can be changed with any operator login; Tuning parameter changes require an administrative
login. Each Operating parameter consists of three (3) configured parameters representing the Operating
parameters value, description, and scale. Each of these configured parameters must be created (indexing
the parameter numbers and copying the parameter types) to create additional Operating parameters. For
instance, if an equipment module has 1 operating parameter and a second one is desired, the following
parameters should be added in the parameter window: PARAM2 (floating point), PARAM2_DESC (string),
PARAM2_SCALE (scaling). Tuning parameters are configured the same as Operating parameters but are
named TN_PARAMX instead of PARAMX.
Document #: CS17160
Revision Date: 02/21/2013
Page: 13 of 58
Effective Date: 04/29/2013
Permissive parameters in equipment modules are also configured in the parameters window in the top level
equipment module and also display on the equipment module detail faceplate. Equipment module
Permissives are handled in the monitor embedded composite and reference parameters PERMX (where X
is the permissive number) which are external references to a condition in an interlock module. A
PERMX_DESC parameter is used to identify the permissive in the equipment module detail display.
The monitor embedded composite in the top level equipment module is a function block composite that
monitors for device failures and places the equipment module in Hold if a monitored device fails,
enables/disables global device holds* where a single command in the Activate state enables/disables Holds
for all devices, and regulates what states the equipment module is allowed to be switched to from other
states. * A device may have its Hold enabled in the Running mode because Hold monitoring for the device
is limited to only certain portions of the Running logic.
6.2. Bottom Level
The bottom level command driven equipment module displays in the top level as EM_MODES and defines
the running modes for the Equipment module. The modes are process functions the equipment module
performs. An equipment module may have only one mode which is either Running or Idle; but may have
multiple modes, e.g., 1) charge material 1 to reactor, 2) charge material 2 to reactor, etc. Multiple modes
are selectable from a drop-down box on the equipment module faceplate. The bottom level equipment
module also has an embedded monitor composite that is generally used for totalizer or any other additional
continuous monitoring logic needed.
7.
INTERLOCKS
7.1. Interlock Modules
Interlock modules consolidate all input conditions that interlock control devices to the passive state. Unit
Interlock modules consolidate input conditions from a Unit; Area Interlock modules consolidate input
conditions from modules not assigned to a Unit. Interlock modules have no faceplate displays. Interlock
descriptors are referenced by the control modules being interlocked so that input conditions tripping
interlocks are displayed on the interlocked devices detailed faceplate.
Interlock conditions in control modules are external references to condition function blocks located in an
interlock module. Both the OUT_D and the DESC parameters of each condition block are referenced.
Use the Unit module template INTERLOCKS as the starting point for all interlock modules.
7.2. Interlock Conditions
Interlock Modules contain a collection of condition function blocks, each with an expression that provides a
single trip to a devices interlocks, a descriptor so that the particular trip can be identified on the interlocked
devices detailed faceplate, and a time duration which provides an optional delay to any interlock condition.
The following guidelines should be used when configuring conditions inside Interlock modules:
1.
The name of the CND block should be changed to something describing the condition. For
example, if the condition has to do with a high level in Reactor 4, the CND block name should be
changed from CND1 to R4_HI_LVL.
2.
Enter a trip description in the DESC parameter. The maximum allowed characters is 40 for
interlock descriptors (standard faceplate configured space). Sentence format shall be used for all
interlock descriptors. Use abbreviations for temperature (temp), pressure (pres), high (hi), high
high (hihi), low (lo), and low low (lolo) if required to save space. Use phrases like hi temp, and lolo
pres to reference the modules alarm points; if a trip is at a process value different from an alarm
point, spell out the trip point, e.g., T9 pres > 30 psia.
Document #: CS17160
Revision Date: 02/21/2013
Page: 14 of 58
Effective Date: 04/29/2013
3.
Interlock conditions that are triggered by an analog alarm should reference the XX_ACT of the AI
or PID block associated with the module. This ensures that interlock conditions trip even if the
referenced alarm is disabled.
4.
If the expression is a comparison with a fixed value, create an Internal Read Parameter next to the
CND block and store the value in the parameter. Reference this parameter in the required CND
function block expression.
5.
Expose the TIME_DURATION parameter on any CND function block that contains interlock
conditions.
6.
Interlocks conditions that reference a value or alarm from a module that has a BAD_ACTIVE alarm
should also reference the modules BAD_ACTIVE parameter so that the interlock trips in the event
of a bad signal from the source module. Analog Input, Discrete Input, and PID Control modules
have BAD_ACTIVE alarms. Following is an example expression in an Interlock condition block:
//044-PIC-R3B/PID1/HI_ACT.CV OR //044-PIC-R3B/PID1/BAD_ACTIVE.CV.
Since Interlock and Permissive conditions in control modules are external reference type parameters, every
interlock parameter must be resolved (reference an external module) to eliminate integrity errors inside the
control module. Class based control modules with interlocks have fixed numbers of Interlocks (and
Permissives): 4, 8, 16, 32, 48, etc. Interlock and Permissive references in control modules that do not
reference actual interlock logic must reference a condition block with false as the condition expression and
a blank condition DESC parameter. Detail faceplates are configured to show nothing in places where the
referenced interlock condition DESC parameter is blank. A global false CND block with a blank DESC
parameter called CND0 has been configured in control module K3_INTERLOCK, located in AREA_A, for
this purpose. Any external reference parameter that must be resolved to a false value should be pointed to
this CND block. All Interlocks and Permissives in class based modules reference this CND block.
8.
Document #: CS17160
Revision Date: 02/21/2013
Page: 15 of 58
Effective Date: 04/29/2013
VFD Modules without analog feedback - MODE not in CAS, FAIL_ALM, Active SP and Interlocked, and
An active setpoint is passed to the device while it is in the passive state and there is an active
permissive condition.
When the control module enters a Hold state, the control module generates a critical alarm and the
equipment module and/or active phases on the corresponding unit go to their Hold state. The control
module Hold must be reset by an operator via the faceplate before the unit may be restarted.
8.2. Failure Monitoring
There are three places in the Kankakee DeltaV configuration that could be referred to as Fail Monitors. To
try to avoid confusion, the following definitions will be used in this document:
Unit Failure Module - A control module that is associated with a batch unit. An example would be 019R1-FAIL. These modules are simply a collection of condition blocks. Each condition block looks at the
HELD parameter of a different control module that is part of the unit. If a Hold Condition (defined in
above) is detected for any of the modules being monitored, the phases running on that unit will be put
to the Held state. When a recipe goes to Hold, the Unit Failure Module faceplate will indicate the first
device hold that became active.
Phase Failure Monitor - A composite block that is a part of each phase class. The composite contains a
calc block that references the Unit Failure Module. This calc block expression is what actually sets the
phase to Hold if the Unit Failure Module detects a Hold Condition.
EM Monitor - A composite block that is a part of each command driven equipment module. The EM
Monitor is responsible for monitoring control module Hold Conditions for equipment modules that are
not being commanded by a phase. If the EM Monitor detects a Hold Condition the EM is commanded to
the Held state.
8.3. Unit Phase Modules
Unit phase modules define active states (running, stopping, restarting, aborting, and holding) of the phases
of a recipe. Phase modules contain logic that governs the transitions between states of a phase. State
transition logic is configured using sequential function charts. The scope of phase modules is such that
operators can manually execute a series of phase modules to complete processing on a unit. Examples of
phase modules are Charging, Agitation, Heating, and Discharging.
Unit phase modules issue commands to discrete and analog control modules. All safety interlocks for
devices are handled outside of the Phase Logic Module.
8.3.1.
8.3.2.
Aborting Block
Aborting blocks are configured in an SFC. Abort places the phases equipment into a fail-safe
state. Once aborted, the phase must be reset to return to the initial idle state.
8.3.3.
Holding Block
Holding blocks are configured in an SFC. Upon completion of holding logic, the phase transitions
to the hold state. Once held, operators can abort, stop or restart the phase.
8.3.4.
Document #: CS17160
Revision Date: 02/21/2013
Page: 16 of 58
Effective Date: 04/29/2013
Running Block
Running blocks are configured in an SFC. SFC logic operates phase equipment. In running mode,
the phase completes running logic and continues to the complete state. Phases can be held or
stopped by failure conditions or operator intervention.
8.3.5.
Stopping Block
Stopping blocks are configured in an SFC. SFC logic brings the phase to a controlled stop. A reset
transitions phases to the idle state. Also, from the stopping state, phases can be manually placed
in aborting if required.
8.3.6.
Restarting Block
Restarting blocks are configured in an SFC. SFC logic restarts the phase after it has been held or
failed. Logic is designed such that restarting the phase returns the phase to its pre hold running
state and then completes running logic from that point forward.
9.
WORKSTATION CONFIGURATION
The following sections describe the philosophy used in configuration of workstations.
9.1. Workstation Names
Workstations on the DeltaV Control Network are named by the area, then function, then number. Examples
are provided below:
Workstation
Professional Plus
Professional
Operator
Application (Batch Executive)
Application (Continuous Historian)
Application (general)
Name
PROP-4096
021-PRO-1
021-OP-1
001-BE-1
001-CH-1
072-APP-1
Document #: CS17160
Revision Date: 02/21/2013
Page: 17 of 58
Effective Date: 04/29/2013
Security
The DeltaV User Manager application provides an interface to the five essential components of
security:
Locks
Prevent users from changing parameters and parameter fields assigned to the lock and
prevent users from performing certain functions. DeltaV Explorer is used to assign locks
to parameters, parameter fields and functions. It is helpful to think of a lock as something
that specifies the name of the key that grants access.
Keys
Provide permissions to individual users or whole groups of users. Each key is associated
with a lock. Keys are granted under the group and user properties dialogs. Users can be
granted any number of keys or none at all.
Groups Classify users together and grant keys to everyone in the group.
Users
DeltaV system and Windows users. Users may be assigned to one or more groups. The
DeltaV User Manager application also allows new Windows users to be created without
accessing the Windows User Manager application. When a new user is created, it is
specified whether the user is a Windows user, a DeltaV system user, or both.
Areas
DeltaV system users can be granted different sets of keys in each area. This feature can
be used to grant parameter write access to operators for control modules within the
operators' responsibility, yet withhold parameter write access to other similar modules
outside their responsibility.
Users are created and maintained on the Kankakee DeltaV domain (user privileges are based on
login and are independent of workstation). Refer to Construction Specification CS17180 Control
Systems Security Standards.
9.2.2.
Users
All user accounts are password protected. User profiles are created from the following Groups:
Operate
The Operator login can control all plant areas it is assigned to from any workstation
on the network. The Operator User is granted standard DeltaV Operator access
that includes the ability to open/close valves; stop/start motors; change loop
setpoints, mode, and output; and view/acknowledge area alarms.
Supervise
Configure
User accounts at the Kankakee facility are usually one of four types, Engineers, E&I Technicians,
Team Leaders, and Operators. All users can view the entire Kankakee system.
Operators login under an area account, e.g., A97OPER, with Operate privileges only to areas
under the operators responsibility.
Team Leaders login with an individual account with Supervise privileges only to areas under
the supervisors responsibility.
E&I Technicians login with an individual account with Supervise, downloading, and AMS write
privileges to all areas.
Engineers and integrators login with an individual or company account with Configure
privileges to all areas.
9.2.3.
Document #: CS17160
Revision Date: 02/21/2013
Page: 18 of 58
Effective Date: 04/29/2013
Additional Setup
New operator workstations should have the following settings:
Flexlock Uncheck Autorun DeltaV Operate; check Autoswitch Desktop
Display Properties Screen Resolution: 1280x1024; Color quality: Medium (16 bit)
Workspace/User Preferences General: Uncheck Full Screen in Run Mode; Environment
Protection: Check Disable Title Bar and Menu Bar
Dual monitors Log on to desktop as administrator, Start/Programs/ATI Hydravision /Hydravision
Properties:
Dialog control - check Enable dialog repositioning, select Show at cursor
Window control - check Hydravision Max/Restore button, select Max to full desktop
General check Application position memory, uncheck Automatically align monitors
10.
Document #: CS17160
Revision Date: 02/21/2013
Page: 19 of 58
Effective Date: 04/29/2013
This Configuration Standard references colors by name (First Column) and the following table crossreferences Color Name with DeltaV Color Name (visible within DeltaV Color Palette).
COLOR
Black
Cyan
Gray
Green
Dim Green
Light Green
Teal
Dark Teal
Red
Dim Red
White
Blue
Purple
Yellow
Orange
In addition to the colors shown above, all process graphic displays have the following default parameters.
Other elements that appear on process graphic displays are described in subsequent sections.
PARAMETER
Background Color
PV & PV Units
SP & SP Units
%OUTPUT & OUTPUT Units
Default Value
Dark Teal
Yellow
White
Cyan
A white square appears next to the device with first letter of current
mode; Shown only when mode is not normal
A red circle with a black i appears next to the device when an
interlock is active
An orange circle with a black B appears next to the device when an
interlock is bypassed
A red circle with a black H appears next to the device when a hold
condition is active
A square with an F appears next to the device when the module is
failed (color determined by fail alarm priority)
Analog PVs will take on the Alarm Priorities Colors as well as the
Alarm Acknowledgement Status (act identical to Operator Alarm
Banner)
Discrete Function (e.g., High Level) Text will be displayed when the
Discrete condition is Active. The Text has the PV color when the
discrete condition is Inactive.
Tool Tips will be enabled and display a description of the
device/measurement.
Mode
Interlock Status
Interlock Bypass Status
Hold Status
Failure Status
Analog Alarm Indication
Discrete Indication
Tool Tips
10.1.1. Overview Graphic
Every major Area should have an Overview graphic which sketches the entire process, displays no
data links, and contains graphics links to all process graphic displays.
10.1.2. Title Block
Each process graphic display has a title block in white text located in the Top center of the display.
Every title should begin with Area XX, e.g., Area 82 Hot Oil System. This assists in identification
of screen printouts and provides easy identification of Graphic displays.
Document #: CS17160
Revision Date: 02/21/2013
Page: 20 of 58
Effective Date: 04/29/2013
Document #: CS17160
Revision Date: 02/21/2013
Page: 21 of 58
Effective Date: 04/29/2013
Document #: CS17160
Revision Date: 02/21/2013
PARAMETER
Pump Module Name Color
Pump Running
Pump Stopped
Pump Failed
Pump Actual Mode
Pump Module Interlock Indication
Pump Module Interlock Bypass
Indication
Pump Batch Hold Status
Page: 22 of 58
Effective Date: 04/29/2013
Default Value
Black
Green with rotating center
Red with static center
A square with an F appears next to the pump
(color based on Fail Alarm priority) when failed
A white square appears next to the pump with
first letter of current mode; shown only when
mode is incorrect for batch operation
A red circle with a black i appears next to the
pump when active
An orange circle with a black B appears next
to the pump when bypassed
A red circle with a black H appears on the
pump when held
Other Motors
Blowers are identical to pumps, but are shown without a base. Motors for airlocks and agitators
are also shown below.
Document #: CS17160
Revision Date: 02/21/2013
Page: 23 of 58
Effective Date: 04/29/2013
10.1.6. Valves
Discrete Valves
Discrete valves are displayed as shown in the screen shot below. The rectangular actuator is
dynamically colored to correspond to setpoint (SP); and the rectangular actuator will become
hollow when the valve is energized. The valve body changes color corresponding to the valves
actual position (PV).
Valves transitioning between states will show a gray body until a limit switch is reached (typical of
very large valves). Valves that are configured without confirm switch feed back will always show a
gray body and only the actuator will change colors.
Module Name, Mode, Interlock Status, Interlock Bypass Status, and Batch Hold Status also
appear near each valve.
Discrete indication only valves are similar to DC valves, but only the Hold and fail satellites are
present.
PARAMETER
Valve Module Name Color
Valve Open Color
Valve Closed Color
Valve Failed
Valve Actual Mode
Valve Module Interlock Status
Valve Module Interlock Bypass
Status
Valve Module Batch Hold Status
Default Value
Black
Green
Red
A square with an F appears next to the valve
when failed
A white square appears next to the valve with
first letter of current mode; shown only when
mode is incorrect for batch operation
A red circle with a black i appears next to the
valve when interlocked
An orange circle with a black B appears next
to the valve when bypassed
A red circle with a black H appears on the
valve when held.
Control Valves
Control valves are displayed as shown in the screen shot below. The actuator is dynamically
colored to correspond to output. Valve output is always displayed as % open regardless of fail
position or drive signal.
Document #: CS17160
Revision Date: 02/21/2013
Page: 24 of 58
Effective Date: 04/29/2013
If valve output is greater than 2%, the valve is considered open and thus the actuator is green.
Valve Output, Module Name, Mode, Interlock Status, Interlock Bypass Status, and Batch Hold
Status appear near each valve.
PARAMETER
Valve Module Name Color
Valve Open Declaration
Valve Open Color
Valve Closed Color
Valve Output Value Color
Valve Actual Mode
Valve Module Interlock Status
Valve Module Interlock Bypass
Status
Valve Module Batch Hold Status
Default Value
Black
Output > 2%
Green
Red
Cyan
A white square appears next to the valve with
first letter of current mode; shown only when
mode is incorrect for batch sequence
A red circle with a black i appears next to the
valve when interlocked
An orange circle with a black B appears next
to the valve when bypassed
A red circle with a black H appears on the
valve when held.
Also, PVs will take on the configured Alarm Priority and Alarm Acknowledgement status colors
when in alarm.
PARAMETER
Control Module Name Color
PV & Units Color
SP & Units Color
Instrument Failed
Module Batch Hold Status
Default Value
Black
Yellow
White
A red square with a white F appears next to
the control loop data box when failed
A red circle with a black H appears next to
the control loop data box when held
Document #: CS17160
Revision Date: 02/21/2013
Page: 25 of 58
Effective Date: 04/29/2013
PARAMETER
Indicator Module Name Color
PV & Units Color
Instrument Failed
Module Batch Hold Status
Default Value
Black
Yellow
A red square with a white F appears next to
the indicator data box when failed
A red circle with a black H appears next to
the indicator data box when held
PARAMETER
Totalizer Module Name Color
Total Color
SP Color
Module Batch Hold Status
Default Value
Black
Cyan
White
A red circle with a black H appears next to
the totalizer data box when held
Document #: CS17160
Revision Date: 02/21/2013
Page: 26 of 58
Effective Date: 04/29/2013
PARAMETER
Active Alarm Color
Passive Color
Module Batch Hold Status
Instrument Failed
Default Value
Matches Alarm Priority (Critical Shown)
Yellow
A red circle with a black H appears next to
the indicator data box when held
A red square with a white F appears next to
the indicator data box when failed
PARAMETER
Activated Color
Running Color
Stopping Color
Deactivated Color
Default Value
White
Green
Red
Gray
Document #: CS17160
Revision Date: 02/21/2013
Page: 27 of 58
Effective Date: 04/29/2013
Multiple run mode equipment modules show the current state of the equipment module (i.e.
Activated, Running, etc.) and which run mode is selected. Equipment modules can also have
additional messaging text on displays as needed.
PARAMETER
EM Module Name Color
PV Color
SP Color
Run State
Default Value
Black
Yellow
White
Cyan
PARAMETER
Unit Name Color
Phase Name Idle Color
Phase Message Waiting Color
Phase Operator Action Required
Color
Phase Running Color
Phase Stopped Color
Phase Held Color
Phase Restarting Color
Phase Aborted Color
Default Value
Cyan
Gray
Yellow
Yellow, Blink to White
Green
Blue
Red
Dim Green
Purple
Document #: CS17160
Revision Date: 02/21/2013
Page: 28 of 58
Effective Date: 04/29/2013
If a phase requires an operator prompt to be answered, the prompt button on the right will flash.
Clicking the prompt button will hide the message line and show the prompt box below in white.
Doubling clicking the prompt box will bring up the DeltaV standard batch acknowledge box where
the operator can choose a response.
Document #: CS17160
Revision Date: 02/21/2013
Page: 29 of 58
Effective Date: 04/29/2013
Document #: CS17160
Revision Date: 02/21/2013
Page: 30 of 58
Effective Date: 04/29/2013
A
H
C
D
B
G
I
The interlock and bypass status of the control module (H) are displayed at the top of the faceplate.
A standard button bar along the bottom of the DC faceplate (I) allows for (buttons described from
left to right) opening the control modules detail display (see below), opening the primary control
display for the control module, real time trending, launching the Process History View application
for historical trend viewing, launching the Control Studio application, and module alarm
acknowledging. A blinking blue line below the detail display button on the left indicates a module
error and usually is caused by a signal wire losing connection to the Delta V IO card.
The DC detail display consists of 6 tabs. Clicking on a tab heading changes the information
displayed on the detail display to the selected tabs associated information.
Document #: CS17160
Revision Date: 02/21/2013
Device State
Diagnostics
Page: 31 of 58
Effective Date: 04/29/2013
Alarm
Options
Document #: CS17160
Revision Date: 02/21/2013
Interlocks
Page: 32 of 58
Effective Date: 04/29/2013
Permissives
The interlock and permissive tabs list the devices interlock and permissive conditions as well as
the status of these conditions (inactive or active; bypassed). Inactive conditions display in light
grey and active conditions display in black. Bypassed conditions will display a check symbol in the
white box to the right of the conditions description. When a condition trips the device, a red arrow
will show to the left of the condition to indicate a first out and a reset button will become visible.
The reset button and arrow will stay visible and will not move until the first out is reset by clicking
the reset button.
10.2.2. Discrete Input Faceplate
The DI faceplate (shown below for a general alarm) contains the control module name and
description (A) as well as the unit name that the control module is assigned to (B).
The input from the field (C) is shown in standard PV color. The discrete device alarm (D) is
triggered when the discrete alarm becomes active and will change color depending on the alarm
priority. The alarm circle will be grayed out if disabled and black if enabled and not in alarm.
The module hold alarm is displayed (E) along with a button to reset the alarm after the condition
that has caused the hold clears.
The alarms window (F) shows all active alarms associated with the module. Alarms are arranged
from top to bottom by highest priority. A check box indicates the alarm has been acknowledged.
Document #: CS17160
Revision Date: 02/21/2013
Page: 33 of 58
Effective Date: 04/29/2013
A
C
F
B
E
G
A standard button bar along the bottom of the DI faceplate (G) allows for (buttons described from
left to right) opening the control modules detail display (see below), opening the primary control
display for the control module, real time trending, launching the Process History View application
for historical trend viewing, launching the Control Studio application, and module alarm
acknowledging. A blinking blue line below the detail display button on the left indicates a module
error and usually is caused by a signal wire losing connection to the Delta V IO card.
The DI detail display consists of 4 tabs. Clicking on a tab heading changes the information
displayed on the detail display to the selected tabs associated information.
Alarms
Device State
Document #: CS17160
Revision Date: 02/21/2013
Diagnostics
Page: 34 of 58
Effective Date: 04/29/2013
Empty
Document #: CS17160
Revision Date: 02/21/2013
Page: 35 of 58
Effective Date: 04/29/2013
A
J
C
D
G
E
H
F
The interlock and bypass status of the control module (J) are displayed at the top of the faceplate.
A standard button bar along the bottom of the PID faceplate (L) allows for (buttons described from
left to right) opening the control modules detail display (see below), opening the primary control
display for the control module, real time trending, launching the Process History View application
for historical trend viewing, launching the Control Studio application, and module alarm
acknowledging. A blinking blue line below the detail display button on the left (seen above)
indicates a module error and usually is caused by a signal wire losing connection to the Delta V IO
card.
The PID detail display consists of 6 tabs. Clicking on a tab heading changes the information
displayed on the detail display to the selected tabs associated information.
Document #: CS17160
Revision Date: 02/21/2013
Alarms
Options
Page: 36 of 58
Effective Date: 04/29/2013
Device State
Diagnostics
Document #: CS17160
Revision Date: 02/21/2013
Tuning
Page: 37 of 58
Effective Date: 04/29/2013
Tracking
The tuning tab lists all the tuning parameters and also shows a button with Duncan holding a
tuning fork which launches DeltaV Insight (Auto tuner).
The tracking tab lists the devices tracking conditions as well as the status of these conditions
(inactive or active; bypassed). Inactive conditions show up in light grey and active conditions are
shown in black. Bypassed conditions will display a check symbol in the white box to the right of the
conditions description. When a condition becomes active, the loop output will go to its track
position, a red arrow will show to the left of the condition to indicate a first out, and a reset button
will become visible. The reset button and arrow will stay visible and will not move until the first out
is reset by clicking the reset button. The tracking position is shown above the interlock conditions.
10.2.4. Analog Input Faceplate
The AI faceplate (shown below) contains the control module name and description (A) as well as
the unit name that the control module is assigned to (B).
The PV is shown both numerically and graphically in the form of a bar (C) in standard PV color.
Standard analog alarms (LoLo, Lo, Hi, HiHi) (D) are shown at the bottom of the faceplate. Alarm
limits are visible by holding the cursor over the alarm lights on the faceplate. In the faceplate
below, the Hi alarm is active. Suppressed alarms are depicted by the prohibited symbol on the
alarm light. Disabled alarms, like the LoLo alarm, are shown as grayed out.
The module hold alarm is displayed (E) along with a button to reset the alarm after the condition
that has caused the hold clears.
The alarms window (G) shows all active alarms associated with the module. Alarms are arranged
from top to bottom by highest priority. A check box indicates the alarm has been acknowledged.
Document #: CS17160
Revision Date: 02/21/2013
Page: 38 of 58
Effective Date: 04/29/2013
G
D
B
E
F
A standard button bar along the bottom of the AI faceplate (F) allows for (buttons described from
left to right) opening the control modules detail display (see below), opening the primary control
display for the control module, real time trending, launching the Process History View application
for historical trend viewing, launching the Control Studio application, and module alarm
acknowledging. A blinking blue line below the detail display button on the left (seen above)
indicates a module error and usually is caused by a signal wire losing connection to the Delta V IO
card.
The AI detail display consists of 4 tabs. Clicking on a tab heading changes the information
displayed on the detail display to the selected tabs associated information.
Document #: CS17160
Revision Date: 02/21/2013
Page: 39 of 58
Effective Date: 04/29/2013
Device State
Alarms
Diagnostics
Options
Document #: CS17160
Revision Date: 02/21/2013
Page: 40 of 58
Effective Date: 04/29/2013
A
F
C
E
B
G
The alarms window (E) shows all active alarms associated with the module. Alarms are arranged
from top to bottom by highest priority. A check box indicates the alarm has been acknowledged.
The interlock and bypass status of the control module (F) are displayed at the top of the faceplate.
A standard button bar along the bottom of the AI faceplate (G) allows for (buttons described from
left to right) opening the control modules detail display (see below), opening the primary control
display for the control module, real time trending, launching the Process History View application
for historical trend viewing, launching the Control Studio application, and module alarm
acknowledging. A blinking blue line below the detail display button on the left indicates a module
error and usually is caused by a signal wire losing connection to the Delta V IO card.
The Manual Loader detail display consists of 4 tabs. Clicking on a tab heading changes the
information displayed on the detail display to the selected tabs associated information.
Document #: CS17160
Revision Date: 02/21/2013
Device State
Diagnostics
Page: 41 of 58
Effective Date: 04/29/2013
Options
Tracking
Document #: CS17160
Revision Date: 02/21/2013
Page: 42 of 58
Effective Date: 04/29/2013
The tracking tab lists the devices tracking conditions as well as the status of these conditions
(inactive or active; bypassed). Inactive conditions show up in light grey and active conditions are
shown in black. Bypassed conditions will display a check symbol in the white box to the right of the
conditions description. When a condition becomes active, the loop output will go to its track
position, a red arrow will show to the left of the condition to indicate a first out, and a reset button
will become visible. The reset button and arrow will stay visible and will not move until the first out
is reset by clicking the reset button. The tracking position is shown above the interlock conditions.
10.2.6. Totalizer Faceplate
The Totalizer faceplate (shown below) contains the control module name and description (A) as
well as the unit name that the control module is assigned to (B).
The SP is shown both numerically and graphically in the form of an arrow (C) in standard SP color.
The current totalizer output is depicted numerically and graphically (D) in the form of bar in
standard output color.
The actual mode (E) is displayed next to buttons for selecting enabled modes.
Two standard analog alarms (Hi, HiHi) are depicted (F) just above the modes. Alarm limits are
visible by holding the cursor over the alarm lights on the faceplate.
Batch hold alarms are displayed (G) along with a button to reset the alarm after the condition that
has caused the hold clears.
H
E
B
G
I
Document #: CS17160
Revision Date: 02/21/2013
Page: 43 of 58
Effective Date: 04/29/2013
The alarms window (H) shows all active alarms associated with the module. Alarms are arranged
from top to bottom by highest priority. A check box indicates the alarm has been acknowledged.
A standard button bar along the bottom of the Totalizer faceplate (I) allows for (buttons described
from left to right) opening the control modules detail display (see below), opening the primary
control display for the control module, real time trending, launching the Process History View
application for historical trend viewing, launching the Control Studio application, and module alarm
acknowledging. A blinking blue line below the detail display button on the left indicates a module
error and usually is caused by a signal wire losing connection to the Delta V IO card. Totalizers
typically have no DSTs, so a blinking blue line is likely caused by a configuration error.
The Totalizer detail display consists of 4 tabs. Clicking on a tab heading changes the information
displayed on the detail display to the selected tabs associated information.
Alarms
Device State
Document #: CS17160
Revision Date: 02/21/2013
Diagnostics
Page: 44 of 58
Effective Date: 04/29/2013
Empty
Document #: CS17160
Revision Date: 02/21/2013
Page: 45 of 58
Effective Date: 04/29/2013
F
G
Equipment module parameters, setpoints, or alarm limits can be accessed through the details
button (G).
The detail display consists of 3 tabs. Clicking on a tab heading changes the information displayed
on the detail display to the selected tabs associated information.
Document #: CS17160
Revision Date: 02/21/2013
Operator Parameters
Permissives
Page: 46 of 58
Effective Date: 04/29/2013
Document #: CS17160
Revision Date: 02/21/2013
Page: 47 of 58
Effective Date: 04/29/2013
Tuning Parameters
Document #: CS17160
Revision Date: 02/21/2013
Page: 48 of 58
Effective Date: 04/29/2013
A Unit failures display is accessible by clicking the parameters button (D). The Unit failures
display lists all of the conditions that can cause the unit to go into a failure state and cause the
batch to transition to the Held state.
Document #: CS17160
Revision Date: 02/21/2013
Page: 49 of 58
Effective Date: 04/29/2013
A
B
C
D
Document #: CS17160
Revision Date: 02/21/2013
Page: 50 of 58
Effective Date: 04/29/2013
11.
Alarm Management
Alarms are provided to warn the operator of an abnormal event that might require corrective
action, and to record those events for future analysis. An important consideration for alarm
management is the number of alarms configured to report to an operator. If too many alarms are
configured or if alarms are configured to remain active during normal operations, alarm displays
will always be full. The operator will then have difficulty noticing new alarms. On the other hand, it
is important to alarm (and sometimes pre-alarm) all events that require corrective action.
An effective alarm strategy is to automatically enable and disable certain alarms based on certain
conditions. For instance, enable flow alarms when charging is in process and disable flow alarms
when charging is complete. Alarm trip points can also be automatically adjusted. This is often
done during sequences controlled by an equipment module, or in batch phases. Another
application is to automatically disable all module alarms associated with an entire unit of that unit
is not running. Care should be exercised when configuring alarm strategies.
Document #: CS17160
Revision Date: 02/21/2013
Page: 51 of 58
Effective Date: 04/29/2013
Level
Value
Alarm
Priority
Name
Auto
Acknowledged
Auto Ack
Inactive
Horn
Enabled
Horn
Sound
15
11
7
3
CRITICAL
WARNING
ADVISORY
LOG
No
No
Yes
Yes
No
No
No
No
Yes
Yes
No
No
Buzz.wav
Alert_tone.wav
Beep.wav
None
Document #: CS17160
Revision Date: 02/21/2013
Page: 52 of 58
Effective Date: 04/29/2013
Up to eight additional priorities may be defined using DeltaV Explorer. Alarm priority names may be
modified to better describe the alarm prioritizing system. The Kankakee system uses the defaults listed
above. Priority levels not explicitly configured are given the same properties as the next higher configured
priority level.
Alarm priority is distinguished by color: in the Kankakee system, active Critical alarms show red, active
Warning alarms show yellow, and active Advisory alarms show purple.
Following is a list of default alarm priorities found in class based modules. These can be changed in
module instances.
PARAMETER
Analog HiHi Alarm
Analog High Alarm
Analog Low Alarm
Analog LoLo Alarm
SP Deviation HiHi Alarm
SP Deviation High Alarm
Analog PV Bad Alarm
Discrete Control (DC) fail alarm
Discrete Input
ENABLED
False
False
False
False
False
False
True
True
True
PRIORITY
CRITICAL
WARNING
WARNING
CRITICAL
CRITICAL
WARNING
CRITICAL
CRITICAL
CRITICAL
12.
Document #: CS17160
Revision Date: 02/21/2013
Page: 53 of 58
Effective Date: 04/29/2013
Module Type
Variable Type
Collection Rate
Compression
Deviation
Analog Monitoring
Flow
2 Seconds
0.5%
Level
5 Seconds
0.5%
Pressure
2 Seconds
0.5%
Temperature
5 Seconds
1%
Control Loop
PV
SP
Output
1%
1%
The Compression Deviation is configured in engineering units (EU) and not in % of span and must be
calculated for individual ranges.
12.2. Historical Data Archiving
Historical data sets on 001-CH-1 automatically archive when the data sets become full. About six (6)
months data is typically available to workstations at all times. In order to view data older than this, archived
data must be converted to active data. Contact the Process Control Engineer to have this done if required.
12.3. Historical Data Display
Historical data is displayed on workstations using the Process History View application. Each workstation
must be connected to a valid data source in order to view trends and event data. This is done in the
Process History View application: File\Set Default Data Servers. Set the server to 001-CH-1 and check the
box Save as my Application Startup Data Server on both Continuous Historian and Event Chronicle tabs.
These settings should not be lost even during a reboot, but in practice must be reset periodically.
Charts are configured to display continuous data, event data, or both. Most control modules have a
standard history trend chart that can be accessed by clicking the process history button located on the
bottom of the modules faceplate. Custom charts can also be configured that combine up to eight (8) points
located in different control modules.
Custom charts are created in the Process History View application and chart files should be saved in
DVData\Charts\Areaxx folder, where xx is the Area associated with the chart. Name the file after the chart
design so that the name is easily recognized when selecting it from a list. Most custom charts are
configured to display continuous data only (no event data). Custom charts are saved, uploaded to the
Professional Plus server, and downloaded just like graphics are in order to save them to other workstations.
13.
Document #: CS17160
Revision Date: 02/21/2013
Page: 54 of 58
Effective Date: 04/29/2013
AMS
AMS (Asset Management System) is an application that connects to all Fieldbus and HART
devices to view and configure device parameters available to any HART communicator such as a
Rosemount 375 or 475.
All Fieldbus devices automatically connect to AMS. All HART devices can connect to AMS but
only if the DeltaV IO card channel is configured as a HART Analog Input Channel. Even if HART
signals are not required for process control purposes, every HART device should have its channel
configured as a HART Analog Input Channel so that the device can be viewed and configured with
AMS. Each HART device should also be Auto-sensed at the channel level.
Fieldbus and HART devices have device definition files in the DeltaV library. The file revision
matching a Fieldbus device must be in the DeltaV library in order to commission a Fieldbus
device, let alone allow it to connect to AMS. The file revision matching a HART device need not
be in the DeltaV library in order to utilize HART values for process control purposes or to have the
HART device connect to AMS. If the HART definition file (revision) is not available in the DeltaV
library for a particular device, a warning displays when Auto-sensing the HART channel indicating
that the Auto-sensed device revision information was not found in the library. In such cases,
change the HART device manufacturer property from <none> to Conventional and choose any
device type and revision in order to prevent a runtime mismatch alert.
14.
Document #: CS17160
Revision Date: 02/21/2013
Page: 55 of 58
Effective Date: 04/29/2013
Glossary
Actual Mode
Alarm
Algorithm
Analog Input (AI)
Analog Output (AO)
Areas
Automatic Mode
(AUTO)
Books Online
Cascade Mode (CAS)
Composite
Control module
Controller
Database
Decommission
Debug
DeltaV AMS
DeltaV Operate
DeltaV Workstation
Device Signal Tag
(DST)
Device Tag
Discrete Input (DI)
Discrete Output (DO)
Download
Dynamo
Engineering Units (EU)
Equipment Module
Event
Function Block
Function Block
Diagram (FBD)
History - Continuous
History - Events
HMI
Hub
Iman Mode (IMAN)
Input/Output (I/O)
I/O Card
I/O Carrier
Library
Loop
Manual Mode (MAN)
Mode
Document #: CS17160
Revision Date: 02/21/2013
Page: 56 of 58
Effective Date: 04/29/2013
modified. DeltaV Explorer is especially useful for copying and moving modules to new
nodes using its drag-and-drop capability.
An application that runs on all DeltaV workstations that provides a graphical interlace to
the process.
A personal computer running the Windows operating system and DeltaV software
A Device Signal Tag consists of a Device Tag and a specific signal from that field device.
Device Tags represent the instruments, valves, and other field devices in your DeltaV
System.
An input which has only two possible states ON or OFF.
An output which has only two possible states ON or OFF.
The transfer of configuration data from the engineering workstation to the controllers.
Graphic objects stored in a library that are used to create pictures in the DeltaV Operate
application. Many dynamos are available that represent modules, devices, or
characteristics of your system.
Units associated with an analog signal that indicates how the process variable is
measured. A setpoint has the same engineering units as its process variable. Examples
are lb/min and psig.
A module that provides supervisory control for a collection of control modules.
A noteworthy occurrence in your process or system. The DeltaV system should be
configured to record and react to an event.
A logical processing unit of software that defines the behavior of an algorithm for a
particular module.
A diagram that contains multiple function blocks.
A continuous record of analog and discrete device values. Continuous history is
displayed on trend charts.
A chronological record of events, including the settings and changes made to a module.
This record of events can be referenced to gain information about a particular run or lot
of the product, or to show that the process complied with quality guidelines or
government regulations.
Human-machine interface, usually a workstation monitor.
A device in a network that consolidates control network connections and routes
communications. All communications devices on a hub-based network connect to one or
more hubs.
Is never a permitted target mode. The original definition was Initialization Manipulation,
which means the block tracks downstream operation (typically another block that has an
open cascade).
Signal reception and transmission or signal interfacing. Input, for a process control
device, involves accepting and processing signals from field devices. Output, for a
process control device, involves converting commands into electrical signals to field
devices.
An I/O card is the hardware device that interfaces field signals (wire connections) to
control logic in DeltaV controllers.
The assembly that provides power and communication connections for the DeltaV I/O
Interface Modules and termination blocks.
A repository for objects that are intended to be reused. The library in the DeltaV system
contains modules, function blocks, composites, and items that the user creates for reuse.
A control module that provides continuous PID control. Typically, this achieved by
comparing the process variable (PV) to the setpoint (SP) and using the difference to
calculate the Output. A Loop tries to maintain the PV at the desired SP.
Can be a permitted target mode. Operator or logic external to the function block
determines output.
A changeable attribute of a DeltaV module that determines either the modules
functionality, and/or limits operator access to certain parameters. The mode of most
control modules determines who writes to the modules setpoint.
Module
Node
Operator
Out of Service Mode
(OOS)
Parameter
Process
Process Cell
Process Variable (PV)
Record
Sequential Function
Chart (SFC)
Setpoint (SP)
Step
Target Mode
Unit Module
Document #: CS17160
Revision Date: 02/21/2013
Page: 57 of 58
Effective Date: 04/29/2013
Document #: CS17160
Revision Date: 02/21/2013
Page: 58 of 58
Effective Date: 04/29/2013
Revision History
Revision
Date
Page
07/19/10
All
02/21/13
7, 8,
10, 17
Description
Initiator
Original
J. Shute
J. Shute