Delta V Overview

DeltaV Overview
TM
EMERSON Process Management Educational Services Copyrighted Material / Reproduction Restricted

EMERSON Process Management – Educational Services Course 7009 – Rev 9 – 8/15/07 Copyrighted Material / Duplication Prohibited
1-2
Objectives
Upon completion of this module, you will be able to define
• DeltaV System architecture
• DeltaV Software components
• DeltaV System capacities
• PlantWeb
1-3
DeltaV System Architecture
10/100BaseT Cable
Workstation Maximum Length 100m (330ft)
Controller
Primary Switch
Secondary Switch
10/100BaseTx Cable
Maximum Length 100m (330ft)
1-4
The figure above illustrates a basic DeltaV Control Network.
Refer to DeltaV Books Online for additional information about the DeltaV system
architecture.
1-5
Multiple Nodes
Workstation
Primary Switch Secondary Switch
System Power Supply,

Controller, and
I/O Subsystem
Legend:
Primary Control Network
Secondary Control Network
1-6
Multiple Nodes
The figure above illustrates a DeltaV Control Network with eight nodes.
Maximums:
120 — Nodes
100 — Controllers / Simplex or Redundant Pairs
60 — Workstations
Notes: A server may be required depending on system size.

Refer to DeltaV Books Online for additional information about the DeltaV system
capacities.
1-7
DeltaV Zones
Zone 1 Zone 2
Inter-Zone
Servers
Zone 3 Zone 4
Inter-Zone
Servers
1-8
DeltaV Zones
DeltaV Zones allow multiple DeltaV Systems to communicate operating data and alarms
between one another via Inter-Zone Servers (IZS).
Each zone is a standalone DeltaV system, comprised of the Pro+ node, an Inter-Zone
Server node, and other nodes as desired.
Zone considerations:
• The ability to upgrade systems independently while maintaining communications
• Large systems greater than 30,000 DSTs and/or 120 Nodes
• A maximum of 10 Zones
• Optional redundant IZS
• Each Zone requires a license
1-9
DeltaV I/O Interface
2-Wide Power/ 8-Wide I/O
Controller Carrier Interface Carrier
Mounting Screw
DIN Rail I/O Card I/O Terminal Block
1 - 10
DeltaV I/O Interface
The I/O Subsystem includes I/O Interfaces mounted on one or more 8-wide I/O
Interface Carriers and an optional power source that provides power to field devices.
The I/O Interface consists of the following components as illustrated above:
• I/O Terminal Block which snaps onto the I/O Interface Carrier to provide screw
termination's for field wiring.
• I/O Card which snaps over the I/O Terminal Block on the I/O Interface Carrier
which converts field signals to a digital format for control and communications.
Refer to DeltaV Books Online for additional information about the DeltaV System
architecture.
1 - 11
DeltaV I/O Card Types
Analog Inputs
• Series 2 AI, 8 Channel, 4 to 20 mA, HART
• AI, 16 Channel, 4 to 20 mA, HART
• AI, 4 Channel, Isolated Input (Tcouple, RTD, MVolt, Ohms, Voltage)
• AI, 8 Channel, 4 to 20 mA
• AI, 8 Channel, 1-5v
• I.S. AI, 8 Channel, 4 to 20 mA, HART
• RTD, 8 Channel
• Thermocouple, 8 Channel
1 - 12
Discrete Inputs
• DI, 8 Channel, 24 VDC, Isolated
• Series 2 DI, 8 Channel, 24 VDC, Dry Contact
• DI, 8 Channel, 24 VDC, Dry Contact
• DI, 8 Channel, 120 VAC, Isolated
• DI, 8 Channel, 120 VAC, Dry Contact
• High Density DI, 32 Channel, 24 VDC, Dry Contact
• I.S. DI, 16 Channel, 12 VDC I.S. Power
• Multifunction, 4 Channel, DI or Pulse Input
• SOE (Sequence of Events), 16 Channel, Standard DI or SOE
1 - 13
Analog Outputs
• Series 2 AO, 8 Channel, 4 to 20 mA, HART
• AO, 8 Channel, 4 to 20 mA, HART
• AO, 8 Channel, 4 to 20 mA
• I.S. AO, 8 Channel, 4 to 20 mA
• I.S. AO, 8 Channel, 4 to 20 mA, HART
1 - 14
Discrete Outputs
• DO, 8 Channel, 120/230 VAC, Isolated
• DO, 8 Channel, 120/230 VAC, High Side
• DO, 8 Channel, 24 VDC, Isolated
• Series 2 DO, 8 Channel, 24 VDC, High Side
• DO, 8 Channel, 24 VDC, High Side
• High Density DO, 32 Channel, 24 VDC, High Side
• I.S. DO, 4 Channel, 12 VDC I.S. Power
1 - 15
DeltaV Communication Interface
FOUNDATION™ fieldbus Interface
• 2 Ports, maximum of 16 Devices/Port, 1900 meters
DeviceNet (Series 2)
• 1 Port, maximum of 61 Devices, 500 meters @ 125K baud
Profibus DP
• 1 Port, maximum of 64 Devices, 2000 meters @ 1.5M baud
Actuator Sensor Interface (AS-i)
• 2 Ports, maximum of 31 Devices/Port, 300 meters
Serial Interface
• 2 Port Modbus Protocol, RS232/RS485 or 2 Port Programmable
1 - 16
1 - 17
Remote I/O
Remote I/O consists of a Remote Interface Unit and I/O cards. The Remote Interface
Unit communicates on the control network and allows the I/O to be mounted distances
from controllers that are supported by the control network.
The Remote Interface Unit is considered a node on the control network but does not
count against the 120 node capacity. Remote I/O cards can be assigned to different
controllers on a card by card basis.
Controller
Remote Interface Unit

1 - 18
DeltaV Remote I/O Card Types Zone 2
Analog Inputs
• AI, 8 Channel, 1-5v
• AI, 8 Channel, 4 to 20 mA
• AI, 8 Channel, 4 to 20 mA, HART (Series 1 and 2)
• Millivolt, 8 Channel
• RTD, 8 Channel
• Thermocouple, 8 Channel
Analog Output
• AO, 8 Channel, 4-20 mA
• AO, 8 Channel, 4 to 20 mA, HART (Series 1 and 2)
1 - 19
DeltaV Remote I/O Card Types Zone 2
Discrete Inputs
• DI, 8 Channel, 24 VDC, Isolated
• DI, 8 Channel, 24 VDC, Dry Contact (Series 1 and 2)
• High Density DI, 32 Channel, 24 VDC, Dry Contact
Discrete Outputs
• DO, 32 Channel, High Density
• DO, 8 Channel, 120/230 VAC, High Side
• DO, 8 Channel, 120/230 VAC, Isolated
• DO, 8 Channel, 24VDC High Side (Series 1 and 2)
• DO, 8 Channel, 24VDC, Isolated
1 - 20
Card Types Zone 1
Remote I/O Card Types Zone 1
• Analog Input/Output
8 AI Channels, 4 to 20 mA, HART
4 AO Channels, 4 to 20mA, HART
• Discrete Input/Output
16 DI Channels, Dry Contact
8 DO Channels, High Side
Refer to DeltaV Books Online
Configuration → I/O configuration → DeltaV Remote I/O
For card specifications, refer to the HART Analog Input Channel specifications, HART
Analog Output Channel specifications, Discrete Input Channel specifications and
Discrete Output Channel specifications topics in the Installing of your DeltaV Zone 1
hardware manual.
1 - 21
DeltaV SIS - SLS 1508 Logic Solver
16 channels of I/O per Logic Solver consists of a mix of:
• HART Analog Input
• Analog Input
• HART two-state Output
• Discrete Input 12VDC dry contact
• Discrete Output 24 VDC High Side
• Line fault detection on I/O
• Separate I/O processor
• Redundant Main Processors
• 50mS Module Execution
• SOE timestamp at module execution
• Eight additional Boolean values published Peer-to-Peer on every scan
1 - 22
1 - 23
Controller
2-Wide Power/ 8-Wide I/O
Controller Carrier Interface Carrier
I/O Card
DIN Rail
Mounting Screw I/O Terminal Block
Controller
1 - 24
Controller
The DeltaV Controller mounts in the right slot of the 2-wide Power/Controller Carrier as
illustrated above. Vertical mount carriers are also available for Controllers and I/O cards.
Refer to DeltaV Books Online for additional information about DeltaV.

Search: Installing Your DeltaV System.
1 - 25
DeltaV Hubs & Switches
Hubs and switches provide a means to connect multiple nodes. Hubs are used in small
training or demo systems, typically less than 8 nodes. Hubs serve as a connection point
and rejuvenate the electrical signal as messages are forwarded on the control network.
Switches are recommended in on-line plant systems. Switches provide the same
function as a hub and additionally separate traffic to improve throughput.
To ensure that you have proper switch configuration and the correct switch software for
your DeltaV system, you should purchase switches through normal Emerson channels.
1 - 26
DeltaV Hubs & Switches
Available unmanaged switches for small systems, 12-15 nodes:
• Allied Telesyn AT-FS708, 8-port 10/100Base-TX
• Allied Telesyn AT-FS 709FC, 8-port 10/100Base-TX, 1 Fiber port
• Emerson Media Converter, 4x10/100Base-TX to 1x100Base-FX, Class 1 Div2
Available managed switches, for systems with greater than 15 nodes:
• Cisco Catalyst 2940, 8-port 10/100Base-TX, 1 Fiber port
• Cisco Catalyst 2950-24, 24-port 10/100Base-TX
• Cisco Catalyst Stackable 2950C, 24-port 10/100Base-TX, 2 100Base-FX MTJR
Uplinks
• Cisco Catalyst Stackable 3750-24FS, 24-port 100Base-FX
Gigabit connections are supported only between switches. Connections between
controllers and workstations are 10/100MB.
1 - 27
DeltaV System Power Supply
G Bulk Power Supply
N Power
Distribution
N
Ground DC Return
- +
Pwr
Fault
1
DC Return 2
3
4
5
6
7
8
Bulk Power Supply
System Power Supply

2-Wide I/O Carrier

Power/Controller Carrier
1 - 28
DeltaV Power Supplies
The DeltaV System Power Supply consists of the following options
• System Power Supply (AC/DC) – Input 110VAC or 220VAC
• System Power Supply (Dual DC/DC) – Input 24VDC or 12VDC
The DeltaV Bulk Power Supply consists of the following options
• Bulk AC to 24 VDC Power Supply
• Bulk AC to 12 VDC Power Supply
• Bulk 24 VDC to 12 VDC Power Supply
An Intrinsically Safe Power Supply is available for the Intrinsically Safe I/O
• Intrinsically safe (DC/DC) - Input 24VDC
1 - 29
User Station Hardware
Workstation — Dell Intel Pentium with
• CD-ROM
• Network Interface card(s)
Workstation − for any station type
• One parallel port
• 17/21-inch monitor or 19-inch flat panel
• Dual Monitor Optional
• Four-Monitor Optional
Server — Dell Single or Dual Intel Xeon with
Server − typically used as an
• CD-ROM
Application Station or a
• Network Interface card(s) ProfessionalPLUS on large systems
• One parallel port
• Tape Backup
• RAID 5 (Redundant Array of Independent Drives)
1 - 30
System Capacity
System Sizing
• 120 max. Nodes (redundant nodes count as 1 node)
• 60 max. workstations of any kind
• 1 Professional PLUS Station
• 10 max. Professional Stations
• 59 max. Operator Stations
• 10 max. Application Stations
• 72 max. Remote Workstations
• 8 max. Remote Data Servers (Professional PLUS and 7 Application stations)
• 2 max. Remote clients per Professional PLUS
• 4 max. Remote clients per Operator Station with Windows Server 2003
• 100 max. simplex/redundant Controllers
• 30,000 DSTs
• 750 max DST’s per Controller
• Unlimited SCADA tags
• 15,000 Advanced Unit Management DSTs
1 - 31
Device Signal Tag (DST) Licensing
DST licensing is based on the number of inputs and outputs as follows:
• Analog Output
• Analog Input
• Discrete Output
• Discrete Input
Generally speaking each instrument wired into a set of screw terminals will require 1
DST. When identifying the required DST licensing start with the P&ID and count the
number and type of instruments. The exception would be FOUNDATION fieldbus
devices. Intelligent devices like this can have multiple inputs and outputs per
instrument, resulting in multiple DSTs for a device.
1 - 32
Workstation Licensing
Workstations are licensed based on the functionality required as follows:
• ProfessionalPLUS Station — Configuration, Operation and Configuration
Database node
• Professional Station — Configuration and Operation
• Operator Station — Operation
• Maintenance Station — Diagnostics
• Base Station — Select necessary functionality
• Application Station — Run-time database plus user selected applications. User
applications might be DeltaV Batch software or other third party OPC
applications for interfacing to the plant business systems.
1 - 33
1 - 34
User Station Software Components
The DeltaV User Station Software consists of
• Operate
• Configuration Suite
• Diagnostics
1 - 35
DeltaV Operate
The DeltaV Operate (Run) is used by the operator to view and control the process. It
consists of three items:
• Button Toolbar
• Working Area
• Alarm Banner
DeltaV Operate (Configure) is used to create and edit DeltaV graphics.
Access DeltaV Operate by selecting
Start → DeltaV → Operator → DeltaV Operate Run
1 - 36
DeltaV Operate
DeltaV Operate (Run) Button
Toolbar
Working
Area
Alarm
Banner
1 - 37
DeltaV Operate (Configure)
1 - 38
1 - 39
DeltaV Control Module
P Hierarchy Displays
a
r Alarms
a
m
Conditionals
e
t
e Algorithm Module
r
s I/O
1 - 40
DeltaV Control Module
The DeltaV Control Module contains algorithms that define the control system’s
behavior. The DeltaV Module consists of the following:
• Hierarchy
• Displays
• Alarms
• Conditionals
• Algorithms
• Module
• I/O
• Parameters
1 - 41
1 - 42
DeltaV Configuration Suite
The DeltaV User Station Configuration Suite includes the following:
• DeltaV Explorer
• Control Studio
1 - 43
DeltaV Explorer
Access the DeltaV Explorer by selecting
Start → DeltaV → Engineering → DeltaV Explorer
1 - 44
DeltaV Explorer
The DeltaV Explorer is used to view and edit your system’s configuration. Use the
Explorer’s pull-down menus to perform various DeltaV-related functions or use the
buttons at the top of the DeltaV Explorer window to access other DeltaV programs. Also,
use the plus and minus symbols to expand and collapse the selected item.
Access buttons
Pull-down menus
1 - 45
DeltaV Control Studio
Access the DeltaV Control Studio by selecting
Start → DeltaV → Engineering → Control Studio
1 - 46
A typical DeltaV Control Studio display is shown below.
1 - 47
DeltaV Diagnostics
Access DeltaV Diagnostics by selecting
Start → DeltaV → Operator → Diagnostics
1 - 48
DeltaV Diagnostics
A typical DeltaV Diagnostics display is shown below.
1 - 49
Workshop – Commissioning the Controller
Step 1. Power up the DeltaV Monitor and Workstation. The initial Windows XP
Professional log on window appears in approximately one minute.
Step2. Enter the following information — as prompted — in lower case:
Username: student
Password: dv
Step 3. Click the OK button or press the ENTER key to continue.Wait for DeltaV
Logon window to appear and the hour glass has changed to a selector.
Step 4. Log in to DeltaV using the same User name and Password specified above.
Step 5. Select Windows Desktop from the FlexLock menu bar.
Note: Do not select Windows Desktop until completing the DeltaV Log On.
1 - 50
1 - 51
Decommissioned Controllers
View a list of decommissioned controllers by first launching the DeltaV Explorer
Start → DeltaV → Engineering → DeltaV Explorer
Decommissioned controllers are listed in the Contents window of the DeltaV Explorer
accessed by selecting
Physical Network → Decommissioned Controllers
1 - 52
Decommissioned Controllers
CTLR-00CBA2, shown above, is a decommissioned controller.
Decommissioned State — Controller(s) are non-active members of a Control Network.
For example:
• A new Controller added to the Control Network.
• A replacement for an existing controller (any new controller starts in a
decommissioned state).
• A controller deliberately decommissioned for an extended scheduled shutdown.
Decommissioned State Visual Indicators
Power LED (Green) ON
Error LED (Red) FLASH at one second interval
Active/Standby LED (Green) OFF
Yellow LEDs FLASH at random
1 - 53
Identify Controller
Identify the controller from DeltaV Explorer by selecting
(right mouse button) Decommissioned Controller CTLR-00CBA2 →
(left mouse button) Properties → Flash lights
1 - 54
Identify Controller
Identify State — A specific Controller is located on the DeltaV network. Identify is a
property of the Controller that can be used to located a specific controller when multiple
controllers are part of a DeltaV Network. Identify can be performed on Decommissioned
and Commissioned Controllers.
Identify State Visual Indicators
Power LED (Green) ON
All other LEDs FLASH at one second interval
Note: Automatically terminate the identify state by closing the Identify pop-up dialog
box or selecting Stop Flashing on the controller’s Properties window.
1 - 55
Commissioning a Controller & Auto-Sensing
I/O Cards
Commission a controller and auto-sense the I/O cards from the DeltaV Explorer
by selecting the Decommissioned Controller CTLR-00CBA2 and drag ‘n drop it onto
the Control Network or existing placeholder. A Properties window appears requesting
various information.
Drag ‘n Drop
1 - 56
Commissioning a Controller & Auto-Sensing
I/O Cards
Commission — The act of making a controller an active member of a DeltaV Control
Network. A TCP/IP address is automatically assigned by the ProfessionalPLUS
Workstation at commissioning. This can be performed from the DeltaV Explorer or
Configuration Assistant application. The last step of commissioning will prompt the
user with a question to Auto-Sense I/O cards.
1 - 57
Commissioning a Controller
1 - 58
Define Controller Properties as follows:
• Name: A user-defined name with a maximum of 16 characters containing at
least one alpha character. It may also contain $, -, or _.
• Description: An optional user description of no more than 255 characters
appearing in the DeltaV Explorer. It is for information only and not used by the
controller.
• Associate Alarms & Events with Area: Define the plant area that will be
associated with controller node and subordinate field device alarms.
• Enable System Hardware Alarms: Checking the box ; Enables controller
hardware errors to appear as alarms.
• Enable network redundancy for this node: Checking the box ; Enables the
secondary control network for the node.
1 - 59
• Show integrity error when not in time sync: Checking the box ; Enables an
integrity error on this controller when the time is not synchronized with the
master time server.
• Node is redundant: A Simplex Controller will be grayed out. A checked box ;
indicates the controller is redundant.
1 - 60
Auto-Sensing I/O Cards
When the above fields have been completed, click the OK button to continue. The last
step in commissioning the controller permits you to Auto-sense the I/O cards for the
controller.
Auto-Sense I/O cards — Clicking the YES button causes the controller to scan its I/O
sub-system and identify the card types and carrier slots where the I/O cards are installed.
By clicking the NO button, the controller WILL NOT SCAN the I/O sub-system for
installed I/O cards but will continue to commission itself. Auto-sense can be done at
any time from the DeltaV Explorer.
1 - 61
Cold Restart
Define a cold restart by selecting from the DeltaV Explorer
CTLR → Properties → Controller tab
1 - 62
Cold Restart
In the event of a power failure, the controller can download itself using the
configuration data in non-volatile memory. If the non-volatile memory is not present or
does not match the ProfessionalPLUS database, the system downloads the download
script from the ProfessionalPLUS workstation.
You can set this feature on an individual controller basis using the DeltaV Explorer as
shown above.
The amount of time is set in any combination of Days (0 thru 30 max), Hours (0 thru
23 max) or Minutes (0 thru 59 max). Commissioning and downloading procedures will
be executed if power returns to the controller in less than or equal to the cold restart
time. A setting of 0 disables the Cold Restart (automatic restart).
Note: It is recommended to set the Cold Restart Time to at least two minutes.
1 - 63
Cold Restart
It is further recommended that a UPS be installed between the AC distribution (source)
and the System Power Supply for the controller(s) to ensure controller operations during
short interruptions of plant power.
Note: Refer to Books On Line for additional information about Cold Restart.
Search: Preserving Configuration During Power Loss
1 - 64
DeltaV Explorer Indicators
Access Help by clicking the question mark on the DeltaV

