Display

Engineering and Construction Specifications
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.
GENERAL GUIDELINES AND NAMING CONVENTIONS ............................................................................................ 3

3.1.
3.2.
3.3.
3.4.
3.5.
3.6.
3.7.
3.8.
4.
ANALOG MONITORING AND CONTROL CLASSES.................................................................................................... 7

4.1.
4.2.
4.3.
4.4.
4.5.
4.6.
4.7.
4.8.
5.
TOP LEVEL ..................................................................................................................................................................... 12

BOTTOM LEVEL .............................................................................................................................................................. 13
INTERLOCKS...................................................................................................................................................................... 13
7.1.
7.2.
8.
DISCRETE INPUT ............................................................................................................................................................ 11

DISCRETE CONTROL ...................................................................................................................................................... 11
EQUIPMENT MODULES................................................................................................................................................... 12
6.1.
6.2.
7.
HART SIGNAL CONFIGURATION ...................................................................................................................................... 7

ANALOG INPUT ................................................................................................................................................................. 8
PSEUDO/CALC ANALOG INPUT......................................................................................................................................... 8
SETPOINT TOTALIZER ...................................................................................................................................................... 8
TIMED TOTALIZER ............................................................................................................................................................ 9
PID CONTROL LOOP........................................................................................................................................................ 9
GAP DO CONTROL LOOP .............................................................................................................................................. 10
MANUAL OUTPUT LOADER ............................................................................................................................................. 10
DISCRETE MONITORING AND CONTROL CLASSES............................................................................................... 11

5.1.
5.2.
6.
CONTROLLER NAME ......................................................................................................................................................... 3

PLANT AREAS .................................................................................................................................................................. 3
PROCESS CELLS .............................................................................................................................................................. 3
UNITS ............................................................................................................................................................................... 4
CONTROL MODULES ........................................................................................................................................................ 4
OTHER MODULES ............................................................................................................................................................ 5
NAMED SETS ................................................................................................................................................................... 6
MODULE DEFAULTS ......................................................................................................................................................... 7
INTERLOCK MODULES .................................................................................................................................................... 13

INTERLOCK CONDITIONS ................................................................................................................................................ 13
BATCH MONITORING AND CONTROL......................................................................................................................... 14

8.1.
HOLD MONITORING ........................................................................................................................................................ 14
8.2.
FAILURE MONITORING .................................................................................................................................................... 15
8.3.
UNIT PHASE MODULES .................................................................................................................................................. 15
8.3.1.
Failure Monitor Block ........................................................................................................................................ 15
8.3.2.
Aborting Block .................................................................................................................................................... 15
8.3.3.
Holding Block ..................................................................................................................................................... 15
8.3.4.
Running Block .................................................................................................................................................... 16
8.3.5.
Stopping Block ................................................................................................................................................... 16
8.3.6.
Restarting Block................................................................................................................................................. 16
8.4.
PROCESS UNIT .............................................................................................................................................................. 16
8.5.
BATCH HISTORIAN ......................................................................................................................................................... 16
9.
WORKSTATION CONFIGURATION ............................................................................................................................... 16

9.1.
9.2.
W ORKSTATION NAMES .................................................................................................................................................. 16

W ORKSTATION CONFIGURATION.................................................................................................................................... 17

Revision: 1
9.2.1.
9.2.2.
9.2.3.
10.
Document #: CS17160
Page: 2 of 58
Security ............................................................................................................................................................... 17
Users ................................................................................................................................................................... 17
Additional Setup................................................................................................................................................. 18
OPERATOR HMI: GRAPHICAL DISPLAYS.............................................................................................................. 18
10.1. PROCESS GRAPHIC DISPLAYS ....................................................................................................................................... 18

10.1.1. Overview Graphic .............................................................................................................................................. 19
10.1.2. Title Block ........................................................................................................................................................... 19
10.1.3. Tanks and Vessels ............................................................................................................................................ 20
10.1.4. Pipes and Control Lines ................................................................................................................................... 21
10.1.5. Motor Controlled Devices ................................................................................................................................. 21
10.1.6. Valves.................................................................................................................................................................. 23
10.1.7. Control Loops ..................................................................................................................................................... 24
10.1.8. Analog Indication Points ................................................................................................................................... 25
10.1.9. Totalizer Points .................................................................................................................................................. 25
10.1.10.
Discrete Indication Points ............................................................................................................................ 26
10.1.11.
Equipment Modules Single Run Mode ................................................................................................... 26
10.1.12.
Equipment Modules Multiple Run Modes ............................................................................................... 27
10.1.13.
Unit Phase Displays...................................................................................................................................... 27
10.1.14.
Prompt Phase Display .................................................................................................................................. 28
10.2. FACEPLATES AND DETAIL DISPLAYS .............................................................................................................................. 29
10.2.1. Discrete Control Faceplate............................................................................................................................... 29
10.2.2. Discrete Input Faceplate................................................................................................................................... 32
10.2.3. Analog Control (PID) Faceplate ...................................................................................................................... 34
10.2.4. Analog Input Faceplate..................................................................................................................................... 37
10.2.5. Manual Loader Faceplate................................................................................................................................. 40
10.2.6. Totalizer Faceplate ............................................................................................................................................ 42
10.2.7. Equipment Module Faceplate .......................................................................................................................... 44
10.2.8. Unit Alarms Faceplate....................................................................................................................................... 47
10.2.9. Batch Unit Faceplate......................................................................................................................................... 48
10.2.10.
Phase Faceplate ........................................................................................................................................... 49
10.3. USERSETTINGS/LAYOUT FILES ...................................................................................................................................... 50
11.
ALARM MANAGEMENT............................................................................................................................................... 50
11.1.
11.2.
11.3.
12.
ALARM REPORTING ........................................................................................................................................................ 51

ALARM PRIORITIES ......................................................................................................................................................... 51
ALARM TYPES ................................................................................................................................................................ 52
TRENDING AND DATA ARCHIVING.......................................................................................................................... 52
12.1.
12.2.
12.3.
HISTORICAL DATA COLLECTION ..................................................................................................................................... 52

