SIS-OW351 - 47 - Ovation SIS User Guide

Safety Instrumented System (SIS) User Guide for
Ovation 3.5.1
OW351_47
Version 1
March 2014
Copyright Notice
Since the equipment explained in this document has a variety of uses, the user and those
responsible for applying this equipment must satisfy themselves as to the acceptability of each
application and use of the equipment. Under no circumstances will Emerson Process
Management be responsible or liable for any damage, including indirect or consequential losses
resulting from the use, misuse, or application of this equipment.
The text, illustrations, charts, and examples included in this manual are intended solely to explain
TM
the use and application of the Ovation Unit. Due to the many variables associated with specific
uses or applications, Emerson Process Management cannot assume responsibility or liability for
actual use based upon the data provided in this manual.
No patent liability is assumed by Emerson Process Management with respect to the use of
circuits, information, equipment, or software described in this manual.
No part of this publication may be reproduced, stored in a retrieval system, or transmitted in any
form or by any means, including electronic, mechanical, photocopying, recording or otherwise
without the prior express written permission of Emerson Process Management.
The document is the property of and contains Proprietary Information owned by Emerson Process
Management and/or its subcontractors and suppliers. It is transmitted in confidence and trust, and
the user agrees to treat this document in strict accordance with the terms and conditions of the
agreement under which it was provided.
This manual is printed in the USA and is subject to change without notice.
Ovation is the mark of Emerson Process Management. Other marks are the property of their
respective holders.
Copyright © Emerson Process Management Power & Water Solutions, Inc. All rights reserved.
Emerson Process Management
Power & Water Solutions
200 Beta Drive
Pittsburgh, PA 15238
USA
E-Mail: Technical.Communications@Emerson.com
Web site: https://www.ovationusers.com
Contents
1 Introduction to Ovation Safety Instrumented System (SIS) 1

1.1 What is a Safety Instrumented System? .......................................................................... 1
1.2 Functions of Ovation SIS ................................................................................................ 2
1.3 Safety Instrumented System terminology ........................................................................ 2
2 Planning the Safety Instrumented System 5

2.1 SIS aspects to consider .................................................................................................. 5
2.1.1 Safety Instrumented Functions (SIFs)................................................................. 6
2.1.2 Safety Integrity Levels (SILs) .............................................................................. 6
2.2 Capacities for Ovation SIS system .................................................................................. 7
2.3 SIS environmental specifications for Ovation SIS devices ............................................... 7
2.4 Supported SIS network ................................................................................................... 8
2.4.1 SIS Network with four (4) SIS Switches .............................................................. 8
2.4.2 SIS Network with three (3) SIS Switches .......................................................... 17
2.4.3 SIS Network with two (2) SIS Switches ............................................................. 23
2.4.4 SIS Network with one (1) SIS Switch ................................................................ 27
2.4.5 Hardware cabinet design example .................................................................... 30
2.5 Planning the hardware installation................................................................................. 39
2.5.1 Installation tools ............................................................................................... 39
3 Hardware for Ovation SIS 41

3.1 Hardware components of Ovation SIS .......................................................................... 41
3.2 SIS Carriers .................................................................................................................. 43
3.2.1 Horizontal Carriers ........................................................................................... 43
3.2.2 Vertical Carriers ............................................................................................... 44
3.2.3 To install the 1-wide Horizontal carrier (dual left-right extender cables) ............. 47
3.2.4 To use 1-wide carrier as a terminator ............................................................... 47
3.2.5 To use the 2-wide Horizontal power/SIS Data Server carriers ........................... 48
3.2.6 To install the Vertical Controller (4-wide Power/SIS Data Server) carrier ........... 50
3.2.7 To install the 8-wide Horizontal I/O interface carrier (can hold up to four
simplex/two redundant Logic Solvers) .............................................................. 51
3.2.8 To install the Vertical (8-wide left/right side) carrier (can hold up to four
simplex/two redundant Logic Solvers) .............................................................. 52
3.3 SLS Simplex and Redundant terminal blocks ................................................................ 53
3.3.1 To install Terminal Blocks................................................................................. 54
3.4 Carrier extender cables................................................................................................. 54
3.4.1 Carrier extender cable part numbers ................................................................ 55
3.4.2 To install carrier extender cables ...................................................................... 55
3.5 SIS Interface Controller (SIS DROP) ............................................................................. 56
3.6 SIS Data Server............................................................................................................ 56
3.6.1 SIS Data Server part number ........................................................................... 56
3.6.2 To install an SIS Data Server ........................................................................... 57
OW351_47 i
Table of Contents
3.6.3 To power up a simplex SIS Data Server ........................................................... 57

3.6.4 To power up an additional SIS Data Server from a redundant pair .................... 58
3.6.5 To remove an Active SIS Data Server from a redundant pair ............................ 58
3.6.6 SIS Data Server LEDs...................................................................................... 59
3.6.7 SIS Data Server specifications ......................................................................... 61
3.7 SIS Logic Solver ........................................................................................................... 61
3.7.1 Logic Solver 8-Slot carrier numbering scheme .................................................. 63
3.7.2 SIS Logic Solver part number ........................................................................... 64
3.7.3 To install Logic Solvers .................................................................................... 64
3.7.4 Logic Solver redundancy .................................................................................. 65
3.7.5 SIS Logic Solver LED indicator patterns ........................................................... 66
3.7.6 Logic Solver specifications ............................................................................... 67
3.7.7 SIS I/O channels .............................................................................................. 67
3.8 SISNet Repeater .......................................................................................................... 72
3.8.1 SISNet Repeater part number .......................................................................... 73
3.8.2 To install SISNet Repeaters for horizontal mounting ......................................... 73
3.8.3 SISNet Distance Extender ................................................................................ 74
3.8.4 SISNet Repeater LEDs .................................................................................... 74
3.8.5 SISNet Repeater specifications ........................................................................ 75
3.8.6 SISNet Distance Extender specifications .......................................................... 76
3.9 Fiber-optic cable\ring .................................................................................................... 77
3.10 Power Supply ............................................................................................................... 77
3.10.1 Power supply part number ................................................................................ 77
3.10.2 Power supply specifications.............................................................................. 78
3.10.3 To install power supplies .................................................................................. 78
3.10.4 To provide power to the Logic Solvers .............................................................. 78
3.10.5 To provide power to the SISNet Repeaters ....................................................... 79
3.10.6 To provide power to SISNet Distance extenders ............................................... 80
3.10.7 SIS Power Supply LEDs ................................................................................... 82
3.11 SIS Network Switches and Routers............................................................................... 82
3.12 Ovation SIS accessories ............................................................................................... 82
3.12.1 SIS Relay module ............................................................................................ 83
3.12.2 Voltage Monitor module.................................................................................... 88
3.12.3 SIS Current Limiter module .............................................................................. 92
3.12.4 Auxiliary Relay DTA-Inverting module .............................................................. 95
3.12.5 Auxiliary Relay ETA-Direct module ................................................................... 99
3.12.6 Auxiliary Relay Diode module ......................................................................... 100
3.12.7 RC Compensator module ............................................................................... 102
3.12.8 End of Line Resistance module ...................................................................... 103
4 Adding and configuring SIS components in the Ovation Developer

Studio 105
4.1 Software components of Ovation SIS .......................................................................... 105
4.2 Overview of adding and configuring SIS components .................................................. 106
4.3 Using the Ovation Developer Studio to configure SIS components .............................. 108
4.4 Verify SIS licenses ...................................................................................................... 108
4.5 To add an SIS System to the Ovation System ............................................................. 108
4.6 To add an SISNet Rings to the Ovation System .......................................................... 109
4.7 To add an SIS Data Server to the Ovation System ...................................................... 111
4.8 To add an SIS Router to the Ovation System .............................................................. 114
4.9 To add an SIS Network Switch to the Ovation System ................................................ 117
ii OW351_47
Table of Contents
4.10 To add an SIS Interface Controller (SIS Drop) ............................................................. 119

4.11 To add an IOIC device and an SIS I/O device number (Device driver) ......................... 120
4.12 To add an I/O device to the Ovation System ............................................................... 123
4.13 To add an SIS I/O device to the Ovation System ......................................................... 123
4.13.1 To associate a Node point with an SIS I/O device ........................................... 127
4.14 To assign an SIS Data Server to an SIS I/O Device .................................................... 129
4.15 To configure SIS LAN Network Switches..................................................................... 132
4.16 To upload configuration files to SIS Switch from Ovation drop using Ovation Network
Connection (Ethernet option): Generate & Configure Source Type .............................. 133
4.17 To generate SIS Switch configuration files for manual configuration: Generate & Save
Source Type ............................................................................................................... 146
4.18 To upload configuration files to SIS Switch from non-Ovation drop using serial connection
(Serial option): Configure via Serial Source Type ........................................................ 151
4.19 To add and configure SIS Logic Solvers in the Ovation System................................... 161
4.19.1 Configuring the Logic Solver Config tab .......................................................... 163
4.19.2 Configuring the Logic Solver General tab ....................................................... 165
4.19.3 Configuring the Logic Solver Proof Testing tab ............................................... 167
4.20 To configure an SIS I/O channel ................................................................................. 168
4.20.1 Configuring a Digital Input Channel ................................................................ 170
4.20.2 Configuring a Digital Output Channel.............................................................. 171
4.20.3 Configuring a HART Analog Input Channel ..................................................... 172
4.20.4 Configuring a HART Two-state Output Channel.............................................. 174
4.20.5 Configuring an Analog Input Channel ............................................................. 176
4.21 Ovation Point for SIS Hardware Inputs (Analog/Digital Inputs) ..................................... 177
4.22 SIS Hardware Outputs (Digital Outputs) ...................................................................... 180
4.23 To configure SIS Control Modules............................................................................... 185
4.24 To add an SIS Control Sheet to the SIS Ovation system ............................................. 187
4.25 SIS Alarming with Logic Solver timestamp .................................................................. 188
4.25.1 Configuring Ovation system for SIS alarms..................................................... 188
4.25.2 Configuring an alarm for SIS digital point ........................................................ 190
4.25.3 SIS Sensor Alarms ......................................................................................... 191
4.26 To view SIS points ...................................................................................................... 195
4.27 Removing or Deleting an SIS Point ............................................................................. 197
4.27.1 To remove an SIS Point from the SIS Control Sheets ..................................... 197
4.27.2 To delete an SIS Point ................................................................................... 197
5 Using Ovation SIS 199

5.1 Loading Logic Solvers................................................................................................. 199
5.1.1 To load an SIS Logic Solver ........................................................................... 199
5.2 Using Point Information (PI) to identify SIS points ....................................................... 201
5.2.1 To use Point Information to identify SIS points ................................................ 202
5.3 Viewing SIS Tuning windows for SIS algorithms.......................................................... 203
5.3.1 To access the SIS Tuning window for SIS algorithms ..................................... 204
5.3.2 SIS Tuning window for the LSCEM algorithm ................................................. 204
5.4 Forcing an algorithm input value ................................................................................. 205
5.4.1 To force an algorithm input value .................................................................... 206
5.4.2 To set a new forced SIS algorithm input value and quality .............................. 212
5.4.3 To clear the force value and leave Debug mode ............................................. 215
OW351_47 iii
Table of Contents
5.5 Bypasses and overrides .............................................................................................. 217

5.5.1 Override types................................................................................................ 218
5.5.2 Configuration of bypasses .............................................................................. 218
5.5.3 Operation of bypasses ................................................................................... 218
5.6 Making online scaling changes in HART transmitters .................................................. 220
5.7 Restarting a Logic Solver ............................................................................................ 221
5.7.1 To restart (reboot) a Logic Solver ................................................................... 221
5.8 Requiring a reset before outputs can become energized ............................................. 223
5.9 Configuring the Logic Solver's response to detected faults .......................................... 223
5.9.1 Detecting faults on input channels .................................................................. 224
5.9.2 Detecting faults on output channels ................................................................ 227
5.10 Choosing the Logic Solver scan rate ........................................................................... 228
5.11 Loading to a running process ...................................................................................... 228
5.12 Restarting a Logic Solver after a power failure ............................................................ 229
5.13 System Administration functions ................................................................................. 229
5.13.1 Backing up the database ................................................................................ 229
5.13.2 Making configuration changes after startup..................................................... 229
5.13.3 Reconciling parameter changes ..................................................................... 229
5.14 Proof Testing the Logic Solver .................................................................................... 230
5.14.1 Automatic proof testing ................................................................................... 231
5.14.2 Manual proof testing ....................................................................................... 231
5.15 Customizing Ovation Control Builder frame ................................................................. 232
5.16 Upgrading SIS firmware .............................................................................................. 232
5.16.1 To initially load or upgrade an SIS Data Server............................................... 233
5.16.2 To upgrade an SIS Logic Solver ..................................................................... 234
5.16.3 To upgrade an SIS Net Repeater ................................................................... 235
5.17 Using Fault Codes for SIS........................................................................................... 236
5.18 SIS Node Point (RN Point) .......................................................................................... 239
5.19 SIS Events.................................................................................................................. 242
5.19.1 To configure SIS Loggers ............................................................................... 243
5.19.2 Viewing Historical SIS Events......................................................................... 247
5.19.3 SIS Events Types........................................................................................... 248
Index 257
iv OW351_47
S E C T I O N 1
1 Introduction to Ovation Safety Instrumented System

(SIS)
IN THIS SECTION
What is a Safety Instrumented System? ..........................................................................1

Functions of Ovation SIS .................................................................................................2
Safety Instrumented System terminology .........................................................................2
1.1 What is a S afety Instrumented Sy stem?
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.
OW351_47 1
1.2 Functions of Ovation SIS
1.2 Functions of Ov ation 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.
1.3 Safety Instrumented Sy stem t erminology

TE RM D E S C RIP T IO N
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
Controller (CIS) SIS process data 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. 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.
2 OW351_47
1.3 Safety Instrumented System terminology
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
(Local peer bus) to one SIS Data Server. Achieved via carrier backplanes and
coaxial extender cables.
LOPA Layers of Protection Analysis. Requirements for SIS projects.
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
(Remote peer bus) Data Servers. Achieved via SISNet Repeaters and a fiber optic
loop
Shadow algorithm Term used to describe 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 Safety Instrumented Function (see page 6).
SIL Safety Integrity Level (see page 6).
SIS Force Force operation (see page 205) occurs when a value and quality
for an algorithm input parameter (pin) is manually changed,
typically for testing purposes.
SIS hardware Refer to Hardware components (see page 41).
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.
OW351_47 3
1.3 Safety Instrumented System terminology
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
(SDS) Controller, Logic 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
1508) capability and provide an interface to a maximum of 16 user
configurable I/O channels.
4 OW351_47
S E C T I O N 2
2 Planning the Safety Instrumented System
IN THIS SECTION
SIS aspects to consider...................................................................................................5

Capacities for Ovation SIS system...................................................................................6
SIS environmental specifications for Ovation SIS devices ................................................7
Supported SIS network ...................................................................................................8
Planning the hardware installation .................................................................................39
2.1 SIS aspect s to con sider

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 6)) 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.
OW351_47 5
2.1 SIS aspects to consider
 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
2.1.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 6)) assigned to it.
2.1.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
6 OW351_47
2.2 Capacities for Ovation SIS system
2.2 Capacities for Ov ation SIS sy ste m
Capacities for Ovation SIS system
C O M P O NE NT M AX IM UM L IM IT
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
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
2.3 SIS env ironmental sp ecific ations for Ov ation SIS dev ic es
The following table provides the environmental specification for normal operation of Ovation SIS
devices.
SIS environmental specifications
S P E C I F I C AT I O N D E S C RIP T IO N
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
OW351_47 7
2.4 Supported SIS network
Electromagnetic compatibility Per EN61326-1, Criteria A and Namur NE21
2.4 Supported SIS net work
Ovation 3.5.1 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 8).
 SIS Network with three (3) SIS Switches (see page 17).
 SIS Network with two (2) SIS Switches (see page 23).
 SIS Network with one (1) SIS Switches (see page 27).
2.4.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.
8 OW351_47
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.
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
P O RT U S AG E
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
OW351_47 9
P O RT U S AG E

Fa3/7 Not used
Fa3/8 Not used
Second switch (switch number 1_B) in ring network
P O RT U S AG E
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
10 OW351_47
Third switch (switch number 2) in ring network
P O RT U S AG E

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
Fourth switch (switch number 2_B) in ring network
P O RT U S AG E

OW351_47 11
P O RT U S AG E

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
Fifth switch (switch number 3) in ring network
P O RT U S AG E

Fa1/5 Pri of SDS 17
Fa1/7 Pri of SDS 18
Fa2/1 Pri of SDS 19
12 OW351_47
P O RT U S AG E

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
Sixth switch (switch number 3_B) in ring network
P O RT U S AG E

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
OW351_47 13
P O RT U S AG E

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
Seventh switch (switch number 4) in ring network
P O RT U S AG E

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
14 OW351_47
P O RT U S AG E
Fa3/6 Not used

Fa3/7 Not used
Fa3/8 Not used
Eighth switch (switch number 4_ B) in ring network
P O RT U S AG E

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
OW351_47 15
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 1: SIS Network with Four (4) SIS Switches
16 OW351_47
2.4.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 8).
First switch (switch number 1) in ring network
P O RT U S AG E

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
OW351_47 17
P O RT U S AG E

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
P O RT U S AG E

18 OW351_47
P O RT U S AG E

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
P O RT U S AG E

Fa1/5 Sec of SDS 09
Fa1/7 Sec of SDS 10
Fa2/1 Sec of SDS 11
OW351_47 19
P O RT U S AG E

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
Fifth switch (switch number 3) in ring network
P O RT U S AG E

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
20 OW351_47
P O RT U S AG E

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
Sixth switch (switch number 3_B) in ring network
P O RT U S AG E

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
OW351_47 21
P O RT U S AG E
Fa3/6 Not used

Fa3/7 Not used
Fa3/8 Not used
Figure 2: SIS Network with three (3) SIS Switches
22 OW351_47
2.4.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 8).
P O RT U S AG E

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
OW351_47 23
P O RT U S AG E

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
P O RT U S AG E

24 OW351_47
P O RT U S AG E

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
P O RT U S AG E

Fa1/5 Sec of SDS 09
Fa1/7 Sec of SDS 10
Fa2/1 Sec of SDS 11
OW351_47 25
P O RT U S AG E

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
26 OW351_47
Figure 3: SIS Network with two (2) SIS Switches
2.4.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 8).
P O RT U S AG E

Fa1/2 Not used
OW351_47 27
P O RT U S AG E
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
P O RT U S AG E

Fa1/2 Not used
Fa1/7 Sec of SDS 01
28 OW351_47
P O RT U S AG E
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
OW351_47 29
Figure 4: SIS Network with one (1) SIS Switches
2.4.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.
30 OW351_47
 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 6, 8-wide carrier limit in this arrangement.
OW351_47 31
Figure 5: Horizontal installation with cabinet width of 800mm
32 OW351_47
Example 2:
Horizontal Installation
 Cabinet Width 1200mm.

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

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

 KJ4003X1-BH2-PW (Local Bus, D25M-D25 17").
OW351_47 37
Figure 8: Vertical installation with cabinet width of 1200mm
38 OW351_47
2.5 Planning the hardware installation
2.5 Plan ning the h ardware instal lation

The following list provides an overview of the basic SIS hardware installation. Refer to the specific
sections for installation details.
1. Install appropriate carriers (see page 43) on the DIN rails in a hardware cabinet.
2. Install terminal blocks (see page 54) onto a carrier.
3. Install the SIS Data Servers (see page 57) onto a carrier.
4. Install Logic Solvers (see page 64) onto the terminal block.
5. Connect the field wiring.
6. Install the SISNet Repeaters (see page 73).
7. Install extender cables (see page 55).
8. Terminate the local bus.
9. Provide power to (see page 77):
 SIS Data Servers
 SIS Logic Solvers.
 SISNet Repeaters.
 SISNet Extenders.
10. If desired, install auxiliary equipment (see page 82).
2.5.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).
OW351_47 39
S E C T I O N 3
3 Hardware for Ovation SIS
IN THIS SECTION
Hardware components of Ovation SIS ...........................................................................41

SIS Carriers ..................................................................................................................43
SLS Simplex and Redundant terminal blocks ................................................................53
Carrier extender cables .................................................................................................54
SIS Interface Controller (SIS DROP) .............................................................................56
SIS Data Server ............................................................................................................56
SIS Logic Solver............................................................................................................61
SISNet Repeater ...........................................................................................................72
Fiber-optic cable\ring.....................................................................................................77
Power Supply ................................................................................................................77
SIS Network Switches and Routers ...............................................................................82
Ovation SIS accessories ...............................................................................................82
3.1 Hard ware c ompon ents of Ov ation 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
H ARD W A RE C O M P O NE NT D E S C RIP T IO N
SIS Carriers (see page 43) Vertical or horizontal brackets that mount on the DIN rails in a
cabinet and hold the Logic Solvers and terminal blocks.
Simplex terminal block (see Interfaces between I/O devices and one Logic Solver that acts in a
page 53) simplex configuration.
Redundant terminal block Interfaces between I/O devices and two Logic Solvers that act in a
(see page 53) redundant configuration.
SIS Interface Controller Provides interface between Ovation and SIS Data Server.
(see page 56)
SIS Data Server (see page Provides the interface between the SIS Interface Controller and
56) Logic Solvers and SISNet Repeaters. The SIS Data Server can
manage up to 32 simplex or 16 redundant Logic Solvers.
SIS Logic Solvers (see Hardware modules that contain logic solving capability and
page 61) provide an interface to a maximum of 16 user configurable I/O
channels.
SISNet Repeaters (see Provides secure communication between Logic Solvers that are
page 72) connected to different SIS Data Servers.
OW351_47 41
3.1 Hardware components of Ovation SIS
H ARD W A RE C O M P O NE NT D E S C RIP T IO N
Fiber optic cable/ring (see SISNet Repeaters connected to an SIS Data Server communicate
page 77) with another SISNet Repeater connected to a different SIS Data
Server.
Carrier Extender cables Connects power and signals between 8-wide carriers.
(see page 54)
SISNet Distance Extender Permits SISNet Repeaters to communicate over greater
(see page 74) distances.
Power Supply (see page Provides power to the SIS Data Server.
77)
The following graphic illustrates the SIS hardware components in a typical system.
Figure 9: SIS Hardware components
42 OW351_47
3.2 SIS Carriers
3.2 SIS Carriers

SIS carriers are brackets that are used to secure the SIS modules in a cabinet. The SIS carriers
mount on standard 35 mm (1.38 in.) T- or G-type DIN rails in the hardware cabinets.
There are two types of SIS carriers:

 Horizontal carriers (see page 43)
 Vertical carriers (see page 44)
Note: The LocalBus, including all cabling, cannot be longer than 6.5 m (21.3 ft).
3.2.1 Horizontal Carriers
There are three types of Horizontal Carriers:
 1-wide carrier (dual-left/right cable extender).

 2-wide carriers (SIS Data Server, SISNet Repeater).
 8-wide carriers (I/O) (can hold up to four simplex/two redundant Logic Solvers).
Figure 10: Terminal blocks installed on an 8-wide carrier
Horizontal Carrier parts
C AR RIE R P A RT # D E S C RIP T IO N
KJ4001X1-NA1-PW 1-Wide Horizontal Dual Right Cable Extender

KJ4001X1-NB1-PW 1-Wide Horizontal Dual Left Cable Extender
KJ2221X1-EA1-PW 2-Wide Horizontal - holds SISNet Repeaters
KJ4001X1-BA3-PW 2-Wide Horizontal - SIS Data Server w/ Redundancy
KJ4001X1-BE1-PW 8-Wide Horizontal Backplane for mounting Logic Solvers and terminal blocks
OW351_47 43
3.2 SIS Carriers
3.2.2 Vertical Carriers
Vertical carriers mount on standard 35 mm (1.38 in.) T- or G-type DIN rails.

 Vertical carriers
 1-wide carrier (right cable extender Vertical).
 1-wide carrier (left cable extender Vertical).
 4-wide Vertical (Power/SIS Data Server).
 4-wide Vertical (SISNet Repeater).
 8-wide Vertical (I/O, left/right side) (can hold up to four simplex/two redundant Logic
Solvers).
Note: The LocalBus, including all cabling, cannot be longer than 6.5 m (21.3 ft).
The vertical carriers are mounted properly when the lettering is in the upright position.
There are six types of carriers for mounting vertically in a cabinet:

 Two types of 1-wide (right/left) extenders.
 Two types of 4-wide carriers for power/SDS and SISNet Repeaters.
 Two types of 8-wide I/O interface carriers (8-wide carrier can hold up to four simplex/two
redundant Logic Solvers).
44 OW351_47
3.2 SIS Carriers
There are two separate cable lengths for connecting the 8-wide I/O interface carriers (8-wide
carrier can hold up to four simplex/two redundant Logic Solvers):
 1 meter bottom cable extender.
 2 meter top cable extender.
Figure 11: Cabinet with vertical SIS configuration
Vertical carrier parts
KJ4003X1-BC1-PW 4-Wide Vertical Power/SDS

KJ4003X1-BD1-PW 4-Wide Vertical SISNet Repeater
OW351_47 45
3.2 SIS Carriers
KJ4003X1-BA1-PW 8-Wide Vertical - I/O SIS Compatible, Left Side (Can hold up to four simplex
and two redundant Logic Solvers)
KJ4003X1-BB1-PW 8-Wide Vertical - I/O SIS Compatible, Right Side (Can hold up to four simplex
and two redundant Logic Solvers)
KJ4003X1-BE1-PW Extender, Right 1-Wide Vertical
KJ4003X1-BF1-PW Extender, Left 1 -Wide Vertical
The following figure illustrates suggested spacing for vertical DIN rail installation.
Figure 12: Vertical DIN rail installation
46 OW351_47
3.2 SIS Carriers
3.2.3 To install the 1-wide Horizontal carrier (dual left-right extender cables)
The 1-wide carrier is used to extend the local peer bus through the use of extender cables (see
page 55) or to terminate the Local peer bus.
See To install carrier extender cables (see page 55) for directions on using 1-wide carriers as
extenders.
Note: The local peer bus is terminated by 120 ohms BNC terminators on the right one-wide
carrier connected to the last 8-wide carrier.
Figure 13: Dual Left-Right Extender
3.2.4 To use 1-wide carrier as a terminator

1. Install a right, one-wide carrier at the end of the last carrier on the DIN rail.
2. Place a 120 ohms BNC terminator (KJ4010X1-BN1) onto each BNC connector on the carrier
and push and turn to lock the terminator into place.
OW351_47 47
3.2 SIS Carriers
3. Terminate both connectors.
Figure 14: One-wide SIS carrier
3.2.5 To use the 2-wide Horizontal power/SIS Data Server carriers

1. Use the 2-wide power/SDS carrier to install one power supply and one SIS Data Server.
2. Install the 2-wide power/controller carrier on the DIN rails in the cabinet.
3. Install an SIS Data Server and power supply on the 2-wide power/SIS Data Server carrier.
4. Use another 2-wide power/SDS carrier to install redundant power supply and SIS Data
Server.
48 OW351_47
3.2 SIS Carriers
Note: Make sure that you are using the 2-wide power/SIS Data Server carrier numbered
KJ4001X1- BA3-PW or higher for any SIS installation.
5. Install the 2-wide SISNet Repeater carriers on the DIN rails if remote communication is
required. (SISNet Repeater carriers can be installed anywhere between the 2-wide
power/SDS carrier and the terminated one-wide carrier.)
6. Connect the carriers to any adjacent carriers by sliding together the 48 pin connectors on the
sides of the carriers.
7. If you are installing carriers on separate DIN rails, you will need to connect two (left and right)
one-wide carriers and then connect cables to extend the LocalBus and Local Peer Bus.
Figure 15: Two-wide SIS carrier
OW351_47 49
3.2 SIS Carriers
3.2.6 To install the Vertical Controller (4-wide Power/SIS Data Server) carrier
Use the 4-wide power/SIS Data Server carrier to install two power supplies and two redundant
SIS Data Servers.
The 4-wide power/SIS Data Server carriers supply power and communications connections for
vertically mounted SIS Data Servers.
 Top 4-wide power/controller carriers connect to the left 8-wide I/O interface carrier. The 96 pin
connector is at the bottom of this carrier. (The left 8-wide I/O interface carrier holds cards 1-8
from top to bottom.)
Figure 16: Vertical Controller SIS carrier
50 OW351_47
3.2 SIS Carriers
3.2.7 To install the 8-wide Horizontal I/O interface carrier (can hold up to four
simplex/two redundant Logic Solvers)
Use the 8-wide carrier to install eight I/O cards with terminal blocks.
The power and cable specifications are:

 Local Bus that powers I/O cards uses 8.0 A.
(For large systems, use the LocalBus extenders to add more power.)
 Bussed field power bus that is shared by multiple I/O card pairs uses 6.5 A for each
connection.
 Local Bus cable =1 .2 m (3.9 ft) long.
1. Install the 8-wide I/O interface carrier on the DIN rail in the cabinet next to the 2-wide carrier.
2. Install Logic Solver terminal blocks on the 8-wide carrier.
Figure 17: Eight-wide SIS carrier
OW351_47 51
3.2 SIS Carriers
3.2.8 To install the Vertical (8-wide left/right side) carrier (can hold up to four
simplex/two redundant Logic Solvers)
Use the 8-wide Vertical carrier to install up to four Logic Solvers with terminal blocks.
There are two types of 8-wide interface carriers:

 Left 8-wide interface carrier (card positions 1-8 from top to bottom).
 Right 8-wide interface carrier (card positions 8-1 from top to bottom).