Explorer menu and subsequently clicking on the item of interest.
1 - 65
Workshop – Commissioning the Controller
Commission the decommissioned controller CTLR-XXXXXX from DeltaV Explorer by
performing the following tasks:
Step 1. Identify the Controller using the Identify State.
Step 2. Commission the Controller, name it, enable network redundancy and
Auto-sense I/O.
Step 3. Set Cold Restart to 5 minutes.
1 - 66
1 - 67
PlantWeb Architectural Model
Management Execution (OPC)

Plant-Wide Network
Integrated, Modular Software

DeltaV/AMS
Intelligent Device Manager
Integrated smart SIS

Scalable Platforms
(DeltaV Hardware)
Intelligent Field Devices
1 - 68
PlantWeb Architectural Model
PlantWeb is the proven digital plant architecture that uses the power of predictive
intelligence to improve plant performance.
• Intelligent Field Devices — Can be remotely configured and calibrated via software
using an appropriate host or configurator. Many field devices include PID functions
to allow true distributed control to support the Control Anywhere concept.
• Scalable platforms — The DeltaV host has been designed to manage large amounts
of data. It is equally well suited for small and large applications. The hardware is
easily expanded by adding additional controllers and additional I/O capacity.
• Integrated, modular software (AMS) — A package that allows users to commission,
configure, calibrate, and troubleshoot devices from a Windows Explorer type
screen.
• Management execution — With OLE for Process Control (OPC), data from the
DeltaVsystem can be communicated via the existing business LAN to other
compliant Windows applications such as Excel and Access.
• Integrated smart SIS — TÜV certified for SIL 3 applications, integrated yet
separate.
1 - 69
Summary
You should now be able to define
• DeltaV System architecture
• DeltaV Software components
• DeltaV System capacities
• PlantWeb
1 - 70
The Simulated Process
TM

2-2
Objectives
Upon completion of this module you will be able to
• Define the process to be controlled
• Define the characteristics of the various plant areas
• Define the characteristics of the Device Signal Tags (DSTs)
• Perform a total download
• View diagnostics
2-3
PLANT_AREA_A
Tank101
LEVEL-101
SFC-T101
LI-101
FIC-102
XV-101
MTR-102
= = XVSTAT-101
To Tank201
2-4
PLANT_AREA_A Control Modules
Listed below are PLANT_AREA_A’s control modules:
• LEVEL-101
• LI-101
• XV-101
• XVSTAT-101
• MTR-102
• FIC-102
• SFC-T101 — Sequential Function Chart for automated STARTUP and
SHUTDOWN
• Operator Display — picture named Tank101
2-5
PLANT_AREA_B
Tank201
From Tank101 PLM-SHUTDOWN
LEV2-SIM LIC-20X
FIC-20X
MTR-203
=
2-6
PLANT_AREA_B Control Modules
Listed below are PLANT_AREA_B’s control modules:
• LIC-20X
• FIC-20X
• MTR-203
• LEV2-SIM
• PLM-SHUTDOWN — Phase Logic Module for automated plant shutdown
• Operator Display — picture named Tank201
2-7
Plant Areas
Listed below are the characteristics of a Plant Area.
• Contain control modules
• Define user privilege boundaries
• Define workstation alarms boundaries
Workstation 2
Workstation 1
User 1 User 2
Area A Area B Area C
FIC-101 FIC-201 FIC-301

LIC-101 LIC-201 LIC-301
XV-101 XV-201 XV-301
MTR-101 MTR-201 MTR-301
2-8
2-9
Equipment Hierarchy
n
o
p
q
r
2 - 10
Equipment Hierarchy
DeltaV supports a logical hierarchy which includes the following:
n Area — logical division of a process control system. Areas typically represent plant
locations or main processing functions.
o Process Cell — may be class-based (available to the Batch Executive) or non class-
based. The process cell can be used to organize units and modules.
p Unit Module — allows you to take advantage of advanced alarming techniques.
Units are also key to the Batch Hierarchy.
q Equipment Module — a grouping of equipment that performs a minor task like a
totalizer or header. Allows you to take advantage of advanced alarming techniques.
r Control Module — links I/O, algorithms, conditions displays, and other parameters
to the equipment. Modules typically control a single entity like a motor or flow
loop.
Important: DeltaV Batch requires a full hierarchy of area, cell, and unit to operate
properly.
2 - 11
Equipment Hierarchy
Areas
Building A Building B
Process Cells
Raw Materials Raw Materials
Tank A Tank A
Tank B Tank B
Tank C Tank C
Processing Processing
Line A Line A
Line B Line B
Storage Storage
Tank A Units
Tank A
Tank B Tank B
Tank C Tank C
2 - 12
2 - 13
Device Signal Tags (DSTs)
Card 1 2
Controller AI AO
CH2 CH2
FIC-102 FT-2 FY-2
IO_IN FT-2
IO_OUT FY-2
FT-2 FY-2
2 - 14
Device Signal Tags (DSTs)
DeltaV Device Signal Tags are
• Named items which attach an I/O channel to a control module
• Typically named to match an instrument name
• Define I/O properties such as
– Analog In vs. HART
– DO Latching vs. Momentary
2 - 15
Workshop – Defining Plant Areas
The following workshop requires you to rename
AREA_A as PLANT_AREA_A. From the DeltaV
Explorer select
Control Strategies → AREA_A → Rename
AREA_A appears as a highlighted selection in the
Contents window. Enter the new name
PLANT_AREA_A before pressing the ENTER key.
2 - 16
Workshop – Defining Plant Areas
The following workshop requires you to add
PLANT_AREA_B. From the DeltaV Explorer select
Control Strategies → New Area
AREA1 appears as a highlighted selection in the
Contents window. Enter the new name
PLANT_AREA_B before pressing the ENTER key.
2 - 17
Workshop – Configuring DSTs
2 - 18
Configure DSTs from the DeltaV Explorer by selecting
CTLR → I/O → Card # (CO1) → Channel #(CH01) → Properties
The selected channel’s Properties box appears providing an opportunity for you to enter
the Description, Channel type and Device Tag. Remember to check the ; Enable box to
activate the channel.
Click the OK button to continue.
Note: DSTs can also be configured using the I/O Configuration button on the
DeltaV Explorer.
2 - 19
Configure Cards 1 through 4 as follows:
DST Type DST Type
Card 1 Card 3
Chnl 1 LT-1 Analog Input Chnl 1 LSO-1 Discrete Input
Chnl 2 FT-2 Analog Input Chnl 2 XI-2 Discrete Input
Card 2 Card 4
Chnl 1 LY-1 Analog Output Chnl 1 XV-1 Discrete Output
Chnl 2 FY-2 Analog Output Chnl 2 ZX-2 Discrete Output
2 - 20
2 - 21
Downloads
Download the controller from the DeltaV Explorer by selecting
CTLR → Download → Controller
2 - 22
Total / Full Download
Download — Transfers Controller configuration, setup data and cold restart memory
from the configuration database of the ProfessionalPLUS to the controller(s) and/or
workstation(s) run time database. Downloads are performed from DeltaV Explorer or
Control Studio.
Two Main Types of Downloads
• Total/Full Download — Downloads the entire configuration for the selected
node (controller or workstation). A total/full controller download will download
all control modules assigned to the selected node. Control parameters will go to
configured default values. This download type is performed from DeltaV
Explorer.
Important: It may not be desirable to perform a Total/Full Download on a running
process.
• Partial Download — Downloads only specific parts of the configuration; i.e., a
single control module or card. This only affects the control module or card that is
being downloaded. All partial downloads are performed from the DeltaV
Explorer or Control Studio.
2 - 23
Download Status Indicators
A triangle with a question mark indicates that some of the node’s configuration
database parameters may not match the parameters in the node itself. By selecting
Update Download Status the system will determine if differences exist, resulting in a
blue triangle, if the parameters match, the triangle will disappear.
A blue triangle indicates that some of the node’s configuration database
parameters do not match the parameters in the node itself. If you perform a download,
some changes will be made to the node. If this indicator is not present, no download is
required.
A yellow triangle indicates no configuration.
2 - 24
Download Options
Update Download Status — Updates the download status of the individual Nodes or
Network depending on where it is initiated. Performed from the DeltaV Explorer.
Download Subsets — Configuration data that is not directly related to a control module
or card.
• Setup Data — includes named sets, parameter security, cold restart information,
redundancy information, alarm preferences and event chronicle definitions.
Setup data can be downloaded to Controllers and Workstations. Performed from
DeltaV Explorer.
• Changed Setup Data — Sends only changed setup data items.
2 - 25
Download Options
• Controller Cold Restart Memory — Updates the controller non-volatile memory
so that the Cold Restart download script is valid. Should be performed after any
of the following tasks:
– Controller Upgrade
– Decommissioning and re-commissioning
– Partial download and/or Uploads
Note: Does not affect the working configuration in the controller!
2 - 26
Download Options
• Re-send Last Known Good Download — Sends the last successful total download
to a node without going to the database.
If you have performed a total download followed by one or more partial
downloads, this function resends the information contained in the total download as
well as the partials. For controllers, the function sends the same download script
that would be sent to a controller that restarts after a power failure. This is
especially useful for situations where a workstation fails due to a disk error. It
enables you to bring the new or repaired node up to the previous operational status
without downloading recent edits to the configuration.
Do not use this download function after de-commissioning a controller. Perform a
full download after re-commissioning a controller.
2 - 27
Workshop – Completing the Configuration
You will notice, after configuring the channel,
that a blue triangle with a question mark appears
next to the CTLR, I/O and card listing in the tree.
You must update the download status and/or
download the controller to remove the blue
triangle.
2 - 28
Workshop – Updating the Download Status
Update the Download Status by selecting from the
DeltaV Explorer
CTLR → Update Download Status
The blue triangle will either disappear following
the up-date or will remain; indicating that the
controller must be downloaded.
2 - 29
Workshop – Downloading the Controller
Download the controller by selecting from the
DeltaV Explorer
CTLR → Download → Controller
You will be required to respond to several options
while stepping through the download process.
2 - 30
Verify the configuration download options provides the opportunity to check selected
items for unresolved references and other configuration problems before downloading.
You will be alerted to problems and given the opportunity to resolve them before
continuing with the download.
The cautionary note below gives you the opportunity to abort the controller’s pending
download. Click the Yes button if you wish to continue.
2 - 31
Download Dialogue Box
2 - 32
Download Dialogue Box
The Downloading Selected Objects dialogue box above displays the download’s progress.
The checkmark beside each item indicates that the function is complete. As a specific
event is processing, it is displayed as bold type. Stippled items are events that do not need
to be performed during the current download.
• Creating Log File creates the log file for the download which is stored
on the hard drive. (C or D:\DeltaV\DVData\DownLoadProgress.log)
• Performing Upload Checks verifies values on uploadable items.
• Performing PreDownload Checks determines which items are installable, loaded,
created, licensed and if the user has download privileges.
• Performing Dependency Checks are initiated when Fieldbus devices or modules
with Fieldbus blocks are included.
Click the Close button to continue when the download is complete.
2 - 33
The blue triangles are removed after the download is complete.
2 - 34
Workshop – Checking the System
Launch Diagnostics from the DeltaV Explorer by clicking the Diagnostic button
on the toolbar or by selecting
Start → DeltaV → Operator → Diagnostics
Once Diagnostics has been successfully launched, check out your system.
2 - 35
Summary
You should now be able to
y Define the process to be controlled
y Define the characteristics of the various plant areas
y Define the characteristics of the Device Signal Tags (DSTs)
y Perform a total download
y View diagnostics
2 - 36
DeltaV Control Modules
TM