HISTORICAL DATA ARCHIVING........................................................................................................................................ 53
HISTORICAL DATA DISPLAY............................................................................................................................................ 53
13.
AMS .................................................................................................................................................................................. 54
14.
GLOSSARY..................................................................................................................................................................... 55
REVISION HISTORY .................................................................................................................................................................. 58

Revision: 1
1.
Document #: CS17160
Page: 3 of 58
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.
GENERAL GUIDELINES AND NAMING CONVENTIONS

General configuration layout and naming conventions are listed below. The plant Process Control
Engineer provides all names to outside contractors hired to configure the plant DeltaV system.
3.1. Controller Name
Each controller is named with the 3-digit area number as the prefix followed by the controller number.
Redundant controllers have a single name. Examples are provided below:
Controller
Location
019-C-1
Area 19 Controller 1
097-C-1
097-C-2
3.2. Plant Areas

Plant Areas are logical groupings of all equipment that define span of control. Areas are the highest
hierarchical level in DeltaV under Control Strategies. Each control module/equipment module is assigned
to an Area (directly or indirectly see below). How these Areas are assigned determines 1) whether a
module alarm displays on a workstation, and 2) whether control access is granted for a module (ability for
operator to change a module setpoint). Areas are assigned to both workstations and user profiles (login to
DeltaV). Module alarm display on a workstation is limited to modules whose area is assigned to that
workstation AND whose area is assigned to the user (profile) currently logged in at a workstation.
Control of modules is limited to modules whose area is assigned to the user (profile) currently logged in
at a workstation. See ALARM MANAGEMENT. DeltaV Areas are named after the plant area number
located on the plant plot plan. Examples are provided below:
Plant Area Name
AREA19
AREA21
AREA97
3.3. Process Cells
Process Cells are logical groupings of major process equipment required to produce a batch of material.
Process Cells are right below Areas in the overall DeltaV hierarchy and are assigned to an Area. Modules
assigned to a Process Cell are assigned to the Area to which the Process Cell is assigned. Process cells
are required when DeltaV Batch is utilized, but are otherwise optional for organizational purposes only.
Process Cells are named after the production line. Examples are provided below:
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 4 of 58
Process Cell Name

AREA_19
A72-MTO_TANKS
A21-STEROL_REC
3.4. Units
Units are logical groupings of major process equipment in which a single processing activity is conducted.
Units are right below Process Cells in the overall DeltaV hierarchy. Units are either directly assigned to an
Area or indirectly by being assigned to a Process Cell that is assigned to an Area. Modules assigned to a
Unit are assigned to the Area to which the Unit is assigned. Units provide the ability to group module alarm
displays and should be organized so that all modules assigned to a Unit display on a single DeltaV graphic.
That graphic should be assigned to the Units Primary Control Display: this provides automatic navigation
from the Unit alarm to the Units primary display. See ALARM MANAGEMENT. Units are named after the
major process equipment name found on plant P&IDs. Examples are provided below:
Unit Name
Corresponding P&IDs
019-R-1
Drawing 1
019-WFE-2
Drawing 2
090-DE-206
Drawing 3
3.5. Control Modules

Control modules provide direct monitoring and control of field devices and are accessible to operators via
graphical links and faceplates. Examples are flow/level/pressure/temperature indicators;
flow/level/pressure/temperature controllers where a control valve is automatically modulated to control the
process measurement to a setpoint; discrete valve (open/close) controllers; motor (start/stop) controllers.
Each control module should have a Primary Control Display assigned: this allows easy navigation from the
control module faceplate to the modules primary display.
Device signal tags (DST), associated with the IO cards (channels/ports), are the means for control modules
to read data from field devices (e.g., flow rate) and write date to control devices (e.g., control valve). Both
control modules and DSTs have tag names.
The DST and control module tag naming convention is as follows: AAA-BBB-CCC: AAA is the 3-digit area
number; BBB is based on ISA (International Society of Measurement and Control) conventions; CCC is
either the tag of the associated device or a sequential number. BBB for a DST represents the signal field
device, such as a transmitter or switch; BBB for a control module represents the control device as a whole,
such as and indicator, controller, pump, agitator, or XV valve. DST and control module tags are
documented on a Plant supplied Instrument IO list.
The maximum allowed characters is 16 for DST and module tag names (DeltaV system limitation). The
maximum allowed characters is 50 for DST descriptors (DeltaV system limitation) and 28 for module
descriptors (standard faceplate configured space). Sentence format shall be used for all DST and module
descriptors. Use abbreviations for temperature (temp), pressure (pres), high (hi), high high (hihi), low (lo),
and low low (lolo) if required to save space.
The following are example DST and module tag names:
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Module Type
Document #: CS17160
DST Description
DST Tag*
Page: 5 of 58
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
T-15 to T-35 or T45
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
R1 supply pump start

R1 supply pump stop
R1 supply pump run cfrm
R2 outlet valve open
R2 outlet valve close cfrm
R2 outlet valve open cfrm
Out
019-SV-F101
F101 carriage valve open
In 1
In 2
Out
In 1
In 2
044-ZSC-T3
044-ZSO-T3
090-SV-300
090-ZSA-300
090-ZSB-300
T3 supply valve close cfrm

T3 supply valve open cfrm
T-15 to T-45 open
T-15 to T-35 cfrm
T-15 to T-45 cfrm
Discrete Monitoring
In
072-XS-400
Tote fast speed switch
072-XI-400
Discrete Alarm
In
046-LSH-T4
T4 high level switch
046-LAH-T4
Discrete Output
Out
072-XO-500
T42 heating permit switch
072-XD-500
Analog Monitoring
In
060-FT-600
Boiler 1 steam flow xmtr
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
T10 agitator speed control

output
SO3 to R1 flow xmtr
SO3 to R1 flow control
output
019-SC-700
097-FIC-800
Tote fast speed

status
T4 high level
alarm
T42 heating
permit
Boiler 1 steam
flow
T10 agitator
speed control
SO3 to R1 flow
control
*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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 6 of 58
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
3.7. Named Sets

