Global Engineering Modularity Standards

(GEMS) SM_V2S - Two State Valve

User Manual
(Module Number: KGEOB10001)

SAP DIR: 10003507911 v00

Preface

(This page is left intentionally blank)

Publication KGEOB10001-00008 - December, 2017

Important User Information

In no event will Rockwell Automation, Inc. be responsible or liable for indirect or consequential damages
resulting from the use or application of this equipment.

The examples and diagrams in this manual are included solely for illustrative purposes. Because of the
many variables and requirements associated with any particular installation, Rockwell Automation, Inc.
cannot assume responsibility or liability for actual use based on the examples and diagrams.

No patent liability is assumed by Rockwell Automation, Inc. with respect to use of information, circuits,
equipment, or software described in this manual.

Reproduction of the contents of this manual, in whole or in part, without written permission of Rockwell
Automation, Inc., is prohibited.

Throughout this manual, when necessary, we use notes to make you aware of safety considerations.

Identifies information that is critical for successful application and understanding of the
product.

AADvance, Rockwell Automation, and TechConnect are trademarks of Rockwell Automation, Inc.

Trademarks not belonging to Rockwell Automation are property of their respective companies.
 Summary of Changes

This document contains the following changes:

Updated Information
Change: Page:

Initial Issue for Release 1.0.0 All

Publication KGEOB10001-00008 - December, 2017 i

 Preface

This document provides users of the Process Safety Toolkit with the
Introduction required information for the use of the Safety Two State Valve
(SM_V2S) in an AADvance based Safety Instrumented System.

A prerequisite for using the Process Safety Toolkit is that users have
the required AADvance and FTView proficiency and have taken the
Process Safety Toolkit training.

The SM_V2S Safety Module includes a Function

Block for use with Release 1.34 or later of AADvance
Workbench and controller firmware, plus a multi-
tabbed faceplate and graphic symbols for use in
building displays within FactoryTalk View SE 9.0 or
later.

References
The following references should be consulted in conjunction with this
manual. The latest version of these documents are available from the
Rockwell Automation Literature Library.

Title Document Number

AADvance System Build Manual ICSTT-RM448

AADvance Configuration Guide (WB1.3) ICSTT-RM405

AADvance Solutions Handbook ICSTT-RM447

Common The Global Engineering Modularity Standards (GEMS) Function Block

set has several common attributes. The following GEMS references
Information for All should be consulted in conjunction with this manual.
Function Blocks
Title Document Number

HMI Standards KGESTA0003

Publication KGEOB10001-00008 - December, 2017 ii

 Preface

Conventions and Set and Clear

Related Terms This manual uses set and clear to define the status of bits (booleans) and
values (non-booleans):

This Term: Means:

Set A boolean is made equal to 1 (ON)

An analog value is made equal to any non-
zero number

Clear A boolean is made equal to 0 (OFF)

An analog value is made equal to zero (i.e.
all the bits are equal to 0)

Edge and Level

This manual uses Edge and Level to describe how bit (boolean) Commands,
Settings, Configurations and Inputs are processed by this Function Block.

Send/Receive
Method: Description:

Edge • Action is triggered by "rising edge" transition of input

(0-1)
• Separate inputs are provided for complementary
functions (such as "enable" and "disable")
• Sending logic SETS the bit (writes a 1) to initiate the
action; this Function Block CLEARS the bit (to 0)
immediately, then acts on the request if possible

Edge triggering allows multiple senders per Command,

Setting, Configuration or Input (many-to-one relationship)

Level • Action ("enable") is triggered by input being at a level

(in a state, usually 1)
• Opposite action ("disable") is triggered by input being
in opposite state (0)
• Sending logic SETS the bit (writes a 1) or CLEARS
the bit (writes a 0); this Function Block does not
change the bit

Level triggering allows only one sender can drive each

Level

All Operator Commands (OCmd_) and Maintenance

Commands (MCmd_) are Edge triggered. The HMI graphic
object or faceplate SETS (writes a 1 to) each Command bit
and the Function Block CLEARS (writes a 0 to) the
Command bit, then performs the function, if possible.

Publication KGEOB10001-00008 - December, 2017 iii

Preface

This Safety Module has Program Commands (PCmd_).

All Program Commands are Edge triggered. The
application logic will SET (write a 1 to) each Command bit
and the Function Block will CLEAR (write a 0 to) the
Command bit, then performs the function, if possible.

Function Block States

The controller evaluates function block instructions based on the state of
different conditions.

Possible Condition: Description:

First scan First scan refers to the first time an instance of

the Function Block is performed. The Function
Block may contain code to normalize the instance
(e.g. clear commands).
NOTE: The controller will always read current
inputs and determine the appropriate state to be
in.

iv Publication KGEOB10001-00008 - December, 2017

 Table of Contents

Updated Information............................................................................................................................... i

Introduction ........................................................................................................................................... ii

Common Information for All Function Blocks ..................................................................................... ii

Conventions and Related Terms ......................................................................................................... iii

OVERVIEW ..................................................................................................................... 1
Functional Overview.............................................................................................................................. 2

Primary Operations ............................................................................................................................... 6

Modes of Operation ............................................................................................................................... 6

AADvance Code and Data Size ............................................................................................................ 7

Alarms .................................................................................................................................................... 8

QUICK START ................................................................................................................ 9

Import/Update Components ................................................................................................................ 10
Import FactoryTalk View SE ActiveX Component ............................................................................................ 10
Import AADvance Supporting Function Components ........................................................................................ 11
Import AADvance SM_V2S Component ........................................................................................................ 12
Import FactoryTalk View SE Image Components ............................................................................................. 12
Import FactoryTalk View Global Components ................................................................................................. 13
Import FactoryTalk View SE SM_V2S Components ......................................................................................... 14

Instantiate ............................................................................................................................................ 15

Configure ............................................................................................................................................. 17

Map I/O ................................................................................................................................................. 18

Create Interface Logic ......................................................................................................................... 18

Examples ............................................................................................................................................. 19
Scenario 1 ............................................................................................................................................ 19
Scenario 2 ............................................................................................................................................ 21

CONFIGURATION OPTIONS ....................................................................................... 24

Configuration Parameters ................................................................................................................... 24

DATA REFERENCE ..................................................................................................... 30

Configuration (Cfg_) ............................................................................................................................ 30

Publication KGEOB10001-00008 - December, 2017 v

Table of Contents

Mode Commands (PCmd_, OCmd_, MCmd_) and Mode Readies ..................................................... 32

Mode Commands ................................................................................................................................... 33
Mode Command Readies ......................................................................................................................... 33

Program Device Commands (PCmd_) ................................................................................................ 34

Device Commands.................................................................................................................................. 34

Operator Device Commands (OCmd_), Maintenance Device Commands (MCmd_), and Readies
(Rdy_) ................................................................................................................................................... 35
Device Commands.................................................................................................................................. 35
Device Command Readies ........................................................................................................................ 36

Values (Val_) ........................................................................................................................................ 37

Status (Sts_) ........................................................................................................................................ 38

Device Status ........................................................................................................................................ 38
Mode Status.......................................................................................................................................... 39

HMI REFERENCE......................................................................................................... 42
Graphic Object..................................................................................................................................... 42
Graphical Representation ......................................................................................................................... 43
Mode Indicators ..................................................................................................................................... 44
Status Qualifier Indicators ......................................................................................................................... 45
Alarm Indicator....................................................................................................................................... 45

Faceplate.............................................................................................................................................. 47
FactoryTalk View ® Diagnostics ................................................................................................................. 48
Operator Tab ......................................................................................................................................... 49
Alarm Tab............................................................................................................................................. 52
Help Tab .............................................................................................................................................. 55
Maintenance Tab.................................................................................................................................... 57
Configuration - Device Tab ........................................................................................................................ 60

vi Publication KGEOB10001-00008 - December, 2017

 Chapter 1

Overview
The SM_V2S (Two State Valve) object controls a Two State Valve in a
variety of modes and monitors for fault conditions. The Two State
Valve Function Block controls a single AADvance digital output, and
includes the capability to generate related digital output alarms, such
as Failed To Open, Failed To Close, and/or Illegal Feedback.
The Two State Valve Function Block includes the following
functionality
• Allows manual control of the valve output (when not in a
tripped state) by authorized personnel to handle testing or a
faulted input.
• Allows Maintenance Bypass by authorized personnel to carry
out maintenance work on the field device.
• Allows configuration of the Mean Time To Repair (MTTR), to
enable the object to alarm or alarm and shutdown a faulty
output after the configured time.

Use when:
• As part of the Safety Instrumented Function (SIF)
implementation you want to interface to a Two State Valve
which requires a single Digital Output (i.e. a single solenoid).
• You need to monitor and confirm the state of a Two State
Valve and produce alarms based on failed confirmation.
• You need to apply mode, permissives and interlocks to the
Digital Output.

Do NOT use when:

• You want to control a simple digital output, use custom logic or
the SM_DOUT instead.
• You want to interface with a control valve, use custom logic
instead.
• You want to control a motor, use SM_DOUT for basic control
with feedback. For more extensive motor interface, use
custom logic instead.
• You only want to display the state of an output on the HMI,
and do not require alarming, mode, feedback monitoring.

Publication KGEOB10001-00008 - December, 2017 1

Chapter 1 Overview

Functional Overview
The following diagram provides an overview of the functionality of the module – it does NOT contain all
logical aspects. Of particular note are the absence of latches for statuses, the absence of ‘Configuration’
variables, and the effect of Disable on Safety Module functionality. For full functionality details, refer to
later sections of this document.

(Timer Configuration Settings) Config