3-2
Objectives
• Define DeltaV Control Module characteristics
• Create a Discrete Output control module
• Create a Discrete Input control module
• Create a Control display (picture)
• Create Previous and Next display links
• Add Data Links to a display (picture)
• Add Static Objects Text
• Add a Dynamo
3-3
P Hierarchy Displays
a
r Alarms
a
m
Conditionals
e
t
e Algorithm Module
r
s I/O
3-4
DeltaV Control Modules exhibit the following characteristics:
• Unique name — 16 characters maximum with one alpha, alphanumeric, $, -, or_
• Executes control algorithms
• Smallest entity that may be downloaded to the controller
• Flexible size
• May be independently taken out of service
• Independent scan rate per module
• References a primary, detail and faceplate display
• Independent function block scan rate, execute block every (1-255) module scan(s)
• Set function block execution order, automatically or manually
3-5
Parameter Path
Module FIC-20X Function Block PID1
Parameter OUT
3-6
Parameter Path
The parameter path is Data Server.Module/Block/Parameter.Type_Field
For example:
DVSYS.FIC-20X/PID1/OUT.F_CV
• Data Server — The Workstation’s data server that provides real-time data to
DeltaV Operate.
• Control Module — a control algorithm that links conditions, alarms, displays and
other characteristics together for a particular piece of equipment.
• Function Block — contains standard process control algorithms such as PID,
Analog Out and Analog In. When wired together in an appropriate and logical
sequence, multiple function blocks form a control module.
• Parameter — data transmitted between function blocks for trending, alarming,
diagnostics and advanced process control.
• Type — parameter types are Floating (F) for numbers and ASCII (A) for text.
Floating is the default parameter.
• Field — the most common fields are Current Value (CV) and Status (ST).
3-7
Module Templates
Module Templates may be used as a starting point for
modules. Access DeltaV Module Templates by selecting
Start → DeltaV → Engineering → DeltaV Explorer →
Library → Module Templates
3-8
Control Studio is used to define and modify control modules. Launch Control Studio
from DeltaV Explorer by clicking the Control Studio button
Or from the Task bar by selecting
Start → DeltaV → Engineering → Control Studio
3-9
1 3
4 5
3 - 10
1 Hierarchy View — Displays the contents of the Function Block diagram or
Sequential Function Chart.
2 Diagram View — The working area where you build control strategies for the
control module.
3 Palette — The selectable window containing different function blocks,
parameters and custom blocks used to build control strategies for the control
module.
4 Parameter View — The window displays module level parameters or function
block parameters when a function block is selected.
5 Alarm View — The area in which pre-defined alarms or user-created alarms will
be created and displayed.
3 - 11
Workshop – Creating Module XV-101
DO
CTLR
XV-101
XV-1
= =
3 - 12
Workshop – Creating Module XV-101
This workshop requires that you perform the following tasks:
Task 1. Define a new Discrete Output control module
Task 2. Download the Control Module
3 - 13
Defining a Discrete Output Module
Using the Control Studio, create the new Control module XV-101 in the following
manner:
Step 1. Right click on Plant_Area_A → New → Control Module. Enter XV-101 as

the Object name.
Step 2. Right click on XV-101 → Open→ Open with Control Studio.
Step 3. Drag ‘n drop Discrete Output from the IO palette.
Step 4. Double click Filtered by: in the parameter window.
Step 5. Check Quick Configuration and Common Configuration.
3 - 14
Defining a Discrete Output Module
Step 6. Modify IO_OUT to use the DST XV-1.
Step 7. Modify the Mode parameter. Change Target from Cascade to Auto.
Step 8. Select the button to assign the control module to CTLR.
Step 9. Select the button to modify the module properties primary control
display Tank101
Step 10. Select the button to save the module.
Step 11. Download the control module from the Control Studio window.
Step 12. Select the button for the on-line view.
Step 13. Select the DO function block.
Step 14. Change the SP_D parameter to 1 and verify that Card 4 Channel 1 is on.
3 - 15
Workshop – Creating Module XVSTAT-101
DI
CTLR
XVSTAT-101
= = LSO-1
3 - 16
Workshop – Creating Module XVSTAT-101
Task 1. Copy a module template from the library
Task 2. Define a Discrete Input module
3 - 17
Defining a Discrete Input Module
Use the DeltaV Explorer to create the new module XVSTAT-101 in the following manner:
Step 1. From the DeltaV Explorer select
Library → Module Templates → Monitoring
Step 2. Drag ‘n drop the DISCRETE Module Template from the Library to
PLANT_AREA_A
Step 3. Rename the module XVSTAT-101
Step 4. Launch the Control Studio by selecting
XVSTAT-101 → Open → Open with Control Studio
3 - 18
Defining a Discrete Input Module
Step 5. Modify XVSTAT-101 as follows:
a. Modify IO_IN to use DST LSO-1
b. Modify the Discrete Alarm to alarm on a value of 0
c. Select the button to assign to your controller
d. Select the button to modify Module Properties displays Primary

control to Tank101
e. Select the button to save
f. Select the button to download the module to the controller
g. Select the button and verify that XVSTAT-101 works
3 - 19
DeltaV Operate (Run)
Launch DeltaV Operate (Run) by selecting the button.

3 - 20
Open the DeltaV Operate (Configure) by clicking the button on the DeltaV
Explorer.
Or, from DeltaV Operate (Run), right click and select Quick Edit and enter DeltaV
Operate (Configure).
3 - 21
Button
Bars
Tool
Box
Work
Area
System
Tree
3 - 22
DeltaV Operate
Operate Modes
• Configure — used during the picture configuration process
• Run — used to run the Operator Interface
System Tree
• Shows the files associated with the project
• Shows objects associated with each file
• Can be resized, moved or not displayed
Work Area
• Contains the current active picture/document
Menu Bar/Tool Bars
• Contains tools and menu selections that allow the user to manipulate the current
document
3 - 23
Creating a New Picture
New Picture from template
3 - 24
Pictures created using the

main template have objects
already on them.
3 - 25
Each object in the illustration on the previous page has other objects grouped with it. To
see the other objects, click on the plus symbol (+) next to the object in the System Tree.
Selecting an object, or a group of objects, will select that object on the picture.
3 - 26
New Picture Objects
3 - 27
Object Terminology
• Object — Comprised of data and procedures that are treated as a unit
– Rectangle
• Properties — Characteristics of an object
– Color
– Size
– Fill
• Methods — Subroutines that effect the behavior of an object
− Scaling
− Moving
• Events — Actions, initiated by the user, program or the system, which the object
recognizes
− Mouse Click
− Timers Expire
− Values Change
3 - 28
Workshop – Creating a New Picture
This workshop requires you to define a display with Previous and Next navigation.
3 - 29
The following steps you through the creation of operator display Tank101:
Step 1. Launch DeltaV Operate by selecting the button from the Explorer
window.
Step 2. Switch to DeltaV Operate (Configure) by pressing CTRL-W.
Step 3. Select the DeltaV tool bar’s New Picture button. Select the main template and
specify Tank101 as the Picture Name. Click OK to continue.
Step 4. Select Edit/Picture... and make the following change
Background Color: Select a color of your choice from the dialog box’s color
pallet
Step 5. Select the text in the middle of the picture and delete it.
3 - 30
Step 6. Double click on the Previous/Next buttons. The Previous/Next Picture dialog
box shown above appears. Enter the following Previous and Next Picture
names.
Previous Picture Name: Ovw_ref.grf
Next Picture name: alarmList.grf
Click OK to continue.
Step 7. Save Tank101.
3 - 31
Datalink
Add a datalink to a picture by clicking the Datalink Stamper button in the
DeltaV_ToolBox. The Datalink dialog box appears.
Open the Expression Builder / Browser by clicking the browse (ellipsis) button next to
the source field on the Datalink dialog.
3 - 32
Datalink
• Source — Used to specify the source of the datalink information
– Can be typed in, selected from the most recently used list, or browsed for
using the browse button
• Data Entry — Used to specify if data entry is allowed on the datalink
– Options — NONE / IN-PLACE
– Confirm is used to confirm the data write
• Error Configuration — Used to specify how errors are handled by the datalink
– Use Error Table
– Use Current Output - DO NOT USE!
• Formatting — Used to specify the format for the datalink on the picture
– Type — Alpha-Numeric / Numeric is automatically selected based on the
data format (A / F) of the datalink
– Lines / Characters/Line — Specifies the field width and display format
3 - 33
Expression Builder / Browser
3 - 34
Click the Browse DeltaV Control Parameters button to launch the DeltaV database
browser. The browser will allow you to select the appropriate parameter path to be
displayed in the following format:
DVSYS.MODULE/BLOCK/PARAMETER.TYPE_FIELD
Example - DVSYS.XV-101/DO1/SP_D.F_CV
The Help on Display Parameters button lists additional Workstation display parameters
that are not Control Module parameters. For example,
DVSYS.THISUSER/USERNAME.A_CV
identifies the current user logged onto the DeltaV Workstation.
The Refresh Rate specifies how often data on the operator display is refreshed.
Remember to set the refresh rate to a realistic value.
3 - 35
1 2 3 4
3 - 36
1 FIX Database
– Browse to key Workstation parameters
– Expression window
à Enter the parameter path/expression
à Use the Browser to create the parameter path/expression
à Use Mathematical Functions in the expression
2 Pictures
– Browse for information on any open picture (Not recommended)
3 Globals
– Browse for information stored in Globals
4 Data Servers
– Browse for information available from other configured data servers; i.e., OPC
3 - 37
Workshop – Adding a Datalink
Step 1. With picture Tank101 open, select the Datalink Stamper button from the
DeltaV_ToolBox.
Step 2. When the Datalink dialog opens, select the ellipsis button to start the Expression
Builder.
Step 3. When the Expression Builder opens, select the DeltaV tab and click on
the Browse DeltaV Control Parameters button to start the browser.
Step 4. Browse to XV-101/DO1/SP_D.F_CV. Check the Refresh Rate. Click OK to
continue.
Step 5. In the Data Entry portion of the dialog, change the Type from None to In-Place.
3 - 38
Workshop – Adding a Datalink
Step 6. Check the format information to make sure the display format is acceptable and
click OK.
Step 7. Move the stamper to the desired position and click the left mouse button to
complete.
Step 8. Modify the color of the datalink as necessary from the menu bar by selecting
View → Color Selections.
Step 9. Add a datalink for XVSTAT-101/DI1/PV_D.F_CV. Remember to check the
Refresh Rate.
3 - 39
Workshop – Creating Static Objects / Text
The following steps permit you to add text to identify your datalinks.
Step 1. Select the Text button from DeltaV_ToolBox and click on the picture
where the text is to be placed. Begin typing the text. When done typing, click
on another object or on an open area of the picture.
Step 2. Modify the color of the text by selecting
View → Color Selections
from the menu bar and select the desired color.
Step 3. Modify the text, as illustrated below, by selecting the text on the picture
before selecting
View → Property Window
from the menu bar and changing the window’s Caption property
3 - 40
3 - 41
Step 4. Another option to modify the text would be to use the Text Caption Editor
button from the DeltaV_ToolBox.
Step 5. Select the text to be modified, click on the button, modify the selected text,
and click on Write Caption. To modify other text fields, select the field, click
on Read Caption, make the modifications and click on Write Caption. Click
Close when done.
3 - 42
Step 6. If you wish to modify the text’s font, select the text, right click and select Font
from the pop-up list. The Font dialog box appears.
3 - 43
Step 7. An alternative method of modifying text is to select the text, open the property
window and modify the FontName, FontSize and FontStyle properties for the
text object.
3 - 44
3 - 45
Dynamos
A Dynamo is a group of objects that represent a
graphic object such as a pump, valve or transmitter.
Some dynamo objects have dynamic properties built
into them. Dynamos are grouped and stored in
dynamo sets as shown below.
3 - 46
Dynamos
Dynamos with dynamic properties are typically stored in dynamo sets with the Anim
suffix, for example PumpsAnim. Other dynamo sets with dynamic properties have
specific purposes as listed below:
• AGA — AGA function block dynamos
• frsAdvCFncblk — Advanced control function block dynamos
• frsFncblk — Function block dynamos, allows referencing any block name
• frsModGrp — Dynamo to create group displays
• frsModules — Dynamos for various module templates in the DeltaV database
• frsPopups — Pop up window controls
• frsValves_Xmit — Various FRSI valves and transmitters
3 - 47
Workshop – Adding a Dynamo
The following permits you to add a dynamo to your picture.
Step 1. Expand Dynamo Sets in the System Tree. Double click
on Valves2 to display the valve selections in Valves2.fds.
Step 2. Expand Valves2 and select the Valve17 and drag it onto
the picture.
3 - 48
Workshop – Adding a Dynamo
Step 3. Save your picture.
Step 4. Select File→ Close to close Tank101.
Step 5. Open Ovw_ref and modify Next Picture to be Tank101.
Step 6. Save Ovw_ref.
3 - 49
Workshop – Operating & Verifying
Verify the operation of the module XV-101 and monitor XVSTAT-101 in the following
manner:
Step 1. Select Window → Close All to close all open pictures and dynamo sets.
Step 2. Launch DeltaV Operate (Run) by selecting from the menu bar
Workspace → Switch to Run
Step 3. Open Tank101 by selecting the Open Main Display button. Scroll down
and select Tank101 and press the Enter button.
Step 4. Verify that XV-101’s output manipulates XVSTAT-101’s input.
Step 5. Verify the alarm on XVSTAT-101.
Step 6. Verify Previous and Next Picture navigation.
3 - 50
Summary
• Define DeltaV Control Module characteristics
• Create a Discrete Output control module
• Create a Discrete Input control module
• Create a Control display (picture)
• Create Previous and Next display links
• Add Data Links to a display (picture)
• Add Static Objects Text
• Add a Dynamo
3 - 51
3 - 52
Configuring DeltaV Alarms
TM

4-2
Objectives
• Define basic alarm characteristics
• Create an Analog Output module
• Define cold restart behavior of parameters
• Define partial download behavior of parameters and critical block values
• Create an Analog Input module
• Utilize Visibility and Data Entry Experts
• Create a tank graphic using a Dynamo
• Define detailed alarm characteristics
• Define the Event Chronicle
4-3
DeltaV Alarms
A module created from a Module Template

may include pre-assigned alarm(s).
4-4
DeltaV Alarms
Right click a selected function block to assign an alarm.
4-5
DeltaV Alarms
DeltaV Alarms
• Represent a Boolean evaluation of a pre-defined process state. For example,
LI-101 > 950
• Are specific to a module. For example, LI-101/HI_ALM.A_CV
Access DeltaV Alarms from the DeltaV Control Studio by selecting
File → Open → LI-101 (module name)
4-6
4-7
Workshop – Creating Analog Modules &
Defining Analog Alarms
This workshop requires you to perform the following tasks:
Task 1. Create an Analog Output control module.
Task 2. Create an Analog Input control module.
Task 3. Define Analog alarms.
Task 4. Add a tank Dynamo.
4-8
Defining the Analog Output Module
AO
CTRL1
LEVEL-101
LY-1
= =
4-9
Defining the Analog Output Module
Use the Control Studio to create a new Analog Output module LEVEL-101 in the
following manner:
Step 1. Drag ‘n drop Analog Output from the IO palette
Step 2. Select the Parameter Window and modify the following
IO_OUT to DST LY-1 AO
PV_SCALE 0-1000 gal SP Cas_In
SP_HI_LIM 1000
SP_LO_LIM 0
Step 3. Drag ‘n drop Input Parameter from the Special Items palette and name the
parameter SP. The parameter type is Floating Point.
Step 4. Connect the SP parameter to Cas_In on the AO function block.
Step 5. Select the button to assign to controller .
Step 6. Select the button to modify properties and the button to save.
Step 7. Select the button to download controller.
4 - 10
Promoting a Parameter
By promoting a parameter, a parameter is elevated to a higher level in the function
block diagram thereby shortening the parameter path. The means by which a parameter
is promoted is contained in Steps 3 and 4 of the Analog Output Module Workshop
above.
This — LEVEL-101/SP.F_CV
Mode =CAS
SP
Instead of this — LEVEL-101/AO1/SP.F_CV

Mode = AUTO
SP
4 - 11
Restore Parameter Value After Restart
The Default Value for SP below is 500 which will set the SP to 500 on a Cold Restart of
the controller. However, you may not want the default value applied on Cold Restart of
the controller. By checking the parameter’s Restore parameter value after restart and
the module level Restore parameter values after restart the current operating value will
be stored in NVM and restored on a Cold Restart.
4 - 12
Parameter Download Behavior
Module Properties also allow you to define the partial download behavior of a module.
This applies to two types of parameters, user-defined (SP) and critical block parameters.
A sample of critical block parameters is shown below. A complete table of critical block
parameters can be found in BOL, by searching the phrase “downloading data”.
Partial Download (Mode) critical block value (SP) user-defined

behavior
Configuration database CAS 500
On-line Value AUTO 555
Preserve critical block AUTO 500

values
Preserve user-defined and AUTO 555