DeltaV provides Named Sets that are arrays of text names where each text name is associated with an
integer value. Named sets are primarily used so reports and messages to operators are easier to
understand. Some examples of standard named sets are mtr2-sp (two state motor setpoint) and vlvnc-pv
(valve normally closed process variable), which specify names and values for motors and valves. DeltaV
standard named sets are all lower case.
Custom developed named sets should be named with all caps and each name should be based on its
function. Plant-wide name sets belong in the K3 General folder. Area-specific named sets belong in the
Area folder and named Axx_yyy, where xx is area number and yyy is based on function i.e.
A19_CHRG_TANK. A DeltaV requirement for Named Sets used in class based modules is that the
number of text names (size of array) must be the same for all instances of the class. This has application
with tank level indicator modules and Named Sets used for tank contents and tank quality status.
When configuring expressions for actions, conditions, transitions, etc., named set names instead of the
named set values should be referenced when the parameter being referenced is a named set. For
example, //044-XV-R3A/DC1/PV_D.CV = vlvnc-pv:OPEN should be the expression, not //044-XVR3A/DC1/PV_D.CV = 1. This applies to Interlock modules, Equipment modules, and Batch phases.
All new name sets created must be approved by the plant Process Control Engineer.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 7 of 58
3.8. Module Defaults

Unless expressly detailed in this document or the Detailed Design Specification, the following basic DeltaV
module classes will be used. Additional classes derived from these basic classes also exist in the database
library. If additional classes are created, the modules in the list below should be used as a starting point.
Module/Point Type
Analog Input
Analog Alarm
Setpoint Totalizer
Timed Totalizer
Discrete Input
Discrete Output Pushbutton
PID Control Loop
Input Selector Control Loop
Split Range Control Loop
Gap DO Control Loop
Manual Output Loader
Discrete Normally Closed Valve
Discrete Normally Open Valve
3 Way Discrete Valve
Discrete Motor (1 Output)
Discrete Motor (2 Outputs)
Variable Speed Motor with no speed indication
Unit Failure
4.
Module Class Name

CL_AI_STD
CL_AI_PSEUDO
CL_TOT_SP
CL_TOT_TIME
CL_DI_STD
CL_ DO_PB_STD
CL_PID_STD
CL_PID_SELECT
CL_PID_SPLIT_STD
CL_GAP_DO
CL_MAN_STD
CL_VALVE_NC
CL_VALVE_NO
CL_VALVE_3WAY
CL_MOTOR_11
CL_MOTOR_12
CL_MOTOR_VFD_NF
CL_UNIT_FAIL
ANALOG MONITORING and CONTROL CLASSES

The following Faceplate and Detail displays are used for Analog Monitoring and Control classes.
Module/Point Type
Analog Input
AI-Pseudo
AI-Calc
Setpoint Totalizer
Timed Totalizer
PID Control Loop
Input Selector Control Loop
Split Range Control Loop
Gap DO Control Loop
Manual Output Loader
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
4.1. HART Signal Configuration