Status1.5
Check
Logic
(Config Error)
(Timer Values)

State
DO T9K.STA Validity
Check

State
Close Limit T9K.STA Validity Status1.7
Check OR (IO Fault)

State
Open Limit T9K.STA Validity
Check
Status1.4
(Discrepancy)
DO T9K.DIS

Close Limit T9K.DIS OR

Open Limit T9K.DIS

Status1.1
MCmd_MaintBypEnbl
Activate Maintenance Bypass
T (MaintByp Enabled)

Remove Maintenance Bypass Status1.0

MCmd_MaintBypRmv TON
(MaintByp PreExp)

(Maintenance Bypass Pre-Expiration Limit)

Status1.15
TON
(MaintByp Expired)

Val_MaintBypTime
Val_MaintBypRT

2 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

Functional Overview (cont.)

Status1.13
(Loss of Closed)

Status2.1
(Any Close Command)
(Closed)
(A command to close the valve issued by either Operator
or Maintenance users or by Program control.)
Status2.3
Close Limit T9K.DI
(Closing)
Position
Status
Logic
Status2.4
Open Limit T9K.DI
(Opening)

(Any Open Command)

Status2.2
(A command to open the valve issued by either Operator
(Opened)
or Maintenance users or by Program control.)

Status1.14
(Loss of Opened)

Status1.10
AND
(Illegal Feedback)

Status1.11
AND TON
(Close Full Stall)
(Any Close Command)
(A command to close the Val_FullStallT
valve issued by either
Operator or Maintenance Status1.13 Status1.8
users or by Program
(Loss of Closed)
OR (Failed To Close)
control.)

AND TON
NOT
Val_TransitStallT

Status1.12
AND TON
(Open Full Stall)
(Any Open Command)
(A command to open the Val_FullStallT
valve issued by either
Operator or Maintenance Status1.14 Status1.9
users or by Program
(Loss of Opened)
OR (Failed To Open)
control.)

AND TON
NOT
Val_TransitStallT

Publication KGEOB10001-00008 - December, 2017 3

Chapter 1 Overview

Functional Overview (cont.)

MCmd_OOSRmv
Enable Device

Status1.6
MCmd_OOSEnbl
Disable Device
T (Disabled)

Status2.13
(Operator Mode)

(Program / Operator Mode Commands)

Mode Status2.14
Logic (Program Mode)
Status1.1
(MaintByp Enabled)

Status2.15
(ProgOperLock)

Status1.5
NOT
(Config Error) Status2.12
AND
(Available)
Status1.6
NOT
(Disabled)

Status1.7
(IO Fault) Status1.2
TON
(MTTR PreExp)

Status1.8 (MTTR Pre-Expiration Limit)

(Failed To Close)
Status1.3
OR TON
(MTTR Exp)
Status1.9
(Failed To Open) Val_MTTR
Val_MTTRRT
Status1.10
(Illegal Feedback)

4 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

Functional Overview (cont.)

Status2.8
Inp_NBIntl
(Non-Bypassable Interlock Input) (NB Interlock Sts)

Status2.9
Inp_Intl
(Bypassable Interlock Input) (Interlock Sts)

Status2.10
Inp_NBPerm
(Non-Bypassable Permissive Input) (NB Permissive Sts)

Status2.11
Inp_Perm
(Bypassable Permissive Input) (Permissive Sts)

(Any Close Command)

(A command to close the valve issued by either Operator
or Maintenance users or by Program control.) OUT
(Any Open Command)
(A command to open the valve issued by either Operator Output
or Maintenance users or by Program control.) Sense
Status2.0
&
Permissive (Sts_Out)
Logic
Status1.6
(Disabled)

Status1.3 Normally Energized /

(MTTR Exp) De-Energized configuration

LEGEND
Miscellaneous Main
Analog Discrete
Input/Output Input/Output

Input 1
Input 1 OR / AND Gate
Input Selector OR Output Logical OR / AND of ‘n’ Boolean inputs
Input 2 T Output Input 2 (only two shown in example OR gate)

Input to be checked >= Analog Comparator

Output
Input to be checked against Analog comparison with optional deadband.
Performs comparison between an analog input and an analog value of the
same type.
Deadband Value Analog comparison may be <, <=, >, >=, =, or <>.
(If 0 then con nector is optional) Deadband is not applicable to = or <>.
(Not applicable for = and <> compare)

Timer
Input TON Output
Timer function with optional ‘Remaining Time’ output.
Generates output based on timer type, Input status, and configured time ‘t’.
t Type may be TON (Timer ON delay), TOF (Timer OFf delay), or TP (Time Pulse).
Remaining Time
(optional)

Publication KGEOB10001-00008 - December, 2017 5

Chapter 1 Overview

Primary Operations The primary operations of the SM_V2S (Two State Valve) are to:
• Energize a solenoid to open the valve, or in the case of a
reverse acting (“fail open”) valve close the valve.
• Monitor optional open feedback and/or optional closed
feedback and display actual Valve status.
• Detect and alarm Failure to Open (feedback signal
confirming opened status not achieved with in defined
period), and Loss of Opened alarm (open limit made then
lost)
• Detect and alarm Failure to Close (feedback signal
confirming closed status not achieved with in defined period),
and Loss of Closed alarm ( closed limit made then lost)
• Monitor permissive conditions to prevent Valve operation.
• Monitor interlock conditions to drive Valve to ‘tripped’ state.
• Operate in maintenance, program and operator modes.
• Allow Maintenance Bypass of the device, available based on
security log in.
• Provide an “available” status, to indicate the Valve is
available for operation.

Modes of Operation The SM_V2S (Two State Valve) uses the following standard modes
implemented using embedded logic.

Mode Description

Operator The operator opens and closes the Valve using

the HMI faceplate.

Program Logic outside the SM_V2S opens and closes

the Valve using Program Commands.

Maintenance Maintenance personnel have control of the

Valve using the HMI faceplate and it is not
available for normal operation by operators or
program logic; bypassable interlocks, and
bypassable permissives are bypassed.

6 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

AADvance The SM_V2S will use the following space (code and data) in the
AADvance controller:
Code and Data Size
Component Overhead Per Instance

Code Config Code Config

(Bytes) (Bytes) (Bytes) (Bytes)

Func_LimAlmSeverity 296 28 N/A* N/A*

Func_LimTIME 344 12 N/A* N/A*

Func_ValNotify 1,112 132 N/A* N/A*

SM_V2S 32,576 532 422 3,140

* The code and config space for these functions is included in the
instantiated data for this Function Block.

The AADvance controller has the following limits,

which cannot be exceeded for an application.
Code space: 524,288 bytes
Config space: 655,360 bytes
Note: ‘Code Space’ is ISaGRAF Space 1.
‘Config Space’ is ISaGRAF Space 3.
For an application, the sum of ALL Safety Modules
plus all additional application logic and variables
MUST be with the limits specified above.

Publication KGEOB10001-00008 - December, 2017 7

Chapter 1 Overview

Alarms The SM_V2S (Two State Valve) has the following FactoryTalk View
alarms.

Alarm Description

* Failed to Close While Closing, failed to receive the Closed confirmation

feedback within the configured time period

* Loss of Closed Upon reaching the "Confirmed Closed" state, the

Closed confirmation feedback is lost

* Close Full Stall While Closing, failed to lose the Opened confirmation
feedback within the configured time period

* Failed to Open While Opening, failed to receive the Opened

confirmation feedback within the configured time period

* Loss of Opened Upon reaching the "Confirmed Opened" state, the

Opened confirmation feedback is lost

* Open Full Stall While Opening, failed to lose the Closed confirmation
feedback within the configured time period

Illegal Feedback Opened and Closed confirmation (limits) are both active
at the same time.

I/O Fault / An I/O failure has occurred, or communications with I/O

Discrepancy has been lost

MaintBypPreExp The Maintenance Bypass is within the configured Pre-

Expiration limit

MaintBypExp The Maintenance Bypass has expired

MTTRPreExp The Mean Time To Repair (MTTR) is within the

configured Pre-Expiration limit

MTTRExp The Mean Time To Repair (MTTR) has expired

* The Loss of Opened, Open Full Stall and Failed to Open

alarms share a single common alarm. Similarly, the Loss
of Closed, Close Full Stall and Failed to Close alarms
share a single alarm instruction.
The Open and Close Full Stall alarms share the
Cfg_FullStallTime attribute.
The Open and Close Transit Stall alarms share the
Cfg_TransitStallTime attribute.
All other attributes are shared with the Failed to Open /
Failed To Close alarm respectively:

8 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

Quick Start
The Quick Start section is intended to provide a brief overview of the
steps required to implement a SM_V2S instance within your Controller
and HMI applications. Additional, detailed, information may be found in
the remainder of this document.

This section outlines the following:

• Import components
• Instantiate
• Configure
• Map I/O
• Create Interface Logic

Publication KGEOB10001-00008 - December, 2017 9

Chapter 1 Overview

The Import/Update Components section details how to bring the

Import/Update relevant components into the controller and visualization environment.
Components Instructions are provided to enable a step-by-step installation.

These sections detail bringing support components and safety modules

in to AADvance Workbench and global object, graphical files, HMI Tags
and FTAE components in to FactoryTalk View SE.

The files specified in the following sections are available from the
Package Downloader (search for ‘Process Safety Toolkit’). To install the
Package Downloader and be provided with access to the relevant
software, contact your regional GEMS Champion.

Import FactoryTalk View SE ActiveX Component

This component is common to all GEMS Process

Safety Toolkit safety modules and therefore needs to
be imported into your application one time only.