critical block values
Use configured values CAS 500
4 - 13
Using Analog Module Templates
AI
CTRL1
LI-101
LT-1
= =
4 - 14
Using Analog Module Templates
Use Analog Module templates to monitor Analog Input in the following manner:
Step 1. Using the DeltaV Explorer, drag ‘n drop the Monitoring - ANALOG Module
Template from the Library to PLANT_AREA_A
Step 2. Rename the module LI-101
Step 3. Launch Control Studio and modify the module as follows:
a. Modify IO_IN to use DST LT-1
b. Modify OUT_SCALE 0-1000 gal
c. Modify HI_ALM limit to 950
d. Modify LO_ALM limit to 100
e. Assign to the controller and modify the primary display to TANK101
f. Save the module
g. Download the module to the controller
4 - 15
Modifying the Operator Display
Add LI-101 and LEVEL-101 to the Tank101 display in the following manner:
Step 1. Launch the DeltaV Operate (Configure) application and open the Tank101
display
Step 2. Add the Data Link LI-101/AI1/PV.F_CV.
Step 3. Add another datalink to your picture for LEVEL-101/SP.F_CV.
Step 4. On the Datalink dialog leave the Data Entry set to None and click OK.
Step 5. With the new datalink selected on the picture, click on the Data Entry Expert
button in the DeltaV_ToolBox.
4 - 16
Step 6. When the Data Entry Expert dialog
box appears, choose the
Numeric/Alpha tab from the Entry
Method frame, select Numeric Entry,
uncheck Fetch Limits from the Data
Source and set the limits to 0 - 1000.
Click OK to continue.
Step 7. Modify the color of the datalink as
necessary.
4 - 17
Step 8. Add a Tank from the dynamo set Tanks.
Step 9. Add a rectangle to the picture using the rectangle button from the
DeltaV_ToolBox.
Step 10. Right click on the rectangle and select color to choose a foreground /
background color.
Step 11. Select the rectangle and right click to select Animations from the pop-up
window. Check the Fill Percentage box on the basic animation dialog.
4 - 18
Step 12. Modify the Data Source to point to the module LI-101 and parameter PV.
Step 13. Check the Vertical Direction and Fetch Limits from Data Source box.
Step 14. Save the picture.
Important: Remember to close all pictures and dynamo sets.
4 - 19
Operating the Analog Module
Operate LEVEL-101 and monitor LI-101 in the following manner:
Step 1. Run the DeltaV Operate application
Step 2. Verify LEVEL-101 output manipulates LI-101 input
Note: Alarms occurring on LI-101 can be acknowledged by selecting the Acknowledge
button on LI-101’s faceplate.
4 - 20
4 - 21
DeltaV Alarm Priorities
DeltaV Alarm Priorities:
• Indicate importance of an alarm
• Affect the order alarms appear in the Alarm Banner and the Alarm List pictures
in DeltaV Operate
• Maximum of 12 alarm priority levels, numeric values ranging from 4 (lowest) to
15 (highest), and a log only priority level of 3.
4 - 22
DeltaV Default Alarms
CRITICAL (15) WARNING (11) ADVISORY (7)
• Time stamped in the controller
• Included in the list of highest priority alarms
• One to five alarms appear on the Alarm Banner
• May cause alarm audible at the Workstation
• Generate alarm records in the Event Chronicle
• Capture a maximum of two parameters
LOG (3)
• Generate event records in the Event Chronicle
• Capture up to two parameters
4 - 23
DeltaV Alarm Ranking
DeltaV Alarms are prioritized in the following manner:
y Unacknowledged alarms are more important than acknowledged alarms
y Alarms with equal acknowledgment status — Active alarms are more important
than inactive alarms
y Alarms with equal acknowledgement status and active status — alarms with
higher priority (numeric) values have the greatest importance.
y Alarms with equal acknowledgement status, active status and priority value —
NEWER alarms (i.e., alarms with more recent time stamps) are more important
than OLDER alarms.
4 - 24
4 - 25
DeltaV Alarm List Display
DeltaV Operate provides an alarm list display which consists of an ActiveX object
called an alarm summary. The alarm list display is accessed by clicking the bell
icon.
4 - 26
DeltaV Alarm Summary
The following are valid Alarm Fields which may appear in the DeltaV Alarm Summary.
• Ack • Node
• Alarm • Param
• Area • Part of
• Category • Priority
• Description • Time In
• Message • Time Last
• Module • Unit
• Module/Param • Zone
4 - 27
DeltaV Explorer Alarm Priorities
Access the DeltaV Alarm Priorities definition from the DeltaV Explorer by selecting:
System Configuration → Setup → Alarm Preferences → Alarm Priorities →
Alarm Priorities (i.e., Advisory) → Properties
4 - 28
DeltaV Explorer Alarm Priorities
• Value — Determines the priority value of the
alarm.
• Auto Acknowledge New Alarms —
Determines if the alarm is automatically
acknowledged at the time the alarm is
detected.
• Auto Acknowledge When Inactive —
Determines if the alarm is automatically
acknowledged when the condition causing
the alarm clears.
• Alarm Banner Shows — Determines when
the alarm is displayed in the Alarm banner.
The choices are Not Hidden, Module or
Unit/Equipment Module.
• Wave File — Determines the sound
associated with active alarms of this priority.
4 - 29
DeltaV Explorer Alarm Types
Access the DeltaV Alarm Types definition from the DeltaV Explorer by selecting
System Configuration → Setup → Alarm Preferences → Alarm Types →
Alarm Type (i.e.,High Alarm) → Properties
4 - 30
Alarm Type Properties
The Alarm Types Properties form defines alarm characteristics by alarm type. For
example, all high alarms use the alarm word HIGH for the operator display.
The Alarm Types Properties form is also used to
• Modify existing alarm properties
• Add new alarm types
A maximum of 255 alarm types may be added and defined.
• Alarm Word appears in the DeltaV Operate when the alarm is active or
unacknowledged.
• Category appears in the Event Chronicle for every alarm state change.
• Message appears in the standard Alarm List picture. The alarm message is
defined as the description field. It is also logged in the Event Chronicle.
4 - 31
Configured from the DeltaV Explorer,
Alarm Type Properties define each
alarm’s individual characteristics.
4 - 32
Note: Parameter 1 (%P1) and Parameter 2 (%P2)
are established when an Alarm is associated with
an alarm on a function block.
4 - 33
DeltaV Alarm Fields
Field R/W A_ASCI F_FLOAT
CUALM Current Alarm R OK/HIGH 0/16
LAALM Latched Alarm R OK/HIGH 0/16
CV Same as LAALM R OK/HIGH 0/16
NALM New Unacknowledged R/W NO/YES 0/1
PRI Priority R/W CRITICAL . . . LOG 15 . . . 3
ENAB Enabled R/W NO/YES 0/1
INV Invert Input R/W NO/YES 0/1
OPSUP Alarm Suppression R/W NO/YES 0/1
SUPTMO Suppression Timeout R/W Time(minutes) Time(minutes)
SUPTMR Suppression Timer R/W Time(minutes) Time(minutes)
Display example: Module/Alarm.Format_Field

LI-101/HI_ALM.A_CV
4 - 34
DeltaV Alarm Fields ALARM_HYS = 0
Acknowledge Acknowledge
HI_LIM
PV
16 HIGH
CUALM
0 OK
16 HIGH
LAALM
0 OK
1 YES
NALM
0 NO
4 - 35
Default Alarm Type Floating Point Values
DeltaV Alarm Types F_Float DeltaV Alarm Types F_Float

Discrete Device 1 Change From Normal 11
Communication Error 2 Change of State 12
Open Circuit Detected 3 High High Alarm 13
General I/O Failure 4 Low Low Alarm 14
Floating Point Error 5 Rate of Change 15
Over Range 6 High Alarm 16
Under Range 7 Low Alarm 17
Statistical Error 8 Deviation Alarm 18
New Alarm 9 Adapt Alarm Active 254
Any Alarm 10 Inspect Limit Active 255
4 - 36
4 - 37
Workshop – Modifying the Operator Display
display
Step 2. Add the following Data Links:
LI-101/HI_ALM.A_CV
LI-101/LO_ALM.A_CV
Step 3. Save and close the display.
4 - 38
Operating the Analog Module
Step 1. Run the DeltaV Operate application
Step 2. Verify that LI-101’s HIGH and LOW alarms function properly
Note: Now that alarm data links have been added to the display, the alarms can be
acknowledged by selecting the acknowledge button on the alarm banner.
4 - 39
ALARMS[1-5] Parameter
The ALARMS[1] parameter will Field A_(ASCII) F_(FLOAT)
display the highest priority alarm
LAALM OK 0
that is active for a given module.
LOW 17
For example: HIGH 16
LI-101/ALARMS[1].A_LAALM
CUALM OK 0
LOW 17
HIGH 16
NALM NO 0
YES 1
PRI CRITICAL 15
WARNING 11
ADVISORY 7
ATTR ALARM NAME N/A
TIN Tue Jan 29, 2002 N/A
14:22:05:.22
4 - 40
ALARMS[1-5] Parameter
Picture Configuration Data Displayed

LI-101/ALARMS[1].A_LAALM HIHI
A_NALM NO
A_PRI CRITICAL
A_ATTR HI_HI_ALM
A_TIN Tue Mar 20, 2007 21:05:03.57
LI-101/ALARMS[2].A_LAALM HIGH
A_NALM NO
A_PRI WARNING
A_ATTR HI_ALM
A_TIN Tue Mar 20, 2007 21:05:03.45
4 - 41
ALARMS Control Fields
ALARMS.F_MACK — Module Ack
• Setting to a 1 or YES causes all Alarms in the module to be acknowledged
• Immediately returns to 0
ALARMS.F_ENAB — Module Alarm Enable
• Setting to a 0 or NO causes all Alarms to be disabled
ALARMS.F_PRIAD — Module Priority Adjustment
• Adjusts the effective priority of all alarms in the module (0 . . . 12)
• Setting to a 0 causes alarms to be treated as pre-configured priority
4 - 42
4 - 43
Workstation Alarm Consolidation
Workstations maintain a list of the most important alarms for display in the Alarm
Banner for THISUSER.
Alarms qualify for the Workstation Alarm Banner by being in an eligible Plant Area
which includes:
• Plant Area configured as part of this workstation’s Alarms and Events Subsystem
• Plant Area where current user is granted any attribute security write keys
For example:
• Areas in this node’s Alarms and Events subsystem A B C D
• Areas in which user has write privileges CDEF
• Areas in which alarms are consolidated CD
4 - 44
Workstation Alarm Consolidation
User
Area A Area B Area C Area D Area E Area F

FIC-101 FIC-201 FIC-301 FIC-401 FIC-501 FIC-601
LIC-101 LIC-201 LIC-301 LIC-401 LIC-501 LIC-601
XV-101 XV-201 XV-301 XV-401 XV-501 XV-601
4 - 45
Alarms by Plant Area
Alarms, grouped by plant area, exhibit the following:
• Every Alarm parameter is part of a Module
• Every Module is assigned to a Plant Area
• Each Workstation informs each controller of the list of Plant Areas in which it is
listening for alarms
• Every state change detected in an alarm parameter generates an event occurrence
record which is sent to Workstations which are listening for alarms in that
specific plant area
• Workstations maintain a list of active alarms, ordered by importance, from the
event occurrence records they receive
4 - 46
Additional Alarm Parameters
DVSYS.THISUSER/ALARMS[1-100]
• Provides top one hundred Alarms for this user
• Valid fields LAALM, MODULE, CV, NALM, PRI, ATTR, TIN
DVSYS.AREA/ALARMS[1-50]
• Provides top fifty Alarms for this area
• Valid fields LAALM, MODULE, CV, NALM, PRI, ATTR, TIN
Refer to Help on Display Parameters when adding data links for a more complete list of
parameters.
4 - 47
DeltaV Event Chronicle Time stamped in the controller
4 - 48
DeltaV Event Chronicle
The Event Chronicle is a journal of system, process and user events associated with a
workstation and its associated areas.
Access the DeltaV Event Chronicle by selecting the Process History View button
in DeltaV Operate. Or, access the DeltaV Event Chronicle by selecting:
Start → DeltaV → Operator → Process History View → Event
4 - 49
DeltaV Event Chronicle Properties – General
4 - 50
DeltaV Event Chronicle Properties – General
Access the DeltaV Event Chronicle from the DeltaV Explorer by selecting:
Physical Network → Control Network → Workstation→
Alarms And Events→ Properties
• Enable Event Chronicle — Check to establish an Event Chronicle for this
workstation. After downloading the workstation node, the Event Chronicle
begins capturing system, user and process events associated with the
workstation.
• System SOE Collector — Check to establish this node as the system wide SOE
collector.
• Name — Name of the Event Chronicle for this workstation.
4 - 51
display.
Step 2. Delete the HI_ALM and LO_ALM data links on the display.
Step 3. Add the Data Link LI-101/ALARMS[1].A_LAALM.
4 - 52
Step 4. Select the alarm datalink and click the Visibility Expert button from
DeltaV_Toolbox.
Note: Experts simplify the task of adding animation to an object.
Step 5. Set the Data Source to LI-101/ALARMS[1].F_LAALM.
Step 6. Set the condition so that the datalink is visible only when an alarm is active.
Step 7. Close all dialogs and return to the picture.
Step 8. Save Tank101 display.
4 - 53
Workshop – Operating the Analog Module
Step 1. Run the DeltaV Operate application.
Step 2. Verify that LI-101/ALARMS[1].A_LAALM functions properly.
Step 3. Verify that the Event Chronicle is logging alarms and events.
4 - 54
4 - 55
Optional Exercise
Create a custom alarm with an advisory priority and an alarm word of Unsafe
Practice. The alarm will advise the operator of impending danger if LI-101 is greater
than 900 gallons and XVSTAT-101 is closed for more than 20 seconds.
Hints:
1. Create a new alarm type
2. Use a condition block
3. Right click the alarm area in LI-101 to create a custom alarm
Operate View
Process History View
4 - 56
Summary
• Define basic alarm characteristics
• Create an Analog Output module
• Define cold restart behavior of parameters
• Define partial download behavior of parameters and critical block values
• Create an Analog Input module
• Utilize Visibility and Data Entry Experts
• Create a tank graphic using a Dynamo
• Define detailed alarm characteristics
• Define the Event Chronicle
4 - 57
4 - 58
DeltaV Motor Control
TM

5-2
Objectives
• Identify the appropriate module template for motor control
• Define state masks
• Define named sets
• Define device options
• Define condition expressions
5-3
Module MTR-102
DI DO
CTLR
MTR-102
XI-2
= =
ZX-2
5-4
Motor-2 State Templates
Access the DeltaV’s two state motors from the DeltaV Explorer by selecting
Library → Module Templates → Motors-2State
5-5
MTR-11_ILOCK
The driving force behind motor control is the Device Control block (DC). The parameter
window, shown above, displays the DC block’s common configuration parameters.
Selecting STATE_MASKS above displays the STATE_MASKS Properties box shown
below.
5-6
State Masks
The STATE_MASKS Properties dialog box
can be modified to meet specific operating
requirements.
Empty = 0 value on I/O channel
Check mark = 1 value on I/O
channel
Stippled check mark light gray
background = don’t care
Stippled check mark dark gray
background = not available
• Passive: = 0 in named set
• Active1: = 1 in named set
5-7
Named Sets
Access the Named Set Properties: mtr2-sp dialog box from DeltaV Explorer by selecting
Setup → Named Sets
Not all default Named Sets can be modified. However, new Named Sets can be created if
needed.
5-8
SP_D Parameter
Selecting the SP_D properties for the DC block allows you to browse for the available
named sets. The names in the named set will become the set point names for your DC
block.
5-9
Device Options
Modify the DeltaV Device Options properties for the Device Control (DC) block so that it
satisfies the process’ control strategy and the operation’s safety requirements.
5 - 10
Interlocking
Interlocking is provided by the use of condition blocks for Expression evaluation. The
Boolean Fan Input (BFI) block provides a first out trap for operator indication and the
OR block provides operator indication of bypassed conditions.
5 - 11
Workshop – Creating a Motor Control Module
DI DO
CTLR
MTR-102
XI-2
= =
ZX-2
5 - 12
Task 1. Create the motor control module MTR-102 using a module template
Task 2. Define interlocks
Task 3. Display a pump dynamo
Task 4. Create Datalinks and add Expert functionality
5 - 13
Create motor control module MTR-102 in the following manner:
Step 1. From the DeltaV Explorer, drag ‘n drop the MTR-11_ILOCK template from
the Library to PLANT_AREA_A.
Step 2. Rename the module MTR-102.
Step 3. Launch the Control Studio and modify the module as indicated below:
I/O IO_IN_1 XI-2 Card 3 Channel 2
IO_OUT_1 ZX-2 Card 4 Channel 2
Device_Opts Passive on Active Timeout
Passive when confirmed
Trip
5 Reset required
5 Permissive
SP Track
5 Interlock
5 - 14
Step 4. Provide Permissive and Interlock conditions
Block DESC Time_Duration Expression
CND1 XVSTAT-101 is closed ‘//XVSTAT-101/DI1/PV_D’=0
CND2 Tank101 level is <50 4 Secs ‘//LI-101/AI1/PV’<50
Step 5. Assign the module to the controller.