AI channels that connect to HART capable transmitters should have HART enabled. Even if HART values
are not used in module configuration, enabling HART allows the transmitter to be added to the AMS
database, providing transmitter calibration and advanced diagnostics from a DeltaV Pro station.
Modules containing a standard (non-Fieldbus) AI function block (Analog Input classes, PID control loop
classes, and Gap DO control loop classes) have the AI1 function block Status_Opts Properties exposed for
configuration. For those modules with the AI channel HART enabled, check the Bad if Limited box in the
AI1 Status_Opts Properties. This is done in order for the Bad_Active to trip (showing a FAIL icon near the
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 8 of 58
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 9 of 58
4.5. Timed Totalizer

Totalizers allow integration of an analog value. 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 ? periodic & demand reset and should not
be changed.
A Date Time Event function block contains the INTERVAL_STR and TE_TIME_STR parameters which
define the interval for resetting the totalizer and the start time respectively.
Mode Lock Mode lock hides the mode buttons on the totalizer faceplate.
Stack Totals The totalizer stores the previous three (3) totals. Totals are moved down then stack
each time the totalizer is reset.
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.
4.6. PID Control Loop
PID control loops combine all necessary logic to perform analog input channel processing, proportionalintegral-derivative (PID) control, and analog output channel processing. PID control modules use the
standard DeltaV PID function block wired to an Analog Input Block and Analog Output Block with the
following added features.
Interlock 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.
Default control options for the PID function block are the following and should not be changed:
Obey SP limit if Cas or RCas mode.
Track Enabled.
Track in Manual.
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 Alarms A high and high-high limit are configured for setpoint deviation alarms.
The PV Bad alarm is active during an Input Failure/Bad PV or Simulate Active on the AI, PID, or AO
function block.
Input Selector control loops (CL_PID_SELECT module class) are exactly the same with the addition of
three (3) AI function blocks and a signal selector (ISEL) function block.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 10 of 58
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
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
5.
Document #: CS17160
Page: 11 of 58
DISCRETE MONITORING and CONTROL CLASSES

All discrete modules contain critical alarms indicating when the device is in the wrong state or has
failed to reach the desired state. The following Faceplate and Detail displays are used for Discrete
Monitoring and Control classes.
Module/Point Type
Discrete Input
Discrete Normally Closed Valve
Discrete Normally Open Valve
3 Way Discrete Valve
Discrete Motor
Variable Speed Motor with No Speed Feedback
Variable Speed Motor with Speed Feedback
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
5.1. Discrete Input

Discrete inputs read a single binary value from a two-state field device. Discrete input modules use the
standard DeltaV DI function block.
5.2. Discrete Control
Device Control (DC) blocks provides setpoint control for multi-state discrete devices, such as motors and
on-off valves. DC blocks compare the requested state (setpoint) to the actual state reported from the
device (PV) and detect failure alarms after allowing time for change of state. Discrete control modules use
the standard DeltaV DC function blocks with the following added features.
Interlock Up to four (4) separate conditions can comprise an interlock for the discrete loop. (More
Permissive Up to four (4) separate conditions can comprise a permissive for the discrete loop. (More
conditions are available by using a different PERMISSIVE composite) Each condition may be
Mode Lock Mode lock hides the mode buttons on the discrete control faceplate.
Additional Mode An RCas mode has been added to Discrete Control modules. RCAS mode is
achieved by setting the R_CAS parameter to 1 and the DC function block mode to CAS. Phases write
to an input (PHASE_IN_D) parameter to control the module in RCas and Equipment Modules write to a
separate input (EM_IN_D) parameter to control the module in Cas mode.
The Interlocked DC state is omitted from the module device failure alarm.
For valves, the DEVICE_OPTS parameter in the DC function block is set as follows and should not be
changed:
Permissive
SP Track
Interlock
For motors, the DEVICE_OPTS parameter in the DC function block is set as follows and should not be
changed:
Passive on Active Timeout
Trip (with 5 sec delay)
Permissive
SP Track
Interlock
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 12 of 58
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 13 of 58
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 14 of 58
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.
BATCH MONITORING AND CONTROL

8.1. Hold Monitoring
All of the standard device control modules contain a HOLD linked composite that can be used for failure
monitoring. The control module will only Hold when enabled. The Hold logic must be enabled/disabled by
a phase, equipment module, or a user with proper access.
This composite should be left in the module even if the device is not currently manipulated by a phase or
equipment module. This will ensure future compatibility and minimizes the number of faceplates required.
In general, any Critical priority alarm will cause a HOLD for a control module if the hold parameter is
enabled. Some examples of a Critical alarm are a High High Alarm on an analog input, or PID module, or a
Fail alarm for a discrete device such as a valve or motor. The following conditions cause a HOLD for
different module types:
Analog Input Modules - HI_HI_ALM, LO_LO_ALM, and PVBAD_ALM
PID Modules - HI_HI_ALM, LO_LO_ALM, DEV_HI_HI_ALM, and PVBAD_ALM
Discrete Modules (motors, valves, etc.) - 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.
Totalizer Modules - MODE not in AUTO, HI_HI_ALM
VFD Modules - HI_HI_ALM, LO_LO_ALM, PVBAD_ALM, 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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 15 of 58
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.
Failure Monitor Block

Failure Monitor blocks are configured in calculation blocks and monitor the status of state
transitions and operation of composite blocks within the phase. Phase failures consist of
arbitration and equipment failures. Any detected failure places the phase immediately into the
holding state.
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
8.3.4.
Document #: CS17160
Page: 16 of 58
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.
8.4. Process Unit

Process units divide process equipment into logical groupings that are acquired by phases in a recipe.
Equipment arbitration functions of DeltaV rely on configuration of units to notify operators when equipment
is allocated to another recipe in the process. This convention is used to configure units with one or more
owners.
8.5. Batch Historian
All batch events and alarms are collected in a Batch Historian running on the Continuous Historian server
001-CH-1.
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
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 17 of 58
9.2. Workstation Configuration

9.2.1.
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
In addition to Operator privileges, the Supervisor User is able to tune loops,

disable/enable/suppress alarms, change alarm trip points, and bypass interlocks.
Configure
In addition to Operator and Supervisor privileges, the Configurer User is able to

change configuration, build recipes, operate Batch, and download to controllers.
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.
Administrators have unrestricted access to the entire DeltaV system.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
9.2.3.
Document #: CS17160
Page: 18 of 58
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.
Operator HMI: Graphical Displays

Graphical displays are the primary interface operators use to view and control the processes
under their control. All other types of displays (e.g., trends, batch list) can be accessed from
graphical displays or from icons provided within the DeltaV Operate application.
10.1. Process Graphic Displays

Process graphic displays are custom displays designed to present a graphical view of the process and
appear much like Process and Instrumentation Diagrams. In addition to static layout of equipment and
process lines shown on those drawings, these displays have dynamic information indicating the current
process conditions. Color change is applied to text and numeric values and devices (e.g., valves and
motors) to indicate current state.
All graphics must be created from a New Template (Main1280). Once created, delete the grpDesc (main
text), delete the NavigateButtons, and delete the grpOpen buttons. Leave in place the bmpClosepic,
dtlCurrentLink, and the VariableGroup. Change the background color to Dark Teal (color 152). The graphic
is now ready to add process information. All major devices and other items found on process graphics
(graphic title text, pipes and elbows, arrows, graphic linking arrows, pumps, agitators, automated and
manual valves, module data boxes) are located on standard graphics on the Kankakee system:
K3Template1, K3Template2, and K3Template3. All new graphics must be created by copying items
from these template graphics. In addition, graphics should not be over populated to avoid the system
warning, Maximum number of recommended datalinks exceeded.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 19 of 58
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
DELTAV COLOR NAME/NUMBER

BLACK
BRIGHT CYAN
GRAY60
BRIGHT GREEN
GREEN
COLOR5
CYAN
COLOR152
BRIGHT RED
RED
WHITE
BRIGHT BLUE
MAGENTA
BRIGHT 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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 20 of 58
10.1.3. Tanks and Vessels

Tanks and other vessels are various shades of gray in color with no dynamic color change. All
Tanks/Vessels have their equipment number centered in the top portion of the Tank/Vessel. Tank
numbers should be displayed with a prefix of the area they are in only if different from the area
identified in the graphic title.
Tanks/Vessels equipped with level transmitters or load cells include a vertical bar graph that fills
based on PV of the Level/Weight measurement. In addition to the bar graph, a dynamic value
field displays actual level/weight on the side or within the vessel.
The bottom of tank level bars should be configured to equal the amount in the tank when the
transmitter is reading 0% signal, and the top of tank level bars should be configured to equal the
tank capacity. Note: the vertical bar graph on the tank level faceplate will differ its bottom is also
the amount in the tank when the transmitter is reading 0% signal, but its top is the amount in the
tank when the transmitter is reading 100% signal. In instances where the level transmitter span
exceeds the tank capacity, the top of the faceplate vertical bar graph exceeds tank capacity. Bulk
tanks should have the tank capacity displayed (shown as Max xx yyyy with xx engineering units
and yyyy the amount) on or near the tank. Tank capacity is a parameter in each class based level
monitoring module.
A dynamo is provided for most bulk storage tanks allowing operator entry of the tank contents
(material) and status (of the material or tank). Tank Contents and Quality Status are parameters
in each class based level monitoring module.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 21 of 58
10.1.4. Pipes and Control Lines

All pipes are colored in various shades of gray, similar to that of tanks. Piping is not dynamically
colored. Arrows on or at the end of pipes distinguish between process (Orange) and utility (Lt.
Green) lines. Arrows at the end of pipes with a gray outline indicate a graphics link that will
change the display when clicked. Arrows (Orange or Lt. Green) can be added in the middle of
pipes to clear up the direction of flow.
Dash dot dot lines or polylines should be added to clarify control device location. Yellow shows
were PV is coming from (transmitter location) and cyan represents what the output is controlling.
Cyan lines connecting to a control valve can terminate either near the output value (as shown
below) or on the control valve small top hat.
10.1.5. Motor Controlled Devices

Pumps
Module Name (e.g., 066-P-20), Mode, Interlock Status, Interlock Bypass status, and Batch Hold
Status appear near each pump. The body color of the pump is linked to the setpoint command
(SP) and the impeller or blade movement is linked to the actual state (PV). A sample screen shot
with all satellite indications is shown below.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
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
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 23 of 58
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
mode is incorrect for batch operation
valve when interlocked
to the valve when bypassed
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 24 of 58
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
mode is incorrect for batch sequence
valve when interlocked
to the valve when bypassed
valve when held.
10.1.7. Control Loops

Control Loop information is displayed near the analog transmitter. Information displayed for a
Control Loop is as follows; Module Name, Process Variable (PV), Setpoint (SP), Engineering Units
(EU), Batch Hold Status (H), and Fail Status (F). A sample is shown below.
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
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 25 of 58
10.1.8. Analog Indication Points

Analog information is displayed near the analog transmitter. Information displayed for an Analog
Input is as follows: Module Name, Process Variable (PV), Engineering Units (EU), Batch Hold
Status (H), and Fail Status (F). A sample is shown below. PVs will take on the configured Alarm
Priority and Alarm Acknowledgement status colors when in alarm.
PARAMETER
Indicator Module Name Color
PV & Units Color
Instrument Failed
Default Value
Black
Yellow
the indicator data box when failed
the indicator data box when held
10.1.9. Totalizer Points

Totalizer Information is displayed near to where the transmitter or device is located. Information
displayed for a Totalizer is as follows: Module Name, Set Point (SP), Current Totalizer Output
(Total), and Batch Hold Status (H). A sample is shown below. Outputs will take on the configured
Alarm Priority and Alarm acknowledgment status colors when in alarm.
PARAMETER
Totalizer Module Name Color
Total Color
SP Color
Default Value
Black
Cyan
White
the totalizer data box when held
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 26 of 58
10.1.10. Discrete Indication Points

Discrete Indicators are displayed near the discrete source. Indication colors take on the
configured Alarm Priority and Alarm Acknowledgement status colors when in alarm (shown). The
non-alarm state text (e.g., LEVEL OK) appears in the standard PV color when the indicator is in
the non-alarm status. A batch hold satellite and a Fail Satellite are also present.
PARAMETER
Active Alarm Color
Passive Color
Instrument Failed
Default Value
Matches Alarm Priority (Critical Shown)
Yellow
the indicator data box when held
the indicator data box when failed
10.1.11. Equipment Modules Single Run Mode

Single run mode equipment modules are represented on process graphics by text with color
animations based on the current state of the equipment module (i.e. Activated, Running, etc.).
Equipment Module names are always visible, but appear gray when they are deactivated.
PARAMETER
Activated Color
Running Color
Stopping Color
Deactivated Color
Default Value
White
Green
Red
Gray
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 27 of 58
10.1.12. Equipment Modules Multiple Run Modes
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
10.1.13. Unit Phase Displays

Unit Phase Displays are placed on the graphic(s) that contain the main unit that the phases will be
acting upon. Unit Phase Displays depict the unit name and all of the active phases for that unit.
Phases that are not currently loaded are not displayed. Phase names colors are animated to give
feedback to the operator regarding phase status. Gray phase text indicates that there is no phase
message, yellow indicates that there is a phase message, and blinking yellow/white indicates that
the phase is waiting for operator action. Other possible colors are summarized below.
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
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 28 of 58
10.1.14. Prompt Phase Display

One Message Phase Display is placed on a graphic for each unit that is represented on that
graphic. Prompt Phase Displays show running phases for the unit as individual tabs above the
message line. The tab with the blue line below it indicates which phase message is being
displayed. Clicking on other tabs will show that phases message.
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 29 of 58
10.2. Faceplates and Detail Displays

Each of the graphical representations shown above (pumps, valves, analog, discrete, etc) launches a
faceplate for a control module when they are clicked. Faceplates display additional information about a
device as well as allow for mode, setpoint, or output manipulation.
Detail displays can be launched from a faceplate and provide additional information for trouble shooting as
well as allow users with the appropriate privileges to change tuning level parameters.
Discrete Control, Manual Loader, and Analog Loop (PID) details also contain an interlock section that
contains a list of all interlock conditions for a device as well as the current state of each condition (inactive
or active; bypassed).
10.2.1. Discrete Control Faceplate
The DC faceplate (shown below for a valve) 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 output to the field (D) is
manipulated by the device control buttons shown (the text on the buttons changes depending on
the device type). The device control buttons are only enabled when the device is in a mode that
the operator is allowed to manipulate the output (AUTO for DC devices). A third button is used for
three state devices.
The actual mode (E) is displayed next to buttons for selecting enabled modes.
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.
The module hold alarm is displayed (G) along with a button to reset the alarm after the condition
that has caused the hold clears.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 30 of 58
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Device State
Diagnostics
Last printed 6/19/2014 10:13:00 AM
Page: 31 of 58
Alarm
Options

Revision: 1
Document #: CS17160
Interlocks
Page: 32 of 58
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
The alarms window (F) shows all active alarms associated with the module. Alarms are arranged
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 33 of 58
A
C
F
B
E
G
A standard button bar along the bottom of the DI faceplate (G) allows for (buttons described from
The DI detail display consists of 4 tabs. Clicking on a tab heading changes the information
Alarms
Device State
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Diagnostics
Page: 34 of 58
Empty
10.2.3. Analog Control (PID) Faceplate

The PID 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.
The set point is depicted numerically and graphically in the form of an arrowhead (D) alongside the
PV bar.
The controller output to the field is depicted numerically and graphically (E) in the form of bar in
standard output color.
The actual mode (F) is displayed next to buttons for selecting enabled modes.
The SP deviation alarms (G) are located directly below the set point. Standard analog alarms
(LoLo, Lo, Hi, HiHi) are depicted (K) just above the modes. Alarm limits are visible by holding the
cursor over the alarm lights on the faceplate. In the faceplate below, the Hi alarm is active and the
Lo alarm is currently suppressed. Suppressed alarms are depicted by the prohibited symbol
shown on the alarm light. Disabled alarms, like the LoLo alarm, are shown as grayed out.
The module hold alarm is displayed (I) along with a button to reset the alarm after the condition
The alarms window (H) shows all active alarms associated with the module. Alarms are arranged
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 35 of 58
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
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
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Alarms
Options
Last printed 6/19/2014 10:13:00 AM
Page: 36 of 58
Device State
Diagnostics

Revision: 1
Document #: CS17160
Tuning
Page: 37 of 58
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
The alarms window (G) shows all active alarms associated with the module. Alarms are arranged
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 38 of 58
G
D
B
E
F
A standard button bar along the bottom of the AI faceplate (F) allows for (buttons described from
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
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 39 of 58
Device State
Alarms
Diagnostics
Last printed 6/19/2014 10:13:00 AM
Options

Revision: 1
Document #: CS17160
Page: 40 of 58
10.2.5. Manual Loader Faceplate

The Manual Loader 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 manual output to the field is depicted numerically and graphically (C) in the form of bar in
standard output color. The output is adjusted by either slewing the arrowhead alongside the OUT
bar or clicking directly on the setpoint box.
The actual mode (D) is displayed next to buttons for selecting enabled modes.
A
F
C
E
B
G
The alarms window (E) shows all active alarms associated with the module. Alarms are arranged
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
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Device State
Diagnostics
Last printed 6/19/2014 10:13:00 AM
Page: 41 of 58
Options
Tracking

Revision: 1
Document #: CS17160
Page: 42 of 58
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
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 43 of 58
The alarms window (H) shows all active alarms associated with the module. Alarms are arranged
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
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
Alarms
Last printed 6/19/2014 10:13:00 AM
Device State

Revision: 1
Document #: CS17160
Diagnostics
Page: 44 of 58
Empty
10.2.7. Equipment Module Faceplate

The Equipment Module faceplate (shown for an activated equipment module) shows the
equipment module name and description (A) as well as the unit that it acts upon (B).
The faceplate has a button for each of the five equipment module states: Activate (not visible),
Deactivate, Start, Stop (not visible), and Hold (not visible) (C). A Restart button (not visible)
becomes visible when the equipment module is in the Hold state and all Holds have cleared.
The current state of the equipment module (D) is depicted in a color to represent the actual state.
A combo box (E) allows operators to change the mode of the equipment module (e.g., what
resource tank to charge from, etc.). A message box (F) provides feedback to the operator.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 45 of 58
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Operator Parameters
Permissives
Last printed 6/19/2014 10:13:00 AM
Page: 46 of 58

Revision: 1
Document #: CS17160
Page: 47 of 58
Tuning Parameters
10.2.8. Unit Alarms Faceplate

The alarm priorities on the Kankakee system are configured to show the control modules
associated unit module on the alarm banner. If a module goes into alarm and has been assigned
to a unit, the unit will display on the alarm banner. Clicking on the unit on the alarm banner opens
the Unit Alarms faceplate which displays all control module alarms that are assigned to that Unit.
The Unit Alarms faceplate works the same as the alarm banner where the highest priority alarms
are at the top of the list. Tabs are provided for extended lists.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 48 of 58
10.2.9. Batch Unit Faceplate

The Batch Unit faceplate is accessible by clicking on a units name (cyan in color) from a main
display. A Unit faceplate shows the unit name and description (A) as well as information regarding
the batch ID (B) and the operation, unit procedure, and procedure (C) that are currently acting on
the unit.
D
A
B
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 49 of 58
10.2.10. Phase Faceplate

The phase faceplate provides the operator with information about a running phase. The phase
faceplate shows the phase name (A), the batch ID that the phase is currently processing (B), the
current phase state (Running, Stopping, Stopped, Held, etc.) (C), and the current step that the
phase is executing (D).
If a message is available, it will display (E) along with the tag name and target value of a device
that the phase is waiting for.
A
B
C
D
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 50 of 58
10.3. UserSettings/Layout Files

The UserSettings picture, located in the DVData\Graphics-iFix\Pic\Standard folder, contains Visual Basic
script that is used to set values when DeltaV Operate initializes. The picture can be edited and saved for
system-wide settings and/or workstation-specific settings. This file should be modified only by or with
permission from the plant process control engineer.
The Kankakee facility has the following options configured in the UserSettings picture:
Pushpin The pushpin is visible on faceplates. A pushed in pin keeps the faceplate from being closed
when subsequent faceplates are open.
Workstation Node Status The audible horn does not sound for workstation node status changes.
Toolbars/Alarm Banners The toolbar above the graphic and the alarm banner below the graphic is
specified for each screen of a workstation.
Overview/Display Directory The Overview and Display Directory icons on the toolbar above the
graphic is specified for each screen of a workstation.
Initial Displays The graphic that initially loads when the DeltaV Operate application starts is specified
for each screen of a workstation.
Quad Monitor workstations must have a Layout file configured to specify left(x) and top(y) position in pixels
for the displays (including toolbars and alarm banners). Layout files are located in the DVData\GraphicsiFix\Local folder, and are named after the name of each workstation. Layout files are created for all
workstations in the Kankakee DeltaV system (not just quad monitor stations). Besides specifying positions,
the names of the Toolbars, Alarm Banners, and Initial Displays are specified in layout files. These three
items are also specified in the UserSettings file, but if/when these items are specified in both locations, the
information in the Layout file overwrites those values specified in the UserSettings file. The practice at the
Kankakee plant is to specify the same Toolbars, Alarm Banners, and Initial Displays in both locations
(UserSettings and Layout files).
The UserSettings file does provide some features not available in the Layout files. Among other things, the
UserSettings file can reserve pictures for fast call-up times, pre-populate a main display history list, specify
how the Process History View application is launched, and open Schedulers.
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 51 of 58
11.1. Alarm Reporting

All module alarms are events and are collected in an Event Chronicle running on the Continuous Historian
server 001-CH-1. Alarms and Events are also enabled on all Professional workstations to provide
redundant collection of events. The Event Chronicle running on 001-CH-1 records every event reported for
all modules in the plant. Each Professional workstation records only events of modules assigned (by Area)
to the workstation.
Whether a process alarm reports to a workstation depends on Area assignment. Each module is assigned
to an Area. If a modules Area is assigned to that workstation AND if the modules Area is assigned to
the user (profile) currently logged in at a workstation, then that modules (active) alarm displays and
sounds the alarm horn on that workstation. The alarm horn can be optionally disabled. Workstations in a
control room should be configured so that all relevant alarms are reported to at least one workstation in that
control room. It is acceptable to split alarm reporting between workstations, i.e. report some Area alarms to
one workstation and other Area alarms to another workstation. If this is done and one workstation fails,
licensing should be temporarily moved to the remaining workstation(s) so that alarm reporting is not lost
during the time the failed workstation is being repaired/replaced.
Process alarms display on workstations in various locations, including the alarm banner below the graphic,
the graphic itself through animated colors, faceplates, and the Alarm List. How a process alarm displays on
a workstations alarm banner depends on how each alarm priority is configured on the DeltaV system. All
process alarm priorities on the Kankakee system are configured to show the unit module on the alarm
banner. Most but not all modules are assigned to units. If an alarm becomes active on a module assigned
to a unit, its unit module displays on the alarm banner. Clicking on the unit on the alarm banner opens the
unit alarms faceplate and the units primary display opens on the screen. If an alarm becomes active on
a module not assigned to a unit, its module displays on the alarm banner. Clicking on the module on the
alarm banner opens the module faceplate and the modules primary display opens on the screen.
11.2. Alarm Priorities
Alarm priorities indicate to operators the importance of the alarm event. The order in which alarms appear
in the Alarm Banner and Alarm List is determined by alarm priority, acknowledged status, and time stamp.
There are twelve (12) possible alarm priority levels: numeric values 4 through 15 plus a special "log only"
priority level (value 3). Alarms with higher priority value are more important than alarms with lower priority
value. The highest priority value is 15. The lowest priority value is 4.
Events with Log priority (level value 3) are not considered alarms. Log priority is to designate an event
important enough to be recorded in the Event Chronicle but not something operators must be aware of.
Events with Log priority are not displayed in the Alarm Banner or Alarm List and do not activate the alarm
horn.
By default, only four of the 12 (plus Log) priority levels are available for configuring alarm parameters in the
system:
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
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 52 of 58
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
11.3. Alarm Types

A number of alarm types are provided by the DeltaV system. Examples are Change from Normal, Change
of State, Deviation Alarm, General I/O Failure, High Alarm, High High Alarm, Low Alarm, Low Low Alarm,
Over Range, Rate of Change, and Under Range. Pertinent alarm types have been configured in all module
classes.
12.
TRENDING AND DATA ARCHIVING
12.1. Historical Data Collection

Historical data is collected on the DeltaV continuous historian server 001-CH-1. Historical data can also be
collected on local workstations. Event data is also collected on each Professional workstation to provide
redundancy to 001-CH-1. Continuous data is also collected on some local workstations to provide
redundancy to 001-CH-1 for Areas that use historical data to demonstrate regulatory compliance. In those
Areas, modules recording regulatory data are placed in a separate Area and that Area is assigned to both
001-CH-1 and the local workstation. The number of history points in the regulatory Area must not exceed
the workstation limitation of 250.
Data compression is utilized when collecting historical data in order to optimize disc space. Collection rate
and compression deviation is applied to analog data collection based on how fast the analog signal is
expected to change, and is typically configured as listed in the following table.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 53 of 58
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%
Per variable type

above
2X per variable
type above
2X per variable
type above
Per variable type

above
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
13.
Document #: CS17160
Page: 54 of 58
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
14.
Document #: CS17160
Page: 55 of 58
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 Control Studio

DeltaV Diagnostics
DeltaV Explorer
The current operating mode of the block.

Alarms alert the operator that a particular event has occurred. Alarm priority, color, and
sound can be changed to user preferences.
A set of logical steps for solving a problem or accomplishing a task. The modules
algorithm defines how the module behaves.
The Analog Input (AI) function block accesses a single analog measurement value and
status from an I/O channel. The AI function block supports block alarming, signal
scaling, signal filtering, signal status calculation, mode control, and simulation.
The Analog Output (AO) function block assigns an output value to a field device through
a specified I/O channel. The block supports mode control, signal status calculation, and
simulation.
A logical division of a process control system. Areas typically represent plant locations
or main processing functions.
Can be a permitted target mode. Setpoint is local to the block, (not being driven
externally). The block algorithm determines block outputs. A module in AUTO mode has
its setpoint entered by the operator from the faceplate.
A DeltaV application that includes the content of the paper documentation plus theory of
operation, configuration planning, and application-specific and system-wide reference
information.
Can be a permitted target mode. Cascade connection to setpoint. Setpoint is being
driven through CAS_IN (the Cas input). The block algorithm determines block outputs. A
module in CAS mode has its setpoint entered by another module.
A block in an algorithm that is made up of two or more blocks. A composite can contain
function blocks or sequential-function charts.
From an operator perspective, a control module is the lowest level module in the system:
control modules monitor or control single devices. Examples of control modules are 1)
tank level indicator, 2) reactor pressure control loop, 3) XV valve controllers, 4) motor
controllers for pumps and agitators.
The DeltaV system device that runs the algorithms to control the process equipment and
communicates the process data to the operator workstation.
A collection of data organized for rapid search and retrieval. The DeltaV database allows
you to make on-line and off-line changes to your configuration. The DeltaV database
resides on the Professional Plus server.
To take a controller out of service, usually to replace a failed controller. This resets the
IP address to the default address and resets the controllers configuration. (After a
controller is decommissioned, a controller placeholder that contains configuration
information remains on the system: this placeholder should not be deleted).
To find and eliminate problems with an installed module by stepping through the
algorithm and examining values.
Asset Management System or Intelligent Device Manager. An application that can run
on a Professional workstation 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. Besides viewing and configuring device parameters, AMS can
be used to perform a number of other tasks based on optional additional software
installed.
An application that can run online or offline on a Professional workstation and offline only
on Operator workstations that provides a view of the function block configuration of
modules.
An application that can run on all workstations that provides diagnostic information on the
DeltaV system.
An application that can run on a Professional workstation that provides a view of the
DeltaV system similar to the view Windows Explorer provides for a personal computer. It
allows the DeltaV hierarchy (areas, nodes, and modules) to be viewed, created, and
Last printed 6/19/2014 10:13:00 AM