The extender cable specifications are:
 Bottom cable extender = 1.0 m (3.3 ft) nominal length.
 Top cable extender = 2.0 m (6.6 ft) nominal length.
 Local Bus cable = 1.2 m (3.9 ft) long.
1. Mount the DIN rail at the appropriate location.
2. Connect each 8-wide carrier to any adjacent carriers by sliding the 96-pin connectors at the
top or bottom of the carriers together. Hold the carrier in position to ensure that it does not fall.
3. Turn the screws counter-clockwise to disengage the latch. With the carrier on the rail, tighten
the screws clockwise to latch.
Note: The middle two screws are for G-rail mounting and the outer screws are for T-rail
mounting.
4. If you are mounting 8-wide carriers on separate rails, use the bottom cable extender for a left-
to-right bridge and the top cable extender for a right-to-left bridge.
52 OW351_47
3.3 SLS Simplex and Redundant terminal blocks
5. Install ground wiring. For a good connection, use a signal ground cable and a block spade
terminal, sized for AC/DC system power.
Figure 18: Installing 8-wide SIS carrier
3.3 SLS Simplex and Red undant ter minal blo cks
Terminal blocks connect the wires from the devices in the plant to the SIS Logic Solvers. The
terminal blocks are mounted on the SIS 8-wide I/O carriers in the Ovation cabinets. SIS terminal
blocks are yellow.
The Carrier can hold four Simplex or two Redundant Terminal blocks. The Simplex Terminal
Block takes up two slots and can be mounted in slots starting with 1, 3, 5, or 7.
The Redundant Terminal Block takes four slots and can be mounted in slots starting with 1, 5, or
9.
Terminal block part numbers
TE RM INAL B L O C K P A RT D E S C RIP T IO N
N UM B E R
KJ2201X1-HA1-PW Connects to SIS Logic Solver (Simplex).

KJ2201X1-JA1-PW Connects to Redundant SIS Logic Solver (Redundant).
OW351_47 53
3.4 Carrier extender cables
3.3.1 To install Terminal Blocks

1. Install an 8-wide I/O carrier onto a DIN rail.
2. Locate an odd slot number on the I/O interface carrier. Simplex terminal blocks occupy two
slots starting with 1, 3, 5, or 7 and redundant terminal blocks occupy four slots starting with 1,
5, or 9. This slot numbering is used as an example and does not hold true if combination of
Simplex and redundant terminal blocks is used.
3. Insert the tabs on the back of the terminal block through the slots on the carrier and push the
terminal block up to lock it into place. The following figure shows a redundant terminal block
installed on an I/O interface carrier.
4. Connect the field wiring.
The following figure illustrates the installation of an SIS terminal block on a horizontal 8-wide
carrier:
Figure 19: Terminal blocks installed on an 8-wide carrier
3.4 Carrier extender c ables
Carrier extender cables extend power and signals between 8-wide carriers (can hold up to four
simplex/two redundant Logic Solvers). Local peer bus extender cables extend the local peer bus
between Logic Solvers on different carriers. One-wide carriers with terminators terminate the local
peer bus at the final carrier.
When carriers are installed on separate DIN rails, carrier extender cables and local peer bus
extender cables are used to extend the LocalBus and local peer bus. Extender cables connect to
one-wide carriers on the left and right sides of the 8-wide carriers.
54 OW351_47
3.4 Carrier extender cables
3.4.1 Carrier extender cable part numbers
Carrier extender cables extend power and signals between 8-wide carriers.
Carrier extender cable part numbers
C AB L E E XT E ND E R P A RT NUM B E RS D E S C RIP T IO N
(HO RIZO NT AL )
KJ4002X1-BF2-PW Carrier extender cable, bottom, 44 inches

KJ4002X1-BE1-PW Carrier extender cable, top, 77 inches
C AB L E E XT E ND E R P A RT NUM B E RS D E S C RIP T IO N
(V E RT IC AL )
KJ4003X1-BH1-PW Carrier extender cable, 43 inches

KJ4003X1-BH2-PW Carrier extender cable, 17 inches
C AB L E E XT E ND E R P A RT NUM B E RS (BNC) D E S C RIP T IO N
KJ4010X1-BL1-PW Cable Assembly, SISNet, Coax, Black, 46 inches

KJ4010X1-BM1-PW Cable Assembly, SISNet, Coax, White, 46 inches
3.4.2 To install carrier extender cables
A standard installation uses one carrier extender cable; however, dual carrier extender cables can
also be used. The following procedure is for a standard installation that uses one carrier extender
cable.
1. Install the right and left-side one-wide carriers by sliding together the 48-pin connectors on the
sides of the carriers.
2. Connect the 44-pin D-shell (male) connector on the carrier extender cable to the top D-shell
connector labeled A on the right-side carrier and fasten the retainer screws.
3. Connect the 44-pin D-shell connector on the other end of the cable to the top D-shell
connector labeled A on the left-side carrier and fasten the retainer screws.
4. Repeat Steps 2 and 3 for dual connection.
5. Notice that the local peer bus extender cable has black and white boots. The cables connect
black-to-black (D) and white-to-white (C).
OW351_47 55
3.5 SIS Interface Controller (SIS DROP)
6. Place the cable end onto the BNC connector on the carrier and push and turn to lock the
cable into place.
Figure 20: Carrier extender cables
3.5 SIS Interface Controller (SIS DROP)
The Ovation Controller (OCR400/OCR1100) is used as an interface between Ovation Database,

SIS Data Server, and Logic Solver. In an SIS System, there can be eight (8) simplex or redundant
OCR400/OCR1100 Controllers dedicated to SIS. The N1 and N4 interface connections are used
to connect to SIS network whereas the N2 and N3 interface connections are used for the Ovation
network. For more information on OCR400/OCR1100, refer to the applicable Controller (OCR400)
User Guide / Controller (OCR1100) User Guide.
3.6 SIS Data S erv er
An SIS Data Server provides the interface between the Ovation Controller and Logic Solvers and
SISNet Repeaters.
3.6.1 SIS Data Server part number
Data server part number
D AT A S E RV E R P A RT N UM B E R D E S C RIP T IO N
KJ2003X1-PW1 Ovation SIS Data Server
56 OW351_47
3.6 SIS Data Server
3.6.2 To install an SIS Data Server

1. Install a 2-wide power/SIS Data Server carrier onto a DIN rail.
2. Align the connectors on the back of the SIS Data Server with the connectors on the right slot
of the 2-wide power/SIS Data Server carrier and push to attach.
3. Tighten the mounting screw.
4. Repeat Steps 1 and 2 if the system is redundant.
Figure 21: Installed SIS Data Server
3.6.3 To power up a simplex SIS Data Server
Prerequisites:
 Install (see page 57) the SIS Data Server into a 2-wide carrier.
 Make sure that the system power supply is connected to the SIS Data Server and the power
is off.
 Make sure that the Ovation network is set up in such a way that the SIS Data Server is able to
communicate (once it is powered up) with a DHCP server.
Procedure
1. Power up the SIS Data Server power supply.
2. Refer to the flashing LEDs (see page 59) on the SIS Data Server:
OW351_47 57
3.6 SIS Data Server
 The SIS Data Server attempts to contact the DHCP server and obtain its runtime
configuration. Until the DHCP transaction is complete, the SIS Data Server continues to
flash its LEDs.
 The SIS Data Server initializes in the ACTIVE mode. The ACTIVE LED switches to the
constant ON state. The Pri CN and Sec CN LEDs flash to indicate network activity.
Note: If the DHCP server does not contain a valid configuration for the SIS Data Server, the SIS
Data Server remains in the ‘obtaining runtime configuration’ state until a valid configuration can
be provided by the DHCP server.
3.6.4 To power up an additional SIS Data Server from a redundant pair
Prerequisites:
 Install (see page 57) the SIS Data Server into a 2-wide carrier.
 Make sure that the system power supply is connected to the SIS Data Servers and the power
is off.
 Make sure that the Ovation network is set up in such a way that the SIS Data Servers are
able to communicate (once it is powered up) with a DHCP server.
 Make sure that the SIS Data Server's redundant partner is running.
Procedure
1. Power up the SIS Data Server's power supply.
 The SIS Data Servers attempt to contact the DHCP server and obtain its runtime
configuration. Until the DHCP transaction is complete, the SIS Data Servers continue to
flash its LEDs.
 The SIS Data Server communicates with its partner over the redundancy link. It detects
the ACTIVE state of the two SDSs. The ACTIVE LED switches to the constant ON state.
The partner SDS initializes in the STANDBY state. The STANDBY LED switches to the
constant ON state. The Pri CN and Sec CN LEDs flash to indicate network activity.
 Note that if the redundancy configuration obtained from the DHCP server by the two SIS
Data Servers does not match, the two SIS Data Servers cannot communicate over the
redundancy link. The SIS Data Server reboots while the redundant partner continues to
operate in the ACTIVE mode. This cycle will repeat itself until the redundancy
configuration is the same for both SIS Data Servers.
3.6.5 To remove an Active SIS Data Server from a redundant pair
Prerequisites:
1. Make sure both SIS Data Servers in a redundant pair are running and both have active
connections to the Ovation network.
Procedure
1. Remove the ACTIVE redundant SIS Data Server from its slot on the carrier.
 The partner SIS Data Server in the redundant pair detects the failure of its partner and
switches to ACTIVE mode.
58 OW351_47
3.6 SIS Data Server
 The STANDBY LED switches to the constant OFF state. The ACTIVE LED switches to
the constant ON state. The Pri CN and Sec CN LEDs flash as per network activity. The
Pri CN and Sec CN LEDs flash to indicate network activity.
Note: If the standby SIS Data Server is removed from its slot on the carrier, the active partner
remains unaffected and continues to run in the ACTIVE state.
3.6.6 SIS Data Server LEDs
LED L E D S T AT U S D A T A S E R V E R S T AT U S
Power (Green) On Power is supplied to the unit.

Off System power is not supplied to unit (possible
line power problem or Internal fault).
Error (Red) On (solid/continuous) Internal fault.
Off No Fault.
On for one second followed Unit went through RESET due to an
by all LEDs on for five unrecoverable software error.
seconds
Flashing SIS Data Server is cleared.
Active (Green) On SIS Data Server is Active.
Off SIS Data Server is on Standby.
SIS Data Server is cleared.
(Internal Fault)
Standby On SIS Data Server is on Standby.
(Green)
Off SIS Data Server is Active.
Flashing SIS Data Server is not configured.
Primary CN Flashing Communication is active for Primary Physical
(Orange) Interface.
Off Communication is not active for Primary
Physical Interface.
Secondary CN Flashing Communication is active for Secondary
(Orange) Physical Interface.
Off Communication is not active for Secondary
Physical Interface.
When you install an Ovation SIS Data Server, the LEDs flash a pattern that reveals the state of
the SIS Data Server.
OW351_47 59
3.6 SIS Data Server
Initialization state
When you install (see page 57) an SIS Data Server in an Ovation carrier, the LEDs perform the
following sequence, with one second between each phase, until the SIS Data Server is fully
activated:
Initialization phases
LED P HAS E 1 P HAS E 2 P HAS E 3 P HAS E 4 P HAS E 5
Power ON ON ON ON ON
Error OFF OFF OFF OFF OFF
Active OFF ON ON ON ON
Standby OFF OFF ON ON ON
Pri CN OFF OFF OFF ON ON
Sec CN OFF OFF OFF OFF ON
Minimal Firmware load
After the SIS Data Server has been initialized, the LEDs perform the following sequence to
indicate that the basic SIS firmware is loaded on the SIS Data Server:
LED states
LED ST AT E
Power Constant ON
Error Constant OFF
Active If this is the active SIS Data Server, constant ON.
If this is not the active SIS Data Server, constant OFF.
Standby If this is the standby SIS Data Server, constant ON.
If this is not the standby SIS Data Server, constant OFF.
Pri CN Dependent on network activity.
Sec CN Dependent on network activity.
Upgraded Firmware load
After the SIS Data Server has been upgraded, the LEDs perform the following sequence only
once to indicate that upgraded SIS firmware is now loaded on the SIS Data Server:
LED states
LED ST AT E
Power Constant ON
Error Constant OFF
Active Blinks every two seconds.
Standby Blinks every 0.5 seconds.
60 OW351_47
3.7 SIS Logic Solver
LED ST AT E
Pri CN Dependent on network activity.

Sec CN Dependent on network activity.
3.6.7 SIS Data Server specifications
SIS Data Server specifications
Power requirement (supplied by system power +5 VDC at 1.4 A maximum

supply through 2-wide power/controller carrier)
Fuse protection 3.0 A, non-replaceable fuses
Power dissipation 5.0 W typical
7.0 W maximum
Mounting On right slot of the power/Controller carrier
Dimensions Height 159.6 mm (6.3 in.)
Width 41.8 mm (1.6 in.)
Depth 107.0 mm (4.2 in.)
3.7 SIS Logic Solv er
Logic Solvers are hardware modules that contain logic solving capability. There are simplex and
redundant Logic Solvers.
Each Logic Solver can provide an interface to a maximum of 16 user configurable I/O channels.
The following table lists the available types of SIS I/O.
Types of SIS I/O
I/O TYPE D E S C RIP T IO N FU NC T IO NAL IT Y
Analog input Reports the analog value present at Used with LSAI algorithms as
the channel. input references.
HART analog Reports the analog value present at Used with LSAI algorithms as
input the channel and up to four digital input I/O references. Used with
values from a HART field device. LSAI algorithms as read back
references to read a 4 to 20 mA
signal.
HART two- Drives a digital valve controller Used with LSDVC algorithm to
state output output device. drive DVC6000ESD digital valve
 On value is 20 mA. controllers.
 Off value is configurable: either 0