Step 6. Select the button to modify module properties primary display Tank101
and modify Detail to match the number of defined condition blocks.
Step 7. Select the button to save and the button to download the module.
Note: Search Books On-line for “Using Profibus DP, DeviceNET, and AS-Interface with
DeltaV Functions Blocks” for special considerations with the DC block.
5 - 15
Workshop – Modifying an Operator Display
Modify the operator display by adding motor control module MTR-102 to the Tank101
display in the following manner:
display.
Step 2. Add Datalinks with the following characteristics:
MTR-102/DC1/PV_D.A_CV
MTR-102/DC1/SP_D.A_CV (Data Entry Expert/Multi-Item Select)
MTR-102/ALARMS[1].A_LAALM (Visible only when an alarm is active)
Step 3. Add the Dynamo PumpAnimC1 from Dynamo set PumpsAnim
5 - 16
Step 4. Animate the pump’s color by checking ; the Animate Pump Color or clicking
the Color button on the Pump Dynamo dialog box. The Color By dialog box
appears.
5 - 17
Step 5. Enter the following parameters in the Color By dialog box shown above.
Data Source: MTR-102/DC1/PV_D.F_CV
Color By: Current Value
Color Threshold: Exact Match
Value: 0 Color: White
Value: 1 Color: Yellow
Step 6. Save the display.
5 - 18
Workshop – Operating the Motor Control Module
Verify the operation of motor control module MTR-102 in the following manner:
Step 2. Energize (open) XV-101.
Step 3. Fill Tank101 to 500 gallons.
Step 4. Verify that motor control module MTR-102 is operating properly by
manipulating the SP_D.
Step 5. De-energize (close) XV-101 and verify that the interlock occurs.
Step 6. Adjust Tank101’s level to 10 gallons and verify that the interlock occurs.
5 - 19
Optional Exercise
Create a new module named XV-OPTION. This valve will be controlled with a
device control block. This is the typical way to control Open/Close valves as compared
to the training example seen earlier with XV-101 and XV-STAT using a DO and DI
block respectively. The process engineer has also requested that the Setpoint names
should be Flush(1) and Hold(0). The Process Variable names should be Flushing(1)
and Holding(0). DeltaV Operate View
Hints:
1. Module Templates
2. New Named Sets (must have 4 names)
XV-OPTION
Card 4 Channel 4
Card 3 Channel 4
=
5 - 20
Summary
• Identify the appropriate module template for motor control
• Define named sets
• Define state masks
• Define device options
• Define condition expressions
5 - 21
5 - 22
DeltaV Regulatory Control
TM

6-2
Objectives
• Determine DST license requirements
• Define a Regulatory Control module using the PID_LOOP template
• Define modes and fields
6-3
Device Signal Tag (DST) Licensing
DST licensing is based on the
number of inputs and outputs:
• Analog Output
• Analog Input
• Discrete Output
• Discrete Input
DeltaV will keep track of DST usage
for you. LI-101 references 1 Analog
Input channel, as a result it uses 1
DST.
Note: DSTs can be substituted for
less functional DSTs. Example, an
Analog Output DST License could be
used for an Analog Input DST.
6-4
Total System DSTs
For a system summary of DST usage, the ProfessionalPLUS Station licensing properties
can be viewed from the DeltaV Explorer.
6-5
DeltaV Licenses
DeltaV licenses are provided in the form of a license file(s) provided on a mini CD and a
unique System Identifier (ID) Key.
Licenses are encoded ensuring they will only work with a matching System ID Key. The
System ID Key Must remain on a DeltaV workstation to permit configuration downloads.
Mini License CD USB System ID Key
6-6
Loading Licenses
Licenses are loaded into your DeltaV database as shown below. The file number must
match the number on your System ID Key.
6-7
Assigning Licenses to Nodes
Licenses can be assigned to the appropriate node using drag n’ drop.
6-8
Modes
DeltaV Modes include:
• Manual (MAN) — The output is set by the operator.
• Automatic (AUTO) — The setpoint is adjusted by an external source and the
loop calculates the output based on the algorithm.
• Cascade (CAS) — The setpoint is adjusted by another function block through
the CAS_IN parameter and the loop calculates the output based on the algorithm.
• Initialize Manual (IMAN) — The block output is being set in response to the
status of the BKCAL_IN parameter. For example, when the secondary loop is
not in Cascade, the primary loop goes to IMAN to prevent windup.
• Out of Service (OOS) — The block does not perform the algorithm. The status is
set to bad.
6-9
Modes
• Remote Cascade (RCAS) — Similar to Cascade except that the setpoint is
supplied by an external control program through the RCAS_IN parameter.
• Remote Out (ROUT) — Similar to Manual except that the OUT value is supplied
by an external control program rather than directly by the operator. OUT is
supplied through the ROUT_IN parameter.
• Local Override (LO) — The block is put into this mode when tracking is
activated. When tracking is deactivated, the block returns to its target mode.
Note: IMAN = 2.0 (Target); 2.0 (Actual)
MAN = 8.0 (Target); 8.0 (Actual)
CAS = 48.0 (Target); 32.0 (Actual)
AUTO = 16.0 (Target); 16.0 (Actual)
OOS = 1.0 (Target); 1.0 (Actual)
RCAS = 80.0 (Target); 64.0 (Actual)
ROUT = 144.0 (Target); 128.0 (Actual)
LO = N/A (Target); 4.0 (Actual)
Important: Always use numeric values, not the word, when writing the mode to
fieldbus devices!
6 - 10
Modes
BKCAL_IN
IN OUT
TANK LEVEL CAS_IN
BKCAL_OUT
OUT
IN FLOW
MOTOR
=
6 - 11
Mode Fields
DeltaV Mode Fields include:
• Target — Mode is requested by the operator. Only modes from the permitted list
may be requested.
• Actual — This is the block’s current mode. This may differ from the target based
on operating conditions.
• Normal — This is the mode the block should be set to during normal operating
conditions. May be configured and read but is not used by the block algorithm.
• Permitted — List of valid mode choices.
6 - 12
Regulatory Control Module FIC-102
AI AO
FIC-102 CTLR
0-100 GPM
FT-2 Gain = 0.5
PV Reset = 3
Rate= 0
SP
P I Reverse Act
FY-2 Increase to Open
FY-2
FT-2
= =
6 - 13
Workshop – Creating a Regulatory Loop
Task 1. Record DST usage prior to configuring FIC-102.
Task 2. Configure the regulatory loop FIC-102 using the PID_LOOP module template.
Task 3. Display loop parameters using Datalinks.
Task 4. Display PipesAnim Dynamos.
Task 5. Record DST usage after configuring FIC-102.
6 - 14
Record DST usage prior to configuring FIC-102 in the following manner:
Step 1. Launch the DeltaV Explorer.
Step 2. Right click on your Workstation and select Licensing→ Licensing Properties.
Step 3. Record the number of DSTs configured for:
Analog Outputs __________
Analog Inputs __________
Discrete Outputs __________
Discrete Inputs __________
6 - 15
Workshop – Using the PID_LOOP Template
Create Regulatory Control module FIC-102 in the following manner:
Step 1. From the DeltaV Explorer, drag ‘n drop the PID_LOOP template from the
Library to PLANT_AREA_A.
Step 2. Rename the module FIC-102.
Step 3. Launch Control Studio and modify the module as indicated below:
IO_IN FT-2 Card 1 Channel 2
IO_OUT FY-2 Card 2 Channel 2
GAIN 0.5
RESET 3 seconds/repeat
PV_SCALE 0 - 100 GPM
IO_OPTS Increase to OPEN
CONTROL_OPTS Reverse Acting
Alarms LOW = 10 HIGH = 90
6 - 16
Workshop – Using the PID_LOOP Template
Step 4. Select the button to assign the module to the controller.
Step 5. Select the button to modify Module Properties primary display Tank101.
Step 6. Select the button to save and the button to download the module.
6 - 17
Record DST usage after configuring FIC-102 in the following manner.
Step 1. Launch the DeltaV Explorer.
Step 2. Right click on your Workstation and select Licensing→ Licensing Properties.
Step 3. Record the number of DSTs configured for:
Analog Outputs __________
Analog Inputs __________
Discrete Outputs __________
Discrete Inputs __________
6 - 18
Modify the operator display by adding Regulatory Control module FIC-102 to the
Tank101 display in the following manner:
display.
Step 2. Add Datalinks with the following characteristics:
FIC-102/PID1/SP (data entry – numeric)
FIC-102/PID1/PV
FIC-102/PID1/OUT (data entry – ramp)
FIC-102/PID1/MODE.A_TARGET (data entry – Multiple-Item Select)
FIC-102/PID1/MODE.A_ACTUAL
FIC-102/ALARMS[1].A_LAALM (Visible when an alarm is active)
Step 3. Add the Dynamo ValveHorizontalControlD1 from Dynamo set ValvesAnim
Hint: Click on the get names button on the Multi-Item Select box to allow data entry on
the Mode parameter.
6 - 19
Step 4. Animate the Valve color:
MTR-102 is RUNNING AND XVSTAT-101 is OPEN
1 - True YELLOW 0 - False GREEN
Step 5. Animate the Actuator color:
FIC-102 is OPEN
1 - True YELLOW 0 - False GREEN
Step 6. Connect the TANK, PUMP and VALVES together using PipesAnim.
6 - 20
Workshop – Operating & Verifying
Verify the operation of Regulatory Control loop FIC-102 in the following manner:
Step 2. Verify Regulatory Control loop FIC-102’s functionality by manipulating the
SP.
Step 3. Open the detail picture for FIC-102 and adjust the tuning parameters.
Note: Open the real-time trend from FIC-102’s faceplate.
6 - 21
Uploading Parameter Changes
On-Line values can be changed from Control Studio or DeltaV Operate. The Upload
option will allow you to write on-line values back to the configuration database.
ProfessionalPLUS DeltaV Operate
Configuration Database
FIC-102 Default
Gain 0.5
Reset 3
Rate 0
CTLR
FIC-102 On-line
Upload Gain 0.7

Reset 2.5
Rate 0
6 - 22
The Upload option can be accessed by right clicking the module of interest.
6 - 23
Select the parameters you want written back to the database and click the OK button to
continue.
6 - 24
The Upload complete confirmation box appears once the selected data has been
successfully uploaded.
6 - 25
Downloading with an Upload
Selecting a download will prompt you with an Upload option if external changes have
been made to the on-line data. If an Upload is not necessary, click the OK button
because, by default, no parameters are selected.
6 - 26
Upload Select None
When you clicked the OK button on the Upload dialog box above no parameters are
uploaded even though the Upload appears to execute. This is necessary for internal
housekeeping.
6 - 27
Optional Exercise
Tune FIC-102 using DeltaV Tune. To emulate a realistic process response your
first step will be to apply a filter on FIC-102’s input channel.
Hints:
1. Apply a 2.6 second filter on Card 1 Channel 2 and download Card 1
2. Launch DeltaV Tune from the FIC-102’s detail picture

3. First Test the process, then Update with new tuning parameters.
6 - 28
Optional Exercise
Create a global user threshold table named flow_color. The threshold table should
have two colors one to indicate product flow and a second color for no flow. Then
modify your piping, pump, and valve animation to use the threshold table.
Hints:
1. Create the Threshold Table in the System Tree
2. Verify the colors change on all objects.
3. Select a new flow color in the threshold table and verify the new color appears on
all the objects.
6 - 29
Optional Exercise
FIC-102 is designed to operate in the AUTO mode under normal conditions. The
process engineer has requested that any time FIC-102’s actual mode is not AUTO, make
the datalink FIC-102/PID1/MODE.A_ACTUAL flash red, otherwise make it invisible.
Hint: Use the ISAN (Is Actual Normal) field for animation
6 - 30
Summary
• Determine DST license requirements
• Define a Regulatory Control module using the PID_LOOP template
• Define modes and fields
6 - 31
6 - 32
Sequential Function Charts
(SFCs)
TM

7-2
Objectives
Upon completion of this module you will be able to define
• The application of a Sequential Function Chart
• The execution of a Sequential Function Chart
• Steps in a Sequential Function Chart
• Actions in a Step
• Action Qualifiers in a Step
• Transitions
• Named Sets for a Sequential Function Chart
7-3
Sequential Function Charts (SFCs)
• SFCs are used to control time/event sequences; i.e., the
startup/shutdown sequence for a piece of equipment.
• SFCs consist of
– Steps − Executes action(s)
– Transitions − Determines when to proceed to the next
Step based on an expression being evaluated as TRUE
– Termination − Special symbol that represents the end of
a sequence
7-4
Step Actions
There are three types of Step Actions:
• Assignment — Assigns the result of an expression to a destination
• Boolean — References a module-level Boolean parameter
• Non-Boolean — References a function block
7-5
Action Qualifiers
7-6
Action Qualifiers
N D D L L P P P S S SD SD DS DS SL SL
2s 12s 7s 16s 4s Exp 4s 14s 4s 14s 25 40s
0s
5s
10s
+
15s
Only active during

the first step
20s
Does not activate
+ R R R R R
Does not
activate
25s
30s
+
7-7
Action Qualifiers
There are two categories of Action Qualifiers:
Non-Stored action qualifiers are only active while the associated step is active or a
portion of the time the step is active.
• N (Non-Stored) — Only active when the step is active.
• R (Reset) — Active on the first scan through a step. Used to stop a stored action.
• L (Time Limited) — Only active when the step is active. Also, you can specify
the action to be “active” for a maximum time or based on an expression.
• D (Delayed) — Only active when the step is active. Also, you specify a delay
based on time or an expression before the action becomes active.
• P (Pulse) — Executes the action once based on a delay time or an expression.
7-8
Action Qualifiers
Stored action qualifiers may be active for only a portion of the time that the associated
step is active or they may remain active after the associated step has become inactive
depending on the specific qualifier.
• S Set (Stored) — Active when the step becomes active and stays active until it is
reset.
• SD (Stored and Delayed) — Active after a delay time or an expression evaluated
“true” when the step becomes active and stays active until it is reset.
• DS (Delayed and Stored) — Active after a delay based on time or an expression
when the step becomes active and stays active until it is reset. If the step goes
inactive before the time delay is up, this action will not go active.
• SL (Stored and Time Limited) — Active when the step becomes active and stays
active until the configured time has elapsed or expression is evaluated “true”.
7-9
SFC Execution
Valid divergence and convergence include:
Divergent Paths
Sequence Select Convergence
7 - 10
SFC Execution
Parallel Divergence
Parallel Convergence
7 - 11
Adding an Action to a Step
Add Actions by selecting Step, placing the positioning selector in the Action window,
clicking the right mouse button and selecting the Add option.
7 - 12
Defining Action Properties
Modify an action by selecting Action, clicking the right mouse button and selecting
Properties from the pop-up menu which appears. The Expression Assistant launches the
Browser.
7 - 13
Defining Transition Properties
Modify or define the transition condition by selecting Transition, clicking the right
mouse button and selecting Properties from the pop-up menu which appears. The
T1 Properties dialog box appears.
7 - 14
Workshop – Using SFCs
Task 1. Define parameter paths required to manipulate Tank101 equipment.
Task 2. Create a Named Set which will be used for operator interface to the SFC.
Task 3. Create an SFC which will Startup Tank101.
Task 4. Display Named Set to the operator.
7 - 15
Workshop – Parameter Paths
List the parameter paths required to:
Open or close the block valve____________________________________________
Determine if the block valve is open or closed ______________________________
Start or stop the motor _________________________________________________
Determine if the motor is running or stopped _______________________________
Set the mode of the flow loop ___________________________________________
Set the setpoint of the flow loop _________________________________________
Manipulate the output of the flow loop ____________________________________
Determine the mode of the flow loop _____________________________________
Determine the flow rate ________________________________________________
7 - 16
Workshop – Using SFC-T101
‘MESSAGE’ := ‘NS-T101:SELECT SEQUENCE’
Named Set NS-T101
1 = STARTUP
255 = SELECT SEQUENCE Open the block valve XV-101
Set the flow rate to 50 GPM FIC-102
parameter - MESSAGE
(Named Set, NS-T101)
Start pump MTR-102
7 - 17
Step 1. Create Named Set NS-T101 using DeltaV Explorer.
7 - 18
Step 2. Modify Properties and add names and values as shown below.
Named Set NS-T101 (Name- Case sensitive) Visible User Selectable

