Ref 1005 PDF

Planning Your Ovation System
REF_1005
November 2011
Copyright Notice
Since the equipment explained in this document has a variety of uses, the user and those
responsible for applying this equipment must satisfy themselves as to the acceptability of each
application and use of the equipment. Under no circumstances will Emerson Process
Management be responsible or liable for any damage, including indirect or consequential losses
resulting from the use, misuse, or application of this equipment.
The text, illustrations, charts, and examples included in this manual are intended solely to explain
TM
the use and application of the Ovation Unit. Due to the many variables associated with specific
uses or applications, Emerson Process Management cannot assume responsibility or liability for
actual use based upon the data provided in this manual.
No patent liability is assumed by Emerson Process Management with respect to the use of
circuits, information, equipment, or software described in this manual.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, including electronic, mechanical, photocopying, recording or otherwise
without the prior express written permission of Emerson Process Management.
The document is the property of and contains Proprietary Information owned by Emerson Process
Management and/or its subcontractors and suppliers. It is transmitted in confidence and trust, and
the user agrees to treat this document in strict accordance with the terms and conditions of the
agreement under which it was provided.
This manual is printed in the USA and is subject to change without notice.
Ovation is the mark of Emerson Process Management. Other marks are the property of their
respective holders.
Copyright Emerson Process Management Power & Water Solutions, Inc. All rights reserved.
Emerson Process Management
Power & Water Solutions
200 Beta Drive
Pittsburgh, PA 15238
USA
E-Mail: Technical.Communications@Emerson.com
Website: https://www.ovationusers.com
Summary of Changes
Planning Your Ovation System
REF_1005
November 2011
The November 2011 version of Planning Your Ovation System contains
Additions/Corrections/Deletions about the following items:
New items:
19" Dell 190S Monitor (5X00473).
24" Dell U2410 WFP Monitor (5X00474).
OKIDATA Microline Printer (5X00445).
Dell T310 PowerEdge Domain Controller (5X00487).
Dell T310 PowerEdge Ovation Process Historian (5X00488).
Added information on the following new modules:
16 Channel 4-20mA Analog Input.
32 Channel 24V DC Single-Ended Digital Input.
32 Channel 24V DC Single-Ended Digital Output.
Added information for Numalogic Fast Ethernet Remote Node Controller.
Updated information for replacement parts, repair services, and material returns to Emerson
PWS.
Updated WDPF to Ovation Migration I/O module group numbers.
Updated Ovation terminology.
Obsoleted items:
Desktop LCD:
24" Dell 2408WFP (Obsoleted)
20" Dell UltraSharp 2001FP (Obsoleted)
20" NEC LCD2010X (Obsoleted)
19" Dell 1901FP (Obsoleted)
18" Dell 1801FP (Obsoleted)
18" NEC LCD1850E (Obsoleted)
18" NEC LCD1830 (Obsoleted)
Desktop CRT:
22"/20"v NEC AS120BK (Obsoleted)
22"/20"v Samsung 1100MB - CE (Obsoleted)
22"/20"v Samsung 1100DF - CE (Obsoleted)
22"/20"v NEC FE2111sb (Obsoleted)
22"/20"v NEC FE1250+ (Obsoleted)
22"/20"v Mitsubishi Diam.+ 200 (Obsoleted)
21" Mitsubishi (Obsoleted)
20" Sun-Sony 20D20/20E10 (Obsoleted)
Industrial CRT:
20" Intecolor V80 (Obsoleted)
19" Intecolor E19Z (Obsoleted)
Large Screen LCD:
57" NEC LCD5710-2 (Obsoleted)
57" NEC LCD5710-BK-IT (Obsoleted)
Large Screen CRT:
27" EDL 6127 (Obsoleted)
27" Conrac 9527 (Obsoleted)
Plasma Displays:
61" NEC PX-61XM3A (Obsoleted)
42" NEC PX-42VP5A (Obsoleted)
50" NEC PX-50XM4A (Obsoleted)
Color (Video Copy/Report) Printers:
HP Color Laserjet 5550 (Obsoleted)
HP Color Laserjet 4650N (Obsoleted)
HP 2600DN (Obsoleted)
HP 2500CM (Obsoleted)
HP Color Deskjet 1600CM (Obsoleted)
HP Color Deskjet 1200C (Obsoleted)
Tektronix Phaser 350 (Obsoleted)
Tektronix 4694 (Obsoleted)
Tektronix 4693 (Obsoleted)
Black & White Laser Printers:
HP Laserjet 5100 (Obsoleted)
HP Laserjet 4000N (Obsoleted)
HP Laserjet 5M (Obsoleted)
HP Laserjet 4M+ (Obsoleted)
HP Laserjet 4M (Obsoleted)
HP Laserjet III (Obsoleted)
Color (Alarm) Printers:
Tally LA36WC (Obsoleted)
Tally/Genicom T2265C (Obsoleted)
Genicom 3850 (Obsoleted)
Genicom 1040A (Obsoleted)
Serial High Speed Line Printers:
Genicom 4440XT (Obsoleted)
Windows Storage Devices:
RAID Disk Array 5X00163 (Obsoleted)
RAID Disk Array 5X00072 (Obsoleted)
Plasmon D120 CD-R Library (Obsoleted)
Solaris Storage Devices:
HP Desktop Optical Drives (Obsoleted)
Sun Unipack - Disk, Mag. Tape & CDROM (Obsoleted)
Artecon Lynx - Disk, Tape & CDROM (Obsoleted)
Sun Diskpak - Hard Disk (Obsoleted)
Other Obsoleted items:
Dell Precision M6400 Laptop (Obsoleted)
Unmouse Touchpads (Obsoleted)
SCSI Serial Port Expansion Devices (Obsoleted)
Modem, US Robotics, V.34 28.8/33.6Kbps (Obsoleted)
Contents
1
Introduction to planning your Ovation system
1.1
1.2
1.3
1.4
What is an Ovation system? ............................................................................................... 1

Ovation system terminology ................................................................................................ 2
What are the components of an Ovation system? .............................................................. 6
Planning the elements of an Ovation system ...................................................................... 9
Planning your Ovation equipment
2.1
2.2
2.3
Selecting equipment locations .......................................................................................... 11

Protecting the Ovation equipment ..................................................................................... 11
Electrical information for Ovation equipment .................................................................... 12
2.3.1
I/O cabinets (main/aux power and main/aux heat dissipation) (drawn from
AC/DC Mains power) ........................................................................................................ 13
2.3.2
Analog I/O modules (main/aux power and main/aux heat dissipation) (drawn
from AC/DC Mains power) ................................................................................................ 15
2.3.3
Bus interface modules ..................................................................................... 19
2.3.4
Digital I/O modules (main/aux power and main/aux heat dissipation) (drawn
2.3.5
Specialty I/O modules (main/aux power and main/aux heat dissipation) (drawn
2.3.6
Remote function modules (main/aux power and main/aux heat dissipation)
(drawn from AC/DC Mains power) .................................................................................... 33
2.3.7
Calculating Ovation main power requirements for OCR400 Controller .......... 34
2.3.8
Calculating Ovation main power requirements for OCR161 Controller .......... 35
Planning your Ovation network
3.1
3.2
3.3
3.4
3.5
What is the Ovation network? ........................................................................................... 38

Network terminology ......................................................................................................... 38
Network planning guidelines for Ovation systems ............................................................ 40
Preventing data collisions ................................................................................................. 41
Using Ethernet switches to provide network stability ........................................................ 41
3.5.1
Example of network switch configuration file .................................................. 42
3.5.2
Switches used in Ovation networks................................................................. 42
3.5.3
Media converters used In Ovation networks ................................................... 44
OSI Seven-Layer Model .................................................................................................... 45
Fast Ethernet network configurations ............................................................................... 47
Cable connection types for your network .......................................................................... 48
Single-tier network arrangement ....................................................................................... 50
Two-tier network arrangement .......................................................................................... 51
3.10.1
IP traffic switch ................................................................................................ 52
3.6
3.7
3.8
3.9
3.10
REF_1005
11
37
Table of Contents
3.11
3.12
3.13
3.14
3.15
Connecting workstations to your Ovation network ............................................................ 52

Connecting OCR400 Controllers to your Ovation network ............................................... 53
Connecting Ovation devices to your Ovation network ...................................................... 57
Connecting non-Ovation devices to your Ovation network ............................................... 58
Planning your Ovation multiple networks
4.1
4.2
4.3
4.4
What is an Ovation multiple network? ............................................................................... 59

Multiple network terminology ............................................................................................. 59
Multiple network planning guidelines for Ovation systems ............................................... 61
What do you need to plan before connecting multiple networks? .................................... 63
4.4.1
What is a multiple network implementation for new Ovation systems? .......... 64
4.4.2
What is a multiple network implementation for existing Ovation systems?..... 65
4.4.3
What is a multiple network implementation for hybrid Ovation systems? ....... 66
What is the connection plan for multiple networks? .......................................................... 67
4.5.1
What is backbone connectivity for multiple networks? .................................... 68
4.5.2
What is collapsed backbone connectivity for multiple networks? ................... 70
4.5.3
Hardware information for Ovation multiple networks ...................................... 71
4.5
Planning cable configurations for your Ovation system
5.1
Network cable configuration types for your Ovation system ............................................. 73

5.1.1
Unshielded twisted pair (UTP)......................................................................... 73
5.1.2
Multi-mode fiber optic cable ............................................................................ 74
5.1.3
Single-mode fiber optic cable .......................................................................... 74
5.1.4
Media converters ............................................................................................. 75
Selecting network cable .................................................................................................... 75
5.2.1
Existing network cable infrastructure............................................................... 75
5.2.2
EMI/RFI environment for network cable .......................................................... 75
5.2.3
Grounding network cable ................................................................................ 76
5.2.4
Distance between network nodes ................................................................... 76
5.2.5
Permanently installed network cables ............................................................. 76
Planning network and I/O field wiring routing .................................................................... 77
5.3.1
Field wiring requirements ................................................................................ 80
5.3.2
AC/DC Mains wiring requirements .................................................................. 81
5.2
5.3
73
Planning grounding for your Ovation system
6.1
6.2
6.3
6.4
General grounding guidelines ........................................................................................... 83

Protective earth ................................................................................................................. 83
Ovation cabinet EMC grounding ....................................................................................... 83
Grounding guidelines for single cabinet arrangements .................................................... 84
6.4.1
AWG diameters for solid and stranded wire .................................................... 85
6.4.2
Example of finding the diameter of a network cable ....................................... 86
Grounding guidelines for clustered cabinet arrangements ............................................... 86
6.5.1
To remove the shorting bar from an Ovation cabinet ...................................... 87
6.5
ii
59
83
REF_1005
Table of Contents
Planning I/O modules for your Ovation system
7.1
7.2
7.3
7.4
What is an Ovation module? ............................................................................................. 91

Ovation I/O module features ............................................................................................. 91
Standard I/O modules ....................................................................................................... 93
Remote function modules (RIO)........................................................................................ 93
7.4.1
MAU module .................................................................................................... 94
7.4.2
RNC module .................................................................................................... 96
Relay Output modules ....................................................................................................... 98
Guidelines for replacing, adding, or combining Ovation modules..................................... 99
Installing Ovation standard I/O modules ......................................................................... 101
7.7.1
To hot swap standard I/O modules ............................................................... 101
7.7.2
To add new standard I/O modules ................................................................ 102
Installing Ovation Relay Output modules ........................................................................ 102
7.8.1
To hot swap Relay Output Electronics modules ........................................... 102
7.8.2
To add new Relay Output I/O modules ......................................................... 103
What are the I/O module types? ..................................................................................... 104
7.9.1
Analog Input modules .................................................................................... 105
7.9.2
Analog Output modules ................................................................................. 108
7.9.3
Digital Input modules ..................................................................................... 110
7.9.4
Digital Output modules .................................................................................. 114
7.9.5
Bus interface modules ................................................................................... 116
7.9.6
Specialty Modules ......................................................................................... 117
7.5
7.6
7.7
7.8
7.9
91
Planning Ovation cabinets for your Ovation system
8.1
8.2
8.3
8.4
8.5
8.6
What are Ovation cabinets? ............................................................................................ 124

Cabinet configuration guidelines ..................................................................................... 125
Ovation cabinet components........................................................................................... 126
How many I/O modules can an OCR400 Controller support? ........................................ 127
Ovation Controller cabinet ............................................................................................... 128
8.6.1
Controller cabinet configuration for local Ovation I/O.................................... 128
8.6.2
Controller cabinet configuration for remote Ovation I/O ................................ 129
8.6.3
Controller cabinet configuration for mixed (local and remote) Ovation I/O ... 129
8.6.4
Controller cabinet configuration for local Q-Line I/O ..................................... 130
8.6.5
Controller cabinet configuration for remote Q-Line I/O ................................. 130
8.6.6
Illustrations of Controller cabinet configurations ........................................... 131
Ovation Marshalling cabinet ............................................................................................ 133
Illustrations of Marshalling cabinet configurations .......................................................... 133
Ovation extended I/O cabinet.......................................................................................... 136
8.9.1
Illustrations of Extended cabinet configurations ............................................ 136
Remote Node cabinet ..................................................................................................... 138
8.10.1
Illustrations of Remote Node cabinet configurations ..................................... 139
8.10.2
Illustrations of Relay Panel cabinet configurations........................................ 142
8.7
8.8
8.9
8.10
REF_1005
123
iii
Table of Contents
8.11
8.12
8.13
8.14
8.15
8.16
8.18
Examples of cable access areas and floor bolting in Ovation cabinets .......................... 143
Examples of available usage area for field wiring ........................................................... 149
Weights of Ovation cabinets ........................................................................................... 151
Floor plan recommendations ........................................................................................... 153
Cleaning and maintenance guidelines for Ovation Controller cabinets .......................... 154
OCR400 Controller Modules ........................................................................................... 155
8.16.1
To replace OCR400 Controller modules ....................................................... 155
OCR161 Controller cover ................................................................................................ 157
8.17.1
To open the OCR161 Controller cover .......................................................... 159
8.17.2
To close the OCR161 Controller cover ......................................................... 160
8.17.3
Removing the OCR161 Controller fan assembly .......................................... 160
8.17.4
Replacing the OCR161 Controller fan assembly .......................................... 160
User-supplied cabinets .................................................................................................... 161
Planning power for your Ovation cabinets
9.1
How is power distributed in an Ovation system? ............................................................ 163

9.1.1
Example of OCR400 Controller/Marshalling cabinet
(with local and remote cabling) ...................................................................... 165
9.1.2
Example of OCR161 Controller/Marshalling cabinet
(with local and remote cabling) ...................................................................... 166
9.1.3
Example of extended I/O cabinet (illustrating cables and standard I/O) ....... 167
9.1.4
Example of extended I/O cabinet
(illustrating cables and relay output modules) ............................................... 168
9.1.5
Example of Ovation Remote Node cabinet (illustrating cables) .................... 169
9.1.6
Example of Ovation Power Distribution Module (PDM) ................................ 170
9.1.7
Examples of transition panels ....................................................................... 171
9.1.8
Example of Controller OCR400 backplane ................................................... 173
9.1.9
Example of Controller OCR161 backplane ................................................... 174
Connecting the power mains to an Ovation cabinet ....................................................... 175
9.2.1
To connect the AC Mains to the line filter assembly (CE Mark Certified) ..... 175
9.2.2
To connect the AC/DC Mains to the Power Distribution Module (PDM) ....... 178
Using power supply modules .......................................................................................... 179
9.3.1
Power supply features ................................................................................... 179
9.3.2
Available power supply modules ................................................................... 180
9.3.3
Power supply limits ........................................................................................ 182
9.3.4
Controller Cabinet On/Off Controls ............................................................... 182
9.4
Calculating Ovation power supply requirements
(drawn from +24V main or auxiliary power supply) ............................................ 184
9.4.1
Calculating power supply requirements for I/O Cabinet components ........... 184
9.4.2
Calculating power supply requirements for Analog I/O modules .................. 186
9.4.3
Calculating power supply requirements for Bus interface modules .............. 188
9.4.4
Calculating power supply requirements for Digital I/O modules ................... 189
9.4.5
Calculating power supply requirements for Specialty I/O modules ............... 193
9.4.6
Calculating power supply requirements for remote function modules .......... 195
Monitoring power supply status....................................................................................... 195
9.5.1
Monitoring one set of redundant power supplies .......................................... 195
9.5.2
Monitoring two sets of redundant power supplies ......................................... 196
8.17
9.2
9.3
9.5
iv
163
REF_1005
Table of Contents
9.6
Using an external power supply ...................................................................................... 197
10
Planning for replacement parts and repair service
10.1
10.3
10.4
10.5
Ordering spare parts ....................................................................................................... 205

10.1.1
Determining a spare part number.................................................................. 205
10.1.2
Determining a spare part price ...................................................................... 206
Returning parts to Emerson for repair service ................................................................ 206
10.2.1
Obtaining a Material Return Tracking (MRT) number ................................... 207
10.2.2
Handling in-warranty and non-warranty part repairs ..................................... 208
Part failure during project startup .................................................................................... 208
Determining repair prices ................................................................................................ 208
Tracking part repairs ....................................................................................................... 209
11
Planning for shipping and storage of Ovation equipment
11.1
11.2
11.3
11.4
11.5
11.6
11.7
Guidelines for shipping Ovation equipment .................................................................... 211

Guidelines for lifting Ovation equipment ......................................................................... 212
Guidelines for off-loading and unpacking Ovation equipment ........................................ 213
Guidelines for repacking and returning Ovation equipment ............................................ 214
Guidelines for repacking third-party products ................................................................. 214
Guidelines for transporting Ovation equipment to the specific installation location ........ 214
Guidelines for storing Ovation equipment ....................................................................... 214
12
Planning your CE Mark Certified system
12.1
12.2
12.3
What is a CE Mark Certified system? ............................................................................. 218

Using third-party components in CE Mark Certified systems ......................................... 219
Using a grounding panel for CE Mark Certified systems ................................................ 220
12.3.1
Grounding panel configuration ...................................................................... 221
10.2
REF_1005
205
211
217
Table of Contents
vi
12.4
12.5
12.6
12.7
Cabling requirements for CE Mark Certified systems ..................................................... 223

AC line filtering (Applicable to EMC Cabinet approach only) .......................................... 223
Internal cable ferrites (non-EMC cabinet approach only) ............................................... 224
Ovation Suppression Panel ............................................................................................. 224
13
Planning your IEC61131-2 system
13.1
13.2
13.3
What is an IEC61131-2 certified system? ....................................................................... 225

Using a grounding panel for IE61131-2 certified system ................................................ 225
Cabling requirements for IEC61131-2 certified systems ................................................ 225
14
Planning to meet industry standards of compliance
14.1
14.2
14.3
14.4
Design standards ............................................................................................................ 227

Reliability standards ........................................................................................................ 227
Electrical interference standards ..................................................................................... 227
Safety standards ............................................................................................................. 227
15
Planning your internet addressing
15.1
15.2
15.3
15.4
15.5
Classes of internet addresses ......................................................................................... 229

Internet address notation ................................................................................................ 230
Allowable internet addresses .......................................................................................... 230
Internet address conventions .......................................................................................... 231
Subnet masks.................................................................................................................. 231
16
Planning your Ovation database
16.1
16.2
16.3
16.4
16.5
16.6
16.7
16.8
What is a Relational Database? ...................................................................................... 233

What is a point? .............................................................................................................. 234
What are point records? .................................................................................................. 235
What is point frequency? ................................................................................................. 236
Understanding point names ............................................................................................ 236
Using valid Ovation point names..................................................................................... 236
Using fully qualified point names..................................................................................... 238
Creating the Ovation Database ....................................................................................... 238
16.8.1
Database tools............................................................................................... 239
16.8.2
What is the Database Initial Definition tool (DBID)? ...................................... 239
16.8.3
Entering information in DBID fields ............................................................... 240
225
227
229
233
REF_1005
Table of Contents
17
Planning software installation for

Windows-based Ovation systems
243
17.1
17.2
17.3
17.4
17.5
17.6
17.7
17.8
17.9
Understanding the software installation process for Windows-based Ovation systems. 243
What is the domain concept? .......................................................................................... 244
Best practices for installing Ovation system software ..................................................... 245
What are the hardware requirements for a domain controller? ...................................... 245
What are the hardware requirements for a domain member as a Database Server? .... 245
What are the software requirements for a domain controller? ........................................ 246
What are the software requirements for a domain member? ......................................... 246
What are the licensing requirements for an Ovation Windows-based system? ............. 247
What is the drop type? .................................................................................................... 248
18
Planning control for your Ovation system
18.1
18.2
18.3
18.4
18.5
18.6
18.7
18.8
18.9
18.10
18.11
18.12
What is Ovation control? ................................................................................................. 250

What types of control are supported in Ovation? ............................................................ 251
What is the Ovation Control Builder? .............................................................................. 252
Control Builder terminology ............................................................................................. 253
What is the control planning process? ............................................................................ 256
What is the scope of your control project? ...................................................................... 257
What are the best practices for planning control? ........................................................... 257
Planning for system expansion ....................................................................................... 259
Using diagrams in planning control ................................................................................. 260
What are the best practices for designing control? ......................................................... 260
What are Ovation control functions (control sheets)? ..................................................... 261
What are the best practices for building control sheets? ................................................ 262
19
Planning your Ovation Controller
19.1
19.2
What is the Ovation OCR400 Controller? ....................................................................... 263

What are the OCR400 Controller I/O interfaces? ........................................................... 264
20
Planning Virtual Controllers
20.1
20.2
20.3
20.4
20.5
20.6
What is a Virtual Controller? ........................................................................................... 267

Why use Virtual Controllers?........................................................................................... 268
Requirements for Ovation Virtual Controllers ................................................................. 269
Hardware requirements for the Ovation Virtual Controller host ...................................... 269
Software requirements for the Ovation Virtual Controller host ....................................... 269
What are the licensing requirements for Ovation Virtual Controllers? ............................ 269
21
Planning security for your Ovation system
21.1
What is external security? ............................................................................................... 272
REF_1005
249
263
267
271
vii
Table of Contents
viii
21.2
21.3
21.4
21.5
What is Ovation internal security?................................................................................... 272

Using the domain concept in security ............................................................................. 273
What are the best practices for establishing a secure system? ...................................... 274
What is antivirus software? ............................................................................................. 274
21.5.1
Why is antivirus software important?............................................................. 275
21.5.2
What are the components of Kaspersky antivirus? ....................................... 275
22
Planning for an Ovation Process Historian (OPH)
22.1
22.2
22.3
22.4
22.5
22.6
22.7
What is the Ovation Process Historian? ......................................................................... 277

How many historians do you need? ................................................................................ 279
How many scanners do you need? ................................................................................. 279
How will you archive your data?...................................................................................... 280
Who are your end users? ................................................................................................ 281
Do you need to migrate eDB or HSR data to your new historian? ................................. 282
Will you need any third-party software? .......................................................................... 282
23
Planning for first generation (gateway) Foundation Fieldbus
23.1
23.2
23.3
23.4
23.5
23.6
23.7
23.8
Foundation Fieldbus first and second generation solutions ............................................ 283

What is Foundation Fieldbus?......................................................................................... 284
Understanding Foundation Fieldbus interoperability....................................................... 285
Understanding Foundation Fieldbus segmentation ........................................................ 286
What is good Foundation Fieldbus segmentation design? ............................................. 286
23.5.1
Planning the Foundation Fieldbus topology .................................................. 287
23.5.2
What should be Foundation Fieldbus I/O? .................................................... 290
23.5.3
Partitioning instruments and applications ...................................................... 291
What are the recommended installation practices for Foundation Fieldbus? ................. 291
Using Fieldbus in Ovation control ................................................................................... 292
Using PlantWeb Alerts for Fieldbus alarms .................................................................... 293
24
Planning for second generation (I/O module) Foundation Fieldbus 295
24.1
24.2
24.3
24.4
24.5

Understanding Foundation Fieldbus interoperability....................................................... 297
What are the Foundation Fieldbus and Ovation components? ....................................... 298
24.5.1
Planning the Foundation Fieldbus topology .................................................. 301
24.5.2
What should be Foundation Fieldbus I/O? .................................................... 304
24.5.3
Partitioning instruments and applications ...................................................... 305
24.5.4
What are the recommended installation practices for Foundation Fieldbus?305
277
283
REF_1005
Table of Contents
24.6
What are the supported Fieldbus algorithms? ................................................................ 306
25
Planning for Profibus
25.1
25.2
25.3
25.4
25.5
25.6
What is an overview of Profibus? .................................................................................... 308

What is device interoperability? ...................................................................................... 309
What are the Profibus and Ovation components? .......................................................... 310
What are Profibus devices? ............................................................................................ 311
What is Profibus redundancy? ........................................................................................ 313
What are Profibus hardware and software requirements? ............................................. 315
26
Planning for DeviceNet
26.1
26.2
26.3
26.4
26.5
What is an overview of DeviceNet? ................................................................................ 318

What is field device interoperability? ............................................................................... 319
What are the DeviceNet and Ovation components? ....................................................... 320
What is a DeviceNet module? ......................................................................................... 321
What are the DeviceNet hardware and software requirements? .................................... 321
27
Planning alarm management
27.1
What is an alarm? ........................................................................................................... 323

27.1.1
What is an example of the life of an alarm? .................................................. 324
What is alarm management? .......................................................................................... 324
What are some alarm management problems? .............................................................. 325
What are some best practices for planning alarms? ....................................................... 325
27.4.1
Establishing a philosophy for alarm management ........................................ 326
What points can be used as alarms? .............................................................................. 326
27.5.1
When is a point out of service? ..................................................................... 327
How does the Ovation alarm system operate? ............................................................... 327
Types of alarm displays .................................................................................................. 328
Alarm list information fields ............................................................................................. 328
Displaying Alarm lists ...................................................................................................... 329
Alarm list tabs that display in the Alarm window ............................................................. 330
27.10.1
Alarm List in the Operator Station Alarm window.......................................... 332
27.10.2
History list in the Operator Station Alarm window ......................................... 333
27.10.3
Acknowledged list in the Operator Station Alarm window ............................. 334
27.10.4
Unacknowledged list in the Operator Station Alarm window ........................ 335
27.10.5
Reset list in the Operator Station Alarm window ........................................... 336
27.10.6
Icon list in the Operator Station Alarm window ............................................. 337
Remote Network Status list in the Operator Station Alarm window ................................ 339
What is the Alarm Annunciation window at the Operator Station? ................................. 341
What are some best practices for managing alarms?..................................................... 342
What are nuisance alarms? ............................................................................................ 342
27.14.1
What methods can be used to manage nuisance alarms? ........................... 343
What are alarm floods? ................................................................................................... 343
27.15.1
What are suggested alarm rates? ................................................................. 343
27.15.2
Configuring filtering for alarms ...................................................................... 343
27.2
27.3
27.4
27.5
27.6
27.7
27.8
27.9
27.10
27.11
27.12
27.13
27.14
27.15
REF_1005
307
317
323
ix
Table of Contents
27.15.3
27.15.4
27.15.5
27.15.6
27.15.7
27.15.8
27.15.9
Using audio for situation awareness ............................................................. 348

What are the methods used to log alarms? .................................................. 348
Using security for alarm management .......................................................... 349
Using PlantWeb Alerts for Fieldbus alarms ................................................... 350
Setting alarm limits ........................................................................................ 351
What methods are available to reduce the number of
alarms in your system?.................................................................................. 352
What are the benefits of good alarm management? ..................................... 356
28
Planning Connectivity for your Ovation system
357
28.1
28.2
28.3
28.4
28.5
What is Ovation Connectivity? ........................................................................................ 357

What are the available platforms for an Ovation communication interface? .................. 357
What are the physical connection options for an Ovation communication interface? .... 358
What are the current message protocols for an Ovation communication interface? ...... 359
Communication interface spreadsheets .......................................................................... 359
28.5.1
Hardware/Device spreadsheet ...................................................................... 361
28.5.2
Release version spreadsheet ........................................................................ 364
29
Planning your Ovation Security Center
29.1
29.2
29.3
29.4
What is the Ovation Security Center? ............................................................................. 367

Functions of the Ovation Security Center ....................................................................... 367
Appliances in the Ovation Security Center ..................................................................... 368
OSC compatibility with Ovation releases ........................................................................ 370
30
Planning your Safety Instrumented System
30.1
30.2
30.3
30.4
30.5
30.6
What is a Safety Instrumented System? ......................................................................... 371

Functions of Ovation SIS ................................................................................................ 372
Limitations for Ovation SIS system ................................................................................. 372
Hardware components of Ovation SIS ............................................................................ 373
30.4.1
Planning your hardware installation .............................................................. 375
Software components of Ovation SIS ............................................................................. 375
Ovation SIS Logic Solver algorithm table ....................................................................... 376
31
Ovation hardware specification sheets
31.1
Cabinet specification sheets ........................................................................................... 380

31.1.1
EMC cabinet, NEMA12, Rittal (4D33947) ..................................................... 380
31.1.2
Cabinet vented, NEMA12 (5X00018) ............................................................ 381
31.1.3
Cabinet sealed NEMA12 (5X00019H01) ...................................................... 382
31.1.4
Cabinet sealed NEMA4 (5X00019H02) ........................................................ 383
31.1.5
Cabinet vented NEMA12 (without mounting plate) (5X00020) ..................... 384
31.1.6
Cabinet vented NEMA12 (with mounting plate) (5X00127) .......................... 385
31.1.7
31.1.8
Cabinet sealed, NEMA12 (5X00035H01/H03) .............................................. 387
31.1.9
Cabinet sealed, NEMA4 (5X00035H02/H04) ................................................ 388
31.1.10
Cabinet sealed, NEMA12 (5X00046H01) ..................................................... 389
31.1.11
Cabinet sealed, NEMA4 (5X00046H02) ....................................................... 390
31.1.12
Cabinet vented, NEMA12 (front access only) (5X00068) ............................. 391
367
371
379
REF_1005
Table of Contents
31.2
31.3
31.4
31.5
31.6
31.7
31.8
REF_1005
31.1.13
31.1.14
Cabinet sealed, NEMA12 (1X00455) ............................................................ 391
31.1.15
Cabinet vented (1X00518) ............................................................................ 391
31.1.16
Cabinet vented (1X00545) ............................................................................ 392
Ovation workstation specification sheets ........................................................................ 393
31.2.1
Dell Poweredge T310 Domain Controller or Terminal Server Host
Workstation (5X00487) (Windows Server 2008) ........................................... 393
31.2.2
Dell Poweredge R710 Domain Controller/Database Server (Rack Mount)
(5X00462) (Windows Server 2008) ............................................................... 394
31.2.3
Dell Precision T3500 Engineer / System Database Server (5X00557 for XP)
(5X00558 for Win7) ....................................................................................... 395
31.2.4
Dell Optiplex 990 Engineer Client Station/Operator Station/Virtual Controller
(XP) (5X00571) .............................................................................................. 395
31.2.5
Dell Optiplex 990 Engineer Client Station/Operator Station/Virtual Controller
(Windows 7) (5X00572) .................................................................................................. 396
31.2.6
Dell Precision R5400 Operator Station (XP) (Rack Mount) (5X00559) ........ 396
31.2.7
Dell Precision R5400 Operator Station (Windows 7)
(Rack Mount) (5X00461) ............................................................................... 397
31.2.8
Dell Poweredge T310 Server Ovation Process Historian (OPH) (5X00488)
(Windows Server 2008) ................................................................................. 397
31.2.9
Dell Poweredge R710 Ovation Process Historian (Rack Mount) (5X00463)
(Windows Server 2008) ................................................................................. 398
31.2.10
Dell Precision T5500n EDS Workstation (5X00569) (Windows 7) (64-bit) ... 399
31.2.11
Dell Precision T5500n EDS Workstation Linux Red Hat Enterprise
(5X00567) ...................................................................................................... 399
31.2.12
Dell Poweredge R710 EDS Windows Server 2008 (5X00570) ..................... 400
31.2.13
Dell Poweredge R710 EDS Linux Red Hat Enterprise (5X00568) ................ 401
Monitor specification sheets ............................................................................................ 402
31.3.1
Dell 190S FP (19" monitor) (5X00473) .......................................................... 403
31.3.2
Dell 2007FP (20" monitor) (5X00310) ........................................................... 404
31.3.3
Dell U2410 (24" monitor) (5X00474) ............................................................. 404
31.3.4
NEC V321 (32" monitor) (5X00493) .............................................................. 405
31.3.5
NEC P401 (40" monitor) (5X00494) .............................................................. 405
31.3.6
NEC P461 (46" monitor) (5X00495) .............................................................. 405
Keyboard specification sheet .......................................................................................... 406
31.4.1
Ovation Keyboard (4D33935)........................................................................ 407
Printer specification sheets ............................................................................................. 408
31.5.1
HP B/W Laserjet 5200 printer (5X00328) ...................................................... 409
31.5.2
HP Thermal/Inkjet 2800DTN printer (5X00243) ............................................ 410
31.5.3
Okidata Microline 395C (5X00445) ............................................................... 410
31.5.4
HP Color Laserjet Enterprise CP4525n/4525dn (5X00520) ......................... 410
31.5.5
HP Color Laserjet 5525 (5X00550) ............................................................... 411
Storage device specification sheets ................................................................................ 412
31.6.1
RAID SATA to iSCSI Media (5X00523) ........................................................ 413
I/O module environmental specifications ........................................................................ 413
Analog Input module electrical specification sheets ....................................................... 414
31.8.1
Analog Input 13 bit module (legacy systems) ............................................... 415
31.8.2
Analog Input 14 bit module ............................................................................ 418
31.8.3
Analog Input 14 bit high speed module ......................................................... 419
31.8.4
HART Analog Input module ........................................................................... 422
31.8.5
HART High Performance Analog Input module ............................................ 423
31.8.6
RTD Input module (4 channel) ...................................................................... 424
31.8.7
RTD Input module (8 channel) ...................................................................... 425
xi
Table of Contents
31.9
31.10
31.11
31.12
31.13
31.14
31.15
Index
xii
Analog Output module electrical specification sheets..................................................... 426

31.9.1
Analog Output module (4 channels) .............................................................. 427
31.9.2
HART Analog Output module ........................................................................ 428
31.9.3
HART High Performance Analog Output module .......................................... 429
Digital Input module electrical specification sheets......................................................... 430
31.10.1
Digital Input module (16 channels) ................................................................ 431
31.10.2
Compact Digital Input module ....................................................................... 433
31.10.3
Contact Input module .................................................................................... 435
31.10.4
Compact Contact Input module ..................................................................... 436
31.10.5
Sequence of Events Digital Input module ..................................................... 437
31.10.6
Compact Sequence of Events Digital Input module ...................................... 439
31.10.7
Enhanced Compact Sequence of Events Digital
Input module (16 channels) ........................................................................... 441
Digital Output module electrical specification sheets ...................................................... 444
31.11.1
Digital Output module electrical (16 channels) .............................................. 445
31.11.2
High Side Digital Output module (24VDC) .................................................... 449
31.11.3
Relay Output module electrical ..................................................................... 450
Bus interface module electrical specification sheets ...................................................... 452
31.12.1
Foundation Fieldbus module (2 channels) .................................................... 452
31.12.2
Profibus module (2 channels)........................................................................ 453
31.12.3
DeviceNet module (2 channels) .................................................................... 453
31.12.4
Ethernet Link Controller module (1 channel) ................................................. 453
Specialty module electrical specification sheets ............................................................. 454
31.13.1
Link Controller module .................................................................................. 455
31.13.2
Loop Interface module (normal non-electric drive)........................................ 456
31.13.3
Loop Interface module (electric drive) ........................................................... 460
31.13.4
Pulse Accumulator module ............................................................................ 463
31.13.5
Servo Driver module ...................................................................................... 465
31.13.6
Speed Detector module ................................................................................. 467
31.13.7
Valve Positioner module ................................................................................ 468
31.13.8
SLIM (Small Loop Interface module) ............................................................. 470
Remote Function module electrical specification sheets ................................................ 471
31.14.1
Remote Media Attachment Unit (MAU) module specifications ..................... 472
31.14.2
Remote Node Controller (RNC) module specifications ................................. 473
Cable specification sheets .............................................................................................. 474
31.15.1
Network Fiber-Optic cable specifications (5A26164Gxx) .............................. 475
31.15.2
Network UTP cable specifications ................................................................. 476
31.15.3
Network Remote I/O cable specifications ..................................................... 477
479
REF_1005
E C T I O N
IN THIS SECTION
What is an Ovation system? ............................................................................................... 1
Ovation system terminology ................................................................................................ 1
What are the components of an Ovation system? .............................................................. 6
Planning the elements of an Ovation system ...................................................................... 9
1.1
What is an Ovation system?

Ovation is a Distributed Control System (DCS) whose modular design permits you to configure
your process management system exactly as it is needed. You can expand a small installation to
include as many as 254 intelligent modules (referred to as drops). Each drop is a separate
module that can perform various functions. Ovation systems use commercially available hardware
platforms, operating systems, and open network technology.
You should consider the following elements when you plan and configure your Ovation system:
Redundant high-speed network that uses Fast Ethernet standards to send input and output
data to all the stations and Controllers connected to the network.
Workstations (Windows-based computers) that receive and send data in order to perform
any operations needed to run a process. These workstations are typically connected to a
switch, which is, in turn, connected to the network.
A Controller that executes modulating and sequential control strategies and interfaces to
input and output modules. The Controller is the drop containing the modules (I/O) that are
attached to sensors on the actual plant equipment. These sensors measure the point values
that are then broadcast onto the Ovation Network.
Hardware such as cabinets, cables, and grounding equipment.
Input/Output (I/O) modules that interface field signals (temperature, pressure, and so forth)
from the actual plant processes to the Controller. The Controller sends the information over
the network to the workstations. In turn, messages are sent from the workstations to the
Controller, so that adjustments can be made, as needed, by the Controller.
Software packages that run on Ovation workstations and perform the tasks needed to
configure, manage, and operate an Ovation system.
Note: Contact your project manager for answers to any questions you might have about your
specific system.
REF_1005
1.2 Ovation system terminology
1.2
Ovation s ystem termin ology

TERM
DESCRIPTION
AC Mains
Cables that carry the main AC current into the I/O cabinets.
API
Database Application Programming Interface. Used to talk or interface to the system

Relational Databases: Oracle (Master Database) or Raima (Distributed Database used by
Operator Stations and populated from Oracle).
AUI cable
Attachment Unit Interface (AUI) Cable that interfaces the IOIC card to the MAU module in
remote I/O applications.
B side
Refers to the right side board-to-board connector of the base unit when the terminal block or
AUI Cable connector is facing the viewer.
Base unit
Consists of a printed circuit board, various connectors, and plastic housing. It provides a
mechanism to attach field wiring, and to connect the field signals to the I/O module. The unit
enables the I/O module to receive power, and also provides a low-impedance earth ground
connection. Each Base Unit can house two sets of I/O modules, along with the associated
field wiring.
Baud rate
Number of bits-per-second a modem can send or receive.
Branch
Set of Base Units configured consecutively on a DIN rail with a local bus being connected to
the Ovation I/O controller.
Bridge
Device that connects two or more network components and transmits data with source and
destination addresses on different network components.
Broadcast
Data packet delivery system where copies of the packet are delivered to all destinations on
the network.
Business Rules
Layer of software between Ovation applications and the database interface software.
Client
A computer or software program that is used to contact and obtain data from a server
software program on a networked computer.
Collision
The garbling of data when two or more nodes on the same network segment transmit
simultaneously.
Compact I/O
modules
Ovation I/O modules that do not contain a Personality module, only an Electronics module.
Control Builder
Power tool package used to build control drawings and generate source code from the
drawings.
Controller
Drop used to control a process. The Controller passes process control information over the
network to other drops or devices that need it.
CSMA/CD
Carrier Sense Multiple Access with Collision Detection. Senses a collision and causes the
colliding frames to be retransmitted increasing network congestion, which reduces system
throughput.
DCS
Distributed Control System.
Discrete I/O
Individual hard-wired circuits connecting real-world field devices with the processor. Each
discrete input provides the processor with a single digital signal based on a single state in
the field device. Each discrete output sends a single digital signal to the field based on a
single bit of data in the processor.
Distributed
Database
Contains a subset of the information stored on the Master Database. A Distributed Database
is present on each drop in the system and is continually updated as point information
changes.
REF_1005
TERM
DESCRIPTION
Distributed I/O
Hardware used to communicate between the processor and I/O modules located outside the
processor chassis (also called Remote I/O). Refers either to the Q-Line or the Ovation I/O
line.
Drop
A collective term for a Controller, Workstation, or Database Server that is a member of an

Ovation network and is defined as a drop by an Ovation configuration tool (Developer Studio
for Windows or Init and Admin Tools for Solaris)
Dual attachment
Connection to two different switches. A Dual Attached Station (DAS) is a node that is
connected to two different switches.
Electronics
module
Portion of an I/O module that provides a plastic housing with associated lenses and labeling.
It contains up to two printed circuit boards (the logic board and field board) that provide the
electronics necessary to interface the field devices with the I/O Controller.
Fast Ethernet
Ethernet specification that runs at 100 megabits per second.
I/O module
Standard I/O modules are made up of an Electronics module and a Personality module.
Compact modules and Relay Output modules do not contain a Personality module. These
modules perform the interface between the I/O Controller and the field devices.
IOIC card
Generic name for the Ovation I/O Interface card. Also known as PCI card. Options are
PCQL, PCRL, and PCRR cards for the OCR161 Controller. The OCR400 Controller uses
only one IOIC module.
Init and Admin

Tools
Configuration tools that house all of the integrated engineering tools necessary for a Solarisbased Ovation system.
IP address
Internet Protocol address. Uniquely identifies a computer connected to a network. Typically

assigned by the system administrator. For example: 133.225.22.22.
LAN
Local Area Network. A computer network limited to the immediate area, usually the same
building.
License
A necessary permission to use certain Emerson Process Management software products.
Load function
Ovation function that is used to transfer data from the Master Database and distribute it to
control drops and those drops that originate points.
Master Database
Contains the entire process database. It is used for creating, modifying, and verifying control
strategies and process points. At runtime, it supports queries of the process database,
captures changes made to control and point attributes, and propagates those changes to
the distributed database.
MAU
Media Attachment Unit (MAU) is an alternate name for the Attachment Unit Module and
includes the Electronics module and Personality module combined. This device interfaces
the IOIC card (via the AUI cable) to the RNC (via fiber-optic cable) in remote I/O
applications.
Membrane
Keyboard
Also known as the Ovation Keyboard. Optional keyboard that is used in conjunction with the
standard keyboard and mouse. It allows the operator to access data acquisition and control
applications.
Migration
Process where the legacy Q-Line I/O is interfaced to an Ovation Controller.
Network
The communication link used to transfer time-critical information between drops or stations.
Network Nodes
Another term for drops on the Ovation Network.
NIC
A Network Interface Card (NIC) is required in each of the end stations, Controller or HMI.
NICs are available in two configurations, Single Attach Station (SAS) or Dual Attach Station
(DAS) with copper connections. Within a system, it is NOT necessary that all stations have
like modes of attachment. SAS and DAS may be mixed as economics, function, and
redundancy dictate.
REF_1005
TERM
DESCRIPTION
Node
Active element on a Fast Ethernet network that has an address. Can be a station or a
switch. Up to 1000 nodes are permitted per network.
Operator Station
A drop in an Ovation system, used to control and monitor plant operation.
Ovation Developer
Studio
Configuration tool that houses all of the integrated engineering tools necessary for a
Microsoft Windows-based Ovation system.
Ovation network
Local area network in which Ovation drops communicate with each other through Fast
Ethernet media.
Ovation system
An open architecture Emerson Process Management System that is based on ANSI and
ISO network standards. Uses snap-in modules for I/O.
PCI
Peripheral Component Interconnect. Main bus used in the Controller for communication
between the Controller CPU network interface and I/O Controller modules. Also known as
IOIC cards. Controller OCR 161 uses PCQL, PCRL, and PCRR cards. Controller OCR 400
uses only one IOIC card.
PCQL card
Ovation IOIC card in OCR 161 Controller used to interface with Q-Line modules.
PCRL card
Ovation IOIC card in OCR 161 Controller used to interface with local Ovation modules.
PCRR card
Ovation IOIC card in OCR 161 Controller used to interface with remote Ovation modules
and remote Q-Line modules in migrated systems.
Personality
module
Portion of an I/O module that provides a plastic housing with associated lenses and labeling.
It contains a printed circuit board to perform the necessary signal interconnections required
for interfacing the I/O modules to particular field devices.
Typically, the module contains only passive components, but the Media Attachment Unit
module and Remote Node Controller module contains fiber-optic transmitters, receivers, and
transceivers in their Personality modules. The module plugs directly into the base.
Point
A record in the global database containing a value (such as an input or output) and related
data.
Point name
Alphanumeric identifier associated with a point on the Ovation network (up to 24 characters
for Windows).
Port
Entry/exit mechanism in a node that can connect to the network cable and can connect to
another node.
Q-Line
Line of legacy Emerson I/O modules.
QOR Card
Remote Q-Line card (housed in a remote node Q-Crate) that permits remote nodes to be
interfaced to an Ovation Controller, through the use of fiber optic cable, an MAU, and a
PCRR card in the Ovation Controller.
Record
The set of data associated with a point, including the point name, System ID, value, status,
and various other fields, depending on the point record type.
Remote I/O
A configuration where the I/O is located remotely from the Controller.
Remote Node
A grouping of I/O modules that communicates with the Controller via media that can carry
control signals over a long distance (for example, fiber-optic).
Remote I/O
A configuration where the I/O is located remotely from the Controller.
RNC
Remote Node Controller (RNC) is an alternate name for the Ovation module containing the
Remote Node Electronics module and Remote Node Personality module. The RNC
interfaces the I/O modules in the Remote Node to an MAU module at the Controller via a
fiber-optic communication link.
Router
A hardware or software set-up that handles the connection between two or more networks.
SCSI
Small Computer System Interface, a peripheral-connect interface used to connect hard

drives, CDROM drives, and other storage devices to a computer.
REF_1005
TERM
DESCRIPTION
Server
A computer, or software program that provides a specific kind of service to client software
running on other computers.
Single attachment
Connection to one switch. A Single Attached Station (SAS) is a node that is connected to
one switch.
SNMP
Simple Network Management Protocol. Network management protocol of TCP/IP. Monitors

and reports about the activity in various devices on the network. This information is
maintained in a structure known as a management information block.
Software Server
A drop on a network that provides storage and control of system software files.
Station
Addressable node on Fast Ethernet network; can transmit and receive data.
Synchronous
High speed data communication that is time critical. Must be guaranteed service for nodes
transmitting synchronous data. Typically provided periodically.
System ID
System Identification number. The network reference number for each point which may be
transmitted.
Switch
Connects stations and/or LAN segments. Operates at Data Link Layer.
TCP/IP
Transmission Control Protocol / Internet Protocol, a set of communication protocols that

allows dissimilar computers to share information over a network.
Transition panels
Types are:
ROP - I/O transition panel.
TND - Remote Node transition panel.
RRP - Relay Base transition panel (top location).
RRB - Relay Base transition panel (bottom location).
Working area
Part of the Master Database that is used when working with the system. This is where all
interaction with the database takes place. This is the only part of the database that can be
edited.
Workstation
Windows-based computer that receives and sends data in order to perform any operations
needed to run a process. These workstations (drops) are typically connected to a switch,
which is, in turn, connected to the Ovation network.
REF_1005
1.3 What are the components of an Ovation system?
1.3
What are the components of an Ov ation s ystem?

Ovation is the control industrys most reliable and responsive real-time plant monitoring and
process control system using commercially available hardware platforms, operating systems and
network technology.
The Ovation system consists of different workstations that are linked to each other through a highspeed network. These workstations perform different functions and communicate the results of
these functions by sending data throughout the entire network. Therefore, each station on the
network is able to collect data and also to send out data when requested by other stations.
Ovation offers unique features to its users:
Transmits real-time data.
Detects, reports, or bypasses system faults.
Provides redundancy for all critical functions.
Since Ovation provides redundancy for the most important system elements (such as control), the
flow of data throughout the system is not interrupted by any single component, cable or device
failure. This redundancy helps prevent possible work stoppage.
The basic drops or functions used in an Ovation system are listed below and described briefly.
Ovation network
The Ovation network connects the components of the Ovation system so that all components can
communicate quickly and easily with each other. The Ovation Network is based on the standard
Fast Ethernet protocol, implemented in a robust, fail-safe, open design. This design provides for
easy, direct connection of third-party devices such as printers, WANs, LANs, Allen-Bradley PLCs,
GE Mark V/VI turbine controls, and other similar equipment that use Ethernet communications.
The network is media independent, allowing both fiber-optic and/or copper (UTP) implementation.
Ovation database
The Ovation database consists of a Master Database that uses the relational database software
package Oracle. This database contains system configuration, control algorithm information, and
the process point database. The Ovation database provides the capability to integrate and
organize the massive amounts of raw data in the system to create meaningful and valuable
information.
All programming tools and user interfaces store their data in the Ovation database, and that
information is transmitted to the control system. Application software and the control system can
be easily accessed via third party SQL (Structured Query Language) tools. This means that the
Ovation process control system data is open and accessible to all components of the Ovation
network that have permission to access the database data. (See Ovation Database User Guide.)
REF_1005
Ovation input/output modules

Ovation Input and Output (I/O) modules consist of modular, plug-in components that offer built-in
fault tolerance and system diagnostics. Ovation I/O modules convert input signals and create
output signals, which perform a multitude of functions. Specialized I/O modules are also available
for loop interfacing, serial linking, and pulse accumulating functions. These modules are typically
located in Ovation Controller cabinets, but they can also be installed in remote cabinets that are
up to 2,000 meters away from the Controller. (See Ovation I/O Reference Manual.)
Ovation Controller
The Ovation Controller is a process controller that is based on a commercially available operating
system. The Controller executes modulating and sequential control strategies and supports the
following functions:
Originates and receives process points.
Adds, deletes, and modifies points online.
Provides alarming and command word processing for originated points.
Reads I/O modules and converts data to process points.
Reads process points and writes data to I/O modules.
Executes control algorithms.
Adds, deletes, and modifies control online. (See Ovation Controller User Guide.)
Ovation Operator Station

The Ovation Operator Station drop provides communication with plant processes through the
Ovation network and monitors normal and abnormal plant conditions. A Distributed Database
(Raima) supports the Operator Station. This database is a subset of the information found in the
Master Database and contains only those data items necessary to support Operator Station
functions.
Several applications are included in the Operator Station functions:
Alarm System: Detects and displays abnormal plant conditions, such as drop time outs, points
out of range, digital state changes, etc.
Graphics Display or Process Diagram System: Displays graphic diagrams that represent the
actual plant process control equipment used to monitor and control the system.
Point Information (PI) System: Views and edits point information from the Ovation Network
and the Point Builder.
Error Log: Provides information about system errors and writes messages to a log file.
Point Review: Searches the database for points having specific characteristics or belonging to
a particular point group.
Trend: Displays data samples collected for live points on the Ovation Network in graphical or
tabular trends.
Signal diagrams: Displays diagrams created in the Control Builder that can be used at the
Operator Station to monitor and tune a control process.
Developer Studio (Windows)

The Engineering drop provides tools that are used for the development, configuration, and
maintenance of application and system software. These tools are known as Ovation Power Tools.
REF_1005

These Power Tools perform the following functions:
Define and configure your Ovation system.
Create, modify, and delete points.
Define the I/O modules used in an Ovation system.
Store values from algorithms (typically, for Special Functions and ladder applications).
Load control and originating point information into drops in an Ovation system. Links the
Master Database with other drops in the system.
Force Controller changes (online) into the database.
Create point groups used in trends or graphics.
Create, modify, and delete security objects and definitions.
Track changes made to the database.
Compare an external database with your Master Database.
Create control logic that runs on the Ovation Controller.
Create and edit system process diagrams that display on the Operator Station. (See Ovation
Developer Studio User Guide or Ovation Init and Admin Tools User Guide.)
Historical storage and reporting capabilities

Ovation Historians provide mass storage and retrieval of process data, alarms, sequence of
events (SOE), logs and operator actions in the Ovation process control system. Reports can then
be generated that provide meaningful information to operators, engineers, and maintenance
personnel. (See the applicable Ovation Historian User Guide.)
Third-party devices
Ovation provides the ability to reliably exchange information between the plant control system and
diverse third-party devices such as Allen-Bradley, GE Mark V/VI, Modbus, RTP I/O, Toshiba, and
MHI devices.
Connectivity products
Emerson connectivity products, such as Web Access View Enabler (WAVE), ODBC Server,
NetDDE Server, OPC Server, and SCADA Server connect the plant control system to corporate
networks. By integrating plant control and information systems, plants can develop new
applications including global process tuning, predictive control, neural networks, and process
analysis.
REF_1005
1.4 Planning the elements of an Ovation system
1.4
Planning the elements of an Ovation system

The planning and configuration of process control equipment within a specific Ovation system
determines the systems response to the controlled process. The system designer must have a
detailed and intimate knowledge of the specific process characteristics of that system and the
system equipment.
You can use many types of equipment in your Ovation system. Specific equipment can change as
new technology replaces existing technology. Emerson strives to provide the latest and best
equipment in an Ovation system.
Since each system is unique, it is not possible to provide definite installation rules that will fit
every situation. The project planner should consider the following when planning and designing
the system:
Equipment location (see page 11).

Use a site plan to determine relative locations (horizontally and vertically) of all equipment
rooms that contain drops.
Know the nature and location of any existing structured cable plant within the site facility.
Equipment specifications :
Ovation workstations (see page 393).
Number of workstations (up to 254).
Type of workstations.
Distribution of workstations.
Monitors (see page 402).
Keyboards (see page 406).
Printers (see page 408).
Storage devices for Ovation data (see page 412).
Ovation cabinets (see page 380).
Ovation Network guidelines (see page 40).
System-wide compatibility between cable (see page 73), switches, Controllers, workstations,
and peripherals.
Know the Electro-Magnetic Interference (EMI) and Radio Frequency Interference (RFI)
environment where cables will run. Factors that can disrupt the system:
Power failures.
Static discharge.
Conducted and radiated EMI.
Accidents and human error.
REF_1005
1.4 Planning the elements of an Ovation system
Inclusion of such items as cross-limits, interlocks, alarms, dealing with bad quality, and safety
control equipment.
Additional planning information is available in the Ovation User Guides and Reference manuals.
Also, refer to the commonly used standards and guidelines located in the following manuals:
System Configuration Reference Manuals
DOCUME NT NAME
DESCRIPTION
CSA Standard C22.2 Number 0.8-M1986

Safety Functions Incorporating
Electronic Technology
Prescribes guidelines for the design, evaluation, and testing of

electronic safety functions. It applies to individual electronic
components, assemblies and systems, including software and
hardware that perform safety functions.
Factory Mutual Engineering Corp.
Contains descriptions of, and recommendations for, electronic

programmable controllers used in process control systems and
industrial equipment. It includes installation and maintenance
practices, and methods of improving reliability with redundant
components and systems.
Loss Prevention Data

5-27/14-27
Factory Mutual Engineering Corp.
Loss Prevention Data 6-5
10
Contains descriptions of and recommendation for oil and gas-fired

multiple burner boilers.
Industrial Risk Insurers IR Information

P.3.8 Programmable Logic Controllers
for Use with Burner Management
Systems (April 3, 1987)
Provides guidance in evaluating the safety of programmable logic

controllers in burner management systems. It also provides
information regarding potential failures modes.
American National Standards

Institute/National Fire Protection
Association Standard ANSI/NFPA
Numbers 85A through 85I
Covers single and multiple burner boilers.
American National Standards

Institute/National Fire Protection
Association Standard ANSI/NFPA
Number 86C
Covers ovens and furnaces.
Any industry accepted manual describing

Fast Ethernet and Gigabit Ethernet
networks.
Covers different types of networks.
REF_1005
E C T I O N
Planning your Ovation equipment
IN THIS SECTION
Selecting equipment locations .......................................................................................... 11
Protecting the Ovation equipment ..................................................................................... 11
Electrical information for Ovation equipment .................................................................... 12
2.1
Selecting equipment locations

As part of initial system installation planning, you must select the permanent locations for Ovation
equipment. Generally, you should place the Ovation cabinets in groups, called clusters, to meet
grounding requirements. A cluster can be a Controller (drop) or remote I/O node.
Use facility architectural drawings as an aid to both planning and actual installation. While
selecting the permanent drop locations, also plan the following:
Determine the area to be used for receiving and unpacking the Ovation equipment (see page
211).
Note: Most Ovation equipment is designed to meet the industry standards for shock (IEC 68-26) and vibration (IEC-68-2-27).
2.2
If you plan to store the equipment prior to installation, determine an appropriate storage
location.
Reserve space for portable support and maintenance equipment at each drop location, and
designate a maintenance area for the facility.
Provide adequate space around each drop for access (including door swing) and airflow.
If the recommended access space is not available, make provisions to permit access (for
example, extra length service loop wiring and methods for moving the drop into an accessible
area).
Make sure all intake and exhaust ports are unobstructed, so that fans within the enclosures
will operate properly to provide forced-air cooling.
Protecting the Ovation equipment

You must be able to monitor and control temperature and humidity at storage sites and at the
equipments permanent location. Select or modify the equipment location to meet the following
criteria:
Make provisions to protect the Ovation equipment from the following:

Direct sunlight.
Weather (rain, snow, and so forth).
Lightning.
REF_1005
11
2.3 Electrical information for Ovation equipment

Dust.
ESD (Electrostatic Discharge).
EMI/RFI (Electro-Magnetic Interference/Radio Frequency Interference).
If harsh environmental conditions will be present, plan to use the optional sealed NEMA
enclosures (refer to ISA S71.04 for specifics on NEMA usage).
If combustible airborne material (such as gases, dust, or fibers) is present, plan installation in
accordance with process safety analysis and hazardous area classification. Assure a source
of clean air for ventilated cabinets.
If temperatures above those specified for a particular piece of equipment may occur, plan to
install auxiliary cooling or air conditioning. Optional enclosures are available with selfcontained air conditioning units.
The Ovation system requires a reliable power source with minimal voltage and frequency
fluctuations. Install wiring that is in accordance with accepted practices, as defined in the National
Electric Code.
2.3
Electrical information for Ovation equipment

The following sections provide tables containing electrical information for the Ovation equipment:
I/O cabinets (main/aux power and main/aux heat dissipation (drawn from AC/DC Mains
power) (see page 13).
Example of calculating power requirements for OCR400 Controller (see page 34).
Example of calculating power requirements for OCR161 Controller (see page 35).
Analog I/O modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
Mains power) (see page 15).
Bus interface modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
Digital I/O modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
Specialty I/O modules (main/aux power and main/aux heat dissipation) (drawn from AC/DC
Remote function modules (main/aux power and main/aux heat dissipation (drawn from AC/DC
You can also refer to Ovation equipment spec sheets (see page 379).
Note: All devices are subject to change as technology improves and evolves.
12
REF_1005
2.3.1 I/O cabinets (main/aux power and main/aux heat dissipation) (drawn from
AC/DC Mains power)
All Ovation I/O cabinet styles have the following voltage and frequency specifications:
Input voltages:
85 - 264 VAC (Line-Neutral configuration only) (CE Mark Certified).
90 -250 VDC .
Input frequency: 47 - 63 Hz.
The following table lists the power a component draws from the cabinets AC or DC Mains power
supply when the component is installed within the cabinet. Refer to Calculating Ovation main
power requirements (see page 34) in Planning your Ovation System for instructions on using
these values to calculate power requirements for populated Ovation I/O cabinets.
Refer to the applicable I/O module table for module power requirements.
Do NOT use the following table to determine the power drawn from the +24V Power Supply.
Refer to Calculating Ovation power supply requirements (see page 184) in Planning your Ovation
System.
CAUTION! Limit access to the inside of an Ovation cabinet to qualified, trained personnel only.
Electrical Specifications for Ovation I/O Cabinet Components

(power supply efficiency is included)
COMPONENT
EMERSON
PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN
HEAT
DISSIPATION
AUX
HEAT
DISSIPATION
Controller Cabinet (cabinet

+ power supply fans)
N/A
24 W/VA
N/A
82 BTUs/hr
N/A
Marshalling Cabinet
(cabinet + power supply
fans)
N/A
24 W/VA
N/A
82 BTUs/hr
N/A
Extended I/O Cabinet

fans)
N/A
24 W/VA
N/A
82 BTUs/hr
N/A
Remote I/O Cabinet

(ventilated) (cabinet +
power supply fans)
N/A
24 W/VA
N/A
82 BTUs/hr
N/A
Remote I/O Cabinet

(sealed) (cabinet + power
supply fans)
N/A
32 W/VA
N/A
EMC Controller Cabinet

fans)
N/A
24 W/VA
N/A
OCR161 or
OCR400 Controller
REF_1005
109.2
BTUs/hr
82 BTUs/hr
N/A
N/A
13
COMPONENT
EMERSON
PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN
HEAT
DISSIPATION
AUX
HEAT
DISSIPATION
EMC Extended I/O

Cabinet (cabinet + power
supply fans)
N/A
24 W/VA
N/A
82 BTUs/hr
N/A
EMC Remote I/O Cabinet

(ventilated) (cabinet +
power supply fans)
N/A
24 W/VA
N/A
82 BTUs/hr
N/A
EMC Remote I/O Cabinet

(sealed) (cabinet + power
supply fans)
N/A
32 W/VA
N/A
109.2
BTUs/hr
N/A
Single OCR161 Controller:
4D33942
G02
(hinged)
57.6 W/VA
N/A
196.5
BTUs/hr
N/A
115.2 W/VA
N/A
393 BTUs/hr
N/A
7.7 W/VA
N/A
26.3 BTUs/hr
N/A
5X00127
25 W/VA
N/A
85.4 BTUs/hr
N/A
5X00127
50 W/VA
N/A
170.8
BTUs/hr
N/A
1 Processor card
1 NIC card
1 IOIC card
1 Fan
Dual OCR 161 Controller:

2 Processor cards
2 NIC cards
2 IOIC cards
2 Fans
OR
4D33901G
02
4D33942
G01
(hinged)
OR
4D33901G
01
4D33943
G01-EMC
(hingd)
OR
4D33937G
01
Extra IOIC card in Dual

OCR161 Controller
3A99158
PCRL
3A99190
PCRR
3A99141
PCQL
Single OCR 400

Controller:
1 Processor card
1 IOIC card
1 Fan
2 Processor cards
2 IOIC cards
2 Fans
14
REF_1005
COMPONENT
EMERSON
PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN
HEAT
DISSIPATION
AUX
HEAT
DISSIPATION
Redundant Remote Node

Controller module (in
Remote Node Cabinet)
1C31203
(E)
16 W/VA
N/A
54.6 BTUs/hr
N/A
Redundant MAU module

(Controller cabinet)
1C31179
(E)
17.6 W/VA
N/A
60 BTUs/hr
N/A
1C31204G
01, G03
(P)
1C31181
G01-G04
(P)
2.3.2 Analog I/O modules (main/aux power and main/aux heat dissipation) (drawn
from AC/DC Mains power)
The following table lists the power a module draws from the cabinets AC or DC Mains power
supply when the component is installed within the cabinet. Refer to Calculating Ovation Main
Power Requirements (see page 34) for instructions on using these values to calculate power
requirements for populated Ovation I/O cabinets.
Note that (E) designates an Electronics module and (P) designates a Personality module.
Refer to Calculating Ovation Power Supply Requirements (drawn from +24V Main or Auxiliary
Power Supply) (see page 184) in Planning you Ovation System.
1
Electrical Information for Ovation Analog I/O Modules

(A 75% power supply efficiency is included)
COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Analog Input (13bit)
1C31113
G01-G06 (E)
3.4 W/VA
N/A
11.6 BTUs/hr
T/C, Volts and

Field Powered mA
1C31116G01,
G02, G04 (P)
N/A for
voltage input
channels.
REF_1005
0.41 BTUs/hr
per field
powered mA
channel.
15
COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
1C31113G05 (E)
3.4 W/VA
0.64 W/VA
per locally
powered
channel
1C31116G03 (P)
Local Powered mA
1C31224G02 (E)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
11.6 BTUs/hr
0.96 BTUs/hr
3
per locally
powered mA
channel
3.2 W/VA
Not Applicable
3.2 W/VA
0.64 W/VA
per locally
powered
channel. Not
applicable for
field-powered
channels.
10.9 BTUs/hr
N/A
10.9 BTUs/hr
0.41
3, 4
BTUs/hr
per field
powered
channel
1C31227G02 (P)
Volts (+/- 1 Volt)

1C31224G01 (E)
1C31227G01 (P)
Field and Local

Powered mA
0.96 BTUs/hr
3
per locally
powered
channel
Analog Input (14bit) (High Speed)
5X00070G02 (E)
3.2 W/VA
Not Applicable
10.9 BTUs/hr
N/A
3.2 W/VA
Not Applicable
10.9 BTUs/hr
N/A
3.2 W/VA
0.64 W/VA
per locally
powered
channel. Not
applicable for
field-powered
channels.
10.9 BTUs/hr
0.41
3, 4
BTUs/hr
per field
powered
channel
1C31227G02 (P)
( 100mV,
250mV, 1V Volt)
5X00070G03 (E)
1C31227G02 (P)
( 5V, 10V Volt)

5X00070G01 (E)
1C31227G01 (P)
Field and Local

Powered mA
0.96 BTUs/hr
3
per locally
powered
channel
Analog Input (14bit) (Medium
Speed)
5X00070G04 (E)
3.2 W/VA
Not Applicable
10.9 BTUs/hr
Not Applicable
1C31116G04 (P)
( 20mV, 50mV,
100V)
(Thermocouple)
16
REF_1005
COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION

Speed)
5X00070G05 (E)
3.2 W/VA
Not Applicable
10.9 BTUs/hr
Not Applicable
3.2 W/VA
Not Applicable
10.9 BTUs/hr
Not Applicable
3.2 W/VA
0.032 W/VA
per channel
10.9 BTUs/hr
0.028
3
BTUs/hr
per channel
3.2 W/VA
Not Applicable
10.9 BTUs/hr
0.001
4
BTUs/hr
per channel
1.6 W/VA
2.4 W/VA plus

3
0.64 W/VA
per locally
powered
channel.
5.5 BTUs/hr
8.2 BTUs/hr
plus 0.41
3, 4
BTUs/hr
per field
powered
channel
1C31116G04 (P)
( 20mV, 50mV,
100V)
(Thermocouple)
Speed)
5X00070G04 (E)
1C31116G01 (P)
( 20mV, 50mV,
100V)
5X00070G02 (E)
1C31116G03 (P)
( 1mA 2 wire local

powered)
5X00070G02 (E)
1C31116G02 (P)
( 1mA 4 wire field

powered)
HART Analog
Input
5X00058G01 (E)
5X00059G01 (P)
and
1.27 BTUs/hr
3
per locally
powered
channel
HART High
Performance
Analog Input
5X00106G01 (E)
5X00109G01 (P)
5.5 W/VA
0.64 W/VA per

locally powered
channel. Not
applicable for
field powered
channels.
18.77 BTUs/hr
0.41
3, 4
BTUs/hr
per field
powered
channel
0.96 BTUs/hr
3
per locally
powered
channel
REF_1005
17
COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
HART High
Performance
Analog Input
5X00106G02 (E)
5.5 W/VA
0.64 W/VA per

locally powered
channel. Not
applicable for
field powered
channels.
18.77 BTUs/hr
0.41
3, 4
BTUs/hr
per field
powered
channel
5X00109G01 (P)
0.96 BTUs/hr
3
per locally
powered
channel
Analog Output
(Voltage)
1C31129G01,
G02 (E)
2.7 W/VA
Not Applicable
9.2 BTUs/hr
Not Applicable
5.4 W/VA
Not Applicable
18.4 BTUs/hr
Not Applicable
1.6 W/VA
8 W/VA
5.5 BTUs/hr
27.2 BTUs/hr
6.08 W/VA
Not Applicable
20.74 BTUs/hr
Not Applicable
4.8 W/VA
Not Applicable
16.4 BTUs/hr
Not Applicable
4.8 W/VA
Not Applicable
16.4 BTUs/hr
Not Applicable
4.8 W/VA
Not Applicable
16.4 BTUs/hr
Not Applicable
4.8 W/VA
Not Applicable
16.4 BTUs/hr
Not Applicable
1C31129G05 (E)
(0 to 20MA
Redundant)
1C31132G01 (P)
Analog Output
(Current)
1C31129G03,
G04 (E)
1C31132G01 (P)
HART Analog
Output
5X00062G01 (E)
HART High
Performance
Analog Output
5X00167G01 (E)
RTD Input
1C31161G01 (E)
(4 channels)
1C31164G01 (P)
RTD Input
1C31161G02 (E)
(50Hz/60Hz
filtered inputs)
1C31164G02 (P)
5X00063G01 (P)
1X00188H01
(cavity insert)
(4 channels)
18
RTD Input
5X00119G01 (E)
(8 channels)
5X00121G01 (P)
RTD Input
5X00119G02 (E)
(8 channels)
5X00121G01 (P)
REF_1005
COMPONENT
1
2
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Refer to Q-Line Installation Manual for power consumption for Q-Line modules.
Due to power factor correction in Ovation power supplies, Power and VA are the same.
24V Aux power supply. Heat dissipated by the AI input transmitters is outside the cabinet and is not
included.
4
For Field Powered Channels. The heat dissipation is not due to the 24V Aux power supply, but to the
externally sourced input current. Heat dissipated by the field powered AI input transmitters is outside the
cabinet and is not included.
2.3.3 Bus interface modules

Note: For detailed information about bus interface modules, refer to the Ovation I/O Reference
Manual.
Power Supply (see page 184) in Planning you Ovation System.
Electrical Specifications for Ovation Bus Interface modules

COMPONENT
EMERSON
PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Foundation
Fieldbus
5X00301G01
(E)
2.4 W/VA
0.55 W/VA per

channel
8.16 BTUs/hr
Fieldbus heat
dissipation
5X00327G01
(P)
REF_1005
1.88 BTUs/hr per

channel
19
COMPONENT
EMERSON
PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Foundation
Fieldbus Power
Conditioner
1X00418H01
N/A
2.4 W/VA per

segment
N/A
8.16 BTUs/hr per

segment
Profibus
5X00300G01
(E)
5.1 W/VA
N/A
17.3 BTUs/hr
N/A
3.84 W/VA
0.77 W/VA per

channel
13.1 BTUs/hr
2.63 BTUs/hr per

channel
2.2 W/VA
N/A
7.51 BTUs/hr
N/A
5X00321G01
(P)
DeviceNet
5X00376G01
(E)
5X00375G01
(P)
Ethernet Link
Controller
20
5X00419 (E)
1X00569
(Cavity insert)
REF_1005
2.3.4 Digital I/O modules (main/aux power and main/aux heat dissipation) (drawn
from AC/DC Mains power)
Note that (E) designates an Electronics module, (P) designates a Personality module, and (R)
designates a Relay panel.
1
Electrical Information for Ovation Digital I/O Modules

COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX
POWER
(W) AND
2
VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Contact Input
1C31142G01 (E)
1C31110G03 (P)
6.1 W/VA
Not
Applicable
20.8 BTUs/hr
Not
Applicable
Compact Contact
Input
1C31234G01 (E)
1C31238H01 (Cavity
Insert)
6.1 W/VA
Not
Applicable
20.8 BTUs/hr
Not
Applicable
Digital Input
1C31107G01 (E)
1.5 W/VA
1.0 W/VA
(24V)
5.1 BTUs/hr
3.4 BTUs/hr
(24V)
24VDC/48VDC
1C31110G01, G02
(P)
6.8 BTUs/hr
(48V)
2.0 W/VA
(48V)
Digital Input
125VDC
1C31107G02 (E)
1C31110G01, G02
(P)
1.5 W/VA
Not
4
Applicable
5.1 BTUs/hr
11.26
5
BTUs/hr
Compact Digital
Input
1C31232G01 (E)
1.5 W/VA
0.87 W.VA
(24V)
5.1 BTUs/hr
2.98BTUs/hr
(24V)
24/48VDC singleended inputs with

common return
1C31238H01 (cavity
insert)
REF_1005
2.33 W/VA
(48V)
7.95 BTUs/hr
(48V)
21
COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX
POWER
(W) AND
2
VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Compact Digital
Input
1C31232G02 (E)
1.5 W/VA
0.92 W/VA
(24V)
5.1 BTUs/hr
3.14 BTUs/hr
(24V)
24/48VAC/VDC
isolated differential
inputs
1C31238H01 (cavity
insert)
Compact Digital
Input
1C31232G02 (E)
24/48VAC/VDC
individually fused
inputs with
common power
supply
5X00034G01 (P)
Compact Digital
Input
1C31232G03 (E)
125VAC/VDC
isolated differential
inputs
1C31238H01 (cavity
insert)
Compact Digital
Input
1C31232G03 (E)
125VAC/VDC
individually fused
inputs with
common power
supply
5X00034G01 (P)
Digital Output
1C31122G01 (E)
(no relay panel)
1C31125G01 (P)
2.33 W/VA
(48V)
1.5 W/VA
7.95 BTUs/hr
(48V)
0.92 W/VA
(24V)
5.1 BTUs/hr
2.33 W/VA
(48V)
3.14 BTUs/hr
(24V)
7.95 BTUs/hr
(48V)
1.5 W/VA
Not
4
Applicable
5.1 BTUs/hr
17.4 BTUs/hr
1.5 W/VA
Not
4
Applicable
5.1 BTUs/hr
17.4 BTUs/hr
3.0 W/VA
25.6 W/VA
(24V Aux)
10.3 BTUs/hr
22.38
3
BTUs/hr
51.2 W/VA
(48V Aux)
(24V Aux)
44.56
3
BTUs/hr
(48V Aux)
Digital Output plus
1C31122G01 (E)
Solid State Relay

Panel (16 relays)
1C31125G02 (P)
3.0 W/VA
7.87 W/VA
(16 outputs
on)
10.3 BTUs/hr
26.8 BTUs/hr
(24V Aux)
5A22410G01 (R) AC
contacts
6.9 BTUs/hr
or
(24V Aux)
5A22410G02 (R) DC
contacts
22
REF_1005
COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX
POWER
(W) AND
2
VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Digital Output plus
1C31122G01 (E)
3.0 W/VA
10.3 BTUs/hr
20.3 BTUs/hr
Solid State Relay

Panel (16 relays)
1C31125G03 (P)
Not
applicable
(16 outputs
on)
5A22410G01 (R) AC
contacts
(24V Aux)
0.18 BTUs/hr
(24V Aux)
or
5A22410G02 (R) DC
contacts
Digital Output plus
1C31122G01 (E)
G2R Style Panel

(16 relays)
1C31125G02 (P)
3.0 W/VA
14.5 W/VA
(16 outputs
on)
10.3 BTUs/hr
49.47
8
BTUs/hr
(24V Aux)
5A22411G01 (R)
12.72
9
BTUs/hr
(24V Aux)
Digital Output plus
1C31122G01 (E)
G2R Style Panel

(16 relays)
1C31125G03 (P)
3.0 W/VA
5A22411G01 (R)
Not
applicable
(16 outputs
on)
10.3 BTUs/hr
37.43
8
BTUs/hr
(24V Aux)
0.34 BTUs/hr
(24V Aux)
Digital Output plus
1C31122G01 (E)
KUEP Style Panel

(8 Form C relays)
1C31125G02 (P)
3.0 W/VA
21.12 W/VA
(8 outputs
on)
10.3 BTUs/hr
72.06
8
BTUs/hr
(24V Aux)
5A22412G01 (R)
18.53
9
BTUs/hr
(24V Aux)
Digital Output plus
1C31122G01 (E)
KUEP Style Panel

(8 Form C relays)
1C31125G03 (P)
3.0 W/VA
Not
applicable (8
outputs on)
10.3 BTUs/hr
54.55
8
BTUs/hr
(24V Aux)
5A22412G01 (R)
0.51 BTUs/hr
(24V Aux)
Digital Output plus
two
KUEP Style
Panels (2 x 8
Form C relays)
1C31122G01 (E)
1C31125G02 (P)
5A22412G01 (R)
3.0 W/VA
42.24 W/VA
(16 outputs
on)
10.3 BTUs/hr
144.12
8
BTUs/hr
(24V Aux)
37.16
9
BTUs/hr
(24V Aux)
REF_1005
23
COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX
POWER
(W) AND
2
VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Digital Output plus

two
1C31122G01 (E)
3.0 W/VA
Not
applicable
(16 outputs
on)
10.3 BTUs/hr
109.21
8
BTUs/hr
KUEP Style
Panels (2 x 8
Form C relays)
1C31125G03 (P)
5A22412G01 (R)
(24V Aux)
1.12 BTUs/hr
(24V Aux)
Digital Output plus
1C31122G01 (E)
KUEP Style Panel

(8 Form X relays)
1C31125G02 (P)
3.0 W/VA
15.04 W/VA
(8 outputs
on)
10.3 BTUs/hr
51.32
8
BTUs/hr
(24V Aux)
5A22412G02 (R)
13.18
9
BTUs/hr
(24V Aux)
Digital Output plus
1C31122G01 (E)
KUEP Style Panel

(8 Form X relays)
1C31125G03 (P)
3.0 W/VA
Not
applicable (8
outputs on)
10.3 BTUs/hr
38.84
8
BTUs/hr
(24V Aux)
5A22412G02 (R)
0.35 BTUs/hr
(24V Aux)
Digital Output plus
two
KUEP Style
Panels (2 x 8
Form X relays)
1C31122G01 (E)
3.0 W/VA
1C31125G02 (P)
30.08 W/VA
(16 outputs
on)
10.3 BTUs/hr
102.63
8
BTUs/hr
(24V Aux)
5A22412G02 (R)
26.4 BTUs/hr
(24V Aux)
Digital Output plus
two
KUEP Style
Panels (2 x 8
Form X relays)
1C31122G01 (E)
3.0 W/VA
1C31125G03 (P)
5A22412G02 (R)
Not
applicable
(16 outputs
on)
10.3 BTUs/hr
77.72
8
BTUs/hr
(24V Aux)
0.75 BTUs/hr
(24V Aux)
5X00270G01 (E)
High Side Digital
6
Output
24
5X00273G01 (P)
2.88 W/VA
64W/VA
9.83 BTUs/hr
13.65
7
BTUs/hr
REF_1005
COMPONENT
Relay Output
module (E) plus
base with
EMERSON PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX
POWER
(W) AND
2
VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
1C31219G01 (E)
2.54 W/VA
(E)
0.39 W/VA
(E)
8.66 BTUs/hr
1.33 BTUs/hr
(E)
Base not
applicable
+ 12.3 W/VA
+ 42 BTUs/hr
(base + 16
relays)
(base + 16
relays)
----------------
----------------
= 12.69
W/VA
= 43.33 W/VA
1C31223G01 (Base)
16 G2R relays
Relay Output
module (E) plus
base with 12
KUEP Form C
Relays added
Relay Output
module (E) plus
base with 12
KUEP Form X
Relays added
1C31219G01 (E)
1C31222G01 (Base)
1C31219G01 (E)
1C31222G01 (Base)
Sequence of
Events
1C31157G01 (E)
24VDC/48VDC
1C31110G01, G02
(P)
Digital Input
Sequence of
Events
125VDC Digital
Input
Sequence of
Events
48V Contact Input
On-card
REF_1005
1C31157G02 (E)
2.54 W/VA
(E)
0.39 W/VA
(E)
Base not
applicable
+ 31.66
W/VA
+ 108
BTUs/hr
(base + 12
relays)
(base + 12
relays)
----------------
----------------
= 32.05
W/VA
= 109.33
W/VA
0.39 W/VA
(E)
Base not
applicable
+ 21.46
W/VA
+ 73.22
BTUs/hr
(base + 16
relays)
(base + 12
relays)
----------------
----------------
= 21.85
W/VA
= 74.55 W/VA
2.0 W/VA
1.5 W/VA (E)
8.66 BTUs/hr
1.33 BTUs/hr
(E)
2.54 W/VA
(E)
6.8 BTUs/hr
1.33 BTUs/hr
(E)
5.1 BTUs/hr
(24V)
(24V)
3.0 W/VA
10.2 BTUs/hr
(48V)
(48V)
5
2.0 W/VA
Not
4
Applicable
6.8 BTUs/hr
11.26
BTUs/hr
6.1 W/VA
Not
Applicable
20.8 BTUs/hr
Not
Applicable
1C31110G01, G02
(P)
1C31157G03 (E)
1C31110G03 (P)
8.66 BTUs/hr
25
COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX
POWER
(W) AND
2
VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Compact Seq. of
Events
1C31233G01 (E)
2.0 W/VA
0.88 W/VA
(24V)
6.8 BTUs/hr
3.0 BTUs/hr
(24V)
24/48VDC singleended digital

inputs with
common return
1C31238H01 (cavity
insert)
Compact Seq. of
Events
1C31233G02 (E)
24/48VDC isolated
differential digital
inputs
Compact Seq. of
Events
2.27 W/VA
(48V)
2.0 W/VA
1C31238H01 (cavity
insert)
1C31233G02 (E)
125VDC isolated
inputs
Compact Seq. of
Events
6.8 BTUs/hr
2.27 W/VA
(48V)
2.0 W/VA
5X00034G01 (P)
24/48 VDC
individually fused
digital inputs with
common power
supply
Compact Seq. of
Events
0.88 W/VA
(24V)
7.74 BTUs/hr
(48V)
0.88 W/VA
(24V)
7.74 BTUs/hr
(48V)
6.8 BTUs/hr
2.27 W/VA
(48V)
1C31233G03 (E)
3.0 BTUs/hr
(24V)
7.74 BTUs/hr
(48V)
2.0 W/VA
Not
4
Applicable
6.8 BTUs/hr
14.5 BTUs/hr
2.0 W/VA
Not
4
Applicable
6.8 BTUs/hr
14.5 BTUs/hr
6.1 W/VA
Not
Applicable
20.8 BTUs/hr
Not
Applicable
2.47 W/VA
0.93 W/VA
(24V)
8.43 BTUs/hr
3.17 BTUs/hr
(24V)
1C31238H01 (cavity
insert)
1C31233G03 (E)
3.0 BTUs/hr
(24V)
5X00034G01 (P)
125VDC
individually fused
digital inputs with
common power
supply
Compact Seq. of
Events
Contact Input
Enhanced
Compact Seq. of
Events
24/48 VDC singleended digital
inputs with
common return
26
1C31233G04 (E)
1C31238H01 (cavity
insert)
5X00357G01 (E)
1C31238H01 (cavity
insert)
1.86 W/VA
(48V)
6.35 BTUs/hr
(48V)
REF_1005
COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX
POWER
(W) AND
2
VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Enhanced
Compact Seq. of
Events
5X00357G02 (E)
2.01 W/VA
0.87 W/VA
(24V)
6.88 BTUs/hr
2.97 BTUs/hr
(24V)
1C31238H01 (cavity
insert)
1.73 W/VA
(48V)
24/48VDC isolated
inputs
Enhanced
Compact Seq. of
Events
5X00357G02 (E)
2.01 W/VA
5X00034G01 (P)
6.88 BTUs/hr
1.73 W/VA
(48V)
24/48 VDC single

ended individually
fused digital inputs
with common
power supply
Enhanced
Compact Seq. of
Events
0.87 W/VA
(24V)
5.94 BTUs/hr
(48V)
5X00357G03 (E)
2.97 BTUs/hr
(24V)
5.94 BTUs/hr
(48V)
1.99 W/VA
Not
4
Applicable
6.78 BTUs/hr
6.4 BTUs/hr
1.99 W/VA
Not
4
Applicable
6.78 BTUs/hr
6.4 BTUs/hr
5.51 W/VA
Not
Applicable
18.79
BTUs/hr
Not
Applicable
2.4 W/VA
2.85 W/VA
8.19 BTUs/hr
9.74 BTUs/hr
1C31238H01 (cavity
insert)
125 VDC isolated

inputs
Enhanced
Compact Seq. of
Events
5X00357G03 (E)
5X00034G01 (P)
125 VDC single

ended individually
with common
power supply
Enhanced
Compact Seq. of
Events
5X00357G04 (E)
1C31238H01 (cavity
insert)
48 VDC contact
input
Enhanced
Compact Seq. of
Events
5X00357G05 (E)
1C31238H01 (cavity
insert)
24 VDC isolated
inputs
REF_1005
27
COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX
POWER
(W) AND
2
VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Enhanced
Compact Seq. of
Events
5X00357G05 (E)
2.4 W/VA
2.85 W/VA
8.19 BTUs/hr
9.74 BTUs/hr
5X00034G01 (P)
24 VDC single
ended individually
with common
power supply
1
2
Loads are located outside the cabinet. Their heat dissipation is not included. Eight outputs on @ 100 mA
per output.
4
Assumes that the 125VAC or 125VDC power source is located outside the Ovation I/O cabinet.
5
Heat dissipation is due solely to the I/O module front-end circuit external power consumption.
Module standard configuration employs an external +24 VDC power supply for field power and does not
use auxiliary power. You may optionally use auxiliary power to provide module field power, but then the
module allowable maximum total load current is reduced to 2 A.
7
Assume eight outputs on and eight outputs off with the on outputs supplying 250 mA each.
8
9
28
Relay panels located inside Ovation I/O cabinet.

Relay panel located outside Ovation I/O cabinet and its heat dissipation is not included.
REF_1005
2.3.5 Specialty I/O modules (main/aux power and main/aux heat dissipation)
(drawn from AC/DC Mains power)
1
Electrical Information for Ovation Specialty I/O Modules

COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Link Controller
For RS232:
3.9 W/VA
Not Applicable
13.3 BTUs/hr
Not Applicable
1C31166G01
(E)
1C31169G01
(P)
For RS485/422:
1C31166G01
(E)
1C31169G02
(P)
REF_1005
29
COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Loop Interface
1C31174GX1,
GX2 (E)
3.6 W/VA
When used:
12.3 BTUs/hr
When used:
13-bit Voltage AI
(E) GX1 = 0 to
10V
(E) GX2 = 0 to 5
V
12-bit Voltage AO
0 to 10V
(X = 0 or 2)
1C31177G01
(P)
Digital Inputs
Digital Inputs
(X = 0 or 2)
0.18W/VA
(24V)
0.6 BTUs/hr
(24V)
0.36W/VA
(48V)
1.2 BTUs/hr
(48V)
Digital
Outputs
Digital Output
(100mA per
output)
6.4 W/VA
(24V)
12.8W/VA
(48V) Not
applicable for
voltage analog
inputs
30
(100mA per
output)
5.6 BTUs/hr
(24V)
11BTUs/hr (48V)
Not applicable for
voltage analog
inputs
REF_1005
COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Loop Interface
1C31174GX3,
GX4 (E)
3.6 W/VA
When used:
12.3 BTUs/h
When used:
13-bit 4-20mA
Current AI
(P) G02 = local
power
1C31177G02,
G03 (P)
Digital Inputs
Digital Inputs
(X = 0 or 2)
0.18W/VA
(24V)
0.6 BTUs/hr
(24V)
0.36W/VA
(48V)
1.2 BTUs/hr
(48V)
Digital
Outputs
Digital Output
(P) G03 = field

power
12-bit 4-20mA
Current AO
(100mA per
output)
(100mA per
output)
(E) GX3
No AO
5.6 BTUs/hr
(24V)
6.4 W/VA
(24V)
(E) GX4
11 BTUs/hr (48V)
12.8 W/VA
(48V)
(X = 0 or 2)
Local Powered
Current Analog
3
Inputs
Local
Powered
Current
Analog Inputs
Only
(2 inputs @
20mA per input)
1.91BTUs/hr
(24V)
(20mA per
input)
Field Powered
Current Analog
7
Inputs
1.28W/VA
(24V)
(2 inputs @
20mA per input)
0.82 BTUs/hr
(24V)
Pulse
Accumulator
1C31147G01
(E)
24/48 VDC Count

Inputs
1C31150G01G02 (P)
2.2 W/VA
When used:
Both count
inputs = 50%
duty cycle
0.23 W/VA
(24V)
0.47 W/VA
(48V)
7.51 BTUs/hr
When used:
Both count inputs
= 50% duty cycle
0.78 BTUs/hr
(24V)
1.6 BTUs/hr
(48V)
Not applicable
for 12V/5V
count inputs
REF_1005
31
COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Pulse
Accumulator
1C31147G01
(E)
2.2 W/VA
Not Applicable
7.51 BTUs/hr
24/48 VDC Count

Inputs
1C31150G03
(P)
When used: Both

count inputs =
50% duty cycle
0.58 BTUs/hr
8
(24V)
1.19 BTUs/hr
8
(48V)
Pulse
Accumulator
1C31147G02
(E)
High Speed
1C31150G01G03 (P)
+5V Count Inputs

Servo Driver
DC LVDT
1C31199G01
(E)
2.2 W/VA
Not Applicable
7.51 BTUs/hr
0.68 BTUs/hr
Both high speed

count inputs =
50% duty cycle
9.0 W/VA
Not Applicable
30.7 BTUs/hr
Not Applicable
7.1 W/VA
Not Applicable
24.2 BTUs/hr
Not Applicable
4D33741G01G03
4.8 W/VA
Not Applicable
16.4 BTUs/hr
Not Applicable
1C31189G01
(E)
6.4 W/VA
Not Applicable
21.8 BTUs/hr
Not Applicable
5.8 W/VA
Digital Input
19.8 BTUs/hr
Digital Input
1C31201G01
(P)
Servo Driver
AC LVT
1C31199G02,
G03 (E)
1C31201G02
(P)
SLIM
Speed Detector
1C31192G01
(P)
Valve Positioner
1C31194G01,
G02 (E)
1C31197G01G04 (P)
0.12W/VA
(24VDC)
0.41 BTUs/hr
(24V)
0.24W/VA
(48VDC)
0.82 BTUs/hr
(48V)
Digital Output
Digital Output
(100mA load)
2.79 BTUs/hr
(24V)
3.2W/VA
(24VDC)
6.4W/VA
(48VDC)
32
5.53 BTUs/hr
(48V)
REF_1005
COMPONENT
1
2
EMERSON
PART NUMBE R
MAIN +24
POWER
(W) AND
VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
24V Aux power supply. Heat dissipated by the AI input transmitters is outside the cabinet and is not
included.
4
Loads are located outside the cabinet. Their head dissipation is not included. Two outputs on @100 mA
per output.
5
SLIM is not located in the Ovation I/O cabinet and is not powered by an Ovation power supply. It is listed
here as a convenience for determining system power requirements.
6
The load is located outside the cabinet and its heat dissipation is not included.
For Field Powered Channels. The heat dissipation is not due to the 24V Aux power supply, but to the
externally sourced input current. Heat dissipated by the field powered AI input transmitters is outside the
8
Heat dissipation is due solely to the I/O module front-end circuit external power consumption.
2.3.6 Remote function modules (main/aux power and main/aux heat dissipation)
(drawn from AC/DC Mains power)
1
Electrical Specifications for Ovation Remote Function Modules

COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER (W)
AND VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
Redundant
Remote Node
Controller module
(in Remote Node
1C31203 (E)
16 W/VA
Not Applicable
54.6 BTUs/hr
Not
Applicable
REF_1005
1C31204G01,
G03 (P)
33
COMPONENT
EMERSON
PART NUMBE R
MAIN +24
POWER (W)
AND VA
(TYPICAL)
AUX POWER
2
(W) AND VA
(TYPICAL)
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
1C31179 (E)
17.6 W/VA
Not Applicable
60 BTUs/hr
Not
Applicable
Cabinet)
Redundant MAU
module
(in Controller
cabinet)
1C31181G01G04 (P)
2.3.7 Calculating Ovation main power requirements for OCR400 Controller

You can calculate the Power (VA) requirements for a specific Ovation cabinet by adding the
Power (VA) values for the cabinet components (such as Controller (see page 13) and modules
(see page 413)), plus the Power (VA) values for the Auxiliary (AUX) supplies.
In this example, the Ovation I/O cabinet configuration consists of the following:
Controller Cabinet (Main: 24 W).
Dual Controller (Main: 50 W).
16 Analog Input T/C modules (Main: 3.4 W per module).
16 Analog Input modules - System Powered 4-20 mA (Main:3.4 W per module;

AUX: 5.2 W per module).
Refer to the following table for the figures used in the calculation:
1. Add the Main (182.8 W/VA) and AUX (83.2 W/VA) Power totals = 266 W/VA total power
needed from the AC or DC Mains.
2. Add the Main (624.6 BTU) and AUX (113.6 BTU) Heat Dissipation = 636.2 BTUs/hr heat
dissipation inside the cabinet.
Power Calculation Example
I/O CABINET
COMPONENT
MAIN
2
POWER
AUX
POWER
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
COLD START
INRUSH CURRENT
3
Cabinet
24 W/VA
N/A
82 BTUs/hr
N/A
N/A
Dual Controller
50 W/VA
N/A
170.8 BTUs/hr
N/A
65 amps (230 VAC)

33 amps (115 VAC)
25 amps (125 VDC)
34
16 AI modules
- T/C
54.4 W/VA
N/A
185.6 BTUs/hr
16 AI modules
- 4-20 mA
54.4 W/VA
83.2 W/VA
185.6 BTUs/hr
N/A
113.6
BTUs/hr
N/A
N/A
REF_1005
I/O CABINET
COMPONENT
Total
MAIN
2
POWER
AUX
POWER
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
COLD START
INRUSH CURRENT
3
182.8 W/VA
83.2 W/VA
624.6
BTUs/hr
113.6
BTUs/hr
N/A
The values used in this table are taken from Electrical Information for Ovation Equipment (see page 12)
(drawn from AC or DC Mains power).
2
3
The VA rating is the same as the Watts due to the Ovation power supply power correction.
These values assume a 60 second minimum delay after powering down the Controller before power-up.
2.3.8 Calculating Ovation main power requirements for OCR161 Controller

You can calculate the Power (VA) requirements for a specific Ovation cabinet by adding the
Power (VA) values for the cabinet components (such as Controller (see page 13) and modules
(see page 413)), plus the Power (VA) values for the Auxiliary (AUX) supplies.
In this example, the Ovation I/O cabinet configuration consists of the following:
Controller Cabinet (Main: 24 W).
Dual Controller (Main: 115.2 W).
16 Analog Input T/C modules (Main: 3.4 W per module).
16 Analog Input modules - System Powered 4-20 mA (Main:3.4 W per module;

AUX: 5.2 W per module).
Refer to the following table for the figures used in the calculation:
1. Add the Main (248 W/VA) and AUX (83.2 W/VA) Power totals = 331.2 W/VA total power
needed from the AC or DC Mains.
2. Add the Main (846.2 BTU) and AUX (113.6 BTU) Heat Dissipation = 959.8 BTUs/hr heat
dissipation inside the cabinet.
Power Calculation Example
I/O CABINET
COMPONENT
Cabinet
Dual Controller
MAIN
2
POWER
AUX
POWER
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
24 W/VA
N/A
82 BTUs/hr
N/A
115.2 W/VA
N/A
393 BTUs/hr
N/A
COLD START
INRUSH
3
CURRENT
N/A
65 amps (230
VAC)
33 amps (115
VAC)
25 amps (125
VDC)
16 AI modules T/C
REF_1005
54.4 W/VA
N/A
185.6
BTUs/hr
N/A
N/A
35
I/O CABINET
COMPONENT
MAIN
2
POWER
AUX
POWER
MAIN HEAT
DISSIPATION
AUX HEAT
DISSIPATION
COLD START
INRUSH
3
CURRENT
16 AI modules - 420 mA
54.4 W/VA
83.2 W/VA
185.6
BTUs/hr
113.6
BTUs/hr
N/A
Total
248 W/VA
83.2 W/VA
846.2
BTUs/hr
113.6
BTUs/hr
N/A
The values used in this table are taken from Electrical Information for Ovation Equipment (see page
12) (drawn from AC or DC Mains power).
2
The VA rating is the same as the Watts due to the Ovation power supply power correction.
These values assume a 60 second minimum delay after powering down the Controller before powerup.
36
REF_1005
E C T I O N
Planning your Ovation network
IN THIS SECTION
What is the Ovation network? ........................................................................................... 38
Network terminology ......................................................................................................... 38
Network planning guidelines for Ovation systems ............................................................ 40
Preventing data collisions ................................................................................................. 41
Using Ethernet switches to provide network stability ........................................................ 41
OSI Seven-Layer Model .................................................................................................... 45
Fast Ethernet network configurations................................................................................ 47
Cable connection types for your network .......................................................................... 48
Single-tier network arrangement ....................................................................................... 50
Two-tier network arrangement .......................................................................................... 51
Connecting workstations to your Ovation network ............................................................ 52
Connecting Ovation devices to your Ovation network ...................................................... 57
Connecting non-Ovation devices to your Ovation network ............................................... 58
REF_1005
37
3.1 What is the Ovation network?
3.1
What is the Ovation netw ork?

The Ovation network connects the components of the Ovation system so that all components can
communicate quickly and easily with each other. In order to provide the latest networking
technology advances, the Ovation network is based on the standard Ethernet protocols, and
implemented in a robust, fault tolerant, open design.
Ethernet has evolved to become the industry standard of network technology. Current commonly
available, commercial network products support the following performance levels:
Ethernet
10Mbps
FastEthernet
100Mbps
Gigabit Ethernet
1,000Mbps
10 Gigabit Ethernet 10,000Mbps
Emerson has designed the Ovation network strictly within the applicable IEEE 802.x standards in
order to incorporate the latest cost-effective networking technologies.
This design provides for easy connection of workstations (drops), third-party devices, and other
equipment to the Ethernet network.
The Ovation network is media independent, allowing both fiber-optic and/or copper (UTP)
implementation. Media converters convert data transmissions between copper cable and fiberoptic cable so that data can flow seamlessly over the network.
Unlike some proprietary designs based on customized Ethernet protocol, Ovation adheres to the
IEEE standards.
The Ovation network design prevents data collisions (see page 41) and provides network stability
(see page 41).
3.2
38
Netw ork terminology

TERM
DESCRIPTION
Backup Root Switch
The backup root takes over functions of the root switch in the event of a root failure. If the
root fails, backup-root switches can accept switch and drop connections. Groups 3, 7, 9,
and 13 in the switch configuration file example (see page 42) are examples of backup
root switches.
Channel-Group Port
Channel-Group ports are only used on root and backup root groups. These ports provide
a redundant connection between the root and backup root. Groups 2 and 3 in the switch
configuration file example (see page 42) are examples of channel group ports. If a Root
is used in a non-redundant configuration, these ports cannot be used to connect any
device.
Destination Monitor
Port
Can only be used to monitor traffic transmitted and received on the source monitor
port(s). Any traffic received on this port from the connected device is discarded. Thus,
the device connected to this port has no network connectivity; it can only monitor traffic.
A destination monitor port is only provided on an I/O device switch.
REF_1005
3.2 Network terminology
TERM
DESCRIPTION
Fanout Area Switches
The fanout switch is at the edge of the network. Deployed in a pair called PrimaryPartner, the fanout area switches provide connectivity to drops in areas distant from the
root. Groups 4 and 5 in the switch configuration file example (see page 42) are examples
of primary and partner fanout area switches, respectively. Fanout area switches can
accept drop connections and a connection from the root and backup root. Fanout area
switches are connected to each other via the fanout cross-connect ports, although in
normal operation, this connection does not carry any traffic.
Fanout CrossConnect Port
This port can only be used to connect between primary and partner switches. It provides
an alternate communications path in the event a fanout switch pair is isolated from the
root and backup root.
I/O Device Switches
The I/O device switch accepts connections from various field devices that are not
connected to the Ovation network. The I/O device switch employs a separate VLAN to
isolates all connected devices from the Ovation network. One port is used to connect the
I/O device switch to the Ovation network only for management. Two ports are used to
chain I/O device switches to one another.
I/O Device Port
Can only be connected to field devices, PLCs, and related I/O equipment. I/O device
ports have no direct connectivity to the Ovation network; these ports are in a different
VLAN than the Ovation network. Any communication to the Ovation network from the I/O
device port requires a router or other device that must perform routing functions. I/O
device ports are configured only on I/O device switches.
IP-Only Port
The IP-only port on root and fanout switches allows ancillary devices to be directly
connected to the Ovation network. Examples of ancillary devices are unmanaged
switches, hubs, printers, GPS devices, and PLCs.
IP Switch
Ovation provides two managed switch styles for connecting ancillary devices to Ovation
networks. The IP-only switch connects to an IP-only port on a root or fanout switch to
accept connections from ancillary devices. Group 1 in the switch configuration file
example (see page 42) is an example of an IP-only switch. The IP-traffic switch connects
redundantly to a root and backup root switch (for example; a fanout switch). Group 10 is
an IP-only switch which also accepts connections from ancillary devices. Group 10 in the
switch configuration file example (see page 42) is an example of an IP-traffic switch.
IP-Uplink Port
Can only be used to connect an IP-only traffic switch to an IP-only port. This type exists
only on a Group 1 IP-traffic switch.
Managed Switches
A managed switch can be configured and monitored via standard network tools such as
SNMP to Ovation.
Ovation Drop Port
Can only be used to connect Ovation drops. Ovation drop ports exist on most root and all
fanout switch configurations.
Ovation Management
Port
Can only be used to connect an I/O device switch to an Ovation drop port. This permits
the I/O device switch to be managed from the Ovation network while isolating all other
connected devices from the Ovation network.
Root switch
The root is the center of the network. All Ovation drops and switches have a path to the
root. The root forms the distribution hub for all traffic not local to a fanout switch. Groups
2, 6, 8, and 12 in the switch configuration file example (see page 42) are examples of
root switches. Root switches can accept switch and drop connections.
Root Switch Port
These are the ports on a root or backup root switch that are reserved for connecting to a
fanout or IP traffic switch. Root switch ports only exist on root and backup root
configurations
Source Monitor Port
An I/O device port which is configured to mirror traffic to the destination monitor port. The
normal I/O device port function is preserved; the mirroring of traffic is transparent to the
connected device. A source monitor port is only provided on an I/O device switch.
Switch
Connects stations and/or LAN segments. Operates at the data link layer.
REF_1005
39
3.3 Network planning guidelines for Ovation systems
3.3
TERM
DESCRIPTION
Switch Chaining Port
Can only be used to connect one I/O device switch to another I/O device switch.
Switch Uplink Port
This is the uplink port on a Fanout or IP-traffic switch that is used to connect to the root
or backup root switches.
Unmanaged Switch
An unmanaged switch is one which cannot be configured or monitored. It automatically

configures each ports speed and duplex via auto-negotiation. It does not record or
provide any status information.
Netw ork planning guidelines for Ovation s ystems

As you plan and design your Ovation network, observe the following guidelines for your proposed
network:
1. Know the number of drops you plan to connect to your Ovation network. You can connect up
to 254 drops.
2. Know the types of drops your Ovation system needs.
3. Know how you will distribute and connect the Ovation drops to your network.
4. Make sure you can access a site plan that describes the relative locations (horizontally and
vertically) of all equipment rooms containing Ovation drops.
5. Know what Electro-Magnetic Interference (EMI) and Radio Frequency Interference (RFI)
environment the network cable will run through.
6. Know what types of network switches you will use. Use only switches (see page 42) that are
approved by Emerson.
7. Know the types of network configurations you will use. Use only configurations that are
defined by Emerson.
8. Make sure you use switch connections that are valid for your Ovation network schema.
Connect hubs and unmanaged switches to the IP traffic-only port (normally Port 1) of the
Ovation switches to allow multiple printers and other third-party devices to be connected.
Connect only the following equipment to the DCS network switches (except the IP trafficonly port - typically Port 1):
Ovation Controllers.
Ovation Windows-based Workstations.
Approved network switches and routers.
40
REF_1005
3.4 Preventing data collisions
3.4
Preventing data collisions

Data collisions occur when two or more nodes on the network try to transmit data at the same
time.
Ovation employs intelligent network switches that support simultaneous, full-duplex
communications on all switch ports. When a switch receives concurrent messages from multiple
ports that are destined to be output to the same port(s), the messages are buffered (stored)
internally. The messages are then transmitted to the destination port one at a time, thereby
eliminating collisions within the switch.
Ovation uses full-duplex communication to connect a single end-station per switch port and
avoids collisions between the end-station and the switch. Combining these two techniques totally
eliminates data collisions in your Ovation system.
3.5
Using Ethernet switches to provide netw ork stability

Along with avoiding data collisions, Emerson uses Ethernet switches to implement a system with
built-in fault tolerance, thus guaranteeing system reliability and performance. A single component
failure, therefore, cannot disrupt or disable communications over the entire Ovation network.
Observe the following practices when using switches in Ovation systems:
Deploy Ethernet switches in pairs to supply redundant connection points for each station.
You can connect a station to both switches via a dual ported Ethernet card. This arrangement
provides each station with dual paths to and from the network.
Use additional groups of two switches that are geographically separated from the previously
defined two switches, to create clusters of stations. The distribution and number of clusters is
dictated by individual system configurations.
Connect the geographically located clusters of Ethernet switch pairs together using an
additional pair of cables. These form an up-link in a hierarchical tree. The depth of the
hierarchical tree is limited to two tiers (see page 51) to ensure predictable fail-over behavior.
This interconnection scheme provides fault tolerance originating at each station and
extending throughout the entire network.
REF_1005
41
3.5 Using Ethernet switches to provide network stability
3.5.1 Example of network switch configuration file

The following information provides an example of a network switch configuration file. Emerson
provides a project- specific configuration file for each Ovation system when the system is built.
G01 = Generic IP switch.
G02 = Root switch, zero fanout switches supported.
G03 = Backup root switch, zero fanout switches supported.
G04 = Primary fanout switch.
G05 = Partner or secondary fanout switch.
G06 = Root switch, up to three pairs of fanout switches supported.
G07 = Backup switch, up to three pairs of fanout switches supported.
G08 = Root switch, up to ten pairs of fanout switches supported.
G09 = Backup switch, up to ten pairs of fanout switches supported.
G10 = Dual attached, IP traffic only switch.
G12 = Root switch, one fanout area supported.
G13 = Backup root switch, one fanout area supported.
3.5.2 Switches used in Ovation networks

The following Ethernet switches are currently used in Ovation networks. Switch configuration is
based on the needs of each individual network and is performed by Emerson network specialists.
Note: All switches are subject to change as new technology is constantly improving and
evolving.
Managed Switches
Cisco WS-C2960-24
Intelligent Ethernet switch that supports 24-10/100 ports and 2 fixed 10/100/1000 uplink
ports.
Used for Ovation root, backup root, fanout, IP traffic, IP switches, and I/O device switch.
Can also be used as a general purpose managed switch.
Cisco WS-C2960-48TT-L
Intelligent Ethernet switch that supports 48-10/100 ports.
Supports two GBIC module slots.
Used for Ovation root and backup root switches to support more than 10 fanout areas.
Cisco WS-C2960C-24
Intelligent Ethernet switch that supports 24 10/100 ports.
42
REF_1005

Supports two 10/100 multi-mode fiber uplink ports.
Used for Ovation fanout and IP traffic switches.
Cisco WS-C2955T-12
Intelligent Industrial Ethernet switch that supports 12 10/100 ports.
Supports two 10/100 copper uplink ports.
Can be DIN rail mounted.
24VDC powered.
Used for Ovation fanout and IP traffic switches, and I/O device switches.
Cisco WS-C2955C-12
Supports two 10/100 multi-mode fiber uplink ports.
24VDC powered.
Cisco WS-C2955S-12
Supports two 10/100 single-mode fiber uplink ports.
24VDC powered.
Cisco WS-C3560-24-TS
Multi-network switch.
Intelligent Ethernet switch that supports 24 10/100 ports.
Supports two small form-factor pluggable (SFP) ports.
Used as Ovation core and backup core switches.
Unmanaged Switches
Allied-Telesis AT-FS708
Unmanaged Ethernet switch that supports eight 10/100 ports.
Works with integral power supply.
Used for IP-only devices (such as printers).
Hirschmann RS2-5TX Switch

Unmanaged Ethernet switch that supports five 10/100 ports.
24VDC powered.
Used for IP-only devices (such as printers).
REF_1005
43
3.5.3 Media converters used In Ovation networks

The following media converters are currently used in Ovation networks:
Note: All media converters are subject to change as new technology is constantly improving
and evolving.
EtherWAN EL900 series 10/100Base-TX to 100Base-FX Hardened Media Converter UTP to
Multi-mode or Single-mode Fiber. 1X00484
Features:
Link-Fault-Pass-through,
DIN rail mounting
-34C to 74C (-29F to 165F) extended operating temperature range.
redundant 10 to 48VDC power inputs.
provides a status relay contact output.
EtherWAN EL100 series 10/100Base-TX to 100Base-FX Media Converter UTP to Multi-mode

or Single-mode Fiber. 1X00529
Features:
Link-Fault-Pass-through
0C to 45C (32F to 113F) operating temperature range
rack mountable.
EtherWAN EMC1600 Chassis System 19 chassis system that provides 16-bays for EL100
Media Converters. 1X00530
Features:
44
hot swap
redundant power supplies
(100~240VAC, 50~60Hz, 0C to 45C (32F to 113F) operating temperature range.
REF_1005
3.6 OSI Seven-Layer Model
3.6
OSI Seven-La yer Model

The Ovation Fast Ethernet network uses equipment that is based on the OSI Seven-Layer Model.
The Open Systems Interconnection (OSI) model is the basis for open system protocols and
describes a network architecture composed of layers. The seven layers of the model reflect the
functions in data communications networks, and they serve as a framework for the various
networking standards. It has become a common reference point when discussing network
protocols, features, and hardware. The functional layers of the model are shown in the following
figure and are described below:
Figure 1: OSI Seven Layer Model
REF_1005
45
3.6 OSI Seven-Layer Model

Physical Layer this layer provides for the transmission of data and defines electrical and
mechanical properties. Media converters and repeaters operate at the physical layer and perform
the following functions:
Link two or more segments of any media types.
Regenerate signals.
Extend the physical span of a network.
Pass all traffic with no filtering.
Data Link Layer this layer controls the transmission of blocks of data between network peers
over a physical link. It monitors and resolves errors that may occur on the physical layer. The data
link layer used in Ovation networks is governed by the Ethernet standards. The switches and
network adapters operate at the data link layer. Ovation uses the Ethernet MAC (Media Access
Control) and IEEE 802 LLC (Logical Link Control) at this layer for addressing and data
communication.
Bridges and switches operate at the data link layer and perform the following functions:
Link two segments (bridges) of any media types.
Link two or more segments (switches) of any media types.
Regenerate the signals.
Isolate network segments to enhance performance.
Provide filtering to only pass selected traffic.
Isolate faulty segments and signals.
Network layer this layer routes data from one network node to other nodes. The network
layer used for communication in Ovation networks is IP (Internet Protocol). Ovation drops have
names such as DROP200 which is associated with an IP address. The IP addressing scheme
frequently used for Ovation is nnn.nnn.n.X where X is the drop number.
Routers operate at the network layer and perform the following functions:
Join multiple networks.
Provide network-to-network isolation.
Provide protocol-specific filtering, forwarding, and routing.
Provide controlled network-to-network access.
Provide firewall protection.
Example of network layer data: Ovation DDBs (Dynamic Data Blocks) that contain real-time
process data.
Transport Layer this layer ensures that data from the source arrives at the destination
correctly and in proper sequence. The transport layers used in Ovation networks are TCP
(Transmission Control Protocol) and UDP (User Datagram Protocol). TCP exchanges directed
messages between drops. UDP exchanges messages between drops and broadcasts messages
to many drops simultaneously.
Example of transport layer data: Alarms.
Session Layer this layer allows cooperating applications to synchronize and manage their
dialog and data exchange. Much communication in the Ovation network takes place at the
session layer.
46
REF_1005
3.7 Fast Ethernet network configurations

Examples of session layer data: Trend retrieval taken from an HSR and a query/download to a
drop from the Software Server.
Presentation Layer this layer provides services that interpret the meaning of the information
exchanged. Several different data representation standards are used in Ovation at the
presentation layer.
Example of presentation layer data: XDR (External Data Representation).
Application Layer this layer directly serves the end user. It supports end applications such as
file transfer and database access. Communication at the application layer occurs both within the
Ovation network and between the Ovation network and any external network. Any process used
to extract information from an Ovation network such as WAVE or OPC is an example of the
application layer.
Example of application layer data: WAVE or OPC data.
3.7
Fast Ethernet netw ork configurations

Currently, Ovation supports a single network topology that is a fault tolerant tree. The topology
always builds from a pair of root switches. If you need additional capacity or physical distribution,
you can add a second tier of switch pairs to fanout the structure. The depth of the tree is limited
to two tiers to ensure predictable fail-over behavior.
The operation of any DCS is dependent upon the control Local Area Network (LAN). Therefore,
Emerson tests extensively all the network components selected for use in the Ovation System.
This includes verifying performance, testing interoperability, characterizing the behavior in various
failure scenarios, and measuring the convergence time when a network topology change occurs.
Virtually all commercial network equipment meets the minimum standards of operation for typical
applications. However, only a subset meets the rigorous requirements needed to produce a
reliable DCS.
As a result, Emerson suggests guidelines (see page 40) as to the selection, configuration, and
interconnection of network equipment within the DCS LAN.
REF_1005
47
3.8 Cable connection types for your network
3.8
Cable connection types for your netw ork

The Ovation network has a high bandwidth to support large, geographically dispersed systems,
while being flexible enough to incorporate various media and topologies. The network is media
independent, allowing both fiber optic and/or copper (UTP) implementation.
Copper UTP (Unshielded Twisted Pair) represents the lowest cost option for cabling and
associated devices. However, copper is only appropriate for distances up to 100 meters while
fiber optic can manage distances of two kilometers or greater. Fiber optic is also less susceptible
to EMI noise.
You can substitute fiber optic media for any Fast Ethernet UTP copper cable in the Ovation
network. This enables you to extend a network run length beyond 100 meters or to enhance
Electro-Magnetic Interference (EMI) and Radio Frequency Interference (RFI) noise immunity.
The standard approach uses a media converter at each end of the optic segment with a short
UTP segment to connect to the switch of the NIC port. In the case of fanout-to-root switch
connections, the media converter at the fanout switch location can be eliminated by selecting one
of the switches with fiber optic uplinks.
Figure 2: Fiber Optic Media Options
48
REF_1005
3.8 Cable connection types for your network

The media converters are for multi-media fiber terminated with SC connectors and operate up to
two kilometers. The same vendor also makes a converter for single-mode fiber in the same form
factor if greater length is required. The converters can be used standalone with the included wall
plug transformer. When multiple converters are being installed in the same location, a mounting
rack can be used to mount up to 12 converters. This unit eliminates the wall mount transformers
with a pair of hot-swappable redundant power supplies. The individual modules can also be hotswapped. This greatly simplifies power distribution for a multiple converter cluster.
The media converters are configured to allow each pair to be bypassed during factory acceptance
test with a straight-through UTP cable when the fiber media is not available, as would be the case
of field installed fiber optic cable.
The standard fiber optic cable is the same duplex fiber Emerson used for FDDI installations. A
customers installed fiber optic cable may be reused by applying re-termination, new patch cables,
or adapter cables as necessary.
CAUTION! If you use non-redundant power for the media converters, it is imperative that you
power them from the same AC feed that supplies the switch to which they are connected.
REF_1005
49
3.9 Single-tier network arrangement
3.9
Single-tier netw ork arrangement

Every Ovation DCS is built around a pair of root switches that are interconnected for redundancy.
This pair of switches forms the root of the network tree. Consequently, they are named Root and
Backup Root. The simplest DCS consists of just this pair of switches and is suitable for relatively
small systems typically located in a single area. These systems commonly will be wired entirely
with UTP cable, although in some situations, media converters and fiber optic cable can be used
for remote nodes.
The following figure illustrates a small DCS configured around the pair of root switches. As the
size of the system increases or if clusters of Ovation drops are located in physically separate
areas, a second tier of switches can be added to fanout the tree. The maximum number of fanout
areas supported is governed by the root switch configuration used.
Figure 3: Single-Tier Ovation Network
50
REF_1005
3.10 Two-tier network arrangement
3.10 Tw o-tier netw ork arrangement

As the DCS grows beyond the port capacity of the root switches or when the Ovation drops are
physically distributed, the network can be expanded by adding a tier of fan-out switches. Fan-out
switches are deployed in pairs for redundancy, the same way as root switches. In this case, the
switches are named Primary and Partner.
The following figure illustrates a two-tier area with three fan-out switches. Cables interconnect the
primary and partner switches.
This allows a cluster of Ovation drops to be isolated for maintenance or to be operated locally
despite multiple failures. Typically, the cluster of drops in the fan-out switch area is wired with
UTP cable, and fiber optic cable may be used to connect these switches to the root switches.
Figure 4: Two-Tier Ovation Network
REF_1005
51
3.11 Connecting workstations to your Ovation network

The proper configuration of the switches is critical to correct and reliable system operation.
Emerson provides a switch configuration file (see page 42) for every Ovation system.
A closeup of a fan-out area is shown in the following figure.
Figure 5: Closeup of Fan-Out Area
3.10.1 IP traffic switch

In addition to the configurations listed in the previous section, you can use an IP traffic switch as
another mechanism to dual attach a non-redundant device to the DCS LAN.
The IP traffic switch is essentially a variation of the primary fan-out switch configuration. They are
suitable for connecting printers and other Ethernet devices.
3.11 Connecting w orkstations to your Ovation netw ork

Ovation workstation nodes (either Windows or UNIX based) are configured from commercially
available hardware. This equipment normally does not have provisions for redundant power
supplies or redundant AC feeds. Consider the following when designing the network connections
for workstations:
Power a workstation from the same AC feed as the switch to which it is connected.
Operator Stations seldom require dual attachment.
The dual attachment of a workstation to the network requires installation of either a dual-attached
NIC or two single-attached NICs via an OHI (Ovation Highway Interface) driver. Additionally, a
dual attached workstation consumes two switch ports, one on each of the dual switches in the
area.
52
REF_1005
3.12 Connecting OCR400 Controllers to your Ovation network

A redundant Controller consists of a primary and back-up processor. Each processor has its own
network connection that is integrated into the process module and provides complete redundancy.
To ensure redundant communications, each processor in the redundant pair should be attached
to a different switch. This ensures that there is no single point of failure.
The Processor (CPU) module in the OCR400 Controller contains four RJ45 ports at the top of the
module. The ports are numbered N1 through N4 and provide the following:
N1 = Connection to additional interfaces (for example, third-party device).
N2 = Connection to single-attached network interface.
N3 = Connection to dual-attached network.
N4 = Provides dedicated control synchronization for redundant Controllers.
A single-attached network connection is located in both the primary and redundant side of the
Controller. Each side of the Controller is connected to a different switch. Failure of a switch results
in the loss of communications for any Controller that is connected to that switch. If this switch
connects the primary side of the Controller, it will fail over to its associated redundant partner
which is connected via a separate switch.
Dual attachment of Controllers requires that both the primary and secondary Controller have a
dual- attached network connection and that twice as many ports be allocated in the associated
switches as would be required using the recommended approach.
The following figures illustrate typical network connections for an OCR400 Controller.
REF_1005
53
Figure 6: Network Connections to an OCR400 Controller - Single Attached
54
REF_1005
Figure 7: Network Connections to an OCR400 Controller - Dual Attached
REF_1005
55

A redundant Controller consists of a primary and back-up processor. Each processor has its own
NIC providing complete redundancy. To ensure redundant communications, attach each
processor in the redundant pair to a different switch. This ensures that there is no single point of
failure.
Controllers are allocated two ports per Controller. With this configuration, a single-attached NIC is
located in both the primary and redundant side of the Controller. Each side of the Controller is
connected to a different switch. Failure of a switch results in the loss of communications for any
Controller that is connected to that switch. If this switch connects the primary side of the
Controller, it will fail over to its associated redundant partner which is connected via a separate
switch.
Dual attachment of Controllers requires that both the primary and secondary Controller have a
dual- attached NIC, and that twice as many ports be allocated in the associated switches as
would be required using the recommended approach.
Figure 8: Ethernet Connections to OCR 161 Controller NIC Card Single Attached
56
REF_1005
3.14 Connecting Ovation devices to your Ovation network
Figure 9: Ethernet Connections to OCR 161 Controller NIC Card Dual Attached
3.14 Connecting Ovation devices to your Ovation netw ork

The selection of appropriate network interface cards (NIC) for use in an Ovation Ethernet drop
depends upon the connection requirements for the drop. An Ovation drop is attached to the
network using two single-attached station NICs along with an OHI driver.
An SAS has a single network port that connects to a single switch. Because SAS does not
provide connection redundancy, it is normally used for stations that are redundant by their nature
in a system. For example, an Ovation Controller is normally deployed as a primary and backup
pair. If the primary is single-attached to one switch and the backup is single-attached to another
switch, the Controller is fully redundant.
REF_1005
57
3.15 Connecting non-Ovation devices to your Ovation network
3.15 Connecting non-Ovation devices to your Ovation network

CAUTION! Do not use non-Emerson approved methods to connect third-party devices to your
Ovation network since this may degrade the operation of the DCS network.
Most networks and network devices, such as printers and GPS clocks, are not designed to
operate in a fault tolerant network. If they are improperly connected, they can introduce
unpredictable network behavior in the event of a device or cable fault.
An Ovation DCS can generate sustained high levels of multicast traffic. This can overwhelm many
devices, such as printers or equipment with a 10mbps Ethernet interface. Consequently, you must
isolate these devices from multicast traffic or they will degrade overall network performance. To
simplify the task of interfacing to printers, for Ethernet, Fast Ethernet, or non-Ovation devices that
require IP connectivity, the standard configurations for root and fan-out switches reserve Port 1.
This port is configured to block all Ovation multicast traffic, to auto-negotiate speed and duplicity,
and has root-guard enabled to protect the Ovation network from a misconfigured device. If
multiple devices must share this port, the following options are acceptable:
58
Use a managed switch this allows the standard Ovation network tools to be used to
configure and monitor the switch. Its operation status can be displayed on system graphics.
SNMP trap messages can be recorded in the system log. The WS-C2950-24 switch
configuration is intended specifically for this use. It is configured to support the generic IP
traffic required by non-Ovation devices. The IP-only port of this switch can be connected to an
IP-only port of any root or fan-out switch. It provides 23 ports that will auto-negotiate speed
and duplicity.
Use an unmanaged hub this is an economical method to provide a "shared" Ethernet

connection for multiple devices connected to Port 1 of a root or fan-out switch. An unmanaged
hub does not provide status information to the Ovation system so it cannot be monitored or
logged.
Use an unmanaged switch (see page 42) this is an economical method to provide
"switched" Ethernet connections for multiple devices connected to Port 1 of a root or fan-out
switch. An unmanaged switch does not provide any status information to the Ovation system
so it cannot be monitored or logged.
REF_1005
E C T I O N
Planning your Ovation multiple networks
IN THIS SECTION
What is an Ovation multiple network? ............................................................................... 59
Multiple network terminology ............................................................................................. 59
Multiple network planning guidelines for Ovation systems ............................................... 61
What do you need to plan before connecting multiple networks? .................................... 63
What is the connection plan for multiple networks? .......................................................... 67
4.1
What is an Ovation multiple netw ork?

The Ovation multiple network feature enables separate Ovation networks to communicate with
each other, making it possible to gather and retrieve data and implement control from one
network to another. An Ovation system configured for multi-network functionality supports
monitoring, control, and engineering functions across networks (see Ovation Multiple Networks
User Guide).
In order to use multiple networks, you must first use the appropriate configuration tool to define
the networks that will interface with each other (see Ovation Developer Studio User Guide (for
Windows applications).
4.2
Multiple netw ork terminology

Multiple network terms
TERM
DESCRIPTION
Alarm Collector
Software that runs on a local drop collects alarms from remote networks and distributes it to
the Alarm System on the Operator Stations on the local network. For each Alarm Collector,
the remote network(s) it connects to must be defined. You can define a Primary and a
Secondary Alarm Collector for redundancy.
Alarm-Data
Server
Drop on remote network where alarms are collected and sent to the Alarm Collector in the
local network. This drop can also serve as the remote data server. You can define a Primary
and a Secondary Alarm-Data Server for redundancy.
This information displays on the Base Alarm window.
Backbone
Top layer of network configuration. Provides IP connectivity between units.
Core
Core switch is the primary router that handles communication between multiple networks.
Backup core provides redundancy if the core fails.
DCS
Distributed Control System (such as an Ovation Control System).
REF_1005
59
4.2 Multiple network terminology
TERM
DESCRIPTION
Each point name consists of three parts and uses the format pointname.unit@network:
point name (up to 24 characters for Windows.
unit name (up to 6 characters).
network name (up to 8 characters) or network name alias.
Fully qualified
point name
In addition to the above parameters, the . and @ are required and are reserved
characters. Therefore, the maximum number of characters in a fully qualified point name is
40.
In a multiple network implementation, the network name segment can be one of the following:
actual name of the local network (for points on local network).
any of the defined network aliases (including the local network).
IP Address
Internet Protocol (IP) address uniquely identifies a computer so that data can be transferred
between computers and networks. This is used to establish the IP connectivity that is
necessary for sharing data between networks.
LAN
Local Area Network. Network that typically contains units that are located in the same
geographical location.
Local data server
Drop in a local network that contains special software that allows it to provide Ovation point
data to Ovation drops on a remote network when requested. This is defined from the local
network.
Note: It is recommended that the Ovation Database Server not be configured as a local data
server due to processing performance issues.
Local network
Network on the local system. This is the Ovation network that is connected directly to the
Ovation drops in the local system.
Machine Alias
User-defined name for the purpose of referencing a machine/drop in a remote network. For
example, a machine alias is used when adding a reference/specification to a remote data
server. This name must be unique within the local systems Ovation database and cannot
conflict with any local drop names.
Machine Name
Drop number (for example, drop200).
Network Name
Alias
Unique user-defined name given to a network to identify it from other networks in a multiple
network configuration. This is not the original network name that was defined in the
Developer Studio for Windows or Init and Admin Tools for Solaris when the system was first
configured.
An alias cannot have more than eight characters and cannot contain any spaces, dashes (-),
periods (.), or at signs (@) in the name.
It is recommended that the network aliases be consistent across all networks in the multiple
network setting (that is, NET1 refers to the same network in each network).
Number assigned consecutively by the system to a network to identify it from other networks
in a multiple network configuration. This number is automatically generated by the system
configuration tool (Developer Studio for Windows or Init and Admin Tools for Solaris).
Note: The local network is always network number zero (0).
Network Number
Alias
If a remote network is removed through the system configuration tool, you can reassign the
network alias number so that the remaining networks can be numbered consecutively. If this
occurs, all drops must be downloaded with configuration information. If drops are
downloaded, you must reboot them.
For example, if a system has three remote networks defined, their network aliases would be
1, 2, and 3. If you remove network 2 through the system configuration tool, then network 3
would be renumbered as network alias 2. You should then download all drops with this new
information.
60
REF_1005
4.3 Multiple network planning guidelines for Ovation systems
TERM
DESCRIPTION
Remote Data
Server
Drop in a remote network that contains special software that allows it to send Ovation point
data from the remote network when requested. This is defined from the local network.
Remote Network
Alias
Unique user-defined name given to a remote network to identify it from other networks in a
multiple network configuration. This is not the original network name that was defined in the
Developer Studio for Windows or Init and Admin Tools for Solaris when the system was first
configured.
It is recommended that the network aliases be consistent across all networks in the multiple
network setting (that is, NET1 refers to the same network in each network).
Remote Network
4.3
Network on another system that is interfaced to a local network (in the local system) so that
data can be exchanged between the networks (also known as an External network or a
Client).
The software can interface up to 32 multiple networks (31 remote networks and one local),
but the actual number of networks that are interfaced depends on the hardware used and the
system requirements.
Router
Hardware that isolates a network but provides selective connectivity between IP addresses
on local and remote networks. The router is used to determine what data can be shared
between networks.
Switch
Hardware that selects the path for sending data to networks. Typically, a switch provides the
connections between the router and the system drops.
WAN
Wide Area Network. Network that typically contains units that are NOT located in the same
geographical location.
Multiple netw ork planning guidelines for Ovation s ystems

Planning and implementing a multiple network is a complex process. Emerson can provide you
with expert advice and guidance to ensure that your multiple networks work correctly and
efficiently. As you and Emerson plan and design your Ovation multiple network system, observe
the following guidelines:
1. Collect the following information:
Number of Ovation networks you want to include in your multi-network system.
Number of drops in each network.
Types of drops.
Which networks will remotely control other networks.
Type of security you want to establish.
Changes to existing networks to accommodate a multi-network environment.
Limitations imposed by your local network infrastructure.
2. You must provide IP connectivity between the Ovation DCS networks that you want to
connect.
Identify (see page 63) whether this connectivity will come from new networks, existing
networks, or a combination of both.
Identify the IP addresses for all the equipment you will use in your multiple network
design.
3. Determine what type of hardware you need to physically connect your networks:
REF_1005
61
4.3 Multiple network planning guidelines for Ovation systems

Routers.
Switches.
Cables.
Currently, Emerson recommends using a multi-network core router/switch (see page 42) that
combines switching and routing capabilities. You can use this core router/switch to connect
up to 16 networks.
4. Provide for redundant multiple-network connections by installing a second core router/switch
that connects the networks. This ensures that automatic failover occurs if your main core
router/switch fails.
5. Your multiple network system should support the following types of connectivity:
Wide-area connectivity using dedicated T1s, frame-relay, or other network types.
Local-area connectivity using Ethernet, Fast Ethernet, or Gigabit Ethernet.
6. Use routers to make sure that each separate DCS network is isolated from the other networks
in the multiple-network system.
7. Do not connect a core router to a fan-out area switch.
8. After the hardware is installed for your multiple-network system, you need to configure the
software so that the separate networks can communicate with each other. Refer to Ovation
Multiple Networks User Guide for configuration instructions.
62
REF_1005
4.4 What do you need to plan before connecting multiple networks?
4.4
What do you need to plan before connecting multiple netw orks?

After you make the decision to connect multiple Ovation networks together, you must develop a
plan to implement your multi-network environment in a logical and consistent manner. There are
many ways that you can establish a multi-network Ovation environment.
This section is included to help you develop a plan through the use of simple examples illustrating
three of the most basic scenarios that you may encounter. Each specific installation requires
unique configuration details to accommodate local conditions. These details are best addressed
by consultations between your system engineers and network administrator.
Before you initiate your multi-network plan, assess your situation. This assessment includes how
many Ovation systems you want to multi-network, the number of drops and drop types, the
systems that are to control other systems remotely, the kind of security that you want to establish,
and what changes you must make to existing systems to accommodate a multi-net environment.
Also, be aware of any specific limitations imposed by your local network infrastructure.
There are three basic scenarios that drive most multi-network projects:
New Installation (see page 64) you want to install new Ovation control systems and set
them up from the outset to work in a multi-network environment.
Networking Existing Separate Ovation Systems (see page 65) you already have two or
more Ovation control systems and you want to use them in a multi-network environment.
Hybrid (see page 66) you already have one or more existing Ovation control systems that
you want to add additional Ovation systems to for use in a multi-network environment.
Note: Any and all Domain Controllers for a shared domain (in a multiple network environment)
must run Windows Server 2008, if all Ovation systems that it serves will run Ovation 3.3.1 or
later.
Any and all Domain Controllers for a shared domain (in a multiple network environment) must
run Windows Server 2003 if any Ovation systems that it serves will be a mix of Ovation 3.3.1 (or
later) and Ovation releases 2.4.0 through 3.3.0.
Pay special attention to systems where the Database Server is also configured as a Domain
Controller. The Database Server must run Windows Server 2008 (for Ovation 3.3.1 and later
releases). Therefore, a Database Server cannot be configured as a Domain Controller in
systems that are running mixed versions of Ovation (that is, running a mix of Ovation 3.3.1 (or
later) and Ovation releases 2.4.0 through 3.3.0.
Refer to Software Installation Manual for Ovation 3.3.1 for more information.
REF_1005
63
4.4.1 What is a multiple network implementation for new Ovation systems?

The new installation scenario represents the easiest method to establish a multi-networked
Ovation environment. New Installations minimize or eliminate issues related to accommodating
legacy decisions made before multi-networking was an option.
The main issue with this scenario is to establish a logical and consistent naming convention. Up
to this point, most of the discussion was about the naming concerned aliases. However, in
addition to the network alias, each Ovation system also has a network name. The alias concept
was designed to deal with situations where existing multiple Ovation systems were similarly
named. Take this opportunity to avoid future problems with newly installed systems, even if you
do not want to multi-network at this time.
Emerson recommends that you designate each separate Ovation system (each Ovation database
defines a separate Ovation system) with a unique network name. Furthermore, we recommend
that the network alias match the network name for each system. The network name has
implications for your Ovation point names, while the network alias has implications for multinetworking and security. When using the Security Manager (see Managing Ovation Security), use
the same name for the network as you use for the alias. This strategy allows security policies that
are created offline to be automatically assigned to your networks when they are created in the
applicable system configuration tool.
Utilizing matching names greatly reduces administration problems and avoids confusion.
64
REF_1005
4.4.2 What is a multiple network implementation for existing Ovation systems?

This scenario assumes that you already have two or more existing Ovation control systems
installed and they are currently operating in a non-networked mode. That is, each Ovation system
is completely independent of the other(s) and you want to take advantage of the efficiencies of
operating in a multi-networked environment, and you have no immediate plans to include
additional Ovation systems at this time. If you are adding a new Ovation control system, see
Hybrid Networking (see page 66).
Usually, the major concern with this scenario is an inconsistent or non-existent naming policy.
Prior to the release of software version 2.2, Ovation operated only in a single system mode. In
this mode, references to points, drops, and other devices are relative to the system itself, making
a naming strategy less important. However, in a multi-network environment, when one Ovation
system needs to communicate with devices on another Ovation system, consistent naming
becomes critical.
This situation is why network aliases were introduced for Ovation. Creating an alias for your
Ovation systems eliminates the need for you to rename your networks a complex procedure
that can have negative consequences for using historical data from your system.
If your local conditions are similar to this scenario, we recommend that you develop a logical and
consistent naming strategy and apply it to the aliases that you create for your individual Ovation
systems before you attempt to establish a multi-net environment. It is further recommended that
you retain the existing network names. If you add new Ovation systems in the future, apply your
naming strategy to both the network names and network aliases for the new systems. Using
unique aliases for each individual Ovation system enables a multi-network environment to
properly route data traffic between devices in different systems.
When defining security policies for your Ovation multi-network, use the same aliases in the
Security Manager (see Managing Ovation Security) as you assign here.
Example:
For example, assume you have an Ovation system in Unit 1 at Site A and another Ovation system
in Unit 1 at Site B. Up to this point Site A and Site B operated independently of each other, but
with Ovation multi-networking they can now be networked together so that an operator at Site A
can monitor and control operations at Site B. The problem is that each Ovation system has the
network name of "Unit1." This would result in conflicts when Site A tries to communicate with
similarly named points at Site B.
The solution is to apply appropriate network aliases to each system. Using a naming strategy
based on the planets and moons of the solar system, Unit1 at Site A is assigned the alias "Mars"
and Unit1 at Site B is assigned the alias "Jupiter." Now, similarly named points at both sites can
be uniquely addressed by means of their aliases. With this particular naming strategy, a new
Ovation system that is later added at Site A might be named "Phobos" and a corresponding
system added to Site B might be named "Europa."
For more information regarding Ovation point names, refer to the point builder information in the
Ovation Developer Studio User Guide (for Ovation Windows systems).
REF_1005
65
4.4.3 What is a multiple network implementation for hybrid Ovation systems?

This scenario describes the situation where you have existing Ovation systems that operate
independently, and you are planning to add new Ovation systems and use them all in a multinetwork environment. This scenario borrows its approach from both the existing Ovation systems
(see page 65) and the new system installation (see page 64)scenarios. A review of each of these
topics might be helpful to you to better understand the issues involved.
When planning for a multi-net environment in this scenario, begin with developing a logical and
consistent naming strategy for your Ovation systems. Refer to new system installation (see page
64) for a discussion of this step.
Apply your naming strategy to your Ovation systems, but retain the existing network names for
your existing Ovation systems. Assign these existing system aliases according to your naming
strategy. For your new Ovation systems, assign both network names and aliases that conform to
your naming strategy. When you define security policies for your Ovation multi-network, use the
same aliases in the Security Manager (see Managing Ovation Security) that you assign here.
66
REF_1005
4.5 What is the connection plan for multiple networks?
4.5
What is the connection plan for multiple netw orks?

This section provides an overview of how to plan for multiple networks and how they are
connected. For Ovation multiple networks to communicate with each other, you must connect
networks via specialized hardware. Other considerations involve security, permissions, and
addressing and naming conventions.
The hardware that is used depends upon what functions the system is required to perform. This
hardware includes items such as workstations, I/O modules housed in cabinets, routers, switches,
cables, and assorted devices. (See Planning Your Ovation System.)
The way you intend your Ovation systems to interact with each other and the roles various users
have relative to each system, or network, affects the decisions you make in the planning stage.
The following flowchart illustrates the necessary stages of connecting multiple Ovation networks.
Figure 10: Multiple Network Planning Flowchart
REF_1005
67
This section discusses the principles for connecting multiple networks and the considerations for
implementing connected networks. After you have read this section, you should be able to answer
the following questions:
What is backbone connectivity (see page 68)?
What is collapsed backbone connectivity (see page 70)?
How do I establish security and assign roles in a multiple network scheme?
4.5.1 What is backbone connectivity for multiple networks?

The following figure illustrates a typical multi-network Ovation configuration that uses backbone
connectivity. In this figure, the two units shown might be located in close proximity or in widely
separated geographic locations. In either case, the concept of operation is the same, where a
backbone or core network provides IP connectivity between all the connected units.
Figure 11: Example Configuration for Backbone Connectivity
68
REF_1005

If the units are in the same area, there can be a LAN connection that is essentially a collapsed
backbone. If the units are not in the same area, this can be a WAN connection, and you can use
any appropriate combination of media and protocols (such as dedicated T1 lines, VPN tunnels
over the Internet, Sonnet on an ATM mesh, or Frame Relay clouds) can be used. Each system
configuration varies because every system has different functions and requirements.
The root switch of the Ovation DCS LAN in each unit provides a Fast Ethernet port for the primary
connection from the unit to the backbone network. A second connection is available from the
backup root switch to support redundancy.
A router provides address translation, basic network security, and any protocol mapping required
to connect Fast Ethernet to the backbone network. The backbone network provider typically
supplies this router.
Each drop or workstation has a unique IP address that is used by the routers and switches to
transfer data between drops and between networks.
The following hardware is used in the Example Configuration for Backbone Connectivity figure
(this hardware configuration allows for redundancy):
Routers for each network (typically, part of the IP Backbone).
Two switches for each network (typically, part of the DCS LAN).
Additional hardware needed in each unit:

Two drops that serve as data servers for each network. We recommend that your data
server reside on a dedicated drop.
Two drops that serve as alarm collectors for each network. Alarm collectors do not need
to be on dedicated drops.
When you design a backbone network that provides IP connectivity for the Ovation DCS LANs,
ensure that the communication demands of the connected units meets the bandwidth limitations
of the technology you select. If the system is not designed to accommodate traffic demands,
multiple networks communication cannot provide the speed and efficiency needed by a control
system.
If you want to perform Ovation functions between systems after your system(s) are installed and
connected, you need to configure the software multiple network function for your system. Refer to
the software configuration information.
REF_1005
69
4.5.2 What is collapsed backbone connectivity for multiple networks?

The following figure illustrates the collapsed backbone that is typically used when units are
located within the same facility.
Figure 12: Example of configuration for Collapsed Backbone Connectivity

The collapsed backbone LAN consists of a pair of layer 3 switches. Layer 3 switches combine a
switch and a router within a single device. Each drop has a unique IP address that is used by the
routers and switches to transfer data between drops and between networks.
The following hardware is used in the example configuration (this hardware configuration allows
for redundancy):
Two switches for each network that are typically part of the DCS LAN.
Additional hardware needed in each unit:

Two drops that serve as data servers for each network. We recommend that your data
server reside on a dedicated drop.
Two drops that serve as alarm collectors for each network. Alarm collectors do not need
to be on dedicated drops.
If you want to perform Ovation functions between systems after your system(s) are installed and
connected, you must configure the software multiple network function for your system. Refer to
the software configuration information.
70
REF_1005
4.5.3 Hardware information for Ovation multiple networks

Switches/Routers
The Cisco WS-C3560-24 TS has been selected as the Ovation standard core switch.
This switch with integral routers provides the following features:
24 10/100 ports.
2 Gigabit Interface Converter (GBIC)-based Gigabit Ethernet ports supporting 1000Base-T,

1000Base-SX, 1000Base-LX/LH, and 1000Base-ZX GBICs.
Integral routing capabilities include hardware-based IP unicast and multicast routing, intervirtual LAN (VLAN) routing, routed access control lists (RACLs), and the Hot Standby Router
Protocol (HSRP).
8.8 Gbps switching fabric.
4.4 Gbps maximum forwarding bandwidth at Layer 2 and Layer 3.
128 MB DRAM and 32 MB Flash memory.
Compatibility with the Cisco RPS-300 redundant power supply.
326,000 hour Mean Time Between Failure (MTBF).
Once a WS-C3560-24 switch has been configured, it should be referred to as a multi-network

router.
Ports 1 through 15 on the core and back-up core routers are configured in pairs (one port on each
router) as a VLAN per potential DCS LAN. Each port is configured with:
Fixed 100mbs, full-duplex.
UDLD disabled (UDLD must be configured symmetrically with the Ovation drop ports on the
root and backup switches).
STP disabled (this allows the port to enable immediately providing secure port behavior).
DDB multicast traffic blocked (DDB multicasts are blocked from reaching other networks
because intra-VLAN communications is limited to layer-3 IP only traffic and there is only a
single active port per switch in each VLAN).
Connect these ports to a port on the DCS LAN root and back-up root switches that have the
standard Ovation drop connection configuration. Do not configure these ports to a port configured
for connection to fan-out areas or IP-only connections. Do not connect a core router to a fan-out
area switch.
Configure ports 16 through 24 on the core and back-up core routers as single sixteenth VLAN to
support direct connections of drops such as eDBs, OPHs, Dedicated Domain Controllers, GPSbased NTP servers, and anti-virus management stations with:
Fixed 100mb/sec full-duplex setting.
UDLD disabled.
Spanning-Tree PortFast enabled.
Configure port 24 for the connection of printers and other IP only devices with:
Auto-negotiation enabled.
UDLD disabled.
Multi-cast traffic blocked.
REF_1005
71

Cabling Considerations
The increase in data rate provided by Gigabit Ethernet cable requires the use of different cables
and imposes greater restrictions on maximum distances.
The typical Ovation installation utilizes the 1000Base-T GBICs with short Category 5e copper
cables (1X00109). This is a high quality, 4-pair straight-through cable and is different than
standard Ethernet Category 5 cables (5A26155).
Make the connection between the multi-network routers and the root switches in the DCS LAN the
same as the root to fan-out area switches within the DCS LAN. Use the standard 1X00063
Category 5 crossover cable. If a fiber optic connection is required, use the 1X00046 media
converters in the standard switch-to-switch configuration.
72
REF_1005
E C T I O N
Planning cable configurations for your Ovation

system
IN THIS SECTION
Network cable configuration types for your Ovation system ............................................. 73
Selecting network cable .................................................................................................... 75
Planning network and I/O field wiring routing .................................................................... 77
5.1
Netw ork cable configuration types for your Ovation system

Ovation supports a variety of standard network configurations. This can result in multiple media
options being used within one system (copper and fiber optic). The following cable types are most
commonly used in an Ethernet-based network.
Unshielded Twisted Pair (UTP).
Multi-Mode Fiber Optic Cable.
Single-Mode Fiber Optic Cable.
5.1.1 Unshielded twisted pair (UTP)

A minimum of Category 5 Unshielded Twisted Pair (UTP) cable is required to support
transmission speeds of 100 Mbps. Category 5 refers to not only the cable itself but also to the
termination components and the installation practices as well. To conform to Category 5 specified
levels, all connectors, patch panels, punch down blocks, patch cords, and so on must be
Category 5 approved.
In addition, you must perform the installation according to Category 5 standards. Category 5 cable
installations should be certified at the time of installation by an independent testing agency.
Furthermore, any existing plant cables already installed and used should be re-tested and recertified to Category 5 standards prior to DCS start-up. This will avoid the situation where
problems with the network infrastructure will be attributed to performance difficulties with the DCS
itself.
UTP is suitable for applications where separation distance between the end station and the switch
does not exceed a cabling distance of 100 meters.
Note: This is the minimum cable requirements for Ovation systems, but there are many other
valid cable options that you can use. Category 5E and Category 6 are also appropriate for use
in Ovation systems. Consult your network management team for additional suggestions.
REF_1005
73
5.1 Network cable configuration types for your Ovation system
5.1.2 Multi-mode fiber optic cable

Multi-mode fiber optic cable used for Fast Ethernet consists of either a 50 m or a 62.5 m
diameter glass core encased in a 125 m diameter cladding.
Fiber optic cable does require special installation and termination skills. As with Category 5 UTP
installations, fiber optic media installations should be certified to applicable standards.
The non-conductive nature of fiber optic cable makes it immune to Electro-Magnetic Interference
(EMI) and Radio Frequency Interference (RFI), and is the best choice for use in harsh EMI/RFI
environments.
The low optical loss combined with an excellent signal to noise ratio allows multi-mode fiber optic
cable to be used for distances of up to two kilometers (1.25 miles).
5.1.3 Single-mode fiber optic cable

Single-mode fiber optic cable provides a signal path of much longer distance than does multimode fiber optic cable. Single-mode fiber optic cable can be used in circumstances when
distances exceed two kilometers. Single-mode fiber is able to span these distances due to both its
construction and the use of laser transmitters with avalanche PIN diode receivers.
Maximum distances are determined by the specifics of the installation, but are frequently cited as
being 30 kilometers (approximately 18 miles).
Note: For single-mode applications, Emerson recommends that you consult your network
management team for additional suggestions.
Planning safety for single-mode fiber optic cable
Single-mode applications generally require special safety precautions due to the high energy
lasers used for transmission. The frequency of the laser radiation used is not visible, but is
intense and can cause permanent eye damage.
Use the following precautions to help ensure safe use of single-mode applications:
Limit the physical access to equipment.
Certify technicians who will work on the equipment.
Contact OSHA or an equivalent local authority for additional precautions needed when using
equipment that contains a laser hazard.
Note: You may require a valid export license to export single-mode components to certain
countries.
74
REF_1005
5.2 Selecting network cable
5.1.4 Media converters

Media converters (essentially a repeater) provide additional network flexibility. They are used
external to a switch or NIC to convert from one media type to another.
The standard approach uses a media converter at each end of the optic segment with a short
UTP segment to connect the switch of the NIC port.
For example, consider an application where a single station or Controller is located in excess of
100 meters from a switch. In this situation, you can use media converters to change UTP to fiber
and back.
Note: If you use a media converter in your Ovation Controller cabinet, ensure that the Controller
does not exceed the recommended ambient operating temperature.
5.2
Selecting netw ork cable

There are several factors that influence the selection of network cable:
Existing cable infrastructure (see page 75).
Electro-Magnetic Interference (EMI) and Radio Frequency Interference (RFI) (see page 75).
Grounding (see page 76).
Node-to-node or total distance (see page 76).
Permanently installed cable versus patch cables (see page 76).
5.2.1 Existing network cable infrastructure

Many facilities have an extensive data communications cable plant already installed. If this cable
plant can be used for control system installation, it can reduce the costs of supplying and
installing dedicated control system network cables.
The largest cost component of network cabling is not the media itself but rather the installation.
Building upon the existing infrastructure may influence the selection for additional media.
To be used successfully with Ovation, the existing cable plant must meet or exceed the
requirements discussed in Network cable configuration for your Ovation system (see page 73).
5.2.2 EMI/RFI environment for network cable

You must consider the levels of Electro-Magnetic Interference (EMI) and Radio Frequency
Interference (RFI) in the vicinity of cable runs when selecting media:
Signal transmission over UTP or coaxial cable is adversely effected in harsh EMI/RFI
environments.
Fiber optic media is immune to EMI and RFI and is typically the best choice for use in harsh
EMI/RFI environments.
REF_1005
75
5.2 Selecting network cable
5.2.3 Grounding network cable

Be aware of improper grounding or differences in ground potential between nodes:
Conductive media (UTP) can experience signal degradation from stray currents resulting from
the ground differences.
Non-conductive media (fiber optic cable) effectively eliminates these stray currents and is not
affected by the ground differences.
5.2.4 Distance between network nodes

Within a Fast Ethernet-based network, the maximum distance between nodes is limited by the
type of media being used. The maximum node-to-node cable distances are given below:
Category 5 UTP cable has a maximum distance of 100 meters (330 feet).
Multi-mode fiber optic cable has a maximum distance of 2,000 meters

(1.25 miles).
Single mode fiber optic cable has a typical distance of 30,000 meters
(18.5 miles).
5.2.5 Permanently installed network cables

Permanently installed cables are pulled through conduit, laid in cable trays, suspended on poles,
or buried underground. They typically run from room-to-room or building-to-building. These cables
are expensive to install, replace, or repair.
This document cannot provide installation instructions for permanently installed cabling, since
each cable installation varies greatly and is dependent upon the topography of a particular
installation. Emerson provides assistance, as requested, on a system-by-system basis.
However, in general, there are two things that should be considered for permanently installed
cables:
Spares - Provide spares, because the cost of the media is negligible when compared to the
installation cost. Using cable with spare pairs or fibers is good planning.
Patch panel - Terminate the permanent cabling at a patch panel so that it is not necessary to
handle the permanent cabling. Use an easily replaced (inexpensive) patch cable to connect
from the patch panel to the end station. Currently, two patch panels are recommended:
Rack-mount panel (1X00114).
Plate-mounted panel (5X00133).
76
REF_1005
5.3 Planning network and I/O field wiring routing
5.3
Planning netw ork and I/O field w iring routing

It is essential to protect all I/O signal cables from noise. You can do this by using appropriate
shielding and conduit, and by maintaining separation between noise-sensitive signal cables and
noise sources, including noise-producing cables such as power cables.
The following tables provide information on noise classes, cable and conduit selection, and
distances between cable types.
Follow these guidelines in planning cable routing:
Avoid parallel runs with noise sources.
Make crossovers at right angles.
Ground each field signal at a single point close to the source. If source grounding is not
possible, ground at the drop.
CAUTION! Multiple grounds can create noise currents. Ground each field signal (directly or
through its shield) only at a single reference point. (See Ovation I/O Reference Manual).
REF_1005
77
I/O Noise Class Criteria

NOISE
CLASS
DE FINITION/EX AMP LES
TYPE OF
CABLE
CONDUIT
Includes analog I/O signals,

digital pulse inputs to highspeed counting circuits, and
data links.
Shielded
twisted pair.
Conduit on tray must be bonded to plant

ground. Trays with 85% metallic coverage on
top, side, and bottom are recommended.
24/48V digital I/O and contact

input.
Twisted pair
recommended.
Conduit on tray must be bonded to each

ground.
Digital I/O greater than 48V.
Twisted pair
recommended.
Conduit on tray must be bonded to each

ground.
AC/DC power signals:

110 VAC, 250 VDC under
15 A except brakes and
fields.
Up to 100 A, 500 VDC or
440 VAC including brakes
and fields.
Over 100 A, 500 VDC,
440 VAC.
2.3 kV and over.
Cable type
determined by
voltage and
current of
circuit.
Both outgoing and return-carrying conductors

to be pulled in same conduit or laid side by
side in trays and secured in vertical runs.
(Quiet)
(Very Low)
L
(Low)
M
(Medium)
H
(High)
AND
TRAY INFORMATION
General Notes
1. Table information is based on 121 meters (400 ft.) run.
2. All shielded cables must be jacketed.
3. Except for mechanical protection, covered trays are not required for Class L and M cables if proper spacing is
maintained between dissimilar trays.
4. Class L and M cables may be in same tray if shielded cables are used.
78
REF_1005
Minimum Spacing between Noise Classes

NOISE
1
CLASSES
Q (QUITE/VERY
LOW)
L (LOW)
M (MEDIUM)
H (HIGH)
15 cm (6 in) in tray
15 cm (6 in.) in tray
or
or
or
7.6 cm (3 in)
between conduit
between conduit
7.6 cm (3 in) between

conduit
25.4 cm (10 in) both
51 cm (20 in) both
or
or
or
7.6 cm (3 in)
between conduit
7.6 cm (3 in)
between conduit
7.6 cm (3 in)
between conduit
23 cm (9 in) both
38 cm (15 in) both
Q
(Very Low)
L
(Low)
M
(Medium)
H
(High)
REF_1005
or
or
or
between conduit
7.6 cm (3 in)
between conduit
7.6 cm (3 in) between

conduit
15 cm (6 in) both
15 cm (6 in) both
23 cm (9 in) both
or
or
or
7.6 cm (3 in)
between conduit
25.4 cm (10 in)
both
35.6 cm (14 in)
both
51 cm (20 in) both
7.6 cm (3 in)
between conduit
23 cm (9 in) both
30.5 cm (12 in)
both
38 cm (15 in)
both
7.6 cm (3 in)
between conduit
15 cm (6 in) both
15 cm (6 in) both
23 cm (9 in) both
79
5.3.1 Field wiring requirements

All field wiring entering the Ovation I/O and Controller cabinets must meet the following
requirements. Additional requirements for CE Mark certified systems are included:
Insulation must be rated for the working voltage of the associating conductors.
For field wiring carrying hazardous voltages (voltages greater than 30Vrms (42.4 V peak) or
60VDC), the insulation must be rated for at least twice the hazardous voltage level, or the
insulation of all field conductors entering the cabinet must be rated for the highest hazardous
voltage entering the cabinet via field wiring.
The insulation must be continuous to the point of termination.
A single wire connection to an I/O module Base Unit terminal block can be wire gauge 22 up
to 12 AWG. Two wires connected to a single terminal in the Base Unit terminal block can be a
maximum wire gauge of 14 AWG.
Each terminal block on a G2R Relay Output module base can accept a single wire (gauge 22
up to 12 AWG).
Each terminal block on the KUEP Relay Output module base can accept a single stranded
wire (gauge 22 up to 14 AWG), or a single solid wire (gauge 22 up to 12 AWG).
Be sure that each wire opening in the terminal block is fully open before inserting the wire.
This ensures that the wire is clamped securely when the screw is tightened.
(CE Mark Certified System Only) ALL customer supplied I/O wiring to a CE Mark certified
Ovation cabinet MUST be braid shielded (90% coverage). All cable shields must be grounded
at the entry point of the cabinet using the approved grounding panel.
The temperature range of the field wiring must be 0 - 70 C or wider.
Note: The Ovation Controller and a subset of the I/O has been certified to IEC61131-2 Revision
2, Programmable Controllers. A list of these components can be found in Emerson drawing
5X00393. Refer to additional information about IEC61131-2 cabling requirements (see page
225).
80
REF_1005
5.3.2 AC/DC Mains wiring requirements

All wiring connected to the AC/DC Mains (AC/DC power cables) must meet the following
requirements. Additional requirements for CE Mark certified systems are included:
Each AC/DC Main must be single phase with a protective earth conductor.
CAUTION! A grounded neutral is required to prevent damage to the power supplies. The
neutral should be bonded to the protective earth conductor at a single point and earthed at a
point electrically common with the cabinet ground.
The insulation of the AC/DC Mains conductors should be rated for twice the AC/DC Mains
Voltage.
The conductor size of the AC/DC Mains conductors should not be less than 14 AWG.
The maximum size for the AC/DC power cable to the Ovation Power Distribution Module is 12
AWG (3.66 mm2).
You must supply an opening in the top or bottom gland plates as appropriate for entry of the
AC/DC Mains cords.
Note: The CE Mark Certified System supports AC Mains.
(CE Mark Certified Systems only) The cable must meet the requirements of IEC227 or IEC
245. AC Mains supply cords certified or approved by a national test house are considered
acceptable.
(CE Mark Certified Systems only) Green/yellow covered conductors shall be used only for
connection to the protective earth terminal. The cords must be protected against abrasion and
sharp bends at the point where the cord(s) enter the equipment.
Acceptable means are an inlet or bushing with a smoothly rounded bell mouthed opening with
a radius of curvature at least 1.5 times the diameter of the cord with the largest cross
sectional area that can be fitted OR a reliably fixed cord guard made of insulating material
protruding beyond the inlet opening by at least five times the diameter of the cord with the
largest cross sectional area that can be fitted.
(CE Mark Certified Systems only) A 10 Amp circuit breaker is required as part of the
building installation on each AC main connection to the Ovation Controller. It should be in
close proximity to the equipment and within easy reach of the operator.
The breaker should meet the requirements of IEC 947-1 and 947-3 and should indicate
use as a disconnecting device via IEC 417 symbols 5007 and 5008. The breaker should
be lockable in the off position.
Note: The Ovation Controller and a subset of the I/O has been certified to IEC61131-2 Revision
2, Programmable Controllers. A list of these components can be found in Emerson drawing
5X00393. Refer to additional information about IEC61131-2 cabling requirements (see page
225).
REF_1005
81
E C T I O N
IN THIS SECTION
General grounding guidelines ........................................................................................... 83
Protective earth ................................................................................................................. 83
Ovation cabinet EMC grounding ....................................................................................... 83
Grounding guidelines for single cabinet arrangements..................................................... 84
Grounding guidelines for clustered cabinet arrangements ............................................... 86
6.1
General grounding guid elines

The following guidelines apply to all Ovation cabinet configurations:
6.2
Do not ground through non-Ovation equipment.
Do not ground non-Ovation equipment to the Ovation cabinets.
Do not connect the Ovation Electromagnetic Compatibility (EMC) ground to a ground point
used by high voltage equipment.
Do not ground to structural members.
Protective earth
For continued protection against electrical shock, the Protective Earth conductor of the AC/DC
Input power cable must be connected to the Protective Earth terminal on the AC/DC Input
connectors located on the Power Distribution Module (refer to Example of Ovation Power
Distribution Module (PDM) (see page 170)). The Protective Earth terminal can be identified with a
"circled ground" symbol.
Do not, under any circumstances, use the EMC ground as the Protective Earth.
6.3
Ovation cabinet EMC grounding

You must ground the Ovation cabinets in your Ovation system to achieve proper Electromagnetic
Compatibility (EMC) performance and system reliability.
The information in this section is in addition to, but not in place of, the proper safety grounding of
the cabinet through the AC Mains (see page 81). Although the EMC ground connection is
electrically continuous with the safety ground terminal, relying on the EMC ground for the safety
ground may violate National Electrical Codes.
REF_1005
83
6.4 Grounding guidelines for single cabinet arrangements
6.4
Grounding guidelines for single cabinet arrangements

Use the following guidelines for grounding single cabinet arrangements:
Use a minimum of 4 AWG cable (preferably 0000 AWG) to make the EMC ground
connections to the earth grounding point. Use the dedicated studs on the bottom left and right
of the mounting plate within the cabinet to make the EMC connection (as shown in the
following figure). Make certain that the DC resistance from the cabinet to the earth grounding
point is less than 1 ohm and the length is minimized.
To minimize the chance of ground loops, ensure that the AC mains safety ground is at a
location that is electrically common with the EMC ground point or at least within one ohm of
this point. Tie the AC safety ground to earth only at the distribution source. Avoid connections
to earth at the intermediate load centers.
Figure 13: Single Cabinet Arrangement
84
REF_1005
6.4 Grounding guidelines for single cabinet arrangements
6.4.1 AWG diameters for solid and stranded wire

AWG diameters for solid wire
AWG RATING
SOLID WIRE DIAME TE R

(INCHES)
0000
0.4600
000
0.4096
00
0.3648
0.3249
0.2893
0.2576
0.2294
0.2043
To obtain the diameter in inches for stranded wire, a multiplier must be used. See the example
below.
Multiplier for stranded wire
NUMBER
WIRES
REF_1005
OF
MULTIPLIER
1.244
1.134
12
1.199
19
1.147
37
1.151
61
1.152
91
1.153
127
1.154
169
1.154
217
1.154
271
1.154
85
6.5 Grounding guidelines for clustered cabinet arrangements
6.4.2 Example of finding the diameter of a network cable

In a particular conductor, there are 19 stranded wires. To find the diameter (in inches) for a
particular AWG, refer to the following example. Find the solid wire diameter in inches for the
desired AWG (0.2043) and multiply it by the multiplier.
(multiplier for
19 wires)
1.147
(solid wire
diameter for
4 AWG)
x
0.2043
(diameter in inches of AWG

4 with 19 stranded wires)
=
0.2343
Therefore, the diameter for a 4AWG conductor with 19 stranded wires would be 0.2343 inches.
6.5
Grounding guidelines for clustered cabinet arrangements

It is acceptable to cluster cabinets to simplify the EMC grounding. The following guidelines apply:
Examples of clustered cabinet arrangements are shown in the figures in To remove the
shorting bar from an Ovation cabinet (see page 87). Cabinet #1 shall be designated the focal
cabinet. The focal cabinet is the cabinet in which the EMC ground connection is made. The
other cabinets shall be designated as the adjacent cabinets. In all systems, it is mandatory
that no adjacent cabinet be more than 10 meters from the central cabinet and it is
recommended that no more than five cabinets be part of a cluster.
In CE Mark Certified systems, the clustered cabinets MUST be suited (the side-skins are
removed between adjacent cabinets and the adjacent cabinets are bolted together with EMC
gasketing that is approved for the cabinets). Alternatively, it is permissible to wave the suited
cabinet requirement if all electrical cabling between cabinets within the cluster (with the
exception of the EMC grounding cable) is run in grounded metal conduit that is continuous
with the cabinets.
Make the EMC earth ground connections from the focal cabinet within the cluster using a
minimum of 4 AWG cable (preferably 0000 AWG) to the earth grounding point. Use the
dedicated studs on the bottom left and right of the mounting plate within the cabinet to make
this connection. Make certain that the DC resistance from the cabinet to the earth grounding
point is less than 1 ohm.
Additionally, all cabinets in the cluster must have their EMC grounds daisy chained together
from the focal cabinet using #4 AWG minimum cable. Make certain that the total length of the
ground cable from the ground point to the last cabinet in the cluster is minimized.
To minimize the chance of ground loops, ensure that the protective earth is grounded at a
location that is electrically common with the EMC ground point or at least within one ohm of
this point. Ground the protective earth conductor only at the distribution source. Avoid
connections to earth at the intermediate load centers.
The Digital Power Ground (PGND) is tied to the cabinet by a factory-installed shorting bar on
the Power Distribution Panel. When installing cabinet clusters, remove this shorting bar (see
page 87) on all cabinets except the focal cabinet.
Every cabinet has a factory installed strap between a PGND stud on the distribution panel
and a PGND stud on the CBO backplane or transition panel (transition panels include ROP,
RRP, RRB, and TND). To connect the PGNDs in clustered cabinets, do the following:
Connect an 8AWG strap from a PGND stud on the Power Distribution Panel of the focal
cabinet to a PGND stud on the backplane or transition panel on the adjacent cluster
cabinets.
86
REF_1005
Note: In the event that an adjacent cabinet in the cluster has multiple backplanes or panels,
connect the strap to only one backplane or panel. All transition panels within a cabinet should
have the PGND points connected.
In the event that there are multiple adjacent cabinets on one side of the focal cabinet,
place a PGND strap between each of these cabinets or directly to the focal cabinet as
appropriate. You can connect the strap to any available PGND stud found on a
distribution panel, a backplane, or transition panel in each cabinet.
6.5.1 To remove the shorting bar from an Ovation cabinet

The Digital Power Ground (PGND) is tied to the cabinet by a factory-installed shorting bar on the
Power Distribution Panel. When you install cabinets in clusters (see page 86), remove this
shorting bar on all cabinets except the focal cabinet (as shown in the following figures).
Perform the following steps to remove the shorting bar from an Ovation cabinet:
1. Turn off the power to the cabinet.
2. Remove the four thumb screws holding the cover on the Power Distribution Module.
3. Remove the nuts and lock washer attaching the shorting bar to the distribution panel. Remove
the cable strap connected to the mounting plate and the shorting bar. Discard the shorting
bar.
4. Reattach the cable strap (using the nut and lock washer previously removed) to the stud
referenced by the circled ground symbol (the upper left most stud).
REF_1005
87

5. Reattach the cover using the four thumb screws.
Figure 14: OCR400 Controller cabinet grounding cluster
88
REF_1005
Figure 15: OCR161 Controller cabinet grounding cluster
REF_1005
89
E C T I O N
Planning I/O modules for your Ovation system
IN THIS SECTION
What is an Ovation module? ............................................................................................. 91
Ovation I/O module features ............................................................................................. 91
Standard I/O modules ....................................................................................................... 93
Remote function modules (RIO) ........................................................................................ 93
Relay Output modules ....................................................................................................... 98
Guidelines for replacing, adding, or combining Ovation modules ..................................... 99
Installing Ovation standard I/O modules ......................................................................... 101
Installing Ovation Relay Output modules ........................................................................ 102
What are the I/O module types? ..................................................................................... 104
7.1
What is an Ovation module?

The Ovation Distributed Control System provides modulating control, sequential control, and data
acquisition for a variety of system applications. This system consists of a configurable mix of
functional Input/Output (I/O) modules that communicate on the I/O bus to the Ovation Controller.
Ovation modules provide an interface between the Ovation Controller and the processes in the
plant. Ovation modules are plug-in components with built-in fault tolerance and diagnostics. The
Ovation modules are housed in the various cabinets where they are mounted on DIN rails and
wired to the appropriate field devices. See Ovation I/O Reference Manual for additional
information about the use and configuration of Ovation I/O modules.
If Q-Line I/O is used with your Ovation system, see Q-Line Installation Manual for additional
information about the use and configuration of Q-Line I/O modules.
7.2
Ovation I/O module features

The Ovation modules have the following features:
Available in both remote and local configurations.
Modular, plug-in components.
Quick installation and configuration of the modules.
DIN Rail mounting of the I/O Base Units.
Wiring schematic labels are provided on Personality modules for Standard I/O.
Wiring schematic labels are provided on foam inserts for the following modules. This insert fits
into the Personality module cavity in the Base Unit.
Compact Contact Input.
Compact Digital Input.
Compact Sequence of Events.
REF_1005
91
7.2 Ovation I/O module features
Wiring directions are provided on the Base Unit for Relay Output modules:
Normally Closed (NC).
Normally Open (NO).
Common (C).
92
Writable surface labels are provided on Standard I/O Electronics modules so that up to 16
point names can be identified on each label.
The labels on the Standard I/O Personality and Electronics modules are color-coded to match
the appropriate modules.
Unique Base Unit interconnection scheme eliminates power and communications wiring.
Module style, group, serial number, and revision are stored electronically on each I/O
Electronics module.
Hot swapping capabilities streamline system maintenance.
Status indicators that display standardized diagnostic LED color codes.
Up to 128 standard Ovation modules per local Controller (Electronics module plus a
Personality module = 1 module unit).
Up to 1024 standard Ovation modules per remote Controller (Electronics module plus a
Personality module = 1 module unit).
Base Unit common to all standard I/O modules.
Two Base Unit styles (G2R and KUEP) are available for Relay Output modules
Testpoint/probe holder on each field terminal (except G2R style Base Unit).
Built-in spare fuse holders and wire strip gauge in standard I/O Base Units.
REF_1005
7.3 Standard I/O modules
7.3
Standard I/O modules

Standard I/O modules combine special Personality modules with Electronics modules, in order to
operate at a wide range of signals, and perform a multitude of functions.
The standard Ovation modules are illustrated below and consist of the following:
Electronics modules.
Personality modules.
Foam inserts are used instead of Personality modules for some I/O modules.
Base Units (containing I/O bus power, signals, and field terminations).
Note: For the Standard I/O Marshalling Base Unit, field terminations are located on the half
shells and connected to the base.
Personality
Modules
Electronics Modules
I/O Bus Power
and Signals
I/O Bus Power

and Signals
Base Unit
Field Terminations*
*Tightening torque: 5-7 in-ibs. (0.56-0.79 Nm)
*Single wire: 22-12 AWG
Two wires: 14 AWG max each
Figure 16: Standard I/O Modules and Base
7.4
Remote function modules (RIO)

Remote Function modules, used in remote I/O applications, include a Media Attachment Unit
(MAU) located in the Controller cabinet, and a Remote Node Controller (RNC) located in the
Remote Node cabinet.
These modules contain:
Electronics modules.
Personality modules.
Base Units (containing I/O bus power, I/O signal, cable connectors, and switches).
The Remote Function modules have the same environmental specifications (see page 413) as
the standard I/O modules have.
REF_1005
93
7.4 Remote function modules (RIO)
7.4.1 MAU module
Media Attachment Unit

Personality
Modules
Media Attachment Unit

Electronics Modules
I/O Bus
Power
and
Signals
R T
R T
R T
R T
R T
R T
Fiber-Optic Transmit/Receive
Connector Pairs
A-Side TWI
Connector
P3
R T
R T
I/O Bus
Power
and
Signals
B-Side TWI
Connector
P5
AUI Cable Connectors
Figure 17: Media Attachment Unit (MAU)
94
REF_1005

Place MAU modules only after the last addressed I/O module on a left branch in a cabinet, or
before the first addressed I/O module on a right branch. The following figure illustrates typical
valid positions for MAU modules in an I/O cabinet. In this example, there are six addressed I/O
modules on the left branch, and MAU 1 is after Module 6.
MAU 1 after last

addressed I/O module
on left branch
Controller
Controller
Note: MAU modules occupy spaces on a branch but do NOT occupy an address position. They
are not part of the system addressing scheme.
MAU 2 before first

addressed I/O module
on right branch
Controller Cabinet
Front
*This positioning also valid for Marshalling Cabinet.
REF_1005
95

Figure 18: Example of Typical Valid MAU Positions
7.4.2 RNC module

Remote Node Controller
Personality
Modules
Remote Node Controller

Electronics Modules
TWI
Connector
to TND
RS232
Serial
Ports
Remote Node
Address Switch
Local I/O Bus

Connector
Figure 19: RNC Module and Base (for Fiber Optic Media)
96
REF_1005

RNC modules must be placed on (connected to) a TND Remote Node Controller transition panel.
The following Figure illustrates the position of an RNC module in a Remote Node cabinet.
RNC
Module
TND
Transition
Panel
Remote Node Cabinet

Front
Figure 20: Example of Typical RNC Position
REF_1005
97
7.5 Relay Output modules
7.5
Rela y Output modules

Relay Output modules combine Electronics modules with Base Units in order to switch current
and voltage devices located in the field. The Relay Output module consists of the following:
Electronics module.
Relays mounted on the Base Unit (12 KUEP style or 16 G2R style relays).
Base Unit (containing I/O bus power, signals, and field terminations).
There are two variations of Base Units, one for 12 KUEP style relays, and one for 16 G2R
style relays.
Electronics Module
I/O Bus Power
and Signals
I/O Bus Power

and Signals
Relays
Base Unit
Field Terminations*
*Tightening torque: 4.4-7.1 in-ibs. (0.50-0.80 Nm)

*Single wire: 22-12 AWG (solid)
22-14 AWG (stranded)
Figure 21: Relay Output Module (12 KUEP Style Relays)

Electronics Module
I/O Bus Power
and Signals
I/O Bus Power

and Signals
Relays
Base Unit
Field Terminations*
*Tightening torque: 4.4-5.3 in-ibs. (0.50-0.60 Nm)

*Single wire: 22-12 AWG
Figure 22: Relay Output Module (16 G2R Style Relays)
98
REF_1005
7.6 Guidelines for replacing, adding, or combining Ovation modules
7.6
Guidelines for replacing, adding, or combining Ovation modules

Observe the following guidelines when replacing or adding modules:
Make sure that the replacement module is the exact replacement for the I/O module, both the
Electronic module and the Personality module.
Place modules from top to bottom on the left side of a cabinet and from bottom to top on
the right side of a cabinet.
If Relay Output modules are mixed with standard I/O modules on the same branch, ALWAYS
start the standard I/O module base in an odd-numbered module position on the branch
(positions 1/2, 3/4, 5/6, or 7/8).
You can place Relay Output modules in odd or even numbered positions. For example,
modules can begin in 1, 2, 3, 4, 5, 6, 7, or 8 slots.
Ensure proper Auxiliary voltage is available for all modules contained within the configuration.
Note that physical cabinet size, branch power requirements, and module auxiliary voltage
differences may limit the number and types of modules that can be configured in a branch.
You must terminate every I/O branch using one of the following:
Left terminator.
Right terminator.
MAU base module (right or left side).
RRP Transition Panel (right side only).
Refer to the applicable Controller documentation for additional information about
addressing the I/O modules.
REF_1005
99
7.6 Guidelines for replacing, adding, or combining Ovation modules
CAUTION! The I/O addressing for the Ovation database is determined from the positions of
the bases installed in the cabinets.
Emerson strongly recommends that you install all possible bases in the right-most branch of
each side of a cabinet, even if they are not all filled with I/O modules. This will prevent
disruption of the database if additional I/O modules are installed in the future.
Install I/O modules in the left-most branch of each side of a cabinet from the TOP DOWN
(making sure that each branch is properly terminated).
Install I/O modules in the right-most branch of each side of a cabinet from the BOTTOM UP
Approximately
500 mm
Controller
Controller
Controller
Controller
ROP
Remote
Node
Controller
ROP Trans Panel
4 1
3 2
2 4
1 7
Controller
TND
8
4
Marshalling
2
1
Extended
Remote Node
Figure 23: Examples of Standard

I/O and Relay Modules
Terminators
100
REF_1005
7.7 Installing Ovation standard I/O modules
7.7
Installing Ovation standard I/O modules

You install Ovation standard modules (except Relay Output modules) in Base Units mounted on
DIN rails in Ovation cabinets. Each Base Unit can contain two I/O modules. Even if you only use
one I/O module, you must still use a Base Unit that contains two terminal blocks.
DIN rails and modules are typically installed at the factory according to system requirements.
Note: For CE Mark certified systems:
Any Base Unit that contains a 125VAC/DC Digital Input Electronics module (1C31107G02) and
interfaces to hazardous voltage (>30 V RMS, 42.4 V peak, or 60 VDC) must include a
hazardous voltage warning label (1B30025H01).
Place this label in a visible location on the Base Unit, preferably above the spare fuse location.
The project drawings must indicate this.
7.7.1 To hot swap standard I/O modules

CAUTION! Before hot swapping Ovation I/O modules, you must have a thorough
understanding of the control process, the control logic, field device signals, control power
failure modes, and the settings for Ovation I/O modules as well as any other related control
hardware settings.
If you decide that hot swapping a module is feasible, make sure that you maintain the
appropriate settings for forced point values and/or field power jumpers in order to maintain the
system in a safe condition during the time period of the module hot-swap procedure.
Be sure to properly document forced point values and jumpers according to plant safety
procedures.
You can replace standard Ovation I/O modules quickly and easily without shutting down the
cabinet power supplies or reconfiguring the modules. Ovation I/O modules can be hot swapped
with no harm to the control system hardware; however, you are responsible for the I/O module
hardware settings and an analysis of process safety effects.
1. Determine what module needs to be replaced in the cabinet. Be sure you are using exact
replacements for both the Electronics and Personality modules.
2. Evaluate whether any affected plant processes can be maintained in a safe state during the
module hot swap, or whether a shutdown is required:
Identify all field equipment (inputs/outputs) terminated on the module.
Evaluate any possible effects on field equipment and control logic due to the loss of
signals and control power during the module replacement. Note that the signal quality
propagation in the logic scheme could be affected.
Evaluate whether the replacement I/O module requires a hardware setup.
3. Remove the old module by unlatching the blue corner latches on the Electronics module,
removing the Electronics module, and then removing the Personality module.
4. Install the new Personality module in the Base Unit first.
5. Then, install the new Electronics module next to the Personality module.
REF_1005
101
7.8 Installing Ovation Relay Output modules

6. Use the blue corner latches on the Electronics module to secure both modules into the Base
Unit.
The module is immediately functional.
7. After an I/O module has been swapped out, evaluate the current state of inputs and outputs
and the effect of current "real values" in order to perform safe removal of jumpers or forced
point values.
7.7.2 To add new standard I/O modules

Sometimes, during factory installation, not all of the available slots on a branch in a cabinet are
filled with modules. Typically, empty Base Units are installed to fill the available slot positions.
This is done to ensure that the module addressing is not disrupted if additional modules are
added later.
Use the following procedure to add additional modules to the existing Base Units:
1. Determine what modules are to be installed in the existing Base Units in the cabinet.
2. Install the Personality module in the Base Unit first. Then, install the Electronics module next
to the Personality module.
3. Use the blue corner latches on the Electronics module to secure both modules into the Base
Unit.
4. Connect the wires from the field devices to the terminal block in the Base Unit.
The wiring connections to the terminal block for each combination of Electronics module and
Personality module are printed on each Personality module.
Note: Be sure that each wire opening in the terminal block is fully open before inserting the
wire. This ensures that the wire is clamped securely when the screw is tightened.
7.8
Installing Ovation Rela y Output modules

You install Ovation Relay Output modules in Relay Output Base Units mounted on DIN rails in
Ovation cabinets. DIN rails and modules are typically installed at the factory according to system
requirements.
There are two styles of Relay Output Base Units:
1C31222 (12 KUEP relays).
1C31223 (16 G2R relays).
Each base unit can contain one Relay Output Electronic module and the appropriate relays.
7.8.1 To hot swap Relay Output Electronics modules

You can replace Ovation Relay Output Electronics modules quickly and easily without shutting
down the cabinet power supplies or reconfiguring the modules.
1. Determine what module needs to be replaced in the cabinet. Be sure you are using an exact
replacement for the Relay Output Electronics module.
2. Remove the old module by sliding the two latches, located on the card guides, to the open
position (a diagram is located on the module cover).
102
REF_1005
7.8 Installing Ovation Relay Output modules

3. Remove the old Relay Output Electronics module.
4. Install the new Relay Output Electronics module and slide the two latches into the locked
position.
The module is immediately functional.
7.8.2 To add new Relay Output I/O modules

Sometimes, during factory installation, not all of the available slots on a branch in a cabinet are
filled with modules. Typically, on the right side of the cabinet, empty Base Units are installed to
fill the available slot positions. This is done to ensure that the module addressing is not disrupted
if additional modules are added later.
Use the following procedure to add additional modules to the existing Base Units:
1. Determine what modules are to be installed in the existing Base Units in the cabinet.
2. Install the new Relay Output Electronics module and slide the two latches into the locked
position. Snap Relay Output Base unit onto desired branch position.
3. Connect the wires from the field devices to the terminal block in the Base Unit.
Note: Be sure that each wire opening in the terminal block is fully open before inserting the
wire. This ensures that the wire is clamped securely when the screw is tightened.
4. Note that the following wiring options are provided on the Base Unit. Select the appropriate
wiring option for each relay:
Normally Closed (NC).
Normally Open (NO).
Common (C).
Note: When wiring to the KUEP Base Unit (with Form X relays installed), wire between NO and
C. Do not connect any wiring to the NC terminal.
REF_1005
103
7.9 What are the I/O module types?
7.9
What are the I/O module types?

Analog Input modules (see page 105)
Analog Input (13 bits) (Legacy product).
Analog Input (14 bits).
Analog High Speed Input (14 bits).
HART Analog Input.
HART High Performance Analog Input.
RTD (4-Inputs).
RTD (8-Inputs).
16 Channel 4-20mA Analog Input.
Analog Output modules (see page 108)
Analog Output.
HART Analog Output.
HART High Performance Analog Output.
Digital Input modules (see page 110)
Digital Input.
Redundant Digital Input (Windows Ovation 3.2 and above).
Compact Digital Input.
Contact Digital Input.
Compact Contact Digital Input.
Sequence of Events Digital Input.
Sequence of Events Contact Digital Input Field Interface.
Sequence of Events Compact Digital Input Field Interface.
Enhanced Compact Sequence of Events Digital Input.
32 Channel 24V DC Single-Ended Digital Input
Digital Output modules (see page 114)
Digital Output.
High Side Digital Output (24 VDC).
Relay Output.
Fused Relay Output.
32 Channel 24 VDC Single-Ended Digital Output.
Bus interface modules (see page 116)
DeviceNet.
Foundation Fieldbus.
Profibus.
Ethernet Link Controller.
Specialty modules (see page 117)
104
Link Controller.
REF_1005
Loop Interface.
Pulse Accumulator.
Servo Driver.
Small Loop Interface.
Speed Detector.
Valve Positioner.
Numalogic Fast Ethernet Remote I/O subsystem.
7.9.1 Analog Input modules

Analog Input module (13 bits) - (Legacy product) - provides an interface to eight galvanically
isolated analog inputs with sampling rates of approximately 10 time/sec. Several voltage and
current configurations are available including cold junction compensation for thermocouple inputs.
1
Analog Input subsystems (13-bit)

RANGE
CHNLS
ELECTRONICS
PERSONALITY
MODULE
MODULE
20mV
1C31113G01
50mV
1C31113G02
100mV
1C31113G03
20mV Compensated (Thermocouple)
1 VDC
1C31113G04
5 VDC
1C31113G05
10 VDC
1C31113G06
0-20 mA Field powered

(4-20 mA Field powered can also be selected in the I/O Builder;
card is configured appropriately)
1C31113G05
0-20 mA Locally powered

(4-20 mA Locally powered can also be selected in the I/O
Builder; card is configured appropriately)
1C31113G05
1
3
3
3
3
1C31113G01
1C31113G02
1C31113G03
1C31116G01
1C31116G01
1C31116G01
1C31116G04
1C31116G04
1C31116G04
1C31116G01
1C31116G01
1C31116G01
1, 2
1C31116G02
1, 2
1C31116G03
This module configurations is CE Mark Certified.

This module configurations is CE Mark Certified (Non-EMC Cabinet).
A ninth logical channel (does not connect to a device) is provided when using the Analog Input module with
temperature sensor. This ninth point is needed for the CJ Compensation field of the Point Builder
Instrumentation Tab when defining the eight other thermocouple points for the AI module. (See Ovation
Developer Studio User Guide (for Windows).
REF_1005
105
Analog Input module (14 bits) - provides an interface to eight galvanically isolated analog inputs
with a minimum sampling rate of 10 time/sec. A low cost 4-20 mA current input is available along
with a 1V voltage input (legacy) configuration.
Analog Input subsystems (14-bit)
RANGE
4 - 20mA, Field or Locally powered
CHANNELS
1
1 VDC
1
ELECTRONICS
PERSONALITY
MODULE
MODULE
1C31224G01
1C31224G02
1C31227G01
1C31227G02
The 4-20mA Configuration is CE Mark certified.
Analog Input High Speed module (14-Bit) - provides an interface to eight galvanically isolated
analog inputs with sampling rates of medium speed (16/20 time/sec.) or high speed (50/60
times/sec.). Several voltage and current input configurations are available including cold junction
compensation for thermocouple inputs.
High Speed Analog Input subsystems (14-bit)
RANGE
ELECTRONICS
PERSONALITY
MODULE
MODULE
4 - 20mA, Field or Locally powered
5X00070G01
100mV, 250mV, 1V
5X00070G02
5V, 10V
5X00070G03
1mA 2 wire local powered
5X00070G02
1mA 4wire field powered
5X00070G02
20mV, 50mV, 100 (Thermocouple)
5X00070G04
20mV, 50mV, 100 (Thermocouple)
5X00070G05
1
2
106
CHANNELS
1,2
1C31227G01
1,2
1C31227G02
1,2
1C31227G02
1,2
1C31116G03
1,2
1C31116G02
1C31116G04
1C31116G04
This module configuration is CE Mark Certified.

This module configuration is CE Mark Certified (Non-EMC Cabinet).
REF_1005
HART Analog Input module - provides an interface for eight galvanically isolated HART field
devices with 4-20 mA current loop analog inputs (common reference). In addition to the analog
inputs, digital information can be exchanged between HART compliant devices and the Controller.
HART Analog Input subsystems (16-bit)
RANGE
CHANNELS
4-20 mA loop powered (2 wire) or active source

(4 wire)
1
ELECTRONICS
PERSONALITY
MODULE
MODULE
5X00058G01
5X00059G01
HART High Performance Analog Input module - provides an interface for eight galvanically
isolated HART field devices with 4-20 mA current loop analog inputs. In addition to the analog
inputs, digital information can be exchanged between HART compliant devices and the Controller.
HART High Performance Analog Input subsystems (16-bit)
RANGE
4-20 mA
CHANNELS
1
4-20 mA (Reduced radiated emissions).
4-20 mA
1
2
Analog Output pin-compatible.
ELECTRONICS
PERSONALITY
MODULE
MODULE
5X00106G01
5X00109G01
or
5X00109G02
(Ovation releases
3.4 and later)
5X00106G02
5X00109G01
or
5X00109G02
(Ovation releases
3.4 and later)
5X00106G01
5X00170G01

This module configuration is CE Mark Certified (Non-EMC Cabinet).
RTD module (4 Channel) - provides an interface to four galvanically isolated Resistance

Temperature Detectors. Several 3 and 4 wire RTD types are supported. A 50/60 Hz filtered
configuration is available for CE Mark applications.
RTD (4 Channel) module subsystems
RANGE
All
REF_1005
CHANNELS
4
ELECTRONICS
PERSONALITY
MODULE
MODULE
1C31161G01
1C31164G01
107
RANGE
CHANNELS
All (for 50/60 Hz filtered inputs and CE Mark certified

systems)
1
ELECTRONICS
PERSONALITY
MODULE
MODULE
1C31161G02
1C31164G02
Configuration 1C3116G02 / 1C31164G02 is CE Mark Certified.
RTD module (8 Channel) - provides an interface to eight galvanically isolated Resistance

Temperature Detectors. Several 3 and 4 wire RTD types are supported.
RTD module (8-Channel) subsystems
CHANNELS
1
2
ELECTRONICS
8
5X00119G01
5X00119G02
PERSONALITY
MODULE
5X00121G01
5X00121G01
MODULE

This module configuration is CE Mark Certified (Non-EMC cabinet).
16 Channel 4-20mA Analog Input module - provides an interface between the Ovation
Controller and 16 field devices that use a 4-20mA current loop. Up to 16 4-20mA (2-wire or 4wire) transmitters can be connected per module.
16 Channel 4-20mA Analog Input subsystems
DESCRIPTION
CHANNELS
ELECTRONICS
PERSONALITY
MODULE
MODULE
16 Channel 4-20mA Analog Input, 2wire and 4-wire
16
5X00501G01
5X00502G01
16 Channel 4-20mA Analog Input, 2wire only
16
5X00501G01
1X00692H01
7.9.2 Analog Output modules

Analog Output module - provides an interface to four galvanically isolated analog outputs using
12-bit digital-to-analog converters.
Analog Output subsystems
RANGE
0-5 Volts DC
108
CHANNELS
4
ELECTRONICS
PERSONALITY
MODULE
MODULE
1C31129G01
1C31132G01
REF_1005
RANGE
CHANNELS
ELECTRONICS
PERSONALITY
MODULE
MODULE
0-10 Volts DC
1C31129G02
0-20 mA with Diagnostics

(4-20 mA with Diagnostics can also be selected in
the I/O Builder; card will be configured
appropriately).
1C31129G03
0-20 mA without Diagnostics

(4-20 mA without Diagnostics can also be selected
in the I/O Builder; card will be configured
appropriately).
1C31129G04
4-20 mA with Diagnostics (For Redundant

applications).
1C31129G05
1
2
1C31132G01
1C31132G01
1C31132G01
1C31132G02
This module configurations is CE Mark Certified.

For Redundant applications using Windows Ovation 3.2 and above.
HART Analog Output module - provides an interface for eight galvanically isolated HART field
devices using 4-20 mA current loop analog outputs (common reference). In addition to the analog
outputs, digital information can be exchanged between HART compliant devices and the
Controller.
HART Analog Output subsystems (14 bit)
RANGE
CHANNELS
4-20 mA
1
ELECTRONICS
5X00062G01
PERSONALITY
MODULE
MODULE
5X00063G01
This module configuration is CE Mark certified.
HART High Performance Analog Output module - provides an interface for four galvanically
isolated HART field devices using 4-20 mA current loop analog outputs. In addition to the analog
outputs, digital information can be exchanged between HART compliant devices and the
Controller.
1
HART High Performance Analog Output subsystems (16-bit)

RANGE
CHANNELS
ELECTRONICS
4-20 mA
5X00167G01
4-20 mA
5X00167G01
REF_1005
MODULE
PERSONALITY
MODULE
1X00188H01 (molded plastic cavity insert)

5X00211G03 (Q-line migration)
109
7.9.3 Digital Input modules

Digital Input module - provides an interface for 16 current-sinking digital inputs using a
Personality module. Various input configurations are available.
Digital Input subsystems
RANGE
CHANNELS
ELECTRONICS
PERSONALITY
MODULE
MODULE
24/48 VAC/VDC Single-ended

Differential
16
16
1C31107G01
1C31107G01
1C31110G01
1C31110G02
125 VAC/VDC
16
16
1C31107G02
1C31107G02
1C31110G01
1C31110G02
Single-ended
Differential
All module configurations listed in the table are CE Mark Certified.
Redundant Digital Input module provides 16 digital channels to monitor the states (0 or 1)
of 16 field digital inputs. The module contains two voltage sensing circuits for each of the 16 I/O
channels located on the module. Redundant power for all 16 digital input channels is either
supplied by the Ovation auxiliary power supply or by an external 24V auxiliary power source. In
either situation, the redundant pair module shares a common 24VDC auxiliary power source.
Redundant Digital Input subsystems
RANGE
CHANNELS
24 V (Single Ended) Digital Input current

sinking, IEC 61131-2 Compliant Type 1
digital Inputs.
16
ELECTRONICS
PERSONALITY
MODULE
MODULE
5X00411G01
5X00414G01
Compact Digital Input module - provides a low cost interface for 16 current-sinking digital inputs
without requiring a personality module.
Compact Digital Input subsystems
RANGE
CHANNELS
ELECTRONICS
MODULE
PERSONALITY
MODULE OR CAV ITY
2
INSERT
24/48 VDC Single-ended
16
1C31232G01
1C31238H01 (molded
plastic cavity insert)
24 VAC/VDC Differential
16
1C31232G02
5X00034G01(Fused
Pmod)
48 VDC Differential
1C31238H01 (molded
110
REF_1005
RANGE
CHANNELS
ELECTRONICS
MODULE
125 VAC/VDC
Single-ended
16
1C31232G03
PERSONALITY
MODULE OR CAV ITY
2
INSERT
5X00034G01 (Fused
Pmod)
1C31238H01(molded
All module configurations listed in the table are CE Mark Certified.
This is an insert that fits into the Personality module position and provides a wiring schematic label for the
module.
Contact Digital Input module provides an interface for 16 current-sourcing digital (contact)
inputs using a personality module. The following input configuration is available: 48 VDC (singleended channels have a common return, which is the return for the on-module 48 VDC current
limited contact wetting power supply).
Contact Digital Input subsystems
RANGE
CHANNELS
48 VDC On-Card Auxiliary (Legacy)

1
16
ELECTRONICS
PERSONALITY
MODULE
MODULE
1C31142G01
1C31110G03
This module configuration is CE Mark certified.
Compact Contact Digital Input module provides a low cost interface for 16 current-sourcing
digital (contact) inputs without requiring a personality module. The following input configuration is
available: 48 VDC (single-ended channels have a common return, which is the return for the onmodule 48 VDC current limited contact wetting power supply).
Compact Contact Digital Input subsystems
RANGE
CHANNELS
Compact Contact with 48 VDC On-Card

Auxiliary
1
16
ELECTRONICS
MODULE
MOLDE D PLAS TIC

2
CAV ITY INS ERT
1C31234G01
1C31238H01
This is an insert that fits into the Personality module position and provides a wiring schematic label for the
module.
REF_1005
111
Sequence of Events Digital Input module provides an interface for 16 digital inputs using a
personality module. The Sequence of Events module monitors the states of the 16 digital inputs
and uses digital filtering to reject state changes less than 4 msec. It performs event tagging and
chatter control for each digital input.
Sequence of Events Digital Input subsystems
RANGE
CHANNELS
24/48 VDC Single-ended (Legacy)

Differential (Legacy)
125 VDC
ELECTRONICS
PERSONALITY
MODULE
MODULE
16
1C31157G01
1C31110G01
16
1C31157G01
1C31110G02
1C31157G02
1C31110G01
1C31157G02
1C31110G02
Single-ended (Legacy)
Differential (Legacy)
16
All module configurations listed in the table are CE Mark certified unless they contain a 5FDI.
Sequence of Events Contact Digital Input Field Interface module - provides 16 contact input
current detecting channels with common returns.
Sequence of Events Contact Digital Input Field interface subsystems
RANGE
Contact Input w/ 48 VDC On-Card auxiliary
(Legacy)
CHANNELS
16
ELECTRONICS
PERSONALITY
MODULE
MODULE
1C31157G03
1C31110G03
All module configurations listed in the table are CE Mark certified unless they contain a 5FDI.
Sequence of Events Compact Digital Input Field module provides a low cost interface for 16
digital inputs without requiring a personality module. The Compact Sequence of Events module
monitors the states of the 16 digital inputs and uses digital filtering to reject state changes less
than 4 msec. It performs event tagging and chatter control for each digital input.
Sequence of Events Compact Digital Input Field subsystems
RANGE
CHANNELS
ELECTRONICS
PERSONALITY
MODULE
MODULE OR
CAV ITY INS ERT
112
Compact 24/48 VDC SOE Single-ended

digital input
16
1C31233G01
1C31238H01
(molded plastic
cavity insert)
Compact 24/48 VDC SOE Differential

digital input
16
1C31233G02
1C31238H01
(molded plastic
cavity insert)
REF_1005
RANGE
CHANNELS
ELECTRONICS
PERSONALITY
MODULE
MODULE OR
CAV ITY INS ERT

Compact 24/48 VDC SOE Single Ended
digital input
16
1C31233G02
5X00034G01
(Fused Pmod)
Compact 125 VDC SOE Differential

digital input
16
1C31233G03
1C31238H01
(molded plastic
cavity insert)
Compact 125 VDC SOE Single Ended

digital input
16
1C31233G03
5X00034G01
(Fused Pmod)
Compact 48 VDC SOE On-card auxiliary

Contact Input w/48V wetting
16
1C31233G04
1C31238H01
(molded plastic
cavity insert)
All module configurations listed in this table are CE Mark Certified.
This is a cavity insert that fits into the Personality module position and provides a wiring schematic label
for the module.
Enhanced Compact Sequence of Events Digital Input module provides a low cost interface
for 16 digital inputs without requiring a personality module. The Enhanced Compact Sequence of
Events module monitors the states of the 16 digital inputs and uses digital filtering to reject state
changes less than 4 msec. It performs event tagging and chatter control for each digital input.
Unlike other Ovation Sequence of Events (SOE) modules, the Enhanced Compact Sequence of
Events module also offers a field digital input state change detection feature (SOE One Shot).
Enhanced Compact Sequence of Events Digital Input subsystems
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE OR
CAV ITY INS ERT
24/48 VDC Single-ended Digital Input - Current

Sinking
16
5X00357G01
1C31238H01
24/48 VDC Differential Digital Input - Current

Sinking
16
5X00357G02
1C31238H01
24/48 VDC (Individually Fused Channels with

Common power supply) Single-Ended Digital
Input - Current Sinking
16
5X00357G02
5X00034G01
125 VDC Differential Digital Input - Current

Sinking
16
5X00357G03
1C31238H01
125 VDC (Individually Fused Channels with

Input - Current Sinking
16
5X00357G03
5X00034G01
48 VDC Single-ended Digital Input - Current

Sourcing (Contact input) with On-Card 48 VDC
power supply
16
5X00357G04
1C31238H01
24 VDC (Differential) Digital Input - Current

Sinking, IEC61131-2 Compliant Type 1 Digital
Inputs
16
5X00357G05
1C31238H01
REF_1005
1
1
113
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE OR
CAV ITY INS ERT
24 VDC (Individually Fused Channels with

Input - Current Sinking, IEC61131-2 Compliant
Type 1 Digital Inputs
16
5X00357G05
5X00034G01
This is a plastic insert that fits into the base units Personality module cavity and provides a base unit
terminal block wiring label for the module.
32 Channel 24V DC Single-Ended Digital Input module - monitors the state ("0" or "1") of 32
single-ended field digital inputs. The 32 Channel 24V DC Single-Ended Digital Input module is
designed to meet IEC 61131-2 type 3 characteristics for 24VDC digital inputs in industrial
automation.
32 Channel 24V DC Single-Ended Digital Input Subsystems
RANGE
CHANNELS
32 Channel 24V DC Single-Ended Digital Input
32
ELECTRONICS
PERSONALITY
MODULE
MODULE
5X00499G01
1X00690H01
7.9.4 Digital Output modules

Digital Output module - provides a means to switch up to 60 VDC at moderate currents (for
example, relay coils and lamps). The Digital Output module contains 16 current sinking transistor
outputs capable of switching 60 VDC loads at up to 500mA.
Digital Output subsystems
ELECTRONICS
MODULE OR PANEL
KIT
PERSONALITY
16
1C31122G01
1C31125G01
Local Power Supply
16
1C31122G01
1C31125G02
Field Power Supply
16
1C31122G01
1C31125G03
Relay Panels: Solid State Relay Panel (AC)
16
5A22410G01
Solid State Relay Panel (DC)
16
5A22410G02
G2R Relay Panel (Low Power Electro-mechanical)
16
5A22411G01
16
5A22412G01 - G03
DESCRIPTION
CHANNELS
5-60 VDC Single ended Direct
MODULE
Relay Panel Interface:
KU Relay Panel
1
2
114
(High Power Electro-mechanical)
All configurations listed in the table are CE Mark certified, unless they use AC/DC solid state relay panels.
Two panels (8 relays each) are included in the KU Relay Panel kit 5A22412G01, G02, and G03.
REF_1005
High Side Digital Output (24 VDC) module - an intelligent microcontroller-based digital output
module. The HSDO consists of two modules, (electronics and personality), that are inserted into
an Ovation I/O module base unit. The HSDO module contains sixteen optically isolated digital
output channels. Each digital output channel is capable of sourcing up to 500 mA of output
current.
High Side Digital Output (24VDC) subsystems
RANGE
24VDC
CHANNELS
16
ELECTRONICS
PERSONALITY
MODULE
MODULE
5X00270G01
5X00273G01
Relay Output module - consists of an Electronics module, a base assembly, and relays. The
Relay Output module provides a means to switch high AC voltages at high currents to field
devices. There are two versions of the Relay Output base assembly which contain either 12 or 16
relays within each base.
The Relay Output base assembly does not incorporate a Personality module. For more
information on module configuration, refer to the following topics: Electronics modules (Emod),
Base assemblies, and Panel kits.
Fused Relay Output module - provides a means to switch high current and voltage devices
located in the field. You have a choice between a fused low power relay output assembly and a
fused high power relay output assembly for differing applications.
The Fused Relay Output base assembly does not incorporate a Personality module. For more
information on module configuration, refer to the following topics: Electronics modules (Emod)
and Base assemblies - (FRO).
32 Channel 24 VDC Single-Ended Digital Output module - contains 32 24-volt single-ended
digital output channels. Each digital output channel is capable of sourcing up to 500 mA of output
current with a 2A maximum total output current limit per module.
32 Channel 24V DC Single-Ended Digital Output subsystems
DESCRIPTION
32 Channel 24V DC High-Side, Single-Ended
Digital Output
REF_1005
CHANNELS
32
ELECTRONICS MODULE
OR PANEL KIT
PERSONALITY
5X00500G01
1X00691H01
MODULE
115
7.9.5 Bus interface modules

Foundation Fieldbus module The Ovation Foundation Fieldbus module provides a means to
interface the Ovation system to industry standard Foundation Fieldbus devices. The interface to
the module is through the Ovation I/O bus; therefore, this module is native to Ovation as opposed
to an add-on or linking approach.
The Ovation Foundation Fieldbus module interfaces with one or two networks. The module
supports redundancy and can be installed on each network. Only one module can be the master
at any given time. Inter-module redundancy communication is handled through a private RS232
communication link between the redundant pair. The communication cable is connected to a
RJ45 jack on the Pmod.
Foundation Fieldbus subsystems
CHANNELS
ELECTRONICS
2 (non-redundant)
5X00301G01
1C31238H01 (cavity insert)
2 (redundant)
5X00301G01
5X00327G01
MODULE
PERSONALITY
MODULE
Profibus module Profibus (Process Field Bus) DP (decentralized periphery) is an all digital,
two-way communication system that links devices (also known as slaves) and automation
systems. A decentralized periphery uses a network bus (in this instance, Profibus) between the
Controller (Ovation) and its connected I/O channels. Therefore, the I/O is decentralized as
compared to a programmable logic Controller (PLC) that has its I/O arranged centrally. At the
base level in the hierarchy of plant networks, Profibus serves as a Local Area Network (LAN) for
instruments.
Profibus subsystems
CHANNELS
2
ELECTRONICS
MODULE
5X00300GO1
PERSONALITY
MODULE
5X00321G01
DeviceNet module The Ovation DeviceNet Module provides an interface with one or two
DeviceNet networks, respectively. The DeviceNet has an associated Personality Module.
DeviceNet offers robust, efficient data handling based on Producer/Consumer technology that
allows you to determine effectively what information is needed and when.
DeviceNet subsystems
CHANNELS
2
116
ELECTRONICS
5X00376G01
MODULE
PERSONALITY
MODULE
5X00375G01
REF_1005
Ethernet Link Controller (see page 453) The Ethernet Link Controller provides an interface
with a single Ethernet link. This module uses a straight RJ45 connector which allows the port to
be accessed outside of the Electronics module.
Ethernet Link Controller subsystems
CHANNELS
2
ELECTRONICS
PERSONALITY
MODULE
5X00419GO1
MODULE
1X000569H01
7.9.6 Specialty Modules

Link Controller module provides a serial RS232, RS422, or RS485 data communications link
to a third-party device or system. To use this module, the appropriate SLC algorithm must reside
in the Ovation Controller.
Link Controller subsystems
RANGE
CHANNELS
ELECTRONIC
PERSONALITY
S MODULE
MODULE
RS232
One (1) Serial Port (Able to handle many

points)
1C31166G01
or
1C31166G02
RS485/RS422 Four
wire
One (1) Serial Port (Able to handle many

points)
1C31166G01
or
1C31166G02
1C31169G01
1C31169G02
All module configurations listed in the table are CE Mark Certified. 1C31166G02 pending CE Mark
Certification.
2
Not for new projects. Used for spares and replacements only.
To use this module, the appropriate SLC algorithm must reside in the Ovation Controller. (See Ovation
Algorithm Reference Manual.)
Loop Interface module provides an interface to the analog and digital I/O needed to control a
single process loop (up to 2 AI, 1 AO, 2 DI, 2 DO). In addition, the loop interface can display the
process information and provide for manual control via a local operator interface station (SLIM).
Loop Interface subsystems
1, 4
RANGE
CHANNELS
ELECTRONICS
PERSONALITY
MODULE
MODULE
Normal (Non-electric) Drive modules

0-10V Analog Inputs/Output
2
0-10V AI/AO - user defined Digital Inputs
REF_1005
6
6
1C31174G01
1C31174G21
1C31177G01
1C31177G01
117
RANGE
CHANNELS
ELECTRONICS
PERSONALITY
MODULE
MODULE
Normal (Non-electric) Drive modules

0-5V Analog Inputs, 0-10V Analog Output
0-5V AI, 0-10V AO - user defined Digital
2
Inputs
6
6
1C31174G02
1C31174G22
1C31177G01
1C31177G01
4-20mA AI/AO Locally powered analog inputs

4-20mA AI/AO Field powered analog inputs
2
4-20mA AI/AO - user defined Digital Inputs
Locally powered analog inputs
2
Field powered analog inputs
6
6
6
1C31174G03
1C31174G03
1C31174G23
1C31177G02
1C31177G03
1C31177G02
1C31174G23
1C31177G03
Pulse Accumulator module counts pulse for up to two input channels and provides the
information to the Controller. The Pulse accumulator may be used to count over a defined time
period to measure speed (frequency), count until instructed to stop, or can be used to measure
the duration of a pulse.
Pulse Accumulator subsystems
RANGE
ELECTRONICS
PERSONALITY
MODULE
MODULE
Field count: +5/12V (medium speed)

+ 24/48V (medium speed)
Field controls: +24/48V
1C31147G01
1C31150G01

+ 24/48V (medium speed)
1C31147G01
1C31150G02

+24/48V (medium speed)
1C31147G01
1C31150G03
Field count: +5V (high speed)
1C31147G02
1C31150G01
1C31147G02
1C31150G02
1C31147G02
1C31150G03
118
CHANNELS
+24/48V medium-speed configurations are CE Mark Certified.
REF_1005
Servo Driver module provides an interface to an electro-hydraulic servo actuator (servo-motor)

used to control a steam turbine.
Servo Driver subsystems
RANGE
CHANNELS
ELECTRONICS
PERSONALITY
MODULE
MODULE
16 Volts DC to a DC LVDT
60 mA into a 60 ohm coil (CD1) or
40 mA into an 80 ohm coil (CD2) or
40 mA into a 40 ohm (CD3) coil
1C31199G01
1C31201G01
19 Volts AC peak-to-peak 1 KHz to an AC LVT

8 mA into two 1000 ohm coils
1C31199G02
1C31201G02

1C31199G03
1C31201G02
16 Volts DC to a DC LVDT (Firmware)

1C31199G04
1C31201G01
19 Volts AC peak-to-peak 1 KHz to an AC LVT (Firmware)

1C31199G05
1C31201G02
19 Volts AC peak-to-peak 3 KHz to an AC LVT (Firmware)

1C31199G06
1C31201G02
REF_1005
119
Small Loop Interface module contains displays and keyboard inputs needed for an operator to
monitor and control the I/O functions of the Ovation Loop Interface or Valve Positioner module.
The SLIM is located external to the Ovation I/O cabinet and connected to the Loop Interface or
Valve Positioner via cable.
For more information on module configurations, refer to Assemblies - SLIM.
Speed Detector module provides the Controller with frequency measurements of a sinusoidal
or pulse train tachometer. A 16-bit output can be updated at a rate of 5 ms for over-speed
detection, and a 32-bit output can be updated at a variable rate for speed regulation.
Speed Detector has the G01 and the G03 subsystems. For more information refer to Subsystems
- (SD).
Valve Positioner module provides an interface to an electro-hydraulic servo actuator.
Governor valves, interceptor valves, extraction valves, and bypass valves can be controlled. The
module provides closed loop valve positioning control and also interfaces to a local operator
interface station (SLIM).
Valve Positioner Subsystems
RANGE
CHANNELS
ELECTRONICS
PERSONALITY
MODULE
MODULE
Valve Positioner Controller

17 Volts AC LVDT: 24.9 mA
1C31194G01
1C31197G01
1C31194G01
1C31197G02
1C31194G01
1C31197G03
17 Volts AC LVDT: 36 mA
1C31194G01
1C31197G04
24 Volts Fused DC LVDT: 50 mA
1C31194G01
1C31197G05
23.75 Volts AC LVDT: 24.9mA
1C31194G02
1C31197G01
23.75 Volts AC LVDT: 16.8 mA
1C31194G02
1C31197G02
23.75 Volts AC LVDT: 8.3 mA
1C31194G02
1C31197G03
23.75 Volts AC LVDT: 36 mA
1C31194G02
1C31197G04
24 Volts Fused DC LVDT: 50 mA
1C31194G02
1C31197G05
Numalogic Fast Ethernet Remote Node - is a remote I/O subsystem which provides an
interface to the Numalogic PC700 series Remote I/O. The NFE-RN is comprised of a base
assembly, power supplies, and redundant Numalogic Fast Ethernet Remote Node Controllers
(NFE-RNCs). The NFE-RNCs contain four Ethernet ports.
Numalogic Fast Ethernet Remote Node
120
PART
NUMBER
Numalogic Remote I/O Kit
5X00512
REF_1005
PART
NUMBER
Numalogic Remote Node Controller
5X00467
PWSN Power Supply Assembly
5X00522
Numalogic Remote I/O Backplane Assembly
5X00468
REF_1005
121
E C T I O N
Planning Ovation cabinets for your Ovation system
IN THIS SECTION
What are Ovation cabinets? ............................................................................................ 124
Cabinet configuration guidelines ..................................................................................... 125
Ovation cabinet components ........................................................................................... 126
Ovation Controller cabinet ............................................................................................... 128
Ovation Marshalling cabinet ............................................................................................ 133
Illustrations of Marshalling cabinet configurations .......................................................... 133
Ovation extended I/O cabinet .......................................................................................... 136
Remote Node cabinet ..................................................................................................... 138
Examples of cable access areas and floor bolting in Ovation cabinets .......................... 143
Examples of available usage area for field wiring ........................................................... 149
Weights of Ovation cabinets ........................................................................................... 151
Floor plan recommendations ........................................................................................... 153
Cleaning and maintenance guidelines for Ovation Controller cabinets .......................... 154
OCR400 Controller Modules ........................................................................................... 155
OCR161 Controller cover ................................................................................................ 157
User-supplied cabinets .................................................................................................... 161
REF_1005
123
8.1 What are Ovation cabinets?
8.1
What are Ovation cabinets?

Ovation cabinets are metal enclosures that contain the Ovation Controller, power supplies,
connections, and Ovation I/O modules in many different combinations.
You can modify the Ovation cabinet configuration to accommodate many different system
requirements and specifications. The final configuration for your system depends on the needs of
your system.
Ovation cabinets are divided into the following types:
Controller cabinets (see page 128).
Marshalling cabinets (see page 133).
Extended cabinets (see page 136).
Remote Node cabinets (see page 138).
Relay Panel cabinets (see page 142).
Workstation cabinets (see page 391).
Server cabinets (see page 392).
Ovation cabinets (including doors and enclosures) are approximately 2000 mm (78 in) in height,
but are available in the following approximate widths:
610 mm (24 in).
813 mm (32 in).
914 mm (36 in).
You can select the cabinet width that is best for your system needs.
124
REF_1005
8.2 Cabinet configuration guidelines
8.2
Cabinet configuration guidelines

The amount of Ovation I/O modules that you can configure in a cabinet depends upon the
following factors:
Physical dimensions of the cabinet.
Power must be available for each branch.
Standard I/O modules are housed in a Base Unit that contains two modules. Relay modules
are housed in a Base Unit that contains only one module. A Relay module Base Unit is 1.5
times longer than a Standard I/O Base Unit.
If Relay Output modules are mixed with Standard I/O modules on the same branch, always
start the Standard I/O module base in an odd-numbered module position on the branch
(positions 1/2, 3/4, 5/6, or 7/8).
CAUTION! The I/O addressing for the Ovation database is determined from the positions of
the bases installed in the cabinets.
Emerson strongly recommends that you install all possible bases in the right-most branch of
each side of a cabinet, even if they are not all filled with I/O modules. This will prevent
disruption of the database if additional I/O modules are installed in the future.
Install I/O modules in the left-most branch of each side of a cabinet from the TOP DOWN
Install I/O modules in the right-most branch of each side of a cabinet from the BOTTOM UP
Refer to the applicable Controller documentation for additional information about addressing
the I/O modules.
REF_1005
125
Approximately
500 mm
8.3 Ovation cabinet components
Controller
Controller
Controller
Controller
ROP
Remote
Node
Controller
ROP Trans Panel
4 1
3 2
2 4
1 7
TND
8
4
Controller
Marshalling
2
1
Extended
Remote Node
Figure 24: Examples of Standard

I/O and Relay Modules
Terminators
8.3
Ovation cabinet components

Ovation cabinets contain various components that work together to carry data from the field
devices to the Controller and then transmit commands from the Controller back to the field
devices. Some of the main components are:
Ovation modules:
Standard modules.
Relay Output modules.
Remote Function modules.
126
Wiring and cabling.
Terminator assemblies.
ROP Transition panels.
Remote Node Transition panels.
RRP Top Transition panels.
RRB Bottom Transition panels.
REF_1005
8.4 How many I/O modules can an OCR400 Controller support?
8.4
How many I/O modules can an OCR400 Controller support?

The Ovation OCR400 Controller contains one IOIC module. This module provides ports that
connect to and support the following I/O module locations:
Local Ovation I/O connects through ports L1 and L2.
Remote Ovation I/O connects through IOIC ports R3 (nodes 0 through 3) and R4 (nodes 4
through 7).
Local Q-line I/O connects through IOIC ports Q5 (DIOB 0) and R4 (DIOB 1).
Remote Q-line I/O connects through IOIC ports R3 (nodes 0 through 3) and R4 (nodes 4
through 7).
One OCR400 Controller can support the following I/O modules in various combinations:
Maximum of 128 local Ovation I/O modules.
Maximum of 512 remote Ovation I/O modules.
Maximum of 96 local Q-line I/O cards.
Maximum of 384 remote Q-line I/O cards.
Observe the following combination rules:
If you connect to remote Q-line I/O, you cannot connect to remote Ovation I/O. You can
connect to local Q-line through port Q5 (DIOB 0).
If you connect to remote Ovation I/O, you cannot connect to remote Q-line I/O. You can
connect to local Q-line through port Q5 (DIOB 0).
If you use both ports Q5 and R4 to connect to local Q-line I/O, you cannot connect to any
remote I/O.
You can always connect to local Ovation I/O.
Note: See the appropriate Ovation Controller User Guide for more information.)
8.5
How many I/O modules can an OCR161 Controller support?

The Ovation OCR161 Controller can contain up to two IOIC cards. These cards can support the
following I/O combinations:
PCRL card for local Ovation I/O.
PCRR card for remote Ovation I/O and remote Q-line I/O.
PCQL card for local Q-line I/O.
Using two IOIC cards, one OCR161 Controller can support the following I/O modules in various
combinations:
Maximum of 128 local Ovation I/O modules.
Maximum of 1024 remote Ovation I/O modules.
Maximum of 96 local Q-line I/O cards.
Maximum of 768 remote Q-line I/O cards.
Note: See the appropriate Ovation Controller User Guide for more information.)
REF_1005
127
8.6 Ovation Controller cabinet
8.6
Ovation Controller cabinet

A typical Ovation Controller cabinet contains the following:
Chassis containing provisions for a redundant pair of Ovation Controllers.

Each separate OCR400 Controller (5X00293 is CE Mark Certified) contains one
Processor module and one IOIC module. This IOIC module communicates with Ovation
I/O and Q-line I/O.
Each separate OCR161 Controller (4D33953 is CE Mark Certified) contains two PCI
expansion slots which can house up to two I/O Interface Controller (IOIC) cards.
Redundant power supplies with distribution panel.
ROP I/O transition panel.
Up to four terminated branches of Ovation I/O base units which house the I/O modules.
8.6.1 Controller cabinet configuration for local Ovation I/O

OCR400 Controller
When local Ovation I/O is required, use an IOIC module in the Ovation Controller to communicate
with up to two nodes of eight local I/O branches (128 I/O modules).
The standard Controller cabinet contains four branches. If additional local I/O modules are
desired, you can use Ovation Extended I/O cabinets to house four additional branches each (32
I/O modules). This maximum configuration consists of up to 128 modules.
OCR161 Controller
When local Ovation I/O is required, use a PCRL card in the Ovation Controller to communicate
with up to eight local I/O branches (64 I/O modules).
desired, you can use an Ovation Extended I/O cabinet to house four additional branches.
For larger local I/O subsystem, a second PCRL card can be added to each Controller to achieve
connections to an additional eight local I/O branches. These additional I/O modules would be
housed within additional Extended I/O cabinets. This maximum configuration consists of up to 128
modules.
128
REF_1005
8.6.2 Controller cabinet configuration for remote Ovation I/O

OCR400 Controller
When remote Ovation I/O is required, use an IOIC module in the Ovation Controller to
communicate with up to eight remote nodes. This allows communications with up to 512
modules.
In remote applications, the I/O modules are enclosed in Remote Node and/or Extended cabinets
which are remotely located from the Controller cabinet.
OCR161 Controller
When remote Ovation I/O is required, use a PCRR card in the Ovation Controller to communicate
with up to eight remote nodes. You can use a maximum of two PCRR cards in each Controller.
This allows communications with up to 16 remote nodes (up to 1024 modules).
In remote applications, the I/O modules are enclosed in Remote Node and/or Extended cabinets
which are remotely located from the Controller cabinet.
8.6.3 Controller cabinet configuration for mixed (local and remote) Ovation I/O
OCR400 Controller
When both local and remote I/O are required, use an IOIC module in the Ovation Controller to
communicate with up to eight remote nodes (up to 512 modules) and 16 local I/O branches (up
to 128 modules).
desired, you can use an Ovation Extended I/O cabinet to house four additional branches.
Remote I/O modules are enclosed in Remote Node and/or Extended cabinets which are remotely
located from the Controller cabinet. Up to eight remote nodes are supported in this mixed
configuration.
OCR161 Controller
When both local and remote I/O are required, use a PCRL card (for communication with up to
eight local I/O branches) and a PCRR card (for communication with up to eight remote nodes) in
the Ovation Controller. This maximum configuration consists of 64 local modules and 512
remote modules.
desired, use an Ovation Extended I/O cabinet to house four additional branches.
Remote I/O modules are enclosed in Remote Node and/or Extended cabinets which are remotely
located from the Controller cabinet. Up to eight remote nodes are supported in this mixed
configuration.
REF_1005
129
8.6.4 Controller cabinet configuration for local Q-Line I/O

OCR400 Controller
When a connection between the Ovation Controller and local Q-Line I/O is required, use an IOIC
module in the Ovation Controller. Each IOIC module can communicate with one existing local QLine bus (up to 96 Q-line I/O cards).
The Q-Line must be located near the Ovation Controller. Depending upon the application being
used, the Q-Line I/O can be in the Controller cabinet or in a Q-Line Extended I/O cabinet.
OCR161 Controller
When a connection between the Ovation Controller and local Q-Line I/O is required, use a PCQL
card in the Ovation Controller. Each PCQL card can communicate with one existing local Q-Line
bus (up to 96 Q-line I/O cards).
The Q-Line must be located near the Ovation Controller. Depending upon the application being
used, the Q-Line I/O can be in the Controller cabinet or in a Q-Line Extended I/O cabinet.
8.6.5 Controller cabinet configuration for remote Q-Line I/O

OCR400 Controller
When a connection between an Ovation Controller and remote Q-Line I/O is required, use an
IOIC module in the Ovation Controller. Typically, the Ovation Controller chassis is installed in a
modified WDPF DPU cabinet by an Emerson Migration Team. The maximum configuration
consists of 384 Q-line cards (eight nodes of four crates of 12 Q-line I/O cards).
Along with the cabinet modifications, the team replaces the QRC cards (which are housed in the
WDPF remote node cabinets) with QOR cards.
These QOR cards are then connected to Ovation Remote I/O Media Attachment Units (MAUs)
installed in the DPU cabinet, which are then connected to the IOIC card in the Ovation Controller.
(See WDPF Remote Q-Line Installation Manual.)
OCR161 Controller
When a connection between an Ovation Controller and remote Q-Line I/O is required, use a
PCRR card in the Ovation Controller. Typically, the Ovation Controller chassis is installed in a
modified WDPF DPU cabinet by an Emerson Migration Team. The maximum configuration
consists of 768 Q-line cards.
Along with the cabinet modifications, the team replaces the QRC cards (which are housed in the
WDPF remote node cabinets) with QOR cards.
These QOR cards are then connected to Ovation Remote I/O Media Attachment Units (MAUs)
installed in the DPU cabinet, which are then connected to the PCRR cards in the Ovation
Controller.
(See WDPF Remote Q-Line Installation Manual.)
130
REF_1005
8.6.6 Illustrations of Controller cabinet configurations
REF_1005
131
Note: Measurements are for the mounting plate, and do not include cabernet doors or
enclosures. Add four inches to cabinet height and width for enclosure measurements.
The zones (A - J) are used to assign locations during cabinet assembly and are not to be
confused with bus address locations.
The zones (A - D) are used to assign physical locations during cabinet assembly and are not to
be confused with bus address locations.
The module locations (1 - 8) are used to define bus address locations.
132
REF_1005
8.7 Ovation Marshalling cabinet
8.7
Ovation Marshalling cabinet

A typical Ovation Marshalling cabinet contains the following:
Chassis containing provisions for a redundant pair of Ovation Controllers.

Each separate OCR400 Controller contains one Processor module and one IOIC module.
This IOIC module communicates with Ovation I/O and Q-line I/O.
Each separate OCR161 Controller contains two PCI expansion slots which can house up
to two I/O Interface Controller (IOIC) cards.
8.8
Redundant power supplies with distribution panel.
ROP I/O transition panel.
Up to four terminated branches of Ovation I/O base units which house the I/O modules.
32 ring terminal-style half-shell termination panels.
Illustrations of Marshalling cabinet configurations
REF_1005
133
8.8 Illustrations of Marshalling cabinet configurations
134
REF_1005
8.8 Illustrations of Marshalling cabinet configurations
The zones (1 - 8) are used to define bus address locations.
The zones (1 - 8) are used to define bus address locations.
REF_1005
135
8.9 Ovation extended I/O cabinet
8.9
Ovation extended I/O cabinet

An Ovation Extended I/O cabinet contains the following:
DIN rails.
ROP I/O transition panels, or RRP (cabinet top) and RRB (cabinet bottom) transition panels.
Note: The Relay Output modules can be used with the RRP and RRB transition panels (instead
of the ROP panel). These panels allow one branch of up to eight relay bases to be housed in a
single side of an Ovation ventilated extended cabinet in two columns of four bases.
Redundant power supply with power distribution modules.
Two to four branches of Ovation I/O base units.
The Extended I/O cabinet can be used in either local or remote applications and is placed next to
a Controller cabinet or a Remote Node cabinet.
8.9.1 Illustrations of Extended cabinet configurations
136
REF_1005
8.9 Ovation extended I/O cabinet
REF_1005
137
8.10 Remote Node cabinet

An Ovation Remote Node cabinet contains the following:
Ovation Remote Node Controller (RNC).
Redundant power supply with power distribution modules.
I/O transition panels.
Up to four terminated branches of Ovation I/O base units.
The Remote Node Controller can communicate with up to eight Ovation I/O branches (8 modules
per branch for a total of 64 modules). Therefore, if more than 32 modules are desired, an Ovation
Extended I/O cabinet can be placed next to the Remote Node Controller cabinet and will house
additional modules).
In remote I/O applications, the Ovation OCR400 Controller cabinet must contain the IOIC module.
The Ovation OCR161 Controller cabinet must contain one PCRR card for every eight remote
nodes.
138
REF_1005
8.10.1 Illustrations of Remote Node cabinet configurations
REF_1005
139
140
REF_1005
REF_1005
141
8.10.2 Illustrations of Relay Panel cabinet configurations
These relay panel cabinets house relay panels that are used with Digital Output modules
(1C31122G01) and are not needed when using Relay Output modules (1C31219).
142
REF_1005
8.11 Examples of cable access areas and floor bolting in Ovation cabinets
8.11 Examples of cable access areas and floor bolting in Ova tion
cabinets
The following figures show the cable access area for five sizes of cabinets.
Four bolting locations are provided on the bottom of each of the Ovation cabinets shown. Bolt the
cabinet to the floor at the four locations for stability.
The following typical cabinet configurations are shown:
78 x 24 x 16 inch cabinet.
REF_1005
143
Figure 25: Bottom inside view of 78 x 24 x 16 inch cabinet (illustrating cable access)
144
REF_1005
REF_1005
145
146
REF_1005
REF_1005
147
95.50 mm
(3.76 in)
Back
718.31 mm
(28.28 in)
16 mm dia.
(0.63 in)
4 places
318.5 mm
(12.54 in)
412 mm
(16.22 in)
603.3mm
(23.75 in)
138.2mm
(5.44 in)
95.76 mm
(3.77 in)
Maximum Cable Entry Area
93.2 mm
(3.67 in)
93.2 mm
(3.67 in)
722.8 mm
(28.46 in)
909.32 mm
(35.8 in)
Front
* Overall dimension is based on cabinet with both left

and right side panels.
* Subtract 4.76 mm (0.19 in) if side panel is removed.
Figure 29: Bottom inside view of 78 x 36 x 24 inch cabinet (illustrating cable access and
floor bolting)
148
REF_1005
8.12 Examples of available usage area for field wiring
8.12 Examples of available usage area for field w iring

The following figures provide examples of cabinets showing available usage area for field wiring:
Controller Cabinet.
I/O Extended Cabinet.
Remote I/O Node Cabinet.
Note: The following figures show examples of three typical component configurations in a 78 x
24 x 24 cabinet. Since numerous configurations are possible, this manual only shows a few
typical configurations. See your project drawings and an Emerson Project representative for
specific details on your project configurations.
Back
609.6 mm
(24 in)
215.9 mm
(8.50 in)
175.7 mm
(6.92 in)
Power
Supply
120.65 mm
(4.75 in)
Mounting
Panel
602 mm
(23.70 in)
454.2 mm
(17.88 in)
170.63 mm
(6.72 in)
114.3 mm
(4.5 in)
23 mm
(0.91 in)
Controller
Front
Figure 30: Top view of Controller cabinet - available usage area for field wiring
REF_1005
149
8.12 Examples of available usage area for field wiring
Back
609.6 mm
(24 in)
Relay Base
I/O Branches
(Typical)
602 mm
(23.70 in)
454.2 mm
(17.88 in)
23 mm
(0.91 in)
152.4 mm
(6.0 in)
Mounting
Panel
160.53 mm
(6.32 in)
Front
Figure 31: Top view of I/O extended cabinet - available usage area for field wiring
150
REF_1005
8.13 Weights of Ovation cabinets
Back
609.6 mm
(24 in)
175.7 mm
(6.92 in)
Power
Supply
120.65 mm
(4.75 in)
454.2 mm
(17.88 in)
Mounting
Panel
602 mm
(23.70 in)
152.4 mm
(6.0 in)
160.53 mm
(6.32 in)
Front
Figure 32: Top view of remote I/O node cabinet - available usage area for field wiring

You must consider the weights of cabinets when you need to move them. Four eyebolt lifting lugs
are provided at the top corners of the cabinet for lifting.
When lifting, make certain that all four eyebolts are employed to ensure safe load distribution.
Typical Ovation I/O cabinet weights and dimensions
1
CABINE T TYPE
WEIGHT
DIMENSIONS (H
Ovation Workstation Cabinet:

Vented
183 kg
2083x601x890 mm
(403 lb)
(82x24x35 in)
Ovation Server Cabinet Vented
161 kg
2083x601x890 mm
1X00545
(354 lb)
(82x24x35 in)
D)
1X00518
Static load rating of 680 kg

(1500 lb)
OCR400 Controller
211.71 kg
2000 x 600 x 600 mm
5X00293
(466.75 lbs)
(78 x 24 x 24 in)
CE Mark Certified
REF_1005
151
CABINE T TYPE
WEIGHT
DIMENSIONS (H
OCR161 Controller
222.83 kg
2000 x 600 x 600 mm
4D33953
(491.25 lbs)
(78 x 24 x 24 in)
Extended I/O
208.14 kg
2000 x 600 x 600 mm
CE Mark Certified
(458.86 lbs)
(78 x 24 x 24 in)
Remote I/O
209.48 kg
2000 x 600 x 600 mm
Sealed
(461.83 lbs)
(78 x 24 x 24 in)
Remote I/O
209.48 kg
2000 x 600 x 600 mm
Ventilated
(461.83 lbs)
(78 x 24 x 24 in)
198.56 kg
2000 x 600 x 600 mm
(437.75 lbs)
(78 x 24 x 24 in)
209.67 kg
2000 x 600 x 600 mm
(462.25 lbs)
(78 x 24 x 24 in)
283.6 kg
2000 x 800 x 600 mm
(624 lbs)
(78 x 32 x 24 in)
301 kg
(664 lbs)
2000 x 914 x 600 mm
178.65 kg
2000 x 600 x 600 mm
(393.86 lbs)
(78 x 24 x 24 in)
Remote I/O
180.0 kg
2000 x 600 x 600 mm
Sealed
(396.83 lbs)
(78 x 24 x 24 in)
Remote I/O
180.0 kg
2000 x 600 x 600 mm
Ventilated
(396.83 lbs)
(78 x 24 x 24 in)
D)
CE Mark Certified
CE Mark Certified
CE Mark Certified
OCR400 Controller
OCR161 Controller
Marshalling
Marshalling
Extended I/O
(78 x 36 x 24 in)
Assumes Controller cabinet is populated with 16 I/O base assemblies (32 Electronic modules and 32
Personality modules).
152
REF_1005
8.14 Floor plan recommendations
8.14 Floor plan recommendations

The recommended floor plan for Ovation cabinets is shown below.
This floor plan allows for proper ventilation and provides convenient access for technicians.
Figure 33: Recommended cabinet floor plan
REF_1005
153
8.15 Cleaning and maintenance guidelines for Ovation Controller cabinets
8.15 Cleaning and maintenance guidelines for Ovation Controller

cabinets
The Ovation Controller cabinet requires no on-going maintenance. However, use the following
guidelines for best performance and appearance of your Controllers:
Periodically, inspect the cabinets for the following issues:

Corrosion.
Physical damage.
Fuses.
Ground cables.
Controller cooling fans.
Periodically, inspect the cabinets and clean the following components as needed:
Door air filters.
Cabinet floor.
Controller compartment.
I/O modules.
To ensure optimum air flow, check the air filters on the ventilated cabinets regularly and
replace if necessary.
You can access the air filters by removing the snap-on filter grills on the top and bottom of
each ventilated cabinet door. You can order replacement filters using Emerson part number
5A26317H03.
CAUTION! Only qualified service personnel should check and replace filters.
154
Routine cleaning can be done with a damp (water only) cloth. Ensure that no water is
splashed or spilled on the equipment. DO NOT use cleaning agents.
The cabinets are not watertight. Suitable measures should be taken to ensure that liquids are
not splashed onto or spilled into the equipment.
REF_1005
8.16 OCR400 Controller Modules

The OCR400 Controller contains two main modules:
Processor module. This module communicates with the Ovation network and provides nine
indicator LEDs that display information about the status of network communication.
IOIC module. This module communicates with I/O devices and provides ten indicator LEDs
that display information about the status of I/O communication.
Figure 34: OCR400 Controller modules

Note: The OCR400 Controller does not require a fan assembly.
8.16.1 To replace OCR400 Controller modules

Note: If you need to replace a module in the Controller, you must remove the IOIC module first.
When you re-install the modules, you must install the Processor module first.
1. Determine what Controller module needs to be replaced (Processor or IOIC module).
2. Power down the Controller before replacing modules.
Caution: Controllers must be powered down before removing or replacing modules.
3. Unlatch the blue corner latches on the module case.
REF_1005
155

4. Remove the old module from the Controller backplane.
5. Install the new module in the Controller backplane.
6. Use the blue corner latches on the module to secure it to the Controller backplane.
156
REF_1005
8.17 OCR161 Controller cover

CAUTION! The Ovation Controller has a hinged front panel cover that is used to protect the
Controller chassis.
These covers are equipped with different insert labels designed to match the type of I/O that is
communicating with the Controller. The following figures illustrate three different cover inserts:
Q-Line interface cover is used when a PCQL card is in the Controller and the Controller is
communicating with Q-Line I/O.
Ovation I/O interface cover is used when a PCRL or PCRR card is in the Controller and the
Controller is communicating with Ovation I/O.
Combination cover is used when a PCQL and a PCRL/PCRR card are in the Controller and
the Controller is communicating with Q-Line and Ovation I/O.
REF_1005
157
158
REF_1005
8.17.1 To open the OCR161 Controller cover

The Controller front cover should be in place to protect the Controller cards and cables from
accidental damage. If the cover must be removed for servicing, use the following procedure to
open the cover:
1. Locate the black latch at the bottom of the Controller cover (see page 157).
2. Push in the top of the latch, lift out the bottom of the latch until it clicks into place, and then
turn it 90 degrees to the right or left. This positions the latch in the Open position and
releases the metal latch inside the cover.
3. Swing the cover open.
REF_1005
159
Note: If necessary, the cover can be removed from the Controller by opening the door and lifting
it off the hinges.
8.17.2 To close the OCR161 Controller cover

Use the following procedure to close the cover (see page 157):
1. Make sure the black latch is in the Open position.
If it is not in the Open position, push in the top of the latch, lift out the bottom of the latch until
it clicks into place, and then turn it 90 degrees to the right or left.
2. Swing the cover shut.
3. Twist the black latch until it is in position to snap into place (the latch only closes in one
position).
4. Snap the latch closed. The Controller is now covered.
Note: If the cover has been removed from its hinges, replace it on the hinges and close it as
described above.
8.17.3 Removing the OCR161 Controller fan assembl y

The Controller fan assembly (located above the Controller (see page 157)) should be in place to
provide air flow for heat removal from the Controller. If the fan assembly must be removed for
servicing, use the following procedure:
1. Locate the black latch in the center of the fan assembly.
2. Push in the top of the latch, lift out the bottom of the latch until it clicks into place, and then
turn it 90 degrees to the right or left. This positions the latch in the Open position and
releases the metal latch inside the cover.
3. Pull out the fan assembly.
CAUTION! When a fan is removed from the chassis, it continues to spin for a few seconds
due to inertia. Since there are no finger guards on the fan, a moving parts hazard exists until
the fan stops spinning.
8.17.4 Replacing the OCR161 Controller fan assembly

1. Make sure the black latch is in the Open position (see page 157). If it is not in the Open
position, push in the top of the latch, lift out the bottom of the latch until it clicks into place,
and then turn it 90 degrees to the right or left.
2. Push the fan assembly into the chassis.
3. Snap the top of the cover in place.
4. Twist the black latch until it is in position to snap into place (the latch only closes in one
position).
5. Snap the latch closed. The fan is now installed.
160
REF_1005
8.18 User-supplied cabinets
8.18 User-supplied cabinets

You may want to place the Ovation Controller and associated components in user-supplied or
user-specified cabinets. This may occur when reusing cabinets from prior equipment. In order to
maintain the continued safety of the Ovation Controller and associated components, ensure that
the following conditions apply:
The Controller, I/O modules, and associated components must be mounted on a DIN rail. The
DIN rail must be mechanically and electrically secured to an appropriately sized steel plate.
The cabinet must be steel on all sides with an Ingress Protection (IP) rating of 20 or higher.
All parts of the cabinet should be a minimum of 12 mm (0.47 in) from the terminal blocks and
any openings in the cabinet should be at least 100 mm (3.94 in) away from any terminal
block.
All surfaces of the cabinet and the steel plate must be made electrically common by use of
grounding conductors and also common to the Protective Earth stud of the power distribution
panel. The Protective earth stud can be identified with a circled ground symbol. Further, the
cabinet, plate and grounding conductors must be substantial enough that a fault current of
30A can safely pass from the cabinet to the Protective Earth Stud of the power distribution
panel.
The volume of the cabinet, combined with any cooling mechanisms, should be sufficient to
ensure that the temperature inside of the cabinet does not exceed 60 C (140 F). Under no
circumstances should the metallic accessible areas of the cabinet exceed 70 C (158 F), nor
should the nonmetallic accessible areas of the cabinet exceed 85 C (185 F).
Maintain proper system cabinet grounding in order to ensure EMC characteristics are not
compromised when installing components in alternate cabinets. However, overall system
radiated electromagnetic immunity and emissions must be evaluated to determine any
impacts.
REF_1005
161
E C T I O N
IN THIS SECTION
How is power distributed in an Ovation system? ............................................................ 163
Connecting the power mains to an Ovation cabinet ....................................................... 175
Using power supply modules .......................................................................................... 179
Calculating Ovation power supply requirements (drawn from +24V main or auxiliary power
supply) ............................................................................................................................. 184
Monitoring power supply status ....................................................................................... 195
Using an external power supply ...................................................................................... 197
9.1
How is pow er distributed in an Ovation s ystem?

Note: Ovation Equipment is designed for installation in an Overvoltage Category II environment
per IEC 60664. Overvoltage Category II Equipment is designed for connection to the permanent
electrical installation of a building.
Power for Ovation systems is distributed in the following methods:
The primary and backup input power cables (maximum size = 12 AWG
2
(3.66 mm )) are connected to the Power Distribution Module (PDM) (see page 170). The
PDM is applicable for AC and DC power supplies.
In the CE Mark certified cabinets, a line filter precedes the PDM (see page 175).
There is a single wiring harness between the PDM and each power supply. This harness
provides AC/DC power to the power supply and routes DC power (main and auxiliary) back to
the PDM.
Ovation systems can use AC or DC cabinet power supplies, or a combination of both. The
type used is dependent upon the needs of the system application. (AC power supplies and
AC mains are supported in CE Mark certified systems.)
The PDM distributes power from cabinet power supplies to the following components:
I/O transition panels (ROP, RRP, and RRB) (see page 171).
Remote node transition panel (TND) (see page 171).
OCR400 Controller chassis (see page 173).
OCR161 Controller chassis. (see page 174)
Cabinet fans (OCR161 only).
Additional cabinets.
REF_1005
163
9.1 How is power distributed in an Ovation system?
The PCPS power supply module in the Controller chassis picks up 24 VDC main from the
Controller backplane (see page 174) and converts it to +5 VDC and +/- 12 VDC for use by the
Controller boards. The Controller contains two PCPS power supply modules (one for the left
Controller and one for the right Controller).
Redundant main and auxiliary power is supplied to the CBO backplane and transition panels
through a harness and then passed through the Two Way Interface (TWI) connectors to I/O
modules.
Fuses are provided on the Controller backplane (CBO), and I/O transition panels (ROP, RRP,
RRB, and TND) for the auxiliary power supplies.
Each I/O electronics module is equipped with auctioneering diodes for regulating redundant
main power.
A jumper connector (5A26471G01 (see page 170)) is installed. This connects the auxiliary
and main power supply returns together locally at the distribution panel (P11-2 to P11-5). The
auxiliary and main power supply should remain tied locally at this point.
If this connector position is required for additional power distribution, remove the jumper
connection and then use cable 5A26472. This cable incorporates the same jumper
connection into the connector assembly.
Note: To avoid ground loops, tie the auxiliary return to ground at one point only. When
employing the recommended jumper (5A26471G01) or cable (5A26472), the auxiliary and main
are tied together and referenced to earth ground per the distribution panel shorting bar.
Therefore, do NOT ground the auxiliary return at any other point in the field.
164
REF_1005
9.1.1 Example of OCR400 Controller/Marshalling cabinet (with local and remote

cabling)
REF_1005
165
9.1.2 Example of OCR161 Controller/Marshalling cabinet (with local and remote

cabling)
+24V main, +24V
AUX (internal)
Primary AC/DC Line *

Input (external)
Line Filter
(CE Mark certified
system only)
Backup
Controller
Backup AC Line
Input (external)
+24V main, +24V

AUX (internal)
P5 P7
P12
Backup
Power Supply
+24V main, +24V

AUX, and AC/DC
line (internal)
Primary
Power Supply
PCRR Card
PCRL Card
P1 P2
NIC
Processor
J26
PCPS Converter
PCRR Card
PCRL Card
J25
NIC
PCPS Converter
Processor
Primary
Controller
Power Supply Alarm

Cable from Extended
I/O Cabinet Power
Distribution
P13
J3
J4
P7
P1
P8
P2
Local I/O
Communications
Cable (internal)
Power
Distribution
Module
+24V to Cabinet Fans

(internal)
To extended Local
I/O Cabinet
(external)
Br 5
Local I/O
Transition Panel
(ROP)
I/O
Base and
Modules
I/O
Base and
Modules
Network Cables
to Switches
(external)
Primary
AUI Cable
(internal)
Backup
AUI Cable
(internal)
Remote
Node #1
Primary
Fiber-Optic
Cable
(external)
Typical Customer
Supplied Field
Wiring (external)
Notes
Internal cables
do not exit cabinet.
MAU
Attachment Unit
Base
and Modules
Remote
Node #1
Backup
Fiber-Optic
Cable (external)
External cables
exit cabinet.
Earth ground
cables not shown.
Br 1
Br 2
Cabinet
Front
Br 3
Br 4
Local I/O
Bus
Terminators
Cabinet
Back
* AC Power Supplies are applicable for CE Mark Certified systems.
166
REF_1005
9.1.3 Example of extended I/O cabinet (illustrating cables and standard I/O)
Line Filter
(CE Mark certified
system only)
+24V main, +24V

AUX (internal)

Input (external)
Backup AC/DC Line
Input (external)
Local I/O Communications

Cable from Controller or Remote
Node Cabinet (external) Br "n-1"
Primary
Power Supply
+24V main, +24V

AUX, and AC/DC
line (internal)
+24V main, +24V

AUX (internal)
P1
P5
P7
P12
Backup
Power Supply
P1 P2
P13
P2
P1
P7
P8
Power
Distribution
Module
+24V to Cabinet Fans

(internal)
To extended Local
I/O Cabinet
(external) Br "n+4"
P2
Local I/O
Transition Panel
(ROP)
Local I/O
Transition Panel
(ROP)
Local I/O
Communications
Cable (internal)
I/O
Base and
Modules
I/O
Base and
Modules
Typical Customer
Supplied Field
Wiring (external)
Notes
Internal cables
External cables
exit cabinet.
Earth ground
cables not shown.
Br "n"
Br "n + 1"
Cabinet
Front
Br "n + 2"
Br "n + 3"
Local I/O
Bus
Terminators
Cabinet
Back
REF_1005
167
9.1.4 Example of extended I/O cabinet (illustrating cables and relay output
modules)
Local I/O Communications
Cable from Controller or Remote
Node Cabinet Branch "n-1" (external)
P1
P7 P8
+24V main,
+24V aux (internal)
Line Filter
(CE Mark certified
system only)

Input (external)
Backup AC/DC Line
Input (external)
P2
Relay Base
Transition Panel
(RRP)
P1 P2
Backup
Power Supply
+24V main,
+24V aux (internal)
Primary
Power Supply
+24V main,
+24V aux, and
AC/DC line (internal)
P5 P7
P12
P13
P1
P7
P8
P2
Local I/O
Communications
Cable (internal)
"n+1"
Power
Distribution
Module
+24V to DC Fans
(internal)
To extended Local
I/O Cabinet
Branch "n+3"
(external)
Local I/O
Transition Panel
(ROP)
Standard I/O
Base and
Modules
Relay Output
Base and
Module *
Typical Customer
Supplied Field
Wiring (external)
Notes
Internal cables
External cables
exit cabinet.
Earth ground
cables not shown.
Relay Base
Transition Panel
(RRB)
Branch "n"**
Cabinet
Front
Local I/O
Bus
Terminators
Branch "n+1"
Branch "n+2"
Cabinet
Back
* AC Power Supplies and Relay Output modules/bases are applicable for CE Mark Certified systems.
** With the RRP/RRB, one branch in the addressing scheme (containing 8 Relay Output modules) uses both the left and right side din rails.
168
REF_1005
9.1.5 Example of Ovation Remote Node cabinet (illustrating cables)
Cabinet
Back

Input (external)
Line Filter
(CE Mark certified
system only)
Backup AC/DC Line

Input (external)
Remote Node Controller (RNC)

Base and Modules
J7
+24V main, +24V

AUX, and AC/DC
line (internal)
Primary
Power Supply
Primary
Fiber-Optic
Cable
P5
Backup
Fiber-Optic
Cable
P7
Backup
Power Supply
P1 P2
+24V main, +24V

AUX (internal)
P12
P1 P7
+24V to DC Fans
(internal)
To extended Local
I/O Cabinet
(external) Br 5
P13
+24V main, +24V

AUX (internal)
Power
Distribution
Module
P8
Remote Node
Transition Panel
(TND)
P2
Local I/O
Transition Panel
(ROP)
Local I/O
Communications
Cable
I/O Base
and
Modules
Typical Customer
Supplied Field
Wiring (external)
Notes
Internal cables
External cables
exit cabinet.
Earth ground
cables not shown.
Br 1
Br 2
Br 3
Br 4
Local I/O
Bus
Terminators
REF_1005
169
9.1.6 Example of Ovation Power Distribution Module (PDM)
170
REF_1005
9.1.7 Examples of transition panels
Figure 35: Ovation I/O Transition Panel (ROP)
Figure 36: Ovation Remote Node Transition Panel (TND)
REF_1005
171
+24V and AUX Power Connectors
Local I/O Bus Cable from Branch "n-1"
(P7 supplies power to P8, to +24V fans, and to

the left side of Branch "n")
IN
AUX Supply Fuses for
left side of Branch "n"
Local I/O Bus Cable to Branch "n+1"

(if existing)
OUT
P7
P8
Bus Termination for Branch "n"
+24V Power Connectors

for Cabinet Fans
PGND
F1
F2
PGND
TWI Connector to left side of Local Branch "n"

(starting point of branch addressing)
TWI Connector to right side of Local Branch "n"
Note
The RRP is typically used in conjunction with the RRB.
Figure 37: Relay Base Transition Panel (RRP at top of branch)
Figure 38: Relay Base Transition Panel (RRB at bottom of branch)
172
REF_1005
9.1.8 Example of Controller OCR400 backplane
REF_1005
173
9.1.9 Example of Controller OCR161 backplane

C
Connector
supplies power to PCPS Power Supplies, Controller fans, and Branches 1 and 2
Power Supply Connector
Supplementary Status Connector
(Power and Status)
(Status Only)
J25
J26
Fan Connectors
Reset Cable Connector
Controller #2
Reset Cable Connector
Controller #1
Left PCPS
Power Supply
delivers +5V,
12V to cards
in Controller 1
Slot
L5
Slot R1
AUX Supply
Fuses
Left-side TW
I Connector
(starting point of branch addressing)
174
R2
R3
R4
IOIC Card 2
L4
IOIC Card 1
L3
L2
NIC Card
L1
Processor
PCPS
Power Supply
IOIC Card 2
J4
IOIC Card 1
J3
NIC Card
Used when
IOICs are in
L5 and R5.
Branches
1 through 8
are used.
J25
Processor
PCPS
Power Supply
Local
I/O Cable
Left-side
Right PCPS
Power Supply
delivers +5V,
12V to cards
in Controller 2
R5
Right-side TW
I Connector
Local
I/O Cable
Right-side
Used when
IOICs are in
L4 and R4.
Branches
3 through 8
are used.
The left-side
TWI is used
for Branch 1,
and the
right-side
TWI is used
for Branch 2.
REF_1005
9.2 Connecting the power mains to an Ovation cabinet
9.2
Connecting the power mains to an Ovation cabinet

There are currently two methods for connecting the power mains to an Ovation cabinet:
For a CE Mark Certified system, you must connect the AC Mains to a Line Filter Assembly.
The Line Filter Assembly is typically located at the back of the cabinet in the lower left corner.
However, the Line Filter Assembly can be installed at any corner of the cabinet that is the
point of entry for the AC Mains (the terminal blocks should be on your left when facing the
cabinet). Select the location that minimizes the length of AC cord within the cabinet.
CAUTION! If the assembly is relocated within the cabinet, be sure the ground strap connection
to the assembly mounting panel is reattached.
You can connect the AC/DC Mains to the Power Distribution Module. The Power Distribution
Module is located on the back of the cabinet between the power supplies.
9.2.1 To connect the AC Mains to the line filter assembly (CE Mark Certified)
Note: Currently, only AC power supplies and AC mains are supported in CE Mark Certified
systems.
The AC line filter is only required for the EMC cabinet CE Mark system approach. This is not a
requirement for the Non-EMC cabinet CE Mark system.
1. Remove the service cover from the line filter by removing the two screws that hold the door in
place.
2. Route the AC Mains into the cabinet through the cable clamps in the Filter Assembly. The
2
maximum cable size is 12 AWG (3.66 mm ).
3. Connect the AC Mains to the appropriate PRI (primary) and SEC (secondary) terminal blocks
(be sure the insulation on the conductors is continuous to the terminal block).
4. To ensure proper protective earthing of the Ovation cabinet, connect the earth ground
conductor in the AC Mains cord to the earth terminal on the terminal block (circled earth
symbol). A properly installed EMC ground provides protective earthing of the cabinet;
however, relying on this ground alone may violate National Electrical Codes.
5. Tighten the cable clamps to secure the cables and replace the service door.
REF_1005
175
Power Supply
Breaker / Switch
Power Distribution
Module
Power Supply
Breaker / Switch
Controller
Controller
Note: In the event that only one AC Main cable is required, install a three conductor patch
jumper between the PRI and SEC connector. This patch jumper must have the same electrical
ratings as the AC Mains cord(s).
Line
Filter
Assembly
Terminator
Branch 1
Branch 2
Front
Branch 3
Branch 4
Back
Figure 39: Line filter assembly in CE Mark Certified Ovation OCR400 cabinet (typical
location)
176
REF_1005
Power Supply
Breaker / Switch
Power Distribution
Module
Power
Switch
(one per
controller)
Power Supply
Breaker / Switch
Controller
Controller
(cover removed)
IOIC Cards (1 and 2)
Line
Filter
Assembly
Terminator
Branch 1
Branch 2
Front
Branch 3
Branch 4
Back
Figure 40: Line filter assembly in CE Mark Certified Ovation OCR161 cabinet (typical
location)
REF_1005
177
Cover in Place
Screws
Factory installed
electrical
components
are located here.
No configuration
needed.
Cover Removed
Terminal
Block
Factory installed
electrical
components
are located here.
No configuration
needed.
SEC
PRI
Cable Clamp
Secondary
AC Cord
Primary AC Cord
(maximum cable size
is 12 AWG (3.66 mm2))
Figure 41: Line filter assembly
9.2.2 To connect the AC/DC Mains to the Power Distribution Module (PDM)
1. Route the AC/DC Main cords into the cabinet. The maximum cable size is 12 AWG (3.66
2
mm ).
2. Connect the AC/DC Mains to the appropriate P1 (primary) and P2 (secondary) terminal
blocks.
178
REF_1005
9.3 Using power supply modules

3. To ensure proper protective earthing of the Ovation cabinet, connect the earth ground
conductor in the AC/DC Mains cord to the earth terminal on the connector (circled earth
symbol). A properly installed EMC ground provides protective earthing of the cabinet;
however, relying on this ground alone may violate National Electrical Codes.
Note: In the event that only one AC/DC Main cable is required, install a three conductor patch
jumper between the P1 and P2 connector. This patch jumper must have the same electrical
ratings as the AC/DC Mains cord(s).
9.3
Using pow er supply modules

Ovation power supply modules are located in the Controller cabinet and provide power to the
Controller and I/O modules (main power), and also to any supported field items (auxiliary power).
9.3.1 Power supply features

Ovation power supplies provide the following features:
Wide range inputs.

85 - 264 VAC
90 - 250 VDC
47 - 63 Hz, AC Models.
AC Input Power Supply.

Input Inrush Current =
33A, 5mSec Max, Vin = 115VAC

65A 5 mSec Max, Vin = 230VAC
Input Current =
7.2 A rms, Vin = 90VAC

3.1 A rms, Vin = 198VAC
DC Input Power Supply.

Input Inrush Current =
33A, Vin = 115VDC
Input Current =
7.9 A DC, Vin = 90VDC
Reverse polarity and Improper Lead Connection.

You should always make proper connections to the power distribution module which
provides power to the Ovation power supplies. This ensures proper operation and safety
to the Ovation cabinet and associated electronics. The power supply units are tolerant of
a reversal at the inputs, but proper terminations are important in maintaining the overall
integrity and safety of the system.
Improper voltage level and/or frequency.

You should always maintain proper input voltage and frequency ranges for the applicable
power supply unit. Failure to do so could cause the power supply output to go beyond the
specification limits or cause the output to shut off which could result in a system upset.
Recommended Power Supply Replacement Procedure.

If a failure occurs in the redundant Ovation Powering scheme, Emerson recommends that
you follow the power supply replacement procedure outlined in Ovation I/O Reference
Manual.
REF_1005
179
Main power supply and auxiliary power supply can be contained in the same module.
24 VDC Main and 24/48 VDC auxiliary outputs.

Power factor corrected
Hot swap capability (online replacement in redundant configurations)
32 mS hold-up time
LEDs on the front panel indicate conditions of input/output voltages.
INPUT
LEDs
ON
1
POWER
Output 1
OFF
0
MAIN
+
-
Output 2
Test
Points
AUX
+
-
POWER
SUPPLY
Fas te n Ground Scre w Be fore Ope rating Pow e r Supply
Figure 42: Typical power supply front panel (AC input version)
9.3.2 Available power supply modules

There are Ovation power supply modules available for AC or DC input voltage.
AC module 1X00416H01, H02, and H05.

Uses 115/230 VAC input voltage (85 to 264 Vrms).
Input frequency range 47 to 63 Hz.
DC module 1X00416H03, H04, and H06.

Uses 90 to 250 VDC input voltage.
180
REF_1005

There are two types of power supply modules available (for AC or DC input):
Auxiliary power supplies that provide power only to field items (such as analog input current
loops and relay coils).
Main and auxiliary power supplies, combined into one module, that supply power to the
Controller, I/O modules, and field items.
AC Power Supply Modules (1X00416H01, H02, and H05)

MODULE
1, 2
1X00416H01
OUTPUT
DESCRIPTION
300 Watt - 24 Volt
Dual output - Single main
200 Watt - 24 Volt

1X00416H02
200 Watt - 48 Volt
1X00416H05
300 Watt - 24 Volt

200 Watt - 48 Volt
Single auxiliary
Single auxiliary output - No main

Single auxiliary
1X00416H01 supersedes 1X00024H01, 4D33900G13 and 4D33900G19 for new applications and
replacements.
1X00416H02 supersedes 1X00024H03 and 4D33900G15 for new applications and replacements.
2
1X00416H01, H02, H05 are UL1950 recognized components (File #E150340) and may be used in Ovation
CE Mark Systems.
3
The auxiliary output has an isolation diode placed in series with the internal power supply auxiliary output
voltage.
DC Power Supply Modules (1X00416H03, H04, and H06)

MODULE
1X00416H03
OUTPUT
DESCRIPTION
300 Watt - 24 Volt
200 Watt - 24 Volt

1X00416H04
200 Watt - 48 Volt
1X00416H06
300 Watt - 24 Volt

200 Watt - 48 Volt
Single auxiliary
Single auxiliary output - No main

Single auxiliary
1X00416H03 supersedes 1X00024H04, 4D33925G09 and 4D33925G10 for new applications and
replacements.
2
The auxiliary output has an isolation diode placed in series with the internal power supply auxiliary output
voltage.
REF_1005
181
9.3.3 Power supply limits

The following limits are given per power supply:
Main Power Supply
The Main portion of the power supply module supplies +24 VDC to the Controller and the I/O
modules.
The sum of the Controller power and the total I/O power MUST be less than the 300 watt capacity
of the Main power supply.
Auxiliary Power Supply
The Auxiliary portion of the power supply module typically powers the relay panels, field
transmitters, and single-ended 24/48 Volt Digital Input modules.
The sum of the relay panels, transmitter, and Digital Input power MUST be less than the 200 watt
capacity of the Auxiliary power supply.
9.3.4 Controller Cabinet On/Off Controls

Cabinets contain the following switches:
Cabinet circuit breaker/on/off switch (see page 182).
Controller power switch (see page 183).
Cabinet circuit breaker/on/off switch

Each cabinet power supply provides a cabinet circuit breaker/on/off switch. The two power
supplies form a redundant (auctioneered) pair.
Switching off power to the first power supply (or losing the first power supply), while the second
power supply is working, will NOT cause loss of power to the Controller, I/O, or field devices using
power supply auxiliary voltage.
Switching off power to both power supplies (or losing both power supplies) powers down the
entire cabinet, as well as any field devices that are powered from the cabinet.
Switching on power to either power supply in the redundant pair provides power to the Controller,
energizes the I/O modules, and energizes any field devices using power supply auxiliary voltage.
For correct operation of the redundant powering scheme, both cabinet circuit breakers/on/off
switches must be energized. Each power supply has an independent switch in order to power up
these units independently.
182
REF_1005

Controller power switch
Each redundant Ovation Controller has a Controller on/off power switch. Switching off a
redundant Controller powers down the processor card, the IOIC card(s), and the NIC card
associated with the Controller. However, this will NOT power down the partner Controller or any
of the I/O and field devices associated with the cabinet.
Even if both redundant partner Controllers are switched off, this will NOT power down the I/O or
any field devices associated with the cabinet.
Once the cabinet circuit breaker on/off switch is energized for the redundant powering scheme,
the Controller power switch will energize the Controller. Once energized, the Controller performs
its startup routine and begins executing application code if the Controller was previously
programmed with application code. Each Controller has an independent power switch. Both
Controllers must be energized for proper operation in a redundant Controller scheme.
Figure 43: Ovation OCR400 Controller cabinet configuration (illustrating controls)
REF_1005
183
9.4 Calculating Ovation power supply requirements (drawn from +24V main or auxiliary power supply)
9.4
Calculating Ovation pow er suppl y requirements (draw n from

+24V main or auxiliary pow er supply)
The following sections provide information about power supply requirements that are drawn from
power supplies:
I/O cabinets (main and aux power drawn from power supply) (see page 184).
Analog I/O modules (main and aux power drawn from power supply) (see page 186).
Bus interface modules (main and aux power drawn from power supply). (see page 188)
Digital I/O modules (main and aux power drawn from power supply) (see page 189).
Specialty I/O modules (main and aux power drawn from power supply) (see page 193).
Remote function modules (main and aux power drawn from power supply) (see page 195).
9.4.1 Calculating power supply requirements for I/O Cabinet components

The following table lists the power an I/O cabinet component draws from the +24V Main Power
Supply or Auxiliary Power Supply when the component is installed within the cabinet.
Do NOT use this table to determine the power drawn from the AC or DC Mains power supply.
Refer to Electrical information for Ovation equipment (see page 12) instead.
Power supply requirements for Ovation I/O cabinet components
(power supply efficiency is not included)
COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER (W)
(TYPICAL)
AUX POWER (W)

(TYPICAL)
Controller Cabinet
Not Applicable
18 W
Not Applicable
Not Applicable
18 W
Not Applicable
Not Applicable
18 W
Not Applicable
Not Applicable
18 W
Not Applicable
Not Applicable
24 W
Not Applicable
Not Applicable
18 W
Not Applicable
Not Applicable
18 W
Not Applicable
Not Applicable
18 W
Not Applicable
(cabinet + power supply fans)

OCR400 or
OCR4161Controller
Marshalling Cabinet
Extended I/O Cabinet
Remote I/O Cabinet (ventilated)
Remote I/O Cabinet (sealed)
EMC Controller Cabinet
EMC Extended I/O Cabinet
EMC Remote I/O Cabinet (ventilated)
184
REF_1005
COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER (W)
(TYPICAL)
AUX POWER (W)

(TYPICAL)
EMC Remote I/O Cabinet (sealed)
Not Applicable
24 W
Not Applicable
5X00127
20 W
Not Applicable
5X00127
40 W
Not Applicable
Single OCR161 Controller:
4D33942G02
43.2 W
Not Applicable
1 Processor card
(hinged)
86.4 W
Not Applicable
5.8 W
Not Applicable
12 W
Not Applicable
13.2 W
Not Applicable

Single OCR 400 Controller:
1 Processor card
1 IOIC card
1 Fan
2 Processor cards
2 IOIC cards
2 Fans
1 NIC card
1 IOIC card
OR
4D33901G02
1 Fan
4D33942G01
2 Processor cards
(hinged)
2 NIC cards
2 IOIC cards
OR
4D33901G01
2 Fans
4D33943G01-EMC
(hinged)
OR
4D33937G01
Extra IOIC card in Dual OCR161 Controller
3A99158 PCRL
3A99190 PCRR
3A99141 PCQL
Redundant Remote Node Controller

module (in Remote Node Cabinet)
1C31203 (E)
1C31179 (E)
1C31181G01-G04 (P)
REF_1005
1C31204G01, G03
(P)
185
9.4.2 Calculating power supply requirements for Analog I/O modules

The following table lists the power an Analog I/O module draws from the +24V Main Power
Supply or Auxiliary Power Supply when the component is installed within the cabinet.
Power supply requirements for Ovation Analog I/O modules
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER (W)

(TYPICAL)
Analog Input (13-bit)
1C31113G01-G06
(E)
2.5 W
Not Applicable
2.5 W
3.84 W
T/C, Volts and Field Powered mA
1C31116G01,
G02, G04 (P)
1C31113G05 (E)
Local Powered mA
1C31116G03 (P)
(8 channels on @20mA
each)
(0.48W per locally
powered channel)
1C31224G02 (E)
Volts (+/- 1 Volt)
1C31227G02 (P)
1C31224G01 (E)
Field and Local Powered mA
1C31227G01 (P)
2.4 W
Not Applicable
2.4 W
3.84 W
(8 locally powered
channels on @20mA
each)
(0.48W per locally
powered channel)
Analog Input (14-bit) (High Speed)
5X00070G02 (E)
( 100mV, 250mV, 1V Volt)
1C31227G02 (P)
5X00070G03 (E)
( 5V, 10V Volt)
1C31227G02 (P)
5X00070G01 (E)
Field and Local Powered mA
1C31227G01 (P)
2.4 W
Not Applicable
2.4 W
Not Applicable
2.4 W
3.84 W
(8 locally powered
channels on @20mA
each)
(0.48W per locally
powered channel)
Analog Input (14-bit) (Medium

Speed)
5X00070G04 (E)
2.4 W
Not Applicable
1C31116G04 (P)
( 20mV, 50mV,
100V) (Thermocouple)
186
REF_1005
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER (W)

(TYPICAL)

Speed)
5X00070G05 (E)
2.4 W
Not Applicable
2.4 W
Not Applicable
2.4 W
0.19 W
1C31116G04 (P)
( 20mV, 50mV,
100V) (Thermocouple)
Speed)
5X00070G04 (E)
1C31116G01 (P)
( 20mV, 50mV, 100V)

5X00070G02 (E)
( 1mA 2 wire local powered)
1C31116G03 (P)
(8 locally powered
channels on @1mA
each)
(0.024W per locally
powered channel)
5X00070G02 (E)
( 1mA 4 wire field powered)
1C31116G02 (P)
HART Analog Input
5X00058G01 (E)
2.4 W
Not Applicable
1.2 W
5.64 W
5X00059G01 (P)
(8 locally powered
channels on @20mA
each)
1.8 W + 0.48W per
locally powered channel)
HART High Performance Analog

Input
5X00106G02 (E)
4.1 W
5X00109G01 (P)
3.84 W
(8 locally powered
channels on @20mA
each)
(0.48W per locally
powered channel)
Analog Output
(Voltage)
1C31129G01, G02
(E)
2W
Not Applicable
4W
Not Applicable
1.2 W
6W
4.56 W
Not Applicable
3.6 W
Not Applicable
1C31132G01 (P)
Analog Output
(Current)
1C31129G03, G04
(E)
1C31132G01 (P)
HART Analog Output
5X00062G01 (E)
5X00063G01 (P)
HART High Performance Analog

Output
5X00167G01 (E)
1X00188H01
(molded plastic
cavity insert)
RTD Input
1C31161G01 (E)
(50Hz/60Hz filtered inputs)
1C31164G01 (P)
(4 channels)
REF_1005
187
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER (W)

(TYPICAL)
RTD Input
1C31161G02 (E)
3.6 W
Not Applicable
(4 channels)
1C31164G02 (P)
RTD Input
5X00119G01 (E)
3.6 W
Not Applicable
(8 channels)
5X00121G01 (P)
RTD Input
5X00119G02 (E)
3.6 W
Not Applicable
(8 channels)
5X00121G01 (P)
9.4.3 Calculating power supply requirements for Bus interface modules

The following table lists the power a Bus interface module draws from the +24V Main Power
Supply or Auxiliary Power Supply when the module is installed within the cabinet.
Power requirements for Ovation bus interface modules
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER (W)

(TYPICAL)
AUX POWER
(W) (TYPICAL)
Foundation Fieldbus
5X00301G01 (E)
1.82 W
0.4128 W per channel
5X00327G01 (P)
Foundation Fieldbus Power
Conditioner
1X00418H01
Not Applicable
1.8 W per segment
Profibus
5X00300G01 (E)
3.84 W
Not Applicable
3.17 W
0.576 W per channel
1.68 W
Not Applicable
5X00321G01 (P)
DeviceNet
5X00376G01 (E)
5X00375G01 (P)
Ethernet Link Controller
5X00419G01 (E)
1X00569H01
188
REF_1005
9.4.4 Calculating power supply requirements for Digital I/O modules

The following table lists the power a Digital I/O module draws from the +24V Main Power Supply
or Auxiliary Power Supply when the component is installed within the cabinet.
Note that (E) designates an Electronics module, (P) designates a Personality module, and (R)
designates a Relay panel.
Power supply requirements for Ovation Digital I/O modules
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER (W)

(TYPICAL)
Contact Input
1C31142G01 (E)
4.5 W
Not Applicable
4.5 W
Not Applicable
1.1 W
0.75 W (24V) All channels

on.
1C31110G03 (P)
Compact Contact Input
1C31234G01 (E)
1C31238H01 (molded
Digital Input
1C31107G01 (E)
24VDC/48VDC
1C31110G01, G02
(P)
Digital Input
1C31107G02 (E)
125VDC
1C31110G01, G02
(P)
Compact Digital Input
1C31232G01 (E)
24/48VDC single-ended inputs

with common return
1C31238H01
(molded plastic cavity
insert)
1C31232G02 (E)
24/48VAC/VDC isolated
differential inputs
1C31238H01
insert)
1C31232G02 (E)
24/48VAC/VDC individually
fused inputs with common
power supply
5X00034G01 (P)
1C31232G03 (E)
125VAC/VDC isolated
differential inputs
1C31238H01
insert)
1C31232G03 (E)
125VAC/VDC individually fused

inputs with common power
supply
5X00034G01 (P)
REF_1005
1.5 W (48V) All channels on.

1.1 W
Not Applicable
1.1 W
0.65 W (24V)
1.75 W (48V)
1.1 W
0.69 W (24V)
1.75 W (48V)
1.1 W
0.69 W (24V)
1.75 W (48V)
1.1 W
Not Applicable
1.1 W
Not Applicable
189
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER (W)

(TYPICAL)
Digital Output
1C31122G01 (E)
2.2 W
19.2 W (24V)
(no relay panel)
1C31125G01 (P)
38.4 W (48V)
(8 outputs on @100 mA
each)
Digital Output plus
1C31122G01 (E)
2.2 W (module)
Solid State Relay Panel (16

relays)
1C31125G02 (P)
(R) not applicable
5.9 W (24V) (R)
5A22410G01 (R) AC
contacts
or
5A22410G02 (R) DC
contacts
Digital Output plus
1C31122G01 (E)
2.2 W (module)
Solid State Relay Panel (16

relays)
1C31125G03 (P)
(R) not applicable
Not applicable (assumes

panel powered from external
24V power supply)
10.87 W (24V) (R)
5A22410G01 (R) AC
contacts
or
5A22410G02 (R) DC
contacts
Digital Output plus
1C31122G01 (E)
2.2 W (module)
G2R Style Panel (16 relays)
1C31125G02 (P)
(R) not applicable
5A22411G01 (R)
Digital Output plus
1C31122G01 (E)
2.2 W (module)
G2R Style Panel (16 relays)
1C31125G03 (P)
(R) not applicable

24V power supply)
15.84 W (24V) (R)
5A22411G01 (R)
190
Digital Output plus
1C31122G01 (E)
2.2 W (module)
KUEP Style Panel (8 Form C

relays)
1C31125G02 (P)
(R) not applicable
Digital Output plus
1C31122G01 (E)
2.2 W (module)
KUEP Style Panel (8 Form C

relays)
1C31125G03 (P)
(R) not applicable

24V power supply)
Digital Output plus two
1C31122G01 (E)
2.2 W (module)
31.68 W (24V) (R)
KUEP Style Panels (2 x 8 Form

C relays)
1C31125G02 (P)
(R) not applicable
1C31122G01 (E)
2.2 W (module)

C relays)
1C31125G03 (P)
(R) not applicable

24V power supply)
Digital Output plus
1C31122G01 (E)
2.2 W (module)
11.28 W (24V) (R)
KUEP Style Panel (8 Form X

relays)
1C31125G02 (P)
(R) not applicable
5A22412G01 (R)
5A22412G01 (R)
5A22412G01 (R)
5A22412G01 (R)
5A22412G02 (R)
REF_1005
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER (W)

(TYPICAL)
Digital Output plus
1C31122G01 (E)
2.2 W (module)
KUEP Style Panel (8 Form X

relays)
1C31125G03 (P)
(R) not applicable

24V power supply)
1C31122G01 (E)
2.2 W (module)
22.56 W (24V) (R)

X relays)
1C31125G02 (P)
(R) not applicable
1C31122G01 (E)
2.2 W (module)

X relays)
1C31125G03 (P)
(R) not applicable
High Side Digital Output
5X00270G01 (E)
5A22412G02 (R)
5A22412G02 (R)
5A22412G02 (R)
2.16 W
5X00273G01 (P)
Relay Output module (E) plus
base with

24V power supply)
1C31219G01 (E)
1.88 W (E)
1C31223G01 (Base)
Base not applicable
16 G2R relays
48 W (VS=24V,
8 channels on
@250mA/channel)
0.29 W (E)
+ 9.1 W (Base with 16
relays)
----------------------= 9.39 W

base with 12 KUEP Form C
Relays added
1C31219G01 (E)
1C31222G01 (Base)
1.88 W (E)
Base not applicable
0.29 W (E)
+ 23.45 W (Base with 12
relays)
----------------------= 23.74 W

base with 12 KUEP Form X
Relays added
1C31219G01 (E)
1C31222G01 (Base)
1.88 W (E)
Base not applicable
0.29 W (E)
+ 15.9 W (Base with 12
relays)
----------------------= 16.19 W
Sequence of Events
1C31157G01 (E)
24VDC/48VDC
1C31110G01, G02
(P)
Digital Input
Sequence of Events
1C31157G02 (E)
125VDC Digital Input
1C31110G01, G02
(P)
Sequence of Events
1C31157G03 (E)
48V Contact Input
1C31110G03 (P)
Compact Seq. of Events
1C31233G01 (E)
24/48VDC single-ended inputs

with common return
1C31238H01 (molded
REF_1005
1.44 W
1.1 W (24V) All inputs on

2.2 W (48V) All inputs on
1.44 W
Not Applicable
4.56 W
Not Applicable
1.44 W
0.66 W (24V)
1.7 W (48V)
191
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER (W)

(TYPICAL)
1C31233G02 (E)
1.44 W
0.66 W (24V)
24/48VDC isolated differential

digital inputs
1C31238H01 (molded
1C31233G02 (E)
24/48 VDC individually fused

digital inputs with common
power supply
5X00034G01 (P)
1C31233G03 (E)
125VDC isolated differential

digital inputs
1C31238H01 (molded
1C31233G03 (E)
125VDC individually fused

digital inputs with common
power supply
5X00034G01 (P)
1C31233G04 (E)
48 V Contact Input
1C31238H01
insert)
Enhanced Compact Seq. of

Events
5X00357G01 (E)
24/48 VDC single-ended digital

inputs with common return
Events
24/48 VDC isolated differential
digital inputs
Events
1.7 W (48V)
1.44 W
1.7 W (48V)
1.44 W
Not Applicable
1.44 W
Not Applicable
4.5 W
Not Applicable
1.85 W
0.7 W (24V)
1C31238H01 (molded
5X00357G02 (E)
1.39 W (48V)
1.51 W
1C31238H01 (molded
5X00357G02(E)
125 VDC isolated differential

digital inputs
Events
0.65 W (24V)
1.30 W (48V)
1.51 W
0.65 W (24V)
5X00034G01 (P)
24/48 VDC single-ended

individually fused digital inputs
with common power supply
Events
0.66 W (24V)
1.30 W (48V)
5X00357G03 (E)
1.49 W
Not Applicable
1.49 W
Not Applicable
4.13 W
Not Applicable
1C31238H01 (molded
5X00357G03(E)
5X00034G01 (P)
125 VDC single-ended

Events
48 VDC contact input
192
5X00357G04 (E)
1C31238H01 (molded
REF_1005
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER (W)

(TYPICAL)

Events
5X00357G05 (E)
1.8 W
2.14 W
1.8 W
2.14 W
24 VDC isolated differential

digital inputs
Events
1C31238H01 (molded
5X00357G05 (E)
5X00034G01 (P)
24 VDC single-ended
9.4.5 Calculating power supply requirements for Specialty I/O modules

The following table lists the power a Specialty module draws from the +24V Main Power Supply
or Auxiliary Power Supply when the module is installed within the cabinet.
Power supply requirements for Ovation Specialty I/O modules
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER
(W) (TYPICAL)
Link Controller
For RS232:
3W
Not Applicable
2.7 W
When used:
1C31166G01 (E)
1C31169G01 (P)
For RS485/422:
1C31166G01 (E)
1C31169G02 (P
Loop Interface
1C31174GX1, GX2 (E)
13-bit Voltage AI
1C31177G01 (P)
Digital Inputs
(E) GX1 = 0 to 10V
(X = 0 or 2)
0.13W (24V)
(E) GX2 = 0 to 5 V
0.27W (48V)
(X = 0 or 2)
Digital Outputs
12-bit Voltage AO
0 to 10V
(2 outputs @100mA
each)
4.8 W (24V)
9.6 W (48V)
REF_1005
193
COMPONENT
EMERSON PART
NUMBER
MAIN +24 POWER

(W) (TYPICAL)
AUX POWER
(W) (TYPICAL)
Loop Interface
1C31174GX3, GX4 (E)
2.7 W
When used:
13-bit 4-20mA Current AI
1C31177G02, G03 (P)
Digital Inputs
(P) G02 = local power
(X = 0 or 2)
0.13 W (24V)
(P) G03 = field power
0.27 W (48V)
Digital Outputs
12-bit 4-20mA Current AO
(2 outputs @100mA
each)
(E) GX3
4.8 W (24V)
9.6 W (48V)
No AO
(E) GX4
Local Powered Analog

Inputs:
(X = 0 or 2)
(2 inputs @20mA each)

0.96 W (24V)
Pulse Accumulator
1C31147G01 (E)
24/48 VDC Count Inputs
1C31150G01-G02 (P)
1.6 W
When used:
Both count inputs = 50%
duty cycle
0.17 W (24V)
0.35 W (48V)
Not applicable for
12V/5V count inputs
Pulse Accumulator
1C31147G01 (E)
24/48 VDC Count Inputs
1C31150G03 (P)
Pulse Accumulator
1C31147G02 (E)
High Speed
1C31150G01-G03 (P)
1.6 W
Not Applicable
1.6 W
Not Applicable
6.7 W
Not Applicable
5.3 W
Not Applicable
4.8 W
Not Applicable
4.32 W
Digital Input
+5V Count Inputs

Servo Driver
1C31199G01 (E)
DC LVDT
1C31201G01 (P)
Servo Driver
1C31199G02, G03 (E)
AC LVT
1C31201G02 (P)
Speed Detector
1C31189G01 (E)
1C31192G01 (P)
Valve Positioner
1C31194G01, G02 (E)

1C31197G01-G04 (P)
0.09W (24V)
0.18W (48V)
Digital Output
(100mA load)
2.4 W (24V)
4.8 W (48V)
194
REF_1005
9.5 Monitoring power supply status
9.4.6 Calculating power supply requirements for remote function modules

The following table lists the power a remote function module draws from the +24V Main Power
Supply or Auxiliary Power Supply when the module is installed within the cabinet.
Power requirements for Ovation remote function components
9.5
COMPONENT
EMERSON PART
NUMBER
MAIN +24
POWER (W)
(TYPICAL)
AUX POWER
(W) (TYPICAL)
Redundant Remote Node Controller

module (in Remote Node Cabinet)
1C31203 (E)
12 W
Not Applicable
1C31179 (E)
13.2 W
Not Applicable
1C31181G01-G04 (P)
1C31204G01, G03 (P)
Monitoring pow er suppl y status

Each Ovation Controller IOIC card and each Remote Node has the capability to monitor up to two
sets of redundant Ovation power supply modules (one set contains two redundant power
supplies).
Each power supply typically outputs two voltages. A healthy status indicates the presence of all
output voltages on the power supply. An unhealthy status indicates the lack of one or both output
voltages on the power supply and that the power supply should be replaced. Power supply LEDs
indicate which input/output voltage is bad. A green LED indicates a healthy voltage status, and an
unlit LED indicates an unhealthy voltage status.
The status is reflected in Node (RN) Point Records which are assigned to IOIC and Remote Node
addresses through the I/O Builder. When a power supply fails, this status is displayed at the
Operator Station in the Point Information window and in the Base Alarm window.
9.5.1 Monitoring one set of redundant power supplies

No additional cabling is required to monitor one set of redundant power supplies. The first
redundant power supply set being monitored is contained in the Ovation Controller or in the
Remote Node Controller cabinet.
REF_1005
195
9.5 Monitoring power supply status
9.5.2 Monitoring two sets of redundant power supplies

Monitoring a second set of redundant power supplies for a Controller or a Remote Node
Controller requires an additional power supply status cable connection.
To have the Controller monitor a second set of local power supplies, install cable 5A26467
between connector P9, P10, or P11 on the Power Distribution Module (PDM) and the
Supplementary Status Connector J26 on the Controller Backplane Panel (CBO).
To have the Remote Node Controller monitor a second set of remote power supplies, install
cable 5A26467 between connector P9, P10, or P11 on the Power Distribution Module (PDM) and
the Supplementary Status Connector P6 on the Remote Transition Panel (TND).
Note: Cable 5A26467 is available in lengths from 102 cm (40 in) to 914 cm (360 in).
Status Cable
5A26467
Controller Cabinet
Front
Extended Cabinet
Front
P9
P10
P11
Secondary
Power Supply
PDM
Controller Cabinet
Back
Primary
Power Supply
J2
P9
P10
P11
Power Supply Set 2
Secondary
Power Supply
J1
Primary
Power Supply
Controller
Power Supply Set 1
PDM
Power and Status Cable

(installed at factory)
Extended Cabinet
Back
Figure 44: Monitoring local power supplies (OCR400 Controller)
196
REF_1005
9.6 Using an external power supply
Figure 45: Monitoring Remote Node Power Supplies
9.6
Using an external pow er suppl y

Some Ovation I/O modules require an auxiliary power supply. Auxiliary power may be obtained
either from the internal auxiliary power supply (backplane) or from an external power supply.
If an Ovation I/O module is to be connected to an external power supply, perform the following
steps BEFORE connecting the power supply to the Ovation module and powering it up.
CAUTION! Using an external power supply may introduce dangerous voltages at these
locations. Do NOT apply external power to the cabinet until the appropriate internal auxiliary
power supply fuses have been removed and the required fuse covers have been installed.
1. Identify the I/O branch to which the Ovation I/O module is assigned and the back panel (CBO)
or transition panel associated with the I/O branch.
REF_1005
197

2. If the I/O branch that requires external auxiliary power is associated with a transition panel,
perform the following:
a) If the transition panel has a cover, remove the cover in order to expose
the fuses.
b) Remove the pair of round plug-in fuses located nearest the I/O branch that
you identified in Step 1.
c) If you have removed a transition panel cover, replace the cover after the
uses are removed. A fuse cover kit is not required. However, if the
transition panel does not have a cover, then fuse cover caps (5A26371H20)
are required.
Note: Fuse cover caps are required only if the external power supply output voltage is greater
than 60 VDC, 42 VAC peak, or 30 VAC rms.
3. If the I/O branch that requires external auxiliary power is associated with a backplane (CBO),
refer to the following figure and perform the following:
a) Identify the artwork level of the backplane.
b) Determine what fuse cover kit is needed for the backplane:
1C31213G01 for artwork level 3CBO and earlier.
1C31213G02 for artwork level 5CBO and later.
c) Remove the pair of round plug-in fuses located nearest the I/O branch that
you identified in Step 1.
d) Install the appropriate fuse cover kit over the fuse sockets from where the
fuses were removed.
Note: The fuse cover kit is required ONLY if the external power supply output voltage is greater
than 60 VDC, 42 VAC peak or 30 VAC rms.
4. After the fuse covers are securely installed, connect the external voltage power supply
positive (+) and negative (-) outputs to the Ovation I/O module base unit terminal block PS+
(A17 or B17) and PS- (A18) terminals. Once the external power supply is connected to the
base unit terminal block and is powered up, the entire I/O branch has access to the external
power supply voltage.
198
REF_1005
Power
PDM
Power
Controller
Controller
Controller
Controller
Note: Base unit terminal block locations A17 (PS+) and B17 (PS+) are connected to the same
potential within the base unit.
Fuses
Fuses
ROP Trans Panel
Controller Cabinet
Front
Marshalling Cabinet
Front
Figure 46: Locations of cabinet panels (ROP and TND) OCR400 Controller and
Marshalling cabinets
REF_1005
199
PDM
Power
Fuses
Power
Controller
CBO
Backplane
(cover removed)
Controller
(cover removed)
CBO
Backplane
Fuses
ROP Trans Panel
Controller Cabinet
Front
Marshalling Cabinet
Front
Figure 47: Locations of cabinet panels (CBO, ROP, and TND) OCR161 Controller and
Marshalling cabinets
200
REF_1005
ROP
Transition
Panel
Fuses
Extended Cabinet
Front
TND
Transition
Panel
Fuses
Remote Node Cabinet

Front
Figure 48: Locations of cabinet panels (CBO, ROP, and TND) Extended and Remote
Node cabinets
REF_1005
201
Power Supply
Breaker / Switch
Power Distribution
Module
Power Supply
Breaker / Switch
Fuses
ROP
Transition
Panel
Terminator
Controller Cabinet/
Extended Cabinet/
Remote Node Cabinet
Back
Figure 49: Location of ROP panel in cabinet backs
202
REF_1005
+24V and AUX Power Connectors *

(P7 supplies power to P8, to +24V fans, and
to Branches "n" and "n+1")
IN
AUX Supply Fuses for Branch "n"
PGND
F1
P7
OUT
P8
AUX Supply Fuses for Branch "n+1"
F2
F7
TWI Connector to Local Branch "n"
F8
PGND
TWI Connector to Local Branch "n+1"
I/O Transition Panel (ROP) **

+24V and AUX Power Connector *
(P5 supplies power to Remote Node Controller,
to +24V fans, and to Branches 1 and 2)
P6
P5
AUX Supply Fuses for Branch 1
F1
PGND
AUX Supply Fuses for Branch 2
F2
F6
Branch
1
Branch
2
F7
PGND
TWI Connectors to Local

I/O Branch
Remote Node Transition Panel (TND) **

* When fuses are removed, AUX power (if needed) must be supplied externally, instead of through the Transition Panel.
** Panel covers are not shown.
Figure 50: Auxiliary power supply fuse locations on ROP and TND panels
REF_1005
203
+24V and AUX Power Connectors *

(P7 supplies power to P8, to +24V fans, and to
the left side of Branch "n")
IN
AUX Supply Fuses for
left side of Branch "n"
PGND
F1
OUT
P7
P8
F2
PGND
TWI Connector to left side of Local Branch "n"
TWI Connector to right side of Local Branch "n"
Relay Base Transition Panel (RRP)
TWI Connector for left side of Local Branch "n"
TWI Connector for right side of Local Branch "n"
PGND
PGND
F2
+24V and AUX Power *
Connectors
(P7 supplies power to P8,
to 24V fans, and to the
right side of Branch "n")
P8
P7
OUT
IN
F1
AUX Supply Fuses

for right side of
Branch "n"
Relay Base Transition Panel (RRB)
When fuses are removed, AUX power (if needed) must be supplied externally, instead of through the Transition Panel.
Relay Output modules require +24 V auxiliary.
Figure 51: Auxiliary power supply fuse locations on RRP and RRB panels
204
REF_1005
E C T I O N
10
10 Planning for replacement parts and repair service
IN THIS SECTION
Ordering spare parts ....................................................................................................... 205
Returning parts to Emerson for repair service ................................................................ 206
Part failure during project startup .................................................................................... 208
Determining repair prices ................................................................................................ 208
Tracking part repairs ....................................................................................................... 209
10.1 Ordering spare parts

Spare parts for any of the main components of an Ovation system are available from the Renewal
Parts Department of Emerson Process Management Power and Water Solutions (hereafter
known as Emerson). Many Ovation parts are maintained for immediate shipment from the factory.
Make sure you have the correct part number (see page 205) for any part you order. You might
also want to know the price of a part (see page 206) before you order it.
Emerson provides several methods that you can use to order parts, including the Ovation &
WDPF Users Web site. This free Web site is provided to all Ovation and WDPF customers.
Contact your Emerson representative to register for Web site access.
The Web site URL is https://www.ovationusers.com.
If you do not have access to the Web site, you can contact your local regional office. You can also
contact the Renewal Parts Department at 412-963-4247 or fax your request to 412-963-4245.
10.1.1 Determining a spare part number

Before you place a parts order, you need to determine the part numbers of the desired parts. You
can determine part numbers from applicable instruction books or drawings that are supplied with
your Ovation system. The part number is also typically marked on each part.
When ordering replacement parts or components, use the assigned Emerson ten-character,
alphanumeric assembly or style number (for example, 5X00070G01), which consists of the
following:
First seven characters are the main drawing number of the item.
Last three characters describe a variation of the main drawing.
REF_1005
205
10.2 Returning parts to Emerson for repair service
10.1.2 Determining a spare part price

You can determine the price of a part by using the Ovation & WDPF Users web site,
www.ovationusers.com.
If you do not have access to the web site, you can contact your local regional office. You can also
contact the Renewal Parts Department at 412-963-4247 or fax your request to 412-963-4245.

Emerson requests your cooperation in adhering to the following procedures when returning parts
for repair. Your cooperation will enable us to process returned material safely and efficiently.
1. To obtain a Material Return Tracking (MRT) number from Emerson (see page 207).
2. Mark the MRT Number on all material returned to our Repair Department. Shipments
delivered to the Emerson dock that do not have an MRT Number clearly marked on each
carton will be refused and returned to the sender at his/her expense.
3. Include a phone or fax number for a person to be contacted in case of problems or questions.
4. For small electronic components being returned, document the MRT Number on the outside
of the anti-static container. DO NOT attach anything directly to PC boards. Although CRTs
and other bulky materials do not need anti-static containers, make sure that the MRT number
is visible on these items.
5. Use the following shipping instructions:
Note: No collect shipments will be accepted.
CUSTOMER
ADDRESS
METHOD
COMMENTS
EMERSON CARRIERS
US
Customers
Emerson Process
Management
200 Beta Drive
Prepaid
Provide shipment
information (airway
bill number) via
telephone, fax, email,
or mail.
Utilize the following

carriers:
ATTENTION:
Repair Department
*MRT NUMBER:
___________
FedEx for Domestic Small

Packages
FedEx Freight for
Domestic Over 150 Lbs
*Note: At least one of the

assigned MRT Numbers must
be shown.
206
REF_1005
CUSTOMER
ADDRESS
METHOD
COMMENTS
EMERSON CARRIERS
Non-US
Customers
Emerson Process
Management
200 Beta Drive
Prepaid
Prior to shipping, the

returnee must provide
shipment information
to the Emerson
Repair Department
via telephone, fax,
email, or mail. This
information should
include airway bill
number, method of
shipment, weights
and dimensions, and
a copy of the
proforma or
commercial invoice.
Utilize the following

carriers:
ATTENTION:
Repair Department
*MRT NUMBER:
___________
For DHL or UPS contact upon
arrival:
UPS Supply Chain Solutions
(866) 955-6591
Email:
UPSEmersonBrokerageTeam
@ups.com
UPS
DHL
FedEx
Returns of repaired
parts from Emerson
are prepaid only to
the US port of export.
For FedEx shipments:

Contact Upon Arrival
FedEX Trade Networks
(716) 871-3529
*Note: At least one of the
assigned MRT Numbers must
be shown.
Note: Customs Values and Inco terms will be provided with the MRT number.
10.2.1 Obtaining a Material Return Tracking (MRT) number

Before returning a component to Emerson Process Management Power & Water Solutions for
repair, you must obtain a Material Return Tracking (MRT) number.
You must mark the Material Return Tracking (MRT) number on all material returned to the Repair
Department. Shipments delivered to the Emerson dock that do not have an MRT Number clearly
marked on each carton will be refused and returned to the sender at his/her expense.
1. If for any reason you need to return a product for repair, please contact Emerson to obtain an
MRT number before shipping the defective material to Emerson. Use one of the following
methods to obtain an MRT number:
Via email at PWS.Aftermarket@emersonprocess.com
Via the Ovation & WDPF Users Web site (https://www.ovationusers.com).
Via FAX at (412) 963-4245.
Via telephone at (800) 397-9767 or (412) 963-4244.
In case of an emergency, call the Technical Support phone at (800) 445-9723.
2. When you contact Emerson to obtain an MRT number, please be prepared to provide the
following information:
REF_1005
207
10.3 Part failure during project startup

Company name
Site name
Shipping address
Your name, telephone number, email, and fax number
Purchase order number (if system is no longer under warranty)
Project number (if system is under warranty)
Quantity of items being returned
Drawing numbers
Mnemonic of items
Detailed description of the problem or update request
10.2.2 Handling in-warranty and non-warranty part repairs

When you return a part to Emerson for repair service, refer to the following table for directions on
sending in-warranty parts and non-warranty parts.
PART STATUS
REQUIREMENTS
SHIPPING
METHOD
SHIPPING
In-warranty
parts
- MRT number (provided by

Emerson)
Prepaid
Refer to Returning parts to Emerson

for repair service (see page 206).
Prepaid
Refer to Returning parts to Emerson

for repair service (see page 206).
GUIDELINES
- Contact person (at customer site)

- Emerson Project number
Non-warranty
parts
- MRT number (see page 207)

(provided by Emerson)
- Contact person (at customer site)
- PO (provided by customer via email
or faxed to Emerson 412-963-4245)
- PO should reference part number
and associated MRT number.
10.3 Part failure during project startup

If you experience a part failure during the startup of your Ovation project, you should contact your
onsite Emerson field engineer (where applicable) or your Emerson regional field office.
They will coordinate with Emerson Pittsburgh for the provision of rapid turnaround replacement
parts and provide you with instructions for returning the defective parts.
10.4 Determining repair prices

You can determine the price of part repair (non-warranty) by using the Ovation & WDPF Users
Web site:
1. Log on to the Web site (https://www.ovationusers.com).
208
REF_1005
10.5 Tracking part repairs

2. Select Spare Parts & Repairs.
3. Select Repair Pricing.
4. Use the form that appears to locate the part you want to repair and the price of making that
repair.
10.5 Tracking part repairs

You can track the progress of a part repair by using the Ovation & WDPF Users Web site:
1. Log on to the Web site (https://www.ovationusers.com).
2. Select Spare Parts & Repairs.
3. Select Track Repairs.
4. Enter the MRT number of the part and press Submit.
5. A window appears informing you of the progress of the repair status.
REF_1005
209
E C T I O N
11
11 Planning for shipping and storage of Ovation

equipment
IN THIS SECTION
Guidelines for shipping Ovation equipment .................................................................... 211
Guidelines for lifting Ovation equipment ......................................................................... 212
Guidelines for off-loading and unpacking Ovation equipment ........................................ 213
Guidelines for repacking and returning Ovation equipment ............................................ 214
Guidelines for repacking third-party products ................................................................. 214
Guidelines for transporting Ovation equipment to the specific installation location ........ 214
Guidelines for storing Ovation equipment ....................................................................... 214
11.1 Guidelines for shipping Ovation equipment

Use the following general guidelines for shipping equipment.
1. Since many pieces of an Ovation system are large and heavy, provide adequate off-loading
equipment (along with experienced personnel to operate the equipment) at the site.
2. Plan in advance the best manner and route to transport the equipment (after it is off-loaded).
Consider any problem obstacles, such as stairways, doorways, or difficult turns.
3. Ship any components that are contained in the main housing of a drop (that is, an I/O cabinet)
fully assembled.
4. Connect, prior to shipment, any cables connected entirely within the main housings.
5. Pack in a separate package, any cables used to connect external components together, and
ship them along with the main enclosure.
6. Mount cabinet housings on pallets.
7. Secure all internal cables to prevent rubbing or chafing, and relieve stress with cable ties.
8. Secure all internal components or lock them in place by anchoring the devices.
9. Remove all temporary cushioning, blocking, bracing, and anchoring material before powering
up the system.
10. Wrap the housings in heavy-duty plastic wrap.
11. Route shipments, if possible, by air-ride electronic vans directly to the point of destination, to
eliminate any unnecessary unloading and reloading.
12. Prepare shipments for possible shock and vibration encountered during shipment by utilizing
internal bracing and suitable anchoring.
13. Mark shipping containers to identify the following:
Front and back.
Destination.
REF_1005
211
11.2 Guidelines for lifting Ovation equipment

Return address.
Package numbers showing the purchase order number, followed by the package number
and the total number of packages.
Material identification number.
Handling instructions (for example, Fragile, Center of Gravity, Keep Dry, This Side Up,
Sling Here, Do Not Freeze, and stacking limitations if appropriate).
Weight and dimensions (as applicable).
Special instructions (for example, Desiccant Inside; special inspections; storage or
unpacking restrictions, as appropriate).
14. Ship cabinets in an upright position or placed on the front or back door, heavy side down,
then on a heavy-duty pallet and covered with heavy-duty plastic. Cover the cabinet with
styrofoam and plywood on all four sides, and band the covered cabinets with high-strength
banding. Use either a skid or a crate.
15. For shipments by air and ocean, use waterproof paper, as needed.
16. For shipments by ocean, place a desiccant in the sealed container. Encase the sealed
enclosure in a military-type plywood crate. If required, mark the crate to indicate the center of
balance, fork lift and sling handling points, and use cautioning marks and symbols.
17. For spare parts and/or kits:
By Land: Mobile wrap boxes and use pallets.
By Air: Mobile wrap waterproof boxes and use cable crates.
By Ocean: Vapor pack boxes, wrap them in waterproof paper, and place them in plywood
crates.
11.2 Guidelines for lifting Ovation equipment

Observe the following guidelines for safe lifting.
1. If it is necessary to lift equipment by crane or other hoisting devices, Emerson can provide
this service at an additional cost.
2. Emerson can provide rigging and rigging supervision to ensure a complete and safe
off-loading. For more information, contact your Emerson representative.
3. If eye bolt lugs are provided at the top corners of the cabinets for lifting, make certain that all
four eyebolts are fastened to ensure safe load distribution.
Ovation I/O cabinet weights and dimensions
1
CABINE T TYPE
WEIGHT
DIMENSIONS (H
Ovation Workstation Cabinet: Vented
183 kg
2083x601x890 mm
1X00518
(403 lb)
(82x24x35 in)
Ovation Server Cabinet Vented
161 kg
2083x601x890 mm
1X00545
(354 lb)
(82x24x35 in)
D)
Static load rating of 680 kg

(1500 lb)
OCR400 Controller
212
211.71 kg
2000 x 600 x 600 mm
REF_1005
11.3 Guidelines for off-loading and unpacking Ovation equipment
CABINE T TYPE
WEIGHT
DIMENSIONS (H
5X00293
(466.75 lbs)
(78 x 24 x 24 in)
OCR161 Controller
222.83 kg
2000 x 600 x 600 mm
4D33953
(491.25 lbs)
(78 x 24 x 24 in)
Extended I/O
208.14 kg
2000 x 600 x 600 mm
CE Mark Certified
(458.86 lbs)
(78 x 24 x 24 in)
Remote I/O
209.48 kg
2000 x 600 x 600 mm
Sealed
(461.83 lbs)
(78 x 24 x 24 in)
Remote I/O
209.48 kg
2000 x 600 x 600 mm
Ventilated
(461.83 lbs)
(78 x 24 x 24 in)
198.56 kg
2000 x 600 x 600 mm
(437.75 lbs)
(78 x 24 x 24 in)
209.67 kg
2000 x 600 x 600 mm
(462.25 lbs)
(78 x 24 x 24 in)
283.6 kg
2000 x 800 x 600 mm
(624 lbs)
(78 x 32 x 24 in)
301 kg
(664 lbs)
2000 x 914 x 600 mm
178.65 kg
2000 x 600 x 600 mm
(393.86 lbs)
(78 x 24 x 24 in)
Remote I/O
180.0 kg
2000 x 600 x 600 mm
Sealed
(396.83 lbs)
(78 x 24 x 24 in)
Remote I/O
180.0 kg
2000 x 600 x 600 mm
Ventilated
(396.83 lbs)
(78 x 24 x 24 in)
D)
CE Mark Certified
CE Mark Certified
CE Mark Certified
CE Mark Certified
OCR400 Controller
OCR161 Controller
Marshalling
Marshalling
Extended I/O
(78 x 36 x 24 in)
Assumes Controller cabinet is populated with 16 I/O base assemblies (32 Electronic modules and 32
Personality modules).
11.3 Guidelines for off-loading and unpacking Ovation equipment

1. Off-load all shipments of Ovation equipment with Roll-A-Lift jacks, hydraulic lift trucks, or
four-wheel dollies. Do not hoist domestic shipments, but you may hoist overseas shipments at
the center-of-gravity marks, shown on the container.
2. Locate a packing list for all shipments. Check the shipment against the list to be sure that all
items have been delivered. If any of the shipment is missing, notify the carrier of the shortage,
and obtain proof of the shortage.
REF_1005
213
11.4 Guidelines for repacking and returning Ovation equipment

3. Inspect the complete shipment for visible damage to any of the packing containers, and verify
any damage with the carrier.
4. Unpack the equipment by cutting any banding and removing all exterior packaging such as
cardboard and plastic wrap. Place any drops that were shipped on their side in an upright
position. Inspect the shipment again for visible damage such as dents, scrapes, and severely
scratched paint work. Verify any damage with the carrier.
5. Save all reusable packing material (that is, pallets, containers, and so on) in case you need to
return the shipment.
6. Open all cabinet doors and remove all shipping materials. Inspect the interior of all drop
enclosures for obvious mechanical damage.
WARNING! Do not allow, under any circumstances, any equipment to sit in an area exposed
to the weather.
11.4 Guidelines for repacking and returning Ovation equipment

1. If you must return an Ovation component to the factory, repackage it in a manner similar to
the way it was shipped.
In general, package the equipment so that no damage will occur during transportation. This
means that you must protect exteriors and secure interior devices.
2. Before returning any equipment to Emerson, contact an Emerson representative for return
approval.
3. Attach documentation, which states the reason for the return, to the returned equipment.
11.5 Guidelines for repacking third -party products

Since Ovation is an open system, many components of your Ovation system are third-party
products (such as switches, monitors, and workstations). Use the following guidelines when
dealing with third-party products:
Save the products original shipping containers in case it would need to be returned to
Emerson or to the manufacturer for repairs.
Save the documentation that is provided with the product. This includes User Guides,
warranty information, and so forth.
11.6 Guidelines for transporting Ovation equipment to the specific

installation location
1. Transport equipment to the final installation location with Roll-A-Lift jacks, hydraulic lift trucks,
or four-wheeled dollies.
2. Do not hoist equipment for final installation. Only certain cabinet enclosures are designed with
holes to attach eye bolts.
11.7 Guidelines for storing Ovation equipment

You may need to store an Ovation system before you can install the system.
1. Storage temperatures for Ovation components are listed in Specifications for Ovation
Equipment. (see page 11)
214
REF_1005
11.7 Guidelines for storing Ovation equipment

2. Verify that the storage area will be:
Rodent and pest-free.
Insect controlled.
Equipped with a fire prevention system and a fire sensing and alarm system.
Located in a key-lock-controlled area.
Located in a personnel-controlled area.
Kept free of all combustible material except essential packing materials.
Protected from airborne dust.
Free from water leaks and water accumulation.
Free of corrosive gasses.
Free of excessive vibration.
Stored in the non-energized state with desiccant bags in each enclosure.
Stored with the cabinet doors locked.
Stored with dust covers intact.
Stored in a last in/first out manner to avoid re-handling.
3. Stack cables on two-inch-by-four-inch lumber to a maximum height of three feet.
REF_1005
215
E C T I O N
12
12 Planning your CE Mark Certified system
IN THIS SECTION
What is a CE Mark Certified system? ............................................................................. 218
Using third-party components in CE Mark Certified systems.......................................... 219
Using a grounding panel for CE Mark Certified systems ................................................ 220
Cabling requirements for CE Mark Certified systems ..................................................... 223
AC line filtering (Applicable to EMC Cabinet approach only) .......................................... 223
Internal cable ferrites (non-EMC cabinet approach only)................................................ 224
Ovation Suppression Panel ............................................................................................. 224
REF_1005
217
12.1 What is a CE Mark Certified system?
12.1 What is a CE Mark Certified s ystem?

CE Mark certification on a product is a manufacturer's declaration that the product complies with
the essential requirements of the relevant European health, safety, and environmental protection
legislation. CE Mark on a product indicates to governmental officials that the product may be
legally placed on the market in their country and ensures the free movement of the product within
the European Free Trade Association (EFTA) & European Union (EU) single market (total of 28
countries).
Ovation has two methods of achieving a CE Mark system:
EMC cabinet.
Non-EMC cabinet.
EMC cabinet approach

A CE Mark Certified Ovation system can use special EMC cabinets, supplementary internal
filtering, and exacting requirements on field wiring and grounding to ensure compliance with the
specific European Electromagnetic Emissions/Immunity and low voltage safety.
The CE Mark Certified Ovation Controller cabinet assembly, Extended I/O cabinet assembly, and
Remote I/O cabinet assembly are certified for operation in the Industrial Environment as
documented in the EMC Technical Construction File for Ovation (5A26444) and the Low Voltage
Safety Technical File for Ovation (5A26443).
The CE Mark Certified Controller cabinet assembly drawing for the OCR400 Controller is
5X00293.
The CE Mark Certified Controller cabinet assembly drawing for the OCR161 Controller is
4D33953.
The specific requirements for the CE Mark Certified Systems are discussed throughout this
document and also in the following:
Drawing 5A26418 - This drawing contains a baseline listing of all components applicable for
the CE Mark Certified System.
Drawing 5A26370 - This drawing contains a baseline listing of workstation and peripheral
components applicable for the CE Mark Certified System.
Non-EMC cabinet approach

A CE Mark Certified system can also use non-EMC cabinets. This is accomplished by utilizing a
Non-EMC cabinet approach in which baseline testing was performed on the standard Ovation
cabinet style 5X00127H02.
This approach utilizes requirements on field wiring shield termination and internal cabinet cable
ferrites in specific locations to ensure compliance with the specific European Electromagnetic
Emissions/Immunity and low voltage safety.
The baseline cabinet assemblies utilized for the Non EMC Cabinet approach testing are
5X00127H02 (ventilated cabinet assembly) or 5X00046H03 (sealed cabinet assembly). Alternate
models shall be considered ongoing based upon equivalency and may include criteria such as
welded steel frame construction, gauge of metal side panels, overlapping door seams, internal
ground straps connecting all panels to the mounting plate, and a grounding stud for tying the EMC
ground.
218
REF_1005
12.2 Using third-party components in CE Mark Certified systems

The specific requirements for the Non EMC Cabinet CE Mark approach are discussed throughout
this document and are also in the following:
Drawing 5X00424 This drawing contains a baseline listing of all components applicable for
the Non EMC Cabinet CE Mark Certified System approach.
Drawing 5A26370 This drawing contains a baseline listing of workstation and peripheral
components applicable for the CE Mark Certified System.
12.2 Using third -party components in CE Mark Certified s ystems

Observe the following rules when using third-party components in CE Mark Certified Fast
Ethernet Ovation Systems that are based on the type of environment where the equipment is
located:
For all environments
Use only components that are approved for use in CE Mark Certified Ovation Systems. A
complete list of approved components is contained within Emerson drawing 5A26418 or
5X00424 (for Ovation Controller and I/O) and drawing 5A26370 (for workstation and
peripheral equipment).
Follow all vendor-recommended CE Mark requirements and installation guidelines as listed in

the vendors documentation.
For control room environments
Use copper and fiber network connections that are recommended by the vendor for
installation in an industrial/light industrial environment using CE Mark calibrated equipment.
For plant floor/industrial environments or Controller cabinets
Locate all components or devices within an approved RFI gasketed welded steel frame
cabinet as listed in CE Mark Certified Ovation Systems Components drawing 5A26418 for the
EMC cabinet approach.
Locate all components within an approved welded steel frame cabinet as listed in CE Mark
Certified Ovation Systems Components drawing 5X00424 for the non- EMC cabinet
approach.
Use only fiber-optic network connections to/from cabinets in CE Mark Certified Ovation
Systems.
For copper-based devices, you need a fiber optic media converter to convert the copper
signals to fiber. The media converter must contain redundant AC feeds connected to the
separate AC inputs (primary/secondary).
You can single attach each side of a redundant Ovation Controller to separate switches,
provided the switches are powered from independent power feeds.
You can dual attach non-redundant Ovation Controllers to separate switches where each
switch is powered from a different power feed. When independent power feeds are not
available, you can power the switch by a UPS located within three meters of a switch,
provided the UPS switch is CE Mark Certified for use in an industrial environment.
REF_1005
219
12.3 Using a grounding panel for CE Mark Certified systems
12.3 Using a grounding panel for CE Mark Certified s ystems

You must earth ground all shielded cables entering a CE Mark certified cabinet at the entry point
of the cabinet. Use the prescribed grounding panel (3A99245G01).
Each grounding panel can accommodate up to 16 cable clamps. The cable clamps come in three
styles which you can mix on each panel:
12mm diameter (5A26440H01).
Use the following procedure to use the panel to ground the cable shields:
1. Strip the cable jacket away at the clamping point.
Do not overstrip the cable or the shield could short against a nearby clamp.
2. Place the exposed shield under the clamp and then bolt the clamp to the panel.
3. Place one panel in each corner of the cabinet as required; however, a panel must be located
at the point where the cable enters the cabinet.
4. Refer to the Ovation CE Marked cabinet drawings 5X00293, 4D33953, 4D33954, 4D33955,
and 4D33956 for detailed instructions on the installation of the panels and the installation of
the cables within the clamps.
Additionally, you can install multiple cables in each clamp provided that the exposed shields
come in direct contact with the clamp.
The shield of the field wiring should remain continuous within the cabinet to the terminal block
of the appropriate base unit. The shield, however, should not be connected to any point on
the terminal block.
220
REF_1005
12.3.1 Grounding panel configuration

The grounding panel has two configurations associated with each clamp:
Direct grounding.
Capacitive grounding.
The direct configuration is the standard configuration and is recommended for most cables.
The exceptions are low level (such as thermocouple) analog inputs where the sensor is
referenced to earth in the field. For maximum noise immunity, the cable shield should be directly
grounded at the sensor, and grounded through a capacitor at the cabinet. The cable clamp on the
panel can be configured for capacitive grounding by clipping out the shunt located adjacent to the
clamp.
For Ovation bus modules, the following grounding methods apply in addition to earth grounding at
the cabinet entry point:
For Foundation Fieldbus modules, I/O cable shield is grounded at the segment power
conditioner in accordance with Emerson drawing 5X00330.
For Profibus modules, use of a shielded 9-pin Dsub connector is mandatory. Drawing
5X00363 lists prefabricated lengths of cable with acceptable shielded connectors.
For DeviceNet modules, I/O cable drain wire is connected to the center pin of a 5-pin
combicon style connector (if a combicon connector is used) or connected to an Ovation base
at either channel one or channel two drain terminal. Refer to Personality module 5X00375
side label for terminal locations.
REF_1005
221
0.81
Remove this
shunt if the
cable(s) in the
adjacent clamp
are to be
capacitively
grounded.
Cable Clamp
(user installed)
5A26440H01
Mounting Hole
(typical, 8 places)
12mm dia.
5A26440H02
8mm dia.
5A26440H03
6mm dia.
0.81
9.46
1.00
2.00
2.00
2.00
1.00
8.00
Figure 52: Grounding Panel
222
REF_1005
12.4 Cabling requirements for CE Mark Certified systems

Alternatively, for the non-EMC Cabinet approach, there are equivalent options for terminating the
I/O cable shields at the cabinet entry point:
One equivalent method is to utilize EMC cable glands which are fastened within a drilled hole
located within the cabinet panel. The cable jacket is stripped backed exposing the shield and
the gland is tightened on the I/O cable shields firmly, thereby connecting the shield to the
cabinet panel/cabinet ground.
Another equivalent method includes utilizing a shield termination grounding bar located at the
cabinet entry point. The cable jacket is stripped back exposing the shield which is then
clamped to the bar assembly terminating the shields to cabinet ground through the shield bar
assembly.
Refer to components drawing 5X00424 for additional information. For maximum noise immunity
where thermocouples are grounded at the sensor, a grounding terminal block may be utilized at
the cabinet entry in which the shield drain wires are connected through a 0.01uF 1kV capacitor
(4930A55H02) to a grounding termination bar. The grounding termination is then tied to cabinet
ground.
12.4 Cabling requirements for CE Mark Certified s ystems

When the following cable assemblies are used in CE Mark certified systems, they must stay
within the confines of a prescribed CE Mark certified Ovation cabinet or within an EMC suited set
of the prescribed cabinets. Alternatively, these cables can run between two non-suited EMC
cabinets provided the cables are run in solid grounded metallic conduit:
Ovation power cable assembly: 5A26137.
Remote I/O AUI cable assembly: 5A26147.
Local I/O bus cable assembly: 5A26141.
Ovation power supply monitor status cable: 5A26467.
The RLI-SLIM cable MUST use style 5A26429 and MUST adhere to the installation
requirements when exiting the Ovation cabinet. (Applicable to EMC Cabinet approach only).
12.5 AC line filtering (Applicable to EMC Cabinet approach onl y)

CE Mark certified cabinets require the use of a line filter on the AC input power to the Ovation
power supplies. Refer to To connect the AC Mains to the line filter assembly (see page 175) for
information about connection procedures to the line filter from the AC Mains.
Note: This is only applicable for the EMC Cabinet approach. This is not applicable for the nonEMC Cabinet approach.
REF_1005
223
12.6 Internal cable ferrites (non-EMC cabinet approach only)
12.6 Internal cable ferrites (non -EMC cabinet approach only)

The Non-EMC cabinet approach requires several cable ferrites to ensure compliance with the CE
Mark requirements. The ferrite should be a round split core type style, Fair Rite 0431164181 or
equivalent.
The cable ferrites must be located on the following cables:
IOIC to AUI Cable Assembly 5X00238. Locate above the IOIC, placing one wrap of the cable
within the split round core ferrite.
Ovation Power Supply to AC Distribution Panel Cable 5A26137G01. Locate the ferrite close
to the Power Supply connector. No loop through the split core ferrite is required.
Ovation Cat 5 network connecting to the Controller. Locate above the Controller, placing one
wrap of the cable within the split round core ferrite. This ferrite is not required in instances
where media convertors are employed within the cabinet which converts the UTP to fiber
optics.
12.7 Ovation Suppression Panel

The Ovation CE Mark system requires that an Ovation Suppression Panel (5X00281G01) be
located below the OCR400 Controller prior to branches 1 and 2 in the Controller cabinets.
224
REF_1005
E C T I O N
13
13 Planning your IEC61131-2 system
IN THIS SECTION
What is an IEC61131-2 certified system? ....................................................................... 225
Using a grounding panel for IE61131-2 certified system ................................................ 225
Cabling requirements for IEC61131-2 certified systems................................................. 225
13.1 What is an IEC61131-2 certified s ystem?

The International Electrotechnical Commission (IEC) is the leading global organization that
prepares and publishes international standards for all electrical, electronic, and related
technologies. These serve as a basis for national standardization and as references when drafting
international business agreements and contracts.
An Ovation IEC61131-2 certified system is a system whose components are compliant with the
standards described in IEC61131-2. The Ovation Controllers and a subset of the Ovation I/O
modules comply with these standards.
The specific requirements for IEC61131-2 certified systems are discussed in the following:
Drawing 5X00393 - This drawing contains a baseline listing of all Ovation components applicable
for the IEC61131-2 Certified System.
13.2 Using a grounding panel for IE61131 -2 certified s ystem

You must earth ground all shielded cables entering an IEC61131-2 certified cabinet at the entry
point of the cabinet. Use the prescribed grounding panel (3A99245G01). Refer to Using a
grounding panel for CE Mark Certified systems (see page 220) and Grounding panel
configuration (see page 221) for instructions on how to use the grounding panels.
You can use equivalent I/O cable termination methods. Refer to the end of Grounding panel
configuration (see page 221) for a list of acceptable equivalent I/O termination methods.
13.3 Cabling requirements for IEC61131 -2 certified s ystems

The Ovation Controller and a subset of the I/O has been certified to IEC61131-2 Revision 2,
Programmable Controllers." A list of these components can be found in Emerson drawing
5X00393. When claiming compliance, the following additional cabling considerations apply:
1. All I/O wiring must be shielded twisted pair.
a) For Analog Input and Output modules, ground the shield at the cabinet entry or the field
device per the recommendations in the Analog Input and Output module sections in
the Ovation I/O Reference Manual. The exception is the Hart High Performance
Analog Input module where you must ground the shield at both ends.
REF_1005
225
13.3 Cabling requirements for IEC61131-2 certified systems

b) For Digital Input and Output modules, ground the shields at the cabinet base.
2. To mitigate the effects of radiated emissions, add ferrite suppressors to various cabling as
follows:
a) IOIC to AUI Cable Assembly 5X00238. Locate above the IOIC, placing one wrap of the
cable within the split round core ferrite.
b) If more than the first two branches of local Ovation I/O are used, then you must install a
ferrite suppressor on the Ovation I/O Bus cable at the point closest to the Ovation
Controller backplane.
c) Ovation Power Supply to AC Distribution Panel Cable 5A26137G01. Locate the ferrite
close to the Power Supply connector. No loop through the split core ferrite is required.
d) Ovation Cat 5 network connecting to the Controller. Locate above the Controller placing
one wrap of the cable within the split round core ferrite. This ferrite is not required in
instances where media convertors are employed within the cabinet which converts the
UTP to fiber optics.
e) In all of the above cases, the use of snap-on ferrites is acceptable. Secure the ferrite
against movement through the use of tie wraps or other means. The ferrite material
should have good broadband suppression capabilities such as material type 31 or
equivalent.
3. When stranded I/O wiring is installed, you must crimp ferules onto the stripped end prior to
installing the wiring in the I/O base.
4. Locate the Ovation Suppressor Panel, 5X00281G01, below the Controller prior to local I/O
branches 1 and 2 in the Controller cabinets.
5. The Ovation I/O Controller electronics module assemble, 5X00226, must be Revision 10 or
later.
For Ovation bus modules, the following grounding methods apply in addition to earth grounding at
the cabinet entry point:
226
For Foundation Fieldbus modules, I/O cable shield is grounded at the segment power
conditioner in accordance with Emerson drawing 5X00330.
For Profibus modules, use of a shielded 9-pin Dsub connector is mandatory. Drawing
5X00363 lists prefabricated lengths of cable with acceptable shielded connectors.
For DeviceNet modules, I/O cable drain wire is connected to the center pin of a 5- pin
combicon style connector (if a combicon connector is used) or connected to an Ovation base
at either channel one or channel two drain terminal. Refer to Personality module 5X00375
side label for terminal locations.
REF_1005
E C T I O N
14
14 Planning to meet industry standards of compliance
IN THIS SECTION
Design standards ............................................................................................................ 227
Reliability standards ........................................................................................................ 227
Electrical interference standards ..................................................................................... 227
Safety standards ............................................................................................................. 227
14.1 Design standards

Ensure that you plan your Ovation I/O system to comply with the following industry design
standards:
Printed Circuit Wiring Design Standard - Emerson Drawing Number 404A339

This document establishes design and product requirements for printed circuit cards.
ANSI/IEEE 802.3 Standard for Local Area Networks - This document applies to the
components establishing the Ethernet physical layer on the Remote I/O subsystem.
14.2 Reliability standards

Ensure that you plan your Ovation I/O system to comply with the following industry reliability
standards:
MIL-HDBK-217 Reliability Prediction of Electronic Equipment.
14.3 Electrical interference standards

Ensure that you plan your Ovation I/O system to comply with the following industry electrical
interference standards:
ANSI C37.90-1989 IEEE Standard Surge Withstand Capability.
European EMC directive 89/336/EEC when part of the Standard CE Mark Certified System.
14.4 Safety standards

Ensure that you plan your Ovation I/O system to comply with the following industry safety
standards:
European Low Voltage Safety Directive 73/23/EEC when part of the Standard CE Mark
Certified System.
Certain Ovation Power Supplies and I/O modules are recognized to UL 1950.
International standard IEC 61511 that provides guidance to end-users on the application of
Safety Instrumented Systems (see page 371) in the process industries.
REF_1005
227
E C T I O N
15
15 Planning your internet addressing
IN THIS SECTION
Classes of internet addresses ......................................................................................... 229
Internet address notation ................................................................................................ 230
Allowable internet addresses .......................................................................................... 230
Internet address conventions .......................................................................................... 231
Subnet masks.................................................................................................................. 231
15.1 Classes of internet addresses

Internet addresses are 32-bit quantities, divided into five classes. Each class differs in the number
of bits allocated to the network and host portions of the address. For this discussion, consider a
network to be a collection of computers (hosts) that have the same network field value in their
Internet addresses.
The Class A Internet address format allocates the highest eight bits to the network field and sets
the highest priority bit to zero. The remaining 24 bits form the host field. Only 128 Class A
networks can exist, but each Class A network can have almost 17 million hosts. The Class A
format is shown below.
1
24
Network
Host
The Class B Internet address format allocates the highest 16 bits to the network field and sets the
two highest-order bits to 1, 0. The remaining 16 bits form the host field. Over 16,000 Class B
networks can exist, and each Class B network can have up to 65,000 hosts. The Class B format
is shown below.
1
14
16
Network
Host
The Class C Internet address format allocates the highest 24 bits to the network field and sets the
three highest-order bits to 1, 1, and 0. The remaining eight bits form the host field. Over two
million Class C networks can exist, and each Class C network can have up to 255 hosts. The
Class C format is shown below.
REF_1005
21
Network
Host
229
15.2 Internet address notation

The Class D Internet address format is reserved for multicast groups. In Class D addresses, the
four highest-order bits are set to 1, 1, 1, and 0.
The Class E Internet address format is reserved for future use. In Class E addresses, the four
highest-order bits are set to 1, 1, 1, 1. Routers typically ignore Class D and Class E Internet
addresses, except for the global broadcast address 255.255.255.255.
15.2 Internet address notation

Internet addresses are written as four 3-digit numbers separated by dots (periods). Each number,
written in decimal format, represents an 8-bit octet. When strung together, the four octets form the
32-bit Internet address. This notation is called dotted decimal.
The following examples show 32-bit values expressed as Internet addresses:
192.31.7.19
10.7.0.11
255.255.255.255
0.0.0.0
The largest possible value of a field in a dotted-decimal number is 255, which represents an octet
of all ones.
15.3 Allow able internet addresses

Some Internet addresses are reserved for special uses and cannot be used for host, subnet, or
network addresses. The following table lists the ranges of Internet addresses and shows which
addresses are reserved and which are available for use.
Reserved and available internet addresses
CLASS
A
D, E
230
ADDRESS
OR
RANGE
STATUS
0.0.0.0
Reserved
1.0.0.0 through 126.0.0.0
Available
127.0.0.0
Reserved
128.0.0.0
Reserved
128.1.0.0 through 191.254.0.0
Available
191.255.0.0
Reserved
192.0.0.0
Reserved
192.0.1.0 through 223.255.254.0
Available
223.255.255.0
Reserved
224.0.0.0 through 255.255.255.254
Reserved
255.255.255.255
Broadcast
REF_1005
15.4 Internet address conventions
15.4 Internet address conventions

If the bits in the host portion of an address are all 0, that address refers to the network specified in
the network portion of the address. For example, the Class C address 192.31.7.0 refers to a
particular network.
Conversely, if the bits in the network portion of an address are all 0, that address refers to the
host specified in the host portion of the address. For example, the Class C address 0.0.0.234
refers to a particular host.
If the bits in the host portion of an address are all 1, that address refers to all hosts on the network
specified in the network portion of the address. For example, the Class B address 128.1.255.255
refers to all hosts on the 128.1.0.0 network.
Note: Because of these conventions, be cautious when using an Internet address with all zeros
or all ones in the host portion of a router address entry.
15.5 Subnet masks

A subnet mask identifies the subnet field of a network address. This mask is a 32-bit Internet
address written in dotted-decimal notation with all ones in the network and subnet portions of the
address. For example, the subnet mask for a Class C network of 192.168.1.0 is 255.255.255.0.
The following table shows the subnet masks you can use to divide an octet into subnets and host
fields. The subnet field can consist of any number of the host field bits; you do not need to use
multiples of eight. However, you should use three or more bits for the subnet field a subnet
field of two bits yields only four subnets, two of which are reserved (the 1, 1 and the 0, 0 values).
Subnet Masks
SUBNET BITS
REF_1005
HOST BITS
HEX M AS K
DECIM AL M AS K
0x80
128
0xC0
192
0xE0
224
0xF0
240
0xF8
248
0xFC
252
0xFE
254
0xFF
255
231
E C T I O N
16
16 Planning your Ovation database
IN THIS SECTION
What is a Relational Database? ...................................................................................... 233
What is a point?............................................................................................................... 234
What are point records? .................................................................................................. 235
What is point frequency? ................................................................................................. 236
Understanding point names ............................................................................................ 236
Using valid Ovation point names ..................................................................................... 236
Using fully qualified point names ..................................................................................... 238
Creating the Ovation Database ....................................................................................... 238
16.1 What is a Relational Database?

The Ovation system uses the Relational Database Management System (RDBMS) philosophy.
This philosophy consists of three major components:
Common mechanism for performing similar actions.
Sophisticated sharing of data.
Interaction with a shared repository of data.
A Relational Database Management System stores information in tables rows and columns of
data and conducts searches by using data in specified columns of one table to find additional
data in another table. In a relational database, the rows of a table represent records (collections of
information about separate items) and the columns represent fields (particular attributes of a
record). In conducting searches, a relational database matches information from a field in one
table with information in a corresponding field of another table to produce a third table that
combines requested data from both tables.
Many pieces of information in the Ovation system, including system configuration, control
algorithm information, and the process point database, are stored in the Ovation Database. The
Ovation Database provides the capability to integrate and organize the massive amounts of raw
data in the system to create meaningful and valuable information.
All programming tools and user interfaces store their data in the Ovation Database, and then the
information is transmitted to the control system. The Ovation Database allows the applications
software and the control system to be easily accessed through third-party SQL (Structured Query
Language) tools. This means that the Ovation process control system data is open and
accessible.
The Ovation Database is based on Oracle 11G. For computing environments, such as Ovation,
that are connected via networks, Oracle combines the data physically located on different
computers into one logical database that can be accessed by non-controller network nodes.
REF_1005
233
16.2 What is a point?
16.2 What is a point?

A point is any item of data used within the Ovation system. Points include inputs and outputs from
field devices, calculated values, and internal system information. A name and a unique System ID
number identify each point and this information is stored in the Ovation Master Database. An
Ovation system can support up to 200,000 process points.
The Ovation control system scans or processes the following types of input/output. The control
system converts incoming information to engineering units then stores it in the point records. This
information is available for use in all parts of the system and for transmission to all parts of the
system.
Analog Input
Thermocouples.
RTD.
Milliamp DC.
Millivolt DC.
Volt DC.
Digital Input
Standard Digital.
Sequence of Events.
Pulsed Input.
234
Transforms of Analog inputs.
Calculated logicals (Boolean).
Analog calculated values.
Analog outputs.
Digital outputs.
Relay outputs.
Loop Controllers (modulating and digital).
Serial interfaces.
Turbine Control I/O.
PLCs.
Smart Transmitters.
Digital Valve Controllers.
FOUNDATION Fieldbus.
Profibus DP I/O.
DeviceNet I/O.
Third-party I/O interfaces.
OPC.
Ovation multi-network I/O.
REF_1005
16.3 What are point records?
16.3 What are point records?

A point record stores the information which defines the attributes of a point (see page 234).
Point records are used within each drop, and to communicate over the Ovation network to other
drops. The Ovation system has 11 record or point types:
Long Analog (LA).
Deluxe Analog (DA).
Long Digital (LD).
Deluxe Digital (DD).
Long Packed (LP).
Deluxe Packed (DP).
Module (one size - RM) (This point is read only in the Control Builder.)
Node (one size - RN) (This point is read only in the Control Builder.)
Packed Digital (one size - PD).
Algorithm (one size - LC).
Drop (one size - DU).
The record types have two possible sizes: Long and Deluxe. Only the Analog, Digital, and Packed
record types can have Deluxe records.
Long records are the default and have full alarming and I/O capabilities. Deluxe records (an
optional feature not used by standard Ovation software) provide two additional functions:
Limits can be defined that are based on plant mode (1 up to 6). Plant mode is configurable
and is used to define the current state of the plant (for example, 1 could represent plant startup). If the plant mode changes, then the active limits would be the limits that were defined for
that specific plant mode.
The scan time can be displayed in these fields.
Point records are constructed of record fields. Some fields can be defined by the user, while other
fields store information the system needs to process the point value. (See Ovation Record Types
Reference Manual.)
You cannot configure the point fields from the Control Builder; you must use the Developer Studio
to customize any necessary fields.
Point record information is required in many contexts when programming the Ovation system.
Every drop incorporates a point database, which must be defined to include all of the points
originated or received by the drop. In addition, each drop's application may use specific point
record fields. Examples of tasks which require familiarity with point records include the following:
Defining the point database for any drop.
Creating graphics which include process point information.
Troubleshooting system faults.
REF_1005
235
16.4 What is point frequency?
16.4 What is point frequenc y?

Frequency is the measurement of the number of occurrences of a repeated event over a period of
time. Point frequency is the number of times per second that a point is broadcast on the Ovation
network. Points are scanned according to the frequency that is defined for the point. (F)ast points
are scanned every 0.1 of a second, (S)low points are scanned every second, and (A)periodic
points are scanned according to need and user definition.
16.5 Understanding point names

Point names are defined early in the system process either through the Database Initial Definition
tool (DBID) import file or through the Ovation Developer Studio. The point names are entered into
the system database. Point names are based on the ISA-style point naming convention which can
be found on the ISA Web site (www.isa.org).
Typically, the point names are based on the field equipment they will be associated with.
For example, a point name that can be used for a pump valve could be B1AHVAO1232.
Where:
B = Boiler.
1 = Boiler number.
AH = Ash Handling.
VAO = Valve - Air Operated.
1 = First Floor.
232 = Individual equipment number.
A database contains multiple point names that should be appropriately named to ensure that the
point names can be mapped to the applicable element in the plant.
Note: Typically, these point names become fully qualified point names when they are used in
the Ovation Distributed Database.
16.6 Using valid Ovation point names

Use the following rules to ensure valid point names in your Ovation system:
1. All points in the Ovation system are fully specified by three parameters:
Point name
24-character maximum for Windows-based systems.
Six-character maximum sub-network (unit).
Eight-character maximum network name.
A fully qualified name follows the format name. unit@network. The (.) and @ are reserved
characters for point names.
However, when inserting a point into the Ovation Developer Studio, do not enter fully qualified
names. Only the point name parameter is used.
2. A point name cannot be a reserved word (see Ovation Graphics Language Manual for more
information) or contain reserved characters (see the following table).
236
REF_1005
16.6 Using valid Ovation point names

Reserved point name characters
CHARACTER
ASCII
(IN HEX)
CHARACTER
ASCII
(IN HEX)
CHARACTER
ASCII
(IN HEX)
24
2A
7E
25
2C
60
&
26
40
27
2E
5C
22
3. Characters may be any combination of alphabetic, numeric (0 - 9), or special punctuation

characters.
4. Do not begin user defined point names or Control Builder default point names with OCB.
5. Some special characters that may be used are listed in the following table (Valid Point Name
Characters).
6. Point names are not case sensitive. Lower case characters convert to upper case. For
example, point name A0113 is considered the same as a0113.
7. Do not include a space in a point name.
Valid point name characters
CHARACTER
REF_1005
ASCII
(IN HEX)
CHARACTER
ASCII
(IN HEX)
CHARACTER
ASCII
(IN HEX)
21
3F
56
23
41
57
28
42
58
29
43
59
2B
44
5A
2D
45
[*
5B
2F
46
]*
5D
30
47
5E
31
48
5F
32
49
7B
33
4A
7C
34
4B
7D
35
4C
36
4D
37
4E
38
4F
39
50
:*
3A
51
3B
52
237
16.7 Using fully qualified point names
CHARACTER
ASCII
(IN HEX)
CHARACTER
ASCII
(IN HEX)
<*
3C
53
3D
54
>*
3E
55
CHARACTER
ASCII
(IN HEX)
* Emerson recommends that you do not use these characters in point names since they may cause confusion on
control sheets.
16.7 Using full y q ualified point names

Once a point name is in the Ovation database, it can be identified by a fully qualified point name
that describes the location of the point. A fully qualified point name consists of three parameters:
Point name (up to 24 characters for Windows)
Unit name (up to 6 characters)
Network name (up to 8 characters)
For example, B1AHVAO1232.UNIT3@NETWORK1 would reference point B1AHVAO1232

located in the unit whose name is UNIT3 and in the network whose name is NETWORK1. This
allows for the use of the same point name in different units or networks. Ovation is able to identify
each point since a unique SID was assigned to each point as it was entered into the system.
During point retrievals, fully qualified point names are built dynamically from the three parameters
(point name, unit name, and network name) and displayed as requested. This is true for Ovation
Engineering applications (using the Master Database) or for Operator Station applications (using
the Distributed Database). When creating a point name through the Ovation Developer Studio,
only the basic point name should be used.
16.8 Creating the Ovation Database

The creation of the Ovation Database is a product of a combined effort between customer design
engineers and Emerson project engineers. Typically, the following process is used:
1. You determine the names and types of I/O points that are needed for your system. This
information is based on the quantity and types of devices that need to be monitored in your
control system.
2. You and/or Emerson enter these points into a database tool (such as DBID, Access, or Excel)
along with the fields required for each point.
3. Emerson decides what Ovation I/O modules are needed in order to handle the proposed
points.
4. Emerson determines how I/O modules should be mounted in the system cabinets so that the
total of all the points can be partitioned accordingly.
5. You provide point information and that information is entered into DBID and then imported
into the Master Database.
6. Point-by-point changes are done using the applicable point building tool. After the edits are
completed, the file is imported into the Master Database again.
238
REF_1005
16.8.1 Database tools

The following table provides brief descriptions of the various database tools used to populate the
Ovation database.
Database tools and descriptions
TOOL
DESCRIPTION
DBID (see page 239)

(Emerson Tool)
Microsoft Access graphical interface used to create points in a text (ASCII) file that can
then be imported into the Master Database.
OvPtImport
(Ovation Tool)
Imports data from a text file (for example, a DBID produced file) into a Master
Database. Can be used to restore the database (using data from a previous OvPtExport
file).
do_ptadmin_import
Restores the database from the backup that was created.
(Ovation Tool)
OvPtExport
(Ovation Tool)
Exports data from the Master Database and produces a text file. This file does not
contain SIDs or a point's network interface information.
imp
(Oracle Tool)
Can be used to restore a database after a catastrophic failure (such as a disk crash).
Operates on the binary file produced by exp. Not recommended.
exp
(Oracle Tool)
Can be used to backup a system. Produces a binary file.
16.8.2 What is the Database Initial Definition tool (DBID)?

The Database has the potential to be a large repository of data. A method was needed to perform
mass data entry and to import data that had been defined in a format foreign to the Master
Database.
To facilitate the initial population of the Database, the Database Initial Definition tool (DBID) was
created. DBID provides a graphical user interface for creating, deleting, and modifying point data.
The DBID also supports mass data entry and global edit/replace functions by allowing you to
modify data directly in the point tables.
DBID is based on the Microsoft Access database products along with other programs used for
data checking. DBID is similar to the Ovation point building program, since it contains forms for
definitions and configuration of hardware in the system and for entry and editing of the point data.
Data may be entered manually or point data may be loaded from a number of other sources such
as DBASE or spreadsheet files. Some customer conversion may be required, depending on the
structure of the external data.
DBID generates a text file that can be imported by Emerson Process Management into the
Ovation Database.
Once information is entered in DBID, processed by Emerson Process Management, and imported
into the Master Database, it can be modified through the Ovation point building process on a
point-by-point basis.
Note: For more information, refer to the DBID documentation.
REF_1005
239
16.8.3 Entering information in DBID fields

In order to correctly identify information for the points in your Ovation system, you must enter
information into Data Base Initial Definition (DBID) fields. The main fields are listed below, but
different point types require different fields. Work with your Emerson project engineers to ensure
that you are completing your DBID fields correctly.
Point Name (PNAME) is a text field (1 to 24 characters for Windows).

Point names ARE NOT case sensitive. Lower case letters are converted to upper case.
Characters A through Z and numbers 0 to 9 are all valid.
DO NOT use special characters: @ % & * , \ ~ ' ` " . or space.
Description (DESC) is a text field from 1 to 30 characters.
Input Output or SOE (HW_IN_OUT) field. For analogs, set this field to AI, AO or PI (pulse
input). For digitals, set this field to DI, DO, RO, or SOE.
Transmitter Description (XMIT_DESC) field. For analogs, set this field to 4-20ma, RTD-Pt,
Type E, Type K, etc. For digitals, set this field to 48 VDC, 120 VAC, 125 VDC, etc.
Power (POWER) field. For 4-20 analog inputs, set this field to SELF or FIELD (All analog
outputs, thermocouples, and RTDs will be SELF). This defines who is supplying the loop
power. For digitals, set this field to SELF or FIELD. This defines who is wetting the
input/output contacts.
FIELD = field powered points.
SELF = DCS powered points.
High Operating Range (HOPRANGE) - Set this field to the high operating range for each
thermocouple input. This is used to select the proper thermocouple module. High temperature
ranges for the available mV range thermocouple modules are as follows:
Type E :
0-20mV = 548.6 deg F
0-50mV = 1223 deg F
0-100mV = 1832 deg F
Type K :
0-20mV = 905 deg F
0-50mV = 2251 deg F
0-100mV = 2498 deg F (54.8mV)
240
REF_1005
Cabinet (ANC_1) - Set this field to the cabinet location (name or number) for each point.
ANC_2 through ANC_100 are available for P&ID number, transmitter tag, etc. Provide any
special requirements on distribution of I/O (if related digital inputs and outputs require
adjacent terminations, etc.).
Engineering Units (ENGUNITS) is a text field from 1 to 6 characters. Set to DEGF, T/H,
etc. If possible, only use the first four characters (since the standard process point macros
used in custom graphics use only the first four characters).
Low and High Operating Ranges (LOPRANGE) - Set these fields to the low and high
operating range (in engineering units).
Set and Reset Descriptions (SETDESC) - These are text fields from 1 to 6 characters long.
They provide a textual description of the corresponding SET (value = 1 or TRUE) and RESET
(value = 0 or FALSE) for use in displays and reports.
Characteristics (CHARST) provide a method for sorting the database based on plant area,
signal type, equipment, or other concepts you may want to use. There are eight alphanumeric
characters available per point.
Usually the point name contains some combination of alphanumeric characters that define the
plant area (feedwater, steam, etc.) and signal type (flow, temperature, etc.). These characters
are usually a good basis for building characteristics. Each Operator Workstation can be
defined to receive alarms from specific plant areas or destinations. This is done by assigning
a unique destination to each point.
The destination is defined by the first character in the CHARST field. The destination must be
either a letter (A to Z), a dash (-) (which matches all characters on a given sort), or a blank ( )
(which does not match any character). Points that are alarmed cannot have a blank
destination. Characters 2 through 8 may be any alphanumeric character (A-Z, 0-9, -, or
blank).
REF_1005
241
E C T I O N
17
17 Planning software installation for Windows-based

Ovation systems
IN THIS SECTION
Understanding the software installation process for Windows-based Ovation systems . 243
What is the domain concept? .......................................................................................... 244
Best practices for installing Ovation system software ..................................................... 245
What are the hardware requirements for a domain controller? ...................................... 245
What are the hardware requirements for a domain member as a Database Server? .... 245
What are the software requirements for a domain controller? ........................................ 246
What are the software requirements for a domain member? ......................................... 246
What are the licensing requirements for an Ovation Windows-based system? ............. 247
What is the drop type? .................................................................................................... 248
17.1 Understanding the softw are installation process for Window s based Ovation systems
The process of installing and maintaining the required software on your Ovation system drops
consists of several operations:
Planning Security for your Ovation system.
Creating a domain for your system by defining the drop that will function as the primary
domain controller. All other drops in the system will function as domain members or as
redundant domain controllers.
Installing the appropriate Windows operating systems on your drops.
Defining the appropriate drop type for each drop (see page 248).
Installing the appropriate software applications on drops.
Updating your Ovation software as needed.
Providing a reliable method to back up and restore your Ovation system.
Note: Always refer to the applicable Ovation Software Installation Manual for complete
instructions on installing and configuring software on your Ovation system.
REF_1005
243
17.2 What is the domain concept?
17.2 What is the domain concept?

It is assumed that your Ovation system has been carefully designed before you begin the
software installation process for your Ovation system. You need to know how many drops your
system contains and what the drop functions are.
You also need to have a security plan for your system. Ovation incorporates a security approach
that provides for the assignment of security roles for users and drops in the domain.
Ovation systems prior to Ovation 2.4 use the Windows workgroup model to logically group
computers and handle security on a network. In this configuration, all computers on a network are
considered as equals and each one maintains its own security policies and database of
resources, such as users, printers, file shares, and so forth. Although this model is simple to
configure, managing this model is difficult because the administrative tasks are decentralized and
need to be performed on each computer. For example, user accounts need to be created on each
individual computer in a workgroup model network.
Ovation systems beginning with Ovation 2.4 use the Windows domain model to logically group
computers and handle security on a network. In this configuration, all computers on a network are
part of a domain whose security is controlled by drops configured to be the domain controllers.
In the domain model, the security policies and database of resources, such as users, printers, and
file shares are stored in a central location on servers (known as a domain controllers) and are
shared by all computers on a network. Although this model requires domain controllers, it is easy
to manage because of the centralized administrative nature. For example, user accounts need to
be created only once on a domain controller and all domain member computers can then share
the user accounts.
Most drops on the system contain the Ovation Security Manager application (not required on
redundant domain controllers). The drop that is selected to manage the security is promoted to be
the primary domain controller. After this drop is promoted, the Security Manager Server software
is installed on the drop. This enables the drop to manage the security for all the drops in the
domain. Any drop in the system that is not a domain controller drop is configured to be a domain
member and runs the Security Manager Client software.
Before you install the software on a drop, you need to decide what domain role the drop will
perform.
Primary Domain Controller - This station manages group policies plus computer and user
information for the entire domain.
Redundant Domain Controller - This station takes over domain security management if the
primary domain controller fails.
Domain Member - This station is a client of the domain controllers.
Note: The Security Manager Server software which runs on the primary domain controller can
be successfully installed on a drop even if the drop does not contain the Ovation software. This
means you can have domain controllers in an Ovation system that are not Ovation stations.
244
REF_1005
17.3 Best practices for installing Ovation system software
17.3 Best practices for installing Ovation system softw are
You must have a primary domain controller on every Ovation system that is 3.0 or beyond.
Create the primary domain controller for your system before you create your other drops
(including redundant domain controllers).
The first software installation in a new system should be the installation of Windows Server
2008 Standard Edition operating system - English version - 32 bit (with Service Pack 2) on the
drop that will be the primary domain controller. This creates a domain, and all subsequent
Ovation drops will then join that domain.
Do not define a primary domain controller to be an Ovation Operator Station or an Ovation

Base Station in your system.
You may define a redundant domain controller to be an Ovation Operator Station, an Ovation
Base Station, or a Database Server in your system.
If you have multiple Ovation networks/systems, you can manage security more efficiently if
you create an Ovation Security Server to function as the primary domain controller. This
provides centralized security administration for all the networks.
A Database Server can only run on a Windows Server 2008 Standard Edition operating
system - English version - 32 bit (with Service Pack 2) as a Domain Controller or a Domain
Member.
17.4 What are the hardware requirements for a domain controller?

You must configure one computer on an Ovation system to act as a primary domain controller.
Optionally, you can configure one or more computers to act as redundant domain controllers.
The following minimum requirements are needed for a computer that will serve as a domain
controller:
Standard Intel Pentium computer with a minimum processor speed of 2GHz.
At least 1 GB of RAM for an Ovation Security Server.
At least 2 GB of RAM for a domain controller that is also a Database Server.
At least 2 GB of free disk space for an Ovation Security Server.
At least 25 GB of free disk space if a domain controller is also a Database Server.
A DVD drive.
At least 2 physical hard disks for database servers.
17.5 What are the hardware requirements for a domain member as a

Database Server?
The following minimum requirements are needed for a computer that serves as a domain
member:
Standard Intel Pentium computer with a minimum processor speed of 2 GHz.
At least 2 GB of RAM for a domain member.
At least 25 GB of free disk space for a domain member.
A DVD drive.
At least 2 physical hard disks.
REF_1005
245
17.6 What are the software requirements for a domain controller?
17.6 What are the software requirements for a domain controller?

You must configure one computer in an Ovation system to act as a primary domain controller.
Emerson recommends that you configure one or more computers on an Ovation system to act as
redundant domain controllers, although this is an optional practice it is the recommended practice.
The following minimum requirements apply to a computer that will serve as a domain controller in
Ovation 3.3.1 or 3.4 systems:
Windows Server 2008 Standard Edition operating system - English version - 32 bit (with
Service Pack 2).
Computer must be promoted to a Domain controller.
Domain naming service (DNS) installed.
17.7 What are the software requirements for a domain member?

Any computer in a domain that is not a domain controller, is considered to be a domain member.
The following requirements apply to a computer that will be a domain member in Ovation 3.3.1 or
3.4 systems.
The computer must use one of the following Operating Systems:

Windows 7 Professional Edition - 32bit.
Windows Server 2008 Standard Edition operating system - English version - 32 bit (with
Service Pack 2).
Windows XP professional edition operating system - English version (with Service Pack
3).
Windows 2003 Server Standard Edition operating system - English version (with Service
Pack 2).
If the computer will not be an Ovation drop, it must use a Windows 7 (preferred), XP or later
operating system.
If the computer will be a database server, it must run Windows Server 2008 Standard Edition
operating system - English version - 32 bit (with Service Pack 2).
Note: Refer to the applicable Ovation Software Installation Manual (OW_3.x.x_10) for additional
software level information.
246
REF_1005
17.8 What are the licensing requirements for an Ovation Windows-based system?
17.8 What are the licensing requirements for an Ovation Window s based s ystem?
Plan your software installation or upgrade to ensure that you will have key codes or license files
readily available when they are needed during the installation. These licenses are available during
normal work hours from your Emerson representative. Depending on your situation, this contact
might be your project engineer, after-market representative, or Field Service engineer. Contact
Emerson prior to installations or upgrades to ensure the availability of required key codes or
licenses.
If you are planning to perform a new installation, you would typically contact your project
engineer.
If you are planning to perform an upgrade, you would typically contact your Field Service
engineer or possibly your after-market representative.
Note: If your system was initially loaded at the Emerson plant, the license codes that were used
for the load procedures will be provided in your Software and Licensing Kit binder. However, if
you are upgrading the Windows Operating System, you will need a new Microsoft product key
code.
If you are performing an emergency reload, you can call 1-800-445-9723 for license
assistance. Be prepared to provide your name, your project or company name, and the exact
nature of your installation needs. Your call will be evaluated for emergency status and then
forwarded to the appropriate support department. You will receive a response as soon as
possible, based on your need and on the level of your Support Agreement with Emerson.
The following software packages require licensing:
Microsoft Operating System - A product key is provided by Microsoft with the software
media or by Emerson in the Software and Licensing Kit binder. This key is needed when you
prepare a drop to be a Database Server or an Operator/Base Station.
Make sure you register your operating system with Microsoft within 30 days or you may be
locked out of your system.
Note: If you are upgrading to a new Windows operating system, you will need a new Microsoft
product key code from Microsoft or Emerson.
Ovation - A key code will be requested during the installation. Send the Locking Code that is
displayed in the License Manager to Emerson. A key code will then be provided by Emerson
(this key code is needed when you install Ovation on a Database Server or an Operator/Base
Station).
Note: A ten-day trial license automatically takes effect at the initial installation of Ovation on the
Ovation Database Server. The trial license permits the configuration/specification of the
maximum number of Ovation drop types, limited only by the overall number of drops in the
system.
The trial license also provides one floating license for each of the engineering applications. The
ten-day trial permits the system to be used until the proper license codes and license keys are
acquired from Emerson Process Management. During the trial period, messages appear stating
the number of days that remain in your trial license.
REF_1005
247
17.9 What is the drop type?
17.9 What is the drop type?

Before you install software on an Ovation drop you must determine what drop type you want this
drop to be.
When you install Ovation on your drop, you are prompted by the "Select Drop Type" window to
select the desired drop type. The drop type choices are presented on the Ovation DVD and your
selection determines what software will be installed and how it will be configured. This choice is
made during the Ovation installation process.
248
Ovation Operator Station - This choice installs the Developer Studio package, Ovation
applications, and point management services.
Ovation Base Station - This choice installs Point Information, Error Log, and point
management services. This type can view the security settings. (This type is not
recommended for installation on a primary domain controller.)
Ovation Database Server - This choice installs the Developer Studio, Ovation Operator
Station Applications, point management services, and Oracle software for the database
functions.
Ovation Security Server - This choice installs the Security Manager software but no Ovation
applications. This computer is not a member of any Ovation network and will not appear in
any Developer Studio tree.
REF_1005
E C T I O N
18
18 Planning control for your Ovation system
IN THIS SECTION
What is Ovation control? ................................................................................................. 250
What types of control are supported in Ovation? ............................................................ 251
What is the Ovation Control Builder? .............................................................................. 252
Control Builder terminology ............................................................................................. 253
What is the control planning process? ............................................................................ 256
What is the scope of your control project? ...................................................................... 257
What are the best practices for planning control? ........................................................... 257
Planning for system expansion ....................................................................................... 259
Using diagrams in planning control ................................................................................. 260
What are the best practices for designing control? ......................................................... 260
What are Ovation control functions (control sheets)? ..................................................... 261
What are the best practices for building control sheets? ................................................ 262
REF_1005
249
18.1 What is Ovation control?
18.1 What is Ovation control?

An Ovation control system is an advanced system that plans and manages processes such as
steam generation, water purification, and chemical containment with accurate precision.
Companies and utilities use these processes to provide electricity, purify waste water, and confine
undesirable chemicals.
WARNING! This process management is accomplished by sophisticated hardware and
software working together to provide information and guidance between field devices out in the
plant and an Ovation Controller. Ovation control systems use either discrete logic (digital) or
continuous modulating control (analog) to send the commands from the Controller to the
devices.
The devices in the plant monitor processes and make physical changes to the process as
needed. These changes might be to open a valve, close a switch, or sound an alarm. Each
monitored process is based on pieces of data (known as process points) that carry information
about the process throughout the Ovation system. These points carry the current value of the
process variable (for example, temperature, pressure, or volume) from the devices to the
Controller.
The Controller in the plant is typically a cabinet that contains Input and Output modules that
connect to the field devices by wires. These modules monitor each device for any change in the
devices condition. When a change is detected (input), the Controller reads the change and tells
the device (output) to perform an action that the Controller decides is appropriate.
This action has been programmed into the Controller by control sheets (also known as functional
drawings) that are created in the Ovation Control Builder. The Control Builder sheets consist of
building blocks (algorithms) arranged in a logical pattern that defines in detail what action should
be taken when certain events occur in a device. These algorithms are linked by signals and can
represent a simple two-step process or a complex process made up of many algorithms
contained on many sheets.
The Ovation control systems consist of three elements: input, control logic, and output.
Input consists of analog or digital signals collected from field devices. These devices control
some physical operation in the field.
Control logic is created in the Control Builder and processes the input information and
determines which output functions should be activated.
Output consists of analog or digital signals defined by the control logic and sent out to
activate the appropriate field devices.
These elements of control can be displayed to the user as graphics, instead of complex
programming commands. These graphics provide a user-friendly representation of the strategy.
Control can then be monitored and modified from these diagrams (in real time) by tuning the
constants, logic, and control schemes.
250
REF_1005
18.2 What types of control are supported in Ovation?
18.2 What types of control are supported in Ovation?

Ovation supports various types of control. The control type that you choose to run a process
depends on the device that you want to control and what type of output is required from the
process. You must choose algorithms that are designed to perform the various types of control
carefully before you add them to the control sheet.
The following control types account for most of the possible Ovation control schemes.
Sequential Control (digital).

Sequential control is instantaneous in response time if the proper conditions exist (that is,
when the input occurs, usually the output follows immediately). For example, when an
operator presses the button to start a pump, the pump either starts or it does not. The various
types of sequential control are:
Boolean - AND, OR, NOR logic. Output = on or off; 1 or 0; yes or no.
Ladder logic - Similar to Boolean. Simulates electrical relay system.
Note: Ovation supports ladders created in WDPF systems and migrated to Ovation systems.
However, ladders typically are not used in the design and implementation of new control logic in
an Ovation system.
Continuous Modulating Control (analog).

Modulating control is not instantaneous in response time. It occurs over a given time period.
Typically, an operator defines a desired value for a process and the control system works to
attain that value. For example, when the desired level or set point for a tank is set by the
operator, the system cannot obtain that level instantaneously. It takes time to either raise or
lower the level until it matches the set point. The various types of modulating control are:
PID Control - Proportional, integral, and derivative. Output = results of PID equation.
Lead/Lag functions - Nonlinear lead/lag control. Output = function of old output, old input,
new input, gain, and lead/lag time constants.
Hi/Low/Medium select - Measures and compares inputs.
Rate of change limit - Rate of change in input. Output = rate sampled every second.
Total, average, weighted averages - Measures and calculates inputs. Output = sum or
average of inputs.
Sample and hold - Mathematical calculations of sample inputs.
Mathematical functions - Sine, Cosine, Sum, Divide, Log, and so forth.
Operator Station functions - Keyboard, MA Station.
Adaptive and auto tuning control - Dynamic functions.
Advanced Control
Advanced control uses sophisticated algorithms that can adapt control strategies to meet
the control process requirements. This type of control is typically used for the following:
Equipment startup.
Demineralization.
Optimal valve settings.
Plant performance, Opacity, and Low NOx optimization.
Advanced sootblowing.
REF_1005
251
18.3 What is the Ovation Control Builder?
18.3 What is the Ovation Control Builder?

The Ovation Control Builder is a graphical editor that creates the control logic that runs in the
Ovation Controller. This logic consists of algorithms that are placed on functional drawings (also
known as control sheets) and direct the control strategy for the Ovation system. Typically, there
are many different control sheets linked together to form the complete control structure for an
Ovation system.
The Control Builder application consists of three main areas or windows:
Main window with the drawing canvas.
Object Browser.
Property Editor.
Each window has a different function, but they all work together to give you a complete picture of
your control. In general, items such as inputs, algorithms, signals, and so forth appear on the
drawing canvas, which provides the visual display of the sheet. Any item that you place on the
drawing canvas is put into the hierarchy in the Object Browser. The Object Browser shows the
relationships between the items placed on the drawing canvas. The Property Editor is used for
editing the attributes of the items found on the drawing canvas and in the Object Browser.
Since the three main areas of the Control Builder give you a different perspective on your control
function, there are many ways to perform various tasks. This makes the application flexible and
easy to use since you choose which way is best to perform a certain function.
All Control Builder windows are dockable and floatable. Dockable means it can be attached to
one of the sides of the main window. Floatable means it can be displayed as a pop-up window
with a title and a window close button in the upper right corner.
The following figure shows an example of how the Control Builder may look loaded with a control
function. Since the Control Builder application is flexible and configurable, you may move, resize,
or close windows in order to create more drawing space.
252
REF_1005
18.4 Control Builder terminology
Figure 53: Control Builder main window

The following sections of this document discuss each area of the Control Builder application,
along with its menus and toolbars. Understanding how these main areas work together enables
you to use the Control Builder quickly and efficiently when creating various control functions.
In addition to the three main windows, the Control Builder uses other windows and dialog boxes
to design control functions. These windows are also discussed throughout the document.

The following terms and descriptions may be helpful to your understanding of the Ovation Control
Builder.
Control Builder terminology
TERM
DESCRIPTION
Algorithms
Set of rules, procedures, and mathematical formulas that define a control strategy.
(See Ovation Algorithms Reference Manual.)
An algorithm does not have a name; it is a collection of points and is identified by
the Algorithm Control Record.
Aperiodic Points
These are points whose values are scanned as needed or as requested. See
also Periodic Points.
Asynchronously
Performed at different times. For example, control tasks operate asynchronously.
Batch Processing or
Run Scripts
Performs same operation on multiple control sheets.
REF_1005
253
TERM
DESCRIPTION
Component Code
Text strings that represent a sheet's or document's location in a folder structure or

hierarchy.
Configuration Tool
Software function used to configuration parameters for the Ovation system. For
Ovation Windows systems, the configuration tool is the Developer Studio.
Control Function
Drawing that contains a graphical representation of a control scheme.
(also known as a
control sheet or
functional drawing)
Control Task
(also known as Set
or Area)
Refers to a specific Controller area where all the control sheets in that area are
scanned at the same frequency. Up to five control tasks can be defined.
All the sheets in the Control Task 1 area are scanned every 0.1 second or 100
milliseconds (also known as fast time).
All the sheets in the Control Task 2 area are scanned every 1 second or 1000
milliseconds (also known as slow time).
The scan times for sheets in Control Task 3, 4, and 5 are user-defined.
Points are grouped by control tasks so they can be updated (scanned) at different
rates. The rate is set in the applicable Ovation configuration tool during configuration
for a Controller drop.
It is recommended that third-party points have their own task area and their scan
rate should be no faster than one second because of communication overhead.
Cycle
Time interval during which the scanning of inputs, execution of algorithms, and the
transmission of output values to devices occur.
Deadband
The range of values through which an input signal may vary without initiating an
action of causing an observable change in the output signal.
Database
Contains information about the system configuration, the system points, and control
strategies.
Default Points
Points created by OCB that have the following naming convention:
(see also UserDefined Points)
OCBssssaaa-pppp, where:
ssss = Unique sheet identifier (Hex)
aaa = Unique algorithm identifier (Hex)
pppp = Parameter mnemonic (for example, OUT)
254
Discrete Control
Control where inputs, algorithms, and outputs are based on logical values (yes/no,
on/off, or 0/1).
Distributed Database
Contains a subset of the information stored on the Master Database and is stored
locally on a drop to allow that drop to operate if the Master Database is unavailable.
A Distributed Database is present on each drop in the system and is continually
updated as point information changes.
Hyperlinks
Mechanism for linking sheets and documents to each other.
Interlocks
Interlocks are the situations where the status of a device is affected by the status of
another device. For example, if the temperature in a water tank increases, a valve
opens. When the valve opens, a switch closes. Interlocks are often used as safety
precautions when planning a control strategy.
Macro
A user-defined control strategy, with clearly defined inputs and outputs. Even though
a macro typically consists of several algorithms, it is represented in a functional
drawing as a single user-defined algorithm.
REF_1005
TERM
DESCRIPTION
Master Database
Contains the entire process database. It is used for creating, modifying, and
verifying control strategies and process points. At runtime, it supports queries of the
process database, captures changes made to control and point attributes, and
propagates those changes to the distributed databases.
Mode
Control block operational condition, such as manual, automatic, or cascade.
Object Browser
Control Builder window that shows the relationships between the items placed on
the drawing canvas.
Originated Points
Points that were created in the current drop. For example, Drop 202 refers to all
points that were created in Drop 202 as originated points.
Periodic Points
These are points whose values are scanned periodically at a defined frequency
such as 0.01 of a second. See also Aperiodic Points.
Plant Area
Designated points (inputs, outputs, and calculated values) that belong to a

geographical or functional section of a plant.
Point
Process variable derived from an input signal or calculated in a process calculation.
Property Editor
Control Builder window that is used for editing the attributes of the items found on
the drawing canvas and in the Object Browser.
Received Points
Points that were not created in the current drop. For example, Drop 202 refers to all
points that were created in Drop 210 as received points.
Redundant Pair
Mismatch
When Control information between a pair of redundant Controllers is different.
Regulatory Control
Functions of control (process measurement, algorithm execution, and final control

device manipulation) that provide closed loop control of a plant process. For
example, an operator defines a value for a process setpoint, and the control process
adjusts until it achieves that setpoint.
Safety Instrumented
System (SIS)
A set of components that includes sensors, Logic Solvers, and final control elements
whose purpose is to respond to plant conditions, which may be hazardous. A project
must purchase a Safety Instrumented System in order to access the SIS algorithms.
Scratchpad
Temporary library file.
Signals
Lines connecting algorithms on a sheet. Signals start from an algorithm output pin
and connect to one or more algorithm input pins. They are comprised of one or more
segments.
Signal Diagram
Ovation Operator Station application that monitors or tunes a control process.
Signal Doughnut
Circle representing multiple downstream connections.
Signal Junction
Where two or more signal segments connect. If more than two signal segments
connect, a signal doughnut is visible.
Signal Segment
Primary building block of a signal. Straight line with a start point and an end point.
Supervisory Control
Higher level control functions that interface with regulatory control functions. For
example, an Advanced Control process outside the control loop defines a value for a
process setpoint, and the control process adjusts until it achieves that setpoint.
Supplemental
Documents
Any documents that do not have control associated with them. There is no algorithm
folder attached to the document. Examples of supplemental documents include
Microsoft Word files, pdf files, and Control Builder simple graphic .svg files.
Tracking
Exchange of information between different control strategies (for example, going

from manual to automatic mode).
REF_1005
255
18.5 What is the control planning process?
TERM
DESCRIPTION
User-Defined Points
Points created by you through the Ovation Developer Studio (Windows systems).
Do NOT begin these point names with OCB.
(see also Default

Points)
Zoom
Changes magnification (larger or smaller) of objects or of complete drawings.
18.5 What is the control planning process?

When you must plan a control procedure, there is a best practice process that helps to ensure
that the final outcome of the process will be a successful control scheme. The following
information lists the steps used in this planning process. Additional information about each step is
provided where indicated:
Note: This process assumes you are a proficient process control engineer or the equivalent.
1. Investigate the contemplated process and determine what functions you need to control and
what would be the best way to accomplish that control.
2. Storyboard the process. This involves breaking the entire control scheme into smaller and
more manageable pieces with each piece containing distinct functionality.
3. Separate the control into the Controller that has the I/O associated with that Controller.
4. Construct any standardized control for the system so that it can be used numerous times
throughout the system.
5. Test the standardized control before reproducing the control for each associated device.
6. Build the control and load the Controller.
7. Test the control sheets in an offline Simulator environment.
8. Commission or tune the sheets in the field to ensure all the control processes work as
planned.
256
REF_1005
18.6 What is the scope of your control project?
18.6 What is the scope of your control project?

There are many processes in a plant that you need to control. Some possible functions of the
system that you will control are listed below:
Combustion control.
Turbine control.
Burner management.
Flue gas desulphurization.
Water treatment.
Ash handling.
Coal handling.
Limestone handling.
Soot blowing.
Motor control logic.
Data acquisition.
Annunciation.
18.7 What are the best practices for planning control?

Before you begin to plan your control strategies, there are some control building best practices
that provide for simpler and more effective implementation of your control logic:
Organize the control project before you install any system hardware or software.
Collect similar devices into virtual groups and then define the unique devices. For example, all
pumps might be in a group, but the oil pumps would be unique pumps. All pumps could have
the same basic control scheme, but the oil pumps would have special control issues that
would require additional control logic.
REF_1005
257
18.7 What are the best practices for planning control?
Rework is time consuming. Carefully consider your goals before you commit your control
schemes to a control sheet.
Identify algorithms correctly from the beginning of your control plans. If algorithms are not
correctly identified, you will need to perform rework to avoid inconsistencies and rework is
always difficult and costly.
Spend time reviewing the P&ID drawings and determining how you should map the database
points (process points) to the processes that you want to control.
Determine what types of sensors will be used in the field.
Define what inputs and outputs need to be monitored. How will interlocks be handled?
Interlocks are the situations where the operation of a device is affected by the status of
another device. For example, if the temperature in a water tank increases, a valve opens.
When the valve opens, a switch closes. Interlocks are often used as safety precautions when
planning a control strategy.
Plan to use some form of simulator to test the control logic as you create it. Avoid testing the
logic on a running plant whenever possible.
Minimize signal crossing in your drawings to avoid confusion where lines meet and cross.
Use tags where ever possible for any dynamic analog values for algorithms. Comments do
not dynamically update.
Remember the basic concepts of how changes to control sheets are saved to the database
by the Control Builder:
If a sheet is open when a change is made to the sheet, the sheet is master, and the
changes are saved to the database from the sheet.
If a sheet is closed when a change is made, the database is master, and the changes are
saved to the sheet from the database.
The Control Builder configuration file is always the master, and any changes made to it
are saved to the sheet and to the database.
258
REF_1005
18.8 Planning for system expansion
18.8 Planning for s ystem expansion

An Ovation Distributed Control System is designed for future expansion. You can expand your
Ovation system by adding the following:
Hardware cabinets containing I/O modules.
Input/output points and local/remote I/O.
Programmable Logic Controllers (PLCs).
Operator Station, Engineer Station, and Controller drops.
Peripherals.
Control loops.
Sequential control (ladders, Boolean).
Data acquisition functions.
Regulatory and supervisory control.
Typically, the future plans for a system are known in advance. This knowledge makes it easier to
add control by following these guidelines:
Use a modular approach to develop your control logic. This enables you to easily reuse
portions of the logic in future control schemes. It is also easier to troubleshoot logic that is
made up of modules instead of one long extensive function.
Create blank control sheets between functions so you can easily add to your control plan.
Make sure that there are enough points created so you can expand your system as needed.
Remember to consider:
Memory allocation for control tasks. If a task is filled, the Controller must be downloaded,
cleared, and loaded to extend the space.
Point limitations.
Licensing limitations for adding new drops.
REF_1005
259
18.9 Using diagrams in planning control
18.9 Using diagrams in planning control

You need to plan control carefully before you begin creating control sheets. Planning actually
begins before a plant is even constructed or upgraded. Plant engineers or Architectural Engineers
(AEs) typically meet with Emerson representatives to discuss the control needs of the system and
the best control techniques to meet those needs. For example, how much power must a power
plant produce during peak times and what types of emissions must be controlled during those
times? You must consider and address questions such as these, plus many more complex
questions, before actual control schemes are developed and implemented.
At the beginning of the planning process, you should collect and study diagrams from the plant to
help determine the control schemes that are needed to operate the plant processes. Next, a joint
effort between plant and Emerson engineers is employed to create and populate the system
database.
Since a plant may have hundreds of devices that need to be controlled, many control sheets will
be produced and the more planning that is done before those sheets are created, the more
efficient the control creation process will be.
Planning for good control is based on many factors and includes the understanding and usage of
the following topics:
Piping and Instrumentation Diagrams.
Oil Diagrams.
Plant Schematics:
Electrical Drawings.
Control Wiring Drawings (CSDs).
18.10 What are the best practices for designing control?

Spending the time to design your control before implementation saves time and frustration for
your current project and enables you to reuse the control in future projects.
By laying out the design for the control, you create a comprehensive and consistent picture of
how the control functions throughout the system. Your control scheme will be better organized
and the inputs and outputs will be clearer.
Using consistency in the design of control sheets helps to ensure that all engineers involved in the
control system can understand any control sheet in the plant. If every designer uses the same
design process, then any changes that need to be made can be done easily with a minimum of
questions and confusion.
Before you begin to design your control strategies, there are some control building best practices
that you should follow:
Do not force too much control strategy on one sheet. Spread it out so it can be easily read,
understood, and modified.
Troubleshooting a sheet is much easier if the information on the sheet is well organized with
enough space for changes and additions.
Segment the various control functions.

Separate self-contained control functions.
Minimize off-page functions.
260
REF_1005
18.11 What are Ovation control functions (control sheets)?
Block out the analog and digital algorithms that will be used:
Logic is executed in ascending order of the algorithm numbers that are assigned in a
sheet. Typically, build logic from top to bottom and left to right. You need to review the
execution order and override it, as needed.
Logically group functions (for example, put all the temperature logic on a sheet).
You can mix analog and digital algorithms on a sheet.
Analog signals should flow top to bottom. As much as possible, all inputs should be
brought in on the extreme top of the sheet. Outputs should be extended to and shown
on the extreme bottom of the sheet. The logic should be drawn from top to bottom.
Digital signals should flow left to right. As much as possible, all inputs should be
brought in on the extreme left of the sheet. Outputs should be extended to and shown
on the extreme right of the sheet. The logic should be drawn from left to right.
Allow room for descriptions for all signals.

Provide descriptions that allow you to trace logic destinations.
Implementation will be simpler if the BALANCER algorithm and all the downstream balanced
algorithms are on the same sheet.
Segregate the control into specific Controllers based on hardware and available points.
Logic segments that have multiple interlocks should be on different sheets. Segments that do
not have multiple interlocks can be mixed on one sheet.
Typically, tracking from algorithms that have a single track output is out of the IN1 line.
18.11 What are Ovation control functions (control sheets)?

An Ovation control function (control sheet) is a graphical representation of the control logic that is
used by the Ovation system to control the processes in a plant.
Note: Throughout this manual, control functions are also referred to as control sheets, functional
drawings, or files.
The Control Builder creates control sheets and then sends them, as needed, to the Controller. Up
to 1500 control sheets can be maintained in one Controller. The sheet also exists as a graphic file
and has a file name extension of .svg. An example of a control sheet name would be 2250.svg.
The Controller uses the sheets to control and adjust the system processes as needed. These
sheets consist of building blocks (algorithms) arranged in a logical pattern that defines in detail
what action should be taken when certain events occur in a device.
These algorithms on a sheet are linked together by signals to create a control scheme. A control
scheme can represent a simple two-step process or a complex process made up of many
algorithms contained on many sheets.
After these schemes are compiled and verified, they are loaded into the Ovation Controller. A
service running in the background downloads the sheets to the MMIs on startup and every few
minutes. Once sheets are downloaded, they can be used to execute control strategies in Ovation
systems.
REF_1005
261
18.12 What are the best practices for building control sheets?
18.12 What are the best practices for building control sheets?
Refer to the following practices when building control sheets:
262
Plan the use of control task areas carefully. It is time consuming to move control sheets from
one area to another (sheets would have to be libraried, deleted, and re-added to the new
area). Review what is contained in each control task area. (Moving sheets from one task area
to another can be accomplished through the applicable Ovation configuration tool.)
Place all algorithms on the sheet first. Use a full window to make placement easier, then add
signal lines. It is easier to move a single algorithm than to move many algorithms.
Use the entire drawing area since it is easier to read.
Leave plenty of room for editing, connectors, and so forth.
Test control templates thoroughly before duplicating them.
Avoid crossing lines.
Up to 1500 control sheets can be maintained in one Controller, but approximately 800 sheets
allows for the most efficient management of control by one Controller.
REF_1005
E C T I O N
19
19 Planning your Ovation Controller
IN THIS SECTION
What is the Ovation OCR400 Controller? ....................................................................... 263
What are the OCR400 Controller I/O interfaces? ........................................................... 264
19.1 What is the Ovation OCR400 Controller?

The Controller in the plant is typically one or more cabinets containing input and output modules
connected to field devices by wires. These modules monitor each device for changes in the
device's condition. The Ovation Controller communicates with both Q-Line I/O and Ovation I/O, as
well as select third-party I/O. (See the Q-Line Installation Manual and Ovation I/O Reference
Manual.) When detecting a change (input), the Controller reads the change and tells the device
(output) to perform an appropriate action as determined by the Controller.
This action has been programmed into the Controller by control sheets (also known as functional
drawings) that are created in the Ovation Control Builder. The Control Builder sheets consist of
building blocks (algorithms) arranged in a logical pattern that define in detail what action to take
when certain events occur in a device. These algorithms, linked by signals, represent a simple
two-step process or a complex process made up of many algorithms contained on many sheets.
The Ovation Controller is based on the Intel Pentium processor and runs on a commercially
available operating system. The Controller uses an off-the-shelf interface to connect it to the
Ovation network.
Figure 54: OCR400 Controller
REF_1005
263
19.2 What are the OCR400 Controller I/O interfaces?

The Controller executes modulating and sequential control strategies and supports the following
functions:
Originates and receives process points.
Adds, deletes, and modifies points on-line.
Provides alarming and command word processing for originated points.
Reads I/O modules and converts data to process points.
Reads process points and writes data to I/O modules.
Executes control algorithms.
Adds, deletes, and modifies control online.
19.2 What are the OCR400 Con troller I/O interfaces?

The Ovation Controller provides various types of interfaces to communicate with the system and
other devices. These interfaces include:
Ovation network.
Dedicated backup.
I/O devices.
Network interface ports

The Controller's processor module provides four network interface ports, labeled N1, N2, N3, and
N4. These ports are located at the top of the module housing. Port N2 is typically used for single
attached networking to the Ovation network. Port N3 provides an additional Ethernet interface for
dual attached networking. N4 is the default Ethernet interface for dedicated control
synchronization. Port N1 is an additional Ethernet interface for other uses, such as third-party
links, if necessary.
Network Ports
264
PORT
SUPPORTS
N1
Third-party devices.
N2
Single attached network interface.
N3
Dual attached network interface or third-party device.
N4
Dedicated control synchronization or third-party device.
REF_1005
Note: In the OCR400, when using the direct connection (Port N4 to N4) control synchronization,
make sure that both Controllers have control synchronization enabled and that the cable is
attached before performing a download, reboot and load.
If a pair of redundant Controllers has been running with control synchronization enabled and
control synchronization is then disabled, disconnect the dedicated cable from the Controllers
before rebooting the Controllers with the new configuration.
Conversely, if a pair of redundant Controllers has been running with control synchronization
disabled and control synchronization is then enabled, connect the dedicated cable between the
Controllers after they have been running with the new configuration.
I/O interface ports
The Controller's I/O interface module supports up to 16 branches of local Ovation I/O, using ports
L1 and L2, physically located on the Controller Base Assembly, below the Controller. The
Controller also provides three RJ-45 interface ports to support additional local and remote I/O.
These ports are located at the top of the module housing and are labeled Q5, R4, and R3. The
port labeled Q5 supports up to four crates of local Q-Line I/O. Ports R3 and R4 are configured as
a pair. They can support three different options:
Remote Ovation (R3/R4).
Remote Q-Line (R3/R4).
Local Q-Line (R4 only).
When configured for Ovation I/O, up to four nodes of remote Ovation I/O can be supported on
each port. Local Ovation I/O is not supported on either port. When ports R3/R4 are configured for
remote Q-Line, each port can support up to four nodes each with four crates per node. When
configured for local Q-Line, R4 can support up to four crates (1 node) of local Q-Line, but R3 must
be unoccupied.
Note: Ports R3 and R4 can be configured as a pair to support either Ovation I/O or Q-Line I/O,
but not a mixture of the two. Port Q5 supports only local Q-Line I/O. Ports L1 and L2 only
support local Ovation I/O.
The following list shows the configuration options:
Port L1 supports up to 8 local branches of local Ovation I/O.
Port L2 supports up to 8 local branches of local Ovation I/O.
Port Q5 supports up to 4 crates of local Q-Line I/O (1 node).
Port R3 supports one of the following:

up to 4 nodes of remote Ovation I/O.
up to 4 nodes of remote Q-Line I/O.
Port R4 supports one of the following:

up to 4 nodes of remote Ovation I/O.
up to 4 nodes of remote Q-Line I/O.
1 node of local Q-Line I/O.
REF_1005
265

(See the Q-Line Installation Manual and the Q-Line card types section in the Ovation I/O
Reference Manual for information about Q-Line modules.)
The following figure shows the physical locations of the interface ports and their uses:
Figure 55: Interface port locations
266
REF_1005
E C T I O N
20
20 Planning Virtual Controllers
IN THIS SECTION
What is a Virtual Controller? ........................................................................................... 267
Why use Virtual Controllers? ........................................................................................... 268
Requirements for Ovation Virtual Controllers ................................................................. 269
Hardware requirements for the Ovation Virtual Controller host ...................................... 269
Software requirements for the Ovation Virtual Controller host ....................................... 269
What are the licensing requirements for Ovation Virtual Controllers? ............................ 269
20.1 What is a Virtual Controller?

A Virtual Controller is a software representation of a real Ovation Controller, but no Controller
hardware is required.
Virtual Controllers have all the same functionality as real Controllers but do not have the ability to
actually connect to the plant I/O. A Virtual Controller replicates the operation of actual Ovation
Controllers providing an identical representation of an actual Ovation Controller.
A Virtual Controller is:
A software version of an Ovation Controller.
A replica of a real or actual Ovation Controller in a software package.
A replication of real Ovation Controller software, running in a Microsoft Windows PC.
Unlike actual Controllers that run on the VxWorks operating system, Ovation Virtual Controllers
run on Microsoft Windows-based personal computers. Virtual Controllers execute under the
control and guidance of a Virtual Controller Host software package.
The operator interface to Ovation Virtual Controllers is identical to the operator interface to actual
REF_1005
267
20.2 Why use Virtual Controllers?
20.2 Why use Virtual Controllers?

Simulation using Ovation Virtual Controllers can improve plant efficiency and save your
organization time and money. There are many applications for using Virtual Controllers.
When used as a training tool, Ovation Virtual Controllers teach operators to fully understand plant
control prior to plant startup. Operators have an opportunity to practice on a simulated control
system without the concern of tripping or upsetting the operation of the plant. Operators develop a
thorough understanding of how their actions impact plant operation and overall plant efficiency by
operating control equipment identical to the actual plant control system.
When system changes or equipment upgrades are planned, operators use Ovation Virtual
Controllers to become more proficient with their skills by observing system reactions in various
conditions. The overall result of this type of custom training is an operator who has an in-depth
knowledge of plant equipment and plant processes.
Virtual Controllers act as powerful diagnostic tools for engineering analysis. By simulating various
plant operating conditions, engineers can quickly identify areas in need of improvement.
Engineers can use Virtual Controllers to develop and re-engineer control system logic, allowing
them to observe the effect of plant changes prior to implementation without affecting the normal
day-to-day operation of the plant.
Simulation using Virtual Controllers provides an interactive method for training new operators and
can be used as a tool to solve plant problems. Ovation Virtual Controllers let you "test drive" or
practice operating your control system before you actually begin real plant control. As you
become more familiar with Ovation, you will want to use Virtual Controllers to aid in future
decisions regarding plant operations.
Emerson designed Ovation Virtual Controllers for the following reasons:
268
Offer customers a portable simulation system.
Provide a simulation system with less hardware and hardware expense.
Provide full simulation functionality with greater flexibility.
Improve performance of plant technicians and operators through training.
Provide a thorough engineering analysis tool.
Increase cost savings through operator efficiency.
Reduce down time and risk of plant tripping.
Improve efficiency and reduce cost of plant startup and shutdown.
Enhance operator's ability to identify and correct plant upset.
Decrease system and equipment failures.
REF_1005
20.3 Requirements for Ovation Virtual Controllers
20.3 Requirements for Ovation Virtual Controllers

A Virtual Controller Host consists of a Windows-based PC running Virtual Controller software. A
minimum of one Virtual Controller must be loaded on the Virtual Controller Host. You can load a
maximum of five Virtual Controllers on a Virtual Controller Host before a second host is needed.
The host software has the ability to coexist with other Ovation HMIs. Host machines can be any
HMI. For example:
Operator Station.
Engineer Station.
Database Server.
Base Station.
Each Ovation drop, including the host and each of the Virtual Controllers, has a unique IP
address. Therefore, each drop will have its own individual drop identity on the Ovation network.
20.4 Hardw are requirements for the Ovation Virtual Controller host
The amount of hardware necessary for more than one Virtual Controller depends on the size of
your control system and the amount of available memory on the Virtual Controller Host PC.
The minimum hardware requirement to operate one Virtual Controller Host is:
One Windows-based PC (XP or later operating system).
2GB Memory for up to 5 Virtual Controllers.
4GB Memory is required for more than 5 Virtual Controllers.
USB Dongle (hardware key).
2.8 GHz Pentium 4.
20.5 Softw are requirements for the Ovation Virtual Controller host
The following requirements are necessary for software installation of a Virtual Controller:
One Windows-based PC (XP or later operating system).
2GB of memory.
Standard Ovation CD.
20.6 What are the licensing requirements for Ovation Virtual

Controllers?
Two licenses are required for Virtual Controllers.
Virtual Controller Host software license (includes required Dongle).
Virtual Controller software license.
REF_1005
269
E C T I O N
21
21 Planning security for your Ovation system
IN THIS SECTION
What is external security? ............................................................................................... 272
What is Ovation internal security?................................................................................... 272
Using the domain concept in security ............................................................................. 273
What are the best practices for establishing a secure system? ...................................... 274
What is antivirus software? ............................................................................................. 274
REF_1005
271
21.1 What is external security?
21.1 What is external security?

External security refers to the concept of protecting the Ovation system from any outside
influences that might disrupt the operation and functions of the Ovation system. These influences
might include the Internet, a company intranet and any external devices that are linked to a
system.
The following figure illustrates an Ovation system and the defense perimeter that is defined to
protect the system.
Figure 56: Defense perimeter for Ovation system
21.2 What is Ovation internal security?

Internal security protects an Ovation system from any inside influences that might disrupt the
operation and functions of the Ovation system. These influences might include unauthorized use
of Ovation functions, inability to manage security for a large complex system, and unprotected
workstations in remote sections of a plant.
272
REF_1005
21.3 Using the domain concept in security
21.3 Using the domain concept in security

Planning security for Ovation requires a thorough understanding of how security is administered
in a system based on the domain concept.
In a domain, all computers are logically connected and their security settings are controlled by a
computer that is configured to be the domain controller. All computers in the domain that are not
the domain controller are known as domain members.
Ovation provides you with an Ovation Security Manager application to help you more easily
understand your security requirements. This user-friendly software GUI is used to define and
manage the security for all the users and computers in a domain.
The person who will administer security for the Ovation system should be identified before the
system is installed.
Ovation system designers study the security needs for a system and implement the latest state-of
the-art security practices for each system. After the security plan is in place, plant administrators
can easily manage the day-to-day changes needed in a dynamic security system.
When planning security, keep in mind that the ability to perform certain operations in the Ovation
system is dictated by two factors:
The session in which the Ovation application runs. This is based on the Group policy
assigned to the user/computer.
A session consists of the logged-in user, the logged-in computer, and the applicable console
(that is, whether the user is locally logged-in at the computer or remotely logged-in through
the remote desktop service).
The Ovation roles to which the session belongs. This is based on the Ovation role policy
assigned to the user/computer.
Note: Refer to the applicable Managing Ovation Security for additional information.
REF_1005
273
21.4 What are the best practices for establishing a secure system?
21.4 What are the best practices for establishing a secure system?
Employ a standard firewall configuration for each Ovation system to prevent unwanted data
entering the control system from the outside world.
Formalize plans for loading applications and software on an Ovation system so that only
designated users (administrators) can install software on the system.
Assign roles so that functions can be performed throughout the Ovation system.
Assign more than one Administrator to ensure the continuation of security in case the original
Administrator is not available.
Define redundant domain controller(s) to ensure logins are dynamic and not based on a
cache of security data.
Use backup programs and procedures to ensure that in case of a system disruption, the
system data can be restored.
Use Virus detection software to help prevent system damage from the spread of software
viruses.
Use the security patches that Microsoft provides to ensure the security of your Windows
Operating System. These patches have been tested by Emerson for compatibility with the
Ovation software. Access these tested patches from the Emerson Users Group Web site and
then download the patches onto the computer. (See Ovation Software Installation Manual.)
If you plan to use remote and local console design in your Ovation system, make sure you
have adequate provisions for remote console security.
Create a plan that outlines in detail how security will be implemented.
21.5 What is antivirus softw are?

Using antivirus software to protect your Distributed Control System (DCS) is an important step
towards meeting the NERC CIP cyber security requirements, and protecting your plant's safety
and profitability. Emerson is confident that Kaspersky Lab's antivirus software provides the best
protection possible for your DCS. However, the Kaspersky software must be deployed on your
Ovation DCS correctly in order to maintain performance and reliability and not introduce any
operational risks to your plant.
Though Emerson designed the Ovation control system to be fully compliant with openarchitecture standards, running, installing, or configuring untested third-party applications on
Ovation drops can introduce security risks that have the potential to impact the robustness of your
plant's control system and ultimately the operation of your plant. Even adding standard Microsoft
tools that have not been fully tested and certified with the Ovation system can pose undue risk.
Unvalidated freeware and computer games are especially dangerous to the security of your
system.
Emerson recommends that only Ovation-validated applications that are absolutely necessary for
the operation of your plant or control system be installed on Ovation workstations.
If you are interested in installing an application that has not been validated with Ovation, contact
your Emerson representative before you install or execute software. Emerson has rigorous design
and testing standards in place to ensure system stability with many third-party packages, and the
open architecture of the Ovation network makes it easy to interface to a multitude of business
systems using standard communications protocols, without installing software on critical
components of your control system.
274
REF_1005
21.5 What is antivirus software?
21.5.1 Why is antivirus software important?

The types of attacks aimed at power generation plants are diverse and increasingly coming from
outside sources. External attacks, in the forms of viruses, worms, and other products of malicious
hackers are an increasing concern. Viruses or other external elements can cause damage to your
system in the form of:
A disruption in the balance of your operating parameters, which can lead to a plant shutdown.
A disruption to operation in a way that causes temporary plant shutdown and permanent
equipment damage.
A trip that interferes with proper shutdown procedures, potentially causing catastrophic
damage and endangering plant personnel.
A denial-of-service attack that locks up your DCS server, preventing your server from
performing legitimate operations for legitimate users.
An infection in your DCS servers by viruses or worms that can cause malicious activity such
as emailing critical information to unauthorized users.
Improving the security of your DCS is an important consideration for your plant safety and
profitability. In addition, improving your DCS security is now a necessary requirement to comply
with the NERC CIP standards, which detail the actions your plant must take to ensure its cyber
security.
Emerson also provides an Ovation Security Center (OCS). The OCS is a suite of hardware and
software tools (appliances) that provide electronic security management functions. The OSC
appliances are designed to enhance and manage the cyber security of Ovation Distributed
Control Systems (DCS) without disrupting the controlled process (see Ovation Security Center
User Guide for additional information about OCS).
21.5.2 What are the components of Kaspersky antivirus?

In order to protect your system from known viruses, you must properly install an antivirus software
program and its components on your system.
The following Kaspersky software components are needed to ensure antivirus protection for your
Ovation system:
Kaspersky Administration Kit 8.0.2090 -- The Administration Kit is loaded on the

Management Station. The Kit includes the software for the management station, clients
(workstations and servers), and Network Agent 8.0.2090 which handles the communication
between the management station and the clients.
Kaspersky 6.0 Anti-Virus for Workstations MP4 (6.0.4.1424) -- This software is loaded on
Ovation client workstation drops.
Kaspersky 6.0 Anti-Virus for Servers MP4 (6.0.4.1424) -- This software is loaded on
Ovation client server drops.
Note: The procedures discussed in this manual document how Kaspersky antivirus software is
installed and configured with the Ovation software. Additional information on Kaspersky
applications is provided in the Kaspersky Lab documentation which is provided on the
installation CD.
REF_1005
275
E C T I O N
22
22 Planning for an Ovation Process Historian (OPH)
IN THIS SECTION
What is the Ovation Process Historian? ......................................................................... 277
How many historians do you need? ................................................................................ 279
How many scanners do you need? ................................................................................. 279
How will you archive your data? ...................................................................................... 280
Who are your end users? ................................................................................................ 281
Do you need to migrate eDB or HSR data to your new historian? ................................. 282
Will you need any third-party software? .......................................................................... 282
22.1 What is the Ovation Process Historian?

The Ovation Process Historian collects process values and messages that are generated by your
Ovation control system. The historian stores these values and messages in an optimized
historical data store that runs on a Microsoft Windows platform. You can view and filter this
information, or output it to your printers, files, email, or Web pages. The historian can archive this
information to removable media.
You can use the historian to better understand the typical and abnormal behavior of your plant
processes, to identify common trends, explore abnormalities, and diagnose process flaws and
failures. The frequency and precision of historian monitoring are beneficial when accuracy is of
utmost importance.
The historian can:
Organize real-time process data.
Support online storage and offline archival.
Respond to retrieval requests.
Collect, process, and archive:

Process point values.
Process point attributes.
Alarm history data.
Operator events.
Sequence of events (SOE) data.
ASCII system messages.
User files.
REF_1005
277
22.1 What is the Ovation Process Historian?
Store process point data that does not originate directly from your DCS (lab history data).
Edit and annotate collected historical data.
Advantages of the historian:
You can archive data to removable media.
You can handle larger point counts due to additional storage and retrieval performance.
You can improve upgrade flexibility for future historian modifications.
You have a storage mechanism, scalable for high and low point counts, which enables
optimal retrieval.
You can use redundant historian servers, to ensure reliable historian performance.
Note: If you previously used the eDB or the HSR to collect historical information, you can utilize
Emerson's migration service to shift your collected data onto your new Ovation Process
Historian. Your migrated data is seamlessly merged with your collected data and is available on
trends, reviews, reports, and SQL queries the same as your collected data. Contact your
Emerson representative for details.
278
REF_1005
22.2 How many historians do you need?
22.2 How many historians do you need?

To determine how many historians are required, you must know how many points you want to
collect historical information for. The maximum number of points that one historian can collect is
200,000 points.
In addition to knowing the number of points you want to collect, you must know what type of
points you want to scan for, because different point types are treated differently by the historian
and some require more storage space than others. The number of points and the types of points
that you want to collect both affect your disk space. For example, you should decide if you want to
monitor any points at a 0.1 second scan rate and understand how that will impact your storage
and retrieval performance Emerson recommends that you aim for an overall storage rate of less
than 1-2 % change rate per second, especially if you have a larger point count.
After you have analyzed the various aspects of your historian plan, revisit the question of
how many historians you require. After the various elements of your historian plan are in place,
the number of historians that you need might become more clear.
Reasons to use multiple historians are:
If your system includes a remote area with a potentially unreliable network link to the rest of
your system, multiple historians can provide continued local operation at your remote facility
while offering central historical data storage for your entire system.
If you anticipate running out of licenses (for example, you might want to collect more than
200,000 points, or you might require more non-Ovation clients than one historian allows).
Reasons to use a single historian for multiple units are:
If you do not expect your total point count to exceed 200,000 points.
If your system is confined to one geographical area with reliable network connections.
If you require a low-cost solution to gather historical process data.
Note: If you think that you may eventually use a single historian for multiple units, Emerson
advises that you install your historian on your core network switches.
Reasons to use an embedded historian are (an embedded historian is a historian that you
add to a pre-existing database server workstation):
If you do not expect your total point count to exceed 5,000 points.
If you require the lowest cost solution to gather historical process data.
22.3 How many scanners do you need?

Given the number and type of points that you know you want to scan, decide whether you want to
scan with:
A single scanner.
Using a single scanner simplifies configuration, maintenance, and troubleshooting. Most
users require only one scanner.
Multiple scanners.
Multiple scanners can be useful if you want to scan at remote segments of your control
network. Multiple scanners can continue to collect and buffer remote data during an outage
between the local and remote network segments.
REF_1005
279
22.4 How will you archive your data?

When planning your scanners, consider the number of network vulnerabilities (such as routers
and switches) between your scanner and your historian. Use of multiple scanners on a single
system is a decision that you should make based not on your point count but rather on the quality
of your network connectivity. There are no specific recommendations, but generally, 20,000 points
per scanner ensures good performance quality.
After you have decided whether to use a single scanner or multiple scanners, decide if you want
scanner redundancy. Redundant scanners exist on two separate Ovation machines. They
communicate with one another to determine which of the two scanners is active, and which is
backup. Two scanners that are configured as redundant do not utilize the Ovation primary and
backup mechanism and are not affected by Ovation applications that initiate a failover. The status
of the redundant scanners is displayed as an item on the Maintenance and Status screen.
If you do decide that you want redundancy, the scanner redundancy manager must connect the
scanners, and the historian that they report to, in order to obtain redundant information.
Note: If you use multiple non-redundant historians, a single Ovation process point can be
collected by more than one scanner but it is only configured once for a given historian.
22.4 How will you archive your data?

The historian archive system provides storage and retrieval of the data collected by the historian
to and from removable media. It maintains a database of all data that is stored on removable
media. The removable storage device is a DVD-RAM drive, and is attached to the machine on
which the historian server software is installed.
Disk size estimates are based on the volume and type of information that you want to collect.
Because your disk space needs can change radically based on the volume and type of points that
you want to collect historical information for, the following estimates should be used as general
guidelines only.
The following table of disk space estimates is based on several assumptions:
Your hardware is a Dell PowerEdge 830, 840 or T300 with a standard configuration: three
146-gigabyte drives in RAID 5, approximately 262 gigabytes of usable disk space.
You collect samples at, on average, a 1% rate.
Your total disk space is approximately 200- 250 gigabytes.
Your DVDs can hold a maximum of approximately 8 gigabytes of data.

STORAGE ESTIMATES BASED
280
ON
POINT COUNT
Number of points that you want to collect...
10,000
25,000
50,000
75,000
100,000
Number of days before disk storage is full...
1654
663
332
221
166
Number of years before disk storage is full...
4.5
1.8
0.9
0.6
0.5
The addition of one, 300-Gb external RAID

adds this many additional days before full...
2268
910
455
304
227
The addition of one, 300-Gb external RAID

adds this many additional years before full...
6.2
2.5
1.2
0.8
0.6
Number of days for both sides of a DVD to

become full...
63
25
12
REF_1005
22.5 Who are your end users?

External RAIDs extend your online storage capability and let end users access data online,
without having to load a DVD or other removable media in order to view data. You can add up to
16 external RAIDs to your historian. You can use removable media in conjunction with external
RAIDs.
Removable media offers storage beyond standard online storage. However, archiving to
removable media requires human maintenance, and the removable media can be environmentsensitive (for example, excessive dust or soot can render DVDs unreadable). You might want to
use removable media if you require:
Historical data records for a longer amount of time than you keep them online.
The ability to store copies of your historical data offsite, for increased security.
If you decide that you do want removable media, you can use an internal or external DVD-RAM
drive. Historian archiving supports making backup copies of DVD-RAM volumes to DVD +/- RW
media.
22.5 Who are your end users?

The way that your end users want to view and use your historical data decides the applications
that you should use:
If you want to view your historical data in graphs, use historical trend.
If you want raw historical data, use historical review.
If you want data to analyze, use historical reports.
If you want to analyze your storage utilization, use history manager.
If you want to use data on a spreadsheet, use the Excel add-in or OLe Db.
Consider where your end user is geographically. Local end users present no difficulties (for
example, you can print reports to any network printer). End users that are geographically removed
require special network planning; you will need to address connectivity and firewall difficulties
between the historian system and your end user's system.
For example, if the user at workstation 200 wants to be able to demand historical reports,
workstation 200 must have the report manager software loaded and have connectivity to the
historian server workstation. Also, non-local users who query the historian server frequently, or for
large volumes of data, could greatly impact your network performance.
REF_1005
281
22.6 Do you need to migrate eDB or HSR data to your new historian?
22.6 Do you need to migrate eDB or HSR data to your new historian?
A migration service is available to help you migrate your data from the eDB or HSR to the
historian. You will be required to:
Choose which history types you want to convert.
Choose your start and end times.
If you need to migrate data, budget for work time and services to plan your data migration,
migration cost, and the downtime considerations of migration (downtime is a significant
consideration if you plan to use the same hardware for the historian that you used previously).
It is possible to migrate your custom report templates to the historian, but it can be difficult.
Therefore, Emerson recommends that you do not attempt to migrate your custom report
templates if they meet these criteria:
They are direct, cross tab reports (instead of ExpressCalc reports, which are easier to
migrate).
The reports contain large amounts of custom code.
In addition to migrating point data, it is also possible to migrate your existing point configuration
into your new historian. See your Emerson representative for details.
22.7 Will you need any third -party softw are?

The historian uses the Business Objects product, Crystal Reports, version XI to build report layout
files.
If you want to build report layout files outside of your control system, you must purchase
additional copies of Crystal Reports XI.
282
REF_1005
E C T I O N
23
23 Planning for first generation (gateway) Foundation

Fieldbus
IN THIS SECTION
Understanding Foundation Fieldbus interoperability ....................................................... 285
Understanding Foundation Fieldbus segmentation ........................................................ 286
What are the recommended installation practices for Foundation Fieldbus? ................. 291
Using Fieldbus in Ovation control ................................................................................... 292
Using PlantWeb Alerts for Fieldbus alarms .................................................................... 293
23.1 Foundation Fieldbus first and second generation solutions

There are two generations of Ovation-implemented Foundation Fieldbus. The method that your
application uses to interface to Foundation Fieldbus depends on whether you are using the first
generation solution (gateway) or the second generation solution (I/O module).
Note: Ovation 3.1 and later supports both generation solutions. If you are using the first
generation (gateway) Fieldbus solution, refer to Foundation Fieldbus User Guide for Ovation
3.0.
REF_1005
283
23.2 What is Foundation Fieldbus?

Foundation Fieldbus is an all-digital, two-way, multi-drop communication protocol that
interconnects intelligent devices such as actuators, sensors, discrete devices, and Controllers in
the field. At the lowest level in the hierarchy of plant networks, it is a Local Area Network (LAN) for
instruments that enables basic control and I/O to be moved from the Distributed Control System
(DCS) to the field devices.
The demand for Fieldbus technology is driven by the following benefits:
Better noise immunity through a digital mechanism.
Reduced wiring throughout the plant.
Ability to have multiple variables per device.
Ability to collect field-level diagnostics.
Possibility for redundancy.
Users want a technology that provides true device interoperability, enhanced field-level control
and reduced installation costs. Foundation Fieldbus meets these needs and much more. Fieldbus
offers reduced installation and material cost by replacing the traditional one-to-one wiring scheme
with a networking or multi-drop configuration. Conventional analog and discrete field instruments
use point-to-point wiring; that is, one wire pair per device. If your plant had 1000 field devices, that
would mean 1000 wire pairs. In addition, conventional instruments are limited to carrying only one
piece of information over those wires (usually a process variable or control output).
Foundation Fieldbus supports up to 16 devices on a single pair of wires called a segment. For
Ovation applications, however, considerations such as power, process modularity, and loop
execution speed make six to eight devices per segment a typical average. Based on the above
example of a plant with 1000 devices, you would only need to have 125 to 170 homerun wire
pairs in a Fieldbus application. A homerun is the wire that goes all the way from the equipment
room to the device. This wiring can be new or you can take advantage of your existing plant
wiring. Either way, this translates into a potential for significant savings in wiring and wiring
installation.
284
REF_1005
23.3 Understanding Foundation Fieldbus interoperability

Figure 57: Conventional wiring vs. Fieldbus wiring
Additionally, with Foundation Fieldbus, your field instruments become intelligent data transmitters.
For example, one temperature transmitter might communicate inputs from as many as eight
sensors still only using one wire pair. In addition, information flow can now be two-way. A valve
Controller can accept a control output from a host system or other source and send back the
actual valve position for more precise control.
Fieldbus allows for the reporting of self-diagnostics, calibration, and environmental conditions of
field instruments without disturbing the plant control. Foundation Fieldbus also offers the option of
executing some or all control algorithms in field devices rather than in a central host system (such
as Ovation).
Unlike proprietary network protocols, Foundation Fieldbus is neither owned by any individual
company nor regulated by a single nation. (The International Electric Commission, or IEC, is
considered the governing standards body.) The technology is supported by the Fieldbus
Foundation, a not-for-profit organization consisting of more than 150 of the worlds leading
controls and instrumentation suppliers and end users. The objective of the Fieldbus Foundation is
to develop a single, open, interoperable, international Fieldbus, giving users a wide range of
Fieldbus-compatible equipment from a large selection of vendors.
For more information about the Fieldbus Foundation, visit their Web site at
http://www.fieldbus.org.

The Fieldbus Foundation defines interoperability as the ability to operate multiple devices,
independent of manufacturer, in the same system, without loss of functionality.
Interoperability between field devices means that field devices from different manufacturers can
work together, sending and receiving information related to their specific function in the process.
The Fieldbus Foundation has established guidelines for interoperability between field devices on
a Fieldbus segment. These guidelines address such aspects as physical characteristics,
communication, and software functionality.
To be truly interoperable, devices must:
Be physically and electrically compatible with the Fieldbus segment (as defined by the ISA
50.02-2 Physical Layer Specification).
Include a communication stack that passes the Fieldbus Foundations Stack Conformance
Test.
Correctly implement the Function Block Application Process Model defined in the Foundation
Fieldbus specification. This means a devices function blocks must interconnect and
interoperate with the function blocks of other devices on the network.
Instruments can earn registered status (and the right to carry a Foundation Fieldbus check mark
logo) by passing rigorous tests to demonstrate they meet the requirements for interoperability.
The Foundation does not allow devices to bear the Foundation Fieldbus interoperability check
mark until at least two products of the same type, from different manufacturers, have passed its
tests.
REF_1005
285
23.4 Understanding Foundation Fieldbus segmentation
23.4 Understanding Foundation Fieldbus segmentation

With Foundation Fieldbus, you have a broad range of options for building a network that meets
your needs. The choices you make depend on the location of each device, the amount of existing
wiring you want to use in the new network, and the wiring practices that are best suited for your
plant or project.
Conventional analog installations have a dedicated pair of wires connecting each field device to a
host system. Foundation Fieldbus installations use a single twisted-pair cable, also called a bus or
a trunk, to connect to multiple devices. The cable, connected devices and supporting components
are called a segment, and it can be designed in various ways.
23.5 What is good Foundation Fieldbus segmentation design?

Designing a Fieldbus segment that is both reliable and easy to maintain depends to a large
degree on segmentation.
In conventional, non-Fieldbus point-to-point wiring, an individual pair of wires must be run
between every single field instrument and the I/O modules in the equipment room. These I/O
modules are either located near the Ovation Controller or in a remote I/O cabinet. Usually this is
done by running multi-pair cables to various junction boxes located throughout the plant. Then
individual cables are run from each junction box to field instruments located in its vicinity.
Compared to Ovations conventional wiring, the major topological change introduced by Ovations
Foundation Fieldbus solution is that Fieldbus segments replace the multi-pair cables it is not
necessary to change the wiring from the Ovation Controller to the junction boxes. But once the
segments are brought to a junction box, a different type of distribution must be implemented,
either by using a bussed terminal strip or a multi-port junction, known as a brick or passive field
hub. Then, just like conventional wiring, individual cables are run to each field instrument. These
individual wire pairs are called spurs and the bussed segment wire running from equipment room
to junction boxes is called a trunk.
Figure 58: Trunk and spurs
286
REF_1005

There is no rule that requires only one segment trunk be run to a particular junction box;
sometimes it may be necessary to pass a segment through multiple junction boxes.
Wiring is most economical when you can minimize the number of segments that run through a
junction box and put as many devices as possible onto each segment (within design
recommendations). However, there are other considerations beyond economical wiring that you
should factor into the design of your Fieldbus segment.
23.5.1 Planning the Foundation Fieldbus topology

The topology Emerson recommends for Ovation Foundation Fieldbus segments is designed to
provide the greatest degree of flexibility of segment design, ongoing design changes, and future
incremental retrofits. The design tools already exist for wiring conventional I/O, and the
conventional approach is compatible with Ovation Foundation Fieldbus segment design.
First, Emerson recommend that the placement and location of field junction boxes and the
individual wiring from field instruments to the junction boxes be planned in the conventional way
as shown in the following figure:
Figure 59: Conventional layout
REF_1005
287

Then, Emerson recommends that running three or more Fieldbus segments through a chain of
junction boxes so that each box has multiple segments to choose from and each segment can
traverse a significant area of the plant. See the following figure:
Figure 60: Fieldbus segments through junction boxes
288
REF_1005

With this layout in place, design work specific to Ovation Foundation Fieldbus is reduced to
assigning instruments already brought to a junction box to specific segments in the junction box,
or creating the spurs:
Figure 61: Segment assignments

With this design, it is relatively easy to put redundant transmitters onto separate segments even if
they are in physical proximity to one another and are routed to the same junction box. It is easy to
assign fast loops onto fast segments and slow loops onto slow segments. Then, even if
instruments in the same control loop are separated by some physical distance, there is a greater
probability of being able to assign them to the same segment. By assigning same loop
instruments to same segments, the segment designer still has the ability to implement control-infield if desired.
It is important to understand what devices should be Fieldbus and how to segment these devices
before assigning them to specific segments. The following sections attempt to clarify how to
partition for Ovation Foundation Fieldbus.
REF_1005
289
23.5.2 What should be Foundation Fieldbus I/O?

You should decide which instruments and applications should not be implemented with Ovation
Foundation Fieldbus. A modern plant implementation will have a mix of conventional local and
remote I/O, Foundation Fieldbus I/O and I/O that is implemented on other buses.
Refer to the applicable Ovation Foundation Fieldbus User Guide for information about using
Temperature measurements
Temperature measurements that employ thermocouples or RTDs are usually a slow process
variable. Typically, it is most economical for Ovation local or remote I/O to acquire these
measurements wherever there are many measurements to be made.
The exceptions that favor the use of Fieldbus include wherever there are very few measurements
in a specific area or wherever a multi-variable Fieldbus device can conveniently provide the
measurement. For example, a pressure transmitter or valve with embedded temperature
measurement could use Fieldbus.
Pressure, level and flow
Pressure, level, and flow measurements typically require a pressure transmitter and is best done
with Fieldbus. Also, intelligent transmitters can provide useful diagnostic data in pressure
measurement applications.
Modulating valves
For modulating valves, if the required control loop response is 0.5 second or slower, use
If the required response is faster than 0.5 second, Emerson recommends that you use Ovation
local or remote I/O.
Discrete I/O
Applications that require fast sensing and reaction should use Ovation local or remote I/O. If the
number of I/O points is densely located, it is economical to connect to these points using Ovation
remote I/O.
In instances where the discrete point is embedded in an intelligent instrument or there are only a
few discrete points located near a Fieldbus segment, use Foundation Fieldbus.
Motor control centers and variable frequency drives
You can purchase equipment with bussed communications built in. For motor control centers and
variable frequency drives, use whichever Ovation bus interface is required for communicating to
the equipment DeviceNet, Profibus DP, or Modbus TCP.
290
REF_1005
23.6 What are the recommended installation practices for Foundation Fieldbus?
Non-Foundation Fieldbus instruments
Though you have an option to either use an analog-to-Fieldbus converter or connect non-Fieldbus
instruments directly to Ovation local or remote I/O, Emerson recommends that you design a
system with the knowledge that Fieldbus versions may be offered in the future. This means that
you should either use an analog-to-Fieldbus converter now and eliminate it later, or design the
wiring so it is more easily retrofitted to Fieldbus in the future.
23.5.3 Partitioning instruments and applications

After you decide which devices will use Ovation Foundation Fieldbus, determine how to most
effectively and economically group them on a segment. Use the following criteria to help you
determine the best segmentation schemes:
Relatedness of the Loop - As much as possible, group common processes together. This
consideration is paramount when grouping your devices.
Importance of the Loop - Avoid mixing critically important loops and devices onto the same
segment. It is fine to mix a critical device with less critical loops and devices.
Speed of Response - Avoid mixing loops with different response times on the same
segment. Keep fast-function blocks grouped with fast-function blocks and slow-function
blocks grouped with slow-function blocks.
Proximity of the Devices - After the first three criteria are met, segment devices and loops
that are close to each other on the same segment to save wiring costs.
Good segment design ensures optimized cost savings, and also lowers the complexity of
maintenance and installation. To a large extent, the ease of your experience with Fieldbus
technology depends on the insight of your segmentation design.
23.6 What are the recommended installation practices for Foundation

Fieldbus?
Fieldbus installation differs from a standard installation. Consider the following recommended
practices:
Optimize your wiring. To reduce cost and labor, wire the segment to field junction boxes
closer to your field devices. Then, connect the devices using either of the following methods:
Continue running individual wire pairs (using conduit) from the trunk to the individual
devices using terminal blocks.
Run quick-connect, pre-molded cables from the junction box to the individual devices.
Quick-connect, pre-molded cables cost more than twisted pair, but they install faster,
produce fewer wiring errors, and provide some short circuit protection.
When you connect your devices, take time to investigate the features of the terminal blocks
and make them part of your installation plan. They alleviate concerns like identifying trunk
cabling, having extra spurs for future devices, providing segment terminators, and having
built-in short circuit protection.
REF_1005
291
23.7 Using Fieldbus in Ovation control
Select time-saving devices. Devices with quick-disconnect wire connectors are faster and
easier to connect and can reduce wiring errors. Although quick-connect, pre-molded cables
cost more than twisted pair, they install faster and produce fewer wiring errors, which can
justify the added cost.
Observe device polarity. Because most Fieldbus devices are polarity sensitive, inverting the
positive and the negative anywhere on a segment may cause individual devices or parts of
the segment to malfunction. Although this does not happen with polarity-insensitive devices,
observing the polarity of all devices reduces electrical installation problems.
All Fieldbus devices from Emerson are polarity insensitive. They function regardless of the
polarity of the wiring. This reduces design and installation time, commissioning, and
troubleshooting by eliminating polarity considerations.
Anticipate device and segment changes. Define standard methods of attaching and
removing individual devices, without shorting out the segment. Standard wiring practices can
also help technicians avoid mistakes in connecting (or disconnecting) devices and cables.
When using terminal blocks, add spare spurs to use as connector ports for future devices.
Check voltage requirements. Fieldbus devices require between 9 and 32 volts for operation.
Heavily loaded segments with long runs can result in low voltage at devices. From a design
standpoint, make sure the voltage at the farthest point of the segments is no lower than 11
VDC to accommodate a possible temporary drop when a new device is added.
Document everything. To ensure consistent installation and streamline future maintenance,

immediately update your standards and project records to reflect any changes made during
engineering and installation. Instrumentation Data Sheets enhanced with bus requirements
can provide useful documentation. Also, Emerson recommends that multiple drawings be
replaced with a single drawing of each segment. Avoid adding information to the P&ID except
as necessary for logic or control purposes.
23.7 Using Fieldbus in Ovation control

Foundation Fieldbus allows you to execute control algorithms in the Controller, in the devices, or
both. However, the key is making a choice that best supports your plants needs.
The supported Ovation Fieldbus algorithms shadow the following Fieldbus function blocks: FFAI,
FFAO, FFDI, FFDO, FFPID, and FFMAI.
The Ovation Controller can handle Fieldbus function block to Fieldbus function block or Ovation
algorithm to Fieldbus function block control schemes. For example:
Scenario 1
FFAI
292
FFPID
FFAO
REF_1005
23.8 Using PlantWeb Alerts for Fieldbus alarms
Scenario 2
FFAI
Ov ation
PID
FFAO
23.8 Using PlantWeb Alerts for Fieldbus alarms

The Ovation alarm system can process alarms generated by Foundation Fieldbus devices. These
alarms are identified as PlantWeb Alerts which are separate and distinct from process alarms:
Advisory Alarm Indicates conditions that have no current impact of the devices ability to
sense and control, but may impact operation if some action does not occur to handle the
condition.
Maintenance Alarm Indicates that the device needs maintenance soon and is in danger of
losing its ability to sense and control.
Failed Alarm Indicates that the device needs maintenance now and that the device has lost
its ability to sense and control.
Communication Alarm Ovation is unable to communicate with the device.
REF_1005
293
E C T I O N
24
24 Planning for second generation (I/O module)

Foundation Fieldbus
IN THIS SECTION
Understanding Foundation Fieldbus interoperability ....................................................... 297
What are the Foundation Fieldbus and Ovation components? ....................................... 298
What are the supported Fieldbus algorithms? ................................................................ 306
24.1 Foundation Fieldbus first and second generation solutions

There are two generations of Ovation-implemented Foundation Fieldbus. The method that your
application uses to interface to Foundation Fieldbus depends on whether you are using the first
generation solution (gateway) or the second generation solution (I/O module).
Note: Ovation 3.1 and later supports both generation solutions. If you are using the first
generation (gateway) Fieldbus solution, refer to Foundation Fieldbus User Guide for Ovation
3.0.
REF_1005
295

Foundation Fieldbus is an all-digital, two-way, multi-drop communication protocol that
interconnects intelligent devices such as actuators, sensors, discrete devices, and Controllers in
the field. At the lowest level in the hierarchy of plant networks, it is a Local Area Network (LAN) for
instruments that enables basic control and I/O to be moved from the Distributed Control System
(DCS) to the field devices.
The demand for Fieldbus technology is driven by the following benefits:
Better noise immunity through a digital mechanism.
Reduced wiring throughout the plant.
Ability to have multiple variables per device.
Ability to collect field-level diagnostics.
Possibility for redundancy.
Users want a technology that provides true device interoperability, enhanced field-level control
and reduced installation costs. Foundation Fieldbus meets these needs and much more. Fieldbus
offers reduced installation and material cost by replacing the traditional one-to-one wiring scheme
with a networking or multi-drop configuration. Conventional analog and discrete field instruments
use point-to-point wiring; that is, one wire pair per device. If your plant had 1000 field devices, that
would mean 1000 wire pairs. In addition, conventional instruments are limited to carrying only one
piece of information over those wires (usually a process variable or control output).
Foundation Fieldbus supports up to 16 devices on a single pair of wires called a segment. For
Ovation applications, however, considerations such as power, process modularity, and loop
execution speed make six to eight devices per segment a typical average. Based on the above
example of a plant with 1000 devices, you would only need to have 125 to 170 homerun wire
pairs in a Fieldbus application. A homerun is the wire that goes all the way from the equipment
room to the device. This wiring can be new or you can take advantage of your existing plant
wiring. Either way, this translates into a potential for significant savings in wiring and wiring
installation.
296
REF_1005

Figure 62: Conventional wiring vs. Fieldbus wiring
Additionally, with Foundation Fieldbus, your field instruments become intelligent data transmitters.
For example, one temperature transmitter might communicate inputs from as many as eight
sensors still only using one wire pair. In addition, information flow can now be two-way. A valve
Controller can accept a control output from a host system or other source and send back the
actual valve position for more precise control.
Fieldbus allows for the reporting of self-diagnostics, calibration, and environmental conditions of
field instruments without disturbing the plant control. Foundation Fieldbus also offers the option of
executing some or all control algorithms in field devices rather than in a central host system (such
as Ovation).
Unlike proprietary network protocols, Foundation Fieldbus is neither owned by any individual
company nor regulated by a single nation. (The International Electric Commission, or IEC, is
considered the governing standards body.) The technology is supported by the Fieldbus
Foundation, a not-for-profit organization consisting of more than 150 of the worlds leading
controls and instrumentation suppliers and end users. The objective of the Fieldbus Foundation is
to develop a single, open, interoperable, international Fieldbus, giving users a wide range of
Fieldbus-compatible equipment from a large selection of vendors.
For more information about the Fieldbus Foundation, visit their Web site at
http://www.fieldbus.org.

The Fieldbus Foundation defines interoperability as the ability to operate multiple devices,
independent of manufacturer, in the same system, without loss of functionality.
The Fieldbus Foundation has established guidelines for interoperability between field devices on
a Fieldbus segment. These guidelines address such aspects as physical characteristics,
To be truly interoperable, devices must:
Be physically and electrically compatible with the Fieldbus segment (as defined by the ISA
50.02-2 Physical Layer Specification).
Include a communication stack that passes the Fieldbus Foundations Stack Conformance
Test.
Correctly implement the Function Block Application Process Model defined in the Foundation
Fieldbus specification. This means a devices function blocks must interconnect and
interoperate with the function blocks of other devices on the network.
Instruments can earn registered status (and the right to carry a Foundation Fieldbus check mark
logo) by passing rigorous tests to demonstrate they meet the requirements for interoperability.
The Foundation does not allow devices to bear the Foundation Fieldbus interoperability check
mark until at least two products of the same type, from different manufacturers, have passed its
tests.
REF_1005
297
24.4 What are the Foundation Fieldbus and Ovation components?

The second generation Ovation implementation of Foundation Fieldbus uses native (integral to
Ovation) I/O modules and interfaces to these modules through the Ovation I/O bus. As the
drawing illustrates, the second generation Ovation solution streamlines the amount of hardware
that you need by eliminating the Ethernet network switches and gateways that are used with the
first generation solution.
Figure 63: Architecture overview
298
REF_1005

The features of the second generation implementation include:
Up to 18 pluggable bus modules (also called H1 cards). Each bus module supports two
Fieldbus segments. The bus modules include an I/O terminal block that provides compression
terminations for connecting Fieldbus segments. The I/O terminations connect to the screw
modules on the base.
Power supplies and conditioners for bus power must be supplied externally.
Each Foundation Fieldbus interface module contains two independent Fieldbus channels.
Each channel provides galvanic isolation between the Fieldbus field power conditioner and
the main 24VDC power supply. Each Fieldbus channel uses a microcontroller to control the
Fieldbus data communications.
Foundation Fieldbus interface modules use a Foundation Fieldbus approved H1 host

controller stack in compliance with IEC standard 61158.
Unlike conventional analog installations that have a dedicated pair of wires connecting each field
device to a host system, Foundation Fieldbus segments use a single twisted-pair cable (also
called a bus or a trunk) to connect to multiple devices. The segment is the cable, connected
devices, and supporting components. Typical installations require multiple segments to connect
the devices. The segment can be designed as either a branch or tree layout topology.
On each segment are various Fieldbus devices. Fieldbus devices are intelligent field instruments,
such as transmitters and valves, with processors that monitor device performance and state.
Each segment supports up to 16 Fieldbus devices. However, Emerson typically recommends no
more than 10 to 12 devices per segment.
Field devices are configured and engineered using tools integrated into the Ovation Developer
Studio.
In addition to the Fieldbus and Ovation components mentioned above, you must use the AMS
Device Manager software package. AMS Device Manager analyzes information received through
the control system from intelligent Fieldbus devices to provide operators and maintenance
personnel with the detailed information necessary to calibrate, configure, and diagnose plant
equipment more efficiently. For more information on AMS Device Manager, refer to AMS Device
Manager Books Online.
REF_1005
299

Designing a Fieldbus segment that is both reliable and easy to maintain depends to a large
degree on segmentation.
In conventional, non-Fieldbus point-to-point wiring, an individual pair of wires must be run
between every single field instrument and the I/O modules in the equipment room. These I/O
modules are either located near the Ovation Controller or in a remote I/O cabinet. Usually this is
done by running multi-pair cables to various junction boxes located throughout the plant. Then
individual cables are run from each junction box to field instruments located in its vicinity.
Compared to Ovations conventional wiring, the major topological change introduced by Ovations
Foundation Fieldbus solution is that Fieldbus segments replace the multi-pair cables it is not
necessary to change the wiring from the Ovation Controller to the junction boxes. But once the
segments are brought to a junction box, a different type of distribution must be implemented,
either by using a bussed terminal strip or a multi-port junction, known as a brick or passive field
hub. Then, just like conventional wiring, individual cables are run to each field instrument. These
individual wire pairs are called spurs and the bussed segment wire running from equipment room
to junction boxes is called a trunk.
Figure 64: Trunk and spurs

There is no rule that requires only one segment trunk be run to a particular junction box;
sometimes it may be necessary to pass a segment through multiple junction boxes.
Wiring is most economical when you can minimize the number of segments that run through a
junction box and put as many devices as possible onto each segment (within design
recommendations). However, there are other considerations beyond economical wiring that you
should factor into the design of your Fieldbus segment.
300
REF_1005
24.5.1 Planning the Foundation Fieldbus topology

The topology Emerson recommends for Ovation Foundation Fieldbus segments is designed to
provide the greatest degree of flexibility of segment design, ongoing design changes, and future
incremental retrofits. The design tools already exist for wiring conventional I/O, and the
conventional approach is compatible with Ovation Foundation Fieldbus segment design.
First, Emerson recommend that the placement and location of field junction boxes and the
individual wiring from field instruments to the junction boxes be planned in the conventional way
as shown in the following figure:
Figure 65: Conventional layout
REF_1005
301

Then, Emerson recommends that running three or more Fieldbus segments through a chain of
junction boxes so that each box has multiple segments to choose from and each segment can
traverse a significant area of the plant. See the following figure:
Figure 66: Fieldbus segments through junction boxes
302
REF_1005

With this layout in place, design work specific to Ovation Foundation Fieldbus is reduced to
assigning instruments already brought to a junction box to specific segments in the junction box,
or creating the spurs:
Figure 67: Segment assignments

With this design, it is relatively easy to put redundant transmitters onto separate segments even if
they are in physical proximity to one another and are routed to the same junction box. It is easy to
assign fast loops onto fast segments and slow loops onto slow segments. Then, even if
instruments in the same control loop are separated by some physical distance, there is a greater
probability of being able to assign them to the same segment. By assigning same loop
instruments to same segments, the segment designer still has the ability to implement control-infield if desired.
It is important to understand what devices should be Fieldbus and how to segment these devices
before assigning them to specific segments. The following sections attempt to clarify how to
partition for Ovation Foundation Fieldbus.
REF_1005
303
24.5.2 What should be Foundation Fieldbus I/O?

You should decide which instruments and applications should not be implemented with Ovation
Foundation Fieldbus. A modern plant implementation will have a mix of conventional local and
remote I/O, Foundation Fieldbus I/O and I/O that is implemented on other buses.
Refer to the applicable Ovation Foundation Fieldbus User Guide for information about using
Temperature measurements
Temperature measurements that employ thermocouples or RTDs are usually a slow process
variable. Typically, it is most economical for Ovation local or remote I/O to acquire these
measurements wherever there are many measurements to be made.
The exceptions that favor the use of Fieldbus include wherever there are very few measurements
in a specific area or wherever a multi-variable Fieldbus device can conveniently provide the
measurement. For example, a pressure transmitter or valve with embedded temperature
measurement could use Fieldbus.
Pressure, level and flow
Pressure, level, and flow measurements typically require a pressure transmitter and is best done
with Fieldbus. Also, intelligent transmitters can provide useful diagnostic data in pressure
measurement applications.
Modulating valves
For modulating valves, if the required control loop response is 0.5 second or slower, use
If the required response is faster than 0.5 second, Emerson recommends that you use Ovation
local or remote I/O.
Discrete I/O
Applications that require fast sensing and reaction should use Ovation local or remote I/O. If the
number of I/O points is densely located, it is economical to connect to these points using Ovation
remote I/O.
In instances where the discrete point is embedded in an intelligent instrument or there are only a
few discrete points located near a Fieldbus segment, use Foundation Fieldbus.
Motor control centers and variable frequency drives
You can purchase equipment with bussed communications built in. For motor control centers and
variable frequency drives, use whichever Ovation bus interface is required for communicating to
the equipment DeviceNet, Profibus DP, or Modbus TCP.
304
REF_1005

Non-Foundation Fieldbus instruments
Though you have an option to either use an analog-to-Fieldbus converter or connect non-Fieldbus
instruments directly to Ovation local or remote I/O, Emerson recommends that you design a
system with the knowledge that Fieldbus versions may be offered in the future. This means that
you should either use an analog-to-Fieldbus converter now and eliminate it later, or design the
wiring so it is more easily retrofitted to Fieldbus in the future.
24.5.3 Partitioning instruments and applications

After you decide which devices will use Ovation Foundation Fieldbus, determine how to most
effectively and economically group them on a segment. Use the following criteria to help you
determine the best segmentation schemes:
Relatedness of the Loop - As much as possible, group common processes together. This
consideration is paramount when grouping your devices.
Importance of the Loop - Avoid mixing critically important loops and devices onto the same
segment. It is fine to mix a critical device with less critical loops and devices.
Speed of Response - Avoid mixing loops with different response times on the same
segment. Keep fast-function blocks grouped with fast-function blocks and slow-function
blocks grouped with slow-function blocks.
Proximity of the Devices - After the first three criteria are met, segment devices and loops
that are close to each other on the same segment to save wiring costs.
Good segment design ensures optimized cost savings, and also lowers the complexity of
maintenance and installation. To a large extent, the ease of your experience with Fieldbus
technology depends on the insight of your segmentation design.
24.5.4 What are the recommended installation practices for Foundation Fieldbus?
Fieldbus installation differs from a standard installation. Consider the following recommended
practices:
Optimize your wiring. To reduce cost and labor, wire the segment to field junction boxes
closer to your field devices. Then, connect the devices using either of the following methods:
Continue running individual wire pairs (using conduit) from the trunk to the individual
devices using terminal blocks.
Run quick-connect, pre-molded cables from the junction box to the individual devices.
Quick-connect, pre-molded cables cost more than twisted pair, but they install faster,
produce fewer wiring errors, and provide some short circuit protection.
When you connect your devices, take time to investigate the features of the terminal blocks
and make them part of your installation plan. They alleviate concerns like identifying trunk
cabling, having extra spurs for future devices, providing segment terminators, and having
built-in short circuit protection.
REF_1005
305
24.6 What are the supported Fieldbus algorithms?
Select time-saving devices. Devices with quick-disconnect wire connectors are faster and
easier to connect and can reduce wiring errors. Although quick-connect, pre-molded cables
cost more than twisted pair, they install faster and produce fewer wiring errors, which can
justify the added cost.
Observe device polarity. Because most Fieldbus devices are polarity sensitive, inverting the
positive and the negative anywhere on a segment may cause individual devices or parts of
the segment to malfunction. Although this does not happen with polarity-insensitive devices,
observing the polarity of all devices reduces electrical installation problems.
All Fieldbus devices from Emerson are polarity insensitive. They function regardless of the
polarity of the wiring. This reduces design and installation time, commissioning, and
troubleshooting by eliminating polarity considerations.
Anticipate device and segment changes. Define standard methods of attaching and
removing individual devices, without shorting out the segment. Standard wiring practices can
also help technicians avoid mistakes in connecting (or disconnecting) devices and cables.
When using terminal blocks, add spare spurs to use as connector ports for future devices.
Check voltage requirements. Fieldbus devices require between 9 and 32 volts for operation.
Heavily loaded segments with long runs can result in low voltage at devices. From a design
standpoint, make sure the voltage at the farthest point of the segments is no lower than 11
VDC to accommodate a possible temporary drop when a new device is added.
Document everything. To ensure consistent installation and streamline future maintenance,

immediately update your standards and project records to reflect any changes made during
engineering and installation. Instrumentation Data Sheets enhanced with bus requirements
can provide useful documentation. Also, Emerson recommends that multiple drawings be
replaced with a single drawing of each segment. Avoid adding information to the P&ID except
as necessary for logic or control purposes.
24.6 What are the supported Fieldbus algorithms?

The supported Ovation Fieldbus algorithms shadow the following Fieldbus function blocks: FFAI,
FFAO, FFDI, FFDO, FFPID, and FFMAI.
The Ovation Controller can handle Fieldbus function block to Fieldbus function block or Ovation
algorithm to Fieldbus function block control schemes. For example:
Scenario 1
FFAI
FFPID
FFAO
Ov ation
PID
FFAO
Scenario 2
FFAI
306
REF_1005
E C T I O N
25
25 Planning for Profibus
IN THIS SECTION
What is an overview of Profibus? .................................................................................... 308
What is device interoperability? ...................................................................................... 309
What are the Profibus and Ovation components? .......................................................... 310
What are Profibus devices? ............................................................................................ 311
What is Profibus redundancy? ........................................................................................ 313
What are Profibus hardware and software requirements? ............................................. 315
REF_1005
307
25.1 What is an overview of Profibus?
25.1 What is an overview of Profibus?

Profibus (Process Field Bus) DP (decentralized periphery) is an all-digital, two-way
communication system that links devices (also known as slaves) and automation systems. A
decentralized periphery uses a network bus (in this instance, Profibus) between the Controller
(Ovation) and its connected I/O channels. Therefore, the I/O is decentralized as compared to a
programmable logic controller (PLC) that has its I/O arranged centrally. At the base level in the
hierarchy of plant networks, Profibus serves as a Local Area Network (LAN) for instruments.
Profibus DP offers reduced installation and material cost by replacing the traditional one-to-one
wiring scheme with a networking or multi-drop configuration. Conventional analog and discrete
field instruments use point-to-point wiring (one wire pair per device). For example, if your plant
has 1000 field devices, you would need 1000 wire pairs. In addition, conventional instruments are
limited to carrying only one piece of information over a wire pair (usually a process variable or
control output).
Profibus DP technology does not have these limitations. Ovation Profibus DP supports up to 32
devices on a single wire pair. For all process applications including Ovation, considerations such
as power, process modularity, and data update rate must be considered. For example, a single
Profibus network with the maximum number of slave devices on a single pair of wires might
provide a quantity of I/O that exceeds the automation systems capability. Therefore, process
segmentation is a recommended practice.
Profibus DP is one of a family of protocols that was developed in Germany by a group of many
companies and universities. The technology is controlled by the Profibus User Organization,
consisting of approximately 1,000 member companies in 23 regional user organizations united
under the umbrella organization, Profibus International. The objective of Profibus International is
to develop a single, open, interoperable, international fieldbus. This objective gives users the
option of choosing from a wide range of fieldbus-compatible equipment from a large selection of
vendors.
The Ovation implementation of Profibus DP uses hardware and software components to integrate
Profibus devices with Ovation technology through a Profibus I/O module that resides in a
Controller cabinet. The module operates as a DP-V2 Profibus master and is designed around the
Hilscher EC-1 chip (each EC-1 chip runs its own segment. Each Profibus I/O module supports
communication with two segments per module and up to 32 field devices. The DP-V2 master
allows for redundant modules so that Ovation can support redundant Profibus masters on two
different Profibus segments. This solution eliminates the need for an Ethernet switch and a
gateway module as in previous Ovation releases. The Emerson Profibus interface scans I/O at a
fixed 1 second scan rate.
For more information on Profibus, visit the Profibus User Organization Web site at
http://www.profibus.com.
Note: Refer to the individual Profibus device vendor manuals and Profibus standards
documents for specific details of device and network capabilities.
Refer to the Ovation Profibus User Guide for information about using Profibus with Ovation.
308
REF_1005
25.2 What is device interoperability?
25.2 What is device interoperability?

The Profibus User Organization establishes guidelines for interoperability between field devices
on a Profibus segment. These guidelines address such aspects as physical characteristics,
Manufacturers can apply for a Profibus-approved certificate from the Profibus Trade Organization.
Interoperability for a device is guaranteed after the device has successfully passed all of the tests.
Devices can be certified as either slaves or masters and can use various protocols with the
Profibus standard.
A number of Profibus variants exist including DP-V0, DP-V1, and DP-V2. All devices support, at a
minimum, DP-V0, which provides the guaranteed cyclic transmission of device data. DP-V1 is
also supported for a configuration master where a second connection to Profibus can be used for
configuration software support.
Profibus PA is supported by means of its connection capability to DP-V0. However, the capability
is handled by Ovation through PlantWeb capabilities of Foundation Fieldbus. The Profibus family
of protocols is extensive as is the knowledge needed to understand them. The level of knowledge
for Profibus PA is outside the scope of this manual.
REF_1005
309
25.3 What are the Profibus and Ovation components?
25.3 What are the Profibus and Ovation components?

Unlike conventional analog installations that have a dedicated pair of wires connecting each field
device to a host system, Profibus DP installations use a single twisted-pair cable (also called a
bus or a trunk) to connect to multiple devices. The cable, connected devices, and supporting
components are called a segment. The segment can be designed as either a branch or tree
layout topology. The following figure depicts a typical implementation of Profibus with an Ovation
system.
Figure 68: Implementation of Profibus with Ovation
310
REF_1005
25.4 What are Profibus devices?

In computer networking, master/slave is a communication model where one device or process
(known as the master) controls one or more other devices or processes (known as slaves). The
master makes a service request and the slave fulfills the request. The master/slave model
provides a convenient way to interconnect programs that are distributed efficiently across different
locations.
After the master/slave relationship is established, the direction of local control commands is
always from the master to the slave(s). In the Ovation-Profibus implementation, the Profibus I/O
module is the master and the Profibus devices are the slaves. There are various slave devices
on each segment that collect input information and send output information to the master. The
slave devices are linked to the Ovation Controllers through a Profibus I/O module.
The Profibus I/O module resides in the Controller cabinet. An I/O data agent within the Controller
works with the server to exchange information and diagnostics between the Profibus I/O module
and the Operator Station. The I/O data agent scans I/O at a fixed 1 second rate. The Operator
Station, Controller, and I/O module each run a version of the server in order to facilitate
configuration and diagnostics of Profibus slave devices.

Profibus devices are field instruments that can range from simple I/O devices such as push
buttons and lights to sophisticated devices like motor starters. These slave devices collect input
information and send output information to the master. Profibus devices use a digital, rather than
analog, connection to the Ovation system. Profibus devices notify the control system of standard
operating parameters, are self-diagnosing, and are capable of reporting device problems to the
control system.
Each Profibus device must have a unique physical device tag and a corresponding network
address. The network address is the current address that Profibus is using for the device.
Each Profibus device has its own configuration file known as the GSD file. This file is provided by
the device vendor, contains the system characteristics of the device, and is stored in the Ovation
database.
There are three types of Profibus DP devices:
Master Class 1 (DPM1) [Address 1] DP-V0

Master Class 1 devices perform cyclical user data and provide application data. Class 1
Masters can configure device parameters via the GSD file.
Master Class 2 (DPM2) DP-V1

Master Class 2 devices communicate with the Class 1 devices and all of the slaves. Class 2
Masters read all diagnostic information from the slaves devices.
Slave [Address 2-125] DP-V0 and/or DP-V1

Slaves are peripheral devices (for example VSDs, I/O, motor starters, and so forth) that can
import and export data.
REF_1005
311

Profibus supports both mono-master and multi-master systems. In a mono-master system, there
is only one master device active on the bus. Class 1 Master devices are normally PLCs that
cyclically exchange data with the connected slave devices and act as a main controller for
handling exchange of I/O information. This setup has the shortest bus cycle times. Because
Profibus uses a cyclical polling setup between masters and slaves, the behavior is deterministic,
meaning that the behavior of a Profibus system can be predicted over time.
In a multi-master system, there are several master devices on a single bus. Each of the masters
can read the input and output messages of each slave. Only one master (DP-V0) has write
access to the outputs. A Class 1 master automatically detects the presence of a new segment
connected to a Class 2 master. When the Class 1 master completes its polling cycle, it passes a
"token" to the Class 2 master to grant temporary access to the bus. Each master can only poll the
connected slave devices when it possesses the token.
A slave can only have a single master, so a multi-master system can be two DPM1 masters each
talking to a separate set of Profibus slaves. In effect, you can have two completely separate
Profibus segments sharing common wiring communications. DPM1 and DPM2 masters can be on
the same segment but only the DPM1 master has write access to the slaves. The DPM2 master
can read all diagnostic information from the slave devices only.
312
REF_1005
25.5 What is Profibus redundancy?
25.5 What is Profibus redundanc y?

Profibus redundancy is available for Ovation 3.1.1 and later releases.
Emerson has developed technology to give you the option of using redundant Ovation Profibus
modules, to protect your Profibus system in the event that a module or segment (EC-1 chip) fails.
Failovers between the redundant modules can occur for any of the following reasons:
No communication to all devices on either segment of a module.
No communication/faulty communication between the module and the Controller.
Additional module faults (such as internal hardware or software faults associated with a
module).
Redundant Profibus modules are connected to the Ovation Controllers, and each other, via the
Ovation bus. There can only be one master at a time on the Profibus network (some Profibus
implementations allow more than one master - this is not supported in the Ovation Profibus
network). The module acting as the Profibus master is referred to as being in control. The module
operating as a slave on the Profibus network is considered to be in backup. The module in control
actively exchanges I/O between the Ovation Controller and the Profibus devices. The backup
module does not exchange any I/O and passively waits to take control. Before a backup module
goes into control, it is updated with all Profibus outputs assigned to devices on its Profibus
segments.
The Ovation Controller evaluates the health of each Profibus module and segment. Initially, the
Ovation Controller attempts to make the primary module take control. In the case of a failure on
the control module, if there is a healthy backup, the Ovation Controller will initiate a failover to
make the backup module take control. This ensures that no process data is lost in the case of a
failure on the module in control. The Ovation Controller will only perform a failover if there is a
healthy backup available to take control (control will not be switched to a less healthy module).
The individual modules in a redundant Profibus module pair are designated primary and
secondary. The primary module is located on an odd numbered Ovation branch. The secondary
module is located on the next highest branch number (for example, if a primary module is located
on odd-numbered branch n, the secondary module is located on branch n + 1).
REF_1005
313
25.5 What is Profibus redundancy?
Figure 69: Redundancy diagram
314
REF_1005
25.6 What are Profibus hardware and software requirements?

The module and node records for the redundant Profibus modules and segments contain
information useful in troubleshooting the redundant Profibus modules. The module record
contains information on the operating mode of each segment (control, backup, or off),
communication status of each segment, and general module health status. The node records
contain the segment number, module status, and communication status.
Note: The Ovation Profibus system provides module redundancy only. Due to the nature of the
Profibus cabling requirements, data loss due to disconnected or broken cables is not supported.
The Ovation Profibus system provides module redundancy only (for example, this redundancy
guards against data loss due to a module failure). Due to the nature of the Profibus cabling
requirements, cable redundancy is not explicitly supported (which means that data loss could
possibly occur). Some devices support redundant cabling. Refer to the individual device's manual
for details.
A failover can only occur if there is a healthy module in backup. Once a module loses control
because of a failover, a module enters a failed state. The Port node records contain information
on that failed state. The module needs to be rebooted to remove it from a failed state. This will
clear the error in the Port node record. You should physically check the LEDs on the module,
cabling, and devices to help ensure that the error has truly been cleared. After rebooting, the
module should boot up in backup.
25.6 What are Profibus hardw are and softw are requirements?
Proper operation of a Profibus interface with an Ovation system requires:
Ovation 3.1 or greater. Ovation 3.1.1 or greater is required if you want to utilize redundancy.
One Ovation Operator Station drop, running the Windows operating system.
One or more Profibus I/O modules as necessary.
Profibus cabling (2-wire) as necessary to connect the Profibus I/O module to the Profibus
device(s). Additional modules might be necessary if you plan to create a redundant
connection.
GSD configuration files for each Profibus slave device connected to the network.
Note: When installing Profibus segments, it is crucial to use genuine Profibus cabling. Both
Profibus cables and Type E thermocouple cables are similar purple colors. Ensure that your
Profibus cabling is actually labeled 'Profibus' on the purple cable casing.
REF_1005
315
E C T I O N
26
26 Planning for DeviceNet
IN THIS SECTION
What is an overview of DeviceNet? ................................................................................ 318
What is field device interoperability? ............................................................................... 319
What are the DeviceNet and Ovation components? ....................................................... 320
What is a DeviceNet module? ......................................................................................... 321
What are the DeviceNet hardware and software requirements? .................................... 321
REF_1005
317
26.1 What is an overview of DeviceNet?
26.1 What is an overview of DeviceNet?

DeviceNet is an application layer protocol that links simple industrial devices and automation
systems. Whereas some applications are designed only to move data, DeviceNet is concerned
with the type of data that it carries. Because DeviceNet is an application layer protocol, its
messages convey specific types of information in each explicit message. For example, one byte
might carry only a service code whereas another byte might carry a specific ID. At the base level
in the hierarchy of plant networks, DeviceNet serves as a local area network (LAN) for devices.
DeviceNet offers reduced installation and material cost through the use of a multi-drop
configuration as opposed to the traditional one-to-one wiring scheme. This configuration allows for
node removal without breaking the trunk line or disconnecting power from the segment.
Conventional analog and discrete field instruments use point-to-point wiring, or one wire pair per
device. For example, if your plant has 1000 field devices, that would mean 1000 wire pairs. In
addition, conventional instruments are limited because they can carry only one type of information
(usually a process variable or control output) over the wire pair.
DeviceNet technology does not have these limitations. DeviceNet supports up to 63 devices on a
five-conductor cable. The lacework of devices is called a network. Each DeviceNet device on the
network has an integer address known as a media access identifier (MAC ID). No two devices
can share the same MAC ID. For all process applications including Ovation, considerations such
as power, process modularity, and data update rate must be considered.
DeviceNet is one of a family of protocols developed by the Open Device Vendor Association
(ODVA), an organization that supports technologies built on the Common Industrial Protocol
(CIP). DeviceNet uses CAN (Controller Area Network) for its data link layer, and CIP for the
upper-layers of the network, to create a stable network topology.
All DeviceNet devices must establish a connection before they can exchange information.
DeviceNet combines the CIP protocol and the CAN physical layer to transport information
between DeviceNet devices. DeviceNet devices can be classified as either master devices (also
known as scanners) or slave devices. Master devices gather input data from slave devices and
distribute output data to the slave devices. Slave devices are peripheral devices (for example
variable frequency drives, I/O, motor starters, etc.) that receive and transmit application data to
and from a master device. Each DeviceNet device must have a unique physical device tag and a
corresponding MAC ID. The network address is the current address that DeviceNet uses for the
device.
For more information on DeviceNet, visit the ODVA web site at http://www.odva.org/index.htm.
Note: Refer to the individual DeviceNet device vendor manuals and DeviceNet standards
documents for specific details of device and network capabilities.
Refer to the Ovation DeviceNet User Guide for information about using DeviceNet with Ovation.
318
REF_1005
26.2 What is field device interoperability?
26.2 What is field device interoperability?

work together to send and receive information related to their specific function in the process.
The ODVA has established guidelines for interoperability between field devices on a DeviceNet
segment. These guidelines address such aspects as physical characteristics, communication, and
software functionality.
Manufacturers can apply for a DeviceNet-approved certificate from the ODVA. After a product
passes several conformance tests at one of ODVAs authorized conformance test service
providers, it is certified by the ODVA to operate in open multi-vendor systems and receives an
official Declaration of Conformity from the ODVA. Devices can be certified as either Slaves or
Masters and can use various protocols with the DeviceNet standard.
REF_1005
319
26.3 What are the DeviceNet and Ovation components?
26.3 What are the DeviceNet and Ovation components?

Unlike conventional analog installations that have a dedicated pair of wires to connect each field
device to a host system, DeviceNet installations use two, twisted-pair cables that are enclosed in
a five-conductor cable to connect to multiple devices. One twisted pair is for power and the other
twisted pair is used to carry data, while the fifth wire serves as a drain. The cables, connected
devices, and supporting components are called a segment. You can design the segment as
either a branch or tree layout topology. The following figure depicts a typical implementation of
DeviceNet with an Ovation system.
Figure 70: Typical implementation of DeviceNet with Ovation
320
REF_1005
26.4 What is a DeviceNet module?

DeviceNet devices are intelligent field instruments that can range from simple I/O devices such as
push buttons and lights to sophisticated devices such as motor starters and variable frequency
drives with processors that monitor device performance and state. A common implementation is
to install devices in a motor control center (MCC).
26.4 What is a DeviceNet module?

The DeviceNet module provides an interface to a DeviceNet network. The DeviceNet module
contains a logic card (only the 3FPB or later field card artwork supports DeviceNet). The
DeviceNet module has an associated unique personality module.
The logic card provides a host processor based on ARM9 technology. Communication between
this processor and the Controller is through a 64K dual port memory. The Controller
communicates with the dual port memory using the Enhanced Block Transfer Protocol. This
protocol will allow up to 128 bytes/frame versus two bytes per frame with the standard I/O
transaction. The board also supports the standard block transfer historically used by various
Ovation modules.
The Host processor communicates with the DeviceNET interface. Communication with each
DeviceNet interface is through an 8-bit bus interface with the host processor (32 Kbytes for each
interface).
The logic card provides a 100 base Ethernet, and RS232 port for debug and firmware recovery.
These ports are only accessible with the cap removed from the EMOD. Additionally, a JTAG port
will be available to support emulation and firmware development. These ports are only available
with the modules removed from the case. Note that the JTAG port is not available for boundary
scan testing.
The host processor runs the Windriver VXWorks operating system. 32Mbytes of Flash memory
and 32 Mbytes of DRAM support the operating system and application.
26.5 What are the DeviceNet hardw are and softw are requirements?
Proper operation of a DeviceNet interface with an Ovation system requires:
One or more DeviceNet I/O modules, as necessary.
Device cabling (5-wire) as required.
Bulk power supply for network power, as specified by the DeviceNet Open Device Vendor
Association (ODVA).
Ovation software 3.1.2 or greater.
Ovation Operator Station running Windows XP or later.
Electronic Data Sheet (EDS) configuration files for each DeviceNet connected to the Ovation
network.
OCR400 Controller with a Group 2 IOIC (5X00226G02).
REF_1005
321
E C T I O N
27
27 Planning alarm management
IN THIS SECTION
What is an alarm? ........................................................................................................... 323
What is alarm management? .......................................................................................... 324
What are some alarm management problems? .............................................................. 325
What are some best practices for planning alarms? ....................................................... 325
What points can be used as alarms? .............................................................................. 326
How does the Ovation alarm system operate? ............................................................... 327
Types of alarm displays .................................................................................................. 328
Alarm list information fields ............................................................................................. 328
Displaying Alarm lists ...................................................................................................... 329
Alarm list tabs that display in the Alarm window ............................................................. 330
Remote Network Status list in the Operator Station Alarm window ................................ 339
What is the Alarm Annunciation window at the Operator Station? ................................. 341
What are some best practices for managing alarms? ..................................................... 342
What are nuisance alarms? ............................................................................................ 342
What are alarm floods? ................................................................................................... 343
27.1 What is an alarm?

An Ovation alarm is a message or signal that indicates an abnormal plant condition. This plant
condition is based on the status of an Ovation point. An alarm is created when you define limits
for the value of the point. If these limits are exceeded, the point goes into alarm. Typically, an
alarm requires an operator action.
An alarm indicates one of the following conditions:
Analog point has exceeded its high or low limits.
Analog point is becoming better or worse (value for point is moving closer to or further from its
defined limits).
Digital point has changed its state (on/off, 1 or 0).
An alarm can be a visual message and/or an audible sound that serves the following purposes in
an Ovation system:
Indicates an operator action is required.
Helps maintain normal plant performance.
Recognizes and avoids hazardous conditions.
Identifies deviations that could lead to financial losses.
Provides better understanding of the conditions that affect plant processes.
REF_1005
323
27.2 What is alarm management?
27.1.1 What is an example of the life of an alarm?

When you configure a point using the system configuration tools in the Developer Studio, you
apply default alarm settings to the point.
When you configure filtering for a point at the Operator Station, these settings are temporary and
are canceled when you close the Alarm window. Points in alarm appear in the Alarm window if
they pass the filtering criteria that are currently in effect.
The following is an example of how a point goes into alarm and how the alarm displays in the
system:
1. A point (A3005) exceeds the high limit that was defined by the system configuration tool and
goes into alarm. Assuming that A3005 passes the filtering criteria in effect, an alarm occurs
and appears in red (default color) in the following lists at the Operator Station:
Current Alarm list
Alarm History list
Unacknowledged Alarm list
2. A system operator acknowledges the A3005 alarm from the Acknowledge menu in the Alarm
window. The alarm now appears in the following lists:
Current Alarm list
Alarm History list (original alarm, not the acknowledgment event)
Acknowledged Alarm list
3. Point A3005 changes value and enters the defined range where the point value is no longer in
alarm. The alarm point appears in the following lists, but the color is now green (default color)
to indicate the alarm has returned to its normal value:
Current Alarm list
Alarm History list
Acknowledged Alarm list
Reset Alarm list
4. A system operator resets the A3005 alarm. The alarm then disappears from all the alarm lists
except from the Alarm History list.
27.2 What is alarm management?

Alarm management is the process used to properly design, implement, operate, and maintain
alarms in a plant.
Successful alarm management provides for low alarm rates in the plant without losing any critical
alarms that are required for safe plant operation.
324
REF_1005
27.3 What are some alarm management problems?
27.3 What are some alarm management problems?

Symptoms
Investigate your alarm management techniques if any of the following symptoms are occurring
regularly in your Ovation system:
Any significant operating disturbance generates unmanageable numbers of alarms.
Any minor operating disturbance generates a significant number of alarms.
Operating procedures are not tied to alarm activations.
Some alarms remain active for significant periods of time.
When alarms activate, the operator does not know what to do about them.
When there are no operating disturbances, there are active alarms.
Alarms activate that do not require operator attention.
Seemingly routine operations produce a significant number of alarms.
Causes
The following reasons may cause alarm management problems:
There is no plant-wide alarm philosophy.
Operator training is inadequate.
Operator displays are poorly designed.
Alarm limits that were specified during the system design are rarely reviewed for validity
during actual plant operating conditions.
Alarms are constantly added but are rarely deleted.
There are too many alarms because adding alarms seems to cost nothing. However, there is
cost in plant inefficiency and operator confusion.
27.4 What are some best practices for planning alarms?

As you begin to plan your alarm system, use the following guidelines:
Create an alarm management philosophy.
Gain commitment and ownership of the alarm management philosophy from all employees.
Decide early what points should be alarmed.
Decide what situations will trigger an alarm.
Document alarm guidelines to avoid future confusion.
Define and document procedures for adding and removing alarms.
Set rate goals for your alarms. Determine how many alarms during a defined time period are
acceptable.
Create a plan to manage future alarms.
REF_1005
325
27.5 What points can be used as alarms?
27.4.1 Establishing a philosophy for alarm management

You need to consider the following questions when designing your alarm management plans:
What size alarm screen should you use and how should you configure it?
What type of operator interface should you use (Alarm list or Iconic)?
What security issues do you need to address?
How should the alarms be logged?
How should you segregate the plant areas (destination is indicated by the first character in the
characteristic field)?
What priority definitions should you use to ensure that the most critical alarms are addressed
first?
What audible alarms should you use?
What descriptive fields do you want to see in your alarm list displays?
How can you reduce or suppress alarms?
27.5 What points can be used as alarms?

An alarm point refers to any point that goes into and out of the alarm state. Points in alarm
automatically display on an alarm list at the Operator Station. Unless you make configuration
changes to the alarm object that defines how alarms display, the default values for the alarm
display are used.
The following points can be used as alarm points:
Analogs
Digitals
Packed Digitals
Devices
Drops
Alerts (indicate status of Fieldbus devices in Windows systems).
Analog points have four high, four low, and one user-defined limit. You can assign an incremental
high and low value which re-alarms when values exceed the high (positively) and low (negatively)
limit by this incremental amount. Deadbands shall also be available to define how far the analog
point must return inside the limit in order to be considered returned from the alarm condition. This
helps reduce alarm chattering.
Digital and device points have standard normal/abnormal operating states.
I/O modules are alarmed as devices and they provide information as to the point in alarm and its
possible cause.
Packed group digitals are defined so that the 16 digital inputs are all stored in one database
record which then alarms that record if one or all of the bits go into an abnormal state.
Drop points alarm diagnostic information in the system.
326
REF_1005
27.6 How does the Ovation alarm system operate?
27.5.1 When is a point out of service?

The Ovation system continually scans the system points to monitor their values and quality. When
a point is removed from scan, the Ovation system no longer monitors the point's value, and the
point's quality changes to bad. This removal from scan is achieved either manually or by a
hardware failure.
If a hardware failure occurs and the scan value is no longer reliable, the point is alarmed and also
is identified as having bad quality.
Any point that is identified as having bad quality is considered to be out of service.
If a point is originated by a drop that loses power, the point is given a time-out status and is
considered out of service. It is also possible for application software to change a points quality to
bad.
You can remove any point from scan and insert a new value. A different quality is assigned in this
case (such as fair) and the programs that use this point can determine its validity. The alarm
system handles the inserted value no differently than it handles the scanned value.
27.6 How does the Ovation alarm s ystem operate?

The Ovation alarm system is a multi-process system that performs alarm management functions
from alarm detection to alarm clearing. These functions are done system-wide:
Alarm detection is performed at the drop where a point originates. The point is monitored
whether it is an I/O point or a calculated point whose value is set by algorithm calculations.
When a point is tagged as in alarm, the data is broadcast on the network and then detected
by the destination drops.
The Operator Station detects the alarm event and adds it to the current alarm list.
The Operator Station also updates two additional lists, the History list and the
Unacknowledged list, with the information about the point in alarm.
The alarm appears on any process diagrams that contain that point.
The Historian drop logs and archives the alarm event for later retrieval.
An operator acknowledges the alarm at its source, and this acknowledgement clears the
alarm at all the receiving drops.
REF_1005
327
27.7 Types of alarm displays
27.7 Types of alarm displays

There are two types of alarm displays:
Alarm list displays alarms in a list type (see page 332) of interface with color-coded priorities
and sorted by time stamp. A list provides filtering in normal and priority modes and contains
separate tabs to isolate alarms by states such as acknowledged, unacknowledged, history,
and resets.
Iconic alarm display alarms in a graphical interface (bitmaps) grouping areas in single icons
like Annunciator or light boxes. Bitmaps change colors to indicate alarm condition / status and
are linked to process graphics for additional situation awareness.
27.8 Alarm list information fields

Each line of alarm information in an alarm list can contain the following information fields.
However, you can configure what fields you want to display in an alarm list:
328
Date
Time
Alarm Types
Code
Name
Description of alarm (up to 30 characters)
Alarm Priority
Network Alias
Network ID
Alarm Destination (Characteristics)
Value/Quality
Engineering Units
Limit exceeded
Incremental Limit
Plant Mode
Alarm state (high, low, better, worse, etc.)
REF_1005
27.9 Displaying Alarm lists
27.9 Displa ying Alarm lists

Alarms display on Ovation Operator Station screens. Locate the screen in a central location of the
control room where the operator has the best view of the screen. The screen should not be less
than 20 inches diagonally and should be mounted from a ceiling suspension, whenever possible.
Remove any obstructions that hinder the operator's viewing ability.
The alarm screen contains lines of text that describe each alarm and typically include a time
stamp indicating when the alarm occurred. New alarms appear at the top of the list while older
alarms scroll to the bottom. There are five different alarm lists (see page 330) that identify the
status of each alarm in the system.
The alarm remains on the screen until it is acknowledged and then cleared by the alarm reset
function of the alarm system.
REF_1005
329
27.10 Alarm list tabs that display in the Alarm window
27.10 Alarm list tabs that displ a y in the Alarm w indow

The Alarm window displays different types of alarm lists that provide information about each alarm
in the Ovation system.
The Operator interface to the Alarm system consists of an Alarm window that contains multiple
tabs. These tabs display the following alarm lists:
Alarm list (see page 332).
Alarm History list (see page 333).
Acknowledged Alarm list (see page 334).
Unacknowledged Alarm list (see page 335).
Reset list (see page 336).
Alarm Check Remove list
Icon list (see page 337) (only displayed when the icon list is configured for Iconic Alarming).
Remote Network Status list (see page 339) (only displayed when the Alarm window is
configured to receive alarms from remote networks).
When an alarm occurs, it appears on the Alarm list, the History list, and the Unacknowledged list.
After the alarm is acknowledged, it remains on the Alarm list until it returns to normal and the
return is acknowledged and reset. After the return is reset, the alarm goes off all the Alarm lists.
Note: You can select the desired style of Alarm window from the Developer Studio. The
recommended setting is the Enhanced Grid Mode Style (default) which does not allow gaps or
blank lines in Alarm lists. This provides for better grouping and sorting of alarms.
You can also use the Legacy/Classic Style setting which displays lists as they appeared in Pre3.3.1 Ovation releases. This style allows gaps and blank lines in Alarm lists.
Each list (except the Icon and Remote Network Status lists) incorporates two modes of filtering,
Normal and Priority. A single button switches each display between the two modes of filtering.
The tabs in the Alarm Filtering Definition window correspond to the alarm lists.
From the Alarm window, you can perform individual, group, or page alarm acknowledgment.
You can also right-click a point alarm item in an alarm list to access a Point Menu that provides
information about the point.
The following table shows the data that is displayed for each point type on the Alarm List, Alarm
History List, Acknowledged Alarm List, Unacknowledged Alarm List, and the Reset List.
Alarm Data
330
ALARM EVENT
POINT DATA
Analog Alarm, returns
Date, time, alarm type, code, point name, description, value, units, limit
incrementals, alarm priority, alarm destination, and plant mode.
Digital Alarm, returns
Date, time, alarm type, code, point name, description, set/reset, value, alarm
priority, alarm destination, and plant mode.
Drop Alarm, returns
Date, time, alarm type, point name, description, fault code/fault identification,
fault parameters 1 and 2, alarm priority, and alarm destination.
REF_1005
ALARM EVENT
POINT DATA
Packed Group alarms
Date, time, alarm type, point name, description, value (in its binary
representation), blank or T (time out), bits in alarms in binary, alarm
priority, alarm destination, and plant mode.
Packed Group Alarms

Used as Devices
Date, time, alarm type, PN, ED, set/reset description, value, attention code,
override code, and alarm description.
State Change
Date, time, alarm type, code, point name, description, set/reset, value
quality. State Change only applies to the alarms shown on the Alarm History
List.
Time-Outs
When a timed-out point is in alarm and displayed on the Alarm List or

Unacknowledged Alarm List, or Reset List, the Quality field displays the
letter T.
The letter T only appears on the Alarm History List if the list is updated
after the point times out.
Plant Web Alerts
Date, time, alarm type, code, point name, description, value (identifies the
specific alerts that are active), quality, alarm priority, alarm destination.
Node/Module
Date, time, alarm type, PN, ED, value (binary)/Quality, bits in alarm (binary),
alarm priority, alarm destination.
Records
Alarm Check Removed
REF_1005
Date, time, alarm type, code, point name, description, Net Alias, AP, AY,
value, quality, units, limit, incr, PM, Net ID
331
27.10.1
Alarm List in the Operator Station Alarm window
The Alarm List has the following attributes:
Displays the current system alarms and returns.
Value and status of the alarm constantly update.
The number of alarm lines that display in a window is configurable and is also determined by
the size of the window.
Displays all the points designated by the Alarm list filtering criteria for the current alarm mode
(Normal or Priority).
Displays the most recent alarms on the first page, with the capability to access more alarms
by paging backwards.
In the Legacy/Classic alarm window style, each alarm point appears once in this list. When an
existing alarm changes state causing a new alarm event, either the new status writes over the
old status or the new status is added to the top of the display and the old status is removed.
This is configurable.
Displays the total number of points currently in alarm. You can select alarm entries from the
list and acknowledge them. This changes the color of the alarm to indicate that the alarm is
acknowledged.
Alarm events are color-coded and you can configure the alarms so that different priority
alarms display in different colors. You can also use colors to differentiate between an
acknowledged status and an unacknowledged alarm.
The following figure shows an example of the Alarm window displaying the Home tab in
combination with the List tab.
Figure 71: Alarm window example
332
REF_1005
27.10.2
History list in the Operator Station Alarm window
The Alarm History list has the following attributes:
Each alarm point may appear in this list several times.
Displays all the points designated by the History filtering criteria for the current alarm mode
All incrementals and returns display as individual entries.
Displays the most recent alarms on the first page, with scrolling capabilities available for
paging back.
Contains the 15,000 most recent alarm events (alarms, returns, and state changes).
combination with the History tab.
Figure 72: History list in the Alarm window
REF_1005
333
27.10.3
Acknowledged list in the Operator Station Alarm window
The Acknowledged list has the following attributes:
Displays the current acknowledged alarms.
Displays all the points designated by the Acknowledged filtering criteria for the current alarm
mode (Normal or Priority).
When an acknowledged alarm returns to normal or becomes unacknowledged, it is removed

from the list.
Each alarm point appears once in this list.
combination with the Acknowledged tab.
Figure 73: Acknowledged list in the Alarm window
334
REF_1005
27.10.4
Unacknowledged list in the Operator Station Alarm window
The Unacknowledged Alarm list has the following attributes:
Displays all the points designated by the unacknowledged filtering criteria for the current
alarm mode (Normal or Priority).
Removes the alarm when the alarm is acknowledged.
Alarm point appears only once in this list.
When all alarms in the system are acknowledged, this list is blank.
Adds the newest alarms to the end of the list (in Legacy/Classic alarm style only).
Displays the alarms in reverse order with the oldest unacknowledged alarm appearing at the
top of the first page (in Legacy/Classic alarm style only).
combination with the Unacknowledged tab.
Figure 74: Unacknowledged list in the Alarm window
REF_1005
335
27.10.5
Reset list in the Operator Station Alarm window
The Reset Alarm list has the following attributes:
Displays all the points designated by the Reset filtering criteria for the current alarm mode
Displays all the resettable returns in reverse order of the Alarm list. New resettable returns
are placed at the bottom of the list (in Legacy/Classic alarm style only).
combination with the Reset tab.
Figure 75: Reset list in the Alarm window
336
REF_1005
27.10.6
Icon list in the Operator Station Alarm window
Iconic alarming provides a mechanism to group alarms based on their priority and their plant area.
After you have configured an Iconic alarm, you can display it in the Operator Station Alarm
window in the Iconic list tab (refer to Ovation Operator Station Configuration Guide for information
on configuring Iconic alarms).
Figure 76: Iconic list in the Alarm window
REF_1005
337

These groups of alarms are represented by preconfigured bitmaps. Two bitmaps are typically
defined for each alarm group. One bitmap identifies a group not in alarm; and the other
represents a group in alarm. The maximum number of groups that can be configured is based on
the size of the bitmaps.
Iconic alarming can accommodate xlarge (96 x 96), large (64 x 64), medium (48 x 48), or small
(32 x 32) bitmaps. The maximum number of rows and columns is based on the icon size that is
configured. The following table describes the icon sizes that are available. (See Ovation Operator
Station Configuration Guide.)
Icon size
SIZE
MAX ROW
MAX COL
MAX GROUPS
SIZE
XL
28
12
336
96x96
21
16
336
64x64 (Default)
17
19
323
48x48
13
23
299
32x32
The state of an iconic alarm can be determined by a color-coded border. The border identifies if
the group is in alarm or not in alarm.
For groups that are in alarm, the border color identifies the unacknowledged status. If all the
alarms in a group are acknowledged, the border color displays in the acknowledged color. If at
least one alarm in the group is unacknowledged, the border color remains in the unacknowledged
color. (See Ovation Operator Station Configuration Guide.) You can also configure a default
Iconic alarm group.
There are two ways to display an Iconic Alarm list. You can use the Iconic Configuration Options
window to select the desired type of Iconic alarm display.
Display only the Icon list in the Iconic tab.

When you configure the Icon list in this manner, you can view all other alarm lists (Alarm List,
History, Acknowledged, Unacknowledged, Reset, or Alarm Check Remove).
Display the Icon list above the Alarm list.

When you configure the Icon list in this manner, the list of the alarms associated with the
selected icon group displays under the icon in the Iconic With List tab. No other alarm list tabs
are shown.
The currently selected alarm group is signified with a red border drawn around the icon tile. In
addition, the selected groups location (row, column) displays on the Status bar.
338
REF_1005
27.11 Remote Network Status list in the Operator Station Alarm window
Viewing diagrams from the Icon List
You can view a diagram or diagram group from the Icon List. If more than one diagram or diagram
group can be defined for each group, you may display a menu over the specific icon, right-click,
and select which diagram or diagram group you wish to view.
If only one diagram or diagram group can be defined, then simply left-click the icon to view the
diagram or diagram group. When the Icon List is configured as the Alarm Lists filter, the selection
of an alarm group results in the Alarm List being filtered based on the selected group. Thus, you
can only view the diagrams by displaying the menu over the alarm group when the system is
configured in this manner.
27.11 Remote Netw ork Status list in the Operator Sta tion Al arm
window
The Remote Network Status list presents detailed information concerning each remote network
connection.
Note: If you do not configure the alarm display to receive alarms from remote networks, the
Remote Network Status tab does not display.
Figure 77: Remote Network Status list in Alarm window
REF_1005
339
27.11 Remote Network Status list in the Operator Station Alarm window
You can select the columns that you want to display in the Remote Network Status tab:
Alarm window -> Remote Network Status tab ->- Home ribbon tab -> Select Column(s)
window
Select the Remote Network Status view, select the desired columns, and then select OK.
Figure 78: Columns window for Remote Networks

The columns are defined as follows:
ID - Remote network ID.
Alias - Remote network alias.
Status - Identifies the status of the connection to the remote network.
Alarm Data Server Connection - Identifies the alarm data server where the remote alarm
messages are originating from. When the connection to the alarm data server is lost, it designates
which server the alarm system last connected to.
Primary Alarm Data Server - IP address of the primary alarm data server on the remote network.
This is the machine that sends the remote alarm messages.
Secondary Alarm Data Sever - IP address of the secondary alarm data server on the remote
network. This is the machine that sends the remote alarm messages.
340
REF_1005
27.12 What is the Alarm Annunciation window at the Operator Station?
27.12 What is the Alarm Annunciation w indow at the Operator Station?

The Alarm Annunciation window is an optional alarm application that displays alarms in
configurable alarm bands. The alarm bands contain alarm message boxes that identify current
local alarms (alarms on remote networks do not display in the Alarm Annunciation window). When
a point goes into alarm, it displays in the appropriate band and if configured, also causes an
audible to sound.
You can access a pop-up menu from the Alarm Annunciation window by right clicking on the
Alarm Annunciation window area. This menu provides additional information about the alarms and
the points that are in alarm.
You can configure your alarm system to initiate either an Alarm window or the Alarm Annunciation
window. You can display both alarm window types at the same time, but the Alarm Annunciation
window always appears at the top of the alarm screen and you cannot cover the alarm
annunciation window with any other windows.
You can configure blinking for each Alarm Annunciation window to determine whether
unacknowledged alarms and unacknowledged returns blink or not. If blinking is configured, any
unacknowledged alarm or return blinks until it is acknowledged (see Ovation Operator Station
Configuration Guide).
Note: Any applicable Alarm Annunciation window parameters that are not configured
specifically for the Annunciation window use values that are set for the Alarm system (such as
colors and the use of audio to annunciate alarms).
Figure 79: Alarm Annunciation window example
REF_1005
341
27.13 What are some best practices for managing alarms?
27.13 What are some best practices for managing alarms?

Ideally, your goal should be that under normal plant conditions, there will be no alarms in your
Ovation system. Of course, in actual practice, there will be alarms in your system, so consider
using the following techniques to keep your alarms manageable:
All plant employees should use the same approach to communicate, operate, and optimize
the alarm management system.
Use the same method to add all new alarms.
Use the same method to remove all obsolete and problem alarms.
Configure alarms so they alert operators to disruptive situations in the plant, especially
situations that might result in financial loss or hazardous conditions.
Only show alarms that operators can act upon.
Operators should acknowledge alarms from their area of responsibility.
Use alarms that require operator action.
Re-evaluate alarm priorities frequently and reconfigure alarm priorities to distinguish between
warning conditions and alarm conditions.
To decrease troublesome alarms, consider increasing alarm limits, deadbands, or sensor

limits.
Change operating procedures and training methods to support new alarm strategies.
Use alarm delays to eliminate alarming of transient conditions.
Use analysis tools to investigate alarm origins.
Use mass editing tools as much as possible to verify and improve the alarm system.
When an alarm is removed, use another method for situation awareness, for example,
graphics.
Do not assume that all trip points and limits are correct; review them occasionally to make
sure they have not changed.
Be aware of any new projects that are added to the system (links integration, system
modifications, etc.) since they may trigger excessive alarming.
Ownership needs be consistent and committed; alarm management is a continuous process

that requires constant optimization. Take at least two hours a week to review alarm
management.
Assess the current alarm situation and identify areas that need improvement.
Monitor the active alarms that are being broadcast on the system and analyze the results of
that alarm monitoring.
Reduce the number of unresolved standing alarms.
Identify and resolve alarm management implementation issues.
27.14 What are nuisance alarms?

Nuisance alarms are defined as the following:
342
Alarms that occur that require no operator action.
Alarms that operators do not know how to respond to.
Alarms where nothing is wrong but alarms are still active.
Alarms that are active for long periods of time.
REF_1005
27.15 What are alarm floods?
27.14.1
What methods can be used to manage nuisance alarms?
You can manage nuisance alarms by performing the following:
Remove out-of-commission, redundant, and useless alarms.
Use the priority filter to filter out nuisance alarms.
Change deadband limits or sensor limits for an alarm.
Use the auto acknowledge/reset function.

The term alarm flood refers to large numbers of alarms occurring suddenly. Alarm floods occur
when:
Large numbers of alarms are produced during normal plant operation.
Large numbers of alarms are produced due to a minor disturbance.
An unmanageable number of alarms are produced due to a major disturbance.
You can manage and even eliminate alarm floods by using Best practices for managing alarms
(see page 342).
27.15.1
What are suggested alarm rates?
The Engineering Equipment and Material Users Association (EEMUA) states that the average
rate for a point alarm should not exceed six alarms per hour during normal plant operation.
During a plant disturbance (such as transient condition), the rate for a point alarm should not
exceed 24 alarms per hour during a two-hour time frame.
Careful alarm management can achieve less than one alarm per hour or less than eight alarms
per shift.
27.15.2
Configuring filtering for alarms
You should assign each alarm in your system certain properties to allow a plant operator to
quickly and easily decide the nature of an alarm and what action should be taken to address the
alarm. If you cannot filter alarms, you cannot manage alarms efficiently.
Use the applicable configuration tool (Developer Studio for Windows or Init and Admin Tools for
Solaris) to define the filters for your alarms.
You can assign the following properties to alarms to improve alarm filtering and more quickly
identify and react to alarms:
Alarm Destinations (see page 344).
Priorities (see page 346).
Sounds (see page 348).
Descriptions (see page 344).
REF_1005
343

Using characteristics to filter alarms
Each process point in an Ovation system can be associated with a set of eight alphanumeric
characters called the point characteristics. You can use the Point Builder to assign characteristics
to a point during the creation or editing of a point. These characteristics can be used to help filter
alarms.
Each character within the set defines some characteristic of the point, such as the plant area or
type of equipment. The meaning of each characteristic is dependent on the character and its
position. The first character is always used as the destination (for alarm functions) and is often
defined as the plant area. The other positions may be defined in any way.
The default characteristic is a dash (-) which acts as a wildcard. Using a wildcard instead of a
specific character reduces the alarm filtering capabilities for that point.
The following sample table shows a hypothetical listing of characteristics.
Characteristics
CHARACTER
POSITION
DESCRIPTION
DEFINITION
(M APS
(M APS
TO THE
CHARACTERISTICS FOR
E ACH V ALUE)
(M APS
TO TAB
POSITION 1-8)
344
CHARACTER
TO THE DESCRIPTION
FOR EACH VALUE )
Plant Area
A
B
C
D
E-M
N
O
P
Q
R-Z
Unit 1 Air System

Unit 1 Boiler
Unit 1 Condensate
Unit 1 Generator
Unit 1 Spare
Unit 2 Air System
Unit 2 Boiler
Unit 2 Condensate
Unit 2 Generator
Unit 2 Spare
Subsystem
G
S
W
O
E
Gas
Steam
Water
Oil
Electrical
Equipment
P
I
L
V
F
Pump
IP Turbine
LP Turbine
Valve
Fan
Designator
A
B
C
D
E
W
1
2
A
B
C
D
East
West
1
2
REF_1005
CHARACTER
POSITION
DESCRIPTION
CHARACTER
DEFINITION
(M APS
(M APS
TO THE
CHARACTERISTICS FOR
E ACH V ALUE)
(M APS
TO TAB
POSITION 1-8)
Parameter
T
P
V
F
6-8
Spare
Not applicable
TO THE DESCRIPTION
FOR EACH VALUE )
Temperature
Pressure
Volts
Flow
Not applicable
The following figure is an example of a GUI used to configure characteristics for alarm
destinations.
REF_1005
345

Using priorities to filter alarms
Assigning priorities provides a mechanism for enforcing risk management in a plant. Assign
priority levels based on the response required from the operator.
Priority filtering provides an operator with visual effects to properly manage alarms depending on
the seriousness of the alarm and the required operator response:
Visual effects consist of using colors on the alarm screen to alert and inform the operator
what and where the alarm is.
Sound effects can be incorporated and consist of a unique sound that is clearly audible in the
control room. This sound alerts the operators to a plant disturbance that requires attention.
The sound should be a tone that is easily recognized by plant personnel.
Assign alarm priorities to every alarm tag in your control system. Up to eight priorities can be
assigned to each alarm point. It is possible to filter alarm points based on priority. Examples of
these priorities are described here:
Priority 1 = Unsafe condition. This priority represents a time-critical condition that requires
immediate operator action to prevent equipment damage or personal injury.
Priority 2 = Loss of performance. This priority represents a situation that requires immediate
operator action to prevent the alarm going to a Priority 1.
Priority 3 = Loss of major equipment functionality. Requires some action to correct.
Priority 4 = Loss of minor equipment functionality. Requires some action to correct.
Priority 5 = Maintenance alarms.
Priority 6 - 8 = Used for alerts and can be filtered in a separate alarm screen.
346
REF_1005

The following figure is an example of a GUI used to configure priorities for alarms.
Selecting an alarm filtering mode

You can select either a Normal (N) or Priority (P) mode when you determine the filtering for an
alarm.
You can configure two different scenarios for alarm filtering, one for normal mode and one for
priority mode. You can then toggle between the two modes to display two different alarm filtering
settings.
Alarms that pass the defined filtering parameters for the currently selected mode (normal or
priority) appear on the Base Alarm window.
REF_1005
347
27.15.3
Using audio for situation awareness
You can enhance an operator's awareness and response time to alarms by incorporating alarm
sounds. The following functions are available when you configure or use audio alarms:
Assign an audio alarm based on priority.
Record a sound or voice command to serve as an audio alarm.
Acknowledge an audio alarm in an alarm screen.
Silence an audio alarm when you acknowledge the alarm.
Use external horns for the audio alarm.
Acknowledge an audio alarm from any HMI.
Use a continuous audio system. This type of audio system uses alarms that sound until
manually stopped.
The following figure is an example of a GUI used to configure sounds/audio for alarms.
27.15.4
What are the methods used to log alarms?
Emerson recommends that you log all alarms through a printer and/or a Historian drop. You can
then use this information to analyze events and to improve your alarm management policies.
If a Historian is present in the system, then a printer is typically not used unless there is a special
request for printout of the alarms. The alarm information that is collected and logged can be used
to analyze the alarm patterns and occurrences.
Periodically, evaluate your alarm system and modify it as needed to improve performance.
348
REF_1005
27.15.5
Using security for alarm management
Security provides the ability to designate alarm system privileges based on user roles. Depending
on your defined role, you may or may not be able to perform the following alarm functions:
Set limit checking on or off.
Disable auto cutout.
Modify alarm limits.
Modify UDA limits.
Acknowledge alarms.
Modify alarm filtering.
Allow the segregation of alarm security by using security groups for designated plant areas.
Use a dedicated alarm printer for paper logs and/or send alarms to the Historian.
The following figure is an example of a GUI used to configure security for alarm privileges.
REF_1005
349
27.15.6
Using PlantWeb Alerts for Fieldbus alarms
The Ovation alarm system can process alarms generated by Foundation Fieldbus devices. These
alarms are identified as PlantWeb Alerts which are separate and distinct from process alarms:
350
Advisory Alarm Indicates conditions that have no current impact of the devices ability to
sense and control, but may impact operation if some action does not occur to handle the
condition.
Maintenance Alarm Indicates that the device needs maintenance soon and is in danger of
losing its ability to sense and control.
Failed Alarm Indicates that the device needs maintenance now and that the device has lost
its ability to sense and control.
Communication Alarm Ovation is unable to communicate with the device.
REF_1005
27.15.7
Setting alarm limits
You can set the following types of limits for alarms:

Value Limits
Set the values in these fields to alarm when an out of bound condition occurs. Review these
values periodically to ensure validity.
Variable Limits
Use if the tolerance changes for different operating conditions. For example, lube oil pressure
changes since pressure changes as the load changes.
Incremental Alarms
Use sparingly, where they are applicable (for example, staged alarms), and do not overwhelm the
Operator with multiple incremental alarms.
Deadband Management
Use this technique frequently to avoid chattering around the defined limits. You can correct noisy
signals by using this feature.
EEMUA guidelines suggest that deadbands should be 0.5 to 1% of the defined engineering
range.
Use the configuration tool (Developer Studio for Windows or Init and Admin Tools for Solaris) to
set alarm limits.
REF_1005
351
27.15.8
What methods are available to reduce the number of alarms in your
system?
In order to manage your alarms successfully, you need to incorporate techniques that reduce the
number of alarms in your system. If your system has too many alarms, operators cannot
efficiently manage the alarms and this may result in plant disruptions.
There are techniques available that can help you reduce the number of alarms in your system.
Use these techniques in your alarm management strategy. Refer to Best practices for managing
alarms (see page 342).
352
REF_1005

What is alarm suppression logic?
Alarms that are the result of expected events should be suppressed. You can use suppression
logic to detect the point alarm and to effectively remove it.
You can also use suppression logic to eliminate alarms that are a direct result of other alarms
already reported. An example of alarm suppression is if a motor is turned off, the alarms
associated with other sensors on that motor can be suppressed since they are no longer
meaningful for that condition of the motor. When the motor is turned back on, the alarm
suppression is lifted. This suppression is typically triggered by a digital change of state (on/off,
set/reset, etc.).
Some questions need to be answered before using suppression logic on certain alarms:
1. Is the alarm required if the equipment goes offline?
2. Is the alarm required if the equipment is out of service?
If the answer is No to these questions, then the alarm can be safely suppressed.
You can inhibit any alarm point from being alarmed either through manual suppression by the
operator (turn limit checking off) or through application algorithms that perform logic calculations
and stop (cutout) a point from going into alarm.
Note: Limit checking for a point is defined in the Limits tab of the Point Builder and can be
turned off in the Alarm tab of the Point Information window at the Operator Station.
Alarm cutout for a point is defined in the Alarm tab of the Point Builder and can be turned off in
the Alarm tab of the Point Information window at the Operator Station.
Use the following techniques to suppress alarms:
Do a cutout analysis based on all operating conditions.
Do a validity check on the most important cutout signals (quality checks).
Use a Permissive if suppression logic requires a mechanism where no single point of failure
can prevent the alarm from being actuated. For example, drum level alarms are cut only if
MFT ON and BFPs are off.
Typically, 75% of signals required for cutout already exist. The rest must be rationalized.
REF_1005
353

Delaying alarms
Alarm delays are used to reduce alarm chattering and to reduce nuisance alarms. Only use time
delays for non-critical alarms, such as water treatment operations.
Use the following techniques to delay alarms:
Provide a suitable mechanism to reduce nuisance alarms.
Delaying alarms is only recommended for non-critical alarms, such as water treatment or loss
of DCS redundancy.
Delaying an alarm is useful during equipment startup since equipment needs an opportunity
to reach proper operation before an alarm is triggered. For example, an amps alarm during
fan startup.
Cutout Delays
Cutout delays are a good way to reduce alarms when a unit is starting up.
Delay is in effect after the return of an alarm from the cutout condition. For example, Low flow
alarm is delayed where the pump has not established flow after the on command has been
given.
Use the Point Builder configuration tool (Developer Studio for Windows or Init and Admin Tools
for Solaris) to set alarm delays.
354
REF_1005

What are some techniques for reducing alarms?
The following techniques provide methods to reduce alarms:
Inhibits and Priority action alarms
These alarms reflect DCS initiated actions that are used to manage or initiate process changes in
the Ovation control system. Alarm only the most critical actions that affect the operation of the unit
(for example, LDC blocks and contingent functions). You can alert operators to these changes by
using bar graphs in graphics or by using color changes.
Redundant Transmitters
Where you have redundant transmitters, alarm only the selected transmitter, not individual inputs.
Also alarm transmitter deviations, not failures, since failures typically show as sensor alarms.
Compensated PV alarms
Always alarm on the resulting compensated value, not the raw inputs.
Deviation/Feedback alarms
Alarm the deviation between redundant transmitters and between valve positioners, if feedback is
available.
Ovation DCS System Alarms
Manage these alarms according to severity. Since Ovation is normally a fully redundant system,
most issues are considered maintenance items unless they directly affect the process. Normally,
an operator performs no action with these types of alarms.
Grouping alarms
Use alarm grouping when a set of alarms relates to the same general area and is configured with
the same limit or tolerances.
First out alarms
Use first-out alarms to manage alarms related to one large piece of equipment or process. The
idea of a first-out alarm is to alarm the root cause and the final consequence of the alarm and not
the alarms in between.
If you use a first-out alarm, it is a good idea to create a generic alarm message and link the
operator back to the summary diagram to diagnose the cause of the alarm.
Eclipsing alarms
If there are multiple alarms for the same process conditions, display the most severe alarm and
suppress the prior or less severe alarm condition.
REF_1005
355
27.15.9
What are the benefits of good alarm management?
The following conditions are the result of good alarm management:
356
Safety increases in the plant.
Environmental incidents decrease.
Operators have increased effectiveness.
Quality improves.
Plant availability improves.
Expenses decrease.
Operators experience better job satisfaction and increased confidence.
REF_1005
E C T I O N
28
28 Planning Connectivity for your Ovation system
IN THIS SECTION
What is Ovation Connectivity? ........................................................................................ 357
What are the available platforms for an Ovation communication interface? .................. 357
What are the physical connection options for an Ovation communication interface? .... 358
What are the current message protocols for an Ovation communication interface? ...... 359
Communication interface spreadsheets .......................................................................... 359
28.1 What is Ovation Connectivity?

Connectivity refers to the use of an Ovation communication interface to provide seamless
communication between an Ovation network and a product that is not directly tied to the primary
Ovation product. The interface maps data from field-devices, third-party hardware, and corporate
networks into your Ovation network.
The interface connection consists of a hardware device or a software application which Emerson
project engineers can customize to fit your company's needs. This approach allows a company to
continue to use existing third-party devices and to also expand their system capabilities with new
communication interfaces.
The following issues are considered when developing an Ovation Communication interface:
Platform (see page 357).
Physical connection (see page 358).
Message protocol (see page 359).
28.2 What are the available platforms for an Ovation communication

interface?
There are four platforms that support Ovation communication interfaces:
Link Controller Module (RLC)

This Ovation I/O module supports serial communication on a single serial port. The module
implements serial communication through an RS232, RS422, or RS485 connection. (See
Ovation I/O Reference Manual.)
Ovation Controller
The Controller is a drop on the Ovation network that contains modules (I/O) that are attached
to sensors on the actual plant equipment. These sensors measure the point values that are
then broadcast onto the Ovation Network. (See Ovation Controller User Guide.) The
Controller implements ethernet TCP/IP communication through software drivers.
REF_1005
357
28.3 What are the physical connection options for an Ovation communication interface?
Ethernet Link Controller (ELC)

The Ethernet Link Controller is a process controller that gathers data from remote locations in
order to monitor and manage equipment and conditions. An Ethernet Link Controller module
is designed to be installed in a standard Ovation I/O cabinet. The functionality of the Ethernet
Link Controller is closely related to a SCADA system.
Ovation workstation (typically an MMI or Operator Station)

The Ovation workstation drop provides communication with plant processes throughout the
Ovation network and monitors normal and abnormal plant conditions. The workstation
implements serial or ethernet TCP/IP communication through a software package such as
SCADA or OPC.
28.3 What are the physical connection options for an Ovation

communication interface?
Physical connection refers to the actual medium used to transfer data between Ovation and a
remote device. The medium options are:
Serial
RS-232 serial (Recommended Standard 232) is a standard for exchanging messages.
Ethernet
TCP/IP (Transmission Control Protocol/Internet Protocol) Ethernet
Bus technology
Fieldbus
Profibus
DeviceNet
358
REF_1005
28.4 What are the current message protocols for an Ovation communication interface?
28.4 What are the current message protocols for an Ovation

communication interface?
Message protocols refer to the specifications that define the type of message that is transmitted
over an Ovation communication interface. The current message protocols are:
Allen-Bradley DF1
ControlLogix EIP
PCCC
Modbus RTU
Modbus TCP
Open Modbus TCP
DNP
D-EHC
MHI Proprietary
GSM
GE Proprietary
OPTO-22
Reliance
Siemens 3964R
OPC
CSP (PLC5)
RTP
Fieldbus
Profibus
IEC 61850
IEC 60870-5-104
IEC 60870-5-101
28.5 Communication interface spreadsheets

There are two spreadsheets (Hardware/device and Release version) that provide information
about the different communication interfaces that Ovation currently supports. These spreadsheets
are:
Hardware/device spreadsheet that contains the following information:

Hardware or device used in a communication interface.
Physical connection used for an interface.
Protocol that the interface uses to send messages.
Available platform(s) for the interface.
Interface options to connect to Ovation
Release version spreadsheet

Communication interface name.
Ovation software releases that support the interface.
REF_1005
359

Related Ovation documentation to help you connect, configure, and use the interface.
Here are some suggestions for using the spreadsheets:
1. Use the Hardware/device spreadsheet to identify:
Specific hardware in your interface.
The choices of physical connection for your interface (Ethernet, Serial, or Bus).
The appropriate message protocol.
The desired platform and Ovation interface options.
The release reference code that matches your choices.
2. Once you have made your selections, match the code from the Hardware/device spreadsheet
to the code in the Release version spreadsheet. This identifies the Ovation software releases
that support your communication interface.
360
REF_1005
28.5.1 Hardware/Device spreadsheet
REF_1005
361
362
REF_1005
REF_1005
363
28.5.2 Release version spreadsheet
364
REF_1005
REF_1005
365
366
REF_1005
E C T I O N
29
29 Planning your Ovation Security Center
IN THIS SECTION
What is the Ovation Security Center? ............................................................................. 367
Functions of the Ovation Security Center ....................................................................... 367
Appliances in the Ovation Security Center ..................................................................... 368
OSC compatibility with Ovation releases ........................................................................ 370
29.1 What is the Ovation Security Center?

The Ovation Security Center (OSC) is a suite of hardware and software tools (appliances) that
provide electronic security management functions. The OSC appliances are designed to enhance
and manage cyber security of Ovation Distributed Control Systems (DCS) without disrupting the
controlled process.
Ovation Security Centers can operate on either Ovation software platform; Microsoft Windows or
SUN Solaris systems.
29.2 Functions of the Ovation Security Center

Ovation Security Centers performs the following functions:
Supports Windows and Solaris operating systems.
Supports cyber security of multiple Ovation control systems.
VSPM appliance
Discovers vulnerabilities in operating systems, configurations, patches, malware, and other

system software.
Discovers security issues in all network devices, including servers, workstations, laptops,
switches, and routers.
MP appliance
Allows only whitelisted applications to run in workstations.
Verifies file integrity to prevent tampering.
SIEM appliance
Combines and normalizes events from multiple devices.
Correlates events to identify potential security incidents.
REF_1005
367
29.3 Appliances in the Ovation Security Center

The Ovation Security Center consists of the following components (appliances), plus a
management center:
Vulnerability Scan and Patch Management (VSPM).

VSPM uses two third-party packages from Lumension Security to scan an Ovation
system for security weaknesses and to distribute patches to remedy these weaknesses.
Malware Prevention (MP).

MP uses the third-party package, BOUNCER from CoreTrace, to protect the Ovation
system by employing a whitelist approach to detect and prevent malware from executing.
Security Incident and Event Manager (SIEM).

SIEM uses the third-party package, NitroView Enterprise Security Manager with Receiver
functionality (ESMREC) from NitroSecurity, to collect, correlate, and report security
events.
368
REF_1005

The OSC uses an Emerson hosted subscription infrastructure since OSC requires that reliable
secure communication exists between the management center and the clients that are being
managed.
A secure Internet communications path is also required between the customer's site and the
Emerson hosted subscription server for downloading patches and vulnerability information.
The following graphic illustrates a typical cabinet configuration containing the Security Center
components
A typical cabinet configuration consists of the following components that are displayed in the
following illustration:
Cisco Router.
Primary and secondary CoreTrace Bouncer.
Lumension box supplied by Dell.
Nitro Security USM system.
Primary and secondary power distribution center.
Figure 80: Typical cabinet configuration for OSC appliances
REF_1005
369
29.4 OSC compatibility with Ovation releases
29.4 OSC compatibility w ith Ovation releases

The following table identifies which OSC components are compatible with various Ovation
releases.
OVATION
RELEASE
SIEM
VULNERABILITY
SCANNER
PATCH
MANAGER
MP
Windows software releases

3.1 and later
Yes
Yes
Yes
Yes
3.0 *
Yes
Yes
Yes
Yes
2.4 *
Yes
Yes
Yes *
Yes
Solaris software releases

1.9
Yes
Yes
Yes*
Yes *
1.8
Yes
Yes
Yes*
Yes *
1.7.2
Yes
Yes
Yes*
Yes *
Note: An asterisk (*) indicates that you should contact Emerson for additional information about using
this release with OSC. To discuss using the OSC for software levels not listed, contact Emerson.
370
REF_1005
E C T I O N
30
30 Planning your Safety Instrumented System
IN THIS SECTION
What is a Safety Instrumented System? ......................................................................... 371
Functions of Ovation SIS ................................................................................................ 372
Limitations for Ovation SIS system ................................................................................. 372
Hardware components of Ovation SIS ............................................................................ 373
Software components of Ovation SIS ............................................................................. 375
Ovation SIS Logic Solver algorithm table ....................................................................... 376
30.1 What is a Safety Instrumented S ystem?

A Safety Instrumented System (SIS) is a set of components that includes sensors, Logic Solvers,
and final control elements whose purpose is to respond to dangerous plant conditions, which may
be hazardous. The Safety Instrumented System must generate the correct outputs to prevent the
hazard or reduce the consequences of the hazard.
A Safety Instrumented System (SIS) is a form of process control typically used in industrial
processes, such as those of Power Generation and Waste Water. The SIS performs specified
functions in order to maintain a safe state of a control process when any unacceptable process
conditions are detected.
A safe state is a state of the process operation where the hazardous event cannot occur. The
safe state should be achieved within one-half of the process safety time.
International standard IEC 61508 is a standard of rules applied to all types of industry. This
standard covers the complete safety life cycle, and has its origins in the process control industry
sector.
International standard IEC 61511 was published in 2003 to provide guidance to end-users on the
application of Safety Instrumented Systems in the process industries.
Refer to the Ovation Safety Instrumented System (SIS) User Guide for information about using
SIS with Ovation.
REF_1005
371
30.2 Functions of Ovation SIS
30.2 Functions of Ovation SIS

The Safety Instrumented System performs the following functions:
Implements a risk reduction strategy which is intended to reduce the likelihood of a hazardous
event causing a catastrophe in a plant.
Validates messages that are sent from Ovation workstations to the safety system. This
reduces the risk of sending invalid and perhaps unsafe messages to the SIS. This function is
known as SIS Write.
Manages the safety instrumented functions (SIFs) to provide a risk reduction strategy which is
intended to reduce the likelihood of a hazardous event. Each SIF defines:
Measurement sensors to use.
Actions to take.
When to apply the actions.
How fast to measure and react.
30.3 Limitations for Ovation SIS s ystem
372
COMPONENT
MAXIMUM
SISNet Repeater rings in a system
SISNet Repeater pairs in an Ovation SIS system
32
Logic Solvers per SIS Data Server
32 (simplex), 16 (redundant)
Logic Solvers in a SIS system
1024
Logic Solvers that can publish data globally on a SIS system
32
SIS control modules in a Logic Solver
Algorithms in a SIS control module
127
Secure parameters per Logic Solver
16
Non-Secure parameters per Logic Solver
24
Logic Solvers that can publish data globally on one SIS Data Server
8 (64 slots)
Secure parameters published globally per SIS system
512
SDS (SIS Data Server)
I/O channels
4096
SISLAN
LIMIT
REF_1005
30.4 Hardware components of Ovation SIS
30.4 Hardw are components of Ovation SIS

The SIS system contains various hardware components that are described in the following table.
Note: For information on installing switches and routers in your SIS system, refer to the
manufacturer's installation instructions.
Hardware components
HARDWARE COMP ONENT
DESCRIPTION
SIS carriers
Vertical or horizontal brackets that mount on the DIN rails in a cabinet and hold the
SIS Logic Solvers and terminal blocks.
Simplex terminal block
Interfaces between I/O devices and one Logic Solver.
Duplex terminal block
Interfaces between I/O devices and two Logic Solvers.
SIS Data Server
Provides the interface between the Ovation Controller and Logic Solvers and
SISNet Repeaters. The SIS Data Server can manage up to 32 Logic Solvers.
SIS Logic Solvers
Hardware modules that contain logic solving capability and provide an interface to
16 I/O channels.
SIS Net Repeaters
Provides communication between Logic Solvers that are connected to different SIS
Data Servers.
Fiber optic cable/ring
Used to permit one SISNet Repeater connected to a SIS Data Server to

communicate with another SISNet Repeater connected to a different SIS Data
Server.
Carrier Extender cables
Connects power and signals between 8-wide carriers.
SIS Net Distance Extender
Permits SISNet Repeaters to communicate over greater distances.
Power Supply
Provides power to the SIS Data Server.
REF_1005
373
30.4 Hardware components of Ovation SIS

The following graphic illustrates the SIS hardware components in a typical system.
374
REF_1005
30.5 Software components of Ovation SIS
30.4.1 Planning your hardware installation

The following list provides an overview of the basic SIS hardware installation. Refer to the specific
sections for installation details.
1. Install appropriate carriers on the DIN rails in a hardware cabinet.
2. Install terminal blocks onto a carrier.
3. Install the SIS Data Servers onto a carrier.
4. Install Logic Solvers onto the terminal block.
5. Connect the field wiring.
6. Install the SIS Net Repeaters.
7. Install extender cables.
8. Terminate the local bus.
9. Provide power to:
SIS Data Servers
SIS Logic Solvers.
SIS Net Repeaters.
SIS Net Extenders.
10. If desired, install auxiliary equipment.
30.5 Softw are components of Ovation SIS

SOFTWARE
LOCATION
OPERATING SYSTEM
INTERFACES
TO:
SIS Data Server
SIS Data Server
pSOS operating system
Ovation Controller
Interface to SIS
Data Server (CIS)
Ovation Controller
VxWorks operating system
Ovation SIS Write

Library
Engineering or Operator
Station
MS Windows
2003/XP/2008/Windows 7
CIS
Ovation SIS Engineering tools
Ovation SIS MMI Tools
Ovation SIS
Engineering Tools
Engineering station
MS Windows
CIS
SIS Write Server
Ovation SIS MMI

Tools
Operator Station
MS Windows
CIS
SIS Write Server
COMPONENT
REF_1005
Logic Solver (external)

Net Repeater (external)
CIS
Controller embedded software
(external)
SIS Data Server embedded
software
Ovation SIS Engineering tools
Ovation SIS MMI Tools
SIS Write Server
375
30.6 Ovation SIS Logic Solver algorithm table

Algorithms from the SIS family are not valid in control macros or standard control functions.
376
ALGORITHM
DESCRIPTION
FUNCTION
LSAI
Analog Input
Accesses a single analog measurement value and status from an I/O

channel. The input value is a transmitter's 4 to 20 mA signal.
LSALM
Alarm
Performs alarm detection on a user-specified input. The parameters

generated can then be used to generate alarm events at the user
interface.
LSAND
Logical AND
Generates a digital output value based on the logical AND of two to 16

digital inputs. The algorithm supports signal status propagation.
LSAVTR
Analog Voter
Monitors a number of input values and determines if there are enough

votes to trip. If a configured number of the inputs vote to trip, the algorithm
trips and sets the output of the algorithm to 0 (zero).
LSBDE
Bi-Directional Edge
Trigger
Generates a True (1) digital pulse output when the digital input makes a
positive (False-to-True) or negative (True-to-False) transition since the
last execution of the algorithm. The algorithm supports signal status
propagation.
LSBFI
Boolean Fan In
Generates a digital output based on the weighted binary sum, binary

coded decimal (BCD) representation, or logical OR of one to 16 digital
inputs. The algorithm supports signal status propagation.
LSBFO
Boolean Fan Out
Decodes a binary weighted input to individual bits and generates a digital

output value for each bit (as many as 16 outputs). The algorithm supports
signal status propagation.
LSCALC
Calculation/Logic
Allows you to specify an expression that determines the algorithm's

output. Mathematical functions, logical operators, constants and
parameter references can be used in the expression.
LSCEM
Cause Effect Matrix

(uses advanced
editor)
Defines interlock and permissive logic that associates as many as 16

inputs and 16 outputs. Configure one or more inputs to trip each output.
When an input becomes active, all outputs associated with that input trip.
LSCMP
Comparator
Compares two values and sets a Boolean output based on that

comparison.
LSDI
Digital Input
Accesses a single digital measurement value and status from a two-state

field device and makes the processed physical input available to other
algorithms. The algorithm supports signal inversion, signal filtering, signal
status propagation, and simulation.
LSDO
Digital Output
Takes a digital input value representing the commanded output state and
writes it to a specified Digital Output channel. The algorithm supports fault
state detection and field device confirmation.
LSDVC
Digital Valve
Controller
Drives a HART Two-state Output channel connected to a digital valve

controller. The algorithm supports partial stroke testing, fault state
detection, and field device confirmation.
LSDVTR
Digital Voter
Monitors a number of input values and determines if there are enough

votes to trip. If a configured number of the inputs vote to trip, the algorithm
trips and sets the output of the algorithm to 0 (zero).
LSLIM
Limit
Limits an input value between two reference values. The algorithm has
options that set the output to a default value or the last value if the input
becomes out of range.
REF_1005
ALGORITHM
DESCRIPTION
FUNCTION
LSMID
Middle Signal
Selector
Selects between multiple analog signals. The algorithm selects the midvalued input from the inputs that are not disabled and do not have Bad
status. If there is an even number of inputs, the average of the two middle
valued inputs is used as the middle value.
LSNAND
Logical NAND
Generates a digital output value based on the logical AND of two to 16

digital inputs, then performs a NOT on the result. The algorithm supports
LSNDE
Negative Edge
Trigger
negative (True-to-False) transition since the last execution of the
algorithm. The algorithm supports signal status propagation.
LSNOR
Logical NOR
Generates a digital output value based on the logical OR of two to 16

digital inputs, then performs a NOT on the result. The algorithm supports
LSNOT
Logical NOT
Logically inverts a digital input signal and generates a digital output value.
The algorithm supports signal status propagation.
LSOFFD
Off-Delay Timer
Delays the transfer of a False (0) digital input value to the output by a
specified time period. The algorithm supports signal status propagation.
LSOND
On-Delay Timer
Delays the transfer of a True (1) digital input value to the output by a
specified time period. The algorithm supports signal status propagation.
LSOR
Logical OR
Generates a digital output value based on the logical OR of two to 16

digital inputs. The algorithm supports signal status propagation.
LSPDE
Positive Edge
Trigger
positive (False-to-True) transition since the last execution of the algorithm.
The algorithm supports signal status propagation.
LSRET
Retentive Timer
Generates a True (1) digital output after the input has been True for a
specified time period. The elapsed time the input has been True and the
output value are reset when the reset input is set True.
LSRS
Reset/Set Flip-Flop
Generates a digital output value based on NOR logic of reset and set
inputs.
LSSEQ
Sequencer (uses
advanced editor)
Associates system states with actions to drive outputs based on the

current state.
LSSR
Set/Reset Flip-Flop
Generates a digital output value based on NAND logic of set and reset
inputs.
LSSTD
State Transition
Diagram (uses
advanced editor)
Implements a user-defined state machine. The state machine describes

the possible states, and the transitions between those states, that can
occur.
LSTP
Timed Pulse
Generates a True (1) digital output for a specified time duration when the
input makes a positive (False-to-True) transition. The output remains True
even when the input returns to its initial digital value and returns to its
original False value only when the output is True longer than the specified
time duration.
LSXNOR
Logical XNOR
Performs a NOT on the exclusive OR of two inputs.
LSXOR
Logical XOR
Performs an exclusive OR of two inputs to produce an output.
REF_1005
377
E C T I O N
31
31 Ovation hardware specification sheets
IN THIS SECTION
Cabinet specification sheets ........................................................................................... 380
Ovation workstation specification sheets ........................................................................ 393
Monitor specification sheets ............................................................................................ 402
Keyboard specification sheet .......................................................................................... 406
Printer specification sheets ............................................................................................. 408
Storage device specification sheets ................................................................................ 412
I/O module environmental specifications ........................................................................ 413
Analog Input module electrical specification sheets ....................................................... 414
Analog Output module electrical specification sheets..................................................... 426
Digital Input module electrical specification sheets ......................................................... 430
Digital Output module electrical specification sheets ...................................................... 444
Bus interface module electrical specification sheets....................................................... 452
Specialty module electrical specification sheets ............................................................. 454
Remote Function module electrical specification sheets ................................................ 471
Cable specification sheets .............................................................................................. 474
REF_1005
379
31.1 Cabinet specification sheets

Specifications for cabinets used in Ovation systems are described in the following sections:
EMC Rittal NEMA12 (4D33947) (see page 380).
Vented NEMA12 (5X00018) (see page 381).
Sealed NEMA12 (5X00019H01) (see page 382).
Vented NEMA12 (without mounting plate) (5X00020) (see page 384).
Vented NEMA12 (with mounting plate) (5X00127) (see page 385).
Sealed NEMA12 (O-shell) (5X00035H01/H03) (see page 387).
Sealed NEMA4 (O-shell) (5X00035H02/H04) (see page 388).
Vented NEMA12 (Front access only) (5X00068) (see page 391).
Sealed NEMA12 (1X00455) (see page 391).
Vented Ovation Workstation cabinet (1X000518) (see page 391).
Vented Ovation Server cabinet (1X000545) (see page 392).
31.1.1 EMC cabinet, NEMA12, Rittal (4D33947)
Weight (Empty cabinet) = 155 kg (341lb).
Dimensions (HxWxD) = 2000x600x600 mm (78x24x24 in).

4D33947H01 is a vented cabinet.
4D33947H02 is a sealed cabinet.
Operating Temperature and Storage Temperature.

See Cabinets (weight, dimensions, and temperatures).
380
Relative Humidity = 0 to 90%.
Operating Altitude = 2 km max (6561 ft max).
Ingress Protection Rating (EN60529/10.91) = 53 (4D33947H01); 55 (4D33947H02).
Pollution Degree/Install Category = 2/II
REF_1005
31.1.2 Cabinet vented, NEMA12 (5X00018)
Weight (Empty cabinet) = 136 kg (300 lb).

Operating Humidity = 0 to 95%.
Ingress Protection Rating (EN60529/10.91) = 53
REF_1005
381
31.1.3 Cabinet sealed NEMA12 (5X00019H01)

382
REF_1005
31.1.4 Cabinet sealed NEMA4 (5X00019H02)

REF_1005
383
31.1.5 Cabinet vented NEMA12 (without mounting plate) (5X00020)
Weight (Empty cabinet) = 115.6 kg (255 lb).

384
REF_1005
31.1.6 Cabinet vented NEMA12 (with mounting plate) (5X00127)

REF_1005
385
31.1.7 Cabinet vented, NEMA12 (5X00021)

5X00021H01 uses an O-shell marshalling plate.
5X00021H02 uses a standard marshalling plate.

386
REF_1005
31.1.8 Cabinet sealed, NEMA12 (5X00035H01/H03)

5X00035H01 uses an O-shell plate.
5X00035H03 uses a standard plate.

REF_1005
387
31.1.9 Cabinet sealed, NEMA4 (5X00035H02/H04)

5X00035H02 uses an O-shell plate.

388
REF_1005
31.1.10
Cabinet sealed, NEMA12 (5X00046H01)

REF_1005
389
31.1.11

See Cabinets (weight, dimensions, and temperatures.
390
REF_1005
31.1.12
Cabinet vented, NEMA12 (front access only) (5X00068)

31.1.13
Cabinet vented, NEMA12 (1X00454)

1X00454H01 uses a marshalling plate.

31.1.14
Cabinet sealed, NEMA12 (1X00455)

1X00455H01 uses marshalling plate.
1X00455H02 uses standard plate.

Ingress Protection Rating (EN60529/10.91) = 66 (NEMA 4); 55 (NEMA 12).
31.1.15
Cabinet vented (1X00518)
This cabinet can hold up to 6 Dell Tower workstations with 150 lbs maximum load rating per shelf.
Anti-tip angles made of heavy-gauge steel included with cabinet.
REF_1005
391
31.1.16
Cabinet vented (1X00545)
This cabinet can hold the Ovation Security Center (see page 367) components up to a static load
rating of 680 kg (1500 lb).
392
Anti-tip angles made of heavy-gauge steel included with cabinet.
REF_1005
31.2 Ovation workstation specification sheets
31.2 Ovation w orkstation specification sheets

Specifications for Ovation workstations are described in the following sections:
Engineering Station/Database Server.
Engineer Client Station/Operator Station/Virtual Controller.
Dell T300 Domain Controller or Terminal Server Host
Dell Poweredge T310 Domain Controller or Terminal Server Host Workstation (see page 393)
Dell Poweredge T310 Ovation Process Historian (see page 397)
Ovation Process Historian.
Ovation Process Historian (5X00456)
EDS Workstation (used in Smart Process applications) (see page 399).
Rack Mount Operator Station (see page 396).
Rack Mount Domain Controller (see page 394).
Rack Mount Process Historian (see page 398).
31.2.1 Dell Poweredge T310 Domain Controller or Terminal Server Host

Workstation (5X00487) (Windows Server 2008)
Dell Poweredge T310
Weight = 23.5 kg (52 lbs)
Dimensions (HxWxD) = 44 x 21.8 x 52.1 cm (17.3 x 8.6 x 20.5 in)
Operating Temperature = 10 to 35 C (50 to 95F)
Storage Temperature = -40 to 65 C (-40 to 149 F)
Operating Humidity = 20 to 80%
Storage Humidity = 20 to 85%
Operating Shock = 31 G
Storage Shock = 71 G
Operating Vibration = 0.26 G
Storage Vibration = 1.54 G
Operating Altitude = -16 to 3048 meters (-50 to 10,000 ft)
Storage Altitude = -16 to 10610 meters (-50 to 35,000 ft)
Input Voltage VAC = 100 to 240 VAC
Input Frequency Hz = 50 to 60 Hz
Input Current VAC = 5.8 amps @ 115 VAC;

2.9 amps maximum @ 230 VAC
Power Consumption = 164 watts
Heat Dissipation = 559.7 BTUs per hour
REF_1005
393
31.2.2 Dell Poweredge R710 Domain Controller/Database Server (Rack Mount)

(5X00462) (Windows Server 2008)
394
Dell Poweredge R710
Weight = 26 kg (57.5 lbs)
Dimensions (HxWxD) = 8.64 x 48.2 x 72 cm (3.4 x 19 x 28.4 in) with latches, pwr.supplies,
and bezel
Operating Temperature = 10 to 35 C (50 to 95 F)
Storage Temperature = -40 to 65C (-40 to 149 F)
Input Frequency Hz = 47 to 603Hz
Input Current = 7 amps @115 VAC:

3.5 amps @ 230 VAC
Heat Dissipation = 1945 BTUs per hour
REF_1005
31.2.3 Dell Precision T3500 Engineer / System Database Server (5X00557 for XP)
(5X00558 for Win7)
Dell Precision T3500 Workstation Mini Tower
Dimensions (HxWxD) = 45 x 18 x 47 cm (17.6 x 6.8 x 18.5 in)
Operating Vibration = 5 to 350 Hz at 0.0002 G /Hz
Storage Vibration = 5 to 500 Hz at 0.001 to 0.01 G /Hz
Maximum Current VAC = 6 amperes @ 115 VAC:

3 amperes @ 230 VAC
31.2.4 Dell Optiplex 990 Engineer Client Station/Operator Station/Virtual

Controller (XP) (5X00571)
Dell Optiplex 990 Mini Tower
Weight = 8.8 kg (19.5 lbs)
Operating Shock = Bottom half-sine pulse
Operating Altitude = -15.2 to 3048 meters (-50 to 10,000 ft)
Storage Altitude = -15.2 to 10668 meters (-50 to 35,000 ft)
Input Current = 5.0A max @ 115 VAC:

2.5A max @ 230 VAC
Power Consumption = 81.75 watts
REF_1005
395
31.2.5 Dell Optiplex 990 Engineer Client Station/Operator Station/Virtual

Controller (Windows 7) (5X00572)
Dell Optiplex 990 Mini Tower
Operating Shock = Bottom half-sine pluse
Input Current = 5.0A max @ 115 VAC:

2.5A max @ 230 VAC
31.2.6 Dell Precision R5400 Operator Station (XP) (Rack Mount) (5X00559)
396
Dell Precision R5400 Rack Mount Workstation
Weight = 21 kg (46 lbs)
Dimensions (HxWxD) = 8.6 x 44.4 x 68.5 cm (3.4 x 17.5 x 27 in)
REF_1005
31.2.7 Dell Precision R5400 Operator Station (Windows 7) (Rack Mount) (5X00461)
Dell Precision R5400 Rack Mount Workstation
Dimensions (HxWxD) = 8.6 x 44.4 x 68.5 cm (3.4 x 17.5 x 27 in)
31.2.8 Dell Poweredge T310 Server Ovation Process Historian (OPH) (5X00488)
(Windows Server 2008)
Dell Poweredge T310 Server Process Historian
Input Current VAC = 5.8 amps @ 115 VAC:

2.9 amps maximum @ 230 VAC
REF_1005
397
31.2.9 Dell Poweredge R710 Ovation Process Historian (Rack Mount) (5X00463)
(Windows Server 2008)
398
Dell Poweredge R710
Dimensions (HxWxD) = 864 x 482 x 720 mm (3.4 x 19 x 28.4 in) with rack latches, pwr.
supplies and bezel
Input Current = 7 amps @115 VAC:

3.5 amps @ 230 VAC
REF_1005
31.2.10
bit)
Dell Precision T5500n EDS Workstation (5X00569) (Windows 7) (64-
Dell Precision T5500 Windows 7 Workstation
Dimensions (HxWxD) = 448 x 173 x 468 mm (18 x 7 x 18 in)
Operating Shock = 40 G peak
Storage Shock = 105 G peak
31.2.11
Dell Precision T5500n EDS Workstation Linux Red Hat Enterprise
(5X00567)
Dell Precision T5500 EDS Workstation Linux Red Hat
Dimensions (HxWxD) = 448 x 173 x 468 mm (18 x 7 x 18 in)
Operating Shock = 40 G peak
Storage Shock = 105 G peak
REF_1005
399
31.2.12
400
Dell Poweredge R710 EDS Windows Server 2008 (5X00570)
Dell Poweredge R710 Windows 7 Rack Mounted Server / Workstation
Demenaions = 8.64 x 48.2 x 72 cm (3.4 x 19 x 28.4 in) w/rack latches, pwr. supplies, and
bezel.
Input Current = 3.1 A @115 VAC; 1.5 A @ 230 VAC
REF_1005
31.2.13
Dell Poweredge R710 EDS Linux Red Hat Enterprise (5X00568)
Dell Poweredge R710 Linux Rack Mounted Server / Workstation
Dimensions (HxWxD) = 8.64 x 48.2 x 72 cm (3.4 x 19 x 28.4 in) w/rack latches, pwr.
supplies, and bezel.
Input Current = 3.1 A @115 VAC; 1.5 A @ 230 VAC
REF_1005
401
31.3 Monitor specification sheets

Specifications for monitors are described in the following sections:
Dell 190S FP (19" monitor) (5X00473) (see page 403).
Dell 2007FP (20" monitor) (5X00310) (see page 404).
Dell U2410 (24" monitor) (5X00474) (see page 404).
NEC V321 (32" monitor) (5X00493) (see page 405).
NEC P401 (40" monitor) (5x00494) (see page 405).
NEC LCD461 (46" monitor) (5X00495) (see page 405).
402
REF_1005
31.3.1 Dell 190S FP (19" monitor) (5X00473)
Dimensions (HxWxD) = 493 x 410 x 182 mm (19.4 x 16.15 x 7.17 in) (extended)
Storage Temperature = -20 to 60 C (-4 to 140F)
Operating Altitude = 3048 m max (10,000 ft max)
Storage Altitude = 9144 m max (30,000 ft max)
Input Voltage VAC = 100 - 240 VAC
Input Frequency Hz = 47 to 63 HZ
Input Current = 1.5 amps maximum
Inrush Current = 30 A maximum @ 120V: 60 A maximum @240V
Heat Dissipation = 73.872 BTUs per hour typical operational
REF_1005
403
31.3.2 Dell 2007FP (20" monitor) (5X00310)
Dimensions (HxWxD) = 547x445x194 mm (extended):

(21.6x17.5x7.6 in)
Storage Temperature = 0 to 60 C (32 to 140F)
Operating Altitude = 3.7 km maximum (12000 ft)
Storage Altitude = 12.2 km maximum (40000 ft)
Input Current = 2.0 amps maximum
Inrush Current = 40 amps maximum @ 120V: 80 amps maximum @ 240V
Heat Dissipation = 187.6 BTUs per hour typical: 256 BTUs per hour maximum
31.3.3 Dell U2410 (24" monitor) (5X00474)
404
Weight = 9.57 kg (19.93 lbs)
Dimensions (HxWxD) = 493 x 560 x 202 mm (19.4 x 22 x 8 in)
Operating Altitude = 3658 meters (12,000 ft)
Storage Altitude = 12,192 meters (40,000 ft)
Input Current = 2 amps
REF_1005
31.3.4 NEC V321 (32" monitor) (5X00493)
Weight = 14.3 kg (31.5 lbs) (Without stand)
Dimensions (HxWxD) = 477 x 789 x 133 mm (19 x 31 x 5.3 in)
Operating Altitude = (9840 ft max) (0 to 3,000 M)
Input Current = 1.4A @ 100-120; 0.6A @ 220-240
Input Voltage VAC = 100-120; 220-240 VAC
Input Frequency Hz = 50/60 Hz
31.3.5 NEC P401 (40" monitor) (5X00494)
Weight = 24 kg (53 lbs) (Without stand)
Dimensions (HxWxD) = 532 x 920 x 140mm (21 x 36 x 5.5 in)
Operating Altitude = 3000 m max (9840 ft max)
31.3.6 NEC P461 (46" monitor) (5X00495)
Weight = 29 kg (63.9 lbs) (Without stand)
Dimensions (HxWxD) = 608x1055x140 mm (24x41.6x5.5 in)
Operating Altitude = 0 to 9,840 Feet (0 to 3,000M)
Input Voltage VAC = 100 to 240 VAC; 220 to 240 VAC
Input Current = 3.9A at 100 to120 VAC: 1.6A at 220 to 240 VAC
REF_1005
405
31.4 Keyboard specification sheet

Keyboards are typically provided for a workstation by the manufacturer of the workstation (for
example a Dell keyboard (Windows platform).
However, you can order an Ovation keyboard (also known as a membrane keyboard) from
Emerson. This keyboard is typically used by Operators at an Operator Station. You can program
this keyboard through the use of custom keys to perform special functions for the Operator.
Ovation Keyboard (see page 407).
406
REF_1005
31.4.1 Ovation Keyboard (4D33935)
Dimensions (HxWxD) = 42x508x229 mm (1.66x20x9 in)
Operating Humidity = 95%
Operating Altitude = 2 km max (6562 ft max)
Storage Altitude = 12.5 km max
REF_1005
407
31.5 Printer specification sheets

Specifications for printers used in Ovation systems are described in the following sections:
Color Laserjet Printer (see page 410)
Black and White Printer (see page 409)
Thermal Printer (see page 410)
Color Laserjet Printer
Color Alarm Printer (see page 410)
408
REF_1005
31.5.1 HP B/W Laserjet 5200 printer (5X00328)
Dimensions (HxWxD) = 403x490x599mm (1x19.3x24 in)
Storage Temperature = 0 to 40 C (-32 to 104 F)
Acoustical Noise = 54 dBA Printing: 31 dBA Idle
Input Voltage VAC = 90 to 140 VAC H06: 198 to 264 VAC H02
Input Current = 10 A at 120 VAC H01: 5 A at 230 VAC H02
REF_1005
409
31.5.2 HP Thermal/Inkjet 2800DTN printer (5X00243)
Dimensions (HxWxD) = 263x676x588 mm (10x26x23 in)
Operating Altitude = 3.1 km max (10,000 ft max)
Acoustical Noise = 6.2 B(A)
Input Current = 2.2 A
31.5.3 Okidata Microline 395C (5X00445)
Dimensions (HxWxD) = 177 x 419 x 572 mm (7.1 x 22.4 x 16.4 in)
Operating Humidity = 20 to 80% RH
Acoustical Noise = 58 dBA
Input Voltage VAC = 120 VAC (H01); 220 to 240 VAC (H02)
Power Consumption = 180 VA
31.5.4 HP Color Laserjet Enterprise CP4525n/4525dn (5X00520)
410
Dimensions (HxWxD) = 419x541x524 mm (17 x 22 x 21 in)
Storage Temperature = 0 to 35 C (32 to 95 F)
Input Voltage VAC = 110 to 127 VAC (H01 + H03); 220 to 240 VAC (H02 + H04)
REF_1005
31.5.5 HP Color Laserjet 5525 (5X00550)
Weight = 53.3 kg (117.3 lbs) (H01, H02, H04)
Weight = 84 kg (185 lbs) (H03)
Dimensions (HxWxD) = 465 x 544 x 586 mm (18 x 22 x 23 in) (H01, H02, H04)
Dimensions = (HxWxD) = 885 x 745 x 688 mm (35 x 29 x 27 in) (H03)
Storage Temperature = 0 to 35 C (32 to 95 F)
Input Voltage = 110 to 127 VAC (H01, H02, H03)
Input Voltage = 220 to 240 VAC (H04)
Heat Output = 2116 BTU/Hour
REF_1005
411
31.6 Storage device specification sheets
31.6 Storage device specification sheets

Specifications for storage devices used in Ovation systems are described in the following section:
RAID disk (see page 413).
412
REF_1005
31.7 I/O module environmental specifications
31.6.1 RAID SATA to iSCSI Media (5X00523)
Weight = 11.8 kg (26 lbs) without drives.
Input Voltage VAC = 115 VAC or 230 VAC
31.7 I/O module environmental specifications

All Ovation I/O modules have the same environmental specifications:
Electronics modules
Dimensions = (HxWxD) 155 x 127 x 54.6 mm (6 x 5 x 2.15 in)
Storage Temperature = -40 to 85C (-40 to 185F)
Humidity = 0 to 90% operating
Personality modules
Weight = 0.113 kg (0.25 lbs)
Dimensions = (HxWxD) 87.6 x 119.4 x 28 mm (3.45 x 4.7 x 1.1 in)
Storage Temperature = -40 to 85C (-40 to 185F)
Humidity = 0 to 90% operating
Relay Panels
Weight = 1 kg (2.3 lbs) G2R: 1.6 kg (3.6 lbs) Form C: 1.7 kg (3.8 lbs) Form X
Dimensions = (HxWxD) 114 x 422 x 125 mm (4.5 x 16.6 x 4.9 in)
Operating Temperature
G2R/KUEP Form X = 0 to 60 C (32 to 140 F)
KUEP Form C = 0 to 45 C (32 to 113 F)
Humidity
G2R = 35 to 85% operating
KUEP Form X and Form C = Not applicable
Cavity Inserts are inserts that fit into the Personality module position and provide a wiring
schematic for the module. An insert is only a space holder and not an actual module.
Note: Ovation I/O module power consumption figures are based on assumptions that the
Ovation power supply efficiency is 75%.
REF_1005
413
31.8 Analog Input module electrical specification sheets

Specifications for Ovation analog input modules are described in the following sections:
Analog Input 13 bit module (see page 415).
Analog Input 14 bit module (see page 418).
Analog Input 14 bit High Speed module (see page 419).
HART Analog Input module (see page 422).
HART Analog Input High Performance module (see page 423).
RTD Input module (4 channels) (see page 424).
RTD Input module (8 channels) (see page 425).
The heat dissipation values that are provided in the I/O module specification sheets are based on
the following:
An Ovation I/O module's Main heat dissipation specification (BTUs per hour) is the sum of
the following heat dissipation sources:
Module's heat dissipation due to the 24V power that it draws from the I/O cabinet Ovation
power supply's Main output.
I/O cabinet Ovation power supply heat dissipation due to the Main power that it supplies
to the I/O module (assumes a 75% efficient Ovation power supply).
An Ovation I/O module's Aux heat dissipation specification (BTUs per hour) is the sum of
Module's heat dissipation due to the Aux power that it draws from the I/O cabinet Ovation
power supply's Aux output.
Module's heat dissipation due to the power that it draws from an external power supply
located outside of the Ovation I/O cabinet.
I/O cabinet Ovation power supply heat dissipation due to the Aux power that it supplies to
the I/O module (assumes a 75% efficient Ovation power supply).
Note: See Ovation I/O Reference Manual for additional information.
414
REF_1005
31.8.1 Analog Input 13 bit module (legacy systems)

This module provides an interface to eight individually isolated analog inputs (channels) with
sampling rates of approximately 10 time/sec. Several voltage and current configurations are
available including cold junction compensation for thermocouple inputs.
Note: A ninth logical channel (does not connect to a device) is provided when a thermocouple is
used. This ninth point is needed for the CJ Compensation field of the Point Builder
Instrumentation tab when defining the eight other thermocouple points for the AI module.
The different range configurations are listed below:
20mV range uses 1C31113G01 (E) and 1C31116G01 (P) modules.

Main +24 Power (W) and VA (Typical) that module draws:
Draws from AC/DC Power Mains = 3.4 W/VA
Draws from AC/DC Power Supply = 2.5 W
AUX Power (W) and VA (Typical) = Not applicable
Main heat dissipation = 11.6 BTUs per hour
AUX heat dissipation = Not applicable for voltage input channels.
50mV range uses 1C31113G02 (E) and 1C31116G01 (P).

100mV range uses 1C31113G03 (E) and 1C31116G01 (P).

Draws from AC/DC Power Mains =3.4 W/VA
20mV Compensated (Thermocouple) range uses 1C31113G01 (E) and 1C31116G04 (P).
REF_1005
415

1VDC range uses 1C31113G04 (E) and 1C31116G01 (P).

AUX Power (W) and VA (Typical) =Not applicable

416
REF_1005


0-20 mA field powered range uses 1C31113G05 (E) and 1C31116G02 (P).
Note: 4-20 mA Field powered range can also be selected in the I/O Builder and the module will
be configured appropriately.
AUX heat dissipation = 0.41 BTUs per hour for field-powered mA channel (20mA). The
heat dissipation is not due to the 24V AUX power supply, but to the externally sourced
input current. Heat dissipated by the field powered AI input transmitters is outside the
0-20 mA locally powered range uses 1C31113G05 (E) and 1C31116G03 (P).
AUX Power (W) and VA (Typical) that module draws:
Draws from AC/DC Power Mains = 0.64 W/VA per locally powered channel (20mA).
Draws from AC/DC Power Supply = 0.48 W per locally powered channel (20mA).
Main heat dissipation = 11.6 BTUs per hour.
AUX heat dissipation = 0.96 BTUs per hour per locally powered mA channel (20mA).
Heat dissipated by the AI input transmitters is outside the cabinet and is not included.
REF_1005
417
31.8.2 Analog Input 14 bit module

This module provides an interface to eight individually isolated analog inputs (channels) with a
minimum sampling rate of 10 time/sec. A low cost 4-20 mA current input is available along with a
1V voltage input (legacy) configuration.
4-20 mA Field or Locally powered range uses 1C31224G01 (E) and 1C31227G01 (P).
Draws from AC/DC Power Mains = 0.64 W/VA per locally powered channel (20mA),
Not applicable for field-powered channels.
Draws from AC/DC Power Supply = 0.48 W per locally powered channel (20mA). Not
applicable for field-powered channels.
AUX heat dissipation = 0.41 BTUs per hour for field-powered channels (20mA). The heat
dissipation is not due to the 24V AUX power supply, but to the externally sourced input
current. Heat dissipated by AI input transmitters is outside the cabinet and is not included.
AUX heat dissipation = 0.96 BTUs per hour for locally-powered channels (20mA). Heat
dissipated by the AI input transmitters is outside the cabinet and is not included.
1 Volt range uses 1C31224G02 (E) and 1C31227G02 (P).

Legacy system
418
REF_1005
31.8.3 Analog Input 14 bit high speed module

This module provides an interface to eight individually isolated analog inputs (channels) with
sampling rates of medium speed (16/20 time/sec) or high speed (50/60 times/sec). Several
voltage and current input configurations are available including cold junction compensation for
thermocouple inputs.
4-20 mA Field or Locally powered range uses 5X00070G01 (E) and 1C31227G01 (P).
High Speed
Draws from AC/DC Power Mains = 0.64 W/VA per locally-powered channel (20mA)
Draws from AC/DC Power Supply = 0.48 W per locally-powered channel (20mA)
Not applicable for field-powered channels
AUX heat dissipation = 0.41 BTUs per hour for field-powered channels (20mA). The heat
current. Heat dissipated by the AI input transmitters is outside the cabinet and is not
included.
AUX heat dissipation = 0.96 BTUs per hour for locally-powered channels (20mA). Heat
100mV, 250mV, 1V range uses 5X00070G02 (E) and 1C31227G02 (P).

High Speed
5 V, 10V range uses 5X00070G03 (E) and 1C31227G02 (P).

High Speed
REF_1005
419
1 mA 2 wire local powered range uses 5X00070G02 (E) and 1C31116G03 (P).
High Speed
Draws from AC/DC Power Mains = 0.032 W/VA per locally-powered channel (1mA)
(24V)
Draws from AC/DC Power Supply = 0.024 W per locally-powered channel (1mA)
(24V)
AUX heat dissipation = 0.028 BTUs per channel (1mA). Heat dissipated by the AI input
transmitters is outside the cabinet and is not included.
1 mA 4 wire field powered range uses 5X00070G02 (E) and 1C31116G02 (P).
High Speed
AUX heat dissipation = 0.001 BTUs per channel (1mA). For field powered channels, the
heat dissipation is not due to the 24V AUX power supply, but to the externally sourced
input current. Heat dissipated by the field powered AI input transmitters is outside the
20mV, 50mV, 100V range uses 5X00070G04/5 (E) and 1C31116G04 (P).
Medium Speed
Temperature sensor for cold junction thermocouple compensation
20mV, 50mV, 100V range uses 5X00070G04 (E) and 1C31116G01 (P).
Medium Speed
420
REF_1005

REF_1005
421
31.8.4 HART Analog Input module

This module provides an interface for eight HART field devices with 4-20 mA current loop analog
inputs (common reference). In addition to the analog inputs, digital information can be exchanged
between HART compliant devices and controller.
4-20 mA loop powered (2 wire) or active source (4 wire) range uses 5X00058G01 (E) and
5X00059G01 (P).
Draws from AC/DC Power Mains = 1.6 W/VA.
Draws from AC/DC Power Supply = 1.2 W.
Draws from AC/DC Power Mains =2.4 W/VA (24V) + 0.64 W/VA per locally powered
channel (20mA).
Draws from AC/DC Power Supply = 1.8 W + 0.48 W per locally powered channel
(20mA).
AUX heat dissipation = 8.2 BTUs per hour plus 0.41 BTUs per hour for each fieldpowered channel plus 1.27 BTUs per hour for each locally-powered channel. For field
powered channels, the heat dissipation is not due to the 24V AUX power supply. Heat
dissipated by AI input transmitters is outside the cabinet and is not included.
422
REF_1005
31.8.5 HART High Performance Analog Input module

This module provides eight galvanically isolated 4-20 mA analog inputs (channels) with HART
transceivers. Each HART transceiver provides optically isolated communication to a dedicated
UART (Universal Asynchronous Receiver and Transmitter), thereby maximizing HART
communication throughput.
4-20 mA local powered or field powered transmitter interface range uses 5X00106G01/2
(E) and 5X00109G01 (P).
Draws from AC/DC Power Mains =0.64 W/VA per locally-powered channel (24V).
Draws from AC/DC Power Supply = 0.48 W per locally-powered channel (24V).
Not applicable for field-powered channels.
AUX heat dissipation = 0.41 BTUs per hour for field-powered channel (20mA). The heat
current. Heat dissipated by the field powered AI input transmitters is outside the cabinet
and is not included.
AUX heat dissipation = 0.96 BTUs per hour for locally-powered channel (20mA). Heat
REF_1005
423
31.8.6 RTD Input module (4 channel)

This module provides an interface to four Resistance Temperature Detectors (channels). Several
three- and four-wire RTD types are supported.
All ranges use 1C31161G01 (E) and 1C31164G01 (P).

All (for 50/60 Hz filtered inputs and CE Mark certified systems) ranges use 1C31161G02
(E) and 1C31164G02 (P).
424
REF_1005
31.8.7 RTD Input module (8 channel)

This module provides an interface to eight Resistance Temperature Detectors (channels).
Several three- and four-wire RTD types are supported.
All ranges use 5X00119G01/2 (E) and 5X00121G01 (P).

REF_1005
425
31.9 Analog Output module electrical specification sheets

Specifications for Ovation analog output modules are described in the following sections:
Analog Output module (see page 427).
HART Analog Output module (see page 428).
HART High Performance Analog Output module (see page 429).
the following:
426
REF_1005
31.9.1 Analog Output module (4 channels)

This module provides an interface to four individually isolated analog outputs (channels) using 12
bit digital to analog converters.
0-5 VDC range uses 1C31129G01 (E) and 1C31132G01 (P).

Draws from AC/DC Power Supply = 2 W
AUX Power (W) and VA (Typical) = Not applicable.
0-10 VDC range uses 1C31129G02 (E) and 1C31132G01 (P).

0-20 mA with Diagnostics range uses 1C31129G03 (E) and 1C31132G01 (P).
Note: 4-20 mA with diagnostics range can also be selected in the I/O Builder and the module
will be configured appropriately.
0-20 mA without Diagnostics range uses 1C31129G04 (E) and 1C31132G01 (P).
Note: 4-20 mA without diagnostics range can also be selected in the I/O Builder and the module
will be configured appropriately.
REF_1005
427
31.9.2 HART Analog Output module

This module provides an interface for eight HART field devices with 4-20 mA current loop analog
outputs (channels) (common reference). In addition to the outputs, digital information can be
exchanged between HART compliant devices and the Controller.
4-20 mA range uses 5X00062G01 (E) and 5X00063G01 (P).

Draws from AC/DC Power Mains =8 W/VA (24V)
Draws from AC/DC Power Supply = 6 W (24V)
AUX heat dissipation = 27.2 BTUs per hour.
428
REF_1005
31.9.3 HART High Performance Analog Output module

This module provides an interface for four HART field devices with 4-20 mA current loop analog
outputs (channels) (common reference). In addition to the outputs, digital information can be
exchanged between HART compliant devices and the Controller.
4-20 mA range uses 5X00167G01 (E) and molded plastic cavity insert 1X00188H01.
Note: A Personality module is not required in order to use the HART High Performance Analog
Output module. However, there may be requirements to use the Ovation Analog Output module
base unit terminal assignments for the actuator interface field wiring. In those cases, you must
use the 5X00170G01 HART High Performance Analog Output Personality module.
REF_1005
429
31.10 Digital Input module electrical specification sheets

Specifications for Ovation digital input modules are described in the following sections:
Digital Input module (see page 431).
Compact Digital Input module (see page 433).
Contact Input module (see page 435).
Compact Contact Input module (see page 436).
Sequence of Events Input module (see page 437).
Compact Sequence of Events Input module (see page 439).
Enhanced Sequence of Events Input module (see page 441).
the following:
430
REF_1005
31.10.1
Digital Input module (16 channels)
This module provides an interface for 16 digital inputs (channels). The following input
configurations are available: 24V, 48V, 125V Isolated Differential or Single Ended (common
return).
24/48 VAC/VDC Single-ended range uses 1C31107G01 (E) and 1C31110G01 (P).
Legacy system
Draws from AC/DC Power Mains =1.0 W/VA (24V): 2.0 W/VA (48V)
Draws from AC/DC Power Supply = 0.75 W (24V):1.5 W (48V)
AUX heat dissipation = 3.4 BTUs per hour (24V): 6.8 BTUs per hour (48V)
24/48 VAC/VDC Differential range uses 1C31107G01 (E) and 1C31110G02 (P).
Legacy system
Draws from AC/DC Power Mains = 1.0 W/VA (24V): 2.0 W/VA (48V)
Draws from AC/DC Power Supply = 0.75 W (24V): 1.5 W (48V)
125 VAC/VDC Single-ended range uses 1C31107G02 (E) and 1C31110G01 (P).
Legacy system
AUX Power (W) and VA (Typical) = Not applicable. It is assumed that the 125VAC/DC
power source is located outside the I/O cabinet.
AUX heat dissipation = 11.26 BTUs per hour. Heat dissipation is due solely to the I/O
module front-end circuit external power consumption.
REF_1005
431
125 VAC/VDC Differential range uses 1C31107G02 (E) and 1C31110G02 (P).
Legacy system
AUX Power (W) and VA (Typical) = Not applicable. It is assumed that the 125VAC/DC
module front-end circuit external power consumption.
Note: When the 125VAC/VDC Digital Input Emod (1C31107G02) is used in applications with
the unfused differential Pmod (1C31110G02), external fusing or other current limiting devices
are recommended on the hazardous inputs to provide protection to the external wiring and
power source.
CAUTION! For CE Mark certified systems, any base unit that contains a 125VAC/DC Digital
Input Electronics module (1C31107G02) with a Differential Digital Input Personality module
(1C31110G02) and interfaces to hazardous voltage (>30 V RMS, 42.4 V peak, or 60 VDC)
must include a hazardous voltage warning label (1B30025H01) on that base unit.
Any base unit that contains a 125VAC/DC Digital Input Electronics module (1C31107G02) with
a Single-ended Digital Input Personality module (1C31110G01) and interfaces to hazardous
voltage (>30 V RMS, 42.4 V peak, or 60 VDC) must include a hazardous voltage warning label
(1B30025H01) on ALL base units on the branch.
Place this label in a visible location on the base unit, preferably above the spare fuse location.
The project drawings must indicate this.
432
REF_1005
31.10.2
Compact Digital Input module
This module provides a low cost interface for 16 digital inputs (channels) by eliminating the need
for a Pmod. The following input configurations are available: 24V, 48V, 125 Isolated Differential or
Single Ended (common return). If desired, a Pmod can be added to individually fuse inputs (with
common return).
24/48 VDC Single-ended range uses 1C31232G01 (E) and Cavity Insert 1C1238H01.
24/48 VAC/VDC Differential range uses 1C31232G02 (E) and Cavity Insert 1C1238H01.
24/48 VAC/VDC Individually fused range uses 1C31232G02 (E) and 5X00034G01 (P)
REF_1005
433
125 VAC/VDC Differential range uses 1C31232G03 (E) and Cavity Insert 1C1238H01.
AUX Power (W) and VA (Typical) = Not applicable. It is assumed that the 125 VAC/VDC
module font-end circuit external consumption.
125 VAC/VDC Individually fused range uses 1C31232G03 (E) and 5X00034G01 (P)
AUX Power (W) and VA (Typical) = Not applicable. It is assumed that the 125 VAC/VDC
module font-end circuit external consumption.
Note: When the 125VAC/VDC Compact Digital Input Emod (1C31232G03) is used in
applications without the Fused Pmod (5X00034G01), additional external fusing or other current
limiting devices are recommended on the hazardous inputs to provide additional protection to
the external wiring and power source.
434
REF_1005
31.10.3
Contact Input module
This module provides an interface for 16 digital contact inputs (channels) with common return. A
+48V on-board power supply provides current limited contact wetting.
48 VDC On-card wetting supply range uses 1C31142G01 (E) and 1C31110G03 (P).
Legacy system
REF_1005
435
31.10.4
Compact Contact Input module
This module provides a low cost interface for 16 digital contact inputs with common return by
eliminating the need for a Pmod. A +48V on-board power supply provides current limited contact
wetting.
48 VDC On-card wetting supply range uses 1C31234G01 (E) and molded plastic cavity
insert 1C31238H01
436
REF_1005
31.10.5
Sequence of Events Digital Input module
This module provides an interface for 16 digital inputs (channels) with time tagging information to
within 125 s. An event tagging mask and filters to reject state changes and input chatter are
provided along with time synchronization to the Controller with 1 ms resolution. Several input
configurations are available.
24/48 VDC Single-ended range uses 1C31157G01 (E) and 1C31110G01 (P)
Legacy systems
24/48 VDC Differential range uses 1C31157G01 (E) and 1C31110G02 (P)
Legacy system
Draws from AC/DC Power Mains =1.5 W/VA (24V): 3.0 W/VA (48V)
125 VDC Single-ended range uses 1C31157G02 (E) and 1C31110G01 (P)
Legacy system
AUX Power (W) and VA (Typical) = Not applicable. It is assumed that the 125 DC power
source is located outside the I/O cabinet.
module font-end external 125VDC power consumption.
REF_1005
437
125 VDC Differential range uses 1C31157G02 (E) and 1C31110G02 (P)
Legacy system
AUX Power (W) and VA (Typical) = Not applicable. It is assumed that the 125 DC power
module font-end external 125VDC power consumption.
48 VDC On-card Wetting Supply range uses 1C31157G03 (E) and 1C31110G03 (P)
Legacy system
Note: When the 125VDC Sequence of Events Digital Input Emod (1C31157G02) is used in
applications with the unfused differential Pmod (1C31110G02), external fusing or other current
limiting devices are recommended on the hazardous inputs to provide protection to the external
wiring and power source.
438
REF_1005
31.10.6
Compact Sequence of Events Digital Input module
This module provides a low cost interface for 16 digital inputs (channels) with time tagging
information to within 125 s. An event tagging mask and filters to reject state changes and input
chatter is provided along with time synchronization to the Controller with 1 ms resolution. Several
input configurations are available. If desired, a Pmod can be added to individually fuse some
digital inputs (with common return).
24/48 VDC Single-ended range uses 1C31233G01 (E) and Cavity Insert 1C1238H01.
24/48 VDC Differential range uses 1C31233G02 (E) and Cavity Insert 1C1238H01.
24/48 VDC Individually fused range uses 1C31233G02 (E) and 5X00034G01 (P)
Draws from AC/DC Power Mains =0.88/VA (24V): 2.27 W/VA (48V)
Draws from AC/DC Power Supply = 0.66 (24V):1.70 W (48V)
REF_1005
439
125 VDC Differential range uses 1C31233G03 (E) and Cavity Insert 1C1238H01.
AUX Power (W) and VA (Typical) = Not applicable. It is assumed that the 125 VDC power
module front-end circuit external consumption.
125 VDC Individually fused range uses 1C31233G03 (E) and 5X00034G01 (P)
module front-end circuit external consumption.
48 VDC On-card wetting range uses 1C31233G04 (E) and Cavity Insert 1C1238H01.
Note: When the 125VDC Compact Sequence of Events Digital Input Emod (1C31233G03) is
used in applications without the Fused Pmod (5X00034G01), additional external fusing or other
current limiting devices are recommended on the hazardous inputs to provide additional
protection to the external wiring and power source.
440
REF_1005
31.10.7
Enhanced Compact Sequence of Events Digital Input module (16
channels)
This module provides a low cost interface for 16 field inputs. The module performs a digital debounce on these 16 field input signals in order to obtain the present input state data. The present
input state data will be placed in the module's I/O bus Present Input State register. Using the
present input state data, the module calculates the event change of state information and status
information for the I/O bus.
24/48 VDC Single-ended range uses 5X00357G01 (E) and Cavity Insert 1C1238H01 (FDJ
field card)
24/48 VDC Differential range uses 5X00357G02 (E) and Cavity Insert 1C1238H01 (FDI field
card).
24/48 VDC Single-ended range uses 5X00357G02 (E) and 5X00034G01 (P) (FDI field card).
REF_1005
441

125 VDC Differential range uses 5X00357G03 (E) and Cavity Insert 1C1238H01 (FDI field
card).
AUX Power (W) and VA (Typical) = Not applicable. It is assumed that the 125VDC power
AUX heat dissipation = 6.4 BTUs per hour
Heat dissipation is due solely to the I/O module front-end circuit external consumption.
125 VDC Single-ended range uses 5X00357G03 (E) and 5X00034G01 (P) (FDI field card).
AUX Power (W) and VA (Typical) = Not applicable. It is assumed that the 125VDC power
Heat dissipation is due solely to the I/O module front-end circuit external consumption.
48 VDC Single-ended range uses 5X00357G04 (E) and Cavity Insert 1C1238H01 (FCI field
card).
24 VDC Differential range uses 5X00357G05 (E) and Cavity Insert 1C1238H01 (FDW field
card).
IEC 61131-2 compliant
442
REF_1005

24 VDC Single-ended range uses 5X00357G05 (E) and 5X00034G01 (P) (FDW field card).
IEC 61131-2 compliant
Note: When the 125VDC Enhanced Compact Sequence of Events Digital Input Emod
(5X00357G03) is used in applications without the Fused Pmod (5X00034G01), additional
external fusing or other current limiting devices are recommended on the hazardous inputs to
provide additional protection to the external wiring and power source.
REF_1005
443
31.11 Digital Output module electrical specification sheets
31.11 Digital Output module electrical specification sh eets

Specifications for Ovation digital output modules are described in the following sections:
Digital Output modules (see page 445).
High Side Digital Output module (24VDC) (see page 449).
Relay Output modules (see page 450).
the following:
444
REF_1005
31.11.1
Digital Output module electrical (16 channels)
This module provides an interface to 16 single-ended digital outputs (channels). Five to 60 VDC
loads up to 500 mA each can be controlled. (Total load current is limited by module fuse current
rating.) This module can also be used to interface KUEP, G2R, and solid state relay panels for
increased output current switching capability.
Relay panels increase switching capabilities for digital output modules.
0 to 60 VDC Single-ended direct range uses 1C31122G01 (E) and 1C31125G01 (P).
No relay panel
Main +24 Power that module draws:
AUX Power that module draws:
Draws from AC/DC Power Mains = 25.6 W/VA (24V) (8 outputs on @100 mA each):
51.2 W/VA (48V) (8 outputs on @100 mA each)
Draws from AC/DC Power Supply = 19.2 W (24V) (8 outputs on @100 mA each):
38.4 W (48V) (8 outputs on @100 mA each)
AUX heat dissipation = 22.71 BTUs per hour (24V): 44.56 BTUs per hour (48V). Loads
are located outside the Ovation I/O cabinet. Load heat dissipation is not included. Eight
outputs on @100 mA each.
24 VDC Solid State Style Relay Panel Interface uses 1C31122G01 (E) and 1C31125G02
(P) local Aux power.
5A22410G01 Solid State Relay Panel - AC contacts
OR
5A22410G02 Solid State Relay Panel - DC contacts
AUX Power that module and relay panel draws:
Draws from AC/DC Power Mains = 7.87 W/VA (24V) (16 outputs on)
Draws from AC/DC Power Supply = 5.9 W (24V) (16 outputs on)
AUX heat dissipation = 26.8 BTUs per hour (24V) (16 outputs on, relay panel located
inside cabinet)
6.90 BTUs per hour (24V) (16 outputs on, relay panel located outside cabinet and its heat
dissipation is not included)
REF_1005
445
24 VDC Solid State Relay Panel Interface uses 1C31122G01 (E) and 1C31125G03 (P)
external 24 V power.
5A22410G01 Solid State Relay Panel - AC contacts
or
5A22410G02 Solid State Relay Panel - DC contacts
Not applicable
inside cabinet)
24 VDC G2R Relay Panel Interface uses 1C31122G01 (E) and 1C31125G02 (P) local Aux
power.
5A22411G01 G2R Panel (16 relays)
Draws from AC/DC Power Mains = 14.5 W/VA (24V) (16 outputs on)
Draws from AC/DC Power Supply = 10.87 W (24V) (16 outputs on)
inside cabinet)
12.72 BTUs per hour (24V) (16 outputs on, relay panel located outside cabinet and its
heat dissipation is not included)
24 VDC G2R Relay Panel Interface uses 1C31122G01 (E) and 1C31125G03 (P) external 24
V power.
5A22411G01 G2R Panel (16 relays)
Main +24 Power that module and relay panel draws:
Not applicable
446
REF_1005

inside cabinet)
24 VDC KUEP Form C Relay Panel Interface uses 1C31122G01 (E) and 1C31125G02 (P)
local Aux power.
5A22412G01 KUEP Form C Panel (1 or 2 panels) (8 relays per panel)
AUX Power that module and relay panel(s) draws:
Draws from AC/DC Power Mains = 21.12 W/VA (24V) (1 panel, 8 outputs on)
Draws from AC/DC Power Mains = 42.24 W/VA (24V) (2 panels, 16 outputs on)
Draws from AC/DC Power Supply = 15.84 W (24V) (1 panel, 8 outputs on)
Draws from AC/DC Power Supply = 31.68 W (24V) (2 panels, 16 outputs on)
AUX heat dissipation = 72.06 BTUs per hour (24V) (1 panel, 8 outputs on, relay panel
located inside cabinet)
144.12 BTUs per hour (24V) (2 panels, 16 outputs on, relay panel located inside cabinet)
18.53 BTUs per hour (24V) (1 panel, 8 outputs on, relay panel located outside cabinet
and its heat dissipation is not included)
37.16 BTUs per hour (24V) (2 panels, 16 outputs on, relay panel located outside cabinet
24 VDC KUEP Form C Relay Panel Interface uses 1C31122G01 (E) and 1C31125G03 (P)
5A22412G01 KUEP Form C Panel (1 or 2 panels) (8 relays per panel)
Not applicable
located inside cabinet)
109.21 BTUs per hour (24V) (2 panels, 16 outputs on, relay panel located inside cabinet)
0.51 BTUs per hour (24V) (1 panel, 8 outputs on, relay panel located outside cabinet and
its heat dissipation is not included)
REF_1005
447
24 VDC KUEP Form X Relay Panel Interface uses 1C31122G01 (E) and 1C31125G02 (P)
local Aux power.
5A22412G02 KUEP Form X Panel (1 or 2 panels) (8 relays per panel).
Draws from AC/DC Power Mains = 15.04 W/VA (24V) (1 panel, 8 outputs on)
Draws from AC/DC Power Mains = 30.08 W/VA (24V) (2 panels, 16 outputs on)
Draws from AC/DC Power Supply = 11.28 W (24V) (1 panel, 8 outputs on)
Draws from AC/DC Power Supply = 22.56 W (24V) (2 panels, 16 outputs on)
located inside cabinet).
102.63 BTUs per hour (24V) (2 panels, 16 outputs on, relay panel located inside cabinet).
13.18 BTUs per hour (24V) (1 panel, 8 outputs on, relay panel located outside cabinet
and its heat dissipation is not included).
24 VDC KUEP Form X Relay Panel Interface uses 1C31122G01 (E) and 1C31125G03 (P)
5A22412G02 KUEP Form X Panel (1 or 2 panels) (8 relays per panel).
Not applicable
located inside cabinet).
77.72 BTUs per hour (24V) (2 panels, 16 outputs on, relay panel located inside cabinet).
0.35 BTUs per hour (24V) (1 panel, 8 outputs on, relay panel located outside cabinet and
its heat dissipation is not included).
448
REF_1005
31.11.2
High Side Digital Output module (24VDC)
This module is an intelligent microcontroller-based digital output module. This module consists of
two modules, (electronics and personality), that are inserted into an Ovation I/O module base unit.
The HSDO module contains 16 optically isolated digital output channels. Each digital output
channel is capable of sourcing up to 500 mA of output current.
24 VDC range uses 5X00270G01 (E) and 5X00273G01 (P).

No relay panel.
Draws from AC/DC Power Mains = 64 W/VA (24V).
Draws from AC/DC Power Supply = 48 W (24V).
AUX heat dissipation = 13.65 BTUs per hour.
Note: For auxiliary power:

Module standard configuration employs an external +24 VDC power supply for field power and
does not use auxiliary power. You may optionally use auxiliary power to provide module field
power, but then the module allowable maximum total load current is reduced to 2 A.
Assume eight outputs on and eight outputs off with the on outputs supplying 250 mA each.
REF_1005
449
31.11.3
Relay Output module electrical
This standalone module has its own Electronics module and does not require a Digital Output
module (1C31122G01) for operation.
This module provides an interface to either 12 KUEP relay or 16 G2R relay outputs (channels).
Special relay bases connect directly to the Ovation I/O branches and house the Relay Output
Electronics module and relays.
Relay output modules do not use standard Ovation I/O bases and do not use Personality
modules.
the following:
Relay Output ( 12 KUEP Relays Form C) uses 1C31219G01 (E) and 1C31222G01 (Base
unit).
Use with Relay Panel Kit 5A26458G01
Draws from AC/DC Power Mains = 2.54 W/VA (module)
Draws from AC/DC Power Supply = 1.88 W (module)
Draws from AC/DC Power Mains = 0.39 W/VA module (24V) + 31.66 W/VA (24V) (12
relays) = 32.05 W/VA
Draws from AC/DC Power Supply = 0.29 W module (24V) + 23.45 W (24V) (12
relays) = 23.74 W
AUX heat dissipation = 1.33 BTUs per hour (module) + 108 BTUs per hour (12 relays) =
109.33 BTUs per hour
450
REF_1005
Relay Output (12 KUEP Relays Form X) uses 1C31219G01 (E) 1C31222G01 (Base unit).
relays) = 21.85 W/VA (24V)
Draws from AC/DC Power Supply = 0.29 W module (24V) + 15.9 W (24V) (12 relays)
= 16.19 W
AUX heat dissipation = 1.33 BTUs per hour (module) + 73.22 BTUs per hour (12 relays) =
74.55 BTUs per hour
Relay Output (16 G2R Relays) uses 1C31219G01 (E) 1C31223G01 (Base unit).
relays) = 12.69 W/VA (24V)
Draws from AC/DC Power Supply = 0.29 W module (24V) + 9.1 W (24V) (12 relays) =
9.39 W
AUX heat dissipation = 1.33 BTUs per hour (module) + 42 BTUs per hour (12 relays) =
43.33 BTUs per hour
REF_1005
451
31.12 Bus interface module electrical specification sheets

Specifications for Ovation bus interface modules are described in the following sections:
Foundation Fieldbus module (see page 452).
Profibus module (see page 453).
DeviceNet module (see page 453).
Ethernet Link Controller module (see page 453).
the following:
31.12.1
Foundation Fieldbus module (2 channels)
This module provides an interface to Fieldbus devices through an Ovation I/O bus.
The module uses 5X00301G01 (E) and 5X00327G01 (P).

Draws from AC/DC Power Mains =0.55 W/VA per channel (24V)
Draws from AC/DC Power Supply = 0.41 W per channel (24V)
Aux heat dissipation = 1.88 BTUs per hour per channel.
452
REF_1005
31.12.2
Profibus module (2 channels)
This module provides an interface to Profibus devices through an Ovation I/O bus.
The module uses 5X00300G01 (E) and 5X00321G01 (P).

Aux heat dissipation = Not applicable
31.12.3
DeviceNet module (2 channels)
This module provides an interface to DeviceNet networks through an Ovation I/O bus.
The module uses 5X00376G01(E) and 5X00375G01 (P).

Draws from AC/DC Power Mains =0.77 W/VA per channel (24V)
Draws from AC/DC Power Supply = 0.56 W per channel (24V)
Aux heat dissipation = 2.63 BTUs per hour per channel
31.12.4
Ethernet Link Controller module (1 channel)
This module provides an interface to a single Ethernet link.
The module uses 5X00419G01(E) and 1X00569G01 (Cavity insert).

Aux heat dissipation = Not applicable
REF_1005
453
31.13 Specialty module electrical specification sheets

Specifications for Ovation specialty modules are described in the following sections:
Link Controller module (see page 455).
Loop Interface module (Normal Drive) (see page 456).
Loop Interface module (Electric Drive) (see page 460).
Pulse Accumulator module (see page 463).
Servo Driver (see page 465).
Speed Detector module (see page 467).
Valve Positioner module (see page 468).
SLIM (Small Loop Interface Module) module (see page 470).
the following:
454
REF_1005
31.13.1
Link Controller module
This module provides a serial RS232, RS422, or RS485 data communications link to a third-party
device or system. The module provides one serial port channel that is able to handle many points.
In order to use this module, the appropriate SLC algorithm must reside in the Ovation Controller.
(Refer to Ovation Algorithms Reference Manual.)
RS232 range uses 1C31166G01 (E) and 1C31169G01 (P)

RS485/RS422 four wire range uses 1C31166G01 (E) and 1C31169G02 (P)
REF_1005
455
31.13.2
Loop Interface module (normal non-electric drive)
This module provides an interface to the analog and digital I/O needed to control a single process
loop (up to 2 AI, 1 AO, 2 DI, 2 DO). In addition, the loop interface can display the process
information and provide for manual control via a local operator interface station (SLIM).
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE
0-10V Analog Inputs/Output

2
0-10V AI/AO - user defined Digital Inputs
6
6
1C31174G0
1C31174G21
1C31177G01
1C31177G01
0-5V Analog Inputs, 0-10V Analog Output

0-5V AI, 0-10V AO - user defined Digital Inputs2
6
6
1C31174G02
1C31174G22
1C31177G01
1C31177G01
The ranges listed above have the following specifications:

AUX Power (W) and VA (Typical)
Digital Inputs = 0.18 W/VA (24V): 0.36 W/VA (48V)
Digital Outputs = 6.4 W/VA (24V): 12.8 W/VA (48V)
100 mA per output
AUX heat dissipation
Digital Inputs = 0.6 BTUs per hour (24V): 1.2 BTUs per hour (48V)
Digital Outputs = 5.6 BTUs per hour (24V): 11 BTUs per hour (48V)
Two outputs on 100 mA per output
Loads are outside cabinet and their heat dissipation is not included.
4-20mA AI/AO Locally powered analog inputs
1C31174G03
1C31177G02
4-20mA AI/AO Field powered analog inputs
1C31174G03
1C31177G03
1C31174G23
1C31177G02
1C31174G23
1C31177G03

456
REF_1005
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE

100 mA per output
Analog Inputs = Local powered current (20mA per input) 1.28 W/VA (24V)
100 mA per output
Analog Inputs = (20mA per input) 1.78 BTUs per hour (24V)
When defining points for a normal (non-electric) drive Loop Interface module, the following point types are
required for each channel:
I/O
Channel
Name
Type
Input Source or Output

Destination
Terminal Block
Connection
Raise Runback or user2

defined
Input
Loop Interface Module
DI1
Lower Runback or user2

defined
Input
DI2
User Defined
Output
DO1
User Defined
Output
DO2
Process Variable
(dedicated)
Input
AI1
Process Position
Input
AI2
None
Output
Output
AO
Two additional channels are used at Emod Revision 5 or higher and are discussed below:
REF_1005
Controller Process
Variable
Output
Analog - No Terminations
Controller Setpoint
Output
457
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE
This module controls ONE process loop. To use this module, the MASTATION algorithm must reside in the
Ovation Controller. (See Ovation Algorithm Reference Manual.)
2
Raise and Lower Runback inputs can be disabled and used as user-defined input points. Configuration
instructions are included in Kit 1C31174G20.
3
This output may not appear on the termination list, but must be terminated for proper operation.
Electric Drive Modules

4-20mA Inputs; No Output Locally powered analog
inputs
1C31174G04
1C31177G02
4-20mA Inputs; No Output Field powered analog

inputs
1C31174G04
1C31177G03
4-20mA Inputs; No Output - user defined Digital

2
Inputs
1C31174G24
1C31177G02
1C31174G24
1C31177G03

2
Inputs

When defining points for an electric drive Loop Interface module, the following point types are required for each
channel:
I/O Channel
Name
Raise Runback or user-defined
Lower Runback or user-defined
Type
Input Source or
Output
Destination
Terminal
Block
Connection
Input
Loop Interface
Module
DI1
Input
Loop Interface
Module
DI2
3
None
Output Raise Pulse (dedicated)
Output
Loop Interface
Module
DO1
None
Output Lower Pulse (dedicated)
Output
Loop Interface
Module
DO2
Process Variable (dedicated)
Input
Loop Interface
Module
AI1
Process Position (dedicated)
Input
Loop Interface
Module
AI2
None
Output
Output
Output is compared
to Process Position.
Raise/Lower pulses
are generated as
applicable.
None
458
Controller Process Variable
Output
Analog - No
Terminations
Controller Set Point
Output
Analog - No
Terminations
REF_1005
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE
2
3
REF_1005
459
31.13.3
Loop Interface module (electric drive)
This module provides an interface to the analog and digital I/O (6 channels) needed to control one
process loop (up to 2 AI, 1 AO, 2 DI, 2 DO). In addition, the loop interface can display the process
information and provide for manual control via a local operator interface station (SLIM).
In order to use this module, the MASTATION algorithm must reside in the Ovation Controller.
(Refer to Ovation Algorithms Reference Manual.)
RANGE
CHANNELS
4-20mA Inputs; No Output Locally powered analog

inputs
4-20mA Inputs; No Output Field powered analog inputs
ELECTRONIC
MODULE
PERSONALITY
MODULE
1C31174G04
1C31177G02
1C31174G04
1C31177G03
1C31174G24
1C31177G02
1C31174G24
1C31177G03

2
Inputs
2
Inputs
460
REF_1005
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE

100 mA per output
Analog Inputs = Local powered current (20mA per input) 1.28 W/VA (24V)
100 mA per output
Analog Inputs = (20mA per input) 1.78 BTUs per hour (24V)
When defining points for an electric drive Loop Interface module, the following point types are required for each
channel:
I/O
Channel
Name
Type

Destination
Terminal
Block
Connection
Raise Runback or user-defined
Input
DI1
Lower Runback or user-defined
Input
DI2
None
Output Raise Pulse (dedicated)
Output
DO1
None
Output Lower Pulse (dedicated)
Output
DO2
Process Variable (dedicated)
Input
AI1
Process Position (dedicated)
Input
AI2
None
Output
Output
Output is compared to
Process Position.
Raise/Lower pulses are
generated as applicable.
None
3
3
REF_1005
Controller Process Variable
Output
Controller Set Point
Output
461
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE
2
3
462
REF_1005
31.13.4
Pulse Accumulator module
This module counts the pulse for up to two input channels and provides the information to the
Controller. The pulse accumulator may be used to:
Count over a defined time period to measure speed (frequency).
Count until instructed to stop.
Used to measure the duration of a pulse.
To use this module, the algorithm RPACNT or RPAWIDTH must reside in the Ovation Controller.
(See Ovation Algorithm Reference Manual.)
COUNT INPUT LEVEL
CONTROL (ENABLE AND

SNAPSHOT) INPUT LEVEL
24/48 V Medium Speed
Local field pwr. neg. cmn.
Local field pwr. pos. cmn.
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE
1C31147G01
1C31150G01
1C31147G01
1C31150G02
Ext. field pwr. pos. or

neg. cmn.
Ext. field pwr. pos. or neg.

cmn.
1C31147G01
1C31150G03
5/12 V Medium Speed

2
2
2
1C31147G01
1C31147G01
1C31147G01
1C31150G01
1C31150G02
1C31150G03

cmn.

Both count inputs = 50% duty cycle.
0.23 W/VA (24V)
0.47 W/VA (48V)
Both count inputs = 50% duty cycle.
0.78 W/VA (24V)
1.6 W/VA (48V)
5 V High Speed
REF_1005

1C31147G02
1C31150G01
1C31147G02
1C31150G02

common
1C31147G02
1C31150G03
463
COUNT INPUT LEVEL
CONTROL (ENABLE AND

SNAPSHOT) INPUT LEVEL
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE

Main +24 Power (W) and VA (Typical) = 2.2 W/VA
Both high speed count inputs = 50% duty cycle.
0.68 BTUs per hour
464
REF_1005
31.13.5
Servo Driver module
This module provides an interface to an electro-hydraulic servo actuator (servo-motor) used to

control a steam turbine.
RANGE
CHANNELS
16 Volts DC to a DC LVDT
ELECTRONIC
MODULE
PERSONALITY
MODULE
1C31199G01
1C31201G01
1C31199G02
1C31201G02
1C31199G03
1C31201G02


AUX heat dissipation = Not applicable
REF_1005
465
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE

AUX heat dissipation = Not applicable
When using the Point Builder to define points for a Servo Driver module, only the following point types are valid
for each channel:
1
2
466
I/O
Channel
Name
Type
Input Source or
Output Destination
Terminal Block
Connection 2
Position Feedback (Device 1)
Input
Servo Driver
N/A
Position Feedback (Device 2)
Input
Servo Driver
N/A
Raw Demodulator Voltage (Device

1)
Input
Servo Driver
N/A
Raw Demodulator Voltage (Device

2)
Input
Servo Driver
N/A
Demand (Device 1)
Output
Controller
N/A
Demand (Device 2)
Output
Controller
N/A
This module interfaces to, and provides position control for, two Electro-Hydraulic (EH) actuators in the field.
The terminal block connection depends upon the application being used. Refer to wiring diagrams.
REF_1005
31.13.6
Speed Detector module
This module provides the Controller with frequency measurements of a sinusoidal or pulse train
tachometer. A 16 bit output can be updated at a rate of 5 ms for over-speed detection, and a 32
bit output can be updated at a variable rate for speed regulation.
This module interfaces to one speed sensor to determine the rotation speed of a field device.
RANGE
CHANNELS
16 bit speed (Low Res)
ELECTRONIC
MODULE
PERSONALITY
MODULE
1C31189G01
1C31192G01
1C31189G01
1C31192G01
200 Hz min - 51200 Hz max

32 bit speed (High Res)
0.72 Hz min - 65535 Hz max

When using the Point Builder to define points for a Speed Detector module, only the following point types are
valid for each channel:
REF_1005
I/O
Channel
Name
Type
Terminal Block
Connection
High Resolution (speed value)
Input (can select I/O 1 or

3)
In
Low Resolution (speed value)
Input (can select I/O 1 or

3)
In
Open Wire
Input
N/A
11
Latched Overspeed
Input
N/A
12
Overspeed
Input
N/A
13
Trip Relay Status
Output
N/A
Trip Relay
Input
Relay
Reset Calculations
Input
N/A
467
31.13.7
Valve Positioner module
This module provides an interface to an electro-hydraulic servo actuator. Governor valves,

interceptor valves, extraction valves and bypass valves can be controlled. The module provides
closed loop valve positioning control and also interfaces to a local operator interface station
(SLIM).
This module provides an interface between an Ovation Controller and one Electro-Hydraulic (EH)
servo-valve actuator in the field. To use this module, the MASTATION algorithm must reside in
the Ovation Controller. (See Ovation Algorithm Reference Manual.)
The terminal block connection for the module depends upon the application being used. Refer to
wiring diagrams.
RANGE
17 Volts AC peak-to-peak 1 KHz or 23.75 Volts AC
peak-to-peak 3 KHz to an LVDT
CHANNELS
8
ELECTRONIC
MODULE
PERSONALITY
MODULE
1C31194G01 or
1C31197G01
1C31194G02
24.8 mA into three 82 ohm coils

23.75 Volts AC peak-to-peak 3 KHz or
17 Volts AC peak-to-peak 1 KHz to an LVDT
1C31194G02 or
1C31197G02
1C31194G01

1C31194G02 or
1C31197G03
1C31194G01

1C31194G02 or
1C31197G04
1C31194G01
468
REF_1005
RANGE
CHANNELS
ELECTRONIC
MODULE
PERSONALITY
MODULE

AUX Power (W) and VA (Typical).
Digital Input
0.12 W/VA (24VDC).
0.24 W/VA (48VDC).
Digital Output
100mA load
3.2 W/VA (24VDC).
6.4 W/VA (48VDC).
AUX heat dissipation .
Digital Input
0.41 BTUs per hour (24V).
Digital Output
The load is located outside the cabinet and its heat dissipation is not included.
When using the Point Builder to define points for a Valve Positioner module, only the following point types are
valid for each channel:
REF_1005
I/O
Channel
Name
Type

Destination
Terminal Block
Connection 2
Shutdown Status
Input
Valve Positioner
DI1
Auxiliary (wetting)
Voltage Sense
Input
Valve Positioner
DI2
SLIM ON Signal
Input
Valve Positioner
DI3
Position Feedback
Input
Valve Positioner
Coil 1 Voltage
(Read-back)
Input
Valve Positioner
Coil 1
Coil 2 Voltage
(Read-back)
Input
Valve Positioner
Coil 2
Coil 3 Voltage
(Read-back)
Input
Valve Positioner
Coil 3
Raw Demodulator
Voltage
Input
Valve Positioner
469
31.13.8
SLIM (Small Loop Interface module)
This module contains displays and keyboard inputs needed for an operator to monitor and control
the I/O functions of the Ovation Loop Interface or Valve Positioner module. The SLIM is located
external to the Ovation I/O cabinet and connected to the Loop Interface or Valve Positioner via
cable.
SLIM is not located in an Ovation cabinet and is not powered by an Ovation power supply.
SLIM uses 4D33741G01 - G03.

Main +24 Power (W) and VA (Typical) = 4.8 W/VA.
12VDC Power Supply (4D33743).
SLIM Cable Assembly (5A26166).
470
REF_1005
31.14 Remote Function module electrical specification sheets

Specifications for Ovation remote function modules are described in the following sections:
Remote MAU modules (see page 472).
Remote RNC modules (see page 473).
REF_1005
471
31.14.1
Remote Media Attachment Unit (MAU) module specifications
This module interfaces the remote IOIC card/module to the Ovation RNC module or to a WDPF
QOR card.
Consists of 1C31179 (E) and 1C31181 (G01-G04) (P) modules.

Draws power from the following (power supply efficiency is included):
Drawn from AC/DC Power Mains = 17.66 W/VA
Drawn from AC/DC Power Supply = 13.2 W
Main heat dissipation = 60 BTUs per hour.
472
REF_1005
31.14.2
Remote Node Controller (RNC) module specifications
This module interfaces the I/O modules in the Remote Node cabinet to an MAU module in the
Controller cabinet.
Consists of 1C31203 (E) and 1C31204 (G01, G03) (P) modules.

Draws power from the following (power supply efficiency is included):
Drawn from AC/DC Power Mains = 16 W/VA
Drawn from AC/DC Power Supply = 12 W
REF_1005
473
31.15 Cable specification sheets

The following Emerson approved cables can be used to provide network connections:
Fiber-optic Cable - MMF SC/SC (5A26164Gxx) (see page 477).
Cable Fast Ethernet/CDDI CAT5 (5A26155Gxx) (see page 476).
Remote I/O Cable (3A98763Gxx) (see page 477).
474
REF_1005
31.15.1
Network Fiber-Optic cable specifications (5A26164Gxx)
Note: The following table lists the cables that are currently available. These cables are subject
to change. Refer to your supplied drawings for exact requirements for your system.
Fiber optic network cable specifications
SPECIFICATION
CABLE ASSEM BLY

5 A2 6 1 6 4 G X X
Use of cable
Fast Ethernet
Termination Connectors
SC to SC
Raw cable (no connectors)
3A98763H01 (Green)
Cable Type
Multi-mode Dual Fiber
Core/Cladding diameter
62.5/125 m
Jacketing Material
Halogen Free, Flame Retardant, Low Toxicity
Attenuation @ 850 nm
length(m) x
0.0035db/m + 2db maximum
length(m) x
Outside Diameter
8.10 mm
(0.324 in)
Minimum Bend Radius
12.5 cm (5 in)
Minimum Bend Radius (Long Term)
7.5 cm (3 in)
Cable Assembly - Tensile Load for attenuation

increase 0.5db
300 N (66 lb)
Tensile Load at Installation
1776 N
maximum
(400 lb) max.

Connector Tensile Load
SC: 110 N (25 lb)
Minimum Crush Resistance
46 N/cm
(250 lb/in)
Maximum Cable Weight
46 kg/1 km
(31 lb/1000 ft)
Maximum Cable length
2 km
(6560 ft)
Bandwidth
160 MHz-km @ 850 nm

500 MHz-km @ 1300 nm
REF_1005
475
31.15.2
Network UTP cable specifications
UTP network cable specifications
SPECIFICATION
CABLE ASSEM BLY

1
5 A2 6 1 5 5 G X X
CABLE ASSEM BLY

1
1X00063GXX
Use of cable
Fast Ethernet (Straight-through)
Fast Ethernet (Crossover)
RJ45
RJ45
5A26154H01
5A26154H01
Cable Type
Category 5 UTP - 4 pair
Category 5 UTP - 4 pair
Color
Gray
Gray
Jacketing Material
Low Smoke (IEC 1034)
Low Smoke (IEC 1034)
Zero Halogen,
Zero Halogen,
Non-Plenum, Non-Riser
Non-Plenum, Non-Riser
Impedance
100 ohm
100 ohm
Attenuation 100 Mhz
22.0 db/100m
22.0 db/100m
Mutual Capacitance
4.6 nF/100 M
4.6 nF/100 M
DC Resistance
9.38 ohm/100 m maximum
9.38 ohm/100 m maximum
Outside Diameter
4.6 mm
4.6 mm
(0.181 in)
(0.181 in)
8.55 kg/0.1 km
8.55 kg/0.1 km
(19 lb/100 ft)
(19 lb/100 ft)
100 m
(327 ft)
100 m
(327 ft)

1
476
The cable must be routed in solid grounded conduit continuous to the cabinet (CE Mark Certified Systems only).
REF_1005
31.15.3
Network Remote I/O cable specifications
Remote I/O cable specifications
SPECIFICATION
C A B L E A S S E M B L Y 3 A9 8 7 6 3 G X X
C A B L E A S S E M B L Y 3 A9 8 7 6 4 G X X
Use of cable
Remote I/O
Remote I/O
ST to ST
ST to ST
3A98763H01
3A98764H01
Cable Type
Multimode Fiber
Multimode Fiber
Color
Green
Yellow
Core/Cladding diameter
62.5/125 m
62.5/125 m
Jacketing Material
Halogen Free, Flame Retardant,
Halogen Free, Flame Retardant,
Low Toxicity
Low Toxicity
length(m) x
length(m) x
length(m) x
length(m) x
Outside Diameter
8.10 mm (0.324 in)
8.10 mm (0.324 in)
Minimum Bend Radius
12.5 cm (5 in)
12.5 cm (5 in)
Minimum Bend Radius (Long

Term)
7.5 cm (3 in)
7.5 cm (3 in)
Cable Assembly - Tensile Load

for attenuation increase
0.5db
175 N (40 lb)
175 N (40 lb)
maximum
maximum
Tensile Load at Installation
1776 N (400 lb) max.
1776 N (400 lb) max.
Connector Tensile Load
ST: 175 N (40 lb)
ST: 175 N (40 lb)
Minimum Crush Resistance
46 N/cm (250 lb/in)
46 N/cm (250 lb/in)
46 kg/1 km
46 kg/1 km
(31 lb/1000 ft)
(31 lb/1000 ft)
2 km (6560 ft) using 850 nm

4 km (13,123 ft) using 1300 nm
2 km (6560 ft) using 850 nm

4 km (13,123ft) using 1300 nm
Bandwidth
160 MHz-km @ 850 nm
160 MHz-km @ 850 nm
500 MHz-km @ 1300 nm
500 MHz-km @ 1300 nm
REF_1005
477
Index
A
AC line filtering (Applicable to EMC Cabinet
approach only) 225
AC Mains connection to line filter assembly
175
AC/DC Mains connection to the Power
Distribution Module (PDM) 178
AC/DC Mains wiring requirements 81
Acknowledged list in the Operator Station
Alarm window 338
Alarm Annunciation window definition 345
Alarm definition 327
Alarm delays 358
Alarm display types 332
Alarm example 328
Alarm filtering 347
Alarm flood definition 347
Alarm limits 355
Alarm List in the Operator Station Alarm
window 336
Alarm list information fields 332
Alarm list tabs that display in the Alarm
window 334
Alarm logging methods 352
Alarm management benefits 360
Alarm management definition 328
Alarm management problems 329
Alarm planning best practices 329
Alarm rates 347
Alarm reduction methods 356
Alarm reduction techniques 359
Alarm suppression logic 357
Alarm system operation 331
Alarms that use audio 352
Analog I/O modules (main/aux power and
main/aux heat dissipation) (drawn from
AC/DC Mains power) 15
Analog Input 13 bit module (legacy systems)
419
Analog Input 14 bit high speed module 423
Analog Input 14 bit module 422
Analog Input module electrical specification
sheets 418
Analog Input modules 105
Analog Output module (4 channels) 431
Analog Output module electrical
specification sheets 430
Analog Output modules 108
Antivirus software (importance) 277
REF_1005
Appliances in the Ovation Security Center

372
Archiving your data 282
B
Best practices for establishing a secure
system 276
Best practices for installing Ovation system
software 247
Bus interface module electrical specification
sheets 456
Bus interface modules 19, 116
C
Cabinet circuit breaker/on/off switch 182
Cabinet configuration guidelines 125
Cabinet EMC grounding 83
Cabinet sealed NEMA12 (5X00019H01)
386
Cabinet sealed NEMA4 (5X00019H02) 387
Cabinet sealed, NEMA12 (1X00455) 395
Cabinet sealed, NEMA12
(5X00035H01/H03) 391
393
Cabinet sealed, NEMA4 (5X00035H02/H04)
392
394
Cabinet specification sheets 384
Cabinet vented (1X00518) 395
Cabinet vented (1X00545) 396
Cabinet vented NEMA12 (with mounting
plate) (5X00127) 389
Cabinet vented NEMA12 (without mounting
plate) (5X00020) 388
Cabinet vented, NEMA12 (1X00454) 395
Cabinet vented, NEMA12 (front access only)
(5X00068) 395
Cabinet weights 151
Cabinets (user-supplied) 161
Cable access areas 143
Cable configuration types 73
Cable connection types for your network 48
Cable specification sheets 478
Cabling requirements for CE Mark Certified
systems 225
Cabling requirements for IEC61131-2
certified systems 227
479
Index
Calculating power supply requirements for
Specialty I/O modules 194
CE Mark Certified system definition 220
CE Mark Certified systems (using third-party
components) 221
CE Mark Certified systems grounding panels
222
Communication interface message protocols
363
Communication interface physical
connections 362
Communication interface platforms 361
Communication interface spreadsheets
363
Compact Contact Input module 440
Compact Digital Input module 437
Compact Sequence of Events Digital Input
module 443
Components of an Ovation system 6
Connectivity definition 361
Contact Input module 439
Control Builder terminology 255
Control design best practices 262
Control functions (control sheets) 263
Control planning process 258
Control project scope 259
Control sheet building best practices 264
Control types supported in Ovation 253
Controller cabinet 128
Controller cabinet configuration for local
Ovation I/O 128
Controller cabinet configuration for local QLine I/O 130
Controller cabinet configuration for mixed
(local and remote) Ovation I/O 129
Controller cabinet configuration for remote
Ovation I/O 129
Controller cabinet configuration for remote
Q-Line I/O 130
Controller cabinet illustrations 131
Controller cabinet maintenance 154
Controller Cabinet On/Off Controls 182
Controller OCR161 backplane illustration
174
Controller OCR400 backplane illustration
173
Controller power switch 183
Copyright Notice 2
D
Data collision prevention 41
Database Initial Definition tool (DBID) 241
Database tools 241
DBID fields (entering information) 242
Dell 190S FP (19 407
Dell 2007FP (20 408
480
Dell Optiplex 990 Engineer Client

Station/Operator Station/Virtual Controller
(Windows 7) (5X00572) 400
Dell Optiplex 990 Engineer Client
Station/Operator Station/Virtual Controller
(XP) (5X00571) 399
Dell Poweredge T310 Server Ovation
Process Historian (OPH) (5X00488)
(Windows Server 2008) 401
Dell Poweredge R710 Domain
Controller/Database Server (Rack Mount)
(5X00462) (Windows Server 2008) 398
Dell Poweredge R710 EDS Linux Red Hat
Enterprise (5X00568) 405
Dell Poweredge R710 EDS Windows Server
2008 (5X00570) 404
Dell Poweredge R710 Ovation Process
Historian (Rack Mount) (5X00463)
(Windows Server 2008) 402
Dell Poweredge T310 Domain Controller or
Terminal Server Host Workstation
(5X00487) (Windows Server 2008) 397
Dell Precision R5400 Operator Station
(Windows 7) (Rack Mount) (5X00461)
401
Dell Precision R5400 Operator Station (XP)
(Rack Mount) (5X00559) 400
Dell Precision T3500 Engineer / System
Database Server (5X00557 for XP)
(5X00558 for Win7) 399
Dell Precision T5500n EDS Workstation
(5X00569) (Windows 7) (64-bit) 403
Dell Precision T5500n EDS Workstation
Linux Red Hat Enterprise (5X00567) 403
Dell U2410 (24 408
DeviceNet and Ovation components 324
DeviceNet hardware and software
requirements 325
DeviceNet interoperability 323
DeviceNet module (2 channels) 457
DeviceNet module definition 325
DeviceNet overview 322
Diagrams in planning control 262
Digital I/O modules (main/aux power and
Digital Input module (16 channels) 435
Digital Input module electrical specification
sheets 434
Digital Input modules 110
Digital Output module electrical (16
channels) 449
Digital Output module electrical specification
sheets 448
Digital Output modules 114
Displaying Alarm lists 333
Distance between network nodes 76
REF_1005
Index
Domain concept definition 246
Domain concept usage in security 275
Domain controller hardware requirements
247
Domain controller software requirements
248
Domain member software requirements
248
Drop types 250
E
eDB or HSR migration 284
Electrical information for Ovation equipment
12
Elements of an Ovation system 9
EMC cabinet, NEMA12, Rittal (4D33947)
384
End users for OPH 283
Enhanced Compact Sequence of Events
Digital Input module (16 channels) 445
Equipment locations 11
Equipment protection 11
Establishing a philosophy for alarm
management 330
Ethernet Link Controller module (1 channel)
457
Ethernet switches provide network stability
41
Example of network switch configuration file
42
Extended I/O cabinet 136
Extended I/O cabinet illustration 167, 168
External power supply usage 198
External security definition 274
F
Fast Ethernet network configurations 47
Field wiring available usage 149
Field wiring requirements 80
Floor plan recommendations 153
Foundation Fieldbus and Ovation
components 300
Foundation Fieldbus definition 286, 298
Foundation Fieldbus discrete I/O 292, 306
Foundation Fieldbus first and second
generation solutions 285, 297
Foundation Fieldbus I/O 292, 306
Foundation Fieldbus interoperability 287,
299
Foundation Fieldbus modulating valves
292, 306
Foundation Fieldbus module (2 channels)
456
Foundation Fieldbus motor control centers
and variable frequency drives 292, 306
Foundation Fieldbus partitioning instruments
and applications 293, 307
REF_1005
Foundation Fieldbus pressure, level and flow

292, 306
Foundation Fieldbus recommended
installation practices 293, 307
Foundation Fieldbus segmentation design
288, 302
Foundation Fieldbus temperature
measurements 292, 306
Foundation Fieldbus topology 289, 303
Foundation Fieldbus used in Ovation control
294
Functions of Ovation SIS 376
Functions of the Ovation Security Center
371
G
Grounding guidelines 83
Grounding guidelines for clustered cabinet
arrangements 86
Grounding guidelines for single cabinet
arrangements 84
Grounding panel configuration 223
Guidelines for replacing, adding, or
combining Ovation modules 99
H
Hardware components of Ovation SIS 377
Hardware information for Ovation multiple
networks 71
Hardware/Device spreadsheet 365
HART Analog Input module 426
HART Analog Output module 432
HART High Performance Analog Input
module 427
HART High Performance Analog Output
module 433
High Side Digital Output module (24VDC)
453
Historians (OPH) needed 281
History list in the Operator Station Alarm
window 337
HP B/W Laserjet 5200 printer (5X00328)
413
HP Color Laserjet 5525 (5X00550) 415
HP Color Laserjet Enterprise
CP4525n/4525dn (5X00520) 414
HP Thermal/Inkjet 2800DTN printer
(5X00243) 414
I
I/O cabinets (main/aux power and main/aux
heat dissipation) (drawn from AC/DC
Mains power) 13
I/O module definition 91
I/O module environmental specifications
417
481
Index
I/O module features 91
I/O module types 104
I/O modules (add new) 102
I/O modules (hot swap) 101
I/O modules (standard) 93
I/O modules for OCR161 Controller 127
I/O modules for OCR400 Controller 127
I/O modules installation 101
Icon list in the Operator Station Alarm
window 341
IE61131-2 certified system grounding panel
227
IEC61131-2 certified system definition 227
Illustrations of Extended cabinet
configurations 136
Industry standards of compliance (design
standards) 229
Industry standards of compliance (electrical
interference standards) 229
Industry standards of compliance (reliability
standards) 229
Industry standards of compliance (safety
standards) 229
Internal cable ferrites (non-EMC cabinet
approach only) 226
Internal security definition 274
Internet address classes 231
Internet address conventions 233
Internet address notation 232
Internet address subnet masks 233
Internet addresses (allowable) 232
1
IP traffic switch 52
K
Keyboard specification sheet 410
L
Limitations for Ovation SIS system 376
Link Controller module 459
Loop Interface module (electric drive) 464
Loop Interface module (normal non-electric
drive) 460
M
Managing alarms best practices 346
Marshalling cabinet 133
Marshalling cabinet illustrations 133
MAU module 94
Media converters 75
Media converters used In Ovation networks
44
Monitor specification sheets 406
Multi-mode fiber optic cable 74
482
Multiple network and new Ovation systems

64
Multiple network definition 59
Multiple network planning guidelines for
Ovation systems 61
Multiple network terminology 59
Multiple networks (before connecting) 63
Multiple networks and existing Ovation
systems 65
Multiple networks and hybrid Ovation
systems 66
Multiple networks backbone connectivity 68
Multiple networks collapsed backbone
connectivity 70
Multiple networks connection plan 67
N
NEC P401 (40 409
NEC P461 (46 409
NEC V321 (32 409
Network cable (EMI/RFI environment) 75
Network cable (finding diameter) 86
Network cable (grounding) 76
Network cable (selecting) 75
Network cable infrastructure 75
Network cables (installed) 76
Network Fiber-Optic cable specifications
(5A26164Gxx) 479
Network planning guidelines for Ovation
systems 40
Network Remote I/O cable specifications
481
Network terminology 38
Network UTP cable specifications 480
Non-Foundation Fieldbus instruments 293,
307
Non-Ovation devices (connecting) 58
Nuisance alarms 346
Nuisance alarms management 347
O
Obtaining a Material Return Tracking (MRT)
number 209
OCR161 Controller cover 157
OCR161 Controller cover (close) 160
OCR161 Controller cover (open) 159
OCR161 Controller fan assembly (removing)
160
OCR161 Controller fan assembly (replacing)
160
OCR161 Controller power requirements
(calculating) 34
OCR161 Controller/Marshalling cabinet
illustration 166
OCR161 Controllers (connecting) 56
OCR400 Controller definition 265
OCR400 Controller I/O interfaces 266
REF_1005
Index
OCR400 Controller module replacement
155
OCR400 Controller Modules 155
OCR400 Controller power requirements
(calculating) 33
OCR400 Controller/Marshalling cabinet
illustration 165
OCR400 Controllers (connecting) 53
Okidata Microline 395C (5X00445) 414
OPH third-party software 284
OSC compatibility with Ovation releases
374
OSI Seven-Layer Model 45
Ovation cabinet components 126
Ovation cabinet definition 124
Ovation Control Builder definition 254
Ovation control definition 252
Ovation Database (creating) 240
Ovation devices (connecting) 57
Ovation equipment lifting guidelines 214
Ovation equipment off-loading and
unpacking guidelines 215
Ovation equipment repacking and returning
guidelines 216
Ovation equipment shipping guidelines 213
Ovation equipment storage guidelines 216
Ovation equipment transportation guidelines
216
Ovation hardware specification sheets 383
Ovation Keyboard (4D33935) 411
Ovation network definition 38
Ovation SIS Logic Solver algorithm table
380
Ovation Suppression Panel 226
Ovation system definition 1
Ovation system terminology 1
Ovation workstation specification sheets
397
P
Part failure during project startup 210
Part repairs (tracking) 211
Parts repairs (handling) 210
Parts return 208
Planning alarm management 327
Planning cable configurations for your
Ovation system 73
Planning Connectivity for your Ovation
system 361
Planning control best practices 259
Planning control for your Ovation system
251
Planning for an Ovation Process Historian
(OPH) 279
Planning for DeviceNet 321
Planning for first generation (gateway)
Foundation Fieldbus 285
REF_1005
Planning for Profibus 311

Planning for replacement parts and repair
service 207
Planning for second generation (I/O module)
Foundation Fieldbus 297
Planning for shipping and storage of Ovation
equipment 213
83
Planning I/O modules for your Ovation
system 91
Planning network and I/O field wiring routing
77
Planning Ovation cabinets for your Ovation
system 123
163
Planning security for your Ovation system
273
Planning software installation for Windowsbased Ovation systems 245
Planning to meet industry standards of
compliance 229
Planning Virtual Controllers 269
Planning your CE Mark Certified system
219
Planning your hardware installation 379
Planning your IEC61131-2 system 227
Planning your internet addressing 231
Planning your Ovation Controller 265
Planning your Ovation database 235
Planning your Ovation equipment 11
Planning your Ovation multiple networks 59
Planning your Ovation network 37
Planning your Ovation Security Center 371
Planning your Safety Instrumented System
375
PlantWeb Alerts for Foundation Fieldbus
alarms 295, 354
Point description 236
Point frequency description 238
Point name understanding 238
Point names (fully qualified) 240
Point names (valid) 238
Point out of service 331
Point record description 237
Points used as alarms 330
Power Distribution Module (PDM) illustration
170
Power mains connections 175
Power supply features 179
Power supply limits 182
Power supply module availability 180
Power supply modules (using) 179
Power supply requirement calculations for
Analog I/O modules 187
483
Index
Bus interface modules 189
Digital I/O modules 190
I/O Cabinet components 185
remote function modules 196
Power supply requirements (drawn from
+24V main or auxiliary power supply)
184
Power supply status monitoring 196
Ppower distribution in an Ovation system
163
Printer specification sheets 412
Profibus and Ovation components 314
Profibus device interoperability 313
Profibus devices 315
Profibus hardware and software
requirements 319
Profibus module (2 channels) 457
Profibus overview 312
Profibus redundancy 317
Protective earth 83
Pulse Accumulator module 467
R
RAID SATA to iSCSI Media (5X00523) 417
Redundant power supplies (monitoring one
set) 196
Redundant power supplies (monitoring two
sets) 197
Relational Database definition 235
Relay Output Electronics modules (hot
swap) 102
Relay Output I/O modules (add new) 103
Relay Output module electrical 454
Relay Output module installation 102
Relay Output modules 98
Relay Panel cabinet illustrations 142
Release version spreadsheet 368
Remote Function module electrical
specification sheets 475
Remote function modules (main/aux power
and main/aux heat dissipation) (drawn
from AC/DC Mains power) 32
Remote function modules (RIO) 93
Remote Media Attachment Unit (MAU)
module specifications 476
Remote Network Status list in the Operator
Station Alarm window 343
Remote Node cabinet 138
Remote Node cabinet illluistrations 139
Remote Node cabinet illustration 169
Remote Node Controller (RNC) module
specifications 477
Repair prices 211
484
Reset list in the Operator Station Alarm

window 340
RNC module 96
RTD Input module (4 channel) 428
RTD Input module (8 channel) 429
S
Scanners needed 281
Selecting an alarm filtering mode 351
Sequence of Events Digital Input module
441
Servo Driver module 469
Shorting bar removal 87
Single-mode fiber optic cable 74
Single-mode fiber optic cable (planning) 74
Single-tier network arrangement 50
SLIM (Small Loop Interface module) 474
Software components of Ovation SIS 379
Software installation process for Windowsbased Ovation systems 245
Solid and stranded wire AWG diameters 85
Spare part number 207
Spare part price 208
Spare parts ordering 207
Specialty I/O modules (main/aux power and
Specialty module electrical specification
sheets 458
Specialty Modules 117
Speed Detector module 471
Storage device specification sheets 416
Summary of Changes 3
Switches used in Ovation networks 42
System expansion planning 261
T
Third-party product repacking guidelines
216
Transition panel illustration 171
Two-tier network arrangement 51
U
Unacknowledged list in the Operator Station
Alarm window 339
Understanding Foundation Fieldbus
segmentation 288
Unshielded twisted pair (UTP) cable 73
Using characteristics to filter alarms 348
Using priorities to filter alarms 350
Using security for alarm management 353
V
Valve Positioner module 472
Viewing diagrams from the Icon List 343
Virtual Controller definition 269
REF_1005
Index
Virtual Controller hardware requirements
271
Virtual Controller requirements 271
Virtual Controller software requirements
271
Virtual Controllers usage 270
W
What are the components of Kaspersky
antivirus? 277
What are the hardware requirements for a
domain member as a Database Server?
247
What are the licensing requirements for an
Ovation Windows-based system? 249
What are the licensing requirements for
Ovation Virtual Controllers? 271
What are the supported Fieldbus
algorithms? 308
What is a Safety Instrumented System?
375
What is antivirus software? 276
What is the Ovation Process Historian?
279
What is the Ovation Security Center? 371
Workstations (connecting) 52
REF_1005
485

Ref 1005 PDF

Uploaded by

Document Information

Original Description:

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

Ref 1005 PDF

Uploaded by

Copyright:

Available Formats

Planning Your Ovation System

19" Dell 190S Monitor (5X00473).

24" Dell U2410 WFP Monitor (5X00474).

OKIDATA Microline Printer (5X00445).

Dell T310 PowerEdge Domain Controller (5X00487).

Dell T310 PowerEdge Ovation Process Historian (5X00488).

Added information on the following new modules:

16 Channel 4-20mA Analog Input.

32 Channel 24V DC Single-Ended Digital Input.

32 Channel 24V DC Single-Ended Digital Output.

Added information for Numalogic Fast Ethernet Remote Node Controller.

Updated WDPF to Ovation Migration I/O module group numbers.

Updated Ovation terminology.

24" Dell 2408WFP (Obsoleted)

20" Dell UltraSharp 2001FP (Obsoleted)

20" Dell UltraSharp 2000FP (Obsoleted)

20" NEC LCD2010X (Obsoleted)

19" Dell UltraSharp 1908FP (Obsoleted)

19" Dell UltraSharp 1907FP (Obsoleted)

19" Dell UltraSharp 1905FP (Obsoleted)

19" Dell 1901FP (Obsoleted)

18" Dell 1801FP (Obsoleted)

18" Dell UltraSharp 1800FP (Obsoleted)

18" NEC LCD1850E (Obsoleted)

18" NEC LCD1830 (Obsoleted)

22"/20"v NEC AS120BK (Obsoleted)

22"/20"v Samsung 1100MB - CE (Obsoleted)

22"/20"v Samsung 1100DF - CE (Obsoleted)

22"/20"v NEC FE2111sb (Obsoleted)

22"/20"v NEC FE1250+ (Obsoleted)

22"/20"v Mitsubishi Diam.+ 200 (Obsoleted)

21" Mitsubishi (Obsoleted)

20" Sun-Sony 20D20/20E10 (Obsoleted)

20" Intecolor V80 (Obsoleted)

19" Intecolor E19Z (Obsoleted)

Large Screen LCD:

57" NEC LCD5710-2 (Obsoleted)

57" NEC LCD5710-BK-IT (Obsoleted)

46" NEC LCD4620-2 (Obsoleted)

46" NEC LCD4620 (Obsoleted)

46" NEC LCD4610 (Obsoleted)

40" NEC LCD4020-2 (Obsoleted)

40" NEC LCD4020 (Obsoleted)

40" NEC LCD4010 (Obsoleted)

40" NEC LCD4000 (Obsoleted)

32" NEC LCD3215 (Obsoleted)

32" NEC LCD3210 (Obsoleted)

30" NEC LCD3000 (Obsoleted)

Large Screen CRT:

27" EDL 6127 (Obsoleted)

27" Conrac 9527 (Obsoleted)

61" NEC PX-61XM3A (Obsoleted)

42" NEC PX-42VP5A (Obsoleted)

50" NEC PX-50XM4A (Obsoleted)

Color (Video Copy/Report) Printers:

HP Color Laserjet 5550 (Obsoleted)

HP Color Laserjet 4700 (Obsoleted)

HP Color Laserjet 4650N (Obsoleted)

HP Color Laserjet 4600 (Obsoleted)

HP Color Laserjet 4550N (Obsoleted)

HP Color Laserjet 4500N (Obsoleted)

HP Color Deskjet 1600CM (Obsoleted)