Desgning DeltaV - V103

D800016X142
v10.3:March 2009
Planning and Designing Your

DeltaVt Digital Automation System
Including DeltaVt Safety Instrumented Systems
For Version 10.3

Finding a Contents, Figures, Tables, and Index entries in the manual
are hyperlinked to subject pages. In the Acrobat Bookmarks
Subject in sidebar, click on Contents, Figures, Tables, or Index. When
the .pdf the page appears, click on the desired entry on the page to
Edition access the subject.
© 2001, 2003, 2005 2008, 2009 Fisher-Rosemount Systems, Inc. All rights reserved. Unauthorized
duplication, in whole or in part, is prohibited.
Printed in Singapore
Emerson, Emerson Process Management, the Emerson Process Management design, DeltaV, the DeltaV
design, and PlantWeb are marks of one of the Emerson Process Management group of companies. All
other marks are the property of their respective owners. The contents of this publication are presented
for informational purposes only, and while every effort has been made to ensure their accuracy, they
are not to be construed as warranties or guarantees, expressed or implied, regarding the products or
services described herein or their use or applicability. All sales are governed by our terms and
conditions, which are available on request. We reserve the right to modify or improve the design or
specification of such products at any time without notice.
Contents
Welcome . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Internal Audience Only . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
DeltaV Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Operating System Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xi
Keeping Information Updated . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
What’s New in This Edition . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xii
Reference Publications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
Product Data Sheets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
White Papers and Sales Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiii
DeltaV User Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Third-Party Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Sales Wizard Release Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xiv
Warnings, Cautions, and Notes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . xv
Chapter 1 System Sizing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Sizing Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-2
Maximum Size . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-3
Chapter 2 Control Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

Network Information Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
Network Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1
10 Mbps and 100 Mbps Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Network Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-3
Network Topology . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Special No-Hub Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Remote Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Determining Port and Switch Count . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Small Non−Production Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-6
Connecting Printers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Basic Simplex and Redundant Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Simplex Control Network with Simplex Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-7
Simplex Control Network with Redundant Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Redundant Control Network with Simplex Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . 2-8
Redundant Control Network with Redundant Controllers . . . . . . . . . . . . . . . . . . . . . . . . 2-9
System Planning Guide iii

Chapter 3 Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Simplex Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Redundant Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Selecting Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Controller Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Determining the Quantity of Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Controller Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-3
Enforcement of System-Wide Licensing for Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-4
Advanced Unit Management (Batch) Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-5
SCADA Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-6
Chapter 4 I/O Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Available Simplex and Redundant I/O Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Counting DSTs in a Redundant I/O Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-2
Remote I/O Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Zone 1 Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-3
Zone 2 Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-5
Fiber Optic Switches for Remote I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-7
Determining the Quantity of Classic I/O and HART Interfaces . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Determining the Quantity of Serial Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Determining the Quantity of PROVOX I/O Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-8
Determining the Quantity of RS3 I/O Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Determining the Quantity of Multifunction/Pulse Input Interfaces . . . . . . . . . . . . . . . . . . . . . 4-9
Determining the Quantity of SOE Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-9
Determining the Quantity of AS-i Bus Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Determining the Quantity of DeviceNet Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Determining the Quantity of FOUNDATION fieldbus Segments . . . . . . . . . . . . . . . . . . . . . . 4-15
Determining the Quantity of Profibus Segments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-18
Intrinsically Safe I/O Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
I/O Subsystem Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Fieldbus H1 Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-21
Zone 1 Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
DeltaV Interface for PROVOX I/O Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
DeltaV Interface for RS3 I/O Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
DeltaV FlexConnect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-22
Chapter 5 Smart Wireless Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Smart Wireless Field Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1
Communication Protocols — Version 10.3 and Later . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Communication Protocols — Version 9.3 and Earlier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
Modbus Serial Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
iv v10.3:March 2009
Modbus TCP/IP Protocol . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-2
OPC DA . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Using with AMS Device Manager — Version 10.3 and Later . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Using with AMS Device Manager — Version 9.3 and Earlier . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Installation Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-3
Chapter 6 Safety instrumented Systems . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Smart Logic Solvers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
SISNet Repeaters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-2
Workstation Communication . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
SISNet Distance Extenders . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Using Horizontal I/O Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-4
Using Vertical I/O Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Optional Devices . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
End-of-Line Resister Module for Discrete In . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
RC Compensator for Discrete Out . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Dual Channel Voltage Monitor . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-5
Current Limiter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Relay DTA Module and Relay Diode Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Safety Relay Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-7
Chapter 7 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

System Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
VE5001 AC to DC System Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1
VE5009 DC/DC Dual System Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Using Multiple System Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Bulk Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Using VE5011 for Field Power . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-4
Calculating Current Available for Classic I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-5
Redundancy Considerations for VE5011 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Using VE5012 to Power VE5009 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-6
Redundant Combinations of VE5012 and VE5009 Power Supplies . . . . . . . . . . . . . . . . 7-6
Redundancy Considerations for VE5012 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Intrinsically Safe System Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Selecting Uninterruptible Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-8
Chapter 8 Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

Workstation Licensing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Four-Monitor License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1
Operator Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
System Planning Guide v

Batch Application License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Remote Access Services (RAS) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
Remote Client (Terminal Server) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-3
DeltaV Connect License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
FlexConnect Solutions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
Continuous History Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-4
DeltaV Analyze License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-5
DeltaV Insight Basic and DeltaV Insight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
AMS Device Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-6
Third-Party Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-7
Workstation Application Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
ProfessionalPLUS Station Software Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-10
Professional Station Software Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-12
Operator Station Software Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-14
Base Station Software Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-16
Application Station Software Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-18
Maintenance Station Software Suite . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-20
Workstation Application Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-22
Connecting to a Plant LAN . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-23
DeltaV Zones . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-24
Chapter 9 Computer Selection and Security . . . . . . . . . . . . . . . . . . . . 9-1

Hardware Classes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-1
PC Selection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
ProfessionalPLUS Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Professional Workstation, Operator Workstation, and Maintenance Workstation . . . . . . 9-2
Base Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-2
Application Workstation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-3
Windows Domain Security and Login Accounts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-4
Cyber Security for Dell PCs Used in DeltaV Systems . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9-5
Chapter 10 Hardware Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

OEM Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Site Preparation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-2
AC Power Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-3
Power Requirements for a Controller and I/O Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Mounting DeltaV Systems in Enclosures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-7
Power Dissipation Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-11
Enclosure Selection Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-14
Example Enclosure Selection Calculation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
vi v10.3:March 2009
Physical Dimension Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-15
Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-18
Horizontal Carrier Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-19
VerticalPLUS I/O Carrier Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-24
Legacy Vertical I/O Carrier Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-26
Appendix A System Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Summary of Capacities and Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1
System Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-3
Batch Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
System Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-4
Capacity for All Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
ProfessionalPLUS Workstation Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-5
Operator Workstation Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Application Workstation Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-6
Professional, Maintenance, and Base Workstation Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Controller and I/O Subsystem Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-9
I/O Bus System Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Zone 1 and Zone 2 Remote I/O Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
Smart Wireless Gateway Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-11
SIS System Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-12
Appendix B Product Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

European Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
CSA Certification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Environmental Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1
Appendix C Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

Data Values . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
DeltaV Node . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
Device Signal Tags (DSTs) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1
DSTs in Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-2
DSTs in Fieldbus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
DSTs in Serial I/O . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
DSTs in Application Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-4
Applying DSTs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-5
Device Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
SCADA Tags . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-6
Index . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Index-1
System Planning Guide vii

This page intentionally left blank.
viii v10.3:March 2009

Figures
Figure 1-1 Minimum Set of Components in a DeltaV System . . . . . . . . . . . . . . . . . . . 1-1
Figure 1-2 Maximum Set of Components in a DeltaV System . . . . . . . . . . . . . . . . . . . 1-3
Figure 2-1 Simplex Control Network with Simplex Controller . . . . . . . . . . . . . . . . . . . 2-7
Figure 2-2 Simplex Control Network with Redundant Controllers . . . . . . . . . . . . . . . . 2-8
Figure 2-3 Redundant Control Network with Simplex Controller . . . . . . . . . . . . . . . . . 2-8
Figure 2-4 Redundant Control Network with Redundant Controllers . . . . . . . . . . . . . . 2-9
Figure 3-1 Simplex Controller . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-1
Figure 3-2 Redundant Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3-2
Figure 3-3 Example of Advanced Unit Management Licensing . . . . . . . . . . . . . . . . . . 3-5
Figure 4-1 AS-i I/O Network in a DeltaV System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-10
Figure 4-2 Typical AS-i Segment Configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-11
Figure 4-3 Example Network Consisting of Multiple Repeaters and Segments . . . . . . 4-11
Figure 4-4 DeviceNet Segment In a DeltaV System . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-13
Figure 4-5 FOUNDATION fieldbus Segment in a DeltaV System . . . . . . . . . . . . . . . . 4-17
Figure 4-6 Profibus Segment in a DeltaV System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-19
Figure 4-7 Intrinsically Safe I/O Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-20
Figure 5-1 Outline Dimensions for Gateway Mounting . . . . . . . . . . . . . . . . . . . . . . . . 5-4
Figure 5-2 Outline dimensions for Antenna Mounting . . . . . . . . . . . . . . . . . . . . . . . . . 5-5
Figure 6-1 Safety Instrumented System Integrated into a DeltaV System . . . . . . . . . . 6-3
Figure 6-2 Dimensions and Extender Cables with SISNet Repeaters on
VerticalPLUS I/O Carriers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6-6
Figure 7-1 VE5001 AC to DC System Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . 7-2
Figure 7-2 VE5009 DC/DC Dual System Power Supply . . . . . . . . . . . . . . . . . . . . . . . . 7-3
Figure 7-3 Calculating Current Required from Bulk Power Supplies . . . . . . . . . . . . . . 7-5
Figure 7-4 Redundant Combination of VE5009 and VE5012 for Simplex Controllers 7-7
Figure 7-5 Redundant Combination of VE5000 and VE5012 for Redundant
Controllers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-7
Figure 8-1 Simple Inter-Zone Control Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-25
Figure 10-1 Enclosure Example for Controller and 8 I/O Interfaces . . . . . . . . . . . . . . . . 10-8
Figure 10-2 Enclosure Example for Controller and 24 I/O Interfaces . . . . . . . . . . . . . . . 10-9
Figure 10-3 Enclosure Example for Vertically Mounted I/O Carriers . . . . . . . . . . . . . . . 10-10
Figure 10-4 Calculated Dimensions of Controller I/O Assembly . . . . . . . . . . . . . . . . . . 10-19
Figure 10-5 Width of 2-wide Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Figure 10-6 Width of 8-wide Carrier . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-20
Figure 10-7 One 2-wide Carrier and One 8-wide Carrier Connected . . . . . . . . . . . . . . . 10-21
Figure 10-8 Two 2-wide Carriers and One 8-wide Carrier Connected . . . . . . . . . . . . . . 10-21
Figure 10-9 Extender Cable Connecting Two 8-wide Carriers On Same Level . . . . . . . 10-22
System Planning Guide ix

Figure 10-10 Extender Cable Connecting Two 8-wide Carriers On Stacked Levels . . . . 10-22
Figure 10-11 Horizontal Carriers Connected Together . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-23
Figure 10-12 Dimensions and Connected Extender Cables on VerticalPLUS I/O Carriers 10-25
Figure 10-13 Dimensions for Legacy Vertical I/O Carriers . . . . . . . . . . . . . . . . . . . . . . . . 10-27
Figure 10-14 Connecting Extender Cables on Legacy Vertical I/O Carriers . . . . . . . . . . 10-28
Figure C-1 Relationship Between I/O and Controllers to Count DSTs . . . . . . . . . . . . . C-2
x v10.3:March 2009
Tables
Table 2-1. Maximum Cable Lengths by LAN Types . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-4
Table 2-2. Maximum Distances Between Any Two Nodes Using Combinations of
Copper and Fiber Optic Cables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-5
Table 4-1. Available DeltaV I/O Cards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1
Table 8-1. Workstation Node Types and Supported Software Suites . . . . . . . . . . . . . . 8-1
Table 8-2. System-Wide Licenses for Batch Systems . . . . . . . . . . . . . . . . . . . . . . . . . . 8-2
Table 8-3. Applications Included, Can Be Added, or Not Available in Software
Suites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-8
Table 8-4. ProfessionalPLUS Station Software Suite, VE2101Sxxxx* . . . . . . . . . . . . 8-11
Table 8-5. Professional Station Software Suite, VE2102Sxxxx* . . . . . . . . . . . . . . . . . 8-13
Table 8-6. Operator Station Software Suite, VE2104Sxxxx* . . . . . . . . . . . . . . . . . . . . 8-15
Table 8-7. Base Station Software Suite VE2106 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-17
Table 8-8. Application Station Software Suite VE2201Sxxxx* . . . . . . . . . . . . . . . . . . 8-19
Table 8-9. Maintenance Station Software Suite VE2105 . . . . . . . . . . . . . . . . . . . . . . . 8-21
Table 8-10. Workstation Applications and Their Prerequisite Application . . . . . . . . . . 8-22
Table 10-1. AMP Cable Management Accessories . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1
Table 10-2. AC Current Draw for Control Network Products and Power Supplies . . . . 10-3
Table 10-3. DC Current Requirements for I/O Cards . . . . . . . . . . . . . . . . . . . . . . . . . . 10-4
Table 10-4. Maximum Power Dissipation for DeltaV Products . . . . . . . . . . . . . . . . . . 10-11
Table 10-5. Example Products in the Selection Calculation . . . . . . . . . . . . . . . . . . . . . . 10-15
Table 10-6. Dimensions and Weights . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-16
Table A-1. Function Blocks Which Can Be Assigned in ProfessionalPLUS and
Application Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-7
Table B-1. DeltaV System Temperature and Humidity Specifications . . . . . . . . . . . . B-1
Table B-2. DeltaV System Contaminants, Vibration, and Shock Specifications . . . . . . B-4
System Planning Guide xi

xii v10.3:March 2009

Welcome
The DeltaV System Planning Guide contains information which helps you build a
correct bill of materials for a DeltaV system. This manual includes product
explanations, specifications, licensing requirements, appropriate planning and
design information, and special things you need to consider.
Note ... While this manual contains information you need to make informed
decisions for a bill of materials, it does not include information on all
available DeltaV products or their specifications. See the DeltaV intranet
web site or the latest DeltaV WebCD for all product data sheets and complete
product information.
Internal Audience Only

This manual is intended for sales and service personnel at Emerson Process
Management Local Business Partners and Field Sales Offices (LBP/FSO), and
company personnel of Emerson Process Management. The Information in this
manual should be considered as Confidential, Internal Use Only. The manual is
not intended for distribution to persons outside of the organizations noted.
DeltaV Version
This manual provides planning information for DeltaV version 10.3. This version
contains enhancements not available in earlier versions. When adding
functionality to an existing DeltaV system, keep in mind the functionality which
the existing system can handle.
Operating System Compatibility

DeltaV version 10.3 is compatible with Microsoft Windows XP, as are versions
back through 7.3. Versions 7.2 and earlier are compatible with Microsoft Windows
NT4. Keep this in mind when ordering buyout hardware and software, and when
adding to or replacing components in an existing DeltaV system.
System Planning Guide xiii

Keeping Information Updated
Between releases of this manual, updated planning information may be added to
the DeltaV website so that the latest planning information is available for you. It
is suggested that you periodically check the website to see what updates may
have been added. Updates added to the website are subsequently incorporated
into future versions of this manual. The website may be found at the Emerson
Process Management intranet: http://mydeltav.emersonprocess.com.
What’s New in This Edition

The following changes have been made to this edition from previous editions:
H Chapter 2 Updated list of available DeltaV network equipment.
H Chapter 3 Added references to DeltaV MX controller.
H Chapter 3 Added information about Advanced Unit Management licensing.
H Chapter 5 Added new chapter about Smart Gateway.
H Chapter 7 Added information about VE5009 System Power Supply.
H Chapter 8 Added explanation about DeltaV FlexConnect Solutions.
H Chapter 8 Corrected information in Table 7−3, Applications Included, Can Be

Added, or Not Available in Software Suites.
H Chapter 9 Included latest Dell computer and server information. Check the
factory for transition dates from former to latest offerings.
H Chapter 10 Updated AC current draw, power dissipation, and weights and

measures tables.
H Appendix A Updated Capacity tables.
H Appendix B Updated Environmental Specifications tables.
H Appendix C Expanded definition for Device Signal Tags (DSTs).
xiv v10.3:March 2009

Reference Publications
Throughout this manual, references are made to other publications, both DeltaV
and third-party, that provide supporting technical information you need for
system planning. In some cases, your ability to correctly use the information in
this manual depends on your understanding of the information in the other
publications. Many of these publications can be found on the DeltaV intranet
website and on the DeltaV WebCD.
Product Data Sheets

DeltaV product data sheets provide product descriptions, features, benefits,
specifications, and ordering information. Please have the sheets ready for
reference when you plan your system. For convenience, some product
specifications are included in this manual, but this manual is not intended to
duplicate product data sheets. The sheets are available on the DeltaV intranet
website and on the DeltaV WebCD. Look for the Sales Documents selection.
White Papers and Sales Information

Many white papers and sales information papers are available on the DeltaV
intranet website and on the DeltaV WebCD. These papers add considerably to
your understanding of DeltaV systems and items important to system planning.
Some very important papers are DeltaV Power Considerations, Redundant I/O,
Workstation Sizing Spreadsheet, Controller Redundancy, Controller Loading
Estimator, and various intrinsic safety papers.
The DeltaV Power Considerations paper provides an overview of power

requirements for DeltaV systems. The Workstation Sizing Spreadsheet provides an
organized way to help you determine workstation requirements and the licenses
needed to obtain the desired user interface and process control. The Controller
Loading Estimator provides an indication about the fit of DeltaV controllers to
your application.
System Planning Guide xv

DeltaV User Documentation
Other technical information, such as Control Network design, FOUNDATION
fieldbus installation requirements, intrinsic safety applications, and so forth is
contained in DeltaV user documentation, which includes:
H Installing Your DeltaV Digital Automation System
H Installing Your DeltaV Safety Instrumented System Hardware
H DeltaV Safety Instrumented System Safety Manual
H Fieldbus Installations in a DeltaV Digital Automation System
H Site Preparation and Design for DeltaV Digital Automation Systems
H Getting Started with your DeltaV Digital Automation System
H Books Online (BOL) electronic books built into each DeltaV system
Third-Party Information
Most third-party vendors of products used with DeltaV systems have web sites
available from which you can copy or purchase specifications. Some sites are:
H AS-i Interface http://www.as−interface.com/
H DeviceNet http://www.odva.org/
H Foundation fieldbus http://www.fieldbus.org/
H HART Foundation http://www.hartcomm.org/
H Profibus http://www.profibus.com/
Sales Wizard Release Notes

Sales Wizard Release Notes keep you up to date on product changes for each
DeltaV release. Release notes include lists of new products with their licenses,
deactivated licenses, and product availability status changes.
xvi v10.3:March 2009

Warnings, Cautions, and Notes
Warnings, Cautions, and Notes attract attention to essential or critical information.
The type of information included in each is:
Warning... All warnings have this form. Do not disregard warnings. They are
installation, operation, or maintenance procedures, practices, conditions,
statements, and so forth, which if not strictly observed, may result in
personal injury or loss of life.
Caution... All cautions have this form. Do not disregard cautions. They are
installation, operation, or maintenance procedures, practices, conditions,
statements, and so forth, which if not strictly observed, may result in
damage to, or destruction of, equipment or may cause long term health
hazards.
Note ... All notes have this form. Notes contain installation, operation, or
maintenance procedures, practices, conditions, statements, and so forth,
that alert you to important information which may make your task easier
or increase your understanding.
System Planning Guide xvii

xviii v10.3:March 2009

System Sizing Overview
Figure 1-Table 1
Chapter 1 System Sizing Overview
DeltaVt Digital Automation Systems can be efficiently scaled over a wide range
of process control system sizes. Figure 1-1 shows a minimum set of components
for a DeltaV system, consisting of one workstation, one controller, and associated
equipment. Figure 1-2 illustrates a maximum number of workstations and
controllers with associated equipment.
Professional PLUS 24 VDC Bulk

Workstation Power Supply
Control Network
Switch
I/O Subsystem
System Controller
Power
Supply
Figure 1-1 Minimum Set of Components in a DeltaV System
A DeltaV system includes, at least:
H A control network that provides communication between workstations and

controllers.
H A ProfessionalPLUS workstation that provides a graphical user interface to the

process and system configuration functions.
H A controller that performs control and manages communications between the

I/O subsystem and the control network.
H An I/O subsystem that processes information to and from field devices.
H A system power supply for powering controllers and I/O cards
System Planning Guide 1-1

H A bulk power supply (or 24 VDC plant power) for powering field devices
connected to the DeltaV system.
H DIN-rail mounted carriers that connect power and network communications

to controllers and I/O subsystem.
Sizing Considerations
To determine the required size of a DeltaV system, the following items must be
considered:
H Total Device Signal Tag (DST) count
H Total SCADA tag usage

The total count for SCADA tags is unlimited. However, when using thousands
of them in workstations already heavily loaded with other data items,
workstation performance may be slower than acceptable. See Appendix C for
the definition of SCADA tags as they are used for DeltaV systems.
H Total FOUNDATION fieldbus or other I/O bus system device tag count
H Total number of workstations required

This number is typically driven by the number of Operator Stations desired at
the facility, with one or two more, depending on the number of Application
Stations requested.
H The geographical nature of the system

The geographical layout of the system can influence the number of
controllers needed.
H The percentage of spare capacity desired in controllers from an I/O

perspective
H Whether or not DeltaV batch will be used
1-2 v10.3:March 2009

Maximum Size
As illustrated in Figure 1-2, a DeltaV system can be scaled to include many
workstations, controllers and associated power supplies, and I/O subsystems,
including Classic I/O, HART I/O, and I/O bus systems. Systems can be simplex or
redundant.
Note ... Each system must include one and only one ProfessionalPLUS workstation.
See Appendix A for a complete list of capacities. See Appendix C for definitions
of DST, Data Values, and other terms, as they are used for DeltaV systems.
Note ... Although 160 nodes are implied in the figure, DeltaV system capacity is 120
nodes. A system can contain up to 65 workstation nodes and up to 100
controller nodes, but not more than a total of 120 nodes. See Appendix A
for system capacity details.
Workstation #1
Professional PLUS
Station Workstation #2 . . . . . . . . . . . . . . . . . . . . . . . .. Workstation #64
Switch
24 VDC Bulk 24 VDC Bulk

System Power Supply System Power Supply
Power Power
Supply Supply
I/O Subsystem I/O Subsystem

Controller #1 . . . . . . . . . . . . . . . . . . . . Controller #100
Figure 1-2 Maximum Set of Components in a DeltaV System

1-4 v10.3:March 2009

Control Network
Figure 2-Table 2
Chapter 2 Control Network
The DeltaV Control Network is an IEEE 802.3 Ethernet local area network (LAN)
dedicated to the DeltaV system. The network provides communication between
controllers and workstations.
Network Information Sources

The control network descriptions below use standard Ethernet network
terminology and network design practices. If you wish to review Ethernet
concepts, see the web site at:
http://www.ether manage.com/ethernet/
Note ... This chapter provides information for DeltaV control network planning.
Before you design a control network, read the Control Network
Specifications section and study the examples of various control networks in
the manual, Installing Your DeltaV Digital Automation System. If, after
reviewing specifications and examples, the terminology is not familiar, or if
the network is particularly large or complex, it is recommended that you
contact an expert consultant for network design.
Network Equipment
High-quality third-party vendor switches, screened twisted-pair (ScTP) cable,
shielded and non-shielded RJ45 connectors which meet Category 5E specifications
or better are required to build a DeltaV control network. The following items are
currently available from Emerson Process Management:
H 10/100 Unmanaged Switches

j Ethernet Switch with one 100Base-FX port (MT-RJ Connector) and four
10/100Base-TX ports (RJ45 Connector) This switch is primarily used for
a fiber port connection to Remote Zone 1 components.
j Ethernet Switch with four 100Base-FX port (MT-RJ Connector) and one
10/100Base-TX ports (RJ45 Connector) This switch is primarily used for
a fiber port connection to Remote Zone 1 components.

Control Network
j Allied Telesyn AT-FS708 8-Port 10/100Base-TX Ethernet Switch
j Allied Telesyn AT-FS709FC 8-Port 10/100Base-TX Ethernet Switch with

one 100Base-FX port supporting up to 2 km of fiber
H 10/100 Managed Switches

j Cisco Catalyst 2960−48TC−L 48-Port 10/100Base-TX Fast Ethernet Switch
with two SFP Slots
j Cisco Catalyst 2960-24TC-L 24-Port 10/100Base-TX Fast Ethernet Switch

with two SFP Slots
j Cisco Catalyst 2960-8TC-L 8-Port 10/100Base-TX Fast Ethernet Switch with

one SFP Slot
j Cisco Catalyst 2960-24 TT-L 24-Port 10/100Base-TX Fast Ethernet Switch

with two 10/100/1000 Ports
j Cisco Catalyst 2960-48TT-L 48-Port 10/100Base-FX Fast Ethernet Switch

Note ... 1000 Mbps (1Gigabit) communication noted in the selections below is only
used between switches. Communication between nodes (controller,
workstation) and switches is either 10 Mbps or 100 Mbps.
H 10/100/1000 (Gigabit) Managed Switches

j Cisco Catalyst 3750-24FS 24-Port 100Base-FX Fiber Optic Switch with two
1-Gigabit Interface Converter Ethernet Ports
j Cisco 3750-24-TS-S 24-Port 10/100Base-TX Fast Ethernet Switch with two

slots for Gigabit Transceivers
j Cisco 3750G12S-S 12 Slot Gigabit Switch (uses any combination of

transceivers listed below).
H 10/100/1000 (Gigabit) Transceivers

j Cisco GLC-SX-MM Gigabit Transceiver Module (Up to 550 m of fiber optic
cable)
j Cisco GLC-LH-SM Gigabit Transceiver Module (Up to 10 Km of fiber optic

cable)
2-2 v10.3:March 2009

Control Network
j Cisco GLC-T Gigabit Transceiver Module (Up to 100 m of copper cable)
Note ... DeltaV systems require specific versions of vendor switch software and
special switch configurations. The use of other versions of switch software or
incorrect switch configurations can cause serious degradation in DeltaV
system operation. Their use is not recommended.
Switches ordered from Emerson Process Management are shipped with the
supported software version and pre-configured switch configurations. To ensure
that you have the correct software and proper configuration, purchase switches
through normal factory channels. Switches obtained directly from non-DeltaV
sources may not contain DeltaV supported switch software and may be
impossible to re-program for suitable operation with a DeltaV system.
10 Mbps and 100 Mbps Selection

Early DeltaV controllers through the M5 Plus controller are half-duplex devices
which communicate over a DeltaV Control Network at 10 Mbps. When DeltaV
workstations are connected to 10 Mbps switches, they also communicate at
10 Mbps. Earlier DeltaV controllers can be connected to dual speed 10/100 Mbps
switches, but communicate at 10 Mbps.
MD, MD Plus and MX controllers and DeltaV workstations communicate at

half-duplex or full-duplex (auto-negotiating) and at 10 Mbps or 100 Mbps
(auto-sensing), depending on the system sensed. When two or more MD, MD
Plus, Or MX controllers are used in conjunction with Sequence of Events (SOE)
cards, 100 Mbps switches are required.
Network Considerations
The simplest DeltaV system consisting of one workstation and controller can use
a single connecting cable. Most small DeltaV systems are somewhat larger than
the simplest one and use at least one switch with interconnecting cables.
Larger DeltaV systems normally use multiple switches with a variety of cables. The
manual, Installing Your DeltaV Digital Automation System, shows many examples
of copper cable and fiber optic networks, using several types of switches.

Control Network
When you design a control network, consider:
H Node types are ProfessionalPLUS, Operator, or Application workstation,

Inter-Zone Server, and controller. When workstations, inter-zone servers, or
controllers are operating in redundant mode, each pair is counted as one
node. Therefore, there can be more physical connections than nodes. For
example, a redundant controller requires two switch ports, but is counted as
one node.
H To ensure DeltaV system reliability and performance, non-DeltaV devices and