Perform the following steps to import the ActiveX component into your
FTView application. The provided data entry ActiveX file HMI-ActiveX-
Setup.exe needs to be registered on FTView SE server computers
and each client computer.
On HMI serve computer:
1. Copy HMI-ActiveX-Setup.exe to the following location:
C:\Users\Public\Documents\RSView Enterprise \ActiveX
Control Setup
2. Run the HMI-ActiveX-Setup.exe by double click the file.
On HMI client computer:
1. Copy HMI-ActiveX-Setup.exe to any location.
2. Run the HMI-ActiveX-Setup.exe by double-clicking the file.

10 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

If starting with the GEMS Process Safety Toolkit

Starter Kit application, the steps outlined in the
following sections are not required, as the necessary
components are present within the GEMS Process
Safety Toolkit Starter Kit Controller and HMI
applications.

Import AADvance Supporting Function Components

These components are common to all GEMS

Process Safety Toolkit safety modules and therefore
need to be imported into your application one time
only.

Perform the following steps to import the supporting Functions into

your AADvance Controller application:
1. Store the following provided PXF files in a known location.
Func_LimAlmSeverity
Func_LimReal
Func_LimTime
Func_ValNotify
Func_StructureImport
2. Open your AADvance Workbench project.
3. From the menu bar, click File > Import > Exchange File.
4. Select ‘Import from file’. Click Next.
5. Click ‘Browse’, and select the first of the Functions listed
above from the location in which you stored it (as per step 1).
Click Next.
6. Ensure the Function is selected in the Import Exchange File
window. Click Next.
7. Ensure the name is the same as the Function. Click Next.
8. Wait for the import to complete.
9. Repeat for all the Functions listed in step 1.
10. Click Close.
11. Delete the Func_StructureImport Function POU. This POU is
only required to import additional structures for the application
and is not required at runtime.

Publication KGEOB10001-00008 - December, 2017 11

Chapter 1 Overview

Import AADvance SM_V2S Component

Perform the following steps to import the SM_V2S Function Block into
your AADvance Controller application:
1. Store the provided SM_V2S.PXF file in a known location.
2. Open your AADvance Workbench project.
3. From the menu bar, click File > Import > Exchange File.
4. Select ‘Import from file’. Click Next.
5. Click ‘Browse’, and select the SM_V2S.pxf from the location in
which you stored it (as per step 1). Click Next.
6. Ensure the Function Block is selected in the Import Exchange
File window. Click Next.
7. Ensure the name is SM_V2S. Click Next.
8. Wait for the import to complete.
9. Click Close.

Import FactoryTalk View SE Image Components

These components are common to all GEMS

Process Safety Toolkit safety modules and therefore
need to be imported into your application one time
only.

Perform the following steps to import the FactoryTalkView Image

components into your FTView application. The provided GEMS
Process Safety Toolkit Images.zip file needs to be installed on FTView
SE server computers only.

1. Copy GEMS Process Safety Toolkit Images.zip to any

location.
2. Extract the images by right-clicking on the zip file and
selecting ‘Extract to here’ (may be ‘Unzip to here’ or similar,
depending on installed software and Operating System).
3. Open your FTView HMI project using FTView Studio
4. Within FTView Studio, navigate to Images, then right click and
select ‘Add Component Into Application’.
5. Select all the extracted graphics files (.bmp) from the location
in which you stored them (step 1). Then select/click Open.

12 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

Import FactoryTalk View Global Components

These components are common to all GEMS

Process Safety Toolkit safety modules and therefore
need to be imported into your application one time
only.

Perform the following steps to import the global graphic components

into your FTView application:
1. Store the following provided files in a known location:
Global Object files:
(RA-SIS) GO_SIS_Alarm.ggfx
(RA-SIS) GO_SIS_Analog.ggfx
(RA-SIS) GO_SIS_Common.ggfx
(RA-SIS) GO_SIS_Configuration.ggfx
(RA-SIS) GO_SIS_Digital.ggfx
(RA-SIS) GO_SIS_Help.ggfx
(RA-SIS) GO_SIS_Maintenance.ggfx
(RA-SIS) GO_SIS_Mode.ggfx
(RA-SIS) GO_SIS_Valve.ggfx
Graphic files:
(RA-SIS) F_Data_Entry_Num.gfx
(RA-SIS) F_Data_Entry_Num_wUOM_Cfm.gfx
(RA-SIS) F_SM_ALARM-Faceplate.gfx
(RA-SIS) F_SM_ALARM-Help.gfx
(RA-SIS) F_SM_ALARM-Shelve.gfx
2. Open your FTView HMI project using FTView Studio
3. Within FTView Studio, navigate to Global Objects, then right
click and select ‘Add Component Into Application’
4. Select the global objects file (.ggfx) from the location in which
you stored them (step 1). Then select/click Open.
5. Within FTView Studio, navigate to Displays, then right click
and select ‘Add Component Into Application’.
6. Select the graphics files (.gfx) from the location which you
stored them (step 1). Then select/click Open.

Publication KGEOB10001-00008 - December, 2017 13

Chapter 1 Overview

Import FactoryTalk View SE SM_V2S Components

Perform the following steps to import the SM_V2S graphic

components into your FTView application:
1. Store the following provided files in a known location:
Global Object file:
(RA-SIS) SM_V2S-Library.ggfx
Graphic files:
(RA-SIS) F_SM_V2S-Config.gfx
(RA-SIS) F_SM_V2S-ConfirmMaintCmd.gfx
(RA-SIS) F_SM_V2S-Faceplate.gfx
(RA-SIS) F_SM_V2S-Help.gfx
Supporting files:
SM_V2S_HMITags.csv
SM_V2S_FTAE.xls
SM_V2S_KEPServer.csv
2. Open your FTView HMI project using FTView Studio
3. Within FTView Studio, navigate to Global Objects, then right
click and select ‘Add Component Into Application’
4. Select the global objects file (.ggfx) from the location in which
you stored it (step 1). Then select/click Open.
5. Within FTView Studio, navigate to Displays, then right click
and select ‘Add Component Into Application’.
6. Select the graphics files (.gfx) from the location which you
stored them (step 1). Then select/click Open.
7. Within FTView Studio, in the menu bar click Tools and then
‘Tag Import and Export Wizard’.
8. Under Operation, select ‘Import FactoryTalk View tag CSV
files’. Click Next.
9. Change Project Type to ‘Site Edition’.
10. Navigate to the project SED file using the browse (P) button.
Double-click the SED file to select the project. Click Next.
11. Ensure Tags is checked. Using the browse (P) button, select
the HMI Tags file (.csv) from the location in which you stored it
(step 1). Click Next.
12. Select ‘Update existing’. Click Next, and then click Finish.
13. Review the message window to ensure that there were no tag
import failures. Close the window.
14. Within FTView Studio, navigate to the FTAE server, then right
click and select ‘Import and Export’
15. Select ‘Import alarm configuration file from Excel file’. Click
Next.
16. Using the browse (P) button, select the FTAE file (.xls) from
the location in which you stored it (step 1). Click Next.
17. Select ‘Update existing alarm definitions and create new
alarms definitions from the import file’. Click Finish.
18. Within KEPServerEX navigate to Device, then right click and
select ‘Import CSV’
19. Using the browse (P) button, select the KEPServer CSV file
(.csv) from the location in which you stored it (step 1). Click
Next.

14 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

Determine whether the new module instance you want to create needs
Instantiate a Global or Local scoped tag.
1. A Global scoped tag is used when interface to the module is
required across multiple Programs.
2. A Local scoped tag is only available for use inside the
Program in which it resides.

The following steps are required to instantiate a SM_V2S module

within the AADvance controller program.
NOTE: The following assumes that the I/O is already specified and
wired, all required Program POUs have been created, and system
Maintenance Bypass and Reset variables have been created.
1. Open the AADvance Dictionary.
2. Double-click on the ‘P’ icon at the bottom of the Dictionary
variables.
3. Assign tag Name (for example, SDV_121), and select Type
S_V2S. Enter a Comment if desired (for example, Process
Shutdown Valve).
4. For Global tags, set the Scope as Global. For Local tags,
select the appropriate Program name from the list.
5. Click OK.
6. Select the desired Program within the application to create the
SM_V2S instance.
7. Create the SM_V2S instance by selecting Function Block (F3)
from the Language Toolbar, and clicking in the Program where
the instance should be created. Select SM_V2S from the list
of available Function Blocks.
8. Connect the instance tag created in step 3 to the SV2S pins (1
input, 1 output).
9. Connect the appropriate field output tag (Type T9K_DO_Full)
to the V2S pin.
10. Connect the appropriate field output tag DOP element (Type
BOOL) of the variable in step 9 to the Out pin. Note: This can
be entered by switching to Manual Input under the Options.
11. Connect the appropriate Closed and Opened Limit Switch field
input tag (Type T9K_DI_Full) to the CLS and OLS pins
respectively.
12. Connect the appropriate Maintenance Bypass Enable,
Remove and Reject tags (Type BOOL) to the ByME, ByMR
and ByRj pins respectively.
13. Connect the appropriate Reset tag (Type BOOL) to the Rst
pin.
14. Connect the appropriate non-bypassable and bypassable
interlocks from the application logic to the NBIL and IL pins
respectively.
15. Connect the appropriate non-bypassable and bypassable
permissives from the application logic to the NBPm and Perm
pins respectively.

Publication KGEOB10001-00008 - December, 2017 15

Chapter 1 Overview

All input pins on the Function Block (i.e. those on the

left-hand side) MUST be connected.
If an input is not required to be used, then an inline
constant (such as ‘TRUE’ or ‘FALSE’) or a ‘dummy’
variable of the appropriate type must be created and
connected.