mA or 4 mA (to allow for HART
communications).
OW351_47 61
I/O TYPE D E S C RIP T IO N FU NC T IO NAL IT Y
Digital Input Reports the digital value present at Used with LSDI algorithms as
the channel. input references when reading a
digital (On/Off) signal. Used with
LSDO algorithms as a read back
I/O reference for a digital signal.
Digital Output Drives the output to a digital value Used with LSDO algorithms as
and holds the output at that value. output references when driving a
Outputs immediately reflect the digital signal.
output value that was received.
Upon receiving a configuration that
indicates a change from one type of
output to another, the outputs
switch to the off state
62 OW351_47
3.7.1 Logic Solver 8-Slot carrier numbering scheme
Logic servers can be mounted on the 8-slot carriers. Each 8-slot carrier has slot numbers 1-8
painted on it. Up to eight 8-slot carriers can be daisy chained together for a total of 64 slots. In the
SIS system the 8-slot carriers will only handle Logic Solvers. Logic Solvers take up two slots for a
standard (simplex) module and four slots for a redundant Logic Solver.
When mounting a Logic Solver module in a carrier, the first slot must be an odd numbered slot 1,
3, 5, and 7 for Standard (simplex) and 1, 5, 9 and 13 for Redundant Logic Solvers. The electronic
slot numbering must be unique, so each slot is numbered according to its place in the daisy chain.
Since the even numbers are not counted, the First carrier has four slots. For the First carrier, Slot
1 = 1, Slot 3 = 2, Slot 5 = 3, and Slot 7 = 4. For carrier #8 1 = 29, 3 = 30, 5 = 31 and 7 = 32. The
slot layout for an 8 carrier setup looks like the following:
#1 1 - 3- 5 -7
1 - 2- 3- 4
#2 1 - 3- 5 -7
5 - 6- 7- 8
#3 1 - 3- 5 -7
9 - 10 - 11 - 12
#4 1 - 3- 5 -7
13 - 14 - 15 - 16
#5 1 - 3- 5 -7
17 - 18 - 19 - 20
#6 1 - 3- 5 -7
21 - 22 - 23 - 24
#7 1 - 3- 5 -7
25 - 26 - 27 - 28
#8 1 - 3- 5 -7
29 - 30 - 31 - 32
Placing a Logic solver module in a specific carrier slot, Slot #5 (painted number) in Carrier #4 for
instance, requires counting the number of slots starting from the first carrier to get the electronic
slot number.
Or use the chart above. For the example above, Carrier #4, Slot #5, using the chart above, the
electronic number for that slot is 15.
Or, the following formula will help figure out the electronic slot.
{[(Physical Carrier # - 1) X 8 + (Painted Slot # - 1)] / 2} +1
For the example above Carrier #4, Slot #5, using the formula above will also give the correct
electronic number..
OW351_47 63
{[(4 - 1) X 8 + (5 - 1)] / 2} +1 =
{[(3 X 8) + (4)] / 2} +1 =
{[24 + 4] / 2} +1 =
{28 / 2} +1 =
14 + 1 =
15
3.7.2 SIS Logic Solver part number
Logic Solvers are hardware modules that contain logic solving capability.
Logic Solver part numbers
LOGIC SOLVER P ART NUM B E R D E S C RIP T IO N
KJ2201X1-PW1 Ovation SIS Logic Solver
3.7.3 To install Logic Solvers
Logic Solvers are hardware modules that contain logic solving capability. These modules
communicate with each other through the SIS carriers.
1. Install an 8-wide I/O carrier (can hold up to four simplex/two redundant Logic Solvers) onto a
DIN rail.
2. Install a Logic Solver terminal block on the I/O interface carrier.
3. Install a Logic Solver on the terminal block.
4. Use odd numbered slots (1, 3, 5, and 7) on an 8-wide carrier.
5. Use two slots for Simplex Logic Solvers and four slots for redundant Logic Solvers (see page
65).
6. Align the connectors on the back of the Logic Solver with the connectors on the front of the
terminal block and push to attach.
64 OW351_47
Figure 22: Installation of Logic Solver
3.7.4 Logic Solver redundancy
A redundant Logic Solver configuration consists of a pair of Logic Solvers mounted in adjacent
carrier slots with a common terminal block. Each Logic Solver is powered separately. The
redundant Ovation SIS Logic Solver modules are connected to the field at the redundant terminal
block.
No control sheet configuration is required to take advantage of Logic Solver redundancy, as the
system automatically recognizes the redundant pair of cards. An integrity error alarm in a
redundant Logic Solver pair will notify the operator if a Logic Solver fails.
When an Ovation SIS System uses redundant Logic Solvers, this means that any two redundant
Logic Solvers run in parallel at all times. Both Logic Solvers read the inputs from the I/O terminals,
both execute the logic and both drive the outputs at the I/O terminals.
There is no concept of primary and backup or master and slave. The only difference between the
two is that the Active Logic Solver communicates with both the Ovation Developer Studio and the
Ovation Operator Station, and the dedicated safety network (SISNet). The Standby Logic Solver
is communicating only on the SISNet.
If a failure is detected in one of the Logic Solvers, it automatically goes to a failed state. In this
condition all its output channels are de-energized. This has no impact on the other Logic Solver or
the physical outputs because the other module continues to read inputs, execute logic, and drive
outputs. The transition from the active to the standby Logic Solver is therefore completely
bumpless.
OW351_47 65
3.7.5 SIS Logic Solver LED indicator patterns

S I S LO G IC S O L VE R LE D IND IC AT O R P AT T E RNS
P O WE R L E D E RRO R LE D A C T I V E L ED ST AND B Y LE D S L S S T AT U S
(GRE E N ) (RED) (Y E L L O W) (Y E L L O W)
On On On On Power-up tests in
Flashing in sync Flashing in sync Flashing in sync Flashing in sync progress
with Standby with Active with Error with Power
Alternating with Alternating with Alternating with Alternating with
Error and Active Power and Power and Error and Active
Standby Standby
On On On Off Non-Redundant
Solid Flashing in sync Flashing in sync Setup
with Active with Error Not initialized
On On On Off Redundant pair
Solid Flashing in sync Flashing in sync (Active)
with Active with Error Not initialized
On On Off On Redundant pair
Solid Flashing in sync Flashing in sync (Standby)
with Standby with Error Not initialized
On Off On Off Non-Redundant
Solid Flashing Setup
Initialized, not
configured
On Off On Off Redundant pair
Solid Flashing (Active)
Initialized, not
configured
On Off Off On Redundant pair
Solid Flashing (Standby)
Initialized, not
configured or
configuration in
progress
On Off On Off Non-Redundant
Solid Solid Setup
Configured
On Off On Off Redundant pair
Solid Solid (Active)
Configured
On Off Off On Redundant pair
Solid Solid (Standby)
Configured
On On On On Card is not fully
Solid Solid Flashing Flashing operational
(Contact technical
support)
On On Off Off Error detected during
Solid Solid power-up tests
(Contact technical
support)
66 OW351_47
3.7.6 Logic Solver specifications
Logic Solver specifications
Storage temperature -40 to 85 C (-40 to 185 deg. F)

Operating temperature -40 to 70 C (-40 to 158 deg. F)
Relative humidity 5 to 95%, non-condensing
Airborne contaminants ISA-S71.04-1985 Airborne Contaminants
class G3
Conformal coating
Protection rating IP 20, NEMA 12
Shock 10 g ½-sine wave for 11 ms
Vibration 1 mm peak-to-peak from 5 to 16 Hz; 0.5 g from 16 to 150 Hz
Input power 24 VDC +- 20%, 1.0 A plus field power (5.0 A total)
Note: it is recommended that the Logic Solver and SIS Data Server use
separate power supplies
Field power 4 A maximum (actual value depends upon channel type and field device type)
Isolation Each channel is optically isolated from the system and factory-tested to 1500
VDC. No channel-to channel isolation.
LocalBus current None
Mounting In SIS terminal blocks in odd-numbered slots (1,3,5,7) on the 8-wide carrier.
Simplex logic solvers take two slots and redundant Logic Solvers take four slots
Width 83.8 mm (3.3 in.)
Depth 110.0 mm (4.3 in.)
3.7.7 SIS I/O channels
A Logic Solver provides 16 channels of flexible I/O. This means that each channel can be used as
one of the following:
 Analog Input and HART Analog Input Channel Specifications and Wiring (see page 68).
 HART Two-state Output Channel Specifications and Wiring (see page 68).
 Digital Input Channel Specifications and Wiring (see page 69).
 Digital Output Channel Specifications and Wiring (see page 71).
Note: To configure an SIS I/O channel (see page 168) provides information on configuring the
SIS I/O channels.
OW351_47 67
Analog Input and HART Analog Input Channel Specifications and Wiring
Number of channels 16
Isolation Each channel is optically isolated from the system and factory
tested to 1500 VDC. No channel-to-channel isolation.
Nominal signal range (span) 4 to 20 mA
Full signal range 1 to 24 mA
Field circuit power per channel 24 mA
2-wire transmitter power 15.0 V minimum terminal to terminal @ 20 mA; current limited to 24
mA max.
Input Measurement Accuracy 0.1% of Span
Safety/diagnostic accuracy 2.0% of span
Resolution 16 bits, 2-pole filter, corner frequency 5.68 Hz
Filtering -3 db at 5.68 Hz
-20.0 db at 40 Hz (half the sample rate)
Figure 23: Wiring diagram and terminations for Analog Input and HART Analog Input
channels
HART Two-state Output Channel Specifications and Wiring
Isolation Each channel is optically isolated from the system and factory tested to
1500 VDC. No channel-to-channel isolation.
Nominal signal range On state - 20 mA
(span) Off state - 0 to 4 mA (configurable (see page 174))
68 OW351_47
Full signal range 0 to 24mA

Safety/diagnostic 5% of span
accuracy
Resolution 12 bits
Compliance voltage 20 mA into 600  load
Open-loop detection <1.0mA - when the output drifts 15% out of the configured value
Figure 24: Wiring diagram and terminations for HART Two-state output channels
Digital Input Channel Specifications and Wiring
Isolation Each channel is optically isolated from the system and factory tested to 1500
VDC. No channel-to-channel isolation.
Detection level for ON  2 mA
Detection level for < 1.65 mA
OFF
Input impedance ~ 1790 Inputs compatible with NAMUR sensors (12 V)
Input compatibility Dry contact with end of line resistance
<100  for guaranteed short circuit detection
1 >6 mA (simplex)
Line fault detection
Short circuit (optional) >11 mA (redundant)
Line fault detection >40 k for guaranteed open loop detection

Open circuit (optional) <0.35 mA
OW351_47 69
1
Digital Input channels have line fault detection for detecting open or short circuits in field wiring. To us e
this capability you must:
 Enable line fault detection in your configuration. Enable line fault detection on a channel -by-channel
basis when you configure the channels.
 Connect the dry contact to external resistors. Connect the dry contact to a 12 K resistor in parallel
(allows the open circuit detection) and a 2.4 Kresistor in series (allows short circuit detection).
Emerson's End of Line Resistance Module (KJ2231X1-EC1) provides this function. This module
connects to the Digital Input channel and to a field contact.
Line fault detection is built into NAMUR sensors (see page 2). Do not use external resistors with NAMUR
sensors; however, you must enable line fault detection in your configuration when using NAMUR sensors.
Figure 25: Wiring diagram and terminations for digital input channels (with line fault
detection options)
70 OW351_47
Figure 26: Wiring diagram and terminations for digital input channels (without line fault
detection options)
Digital Output Channel Specifications and Wiring
Isolation Each channel is optically isolated from the system and factory tested to
1500 VDC. No channel-to-channel isolation.
Output voltage Field power minus 2 V
Field power 0.5 A continuous per channel; 4.0 A max. per card
Output loading 56 to 3500 
Open loop test off. 4.5 A typical; 10 A max.
Off-state leakage Optional pulse test will apply 24 VDC pulse on line for 1.0 mS every 50
mS.
Short circuit Outputs current limited to 2.0 A typical
protection
Line fault detection

1 < 5  for > 1 second with +24 VDC field power.
Short circuit (optional) < 25 k for guaranteed open loop detection
Line fault detection < 3.5 k for guaranteed no open loop detection.
Open circuit (with +24
VDC field power)
OW351_47 71
3.8 SISNet Repeater
1
Digital Output channels have line fault detection for detecting open or short circuits in field wiring.
To use this capability you must:
 Enable line fault detection in your configuration. Enable line fault detection on a channel -by-
channel basis when you configure the channels.
 When driving inductive loads greater than or equal to 0.8 Henry in simplex or 0.3 Henry in
redundant, an RC compensator may be required. Size the RC compensator at 3.3 k and 0.47 f
for simplex and 2.7 k and 0.22 f for redundant as shown in the following figure. Emerson's RC
compensator module (KJ2231X1-ED1) provides this function. This module can be used for
simplex and for redundant applications.
Pulse testing is recommended; however, it can be disabled for field devices such as solid state
relays or active electronics that cannot support it. With redundant Logic Solvers, pulse testing
requires partner synchronization and stops if the redundant partner becomes unavailable.
Figure 27: Wiring diagram and terminations for digital output channels
3.8 SISNet Rep eater
SISNet Repeaters are hardware modules that provide communication beyond the local Logic
Solvers that are connected to one SIS Data Server.
The Repeaters broadcast global messages to remote Logic Solvers that are attached to another
SIS Data Server. This communication is done through the use of a fiber-optic network.
Global messages refer to messages that are intended for all Logic Solvers.
72 OW351_47
3.8 SISNet Repeater
3.8.1 SISNet Repeater part number
SISNet Repeater part number
S I SN E T R E P E A T E R P A RT NUM B E R D E S C RIP T IO N
KJ2221X1-PW1 Ovation SISNet Repeater
3.8.2 To install SISNet Repeaters for horizontal mounting

1. Install a 2-wide SISNet Repeater carrier onto a DIN rail.
2. Install the SISNet Repeater on the carrier. There is a primary and secondary SISNet
Repeater on each carrier.
3. Align the connector on the back of the SISNet Repeater with the connector on the 2-wide
SISNet Repeater carrier and push to attach.
Figure 28: Installed SISNet Repeater
OW351_47 73
3.8 SISNet Repeater
3.8.3 SISNet Distance Extender
SISNet Distance Extenders convert multimode fiber-optic signals to single mode fiber-optic
signals to allow SISNet Repeaters to communicate over greater distances. Depending upon the
installation, the remote peer ring can be extended by an additional 20 km when single mode fiber-
optic cable is used.
SISNet Distance Extender
N ET D IST ANC E E XT E ND E R P A RT D E S C RIP T IO N

N UM B E R
KJ2222X1-BA1-PW Ovation SISNet Distance Extender
3.8.4 SISNet Repeater LEDs
LED L E D S T AT U S S I S N E T R E P E A T E R S T AT U S
Power On Power is applied to Unit.

(Green)
Off Power is not applied to unit.
Error On Internal Fault.
(Red)
Off There is no Fault.
Flashing Maintenance Required.
Local Peer On Normal operation, SIS Net Repeater is receiving global data from
Tx other SISNet Repeaters and transmitting it to the local peer bus.
(Yellow)
Off Normal operation, there is no Logic Solver for the SISNet Repeater
to synchronize with on the local peer bus.
OR
The SIS Net Repeater local peer bus transmitter hardware has
detected a problem
Flashing (local The SISNet Repeater is not receiving its own transmissions while
peer Tx only) still receiving the transmissions of local Logic Solvers.
Flashing (both Local peer bus extender cables are disconnected; bus is not
local Tx and Rx) terminated or is terminated with wrong resistance.
Local Peer On Normal operation, SISNet Repeater is receiving transmissions from
Rx local Logic Solvers.
(Yellow)
Off Normal operation, there is no Logic Solver for the SISNet Repeater
to synchronize with on the local peer bus.
OR
SISNet Repeater local peer bus receiver hardware has detected an
error.
Flashing (both Local peer bus extender cables are disconnected; bus is not
local Tx and Rx) terminated or is terminated with wrong resistance; More than 5% of
received messages have errors.
Remote Peer On Normal operations, SISNet is transmitting local and remote global
Tx messages on the fiber-optic ring.
(Yellow)
Off Hardware error.
Flashing Break in fiber-optic ring.
74 OW351_47
3.8 SISNet Repeater
LED L E D S T AT U S S I S N E T R E P E A T E R S T AT U S
Remote Peer On Normal operation, the SISNet Repeater is receiving global data.
Rx
(Yellow) Off Hardware error.
Flashing Fiber-optic cable is disconnected, broken, or crossed; More than 5%
of received messages have errors.
3.8.5 SISNet Repeater specifications
SISNet Repeater specifications
Port type ST female

Cable type Multimode 62.5 /125 µm ST type or Multimode 50
/125 µm ST type
Output power < -12 dBm
Mounting Multimode 62.5/125 µm - attenuation 11 dB
maximum
Multimode 50/125 µm - attenuation 8 dB maximum
Wavelength 1300 nm
Link distance (nominal) 2 km one way TxD to RxD; actual length depends
upon the quality of the fiber-optic cable.
Topology Physical ring: RxD connects to TxD of predecessor
and TxD connects to RxD of successor.
SISNet Bridge port Used to make an Ethernet connection between
SISNet Repeaters in different SISNet Rings.
Mounting 2-wide SISNet Repeater carrier
Left carrier position is primary SISNet Repeater;
right carrier position is secondary SISNet Repeater.
Input power 24 VDC 300 mA maximum
Width 41.8 mm (1.6 in.)
Depth 110.0 mm (4.3 in.)
OW351_47 75
3.8 SISNet Repeater
3.8.6 SISNet Distance Extender specifications
SISNet Distance Extender specifications
Port type Multimode fiber port - Duplex SC

Single mode fiber port - Duplex LC
Cable types Multimode - 62.5/125 µm ST type or 50/125 µm ST type
Single mode - 9/125 µm, 8.8/125 µm, 8.5/125 µm, 8.2/125 µm
Output power Multimode - 14 dBm
Single mode - 0 dBm
Link budget Multimode:
62.5 /125 µm - attenuation 11 dB maximum
50/125 µm - attenuation 8 dB maximum
Wavelength 1300 nm
Single mode:
9/125 µm - attenuation 30.0 dB maximum
8.8/125 µm - attenuation 29.0 dB maximum
Wavelength 1310 nm
Link distance (nominal) Multimode - 2 km one way TxD to RxD
Single mode - 60 km one way TxD to RxD
Note: Actual length depends upon the quality of the fiber-

optic cable and the connections.
Topology Multimode (between SISNet Repeaters and SISNet Distance

Extenders): SISNet Repeater RxD to SISNet Distance
Extender TxD and SISNet Repeater TxD to SISNet Distance
Extender RxD.
Single mode (between SISNet Distance Extenders): RxD of
successor SISNet Distance Extender to TxD of predecessor
SISNet Distance Extender.
Mounting DIN rail
Input power 19.2 VDC to 28.8 VDC @ 250 mA maximum
Width 19.2 mm (0.75 in.)
Depth 113.5 mm (4.5 in.)
76 OW351_47
3.9 Fiber-optic cable\ring
3.9 Fiber -optic ca ble\ring

A fiber-optic cable/ring allows one SISNet Repeater (connected to an SIS Data Server) to
communicate with another SISNet Repeater (connected to a different SIS data Server).
A local SISNet Repeater collects locally generated global messages into a single message and
sends it to the next SISNet Repeater in the ring. Upon receipt of a message, the receiving SISNet
Repeater broadcasts it to its local peer bus and forwards the message to the next SISNet
Repeater in the ring.
A global message is forwarded around the ring once.
The primary SISNet Repeaters form one fiber-optic ring and the secondary form a separate,
independent ring.
SISNet Distance Extenders (see page 74) that convert multimode fiber-optic signals to single
mode fiber-optic signals can be used to extend the remote peer ring
3.10 Po wer Supply
Logic Solvers, SISNet Repeaters, and SISNet Distance Extenders are powered separately from
SIS Data Servers. This ensures that a loss of power to the SIS Data Server does not affect the
operation of Logic Solvers, SISNet Repeaters, and SISNet Distance Extenders. In most
installations, redundant 24 VDC power is used for both simplex and redundant SIS applications.
When redundant 24 VDC power is used, both power supplies must be referenced to a common
connection to ground
The SDS power supply takes line power or power from a bulk power supply and converts it to 12
VDC power to drive the SIS Data Server. The SDS power supply mounts on first slot of the 2-wide
power/SDS carrier. Power supply for Logic Solvers, SISNet Repeaters, and SISNet Distance
Extenders needs to be designed using the third party components (typically, Phoenix Contact)
and customized to match the project requirements (for example, total power consumption).
CAUTION! Although the screw terminal connector on the Logic Solver, SISNet Repeater, and
SISNet Distance Extender has two positive and two negative connectors, it is recommended
that they NOT be used to daisy-chain power. Daisy-chaining could result in a loss of power to
downstream Logic Solvers if power is removed or lost at an upstream Logic Solver.
3.10.1 Power supply part number
Power supply part number
P O WE R S UP P L Y P ART N UM B E R D E S C RIP T IO N
KJ1501X1-PW1 Ovation SIS power supply
OW351_47 77
3.10 Power Supply
3.10.2 Power supply specifications

P O WE R S U P P L Y S P E C I F I C AT I O N S
P O WE R S UP P L Y P AR AM ET E R V AL UE
Input power rating 24V DC, +/-20% (5.4A) OR 12V DC, -4%+5% (14.8A)
Output power rating -40 to 60 C 12V DC, 8.0A OR 12V DC, 13.0A
(-40 to 140 F)
Output power rating 70 C (158F) 12V DC, 6.0A OR 12V DC, 10.0A
Output power rating 5.1V DC, 2.0A

Output power rating 3.4V DC, 2.0A
Note: Combined output power of 10.2 Watts Maximum
5.1V DC and 3.4 VDC DC
Ambient temperature -40 to 70 C
Alarm relay contact rating 30V DC, 2A OR 250 AC, 2A
3.10.3 To install power supplies

1. Install a 2-wide or 4-wide power/SIS Data Server carrier onto a DIN rail.
2. Connect the input supply wires to the input power connection on the top of the system power
supply.
3. If the system has secondary power supplies, connect the input supply drops to each system
power supply.
WARNING! Always remove input power to the supply before connecting or disconnecting the
input power connection. The connector should not interrupt current flow and could be
damaged if actuated under a load condition.
4. Align the system power supply with the connector on the 2-wide or 4-wide power/SIS Data
Server carrier and push to attach.
3.10.4 To provide power to the Logic Solvers
Note: 24 V DC power to the Logic solvers must be provided by the independent feed cables
from the bus bar. Also, the daisy chaining must be avoided.
1. Locate the removable 24 VDC screw terminal connectors on the top of the Logic Solver.
78 OW351_47
3.10 Power Supply
2. Connect power supply positive (+) to the positive (+) connector on the Logic Solver and power
supply negative (-) to the negative (-) connector on the Logic Solver.
Figure 29: Providing power for Logic Solvers
3.10.5 To provide power to the SISNet Repeaters

1. Locate the removable 24 VDC screw terminal connectors on the top of the SISNet Repeater.
OW351_47 79
3.10 Power Supply
2. Connect power supply positive (+) to the positive (+) connector on the SISNet Repeater and
power supply negative (-) to the negative (-) connector on the SISNet Repeater.
Figure 30: Providing power for SISNet Repeaters
3.10.6 To provide power to SISNet Distance extenders

1. Locate the removable 24 VDC screw terminal connectors on the top of the SISNet Distance
Extender.
80 OW351_47
3.10 Power Supply
2. Connect power supply positive (+) to the positive (+) connector on the SISNet Distance
Extender and power supply negative (-) to the negative (-) connector on the SISNet Distance
Extender.
Figure 31: Providing Power for SISNet Distance Extender
OW351_47 81
3.11 SIS Network Switches and Routers
3.10.7 SIS Power Supply LEDs
SIS Power Supply LEDs
LED LED P O W E R S U P P L Y S T AT U S
ST AT US
Power On Power is supplied to the unit.

(Green)
Off System power is not supplied to unit (Possible line power problem) (Internal
Fault)
Error On Outputs are outside of tolerance. Inputs over voltage. Unit shuts down.
(Red)
Off No fault.
3.11 SIS Net work S witche s and Ro uters
For information on installing switches and routers in SIS system, refer to the manufacturer's
installation instructions.
3.12 Ov ation SIS ac ces sories

Typically, Ovation SIS equipment will connect to either 4-20 mA analog signal devices or digital
I/O devices rated at up to 500 mA per channel. Almost all the outputs will be "de-energize-to-trip."
However, there may be some output signals that require higher voltages or currents. Some
environments may require nonincendive outputs. Some devices may require "energize-to-trip"
functionality.
SIL3 applications that require higher voltage or current than the Logic Solver natively supplies
may employ the SIS Relay module. The Voltage Monitor may be used to verify the correct state of
the relay. For applications where the current to the final device needs to be limited for
nonincendive ratings, there is the current limiter module.
For other applications that simply need high current, Ovation offers the Auxiliary Relay Energize
to Actuate (ETA Direct) module. For applications where the current to the final device needs to be
switched on when the system trips, there is the Auxiliary Relay De-energize to Actuate (Inverting),
or DTA-Inverting relay. Either of these relay modules, when paired with the Auxiliary Relay Diode
module, allows Ovation SIS to meet higher-current digital output requirements while maintaining
its field wiring monitoring and ensuring that the relay changes states correctly.
The following auxiliary equipment can be used with SIS applications:

 SIS Relay module (see page 83)
 Voltage Monitor module (see page 88)
 SIS Current Limiter module (see page 92)
 Auxiliary Relay DTA Inverting module (see page 95)
 Auxiliary Relay ETA Direct module (see page 99)
 Auxiliary Relay Diode module (see page 100)
82 OW351_47
3.12 Ovation SIS accessories
3.12.1 SIS Relay module
The SIS Relay module is suitable for use in both high and low de-energize-to-trip safety critical
applications. This module can extend the voltage and current capability of the Ovation SIS Logic
Solver or any other safety PLC 24VDC digital output without compromising safety integrity. It is
capable of switching up to 2.5A at 250 VAC or 2.5A at 24 VDC for safety applications following
the de-energize-to-trip conventions by disconnecting field power when de-energized.
Two sets of output switches that are controlled by one common input are provided. The DC mode
of operation is configured to provide two independent sets of DC input power while the AC mode
of operation is configured to switch both sides of the AC input power.
The SIS Relay module contains three relays from different manufacturers. A relay coil is
energized for all three relays in normal operation. If a demand occurs, the Logic Solver removes
the power from the coil for all three relays at the same time. Each relay can be proof tested in the
field. Refer to the Proof Testing the SIS Relay for AC Wiring for AC input source and Proof
Testing the SIS Relay for DC Wiring for DC input source.
AC Field Wiring
Refer to the following figure for AC field wiring connections for the SIS Relay module:
Figure 32: SIS Relay AC Field Wiring Connection
OW351_47 83
 Two-pin digital input connection for input from a Logic Solver or generic safety PLC 24VDC
Digital Output channel.
 Two-pin connection for input from an AC power source.
 Two-pin connection for the switched AC output to an AC field device.
DC Field Wiring
Refer to the following figure for DC field wiring connections for the SIS Relay module:
Figure 33: SIS Relay DC Field Wiring Connection
84 OW351_47
 Two-pin digital input connection for input from a Logic Solver or generic safety PLC 24VDC
Digital Output channel.
 Four-pin connection for input from two DC power sources.
 Four-pin connection for the switched outputs to two DC field devices.
The SIS Relay module's LED shows the state of the relay coil if the digital input is correctly
connected to the Logic Solver output. The LED is illuminated when the relays are energized and
supplying power through the switched power outputs.
Refer to the following figures for the SIS Relay Terminal details and the SIS Relay Connection
details:
Figure 34: SIS Relay Terminal Details
OW351_47 85
Figure 35: SIS Relay Connection Details
The following table shows the specifications for the SIS Relay module:
SIS Relay Module Specifications
IT EM S P E C I F I C AT I O N S
Input for energized relay > 18VDC

Input for de-energized relay < 6VDC
Input current at 24 VDC < 70 mA ±- 20%
Relay current rating for AC operation 2.5A @ 250 VAC
Relay current rating for DC operation (when 2.5A @ 30 VDC

used in switched applications where transients
and current are limited)
Maximum AC Source 280 VAC
86 OW351_47
Maximum DC Source 30 VDC

Output series impedance (energized state) < 0.5 Ω
Output series impedance (de-energized state) > 1 MΩ
Maximum DC source 1 to source 2 potential 100 V
Input to Output isolation rating 300 VAC
Input to output delay (de-energize) 10 msec
Input to output delay (energize) 12 msec
Mounting configuration Horizontal DIN rail
Lifetime limitation on number of relay cycles >30,000 cycles or 20 years
The dimensions for the SIS Relay module are similar to the Voltage Monitor Module (see page
88).
OW351_47 87
3.12.2 Voltage Monitor module
The Voltage Monitor provides two independent sets of voltage monitoring circuitry in a single
device. Each circuit is suitable for use in both high and low de-energize-to-trip applications. As a
result, this helps to extend the voltage input monitoring capability of the Ovation SIS Logic Solver
or any other safety PLC digital input compatible with its specified output states. The Voltage
Monitor also supplies a secondary output for non-safety critical monitoring for each input. Refer to
Proof Testing the Voltage Monitor for information on proof testing the Voltage Monitor.
The state of both outputs for an associated input is controlled by the voltage level of the input with
the outputs going to the de-energized state when the input goes below a specified value.
The Voltage Monitor is designed to be used with the Ovation SIS Logic Solver to drive the Logic
Solver's Digital Input channel or an Ovation Digital Input channel (auxiliary) based on the output of
the SIS Relay module. Refer to the following figures:
Figure 36: Voltage Monitor Top View and Dimensions
88 OW351_47
Figure 37: Voltage Monitor Bottom View
OW351_47 89
 Two four-pin connection blocks, one for each voltage monitoring channel for connection to DC
or AC power source being monitored.
 Two four-pin connection blocks, one for each voltage monitoring channel for connecting the
output to a Logic Solver or other safety PLC monitored Digital Input (DI) channel and an
Ovation Digital Input channel (auxiliary).
Refer to the following figure for the Voltage Monitor Terminal details and the Voltage Monitor
Connection details:
Figure 38: Voltage Monitor Terminal Details
90 OW351_47
Figure 39: Voltage Monitor Connection Details
The following table shows the specifications for the Voltage Monitor module:
Voltage Monitor Specifications
Input for energized output >18 VDC or > 80 VAC

Input for de-energized output <3 VDC or <3 VAC
Maximum input voltage rating 250 VAC
Input current at 24 VDC < 6 mA ± 20%
Input current at 120 VAC <12mA
Input current at 230 VAC <15 mA
OW351_47 91
Output impedance (energized state) < 3.5 KΩ

Output impedance (de-energized state) >8.5 KΩ
Maximum output voltage rating 30 VDC
Input to output isolation rating 250 VAC
Safety output to auxiliary isolation rating 30 VAC
Channel-to-channel isolation rating 250 VAC
Input to output delay (de-energize) 30 msec
Input to output delay (energize) 5 msec
Mounting configuration Horizontal DIN rail
Lifetime limitations 30,000 cycles or 20 years
3.12.3 SIS Current Limiter module
The SIS Current Limiter module limits the current from the Logic Solver Digital Output channels to
levels below the ignition curves for Class 1 Division 2 and Zone 2 installations. Field wiring from
the Current Limiter output to the field can be removed and reconnected under power.
SIS Current Limiter module specifications
Input power (from Logic Solver Digital Output channels) 17 to 29 VDC; 22 VDC nominal
Output power 28.8 VDC (max)
Output current range 0-100 mA (max)
Output current limit threshold 100 mA (min); 120 mA (max)
Mounting Horizontal DIN rail
92 OW351_47
Refer to the following figures for illustrations of pin connections:

 Four pin connections for input from the Logic Solver Digital Output channels.
 Four pin connections for output to energy-limited loads.
Figure 40: SIS Current Limiter top view and dimensions
OW351_47 93
Figure 41: SIS Current Limiter bottom view and connections
94 OW351_47
3.12.4 Auxiliary Relay DTA-Inverting module
The Auxiliary Relay DTA-Inverting (De-Energize to Actuate) module is connected to a Logic

Solver's digital input and digital output channels and is then connected to a dual 24 VDC power
supply.
Two field terminals are then used to connect to the Auxiliary Relay Diode module (see page 100)
that is located next to the field actuator as shown in the following figure.
The Auxiliary Relay DTA-Inverting module energizes the field when Digital Output is turned Off.
The Auxiliary Relay DTA-Inverting module is paired with the Auxiliary Relay Diode module to
enable monitoring of the field wiring and the status of the relay. A switch on the Auxiliary Relay
Diode module is used to change between Energize to Actuate (ETA) and De-Energize to Actuate
(DTA). The Auxiliary Relay DTA-Inverting module's LED shows if power is correctly installed and
the state of the relay coil.
This module is not intended for SIL-certified applications.
Figure 42: Example of module connections to Auxiliary Relay Diode module
OW351_47 95
Figure 43: SIS Auxiliary Relay DTA Inverting top view and dimensions
96 OW351_47
Figure 44: SIS Auxiliary Relay DTA Inverting module bottom view and connections
The Auxiliary Relay DTA-Inverting module has the following connections:

 Two pin connections for primary power
 Two pin connections for secondary power
 Two pin connections for field output to the Auxiliary Relay Diode module
 Two pin connections for coil input
 Two pin connections for status output
 Two pin connections for auxiliary output contact closure (not shown in the "Example of
module connections to Auxiliary Relay Diode module" graphic)
Auxiliary Relay DTA-Inverting Module Specifications
Input field power 24 VDC ± 20% 5A maximum (actual current depends upon actuator
used)
Contains integrated OR-ing diodes for redundant 24 V inputs.
OW351_47 97
Relay current rating 5 A @ 24 VDC nominal

Isolation Power input and Logic Solvers must be connected to a common
ground.
Coil input voltage 17-28.8 VDC to energize
Coil input impedance 430 Ohms
Auxiliary Relay DTA-Inverting module functions
P RO C E S S DO R E L AY R E L AY R E L AY DI 1
LINE F A UL T D ET E CT IO N
ST AT E C HA N NE L ST AT E LED OUT P UT C HA N NE L
(R E L AY
ST AT US )
DO DI Relay
Output
Normal On (1) On On Off On (1) Open/ Open/ Open/
(Alarm Short Short Short
Off)
Tripped Off (10 Off Off On Off (0) Open/ Open/ N/A
(Alarm Short Short
On)
1
Only applies when Line Fault Detection is enabled. When Line Fault Detection is not enabled, the On
states detect opens only and the Off states detect shorts only.
98 OW351_47
3.12.5 Auxiliary Relay ETA-Direct module
The Auxiliary Relay ETA-Direct (Energize to Actuate) module is connected to a Logic Solver's
digital input and digital output channels and is then connected to a dual 24 VDC power supply.
Two field terminals are then used to connect to the Auxiliary Relay Diode module that is located
next to the field actuator in a similar manner as that shown in the graphic in the Auxiliary Relay
DTA-Inverting module (see page 95) topic.
Note: The dimensions and connections for the Auxiliary Relay ETA-Direct module are the same
as those for the Auxiliary Relay DTA-Inverting module (see page 95).)
The Auxiliary Relay ETA-Direct module energizes the field when Digital Out is turned On.
The Auxiliary Relay ETA-Direct module is paired with the Auxiliary Relay Diode module to enable
monitoring of the field wiring and the status of the relay. A switch on the Auxiliary Relay Diode
module is used to change between Energize to Actuate (ETA) and De-Energize to Actuate (DTA).
The Auxiliary Relay ETA-Direct module's LED shows if power is correctly installed and the state of
the relay coil.
This module is not intended for SIL-certified applications but may be useful in lock-out or deluge
applications where an unintended trip caused by a Logic Solver fault or operator error could be
hazardous to personnel and equipment.
Auxiliary Relay ETA-Direct Module Specifications
Input field power 24 VDC ± 20% 5A maximum l (actual current depends upon
actuator used)
Contains integrated OR-ing diodes for redundant 24 V inputs.
Relay current rating 5 A @ 24 VDC nominal
Isolation Power input and Logic Solvers must be connected to a common
ground.
Coil input voltage 17-28.8 VDC to energize
Coil input impedance 430 Ohms
Auxiliary Relay ETA-Direct module functions
P RO C E S S DO R E L AY R E L AY R E L AY DI LINE F A UL T
ST AT E C HA N NE L ST AT E LED OUT P UT C HA N NE L 1
D ET E CT IO N
(R E L AY
ST AT US )
DO DI Relay
Output
Normal Off (0) Off Off Off On (1) Open/ Open/ Open/
(Alarm Short Short Short
Off)
Tripped On (1) On On On Off (0) Open/ Open/ N/A
(Alarm Short Short
On)
OW351_47 99
P RO C E S S DO R E L AY R E L AY R E L AY DI LINE F A UL T
ST AT E C HA N NE L ST AT E LED OUT P UT C HA N NE L 1
D ET E CT IO N
(R E L AY
ST AT US )
1
Only applies when Line Fault Detection is enabled. When Line Fault Detection is not enabled, the On
states detect opens only and the Off states detect shorts only.
3.12.6 Auxiliary Relay Diode module
The Auxiliary Relay Diode module is paired with either the Auxiliary Relay ETA-Direct module
(see page 99) or the Auxiliary Relay DTA Inverting modules (see page 95) to extend the Logic
Solver's automatic testing of field wiring past these relays to the digital end device.
A switch on the Auxiliary Relay Diode module is used to change between Energize to Actuate and
De-Energize to Actuate operation.
Auxiliary Relay module specifications
Mode selection Switch selectable between ETA and DTA operation. Incorrect switch position will
cause bad quality on Logic Solver Digital Input.
Diode rating 24 VDC ± 20% 5 A maximum (actual current depends upon actuator used)
Mounting Per DIN 43729
100 OW351_47
The following figure shows the dimensions, connections, and switch positions on the Auxiliary
Relay Diode module.
Figure 45: Auxiliary Relay Diode Module
OW351_47 101
3.12.7 RC Compensator module
When driving inductive loads greater than or equal to 0.8 Henry in simplex or 0.3 Henry in
redundant, an RC compensator may be required. The RC Compensator module is sized at 3.3 kΩ
and 0.47 μf for simplex and 2.7 kΩ and 0.22 μf for redundant. This module can be used for
simplex and redundant applications. The dimensions of the RC Compensator module are as
follows
 Height 2.31 cm (0.91 in.)
 Width 3.48 cm (1.37 in.)
 Depth 1.7 cm (0.67 in.)
Figure 46: Wiring diagram and terminations for digital output channels with RC
compensator
102 OW351_47
3.12.8 End of Line Resistance module
The Digital Input channels have line fault detection for detecting open or short circuits in field
wiring. The End of Line Resistance module provides a 12 KΩ resistor in parallel (allows the open
circuit detection) and a 2.4 KΩ resistor in series (allows short circuit detection) to provide the
appropriate resistance for line fault detection. This module connects to the digital input channel
and to a field contact. The dimensions of the RC Compensator module are as follows
 Height 2.31 cm (0.91 in.)
 Width 3.48 cm (1.37 in.)
 Depth 1.7 cm (0.67 in.)
Figure 47: Wiring diagram and terminations for digital input channels (with line fault
detection options)
OW351_47 103
S E C T I O N 4
4 Adding and configuring SIS components in the

Ovation Developer Studio
IN THIS SECTION
Software components of Ovation SIS .......................................................................... 105

Overview of adding and configuring SIS components .................................................. 106
Using the Ovation Developer Studio to configure SIS components .............................. 108
Verify SIS licenses ...................................................................................................... 108
To add an SIS System to the Ovation System ............................................................. 108
To add an SISNet Rings to the Ovation System........................................................... 109
To add an SIS Data Server to the Ovation System ...................................................... 111
To add an SIS Router to the Ovation System .............................................................. 114
To add an SIS Network Switch to the Ovation System ................................................. 117
To add an SIS Interface Controller (SIS Drop) ............................................................. 119
To add an IOIC device and an SIS I/O device number (Device driver) ......................... 120
To add an I/O device to the Ovation System................................................................ 123
To add an SIS I/O device to the Ovation System ......................................................... 123
To assign an SIS Data Server to an SIS I/O Device ..................................................... 129
To configure SIS LAN Network Switches ..................................................................... 132
To upload configuration files to SIS Switch from Ovation drop using Ovation Network
Connection (Ethernet option): Generate & Configure Source Type .............................. 133
To generate SIS Switch configuration files for manual configuration: Generate & Save Source
Type ........................................................................................................................... 146
To upload configuration files to SIS Switch from non-Ovation drop using serial connection
(Serial option): Configure via Serial Source Type ......................................................... 151
To add and configure SIS Logic Solvers in the Ovation System ................................... 161
To configure an SIS I/O channel .................................................................................. 168
Ovation Point for SIS Hardware Inputs (Analog/Digital Inputs) ..................................... 177
SIS Hardware Outputs (Digital Outputs) ...................................................................... 180
To configure SIS Control Modules ............................................................................... 185
To add an SIS Control Sheet to the SIS Ovation system .............................................. 187
SIS Alarming with Logic Solver timestamp ................................................................... 188
To view SIS points ...................................................................................................... 195
Removing or Deleting an SIS Point.............................................................................. 197
4.1 Software co mpon ents of Ov ation SIS

S O FT WARE C O M P O NE NT S O F O V A T I O N S IS
S O FT WARE LO C AT IO N OP E RAT ING S Y S T EM I NT E RF AC E S TO:

C O M P O NE NT
SIS Data Server SIS Data Server pSOS operating system  Logic Solver (external)
 Net Repeater
(external)
 CIS
OW351_47 105
4.2 Overview of adding and configuring SIS components
S O FT WARE LO C AT IO N OP E RAT ING S Y S T EM I NT E RF AC E S TO:

C O M P O NE NT
Ovation Ovation Controller VxWorks operating system  Controller embedded

Controller software (external)
Interface to SIS  SIS Data Server
Data Server embedded software
(CIS)  Ovation SIS
Engineering tools
 Ovation SIS MMI
Tools
 SIS Write Server
Ovation SIS Engineering or MS Windows 2008/Windows 7  CIS
Write Library Operator Station  Ovation SIS
Engineering tools
 Ovation SIS MMI
Tools
Ovation SIS Engineering MS Windows 2008/Windows 7  CIS
Engineering station  SIS Write Server
Tools
Ovation SIS Operator Station MS Windows 2008/Windows 7  CIS
MMI Tools  SIS Write Server
4.2 Ov erv iew of adding and c onfiguring SIS co mpon ents

The following steps provide an overview of adding and configuring the SIS hierarchy in the
Ovation Developer Studio:
1. Verify SIS licenses (see page 108).

2. Add a new SIS System (see page 108).
3. Add a new SISNet Rings (see page 109).
4. Add a new SIS Data Server (see page 111).
5. Add a new SIS Router (see page 114).
6. Add new Network Switches (see page 117).
7. Add an SIS Interface Controller (see page 119).
8. Add an SIS I/O device number (see page 120).
9. Associate a Node point (see page 127) with an SIS I/O device.
10. Assign an SIS Data Server (see page 129) to an SIS I/O device.
11. Configure the SIS LAN Network Switches (see page 132).
12. Add a new SIS Logic Solver (see page 161).
13. Configure SIS I/O channel (see page 168).
14. Add a new Control Sheet (see page 187).
106 OW351_47
4.2 Overview of adding and configuring SIS components
The following figure illustrates an example of an SIS configuration hierarchy in the Ovation
Developer Studio.
Figure 48: SIS configuration hierarchy
OW351_47 107
4.3 Using the Ovation Developer Studio to configure SIS components
4.3 Using the Ov ation Dev eloper Studio to co nfigure SIS

compon ents
Information on adding and configuring the various software components of Ovation SIS can be
found in the following sections. Adding networks, devices and points usually require using the
Insert New function initiated by right-clicking menu of an item in the Ovation Developer Studio
hierarchy. For a better understanding of the other right-click functions, see the Ovation Developer
Studio User Guide.
Note: An SIS point must be in the SIS Data Server and not in the SIS Logic Solver, have any
references removed and moved using drag- and-drop operation to the parent Controller before it
can be deleted (See Deleting an SIS Point.)
4.4 Verify SIS licenses
SIS can only be enabled if SIS licenses are installed on the Ovation system. Before starting SIS
configuration, verify the availability of the SIS licenses. The SIS licenses are accessed through
the Developer Studio. Refer to the Ovation Developer Studio User Guide.
4.5 T o add an SIS Sy stem to the Ov ation Sy stem
For the Ovation 3.5.1 release, the SIS Network node will not be available in the SIS hierarchy;
instead a new node, SIS-System, will be available in the SIS hierarchy. This will be a virtual
node (no properties) added in to the hierarchy by the system.
The SIS Switches, SISNet Rings, SIS Interface Controllers, and the corresponding SDSs are
defined under SIS System.
The SIS-System contains two virtual nodes:

 SISNet Rings: It is a Fiber optic based ring topology network made between the SISNet
Repeaters. SISNet Ring is used for exchanging the global secure parameters. SISNet Ring
can exist between different SIS Interface Controller SDSs. In other words, SISNet Ring can
be configured by connecting SDSs from different SIS Interface Controllers.
 SIS Networks: Two or more SIS Switches connected in a ring using the Gigabit Ethernet.
Prerequisites
 Make sure that the Ovation network server is up and running.
Procedure
1. Access the Ovation Developer Studio.

2. Use the system tree to navigate through the following nodes and their sub nodes to the SIS
System:
Hardware Root
Systems
[System name]
Networks
[Network name]
108 OW351_47
4.6 To add an SISNet Rings to the Ovation System
SIS System
3. Right-click SIS System and select Insert New. The Insert New window appears.
Figure 49: Insert New SIS System window
Note: You can add only one SIS-System in the Ovation Developer Studio hierarchy .
4. Name of the SIS System should always be SIS-System. This is a system generated name.
5. Click Ok. The new SIS-System with two virtual nodes (SISNet Rings and SIS Networks)
appears in the Ovation Developer Studio hierarchy.
4.6 T o add an SISNet Rings to the Ov ation Sy stem
Prerequisites
 Make sure an SIS-System is added in Ovation Developer Studio hierarchy (see page 108).
Procedure
2. Use the system tree to navigate through the following nodes and their sub nodes to the
SISNet Rings:
Hardware Root
Systems
[System name]
Networks
[Network name]
SIS-System
SISNet Rings
OW351_47 109
4.6 To add an SISNet Rings to the Ovation System
3. Right-click SISNet Rings and select Insert New. The Insert New Wizard appears.
Figure 50: Insert New SISNet Rings Wizard
4. Enter a unique SISNet Rings Name (Maximum 17 characters) that is not used anywhere else
in system.
Note: The name can contain alphanumeric characters, underscore (_), hyphen (-), or may be a
combination of all these, but no spaces or special characters are allowed. The SISNet Rings
name will be converted to uppercase character by the system automatically.
5. Enter a valid and unique SISNet Rings identifier number. The valid numbers are between 0-
31. Negative numbers and blank identifiers are not allowed.
Note: The SISNet Rings name and identifier can be renamed after it has been created. Also, no
more than 32 SISNet Rings per system are allowed.
110 OW351_47
4.7 To add an SIS Data Server to the Ovation System
6. Click the Finish button. The SISNet Rings window appears.
Figure 51: SISNet Rings window
7. Select the Ok button. The new SISNet Rings appears in SIS-System hierarchy under the
SISNet Rings node.
Note: If a duplicate SISNet Rings name or identifier is found, system will not allow inserting the
new SISNet Rings.
4.7 T o add an SIS Data Serv er to the Ov ation Sy ste m

Prerequisites
 Make sure SISNet Rings are added in the SIS-System hierarchy (see page 109).
Procedure

Network Data Servers:
Hardware Root
Systems
[System name]
Networks
[Network name]
SIS-System
SISNet Rings
[SISNet Rings name]
SIS Networks Data Servers
OW351_47 111
3. Right-click SIS Network Data Servers and select Insert New. The New SIS Network Data
Servers Wizard appears.
Figure 52: New SIS Data Server window
4. Enter a unique SIS Data Server name (maximum of 14 characters) that is not used anywhere
else in the system. The Data Server name must have at least one (1) alphanumeric character
and may contain the dollar symbol ($), underscore (_) or hyphen (-). Spaces, special
characters, and _B suffix are not allowed. The _B suffix is used for secondary Data server
only.
112 OW351_47
Note: The SIS Data Server name can be renamed before assigning it to an SIS IO device. It
cannot be renamed once it is assigned to an SIS IO device.
5. Click the Finish button. The new SIS Networks Data Servers configuration window appears.
Figure 53: SIS Data Server configuration window
6. Enter the following attributes for the new SIS Data Server:
SIS Data Server attributes
AT T RI B UT E D E S C RIP T IO N
Data Server Name The name that entered when the new SIS Data Server (Step 3) is inserted
(maximum of 14 characters). At least one (1) alphanumeric must be used, and it
can include $, -, and _. The Suffix _B is not allowed.
SIS Identifier This is set by the system. The valid range is 1-254.
SISNet Ring This is set by the system. It takes the value of SISNet Ring under which this SIS
identifier Data Server is added. The valid range is 0-31.
Assigned Drop This will be grayed-out. It is automatically populated when the SIS Data Server is
assigned to an SIS Interface Controller.
Virtual Data Server Indicates if SIS Data Server is a Virtual Server. Refer to Virtual Safety
Instrumented System (SIS) User Guide for information about Virtual SIS and
Virtual SIS Data Servers.
Redundant Data When this check box is selected, the SIS Data Server works in the redundant
Server mode (if partner is present).
Data Server This is automatically generated based on the SIS Data Server Name field and
Partner Name additional ‘_B’ letter.
Maximum Raw I/O SIS Data Server receives I/O data from Logic Solvers. It can either send that data
Delay (msec) to the SIS Interface Controller immediately or buffer it for 10-100 minutes. This
mechanism prevents network packets fragmentation. However, it slightly
increases the time needed to update point value on the Ovation network.
OW351_47 113
4.8 To add an SIS Router to the Ovation System
Primary
Data Server IP IP address of the Primary SIS Data Server (must be a valid IP address in the SIS
Address network). If this is a redundant configuration, the Primary IP address must be
lower than the Partner IP address.
Data Server Ethers Enter the Ethers (MAC) address of the Primary SIS Data Server using the format
Address xx:xx:xx:xx:xx:xx (insert colons between every two characters).
The address is located on the SIS Data Server module.
Partner
Data Server IP IP address of the Partner SIS Data Server (available if there is a SIS Data Server
Address Partner). If this is a redundant configuration, the Partner IP address must be
higher than the Primary IP address.
Data Server Ethers Enter the Ethers (MAC) address of Partner SIS Data Server (available if there is
Address a SIS Data Server Partner) (using the format xx:xx:xx:xx:xx:xx (insert colons
between every two characters)).
The address is located on the SIS Data Server module.
7. Click Apply.
4.8 T o add an SIS Router to the Ov ation Sy stem

Prerequisites
 Make sure an SIS System is added in Ovation Developer Studio hierarchy (see page 108).
Procedure

Networks:
Hardware Root
Systems
[System name]
Networks
[Network name]
SIS System
SISNet Rings
SIS Networks
114 OW351_47
3. Right-click SIS Networks and select Insert New. The Insert New SIS Networks Wizard
appears.
Figure 54: New SIS Networks wizard
4. Enter a unique SIS router name (maximum of 14 characters) that is not used anywhere else
in system. Only lowercase alphanumeric character, and hyphen (-) are permitted. Spaces,
special characters, and underscore (_) are not permitted. Also -b suffix is prohibited. This
suffix is used for the secondary router only.
Note: SIS router name can be renamed after it has been created.
OW351_47 115
5. Click the Finish button. The new SIS Networks configuration window appears.
Figure 55: New SIS Networks configuration window
6. Enter the following attributes for the new SIS Networks:
SIS Networks attributes
SIS Router Name The name that was entered when the new SIS Network (Step 3) is inserted
(maximum of 14 characters). Only lowercase alphanumeric character and
hyphens (-) are permitted. Spaces, special characters, and underscores (_) are
not permitted. Also -b suffix is not allowed. This suffix is used for secondary router
only.
Backup SIS Router This is automatically generated based on the SIS Router Name field and
Name additional ‘-b’ letter
Ovation Highway Interface
Active Router IP Must be filled in. IP address of Ovation Interface-A. Must be a valid IP address in
Address Ovation network in regards to netmask and must be unique across system.
Backup Router IP Must be filled in. IP address of Ovation Interface-B. Must be a valid IP address in
116 OW351_47
4.9 To add an SIS Network Switch to the Ovation System
Router A IP Must be filled in. IP address of Ovation HSRP-A. Must be a valid IP address in
Router B IP Must be filled in. IP address of Ovation HSRP-B. Must be a valid IP address in
Netmask Must be filled in. Must be a valid mask.
SNMP TrapHost IP Optional. Must be a valid IP address if filled in.
Address
SIS Network Interface
Active Router IP Must be filled in. IP address of SIS Interface-A. Must be a valid IP address in SIS
Address network in regards to SIS netmask and must be unique across system.
Backup Router IP Must be filled in. IP address of SIS Interface-B. Must be a valid IP address in SIS
Address network in regards to SIS netmask and must be unique across system.
Router A IP Must be filled in. IP address of SIS HSRP-A. Must be a valid IP address in SIS
Address network in regards to netmask and must be unique across system.
Router B IP Must be filled in. IP address of SIS HSRP-B. Must be a valid IP address in SIS
Address network in regards to netmask and must be unique across system.
SIS Netmask Must be filled in. Must be a valid Network mask.
Time Zone
Name Set by system.
UTC offset Set by system.
DST Timezone Set by system.
7. Select Apply/OK. The new SIS Router node appears in SIS hierarchy.
4.9 T o add an SIS Network S witc h to the Ov ation Sy stem
Prerequisites
 Make sure an SIS Router is added in Ovation Developer Studio hierarchy (see page 114).
Procedure
Networks Switches:
Hardware Root
Systems
[System name]
Networks
[Network name]
SIS System
SISNet Rings
[SISNet Rings name]
SIS Networks
OW351_47 117
4.9 To add an SIS Network Switch to the Ovation System
[SIS Router name]

SIS Network Switches
3. Right-click SIS Network Switches and select Insert New. The Insert New SIS Network
Switches Wizard appears.
Figure 56: New SIS Network Switches window
4. Enter a unique Switch name (maximum of 40 characters) that is not used anywhere else in
the system. Alphanumeric character, underscore (_) and hyphen (-) are permitted. Spaces
and special characters are not permitted. Also, _B suffix is prohibited. This suffix is used for
the secondary switch only.
Note: Switch name can be renamed after it has been created.
118 OW351_47
4.10 To add an SIS Interface Controller (SIS Drop)
5. Click the Finish button. The new SIS Networks Switches configuration window appears.
Figure 57: New SIS Networks Switches window
6. Enter the following attributes for the new SIS Networks Switches:
SIS Networks Switches attributes
Switch Name The name that was entered when the new SIS Network Switch (Step 3) is
inserted (maximum of 40 characters). Alphanumeric character, underscore (_),
and hyphen (-) are permitted. Spaces and special characters are not permitted.
Number of Ports The only valid numbers are: 10, 18, and 26.
Is Router This has to be checked if SIS router is connected to the SIS Switch.
Connected
Switch IP Address IP address of primary switch. Must be a valid IP address and must be unique
across system.
Partner
Name This is automatically generated based on the SIS Network Switch field and
additional ‘_B’ letter.
IP Address IP address of secondary switch. Must be a valid IP address and must be unique
across system.
7. Click Apply/OK. The new SIS Network Switch appears in the Ovation Studio WorkPad.
4.10 T o add an SIS Interface Co ntroller (SIS Drop)
The procedure for adding an SIS Interface Controller (SIS drop) is similar to adding an Ovation
drop. For adding an Ovation drop, refer the Ovation Developer Studio User Guide.
OW351_47 119
4.11 To add an IOIC device and an SIS I/O device number (Device driver)
4.11 T o add an IOIC d ev ice and a n SIS I/ O dev ice nu mber ( Dev ice
driv er)
Prerequisites
 Make sure you have added and configured an SIS System (see page 108).
 Make sure you have added and configured an SIS Data Server (see page 111).
 Make sure you have added and configured an SIS Interface Controller (SIS Drop) (see page
119).
Procedure
Note: After adding and configuring the SIS-System, SIS Data Server, and SIS Drop, the next
step is to add a device and an SIS I/O device number (device driver). However, before
performing this, a device number (driver) for the device needs to be added.

Use the system tree to navigate through the following nodes and their sub nodes to the
Device Numbers:
Hardware Root
Systems
[System name]
Networks
[Network name]
Unit
[Unit name]
Drops
[Drop name]
Configuration
Controller
Devices
Device Numbers
2. Right-click on the Device Numbers item.
120 OW351_47
3. Select Insert New from the pop-up menu. The Insert New Device Numbers Wizard appears.
Figure 58: Insert New Device Numbers Wizard
Note: If you need to change a driver on a previously configured device, or anytime a new device
is added, perform a clear/load function on the Controller. The Device Number represents the
physical devices that can communicate with the Controller.
4. Select a number sequentially, starting at 1 to a maximum of 9. An example would be if two

devices were to be configured, their device numbers would be 1 and 2, not 1 and 3 or 4 and 5.
5. Click Finish. The New Device Numbers dialog box appears showing the Controller Driver
Parameters tab.
OW351_47 121
6. Select I/O Driver Type as OVATION for IOIC device and select I/O Driver Type as Ovation
SIS for SIS device as shown in the following figures:
Figure 59: I/O Driver Type option for IOIC device
Figure 60: I/O Driver Type option for SIS device
Note: The failover occurs in SIS Interface Controller, if the following settings are made:
In Developer Studio navigate to: SIS Controller > Configuration > Controller > Devices >
Device Numbers.
Find SIS Device (usually ‘Device 2’), open the device and set the Fail Controller On
Error option to True.
Ovation Controller network cables are unplugged (or broken), then the controller will failover
after ‘timeout’. If the connection needs to be restored before timeout, then the controller will not
failover. By default, the Timeout is set to 10000 msec.
122 OW351_47
4.12 To add an I/O device to the Ovation System
4.12 T o add an I/O d ev ice to the Ov ation Sy stem

For adding I/O device to the Ovation System, refer the Ovation Developer Studio User Guide.
4.13 T o add an SIS I/O d ev ice to the Ov ation Sy stem
Prerequisites
 Make sure you have added and configured an SIS Interface Controller (SIS Drop (see page
119)).
 Make sure you have added an SIS I/O device number (see page 120).
Procedure
After you have added and configured an SIS Data Server for your Ovation system, you need to
assign this Data Server to an Ovation SIS Interface Controller drop (SIS Drop). In order to
perform this, you must add a new I/O device to the Controller and then assign the Data Server to
this I/O device.

2. Use the system tree to navigate through the following nodes and their sub nodes to the I/O
Devices:
Hardware Root
Systems
[System name]
Networks
[Network name]
Unit
[Unit name]
Drops
[Drop name]
I/O Devices
OW351_47 123
4.13 To add an SIS I/O device to the Ovation System
3. Right-click I/O Devices and select Insert New. The Insert New I/O Device Wizard appears.
Figure 61: Insert New I/O Device wizard
4. Select an I/O Device Number sequentially, starting at 5 to a maximum of 11. Select Ovation
SIS for the I/O Device Type.
Note: Configuration with more than one SIS I/O device on the SIS Interface Controller is not
supported.
124 OW351_47
5. Select the Finish button. The configuration window for the new SIS I/O device appears.
(Notice that the field for the Node Record Point Name is blank.)
Figure 62: SIS I/O device configuration window
6. Enter the following attributes for the new I/O device:
SIS I/O device attributes
I/O Device Number Number of the SIS I/O device. This is displayed by the system.
I/O Device Type Should be Ovation SIS. This is displayed by the system.
Node Record Point Comes from the Node point (RN record type). Refer to: To associate a
Name Node point with an SIS I/O device (see page 127) for instructions on
creating the Node point.
SIS identifier This is displayed by the system.
Enable SIS I/O Indicate whether Virtual SIS I/O simulation should be enabled. Refer to
Simulation Virtual Safety Instrumented System (SIS) User Guide for information
about Virtual SIS and Virtual SIS I/O simulation.
Network Interface
OW351_47 125
Message Port UDP port used for communication between the SIS Data Server and the
SIS Interface Controller. This is a socket number. The recommended
value is 2080, DO NOT change this number.
Alarm Handler Port Transfers alarm messages between the SIS Data Server and the SIS
Interface Controller. This is a UDP port number. The recommended value
is 3051, DO NOT change this number.
Network Interface This can be a single or dual network connection.
Connection
Network Interface Primary SIS Network Interface Select N1 from the drop-down list.
Backup Network Backup SIS Network Interface Select N4 from the drop-down list. This
Interface option is applicable only to hardware controller when Network Interface
Connection is set to Dual.
Primary Network Interface
IP Address IP Address of primary SIS network interface (typically provided by the
System Administrator).
Interface Mode Ethernet connection speed and duplex mode. Should be always
100mbps/full duplex.
Backup Interface Ethernet connection speed and duplex mode. Should be always
Mode 100mbps/full duplex.
Partner Network Interface
IP Address IP Address of partner network interface (typically provided by the System
Administrator).
Interface Mode Ethernet connection speed and duplex mode. Should be always
100mbps/duplex.
Backup Interface Ethernet connection speed and duplex mode. Should be always
Mode 100mbps/duplex.
Network Device
Switch Select one of the defined switches. Ideally the switch where the SIS
Interface Controller network interface is connected.
SIS Netmask Set by the system.
Multicast IP Multicast IP addressing should be calculated by the system and should be
Address in the 127.51.5.XXX format, where xxx is drop ID.
SIS Active Router Set by the system.
IP
7. Click the Apply button and the new SIS I/O Device appears in the Ovation Studio hierarchy
tree.
Note: For a better understanding of the other right-click functions, see the Ovation Developer
Studio User Guide.
126 OW351_47
4.13.1 To associate a Node point with an SIS I/O device
Prerequisites
 Make sure you have added and configured an SIS Data Server. (see page 109)
119).
 Make sure you have added an SIS I/O device (see page 123).
Procedure
Note: After you have added an SIS I/O device, you need to create a Node point and assign it to
the new I/O device.

2. Use the system tree to navigate through the following nodes and their sub nodes to the Node
Points:
Hardware Root
Systems
[System name]
Networks
[Network name]
Unit
[Unit name]
Drops
[Drop name]
Points
Node Points
OW351_47 127
3. Right-click Node Points and select Insert New. The Insert New Node Points Wizard appears.
Figure 63: Insert New Node Points Wizard
4. Enter a point name and select the desired frequency for the point.
5. Click Finish. The configuration window for the Node point appears.
6. Select the Hardware tab.
128 OW351_47
4.14 To assign an SIS Data Server to an SIS I/O Device
7. Select the SIS I/O device you want to associate with the Node point. Select the I/O task
index as 2.
Figure 64: Node Point configuration window
8. After the Node point is created, select the Refresh button and the name of the Node point
appears in the Node Record Point Name field in the New I/O devices window.
4.14 T o assign an SIS Dat a Serv er to an SIS I/O Dev ice
Prerequisites
 Make sure you have added and configured an SIS Interface Controller Drop (see page 119).
 Make sure you have added and configured an SIS I/O device (see page 123).
Procedure
After you have added and configured an SIS Data Server, an SIS I/O device, and SIS Drop to
your Ovation system, you need to assign this Data Server to an SIS Interface Controller.

Data Server:
Hardware Root
Systems
[System name]
Networks
[Network name]
Unit
OW351_47 129
[Unit name]
Drops
[Drop name]
I/O Devices
I/O Device 5 Ovation SIS
SIS Data Servers
3. Right-click SIS Data Servers and select Insert New. The Insert New SIS Data Server Wizard
appears.
Figure 65: Insert New SIS Data Server Wizard
4. Enter the following attributes for the new I/O Data Server Device.
SIS Data Server device attributes
Data Server Name This is a pull-down list of the SIS Data Servers that is defined under the SIS
System node.
SIS Data Server ID Sequential number assigned to the Data Server.
130 OW351_47
5. Click Finish. The configuration window for the new SIS I/O Data Server appears.
Figure 66: SIS Data Server configuration window
6. Enter the following attributes for the new I/O Data Server.
SIS Data Server attributes
Data Server Name This is a pull-down list of the SIS Data Servers that you defined under the
SIS System node.
SIS Net Ring SISNet Ring identifier number. This is read-only field.
Identifier
SIS Data Server ID Sequential number assigned to the Data Server.
Diagnostic/Status
Suppress SIS Should be selected if Repeaters are not used in system.
Network Repeater
Alarm
Ovation Point Name Ovation point that holds diagnostic status of the SIS Data Server. Enter the
point name in the Ovation Point Name field that determines the quality of
the Data Server. Point will be created under Node point and hardware
assignment will be made automatically. This is the preferred way to assign
points to SIS hardware. Otherwise, the description of bits will not be filled
properly.
7. Click Apply and the new SIS I/O Device appears in the Ovation Studio hierarchy tree.
Note: For a better understanding of the other right-click functions, see the Ovation Developer
Studio User Guide.
OW351_47 131
4.15 To configure SIS LAN Network Switches
4.15 T o configure SIS LAN Net work S witche s

The SIS Switch Configuration Tool enables you to create and upload switch configuration files for
the SIS Network Switches (such as Cisco IE 3000) that are used in an SIS System. The following
are the ways to create and upload the configuration files to physical SIS Switches.
 To Upload Configuration files to SIS Switches from an Ovation drop using an Ovation
Network Connection (Ethernet option): Generate & Configure Source Type.
 To generate SIS Switch configuration files for manual configuration: Generate & Save Source
Type.
 To Upload Configuration files to SIS Switches from a Non-Ovation drop using Serial
Connection (Serial option): Configure via Serial Source Type.
After the configuration files are uploaded to the switch successfully, the SDSs should be rebooted
to obtain the new parameters from DHCP.
Prerequisites for configuring the switch file

 Make sure SIS Switches have proper firmware loaded (for example, IOS Version
12.2(50)SE2).
 Make sure you have added and configured an SIS System (see page 108) in hierarchy.
 Make sure you have added and configured the SISNet Rings (see page 109).
 Make sure you have added and configured the SIS Routers (see page 114) under SIS
Networks.
 Make sure you have added an SIS Network Switch (see page 117).
 Make sure you have added and configured an SIS Interface Controller (see page 119).
 Make sure you have added an SIS I/O device (see page 123).
 Make sure you have associated a Node point (see page 127) with the SIS I/O device.
 Make sure you have configured the NTP server.
 Make sure you have assigned an SIS Data Server (see page 129) to the SIS I/O device.
 Make sure you have configured the SIS loggers (see page 243).
Note: The information to check firmware version and to upgrade the firmware can be found on
the CISCO Website:
http://www.cisco.com/en/US/docs/switches/lan/cisco_ie3000/software/release/12.2_50_se/relea
se/notes/ol19166.html#wp39570
This procedure should be followed each time when one of the below situations occurs:
 New SDS is added to system.
 SDS IP changes.
 SIS IO Device IP changes.
 One of SDSs is replaced (MAC address changes).
 IP address of SIS Switch, SDS, or SIS Interface Controller changes.
 NTP server changes.
 Any of the SIS System properties changes.
132 OW351_47
4.16 To upload configuration files to SIS Switch from Ovation drop using Ovation Network Connection
(Ethernet option): Generate & Configure Source Type
 SIS logger’s addresses change.

 SIS identifier of the SDS changes while importing the database.
 Switch port configuration changes in the Developer Studio with regards to router connected (if
one switch is removed from the connected router).
 SDS is moved from one controller to another controller, it results in changing the option 229
and requires you to re-run the SIS Switch Configuration Tool.
 Raw I/O delay time is changed, which needs the option 231 to be updated in the SIS Switch.
4.16 T o upload configuration fil es to SIS S witch from Ov ati on drop

using Ov ation Net work Con nection (Eth ernet option): Generate &
Configure Source T y pe
Note: The Ethernet method for uploading configuration is only possible if the switch has an IP
address assigned to it.

Networks:
Hardware Root
Systems
[System name]
Networks
[Network name]
SIS System
SIS Networks
OW351_47 133
3. Right-click the desired SIS Network and select the Run SIS Configuration option. The
Ovation SIS Configuration Tool Select mode window appears.
Figure 67: Ovation SIS Configuration Tool Select mode window
134 OW351_47
4. Select the Configure SIS Switch option. The Ovation SIS Switch Configuration Tool Select
configuration source type window appears.
Figure 68: Generate & Configure option
5. Click the Generate & Configure option to configure an SIS Network Switch.
OW351_47 135
6. After clicking the Generate & Configure option, the Developer Studio creates an XML file with
all the required information. The name of the file is same as the name of the SIS System.
Figure 69: XML validation
7. The Configuration Tool will validate the XML that was selected. You will be informed, if any
required property is missing or the file is corrupted. You can proceed only if the file is
successfully validated.
136 OW351_47
8. Click Next to proceed. The Ovation SIS Switch Configuration Tool configure network
connection window appears. The list of the available switches is displayed on the left side of
the window. Select the switch/switches from the available switches and move to the right
side of the window (Apply new configuration).
Figure 70: Configure network connection: Available switches
OW351_47 137
Figure 71: Configure network connection: Single switch selected
138 OW351_47
Figure 72: Configure network connection: Multiple switches selected
OW351_47 139
The Verify SIS Switches connection properties window appears for every switch to verify the
connection properties. The new properties for every switch are available under the
Configuration properties.
Figure 73: Verify SIS Switches connection properties
9. Select the Reboot check box to allow the tool to reboot the switch after configuration.
Otherwise, the new configuration will be merged into the running configuration and the switch
will not be rebooted.
10. Click Next to proceed. The Configuration settings summary window appears.
WARNING! Merging a new configuration into a running configuration may have unexpected
results. Therefore, the preferred method of applying a new configuration is to copy the startup
configuration and reboot the switch.
Note: The switch reboot procedure can take a few minutes to execute. During that time, the
switch is unavailable.
140 OW351_47
11. Review the configuration setting summary of the selected switches. Click the Configure
button to start the upload process.
Figure 74: Configuration settings summary
12. The Tool will configure and reboot the devices. During this process, some messages will be
displayed on the configuration tool window.
Note: If multiple switches are selected, the Tool configures and reboots the switches one by
one.
OW351_47 141
142 OW351_47
Figure 75: Configuring device status-2
OW351_47 143
144 OW351_47
OW351_47 145
4.17 To generate SIS Switch configuration files for manual configuration: Generate & Save Source Type
13. Click Run again for configuring the other switches.

14. After configuring all the connected SIS Switches, click the Close button to close the
application.
4.17 T o generate SIS Swit ch configur ation files for m anual

configuration: Generat e & Sav e Source T y pe
Note: The Generate & Save source type option does not configure a SIS Switch; it only creates
configuration files. Use the To upload configuration files to SIS Switch from non-Ovation drop
using serial connection (Serial option): Configure via Serial Source Type (see page 151) to
configure the SIS Switch by using the files generated by this source type option.

2. Use the system tree to navigate through the following nodes to the SIS Networks:
Hardware Root
Systems
[System name]
Networks
[Network name]
SIS System
SIS Networks
146 OW351_47
3. Right-click the desired SIS Networks and select the Run SIS Configuration option. The
Ovation SIS Configuration Tool window appears.
Figure 79: Ovation SIS Configuration Tool window

4. Select the Configure SIS Switch option. The Ovation SIS Switch Configuration Tool window
appears.
OW351_47 147
5. Select the Generate & Save option to create a new configuration file.
Figure 80: Generate & Save option
6. After clicking the Generate & Save option, the Developer Studio creates an XML file with all
the required information. The name of the file is same as the name of the SIS system.
148 OW351_47
7. The Tool will validate the XML that was selected. If any required property is missing or the file
is corrupted, the Tool will provide the information about the problem. Proceed only if the file is
successfully validated. Click Next to proceed.
Figure 81: XML validation
OW351_47 149
8. The Select destination path for new configuration file window appears. Specify the path to
save the configuration files on the disk. Click the Save button.
Figure 82: Configuration file destination path
150 OW351_47
4.18 To upload configuration files to SIS Switch from non-Ovation drop using serial connection (Serial
option): Configure via Serial Source Type
9. The Saving configuration files status window appears. Verify the path displayed on the
window.
Figure 83: Saving the configuration files
10. To configure the SIS Switch using the files created in Step 9, see To upload configuration files
to SIS Switch from non-Ovation drop using serial connection (Serial option): Configure via
Serial Source Type (see page 151).
11. After saving files on the disk, click the Close button to close the application.
4.18 T o upload configuration fil es to SIS S witch from n on -Ov ation

drop using s erial con nection (S erial option): Configure v ia
Serial Source T y pe
Note: Initially, the IP address is not assigned to the SIS Switch. Therefore, it is not possible to
upload the configuration file using the Ethernet option method. To upload a new configuration
file, use the Serial option method.
1. This source type does not create configuration files. To use this source type, you need to
generate and save switch configuration files by using the Generate & Save source type (see
To generate SIS Switch configuration files for manual configuration: Generate & Save Source
Type (see page 146).)
OW351_47 151
2. Copy the configuration files that were created in Step 1 and the Switch Configuration Tool
executable (Ovation\OvationBase\OvSisSwitchTool.exe) and the library
(Ovation\OvationBase\OvSisXmlConfig.dll) to the machine that is connected to an SIS Switch
with a serial cable.
3. Run the Switch Configuration Tool application. The Ovation SIS Configuration Tool Select
configuration source type mode window appears.
Figure 84: Select configuration source type

4. Click the Configure via Serial source type to configure the switch. The Select file with pre
made switch configuration window appears.
152 OW351_47
5. Select the appropriate configuration file. Only text configuration files are valid. Click Next to
proceed.
Figure 85: Select file with pre made switch configuration
The Configure serial port connection window appears.
OW351_47 153
6. Enter the appropriate serial port connection details. Click Next to proceed.
Figure 86: Configure serial port connection
154 OW351_47
7. Review the summary of the selected options. Click the Configure button to start the upload
process. The new configuration is merged into the running configuration on the switch. If the
Reboot switch after configuration check box is selected, the Switch reboots after
configuration.
Figure 87: Configuration settings summary
8. The Tool configures and reboots the switch. During this process some messages are
displayed on the Configuration Tool window.
Note: The Configuration Tool configures and reboots only one switch at a time. Repeat this
procedure for configuring multiple switches.
OW351_47 155
156 OW351_47
OW351_47 157
158 OW351_47
OW351_47 159
160 OW351_47
4.19 To add and configure SIS Logic Solvers in the Ovation System
9. After configuring the SIS switch, click the Close button to close the application.
10. Click the Run again option for configuring the other switches.
4.19 T o add and configure SIS Logic Solv ers in th e Ov ation Sy stem
Prerequisites
 Make sure you have added and configured an SIS Data Server. (see page 111)
 Make sure you have added and configured an SIS Network Switch (see page 117).
 Make sure you have added an SIS Interface Controller (SIS Drop) (see page 119).
Procedure

2. Use the system tree to navigate through the following nodes and their sub nodes to the Logic
Solvers:
Hardware Root
Systems
OW351_47 161
[System name]
Networks
[Network name]
Unit
[Unit name]
Drops
[Drop name]
I/O Devices
SIS Data Servers
[SIS Data Server name]
SIS Logic Solvers
3. Right-click Logic Solvers and select Insert New. The Insert New Logic Solver Wizard
appears.
Figure 94: Insert New Logic Solver wizard
4. Enter the following attributes for the new Logic Solver.
Logic Solver attributes
SIS Logic Solver Enter a unique Logic Solver name that is not used anywhere else in your system.
Name
162 OW351_47
Redundant SIS Select this checkbox to enable the Logic Solver to work in redundant mode (if a
Logic Solver partner is present).
You cannot change the redundancy mode after you have added in the hierarchy.
SIS Logic Solver This is the slot used by the Logic Solver. Slot numbers range from 1 to 32 and
Slot Number must be unique within the SIS Data Server.
You cannot change the slot number after configuring it.
5. Click Finish button. The configuration window for the new Logic Solver appears. Enter the
appropriate values for the attributes in each tab and then select OK.
 Config tab (see page 163).
 General tab (see page 165).
 Proof Testing tab (see page 167).
6. The new Logic Solver appears in the Ovation Studio hierarchy tree.
Notes: When a Logic Solver is added to the Studio, four Control Modules (see page 185) are
automatically created and appear under the Logic Solver in the Studio tree.
Sixteen I/O channels are also included under each Logic Solver and they appear in the Studio
WorkPad area.
For a better understanding of the other right-click functions, see the Ovation Developer Studio
User Guide.
4.19.1 Configuring the Logic Solver Config tab
After you have added an SIS Logic Solver, use the following Config tab to configure the Logic
Solver.
Figure 95: Logic Solver configuration window (Config tab)
OW351_47 163
Logic Solver attributes in Config tab
SIS Logic Solver Name Enter a unique Logic Solver name that is not used anywhere else in a
system.
Redundant SIS Logic Select this check box to enable Logic Solver to work in redundant mode (if a
Solver partner is present).
You cannot change the redundancy mode after you have added in the
hierarchy.
SIS Logic Solver Slot This is the slot used by the Logic Solver. Slot numbers range from 1 to 32
Number and must be unique within the SIS Data Server.
You cannot change the slot number after configuring it.
Overall CRC for the CRC code which reflects the configuration of the entire Logic Solver as
device calculated by the Ovation Developer Studio and is compared with the code
that is calculated by the Logic Solver at load time.
SIS Data Server SIS Data Server to which this Logic Solver is directly connected through
backplane connections. Name is entered by the system.
GSLOT Identifier Logic Solver global identifier. This is set by the system and is used as an
identifier for Logic Solvers configured to publish secure parameters globally
in the SISNet.
Combined CRC for all CRC code which reflects the configuration of all I/O channels as calculated
I/O channels by the Ovation Developer Studio and is compared with the code that is
calculated by the Logic Solver at load time. This code is the latest database
CRC value.
Diagnostic/Status
Ovation Point Name Enter the point name in the Ovation Point Name field. That point will hold
Logic Solver status information. Point will be created under Node Point and
Hardware assignment will be performed automatically.
This is the preferred way to assign points to the SIS hardware. Otherwise, the
description of the bits is not filled properly.
164 OW351_47
4.19.2 Configuring the Logic Solver General tab
After you have added an SIS Logic Solver, use the following General tab to configure the Logic
Solver.
Figure 96: Logic Solver configuration window (General tab)
Logic Solver attributes in General tab
Scan Rate This is the Logic Solver loop time. The available scan rates are 50ms, 100m s,
150ms, and 200 ms per period. The default rate (see page 228) is 50 ms.
Since the SIS Data Server sends control module information to the Controller
every second, scan rate is not related to update time.
OW351_47 165
I/O Data Update Determines interval of sending I/O channels’ values and qualities to SIS Data
Time Server. Logic Solver scans I/O channels in 50 ms loop. This parameter affects
only update rate of Ovation points.
Shadow block Refers to a specific Controller area where all the control sheets that contain
Control Task shadow algorithms are scanned at the same frequency.
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. Real update time is limited by SDS
update frequency. Assigning point to high frequency control task will not make
it faster.
Secure parameters
Publish secure Select this checkbox to enable this Logic Solver to publish secure parameters
params globally globally over the SIS Network.
Enable high-density This checkbox is currently enabled, but is disabled for editing. This option
secure parameters activates 16 secure parameters for each Logic Solver.
Nonsecure parameters
Nonsecure Identifies nonsecure parameters associated with this Logic Solver. Non-secure
parameters parameter reference per logic solver is 24.
166 OW351_47
4.19.3 Configuring the Logic Solver Proof Testing tab
After you have added an SIS Logic Solver, use the Proof Testing tab to configure the Logic
Solver.
Ovation SIS performs an automatic diagnostic whenever a Logic Solver reboots. You can use the
parameters in the Proof Testing tab to set the desired configuration for diagnostics:
 You can configure the Proof test timer period so that when the timer period expires, there will
be an automatic transfer to the backup Logic Solver. This forces a reboot and diagnostics are
performed (only available for redundant Logic Solvers).
 You can configure the Proof test timer to generate an SIS Event before the Proof Test timer
will expire.
 If a Logic Solver fails the power diagnostic during boot up, it will try again. If it fails a second
time, the Logic Solver will enter a "reduced mode." This mode will be indicated through the
Logic Solver RN record.
Figure 97: Logic Solver configuration window (Proof Testing tab)
Logic Solver attributes in Proof Testing tab
Proof test interval

Proof test interval (years) This, plus the days count, is the total proof test interval.
Proof test interval (days) This, plus the years count, is the total proof test interval.
Proof test reminder alert
Proof test remind alert due This is the number of days until the user is reminded to execute
(days) a proof test.
Enable automatic proof test to Select this check box to allow a proof test to run automatically
run at reminder time without operator attention (only available for redundant Logic
Solvers).
OW351_47 167
4.20 To configure an SIS I/O channel
4.20 T o configure an SIS I/ O chan nel
Prerequisites
 Make sure you have added and configured an SIS Logic Solver (see page 161).
Procedure
2. Use the system tree to navigate through the following nodes and their sub nodes to the I/O
Channels node:
Hardware Root
Systems
[System name]
Networks
[Network name]
Unit
[Unit name]
Drops
[Drop name]
I/O Devices
SIS I/O Device
SIS Data Servers
[SIS Data Servers name]
SIS Logic Solvers
SIS I/O Channels
Note: 16 I/O channels are also included under each Logic Solver and they appear in the Studio
WorkPad area.
168 OW351_47
3. Right-click on any I/O Channels in the WorkPad area and select Open. The I/O Channel
window appears.
Figure 98: I/O Channel window (Config tab)
4. Enter the following attributes for the I/O Channel in the Config tab. Each channel type has the
same attributes in the Config tab .
I/O Channel attributes for Config tab
Channel Number Number of the channel (1 through 16)

Enabled When box is checked, the channel is enabled and can be used.
Channel Type Type of channel that will be used:
 Undefined Channel Type.
 Analog Input Channel (see page 176).
 HART Analog Input Channel (see page 172).
 HART Two-state Output Channel (see page 174).
 Digital Input Channel (see page 170).
 Digital Output Channel (see page 171).
Ovation Point Name of the Ovation point that is assigned to the channel.
CRC (see page 2) CRC code which reflects the configuration of this I/O channel as calculated by
for individual I/O the Ovation Developer Studio and is compared with the code that is calculated
channel by the Logic Solver at load time.
SOE Enable To Enable Sequence of Events Function. (Applicable only for Digital input
channels).
5. After you have defined the attributes in the Config tab, use the applicable Attributes tab to
enter values for the selected Channel Type.
6. After you have entered the applicable attribute values in the Attributes tabs, select OK.
OW351_47 169
4.20.1 Configuring a Digital Input Channel

1. After you have configured the Config tab (see page 168) for a Digital Input channel, use the
Attributes tab to configure a Digital Input Channel.
Figure 99: I/O Channel window (Attributes tab for digital input channel)
I/O Channel attributes for digital input channel
Detect open and When this box is checked, this enables the card to detect open and short
short circuit circuits in field wiring.
Inverted When this box is checked, the value reported by the LSDI algorithm will be the
opposite value of that on the physical input channel.
2. Enter the applicable Attributes and select OK.
Once the Input channel is defined, a corresponding Ovation raw input point needs to be
created.
170 OW351_47
4.20.2 Configuring a Digital Output Channel

1. After you have configured the Config tab (see page 168) for a Digital Output channel, use the
following Attributes tab to configure a Digital Output Channel.
Figure 100: I/O Channel window (Attributes tab for digital output channel)
I/O Channel attributes for digital output channel
Detect open and When this checkbox is checked, this enables the card to detect open and
short circuit short circuits.
OW351_47 171
4.20.3 Configuring a HART Analog Input Channel

1. After you have configured the Config tab (see page 168) for a HART Analog Input channel,
use the Attributes tab to configure a HART Analog Input Channel.
Figure 101: I/O Channel window (Attributes tab for HART analog input channel)
172 OW351_47
I/O Channel attributes for HART analog input channel
Enable NAMUR alarming When this checkbox is checked, NAMUR alarming is performed on
the channel. If enabled and if the transmitter supports it, any analog
value that is outside the NAMUR limits (106.25% top limit and -2.5%
bottom limit) for four seconds has its quality set to BAD. (NAMUR is
an international association of automation technology in process
control industries.)
Analog over range pct The percent value at which the analog value is considered
overrange. Should be used in conjunction with Bad if limited.
Analog under range pct The percent value at which the analog value is considered
underrange. Should be used in conjunction with Bad if limited.
Conversion Type Raw data is converted to point values. Indirect is the only type of
conversion currently in use.
Bottom of Scale The low scale value, engineering units code, and number of digits to
the right of the decimal point associated with OUT.
Top of Scale The high scale value, engineering units code, and number of digits to
the right of the decimal point associated with OUT.
Bad if Limited When this box is checked, the LSAI algorithm assigned to given
channel propagates BAD quality to downstream algorithm if point is
outside the configured over/under range. The quality of point
associated with the input channel is not set to BAD.
Analog under range pct The percent value at which the analog value is considered
underrange. If the signal is below this limit, its status indicates the
value is limited low.
Loop current mismatch detection When checked, you can enable the detection of a loop current
mismatch between the analog and digital current values from the
HART device.
HART Errors
Ignore PV Out Limits Primary Variable (PV) values that are higher or lower than the
configured limits are ignored when determining PV quality.
Ignore Analog-Digital Mismatch Ignores discrepancy between the current on channel and its digital
equivalent. A mismatch can indicate that current is leaking to ground
even though the circuit appears healthy.
Ignore PV Output Saturated PV values that are output saturated are ignored when determining
PV quality.
Ignore PV Output Fixed PV values that have a fixed output are ignored when determining PV
quality.
Ignore Loss of Digital Comms Ignores loss of digital communication with HART device (loss is
detected after three retries).
Ignore Field Device Malfunction Values determined during a field device malfunction are ignored
when determining quality.
OW351_47 173
4.20.4 Configuring a HART Two-state Output Channel

1. After you have configured the Config tab (see page 168) for a HART Two-state Output
channel, use the Attributes tab to configure a HART Two-state Output Channel.
Figure 102: I/O Channel window (Attributes tab for HART two-state output channel)
174 OW351_47
Loop current mismatch detection When checked, you can enable the detection of a loop current
mismatch between the analog and digital current values from the
HART device.
The slot 0 device code from the The slot 0 device variable code sent digitally from the Analog Output
AO card card. Defines the HART variable whose data is reported by
HART_VAL0.
HART_VAL1.
HART_VAL2.
HART_VAL3.
Enabled HART slot 0 When checked, HART slot 0 is enabled and can be used.
4th Variable Point Name Variable returned by HART transmitter, in Engineering Units. Read
digitally.
Primary Variable Point Name Variable returned by HART transmitter, in Engineering Units. Read
digitally.
Second Variable Point Name Variable returned by HART transmitter, in Engineering Units. Read
digitally.
Tertiary Variable Point Name Variable returned by HART transmitter, in Engineering Units. Read
digitally.
HART Errors
Ignore PV Out out Limits Primary Variable (PV) values that are higher or lower than the
configured limits are ignored when determining PV quality.
Ignore Analog-Digital Mismatch Ignores discrepancy between the current on channel and its digital
equivalent. A mismatch can indicate that current is leaking to ground
even though the circuit appears healthy.
Ignore PV Output Saturated PV values that are output saturated are ignored when determining
PV quality.
Ignore PV Output Fixed PV values that have a fixed output are ignored when determining
PV quality.
Ignore Loss of Digital Comms Ignores loss of digital communication with HART device (loss is
detected after three retries).
Ignore Field Device Malfunction Values determined during a field device malfunction are ignored
when determining quality.
OW351_47 175
4.20.5 Configuring an Analog Input Channel

1. After you have configured the Config tab (see page 168) for an Analog Input channel, use the
Attributes tab to configure an Analog Input Channel.
Figure 103: I/O Channel window (Attributes tab for analog input channel)
I/O Channel attributes for analog input channel
NAMUR alarming When this box is checked, NAMUR alarming is performed on the channel. If enabled
and if the transmitter supports it, any analog value that is outside the NAMUR limits
(106.25% top limit and -2.5% bottom limit) for four seconds has its quality set to BAD.
(NAMUR is an international association of automation technology in process control
industries.)
Analog over range The percent value at which the analog value is considered overrange. Should be used
pct in conjunction with Bad if limited.
Analog under The percent value at which the analog value is considered underrange. Should be
range pct used in conjunction with Bad if limited.
Conversion type Raw data is converted to point values. Indirect is the only type of conversion currently
in use.
Bottom of Scale The low scale value, engineering units code, and number of digits to the right of the
decimal point associated with OUT.
Top of Scale The high scale value, engineering units code, and number of digits to the right of the
decimal point associated with OUT.
Bad if limited When this box is checked, the LSAI algorithm assigned to a given channel propagates
the BAD quality to downstream algorithm if point is outside the configured over/under
range. The quality of point associated with the input channel is not set to BAD.
176 OW351_47
4.21 Ovation Point for SIS Hardware Inputs (Analog/Digital Inputs)
4.21 Ov ation Point for SIS Hardware Inputs ( An alog/ Digital I nputs)
Once the SIS hardware channel is defined, (Refer to: To configure an SIS I/O channel (see page
168)), a corresponding Ovation point needs to be created.

2. Use the system tree to navigate to the Points node under SIS Interface Controller (SIS drop):
Hardware Root
Systems
[System name]
Networks
[Network name]
Unit
[Unit name]
Drops
[Drop name]
Points
3. Right-click the desired Points folder (Analog/Digital).
4. Select Insert New. The Insert New Analog/Digital Points Wizard appears.
Figure 104: Insert New Analog/Digital Points Wizard
5. Enter the Point name in the Point Name Value Field.

6. Select the frequency from the pull-down menu.
 S – Slow (1 second.)
 F – Fast (0.1 second.)
OW351_47 177
 A – Aperiodic (as needed.)

7. Select Finish and the new Analog/Digital Point dialog box appears.
Figure 105: Analog/Digital Point dialog box
8. Select appropriate tab and enter all required information. (Refer to Ovation Developer Studio
User Guide for information about creating points).
9. Make sure that you have selected the suitable hardware in the Hardware tab.
Figure 106: Hardware settings in the Hardware tab
10. Select Apply or Ok button to add the point to the database. If all the required fields have
been completed, the point is added to the database. The point is not available on the Ovation
network until it is loaded.
178 OW351_47
11. After the SIS Interface Controller (SIS drop) is loaded, the point will be available on the
Ovation network under SIS drop. The points also appear in the SIS I/O channels WorkPad
area, as shown in the following figure:
Figure 107: SIS I/O channels WorkPad area
Note: Ovation point with SIS hardware assignment can be used by the LSAI/LSDI algorithms on
the SIS control sheets. Though the Ovation points are used by LSAI/LSDI algorithms, they
cannot be treated as SIS point; these points always considered as Ovation points because they
reside under an SIS drop.
OW351_47 179
4.22 SIS Hardware Outputs (Digital Outputs)
4.22 SIS Hard ware Outputs ( Digit al Outp uts)

To have a point name associated with a digital output signal the point needs to be originated on
the output of an upstream algorithms that is connected to the CASND input of LSDO algorithm.
Refer to the following procedure to assign the OUT parameter to CASND of the LSDO algorithm.
1. Select an appropriate Logic Solver and define the SIS digital output channel (Refer to
Configuring a Digital Output Channel (see page 171))
2. Drag an LSDO algorithm on a control sheet, select the Discrete IO Output Channel field
from the property window of LSDO algorithm, and assign the appropriate SIS hardware
output channel.
Figure 108: Property Editor
3. Connect output from the upstream algorithm to the CASND input of the LSDO algorithm.
Typically, the upstream algorithm is LSCEM and its output is connected to the LSDO CASND
input is EFFx.
180 OW351_47
4. Enter a suitable point name (you can provide a digital output tag name here) in the output
parameter of the upstream algorithm.
Figure 109: Point name entry window
5. Create the point using the Create User Points option of the Control Builder or create the point
manually in the Developer Studio in the Digital Points container under the associated Ovation
Controller.
6. When the SIS control sheet is saved, the point appears in the Developer Studio hierarchy or
will be moved to the SIS Points container under the associated SIS Data Servers.
OW351_47 181
7. The sheet title reference will be reflected for the enabled channel (Digital Output Channel) in
the Workpad area under the SIS I/O Channels folder.
182 OW351_47
8. When the SIS Control Sheet is loaded to the Logic Solver, the point appears in the SIS Points
folder under the SIS Logic Solvers folder.
OW351_47 183
Figure 110: SIS Point folder
Note that the point in the SIS Points under the Logic Solvers folder does not have any hardware
assignment.
Note: Another way to assign an Ovation point to an LSDO algorithm is to create an Ovation
point without hardware assignment in the SIS drop. Assign the Ovation point to algorithm. Put a
pin where the LSDO CASIN_D parameter is connected. After the Control Sheet is saved, the
point appears in the Developer Studio hierarchy in the SIS Points folder under the SIS Data
Servers folder. When the SIS Control Sheet is loaded to the Logic Solver, the point moves to the
SIS Point folder under the Logic Solvers folder.
184 OW351_47
4.23 To configure SIS Control Modules
4.23 T o configure SIS Control M odules
Prerequisites
 Make sure you have added and configured an SIS Network switch (see page 117).
119).
 Make sure you have added an I/O device number (see page 120).
Procedure

2. Select the desired Logic Solver. The four control modules for that Logic Solver appear in the
Studio tree under the Logic Solver.
3. Right-click on the desired control module and select Open. The Control Module dialog (Config
tab) appears.
Figure 111: Control Module window (Config tab)
Control Module attributes for Config tab
Control Module CRC CRC code which reflects the configuration of this control module as calculated by
the Ovation Developer Studio and is compared with the code that is calculated by
the Logic Solver at load time.
User Documentation
OW351_47 185
4.23 To configure SIS Control Modules
Module Name Name of the control module which is contained in the Logic Solver.
Module Number Number of the control module which is contained in the Logic Solver.
Module Revision Revision of the control module which is contained in the Logic Solver.
Diagnostic/Status
Ovation Point Name Enter the point name in the Ovation Point Name field. This point will hold the
status information. Point will be created under the Node Point automatically.
Note: SIF Errors & SIF Alerts are generated only if RN point is assigned to that Control Module.
Figure 112: Control Module window (SIS tab reserved for Emerson use only)
Note: When you attempt to load an SIS Logic Solver (see page 199), a Confirm window
appears that lists all the SIS devices for that Logic Solver that may be affected by the load. The
previous CRC value for each device is listed and the Current CRC value is also listed. The
Current value is the CRC value that the device will change to if you continue with the load
process.
186 OW351_47
4.24 To add an SIS Control Sheet to the SIS Ovation system
4.24 T o add an SIS Control Sheet to th e SIS Ov ation sy ste m
Prerequisites
 Make sure you have added and configured a SIS Network switch (see page 117).
119).
 Make sure you have added an I/O device number (see page 120).
 Make sure you have assigned a Data Server (see page 129) to the SIS I/O device.
Procedure

2. Use the system tree to navigate through the following nodes and their sub nodes to the
Control Sheets:
Hardware Root
Systems
[System name]
Networks
[Network name]
Unit
[Unit name]
Drops
[Drop name]
I/O Devices
SIS Data Servers
[SIS Data Servers name]
SIS Logic Solvers
[Logic Solver name]
Control Modules
[Control Module name]
Control Sheets
OW351_47 187
4.25 SIS Alarming with Logic Solver timestamp
3. Right-click Control Sheets and select Insert New. The Insert New Control Sheets window
appears.
Figure 113: Insert New Control Sheets window
4. Enter the following attributes for the new control sheet.
Insert New Control Sheets attributes
Sheet Name Defines how the sheet is described in the system. This name (up to 30 characters)
appears in the Control Sheets section of the Studio hierarchy.
Sheet Number Short reference number (maximum of three characters). This number is used to
identify the sheet to the user, but is not the unique internal .svg file number that is
assigned by the Control Builder.
Sheet Component Defines the sheet component code. Component codes are text strings that are
assigned to each sheet or supplemental document that represent the sheet's or
document's location in the hierarchy.
5. Select OK. The Ovation Control Builder opens.
6. Draw the desired control scheme and save the sheet. (Refer to the Ovation Control Builder
User Guide for more information.)
4.25 SIS Alarmi ng with Logic S olv er timesta mp
The following sections describe how to configure SIS digital points for alarming with Logic Solver
timestamps.
4.25.1 Configuring Ovation system for SIS alarms

1. Enable millisecond resolution point processing:
a) Use the Ovation Developer Studio system tree to navigate to the Point Processing item:
System (or appropriate level such as Network, Unit, or Drop)
Configuration
Point Processing
188 OW351_47
b) Insert new configuration.