other networks must not be connected to a DeltaV control network. Integrate
non-DeltaV devices and other networks into a DeltaV control network only
through a DeltaV Application Workstation. Be sure to follow the instructions
for adding non-DeltaV devices to a DeltaV control network as described in
Knowledge Based Article (KBA) NA-0500-0059, Using the CISCO Model 3750
Series Switches with DeltaV, Section 6, Approved IP Addresses for Switches and
non-DeltaV Devices.
H All DeltaV workstations and controllers have redundant control network ports
as a standard feature. When installed in a simplex control network, the
redundant port of each device is not used.
Network Topology
The DeltaV control network can be configured in a daisy-chained (cascaded)
technology, a star topology, or a combination of the two. Table 2-1 lists maximum
cable lengths allowed in a DeltaV control network. The lengths conform to IEEE
802.3 Local and Metropolitan Area Network standards.
Table 2-1. Maximum Cable Lengths by LAN Types

Cable Type Maximum Length
per Hop
10Base-T and 100Base-T Cat 5 Screened, Twisted-Pair 100 m (330 ft.)
copper cable (half-duplex, end to end) or 1 Gigabit Cisco
GLX-T Transceiver Module
1 Gigabit Cisco GLC-SX-MM Transceiver Module 550 m (1805 ft)
100Base-FX Full-Duplex Fiber Optic cable (using switches) 2 km (6560 ft.)
1 Gigabit Cisco GLC-LH-SM Transceiver Module 10 km (32,800 ft)
2-4 v10.3:March 2009

Control Network
Hops let you extend a control network. A hop is a data link between a hub or
switch and another hub or switch, and between a hub or switch and a controller
or workstation. The maximum number of hops depends upon transmission speed
and whether a hub or switch is used. Across an entire system, hubs and switches
can be daisy-chained up to a maximum of:
H 4 hops for hubs in a 10 Mbps system (including fiber optic extensions)
H 2 hops for a hubs in a 100 Mbps system (including fiber optic extensions)
H 6 hops for switches, any speed (including fiber optic extensions)
The number of nodes in a combination daisy-chain and star configuration is

limited by the maximum node count in a DeltaV system 120 nodes.
Table 2-2 shows maximum distances between any two DeltaV nodes.
Table 2-2. Maximum Distances Between Any Two Nodes Using Combinations
of Copper and Fiber Optic Cables
Network Device Copper Only Cable Copper and Fiber
Optic Cable
10 Mbps Hubs, Half-Duplex, Four Hops 500 m (1640 ft) 2.5 km (8200 ft)
Maximum
10/100 Mbps Switches, Half-Duplex and 100 m (328 ft) Various extended
Full-Duplex Auto-Negotiation, Two-Hops distances (1)
Maximum
1. Extended distances are possible with fiber optic extenders and transceiver modules. Consult
vendor manuals, the manual “Installing your DeltaV Digital Automation System”, and the factory
for information.
Special No-Hub Cable

For DeltaV systems containing one workstation and one simplex controller, such
as demo" or training systems, and the distance between the workstation and
controller is no greater than 100 meters, a special crossover cable can be
constructed. The cable plugs directly between the workstation and the controller.
See the manual, Installing Your DeltaV Digital Automation System, for
construction details.

Control Network
Remote Network
A DeltaV Remote Network is an Ethernet 10/100BaseT local area network (LAN)
which provides communications between remote workstations and a DeltaV
system. The network can be a dedicated LAN that contains only DeltaV remote
workstations, or it can be a plant-wide LAN that contains other personal
computers or Ethernet devices, such as printers. See the manual, Installing Your
DeltaV Digital Automation System, for further information and illustrations.
Determining Port and Switch Count

The port and switch count required for your system depends on the quantity of
workstations and controllers in the system. To determine the count, first
determine the port count required for a simplex control network. Then, taking the
total quantity of nodes into consideration, convert the port count into a switch
count. For redundant control networks, double the count.
Calculate the required port count as follows:
Total quantity of workstations + total quantity of simplex controllers + 2 X

(quantity of redundant controllers) = required port count.
Calculate the quantity of nodes required as follows:
Total quantity of workstations + total quantity of simplex controllers + total

quantity of redundant controllers = total quantity of nodes.
Small Non−Production Systems

Small non-production systems, such as demo" or training systems, with eight or
less Ethernet nodes should use the 8-port switch.
2-6 v10.3:March 2009

Control Network
Connecting Printers
Microsoft Windows operating systems contain many built-in printer drivers.
Printers which can be run with these drivers normally operate correctly with
DeltaV systems, other than possible effects on workstation loading. Printers can
be connected to the same plant LAN as a workstation or directly to the
workstation. Sometimes, printers connected directly to a LAN require an interface
device.
When a printer is connected to a workstation which is connected to a LAN, other

workstations on the LAN can print to the printer. Be aware that printing activity
will significantly increase CPU loading on the workstation with the connected
printer which may cause slow operating-data updates on that workstation. Print
resources should never be shared across a DeltaV control network.
Basic Simplex and Redundant Systems

Simplex and redundant systems use single or multiple switches to achieve the
required levels of simplex or redundant operation. Four examples of basic
simplex and redundant systems are given below.
Simplex Control Network with Simplex Controllers

As shown in Figure 2-1, the basic simplex control network consists of a switch
and cables which connect a workstation node and a controller node.
Simplex Controller
ProPLUS
Station
Switch
Figure 2-1 Simplex Control Network with Simplex Controller

Control Network
Simplex Control Network with Redundant Controllers

A simplex control network can be used with redundant controllers as shown in
Figure 2-2. Note that the redundant controller uses two switch ports; however, the
redundant controller is still considered one node.
Note ... The arrangement of Figure 2-2 is shown because it is possible, but it is not
recommended. A simplex control network becomes a single point of
communication failure for the redundant controllers.
Redundant Controllers
ProPLUS
Station
Switch
Figure 2-2 Simplex Control Network with Redundant Controllers
Redundant Control Network with Simplex Controllers

Network redundancy for communications reliability is provided by a secondary
switch that establishes a secondary control network identical to the primary
control network. The secondary network is connected to the redundant
communications port of each workstation and controller, and includes a separate,
secondary switch as shown in Figure 2-3.
Simplex Controller
ProPLUS
Station
Primary Switch
Secondary Switch
Figure 2-3 Redundant Control Network with Simplex Controller
2-8 v10.3:March 2009

Control Network
Redundant Control Network with Redundant Controllers

A redundant control network connected to redundant controllers is shown in
Figure 2-4. Although there are two network connections to the workstation and
the controller, there is only one workstation node and one controller node.
ProPLUS Redundant Controllers

Station
Primary Switch
Secondary Switch
Figure 2-4 Redundant Control Network with Redundant Controllers

Control Network
2-10 v10.3:March 2009

Controllers
Figure 3-Table 3
Chapter 3 Controllers
Simplex Controllers
A simplex controller consists of a controller card and system-wide I/O based
controller licenses. The controller can be configured to perform the function you
need, such as data acquisition, calculation control, sequence control, regulatory
control, or batch control. Specific functionality depends on the controller license
installed. See Controller Licensing below for selection guidelines.
Figure 3-1 illustrates a simplex controller card in a small DeltaV system. The
controller card installs on a 2-wide power/controller carrier with a system power
supply.
ProfessionalPLUS
Workstation 2−Wide Carrier with
Controller and System Controller
Power Supply
Switch
Figure 3-1 Simplex Controller
Redundant Controllers
A redundant controller consists of two controller cards, the same system-wide
controller licenses as used for simplex controllers, and a controller redundancy
license. Figure 3-2 illustrates redundant controllers installed on a 2-wide
power/controller carrier.

Controllers
ProfessionalPLUS
Workstation Two 2-Wide Carriers with
Controllers and Power Supplies
Primary Switch
Secondary Switch
Figure 3-2 Redundant Controllers
Selecting Controllers
MD, MD Plus, and MX controllers are available for DeltaV version 10.3. MD Plus
controllers have more memory and higher performance than MD controllers. And
MX controllers have more memory and higher performance than MD Plus
controllers. Refer to the Controller Loading Estimator on the DeltaV WebCD to
obtain an indication of which controller is recommended and the required
quantity of controllers.
Note ... An MD Plus controller only runs on DeltaV v8.3 and later systems. An MX
controller only runs on DeltaV v10.3 and later systems. Neither are
backward compatible to earlier systems.
Controller Carriers
Controllers mount on either 2-wide or 4-wide power/controller carriers. Two-wide
carriers are used when I/O cards are mounted on a horizontal carrier, and 4-wide
carriers are used when I/O cards are mounted on vertical carriers. For horizontally
mounted I/O cards, order one 2-wide carrier for each simplex controller or two
2-wide carriers for each redundant controller. For vertically mounted I/O cards,
order one 4-wide carrier for either simplex or redundant controllers. Further
information about carriers is given in Chapters 4 and 10. Also, see the I/O
Subsystem Carriers product data sheet for further information.
3-2 v10.3:March 2009

Controllers
Determining the Quantity of Controllers

The application determines the quantity of controllers your control strategy
requires: that is, you may need to divide the total application into multiple
controllers. To determine the required quantity of simplex or redundant
controllers, consider the following:
H Some applications require a widely dispersed system with field-mounted

controllers connected to small pockets of I/O. In these applications,
geographical considerations determine the controller count.
H Some applications use a central I/O room. In these applications, I/O capacity
and CPU capacity determine the controller count.
H If an application requires more DST capacity than a single controller (either

simplex or redundant) can handle, add additional controllers. See Appendix A
for controller capacities.
Controller Licensing
Controller licensing is system-wide, and is based on the types of I/O in your
system. Determine the types of I/O and the total quantity of DSTs used for
control, and then purchase sufficient licenses of each type to meet the total DST
quantity. The four I/O licenses are:
H Discrete Monitor Input (VE3111Sxxxxx)
H Discrete Control Output (VE3112Sxxxxx)
H Analog Monitor Input (VE3113Sxxxxx)
H Analog Control Output (VE3114Sxxxxx)

The licenses are assigned to a ProfessionalPLUS workstation only.
To determine the quantity of Discrete Monitor Input licenses required, determine

the quantity of discrete input signals coming into the DeltaV system via
conventional I/O, I/O bus, Serial I/O, and OPC. Then, subtract the quantity of
discrete signals used for display-only from the total quantity coming in. The
remainder determines the size of the VE3111Sxxxxx Discrete Monitor Input
licenses required. This same logic applies to the other licenses.

Controllers
Since it can be difficult to determine the exact count of licenses needed when a
system is purchased, certain licenses can cover for" other ones. That is, any
excess DO licenses can be used to cover a shortage of DI licenses. Likewise,
excess AI licenses can cover for a shortage of DO or DI licenses, and an excess of
AO licenses can cover for a shortage of DI, DO, or AI licenses.
When redundant controllers are used, the VE31RED Controller Redundancy

license is required. A serial port license is not required in DeltaV v9.3 and later.
Licensing for controllers used in the DeltaV Interface to PROVOXr I/O and in the
DeltaV Interface to RS3t I/O is the same as described above for controller
licensing.
Enforcement of System-Wide Licensing for Controllers

System-wide controller licenses reside in the ProfessionalPLUS station. The system
checks the entire configuration database at the time of download to determine if
the configured DST counts are within the sizes of the system-wide licenses. DSTs
are in a hierarchy with AO DSTs as the highest type, then AI DSTs, DO DSTs, and
DI DSTs in that order.
The system does not permit a download if either:
H The total DST count exceeds the ProfessionalPLUS station license size, or
H The number of any of the DST types as AO, AI, DO, DI exceeds the
system-wide control license size for that type of DST and enough unused
DSTs of a higher type are not available to make up the difference.
For example, a system is licensed for 25 AO DSTs and 25 AI DSTs, but is

configurated for 20 AO DSTs and 27 AI DSTs. Though the configuration exceeds
the licensed AI DST limit, the download is permitted because there are enough
licensed, but unused, AO DSTs to make up the difference.
If the system contains classed-based units, one more check is made before the
download is permitted. This check counts DSTs configured and associated with
class-based units and compares the quantity with the DST size of the system-wide
Advanced Unit Management license. A download will not occur if the DST count
exceeds the size of the Advance Unit Management license.
3-4 v10.3:March 2009

Controllers
Advanced Unit Management (Batch) Licensing

The Advanced Unit Management license (VE3009Sxxxxx) is a system-wide
controller license that allows you to create class-based units, typically used in
batch control. Class-based units provide the phase logic structure and the
embedded interface to the batch executive.
The quantity of DSTs in each unit is the sum of all AO, AI, DO, and DI DSTs
assigned to the unit. The Advanced Unit Management license must be sized equal
to or greater than the total DSTs associated with all class-based units.
Figure 3-3 illustrates a logical representation of class-based units and controller

modules. Each class-based unit takes on the total DST count of all of the modules
assigned to it. As illustrated, Class-based Unit #1 has a DST count of 300 made up
of 250 AO, AI, DO, and DI DSTs in one controller module plus 50 AO, AI, DO,
and DI DSTs in the other module. Also, as shown, Class-based Unit #2 has 400
DSTs and Class-based Unit #3 has 200 DSTs. The advanced Unit Management
license that allows the creation of these class-based units must be equal to or
greater than the sum of the DSTs assigned to the class-based units. In this
example, the sum of all DSTs assigned to the class-based units is 900. Therefore, a
900 DST or greater license is required.
Advanced Unit Management License

(900 DSTs)
Class-Based Unit #1 Class-Based Unit #2 Class-Based Unit #3

(300 DSTs) (400 DSTs) (200 DSTs)
Controller Controller Controller Controller Controller Controller

Modules 1 Modules 1 Modules 1 Modules 1 Modules 1 Modules 1
through N through N through N through N through N through N
having a having a having a having a having a having a
total of 250 total of 50 total of 300 total of 100 total of 100 total of 100
AO, AI, DO, AO, AI, DO, AO, AI, DO, AO, AI, DO, AO, AI, DO, AO, AI, DO,
and DI and DI and DI and DI and DI and DI
DSTs DSTs DSTs DSTs DSTs DSTs
Figure 3-3 Example of Advanced Unit Management Licensing

Controllers
SCADA Tags
SCADA tags in a DeltaV system are raw" data displayed to an operator. They are
not licensed and do not count as DSTs. The SCADA tag limit is the physical
capacity of DeltaV products. See Appendix A for capacities. SCADA tags are
brought through a DeltaV controller and Application Station for use in a DeltaV
system. They are not used within any control or alarm functionality, but they may
be displayed, trended, and historized on a workstation.
3-6 v10.3:March 2009

I/O Subsystem
Figure 4-Table 4
Chapter 4 I/O Subsystem
DeltaV I/O subsystems can include classic I/O, HART, serial interface, I/O bus
systems (ASi-Interface, DeviceNet, FOUNDATION fieldbus, and Profibus), Remote
I/O, and intrinsically safe I/O.
Available Simplex and Redundant I/O Cards

I/O subsystem products include a complete range of simplex I/O cards for all
DeltaV versions, and a wide range of redundant I/O cards for DeltaV versions 6.x
and higher. Available cards are listed in Table 4-1. Each card includes a terminal
block for field-wiring. For capacity information, see Appendix A.
Table 4-1. Available DeltaV I/O Cards

Card Type Pre-Series 2 Series 2 for DeltaV
Simplex-only Versions 6.x and Higher
for All DeltaV
Versions Simplex Redundant
AI, 4-channel, Isolated, mV, V, RTD, Ohms, TC X X
AI, 8-channel, 4−20 mA with HART, 2-wire or 4-wire X X X
connection in groups of 4 signals
AI, 8-channel, 1−5 VDC X
AI, 8-channel, mV X
AI, 8-channel, TC X
AI, 8-channel, RTD X
AI, 16-channel, 4−20 mA with HART X X
AO, 8-channel, 4−20 mA with HART X X X
DI, 8-channel, 24 VDC, Isolated X
DI, 8-channel, 24 VDC, Dry Contact X X X
DI, 8-channel, 120 VAC, Isolated X
DI, 8-channel, 120 VAC, Dry Contact X
DI, 8-channel, 230 VAC, Isolated X
DI, 8-channel, 230 VAC, Dry Contact X
DI, 16-channel, Sequence of Events (SOE) X
DI, 32-channel, 24 VDC, Dry Contact X X
DO, 8-channel, 24 VDC, Isolated X

I/O Subsystem
Table 4-1. Available DeltaV I/O Cards (Continued)

Card Type Pre-Series 2 Series 2 for DeltaV
Simplex-only Versions 6.x and Higher
for All DeltaV
Versions Simplex Redundant
DO, 8-channel, 24 VDC, High-side (uses bussed field X X X
power)
DO, 8-channel, 115/230 VAC, Isolated X
DO, 8-channel, 115/230 VAC, High-side X
DO, 32-channel, 24 VDC, High Side X X
ASi-Interface X
DeviceNet X X
Fieldbus H1 X X X
Multifunction/Pulse X
Profibus DP X X
Serial Interface with 2 Ports X X X
Counting DSTs in a Redundant I/O Subsystem

For redundant I/O, MD, MD Plus, or MX controllers and Series 2 I/O cards are
required. Redundant pairs of cards install next to each other on a horizontal or
vertical I/O carrier. A redundant card pair acts as a single card for DST count
against the MD, MD Plus, and MX controller DST limit. Thus, a redundant
8-channel card pair providing 16 channels (eight pairs of redundant channels) is
counted as eight DSTs.
Each redundant card pair counts as 2 interfaces per controller against the I/O
interface limit. Thus, if there are 64 interfaces in a fully redundant I/O system,
each controller is limited to 32 interfaces.
Accurate controller count increases in complexity when planning a redundant I/O

system. If, for example, a simplex system has 1000 DSTs, two or MD Plus
controllers are required. However, in a 1000 DST redundant system, four MD or
MD Plus controllers are required. For MX controllers, a simplex system of 1000
DSTs requires one controller and a redundant system of 1000 DSTs requires two
controllers.
4-2 v10.3:March 2009

I/O Subsystem
Remote I/O Cards

DeltaV remote I/O subsystems are installed in Zone 1 and remote Zone 2 areas to
incorporate I/O signals in these areas into a DeltaV system. Remote I/O cards are
connected to DeltaV controllers through the DeltaV control network. Remote I/O
cards are added to the I/O subsystem under Remote I/O Nodes and the cards are
assigned to a DeltaV controller. It is possible to assign all cards under a Remote
I/O Node to a single controller or assign individual cards under one Remote I/O
Node to multiple controllers.
Zone 1 Remote I/O

A Remote I/O Node installed in Zone 1 supports the following types of I/O cards:
H Zone 1 Analog Input and Output
H Zone 1 Discrete Input and Output

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
Your DeltaV Zone 1 Hardware manual.
A Zone 1 Carrier holds the I/O cards, power supply, and CPU. Zone 1 carriers are
housed in an increased-safety enclosure.
A Zone 1 Power Supply provides an isolation barrier between incoming power

and power supplied to the other units and field circuits in the system. The source
voltage is 24 VDC. The Power Supply, which plugs into the left-most position on
the carrier, is housed in a flameproof enclosure.
A Zone 1 CPU performs control, communications, and power conversion for the
intrinsically safe system. Most connections to the CPU are through the carrier.
Two fiber-optic Ethernet ports on the CPU provide communications interface to
the DeltaV system. The CPU, which plugs into the carrier to the right of the
power supply, is housed in a flameproof enclosure.

I/O Subsystem
Use the following guidelines when developing a bill of materials for a Zone 1
Remote I/O system:
H Each remote I/O node is defined as a CPU, power supply, and up to 4

Zone 1 I/O cards on a Zone 1 carrier.
H Remote I/O nodes and all associated MD, MD Plus, or MX controllers should
be connected to control network switches, not hubs.
H One MD, MD Plus, or MX controller can support up to 16 remote I/O nodes;

therefore, one controller can talk to 64 Zone 1 remote I/O cards plus its
normal 64 local I/O cards, as long as the controller DST limit is not exceeded.
H An I/O card on a remote I/O node can be associated with one, and only one,
MD, MD Plus, or MX controller.
H Any I/O card/controller association is possible as long as:

j An I/O card talks to only one MD, MD Plus, or MX controller.
j Each MD, MD Plus, or MX controller talks to no more than 16 remote I/O

nodes.
j Each remote I/O node talks to no more than four MD, MD Plus, or MX
controllers.
H One remote I/O node can support up to four MD, MD Plus, or MX

controllers. For example, from one remote I/O node, I/O card #1 can talk to
controller #1, I/O card #2 can talk to controller #2, I/O card #3 can talk to
controller #3, and I/O card #4 can talk to controller #4.
H Each CPU supports redundant ethernet; however, there is no such thing as

redundant CPUs.
H There can be up to 60 remote I/O nodes on the control network. They do not
count against the maximum 120 nodes of controllers and workstations.
4-4 v10.3:March 2009

I/O Subsystem
Zone 2 Remote I/O

A Remote I/O Node installed in Zone 2 supports the following types of I/O cards:
H Analog Input Cards

AI, 8-channel, 1−5 VDC
AI, 8-channel, 4−20 mA
AI, 8-channel, 4−20 mA HART and Series 2
AI, 16-channel, 4−20 mA HART
Millivolt, 8-channel
RTD, 8-channel
Thermocouple, 8-channel
H Analog Output Cards

AO, 8-channel, 4−20 mA
AO, 8-channel, 4−20 mA HART (Series 1 and 2)
H Discrete Input Cards

DI, 32-channel, High Density
DI, 8-channel, 120 VAC, Dry Contact
DI, 8-channel, 120 VAC, Isolated
DI, 8-channel, 230 VAC, Dry Contact
DI, 8-channel, 230 VAC, Isolated
DI, 8-channel, 24 VDC, Dry Contact (Series 1 and 2)
DI, 8-channel, 24 VDC, Isolated

I/O Subsystem
H Discrete Output Cards
DO, 32-channel, High Density
DO, 8-channel, 120/230 VAC, High Side
DO, 8-channel, 120/230 VAC Isolated
DO, 8-channel, 24 VDC High Side (Series 1 and 2)
DO, 8-channel, 24 VDC, Isolated
For card specifications, refer to the I/O Cards topic in the Installing Your DeltaV
Automation System manual.
A standard 8-wide horizontal I/O carrier holds the I/O cards. A 24 VDC bulk
power supply provides power to the system power supply and field circuits in the
system. A scanner provides communications interface to the DeltaV system. The
power supply and the scanner plug into a power/controller carrier. This carrier
plugs into the left side of the horizontal I/O carrier .
Use the following guidelines when developing a bill of materials for a Zone 2
Remote I/O system:
H Each remote I/O node is defined as a scanner and a power supply on a

2-wide carrier connected to one 8-wide carrier with up to 8 I/O cards.
H All existing intrinsically safe I/O, bus I/O, serial I/O, Multifunction I/O, and
discrete-in with SOE cannot be used for remote I/O.
H Except as noted above, all other existing 4-, 8-, 16- and 32-channel simplex
I/O cards can be used for remote I/O.
H Redundant I/O cards cannot be used for remote I/O.
H Remote I/O nodes and all associated MD, MD Plus. or MX controllers should
be connected to control network switches, not hubs.
H One MD, MD Plus, or MX controller can support up to 16 remote I/O nodes;

therefore, one controller can talk to 128 remote I/O cards plus its normal 64
local I/O cards, as long as the controller DST limit is not exceeded.
4-6 v10.3:March 2009

I/O Subsystem
H One I/O card on a remote I/O node can be associated with one, and only
one, MD, MD Plus, or MX controller
H Any I/O card/controller association is possible as long as:

j One I/O card talks to only one MD, MD Plus, or MX controller
j Each MD, MD Plus, or MX controller talks to no more than 16 remote I/O

nodes.
j Each remote I/O node talks to no more than four MD, MD Plus, or MX
controllers.
H One remote I/O node can support up to four MD, MD Plus, or MX

controllers. For example, from one remote I/O node, I/O card #1 can talk to
controller #1, I/O card #2 can talk to controller #2, I/O card #3 can talk to
controller #3, and I/O cards 4 thru 8 can talk to controller #4.
H Each scanner supports redundant ethernets; however, there is no such thing

as redundant scanners.
H In a DeltaV system, there can be up to 60 remote I/O nodes on the control

network. They do not count against the maximum 120 nodes of controllers
and workstations.
Fiber Optic Switches for Remote I/O

Two DeltaV Fiber Switches are available for fiber optic communication to Remote
I/O areas. The Single Port Fiber Switch is an Ethernet switch with one 100BaseFx
port and four 10/100BaseTx ports. The Four Port Fiber Switch is an Ethernet
switch with four 100BaseFx ports and one 10/100BaseTx port.
The switches can be mounted on a DIN rail. They provide comprehensive LED
diagnostics. Primarily, the switches are used for the fiber port connection to Zone
1 components over the certified energy-limited fiber port. The switches can be
installed in Zone 2 and they can be used for DeltaV control network applications.

I/O Subsystem
Determining the Quantity of Classic I/O and HART

Interfaces
A DeltaV system can use standard 4−20 mA and 1−5 VDC analog input and output
signals; millivolt, RTD, Ohms, and thermocouple input signals; and a wide-range
of discrete input and output signals in both classic and HART I/O interfaces. Refer
to the Classic I/O and HART I/O product data sheets for determining the quantity
of interfaces.
Determining the Quantity of Serial Interfaces

Each serial interface card includes two serial communications ports that support
RS232, RS422/485 half duplex, or RS422/485 full duplex signals. Each port can
support 16 datasets all input, all output, or a combination of input and output.
The ports support multi-dropping of devices if RS485 is used. A dataset can be a
set of contiguous registers/coil values from a programmable logic controller
(PLC). The 16 datasets may be spread over 1 to 16 devices, depending on the
amount and organization of the data. Each dataset can hold up to 100 data values.
In most cases, the controller DST capacity dictates the size limit. If you have 100
data values in a dataset configured to one controller, the dataset counts as one
DST. If you have the same 100 values in a dataset configured to six controllers,
the dataset counts as six DSTs. In both cases, you can alarm and control any of
the 100 values, but the DST count remains as configured. The maximum number
of DSTs supported per serial interface card is 500.
Data values greater than 100 are spread over several datasets. For example,
reading 140 values from a PLC and writing back 110 values consumes four
datasets. In this case, four datasets on one port are required to support the PLC.
Twelve datasets remain for use. However, if dataset values are used in control
strategies, the values count as DSTs (as opposed to SCADA tags), and the normal
controller DST limit determines the number of datasets you can use on the port.
Determining the Quantity of PROVOX I/O Interfaces

An MD, MD Plus, or MX controller is used for DeltaV Interface to PROVOX I/O.
The quantity of PROVOX I/O interfaces is governed by the DST capability of the
associated controller. One PROVOX I/O channel is equal to one DST.
If the PROVOX I/O system is redundant (with two I/O busses), a redundant
interface is required. That is, the interface requires two DeltaV system power
4-8 v10.3:March 2009

I/O Subsystem
supplies, two controllers, and two I/O interface cards. Redundant PROVOX I/O
interfaces require twice as many controllers as an equivalent simplex system.
Certain PROVOX I/O cards using serial interface in a PROVOX system must be
replaced with a DeltaV Serial Interface Card for use in a DeltaV system. Refer to
the DeltaV Interface for PROVOX I/O product data sheet for additional details.
Determining the Quantity of RS3 I/O Interfaces

An MD, MD Plus, or MX controller is used for DeltaV Interface to RS3 I/O. The
quantity of RS3 I/O interfaces is governed by the DST capability of the associated
controller. One RS3 I/O channel is equal to one DST. Refer to the DeltaV Interface
for RS3 I/O product data sheet for a list of RS3 I/O types supported.
If the RS3 I/O system is redundant, a redundant interface is required. That is, the
interface requires two DeltaV system power supplies, two controllers, and two
I/O interface cards. Redundant RS3 I/O interfaces require twice as many
controllers as an equivalent simplex system.
Determining the Quantity of Multifunction/Pulse Input

Interfaces
The Multifunction/Pulse Input card is both an analog input card and a pulse train
input card. It installs on 8-wide horizontal carriers and vertical carriers. It does not
provide field power, thus field devices requiring external power must have
separate power supplies. There are no special requirements for installing or using
the Multifunction/Pulse Input card, other than the need to provide external
power for field devices. See the product data sheet for specifications.
Determining the Quantity of SOE Interfaces

On a Sequence of Events (SOE) card, any of the inputs can be used for sequence
of events inputs or for standard discrete inputs. An SOE card installs on both
8-wide horizontal carriers and vertical carriers. Because of the fast reaction to
events, an SOE card requires an MD, MD Plus, or MX controller. If several
controllers are receiving signals from an SOE card, a Network Time Protocol
server is required to obtain an accurate time stamp of the events. This server
replaces the synchronization signal from a DeltaV workstation. See the SOE
interface product data sheet for specifications.