1 = STARTUP Yes Yes
255 = SELECT SEQUENCE Yes No
7 - 19
Step 3. Use Control Studio to create Sequential Function Chart SFC-T101. Select
New. Change the Algorithm Type to Sequential Function Chart.
7 - 20
Step 4. Create parameter MESSAGE (Named Set, NS-T101).
7 - 21
Step 5. Create Sequential Function Chart using Steps, Transitions and
Terminations from the All SFC Items Palette.
‘MESSAGE’ := ‘NS-T101:SELECT SEQUENCE’
‘MESSAGE’ = ‘NS-T101:STARTUP’
Open the block valve XV-101
Wait for the block valve to open XVSTAT-101
Set the flow rate to 50 GPM FIC-102
Wait for flow valve to be > 30 % open
Start pump MTR-102
Wait for pump to start
7 - 22
Step 6. Modify Module Properties and assign the SFC to your controller.
Step 7. Save and download the SFC.
Step 8. If an algorithm error occurs, use the button to check the SFC.
Step 9. Add the MESSAGE parameter to operator display Tank101 with Data Entry
capability.
Step 10. Verify that the sequence executes properly.
Note: Remember to download Changed Setup Data.
7 - 23
Action Properties (General Tab)
Delay allows you to define a time or an expression you want satisfied before the action
is executed. When the time has lapsed or the expression has been evaluated TRUE, the
action will be performed.
Note: The delay does not hold the step.
7 - 24
7 - 25
Action Properties (Confirm Tab)
7 - 26
Action Properties (Confirm Tab)
If you add a Confirm to an Action, you must configure the transition or termination that
follows to an expression that allows for the confirmation to complete.
• CONFIRM_FAIL — set whenever an action has a confirmed timeout before the
expression used in confirming becomes TRUE.
• FAILED_CONFIRMS — the number of actions on the step that have failed to
confirm.
• PENDING_CONFIRMS — the number of actions on the step not yet confirmed
or failed.
7 - 27
Workshop – Modifying SFC-T101
Step 1. Modify NS-T101 to include shutdown as an option.
Step 2. Modify SFC-T101 so it will Startup and Shutdown Tank101 using divergent
paths as shown below.
Step 3. Download the SFC.
Step 4. If an algorithm error occurs, use the button to check the SFC.
Step 5. Verify that the sequence executes properly.
7 - 28
Workshop – Startup & Shutdown
Wait for STARTUP message Wait for SHUTDOWN message
Open the block valve XV-101 Stop pump MTR-102
Wait for block valve to open XVSTAT-101 Wait for pump to stop
Set the flow rate to 50 GPM FIC-102. Close block valve XV-101
Wait for flow valve to be > 30 % open Wait for block valve XVSTAT-101 to close
Set the mode of FIC-102 to MAN.

Start pump MTR-102
Set OUT of FIC-102 to 0%
Wait for pump to start Wait for flow valve to be < 2 % open
No Action
True
7 - 29
Optional Exercise
Update the operator with a message pertaining to what the SFC is waiting for in
each transition.
Hints:
1. Add values to the Named Set NS-T101
2. Add actions in the appropriate steps to update the MESSAGE parameter
7 - 30
Optional Exercise
Modify the SFC so that Startup will make sure the level in Tank101 is high enough
to allow MTR-102 to start and MTR-102’s lock is reset if necessary.
7 - 31
Optional Exercise
Cause an alarm to be displayed in DeltaV Operate (Run) when the SFC exceeds a
specified time (i.e., over 30 seconds) to execute.
Hints:
1. Add an Alarm Type
2. Add an alarm to the SFC
3. Add a function block to the SFC to trigger the alarm
4. Start the function block (Non-Boolean action)
7 - 32
Summary
• The application of a Sequential Function Chart
• The execution of a Sequential Function Chart
• Steps in a Sequential Function Chart
• Actions in a Step
• Action Qualifiers in a Step
• Transitions
• Named Sets for a Sequential Function Chart
7 - 33
7 - 34
DeltaV Cascade Control
TM

8-2
Objectives
• Perform top down configuration
• Implement cascade control using CASCADE_MASTER and CASCADE_SLAVE
templates
• Implement flow simulation with an Embedded Composite Block
• Implement level simulation with the Integrator Function Block
• Use Control Studio On-line for testing modules
• Implement the Continuous Historian
8-3
Cascade Level Control of TANK201
From Tank101 FIC-102
LEV2-SIM IN OUT
“INT” LIC-20X
CAS_IN
OUT
IN FIC-20X
MTR-203
= FLOWSIM
8-4
Workshop – Flow Control
You are required to perform the following tasks:
Task 1. Create MTR-203 using the MTR-11 module template
Task 2. Create a flow loop using an Embedded Composite Block
Task 3. Use a Calc Block for flow simulation
Task 4. Create an operator display with next and previous links
Task 5. Drag ’n drop frsModules Dynamos
8-5
Workshop – Creating Motor MTR-203
Create motor MTR-203 in the following manner:
Step 1. From the DeltaV Explorer, drag ‘n drop the MTR-11 template from the
Library to PLANT_AREA_B.
Step 2. Rename the module MTR-203.
Step 3. Launch the Control Studio and modify the module as indicated below:
IO IO_IN_1 XI-3 Card 3 Channel 3
IO_OUT_1 ZX-3 Card 4 Channel 3
Step 4. Modify module properties’ primary control display Tank201.
Step 5. Assign to the controller.
Step 6. Save the control module.
8-6
Step 7. Assign DSTs XI-3 and ZX-3 to the appropriate card and channel.
Note: The warning is expected.
8-7
Step 8. Select the appropriate channel, go to
properties and enable both channels XI-3
and ZX-3.
Step 9. Download I/O Cards 3 and 4.
Step 10. Download Control Module
MTR-203.
8-8
Step 11. Verify that the motor STARTS and STOPS using the Control Studio’s On-line
button.
8-9
Secondary Flow Control
FIC-20X
PID1 FLOWSIM
OUTPUT
0-100 GPM PV
IN Gain = 0.5
PV Reset = 3
Rate= 0 FILTER OUT
SP IN FIC-20X
Reverse Act IN OUT
P I
TIMECONST = 2
FLOWSIM
OUT
CALC
Increase to Open
INPUT IN1 OUT1
VO
Pass flow signal only if
MTR-203 is running
8 - 10
Workshop – Create FIC-20X
PID1
FIC-20X 0-100 GPM
Gain = 0.5
Reset = 3
PID1
BKCAL_OUT Rate= 0
BKCAL_OUT
CAS_IN CAS_IN Reverse Act
OUT Increase to Open
IN
OUT
IN FIC-20X
FLOWSIM
VO PV
“Embedded” VO
PV FLOWSIM
8 - 11
Create FIC-20X in the following manner:
Step 1. Drag ‘n drop, from the DeltaV Explorer, the CASCADE_SLAVE template
located in the Module Template Library’s AnalogControl category to
PLANT_AREA_B.
Configuration tips:
1. The control blocks and parameters are shown above.
2. The parameters for PID1 are shown above.
3. DSTs are not used for IO_IN and IO_OUT. The IO_IN will be supplied from the
FLOWSIM’s PV and IO_OUT will be passed to FLOWSIM’s VO.
8 - 12
Step 2. Add the Embedded Composite block to FIC-20X by dragging and dropping a
Custom Block found in the Special Items palette. Name it FLOWSIM.
8 - 13
Custom Block Types
• Function Block — A basic block provides commonly used functions for your
algorithm.
• Extended Block — A DeltaV function block is defined to run in a Fieldbus device.
• Embedded Composite — A block that is not linked to the original object. An
embedded composite contains one or more other blocks and parameters. If
changes are made to the original object, this composite will be unaffected. Use this
type when you want an independent, standalone copy of an existing composite.
• Linked Composite — A block that is linked to a composite block or template. A
linked block is a composite of one or more other blocks and parameters. If
changes are made to the original composite block, the changes will affect this
block.
• Module Block — A block that provides input/output connectors to another module
you are editing. For example, when implementing cascade control, you could
have an inner loop and an outer loop that execute at different rates. The module
block you add here could control one loop, and the module you are editing could
control the other. The scan rate is a property of a module.
8 - 14
Embedded Composite
Modification of Embedded Composite Blocks DOES NOT MODIFY instances
• You may drill down and modify an Embedded block from an instance usage.
• You may drill down and modify the parameters of an Embedded block.
8 - 15
Linked Composite
Library Composite Template
Param1 CALC1
Edit
PID1 Linked Composite PID1 Linked Composite PID1 Linked Composite

Param1 CALC1 Param1 CALC1 Param1 CALC1
Drill down
Module_1 Module_2 Module_3
Modifying Linked Composite Blocks modifies instances

• You are not permitted to drill down and modify a Linked block from an
instance; you must open another Control Studio application.
• You are permitted to drill down and modify a Linked block’s parameters. The
parameter modifications are only applicable to the module from which they are
modified.
8 - 16
FLOWSIM
CALC FILTER
INPUT OUTPUT
IN1 OUT1 IN OUT
VO PV
Pass flow signal only if TIMECONST = 2
MTR-203 is running
OUT
IN FIC-20X
FLOWSIM
8 - 17
Step 3. Select the FLOWSIM block by clicking the right mouse button to Drill Down
or Edit Object according to the following
a. Drag ‘n drop the CALC/LOGIC block from the Analog Control palette
b. Select the CALC1 block by clicking the right mouse button
c. Select the Extensible parameters... and set the IN and OUT to 1
d. Select the CALC1 block again and define the Expression... as follows
IF '//MTR-203/DC1/PV_D.CV' = 'mtr2-pv:RUNNING’
THEN
'OUT1.CV' := 'IN1.CV';
ELSE
'OUT1.CV' := 0;
ENDIF;
8 - 18
Step 4. Drag and drop the FILTER block from the Analog Control palette
a. Set the TIMECONST parameter on the Filter block to 2 seconds
b. Re-name Input Parameter PARAM1 to VO
c. Re-name Output Parameter PARAM2 to PV
d. Connect the blocks and parameters according to the diagram below.
8 - 19
Step 5. Click the right mouse button and Back Out in order to return to the top level
of FIC-20X.
Step 6. Connect the PID1 and FLOWSIM blocks as illustrated below.
Step 7. Modify the Module Properties.
Step 9. Save and download.
8 - 20
Workshop – Adding an Operator Display
This workshop requires you to add FIC-20X to a new display called Tank201 in the
following manner:
Step 1. Create a new display called Tank201 using the main template
Step 2. Add the Dynamo PID_LOOP_1_ from the frsModules Dynamo set to
manipulate FIC-20X
Hint: Replace the word MODULE with FIC-20X
Step 3. Add a Pump Dynamo for MTR-203
Hint: You can use a frsModules Dynamo here as well.
Step 4. Create the display hierarchy by defining the PREVIOUS and NEXT pictures as
follows:
Previous = Tank101 Next = Ovw_ref
8 - 21
Workshop – Operate & Verify
Verify the operation of FIC-20X in the following manner:
Step 2. Verify FIC-20X’s functionality by manipulating the SP.
Step 3. Verify MTR-203’s functionality by STARTING and STOPPING the motor.
Note: Tune if necessary.
8 - 22
8 - 23
Primary Level Control
IN OUT
LEV2-SIM LIC-20X
“INT” CAS_IN
OUT
IN FIC-20X
MTR-203
= FLOWSIM
8 - 24
Primary Level Control
LEV2_SIM
FIC-102_PV
201_LEV
FIC-20X_PV
LIC-20X FIC-20X
0-1000 GAL 0-100 GPM

IN Gain = 8 IN Gain = 0.5
PV Reset = 30 PV Reset = 3
Rate= 0 SP (CAS) Rate= 0
SP
Direct Act Reverse Act
P I P I
BKCAL_OUT
OUT
BKCAL_IN
Increase to Open Increase to Open
8 - 25
Workshop – Level Control
Task 1. Create a LEV2-SIM simulation module using the Integrator function block.
Task 2. Run On-line to verify module functionality.
Task 3. Create a level loop using the CASCADE_MASTER template.
Task 4. Reference the LEV2-SIM module using a Read Only external reference.
8 - 26
Workshop – Creating LEV2-SIM
Step 1. Create a new module named LEV2-SIM using Control Studio. Follow the
remaining steps to build the module according to the illustration below :
INTEGRATOR
OUT 201_LEV
FIC-102_PV IN_1
FIC-20X_PV IN_2
REV_FLOW2
Step 2. Drag ‘n drop the Integrator function block from the Math palette onto the
function block diagram
Step 3. Double click in the filter area of the Parameter window. Select the Connectors
in the Parameter Filtering window and leave the Common configuration
checked.
8 - 27
Step 4. Modify the following parameters:
ENABLE_IN_2 - 1 (True)
INTEG_TYPE - 0 to ?-demand reset
REV_FLOW2 - 1 (negative integration)
TIME_UNIT1 - Minutes
TIME_UNIT2 - Minutes
Step 5. Drag ‘n drop two Input parameters or Internal Read parameters onto the
function block diagram from the Special Items palette.
PARAM1 - Name: FIC-102_PV
Parameter type: External Reference
Browse for external parameter path: FIC-102/PID1/PV
PARAM2 - Name: FIC-20X_PV

Browse for external parameter path: FIC-20X/PID1/PV
8 - 28
Step 6. Drag ‘n drop an Output parameter onto the function block diagram from the
Special Items palette; promoting a parameter.
PARAM1 - Name: 201_LEV
Parameter type: Floating point
Step 7. Wire connections to all parameters as illustrated above.
Step 8. Modify module properties, assign to the controller, save as LEV2-SIM in
PLANT_AREA_B and download.
Step 9. Verify the level is being integrated properly by using the on-line tool.
Hint: The Integrator may be reset or returned to zero by setting the RESET_IN
parameter to 1 then re-setting the RESET_IN parameter back to 0 using
ON-LINE.
8 - 29
Workshop – Creating LIC-20X
Step 1. Create a new module named LIC-20X using the CASCADE_MASTER module
template, located in the Module Template Library’s AnalogControl category,
according to the illustration below:
PID1 FIC-20X
BKCAL_IN OUT CAS_IN BKCAL_OUT
0-1000 GAL
Gain = 8
Reset = 30
201_LEV IN Rate= 0
Ext Ref. Read Only Direct Acting
Increase to Open
SP_HI_LIM 1000
SP_LO_LIM 0
HI_ALM 950
LO_ALM 100
OUT_SCALE 0-100
Step 2. Modify PID1’s parameters as illustrated above.
8 - 30
Workshop – Creating LIC-20X
Step 3. Add an Input parameter from the Special Items palette and assign it the
following characteristics:
Name: 201_LEV
Browse for the path: LEV2-SIM/201_LEV
As illustrated above, connect the External Reference parameter to the IN
parameter on PID1.
Step 4. Select the slave loop by clicking the right mouse button and select Convert >
To Existing Object... FIC-20X
Step 5. Modify the Module Properties.
Step 7. Save and download.
Step 8. Download FIC-20X.
8 - 31
Workshop – Adding LIC-20X to Tank201 Display
LEV2-SIM LIC-20X
FIC-20X
MTR-203
=
8 - 32
Workshop – Adding LIC-20X to Tank201 Display
Add LIC-20X to the Tank201 display in the following manner:
Step 1. Add the Dynamo PID_LOOP_1_ from the frsModules Dynamo set to
manipulate LIC-20X.
Step 2. Finish the display by adding the equipment shown above.
Step 4. Close all pictures.
8 - 33
Workshop – Operate & Verify
Verify the operation of LIC-20X in the following manner:
Step 2. Verify LIC-20X’s functionality by manipulating the inlet feed FIC-102 to
verify the level is maintained.
Note: Tune if necessary.
Step 3. Set FIC-20X to AUTO and verify LIC-20X’s output tracks FIC-20X’s SP.
Step 4. Verify that LIC-20X’s HIGH and LOW alarms function properly.
8 - 34
8 - 35
Continuous Historian
Continuous Historian allows the collection of user-specified parameters for long-term
storage, retrieval and presentation.
• History Collection — allows you to define module and node parameters to be
monitored and stored in the Continuous Historian.
• Continuous History Subsystems — monitors modules for history collection data
on a plant area basis because each workstation has a Continuous History
Subsystem capable of detecting and storing historical data.
• Process History View — displays real-time and historical data from the
Continuous History Subsystems as well as from the Event Chronicle.
8 - 36
Workshop – Continuous Historian
Task 1. Define parameters for history collection.
Task 2. Start collection of data by enabling the Continuous Historian and assigning
plant areas to it.
Task 3. Configure a Chart.
Task 4. Display Historical data.
8 - 37
Workshop – Defining a History Collection
This workshop requires you to define history collection for LIC-20X in the following
manner:
Step 1. Expand PLANT_AREA_B.
Step 2. Select LIC-20X by clicking the
right mouse button.
Step 3. Select History Collection.
8 - 38
Workshop – Defining a History Collection
Step 4. Define a History Collection