c) Enable Millisecond resolution option.
Figure 114: Millisecond resolution point processing settings
Note: Point Processing configuration from lower level overrides configuration from higher levels
(for example, Unit configuration takes precedence over System configuration).
2. Configure timestamps display for alarms:

a) Use the Ovation Developer Studio system tree to navigate to the Alarm item:
System (or appropriate level such as Network, Unit, or Drop)
Configuration
Alarm
b) Right-click on the Alarm item and click Open. The Alarm window appears.
c) Scroll to select the Alarm Display tab by using the scroll bar.
d) Select Yes for the Show Millisecond Resolution field, and 100 Milliseconds for the
Millisecond Format field. All points under this setting in the tree will now contain these
settings for timestamps.
OW351_47 189
Figure 115: New alarm attribute settings

3. Download the changes to the drop and reboot the drop for the changes to take effect.
4.25.2 Configuring an alarm for SIS digital point

1. Create an Ovation point. (See Ovation Developer Studio User Guide for information about
adding a point.)
2. Open the point properties window. Click the Point tab, and set the OPP rate to U (User
defined).
Note: Point alarm will be displayed in Alarm Application only when the point’s characteristics
field is set; otherwise, Point alarm will not be displayed in the Alarm Application. (Refer to
Ovation Developer Studio User Guide for information about Building Points).
3. Click the Config tab and enable alarming.
190 OW351_47
4. To make a new point an SIS point, open the Control Builder and use the point on an SIS
Control Sheet. Save the control sheet. (Refer to the Ovation Control Builder User Guide for
more information.)
5. Access the Ovation Developer Studio hierarchy tree. The point now appears in the SIS Points
folder under the SIS Data Servers folder.
6. Load the Control Sheet to the Logic Solver.
7. The point now appears in the SIS Points folder under the Logic Solvers folder.
4.25.3 SIS Sensor Alarms
Logic Solver Sensor Alarms provide sensor alarms functionality for Digital input, Analog input, and
HART analog input channels of the Logic Solver. Those alarms have timestamps originated on
the Logic Solver.
Sensor alarms functionality is enabled per the Logic Solver. Perform the following steps to enable
it:
1. Navigate to one of Control Modules of a given Logic Solver.
OW351_47 191
2. Insert a new control sheet. Use ALRM as the sheet number. Its name can be custom.
Figure 116: New Control Sheets