Revision: 1
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
Page: 56 of 58
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.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
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
Page: 57 of 58
A reusable configuration structure. Modules link algorithms, conditions, alarms, displays,

history, and other characteristics together for a particular piece of equipment to develop
a control strategy.
A device (either a DeltaV controller or workstation) on the control network.
A person who supervises and controls the running process using the DeltaV Operate
Interface application to monitor and set process values.
Is always a permitted mode. The block is out of service.
The name of a logical grouping of data such as SP or PV. Each element of data within
the group is referred to as a field. A user with the appropriate privileges can modify
parameters off-line or on-line to affect the current process.
A collection of physical devices and methods used in the production or manufacturing of
a product.
A logical grouping of equipment that includes all equipment required for production of a
batch. Defines the span of logical control of one set of process equipment within an
area.
The process plant signal input that is available as an attribute for certain DeltaV modules
such as DC, AI, and Loop modules.
A collection of data (such as date/time, parameter, node, area, level, etc.) for a single
event. Records, which can be copied, printed, and exported, are presented as rows in
an event chronicle.
A diagram that defines the sequence of events with steps, transitions, and actions.
The process plant signal desired value that is available as an attribute for certain DeltaV
modules such as DC and Loop modules.
An element of a sequential function chart (SFC) that contains a set of actions. A step is
either active or inactive.
The mode that the block is trying to attain. When an operator sets the mode, it is the
target mode that is being set.
Contains variables, phase, and/or control modules for a single process unit.
Last printed 6/19/2014 10:13:00 AM