consisting of LIC-20X’s PV,
SP and OUT.
Note: When using Library items, some
parameters are predefined for the
History Collection.
8 - 39
Workshop – Start Data Collection
This workshop requires you to begin collecting data in the following manner:
Step 1. Expand your workstation.
Step 2. Select Continuous Historian by clicking the right
mouse button.
Step 3. Select Properties ; Enabled
8 - 40
Workshop – Start Data Collection
Step 4. Drag ‘n drop PLANT_AREA_B to Continuous Historian.
Step 5. Download the workstation.
8 - 41
Workshop – Configuring a Chart
This workshop requires that you display historical data for LIC-20X in the following
manner:
Step 1. Launch Process History View.
Note: Launching Process History View from DeltaV Operate (Run) toolbar displays the
Event Chronicle. Launching Process History View from a faceplate will open a default
chart for that module type. Launching Process History View from anything other than
DeltaV Operate (Run) displays the last chart that was viewed, if any.
8 - 42
Step 2. Select New.
Step 3. Select Chart.
8 - 43
Step 4. Configure the chart to include the PV, SP and OUT of LIC-20X using the Add
button and browse for the parameter path.
8 - 44
Step 5. View the data.
8 - 45
Embedded Trend Configuration
An embedded trend object can be placed in a graphic display by using the embedded
trend button in the DeltaV Toolbox.
Double-clicking the object in the configure mode allows you to configure the chart.
8 - 46
Embedded Trend Operation
Right-clicking the embedded trend object in the run mode provides many of the same
options as Process History View shown below.
8 - 47
Optional Exercise
Add an embedded trend object to the Tank201 display for monitoring LIC-20X.
Hint: Don’t forget the embedded Trend button in the DeltaV toolbox
8 - 48
Optional Exercise
Modify the PV_SCALE of FIC-20X so that the outlet flow for Tank201 does not
equal the inlet flow. This will allow Tank201 to drain faster.
Hint: Don’t forget to modify LIC-20X
8 - 49
Optional Exercise
Modify Tank101 and Ovw_ref displays to include Tank201 in the navigation.
Hints:
1. Modify the PREVIOUS and NEXT picture buttons
OR
2. Create buttons and use the Replace Picture Expert
8 - 50
Optional Exercise
Add a data link to the TANK201 display to reset the integrator.

OR
Replace the integrator block with a calc block that will perform the integration and limit
the value between 0 and 1000.
8 - 51
Summary
• Perform top down configuration
• Implement cascade control using CASCADE_MASTER and CASCADE_SLAVE
templates
• Implement flow simulation with an Embedded Composite Block
• Implement level simulation with the Integrator Function Block
• Use Control Studio On-line for testing modules
• Implement the Continuous Historian
8 - 52
Conditional Alarms
TM

9-2
Objectives
• Modify alarms using the System Alarm Management application
• Create a Conditional Alarm for a loop
9-3
System Alarm Management
The System Alarm Management application lets you view all alarms within selected
Areas, Modules, Units, Logic Solvers and Nodes. The application provides a way to
efficiently view, enable and disable, and set limits and priorities on multiple alarms.
9-4
The System Alarm Management application can be accessed several ways. Two methods
are shown below.
By clicking on the plant area to display

all the alarms in the plant area
From the DeltaV Explorer toolbar under
Applications
Note: By default, no alarms are listed when the application first opens using this method.
9-5
Alarms may be viewed by Area, Module, Unit, Logic Solver, and Node.
9-6
Other Areas, Modules, Units, Logic Solvers, or Nodes can be displayed by adding them
to the list.
9-7
Alarm properties can be modified individually or in groups.
Note: Modifications to alarm properties will not take effect until they are downloaded.
9-8
9-9
Conditional Alarming
Conditional Alarming enables you to add time delays and enable/disable alarms to
minimize nuisance alarms. For example, a low flow alarm is needed for FIC-20X.
However, we do not want a low flow alarm if the pump is not running. Conditional
alarming allows us to disable the alarm if the pump is not running.
The AI, Alarm, Manual Loader, PID, Fuzzy Logic Control and Ratio function blocks
support conditional alarming for the standard alarms: HI, HI_HI, DV_HI, DV_LO, LO
and LO_LO. The DI function block supports conditional alarming for the DISC alarm.
9 - 10
Conditional Alarming is enabled from the Assign Alarm… dialogue box.
9 - 11
Check the Conditional alarming box on the
Block Alarms dialogue box. The dialogue box
indicates the Conditional Alarming features
for each alarm as it is selected.
Use the Conditional Alarming feature to set
any delay times needed for the alarms.
9 - 12
When conditional alarming is enabled, five new parameters are added to the function
block for each alarm. These include DV_HI, DV_LO, HI, HI_HI, LO, LO_LO and
DISC. The following descriptions refer to the condition that sets the <alarm>_ACT
to TRUE.
9 - 13
• <alarm>_DELAY_OFF — This parameter delays the time (in seconds) that it
takes for <alarm>_ACT to be set to false (0) after the alarm condition clears.
The timer resets every time the alarm condition is detected.
• <alarm>_DELAY_ON — This parameter delays the time (seconds) that it takes

for the <alarm>_ACT to be true (1) after the alarm condition is detected. The
timer resets every time the alarm condition clears.
• <alarm>_ENAB — This Boolean parameter enables/disables alarm processing

for a single alarm. The default value for this parameter is enabled (1). You can
write to the _ENAB parameter to dynamically enable/disable the alarm based on
external process conditions.
When <alarm>_ENAB is disabled (0), the <alarm>_ACT parameter is

immediately forced to false (0). No alarm can occur.
9 - 14
• <alarm>_ENAB_DELAY — This parameter sets the time (in seconds) before the
alarm processing begins after the <alarm>_ENAB is written to true (1). The
<alarm>_ACT parameter is forced to false (0) for the time specified. The timer
resets when <alarm>_ENAB goes from 0 to 1.
• <alarm>_HYS — This parameter is used as a deadband when resetting base
alarm conditions for analog values. The block uses the value of <alarm>_HYS
rather than the standard ALARM_HYS on the module.
9 - 15
Once conditional alarming is enabled, the condition on which to alarm may be defined.
Click on the function block and select Show Parameter.
9 - 16
Apply a condition to FIC-20X to enable the LO_ALM only when MTR-203 is running.
Show the LO_ENAB input parameter. When this parameter is 1, the LO_ACT will be
set to 1 when flow is below the trip level.
9 - 17
An external reference parameter is wired into the LO_ENAB input on the PID1 function
block. When MTR-203’s PV is Running or 1, the LO_ENAB will be set to 1.
9 - 18
Workshop – Configuring a Conditional Alarm
While the level alarms are valid, FIC-20X’s low alarm is a nuisance unless the pump,
MTR-203, is running. In the following exercise, you will configure a conditional on the
LO_ALM of FIC-20X to only enable when the motor is running.
9 - 19
Step 1. Open FIC-20X in Control Studio.
Step 2. Right Click the PID1 block and select Assign Alarm…
Step 3. Check the Conditional alarming option.
Step 4. Select the LO alarm and verify that the limit value is 10. No delays are
necessary for this alarm. Enable LO_ALM. Click OK to continue.
Step 5. Right click on the PID1 block and select Show Parameter….
Step 6. Browse and select the LO_ENAB parameter, an input parameter, from the list.
9 - 20
Step 7. Add an Input Parameter to your diagram. Name the parameter MTR-203 and
set the type to External Reference. Assign the category to Alarm. Set the
parameter path to MTR-203/DC1/PV_D.
Step 8. Connect the input parameter to LO_ENAB on the PID1 block. Only when the
input is 1 (pump is running) will the LO_ACT be enabled.
Step 9. Save and Download FIC-20X.
Step 10. Verify that the LO_ALM for FIC-20X is not triggered unless the pump is
running.
9 - 21
Summary
• Modify alarms from the System Alarm Management application
• Create a Conditional Alarm for a loop
9 - 22
Phase Logic Modules
(PLMs)
TM
EMERSON Process Management Educational Services Copyrighted Material / Duplication Prohibited

EMERSON Process Management – Educational Services Course 7009 - Rev 9 – 8/15/07 Copyrighted Material / Duplication Prohibited
10-2
Objectives
• Define the application of a Phase Logic Module
• Define States of a PLM
• Define a Named Set for FAIL_MONITOR
• Export DeltaV Database Objects
• Copy Pictures
10-3
Phase Logic Module
10-4
Phase Logic Module
The Phase Logic Module is a module that defines the states of the phase and logic
associated with each state.
10-5
Failure_Monitor
10-6
Failure_Monitor
The Failure_Monitor continuously monitors failure conditions and sets the
FAIL_INDEX equal to the fail number. When FAIL_INDEX is a non-zero, the phase
transitions to the Holding state.
10-7
Failure_Monitor Defaults
10-8
FAIL_INDEX
10-9
Workshop – PLM Plant Shutdown
Step 1. Modify Name Set phase_failures. Add the name for the phase failure: Block
valve 101 is open.
10-10
Step 2. From DeltaV Explorer create PLM-SHUTDOWN. Change the Object type to
Phase Logic Module.
10-11
Step 3. Open PLM-Shutdown with Control
Studio. Create a PLM parameter
SHUTDOWN_LEVEL (floating point).
10-12
Step 4. Add a Condition Block to FAIL_MONITOR to determine whether Tank101’s
block valve is OPEN (XVSTAT-101). Set the Condition Block’s Disable
parameter to 1.
Step 5. Modify the expression of BLOCK1 to include an IF THEN statement to check
OUT_D of the Condition Block and set FAIL_INDEX if the block valve is
OPEN.
10-13
Step 6. Define RUN_LOGIC. RUN_LOGIC
Note: Assumption for RUN_LOGIC to Perform actions necessary to shutdown
Tank101 utilizing confirms
work, process is running with the
Cascade Pair in the normal mode. Wait for above devices to transition utilizing the
PENDING_CONFIRMS parameter.
Enable monitoring of phase FAIL_MONITOR

condition (set Disable parameter to 0).
Set LIC-20X SP to SHUTDOWN-LEVEL
Wait for level to be satisfied.
Stop MTR-203
Wait for motor to stop.
Close FIC-20X.
Disable monitoring of phase FAIL_MONITOR
condition (set Disable parameter to 1).
Wait for flow valve to close.
10-14
Step 7. Define HOLD_LOGIC.
HOLD_LOGIC
Disable monitoring of phase

FAIL_MONITOR condition
Failure detected
(‘/FAIL_INDEX.CV’!=0) True
Close Tank101 block valve
Step active for at least 2 sec

(Step parameter - TIME)
Stop MTR-203 and confirm

Close FIC-20X and confirm
Wait for above devices to transition utilizing the

PENDING_CONFIRMS parameter
10-15
Step 8. Define RESTART_LOGIC.
RESTART_LOGIC
Set FIC-20X mode to CAS
Start MTR-203
Enable monitoring of phase FAIL_MONITOR condition
Wait for motor to start
Step 9. Assign PLM to your controller.

Step 10. Save and download the PLM.
Step 11. If an algorithm error occurs, use the Check button to check the PLM.
Step 12. Add the PLM_ dynamo from frsModules dynamo set to an operator display.
10-16
Step 13. Toggle Phase Owner to External by clicking on the
toggle button.
10-17
Step 14. Click on the Phase Command
ellipse button to display a list of
valid phase commands. Issue the
Start command.
10-18
Step 15. While the PLM is running, Open XV-101 to cause a
failure. Verify PLM runs HOLD logic.
Step 16. Verify Failure State utilizing the Detail Faceplate.
10-19
Step 17. Clear Failures.
10-20
Step 18. Issue the Restart command.
10-21
Step 19. Issue a Hold command while
PLM is running.
Step 20. Restart PLM after Hold logic is
complete.
10-22
Step 21. Reset PLM when it is complete. Also verify that PLM transitions to Idle.
10-23
Optional Exercise
Define logic for Stop and Abort.
10-24
Summary
• Define the application of a Phase Logic Module
• Define States of a PLM
• Create a Named Set for FAIL_MONITOR
• Export DeltaV Database Objects
• Copy Pictures
10-25
10-26
DeltaV Security
TM

11 - 2
Objectives
Upon completion of this module you will be able to define
• Parameter, field, and function security
• Users
• Groups
• Locks
• Flexlock Application
• Electronic Signatures
• Workstation Options
• DeltaV Simulate
• Mimic
• AMS
• DeltaV Export
11 - 3
DeltaV Locks & Keys
Through the use of Locks & Keys, the DeltaV

System provides security for parameters, fields,
functions, and electronic signatures.
11 - 4
DeltaV Locks & Keys
• Control — lock assigned to parameters that an operator needs to write to or
modify in order to control the process
Example: MODE, SP, OUT
• Restricted Control — lock assigned to parameters or fields that supervisors and
engineers might use to configure the process
Example: BKCAL_IN, FF_ENABLE, RESTART_ENABLE
• Tuning — lock assigned that maintenance tech and supervisors use to tune the
performance of the process
Example: GAIN, RESET, HI_LIM
11 - 5
DeltaV Locks & Keys
• System Records — lock assigned that affect the records kept by the system
Example: ENAB
• Diagnostic — lock assigned to parameters and fields that affect diagnostic
information maintained by the system
• Alarms — lock assigned to parameter and fields that affect alarm handling
Example: HORN, MACK, NALM
• User Lock 01 through User Lock 10 — locks that can be assigned to parameters
and fields that allow customized security schemes to be implemented
• Batch Operate — lock assigned that will allow a user with this key to operate the
DeltaV batch subsystem.
11 - 6
DeltaV Locks & Keys
• Build Recipes — lock assigned that will allow a user with this key to use the
Recipe Studio.
• Can Calibrate — lock assigned that would allow a user with this key to use the
AMS device configuration and calibration features.
• Can Configure — lock assigned that would allow a user with this key to change
the configuration database.
• Can Download — lock assigned that would allow a user to download
configurations to nodes in the control network.
• System Admin — lock assigned that would allow a user with the key to access
the database administration tools to create, copy and rename databases.
11 - 7
Parameter Security
Access the DeltaV Parameter Security Properties dialog box from DeltaV Explorer by
selecting
System Configuration → Setup → Security → Parameter Security → Properties
11 - 8
Parameter Security
“Writable” parameters have locks assigned to them. The Properties dialog box, shown
below, permits you to change the lock assignments.
11 - 9
Field Security
Access the DeltaV Field Security Properties dialog box from the DeltaV Explorer by
selecting
System Configuration → Setup → Security → Field Security → Properties
11 - 10
Field Security
“Writable” fields have locks assigned to them. The Properties dialog box, shown
below, permits you to change the lock assignments.
11 - 11
Function Security
Access the DeltaV Function Security Properties dialog box from the DeltaV Explorer
by selecting
System Configuration → Setup → Security → Function Security → Properties
11 - 12
Function Security
Various “writable” functions have locks assigned to them. The Properties dialog box,
shown below, permits you to change the lock assignments.
11 - 13
User Manager
Access the DeltaV User Manager form from the DeltaV Explorer by selecting the
Lock Key button. The DeltaV User Manager dialog box appears.
11 - 14
User Manager
The DeltaV User Manager dialog box, shown above, allows you to ADD or DELETE
user and group.
11 - 15
User Properties
Access the DeltaV General User properties form by clicking the right mouse button in
a blank area of the Users’ Window and selecting New from the pull down menu. The
New User form appears with the General tab selected.
11 - 16
User Properties
Use the General tab, shown on the New User dialog box above, to ADD and IDENTIFY
a user.
Note: Press the Help button for detail information on specific fields.
11 - 17
Advanced User
Access the Advanced User form by selecting the Advanced tab from the New User
dialog box.
11 - 18
Advanced User
Use the Advanced tab, shown on the New User dialog box above, to change the USER
ACCOUNT and PASSWORD STATUS.
11 - 19
User Groups
Access the Groups form by selecting the Groups tab from the New User dialog box.
11 - 20
User Groups
Use the Groups tab, shown on the New User dialog box above, to modify the groups to
which a user belongs.
11 - 21
User Keys
Access the Keys form by selecting the Keys tab from the New User dialog box.
11 - 22
User Keys
Use the Keys tab, shown on the Properties For User dialog box above, to grant keys to,
or remove keys from, a user account.
11 - 23
Group Properties
Access the DeltaV Properties for Group: Operate form by double clicking a Group in
the Groups window. The form appears with the General tab selected.
11 - 24
Group Properties
Use the Properties for Group dialog box, shown above, to ADD or MODIFY a group.
Use the General tab to name and describe a user group.
11 - 25
Group Members
Access the Members form by selecting the Members tab from the Properties for Group
dialog box.
11 - 26
Group Members
Use the Members tab, shown on the Properties for Group dialog box above, to modify a
user group by ADDING or DELETING members.
11 - 27
Group Keys
Access the Keys form by selecting the Keys tab from the Properties for Group dialog
box.
11 - 28
Group Keys
Use the Keys tab, shown on the Properties for Group dialog box above, to grant keys to,
or remove keys from, the group currently being created or modified.
11 - 29
Flexlock
The FlexLock provides a secure operating environment by limiting desktop access to
those users with the required privileges for that desktop. The DeltaV FlexLock
application opens when a user logs on to DeltaV.
FlexLock available desktops are the Windows and DeltaV desktops.