3. Save the empty sheet.
4. To trigger a sensor alarm on a specific channel, the following options need to be configured:
a) For digital inputs, select the Detect open and short circuit check box. The Sensor alarm
will appear if there is an open or short circuit in the digital input loop (use of End of
Line Resistance module is required).
Figure 117: Attributes settings window for digital input
192 OW351_47
b) For analog inputs, the Bad if limited check box can be checked optionally. This setting
determines when sensor alarm should be generated. If it is set, the sensor alarm is
generated when the value of the channel is underrange/overrange. Otherwise, exceeding
the limits by -20% at bottom of the scale and 116.6% at top of the scale causes sensor
alarm.
Figure 118: Attributes settings window for analog input
OW351_47 193
c) For HART analog inputs, the Bad if limited check box can be selected optionally. Setting
this option has the same effect as for the analog channels. Additionally, the sensor alarm
can be generated when a HART error condition occurs (HART transmitter needs to
support this functionality). This behavior can be changed by selecting the check boxes in
the HART Errors section (for example, Ignore PV Out of Limits).
Figure 119: Attributes settings window for HART analog input
194 OW351_47
4.26 To view SIS points
5. Load the Logic Solver and SIS Controller. The ALRM sheet will be automatically filled with
logic required for the sensor alarms generation.
Figure 120: ALRM sheet
Note: Do not manually modify the ALRM sheet. It is regenerated on each Logic Solver load;
therefore, any changes made on it are discarded. However, you have to remove the previously
configured input channel. The LSDI or LSAI algorithm that references the input channel that is
being removed has to be deleted manually from the ALRM sheet.
To disable sensor alarms, the ALRM sheet should be removed. On the next load, it will not be
regenerated.
Logic for sensor alarms generation consists of one input algorithm (LSDI or LSAI) per configured
input channel and one LSCALC algorithm. The number of algorithms per Control Module is limited
to 127; therefore, using the sensor alarms functionality decreases the maximum number of
algorithms available for you.
Bad Quality is set for the channels that are in the Sensor Alarm.
Note: After removing the ALRM sheet, clear the SIS Interface Controller.
4.26 T o v iew SIS points
SIS points will appear in the WorkPad section of the Studio interface after the applicable Logic
Solver has been successfully loaded. When the Logic Solver is loaded, the points will move from
the parent SIS Data Server to the Logic Solver.
Procedure
1. Use the system tree to navigate to the SIS Points:
Hardware Root
OW351_47 195
4.26 To view SIS points
Systems
[System name]
Networks
[Network name]
Drops
[Drop name]
I/O Devices
SIS Data Servers
[SIS Data Server name]
SIS Points
2. Click on the applicable point’s icon (Analog, Digital, or Algorithm) and any points that have
been loaded into the parent Logic Solver display in the WorkPad section.
Figure 121: SIS points in the Ovation Developer Studio hierarchy
196 OW351_47
4.27 Removing or Deleting an SIS Point
4.27 Remov ing or Del eting an SIS Point

There are several steps be able to delete an SIS Point. An SIS Point cannot be deleted if it is in
any of the SIS folders. The point must be moved out of the SIS folder and into the correct path
under the appropriate Controller. Moving the point can only be accomplished with a point that is in
the SIS Data Server and is not referenced by any SIS object. To delete an SIS Point, you need to
perform either of these tasks:
1. Remove the SIS Point from the Control Sheet (see page 197).
2. Delete the SIS Point (see page 197).
4.27.1 To remove an SIS Point from the SIS Control Sheets
If you want to remove an SIS point from its SIS Control status, you can perform this through the
Ovation Control Builder:
1. Access the Ovation Control Builder (refer to Ovation Control Builder User Guide for details).
2. Open the control sheet that contains the SIS Point that you want to remove.
3. Remove the desired SIS points and save the sheet.
4. Load the Logic Solver that contains the sheet. The point will move from the SIS points folder
under the Logic Solver to the SIS Points folder under the SIS Data Server folder. This
indicates that the Point is no longer used as a SIS point in the SIS control scheme.
4.27.2 To delete an SIS Point

2. Use the system tree to navigate to the SIS folders.
3. Navigate the SIS folders to locate the appropriate SIS Point to be deleted.
 If the Point is in the SIS Point node under the SIS Data Server, and is not in the SIS Logic
Solver hierarchy, go to Step 7.
 If the Point is in the SIS Point node under the SIS Logic Solver hierarchy continue with
