OW360 - R1005 - Planing Your Ovation System

Planning Your Ovation System
OW360_R1005
(For use with Ovation 3.6.0 systems and Feature Pack 1)

February 2017
Version 2
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 Power & Water Solutions, Inc. (Emerson) 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
the use and application of the OvationTM Unit. Due to the many variables associated with specific
uses or applications, Emerson cannot assume responsibility or liability for actual use based upon
the data provided in this manual.
No patent liability is assumed by Emerson 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.
The document is the property of and contains Proprietary Information owned by Emerson 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. 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
Web site: https://www.ovationusers.com
Summary of Changes
Planning Your Ovation System
OW360_R1005
February 2017
Version 2
This version of Planning Your Ovation System includes the following new information:
 Added information on Gigabit Ethernet (see page 39).
 Updated information for the following modules:
 Digital Input Compact module (16 Channel) (see page 140).
 Sequence of Events Compact Digital Input Field Interface module (16 Channel) (see
page 143).
 Sequence of Events Enhanced Compact Digital Input module (16 Channel) (see page
144).
 Digital Output module (see page 145).
 Servo Driver (RSR) module (see page 157).
 Speed Detector module (see page 158).
 Valve Positioner module (see page 162).
 Made miscellaneous corrections and clarifications.
Contents
1 Introduction to planning your Ovation system 1

1.1 What is an Ovation system? ............................................................................................... 1
1.2 What are the components of an Ovation system? .............................................................. 2
1.2.1 Ovation network ..................................................................................................... 2
1.2.2 Ovation database ................................................................................................... 3
1.2.3 Ovation input/output modules ................................................................................ 3
1.2.4 Ovation Controllers ................................................................................................ 3
1.2.5 Ovation Operator Stations...................................................................................... 4
1.2.6 Developer Studio (Windows).................................................................................. 4
1.2.7 Historical storage and reporting capabilities .......................................................... 5
1.2.8 Third-party devices ................................................................................................. 5
1.2.9 Connectivity products ............................................................................................. 5
1.3 Planning the elements of an Ovation system ...................................................................... 5
1.4 Ovation system terminology ................................................................................................ 7
1.5 Ovation reference documentation ..................................................................................... 11
2 Planning your Ovation equipment 13

2.1 Selecting equipment locations .......................................................................................... 13
2.2 Protecting the Ovation equipment ..................................................................................... 14
2.3 Electrical information for Ovation equipment .................................................................... 15
2.3.1 Understanding heat dissipation ............................................................................ 15
2.3.2 I/O cabinet components (main/aux power and main/aux heat dissipation)
(drawn from AC/DC Mains power) ....................................................................... 16
2.3.3 Analog I/O modules (main/aux power and main/aux heat dissipation)
2.3.4 Digital I/O modules (main/aux power and main/aux heat dissipation)
2.3.5 Bus interface modules (main/aux power and main/aux heat dissipation)
2.3.6 Specialty I/O modules (main/aux power and main/aux heat dissipation)
2.3.7 Remote function modules (main/aux power and main/aux heat dissipation)
2.3.8 Calculating main power requirements .................................................................. 37
3 Planning your Ovation network 39

3.1 Understanding Ovation networks ...................................................................................... 39
3.1.1 Preventing data collisions .................................................................................... 40
3.1.2 Network terminology ............................................................................................ 40
3.2 Fast Ethernet network configurations ............................................................................... 42
3.3 Gigabit Ethernet network configurations ........................................................................... 43
3.4 Ovation network generations ............................................................................................ 43
3.4.1 Ovation second generation network technology .................................................. 44
OW360_R1005 i
Table of Contents
3.4.2 Ovation third generation network technology....................................................... 45

3.5 Hardware used in Ovation networks ................................................................................. 46
3.5.1 Using Ethernet switches to provide network stability ........................................... 46
3.5.2 Switches used in Ethernet second and third generation Ovation networks ......... 47
3.5.3 Switches used in Gigabit Ovation networks ......................................................... 50
3.5.4 Media converters used in Ovation networks ........................................................ 51
3.5.5 Cable connection types for your network ............................................................. 52
3.6 Network topology .............................................................................................................. 53
3.6.1 Single-tier network arrangement .......................................................................... 54
3.6.2 Two-tier network arrangement ............................................................................. 55
3.7 Network planning guidelines for Ovation systems ............................................................ 57
3.8 Connecting equipment to your network ............................................................................ 57
3.8.1 Connecting OCR400 or OCR1100 Controllers to your Ovation network ............. 58
3.8.2 Connecting workstations to your Ovation network ............................................... 60
3.8.3 Connecting Ovation devices to your Ovation network ......................................... 61
3.8.4 Connecting non-Ovation devices to your Ovation network .................................. 61
4 Planning your Ovation multiple networks 63

4.1 What is an Ovation multiple network? ............................................................................... 63
4.2 What are the basics of multi-networking? ......................................................................... 64
4.2.1 Local and Remote Network Concepts ................................................................. 65
4.2.2 What is the network name alias concept? ........................................................... 66
4.2.3 What is IP addressing? ........................................................................................ 67
4.2.4 What are other possible multi-network configurations? ....................................... 68
4.2.5 What is needed to make multi-networks work? ................................................... 70
4.2.6 Multiple network terminology................................................................................ 72
4.3 Multiple network planning guidelines for Ovation systems ............................................... 74
4.4 What do you need to plan before connecting multiple networks? .................................... 76
4.4.1 What is a multiple network implementation for new Ovation systems? ............... 77
4.4.2 What is a multiple network implementation for existing Ovation systems? ......... 78
4.4.3 What is a multiple network implementation for hybrid Ovation systems? ............ 79
4.5 What is the connection plan for multiple networks? .......................................................... 80
4.6 What is backbone connectivity for multiple networks? ..................................................... 81
4.7 What is collapsed backbone connectivity for multiple networks? ..................................... 83
4.7.1 Connections for core switches ............................................................................. 84
4.8 Licensing in Multiple Networks .......................................................................................... 84
4.9 What security is needed for multiple networks?................................................................ 84
4.10 Hardware information for Ovation multiple networks ........................................................ 85
5 Planning cable configurations for your Ovation system 87

5.1 Network cable configuration types for your Ovation system ............................................. 87
5.1.1 Unshielded twisted pair (UTP) ............................................................................. 87
5.1.2 Multi-mode fiber optic cable ................................................................................. 88
5.1.3 Single-mode fiber optic cable ............................................................................... 88
5.1.4 Media converters .................................................................................................. 89
5.2 Selecting network cable .................................................................................................... 89
5.2.1 Existing network cable infrastructure ................................................................... 89
5.2.2 EMI/RFI environment for network cable ............................................................... 89
5.2.3 Grounding network cable ..................................................................................... 90
ii OW360_R1005
Table of Contents
5.2.4 Distance between network nodes ........................................................................ 90

5.2.5 Permanently installed network cables .................................................................. 90
5.3 Planning network and I/O field wiring routing.................................................................... 91
5.3.1 Field wiring requirements ..................................................................................... 94
5.3.2 AC/DC Mains wiring requirements ....................................................................... 95
6 Planning grounding for your Ovation system 97

6.1 General grounding guidelines ........................................................................................... 97
6.2 Protective earth ................................................................................................................. 97
6.3 Ovation cabinet EMC grounding ....................................................................................... 97
6.4 Grounding guidelines for single cabinet arrangements .................................................... 98
6.4.1 AWG diameters for solid and stranded wire ........................................................ 99
6.4.2 Example of finding the diameter of a network cable .......................................... 100
6.5 Grounding guidelines for clustered cabinet arrangements ............................................. 100
6.5.1 Auxiliary ground strap ........................................................................................ 101
6.5.2 To remove the shorting bar from an Ovation cabinet ........................................ 101
7 Planning I/O modules for your Ovation system 103

7.1 What is an Ovation module? ........................................................................................... 103
7.2 What is the purpose of an Ovation I/O module? ............................................................. 104
7.3 Ovation I/O reference terminology .................................................................................. 104
7.4 Ovation I/O module features ........................................................................................... 109
7.5 Standard Ovation I/O module Base components............................................................ 111
7.6 Standard two-slot Ovation I/O Base assembly (1B30035) ............................................. 115
7.7 Marshalling two-slot I/O Base (1X00014) ....................................................................... 116
7.8 Marshalling two-slot I/O Base with secure connectors (5X00334) ................................. 117
7.9 Four-slot I/O Base with common strip connections (5X00497) ....................................... 118
7.10 Remote function modules (RIO)...................................................................................... 120
7.10.1 MAU with typical fiber-optic connector pairs for OCR400 and OCR1100
Controllers .......................................................................................................... 121
7.10.2 Remote Node Controller (RNC) (1C31205) ....................................................... 122
7.11 Relay Output Bases ........................................................................................................ 122
7.11.1 Relay Output Base (32 channel fused) Slim 28x5mm relay (5X00623) ............ 123
7.11.2 Relay Output Base (32 channel non-fused) Slim 28x5mm relay (5X00584) ..... 124
7.11.3 Relay Output Base (16 channel fused) low-power relay GR2 (5X00431) ......... 125
7.11.4 Relay Output Base (16 channel non-fused) low-power relay GR2 (1C31223) .. 126
7.11.5 Relay Output Base (12 channel fused) high-power relay KUEP (5X00430) ..... 127
7.11.6 Relay Output Base (12 channel non-fused) high-power KUEP (1C31222) ....... 128
7.11.7 Relay Output Base (8 channel with contact monitoring) high-power KUEP
(5X00564)........................................................................................................... 129
7.12 What are the I/O module types? ..................................................................................... 130
7.12.1 Analog Input module (13 Bit) (8 Channel) (Legacy product) ............................. 131
7.12.2 Analog Input module (14 Bit) (8 Channel) .......................................................... 132
7.12.3 Analog Input High Speed module (14 Bit) (8 Channel) ...................................... 133
7.12.4 Analog Input module (0-10V High Impedance) (8 channel) ............................... 133
7.12.5 HART Analog Input module (8 Channel) ........................................................... 134
7.12.6 HART High Performance Analog Input module (8 Channel) ............................. 134
7.12.7 RTD Analog Input module (4 Channel) .............................................................. 135
7.12.8 RTD Analog Input module (8 Channel) .............................................................. 135
OW360_R1005 iii
Table of Contents
7.12.9 RTD Analog Input module (8 Channel Compact) .............................................. 136

7.12.10 RTD Analog Input module (16 Channel) ............................................................ 136
7.12.11 Analog Input module 4-20mA (16 Channel)....................................................... 137
7.12.12 Thermocouple Input module (16 Channel) ........................................................ 137
7.12.13 Analog Output module (4 Channel) ................................................................... 138
7.12.14 HART Analog Output module (8 Channel) ......................................................... 138
7.12.15 HART High Performance Analog Output module (4 Channel) .......................... 139
7.12.16 Digital Input module (16 Channel) ..................................................................... 139
7.12.17 Digital Input Redundant module (16 Channel) (Windows Ovation 3.2 and
above) ................................................................................................................ 140
7.12.18 Digital Input Compact module (16 Channel) ...................................................... 140
7.12.19 Digital Input Contact module (16 Channel) ........................................................ 141
7.12.20 Digital Input Compact Contact module (16 Channel) ........................................ 141
7.12.21 Sequence of Events Digital Input module (16 Channel) .................................... 142
7.12.22 Sequence of Events Contact Input Field module (32 Channel) ......................... 142
7.12.23 Sequence of Events Compact Digital Input Field Interface module
(16 Channel) ...................................................................................................... 143
7.12.24 Sequence of Events Enhanced Compact Digital Input module (16 Channel) ... 144
7.12.25 Digital Input module 24 VDC (32 Channel) ........................................................ 145
7.12.26 Digital Output module (16 Channel) ................................................................... 145
7.12.27 Digital Output module 24 VDC (32 Channel) ..................................................... 146
7.12.28 Digital Output High Side (24 VDC) module (16 Channel) .................................. 146
7.12.29 Relay Output panel ............................................................................................ 147
7.12.30 Relay Output panel with Contact Monitoring module ......................................... 148
7.12.31 Relay Output panel (32 Channel) ...................................................................... 149
7.12.32 Relay Output (Fused) panel ............................................................................... 150
7.12.33 Foundation Fieldbus module .............................................................................. 151
7.12.34 Profibus DP module ........................................................................................... 151
7.12.35 DeviceNet module .............................................................................................. 151
7.12.36 Ethernet Link Controller (ELC) module .............................................................. 152
7.12.37 Link Controller module ....................................................................................... 152
7.12.38 Loop Interface module ....................................................................................... 153
7.12.39 Pulse Accumulator module ................................................................................ 156
7.12.40 Servo Driver (RSR) module ............................................................................... 157
7.12.41 Speed Detector module ..................................................................................... 158
7.12.42 Valve Positioner module .................................................................................... 162
7.12.43 Small Loop Interface module (SLIM) ................................................................. 163
7.12.44 Numalogic Fast Ethernet Remote Node ............................................................ 163
7.12.45 Machinery Health Monitor module ..................................................................... 164
7.12.46 Digital Excitation Controller (DEC) module ........................................................ 165
7.13 Guidelines for replacing, adding, or combining Ovation modules................................... 166
7.14 Installing Ovation standard I/O modules ......................................................................... 167
7.14.1 To hot swap standard I/O modules .................................................................... 168
7.14.2 To add new standard I/O modules ..................................................................... 169
7.15 Installing Ovation Relay Output modules ........................................................................ 169
7.15.1 To hot swap Relay Output Electronics modules ................................................ 169
7.15.2 To add new Relay Output I/O modules .............................................................. 170
iv OW360_R1005
Table of Contents
8 Planning Ovation cabinets for your Ovation system 171

8.1 What are Ovation cabinets? ............................................................................................ 172
8.2 Cabinet configuration guidelines ..................................................................................... 173
8.3 Ovation cabinet components........................................................................................... 174
8.4 How many I/O modules can an OCR400 or an OCR1100 Controller support? .............. 175
8.5 Ovation Controller cabinet ............................................................................................... 175
8.5.1 Controller cabinet configuration for local Ovation I/O ........................................ 176
8.5.2 Controller cabinet configuration for remote Ovation I/O .................................... 176
8.5.3 Controller cabinet configuration for mixed (local and remote) Ovation I/O ........ 176
8.5.4 Controller cabinet configuration for local Q-Line I/O .......................................... 176
8.5.5 Controller cabinet configuration for remote Q-Line I/O ...................................... 177
8.5.6 Illustrations of Controller cabinet configurations ................................................ 178
8.6 Ovation Marshalling cabinet ............................................................................................ 180
8.6.1 Marshalling cabinet configuration illustrations ................................................... 180
8.7 Ovation extended I/O cabinet.......................................................................................... 183
8.7.1 Extended cabinet configuration illustrations ....................................................... 184
8.8 Remote Node cabinet ..................................................................................................... 186
8.8.1 Remote Node cabinet configuration illustrations................................................ 187
8.8.2 Relay Panel cabinet configuration illustrations .................................................. 191
8.9 Examples of cable access areas and floor bolting in Ovation cabinets (Hoffman
cabinets) .......................................................................................................................... 192
8.10 Examples of cable access areas and floor bolting in Ovation cabinets (Rittal cabinets) 197
8.11 Examples of available usage area for field wiring ........................................................... 200
8.12 Weights of Ovation cabinets ........................................................................................... 202
8.13 Floor plan recommendations ........................................................................................... 203
8.14 Cleaning and maintenance guidelines for Ovation Controller cabinets .......................... 204
8.15 OCR400 Controller and OCR1100 Controller Modules .................................................. 205
8.15.1 To replace Controller modules ........................................................................... 206
8.16 User-supplied cabinets .................................................................................................... 206
9 Planning power for your Ovation cabinets 207

9.1 How is power distributed in an Ovation system? ............................................................ 207
9.1.1 OCR400 Controller/Marshalling cabinet (with local and remote cabling)
example .............................................................................................................. 208
9.1.2 Extended I/O cabinet (illustrating cables and standard I/O) example ................ 209
9.1.3 Extended I/O cabinet (illustrating cables and relay output modules) example .. 210
9.1.4 Ovation Remote Node cabinet (illustrating cables) example ............................. 211
9.1.5 Ovation Power Distribution Module (PDM) example ......................................... 212
9.1.6 Remote Node Transition Panel (dual-branch TND - top) (1P00028) ................. 213
9.1.7 Dual Branch I/O Transition Panel - top (ROP) (3A99266) ................................. 213
9.1.8 Controller OCR400 and Controller OCR1100 backplane example ................... 214
9.2 Connecting the power mains to an Ovation cabinet ....................................................... 214
9.2.1 To connect the AC/DC Mains to the input power DIN rail assembly ................. 214
9.3 Power supply front view .................................................................................................. 216
9.3.1 Diagnostic power supply LEDs .......................................................................... 217
OW360_R1005 v
Table of Contents
9.4 Power supply wiring illustration ....................................................................................... 218

9.5 Power supply wiring connections .................................................................................... 219
9.6 Functional diagram .......................................................................................................... 220
9.7 Power supply locking mechanism ................................................................................... 221
9.8 Power supply specifications ............................................................................................ 222
9.9 Power supply replacement cautions ............................................................................... 223
9.10 Using power supply modules .......................................................................................... 224
9.10.1 Power supply features ........................................................................................ 224
9.10.2 Power supply module ......................................................................................... 226
9.10.3 Power supply limits ............................................................................................ 226
9.10.4 Cabinet circuit breaker/on/off switch .................................................................. 227
9.10.5 Controller power switch ...................................................................................... 228
9.11 Power supply requirements (drawn from +24V main or auxiliary power supply) ............ 229
9.11.1 I/O cabinet components power supply requirements ......................................... 229
9.11.2 Analog I/O module power supply requirements ................................................. 231
9.11.3 Digital I/O module power supply requirements .................................................. 234
9.11.4 Bus interface module power supply requirements ............................................. 240
9.11.5 Specialty I/O module power supply requirements ............................................. 241
9.11.6 Power supply requirements for remote function modules .................................. 244
9.12 Monitoring power supply status....................................................................................... 244
9.12.1 Monitoring one set of redundant power supplies ............................................... 244
9.12.2 Monitoring two sets of redundant power supplies .............................................. 245
9.13 What is an external supply? ............................................................................................ 246
9.13.1 To prepare for connecting an external power supply ......................................... 247
9.14 Power distribution scheme .............................................................................................. 251
10 Planning for replacement parts and repair service 253

10.1 Ordering spare parts ....................................................................................................... 253
10.1.1 Determining a spare part number ...................................................................... 253
10.1.2 Determining a spare part price ........................................................................... 254
10.2 Returning parts to Emerson for repair service ................................................................ 254
10.2.1 Obtaining a Material Return Tracking (MRT) number ........................................ 255
10.2.2 Handling in-warranty and non-warranty part repairs .......................................... 256
10.3 Part failure during project startup .................................................................................... 257
10.4 Determining repair prices ................................................................................................ 257
10.5 Tracking part repairs ....................................................................................................... 257
11 Guidelines for shipping and storage of Ovation equipment 259

11.1 Shipping Ovation equipment guidelines .......................................................................... 259
11.2 Lifting Ovation equipment guidelines .............................................................................. 261
11.3 Off-loading and unpacking Ovation equipment ............................................................... 262
11.4 Repacking and returning Ovation equipment .................................................................. 262
11.5 Repacking third-party products ....................................................................................... 263
11.6 Transporting Ovation equipment to the specific installation location .............................. 263
11.7 Storing Ovation equipment .............................................................................................. 263
vi OW360_R1005
Table of Contents
12 Planning your CE Mark Certified and KC Compliance mark systems

265
12.1 CE Mark certified systems .............................................................................................. 265
12.2 CE Mark accuracy considerations................................................................................... 266
12.3 Third-party components usage in CE Mark Certified systems ........................................ 266
12.4 Grounding cable shields for CE Mark Certified systems ................................................ 267
12.4.1 Grounding panel (3A99245G01) method ........................................................... 267
12.4.2 Grounding panel configuration ........................................................................... 268
12.4.3 Alternative shield grounding ............................................................................... 270
12.5 Cabling requirements for CE Mark Certified systems ..................................................... 270
12.6 KC Compliance mark ...................................................................................................... 270
13 Planning your IEC61131-2 system 271

13.1 What is an IEC61131-2 certified system? ....................................................................... 271
13.2 Grounding cable shields for IE61131-2 certified system ................................................ 271
13.3 Cabling requirements for IEC61131-2 certified systems ................................................ 272
14 Planning to meet industry standards of compliance 273

14.1 Design standards ............................................................................................................ 273
14.2 Reliability standards ........................................................................................................ 273
14.3 Electrical interference standards ..................................................................................... 273
14.4 Safety standards ............................................................................................................. 273
14.5 Security standards .......................................................................................................... 274
15 Planning your internet addressing 275

15.1 Classes of internet addresses ......................................................................................... 275
15.2 Internet address notation ................................................................................................ 276
15.3 Allowable internet addresses .......................................................................................... 276
15.4 Internet address conventions .......................................................................................... 277
15.5 Subnet masks.................................................................................................................. 277
16 Planning your Ovation database 279

16.1 What is a Relational Database? ...................................................................................... 280
16.2 What are the types of Ovation Databases? .................................................................... 281
16.3 How does the Database relate to other Ovation functions? ........................................... 282
16.4 What is the organization of the Ovation database? ........................................................ 283
16.4.1 What is the Ovation Master Database schema?................................................ 283
16.4.2 What is the Ovation engineering tools audit schema? ....................................... 284
16.5 Database terminology ..................................................................................................... 285
16.6 What is a point? .............................................................................................................. 286
16.7 What are point records? .................................................................................................. 288
OW360_R1005 vii
Table of Contents
16.8 What is point frequency? ................................................................................................. 289

16.9 Understanding point names ............................................................................................ 289
16.10 Using valid Ovation point names..................................................................................... 290
16.11 Using fully qualified point names..................................................................................... 292
16.12 Creating the Ovation Database ....................................................................................... 292
16.12.1 Database tools ................................................................................................... 293
17 Planning software installation for Windows-based Ovation systems

295
17.1 What is involved in the Ovation installation process? ..................................................... 296
17.2 Software installation terminology .................................................................................... 296
17.3 Understanding disk storage ............................................................................................ 298
17.3.1 Disk partitioning .................................................................................................. 299
17.4 Best practices for installing Ovation 3.6.0 software ........................................................ 300
17.5 Hardware requirements for Domain Controllers (primary or redundant) ........................ 301
17.6 Hardware requirements for a domain member that is a Database Server ..................... 301
17.7 Software requirements for a Domain Controller (primary or redundant)......................... 302
17.8 Software requirements for a domain member ................................................................. 302
17.9 Licensing requirements for an Ovation Windows-based system .................................... 303
17.10 Hardware requirements for a domain member that is NOT a Database Server ............. 304
17.11 What is the drop type? .................................................................................................... 304
17.12 What is the Ovation Remote Station? ............................................................................. 305
17.12.1 Supported Ovation applications ......................................................................... 305
17.12.2 Hardware requirements for a Remote Station drop ........................................... 306
18 Planning control for your Ovation system 307

18.1 What is Ovation control? ................................................................................................. 308
18.2 What types of control are supported in Ovation? ............................................................ 309
18.3 What is the Ovation Control Builder? .............................................................................. 310
18.4 What is the role of the Control Builder in Ovation? ......................................................... 311
18.5 What is the control planning process? ............................................................................ 311
18.6 Using diagrams in planning control ................................................................................. 312
18.6.1 What are piping and instrumentation diagrams (P&ID)? ................................... 313
18.6.2 What are oil diagrams? ...................................................................................... 313
18.6.3 What are plant process schematics? ................................................................. 314
18.7 What is storyboarding for control? .................................................................................. 314
18.8 What are Ovation control functions (control sheets)? ..................................................... 315
18.9 Planning for system expansion ....................................................................................... 316
18.10 Control Builder terminology ............................................................................................. 316
18.11 What is the scope of your control project? ...................................................................... 319
18.12 What are the best practices for planning control? ........................................................... 320
18.13 What are the best practices for designing control? ......................................................... 321
18.14 What are the best practices for building control sheets? ................................................ 322
18.15 What are other control products? .................................................................................... 322
viii OW360_R1005
Table of Contents
19 Planning your Ovation Controller 325

19.1 What is the Ovation Controller? ...................................................................................... 326
19.2 Ovation Controller I/O interfaces ..................................................................................... 327
19.2.1 Network Interface ports ...................................................................................... 327
19.2.2 I/O interface ports ............................................................................................... 329
19.2.3 Small Form-factor Pluggable Transceivers (SFPs)? ......................................... 330
20 Planning Simulation 331

20.1 What is Scenario simulation? .......................................................................................... 331
20.1.1 What are the Simulation components? .............................................................. 331
20.1.2 What is the Simulation process? ........................................................................ 332
20.2 Scenario simulation model for high fidelity simulators .................................................... 333
20.3 Tie-back simulation model .............................................................................................. 334
21 Planning Virtual Controllers 335

21.1 What is Ovation Virtual Controller simulation? ................................................................ 335
21.1.1 Who uses Virtual Controller technology? ........................................................... 336
21.1.2 Why use Virtual Controllers?.............................................................................. 337
21.2 What is an Ovation Virtual Controller? ............................................................................ 338
21.3 What is an Ovation Virtual Controller Host? ................................................................... 338
21.4 What are the Virtual Controller commands? ................................................................... 339
21.5 What is the operation of the Virtual Controller? .............................................................. 340
21.6 What is the Virtual Controller Manager window? ............................................................ 341
21.7 Virtual Controller terminology .......................................................................................... 341
21.8 What are the architecture types of Ovation Virtual Controllers? ..................................... 342
21.8.1 What is the Virtual Controller single-machine architecture? .............................. 343
21.8.2 What is the Virtual Controller networked architecture? ...................................... 344
21.9 What are the requirements for Ovation Virtual Controllers? ........................................... 345
21.10 What are the hardware requirements for the Ovation Virtual Controller host? ............... 345
21.11 What are the software requirements for the Ovation Virtual Controller host? ................ 345
21.12 What are the Virtual Controller license types? ................................................................ 346
21.12.1 What is needed to license the Virtual Controller? .............................................. 346
22 Planning security for your Ovation system 347

22.1 What is external security? ............................................................................................... 348
22.2 What is Ovation internal security?................................................................................... 348
22.3 Security terminology ........................................................................................................ 349
22.4 What is Ovation hardening? ............................................................................................ 351
22.5 Using the domain concept in security ............................................................................. 351
22.6 What are the best practices for establishing a secure system? ...................................... 352
22.7 What is antivirus software? ............................................................................................. 352
22.7.1 Why is antivirus software important? ................................................................. 353
22.8 What is a RADIUS server? .............................................................................................. 353
OW360_R1005 ix
Table of Contents
23 Planning for an Ovation Process Historian (OPH) 355

23.1 Ovation Process Historian overview ............................................................................... 355
23.1.1 Functions performed by using the Ovation Process Historian ........................... 355
23.1.2 Advantages of the Ovation Process Historian ................................................... 356
23.2 Historian component overview ........................................................................................ 356
23.3 Historian terminology ...................................................................................................... 357
23.4 Hardware requirements for the historian ......................................................................... 359
23.5 Software requirements for the historian .......................................................................... 359
23.6 Historian server redundancy ........................................................................................... 360
23.7 How does the historian work? ......................................................................................... 361
23.8 Historian planning overview ............................................................................................ 361
23.9 How many historians do you need? ................................................................................ 362
23.9.1 Reasons to use multiple historians .................................................................... 362
23.9.2 Reasons to use a single historian for multiple units ........................................... 362
23.9.3 Reasons to use an embedded historian ............................................................ 362
23.9.4 Do you need redundant historian servers? ........................................................ 363
23.10 How many scanners do you need? ................................................................................. 363
23.11 How will you archive your data?...................................................................................... 364
23.12 Who are your end users? ................................................................................................ 365
23.13 Do you need to migrate eDB or HSR data to your new historian? ................................. 366
23.14 Will you need any third-party software? .......................................................................... 366
23.15 What are the Desktop Tools?.......................................................................................... 366
23.15.1 Do you want to use the Desktop Tools? ............................................................ 366
24 Planning for second generation (I/O module) Foundation Fieldbus 367

24.1 What is Foundation Fieldbus?......................................................................................... 368
24.1.1 Understanding Foundation Fieldbus interoperability ......................................... 369
24.1.2 Fieldbus terminology .......................................................................................... 370
24.2 Foundation Fieldbus second generation solutions.......................................................... 371
24.3 What are the Foundation Fieldbus and Ovation components? ....................................... 372
24.4 What is the Foundation Fieldbus communications model? ............................................ 374
24.4.1 Physical layer ..................................................................................................... 374
24.4.2 Data link and application layers ......................................................................... 375
24.4.3 User layer ........................................................................................................... 375
24.5 What is good Foundation Fieldbus segmentation design? ............................................. 376
24.5.1 Planning the Foundation Fieldbus topology ....................................................... 377
24.5.2 What should be Foundation Fieldbus I/O? ......................................................... 380
24.5.3 Partitioning instruments and applications .......................................................... 381
24.5.4 What are the recommended installation practices for Foundation Fieldbus? .... 381
24.6 What are the supported Fieldbus algorithms? ................................................................ 383
x OW360_R1005
Table of Contents
25 Planning for Profibus 385

25.1 What is Profibus? ............................................................................................................ 386
25.2 What is device interoperability? ...................................................................................... 387
25.3 What are the Profibus and Ovation components? .......................................................... 388
25.4 What are Profibus devices? ............................................................................................ 389
25.5 What is Profibus module redundancy? ........................................................................... 391
25.6 What is Profibus port redundancy? ................................................................................. 394
25.7 What are Profibus hardware and software requirements? ............................................. 395
25.8 To support acyclic exchange of data .............................................................................. 395
26 Planning for DeviceNet 397

26.1 What is DeviceNet? ......................................................................................................... 398
26.2 What is field device interoperability? ............................................................................... 399
26.3 What is DeviceNet messaging? ...................................................................................... 399
26.4 What are the DeviceNet communication methods? ........................................................ 399
26.5 What are the DeviceNet and Ovation components? ....................................................... 401
26.6 What is a DeviceNet module? ......................................................................................... 402
26.7 What are the DeviceNet hardware and software requirements? .................................... 402
27 Planning alarm management 403

27.1 What is an alarm? ........................................................................................................... 404
27.1.1 What is an example of the life of an alarm? ....................................................... 404
27.2 What is alarm management? .......................................................................................... 405
27.3 What are some alarm management problems? .............................................................. 405
27.4 What are some best practices for planning alarms? ....................................................... 406
27.4.1 Establishing a philosophy for alarm management ............................................. 406
27.5 What points can be used as alarms? .............................................................................. 407
27.5.1 When is a point out of service? .......................................................................... 407
27.6 How does the Ovation alarm system operate? ............................................................... 408
27.7 Types of alarm displays .................................................................................................. 408
27.8 Alarm list information fields ............................................................................................. 409
27.9 Displaying Alarm lists ...................................................................................................... 409
27.10 Alarm lists that display in the Alarm window ................................................................... 410
27.10.1 Alarm List in the Operator Station Alarm window .............................................. 412
27.10.2 History list in the Operator Station Alarm window .............................................. 413
27.10.3 Acknowledged list in the Operator Station Alarm window ................................. 414
27.10.4 Unacknowledged list in the Operator Station Alarm window ............................. 415
27.10.5 Reset list in the Operator Station Alarm window ............................................... 416
27.10.6 Alarm Check Remove list in the Operator Station Alarm window ...................... 417
27.10.7 Alarm Frequency list in the Operator Station Alarm window ............................. 418
27.10.8 Iconic list in the Operator Station Alarm window ............................................... 418
27.11 Remote Network Status list in the Operator Station Alarm window ................................ 420
27.12 What is Alarm Suppression? ........................................................................................... 421
27.13 What is Alarm Shelving? ................................................................................................. 421
OW360_R1005 xi
Table of Contents
27.14 What is the Alarm Annunciation window at the Operator Station? ................................. 422
27.15 What are some best practices for managing alarms?..................................................... 423
27.16 What are nuisance alarms? ............................................................................................ 424
27.16.1 What methods can be used to manage nuisance alarms? ................................ 424
27.17 What are alarm floods? ................................................................................................... 424
27.17.1 What are suggested alarm rates? ...................................................................... 424
27.17.2 Configuring filtering for alarms ........................................................................... 425
27.17.3 Using audio for situation awareness .................................................................. 427
27.17.4 What are the methods used to log alarms? ....................................................... 427
27.17.5 Using security for alarm management ............................................................... 428
27.17.6 Using PlantWeb Alerts for Fieldbus alarms ....................................................... 428
27.17.7 Setting alarm limits ............................................................................................. 429
27.17.8 What methods are available to reduce the number of alarms in your system? . 430
27.17.9 What are the benefits of good alarm management? .......................................... 432
27.18 What is the Alarm Health Advisor? ................................................................................. 433
27.18.1 What is the benefit of using the Alarm Health Advisor? ..................................... 433
27.18.2 Functions of the Alarm Health Advisor ............................................................... 433
27.19 What is the Alarm Guidance window? ............................................................................ 434
27.20 What is Remote Alarm Viewer? ...................................................................................... 434
28 Planning Connectivity for your Ovation system 435

28.1 What is Ovation Connectivity? ........................................................................................ 435
28.1.1 What are the available platforms for an Ovation communication interface? ..... 435
28.1.2 What are the physical connection options for an Ovation communication
interface?............................................................................................................ 436
28.1.3 What are the current message protocols for an Ovation communication
interface?............................................................................................................ 436
28.2 Communication interface spreadsheets .......................................................................... 437
28.2.1 Hardware/Device spreadsheet ........................................................................... 438
28.2.2 Release version spreadsheet ............................................................................ 440
29 Planning your Ovation Security Center 443

29.1 What is the Ovation Security Center? ............................................................................. 443
29.2 Hardware and software components of the Ovation Security Center ............................. 444
29.3 Appliances in the Ovation Security Center ..................................................................... 444
29.4 Terminology for the Ovation Security Center .................................................................. 445
30 Planning your Safety Instrumented System 449

30.1 What is a Safety Instrumented System? ......................................................................... 449
30.2 Functions of Ovation SIS ................................................................................................ 450
30.3 Safety Instrumented System terminology ....................................................................... 450
30.4 SIS aspects to consider .................................................................................................. 452
30.4.1 Safety Instrumented Functions (SIFs) ............................................................... 453
30.4.2 Safety Integrity Levels (SILs) ............................................................................. 453
xii OW360_R1005
Table of Contents
30.5 Capacities for Ovation SIS system ................................................................................. 453

30.6 SIS environmental specifications for Ovation SIS devices ............................................. 454
30.7 SIS System...................................................................................................................... 454
30.8 Supported SIS network ................................................................................................... 455
30.8.1 SIS Network with four (4) SIS Switches ............................................................. 455
30.8.2 SIS Network with three (3) SIS Switches ........................................................... 465
30.8.3 SIS Network with two (2) SIS Switches ............................................................. 472
30.8.4 SIS Network with one (1) SIS Switch ................................................................. 476
30.8.5 Hardware cabinet design example ..................................................................... 480
30.9 Planning the SIS hardware installation ........................................................................... 485
30.9.1 Installation tools ................................................................................................. 485
30.10 Hardware components of Ovation SIS ............................................................................ 486
30.11 Software components of Ovation SIS ............................................................................. 488
30.12 What are Ovation SIS Logic Solver algorithms? ............................................................. 489
31 Planning your Safety Instrumented System (SIS) with Electronic

Marshalling 493
31.1 What is a Safety Instrumented System with Electronic Marshalling? ............................. 493
31.2 Functions of Ovation SIS with Electronic Marshalling..................................................... 494
31.3 SIS with Electronic Marshalling aspects to consider....................................................... 494
31.3.1 Safety Instrumented Functions (SIFs) ............................................................... 495
31.3.2 Safety Integrity Levels (SILs) ............................................................................. 495
31.4 Capacities for Ovation SIS with Electronic Marshalling system ...................................... 496
31.5 SIS environmental specifications for Ovation SIS with Electronic Marshalling devices . 497
31.6 Supported SIS Local Safety Network .............................................................................. 497
31.7 Hardware components of Ovation SIS with Electronic Marshalling ................................ 499
32 Planning your Virtual Safety Instrumented System 505

32.1 What is Virtual Safety Instrumented System?................................................................. 505
32.2 Functions of Virtual SIS ................................................................................................... 506
32.3 Virtual SIS terminology.................................................................................................... 506
32.4 Rules for working with Virtual SIS ................................................................................... 507
32.5 Hardware requirements for Virtual SIS ........................................................................... 507
32.6 Software requirements for Virtual SIS ............................................................................. 508
32.7 Ovation requirements for Virtual SIS .............................................................................. 508
32.8 Reporting issues ............................................................................................................. 508
33 Planning your Virtual Safety Instrumented System (SIS) with

Electronic Marshalling 509
33.1 What is Virtual Safety Instrumented System with Electronic Marshalling? ..................... 509
33.2 Functions of Virtual SIS CHARMs................................................................................... 510
33.3 Terminology of Virtual SIS CHARMs .............................................................................. 510
33.4 Rules for working with Virtual SIS CHARMs ................................................................... 510
33.5 Hardware requirements for Virtual SIS CHARMs ........................................................... 511
OW360_R1005 xiii
Table of Contents
33.6 Software requirements for Virtual SIS CHARMs ............................................................. 511

33.7 Licensing requirements for Virtual SIS CHARMs ............................................................ 512
33.7.1 Overview of planning the Virtual SIS CHARMs system ..................................... 512
33.7.2 Virtual SIS CHARMs with hardware-based Ovation .......................................... 512
33.7.3 Virtual SIS CHARMs with Virtual Ovation .......................................................... 513
34 Planning your System Backup and Restore 515

34.1 Why perform Ovation system backups? ......................................................................... 515
34.2 Backing up and restoring the system .............................................................................. 516
34.3 What are the programs involved in backup and restore operations? ............................. 516
34.4 Restoring Active Directory Domain Services (AD DS) (Domain Controllers) ................. 517
34.4.1 Criteria for using the restore type ....................................................................... 518
35 Ovation hardware specification sheets 519

35.1 Hardware specification sheets overview ......................................................................... 519
35.2 Cabinets, vented, NEMA12 with standard mounting plate ............................................. 520
35.2.1 NEMA12, vented, 2000 mm x 600 mm x 400 mm, (front access only) Hoffman
(5X00068H01/H02) ............................................................................................ 521
35.2.2 NEMA12, vented, 2000 mm x 600 mm x 400 mm, Rittal (1X00903H01) .......... 522
35.2.3 NEMA 12, vented, 2000 x 600 x 500 mm, Hoffman (5X00018H01) .................. 523
35.2.4 NEMA12, vented, 2000 mm x 600 mm x 600 mm, Hoffman
(5X00127H01/H02) ............................................................................................ 524
(5X00021H02/H04) ............................................................................................ 526
35.2.8 NEMA12, vented, 2000 mm x 914 mm x 600 mm, Hoffman (1X00454H02) ..... 528
35.2.10 NEMA12, EMC cabinet, vented, 2000 mm x 600 mm x 600 mm, Rittal
(1X00520H01) .................................................................................................... 530
35.3 Cabinets, vented, NEMA12 with Marshalling mounting plate ......................................... 531
(5X00021H01/H03) ............................................................................................ 532
35.4 Cabinets, sealed, NEMA12 with standard mounting plate .............................................. 536
35.4.1 NEMA12, sealed, 2000 mm x 600 mm x 500 mm, Hoffman (5X00019H01) ..... 537
35.4.2 NEMA12, sealed, 2000 mm x 600 mm x 600 mm, Hoffman
(5X00046H01/H03) ............................................................................................ 538
35.4.3 NEMA12, sealed 2000 mm x 600 mm x 600 mm, Rittal (1X00902H01) ........... 539
(5X00035H03/H07) ............................................................................................ 540
35.4.5 NEMA12, sealed, 2000 mm x 800 mm x 600 mm, Rittal (1X00905H03) .......... 541
35.4.8 NEMA12, EMC cabinet, sealed, 2000 mm x 600 mm x 600 mm, Rittal
(1X00520H02) .................................................................................................... 544
xiv OW360_R1005
Table of Contents
35.5 Cabinets, sealed, NEMA12 with Marshalling mounting plate ......................................... 545
(5X00035H01/H05) ............................................................................................ 546
35.6 Cabinets, sealed, NEMA4 with standard mounting plate ................................................ 550
35.6.1 NEMA4, sealed, 2000 mm x 600 mm x 500 mm, Hoffman (5X00019H02) ....... 551
35.6.2 NEMA4, sealed, 2000 mm x 600 mm x 600 mm, Hoffman (5X00046H02/H04) 552
35.6.3 NEMA4, sealed, 2000 mm x 600 mm x 600 mm, Rittal (1X00902H02) ............ 553
35.7 Cabinets, sealed, NEMA4 with Marshalling mounting plate ........................................... 558
35.8 Cabinets, vented, NEMA12 with no mounting plate........................................................ 563
35.8.1 NEMA12, vented, 2000 mm x 600 mm x 600 mm, Hoffman (
5X00020H01/H02) ............................................................................................. 564
35.8.3 NEMA12, vented, 2000 mm x 600 mm x 600 mm, (without mounting plate) Rittal
(1X00901H01) .................................................................................................... 566
35.9 Ovation Workstation Cabinet vented (1X00518) ............................................................. 567
35.10 Ovation Server Cabinet vented (1X00545) ..................................................................... 567
35.11 Ovation workstation specification sheets ........................................................................ 568
35.11.1 Dell PowerEdge T320 (5X00618) ...................................................................... 569
35.11.2 Dell PowerEdge T110 II (5X00659) .................................................................. 570
35.11.3 Dell OptiPlex 9020 (5X00673)............................................................................ 571
35.11.4 Dell OptiPlex 3020 (5X00678)............................................................................ 571
35.11.5 Dell PowerEdge T320 (5X00619) ...................................................................... 572
35.11.6 Dell PowerEdge T630 (Linux Server) (5X00720)............................................... 572
35.11.7 Dell PowerEdge T630 (Windows Server) (5X00721) ........................................ 573
35.11.8 Dell PowerEdge R730 (Rack Mount) (5X00727) ............................................... 574
35.11.9 Dell Precision R7910 (Rack Mount) (5X00729) ................................................. 574
35.11.10 Dell PowerEdge R730 (Rack Mount) (5X00728) ......................................... 575
35.11.14 Dell PowerEdge R720 (Rack Mount) (Linux Server) (5X00722) .................. 577
35.11.15 Dell PowerEdge R720 (Rack Mount) (Windows Server) (5X00723)............ 577
35.11.16 Phoenix Contact Valueline PC (Panel Mount) (1X00919) ........................... 578
35.11.17 Phoenix Contact PC with display Windows 7 (VL2 PPC 3000) (1X01011) . 578
35.12 Monitor specification sheets ............................................................................................ 579
35.12.1 Dell U3014 (30" Desktop LCD Monitor) (1X00922) ........................................... 579
35.12.2 Dell U2412M (24" Desktop LCD Monitor) (1X00920) ........................................ 580
35.12.3 Dell P2213H (22" Desktop LCD Monitor) (1X00923) ......................................... 580
35.12.4 Dell P2014H (20" Desktop LCD Monitor) (1X00894) ......................................... 581
35.12.5 Dell P1914S (19" Desktop LCD Monitor) (1X00898) ......................................... 581
35.12.6 NEC P553 (55" Large Screen LCD Monitor) (5X00749).................................... 582
35.12.7 NEC P463-AVT (46" Large Screen LCD Monitor) (5X00697) ........................... 582
OW360_R1005 xv
Table of Contents
35.12.8 NEC P403 (40" Large Screen LCD monitor) (5X00718).................................... 583
35.12.9 NEC V323 (32" Large Screen LCD monitor) (5X00716).................................... 583
35.13 Keyboard specification sheet .......................................................................................... 584
35.13.1 Ovation Keyboard (4D33935) ............................................................................ 584
35.14 Printer specification sheets ............................................................................................. 585
35.14.1 HP Color Officejet 7612 Wide Format e-All-in-one (1X00995) .......................... 585
35.14.2 HP Color Laserjet Enterprise M750 (5X00677) ................................................. 586
35.14.3 HP Color Laserjet Enterprise CP4025n/CP4025dn (1X00989) ......................... 586
35.14.4 Okidata Microline 395C (5X00445) .................................................................... 586
35.14.5 HP B/W Laserjet M712n (5X00639) ................................................................... 587
35.15 Storage device specification sheets ................................................................................ 588
35.15.1 NAS/iSCSI RAID 5 SATA Storage (5X00683) ................................................... 588
35.16 Miscellaneous specification sheets ................................................................................. 589
35.16.1 Dell Precision M6800 Laptop Workstation (1X00895) ....................................... 589
35.16.2 Spectracom SecureSync GPS Modular Time Synchronization System
(1X00932)........................................................................................................... 589
35.17 Ovation I/O module environmental specifications ........................................................... 590
35.18 Cable specification sheets .............................................................................................. 590
35.18.1 Network Fiber-Optic cable specifications (5A26164Gxx) .................................. 591
35.18.2 Network UTP cable specifications ..................................................................... 592
35.18.3 Network Remote I/O cable specifications .......................................................... 593
Index 595
xvi OW360_R1005
S E C T I O N 1
1 Introduction to planning your Ovation system
IN THIS SECTION
What is an Ovation system? ............................................................................................... 1

What are the components of an Ovation system? .............................................................. 2
Planning the elements of an Ovation system ...................................................................... 5
Ovation system terminology ................................................................................................ 7
Ovation reference documentation ..................................................................................... 10
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.
Ovation is the control industry’s most reliable and responsive real-time plant monitoring and
process control system that uses commercially available hardware platforms, operating systems,
and open network technology.
You can expand a small Ovation installation to include as many as 254 intelligent modules
(referred to as drops). Each drop is a separate module that can perform various control functions.
You should consider the following elements when you plan and configure your Ovation system:
 A 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.
 Controllers 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 specific questions about your Ovation system.
OW360_R1005 1
1.2 What are the components of an Ovation system?
1.2 What are the components of an Ovation s ystem?
The Ovation system consists of different types of workstations that are linked to each other
through a high-speed network. These workstations perform different functions and send data
throughout the entire network to communicate the results of these functions. 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:
 Ovation network (see page 2)
 Ovation database (see page 3)
 Ovation input/output modules (see page 3)
 Ovation Controller (see page 3)
 Ovation Operator Station (see page 4)
 Developer Studio (Windows) (see page 4)
 Historical storage and reporting capabilities (see page 5)
 Third-party devices (see page 5)
 Connectivity products (see page 5)
1.2.1 Ovation network
The Ovation network connects the components of the Ovation system so that all components can
communicate with each other in real time.
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.
2 OW360_R1005
1.2.2 Ovation database
The Ovation database provides the capability to integrate and organize massive amounts of raw
data in the system to create meaningful and valuable information.
The Ovation database consists of a Master database that uses Oracle software for its relational
database. The Master database contains the system configuration, control algorithm information,
and the process point database.
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. (Refer to the Ovation Database User
Guide.)
1.2.3 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 cabinets that are up to 2,000 meters away from the Controller. (Refer
to the Ovation I/O Reference Manual and Ovation Bus and Specialty I/O Reference Manual.)
1.2.4 Ovation Controllers
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. (Refer to the Ovation Controller User Guide.)
OW360_R1005 3
1.2.5 Ovation Operator Stations
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 such as:
 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.
1.2.6 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.
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).
 Loads control and originating point information into Ovation drops and links the Master
Database with other drops within the system.
 Force Controller changes (online) into the database.
 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. (Refer to the
Ovation Developer Studio User Guide.)
4 OW360_R1005
1.3 Planning the elements of an Ovation system
1.2.7 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. (Refer to the applicable Ovation Process Historian User Guide.)
1.2.8 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, Modbus, RTP I/O, Toshiba, and MHI
devices.
1.2.9 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.
The planning and configuration of process control equipment within a specific Ovation system
determines the system’s response to the controlled process. The system designer must have a
detailed and extensive 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 13).
 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.
 Number of workstations (up to 254).
 Type of workstations.
 Distribution of workstations.
 Monitors.
 Keyboards.
 Printers.
 Storage devices for Ovation data.
OW360_R1005 5
 Ovation cabinets.
 Ovation Network guidelines (see page 56).
 System-wide compatibility between cable (see page 87), 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.
 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 Prescribes guidelines for the design, evaluation, and testing
“Safety Functions Incorporating of electronic safety functions. It applies to individual
Electronic Technology” 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
Loss Prevention Data systems and industrial equipment. It includes installation and
5-27/14-27 maintenance practices, and methods of improving reliability
with redundant components and systems.
Factory Mutual Engineering Corp. Contains descriptions of and recommendation for oil and
gas-fired multiple burner boilers.
Loss Prevention Data 6-5
Industrial Risk Insurers IR Information Provides guidance in evaluating the safety of programmable
P.3.8 “Programmable Logic Controllers logic controllers in burner management systems. It also
for Use with Burner Management provides information regarding potential failures modes.
Systems (April 3, 1987)
American National Standards Covers single and multiple burner boilers.
Institute/National Fire Protection
Association Standard ANSI/NFPA
Numbers 85A through 85I
American National Standards Covers ovens and furnaces.
Institute/National Fire Protection
Association Standard ANSI/NFPA
Number 86C
Any industry accepted manual describing Covers different types of networks.
Fast Ethernet and Gigabit Ethernet
networks.
6 OW360_R1005
1.4 Ovation system terminology
1.4 Ovation s ystem terminology

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.
A Side Refers to the left side board-to-board connector of the base unit when the terminal
block or AUI Cable connector is facing the viewer. It can also refer to the Controller
cabinet or the "A" cabinet.
AWG American wire gauge is used in the United States as a standard method of denoting
wire diameter. Increasing gauge numbers give decreasing wire diameters. Outside of
North America, wire sizes for electrical purposes are usually given as the cross
sectional area in square millimeters.
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. It can also refer to the Termination
cabinet or the "B" cabinet.
Base unit The DIN Rail mounted Ovation Base serves as the mechanical means to hold and
secure the Ovation I/O electronics and personality modules while providing an
electrical interface between a customer's field connections, Ovation I/O Controller,
and transition panels.
The Ovation Bases, when connected together, form the Ovation I/O bus used by the
Ovation Controller to communicate with its I/O subsystem and to distribute power to
the I/O modules.
Each standard two-slot base can house up to two sets of electronic and personality
I/O modules, while four-slot base units can house up to four sets of I/O modules.
Baud rate Number of bits-per-second a modem can send or receive.
Branch A set of two four-slot base units or four standard two-slot bases configured
consecutively on a DIN rail with a local Ovation I/O bus being connected to the
Ovation Controller. A maximum of eight I/O modules is supported on a branch.
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 Ovation I/O modules that do not contain a Personality module, only an Electronics
modules 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 (OCR1100 or OCR400) passes
process control information over the network to other drops or devices that need it.
OW360_R1005 7
TERM DESCRIPTION
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 Contains a subset of the information stored on the Master Database. A Distributed
Database Database is present on each drop in the system and is continually updated as point
information changes.
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)
Dual attachment Connection to two different switches. A Dual Attached Station (DAS) is a node that is
connected to two different switches.
Electronics Portion of an I/O module that provides a plastic housing with associated lenses and
module 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. The
OCR400 and OCR1100 Controller uses only one IOIC module.
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 Also known as the Ovation Keyboard. Optional keyboard that is used in conjunction
Keyboard with the standard keyboard and mouse. It allows the operator to access data
acquisition and control applications.
8 OW360_R1005
TERM DESCRIPTION
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.
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 Configuration tool that houses all of the integrated engineering tools necessary for a
Studio 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 400 uses only one IOIC card.
Personality Portion of an I/O module that provides a plastic housing with associated lenses and
module 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 through media that
can carry control signals over a long distance (for example, fiber-optic).
OW360_R1005 9
TERM DESCRIPTION
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.
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.
10 OW360_R1005
1.5 Ovation reference documentation
1.5 Ovation reference documentation

The Planning Your Ovation System reference manual is intended to give you an overview of the
entire Ovation system. Since Ovation is a complex and powerful system, detailed information on
each application cannot be contained in one manual.
The following manuals may provide more information about various topics in this manual:
 Software Installation Manual for Ovation.
 Ovation Database User Guide.
 Ovation Operator Station User Guide.
 Foundation Fieldbus User Guide.
 PlantWeb Alerts User Guide.
 Profibus User Guide.
 DeviceNet User Guide.
 Managing Security for Ovation.
 Safety Instrumented System (SIS) User Guide.
 Virtual Safety Instrumented System (SIS) User Guide.
 Safety Instrumented System (SIS) with Electronic Marshalling User Guide.
 Virtual Safety Instrumented System (SIS) with Electronic Marshalling User Guide.
 Ovation Simulation User Guide.
 Ovation Virtual Controller User Guide.
 Ovation Controller User Guide.
 Ovation Developer Studio User Guide.
 Ovation Multiple Networks User Guide.
 Ovation Control Builder User Guide.
 Ovation Graphics Builder User Guide.
 Ovation Standard Algorithms Reference Manual.
 Ovation Specialty Algorithms Reference Manual.
 Ovation Record Types Reference Manual.
 Ovation I/O Reference Manual.
 Q-Line I/O to Ovation I/O Migration Reference Manual.
 Ovation Bus and Specialty I/O Reference Manual.
 Maintaining Your Ovation System.
 Alarm Health Advisor User Guide.
 APC Toolkit User Guide.
 Ovation Process Historian User Guide.
 Ovation Security Center User Guide.
 Using Kaspersky Antivirus Software with Ovation.
 System Backup and Recovery User Guide.
 Ethernet Link Controller (ELC) User Guide.
 SCADA User Guide.
OW360_R1005 11
S E C T I O N 2
2 Planning your Ovation equipment
IN THIS SECTION
Selecting equipment locations .......................................................................................... 13

Protecting the Ovation equipment ..................................................................................... 13
Electrical information for Ovation equipment .................................................................... 15
2.1 Selecting equipment locati ons

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
259).
Note: Most Ovation equipment is designed to meet the industry standards for shock (IEC 68-2-
6) and vibration (IEC-68-2-27).
 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).
 Ensure all intake and exhaust ports are unobstructed, so that fans within the enclosures
operate properly to provide forced-air cooling.
OW360_R1005 13
2.2 Protecting the Ovation equipment
2.2 Protecting the Ovation equipment
You must be able to monitor and control temperature and humidity at storage sites and at the
equipment’s 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.
 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 gasses, 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 self-
contained 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.
For more information on operating and storage temperature, vibration and shock, refer to the
Planning Your Ovation System manual. Note that all devices are subject to change as new
technology is constantly improving and evolving.
14 OW360_R1005
2.3 Electrical information for Ovation equipment
The following sections provide tables containing electrical information for Ovation equipment. The
tables list main/auxiliary power and main/auxiliary heat dissipation.
 I/O cabinet components (see page 16).
 Analog I/O modules (see page 18).
 Digital I/O modules (see page 22).
 Bus interface modules (see page 31).
 Specialty I/O modules (see page 32).
 Remote function modules (see page 36).
See Calculating Ovation main power requirements (see page 37) for instructions on using these
values to calculate power requirements for populated Ovation I/O cabinets.
Do NOT use the following tables to determine the power drawn from the internal +24V Power
Supply. See I/O cabinet components power supply requirements (see page 229).
In the following tables, (E) designates Electronics modules and (P) designates Personality
modules. Values are rounded to the next tenth.
CAUTION! Access to the inside of Ovation cabinets should be limited to qualified, trained
personnel only.
2.3.1 Understanding heat dissipation
The heat dissipation values provided in the I/O module tables are based on the following:
 An Ovation I/O module's Main heat dissipation specification (BTU/h) is the sum of the
following heat dissipation sources:
 Module's heat dissipation due to the 24 V 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 Auxiliary (Aux) heat dissipation specification (BTU/h) is the sum of
the following heat dissipation sources:
 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: Refer to the Ovation I/O Reference Manual for additional information.
OW360_R1005 15
2.3.2 I/O cabinet components (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 cabinet’s AC or DC Mains power
supply when the component is installed within the cabinet. See Calculating main power
requirements (see page 37) 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.
Electrical specifications for Ovation I/O cabinet components

(power supply efficiency is included)
COMPONENT EMERSON MAIN +24 AUX POWER MAIN AUX

P ART POWER (W) AND VA2 HEAT HEAT
NUMBER (W) AND (TYPICAL) DISSIPATION DISSIPATION
VA (TYPICAL (TYPICAL)
(TYPICAL)
Controller Cabinet (cabinet N/A 24 W/VA N/A 82 BTU/h N/A

+ power supply fans)
OCR1100 or
OCR400 Controller
Marshalling Cabinet N/A 24 W/VA N/A 82 BTU/h N/A
(cabinet + power supply
fans)
Extended I/O Cabinet N/A 24 W/VA N/A 82 BTU/h N/A
fans)
Remote I/O Cabinet N/A 24 W/VA N/A 82 BTU/h N/A
(ventilated) (cabinet +
power supply fans)
Remote I/O Cabinet N/A 32 W/VA N/A 109.2 BTU/h N/A
(sealed) (cabinet + power
supply fans)
EMC Controller Cabinet N/A 24 W/VA N/A 82 BTU/h N/A
fans)
EMC Extended I/O N/A 24 W/VA N/A 82 BTU/h N/A
Cabinet (cabinet + power
supply fans)
EMC Remote I/O Cabinet N/A 24 W/VA N/A 82 BTU/h N/A
(ventilated) (cabinet +
power supply fans)
16 OW360_R1005
COMPONENT EMERSON MAIN +24 AUX POWER MAIN AUX

P ART POWER (W) AND VA2 HEAT HEAT
NUMBER (W) AND (TYPICAL) DISSIPATION DISSIPATION
VA (TYPICAL (TYPICAL)
(TYPICAL)
EMC Remote I/O Cabinet N/A 32 W/VA N/A 109.2 BTU/h N/A
(sealed) (cabinet + power
supply fans)
Single OCR 400 5X00241 25 W/VA N/A 85.4 BTU/h N/A
Controller:
1 Processor card
1 IOIC card
1 Fan
Dual OCR 400 Controller: 5X00241 50 W/VA N/A 170.8 BTU/h N/A
2 Processor cards
2 IOIC cards
2 Fans
Single OCR 1100 5X00481 25 W/VA N/A 85.4 BTU/h N/A
Controller:
1 Processor card
1 IOIC card
1 Fan
Dual OCR 1100 5X00481 50 W/VA N/A 170.8 BTU/h N/A
Controller:
2 Processor cards
2 IOIC cards
2 Fans
Redundant Remote Node 1C31203 16 W/VA N/A 54.6 BTU/h N/A
Controller module (in (E)
Remote Node Cabinet)
1C31204G
01, G03
(P)
Redundant MAU module 1C31179 18 W/VA N/A 60 BTU/h N/A
(Controller cabinet) (E)
1C31181
G01-G04
(P)
OW360_R1005 17
2.3.3 Analog I/O modules (main/aux power and main/aux heat dissipation) (drawn
from AC/DC Mains power)
The following table lists the power an analog input/analog output module draws from a cabinet's
AC or DC Mains power supply when the module is installed within the cabinet.
Electrical information for Ovation 1 Analog I/O modules

(A 75% power supply efficiency is included)
COMPONENT EMERSON PART MAIN +24 AUX POWER MAIN HEAT AUX HEAT
NUMBER POWER (W) AND VA2 DISSIPATION DISSIPATION
(W) AND (TYPICAL) (TYPICAL) (TYPICAL)
VA
(TYPICAL)
Analog Input (13- 1C31113G01 (E) 3.4 W/VA Not applicable 11.6 BTU/h N/A for voltage
bit) input channels.
1C31116G01 (P)
(± 20mV) 0.41 BTU/h4 per
field powered
mA channel.
Analog Input (13- 1C31113G02 (E) 3.4 W/VA Not applicable 11.6 BTU/h N/A for voltage
1C31116G01 (P)
(± 50mV) 0.41 BTU/h4 per
field powered
mA channel.
Analog Input (13- 1C31113G03 (E) 3.4 W/VA N/A 11.6 BTU/h N/A for voltage
1C31116G01
(± 100mV) (P) 0.41 BTU/h4 per
field powered
mA channel.
Analog Input (13- 1C31113 3.4 W/VA Not applicable 11.6 BTU/h N/A for voltage
bit) G01-G06 (E) input channels.
T/C, Volts and 1C31116G01, 0.41 BTU/h4 per
Field Powered mA G02, G04 (P) field powered
mA channel.
Analog Input (13- 1C31113G05 (E) 3.4 W/VA 0.64 W/VA 3 11.6 BTU/h 0.96 BTU/h3
bit) per locally per locally
1C31116G03 (P)
Local Powered mA powered powered mA
channel channel
Analog Input (14- 1C31224G02 (E) 3.2 W/VA Not applicable 10.9 BTU/h Not applicable
bit)
1C31227G02 (P)
Volts (+/- 1 Volt)
Analog Input (14- 1C31224G01 (E) 3.2 W/VA 0.64 W/VA 3 10.9 BTU/h 0.41 BTU/h3, 4
bit) per locally per field
1C31227G01 (P)
Field and Local powered powered
Powered mA channel. Not channel
applicable for
field-powered 0.96 BTU/h 3
channels. per locally
powered
channel
18 OW360_R1005
VA
(TYPICAL)
Analog Input (14- 5X00070G02 (E) 3.2 W/VA Not applicable 10.9 BTU/h Not applicable
bit) (High Speed)
1C31227G02 (P)
(± 100mV, ±
250mV, ± 1V Volt)
bit) (High Speed)
1C31227G02 (P)
(± 5V, ± 10V Volt)
Analog Input (14- 5X00070G01 (E) 3.2 W/VA 0.64 W/VA 3 10.9 BTU/h 0.41 BTU/h3, 4
bit) (High Speed) per locally per field
1C31227G01 (P)
Field and Local powered powered
Powered mA channel. Not channel
applicable for
field-powered 0.96 BTU/h 3
channels. per locally
powered
channel
bit) (Medium
Speed) 1C31116G04 (P)
(± 20mV, ± 50mV,
± 100V)
(Thermocouple)
bit) (Medium
Speed) 1C31116G04 (P)
(± 20mV, ± 50mV,
± 100V)
(Thermocouple)
bit) (Medium
Speed) 1C31116G01 (P)
(± 20mV, ± 50mV,
± 100V)
Analog Input (14- 5X00070G02 (E) 3.2 W/VA 0.032 W/VA 10.9 BTU/h 0.028 BTU/h3
bit) (High Speed) per channel per channel
1C31116G03 (P)
(± 1mA 2 wire local
powered)
Analog Input (14- 5X00070G02 (E) 3.2 W/VA Not applicable 10.9 BTU/h 0.001 BTU/h4
bit) (High Speed) per channel
1C31116G02 (P)
(± 1mA 4 wire field
powered)
OW360_R1005 19
VA
(TYPICAL)
10V High
Impedance (8 1C31227G02 (P)
channel)
HART Analog 5X00058G01 (E) 1.6 W/VA 2.4 W/VA plus 5.5 BTU/h 8.2 BTU/h plus
Input
5X00059G01 (P) 0.64 W/VA3 0.41 BTU/h3, 4
per locally per field
powered powered
channel. channel
and
1.27 BTU/h3
per locally
powered
channel
HART High 5X00106G01 (E) 5.5 W/VA 0.64 W/VA per 18.7 BTU/h 0.41 BTU/h3, 4
Performance locally powered per field
Analog Input 5X00109G01 (P) channel. Not powered
applicable for channel
field powered
channels. 0.96 BTU/h3
per locally
powered
channel
HART High 5X00106G02 (E) 5.5 W/VA 0.64 W/VA per 18.7 BTU/h 0.41 BTU/h3, 4
Performance locally powered per field
Analog Input 5X00109G01 (P) channel. Not powered
applicable for channel
field powered
channels. 0.96 BTU/h3
per locally
powered
channel
Analog Output 1C31129G01, 2.7 W/VA Not applicable 9.2 BTU/h Not applicable
G02 (E)
(Voltage)
1C31129G05 (E)
(4 to 20mA
Redundant)
1C31132G01 (P)
Analog Output 1C31129G03, 5.4 W/VA Not applicable 18.4 BTU/h Not applicable
G04 (E)
(Current)
1C31132G01 (P)
HART Analog 5X00062G01 (E) 1.6 W/VA 8 W/VA 5.5 BTU/h 27.2 BTU/h
Output
5X00063G01 (P)
20 OW360_R1005
VA
(TYPICAL)
HART High 5X00167G01 (E) 6.1 W/VA Not applicable 20.8 BTU/h Not applicable
Performance
Analog Output 1X00188H01
(cavity insert)
RTD Input 1C31161G01 (E) 4.8 W/VA Not applicable 16.3 BTU/h Not applicable
(4 channels) 1C31164G01 (P)
RTD Input 1C31161G02 (E) 4.8 W/VA Not applicable 16.3 BTU/h Not applicable
(50Hz/60Hz 1C31164G02 (P)
filtered inputs)
(4 channels)
RTD Input 5X00119G01 (E) 3.6 W/VA Not applicable 12.3 BTU/h Not applicable
(8 channels) 5X00119G02 (E)
5X00121G01 (P)
RTD Input 5X00621G01 (E) 2.0 W/VA Not applicable 6.8 BTU/h Not applicable
(8 channels 1X00885H01
Compact) (Cavity insert)
RTD Input (16 5X00622G01 (E) 3.9 W/VA Not applicable 13.3 BTU/h Not applicable
channels)
No personality
module
RTD16 Channel 5X00594G01 (E) 2.4 W/VA Not applicable 8.2 BTU/h Not applicable
Thermocouple
Input 1C31116G05 (P)
(20 mV, 50 mV,

100 mV)
16 Channel 4-20 5X00501G01 (E) 1.2 W/VA 8.16 W/VA 4.1 BTU/h 1.7 BTU/h
mA Analog Input (assumes
(2-wire only) and 5X00502G01 (P) 20mA for all
(4-wire) 1X00692H01 (P) channels)
OW360_R1005 21
VA
(TYPICAL)
Note: Aux heat dissipation includes the heat dissipated in the Ovation module and not the heat dissipated
in the external field devices.
1 Refer to the Q-Line Installation Manual for power consumption for Q-Line modules.
2 Due to power factor correction in Ovation power supplies, Power and VA are the same.
3 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.4 Digital I/O modules (main/aux power and main/aux heat dissipation) (drawn
from AC/DC Mains power)
The following table lists the power a digital input/digital output module draws from a cabinet's AC
or DC Mains power supply when the module is installed within the cabinet.
Electrical information for Ovation 1 Digital I/O modules

COMPONENT EMERSON PART MAIN +24 AUX MAIN HEAT AUX HEAT
NUMBER POWER POWER DISSIPATION DISSIPATION
(W) AND (W) AND (TYPICAL) (TYPICAL)
VA V A2
(TYPICAL) (TYPICAL)
Contact Input 1C31142G01 (E) 6.1 W/VA Not 20.8 BTU/h Not applicable
1C31110G03 (P) applicable
Contact Input 5X00605G01 (E) 7.0 W/VA Not 23.8 BTU/h Not applicable
Sequence of applicable
Events (32- 1X00884H01 (Cavity
Channel) Insert)
Compact Contact 1C31234G01 (E) 6.1 W/VA Not 20.8 BTU/h Not applicable
Input 1C31238H01 (Cavity applicable
Insert)
Digital Input 1C31107G01 (E) 1.5 W/VA 1.0 W/VA 5.1 BTU/h 3.4 BTU/h
(24V) (24V)
24 VDC/48VDC
1C31110G01, 2.0 W/VA 6.8 BTU/h
G02 (P) (48V) (48V)
22 OW360_R1005
VA V A2
(TYPICAL) (TYPICAL)
Digital Input 5X00411G01 (E) 3.5 W/VA Not 11.9 BTU/h Not applicable
(current sinking - applicable
redundant) 5X00414G01 (P)
24 V (single-
ended)
IEC 61131-2
Compliant Type 1
Digital Input 1C31107G02 (E) 1.5 W/VA Not 5.1 BTU/h 11.26 BTU/h5
125 VDC 1C31110G01, G02 applicable4
(P)
Compact Digital 1C31232G01 (E) 1.5 W/VA 0.87 W.VA 5.1 BTU/h 2.98 BTU/h
Input (24V) (24V)
24/48 VDC single- 1C31238H01 (cavity 2.33 W/VA 7.95 BTU/h
ended inputs with insert) (48V) (48V)
common return
Compact Digital 1C31232G02 (E) 1.5 W/VA 0.92 W/VA 5.1 BTU/h 3.13 BTU/h
Input (24V) (24V)
24 VDC/VAC, 1C31238H01 (cavity 2.33 W/VA 7.93 BTU/h
48 VDC isolated insert) (48V) (48V)
differential inputs
Compact Digital 1C31232G02 (E) 1.5 W/VA 0.92 W/VA 5.1 BTU/h 3.13 BTU/h
Input (24V) (24V)
24 VDC/VAC, 5X00034G01 (P) 2.33 W/VA 7.93 BTU/h
48 VDC (48V) (48V)
individually fused
inputs with
common power
supply
Compact Digital 1C31232G02 (E) 1.5 W/VA 0.92 W/VA 5.1 BTU/h 3.13 BTU/h11
Input
5X00765G01 (P)
24VDC
individually current
limited with
common power
supply
Compact Digital 1C31232G03 (E) 1.5 W/VA Not 5.1 BTU/h 17.4 BTU/h5
Input Applicable4
125 VAC/VDC 1C31238H01 (cavity
isolated differential insert)
inputs
OW360_R1005 23
VA V A2
(TYPICAL) (TYPICAL)
Compact Digital 1C31232G03 (E) 1.5 W/VA Not 5.1 BTU/h 17.4 BTU/h5
Input applicable4
125 VAC/VDC 5X00034G01 (P)
individually fused
inputs with
common power
supply
Digital Input 5X00499G01 (E) 1.5 W/VA 2.9 W/VA 5.1 BTU/h 9.8 BTU/h
24 VDC (32 1X00690H01 (P)
Channel)
Digital Output 1C31122G01 (E) 3.0 W/VA 25.6 W/VA 3 10.3 BTU/h 22.4 BTU/h3
(no relay panel) or (24V Aux)
(24V Aux)
1C31122G02 (E) 51.2 W/VA3
44.6 BTU/h3
(48V Aux)
1C31125G01 (P)
(48V Aux)
Digital Output 5X00500G01 (E) 2.4 W/VA 50 W/VA 8.0 BTU/h 1.2 BTU/h
(32 Channel 24 1X00691H01 (P) (assumes 2A
VDC High-Side, for all 32
Single-Ended) channels)
Digital Output plus 1C31122G01 (E) 3.0 W/VA 7.9 W/VA 10.3 BTU/h 26.8 BTU/h8
(16 outputs
Solid State Relay or on) (24V Aux)
Panel (16 relays)
1C31122G02 (E)
6.9 BTU/h9
1C31125G02 (P)
(24V Aux)
5A22410G01 (R) AC
contacts
or
5A22410G02 (R) DC
contacts
Digital Output plus 1C31122G01 (E) 3.0 W/VA Not 10.3 BTU/h 20.3 BTU/h8
applicable
Solid State Relay or (16 outputs (24V Aux)
Panel (16 relays) on)
1C31122G02 (E)
0.2 BTU/h9
1C31125G03 (P)
(24V Aux)
5A22410G01 (R) AC
contacts
or
5A22410G02 (R) DC
contacts
24 OW360_R1005
VA V A2
(TYPICAL) (TYPICAL)
(16 outputs
G2R Style Panel or on) (24V Aux)
(16 relays)
1C31122G02 (E)
12.8 BTU/h9
1C31125G02 (P)
(24V Aux)
5A22411G01 (R)
Digital Output plus 1C31122G01 (E) 3.0 W/VA 21.2 W/VA 10.2 BTU/h 72 BTU/h8
(8 outputs
KUEP Style Panel or on) (24V Aux)
(8 Form C relays)
1C31122G02 (E)
18.5 BTU/h9
1C31125G02 (P)
(24V Aux)
5A22412G01 (R)
two (16 outputs
or on) (24V Aux)
KUEP Style
1C31122G02 (E)
Panels (2 x 8 37.2 BTU/h9
Form C relays) 1C31125G02 (P)
(24V Aux)
5A22412G01 (R)
two applicable
or (16 outputs (24V Aux)
KUEP Style on)
1C31122G02 (E)
Form C relays) 1C31125G03 (P)
(24V Aux)
5A22412G01 (R)
(8 outputs
KUEP Style Panel or on) (24V Aux)
(8 Form X relays)
1C31122G02 (E)
13.2 BTU/h9
1C31125G02 (P)
(24V Aux)
5A22412G02 (R)
applicable (8
KUEP Style Panel or outputs on) (24V Aux)
(8 Form X relays)
1C31122G02 (E)
0.4 BTU/h9
1C31125G03 (P)
(24V Aux)
5A22412G02 (R)
OW360_R1005 25
VA V A2
(TYPICAL) (TYPICAL)
two (16 outputs
or on) (24V Aux)
KUEP Style
1C31122G02 (E)
Form X relays) 1C31125G02 (P)
(24V Aux)
5A22412G02 (R)
two applicable
or (16 outputs (24V Aux)
KUEP Style on)
1C31122G02 (E)
Form X relays) 1C31125G03 (P)
(24V Aux)
5A22412G02 (R)
5X00270G01 (E) 2.9 W/VA 64 W/VA 7 9.9 BTU/h 13.7 BTU/h7
High Side Digital 5X00273G01 (P)
Output 6
1C31219G01 (E) 2.6 W/VA (E) 0.39 W/VA 8.7 BTU/h 1.33 BTU/h
(E) (E)
Relay Output OR Base not
module (E) plus applicable + 12.3 W/VA + 42 BTU/h
base with 1C31219G02 (E)
(base + 16 (base + 16
16 G2R relays 1C31223G01 (Base) relays) relays)
---------------- ----------------
= 12.7 W/VA = 43.4 W/VA
Relay Output 32 5X00583G01 (E) 2.7 W/VA (E) 1.3 W/VA (E) 9.2 BTU/h 4.43 BTU/h
channel plus base (E)
with 32 Form C 5X00584G01(Base) Base not + 15 W/VA
Relays applicable (base) + 51.2 BTU/h
OR (base)
-----------------
5X00623G01 (Base) - -------------------
= 16.3 W/VA = 55.6 BTU/h
Relay Output 1C31219G01 (E) 2.6 W/VA (E) 0.39 W/VA 8.7 BTU/h 1.33 BTU/h
module (E) plus (E) (E)
base with 12 OR Base not
KUEP Form C applicable + 31.66 + 108 BTU/h
Relays added 1C31219G02 (E) W/VA
(base + 12
1C31222G01 (Base) (base + 12 relays)
relays)
----------------
----------------
= 109.4 W/VA
= 32.1 W/VA
26 OW360_R1005
VA V A2
(TYPICAL) (TYPICAL)
Relay Output 1C31219G01 (E) 2.6 W/VA (E) 0.4 W/VA (E) 8.7 BTU/h 1.4 BTU/h (E)
module (E) plus
base with 12 OR Base not + 21.5 W/VA + 73.3 BTU/h
KUEP Form X applicable
1C31219G02 (E) (base + 12 (base + 12
Relays added relays) relays)
1C31222G01 (Base)
---------------- ----------------
= 21.9 W/VA = 74.6 W/VA
Relay Output with 1C31219G01 (E) 2.6 W/VA (E) 0.4 W/VA (E) 8.7 BTU/h 1.4 BTU/h (E)
Contact Monitoring
OR Base not + 14.3 W/VA + 48.8 BTU/h
applicable
1C31219G02 (E) (base + 8 (base + 8
relays) relays) + 61.1
5X00564G01, G02
(Base) ---------------- BTU/h 10
= 14.69 ----------------
W/VA = 111.2 W/VA
Sequence of 1C31157G01 (E) 2.0 W/VA 1.5 W/VA (E) 6.8 BTU/h 5.1 BTU/h
Events
(24V) (24V)
24 VDC/48VDC 1C31110G01, G02
(P) 3.0 W/VA 10.2 BTU/h
Digital Input
(48V) (48V)
Sequence of 1C31157G02 (E) 2.0 W/VA Not 6.8 BTU/h 11.35 BTU/h
Events
1C31110G01, G02 Applicable4
125 VDC Digital (P)
Input
Sequence of 1C31157G03 (E) 6.1 W/VA Not 20.8 BTU/h Not
Events 1C31110G03 (P) Applicable Applicable
48V Contact Input
On-card
Compact Seq. of 1C31233G01 (E) 2.0 W/VA 0.9 W/VA 6.8 BTU/h 3.0 BTU/h
Events (24V) (24V)
24/48 VDC single- 1C31238H01 (cavity 2.3 W/VA 7.8 BTU/h
ended digital insert) (48V) (48V)
inputs with
common return
Events (24V) (24V)
1C31238H01 (cavity
24/48 VDC insert) 2.3 W/VA 7.8 BTU/h
isolated differential (48V) (48V)
digital inputs
OW360_R1005 27
VA V A2
(TYPICAL) (TYPICAL)
Events (24V) (24V)
5X00034G01 (P)
24/48 VDC 2.3 W/VA 7.8 BTU/h
individually fused (48V) (48V)
digital inputs with
common power
supply
Compact Seq. of 1C31233g02 (E) 2.0 W/VA 0.9 W/VA 6.8 BTU/h 3.0 BTU/h11
Events (24V) (24V)
5X00765G01 (P)
24VDC individually
current limited with
common power
supply
Compact Seq. of 1C31233G03 (E) 2.0 W/VA Not 6.8 BTU/h 14.5 BTU/h5
Events
1C31238H01 (cavity applicable4
125 VDC isolated insert)
differential digital
inputs
Compact Seq. of 1C31233G03 (E) 2.0 W/VA Not 6.8 BTU/h 14.5 BTU/h5
Events
5X00034G01 (P) applicable4
125 VDC
individually fused
digital inputs with
common power
supply
Compact Seq. of 1C31233G04 (E) 6.1 W/VA Not 20.8 BTU/h Not applicable
Events applicable
1C31238H01 (cavity
Contact Input insert)
Enhanced 5X00357G01 (E) 2.5 W/VA 1.0 W/VA 8.5 BTU/h 3.8 BTU/h
Compact Seq. of (24V) (24V)
Events 1C31238H01 (cavity
insert) 1.9 W/VA 6.4 BTU/h
24/48 VDC single- (48V) (48V)
ended digital
inputs with
common return
insert) 1.8 W/VA 5.9 BTU/h
24/48 VDC (48V) (48V)
isolated differential
digital inputs
28 OW360_R1005
VA V A2
(TYPICAL) (TYPICAL)
Events 5X00034G01 (P)
1.8 W/VA 5.9 BTU/h
24/48 VDC single (48V) (48V)
ended individually
fused digital inputs
with common
power supply
Enhanced 1C31357G02 (E) 2.0 W/VA 0.9 W/VA 6.8 BTU/h 3.0 BTU/h11
24VDC
single ended
individually current
limited with
common power
supply
Enhanced 5X00357G03 (E) 2.0 W/VA Not 6.8 BTU/h 6.4 BTU/h5
Compact Seq. of
1C31238H01 (cavity applicable4
Events
insert)
125 VDC isolated
inputs
Enhanced 5X00357G03 (E) 2.0 W/VA Not 6.8 BTU/h 6.4 BTU/h5
Compact Seq. of
5X00034G01 (P) applicable4
Events
125 VDC single
ended individually
with common
power supply
Enhanced 5X00357G04 (E) 5.5 W/VA Not 18.8 BTU/h Not applicable
Compact Seq. of applicable
insert)
48 VDC contact
input
Compact Seq. of
insert)
24 VDC isolated
inputs with wire
break detection
OW360_R1005 29
VA V A2
(TYPICAL) (TYPICAL)
Compact Seq. of
24 VDC single
ended individually
with common
power supply with
wire break
detection
Enhanced 1C31357G02 (E) 2.4 W/VA 2.9 W/VA 8.2 BTU/h 9.8 BTU/h11
Compact Seq. of
24 VDC single
ended individually
current limited with
common power
supply with wire
break detection
3 Loads are located outside the cabinet. Their heat dissipation is not included. Eight outputs on @ 100 mA
per output.
4 Assumes that the 125 VAC or 125 VDC 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.
6 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 Assumes eight outputs on and eight outputs off with the on outputs supplying 250 mA each.
8 Relay panels located inside Ovation I/O cabinet.
9 Relay panel located outside Ovation I/O cabinet and its heat dissipation is not included.
10 Heat dissipation from 16 monitor circuits is supplied by an external source not by the auxiliary power
supply.
11 Only applicable for 24VDC.
30 OW360_R1005
2.3.5 Bus interface modules (main/aux power and main/aux heat dissipation)
The following table lists the power a bus module draws from a cabinet's AC or DC Mains power
supply when the module is installed within the cabinet.
Note: For detailed information about bus interface modules, refer to the Ovation Bus and
Specialty I/O Reference Manual.
Electrical Specifications for Ovation Bus Interface modules

COMPONENT EMERSON MAIN +24 AUX POWER MAIN HEAT AUX HEAT
PART POWER (W) AND VA2 DISSIPATION DISSIPATION
NUMBER (W) AND (TYPICAL) (TYPICAL) (TYPICAL)
VA
(TYPICAL)
Foundation 5X00301G01 2.4 W/VA 0.55 W/VA per 8.16 BTU/h Fieldbus heat
Fieldbus (E) channel dissipation
5X00327G01 1.88 BTU/h per
(P) channel
Foundation 1X00418H01 N/A 2.4 W/VA per N/A 8.16 BTU/h per
Fieldbus Power segment segment
Conditioner
Profibus 5X00300G01, 5.1 W/VA N/A 17.3 BTU/h N/A

G02 (E)
5X00321G01
(P)
DeviceNet 5X00376G01 3.84 W/VA 0.77 W/VA per 13.1 BTU/h 2.63 BTU/h per
(E) channel channel
5X00375G01
(P)
Ethernet Link 5X00419G01 2.2 W/VA N/A 7.51 BTU/h N/A
Controller (E)
1X00569H01
(Cavity insert)
OW360_R1005 31
2.3.6 Specialty I/O modules (main/aux power and main/aux heat dissipation)
The following table lists the power a specialty I/O module draws from a cabinet's AC or DC Mains
power supply when the module is installed within the cabinet.
Note: For detailed information about bus interface modules, refer to the Ovation Bus and
Specialty I/O Reference Manual.
Electrical Information for Ovation 1 Specialty I/O Modules

NUMBER POWER (W) (W) AND VA2 DISSIPATION DISSIPATION
AND VA (TYPICAL) (TYPICAL) (TYPICAL)
(TYPICAL)
Link Controller For RS232: 3.9 W/VA Not applicable 13.3 BTU/h Not applicable
1C31166G01 (E)
1C31169G01 (P)
For RS485/422:
1C31166G01 (E)
1C31169G02 (P)
Loop Interface 1C31174GX1, GX2 3.6 W/VA When used: 12.3 BTU/h When used:
(E)
13-bit Voltage AI
1C31177G01 (P)
(E) GX1 = 0 to Digital Inputs Digital Inputs
10V (X = 0 or 2)
0.18 W/VA (24V) 0.6 BTU/h (24V)
(E) GX2 = 0 to 5
V 0.36 W/VA (48V) 1.2 BTU/h (48V)
Digital Outputs Digital Output4
12-bit Voltage AO (100mA per (100mA per

output) output)
0 to 10V
6.4 W/VA (24V) 5.6 BTU/h (24V)
(X = 0 or 2)
12.8 BTU/h (48V) 11 BTU/h (48V)
Not applicable for Not applicable for
voltage analog voltage analog
inputs. inputs.
32 OW360_R1005
(TYPICAL)
Loop Interface 1C31174GX3, GX4 3.6 W/VA When used: 12.3 BTU/h When used:
(E)
13-bit 4-20mA
Current AI 1C31177G02, G03
Digital Inputs Digital Inputs
(P)
(P) G02 = local
power (X = 0 or 2) 0.18 W/VA (24V) 0.6 BTU/h (24V)
(P) G03 = field 0.36 W/VA (48V) 1.2 BTU/h (48V)

power Digital Outputs Digital Output4
(100mA per (100mA per
12-bit 4-20mA output) output)
Current AO 6.4 W/VA (24V) 5.6 BTU/h (24V)
(E) GX3 12.8 W/VA (48V) 11 BTU/h (48V)
No AO Local Powered Local Powered
Current Analog Current Analog
(E) GX4
Inputs Only
(X = 0 or 2) Inputs 3
(20mA per input)
(2 inputs @
1.28 W/VA (24V) 20mA per input)
1.91 BTU/h
(24V)
Field Powered
Current Analog
Inputs 7
(2 inputs @
20mA per input)
0.82 BTU/h
(24V)
Pulse 1C31147G01 (E) 2.2 W/VA When used: 7.5 BTU/h When used:
Accumulator
1C31150G01-G02 Both count inputs Both count inputs
24/48 VDC Count (P) = 50% duty cycle = 50% duty cycle
Inputs
0.23 W/VA (24V) 0.78 BTU/h (24V)
0.47 W/VA (48V) 1.6 BTU/h (48V)
Not applicable for
12V/5V count
inputs
Pulse 1C31147G01 (E) 2.2 W/VA Not applicable 7.5 BTU/h When used: Both
Accumulator count inputs =
1C31150G03 (P) 50% duty cycle
24/48 VDC Count
Inputs 0.58
BTU/h(24V)8
1.19
BTU/h(48V)8
OW360_R1005 33
(TYPICAL)
Pulse 1C31147G02 (E) 2.2 W/VA Not applicable 7.5 BTU/h 0.68 BTU/h8
Accumulator
1C31150G01-G03 Both high speed
High Speed (P) count inputs =
+5V Count Inputs 50% duty cycle
Servo Driver 1C31199G01, G04 9.0 W/VA Not applicable 30.6 BTU/h Not applicable
(E)
DC LVDT
1C31201G01 (P)
Servo Driver 1C31199G02, G03, 7.1 W/VA Not applicable 24.2 BTU/h Not applicable
G05, and G06 (E)
AC LVT
1C31201G02 (P)
Servo Driver 1C31199G06 (E) 7.1 W/VA Not applicable 24.2 BTU/h Not applicable
AC LVT 1C31201G03 (P)
(LM6000 Gas
Turbine
Application)
SLIM 5 4D33741G01-G03 4.8 W/VA Not applicable 16.4 BTU/h Not applicable
Speed Detector 1C31189G01, G03, 6.4 W/VA Not applicable 21.8 BTU/h Not applicable
G04 (E)
1C31192G01 (P)
Valve Positioner 1C31194G01-G05 6.3 W/VA Digital Input 21.4 BTU/h Digital Input
(E) (Rev.50 and
(ARM9 later) 0.12 W/VA (24 0.41 BTU/h (24V)
microprocessor) VDC)
1C31197G01-G05 0.82 BTU/h (48V)
(Second (P) 0.24 W/VA (48
generation VDC) Digital Output6
module)
Digital Output 10.9 BTU/h (24V)
(100mA load) 21.8 BTU/h (48V)
3.2 W/VA (24
VDC)
6.4 W/VA (48
VDC)
34 OW360_R1005
(TYPICAL)
Valve Positioner 1C31194G01-G04 9.2 W/VA9 Digital Input 31.3 BTU/h Digital Input
(E) (Rev. 42
(ARM9 through Rev. 49) 0.12 W/VA (24 0.41 BTU/h (24V)
microprocessor) VDC)
1C31197G01-G05 0.82 BTU/h (48V)
(Second (P) 0.24 W/VA (48
generation VDC) Digital Output6
module)
Digital Output 10.9 BTU/h (24V)
(100mA load) 21.8 BTU/h (48V)
3.2 W/VA (24
VDC)
6.4 W/VA (48
VDC)
Valve Positioner 1C31194G01-G02 4.3 2 W Digital Input 14.6 BTU/h Digital Input
(E) Typical Typical
(86C196 0.09 W (24 VDC) 0.31 BTU/h (24V)
microprocessor) 1C31197G01-G05 6.5 W Typical 22.1 BTU/h 0.61 BTU/h (48V)
(P) Maximum Maximum
(First generation 0.18 W (48 VDC) Digital Output
module) Typical
(This module is 8.2 BTU/h (24V)
supported but is 16.3 BTU/h (48V)
Digital Output
no longer
available due to (100mA load)
parts 2.4 W (24 VDC)
obsolescence.) Typical
4.8 W (48 VDC)

Typical
Numalogic Fast 5X00467 4.3 W/VA Not available 14.7 BTU/h Not available
Ethernet Remote (E)
I/O (part of kit
5X00512)
Machinery Health 5X00717G01 (E) 8.3 W/VA 11.06 W/VA (8 - 28.3 BTU/h 6.8 BTU/hr
Monitor 35 mA loads)
(1 logic card and 2 +
field cards) 9.6 W/VA (8 - 30  4.2 BTU/hr (8 -
mA loads)
35 mA loads)6
7.3 W/VA (8 - 20  3.5 BTU/hr (8 -
mA loads)
30 mA loads)6
 2.5 BTU/hr (8 -
20 mA loads)6
Digital Excitation 5X00658G01 (E) 8 W/VA 2.6 W/VA 27.3 BTU/h 8.87 BTU/h
Controller (+/-
10V analog (1 logic card and 2
output) field cards)
OW360_R1005 35
(TYPICAL)
Digital Excitation 5X00658G02 (E) 8 W/VA 2.6 W/VA 27.3 BTU/h 8.87 BTU/h
Controller (4-
20mA analog
output) (1 logic card and 2
field cards)
Note: Aux heat dissipation includes the heat dissipated in the Ovation module and not the heat dissipated in the
external field devices.
3 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. Total servo valve coil current = 100 mA
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.
7 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.
8 Heat dissipation is due solely to the I/O module front-end circuit external power consumption.
9 Based on an LVDT installed with 100 mA coil load. (Total servo valve coil current = 100 mA)
36 OW360_R1005
2.3.7 Remote function modules (main/aux power and main/aux heat dissipation)
The following table lists the power a remote function module draws from a cabinet's AC or DC
Mains power supply when the module is installed within the cabinet.
Electrical Specifications for Ovation 1 Remote Function Modules

(TYPICAL)
Redundant 1C31203 (E) 16 W/VA Not applicable 54.6 BTU/h Not applicable
Remote Node
Controller module 1C31204G01,
(in Remote Node G03 (P)
Cabinet)
Redundant MAU 1C31179 (E) 17.6 W/VA Not applicable 60 BTU/h Not applicable
module
(in Controller 1C31181G01-
cabinet) G04 (P)
2.3.8 Calculating main power requirements
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 16) and modules),
plus the Power (VA) values for the Auxiliary (AUX) supplies.
For example, assume your Ovation I/O cabinet configuration consists of the following
components:
 A 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 values 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 (622 BTU/h) and AUX (282.9 BTU/h) Heat Dissipation = 904.9 BTU/h heat
dissipation inside the cabinet.
OW360_R1005 37
Power calculation example 1
I/OCABINET MAIN AUX POWER MAIN HEAT AUX HEAT COLD START
COMPONENT POWER
2 DISSIPATION DISSIPATION INRUSH CURRENT
3
Cabinet 24 W/VA N/A 82 BTU/h N/A N/A
Dual Controller 50 W/VA N/A 170 BTU/h N/A 65 A (230 VAC)

33 A (115 VAC)
25 A (125 VDC)
16 AI modules 54.4 W/VA N/A 185 BTU/h N/A N/A
- T/C
16 AI modules 54.4 W/VA 83.2 W/VA 185 BTU/h 282.9 BTU/h N/A
- 4-20 mA
Total 182.8 W/VA 83.2 W/VA 622 BTU/h 282.9 BTU/h N/A
1 The values used in this table are taken from Electrical Information for Ovation Equipment (see page 15)
(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.
3 These values assume a 60 second minimum delay after powering down the Controller before power-up.
38 OW360_R1005
S E C T I O N 3
3 Planning your Ovation network
IN THIS SECTION
Understanding Ovation networks ...................................................................................... 39

Fast Ethernet network configurations................................................................................ 42
Gigabit Ethernet network configurations ........................................................................... 43
Ovation network generations ............................................................................................ 43
Hardware used in Ovation networks ................................................................................. 46
Network topology............................................................................................................... 53
Network planning guidelines for Ovation systems ............................................................ 56
Connecting equipment to your network............................................................................. 57
3.1 Understanding Ovation netw orks
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 standard
Ethernet protocols and implemented in a robust, fault tolerant, open design.
Ovation’s design integrates standard, non-proprietary hardware and works within the applicable
IEEE 802.x standards. This design provides for easy connection of workstations (drops), third-
party devices, and other equipment to the Ethernet network. It is also completely fault tolerant for
any single point of failure.
The Ovation network is media independent, allowing both fiber-optic and/or copper (UTP)
implementation. Media converters convert data transmissions between copper cable and fiber-
optic cable so that data can flow seamlessly over the network.
Currently, Emerson offers a second and third generation Ovation network based on standard,
unaltered Fast Ethernet and Gigabit Ethernet, implemented in a robust and fail-safe scheme.
Ovation dedicates one switch port per end station and configures the link to be full duplex to
eliminate the possibility of collisions (see page 40). Maximum built-in redundancy is achieved
through dual Ethernet switches and either a dual-ported Ethernet NIC card or two individual cards
for each node attached to the network.
For designs with geographically dispersed control areas, islands of switch pairs are connected
together with additional pairs of switches (fan-out switches) to create an up-link hierarchical tree.
The up-link interconnection provides total redundancy originating at each station that extends
throughout the entire Ovation network. Fiber-optic media may also be used to extend a network
run length beyond 100 meters or to enhance EMI/RFI noise immunity.
OW360_R1005 39
3.1 Understanding Ovation networks
3.1.1 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.1.2 Network terminology
The following table lists terms that are common to networking.
Commonly used terms used in network technology
TERM DESCRIPTION
Access port Port on a switch that is typically used to connect to non-network equipment such as an
Ovation drop, router, or IP-only device. Also called a Downlink port.
Backup Root Switch Takes over the 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 47) 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 47) 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 Can only be used to monitor traffic transmitted and received on the source monitor
Port 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.
Downlink port Port on a switch that is typically used to connect to non-network equipment such as an
Ovation drop, router, or IP-only device. Also called an Access port.
Fan out Area Switch at the edge of the network. Deployed in a pair called Primary-Partner, the fan out
Switches area switches provide connectivity to drops in areas distant from the root. Groups 4 and
5 in the switch configuration file example (see page 47) are examples of primary and
partner fan out area switches, respectively. Fan out area switches can accept drop
connections and a connection from the root and backup root. Fan out area switches are
optionally connected to each other via the fan out cross-connect ports, although in
normal operation, this connection does not carry any traffic.
Fan out Cross- Port that can only be used to connect between primary and partner switches. This
Connect Port optional connection provides an alternate communications path in the event a fan out
switch pair is isolated from the root and backup root.
Fast Ethernet Local area network (LAN) transmission standard that provides a data rate of 100
megabits per second.
40 OW360_R1005
3.1 Understanding Ovation networks
TERM DESCRIPTION
Gigabit Ethernet Transmission technology based on the Ethernet frame format and protocol used in local
area networks (LANs) that provides a data rate of 1 billion bits per second (one gigabit).
Gigabit Ethernet is defined in the IEEE 802.3 standard.
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.
I/O Device Switches Switch that accepts connections from various field devices that are not connected to the
Ovation network. The I/O device switch employs a separate VLAN to isolate 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.
IP-Only Port Port on root and fan out switches that 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 fan out switch to
accept connections from ancillary devices. Group 1 in the switch configuration file
example (see page 47) is an example of an IP-only switch. The IP-traffic switch connects
redundantly to a root and backup root switch (for example; a fan out 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 47) is an example of an IP-traffic switch.
Managed Switch Switch that can be configured and monitored through standard network tools such as
snmp2ovation.
Ovation Drop Port Can only be used to connect Ovation drops. Ovation drop ports exist on most root and all
fan out switch configurations.
Ovation Management Can only be used to connect an I/O device switch to an Ovation drop port. This permits
Port 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 fan out switch. Groups
2, 6, 8, and 12 in the switch configuration file example (see page 47) are examples of
root switches. Root switches can accept switch and drop connections.
Root Switch Port Ports on a root or backup root switch that are reserved for connecting to a fan out or IP
traffic switch. Root switch ports only exist on root and backup root configurations
SFP Small Form-factor Pluggable. SFP modules plug into SFP slots. Different SFP modules
provide various types of Ethernet connections, including copper, multimode and single
mode connections.
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.
Switch Chaining Port Port that can only be used to connect one I/O device switch to another I/O device switch.
Switch Uplink Port Port on a fan out or IP-traffic switch that is used to connect to the root or backup root
switches.
Trunk Port on a switch that carries multiple virtual local area networks (VLANs).
OW360_R1005 41
3.2 Fast Ethernet network configurations
TERM DESCRIPTION
Unmanaged Switch Switch that cannot be configured or monitored. It automatically configures each port's
speed and duplex via auto-negotiation. It does not record or provide any status
information.
Uplink port Port on a switch that is used to connect to another switch.
3.2 Fast Ethernet netw ork configurations
Fast Ethernet is a local area network (LAN) transmission standard that provides a data rate of 100
megabits per second (100 Mbps). It also supports the Ovation network requirement of transmitting
200,000 points per second along with all alarm, configuration, and download traffic. Second (see
page 44) and third (see page 45) generation Ovation networks use Fast Ethernet technology.
Currently, Ovation supports a single network topology (see page 53) 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 “fan out” 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 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.
Use Emerson's guidelines (see page 56) as to the selection, configuration, and interconnection of
network equipment within the DCS LAN.
42 OW360_R1005
3.3 Gigabit Ethernet network configurations
3.3 Gigabit Ethernet netw ork configurations
Gigabit Ethernet is a version of the Ethernet technology used in local area networks (LANs) for
transmitting Ethernet frames at 1 Gbps (1,000 Mbps). Gigabit Ethernet is an extension to the
preceding 10 Mbps and 100 Mbps 802.3 Ethernet standards.
Gigabit Ethernet offers the following benefits over 100 Mbps Ethernet:
 Transmits at a rate of 10 times greater than Fast Ethernet.
 Offers full-duplex capacity that can provide virtually doubled bandwidth.
 Offers cumulative bandwidth for faster speed by employing gigabit server adapters and
switches.
 Works with existing installed Ethernet nodes.
 Transfers a large amount of data quickly.
In previous deployments of Ovation networks, the interface roles for each switch were assigned in
fixed configurations. For example, each fanout area switch had a set of drop ports, three
drop/router ports, and one IP-only port.
However, using Emerson's Gigabit Ethernet solution provides for flexible port assignments. This
translates to cost savings by reducing the amount of hardware needed in the Ovation network.
For example, since several ports on other switches can be configured to be IP-only, the need for
IP Traffic switches could be either significantly reduced or completely eliminated. In addition,
drop/router ports could be eliminated, since port roles are available to connect specifically to a
router, eliminating the constraints of the existing drop/router port configurations.
The Gigabit Ovation network also allows for the separation of the Ovation network and the
Ovation system's Management network. Each drop has two Network Interface Cards (NICs) to
connect to two different switches. With the Gigabit Ovation network, you would define a third NIC
on an existing computer in your system (Ovation drop or corporate computer) to be dedicated as
the Management port.
In order to set up a Gigabit Ethernet network, you must have devices equipped with Gigabit-
compatible network adapters connected through a Gigabit Ovation LAN switch.
Gigabit Ethernet usually employs optical fiber connections to transmit information at a very high
speed over long distances. For short distances, copper cables and twisted pair connections are
used.
3.4 Ovation netw ork generations
The Ovation network has developed through the following generations:

 First generation -- FDDI (obsolete).
 Second generation -- Fast Ethernet access ports with STP+.
 Third generation -- Fast Ethernet access ports with RSTP and Gigabit Ethernet uplinks.
 Gigabit Ethernet -- Gigabit Ethernet access ports and Gigabit Ethernet uplinks.
The active generations (second and third) share the idea of root, fanout, and IP traffic switches.
However, they differ in terms of cable cost, supported hardware, and port flexibility.
OW360_R1005 43
3.4 Ovation network generations
3.4.1 Ovation second generation network technology
For Ovation's second generation network solution, Emerson implemented Spanning Tree Protocol
(STP) with proprietary extensions. This provides a robust network technology that prevents
network loops and introduces redundancy in link connections. The second generation technology
allows for the network to be media independent, allowing both fiber optic and/or copper (UTP)
implementation. Media converters are used to bridge the communication between the copper and
fiber cables.
The following table shows the features of the second generation Ovation network.
Features of second generation Ovation network
FEATURE SECOND GENERATION
Technology Fast Ethernet

Speed 100 Mbps
Components  2960Plus family of switches
 IE2000 family of industrial switches
Topology Duel-Centered Star
 Pair of root switches with redundant cross-connect
 Pairs of fan out switches dual attached to root switches (two uplinks for each
fan out switch)
Media Copper; fiber optic supported via media converters and optional fiber optic
SFP modules in fan out switches
Notes  Root switches have copper ports for connecting to fan out switches and
drops
 Fan out switches have copper ports only for connecting to drops.
For second generation networks, each switch is connected to the root and backup root switches,
or optionally, to each other.
44 OW360_R1005
3.4 Ovation network generations
3.4.2 Ovation third generation network technology
For Ovation's third generation network solution, Emerson incorporated Rapid Spanning Tree
Protocol (RSTP), which is an advanced and improved implementation of STP.
Some of the benefits of Emerson's third generation network are:

 Eliminates the need for media converters between switches.
 Provides the capability of using only fiber optic cable from switch to switch.
 Reduces the number of connections (uplinks) from four to two between fan out areas and root
areas.
 Allows the connection between root and fan out switches to be Gigabit Ethernet (1000 Mbps).
The following table shows the features of third generation Ovation networks.
Features of third generation Ovation networks
FEATURE THIRD GENERATION (FAST GIGABIT OVATION ETHERNET

ETHERNET)
Technology Gigabit Ethernet (and Fast Ethernet) Gigabit Ethernet compatible

compatible
Speed  Switch to switch 100 or 1000Mbps  Switch to switch 1000Mbps
 Switch to end-station 100Mbps  Switch to end-station 1000 Mbps
Components Root switches: IE5000 family of industrial switches
 IE5000 family of switches. Multinetworking
Fan out switches:  Cisco WS-C3650-24TS-S
 2960Plus family of switches
 IE2000 and IE5000 family of industrial
switches
Topology Overlapping rings dual connections Overlapping rings dual connections
optional. optional.
Media Copper, single-mode / multi-mode fiber. Copper, single-mode / multi-mode fiber.
Media converters are only required at Media converters are only required at
end stations. end stations.
For third generation and Gigabit Ovation networks, each fanout switch is connected to either the
root or the backup root switch and to each other. Drops connect to both switches in an area.
OW360_R1005 45
3.5 Hardware used in Ovation networks
3.5 Hardw are used in Ovation netw orks
The following hardware components comprise an Ovation network:
Network components:
 Switches
 Routers
 Media converters
 Cables
Ovation components:
 Controllers
 Workstation drops (Operator Stations, Database Server, and so forth)
Non-Ovation components:
 Printers
 Time Servers
3.5.1 Using Ethernet switches to provide network stability
Along with avoiding data collisions, Emerson uses Ethernet switches to implement a system with
built-in fault tolerance, thereby guaranteeing system reliability and performance. A single
component failure, 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 Ethernet cards. 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 with the first pair
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 55) to ensure predictable fail-over
behavior. This interconnection scheme provides fault tolerance originating at each station and
extending throughout the entire network.
46 OW360_R1005
Example of a second generation 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 fan out switches supported.
G03 = Backup root switch, zero fan out switches supported.
G04 = Primary fan out switch.
G05 = Partner or secondary fan out switch.
G06 = Root switch, up to three pairs of fan out switches supported.
G07 = Backup switch, up to three pairs of fan out switches supported.
G08 = Root switch, up to ten pairs of fan out switches supported.
G09 = Backup switch, up to ten pairs of fan out switches supported.
G10 = Dual attached, IP traffic only switch.
G12 = Root switch, one fan out area supported.
G13 = Backup root switch, one fan out area supported.
3.5.2 Switches used in Ethernet second and third generation 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+24TC-L (second and third generation architectures)
 Intelligent Ethernet switch that supports 24 Ethernet 10/100 ports and 2 dual purpose
10/100/1000 Ethernet uplink ports (copper for fiber using SFP module).
 Used for Ovation fan out and IP traffic switches.
 Can also be used as a general purpose managed switch.
 Root of second generation.
OW360_R1005 47
 Cisco WS-C2960+48TT-L (second generation architecture only)

 Intelligent Ethernet switch that supports 48 Ethernet 10/100 ports and two fixed
10/100/1000 Ethernet uplink ports.
 Supports two GBIC module slots.
 Used for Ovation root and backup root switches to support more than 10 fan out areas.
 Cisco IE-2000-4T-G-B (second and third generation architectures)

 Intelligent industrial Ethernet switch that supports 4 10/100 ports plus 2 10/100/1000
copper uplink ports.
 DIN-rail mount.
 24VDC powered.
 Extended temperature range.
 Cisco IE-2000-4TS-G-B (second and third generation architectures)

 Intelligent industrial Ethernet switch that supports 4 10/100 ports plus 2 Gigabit SFP slots
for fiber uplinks.
 DIN-rail mount.
 24VDC powered.
 Cisco IE-2000-8TC-G-B (second and third generation architectures)

 Intelligent industrial Ethernet switch that supports 8 10/100 ports plus 2 Gigabit Combo
RJ45/SFP slots for fiber uplinks.
 DIN-rail mount.
 24VDC powered.
 Cisco IE-2000-16TC-G-E (second and third generation architectures)

 Intelligent industrial Ethernet switch that supports 16 10/100 ports plus 2 Fast Ethernet
SFP slots plus 2 Gigabit Combo RJ45/SFP slots for fiber uplinks.
 DIN-rail mount.
 24VDC powered.
48 OW360_R1005
 Cisco WS-C3750V2-24FS-S (existing third generation systems only)

 Intelligent StackWise switch optimized for Gigabit Ethernet. Provides 24SFP Fast
Ethernet slots for 100 Base FX ports plus 2 SFP Gigabit slots for fiber optic uplinks.
 Used as Ovation fan out and root switches.
 Note: This switch cannot be included in stacks on Ovation networks.
 Cisco WS-C3750X-24T-S (existing third generation systems only)

 Intelligent StackWise Plus switch optimized for Gigabit Ethernet.
 Unites multiple switches into a single logical unit.
 Individual switches can have any combination of Cisco Catalyst 3750X series switches.
 Provides 24 Gigabit 10/100/1000 Base T ports, RJ45 connectors plus a network module
slot that adds 4-SFP based gigabit uplink ports.
 Incorporates modular hot-swappable fans and power supplies.
 Can be configured with an optional redundant power supply module.
 Used as Ovation core and backup core switches.
 Cisco WS-C3750X-12S-S (existing third generation systems only)

 Intelligent StackWise Plus switch optimized for Gigabit Ethernet.
 Unites multiple switches into a single logical unit.
 Individual switches can have any combination of Cisco Catalyst 3750X series switches.
 Provides 12-SFP based Gigabit ports.
 Incorporates modular hot-swappable fans and power supplies.
 Can be configured with an optional redundant power supply module.
 Used as Ovation core and backup core switches.
 Cisco IE-5000-16S12P (third generation and Gigabit Ovation systems)

 Intelligent Ethernet switch that supports 12 10/100/1000 Ports,
 Provides four Gigabit SFP uplinks and 12 100/1000 Mbps SFP downlink ports.
 Available with single High AC/DC power supply or with single low DC power supply.
OW360_R1005 49
3.5.3 Switches used in Gigabit Ovation networks
The following Ethernet switches have been defined for use in Ovation Gigabit 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.
IE-5000, rack-mounted industrial switch

 Cisco IE-5000-16S12P
 Rack-mounted with 12 Gigabit copper access ports, 12 Gigabit SFP access slots, plus
four Gigabit SFP uplink slots.
 Ruggedized to stand up to extreme temperatures, vibrations, and shock.
 Extended temperature ratings (-40 degrees C to 74 degrees C).
 Conformal coating.
 Hardened for shot, surge, and electrical noise.
 Redundant power supplies available.
 Two power supplies option:
AC-DC: 100 - 240V AC or 100 - 250V DC
Low DC: 24 - 60V DC
 No moving parts (no fan).
 Support for PTP
 Support for segments and rings (REP)
 Alarm I/O: four contact inputs, one relay output
Note: Because of the mix of copper ports and SFP slots, systems using the IE-500 switch
should not need media converters for switch-to-switch connections and can minimize the use of
media converters for drop-to-switch connections.
Cisco 3650 - Multinetworking

 Cisco WS-C3650-24TS-S
 Currently used as the multinetworking switch for Ovation.
 Access ports on the switch are both 100 Mbps and Gigabit capable.
 Not ruggedized
 AC-powered and has an internal fan.
50 OW360_R1005
3.5.4 Media converters used in Ovation networks
Depending on your network configuration, you may use media converters in your Ovation
network. Two styles of Etherwan media converters are used to convert copper signals to fiber
signaling. The following styles of media converters are used on the Ovation network:
 1X00484 - 24VDC (DIN Rail mounted)
 1X00529 - EL100 Series
Multimode media converter versions with ST or SC ports can interface 50 micron or 62.5 micron
fiber.
Note: All media converters are subject to change as new technology is constantly improving
and evolving.
Media converters
MEDIA CONVERTER EMERSON PART FEATURES

NUMBER
EtherWAN EL900 series 10/100 1X00484  Link-fault-pass-through.

Base-TX to 100 Base-FX hardened  DIN rail mounting.
media converter UTP to multi-mode  -34°C to 74°C (-29°F to 165°F)
or single-mode fiber extended operating temperature range.
 Redundant 10 to 48 VDC power inputs.
 Provides a status relay contact output.
EtherWAN EL100 series 10/100Base- 1X00529  Link-fault-pass-through.
TX to 100Base-FX media converter  0°C to 45°C (32°F to 113°F) operating
UTP to multi-mode or single-mode temperature range.
fiber  Rack mountable.
In addition, Emerson provides the EtherWAN EMC1600 Chassis System 19 chassis system that
provides 16-bays for EL100 media converters (1X00530).
OW360_R1005 51
3.5.5 Cable connection types for your network
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 (for second generation
networks) or an all fiber optic implementation for third generation networks.
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 2 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 option 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.
Second generation networks use 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 fan out-to-root switch
connections, the media converter at the fan out switch location is eliminated by selecting one of
the switches with fiber optic uplinks.
Figure 1: Fiber optic media options
52 OW360_R1005
3.6 Network topology
The media converters are for multi-mode 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 hot-
swapped. 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.
If you have an existing fiber optic cable installed, it may be reused by applying retermination, new
patch cables, or adapter cables as necessary. Higher grade cable should be used with new
installations.
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.
3.6 Netw ork topology
An Ovation network at its basic form is a root switch and a backup root switch. A root and backup
root switch add redundancy to the network because drops connect to both switches. Alternatively,
primary Controllers can connect to one switch and the backup Controller connects to the other
switch.
A basic Ovation network is suitable for systems that have a small number of drops that are
physically near each other. However, this type of network is limited in its number of ports and
geographic scope.
An Ovation network at its maximum form is a root area (root and backup root switches) along with
fanout areas. Each fanout area is two switches.
For second generation networks (see page 44), each switch is connected to the root and backup
root switches, and optionally, to each other. Drops connect to both switches in an area.
For third generation networks (see page 45), each switch is connected to either the root or the
backup root switch and to each other. Drops connect to both switches in an area.
OW360_R1005 53
3.6.1 Single-tier network 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 fan out the tree. The maximum number of fan
out areas supported is governed by the root switch configuration used.
Figure 2: Single-tier Ovation network
54 OW360_R1005
3.6.2 Two-tier network 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. Similar to
root switches, fan out switches are deployed in pairs for redundancy. In this case, the switches
are named Primary and Partner.
The following figure illustrates a two-tier, third generation network with three fan out areas. A third
generation system comes with cross cables that interconnect the primary and partner switches.
This arrangement allows a cluster of Ovation drops to be isolated for maintenance or to be
operated locally despite multiple failures. For second generation networks, the cross cable is an
optional feature. Typically, the cluster of drops in the fan out switch area is wired with a UTP
cable, and a fiber optic cable may be used to connect these switches to the root switches.
Figure 3: Two-tier Ovation network, third generation
OW360_R1005 55
The proper configuration of the switches is critical to correct and reliable system operation.
Emerson provides switch configuration files (see page 47) for every Ovation system.
The following figure shows a closeup of a fan out area.
Figure 4: Closeup of Fan-Out area, second generation
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 non-Ovation Ethernet devices.
56 OW360_R1005
3.7 Network planning guidelines for Ovation systems
3.7 Netw ork planning guidelines for Ovation s ystems
As you plan and design your Ovation network, observe the following guidelines for your proposed
network:
3. Know the number of drops you plan to connect to your Ovation network. You can connect up
to 254 drops.
4. Know the types of drops your Ovation system needs.
5. Know how you will distribute and connect the Ovation drops to your network.
6. Ensure you can access a site plan that describes the relative locations (horizontally and
vertically) of all equipment rooms containing Ovation drops.
7. Know what Electro-Magnetic Interference (EMI) and Radio Frequency Interference (RFI)
environment the network cable will run through.
8. Know what types of network switches you will use. Use only switches (see page 47) that are
supplied by Emerson.
9. Know the types of network configurations you will use. Use only configurations that are
defined by Emerson.
10. Ensure you use switch connections that are valid for your Ovation network schema.
 Connect only the following equipment to the DCS network switches (except the IP traffic-
only port - typically Port 1):
 Ovation Controllers.
 Ovation Windows-based workstations.
 Approved network switches and routers.
Note: All devices are subject to change as technology improves and evolves.
3.8 Connecting e quipment to your network
The following sections discuss connecting drops and devices to the Ovation network:
 Controllers (see page 58).
 Workstations (see page 60).
 Ovation devices (see page 61).
 Non-Ovation devices (see page 61).
OW360_R1005 57
3.8 Connecting equipment to your network
3.8.1 Connecting OCR400 or OCR1100 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 Processor (CPU) module in the OCR1100 G01 Controller also contains four RJ-45
ports at the top of the module. However, the Processor (CPU) module in the OCR1100 G02
Controller contains one RJ-45 port and three SFP transceiver ports (N1 - N3) 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 or Ethernet I/O network).
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 single-attached network connection approach.
The following figures illustrate typical network connections for an OCR400 or 1100 Controller.
58 OW360_R1005
Figure 5: Network Connections to an OCR400 or OCR1100 Controller — Redundant, Single

Attached
OW360_R1005 59
Figure 6: Network Connections to an OCR400 or OCR1100 Controller - Redundant, Dual

Attached
3.8.2 Connecting workstations to your Ovation network
Ovation workstation nodes 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.
60 OW360_R1005
3.8.3 Connecting Ovation devices to your Ovation network
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.
3.8.4 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 duplexity,
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:
 Use an IP traffic 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. An IP traffic switch is configured to
support the generic IP traffic required by non-Ovation devices. The uplink 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 duplexity.
OW360_R1005 61
S E C T I O N 4
4 Planning your Ovation multiple networks
IN THIS SECTION
What is an Ovation multiple network? ............................................................................... 63

What are the basics of multi-networking? ......................................................................... 64
Multiple network planning guidelines for Ovation systems ............................................... 74
What do you need to plan before connecting multiple networks? .................................... 76
What is the connection plan for multiple networks? .......................................................... 80
What is backbone connectivity for multiple networks?...................................................... 81
What is collapsed backbone connectivity for multiple networks? ..................................... 83
Licensing in Multiple Networks .......................................................................................... 84
What security is needed for multiple networks? ................................................................ 84
Hardware information for Ovation multiple networks ........................................................ 85
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).
OW360_R1005 63
4.2 What are the basics of multi-networking?
4.2 What are the basics of multi -netw orking?
To help explain multiple networks, consider a two-network scenario with bi-directional

communication and one-way control. In the following example, bi-directional communication
indicates that data flows both ways, but only one network, Unit 2, is able to monitor, control and
engineer the other network, Unit 1. Unit 1 is not able to monitor, control or engineer Unit 2, but
data can be transmitted from Unit 1 to Unit 2.
Figure 7: Bi-directional Communication with One-way Control
To begin, it is important for you to understand a basic concept of multi-networking — local and
remote networks.
64 OW360_R1005
4.2.1 Local and Remote Network Concepts
Local and remote refer to networks in a multiple network configuration. The terms local and
remote are completely relative to your position. If you are a plant technician working on Unit 2,
Unit 2 is your local network. However, for the operator who is monitoring control in Unit 1’s control
room, Unit 1 is his local network.
Figure 8: Local and Remote Networks
If, as the local technician on Unit 2, you initiate a control change on Unit 1, you are working on a
remote network. Conversely, the operator on Unit 1 sees the control change on his local network.
For the sake of our discussion about multi-networking, think of the local network as a client,
sending requests and receiving information, and think of the remote network as a server,
responding to requests and sending information back to the client.
OW360_R1005 65
4.2.2 What is the network name alias concept?
The network name alias is a basic concept associated with multi-network functionality. An alias is
a second name assigned to a network. Because networks in a plant could have the same primary
name, a local network looks for a remote network’s alias, not its primary name.
Network aliases are helpful for people to quickly differentiate between different locations, but the
Ovation system depends on IP addresses to route traffic correctly. This is the same addressing
scheme used on the Internet. IP stands for "Internet Protocol." Think of the relationship between
aliases and IP addresses as similar to the relationship between domain names and IP addresses
on the Internet. Ovation networks work in a similar way except that you need to assign the IP
addresses.
Figure 9: Network Alias and Remote Network Alias
In this example, Unit 1 has configured its network alias to be Durham. The alias Durham makes
Unit 1 available to other networks by that name.
To retrieve information from Unit 1, Unit 2 must define a remote network using the Durham alias.
The technician working on Unit 2 now has the ability to view all information about remote network
Durham. All dialog boxes and information refer to the remote network by its alias, not its network
name. In other words, any reference to Durham actually refers to Unit 1.
66 OW360_R1005
Before assigning a network alias, you should establish or consult your plant’s naming policy for
multiple networks. The alias is how engineers, technicians and operators will recognize your
network in a remote connection. In this example and those that follow, the plant chose to assign
aliases based on North Carolina towns and cities. A consistent naming policy should make it
easier to recognize logical relationships between your multiple networks.
Now that you have established a local network that recognizes a remote network using its alias,
look at how communication works. The local network, Unit 2, sends a request for data to Durham.
Durham receives the request and sends information back to Unit 2 using its data servers.
A Data Server is a drop on a network that services another network’s request for data. A Data
Server is not the Ovation database, but a drop specifically configured to respond to remote
requests. Because the Ovation database server only supports a single network, each network
must have its own Data Server. The previous figure shows Durham as having two data servers,
but only one is required to service remote requests and is referred to as the primary. Additional
data servers, as in this example, can be defined as secondary to provide redundancy.
Notice the alarm collectors on Unit 2. These two alarm collectors retrieve all alarm information
from Durham’s data servers and enable each MMI on Unit 2 to see those alarms on Durham.
Alarm collectors are drops configured on a local network to connect to a remote data server. The
alarm collector receives the remote network’s alarms and distributes the remote alarm data to the
local MMIs. Alarm collectors only enable alarm data communication, not control or engineering
functions. Only one alarm collector is required to provide multi-network communication; the
second provides redundancy. Since Unit 2’s alarm collectors are configured to communicate with
Durham’s data servers, an operator working locally on Unit 2 can view the alarms from both Unit 2
and Durham. An alarm collector is not required if you do not want to see remote alarms in your
multi-networking scheme.
4.2.3 What is IP addressing?
Network aliases are helpful for people to quickly differentiate between different locations, but the
Ovation system depends on IP addresses to route traffic correctly. This is the same addressing
scheme used on the Internet. IP stands for "Internet Protocol." Think of the relationship between
aliases and IP addresses as similar to the relationship between domain names and IP addresses
on the Internet. Ovation networks work in a similar way except that you need to assign the IP
addresses.
OW360_R1005 67
4.2.4 What are other possible multi-network configurations?
The following figure shows two networks configured for multi-network functionality with two-way
communication, meaning that each network can monitor, control and engineer the other network.
Each network has defined both a network alias and a remote network alias.
Figure 10: Two-way Network Communication
In this scenario, Unit 2 became available remotely by configuring its alias and data servers. Unit 1
added alarm collectors, defined a remote network to communicate with Raleigh, and defined
remote data servers from Raleigh. By doing this, Unit 1 establishes the ability to send requests
and receive data from Raleigh.
Since both Unit 1 and Unit 2 now have data servers and alarm collectors, both networks can be
configured to monitor, control, and engineer the other network as long as proper security has
been defined.
68 OW360_R1005
The following figure shows several networks communicating in a complex, expanded multi-
network configuration.
Figure 11: Complex Multi-Network Configuration
Look at the two networks at the bottom of the previous figure. Notice that they have the same
network name, Unit 3. In this configuration, it is imperative for each network to define a unique
alias so that when you are using the multi-networking you can identify which remote network you
are accessing.
Each local network has defined three remote networks so that you can be able to work on any
local network across all networks, as long as the security and proper drop configuration have
been established.
Ovation multi-networking is flexible. Therefore, there are many different configuration scenarios
available for defining Ovation multiple networks. The following sections describe how to use the
tools to configure multiple network functionality and to map out the features that make this
functionality so flexible.
OW360_R1005 69
4.2.5 What is needed to make multi-networks work?
To make a network available for multi-network functionality, you must configure certain items
locally. In the context of multiple networks, configuring refers to setting up a local network so that
it can be accessed remotely. Remember that local and remote are perspective based — where
you are is the local network.
To illustrate this concept, consider a scenario where you have two networks that you want to
connect for multi-network functionality. In the following figure, you are configuring Unit 1 so that it
can be accessed by other networks. Local configurations that need to be made include the
network alias, data servers, and security policies for authorized users. Refer to Managing Ovation
Security for a better understanding of security policies and the concept of role assignment, as well
as examples of how you can implement security and roles for your site's specific situation.
Figure 12: Configure Locally
Unit 1 configured its network alias, Durham, so that a remote network can identify it and establish
communication. In configuring the data servers, Unit 1 establishes names and IP addresses so
that a remote network can find it and establish communication. These configurations allow remote
users to communicate across networks, and the only thing that limits what a remote user can do
is the security that Unit 1 configures.
70 OW360_R1005
Because remote users have access to your local network, security is very important in multi-
networking. Special emphasis should be placed on the creation of your security policies. Refer to
Managing Ovation Security for a more in-depth discussion.
Typically, in a multi-network environment, you have a security administrator who is responsible for
implementing security policies and roles for authorized users. The Security Manager is the tool
that performs these tasks. Refer to Managing Ovation Security.
At this point, Unit 1 has been configured for multi-network capability. For Unit 2 to access Unit 1,
you must move to Unit 2 and locally define Unit 1 as the remote network that you want to
communicate with. To define a remote network means that you locally identify the remote
network and its data servers to which the local network connects.
To continue with the example, you are now working locally on Unit 2 and defining it so that you
can access Unit 1 remotely. Required definitions include: the remote network alias, the remote
database servers, the alarm collectors, and specific drops that connect remotely.
Figure 13: Define the Remote Network
The first step is to define a remote network as Durham. Next, identify and define the remote data
servers' IP addresses and optionally whether they should serve as primary or secondary. You
must also define the remote Ovation Database.
OW360_R1005 71
You must define specific remote data servers for each local alarm collector, and because there is
more than one remote data server, a primary and a secondary data server (optional) should be
established for each alarm collector.
The final step in establishing multi-network functionality is defining which alarm collectors and
data servers that specific drops on a local network use to perform remote functions. Each local
drop can be configured to communicate with a specific remote primary and secondary (optional)
data server, as well as a local primary and secondary (optional) alarm collector. You can tell each
local drop which data server and alarm collector it can communicate with.
Like all configuration set in the Developer Studio, you can make multi-network settings at the
Network, Unit, and Drop levels. After all the configuring and defining is complete, when you are on
Unit 2 you can remotely do anything on Durham that you can on Unit 2, unless Unit 1’s security
denies you the access.
Note: Settings at the lowest defined level in the hierarchy take precedence over the other
defined levels. For example, settings at the Drop level take precedence over settings at the Unit
level.
4.2.6 Multiple network terminology
The following table describes the common terms used in this user manual.
Multiple network terms
TERM DESCRIPTION
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
Alarm Collector
Collector, the remote network(s) it connects to must be defined. You can define a
Primary and a Secondary Alarm Collector for redundancy.
Drop on remote network where alarms are collected and sent to the Alarm Collector on
Alarm-Data the local network. This drop can also serve as the remote data server. You can define a
Server Primary and a Secondary Alarm-Data Server for redundancy.
This information displays on the Base Alarm window on the Operator Station.
Backbone Top layer of network configuration. Provides IP connectivity between units.
Core switch is the primary router that handles communication between multiple
Core
networks. Backup core provides redundancy if the core fails.
DCS Distributed Control System (such as an Ovation Control System).
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 In addition to the above parameters, the “.” and “@” are required and are reserved
point name 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).
72 OW360_R1005
TERM DESCRIPTION
Alarm Collector
Internet Protocol (IP) address uniquely identifies a computer so that data can be
IP Address transferred between computers and networks. This is used to establish the IP
connectivity that is necessary for sharing data between networks.
Local Area Network. Network that typically contains units that are located in the same
LAN
geographical location.
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.
Local data server
Note: It is recommended that the Ovation Database Server not be configured as a
local data server due to processing performance issues.
Network on the local system. This is the Ovation network that is connected directly to
Local network
the Ovation drops in the local system.
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
Machine Alias
data server. This name must be unique within the local system’s Ovation database and
cannot conflict with any local drop names.
Machine Name Drop number (for example, drop200).
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 when the system was first configured.
Network Name
An alias cannot have more than eight characters and cannot contain any spaces,
Alias
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).
Note: The local network is always network number zero (0).
Network Number If a remote network is removed through the system configuration tool, you can reassign
Alias 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.
Drop in a remote network that contains special software that allows it to send Ovation
Remote Data
point data from the remote network when requested. This is defined from the local
Server
network.
OW360_R1005 73
4.3 Multiple network planning guidelines for Ovation systems
TERM DESCRIPTION
Alarm Collector
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
Remote Network defined in the Developer Studio when the system was first configured.
Alias
Emerson recommends 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).
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 300 multiple networks (299 remote networks and one
local), but the actual number of networks that are interfaced depends on the hardware
Remote Network
used and the system requirements. However, at any one time in the Ovation Developer
Studio, there can only be a maximum of 31 concurrent actively mapped remote
networks.
The controller also can only access a maximum number of 32 (31 remote and one local)
networks.
The Ovation Studio has been updated to better categorize or group remote networks
Remote Node under a Remote Node. Remote node is only container to group the remote networks in
a hierarchical structure.
Hardware that isolates a network but provides selective connectivity between IP
Router addresses on local and remote networks. The router is used to determine what data can
be shared between networks.
Hardware that selects the path for sending data to networks. Typically, a switch
Switch
provides the connections between the router and the system drops.
Wide Area Network. Network that typically contains units that are NOT located in the
WAN
same geographical location.
4.3 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 regarding Ovation users and roles.
 Type of security required between Ovation and the infrastructure used to connect the
systems together
74 OW360_R1005
4.3 Multiple network planning guidelines for Ovation systems
 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 76) 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:
 Routers.
 Switches.
 Cables.
Currently, Emerson recommends using a multi-network core router/switch (see page 47) that
combines switching and routing capabilities. You can use this core router/switch to connect
up to 16 networks in the same facility.
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 could 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. 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.
OW360_R1005 75
4.4 What do you need to plan before connecting multiple networks?
4.4 What do you need to plan before connect ing 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 77) – 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 78) – you already have two or
more Ovation control systems and you want to use them in a multi-network environment.
 Hybrid (see page 79) – 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.
Notes:
 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.
76 OW360_R1005
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 multi-
networking and security. When using the Security Manager (refer to 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.
OW360_R1005 77
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 79).
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 (refer to 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).
78 OW360_R1005
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 multi-
network environment. This scenario borrows its approach from both the existing Ovation systems
(see page 78) and the new system installation (see page 77) 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. See new system installation (see page 77)
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 (refer to Managing Ovation Security) that you assign here.
OW360_R1005 79
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.
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 14: Multiple Network Planning Flowchart
80 OW360_R1005
4.6 What is backbone connectivity for multiple networks?
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 81)?
 What is collapsed backbone connectivity (see page 83)?
 How do I establish security and assign roles in a multiple network scheme?
4.6 What is backbone connectivity for multiple netw orks?
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 15: Example Configuration for Backbone Connectivity
OW360_R1005 81
4.6 What is backbone connectivity for multiple networks?
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. See
software configuration information.
82 OW360_R1005
4.7 What is collapsed backbone connectivity for multiple networks?
4.7 What is collapsed backbone connectivity for multiple netw orks?
The following figure illustrates the collapsed backbone that is typically used when units are
located within the same facility.
Figure 16: Example of configuration for Collapsed Backbone Connectivity
The collapsed backbone LAN consists of a pair of layer three switches. Layer three 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. See
software configuration information.
OW360_R1005 83
4.8 Licensing in Multiple Networks
4.7.1 Connections for core switches
The following information discusses the connections to core switches:

 Ports 1 - 15 -- Reserved for uplinks from Ovation systems' root switches.
 Ports 16 - 23 -- Intended for IP-only devices that support explicit configuration for 100
megabits per second/full-duplex connections (typically includes standalone Domain
Controllers, standalone eDB Historians, standalone Ovation Process Historians, modern
printers, modern GPS-based NTP servers, and so forth). Devices that are connected to these
ports are typically intended to be shared resources to be used by devices on each of the
lower-tier Ovation systems.
 Port 24 -- Intended for IP-only devices that cannot support explicit configuration for 100
megabits per second/full-duplex connections (typically includes legacy printers or GPS-based
NTP servers that may only support 10 megabits per second and/or half-duplex). Devices that
are connected to this port are typically intended to be shared resources to be used by devices
on each of the lower-tier Ovation systems.
4.8 Licensing in Multiple Netw orks
The number of remote networks, and local data servers must be licensed in the Ovation system.
The License Manager, accessed from the Ovation Developer Studio, only allows you to add as
many remote networks and data servers that are defined by a license key. Refer to Ovation
Developer Studio User Guide.
To obtain a license key, you must first access the License Manager on the Developer Studio and
record the locking code. Then, contact your Emerson representative during normal work hours.
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.
Once the license key is obtained, enter it into the License Manager. The license key defines the
number and types of remote networks and data servers that you can configure.
4.9 What security is needed for multiple netw orks?
When connecting multiple networks, you must plan ahead to define roles for both machines and
users. These roles are associated with specific permissions that allow or disallow various
activities on all connected Ovation networks. Roles are an essential component in maintaining the
security and integrity of your Ovation system.
After you define and configure your multiple networks, you need to consider system security.
Security for multiple networks is used to determine the users that can access the remote networks
and what operations they can perform.
Refer to Managing Ovation Security for information on security policies and role assignments, as
well as examples of how you can implement security and roles for your site's specific situation.
84 OW360_R1005
4.10 Hardware information for Ovation multiple networks
4.10 Hardw are information for Ovation multiple netw orks
Switches/Routers
The Cisco WS-C3560V2-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, inter-
virtual 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 for each 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 for second generation Ovation networks or to
standard drop/router ports for third generation Ovation networks. Do not connect these ports to a
port configured for connection to fan out areas or IP-only connections.
Ports 16 through 24 on the core and back-up core routers are configured as single sixteenth
VLAN to support direct connections of drops such as OPHs, Dedicated Domain Controllers, GPS-
based NTP servers, and anti-virus management stations with:
 Fixed 100mb/sec full-duplex setting.
 UDLD disabled.
 Spanning-Tree PortFast enabled.
Port 24 is configured for the connection of printers and other IP only devices with:
 Auto-negotiation enabled.
 UDLD disabled.
 Multi-cast traffic blocked.
OW360_R1005 85
4.10 Hardware information for Ovation multiple networks
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).
Use the standard 1X00063 Category 5 crossover cable. If a fiber optic connection is required, use
the 1X00484 or 1X00529 media converters in the standard switch-to-switch configuration.
86 OW360_R1005
S E C T I O N 5
5 Planning cable configurations for your Ovation

system
IN THIS SECTION
Network cable configuration types for your Ovation system ............................................. 87

Selecting network cable .................................................................................................... 89
Planning network and I/O field wiring routing .................................................................... 91
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 re-
certified 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.
OW360_R1005 87
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 multi-
mode 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.
88 OW360_R1005
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 89).
 Electro-Magnetic Interference (EMI) and Radio Frequency Interference (RFI) (see page 89).
 Grounding (see page 90).
 Node-to-node or total distance (see page 90).
 Permanently installed cable versus patch cables (see page 90).
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 87).
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.
OW360_R1005 89
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).
90 OW360_R1005
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 about 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).
OW360_R1005 91
I/O Noise Class Criteria
NOISE DE FINITION/EX AMP LES TYPE OF CONDUIT AND TRAY INFORMATION

CLASS CABLE
Q Includes analog I/O signals, Shielded Conduit or tray must be bonded to plant
digital pulse inputs to high- twisted pair. ground. Trays with 85% metallic coverage
(Quiet) speed counting circuits, and on top, side, and bottom are recommended.
(Very Low) data links.
L 24/48V digital I/O and contact Twisted pair Conduit or tray must be bonded to each
input. recommended. ground.
(Low)
M Digital I/O greater than 48V. Twisted pair Conduit or tray must be bonded to each
recommended. ground.
(Medium)
H AC/DC power signals: Cable type Both outgoing and return-carrying
 110 VAC, 250 VDC under determined by conductors to be pulled in same conduit or
(High) voltage and laid side by side in trays and secured in
15 A except brakes and
fields. current of vertical runs.
circuit.
 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.
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.
92 OW360_R1005
Minimum Spacing between Noise Classes
NOISE Q (QUITE/VERY L (LOW) M (MEDIUM) H (HIGH)

CLASSES1 LOW)
Q 15 cm (6 in) in tray 15 cm (6 in.) in tray 15 cm (6 in) in tray

(Very Low) or or or
7.6 cm (3 in) between conduit 7.6 cm (3 in) between
between conduit conduit
 25.4 cm (10 in) both
 35.6 cm (14 in) both
 51 cm (20 in) both
L 15 cm (6 in) in tray 15 cm (6 in) in tray 15 cm (6 in) in tray
(Low) or or or
7.6 cm (3 in) 7.6 cm (3 in) 7.6 cm (3 in)
between conduit between conduit between conduit
 30.5 cm (12 in) both
M 15 cm (6 in) in tray 15 cm (6 in) in tray 15 cm (6 in) in tray
(Medium) or or or
between conduit 7.6 cm (3 in) 7.6 cm (3 in) between
between conduit conduit
H 15 cm (6 in) in tray 15 cm (6 in) in tray 15 cm (6 in) in tray
(High) or or or
7.6 cm (3 in) 7.6 cm (3 in) 7.6 cm (3 in)
between conduit between conduit between conduit
 25.4 cm (10 in)  23 cm (9 in) both  15 cm (6 in) both
both  30.5 cm (12 in)  15 cm (6 in) both
 35.6 cm (14 in) both  23 cm (9 in) both
both  38 cm (15 in)
 51 cm (20 in) both both
OW360_R1005 93
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
60 VDC), 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
271).
94 OW360_R1005
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
271).
OW360_R1005 95
S E C T I O N 6
6 Planning grounding for your Ovation system
IN THIS SECTION
General grounding guidelines ........................................................................................... 97

Protective earth ................................................................................................................. 97
Ovation cabinet EMC grounding ....................................................................................... 97
Grounding guidelines for single cabinet arrangements..................................................... 98
Grounding guidelines for clustered cabinet arrangements ............................................. 100
6.1 General grounding guidelines
The following guidelines apply to all Ovation cabinet configurations:

 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.
6.2 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 212)). 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 95). 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.
OW360_R1005 97
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 17: Single Cabinet Arrangement
98 OW360_R1005
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 0.3249
1 0.2893
2 0.2576
3 0.2294
4 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 OF MULTIPLIER
WIRES
3 1.244
7 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
OW360_R1005 99
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 (solid wire (diameter in inches of AWG

19 wires) diameter for 4 with 19 stranded wires)
4 AWG)
1.147 x 0.2043 = 0.2343
Therefore, the diameter for a 4AWG conductor with 19 stranded wires would be 0.2343 inches.
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 101). Designate Cabinet #1 as the focal
cabinet. The focal cabinet is the cabinet in which the EMC ground connection is made.
Designate the other cabinets 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 sideskins 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 101) on all cabinets except the focal cabinet.
100 OW360_R1005
 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.
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 Auxiliary ground strap
Every cabinet has a factor installed strap between AUX GND and earth. The strap references the
Auxiliary power supply return (-) to earth. This strap should remain in place for all the
configurations.
6.5.2 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 100), 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 thumbscrews 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).
OW360_R1005 101
5. Reattach the cover using the four thumbscrews.
Figure 18: OCR400 or OCR1100 Controller and cabinet grounding cluster
102 OW360_R1005
S E C T I O N 7
7 Planning I/O modules for your Ovation system
IN THIS SECTION
What is an Ovation module? ........................................................................................... 103

What is the purpose of an Ovation I/O module? ............................................................. 104
Ovation I/O reference terminology .................................................................................. 104
Ovation I/O module features ........................................................................................... 109
Standard Ovation I/O module Base components ............................................................ 111
Standard two-slot Ovation I/O Base assembly (1B30035).............................................. 115
Marshalling two-slot I/O Base (1X00014) ....................................................................... 116
Marshalling two-slot I/O Base with secure connectors (5X00334) ................................. 117
Four-slot I/O Base with common strip connections (5X00497) ....................................... 118
Remote function modules (RIO) ...................................................................................... 120
Relay Output Bases ........................................................................................................ 122
What are the I/O module types? ..................................................................................... 130
Guidelines for replacing, adding, or combining Ovation modules ................................... 165
Installing Ovation standard I/O modules ......................................................................... 167
Installing Ovation Relay Output modules ........................................................................ 169
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. Refer to Ovation I/O Reference Manual and Ovation Bus
and Specialty 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, Refer to Q-Line Installation Manual for additional
information about the use and configuration of Q-Line I/O modules.
Specification sheets for each individual module type can be found in Ovation hardware
specification sheets.
OW360_R1005 103
7.2 What is the purpose of an Ovation I/O module?
7.2 What is the purpose of an Ovation I/O module?
Ovation control systems consist of a configurable mix of functional Input/Output (I/O) modules that
communicate with the Ovation Controller.
I/O modules provide an interface between the Ovation Controller and the processes in the plant.
Ovation I/O modules are a plug-in component with built-in fault tolerance and diagnostics. They
are able to operate on a wide range of signals and perform a multitude of functions.
Ovation I/O modules are seated into base units and are latched into place. Base units are housed
in the Controller cabinet where they are mounted on DIN rails and wired to the appropriate field
devices.
The standard modular components typically consist of the following:

 Electronics module (Emod).
 Personality module (Pmod).
 Base unit (containing the field terminations).
The relay output modular components consist of the following:
 Electronics module.
 Base unit (containing the field terminations).
7.3 Ovation I/O reference terminology

TERM DESCRIPTION
AC Mains Cables that carry the main AC current into the I/O cabinets.
AWG American wire gauge is used in the United States as a standard method of denoting wire
diameter. Increasing gauge numbers give decreasing wire diameters. Outside of North
America, wire sizes for electrical purposes are usually given as the cross sectional area
in square millimeters.
A Side Refers to the left side board-to-board connector of the base unit when the terminal block
or AUI Cable connector is facing the viewer.
Can also refer to the Controller cabinet or the "A" cabinet.
Analog signaling A low frequency current signal (usually 4-20 mA) from a Transmitter device to a Current
Input device.
Attention The Ovation I/O bus cycle status when the Electronics module returns a reply requesting
attention.
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.
Can also refer to the Termination cabinet or the "B" cabinet.
104 OW360_R1005
TERM DESCRIPTION
Base unit The DIN rail mounted base units consist of a printed circuit board, various connectors,
and plastic housing. The following Ovation bases are available:
 Standard two-slot I/O base
 Marshalling base (2-slot)
 Four-slot I/O base
 Relay Output base
The DIN Rail mounted Ovation base serves as the mechanical means to hold and secure
the Ovation I/O Electronics and personality modules. The base unit also provides a
mechanism for you to land field wiring and provides an electrical interface between the
field connections, Ovation Controller, and transition panels.
The base unit enables the Electronics Module to receive power and communicate over
the I/O bus, and also provides a low-impedance earth ground connection.
The Ovation bases when connected together form the Ovation I/O bus used by the
Ovation Controller to communicate with its I/O subsystem and the distribute power to the
I/O modules.
Each Standard two-slot Ovation I/O and Marshalling I/O base can house up to two sets
of electronic and personality I/O modules, while the Four-slot base unit can house up to
four sets of I/O modules.
The Relay Output base unit houses one Relay Electronics module.
The base unit enables the Electronics Module to receive power and communicate over
the I/O bus, and also provides a low-impedance earth ground connection.
Baud rate Number of bits-per-second a modem can send or receive.
Branch A set of two Four-slot base units or four Standard two-slot bases configured
consecutively on a DIN rail with a local Ovation I/O bus being connected to the Ovation
Controller. A Maximum of eight I/O modules is supported on a branch.
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.
Chatter Control A bit indicating the input channel has changed states enough to be checked until the flag
Flag is reset.
Chattering A condition when the input changes exceeded a specified number in the time between
when the DPU read the event buffer, or the rate of input changes exceed a specified
amount.
Compact I/O Ovation I/O modules that do not contain a Personality module, only an Electronics
modules module.
Contact Input An input where the electronics module supplies the contact wetting voltage.
Controller Interface between the Network and the I/O. The Controller is typically located in the
Ovation I/O or "A" cabinet. OCR400 or OCR1100. The Controller is a drop used to
control a process and passes process control information over the network to other drops
or devices that need it.
Current Sinking A digital voltage input circuit made of an input voltage protection, a serial current limiting
Digital Input circuit and an output interface. Each channel circuit terminates the connection between
the logic input and its associated high side sensor or switch. Any short circuit to the
reference potential or field wire breakages are interpreted as the “off” or “0” state.
OW360_R1005 105
TERM DESCRIPTION
DCS Distributed Control System.
Digital signaling The communication of information via the 1200bits/sec. Frequency Shift-Keying (FSK)
HART signal.
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 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 term used to refer to 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)
Dual attachment Connection to two different switches. A Dual Attached Station (DAS) is a node that is
connected to two different switches.
Electronics A plastic housing containing the necessary electronic circuitry and associated lenses and
module labeling to interface between field devices and the Ovation I/O bus. Electronics modules
are inserted directly into an Ovation I/O base unit and are typically (but, not always)
paired with an associated Personality module.
Event A digital input change of state detected by the Ovation Digital Input electronics module.
Fast Ethernet Ethernet specification that runs at 100 megabits per second.
Field A standard off-the-shelf user-configuration integrated circuit that is used to implement

Programmable custom logic functions.
Gate Array
(FPGA)
Four-slot I/O Each Four-slot I/O Base can house four sets of Electronics and Personality Modules,
Base along with the associated field wiring.
This base unit consists of a printed circuit card, various connectors, and plastic housing.
The base unit provides a mechanism to land field wiring and provide a connection from
the field signals to the personality module and then to the electronics module.
The base unit enables the electronics module to receive power and communicate over
the I/O bus and provides a low-impedance earth-ground connection.
Frequency Shift A method of modulation in which digital information is encoded into an analog signal.
Keying (FSK) Two distinct frequencies are utilized to represent a logic 0 or 1. In the HART protocol, a
logic 0 is represented by 2200 Hz, while a logic 1 is represented by 1200 Hz.
Galvanic The principle of isolating functional sections of electronic circuits so that charge-carrying
Isolation particles cannot move from one section to another, for example, there is no electrical
current flowing directly from one section to the next. Energy and/or information can still
be exchanged between the sections by other means, however, such as by capacitance,
electromagnetic waves, or mechanical means.
HART Highway Addressable Remote Transducer.
Hot swappable Provides the capability of removing and installing the I/O module from the base unit with
power applied.
IOIC card Generic name for the Controller PCI I/O Interface card. The OCR400 Controller and
OCR1100 Controller require the IOIC module.
106 OW360_R1005
TERM DESCRIPTION
IOSC The I/O Slave Controller FPGA, located on every Electronics Module, provides a slave
interface to the master controllers.
I/O Module Standard Ovation I/O modules are made up of an Electronics module and a Personality
module. These modules perform the interface between the Ovation I/O Controller and
the field devices.
Compact modules and Relay Output modules do not contain a Personality module.
Wide-bodied modules do not require a personality module since some of the functions of
the personality module are incorporated within the module.
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.
LSB Least significant bit.
Master Contains the entire process database. It is used for creating, modifying, and verifying
Database 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 (through an AUI cable) to the RNC (through a fiber-optic cable)
in remote I/O applications.
Membrane Also known as the Ovation Keyboard. Optional keyboard that is used in conjunction with
Keyboard 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.
MSB Most significant bit.
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.
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 Network Local area network in which Ovation drops communicate with each other through Fast
Ethernet media.
Partial Rotation A partial rotation is directly associated with samples. Samples, representing pulses and
time elapsed for those pulses, are combined each sample period into the pulse count
and time elapsed for a full rotation. Typically, a partial rotation is what is sampled.
OW360_R1005 107
TERM DESCRIPTION
Personality The plastic housing with associated lenses and labeling that contains a printed circuit
module card to perform the necessary signal interconnections between the base unit’s
termination block and the electronics module as required for a particular application.
The personality module may also contain various passive components for transient
protection, but the Media Attachment Unit module and Remote Node Controller contain
fiber-optic transmitters, receivers, and transceivers in their Personality modules. The Link
Controller I/O module contains optical couplers and RS-232/RS-485 transceivers in its
Personality module. The module plugs directly into the base.
PLD Programmable Logic Device (Complex Programmable Logic Device). A standard off-the-
shelf user-configurable integrated circuit that is used to implement custom logic functions
using Flash memory.
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).
Remote Node A grouping of I/O modules that communicates with the Controller through media that can
carry control signals over a long distance (for example, fiber-optic).
RNC Remote Node Controller (RNC) is an alternate name for the 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
through a fiber-optic communication link.
Rotation Time The time of a full rotation of the toothed wheel given in 24 MHz timer ticks. Normally the
rotation time is the summation of a number of sample times.
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.
Server A computer, or software program that provides a specific kind of service to client
software running on other computers.
Single Connection to one switch. A Single Attached Station (SAS) is a node that is connected to
attachment 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, which is the network reference number for each point that
may be transmitted.
TCP/IP Transmission Control Protocol / Internet Protocol, a set of communication protocols that
allows dissimilar computers to share information over a network.
Termination Refers to the Ovation "B" cabinet. The termination cabinet houses termination block
cabinet locations to land internal and external wiring.
108 OW360_R1005
7.4 Ovation I/O module features
TERM DESCRIPTION
Transition Types are:

Panels
ROP - I/O transition panel.
TND - Remote Node transition panel.
RRP - Relay base transition panel (top location).
RRB - Relay base transition panel (bottom location).
Transmitter A Data Link Layer term for a device (such as a field instrument) that responds to a
Current Input (Primary Master) or Secondary (Secondary Master) device.
Watchdog Timer A timer that, if allowed to expire, will reset the microprocessor.
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.
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.
 Wiring directions are provided on the Base Unit for Relay Output modules:
 Normally Closed (NC).
 Normally Open (NO).
 Common (C).
OW360_R1005 109
 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.
110 OW360_R1005
7.5 Standard Ovation I/O module Base components
Standard Ovation I/O module bases combine Personality modules with Electronics modules in
order to operate a wide range of communication signals, and perform a multitude of input and
output functions.
Standard Ovation bases consist of the following:

 Base unit (containing I/O bus power, signals, and field terminations).
 Electronics module, referred to as an Emod.
 Personality module, referred to as a Pmod.
 Cavity insert - (Foam or plastic inserts are used in place of Personality modules).
 Terminal blocks for field termination
 Two-way interface connections (TWI connections)
A Standard Ovation I/O Base is illustrated below and describes its attributes:
OW360_R1005 111
Figure 19: Standard two-slot Ovation I/O Base
112 OW360_R1005
1. Base unit
Each base unit accommodates two Ovation Electronics (Emod) and Personality (Pmod)
modules and mounts onto a mounting bracket referred to as a DIN Rail.
The dimensions of a Standard Ovation I/O Base unit are:
27.9 cm Long (11 in)
12.7 cm Wide (5 in)
16.5 cm High (6.5 in)
The Standard Ovation two-slot I/O Base can be used for either singular or dual I/O modules.
For the Marshalling base unit, See Marshalling two-slot I/O Base assembly (1X00014) (see
page 116) for more information.
CAUTION! For CE Mark Certified Systems:
Base units containing differential digital input modules configuration with hazardous input
voltages (>30 V RMS, 42.4 V peak, or 60 VDC) listed in the following table must include a
hazardous voltage warning label (1B30025H01) on that base unit. Hazardous voltage is
present on the individual module terminal blocks and module connector(s).
Differential digital input module configurations with hazardous input voltages
CONFIGURATION EMOD PMOD
125VAC/VDC Digital Input (Diff) 1C31107G02 1C31110G02

125VAC/VDC Compact Digital Input (Diff) 1C31232G03 1C31238H01
125VDC Sequence of Events (Diff) 1C31157G02 1C31110G02
125VDC Compact Sequence of Events (Diff) 1C31233G03 1C31238H01
125VDC Enhanced Compact Sequence of Events (Diff) 5X00357G03 1C31238H01
CAUTION! Base units containing single-ended or fused digital input modules with hazardous
voltages (>30 V RMS, 42.4 V peak, or 60 VDC) listed in the following table must include a
hazardous voltage warning label (1B30025H01) on the base unit as well as ALL base units of
the branch. Hazardous voltage is present on terminal block and module connectors of bases
on an entire branch. In addition, auxiliary power fuses must be removed and a fuse cover kit
should be added.
OW360_R1005 113
Base units containing single-ended or fused digital input modules with hazardous voltages
CONFIGURATION EMOD PMOD
125VAC/VDC Digital Input (Sing) 1C31107G02 1C31110G01

125VAC/VDC Compact Digital Input (Fused) 1C31232G03 5X00034G01
125VDC Sequence of Events (Sing) 1C31157G02 1C31110G01
125VDC Compact Sequence of Events (Fused) 1C31233G03 5X00034G01
125VDC Enhanced Compact Sequence of Events (Fused) 5X00357G03 5X00034G01
CAUTION! Hazardous labels must be placed in a visible location on the base unit, preferably
above the spare fuse location. This information is indicated in the application specific project
drawings.
2. Electronics module (Emod)

The Electronics module fits securely into the base unit. (Emods are configured by adding the
appropriate Personality module)
3. Personality module (Pmod)
The Personality module fits into the base unit beside the appropriate Electronics module.
(Pmods are used to configure the Electronics module).
Note: The Personality module is installed in the base unit first. Then, the Electronics module is
installed and interlocks with the Personality module. The blue latches on the Electronics module
locks both modules into the Base.
Wires from field devices are connected to terminal blocks located on the base.
Each Emod/Pmod pair requires a unique wiring diagram that is typically illustrated on the side of
each Electronics module, Personality module, or cavity insert. The wiring connection diagrams
are also shown for each module in this manual in the associated module sections.
114 OW360_R1005
7.6 Standard two-slot Ovation I/O Base assembly (1B30035)
7.6 Standard tw o-slot Ovation I/O Base assembl y (1B30035)
A Standard Ovation I/O Base houses up to two Standard Ovation I/O modules. Standard Ovation
Emods and Pmods modules fit securely into the Ovation I/O Base. Each standard I/O module is
assigned a logical address. A Standard I/O Base occupies two logical module addresses, one
address is assigned for each module housed within the base unit.
Note: Some Ovation I/O modules are specifically designed for the Four-slot I/O Base. Refer to
the Four-slot I/O Base assembly (5X00497) (see page 118) section for more information.
The following diagram illustrates a typical Standard two-slot Ovation I/O Base assembly
(1B30035H01):
Figure 20: Standard two-slot Ovation I/O Base
Note: I/O Bases are mounted to the DIN Rail by a 1/4 inch hex head mounting screw clamp
located in the middle of the Base. The torque specification for tightening the mounting screw is
33 to 35 inch pounds or, 3.73 to 3.95 N·m.
The torque specification for the terminal block termination screws is 5 to 7 inch pounds or, 0.56
to 0.79 N·m. Single wire: 22-12 AWG, Two-wire: 14AWG max each.
OW360_R1005 115
7.7 Marshalling two-slot I/O Base (1X00014)
7.7 Marshalling tw o-slot I/O Base (1X00014)
The Ovation Marshalling Base unit serves as an interface between the field connections, the I/O
bus, and the Personality and Electronics Modules. The I/O bus is used by the Controller to
communicate with the I/O subsystem through the Ovation Marshalling base unit backplane.
Power is distributed to the Electronics module through the I/O bus.
The Ovation Marshalling Base unit is similar to the Standard Ovation I/O Base except that the
field termination terminal blocks are replaced with 17 Pin connector headers. The headers are
mated with 17-position connectors. This arrangement allows the use of pre-terminated cables for
field wiring. Marshalling cabling and pinout information is typically specified at the projects level in
the project wiring diagrams and cable lists.
The following diagram illustrates a typical two-slot Ovation Marshalling I/O Base:
Figure 21: Marshallng two-slot I/O Base
33 is 35 inch pounds or, 3.73 is 3.95 N·m.
Rows A, B, and C, are 17 pin connectors providing a total of 51 termination points for field
cabling.
116 OW360_R1005
7.8 Marshalling two-slot I/O Base with secure connectors (5X00334)
7.8 Marshalling tw o-slot I/O Base w ith secure connectors (5X00334)
The Ovation Marshalling Base unit serves as an interface between the field connections, the I/O
bus, and the Personality and Electronics Modules. The I/O bus is used by the Controller to
communicate with the I/O subsystem through the Ovation Marshalling base unit backplane.
Power is distributed to the Electronics Modules through the I/O bus. Marshalling I/O Bases house
two Ovation I/O modules.
The Ovation Marshalling Base with secure connectors is similar to the Standard Marshalling I/O
Base except that the cable connectors can be secured to the headers with a secure screwed-
down connection. Cables utilize (1X00439H01) cable connectors.
Pinout information for Marshalling cables is typically found at the project level in the project wiring
diagrams and cable lists.
The following figure illustrates a typical configuration for the Marshalling I/O Base with secure
connectors:
Figure 22: Marshalling I/O Base with secure connectors
Rows A, B, and C, are 17 pin connectors providing a total of 51 termination points for field
cabling.
Screw sockets are provided at each end of the connector to secure pre-wired cable connectors.
OW360_R1005 117
7.9 Four-slot I/O Base with common strip connections (5X00497)
7.9 Four-slot I/O Base w ith common strip connections (5X00497)
The Four-slot I/O Base assembly houses four Ovation I/O modules. The electrical functionality of
the Four-slot I/O Base is identical to the Standard two-slot I/O Base.
Note: Some Ovation I/O modules are keyed and will only operate in the Four-slot I/O Base.
The following I/O modules require the use of a Four-slot I/O Base:
 5X00499 Digital Input module 24 VDC (32 Channel)
 5X00500 Digital Output module 24 VDC (32 Channel)
 5X00501 Analog Input module 4-20 mA (16 Channel)
 5X00594 Thermocouple Analog Input module (16 Channel) - (TCI)
 5X00605 Sequence of Events Contact Input module (32 Channel) - (SOE)
 5X00622 RTD Analog Input module (16 Channel) - (RTD-16)
The following figure illustrates a typical Four-slot Ovation I/O Base:
118 OW360_R1005
7.9 Four-slot I/O Base with common strip connections (5X00497)
Figure 23: Four-slot I/O Base
OW360_R1005 119
7.10 Remote function modules (RIO)
Note: I/O Bases are attached to the DIN Rail by a 1/4 inch hex head mounting screw clamp
located in the middle of the Base. The torque specification for tightening the DIN Rail mounting
screw is 33 to 35 inch pounds or, 3.73 to 3.95 N·m.
Termination Torque specifications:
Rows A, B, and C termination screws = 3 to 4 inch pounds or, 0.33 to 0.45 N·m.
Single wire: 22-12 AWG, Two-wire: 14AWG max each. Rows A, B, and C, provide a total of 53
termination points for field cabling.
Row D termination screws = 3.5 to 4.0 inch pounds or, 0.39 to 0.45 N·m.
16AWG Maximum, ferrule is required. (16AWG insulated ferrule - 1X00561H01). Row D
provides 16 common ground termination screws per module, (2 terminations are permitted per
terminal position - providing a total of 32 terminations).
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 as the standard I/O
modules have.
120 OW360_R1005
7.10.1 MAU with typical fiber-optic connector pairs for OCR400 and OCR1100
Controllers
The following figure illustrates an MAU I/O Base:
Figure 24: MAU with typical fiber-optic connector pairs
OW360_R1005 121
7.11 Relay Output Bases
7.10.2 Remote Node Controller (RNC) (1C31205)
The following figure illustrates a typical Remote Node Controller (RNC) module. RS232 Serial
Ports are accessible on the RNC Pmod for fiber-optic media.
Figure 25: Remote Node Controller Module (RNC) (for fiber-optic media)
7.11 Rela y Output Bases

The Relay Output base is 1.5 times longer than the Standard Ovation I/O Base (approximately
17 inches) which allows additional space to house the relays. The relay output base houses one
relay electronics module and requires one I/O address.
The figures in the following sections illustrate hardware components that may be contained in
both Controller cabinets, remote node cabinets, and extended cabinets:
 Relay Output Base (32 channel fused) low-power relay (5X00623G01) (see page 123)
 Relay Output Base (32 channel non-fused) Slim 28x5mm relay (5X00584G01-G02) (see
page 123)
 Relay Output Base (16 Channel fused) low-power GR2 (5X00431G01-G02) (see page 125)
 Relay Output Base (16 channel non-fused) low-power GR2 (1C31223G01) (see page 125)
 Relay Output Base (12 channel fused) high-power, KUEP (5X00430G01-G04) (see page 126)
 Relay Output Base (12 Channel non-fused) high-power KUEP (1C31222G01) (see page 127)
 Relay Output Base (8 Channel with contact monitoring) high power KUEP (5X00564G01-
G02) (see page 129)
122 OW360_R1005
7.11.1 Relay Output Base (32 channel fused) Slim 28x5mm relay (5X00623)
The following diagram illustrates a (fused) 32 channel Relay Output Base:
Figure 26: Relay Output Base - 32 Channel (fused)
Note: Relay Bases are mounted to the DIN Rail by a 1/4 inch hex head mounting screw clamp
Terminal blocks TB1 through TB32 are used for field terminations.
The torque specification for the terminal block termination screws is 4.4 to 5.3 inch pounds or,
0.5 to 0.6 N·m.
Single wire: 22-12 AWG.
OW360_R1005 123
7.11.2 Relay Output Base (32 channel non-fused) Slim 28x5mm relay (5X00584)
The following diagram illustrates a (non-fused) 32 channel Relay Output Base:
Figure 27: Relay Output Base - 32 Channel (non-fused)
0.5 to 0.6 N·m. (Single wire: 22-12 AWG).
124 OW360_R1005
7.11.3 Relay Output Base (16 channel fused) low -power relay GR2 (5X00431)
The following diagram illustrates a (fused) 16 channel low-power Relay Output Base (w/GR2
relays):
Figure 28: Relay Output Base (fused) 16 Channel Low Power GR2
located in the middle of the Base.
The torque specification for tightening the DIN rail mounting screw is 33 to 35 inch pounds or,
3.73 to 3.95 N·m.
OW360_R1005 125
7.11.4 Relay Output Base (16 channel non-fused) low-power relay GR2 (1C31223)
The following diagram illustrates a (non-fused) 16 Channel low-power Relay Output Base (w/GR2
relays):
Figure 29: Relay Output Base (16 channel non-fused) low-power GR2 (1C31223)
0.50 to 0.60 N·m. (Single wire: 22-12 AWG).
126 OW360_R1005
7.11.5 Relay Output Base (12 channel fused) high-power relay KUEP (5X00430)
The following figure illustrates a 12 channel high-power Relay Output Base (w/KUEP relays).
Figure 30: Relay Output panel - 12 channel fused
OW360_R1005 127
7.11.6 Relay Output Base (12 channel non-fused) high-power KUEP (1C31222)
The following diagram illustrates a (non-fused) 12 channel high-powered Relay Output Base
(w/KUEP relays).
Figure 31: Relay Panel Base 12 Channel High Power KUEP
The torque specification for the terminal block termination screws is 4.4 inch pounds or, 0.50
N·m.
Single wire: 22-12 AWG (solid) - 22-14 (stranded).
128 OW360_R1005
7.11.7 Relay Output Base (8 channel with contact monitoring) high -power KUEP
(5X00564)
The following diagram illustrates an 8 channel high-power Relay Output Base with contact
monitoring:
Figure 32: Relay Output Base (8 channel with contact monitoring) high-power
The tightening torque for P1, P2, P3, and P4 termination screws = 4.4 to 5.3 inch pounds or 0.5
to 0.6 N·m.
The tightening torque for P5 termination screws = 2.0 to 2.2 inch pounds or 0.22 to 0.25 N·m.
OW360_R1005 129
7.12 What are the I/O module types?
Ovation supports the following I/O module types:
Analog Input modules

 Analog Input module (13 Bit) (8 Channel) (Legacy product) (see page 131)
 Analog Input module (14 Bit) (8 Channel) (see page 132).
 Analog Input High Speed module (14 Bit) (8 Channel) (see page 133).
 Analog Input module (0-10V High Impedance) (8 channel) (see page 133).
 HART Analog Input module (8 Channel) (see page 134).
 HART High Performance Analog Input module (8 Channel) (see page 134).
 RTD Analog Input module (4 Channel) (see page 135).
 RTD Analog Input module (8 channel Compact) (see page 136).
 Analog Input module 4-20mA (16 Channel) (see page 137)
 Thermocouple Input module (16 Channel) (see page 137).
Analog Output modules

 Analog Output module (4 Channel) (see page 138).
 HART Analog Output module (8 Channel) (see page 138).
 HART High Performance Analog Output module (4 Channel) (see page 139).
Digital Input modules

 Digital Input module (16 Channel) (see page 139).
 Digital Input Redundant module (16 Channel) (Windows Ovation 3.2 and above) (see page
140).
 Digital Input Compact module (16 Channel) (see page 140).
 Digital Input Contact module (16 Channel) (see page 141).
 Digital Input Compact Contact module (16 Channel) (see page 141).
 Sequence of Events Digital Input module (16 Channel) (see page 141).
 Sequence of Events Contact Input Field module (32 Channel) (see page 142).
 Sequence of Events Compact Digital Input Field Interface module (16 Channel) (see page
143).
 Sequence of Events Enhanced Compact Digital Input module (16 Channel) (see page 144).
 Digital Input module 24 VDC (32 Channel) (see page 145).
Digital Output modules

 Digital Output module (16 Channel) (see page 145)
 Digital Output module 24 VDC (32 Channel) (see page 146).
 Digital Output High Side (24 VDC) module (16 Channel) (see page 146).
130 OW360_R1005
Relay Output modules

 Relay Output panel (see page 147).
 Relay Output panel with Contact Monitoring module (see page 148).
 Relay Output panel (32 Channel) (see page 149).
 Relay Output (Fused) panel. (see page 150)
Bus interface modules

 Foundation Fieldbus module (see page 151).
 Profibus DP module (see page 151).
 DeviceNet module (see page 151).
 Ethernet Link Controller (ELC) module (see page 152).
Specialty modules
 Link Controller module (see page 152).
 Loop Interface module (see page 153).
 Pulse Accumulator module (see page 156).
 Servo Driver module (see page 157).
 Speed Detector module (see page 158).
 Valve Positioner module (see page 162) (standard and triplex).
 Small Loop Interface module (SLIM) (see page 163).
 Numalogic Fast Ethernet Remote Node (see page 163).
 Machinery Health module (see page 164).
 Digital Excitation Controller module (see page 165).
7.12.1 Analog Input module (13 Bit) (8 Channel) (Legacy product)
The Analog Input module (13 bits) 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.
Due to power factor correction in Ovation power supplies, Power and VA are the same.
Analog Input valid module combinations (13-bit)1
RANGE CHANNELS ELECTRONICS PERSONALITY

MODULE MODULE
± 20mV 8 1C31113G011 1C31116G01
±50mV 8 1C31113G021 1C31116G01
± 100mV 8 1C31113G031 1C31116G01
± 20mV Compensated (Thermocouple) 83 1C31113G011 1C31116G04
OW360_R1005 131

MODULE MODULE
± 1 VDC 8 1C31113G041 1C31116G01
± 5 VDC 8 1C31113G051 1C31116G01
± 10 VDC 8 1C31113G061 1C31116G01
0-20 mA Field powered 8 1C31113G051, 2 1C31116G02

(4-20 mA Field powered can also be selected)
0-20 mA Locally powered 8 1C31113G051, 2 1C31116G03
(4-20 mA Locally powered can also be selected)
1 This module configuration is CE Mark certified.

3 This module configuration is CE Mark certified (Non-EMC Cabinet).
3 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 when
defining the eight other thermocouple points for the AI module. (Refer to Ovation Developer Studio User
Guide.
7.12.2 Analog Input module (14 Bit) (8 Channel)
The Analog Input module (14 bits) 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.
Analog Input valid module combinations (14-bit)

MODULE MODULE
4 - 20mA, Field or Locally powered1 8 1C31224G011 1C31227G01
± 1 VDC 8 1C31224G021 1C31227G02
1 The 4-20mA configuration is CE Mark certified.
132 OW360_R1005
7.12.3 Analog Input High Speed module (14 Bit) (8 Channel)
The Analog Input High Speed module (14-Bit) 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.
High Speed Analog Input valid module combinations (14-bit )

MODULE MODULE
4 - 20mA, Field or Locally powered 8 5X00070G011,2 1C31227G01
± 100mV, ± 250mV, ± 1V 8 5X00070G021,2 1C31227G02
± 5V, ± 10V 8 5X00070G031,2 1C31227G02
± 1mA 2 wire local powered 8 5X00070G021,2 1C31116G03
± 1mA 4wire field powered 8 5X00070G021,2 1C31116G02
± 20mV,  50mV,  100 (Thermocouple) 8 5X00070G041 1C31116G04
± 20mV,  50mV,  100 (Thermocouple) 8 5X00070G052 1C31116G04
1This module configuration is CE Mark certified.

7.12.4 Analog Input module (0-10V High Impedance) (8 channel)
The 8 channel 0-10V High Impedance Analog Input module converts 0-10V analog signals to
digital equivalents with a much higher input impedance than is available with standard Ovation
Analog Input modules. Eight sets of isolated input channels are provided. The converted input
signals are formatted to conform to the 14 bit Ovation data format and stored on the module. The
digitized data is presented to the Ovation Controller through the control systems I/O bus and is
available on demand.
The 0-10V High Impedance Analog Input I/O module provides signal conditioning and analog-to-
digital conversion for eight individually isolated inputs.
High Impedance Analog Input valid module combinations (0-10V High Impedance AI)

MODULE MODULE
0 - 10V High Impedance Analog Input 8 5X00679G01 1C31227G02

This module configuration is CE Mark compliant when used with shielded cables.
OW360_R1005 133
7.12.5 HART Analog Input module (8 Channel)
The HART Analog Input 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.
HART Analog Input valid module combinations (16-bit) 1

MODULE MODULE
4-20 mA loop powered (2 wire) or active source 8 5X00058G011 5X00059G01

(4 wire)
7.12.6 HART High Performance Analog Input module (8 Channel)
The HART High Performance Analog Input 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.
HART High Performance Analog Input valid module combinations (14-bit)

MODULE MODULE
4-20 mA 1 8 5X00106G01 5X00109G01

or
5X00109G02 (Ovation
releases 3.4 and later)
4-20 mA2 (Reduced radiated emissions). 8 5X00106G02 5X00109G01

or
5X00109G02 (Ovation
releases 3.4 and later)
1This module configuration is CE Mark certified.
134 OW360_R1005
7.12.7 RTD Analog Input module (4 Channel)
The RTD module (4 Channel) module provides an interface to four galvanically isolated
Resistance Temperature Detectors. Several three and four-wire RTD types are supported. A
50/60 Hz filtered configuration is available for CE Mark applications.
RTD (4 Channel) module valid module combinations

MODULE MODULE
All 4 1C31161G01 1C31164G01

All (for 50/60 Hz filtered inputs and CE Mark certified 4 1C31161G02 1 1C31164G02 1
systems)
1 Configuration 1C3116G02 / 1C31164G02 is CE Mark certified.
The RTD (8 Channel) module provides an interface to eight Resistance Temperature Detectors
(channels). Several three- and four-wire RTD types are supported.
RTD module (8-Channel) valid module combinations1
CHANNELS ELECTRONICS MODULE PERSONALITY MODULE
8 5X00119G011 5X00121G01
8 5X00119G022 5X00121G01
8 5X00119G03 5X00121G01
2 This module configuration is CE Mark certified (Non-EMC cabinet).
OW360_R1005 135
7.12.9 RTD Analog Input module (8 Channel Compact)
The RTD Input Subsystem is used to convert inputs from Resistance Temperature Detectors
(RTD's) to digital data.
The RTD Input Subsystem is implemented by an 8 Channel RTD Input Electronics Module
(5X00621).
The function of the RTD Input Subsystem is used to convert the resistance (RX) of a Resistance
Temperature Detector (RTD) to a 14 bit digital output. The 14 bit output is a linear progression of
integer values, where 0 (zero) represents 0 ohms and 0x3FFF equals the maximum resistance of
the range selected.
8 Channel RTD Analog Input valid module combinations
DESCRIPTION CHANNELS ELECTRONICS PERSONALITY MODULE

MODULE
8 Channel Analog Input (only 3-wire 8 5X00621G01 1X00885H01

RTD's are supported) (Cavity insert)
This module is CE Mark compliant.
The RTD Input Subsystem is implemented by a 16 Channel RTD Input Electronics Module
(5X00622).
The function of the RTD Input Subsystem is used to convert the resistance (RX) of a Resistance
Temperature Detector (RTD) to a 14-bit digital output. The 14-bit output is a linear progression of
integer values, where 0 (zero) represents 0 ohms and 0x3FFF equals the maximum resistance of
the range selected.
Note: The 16 channel RTD module requires a four-slot I/O base with common shield strip
connections.
The 16 channel RTD module supports three-wire RTDs only.
16 Channel RTD Analog Input valid module combinations
DESCRIPTION CHANNELS ELECTRONICS PERSONALITY MODULE

MODULE
16 Channel Analog Input (only 3-wire 16 5X00622G01 N/A

RTD's are supported)
This module is CE Mark compliant.
136 OW360_R1005
7.12.11 Analog Input module 4-20mA (16 Channel)
The 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 4-
wire) transmitters can be connected per module.
16 Channel 4-20mA Analog Input valid module combinations
DESCRIPTION CHANNELS ELECTRONICS PERSONALITY

MODULE MODULE
16 Channel 4-20mA Analog Input, 2- 16 5X00501G01 5X00502G01

wire and 4-wire
16 Channel 4-20mA Analog Input, 2- 16 5X00501G01 1X00692H01
wire only
This module configuration is CE Mark certified.
Note: A 16 Channel 4-20mA Analog Input module must be inserted into an Ovation 4-slot I/O
base (5X00497G01) for proper operation. The Ovation 16 Channel Analog Input module will not
function in a standard 2-slot Ovation I/O base.
7.12.12 Thermocouple Input module (16 Channel)
The 16 Channel Thermocouple Input module provides signal conditioning and analog-to-digital
conversion for 16 individually isolated inputs. The module is designed to convert thermocouple
signals to digital equivalents. The converted input signals are formatted to conform to the 14-bit
Ovation data format and stored on the module.
16 Channel Thermocouple valid module combinations (16-bit) 1

MODULE MODULE
20 mV, 50 mV, 100 mV 16 5X00594G011 1C31116G05
1 This module configuration is CE Mark compliant.
OW360_R1005 137
7.12.13 Analog Output module (4 Channel)
The Analog Output module provides an interface to four individually isolated analog outputs
(channels) using 12-bit digital to analog converters.
Analog Output valid module combinations

MODULE MODULE
0-5 Volts DC 4 1C31129G011 1C31132G01
0-10 Volts DC 4 1C31129G021 1C31132G01
0-20 mA with Diagnostics 4 1C31129G031 1C31132G01

(4-20 mA with Diagnostics can also be selected)
0-20 mA without Diagnostics 4 1C31129G041 1C31132G01

(4-20 mA without Diagnostics can also be
selected)
4-20 mA with Diagnostics (For redundant 4 1C31129G052 1C31132G02
applications)
2 For redundant applications using Windows Ovation 3.2 and above.
7.12.14 HART Analog Output module (8 Channel)
The HART Analog Output module provides an interface for eight HART field devices with 4-20
mA current loop analog outputs (channels) (common reference). In addition to the analog outputs,
digital information can be exchanged between HART compliant devices and the Controller.
HART Analog Output valid module combinations (14 bit) 1
RANGE CHANNELS ELECTRONICS MODULE PERSONALITY MODULE
4-20 mA 8 5X00062G011 5X00063G01
138 OW360_R1005
7.12.15 HART High Performance Analog Output module (4 Channel)
The HART High Performance Analog Output 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.
HART High Performance Analog Output valid module combinations (14-bit)1
RANGE CHANNELS ELECTRONICS PERSONALITY MODULE

MODULE
4-20 mA 4 5X00167G011 1X00188H01 (molded plastic cavity insert)
4-20 mA 4 5X00167G01 5X00211G03 (Q-line migration)

7.12.16 Digital Input module (16 Channel)
The 16 channel Digital Input 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).
Digital Input valid module combinations 1

MODULE MODULE
24/48 VAC/VDC Single-ended 16 1C31107G01 1C31110G01

Differential 16 1C31107G01 1C31110G02
125 VAC/VDC Single-ended 16 1C31107G02 1C31110G01

Differential 16 1C31107G02 1C31110G02
1 All module configurations listed in the table are CE Mark certified.
OW360_R1005 139
7.12.17 Digital Input Redundant module (16 Channel) (Windows Ova tion 3.2
and above)
The 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 24 VDC auxiliary power source.
Redundant Digital Input valid module combinations

MODULE
24 V (Single-ended) Digital Input 16 5X00411G01 5X00414G01

current sinking, IEC 61131-2
Compliant Type 1 digital Inputs.
7.12.18 Digital Input Compact module (16 Channel)
The Compact Digital Input module provides a low cost interface for 16 current-sinking digital
inputs (channels) by eliminating the need for a Personality module. 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).
Compact Digital Input valid module combinations
RANGE 1 CHANNELS ELECTRONICS MODULE PERSONALITY MODULE

OR CAVITY INSERT
2
24/48 VDC Single-ended 16 1C31232G01 1C31238H01 (molded

plastic cavity insert)
24 VAC/VDC Differential 16 1C31232G02 1C31238H01 (molded
48 VDC Differential
24 VAC/VDC, Individually 16 1C31232G02 5X00034G01(Fused Pmod)
fused, common power supply
48 VDC, Individually fused,
common power supply
24 VDC, Individually current 16 1C31232G02 5X00765G01 (current
limited, common power supply limited Pmod3)
125 VAC/VDC, Individually 16 1C31232G03 5X00034G01 (Fused
fused, common power supply Pmod)
125 VAC/VDC Differential 1C31232G03 1C31238H01(molded
2 This is an insert that fits into the Personality module position and provides a wiring schematic label for the
module.
3 Only applicable for 24VCD.
140 OW360_R1005
7.12.19 Digital Input Contact module (16 Channel)
The 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 (single-
ended – channels have a common return, which is the return for the on-module 48 VDC current
limited contact wetting power supply).
Contact Digital Input valid module combinations1

MODULE
48 VDC On-Card Auxiliary (Legacy) 16 1C31142G01 1C31110G03
7.12.20 Digital Input Compact Contact module (16 Channel)
The 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 on-
module 48 VDC current limited contact wetting power supply).
Compact Contact Digital Input valid module combinations 1
RANGE CHANNELS ELECTRONICS MOLDE D PLAS TIC

MODULE CAV ITY INS ERT 2
Compact Contact with 48 VDC On-Card 16 1C31234G01 1C31238H01

Auxiliary
2 This is an insert that fits into the Personality module position and provides a wiring schematic label for the
module.
OW360_R1005 141
7.12.21 Sequence of Events Digital Input module (16 Channel)
The Sequence of Events Digital Input module provides an interface for 16 digital inputs
(channels) with time tagging information to within 125 s. The 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 valid module combinations

MODULE MODULE
24/48 VDC Single-ended (Legacy) 16 1C31157G01 1C31110G01

Differential (Legacy) 16 1C31157G01 1C31110G02
125 VDC Single-ended (Legacy) 1C31157G02 1C31110G01
Differential (Legacy) 16 1C31157G02 1C31110G02
48 VDC with On-card Wetting Supply 16 1C31157G03 1C31110G03
(Contact input)
All module configurations listed in the table are CE Mark certified unless they contain a 5FDI.
7.12.22 Sequence of Events Contact Input Field module (32 Channel)
The 32 Channel Sequence of Events Contact Digital Input module performs sequence of
event functions. This module provides 32 contact channels in a single-ended contact input format
to monitor the states (“0” or “1”) of 32 field contact inputs and includes digital input state change
detection (SOE One Shot). The SOE one shot feature enables SOE event detection that happen
asynchronously to Controller tasks that read the present input state and event buffers.
32 Channel Sequence of Events Contact Digital Input valid module combinations
RANGE CHANNELS ELECTRONICS CAV ITY

MODULE INSERT
32 Channel Contact Input SOE 32 5X00605G01 1X00884H01

This module configuration is CE Mark compliant.
142 OW360_R1005
7.12.23 Sequence of Events Compact Digital Input Field Interface module (16
Channel)
The Sequence of Events Compact Digital Input 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
personality module can be added to individually fuse some digital inputs (with common return).
Sequence of Events Compact Digital Input valid module combinations 1

MODULE MODULE OR
CAV ITY INS ERT 1
Compact 24/48 VDC SOE Single-ended 16 1C31233G01 1C31238H012

digital input (molded plastic
cavity insert)
Compact 24/48 VDC SOE Differential 16 1C31233G02 1C31238H012
cavity insert)
Compact 24/48 VDC SOE Individually 16 1C31233G02 5X00034G01
fused, common power supply digital input (Fused Pmod)
Compact 24 VDC SOE, Individually 16 1C31233G02 5X00765G01 (P)
current limited, common power supply (current limited
digital input Pmod3)
Compact 125 VDC SOE Differential 16 1C31233G03 1C31238H012

cavity insert)
Compact 125 VDC SOE Individually 16 1C31233G03 5X00034G01
fused, common power supply digital input (Fused Pmod)
Compact 48 VDC SOE On-card auxiliary 16 1C31233G04 1C31238H012
Contact Input w/48V wetting (molded plastic
cavity insert)
1 All module configurations listed in this table are CE Mark certified.
2 This is a cavity insert that fits into the Personality module position and provides a wiring schematic label
for the module.
OW360_R1005 143
7.12.24 Sequence of Events Enhanced Compact Digital Input module (16

Channel)
The 16 channel Enhanced Sequence of Events Compact Digital Input module provides a low
cost interface for 16 field inputs. The module performs a digital de-bounce 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.
Note: Ovation I/O module power consumption figures are based on assumptions that the
Ovation power supply efficiency is 75%.
Enhanced Sequence of Events Compact Digital Input valid module combinations
RANGE CHANNELS ELECTRONIC PERSONALITY

MODULE MODULE OR
CAV ITY INS ERT
24/48 VDC Single-ended Digital Input - Current 16 5X00357G01 1C31238H011

Sinking
24/48 VDC Differential Digital Input - Current 16 5X00357G02 1C31238H011
Sinking
24/48 VDC (Individually Fused Channels with 16 5X00357G02 5X00034G01
Common power supply) Digital Input - Current (fused Pmod)
Sinking
24 VDC (Individually current limited Channels 16 5X00357G02 5X00765G01
with Common power supply) Digital Input - (current limited
Current Sinking Pmod2)
125 VDC Differential Digital Input - Current 16 5X00357G03 1C31238H011
Sinking
125 VDC (Individually Fused Channels with 16 5X00357G03 5X00034G01

Common power supply) Digital Input - Current
Sinking
48 VDC Single-ended Digital Input - Current 16 5X00357G04 1C31238H011
Sourcing (Contact input) with On-Card 48 VDC
power supply
24 VDC (Differential) Digital Input - Current 16 5X00357G05 1C31238H011
Sinking, IEC61131-2 Compliant Type 1 Digital
Inputs with Wire break detection
24 VDC (Individually Fused Channels with 16 5X00357G05 5X00034G01
Common power supply) Digital Input - Current (fused Pmod)
Sinking, IEC61131-2 Compliant Type 1 Digital
Inputs with wire break detection
24 VDC (Individually Current Channels with 16 5X00357G05 5X00765G01
Common power supply) Digital Input - Current (current limited
Sinking, IEC61131-2 Compliant Type 1 Digital Pmod2)
Inputs with wire break detection
1 This is a plastic insert that fits into the base unit’s Personality module cavity and provides a base unit
terminal block wiring label for the module.
144 OW360_R1005
7.12.25 Digital Input module 24 VDC (32 Channel)
The 32 Channel 24 VDC Digital Input module monitors the state ("0" or "1") of 32 single-ended
field digital inputs. The module is designed to meet IEC 61131-2 type 3 characteristics for 24 VDC
digital inputs in industrial automation.
Note: The 32 Channel 24 VDC Digital Input module requires the use of an Ovation 4-slot I/O
base (5X00497G01) that provides additional wire terminations to support the 32 channels. The
32 Channel 24 VDC Digital Input module cannot be used with the standard I/O Bases
(1B30035H01, 1X00014H01, or 5X00334G01).
32 Channel 24 VDC Digital Input Valid module combinations

MODULE MODULE
32 Channel 24 VDC Single-Ended Digital Input 32 5X00499G01 1X00690H01

7.12.26 Digital Output module (16 Channel)
The 16 channel Digital Output 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.
The G01 version of the Electronics module provides a single selection for the Timeout Action
(Reset or Latch) for all the channels on the module. With the G02 version, you can configure the
Timeout Action on a channel-by-channel basis.
16 Channel Digital Output valid module combinations 1
DESCRIPTION1 CHANNEL ELECTRONICS PERSONALITY

S MODULE OR PANEL MODULE
KIT
5-60 VDC Single-ended Direct 16 1C31122G01 1C31125G01
5-60 VDC with Relay Panel Interface, Local Power 16 1C31122G01 1C31125G02
Supply
5-60 VDC with Relay Panel Interface, Field Power 16 1C31122G01 1C31125G03
Supply
5-60 VDC Single-ended Direct w/ Ch STO 16 1C31122G02 1C31125G01
5-60 VDC w/ Ch STO and Relay Panel Interface, Local 16 1C31122G02 1C31125G02
Power Supply
5-60 VDC w/ Ch STO and Relay Panel Interface, Field 16 1C31122G02 1C31125G03
Power Supply
Relay Panels: Solid State Relay Panel (AC) 16 5A22410G01
Solid State Relay Panel (DC) 16 5A22410G02
OW360_R1005 145
DESCRIPTION1 CHANNEL ELECTRONICS PERSONALITY

S MODULE OR PANEL MODULE
KIT
G2R Relay Panel (Low Power Electro-mechanical) 16 5A22411G01
KU Relay Panel 2 (High Power Electro-mechanical) 16 5A22412G01 - G03
1 All configurations listed in the table are CE Mark certified, unless they use AC/DC solid state relay panels.
2 Two panels (8 relays each) are included in the KU Relay Panel kit 5A22412G01, G02, and G03.
Relay panels increase switching capabilities for digital output modules.
7.12.27 Digital Output module 24 VDC (32 Channel)
The 32 Channel 24 VDC 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 24 VDC Digital Output valid module combinations
DESCRIPTION CHANNELS ELECTRONICS PERSONALITY

MODULE OR PANEL MODULE
KIT
32 Channel 24 VDC High-Side, Single-Ended 32 5X00500G01 1X00691H01

Digital Output
Note: The 32 Channel 24 VDC Digital Output requires the use of an Ovation 4-slot I/O base
(5X00497G01) that provides additional wire terminations to support the 32 channels. The 32
Channel 24 VDC Digital Output cannot be used with the standard I/O Bases (1B30035H01,
1X00014H01, or 5X00334G01).
7.12.28 Digital Output High Side (24 VDC) module (16 Channel )
The High Side Digital Output (24 VDC) 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.
High Side Digital Output (24VDC) valid module combinations
RANGE CHANNELS ELECTRONICS MODULE PERSONALITY MODULE
24 VDC 16 5X00270G01 5X00273G01
146 OW360_R1005
7.12.29 Relay Output panel
An Ovation Relay Output module consists of an Electronics module (1C31219G01), 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 12 Relay Output Base assembly provides the
additional advantage of being able to switch larger DC voltages at high currents.
Each Relay Output Base assembly incorporates an integral Relay Output Electronics module to
interface between the relays and the Ovation I/O Controller. The Relay Output Electronics module
provides configurable communication timeout periods and LEDs to indicate the status of each
output.
The Relay Output module is a CE Mark certified module.
Relay Output panel valid module combinations
MODULE DESCRIPTION RELAY ELECTRONICS RELAY OUTPUT BASE

MODULE
Relay Output Module G2R 1C31219G01 1C31223G01

Relay Output Module KUEP 1C31219G01 1C31222G01
Relay Output Module w/ Ch STO G2R 1C31219G02 1C31223G01
Relay Output Module w/ Ch STO 1C31219G02 1C31222G01

KUEP
OW360_R1005 147
7.12.30 Relay Output panel with Contact Monitoring module
The Relay Output with Contact Monitoring module consists of an Electronics module
(1C31219G01), a base assembly, and relays. The Relay Output module provides a means to
switch high AC voltages at high currents to field devices. It provides a single FORM X relay
contact to drive the field devices. In addition, the module has two monitoring circuits per channel,
which provide a feedback to the standard Ovation Contact Input module or Digital Input Module to
indicate the contact state of the relay.
The Relay Output base assembly does not incorporate a Personality module. For more
information about module configuration, refer to the following topics: Electronics modules (Emod)
- (ROCM) and Base assemblies - (ROCM) in the Ovation I/O Reference manual.
Each Relay Output with Contact Monitoring base assembly incorporates an integral Relay Output
Electronics module to interface between the relays and the Ovation I/O Controller. The Relay
Output Electronics module provides configurable communication timeout periods and LEDs to
indicate the status of each output.
The Relay Output with Contact Monitoring contains shorting jumpers to enable or disable both
contact monitoring circuits on a per channel basis. The Relay Output with Contact Monitoring
contains the field terminal headers, which accept pluggable terminal blocks in either right angle
screw compression or vertical crimp pin styles. In addition, the Relay Output with Contact
Monitoring Base contains the contact monitoring terminal headers, which accept pluggable
terminal blocks. The pluggable terminal blocks contain a screw hold down to the terminal header
for mechanical stability.
Relay Output panel with Contact Monitoring valid module combinations
MODULE DESCRIPTION RELAY ELECTRONICS RELAY OUTPUT

MODULE BASE
Relay Output with Contact Monitoring 1C31219G01 5X00564G01

Assembly, KUEP Form X, Marshalling (No
terminal blocks installed).
Relay Output with Contact Monitoring 1C31219G01 5X00564G02
Assembly, KUEP Form X, Field Termination
(Terminal blocks installed).
Relay Output with Contact Monitoring Assembly 1C31219G02 5X00564G01
and Ch STO, KUEP Form X, Marshalling (No
terminal blocks installed).
Relay Output with Contact Monitoring Assembly 1C31219G02 5X00564G02
and Ch STO, KUEP Form X, Field Termination
(Terminal blocks installed).
148 OW360_R1005
7.12.31 Relay Output panel (32 Channel)
The Ovation 32 Channel Non-Fused and Fused Relay Output assemblies provide a means to
switch high current and voltage devices located in the field. The 32 relays are SLIM-line style
which are utilized within the control and PLC markets for resistive loads and light inductive loads
such as interposing relay coils and auxiliary contacts on external controllers.
The Ovation 32 Channel Relay Base Subsystem consists of a 32 Channel Non-Fused Relay Base
assembly or 32 Channel Fused Relay Base assembly, a 32 Channel Relay Output Electronics
module, and 32 - 1 FORM C SLIM-line style medium power electromechanical relays for
switching field devices.
The 32 Channel Relay Output Electronics module consists of 32 relay channel driver circuits,
employing the use of the standard main Ovation +24V power supply. The 32 Channel Relay
Output Electronics module provides 32 output relay output driver circuits that interface with the
SLIM line relays located on the Ovation 32 Channel Non-Fused Relay Base assembly and the 32
Channel Fused Relay Base assembly.
The 32 Channel Non-Fused Relay Base assembly is capable of driving 5A, 250 VAC resistive
loads (PF=1). The 32 Channel Fused Relay Base assembly is capable of driving 3.15A, 250 VAC
resistive loads (PF=1) which is fuse limited with an integral 3.15A Type T fuse. The relays are
also capable of driving small inductive loads such as interposing relay coils at AC 15 load type.
Relay Output panel (32 Channel) valid module combinations
MODULE DESCRIPTION RELAY ELECTRONICS RELAY OUTPUT

MODULE BASE
32 Channel Relay Output Electronics Module with 5X00583G01 5X00623G01

the 32 Channel Fused Relay Base assembly which
accommodates 32 low power relays.
G01 = SLIM Line Relays installed. 5X00623G02
G02 = No SLIM Line Relays installed.

32 Channel Relay Output Electronics Module with 5X00583G01 5X00584G01
the 32 Channel Non-Fused Power Relay Base
assembly which accommodates 32 low power
relays. 5X00584G02
G01 Base = SLIM Line Relays installed.
G02 Base = No SLIM Line Relays installed.
OW360_R1005 149
7.12.32 Relay Output (Fused) panel
The 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 Electronics module
(1C31219G01) provides an interface between the Ovation Controller and the mechanical relays.
The Fused Relay Output base assembly does not incorporate a Personality module. For more
information about module configuration, refer to the following topics: Electronics modules (Emod)
- FRO and Base assemblies - (FRO) in the Ovation I/O Reference manual.
Fused Relay Output panel valid module combinations 1
DESCRIPTION RELAYS RELAY RELAY OUTPUT

ELECTRONICS BASE 1
MODULE
Relay Output Assembly G2R Fused, Marshalling 16 1C31219G01 5X00431G01

Relay Output Assembly G2R Fused, Customer 16 1C31219G01 5X00431G02
Termination
Relay Output Assembly KUEP Form C, Fused, 12 1C31219G01 5X00430G01
Marshalling
Relay Output Assembly KUEP Form X, Fused, 12 1C31219G01 5X00430G02
Marshalling
Relay Output Assembly KUEP Form C, Fused, 12 1C31219G01 5X00430G03
Customer Termination
Relay Output Assembly KUEP Form X, Fused, 12 1C31219G01 5X00430G04
Customer Termination
Relay Output Assembly with Ch STO G2R 16 1C31219G02 5X00431G01
Fused, Marshalling
Relay Output Assembly with Ch STO G2R 16 1C31219G02 5X00431G02
Fused, Customer Termination
Relay Output Assembly with Ch STO KUEP 12 1C31219G02 5X00430G01
Form C, Fused, Marshalling
Form X, Fused, Marshalling
Form C, Fused, Customer Termination
Form X, Fused, Customer Termination
1 Relay Outputs do not use standard Ovation I/O bases. Use the listed base units for Relay Output
applications. Also note that the Relay Output module does not use a Personality module.
150 OW360_R1005
7.12.33 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 valid module combinations
2 (non-redundant) 5X00301G01 1C31238H01 (cavity insert)

2 (redundant) 5X00301G01 5X00327G01
7.12.34 Profibus DP 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. The
Profibus module provides an interface to Profibus devices through an Ovation I/O bus.
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 valid module combinations
2 5X00300G01 or 5X00300G02 5X00321G01
7.12.35 DeviceNet module
The Ovation DeviceNet module provides an interface with one or two DeviceNet networks
through an Ovation I/O bus. 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 valid module combinations
2 5X00376G01 5X00375G01
OW360_R1005 151
7.12.36 Ethernet Link Controller (ELC) module
The Ethernet Link Controller module provides an interface with a single Ethernet link. This
module uses a straight RJ45 connector that allows the port to be accessed outside of the
Electronics module.
Ethernet Link Controller valid module combinations
2 5X00419G01 1X00569H01
7.12.37 Link Controller module
The Link Controller 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 the Ovation Algorithms Reference Manual for more information.
Link Controller valid module combinations1

MODULE MODULE
RS232 One (1) Serial Port (Able to handle 1C31166G012 1C31169G01

many points) or
1C31166G02
RS485/RS422 Four One (1) Serial Port (Able to handle 1C31166G012 1C31169G02
wire many points) or
1C31166G02
1 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. (Refer to the
Ovation Algorithm Reference Manual.)
152 OW360_R1005
7.12.38 Loop Interface module
The Ovation single-loop Controller is designed to interface to the analog and digital I/O necessary
to control a single process loop. In addition, the Ovation single-loop Controller displays this
process information and provides for manual control via a local operator interface station.
The Ovation single-loop interface module provides the following field inputs and outputs
necessary to interface to a single loop:
 Two galvanically isolated analog inputs.
 One analog output.
 Two galvanically isolated digital inputs.
 Two digital outputs (the outputs share a common ground with each other, but are galvanically
isolated from the other I/O circuits and from the logic portion of the module).
In addition, the single-loop interface module contains an RS422 serial port for communications
with a loop interface module (SLIM) and an interface for communications over the Ovation serial
I/O bus.
The Loop Interface module is a CE Mark certified module.
Loop Interface valid module combinations1, 4

MODULE MODULE
Normal (Non-electric) Drive modules

0-10V Analog Inputs/Output 6 1C31174G01 1C31177G01
0-10V AI/AO - user defined Digital Inputs2 6 1C31174G21 1C31177G01
0-5V Analog Inputs, 0-10V Analog Output 6 1C31174G02 1C31177G01

0-5V AI, 0-10V AO - user defined Digital Inputs2 6 1C31174G22 1C31177G01
4-20mA AI/AO Locally powered analog inputs 6 1C31174G03 1C31177G02

4-20mA AI/AO Field powered analog inputs 6 1C31174G03 1C31177G03
4-20mA AI/AO - user defined Digital Inputs2 6 1C31174G23 1C31177G02
Locally powered analog inputs
6 1C31174G23 1C31177G03
4-20mA AI/AO - user defined Digital Inputs2
Field powered analog inputs
4-20mA Locally Powered Electric Beck Drive 6 1C31174G04 1C31177G02
4-20mA Field Powered Electric Beck Drive 6 1C31174G04 1C31177G03
6 1C31174G24 1C31177G02
4-20mA Locally Powered Electric Beck Drive 6 1C31174G24 1C31177G03
4-20mA Field Powered Electric Beck Drive
OW360_R1005 153

MODULE MODULE
When defining points for a normal (non-electric) drive Loop Interface module, the following point types are
required for each channel:
I/O NAM E TYPE INPUT SOURCE OR TERMINAL BLOCK

CHANNEL OUTPUT DESTINATION CONNECTION
1 Priority Raise or user-defined 2 Input Loop Interface module DI1
2 Priority Lower or user-defined 2 Input Loop Interface module DI2
3 User Defined Output Loop Interface module DO1

4 User Defined Output Loop Interface module DO2
5 Process Variable Input Input Loop Interface module AI1
(dedicated)
6 Set point Input (optional) Input Loop Interface module AI2
None Output Output Loop Interface module AI33
Two additional channels are used at Emod Revision 5 or higher:
7 Controller Process Variable Output Analog No Terminations
8 Controller Set Point Output Analog No Terminations
Electric Drive modules
4-20mA Inputs; No Output Locally powered 4 1C31174G04 1C31177G02

analog inputs 1C31177G03
4-20mA Inputs; No Output Field powered 4 1C31174G04 1C31177G02
analog inputs
4-20mA Inputs; No Output - user defined Digital 4 1C31174G24 1C31177G03
Inputs2 Locally powered analog inputs
4-20mA Inputs; No Output - user defined Digital 4 1C31174G24
Inputs2 Field powered analog inputs
154 OW360_R1005

MODULE MODULE
When defining points for an electric drive Loop Interface module, the following point types are required for
each channel:
I/O NAM E TYPE INPUT SOURCE OR TERMINAL BLOCK

CHANNEL OUTPUT DESTINATION CONNECTION
1 Priority Raise or user-defined Input Loop Interface module DI1

2
2 Priority Lower or user-defined Input Loop Interface module DI2

2
None Output Raise Pulse Output Loop Interface module DO13

(dedicated)
None Output Lower Pulse Output Loop Interface module DO23
(dedicated)
5 Process Variable Input Input Loop Interface module AI1
(dedicated)
6 Process Position (dedicated) Input Loop Interface module AI2
None Output Output Output is compared to No Terminations
Process Position.
Raise/Lower pulses
(DO1, DO2) are
generated as applicable.
Two additional channels are used at Emod Revision 5 or higher:
7 Controller Process Variable Output Analog No Terminations
8 Controller Set Point Output Analog No Terminations
1 This module controls ONE process loop. To use this module, the MASTATION algorithm must reside in the
Ovation Controller. (Refer to Ovation Algorithm Reference Manual.)
2 Priority Raise and Lower 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.
OW360_R1005 155
7.12.39 Pulse Accumulator module
The Pulse Accumulator 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.
(Refer to Ovation Algorithm Reference Manual.)
Pulse Accumulator valid module combinations
COUNT INPUT LEVEL CONTROL (ENABLE AND CHANNELS ELECTRONIC PERSONALITY

SNAPSHOT) INPUT LEVEL MODULE MODULE
24/48 V Medium Speed 24/48 V Medium Speed

Local field pwr. neg. cmn. Local field pwr. neg. cmn. 2 1C31147G01 1C31150G01
Local field pwr. pos. cmn. Local field pwr. pos. cmn. 2 1C31147G01 1C31150G02
Ext. field pwr. pos. or Ext. field pwr. pos. or neg. 2 1C31147G01 1C31150G03
neg. cmn. cmn.
5/12 V Medium Speed 24/48 V Medium Speed

Local field pwr. neg. cmn. 2 1C31147G01 1C31150G01
Local field pwr. pos. cmn. 2 1C31147G01 1C31150G02
Ext. field pwr. pos. or neg. 2 1C31147G01 1C31150G03
cmn.
The ranges listed above have the following specifications:
 Main +24 Power (W) and VA (Typical):

 Draws from AC/DC Power Mains = 2.2 W/VA
 Draws from AC/DC Power Supply = 1.6 W
 AUX Power (W) and VA (Typical)
 Both count inputs = 50% duty cycle.
0.23 W/VA (24V)
0.47 W/VA (48V)
 Main heat dissipation = 7.51 BTU/h
 AUX heat dissipation
 Both count inputs = 50% duty cycle.
0.78 W/VA (24V)
1.6 W/VA (48V)
5 V High Speed 24/48 V Medium Speed
Local field pwr. neg. cmn. 2 1C31147G02 1C31150G01
Local field pwr. pos. cmn. 2 1C31147G02 1C31150G02
Ext. field pwr. pos. or neg. 2 1C31147G02 1C31150G03
common
156 OW360_R1005
COUNT INPUT LEVEL CONTROL (ENABLE AND CHANNELS ELECTRONIC PERSONALITY

SNAPSHOT) INPUT LEVEL MODULE MODULE
 Main +24 Power (W) and VA (Typical) = 2.2 W/VA

 AUX Power (W) and VA (Typical) = Not applicable
 AUX heat dissipation
 Both high speed count inputs = 50% duty cycle.
0.68 BTU/h
7.12.40 Servo Driver (RSR) module
The Servo Driver module provides an interface to an electro-hydraulic servo actuator (servo-
motor) used to control a steam turbine.
Servo Driver valid module combinations

MODULE MODULE
±16 Volts DC to a DC LVDT 6 1C31199G01 1C31201G01

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
19 Volts AC peak-to-peak 1 KHz to an AC LVT 6 1C31199G02 1C31201G02
8 mA into two 1000 ohm coils
±16 Volts DC to a DC LVDT (I/O Bus Firmware 6 1C31199G04 1C31201G01
updates)
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
(I/O Bus Firmware updates)
OW360_R1005 157

MODULE MODULE
The following point types are valid for each channel:

I/O Name Type Input Source or Terminal Block
Channel Output Destination Connection2
1 Position Feedback (Device 1) Input Servo Driver N/A
2 Position Feedback (Device 2) Input Servo Driver N/A
3 Raw Demodulator Voltage (Device 1) Input Servo Driver N/A
4 Raw Demodulator Voltage (Device 2) Input Servo Driver N/A
5 Demand (Device 1) Output N/A N/A
6 Demand (Device 2) Output N/A N/A
1 This module interfaces to, and provides position control for two Electro-Hydraulic (EH) actuators in the field.
2 The terminal block connection depends upon the application being used. Refer to the appropriate wiring
diagrams.
7.12.41 Speed Detector module
The Speed Detector module provides the Controller with frequency measurements of a
sinusoidal or pulse train input signal. A 16-bit output is updated at a rate of 5 ms for over-speed
detection (G01 only), and a 32-bit output is updated at a variable rate for speed regulation (G01
and G03). A 16-bit acceleration output is updated at the same rate as the 32-bit speed output
(G03 only).
This module interfaces to one speed sensor to determine the rotational speed of a field device.
Speed Detector subsystems (G01)

MODULE MODULE
16 bit speed (Low Resolution) 1 1C31189G01 1C31192G01

200 Hz Min - 51200 Hz Max
32 bit speed (High Resolution) 1 1C31189G01 1C31192G01

0.72 Hz Min - 65535 Hz Max
 Main +24 Power (W) and VA (Typical):

 Draws from AC/DC Power Mains = 6.4 W/VA
 Draws from AC/DC Power Supply = 4.8 W
When using the Point Builder to define points for a Speed Detector module, only the following point types are
valid for each channel:
158 OW360_R1005

MODULE MODULE
I/O Channel Name Type Terminal Block

Connection
1* 32 bit Speed value Analog Input B15, B16
(can select I/O 1 or 3)
3* 16 bit Speed value Analog Input B15, B16
(can select I/O 1 or 3)
5 Open Wire Digital Input N/A
11 Overspeed Digital Input N/A
12 Latched Overspeed Digital Input N/A
13 Trip Relay Status Digital Input N/A
2* Reset Calculations Digital Output N/A
1* Trip Relay Digital Output A6, A7, B6
A11, A12, B11
* Note: When the Open Wire Detection option is selected, points assigned to the (*) channels will have Bad
Quality when an Open Wire condition is detected.
All module configurations listed in the table are CE Mark Certified.

This module interfaces to ONE speed sensor to determine the rotation speed of a field device.
Ch. 11--This channel is the instantaneous status of the overspeed calculation. If the bit is true ( =1
), the most recent overspeed calculation result is that the machine is in an overspeed condition.
This bit comes from bit 10 in the module status record and clears ( = 0 ) as soon as the overspeed
condition disappears.
Ch. 12--This channel is a latched version of Ch. 11 and is located at bit 11 of the status register.
Once set true, the bit remains true until the Ovation Controller reads the status register. When the
Ovation Controller reads the status register, this bit will be cleared if there is no overspeed
condition.
Ch. 13--This channel reports the instantaneous status of the relay coil drive circuit. This bit is
located in the module status register at bit 12. If the bit is true ( =1 ), the relay coil is driven to
actuate the output relay.
Note: The Ovation Controller reads the status register and clears bit 11 both for scanning the
module record, and for I/O scanning if any of I/O channels 11, 12, or 13 are defined.
If channel 11 is used on a control sheet, then the logic must accommodate the possibility that
the I/O scan will miss the overspeed condition in a case where the condition is coming in and
out quickly, and is cleared when the module record is scanned.
OW360_R1005 159
Valid Speed Detector module combinations for (G03 and G04)

MODULE
16-bit acceleration 1 1C31189G03 1C31192G01

+/-32767 RPM/min
32-bit speed (High Resolution)
0.1 Hz Min - 30000 Hz Max
16-bit acceleration 1 1C31189G04 1C31192G01
+/-32767 RPM/min
32-bit speed (High Resolution)
0.1 Hz Min - 30000 Hz Max
The following point types are valid for each channel:
I/O Channel Name Type Terminal Block

Connection
1* 32-bit Speed value Analog Input B15, B16
4* 16-bit Acceleration value Analog Input B15, B16
5 Open Wire Digital Input N/A
11 Overspeed Digital Input N/A
12 Overspeed Latched Digital Input N/A
13 Relay Activated Digital Input N/A
6* SpeedLimit or 0 - 65535 rpm Analog Output N/A
5* AccellLimit or Analog Output N/A
(Acell+Speed Limit +/- 32767)
3* SimulateSpeed Digital Output N/A
4* AckRelay Digital Output N/A
1* Trip Relay Digital Output A6, A7, B6
0 = (normal) A11, A12, B11
1 = (trip)
For the G03 module
0 = not activated (normal)
1 = activated (trip)
For the G04 module
0 = not deactivated (normal)
1 = deactivated (trip)
* Note: When the Open Wire Detection option is selected, Points assigned to the (*) channels will have Bad
Quality when an Open Wire condition is detected.
1C31189G03 modules are applicable to Ovation 3.3.1 and later Ovation software releases.
Module configurations listed are non-CE Mark certified.

This module interfaces to ONE speed sensor to determine the rotation speed of a field device.
160 OW360_R1005
Ch. 11 - This channel is the instantaneous status of the overspeed calculation. If the bit is true (
=1 ), the most recent overspeed calculation result is that the machine is in an overspeed
condition. This includes both the overspeed calculation, or the over-acceleration or over-
speed+acceleration calculation. This bit comes from bit 10 in the module status record and clears
( = 0 ) as soon as the overspeed condition disappears. The overspeed condition is reflected by
the overspeed LED as well.
Ch. 12 - This channel is a latched version of Ch. 11 and is located at bit 11 of the status register.
Bit 11 is latched in hardware until the overLimit condition disappears and the Ovation Controller
reads the bit.
Ch. 13 - This channel reports the status of the relay coil drive circuit. This bit is located in the
module status register at bit 12. If the bit is true ( = 1 ), the relay coil is driven to actuate the G03
output relay. Relay activation from overspeed conditions are latched in firmware and are not
released until the Ovation Controller acknowledges the condition by pulsing channel 4, as
described above. The relay can also be activated by the Ovation Controller. (G03 = activated;
G04 = deactivated)
Note: If the Controller is updating the speed limit I/O point, the configured limit is ignored.
The acceleration limit I/O can be positive or negative. Positive values indicate the customer
preference for relay action on high acceleration, whereas negative values are for high
amplitudes of deceleration.
(Positive acceleration will not cause relay action if the limit is negative.)
OW360_R1005 161
7.12.42 Valve Positioner module
The Ovation Valve Positioner I/O module provides an interface between an Ovation Controller
and an electro-hydraulic servo valve actuator. Two modules, the electronics module and the
personality module, form the Ovation Valve Positioner I/O module assembly.
A valve position setpoint is maintained by the Ovation Valve Positioner electronics module. The
setpoint is normally altered by the Ovation Controller through the Ovation I/O bus.
The valve position setpoint causes the Valve Positioner module to generate redundant output
control signals which drive the electro-hydraulic servo valve actuator coils. The feedback loop is
closed with the valve’s position measurement being obtained from an LVDT that is mounted on
the valve stem.
The Ovation Triplex Valve Positioner module has a redundancy capability allowing three Valve
Positioner modules to monitor and control valve position.
The main function of the Triplex Valve Positioner is to have the ability to control a valve that has
three LVDT sensors. The linear valve positions reported by these sensors are checked for
consistency by the Ovation Controller. The Triplex configuration may also be referred to as a triple
redundancy configuration. The triple redundant aspect refers particularly to the valve position
measurement to avoid LVDT failures.
Current Ovation Valve Positioner modules are built on the ARM9 micro-controller platform and are
available in the following groups.
 1C31194G01 17 VAC p-p 1 kHz LVDT primary winding excitation output. ±10.24 VDC servo
valve actuator coil drive output voltage.
valve actuator coil drive output voltage. Triplex module configuration. Must be used for triple
redundant configurations.
Note: G03 and G04 Valve Positioner modules offer added functionality and are recommended
for Ovation 3.5 and later software releases.
G05 Triplex Valve Positioner modules must be used for triple redundancy configurations and are
available for Ovation 3.6 and later software releases.
Currently, a total of seven Valve Positioner Electronics modules are supported by Emerson and
can be paired with any Valve Positioner Personality module.
162 OW360_R1005
Valve Positioner Electronics modules
EMOD NUMBER VERSION MICRO-CONTROLLER USED AS

PLATFORM
1C31194G01 and First generation. 80C196 Spares or repaired modules

1C31194G02 on Ovation pre-3.5 systems.
(Module parts are

obsolete.)
1C31194G01 and Second generation. ARM9 Direct replacement module

1C31194G02 for Ovation pre-3.5 systems.
1C31194G03 and Second generation. ARM9 Used exclusively on Ovation
1C31194G04 3.5 and later systems.
1C31194G05 Second generation. ARM9 Used exclusively on Ovation
3.6 and later systems. Must
be used for triple redundant
configurations.
All Valve Positioner Personality modules (1C31197G01 - G05) are compatible with the electronics
modules. Any 1C31194 Emod can operate in combination with any 1C31197 Pmod.
Refer to the Valve Positioner User Guide for additional information on the Ovation Valve
Positioner I/O module.
7.12.43 Small Loop Interface module (SLIM)
The Small Loop Interface module (SLIM) 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.
7.12.44 Numalogic Fast Ethernet Remote Node
The Numalogic Fast Ethernet Remote Node (NFE-RN) module is a remote I/O subsystem that
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
PART NUMBER
Numalogic Remote I/O Kit 5X00512

Numalogic Fast Ethernet Remote I/O Electronics module 5X00467
Numalogic Fast Ethernet Remote I/O Base Assembly 5X00468
PWSN 8V Power Supply 5X00522
OW360_R1005 163
7.12.45 Machinery Health Monitor module
The Ovation Machinery Health Monitor module (MHM) is used to monitor vibrations of your plant's
rotating apparatus. The Machinery Health Monitor is a multichannel analog input module. The
module monitors the vibration produced by plant equipment, acquires high resolution vibration
waveform data, calculates values of various parameters, and sends these scalar values to the
Ovation Controller for processing.
Using the data obtained by the module, you can determine the condition of the monitored plant
equipment. This data is useful when making decisions on when to perform maintenance or how to
prevent future problems from occurring.
The overall goal of the MHM module is to monitor your rotating equipment and gather information
to help you determine the condition of monitored plant equipment, then use the data as a
prediction method for planning machinery maintenance and to protect the future health of your
plant equipment.
The MHM module (Emod 5X00717) consists of one Logic card and two Field cards housed within
an Ovation wide-bodied Emod enclosure.
 The logic card is a Freescale P1010 microprocessor based assembly with interfaces to the
Ovation backplane I/O and the field cards.
 Two field cards (Field Card A and Field Card B) supply sensor power and signal conditioning
to external sensors.
A Personality module is not required for the MHM.
Refer to the Machinery Health Monitor User Guide for additional information on the Ovation
Machinery Health Monitor module.
164 OW360_R1005
7.12.46 Digital Excitation Controller (DEC) module
The Digital Excitation Controller module is a high-speed I/O module that is part of a fully
redundant Ovation Excitation solution. The module offers precise excitation control for a broad
range of synchronous generators. It monitors the condition of the generator and detects abnormal
conditions. It can then take the appropriate actions to protect the generator including limiters,
forcing manual operation and tripping the generator lockout.
The benefits of using the Digital Excitation Controller module include:

 Improves operator efficiency.
 Enables better decision making.
 Increases reliability.
 Streamlines lifecycle management.
 Supports the ability to comply with new NERC requirements.
Your system requires a minimum of Ovation 3.6.0 software or later with the appropriate patches
to operate the Digital Excitation Controller module. In addition, a Group 3 or later IOIC module is
required when using the Digital Excitation Controller module.
Note: Ovation 3.5.1 systems can also use the Digital Excitation Controller module but will
require the appropriate software patches.
The 5X00658 Digital Excitation Controller module consists of one logic card and two field cards
housed within an Ovation wide-bodied Emod housing. There are two groups of the Digital
Excitation Controller module:
 5X00658G01 – +/- 10V Analog Output
 5X00658G02 – 4–20mA Analog Output
Refer to the Digital Excitation Controller User Guide for additional information on the Ovation
Digital Excitation Controller module.
OW360_R1005 165
7.13 Guidelines for replacing, adding, or combining Ovation modules
7.13 Guidelines for replacing, adding, or combining Ovation modules
Observe the following guidelines when replacing or adding modules:

 Ensure 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.
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
166 OW360_R1005
7.14 Installing Ovation standard I/O modules
Figure 33: Examples of Standard I/O and Relay 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 125 VAC/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.
OW360_R1005 167
7.14.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, ensure 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 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. Install the new Electronics module next to the Personality module.
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.
168 OW360_R1005
7.15 Installing Ovation Relay Output modules
7.14.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.
3. Install the Electronics module next to the Personality module.
4. Use the blue corner latches on the Electronics module to secure both modules into the Base
Unit.
5. 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.15 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.15.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).
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.
OW360_R1005 169
7.15 Installing Ovation Relay Output modules
7.15.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 the Relay Output Base unit onto the 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.
170 OW360_R1005
S E C T I O N 8
8 Planning Ovation cabinets for your Ovation system
IN THIS SECTION
What are Ovation cabinets? ............................................................................................ 172

Cabinet configuration guidelines ..................................................................................... 173
Ovation cabinet components ........................................................................................... 174
How many I/O modules can an OCR400 or an OCR1100 Controller support? .............. 175
Ovation Controller cabinet ............................................................................................... 175
Ovation Marshalling cabinet ............................................................................................ 179
Ovation extended I/O cabinet .......................................................................................... 183
Remote Node cabinet ..................................................................................................... 186
Examples of cable access areas and floor bolting in Ovation cabinets
(Hoffman cabinets) .......................................................................................................... 192
Examples of cable access areas and floor bolting in Ovation cabinets (Rittal cabinets) 197
Examples of available usage area for field wiring ........................................................... 200
Weights of Ovation cabinets ........................................................................................... 202
Floor plan recommendations ........................................................................................... 203
Cleaning and maintenance guidelines for Ovation Controller cabinets .......................... 204
OCR400 Controller and OCR1100 Controller Modules .................................................. 205
User-supplied cabinets .................................................................................................... 206
OW360_R1005 171
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 175).
 Marshalling cabinets (see page 179).
 Extended cabinets (see page 183).
 Remote Node cabinets (see page 186).
 Relay Panel cabinets (see page 191).
 Workstation cabinets.
 Server cabinets.
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).
 800 mm (32 in).
 900 mm (36 in).
You can select the cabinet width that is best for your system needs.
172 OW360_R1005
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.
OW360_R1005 173
8.3 Ovation cabinet components
Figure 34: Examples of Standard I/O and Relay Modules
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 Controllers.
 Ovation modules:
 Standard modules.
 Relay Output modules.
 Remote Function modules.
 Wiring and cabling.
 Terminator assemblies.
 ROP Transition panels.
 Remote Node Transition panels.
 RRP Top Transition panels.
 RRB Bottom Transition panels.
174 OW360_R1005
8.4 How many I/O modules can an OCR400 or an OCR1100 Controller support?
8.4 How many I/O modules can an OCR400 or an OCR1100 Controller

support?
The Ovation OCR400 or the OCR1100 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 or one OCR1100 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 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.
 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.
OW360_R1005 175
8.5.1 Controller cabinet configuration for local Ovation I/O
OCR400 and OCR1100 Controllers
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.
8.5.2 Controller cabinet configuration for remote Ovation I/O
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.
8.5.3 Controller cabinet configuration for mixed (local and remote) Ovation I/O
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).
The standard Controller cabinet contains four branches. If additional local I/O modules are
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.
8.5.4 Controller cabinet configuration for local Q-Line I/O
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 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.
176 OW360_R1005
8.5.5 Controller cabinet configuration for remote Q-Line I/O
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.)
OW360_R1005 177
8.5.6 Illustrations of Controller cabinet configurations
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.
178 OW360_R1005
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.
OW360_R1005 179
8.6 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.
 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.
8.6.1 Marshalling cabinet configuration illustrations
Figure 35: Ovation Marshalling Cabinet Configuration (illustrating DIN-rails)
Note: Measurements are for the mounting plate, and do not include cabinet doors or
180 OW360_R1005
Figure 36: Ovation Marshaling Cabinet Configuration (illustrating Standard I/O modules)
The zones (1 - 8) are used to define bus address locations.
OW360_R1005 181
Figure 37: Ovation Marshalling Cabinet Configuration (illustrating Relay Output modules)
The zones (1 - 8) are used to define bus address locations.
182 OW360_R1005
8.7 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.
OW360_R1005 183
8.7.1 Extended cabinet configuration illustrations
Figure 38: Ovation Extended Cabinet Configuration (illustrating Standard I/O Modules)
184 OW360_R1005
Figure 39: Ovation Marshaling Cabinet Configuration (illustrating Standard I/O modules)
OW360_R1005 185
8.8 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.
186 OW360_R1005
8.8.1 Remote Node cabinet configuration illustrations
The following figures illustrate Remote Node cabinet configurations:
Figure 40: Remote cabinet configuration
OW360_R1005 187
Figure 41: Ovation Remote Node Cabinet Configuration (illustrating DIN-rails)
188 OW360_R1005
Figure 42: Ovation Remote Node Cabinet (illustrating Standard I/O modules)
OW360_R1005 189
Figure 43: Ovation Remote Node Cabinet (illustrating Relay Output modules)
190 OW360_R1005
8.8.2 Relay Panel cabinet configuration illustrations
The following figure illustrates a typical Relay Panel cabinet configuration:
Figure 44: Ovation Relay Panel Cabinet Configuration (illustrating DIN-rails)
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).
OW360_R1005 191
8.9 Examples of cable access areas and floor bolting in Ovation cabinets (Hoffman cabinets)
8.9 Examples of cable access areas and floor bolting in Ovation

cabinets (Hoffman cabinets)
The following figures show the cable access area for the five sizes of Hoffman 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.
Figure 45: Bottom inside view of 78 x 24 x 16 inch cabinet (illustrating cable access)
192 OW360_R1005
Figure 46: Bottom inside view of 78 x 24 x 20 inch cabinet (illustrating cable access)
OW360_R1005 193
Figure 47: Bottom inside view of 78 x 24 x 24 inch Cabinet (illustrating cable access and
floor bolting)
194 OW360_R1005
floor bolting)
OW360_R1005 195
floor bolting)
196 OW360_R1005
8.10 Examples of cable access areas and floor bolting in Ovation cabinets (Rittal cabinets)
8.10 Examples of cable access areas and floor bolting in Ovation

cabinets (Rittal cabinets)
The following figures show the cable access area for the five sizes of Rittal 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:

floor bolting)
OW360_R1005 197
floor bolting)
floor bolting)
198 OW360_R1005
floor bolting)
floor bolting)
OW360_R1005 199
8.11 Examples of available usage area for field wiring
8.11 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.
Figure 55: Top view of Controller cabinet - available usage area for field wiring
200 OW360_R1005
8.11 Examples of available usage area for field wiring
Figure 56: Top view of I/O extended cabinet - available usage area for field wiring
Figure 57: Top view of remote I/O node cabinet - available usage area for field wiring
OW360_R1005 201
8.12 Weights of Ovation cabinets
8.12 Weights of Ovation cabinets

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
CABINE T TYPE WEIGHT 1 DIMENSIONS (H X W X D)
Ovation Workstation Cabinet: 183 kg 2083x601x890 mm

Vented
(403 lb) (82x24x35 in)
1X00518
Ovation Server Cabinet Vented 161 kg 2083x601x890 mm
1X00545 (354 lb) (82x24x35 in)
Static load rating of 680 kg
(1500 lb)
OCR400 Controller 211.71 kg 2000 x 600 x 600 mm
5X00293 (466.75 lb) (78 x 24 x 24 in)
CE Mark Certified
Extended I/O 208.14 kg 2000 x 600 x 600 mm
CE Mark Certified (458.86 lb) (78 x 24 x 24 in)
Remote I/O 209.48 kg 2000 x 600 x 600 mm
Sealed (461.83 lb) (78 x 24 x 24 in)
CE Mark Certified
Remote I/O 209.48 kg 2000 x 600 x 600 mm
Ventilated (461.83 lb) (78 x 24 x 24 in)
CE Mark Certified
(437.75 lb) (78 x 24 x 24 in)
Marshalling 283.6 kg 2000 x 800 x 600 mm
(624 lb) (78 x 32 x 24 in)
Marshalling 301 kg 2000 x 914 x 600 mm
(664 lb)
(78 x 36 x 24 in)
(393.86 lb) (78 x 24 x 24 in)
Remote I/O 180.0 kg 2000 x 600 x 600 mm
Sealed (396.83 lb) (78 x 24 x 24 in)
Remote I/O 180.0 kg 2000 x 600 x 600 mm
1 Assumes Controller cabinet is populated with 16 I/O base assemblies (32 Electronic modules and 32
Personality modules).
202 OW360_R1005
8.13 Floor plan recommendations
8.13 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 58: Recommended cabinet floor plan
OW360_R1005 203
8.14 Cleaning and maintenance guidelines for Ovation Controller cabinets
8.14 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
5A26371H03.
CAUTION! Only qualified service personnel should check and replace filters.
 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.
204 OW360_R1005
8.15 OCR400 Controller and OCR1100 Controller Modules
8.15 OCR400 Controller and OCR1100 Controller Modules
The OCR400 or OCR1100 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 59: OCR400 Controller and OCR1100 Controller modules
Note: The OCR400 and OCR1100 Controllers do not require a fan assembly.
OW360_R1005 205
8.16 User-supplied cabinets
8.15.1 To replace 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.

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.
8.16 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.
206 OW360_R1005
S E C T I O N 9
9 Planning power for your Ovation cabinets
IN THIS SECTION
How is power distributed in an Ovation system? ............................................................ 207

Connecting the power mains to an Ovation cabinet ....................................................... 214
Power supply front view .................................................................................................. 216
Power supply wiring illustration ....................................................................................... 218
Power supply wiring connections .................................................................................... 219
Functional diagram .......................................................................................................... 220
Power supply locking mechanism ................................................................................... 221
Power supply specifications ............................................................................................ 221
Power supply replacement cautions ............................................................................... 223
Using power supply modules .......................................................................................... 224
Power supply requirements (drawn from +24V main or auxiliary power supply) ............ 229
Monitoring power supply status ....................................................................................... 244
What is an external supply? ............................................................................................ 246
Power distribution scheme .............................................................................................. 251
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 = 10 AWG (4 mm2)) are
connected to the AC input DIN rail.
 There is a single wiring harness from the input DIN rail components (mains power) to each
power supply.
 There is a single wiring harness between the PDM and each power supply. This harness
routes DC power (main and auxiliary) 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:
 Remote node transition panel (TND) (see page 212).
 Single branch I/O transition panels (RRP, and RRB).
 Dual branch I/O transition panels (ROP) (see page 213).
 OCR400 Controller chassis (see page 214).
 Additional cabinets.
OW360_R1005 207
9.1 How is power distributed in an Ovation system?
 The IOIC module in the Controller chassis picks up 24 VDC main from the Controller
backplane and converts it to +5 VDC and +3.3 VDC for use by the Controller boards. The
Controller contains two IOIC 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.
9.1.1 OCR400 Controller/Marshalling cabinet (with local and remote cabling)

example
Note: For the power distribution scheme, see Power distribution scheme (see page 251).
Figure 60: OCR400 Controller/Marshalling cabinet
208 OW360_R1005
9.1.2 Extended I/O cabinet (illustrating cables and standard I/O) example
Figure 61: Extended I/O cabinet (illustrating cables and standard I/O)
OW360_R1005 209
9.1.3 Extended I/O cabinet (illustrating cables and relay output modules)
example
Figure 62: Extended I/O cabinet (illustrating cables and relay output modules)
210 OW360_R1005
9.1.4 Ovation Remote Node cabinet (illustrating cables) example
Figure 63: Ovation Remote Node cabinet (illustrating cables)
OW360_R1005 211
9.1.5 Ovation Power Distribution Module (PDM) example
Figure 64: Ovation Power Distribution Module (PDM)
212 OW360_R1005
9.1.6 Remote Node Transition Panel (dual-branch TND - top) (1P00028)
The following figure illustrates a Remote Node Transition panel:
Figure 65: Remote Node Transition panel (TND)
Note: Remote Node Transition panels are mounted to the DIN Rail by a 1/4 inch hex head
mounting screw clamp located on the panel. The torque specification for tightening the mounting
9.1.7 Dual Branch I/O Transition Panel - top (ROP) (3A99266)
The following figure illustrates an example of a dual-branch I/O Transition Panel (ROP):
Figure 66: Dual Branch I/O Transition Panel (ROP)
Note: Transition Panels are mounted to the DIN Rail by a 1/4 inch hex head mounting screw
clamp located in the middle of the Base. The torque specification for tightening the mounting
OW360_R1005 213
9.2 Connecting the power mains to an Ovation cabinet
9.1.8 Controller OCR400 and Controller OCR1100 backplane example
Figure 67: Controller OCR400 and Controller OCR1100 backplane
The AC/DC mains connect to the input power DIN rail assembly. Terminate the input power feeds
to the DIN rail components.
9.2.1 To connect the AC/DC Mains to the input power DIN rail assembly
1. Route the AC/DC Main cords into the cabinet. The maximum cable size is 10 AWG (4 mm 2).
2. Connect the AC/DC Mains to the appropriate Primary and Secondary terminal blocks.
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 DIN rail (PE). A properly
installed EMC ground provides protective earthing of the cabinet; however, relying on this
ground alone may violate National Electrical Codes.
214 OW360_R1005
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).
Figure 68: Line filter assembly in CE Mark Certified Ovation OCR400 or OCR1100 cabinet
(typical location)
OW360_R1005 215
9.3 Power supply front view
9.3 Pow er supply front view
The Ovation 24VDC power supply is a CE Mark certified power supply available in two styles:
 1X00781H01L - 24VDC 10A
 1X00781H02L - 24VDC 10A, Wide DC input
The following illustration shows the front view of the Ovation power supply and its associated
attributes.
Figure 69: Ovation Power supply
216 OW360_R1005
9.3 Power supply front view
Power supply attributes
ITEM DESCRIPTION
+ Output terminal - Positive output. Quick-connect spring clamp terminals, two pins per
pole.
- Output terminal - Negative (return) output. Quick-connect spring clamp terminals, two
pins per pole.
13 and 14 The DC ok relay contact is synchronized with the DC ok LED. Quick-connect spring
DC ok clamp terminals.
24 - 28 V Output Voltage Potentiometer - Open the flap to adjust the output voltage.
DC ok Green LED - Illuminates when the output voltage is >90% of the adjusted output voltage.
Overload Red LED - Illuminates when the voltage in the output terminals is <90% of the adjusted
output voltage, or in case of a short circuit in the output. Input voltage is required.
LED flashes when the unit has switched off due to over-temperature.
N N - Neutral input terminal. Quick-connect spring clamp terminals. (DC Return)
L L - Line input terminal. Quick-connect spring clamp terminals. (+DC Input)
GND PE (Protective Earth input). Quick-connect spring clamp terminals.
9.3.1 Diagnostic power supply LEDs
Diagnostic LEDs
LED INDICATORS OVERLOAD LED DC OK LED DC OK CONTACT
Normal mode OFF ON Closed

During Bonus Power OFF ON Closed
Overload (Volt < 90%) ON OFF Open
Output short circuit ON OFF Open
Temperature Shutdown Intermittent OFF Open

No input power OFF OFF Open
Note: All parameters are specified at 24 V, 10 A, 230 VAC, 25 C, 77F ambient and after five minutes run-in
time unless otherwise noted.
OW360_R1005 217
9.4 Power supply wiring illustration
9.4 Pow er supply w iring illustration
The following figure illustrates the power supply wiring from the front view of the power supply:
Figure 70: Power supply wiring illustration
218 OW360_R1005
9.5 Power supply wiring connections
9.5 Pow er supply w iring connections
The following diagram illustrates how wires are connected and disconnected into the power
supply terminal block.
Figure 71: Power supply wire connection
CAUTION!
1. Follow all national and local installation codes and installation regulations.
2. Make sure you use appropriate copper cables and wires and that all strands of a stranded
wire enter the terminal connection.
3. Up to two stranded wires with the same cross section are permitted in one connection point
(except PE wire).
4. Do not use the unit without the PE connection.
5. Unused terminal compartments should be securely tightened.
Terminals and wiring
WIRE INPUT OUTPUT DC-OK SIGNAL
spring-clamp terminals spring-clamp terminals spring-clamp terminals

Solid wire 0.5-6mm2 0.5-6mm2 0.5-6mm2
Stranded wire 0.5-4mm2 0.5-4mm2 0.5-4mm2
American Wire Gauge 20 - 10 AWG 20 - 10 AWG 20 - 10 AWG
OW360_R1005 219
9.6 Functional diagram
9.6 Functional diagram
Figure 72: Functional diagram
220 OW360_R1005
9.7 Power supply locking mechanism
9.7 Pow er supply locking mechanism
A locking mechanism, located at the bottom on the power supply, holds the power supply firmly to
the DIN rail. Use a slotted head screwdriver to pull down the lever arm to release the power
supply from the rail assembly. Lift the unit from the rail assembly while the lever arm is pulled
down.
To re-attach the power supply, engage the top the power supply to the rail and push the bottom of
the power supply onto the rail.
Figure 73: Power supply locking mechanism
OW360_R1005 221
9.8 Power supply specifications
9.8 Pow er supply specifications
The following table lists specifications for the 24 VDC power supply.
ITEM SPECS. COMMENTS
AC input nominal AC 100 - 240V

AC input range minimum 85 - 276 VAC Continuous operation
minimum 60 - 85 VAC Full power for 200ms, no damage between 0 and 85
VAC
minimum 276 - 300 VAC < 500ms
Input current Typical AC 100V AC 120V AC 230V
2.65A 2.22A 1.22A at 24V, 10A
Power factor Typical AC 100V AC 120V AC 230V
0.99 0.98 0.92 at 24V, 10A
Note: The power factor is the ratio of the true (or real)
power to the apparent power in an AC circuit.
AC input allowed maximum 300 VAC
voltage
L or N to earth
Input frequency nominal 50 - 60Hz +/- 6%
Inrush current AC 100V AC 120V AC 230V
maximum 10A peak 10A peak 10A peak
5A peak 4A peak 7A peak
typical
Values are over entire temperature range.
Turn-on voltage typical 81 VAC Steady-state value
Shut-down voltage typical 63 VAC Steady-state value
DC input - H01L nominal 110-150 V -20%/+25%
DC input range minimum 88-187 VDC Continuous operation
DC input current typical 2.37A 110 VDC, at 24V, 10A
DC input - H02L nominal 110-300 V -20%/+25%
DC input range minimum 88-375 VDC Continuous operation
DC input current typical 2.37/ 0.85 A 110/300 VDC, at 24V, 10A
Turn-on voltage typical - 80 VDC Steady state value
Shut-down voltage typical - 55 VDC Steady state value
Output voltage nominal 24V
typical 24.1V
Output current nominal 10A Continuously available at 24V
222 OW360_R1005
9.9 Power supply replacement cautions
ITEM SPECS. COMMENTS
Hold-up time AC 100V AC 120V AC 230V

typical 51ms 53ms 55ms at 24V, 5A
typical 26ms 27ms 28ms at 24V, 10A
Terminals and Spring-clamp terminals.
Wiring
Operational -13o F to 158o F or (25o C to Operational temperature is the same as the ambient
temperature temperature and is defined as the air temperature 2cm
+70o C) below the unit.
Storage -40o F to 185o F or (-40o C For storage and transportation.
Temperature
to +85o C)
Humidity 5 to 95% r.H. Do not energize while condensation is present.
Altitude 0 to 2000m (0 to 6560 ft.) Without restrictions.

2000 to 6000m (6560 to Reduce output power or ambient temperature.
20000 ft.)
Dimensions Length/Height - 4.9 inches
Width - 2.4 in.
Depth - 4.6 in.
Weight 2 lb
Note: All parameters are specified at 24 V, 10 A, 230 VAC, 25 C, 77F ambient and after five minutes run-in
time unless otherwise noted.
9.9 Pow er supply replacement cautions
CAUTION! Emerson recommends that a certified electrical technician performs the

replacement procedure when you are replacing power supplies while your system is powered
and online.
When replacing both primary and secondary power supply units, begin by replacing the
secondary power supplies first. After the secondary unit is re-installed and turned ON, indicator
lights illuminate indicating that you have power-on the secondary power supplies. Ensure the
secondary power supply units are online before removal of the primary units.
Proceed by turning the power OFF at the primary power supplies. The primary power supplies fail
over to the secondary power supplies, allowing replacement of both power supplies to be
accomplished without taking the system offline. Install the replacement power supplies and
reapply power to the primary power supply unit.
Both primary and secondary power supply units can be replaced by using the following
procedure:
 To replace redundant power supplies.
OW360_R1005 223
9.10 Using power supply modules
9.10 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.10.1 Power supply features
Ovation power supplies provide the following features:

 Wide range inputs.
 85 - 264 VAC
 88 - 187 VDC (H01L)
 88 - 375 VDC (H02L)
 47 - 63 Hz, AC Models.
 AC Input Power Supply.
 Input Inrush Current = 10A Max, 100 VAC, 120VAC
5A typical 100 VAC
4A peak 120 VAC
7A peak 230 VAC
 Input Current = 2.65 A rms, Vin = 100 VAC @24 VDC, 10A
1.22 A rms, Vin = 230 VAC @24 VDC, 10A
 DC Input Power Supply.
 Input Current = 2.37 A DC, Vin = 110 VDC @ 24 VDC, 10A
 Reverse polarity and Improper Lead Connection.
 You should always make proper connections to the power distribution module that
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 the Ovation I/O Reference
Manual.
 Main power supply and auxiliary power supply are individual DIN rail power supply units.
 24 VDC auxiliary output.
 Power factor corrected.
 Hot swap capability (online replacement in redundant configurations).
 26 mS @ 100 VAC, 28 mS @ 230 VAC Hold-up (Full load).
224 OW360_R1005
 LEDs on the front panel indicate conditions of input/output voltages.
Figure 74: Typical power supply front panel
OW360_R1005 225
9.10.2 Power supply module
There are Ovation power supply modules available for AC or DC input voltage.
 AC/DC module 1X00781H01L
 Uses 85 to 265 VAC or 88 to 187 VDC.
 AC/DC module 1X00781H02L
 Uses 85 to 265 VAC or 88 to 375 VDC.
There is one type of power supply module available (for AC or DC input):

 Auxiliary power supplies provide power only to field items (such as analog input current loops
and relay coils).
 Main power supplies provide power to the Controller and I/O modules.
AC/DC Power Supply Modules (1X00781H01L, 1X00781H02L)
MODULE OUTPUT DESCRIPTION
1X00781H01L 240 W - 24 V Single output
1X00781H02L 240 W - 24 V Single output. Wide range DC input.
9.10.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 240 W 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 240 W
capacity of the Auxiliary power supply.
226 OW360_R1005
9.10.4 Cabinet circuit breaker/on/off switch
Each cabinet provides a cabinet circuit breaker/on/off switch for the primary and backup input
power feeds. The two power supply sets form a redundant (auctioneered) pair.
Switching off power to the first set of power supplies (or losing the first set of power supplies),
while the second set of power supplies are working, will NOT cause loss of power to the
Controller, I/O, or field devices using power supply voltage.
Switching off power to both sets of power supplies (or losing both sets of power supplies) powers
down the entire cabinet, as well as any field devices that are powered from the cabinet.
Switching on power to either set of power supplies in the redundant pair provides power to the
Controller, energizes the I/O modules, and energizes any field devices using power supply
voltage. For correct operation of the redundant powering scheme, both cabinet circuit
breakers/on/off switches must be energized. Each set of power supplies (primary and backup)
has an independent switch in order to power up these units independently.
OW360_R1005 227
9.10.5 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 75: Ovation OCR400 or OCR1100 Controller cabinet configuration (illustrating

controls)
228 OW360_R1005
9.11 Power supply requirements (drawn from +24V main or auxiliary power supply)
9.11 Pow er supply requirements (draw n from +24V main or auxiliar y

pow er suppl y)
The following sections provide tables containing the power supply information for Ovation
equipment. The tables list main and auxiliary power.
 I/O cabinet components (see page 229).
 Analog I/O modules (see page 230).
 Digital I/O modules (see page 233).
 Bus interface modules (see page 240).
 Specialty I/O modules (see page 241).
 Remote function modules (see page 244).
Do NOT use these tables to determine the power drawn from the AC or DC Mains power supply.
See Electrical information for Ovation equipment (see page 15) instead.
In the following tables (E) designates Electronics modules and (P) designates Personality
modules. Values are rounded to the next tenth.
CAUTION! Access to the inside of Ovation cabinets should be limited to qualified, trained
personnel only.
9.11.1 I/O cabinet components power supply requirements
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.
Power supply requirements for Ovation I/O cabinet components

(power supply efficiency is not included)
COMPONENT EMERSON PART MAIN +24 POWER AUX POWER (W)

NUMBER (W) (TYPICAL) (TYPICAL)
Controller Cabinet Not applicable 18 W Not applicable

(cabinet + power supply fans)
OCR400 or
OCR1100 Controller
Marshalling Cabinet Not applicable 18 W Not applicable
Extended I/O Cabinet Not applicable 18 W Not applicable
Remote I/O Cabinet (ventilated) Not applicable 18 W Not applicable
Remote I/O Cabinet (sealed) Not applicable 24 W Not applicable
EMC Controller Cabinet Not applicable 18 W Not applicable
OW360_R1005 229

EMC Extended I/O Cabinet Not applicable 18 W Not applicable

EMC Remote I/O Cabinet Not applicable 18 W Not applicable
(ventilated)
EMC Remote I/O Cabinet Not applicable 24 W Not applicable
(sealed)
Single OCR 400 Controller: 5X00127 20 W Not applicable
1 Processor card
1 IOIC card
1 Fan
Dual OCR 400 Controller: 5X00127 40 W Not applicable
2 Processor cards
2 IOIC cards
2 Fans
Redundant Remote Node 1C31203 (E) 12 W Not applicable
Controller module (in Remote
Node Cabinet) 1C31204G01, G03 (P)
Redundant MAU module 1C31179 (E) 13.2 W Not applicable

(Controller cabinet) 1C31181G01-G04 (P)
230 OW360_R1005
9.11.2 Analog I/O module power supply requirements
The following table lists the power an analog input/analog output 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


Analog Input (13-bit) 1C31113G01-G06 2.5 W Not applicable

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


Speed)
1C31116G04 (P)
(± 20mV, ± 50mV,
± 100V) (Thermocouple)
Speed)
1C31116G01 (P)
(± 20mV, ± 50mV, ± 100V)
Analog Input (14-bit) (High Speed) 5X00070G02 (E) 2.4 W 0.2 W
(± 1mA 2 wire local powered) 1C31116G03 (P) (8 locally powered
channels on @1mA
each)
(0.024W per locally
powered channel)
(± 1mA 4 wire field powered) 1C31116G02 (P)
Analog Input (0-10V High 5X00679G01 (E) 3.1 W Not applicable
Impedance (8 channel)
1C31227G02 (P)
HART Analog Input 5X00058G01 (E) 1.2 W 5.7 W

5X00059G01 (P) (8 locally powered
channels on @20mA
each)
1.8 W + 0.48W per
locally powered
channel)
HART High Performance Analog 5X00106G01/2 (E) 4.1 W 3.9 W
Input
5X00109G01 (P) (8 locally powered
channels on @20mA
each)
(0.48W per locally
powered channel)
Analog Output 1C31129G01, G02 2W Not applicable
(E)
(Voltage)
1C31132G01 (P)
Redundant Analog Output 1C31129G05 (E) 4W Not applicable
(Voltage - for redundant 1C31132G02 (P)
applications)
Analog Output 1C31129G03, G04 4W Not applicable
(E)
(Current)
1C31132G01 (P)
HART Analog Output 5X00062G01 (E) 1.2 W 6W
5X00063G01 (P)
232 OW360_R1005

HART High Performance Analog 5X00167G01 (E) 4.6 W Not applicable

Output
1X00188H01
(molded plastic
cavity insert)
RTD Input 1C31161G01 (E) 3.6 W Not Applicable
(50Hz/60Hz filtered inputs) 1C31164G01 (P)
(4 channels)
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)
(8 channels) 5X00121G01 (P)
(8 channels Compact) 1X00885H01
(Cavity insert)
RTD Input (16 channels) 5X00622G01 (E) 3.9 W Not applicable
No personality
module
16 Channel Thermocouple Input 5X00594G01 (E) 2.4 W Not applicable
(20 mV, 50 mV, 100 mV) 1C31116G05 (P)
16 Channel 4-20 mA Analog Input 5X00501G01 (E) 9.4 W Not applicable
(2-wire and 4-wire) 5X00502G01 (P)
16 Channel 4-20 mA Analog Input 5X00501G01 (E) 9.4 W Not applicable
(2-wire only) 1X00692H01 (P)
OW360_R1005 233
9.11.3 Digital I/O module power supply requirements
The following table lists the power a digital input/digital output 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 Digital I/O modules


Contact Input 1C31142G01 (E) 4.5 W Not applicable

1C31110G03 (P)
Contact Input Sequence of 5X00605G01 (E) 3.4 W w/all inputs Not applicable
Events (32-Channel) open
1X00884H01 (cavity
insert) 7 W w/all inputs
closed
Compact Contact Input 1C31234G01 (E) 4.5 W Not applicable
1C31238H01 (molded
Digital Input 1C31107G01 (E) 1.1 W 0.75 W (24V) All channels
on.
24 VDC/48VDC 1C31110G01, G02
(P) 1.5 W (48V) All channels
on.
Digital Input (current sinking - 5X00411G01 (E) 1.1 W w/all inputs off Not applicable
redundant)
5X00414G01 (P) 3.5 W w/all inputs on
24 V (single-ended)
IEC 61131-2 Compliant Type 1
Digital Input 1C31107G02 (E) 1.1 W Not applicable
125 VDC 1C31110G01, G02
(P)
Compact Digital Input 1C31232G01 (E) 1.1 W 0.7 W (24V)
24/48 VDC single-ended inputs 1C31238H01 1.8 W (48V)
with common return (molded plastic cavity
insert)
24/48 VAC/VDC isolated 1C31238H01 1.8 W (48V)
differential inputs (molded plastic cavity
insert)
24/48 VAC/VDC individually 5X00034G01 (P) 1.8 W (48V)
fused inputs with common
power supply
234 OW360_R1005

Compact Digital Input 1C31232G02 (E) 1.1 W 0.7 W (24V)1

24VDC 5X00765G01 (P)
individually current limited with
common power supply
Compact Digital Input 1C31232G03 (E) 1.1 W Not applicable
125 VAC/VDC isolated 1C31238H01
differential inputs (molded plastic cavity
insert)
Compact Digital Input 1C31232G03 (E) 1.1 W Not applicable
125 VAC/VDC individually fused 5X00034G01 (P)
inputs with common power
supply
Digital Input 5X00499G01 (E) 1.6 W 3.2 W
24 VDC (32 Channel) 1X00690H01 (P)
Digital Output 1C31122G01 (E) 2.2 W 19.2 W (24V)

(no relay panel) or 38.4 W (48V)
1C31122G02 (E) (8 outputs on @100 mA
each)
1C31125G01 (P)
Digital Output 5X00500G01 (E) 1.3 W 53 W
(32 Channel 24 High-Side, 1X00691H01 (P)
Single-Ended) VDC
Digital Output plus 1C31122G01 (E) 2.2 W (module) 5.9 W (24V) (R)
Solid State Relay Panel (16 or (R) not applicable
relays)
1C31122G02 (E)
1C31125G02 (P)
5A22410G01 (R) AC
contacts
or
5A22410G02 (R) DC
contacts
Digital Output plus 1C31122G01 (E) 2.2 W (module) Not applicable (assumes
panel powered from
Solid State Relay Panel (16 or (R) not applicable external 24V power
relays) supply)
1C31122G02 (E)
1C31125G03 (P)
5A22410G01 (R) AC
contacts
or
5A22410G02 (R) DC
contacts
OW360_R1005 235

G2R Style Panel (16 relays) or (R) not applicable
1C31122G02 (E)
1C31125G02 (P)
5A22411G01 (R)
panel powered from
G2R Style Panel (16 relays) or (R) not applicable external 24V power
1C31122G02 (E) supply)
1C31125G03 (P)
5A22411G01 (R)
KUEP Style Panel (8 Form C or (R) not applicable
relays)
1C31122G02 (E)
1C31125G02 (P)
5A22412G01 (R)
panel powered from
KUEP Style Panel (8 Form C or (R) not applicable external 24V power
relays) supply)
1C31122G02 (E)
1C31125G03 (P)
5A22412G01 (R)
Digital Output plus two 1C31122G01 (E) 2.2 W (module) 31.68 W (24V) (R)
KUEP Style Panels (2 x 8 Form or (R) not applicable
C relays)
1C31122G02 (E)
1C31125G02 (P)
5A22412G01 (R)
Digital Output plus two 1C31122G01 (E) 2.2 W (module) Not applicable (assumes
panel powered from
KUEP Style Panels (2 x 8 Form or (R) not applicable external 24V power
C relays) supply)
1C31122G02 (E)
1C31125G03 (P)
5A22412G01 (R)
KUEP Style Panel (8 Form X or (R) not applicable
relays)
1C31122G02 (E)
1C31125G02 (P)
5A22412G02 (R)
236 OW360_R1005

panel powered from
KUEP Style Panel (8 Form X or (R) not applicable external 24V power
relays) supply)
1C31122G02 (E)
1C31125G03 (P)
5A22412G02 (R)
Digital Output plus two 1C31122G01 (E) 2.2 W (module) 22.56 W (24V) (R)
KUEP Style Panels (2 x 8 Form or (R) not applicable
X relays)
1C31122G02 (E)
1C31125G02 (P)
5A22412G02 (R)
Digital Output plus two 1C31122G01 (E) 2.2 W (module) Not applicable (assumes
panel powered from
KUEP Style Panels (2 x 8 Form or (R) not applicable external 24V power
X relays) supply)
1C31122G02 (E)
1C31125G03 (P)
5A22412G02 (R)
High Side Digital Output 5X00270G01 (E) 2.2 W 48 W (VS=24V,
8 channels on
5X00273G01 (P) @250mA/channel)
Relay Output module (E) plus 1C31219G01 (E) 1.9 W (E) 0.29 W (E)
base with
OR Base not applicable + 9.1 W (Base with 16
16 G2R relays relays)
1C31219G02 (E)
-----------------------
1C31223G01 (Base)
= 9.39 W
base with 12 KUEP Form C
Relays added OR Base not applicable + 23.45 W (Base with 12
relays)
1C31219G02 (E)
-----------------------
1C31222G01 (Base)
= 23.74 W
base with 12 KUEP Form X
OR Base not applicable + 15.9 W (Base with 12
Relays added
relays)
1C31219G02 (E)
-----------------------
1C31222G01 (Base)
= 16.19 W
OW360_R1005 237

Relay Output with Contact 1C31219G01 (E) 1.9 W 0.29 W (E)

Monitoring module
OR + 10.6 W (Base with 8
relays)
1C31219G02 (E)
-----------------------
5X00564G01 and
5X00564G02 (Base) = 10.89 W
Relay Output 32 channel (E) 5X00583G01 (E) 2.0 W 1.0 W (24V)

plus base with 32 Form C
Relays added 5X00584G01 (Base, Base not applicable + 11.3 W (24V)
non-fused)
----------------------------
OR
= 12.3W
5X00623G01 (Base,
fused)
Sequence of Events 1C31157G01 (E) 1.5 W 1.1 W (24V) All inputs on
24 VDC/48VDC 1C31110G01, G02 2.2 W (48V) All inputs on
(P)
Digital Input
Sequence of Events 1C31157G02 (E) 1.5 W Not applicable
125 VDC Digital Input 1C31110G01, G02
(P)
Sequence of Events 1C31157G03 (E) 4.6 W Not applicable
48V Contact Input 1C31110G03 (P)
Compact Seq. of Events 1C31233G01 (E) 1.5 W 0.7 W (24V)
24/48 VDC single-ended inputs 1C31238H01 (molded 1.7 W (48V)
with common return plastic cavity insert)
24/48 VDC isolated differential 1C31238H01 (molded 1.7 W (48V)
digital inputs plastic cavity insert)
24/48 VDC individually fused 5X00034G01 (P) 1.7 W (48V)
digital inputs with common
power supply
Compact Seq. of Events 1C31233g02 (E) 1.5 W 0.7 W (24V)1
24VDC individually current 5X00765G01 (P)
limited with common power
supply
Compact Seq. of Events 1C31233G03 (E) 1.5 W Not applicable
125 VDC isolated differential 1C31238H01 (molded
digital inputs plastic cavity insert)
Compact Seq. of Events 1C31233G03 (E) 1.5 W Not Applicable
125 VDC individually fused 5X00034G01 (P)
digital inputs with common
power supply
238 OW360_R1005

Compact Seq. of Events 1C31233G04 (E) 4.5 W Not Applicable

48 V Contact Input 1C31238H01
(molded plastic cavity
insert)
Enhanced Compact Seq. of 5X00357G01 (E) 1.9 W 0.7 W (24V)
Events
1C31238H01 (molded 1.4 W (48V)
24/48 VDC single-ended digital plastic cavity insert)
inputs with common return

Events
1C31238H01 (molded 1.3 W (48V)
24/48 VDC isolated differential plastic cavity insert)
digital inputs
Events
5X00034G01 (P) 1.3 W (48V)
24/48 VDC single ended
individually fused digital inputs
with common power supply
Enhanced Compact Seq. of 1C31357G02 (E) 1.6 W 0.7 W (24V)1
Events
5X00765G01 (P)
24VDC single ended
common power supply
Enhanced Compact Seq. of 5X00357G03 (E) 1.5 W Not applicable
Events
1C31238H01 (molded
125 VDC isolated differential plastic cavity insert)
digital inputs
Enhanced Compact Seq. of 5X00357G03(E) 1.5 W Not applicable
Events
5X00034G01 (P)
125 VDC single-ended
with common power supply
Enhanced Compact Seq. of 5X00357G04 (E) 4.3 W Not applicable
Events
1C31238H01 (molded
48 VDC contact input plastic cavity insert)
Enhanced Compact Seq. of 5X00357G05 (E) 1.8 W 2.14 W
Events
1C31238H01 (molded
24 VDC isolated differential plastic cavity insert)
digital inputs with Wire break
detection
Enhanced Compact Seq. of 5X00357G05 (E) 1.8 W 2.14 W
Events
5X00034G01 (P)
24 VDC single ended
with common power supply with
wire break detection
OW360_R1005 239

Enhanced Compact Seq. of 1C31357G02 (E) 1.8 W 2.14 W 1

Events
5X00765G01 (P)
24 VDC single ended
common power supply with wire
break detection
9.11.4 Bus interface module power supply requirements
The following table lists the power a bus interface module draws from the +24V Main Power
Power requirements for Ovation Bus interface modules

COMPONENT EMERSON PART MAIN +24 POWER (W) AUX POWER

NUMBER (TYPICAL) (W) (TYPICAL)
Foundation Fieldbus 5X00301G01 (E) 1.82 W 0.42 W per channel

5X00327G01 (P)
Foundation Fieldbus 1X00418H01 Not applicable 1.8 W per segment
Power Conditioner
Profibus 5X00300G01, G02 (E) 3.84 W Not applicable
5X00321G01 (P)
DeviceNet 5X00376G01 (E) 3.17 W 0.58 W per channel
5X00375G01 (P)
Ethernet Link Controller 5X00419G01 (E) 1.68 W Not applicable
1X00569H01
240 OW360_R1005
9.11.5 Specialty I/O module power supply requirements
The following table lists the power a specialty 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 Specialty I/O modules

COMPONENT EMERSON PART MAIN +24 POWER AUX POWER

NUMBER (W) (TYPICAL) (W) (TYPICAL)
Link Controller For RS232: 3W Not applicable

1C31166G01 (E)
1C31169G01 (P)
For RS485/422:
1C31166G01 (E)
1C31169G02 (P
Loop Interface 1C31174GX1, GX2 (E) 2.7 W When used:
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
(2 outputs @100mA
each)
12-bit Voltage AO
4.8 W (24V)
0 to 10V
9.6 W (48V)
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
Local Powered
(E) GX4 Analog Inputs:
(X = 0 or 2) (2 inputs @20mA
each)
0.96 W (24V)
OW360_R1005 241

Pulse Accumulator 1C31147G01 (E) 1.6 W When used:

24/48 VDC Count Inputs 1C31150G01-G02 (P) 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) 1.6 W Not applicable
24/48 VDC Count Inputs 1C31150G03 (P)
Pulse Accumulator 1C31147G02 (E) 1.6 W Not applicable
High Speed 1C31150G01-G03 (P)
+5V Count Inputs
Servo Driver 1C31199G01,G04 6.7 W Not applicable
DC LVDT 1C31201G01 (P)
Servo Driver 1C31199G02, G03, 5.3 W Not applicable
G05, and G06 (E)
AC LVT
1C31201G02 (P)
Servo Driver 1C31199G06 (E) 5.3 W Not applicable
AC LVT 1C31201G03 (P)
(LM6000 Gas Turbine

Application)
Speed Detector 1C31189G01, G03, 4.8 W Not applicable
G04 (E)
1C31192G01 (P)
Valve Positioner 1C31194G01-G05 (E) 6.3 W/VA Digital Input
(Rev.50 and later)
(ARM9 microprocessor) 0.12 W/VA (24 VDC)
1C31197G01-G05 (P)
(Second generation module) 0.24 W/VA (48 VDC)
Digital Output
(100mA load)
3.2 W/VA (24 VDC)
6.4 W/VA (48 VDC)
Valve Positioner 1C31194G01-G04 (E) 9.2 W/VA9 Digital Input
(Rev. 42 through Rev.
(ARM9 microprocessor) 49) 0.12 W/VA (24 VDC)
(Second generation module) 1C31197G01-G05 (P) 0.24 W/VA (48 VDC)
Digital Output
(100mA load)
3.2 W/VA (24 VDC)
6.4 W/VA (48 VDC)
242 OW360_R1005

Valve Positioner 1C31194G01-G02 (E) 4.3 2 W Typical Digital Input

0.09 W (24 VDC)
(86C196 microprocessor) 1C31197G01-G05 (P) 6.5 W Maximum Typical
(First generation module) 0.18 W (48 VDC)
(This module is supported but is Typical
no longer available due to parts
obsolescence.) Digital Output
(100mA load)
2.4 W (24 VDC)
Typical
4.8 W (48 VDC)

Typical
Numalogic Fast Ethernet Remote 5X00467 (E) 4.3 W Not available
I/O Electronics module Part of kit 5X00512
Machinery Health Monitor 5X00717G01 (E) 7.51 W Power supply
requirements:
(1 logic card and 2 field
cards)  9.96 W (8 - 35 mA
loads)
 8.64 W (8 - 30 mA
loads)
 6.6 W (8 - 20 mA
loads)
Power dissipated in
module case:
1.76 W
+
 1.23 W (8 - 35 mA
loads)
 1.03 W (8 - 30 mA
loads)
 0.72 W (8 - 20 mA
loads)
Digital Excitation Controller (+/- 5X00658G01 (E) 7.2 W 2.4 W
10V analog output)
cards)
Digital Excitation Controller (4- 5X00658G02 (E) 7.2 W 2.4 W
20mA analog output)
cards)
Note:
(E) - designates Electronics modules.
(P) - designates Personality modules.
CAUTION! When designing a cabinet layout configuration, Emerson recommends maintaining

a 20% reserve on cabinet power supply output loading. System designers should target 80%
of power supply output rating as the upper limit in order to allow for margin within the overall
power supply scheme.
OW360_R1005 243
9.12 Monitoring power supply status
9.11.6 Power supply requirements for remote function modules
The following table lists the power a remote function module draws from the +24V Main Power
Power requirements for Ovation remote function components


Redundant Remote Node 1C31203 (E) 12 W Not applicable

Controller module (in Remote
Node Cabinet) 1C31204G01, G03 (P)
Redundant MAU module 1C31179 (E) 13.2 W Not applicable

(Controller cabinet) 1C31181G01-G04 (P)
9.12 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 four redundant power
supplies).
A healthy status indicates the presence of output voltage on the power supplies. An unhealthy
status indicates the lack of one or both output voltages on the power supplies 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 a red LED indicates an unhealthy voltage
status.
The status is reflected in Node (RN) Point Records that 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. Refer to the
Ovation Operator Station User Guide for more information on the Point Information and Base
Alarm applications.
9.12.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.
244 OW360_R1005
9.12 Monitoring power supply status
9.12.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 (CBK).
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).
Figure 76: Monitoring local power supplies
OW360_R1005 245
9.13 What is an external supply?
Figure 77: Monitoring remote node power supplies
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.
The auxiliary power is bussed along an entire branch of I/O modules. All I/O modules within a
branch MUST use the same auxiliary power voltage for proper operation. External auxiliary power
can be applied to each branch individually.
If an Ovation I/O module is to be connected to an external power supply, perform the following
procedure BEFORE connecting the power supply to the Ovation module and before power-up.
Note: Using external auxiliary power with the Relay Output module is not recommend. Instead,
use the Ovation internal auxiliary supply for relay coil power.
246 OW360_R1005
9.13.1 To prepare for connecting an external power supply
CAUTION! Using an external power supply may introduce dangerous voltages to an I/O
cabinet. Do NOT apply external power to a cabinet until the appropriate internal auxiliary
power supply fuses have been removed and the required fuse covers have been installed.
1. Identify the specific I/O branch to which the Ovation I/O module is assigned and the back
panel (CBO) or transition panel (ROP or TND) associated with the I/O branch (see the
following figures for panel locations).
Figure 78: Locations of CBO, ROP, and TND cabinet panels
OW360_R1005 247
Figure 79: Location of ROP panel in cabinet backs
2. If the I/O branch is associated with a transition panel, perform the following:
a) If the transition panel has a cover, remove it 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) Replace the transition panel cover (where applicable) after the fuses are removed. A fuse
cover kit is not required for transition panels that have a cover. 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.
248 OW360_R1005
Figure 80: Auxiliary power supply fuse locations for ROP and TND panels
OW360_R1005 249
3. If the I/O branch is associated with a back-plane (CBO), 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.
Note: Base unit terminal block locations A17 (PS+) and B17 (PS+) are connected to the same
potential within the base unit.
250 OW360_R1005
9.14 Power distribution scheme
9.14 Pow er distribution scheme
Figure 81: Power distribution scheme
OW360_R1005 251
S E C T I O N 10
10 Planning for replacement parts and repair service
IN THIS SECTION
Ordering spare parts ....................................................................................................... 253

Returning parts to Emerson for repair service ................................................................ 254
Part failure during project startup .................................................................................... 256
Determining repair prices ................................................................................................ 257
Tracking part repairs ....................................................................................................... 257
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 253) for any part you order. You might
also want to know the price of a part (see page 254) 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.
OW360_R1005 253
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. Obtain Material Return Tracking (MRT) number (see page 255) from Emerson.
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.
Shipping instructions
CUSTOMER ADDRESS METHOD COMMENTS FREIGHT CARRIERS
US Emerson Process Prepaid Provide shipment Recommended carrier

Customers Management information information is provided
Power & Water Solutions (airway bill when an MRT number
200 Beta Drive number) via is requested.
Pittsburgh, PA 15238 telephone, fax,
email, or mail.
ATTENTION:
Repair Department
MRT NUMBER:
___________*
*Note: At least one of the
assigned MRT numbers must
be shown.
254 OW360_R1005
CUSTOMER ADDRESS METHOD COMMENTS FREIGHT CARRIERS
Non-US Emerson Process Prepaid Prior to shipping, Recommended carrier

Customers Management the returnee must information is provided
Power & Water Solutions provide shipment when an MRT number
200 Beta Drive information to the is requested.
Pittsburgh, PA 15238 Emerson Repair
Department via
ATTENTION: telephone, fax,
Repair Department email, or mail. This
information should
MRT NUMBER: include airway bill
___________ number, method of
shipment, weights
and dimensions,
*Note: At least one of the and a copy of the
assigned MRT numbers must proforma or
be shown. commercial
invoice.
Returns of
repaired parts
from Emerson are
prepaid only to the
US port of export.
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 (see page 255).
You must mark the Material Return Tracking (MRT) number (see page 255) 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.
1. If for any reason you need to return an Emerson product for repair, please contact us to
obtain an MRT number before shipping the defective material to Emerson. You may contact
us to obtain an MRT number through one of the following methods:
 Via email at PWS.Aftermarket@emersonprocess.com
 Via the Ovation & WDPF Users Web site (https://www.ovationusers.com)
 Via FAX at (412) 963-4245 during normal work hours.
 Via telephone at (800) 397-9767 or
(412) 963-4244 during normal work hours.
 In case of an emergency, call the Technical Support phone at (800) 445-9723.
OW360_R1005 255
2. When you contact Emerson to obtain an MRT number, please be prepared to provide the
following information:
 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 SHIPPING GUIDELINES

METHOD
In-warranty - MRT number (see page 255) Prepaid Refer to Returning parts to
parts (provided by Emerson) Emerson for repair service. (see
page 254)
- Contact person (at customer site)
- Emerson Project number
Non-warranty - MRT number (see page 255) Prepaid Refer to Returning parts to
parts (provided by Emerson) Emerson for repair service (see
page 254).
- 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.
256 OW360_R1005
10.3 Part failure during project startup
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).

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.
OW360_R1005 257
S E C T I O N 11
11 Guidelines for shipping and storage of Ovation

equipment
IN THIS SECTION
Shipping Ovation equipment guidelines .......................................................................... 259

Lifting Ovation equipment guidelines .............................................................................. 260
Off-loading and unpacking Ovation equipment ............................................................... 262
Repacking and returning Ovation equipment .................................................................. 262
Repacking third-party products ....................................................................................... 263
Transporting Ovation equipment to the specific installation location .............................. 263
Storing Ovation equipment .............................................................................................. 263
11.1 Shipping Ovation equipment guidelines
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.
OW360_R1005 259
11.1 Shipping Ovation equipment guidelines
13. Mark shipping containers to identify the following:

 Front and back.
 Destination.
 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.
260 OW360_R1005
11.2 Lifting Ovation equipment guidelines
11.2 Lifting Ovation equipment guidelines
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
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)
Static load rating of 680 kg
(1500 lb)
5X00293 (466.75 lb) (78 x 24 x 24 in)
CE Mark Certified
CE Mark Certified (458.86 lb) (78 x 24 x 24 in)
Remote I/O 209.48 kg 2000 x 600 x 600 mm
Sealed (461.83 lb) (78 x 24 x 24 in)
CE Mark Certified
Remote I/O 209.48 kg 2000 x 600 x 600 mm
CE Mark Certified
(437.75 lb) (78 x 24 x 24 in)
Marshalling 283.6 kg 2000 x 800 x 600 mm
(624 lb) (78 x 32 x 24 in)
Marshalling 301 kg 2000 x 914 x 600 mm
(664 lb)
(78 x 36 x 24 in)
(393.86 lb) (78 x 24 x 24 in)
Remote I/O 180.0 kg 2000 x 600 x 600 mm
Sealed (396.83 lb) (78 x 24 x 24 in)
OW360_R1005 261
11.3 Off-loading and unpacking Ovation equipment
Remote I/O 180.0 kg 2000 x 600 x 600 mm

1 Assumes Controller cabinet is populated with 16 I/O base assemblies (32 Electronic modules and 32
Personality modules).
11.3 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.
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 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.
262 OW360_R1005
11.5 Repacking third-party products
11.5 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 product’s 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 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 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 13)
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 rehandling.
3. Stack cables on two-inch-by-four-inch lumber to a maximum height of three feet.
OW360_R1005 263
S E C T I O N 12
12 Planning your CE Mark Certified and KC Compliance

mark systems
IN THIS SECTION
CE Mark certified systems .............................................................................................. 265

CE Mark accuracy considerations ................................................................................... 266
Third-party components usage in CE Mark Certified systems ........................................ 266
Grounding cable shields for CE Mark Certified systems ................................................ 267
Cabling requirements for CE Mark Certified systems ..................................................... 270
KC Compliance mark ...................................................................................................... 270
12.1 CE Mark certified systems
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) and European Union (EU) single market.
Non-EMC cabinet approach
A CE Mark Certified system is constructed with 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.
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 (5X00423) and the Low Voltage
Safety Technical File for Ovation (5X00394).
This approach utilizes requirements on field wiring shield termination to ensure compliance with
the specific European Electromagnetic Emissions/Immunity and low voltage directive safety
requirement.
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 or equivalent, and a grounding stud for
tying the EMC ground.
OW360_R1005 265
12.2 CE Mark accuracy considerations
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.
 Drawing 5X00475 - This drawing contains a baseline listing of third party workstation and
peripheral components applicable for the CE Mark Certified System.
12.2 CE Mark accurac y consideration s
EMC Technical Construction File and 5X00423 references various temporary electromagnetic
interferences that the Ovation system must operate through. During these conditions, the
accuracy of all Ovation analog points shall be derated to 2.5%.
12.3 Third-party components usage in CE Mark Certified systems
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 5X00424 (for
Ovation Controller and I/O) and drawing 5X00475 (for workstation and peripheral equipment).
 Follow all vendor-recommended CE Mark requirements and installation guidelines as listed in
the vendor’s 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 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.
266 OW360_R1005
12.4 Grounding cable shields for CE Mark Certified systems
12.4 Grounding cable s hields 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.
12.4.1 Grounding panel (3A99245G01) method
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.
OW360_R1005 267
12.4.2 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.
268 OW360_R1005
Mounting Hole
Cable Clamp (typical, 8 places)
0.81
(user installed)
Remove this 5A26440H01
shunt if the 12mm dia.
cable(s) in the 5A26440H02
adjacent clamp 8mm dia.
are to be 5A26440H03
capacitively 6mm dia.
grounded.
9.46
0.81
1.00 2.00 2.00 2.00 1.00
8.00
Figure 82: Grounding Panel
OW360_R1005 269
12.5 Cabling requirements for CE Mark Certified systems
12.4.3 Alternative shield grounding
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.5 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.6 KC Compliance mark
The KC Compliance mark indicates that a product has been manufactured to comply with Korean
Radio Act standards.
In accordance with the KC Compliance mark, the manufacturer's name, address, and contact
number are as follows:
Emerson Process Management, Power & Water Solutions Inc.

200 Beta Drive
Pittsburgh, Pennsylvania 15238 (USA)
(412) 963-4000
270 OW360_R1005
S E C T I O N 13
13 Planning your IEC61131-2 system
IN THIS SECTION
What is an IEC61131-2 certified system? ....................................................................... 271

Grounding cable shields for IE61131-2 certified system ................................................ 271
Cabling requirements for IEC61131-2 certified systems................................................. 271
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:
 Technical File 500394
 Drawing 5X00393 - This drawing contains a baseline listing of all Ovation components
applicable for the IEC61131-2 Certified System.
13.2 Grounding cable shields 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. Refer to Using a grounding panel for CE Mark Certified systems (see page
267) and Grounding panel configuration (see page 268) 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 268) for a list of acceptable equivalent I/O termination methods.
OW360_R1005 271
13.3 Cabling requirements for IEC61131-2 certified systems
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.
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:
 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.
272 OW360_R1005
S E C T I O N 14
14 Planning to meet industry standards of compliance
IN THIS SECTION
Design standards ............................................................................................................ 273

Reliability standards ........................................................................................................ 273
Electrical interference standards ..................................................................................... 273
Safety standards ............................................................................................................. 273
Security standards........................................................................................................... 274
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 in the process industries.
OW360_R1005 273
14.5 Security standards
14.5 Security standards
Most current process control systems were designed for functionality and performance, not for
security. In today's security-conscious climate, many organizations, such as North America
Electric Reliability Corporation (NERC), are working with the process control industry to improve
the process control industry's approach to security.
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 e-mailing critical information to unauthorized users.
Improving the security of your Ovation Distributed Control System (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 strongly 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.
Emerson also provides an Ovation Security Center (OSC). 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 the cyber security of your Ovation DCS without
disrupting the controlled process. Refer to the Ovation Security Center User Guide for additional
information about OSC.
274 OW360_R1005
S E C T I O N 15
15 Planning your internet addressing
IN THIS SECTION
Classes of internet addresses ......................................................................................... 275

Internet address notation ................................................................................................ 276
Allowable internet addresses .......................................................................................... 276
Internet address conventions .......................................................................................... 277
Subnet masks.................................................................................................................. 277
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 7 24
0 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 1 14 16
1 0 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.
1 1 1 21 8
1 1 0 Network Host
OW360_R1005 275
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 ADDRESS OR RANGE STATUS
A 0.0.0.0 Reserved
1.0.0.0 through 126.0.0.0 Available
127.0.0.0 Reserved
B 128.0.0.0 Reserved
191.255.0.0 Reserved
C 192.0.0.0 Reserved
223.255.255.0 Reserved
D, E 224.0.0.0 through 255.255.255.254 Reserved
255.255.255.255 Broadcast
276 OW360_R1005
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 HOST BITS HEX M AS K DECIM AL M AS K
0 8 0 0
1 7 0x80 128
2 6 0xC0 192
3 5 0xE0 224
4 4 0xF0 240
5 3 0xF8 248
6 2 0xFC 252
7 1 0xFE 254
8 0 0xFF 255
OW360_R1005 277
S E C T I O N 16
16 Planning your Ovation database
IN THIS SECTION
What is a Relational Database? ...................................................................................... 280

What are the types of Ovation Databases? .................................................................... 281
How does the Database relate to other Ovation functions? ........................................... 282
What is the organization of the Ovation database? ........................................................ 282
Database terminology ..................................................................................................... 284
What is a point?............................................................................................................... 286
What are point records? .................................................................................................. 288
What is point frequency? ................................................................................................. 289
Understanding point names ............................................................................................ 289
Using valid Ovation point names ..................................................................................... 289
Using fully qualified point names ..................................................................................... 291
Creating the Ovation Database ....................................................................................... 292
OW360_R1005 279
16.1 What is a Relational Database?
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 12c. For computing environments, such as Ovation
that are connected through networks, Oracle combines the data physically located on different
computers into one logical database that can be accessed by non-controller network nodes.
280 OW360_R1005
16.2 What are the types of Ovation Databases?
16.2 What are the types of Ovation Databases?

At the heart of the RDBMS is the Ovation Database which consists of a Master Database and is
supported by various Distributed Databases.
The Distributed Database contains subsets of information from 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.
The contents of these subsets depend on the system drops as defined below:
 Identification of Plant Mode Point (if applicable).
 Information used to retrieve process point data from the Ovation Network. For Operator
Stations, this includes all system points updated through the Load function for originated and
explicitly received points and the Distributed Database Propagation software for all other
system points. For Controllers, this includes only originated and explicitly received points
(updated through the Drop load function). Refer to Ovation Developer Studio User Guide, for
more information.
 Identification of primary/partner drop ID pairings for system drops. For Ovation Operator
Stations, this includes all system drops updated through Distributed Database Propagation
Software. For Controllers, this means only itself (if redundant) and any redundant drops which
it explicitly receives points from (updated through the Load function).
 System Point Directory. This is for Ovation Operator Stations only. It is updated through the
Distributed Database Propagation Software.
 MMI data for all System Points. This is for Ovation Operator Stations only. It is updated
through the Distributed Database Propagation Software.
 Global Point Groups. This is for Ovation Operator Stations only. They are updated through
the Distributed Database Propagation Software.
The Distributed Database subsets are kept consistent with the contents of the Master Database.
Database propagation provides the mechanism whereby the database contents at each
distributed location are kept consistent with the contents of the Master Database. The propagation
of all database changes is performed by an exchange of messages between a server process
(db_xmit_server) which monitors the Master Database and client processes (db_xmit_client)
which operate on each distributed station.
Changes to the Master Database are performed using system editing functions such as those
provided by the Ovation Developer Studio and the Ovation Control Builder. These changes are
applied to the database through the business rules Application Programming Interface (API)
functions. When a point modification is loaded to the originating drop(s) through the Load
function, a record of the change is maintained in a table in the Master Database.
Similarly, a change is recorded whenever Point Group objects are changed in the Ovation
Developer Studio or Point Builder. The server monitors this table to identify when changes have
been loaded to the system.
Each change is identified by a unique sequence number which allows the server to ensure that
changes are applied to the Distributed Databases in the same order that they were applied to the
Master Database.
OW360_R1005 281
16.3 How does the Database relate to other Ovation functions?
As changes are made/loaded, the server performs a multicast broadcast of applicable data for
each change in sequence. Mechanisms exist whereby clients can detect if messages have been
missed and establish a direct TCP connection with the server to quickly get “up-to-date.” The
server also periodically broadcasts (through multicast) the Plant Mode Point Information,
primary/partner drop information, drop mismatch information, and the current sequence number.
Clients use the current sequence number to determine if they need to explicitly request an
update.
16.3 How does the Database relate to other Ovation functions?
The Ovation Database is provided with the Ovation Windows System. The database consists of a
relational database and supporting distributed databases. All the supporting pieces of information
that are used by an Ovation system are contained in the database. This includes information such
as process point information, drop configuration, process control sheets, and many other types of
system data.
Having all the pertinent system information in one database provides the flexibility and processing
speed needed to ensure that Ovation is able to perform all its functions quickly and efficiently.
The Ovation Database has a relationship with other Ovation functions as described below:
Ovation Developer Studio — The Developer Studio provides a package of tools necessary to
build and maintain a process control system. Using the tools available, you can build an entire
system, import information from a previously created database into the Developer Studio, and edit
and update attributes such as network configurations and point information.
Ovation Control Builder — Algorithm and Control Builder default points are created, deleted,
and modified with the Control Builder. Control program instructions and Boolean program
instruction information are created and deleted with the Control Builder. The Load function of the
Ovation Developer Studio is used to load the information to the originating drop(s).
282 OW360_R1005
16.4 What is the organization of the Ovation database?
The Ovation database is based on an Oracle database. For computing environments, such as
Ovation that are connected through networks, Oracle combines the data physically located on
different computers into one logical database that can be accessed by non-controller network
nodes.
You are allowed to change the Oracle passwords. Refer to Ovation Security Manager User
Interface for details.
16.4.1 What is the Ovation Master Database schema?
The information in the Master Database is organized in a set of tables and related functions. This
is called a schema. The Ovation Master Database schema is divided into two major sections: the
user level and the system level.
The user level consists of the following groups of tables (all of which are available for SQL read
access):
 Point tables - represent the user-level attributes of points. They are populated through the
import utility and through the Point Builder and Control Builder.
 Configuration tables - represent the configuration of the system. They are populated through
the import utility, Admin Tool and I/O Builder.
 Reference tables - represent Ovation system constants, hardware module reference
information and Ovation record type information and are populated at the time the database is
created.
 Baseline tables - used to capture baselines of the user-level table contents.
The system level consists of the following groups of tables:
 Ovation-specific tables - represent the process point database in a version/format similar to
the process point fields. Refer to Ovation Record Types Reference Manual.
 Dynamic tables - used by system-level processes to load originating drops and propagate the
Distributed Database.
OW360_R1005 283
16.4.2 What is the Ovation engineering tools audit schema?
This schema consists of tables and functions dedicated to collecting information from the
engineering tools audit function. The audit trail can be maintained and retained during full Ovation
database imports.
 Audit Log tables - contains the actual auditable events
 Audit_Date: This field contains a time/stamp of the event.
 Audit_Level: This field is used to indicate the category or severity of the event.
 Action: This field indicates the specific operation being audited.
 Object_Type: When applicable, this field indicated the type of object being audited.
 Object_Name: This field indicates the name of the object being audited.
 Parameter: During low-level auditing, this item indicates the object's attribute which was
altered.
 Old_Value: During low-level auditing, this item indicates the value of the object's attribute
prior to its modification.
 New_Value: During low-level auditing, this item indicates the value of the object's attribute
after its modification.
 OS_User: This field indicates the user account from which the audited action was
performed.
 Machine: This field indicates the computer name from where the audited action was
performed.
 Data: This text-based field provided additional data for supplemental information as
necessary.
 Configuration table - contains the auditing level currently in effect.
 Audit Archive - Maintains a record of the audit trails which have been archived.
284 OW360_R1005
16.5 Database terminology
16.5 Database terminology
The following terms and descriptions will be helpful to your understanding of the Ovation
database:
Security terms
TERM DEFINITION
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).
Business Rules Layer of software between Ovation applications and the database interface software.
(Ovation)
Distributed Contains a subset of the information stored on the Master Database. A Distributed
Database Database is present on each drop in the system and is continually updated as point
information changes. It contains an updatable system point directory and the MMI data
fields of the process points (ED, SD, RS, and so forth) as well as the other fields not
broadcast as part of a point’s static data.
Distributed Continuously running daemon process on the Server drop which broadcasts, through
Database multicast address, distributed database information to all system drops. It also supports
Propagation a mode whereby clients can receive information by TCP connection if they are
Software significantly out of date.
Export Ovation utility that is run to copy data from the database to a text file.
(OvPtExport)
function
Import Ovation utility that is run to put data into the database. This is done by means of a text
(OvPtImport) file.
function
Load function on Ovation function that is used to transfer data from the Master Database and distribute it
the Ovation to control drops and those drops that originate points.
Developer
Studio
Master Contains the entire process database. It is used for creating, modifying, and verifying
Database 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.
Network Nodes Another term for drops on the Ovation Network.
Oracle Oracle’s utility that is used to put data into the database and to backup the data in the
import/export database. However, this function is used for complete restoration of the entire database
function (structure and contents) following a catastrophic failure (disk crash, operating system
reload, and so forth). This tool is NOT for saving and restoring database contents during
an Ovation software upgrade.
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.
OW360_R1005 285
16.6 What is a point?
CAUTION! Understanding point information is a complex subject. For this reason, this section
provides an overview of points and how they relate to the Developer Studio. More information
about points and record types is described in the Ovation Record Types Reference Manual.
Since correct point configuration is very important to the integrity of your Ovation system, only
knowledgeable personnel should create points.
A point is a record in the global database that contains a value and other related data. 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 (see
page 288). 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
 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
286 OW360_R1005
 Third-party I/O interfaces

 OPC
 Ovation multi-network I/O
Note: Ovation Control Builder-generated points should never be modified in the Studio. These
points are intentionally hidden from the Hardware view. User-defined points should be used if
customization is necessary.
OW360_R1005 287
16.7 What are point records?
16.7 What are point records?
A point record stores the information which defines the attributes of a point (see page 286).
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 start-
up). 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.
288 OW360_R1005
16.8 What is point frequency?
16.8 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.9 Understanding point names
Point names are defined early in the system configuration process by plant personnel and
Emerson project team members. Sometimes, existing point names are imported into a new
Ovation system with some minor enhancements. Other times, point names are created in the
Developer Studio.
Note: Points can also be created in the Control Builder. Refer to the Ovation Control Builder
User Guide for more information.
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 (see page 291) when
they are used in the Ovation Distributed Database.
OW360_R1005 289
16.10 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).
Reserved point name characters
CHARACTER ASCII CHARACTER ASCII CHARACTER ASCII

(IN HEX) (IN HEX) (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

! 21 ? 3F V 56
# 23 A 41 W 57
( 28 B 42 X 58
) 29 C 43 Y 59
+ 2B D 44 Z 5A
290 OW360_R1005

- 2D E 45 [* 5B
/ 2F F 46 ]* 5D
0 30 G 47 ^ 5E
1 31 H 48 _ 5F
2 32 I 49 { 7B
3 33 J 4A | 7C
4 34 K 4B } 7D
5 35 L 4C
6 36 M 4D
7 37 N 4E
8 38 O 4F
9 39 P 50
:* 3A Q 51
; 3B R 52
<* 3C S 53
= 3D T 54
>* 3E U 55
* Emerson recommends that you do not use these characters in point names since they may cause
confusion on control sheets.
OW360_R1005 291
16.11 Using fully qualified point names
16.11 Using full y qualified point names
A fully qualified point name in the Ovation system uses the following format:
“name.unit@network”
This format consists of three parameters:

 A 24-character maximum point name.
 A six-character maximum unit name.
 An eight-character maximum network name.
The “.” and “@” are required and are reserved characters. They are part of a fully qualified point
name, but are not allowed in the name portion of the fully qualified point name. Therefore, the
maximum number of characters in a fully qualified point name is 40.
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.
In a multiple network implementation, the network name segment must be one of the following:
 Actual name of the local or remote network.
 Any of the defined network aliases (the alias for the remote or local network).
Note: For more information about multiple networks, refer to the Ovation Multiple Networks User
Guide.
16.12 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 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 Emerson internal tool 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.
292 OW360_R1005
16.12 Creating the Ovation Database
16.12.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
OvPtImport Imports data from a text file into a Master Database. Can be used to
(Ovation Tool) 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 Exports data from the Master Database and produces a text file. This file
(Ovation Tool) does not contain SIDs or a point's network interface information.
imp Can be used to restore a database after a catastrophic failure (such as a
(Oracle Tool) disk crash). Operates on the binary file produced by exp. Not
recommended.
exp Can be used to backup a system. Produces a binary file.
(Oracle Tool)
OW360_R1005 293
S E C T I O N 17
17 Planning software installation for Windows-based

Ovation systems
IN THIS SECTION
What is involved in the Ovation installation process? ..................................................... 296

Software installation terminology .................................................................................... 296
Understanding disk storage ............................................................................................ 298
Best practices for installing Ovation 3.6.0 software ........................................................ 300
Hardware requirements for Domain Controllers (primary or redundant) ........................ 301
Hardware requirements for a domain member that is a Database Server ..................... 301
Software requirements for a Domain Controller (primary or redundant) ......................... 302
Software requirements for a domain member ................................................................. 302
Licensing requirements for an Ovation Windows-based system .................................... 303
Hardware requirements for a domain member that is NOT a Database Server ............. 304
What is the drop type? .................................................................................................... 304
What is the Ovation Remote Station? ............................................................................. 305
OW360_R1005 295
17.1 What is involved in the Ovation installation process?
17.1 What is involved in the Ovation installation process?
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.
The purpose of this manual is to discuss the initial installation and configuration of an Ovation
3.6.0 system.
Installing and maintaining an Ovation system consists of several operations, including the
following:
 Understanding the domain concept.
 Creating a domain for your system by defining the drop that functions as the Primary Domain
Controller. All other drops in the system function as domain members or as Redundant
Domain Controllers.
 Installing the appropriate Windows operating system on the drops. The correct operating
system version depends on the machine's domain role and drop type.
 Installing the Ovation software.
 Defining the appropriate drop type for each drop.
 Planning security for your Ovation system.
 Providing a reliable method to back up and restore your Ovation system.
The Ovation software is provided on a DVD.
Note: Typically, your computer is pre-configured and set up by Emerson. Computers not pre-
configured may contain software that is not validated by Emerson. Computers with non-
validated software must have the hard disks reformatted. Microsoft Windows must then be
reinstalled from your software DVD.
17.2 Softw are installation terminology
The following terms and descriptions may be helpful while using this manual.
Software installation terms
TERM DESCRIPTION
Active Directory (AD) Component of Microsoft Windows Operating System. Provides a method to
Database securely manage the identities and relationships in a domain. Computer names
are identified here.
Additional or This drop (hereafter referred to as redundant) mirrors the security information in
Redundant Domain the Primary Domain Controller and performs Windows/domain security functions
Controller if the Primary Domain Controller fails.
Backup and Recovery System Backup and Recovery (SBR) software is an optional backup solution that
is offered on all Ovation 3.5 and later systems.
Backup and Restore The Ovation Backup and Restore software OvPtBackup is a standard Ovation
backup software.
296 OW360_R1005
17.2 Software installation terminology
TERM DESCRIPTION
Domain Logical collection on a network of computers and users that shares a common
security database.
Domain Administrator User in a domain who can install Ovation software in addition to performing
standard Windows administrative tasks. By default, the Administrator has these
privileges.
Domain Member Computer in a domain that is not a Domain Controller but responds to the
Domain Controller computer.
Domain Name Distributed database that uses a hierarchical naming system. Creates user-
System (DNS) friendly unique names for computers (such as drop200) and locates computers
on a network.
DNS Server Computer that can answer Domain Name System (DNS) queries.
Forest Collection of Trees that represent the outermost boundary within which users,
computers, groups, and other objects exist. The forest is the security boundary
for Active Directory.
FSMO Flexible Single Master Operation (FSMO). A feature of Microsoft's Active
Directory (AD) and is a specialized Domain Controller (DC) set of tasks.
Fully Qualified Address name of a computer using DNS. Recommended format is:
Domain Name
(FQDN) <unique name>.Ovation.<company name>.local
IP Address Unique number consisting of four parts (known as tuples) separated by dots. An
example of an IP address is 129.228.36.38. Each computer that is on the
Internet has a unique IP address.
Local Administrator User in a domain who, by default, exists on a domain member computer and has
administrative privileges only on that computer. For example, a local
administrator cannot install Ovation.
Netmask The netmask (also known as an address mask) is a number that identifies the
range of IP addresses that are on a local network. The netmask serves as a filter
that enables a computer to determine whether it can transfer data directly to
another machine on the local network or if the computer must use a router to
transfer data.
Ovation Administrator User who has the authority to manage and configure the security for the Ovation
system.
Ovation Database Computer on a network that contains the Oracle relational database. Most of the
Server (DBS) Ovation system data, including control information, configuration information, and
process point information, are stored on the Database Server.
Preferred DNS Server DNS Server in the same site as the computer you are configuring. Designated as
"preferred" in a domain.
Primary Domain Server in a domain that contains the security database for a network and controls
Controller the access to network security resources. This drop must be the first drop
configured in a domain.
A Primary Domain Controller can control security for separate Ovation systems.
Remote Desktop on Provides access to a Windows session that is running on a computer when you
Windows are at another computer. For example, you can connect to an Ovation computer
from home and have access to your Ovation applications, files, and resources as
though you were in front of the computer at work.
OW360_R1005 297
17.3 Understanding disk storage
TERM DESCRIPTION
Round Robin Technique for balancing the load between servers that perform the same
functions on the internet.
Security Manager Software that runs on all Ovation drops and receives security configuration
Client settings from the security database in the Domain Controller.
Security Server (OSS) Software that runs on the Primary Domain Controller and communicates security
configuration settings from the security database to the Ovation drops.
Terminal Services Microsoft software that provides multiple remote desktop connections. Windows
Server 2008 R2 operating systems must be used to run this service. Special
licenses are required from Microsoft.
Tombstone Lifetime The number of days before a deleted object is removed from the directory
services.
Tree A Tree consists of a single domain or multiple domains in a contiguous
namespace. A forest is a collection of Trees.
Emerson provides drops with two different types of storage options:

 Redundant Array of Independent Disks (RAID) is a data storage technology that combines
multiple disk drive components in a logical unit. Data is distributed across the drives in one of
several ways called "RAID levels," depending on the level of redundancy and performance
required.
RAID encompasses various data storage schemes that can divide and replicate data among
multiple physical drives. The different schemes or architectures are named by the word RAID
followed by a number (for example, RAID 0, RAID 1, and so forth). Each scheme provides a
different balance between reliability, availability, performance, and capacity.
Note: Ovation Process Historian (OPH) server drops use RAID 5 technology. For more
information on RAID 5 and the OPH, refer to the applicable Ovation Process Historian User
Guide.
If you choose RAID technology, Emerson offers RAID 1 for use with the Ovation Database
Server. Emerson's offering of RAID 1 consists of four physical disks that are configured as
two RAID 1 volumes, also referred to as Virtual Disks by the RAID controller.
 Regular, physical hard disks come from the manufacturer of the machine. For Database
Servers, you must have at least two physical hard disks. However, all Domain Controllers are
also configured with a minimum of two disks as well.
298 OW360_R1005
17.3.1 Disk partitioning
Typically, disk partitioning is performed before you receive your Ovation system from Emerson.
Emerson ensures that your machines are properly configured and have enough disk storage to
properly install and run the operating system and Ovation software. However, if, for any reason,
you have a need to revisit your disk configuration (such as during a reload of the operating
system, first-time setup of unconfigured hardware, or recovering from a hardware failure), use the
following rules:
 If you are using RAID 1 disk storage technology (see page 298), and your drop has four
physical hard disks, you must first ensure that they are assigned as two separate RAID 1
Virtual Disks. This step typically requires verification of the configuration in the system’s RAID
BIOS, which is accessible during the boot process. You must then partition and assign the
entire capacity of the first RAID 1 Virtual Disk to be drive letter C: and the entire capacity of
the second RAID 1 Virtual Disk to be drive letter D: during the course of Windows installation
and configuration.
 If you are not using RAID 1 storage, and your drop has two physical hard disks, you must
first ensure that they are assigned as two RAID 0 Virtual Disks, with each Virtual Disk
assigned just a single physical hard disk. OEM factory configuration of such systems prior to
Emerson configuration may default to an undesired configuration consisting of a single RAID
0 Virtual Disk assigned with both physical hard disks. This type of configuration would leave
the machine less fault tolerant and not achieve the desired configuration for optimal
performance. Use the system's RAID BIOS to verify and configure this. You must then
partition and assign the entire capacity of the first Virtual Disk to be drive letter C: and then
partition and assign the entire capacity of the second Virtual Disk to be drive letter D:.
 If the machine only has one hard disk (such as for Operator Stations and Base Stations), you
must partition and assign the disk to be drive letter C:. The C: partition should contain the
entire capacity of the hard disk.
Note: Assigning the disks or disk volumes to something other than C: and D: may result in
improper placement of certain software elements during installation.
 Regardless of the type or number of disks on a machine, ensure that you have at least 80GB
of free disk space on the system partition (C:).
 For Domain Controllers, ensure that you have at least 30GB of free disk space on a non-
system partition in order to perform any type of system backup. For example, if Windows is
installed on C:, then 30GB of space must be allocated on D: for backup purposes.
 For Remote Stations, ensure you have at least 30GB of free disk space on a non-system
partition in order to perform any type of system backup. For example, if Windows is installed
on C:\ and OPH Scanner software is installed on D:\, then 30GB of space must be allocated
on E:\ (or another drive) for backup purposes.
All hard disks must use the NTFS file system. Due to the possibility of various disk partitioning
scenarios, it is recommended that you contact your Emerson representative if you have questions
about partitioning your disks.
OW360_R1005 299
17.4 Best practices for installing Ovation 3.6.0 software
17.4 Best practices for installing Ovation 3.6.0 softw are
For best results, use the following rules when installing your Ovation system:
 You must have a Primary Domain Controller on every Ovation system that is Ovation release
2.4 or later.
 Make sure that the disks have been partitioned (see page 299) with adequate free disk space
on each drive.
 Create the Primary Domain Controller for your system before you create any other drops
(including Redundant Domain Controllers).
 The first software installation in a new system should be the installation of Windows Server
2012 R2 Standard Edition - English version - 64-bit 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.
 You may define a Redundant Domain Controller to be an Ovation Operator Station, an
Ovation Base Station, or a Database Server.
 Regardless of the domain role, Database Servers must run Windows Server 2012 R2
Standard Edition - English version - 64-bit.
 Ovation Security Servers must be run on either Windows Server 2008 R2 Standard Edition
SP1 English version 64-bit or Windows Server 2012 R2 Standard Edition English version 64-
bit.
 Workstation drops (Operator Stations or Base Stations) can use any of the allowable
operating systems for Ovation 3.6.
 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.
Note: The Database Server on an Ovation 3.6 or later system MUST reside on a server class
machine loaded with the Windows Server 2012 R2 standard (64-bit) operating system.
300 OW360_R1005
17.5 Hardware requirements for Domain Controllers (primary or redundant)
17.5 Hardw are requirements for Domain Controllers (primary or

redundant)
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 serves as a Domain
Controller:
 Standard Intel Pentium computer with a minimum processor speed of 2GHz (primary or
redundant).
 At least 1 GB of RAM for an Ovation Security Server (only Primary Domain Controllers can be
Ovation Security Servers).
 At least 2 GB of RAM for a Domain Controller (primary or redundant) that is also a Database
Server.
 At least 2 GB of free disk space for an Ovation Security Server (only Primary Domain
Controllers can be Ovation Security Servers).
 At least 25 GB of free disk space if a Domain Controller (primary or redundant) is also a
Database Server.
 A DVD drive.
 At least two physical hard disks for Domain Controllers (primary or redundant) that are
Database Servers.
17.6 Hardw are requirements for a domain member that is a Database

Server
The following minimum requirements are needed for a computer that is a Database Server, but
whose domain role is that of 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 two physical hard disks.
OW360_R1005 301
17.7 Software requirements for a Domain Controller (primary or redundant)
17.7 Softw are requirements for a Domain Controller (primary or

redundant)
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. This is an optional, but recommended, practice.
The following minimum requirements apply to a computer that serves as a primary or redundant
Domain Controller in Ovation 3.6.0 systems:
 Windows Server 2008 R2 Standard Edition - English version - 64-bit (with Service Pack 1).
 Windows Server 2012 R2 Standard Edition - English version - 64-bit.
 Computer must be promoted to a Primary or Redundant Domain Controller.
 Domain naming service (DNS) installed.
Note: Database Servers configured as Primary Domain Controllers MUST run Windows Server
2012 R2. See Supported Ovation 3.6 operating systems based on domain role and drop type for
more information.
17.8 Softw are requirements for a domain member
Any computer in a domain that is not a Domain Controller (primary or redundant) is considered to
be a domain member.
The following requirements apply to a computer that is a domain member in an Ovation 3.6.0
system:
 The computer must use one of the following operating systems:
 Windows 7 Professional Edition - 64-bit (with Service Pack 1).
 Windows 10 IoT Enterprise 2016 LTSB.
 Windows Server 2008 R2 Standard Edition - English version - 64-bit (with Service
Pack 1).
 Windows Server 2012 R2 Standard Edition - English version - 64-bit.
 If the computer will not be a Database Server, it must use Windows 7 SP1 Professional (64-
bit) or Windows 10 IoT Enterprise 2016 LTSB.
 If the computer will be a Database Server, it must run Windows Server 2012 R2 Standard
Edition.
Note: Typically, your computer is pre-configured and set up by Emerson. Computers not pre-
configured may contain software that is not validated by Emerson. Computers with non-
validated software must have the hard disks reformatted. Microsoft Windows must then be
reinstalled from your software CD.
302 OW360_R1005
17.9 Licensing requirements for an Ovation Windows-based system
17.9 Licensing requirements for an Ovation Window s -based system
Plan your software installation or upgrade to ensure that you 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 are provided in your Software and Licensing Kit binder. 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 that 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.
OW360_R1005 303
17.10 Hardware requirements for a domain member that is NOT a Database Server
17.10 Hardw are requirements fo r a domain member that is NOT a

Database Server
The following minimum requirements are needed for a computer that serves as a domain
member, but is not a Database Server:
 Standard Intel Pentium computer with a minimum processor speed of 2 GHz.
 At least 512 MB of RAM for a domain member.
 At least 2 GB of free disk space for a domain member.
 A DVD drive.
17.11 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 is installed and how it is configured. This choice is made
during the Ovation installation process.
 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 drop 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.
304 OW360_R1005
17.12 What is the Ovation Remote Station?
The Ovation Remote Station was designed for facilities that have limited space or that have
several remote locations.
For example, a facility could have one or two control centers and several remote sites. On every
remote site, a separate Ovation system must be installed; however, there is limited space at the
remote site for the equipment.
The Ovation Remote Station Solution solves this issue by allowing multiple Ovation applications
to run on one physical machine. This machine is controlled from a control center that may be
several miles away. A Wide Area Network (WAN) is used to connect the Ovation Remote Station
machine(s) at the remote sites to the central control room. For this reason, it is important to make
sure there is enough bandwidth to handle network traffic between these locations.
The Remote Station machines can be used in places where extreme temperature conditions
exist. Hardened Remote Station machines may be placed in areas that do not have an air
conditioned enclosed space. Non-hardened Remote Station machines are installed in air
conditioned areas.
Note: The Ovation Remote Station does not require special or additional Ovation security.
Standard Ovation security is used.
17.12.1 Supported Ovation applications
The following Ovation applications can be installed on a single Remote Station machine. Note
that you can install as many of these applications as desired on a single machine.
 Ovation Database Server.
 Ovation Virtual Controller Host.
 Ovation Virtual Controller (only one).
 Ovation Process Historian Scanner.
 SCADA Server.
 APC Toolkit.
 Kaspersky anti-virus software (managed externally).
 EDS Feeder.
 OPC Server.
 Domain Controller.
 Patch management agent (OSC).
 White listing agent (OSC).
 Data Server.
 System Backup and Recovery agent.
Note: The use of "agents" or the EDS Feeder implies the requirement of a server or
management station in a control room to manage the agent stations.
Each of the supported Ovation applications is discussed in other Ovation user manuals. These
manuals can be obtained from the Ovation Users website or from your Emerson customer service
representative. Therefore, it is beyond the scope of this document to describe the installation and
use of these individual Ovation applications.
OW360_R1005 305
17.12.2 Hardware requirements for a Remote Station drop
For environments that require hardened equipment, the Ovation Remote Station Solution resides
on a SEL 3355 machine, manufactured by Schweitzer Engineering Laboratories, Inc.
The SEL 3355 is used since it can be configured with a wide range of power supplies for multiple
applications in different environments without external inverters.
For Ovation Remote Station drops that will reside in non-hardened environments, use the
machine that is designated as the currently supported hardware for an Ovation Database Server.
306 OW360_R1005
S E C T I O N 18
18 Planning control for your Ovation system
IN THIS SECTION
What is Ovation control? ................................................................................................. 308

What types of control are supported in Ovation? ............................................................ 309
What is the Ovation Control Builder? .............................................................................. 310
What is the role of the Control Builder in Ovation? ......................................................... 311
What is the control planning process? ............................................................................ 311
Using diagrams in planning control ................................................................................. 312
What is storyboarding for control? .................................................................................. 314
What are Ovation control functions (control sheets)? ..................................................... 315
Planning for system expansion ....................................................................................... 316
Control Builder terminology ............................................................................................. 316
What is the scope of your control project? ...................................................................... 319
What are the best practices for planning control? ........................................................... 319
What are the best practices for designing control? ......................................................... 321
What are the best practices for building control sheets? ................................................ 322
What are other control products? .................................................................................... 322
OW360_R1005 307
18.1 What is Ovation control?
18.1 What is Ovation control?
An Ovation control system is an advanced process control system that controls industrial plant
processes. Ovation control systems are typically used by utility companies and waste water
companies to control the entire processes of the plant in real time with accurate precision.
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. Therefore, developing control sheets should only be
performed by experienced personnel.
The devices in the plant monitor processes and make 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 control cabinet that contains Input and Output modules
that connect to the field devices, usually by wires. These modules monitor each device for any
change in the device’s 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.
308 OW360_R1005
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.
OW360_R1005 309
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.
Figure 83: Control Builder main window
310 OW360_R1005
18.4 What is the role of the Control Builder in Ovation?
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.
18.4 What is the role of the Control Builder in Ovation?
The Control Builder creates the control logic that runs in the Ovation Controller. In addition to
editing the control sheets containing the logic, the Control Builder facilitates the integration of the
logic into the Controller.
The logic that is created and edited by the Control Builder affects the Ovation database since the
database is modified to reflect the logic changes.
The actual editing by the Control Builder is done at an Ovation Engineering Station. Here, control
sheets, which are SAMA drawings, are created and edited by a control design engineer. These
sheets contain the various algorithms that are used in the control designs.
The drawings that are created at the Engineering Station can be displayed at an Operator Station
through signal diagrams. Here, an Operator can monitor the systems that are displayed and
perform certain tuning functions.
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.
OW360_R1005 311
18.6 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).
312 OW360_R1005
18.6.1 What are piping and instrumentation diagrams (P&ID)?
Planning control typically begins when the plant provides P&ID (Piping and Instrumentation
Diagrams) drawings to the engineering staff that will be creating the control. These diagrams are
actual drawings of all the proposed functions in the plant that must be controlled by the control
system.
Sometimes a plant may only provide Process Narratives, which are text files that describe in
detail what plant processes need to be implemented and monitored. If there are no P&ID
drawings, Emerson uses the Narratives to create the control schemes.
Along with the P&ID drawings, the plant also provides the database that will be used to identify all
the elements in the system that need to be managed by the Ovation control system. This
database might be in the form of a text file, a DBASE file, or spreadsheets. After the elements on
the P&ID drawings are matched to the database point names, then control design can be started.
The following figure is an example of a section of a P&ID drawing.
Figure 84: Example of P&ID drawing
18.6.2 What are oil diagrams?
Oil diagrams, contain locations of inputs and outputs and other process information for the piece
of equipment being controlled.
Plants often use machinery that must be controlled and managed through a process control
system. This machinery may be equipment such as turbines, grinding mills, pumps and valves.
Some of these products provide diagrams or schematics that can be used to help determine the
requirements for the control process. These diagrams, often referred to as Oil diagrams.
The control design engineer can combine the P&ID diagrams with the Oil diagrams in order to
visualize and better understand the control requirements for the system equipment.
OW360_R1005 313
18.7 What is storyboarding for control?
18.6.3 What are plant process schematics?
Many types of schematics are created for the processes of a plant. These drawings are used by
the control engineers to plan the control schemes that are represented by the associated
processes. Some of these schematics are the electrical drawings and the Control Wiring
Drawings. Different processes may require additional types of schematics.
The following figure is an example of a section of a schematic drawing.
Figure 85: Example of schematic drawing
18.7 What is storyboarding for control?
Storyboarding (also known as block diagramming or modeling) is commonly done in many

industries, such as advertising, films, literature, and construction. It can also be used in designing
process control. Storyboarding provides a visual method of illustrating a process without the
actual creation of the process. It is during this process that potential mistakes can be identified
and easily corrected.
Storyboarding the control is the practice of designing the control before you create the control
sheets. Each control design engineer has his own approach to storyboarding. Some use sticky
notes, some use paper and pencil, and some use a software package. Whatever is most
comfortable for you is the approach that is best for you.
Some of the concepts that can be illustrated through storyboarding are listed below:
 Determine what types of user interfaces are desired:
 Setpoint control.
 Off/On choices.
 Auto/Manual selection.
314 OW360_R1005
18.8 What are Ovation control functions (control sheets)?
 Segment the various control functions:

 Separate self-contained control functions.
 Minimize off-page functions.
 Block out the algorithms that will be used:
 Analog and digital algorithms.
 Analog and digital algorithms can be mixed on a sheet.
 Logically group functions (for example, put all the temperature logic on a sheet).
 Analog signals flow top to bottom.
 Digital signals flow left to right.
 Layout the sheets:
 Allow room for descriptions for top and bottom 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 that is used in a specific Controller drop.
18.8 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.
OW360_R1005 315
18.9 Planning for system expansion
18.9 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.
18.10 Control Builder terminology
The following terms and descriptions are associated to Ovation control systems and may help you
understand the Ovation Control Builder.
Control Builder terminology
TERM DESCRIPTION
Algorithms Set of rules, procedures, and mathematical formulas that define a control strategy.
For more information, refer to the applicable Ovation Standard Algorithms Reference
Manual or Ovation Q-Line and Specialty 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 Performs same operation on multiple control sheets.

Run Scripts
316 OW360_R1005
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 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.
(also known as Set
or Area) 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 User- OCBssssaaa-pppp, where:
Defined Points)
ssss = Unique sheet identifier (Hex)
aaa = Unique algorithm identifier (Hex)
pppp = Parameter mnemonic (for example, OUT)
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.
OW360_R1005 317
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 When Control information between a pair of redundant Controllers is different.
Mismatch
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 A set of components that includes sensors, Logic Solvers, and final control elements
System (SIS) 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 Any documents that do not have control associated with them. There is no algorithm
Documents 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).
318 OW360_R1005
18.11 What is the scope of your control project?
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.11 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.
OW360_R1005 319
18.12 What are the best practices for planning control?
18.12 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.
 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 wherever 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.
320 OW360_R1005
18.13 What are the best practices for designing control?
18.13 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 a few 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 about 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.
 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.
OW360_R1005 321
18.14 What are the best practices for building control sheets?
18.14 What are the best practices for building control sheets?
Refer to the following practices when building control sheets:

 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 multiple 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.
Note: If you come across a document that is password protected, contact your Emerson
representative for more information.
18.15 What are other control products?
The another control products are as follows:

 Advanced Process Control (APC) ToolKit: The Ovation system comes bundled with a
standard algorithm set for the Ovation Controller. Algorithms streamline and simplify plant
processes by using sets of rules and mathematical formulas to define the control strategy of a
plant.
The Advanced Process Control (APC) ToolKit is an extension to the Ovation system that
allows advanced algorithms to be added to an Ovation Advanced Controller. It allows you to
build more powerful control strategies, tighter control, more efficient operation, and systematic
approaches to handling control. The APC ToolKit provides the means to support these
advanced algorithms that extend the Ovation control capability beyond the standard algorithm
set. This collection of advanced algorithms was developed to simplify engineering and
programming of complex mathematical, modeling, or optimization functions in the Ovation
system.
For more information about the Advanced Process Control (APC) ToolKit, refer to the
applicable APC Toolkit User Guide.
 Intelligent Sootblower:The Intelligent Sootblower is a web-enabled tool that allows the user
to significantly reduce the drawbacks of fixed soot blowing through consistent, balanced soot
blowing sequences. The Intelligent Sootblower has the capability to calculate the cleanliness
factors of the soot blowing process.
The Intelligent Sootblower uses a dynamic modeling tool to develop boiler section heat
absorption models that reflect the relationships of heat transfer sections throughout the boiler.
After a model is created, the Intelligent Sootblower delivers sequenced soot blowing control to
ensure that soot is blown when advised for in the required locations.
322 OW360_R1005
18.15 What are other control products?
The function of intelligent soot blowing is to determine what blower(s) require activation on a
specified schedule in order to remove fouling on boiler surfaces. Intelligent soot blowing will
make decisions based on plant measurements assisting operators or, when in control mode,
will execute pre-programmed blowing. Intelligent soot blowing enables automated soot blower
controls to measure, calculate, and operate the entire soot blowing process to maximize
boiler efficiency and minimize additional maintenance costs.
Slagged areas can be identified and cleaned so that only affected areas of the boiler are
blown. This approach conserves resources, reduces the required number of soot blower
operations, and ensures that the boiler surfaces are not over-blown. The optimum soot
blowing strategy can achieve reductions in NOx, limit the steam temperature, and keep heat
rate impacts at manageable levels.
For more information about the Intelligent Sootblower, refer to the Intelligent Sootblower User
Guide.
 Economic Optimizer: The Economic Optimizer is a general purpose solver for linear and
nonlinear optimization problems. Some possible applications are:
 Economic dispatch of combined cycle plants.
 Economic dispatch of industrial captive and co-generation plants.
 Economic dispatch of hydro turbines.
 Economic dispatch of water pumps in waste water or water treatment plants.
 Fuel blending optimization.
 Fleet-wide economic dispatch.
 Cooling tower optimization.
The Optimizer communicates with the distributed process control system through OLE for
Process Control (OPC). The Optimizer allows you to build complex optimization problems to
help you find a solution that satisfies a set of constraints to minimize or maximize an
objective function. The Optimizer contains a set of algorithms that provide the user with the
capability to solve linear, quadratic, nonlinear, non-smooth optimization problems, and mixed-
integer problems of varying size. The Optimizer can handle problems of up to 16,384
variables and 16,384 constraints.
For more information about the Economic Optimizer, refer to the SmartProcess Optimizer
Manual.
OW360_R1005 323
S E C T I O N 19
19 Planning your Ovation Controller
IN THIS SECTION
What is the Ovation Controller? ...................................................................................... 326

Ovation Controller I/O interfaces ..................................................................................... 327
OW360_R1005 325
Table of Contents
19.1 What is the O vation 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. (Refer to Q-Line Installation Manual, Ovation I/O Reference Manual,
and Ovation Bus and Specialty 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.
Refer to the Ovation Control Builder User Guide.
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 86: Ovation Controller
326 OW360_R1005
Table of Contents
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 Ovation Controller I/O interfaces
Ovation Controllers provide various types of interfaces to communicate with the Ovation system
and other devices. These interfaces include:
 Ovation network
 Dedicated backup
 I/O devices
19.2.1 Network Interface ports
The OCR1100 Ovation Controller has the following NIC port options:
 G01 - Four RJ45 connections.
 G02 - One RJ45 and three SFP Fiber connections.
 G03 - Four RJ45 connections.
 G04 (applicable to OCR 1100 only) - Four RJ45 connections.
The Ovation 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.
Network interface ports
PORT SUPPORTS
N1 Used for third-party devices. This is an additional Ethernet interface for other uses, such as
third-party links, if necessary.
N2 Typically used for single attached networking to the Ovation network.
N3 Provides an additional Ethernet interface for dual attached networking.
N4 This is the default Ethernet interface for dedicated control synchronization or third-party device.
OW360_R1005 327
Table of Contents
PORT SUPPORTS
Note: When using direct connection (Port N4 to N4) control synchronization, make sure 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.
Note:
OCR400 Controllers are available in the following two groups:
G01 (64MB) implements N1, N2, N3, and N4 as the RJ-45 connectors.
G02 (128 MB) implements N1, N2, N3, and N4 as the RJ-45 connectors.
OCR1100 Controllers are available in the following four groups:
G02 (256 MB) implements N1, N2, and N3 as the Small Form Factor Pluggable (SFP)
transceivers and N4 as a RJ-45 connector.
Only approved SFPs can be installed in the OCR1100 G02. Approved SFPs are listed in the
following Ovation drawing - 1X00832.
328 OW360_R1005
Table of Contents
19.2.2 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.
(Refer to 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.)
OW360_R1005 329
Table of Contents
19.2.3 Small Form-factor Pluggable Transceivers (SFPs)?
Small Form-factor Pluggable Transceivers (SFPs) are compact pluggable transceivers used for
telecommunication and data communications. SFPs are used on the G02 OCR1100 Controller.
SFPs are inserted into designated Ethernet ports on the OCR1100 Controller.
There are 3 SFP Ethernet ports on the G02 OCR1100 Controller and one copper RJ45 port, this
Controller option has a temperature rating of 0-50 deg. C or 32-122 deg. F.
Currently, there are three approved SFPs. Refer to the Ovation drawing - 1X00832 for additional
information on approved SFPs.
Note: Use of non-approved SFPs is not permitted on the Ovation system.
The OCR1100 G02 Controller ports are protected by factory installed dust covers. Dust covers
are removed prior to usage.
Replacement dust covers can be ordered as a separate item using the following part numbers:
 SFP dust cover - 1X00828H04
 RJ45 dust cover - 5A26371H95
330 OW360_R1005
S E C T I O N 20
20 Planning Simulation
IN THIS SECTION
What is Scenario simulation? .......................................................................................... 331

Scenario simulation model for high fidelity simulators .................................................... 333
Tie-back simulation model .............................................................................................. 334
20.1 What is Scenario simulation?

Scenario simulation is a software package designed to provide an interface between a software
model of a plant and an Ovation Control System on an Ovation network. The interface is
accomplished by simulating the I/O for the Ovation Controllers across the network. This is
accomplished by the SP field in analog, digital, and packed points. Refer to the Ovation Record
Types Reference Manual for more information.
Simulators for the Ovation 3.1 software release and later include bus technologies as well as
provide simulation over multi-network systems.
The Scenario simulation software package is valuable for several reasons. Two primary benefits
are:
 To maximize plant efficiency by testing I/O logic before it is used in a real plant application.
 To provide hands-on personnel training without interrupting the operation of the plant.
20.1.1 What are the Simulation components?
The Scenario Simulation software package incorporates the following main components:
 SimController — Standard Ovation Controller or Virtual Controller loaded with Simulator
software in addition to the normal plant database and control software. SimControllers
interface to the Sim Operator Station to access the I/O. All Controllers that are to participate in
the simulation should be configured as SimControllers.
 Sim Operator Station — Ovation Operator Station configured with Simulator software.
 Model — Imitates how an actual plant would respond to the outputs of the SimControllers.
You can choose either the High Fidelity or Tie-back options.
 Simulator Translation File — User-defined file that contains a list of points that map a point
in the SimController to a point in the Model.
 SIMAPI — Transfers data between Models, Sim Operator Stations, and SimControllers via
Application Programming Interface (API) calls.
OW360_R1005 331
20.1 What is Scenario simulation?
20.1.2 What is the Simulation process?
The Sim Operator Station uses the Simulator Translation File to map the simulated plant process
point to an input point normally read by the plant control via physical I/O. The Sim Operator
Station then sends the I/O point over the network back to the SimController. The SimControllers
read the inputs coming from the Sim Operator Station, rather than actually reading the physical
I/O to receive the signal.
An output point in the plant control loaded in a SimController is sent out over the network rather
than being sent to the physical I/O. That value is then used in the Model (located in a dedicated
SimController) as a receive point. The Model simulates plant response to the control signals and
generates simulated plant process points. The simulated plant process point is then sent over the
network to the Sim Operator Station.
Ovation high-fidelity and low-fidelity simulators are both configured using exact plant control
hardware and software. The main difference between the two options is the method used to
simulate plant processes. Ovation high-fidelity simulators use mathematical models, while low-
fidelity simulators use simulation logic to emulate plant processes.
332 OW360_R1005
20.2 Scenario simulation model for high fidelity simulators
20.2 Scenario simulation model for high fidelity simulators
Simulation models can either be from an Ovation or a high-fidelity mathematical model. A third-
party model interfaces with the Sim Operator Station software to transfer data from the Sim
Operator Station into the Model. For purposes here, the tie-back model is assumed throughout
the manual.
The following figure shows the data flow for the Scenario simulation system.
Figure 87: Ovation simulator data flow for high-fidelity
OW360_R1005 333
20.3 Tie-back simulation model
20.3 Tie-back simulation model
The following diagram illustrates the data flow for tie-back simulation.
Figure 88: Ovation Simulator data flow for tie-back
334 OW360_R1005
S E C T I O N 21
21 Planning Virtual Controllers
IN THIS SECTION
What is Ovation Virtual Controller simulation? ................................................................ 335

What is an Ovation Virtual Controller? ............................................................................ 338
What is an Ovation Virtual Controller Host? ................................................................... 338
What are the Virtual Controller commands? ................................................................... 339
What is the operation of the Virtual Controller? .............................................................. 340
What is the Virtual Controller Manager window? ............................................................ 341
Virtual Controller terminology .......................................................................................... 341
What are the architecture types of Ovation Virtual Controllers? ..................................... 342
What are the requirements for Ovation Virtual Controllers? ........................................... 345
What are the hardware requirements for the Ovation Virtual Controller host? ............... 345
What are the software requirements for the Ovation Virtual Controller host? ................ 345
What are the Virtual Controller license types? ................................................................ 346
21.1 What is Ovation Virtual Controller simulation?
Ovation Virtual Controller simulation is a simulation of an actual Ovation Control system, except
that Virtual Controllers do not have actual plant control capabilities. Essentially, an Ovation Virtual
Controller is an Ovation Controller within a software package.
The Ovation Virtual Controller simulates the processes of your plant's control system. Virtual
Controllers emulate plant conditions with full modeling capabilities but with less hardware
requirements than standard Ovation control systems.
Ovation Virtual Controllers operate within a Windows operating system under the Wind River
VxWorks simulator. Virtual Controllers perform identically to actual Ovation Controllers. The
difference between the operation of actual Ovation Controllers and Virtual Controllers is that
Virtual Controllers do not have I/O interface capability; therefore, they cannot connect and
perform actual control functions.
Simulation of advanced control systems plays an important role in reducing time, cost, and risk in
plant operations. Since Ovation Virtual Controllers provide an exact simulation of your Ovation
control system, they allow operators and engineers to evaluate and analyze plant conditions
without interrupting the day-to-day operation of the plant.
OW360_R1005 335
21.1.1 Who uses Virtual Controller technology?
Virtual Controller technology can be used by any Ovation control system user. The use of Ovation
Virtual Controllers on your control system depends on how you would like to apply virtual
technology.
As a control system operator, you need to know what to expect when operating your Ovation
control system and how to react to conditions and situations as they occur. Every Ovation
simulated system with Virtual Controllers is designed to imitate your plant control system and
provide operators and technicians with an opportunity to learn how to react to problems if they
arise.
Virtual Controllers can be used in various ways. For example, Emerson uses Virtual Controllers to
build simulator systems, plant modeling, operator training, event handling, and proof testing of
new control schemes and control strategies. You may also want to use your Virtual Controllers for
the same type of applications, or you may choose to design your own custom strategies for your
control system. Typically, the following plant personnel use Virtual Controllers:
 Plant technicians
Virtual Controllers provide many advantages for technicians during system testing and
startup. Using Virtual Controllers minimizes the amount of down time plant technicians
experience during system changes and system set up. In addition, technicians gain
knowledge and experience of how Ovation control systems operate.
 Control system operators
Control room operators use Virtual Controllers to become more familiar with the Ovation
System and gain confidence and understanding of the function of an Ovation system.
 Plant engineers
Plant engineers use simulator systems with Virtual Controllers to test and verify
engineering upgrades and to help plan future changes. Engineers also use Virtual
Controllers for analysis of plant operations.
Virtual Controllers provide an exact imitation of the plant control system, allowing
engineers to use Virtual Controllers to evaluate almost any aspect of the control system
and plant performance. Engineers can test control strategies on Virtual Controllers prior
to actual implementation.
 Trainers
Instructors use Virtual Controller simulation in training programs to improve the skills of
operators, engineers, and technicians by simulating plant conditions. The experience
gained through training helps reduce start time and minimizes operator error.
336 OW360_R1005
21.1.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 affect 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 before they begin actual plant control.
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 allow you to 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.
Ovation Virtual Controllers are designed for the following reasons:

 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.
OW360_R1005 337
21.2 What is an Ovation Virtual Controller?
21.2 What is an Ovation Virtual Controller?
An Ovation 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 actually connect to
the plant I/O. A Virtual Controller replicates the operation of an actual Ovation Controller and
provides 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.
 Actual Ovation Controller software, running under the Wind River VxWorks simulator.
Virtual Controllers execute under the control and guidance of a Virtual Controller Host software
package.
The operator interface to an Ovation Virtual Controller is identical to the operator interface of
actual Ovation Controllers.
21.3 What is an Ovation Virtual Controller Host?
The Ovation Virtual Controller Host software package permits Virtual Controllers to run in the PC
environment. The Virtual Controller Host manages Virtual Controllers and coordinates their
operation. The Host machine can coordinate the activity of one or several Virtual Controllers.
Host machines can be any Windows HMI (Human Machine Interface) that has the required
amount of memory. Hosts can handle up to 20 Virtual Controllers on each Windows PC,
depending on the amount of memory installed on your computer.
Note: For maximum performance, Emerson recommends that you limit the number of Virtual
Controllers per host to a maximum of 10.
The Virtual Controller Host has the capability to stop and start Virtual Controllers and support their
control execution timing and Ovation network interface. Therefore, the simulation of an Ovation
Controller is accomplished exclusively by a Virtual Controller.
A Virtual Controller Host is:

 A Windows-based PC, licensed as an Ovation Windows HMI.
 Any HMI designated as a Virtual Controller Host must be equipped with sufficient memory:
 4GB Memory.
 An HMI could be one of the following:
 Operator Station.
 Engineering Station.
 Database Server.
 Base Station.
338 OW360_R1005
21.4 What are the Virtual Controller commands?
The functions of Virtual Controller Hosts are:

 To house Virtual Controllers.
 To enable Virtual Controllers to operate.
 To coordinate the operation of Virtual Controllers.
21.4 What are the Virtu al Controller commands?
The Virtual Controller Host software package has a user interface that allows Virtual Controllers to
be managed and to operate in a PC environment. The available commands include the following:
 Run: Begins Controller scan execution. Virtual Controllers execute with real-time speeds,
similar to real or actual Controller standards of one scan every second. When running
simulation in real time, the Virtual Controller software ensures that the perceived performance
is not faster or slower than real time.
 Freeze: Suspends scan execution. This state causes all Virtual Controllers and their
associated models to stop execution. When Virtual Controllers are in this state, they remain
frozen until the operator takes action to change the state.
 Save: Takes a snapshot or image of the Virtual Controller's relevant data, such as the
Controller's current operating state of all models and control schemes. The following
information is saved for each Virtual Controller:
 Local Memory.
 Network Shared Memory.
 All I/O tables.
 Load: Restores a previously saved image of the Virtual Controller. Loading a previously
saved state of the Virtual Controller causes the initial conditions to be in the exact state as
when the save occurred.
OW360_R1005 339
21.5 What is the operation of the Virtual Controller?
21.5 What is the operation of the Virtual Controller?
The Ovation Virtual Controller software package replicates the operation and the functionality of a
real or actual Ovation Controller. Virtual Controller software offers all standard VxWorks Ovation
Controller capabilities plus the benefit of operating in a Microsoft Windows operating environment.
Ovation Virtual Controller Hosts are loaded with Virtual Controller software on a Windows-based
PC. The Host Controller permits Virtual Controllers to operate on desktop workstations thus
providing portability for use throughout the facility. One Virtual Controller for every actual Ovation
Controller is necessary to fully simulate your control system.
An Ovation Simulator using Virtual Controller technology replicates a full scope simulator. Each
unit's specific Controller configuration and graphics are loaded along with the plant's model to
make the desktops replicate the plant's controls exactly.
Virtual Controllers use the same internal processes as actual Ovation Controllers. The following
processes are identical to actual Ovation control systems, except Virtual Controllers run on a
Windows PC:
 Point origination.
 Point naming and alarming.
 Control sheet execution.
 Control areas and timing.
 Algorithm execution.
Plant operators use standard Ovation configuration tools to access, configure, and load Virtual
Controllers. The configuration files for each Controller are maintained and available for
modification on the Simulator Database Server.
A user interface on the Ovation Virtual Controller Host allows the operator to control the operation
of individual Virtual Controllers.
340 OW360_R1005
21.6 What is the Virtual Controller Manager window?
21.6 What is the Virtual Controller Manager w indow ?
The Virtual Controller manager is a graphical user interface that displays information regarding
your Virtual Controller. The manager displays a list of the Virtual Controllers that are configured to
run on the local machine. It also displays a status for each of the Virtual Controllers. There is a
control section for each Virtual Controller that allows you to start or stop each Virtual Controller
individually.
The following figure illustrates the Ovation Controller Manager window:
Figure 89: Ovation Virtual Controller Manager
21.7 Virtual Controller terminology
Virtual Controller terminology
TERM DESCRIPTION
DDB Dynamic data is a portion of a point record. It is broadcast on the Ovation Network in
Dynamic Data Blocks or DDBs.
License file Required to run the VxWorks simulation.
MAC address Media access control (MAC) address is an address used by network interfaces to
uniquely identify themselves on a network.
Model A recreation of a computer design. A model is the software representing the
operation of the physical plant.
Ovation An Ovation drop type that provides the capability to define the Ovation database and
Database engineering capabilities for the complete system.
Server
Ovation HMI An Ovation drop type that provides operator interface functionality. HMIs can be any
Ovation Operator Station. An Ovation HMI with sufficient memory can perform as a
Virtual Controller Host.
OW360_R1005 341
21.8 What are the architecture types of Ovation Virtual Controllers?
TERM DESCRIPTION
Ovation Plant A collection of Ovation Controllers with I/O and HMI drops in a network configured
Control System according to the requirements for control of a specific plant.
Ovation An Ovation SimController is a Controller in which the I/O interface hardware and
SimController software driver can be used with, or replaced by, a Simulation I/O software driver.
Use of the Simulation I/O driver allows points that are normally accessed by their
hardware addresses to be re-directed to the Ovation network. A modeling function
on the network provides the data rather than accessing data through the field I/O
interface.
Ovation A collection of Ovation drops that provides the same functionality as an Ovation
Simulator plant control system without using real Ovation I/O. The addition of a plant
simulation model replaces the I/O functions.
Ovation Virtual Software-based Controllers executing in a Windows operating system are
Controller configurable using the same tools as the Ovation Controller. Virtual Controllers
execute all of the Controller functionality including the same algorithm sets as the
Ovation Controller but do not require any of the Ovation I/O hardware interfaces.
Ovation Virtual An Ovation personal computer running on a Windows operating system. A Host is
Controller Host capable of supporting 1 to 20 Virtual Controllers, providing Virtual Controller
coordination.
Ovation Virtual A combination of the attributes of the Ovation SimController with Simulated I/O
SimController driver but running on a Windows operating system.
Port security Restricts input to a network interface by limiting and identifying MAC addresses of
the workstations that are allowed to access a switch port.
Real or Actual A Controller having the capability to connect to the actual plant I/O and perform plant
Controller control. Actual Controllers run on the VxWorks operating system.
Storm control A traffic storm occurs when a large number of data packets are transmitted through
a network, creating excessive traffic and degrading network performance. The storm
control feature monitors and compares the incoming traffic levels with the configured
storm control level.
Ovation Virtual Controllers offer a choice of two configurations:

 Single-machine architecture.
 Networked architecture.
The Ovation Virtual Controller architecture executes standard Ovation Controller functionality on a
Microsoft Windows-based workstation, referred to as the Ovation Virtual Controller Host. Virtual
Controllers reside on the host machine and identically simulate the functionality of actual Ovation
Controllers and the plant control system network. Therefore, to fully simulate the entire control
system, one Virtual Controller is required for each real Controller installed on your system.
An algorithm library, built from the Ovation Controller algorithm library, provides the tools
necessary to build plant responses.
342 OW360_R1005
21.8.1 What is the Virtual Controller single-machine architecture?
Single machine architecture mimics the behavior of the Ovation control system on a single
Windows-based PC. The single-machine architecture can consist of up to 20 Ovation Virtual
Controllers and a combination of Operator or Engineer Stations, Database Server, or Base
Station functions executing on the same Windows-based machine.
Notes:
 For maximum performance, Emerson recommends that you limit the number of Virtual
 The number of Virtual Controllers that can be run is dependent on the processor and
amount of installed memory.
The single machine architecture can be used for offline control building, database testing, and
control strategies without requiring an actual Ovation control system. Ovation Virtual Controllers
use the same source code that actual Controllers use.
The following figure depicts the Ovation single-machine architecture.
Figure 90: Single-machine architecture illustration
OW360_R1005 343
21.8.2 What is the Virtual Controller networked architecture?
The networked system configuration allows for a number of actual Ovation drops to exist with
Ovation Virtual Controllers on an actual Ovation Fast Ethernet network. Virtual Controllers can be
hosted on a single host machine or can be distributed across multiple machines.
Networked architecture includes the Ovation Virtual Controller Host with Virtual Controllers along
with other Ovation drops, such as Ovation Operator, Engineer, Database workstations, and
Controllers, all connected to an Ovation network.
The networked configuration allows any type of Ovation drop to coexist on the network with
Virtual Controllers, including actual VxWorks-based Controllers. Networked configurations are
designed to accommodate multiple workstations as well as allow for system expansion while
reducing the amount of hardware.
The following figure depicts an Ovation Networked system.
Figure 91: Networked architecture illustration
344 OW360_R1005
21.9 What are the requirements for Ovation Virtual Controllers?
21.9 What are the requirements for Ovation Virtual Controllers?
A Virtual Controller Host is 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 20 Virtual Controllers on a Virtual Controller Host before a second host is needed.
Notes:
 For maximum performance, Emerson recommends that you limit the number of Virtual
 The number of Virtual Controllers that can be run is dependent on the processor and
amount of installed memory.
The host software has the ability to coexist with other Ovation workstations. Host machines can
be any HMI listed below:
 Operator Station.
 Engineering Station.
 Database Server.
 Base Station.
Each Ovation drop type, including the host and up to 20 Virtual Controllers, has a unique IP
address. Therefore, each drop has its own individual drop identity on the Ovation network.
21.10 What are the hardware requirements for the Ovation Virtual
Controller host?
The minimum hardware requirements to operate one Virtual Controller Host are as follows:
 A Windows-based PC (Windows 7 / Server 2008 operating system / Server 2012 R2 (64-bit)
operating system/ Windows 10 Enterprise 2016 LTSB)
 4-GB Memory.
 3.1 GHz Pentium 4.
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.
21.11 What are the software requirements for the Ovation Virtual
Controller host?
The following minimum requirements are necessary for software installation of a Virtual
Controller:
 One Windows-based PC (Windows 7 / Server 2008 / Server 2012 R2 (64-bit) operating
system/ Windows 10 Enterprise 2016 LTSB).
 4-GB Memory.
 Standard Ovation software DVD.
OW360_R1005 345
21.12 What are the Virtual Controller license types?
21.12 What are the Virtual Controller license types?
Two licenses are required for a Virtual Controller system:

 Virtual Controller Host software license (includes required license file).
 Virtual Controller software license (see page 346).
Each host requires a software license. Each Virtual Controller added to the host machine also
requires a software license. Both licenses are fixed licenses.
21.12.1 What is needed to license the Virtual Controller?
Each Virtual Controller loaded on your system requires a license to become active. A maximum of
20 Virtual Controllers can be licensed to each host. Virtual Controllers reside within host
machines and are configured and loaded using standard Ovation Developer Studio tools.
The configuration files for each Virtual Controller are maintained and available for modification on
the system Database Server.
346 OW360_R1005
S E C T I O N 22
22 Planning security for your Ovation system
IN THIS SECTION
What is external security? ............................................................................................... 348

What is Ovation internal security?................................................................................... 348
Security terminology ........................................................................................................ 349
What is Ovation hardening? ............................................................................................ 351
Using the domain concept in security ............................................................................. 351
What are the best practices for establishing a secure system? ...................................... 352
What is antivirus software? ............................................................................................. 352
What is a RADIUS server? .............................................................................................. 353
OW360_R1005 347
22.1 What is external security?
22.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 92: Defense perimeter for Ovation system
22.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.
348 OW360_R1005
22.3 Security terminology
Security terms
TERM DESCRIPTION
Account Represents a physical entity, such as a computer or person.

Active Directory (AD) Component of Windows. Provides a method to securely manage the identities
Database and relationships in a domain.
Additional or Redundant This drop (hereafter referred to as redundant) mirrors the security information
Domain Controller in the primary Domain Controller and performs security functions if the primary
Domain Controller fails.
CIP Critical Infrastructure Protection (CIP) is a set of cyber security standards for
electric power generation, transmission, and distribution organizations. The
North American Electric Reliability Corporation (NERC) developed CIP
standards with oversight from the Federal Energy Regulatory Commission
(FERC).
Computer Account Information that uniquely identifies a computer in a domain. Every computer
that joins a domain has a computer account automatically assigned to it.
Similar to user accounts, computer accounts provide a means for
authenticating computer access to the network and to domain resources.
Domain Logical collection of computers and users on a network that share a common
security database.
Domain Administrator User in a domain who can install Ovation software in addition to performing
standard Windows administrative tasks. By default, the Administrator has
these privileges.
Domain Member Any computer in a domain that is not a Domain Controller but responds to the
Domain Controller computer.
Domain Security Model Security policies and resource database are maintained on one computer
(server) known as a Domain Controller. This data is shared with all computers.
Firewall Security system intended to protect an organization's computer network from
external threats. All communication between the internal computer network
and the outside world is routed through a server that determines if a message
is safe to pass to the internal network.
Global Role A role defined as a global role enforces the same set of rules for a user on all
Ovation networks without having to create individual roles on every network.
There is only one global category for each domain.
Group Policy Collection of Windows group policy rules that defines what desktop and
system features a user or a computer has access to.
Local Console Identifies a Windows session for a user sitting directly in front of an Ovation
computer that he or she is logged on to.
NERC North American Electric Reliability Corporation (NERC) is an agency that
oversees the reliability and adequacy of bulk power supply in electric utility
systems.
Ovation Security Center Provides electronic security management functions to manage the cyber
(OSC) security of Ovation Distributed Control Systems (DCS) without disrupting the
controlled process.
Ovation Administrator User who has the authority to manage and configure the security for the
Ovation system.
OW360_R1005 349
TERM DESCRIPTION
Ovation Role Collection of Ovation rules that define what Ovation functions a user or
computer can perform on an Ovation system. A role must be assigned to a
User account and may be assigned to a Computer account.
Primary Domain Controller Server in a domain that contains the common security database for a network
and controls the access to network security resources. This drop must be the
first drop configured in a domain. If this drop fails, security is managed by a
redundant Domain Controller.
A primary Domain Controller can control security for separate Ovation
systems. These Ovation systems may or may not be configured for multi-
networking
Private Role Private role enforces rules for only the network where the role is defined.
There is only one private category for each Ovation network.
Remote Console Identifies a Windows session for a user sitting directly in front of an Ovation
computer but remotely logged on to another computer. Remote Desktop is
used to perform this connection and login.
Remote Desktop on You can have access to a Windows session that is running on a computer
Windows when you are at another computer. For example, you can connect to an
Ovation computer from home and have access to your Ovation applications,
files, and resources as though you were in front of the computer at work.
Rule Defines an aspect of the run-time behavior of any software. For instance,
“Deny network access” could be a rule. May be Ovation rules or Microsoft
group policy rules.
Security Manager Client Software that runs on domain members and receives security configuration
settings from the security database in the Domain Controller.
Security Manager Server Software that runs on the Domain Controller and communicates security
configuration settings from the security database to the domain members.
User Account Information that uniquely identifies a person in a domain. A user account
enables a user to log on to computers in a domain with an identity that can be
authenticated by the domain.
Each user who logs on to the domain should have a unique user account and
password. Typically, the administrator creates user accounts for each person
on the network.
Workgroup security model All computers are peers and each computer maintains its own security policies
and resources database. User accounts must be created on each computer.
Used in Ovation systems prior to 2.4.
350 OW360_R1005
22.4 What is Ovation hardening?
22.4 What is Ovation hardening?
Hardening is the process of securing a system by reducing its surface of vulnerability. The more
functions that a system performs, the larger its vulnerability surface.
In the Ovation system, the purpose of system hardening is to improve its security posture by
configuring certain Windows policy settings to align with industry best practices without
compromising the functionality of the Ovation software. You should perform the hardening
procedures on all Operator Station/Engineering Station drops after Ovation is installed, and after
the drops have been loaded and downloaded for the first time.
Note: Hardening procedures can be run at any time after Ovation is installed. However,
Emerson recommends that you perform these procedures right after the install in order to
minimize the chance of your customized setting being overwritten. Backups are made as part of
the hardening process to aid in recovering any lost settings.
These hardening procedures apply to Windows Server 2012 R2 and Windows Server 2008 R2
functional domains.
22.5 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 manual for additional information.
OW360_R1005 351
22.6 What are the best practices for establishing a secure system?
22.6 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. (Refer to the Ovation Software Installation
Manual.)
 If you plan to use remote and local console design in your Ovation system, ensure that you
have adequate provisions for remote console security.
 Create a plan that outlines in detail how security will be implemented.
22.7 What is antivirus softw are?
Antivirus software is a program or set of programs that are designed to prevent, search for,
detect, and remove software viruses, and other malicious software like worms, trojans, adware,
and more.
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.
Though Emerson designed the Ovation control system to be fully compliant with open-
architecture 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.
352 OW360_R1005
22.8 What is a RADIUS server?
22.7.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) (see page 443). 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).
22.8 What is a RADIUS server?
Remote Authentication Dial In User Service (RADIUS) is a client-server protocol and software
program that enables remote access clients to communicate with a central server to authenticate
dial-in users and authorize their access to the requested system or service. In Windows Server
2012, Network Policy Server (NPS) is the Microsoft implementation of the RADIUS server.
OW360_R1005 353
S E C T I O N 23
23 Planning for an Ovation Process Historian (OPH)
IN THIS SECTION
Ovation Process Historian overview ............................................................................... 355

Historian component overview ........................................................................................ 356
Historian terminology ...................................................................................................... 357
Hardware requirements for the historian ......................................................................... 359
Software requirements for the historian .......................................................................... 359
Historian server redundancy ........................................................................................... 360
How does the historian work? ......................................................................................... 361
Historian planning overview ............................................................................................ 361
How many historians do you need? ................................................................................ 362
How many scanners do you need? ................................................................................. 363
How will you archive your data? ...................................................................................... 364
Who are your end users? ................................................................................................ 365
Do you need to migrate eDB or HSR data to your new historian? ................................. 366
Will you need any third-party software? .......................................................................... 366
What are the Desktop Tools? .......................................................................................... 366
23.1 Ovation Process Historian overview
The Ovation Process Historian (OPH) 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, e-mail, or Web pages. The historian can archive this
information to a removable media or to a nearby or remote fixed disk storage unit.
You can use the historian to better understand the typical and abnormal behavior of your plant
processes, to identify common trends, to explore abnormalities, and to diagnose process flaws
and failures. The frequency and precision of historian monitoring are beneficial when accuracy is
of utmost importance.
23.1.1 Functions performed by using the Ovation Process Historian
You can perform the following functions by using the Ovation Process Historian:
 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.
OW360_R1005 355
23.2 Historian component overview
 Operator events.
 Sequence of events (SOE) data.
 ASCII system messages.
 User files.
 Store process point data that does not originate directly from your DCS (lab history data).
 Edit and annotate collected historical data.
23.1.2 Advantages of the Ovation Process Historian
The Ovation Process Historian has the following advantages:

 You can archive data for the following purposes:
 Duplication of valuable historical records.
 Off-site storage to provide protection of data loss due to a catastrophic event.
 To make room in the main storage area for the newly collected data.
 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 have previously used the eDB or the HSR to collect historical information, you can
utilize Emerson's migration service to shift your collected data to 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.
23.2 Historian component overview
The Ovation Process Historian includes several user interfaces and other components to help you
get the most from your historical data monitoring, storage, retrieval, and archiving.
Components of the Ovation Process Historian
COMPONENT USE
Historian server Facilitates collection, storage, archiving, and retrieval, as well as the
historian license manager.
Scanner(s) Monitors points and collects data that includes attributes, alarms,
operator events, SOE, and SCADA.
Engineering tools (includes Helps you configure your historian server, disks, archive, scanners,
Historian Configuration Tool and scan groups, and points. In addition, this component helps you edit
History Edit tool) and annotate historical data.
Report Manager Enables you to schedule and generate customized reports to display
your historical data
Status Explorer A Web-based user interface that enables you to check the
configuration and health of your system.
356 OW360_R1005
23.3 Historian terminology
COMPONENT USE
Client interface Enables you to use OLE DB to write your own programs to retrieve
data.
Client Desktop Tools Enables you to query and retrieve information by using SQL, trend,
review, and the Excel add-in.

The following table describes terms that are generally used with the Ovation Process Historian.
Terms used with the Ovation Process Historian
TERM DESCRIPTION
Absolute time Date and time that are specified in numeric month, day, year and hour, minute,
second.
Alias An alternative name assigned to a process point in a database.
API Application Programming Interface specifies how software components should

interact with each other.
Auto Historian When specified as a Historian for a trace item, historical data is obtained from the
first historian in the historian list that permits a connection and fulfills a data retrieval
request.
Compound trace This is a trace item that is not directly a process point but derives its values from
other process point values by applying the specified calculation logic.
DCS Distributed Control System (or plant control system); the Ovation system or systems
that provide the source of the process point data and alarms and events that are
collected by the historian.
Deadband A configuration that specifies the amount of change needed to occur before a point
is collected.
Fixed archive A duplication of historical data files stored on to a non-removable storage device,
typically a networked-attached storage (NAS), direct-attached storage (DAS), or
storage area network (SAN) unit, where the archive is typically online and available
for access.
GUI Graphical user interface is a type of user interface that allows users to interact with
electronic devices by using images rather than text commands.
Historical Trend This type of trend shows the historical view of process point values for a specified
time span. It interfaces with OPH to obtain historical data of specified granularity
and data aggregation criteria, such as actual-value, minimum, maximum, average,
and more.
Lab Data Historical point data that is entered into the system from an outside application, not
the Ovation network (you provide the timestamps for this information).
Live Trend This type of trend continuously updates the Trend display to show real-time updates
to process point values.
Migrated data Historical data that is transformed to the Ovation Process Historian historical file
format from a previous historical file format.
NAS disc CD/DVD that contains the NAS support files. The disc is labeled as NAS Support
Files for OPH 3.6.0 and SBR 2.0 – June 2016.
OW360_R1005 357
TERM DESCRIPTION
NAS PC Personal computer (PC) used to configure a Network Attached Storage (NAS) unit.
NSECS Nanosecond is one billionth of a second.
NTFS NT File System: an advanced file system that is designed for use specifically with
the Windows operating system.
ODBC Open Database Connectivity is a standard C programming language API for

accessing database management systems (DBMS).
OLAP Online Analytical Processing is an approach to answer multi-dimensional analytical
(MDA) queries swiftly.
OLE Object Linking and Embedding is a distributed object system and protocol
developed by Microsoft.
OPC OLE for Process Control is a set of standard OLE/COM interface protocols that are
intended to foster greater interoperability between automation/control applications,
field systems/devices, and business/office applications in the process control
industry.
RAID Redundant Array of Independent Disks: a data storage method in which data is
distributed among two or more hard disk drives.
Relative time This is a method of specifying start and/or end time for a Historical Trend and is
relative to commonly understood time boundaries, such as current time, current
hour, today, yesterday, and so forth. This is represented as an expression
comprised of various mnemonics. One example is ‘ct -10hr - 10mi’ meaning subtract
10 hours and 10 minutes from current time, to determine the time value. Relative
time is useful for Historical Trends because it makes it unnecessary to specify
absolute time values every time a trend needs to be generated.
Removable archive A duplication of historical data files stored across a library of individual DVD-RAM
discs. Access is limited to the data contained on the mounted volume at any one
time.
Scanner Mechanism that is used by the historian for process point data and message-based
data collection.
SCSI Small Computer System Interface: a SCSI bus that is used to connect
microcomputers to peripheral devices.
SOE Sequence of Events is the order in which a set of events happens.
SQL Structured Query Language is a special-purpose programming language designed
for managing data held in a relational database management system (RDBMS).
TCP/IP Transmission Control Protocol/Internet Protocol: the default standard for data
transmission over networks.
Time Zone This is a three- or four-letter abbreviation for the time zones that are available on a
Abbreviation Windows machine, and which users intend to use for specifying the absolute start
and/or end times for a Historical Trend. Using these abbreviations, times can be
specified from nonlocal time zones.
Trace Trace is a graph line representing the values for a process point. The whole Trend is
comprised of a maximum of 32 traces.
Trace values explorer This feature allows you to examine trace values while simultaneously moving a
vertical cursor line horizontally across the trend chart.
User preferences These are the settings for controlling the behavior of the application. You can save
these settings in order and apply them to any new application sessions.
UTC Coordinated Universal Time is the high-precision atomic time standard.
358 OW360_R1005
23.4 Hardware requirements for the historian
23.4 Hardw are requirements for the historian
The hardware requirements for the Ovation Process Historian are as follows:
 Dell PowerEdge T310, T320, T330, R710, R720, or R730.
23.5 Softw are requirements for the historian
The software requirements for the Ovation Process Historian are as follows:
 Microsoft Windows 7 (32 bit).
 Microsoft Windows 7 (64 bit).
 Microsoft Windows 2008 R2 Standard SP1 (64 bit).
 Microsoft Windows 2008 SP2 (32 bit).
 Microsoft Windows Server 2012 R2 Standard.
OW360_R1005 359
23.6 Historian server redundancy
23.6 Historian server redundanc y
Server redundancy protects against data loss due to types of failures including:
 Hardware failure in the primary server.
 Software failure in the primary server.
 Some connectivity failures (for example, if a scanner loses connectivity to the primary server,
server redundancy directs the scanner to send its data to the partner server).
Redundant servers protect against data loss by communicating to each other for two reasons: to
forward messages from the primary server to the partner server in real time, and to backfill data
that was missed when one of the servers went offline.
During normal operation, the scanner communicates to the primary server, which in turn forwards
that information to the partner server. The partner server acknowledges receipt of information to
the primary server, which in turn passes the acknowledgement to the scanner.
During failover operation, when the primary server is offline, the scanner automatically
communicates with the partner server, and the partner server acknowledges receipt of information
back to the scanner.
During failback operation, when the primary server has come back online, the scanner
automatically switches its communications back to the primary server, which forwards that
information to the partner server. The partner server not only acknowledges receipt of that
information, it also forwards the missing data that the primary server was unable to collect while it
was offline.
Synchronous configuration is required for using redundant servers. Synchronous configuration

means that both partner servers are configured to collect data from the same points, with the
same IDs. All configuration choices for servers are handled through the Historian Configuration
Tool. Having identical configuration allows historian server pairs to exchange history data at all
times.
When partner servers are running, they work together automatically to establish synchronization.
For example, if you add a point to drop 61, it communicates your settings to partner drop 62, to
ensure configuration synchronization.
If the partner servers are not in sync, you will be unable to download any new configuration
settings, such as adding points, though the servers will continue working. It is possible to get out
of sync in the following situation: if you add new configurations to the primary while the partner is
failed, and then shut down the primary and restart the partner. Because the servers in this
situation do not have a chance to send missed configuration settings and other missed data, this
situation will create a lack of synchronization. When both servers are up and running, they
reestablish their synchronized configuration.
After recovery, both servers will automatically share all available historical data (up to six months'
worth). If you shift from a non-redundant historian to using redundant servers, it backfills up to six
months of data. All backfills are implemented at a throttled rate in order not to slow down your
network.
360 OW360_R1005
23.7 How does the historian work?
23.7 How does the historian w ork?
The historian enables you to perform four main tasks on your control system:
 Scan.
 Store.
 Archive.
 Retrieve.
23.8 Historian planning overview
There are many factors that determine the number of historians and scanners you need. Your
total point count, as well as the way that you divide those points across various systems,
determines the number of historians that you need for your Ovation system.
The number of historians that you use can help decide the number of scanners that you need
(you need at least one scanner per historian).
The number of scanners that you use determines the amount and detail of data that you can
archive and retrieve from your system.
Because these considerations are intertwined, Emerson recommends that you plan your historian
setup with a thorough understanding of the options available to you. The following questions can
help you create your historian plan:
9. How many historians do you need? (see page 362)

10. Do you need redundant historian servers? (see page 363)
11. How many scanners do you need? (see page 363)
12. How will you archive your data? (see page 364)
13. Who are your end users? (see page 365)
14. Do you need to migrate eDB or HSR data to your new historian? (see page 366)
15. Will you need any third-party software? (see page 366)
16. Do you want to use the Desktop Tools? (see page 366)
OW360_R1005 361
23.9 How many historians do you need?
23.9 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 should become clearer.
23.9.1 Reasons to use multiple historians
The reasons to use multiple historians are as follows:

 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.
23.9.2 Reasons to use a single historian for multiple units
The reasons to use a single historian for multiple units are as follows:
 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.
23.9.3 Reasons to use an embedded historian
An embedded historian is a historian that you add to a pre-existing database server workstation.
The reasons to use an embedded historian are as follows:
 If you do not expect your total point count to exceed 10,000 points.
 If you require the lowest cost solution to gather historical process data.
362 OW360_R1005
23.10 How many scanners do you need?
23.9.4 Do you need redundant historian servers?
You can use redundant servers to protect against data loss due to the following reasons:
 Hardware failure in the primary server.
 Software failure in the primary server.
 Some connectivity failures (for example, if a scanner loses connectivity to the primary server,
server redundancy directs the scanner to send its data to the partner server).
If historical data collection is critical to your plant, consider utilizing redundant servers. If you are
currently using a non-redundant historian server, you can convert to redundant servers. The
redundant servers will backfill up to six months of data, at a throttled rate in order not to slow
down your network.
Redundant historian servers are only available to customers with Ovation 3.1.1 or higher, or
customers with Ovation 3.0.4.
23.10 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.
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 one of the two scanners is active, and which
one 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.
OW360_R1005 363
23.11 How will you archive your data?
23.11 How will you archive your data?
The historian archive system provides an optional (though recommended) capability for storage
and retrieval of the collected data to and from a removable and/or fixed archive. It maintains a
database of all data that is stored on the archive. The removable archive storage device is a
DVD-RAM drive, and is attached to the machine on which the historian server software is
installed. However, a fixed archive typically consists of a disk storage system, such as networked
attached storage (NAS) or a storage area network (SAN), accessible to the historian server (see
Archiving data).
Note: Emerson strongly recommends the use of an Emerson-standard network attached

storage (NAS) device for fixed archiving purposes.
Disk size estimates are based on the volume and type of information that you want to collect.
Since your disk space needs can change radically based on the volume and type of points that
you want to collect historical information for, use the following estimates as general guidelines
only.
The following table of disk space estimates is based on several assumptions:

 Your hardware is a Dell PowerEdge T320 or R720 with a standard configuration: three 300-
gigabyte drives in RAID 5, approximately 540 gigabytes of usable disk space.
 You collect samples at, on average, a 1% rate.
 Your total disk space is approximately 510 gigabytes.
 Your DVDs can hold a maximum of approximately 8 gigabytes of data.
Storage estimates based on point count
NUMBER OF NUMBER OF YEARS NUMBER OF NUMBER OF DAYS FOR BO TH

POINTS BEFORE DISK ADDITIONAL YEARS SIDES OF A DVD TO BECOME
TO STORAGE IS FULL THAT 1-TB RAID FULL
COLLECT ADDS FOR STORAGE
10,000 11 21 30
25,000 4.5 8.5 12
50,000 2.2 4.2 6
75,000 1.5 2.9 4
100,000 1 2.1 3
External RAIDs extend your main 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. However, deploying an external RAID unit as a fixed archive device provides the benefit
of duplicating the primary storage data while also providing an online access to the data that is no
longer available in the main storage.
364 OW360_R1005
23.12 Who are your end users?
DVD-RAM storage is a low-cost media with the following advantages:

 The discs can be moved off-site to protect against data loss due to a catastrophic event.
 The discs are impervious to magnetic fields.
 It is easy to make duplicate copies of the media.
 With proper handling, the discs are durable and can last a very long time.
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.
Removable media offers storage beyond standard online storage. However, the removable
archive requires periodic manual interaction to remove full volumes and insert blank media, or to
insert older media when there is a need to access data that precedes the data on the main
storage.
A fixed archive provides an archive solution with minimal human involvement. In addition to
unmanned operation, a fixed archive has the following advantages:
 Volumes are always mounted and accessible for data retrieval, eliminating the need for the
primary extended storage or reloading of files from the archive.
 Faster read and write times than a DVD-RAM.
 Catastrophic data loss protection can be provided by locating the storage system remotely.
 The fixed archive itself can be backed up and restored.
23.12 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 to perform ad hoc queries to explore raw historical data, use Historical Review.
 If you want tabular data to analyze, print, or save to files, 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 database queries.
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. In addition, non-local users who query the historian server frequently,
or for large volumes of data, could greatly impact your network performance.
OW360_R1005 365
23.13 Do you need to migrate eDB or HSR data to your new historian?
23.13 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, you should budget for work time and services to plan your data
migration, migration cost, and downtime. The 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 there can be difficulties.
Therefore, Emerson recommends that you do not attempt to migrate any custom report templates
that meet the following criteria:
 The reports 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 possible to migrate your existing point configuration into
your new historian. See your Emerson representative for details.
23.14 Will you need any third -party softw are?
The historian uses the SAP Crystal Reports 2016 to build report layout files. If you want to build
report layout files outside of your control system, you must purchase additional copies of SAP
Crystal Reports 2016.
23.15 What are the Desktop Tools?
The Desktop Tools are as follows:

 Trend (Using Historical Trends).
 Historical Review (Using Historical Reviews).
 Excel Add-in for Microsoft Excel spreadsheets (Using the Microsoft Excel add-in).
23.15.1 Do you want to use the Desktop Tools?
The Desktop Tools enable you to access process data stored in your Historian from computers
that are non-Ovation DCS workstations. See the Historian Desktop Tools overview for more
information.
366 OW360_R1005
S E C T I O N 24
24 Planning for second generation (I/O module)

Foundation Fieldbus
IN THIS SECTION
What is Foundation Fieldbus?......................................................................................... 368

Foundation Fieldbus second generation solutions .......................................................... 371
What are the Foundation Fieldbus and Ovation components? ....................................... 372
What is the Foundation Fieldbus communications model?............................................. 374
What is good Foundation Fieldbus segmentation design? ............................................. 376
What are the supported Fieldbus algorithms? ................................................................ 383
OW360_R1005 367
24.1 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.
Figure 93: Conventional wiring vs. Fieldbus wiring
368 OW360_R1005
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 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 world’s 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
(http://www.fieldbus.org).
24.1.1 Understanding Foundation Fieldbus interoperability
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 Foundation’s Stack Conformance
Test.
 Correctly implement the Function Block Application Process Model defined in the Foundation
Fieldbus specification. This means a device’s 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.
OW360_R1005 369
24.1.2 Fieldbus terminology
The following table contains a list of terms used in conjunction with Foundation Fieldbus.
Fieldbus terminology
TERM DEFINITION
AMS Device Manager Asset Management System Device Manager. A comprehensive and integrated
family of applications from Emerson developed for predictive maintenance,
performance monitoring, and economic optimization.
Branch Single "limb" or spur off the main trunk of a Fieldbus segment.
Commissioned State of a Fieldbus device when the device is assigned an address on the
segment, and is associated to the device tag name defined in Ovation. The
physical device is made operational and available to the Ovation system.
Decommissioned State of a Fieldbus device where the association between the Fieldbus
Engineering software and the physical device is removed.
Device Descriptions Software file that provides the information a host system needs to understand
both the meaning of the data and the capabilities of the device.
Devices Field instruments, such as transmitters and valves, with processors that
monitor device performance and state.
Fieldbus Algorithms Algorithms are mathematical formulas that define a specific control strategy.
While function blocks reside in a device, the Ovation control system uses
algorithms on control sheets that mimic the function blocks. Fieldbus devices
can be controlled by Ovation Fieldbus algorithms and can be part of an
Ovation control scheme.
Function Blocks Self-contained software modules that reside in the Fieldbus devices and
enable the I/O to be moved from the Ovation Controller to the field devices.
Interoperability Ability for field devices from different manufacturers to work together, sending
and receiving information related to their specific function in the process.
Link Active Scheduler Determines which Fieldbus device communicates at what time and in what
(LAS) order.
Macrocycle Period of time on a segment between repetitions of all the functions on the
segment.
PlantWeb Alerts Special type of alarm generated by Foundation Fieldbus devices for the
purpose of providing self-checking, fault diagnostics, and user support.
Publisher/Subscriber Method of scheduled communications where data is sent on the bus or
communications "published" once, and all devices that need the data listen to or "subscribe" to
the same transmission.
Publisher VCR Output from a function block, and it distributes the output to one or more
function blocks.
Repeaters Optional components used either to extend the length of a Fieldbus segment
or to increase the number of devices on a segment.
Resource Blocks Self-contained software modules that reside in the Fieldbus devices that deal
with the overall device. Blocks contain information such as manufacturer,
device type, and serial number.
Second Generation Ovation system that connects to the Fieldbus segment through a bus module
Fieldbus (also called an H1 card).
Segment Cable, connected devices, and supporting components.
370 OW360_R1005
24.2 Foundation Fieldbus second generation solutions
TERM DEFINITION
Splice Connections that have a distance of less than one meter from the main trunk.
Spurs Connections in which the distance from the main trunk to the instrument is 1 to
120 meters.
Stale Link Count Limit Specifies the number of communications that can be missed before the
parameter status is set to BAD.
Subscriber VCR Input to a function block, and it receives output from another function block.
Transducer blocks Self-contained software modules that reside in the Fieldbus devices. These
modules deal with the wetted parts of a device (parts of the device with
voltage). They provide local input/output functions needed to read sensors and
to command actuators, displays, or other output hardware.
Tree A layout topology that has a number of branches or spurs that connects to the
main trunk in one location.
Trunk Bussed segment wire that runs from the equipment room to junction boxes.
VCR A Virtual Communication Relationship (VCR) is the connection between a
Fieldbus parameter in one device on the segment and a Fieldbus parameter in
another device on the same segment or to the Ovation Controller.
24.2 Foundation Fieldbus second generation solutions

Ovation 3.5 and later releases support the second generation solution (I/O module) for the
application to interface with Foundation Fieldbus.
Note: Ovation 3.5 and later releases do not support the first generation Fieldbus. It will only
interface with the Fieldbus I/O module.
The following table describes the first and second generation of Foundation Fieldbus solutions.
First and second generation of Foundation Fieldbus solutions
FIELDBUS DESCRIPTION
SOLUTIONS
Second generation 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. In the second generation Fieldbus solution, the
Ovation system connects to the Fieldbus segment through a bus module
(also called an H1 card). It streamlines the amount of hardware that you
need by eliminating the use of Ethernet network switches and gateways.
These modules require external power conditioners, where the power is
supplied to the external power conditioners from the standard Ovation power
supplies.
First generation The first generation Ovation implementation of Foundation Fieldbus uses
hardware and software components to integrate Fieldbus devices with
Ovation technology through a gateway module. The gateway may reside in
an Ovation Controller cabinet or it may be located up to 100 meters from the
Controller.
Note: To upgrade FET database to the new Ovation 3.5 Fieldbus system, refer to FET Migration
in the Ovation Software Installation Manual.
OW360_R1005 371
24.3 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 use of Ethernet network switches and gateways.
Figure 94: Architecture overview
372 OW360_R1005
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 micro-controller 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 about AMS Device Manager, refer to the AMS
Device Manager documentation online.
OW360_R1005 373
24.4 What is the Foundation Fieldbus communications model?
The Foundation Fieldbus H1 technology is modeled on the Open Systems Interconnect (OSI)
Seven-Layer model and consists of three parts:
 Physical Layer
 Communication Stack
 User Layer
The Foundation Fieldbus communications stack is a single software implementation that performs
functions similar to layers 2 through 7 of the OSI module. The user layer (also called the function
block application process) is unique to Foundation Fieldbus and is not part of the OSI model.
Figure 95: Comparison of the OSI model and the Fieldbus stack
24.4.1 Physical layer
The first function layer of the Foundation Fieldbus communications model is the physical layer.
The physical layer translates messages into physical signals on the wire.
The physical layer also provides the common electrical interface for all Foundation Fieldbus
devices. Foundation Fieldbus H1 segments require 9 - 32 volts DC power and approximately 15-
20 mA of current per device.
The Foundation Fieldbus physical layer is defined by approved standards (IEC 61158-2 and
ANSI/ISA 50.02, part 2). It can run on existing field wiring over long distances, supports two-wire
devices, and the standard makes provisions for intrinsically safe wiring practices as defined by the
applicable governing bodies.
374 OW360_R1005
24.4.2 Data link and application layers
The second part of the communications model combines several technologies that together
control transmission of data on the Fieldbus. These layers combined together are referred to as
the communications stack.
The data link and applications layers provide a standard way of “packaging” the data, as well as
managing the schedule for communication and function block execution.
24.4.3 User layer
The user layer sits on top of the communications stack, where it enables you to interact with other
layers and with other applications.
The user layer contains resource blocks, transducer blocks, and function blocks that describe and
execute device capabilities such as control and diagnostics.
This release of Ovation software supports the following function block types: FFAI, FFAO, FFDI,
FFDO, FFISEL, FFMAI, FFMAO, FFMDI, FFMDO, and FFPID. Within this group of supported
function block types, Ovation uses device descriptions to configure function blocks and enable the
display of parameters without custom programming.
Device Descriptions enable the Ovation system to interact with and understand these blocks
without custom programming.
OW360_R1005 375
24.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 Ovation’s conventional wiring, the major topological change introduced by Ovation’s
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 96: 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.
376 OW360_R1005
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 97: Conventional layout
OW360_R1005 377
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 98: Fieldbus segments through junction boxes
378 OW360_R1005
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 99: 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-in-
field 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.
OW360_R1005 379
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
Foundation Fieldbus.
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
Foundation Fieldbus.
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.
380 OW360_R1005
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.
OW360_R1005 381
 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.
382 OW360_R1005
24.6 What are the supported Fieldbus algorithms?
24.6 What are the supported Fieldbus algorithms?
The supported Ovation Fieldbus algorithms shadow the following Fieldbus function blocks:
 FFAI
 FFAO
 FFDI
 FFDO
 FFISEL/FFISELX
 FFMAI
 FFMAO
 FFMDI
 FFMDO
 FFPID
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
Scenario 2
FFAI Ov ation FFAO

PID
OW360_R1005 383
S E C T I O N 25
25 Planning for Profibus
IN THIS SECTION
What is Profibus? ............................................................................................................ 386

What is device interoperability? ...................................................................................... 387
What are the Profibus and Ovation components? .......................................................... 388
What are Profibus devices? ............................................................................................ 389
What is Profibus module redundancy? ........................................................................... 391
What is Profibus port redundancy? ................................................................................. 394
What are Profibus hardware and software requirements? ............................................. 395
To support acyclic exchange of data............................................................................... 395
OW360_R1005 385
25.1 What is Profibus?
25.1 What is 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 system’s 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 about 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.
386 OW360_R1005
25.2 What is device interoperability?
25.2 What is device interoperability?
work together, sending and receiving information related to their specific function in the process.
The Profibus User Organization establishes guidelines for interoperability between field devices
on a Profibus segment. These guidelines address such aspects as physical characteristics,
communication, and software functionality.
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.
OW360_R1005 387
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 100: Implementation of Profibus with Ovation
388 OW360_R1005
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.
OW360_R1005 389
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.
390 OW360_R1005
25.5 What is Profibus module redundancy?
Profibus module 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).
OW360_R1005 391
Figure 101: Redundancy diagram
392 OW360_R1005
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 about 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.
OW360_R1005 393
25.6 What is Profibus port redundancy?
25.6 What is Profibus port redun danc y?
Ovation Port Redundancy implements a form of Profibus System Redundancy (SR) providing
Profibus master, physical layer media, and slave channels redundancy.
Ovation Native Profibus Port Redundancy allows you to pair simplex Ovation Native Profibus
ports for redundant operation. This allows you to configure a single channel, assign a single set of
device node record and I/O points to a redundant pair and still get port redundant Profibus
operation.
Ovation Native Profibus Port Redundancy evaluates redundancy per slave device and not per
overall channel. As a result, there is no failover. Both channels of every device are active and the
Ovation Native Profibus driver in the Ovation Controller reads inputs from every device, evaluates
device status, and determines which channel’s data to write to the system.
Note: Profibus Port redundancy is available for Ovation 3.3.1 and later releases.
Use the following guidelines to implement Ovation Profibus Port Redundancy:

 Any two Ovation Native Profibus ports on the same controller can be paired for redundant
operation (this includes ports on the same module). This differs from the existing Ovation
Native Profibus module redundancy solution, where redundant modules need to be
configured on adjacent branches.
 Each Ovation Profibus port has a mode designating it as either Stand-alone, Channel A, or
Channel B. Ports for pairing must be designated as either Channel A or Channel B. The
default mode for each port is stand-alone (simplex).
 Only one set of I/O points and device node records is assigned for each redundant pair. The
Ovation Profibus driver internally tracks the status and values of the individual channels and
writes to the set of node records and I/O points for the pair. The redundancy logic is applied
on a slave-by-slave basis as follows:
Port Redundancy Logic
CH. A CH. B WRITE USES INPUTS STATUS VALUE POINT

STATUS STATUS OUTPUT TO FROM TO WRITE TO QUALITY
CHANNEL CHANNEL NODE RECORD
OK OK Both Channel A Channel A GOOD
OK BAD Both Channel A Channel A GOOD

BAD OK Both Channel B Channel B GOOD
BAD BAD Both Channel A Channel A BAD
394 OW360_R1005
25.7 What are Profibus hardware and software requirements?
25.7 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.
25.8 To support acyclic exchange of data
DP-V1 supports the exchange of acyclic data for use in diagnostics, parameterization and alarm
support. Profibus engineering tools have been enhanced in the Ovation 3.5.1 release to operate
with third-party DTM files.The SYCON tool is enabled to display the vendor's Device DTM file.
The Ovation Controller and Profibus module facilitates the transfer of DP-V1 data messages
between SYCON and the Profibus module.
The DTM file should be obtained from the vendor by the projects and loaded on the Ovation
Stations. It is your responsibility to obtain the necessary configuration for these third-party
products by consulting the vendor’s website and/or documentation. Due to the large number of
possible vendor products, Emerson cannot make configuration recommendations for these
products as it could compromise the integrity of Ovation. After successful loading of the vendor
DTM file on Ovation, you will be able to view and modify DP-V1 data in the Ovation Developer
Studio.
OW360_R1005 395
S E C T I O N 26
26 Planning for DeviceNet
IN THIS SECTION
What is DeviceNet? ......................................................................................................... 398

What is field device interoperability? ............................................................................... 399
What is DeviceNet messaging? ...................................................................................... 399
What are the DeviceNet communication methods? ........................................................ 399
What are the DeviceNet and Ovation components? ....................................................... 401
What is a DeviceNet module? ......................................................................................... 402
What are the DeviceNet hardware and software requirements? .................................... 402
OW360_R1005 397
26.1 What is DeviceNet?
26.1 What is 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.
398 OW360_R1005
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 ODVA’s 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.
26.3 What is DeviceNet messa ging?
There are three types of messages that can transmit between DeviceNet nodes:
 Peer messages
Peer messages are data packets that are exchanged from one DeviceNet device to another
over any non-master/slave connection. Peer messages are generally used between devices
manufactured by the same vendor. The vendor defines the structure and contents of the
message so that all devices can understand the contents of the message. Unlike a message
between a DeviceNet master and slave, there is no implicit meaning to the bytes sent over a
peer message connection.
 Explicit messages
Explicit messages are request/response messages that a DeviceNet master device sends to
a DeviceNet slave device over an explicit message connection. Each explicit message
contains specific information that is pertinent to the device type and its parameters.
 I/O messages
I/O messages transfer predefined messages between a DeviceNet master device and an I/O
device. These messages contain real-time I/O information for a device. All I/O messages
transfer an I/O assembly between a master device and a slave device. There are three types
of I/O messages: polled, cyclic, and change of state (COS).
26.4 What are the DeviceNet communication methods?

In computer networking, master/slave is a communication model where one device or process
(master) controls one or more other devices or processes (slaves). The master can make a
service request whereby the slave fulfills the request. The master/slave model provides a
convenient way to interconnect programs that are distributed efficiently across different locations.
A master/slave relationship must be established before data can be transferred between Device
Net devices. DeviceNet supports a number of communication methods over the master/slave
connection:
 Polled
A polled message scheme is where I/O data is transmitted by a master device to a slave
device at some rate. The slave device produces the I/O data in its input assembly to respond
to the polled message.
OW360_R1005 399
26.4 What are the DeviceNet communication methods?
 Cyclic
A cyclic data scheme is where a master device transmits I/O data to a slave device at some
rate. Unlike polled messaging, the slave device might not be configured to respond
immediately to the master device. Instead, slave devices report I/O data on a user-configured
time increment. Cyclic data production is more efficient for applications with I/O that changes
at a slow rate. The result of a cyclic data scheme is reduced network traffic and repeatable
performance.
 Change of state (COS)
In a change of state data scheme, devices report data on a change-of-state basis as events
occur. Rather than a master device sending a periodic message to slave devices, slave
devices produce I/O data only when the application layer reports a data change or upon the
expiration of a heartbeat timer. The result of a change of state data scheme is reduced
network traffic and improved performance.
 Bit Strobe
Bit strobe command and response messages rapidly move small amounts of output data
between the master device and one, some, or all slave devices. The bit strobe message
contains a bit string of 64 bits of output data, one output bit per possible device. Each bit is
assigned to one device address (MAC-ID) in the network.
This service has broadcast functionality, which means that more than one slave device can
be addressed by one command. Because all addressed slave devices get this command at
the same time, this command is normally used to synchronize data transfer to several slave
devices.
A slave device can take its corresponding output bit as real output information to give it to the
peripheral connections (for example, an LED) and/or use the bit as a trigger to send back its
input data with a poll response message. The data that can be sent back from each slave
after a bit strobe command was received is limited to 8 bytes in length. Bit strobe usage
causes a reduced bus loading compared to polled connections.
400 OW360_R1005
26.5 What are the DeviceNet and Ovation components?
26.5 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 either design the segment
as a branch or a tree layout topology. The following figure depicts a typical implementation of
DeviceNet with an Ovation system.
Figure 102: Typical implementation of DeviceNet with Ovation
OW360_R1005 401
26.6 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.6 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.7 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).
402 OW360_R1005
S E C T I O N 27
27 Planning alarm management
IN THIS SECTION
What is an alarm? ........................................................................................................... 404

What is alarm management? .......................................................................................... 405
What are some alarm management problems? .............................................................. 405
What are some best practices for planning alarms? ....................................................... 406
What points can be used as alarms? .............................................................................. 407
How does the Ovation alarm system operate? ............................................................... 408
Types of alarm displays .................................................................................................. 408
Alarm list information fields ............................................................................................. 409
Displaying Alarm lists ...................................................................................................... 409
Alarm lists that display in the Alarm window ................................................................... 410
Remote Network Status list in the Operator Station Alarm window ................................ 420
What is Alarm Suppression? ........................................................................................... 421
What is Alarm Shelving? ................................................................................................. 421
What is the Alarm Annunciation window at the Operator Station? ................................. 422
What are some best practices for managing alarms? ..................................................... 423
What are nuisance alarms? ............................................................................................ 423
What are alarm floods? ................................................................................................... 424
What is the Alarm Health Advisor? ................................................................................. 432
What is the Alarm Guidance window? ............................................................................ 434
What is Remote Alarm Viewer? ...................................................................................... 434
OW360_R1005 403
27.1 What is an alarm?
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.
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:
 Alarm History list (original alarm, not the acknowledgment event)
 Acknowledged Alarm list
404 OW360_R1005
27.2 What is alarm management?
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:
 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.
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.
OW360_R1005 405
27.4 What are some best practices for planning alarms?
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.
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?
406 OW360_R1005
27.5 What points can be used as alarms?
27.5 What points can be used as alar ms?
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.
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 point’s 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.
OW360_R1005 407
27.6 How does the Ovation alarm system operate?
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.
27.7 Types of alarm displays
There are two types of alarm displays:

 Alarm list displays alarms in a list type (see page 412) 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.
408 OW360_R1005
27.8 Alarm list information fields
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:
 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.)
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 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.
OW360_R1005 409
27.10 Alarm lists that display in the Alarm window
27.10 Alarm lists that display 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 412).
 Alarm History list (see page 413).
 Acknowledged Alarm list (see page 414).
 Unacknowledged Alarm list (see page 415).
 Reset list (see page 416).
 Alarm Check Remove list (see page 417)
 Icon list (see page 418) (only displayed when the icon list is configured for Iconic Alarming).
 Remote Network Status list (see page 420) (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 Pre-
3.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
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.
410 OW360_R1005
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 Date, time, alarm type, PN, ED, set/reset description, value, attention code,
Used as Devices 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 Date, time, alarm type, code, point name, description, Net Alias, AP, AY,
value, quality, units, limit, incr, PM, Net ID
OW360_R1005 411
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 alarms constantly update.
 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 103: Alarm window example
412 OW360_R1005
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 104: History list in the Alarm window
OW360_R1005 413
27.10.3 Acknowledged list in the Operator Station Alarm wi ndow
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 105: Acknowledged list in the Alarm window
414 OW360_R1005
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 106: Unacknowledged list in the Alarm window
OW360_R1005 415
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 107: Reset list in the Alarm window
416 OW360_R1005
27.10.6 Alarm Check Remove list in the Operator Station Alarm window
The Alarm Check Remove list has the following attributes:

 Displays all the alarms that are currently alarm check removed.
 Displays the date, time, point name, and description of each point in the list.
 Allows the user to turn alarm checking back on from the list.
Note: To periodically remind you that points have been removed from alarm checking, the
system prompts you to decide if those points should be put back into alarm checking or not. The
points that are reconfirmed by you remain in alarm check removed.
This process is accomplished by using an Alarm Check Reconfirm task. For information on
configuring an Alarm Check Reconfirm task, refer to the Ovation Operator Station Configuration
Guide.
The following figure shows an example of the Alarm window displaying the Alarm/Limit tab in
combination with the Alarm Check Remove tab.
Figure 108: Alarm Check Remove list in the Alarm window
OW360_R1005 417
27.10.7 Alarm Frequency list in the Operator Station Alarm window
The Alarm Frequency tab allows you to view the most frequent alarms that are detected on a
workstation. The tab allows you to identify the number of times a local point goes into an alarm
condition. It displays a running total of the most frequent alarms since the workstation has been
turned on.
However, this feature is only applicable to local alarms and not remote alarms.
The following figure shows an example of the Alarm window displaying the Alarm Frequency tab.
Figure 109: Alarm Frequency tab
27.10.8 Iconic list in the Operator Station Alarm window
The Iconic Alarm list has the following attributes:

 Provides a mechanism to group alarms based on their priority and their plant area.
 These groups of alarms are represented by preconfigured bitmaps (tiles).
 A currently selected alarm group is indicated by a colored border around the icon tile.
 The location (row, column) of the currently selected alarm displays on the Status bar.
You must configure iconic alarming in order to add an Iconic tab to the Alarm window. After you
have configured Iconic alarming (refer to the section To display the Iconic alarms), you can
display it in the Operator Station Alarm window in the Iconic list tab (refer to Ovation Operator
Station Configuration Guide for information about configuring Iconic alarms).
418 OW360_R1005
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 List’s 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.
OW360_R1005 419
27.11 Remote Network Status list in the Operator Station Alarm window
27.11 Remote Netw ork Status list in the Operator Station Al arm
window
The Remote Network Status list has the following attributes:
 Presents detailed information concerning each remote network connection.
 Allows the user to select what information to display in the list.
Note: If you do not configure the alarm display to receive alarms from remote networks, the
Remote Network Status tab does not display.
Figure 110: Remote Network Status list in Alarm window
To select the columns that you want to display in the Remote Network Status tab:
1. Access the Alarm window.

2. Select the Remote Network Status tab.
3. Select the Home ribbon tab.
4. Select the Column(s) window.
5. Select the Remote Network Status view.
6. Select the desired columns and then select OK.
420 OW360_R1005
27.12 What is Alarm Suppression?
The columns choices 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.
27.12 What is Alarm Suppression?
Alarm suppression is a method to prevent an indication of alarm to the operator when the base
alarm condition is present. The base alarm condition can be shelving, alarm check remove, or
alarm cutout.
27.13 What is Alarm Shelving?
Alarm Shelving is a method to temporarily suppress an alarm. It is similar to the Alarm Check
remove functionality. However, the alarm shelving is not a permanent feature. It has a timeout
period that is not saved over reboot. When a point is shelved, an Alarm Check remove
functionality override and remove the Shelving indications.
OW360_R1005 421
27.14 What is the Alarm Annunciation window at the Operator Station?
27.14 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 define whether
unacknowledged alarms and unacknowledged returns blink or not. If blinking is configured, any
unacknowledged alarm or return blinks until it is acknowledged (Refer to the 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 111: Alarm Annunciation window example
422 OW360_R1005
27.15 What are some best practices for managing alarms?
27.15 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.
OW360_R1005 423
27.16 What are nuisance alarms?
27.16 What are nuisance alarms?
Nuisance alarms are defined as the following:

 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.
27.16.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.
27.17 What are alarm floods?

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 423).
27.17.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.
424 OW360_R1005
27.17.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) 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.
 Priorities.
 Sounds (see page 427).
 Descriptions.
Using characteristics for filtering 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 DESCRIPTION CHARACTER DEFINITION

POSITION
(M APS TO THE (M APSTO THE DESCRIPTION
(M APSTO TAB CHARACTERISTICS FOR FOR EACH VALUE )
POSITION 1-8) E ACH V ALUE)
1 Plant Area A Unit 1 Air System

B Unit 1 Boiler
C Unit 1 Condensate
D Unit 1 Generator
E-M Unit 1 Spare
N Unit 2 Air System
O Unit 2 Boiler
P Unit 2 Condensate
Q Unit 2 Generator
R-Z Unit 2 Spare
OW360_R1005 425
CHARACTER DESCRIPTION CHARACTER DEFINITION

POSITION
(M APS TO THE (M APSTO THE DESCRIPTION
(M APSTO TAB CHARACTERISTICS FOR FOR EACH VALUE )
POSITION 1-8) E ACH V ALUE)
2 Subsystem G Gas
S Steam
W Water
O Oil
E Electrical
3 Equipment P Pump
I IP Turbine
L LP Turbine
V Valve
F Fan
4 Designator A A
B B
C C
D D
E East
W West
1 1
2 2
5 Parameter T Temperature
P Pressure
V Volts
F Flow
6-8 Spare Not applicable Not applicable
Using priorities for filtering 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.
426 OW360_R1005
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.
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.
27.17.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.
27.17.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.
OW360_R1005 427
27.17.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.
27.17.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:
 Advisory Alarm – Indicates conditions that have no current impact of the device’s 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.
428 OW360_R1005
27.17.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) to set alarm limits.
OW360_R1005 429
27.17.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 423).
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:
7. Is the alarm required if the equipment goes offline?

8. 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.
430 OW360_R1005
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.
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.
OW360_R1005 431
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.
27.17.9 What are the benefits of good alarm management?
The following conditions are the result of good alarm management:

 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.
432 OW360_R1005
27.18 What is the Alarm Health Advisor?
27.18 What is the Alarm Health Advisor?
The Alarm Health Advisor is an application that performs statistical analysis on alarm historical
information. Point data is collected from your system database and consolidated with alarm data
from your system historian. The data is parsed and organized when you create a new "solution" at
the Alarm Health Advisor window. You then use this solution information to create various reports.
These reports help identify alarm occurrences that need improvement as well as measure the
performance of the alarm system during normal and abnormal conditions. Reports can provide
alarm summaries based on the plant area, priority, rate, and frequency of alarms.
The Alarm Health Advisor is flexible and easy to customize in order to provide reports that help
you visualize and understand your system's alarm information. This application can run on any
computer using the Windows XP or later operating system, and does not require Ovation to run.
27.18.1 What is the benefit of using the Alarm Health Advisor?
The use of an alarm management strategy is a critical component in reducing plant downtime and
increasing operator productivity. The Alarm Health Advisor is an important component in an
effective alarm management plan.
The occurrence of large numbers of alarms in a plant has the potential to overwhelm an operator
and cause the person to either overlook an important situation, or unnecessarily trip the unit as a
safety measure.
Operators must be able to distinguish between critical events that require intervention, and
nuisance alarms. The Alarm Health Advisor examines the alarm data collected by the Ovation or
WDPF historian and provides the engineers with information necessary to help minimize
unnecessary alarms. This enables plant operators to effectively address real, high-priority alarms
and quickly take appropriate action.
An effective alarm management strategy contributes to plant safety and profitability since it helps
plants achieve higher levels of reliability while reducing operator confusion and errors.
27.18.2 Functions of the Alarm Health Advisor
The data provided by the Alarm Health Advisor can help to achieve the following functionality:
 Identify and create a plan to eliminate nuisance alarms.
 Tune and properly assign alarm priorities.
 Eliminate alarms with the same root cause.
 Identify and eliminate alarms with no associated actions (standing alarms).
 Analyze and compare alarm flood events.
 Measure and compare alarm activity with targeted performance rates.
 Analyze alarm configuration and provide reports for comparison with industry
recommendations.
 Perform analysis for the plant, the unit, or individual subsystems.
 Help users identify when to use Alarm Management features to properly manage Ovation and
WDPF alarms.
OW360_R1005 433
27.19 What is the Alarm Guidance window?
27.19 What is the Alarm Guidance w indow?
The Alarm Guidance window provides a mechanism to view the point-specific alarm guidance
information that can be defined for each point in the system. An example of alarm guidance
information could be the corrective action for an alarm or the cause of the situation.
When the Point Menu is configured to display the Alarm Guidance option, you can access the
Alarm Guidance window from the Point Menu and from all Ovation applications that contain the
Point Menu (such as Point Information, Trend, and so forth). To configure the Alarm Guidance
option from the Point menu, refer to the Ovation Operator Station Configuration Guide.
Figure 112: Ovation Alarm Guidance window
Once the Alarm Guidance window is open, you can send a new point to it either by the Point
menu or by the drag-and-drop operation.
Note: The alarm guidance data is retrieved from the Ovation database. If the Ovation Database
Server is not running, a message appears stating that the alarm guidance data cannot be
retrieved.
The Alarm Guidance window displays both local and remote points, provided the remote point
originates from a system that contains the alarm guidance functionality.
27.20 What is Remote Al arm View er?
Remote Alarm Viewer allows you to view all the alarms for the remote network that the summary
point is from. It is enabled only for remote summary points. Refer to the Ovation Multiple
Networks User Guide for more information.
434 OW360_R1005
S E C T I O N 28
28 Planning Connectivity for your Ovation system
IN THIS SECTION
What is Ovation Connectivity? ........................................................................................ 435

Communication interface spreadsheets .......................................................................... 437
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 that 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.
Consider the following aspects when developing an Ovation Communication interface:

 Platform (see page 435).
 Physical connection (see page 436).
 Message protocol (see page 436).
28.1.1 What are the available platforms for an Ovation communication interface?
There are four platforms that support Ovation communication interfaces:

 Link Controller Module (RLC-G02): 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. Refer to the Ovation Bus and Specialty I/O Reference Manual
for more information.
 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 on to the Ovation Network. The Controller implements
Ethernet TCP/IP communication through software drivers. Refer to the Ovation Controller
User Guide for more information.
 Ethernet Link Controller (ELC): The Ethernet Link Controller is a process controller that
gathers data from remote locations 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.
OW360_R1005 435
28.1 What is Ovation Connectivity?
28.1.2 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 as follows:
 Serial
 RS-232 serial (Recommended Standard 232) is a standard for exchanging messages.
 Ethernet
 TCP/IP (Transmission Control Protocol/Internet Protocol) Ethernet
 Bus technology
 Foundation Fieldbus
 Profibus
 DeviceNet
28.1.3 What are the current message protocols for an Ovation communication
interface?
Message protocols refer to the specifications that define the type of message transmitted over an
Ovation communication interface. The current message protocols are as follows:
 Allen-Bradley DF1
 ControlLogix EIP
 PCCC
 Modbus RTU
 Modbus TCP
 Open Modbus TCP
 DNP
 D-EHC
 MHI Proprietary
 GSM
 GE Proprietary
 OPC
 CSP (PLC5)
 RTP
 Foundation Fieldbus
 Profibus
 DeviceNet
 IEC 61850 MMS
 IEC 60870-5-104
 IEC 60870-5-101
436 OW360_R1005
28.2 Communication interface spreadsheets
The following spreadsheets provide information about the different communication interfaces that
Ovation currently supports:
 Hardware/Device spreadsheet (see page 438). This spreadsheet 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 (see page 440). This spreadsheet contains the following
information:
 Communication interface name.
 Ovation software releases that support the interface.
 Related Ovation documentation to help you connect, configure, and use the interface.
Following are some suggestions for using these 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 step identifies the Ovation software
releases that support your communication interface.
OW360_R1005 437
28.2.1 Hardware/Device spreadsheet
Figure 113: Hardware/Device spreadsheet - Page 1
438 OW360_R1005
OW360_R1005 439
28.2.2 Release version spreadsheet
Figure 116: Release version spreadsheet - Page 1
440 OW360_R1005
OW360_R1005 441
S E C T I O N 29
29 Planning your Ovation Security Center
IN THIS SECTION
What is the Ovation Security Center? ............................................................................. 443

Hardware and software components of the Ovation Security Center ............................. 444
Appliances in the Ovation Security Center ..................................................................... 444
Terminology for the Ovation Security Center .................................................................. 445
29.1 What is the Ovation Security Center?
The Ovation Security Center (OSC) is a suite of hardware and software tools that provide
electronic security management functions. The OSC applications are designed to enhance and
manage cyber security of the Ovation Distributed Control Systems (DCS) without disrupting the
controlled process.
The OSC is comprised of one or more security software applications. Since the OSC is a flexible
and configurable system, you may pick one or several applications to best meet the security
needs of your plant. Infrastructure security is also necessary in meeting the North American
Electric Reliability Corporation (NERC) Critical Infrastructure Protection (CIP) requirements.
OW360_R1005 443
29.2 Hardware and software components of the Ovation Security Center
29.2 Hardw are and software components of the Ovation Security

Center
An OSC system is comprised of several components on an OSC VM Host acting as a

Management Server:
 OSC User Interface (UI): Graphical User Interface used for the installation and configuration
of the virtualization software. Resides on its own physical machine that is connected to a
monitor and keyboard.
 Virtual Machine Host (VMHost): Physical computer on which the virtual machines run.
 Applications/Appliances: Security software that performs a specific security task and runs
as a virtual machine on a host machine.
 Switch: Switch used to connect the OSC UI to the host machine. Also provides connectivity
to Ovation.
 Router: Small physical device that joins networks together.
 vSphere suite of software products: VMware's software products (ESXi and vSphere
Client) that create the virtualization layer on a host machine and allow you to interface with it.
 Network Attached Storage (NAS): Storage system that allows computers to share large
volumes of data across high-speed LAN connections.
 McAfee ESM devices: Used with the SIEM application to collect and analyze network data.
 NID Sensors: Used with the NID application to discover unauthorized access to a computer
network.
In addition to the items listed above, the following items should be installed or applied: <<<PSH:
To check>>>
 Windows Server 2012 R2 SP1 (64-bit).
 Microsoft Critical Patches (latest).
 Microsoft Internet Explorer 11.
 Adobe Reader 11.0.12 (or latest).
 VMware Tools.
Note: If you have purchased Emerson's System Backup and Recovery software package, you
can install it on an OSC VM Host acting as a Management Server. For more information, refer to
the System Backup and Recovery User Guide.
29.3 Appliances in the Ovation Security Center
The Ovation Security Center consists of the following components, plus a User Interface station:
 Patch Management (PM) - Scans the Ovation system for security weaknesses and
distributes patches to remedy these weaknesses.
 Identifies and installs operating system security patches and updates.
 Manages patch deployment scheme.
 Malware Prevention (MP) - Uses a whitelist approach to detect and prevent malware from
executing.
 Allows only whitelisted applications to run in workstations.
 Verifies file integrity to prevent tampering.
444 OW360_R1005
29.4 Terminology for the Ovation Security Center
 Vulnerability Assessment (VA) - Identifies the effectiveness of an enterprise network's

security posture.
 Qualifies the type of assets in a network.
 Identifies the probable areas for compromise.
 Offers solutions on how to remediate vulnerabilities and protect assets.
 Security Incident and Event Manager (SIEM) -Collects, correlates, and reports security
events.
 Combines and normalizes events from multiple devices.
 Correlates events to identify potential security incidents.
 Enables the retention of logs for forensic analysis.
 Network Intrusion Detection (NID) - Attempts to discover unauthorized access to a
computer network by analyzing traffic on that network for signs of malicious activity
 Detects sophisticated network intrusion attempts.
 Provides deep-packet inspection capabilities.
 Antivirus (AV) - Provides virus protection for Ovation Windows stations.
The following terms and descriptions may be helpful while using this manual.
Terminology for Ovation Security Center
TERM DESCRIPTION
Air gap This is a security measure used for computers and computer networks that must be
extraordinarily secure. An air gap ensures that a secure network is physically,
electrically, and electromagnetically isolated from non-secure networks, such as
the public Internet or from a non-secure local area network.
APM ANSA Patch Manager (APM) scans the Ovation system for security weaknesses
and distributes patches to remedy these weaknesses.
Appliance (Software) A pre-configured virtual machine that typically includes a preinstalled guest
operating system and other software.
Blacklist This is a list of software programs considered unsafe to run on your system. A
blacklist uses the standard signature-based, antivirus approach to security by
blocking any known harmful software or users from the system. See also Whitelist.
CIFS Common Internet File System (CIFS) that operates as an application-layer network
protocol used to provide shared access to files, printers, serial ports, and
miscellaneous communications between nodes on a network.
CIP Critical Infrastructure Protection (CIP) is a set of cyber security standards for
electric power generation, transmission, and distribution organizations. The North
American Electric Reliability Corporation (NERC) developed CIP standards with
oversight from the Federal Energy Regulatory Commission (FERC).
Client tasks Client tasks are specific actions that an endpoint can run. These are assigned to
groups of endpoints or endpoints individually.
OW360_R1005 445
TERM DESCRIPTION
CM Configuration Management (CM) provides an environment to audit configuration

management and the system state of monitored nodes and the option to check
compliance against a pre-established security policy.
DMZ Demilitarized Zone (DMZ) is a network that sits between a trusted internal network
such as a corporate private LAN, and an untrusted external network, such as the
public Internet. The purpose of a DMZ is to add an additional layer of security to an
organization's Local Area Network (LAN). An external attacker would only have
access to equipment in the DMZ, rather than the entire network.
Endpoint In a client/server network architecture, an endpoint is any node that is a destination
of two-way communication, whether requesting or responding (for example, PCs,
laptops, and other similar devices).
The term endpoint in the Lumension Endpoint Management and Security Suite is
similar to a computer in your network that can have an agent installed.
ePO ePolicy Orchestrator (ePO) is a graphical user interface that you can use to
perform various tasks on the McAfee applications.
ESXi Virtualization server software.
Extensions Extensions are additions to the Management Suite Server in order to facilitate the
use of software packages. These are installed on the ePO Server.
FERC Federal Energy Regulatory Commission (FERC) is a United States federal agency
that has jurisdiction over and makes rules for interstate electricity sales and other
energy related rates and pricing.
Firewall A Firewall is a security system intended to protect your computer network from
external threats. All communication between the internal computer network and the
outside world is routed through a server that determines if a message is safe to
pass to the internal network.
Guardian Guardian is an Emerson-provided interface that can provide all the available
information about a system, such as system level, software level, loaded patches,
SureService information, site contacts, Emerson contacts, and related knowledge-
based articles.
Guest OS A guest OS is an operating system that is installed on a virtual machine in addition
to the host or main OS. In virtualization, a single computer can run more than one
OS at the same time. In a virtualization solution, a guest OS can be different from
the host OS.
Hive The name given to a major section of the Windows Registry that contains registry
keys, registry subkeys, and registry values.
Host The physical computer on which ESXi is installed. All virtual machines run on
hosts. If the vSphere Client is connected directly to an ESXi host, only that host is
available for management.
Hypervisor Piece of computer software, firmware, or hardware that creates and runs virtual
machines.
MAC McAfee Application Control (MAC) enables you to prevent the execution of
malicious code and unwanted software through an approach called application
whitelisting. This method allows only authorized applications to run on endpoints.
MAV McAfee Antivirus (MAV) prevents, detects, and removes all forms of malicious
software, such as computer viruses, Trojan horses, worms, and so forth.
McAfee agent McAfee agent is used for endpoints to communicate to the server for all application
activities.
446 OW360_R1005
TERM DESCRIPTION
MDC McAfee Device Control (MDC) enforces flexible usage policies for removable
devices, media, and data. In addition, it provides the capability to limit potential
data leakage or threats from unknown devices.
Malware Malware refers to any software (such as a virus) that has the potential to disrupt a
computer system. Malware is malicious software or executable programs that
should not be executing on a system.
Management The management console is a defined machine on the DCS that controls the
Console administration of your Ovation Security Center.
NID Network Intrusion Detection (NID) attempts to discover unauthorized access to a
computer network by analyzing traffic on that network for signs of malicious activity.
 Detects sophisticated network intrusion attempts.
 Provides deep-packet inspection capabilities.
NERC North American Electric Reliability Corporation (NERC) is an agency that oversees
the reliability and adequacy of bulk power supply in electric utility systems.
OSC Ovation Security Center (OSC) is a suite of hardware and software tools
(appliances) that provide electronic security management functions.
Packages Packages are software that are installed in your environment. Packages are
checked into ePO to be managed.
Passphrase A sequence of words used to log on to your system. For example: The
Performance Received a Standing Ovation in 2010. Often used in combination with
a password.
Policies Policies are used to manage applications in a centralized manner.
Policy Assignment Policy Assignment Rules are rules that can dynamically change policies on the
Rules basis of endpoint criteria.
Product deployment Product deployment is a mechanism to deploy software to endpoints.
OSC UI Graphical User Interface used for the installation and configuration of the
virtualization software. Resides on its own physical machine that is connected to a
monitor and keyboard.
OVF template Open Virtualization Format (OVF) is an open standard for packaging and
distributing virtual appliances, or more generally, software to be run in virtual
(OVA template) machines.
OVF is not only the name of the packaging format standard, but it also refers to the
package when distributed as a group of files.
An OVA (open virtual appliance or application) is a single file distribution of the
same file package, stored in the TAR format.
Root kit Software program that can evaluate the privileges to the root level of your
computer. The program then uses the evaluated information to gain access
(access unknown to the system's owners and legitimate managers) and control of
that computer.
RSD McAfee Rogue System Detection (RSD) provides near real-time discovery of rogue
systems by using Rogue System Sensors installed throughout your network. These
sensors use various passive and active network discovery techniques to detect
systems connected to the network.
SmartProcess SmartProcess software provides adaptive solutions that achieve optimum
performance for equipment in a power plant. SmartProcess uses fuzzy logic, neural
networks, predictive control, and other tools to offer the most advanced suite of
optimization solutions available.
OW360_R1005 447
TERM DESCRIPTION
SIEM Security Incident and Event Manager (SIEM) collects, correlates, and reports
security events.
 Combines and normalizes events from multiple devices.
 Correlates events to identify potential security incidents.
 Enables the retention of logs for forensic analysis.
SMB Server Message Block (SMB), also known as CIFS, is an application-level network
protocol applied to shared access to files, printers, serial ports, and miscellaneous
communications between nodes on a network.
SMTP Simple Mail Transfer Protocol (SMTP) is an Internet standard for email
transmission across Internet Protocol (IP) networks.
SNMP Simple Network Management Protocol (SNMP) is a User Datagram Protocol (UDP-
based) network protocol. It is used for network management systems to monitor
network-attached devices for conditions requiring administrative attention. SNMP
consists of a set of standards for network management.
Tags Tags are used in classifying endpoints and automating tasks.
Trojan horse A Trojan horse is software that appears to perform a useful and harmless action,
but in fact performs another action that can harm your computer, such as
transmitting a computer virus.
UTC Coordinated Universal Time is the primary time standard by which the world
regulates clocks and time.
Virtual Machine A virtualized computer environment in which a guest operating system and
associated application software can run. Multiple virtual machines can operate on
the same managed host machine concurrently.
VPN Virtual Private Network (VPN) is a type of computer network. In a VPN some of the
links between nodes are carried by open connections and in larger networks, (for
example, the Internet), by virtual circuits instead of by physical wires.
TE Tripwire Enterprise (TE) software is used for Configuration Management (CM).

Wave Refers to the staged process used to install new antivirus software so the DCS
system is not disrupted. Typically, three stages (or waves) are used: First wave
would send antivirus software to non-critical drops. If the first wave goes well, then
the second wave would send the antivirus software to moderately critical drops. If
the second wave goes well, then the third wave would send the antivirus software
to very critical drops.
Whitelist A list of software programs considered safe to run on your system. Software
programs not on the whitelist are blocked. See also Blacklist.
WMI Windows Management Instrumentation (WMI) is the Microsoft implementation of

Web-Based Enterprise Management (WBEM). It is the primary management
technology for Windows operating systems, permitting management information to
be shared between management applications.
vSphere A package name for a suite of software products that are part of VMware's family of
data center products. The vSphere suite has many software components such as
vCenter, ESXi, vSphere Client, and so on.
vSphere Client Software installed on client machines. Used from a client machine to connect the
ESXi server and perform management tasks.
448 OW360_R1005
S E C T I O N 30
30 Planning your Safety Instrumented System
IN THIS SECTION
What is a Safety Instrumented System? ......................................................................... 449

Functions of Ovation SIS ................................................................................................ 450
Safety Instrumented System terminology ....................................................................... 450
SIS aspects to consider .................................................................................................. 452
Capacities for Ovation SIS system.................................................................................. 453
SIS environmental specifications for Ovation SIS devices ............................................. 454
SIS System ...................................................................................................................... 454
Supported SIS network ................................................................................................... 455
Planning the SIS hardware installation ........................................................................... 485
Hardware components of Ovation SIS ............................................................................ 485
Software components of Ovation SIS ............................................................................. 487
What are Ovation SIS Logic Solver algorithms? ............................................................. 489
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.
Note: Throughout this manual, IP addresses are shown with "127" as the first octet. These IP
addresses are for example purposes only and should not be used in an actual SIS system.
Contact your Emerson project representative for assistance in obtaining the IP addresses for
your system.
OW360_R1005 449
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 Safety Instrumented System terminology

TERM DESCRIPTION
SIS Algorithms SIS Algorithms are self-contained software modules that reside in the Logic Solvers.
Backplane Backplane is the electronic bus that is part of an SIS carrier. Backplane carries
signals between the Logic Solvers and the SIS Data Server.
SIS Interface Ovation Controller configured to handle the communication of SIS process data
Controller (CIS) between the SIS network and the Ovation network.
Control Module When a Logic Server is added to the Studio, four control modules are automatically
created and appear under the Logic Solver in the Studio tree. The control sheets are
stored in the control modules. All the control sheets stored in a control module are
scanned at the same frequency.
CRC Cyclic Redundancy Check (CRC) is a mathematical function designed to detect
changes to computer data and is commonly used in digital communications and data
storage. A CRC-enabled device calculates CRC code for each block of data. When a
new block is received, the device repeats the calculation; if the new CRC code does
not match the old CRC code, this indicates that there is a difference between the two
blocks of data. This means there is either a data error or a change in the
configuration of the data.
DHCP Dynamic Host Configuration Protocol (DHCP) is a network application protocol used
by devices to obtain configuration information for operation in an Internet Protocol
network. This allows networks to add devices with little or no manual intervention.
HAZOP Hazard and Operational Studies. These are requirements for SIS projects.
IP Address Unique number consisting of four parts separated by dots. An example of an IP

address is 127.228.36.38. Every computer that is on the Internet has a unique IP
address.
Local bus Communications between Logic Solvers and one SIS Data Server. Achieved via
backplanes and extender cables.
Local SISNet Communications of safety data among Logic Solvers connected to one SIS Data
(Local peer bus) Server. Achieved via carrier backplanes and coaxial extender cables.
LOPA Layers of Protection Analysis. Requirements for SIS projects.
450 OW360_R1005
30.3 Safety Instrumented System terminology
TERM DESCRIPTION
Netmask The netmask (also known as an address mask) is a number that identifies the range
of IP addresses that are on a local network. The netmask serves as a filter that
enables a computer to determine whether it can transfer data directly to another
machine on the local network or if the computer must use a router to transfer data.
NAMUR NAMUR is an international association of automation technology in process control
industries. NAMUR alarming can be performed on I/O channels. The NAMUR limits
are 106.25% top limit and -2.5% bottom limit.
NTP task Network Time Protocol. Synchronizes time between the Ovation Controller, SIS Data
Servers, and its attached Logic Solvers and SIS switches.
Remote SISNet Communications among Logic Solvers connected to different SIS Data Servers.
(Remote peer bus) Achieved via SISNet Repeaters and a fiber optic loop
Shadow algorithm Describes SIS algorithms when they are loaded into the Ovation Controller. The
algorithms are not actually used by the Controller for control, but serve as a visual
representation to the user of the algorithms in the Logic Solver.
SIF See Safety Instrumented Function (see page 453) for more information.
SIL See Safety Integrity Level (see page 453) for more information.
SIS Force Force operation occurs when a value and quality for an algorithm input parameter
(pin) is manually changed, typically for testing purposes.
SIS hardware Refers to the hardware needed for an SIS project. See Hardware components (see
page 485) for more information.
SIS LAN Segment of the SIS Network that exists between the SIS Interface Controller and the
SIS Data Servers assigned to that SIS Interface Controller. It covers the network
redundancy. The SIS Routers can be shared between multiple SIS LANs.
SIS point An Ovation point that has been used on an SIS control sheet. After the sheet is saved
and loaded to a Logic Solver, the point can then be used in SIS control schemes. SIS
points can be analog or digital points.
SISNet Ring Fiber optic based ring topology network made between SIS Network Repeaters.
SISNet Ring is used for Global Secure Parameters communication. The SISNet Ring
can exist between different SIS Interface Controller's SIS Data Servers.
SIS Write SIS Write provides for the validation of messages between Ovation Operator Stations
and the Logic Solvers. This function greatly reduces the risk of sending an invalid
message to the safety system from the Ovation system.
SNMP Simple Network Management Protocol (SNMP) is used in network management
systems to monitor network-attached devices.
SIS System In SIS System, the SIS Switches Network, all the SISNet Rings, all the SIS Interface
Controllers, and the corresponding SIS Data Servers are connected.
SIS Switch Cisco IE 3000 Switch in a redundant configuration; two Cisco IE 300 Switches shared
between Ovation Interface Controller and the corresponding SIS Data Servers.
SIS Router Single Cisco 2901 router. SIS network has a requirement for two routers that work as
a redundant pair.
SIS Data Server An SIS Data Server provides the interface between the Ovation Controller, Logic
(SDS) Solvers, and SISNet Repeaters.
SISNet Repeater SISNet Repeater provides the secure communication between the Logic Solvers that
are attached to different SIS Data Servers.
Logic Solver (SLS Logic Solvers are hardware modules that have logic solving capability and provide an
1508) interface to a maximum of 16 user configurable I/O channels.
OW360_R1005 451
30.4 SIS aspects to consider
30.4 SIS aspects to consider
A Safety Instrumented System (SIS) is a form of process control usually implemented in industrial
processes, such as those in a Power generation or Waste water plant. The SIS performs
specified functions to achieve or maintain a safe state of the process when unacceptable or
dangerous process conditions are detected.
Consider the following aspects when planning a SIS project:

 The safe state is a state of the process operation where the hazardous event cannot occur.
You should be able to achieve a safe state within one-half of the process safety time.
 Even though Safety Instrumented Systems are composed of elements that are similar to
elements in a process control system (such as sensors, logic solvers, actuators, and support
systems), you should keep the safety system separate and independent from your regular
control systems.
 The specified functions, or Safety Instrumented Functions (SIF (see page 453)) should be
implemented as part of an overall risk reduction strategy since they are intended to reduce
the likelihood of a catastrophic release and create a safe state.
 The correct operation of an SIS requires a series of equipment to function properly, such as
the following:
 Sensors capable of detecting abnormal operating conditions, such as high flow, low level,
or incorrect valve positioning.
 Logic Solvers that receive the sensor input signal(s), make appropriate decisions based
on the nature of the signal(s), and change its outputs according to user-defined logic.
 Final elements that take action on the process (for example, closing a valve) to bring it to
a safe state due to changes in Logic Solver output.
 Support systems, such as power and communications, are generally required for SIS
operation. The support systems should be designed to provide the required integrity and
reliability.
 Functional and safety integrity requirements for an SIS are determined from hazard and
operability studies (HAZOP), layers of protection analysis (LOPA), risk graphs, and so on. All
techniques are mentioned in IEC 61511 and IEC 61508.
 You need to verify that during SIS design, construction, and operation, these functional
and safety requirements are met.
 You can verify functional requirements by design reviews, such as failure modes, effects,
and diagnostic analysis (FMEDA). You can also use various types of testing, such as
factory acceptance testing, site acceptance testing, and regular functional testing.
 You can verify safety integrity requirements by reliability analysis. For SIS that operates
on demand, it is often the probability of failure on demand (PFD) that is calculated. In the
design phase, the PFD may be calculated using generic reliability data. Later on, the
initial PFD estimates may be updated with field experience from the specific plant in
question.
 Since it is not possible to address all factors that affect SIS reliability through reliability
calculations, you should also have adequate measures in place (for example, processes,
procedures, and individual training and certification) to avoid, reveal, and correct SIS
related failures
452 OW360_R1005
30.5 Capacities for Ovation SIS system
30.4.1 Safety Instrumented Functions (SIFs)
Safety Instrumented Systems are applied to a process to substantially reduce the risk from costly
or dangerous failures in industrial processes. The magnitude of risk reduction needed is
determined from an analysis of the severity of hazardous process events and their probability of
occurrence.
Safety Instrumented Systems are typically comprised of multiple Safety Instrumented Functions
(SIFs). Each SIF can be considered a control loop, defining:
 Measurements (sensors) to use.
 Actions to take (control elements to drive).
 When to apply the actions (logic linking the measurements to the actions).
 How fast to measure and react.
Every SIF has a Safety Integrity Level (SIL (see page 453)) assigned to it.
30.4.2 Safety Integrity Levels (SILs)
Every SIF has a Safety Integrity Level (SIL) assigned to it. SIL is a measure of the risk reduction
provided by a SIF based on four discrete levels, each representing an order of magnitude of risk
reduction. The factors considered in determining a SIL include:
 Device integrity.
 Diagnostics.
 Failures.
 Testing.
 Operation.
 Maintenance.
30.5 Capacities for Ovation SIS s ystem
The following table lists various components of the Ovation SIS system with their capacities:
Capacities for Ovation SIS system
COMPONENT MAXIMUM LIMIT
SISNet Rings in a System 32

SIS Interface Controllers per System 8
SIS Data Server (SDS) per SIS Interface Controller 4
SIS Data Server (SDS) per System 32
Logic Solvers per SIS Data Server 32 (simplex), 16 (redundant)
Logic Solvers in a SIS System 512 (simplex or redundant)
I/O channels in a SIS System 8192
I/O channels per SIS Interface Controller 1024
SISNet Repeater pairs in an Ovation SIS System 32
OW360_R1005 453
30.6 SIS environmental specifications for Ovation SIS devices
Logic Solvers that can publish data globally on a SISNet Ring 32

SIS Control Modules in a Logic Solver 4
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 8
Server
Secure Parameters published globally per SISNet Ring 512
30.6 SIS environmental specifications for Ovation SIS devices
The following table provides the environmental specification for normal operation of Ovation SIS
devices.
SIS environmental specifications
SPECIFICATION DESCRIPTION
Storage temperature -40°C to 85°C (-40°F to 185°F)

Operating temperature -40°C to 70°C (-40°F to 158°F)
Relative humidity 5 to 95%, non-condensing
Airborne contaminants Severity level G3
Protection rating IP 20, NEMA 12
Shock 10 g half-sine wave for 11 ms
Vibration 1 mm peak-to-peak from 5 to 16 Hz; 0.5 g from 16 to 150 Hz
Electromagnetic compatibility Per EN61326-1, Criteria A and Namur NE21
30.7 SIS System
In Ovation 3.5.0 and earlier releases, the Ovation SIS System had limitation of having only one
Ovation SIS Interface Controller per system and that was supporting 1024 I/Os with a maximum
of four (4) SIS Data Severs and a maximum of 64 Logic Solvers (Simplex or Redundant pair of
Logic solvers) with any combination. Also, the SISLAN and the SISNet Ring were the same entity.
With Ovation 3.5.1 release, the Ovation SIS System would support up to 8192 I/Os. That is, the
Ovation SIS system now supports a maximum of eight (8) redundant Ovation SIS Interface
Controllers with a maximum of 32 SIS Data Servers. Also, the SIS LAN and the SISNet Rings are
treated as separate entities.
Note: The Ovation SIS Interface Controller supports a maximum of 1024 SIS hardware I/Os.
454 OW360_R1005
30.8 Supported SIS network
30.8 Supported SIS netw ork
Ovation 3.6.0 supports up to four (4) redundant SIS Switches (Cisco IE 3000) in the network.
Each switch has eight (8) ports and can be extended up to 24 ports. This configuration supports
the maximum considered number of the SIS Interface Controllers and the SIS Data Servers. The
number of the SIS Switches in the network is always an even number, and they are always used
in a redundant configuration.
Note: Network is designed to handle single link or single device failure only.
There are many different ways to design an SIS network. Each system has the unique
requirements that must be considered when planning the SIS network.
The following SIS network design examples illustrate the different design types:
 SIS Network with four (4) SIS Switches (see page 455).
 SIS Network with three (3) SIS Switches (see page 465).
 SIS Network with two (2) SIS Switches (see page 471).
 SIS Network with one (1) SIS Switch (see page 476).
30.8.1 SIS Network with four (4) SIS Switches
The SIS Network with four (4) SIS Switches architecture supports one (1) redundant SIS Router,
four (4) redundant SIS Switches, eight (8) redundant SIS Interface Controllers, and 32 redundant
SIS Data Servers.
The procedure for connecting SIS components in this SIS network architecture is as follows:
1. Make the connection between the SIS Router and the Ovation Switch using port Fast
Ethernet 0/0 on the SIS Router and port 24 on the Ovation Switch.
2. Repeat Step 1 for the Backup SIS Router and the Ovation Switch.
3. Make the connection between the SIS Router and the SIS Switch using Fast Ethernet 0/1 on
the SIS Router and Fast Ethernet port 1/1 on the SIS Switch.
4. Repeat Step 3 for the Backup SIS Router and SIS Switch.
5. The SIS Router should be connected to any SIS Switch available in the network. Make sure
Primary Router is connected to the Primary SIS Switch and the Backup Router is connected
to the Backup SIS Switch.
6. The Backup SIS Switch does not need to be the Partner of the first SIS Switch used for the
SIS Router connection.
7. All the SIS Switches available in the network should be connected in to the ring topology
through the Gigabit Ethernet or SFPs. Connecting all SIS Switches together allows you to
have one redundant pair of SIS Routers.
8. All the redundancy connections between switches should be made by using cross-over
cables.
9. Do not use the SIS Switch Fast Ethernet port 1/2 if the SIS Switch is configured to be
connected with a SIS Router.
10. Use the Fast Ethernet ports 1/3, 1/ 4, 1/ 5 and 1/6 on the Primary SIS Switch for connecting
the SIS Interface Controller N1 interface.
OW360_R1005 455
11. Use the Fast Ethernet ports 1/3,1/ 4,1/ 5 and 1/6 on the Backup SIS Switch for connecting the
SIS Interface Controller N4 interface.
12. SIS Data Servers must be connected to the SIS Switches starting from the Fast Ethernet port
1/7.
13. All of the SIS Data Servers must be connected to the same SIS Switch where the SIS
Interface Controller is connected.
14. Maintain the redundancy between the Ovation Switches using ports 2 and 3.
The following tables show the SIS Switches port usages:
First switch ( switch number 1) in ring network
PORT USAGE
Gi1/1 Gi1/2 of switch number 4_B

Fa1/1 Fa0/1 of Pri router
Fa1/2 Not used
Fa1/3 N1 of Controller 1
Fa1/4 N1 of Controller 1_B
Fa1/7 Pri of SDS 01
Fa1/8 Pri of SDS 01_B
Fa2/1 Pri of SDS 02
Fa2/3 Pri of SDS 03
Fa2/5 Pri of SDS 04
Fa2/7 Pri of SDS 05
Fa3/1 Pri of SDS 06
Fa3/3 Pri of SDS 07
Fa3/5 Pri of SDS 08
Fa3/7 Not used
Fa3/8 Not used
456 OW360_R1005
Second switch (switch number 1_B) in ring network
PORT USAGE
Gi1/1 Gi1/2 of switch number 1

Fa1/1 Fa0/1 of Sec router
Fa1/2 Not used
Fa1/7 Sec of SDS 01
Fa1/8 Sec of SDS 01_B
Fa2/1 Sec of SDS 02
Fa2/3 Sec of SDS 03
Fa2/5 Sec of SDS 04
Fa2/7 Sec of SDS 05
Fa3/1 Sec of SDS 06
Fa3/3 Sec of SDS 07
Fa3/5 Sec of SDS 08
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 457
Third switch (switch number 2) in ring network
PORT USAGE

Fa1/5 Pri of SDS 09
Fa1/7 Pri of SDS 010
Fa2/1 Pri of SDS 11
Fa2/3 Pri of SDS 12
Fa2/5 Pri of SDS 13
Fa2/7 Pri of SDS 14
Fa3/1 Pri of SDS 15
Fa3/3 Pri of SDS 16
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
458 OW360_R1005
Fourth switch (switch number 2_B) in ring network
PORT USAGE

Fa1/5 Sec of SDS 09
Fa1/7 Sec of SDS 10
Fa2/1 Sec of SDS 11
Fa2/3 Sec of SDS 12
Fa2/5 Sec of SDS 13
Fa2/7 Sec of SDS 14
Fa3/1 Sec of SDS 15
Fa3/3 Sec of SDS 16
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 459
Fifth switch (switch number 3) in ring network
PORT USAGE

Fa1/5 Pri of SDS 17
Fa1/7 Pri of SDS 18
Fa2/1 Pri of SDS 19
Fa2/3 Pri of SDS 20
Fa2/5 Pri of SDS 21
Fa2/7 Pri of SDS 22
Fa3/1 Pri of SDS 23
Fa3/3 Pri of SDS 24
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
460 OW360_R1005
Sixth switch (switch number 3_B) in ring network
PORT USAGE

Fa1/5 Sec of SDS 17
Fa1/7 Sec of SDS 18
Fa2/1 Sec of SDS 19
Fa2/3 Sec of SDS 20
Fa2/5 Sec of SDS 21
Fa2/7 Sec of SDS 22
Fa3/1 Sec of SDS 23
Fa3/3 Sec of SDS 24
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 461
Seventh switch (switch number 4) in ring network
PORT USAGE

Fa1/5 Pri of SDS 25
Fa1/7 Pri of SDS 26
Fa2/1 Pri of SDS 27
Fa2/3 Pri of SDS 28
Fa2/5 Pri of SDS 29
Fa2/7 Pri of SDS 30
Fa3/1 Pri of SDS 31
Fa3/3 Pri of SDS 32
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
462 OW360_R1005
Eighth switch (switch number 4_ B) in ring network
PORT USAGE

Fa1/5 Sec of SDS 25
Fa1/7 Sec of SDS 26
Fa2/1 Sec of SDS 27
Fa2/3 Sec of SDS 28
Fa2/5 Sec of SDS 29
Fa2/7 Sec of SDS 30
Fa3/1 Sec of SDS 31
Fa3/3 Sec of SDS 32
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 463
Note: Cisco IE 3000 switches have two pairs of Dual Purpose ports. A Dual Purpose port can
be configured as either a 10/100/1000 port or a SFP module port.
Using SFPs and fiber optics allow connecting the switches over greater distances than using the
copper connections. When SIS Switches are separated by distance greater than copper
standards allow, fiber optics connections can be used without additional external converters.
Figure 120: SIS Network with Four (4) SIS Switches
464 OW360_R1005
30.8.2 SIS Network with three (3) SIS Switches
The SIS network with three (3) SIS Switches architecture supports one (1) redundant SIS Router,
three (3) SIS Switches, six (6) redundant SIS Interface Controllers, and 24 redundant SIS Data
Servers.
The procedure for connecting the SIS components in this SIS network architecture is same as the
procedure for connecting the SIS components in the SIS network with four (4) SIS Switches (see
page 455).
First switch (switch number 1) in ring network
PORT USAGE

Fa1/2 Not used
Fa1/7 Pri of SDS 01
Fa2/1 Pri of SDS 02
Fa2/3 Pri of SDS 03
Fa2/5 Pri of SDS 04
Fa2/7 Pri of SDS 05
Fa3/1 Pri of SDS 06
Fa3/3 Pri of SDS 07
Fa3/5 Pri of SDS 08
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 465
PORT USAGE

Fa1/2 Not used
Fa1/7 Sec of SDS 01
Fa2/1 Sec of SDS 02
Fa2/3 Sec of SDS 03
Fa2/5 Sec of SDS 04
Fa2/7 Sec of SDS 05
Fa3/1 Sec of SDS 06
Fa3/3 Sec of SDS 07
Fa3/5 Sec of SDS 08
Fa3/7 Not used
Fa3/8 Not used
466 OW360_R1005
PORT USAGE

Fa1/5 Pri of SDS 09
Fa2/1 Pri of SDS 11
Fa2/3 Pri of SDS 12
Fa2/5 Pri of SDS 13
Fa2/7 Pri of SDS 14
Fa3/1 Pri of SDS 15
Fa3/3 Pri of SDS 16
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 467
PORT USAGE

Fa1/5 Sec of SDS 09
Fa1/7 Sec of SDS 10
Fa2/1 Sec of SDS 11
Fa2/3 Sec of SDS 12
Fa2/5 Sec of SDS 13
Fa2/7 Sec of SDS 14
Fa3/1 Sec of SDS 15
Fa3/3 Sec of SDS 16
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
468 OW360_R1005
Fifth switch (switch number 3) in ring network
PORT USAGE

Fa1/5 Pri of SDS 17
Fa1/7 Pri of SDS 18
Fa2/1 Pri of SDS 19
Fa2/3 Pri of SDS 20
Fa2/5 Pri of SDS 21
Fa2/7 Pri of SDS 22
Fa3/1 Pri of SDS 23
Fa3/3 Pri of SDS 24
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 469
Sixth switch (switch number 3_B) in ring network
PORT USAGE

Fa1/5 Sec of SDS 17
Fa1/7 Sec of SDS 18
Fa2/1 Sec of SDS 19
Fa2/3 Sec of SDS 20
Fa2/5 Sec of SDS 21
Fa2/7 Sec of SDS 22
Fa3/1 Sec of SDS 23
Fa3/3 Sec of SDS 24
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
470 OW360_R1005
Figure 121: SIS Network with three (3) SIS Switches
OW360_R1005 471
30.8.3 SIS Network with two (2) SIS Switches
The SIS network with two (2) SIS Switches architecture supports one (1) redundant SIS Router,
two (2) redundant SIS Switches, four (4) redundant SIS Interface Controllers, and 16 redundant
SIS Data Servers.
page 455).
PORT USAGE

Fa1/2 Not used
Fa1/7 Pri of SDS 01
Fa2/1 Pri of SDS 02
Fa2/3 Pri of SDS 03
Fa2/5 Pri of SDS 04
Fa2/7 Pri of SDS 05
Fa3/1 Pri of SDS 06
Fa3/3 Pri of SDS 07
Fa3/5 Pri of SDS 08
Fa3/7 Not used
Fa3/8 Not used
472 OW360_R1005
PORT USAGE

Fa1/2 Not used
Fa1/7 Sec of SDS 01
Fa2/1 Sec of SDS 02
Fa2/3 Sec of SDS 03
Fa2/5 Sec of SDS 04
Fa2/7 Sec of SDS 05
Fa3/1 Sec of SDS 06
Fa3/3 Sec of SDS 07
Fa3/5 Sec of SDS 08
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 473
PORT USAGE

Fa1/5 Pri of SDS 09
Fa2/1 Pri of SDS 11
Fa2/3 Pri of SDS 12
Fa2/5 Pri of SDS 13
Fa2/7 Pri of SDS 14
Fa3/1 Pri of SDS 15
Fa3/3 Pri of SDS 16
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
474 OW360_R1005
PORT USAGE

Fa1/5 Sec of SDS 09
Fa1/7 Sec of SDS 10
Fa2/1 Sec of SDS 11
Fa2/3 Sec of SDS 12
Fa2/5 Sec of SDS 13
Fa2/7 Sec of SDS 14
Fa3/1 Sec of SDS 15
Fa3/3 Sec of SDS 16
Fa3/5 Not used
Fa3/6 Not used
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 475
Figure 122: SIS Network with two (2) SIS Switches
30.8.4 SIS Network with one (1) SIS Switch
SIS network with one (1) SIS Switch architecture supports one (1) redundant SIS Router, one (1)
redundant SIS Switch, two (2) redundant SIS Interface Controllers, and eight (8) redundant SIS
Data Servers.
page 455).
PORT USAGE

Fa1/2 Not used
476 OW360_R1005
PORT USAGE
Fa1/7 Pri of SDS 01
Fa2/1 Pri of SDS 02
Fa2/3 Pri of SDS 03
Fa2/5 Pri of SDS 04
Fa2/7 Pri of SDS 05
Fa3/1 Pri of SDS 06
Fa3/3 Pri of SDS 07
Fa3/5 Pri of SDS 08
Fa3/7 Not used
Fa3/8 Not used
OW360_R1005 477
PORT USAGE

Fa1/2 Not used
Fa1/7 Sec of SDS 01
Fa2/1 Sec of SDS 02
Fa2/3 Sec of SDS 03
Fa2/5 Sec of SDS 04
Fa2/7 Sec of SDS 05
Fa3/1 Sec of SDS 06
Fa3/3 Sec of SDS 07
Fa3/5 Sec of SDS 08
Fa3/7 Not used
Fa3/8 Not used
478 OW360_R1005
Figure 123: SIS Network with one (1) SIS Switches
OW360_R1005 479
30.8.5 Hardware cabinet design example
Ovation SIS cabinets are metal enclosures that contain the SIS Interface Controller, power
supplies, SIS Data Server, and Logic Solvers in different combinations.
Example of SIS hardware cabinets are shown below:
Example 1:
Horizontal Installation
 Cabinet width 800mm.

 Installation with the following cables:
 KJ4002X1-BF3-PW (Local Bus, D44M-D44F 31").
 KJ4010X1-BL2-PW (SISNet, Coax, Black 33").
 KJ4010X1-BM2-PW (SISNet, Coax, White 33").
Note: Do not exceed six, eight-wide carrier limit in this arrangement.
480 OW360_R1005
Figure 124: Horizontal installation with cabinet width of 800mm
OW360_R1005 481
Example 2:
Horizontal Installation
 Cabinet Width 1200mm.

 KJ4002X1-BF2-PW (Local Bus, D44M-D44F 44").
Note: Do not exceed eight, eight-wide carrier limit in this arrangement.
Figure 125: Horizontal installation with cabinet width of 1200mm
482 OW360_R1005
Example 3:
Vertical Installation
 Cabinet Width 600mm

 KJ4003X1-BH1-PW (Local Bus, D25M-D25 43").
Figure 126: Vertical installation with cabinet width of 600mm
OW360_R1005 483
Example 4:
Vertical Installation
 Cabinet Width 1200mm

 KJ4003X1-BH2-PW (Local Bus, D25M-D25 17").
Figure 127: Vertical installation with cabinet width of 1200mm
484 OW360_R1005
30.9 Planning the SIS hardware installation
30.9 Planning the SIS hardw are installation
The following list provides an overview of the basic SIS hardware installation. Refer to the specific
sections for installation details.
15. Install appropriate carriers on the DIN rails in a hardware cabinet.

16. Install terminal blocks onto a carrier.
17. Install the SIS Data Servers onto a carrier.
18. Install Logic Solvers onto the terminal block.
19. Connect the field wiring.
20. Install the SISNet Repeaters.
21. Install extender cables.
22. Terminate the local bus.
23. Provide power to:
 SIS Data Servers
 SIS Logic Solvers.
 SISNet Repeaters.
 SISNet Extenders.
24. If desired, install auxiliary equipment.
30.9.1 Installation tools
The following tools are needed to install standard Ovation SIS:

 Standard electrical tools (voltmeter, wire cutter, wire stripper, pliers, screwdrivers).
 Standard installation tools (screwdrivers, drill with standard bits).
 Ethernet cable tools (crimper, cable tester).
OW360_R1005 485
30.10 Hardware components of Ovation SIS
30.10 Hardw are components of Ovation SIS
The SIS System contains various hardware components that are described in the following table.
Note: For information about 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 Logic Solvers and terminal blocks.
Simplex terminal block Interfaces between I/O devices and one Logic Solver that acts in a simplex
configuration.
Redundant terminal block Interfaces between I/O devices and two Logic Solvers that act in a redundant
configuration.
SIS Interface Controller Provides an interface between Ovation and the SIS Data Server.
SIS Data Server Provides the interface between the SIS Interface Controller and Logic
Solvers and SISNet Repeaters. The SIS Data Server can manage up to 32
simplex or 16 redundant Logic Solvers.
SIS Logic Solvers Hardware modules that contain logic solving capability and provide an
interface to a maximum of 16 user configurable I/O channels.
SISNet Repeaters Provides secure communication between Logic Solvers that are connected
to different SIS Data Servers.
Fiber optic cable/ring SISNet Repeaters connected to an SIS Data Server communicate with
another SISNet Repeater connected to a different SIS Data Server.
Carrier Extender cables Connects power and signals between eight-wide carriers.
SISNet Distance Extender Permits SISNet Repeaters to communicate over greater distances.
Power Supply Provides power to the SIS Data Server.
486 OW360_R1005
30.10 Hardware components of Ovation SIS
The following graphic illustrates the SIS hardware components in a typical system.
Figure 128: SIS Hardware components
OW360_R1005 487
30.11 Software components of Ovation SIS
30.11 Softw are components of Ovation SIS
The following table lists various software components of the Ovation SIS:
Software components of Ovation SIS
SOFTWARE LOCATION OPERATING SYSTEM INTERFACES TO:

COMPONENT
SIS Data Server SIS Data Server pSOS operating system  Logic Solver (external)
 Net Repeater (external)
 CIS
Ovation Controller Ovation Controller VxWorks operating system  Controller embedded
Interface to SIS software (external)
Data Server (CIS)  SIS Data Server embedded
software
 Ovation SIS Engineering
tools
 Ovation SIS MMI Tools
 SIS Write Server
Ovation SIS Write Engineering or Operator MS Windows  CIS
Library Station 2008/Windows 7  Ovation SIS Engineering
tools
 Ovation SIS MMI Tools
Ovation SIS Engineering station MS Windows  CIS
Engineering Tools 2008/Windows 7  SIS Write Server
Ovation SIS MMI Operator Station MS Windows  CIS
Tools 2008/Windows 7  SIS Write Server
488 OW360_R1005
30.12 What are Ovation SIS Logic Solver algorithms?
Safety Instrumented System (SIS) algorithms are self-contained software modules that reside in
Logic Solvers. All Logic Solver output channel algorithms can only be accessed by the Logic
Solver where the physical connection is performed.
Note: The term "Logic Solver" refers to both the 1508 Logic Solver and the CSLS.
The use of SIS algorithms and the SIS system, is described in Ovation Safety Instrumented
System (SIS) User Guide.
The SIS algorithms are listed and briefly described in the following table. Note that the SIS
algorithm reference pages follow the same format as the standard Ovation algorithms.
Note: Some SIS algorithm parameters may show "LX" in the Minimum Point Record column in
the Algorithm Definitions table. LX indicates that the parameter can take any (LA (analog), LD
(digital), or LP (packed)) point record.
Algorithms from the SIS family are not valid in control macros or standard control functions
Algorithm Reference table
ALGORITHM DESCRIPTION FUNCTION
LSAI Analog Input Accesses a single analog measurement value and quality 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 2 to
16 digital inputs. The algorithm supports signal quality 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 Generates a True (1) digital pulse output when the digital input
Trigger makes a positive (False-to-True) or negative (True-to-False)
transition since the last execution of the algorithm. The algorithm
supports signal quality propagation.
LSBFI Boolean Fan In Generates a digital output based on the weighted binary sum,
binary coded decimal (BCD) representation, or logical OR of 1 to 16
digital inputs. The algorithm supports signal quality 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 quality 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 Defines interlock and permissive logic that associates as many as
(uses advanced 16 inputs and 16 outputs. Configure one or more inputs to trip each
editor) output. When an input becomes active, all outputs associated with
that input trip.
OW360_R1005 489
LSCMP Comparator Compares two values and sets a Boolean output based on that
comparison.
LSDI Digital Input Accesses a single digital measurement value and quality from a
two-state field device and makes the processed physical input
available to other algorithms. The algorithm supports signal
inversion, and signal quality propagation..
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 Drives a HART Two-state Output channel connected to a digital
Controller 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.
LSMID Middle Signal Selects between multiple analog signals. The algorithm selects the
Selector mid-valued 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 2 to
16 digital inputs, then performs a NOT on the result. The algorithm
LSNDE Negative Edge Generates a True (1) digital pulse output when the digital input
Trigger makes a negative (True-to-False) transition since the last execution
of the algorithm. The algorithm supports signal quality propagation.
LSNOR Logical NOR Generates a digital output value based on the logical OR of 2 to 16
digital inputs, then performs a NOT on the result. The algorithm
LSNOT Logical NOT Logically inverts a digital input signal and generates a digital output
value. The algorithm supports signal quality 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 quality
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 quality
propagation.
LSOR Logical OR Generates a digital output value based on the logical OR of 2 to 16
digital inputs. The algorithm supports signal quality propagation.
LSPDE Positive Edge Generates a True (1) digital pulse output when the digital input
Trigger makes a positive (False-to-True) transition since the last execution
of the algorithm. The algorithm supports signal quality 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.
490 OW360_R1005
LSRS Reset/Set Flip-Flop Generates a digital output value based on NOR logic of reset and
set inputs.
LSSEQ Sequencer (uses Associates system states with actions to drive outputs based on the
advanced editor) current state.
LSSR Set/Reset Flip-Flop Generates a digital output value based on NAND logic of set and
reset inputs.
LSSTD State Transition Implements a user-defined state machine. The state machine
Diagram (uses describes the possible states, and the transitions between those
advanced editor) 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.
OW360_R1005 491
S E C T I O N 31
31 Planning your Safety Instrumented System (SIS)

with Electronic Marshalling
IN THIS SECTION
What is a Safety Instrumented System with Electronic Marshalling? ............................. 493

Functions of Ovation SIS with Electronic Marshalling ..................................................... 494
SIS with Electronic Marshalling aspects to consider ....................................................... 494
Capacities for Ovation SIS with Electronic Marshalling system ...................................... 496
SIS environmental specifications for Ovation SIS with Electronic Marshalling devices . 496
Supported SIS Local Safety Network .............................................................................. 497
Hardware components of Ovation SIS with Electronic Marshalling ................................ 499
31.1 What is a Safety Instrumented S ystem w ith Electronic

Marshalling?
A Safety Instrumented System (SIS) with Electronic Marshalling is a set of components that
includes sensors, SIS CHARMs Logic Solvers, and final control elements whose purpose is to
respond to plant conditions, which may be hazardous. The Safety Instrumented System with
Electronic Marshalling must generate the correct outputs to prevent the hazard or reduce the
consequences of the hazard.
A Safety Instrumented System (SIS) with Electronic Marshalling is a form of process control
typically used in industrial processes, such as those of Power Generation and Waste Water. The
SIS with Electronic Marshalling 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.
addresses are for example purposes only and should not be used in an actual SIS system.
Contact your Emerson project representative for assistance in obtaining the IP addresses for
your system.
OW360_R1005 493
31.2 Functions of Ovation SIS with Electronic Marshalling
31.2 Functions of Ovation SIS w ith Electronic Marshalling
The Safety Instrumented System with Electronic Marshalling 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.
31.3 SIS w ith Electronic Marshalling aspects to consider
A Safety Instrumented System (SIS) with Electronic Marshalling is a form of process control
usually implemented in industrial processes, such as those in a Power generation or Waste water
plant. The SIS with Electronic Marshalling performs specified functions to achieve or maintain a
safe state of the process when unacceptable or dangerous process conditions are detected.
Consider the following aspects when planning an SIS with Electronic Marshalling project:
 The safe state is a state of the process operation where the hazardous event cannot occur.
You should be able to achieve a safe state within one-half of the process safety time.
 Even though Safety Instrumented Systems are composed of elements that are similar to
elements in a process control system (such as sensors, logic solvers, actuators, and support
systems), you should keep the safety system separate and independent from your regular
control systems.
 The specified functions or Safety Instrumented Functions (SIF (see page 453)) should be
implemented as part of an overall risk reduction strategy since they are intended to reduce
the likelihood of a catastrophic release and create a safe state.
 The correct operation of an SIS requires a series of equipment to function properly, such as
the following:
 Sensors capable of detecting abnormal operating conditions, such as high flow, low level,
or incorrect valve positioning.
 Logic Solvers that receive the sensor input signal(s), make appropriate decisions based
on the nature of the signal(s), and change its outputs according to user-defined logic.
 Final elements that take action on the process (for example, closing a valve) to bring it to
a safe state due to changes in Logic Solver output.
 Support systems, such as power and communications, are generally required for SIS
operation. The support systems should be designed to provide the required integrity and
reliability.
494 OW360_R1005
31.3 SIS with Electronic Marshalling aspects to consider
 Functional and safety integrity requirements for an SIS are determined from hazard and
operability studies (HAZOP), layers of protection analysis (LOPA), risk graphs, and so on. All
techniques are mentioned in IEC 61511 and IEC 61508.
 You need to verify that during SIS design, construction, and operation, these functional
and safety requirements are met.
 You can verify functional requirements by design reviews, such as failure modes, effects,
and diagnostic analysis (FMEDA). You can also use various types of testing, such as
factory acceptance testing, site acceptance testing, and regular functional testing.
 You can verify safety integrity requirements by reliability analysis. For SIS with Electronic
Marshalling that operates on demand, it is often the probability of failure on demand
(PFD) that is calculated. In the design phase, the PFD may be calculated using generic
reliability data. Later on, the initial PFD estimates may be updated with field experience
from the specific plant in question.
 Since it is not possible to address all factors that affect SIS with Electronic Marshalling
reliability through reliability calculations, you should also have adequate measures in
place (for example, processes, procedures, and individual training and certification) to
avoid, reveal, and correct SIS related failures.
31.3.1 Safety Instrumented Functions (SIFs)
Safety Instrumented Systems are applied to a process to substantially reduce the risk from costly
or dangerous failures in industrial processes. The magnitude of risk reduction needed is
determined from an analysis of the severity of hazardous process events and their probability of
occurrence.
Safety Instrumented Systems are typically comprised of multiple Safety Instrumented Functions
(SIFs). Each SIF can be considered a control loop, defining:
 Measurements (sensors) to use.
 Actions to take (control elements to drive).
 When to apply the actions (logic linking the measurements to the actions).
 How fast to measure and react.
Every SIF has a Safety Integrity Level (SIL (see page 453)) assigned to it.
31.3.2 Safety Integrity Levels (SILs)
Every SIF has a Safety Integrity Level (SIL) assigned to it. SIL is a measure of the risk reduction
provided by a SIF based on four discrete levels, each representing an order of magnitude of risk
reduction. The factors considered in determining a SIL include:
 Device integrity.
 Diagnostics.
 Failures.
 Testing.
 Operation.
 Maintenance.
OW360_R1005 495
31.4 Capacities for Ovation SIS with Electronic Marshalling system
31.4 Capacities for Ovation SIS w ith Electronic Marshalling system
The following table describes the capacities for SIS with Electronic Marshalling system.
Capacities for Ovation SIS with Electronic Marshalling system
CHARMs Smart Logic Solver per SIS Controller 16

Function Blocks per SIS Module 5001
SIS Module in a CSLS 16
Secure Parameter in a CSLS 96
Non-secure Parameter References in a CSLS 96
LS CHARMs per CSLS (arranged as 8 carriers of 12 96
CHARMS per carrier)
Note: Only 48 of the 96 CHARM slots can
be configured as output LS CHARMs. This
can be any combination of simplex and
redundant as long as slot count of output
LS CHARMs does not exceed 48. This
limit is not enforced during configuration; it
is only enforced during download. The
remaining 48 slots can be configured as
input LS CHARMs.
CHARM baseplate per CSLS 8

Temporary Variables Defined Using VAR… END_VAR per 32
Expression
Function Blocks in the Top Level of an SIS Module 1271
Function Blocks per Composite Block 1271
1The actual value may be less depending on a number of factors including the complexity of SIS module
configuration and the number and type of SIS function blocks used.
496 OW360_R1005
31.5 SIS environmental specifications for Ovation SIS with Electronic Marshalling devices
31.5 SIS environmental specifications for Ovation SIS w ith Electronic

Marshalling devices
The following table provides the environmental specification for normal operation of Ovation SIS
with Electronic Marshalling devices.
SIS environmental specifications
SPECIFICATION DESCRIPTION
Storage temperature -40°C to 85°C (-40°F to 185°F)

Operating temperature -40°C to 70°C (-40°F to 158°F)
Relative humidity 5 to 95%, non-condensing
Airborne contaminants Severity level G3
Protection rating IP 20, NEMA 12
Shock 10 g half-sine wave for 11 ms
Vibration 1 mm peak-to-peak from 2 to 13.2 Hz; 0.7 g from 13.2 to 150 Hz
31.6 Supported SIS Local Safety Netw ork
SIS Local Safety Network (yellow) Ethernet based is shown in the following figure:
Figure 129: SIS Local Safety Network (yellow) Ethernet based
OW360_R1005 497
31.6 Supported SIS Local Safety Network
The Primary Network must be treated as a dedicated standalone Local Area Network (LAN) and
must not be connected to a Backup Network.
When CSLS to SRM100 distance is greater than 100 meters or connection can be subjected to
electromagnetic interference, the fiber optic connections can be used using LSN20 switches.
SRM100 switches can be connected through fiber optics using the SFP adapters or the
expansion modules.
SIS Local Safety Network (yellow) Ethernet and fiber optics based is shown in the following figure:
Figure 130: SIS Local Safety Network (yellow) Ethernet and fiber optics based
Note: An Ovation SIS CHARMs system supports up to 16 redundant CSLSs.
498 OW360_R1005
31.7 Hardware components of Ovation SIS with Electronic Marshalling
31.7 Hardw are components of Ovation SIS w ith Electronic

Marshalling
The SIS with Electronic Marshalling system contains various hardware components that are
described in the following table.
Note: For information about installing switches in your SIS System, refer to the manufacturer's
installation instructions.
Hardware components
HARDWARE
DESCRIPTION
COMPONENT
CSLS Carrier
KL4103X1-BA1
(CHARMs Smart Logic Solver Carrier).
KL1501X1-BA1 CSLS Power Module.
KL2001X1-PW1 CSLS.
KL1603X1-BA1 Safety Network Port Single Copper.
KL4201X1-BA1 CHARM Baseplate.
KL4210X1-BA1 I.S. CHARM Baseplate.
KL4502X1-KA1 CHARM Baseplate ID Label Assembly.
KL4502X1-DA1 CHARM Address Terminal (Screw).
KL4510X1-EA1 I.S. CHARM Address Terminal.
KL4510X1-CA1 I.S. CHARM Separation Wall Assembly.
KL4502X1-JA1 Channel Identifier Labels for CSLS Baseplates.
KL4510X1-BA1 Channel Identifier Labels for CSLS I.S Baseplates.
KL4501X1-BA1 CHARM Baseplate Addressing Plug 1.
KL4501X1-BB1 CHARM Baseplate Addressing Plug 2.
KL4501X1-BC1 CHARM Baseplate Addressing Plug 3.
KL4501X1-BD1 CHARM Baseplate Addressing Plug 4.
KL4501X1-BE1 CHARM Baseplate Addressing Plug 5.
KL4501X1-BF1 CHARM Baseplate Addressing Plug 6.
KL4501X1-BG1 CHARM Baseplate Addressing Plug 7.
KL4501X1-BH1 CHARM Baseplate Addressing Plug 8.
KL4503X1-BA1 Charm Baseplate Extender with Cable connectors, Bottom.
OW360_R1005 499
HARDWARE
DESCRIPTION
COMPONENT
KL4503X1-CA1 Charm Baseplate Extender with Cable connectors, Top.
KL4502X1-EA1 Charm Baseplate Terminator, Bottom.
KL4502X1-FA1 Charm Baseplate Terminator, Top.
KL4503X1-DA1 CSLS Baseplate Cables - 0.5 m cable.
KL4503X1-EA1 CSLS Baseplate Cables - 1 m cable.
KL4503X1-FA1 CSLS Baseplate Cables - 2 m cable.
KL4502X1-BA1 Standard CHARM Terminal Block.
KL4502X1-LA1 Fused injected Power Terminal Block.
KL4502X1-NA1 Thermocouple/mV Terminal Block.
KL4505X1-FA1 LS DVC Terminal Block.
KL4505X1-BA1 LS Redundant Terminal Block.
KL4505X1-GA1 LS Redundant DTA Fused Injected Power Relay Terminal Block.
KL4505X1-EA1 LS Redundant DTA Relay Terminal Block.
KL4505X1-DA1 LS Redundant ETA Relay Terminal Block.
KL4505X1-CA1 LS Redundant DVC Terminal Block.
KL4510X1-DA1 I.S. CHARM Terminal Block.
KL4510X1-EA1 I.S. CHARM Address Terminal.
KL3001X1-LS1 LS DI NAMUR CHARM.
KL3003X1-LS1 LS DI 24 VDC low-side sense (dry contact) CHARM.
KL3005X1-LS1 LS DI 24 VDC Isolated CHARM.
KL3007X1-LS1 LS 24 VDC Power CHARM.
KL3302X1-BA1 LS DO 24 VDC DTA CHARM.
KL3302X1-BB1 LS DO 24 VDC DTA Redundant CHARM.
KL3302X1-BC1 LS DO 24 VDC ETA CHARM.
KL3302X1-BD1 LS DO 24 VDC ETA Redundant CHARM.
KL3322X1-BA1 LS DVC HART DTA CHARM.
KL3322X1-BB1 LS DVC HART DTA Redundant CHARM.
KL3021X1-LS1 LS AI 4-20 mA HART CHARM.
500 OW360_R1005
HARDWARE
DESCRIPTION
COMPONENT
KL3032X1-LS1 LS Thermocouple/mV CHARM.
KL3031X1-LS1 LS RTD CHARM.
KL3023X1-LS1 LS AI 0-10 VDC Isolated CHARM.
KL3011X1-LS1 LS DI 120 VAC Isolated CHARM.
KL3012X1-LS1 LS DI 230 VAC Isolated CHARM.
KL3103X1-LS1 LS IS DI NAMUR CHARM.
KL3101X1-LS1 LS IS AI 4-20 mA HART CHARM.
KL4502X1-QA1 CHARM Protection Cover.
KL4510X1-JA1 I.S. CHARM Protection Cover.
KJ4010X1-BS1 DIN Rail Stop.
OW360_R1005 501
The following table describes the compatibility of different types of CHARMs with the terminal
blocks:
Compatibility matrix
LS REDUNDANT DTA FUSED INJECTED POWER RELAY TERMINAL
LS REDUNDANT DTA RELAY TERMINAL BLOCK
LS REDUNDANT ETA RELAY TERMINAL BLOCK

POWER TERMINAL BLOCK
LS REDUNDANT DVC TERMINAL BLOCK

STANDARD CHARM TERMINAL BLOCK
THERMOCOUPLE/MV TERMINAL BLOCK
LS REDUNDANT TERMINAL BLOCK
I.S. CHARM TERMINAL BLOCK

LS DVC TERMINAL BLOCK
INJECTED
BLOCK
FUSED
LS AI 0-10 VDC

Isolated CHARM
LS AI 4-20 mA HART
CHARM 
LS DI 24 VDC
Isolated CHARM  
LS DI 120 VAC
Isolated CHARM  
LS DI 230 VAC
 
Isolated CHARM
LS DI 24 VDC low-
side sense (dry 
contact) CHARM
LS DI NAMUR

CHARM
LS RTD CHARM 
502 OW360_R1005
OW360_R1005
CHARM
CHARM
CHARM
CHARM
CHARM
input CHARM
LS IS DI NAMUR
LS 24 VDC Power
Redundant CHARM
Redundant CHARM
Redundant CHARM
LS DVC HART DTA

LS DVC HART DTA
LS DO 24 VDC ETA
LS DO 24 VDC ETA
LS DO 24 VDC DTA
LS DO 24 VDC DTA
LS Thermocouple/mV



FUSED INJECTED POWER TERMINAL BLOCK





BLOCK




503
504
HART CHARM
LS IS AI 4-20 mA
FUSED INJECTED POWER TERMINAL BLOCK


BLOCK


OW360_R1005
S E C T I O N 32
32 Planning your Virtual Safety Instrumented System
IN THIS SECTION
What is Virtual Safety Instrumented System? ................................................................. 505

Functions of Virtual SIS ................................................................................................... 506
Virtual SIS terminology .................................................................................................... 506
Rules for working with Virtual SIS ................................................................................... 507
Hardware requirements for Virtual SIS ........................................................................... 507
Software requirements for Virtual SIS ............................................................................. 508
Ovation requirements for Virtual SIS............................................................................... 508
Reporting issues.............................................................................................................. 508
32.1 What is Virtual Safety Instrumented System?
Ovation Virtual Safety Instrumented System (Virtual SIS) enables the simulation of hardware
components of an Ovation SIS system on Microsoft Windows machines. Virtual SIS can be used
to prepare and test safety logic without the actual hardware.
Hardware-based Safety Instrumented System (SIS) is a set of components that includes sensors,
logic solvers, and final control elements. The purpose of these components is to respond to plant
conditions, which may be hazardous. SIS must generate the correct output to prevent the hazard
or to reduce the consequences of the hazard. Refer to the Ovation Safety Instrumented System
(SIS) User Guide for details.
Ovation Virtual SIS enables the virtualization of SIS Data Servers (SDS), Logic Solvers (LS), and
SIS Net Repeaters (SNR). Virtual SIS I/O simulation is handled by a special facility on the Ovation
Controller.
You can configure the Virtual SIS network with a hardware-based Ovation SIS Controller or a
Virtual Controller.
The Virtual SIS application replicates the actual behavior of the hardware SIS in the closest
possible manner. It reduces engineering costs and allows you to understand the system without
compromising an active, real-time hardware-based SIS operation.
addresses are for example purposes only and should not be used in an actual Virtual SIS
system. Contact your Emerson project representative for assistance in obtaining the IP
addresses for your system.
OW360_R1005 505
32.2 Functions of Virtual SIS
32.2 Functions of Virtual SIS
The Virtual SIS application performs the following functions:

 Simulates the hardware components, such as SIS Data Servers, Logic Solvers, and SISNet
Repeaters.
 Prepares and tests the SIS logic before using it in the production environment.
 Trains the Ovation Virtual SIS operators.
 Reduces engineering costs.
32.3 Virtual SIS terminology
The following table describes terms that are generally used with the Virtual SIS application.
Terms used with Virtual SIS
TERM DESCRIPTION
Virtual SIS Data Server Corresponds to the SIS Data Server hardware.
Virtual SIS Logic Solver Corresponds to the Logic Solver hardware.
Virtual SIS Logic Solver I/O Enables the simulation of the Virtual Logic Solver inputs and safety logic
simulator (or SIS I/O Simulator) that is driven by those inputs.
Virtual Peer2Peer Deals with communication between Virtual Logic Solvers running under
the same Virtual SDS and communication between Virtual Logic Solvers
running under different Virtual SDSs. This functionality corresponds to
Peer2Peer communication over hardware backplane and
communication provided by SIS Net Repeaters.
Configuration Tool Reads the configuration of Virtual SIS from the Ovation Database (DB)
Server and applies it on configured Virtual SDSs.
506 OW360_R1005
32.4 Rules for working with Virtual SIS
32.4 Rules for w orking with Virtual SIS
Be advised of the following rules when working with Virtual SIS:

 You cannot use Virtual SIS for safety applications or controlling real process.
 You cannot mix hardware and Virtual SDSs in the same SIS network.
 Virtual SIS only supports one Virtual SDS per physical machine.
 Virtual SIS does not support redundant configuration of Virtual SDSs.
 Virtual SIS does not support network redundancy.
 Logic execution time and I/O scan time are 10 times slower on the Virtual SLS than on the
hardware SLS.
 Restarting a Virtual SDS machine causes all Virtual Logic Solvers to the decommission state;
all Logic Solvers have to be loaded again.
 If the entire system is running on VMware Server, the SNMP traps cannot be configured for
Virtual SIS. However, if the physical SIS Switch is used for configuring Virtual SIS, the SNMP
traps can be configured for Virtual SIS.
 Redundant Virtual Logic Solvers can be configured; however, only one Logic Solver works
from the pair at a time. Therefore, Switchover (L->R) for the Logic Solver does not work.
 Virtual SIS is not possible for some network addresses. For example, you cannot use virtual
SIS when the Ovation network IP is 127.168.1.0/24 and the SIS network IP is 127.4.0.0/16
because there is no possible IP address for a local subnet that would make the Virtual
Controller use it for both interfaces.
32.5 Hardw are requirements for Virtual SIS
The following table describes the hardware requirements for the Virtual SIS application.
Hardware requirements for Virtual SIS
HARDWARE COMPONENT REQUIREMENT
Virtual SIS host computer Each Virtual SDS machine must run on a separate Windows-based
(Virtual SDS machine) machine. Refer to Software requirements for Virtual SIS (see page
508) for a list of supported operating systems.
Virtual Controller A Virtual Controller must run on a Virtual Controller host.
SIS Interface Controller It is possible to run Ovation Virtual SIS on an actual (hardware)
Ovation Controller.
Note: Both Virtual Controller and hardware-based Ovation Controller running VxWorks 6.8 are
supported.
The hardware-based Ovation SIS uses a separate LAN for the Ovation network and the SIS
network. However, in case of a Virtual System, single physical network and two IP subnets are
used to have the Ovation network and the SIS network. The purpose of using such a
configuration is to easily convert the System (or database from export) configured for hardware-
based SIS into Virtual System with Virtual SIS or vice versa.
Note: SIS Switches and Routers are not used in the Virtual SIS network with Virtual Controllers.
OW360_R1005 507
32.6 Software requirements for Virtual SIS
32.6 Softw are requirements for Virtual SIS
Virtual SIS can be installed on one of the following operating systems:

 Windows 7 (32-bit and 64-bit versions)
 Windows Server 2008 R2
Virtual SIS machine must be an Ovation domain member.
32.7 Ovation requirements for Virtual SIS
Virtual SIS is only supported in Ovation 3.5 and later releases.
32.8 Reporting issues
Virtual SIS implements a special functionality to report issues. This functionality allows Emerson
to resolve Virtual SIS crash occurrences.
Use the following instructions when an operational Virtual SDS has stopped working or the
VirtualSDSService.exe service is not running:
 Check whether the Crash dump files at C:\Program Files (x86)\VSDS\CrashDumps is
stored with a recent date. If yes, attach these files with the System Deviation Report, along
with the System details and problem description.
508 OW360_R1005
S E C T I O N 33
33 Planning your Virtual Safety Instrumented System

(SIS) with Electronic Marshalling
IN THIS SECTION
What is Virtual Safety Instrumented System with Electronic Marshalling? ..................... 509
Functions of Virtual SIS CHARMs ................................................................................... 510
Terminology of Virtual SIS CHARMs .............................................................................. 510
Rules for working with Virtual SIS CHARMs ................................................................... 510
Hardware requirements for Virtual SIS CHARMs ........................................................... 511
Software requirements for Virtual SIS CHARMs ............................................................. 511
Licensing requirements for Virtual SIS CHARMs ............................................................ 512
33.1 What is Virtual Safety Instrumented System w ith Electronic

Marshalling?
Ovation Virtual Safety Instrumented System with Electronic Marshalling (Virtual SIS CHARMs)
enables the simulation of hardware components of an SIS CHARMs system. Virtual SIS CHARMs
can be used to prepare and test safety logic without the actual hardware. It is used in a Safety
Instrumented System to place and/or maintain the equipment under control in an appropriate
state.
Hardware-based Safety Instrumented System with Electronic Marshalling is a set of components

that includes sensors, CHARM Smart Logic Solvers (CSLSs), CHARMs I/Os, and final control
elements.The purpose of these components is to respond to plant conditions, which may be
hazardous. Safety Instrumented System with Electronic Marshalling must generate the correct
output to prevent the hazard or reduce the consequences of the hazard. For more information,
refer to the Safety Instrumented System (SIS) with Electronic Marshalling User Guide.
Virtual SIS CHARMs enables the virtualization of CHARM Smart Logic Solvers (CSLSs) and
CHAMRs I/Os that are connected to it.
The Virtual SIS CHARMs system can be configured with a hardware-based Ovation system or a
Virtual Ovation system. Virtual SIS CHARMs uses the Virtual Controllers.
The Virtual SIS CHARMs application replicates the behavior of the SIS CHARMs hardware in the
closest possible manner. It reduces the engineering cost and allows you to understand the
system without compromising the real hardware.
OW360_R1005 509
33.2 Functions of Virtual SIS CHARMs
33.2 Functions of Virtual SIS CHARMs
The Virtual SIS CHARMs performs the following functions:

 Simulates the hardware components.
 Allows preparing and testing the SIS logic before using it in the production environment.
 Helps training the Ovation SIS operators.
 Reduces the engineering costs.
33.3 Terminology of Virtual SIS CHARMs
The following table describes terms that are generally used with the Virtual SIS CHARMs
application.
Terms used with Virtual SIS
TERM DESCRIPTION
CHARMs Characterization Module.

CSLS CHARM Smart Logic Solver.
DBS Database Server.
I/O Refers to CHARM I/O device.
SIS CHARMs Safety Instrumented System with Electronic Marshalling.
SIS I/O simulator Enables the simulation of the Virtual Logic Solver inputs and safety
logic that is driven by those inputs.
VCH Virtual Controller Host.
VCSLS Virtual CHARM Smart Logic Solver.
VM Virtual Machine.
Virtual SIS CHARMs Virtual CHARM Smart Logic Solver Safety Instrumented System with
Electronic Marshalling.
33.4 Rules for w orking with Virtual SIS CHARMs
Be advised of the following rules when working with Virtual SIS CHARMs:
 You cannot use Virtual SIS CHARMs to control the real processes.
 You cannot use CSLSs and VCSLSs under a single Ovation Controller.
 You should always configure VCSLS as simplex.
 Every VCSLS is a separate Virtual Machine (VM).
 VCSLS executes five times slower than the CSLS.
510 OW360_R1005
33.5 Hardware requirements for Virtual SIS CHARMs
33.5 Hardw are requirements for Virtual SIS CHARMs
The following table describes the hardware requirements for the Virtual SIS CHARMs application
apart from the standard Ovation requirements.
Hardware Component
HARDWARE COMPONENT REQUIREMENTS
VM server A hardware machine capable of running VM server software and

multiple VCSLSs.
Each Virtual CHARM Smart Logic Solver (VCSLS) requires the following resources from the VM
server.
Hardware Component Resource
HARDWARE COMPONENT RESOURCE REQUIREMENTS
CPU CPU with about 1 GHz speed.

RAM 256 MB.
Hard Drive on IDE 1 GB.
Network interfaces Two virtual network interfaces.
Note: Unlike hardware-based Ovation SIS CHARMs system, the VCSLS communicates with the
Virtual Controller over the Ovation network interface. The Virtual Controller Host (VCH) network
interface bridge must be configured with a second IP address in the 10.4.*.* IP format. Also, if
the SIS CHARM I/O Device has configured the redundant SIS network, the VCH network
interface bridge must be configured with the third IP address in the 10.6.*.* IP format.
33.6 Softw are requirements for Virtual SIS CHARMs

The following table describes the software requirements for the Virtual SIS CHARM application.
Software requirements
SOFTWARE COMPONENT REQUIREMENTS
VM server VM server software.

VCSLS image The image is located at the DBS machine at the following
location:
Ovation\SIS\Virtual\VCSLS_X86_release.iso
Note: The VCSLS image comes with the Ovation software installation disk. However, the VM
server software is not a part of the Ovation software installation disk.
OW360_R1005 511
33.7 Licensing requirements for Virtual SIS CHARMs
You must have the following licenses to use the Virtual SIS CHARM:
 Ovation.
 SIS CHARMs.
 Virtual Controller.
33.7.1 Overview of planning the Virtual SIS CHARMs system
You can configure the Virtual SIS CHARMs system with a hardware-based Ovation system (see
page 512) or a Virtual Ovation system (see page 513).
33.7.2 Virtual SIS CHARMs with hardware-based Ovation
The Virtual SIS CHARMs can be connected to an existing hardware-based Ovation system by
adding a VCH, VM server to the Ovation network, and VCSLSs on the VM network as shown in
the following figure.
Figure 131: Virtual SIS CHARMs with hardware-based Ovation
512 OW360_R1005
33.7.3 Virtual SIS CHARMs with Virtual Ovation
The Virtual SIS CHARMs can be added to the Virtual Ovation system by adding the VCSLSs as
shown in the following figure.
Figure 132: Virtual SIS CHARMs with Virtual Ovation
OW360_R1005 513
S E C T I O N 34
34 Planning your System Backup and Restore
IN THIS SECTION
Why perform Ovation system backups? ......................................................................... 515

Backing up and restoring the system .............................................................................. 516
What are the programs involved in backup and restore operations? ............................. 516
What are the Ovation Backup/Restore Program functions? ........................................... 517
Restoring Active Directory Domain Services (AD DS) (Domain Controllers) ................. 517
34.1 Why perform Ovation s ystem backups?
The system files (Oracle and Ovation databases as well as other system information) should be
backed up periodically, so that in case of data loss, sufficient data is available to restore the
Ovation system.
The best practice to maintain sufficient data to restore the Ovation system, in the event of a
system disruption, is to periodically back up the following files:
 Oracle database.
 Ovation database.
 System files.
 Any other pertinent system information.
Instructions for using the OvPtBackup program included with your Ovation system are provided in
this manual. Refer to the Ovation Developer Studio User Guide for information about using the
GUI version of the OvPtBackup program. Refer to the Ovation Database User Guide for additional
information about backing up and restoring the database.
Optional Backup and Recovery software is also available in addition to standard Ovation
OvPtBackup backup and restore software. To learn more about the Backup and Recovery utility,
refer to the System Backup & Recovery User Guide.
Note: OvPtBackup backs up and restores the Ovation Database Server. This backup is also
sufficient for systems with Foundation Fieldbus; however, this utility does not back up data
stored on the Ovation Fieldbus Engineering Server.
Once the backup image is restored, Foundation Fieldbus data must be re-exported from the
Ovation database and imported into the Ovation Fieldbus Engineering Server.
OW360_R1005 515
34.2 Backing up and restoring the system
34.2 Backing up and restoring the s ystem
The best practice to maintain sufficient data to restore the Ovation system, in the event of a
system disruption, is to periodically back up the the following files:
 Oracle database.
 Ovation database.
 System files.
 Any other pertinent system information.
Instructions for using the OvPtBackup package included with your Ovation system are provided in
this manual.
Optional Backup and Recovery software is also available in addition to standard Ovation
OvPtBackup backup and restore software. To learn more about the Backup and Recovery utility,
refer to the System Backup and Recovery User Guide.
34.3 What are the programs involved in backup and restore

operations?
The Backup/Restore program (OvPtBackup) can be executed from a command line. You can also
use the GUI version of the Backup/Restore program by accessing the Ovation Backup/Restore
window from the Ovation Developer Studio (refer to the Ovation Developer Studio User Guide for
more information).
When you launch the OvPtBackup program, other programs work behind the scenes to extract
data so that it can be backed up:
 Ovation’s Export program (OvPtExport) extracts Ovation data from Oracle and places it into
a single text file on the hard drive.
 Oracle’s Export program (exp) extracts the entire Oracle database (data and structure) and
places it into a single binary file on the hard drive.
The execution of these programs during a backup is transparent with the GUI version of
OvPtBackup because the Ovation Backup/Restore program manages and directs the backup
process through a user-friendly interface. However, when you perform a restore process, user
interaction with Microsoft Windows Backup is required.
When the Backup/Restore program (OvPtBackup) performs a backup, the following data is
included in the backup:
 Ovation database exported from Oracle in binary form.
 Power Tools database exported from Ovation in text format.
 Ovation engineering data including control sheets, graphics, libraries, and so forth exported
from a designated system.
 Server System network files:
 \etc\hosts
 \etc\bootptab
516 OW360_R1005
34.4 Restoring Active Directory Domain Services (AD DS) (Domain Controllers)
34.4 Restoring Active Directory Domain Services (AD DS) (Domain

Controllers)
Recovering the Active Directory Domain Services (AD DS) is not a routine day-to-day operations
task; it is performed only when it is made necessary by a failure or other conditions from which
Domain Controllers can be recovered only by restoring it to a previous state.
Restoring from backup is not always the best or only option to recover AD DS to a previous state,
and it should not be used as the primary method of recovering from an error or failure condition,
but as a last resort.
Sometimes it is faster to reinstall AD DS and then restore the database through replication from
other Domain Controllers than to recover it from backup.
The primary requirement for recovering Active Directory from the backup is that the backup must
not be older than the tombstone lifetime, which is the number of days the Active Directory
preserves knowledge of deleted objects.
Always check the tombstone lifetime of the Active Directory environment before using a backup to
restore AD DS.
CAUTION! The default tombstone lifetime is 180 days.
AD DS can be recovered from the backup in the following ways:

 Non-authoritative restore – Default method of recovering the AD DS to a previous state. This
method returns the Domain Controller to its state at the time of the backup and then allows
normal replication from other Domain Controllers to overwrite any changes that occurred after
the backup was taken.
Note: Be aware that non-authoritative restore does not restore deleted objects from the backup.
The only way to restore deleted objects from the backup is to use the Authoritative restore
process.
 Authoritative restore – Advanced method of recovering the AD DS from accidental large-scale

deletion. In this method, the deleted objects are recovered from backup and are
authoritatively pushed to other Domain Controllers through replication.
Note: Recovering the Domain Controller through Authoritative restore is an advanced procedure
and is not covered in this guide.
AD DS can also be recovered through re-installation without using a backup. This method relies
on replication to restore a Domain Controller to a working state, and is valid only if another
healthy Domain Controller exists. In addition, this is the only method by which a Domain
Controller that is not part of the backup set can be restored.
CAUTION! Do not restore a failed Domain Controller by using unapproved imaging software.
Doing so may result in a condition known as USN rollbacks. When USN rollback occurs, a
restored Domain Controller will not be able to receive replication updates from other Domain
Controllers and may become out-of-sync permanently.
OW360_R1005 517
34.4 Restoring Active Directory Domain Services (AD DS) (Domain Controllers)
34.4.1 Criteria for using the restore type
Typically, restoring a Domain Controller after a failure involves restoring the Domain Controller
from the previously taken backup; however, this solution is not always feasible or possible. Also,
the recovery solutions depend on many factors, for example: hardware failures, availability of
other Domain Controller(s) in the environment, and the availability of backups.
The following flow chart illustrates how to determine the restore type that must be used to recover
a failed Domain Controller.
518 OW360_R1005
S E C T I O N 35
35 Ovation hardware specification sheets
IN THIS SECTION
Hardware specification sheets overview ......................................................................... 519

Cabinets, vented, NEMA12 with standard mounting plate ............................................. 519
Cabinets, vented, NEMA12 with Marshalling mounting plate ......................................... 531
Cabinets, sealed, NEMA12 with standard mounting plate .............................................. 535
Cabinets, sealed, NEMA12 with Marshalling mounting plate ......................................... 545
Cabinets, sealed, NEMA4 with standard mounting plate ................................................ 550
Cabinets, sealed, NEMA4 with Marshalling mounting plate ........................................... 558
Cabinets, vented, NEMA12 with no mounting plate ........................................................ 563
Ovation Workstation Cabinet vented (1X00518) ............................................................. 567
Ovation Server Cabinet vented (1X00545) ..................................................................... 567
Ovation workstation specification sheets ........................................................................ 568
Monitor specification sheets ............................................................................................ 579
Keyboard specification sheet .......................................................................................... 584
Printer specification sheets ............................................................................................. 585
Storage device specification sheets ................................................................................ 588
Miscellaneous specification sheets ................................................................................. 588
Ovation I/O module environmental specifications ........................................................... 590
Cable specification sheets .............................................................................................. 590
35.1 Hardw are specification sheets overview
This section provides specification sheets for Ovation hardware items.
OW360_R1005 519
35.2 Cabinets, vented, NEMA12 with standard mounting plate
35.2 Cabinets, vented, NEMA12 w ith standard mounting plate
The following table provides specifications for NEMA12 vented cabinets with standard mounting
plates:
NEMA12 vented cabinets with standard mounting plates
EMERSON PART NUMBER DIMENSIONS VENDOR
5X00068H01/H02 (see 2000 mm x 600 mm x 400 mm Hoffman (Front Access only)

page 521) (78 in. x 24 in. x 16 in.)
1X00903H01 (see page 521) 2000 mm x 600 mm x 400 mm Rittal
(78 in. x 24 in. x 16 in.)
5X00018H01 (see page 523) 2000 mm x 600 mm x 500 mm Hoffman
(78 in. x 24 in. x 20 in.)
5X00127H01/H02 (see 2000 mm x 600 mm x 600 mm Hoffman
page 524) (78 in. x 24 in. x 24 in)
(78 in. x 24 in. x 24 in.)
page 525) (78 in. x 32 in. x 24 in.)
(78 in. x 32 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
(78 in. x 24 in. x 24 in.)
(EMC Cabinet)
520 OW360_R1005
35.2.1 NEMA12, vented, 2000 mm x 600 mm x 400 mm, (front access only) Hoffman
(5X00068H01/H02)
 Weight (Empty cabinet) = 127 kg (280 lb).
 Dimensions (HxWxD) = 2000 mm x 600 mm x 400 mm (78 in. x 24 in. x 16 in.).
 5X00068H01 uses a standard double bit handle/lock.
 5X00068H02 uses a keylocking pushbutton swing handle/lock.
 Operating Temperature:
 0 degrees C to 60 degrees C (32 degrees F to 140 degrees F for vented I/O cabinets).
 See note for Controller cabinets.
 Storage Temperature:
 -25 degrees C to 70 degrees C (-13 degrees F to 158 degrees F) for Controller cabinets
that must be vented.
 -25 degrees C to 85 degrees C (-13 degrees F to 185 degrees F) for vented I/O.
 Operating Humidity = 0% to 95% (non-condensing).
 Operating Altitude = 2 km max (6561 ft max).
 Ingress Protection Rating (EN60529/10.91) = 53.
Note: The maximum ambient temperature for an Ovation OCR400/OCR1100 (5X00481G01,

G03, and G04) Controller cabinet is 50 degrees C. The Controller cabinet must be ventilated
with fans mounted in both the front and rear doors. Refer to Ovation ventilated cabinet
5X00127/1X00900.
The use of third-party devices, such fiber-optic media converters and Profibus gateways,
necessitate lower maximum operating temperatures. Based on a 5 degree C internal rise, the
maximum ambient temperature for an OCR400/1100 (5X00481G01, G03, and G04) Controller
cabinet that contains fiber-optic media converters is 35 degrees C. The maximum ambient
temperature for an OCR400/1100 (5X00481G01, G03, and G04) Controller cabinet that
contains a Profibus gateway is 45 degrees C.
The maximum ambient temperature for an Ovation OCR1100 (5X00481G02) Controller cabinet
is 40 degrees C. The Controller cabinet must be ventilated with fans mounted in both the front
and rear doors. Refer to Ovation ventilated cabinet 5X00127/1X00900.
In the event that environmental conditions dictate that an OCR400/OCR1100 (5X00481G01

through G04) Controller needs to be mounted in a sealed cabinet, a properly sized AC unit must
be used to maintain the specified operating temperatures for all of the internal components. The
use of internally mounted circulatory fans is required to eliminate hot spots and provide a
uniform internal temperature.
OW360_R1005 521
35.2.2 NEMA12, vented, 2000 mm x 600 mm x 400 mm, Rittal (1X00903H01)


5X00127/1X00900.

522 OW360_R1005
35.2.3 NEMA 12, vented, 2000 x 600 x 500 mm, Hoffman (5X00018H01)

5X00127/1X00900.

OW360_R1005 523
35.2.4 NEMA12, vented, 2000 mm x 600 mm x 600 mm, Hoffman (5X00127H01/H02)

 Dimensions (HxWxD) = 2000 mm x 600 mm x 600 mm (78 in. x 24 in. x 24 in).
 5X00127H01 uses a standard double bit handle lock.
 0 to 60 degrees C (32 to 140 degrees F for vented I/O cabinets).
 -25 degrees C to 85 degrees C (-13 degrees F to 185 degrees F) for vented I/O cabinets.

5X00127/1X00900.

524 OW360_R1005

 Uses a keylocking pushbutton swing handle/lock.

5X00127/1X00900.

OW360_R1005 525


5X00127/1X00900.

526 OW360_R1005

 Dimensions (HxWxD) = 2000 mm x 800 x 600 mm (78 in. x 32 in. x 24 in.).
 0 degrees C to 60 degrees C (32 to 140 degrees F for vented I/O cabinets).

5X00127/1X00900.

OW360_R1005 527
35.2.8 NEMA12, vented, 2000 mm x 914 mm x 600 mm, Hoffman (1X00454H02)

 Ingress Protection Rating (EN60529/10.91) = 53

5X00127/1X00900.

528 OW360_R1005


5X00127/1X00900.

OW360_R1005 529
35.2.10 NEMA12, EMC cabinet, vented, 2000 mm x 600 mm x 600 mm, Rit tal
(1X00520H01)
 Weight (Empty cabinet) = 155 kg (341lb).
 Relative Humidity = 0% to 90%.
 Ingress Protection Rating (EN60529/10.91) = 53 (4D33947H01); 55 (4D33947H02).
 Pollution Degree/Install Category = 2/II.

5X00127/1X00900.

530 OW360_R1005
35.3 Cabinets, vented, NEMA12 with Marshalling mounting plate
35.3 Cabinets, vented, NEMA12 w ith Marshalling mounting plate
The following table provides specifications for NEMA12 vented cabinets with Marshalling
mounting plates:
NEMA12 vented cabinets with Marshalling mounting plates

page 532) (78 in. x 32 in. x 24 in.)
(78 in. x 32 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
OW360_R1005 531

 5X00021H03 uses a keylocking pushbutton swing handle/lock..

5X00127/1X00900.

532 OW360_R1005


5X00127/1X00900.

OW360_R1005 533


5X00127/1X00900.

534 OW360_R1005


5X00127/1X00900.

OW360_R1005 535
35.4 Cabinets, sealed, NEMA12 with standard mounting plate
35.4 Cabinets, sealed, NEMA12 w ith standard mounting plate
The following table provides specifications for NEMA12 sealed cabinets with standard mounting
plates:
NEMA12 sealed cabinets with standard mounting plates

(78 in. x 24 in. x 20 in.)
5X00046H01/H03 (see 2000 mm x 600 mm x 600 mm
Hoffman
page 538) (78 in. x 24 in. x 24 in.)
(78 in. x 24in. x 24 in.)
page 539) (78 in. x 32 in. x 24 in.)
(78 in. x 32 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
(78 in. x 24 in. x 24 in.)
536 OW360_R1005
35.4.1 NEMA12, sealed, 2000 mm x 600 mm x 500 mm, Hoffman (5X00019H01)

 0 degrees C to 60 degrees C (32 degrees F to 140 degrees F) at 175 W maximum
internal load for sealed I/O cabinets.
 -25 degrees C to 85 degrees C (-13 degrees F to 185 degrees F) for I/O cabinets.
that must have AC.
 Operating Humidity = 0 to 95% (non-condensing).

5X00127/1X00900.

OW360_R1005 537
35.4.2 NEMA12, sealed, 2000 mm x 600 mm x 600 mm, Hoffman (5X00046H01/H03)

that must have AC.

5X00127/1X00900.

538 OW360_R1005
35.4.3 NEMA12, sealed 2000 mm x 600 mm x 600 mm, Rittal (1X00902H01)

that must have AC.

5X00127/1X00900.

OW360_R1005 539

that must have AC.

5X00127/1X00900.

540 OW360_R1005
35.4.5 NEMA12, sealed, 2000 mm x 800 mm x 600 mm, Rittal (1X00905H03)

that must have AC.

5X00127/1X00900.

OW360_R1005 541

that must have AC.

5X00127/1X00900.

542 OW360_R1005

that must have AC.

5X00127/1X00900.

OW360_R1005 543
35.4.8 NEMA12, EMC cabinet, sealed, 2000 mm x 600 mm x 600 mm, Rittal
(1X00520H02)
 Weight (Empty cabinet) = 155 kg (341lb).
that must have AC.
 Relative Humidity = 0% to 90%.
 Ingress Protection Rating (EN60529/10.91) = 53 (4D33947H01); 55 (4D33947H02).
 Pollution Degree/Install Category = 2/II.

5X00127/1X00900.

544 OW360_R1005
35.5 Cabinets, sealed, NEMA12 with Marshalling mounting plate
35.5 Cabinets, sealed, NEMA12 w ith Marshalling mountin g plate
The following table provides specifications for NEMA12 sealed cabinets with Marshalling
mounting plates:
NEMA12 sealed cabinets with Marshalling mounting plates
5X0035H01/H05 (see page 546) 2000 mm x 800 mm x 600 mm Hoffman

(78 in. x 32 in. x 24 in.)
(78 in. x 32 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
OW360_R1005 545

that must have AC.

5X00127/1X00900.

546 OW360_R1005

that must have AC..

5X00127/1X00900.

OW360_R1005 547

that must have AC.

5X00127/1X00900.

548 OW360_R1005

that must have AC.

5X00127/1X00900.

OW360_R1005 549
35.6 Cabinets, sealed, NEMA4 w ith standard mounting plate
The following table provides specifications for NEMA4 sealed cabinets with standard mounting
plates:
NEMA4 sealed cabinets with standard mounting plates

(78 in. x 24 in. x 20 in.)
5X00046H02/H04 (see 2000 mm x 600 mm x 600 mm
Hoffman
page 552) (78 in. x 24 in. x 24 in.)
(78 in. x 24 in. x 24 in.)
page 554) (78 in. x 32 in. x 24 in.)
(78 in. x 32 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
550 OW360_R1005

that must have AC.

5X00127/1X00900.

OW360_R1005 551

that must have AC.

5X00127/1X00900.

552 OW360_R1005

that must have AC.

5X00127/1X00900.

OW360_R1005 553

that must have AC.

5X00127/1X00900.

554 OW360_R1005

that must have AC.

5X00127/1X00900.

OW360_R1005 555

that must have AC.

5X00127/1X00900.

556 OW360_R1005

that must have AC.

5X00127/1X00900.

OW360_R1005 557
35.7 Cabinets, sealed, NEMA4 w ith Marshalling mounting plate
The following table provides specifications for NEMA4 sealed cabinets with Marshalling mounting
plates:
NEMA4 sealed cabinets with Marshalling mounting plates

page 558) (78 in. x 32 in. x 24 in.)
(78 in. x 32 in. x 24 in.)
(78 in. x 36 in. x 24 in.)
(78 in. x 36 in. x 24 in.)

that must have AC.
558 OW360_R1005

5X00127/1X00900.

OW360_R1005 559

that must have AC..

5X00127/1X00900.

560 OW360_R1005

that must have AC.

5X00127/1X00900.

OW360_R1005 561

that must have AC.

5X00127/1X00900.

562 OW360_R1005
35.8 Cabinets, vented, NEMA12 with no mounting plate
35.8 Cabinets, vented, NEMA12 w ith no mounting plate
The following table provides specifications for NEMA12 vented cabinets with no mounting plates:
NEMA12 vented cabinets with no mounting plates

page 564) (78 in. x 24 in. x 24 in.)
(78 in. x 24 in. x 32 in.)
(78 in. x 24 in. x 24 in.)
(78 in. x 24 in. x 32 in.)
OW360_R1005 563

 No mounting plate.
 Weight (Empty cabinet) = 115.6 kg (255 lb).
 5X00020H01 uses a standard, double-bit handle/lock.

5X00127/1X00900.

564 OW360_R1005


5X00127/1X00900.

OW360_R1005 565
35.8.3 NEMA12, vented, 2000 mm x 600 mm x 600 mm, (without mounting plate)
Rittal (1X00901H01)
 Operating Humidity = 0% to 95%.

5X00127/1X00900.


566 OW360_R1005
35.9 Ovation Workstation Cabinet vented (1X00518)
35.9 Ovation Workstation Cabinet vented (1X00518)
This cabinet can hold up to 6 Dell Tower workstations with 150 lb maximum load rating per shelf.
 Operating Temperature = N/A
 Storage Temperature = N/A
 Anti-tip angles made of heavy-gauge steel included with cabinet.
35.10 Ovation Server Cabinet vented (1X00545)
This cabinet can also hold the Ovation Security Center (see page 443) components up to a static
load rating of 680 kg (1500 lb).
 Operating Temperature = N/A
 Storage Temperature = N/A
 Anti-tip angles made of heavy-gauge steel included with cabinet.
OW360_R1005 567
35.11 Ovation workstation specification sheets
35.11 Ovation w orkstation specification sheets

Specifications for Ovation workstations are described in the following sections:
Tower workstations and servers
MODEL EMERSON PART NUMBER DROP TYPE
Dell PowerEdge T320 (Windows 5X00618  Domain Controller

Server 2008 R2 SP1) (see page 569)  Domain Controller/Database
Server
 Terminal Server Host
Dell PowerEdge T110 II (Windows 5X00659  Domain Controller
Server (Mid-Tier)
 Process Historian (Mid-Tier)
Dell OptiPlex 9020 (Windows 7 5X00673  Engineer Client
Professional 64-bit) (see page 571)  Operator Station
 Virtual Controller Host
Dell OptiPlex 3020 (Windows 7 5X00678 Engineer Client or Operator
Professional 64-bit) (see page 571) Station (Mid-Tier)
Dell PowerEdge T320 (Windows 5X00619 Process Historian
Server 2008 R2 SP1) (see page 572)
Dell PowerEdge T630 (Linux Server) 5X00720 EDS
(see page 572)
Dell PowerEdge T630 (Windows 5X00721 EDS
Server) (see page 573)
Rackmount workstations
Dell PowerEdge R730 (Windows 5X00727  Domain Controller

Server
Dell Precision 7910 (Windows 7 5X00729  Engineer Client
Professional 64-bit) (see page 574)  Operator Station
Dell PowerEdge R730 (Windows 5X00728  Ovation Process Historian
Server R2 SP1) (see page 575)
Dell PowerEdge R730 (see page 575) 5X00730  Simulator Virtualization Host
Server
Dell PowerEdge R730 (see page 576) 5X00731  Virtualization Host Server
Dell PowerEdge R320 (Windows 5X00695  Virtualization Management

Server 2008 R2 SP1) (see page 576) Server
Dell PowerEdge R720 (Linux Server) 5X00722  EDS

(see page 577)
Dell PowerEdge R720 (Windows 5X00723  EDS
Server) (see page 577)
568 OW360_R1005
Industrial panel mount workstations
Phoenix Contact Valueline PC 1X00919  Engineer Client

(Windows 7 Professional) (see page  Operator Station
578)
Phoenix Contact PC with display 1X01011  Engineer Client
Windows 7 (VL2 PPC 3000) (see page  Operator Station
578)
35.11.1 Dell PowerEdge T320 (5X00618)

 Factory installed with Windows Server 2008 R2 SP1 Standard Edition.
 Used for Domain Controllers, Domain Controller/Database Server combination drops, and
Terminal Servers.
 Weight = 29.55 kg (65.14 lb)
 Dimensions (HxWxD) = 44.33 cm x 30.45 cm x 55.86 cm (17.45 in. x 11.99 in. x 21.99 in.)
 Operating Temperature = 10ºC to 35ºC (50ºF to 95ºF)
 Storage Temperature = -40ºC to 65ºC (-40ºF to 149ºF)
 Operating Humidity = 10% to 80%
 Storage Humidity = 5% to 95%
 Operating Shock = 31 G
 Storage Shock = 71 G
 Operating Vibration = 0.26 Grms
 Storage Vibration = 1.87 Grms
 Operating Altitude = -15.2 to 3,048 m (-50 to 10,000 ft)
 Storage Altitude = -15.2 to 10,668 m (-50 to 35,000 ft)
 Input Voltage VAC = 100 to 240 VAC
 Input Frequency Hz = 50 to 60 Hz
 Input Current VAC = 6.5 A @ 115 VAC maximum; 3 A @ 230 VAC maximum
 Power Consumption = 195 W
 Heat Dissipation = 665.4 BTU/h
OW360_R1005 569
35.11.2 Dell PowerEdge T110 II (5X00659)

 Used for Domain Controllers, Domain Controller/Database Server combination drops (mid-
tier), and Terminal Servers (mid-tier).
 Weight = 16.1 kg (35.49 lb)
 Input Current VAC = 9 A @ 115 VAC maximum; 4.5 A @ 230 VAC maximum
570 OW360_R1005
35.11.3 Dell OptiPlex 9020 (5X00673)

 Factory installed with Windows 7 Professional 64-bit.
 Used for Engineer Client, Operator Station, and Virtual Controller Host drops.
 Weight = 9.4 kg (20.72 lb)
 Power Consumption = 87.15 W
35.11.4 Dell OptiPlex 3020 (5X00678)

 Factory installed with Windows 7 Professional 64-bit.
 Used for Engineer Client and Operator Station drops (mid-tier).
 Weight = 7.6 kg (16.72 lb)
 Operating Shock = 40 G/2ms
 Storage Shock = 50 G/19ms
OW360_R1005 571
35.11.5 Dell PowerEdge T320 (5X00619)

 Used for Ovation Process Historian (OPH) drops.
 Weight = 29.55 kg (65.14 lb)
 Input Current VAC = 6.5 A @ 115 VAC maximum; 3 A @ 230 VAC maximum
35.11.6 Dell PowerEdge T630 (Linux Server) (5X00720)

 Factory installed with Red Hat Enterprise Linux 7.
 Used for EDS Servers.
 Weight = 51.0 kg (112.43 lb) for 3.5 in hard-drive chassis;
41.8 kg (92.15 lb) for 2.5 in hard-drive chassis
 Operating Altitude = 3048 m (10,000 ft) maximum
 Storage Altitude = 12,000 m (39,370 ft) maximum
 Heat Dissipation = 2891 BTU/h
572 OW360_R1005
35.11.7 Dell PowerEdge T630 (Windows Server) (5X00721)

 Compatible with Windows Server 2008 R2 SP1 Standard Edition.
 Weight = 51.0 kg (112.43 lb) for 3.5 in hard-drive chassis;
41.8 kg (92.15 lb) for 2.5 in hard-drive chassis
 Operating Altitude = 3048 m (10,000 ft) maximum
OW360_R1005 573
35.11.8 Dell PowerEdge R730 (Rack Mount) (5X00727)

 Used for Domain Controllers and Domain Controller/Database Server combination drops.
 Weight = 31.4 kg (69.23 lb)
 Dimensions (HxWxD) = 8.73 cm x 48.24 cm x 75.58 cm (3.44 in. x 18.98 in. x 29.75 in.) with
rack latches and bezel
 Input Frequency Hz = 50/60 Hz
35.11.9 Dell Precision R7910 (Rack Mount) (5X00729)

 Compatible with Windows 7 Professional 64-bit.
 Used for Engineer Client and Operator Station drops.
 Weight = 31.4 kg (69.23 lb)
bezel
 Operating Vibration = 5 to 350 Hz at 0.0002 G^2 /Hz
 Storage Vibration = 10 to 500 Hz at 0.001 to 0.01 G^2 /Hz
574 OW360_R1005

 Used for Ovation Process Historian drops.
 Weight = 31.4 kg (69.23 lb)

 No factory installed operating system.
 Used with Simulator Virtualization Host Server.
 Weight = 31.4 kg (69.23 lb)
OW360_R1005 575

 No factory installed operating system.
 Used with Virtualization Host Server.
 Weight = 31.4 kg (69.23 lb)

 Used with Virtualization Management Host Server.
 Weight = 19.3 kg (42.55 lb)
 Dimensions (HxWxD) = 4.28 cm x 48.24 cm x 66 cm (1.69 in. x 18.98 in. x 26 in.) with rack
latches and bezel.
576 OW360_R1005
35.11.14 Dell PowerEdge R720 (Rack Mount) (Linux Server) (5X00722)

 Factory installed with Red Hat Enterprise Linux 7.
 Weight = 31.4 kg (69.23 lb)
35.11.15 Dell PowerEdge R720 (Rack Mount) (Windows Server) (5X00723)

 Weight = 31.4 kg (69.23 lb)
OW360_R1005 577
35.11.16 Phoenix Contact Valueline PC (Panel Mount) (1X00919)

 Factory installed with Windows 7 Professional:
 15-inch display Windows 7 Professional 32-bit (1X00919H01).
 Weight = 3.4 kg (7.5 lb) with no display attached
 Dimensions (HxWxD) = 20.7 cm x 26.5 cm x 4.9 cm (8.2 in. x 10.4 in. x 1.9 in.) with no
display attached
 Shock = 15 G
 Input Voltage VDC = 24 VDC nominal; 19.2 VDC minimum; 28.8 VDC maximum
 Nominal Voltage = 250 V
 Nominal Current = 12 A
35.11.17 Phoenix Contact PC with display Windows 7 (VL2 PPC 3000)

(1X01011)
 Panel-mount PC, factory installed with Windows 7 Professional:
 15-inch display Windows 7 Professional SP1 64-bit (1X01011H01).
 Weight = 12.6 kg (27.78 lbs)
 Dimensions (HxW). Depth is variable depending on the configuration of the computer:
 H01: 26.32 cm x 39.44 cm (10.36 in. x 15.53 in.)
 H02: 30.32 cm x 45.50 cm (12 in. x 18 in.)
 H03: 34.40 cm x 52.20 cm (13.54 in. x 20.55 in.)
 Operating Temperature = -10ºC to 50ºC (14ºF to 122ºF)
 Storage Temperature = 0ºC to 55ºC (32ºF to 131ºF)
 Storage Humidity = 5% to 95% (non-condensing)
 Shock = 15 G
 Input Voltage VDC = 24 VDC +/-20%
578 OW360_R1005
35.12 Monitor specification sheets
Specifications for monitors are described in the following sections:
Desktop LCD
 Dell U3014 (30" Desktop LCD Monitor) (1X00922) (see page 579).
 Dell U2412M (24" Desktop LCD Monitor) (1X00920) (see page 580).
 Dell P2213H (22" Desktop LCD Monitor) (1X00923) (see page 580).
 Dell P2014H (20" Desktop LCD Monitor) (1X00894) (see page 581).
 Dell P1914S (19" Desktop LCD Monitor) (1X00898) (see page 581).
Large Screen LCD

 NEC P553 (55" Large Screen LCD Monitor) (5X00749) (see page 581).
 NEC P463-AVT (46" Large Screen LCD Monitor) (5X00697) (see page 582).
 NEC P403 (40" Large Screen LCD monitor) (5X00718) (see page 583).
 NEC V323 (32" Large Screen LCD monitor) (5X00716) (see page 583).
35.12.1 Dell U3014 (30" Desktop LCD Monitor) (1X00922)

 Weight = 10.84 kg (23.9 lb) with stand and cables
 Dimensions (HxWxD) = 572.7 mm x 689.7 mm x 201.4 mm (22.55 in. x 27.15 in. x 7.93 in.)
with stand
 Operating Altitude = 5,000 m (16,400 ft) maximum
 Input Frequency Hz = 50/60 Hz 3 Hz
 Input Current = 1.8 A maximum
 Inrush Current = 30 A maximum @ 120V; 60 A maximum @ 240V
 Power Consumption = 84.6 W (On mode); 3.35 W (Sleep mode)
 Heat Dissipation = 204.73 BTU/h (On mode)
OW360_R1005 579
35.12.2 Dell U2412M (24" Desktop LCD Monitor) (1X00920)

 Dimensions (HxWxD) = 513.5 mm x 556 mm x 180.3 mm (20.22 in. x 21.89 in. x 7.10 in.)
extended
 Input Current = 1.2 A
 Power Consumption = 24.72 W (Operational); 0.27 W (Standby)
 Heat Dissipation = 84.54 BTU/h (Operational); 0.92 BTU/h (Standby)
35.12.3 Dell P2213H (22" Desktop LCD Monitor) (1X00923)

with stand
 Input Current = 1.5 A
580 OW360_R1005
35.12.4 Dell P2014H (20" Desktop LCD Monitor) (1X00894)

with stand
 Storage Altitude = 12,191.41 m (40,000 ft) maximum
35.12.5 Dell P1914S (19" Desktop LCD Monitor) (1X00898)

with stand
OW360_R1005 581
35.12.6 NEC P553 (55" Large Screen LCD Monitor) (5X00749)

 Weight = 25.3 kg (55.8 lbs)
 Dimensions (HxWxD):
 72.10 cm x 12.50 cm x 6.93 cm (28.4 in. x 49.2 in. x 2.7 in.) with handle
 72.10 cm x 12.50 cm x 6.45 cm (28.4 in. x 49.2 in. x 2.5 in.) without handle
 Operating Temperature = 0ºC to 40º C (32ºF to 104ºF)
 Operating Altitude = 3,000 m (9,843 ft) (Brightness may decrease with altitude.)
35.12.7 NEC P463-AVT (46" Large Screen LCD Monitor) (5X00697)

 Weight = 21.4 kg (47.2 lb) without stand
without stand
 Operating Altitude = (0 to 3,000 m) (0 to 9,840 ft)
 Power Consumption = 115 W (typical); 2.5 W Energy Saving mode
582 OW360_R1005
35.12.8 NEC P403 (40" Large Screen LCD monitor) (5X00718)

 Weight = 18.0 kg (39.7 lb) without stand
 Dimensions (HxWxD) = 532.2 mm x 920.6 mm x 66.5 mm (21.0 in. x 36.2 in. x 2.6 in.) without
stand
 Operating Altitude = 0 to 3,000 m (0 to 9,840 ft)
 Power Consumption = 110 W (typical); 0.5 W ECO mode (Standby)
35.12.9 NEC V323 (32" Large Screen LCD monitor) (5X00716)

 Weight = 13 kg (28.7 lb) without stand
 Dimensions (HxWxD) = 476.2 mm x 786.8 mm x 93.5 mm (18.7 in. x 31.0 in. x 3.7 in.) without
stand
 Power Consumption = 50 W (typical); 1 W Energy Saving mode
OW360_R1005 583
35.13 Keyboard specification sheet
35.13 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 584).
35.13.1 Ovation Keyboard (4D33935)

 Weight = 2.3 kg (5.3 lb)
 Dimensions (HxWxD) = 42 mm x 508 mm x 229 mm (1.66 in. x 20 in. x 9 in.)
 Operating Humidity = 95%
 Operating Altitude = 2,000 m maximum (6,562 ft maximum)
 Storage Altitude = 12,500 m maximum
584 OW360_R1005
35.14 Printer specification sheets
Specifications for printers used in Ovation systems are described in the following sections:
Color (Video Copy/Report) Printers

 HP Color Officejet 7612 Wide Format e-All-in-one (1X00995) (see page 585).
 HP Color Laserjet Enterprise M750 (5X00677) (see page 586).
 HP Color Laserjet Enterprise CP4025n/CP4025dn (1X00989) (see page 586).
Color (Alarm) Printer

 Okidata Microline 395C (5X00445) (see page 586).
Black and White Printer

 HP B/W Laserjet M712n (5X00639) (see page 587).
35.14.1 HP Color Officejet 7612 Wide Format e-All-in-one (1X00995)

 Weight = 17.6 kg (38.8 lb)
 Dimensions (HxWxD):
 29.7 cm x 61.7 cm x 50.52 cm (11.69 in. x 24.29 in. x 19.89 in.)
 Max: 29.7 cm x 61.7 cm x 79.81 cm (11.69 in. x 24.29 in. x 31.42 in.)
 Acoustical Power Emissions = 6.4 B(A) (Black fast draft printing)
 Input Voltage = 100 to 240 VAC ( 10%)
 Input Frequency Hz = 50/60 (3 Hz)
 Power Consumption:
 27.7 W (printing)
 20.87 W (copying)
 4.57 W (ready)
 1.89 W (sleep)
 0.31 W (manual-off)
 0.31 W (auto-off)
OW360_R1005 585
35.14.2 HP Color Laserjet Enterprise M750 (5X00677)

 Weight = 52.4 kg (115.3 lb) (H01, H02, H04); 83 kg (182.6 lb) (H03, H05)
 Dimensions (HxWxD) = 465 mm x 544 mm x 586 mm (18 in. x 21.4 in. x 23 in.) (H01, H02,
H04); 885 mm x 745 mm x 688 mm (35 in. x 30 in. x 27 in.) (H03, H05)
 Acoustical Power Emissions = 6.7 B(A) (printing); 5.0 B(A) (ready)
 Input Voltage = 110 to 127 VAC (10%) (H01, H02, H03); 220 to 240 VAC (10%) (H04, H05)
 Input Frequency Hz = 50 to 60 Hz (2 Hz) (H01, H02, H03, H04, H05)
 Power Consumption = 677.41 W (printing black and white); 654.92 W (printing color); 59.46
W (standby); 9.09 W (powersave); 0.35 W (Off)
35.14.3 HP Color Laserjet Enterprise CP4025n/CP4025dn (1X00989)

 Weight = 38.5 kg (84.6 lb)
 Dimensions (HxWxD) = 41.91 cm x 54.10 mm x 52.32 cm (16.5 in. x 21.3 in. x 20.6 in.)
 Acoustical Noise = 6.9 B(A) (active); 5.0 B(A) (standby)
 Input Voltage VAC = 110 to 127 VAC (10%) (H01, H03); 220 to 240 VAC (10%) (H04)
 Input Frequency Hz = 50 to 60 Hz (2 Hz) (H01, H03, H04)
 Power Consumption = 740 W (active); 72 W (standby); 19 W (powersave); 0.3 W (off)
 Heat Dissipation = 246 BTU/h (Standby)
35.14.4 Okidata Microline 395C (5X00445)

 Weight = 16.8 kg (37 lb)
 Dimensions (HxWxD) = 180 mm x 569 mm x 417 mm (7.1 in. x 22.4 in. x 16.4 in.)
 Operating Humidity = 20% to 80% RH
 Acoustical Noise = 58 dBA
 Input Voltage VAC = 120 VAC (+10%, -15%) (H01); 220 to 240 VAC (+10%, -15%) (H02)
 Power Consumption = 180 VA
586 OW360_R1005
35.14.5 HP B/W Laserjet M712n (5X00639)

 Weight = 34.7 kg (76.5 lb)
 Dimensions (HxWxD) = 858 mm x 989 mm x 392 mm (33.8 in. x 38.9 in. x 15.4 in.)
(maximum)
 Operating Temperature = 10ºC to 32.5ºC (50ºF to 91ºF)
 Non-operating Humidity = 10% to 90%
 Acoustical Power Emissions = 6.8 B(A)
 Input Voltage VAC = 110 to 127 VAC (10%)
 Input Frequency Hz = 50/60 Hz (2 Hz)
 Power Consumption = 786 W (printing); 22.1 W (ready); 6.1 W (sleep); 0.21 W (off)
 Typical Electricity Consumption (TEC) = 3.289 kWh/Week
OW360_R1005 587
35.15 Storage device specification sheets
35.15 Storage device specification s heets
Specifications for storage devices used in Ovation systems are described in the following section:
 NAS/iSCSI RAID 5 SATA Storage (5X00683) (see page 588).
35.15.1 NAS/iSCSI RAID 5 SATA Storage (5X00683)

 Weight = 9.1 kg (20 lb) without hard disk drives
 Dimensions (HxWxD) = 254 mm x 177.8 mm x 381 mm (10 in. x 7 in. x 15 in.)
 Relative Humidity = 10% to 85%
588 OW360_R1005
35.16 Miscellaneous specification sheets
35.16 Miscellaneous specification sheets
The following sections describe miscellaneous specification sheets:

 Dell Precision M6800 Laptop Workstation (1X00895) (see page 589).
 Spectracom SecureSync GPS Modular Time Synchronization System (1X00932) (see page
589).
35.16.1 Dell Precision M6800 Laptop Workstation (1X00895)

 Factory installed with Windows 7 Professional 64-bit operating system.
 Weight = 3.58 kg (7.89 lb)
 Dimensions (HxWxD) = 3.61 cm x 41.67 cm x 27.06 cm (1.42 in. x 16.40 in. x 10.65 in.) front
 Storage Altitude = 0 to 10,668 m (0 to 35,000 ft)
35.16.2 Spectracom SecureSync GPS Modular Time Synchronization System

(1X00932)
 Weight = 2.95 kg (6.5 lb)
 Dimensions (HxWxD) = 4.4 cm x 42.5 cm x 35.6 cm (1.72 in. x 16.75 in. x 14 in.)
 Operating Temperature = -20ºC to 65ºC (-4ºF to 149ºF)
 Storage Altitude = 0 to 10,668 m (0 to 35,000 ft)
OW360_R1005 589
35.17 Ovation I/O module environmental specifications
35.17 Ovation I/O module environmental specifications
All Ovation I/O modules have the same environmental specifications.

 Electronics modules
 Weight = 0.34 kg (0.75 lb)
 Dimensions (HxWxD) = 155 mm x 127 mm x 54.6 mm (6 in x 5 in x 2.15 in)
 Operating Temperature = 0ºC to 60ºC (32ºF to 140º F)
 Storage Temperature = -40ºC to 85ºC (-40ºF to 185ºF)
 Operating Humidity = 0% to 90%
 Personality modules
 Weight = 0.113 kg (0.25 lb)
 Dimensions (HxWxD) = 87.6 mm x 119.4 mm x 28 mm (3.45 in x 4.7 in x 1.1 in)
 Operating Temperature = 0ºC to 60ºC (32ºF to 140ºF)
 Storage Temperature = -40ºC to 85ºC (-40ºF to 185ºF)
 Operating Humidity = 0% to 90%
 Relay Panels
 Weight = 1 kg (2.3 lb) G2R; 1.6 kg (3.6 lb) Form C; 1.7 kg (3.8 lb) Form X
 Dimensions (HxWxD) = 114 mm x 422 mm x 125 mm (4.5 in x 16.6 in x 4.9 in)
 Operating Temperature
 G2R/KUEP Form X = 0ºC to 60ºC (32ºF to 140ºF)
 KUEP Form C = 0ºC to 45ºC (32ºF to 113ºF)
 Operating Humidity
 G2R = 35% to 85%
 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: For more information on Ovation I/O modules, see Planning I/O modules for your Ovation
system.
35.18 Cable specification sheets
The following Emerson approved cables can be used to provide network connections:
 Fiber-optic Cable - MMF SC/SC (5A26164Gxx) (see page 593).
 Cable Fast Ethernet/CDDI CAT5 (5A26155Gxx) (see page 592).
 Remote I/O Cable (3A98763Gxx) (see page 593).
590 OW360_R1005
35.18.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
Attenuation @ 1300 nm length(m) x
0.0015db/m + 2db maximum
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 300 N (66 lb)
increase  0.5db
maximum
Tensile Load at Installation 1776 N
(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
OW360_R1005 591
35.18.2 Network UTP cable specifications
UTP network cable specifications
SPECIFICATION CABLE ASSEM BLY CABLE ASSEM BLY

5 A2 6 1 5 5 G X X 1 1X00063GXX 1
Use of cable Fast Ethernet (Straight-through) Fast Ethernet (Crossover)

Termination Connectors RJ45 RJ45
Raw cable (no connectors) 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)
Maximum Cable Weight 8.55 kg/0.1 km 8.55 kg/0.1 km
(19 lb/100 ft) (19 lb/100 ft)
Maximum Cable length 100 m 100 m
(327 ft) (327 ft)
1 The cable must be routed in solid grounded conduit continuous to the cabinet (CE Mark Certified
Systems only).
592 OW360_R1005
35.18.3 Network Remote I/O cable specifications
Remote I/O cable specifications
SPECIFICATION CABLE ASSEMBLY 3 A9 8 7 6 3 G X X CABLE ASSEM BLY

3 A9 8 7 6 4 G X X
Use of cable Remote I/O Remote I/O

Termination Connectors ST to ST ST to ST
Raw cable (no connectors) 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
Attenuation @ 850 nm length(m) x length(m) x
0.0035db/m + 2db maximum 0.0035db/m + 2db maximum
Attenuation @ 1300 nm length(m) x length(m) x
0.0015db/m + 2db maximum 0.0015db/m + 2db maximum
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 7.5 cm (3 in) 7.5 cm (3 in)

Term)
Cable Assembly - Tensile 175 N (40 lb) 175 N (40 lb)
Load for attenuation
maximum maximum
increase  0.5db
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)
Maximum Cable Weight 46 kg/1 km 46 kg/1 km

(31 lb/1000 ft) (31 lb/1000 ft)
Maximum Cable length 2 km (6560 ft) using 850 nm 2 km (6560 ft) using 850 nm
4 km (13,123 ft) using 1300 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
OW360_R1005 593
Index
Analog Output module (4 Channel) • 138

A Antivirus software • 352
AC/DC Mains wiring requirements • 95 Antivirus software (importance) • 353
Acknowledged list in the Operator Station Appliances in the Ovation Security Center •
Alarm window • 414 444
Advantages of the Ovation Process Archiving your data • 364
Historian • 356 audit schema • 284
Alarm Annunciation window definition • 422 Auxiliary ground strap • 101
Alarm Check Remove list in the Operator
B
Station Alarm window • 417
Alarm definition • 404 Backing up and restoring • 516
Alarm delays • 431 backup and restore operations • 516
Alarm display types • 408 Best practices for establishing a secure
Alarm example • 404 system • 352
Alarm filtering • 425 Best practices for installing Ovation 3.6.0
Alarm flood definition • 424 software • 300
Alarm Frequency list in the Operator Station Bus interface module power supply
Alarm window • 418 requirements • 240
Alarm limits • 429 Bus interface modules (main/aux power and
Alarm List in the Operator Station Alarm main/aux heat dissipation) (drawn from
window • 412 AC/DC Mains power) • 31
Alarm list information fields • 409
Alarm lists that display in the Alarm window • C
410 Cabinet circuit breaker/on/off switch • 227
Alarm logging methods • 427 Cabinet configuration guidelines • 173
Alarm management benefits • 432 Cabinet EMC grounding • 97
Alarm management definition • 405 Cabinet weights • 202
Alarm management problems • 405 Cabinets (user-supplied) • 206
Alarm planning best practices • 406 Cabinets, sealed, NEMA12 with Marshalling
Alarm rates • 424 mounting plate • 545
Alarm reduction methods • 430 Cabinets, sealed, NEMA12 with standard
Alarm reduction techniques • 431 mounting plate • 536
Alarm suppression logic • 430 Cabinets, sealed, NEMA4 with Marshalling
Alarm system operation • 408 mounting plate • 558
Alarms that use audio • 427 Cabinets, sealed, NEMA4 with standard
Alternative shield grounding • 270 mounting plate • 550
Analog I/O module power supply Cabinets, vented, NEMA12 with Marshalling
requirements • 231 mounting plate • 531
Analog I/O modules (main/aux power and Cabinets, vented, NEMA12 with no
main/aux heat dissipation) (drawn from mounting plate • 563
AC/DC Mains power) • 18 Cabinets, vented, NEMA12 with standard
Analog Input High Speed module (14 Bit) (8 mounting plate • 520
Channel) • 133 Cable configuration types • 87
Analog Input module (0-10V High Cable connection types for your network • 52
Impedance) (8 channel) • 133 Cable specification sheets • 590
Analog Input module (13 Bit) (8 Channel) Cabling requirements for CE Mark Certified
(Legacy product) • 131 systems • 270
Analog Input module (14 Bit) (8 Channel) • Cabling requirements for IEC61131-2
132 certified systems • 272
Analog Input module 4-20mA (16 Channel) • Calculating main power requirements • 37
137 Capacities for Ovation SIS system • 453
OW360_R1005 595
Index
Capacities for Ovation SIS with Electronic Dell PowerEdge R320 (Rack Mount)
Marshalling system • 496 (5X00695) • 576
CE Mark accuracy considerations • 266 Dell PowerEdge R720 (Rack Mount) (Linux
CE Mark certified systems • 265 Server) (5X00722) • 577
Communication interface message protocols Dell PowerEdge R720 (Rack Mount)
• 436 (Windows Server) (5X00723) • 577
Communication interface physical Dell PowerEdge R730 (Rack Mount)
connections • 436 (5X00727) • 574
Communication interface platforms • 435 Dell PowerEdge R730 (Rack Mount)
Communication interface spreadsheets • (5X00728) • 575
437 Dell PowerEdge R730 (Rack Mount)
Components of an Ovation system • 2 (5X00730) • 575
Connecting equipment to your network • 57 Dell PowerEdge R730 (Rack Mount)
Connecting OCR400 or OCR1100 (5X00731) • 576
Controllers to your Ovation network • 58 Dell PowerEdge T110 II (5X00659) • 570
Connections for core switches • 84 Dell PowerEdge T320 (5X00618) • 569
Connectivity definition • 435 Dell PowerEdge T320 (5X00619) • 572
Connectivity products • 5 Dell PowerEdge T630 (Linux Server)
Control Builder terminology • 316 (5X00720) • 572
Control design best practices • 321 Dell PowerEdge T630 (Windows Server)
Control functions (control sheets) • 315 (5X00721) • 573
Control planning process • 311 Dell Precision M6800 Laptop Workstation
Control project scope • 319 (1X00895) • 589
Control sheet building best practices • 322 Dell Precision R7910 (Rack Mount)
Control types supported in Ovation • 309 (5X00729) • 574
Controller cabinet • 175 Dell U2412M (24 • 580
Controller cabinet configuration for local Dell U3014 (30 • 579
Ovation I/O • 176 Desktop Tools? • 366
Controller cabinet configuration for local Q- Developer Studio (Windows) • 4
Line I/O • 176 DeviceNet and Ovation components • 401
Controller cabinet configuration for mixed DeviceNet hardware and software
(local and remote) Ovation I/O • 176 requirements • 402
Controller cabinet configuration for remote DeviceNet interoperability • 399
Ovation I/O • 176 DeviceNet module • 151
Controller cabinet configuration for remote DeviceNet module definition • 402
Q-Line I/O • 177 Diagnostic power supply LEDs • 217
Controller cabinet illustrations • 178 Diagrams in planning control • 312
Controller cabinet maintenance • 204 Digital Excitation Controller (DEC) module •
Controller OCR400 and Controller OCR1100 165
backplane example • 214 Digital I/O module power supply
Controller power switch • 228 requirements • 234
Copyright Notice • 2 Digital I/O modules (main/aux power and
Criteria for using the restore type • 518 main/aux heat dissipation) (drawn from
AC/DC Mains power) • 22
D Digital Input Compact Contact module (16
Data collision prevention • 40 Channel) • 141
Data link and application layers • 375 Digital Input Compact module (16 Channel) •
Database relate to other Ovation functions? 140
• 282 Digital Input Contact module (16 Channel) •
Database terminology • 285 141
Database tools • 293 Digital Input module (16 Channel) • 139
Databases types • 281 Digital Input module 24 VDC (32 Channel) •
Dell OptiPlex 3020 (5X00678) • 571 145
Dell OptiPlex 9020 (5X00673) • 571 Digital Input Redundant module (16
Dell P1914S (19 • 581 Channel) (Windows Ovation 3.2 and
Dell P2014H (20 • 581 above) • 140
Dell P2213H (22 • 580
596 OW360_R1005
Index
Digital Output High Side (24 VDC) module Foundation Fieldbus I/O • 380
(16 Channel) • 146 Foundation Fieldbus interoperability • 369
Digital Output module (16 Channel) • 145 Foundation Fieldbus modulating valves •
Digital Output module 24 VDC (32 Channel) 380
• 146 Foundation Fieldbus module • 151
Disk partitioning • 299 Foundation Fieldbus motor control centers
Displaying Alarm lists • 409 and variable frequency drives • 380
Distance between network nodes • 90 Foundation Fieldbus partitioning instruments
Do you need redundant historian servers? • and applications • 381
363 Foundation Fieldbus pressure, level and flow
Do you want to use the Desktop Tools? • • 380
366 Foundation Fieldbus recommended
Domain concept usage in security • 351 installation practices • 381
Drop types • 304 Foundation Fieldbus second generation
Dual Branch I/O Transition Panel - top solutions • 371
(ROP) (3A99266) • 213 Foundation Fieldbus segmentation design •
376
E Foundation Fieldbus temperature
eDB or HSR migration • 366 measurements • 380
Electrical information for Ovation equipment Foundation Fieldbus topology • 377
• 15 Four-slot I/O Base with common strip
Elements of an Ovation system • 5 connections (5X00497) • 118
End users for OPH • 365 Functional diagram • 220
Equipment locations • 13 Functions of Ovation SIS • 450
Equipment protection • 14 Functions of Ovation SIS with Electronic
Establishing a philosophy for alarm Marshalling • 494
management • 406 Functions of the Alarm Health Advisor • 433
Ethernet Link Controller (ELC) module • 152 Functions of Virtual SIS • 506
Ethernet switches provide network stability • Functions of Virtual SIS CHARMs • 510
46 Functions performed by using the Ovation
Example of a second generation network Process Historian • 355
switch configuration file • 47
G
Examples of cable access areas and floor
bolting in Ovation cabinets (Hoffman Gigabit Ethernet network configurations • 43
cabinets) • 192 Grounding cable shields for CE Mark
Examples of cable access areas and floor Certified systems • 267
bolting in Ovation cabinets (Rittal Grounding cable shields for IE61131-2
cabinets) • 197 certified system • 271
Extended cabinet configuration illustrations • Grounding guidelines • 97
184 Grounding guidelines for clustered cabinet
Extended I/O cabinet • 183 arrangements • 100
Extended I/O cabinet (illustrating cables and Grounding guidelines for single cabinet
relay output modules) example • 210 arrangements • 98
Extended I/O cabinet (illustrating cables and Grounding panel (3A99245G01) method •
standard I/O) example • 209 267
External security definition • 348 Grounding panel configuration • 268
Guidelines for replacing, adding, or
F combining Ovation modules • 166
Fast Ethernet network configurations • 42 Guidelines for shipping and storage of
Field wiring available usage • 200 Ovation equipment • 259
Field wiring requirements • 94
H
Fieldbus terminology • 370
Floor plan recommendations • 203 Hardware and software components of the
Foundation Fieldbus and Ovation Ovation Security Center • 444
components • 372 Hardware cabinet design example • 480
Foundation Fieldbus definition • 368 Hardware components of Ovation SIS • 486
Foundation Fieldbus discrete I/O • 380
OW360_R1005 597
Index
Hardware components of Ovation SIS with I/O module definition • 103

Electronic Marshalling • 499 I/O module features • 109
Hardware information for Ovation multiple I/O module types • 130
networks • 85 I/O modules (add new) • 169
Hardware requirements for a domain I/O modules (hot swap) • 168
member that is a Database Server • 301 I/O modules installation • 167
Hardware requirements for a domain Iconic list in the Operator Station Alarm
member that is NOT a Database Server • window • 418
304 IEC61131-2 certified system definition • 271
Hardware requirements for a Remote Industry standards of compliance (design
Station drop • 306 standards) • 273
Hardware requirements for Domain Industry standards of compliance (electrical
Controllers (primary or redundant) • 301 interference standards) • 273
Hardware requirements for the historian • Industry standards of compliance (reliability
359 standards) • 273
Hardware requirements for Virtual SIS • 507 Industry standards of compliance (safety
Hardware requirements for Virtual SIS standards) • 273
CHARMs • 511 Installation tools • 485
Hardware specification sheets overview • Internal security definition • 348
519 Internet address classes • 275
Hardware used in Ovation networks • 46 Internet address conventions • 277
Hardware/Device spreadsheet • 438 Internet address notation • 276
HART Analog Input module (8 Channel) • Internet address subnet masks • 277
134 Internet addresses (allowable) • 276
HART Analog Output module (8 Channel) • Introduction to planning your Ovation system
138 •1
HART High Performance Analog Input IP addressing • 67
module (8 Channel) • 134 IP traffic switch • 56
HART High Performance Analog Output
module (4 Channel) • 139 K
Historian component overview • 356 KC Compliance mark • 270
Historian planning overview • 361 Keyboard specification sheet • 584
Historian server redundancy • 360
Historian terminology • 357 L
Historians (OPH) needed • 362
Licensing in Multiple Networks • 84
Historical storage and reporting capabilities •
Licensing requirements for an Ovation
5
Windows-based system • 303
History list in the Operator Station Alarm
Licensing requirements for Virtual SIS
window • 413
CHARMs • 512
How does the historian work? • 361
Lifting Ovation equipment guidelines • 261
How many I/O modules can an OCR400 or
Link Controller module • 152
an OCR1100 Controller support? • 175
Local and Remote Network Concepts • 65
HP B/W Laserjet M712n (5X00639) • 587
Loop Interface module • 153
HP Color Laserjet Enterprise
CP4025n/CP4025dn (1X00989) • 586 M
HP Color Laserjet Enterprise M750
(5X00677) • 586 Machinery Health Monitor module • 164
HP Color Officejet 7612 Wide Format e-All- Managing alarms best practices • 423
in-one (1X00995) • 585 Marshalling cabinet • 180
Marshalling cabinet configuration
I illustrations • 180
Marshalling two-slot I/O Base (1X00014) •
I/O cabinet components (main/aux power
116
and main/aux heat dissipation) (drawn
Marshalling two-slot I/O Base with secure
from AC/DC Mains power) • 16
connectors (5X00334) • 117
I/O cabinet components power supply
requirements • 229
I/O interface ports • 329
598 OW360_R1005
Index
MAU with typical fiber-optic connector pairs NEMA12, sealed, 2000 mm x 900 mm x 600
for OCR400 and OCR1100 Controllers • mm, Rittal (1X00907H01) • 549
121 NEMA12, sealed, 2000 mm x 900 mm x 600
Media converters • 89 mm, Rittal (1X00907H02) • 543
Media converters used in Ovation networks • NEMA12, sealed, 2000 mm x 914 mm x 600
51 mm, Hoffman (1X00455H01) • 548
Miscellaneous specification sheets • 589 NEMA12, sealed, 2000 mm x 914 mm x 600
Monitor specification sheets • 579 mm, Hoffman (1X00455H02) • 542
Multi-mode fiber optic cable • 88 NEMA12, vented, 2000 mm x 600 mm x 400
Multi-networking (basics) • 64 mm, (front access only) Hoffman
Multi-networks work (what is needed) • 70 (5X00068H01/H02) • 521
Multiple network and new Ovation systems • NEMA12, vented, 2000 mm x 600 mm x 400
77 mm, Rittal (1X00903H01) • 522
Multiple network definition • 63 NEMA12, vented, 2000 mm x 600 mm x 600
Multiple network planning guidelines for mm, (without mounting plate) Rittal
Ovation systems • 74 (1X00901H01) • 566
Multiple network terminology • 72 NEMA12, vented, 2000 mm x 600 mm x 600
Multiple networks (before connecting) • 76 mm, Hoffman (5X00020H01/H02) • 564
Multiple networks and existing Ovation NEMA12, vented, 2000 mm x 600 mm x 600
systems • 78 mm, Hoffman (5X00127H01/H02) • 524
Multiple networks and hybrid Ovation NEMA12, vented, 2000 mm x 600 mm x 600
systems • 79 mm, Rittal (1X00900H01) • 525
Multiple networks backbone connectivity • 81 NEMA12, vented, 2000 mm x 600 mm x 800
Multiple networks collapsed backbone mm, Rittal (1X00908H01) • 566
connectivity • 83 NEMA12, vented, 2000 mm x 600 mm x 813
Multiple networks connection plan • 80 mm, Hoffman (1X00586H01) • 565
NEMA12, vented, 2000 mm x 800 mm x 600
N mm, Hoffman (5X00021H01/H03) • 532
NAS/iSCSI RAID 5 SATA Storage NEMA12, vented, 2000 mm x 800 mm x 600
(5X00683) • 588 mm, Hoffman (5X00021H02/H04) • 526
NEC P403 (40 • 583 NEMA12, vented, 2000 mm x 800 mm x 600
NEC P463-AVT (46 • 582 mm, Rittal (1X00904H01) • 533
NEC P553 (55 • 582 NEMA12, vented, 2000 mm x 800 mm x 600
NEC V323 (32 • 583 mm, Rittal (1X00904H02) • 527
NEMA 12, vented, 2000 x 600 x 500 mm, NEMA12, vented, 2000 mm x 900 mm x 600
Hoffman (5X00018H01) • 523 mm, Rittal (1X00906H01) • 535
NEMA12, EMC cabinet, sealed, 2000 mm x NEMA12, vented, 2000 mm x 900 mm x 600
600 mm x 600 mm, Rittal (1X00520H02) • mm, Rittal (1X00906H02) • 529
544 NEMA12, vented, 2000 mm x 914 mm x 600
NEMA12, EMC cabinet, vented, 2000 mm x mm, Hoffman (1X00454H01) • 534
600 mm x 600 mm, Rittal (1X00520H01) • NEMA12, vented, 2000 mm x 914 mm x 600
530 mm, Hoffman (1X00454H02) • 528
NEMA12, sealed 2000 mm x 600 mm x 600 NEMA4, sealed, 2000 mm x 600 mm x 500
mm, Rittal (1X00902H01) • 539 mm, Hoffman (5X00019H02) • 551
NEMA12, sealed, 2000 mm x 600 mm x 500 NEMA4, sealed, 2000 mm x 600 mm x 600
mm, Hoffman (5X00019H01) • 537 mm, Hoffman (5X00046H02/H04) • 552
mm, Hoffman (5X00046H01/H03) • 538 mm, Rittal (1X00902H02) • 553
mm, Hoffman (5X00035H01/H05) • 546 mm, Hoffman (5X00035H02/H06) • 558
mm, Hoffman (5X00035H03/H07) • 540 mm, Hoffman (5X00035H04/H08) • 554
mm, Rittal (1X00905H01) • 547 mm, Rittal (1X00905H02) • 560
mm, Rittal (1X00905H03) • 541 mm, Rittal (1X00905H04) • 555
OW360_R1005 599
Index
NEMA4, sealed, 2000 mm x 900 mm x 600 Ovation I/O module environmental

mm, Rittal (1X00907H03) • 562 specifications • 590
NEMA4, sealed, 2000 mm x 900 mm x 600 Ovation I/O reference terminology • 104
mm, Rittal (1X00907H04) • 557 Ovation input/output modules • 3
NEMA4, sealed, 2000 mm x 914 mm x 600 Ovation Keyboard (4D33935) • 584
mm, Hoffman (1X00455H03) • 561 Ovation Master Database schema • 283
NEMA4, sealed, 2000 mm x 914 mm x 600 Ovation network • 2
mm, Hoffman (1X00455H04) • 556 Ovation network generations • 43
Network cable (EMI/RFI environment) • 89 Ovation Operator Stations • 4
Network cable (finding diameter) • 100 Ovation Power Distribution Module (PDM)
Network cable (grounding) • 90 example • 212
Network cable (selecting) • 89 Ovation Process Historian overview • 355
Network cable infrastructure • 89 Ovation reference documentation • 11
Network cables (installed) • 90 Ovation Remote Node cabinet (illustrating
Network Fiber-Optic cable specifications cables) example • 211
(5A26164Gxx) • 591 Ovation requirements for Virtual SIS • 508
Network Interface ports • 327 Ovation second generation network
Network name alias concept • 66 technology • 44
Network planning guidelines for Ovation Ovation Server Cabinet vented (1X00545) •
systems • 57 567
Network Remote I/O cable specifications • Ovation system definition • 1
593 Ovation system terminology • 7
Network terminology • 40 Ovation third generation network technology
Network topology • 53 • 45
Network UTP cable specifications • 592 Ovation Workstation Cabinet vented
Non-Foundation Fieldbus instruments • 381 (1X00518) • 567
Non-Ovation devices (connecting) • 61 Ovation workstation specification sheets •
Nuisance alarms • 424 568
Nuisance alarms management • 424 Overview of planning the Virtual SIS
Numalogic Fast Ethernet Remote Node • CHARMs system • 512
163
P
O
Part failure during project startup • 257
Obtaining a Material Return Tracking (MRT) Part repairs (tracking) • 257
number • 255 Parts repairs (handling) • 256
OCR400 Controller and OCR1100 Controller Parts return • 254
Modules • 205 Phoenix Contact PC with display Windows 7
OCR400 Controller/Marshalling cabinet (with (VL2 PPC 3000) (1X01011) • 578
local and remote cabling) example • 208 Phoenix Contact Valueline PC (Panel
Off-loading and unpacking Ovation Mount) (1X00919) • 578
equipment • 262 Physical layer • 374
Oil diagrams • 313 Piping and instrumentation diagrams (P&ID)
Okidata Microline 395C (5X00445) • 586 • 313
OPH third-party software • 366 Planning alarm management • 403
organization of the Ovation database • 283 Planning cable configurations for your
Other possible multi-network configurations • Ovation system • 87
68 Planning Connectivity for your Ovation
Ovation cabinet components • 174 system • 435
Ovation cabinet definition • 172 Planning control best practices • 320
Ovation Control Builder definition • 310 Planning control for your Ovation system •
Ovation control definition • 308 307
Ovation Controller I/O interfaces • 327 Planning for an Ovation Process Historian
Ovation Controllers • 3 (OPH) • 355
Ovation database • 3 Planning for DeviceNet • 397
Ovation Database (creating) • 292 Planning for Profibus • 385
Ovation devices (connecting) • 61 Planning for replacement parts and repair
Ovation hardware specification sheets • 519 service • 253
600 OW360_R1005
Index
Planning for second generation (I/O module) Power supply limits • 226
Foundation Fieldbus • 367 Power supply locking mechanism • 221
Planning grounding for your Ovation system Power supply module • 226
• 97 Power supply modules (using) • 224
Planning I/O modules for your Ovation Power supply replacement cautions • 223
system • 103 Power supply requirements (drawn from
Planning network and I/O field wiring routing +24V main or auxiliary power supply) •
• 91 229
Planning Ovation cabinets for your Ovation Power supply requirements for remote
system • 171 function modules • 244
Planning power for your Ovation cabinets • Power supply specifications • 222
207 Power supply status monitoring • 244
Planning security for your Ovation system • Power supply wiring connections • 219
347 Power supply wiring illustration • 218
Planning Simulation • 331 Ppower distribution in an Ovation system •
Planning software installation for Windows- 207
based Ovation systems • 295 Printer specification sheets • 585
Planning the SIS hardware installation • 485 Profibus and Ovation components • 388
Planning to meet industry standards of Profibus device interoperability • 387
compliance • 273 Profibus devices • 389
Planning Virtual Controllers • 335 Profibus DP module • 151
Planning your CE Mark Certified and KC Profibus hardware and software
Compliance mark systems • 265 requirements • 395
Planning your IEC61131-2 system • 271 Protective earth • 97
Planning your internet addressing • 275 Pulse Accumulator module • 156
Planning your Ovation Controller • 325
Planning your Ovation database • 279 R
Planning your Ovation equipment • 13 Reasons to use a single historian for
Planning your Ovation multiple networks • 63 multiple units • 362
Planning your Ovation network • 39 Reasons to use an embedded historian •
Planning your Ovation Security Center • 443 362
Planning your Safety Instrumented System • Reasons to use multiple historians • 362
449 Redundant power supplies (monitoring one
Planning your Safety Instrumented System set) • 244
(SIS) with Electronic Marshalling • 493 Redundant power supplies (monitoring two
Planning your System Backup and Restore • sets) • 245
515 Relational Database definition • 280
Planning your Virtual Safety Instrumented Relay Output (Fused) panel • 150
System • 505 Relay Output Base (12 channel fused) high-
Planning your Virtual Safety Instrumented power relay KUEP (5X00430) • 127
System (SIS) with Electronic Marshalling • Relay Output Base (12 channel non-fused)
509 high-power KUEP (1C31222) • 128
Plant process schematics • 314 Relay Output Base (16 channel fused) low-
PlantWeb Alerts for Foundation Fieldbus power relay GR2 (5X00431) • 125
alarms • 428 Relay Output Base (16 channel non-fused)
Point description • 286 low-power relay GR2 (1C31223) • 126
Point frequency description • 289 Relay Output Base (32 channel fused) Slim
Point name understanding • 289 28x5mm relay (5X00623) • 123
Point names (fully qualified) • 292 Relay Output Base (32 channel non-fused)
Point names (valid) • 290 Slim 28x5mm relay (5X00584) • 124
Point out of service • 407 Relay Output Base (8 channel with contact
Point record description • 288 monitoring) high-power KUEP (5X00564) •
Points used as alarms • 407 129
Power distribution scheme • 251 Relay Output Bases • 122
Power mains connections • 214 Relay Output Electronics modules (hot
Power supply features • 224 swap) • 169
Power supply front view • 216 Relay Output I/O modules (add new) • 170
OW360_R1005 601
Index
Relay Output module installation • 169 Sequence of Events Contact Input Field
Relay Output panel • 147 module (32 Channel) • 142
Relay Output panel (32 Channel) • 149 Sequence of Events Digital Input module (16
Relay Output panel with Contact Monitoring Channel) • 142
module • 148 Sequence of Events Enhanced Compact
Relay Panel cabinet configuration Digital Input module (16 Channel) • 144
illustrations • 191 Servo Driver (RSR) module • 157
Release version spreadsheet • 440 Shipping Ovation equipment guidelines •
Remote function modules (main/aux power 259
and main/aux heat dissipation) (drawn Shorting bar removal • 101
from AC/DC Mains power) • 37 Single-mode fiber optic cable • 88
Remote function modules (RIO) • 120 Single-mode fiber optic cable (planning) • 88
Remote Network Status list in the Operator Single-tier network arrangement • 54
Station Alarm window • 420 SIS aspects to consider • 452
Remote Node cabinet • 186 SIS environmental specifications for Ovation
Remote Node cabinet configuration SIS devices • 454
illustrations • 187 SIS environmental specifications for Ovation
Remote Node Controller (RNC) (1C31205) • SIS with Electronic Marshalling devices •
122 497
Remote Node Transition Panel (dual-branch SIS Network with four (4) SIS Switches • 455
TND - top) (1P00028) • 213 SIS Network with one (1) SIS Switch • 476
Repacking and returning Ovation equipment SIS Network with three (3) SIS Switches •
• 262 465
Repacking third-party products • 263 SIS Network with two (2) SIS Switches • 472
Repair prices • 257 SIS System • 454
Reporting issues • 508 SIS with Electronic Marshalling aspects to
Reset list in the Operator Station Alarm consider • 494
window • 416 Small Form-factor Pluggable Transceivers
Restoring Active Directory Domain Services (SFPs)? • 330
(AD DS) (Domain Controllers) • 517 Small Loop Interface module (SLIM) • 163
Role of the Control Builder in Ovation • 311 Software components of Ovation SIS • 488
RTD Analog Input module (16 Channel) • Software installation terminology • 296
136 Software requirements for a Domain
RTD Analog Input module (4 Channel) • 135 Controller (primary or redundant) • 302
RTD Analog Input module (8 Channel Software requirements for a domain member
Compact) • 136 • 302
RTD Analog Input module (8 Channel) • 135 Software requirements for the historian • 359
Rules for working with Virtual SIS • 507 Software requirements for Virtual SIS • 508
Rules for working with Virtual SIS CHARMs • Software requirements for Virtual SIS
510 CHARMs • 511
Solid and stranded wire AWG diameters • 99
S Spare part number • 253
Safety Instrumented Functions (SIFs) • 453, Spare part price • 254
495 Spare parts ordering • 253
Safety Instrumented System terminology • Specialty I/O module power supply
450 requirements • 241
Safety Integrity Levels (SILs) • 453, 495 Specialty I/O modules (main/aux power and
Scanners needed • 363 main/aux heat dissipation) (drawn from
Scenario simulation model for high fidelity AC/DC Mains power) • 32
simulators • 333 Spectracom SecureSync GPS Modular Time
Security and multiple networks • 84 Synchronization System (1X00932) • 589
Security standards • 274 Speed Detector module • 158
Security terminology • 349 Standard Ovation I/O module Base
Selecting an alarm filtering mode • 427 components • 111
Sequence of Events Compact Digital Input Standard two-slot Ovation I/O Base
Field Interface module (16 Channel) • 143 assembly (1B30035) • 115
Storage device specification sheets • 588
602 OW360_R1005
Index
Storing Ovation equipment • 263

Storyboarding for control • 314 W
Summary of Changes • 3 What are other control products? • 322
Supported Ovation applications • 305 What are Ovation SIS Logic Solver
Supported SIS Local Safety Network • 497 algorithms? • 489
Supported SIS network • 455 What are the architecture types of Ovation
Switches used in Ethernet second and third Virtual Controllers? • 342
generation Ovation networks • 47 What are the DeviceNet communication
Switches used in Gigabit Ovation networks • methods? • 399
50 What are the hardware requirements for the
System expansion planning • 316 Ovation Virtual Controller host? • 345
T What are the requirements for Ovation
Virtual Controllers? • 345
Terminology for the Ovation Security Center What are the Simulation components? • 331
• 445 What are the software requirements for the
Terminology of Virtual SIS CHARMs • 510 Ovation Virtual Controller host? • 345
Thermocouple Input module (16 Channel) • What are the supported Fieldbus
137 algorithms? • 383
Third-party components usage in CE Mark What are the Virtual Controller commands? •
Certified systems • 266 339
Third-party devices • 5 What are the Virtual Controller license
Tie-back simulation model • 334 types? • 346
To connect the AC/DC Mains to the input What is a RADIUS server? • 353
power DIN rail assembly • 214 What is a Safety Instrumented System with
To prepare for connecting an external power Electronic Marshalling? • 493
supply • 247 What is a Safety Instrumented System? •
To replace Controller modules • 206 449
To support acyclic exchange of data • 395 What is Alarm Shelving? • 421
Transporting Ovation equipment to the What is Alarm Suppression? • 421
specific installation location • 263 What is an external supply? • 246
Two-tier network arrangement • 55 What is an Ovation Virtual Controller Host? •
338
U What is an Ovation Virtual Controller? • 338
Unacknowledged list in the Operator Station What is DeviceNet messaging? • 399
Alarm window • 415 What is DeviceNet? • 398
Understanding disk storage • 298 What is involved in the Ovation installation
Understanding heat dissipation • 15 process? • 296
Understanding Ovation networks • 39 What is needed to license the Virtual
Unshielded twisted pair (UTP) cable • 87 Controller? • 346
User layer • 375 What is Ovation hardening? • 351
Using characteristics for filtering alarms • What is Ovation Virtual Controller
425 simulation? • 335
Using priorities for filtering alarms • 426 What is Profibus module redundancy? • 391
Using security for alarm management • 428 What is Profibus port redundancy? • 394
What is Profibus? • 386
V What is Remote Alarm Viewer? • 434
What is Scenario simulation? • 331
Valve Positioner module • 162
What is the Alarm Guidance window? • 434
Viewing diagrams from the Icon List • 419
What is the Alarm Health Advisor? • 433
Virtual Controller terminology • 341
What is the benefit of using the Alarm Health
Virtual Controllers usage • 337
Advisor? • 433
Virtual SIS CHARMs with hardware-based
What is the Foundation Fieldbus
Ovation • 512
communications model? • 374
Virtual SIS CHARMs with Virtual Ovation •
What is the operation of the Virtual
513
Controller? • 340
Virtual SIS terminology • 506
What is the Ovation Controller? • 326
What is the Ovation Remote Station? • 305
OW360_R1005 603
Index
What is the Ovation Security Center? • 443

What is the purpose of an Ovation I/O
module? • 104
What is the Simulation process? • 332
What is the Virtual Controller Manager
window? • 341
What is the Virtual Controller networked
architecture? • 344
What is the Virtual Controller single-machine
architecture? • 343
What is Virtual Safety Instrumented System
with Electronic Marshalling? • 509
What is Virtual Safety Instrumented System?
• 505
Who uses Virtual Controller technology? •
336
Why perform Ovation system backups? •
515
Workstations (connecting) • 60
604 OW360_R1005

OW360 - R1005 - Planing Your Ovation System

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OW360 - R1005 - Planing Your Ovation System

Uploaded by

Copyright:

Available Formats

Planning Your Ovation System

(For use with Ovation 3.6.0 systems and Feature Pack 1)

Emerson Process Management Power & Water Solutions

1 Introduction to planning your Ovation system 1

2 Planning your Ovation equipment 13

3 Planning your Ovation network 39

3.4.2 Ovation third generation network technology....................................................... 45

4 Planning your Ovation multiple networks 63

5 Planning cable configurations for your Ovation system 87

5.2.4 Distance between network nodes ........................................................................ 90

6 Planning grounding for your Ovation system 97

7 Planning I/O modules for your Ovation system 103

7.12.9 RTD Analog Input module (8 Channel Compact) .............................................. 136

8 Planning Ovation cabinets for your Ovation system 171

9 Planning power for your Ovation cabinets 207

9.4 Power supply wiring illustration ....................................................................................... 218

10 Planning for replacement parts and repair service 253

11 Guidelines for shipping and storage of Ovation equipment 259

12 Planning your CE Mark Certified and KC Compliance mark systems

13 Planning your IEC61131-2 system 271

14 Planning to meet industry standards of compliance 273

15 Planning your internet addressing 275

16 Planning your Ovation database 279

16.8 What is point frequency? ................................................................................................. 289

17 Planning software installation for Windows-based Ovation systems

18 Planning control for your Ovation system 307

19 Planning your Ovation Controller 325

20 Planning Simulation 331

21 Planning Virtual Controllers 335

22 Planning security for your Ovation system 347

23 Planning for an Ovation Process Historian (OPH) 355

24 Planning for second generation (I/O module) Foundation Fieldbus 367

25 Planning for Profibus 385

26 Planning for DeviceNet 397

27 Planning alarm management 403

28 Planning Connectivity for your Ovation system 435

29 Planning your Ovation Security Center 443

30 Planning your Safety Instrumented System 449

30.5 Capacities for Ovation SIS system ................................................................................. 453

31 Planning your Safety Instrumented System (SIS) with Electronic

32 Planning your Virtual Safety Instrumented System 505

33 Planning your Virtual Safety Instrumented System (SIS) with

33.6 Software requirements for Virtual SIS CHARMs ............................................................. 511

34 Planning your System Backup and Restore 515

35 Ovation hardware specification sheets 519

1 Introduction to planning your Ovation system

What is an Ovation system? ............................................................................................... 1

1.1 What is an Ovation system?

1.2 What are the components of an Ovation s ystem?

Ovation offers unique features to its users:

1.2.1 Ovation network

1.2.2 Ovation database

1.2.3 Ovation input/output modules

1.2.4 Ovation Controllers

1.2.5 Ovation Operator Stations

1.2.6 Developer Studio (Windows)

These Power Tools perform the following functions:

1.2.7 Historical storage and reporting capabilities

1.2.8 Third-party devices

1.2.9 Connectivity products

1.3 Planning the elements of an Ovation system

System Configuration Reference Manuals

DOCUME NT NAME DESCRIPTION