• A user with Windows Desktop Access has access to the Operating System (XP)
and DeltaV desktops.
• A user who does not have Windows Desktop Access is limited to the DeltaV
desktop.
The Windows desktop access includes all the DeltaV programs as well as all programs
available in Windows XP.
The DeltaV desktop limits the user to DeltaV Operate and its associated applications. To
secure your environment, consider giving operators access to the DeltaV desktop only
and configuration engineers access to both the DeltaV and Windows desktops.
11 - 30
Flexlock
When a user logs off, the next user to log on sees the FlexLock application with the
DeltaV Desktop button active. This indicates that the current user has been switched to
the DeltaV desktop.
All users without Windows Desktop Access who attempt to switch to the Windows
Desktop receive a message indicating that they lack the proper privileges and are
prompted to enter an administrator name and password. If they enter the proper
administrator password, FlexLock switches them to the Windows desktop.
If you exit the FlexLock application from the Windows desktop, click
Start → DeltaV → Engineering → FlexLock
to return to the DeltaV desktop.
Important: You cannot exit the FlexLock application from the DeltaV desktop.
11 - 31
Workshop – Defining Users
Task 1. Create a User with OPERATE privilege with area restrictions.
Task 2. Create a User with TUNE privilege.
Task 3. Download and verify.
11 - 32
Step 1. Create a User with OPERATE privilege and the following characteristics:
Name OperatorA
Full Name Alpha Operator
Password operatora
Privileges OPERATE privileges only for PLANT_AREA_A
Step 2. Create a User with TUNE privilege and the following characteristics:
Name Supervisor1
Full Name Sarge Supervisor
Password supervisor1
Privileges Sitewide TUNE privileges and download capability
11 - 33
Step 3. Download the Workstation.
Step 4. Verify by logging all the way out to the XP Log In
a. Close all applications
b. Start → Shut Down → Log off “the current user” and log on as one
of your new users
Step 5. Verify each new user’s functionality.
Note: If a user does not have Windows Desktop Access, press the Ctrl / Alt / Delete
keys before selecting the Log Off button.
11 - 34
DeltaV Electronic Signatures
Electronic signatures are user names and passwords that provide accountability for
operator writes to certain module parameters and fields from DeltaV Operate and Control
Studio online. Electronic Signatures do not apply to OPC writes or to the DeltaV Excel
Add-In application.
Based on the criticality of a module to the process, no signature, one signature
(confirmer), or two signatures (confirmer and verifier) can be configured. It is possible to
allow the same person to be both the confirmer and verifier of an operator write.
Typically, the verifier is a higher-level employee whose signature approves the change
the confirmer is making. The verifier must hold the key to the ACTION_VERIFY
function lock.
11 - 35
Enable Signature Policies on System Preferences.
Start → DeltaV → Engineering → System Preferences
Note: Remember to shutdown and
restart the server using the
DeltaV Database Administrator.
File → Shutdown server followed
by a Connect to server.
11 - 36
Enable electronic signatures by checking Electronic Signatures in DeltaV Operate and
DeltaV Control Studio.
11 - 37
Create a new policy by right clicking on ElectronicSignatures and selecting New Signature
Policy.
11 - 38
Right click and select properties for the new signature policy. Select the Parameter
Confirmation tab and add the parameters of interest and their associated signature
requirement.
11 - 39
Enable Electronic Signature on the Plant Area where the module you are going to
associate the Electronic Signature policy resides.
11 - 40
Right click the module and select Electronic Signature. From the browse window select
the policy you are going to apply to this module. This ties the message policy to the
SFC-T101 module.
Note: SFC-T101 contains a parameter called MESSAGE used to startup and shutdown
Tank101. Remember to download Setup Data.
11 - 41
The Electronic Signature Data Entry dialog box
shows the comment, confirm, and verify entry box.
11 - 42
Electronic Signature events are logged in the Event Chronicle. Process History View
Event 3 shows an attempted parameter change with a verify failure. Event 2 shows a
similar attempt that was successfully confirmed and verified, and Event 1 shows the
resulting parameter change.
11 - 43
ProfessionalPLUS Station Software
Functionality included Options you can add Options NOT allowed
Configuration Database Basic Batch Continuous Historian,
Configuration Suite Configuration Audit >250 parameters
Control Studio-Online Trail (Version Control) DeltaV Web Server
Continuous Historian, DeltaV Operate for PROVOX- OPC Server, >250 data
Graphics values
< 250 parameters
DeltaV Connect - Bailey Remote Access Server (RAS)
Inspect with InSight
Excel Add-in for Application Station
Tune with InSight OPC Server, 250 data values DeltaV Operate for RS3-
Diagnostics OPC Mirror Graphics
Event Chronicle OPC Pager
Flexlock OPC Alarms & Events Included with appropriate
DeltaV Operate OPC History Server system license
Dual Monitor Remote Client MPC Operate and OperatePro
Process History View Remote Access Server (RAS) Predict and PredictPro
AMS Intelligent Device Neural
Manager*
Recipe Studio
(Client or Server)
Batch Operator Interface
* Installed separately
11 - 44
Professional Station Software
Configuration Suite Tune with InSight Basic Batch
Control Studio-Online Excel Add-in Advance Batch
Continuous Historian, OPC History Server Professional Batch
< 250 parameters AMS Intelligent Device Configuration Audit Trail
Inspect with InSight Manager* (Client) (Version Control)
Diagnostics Configuration Database
Event Chronicle Included with appropriate Continuous Historian,
Flexlock system license >250 parameters
Operator Interface DeltaV Connect - Bailey Interface
MPC Operate and OperatePro
Dual Monitor OPC Server, 250 or >250 data values
Predict and PredictPro
Process History View OPC Mirror
Neural
Recipe Studio OPC Pager
Recipe Studio
OPC Alarms & Events
Batch Operator Interface
Remote Access Server (RAS)
for Application Station or
for Professional PLUS
11 - 45
Maintenance Station Software
Configuration Studio for DeltaV Operate for PROVOX- Basic Batch
Maintenance, Graphics Advance Batch
Continuous Historian, DeltaV Operate for RS3- Professional Batch
< 250 parameters Graphics Configuration Audit Trail
Inspect with InSight Control Studio-Online (Version Control)
Diagnostics Tune with InSight Configuration Database
Event Chronicle Excel Add-in Continuous Historian,
Flexlock Recipe Studio >250 parameters
History View Suite Touchscreen DeltaV Connect - Bailey Interface
DeltaV Operate AMS Intelligent Device DeltaV Web Server
Dual Monitor Manager* OPC Server, 250 or >250 data values
(Client or Server) OPC Mirror
Included with appropriate
system license OPC Pager
MPC Operate and OperatePro OPC Alarms & Events
OPC History Server
* Installed separately for Professional PLUS
11 - 46
Operator Station Software
Continuous Historian, Configuration Suite Basic Batch
< 250 parameters Control Studio-Online Advance Batch
Flexlock DeltaV Operate for PROVOX- Professional Batch
Inspect with InSight Graphics Configuration Audit Trail
DeltaV Operate DeltaV Operate for RS3- (Version Control)
Dual Monitor Graphics Configuration Database
Process History View Tune with InSight Continuous Historian,
Diagnostics >250 parameters
Included with appropriate Event Chronicle DeltaV Connect -Bailey Interface
system license Excel Add-in DeltaV Web Server
MPC Operate and OperatePro OPC History Server OPC Server, 250 or >250 data values
Touchscreen OPC Mirror
Recipe Studio OPC Pager
AMS Intellgent Device OPC Alarms & Events
Manager* (Client) Remote Access Server (RAS)
for Professional PLUS
11 - 47
Base Station Software
Continuous Historian, Configuration Studio Suite Basic Batch
< 250 parameters Control Studio-Online Advance Batch
Inspect with InSight Tune with Insight Professional Batch
Flexlock Diagnostics Configuration Audit Trail
Event Chronicle (Version Control)
Excel Add-in Configuration Database
Operator Interface Continuous Historian,
Process History View >250 parameters
Recipe Studio DeltaV Connect - Bailey Interface
Remote Client DeltaV Inspect
AMS Intelligent Device DeltaV Web Server
Manager* (Client) OPC Server, 250 or >250 data values
OPC Mirror
OPC Pager
OPC Alarms & Events
* Installed separately for Professional PLUS
11 - 48
Application Station Software
Continuous Historian, Continuous Historian, Configuration Audit Trail
< 250 parameters < 20,250 parameters (Version Control)
Excel Add-in DeltaV Connect - Configuration Database
OPC Server <30,000** Bailey Interface Configuration Studio Suite
data values DeltaV Web Server
Control Studio-Online
Basic Batch
Inspect with InSight
Advanced Batch
Professional Batch Tune with InSight
Diagnostics Operator Interface
Event Chronicle OPC Server, 250
Process History View Data values
OPC Mirror Recipe Studio
OPC Pager Remote Access Server (RAS)
OPC Alarms & Events for Professional PLUS
OPC History Server
Web Server
* Installed separately Plantwide Event Historian
** Must specify number AMS Intelligent Device
of values Manager*
(Client or Server)
11 - 49
11 - 50
DeltaV Simulate Suite
DeltaV Simulate lets you use all DeltaV software for training and development without
purchasing duplicate system hardware.
• Allows you to configure the DeltaV software suite on a single PC or in a multi-
node system.
• Allows you to test and execute your system configuration and OPC interfaces,
execute batch and continuous control
• Allows you to easily coordinate and initialize control simulation and set control
execution to be faster or slower than real time.
• Provides an ideal environment to which you may add dynamic process
simulation for operator training and process and control development
11 - 51
DeltaV Simulate consists of a training and development dongle, DeltaV CDs and the
following license options.
• DeltaV Simulate or SimulatePRO — Single PC. A single PC license that can be
used only in a training or development system. No communication support is
provided for connections to other DeltaV nodes.
• DeltaV Simulate ProfessionalPLUS Networked (PPN). Same components as
DeltaV Simulate - Single PC, but license enables communication support with
other DeltaV devices in a training and development system.
• DeltaV Simulate Professional Station (PSN). Allows you to perform engineering
and configuration activities in a multi-node system.
11 - 52
• DeltaV Simulate Application Station Networked (ASN). This license includes all
standard and optional components available for a normal Application Station.
• DeltaV SimulatePRO — Multi-node. This license may be assigned in conjunction
with DeltaV Simulate PPN or DeltaV Simulate-ASN license. The SimulatePRO
capability enables more memory for module execution (of any type) and a user
interface for coordination of module execution.
Note: No hardware is included with DeltaV Simulate.
11 - 53
MiMiC Simulation
MiMiC is a client-server software product with built-in process modeling tools.
Together with user-configured models, mimic comprises a complete process simulation
environment. In this environment, the process configuration may be observed and
analyzed.
• Gives you non-intrusive, real-time process simulation software.
• Allows you to check out your control logic before going online.
• Auto-generates simulation tiebacks.
• Trains operators without impacting your process.
11 - 54
Asset Management Solution (AMS)
The AMS Intelligent Device Manger provides the capability to configure, calibrate,
monitor and troubleshoot intelligent field devices. When installed on a DeltaV
Workstation, the Intelligent Device Manager can be launched for HART/Ff devices on
the DeltaV Explorer.
The system provides the following capability:
• Complete capturing of all current device data
• Comparison/reconciliation
• Device alert monitoring
• Device template creation
• Device signal tag and device tag search capability
• Conventional I/O, HART and Fieldbus-based support
• On-line help
• Diagnostic add-on capability
11 - 55
Workshop – Export
This workshop requires you to Export the configuration database and copy the operator
displays to removable media:
Step 1. From the DeltaV Explorer select Physical Network.
Step 2. Right click and select Export.
11 - 56
Workshop – Export
Step 3. Select a removable drive as the destination, thereby exporting the Physical
Network. Click on Save.
Or
11 - 57
Workshop – Export
Step 4. Export Control Strategies. Select a removable drive as the destination, thereby
exporting the Control Strategies. Click on Save.
11 - 58
Workshop – Export
Step 5. Export Named Sets NS-T101. Select a removable drive as the destination,
thereby exporting NS-T101. Click on Save.
11 - 59
Workshop – Export
Step 6. Export Named Sets phase_failures. Select a removable drive as the destination,
thereby exporting phase_failures. Click on Save.
11 - 60
Workshop – Export
Step 7. Launch Windows XP Explorer by selecting
Start → Programs → Accessories → Windows Explorer
11 - 61
Workshop – Export
Step 8. Copy the Ovw_ref.grf, Tank101.grf, and Tank201.grf files to a removable
drive from the XP Explorer.
DeltaV\DVData\Graphics-iFIX\Pic
Step 9. Remove media and take it home with you.
11 - 62
Optional Workshop – Electronic Signatures
Build an Electronic Signature policy for the message parameter in SFC-T101.
It will require the administrator to confirm and verify a startup or shutdown request
by the operator.
Hints:
1. Enable Signature Policies using System Preferences.
2. Enable Electronic Signatures using the DeltaV Explorer
3. Create a new policy
4. Enable Electronic Signatures on the Plant Area and module
11 - 63
Summary
• Parameter, field, and function security
• Users
• Groups
• Locks
• Flexlock Application
• Electronic Signatures
• Workstation Options
• DeltaV Simulate
• Mimic
• AMS
• DeltaV Export
11 - 64

Delta V Overview

Transféré par

Informations du document

Titre original

Copyright

Formats disponibles

Partager ce document

Partager ou intégrer le document

Options de partage

Avez-vous trouvé ce document utile ?

Ce contenu est-il inapproprié ?

Droits d'auteur :

Formats disponibles

Delta V Overview

Transféré par

Droits d'auteur :

Formats disponibles

DeltaV Overview

EMERSON Process Management Educational Services Copyrighted Material / Reproduction Restricted

Primary Switch Secondary Switch

System Power Supply,

Notes: A server may be required depending on system size.

Remote Interface Unit

Refer to DeltaV Books Online for additional information about DeltaV.

Bulk Power Supply

System Power Supply

2-Wide I/O Carrier

Step 5. Select Windows Desktop from the FlexLock menu bar.

Access Help by clicking the question mark on the DeltaV

Management Execution (OPC)

Integrated, Modular Software

Integrated smart SIS

Intelligent Field Devices

EMERSON Process Management Educational Services Copyrighted Material / Reproduction Restricted

From Tank101 PLM-SHUTDOWN

Area A Area B Area C

FIC-101 FIC-201 FIC-301

EMERSON Process Management Educational Services Copyrighted Material / Reproduction Restricted

Module FIC-20X Function Block PID1

Step 1. Right click on Plant_Area_A → New → Control Module. Enter XV-101 as

Step 8. Select the button to assign the control module to CTLR.

Step 10. Select the button to save the module.

Step 12. Select the button for the on-line view.

Step 13. Select the DO function block.

a. Modify IO_IN to use DST LSO-1

b. Modify the Discrete Alarm to alarm on a value of 0

c. Select the button to assign to your controller

d. Select the button to modify Module Properties displays Primary

e. Select the button to save

f. Select the button to download the module to the controller

g. Select the button and verify that XVSTAT-101 works

Launch DeltaV Operate (Run) by selecting the button.

Pictures created using the

EMERSON Process Management Educational Services Copyrighted Material / Reproduction Restricted

A module created from a Module Template

Instead of this — LEVEL-101/AO1/SP.F_CV

Partial Download (Mode) critical block value (SP) user-defined

Configuration database CAS 500

On-line Value AUTO 555

Preserve critical block AUTO 500

Preserve user-defined and AUTO 555

Use configured values CAS 500

LAALM Latched Alarm R OK/HIGH 0/16

CV Same as LAALM R OK/HIGH 0/16

NALM New Unacknowledged R/W NO/YES 0/1

PRI Priority R/W CRITICAL . . . LOG 15 . . . 3

ENAB Enabled R/W NO/YES 0/1

INV Invert Input R/W NO/YES 0/1

OPSUP Alarm Suppression R/W NO/YES 0/1

SUPTMO Suppression Timeout R/W Time(minutes) Time(minutes)

SUPTMR Suppression Timer R/W Time(minutes) Time(minutes)

Display example: Module/Alarm.Format_Field

DeltaV Alarm Types F_Float DeltaV Alarm Types F_Float

Picture Configuration Data Displayed

Area A Area B Area C Area D Area E Area F

Process History View

EMERSON Process Management Educational Services Copyrighted Material / Reproduction Restricted

Step 5. Assign the module to the controller.

2. New Named Sets (must have 4 names)

EMERSON Process Management Educational Services Copyrighted Material / Reproduction Restricted