I/O Subsystem
Determining the Quantity of AS-i Bus Segments

The Actuator/Sensor interface (AS-i) is an I/O network or bus system that
connects binary on-off field devices to controllers over a single pair of wires, thus
replacing many multiple pairs. The AS-i system is a master/slave system in which
a master device controls the transmission of information to and from slaves.
Slaves connect to field devices.
The master is an AS-i card located on a standard DeltaV I/O carrier. The card
operates and appears as another I/O card in the DeltaV I/O Subsystem. Figure 4-1
illustrates a typical AS-i system. Many I/O network configurations can be used, as
shown by examples in Figure 4-2.
Each grouping of AS-i products connected to a port on a DeltaV AS-i card is a

network. If there are no repeaters, the network consists of one segment. When
repeaters are used, up to three segments can make up a network. See Figure 4-3.
Workstation
2−Wide Carrier with
Controller and Power Supply Controller AS-i Card
Switch
AS-i Power AS-i Power

Supply 1 Supply 1
Slaves To Other Field

Devices
AS-i Segment
Power Supply for
Field Devices 1
Note:
1 Each AS-i Segment requires a power supply to power the slaves connected to the segment. In addition,
field devices producing output signals require a separate power supply. See the guidelines below.
Figure 4-1 AS-i I/O Network in a DeltaV System
4-10 v10.3:March 2009

I/O Subsystem
AS-i Card, AS-i Card, AS-i Card, AS-i Card,

Repeater, Repeater, Repeater, Repeater,
or Extender or Extender or Extender or Extender
Star
Line Branch
Indicates
a Slave
Tree
Figure 4-2 Typical AS-i Segment Configurations
DeltaV
AS-i
Card AS-i Power AS-i Power AS-i Power
Supply Supply Supply
AS-i AS-i
Repeater Repeater
AS-i AS-i AS-i AS-i AS-i AS-i

Slave Slave Slave Slave Slave Slave
Figure 4-3 Example Network Consisting of Multiple Repeaters and Segments

I/O Subsystem
Use the following guidelines to determine the type and quality of AS-i hardware
needed for your DeltaV system. If you have special needs, such as extended AS-i
cable distances, contact the factory.
H Each AS-i card supports up to two AS-i networks.

H Each AS-i network can have up to 31 slaves.
H Each slave is capable of reading or writing to a maximum of four
sensors/actuators.
H Select the slave address for each segment. You can choose any address
between 1 and 31 based on the best logical approach for your application.
H Each signal brought into a controller via AS-i counts as a DST, and is handled
in exactly the same manner as directly connected I/O in the control strategies.
The number of DSTs per connected device can vary from 1 to 8 (4 in and 4
out), with a typical device using 3.
H The sum of the length of all cables used in any one segment must not exceed
100 meters (328 ft). Fabricate the AS-i segment cables using the standard AS-i
flat-type, two-pair cable.
If longer distances are required, repeaters or an extender can be used. There

can be two repeaters (three segments) in a network. An extender can be used
to increase the distance by 100 meters between a segment and an AS-i card.
See installation instructions shipped with extenders. An extender does not
use slave devices or power supplies on the AS-i card side of the extension.
H An AS-i power supply is required for each segment to provide power for the
slaves and the loads connected to the segment.
Repeaters divide network segments. A power supply is required on each side

of a repeater. The current capacity needed from the power supply depends
on the loads of all the slaves connected to the segment. To calculate the
required current, add the current draw from each I/O slave plus the current of
any active sensors connected to that I/O slave. I/O devices with output
signals require an additional power supply. Do not use the AS-i power supply
for output signals because changing loads can cause communication errors.
For complete AS-i Bus specifications, refer to European Standard EN50295E. For
more information on the AS-Interface, refer to the AS-Interface web site at
http://www.as-interface.com.
4-12 v10.3:March 2009

I/O Subsystem
Determining the Quantity of DeviceNet Segments

DeviceNet provides single-cable connection of field devices, such as limit
switches, photoelectric cells, valve manifolds, motor starters, drives, and operator
displays, to a DeltaV controller. Controller interface is through the DeltaV I/O
system.
It is very important that you understand DeviceNet specifications before planning

a DeviceNet network. The specifications, along with general user guidelines, are
available through the DeviceNet internet site: www.odva.org. Figure 4-4 shows a
typical DeviceNet segment.

Controller and Power Supply Controller
DeviceNet
Card
Switch
DeviceNet Segment
Up to 61 DeviceNet Slaves
Terminator Slave Slave Terminator
Power
Supply
Figure 4-4 DeviceNet Segment In a DeltaV System

I/O Subsystem
Use the following guidelines to determining the type and quantity of DeviceNet
hardware needed for your DeltaV system. If you have special needs such as
extended DeviceNet cable distances, contact the factory.
H Each DeviceNet card supports one DeviceNet segment.
H Each DeviceNet segment can have up to 61 slave devices plus the DeltaV
DeviceNet card. In a DeltaV system, device numbers 62 and 63 are reserved
for diagnostic tools and new devices, respectively.
H A DeviceNet power supply is required for each segment to provide power for
the slaves and the loads connected to the segment.
The current capacity needed from the power supply depends on the loads of
all the slaves connected to the segment. To calculate the required current, add
the current draw from each I/O slave plus the current of any active sensors
connected to that I/O slave.
I/O devices with output signals require an additional power supply. Do not
use the DeviceNet power supply for output signals because changing output
loads can cause communication errors.
H DeviceNet uses twisted shielded wire as the transmission medium. Line

parameters are defined in the DeviceNet specifications. Standard cables are
available from Belden.
H Determine the best path to run DeviceNet cable. The maximum length of the
cable depends on the selected communication speed. For more information
about maximum length, refer to the cable description in the DeviceNet
specifications.
H Each DeviceNet segment must have appropriate terminators at both ends.
H Select the slave address for the segment. You can choose any address
between 1 and 61 based on the best logical approach for your application.
4-14 v10.3:March 2009

I/O Subsystem
Determining the Quantity of FOUNDATION fieldbus

Segments
FOUNDATION fieldbus H1 Cards install on standard DeltaV 8-wide horizontal
and vertical I/O carriers. Each card has connections for two fieldbus segments.
Each segment supports a maximum of 16 fieldbus devices. Figure 4-5 shows a
possible fieldbus segment.
Use the following guidelines to determine the types and quantities of hardware
needed for your fieldbus segment:
H Up to two fieldbus segments can be connected to a DeltaV H1 Fieldbus card.

(Only one segment is shown in Figure 4-5).
For example, if you have 13 fieldbus transmitters and four fieldbus control
valves, you could put two valves and six transmitters on one segment, and
two valves and seven transmitters on a second segment. You only need one
Fieldbus H1 card.
H A fieldbus segment can have up to 16 fieldbus transmitters and fieldbus

control valves connected to it; however, the factory recommends that you
limit the number of valves per segment to four.
H If a backup linkmaster device is installed on an H1 segment, it can be

commissioned only at device address 20, so care must be taken not to use
this location for other devices. The Rosemount 3051 Rev 4 Pressure
Transmitter and the Rosemount 3244 Rev 3 Temperature Transmitter are
examples of backup linkmaster devices. If control in the field is not
implemented, a backup linkmaster is not required.
H One fieldbus power supply is required for each segment to provide power for
devices connected to the segment. The power supply receives 24 VDC,
typically from a 24 VDC bulk supply, and isolates it. The same bulk power
supply may be used as the one supplying power for classic I/O field devices.

I/O Subsystem
H The sum of the lengths of all cables used in the segment must not exceed 1.9
kilometers.
H The maximum length of the cable drops between a fieldbus device and a
junction block is 120 meters.
H Each end of the trunk cable must be terminated with a fieldbus terminator.
The terminator internal to the fieldbus power supply terminates the left end
of the trunk cable.
H Fabricate the main run and spur cables using standard fieldbus Type A cable
(Belden 3076F) and associated connectors.
H All unused connectors on the junction block(s) must be protected with

closure caps.
H If you are using gland adapters, you may purchase them installed or separate.
The adapter screws into the device’s ½-inch NPT conduit fitting and adapts
the devices’ signal screw terminals to a male connector that matches with a
female connector on the fieldbus cable.
Detailed information on using FOUNDATION Fieldbus with a DeltaV system is

available in the manual, Fieldbus Installations in a DeltaV Digital Automation
System.
4-16 v10.3:March 2009

I/O Subsystem
Control Room Equipment
H1 Cards
Fieldbus Power Supply
with Terminator In
Fieldbus
Junction Block
Spurs Cable
Main Run
Junction Block
Fieldbus Spurs
Devices
Terminator
Figure 4-5 FOUNDATION fieldbus Segment in a DeltaV System

I/O Subsystem
Determining the Quantity of Profibus Segments

Use the following guidelines to determine the type and quantity of Profibus
hardware needed for your DeltaV system. If you have special needs such as
extended Profibus cable distances, contact the factory. Figure 4-6 shows a typical
Profibus segment.
H Each Profibus DP card supports one Profibus segment.
H Each Profibus segment can have up to 64 slave devices plus the DeltaV
master.
H Profibus is not a self-powered bus. Each slave must be supplied with the
appropriate power for the connected device.
H Profibus uses twisted shielded wire as the transmission medium. Line

parameters are defined in EN50170. Standard cables are available from
Belden.
H Determine the best path to run Profibus cable. The maximum length of a
Profibus segment depends on the selected communication speed. For more
information about maximum length, refer to the cable description in the
Profibus specification EN50170.
H Each Profibus segment must have appropriate terminators at both ends. The
DeltaV Profibus terminal block contains a selectable Profibus terminator. It is
common for a Profibus connector to contain one selectable Profibus
terminator. Consult the connector documentation to determine if a connector
contains a Profibus terminator.
For a description of the Profibus interface, refer to the Profibus specification

EN50170. For more information on the Profibus interface, refer to the Profibus
web site at www.profibus.com.
4-18 v10.3:March 2009

I/O Subsystem

Controller and Power Supply
Controller Profibus
Card
Switch
Profibus Segment
Profibus Up to 64 Profibus Slaves Profibus

Terminator Slave Slave Terminator
Power Power
1 Supply Supply 1
Note:
1 Each Profibus slave requires an individual power supply. See the guidelines in text.
Figure 4-6 Profibus Segment in a DeltaV System

I/O Subsystem
Intrinsically Safe I/O Subsystem

The DeltaV intrinsically safe I/O subsystem is isolated from the controller and the
regular system power supply by a Localbus isolator. Figure 4-7 shows a typical
installation using intrinsically safe I/O. One intrinsically safe power supply is
required for each carrier. DeltaV I/O cards available for an intrinsically safe I/O
subsystem include:
H AI, 8-channel, 4−20mA with HART

H AO, 8-channel 4−20mA
H AO, 8-channel, 4−20 mA with HART
H DI, 16-channel
H DO, 4-channel
System Power Non−IS IS

Supply IS
Non−IS I/O Cards Localbus IS I/O Cards Power RH Carrier
Controller (Gray Terminal Blocks) Isolator (Blue Terminal Blocks) Supply Extender
LH Carrier IS I/O Cards IS IS I/O Cards IS

Extender Power Power
Supply Supply
Figure 4-7 Intrinsically Safe I/O Overview
4-20 v10.3:March 2009

I/O Subsystem
For further information about intrinsically safe I/O subsystems, see the following
manuals (located on the DeltaV product disk 2):
H DeltaVt Scalable Process System, Class I Division 2 Installation Instructions

(Part Number − 12P1293)
H DeltaVt Scalable Process System, Class I Div. 2 with Class I, II, III Div. 1
Field Circuits Installation Instructions (Part Number − 12P1892)
H DeltaVt Scalable Process System with Zone 0 Field Circuits Installation

Instructions (Part Number − 12P1990)
H DeltaVt Scalable Process System, Zone 2 Installation Instructions (Part

Number − 12P2046)
I/O Subsystem Carriers

Both horizontal and vertical I/O carriers are available for mounting I/O cards.
Vertical carriers are often used to fit DeltaV I/O into vertical system enclosures.
Horizontal carriers usually provide denser I/O mounting than vertical carriers. Up
to eight I/O cards mount on an 8-wide horizontal carrier or on a vertical carrier.
The minimum required number of carriers is calculated by dividing the quantity

of I/O interfaces by eight and rounding up. Redundant I/O interfaces double the
requirement. I/O interfaces can be spread over more than just the calculated
minimum quantity of I/O carriers.
Note ... You can use both horizontal and vertical carriers in a DeltaV system, but
horizontal and vertical carriers cannot be connected. There is no means of
doing so.
See the Subsystem I/O Carriers product data sheet for further information.
Fieldbus H1 Carrier
A Fieldbus H1 Carrier holds one 8-Channel DI card and one 8-Channel DO card
to connect discrete I/O field devices to fieldbus segments. You may install one or
both cards. The DST count per card is always eight, whether you use one or all
eight channels. Twenty-four VDC power for the carrier and cards must be
supplied separately from 24 VDC power for field devices. The carrier mounts on
T-type DIN rail, wall, or panel. See the H1 Smart Carrier product data sheet for
further information.

I/O Subsystem
Zone 1 Carrier
A Zone 1 Carrier provides connections and hardware for the Zone 1 Power
Supply, Zone 1 CPU, and up to four Zone 1 I/O cards. The carrier mounts on a
panel in a customer-supplied, increased-safety enclosure. The enclosure must
have appropriate certifications for the location in which it is installed. The carrier
includes input power screw terminals and field wiring terminals for the I/O cards.
DeltaV Interface for PROVOX I/O Carrier

A DeltaV Interface for PROVOX I/O Carrier provides a means of connecting
PROVOX I/O to DeltaV MD, MD Plus, or MX Controllers. The PROVOX I/O Bus
connects to a BNC connector on the carrier. Each carrier holds two DeltaV system
power supplies, two controllers, and two I/O interface modules. AC or DC system
power supplies may be used. The carrier mounts on a standard 19-inch EIA rail.
DeltaV Interface for RS3 I/O Carrier

A DeltaV Interface for RS3 I/O Carrier provides a means of connecting RS3 I/O to
DeltaV MD, MD Plus, or MX Controllers. RS3 I/O cabling connects to RS3-type
I/O connectors on the carrier. Each carrier holds one each of a DeltaV system
power supply, a controller, and an I/O interface module for a simplex system, and
two each of DeltaV system power supplies, controllers, and I/O interface modules
for a redundant system. AC or DC system power supplies may be used. The
carrier mounts on a standard 19-inch EIA rail.
DeltaV FlexConnect
DeltaV FlexConnect lets users of competitive control systems connect their I/O
systems to a DeltaV system. FlexConnect is a method of connecting
multiconductor cables from competitive I/O subsystems to DeltaV termination
panels, and auto-marshalling the signals to DeltaV I/O. For further information
about DeltaV FlexConnect products, see corresponding product data sheets.
4-22 v10.3:March 2009

Smart Wireless Gateway
Figure 5-Table 5
Chapter 5 Smart Wireless Gateway
The Smart Wireless Gateway is the field access point through which all
WirelessHART field devices communicate their sensor values to a DeltaV system.
For DeltaV version 10.3 and later, the gateway is a node on the DeltaV control
network, permitting it to be auto-sensed and auto-configured in the DeltaV
Explorer.
The gateway manages the device network, securing the communication and
enabling the host system to configure connected field devices. It can be extended
by a smart wireless plant network and directly connected to a wireless DeltaV
control network segment
Smart Wireless Field Network

The smart wireless field network consists of WirelessHART devices
communicating in a self-organizing mesh network to a Smart Wireless Gateway.
Connection between the gateway and the main process can be made through
wire or, if more convenient, through a wireless plant network. No RF survey is
required for the WirelessHART devices, but the guidelines for WirelessHART
device installation must be followed.
For version 10.3 and later, no further communication devices are required. For
versions 9.3 and earlier, the gateway can be setup to communicate through
Modbus Serial I/O, Modbus TCP/IP I/O, or the gateway’s OPC Server. In the case
of OPC, the OPC Mirror can also be used to map device data from the Smart
Wireless Gateway to the DeltaV OPC Server control modules.
The gateway must be configured to enable the DeltaV Commissioner and HART
Port protocols. This configuration is done for you when you order model
VE4041Exxx series.
For installation of a Smart Wireless Field Network to any legacy control system,
the gateway is setup to communicate through Modbus Serial I/O, Modbus TCP/IP
I/O, or the gateway’s OPC Server.

Communication Protocols — Version 10.3 and Later

For DeltaV version 10.3, no outside communication protocols are required. The
Smart Wireless Gateway connects as a node on a DeltaV control network.
Communication Protocols — Version 9.3 and Earlier

Communication to the Smart Wireless Gateway can be made through:
H Modbus Serial Protocol

H Modbus TCP/IP Protocol
H OPC DA
Modbus Serial Protocol

The Smart Wireless Gateway includes an RS485 port which can be connected to a
DeltaV system using a serial card. The card contains two ports which can be
configured as RS485, allowing up to 16 gateways connected in multidrop fashion.
The serial card is configured as the master with gateways as slaves.
The serial card is limited to 16 datasets per port and each dataset can have up to
100 Modbus registers. This limits the number of devices or variables which can be
connected through a single port. For example, if multiple gateways are connected
in multidrop to a port and if each transmitter has multiple registers associated
with it, there is a significant risk of running out of registers when simply
transferring information of only a couple of gateways since each gateway can
have up to 100 transmitters.
Modbus TCP/IP Protocol

To use Modbus TCP/IP Protocol, a Mynah Virtual I/O Module (VIM) card is
necessary. The card is connected to any Modbus TCP/IP device in a DeltaV
system. To setup parameters in the VIM card, VIMNet software is required. This
software can be purchased from Mynah Technologies. See www.mynah.com for
information about Mynah products.
The VIM card allows for the connection of several Modbus TCP/IP devices into a
DeltaV system in multidrop fashion. Since a DeltaV controller treats the VIM card
as DeltaV serial card, the same limitations apply as noted for Modbus Serial
Protocol concerning the amount of registers allowed by a DeltaV controller.
5-2 v10.3:March 2009

OPC DA
For OPC DA, a separate network must be set up to connect a gateway to an OPC
DA server. The server resides on an DeltaV Application or ProfessionalPLUS
workstation. In addition, an OPC DA server (available on the installation CD
included with the gateway) must be installed in the gateway.
Using with AMS Device Manager — Version 10.3 and Later

HART alerts from WirelessHART devices are passed directly to an AMS Device
Manager, eliminating the need for a separate Ethernet network or other
connection.
Using with AMS Device Manager — Version 9.3 and Earlier

When connecting a gateway using Modbus Serial Protocol or Modbus TCP/IP
Protocol, a separate connection is required to connect the gateway to AMS server.
When using Modbus 485 (with serial protocol) to connect to a DeltaV system, any
of the gateway ports can be used. When using TCP/IP protocol, one port is used
for the gateway and the other port is used to communicate to the AMS server.
For OPC DA, the connection is already made to the Application or

ProfessionalPLUS workstation, containing AMS server. If the AMS server is not
located in the same workstation as OPC DA, the connection must be extended to
the machine which has the OPC DA server.
With these connections, Device Manager contains two networks: The DeltaV
network with HART and field devices and the gateway network to display
wireless devices. It is important to remember that the Alert Monitor from Device
Manager will consolidate the alarms of both networks.
Installation Dimensions
Figure 5-1 and Figure 5-2 show dimensions necessary for planning both the
gateway mounting and its antenna mounting.

Figure 5-1 Outline Dimensions for Gateway Mounting
5-4 v10.3:March 2009

Figure 5-2 Outline dimensions for Antenna Mounting

5-6 v10.3:March 2009

Safety instrumented Systems
Figure 6-Table 6
Chapter 6 Safety instrumented Systems
A DeltaV Safety Instrumented System (SIS) consists of:
H Smart Logic Solvers (SLS) with I/O termination blocks
H SISNet Repeaters
H SISNet Repeater Carrier for use with VerticalPLUS I/O Interface Carriers
H SISNet Distance Extenders
H Local Peer bus extender cables
H Right one-wide carriers for use with Horizontal I/O Interface Carriers
H Terminators
H Optional Devices
Figure 6-1 illustrates an example DeltaV Safety Instrumented System integrated
with a DeltaV Digital Automation System. As shown in the figure, the safety
instrumented system can include SIS equipment in remote locations.
The figure also shows SIS equipment mounted on Horizontal I/O Interface
Carriers. See Chapter 10 for information on horizontal carriers. SIS equipment can
be mounted on VerticalPLUS I/O Interface Carriers. See Chapter 10, Figure 6-2,
and subsection Using Vertical Carriers in this chapter for information on using SIS
on VerticalPLUS carriers.

Smart Logic Solvers

Smart Logic Solvers (SLS) contain the logic solving capability of the SIS system
and provide an I/O interface for up to any 16-channel combination of Analog
Input (HART), Discrete Input, and Discrete Output. SLSs and termination blocks
mount on 8-wide horizontal I/O carriers or VerticalPLUS I/O carriers. SLSs mount
in odd numbered slots (1,3,5,7). Simplex SLSs take two slots and redundant SLSs
take four slots.
Analog Input (HART) and Discrete Input are standard DeltaV I/O specification.
Discrete Output can be voltage (0 and 24 VDC) or current (4 and 20 mA) for full
valve stroke. The current output may also be configured for 0 mA. The current
output includes built-in HART capability for partial stroke testing. Hart is not used
otherwise.
SLSs communicate with each other over a two-channel, peer-to-peer bus. The bus
uses the railbus on the I/O carrier backplane and can be extended to SLSs on
other carriers by peer-to-peer extender cables.
SISNet Repeaters
When one controller (or set of redundant controllers) is used for the local and
remote SLSs, SISNet Repeaters and fiber-optic cable provide ring-type,
global-broadcast communication between local SLSs and SLSs scattered across two
or more I/O subsystems. There is one SISNet Repeater pair for each I/O
subsystem carrier. Up to 32 simplex SLSs or 16 redundant SLSs can be connected
on the fiber-optic ring.
SISNet Repeaters mount in pairs (for redundancy) on 2-wide repeater carriers [9.5
cm (3.8 in.) wide]. Although this carrier is the same width as a power/controller
carrier, it is not interchangeable with the power/controller carrier. For further
information, including allowable fiber-optic cable length, see the manual,
Installing Your DeltaV Safety Instrumented System Hardware.
6-2 v10.3:March 2009

Primary Secondary Workstation

control network control network
Primary hub Secondary hub

Primary control Secondary control
network cables network cables
Controller Local Plant Area
System
Power Power
Error
Power
Error
Active
Standby
Pri CN
Power
Fault
Ch.1
Power
Fault
Ch.1
Power
Fault
Ch.1
Power
Fault
Ch.1
Power
Fault
Ch.1
Power
Fault
Ch.1
Supply System
Sec CN
Controller
MD
Ch. 2
Ch. 3
Ch. 4
Ch. 5
Ch. 6
Ch. 7
Ch. 2
Ch. 3
Ch. 4
Ch. 5
Ch. 6
Ch. 7
Ch. 2
Ch. 3
Ch. 4
Ch. 5
Ch. 6
Ch. 7
Ch. 2
Ch. 3
Ch. 4
Ch. 5
Ch. 6
Ch. 7
Ch. 2
Ch. 3
Ch. 4
Ch. 5
Ch. 6
Ch. 7
Ch. 2
Ch. 3
Ch. 4
Ch. 5
Ch. 6
Ch. 7
Passthrough
Power Supply Ch. 8 Ch. 8 Ch. 8 Ch. 8 Ch. 8 Ch. 8
(DC/DC) System System System System System System LOCK
Repeater Repeater Repeater Repeater Repeater Repeater
B
Dual carrier
FISHER−ROSEMOUNT
extender cables
D
Peer-to-Peer Bus
extender cables
Smart Logic Solvers SISNet Repeaters

Righthand
C D
SS 1508 SS 1508
One-Wide
A Power
Fault
Local Peer PX
Local Peer RX
Power
Fault
Local Peer PX
Local Peer RX
Carrier
Remote Peer PX Remote Peer PX
Remote Peer RX Remote Peer RX
LOCK
System
Repeater
System
Repeater LOCK
Terminator
B B
++
Lefthand D
Terminator
One-Wide
Carrier Multimode Fiber Optic Cables
SISNet
Distance
Extenders
Controller Remote Plant Area (2)
SISNet Repeaters Smart Logic Solvers
Righthand
System One−Wide
Power Power
Error
Power
Error
Active
Standby
Power
Fault
Local Peer PX
Power
Fault
Local Peer PX
SS 1508 SS 1508
Carrier Single mode Fiber
Pri CN
Supply Sec CN Local Peer RX

Remote Peer PX
Remote Peer RX
Local Peer RX
Remote Peer PX
Remote Peer RX
Optic Cables
System
Passthrough
Power Supply
(DC/DC)
Controller
MD
System
Repeater System
Repeater
LOCK
Terminator
FISHER−ROSEMOUNT
B
SISNet
D
Terminator Distance
Extenders
(2)
Figure 6-1 Safety Instrumented System Integrated into a DeltaV System

Workstation Communication
An MD controller of hardware Rev. X or higher, an MD Plus controller, or an MX
controller provides the communications link to the workstation via a DeltaV
control network. Local SLSs are connected to the local controller and remote SLSs
are connected to remote controllers, as shown in the figure. It is highly
recommended that fiber-optic cable be used in the control network between the
remote controller and the workstation. See Chapter 2 for cable specifications.
SISNet Distance Extenders

SISNet Distance Extenders allow fiber optic extensions between SISNet Repeaters
of up to 20 km (nominal) beyond the limitations of multimode fiber optic cable.
The extenders mount directly on DIN-rail wherever it can be conveniently located
(within environmental specifications) and are powered from field 24 VDC.
Single mode fiber optic cable connects local and remote extenders. Two
extenders are used for each cable; one at each end. Redundant extensions use
four extenders as shown in Figure 6-1.
Using Horizontal I/O Carriers

Left-hand and right-hand one-wide cable carriers provide connectors for the
redundant peer-to-peer bus extender cables. The cables require proper electrical
impedance termination which is accomplished with two terminators at the
right-hand one-wide carrier on the farthest I/O horizontal carrier. Horizontal cable
carriers are each 42 mm (1.6 in) wide.
Dual carrier extender cables connect railbus power and signals between carriers.
The cables connect to the same left-hand and right-hand one-wide cable carriers
as the peer-to-peer bus extender cables. SLSs are powered by a 24VDC power
supply that is separate from the DeltaV controller and I/O power supply.
6-4 v10.3:March 2009

Using Vertical I/O Carriers

SIS equipment can be mounted on VerticalPLUS I/O carriers; not Legacy Vertical
carriers. With VerticalPLUS I/O carriers, you can connect SIS systems, such as local
and remote, by SISNet Repeaters mounted on 4-Wide VerticalPLUS SISNet
Repeater Carriers as shown in Figure 6-2. SISNet repeaters are not needed unless
you need to connect to another SIS system.
In the figure, note the extender cable connections. In SIS systems, carrier extender
cables and SISNet Repeater extender cables are required between the left and
right carriers. You may use only one carrier extender cable, but you must use
both SISNet Repeater extender cables for redundancy. The repeater carrier is
always mounted above the cable extender card (left-hand card) used with a
right-hand vertical carrier. SISNet extender cables are one meter long.
Optional Devices
The following items can be added to a SIS system:
End-of-Line Resister Module for Discrete In

End-of-Line Resister Modules for Discrete In are used for Line Fault Detection.
Line Fault Detection must be turned on during system configuration and must
include one End-of-Line Resister Module in each line pair between an SLS and the
discrete input field device where line fault detection is desired.
RC Compensator for Discrete Out

An RC Compensator is used for large inductive loads on SLS Discrete Outs when
Line Fault Detection is turned on. It is not required otherwise. In addition, even
when Line Fault Detection is turned on, it is only used if the inductive load is
greater than 0.8H simplex or 0.3H redundant. A compensator does not assist in
driving inductive loads; it only compensates for line fault detection distortion
caused by large inductive loads.
Dual Channel Voltage Monitor

The Dual Channel Voltage Monitor can be used to drive a Logic Solver’s discrete
input channel based on the output of the Safety Relay Module. Each monitor can
handle two DI channels.