The following steps are required to instantiate a SM_V2S module

within your FTView application:
1. Within FTView Studio, create or open the graphic file
associated with the screen (typically an overview screen) on
which you wish to place the SM_V2S Icon (device symbol).
2. Open the module library file (RA-SIS) SM_V2S-Library.ggfx
from Global Objects directory.
3. Select the desired Graphic Object from the module library file,
and copy to the overview screen.
4. Associate the Graphic Object with the SM_V2S tag in the
controller.
a. Select the (copied) Graphic Object from the overview
screen, right click and open the “Global Object
Parameter Values” window.
• Set parameter #102 to the SM_V2S tag within the
controller (for example XL_402)
• Set parameter #103 to the Controller path which
contains the SM_V2S tag. Format:
/<SERVERNAME>::[<AREA>], where the
SERVERNAME is what you configured on FTView
SE Data Server, such as KEPServerEX, and the
AREA is the area name in the data server
(for example /KEPServer::ModbusTCP.Train1).
• Set parameter #104 to the HMI Server path which
contains the SM_V2S tag. Format:
/<SERVERNAME>::[<AREA>], where the
SERVERNAME is what you configured on FTView
SE HMI Server and the AREA is the area name in
the HMI server
(for example CCR::RA-SIS\Train1\SM_V2S\).
• Set parameter #105 to the FTAE Server path
which contains the SM_V2S tag. Format:
/<SERVERNAME>::[<AREA>], where the
SERVERNAME is what you configured on FTView
FTAE Server and the AREA is the area name in
the FTAE server
(for example /FTAEServer::Train1_).

When using Global Objects with parameters it is

not possible to break links to global objects.

16 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

The SM_V2S module is provided with certain default configuration

Configure settings. See the Configuration section of this document for default
configuration details.

Prior to modifying the configuration of your new SM_V2S instance,

consider the following:
• Physical device characteristics
• Alarming
• Program Interface
• HMI Interface

You may modify the configuration of a SM_V2S instance using either

of the following methods.

NOTE: Process Safety Toolkit applications can only be configured

through the AADvance application; no instance configuration is
possible through FTView, with the exception of string variables (Tag
Name and Description).

1. Modify instance data using AADvance Workbench (may be

modified offline) when using Initial Values to configure
instances. Note: the updated value will only take effect after a
controller restart.
• Navigate to (and monitor) the tag associated with the
SM_V2S instance, within the controller project.
• Expand the tag to view the underlying data elements.
• Select the Configuration (Cfg_) data element you wish to
modify.
• Enter the new value in the Initial Value field.
• Compile and download to the controller.

2. Modify instance data using AADvance Workbench (may be

modified offline) when using application logic to configure
instances. Note: the updated value will take effect immediately
(unless any ‘First Scan’ logic is implemented).
• Navigate to the program containing the configuration
parameters associated with the SM_V2S instance, within
the controller project.
• Select the Configuration (Cfg_) data element you wish to
modify.
• Enter the new value in the application logic.
• Compile and download to the controller.

Publication KGEOB10001-00008 - December, 2017 17

Chapter 1 Overview

In order to control the physical device, you must “map” the Input and
Map I/O Output interface points from the SM_V2S instance to the I/O cards
which contain the hardwired I/O for the physical device.

First determine the physical I/O associated to the device for which you
are creating the SM_V2S module instance. For the SM_V2S module,
the following I/O is used:

Field I/O (Pin) Mandatory Direction Variable Type

Valve Output Y Output T9K_DO_FULL

(V2S)

Closed Limit Switch N Input T9K_DI_FULL

(CLS)

Open Limit Switch N Input T9K_DI_FULL

(OLS)

Steps required to map SM_V2S I/O:

• Open the program in which you have created the SM_V2S
module instance, and navigate to the appropriate instance.
• Connect the appropriate Field I/O variable to the appropriate
pin on the SM_V2S function block.

NOTE: If a Field I/O point is not mandatory and is not being used in
the configuration, it is necessary to create a ‘dummy’ variable of the
same type.

In order to control/monitor the physical device, you will need to utilize

Create Interface Logic various SM_V2S interface points within your logic.

The following are the typical Interface Points to be used within your
logic:
• Commands (PCmd_) – Used to issue commands
• Statuses (Sts_) – Used to monitor status
• Values (Val_) – Used to monitor analog values
• Permissives (Perm, NBPm) – Used to enable/disable device
control
• Interlocks (IL, NBIL) – Used to drive the device to demand state

18 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

Examples Scenario 1
• Emergency Blowdown Valve (BDV1001) is a normally-
energized, normally closed valve with no limit switches.
• BDV1001 has one defined interlock, PAHH1001, which must
never be bypassed.
• All Alarms are not latched, and once the cause of the failure
has cleared the blowdown valve should return to the closed
position.
• In addition, the module shall annunciate the I/O Fault alarm if
the I/O module detects a fault.
• BDV1001 is controlled only by the application logic within the
controller; no manual command or Maintenance Bypass is
permitted.

Name: Value:
BDV1001.Cfg_Tag BDV1001
Tank 2
BDV1001.Cfg_Desc
Temperature

BDV1001.Cfg_MaintBypTime T#12hr
BDV1001.Cfg_MaintBypPreExpLim T#1hr
BDV1001.Cfg_MTTR T#12hr
BDV1001.Cfg_MTTRBypPreExpLim T#1hr

BDV1001.Cfg_FullStallTime T#5s
BDV1001.Cfg_TransitionStallTime T#10s

BDV1001.Config1 128
Config1.0 (Maint Byp) 0
Config1.1 (Spare) 0

Config1.2 (MTTR) 0
Config1.3 (Spare) 0

Config1.4 (Spare) 0
Config1.5 (Spare) 0
Config1.6 (Enable/Disable) 0
Config1.7 (IOFault) 1
Config1.8 (Failed To Close) 0

Config1.9 (Failed To Open) 0

Config1.10 (Illegal Feedback) 0
Config1.11 (Closed Limit Switch) 0

Config1.12 (Opened Limit Switch) 0

Config1.13 (V & I displayed) 0

Config1.14 (Spare) 0
Config1.15 (Spare) 0
BDV1001.Config2 9
Config2.0 (Output auto-reset) 1

Publication KGEOB10001-00008 - December, 2017 19

Chapter 1 Overview

Config2.1 (Safe State on MTTR) 0

Config2.2 (NDE output) 0
Config2.3 (NC valve) 1
Config2.4 (Spare) 0
Config2.5 (Spare) 0
Config2.6 (Spare) 0
Config2.7 (Spare) 0

Config2.8 (Latch alarms) 0

Config2.9 (Latch IOFault) 0
Config2.10 (Spare) 0
Config2.11 (Spare) 0
Config2.12 (Prog Mode > Oper) 0
Config2.13 (Prog Mode default) 0
Config2.14 (Spare) 0
Config2.15 (Spare) 0

The table above represents the configuration required to

implement this example.
The sample logic shown above may be found in the
following logic export: SM_V2S_Scenario1_RTN.PXF.

20 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

Scenario 2
• Shutdown Valve (ESV8005) is a normally-energized, normally
open solenoid valve with open (ESZO8005) and closed
(ESZC8005) limit switches.
• ESV8005 has connections to various programs within the
controller. These connections are combined externally into two
interlocks; one defined interlock (ESV8005_NBIL) must never
be bypassed, and another (ESV8005_IL) may be bypassed.
• All Alarms are configured (I/O Fault, Fail To Open, Failed To
Close, Illegal Feedback) and must be latched. Once the cause
of the failure has cleared the shutdown valve should not return
to the opened position until commanded to do so by the
operator.
• A non-bypassable permissive (ESV8005_NBPerm) is also
connected to allow the operator to open the valve only when
permitted.
• Maintenance Bypass is allowed. A 12-hour limit is applied to
all Maintenance Bypasses, with a 45-minute warning before
expiration.
• The valve SIF has a defined MTTR of 48hrs, but the valve
shall take no action on expiration. The end-user requests a
warning 1-hour before the MTTR expires so that they may
prepare to take action manually.
• The valve should close within 5-seconds of demand, and
should appear to have started closing within 2 seconds.
• The valve is part of a multi-train process, and may be disabled
by the operator if the process train is not in use.
• The operator wishes to see the valve voltage and current on
the faceplate.

Name: Value:

ESV8005.Cfg_Tag ESV8005
Tank 2
ESV8005.Cfg_Desc
Temperature

ESV8005.Cfg_MaintBypTime T#12hr
ESV8005.Cfg_MaintBypPreExpLim T#45min
ESV8005.Cfg_MTTR T#48hr
ESV8005.Cfg_MTTRBypPreExpLim T#1hr

ESV8005.Cfg_FullStallTime T#2s
ESV8005.Cfg_TransitionStallTime T#5s
ESV8005.Config1 16325
Config1.0 (Maint Byp) 1
Config1.1 (Spare) 0

Config1.2 (MTTR) 1
Config1.3 (Spare) 0
Config1.4 (Spare) 0
Config1.5 (Spare) 0
Config1.6 (Enable/Disable) 1

Publication KGEOB10001-00008 - December, 2017 21

Chapter 1 Overview

Config1.7 (IOFault) 1
Config1.8 (Failed To Close) 1
Config1.9 (Failed To Open) 1
Config1.10 (Illegal Feedback) 1
Config1.11 (Closed Limit Switch) 1
Config1.12 (Opened Limit Switch) 1
Config1.13 (V & I displayed) 1