Step 4.
4. Perform a Where Used function (see the Ovation Developer Studio) to check for any
references to control sheets.
5. Remove all Control Sheet references to the SIS Point using the Control Builder, see To
remove an SIS Point from the SIS Control Sheets (see page 197).
6. Continue Step 5 until the SIS Point is reference free, the SIS Point will be moved from the SIS
Logic Solver to the SIS Data Server hierarchy.
7. Drag and drop the SIS Point from the SIS Point folder under the SIS Data Server folder to the
appropriate Controller folder.
8. The Point can then be deleted using the Right-click menu.
OW351_47 197
S E C T I O N 5
5 Using Ovation SIS
IN THIS SECTION
Loading Logic Solvers ................................................................................................. 199

Using Point Information (PI) to identify SIS points ........................................................ 201
Viewing SIS Tuning windows for SIS algorithms .......................................................... 203
Forcing an algorithm input value .................................................................................. 205
Bypasses and overrides .............................................................................................. 217
Making online scaling changes in HART transmitters ................................................... 220
Restarting a Logic Solver ............................................................................................ 221
Requiring a reset before outputs can become energized ............................................. 223
Configuring the Logic Solver's response to detected faults........................................... 223
Choosing the Logic Solver scan rate ........................................................................... 228
Loading to a running process ...................................................................................... 228
Restarting a Logic Solver after a power failure ............................................................. 229
System Administration functions .................................................................................. 229
Proof Testing the Logic Solver..................................................................................... 230
Customizing Ovation Control Builder frame ................................................................. 232
Upgrading SIS firmware .............................................................................................. 232
Using Fault Codes for SIS ........................................................................................... 236
SIS Node Point (RN Point) .......................................................................................... 239
SIS Events .................................................................................................................. 242
5.1 Loading Log ic Solv ers

Logic Solvers contain the SIS logic solving capability and provide an interface to 16 I/O channels.
To update the logic solving of safety applications, load a new or edited logic into the Logic Solver.
5.1.1 To load an SIS Logic Solver
Prerequisites
 Make sure you have SIS load privileges.
Procedure
All loads to Logic Solvers are total loads. Incremental loads are not allowed and you cannot load
multiple Logic Solvers at the same time.
Note: After loading the Logic Solver, the SIS Interface Controller updates the information from
the SIS Data Server. This results in a delay of a few seconds, which keeps nonsecure
parameters in bad quality.
OW351_47 199
5.1 Loading Logic Solvers
Solvers:
Hardware Root
Systems
[System name]
Networks
[Network name]
Units
[Unit name]
Drops
[Drop name]
I/O Devices
SIS Data Servers
[SDS name]
SIS Logic Solvers
3. Select the Logic Solver you want to load.
4. If the Logic Solver is locked, right-click and select Unlock. A confirmation dialog window
appears.
5. On the confirmation dialog, click Confirm to unlock the Logic Solver.
Note: Locking or unlocking a Logic Solver generates a SIS event that is sent to Ovation
Historian.
6. Right-click and select Load.

7. A Confirm window appears listing the Previous CRC codes and Current CRC codes of the
Logic Solver, the four Control Modules, and the I/O channels.
The Previous CRC values are the codes of the object before you perform a load to the Logic
Solver.
The Current CRC values are the codes that the object will have after you perform a load to
the Logic Solver.
If you select Yes to continue the load function, new CRC values for any objects that will
change will appear in the Current CRC column and there will be an asterisk (*) in front of the
device.
200 OW351_47
5.2 Using Point Information (PI) to identify SIS points
Notice in the following Confirm window that there are asterisks in front of the I/O Channels
that have changed after the Logic Solver was loaded.
Figure 122: Logic Solver Confirm window
5.2 Using Point Informatio n (PI) to identify SIS points

You can use the Point Information window to locate SIS points in a system and to determine if a
point is a SIS point. The Point Information window provides the following information about a
selected point (refer to the Ovation Operator Station User Guide for additional information about
the Point Information function):
 The point name (PN record field) displays at the top of the window. All points in the Ovation
system are fully specified by three parameters:
 Point name
 24-character maximum for Windows systems.
 Six-character maximum sub-network (unit) name.
 Eight-character maximum network name.
OW351_47 201
5.2 Using Point Information (PI) to identify SIS points
The fully qualified name is of the format “name. unit@network.” The (.) and @ are
reserved characters for point names.
 The description, point value, quality, and engineering units for analog points display below
the point name.
 The point attributes display by selecting the applicable tabs.
 The point record field that corresponds to the parameter name is listed beside the
parameter. A point record stores the information which defines the attributes of a point. 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. (Refer to the Ovation Record Types
Reference Manual for additional information about point records.)
 The point information displayed in the lower portion of the window displays using a folder
format. The tabs are labeled and the information related to the tab label displays below when
the tab is selected. When a valid point name is entered, information for the point displays for
the first tab, the Point tab.
 The SIS Indication (KC) field identifies if a point is a SIS point.
 The action buttons Cancel and Apply are active only when a tab with modifiable data is
selected.
 Last Active Instance (LAI) - displays in the right bottom corner of the window. This identifies
the Point Information window that is currently active.
Note: Value and status fields update once every second. The remaining point attributes update
once every three seconds. Point Information requests a one-shot every three seconds to make
sure it has the latest static data.
5.2.1 To use Point Information to identify SIS points
Prerequisites
 Make sure that the Ovation point exists and is in the database.
Procedure
1. Open the Ovation Applications folder at the Operator Station and double-click on the Point
Information icon.
OR
If the Point Information application is already running, double click on the PI icon located on
the system tray.
OR
Select Start -> Ovation -> Ovation Applications -> Point Information.
The Point Information window appears.
2. If you know the name of the desired point, type in the name and press Enter. The Point
Information window appears for that point.
3. If you do not know the name of the desired point, click the Search button in the Point
Information window or select from the File pull-down menu. The Find Points window appears.
4. Select the appropriate network, unit, and drop. A scrolling list of all the points for that drop
appears. To discontinue or change the search, click the Abort Search button.
202 OW351_47
5.3 Viewing SIS Tuning windows for SIS algorithms
5. Double click on the desired point name in the list or select the point and click the Apply
button. The Point Information window appears for that point.
6. Select the Configuration tab.
Figure 123: Point Information window (Configuration tab)
7. Check the SIS Indication field at the bottom of the window. If the point is a SIS point, the
value will be 1 or greater. If the point is not a SIS point, the value will be zero (0).
5.3 Viewing SIS T uning windo ws for SIS algorithms
SIS algorithms can be viewed and tuned through an SIS Tuning window in the Signal Diagram
application.
All of the SIS algorithms have SIS Tuning windows. If the SIS algorithm has tunable parameters,
they are tuned through the SIS Tuning window -- not through the Property Summary window. If
the SIS algorithm does not have tunable parameters, the tunable column in the SIS Tuning
window appears blank.
For certain SIS algorithms, the SIS Tuning window has an extra tab. The information in this tab is
read-only, and contains the information that was entered in the advanced editing window in the
Control Builder. The algorithm that has the extra tab is:
 LSCEM (see page 204).
Note: For more information on the SIS algorithms, refer to Ovation Algorithms Reference
Manual.
OW351_47 203
5.3 Viewing SIS Tuning windows for SIS algorithms
5.3.1 To access the SIS Tuning window for SIS algorithms
To access the SIS Tuning window for SIS algorithms, follow the steps below:
1. Access the Signal Diagram window.

2. Select a sheet from the Open Document window.
3. The sheet appears on the display canvas. Right-click the desired SIS algorithm on the sheet.
Select Advanced Tuning from the menu that appears.
The SIS Tuning window applicable to that algorithm displays.
5.3.2 SIS Tuning window for the LSCEM algorithm
Figure 124: LSCEM SIS Tuning window (Properties Summary tab)
204 OW351_47
5.4 Forcing an algorithm input value
Figure 125: LSCEM SIS Tuning window (Cause and Effect Table tab)
5.4 Forcing an a lgorithm input v alue
An SIS Force operation occurs when an SIS algorithm input parameter value or quality is
changed manually. This means the input is "forced."
For example, you might want to see the behavior of an SIS algorithm when it has a certain input
value or quality; however, the SIS algorithm might not currently have the input value or quality you
need. You can use a Signal Diagram (see page 206) to temporarily force the input value or quality
of the SIS algorithm in order to observe the behavior.
You cannot force the output of an SIS algorithm to a particular value or quality; you can only force
the input to a particular value or quality. Before you can force an input value or quality for an SIS
algorithm, you must turn on the Control Module Debug mode.
Debug mode is where you can perform functional testing of safety logic by forcing input values for
algorithms (see page 206).
After you have forced an input value or quality, a blocking icon will appear at the end of the forced
input pin of the algorithm in the Signal Diagram. This icon also appears next to the current value
in the Algorithm Summary window. This icon illustrates that the value or quality for the input signal
is currently forced and cannot be updated by the system.
Note: Remember to remove the forced input value when you want the SIS algorithm to execute
normally.
OW351_47 205
WARNING! Be sure to turn OFF the Debug mode before closing the signal diagram. Failure to
do so may result in unsafe conditions.
5.4.1 To force an algorithm input value
Prerequisites
 Make sure that the applicable Control Sheet has been successfully loaded into the SIS
Interface Controller and the Logic Solver.
Procedure
1. Access the Signal Diagram application:

 From the Operator Station Ovation Applications icons or from a Point Menu.
OR
 From the Control Builder. Refer to Ovation Control Builder User Guide for more
information.
2. Navigate to a sheet in the Open Document window. Refer to Ovation Control Builder User
Guide for more information.
3. Double-click the sheet and the sheet appears on the display canvas of the Signal Diagram
window.
4. Right-click the desired algorithm on the sheet and select Advanced Tuning from the menu.
The SIS Tuning window appears with the selected algorithm name at the top of the window.
The following steps provide an example of how to use the SIS Force function.
Figure 126: SIS Tuning window
206 OW351_47
5. Click the Force button. The Force application window for the selected algorithm appears. The
following window displays when the Control Module with selected algorithm is not in Debug
mode
Figure 127: Force application window in Normal mode
6. If Control Module is in Normal mode, click the Debug ON button and continue to Step 7. If the
Control Module is in Debug mode, skip to Step 9.
Notes: When you turn on the Debug mode, you set the Debug mode for the entire Control
module and all of the SIS Control Sheets in that module.
If bit 9 of the Logic Solver RN point is set, it indicates that Debug mode is ON for any Control
module of that Logic Solver. Control module RN point bit 1 will also indicate that the Control
Module Debug mode is ON.
Turing ON the Debug mode will generate a SIS Event that is sent to Ovation Historian.
7. A window appears asking you to confirm Debug mode selection. Select Confirm. (The SIS
Write function checks to verify that the process is valid.)
Figure 128: Control module Debug ON confirm window
Note: If you do not confirm SIS secure write selection for a few seconds, the command confirm
timeout dialog box appears.
OW351_47 207
8. The Force application window now displays that the Control module for the selected algorithm
is in Debug mode.
Figure 129: Force application window in Debug mode
208 OW351_47
9. Once in Debug mode, select the input pin you want to force from the list on the left side of
the Force application window and click the Set button. See the following figure.
Figure 130: Force application window -- select input pin
Force application window fields and buttons
FIELD D E S C RIP T IO N
Debug ON Use to enter the Debug Mode.

Debug OFF Use to exit the Debug Mode.
Force Inputs
Algorithm Input Lists all of the algorithm pins whose values can be forced with their actual states.
Pins list Forced pins are marked with a warning icon in the left column of the list.
Forced Value Displays the value to which the pin, if forced, is applicable.
Pin Name of pin whose value is being forced.
OW351_47 209
FIELD D E S C RIP T IO N
Set button Sets a new forced value for the pin (appears only when one of the algorithm input pins
is selected).
Clear button Clears or removes the forced value from the pin (appears only when one of the
algorithm input pins is selected).
Change value to Enter the value to which you want to force the pin (appears only when one of the
entry field algorithm input pins is selected).
Change quality to Select quality to force the pin (appears only when one of the algorithm input pins is
entry field selected).
Force button Use this button to change the value and quality of the algorithm input.
Dismiss Use this button to close the current force window.
10. A window appears asking you to confirm that you want to confirm the selected pin. Click
Confirm. (The SIS Write function checks to verify that the process is valid.)
Figure 131: Force Input Confirm window
210 OW351_47
11. The Force application window now shows the forced pin with the warning icon in the
Algorithm Input Pins list.
Figure 132: Force application window showing forced pin and warning icon
Note: A blocking icon appears at the end of the forced input pin of the SIS algorithm in the
Signal Diagram application. This icon also appears next to the current value in the Algorithm
Summary window. This icon illustrates that the value and quality for the input signal is currently
forced and cannot be updated by the system.
12. After you have forced the pin value, do one of the following:
 Set a new forced value and quality for the pin (see page 212).
 Clear the forced value and leave Debug Mode (see page 215).
Refer to Ovation Safety Instrumented System (SIS) User Guide for information on setting and
clearing forced values.
OW351_47 211
5.4.2 To set a new forced SIS algorithm input value and quality
1. To set a new forced value and quality for a pin whose value is already forced, perform the
following in the Force application window:
a) Select one of the forced pins from the Algorithm Input Pins list.
b) For analog inputs, enter the value manually in the "Change value to" field. However, for
digital inputs, you will have to select either a TRUE or FALSE value. The "i" icon, which
appears between the Change quality to field and the Force button, shows that the entered
value is a valid floating point number.
Figure 133: Force Analog Input – change value and quality
212 OW351_47
Figure 134: Force Digital Input – change value and quality
c) Select a quality of GOOD or BAD and click the Force button.
OW351_47 213
2. A window appears asking you to confirm that you want to force the value and quality of the
selected pin. Click Confirm. (The SIS Write function checks to verify that the process is valid.)
Figure 135: Changed forced value and quality confirm window
3. The Force application window now appears showing the new forced value in the Algorithm
Input Pin list.
A BAD forced quality is indicated by letter "B" with the value. However, there will be no
indication if the forced quality is GOOD. Now, clear the force (see page 215) or set a new
forced value again.
214 OW351_47
Figure 136: Force application window updated with new forced value and quality
Note: In the LSDI and LSAI algorithms, the quality force feature is not applicable.
5.4.3 To clear the force value and leave Debug mode

1. To clear the forced value for a pin, perform the following in the Force application window:
a) Select the pin.
b) Click the Clear button.
Note: If Debug Mode is OFF, all forced inputs from the sheets under that Control module will be
cleared.
OW351_47 215
2. A window appears to confirm the clear of the forced input of the selected pin. Click Confirm.
(SIS Write function checks to verify that the process is valid.)
Figure 137: Cleared forced input confirm window
3. Emerson recommends that you leave Debug mode when you are finished with the forcing
tasks. To perform this:
a) Click the Debug OFF button in the Force application window.
Figure 138: Force application window – select Debug OFF
216 OW351_47
5.5 Bypasses and overrides
b) A window appears asking you to confirm that you want the Debug mode switch OFF.
Click Confirm. (The SIS Write function checks to verify that the process if valid.)
Figure 139: Debug OFF confirm window
c) The Force application window shows that the Control module is in Normal mode.
Figure 140: Force application window in Normal mode
5.5 By pass es and ov errides
It is often necessary to maintain an output value during plant startup to prevent a trip caused by
inputs that have not yet stabilized to their normal operating values. You may also want to bypass
inputs to allow for sensor maintenance.
Ovation SIS has built-in capability for creating applications that follow guidelines set forth in the
IEC 61511 standards. Ovation SIS does not limit you to using its built-in bypass capability. You
are free to create Custom logic and interfaces for this purpose.
The following subsections describe the built-in bypass capability in Ovation SIS.
OW351_47 217
5.5.1 Override types
Maintenance bypass
During a maintenance activity such as calibration, proof testing, or repair of a transmitter, a

maintenance bypass temporarily prevents the process value on the input channel from
contributing to a potential trip. The Analog Voter (LSAVTR) and Digital Voter (LSDVTR)
algorithms provide the built-in maintenance bypass capability. When an individual input is
bypassed for maintenance, its vote to trip is not considered in voting logic. A maintenance bypass
is set and cleared by an operator or maintenance technician using an SIS Write operation from a
workstation or a physical key switch, but the bypass could be cleared by the voter algorithm itself
based upon a configurable timeout.
Startup bypass
While a process is starting up, a startup bypass temporarily overrides a process value to allow
time for it to reach a value that does not initiate a trip. The Analog Voter and Digital Voter
algorithms provide the built-in startup bypass capability. The algorithm output maintains the
normal operating value while the startup bypass is active. A startup bypass is initiated by an
operator using an SIS Write operation or by the voter algorithm detecting a process startup
condition. The startup bypass is cleared after a configurable time period or optionally when the
voter algorithm detects a process condition.
Parameter force
This override uses Control Module Debug mode to force an input parameter on an algorithm
diagram to have a value other than the source value. The use of parameter forces is intended for
functional testing, not when the SIF is providing its protection function unsupervised.
5.5.2 Configuration of bypasses
The configurer of SIS module logic uses the BOPn (Bypass Opt n) parameters in the voter
algorithms to determine which maintenance and startup bypass options apply for the algorithm
usage. Refer to the Analog Voter and Digital Voter algorithms topics for details on the available
bypass options.
The configurer must provide a means to annunciate to the operator when a maintenance bypass
condition is active. There is no built-in capability is available in Ovation SIS to annunciate to the
operator when a maintenance bypass condition is active. This type of annunciation can be done
by creating RN point for Control Module. If bypass is active, the bit 12 of RN point will be set and
point will be alarmed. Several other conditions can cause this bit to be set. To check if alarm was
caused by active bypass look for SIF Alert events in Ovation Process Historian.
The ability to set and clear maintenance bypasses in voter algorithms at runtime can be
configured using macros for the voter algorithms and can be used in Ovation Graphics.
5.5.3 Operation of bypasses
A Maintenance bypass is typically used in either of two situations.
1. There is a planned maintenance activity on a transmitter or other sensor. A single input is

bypassed to prevent that input from causing a spurious trip during the activity.
218 OW351_47
2. A failure occurs in a transmitter, the field wiring, or the input circuitry of the Logic Solver
during normal operation. A maintenance bypass is used to prevent BAD quality from causing
a trip in the output algorithm (if the failure itself did not already cause a trip).
The bypass is set from Ovation Graphics, for example, by clicking on an input check box of the
voter algorithm macro and then confirming the selection. A set bypass is cleared using the same
procedure. While the bypass is set.
Operators should be aware of all alarms visible on this display. The handoff at shift change should
include a review of the Alarms. You can create other alarms related to bypasses by referencing
alarm conditions determined in the voter algorithms. These alarms include a reminder that the
expiration of a bypass is imminent and whether a bypassed input is voting to trip.
The history of bypass activity is available in the historian. An entry is also created whenever the
algorithm removes a bypass due to timeout.
Maintenance bypass example
The Failure
A HART transmitter fails, resulting in a Field Device Malfunction HART error and a down-scale
output value as configured in the device.
How the Logic Responds
Bad quality enters the Control Module logic in the Logic Solver because the input channel was
configured to not ignore the Field Device Malfunction error. The Analog Voter algorithm in the
Control Module sheets has a “Greater Than” input detection type (DTYPE) and a 1oo1 voting
arrangement. Bad quality propagates through the voter algorithm, but the down-scale value does
not cause a trip value on the output of the algorithm. Bad quality continues to propagate through
the LSCEM algorithm and causes the fault state timer to start in the Digital Output algorithm, but
no trip occurs on the output.
How the Operator Responds
BAD quality has caused an Input bad alarm in the Control module logic to become active and
appear on the alarm application. The operator opens the respective display. The operator
assesses the impact of the failure by looking at the display, which was created with algorithm
macros. It is clear that a trip has not occurred, but the operator sees on the DO algorithm macro
that the fault state timer value is incrementing and sees the time value at which the output
algorithm initiates a trip.
The operator clicks the bypass check box for the transmitter and confirms the “set bypass.” The
fault state timer stops incrementing and retains its value. The operator initiates the repair activity
for the transmitter, knowing that manual supervision of the SIF is necessary while t he bypass is
active because the Logic Solver is not able to respond to a demand if one occurs. Manual
supervision implies that a local measurement is available for the process value and the operator
can be notified if a demand occurs and has a means to manually initiate a trip.
There are several variations to this scenario to consider.
1. Suppose the voting arrangement is 1oo2. In this case the BAD quality does not propagate.
Manual supervision is not necessary. The SIF is still able to respond to a demand based on
the other transmitter. The operator bypasses the BAD input so a trip does not occur when the
transmitter is replaced.
OW351_47 219
5.6 Making online scaling changes in HART transmitters
2. Suppose the voting is 2oo3. In this case the operator merely follows up on repair for the
transmitter. No maintenance bypass is needed. The other two transmitters are providing the
protection and there is no concern that a trip might occur when the transmitter is replaced.
3. Suppose the transmitter failure results in an up-scale output value. With a 1oo1 or 1oo2
voting arrangement, a false trip occurs. A 2oo3 voting arrangement has the same result as a
down-scale output value. But, 2oo2 voting starts the fault state timer in the output algorithm
because there are not enough good inputs to ensure a proper response to a potential
demand.
Whenever BAD quality enters a Control Module and a determination is made that a repair is
required, the repair should be completed within the allowed repair time for the SIF. This helps to
prevent the PFDavg or PFH from exceeding the SIL verification value.
5.6 M aking online scalin g cha nges i n HART transmitters

A special procedure is recommended if you need to make an online change to the upper or lower
range value in a HART transmitter connected to a channel of the Logic Solver. The Logic Solver
does not automatically synchronize the scaling between the HART device and the associated
analog input channel. Scaling must be configured independently.
The scaling is set using the Top of Scale and Bottom of Scale attributes of HART Analog Input
Channel of the Logic Solver. Loading the Logic Solver or changing the scaling in the HART
analog input channel attributes at runtime does not affect scaling in the HART device. To change
the scaling in the HART device, you must use AMS or a HART Communicator. Similarly,
changing the upper or lower range value in the HART device does not cause a change to Top of
Scale and Bottom of Scale attributes of HART analog input channels of the Logic Solver.
If an online scaling change is made in the HART device, there is a step change in the OUT
parameter of the associated LSAI algorithm, and the value is incorrect until an equivalent manual
change is made to the scaling parameters of the HART analog input channel. When making
online scaling changes, a standard procedure should be followed to prevent spurious trips and to
ensure that matching scaling is achieved. The recommended procedure is as follows:
1. Bypass the LSAVTR algorithm input wired from the OUT parameter of the LSAI algorithm
assigned to the HART device’s channel using the LSAVTR macro on the display. If the
TRSTS parameter of the LSAVTR algorithm becomes “Trip Inhibited” as a result of the
bypass, manually monitor the SIF while the input is bypassed.
2. Make the scaling change in the HART transmitter using AMS.
3. Change the Top of Scale and Bottom of Scale attributes of Logic Solver analog input channel
and load the associated Logic Solver.
4. Check to see that the OUT parameter of the LSAI algorithm has the expected online
engineering unit value.
5. Remove the bypass.
220 OW351_47
5.7 Restarting a Logic Solver
5.7 Restarting a Logi c Solv er

The Ovation SIS system supports redundant Logic Solvers. A redundant Logic Solver consists of
a pair of Logic Solvers mounted in adjacent carrier slots with a redundant terminal block. Each
Logic Solver is powered separately. The Logic Solvers contain the same configuration and run the
same logic.
If you have a redundant Logic Solver configuration, you might need to do one of the following
actions to a redundant Logic Solver:
 Restart the active Logic Solver.
 Restart the standby Logic Solver.
 Switch the active Logic Solver to the standby mode, and the standby Logic Solver to the
active mode.
Note: If you must restart a simplex Logic Solver online, such as for proof testing, you need to
temporarily bypass or block final elements and provide manual supervision.
5.7.1 To restart (reboot) a Logic Solver

Solvers folder:
Hardware Root
Systems
[System name]
Networks
[Network name]
Units
[Unit name]
Drops
[Drop name]
I/O Devices
SIS Data Servers
[SDS name]
SIS Logic Solvers
[Logic Solver name]
OW351_47 221
5.7 Restarting a Logic Solver
3. Right-click on the Logic Solver you want to restart and select Reboot. A Restart Wizard
appears.
Figure 141: Restart Logic Solver Wizard
4. Select the desired action:

 Force Restart Active = Restarts the active Logic Solver.
 Force Restart Standby = Restarts the standby Logic Solver.
 Switchover = Switches the active Logic Solver to standby, and the standby becomes the
active Logic Solver.
5. Select the Finish button. A confirmation dialog window appears.
6. On the confirmation dialog, click Confirm to restart the selected Logic Solver or to switch the
active Logic Solver to standby, and the standby Logic Solver to active.
222 OW351_47
5.8 Requiring a reset before outputs can become energized
5.8 Requiring a res et before output s can beco me e nergiz e d

The configuration of Control Module logic determines which conditions allow de-energized output
channels of the Logic Solver to become energized.
It is generally desirable to require an operator reset of the Logic Solver before the equipment
under control is allowed to go from a shutdown or tripped state to the normal operating state.
However, in some cases, the output channels should be allowed to change from de-energized to
energized based on input channel values without operator intervention, for example, as soon as
an interlock condition clears.
Ovation SIS algorithms provide an easy way to configure Control Module logic to either require or
not require an operator reset before applicable output channels can become energized.
There are certain situations where a powered Logic Solver keeps output channels de-energized
independent of Control Module logic. When the Logic Solver is going through power-up testing
following a reset or restart, has detected a persistent fatal error, or is in an unconfigured state,
output channels remain de-energized. Otherwise, Control Module logic determines the output
channel state.
The recommended technique for requiring an operator reset is to use the Cause Effect Matrix
(LSCEM) algorithm. It has an RRSn (required reset) parameter for each extensible EFFn (output
effect) output of the algorithm. Each EFFn output is connected to one or more output algorithms,
which are bound to output channels. When RRSn is True (the default value), the EFFn output
cannot transition from 0 to 1 unless STAn (current state) is “Ready to Reset” and RSTn (reset)
has been changed to True, typically by an SIS Write from an Ovation Operator station. When
RRSn is False, EFFn can transition from 0 to 1 when associated CSn (input cause) have become
inactive and other permissives are satisfied, without a reset.
The “require reset” option is also available in the two output algorithms (for example, LSDO &
LSDVC); however, it should be used only if there is no LSCEM algorithm in upstream Control
Module logic.
5.9 Configuring the Logi c Solv er's respons e to dete cted fa ults
It is important to consider the quality of the input and output channels of the Logic Solver, as BAD
quality may indicate a problem that must be addressed. The following topics are described below:
 Detecting faults on input channels (see page 224).
 Detecting faults on output channels (see page 227).