Extender
22.8 cm Cables
B A D C
(9.0 in.)
ns
Pins
Pi
Pins
A
Pi
ns
B
C D
Socket
BC
Right(Out) Socket
A
D
B A
C C
Socket
Socket
12 SP
ocks
et 31
2
P P S S 3 in
18.1 cm . W O W O 18.1 cm . N N
(7.1 in.) N N 4
R R (7.1 in.) R R
C
D
T T 3
12
3 SP
oc
nk
iset 31
2 12
323 SP
Soci
cn
okes
kt
et 31
12
2
1
4 5
3 6
2 7
1 8
8
51.0 cm 7
(20.1 in.) 6
5
8 1
7 2
6 3 113.2 cm 12
3 SP
oi
cn
ks
et 31
2
5 4 (44.6 in.) .
4
3
12 SP
oi
c
nk
set 31
2 12 Pc
i
n
ks 31
2
3 3 So et
2
1
4 5
3 6
2 7
1 8
177.5 cm 8
(69.9 in.) 7
6
5
8 1
7 2
6 3 12
3 SP
ocks
inet 31
2
5 4 Socket
AC
B
Socket Left(In)
12
3 SP
oi
c
nk
set 31
2 12
3 Pc
Soi
n
ks
et 31
2
5 P P P P 4-wide
4 17.7 cm.
3 6 W W W W Power
2 7 (7.0 in.) R R R R Carrier
1 8
2.3 cm
8 1 (0.9 in.)
7 2
6 3
5 4
12
3 SP
oc
nk
iset 31
2 12
3 Pi
Son
ks
cet 31
2
Socket
AC
BC
Socket
B
Socket Left(In) Right(Out) Socket

Pins Pins
B
Pins
B
Pins
A
C D C D
SISNet
Extender
Cables
Figure 6-2 Dimensions and Extender Cables with SISNet Repeaters on VerticalPLUS I/O Carriers
6-6 v10.3:March 2009

Current Limiter
The Current Limiter limits the current from SLS discrete output channels to levels
below the ignition curves for Class 1, Div 2 and Zone 2 installations. Each limiter
can handle four DO channels.
Relay DTA Module and Relay Diode Module

Often used for fire and gas applications, but also usable elsewhere, the Relay
De-energize-to-Activate (DTA) Module is an inverting unit which energizes a field
device when a Logic Solver output to the DTA module is turned OFF. The power
supplied to the module for the field device is 24 VDC. Two 24 VDC inputs are
included for redundant power. The DTA module is single channel.
The Relay Diode Module is paired with the Relay DTA Module to perform
required functions, such as monitoring field wiring when not actuated. The diode
module contains a switch to change between energize-to-activate (ETA) and
De-energize-to-Activate (DTA).
Safety Relay Module

For safety applications, the Safety Relay Module lets a SIS discrete output signal
switch (open or close) the connection between either one AC source and its AC
field device or two DC sources and their DC field devices. Relay current rating is
2.5 A at 250 VAC. The safety relay module is single channel.
Licensing
To implement a DeltaV SIS system, an activation license is required: Model
number VS1508.

6-8 v10.3:March 2009

Power Supplies
Figure 7-Table 7
Chapter 7 Power Supplies
DeltaV systems use two types of power supplies: system power supplies which
power DeltaV controllers and I/O subsystems, and bulk power supplies which
power field devices.
System Power Supplies

Two system power supplies are available: VE5001 AC to DC System Power Supply
which operates from 120 or 240 VAC and VE5009 DC/DC Dual System Power
Supply which operates from 12 or 24 VDC.
VE5001 AC to DC System Power Supply

The VE5001 AC to DC System Power Supply, illustrated in Figure 7-1, is typically
used in small DeltaV systems where a single-controller with a limited number of
I/O is required. The supply provides 2.1 A Localbus current, enough to power, for
example:
H 8 Discrete I/O cards, or
H 8 Analog I/O cards, or
H 4 Serial I/O cards, or
H 4 Series 2 H1 cards
The VE5001 accepts 120 or 240 VAC and provides instrument power to a
controller and its associated I/O subsystem. The power supply is mounted
directly to the left of the controller on a 2-wide power/controller carrier.
A system may require more than one VE5001. Three factors determine how many
are needed: 1) the use of simplex or redundant controllers, 2) the type and
quantity of I/O cards used with the controller, and 3) redundant power
requirements for the I/O cards. Additional VE5001 power supplies are mounted to
the left of the controller on additional carriers. See the power supply product data
sheet for output power capacity.

Power Supplies
VE5011 Bulk AC to 24 VDC

Power Supply
From Plant Power
(120/240 VAC) 24 VDC
From Plant Power Field Power

(120/240 VAC)
VE5001 AC to DC System
Power Supply
Controller
I/O Subsystem
Figure 7-1 VE5001 AC to DC System Power Supply
Limits exist to the amount of current an I/O carrier can handle. The horizontal I/O
carrier limit is specified at 8 Amps; the limit for either vertical I/O carrier is
specified at 15 Amps. This limit can be quickly reached when many I/O cards are
used and carriers are connected by extender cables. If the limit is reached,
VE5001 power supplies can be mounted nearer to the I/O cards on carriers
connected in a chain. See the manual, Installing Your DeltaV Digital Automation
System, for further details about horizontal and vertical carrier capabilities.
Note ... Keep in mind any future expansions. If for example your system is sized
using a VE5001 system power supply, and you are using two H1 cards in
your present configuration, you have six empty I/O slots on the 8-wide
carrier. If you are planning future expansions by adding more cards to that
carrier, one VE5001 system power supply will not be sufficient. You can
install additional VE5001 system power supplies; however, you may want to
consider using a VE5009 power supply and a VE5011 or VE5012 bulk
power supply to accommodate future expansions.
7-2 v10.3:March 2009

Power Supplies
VE5009 DC/DC Dual System Power Supply

The VE5009 DC/DC Dual System Power Supply, illustrated in Figure 7-2, is
typically used in DeltaV systems where several controllers and their associated
I/O subsystems are installed and 24 VDC plant power is available. The VE5009
accepts either 12 VDC or 24 VDC and provides instrument power to the controller
and its associated I/O subsystem. The power supply is mounted directly to the
left of the controller on a 2-wide power/controller carrier.
When a VE5009 is operated on 12 VDC, it is rated at 13 Amps LocalBus current.

When the supply is operated on 24 VDC, it is rated at 8 Amps LocalBus current.
A system may require more than one VE5009. Three factors determine how many
are needed: 1) the use of simplex or redundant controllers, 2) the type and
quantity of I/O cards used with the controller, and 3) redundant power
requirements for the I/O cards. Additional VE5009 power supplies are mounted to
the left of the controller on additional carriers.

Power Supply
From AC Plant
Power 24 VDC
(120/240 VAC)
From AC Plant
Power 12 VDC
Field Power
(120/240 VAC)

Power Supply
VE5009 DC/DC Dual

System Power Supply
Controller
I/O Subsystem
Figure 7-2 VE5009 DC/DC Dual System Power Supply

Power Supplies
Limits exist to the amount of current an I/O carrier can handle. The horizontal I/O
carrier limit is specified at 8 Amps; the limit for either vertical I/O carrier is
specified at 15 Amps. This limit can be quickly reached when many I/O cards are
used and carriers are connected by extender cables. If the limit is reached,
VE5009 power supplies can be mounted nearer the I/O cards on carriers
connected in a chain. See the manual, Installing Your DeltaV Digital Automation
System, for further details about horizontal and vertical carrier capabilities.
Using Multiple System Power Supplies

There are several ways to add multiple system power supplies for providing
adequate power to many I/O cards in a large DeltaV system. These ways are
described in System Power Guidelines appendix in the manual, Installing Your
DeltaV Automation System.
Bulk Power Supplies

There are three bulk power supplies available for DeltaV systems.
H The VE5011 DIN-rail mounted supply takes 120 or 240 VAC and supplies 24
VDC to field devices through the DeltaV I/O subsystem.
H The VE5012 DIN-rail mounted supply takes 120 or 240 VAC and supplies 12
VDC to VE5009 DC/DC Dual System Power Supplies.
Using VE5011 for Field Power

The VE5011 bulk power supply accepts 120 or 240 VAC and supplies 24 VDC with
a capacity of 12 Amps for field devices connected to the I/O subsystem
(Figure 7-1). Power to field devices is isolated from power to a DeltaV I/O
subsystem.
In general, AI, AO, and Dry-Contact DI cards use small amounts of current. The
VE5011 provides enough power for approximately 40 of these types of cards. If
you are supplying power to DO cards with high-side switches, you must evaluate
the power requirements carefully.
To calculate the amount of current available for field devices, 0.3 Amps current
drawn by each analog I/O card must be subtracted from the total current
available from the VE5011 bulk supply. Fieldbus usage must also be considered
when calculating available current for field devices. Fieldbus segments powered
7-4 v10.3:March 2009

Power Supplies
by a fieldbus power supply typically receive primary power from the VE5011 bulk
supply. A fieldbus segment has a limit of 0.35 Amps.
Calculating Current Available for Classic I/O

To calculate current available to Classic I/O field devices: 1) multiply the number
of analog input and output cards by 0.3 Amps; 2) multiply the number of fieldbus
segments by 0.35 Amps; 3) subtract both products from 12 Amps. The answer is
the amount of current available for Classic I/O field devices connected to the I/O
subsystem. The technique is illustrated in Figure 7-3. Also, to help you calculate
current, see the Power Supply Calculation Worksheets in the manual, Installing
Your DeltaV Digital Automation System.
System Power Supply

Controller
AI AO
2-Wide 8-Wide Card Card 8-Wide 8-Wide
Carrier Carrier Carrier Carrier
Terminal Terminal
Block Block
Calculation Example: Each AI and AO card uses 0.3 Amps at 24 VDC.
Add total current for each 8-wide carrier, plus the current required by all connected field devices
to determine the carrier current requirement.
For example, one AI card plus one AO card in the left 8-wide carrier requires 0.6 Amps for that
carrier. If you assume that 0.5 Amps are required for the field devices, the total power required
for the two cards and the connected field devices is 1.1 Amps.
Figure 7-3 Calculating Current Required from Bulk Power Supplies

Power Supplies
Note ... Discrete devices driven by the VE4002S1T2B1 or VE4002S1T2B2 high-side

discrete output interfaces typically consume the largest amount of 24 VDC
power. Each interface can handle up to 6 Amps to the discrete devices
connected to its I/O terminal block.
If the calculated current available for field devices after carrier current is
subtracted is greater than the capacity of one VE5011, add another VE5011. One
VE5011 power supply (or a redundant pair) typically has enough capacity to
power more than one set of I/O associated with multiple controllers. Reasons for
not using a single power source for multiple sets of I/O may include:
H The I/O sets and associated controller are located so far apart that it is
impractical to run the power wiring from a single power supply to each I/O
set and controller.
H The application cannot afford to lose power to all I/O upon failure of a single
power supply. In this case, use redundant VE5011 supplies as described
below.
Redundancy Considerations for VE5011 Power Supplies

Redundancy for a VE5011 power supply is available only as one-for-one; that is,
one supply is primary and the other is backup. VE5011 supplies include
integrated OR’ing" diodes, so external diodes are not required for redundant
combinations.
Using VE5012 to Power VE5009 Power Supplies

Use a VE5012 bulk power supply to convert 120 or 240 VAC to 12 VDC to power
a VE5009 DC/DC Dual System Power Supply. One VE5012 can supply several
VE5009 supplies up to the limit of the VE5012. However, keep in mind the
consequences of single points of failure if one bulk supply fails.
Redundant Combinations of VE5012 and VE5009 Power

Supplies
You can add a second combination of VE5012 and VE5009 power supplies as
illustrated in Figure 7-4 to provide system power redundancy for systems using
simplex controllers. You need an extra 2-wide power/controller carrier to add the
second VE5009.
7-6 v10.3:March 2009

Power Supplies
If your system uses redundant controllers, you must use a second combination of
VE5012 and VE5009 power supplies as illustrated in Figure 7-5 to maintain the
controller redundancy. For redundancy, each controller requires its own VE5009
supply. A second 2-wide carrier provides mounting for the second controller of
the redundant pair.
From AC Plant VE5012 Bulk AC to 12 VDC

Power
Power Supplies
(120/240 VAC)
From AC Plant
Power Simplex
(120/240 VAC) Controller
Empty Slot
Redundant VE5009
DC/DC Dual System
Power Supplies
Figure 7-4 Redundant Combination of VE5009 and VE5012 for Simplex Controllers
From AC Plant VE5012 Bulk AC to 12 VDC

Power Power Supplies
(120/240 VAC)
From AC Plant
Power
(120/240 VAC) Redundant Controllers
Redundant VE5009
DC/DC Dual System
Power Supplies
Figure 7-5 Redundant Combination of VE5000 and VE5012 for Redundant Controllers

Power Supplies
Redundancy Considerations for VE5012 Power Supplies

Redundancy for a VE5011 power supply is one-for-one; that is, one supply is
primary and the other is backup. VE5011 supplies include integrated OR’ing"
diodes, so external diodes are not required.
Intrinsically Safe System Power Supply

To power intrinsically safe I/O cards, an intrinsically safe system power supply is
used. The supply accepts nominal 24 VDC input voltage and provides 12 VDC
output at up to 5 Amps. Depending on the type and mix of I.S. cards, the supply
can power eight to fifteen cards. You can have up to ten I.S. power supplies plus
an additional power supply for redundancy. The total quantity of I.S. power
supplies for a redundant system is eleven. Use the I.S. power supply worksheet in
the manual, Installing Your DeltaV Digital Automation System, to determine the
quantity of power supplies needed for your system.
Selecting Uninterruptible Power Supplies

The primary AC power source for DeltaV systems must be free of power
interruptions greater than 20 milliseconds. An interruption greater than this
amount can cause loss of control, system configuration, and process data.
Uninterruptible power supplies (UPS) should be ordered with a DeltaV system if
existing plant power does not meet the 20 millisecond requirement.
A VE5006 uninterruptible power supply (UPS) is available from Emerson Process

Management. Use the following guidelines to determine the quantity of each UPS
model to order:
H Order one VE5006 UPS for each workstation and server.
H Order VE5006 UPS’s for DeltaV controllers as follows:

j If VE5001 system power supplies are used, order one VE5006 UPS for
each controller.
j If a combination of VE5009 power supplies and VE5012 Bulk AC to 12

VDC power supplies are used, order one VE5006 UPS for each VE5012
power supply.
H Order one VE5006 UPS for each VE5011 Bulk AC to 24 VDC power supply.
7-8 v10.3:March 2009

Workstations
Figure 8-Table 8
Chapter 8 Workstations
A DeltaV workstation consists of a Dell-brand personal computer (PC) or server
and a DeltaV software suite.
Workstation Licensing
Generally, process geography, plant operating strategy, and system size determine
the number of workstations and their node type. During DeltaV software
installation, the node type is declared, and then software licenses are assigned to
enable the software suites most appropriate for the DeltaV system.
Four workstation node types can be declared, and each type supports certain
software suites as listed in Table 8-1.
Table 8-1. Workstation Node Types and Supported Software Suites

Workstation Node Type Supported Software Suite
ProfessionalPLUS Station ProfessionalPLUS
Operator Station Professional
Operator
Basic
Maintenance
Application Station Application
Inter-Zone Server Zones Server
Add-on and scale-up licenses are available to add features and functionality to an
initial license and to increase the capacity of an existing license.
Four-Monitor License
Except for the Application Station software suite, each of the workstation software
suites can be viewed on one of the VE2533-series four-monitor workstations.
Licensed software (VE2401K01) is required for user interface across the monitors.

Workstations
Operator Keyboard
Operator keyboard lets you use one of the monitors in a four-monitor
workstation as a touchscreen monitor, displaying a standard-look keyboard. For
the keyboard monitor, select the VE2802 LCD Touchscreen monitor. A VE2401K01
license is required.
Batch Application License

Batch Executive, Batch Historian, Soft Phase Server, and Campaign Manager
applications are enabled in system-wide batch licenses (one batch license per
system). The licenses are Basic Batch, Advanced Batch, and Professional Batch.
Each license enables certain applications as shown in Table 8-2.
Table 8-2. System-Wide Licenses for Batch Systems
System-Wide License Applications Enabled by License
Batch Batch Soft Phase Campaign
Executive Historian Server Manager
Basic Batch X
Advanced Batch X X X
Professional Batch X X X X
After you choose a system-wide license, then choose its size. The size must be
equal to or greater than the size of the Advanced Unit Management license. (See
Chapter 3 for details of this license).
For most DeltaV systems, it is recommended to run Batch Executive and Batch
Historian on separate Application Stations. When these applications are run on
Application Stations, no non-batch applications should run on them.
If a Basic Batch license is 250 DSTs or less, you may be able to run Batch
Executive on other than Application Stations. For assistance in evaluating the
feasibility of this approach, refer to the whitepaper", DeltaV Batch Workstation
Selection, on the DeltaV WebCD.
If the DST size of the Advanced Batch license is expected to be 1,000 DSTs or
fewer, then its applications, along with Process History View Suite, may reside on
one Application Station.
The Batch Operator Interface application is no longer used in DeltaV version 9.3
and later.
8-2 v10.3:March 2009

Workstations
Remote Access Services (RAS)

DeltaV Remote Access Services (RAS) let you use Remote DeltaV Nodes to
perform operator or engineering functions from a non-DeltaV network or a
remote network up-link, such as a microwave or satellite link. The remote DeltaV
nodes connect and communicate through DeltaV RAS to perform operator
functions via standard DeltaV applications. Either a ProfessionalPLUS Station or an
Application Station can run DeltaV RAS.
A ProfessionalPLUS running DeltaV RAS can serve operating data to two remote
nodes. An Application Station running DeltaV RAS can serve up to 10 remote
nodes. These nodes can run Continuous Historian (250 Parameters), Control
Studio On-Line, Diagnostics, Event Chronicle, Process History View Suite, and
operating data to DeltaV Operate. For more details, see the DeltaV Remote Access
Services product data sheet and the Remote DeltaV sales information sheet.
Remote Client (Terminal Server)

DeltaV Remote Client lets you locate full-function DeltaV operator and
engineering workstations remotely to a DeltaV control network. Remote client
consists of a server, clients, and appropriate DeltaV licenses. It uses standard
computer hardware and Microsoft applications: Remote Desktop Connection and
Terminal Server. The client node uses a 32-bit Windows operating system
(preferably Windows XP) and the server uses the Windows Server 2003 operating
system. The computer hardware and Microsoft applications are ordered
separately.
Either a ProfessionalPLUS Station or a Base Station can be setup to function as a

remote client server (host machine). There is no limit to the number of remote
sessions which can be defined; however, there is a limit to the number of
concurrent remote sessions which can be open at one time. Factory tested open
sessions is fifteen. Use this quantity as a guideline, not a fixed limit.
Professional, Operator, or Maintenance Station licenses appropriate for the

intended tasks of the remote user (i.e., engineering, operation, or maintenance)
are assigned at each remote session.

Workstations
DeltaV Connect License

DeltaV Connect products let users of competitive process control systems migrate
to DeltaV workstations. Current DeltaV Connect products include interface to
Bailey consoles (VE2241 series), Siemens-Moore consoles (VE2243 series), and
Honeywell Systems consoles (VE2244 series). As a minimum, an Application
station, running the appropriate DeltaV Connect software, and a ProfessionalPLUS
station are required. For further information about DeltaV Connect products, see
corresponding product data sheets.
FlexConnect Solutions
FlexConnect solutions provide direct connection from other manufacturer’s
termination assemblies to DeltaV I/O card terminal blocks. These solutions permit
the use of their I/O with DeltaV systems. To simplify installation, Emerson
pre-wires FlexConnect solutions to DeltaV I/O termination blocks. See product
data sheets for detailed information and the OEM systems which can be
connected to DeltaV systems.
Continuous History Data

Continuous history data in DeltaV Systems is retrievable from the DeltaV
Continuous Historian for non-DeltaV plant information systems, using the DeltaV
OPC Historical Data Access Server (OPC History Server, model number VE2227).
The OPC History Server is available on the Professional Plus and Application
Stations. One concurrent OPC Historical Data Access client connection is
provided with each OPC History Server. For more than one concurrent client
connection, the OPC History Server license is required. The OPC History Server
license allows up to 25 concurrent client connections per server.
It is recommended that the OPC History Server be used only for periodic
historical data transfer. Real-time data requests from the OPC History Server are
not recommended because real-time data requests may cause excessive load on
the DeltaV Continuous Historian, resulting in higher workstation CPU utilization
and potential loss of historical data. The DeltaV workstation CPU utilization
should always be considered when determining the optimum historical data
transfer rate from the OPC History Server. It is recommended that the CPU load
on the DeltaV workstation not exceed 75% for an extended period of time,
regardless of what applications are running on the workstation.
For real-time data retrieval from the DeltaV system, the DeltaV OPC Data Access
Server (model number series VE2201S) should be considered. All of the DeltaV
8-4 v10.3:March 2009

Workstations
parameters available for collection in the DeltaV Continuous Historian are

available in the OPC Data Access Server. The OPC Data Access Server is much
more efficient than the OPC History Server at retrieving real-time data from the
DeltaV system and it does not require use of the DeltaV Continuous Historian.
DeltaV Analyze License

DeltaV Analyze v1.2 lets you perform alarm analysis for selected plant areas based
on historical data in either Event Chronicle or Plantwide Event Historian. DeltaV
Analyze is ordered separately and is licensed.
DeltaV Analyze can run on a ProfessionalPLUS or Application Station where Event

Chronicle is enabled. Since DeltaV Analyze requires enabled IIS, you must decide
on which station you wish to run it. it can also run on a computer running
Plantwide Event Historian, whether a DeltaV machine or non-DeltaV machine.
When used with Event Chronicle, select VE2131 for single client mode or
VE2132Sxx (where xx is 07 for up to 7 clients, 15 for 8 to 15 clients, and 50 for 16
to 50 clients). When used with Plantwide Event Historian, select VF5005 for single
client mode or VF5006Sxx (where xx is 07 for up to 7 clients, 15 for 8 to 15
clients, and 50 for 16 to 50 clients).
Prerequisites for running DeltaV Analyze are:
H DeltaV system v7.3 or the Plantwide Event Historian v3.0 and later.
H Standard DeltaV workstation hardware specifications suitable for DeltaV

Analyze.
H A DeltaV Application Station with Event Chronicle enabled, or a workstation

with Plantwide Event Historian installed. Each workstation with an event
database to be analyzed must have a DeltaV Analyze license.
H Windows XP or Windows Server 2003 operating system. DeltaV Analyze on

Windows XP is only offered with the single concurrent user.
H Clients may be any workstation with Windows Internet Explorer version 6 or

later. Recommended client memory is 500 Mbytes. Concurrent user timeout is
20 minutes.
H DeltaV Analyze v1.2 is not supported on workstations with Version Control or

Batch Historian enabled.

Workstations
DeltaV Insight Basic and DeltaV Insight

For DeltaV version 9.3 and later, DeltaV Insight Basic replaces DeltaV Tune and
DeltaV Inspect. DeltaV Insight Basic (VE2134BASIC) is a single-client licensed
application which can be added to all workstations except the Application
workstation, It provides all of the functionality of DeltaV Tune with some
improvements in the user interface, history, and system loading.
The broader functionality of DeltaV Insight, contains advanced features, including

model-based metrics (tuning Index), loop diagnostics, and adaptive tuning
recommendations. DeltaV Insight provides system-wide unlimited client
connections based on system DST count. Model numbers are in the
VE2134-series, with selectable DST ranges up to 750, 2000, 5000, and 30,000 DSTs.
Scale up licenses are also available when systems are expanded. See the DeltaV
Insight product data sheet for details.
For existing customers, an upgrade path for DeltaV Tune and Inspect is available.
See the whitepaper, DeltaV Insight Upgrades, for details.
AMS Device Manager

In DeltaV version 9.3 and later, AMS Device Manager replaces DeltaV AMSinside.
Simultaneously, the Fieldbus Device Database is no longer required in DeltaV
v9.3 and later. AMS Device Manager must be used when you have fieldbus
devices in your DeltaV system.
Also in DeltaV 9.3 and later, AMS Audit Trail replaces DeltaV Device Audit Trail.
AMS Audit Trail may be ordered for those who wish to track access to the
manager.
For convenience, AMS Device Manager and AMS Audit Trail media is shipped in
the DeltaV product package on a separate DVD from DeltaV software. Obtain
licenses for AMS Device Manager and AMS Audit Trail from the Asset
Optimization Division.
8-6 v10.3:March 2009

Workstations
Third-Party Software Compatibility

Certain third-party software products are compatible with DeltaV systems and may
be incorporated into a system. A list of compatible software can be found on the
Compatibility Chart in the Release Notes Knowledge Based Article (KBA). It is
highly recommended to run third-party software only on an Application Station.
As with any third-party software, caution should be used when loading and
running it. See the third-party software policy statement on the DeltaV WebCD.
Caution... Do not risk the possible consequences of installing and using third-party
software not listed on the compatibility chart. Installing and using such
software on a DeltaV workstation which is used as a primary operator
interface may cause loss of operator visibility to the process, unexpected
system actions, and other unpredictable results. Emerson Process
Management cannot support proper operation of your system should you
take this risk.
Note ... For computer virus protection, we strongly recommend that you purchase
approved DeltaV anti-virus software and install it on all of your
workstations. Be sure to stay current with subsequent software releases to
protect your system from newly discovered viruses.

Workstations
Workstation Application Summary

Table 8-3 lists applications which are included, which can be added, and which
cannot be added in workstation software suites. This table summaries applications
listed in Table 8-4 through Table 8-9.
In Table 8-3, the marks mean:
n Application included.
- Application can be added with an add-on license.
-P Application can be added with an add-on license. A prerequisite application

may be required as defined in Table 8-10.
NA Application cannot be added.
Table 8-3. Applications Included, Can Be Added, or Not Available in Software Suites
Licensed Workstation Software Suite
Applications
Professional Professional Operator Base Application Maintenance
PLUS Station Station Station Station Station Station
Basic Batch -P NA NA NA -P NA
Advanced Batch NA NA NA NA -P NA
Professional Batch NA NA NA NA -P NA
Configuration Audit - NA NA NA NA NA
Trail
Configuration n NA NA NA NA NA
Database
Configuration n n - - NA -
Studio Suite
Configuration NA NA NA NA NA n
Studio Suite for
Maintenance
Continuous n n n n n n
Historian, 250
Parameters or less
Continuous NA NA NA NA -P NA
Historian > 250
Parameters
Control Studio n n -P -P NA -P
On-Line
DeltaV Analyze - NA NA NA - NA
Note: (1) OPC Excel Add-in OR OPC Events Server, but not both simultaneously
8-8 v10.3:March 2009

Workstations
Table 8-3. Applications Included, Can Be Added, or Not Available in Software Suites (Continued)
Licensed Workstation Software Suite
Applications
Professional Professional Operator Base Application Maintenance
PLUS Station Station Station Station Station Station
DeltaV Connect -P NA NA NA -P NA
DeltaV Insight - - - - NA -
Basic
DeltaV Neural n n NA NA NA NA
DeltaV Operate n n n - NA -
DeltaV Operate for NA NA NA NA NA n
Maintenance
DeltaV RAS for NA NA NA NA - NA
Application Station
DeltaV RAS for - NA NA NA NA NA
Professional-PLUS
Station
DeltaV Web Server NA NA NA NA -P NA
Device Audit Trail - NA NA NA - NA
Diagnostics n n n n n n
Event Chronicle n n - - - n
History View Suite n n n - - n
MPC Operate and n n n NA NA NA
MPC OperatePRO
Multivariate n n NA NA NA NA
Statistical Process
Control (MSPC+)
OPC Events - NA NA NA - NA
Server
OPC Excel Add-in - (1) - - - n -
OPC History - NA NA NA - NA
Server
OPC Mirror - NA NA NA - NA
OPC Pager - NA NA NA - NA
OPC Server, 250 - (1) NA NA NA NA NA
Data Values
OPC Server > 250 NA NA NA NA n NA
Data Values
Predict and n n NA NA NA NA
PredictPRO
Recipe Studio n n -P -P NA -P
Note: (1) OPC Excel Add-in OR OPC Events Server, but not both simultaneously

Workstations
ProfessionalPLUS Station Software Suite

A ProfessionalPLUS Station is the primary engineering and configuration interface
for a DeltaV System. The station provides the global configuration and contains
the configuration database for the system. Each DeltaV system must have one,
and only one, ProfessionalPLUS Station. For small DeltaV systems, a
ProfessionalPLUS Station also serves as the operator and diagnostics interface for
the system.
This station is sized in terms of DSTs. It must be sized to include the total quantity
of DSTs for the system. The quantity of selected DSTs may be larger than actually
required by the process due to rounding up to the nearest size increments.
Table 8-4 describes the ProfessionalPLUS Station Software Suite.
8-10 v10.3:March 2009