Revision: 1
Document #: CS17160
Page: 58 of 58
Revision History
Revision
Date
Page
07/19/10
All
02/21/13
7, 8,
10, 17
Description
Initiator
Original
J. Shute
Updated BASF Header; replace references to

Cognis; add HART configuration to analog input
classes; update AI_PSEUDO and AI_CALC
classes; rename VFD motor module faceplates;
update user account descriptions.
J. Shute
Last printed 6/19/2014 10:13:00 AM

Display

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Display

Uploaded by

Copyright:

Available Formats

Engineering and Construction Specifications

GENERAL GUIDELINES AND NAMING CONVENTIONS ............................................................................................ 3

ANALOG MONITORING AND CONTROL CLASSES.................................................................................................... 7

TOP LEVEL ..................................................................................................................................................................... 12

DISCRETE INPUT ............................................................................................................................................................ 11

HART SIGNAL CONFIGURATION ...................................................................................................................................... 7

DISCRETE MONITORING AND CONTROL CLASSES............................................................................................... 11

CONTROLLER NAME ......................................................................................................................................................... 3

INTERLOCK MODULES .................................................................................................................................................... 13

BATCH MONITORING AND CONTROL......................................................................................................................... 14

WORKSTATION CONFIGURATION ............................................................................................................................... 16