Config1.14 (Spare) 0
Config1.15 (Spare) 0
ESV8005.Config2 776
Config2.0 (Output auto-reset) 0
Config2.1 (Safe State on MTTR) 0
Config2.2 (NDE output) 0
Config2.3 (NC valve) 1
Config2.4 (Spare) 0

Config2.5 (Spare) 0
Config2.6 (Spare) 0

Config2.7 (Spare) 0
Config2.8 (Latch alarms) 1
Config2.9 (Latch IOFault) 1
Config2.10 (Spare) 0
Config2.11 (Spare) 0
Config2.12 (Prog Mode > Oper) 0
Config2.13 (Prog Mode default) 0

Config2.14 (Spare) 0
Config2.15 (Spare) 0

The table above represents the configuration required to

implement this example.
The sample logic shown above may be found in the
following logic export: SM_V2S_Scenario2_RTN.PXF.

22 Publication KGEOB10001-00008 - December, 2017

 Chapter 1 Overview

Notes:

Publication KGEOB10001-00008 - December, 2017 23

 Chapter 2
Configuration Options

Configuration Enter the appropriate values from the following table into the SM_V2S
Function Block instance’s configuration parameters to configure it for
Parameters your application.
Use FactoryTalk View to set the string parameters, and AADvance
Workbench to set the applicable Configuration Parameters.
The parameters are organized into tables of functional subgroups
below which are also associated with a supporting HMI faceplate.
Note: Replace the string “<alarm>” in the generic element name with
any of the following specific alarm names to get the specific element:
• FailedToClose (inc. Loss of Closed and Open Full Stall)
• FailedToOpen (inc. Loss of Opened and Close Full Stall)
• IllegalFeedback
• IOFault
• MaintBypPreExp
• MaintBypExp
• MTTRPreExp
• MTTRExp

Configuration – HMI Interface: These parameters determine the text displayed on the Faceplate, command confirmation and
other HMI attributes.

See HMI Reference – Configuration - Device Tab,, page 60

Parameter: Default: Usage: Associated Parameters

Cfg_Tag SM_V2S_TAGNAME Device ID. Store the Device ID (Device tag) of

this device. This information is displayed on the
Faceplate.
Cfg_Desc SM_V2S_DESCRIPTION Device Description. Stores the text Description
of this device. This information is displayed on
the Faceplate.

Publication KGEOB10001-00008 - December, 2017 24

 Chapter 2 Configuration Options

Configuration – Alarms: These parameters determine the behavior of Valve alarms, including whether or not the alarm is
actively evaluated.

Parameter: Default: Usage: Associated Parameters

Config1.0 1 Maintenance Bypass enabled and will be MaintBypPreExp_Alm

processed. MaintBypExp_Alm
Config1.2 1 Mean Time To Repair (MTTR) enabled and will MTTRPreExp_Alm
be processed. MTTRExp_Alm
Config1.7 1 IOFault Condition enabled and will be IOFault_Alm
processed.
Config1.8 1 Failed To Close Condition enabled and will be FailedToOpen_Alm
processed.
Config1.9 1 Failed To Open Condition enabled and will be FailedToClose_Alm
processed.
Config1.10 1 Illegal Feedback enabled and will be IllegalFeedback_Alm
processed.
Config2.8 1 Alarm Reset Required. <alarm>_Alm
OCmd_Reset
When this parameter is: Inp_Reset

• Set (=1)
Each Valve alarm Latches. The user (HMI
or Logic) must issue a reset command after
the alarm condition returns to normal.

• Clear (=0)
The module automatically clears each Valve
alarm when the alarm condition returns to
normal

Publication KGEOB10001-00008 - December, 2017 25

Chapter 2 Configuration Options

Parameter: Default: Usage: Associated Parameters

Config2.9 1 IOFault Reset Required. IOFault_Alm

OCmd_Reset
When this parameter is: Inp_Reset

• Set (=1)
The IOFault alarm Latches. The user (HMI
or Logic) must issue a reset command after
the alarm condition returns to normal.

• Clear (=0)
The module automatically clears the IOFault
alarm when the alarm condition returns to
normal
Cfg_<alarm>Severity 1 Configuration value for <alarm> Severity: Val_Notify
1..250=Low,
251..500=Medium
501..750=High
751..1000=Urgent

These parameters determine the Priority of

Valve alarms.

Configuration – Alarm Thresholds, Deadband, & Duration: These parameters determine the levels at which each specific
Valve alarm is triggered and cleared.

Parameter: Default: Usage: Associated Parameters

Cfg_MaintBypTime T#8hr Configured Maintenance Bypass Timer. Config1.0

Val_MaintBypTime
This is used to turn off the Maintenance Bypass
after the configured time, and generate the
Maintenance Bypass Expired alarm.
Cfg_MaintBypPreExpLim T#30m Configured Maintenance Bypass Pre-Expiration Config1.0
Warning Timer. Val_MaintBypTime

This is used to generate the Maintenance

Bypass Pre-Expiration alarm.
Cfg_MTTR T#24hr Configured MTTR Timer. Config1.2
Val_MTTRT
This is used to drive the output to the safe state
(if configured to Trip on MTTR Expiration) after
the configured time, and generate the MTTR
Expired alarm.

26 Publication KGEOB10001-00008 - December, 2017

 Chapter 2 Configuration Options

Parameter: Default: Usage: Associated Parameters

Cfg_MTTRPreExpLim T#4hr Configured MTTR Pre-Expiration Warning Config1.2

Timer. Val_MTTRT

This is used to generate the MTTR Pre-

Expiration alarm.
Cfg_FullStallTime T#5s Configured Full Stall Timer. This defines the Config1.8
period of time the module for the Full Stall Config1.9
Status. Val_FullStallT
This is used to generate the Open Full Stall and
Close Full Stall alarms.
Cfg_TransitStallTime T#15s Configured Transit Stall Timer. This defines the Config1.8
period of time the module for the Transit Stall Config1.9
Status. Val_TransitStallT
This is used to generate the Open Transit Stall
and Close Transit Stall alarms.

Once the Config1.x (‘Has <alarm>’) configuration item is cleared (= Once the Config
0), the module will no longer generate the associated alarm, and the 0
Alarm Panel for the associated alarm will disappear from the HMI Alarm Panel for
Faceplate. Faceplate.

Each alarm is configured with a Priority value (as per value in the
table above). In the case where multiple alarms within the SM_V2S
Function Block are active simultaneously, Val_Notify will contain the
numeric value associated with the highest Priority alarm.

Configuration – Miscellaneous: These parameters determine the functionality used by the Valve and EU Minimum and
Maximum values for scaling the HMI.

Parameter: Default: Usage: Associated Parameters

Config1.6 1 Enable/Disable control is allowed and

will be processed
Config1.11 1 Valve has Closed Limit Switch
Config1.12 1 Valve has Opened Limit Switch
Config1.13 0 Voltage and Current displayed on HMI
Config2.0 1 Operator Command required after a
reset to return to normal operating
condition

Publication KGEOB10001-00008 - December, 2017 27

Chapter 2 Configuration Options

Parameter: Default: Usage: Associated Parameters

Config2.1 1 Valve driven to safe state on

expiration of MTTR
Config2.2 1 0 = Valve normally energized
1 = Valve normally de-energized
Config2.3 1 0 = Valve normally open
1 = Valve normally closed

Configuration – Program Interface: These parameters define the interaction between the Valve and the application program.

Parameter: Default: Usage: Associated Parameters:

Config2.12 0 Program Mode takes precedence over Operator

Lock.
Config2.13 0 Program Mode is default mode.

28 Publication KGEOB10001-00008 - December, 2017

 Chapter 2 Configuration Options

Notes:

Publication KGEOB10001-00008 - December, 2017 29

 Chapter 3
Data Reference
This chapter describes the SM_V2S (Two State Valve’s) S_AIn
structure parameters. The structure ‘Direction’ and ‘Attribute’ settings
must remain as ‘Internal’ and ‘Free’ (as provided in the template files).

Configuration (Cfg_) Configuration Data Elements are used to set configurable capabilities,
features and functions of the SM_V2S Safety Module.
The following Configuration data may be modified using the AADvance
Workbench:

Associated
Data Usage Configuration
Name: Type: : Default: Style: Description: Parameters:

Config1.0 UINT Input 1 BOOL 1=Maintenance Bypass functionality is

enabled and will be processed

Config1.2 UINT Input 1 BOOL 1=Mean Time To Repair functionality is

enabled and will be processed

Config1.6 UINT Input 1 BOOL 1=Enable/Disable functionality is allowed

and will be processed

Config1.7 UINT Input 1 BOOL 1=IOFault Alarm exists and will be

processed (PVBad status always
processed)

Config1.8 UINT Input 1 BOOL 1=Failed To Close Condition exists and will
be checked

Config1.9 UINT Input 1 BOOL 1= Failed To Open Condition exists and will
be checked

Config1.10 UINT Input 1 BOOL 1=Illegal Feedback Condition exists and

will be checked

Config1.11 UINT Input 1 BOOL 1=Has Closed Limit Switch

Config1.12 UINT Input 1 BOOL 1=Has Opened Limit Switch

Config1.13 UINT Input 0 BOOL 1=Has Voltage and Current display

Config2.0 UINT Input 1 BOOL 0=Output requires operator command after

trip to return to healthy state;
1=Output will return to healthy state when
interlocks healthy.

Config2.1 UINT Input 1 BOOL 1=Output driven to trip state on MTTR

expiration

Config2.2 UINT Input 1 BOOL 0=Normally Energized;

1=Normally De-Energized

Publication KGEOB10001-00008 - December, 2017 30

 Chapter 3 Data Reference