Workstations
Table 8-4. ProfessionalPLUS Station Software Suite, VE2101Sxxxx*

Applications Included Applications Can Be Added Applications Cannot Be Added
Configuration Database** Basic Batch, VE2234Sxxxx Advanced Batch

Configuration Studio Suite Configuration Audit Trail, Professional Batch
VE2139Sxxxx
Continuous Historian, 250 Configuration Studio Suite for
parameters or less DeltaV Connect: Bailey Blocks, Maintenance
VE2241Sxxxx
Control Studio On-Line Continuous Historian > 250
DeltaV Analyze, VE2131 or parameters
DeltaV Neural*** VE2132Sxx
DeltaV Operate for Maintenance
DeltaV Operate** DeltaV Insight Basic,
VE2134BASIC DeltaV RAS for Application
Diagnostics Station
Event Chronicle** DeltaV RAS for
ProfessionalPLUS, VE2151 DeltaV Web Server
History View Suite OPC Server > 250 data values
Device Audit Trail (xxxxx
MPC Operate and MPC Devices), VE2138Sxxxxx
OperatePRO***
OPC Events Server, VE2228
Predict and PredictPRO***
OPC Excel Add-in, VE2141 or
Recipe Studio*** OPC Server, 250 data values,
VE2223
OPC History Server, VE2227
OPC Mirror, (xxx Servers),
VE2212Sxxx
OPC Pager, VF1002M1
OPC Server, 250 Data Values,
VE2223
Note: * The “xxxx” in the VE-model number indicates that the product being licensed is available in various sizes. See
the product data sheet for details.
** The size of the ProfessionalPLUS determines the DST size of the Configuration Database, DeltaV Operate,
and Event Chronicle.
***With appropriate system license.

Workstations
Professional Station Software Suite

When you require additional DeltaV engineering workstations to that of the
ProfessionalPLUS station, use the Professional Station Software Suite. This suite
provides both an engineering and configuration interface and an operator
interface to a DeltaV System. The system database still resides on the
ProfessionalPLUS Station. Table 8-5 describes the Professional Station Software
Suite.
8-12 v10.3:March 2009

Workstations
Table 8-5. Professional Station Software Suite, VE2102Sxxxx*

Configuration Studio Suite DeltaV Insight Basic, Basic Batch

VE2134BASIC
Continuous Historian, 250 Advanced Batch
Parameters or less OPC Excel Add-in, VE2141
Professional Batch
Control Studio On-Line
Configuration Audit Trail
DeltaV Neural***
Configuration Database
DeltaV Operate**
Configuration Studio Suite for
Diagnostics Maintenance
Event Chronicle** Continuous Historian > 250
parameters
History View Suite
DeltaV Analyze
MPC Operate and MPC
OperatePRO*** DeltaV Connect
Predict and PredictPRO*** DeltaV Operate for Maintenance
Recipe Studio*** DeltaV RAS for Application
Station
DeltaV RAS for
ProfessionalPLUS Station
DeltaV Web Server
Device Audit Trail
OPC Events Server
OPC Mirror
OPC Pager
OPC History Server
OPC Server, 250 data values
OPC Server > 250 data values
the Product data sheet for details.
** The size of the Professional Station determines the DST size of the Operator Interface and Event Chronicle.

Workstations
Operator Station Software Suite

Operator Workstations are used to operate a process. They are sized by the
quantity of DSTs in the defined area of operation. To determine the size of an
Operator Station, define the areas for which an operator at a particular
workstation is responsible. Then, count the DSTs associated with these areas. Size
the station for a DST count that is equal to or greater than the area DST count.
For example, if there are 5 areas in a plant, and areas 1 and 2 are assigned to a
workstation, the station is sized for the total number of DSTs in areas 1 and 2.
The remaining areas can still be viewed from this workstation, but not operated
from it. Table 8-6 describes the Operator Station Software Suite.
To operate and view continuous history only, select the Operator Station Software
Suite. Applications typically added to this suite are Event Chronicle, Diagnostics,
and Control Studio On-Line.
8-14 v10.3:March 2009

Workstations
Table 8-6. Operator Station Software Suite, VE2104Sxxxx*

Continuous Historian, 250 Configuration Studio Suite, Basic Batch

Parameters or less VE2162
Advanced Batch
DeltaV Operate** Control Studio On-Line, VE2161
Professional Batch
Diagnostics DeltaV Insight Basic,
VE2134BASIC Configuration Audit Trail
History View Suite
Event Chronicle, VE2143 Configuration Database
MPC Operate and MPC
OperatePRO*** OPC Excel Add-in, VE2141 Configuration Studio Suite for
Maintenance
Recipe Studio, VE2164
Continuous Historian > 250
Parameters
DeltaV Analyze
DeltaV Connect
DeltaV Neural
DeltaV RAS for Application
Station
DeltaV RAS for
DeltaV Web Server
Device Audit Trail
OPC Events Server
OPC Mirror
OPC Pager
OPC History Server
Predict and PredictPRO
** The size of the Operator Station determines the DST size of the Operator Interface.
***With appropriate system license

Workstations
Base Station Software Suite

The Base Station is a roll-your-own" workstation. When additional workstations
are required to address a single task, such as configuration only or diagnostics
only, the Base Station is a very cost-effective solution.
The Base Station is sized according to the software application licenses added to
it. You may upgrade a Base Station to an Operator Station. If you do, the station
follows the sizing instructions for the Operator Station. Check the product data
sheet of each added software application to understand whether there is a size
dimension that will be attached to the station. Table 8-7 describes the Base
Station Software Suite.
8-16 v10.3:March 2009

Workstations
Table 8-7. Base Station Software Suite VE2106

Continuous Historian, 250 Configuration Studio Suite, Basic Batch

Parameters or less VE2162
Advanced Batch
Diagnostics Control Studio On-Line, VE2161
Professional Batch
DeltaV Insight Basic,
VE2134BASIC Configuration Audit Trail
DeltaV Operate, VE2126Sxxxx Configuration Database
DeltaV Insight Basic, VE2134 Configuration Studio Suite for

Maintenance
Event Chronicle, VE2143
Continuous Historian > 250
History View Suite, VE2145 parameters
OPC Excel Add-in, VE2141 DeltaV Analyze
Recipe Studio, VE2164 DeltaV Connect
DeltaV Neural
Station
DeltaV RAS for
DeltaV Web Server
Device Audit Trail
MPC Operate and MPC Operate
PRO
OPC Events Server
OPC Mirror
OPC Pager
OPC History Server

Workstations
Application Station Software Suite

The Application Station integrates your DeltaV system and the rest of your
day-to-day operations, using OLE for Process Control (OPC). With the Application
Station, you can also extend your DeltaV system with DeltaV applications and
other third-party applications tailored for your particular process.
Generally, the integration needs and add-on application software determine the
number of Application Stations required. Decisions as to the number of
Application Stations are also based on the isolation of key add-on applications. If
you are running batch applications in your system, see the Batch Application
Licensing section for Application Station requirements.
Application Station license size is based upon the number of data values that are
communicated through the OPC Server on the Application Station. Each value (for
example, a flow, a setpoint, a register) communicated through the OPC Server is
counted as a data value.
The sizing equation is:
Application Station size = Quantity of Data Values being read out of the
Application Station + Quantity of Data Values being written into the Application
Station
Once you have determined the approximate number of data values, you need to
consider how this data is being used within the system.
H For data values being read out of a DeltaV system, no further work is needed.
H For data values being written into a DeltaV system, the data values must be
hosted in modules somewhere within the DeltaV system. Each data value will
also be counted as either a DST or as a SCADA tag.
H For less than 50 data values being written into a DeltaV system, the data
values can be hosted in a DeltaV controller.
H For more than 50 data values being written into a DeltaV system, the data
values should be hosted directly in the Application Station.
If you need to integrate data in the Application Station with data from other OPC
Servers, the OPC Mirror application may also be added onto the Application
Station. Table 8-8 describes the Application Station Software Suite.
8-18 v10.3:March 2009

Workstations
Table 8-8. Application Station Software Suite VE2201Sxxxx*

Continuous Historian, 250 Basic Batch, VE2234Sxxx Configuration Audit Trail

Parameters or less
Advanced Batch, VE2235Sxxx Configuration Database
Diagnostics
Professional Batch, VE2236Sxxx Configuration Studio Suite
OPC Excel Add-in
Continuous Historian > 250 Configuration Studio Suite for
OPC Server > 250 data values** parameters, VE22nnSxxxx Maintenance
DeltaV Analyze, VE2131 or Control Studio On-Line
VE2132Sxx
DeltaV Insight Basic
DeltaV Connect: Bailey Block,
VE2241Sxxxxx DeltaV Neural
DeltaV RAS for Application DeltaV Operate

Station, VE2237
DeltaV Web Server, VE2231Sxx
DeltaV RAS for
Device Audit Trail (xxxxx ProfessionalPLUS Station
Devices), VE2138Sxxxxx MPC Operate and MPC
Diagnostics, VE2144 OperatePRO
Event Chronicle, VE2143 OPC Server, 250 data values
History View Suite, VE2145 Predict and PredictPRO
OPC Events Server, VE2228 Recipe Studio
OPC History Server, VE2227

OPC Mirror (xxx Servers),
VE2212Sxxx
OPC Pager, VF1002M1
Note: *The “xxxx” in the VE-model number indicates that the product being licensed is available in various sizes. See
**The size of the Application Station determines the data value size of the OPC Server, and is based on the
license.

Workstations
Maintenance Station Software Suite

The Maintenance Station provides maintenance personnel with a view of a DeltaV
system for maintenance purposes. It is sized according to the software application
licenses added to it.
You may upgrade a Maintenance Station to an Operator Station. If you do, the
station follows the sizing instructions for the Operator station. Check the product
data sheet of each software application added to understand whether there is a
size dimension that will be attached to the station. Table 8-9 describes the
Maintenance Station Software Suite.
8-20 v10.3:March 2009

Workstations
Table 8-9. Maintenance Station Software Suite VE2105

Configuration Studio Suite for Configuration Studio Suite, Basic Batch

Maintenance* VE2162
Advance Batch
Continuous Historian, 250 Control Studio On-Line, VE2161
Parameters or less Professional Batch
DeltaV Insight Basic,
Continuous Historian Excel VE2134BASIC Configuration Audit Trail
Add-in Configuration Database
DeltaV Operate, VE2126Sxxxx
DeltaV Operate for
OPC Excel Add-in, VE2141 Continuous Historian > 250
Maintenance**
parameters
Diagnostics Recipe Studio, VE2164
DeltaV Analyze
Event Chronicle DeltaV Connect
History View Suite
DeltaV Neural
Station
DeltaV RAS for
DeltaV Web Server
Device Audit Trail
MPC Operate and MPC
OperatePRO
OPC Events Server
OPC History Server
OPC Mirror
OPC Pager
OPC History Server
Note: *Allows calibration, but not configuration.
**Allows viewing of device alerts, but cannot acknowledge process alarms.

Workstations
Workstation Application Prerequisites

To be functional, some workstation applications require a prerequisite application
not included in the suite. For example, Advance Unit Management is a
prerequisite Basic Batch, Advanced Batch, and Professional Batch. Even when
one of these batch programs is a standard application in an Application. it is not
operational until Advance Unit Management is added. Table 8-10 lists workstation
applications which require prerequisites (some prerequisites are licensed). If a
workstation application is not listed, it does not require a prerequisite.
Table 8-10. Workstation Applications and Their Prerequisite Application

Workstation Application Prerequisite Application
Basic Batch, Advanced Advanced Unit Management
Batch, Professional Batch
Continuous Historian > Application Station, 250 data values or larger
250 parameters
Control Studio On-Line Operator Interface [Must reside in same station(s) in which Control Studio
On-Line resides].
Operation software for Base or Maintenance Station (VE2126Sxxxxx) is also
required if you wish to run Control Studio On-line on a Base or Maintenance
Station.
DeltaV Connect Application Station, 250 data values or larger
DeltaV Web Server Application Station, 250 data values or larger
Excel Add-in Excel spreadsheet (Purchase separately)
Process History View To view events on stations where Process History View Suite resides, Event
Suite Chronicle must reside on one or more stations.
To view batch history on stations where Process History View Suite resides,
either Advance Batch or Professional Batch must reside in the system.
Recipe Studio A Basic Batch, Advanced Batch, or Professional Batch is required. Any of
these licenses allow four Batch Executives per system, which can reside in
any of the system workstations; however, an Application Station is preferred.
To edit and save Recipe Studio, Configuration Studio Suite is required.
Without this suite, Recipe Studio is view only.
8-22 v10.3:March 2009

Workstations
Connecting to a Plant LAN

In most cases, ProfessionalPLUS Stations and Application Stations can be used as
a gateway between other networks and the DeltaV Control Network. The DeltaV
system provides industry standard interfaces which may be used to transfer data
between a DeltaV system and other systems or applications residing on
workstations connected to the LAN. DeltaV OPC servers provide access to DeltaV
real-time and historical data and may be licensed for use on a ProfessionalPLUS
Station and An application Station. DeltaV Web Services provide access to DeltaV
batch and continuous data and are available for use on an Application Station.
Each ProfessionalPLUS Station and Application Station can support as many as

five Ethernet cards, one of which can be used as a Plant LAN card, as follows:
H One Primary card
H One Secondary card
H One RAS Primary card
H One RAS Secondary card
H One Plant LAN or gateway card

DeltaV stations ship with three Ethernet network interface connections (one
primary DeltaV network connection, one secondary DeltaV network connection
and a Plant LAN connection). If you need more than the three connections, you
need to purchase and install the needed Ethernet cards.
You cannot move a card from an original workstation to another workstation,

even if it appears that the connection is not being used. The DeltaV system
expects that network interface connection to be there and the system will not
function properly without it.

Workstations
DeltaV Zones
DeltaV Zones is a combination of hardware and software for connecting two or
more DeltaV systems through an Inter-Zone Network. DeltaV Zones let you
control or monitor a DeltaV system in one zone with workstations of a DeltaV
system in another zone.
An Inter-Zone Server (IZS) must be installed in each DeltaV system to implement

zones. Inter-Zone Servers are connected by an Inter-Zone Control Network
(IZCN). An IZCN may be simplex or redundant. A simplex network requires one
network switch; a redundant network requires two network switches. An IZCN
follows the same rules as a standard DeltaV Control Network. See Chapter 2 for
details.
The only function of the Inter-Zone Servers and the Inter-Zone Network is to
communicate inter-zone operating data between systems. Refer to the System
Administration and Maintenance manual in DeltaV Books Online for complete
information on implementing zones, zone-to-zone data communication, and
security considerations.
Each zone requires a license. Licenses, (VE2111E000 through VE2111E080), are

purchased based on the quantity of workstations in one zone which will be used
to access systems in other zones. For example, if three workstations in a system
will be used to access systems in other zones, purchase VE2111E003 for the
system. If no workstations in a system will be used for access, but the system is
connected to other zones, purchase VE2111E000 for the system.
When scaling up an installed DeltaV system, scale up licenses, VE2111E053 and

VE2111E054, are available to increase the number of workstations available for
access to other zones. Figure 8-1 shows three DeltaV systems connected to
Inter-Zone Servers through an Inter-Zone Network. Although the figure shows
simplex Inter-Zone Servers, you can have redundant ones. For redundancy, a
redundant license is required, VE2111RED.
8-24 v10.3:March 2009

Workstations
Inter-Zone ProPLUS
Server Station
Controller
Primary
Primary Switch
Switch
Secondary
Secondary Switch
Switch DeltaV Control Network
Inter-Zone ProPLUS
Server Station
Inter-Zone Network
Controller
Primary
Switch
Secondary
Switch
DeltaV Control Network
Inter-Zone ProPLUS
Server Station
Controller
Primary
Switch
Secondary
Switch
DeltaV Control Network
Figure 8-1 Simple Inter-Zone Control Network

Workstations
8-26 v10.3:March 2009

Computer Selection and Security
Figure 9-Table 9
Chapter 9 Computer Selection and Security
Refer to workstation and server product data sheets for detailed information
about computers currently available for DeltaV systems.
Hardware Classes
Computers used in DeltaV systems can be divided into two main classes: server
class and workstation class. For DeltaV version 7.2 and later, a server class
machine runs Microsoft’s Windows Server 2003 operating system and a
workstation class machine runs Microsoft’s Windows XP Professional operating
system.
For a small system, all DeltaV PC nodes can run on workstation class machines.
However, larger systems may require a server class machine. The determining
factors are the overall PC node count of the system, the node’s specific role in the
system, and the desired security and login account scheme.
Servers offer more CPU, more storage capacity, and increased reliability over PCs.
The server operating system is optimized and licensed to serve a large number of
client connections, and is only certified to run on server class machines.
Running the ProfessionalPLUS workstation on a server class machine gives you

the option, at system installation, of using a Windows domain security and login
account scheme. Also, by running the workstation on a server, it can be setup as
a domain controller where user login accounts can be centralized.
If the overall PC node count is over 11, your ProfessionalPLUS workstation must
be licensed as a server class machine. An Application workstation serving a
primary role in a large batch system, OPC data transfer, or historical collection
may also require a server class machine.

PC Selection
A DeltaV system is specifically qualified to run on certain models of Dell PC
hardware. This hardware is extensively tested to ensure optimum performance
and stability for your DeltaV system. Use the Workstation Selection50.xls
spreadsheet, located on your DeltaV WebCD, to calculate which PC platform is
best suited for your system. Use the guidelines below to select the Dell PC for
your workstation.
ProfessionalPLUS Workstation
Use one of the VE2532-series Precision T3400 Workstations except as follows:
If the DeltaV system includes one or more Professional Workstations, use one of
the VE2535C2-series Dual-CPU PowerEdge 2900 III or VE2536C2-series Dual-CPU
PowerEdge 2950 III Servers.
Note ... When a ProfessionalPLUS Workstation is running on a server, it should not

be used as an Operator Station to operate your process. Servers do not
support sound; therefore, they cannot provide audible alarm indications.
Professional Workstation, Operator Workstation, and

Maintenance Workstation
Use one of the VE2531-series Optiplex GX755 PCs except as follows:
H If dual monitors are required, use one of the VE2532-series Precision T3400
Workstations.
H If four monitors are required, use the VE2533M99L01 Precision T3400

Workstation with VE2801 and VE2802 LCD monitors.
Base Workstation
Use one of the VE2531-Series Optiplex GX755 PCs except as follows:
H If dual monitors are required, use one of the VE2532-series Precision T3400
Workstations.
H If four monitors are required, use the VE2533M99L01 Precision T3400

Workstation with VE2801 and VE2802 LCD monitors.
9-2 v10.3:March 2009

H If used as a host server that serves remote clients, use one of the following
servers:
j VE2529-series PowerEdge 840 Server
j VE2535C1-series Single-CPU PowerEdge 2900 III Server or

VE2536C1-series Single-CPU PowerEdge 2950 III Server
Note ... When a Base Workstation is running on a server, it should not be used as
an Operator Station. Servers do not support sound; therefore, they cannot
provide audible alarm indications.
Application Workstation
Use one of the VE2532-series Precision T3400 Workstations except as follows:
H If Batch Executive larger than 15,000 DSTs is installed, use one of the
VE2535C1-series Single-CPU PowerEdge 2900 III Servers or VE2536C1-series
Single-CPU PowerEdge 2950 III Servers.
H If Batch Historian is installed, use one of the VE2535C1-series Single-CPU

PowerEdge 2900 III Servers or VE2536C1-series Single-CPU PowerEdge 2950
III Servers.
Note ... It is recommended that you install the Batch Historian and Batch Executive
on separate Application Workstations.
H If DeltaV Web Server is installed, use one of the VE2535C1-series Single-CPU

PowerEdge 2900 III Servers or VE2536C1-series Single-CPU PowerEdge 2950
III Servers.
Note ... For security purposes, it is recommended that you install DeltaV Web Server
on its own Application Workstation.
H If fault-tolerance is required, use one of the VE2403-series Stratus

Fault-Tolerant servers.

Windows Domain Security and Login Accounts

Large DeltaV systems should be setup in a Windows Active Directory. The benefit
is centralized user account information which reduces the administration tasks of
the system. For this setup, a ProfessionalPLUS station must be a domain controller
for the Active Directory.
Centralized user accounts let each PC validate and authenticate each login with
the centralized database on the domain controller. The accounts also eliminate
the need to update a user account on each machine every time an account needs
to be added, changed, deleted, or a password needs to be changed or reset. The
DeltaV User Manager is automatically integrated with the centralized account
database for the domain. When a user needs a new account or password reset, an
administrator simply logs into a DeltaV PC node, invokes the DeltaV User
Manager, and performs the necessary function, once.
However, with a centralized security system, there may be a concern if the central
point fails. The structure of a Windows domain uses two methods that eliminate
this concern: cached accounts and peer domain controllers.
A cached account is a process where each workstation caches the security

information of each user at login. If the domain controller in the ProfessionalPLUS
workstation is not operating or is unreachable, the cached information allows a
user to login and operate. By default, up to 10 accounts are cached.
A second, or peer, domain controller is a separate computer, running the server

operating system and specifically configured as a domain controller in that
domain. Once configured, the peer domain controller receives replication updates
of the security information for the domain. If the ProfessionalPLUS domain
controller is not operating, the peer domain controller functions as the domain
controller.
A DeltaV system requires the ProfessionalPLUS workstation to be a domain

controller at the time of installation, upgrade, or re-installation (anytime the
Workstation Configuration Utility is initiated). The peer domain controller must be
a server class machine installed as a domain controller for that domain. This
machine can be a DeltaV Application workstation.
9-4 v10.3:March 2009

Cyber Security for Dell PCs Used in DeltaV Systems

Prior to delivery to an end user, Dell PCs must be setup to provide the most cyber
secure DeltaV system possible. In addition, certain pre-cautions must be taken to
minimize any data corruption after delivery. Procedures described below are part
of the requirements for integrator certification for a DeltaV system.
The intention of these procedures is to ensure that the customer receives the most
cyber protected, cyber secure system possible. Integrators must be able to verify
to the customer that the system has been in a secure environment at all times.
When a PC is received from Dell and prior to any network connections being
made, the following must be done:
H The latest supported security patches from Microsoft must be installed.
H The latest supported Symantec anti-virus program and the latest anti-virus
signature files must be installed.
Beyond these actions, a DeltaV PC must never be attached to any network with
direct access to the internet. Direct access means that a user can open the Internet
Explorer and immediately connect to an internet site. E-mail programs must never
be run on a DeltaV workstation at any time.
The DeltaV system should never be connected to any network unless it is

properly protected with a correctly configured firewall. The firewall should
specifically block all port 80 (internet) traffic and any port that can be used for
e-mail traffic. All ports should be blocked in both directions except for those
needed for applications on the DeltaV Control Network.
Upon installation, all default user passwords should be changed to prevent

unauthorized users from accessing the system. Each user at the integrator site
should have a unique account and any account not required for startup must be
deleted before the system is shipped to the customer. After startup is complete, all
non-customer accounts should be deleted.

To insure that only authorized customer accounts remain on the system after
implementation, the customer administrator should change the admin password
and delete any vendor accounts. If a vendor account is required, the user may set
up the account, but it is strongly suggested that the account be given limited
capabilities, only enabled for the time required for the vendor to provide the
necessary service, and then disabled again.
Because an anti-virus program may not completely clean a computer, or if there is

any suspicion that other undetectable malicious programs may have been
installed, it is best practice to have its hard-drive reformatted and the system
completely re-installed. This ensures that no traces of the infection remains and
that no undetected malicious programs remain.
9-6 v10.3:March 2009

Hardware Planning
Figure 10-Table 10
Chapter 10 Hardware Planning
This chapter describes OEM-supplied items, information about determining space,
power requirements, ambient conditions, enclosure specifications, and physical
dimensions for a DeltaV system.
OEM Items
You may need to purchase additional items from suppliers other than Emerson
Process Management to complete your DeltaV system. Items can include:
H Field wiring, marshalling and cable-management hardware (such as panduit,

cable ties, etc.) installed between DeltaV I/O terminations and field devices.
H Mating connectors and associated cabling for multi-pin connectors on the

10-pin, 16-pin and 24-pin mass I/O termination blocks, such as those used in
programmable logic controllers (PLC) and marshalling panel applications.
They are available from suppliers such as Weidmuller, Phoenix Contact, and
AMP.
Table 10-1 provides examples of specific mating connectors and ribbon cables
from AMP. Contact AMP for specification details on the items.
Table 10-1. AMP Cable Management Accessories

Mass I/O AMP Part Number For AMP Part Number AMP Part Number
Terminal Mating Connector For Ribbon Cable For Strain Relief
Block
10-pin 746288-1 57034-3 499252-5
16-pin 746288-3 57034-6 499252-8
24-pin 746288-5 57034-8 1-499252-0
H DIN rail to mount controller and I/O carriers.
H Enclosures to house controllers and I/O. These can be ordered from Emerson
Process Management with an Integrated System Request (ISR).
H Furniture for workstations. These can be ordered from Emerson Process

Management with an Integrated System Request (ISR).

Hardware Planning
H AC power wiring between power mains and the VE5001 AC to DC System

Power Supply, the VE5011 Bulk AC to 24 VDC Power Supply, and the VE5012
AC to 12 VDC bulk power supply.
H 12 VDC power wiring between the VE5008 DC/DC Dual System Power
Supply and either the VE5012 AC to 12 VDC bulk power supply or the
VE5005 24 VDC to 12 VDC bulk power supply.
H 24 VDC power wiring between the VE5011 Bulk AC to 24 VDC Power Supply
and bussed power connectors on I/O carriers.
H Terminal Blocks for power distribution.
H Fiber optic cable to link control network switches and transceivers.
H Additional Ethernet interface cards (three are shipped with each DeltaV
system).
H Bus I/O system cables and termination equipment for As-i Bus, DeviceNet,
FOUNDATION fieldbus, and Profibus systems.
H Microsoft Excel spreadsheets used with the Excel Add-in option available in
the various types of workstation software.
Site Preparation
Proper power, grounding, and signal wiring is extremely important for optimum
DeltaV system operation. Even the best control systems can only be as good as
the electrical foundation on which they are built. Clean input power, single-point
grounding, and adequate shielding from outside interference are a must. For
DeltaV systems to meet customer’s expectations, power, grounding and signal
wiring must be correctly designed and installed before the system is delivered.
For details of proper site preparation, see the manual, Site Design and
Preparation for DeltaV Digital Automation Systems. It is included on the DeltaV
Documentation Library CD, on the DeltaV WebCD, and on the Foundation
Support website. It can also be ordered separately as a printed manual.
10-2 v10.3:March 2009

Hardware Planning
AC Power Calculation
You need to estimate AC power required by a DeltaV system so that an adequate
AC power distribution system can be designed. Table 10-2 provides normal AC
current draw for DeltaV Control Network products and power supplies.
Use the entries in this table to make estimates. For more exact figures, see DeltaV
product data sheets or manufacturer’s manuals. For power consumption of
workstations, servers, and monitors, see the Dell Computer Website at:
www.dell.com.
Table 10-2. AC Current Draw for Control Network Products and Power Supplies
Product Amps at 115 VAC Amps at 230 VAC
Allied Telesyn AT-FS708 8-Port 10/100Base-TX Ethernet 0.4 0.2
Switch
Allied Telesyn AT-FS709FC 8-Port 10/100Base-TX Ethernet 0.8 0.4
Switch (with one 100Base-FX port supporting up to 2 Km of
fiber)
Cisco Catalyst 2960-8TC-L 8-Port 10/100Base-TX Fast 0.5 0.25
Ethernet Switch with one SFP Slot
Cisco Catalyst 2960-24TC-L 24-Port 10/100Base-TX Fast 3.0 1.5
Ethernet Switch with two SFP Slots
Cisco Catalyst 2960−48TC−L 48-Port 10/100Base-TX Fast 3.0 1.5
Ethernet Switch with two SFP Slots
Cisco Catalyst 2960-24 TT-L 24-Port 10/100Base-TX Fast 1.3 0.8
Ethernet Switch with two 10/100/1000 Ports
Cisco Catalyst 2960-48TT-L 48-Port 10/100Base-FX Fast 1.3 0.8
Ethernet Switch with two 10/100/1000 Ports
Cisco Catalyst 3750-24FS 24-Port 100Base-FX Fiber Optic 1.5 0.9
Switch with two 1 Gigabit Converter Interface Ports
Cisco Catalyst 3750-24TS-S 24-Port 10/100Base-TX Fast 1.2 0.6
Ethernet Switch with two slots for Gigabit Transceivers
Cisco 3750G12S-S 12 Slot Gigabit Switch 1.2 0.6
VE5001 AC to DC System Power Supply 0.34 0.17
VE5012 Bulk AC to 12 VDC Power Supply 4.2 4.2
VE5011 Bulk AC to 24 VDC Power Supply 4.2 4.2