W ORKSTATION NAMES .................................................................................................................................................. 16

Engineering and Construction Specifications

OPERATOR HMI: GRAPHICAL DISPLAYS.............................................................................................................. 18

10.1. PROCESS GRAPHIC DISPLAYS ....................................................................................................................................... 18

ALARM REPORTING ........................................................................................................................................................ 51

TRENDING AND DATA ARCHIVING.......................................................................................................................... 52

HISTORICAL DATA COLLECTION ..................................................................................................................................... 52

REVISION HISTORY .................................................................................................................................................................. 58

Engineering and Construction Specifications

GENERAL GUIDELINES AND NAMING CONVENTIONS

3.2. Plant Areas

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

Process Cell Name

3.5. Control Modules

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

T-15 to T-35 or T45

R1 supply pump start

F101 carriage valve open

T3 supply valve close cfrm

Tote fast speed switch

T4 high level switch

T42 heating permit switch

Boiler 1 steam flow xmtr

T10 agitator speed control

Tote fast speed

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

3.7. Named Sets

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

3.8. Module Defaults

Module Class Name

ANALOG MONITORING and CONTROL CLASSES

4.1. HART Signal Configuration

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

4.5. Timed Totalizer

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

DISCRETE MONITORING and CONTROL CLASSES

5.1. Discrete Input

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

Last printed 6/19/2014 10:13:00 AM

Engineering and Construction Specifications

Last printed 6/19/2014 10:13:00 AM