Associated
Data Usage Configuration
Name: Type: : Default: Style: Description: Parameters:

Config2.3 UINT Input 1 BOOL 0=Valve Open in normal operation;

1=Valve Closed in normal operation

Config2.8 UINT Input 1 BOOL 1=Latch Alarms

Config2.9 UINT Input 1 BOOL 1=Latch PVBad status

Config2.12 UINT Input 0 BOOL 1=Program Mode takes precedence over

Operator Lock

Config2.13 UINT Input 0 BOOL 1=Program Mode is default mode;

0=Operator Mode is default mode.

Cfg_MaintBypTime TIME Input T#8hr Time Maintenance Bypass Time

Cfg_MaintBypPreExpLim TIME Input T#30m Time Maintenance Bypass Pre-Expiration Alarm

Time Threshold

Cfg_MTTR TIME Input T#24hr Time Mean Time to Repair

Cfg_MTTRPreExpLim TIME Input T#4hr Time Mean Time to Repair Pre-Expiration Alarm
Time Threshold

Cfg_FullStallTime TIME Input T#5s Time Full Stall Time. Defines the period of time
(seconds) the module waits after receiving
command before setting the Full Stall
Status.

Cfg_TransitStallTime TIME Input T#15s Time Transit Stall (‘Movement’) Time. Defines
the period of time (seconds) the module
waits after receiving command before
setting the Failed To Close / Failed To
Open Status.

Alarms Subcategory The following Cfg_ tag elements are generic for all alarms defined for SM_V2S.
Replace the string “<alarm>” in the generic element name with any of the following specific alarm
names to get the specific element:
• FailedToClose
• FailedToOpen
• IllegalFeedback
• IOFault
• MaintBypPreExp
• MaintBypExp
• MTTRPreExp
• MTTRExp

Cfg_<alarm>Severity INT Local 1 Decimal Alarm Severity level

1..250=Low
251..500=Medium
501..750=High
751..1000=Urgent

Publication KGEOB10001-00008 - December, 2017 31

Chapter 3 Data Reference

Mode Commands (PCmd_, Mode Command Data Elements are used by application logic to
request SM_V2S mode-related actions, such as changing or
OCmd_, MCmd_) and Mode locking Modes.
Readies The following diagram shows how the various modes are
acquired and released and their priority. Note that each layer is
always active; that is, Program and Operator mode commands
affect the state of the Program / Operator mode even when
Maintenance Mode, is active.
The modes have the following priority:-
• Maintenance (Highest)
Control of the device is owned by maintenance. Operator
Commands and Settings from the HMI are accepted.
Bypassable interlocks and permissives are bypassed.
Non-bypassable interlocks and permissives override any
Maintenance commands.
• Program
Control of the device is owned by Program logic.
Program Commands (PCmd_) are accepted. All
interlocks and permissives are processed and override
any Program commands.
• Operator (Lowest)
Control of the device is owned by the operator. Operator
Commands (OCmd_) from the HMI are accepted. All
interlocks and permissives are processed and override
any Operator commands.

Maintenance Mode

Maint

MCmd_MaintBypRmv MCmd_MaintBypEnbl

Program / Operator Mode

PCmd_Unlock

Prog PCmd_Lock Prog Locked

PCmd_Acq OR PCmd_Rel OR
OCmd_UnlockRel OCmd_AcqLock

Oper OCmd_AcqLock Oper Locked

OCmd_UnlockRel

32 Publication KGEOB10001-00008 - December, 2017

 Chapter 3 Data Reference

Mode Commands

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

MCmd_MaintBypEnbl BOOL Local 0 Edge Enable Maintenance Bypass Config1.0

MCmd_MaintBypRmv BOOL Local 0 Edge Remove Maintenance Bypass Config1.0
OCmd_AcqLock BOOL Local 0 Edge 1 = Operator command to place Valve in
Operator mode (‘Acquire’) or (if already in
Operator Mode) to lock the mode.
OCmd_UnLockRel BOOL Local 0 Edge 1 = Operator command to (if locked)
unlock the mode or (if already unlocked)
unlock Operator mode.
PCmd_Acq BOOL Input 0 Edge 1 = Program command to acquire program
ownership of the Valve (from operator
mode to program mode)
PCmd_Rel BOOL Input 0 Edge 1 = Program command to release program
ownership of the Valve (from program
mode to operator mode)
PCmd_Lock BOOL Input 0 Edge 1 = Program command to lock Valve in
program mode
PCmd_Unlock BOOL Input 0 Edge 1 = Program command to Unlock Valve
program mode

Mode Command Readies

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

Ready.12 UINT Output BOOL 1=Ready for Operator Acquire

Ready.13 UINT Output BOOL 1=Ready for Operator Release
Ready.14 UINT Output BOOL 1=Ready for Operator Lock
Ready.15 UINT Output BOOL 1=Ready for Operator Unlock

Publication KGEOB10001-00008 - December, 2017 33

Chapter 3 Data Reference

Program Device Program Command Data Elements are used by application logic to
request SM_V2S actions, such as opening or closing the valve.
Commands (PCmd_)
Application logic sets the Program Command to 1 to request the
action. (See the Edge and Level section in the Preface for more
information). The SM_V2S Safety Module then performs the requested
action if it is in Program Mode and the action can be performed.

Device Commands

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

PCmd_Close BOOL Input 0 Edge 1 = Program command to Close

the Valve
PCmd_Open BOOL Input 0 Edge 1 = Program command to Open
the Valve

34 Publication KGEOB10001-00008 - December, 2017

 Chapter 3 Data Reference

Operator Device Operator Commands and Maintenance Commands are used by the
Operator at the HMI to request actions, such as enabling or disabling,
Commands (OCmd_), suppressing or un-suppressing alarms; or other instance-specific
Maintenance Device actions.
Operator Commands are set (latched) by the HMI and are read and
Commands (MCmd_), then cleared (unlatched) by this Function Block, allowing a many-to-one
and Readies (Rdy_) relationship between HMI requestors and each Command.

Maintenance Commands are only available when Maintenance Bypass

is enabled and active.

Device Commands

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

OCmd_Close BOOL Local 0 Edge 1 = Operator command to Close

the Valve
OCmd_Open BOOL Local 0 Edge 1 = Operator command to Open
the Valve
MCmd_Close BOOL Local 0 Edge 1 = Maintenance command to
Close the Valve
MCmd_Open BOOL Local 0 Edge 1 = Maintenance command to
Open the Valve
MCmd_MaintBypEnbl BOOL Local 0 Edge Enable Maintenance Bypass Config1.0
MCmd_MaintBypRmv BOOL Local 0 Edge Remove Maintenance Bypass Config1.0
MCmd_OOSEnbl BOOL Local 0 Edge Disable the device Config1.6
MCmd_OOSRmv BOOL Local 0 Edge Enable the device Config1.6
OCmd_ResetAll BOOL Local 0 Edge Operator Command to reset all
active alarms (if alarms are
configured to latch) and to reset
the PVBad status (if configured to
latch)

Publication KGEOB10001-00008 - December, 2017 35

Chapter 3 Data Reference

Device Command Readies

Each Operator Command has a corresponding Ready bit which

indicates whether the Command will be accepted and acted upon when
received. The Ready bit is used to enable (1) or gray-out (0) the
Operator Command button on the faceplate.

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

Ready.0 BOOL Local 0 1 = Ready to receive Maintenance Config1.0

Bypass Command.
Ready.1 BOOL Local 0 1 = Ready to Reset Latched Config2.8
Statuses and Alarms. Config2.9
Ready.8 BOOL Local 0 1 = Ready to Close
Ready.9 BOOL Local 0 1 = Ready to Open

36 Publication KGEOB10001-00008 - December, 2017

 Chapter 3 Data Reference

Values (Val_) Value Data Elements contain process or device variables, the
notification level for alarm animation, and the current accepted values of
any limits or other settings (from Program Settings) for the SM_V2S
Function Block. The HMI displays these Values, and they are available
for use by other application logic.
Data Access for all Value Data Elements is set to Read Only, unless
noted in the “Usage” column (N = None, W = Read/Write)

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

Val_MTTR DINT Output Decimal Mean Time to Repair (seconds) Cfg_MTTR

Output Decimal Maintenance Bypass Remaining Time Cfg_MaintBypTime
Val_MaintBypRT DINT
(seconds)
Output Decimal Mean Time To Repair Remaining Time Cfg_MTTR
Val_MTTRRT DINT
(seconds)
Val_FullStallT DINT Output Decimal Valve Full Stall Time (seconds)
Val_TransitStallT DINT Output Decimal Valve Transit Stall Time (seconds)
Output Decimal Duration for Last Valve Closure
Val_CloseDur DINT
(milliseconds)
Output Decimal Duration for Last Valve Opening
Val_OpenDur DINT
(milliseconds)
Output Decimal Device demand
Val_Cmd SINT
(0=None, 1=Close, 2=Open)
SINT Output Decimal Contains the Priority assigned to the active Cfg_<alarm>Severity
Valve alarm. In the case of multiple active
alarms, contains highest Priority:

0 = None
1 = Not in alarm, unacknowledged or reset
Val_Notify
required
2 = Low
4 = Medium
6 = High
8 = Urgent
From #2, # + 1 = Unacknowledged
Val_Current INT Output Decimal Digital Output Current
Val_Voltage UINT Output Decimal Digital Output Voltage

Publication KGEOB10001-00008 - December, 2017 37

Chapter 3 Data Reference

Status (Sts_) Status Data Elements contain process or device states, Mode status
and Alarm status. The HMI displays these Status points, and they are
available for use by other application logic.