Hardware Planning
Power Requirements for a Controller and I/O Subsystem

The amount of power required for a DeltaV controller and I/O subsystem varies
with the type and quantity of I/O cards plugged into the I/O subsystem. If you
use redundant controllers, you need at least two system power suppliesone for
each controller, regardless of the type and quantity of I/O cards.
Caution... Several power supplies are available for DeltaV controllers and I/O
subsystems. To minimize the possibility of carrier damage, you must
choose a power supply that does not have the potential for providing
more current than a carrier can handle. Horizontal carriers are specified at
8A and vertical carriers at 15A.
Each VE5001 AC to DC System Power Supply can deliver a maximum of 25 watts

(2.1A). Each VE5008 DC/DC Dual System Power Supply can deliver a maximum
of 96 watts (8.0A). When determining the number of VE5001 or VE5008 supplies
required for a controller and its associated I/O, only I/O needs to be considered.
To determine power required for I/O, refer to Table 10-3 for the maximum
current draw of individual I/O cards. To determine the total current draw, add the
currents for each card. Complete I/O card specifications are listed in the manual,
Installing Your DeltaV Digital Automation System. Be sure to use the manual
published for DeltaV version 10.3.
Table 10-3. DC Current Requirements for I/O Cards

Product Maximum LocalBus Maximum Field Circuit
Current (12 VDC Nominal), Current (24 VDC, Nominal),
Per Card Per Card
Pre-Series 2 I/O Cards
AI, 8-channel, 4−20 mA 150 mA 300 mA
AI, 8-channel, 4−20 mA with HART 150 mA 300 mA
AI, 8-channel, 1−5 VDC 150 mA 100 mA
AI, 8-channel, Thermocouple, mV 350 mA N/A
AI, 8-channel, RTD 160 mA N/A
AO, 8-channel, 4−20 mA 150 mA 300 mA
10-4 v10.3:March 2009

Hardware Planning
Table 10-3. DC Current Requirements for I/O Cards (Continued)

Per Card Per Card
AO, 8-channel, 4−20 mA with HART 150 mA 300 mA
DI, 8-channel, 24 VDC, Isolated 100 mA N/A
DI, 8-channel, 24 VDC, Dry Contact 100 mA 40 mA
DI, 8-channel, 120 VAC, Isolated 100 mA N/A
DI, 8-channel, 120 VAC, Dry Contact 100 mA N/A
DI, 8-channel, 230 VAC, Isolated 100 mA N/A
DI, 8-channel, 230 VAC, Dry Contact 100 mA N/A
DI, 16-channel, Sequence of Events 75 mA 75 mA
(SOE)
DI, 32-channel, 24 VDC Dry Contact 75 mA 150 mA
DO, 8-channel, 24 VDC, Isolated 150 mA N/A
DO, 8-channel, 24 VDC, High Side 150 mA depends on field devices;
3.0 A maximum
DO, 8-channel, 115/230 VAC, Isolated 150 mA N/A
DO, 8-channel, 115/230 VAC, High Side 150 mA N/A
DO, 32-channel, 24 VDC, High Side 150 mA depends on field devices;
3.2 A maximum
I.S. AI, 8-channel, 4−20 mA with HART 600 mA N/A
I.S. AO, 8-channel, 4−20 mA 630 mA N/A
I.S. AO, 8-channel, 4−20 mA with HART 630 mA N/A
I.S. DI, 16-channel 350 mA N/A
I.S. DO, 4-channel 560 mA N/A
I.S. LocalBus Isolator 60 mA N/A
AS-i Interface 300 mA 40 mA
DeviceNet 600 mA N/A
Fieldbus H1Card 600 mA N/A
Fieldbus H1 Carrier, Input power N/A 20 mA (carrier only); 500 mA
max. with cards)
Multifunction/Pulse 250 mA N/A
Profibus DP 600 mA N/A
Serial Interface with 2 Ports RS232/RS485 300 mA N/A

Hardware Planning
Table 10-3. DC Current Requirements for I/O Cards (Continued)

Per Card Per Card
Series 2 I/O Cards
Series 2 AI, 4-channel, isolated mV, V, 350 mA N/A
RTD, Ohms, TC, Simplex only
Series 2 AI, 8-channel, 4−20 mA with 150 mA 300 mA
HART, Simplex
Series 2 AI, 8-channel, 4−20 mA with 250 mA per card 200 mA per card
HART, Redundant
Series 2 AI, 16-channel, 4−20 mA with 150 mA 600 mA
HART, Simplex only
Series 2 AO, 8-channel, 4−20 mA with 250 mA 300 mA
HART, Simplex
Series 2 AO, 8-channel, 4−20 mA with 250 mA per card 300 mA per card
HART, Redundant
Series 2 DI, 8-channel, 24 VDC, Dry 150 mA 40 mA
Contact, Simplex
Series 2 DI, 8-channel, 24 VDC, Dry 150 mA per card 20 mA per card
Contact, Redundant
Series 2 DI, 32-channel, 24 VDC, Dry 75 mA 150 mA
Contact
Series 2 DO, 8-channel, 24 VDC, High 150 mA depends on field devices;
Side, Simplex 3.0 A
Series 2 DO, 8-channel, 24 VDC, High 150 mA per card depends on field devices;
Side, Redundant 3.0 A per card
Series 2 DO, 32-channel, 24 VDC, High 150 mA 3.2 A
Side, Simplex
Series 2 DeviceNet, Simplex 600 mA 40 mA
Series 2 Fieldbus H1, Simplex 300 mA N/A
Series 2 Fieldbus H1, Redundant 300 mA per card N/A
Series 2 Profibus, Simplex 600 mA N/A
Series 2 Serial Interface with 2 Ports, 300 mA N/A
Simplex
Series 2 Serial Interface with 2 Ports, 300 mA per card N/A
Redundant
10-6 v10.3:March 2009

Hardware Planning
Enclosures
A variety of enclosures are available to protect a DeltaV system from
environmental conditions when the conditions are outside of the specified limits
for DeltaV products. Enclosures can range from simple sheet metal boxes to
NEMA 4X rated units.
Enclosures are designed to properly dissipate heat generated within the

enclosure, maintain an ambient temperature in the enclosure which is within the
range of installed devices, and filter potentially damaging air-borne contaminants.
You must take into account the space needed in and around an enclosure to
service, remove, or replace components.
Note ... To ensure adequate airflow through I/O cards, horizontal I/O carriers must
be mounted horizontally and vertical I/O carriers must be mounted
vertically.
To determine the optimal enclosure for temperature control, consider the

following:
H Maximum external ambient temperature
H Power dissipation of each installed device
H Internal temperature of the enclosure (cannot exceed the ambient rated

temperature for any devices located in the enclosure)
H Physical dimensions of the DeltaV components to be enclosed
H Adequate access space around installed components

Selecting enclosures for control of air-borne contaminants should be done with
the help of experts in this field.
Mounting DeltaV Systems in Enclosures

Figure 10-1 and Figure 10-2 show arrangements for horizontally mounting a
DeltaV system in an enclosure, including areas available for wire management.
Figure 10-3 shows an arrangement for vertically mounting a DeltaV system. Wiring
can be fed into an enclosure through gland plates or through conduit entries. The
cabinet supplier can help you select the proper arrangement for the application.

Hardware Planning
610 mm (24.02 in.)
Mounting
Plate
Top View
Optional
AC Power Wall Mount
Distribution Enclosure 223 mm
(8.78 in.)
Bulk Power Supply
81 mm
DIN (3.19 in.)
Rail
102 mm
(4.0 in.)
610 mm
(24.02 in.) 114 mm
(4.50 in.)
Bundled Cable Area
Optional Wire Way Front View Side View

50 X 75 mm (2 X 3 in.)
Figure 10-1 Enclosure Example for Controller and 8 I/O Interfaces
10-8 v10.3:March 2009

Hardware Planning
1219 m m (48.0 in.)
M ou nt ing
P lat e
Top View
O ptional Wall M ount 223 m m
A C Pow er E nclosure (8.78 in.)
D istribution
B ulk
Pow er S upply
D IN
143 m m
Rai l
(5.63 in.)
102 m m
(4.0 in.)
762 m m
(30.0 in.)
151 m m
(5.96 in.)
B undled C able A rea
Front View Sid e View

O ptional W ire Way
50 x 75 m m (2 x 3 in.)
Figure 10-2 Enclosure Example for Controller and 24 I/O Interfaces

Hardware Planning
Top View
10.2 cm (4.0 in.)
71.1 cm Mounting Sur-

(28.0 in.) face
Bundled
5.8 cm Front View Cable Area
(2.3 in.)
Edge of
Mounting Surface
DIN Rail
185.9 cm
(73.2 in.)
71.1 cm
(28.0 in.)
Figure 10-3 Enclosure Example for Vertically Mounted I/O Carriers
10-10 v10.3:March 2009

Hardware Planning
Power Dissipation Considerations

The power dissipated within an enclosure generates heat. An enclosure vendor
uses power dissipation figures to determine airflow requirements needed to
maintain heat within allowable limits. When there is no internal heat control, a
change in internal heat requires an equal and opposite change in external
ambient temperature.
The power dissipation in an enclosure is relational to the power requirements of

the enclosed equipment, including the power required to operate the equipment
and the field power dissipation within the enclosure. Table 10-4 lists the
maximum power dissipation for DeltaV products. To determine the total power
dissipation, sum the power dissipated by each component.
Table 10-4. Maximum Power Dissipation for DeltaV Products

Product Power Dissipation
(includes power supplies) (1)
Controller Equipment
Remote Interface Unit 6.0 W
MD, MD Plus, and MX Controller 14.0 W
Pre-Series 2 I/O Cards
AI, 8-channel, 4−20 mA 10.1 W
AI, 8-channel, 4−20 mA, HART 10.1 W
AI, 8-channel, 1−5 VDC 10.1 W
AI, 8-channel, Thermocouple, mV 5.9 W
AI, 8-channel, RTD 2.7 W
AO, 8-channel, 4−20 mA 11.9 W
AO, 8-channel, 4−20 mA with HART 11.9 W
DI, 8-channel, 24 VDC, Isolated 3.6 W
DI , 8-channel, 24 VDC, Dry Contact 2.9 W
DI , 8-channel, 120 VAC, Isolated 3.4 W
DI, 8-channel, 120 VAC, Dry Contact 3.4 W
DI, 8-channel, 230 VAC, Isolated 3.6 W
DI, 8-channel, 230 VAC, Dry Contact 3.6 W
DI, 16-channel, SOE 3.5 W
DI, 32-channel, 24 VDC, Dry Contact 5.7 W
DO, 8-channel, 24 VDC, Isolated 4.9 W

Hardware Planning
Table 10-4. Maximum Power Dissipation for DeltaV Products (Continued)

DO, 8-channel, 24 VDC, High Side 3.7 W + load dependent power
dissipation (maximum of 25 W at
24 VDC (2))
DO, 8-channel, 115/230 VAC, Isolated 6.1 W
DO, 8-channel, 115/230 VAC, High Side 6.1 W
DO, 32-channel, 24 VDC, High Side 3.0 W + load dependent power
dissipation (maximum of 27 W at
24 VDC (3))
AS-i Interface 9.6 W
DeviceNet 11.4 W
Fieldbus H1 card 10.2 W
Multifunction/Pulse 8.2 W
Profibus DP 10.1 W
Serial Interface with 2 Ports 5.1 W
PROVOXr I/O Interface Module 3.6 W typical, 6.0 W maximum
RS3t I/O Interface Module 13.2 W typical, 17.0 W maximum
Series 2 I/O Cards
Series 2 AI, 4-channel, Isolated mV, V, RTD, Ohms, 5.9 W
TC, Simplex only
Series 2 AI, 8-channel, 4−20 mA with HART, 8.4 W
Simplex
Series 2 AI, 8-channel, 4−20 mA with HART, 9.1 W per card
Redundant
Series 2 AI, 16-channel, 4−20 mA with HART, 12.7 W
Simplex only
Series 2 AO, 8-channel, 4−20 mA with HART, 10.2 W
Simplex
Series 2 AO, 8-channel, 4−20 mA with HART, 10.2 W per card
Redundant
Series 2 DI, 8-channel, 24 VDC Dry Contact, 3.7 W per card
Simplex and Redundant
Series 2 DI, 32-channel, 24 VDC Dry Contact, 5.7 W per card
Simplex
Series 2 DO, 8-channel, 24 VDC High-Side, 3.7 W per card
Simplex and Redundant
10-12 v10.3:March 2009

Hardware Planning

Series 2 DO, 32-channel, 24 VDC High-Side, 3.0 W + load dependent power
Simplex dissipation (27 W maximum at 24
VDC) (3)
Series 2 DeviceNet, Simplex 11.4 W
Series 2 Fieldbus H1, Simplex and Redundant 6.1 W per card
Series 2 Isolated Input (supports mV, V, RTD, 5.9 W
Ohms, TC), Simplex
Series 2 Profibus, Simplex 10.1 W
Series 2 Serial Interface with 2 Ports, Simplex and 5.1 W per card
Redundant
Intrinsically Safe I/O Cards
I.S. AI, 8-channel, 4−20 mA with HART 9.8 W
I.S. AO, 8-channel, 4−20 mA with HART 11.3 W
I.S. DI, 16-channel 7.6 W
I.S. DO, 4-channel 8.5 W
Power Supplies
AC to DC System Power Supply 4.4 W
Dual DC/DC System Power Supply, 12 VDC input 2.0 W
Dual DC/DC System Power Supply, 24 VDC input 5.2 W
DIN Rail Mounted Bulk AC to 12 VDC Power 12 W
Supply
DIN Rail Mounted Bulk AC to 24 VDC Power 12 W
Supply
Panel-Mounted Bulk AC to 12 VDC Power Supply 22 W
Panel-Mounted Bulk AC to 24 VDC Power Supply 22 W
Bulk 24 VDC to 12 VDC Power Supply 14.5 W
SIS Components
Simplex Logic Solver 21.4 W
Redundant Logic Solver 32 W
SISNet Repeaters 9.6 W (per Repeater)
Auxiliary Relay Modules, Energize to Actuate and 4.65 W
De-Energize to Actuate 24 VDC
Auxiliary Relay Diode Module 2.25 W

Hardware Planning

Miscellaneous Components
Fieldbus H1 carrier 5.2 W (4)
Media converter 5.1 W
DeltaV Single Port Fiber Switch 8.2 W
DeltaV Four Port Fiber Switch 8.4 W
I.S. Local Bus Isolator 1.2 W
I.S. System Power Supply 1.5 W
1. The power dissipation for each DC-powered discrete and analog card includes the
loss of a power supply which is 75% efficient. If the power supply is not included in
the enclosure or a supply with a different efficiency is used, adjust the dissipation
accordingly.
2. Power dissipation in this card is based on a full load of 3 A at 24 V. Actual
dissipation is determined by the following equation:
Supply Voltage X Actual Load Current ( 8 channels) X [(1Bpower supply
efficiency) − 1]
A typical value for eight channels driving eight 24 VDC solenoids is 16.4 W.
3. Power dissipation in this card is based on a full load of 3.2 A at 24 V. Actual
dissipation is determined by the following equation:
Supply Voltage X Actual Load Current (32 channels) X [(1Bpower supply
efficiency) − 1]
4. Does not include I/O card dissipation or 2.2 W power supply dissipation. (Assumes
power supply is not in the same enclosure as the H1 carrier).
Enclosure Selection Procedure

To select the proper enclosure for your DeltaV system:
H Determine the allowable temperature rise by subtracting the expected

ambient temperature from the lowest rated temperature of the components to
be mounted in the enclosure.
H Use Table 10-4 to determine the power dissipation for the components to be
mounted in the enclosure.
H Using the temperature rise and power dissipation information, the enclosure
supplier can determine the enclosure surface area and cooling options
required for your application.
10-14 v10.3:March 2009

Hardware Planning
Example Enclosure Selection Calculation

Assume the system consists of the following components:
Table 10-5. Example Products in the Selection Calculation

Qty Product Power Dissipation
1 MX Controller 14.0 W
1 AI, 8-channel, 4−20 mA, HART 10.1 W
1 AO, 8-channel, 4−20 mA 11.9 W
1 DI, 8-channel, 24 VDC, isolated 3.6 W
1 DO, 8-channel, 24 VDC, high side (driving 8 solenoids) 3.7 W + 16.4 W
2 DO, 8-channel, 120/230 VAC, isolated 12.2 W
2 DI, 8-channel, 120 VAC, isolated 6.8 W
1 AC to DC System Power Supply 4.4 W
1 Bulk AC to 24 VDC Power Supply 22 W
Total power 105.1 W
Assume ambient temperature is 35º C. The DeltaV components are rated for an
ambient temperature of 60º C. Therefore, the enclosure design temperature rise
must be less than 60 − 35 = 25º C with 105.1 W of heat dissipation within it. If the
surface area of the enclosure is insufficient to dissipate the heat, you can use
cooling options such as fans or blowers to improve heat dissipation.
The actual temperature rise varies with layout, enclosure location, and other
factors. If the application is critical, or if the exact conditions are undetermined,
follow your standard corporate/plant safety standards. Cabinet manufacturers
recommend a safety margin of 25%.
Physical Dimension Considerations

To ensure correct enclosure procurement, the size and weight of all items to be
enclosed must be totaled. See Table 10-6 for dimensions and weights.

Hardware Planning
Table 10-6. Dimensions and Weights

Product Height Width Depth Weight
cm (in.) cm (in.) cm (in.) kg (lb)
All Controllers 15.9 (6.3) 4.1 (1.6) 10.7 (4.2) 0.28 (0.62)
Controller Firewall 13.1 (5.2) 4.7 (1.9) 11.1 (4.4) 0.34 (0.75)
2-wide Horizontal Power/Controller 16.5 (6.5) 9.2 (3.5) 3.1 (1.2) 0.16 (0.35)
Carrier
8-wide Horizontal I/O Interface Carrier 16.5 (6.5) 34.3 (13.5) 3.1 (1.2) 0.50 (1.1)
4-Wide Legacy Vertical Power/Controller 18.0 (7.1) 18.3 (7.2) 2.8 (1.1) 0.45 (1.0)
Carrier
4-Wide VerticalPLUS Power/Controller 18.1 (7.1) 22.8 (9.0) 2.8 (1.1) 0.58 (1.3)
Carrier
4-Wide VerticalPLUS SISNet Repeater 18.1 (7.1) 22.8 (9.0) 2.8 (1.1) 0.58 (1.3)
Carrier
8-wide Legacy Vertical I/O Interface 55.9 (22.0) 18.3 (7.2) 2.8 (1.1) 1.36 (3.0)
Carrier
8-wide VerticalPLUS I/O Interface Carrier 51.0 (20.1) 22.8 (9.0) 2.8 (1.1) 1.6 (3.6)
H1 Carrier 17.8 (7.0) 9.1 (3.6) 2.5 (1.0) 0.28 (0.62)
I.S. Power and Localbus Isolator Carriers 16.5 (6.5) 9.1 (3.6) 3.1 (1.2) 0.26 (0.56)
PROVOXr I/O Interface Carrier 22.2 (8.7) 48.3 (19.0) 5.1 (2.0) 2.13 (4.7)
RS3t I/O Interface Carrier 31.1 (12.7) 48.3 (19.0) 8.9 (3.5) 3.04 (6.7)
I/O Interface Card 10.5 (4.1) See figures 10.7 (4.2) 0.18 (0.40)
H1 Fieldbus Card 13.2 (5.2) See figures 10.7 (4.2) 0.28 (0.62)
I/O Interface Termination Block N/A N/A N/A 0.06 (0.13)
PROVOX I/O Interface Card 15.9 (6.3) 4.2 (1.7) 10.7 (4.2) 0.28 (0.62)
RS3 I/O Interface Card 16.2 (6.4) 8.4 (3.3) 11.0 (4.3) 0.59 (1.3)
Extender Cable Connector 16.5 (6.5) 4.1 (1.6) 3.1 (1.2) 0.08 (0.18)
Remote Interface Unit (RIU) 15.9 (6.3) 4.1 (1.6) 10.7 (4.2) 0.28 (0.62)
VE5001 AC to DC System Power Supply 15.9 (6.3) See figures 10.7 (4.2) 0.35 (0.77)
VE5008 DC/DC Dual System Power 15.9 (6.3) See figures 10.7 (4.2) 0.33 (0.73)
Supply
Bulk AC to 12 VDC Power Supply (Panel 12.7 (5.0) 39.4 (15.5) 6.4 (2.5) 2.8 (6.2)
Mount)
Bulk AC to 24 VDC Power Supply (Panel 12.7 (5.0) 39.4 (15.5) 6.4 (2.5) 2.8 (6.2)
Mount)
Bulk AC to 12 VDC Power Supply (DIN 13.5 (5.3) 24.0 (9.5) 10.6 (4.2) 11.2 (24.6)
Rail Mount)
10-16 v10.3:March 2009

Hardware Planning
Table 10-6. Dimensions and Weights (Continued)

Product Height Width Depth Weight
cm (in.) cm (in.) cm (in.) kg (lb)
Bulk AC to 24 VDC Power Supply (DIN 13.5 (5.3) 24.0 (9.5) 10.6 (4.2) 11.2 (24.6)
Rail Mount)
Bulk 24 VDC to 12 VDC Power Supply 12.7 (5.0) 30.5 (12) 6.4 (2.5) 1.6 (3.5)
I.S. System Power Supply 15.9 (6.3) 8.4 (3.3) 10.9 (4.3) 0.33 (0.73)
Fieldbus Power Supply See Manufacturer’s Manual
Workstation See Product Specifications Sheet
Server See Product Specifications Sheet
UPS for Workstations and Servers See Product Specifications Sheet
Monitors See Product Specifications Sheet
Allied Telesyn AT-FS708 8-Port 3.6 (1.4) 24.9 (9.6) 11.6 (4.6) 0.9 (2.0)
10/100Base-TX Ethernet Switch
Allied Telesyn AT-FS709FC 8-Port 4.5 (1.8) 33.0 (13.0) 20.3 (8.0) 2.0 (4.4)
10/100Base-TX Ethernet Switch (with
one 100Base-FX port supporting up to 2
Km of fiber)
Cisco Catalyst 2960-8TC-L 8-Port 4.4 (1.73) 27 (10.6) 16.3 (6.4) 1.4 (3)
10/100Base-TX Fast Ethernet Switch
with one SFP Slot
Cisco Catalyst 2960-24TC-L 24-Port 4.4 (1.73) 44.5 (17.5) 23.6 (9.3) 3.6 (8)
with two SFP Slots
Cisco Catalyst 2960−48TC−L 48-Port 4.4 (1.73) 44.5 (17.5) 23.6 (9.3) 3.6 (8)
with two SFP Slots
Cisco Catalyst 2960-24 TT-L 24-Port 4.4 (1.73) 44.5 (17.5) 23.6 (9.3) 3.6 (8)
Cisco Catalyst 2960-48TT-L 48-Port 4.4 (1.73) 44.5 (17.5) 23.6 (9.3) 3.6 (8)
10/100Base-FX Fast Ethernet Switch
Cisco Catalyst 3750-24FS 24-Port 4.4 (1.7) 44.5 (17.5) 30.1 (11.8) 4.1 (9.0)
100Base-FX Fiber Optic Switch with two
1 Gigabit Converter Interface Ports
Cisco Catalyst 3750-24TS-S 24-Port 4.4 (1.7) 44.5 (17.5) 30.1 (11.8) 4.1 (9.0)
with two slots for Gigabit Transceivers
Cisco 3750G12S-S 12 Slot Gigabit 4.4 (1.7) 44.5 (17.5) 32.6 (12.8) 4.6 (10.1)
Switch

Hardware Planning
Carriers
The DeltaV system supports horizontal carriers, vertical carriers, Intrinsically safe
carriers, and the Fieldbus H1 Carrier. There are two types of vertical carriers:
Legacy and VerticalPLUS. VerticalPLUS careers can be used for both DeltaV basic
process control systems and DeltaV Safety Instrumented Systems (SIS). DeltaV SIS
is not supported on Legacy vertical carriers. The following carriers are currently
available:
H Horizontal Carriers
j 2-Wide Horizontal Power/Controller Carrier
j 4-Wide Horizontal I/O Interface Carrier
j 1-Wide Horizontal Carrier Extender (left and right versions)
H VerticalPLUS Carriers
j 4-Wide VerticalPLUS Power/Controller Carrier
j 4-Wide VerticalPLUS Power Carrier
j 4-Wide VerticalPLUS SISNet Repeater Carrier
j 4-Wide VerticalPLUS I/O Interface Carriers
j 4-Wide VerticalPLUS Carrier Extenders (left and right versions)
H Legacy Vertical Carriers

j 4-Wide Legacy Vertical Power/Controller Carrier
j 8-Wide Legacy Vertical Interface Carriers (left and right versions)
H Intrinsically Safe Carriers

j Intrinsically Safe Power Supply Carrier
j Intrinsically Safe 8-Wide Horizontal Carrier
j Intrinsically Safe LocalBus Isolator Carrier
H Fieldbus H1 Carrier
10-18 v10.3:March 2009

Hardware Planning
Horizontal Carrier Considerations

As shown in Figure 10-4, the depth and height do not vary for each controller
and I/O assembly. However, the width of the assembly varies depending on your
controller and I/O layout. As a beginning, consider:
H 2-wide power/controller carrier: 9.2 cm (3.6 inches) for every 2-wide carrier
H 8-wide horizontal I/O carrier: 34.3 cm (13.5 inches) for every 8-wide carrier
H Extender cable connector: 4.6 cm (1.8 inches); two connectors for each
extender cable
Width must be calculated
Height constant*
*Height and Depth are given in Table 10-6 by

Depth constant* adding carrier depth and controller or I/O card depth
Figure 10-4 Calculated Dimensions of Controller I/O Assembly
Figure 10-5 through Figure 10-10 illustrate how to calculate widths for several
possible arrangements of 2-wide carriers, 8-wide carriers, and the combination of
2- and 8-wide carriers used with an extender cable. The maximum length of
carriers connected together either side by side or with an extender cable is 6.5
meters (21.3 feet).

Hardware Planning
2-wide carrier
System power supply

Controller
DIN rail
9.2 cm (3.6 in.) for

each two-wide carrier
Figure 10-5 Width of 2-wide Carrier

8−wide carrier
I/O Subsystem (8 I/O modules)
34.3 cm (13.5 in.)

All 8−wide carriers
Figure 10-6 Width of 8-wide Carrier
Figure 10-6 shows the width for an 8-wide horizontal carrier. Regardless of the
number of 8-wide carriers you connect directly together (no extender cable used),
you need to add 34.3 cm (13.5 in.). for each carrier. Figure 10-7 shows the total
width when one 2-wide carrier and one 8-wide carrier are connected.
10-20 v10.3:March 2009

Hardware Planning
2−wide Carrier 8−wide Carrier
9.2 cm 34.3 cm
(3.6 in.) (13.5 in.)
43.5 cm
(17.1 in.)
Figure 10-7 One 2-wide Carrier and One 8-wide Carrier Connected
Figure 10-8 shows the total width when a two 2-wide carriers and one 8-wide
carrier are connected.
2-Wide Carriers 8−wide Carrier
18.4 cm 34.3 cm
(7.2 in.) (13.5 in.)
52.7 cm
(20.7 in.)
Figure 10-8 Two 2-wide Carriers and One 8-wide Carrier Connected
Figure 10-9 and Figure 10-10 illustrate the additional 4.6 cm (1.8 in.) width
required when an extender cable is used to connect horizontal carriers. Whether
the connectors are used in extended horizontal (same level) connections or in
stacked connections, 4.6 cm (1.8 in.) must be added.

Hardware Planning
Extender Cable Connector Extender Cable

1.2 m (3.9 ft)
4.6 cm (1.8 in.)
4.6 cm (1.8 in.)
Extender Cable connector
Figure 10-9 Extender Cable Connecting Two 8-wide Carriers On Same Level
4.6 cm (1.8 in.)
Extender Cable
Connector
Extender cable is 1.2 m (3.9 ft) from end