OW351_47 223
5.9 Configuring the Logic Solver's response to detected faults
5.9.1 Detecting faults on input channels
Faults detected by the Logic Solver on input channels can originate in field devices, field wiring, or
in the Logic Solver input circuitry.
The Logic Solver responds to faults detected on input channels by integrating BAD quality with
the channel value and annunciating the fault.
The Logic Solver does not automatically de-energize output channels when faults are detected on
input channels. Control Module logic must be configured to take action based on the requirements
of the application. For example, you may want to prevent a trip from occurring in the presence of
a fault on an input channel, or cause a trip immediately when a fault is detected, or initially
prevent a trip yet cause a trip some time later if the fault persists. SIS algorithms contain
parameters to facilitate the configuration of these options.
Handling BAD quality on analog input channels
An analog input channel (see page 176) always has BAD status when the measured current is
outside the sensor failure limits, 0.78 mA (-20.12%) and 22.66 mA (116.6%). The limits can be
exceeded due to faults in the transmitter, field wiring, or the Logic Solver. You can also cause the
channel to have BAD quality when the current reaches a value inside the sensor failure limits.
Changing the "Enable NAMUR alarming" channel parameter to True enables NAMUR limit
detection, which results in BAD quality being applied when the current is greater than 21.0 mA
(106.25%) or less than 3.6 mA (-2.5%) for four consecutive seconds.
When the channel value exceeds the channel’s configured "Analog over range pct" or "Analog
under range pct," and "BAD if Limited" option is set for analog channel, the LSAI algorithm that
references the given channel applies BAD status to its PV and OUT parameters.
The HART Analog Input channel’s (see page 172) HART related error parameters allow you to
select which HART diagnostic conditions detected in the HART transmitter or by the Logic Solver
cause BAD quality to be integrated with the analog value on the channel (the "BAD if Limited"
channel parameter). The default value of these parameters is to ignore all HART diagnostic
errors, meaning the presence of an error condition does not cause BAD quality on the channel. If
you deselect “Ignore Field Device Malfunction,” for example, the channel has BAD quality if the
transmitter reports a device malfunction, allowing this HART diagnostic to be integrated with your
Control Module logic.
224 OW351_47
Handling BAD quality on digital input channels
Faults detected on digital input channels (see page 170) by the Logic Solver result in BAD quality
on the channel. The Logic Solver detects open and short circuits in field wiring if line fault
detection has been enabled on the channel using the "Detect open and short circuit" parameter.
When line fault detection is enabled, you must use a NAMUR sensor or install end of line resistors
in series and parallel. An open or short detected through line fault detection results in BAD quality
on the channel.
Line fault detection is required when the field switch is normally open, that is, when the channel is
On to indicate a demand.
Line fault detection is recommended when the field switch is normally closed, that is, when the
channel is Off to indicate a demand. If an open circuit occurs in the field wiring, it is a safe failure
whether or not line fault detection has been enabled. But a short in the field can be a dangerous
failure and be undetected, unless line fault is enabled, in which case the channel has BAD status.
Using BAD quality in Control Modules
Two algorithms are available in Control Modules to manipulate output channels: the Digital Output
(LSDO) algorithm and the Digital Valve Controller (LSDVC) algorithm. Each has a CASND input
parameter whose value is the commanded state for the output channel, which is connected from
upstream logic in the Control Module. When the quality of CASND changes to BAD, the algorithm
starts a timer whose value is stored in the FTMR (fault detection timer) parameter. If and when
the timer reaches the configured FTIM (fault detection delay) value, the algorithm enters the fault
state if theFOP2 (Enable detection based on CASND status) option is enabled. The algorithm
drives the output channel Off when it is in the fault state.
SIS algorithms have a predetermined way of propagating the quality of input parameters to output
parameters. Faults detected on input channels cause BAD quality to reach output algorithms in
Control Modules depending on the configuration of other algorithms in the Control Module.
The configured value of FTIM in output algorithms determines how long quality can be BAD
before the output algorithm initiates a trip. The default value is 300 seconds, which gives enough
time for operators to bypass a BAD input and take corrective action before a trip is initiated. Use
an appropriate value for FTIM in each output algorithm. Some SIFs (see page 6) can tolerate a
high number corresponding to your allowed repair time, while other SIFs may require a low
number of just a few seconds.
The following figure illustrates the use of common SIS algorithms to create shutdown logic in a
Control Module. The quality on the output parameter of the input algorithms, LSAI and LSDI, is
the quality of the referenced input channel. The Analog Voter (LSAVTR) and Digital Voter
(LSDVTR) algorithms propagate BAD quality on input parameters selectively. For example, if a
single input of a 1oo2 (1 out of 2) or 2oo3 (2 out of 3) voter algorithm has BAD quality, OUT
continues to have GOOD quality status because there are enough good inputs for a real process
demand to cause a trip. However, if a single input of a 1oo1 or 2oo2 voter algorithm has BAD
status, its OUT has BAD status. If a CSn (input Cause n) input of a Cause and Effect Matrix
(LSCEM) algorithm has BAD status, all EFFn (output Effect n) outputs associated with that input
have BAD status.
OW351_47 225
LSAVTR, LSDVTR, and LSCEM algorithms have a configurable SOPT parameter, which impacts
how the algorithms determine the value of their output parameter(s) based on the quality of their
inputs. These algorithms determine the quality of their output parameter(s) by fixed status
propagation logic unique to the algorithm and independent of the SOPT parameter. This assures
that if BAD quality is capable of preventing a process demand from causing a trip, BAD quality
propagates to the output algorithm(s). Refer to the LSAVTR, LSDVTR, and LSCEM algorithm
documentation for more detail on the impact of the SOPT parameter in these algorithms.
Figure 142: Using SIS algorithms to create shutdown logic
226 OW351_47
5.9.2 Detecting faults on output channels
Faults detected by the Logic Solver on output channels (see page 171) can originate in field
devices, field wiring, or the Logic Solver output circuitry. As with input channels, the Logic Solver
responds to faults on output channels by integrating BAD quality with the channel value and
annunciating the fault.
A fault on an output channel does not prevent the output from being de-energized if there is a
demand to trip on that channel. Suppose a Digital Output channel is stuck "On" due to a fault in
the output circuitry. When Control Module logic detects a process demand to trip and the LSDO
algorithm drives the channel "Off", power remains "On" as a result of the fault. However, the Logic
Solver reads back the output as still being "On" and initiates a reset, which opens the master
power switch and de-energizes all output channels on the Logic Solver.
When the "Detect open and short circuit" parameter on Digital Output channels is True (the
default value), the Logic Solver detects and annunciates stuck "On" conditions by means of
periodic pulse testing. In this way a failed unit can be replaced before a demand occurs, thereby
avoiding a trip on all output channels. The "Detect open and short circuit" parameter should
remain configured as True unless the final element cannot tolerate the 1 millisecond Off pulse
during each 50 millisecond period.
If the Logic Solver detects an open or short in field wiring or the output circuitry, and the FOP3
parameter of the LSDO algorithm associated with that channel is set, the algorithm enters the
fault state and drives the channel Off immediately upon detection. The FTIM value is not used in
this case.
An open or short in field wiring implies the final element is in the de-energized state. Therefore the
default value for the FOP3 parameter drives the channel "Off" when an open or short is detected.
In order to keep the channel "Off" after it is driven "Off", an operator reset must be required
somewhere. The reset can be on the final element itself, in the output algorithm, or in the
upstream LSCEM algorithm.
The following figure shows an example of using an LSCEM algorithm for latching an output "Off".
Figure 143: Using an LSCEM algorithm to latch an output Off
OW351_47 227
5.10 Choosing the Logic Solver scan rate
The CS3 input of the LSCEM algorithm has a value of 1 when neither output algorithm is in the
fault state. FSTAT is normally an internal parameter, but in this example, it is exposed as an
output parameter on the LSDO and LSDVC algorithms and connected to an LSNOR algorithm. If
either output algorithm detects an open or short on its referenced channel, a trip occurs on EFF1
of the LSCEM algorithm and both output algorithms drive their outputs Off (because CASND
becomes 0). The algorithm that detected the open or short had already driven its output Off. The
outputs remain Off until an operator reset is done on EFF1 by changing RST1 of the LSCEM
algorithm to True. The fault state condition clears when a Digital Output channel is driven Off
because the diagnostic no longer detects the condition. The same is true for a HART Two-state
Output channel when OFCUR is “0 milliamps.”
This technique applies to the case where a coordinated trip of multiple final elements is required
when any of the final elements involved in an interlock becomes de-energized due to an open or
short. If you want to drive Off only the output with the open or short, use a separate LSCEM Effect
output for each output algorithm and connect FSTAT into a separate Cause input.
In some applications it may not be desirable to drive an output Off when an open or short is
detected. For example, you may want the final element to become energized without operator
intervention whenever an intermittent short clears. In this case, disable the FOP3 parameter in the
output algorithm.
5.10 Choosing the L ogic Solv er sc an rate
The default scan rate (see page 165) for Control Module execution in the Logic Solver is 50
milliseconds. You can change the scan rate to 100, 150, or 200 milliseconds from the SLS
properties dialog in Ovation Explorer. Increasing the Logic Solver scan rate value impacts the
execution rate of Control Modules. But diagnostic cycle times in the Logic Solver remain constant,
with the exception of the main processor comparison diagnostic, which is a function of control
module scan rate.
The recommended scan rate to use whenever possible is 50 milliseconds. This scan rate
minimizes the input to output response time. The only reason to change the scan rate beyond the
default 50 milliseconds is if the Logic Solver is not able to execute the Control Module or modules
at the configured scan rate.
5.11 Loading to a run ning proc ess

If you anticipate a need to make online changes to Control Module logic, that is, to load Logic
Solvers that are protecting a running process, you should ensure the load does not disrupt the
process.
Locking a Logic Solver prevents it from being loaded. Locking also prevents a user-initiated Logic
Solver switchover. To be able to lock or unlock a Logic Solver you must enable the SIS-Allow full
access to Ovation SIS Configurations rule. A Logic Solver must be unlocked before you can load
to it (see page 199). If you attempt to load a locked Logic Solver, you are given the opportunity to
unlock the Logic Solver and continue.
228 OW351_47
5.12 Restarting a Logic Solver after a power failure
5.12 Restarting a Logi c Solv er after a po wer failure

A restart occurs after power is restored to a Logic Solver that had a running configuration prior to
losing power for less than 10 days. During a restart the Logic Solver reapplies the last loaded
configuration and restores parameters that had been saved to non-volatile memory. At the time
power is lost, outputs of the Logic Solver are de-energized, which should result in the same
output state as after the original load. After a restart the goal is to retain the same process state
that occurred as a result of the power failure, yet to restore the parameter values that were saved
to non-volatile memory, which are more current than the last loaded values.
5.13 Sy stem Ad ministration fun ctions
There are multiple functions that your System Administrator should perform. Some of these
functions are described below:
 Backing up the database (see page 229).
 Making configuration changes after startup (see page 229).
 Reconciling parameter changes (see page 229).
5.13.1 Backing up the database
It is valuable to always have a current backup of the database in case you need to replace
existing workstation for any reason. An automatic daily export is recommended beginning with the
engineering phase and continuing through the entire lifecycle. Use the Daily Export feature of
Ovation Database Administrator to configure automatic database exports.
It is valuable to always have a current backup of the database in case you need to replace the
database. Refer to Ovation Database User Guide for information on backing up your database.
5.13.2 Making configuration changes after startup
After the process is running, it is useful to have an offline Ovation system available in case you
need to make and test configuration changes to Control Modules. If you make changes to Control
Modules in the configuration database of your production system, you should be prepared for a
potential need to load them at any time, for example, if a simplex Logic Solver needs to be
replaced. It is better to import tested changes into the production system just before you plan to
load them.
5.13.3 Reconciling parameter changes
When you change a parameter value at runtime using an SIS Write from an Ovation Operator
Station or from the Control Builder, the change is recorded in the workstation so that you can
reconcile the change with the database later. Reconciling the change with the database keeps the
database value in sync with the runtime value.
However, if there is a need to load the Logic Solver, the new CRC value is different from the
existing value and a functional test is required. One Logic Solver of a redundant pair can be
replaced without a load. If you are using simplex Logic Solvers, you may want to forgo reconciling
parameter changes so that a load does not require a functional test. Instead, check to see if there
are any pending reconciles prior to loading. If so, record the changes, do the load, then manually
repeat the SIS Write operations.
OW351_47 229
5.14 Proof Testing the Logic Solver
5.14 Proof T esting the L ogic Solv er

Logic Solvers must be proof tested periodically to ensure there are no dangerous faults present
that are not being detected by continuous runtime diagnostics. A manual proof test for a Logic
Solver is initiated from the Ovation Developer Studio and causes the Logic Solver to go through
reset and power-up testing. Proof testing of Logic Solvers can also be done automatically.
Immediately following successful power-up testing, there are no known dangerous faults present.
Choose the proof test interval for a Logic Solver based on the associated SIF requiring the
shortest proof test period to achieve the required probability of dangerous failure for its Logic
Solver subsystem.
The Logic Solver proof test timer automatically counts the number of days since the last reset
occurred. The Logic Solver configuration dialog in Ovation Developer Studio has a Proof Testing
tab for entering the required proof testing interval and a reminder time value. See Logic Solver
configuration for information about the fields in this tab (see page 167).
Figure 144: Logic Solver configuration window (Proof Testing tab)
The Logic Solver provides a Proof Test Alert ("Proof Test is Overdue". Hardware Alert Condition
event is sent to Ovation Process Historian. Bit 12 is set in RN point of LS and point is alarmed.)
when the number of days since the last reset exceeds the configured time.
Also, a reminder alert ("Proof Test Reminder is Active". Hardware Alert Condition event is sent to
Ovation Process Historian. Bit 12 is set in RN point of LS and point is alarmed) occurs a
configured number of days before the “exceeds” alert to assist maintenance personnel in the
planning of manual tests.
The proof test timer for a redundant Logic Solver indicates the number of days since the last reset
of the Active unit, which always occurs earlier than the last reset of the Standby.
230 OW351_47
5.14 Proof Testing the Logic Solver
5.14.1 Automatic proof testing
Automatic proof testing is available for redundant Logic Solvers only. The Proof Testing tab of the
Logic Solver configuration dialog has an “Enable automatic proof test to run at reminder time”
check box (this check box is grayed-out for simplex Logic Solvers). When checked, the Logic
Solver performs the proof test when the number of days since the last reset reaches the
configured time. The test begins five minutes after the Logic Solver sets the reminder alert. In this
case the reminder alert informs the operator that a test will occur soon so that the "Partner Not
Available" alerts can be ignored after the test begins. At the time of automatic proof test:
 The Active Logic Solver starts the test by initiating a switchover to the Standby Logic Solver. If
the Standby Logic Solver is not available, the Active Logic Solver tries again in five minutes.
 After switchover, the Standby Logic Solver becomes Active and the new Standby Logic
Solver goes through reset and begins power-up testing. There is no adverse impact to the
running process.
 The new Active Logic Solver still has a proof test due, so it waits for its partner to become
available then initiates a switchover. When the partner has become the Active Logic Solver,
the new Standby Logic Solver goes through reset and power-up testing.
5.14.2 Manual proof testing
The following procedure should be used for manual proof testing of the Logic Solver.
Simplex Logic Solver

1. Initiating a manual reset on a simplex Logic Solver results in all outputs being de-energized. If
you must proof test a simplex Logic Solver online, you need to temporarily bypass or block
final elements and provide manual supervision.
2. The Logic Solver must be unlocked to initiate a manual reset. Select the Logic Solver under
SIS Network in the Ovation Developer Studio. Right-click on the Logic Solver and select
Unlock. Click Confirm on the SIS Write confirmation dialog.
3. Right-click on the Logic Solver and select Reboot. The Restart Wizard appears. Select Force
Restart Active from the options in the Restart Wizard window (see page 221). Clicking
Confirm on the confirmation dialog results in all outputs being de-energized.
4. The Logic Solver goes through power-up testing and returns to the configured state. The
proof test timer resets to 0.
Redundant Logic Solver
The procedure for a redundant Logic Solver allows the proof test to be done online without
adversely affecting the running process.
1. The Logic Solver must be unlocked to initiate a manual reset. Select the Logic Solver under
SIS Network in the Ovation Developer Studio. Right-click on the Logic Solver and select
Unlock. Click Confirm on the SIS Write confirmation dialog.
2. Right-click on the Logic Solver and select Reboot. The Restart Wizard appears. Select Force
Restart Standby from the options in the Restart Wizard window (see page 221). Clicking
Confirm on the confirmation dialog results in all outputs being de-energized.
3. Wait several minutes for the Standby Logic Solver to complete power-up tests and become
configured by the Active Logic Solver. The Partner Not Available maintenance alert goes
inactive when the Standby Logic Solver is fully configured.
OW351_47 231
5.15 Customizing Ovation Control Builder frame
4. Right-click on the Logic Solver and select “Reboot.” The Restart wizard appears. Select the
Switchover option. Click confirm on the confirmation dialog box to make the previously reset
Standby Logic Solver Active.
5. Click Confirm on the confirmation dialog.
6. The previously reset Standby Logic Solver becomes the new Active Logic Solver and the new
Standby Logic Solver goes through power-up tests and is configured by the new Active Logic
Solver. The proof test timer is 0.
5.15 Customiz ing Ov ation Control Build er frame
Every control function, control library, and control macro begins with a template or blueprint that
displays on the drawing canvas. This template, called the frame, contains a standard format that
can be used to enforce a consistent look for all the items in a project. The format also contains
information that identifies the item (sheet, library, and macro) to the system and to the user. By
placing this information in the frame, you do not have to enter it every time you create a new item.
The Control Builder provides an approved frame or template file, called the frame.svg file, which
is shipped with the standard release of the Ovation system. All of the elements of the frame are
defined in the frame.svg file.
You may want to customize a frame in order to more easily identify SIS control sheets. The SIS
Data Server, Logic Solver, and Control Module are available as Document Values under the Draw
menu.
Use the following procedure to create an SIS custom frame (Frame.svg) in the unit's Control
Functions directory.
1. Copy the default frame (C:\Ovation\CtrlBldr\Frame.svg) into the Control Functions Directory.
2. Add a [Document Value] for cb-sis-server in the custom frame (Frame.svg). You may wish to
add items for the Logic Solver and/or the Control Module at this time.
3. Recompile all the control sheets.
4. Load the Logic Solvers and control sheets. This document value will remain hidden on NON-
SIS Control Functions.
Refer to the Ovation Control Builder User Guide for more information about creating frames and
sheets, and adding document values.
5.16 Upgradin g SIS firm ware

Future releases of Ovation software will potentially include updated firmware for the SIS
components. It may not be necessary to upgrade the firmware in SIS hardware components when
the remainder of the Ovation system is upgraded to a new release. But if a new SIS firmware
revision has desired features or corrects a specific issue, you can upgrade to the new revision by
installing files from an Ovation workstation to flash memory in the SIS component.
The following topics provide upgrade procedures:

 To initially load or upgrade an SIS Data Server (see page 233).
 To upgrade an SIS Logic Solver (see page 234).
232 OW351_47
5.16 Upgrading SIS firmware
5.16.1 To initially load or upgrade an SIS Data Server
When an SIS Data Server is shipped, perform an initial load of the firmware. Subsequent loads of
the SIS Data Server are considered to be upgrades.
Emerson provides firmware for the SIS components in Ovation system. Firmware for the upgrade
to SIS Data Server consists of four Hex files and one UDF file. Use the following procedure to
initially load or upgrade your SIS Data Server.
1. Retrieve the new SIS Data Server firmware from the path:
Ovation\SIS\firmware\OvSisSDSFirmware.zip
2. Unzip the files and store the four Hex files and one UDF file in an area where they can be
easily accessed; (for example, C:\temp\sis)
3. Open a Command Prompt window and go to Ovation\OvationBase.
Enter the following command:
OvSisCtlUpgConsole <SDS> -n <path to files>
where:
<SDS> = name or IP address of SIS Data Server to be loaded or upgraded.
<path to files> = absolute path to Hex and UDF files.
(for example, OvSisCtlUpgConsole 127.168.1.1 -n
C:\temp\sis\InstallCtlR_MD.udf)
4. Press the Enter key.
The following text displays at the command prompt during the upgrade process:
Opening component ‘CTLPPCSTART’
Opening component ‘CTLPPCRECOVER’
Opening component ‘CTLPPCAPP’
Opening component ‘UPGRADE_SYS’
When the upgrade process is finished, the following message appears:
----------------------------------------------------------------
Upgrade Completion Summary: <Normal Completion>
-----------------------------------------------------------------
The SIS Data Server is now upgraded.
Note: If power is lost during a firmware upgrade, pull the SDS from Base and wait for a few
minutes. Restart the upgrade process.
OW351_47 233
5.16.2 To upgrade an SIS Logic Solver
Emerson provides firmware for the SIS components in your Ovation system. Use the following
procedure to upgrade your SIS Logic Solver (SLS):
Note: The typical upgrade time for a single Logic Solver is about eight minutes.
If during the upgrade process there is a network failure, or the workstation which is hosting the
upgrade application fails, you can restart the upgrade. To do so, repeat the procedure starting at
Step 4.
1. Retrieve the new Logic Solver firmware package from

C:\Ovation\SIS\Firmware\SLSFirmware.zip. It consists of four files:
 1340.idf
 IO_Compatibility.csv
 SLSApp.hex
 SLSBoot.hex