Device Status

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

Status1.0 UINT Output BOOL 1=Maintenance Bypass Timer about to Expire.

Status1.1 UINT Output BOOL 1=Maintenance Bypass Enabled.
Status1.2 UINT Output BOOL 1=MTTR Timer about to Expire.
Status1.3 UINT Output BOOL 1=MTTR Timer Expired.
UINT Output BOOL 1=Discrepancy between redundant channel
Status1.4
measurements
UINT Output BOOL 1=Configuration Error. Set if any error is active (any
Value parameter not equal to the equivalent
Configuration parameter).
Status1.5

Note: Alarm Errors are processed and annunciated

separately – refer to the Alarms section.
Status1.6 UINT Output BOOL 1=Device is Out of Service.
UINT Output BOOL 1= Digital Output Status is not healthy and/or Digital
Status1.7 Input Status is not healthy, or any Discrepancy
between redundant modules.
Status1.8 UINT Output BOOL 1=Valve Failed To Close (failed to reach closed limit).
Status1.9 UINT Output BOOL 1=Valve Failed To Open (failed to reach open limit).
UINT Output BOOL 1=Feedbacks are in an INVALID state (not OPEN,
Status1.10
CLOSE or TRANSIT).
Status1.11 UINT Output BOOL 1=Valve Full Stall Closed (failed to move from closed).
UINT Output BOOL 1=Valve Full Stall Opened (failed to move from
Status1.12
opened).
Status1.13 UINT Output BOOL 1=Valve Loss of Closed (lost closed without request).
Status1.14 UINT Output BOOL 1=Valve Loss of Opened (lost opened without request).
Status1.15 UINT Output BOOL 1=Maintenance Bypass Timer Expired.

38 Publication KGEOB10001-00008 - December, 2017

 Chapter 3 Data Reference

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

Status2.0 UINT Output BOOL 1=Digital Output energized

UINT Output BOOL Closed Status. Indicates the device is in the Closed
Status2.1
state, based on Closed Limit Switch Input. If the Closed
Limit Switch is not available (Config1.11 = 0), then
Closed Status will reflect the state of Output.
UINT Output BOOL Opened Status. Indicates the device is in the Opened
state, based on Opened Limit Switch Input. If the Open
Status2.2
Limit Switch is not available (Config1.12 = 0), then
Opened Status will reflect the state of Output.
UINT Output BOOL Closing Status. Indicates the Output is requesting the •
Status2.3 device to close, and the Closed Limit Switch Input has
not yet been received.
UINT Output BOOL Opening Status. Indicates the Output is requesting the •
Status2.4 device to open, and the Opened Limit Switch Input has
not yet been received.

Status2.7
UINT Output BOOL 1=Any Limit Switch Fault (Input ≠2 and ≠4) or both limit •
switches on (Illegal Feedback)
UINT Output BOOL 0=Non-Bypassable Interlocks okay, •
Status2.8
1=Non-Bypassable Interlock input demand
UINT Output BOOL 0=Bypassable Interlocks okay, •
Status2.9
1=Bypassable Interlock input demand
UINT Output BOOL 0=Non-Bypassable Permissive okay, •
Status2.10
1=Non-Bypassable Permissive input demand
UINT Output BOOL 0=Bypassable Permissive okay, •
Status2.11
1=Bypassable Permissive input demand

Mode Status

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

Status2.12 UINT Output BOOL 1 = Valve is available for Program Control

UINT Output BOOL 1 = Valve mode is Operator (allows control
Status2.13
from faceplate)

Publication KGEOB10001-00008 - December, 2017 39

Chapter 3 Data Reference

Associated
Configuration
Name: Data Type: Usage: Default: Style: Description: Parameters:

UINT Output BOOL 1 = Valve mode is Program (allows control

Status2.14
from logic)
Status2.15 UINT Output BOOL 1 = Program or Operator has Locked mode

Alarms Subcategory The following Cfg_ tag elements are generic for all alarms defined for SM_V2S.
Replace the string “<alarm>” in the generic element name with any of the following specific alarm
names to get the specific element:
• FailedToClose
• FailedToOpen
• IllegalFeedback
• IOFault
• MaintBypPreExp
• MaintBypExp
• MTTRPreExp
• MTTRExp

<alarm>_Alm BOOL Local Level Alarm status

<alarm>_Severity INT Local Decimal Alarm Severity level Cfg_<alarm>Severity
1..250=Low
251..500=Medium
501..750=High
751..1000=Urgent
<alarm>_StsAlm BOOL Local Level Alarm status from FTAE
<alarm>_StsAck BOOL Local Level Alarm acknowledgement
status to/from FTAE
<alarm>_ValNotify SINT Local Decimal Current alarm severity
and Acknowledgement
(enumeration)
<alarm>_ErrAlm BOOL Local Level Alarm configuration error

40 Publication KGEOB10001-00008 - December, 2017

 Chapter 3 Data Reference

Notes:

Publication KGEOB10001-00008 - December, 2017 41

 Chapter 4

HMI Reference
This chapter describes the HMI Graphic Object(s) and Faceplate(s)
provided for the GEMS SM_V2S (Two State Valve) and their detailed
features and functions.

Graphic Object Graphic Object(s) are used on the HMI Operator screens, and provide
end-users with:
• Information on the Valve’s current state.
• A touch field to open the Valve’s faceplate.
• A label (Valve’s device tag).

Common attributes of the SM_V2S Graphic Object(s) are:

• A graphical representation of the Valve.
• The current state of the Valve.
• The mode status of the Valve.
• Qualifier status’s associated with the Valve.
• A label (Valve’s device tag/ID).
• An alarm indicator that changes color for the Priority of the
alarm (not displayed when no Valve alarms exist).
 Chapter 4 HMI Reference

Graphical Representation

SM_V2S Graphic Objects contain a graphical representation of the

Valve. Examples of Valve graphical representations are:
• Valve (two port)

The (RA-SIS) SM_V2S-Library.ggfx file contains a library of Graphic

Objects for the SM_V2S module.

Global Object With #102 Tag name (no path)

Parameter Definition (e.g. SDV_101A)
#103 Path of Data Server and Controller Name
(e.g. /KEPServer::ModbusTCP.Train1)
#104 Path of HMI Server
(e.g. CCR::RA-SIS\Train1\SM_V2S\)
#105 Path of FTAE Server and System Prefix
(e.g. /FTAEServer::Prefix_)
#120 Additional display parameter
(e.g. /X100 or /CC) (optional)
#121 Additional display parameter
(e.g. /Y100) (optional)

Publication KGEOB10001-00008 - December, 2017 43

Chapter 4 HMI Reference

The graphical representation of the Valve changes color depending on

the state of the Valve.

Color Device State

Grey Closed

White Opened

Grey / White Closing / Opening

Magenta Unknown

Color Actuator State

Grey Valve Output Energized

White Valve Output De-Energized

Mode Indicators

SM_V2S Graphic Object(s) contain mode indicators for the Valve. The
following table lists the mode indicators.

Indicator Description Data Element

Valve has been disabled Status1.6

Valve In maintenance mode Status1.1

Valve in operator mode Status2.13

Valve in program mode Status2.14

44 Publication KGEOB10001-00008 - December, 2017

 Chapter 4 HMI Reference

Status Qualifier Indicators

SM_V2S Graphic Object(s) contain status qualifiers for the Valve. The
following table lists the status qualifier indicators.

Indicator Description Data Element

Maintenance Bypass Status1.15

Status1.7,
PVBad, Device Out of Range,
Status1.4,
Input Discrepancy, Under-
Status1.12,
Range, or Over-Range
Status1.13

Disabled Status1.6

Configuration Error Status1.5

Mean Time To Repair expired Status1.3

Alarm Indicator

An alarm symbol indicator is used to indicate the Valve has an active

or unacknowledged alarm. The alarm indicator changes based on
alarm priority, and blinks if the operator needs to acknowledge the
alarm. The icon is displayed only if the Valve has an active or
unacknowledged alarm.

Definition Data Element

Not in alarm, Alarm Val_Notify =1

Acknowledge required

Low Priority alarm active Val_Notify = 2.3

Medium Priority alarm Val_Notify = 4.5

active

High Priority alarm active Val_Notify = 6.7

Urgent Priority alarm active Val_Notify = 8.9

<alarm>.Disabled
Alarm Disabled or Shelved
<alarm>.Shelved
or Suppressed
<alarm>.Suppressed

Publication KGEOB10001-00008 - December, 2017 45

Chapter 4 HMI Reference

The SM_V2S Function Block contains several embedded

alarms (see Alarms in the Overview section of this
document for a list of alarms). Each alarm is encoded with
value (as per value in the table above) based on alarm
type (per definition in table above). In the case where
multiple alarms within the SM_V2S Function Block are
active simultaneously, the Alarm Indicator will indicate the
color associated with the alarm with the highest value. The
Val_Notify data element contains the value of the active
alarm with the highest value.

46 Publication KGEOB10001-00008 - December, 2017

 Chapter 4 HMI Reference

Faceplate The SM_V2S Faceplate consists of tabbed pages. The Operator page
is the default display, when the Faceplate opens. Click the appropriate
tab at the top of the Faceplate to access a specific page.

Maintenance Exit

Operator Alarm Help

The Maintenance page allows navigation to the SM_V2S

Configuration Faceplate, which contains a page used to display
configuration items.

An ‘X’ symbol in the top right corner of a Configuration

Tab navigation Icon indicates that a configuration error
exists (Status1.5). See Statuses in the Data Reference
section of this document for a complete list of errors
defined for the SM_V2S.