of connector to end of connector
Extender Cable
Connector
4.6 cm (1.8 in.)
Figure 10-10 Extender Cable Connecting Two 8-wide Carriers On Stacked Levels
10-22 v10.3:March 2009

Hardware Planning
As shown in Figure 10-11, horizontal I/O carriers can be plugged together

end-to-end, or they can be connected with a carrier extender cable. The total
length of the carriers plus cable is 6.5 meters (21.3 feet). Since the electrical
current in a horizontal carrier is limited to 8 A, power may be inserted at the
extender cable connector between carriers to maintain proper I/O card power
while keeping carrier current with ratings.
2-Wide Carrier 8−Wide Carrier
...
34.3 cm (13.5 in.) Extender Cable
2−wide 1.2 m (3.9 ft)
Carrier
9.2 cm Plugs Into Next Carrier
(3.6 in.)
Maximum Carrier and Cable Length is 6.5 m (21.3 ft)
Figure 10-11 Horizontal Carriers Connected Together

Hardware Planning
VerticalPLUS I/O Carrier Considerations

VerticalPLUS I/O carriers are available with either right-side or left-side field
terminals that facilitate mounting two columns" of carriers in a vertical enclosure
with field wiring routed between the columns. In each column, carriers can be
connected together end-to-end up to the vertical inner limits of the enclosure.
Figure 10-12 shows VerticalPLUS I/O Carrier dimensions and VerticalPLUS
Power/Controller Carrier dimensions.
To make electrical connections from carriers on the left side to carriers on the
right side, extender cards and extender cables are used. The top cables and the
bottom cables are exactly the same. Although two extender cables are shown,
they are not redundant. Some users may wish to have two cables, but they are
simply parallel cables since the connectors are wired in parallel on the printed
circuit board.
Extender cards are left-hand and right-hand. Order one left-hand card and one
right-hand card for each extension and one or two extender cables for each
extender cards pair, depending on whether you wish to connect one or two
cables between the card pairs. Left and right orientation of the cards is to the
cable connections, not to the carrier. Therefore, the left-hand card connects to the
right-hand carrier and the right-hand card connects to the left-hand carrier. The
total length of the carriers plus cable is 6.5 meters (21.3 feet). The electrical
current capacity in a vertical carrier is specified as 15 A.
If desired, DC power may be inserted at power terminals on the carriers to

provide adequate power for I/O cards, while limiting current on any one carrier
to specification. The figure shows a 4-wide Power Carrier which allows users to
install up to four DC/DC Dual system power supplies adjacent to the vertical
carriers. These supplies can be used to insert 12 VDC power on the carriers.
10-24 v10.3:March 2009

Hardware Planning
22.8 cm
(9.0 in.) Extender
Cables
C C 4.8 cm
18.1 cm P P (1.9 in.)
. O O
(7.1 in.) W W Pins
A
Pins
N N
B
Pins Pins
B
R R
T T Socket Socket
AC
BC
Right-Hand
A
1 Socket 32 1 Pi
ns 32 12 SPi
oc
32 Pi
ns 1 32 Socket 1 3 nk
set 31
2
Extender
4 5 4 Card
3 6 3
2 7 2 Left-Hand
1 8 1 Carrier
51.0 cm
(20.1 in.)
8 1 8
7 2 7
6 3 6
5 4 5
12
3 SP
oc
nks
i et 31
2 12
3 Pc
Soi
nk
set 31
2 113.2 cm 12
3 SPi
oc
nk
set 31
2
.
(44.6 in.)
4 5 4
3 6 3
2 7 2
1 8 1
177.5 cm
164.2 cm
(69.9 in.)
(64.6 in.)
8 1 8
7 2 7
6 3 6
5 4 5
12 SP
oi
c
nks
et 31
2 1 Pi
ns 32 12 SPi
oc
3 32 Socket 1 3 nk
set 31
2
Socket
AC
Socket Left(In)
4 5
3 6
2 7
1 8
P P P P 4-wide
17.7 cm . W W W W Power
(7.0 in.) R R R R Carrier
8 1
7 2
6 3
5 4 2.3 cm
(0.9 in.)
12 SP
oc
Right-Hand
3 nks
i et 31
2 12
3 SPi
nk
ocset 31
2
Carrier
AC
BC
Socket Socket
B
Pins Pins Left-Hand

B
Pins
B
Pins
A
Extender Card
Figure 10-12 Dimensions and Connected Extender Cables on VerticalPLUS I/O Carriers

Hardware Planning
Legacy Vertical I/O Carrier Considerations

Legacy Vertical I/O carriers are available with either right-side or left-side field
terminals that facilitate mounting two columns" of carriers in a vertical enclosure
with field wiring routed between the columns. In each column, carriers can be
connected together end-to-end up to the vertical inner limits of the enclosure. To
make electrical connections from carriers on the left side to carriers on the right
side, extender cables are used. Figure 10-13 shows Legacy Vertical I/O Carrier
dimensions and Legacy Vertical power/controller carrier dimensions.
Two types of extender cables are available. A Bottom Extender Cable allows
connecting bottom carriers and a Top Extender cable allows connecting top
carriers. Each cable contains unique plug connections, so the cables are not
interchangeable. The extender cable socket on a left-hand vertical carrier is next
to I/O card position eight. The extender cable socket on a right-hand vertical
carrier is next to I/O card position one. Figure 10-14 illustrates connections
between Legacy Vertical I/O Carriers.
The total length of the carriers plus cable is 6.5 meters (21.3 feet). The electrical
current capacity in a vertical carrier is specified as 15 A. If need be, DC power
may be inserted at power terminals on the carriers to provide adequate power for
I/O cards, while limiting current on any one carrier to specification. For further
details and illustrations, see the DeltaV Vertical Carriers section in the manual,
Installing Your DeltaV Digital Automation System.
10-26 v10.3:March 2009

Hardware Planning
18.3 cm
(7.2 in.)
Power Supplies
18.0 cm and Controllers
(7.1 in.)
Bussed Field
Power
Connector
55.9 cm 55.9 cm
(22.0 in.) (22.0 in.)
Bussed Field
Power
Connector
3.8 cm 1 1
3.8 cm
(1.5 in.) (1.5 in.)
Left-Hand Carrier Right-Hand Carrier
Note:
1 Minimum distance between carrier and panduit.
Figure 10-13 Dimensions for Legacy Vertical I/O Carriers

Hardware Planning
Power Supplies Top Extender

and Controllers Cable 2 m (6.6 ft.)
Carrier
Edge
Connect
Power
Terminal Left-Hand
for Carrier
Inserting
DC
Power Bottom
Extender
Cable
1 m (3.4 ft)
Left-Hand Right-Hand
Carrier Carrier
Figure 10-14 Connecting Extender Cables on Legacy Vertical I/O Carriers
10-28 v10.3:March 2009

System Capacities
‘Figure A-Table A
Appendix A System Capacities
Summary of Capacities and Requirements

The following list summarizes capacities and requirements for DeltaV, version 10.3.
H Up to 120 nodes per Control Network. The Control Network nodes can
consist of:
j Up to 100 simplex and redundant controllers (a redundant controller is

counted as one node, but uses two physical ports of a switch)
j Up to 65 workstations on a Control Network (non-remote), consisting of:
H One, and only one, ProfessionalPLUS station

H Up to 59 Application, Base, Maintenance, Operator and Professional
stations. Recommended limit of 20 Application stations and 10
Professional stations
H Up to 120 Remote I/O nodes per control network. These are in addition to
the controller node limit.
H Up to 120 Wireless Gateway nodes per control network. These are in addition
to the controller node limit.
H Up to 30,000 DSTs as AI, AO, DI, and DO distributed among controllers and
application workstations: up to 1500 DSTs for MX controller and up to 750
DSTs per MD or MD Plus controller.
See the Controller Loading Estimator on the DeltaV WebCD about the fit of
your application in each controller’s memory and CPU capacity.
H Up to 64 I/O cards per controller, as long as total DSTs does not exceed
controller capability: up to 1500 DSTs for MX controller and up to 750 DSTs
per MD or MD Plus controller
For example: 64 simplex cards X 8 I/O channels = 512 DSTs (controller DST
capacity is not exceeded); 32 redundant cards X 8 channels = 256 DSTs
System Planning Guide A-1

System Capacities
(controller DST capacity is not exceeded); 64 cards X 32 channels = 2048

DSTs (controller DST capacity is exceeded; this combination of cards and
channels is not possible).
H Unlimited SCADA tags as long as their processing doesn’t interfere with

acceptable system performance (factory-tested to 25,000 SCADA tags).
H Up to 10,000 FOUNDATION fieldbus devices.
Note ... For additional specifications and for details concerning the application of
specifications shown below, see Books Online for version 10.3.
A-2 v10.3:March 2009

System Capacities
System Capacities
Description v7.3 v7.4 v8.3 v8.4 v9.3 v10.3
Max. ProfessionalPLUS Stations 1 1 1 1 1 1
Max. Professional Stations 10* 10* 10* 10* 10* 10*
Max. Application Stations (including 10* 10* 10* 10* 10* 20*
RAS)
Max. Local workstations of any kind 60 60 60 60 60 65
Max. Remote Workstations (using RAS 42 (1)* 72 (2)* 72 (2)* 72 (2)* 72 (2)* 72 (2)*
servers)
Max. Application Workstations setup as 4 7 7 7 7 7
RAS servers
Max. Number of simultaneous Asset 4 4 4 4 4 4
Manager Server connections per
Application Workstation
Max. Number of simultaneous Asset 50 50 50 50 50 50
Manager Server connections (all
Application Workstations combined)
Max. Interzone Servers per DeltaV −−− −−− −−− −−− 1 1
system (Simplex or Redundant)
Max. DeltaV zones (including the current −−− −−− −−− −−− 10 10
system)
Max. Simplex and Redundant 100 100 100 100 100 100
Controllers per Control Network (each
redundant pair counts as a single node)
Max. Control Network nodes 120 (3) 120 (3) 120 (3) 120 (3) 120 (3) 120 (3)
Max. Mix of Zone 1 and Zone 2 Remote −−− −−− 60 60 60 60
I/O nodes
Max. DSTs per system 30,000 30,000 30,000 30,000 30,000 30,000
Max. FOUNDATION fieldbus devices 10,000 10,000 10,000 10,000 10,000 10,000
Unsolicited Scan Rate (minimum per 1 1 1 1 1 1
sec)
Control Network Timeout (ms) 200 200 200 200 200 200
Max. Clock skew between nodes (ms) 50 to 50 to 50 to 50 to 50 to 50 to
250 (4) 250 (4) 250 (4) 250 (4) 250 (4) 250 (4)
* Quantities shown in Italics are recommended limits.
(1) 10 on each of four Application Stations, and two on the ProfessionalPLUS Station.
(2) 10 on each of seven Application Stations, and two on the ProfessionalPLUS Station.
(3) Redundant nodes count as one node in the maximum node limit.
(4) If the workstation is participating in an NPT server, the range is 5μsec.

System Capacities
Batch Capacity
Max. Batch Executives per system 4 4 4 4 4 4
Max. Campaign Managers per system 4 4 4 4 4 4
Max. Batch Historians per system 4 4 4 4 4 4
System Configuration
Max. Plant areas 100 100 100 100 250 250
Max. Regular Named sets 1000 (1) 1000 (1) 1000 (1) 1000 (1) 1000 (1) 1000 (1)
Max. SIS Named sets −−− −−− 1000 (1) 1000 (1) 1000 (1) 1000 (1)
Max. Regular Alarm types 255 255 255 255 255 255
Max. SIS Alarm types −−− −−− 255 255 255 255
Max. User accounts per system 200 200 200 200 200 200
Max. Control Studios per workstation 4 4 4 4 4 4
Max. Recipe Studios per workstation 4 4 4 4 4 4
Max. Explorers per workstation 1 1 1 1 1 1
Max. Recommended concurrent 2 to 10 2 to 10 2 to 10 2 to 10 2 to 10 2 to 10
engineers (2) (2) (2) (2) (2) (2)
Max. Function blocks per module 250 250 250 250 250 250
Max. Concurrent database connections 60 60 60 60 60 60
Max. Nesting levels of modules 6 6 6 6 6 6
(1) Includes system enumeration sets. The number available to users is less.
(2) The quantity depends on server performance. Generally, the larger the server, the larger the quantity.
A-4 v10.3:March 2009

System Capacities
Capacity for All Workstations

Unsolicited Values reported per second 2,000 2,000 2,000 5,000 5,000 5,000
Alarms/Events Logged per second per 50 50 50 50 50 50
workstation (burst condition) (1)
Max. Records per Event Chronicle 500,000 500,000 500,000 500,000 −−− −−−
Max. Active History Data Sets (HDSs in −−− −−− −−− −−− 100 (2) 100 (2)
Mbytes) per Event Chronicle
Max. DeltaV Explorer applications open 1 1 1 1 1 1
Max. Control Studio applications open 4 4 4 4 4 4
Max. Recipe Studio Applications open 4 4 4 4 4 4
(1) Bursts of up to 100 events/sec can be handled for a few minutes (recommended limit of 10 minutes). However,
continuous logging at 50 events/sec can potentially reach millions of events, quickly exceeding an Event Chronicle’s size
limits. When size limits are reached, logged data can be corrupted. To determine an appropriate continuous throughput,
use the formula: Maximum Configured Size [(Number of days configured to be collected) + 1].
(2) 100 Mbytes is the recommended size. Generally, 100 Mbytes of disk space can hold between 250,000 and 500,000
event records depending on the content of each event record. 4 Gbytes is the maximum size.
ProfessionalPLUS Workstation Capacity

Max. Data Values per display (1) 600* 600* 600* 600* 600* 600*
Max. Applications open 10* 10* 10* 10* 10* 10*
Max. History values 250 250 250 250 250 250
Max. Faceplates open 8* 8* 8* 8* 8* 8*
Max. Detail displays open 1 1 1 1 1 1
Max. Ethernet ports 5 5 5 5 5 5
(1) As hundreds of links are added to the workstation, the callup rate can become slow. 300 data values per display is
recommended limit when using DeltaV Operate.
Note: See Table A-1 for function blocks allowed in a ProfessionalPLUS station.

System Capacities
Operator Workstation Capacity

Max. Applications open 9 9 9 9 9 30
Max. Cached displays (pre-loaded) 25 25 25 25 25 25
Max. Cached displays (most recently 99 99 99 99 99 99
used)
(1) As hundreds of links are added to the workstation, the callup rate can become slow.
Note: Quantities included in table are also applicable when Operator Stations are used for DeltaV Operate for PROVOXr
Consoles and DeltaV Operate for RS3t Systems
Application Workstation Capacity

Max. Synchronous writes/sec per 50 50 50 50 50 50
controller
Events generated/sec per workstation 50* 50* 50* 50* 50* 50*
controller
DSTs for Data Acquisition and 2000 2000 2000 2000 2000 2000
Calculation Control
Max. Modules in workstation 3,000* 3,000* 3,000* 3,000* 3,000* 3,000*
Max. OPC writes/sec (local) 2,000 2,000 2,000 2,000 2,000 2,000
Max. OPC data values received at 25,0001 30,0001 30,0001 30,0001 30,0001 30,0001
workstation
Max. OPC data values transmitted to 25,0002 30,0002 30,0002 30,0002 30,0002 30,0002
OPC DC client installed on workstation
Max. History data values (continuous 20,000 20,000 20,000 20,000 30,000 30,250
historian)
History sample rate/sec 2,500* 2,500* 2,500* 2,500* 2,500* 3000*
(1) The limit, as noted, is 30,000 values. It is factory tested for 30,000 values per second (scan rate of server or client).
Your value may be less, depending on server and client speed. Your actual value can be seen through the OPC
Subsystem of DeltaV Diagnostics.
(2) The limit, as noted, is 30,000 values. It is factory tested for 30,000 values per second. Your value may be less,
depending on speed of equipment receiving data. Your actual value can be seen through diagnostics.
Note: See Table A-1 for function blocks allowed in an Application station.
A-6 v10.3:March 2009

System Capacities
Professional, Maintenance, and Base Workstation Capacity

Max. Applications open 10* 10* 10* 10* 10* 10*
Max. Cached displays (pre-loaded) 30 30 30 30 30 30
Max. Cached displays (most recently 99 99 99 99 99 99
used)
(1) As hundreds of links are added, the callup rate can become slow. 300 is recommended limit when using DeltaV
Operate.
Note: See Table A-1 for function blocks allowed in a Professional, Maintenance, and Base station.

Application Stations
Function Description Applies
Block Toward DST
Count
ABS Absolute Value
ACT Action
ADD Add
AGA_SI Flow Metering in SI Engineering Units
AGA_US Flow Metering in US Engineering Units
AI Analog Input Yes
ALM Alarm Detection Yes
AND And
AO Analog Output Yes
ARTHM Arithmetic
BDE Bi-Directional Edge Trigger
BFI Boolean Fan In
BFO Boolean Fan Out
CALC Calc/Logic Yes
CMP Comparator
CND Condition
CTR Counter
DI Discrete Input Yes

System Capacities

Application Stations (Continued)
Block Toward DST
Count
DIAG Diagnostic
DIV Divide
DO Discrete Output Yes
DT Dead Time
DTE Date Time Event
FLTR Filter
INSPECT Inspect Data Block
INT Integrator
ISE Isentropic Expansion
ISEL Input Selector
LE Lab Entry
LIM Limit
LL Lead/Lag
MLTX Multiplexer
MLTY Multiply
MPC MPC
MPC_SIM MPC Process Simulator
MPC_PRO MPC Pro
NDE Negative Edge Trigger
NN NN (Neural Network)
NOT Not
OFFD Off-Delay Timer
OND On-Delay Timer
OR Or
PDE Positive Edge Trigger
PID* PID
PIN Pulse Input Yes
RAMP Ramp
RET Retentive Timer
RS RS Flip-Flop
RTLM Rate Limit
SCLR Scaler
SDR Steam Density Ratio
A-8 v10.3:March 2009

System Capacities

Application Stations (Continued)
Block Toward DST
Count
SGCR Signal Characterizer
SGGN Signal Generator
SR SR Flip-Flop
SST Saturated Steam Properties — Given Temperature
STM Steam Properties
SUB Subtract
TP Timed Pulse
TSS Saturated Temperature
WTH Water Enthalpy
WTS Water Entropy
XFR Transfer
Note*: PID blocks assigned to workstations only support the IMAN mode when the
system is based on a User System Identifier.
Controller and I/O Subsystem Capacity

Max. I/O cards per controller 64 64 64 64 64 64
Max. DSTs per M5 Plus controller 500 500 −−− −−− −−− −−−
Max. DSTs per MD controller 750 750 750 750 750 750
Max. DSTs per MD Plus controller −−− −−− 750 750 750 750
Max. DSTs per MX controller −−− −−− −−− −−− −−− 1500
Max. DSTs per DeltaV Interface to 750 750 750 750 750 750
PROVOX I/O
Max. DSTs per DeltaV Interface to RS3 750 750 750 750 750 750
I/O
Max. Modules per controller 750 (1)* 750 (1)* 750 (1)* 750 (1)* 750 (1)* 750 (1)*
User memory (mb) — M5 Plus controller 14 14 −−− −−− −−− −−−
User memory (mb) — MD controller 14 14 14 14 14 14
User memory (mb) — MD Plus controller −−− −−− 48 48 48 48
Max. Values per serial data set 100(2) 100(2) 100(2) 100(2) 100(2) 100(2)
Max. Serial data sets per serial card 32 32 32 32 32 32
Max. Devices per serial port 16 16 16 16 16 16
Fastest module scan rate (ms) 100 100 100 100 100 100

System Capacities

Max. Cable and carrier length (ft) 21 21 21 21 21 21
controller to through last carrier in chain
Max. Carriers per controller 8 8 8 8 8 8
Max. Diagnostic sessions open per 2 2 2 2 2 2
controller
Max. Control Studio on-line sessions per 4 4 4 4 4 4
controller
Events generated per second per 50 50 50 50 50 50
controller — MD and MD Plus controller
Events generated per second per −−− −−− −−− −−− −−− 100
controller — MX controller
Max. Synchronous writes/sec 50 50 50 50 50 50
Unsolicited values per second sent — 500* 500* 1000 2000 2000 2000
MD and MD Plus controller
Unsolicited values per second sent — −−− −−− −−− −−− −−− 4000
MX controller
Unsolicited values per second received 500* 500* 1000 1000 1000 1000
— MD and MD Plus controller
Unsolicited values per second received −−− −−− −−− −−− −−− 2000
— MX controller
Max. Controller connections to other 32/64 32/64 100 100 100 100
nodes (3) (3)
Max. Local controller connections to −−− −−− −−− −−− 100 100
remote zone controller (external ref.) —
MD and MD Plus controller
Max. Local controller connections to −−− −−− −−− −−− −−− 200
remote zone controller (external ref.) —
MX controller
Max. Local controller connections to −−− −−− −−− −−− 100 100
remote zone controller (dynamic ref.)
Minimum macro cycle (msec) 250 250 250 250 250 250
(1) Actual value may be more or less, depending on control strategy.
(2) For floating point, maximum is 50 values per serial data set.
(3) Depends on the controller type.
A-10 v10.3:March 2009

System Capacities
I/O Bus System Capacity

Max. H1 cards per controller 40 40 64 64 64 64
Max. Device function blocks per H1 card 64 64 64 64 64 64
Max. H1 function blocks per H1 card −−− −−− −−− −−− 32 32
Max. Function blocks per H1 card −−− −−− −−− −−− 96 96
(Device plus H1)
Max. Ports per H1 card 2 2 2 2 2 2
Max. Publisher VCR per H1 port 20 20 35 35 35 35
Max. Subscriber VCR per H1 port 20 20 50 50 50 50
Max. Publisher and Subscriber 25 25 50 50 50 50
combined per H1 port
Max. FOUNDATION fieldbus devices per 16 16 16 16 16 16
segment
Min. Macrocycles (msec) 150 250 250 150 150 150
Max. Devices as Backup LAS 1 1 1 1 1 1
Max. Profibus segments per I/O card 1 1 1 1 1 1
Max. Slaves per Profibus segment 64 64 64 64 64 64
Max. AS-i Bus segments per I/O card 2 2 2 2 2 2
Max. Slaves per AS-i Bus segment 31 31 31 31 31 31
Max. DeviceNet segments per I/O card 1 1 1 1 1 1
Max. Slaves per DeviceNet Bus 61 61 61 61 61 61
segment
Zone 1 and Zone 2 Remote I/O Capacity

For capacity limits, see the Remote I/O subsection in Chapter 4.
Smart Wireless Gateway Capacity

Max. Number of controllers to which a −−− −−− −−− −−− 1 1
Smart Gateway node can be assigned
Max. Number of Gateway nodes −−− −−− −−− −−− 16 16
assigned to a controller
Max. Number of I/O devices connected −−− −−− −−− −−− 100 100
to the Gateway
Note: Other capacity specifications are the same as wired HART devices.

System Capacities
SIS System Capacity

Max. Function blocks per SIS module −−− −−− 250 (1) 250 (1) 250 (1) 250 (1)
(including blocks in composite)
Max. function blocks in the top level of a −−− −−− 127 (1) 127 (1) 127 (1) 127 (1)
SIS module
Max. function blocks per composite −−− −−− 127 (1) 127 (1) 127 (1) 127 (1)
block
Max. Levels of composite nesting in an −−− −−− 1 1 1 1
SIS module
Max. SIS modules in a logic solver −−− −−− 4 4 4 4
Max. Secure parameters per Logic −−− −−− 8 8 8 8
Solver
Max. Logic solvers per controller −−− −−− 32 32 32 32
(Simplex)
Max. Logic solvers that can publish data −−− −−− 8 8 8 8
globally on one controller
Max. Logic solvers per system that can −−− −−− 32 32 32 32
publish globally
Max. Non-secure parameter references −−− −−− 24 24 24 24
per logic solver
Max. Temporary variables defined using −−− −−− 32 32 32 32
VAR...END_VAR per expression
Max. Simulated logic solver cards −−− −−− 8 8 8 32
assigned to ProfessionalPLUS
workstation with Windows Server 2003,
Windows Server 2008, Windows XP
Professional, Windows Vista
Max. Simulated logic solver cards −−− −−− 4 4 4 4
assigned to ProfessionalPLUS
workstation with Windows XP
Professional
Max. SISNet repeater pairs in a DeltaV −−− −−− 32 32 32 32
system
Max. SISNet repeater rings in a DeltaV −−− −−− 1 1 1 1
system
Max. Secure parameters published −−− −−− 256 256 256 256
globally per DeltaV system
Max. Logic solvers −−− −−− 1024 1024 1024 1024
(1) The actual value may be less, depending on a number of factors, including: the complexity of SIS module configuration
and the number and type of SIS function blocks used.
A-12 v10.3:March 2009

Product Specifications
Figure B-Table B
Appendix B Product Specifications
Complete product specifications are listed in product data sheets. The specifications
listed below are taken from the product data sheets and provided for your quick
reference.
European Standards
All DeltaV products meet appropriate European standards for Electromagnetic
Compatibility and carry the CE mark.
CSA Certification
All DeltaV products meet industry-appropriate CSA requirements and carry the CSA
mark.
Environmental Specifications
Table B-1 and Table B-2 list environmental specifications for DeltaV products.
Table B-1. DeltaV System Temperature and Humidity Specifications

Product Operating Storage Temperature Relative Humidity
Temperature
Workstations 10°C to 35°C -20°C to 60°C 20% to 80%,
(50°F to 95°F) (-4°F to 140°F) non-condensing
maximum 10°C (18°F)
change per hour
Unmanaged Switches 0°C to 40°C -25°C to 70°C 5% to 95%,
Allied Telesyn AT-FS708
8-Port 10/100Base-TX
Ethernet Switch
Allied Telesyn AT-FS709FC
Ethernet Switch with one
100Base-FX port supporting
up to 2 km of fiber
System Planning Guide B-1

Table B-1. DeltaV System Temperature and Humidity Specifications (Continued)

Temperature
Managed Switches 0°C to 45°C -25°C to 70°C 10% to 85%,

Cisco Catalyst 2960-8TC-L
8-Port 10/100Base-TX Fast
Ethernet Switch with one
SFP slot
Fast Ethernet Switch with
two SFP slots
two SFP slots
Cisco Catalyst 2960-24TT-L
two 10/100/1000 ports
Cisco Catalyst 2960-48TT-L
two 10/100/1000 ports
Cisco 3750-24FS 24-Port
100Base-FX Fiber Optic
Switch with two 1-Gigabit
Interface Converter Ethernet
Ports
Cisco 3750-24-TS-S 24-Port
10/100Base-FX Fast
Ethernet Switch with two
slots for Gigabit
Transceivers
Cisco 3750G12S-S 12-Slot
Gigabit Switch
MD Controller 0°C to 60°C -40°C to 85°C 5% to 95%,
Pre-Series 2 I/O
DeltaV interface for
PROVOX I/O
DeltaV interface for RS3 I/O
B-2 v10.3:March 2009

Table B-1. DeltaV System Temperature and Humidity Specifications (Continued)

Temperature
MD Plus Controller -40°C to 70°C -40°C to 85°C 5% to 95%,

(-40°F to 158°F) (-40°F to 185°F) non-condensing
SIS Devices
MX Controller -40°C to 60°C -40°C to 85°C 5% to 95%,
Single-port Fiber Switch -40°C to 70°C -40°C to 85°C 5% to 95%,
Four-port Fiber Switch
Remote Interface Unit (RIU)
Pre-series 2 Profibus Card 0 to 55°C -40°C to 85°C 5% to 95%,
Pre-series 2 DeviceNet
Card
Series 2 I/O, except Series -25°C to 70°C -40°C to 85°C 5% to 95%,
2 AS-Interface (-13°F to 158°F) (-40°F to 185°F) non-condensing
Series 2 AS-Interface -40°C to 70°C -40°C to 85°C 5% to 95%,
AC/DC System Power 0°C to 60°C -40°C to 70°C 5% to 95%,
Supply (32°F to 140°F) (-40°F to 158°F) non-condensing
DC/DC Dual System Power -40°C to 70°C -40°C to 70°C 5% to 95%,
Supply (-40°F to 158°F) (-40°F to 158°F) non-condensing
DIN rail-mounted Bulk -40°C to 70°C -40°C to 85°C 5% to 95%,
Power Supply (-40°F to 158°F) (-40°F to 185°F) non-condensing
Panel-mounted Bulk Power 0 to 60°C -40°C to 85°C 5% to 95%,
Supply (32°F to 140°F) (-40°F to 185°F) non-condensing
at 300 W and altitude
< 914 m (3000 ft)
DeltaV Controller Firewall 0 to 55°C -40°C to 80°C 10% to 95%
(32°F to 131°F) (-40°F to 176°F)
Fiber Optic Media Converter 0 to 60°C -40°C to 70°C 5% to 95%
(32°F to 140°F) (-40°F to 158°F)
Fieldbus H1 Carrier -40°C to 70°C -40°C to 85°C 5% to 95%,
System Planning Guide B-3