2. Store the four files in an area where they can be easily accessed (for example, C:\temp\sis).
3. Clear the target SLS in the Ovation Developer Studio (see page 161).
4. Clear the Ovation Controller to which the target Logic Solver is assigned.
5. Run the upgrade application from the command prompt:
Ovation.Sis.SlsUpgrade.Console.exe [SDS ip address/hostname]
[logic solver number] [logic solver redundant] [full path to idf file]
where:
[SDS ip address/hostname] = IP address or hostname of the SIS Data Server which is
supervising the Logic Solver that you are upgrading.
[logic solver number] = Number (1-32) of the physical Logic Solver that you are upgrading
(this is not the carrier slot number).
[logic solver redundant] = Flag indicating whether the target Logic Solver is in a redundant
configuration. Accepted values of this attribute are true or false.
[full path to idf file] = Fully qualified file name of the .idf file which is part of the firmware
package, (for example, d:\sls-firmware\v.10.3\1340.idf
6. Confirm that you want to proceed with the upgrade by entering y when prompted.
Note: If Logic Solvers are in a redundant configuration, a confirmation to proceed message will
appear twice.
7. Wait for the application to terminate. The application will periodically output messages
regarding the progress of the upgrade process. In the final step, it will report the status of the
entire upgrade.
WARNING! Do not shutdown the computer or interrupt the upgrade process until it is
completed. Failure to comply may result in corrupting the Logic Solver's flash memory and
making the Logic Solver unusable.
You MUST perform a full function test of the Logic Solver after the firmware upgrade.
234 OW351_47
5.16.3 To upgrade an SIS Net Repeater
Emerson provides firmware for the SIS components in your Ovation system. Use the following
procedure to upgrade your SIS Net Repeater (SNR):
1. Retrieve the new SIS Network Repeater firmware package from

C:\Ovation\SIS\Firmware\SNRFirmware.zip. It consists of four files:
 1345.idf
 IO_Compatibility.csv
 SNRApp.hex
 SNRBoot.hex
2. Store the four files in an area where they can be easily accessed (for example, C:\temp\sis).
3. Run the upgrade application from the command prompt:
Ovation.Sis.SnrUpgrade.Console.exe [SDS ip address/hostname] [SIS
Net Repeater redundant] [full path to idf file]
where:
[SDS ip address/hostname] = IP address or hostname of the SIS Data Server, which is
supervising the SIS Net Repeater that you are upgrading.
[SIS Net Repeater redundant] = Flag indicating whether the target SIS Net Repeater is in a
redundant configuration. Accepted values of this attribute are true or false.
[full path to idf file] = Fully qualified file name of the .idf file which is part of the firmware
package.
For example:
Ovation.Sis.SnrUpgrade.Console.exe SDS1 true c:\tmp\SNRFirmware\1345.idf
4. Check the Firmware version. If the firmware that is used to upgrade the SIS Net Repeater
matches with the firmware in the SIS Net Repeater, the upgrade is stopped for that SIS Net
Repeater.
5. Confirm that you want to proceed with the upgrade by entering y when prompted.
6. Wait for the application to terminate. The application will periodically display messages
regarding the progress of the upgrade process. At the end, it will report the status of the entire
upgrade.
WARNING! Do not shut down your computer or interrupt the upgrade process until it is
completed. Failure to comply may result in corrupting the SIS Net Repeater's flash memory
and making the SIS Net Repeater unusable.
You MUST perform a full function test of the SIS Net Repeater after the firmware upgrade.
Note: If power is lost during firmware upgrade, pull the SNR from the Base and wait for some
time. Restart the upgrade procedure.
OW351_47 235
5.17 Using Fault Codes for SIS
5.17 Using Fault Code s for SIS

The Ovation system generates fault codes and messages that you can use to diagnose
workstation and system problems. This section details the fault codes and messages that are
generated by the Safety Instrumented System.
To research other fault codes generated by your system, access the Ovation fault information tool
at:
https://www.ovationusers.com/FIT/index.asp
You can find fault information on the System Status diagram and the Drop Details diagram. You
can find further information in your Error Log Viewer.
 Fault Code = FC (displayed in decimal in the Drop Details diagram).
 Fault ID = FK (displayed in hexadecimal in the Drop Details diagram).
 Fault Parameter 1 = FS (displayed in hexadecimal in the Drop Details diagram).
 Fault Parameter 2 = FO (displayed in hexadecimal in the Drop Details diagram).
 Fault Parameter 3, 4, and 5 (displayed in hexadecimal in the Windows Error Log Viewer).
The SIS shadow algorithms have the following values:
 Fault Code = 66 which indicates a Controller fault.
 Fault ID = 0x0003 which indicates an algorithm fault.
 Fault Parameter 1 =0x0008 which indicates a problem with an SIS shadow algorithm as it
appears in the Ovation Controller.
Fault codes
FA UL T P ARAM ET E R 2 D E S C RIP T IO N
0x0001 Logic Solver function number (Y1 field) is invalid.

Parameter 3 = Control Module ID
Parameter 4 = Control sheet number
Parameter 5 = Algorithm execution order number for the control sheet
0x0002 Value in an algorithm field (TT field) is invalid.
0x0003 Auxiliary record for the algorithm cannot be found.
0x0004 XDB lock cannot be found and the algorithm did not update parameter and
output values in that loop.
0x0005 There is a module revision mismatch between algorithm point configuration
and Logic Solver module configuration.
236 OW351_47
The SIS I/O faults have following values:
Fault Code = 66 which indicates a Controller fault.
Fault ID = 0x000b which indicates I/O subsystem fault.
Fault Parameter 1 – can have following values:
0x0002 – Data Link I/O error (fails controller if partner is available)
0x0005 – Data Link I/O error (unconditionally fails controller)
0x0006 – Data Link I/O warning (does not fail controller)
Note: For SIS I/O faults category, the Fault Parameter 2 in Ovation Error Log has the additional
bit 0x18000 instead of 0x8000.
Fault codes
FA UL T FA UL T D E S C RIP T IO N AC T I O N
P AR AM ET E R 1 P AR AM ET E R 2
0x0005 0x8000 Failed to check if there are changes in Contact Emerson.

Data Link tables.
Parameter 3 = SIS I/O Device index
Parameter 4 = 0
Parameter 5 = 0
0x0005 0x8001 Failed to check status of SIS I/O Contact Emerson.
device.
Parameter 3 = 1
Parameter 4 = 0
Parameter 5 = 0
0x0005 0x8002 Failed to retrieve points’ tags from Contact Emerson.
Data Link driver.
Parameter 3 = Indicates when
problem occurred (1 – during SIS I/O
task initialization, 2 – after controller
load)
Parameter 4 = 0
Parameter 5 = 0
0x0005 0x8003 Error occurred while setting dynamic Contact Emerson.

fields of SIS I/O or SIS RN point.
Parameter 4 = 0
Parameter 5 = 0
OW351_47 237
0x0005 0x8004 Error occurred while setting static Contact Emerson.

fields of SIS I/O or SIS RN point.
Parameter 4 = 0
Parameter 5 = 0
0x0005 0x8005 Failed to initialize XDB scheduler Verify that SIS I/O
task. Device has SIS
Identifier assigned.
Verify that IP
Parameter 4 = 0 address is assigned
Parameter 5 = 0 to SIS I/O device.
Verify that XDP port
number and XDB
broadcast address
are configured.
0x0005 0x8007 Failed to acquire XDB lock. Contact Emerson
Parameter 4 = Indicates when
problem occurred (1 – during SIS I/O
task initialization, 2 – after controller
load)
Parameter 5 = 0
0x0006 0x8008 Getting point failed in SIS Alarm Contact Emerson.
Handler.
Parameter 3 = Return status
Parameter 4 = Point SID
Parameter 5 = 0
0x0006 0x8009 Error initializing hash map in SIS Contact Emerson.
Alarm Handler.
Parameter 4 = 0
Parameter 5 = 0
0x0005 0x8010 Failed to initialize SIS Alarm Handler. Contact Emerson
Parameter 5 = 0
0x0006 0x8011 Missing or invalid SIS Alarm mapping Load Logic Solver
file. and SIS controller.
Parameter 4 = SIS identifier of SDS
Parameter 5 = LS slot number
238 OW351_47
5.18 SIS Node Point (RN Point)
0x0005 0x8012 Creating/attaching to Hardware Alert Contact Emerson.

Conditions’ message queue failed.
Parameter 3 = Return
statusParameter
4 = Indicates in which task problem
occurred (1 – SIS I/O task, 2 – SIS
Alarm Handler task)
Parameter 5 = errno
0x0005 0x8013 Error when initializing socket for SIS Contact Emerson.
I/O data.
Parameter 5 = errno
0x0006 0x8013 Error occurred while receiving SIS I/O Contact Emerson.
data.
Parameter 5 = errno
0x0006 0x8014 SIS Alarm Handler internal warning. Contact Emerson
Parameter 3 = 0
Parameter 4 = 0
Parameter 5 = 0
0x0005 0x8015 Memory allocation error in SIS I/O Contact Emerson.
task.
Parameter 3 = Error details (identifies
place in source code)
Parameter 4 = errno
Parameter 5 = 0
0x0006 0x8016 Error reading SIS I/O device Verify that SIS I/O
configuration file. device is properly
configured and
Parameter 3 = SIS I/O Device index configuration is
Parameter 4 = 0 downloaded to
Parameter 5 = 0 controller.
0x0005 0x8017 TCP socket error in SIS Alarm Contact Emerson.

Handler.
5.18 SIS Nod e Point (RN Point)
You can perform diagnostics on your SIS system by referring to the bit values of the Node (RN)
record of a point.
1. Access the Ovation Operator Station.
OW351_47 239
2. Access Point Information from your Ovation Applications folder at the Operator Station to view
the node record (refer to the Ovation Operator Station User Guide for more information about
the Point Information function).
3. Navigate to the Value/Status tab in the node record (the value used for the node record is the
A2 field).
4. Review the collected bit information about the module or node.
Bit Information: IO Device RN Point
BIT D E S C RIP T IO N S ET R E S ET I/O D RIV E R S T AT US ( A2 FIELD

D E F INIT IO NS )
0 Configured OK NCONF I/O Driver is configured. This bit is set by the

I/O driver during the first pass.
1 Communication error ERROR OK There is a communication error. The I/O
driver cannot send messages to the SIS Data
Servers.
2 Configuration error ERROR OK There is an error in a configuration file or the
configuration is inconsistent.
3 Alarm handler error ERROR OK The alarm handler has indicated that one or
more alarm files are corrupted.
4- <unused>
15
Bit Information: SIS Data Server RN Point
BIT D E S C RIP T IO N S ET RE S ET D AT A S E RV E R S T AT US ( A2 FIELD

D E F INIT IO NS )
0 Configured OK NCONF SIS Data Server is configured.

1 Primary In Control CTLR NCTLR The primary SIS Data Server is in control.
2 Railbus ERROR OK There is an error in the SIS Data Server
Communication Error communication over the backplane.
3 SIS LAN ERROR OK There is a timeout in the communication

Communication between an SIS Data Server and an Ovation
Timeout Controller.
4 Communication With COMM NCOMM There is no communication with primary SIS
Primary Data Server.
5 Communication With COMM NCOMM There is no communication with secondary
Secondary SIS Data Server.
6 Secondary In Control CTLR NCTLR The secondary SIS Data Server is in control.
7 Redundancy Lost RLOST OK There is no communication with one of the
SIS Data Servers from redundant pair.
8 Left Repeater COMERR OK There is no communication between SIS Data
Communication Server and left SIS Net Repeater or error
occurred in repeater’s Communication
subsystem.
240 OW351_47
BIT D E S C RIP T IO N S ET RE S ET D AT A S E RV E R S T AT US ( A2 FIELD

D E F INIT IO NS )
9 Left Repeater Local LOCERR OK There is an error in Local Peer subsystem of

Peer left SISNet Repeater.
10 Left Repeater Remote REMERR OK There is an error in Remote Peer subsystem
Peer of left SISNet Repeater.
11 Right Repeater COMERR OK There is no communication between SIS Data
Communication Server and right SISNet Repeater or error
occurred in repeater’s Communication
subsystem.
12 Right Repeater Local LOCERR OK There is an error in Local Peer subsystem of
Peer right SISNet Repeater indicates an error.
13 Right Repeater REMERR OK There is an error in Remote Peer subsystem
Remote Peer of right SISNet Repeater.
14 <unused>
15 <unused>
Bit Information: Logic Solver RN Point
BIT D E S C RIP T IO N S ET R E S ET LOGIC SOLVER S T AT U S ( A2 FIELD

D E F INIT IO NS )
0 Configured OK NCONF The Logic Solver is configured.

1 Commissioned OK DECOM The Logic Solver has been recognized by
D Ovation.
2 Calibration ACTIVE NACT The Logic Solver has been calibrated.
3 Configuring State ACTIVE NACT The Logic Solver is configured.
4 Communication Error ERROR OK There is an error in the communication with
the Logic Solver.
5 IO Channel Error ERROR OK There is an error in the Logic Solver's I/O
channels.
6 Primary In Control PRIM BCKP The primary Logic Solver is in control.
7 Locked LOCKED UNLCKD The Logic Solver is locked and cannot be
loaded.
8 Scan Rate Overloaded OVRLD NOVRLD The configured scan rate for the Logic Solver
is exceeded by the estimated execution time.
9 Any Module in Debug DEBUG NORMAL At least one of the Control Modules is in
Mode debug mode.
10 Failed Alert FAILAL NORMAL At least one Hardware Alert Condition from
Failed category is active.
11 Maintenance Alert MTNCAL NORMAL At least one Hardware Alert Condition from
Maintenance category is active.
12 Advisory Alert ADVSAL NORMAL At least one Hardware Alert Condition from
Advisory category is active.
13 Communication Alert COMMAL NORMAL No communication with Logic Solver. No
other conditions can be detected.
OW351_47 241
5.19 SIS Events
BIT D E S C RIP T IO N S ET R E S ET LOGIC SOLVER S T AT U S ( A2 FIELD

D E F INIT IO NS )
14 Register CtrlMod for UNREG NORMAL At least one of the Control Modules is not
SIF data configured for SIF data.
15 Logic Solver RLOST OK There is no communication with one of the
Logic Solvers from redundant pair.
Redundancy Lost
Bit Information: Logic Solver Control Module RN Point
BIT D E S C RIP T IO N S ET R E S ET LOGIC SOLVER M O D U L E S T AT U S ( A2

F IE L D D EF INIT IO NS )
0 Module Not Registered NREG OK The module is not registered

1 Debug Mode DEBUG NORM Control Module is in Debug Mode. The
Debug Mode is where you can perform
functional testing of safety logic by forcing
input values and quality for SIS algorithms.
2- <unused>
10
11 Active SIF Error SIFERR NOERR There is active SIF Error condition in Control
Module.
12 Active SIF Alert SIFALT NOALRT There is active SIF Alert condition in Control
Module.
13- <unused>
15
SDS RN Point bit 9 (bit 12 in case of secondary SISNet Repeater) is set if one of the following
conditions occurred:
 The local peer bus is not terminated or improperly terminated.
 The local peer bus receiver or transmitter hardware indicates an error.
SDS RN Point bit 10 (bit 13 in case of secondary SISNet Repeater) is set if one of the following
conditions occurred:
 The remote fiber-optic ring is not connected to both the transmit and receive ports.
 Another SISNet Repeater in the ring is powered down, causing a broken ring condition.
 The fiber is crossed such that a primary SISNet Repeater is receiving messages from a
secondary SISNet Repeater.
 Remote fiber-optic ring hardware indicating a transmitter or receiver error.
SDS RN Point bits 8 – 13 can be set if there is more than one SIS Data Server in the system.
In case of configuration with simplex SDS, bit 5 is set all the time.
5.19 SIS Ev ents

When SIS Events functionality is configured in SIS system, SIS Events are sent to Ovation
Historian. To determine health of the SIS system or to recreate sequence of events after incident,
the stored events can be accessed in the Operator Events subsystem of the Historian.
242 OW351_47
5.19 SIS Events
5.19.1 To configure SIS Loggers
Before configuring SIS Loggers, make sure that the following prerequisites have been met::
Prerequisites
 Ovation Historian is configured in the system.

 Ovation Historian Operator events scanners are configured in the system.
To enable SIS events functionality, you need to configure the SIS loggers in the system by
performing the following steps:
1. Access the Ovation Developer Studio. Use the system tree to navigate through the following
nodes and their sub nodes to the SIS Logger configuration item:
Hardware Root
System
[System Name]
Networks
[Network Name]
Configuration
SIS Logger
OW351_47 243
5.19 SIS Events
Figure 145: Navigate to SIS Logger
244 OW351_47
5.19 SIS Events
2. Double-click the SIS Logger item in lower pane of the window. The SIS Logger window
appears.
Figure 146: SIS Logger Window
3. In the SIS Logger 1 section, use the drop-down list to select the drop that is configured as the
Ovation Historian Operator events scanner. If scanners are configured as a redundant pair,
select primary scanner in the section SIS Logger 1 and backup in the SIS Logger 2 section.
4. Download and reboot drops selected as SIS Loggers. Use the system tree to navigate
through the following folders and their subfolders to the Controller configuration item of SIS
Interface Controller:
Hardware Root
System
[System Name]
Networks
[Network Name]
Units
[Unit Name]
Drops
[Drop name]
Configuration
Controller
OW351_47 245
5.19 SIS Events
Figure 147: Navigate to Controller properties
246 OW351_47
5.19 SIS Events
5. Right-click the Controller node and select Open from the context menu. The Controller
window appears.
Figure 148: Controller SIS Logger window
6. In the SIS section, select the Use SIS Loggers check box.
7. Download new configuration to the Controllers and reboot them.
8. Generate a new configuration for SIS Switches and upload it (refer to: To configure SIS LAN
Network Switches (see page 132)).
9. Reboot all the SIS Data Servers.
Note: Disconnect the power to the SDS to reboot them.
5.19.2 Viewing Historical SIS Events
To view historical SIS events:
1. Open the Historical Review application from Start ->All Programs -> Ovation -> Ovation
Applications.
OW351_47 247
5.19 SIS Events
2. By default, the SIS view is not shown in the historical review. Click the Select View(s) tab and
add the SIS view to the list.
Figure 149: Add SIS view to Historical Review
3. Select the SIS view, go to filters and select all drops. For SIS actions, there are many events
generated and can be observed in SIS view.
5.19.3 SIS Events Types
The following subsections describe several types of events that occur on the SIS system. These
are:
 Hardware Alert Conditions (HAC)
 Module Events
 SIF Alerts and Errors
 Logic Solver Events
 SDS Events
 Other Events
248 OW351_47
5.19 SIS Events
Hardware Alert Conditions (HAC)
This type of event indicates a problem with the Logic Solver hardware. The RN point for Logic
Solvers contain aggregated information if any of the HAC is active from each category. Their
timestamp is originated on the Logic Solver. The following are the subtypes of the HAC events:
 Failed
Logic Solver is communicating; however, the important functions are not operable or there is
a loss of control functions. The table below lists the possible Failed Hardware Alert conditions:
Failed Hardware Alert conditions
C O ND IT IO N D E S C RIP T IO N
Program Assertion Unspecified internal software error.

Resource Error System software could not obtain a hardware or software
resource.
Memory Test Failure Failure detected in periodic main processor RAM test or power
up test of RAM and NVM.
Uncommanded Switchover Active Logic Solver has gone through reset (become Standby)
because it was not communicating with Controller.
Control Subsystem Compare Error The main processors detected a mismatch in outputs or
secure parameter data.
Timeout on Inter-Processor Link Between Number of scans exceeded for a main processor to respond to
Main Processor 1 and Main Processor 2 the other.
Timeout Between Main Processor 2 and Number of scans exceeded for I/O Processor to respond to the
I/O Processor Main Processor 2. Fatal errors detected by I/O Processor are
revealed by this condition.
Main Processor 2 Compare of I/O The Main Processor 2 validates the calculations done by the
Processor Data Failed I/O Processor. A mismatch in the results of the calculations
causes this condition.
Main Processor 2 Compare of I/O The Main Processor 2 has detected that I/O Processor is
Processor Frequency Failed communicating at an improper rate.
Task Checkpoint Error A control or communications task did not have a timely or
proper completion.
Control Subsystem Scheduling Error The Main Processor 2 is unable to complete writing of output
values prior to beginning new control execution.
Dual Active Logic Solvers One Logic Solver of a pair has gone through reset because
both Logic Solvers were in the active role.
Hardware Watchdog Failure A power up test failed on a watchdog timer or a processor did
not arm its watchdog within the window during operation.
Both SIS Net Connections on Logic Neither of the main processors can communicate on the peer
Solver are Bad bus.
Unspecified hardware Error
OW351_47 249
5.19 SIS Events
 Maintenance
All functions are working; however, attention is required. The table below lists the possible
Maintenance Hardware Alert conditions:
Maintenance Hardware Alert conditions
Calibration Data Questionable One or more calibration values are outside the valid range or
no manufacturing calibration data is present.
Modules Not Executing at Configured The Logic Solver has set the actual scan rate longer than the
Scan Rate configured scan rate based on the estimate of execution time
at download.
Non-Volatile Memory Battery or Chip Non-Volatile Memory battery or chip failure has been
Failure detected during periodic test, or unable to restore saved
parameter records after power up or reset, or a CRC error
occurred when writing a parameter record.
Channel Error Status of one of the channels is bad.

SIS Net Error Any condition other than 'high error rate' is active in peer to
peer subsystem.
Partner Not Available Partner card is not responding to heartbeat messages or is
responding but is not configured.
Partner Not Present Partner card is not responding to heartbeat messages.
Card Not Communicating One card of a redundant pair is not communicating with the
Controller. Not applicable to a simplex Logic Solver.
Card Not Fully Operational The same condition was present on back-to-back resets.
 Advise
A single condition on the hardware is detected. Attention is required. The following table lists
the possible Advisory Hardware Alert conditions:
Advisory Hardware Alert conditions
SIS Net High Error Rate High peer bus error rate detected by the Main Processor 1 or the Main
Processor 2.
I/O Processor Communication The Main Processor 2 views a high percentage error rate in
Error communication with the I/O processor.
Non-Volatile Memory Alert Non-volatile memory availability for parameter change records is low
or exhausted.
High Railbus Error Rate The Main Processor 1 views a high percentage error rate in
communications with the controller.
High Redundancy Link Error The Main Processor 1 views a high percentage communications error
Rate rate on the redundancy link.
I/O Processor Integrity Error The I/O Processor is reporting a calibration or self-test error.
Self-Test Incomplete A periodic memory test did not complete in the allotted time.
Configuration Mismatch Between Controller sees mismatch between configured and reported CRC.
250 OW351_47
5.19 SIS Events
Logic Solver and Controller
Internal Communications Error There is a high percentage error rate in communications between the
main processors.
Non-Critical Mismatch Between The main processors have determined a mismatch in dynamic data
Main Processor Data other than outputs and secure parameter values.
Proof Test Reminder is Active The number of days since the last proof test is approaching the
required proof test interval.
Proof Test is Overdue The number of days since the last proof test has exceeded the
required proof test interval.
CPU Free Time Low <20 The idle time on one or both of the main processors is less than 20%
of the total task time.
Task Checkpoint Alarm A non-critical task has not completed properly in one of the
subsystems.
 Communication
The following message is sent:
Communication Alert Condition
Communication Alert Condition No communication with Logic Solver. No other conditions can be
<param1> detected.
OW351_47 251
5.19 SIS Events
Module Events
The Module events indicate an occurrence of a task in the safety logic that is running in the
specific Control modules of the Logic Solver (for example, DVTR input is voting to trip). Their
timestamp is originated on the Logic Solver. The possible SIS module events are listed below:
 Successful confirmation following a command to trip.
 Failed to confirm following a command to trip.
 Confirmed Off while commanded On.
 Partial stroke test started.
 Partial stroke test denied.
 Partial stroke test failed.
 Successful partial stroke test.
 Partial stroke test past due.
 Successful confirmation following a command to trip.
 Failed to confirm following a command to trip.
 Confirmed Off while commanded On.
 Bypass removed on <param1>.
 Maintenance bypass permitted.
 Maintenance bypass permit removed.
 Maintenance bypass on <param1>.
 Maintenance bypass removed by block due to timeout.
 <param1> voting not to trip.
 <param1> voting to trip.
 A bypassed input is voting to trip.
 No bypassed input is voting to trip.
 A bypassed input is voting to pretrip.
 No bypassed input is voting to pretrip.
 Trip, first out Cause <param1>.
 FIRST_OUT cleared.
252 OW351_47
5.19 SIS Events
SIF Alerts and Errors
SIF Alerts and Errors are created on the SIS Interface Controller. These alerts and errors
describe operational aspects of the Control module. Their timestamp is originated on the
Controller. The possible SIF Alerts and Errors are listed below:
SIF Errors
 'Memory Failure' or 'Config Error' bit set in BLOCK_ERR in a Calc/Logic block.
 An input block or parameter reference has Bad status on its output.
 An output block or secure parameter has Bad status on its output.
 'Failed to Confirm Following a Command to Trip' bit set in DO_ALERTS in an output block.
 'Fault State Active' bit set in BLOCK_ERR in an output block.
 A wired block input is not able to update due to write-check fail or error on source read.
 'Output Failure' bit set in BLOCK_ERR in a Calc/Logic block.
 A parameter path is unresolved.
 Module not executing at configured scan rate.
 The last partial stroke test failed.
SIF Alerts
 A wired input to a block or secure parameter is being forced in Debug.
 An AVTR or DVTR block has a bypassed input.
 An AVTR or DVTR block has an active startup override.
 A bypass or startup override is about to expire in an AVTR or DVTR block.
 Trip consensus in an AVTR or DVTR block.
 Pre-trip consensus in an AVTR block.
 Deviation limit exceeded in an AVTR or MID block.
 A CEM block has a non-zero FIRST_OUT.
 A DO or DVC block is in an Off state.
 Debug View Active.
 Invalid SIF Alert Index.
Note: To get SIF Alerts and SIF Errors, you must define RN points for each Control module.
OW351_47 253
5.19 SIS Events
Logic Solver Events
The Logic Solver events inform you about the occurrence of switchovers, proof tests, and similar
incidents with Logic Solver cards. Their timestamp is originated on the Logic Solver. The possible
Logic Solver events are listed below:
 REDIO: Switchover Occurred; card switch <param1>.
Param1 is the SLS slot number of the Logic Solver that indicates switchover direction by arrow.
 Power Failure Occurred for <param1> seconds.
Param1 is a number representing seconds.
 The fatal error that caused the most recent reset of the logic solver card.
 Logic Solver Card Lost Event(s).
 Logic solver proof test and power up successful.
SDS Events
The SDS events inform you about the incidents on the SIS Data Server (devices, modules
registration, and problems with XDB communication). Their timestamp is originated on the SIS
Data Server. The possible SDS events are listed below:
 Deleting logic solver device.
 Deleting SIF modules.
 SIF module registered.
 SIF module registration failed. Card failure.
 SIF module registration failed. Timeout.
 SIF module registration failed. No active card.
 SIF module registration failed. Unknown error.
 SIF module naming conflict.
 XDB Packet deleted.
 No SIS configuration packets.
 SLS list update.
 Tried to create Logic Solver but module already exists.
 Failed to create Logic Solver.
 PIO SIF data queue error.
 Railbus raw I/O data is stale.
 PIO RIO data queue error.
 XDB: <param1>.
 SIF data parse error.
 Railbus connection lost. Standby SDS went into Unconfigured state.
254 OW351_47
5.19 SIS Events
Other Events
These types of event inform you about the user initiated action (for example, Logic Solver load
and Log Solver lock/unlock) or incidents that do not fall into any of categories described in
previous paragraphs. Their timestamp is originated on the SIS Data Server. Those events are
listed below:
 Completed controller reset initialization.
 Controller experienced powerfail.
 Controller free memory is now below 50K (%p1K).
 Switchover Occurred.
 Logic Solver Commission.
 Logic Solver Decommission.
 Logic Solver Lock.
 Logic Solver Unlock.
 Logic Solver Force restart on active.
 Logic Solver Force restart on standby.
 Logic Solver Switchover.
 Enter debug.
 Leave debug.
 Force input.
 Remove force input.
 SIS Logic Solver Download: Success.
 SIS Logic Solver Download: Failure <param1>.
 Start SIS Logic Solver Download.
 Logic solver proof test and power up successful.
 SIS Logic Solver is not fully operational.
 Configuration is invalid.
 Undefined item while processing download script.
 Invalid field in download script.
 Conversion error while processing download script.
 Download script too large to process.
 SIS module execution exceeds time allowed for 200 ms scan rate.
 Download rejected by Diag subsystem.
 Write to program flash memory failed.
 Unable to erase program flash memory.
 Invalid reference in download script.
 Required item is not found in download script.
 No SIS Logic Solver card present.
 SIS Logic Solver download did not complete due to timeout.
 SIS Logic Solver is not commissioned.
 Card is not in Active role.
 Low Controller free time.
 Low Controller free memory.
OW351_47 255
5.19 SIS Events
256 OW351_47
Index
Configuring SIS components using the

A Developer Studio • 108
Accessing the SIS Tuning window for SIS Configuring SIS control modules • 185
algorithms • 204 Configuring SIS LAN network switches • 132
Adding an SIS control sheet to the SIS Configuring the Logic Solver Config tab •
Ovation system • 187 163
Adding an SIS Data Server to the Ovation Configuring the Logic Solver General tab •
System • 111 165
Adding an SIS I/O device to the Ovation Configuring the Logic Solver Proof Testing
System • 123 tab • 167
Adding an SIS network switch to the Ovation Configuring the Logic Solver's response to
System • 117 detected faults • 223
Adding and configuring SIS components in Copyright Notice • 2
the Ovation Developer Studio • 105 Customizing Ovation Control Builder frame •
Adding and configuring SIS Logic Solvers in 232
the Ovation System • 161
D
Analog Input and HART Analog Input
Channel Specifications and Wiring • 68 Deleting an SIS Point • 197
Associating a Node point with an SIS I/O Detecting faults on input channels • 224
device • 127 Detecting faults on output channels • 227
Automatic proof testing • 231 Digital Input Channel Specifications and
Auxiliary Relay Diode module • 100 Wiring • 69
Auxiliary Relay DTA-Inverting module • 95 Digital Output Channel Specifications and
Auxiliary Relay ETA-Direct module • 99 Wiring • 71
B E
Backing up the database • 229 End of Line Resistance module • 103
Bypasses and overrides • 217
F
C
Fiber-optic cable\ring • 77
Capacities for Ovation SIS system • 7 Forcing an algorithm input value • 205, 206
Carrier extender cable part numbers • 55 Functions of Ovation SIS • 2
Carrier extender cables • 54
Choosing the Logic Solver scan rate • 228 H
Clearing the force value and leave Debug Handling BAD quality on analog input
Mode • 215 channels • 224
Configuration of bypasses • 218 Handling BAD quality on digital input
Configuring a Digital Input Channel • 170 channels • 225
Configuring a Digital Output Channel • 171 Hardware Alert Conditions (HAC) • 249
Configuring a HART Analog Input Channel • Hardware cabinet design example • 30
172 Hardware components of Ovation SIS • 41
Configuring a HART Two-state Output Hardware for Ovation SIS • 41
Channel • 174 HART Two-state Output Channel
Configuring an alarm for SIS digital point • Specifications and Wiring • 68
190 Horizontal Carriers • 43
Configuring an Analog Input Channel • 176
Configuring an SIS I/O channel • 168 I
Configuring Ovation system for SIS alarms •
Installation tools • 39
188
Installing carrier extender cables • 55
Installing Logic Solvers • 64
OW351_47 257
Index
Installing power supplies • 78 Restarting a Logic Solver after a power

Installing Terminal Blocks • 54 failure • 229
Introduction to Ovation Safety Instrumented
System (SIS) • 1 S
L Safety Instrumented Functions (SIFs) • 6
Safety Instrumented System terminology • 2
Loading an SIS Logic Solver • 199 Safety Integrity Levels (SILs) • 6
Loading Logic Solvers • 199 SDS Events • 254
Loading to a running process • 228 SIF Alerts and Errors • 253
Logic Solver 8-Slot carrier numbering SIS Alarming with Logic Solver timestamp •
scheme • 63 188
Logic Solver Events • 254 SIS aspects to consider • 5
Logic Solver redundancy • 65 SIS Carriers • 43
Logic Solver specifications • 67 SIS Current Limiter module • 92
SIS Data Server • 56
M SIS Data Server LEDs • 59
Maintenance bypass example • 219 SIS Data Server part number • 56
Making configuration changes after startup • SIS Data Server specifications • 61
229 SIS environmental specifications for Ovation
Making online scaling changes in HART SIS devices • 7
transmitters • 220 SIS Events • 242
Manual proof testing • 231 SIS Events Types • 248
Module Events • 252 SIS Hardware Outputs (Digital Outputs) •
180
O SIS I/O channels • 67
SIS Interface Controller (SIS DROP) • 56
Operation of bypasses • 218
SIS Logic Solver • 61
Other Events • 255
SIS Logic Solver LED indicator patterns • 66
Ovation Point for SIS Hardware Inputs
SIS Logic Solver part number • 64
(Analog/Digital Inputs) • 177
SIS Network Switches and Routers • 82
Ovation SIS accessories • 82
SIS Network with four (4) SIS Switches • 8
Override types • 218
SIS Network with one (1) SIS Switch • 27
Overview of adding and configuring SIS
SIS Network with three (3) SIS Switches • 17
components • 106
SIS Network with two (2) SIS Switches • 23
P SIS Node Point (RN Point) • 239
SIS Power Supply LEDs • 82
Planning the hardware installation • 39 SIS Relay module • 83
Planning the Safety Instrumented System • 5 SIS Sensor Alarms • 191
Power Supply • 77 SIS Tuning window for the LSCEM algorithm
Power supply part number • 77 • 204
Power supply specifications • 78 SISNet Distance Extender • 74
Powering up a simplex SIS Data Server • 57 SISNet Distance Extender specifications •
Proof Testing the Logic Solver • 230 76
Providing power to SISNet Distance SISNet Repeater • 72
extenders • 80 SISNet Repeater LEDs • 74
Providing power to the Logic Solvers • 78 SISNet Repeater part number • 73
Providing power to the SISNet Repeaters • SISNet Repeater specifications • 75
79 SLS Simplex and Redundant terminal blocks
R • 53
Software components of Ovation SIS • 105
RC Compensator module • 102 Supported SIS network • 8
Reconciling parameter changes • 229 System Administration functions • 229
Removing or Deleting an SIS Point • 197
Requiring a reset before outputs can T
become energized • 223 To add an I/O device to the Ovation System
Restarting a Logic Solver • 221 • 123
258 OW351_47
Index
To add an IOIC device and an SIS I/O Using Fault Codes for SIS • 236
device number (Device driver) • 120 Using Ovation SIS • 199
To add an SIS Interface Controller (SIS Using Point Information (PI) to identify SIS
Drop) • 119 points • 201
To add an SIS Router to the Ovation System Using Point Information to identify SIS points
• 114 • 202
To add an SIS System to the Ovation
System • 108 V
To add an SISNet Rings to the Ovation Verify SIS licenses • 108
System • 109 Vertical Carriers • 44
To assign an SIS Data Server to an SIS I/O Viewing Historical SIS Events • 247
Device • 129 Viewing SIS points • 195
To configure SIS Loggers • 243 Viewing SIS Tuning windows for SIS
To generate SIS Switch configuration files algorithms • 203
for manual configuration Voltage Monitor module • 88
Generate & Save Source Type • 146
To initially load or upgrade an SIS Data W
Server • 233
What is a Safety Instrumented System? • 1
To install an SIS Data Server • 57
To install SISNet Repeaters for horizontal
mounting • 73
To install the 1-wide Horizontal carrier (dual
left-right extender cables) • 47
To install the 8-wide Horizontal I/O interface
carrier (can hold up to four simplex/two
redundant Logic Solvers) • 51
To install the Vertical (8-wide left/right side)
carrier (can hold up to four simplex/two
redundant Logic Solvers) • 52
To install the Vertical Controller (4-wide
Power/SIS Data Server) carrier • 50
To power up an additional SIS Data Server
from a redundant pair • 58
To remove an Active SIS Data Server from a
redundant pair • 58
To remove an SIS Point from the SIS
Control Sheets • 197
To restart (reboot) a Logic Solver • 221
To set a new forced SIS algorithm input
value and quality • 212
To upgrade an SIS Logic Solver • 234
To upgrade an SIS Net Repeater • 235
To upload configuration files to SIS Switch
from non-Ovation drop using serial
connection (Serial option)
Configure via Serial Source Type • 151
To upload configuration files to SIS Switch
from Ovation drop using Ovation Network
Connection (Ethernet option)
Generate & Configure Source Type • 133
To use 1-wide carrier as a terminator • 47
To use the 2-wide Horizontal power/SIS
Data Server carriers • 48
U
Upgrading SIS firmware • 232
Using BAD quality in Control Modules • 225
OW351_47 259

SIS-OW351 - 47 - Ovation SIS User Guide

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

SIS-OW351 - 47 - Ovation SIS User Guide

Uploaded by

Copyright:

Available Formats

Safety Instrumented System (SIS) User Guide for

1 Introduction to Ovation Safety Instrumented System (SIS) 1

2 Planning the Safety Instrumented System 5

3 Hardware for Ovation SIS 41

3.6.3 To power up a simplex SIS Data Server ........................................................... 57

4 Adding and configuring SIS components in the Ovation Developer

4.10 To add an SIS Interface Controller (SIS Drop) ............................................................. 119

5 Using Ovation SIS 199

5.5 Bypasses and overrides .............................................................................................. 217

1 Introduction to Ovation Safety Instrumented System

What is a Safety Instrumented System? ..........................................................................1

1.1 What is a S afety Instrumented Sy stem?

1.2 Functions of Ov ation SIS

1.3 Safety Instrumented Sy stem t erminology

SNMP Simple Network Management Protocol (SNMP) is used in

2 Planning the Safety Instrumented System

SIS aspects to consider...................................................................................................5

2.1 SIS aspect s to con sider

Consider the following aspects when planning a SIS project:

2.1.1 Safety Instrumented Functions (SIFs)

2.1.2 Safety Integrity Levels (SILs)

2.2 Capacities for Ov ation SIS sy ste m

Capacities for Ovation SIS system

SISNet Rings in a System 32

SIS environmental specifications

Storage temperature -40°C to 85°C (-40°F to 185°F)

Electromagnetic compatibility Per EN61326-1, Criteria A and Namur NE21

2.4 Supported SIS net work

2.4.1 SIS Network with four (4) SIS Switches

The following tables show the SIS Switches port usages:

First switch ( switch number 1) in ring network

Gi1/1 Gi1/2 of switch number 4_B

Fa3/6 Pri of SDS 08_B

Second switch (switch number 1_B) in ring network

Gi1/1 Gi1/2 of switch number 1

Third switch (switch number 2) in ring network

Gi1/1 Gi1/2 of switch number 1_B

Fourth switch (switch number 2_B) in ring network

Gi1/1 Gi1/2 of switch number 2

Fa1/4 N4 of Controller 4_B

Fifth switch (switch number 3) in ring network

Gi1/1 Gi1/2 of switch number 2_B

Fa2/2 Pri of SDS 19_B

Sixth switch (switch number 3_B) in ring network

Gi1/1 Gi1/2 of switch number 3

Fa2/8 Sec of SDS 22_B

Seventh switch (switch number 4) in ring network

Gi1/1 Gi1/2 of switch number 3_B

Fa3/6 Not used

Eighth switch (switch number 4_ B) in ring network

Gi1/1 Gi1/2 of switch number 4

Figure 1: SIS Network with Four (4) SIS Switches

2.4.2 SIS Network with three (3) SIS Switches

The following tables show the SIS Switches port usages:

First switch (switch number 1) in ring network

Gi1/1 Gi1/2 of switch number 3_B

Second switch (switch number 1_B) in ring network

Gi1/1 Gi1/2 of switch number 1

Third switch (switch number 2) in ring network

Gi1/1 Gi1/2 of switch number 1_B

Fa1/4 N1 of Controller 4_B

Fourth switch (switch number 2_B) in ring network

Gi1/1 Gi1/2 of switch number 2