Publication KGEOB10001-00008 - December, 2017 47

Chapter 4 HMI Reference

FactoryTalk View ® Diagnostics

Any action initiated from the SM_V2S Faceplate (at run time) will be
logged in the FactoryTalk View ® Diagnostic log, this includes:
• Commands
• Setpoints

The following information is logged for all actions:

• Date and Time
• User
• Location (computer)
• Device ID
• Action description (clear statement of the action, for example –
IO Fault Alarm Acknowledged)

48 Publication KGEOB10001-00008 - December, 2017

 Chapter 4 HMI Reference

Operator Tab

The Operator page provides the interface necessary to control and/or

monitor the Valve.

Valve Description

Navigation

Mode Command
Mode Indication Buttons

Valve State Indicator Command Buttons

Additional Status Interlock & Permissive

(none shown) Indicators

Command Pane

Output current
and voltage

Communication
Status Indicator

Publication KGEOB10001-00008 - December, 2017 49

Chapter 4 HMI Reference

The Operator Tab has the following purpose:

• Displays the Valve mode (see Modes of Operation, in the
Overview section of this document for list of modes supported
by the SM_V2S).
• Allows mode commands to be issued to the SM_V2S.
• Displays the current state of the Valve.
• Allows the user to issue State Commands to the Valve.
• Allows the user to issue Setpoint commands to the Valve.
• Provides Communication status (OK or Fault).
• Displays Interlock & Permissive status.

Associated
Indicator Status Parameter

Device Description Cfg_Desc

Valve State Indicator displays

the state of the Valve using a Status2.1
text description and color Status2.2
indicator (rectangle). Status2.3
Status2.4
Disabled indicates Valve out of Status1.6
service.

AADvance I/O Module has detected

internal channel discrepancy
Status1.4

I/O Fault detected Status1.7

50 Publication KGEOB10001-00008 - December, 2017

 Chapter 4 HMI Reference

Security
Button / Field Action Required

Places the Valve in Program mode

Code B
(OCmd_UnlockRel).

Places the Valve in Operator mode

(OCmd_AcqLock), and Locks Operator
Code B
mode making the Valve unavailable to
the Program.

Unlocks Operator mode

(OCmd_UnlockRel), making the Valve Code B
available to the Program.

Locks Operator mode (OCmd_AcqLock),

making the Valve unavailable to the Code B
Program.

Opens the Valve

Code B
(OCmd_Open / MCmd_Open)

Closes the Valve

Code B
(OCmd_Close / MCmd_Close)

Provides Interlock status.

Provides Permissive status.

The Command Pane is overlaid by the Command

Confirmation window for Maintenance / Operator
commands.

Publication KGEOB10001-00008 - December, 2017 51

Chapter 4 HMI Reference

Alarm Tab

The Alarm page provides a listing of all Alarms for the Valve. Each
Alarm is individually annunciated on this page, and each Alarm may
be disabled, enabled, acknowledged, and reset from this page.

Alarm Indicator /
Navigation Icon

Alarm Panel

Alarm Acknowledge
Command

Alarm Reset
Buttons

52 Publication KGEOB10001-00008 - December, 2017

 Chapter 4 HMI Reference

The Alarm Tab has the following purpose:

• Displays the status of each alarm associated with the Valve.
• Displays a summary alarm status for the Valve
• Allows individual Alarms to be acknowledged.
• Allows Alarms to be reset.
• Allows individual Alarms to be disabled / enabled, shelve /
unshelve

Refer to Global Engineering Modularity Standards (GEMS)

I_Alarm, Alarm Instruction, for more information on alarms.

Associated
Indicator Status Parameter

See the Alarm Indicator

Alarm Indicator/
Navigation Icon
section of this document for Val_Notify
details

An Alarm Panel provides the

status of a particular alarm.
Such as:
• Not in Alarm
• In Alarm,
unacknowledged
• In Alarm, acknowledged <alarm>.Alm
• Alarm condition clear, <alarm>.Sts_Err
unacknowledged <alarm>.Disabled
Alarm Panel • Alarm Suppressed <alarm>.Shelved
• Alarm Disabled <alarm>.Suppressed
<alarm>.Severity
The SM_V2S Function Block
contains several embedded <alarm>.Val_Notify
alarms (see Alarms in the
Overview section of this
document for a list of alarms).
An Alarm Panel exists for
each alarm defined within the
SM_V2S Function Block.

Publication KGEOB10001-00008 - December, 2017 53

Chapter 4 HMI Reference

The Color of the Alarm Panel is determined by the Value

(see Alarms, value column) assigned to the alarm
associated with a particular Alarm Panel. The table below
provides a cross reference between alarm Value and
Alarm Panel color.

Alarm Value Alarm Panel Color Definition

1 Light Grey Out of Alarm

2 Light Blue Low priority

Medium
4 Yellow
priority

6 Red High priority

8 Magenta Urgent priority

The Summary Alarm (Device Alarm Present) Alarm Panel

reflects the color of the active alarm. In the case where
multiple alarms within the SM_V2S Function Block are
active simultaneously, the Alarm Panel will indicate the
color associated with the alarm with the highest Value (see
Alarms, value column). The Val_Notify data element
contains the value of the active alarm with the highest
value.

Security
Button / Field Action Required

Alarm Acknowledge issues an

acknowledge to a specific alarm Code F
(<alarm>.Sts_Ack).

Alarm Reset issues an alarm reset to all

Code F
alarms (OCmd_ResetAll).

Alarm Control Window: By clicking on an Alarm Entry, the

Alarm Control Window appears for the selected alarm.
From the Alarm Control Window, the selected alarm may
be Disabled / Enabled, Shelve/Unshelve and alarm
configuration.
Refer to Alarm module User Manual for the details.

54 Publication KGEOB10001-00008 - December, 2017

 Chapter 4 HMI Reference

Help Tab

The Help page provides Help information for various commands and
status’s available on the Valve Faceplate.

Help
Navigation
Icons

Publication KGEOB10001-00008 - December, 2017 55

Chapter 4 HMI Reference

The Help Tab has the following purpose:

• Identifies all Mode and Status indicators used within the Valve
faceplate.
• Identifies all Operator Command buttons used within the Valve
faceplate.
• Identifies all Maintenance Command buttons used within the
Valve faceplate.
• Provides Navigation to Alarm Help Tab – Provides a list of all
Valve alarms, and an explanation of each.

Security
Button / Field Action Required

Alarm Help Tab, Navigation Icon

Refer to Global Engineering Modularity Standards (GEMS)

Add-On Instructions and Graphics: Users Manual, for more
information on common Faceplates.

56 Publication KGEOB10001-00008 - December, 2017

 Chapter 4 HMI Reference

Maintenance Tab

The Maintenance page provides access to various maintenance

functions available for the Valve.

Maintenance
Navigation Icon

Configuration
Faceplate Navigation

Disabled Indicator
Mode Indicator

Valve Enabled/ Valve

Disabled Indicator Enable and Disable
Commands
Maintenance Bypass
Status Panel Maintenance Bypass
Enable & Disable
Commands
Mean Time To Repair
Status Panel

Publication KGEOB10001-00008 - December, 2017 57

Chapter 4 HMI Reference

The Maintenance Tab has the following purpose:

• Displays the Valve mode (see Modes of Operation, in the
Overview section of this document for list of modes supported
by the SM_V2S).
• Allows the user to place the Valve in maintenance mode, and
remove the Valve from maintenance mode.
• Allows the user to Enable the SM_V2S (place Valve in
service), and Disable the SM_V2S (place Valve out of service)
• Allows the user to see Interlock & Permissive statuses.
• Access to the Device Configuration Faceplate

Associated
Indicator Status Parameter

Enable indicates Valve in service,

Disabled indicates Valve out of Status1.6
service.

Indicates Valve Maintenance

Status1.1
Bypass active / not active.

Security
Button / Field Action Required

Enable SM_V2S, places the

Valve in service. Code C
(MCmd_Enable)

Disable SM_V2S, places the

Valve out of service Code C
(MCmd_Disable)

Places the Valve in Maintenance

Bypass, bypassing bypassable
Code C
Interlocks and Permissives
(Status1.1)

Removes the Valve from

Code C
Maintenance Bypass (Status1.1)

58 Publication KGEOB10001-00008 - December, 2017

 Chapter 4 HMI Reference

Disabling (placing out of service) the SM_V2S Function

Block causes Valve outputs to become de-energized.

Bypassable Interlocks are any Interlocks tied to the IL

input. Non-Bypassable Interlocks are any Interlocks tied to
the NBIL input.
Bypassable Permissives are any Permissives tied to the
PERM input. Non-Bypassable Permissives are any
Permissives tied to the NBPm input.

Publication KGEOB10001-00008 - December, 2017 59

Chapter 4 HMI Reference

Configuration - Device Tab

The Configuration – Device page provides access to configuration

items within the SM_V2S which define the physical characteristics of
the Valve.

Configuration
Device Tab
Navigation Icon

Description
Tag Name

Mean Time To Repair

Configuration

Device Configuration
Check Boxes / Fields

Full and Transit Stall

Time Configurations

Configuration Error
Alarm Error

The Configuration - Device Tab has the following purpose:

• Allows for the configuration of operational parameters for the
Valve.
• Allows for the operational strategy to be defined for the Valve.

All configuration parameters associated with the Valve,

except for the Description and Tag Name, cannot be
changed via the HMI. These configuration parameters can
only be changed in the AADvance controller.

60 Publication KGEOB10001-00008 - December, 2017

 Chapter 4 HMI Reference

Notes:

Publication KGEOB10001-00008 - December, 2017 61