Table B-2. DeltaV System Contaminants, Vibration, and Shock Specifications

Product Airborne Contaminants Vibration Shock
Workstations See Manufacturer’s See Manufacturer’s See Manufacturer’s
Manual for Specifications Manual for Specifications Manual for Specifications
8-Port Hub See Manufacturer’s See Manufacturer’s See Manufacturer’s
(3-COM) Manual for Specifications Manual for Specifications Manual for Specifications
All Allied See Manufacturer’s See Manufacturer’s See Manufacturer’s
Telesyn and Manual for Specifications Manual for Specifications Manual for Specifications
Cisco switches
All Controllers ISA-S71.04-1985 1 mm peak-to-peak from 10 g 1/2-sine wave for 11
Airborne Contaminants 5 Hz to 16 Hz, 0.5 g from ms
Pre-Series 2 I/O Class G3 16Hz to 150 Hz
Series 2 I/O
SIS Devices
DeltaV Interface
for PROVOX I/O
DeltaV Interface
for RS3 I/O
Fieldbus H1
Carrier
Remote
Interface Unit
(RIU)
Single-port Fiber
Optic Switch
System Power
Supplies
DeltaV See Manufacturer’s See Manufacturer’s See Manufacturer’s
Controller Manual for Specifications Manual for Specifications Manual for Specifications
Firewall
Bulk Power ISA-S71.04-1985 MIL-STD-810D Method MIL-STD-810D Method
Supplies Airborne Contaminants 514.3, Category 1, 516.3, Procedure III
Class G2 Procedure I
B-4 v10.3:March 2009

Definition of Terms
Figure C-Table C
Appendix C Definition of Terms
Some terms with special meaning in DeltaV systems are defined below.
Data Values
Data values are all DST and SCADA tags that communicate in or out of a DeltaV
system through the DeltaV OPC Server. The data value count is used strictly for sizing
the DeltaV OPC Server. Each data value is first counted as a DST or SCADA tag for
DeltaV internal system sizing.
Examples of data values are:
H A tank level communicated via the OPC Server to an external historian

package
H An operator setpoint that is communicated via the OPC Server to an

OPC-connected programmable logic controller (PLC)
H An accumulated flow rate that is read from a DeltaV system into an Excel
spreadsheet, using the Excel OPC add-in
H A PLC register coming into a DeltaV system through the DeltaV OPC Server
DeltaV Node
A node is a workstation, a simplex controller, or a redundant controller that is
attached to the DeltaV Control Network.
Device Signal Tags (DSTs)

A Device Signal Tag (DST) is a measured variable input or a control output used in
DeltaV control strategies. Some DST examples are:
H a tank level reading
H a pressure reading
System Planning Guide C-1

Definition of Terms
H a register brought in via OPC or serial interface
H a coil brought in via OPC or serial interface
The inputs and outputs are relative to DeltaV controllers and Application Stations, and
they can be analog or discrete. The signals connect to a controller through its I/O
subsystem and to an Application Station through OPC.
DSTs in Controllers
DSTs in DeltaV controllers result from the manner in which its software is configured.
As shown in Figure C-1, function blocks are grouped into modules, and I/O
referenced by the function blocks constitutes a DST.
Controller
Module 1 Module 2
(3 DSTs) (2 DSTs)
Function Function
Block Block
Function Function
Block Block
Input A Input B Input C Output D
I/O Subsystem (1)
Classic I/O Serial I/O AS-i Bus DeviceNet Profibus DP SIS I/O
Note (1): Each O/O signal referenced by a function block counts as one DST. The DST
is an AO DST, AI DST, DO DST, or DI DST depending on the type of I/O.
Figure C-1 Relationship Between I/O and Controllers to Count DSTs
C-2 v10.3:March 2009

Definition of Terms
The number of DSTs per module for licensing is counted as follows:
H Each output from a function block to the I/O subsystem counts as one DO if
it is a discrete signal or one AO DST if it is an analog signal.
H An input referenced by one or more function blocks in a module counts as

one DI DST if it is a discrete signal or one AI DST if it is an analog signal.
H An input referenced by function blocks in multiple modules counts as a DI

DST or an AI DST in each module.
H Any input that is referenced in a graphic or a history collection and is NOT

referenced in a function block is NOT counted as a DST; it is counted as a
SCADA value.
The total number of DSTs in a controller is equal to the total number of DSTs in all of
its modules. In Figure C-1, the controller has two modules and five DSTs: three input
DSTs (either discrete or analog, depending on signal type) in Module 1 and one input
and one output DST (either discrete or analog, depending on signal type) in Module
2, adding to a total of five DSTs.
In Figure C-1, the DSTs were counted as follows:
H Input A is referenced by one function block and is therefore counted as one

input DST (either discrete or analog, depending on signal type).
H Input B is referenced by two function blocks, but the function blocks are in
the same module so the input is counted as one DST (either discrete or
analog, depending on signal type).
H Input C is referenced by function blocks in two modules so it is counted as

two DSTs.
H Output D is counted as one output DST (either discrete or analog, depending

on signal type).

Definition of Terms
DSTs in Fieldbus
In contrast to other I/O types, for fieldbus I/O, s DST is added to the count when
certain function blocks (as listed below) are added to a controller module. The type
of DST depends on the function block.
Function blocks which add one to the DST count are: FFAI, FFAI_RMT, FFAO,
FFAO_RMT, FFDI, and FFDO.
Function blocks which add eight to the DST count are: FFMAI, FFMAO, FFMAI_RMT,
FFMDI, FFMDI_STD, FFMDO, and FFMDO_STD.
For example, two FFAI blocks contained in the same module and referencing the
same transmitter signal count as two AI DSTs. Similarly, two FFMDI blocks contained
in the same module and referencing the same device count as 16 DI DSTs.
DSTs in Serial I/O

The serial card in the I/O subsystem supports datasets. A dataset can contain up to
100 values of either analog in, analog out, discrete in, or discrete out signals. A value
can be a discrete value, setpoint value, register value, and so on. Datasets which
contain Boolean or discrete values are discrete datasets. Datasets containing anything
else are analog datasets. Each port on a serial card supports up to 16 datasets.
Therefore, a serial card supports up to 3200 values.
Each dataset counts as one DST as long as a single module references all values in the
dataset. If multiple modules reference values in a dataset, the DST count for the
dataset is equal to the number of modules referencing the dataset. Values referenced
only in graphics or a history collection count as SCADA values, not DSTs.
DSTs in Application Stations

Application Stations use certain built-in function blocks which provide the interface to
OPC. The primary difference between the stations and a DeltaV controller is that the
stations do not contain function blocks specifically for control; i.e., PID, etc.
Another difference is the manner in which DSTs are defined and counted. As
described above, controller DSTs are created when function blocks reference I/O
from the I/O subsystem. In Application Stations, I/O is via OPC.
All OPC read and write values are counted as SCADA values unless they are
referenced by one of the following workstation function blocks, in which case, OPC
values are counted as DSTs:
C-4 v10.3:March 2009

Definition of Terms
H Al Analog Input block: Counted as one AI DST
H AO Analog Output block: Counted as one AO DST
H DI Discrete Input block: Counted as one DI DST
H DO Discrete Output block: Counted as one DO DST
H ALM Alarm Detection block: Counted as one AI DST
H CALC Calculation block: Counted as one AI DST
H FFMDI Multiple Discrete Input block: Counted as eight DI DSTs
H FFMDO Multiple Discrete Outputs block: Counted as eight DO DSTs
H PIN Pulse Input block: Counted as one DI DST
Applying DSTs
DSTs are one of the major measures that impacts controller loading and workstation
performance. Knowing the DST count facilitates the calculation of the DeltaV nodes
needed in the system, as well as a number of other systems dimensions. The
following guidelines will help you understand the impact of DSTs on your system
configuration:
H DST variables may or may not originate from the same device. The count is
independent of the origin of the signal.
H If the signal does not need to be conditioned in any form by the DeltaV
system (i.e. the signal is displayed directly on the Operator Interface as in a
SCADA system with no alarming, scaling or control function), the signal is not
considered a DST.
H A discrete signal (such as a proximity sensor) that is used only for display is
not considered a DST and is termed a SCADA tag. SCADA tags are reviewed
in the section below.
H If a FOUNDATION fieldbus device such as a valve is connected, the likely

DST count is 1 for the valve output signal and 1 for the percent open valve
position signal.

Definition of Terms
H For FOUNDATION fieldbus, the DST count is equal to the number of

FOUNDATION fieldbus I/O function blocks. A rule of thumb is that the DST
count for an average device is 1 or 2.
H For Classic I/O (i.e., neither HART nor bussed I/O), the DST count is equal to
the channel count, assuming that the inputs/outputs are all used for control
purposes.
Device Tags
Device tags are tags that are assigned to FOUNDATION fieldbus devices. They are
tags associated with the physical equipment. There is a one-to-one mapping between
device tags and physical devices in the field.
SCADA Tags
Supervisory Control and Data Acquisition (SCADA) tags are values that are not
conditioned in any way (the signal is not scaled), not used in DeltaV control
strategies, or not alarmed. SCADA tags can be easily displayed to an operator, saved
in historian, and displayed in a trend. The following guidelines help define SCADA
tag usage:
H SCADA tags may originate from Classic I/O, HART I/O, Serial Interfaces, OPC
Interfaces or from FOUNDATION fieldbus I/O.
H If the SCADA tag is used in a DeltaV control strategy, then the SCADA tag
becomes a DST.
H A discrete sensor brought into a DeltaV system via a Classic DI card and
displayed on the Operator Interface is a SCADA tag.
H Values brought in via the serial interface card that are displayed on the
Operator Interface constitute SCADA tags.
C-6 v10.3:March 2009

Definition of Terms
H Values brought in via OPC that display on the Operator Interface are
considered SCADA tags.
H The discrete output set by a push-button on the Operator Interface is a

SCADA tag.
H These values have less of an impact on system resources upper limits on

these tags are much higher in DeltaV systems than those for DSTs.
H SCADA tags may be displayed to an operator included in a trend, written to

by OPC, Operator Interfaces, displayed in the Operator Interface and tracked
in the DeltaV Historian.
H The following situations will cause a SCADA tag to transition into a DST:
j Referencing a SCADA tag from within a control strategy
j Scaling the value using an I/O block
j Referencing a SCADA tag as part of an alarm condition.
j External Reference to the SCADA Tag
Note ... A DeltaV system tracks SCADA tags and DSTs separately. The system
maintains a count of SCADA tags and a separate count of DSTs for each
node. If a SCADA tag transitions into a DST, then the count of SCADA tags
will be decreased and the count of DSTs will be increased.
Since DSTs consume system resources more readily than SCADA tags, the DeltaV
system has certain fences in place to prevent system overload conditions. These
fences and other system capacities are tabulated in the Controller and I/O capacity
table in Appendix A.

Definition of Terms
C-8 v10.3:March 2009

Index
A Base station
sizing, 8-16
actuator/sensor interface (AS−i), 4-10 software suite, 8-16
advanced batch license, 8-2 typical use, 8-16
advanced unit management license, 3-5 basic batch license, 8-2
alarm analysis model number, 8-5 batch, capacity by DeltaV version, A-4
AMP connectors and other accessories, 10-1 batch license distribution, 8-2
AMS inside, 8-6 batch license on application stations, 8-2
AMS server, 5-3 batch licensing, 8-2
analog I/O, 4-8 batch operator interface, 8-2
books online, xiv
anti−virus program, 8-7 , 9-5
bulk power supplies, 7-4
application station
calculating current for field devices, 7-5
capability by DeltaV version, A-6
bundled applications, 8-2
sizing, 8-18
software suite, 8-18
typical use, 8-18 C
applications available for RAS, 8-3
cabinets for protection, 10-7
AS−i bus
cable, no−hub, 2-5
extended fieldbus cable distances, 4-12 cabling accessories, 10-1
extender, 4-10 cached accounts, 9-4
network, 4-10 calculating current for field devices, 7-5
repeater, 4-10 calculating events logged, A-5
standard cables, 4-12 carrier width calculation, 10-19
AS−i Bus segments, determining quantity, when local bus cable used, 10-21
4-10 carriers
AS−i card, 4-12 eight−wide, 4-21
AS−Interface web site, 4-12 H1, 4-21
Legacy Vertical I/O carrier, 10-26
LegacyPLUS I/O carrier, 10-24
B mounting for optimal airflow, 10-7
backup linkmaster device, 4-15 PROVOX I/O interface, 4-22
Base station, capability by DeltaV version, RS3 I/O interface, 4-22
A-7 two−wide, 3-1
System Planning Guide Index-1

CAT 5 cable, 2-7 licensing, 3-3
centralized user accounts, benefits, 9-4 MD, MD Plus, 3-2
CISCO switches, 2-1 power requirements, 10-4
class−based units, 3-5 redundant, 3-1
classes, hardware, 9-1 selecting type, 3-2
classic I/O, 4-8 simplex, 3-1
controllers used in PROVOX I/O interface,
closure caps, fieldbus, 4-16
licensing, 3-4
communication errors
controllers used in RS3 I/O interface,
AS−i bus, 4-12 licensing, 3-4
DeviceNeT, 4-14 counting network nodes, 2-4 , 2-6
competitive I/O system, 4-22 CPU, zone 1, 4-3
components CSA certification, B-1
maximum set, 1-3 current, for DeltaV products, 10-3
minimum set, 1-1 customer−supplied enclosure, 4-22
computer virus protection, 8-7 cyber security, 9-5
configuration, system capacity by DeltaV
version, A-4
D
continuous history, which workstation, 8-14
control network, wireless segment, 5-1 data set, calculating, 4-8
control network, 2-1 data values, how they are used, 8-18
inter−zone, 8-24 definitions
data values, C-1
nodes, 2-4
DeltaV node, C-1
redundant network with redundant
controllers, 2-9 device tag, C-6
redundant network with simplex DST, C-1
controllers, 2-8 SCADA tag, C-6
simplex network with redundant DeltaV analyze, 8-5
controllers, 2-8 DeltaV Connect model numbers, 8-4
simplex network with simplex controllers, DeltaV fiber switches, 4-7
2-7
DeltaV insight, 8-6
controller loading calculations, xiii , 3-2 DeltaV inspect, 8-6
controller loading estimator, A-1 DeltaV node, definition, C-1
controllers DeltaV Operate for PROVOX Consoles, A-6
capacity by DeltaV version, A-9 DeltaV Operate for RS3 Systems, A-6
communication speeds, 2-3 DeltaV remote client, 8-3
determining quantity, 3-3 DeltaV tune, 8-6
Index-2 v10.3:March 2009

DeltaV user manager, 9-4 ethernet cards
DeltaV version that this manual covers, xi moving between workstations, 8-23
DeltaV zones (not remote I/O zones), 8-24 quantity supported, 8-23
device audit trail, 8-6 types in workstations, 8-23
device tag, definition, C-6 ethernet network, 2-1
DeviceNeT, card, 4-14 ethernet web site, 2-1
DeviceNet European standards, B-1
determining quantity, 4-13 events logged, calculating, A-5
segments, 4-13 extended cable distances
website, 4-13 AS−i bus, 4-12
dimensions, system capacity by DeltaV fieldbus, 4-15
version, A-3 PROFIBUS, 4-18
discrete I/O, 4-8 extender cables
specifications for multi−function card, 4-9 bottom and top, 10-26
domain security, 9-4 horizontal carriers, 10-19
DST Legacy Vertical I/O carriers, 10-26
counting in controllers, C-2 VerticalPLUS I/O carriers, 10-24
counting in workstations, C-4
definition, C-1 F
how to count, C-1
dual carrier extender cables, 6-4 factors affecting power dissipation in cabinets,
10-11
fiber switches for Zone 1, 2-1 , 4-7
E fiber−optic cable, 6-2
fiber−optic ring, 6-2
eight−wide carrier, 4-21 fieldbus
minimum number, 4-21 device alerts, 3-2
electric current draw, DeltaV products, 10-3 closure caps, 4-16
EN50170, PROFIBUS specification, 4-18 extended cable distances, 4-15
EN50295E, AS−i bus specification, 4-12 gland cable adapter, 4-16
enclosure, flame−proof, 4-3 power supply, 4-15
enclosures standard type A cable, 4-16
determining requirements, 10-7 terminator, 4-16
how to mount system components, 10-7 fieldbus device database, 8-6
selection procedure, 10-14 fieldbus device manager, 8-6
enclosures, increased−safety, 4-3 , 4-22 fieldbus I/O segments, 4-15
environmental specifications, B-1 flame−proof enclosure, 4-3

FlexConnect, 4-22 integrating non−DeltaV devices, 2-4
four−monitor model number, 8-1 inter−zone control network, 8-24
function blocks inter−zone server, 8-24
in controllers, C-2 interface to OEM consoles, 8-4
in workstations, C-4 intrinsically safe installation, I/O subsystem,
4-21
intrinsically safe power supplies, 7-8
G
gateway OPC server, 5-1
gateway to other networks, 8-23 K
gland cable adapter, fieldbus, 4-16
global messages, 6-2 KBA NA−0500−0059 for connecting
non−DeltaV devices, 2-4
H
L
H1 Carrier, 4-21
H1 interface, determining quantity, 4-15 License types, 8-1
hardware classes, 9-1 licenses, assigning to ProfessionalPLUS
HART interfaces, 4-8 station, 3-3
HART output for partial stroke testing, 6-2 licensing
history data, retrievable, 8-4 batch, 8-2
horizontal carriers, electrical capacity, 10-22 batch control, 3-5
controllers, 3-3
I controllers used in PROVOX I/O interface,
3-4
I/O bus systems, capacity by DeltaV version, controllers used in RS3 I/O interface, 3-4
A-11
DeltaV remote client, 8-3
I/O capacities, by DeltaV version, A-9
node−based, 8-1
I/O channel capability, SLS, 6-2
SCADA tags, 3-6
I/O nodes, remote, 4-3
I/O subsystem, 4-1 serial port, 3-4
intrinsically safe installation, 4-21 system−wide, 3-3
power requirements, 10-4 Localbus isolator, intrinsically safe system,
4-20
increased−safety enclosures, 4-3
integrated system request (ISR), obtaining logging events calculations, A-5
OEM items, 10-1 login accounts, 9-4

M O
Maintenance station, capability by DeltaV OEM items, 10-1
version, A-7 OPC DA server, 5-3
maintenance station OPC interface, C-4
sizing, 8-20 OPC mirror, 5-1
software suite, 8-20 OPC mirror application, 8-18
typical use, 8-20 operating and viewing continuous history,
master/slave system, 4-10 8-14
maximum length of connected horizontal operator and diagnostics interface, 8-10 ,
carriers, 10-19 8-12
operator station
maximum set of components, 1-3
capability by DeltaV version, A-6
migrate to DeltaV workstations, 8-4
sizing, 8-14
minimum set of components, 1-1
typical added applications, 8-14
Modbus serial protocol, 5-2
operator station software suite, 8-14
Modbus TCP/IP protocol, 5-2
optimal airflow around carriers, 10-7
mounting system components in enclosures,
10-7 other manuals, xiv
moving ethernet cards between workstations,
8-23 P
multifunction interface, 4-9
Mynah virtual I/O module, 5-1 partial stroke testing, 6-2
peer domain controller, 9-4
peer−to−peer bus, 6-2
N physical dimensions
calculating width on carriers, 10-19
NEMA 4X, 10-7
DeltaV products, 10-16
network. See control network
port, redundant, 2-4
network nodes, counting, 2-4
power and grounding, 10-2
network redundancy, 2-8 power dissipation, DeltaV products, 10-11
network time protocol server, 4-9 power dissipation considerations, 10-11
network topology, 2-4 power interruption, affects, 7-8
no−hub cable, 2-5 power requirements
node count limit on workstations, 9-1 controllers, 10-4
node types, 2-4 I/O subsystem, 10-4
node−based licensing, 8-1 power source, allowable interruptions, 7-8
nodes in control networks, counting, 2-4 power supplies
non−DeltaV devices, integrating, 2-4 12/24 VDC input, 7-3 , 7-4

120/240 VAC input, 7-1 , 7-4 terminator, 4-18
backup, 7-6 , 7-8 website, 4-18
bulk, 7-4 PROFIBUS segments, determining quantity,
4-18
calculating current for field devices, 7-5
PROVOX I/O interface, controller licensing,
determining quantity, 7-1 , 7-3 3-4
fieldbus, 4-15 PROVOX I/O interface carrier, 4-22
intrinsically safe, 7-8 pulse I/O, 4-9
reasons for not using a single source, 7-6
redundancy considerations, 7-6 , 7-8
special power bus link, 7-2 , 7-4 Q
system, 7-1 quad−monitor model number. See
uninterruptible, determining quantity, 7-8 four−monitor model number
power supply, zone 1, 4-3
preparing the site, 10-2
primary configuration and engineering
R
interface, 8-10 , 8-12
RAS. See remote access services
primary power calculation, 10-3 RAS available applications, 8-3
primary power source interruptions, 7-8 redundancy considerations for power
printers supplies, 7-6 , 7-8
connecting to LANs and workstations, 2-7 redundant communications port, 2-8
tested types, 2-7 redundant controllers, 3-1
process history view suite, running on an redundant I/O, 4-1
application station, 8-2 redundant port, 2-4
product data sheets, xiii related manuals, xiv
professional batch license, 8-2 remote access services, 8-3
Professional station, capability by DeltaV remote I/O nodes, 4-3
version, A-7 remote I/O zone 1 card types, 4-3
Professional station software suite, 8-12 remote network, definition, 2-6
ProfessionalPLUS station software suite, 8-10 remote network uplink, high−speed dialup,
ProfessionalPLUS station, capability by DeltaV microwave, satellite, 8-3
version, A-5 replication updates, 9-4
PROFIBUS retrievable history data, 8-4
DP card, 4-18 RS3 I/O interface, controller licensing, 3-4
extended fieldbus cable distances, 4-18 RS3 I/O interface carrier, 4-22
standard cables, 4-18 RS485 capability, 4-8

S special power bus link, 7-2 , 7-4
specifications, environmental, B-1
SCADA tags standard cables, AS−i bus, 4-12
definition, C-6 star topology, 2-4
licensing, 3-6 switch count, 2-6
SCADA value, how to count, C-3 system configuration, by DeltaV version, A-4
screened twisted−pair cable, 2-1 system dimensions, by DeltaV version, A-3
security request, 9-4 system capacities, A-1
segments system database, 8-10
DeviceNet, 4-13 sizing, 8-10
fieldbus I/O, 4-15 system power supplies, 7-1
selecting control network speed, 2-3 system sizing, 1-2
selecting correct workstation PC, 9-2 system−wide licensing, 8-2
sequence of events card, 4-9
serial I/O, 4-8
serial port license, 3-4
T
series 2 I/O, 4-1 tags, SCADA, 3-6
server class machine terminator
determining factors, 9-1 fieldbus, 4-16
node count greater than 11, 9-1 peer−to−peer bus, 6-2
shielded twisted pair cable, 2-7 PROFIBUS, 4-18
signal wiring, 10-2 third−party software
simplex controllers, 3-1 recommended products, 8-7
SIS System, capacities by DeltaV version, A-12 use on application station, 8-7
site preparation, 10-2 using restrictions, 8-7
sizing, system, 1-2 twisted pair cable, shielded, 2-7
sizing equation, application station, 8-18 two−wide carrier, 3-1
SLS I/O channel capability, 6-2 SISNet repeater, 6-2
SLS mounting on I/O carriers, 6-2 Type A cable, fieldbus, 4-16
SLS power, 6-4
smart wireless field network, 5-1
smart wireless plant network, 5-1
U
SOE interface, 4-9 uninterruptible power supplies, 7-8
software, third party. See third−party software determining quantity, 7-8
software suite prerequisites, 8-22 user account information, 9-4
special no−hub cable, 2-5 using data values, 8-18

using remote access services, 8-3 wireless control network segment, 5-1
wireless HART devices, 5-1
workstation
V
application comparison, 8-8
version, product, xi selecting correct PC, 9-2
vertical I/O carriers selection guide, xiii
electrical capacity, 10-26 spreadsheet, xiii
Legacy carrier, 10-26 workstations, common capability by DeltaV
VerticalPLUS carrier, 10-24 version, A-5
VIMnet software, 5-2 workstation class hardware, 9-1
virus protection, 8-7 , 9-5 workstation configuration utility, 9-4
workstation licensing, 8-1
workstation summary, 8-8
W workstations, prerequisites, 8-22
web site
AS−Interface, 4-12
DeltaV, xii , 2-1
Z
DeviceNet, 4-13 zone 1 CPU, 4-3
PROFIBUS, 4-18 zone 1 power supply, 4-3
web sites, third party, xiv zone 2 limitations on card types, 4-6
WebCD, xii zones for DeltaV (not remote I/O zones),
weights, DeltaV products, 10-16 8-24

Notes
Emerson Process Management
12301 Research Blvd
Research Park Plaza, Bldg III
Austin, TX 78759 USA
Tel 1 (512) 835−2190
Fax 1 (512) 832−3944

Desgning DeltaV - V103

Uploaded by

Copyright:

Available Formats

Desgning DeltaV - V103

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Desgning DeltaV - V103

Uploaded by

Copyright:

Available Formats

What are the main changes made in this edition of the manual?

What are the main changes made in this edition of the manual?

What publications provide supporting technical information for system planning?

What publications provide supporting technical information for system planning?

D800016X142

Planning and Designing Your

For Version 10.3

Chapter 1 System Sizing Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1-1

Chapter 2 Control Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2-1

System Planning Guide iii

Chapter 4 I/O Subsystem . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4-1

Chapter 5 Smart Wireless Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5-1

Chapter 6 Safety instrumented Systems . . . . . . . . . . . . . . . . . . . . . . . . 6-1

Chapter 7 Power Supplies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7-1

Chapter 8 Workstations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8-1

System Planning Guide v

Chapter 9 Computer Selection and Security . . . . . . . . . . . . . . . . . . . . 9-1

Chapter 10 Hardware Planning . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10-1

Appendix A System Capacities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . A-1

Appendix B Product Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . B-1

Appendix C Definition of Terms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . C-1

System Planning Guide vii

viii v10.3:March 2009

System Planning Guide ix

System Planning Guide xi

xii v10.3:March 2009

Internal Audience Only

Operating System Compatibility

System Planning Guide xiii

What’s New in This Edition

H Chapter 2 Updated list of available DeltaV network equipment.

H Chapter 3 Added references to DeltaV MX controller.

H Chapter 3 Added information about Advanced Unit Management licensing.

H Chapter 5 Added new chapter about Smart Gateway.

H Chapter 7 Added information about VE5009 System Power Supply.

H Chapter 8 Added explanation about DeltaV FlexConnect Solutions.

H Chapter 8 Corrected information in Table 7−3, Applications Included, Can Be

H Chapter 10 Updated AC current draw, power dissipation, and weights and

H Appendix A Updated Capacity tables.

H Appendix B Updated Environmental Specifications tables.

H Appendix C Expanded definition for Device Signal Tags (DSTs).

xiv v10.3:March 2009

Product Data Sheets

White Papers and Sales Information

The DeltaV Power Considerations paper provides an overview of power

System Planning Guide xv

H Installing Your DeltaV Digital Automation System

H Installing Your DeltaV Safety Instrumented System Hardware

H DeltaV Safety Instrumented System Safety Manual

H Fieldbus Installations in a DeltaV Digital Automation System

H Site Preparation and Design for DeltaV Digital Automation Systems

H Getting Started with your DeltaV Digital Automation System

H AS-i Interface http://www.as−interface.com/

H Foundation fieldbus http://www.fieldbus.org/

H HART Foundation http://www.hartcomm.org/

Sales Wizard Release Notes

xvi v10.3:March 2009

System Planning Guide xvii

xviii v10.3:March 2009