TPSK/Long Son LSP Complex Project

Customized Training Course

Ahmad Tarek Ibrahim Omar

Senior Application Engineer

Confidential Property of Schneider Electric

Internal
Training Objectives
➢ Describe the basic theory of operation of ITCC (TMR) system
➢ Identify the ITCC system components (supplied for the Project)
➢ HMI Graphics screens and Navigation inside HMI
➢ Start-up, shutdown and loading of turbine & compressor
➢ Diagnose, operate and maintain the ITCC

Confidential Property of Schneider Electric | Page 2

Internal
Training
AgendaObjectives 1 I. Introduction to Turbomachinery

Integrated Turbine & 2 II. Introduction to the ITCC

Compressor Control System 3

III. ITCC System Hardware

(ITCC) Components

4 IV. ITCC Application

5 V. HMI Operation

6 VI. Maintenance of ITCC

VII. Basic Principle of Wonderware

7
Intouch

Confidential
ConfidentialProperty
PropertyofofSchneider
SchneiderElectric
Electric| |Page
Page33
Internal
1 Introduction to Turbomachinery

Internal
Introduction to Turbomachinery
Turbomachinery, in mechanical engineering, describes machines that transfer energy between a rotor
and a fluid, including both turbines and compressors. While a turbine transfers energy from a fluid to a
rotor, a compressor transfers energy from a rotor to a fluid.
These two types of machines are governed by the same basic relationships including Newton’s second
Law of Motion and Euler's pump and turbine equation for compressible fluids.
Centrifugal pumps are also turbomachines that transfer energy from a rotor to a fluid, usually a liquid,
while turbines and compressors usually work with a gas

Confidential Property of Schneider Electric | Page 5

Internal
2 Introduction to the ITCC

Internal
 Introduction to the ITCC
What is ITCC
ITCC is abbreviation of Integrated Turbine and Compressor Control System (ITCC) for Turbine Driven
Compressor.
ITCC systems are used in the plant to allow smooth transition from one set of desired operating
conditions to another set and shall compensate for changes in dynamic performance of the plant due to
changing operating conditions.
This Function is Implemented based on the SE excellent Hardware Platform, Intelligent Development
and Runtime Software and Rich project expertise of Engineering expert of SE TMC Engineering Team.

Confidential Property of Schneider Electric | Page 7

Internal
Why Integrated Turbine Compressor Control(ITCC)

Confidential Property of Schneider Electric | Page 8

Internal
 Dis-Integrated Compressor Control
Historically, turbomachinery controls has been managed separately from adjacent processes
and automation strategies. Equipment pieces from various suppliers utilize undisclosed
automation strategies so, in essence, they are unable to ‘speak’ to each other.
Conventional configurations:
➢ Anti-Surge controllers provided by compressor control vendor.
➢ Performance/Capacity provided by compressor control vendor or by DCS.
➢ Turbine/Compressor auxiliary controllers and Trip/Alarms interlock provided by others
(DCS and PLC).
➢ Machine(Vibration) monitor system provided by package vendor.

Confidential Property of Schneider Electric | Page 9

Internal
 Dis-Integrated Compressor Control

Control
System

PLC Gateway

Vibration
Surge
ESD

Governor

Local Panel

Confidential Property of Schneider Electric | Page 10

Internal
 Dis-advantages of Dis-Integrated Compressor Control
With the conventional configuration, it usually has more challenges and dis-advantage as
below:
➢ Not flexible to modify or expand scope due to many different vendors get involve.
➢ Require more time and effort to putting all of above instruments/controller work together.
➢ Integration testing will be challenges, and usually will be done at site which will lead to be
more surprises at last minus.
➢ More training requires and difficult to be maintained overtime.

Confidential Property of Schneider Electric | Page 11

Internal
 Dis-advantages of Dis-Integrated Compressor Control
Failure of this transmitter will cause the
compressor recycle valve to open Failure of this transmitter will cause the
interrupting forward flow of the gas, process cascade to fail.
possible tripping the process.

Governor

PT PT PT

FT

Confidential Property of Schneider Electric | Page 12

Internal
 SE ITCC Overview
Integration combines many functions such as machinery protection, prime mover (turbine, main motors)
start-up sequencing, load/speed control, compressor anti-surge control, and auxiliary control/interlock
(such as process control, alarming and tripping for lube oil, seal gas, condensate, and gland sealing
system, etc) MMC interface into a single control system.
To protect assets and enhance productivity, safety and lifecycle, Schneider has designed a
comprehensive critical compressor control for turbine drive compressor machines.
The ITCC solutions can be tailored to suit a variety of compressor train configurations and installations.

Confidential Property of Schneider Electric | Page 13

Internal
 ITCC System Solution Overview

Confidential Property of Schneider Electric | Page 14

Internal
 Typical ITCC Application Overview

Trip / Interlock
Motor/Pumps Logic
Auxiliary Controls
Startup Sequence
Prime Mover Ctrl
Anti-Surge Ctrl
Stonewall Ctrl
Quench Temp. Ctrl
Limiter Ctrl
Performance Ctrl

Confidential Property of Schneider Electric | Page 15

Internal
 ITCC Controllers Coordination

DCP

ASC
20.0
45.0
12.0

AUT

PM

FM

Confidential Property of Schneider Electric | Page 16

Internal
 Introduction to the ITCC
ITCC solves the hassle of managing multiple ‘black boxes’ by enabling turbomachinery control
elements to communicate with each other, and with adjacent processes.
Capability to perform more than one control task in a single system.

Integrated TMR

Aux / Interlocks
Turbine Governor

Confidential Property of Schneider Electric | Page 17

Internal
 Advantages of ITCC System
The benefits of integration are:
➢ Lower procurement costs
➢ Lower engineering costs
➢ Lower installation costs
➢ Flexible for modification, changes and add-on
control scope
➢ Reduced space requirements
➢ Lower field instrumentation costs

Confidential Property of Schneider Electric | Page 18

Internal
 Advantages of ITCC System
➢ No controller-to-controller communication delays
➢ No interconnection of controllers required
➢ Elimination of controller conflicts
➢ Easy to coupling and coordination of turbine controls and compressor controls
➢ Single hardware system training
➢ Single system software training
➢ Simplified maintenance

Confidential Property of Schneider Electric | Page 19

Internal
Hardware and Software of ITCC System
The ITCC System is compose of
➢ The Major hardware platform for ITCC is Triconex Triple redundant Controller.
➢ HMI Software Platform use World Class Wonderware, InTouch visualization software
➢ Triconex’s Critical Control and Safety System expertise into a comprehensive Human-Machine Interface
System.

Confidential Property of Schneider Electric | Page 20

Internal
3 ITCC System Hardware Components

Internal
ITCC Hardware

Confidential Property of Schneider Electric | Page 22

Internal
ITCC System Hardware Components (Hardware Platform)
SIL-Rated TMR Requirements General Purpose
(Critical Machinery) (Simplex and Redundant)

Tricon Tri-GP Modicon Quantum Modicon M340

Modicon M580 Safety

Trident Tricon CX Modicon M580
(Tricon\Tricon CX-SIL3, Tri-dent-SIL3, Tri-GP-SIL2)

Confidential Property of Schneider Electric | Page 23

Internal
Typical Hardware architecture

Confidential Property of Schneider Electric | Page 24

Internal
Feature of the ITCC Hardware
ITCC systems are designed based on Triconex TMR controllers, which are certified for use based on IEC-
61508 SIL 3.1.
The hardware platform for ITCC is Triconex Triple redundant Controller which ensure the highest possible
availability:
➢ No single point of failure
➢ Fully implemented and transparent triplication
➢ Comprehensive system diagnostics
➢ Complete range of I/O modules
➢ Simple, online module repair

Confidential Property of Schneider Electric | Page 25

Internal
Feature of the ITCC Hardware
ITCC systems are designed based on Triconex TMR controllers, which are certified for use based on IEC-
61508 SIL 3.1. To meet the system availability, redundant and/or fault tolerant technology, All Tricon hardware
used (except the chassis power supply) is based on TMR technology. The following shall be redundant:
➢ TMR Tricon Controllers
➢ TMR I/O Modules
➢ Triplicated internal communication path
➢ Redundant ITCC TCM communication network(HMI and EWS/SOE)
➢ Redundant communication interface with other devices(if applicable)
➢ Redundancy on the Tricon Chassis Power Supply
➢ Redundancy on the Field Power (24VDC) Supply

Confidential Property of Schneider Electric | Page 26

Internal
Typical ITCC Triconex TMR Architecture

Confidential Property of Schneider Electric | Page 27

Internal
Description ITCC Triconex TMR Architecture
A Tricon system contains :
Three Main Processor (MP) Modules to control three separate legs of the system. Each Main Processor
operates in parallel with the other two Main Processors.
A dedicated I/O Communication (IOC) processor on each Main Processor manages the data exchanged
between the Main Processors and the I/O modules. A triplicated I/O Bus is located on the chassis backplane
and is extended from chassis to chassis by means of I/O Bus Cables.
As each input module is polled, the new input data is transmitted to the Main Processor over the appropriate leg
of the I/O Bus. The input data from each Input Module is assembled into a table in the Main Processor and
stored in memory for use in the hardware voting process. The individual input table in each Main Processor is
transferred to its neighboring Main Processors over the proprietary TRIBUS. During this transfer, hardware
voting takes place. The TRIBUS uses a Direct Memory Access programmable device to synchronize, transmit,
vote, and compare data among the three Main Processors.

Confidential Property of Schneider Electric | Page 28

Internal
Typical Interface with Other System

HMI
HMI PANEL MOUNT
(Control DCS
(Rack Room)
& Ex-Proof HMI
Room)

Simplex
TCP/IP + DDE Duplex Modbus TCP/
TCP/IP + DDE IP (Redundant)
Operation Zone

Hardwire

Triconex
LGB/LOP
SSP/LCS ITCC
TMR ESD
Controller

Hardwire
OSTM

Field Instruments
Field Tx..etc)
(Valves, Tx,
Instruments (Valves, SOV,...etc)
Legend
DCS : Distributed Control System
HMI: Human Machine Interface
ESD: Emergency Shutdown Device
LGB: Local Gauge Board
LOP: Local Operation Panel
OSTM: Overspeed Trip Module

Confidential Property of Schneider Electric | Page 29

Internal
Human-Machine Interface (HMI)

Confidential Property of Schneider Electric | Page 30

Internal
Feature of the ITCC HMI Software
Feature of ITCC Software
ITCC HMI use Wonderware Software is compose of Application Manager, WindowMaker and WindowViewer.
The InTouch Application Manager organizes the applications that are created. It is also used to configure
WindowViewer as an NT service, to configure Network Application Development (NAD) for client-based and
server-based architectures, to configure Dynamic Resolution Conversion (DRC) and/or distributed alarming.
The DBDump and DBLoad database utilities are also launched from the Application Manager.
WindowMaker is the development environment, where object-oriented graphics are used to create animated,
touch-sensitive display windows. These display windows can be connected to industrial I/O systems and other
Microsoft Windows applications.
WindowViewer is the runtime environment used to display the graphic windows created in WindowMaker.
WindowViewer executes InTouch Quick Scripts, performs historical data logging and reporting, processes
alarm logging and reporting, and can function as a client and a server for both DDE and Suite Link
communication protocols.

Confidential Property of Schneider Electric | Page 31

Internal
ITCC Project HMI Software
The Wonderware InTouch consists of three major programs, the InTouch Application Manager,
WindowMaker and WindowViewer.
There are two licensing options available for the Wonderware InTouch application – InTouch Development
license and 2InTouch Runtime license.
The InTouch Application Manager organizes the applications that are created. It is also used to configure
WindowViewer as an NT service, to configure Network Application Development (NAD) for client-based
and server-based architectures, to configure Dynamic Resolution Conversion (DRC) and/or distributed
alarming.
The DBDump and DBLoad database utilities are also launched from the Application Manager.

Confidential Property of Schneider Electric | Page 32

Internal
ITCC Project HMI Software
WindowMaker is the development environment, where object-oriented graphics are used to create
animated, touch-sensitive display windows. These display windows can be connected to industrial I/O
systems and other Microsoft Windows applications. The WindowMaker environment will only be available
when the InTouch Development license have been utilized.
WindowViewer is the runtime environment used to display the graphic windows created in WindowMaker.
WindowViewer executes InTouch Quick Scripts, performs historical data logging and reporting, processes
alarm logging and reporting, and can function as a client and a server for both DDE and Suite Link
communication protocols.
The WindowViewer environment can be viewed or operated with either the InTouch Development or
InTouch Runtime license.

Confidential Property of Schneider Electric | Page 33

Internal
ArchestrA Integrated Development Environment (IDE)
ArchestrA Integrated Development Environment (IDE) provides the graphical enhancement for InTouch.
ArchestrA Symbols are graphics you can create and use to visualize data in an InTouch HMI system.
ArchestrA Symbol Editor can be used to create ArchestrA Symbols from basic elements, such as rectangles,
lines, and text elements. After creating an ArchestrA Symbol, it can be embedded it into another symbol or an
InTouch window and use it at run time. An ArchestrA Symbol can be embedded in a template or instance of
an ArchestrA Object, providing a way to visualize object-specific information quickly and easily. Embedding a
symbol in a template means that you can update one symbol and cascade the changes throughout your
application.
The ArchestrA Symbol Editor is a powerful addition to WindowMaker with graphical enhancement.

Confidential Property of Schneider Electric | Page 34

Internal
Tristation 1131

Confidential Property of Schneider Electric | Page 35

Internal
TriStation 1131
Triconex offers a programming system for developing, testing and documenting process control applications
that execute in the Tricon controller. This programming system is the TriStation 1131 version 5.0.1(TS1131).

The TS1131 version 5.0.1software runs in Microsoft Windows 10. It supports the Function Block Diagram,
Ladder Diagram and Structured Text programming languages, which comply with IEC1131 standard.

TriStation 1131 is an easy-to-use software system featuring Windows-like graphical interface and a
comprehensive set of tools for efficiently developing System applications. The Function Block Diagram
programming provides the ability to develop simple, as well as complex governor and Anti-Surge control
schemes for this application.

Confidential Property of Schneider Electric | Page 36

Internal
4 ITCC Application

Internal
ITCC Application

Turbine Start
Sequence

Control
Modules
Turbine/Comp.
Operation
Application
Navigation HMI
Components

HMI Operation

Confidential Property of Schneider Electric | Page 38

Internal
System Description

Confidential Property of Schneider Electric | Page 39

Internal
System Description
➢ Hardware
The following ITCC hardware is included in this design:
• Triconex – PLC (Tricon) with one main and one expansion chassis and redundant communication
modules.
• Triconex – Redundant power supplies
• Triconex – I/O Modules and Termination assemblies
➢ Workstations
One dedicated HMI OWS is provided for each Compressor train and will communicate with ITCC (Tricon) via
Ethernet network. Another common Engineering WorkStation EWS/SOE is provided for logic development
and edit purposes.

The OWS has InTouch Wonderware development license for engineering development work, and has
RunTime license for visualization and monitoring of turbine and compressor related process data.

Confidential Property of Schneider Electric | Page 40

Internal
System Description
➢ Overspeed Trip Device
A dedicated overspeed trip module ProTech-GII is installed in the OSP/BN Cabinet for overspeed trip.
Dedicated three speed probes from field are directly wired to the ProTech-GII, with four Trip outputs wired to
the ESD. There are two hard-wired input signals to ProTech-GII for trip reset and speed fail override from
ITCC. One hard-wired signal to DCS on the system fault alarm.

Confidential Property of Schneider Electric | Page 41

Internal
Description of Modes/ Permissive
➢ Start Permissive come from DCS, the detail refer to the DCS system.
➢ Start Sequence and mode refer to the Start Sequence of CGC, ERC and PRC

Confidential Property of Schneider Electric | Page 42

Internal
Steam Turbine Control Solutions
➢ The governing systems have following basic functions:
• Turbine startup sequence as per OEM startup curves.
• Normal speed/load control.
• Overspeed trip.
In addition, the turbine controls include a number of other functions such as start-up/shut-down controls.
➢ The speed/load control is a fundamental requirement
• Achieved through control of governor valve.
• Load control function achieved by adjusting speed/load reference.
➢ The overspeed control and protection is peculiar to steam turbines.
• It is critical importance for safe operation.
• Speed should be limited to well below the design maximum speed of 120%.

Confidential Property of Schneider Electric | Page 43

Internal
Governor Control (Start Sequence)

Confidential Property of Schneider Electric | Page 44

Internal
Start Sequence - CGC

Confidential Property of Schneider Electric | Page 45

Internal
System Overview - CGC

Confidential Property of Schneider Electric | Page 46

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 47

Internal
Turbine Startup Sequencing

Mode 5

Mode 4

Mode 3
Mode 2

Confidential Property of Schneider Electric | Page 48

Internal
Turbine Startup Sequencing
Mode
Description Target Speed (RPM)
Number
0 Shutdown 0
1 Ready to Start 0
2 1st Idle Speed 600
3 2nd Idle Speed 1200
4 Acceleration 2910
5 Run 2910 – 4365
6 Overspeed Test –

Confidential Property of Schneider Electric | Page 49

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 50

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 51

Internal
Turbine startup sequencing
MODE 0 - SHUTDOWN

Entered Conditions :
➢ Any trips (Trip Table)
➢ In Mode 1 if Start Permissive is lost

Confidential Property of Schneider Electric | Page 52

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN - Trip Table
S/NO TRIP INITAITOR CONDITIONS
.

1 When ITCC is powered down -

2 All ITCC Main Processor Fail -

3 Fail Safe Timer Expired Actual Speed < 250 RPM, after
10 minutes, upon Start
Command issued.

4 Electronic Overspeed Trip Actual Speed > 4758 RPM

5 Loss of Speed Pickups (3oo3) All 3 pickup signals
failed (< 200 RPM)

6 ESD Common Trip -

Confidential Property of Schneider Electric | Page 53

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN – Permissive
Governor Start Permissive is sent from DCS to ITCC via softlink

Confidential Property of Schneider Electric | Page 54

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN

Actions :
➢ ITCC common trip signal is sent to LCP/ESD/DCS/HMI.
➢ The Shutdown timer starts (counting up).
➢ The Trip Speed Recorder records the speed at trip.
➢ The Speed Controller output is clamped to 0%.
➢ The minimum and maximum limits on the GV and ECV are set to
0 %, and forces the GV and ECV to close.
➢ Inlet Steam Pressure Control is disabled and its status is sent to
DCS/HMI.
➢ The Performance Controller is disabled and its status sent to
DCS/HMI.

Confidential Property of Schneider Electric | Page 55

Internal
Turbine Startup Sequencing
MODE 0 - SHUTDOWN

Actions :

➢ Anti-Surge control algorithm is disabled, placed in Partial Manual and

their status sent to DCS/HMI. Anti-surge valves outputs will force to
100% open.
➢ Anti-Surge controllers Manual Demands are initialized to 100%.
➢ Anti-surge controllers can be placed in Full Manual mode to enable
ASV stroking provided the turbine speed is less than 50 RPM.
➢ UZV-2401A output current limit will be set at 4 mA (100% Opening)
to 20mA ( 0% Opening)

Confidential Property of Schneider Electric | Page 56

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN - Shutdown Timer

Confidential Property of Schneider Electric | Page 57

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN – Start-Up Type / Permissive

Confidential Property of Schneider Electric | Page 58

Internal
Turbine Startup Sequencing
MODE 1 – READY TO START

Conditions :
➢ In Shutdown mode, all trips conditions have been cleared
➢ Governor start permissive are met.

Confidential Property of Schneider Electric | Page 59

Internal
Turbine Startup Sequencing
MODE 1 – READY TO START
Actions :
➢ First-out Trip flag is reset.
➢ Common Trip indication is reset and sent to LCP/ESD/DCS/HMI.
➢ Ready to Start indication is sent to LCP/DCS/HMI.
➢ Warm up timers (1st Idle and 2nd Idle Speed Warm-up Timers) are reset.
➢ Anti-Surge control algorithms remain disabled, placed in Partial Manual
and their status is sent to DCS/HMI. Anti-surge valves outputs will be
force to 100% open.
➢ Anti-Surge controllers Manual Demand are initialized to 100%
➢ Performance Control and Pressure control remain disabled.
➢ The minimum and maximum limits on the GV and ECV are set to 0 %,
and forces the GV and ECV to close.
➢ UZV-2401A output current limit will be set at 4 mA (100% Opening) to
20mA ( 0% Opening)
Confidential Property of Schneider Electric | Page 60
Internal
Turbine Startup Sequencing
MODE 1 – READY TO START

Confidential Property of Schneider Electric | Page 61

Internal
Turbine Startup Sequencing
MODE 2 – 1ST IDLE SPEED

Entered Conditions :
➢ In Ready to Start mode, when “Turbine Start” command is issued
from DCS/HMI.

Confidential Property of Schneider Electric | Page 62

Internal
Turbine Startup Sequencing
MODE 2 – 1ST IDLE SPEED
Actions :
➢ Target Speed Setpoint is set to 1st Idle speed (600 RPM). The
Actual Speed Setpoint is ramped towards the target at Normal
Ramp Rate (180 RPM/min).
➢ Target Speed Setpoint is clamped between (0 RPM) and 1st Idle
Speed (600 RPM).
➢ In Auto Start, TTV to be opened fully by field operator before
pressing the Auto Start PB.
➢ When entering from Ready to Start mode, the Peak and Trip
speed recorder are reset and peak speed recorder starts
recording the maximum speed.
➢ Shutdown timer is stopped.

Confidential Property of Schneider Electric | Page 63

Internal
Turbine Startup Sequencing
MODE 2 – 1ST IDLE SPEED

Actions :

➢ Warm up timer (1st Idle Speed Warm-up Timer) will count up when
conditions are fulfilled (refer to Section 4.2.2).
➢ ECV will ramp to 100% at a ramp rate of 1%/sec.
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be force to 100% open.
➢ UZV-2401A output current will ramp from 4mA ( full Open) at a ramp
rate of 0.16mA/sec (1% closing rate) to the opening limit of 14.88mA
(32% Opening)

Confidential Property of Schneider Electric | Page 64

Internal
Turbine Startup Sequencing
MODE 2 – 1st Idle Speed

Confidential Property of Schneider Electric | Page 65

Internal
Turbine Startup Sequencing
MODE 3 – 2ND IDLE SPEED

Entered Conditions :
➢ In 1st Idle speed mode, when “2nd Idle Speed” command is
issued from HMI.
➢ In Acceleration mode, when “2nd Idle Speed” command is issued
from HMI.
➢ In Acceleration mode, when Actual Speed remains in Critical
Speed Band for more than 5 mins, in this case the mode returns
back to 2nd Idle Speed mode and an alarm issued
(m1_CBT_MAX).

Confidential Property of Schneider Electric | Page 66

Internal
Turbine Startup Sequencing
MODE 3 – 2ND IDLE SPEED

Actions :
➢ Target Speed Setpoint is set to 2nd Idle speed (1200 RPM). The
Actual Speed Setpoint is ramped towards the target at Normal
Ramp Rate (180 RPM/min).
➢ Target Speed Setpoint is clamped between 1st Idle Speed (600
RPM) and 2nd Idle Speed (1200 RPM).
➢ Warm up timer (2nd Idle Speed Warm-up Timer) will count up
when conditions are fulfilled (refer to Section 4.2.2).
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be force to 100% open.
➢ UZV-2401A ASV Output Opening will be limited by the output
current of 14.88mA (32% Opening)

Confidential Property of Schneider Electric | Page 67

Internal
Turbine Startup Sequencing
MODE 3 – 2nd Idle Speed

Confidential Property of Schneider Electric | Page 68

Internal
Turbine Startup Sequencing
MODE 4 to MODE 3 – 2nd Idle Speed

Confidential Property of Schneider Electric | Page 69

Internal
Turbine Startup Sequencing
MODE4 -ACCELRATION

Entered Conditions :
➢ In 2nd Idle Speed mode, when “Accelerate” command is issued
from HMI and Actual Speed is greater than 2nd Idle Speed minus 50
RPM.
➢ Idle to Rated Permissive is received from DCS
➢ In Ready to Start mode, when “Turbine Semi-Auto Start” command
is issued from HMI

Confidential Property of Schneider Electric | Page 70

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Actions :
➢ Target Speed Setpoint is set to Minimum Governor Speed (2910
RPM). The Actual Speed Setpoint is ramped towards the target
at normal ramp rate (180 RPM/min).
➢ Target Speed Setpoint is clamped between 2nd Idle Speed
(1200 RPM) and Minimum Governor Speed (2910 RPM).
➢ While speed is in the Critical Speed Band (1674 – 2530 RPM),
the Actual Speed Setpoint is ramped towards the target at Fast
Ramp Rate (700 RPM/min).
➢ If the sequence returned back to 2nd Idle mode from
Acceleration mode because the speed remained in critical band
for more than 5 mins, the alarm flag (m1_CBT_MAX) will be
reset once 2nd Idle mode is entered.

Confidential Property of Schneider Electric | Page 71

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Actions :
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be force to 100% open.
➢ UZV-2401A ASV Output Opening will be limited by the output
current of 14.88mA (32% Opening).

Note:
For Semi-Auto Start, Turbine is started manually. Trip and Throttle Valve (TTV) will be
opened gradually. Turbine is first being warmed up at 1st Idle Speed (600 RPM) and
then proceed to warm up at 2nd Idle Speed (1200 RPM) as per the startup procedure.

After warm-up at 2nd Idle Speed is complete, the operator should carefully open TTV
to ramp through critical speed band and towards Min. Gov. Speed. TTV shall be fully
open when Gov taken controlthe operator may proceed to fully open TTV to ramp
through critical speed band and towards Min. Gov. Speed.

TPSK Operator Reference: Opening of TTV too quickly will cause speed rapidly
increase and may result in turbine / compressor vibration and trip.

Confidential Property of Schneider Electric | Page 72

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Confidential Property of Schneider Electric | Page 73

Internal
Turbine Startup Sequencing
MODE 1 to MODE4 -ACCELRATION

Confidential Property of Schneider Electric | Page 74

Internal
Turbine Startup Sequencing
MODE 5 – RUN

Entered Conditions :
➢ While in Acceleration mode, when the actual Speed reaches 50
RPM below Minimum governor speed.
➢ While in Overspeed Test mode, when “OverSpeed Trip Test” switch
is turned to “off” position from HMI.

Confidential Property of Schneider Electric | Page 75

Internal
Turbine Startup Sequencing
MODE 5 – RUN
Actions :
➢ Shutdown timer is reset.
➢ Turbine Speed
a. Target Speed Setpoint is clamped between Minimum Governor Speed
(2910 RPM) and Maximum Governor Speed (4365 RPM).
b. If Performance controller (1st stage suction pressure) is disabled, the
turbine speed setpoint can be manually adjusted by HMI through
enterable setpoint or using Raise/Lower PBs from LCP/HMI.
➢ First Stage Suction Pressure
a. The 1st stage suction pressure controller can be enabled/disabled from
HMI given that pressure transmitter signal is healthy.
b. When Performance control (1st Stage Suction Pressure) is enabled, the
controller output is cascaded to the Decoupler block to adjust the turbine
speed and the anti-surge control valve opening simultaneously to satisfy
the required suction pressure demand.
c. Operator can adjust the pressure setpoint through Raise/Lower PBs or
the enterable setpoint from HMI.
Confidential Property of Schneider Electric | Page 76
Internal
Turbine Startup Sequencing
MODE 5 – RUN
Actions :
➢ Inlet Steam Pressure Control
a. Inlet Steam pressure control can be enabled only in Run mode when
the ECV minimum limit is 0% or lower than the ECV valve output from
the two valve block. ECV minimum limit can be changed by the
operator from the HMI only by Raise/Lower pushbuttons at a ramp
rate of 1 %/sec. Inlet Steam Pressure Controller will switch to Auto
mode and start controlling the Inlet Steam Pressure using the ECV
and GV. Subsequently, the Inlet Steam Pressure Control Enable
status will be sent to DCS/HMI.
b. Inlet Steam pressure control can be disabled when the ECV minimum
limit is ramped up to 100%. Inlet Steam Pressure Controller will switch
to Manual mode, the Inlet Steam Pressure Control Disable status will
be sent to DCS/HMI.
c. When the Inlet Steam Pressure Control is in Auto mode, the Inlet
Steam Pressure Setpoint is allowed to be set by “Inlet Steam
Pressure Setpoint Raise/Lower” command or by enterable value from
HMI.
Confidential Property of Schneider Electric | Page 77
Internal
Turbine Startup Sequencing
MODE 5 – RUN
Actions :
d. If the Inlet Steam pressure transmitter fails while the Inlet Steam
pressure controller is enabled, the controller is automatically switched to
Manual mode and operator can open/close the ECV/GV through the Inlet
Steam Pressure Control Manual Demand Raise/Lower PBs from HMI.
e. When pressure transmitter returns to healthy status while controller is
enabled, the controller will remain in manual mode and can be placed
back to auto mode when the operator pushes the Inlet Steam Pressure
Control Auto command from HMI.
➢ Surge Control
a. Surge Control is enabled once Run mode is entered and all anti-surge
controllers will be initialized to Partial Manual mode automatically.
b. Operator may select Auto or Partial Manual from HMI. Refer Section
6.2.2 for details.
c. Full Manual mode is only activated if the corresponding flow transmitter
fails in any mode.
Confidential Property of Schneider Electric | Page 78
Internal
Turbine Startup Sequencing
MODE 5 – RUN

Actions :
d. UZV-2401A ASV Output Opening will be limited by the output
current of 14.88mA (32% Opening).
➢ Overspeed Trip Test
a. Overspeed Trip (EOST / IOST) tests can be selected from HMI in
Run mode.

For Information:
In Run Mode, all anti-surge controllers will be initialized to Partial
Manual mode automatically. Any anti-surge controller in Full
Manual due to flow transmitter failure and had recovered but not
placed back into Partial Manual by the operator will be initialized to
Partial Manual mode.

Confidential Property of Schneider Electric | Page 79

Internal
Turbine Startup Sequencing
MODE 5 -RUN

Confidential Property of Schneider Electric | Page 80

Internal
Turbine Startup Sequencing
MODE 6 – OVERSPEED TRIP TEST

Entered Conditions :
➢ In Run mode, either EOST or IOST is selected from HMI.
➢ Inlet Steam Pressure Control and Performance Control are
disabled.
➢ Anti-surge Valves commands are 100%.

Confidential Property of Schneider Electric | Page 81

Internal
Turbine Startup Sequencing
MODE 6 – OVERSPEED TRIP TEST

Actions :
➢ Overspeed Test indication will be sent to DCS/HMI.
➢ Target Speed Setpoint is clamped between Minimum Governor
Speed (2910 RPM) and MAXGOV speed (k1_ MAXGOV /
k1_EOSTMAXGOV / k1_IOSTMAXGOV ) according to the previous
table.
➢ Anti-Surge control algorithm is disabled, placed in Partial Manual
and their status sent to DCS/HMI.
➢ Turbine will trip when Actual Speed is greater than Overspeed
Setpoint and mode will return back to shutdown mode.
➢ UZV-2401A ASV Output Opening will be limited by the output
current of 14.88mA (32% Opening).

Confidential Property of Schneider Electric | Page 82

Internal
Turbine Startup Sequencing
MODE 6 - OVERSPEED TRIP TEST

Confidential Property of Schneider Electric | Page 83

Internal
Start Sequence - ERC

Confidential Property of Schneider Electric | Page 84

Internal
System Overview - ERC

Confidential Property of Schneider Electric | Page 85

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 86

Internal
Turbine Startup Sequencing

Mode 5

Mode 4

Mode 3
Mode 2

Confidential Property of Schneider Electric | Page 87

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 88

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 89

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 90

Internal
Turbine Startup Sequencing
MODE 0 - SHUTDOWN

Entered Conditions :
➢ Any trip occurs (Refer to Trip Conditions).
➢ While turbine is in Ready to Start mode and a Start Permissive is
lost.

Confidential Property of Schneider Electric | Page 91

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN - Trip Table

Confidential Property of Schneider Electric | Page 92

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN – Permissive

➢ Governor Start Permissive is send from DCS to ITCC via softlink

Confidential Property of Schneider Electric | Page 93

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN
Actions :
➢ ITCC common trip signal is sent to LCP/ESD/DCS/HMI.
➢ The Shutdown timer starts (counting up).
➢ The Trip Speed Recorder records the speed at trip.
➢ The Speed Controller output is clamped to 0%.
➢ The minimum and maximum limits on the GV and ECV are set to 0
%, and forces the GV and ECV to close.
➢ Extraction Pressure Control is disabled and its status is sent to
DCS/HMI.
➢ The Performance Controller is disabled and its status sent to
DCS/HMI.
➢ Anti-Surge control algorithm is disabled, placed in Partial Manual
and their status sent to DCS/HMI. Anti-surge valves outputs will
force to 100% open.
Confidential Property of Schneider Electric | Page 94
Internal
Turbine Startup Sequencing
MODE 0 - SHUTDOWN

Actions :
➢ Anti-Surge controllers Manual Demands are initialized to 100%.
➢ Anti-surge controllers can be placed in Full Manual mode to enable
ASV stroking provided the turbine speed is less than 50 RPM.
➢ UZV-2855 output current limit will be set at 4 mA (100% Opening) to
20mA ( 0% Opening)
➢ UZV-2856 output current limit will be set at 4 mA (100% Opening) to
20mA ( 0% Opening)
➢ UZV-2857 output current limit will be set at 4 mA (100% Opening) to
20mA ( 0% Opening)

Confidential Property of Schneider Electric | Page 95

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN - Shutdown timer

Confidential Property of Schneider Electric | Page 96

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN – Start-Up Type / Permissive

Confidential Property of Schneider Electric | Page 97

Internal
Turbine Startup Sequencing
MODE 1 – READY TO START

Conditions :
➢ In Shutdown mode, all trips conditions have been cleared
➢ Governor start permissive are met.

Confidential Property of Schneider Electric | Page 98

Internal
Turbine Startup Sequencing
MODE 1 – READY TO START

Actions :
➢ First-out Trip flag is reset.
➢ Common Trip” indication is reset and sent to LCP/ESD/DCS/HMI.
➢ Ready to Start indication is sent to LCP/DCS/HMI.
➢ Warm up timers (1st Idle and 2nd Idle Speed Warm-up Timers) are
reset.
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be forced to 100% open.
➢ Anti-Surge controllers Manual Demand are initialized to 100%
➢ Performance Control and Extraction Pressure control remain
disabled.

Confidential Property of Schneider Electric | Page 99

Internal
Turbine Startup Sequencing
MODE 1 – READY TO START

Actions :
➢ The minimum and maximum limits on the GV and ECV are set to
0 %, and forces the GV and ECV to close.
➢ UZV-2855 output current limit will be set at 4 mA (100% Opening)
to 20mA ( 0% Opening)
➢ UZV-2856 output current limit will be set at 4 mA (100% Opening)
to 20mA ( 0% Opening)
➢ UZV-2857 output current limit will be set at 4 mA (100% Opening)
to 20mA ( 0% Opening)

Confidential Property of Schneider Electric | Page 100

Internal
Turbine Startup Sequencing
MODE 1 – READY TO START

Confidential Property of Schneider Electric | Page 101

Internal
Turbine Startup Sequencing
MODE 2 – 1ST IDLE SPEED

Entered Conditions :
➢ In Ready to Start mode, when “Turbine Auto Start” command is
issued from LGB/DCS/HMI.

Confidential Property of Schneider Electric | Page 102

Internal
Turbine Startup Sequencing
MODE 2 – 1ST IDLE SPEED
Actions :
➢ Target Speed Setpoint is set to 1st Idle speed (500 RPM). The Actual
Speed Setpoint is ramped towards the target at Normal Ramp Rate
(250 RPM/min).
➢ Target Speed Setpoint is clamped between (0 RPM) and 1st Idle
Speed (500 RPM).
➢ In Auto Start, TTV to be opened fully by field operator before pressing
the Auto Start PB.
➢ When entering from Ready to Start mode, the Peak and Trip speed
recorders are reset and peak speed recorder starts recording the
maximum speed.
➢ Shutdown timer is stopped.
➢ Warm up timer (1st Idle Speed Warm-up Timer) will count up when
conditions are fulfilled (refer to Section 4.2.2).
➢ ECV will ramp to 100% at a ramp rate of 1%/sec.
Confidential Property of Schneider Electric | Page 103
Internal
Turbine Startup Sequencing
MODE 2 – 1ST IDLE SPEED

Actions :
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be forced to 100% open.
➢ UZV-2855 output current will ramp from 4mA ( full Open) at a ramp
rate of 0.16mA/sec (1% closing rate) to the opening limit of 13.60mA
(40% Opening)
➢ UZV-2856 output current will ramp from 4mA ( full Open) at a ramp
rate of 0.16mA/sec (1% closing rate) to the opening limit of 12.80mA
(45% Opening)
➢ UZV-2857 output current will ramp from 4mA ( full Open) at a ramp
rate of 0.16mA/sec (1% closing rate) to the opening limit of 12.96mA
(44% Opening)

Confidential Property of Schneider Electric | Page 104

Internal
Turbine Startup Sequencing
MODE 2 – 1st Idle Speed

Confidential Property of Schneider Electric | Page 105

Internal
Turbine Startup Sequencing
MODE 3 – 2ND IDLE SPEED

Entered Conditions :
➢ In 1st Idle speed mode, when “2nd Idle Speed” command is
issued from HMI.
➢ In Acceleration mode, when “2nd Idle Speed” command is issued
from HMI.
➢ In Acceleration mode, when Actual Speed remains in Critical
Speed Band for more than 5 mins, in this case the mode returns
back to 2nd Idle Speed mode and an alarm issued
(m3_CBT_MAX).

Confidential Property of Schneider Electric | Page 106

Internal
Turbine Startup Sequencing
MODE 3 – 2ND IDLE SPEED
Actions :
➢ Target Speed Setpoint is set to 2nd Idle speed (1000 RPM). The
Actual Speed Setpoint is ramped towards the target at Normal
Ramp Rate (250 RPM/min).
➢ Target Speed Setpoint is clamped between 1st Idle Speed (500
RPM) and 2nd Idle Speed (1000 RPM).
➢ Warm up timer (2nd Idle Speed Warm-up Timer) will count up
when conditions are fulfilled (refer to Section 4.2.2).
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be forced to 100% open.
➢ UZV-2855 output current will ramp from 4mA ( full Open) at a
ramp rate of 0.16mA/sec (1% closing rate) to the opening limit of
13.60mA (40% Opening)

Confidential Property of Schneider Electric | Page 107

Internal
Turbine Startup Sequencing
MODE 3 – 2ND IDLE SPEED

Actions :
➢ UZV-2856 output current will ramp from 4mA ( full Open) at a ramp
rate of 0.16mA/sec (1% closing rate) to the opening limit of 12.80mA
(45% Opening)
➢ UZV-2857 output current will ramp from 4mA ( full Open) at a ramp
rate of 0.16mA/sec (1% closing rate) to the opening limit of 12.96mA
(44% Opening)
➢ UZV-2855 ASV Output Opening will be limited by the output current
of 13.60mA (40% Opening)
➢ UZV-2856 ASV Output Opening will be limited by the output current
of 12.80mA (45% Opening)
➢ UZV-2857 ASV Output Opening will be limited by the output current
of 12.96mA (44% Opening)

Confidential Property of Schneider Electric | Page 108

Internal
Turbine Startup Sequencing
MODE 3 – 2ND IDLE SPEED

Confidential Property of Schneider Electric | Page 109

Internal
Turbine Startup Sequencing
MODE 4 To MODE 3 – 2ND IDLE SPEED

Confidential Property of Schneider Electric | Page 110

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Entered Conditions :
➢ In 2nd Idle Speed mode, when “Accelerate” command is issued
from HMI and Actual Speed is greater than 2nd Idle Speed minus 50
RPM
➢ Idle to Rated Permissive is received from DCS
➢ In Ready to Start mode, when “Turbine Semi-Auto Start” command
is issued from HMI

Confidential Property of Schneider Electric | Page 111

Internal
Turbine Startup Sequencing
MODE4 -ACCELRATION
Actions :
➢ Target Speed Setpoint is set to Minimum Governor Speed (4584
RPM). The Actual Speed Setpoint is ramped towards the target
at normal ramp rate (250 RPM/min).
➢ Target Speed Setpoint is clamped between 2nd Idle Speed
(1000 RPM) and Minimum Governor Speed (4584 RPM).
➢ While speed is in the Critical Speed Band (1204 – 3300 RPM),
the Actual Speed Setpoint is ramped towards the target at Fast
Ramp Rate (1000 RPM/min).
➢ If the sequence returned back to 2nd Idle mode from
Acceleration mode because the speed remained in critical band
for more than 5 mins, the alarm flag (m3_CBT_MAX) will be
reset once 2nd Idle mode is entered.
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be forced to 100% open.
Confidential Property of Schneider Electric | Page 112
Internal
Turbine Startup Sequencing
MODE4 -ACCELRATION

Actions :
➢ UZV-2855 ASV Output Opening will be limited by the output
current of 13.60mA (40% Opening)
➢ UZV-2856 ASV Output Opening will be limited by the output
current of 12.80mA (45% Opening)
➢ UZV-2857 ASV Output Opening will be limited by the output
current of 12.96mA (44% Opening)

Confidential Property of Schneider Electric | Page 113

Internal
Turbine Startup Sequencing
MODE4 -ACCELRATION

Actions :

Note:
For Semi-Auto Start, Turbine is started manually. Trip and Throttle Valve (TTV) will be opened gradually.
Turbine is first being warmed up at 1st Idle Speed (500 RPM) and then proceed to warm up at 2nd Idle
Speed (1000 RPM) as per the startup procedure.

After warm-up at 2nd Idle Speed is complete, the operator should carefully open TTV to ramp through
critical speed band and towards Min. Gov. Speed. TTV shall be fully open when Gov taken control.

TPSK Operator Reference: Opening of TTV too quickly will cause speed rapidly increase and may result
in turbine / compressor vibration and trip.

Confidential Property of Schneider Electric | Page 114

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Confidential Property of Schneider Electric | Page 115

Internal
Turbine Startup Sequencing
MODE 1 to MODE 4 -ACCELRATION

Confidential Property of Schneider Electric | Page 116

Internal
Turbine Startup Sequencing
MODE 5 – RUN

Entered Conditions :
➢ While in Acceleration mode, when the actual Speed reaches 50
RPM below Minimum governor speed.
➢ While in Overspeed Test mode, when “Overspeed Trip Test” switch
is turned to “OFF” position from HMI.

Confidential Property of Schneider Electric | Page 117

Internal
Turbine Startup Sequencing
MODE 5 – RUN
Actions :
➢ Shutdown timer is reset.
➢ Turbine Speed
a. Target Speed Setpoint is clamped between Minimum Governor
Speed (4584 RPM) and Maximum Governor Speed (6876 RPM).
b. If Performance controller (1st stage suction pressure) is disabled, the
turbine speed setpoint can be manually adjusted by HMI through
enterable setpoint or using Raise/Lower PBs from LCP/HMI.
➢ First Stage Suction Pressure
a. The 1st stage suction pressure controller can be enabled/disabled
from HMI given that pressure transmitter signal is healthy.
b. When Performance control (1st Stage Suction Pressure) is enabled,
the controller output is cascaded to the Decoupler block to adjust the
turbine speed and the anti-surge control valve opening
simultaneously to satisfy the required suction pressure demand.
c. Operator can adjust the pressure setpoint through Raise/Lower PBs
or the enterable setpoint from DCS/HMI.
Confidential Property of Schneider Electric | Page 118
Internal
Turbine Startup Sequencing
MODE 5 – RUN
Actions :
➢ Extraction Pressure Control
a. Extraction pressure control can be enabled only in Run mode when the
ECV minimum limit is 0% or lower than the ECV valve output from the
two-valve block. ECV minimum limit can be changed by the operator
from the HMI only by Raise/Lower pushbuttons at a ramp rate of 1
%/sec. Extraction Pressure Controller will switch to Auto mode and
start controlling the Extraction Pressure using the ECV and GV.
Subsequently, the Extraction Pressure Control Enable status will be
sent to DCS/HMI.
b. Extraction pressure control can be disabled when the ECV minimum
limit is ramped up to 100%. Extraction Pressure Controller will switch
to Manual mode, the Extraction Pressure Control Disable status will be
sent to DCS/HMI.
c. When the Extraction Pressure Control is in Auto mode, the Extraction
Pressure Setpoint is allowed to be set by “Extraction Pressure Setpoint
Raise/Lower” command or by enterable value from HMI.
Confidential Property of Schneider Electric | Page 119
Internal
Turbine Startup Sequencing
MODE 5 – RUN
Actions :
a. If the extraction pressure transmitter fails while the extraction
pressure controller is enabled, the controller is automatically
switched to Manual mode and operator can open/close the ECV
through the ECV Manual Demand Raise/Lower PBs from HMI.
b. When extraction pressure transmitter returns to healthy status while
controller is enabled, the controller will remain in manual mode and
can be placed back to auto mode when the operator pushes the
Extraction Control Auto command from HMI.

➢ Overspeed Trip Test

a. Overspeed Trip (EOST / IOST) tests can be selected from HMI in
Run mode.

Confidential Property of Schneider Electric | Page 120

Internal
Turbine Startup Sequencing
MODE 5 -RUN

Confidential Property of Schneider Electric | Page 121

Internal
Turbine Startup Sequencing
MODE 6 – OVERSPEED TRIP TEST

Entered Conditions :
➢ In Run mode, either EOST or IOST is selected from HMI.
➢ Extraction Pressure Control and Performance Control are
disabled.
➢ Anti-surge Valves commands are 100%.

Confidential Property of Schneider Electric | Page 122

Internal
Turbine Startup Sequencing
MODE 6 – OVERSPEED TRIP TEST

Actions :
➢ Overspeed Test indication will be sent to DCS/HMI.
➢ Target Speed Setpoint is clamped between Minimum Governor
Speed (4584 RPM) and MAXGOV speed (k3_ MAXGOV /
k3_EOSTMAXGOV / k3_IOSTMAXGOV ) according to the previous
table.
➢ Anti-Surge control algorithm is disabled, placed in Partial Manual
and their status sent to DCS/HMI.
➢ Turbine will trip when Actual Speed is greater than Overspeed
Setpoint and mode will return back to shutdown mode.

Confidential Property of Schneider Electric | Page 123

Internal
Turbine Startup Sequencing
MODE 6 – OVERSPEED TRIP TEST

Confidential Property of Schneider Electric | Page 124

Internal
Start Sequence - PRC

Confidential Property of Schneider Electric | Page 125

Internal
System Overview - PRC

Confidential Property of Schneider Electric | Page 126

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 127

Internal
Turbine Startup Sequencing

Mode 5

Mode 4

Mode 3
Mode 2

Confidential Property of Schneider Electric | Page 128

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 129

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 130

Internal
Turbine Startup Sequencing

Confidential Property of Schneider Electric | Page 131

Internal
Turbine Startup Sequencing
MODE 0 - SHUTDOWN

Entered Conditions :
➢ Any trip occurs (Refer to Trip Conditions).
➢ While turbine is in Ready to Start mode and a Start Permissive is
lost.

Confidential Property of Schneider Electric | Page 132

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN - Trip Table

Confidential Property of Schneider Electric | Page 133

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN – Permissive

➢ Governor Start Permissive is send from DCS to ITCC via softlink

Confidential Property of Schneider Electric | Page 134

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN

Actions :
➢ ITCC common trip signal is sent to LCP/ESD/DCS/HMI.
➢ The Shutdown timer starts (counting up).
➢ The Trip Speed Recorder records the speed at trip.
➢ The Speed Controller output is clamped to 0%.
➢ The minimum and maximum limits on the GV and ICV are set to 0
%, and forces the GV and ICV to close.
➢ Induction Pressure Control is disabled and its status is sent to
DCS/HMI.
➢ The Performance Controller is disabled and its status sent to
DCS/HMI.

Confidential Property of Schneider Electric | Page 135

Internal
Turbine Startup Sequencing
MODE 0 - SHUTDOWN

Actions :
➢ Anti-Surge control algorithm is disabled, placed in Partial Manual
and their status sent to DCS/HMI. Anti-surge valves outputs will
force to 100% open.
➢ Anti-Surge controllers Manual Demands are initialized to 100%.
➢ Anti-surge controllers can be placed in Full Manual mode to enable
ASV stroking provided the turbine speed is less than 50 RPM.

Confidential Property of Schneider Electric | Page 136

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN - Shutdown timer

Confidential Property of Schneider Electric | Page 137

Internal
Turbine Startup Sequencing
MODE 0 – SHUTDOWN – Start-Up Type / Permissive

Confidential Property of Schneider Electric | Page 138

Internal
Turbine Startup Sequencing
MODE 1 – READY TO START

Conditions :
➢ All trips conditions have been cleared,
➢ Reset command is issued, and all permissives are met.

Confidential Property of Schneider Electric | Page 139

Internal
Turbine Startup Sequencing
MODE 1 – READY TO START
Actions :
➢ First-out Trip flag is reset.
➢ Common Trip” indication is reset and sent to LCP/ESD/DCS/HMI.
➢ Ready to Start indication is sent to LCP/DCS/HMI.
➢ Warm up timers (1st Idle and 2nd Idle Speed Warm-up Timers) are
reset.
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be force to 100% open.
➢ Anti-Surge controllers Manual Demand are initialized to 100%
➢ Performance control and Induction Pressure control remain
disabled.
➢ The minimum and maximum limits on the GV and ICV are set to 0
%, and forces the GV and ICV to close.
Confidential Property of Schneider Electric | Page 140
Internal
Turbine Startup Sequencing
MODE 1 – READY TO START

Confidential Property of Schneider Electric | Page 141

Internal
Turbine Startup Sequencing
MODE 2 – 1ST IDLE SPEED

Entered Conditions :
➢ In Ready to Start mode, when “Turbine Auto Start” command is
issued from LGB/DCS/HMI.

Confidential Property of Schneider Electric | Page 142

Internal
Turbine Startup Sequencing
MODE 2 – 1ST IDLE SPEED

Actions :
➢ Target Speed Setpoint is set to 1st Idle speed (500 RPM). The
Actual Speed Setpoint is ramped towards the target at Normal
Ramp Rate (180 RPM/min).
➢ Target Speed Setpoint is clamped between (0 RPM) and 1st Idle
Speed (500 RPM).
➢ In Auto Start, TTV to be opened fully by field operator before
pressing the Auto Start PB.
➢ When entering from Ready to Start mode, the Peak and Trip
speed recorder are reset and peak speed recorder starts
recording the maximum speed.
➢ Shutdown timer is stopped.
➢ Warm up timer (1st Idle Speed Warm-up Timer) will count up
when conditions are fulfilled

Confidential Property of Schneider Electric | Page 143

Internal
Turbine Startup Sequencing
MODE 2 – 1ST IDLE SPEED

Actions :
➢ ICV maximum limit will ramp to 100% at a ramp rate of 1%/sec.
➢ Induction pressure controller will be Disabled and in Manual mode.
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be force to 100% open.

Confidential Property of Schneider Electric | Page 144

Internal
Turbine Startup Sequencing
MODE 2 – 1st Idle Speed

Confidential Property of Schneider Electric | Page 145

Internal
Turbine Startup Sequencing
MODE 3 – 2ND IDLE SPEED

Entered Conditions :
➢ In 1st Idle speed mode, when “2nd Idle Speed ” command is
issued from HMI.
➢ In Acceleration mode, when “2nd Idle Speed ” command is issued
from HMI.
➢ In Acceleration mode, when Actual Speed remains in Critical
Speed Band for more than 3 mins, in this case the mode returns
back to 2nd Idle Speed mode and an alarm issued
(m2_CBT_MAX).

Confidential Property of Schneider Electric | Page 146

Internal
Turbine Startup Sequencing
MODE 3 – 2ND IDLE SPEED

Actions :
➢ Target Speed Setpoint is set to 2nd Idle speed (1000 RPM). The
Actual Speed Setpoint is ramped towards the target at Normal
Ramp Rate (180 RPM/min).
➢ Target Speed Setpoint is clamped between 1st Idle Speed (500
RPM) and 2nd Idle Speed (1000 RPM).
➢ Warm up timer (2nd Idle Speed Warm-up Timer) will count up
when conditions are fulfilled (refer to Section 4.2.2).
➢ Induction pressure controller will be Disabled and in Manual
mode.
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be force to 100% open.

Confidential Property of Schneider Electric | Page 147

Internal
Turbine Startup Sequencing
MODE 3 – 2ND IDLE SPEED

Confidential Property of Schneider Electric | Page 148

Internal
Turbine Startup Sequencing
MODE 4 to MODE 3 – 2ND IDLE SPEED

Confidential Property of Schneider Electric | Page 149

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Entered Conditions :
➢ In 2nd Idle Speed mode, when “Accelerate” command is issued
from HMI and Actual Speed is greater than 2nd Idle Speed minus 50
RPM.
➢ Idle to Rated Permissive is received from DCS
➢ In Ready to Start mode, when “Turbine Semi-Auto Start” command
is issued from HMI

Confidential Property of Schneider Electric | Page 150

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Actions :
➢ Target Speed Setpoint is set to Minimum Governor Speed (2390
RPM). The Actual Speed Setpoint is ramped towards the target
at normal ramp rate (180 RPM/min).
➢ Target Speed Setpoint is clamped between 2nd Idle Speed
(1000 RPM) and Minimum Governor Speed (2390 RPM).
➢ While speed is in the Critical Speed Band (1395 – 1815 RPM),
the Actual Speed Setpoint is ramped towards the target at Fast
Ramp Rate (700 RPM/min).
➢ If the sequence returned back to 2nd Idle mode from
Acceleration mode because the speed remained in critical band
for more than 3 mins, the alarm flag (m2_CBT_MAX) will be
reset once 2nd Idle mode is entered.

Confidential Property of Schneider Electric | Page 151

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Actions :
➢ Induction pressure controller will be Disabled and in Manual
mode, Raise/Lower PBs will be available for the operator to
open/close the ICV from HMI if necessary.
➢ Anti-Surge control algorithms remain disabled, placed in Partial
Manual and their status is sent to DCS/HMI. Anti-surge valves
outputs will be force to 100% open.

Confidential Property of Schneider Electric | Page 152

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Actions :

Confidential Property of Schneider Electric | Page 153

Internal
Turbine Startup Sequencing
MODE 4 -ACCELRATION

Confidential Property of Schneider Electric | Page 154

Internal
Turbine Startup Sequencing
MODE 1 to MODE 4 -ACCELRATION

Confidential Property of Schneider Electric | Page 155

Internal
Turbine Startup Sequencing
MODE 5 – RUN

Entered Conditions :
➢ While in Acceleration mode, when the actual Speed reaches 50
RPM below Minimum governor speed.
➢ While in Overspeed Test mode, when “Overspeed Trip Test” switch
is turned to “off” position from HMI.

Confidential Property of Schneider Electric | Page 156

Internal
Turbine Startup Sequencing
MODE 5 – RUN
Actions :
➢ Shutdown timer is reset.
➢ Turbine Speed
a. Target Speed Setpoint is clamped between Minimum Governor Speed
(2390 RPM) and Maximum Governor Speed (3585 RPM).
b. If Performance controller (1st stage suction pressure) is disabled, the
turbine speed setpoint can be manually adjusted by HMI through
enterable setpoint or using Raise/Lower PBs from LCP/HMI.
➢ First Stage Suction Pressure
a. The 1st stage suction pressure controller can be enabled/disabled
from HMI given that pressure transmitter signal is healthy.
b. When Performance control (1st Stage Suction Pressure) is enabled,
the controller output is cascaded to the Decoupler block to adjust the
turbine speed and the anti-surge control valve opening simultaneously
to satisfy the required suction pressure demand.
c. Operator can adjust the pressure setpoint through Raise/Lower PBs
or the enterable setpoint from DCS/HMI.
Confidential Property of Schneider Electric | Page 157
Internal
Turbine Startup Sequencing
MODE 5 – RUN

Actions :
➢ Induction Pressure Control
a. Induction pressure control is enabled only in Run mode when the
ICV maximum limit is ramped down to 0%. ICV maximum limit can
be changed by the operator from the HMI only by Raise/Lower
pushbuttons at a ramp rate of 1 %/sec. Induction Pressure
Controller will switch to Auto mode and start controlling the
Induction Pressure using the ICV and GV. Subsequently, the
Induction Pressure Control Enable status will be sent to DCS/HMI.
b. Induction pressure control can be disabled when the ICV maximum
limit is ramped up to 100%. Accordingly, Induction Pressure
Controller will switch to Manual mode and the Induction Pressure
Control Disable status will be sent to DCS/HMI.
c. When the Induction Pressure Control is in Auto mode, the Induction
Pressure Setpoint is allowed to be set by “Induction Pressure
Setpoint Raise/Lower” command or by enterable value from HMI.

Confidential Property of Schneider Electric | Page 158

Internal
Turbine Startup Sequencing
MODE 5 – RUN

Actions :
d. If the induction pressure transmitter fails while the induction
pressure controller is enabled, the controller is automatically
switched to Manual mode and operator can open/close the ICV
through the ICV Manual Demand Raise/Lower PBs from HMI.
e. When Induction pressure transmitter returns to healthy status while
controller is enabled, the controller will remain in manual mode and
can be placed back to auto mode when the operator pushes the
Induction Control Auto command from HMI.

Confidential Property of Schneider Electric | Page 159

Internal
Turbine Startup Sequencing
MODE 5 – RUN

Actions :
➢ Surge Control
a. Surge Control is enabled once Run mode is entered and all anti-
surge controllers will be initialized to Partial Manual mode
automatically.
b. Operator may select Auto or Partial Manual from HMI.
c. Full Manual mode is only activated if the corresponding flow
transmitter fails in any mode.
➢ Overspeed Trip Test
a. Overspeed Trip (EOST / IOST) tests can be selected from HMI in
Run mode.

Confidential Property of Schneider Electric | Page 160

Internal
Turbine Startup Sequencing
MODE 5 – RUN

Actions :

Confidential Property of Schneider Electric | Page 161

Internal
Turbine Startup Sequencing
MODE 5 – RUN

Confidential Property of Schneider Electric | Page 162

Internal
Turbine Startup Sequencing
MODE 6 – OVERSPEED TRIP TEST

Entered Conditions :
➢ In Run mode, either EOST or IOST is selected from HMI.
➢ Induction Pressure Control and Performance Control are disabled.
➢ Anti-surge Valves commands are 100%.

Confidential Property of Schneider Electric | Page 163

Internal
Turbine Startup Sequencing
MODE 6 – OVERSPEED TRIP TEST

Actions :
➢ Overspeed Test indication will be sent to DCS/HMI.
➢ Target Speed Setpoint is clamped between Minimum Governor
Speed (2390 RPM) and MAXGOV speed (k2_ MAXGOV /
k2_EOSTMAXGOV / k2_IOSTMAXGOV ) according to the previous
table.
➢ Anti-Surge control algorithm is disabled, placed in Partial Manual
and their status sent to DCS/HMI.
➢ Turbine will trip when Actual Speed is greater than Overspeed
Setpoint and mode will return back to shutdown mode.

Confidential Property of Schneider Electric | Page 164

Internal
Turbine Startup Sequencing
MODE 6 – OVERSPEED TRIP TEST

Confidential Property of Schneider Electric | Page 165

Internal
Governor Control – ITCC Controller (CGC for example)

Confidential Property of Schneider Electric | Page 166

Internal
Governor Control (Speed Control and Extraction Control)

Confidential Property of Schneider Electric | Page 167

Internal
 Governor Control – ITCC Controller
Steam Turbine and Extraction Control

HP LP
Governing Governing
Valve Valve

Main Steam
Header

Compressor

Super Heat Steam

Turbine Inlet
Extraction Outlet

Condenser

Enthalpy (i)
in
e He1
tL
an Sa
st tu
on rate
Water C Lin
re e
su He2
Zone es
Pr

Turbine Outlet
Hc
Wet Steam

Entropy (s)

Confidential Property of Schneider Electric | Page 168

Internal
 Governor Control – ITCC Controller
Steam Turbine and Extraction Control

Confidential Property of Schneider Electric | Page 169

Internal
Governor Control – Speed Control
During turbine start-up, pre-defined Target Speed setpoint is set based on the active startup
sequence mode as well as Operator commands..
During Run mode, Operator can control the turbine speed with one of two ways:
➢ When Performance Control is disabled, Speed Control is placed into Manual Speed
Control mode and operator can adjust the turbine speed setpoint manually using
Raise/Lower pushbuttons on LCP/HMI or through enterable setpoint from HMI.
➢ When Performance Control is enabled, Speed Control is placed into Performance Control
(auto) mode, and turbine speed setpoint is generated by the ITCC Process-Decoupler
function via the Performance Controller.
During Overspeed Test Mode, performance control is disabled and Speed Control is in manual
mode.

Confidential Property of Schneider Electric | Page 170

Internal
Governor Control – Speed Selection
1. Turbine Speed Selection
This logic function selects one of the three passive speed pickups use in the control logic. The
selected speed is used in the Speed PID function block and for overspeed protection.
2. Enable Pickup Failure
Any speed input that falls below speed pickup failure setpoint (200 RPM) will be considered failed.
Failed pickups will not be used by the speed selection logic. Speed failure is inhibited during the
Shutdown mode and thereafter until turbine speed is greater than 250 RPM. At this speed, the
Enable Speed Failure flag is set true. The individual fail flags will then become false if their speed
input falls below the speed pickup failure setpoint.

Confidential Property of Schneider Electric | Page 171

Internal
Governor Control – Speed Selection
3. Loss of Speed
If all three (3oo3) pickups fail, the Compressor train is tripped.
4. Selected Speed
Prior to the speed pickup failure enable, the selected speed output is equal to the highest of the
probes.
Thereafter, if all three speed pickups are healthy, the selected speed output is equal to the median
value. If two speed pickups are healthy, the highest speed pickup is selected. If only one speed pickup
is healthy, the remaining healthy speed pickup is used. A trip is initiated, when all three speed pickups
fail. Note that a "healthy" pickup is one that is neither failed nor disabled.

Confidential Property of Schneider Electric | Page 172

Internal
Governor Control – Speed Selection
Speed Difference Alarm
An alarm is issued if there is a deviation of more than 10 RPM between healthy pickups.
Turbine Speed Setpoint
This module generates the target speed setpoint. The actual speed setpoint is ramped to match the
target setpoint at the proper rate, and uses a higher rate while in the critical band. The target speed
setpoint is not allowed to reside in the critical band.
Speed Setpoint Limits
The minimum and maximum target limits for each sequence mode are configured. Target speed
setpoint will be clamped within the operating limits. This prevents step changes in the setpoint that
could cause instability in the control loop.

Confidential Property of Schneider Electric | Page 173

Internal
Governor Control – Speed Setpoint Limits

Confidential Property of Schneider Electric | Page 174

Internal
Governor Control – Speed PID
The PID controller is standard. The algorithm compares the process variable (PV) and setpoint
(SP). The controller action will minimize the error between setpoint and measurement. Controller
output rate is determined by the tuning constants (Gain, Reset). The speed PID controller is always
in Auto mode.

Confidential Property of Schneider Electric | Page 175

Internal
Governor Control – Inlet Steam Pressure Control
During Run mode, when Inlet Steam Pressure Control is enabled, ECV will throttle to control turbine
load (speed) and the GV will throttle to control Inlet Steam Pressure. When limiting conditions are
active, speed control is set as priority. Limits include Inlet Steam Pressure minimum/maximum limits
and maximum power limit.
When limiting conditions occur, the control priority will be given to the speed control and the Inlet
Steam Pressure Control will be sacrificed. When this happens, a back-calculation for the Inlet Steam
Pressure demand will be performed by the 2-valve algorithm to restrict the demand from Inlet Steam
Pressure Controller. This is necessary to avoid a bump in control when the system moves away from
the limiting conditions. Because the Inlet Steam Pressure Controller is located in the ITCC, so the
controller output tracking will be done internally in ITCC.

Confidential Property of Schneider Electric | Page 176

Internal
Governor Control – Inlet Steam Pressure Control
To maximize process stability, valve action is managed by a two-valve coordination function. This function
minimizes the process interaction from individual valve movement and permits dynamic speed and Inlet
steam pressure control loop tuning.

Confidential Property of Schneider Electric | Page 177

Internal
Governor Control – Inlet Steam Pressure Control Enable
Inlet Steam pressure control can be enabled only in Run mode when the Inlet Steam Pressure transmitter is
healthy and when the ECV minimum limit is 0% or lower than the ECV valve output from the two valve block.
ECV minimum limit can be changed by the operator from the HMI only by Raise/Lower pushbuttons at a
ramp rate of 1 %/sec.
Inlet Steam pressure control will be disabled when the ECV minimum limit is ramped up to 100%.
The " Inlet Steam Pressure Control Enable/ Disable" status flag will be sent to DCS for indication.

Confidential Property of Schneider Electric | Page 178

Internal
Governor Control – Inlet Steam Pressure Control Auto/Manual
When Inlet Steam Pressure Control is enabled and the Inlet Steam Pressure transmitter is healthy, the Inlet
Steam Pressure Controller is placed to Auto and begins to accept setpoint from HMI.
When Inlet Steam Pressure Control is disabled, the Inlet Steam Pressure Controller is placed to Manual and
the Inlet Steam Pressure Setpoint will track the Inlet Steam Pressure measurement.
In the event of transmitter failure while the controller is enabled, the Inlet Steam Pressure Controller is
switched to Manual mode. The Inlet Steam Pressure Controller can be placed back in auto when the
transmitter is recovered and the operator pushes the Inlet Steam Control Auto command from HMI.
When Induction pressure controller is enabled, it can be switched into manual mode, raise / lower push
button will be available for the operator to open / close the inlet steam pressure control manual demand from
HMI if necessary.

Confidential Property of Schneider Electric | Page 179

Internal
Governor Control – Inlet Steam Pressure Control PID
The PID controller is standard. The algorithm compares the process variable (PV) and setpoint (SP). The
controller action will minimize the error between setpoint and measurement. Controller output rate is
determined by the tuning constants (Gain, Reset).

Confidential Property of Schneider Electric | Page 180

Internal
Governor Control – PID Track
To maximize process stability, valve action is managed by a two-valve coordination function. This function
minimizes the process interaction from individual valve movement and permits dynamic speed and Inlet
steam pressure control loop tuning.
When the Two-Valve Algorithm limiting conditions track flags turn on, the Inlet Steam Pressure PID Controller
Output will track the back-calculated value from the Two-Valve Algorithm.

Confidential Property of Schneider Electric | Page 181

Internal
Governor Control – Inlet Steam Pressure Transmitter Fallback
When the Inlet Steam pressure transmitter fails, the Inlet Steam pressure controller remains
enabled but the controller is placed in Manual mode.
When the transmitter has recovered, the controller will remain in manual mode and can be placed
back to auto mode when the operator pushes the Inlet Steam Pressure Control Auto command
from HMI.

Confidential Property of Schneider Electric | Page 182

Internal
Governor Control – Two Valve Algorithm
The Two-Valve Algorithm uses both the Speed Output and Inlet steam Pressure Demand to determine
GV and ECV positions. The module limits valve travel based on valve limits and load limit priority will be
given to speed in the case that both Inlet Steam pressure and speed cannot be maintained.
The following table describes the actions of the GV and ECV upon changes in speed and Inlet Steam
Pressure demands.
The Two-Valve Algorithm uses both the Speed Output and Inlet steam Pressure Demand to determine
GV and ECV positions. The module limits valve travel based on valve limits and load limit priority will be
given to speed in the case that both Inlet Steam pressure and speed cannot be maintained.
The following table describes the actions of the GV and ECV upon changes in speed and Inlet Steam
Pressure demands.

Confidential Property of Schneider Electric | Page 183

Internal
Governor Control – Response and Parameter

Confidential Property of Schneider Electric | Page 184

Internal
Anti-surge Control (CGC for Example)

Confidential Property of Schneider Electric | Page 185

Internal
 Compressor Control
A gas compressor is a mechanical device that increases the pressure of a gas by reducing its
volume.
Compressors are similar to pumps both increase the pressure on a fluid and both can transport the
fluid through a pipe. As gases are compressible, the compressor also reduces the volume of a gas.
Liquids are relatively incompressible, so the main action of a pump is to transport liquids.
Reverse path on Ts thermodynamic diagram with prime mover
Turbo compressor having specific condition named surge which happens when compressor can not
compress anymore due to process changes, sometimes issue damage to compressor when surge
occurs. To protect surge, Compressor control or Anti-Surge Controller is required.

Confidential Property of Schneider Electric | Page 186

Internal
 Compressor-P&ID and schematic (CGC)

Confidential Property of Schneider Electric | Page 187

Internal
 Anti-Surge Control – Performance Map
Anti-Surge control margins

Maximum speed

Expected Surge
limit Line
Power limit

Potential choke limit Line

Stable zone
of operation
Actual available Minimum speed
operating zone

Confidential Property of Schneider Electric | Page 188

Internal
 Surge Cycle

1->2, System resistance increases, more discharge

pressure required and operating point moves up the
Pressure
curve.
2->3, Operating Point nears the surge Limit 3 2
3->4, Operating Point goes into surge Region
4->5, Drop in discharge pressure re-establishes
forward flow. Compressor resumes full flow 4
1
5
Since resistance has not changed, surge will
continue until cycle is broken. Flow

➢ Operating Point moves from stability into surge at the speed of sound at the gas conditions in the
compressor.
➢ A complete surge cycle takes from 1/2 to 3 seconds, depending on the size of the compressor,
piping volume.
Confidential Property of Schneider Electric | Page 189
Internal
 Causes and Harm of Compressor Surge
➢ What cause compressor surge?
• Upstream or downstream process shutdown, reducing compressor flow.
• Compressor operating in a region where it cannot maintain the pressure ratio (process pressure)
at the given flow rate.
➢ What harm can compressor surge cause ?
• The process can be upset because of flow reversals.
• Compressor seals can be damaged, leading to poor compressor efficiency.
• Severe surge can cause catastrophic failure of the compressor, resulting in partial or complete
loss of process capacity.

Confidential Property of Schneider Electric | Page 190

Internal
 How Can Surge be Prevented?
➢ Accurate determination of the operating point.
➢ Anticipatory action of the Surge Controller.
➢ Opening the recycle valve to increase flow through the compressor and
decrease pressure ratio.

Pressure
FIC
xxx

Flow

Confidential Property of Schneider Electric | Page 191

Internal
 Universal Surge Curve

Confidential Property of Schneider Electric | Page 192

Internal
 Anti-Surge Control - Solution Surge Control Features

Confidential Property of Schneider Electric | Page 193

Internal
 Anti-Surge Control - Solution Surge Control Features
➢ Universal Surge Line
➢ Surge Controller Setpoint Hover
➢ Automatic Adjustment of Safety Margin
➢ Independent Proportional Term
➢ Surge PID Controller with Adaptive Tuning
➢ Controlled Opening/Slow Closing of Recycle Valve
➢ Manual Recycle Valve Control Options
➢ Fallback strategy for faulty transmitters

Confidential Property of Schneider Electric | Page 194

Internal
 Anti-Surge Control - Universal Surge Line

Head Term

Pd
100% N
Ps 90% N
80% N

hs
Flow Term
Ps

Confidential Property of Schneider Electric | Page 195

Internal
 Anti-Surge Control FIC
xxx

Surge Surge Override

Counter Increase Line
Surge Control Hover
Line Line Line

Operating Point

Confidential Property of Schneider Electric | Page 196

Internal
Anti-Surge Anti-Surge Controller Interface

Confidential Property of Schneider Electric | Page 197

Internal
Anti-Surge Anti-Surge Controller Interface
➢ All the process related values.
➢ Easy to identify the output value (ASV output).
➢ Easy to identify the controller status.
➢ DCS/HMI selection.
➢ Auto\Partial\Full Manual mode selection.
➢ Surge Counter Reset
➢ Recalibration Reset
➢ Minimum Flow Reset
➢ PV <-> DEV
➢ OP == OUT

Confidential Property of Schneider Electric | Page 198

Internal
Anti-Surge Anti-Surge Controller Interface

Confidential Property of Schneider Electric | Page 199

Internal
 Anti-Surge Control - Solution Surge Control Features
➢ Universal Surge Line
➢ Surge Controller Setpoint Hover
➢ Automatic Adjustment of Safety Margin
➢ Independent Proportional Term
➢ Adaptive Tuning
➢ Controlled Opening/Slow Closing of Recycle Valve
➢ Manual Recycle Valve Control Options

Confidential Property of Schneider Electric | Page 200

Internal
 Anti-Surge Control - Setpoint Hover

Confidential Property of Schneider Electric | Page 201

Internal
 Anti-Surge Control - Solution Surge Control Features
➢ Universal Surge Line
➢ Surge Controller Setpoint Hover
➢ Automatic Adjustment of Safety Margin
➢ Independent Proportional Term
➢ Adaptive Tuning
➢ Controlled Opening/Slow Closing of Recycle Valve
➢ Manual Recycle Valve Control Options

Confidential Property of Schneider Electric | Page 202

Internal
 Anti-Surge Control - Control Line Recalibration

Confidential Property of Schneider Electric | Page 203

Internal
Anti-Surge Control - Control Line Recalibration

Hover Point Operating Point

Hover Margin

10

Confidential Property of Schneider Electric | Page 204

Internal
Anti-Surge Control - Control Line Recalibration

Hover Point Operating Point

10

Confidential Property of Schneider Electric | Page 205

Internal
Anti-Surge Control - Control Line Recalibration

10

Confidential Property of Schneider Electric | Page 206

Internal
Anti-Surge Control - Control Line Recalibration

10

Confidential Property of Schneider Electric | Page 207

Internal
Anti-Surge Control - Control Line Recalibration

10

Confidential Property of Schneider Electric | Page 208

Internal
 Anti-Surge Control - Solution Surge Control Features
➢ Universal Surge Line
➢ Surge Controller Setpoint Hover
➢ Automatic Adjustment of Safety Margin
➢ Independent Proportional Term
➢ Adaptive Tuning
➢ Controlled Opening/Slow Closing of Recycle Valve
➢ Manual Recycle Valve Control Options

Confidential Property of Schneider Electric | Page 209

Internal
 Anti-Surge Control - Surge Override

10

Confidential Property of Schneider Electric | Page 210

Internal
Anti-Surge Control - Surge Override

0%
Closed
Surge Control Line
Proportional Output
rSUCLN
Or Surge Override
50%
rPROTM

Open 100%
Proportional
Initiation
Surge Limit Line
rSULIN
Py%
10%

7%
Safety Margin
5%
rMAR

0%

hX%

Confidential Property of Schneider Electric | Page 211

Internal
 Anti-Surge Control - Solution Surge Control Features
➢ Universal Surge Line
➢ Surge Controller Setpoint Hover
➢ Automatic Adjustment of Safety Margin
➢ Independent Proportional Term
➢ Adaptive Tuning
➢ Controlled Opening/Slow Closing of Recycle Valve
➢ Manual Recycle Valve Control Options

Confidential Property of Schneider Electric | Page 212

Internal
 Anti-Surge Control - Adaptive Tuning

Confidential Property of Schneider Electric | Page 213

Internal
 Anti-Surge Control - Solution Surge Control Features
➢ Universal Surge Line
➢ Surge Controller Setpoint Hover
➢ Automatic Adjustment of Safety Margin
➢ Independent Proportional Term
➢ Adaptive Tuning
➢ Controlled Opening/Slow Closing of Recycle Valve
➢ Manual Recycle Valve Control Options

Confidential Property of Schneider Electric | Page 214

Internal
 Anti-Surge Control - Controlled Opening
➢Controlled Opening
• Don’t open the recycle valve faster than the process can respond.
• Opening too much, too fast will protect the compressor, but may cause suction pressure relief
valves to open or vent to flare!
➢Slow Closing
• Allows turbine speed controller/process cascade controller to smoothly adjust to new process
operating conditions.
• Maintains process stability.

Confidential Property of Schneider Electric | Page 215

Internal
 Anti-Surge Control - Solution Surge Control Features
➢ Universal Surge Line
➢ Surge Controller Setpoint Hover
➢ Automatic Adjustment of Safety Margin
➢ Independent Proportional Term
➢ Adaptive Tuning
➢ Controlled Opening/Slow Closing of Recycle Valve
➢ Manual Recycle Valve Control Options

Confidential Property of Schneider Electric | Page 216

Internal
 Anti-Surge Control - Manual Recycle Valve Control
➢Partial Authority
• Only allows the operator to open the valve above the surge controller demand.
• Operator cannot close the recycle valve below the surge controller demand.
➢Full Authority
• Allows operator to close the recycle valve below the surge controller demand.
• Used if flow transmitter fails.
• Useful to stroke test recycle valve prior to startup.

Confidential Property of Schneider Electric | Page 217

Internal
Performance Control Control (CGC for Example)

Confidential Property of Schneider Electric | Page 218

Internal
 Performance Control – Suction Pressure Control

Performance
Controller Enable/
Disable Selector
(HMI)

Process Speed Setpoint

Suction
Setpoint Suction
Suct. Press. SP (DCS/HMI) Pressure
Generate Pressure
PID
SP Surge Valve
Raise/Lower (DCS/HMI) Suction Pressure Proc Enable
Ramp
SP Ramp Rate Process/
Surge
Surge Margin Tracking_Flag
Decoupling

Suction Pressure ASV Demand

Srg_Lim

(SPDSPA-MinGov)/
(MaxGov-MinGov) Demand Track

Confidential Property of Schneider Electric | Page 219

Internal
 Performance Control – Suction Pressure Control
The Performance Controller resides in ITCC and controls Compressor 1st Stage Suction Pressure at
the required pressure setpoint. The Performance Controller consists of Setpoint Generator module
and Suction Pressure PID Controller. The output of Performance Controller is sent as Process
Demand (0% - 100%) input for the Process-Decoupler function to manipulate the turbine speed as
well as 1st – 3rd stage anti-surge valve in order to control compressor suction pressure at the required
setpoint.

Confidential Property of Schneider Electric | Page 220

Internal
 Performance Control – Suction Pressure Control Enable
Performance Control can be enabled only in Run mode, local/remote selector switch is in “Remote”
and the Suction Pressure Transmitter is healthy via the "Performance Control Enable/Disable" switch
from HMI. It is disabled in all other sequence modes.
The "Performance Control Enable/Disable” status flag is sent to DCS.
When Performance Control is enabled, the Suction Pressure Controller is placed to Auto and begins to
accept setpoint from HMI.
When Performance Control is disabled, the Suction Pressure Controller is placed to tracking mode.

Confidential Property of Schneider Electric | Page 221

Internal
 Performance Control – Suction Pressure Control
Setpoint Generation
Operator can only enter the Target Setpoint from HMI or via using the raise/lower buttons from HMI,
whenever the Performance Control is enabled.
Setpoint Ramp
The Actual Suction Pressure Setpoint is ramped to match the Suction Pressure Target Setpoint at a ramp rate
of 0.6 KG/CM2G/min
Suction Pressure Controller
The PID controller is standard. The algorithm compares the process variable (PV) and setpoint (SP). The
controller action will minimize the error between setpoint and measurement. Controller output rate is
determined by the tuning constants (Gain, Reset). The suction pressure PID controller is configured as
follows:

Confidential Property of Schneider Electric | Page 222

Internal
 Performance Control – Suction Pressure Control
Transmitter Failure Fallback Strategy
There is only one Suction Pressure transmitter for this compressor used in performance control.
When the Suction Pressure Transmitter fails, Performance Control is disabled and the Suction
Pressure Controller is placed in tracking mode. Speed Control reverts to Manual Speed Control.
When the transmitter has recovered, it will be put back into service automatically. Performance
Controller can be enabled by the operator from HMI.

Confidential Property of Schneider Electric | Page 223

Internal
 Performance Control – Suction Pressure Control
The purpose of the Performance controller is to maintain suction pressure. This is achieved by
manipulating the turbine speed in conjunction with the opening of the surge valve.
Traditionally, Performance Control has been accomplished using a process PID controller to modulate the
turbine speed.
The decoupling function of ITCC inhibits the two controllers from interacting by preventing the Anti-surge
controller measurement from decreasing below its setpoint. Once the split range output has reached the
control line, the decoupling function will shift from manipulating the turbine speed to manipulating the anti-
surge valve position. This split range is unique such that the point at which the controller switches
between turbine speed and surge valve is variable.

Confidential Property of Schneider Electric | Page 224

Internal
 Performance Control – Suction Pressure Control

Confidential Property of Schneider Electric | Page 225

Internal
 Performance Control – Suction Pressure Control
The point at which Performance Control switches from controlling turbine speed to opening the surge
valve is called the dynamic breakpoint. Represented by BP in Figure above
The surge operating point determines whether the dynamic breakpoint ramps up or down. If the operating
point is above the safety margin, the breakpoint integrates downward. If the operating point is less than
the Anti-surge control line, the breakpoint integrates upward. There is a maximum ramp rate imposed to
avoid a quick downturn if operating at a high margin.
Another important feature of the dynamic breakpoint is its hover capability. The breakpoint is prevented
from decreasing less than a hover amount to the left of the capacity control output. If the output of the
capacity controller drops quickly, it becomes less than the dynamic breakpoint and opens the surge
valve. As long as the surge margin is higher than the safety margin, the breakpoint is slowly integrated
down, thereby lowering the speed and closing the surge valve at the same time.

Confidential Property of Schneider Electric | Page 226

Internal
 Performance Control – Suction Pressure Control

Confidential Property of Schneider Electric | Page 227

Internal
4 HMI Operation

Internal
HMI Screens Navigation between Graphics

Confidential Property of Schneider Electric | Page 229

Internal
 Introduction of Human-Machine Interface
➢ The HMI provides complete visualization of exactly what’s going on in the controlled and / or
monitored process at all times through high-resolution color graphical and tabular displays.
➢ Supervisory controls are issued using a combination of cursor positioning and keyboard
action. Unique graphical plotting techniques provide real-time, adaptive visualization of
process and machine operating parameters not previously available to operators.
➢ Schneider Electric application engineering molds together field proven hardware, software.
➢ Wonderware, InTouch visualization software and critical control and safety system expertise
into a comprehensive Human-Machine Interface System.
➢ InTouch consists of three major programs, the InTouch Application Manager, WindowMaker
and WindowViewer.

Confidential Property of Schneider Electric | Page 230

Internal
 Human-Machine Interface Definition
➢ The HMI screen is separated into three windows, (top, center, and bottom)
➢ Screens are developed with different resolution to fit with different monitor’s scree size
➢ Symbols with specific color ,backgrounds and displays.

Confidential Property of Schneider Electric | Page 231

Internal
HMI Window Layout

Confidential Property of Schneider Electric | Page 232

Internal
HMI Screens - ITCC – Top Banner
The Top Banner window is always visible at the top of the display screen. This window area provides:
➢ Project Name.
➢ Indication / Change of Access level.
➢ Common Alarm/ Trip/ indication.
➢ Small Active Alarm Summary highlights the five latest alarms.
➢ A set of Quick Links that when clicked on, calls up other windows.
➢ Schneider Electric-Invensys, Triconex logo & Information.
➢ Time and Date displays.

Confidential Property of Schneider Electric | Page 233

Internal
HMI Screens - ITCC – Top Banner
The Access Level Bar shows the current security level for the HMI application. The operator can access
the login interface by selecting the Access Graphic. Preconfigured usernames will appear, and the
operator will be required to enter the password.
The common Trip/ Alarm Status will turn on if any alarm/ trip is active, the graphic will be red.
The Print Screen Pushbutton is set up to execute the Print Screen command and sends the printout to
the default printer setup in the system. This can be deleted for customers who do not require a Print
Screen function.
The Alarm Summary Window is a smaller version of the alarm screen, highlighting the four latest alarms
and it is configured to display active unacknowledged alarms.
The Alarm Acknowledge Pushbutton acknowledges the alarms in the Alarm Summary.

Confidential Property of Schneider Electric | Page 234

Internal
HMI Screens - ITCC – Lower Data Banner
The Lower Data Bar window is always visible at the bottom of the display screen, and displays the
most common information relevant to the project.
The Lower Data Bar could include the following suggested items:
➢ Status Indication
➢ Turbine/compressor operating mode
➢ Control process data
➢ Controller Quicklinks arranged to depict the overview of the governor control philosophy.

Confidential Property of Schneider Electric | Page 235

Internal
HMI Screens - ITCC – Log on

Confidential Property of Schneider Electric | Page 236

Internal
HMI Screens - ITCC - Main Window
The main graphic window is located between the top banner and the lower data bar. This Window
portion is mainly used for displaying the process graphics, Alarm and events window. A list of
process windows and alarm windows to be used in the project are listed in the below table:

Confidential Property of Schneider Electric | Page 237

Internal
HMI Screens - ITCC - Main Window

Confidential Property of Schneider Electric | Page 238

Internal
 Human-Machine Interface Navigation for TPSK/Long Son LSP Project

Confidential Property of Schneider Electric | Page 239

Internal
Navigation between graphics (CGC as Example)

Confidential Property of Schneider Electric | Page 240

Internal
 HMI Screens - ITCC - Main menu

Confidential Property of Schneider Electric | Page 241

Internal
Start-up / shutdown, normal operation of compressor
(CGC as Example)

Confidential Property of Schneider Electric | Page 242

Internal
HMI Screens - ITCC - Startup and sequence

Confidential Property of Schneider Electric | Page 243

Internal
HMI Screens - ITCC - System Overview

Confidential Property of Schneider Electric | Page 244

Internal
 HMI Screens - ITCC – Steam Line

Confidential Property of Schneider Electric | Page 245

Internal
HMI Screens - ITCC - Surge Control

Confidential Property of Schneider Electric | Page 246

Internal
HMI Screens - ITCC - Surge control

Confidential Property of Schneider Electric | Page 247

Internal
HMI Screens - ITCC – Historical trends

Confidential Property of Schneider Electric | Page 248

Internal
HMI Screens - ITCC – Custom trends

Confidential Property of Schneider Electric | Page 249

Internal
Understanding alarms and responding to alarms
(CGC as Example)

Confidential Property of Schneider Electric | Page 250

Internal
HMI Screens - ITCC – Active Alarm Summary

Confidential Property of Schneider Electric | Page 251

Internal
HMI Screens - ITCC – Historical Alarm Summary

Confidential Property of Schneider Electric | Page 252

Internal
HMI Screens - ITCC – Event Summary

Confidential Property of Schneider Electric | Page 253

Internal
Controller Introduction
(CGC as Example)

Confidential Property of Schneider Electric | Page 254

Internal
HMI Screens - ITCC Controller
There are several ITCC controller for the ITCC Controller for the project. The Following
slide of CGC compressor is to illustrate the controller faceplate only.

Confidential Property of Schneider Electric | Page 255

Internal
HMI Screens - ITCC – Speed Controller

Confidential Property of Schneider Electric | Page 256

Internal
HMI Screens - ITCC – Performance Controller

Confidential Property of Schneider Electric | Page 257

Internal
HMI Screens - ITCC – Decoupling Function

Confidential Property of Schneider Electric | Page 258

Internal
HMI Screens - ITCC – Inlet Steam Pressure Controller

Confidential Property of Schneider Electric | Page 259

Internal
HMI Screens - ITCC – Antisurge Controller

Confidential Property of Schneider Electric | Page 260

Internal
HMI Screens - ITCC – Speed Controller

Confidential Property of Schneider Electric | Page 261

Internal
6 Maintenance of ITCC

Internal
 Maintenance of ITCC
➢ SOE Screen
➢ TS1131 Diagnostic screen

Confidential Property of Schneider Electric | Page 263

Internal
SOE Introduction

Confidential Property of Schneider Electric | Page 264

Internal
 SOE - Overview
The Triconex Sequence of Events (SOE) Recorder software allows you to retrieve event data from as
many as 254 Triconex controllers on a network (up to 16 controllers simultaneously).
This event data can be used to identify the causes of shutdowns, define corrective actions and
procedures for preventive maintenance, and solve other process-control problems.
Understanding the sequence of events that leads to unsafe process conditions and possible shutdowns
may be essential to the safety application.
For Triconex controllers, an event is the state change (transition) of a Boolean variable from True to
False or from False to True. A Triconex controller can collect events and record the date, time, state,
and variable name of each event in SOE blocks that reside in the controller’s memory. This figure
shows how Triconex controllers, a TriStation 1131 application, and SOE Recorder interact to provide
sequence-of-events functionality.

Confidential Property of Schneider Electric | Page 265

Internal
 SOE - Overview

Confidential Property of Schneider Electric | Page 266

Internal
 SOE - Overview
To enable event data to be detected by the controller, you must define the event variables and
SOE blocks in the TriStation 1131 application.
After you download an SOE-enabled application to the controller, the TriStation 1131 software creates an
SOE definition file that contains the SOE block definitions.
To retrieve events with SOE Recorder, you must connect the SOE Recorder PC to an open network
communication port on a Triconex controller. You must use the TriStation 1131 software to set the IP
address of the controller and you must specify the address in SOE Recorder.
SOE Recorder can simultaneously retrieve event data from as many as 16 Triconex controllers. SOE
Recorder queries all the controllers on the network to determine which TriStation 1131 applications
include SOE blocks. If an application includes one or more SOE blocks, SOE Recorder opens the
appropriate SOE definition file and begins retrieving events from the associated controller.

Confidential Property of Schneider Electric | Page 267

Internal
 SOE - Overview
You can control the specific SOE blocks that SOE Recorder should retrieve events from on a per
controller basis. SOE Recorder can save events in an events file until a trip occurs or the maximum
allowable number of events occurs. SOE Recorder can also save snapshots for periods that you specify,
such as the periods that reflect each shift of a plant’s operation. During event retrieval, you can manually
save an intermediate snapshot of event data at any time.
SOE Recorder allows you to find events and copy them to other Windows®-based applications, filter and
sort events, and view the properties of individual events.
SOE Recorder also allows you to export event data, either manually or automatically, to dBASE™ IV,
ASCII, or other file formats. A report engine and standard report are also included.

Confidential Property of Schneider Electric | Page 268

Internal
 Requirements to Install Triconex SOE Recorder
System Requirements
The following are the minimum system requirements for SOE Recorder:
➢ PC running the .NET Framework 4.5.1 and the following Windows operating systems:
— Windows 7 Professional/Enterprise (32-bit or 64-bit)
— Windows Server® 2012 R2, — Windows Server 2008 R2 (64-bit)
➢ 1 GHz processor with 512 MB RAM
➢ Free hard drive space
— For installing SOE Recorder: 10 MB
— For event collection and snapshot file generation: 8 GB
— For installing the prerequisites:
➢ TriStation 1131 and its prerequisites: 500 MB
➢ .NET 4.5.1 Framework: 850 MB (32-bit) or 2 GB (64-bit)

Confidential Property of Schneider Electric | Page 269

Internal
 Requirements to Install Triconex SOE Recorder
➢ SAP® Crystal Reports® runtime engine for .NET Framework: 850 MB
➢ CD-ROM drive
➢ Network adapter card
➢ SVGA monitor running at 1024 x 768 resolution with 64,000 colors

Confidential Property of Schneider Electric | Page 270

Internal
 Installation Procedure Triconex SOE Recorder
1. Log on to Windows as an administrator or as a user with administrator privileges.
2. Close all open applications.
3. Insert the SOE Recorder CD in the CD-ROM drive.
4. If the installation starts automatically, go to step 8. Otherwise, go to the next step.
5. From the Start menu, click Computer.
6. Double-click the CD to open it, and then browse to locate the setup.exe file.
7. Double-click setup.exe to start the installation.
8. Follow the InstallShield Wizard instructions.
9. If prompted to install prerequisite components, click Install Prerequisites. Setup will
10. install all the necessary prerequisites.

Confidential Property of Schneider Electric | Page 271

Internal
 Logging In to SOE Recorder
You must use your Windows user name and password to log in to Triconex SOE Recorder. Your
user information will be authenticated against Windows Active Directory.
1 . On the Start menu, select Programs > Triconex > Triconex SOE Recorder. The Windows login dialog
box appears.
2. Enter your Windows user name (including domain, if necessary) and password, and click OK.

Confidential Property of Schneider Electric | Page 272

Internal
 Configure SOE
To configure your Triconex controllers to collect and retrieve sequence of events information,
you must complete a series of tasks in both the TriStation 1131 software and the SOE Recorder
software.
1. Configure your TriStation 1131 application to enable SOE.
Using the TriStation 1131 software, you must configure your application to use SOE, and then
download it to the controller. You must complete this step before you can configure the SOE Recorder
software to retrieve events.
After you have configured your application to enable SOE, you can use the Triconex Emulator, which
is installed with the TriStation 1131 software, to test the SOE blocks configured in your application.
2. Configure SOE Recorder.
After your application has been configured for SOE and downloaded to the controller, you can set up
SOE Recorder to retrieve and save event information.

Confidential Property of Schneider Electric | Page 273

Internal
 Configuring Application and SOE Recorder for Event Retrieval

Confidential Property of Schneider Electric | Page 274

Internal
 Defining SOE Block Properties
This procedure explains how to define the properties of an SOE block, which is required if you are
using sequence of events in an application.
Defining SOE block properties is related to the general task of controller configuration and can be
completed at the same time. You can define SOE blocks to provide continuous event information to
external devices on a network, or you can define them for limited operation when your controller is not
on a network.
The following table lists the types of SOE blocks that can be defined for each type of sequence of
events recorder:

Confidential Property of Schneider Electric | Page 275

Internal
 Defining SOE Block Properties
1. In TriStation 1131, open the project for the application in which you want to enable SOE.
2. Click the Application tree, and double-click Implementation.
3. Expand the SOE Configuration tree, and double-click a block number.

Confidential Property of Schneider Electric | Page 276

Internal
 Defining SOE Block Properties

Confidential Property of Schneider Electric | Page 277

Internal
 Defining SOE Block Properties

Confidential Property of Schneider Electric | Page 278

Internal
 Assigning Tagnames to SOE Blocks
Tagnames must be aliased memory and/or input tagnames of type BOOL:
➢ Discrete physical input points
➢ Discrete memory read-only aliased variables, or
➢ Discrete memory read/write aliased variables
➢ Discrete output points cannot be assigned to an SOE block.

Procedure
1. In TriStation 1131, open the project for the application in which you want to enable SOE.
2. Open the Application tree and double-click Implementation.
3. Click the SOE Configuration branch. The tagnames and block assignments, if any, are listed in a
pane to the right of the tree.
4. To assign a tagname to one or more SOE Blocks, double-click the row for the tagname.

Confidential Property of Schneider Electric | Page 279

Internal
 Configuring Application and SOE Recorder for Event Retrieval
5. To assign the tagname to specific blocks, select the block number check box.
If the number is disabled, it means the block has not been defined, or the block has been defined as a
Redundant block. You cannot manually assign tagnames to Redundant blocks.
If you add tagnames after opening the SOE Configuration screen, you must close and re-open the
SOE Configuration screen for the new tagnames to appear.
6. Continue to assign tagnames to blocks as needed.
7. After assigning all the tagnames, save the project so the tagnames are available when specifying a
trip variable.

Confidential Property of Schneider Electric | Page 280

Internal
 Configuring Application and SOE Recorder for Event Retrieval
SOESTRT (SOE Start)
The SOESTRT function block starts sequence of events collection for an SOE
block.
The Main Processors write an SOESTRT time stamp entry to the block and
change the state of the block from not started or stopped, to collecting. The Main
Processors use these initial values as the basis for comparison during
subsequent scans.
If the SOESTRT operation is successful, the output status is 1, which indicates
the block is collecting data.
For each SOE block that you want to collect events from, you must execute the
SOESTRT function block before you connect SOE Recorder to the controller.
Note The SOESTRT function block is executed once per scan, which means the
resulting STAT output is only valid for that scan.

Confidential Property of Schneider Electric | Page 281

Internal
 Configuring Application and SOE Recorder for Event Retrieval
SOESTOP (SOE Stop)
The SOESTOP function block writes a time stamp to the SOE block, and
changes the state of the block from collecting to stopped. Event collection stops
until the next SOESTRT (SOE Start) operation.
If the SOESTOP operation is successful, the output status is 2, indicating that
event collection is stopped. If CI is false, no operation occurs (no output
changes).
This function block is optional. It may be useful during application development.
The SOESTOP function block is executed for only one scan, which means the
resulting STAT output is only valid for that scan.

Confidential Property of Schneider Electric | Page 282

Internal
 Configuring Application and SOE Recorder for Event Retrieval
SOECLR (SOE Clear)
The SOECLR function block clears an SOE block. SOECLR removes all entries
from the block and writes an SOECLR time stamp to the block. You must stop
event collection using SOESTOP (SOE Stop) before clearing the block.
If the SOECLR operation is successful, the output status is 2, indicating the
block is cleared. If the event collection was not stopped before the SOECLR
operation was attempted, the status is
0, 1, or 3.
If CI is false, no operation occurs (no output changes). This function block is
optional.
Note The SOECLR function block is executed for only one scan, which means
the resulting STAT output is only valid for that scan.

Confidential Property of Schneider Electric | Page 283

Internal
 Configuring the Controllers to Retrieve Events From
This section explains how to configure the Triconex controllers that SOE Recorder will be communicating
with to retrieve events.
You can configure up to 254 controllers;
Tricon controllers must be assigned to nodes 1 through 254. You cannot duplicate node numbers. You
can create the list of controllers by starting with a blank list and adding each controller individually, or by
displaying the default list of controller addresses and then modifying and deleting controllers as needed.
You can configure the controller list before event retrieval, but not during event retrieval.

Confidential Property of Schneider Electric | Page 284

Internal
 Adding a Controller
This procedure describes how to add a new controller to the list of controllers that SOE Recorder will
be retrieving events from.
1. If any events files are currently open, close them.
The controllers you configure during this procedure will apply to the next events file you create.
2. On the Tools menu, click Options, and then click the Communications tab.

Confidential Property of Schneider Electric | Page 285

Internal
 Adding a Controller

Confidential Property of Schneider Electric | Page 286

Internal
 Adding a Controller
3. Click Add. The IP Address dialog box appears:

Confidential Property of Schneider Electric | Page 287

Internal
 Copying the SOE Definition File
The SOE definition file contains SOE block definitions and point properties for the tagnames assigned
to the SOE blocks. This file is generated on the TriStation PC when you download your application to
the controller.
Depending on the configuration of the controller in your project, an SOE definition file (.soe or .soex) is
generated
You must copy the file(s) to the SOE Recorder’s SoeConfig directory before SOE Recorder can begin
retrieving events. This procedure explains how to copy the SOE definition file(s) to the SoeConfig
folder on the SOE Recorder PC.

Confidential Property of Schneider Electric | Page 288

Internal
 Procedure of Copying the SOE Definition File
1. Ensure that an SOE-enabled application is downloaded to each Triconex controller that will be collecting
events.
2. On the TriStation PC, go to the folder where your TriStation 1131 projects are stored, and locate the SOE
definition file(s).
The file name includes the first eight characters of the TriStation 1131 project name, the major version
number, the minor version number, and a time code. The name of the file is displayed in the TriStation 1131
Message Bar when the application is downloaded to the controller.
3. Copy the SOE definition file(s) to the SoeConfig folder on the SOE Recorder PC. If .soe and .soex files
were generated, you must copy both SOE definition files to the SoeConfig folder. The default location is
C:\ProgramData\Triconex\Triconex SOE Recorder\SoeConfig.
4. Repeat steps 2 and 3 for each controller that will be collecting events.

Confidential Property of Schneider Electric | Page 289

Internal
 Configuring Display Options
This procedure explains how to configure the type and order of information to display—either during event
retrieval or when viewing a saved events file—in SOE Recorder.
By default, all 10 columns of event information are displayed in the order indicated on the
screen. You can change these settings before or during event retrieval, or when viewing a saved events file.
When you create an events file, the current column display settings are automatically applied to the next file
you create unless you change the settings. Adjustments you make to column widths while an events file is
open are saved when you close the file.

Confidential Property of Schneider Electric | Page 290

Internal
 Procedure of Configuring Display Options
1. On the Tools menu, click Options.
2. Specify these settings on the Display tab.
3. Click OK to save your changes.

Confidential Property of Schneider Electric | Page 291

Internal
 Configuring Automatic Export of Event Data
This procedure explains how to configure the automatic export of event data to a dBASE IV or ASCII
journal file. You can enable this option before or after you begin retrieving events. Event data is exported to
the specified file every 20–30 seconds.
To export events, SOE Recorder must have exclusive access to the journal file. If another application
accesses the file for several minutes, SOE Recorder waits until the file is available to resume the export
activity.
The maximum size of the journal file is 2 GB. Once this limit is reached, SOE Recorder will keep collecting
events, but the journal file will no longer be updated and a message will appear in the Message Bar.
If this occurs, rename the existing journal file, or move it to another directory. SOE Recorder will then
automatically create a new journal file and restart the automatic export of event data.

Confidential Property of Schneider Electric | Page 292

Internal
 Procedure of Configuring Automatic Export of Event Data
1. On the Tools menu, click Options, and then click the Auto Export tab.
2. Select the Auto Export to a journal file check box.

Confidential Property of Schneider Electric | Page 293

Internal
 SOE File
SOE Recorder can simultaneously retrieve event data from as many as 16 Triconex controllers on a
network. You can use this event data to identify the causes of shutdowns, define corrective actions
and procedures for preventive maintenance, and solve other process-control problems.
During event retrieval, you can manually save an intermediate snapshot of event data at any time.
To analyze the event data, SOE Recorder includes tools for:
➢ Finding events and copying them to other Windows applications.
➢ Filtering and sorting saved event data.
➢ Specifying the display of point properties for event data.
➢ Viewing the properties of individual events.
SOE Recorder also allows you to export event data, either manually or automatically, to dBASEIV or
ASCII text files. A report engine and standard report are also included.

Confidential Property of Schneider Electric | Page 294

Internal
 Creating a New Events File
This procedure explains how to create a new sequence of events data file so that events can be retrieved
from the configured controllers.
When you create a new events file, SOE Recorder performs the following actions to determine which
controllers are available:
➢ The IP addresses configured in the SOE Recorder controller list (see Configuring the Controllers to
Retrieve Events are polled to determine if they are valid and if a physical connection can be made to
the controller(s).
➢ Each controller is polled to determine whether an SOE-enabled application has been downloaded and
is currently running.
➢ The SOE definition files in the SoeConfig folder on the SOE Recorder PC are compared to the
application running on the controller(s) to determine whether they match.

Confidential Property of Schneider Electric | Page 295

Internal
 Procedure Creating a New Events File
1. In SOE Recorder, on the File menu, click New Primary, New Redundant, or New Custom. One of the
following happens:
➢ For New Primary or New Redundant, the Create New SED File dialog box appears.
➢ For New Custom, you are prompted to select a custom configuration file. If you have previously
created a custom configuration file, select it. If not, create one.
2. In the File name field, enter a name for the events data file, and then click Create.

Confidential Property of Schneider Electric | Page 296

Internal
 Procedure Creating a New Events File

If the controller is available and the SOE definition file matches, the Retrieve check box is selected.

Confidential Property of Schneider Electric | Page 297

Internal
 SOE File
1. In SOE Recorder, on the File menu, click New Primary, New Redundant, or New
Custom.
One of the following happens:
➢ For New Primary or New Redundant, the Create New SED File dialog box appears.
➢ For New Custom, you are prompted to select a custom configuration file. If you have previously created a
custom configuration file, select it. If not, create one.
2. In the File name field, enter a name for the events data file, and then click Create.
3. To specify that a controller should be polled so that events can be retrieved, select the Retrieve SOE check
box next to the node name.
4. Repeat step 3 for each controller you want to retrieve events from.
5. To refresh the display, on the Command menu, click Refresh Node List.

Confidential Property of Schneider Electric | Page 298

Internal
 Starting Event Retrieval
1. Create a new events file and then select the controllers to retrieve events from.
2. With the SOE Retrieve window open, on the Command menu, click Begin Event Retrieval.
3. SOE Recorder displays events in the events file as they are retrieved from the controller. If the Auto
Scroll option is selected (in Tools > Options), the list automatically scrolls as events occur.

Confidential Property of Schneider Electric | Page 299

Internal
 Starting Event Retrieval

Confidential Property of Schneider Electric | Page 300

Internal
 Pausing Event Retrieval
1. On the Command menu, click End Event Retrieval.
2. Do NOT close the SOE Retrieve window.
3. When you are ready to resume event retrieval, on the Command menu, click Begin Event Retrieval.
Event retrieval begins again from where it left off.

Confidential Property of Schneider Electric | Page 301

Internal
 Ending Event Retrieval
1. To stop event retrieval, on the Command menu, click End Event Retrieval.

Confidential Property of Schneider Electric | Page 302

Internal
 Viewing Saved Events
1. On the File menu, click Open. The Open dialog box appears.

Confidential Property of Schneider Electric | Page 303

Internal
 Sorting Event Data
1. Open an existing events file.
2. While viewing the SOE Analysis window, on the Tools menu, click Filter and Sort Events.
3. Click the Sort tab.

Confidential Property of Schneider Electric | Page 304

Internal
 Exporting Report Data
1. Open an existing events file.
2. While viewing the SOE Analysis window, on the File menu, click Print. The report appears in the
new report viewer window.
3. On the report viewer toolbar, click the Export Report button . The Export Report dialog box appears.
4. In File name, enter a name for the report.
5. In Save as type, select the format you want to export the report to, and then click Save.
6. A confirmation message appears once the export is completed.

Confidential Property of Schneider Electric | Page 305

Internal
 Exporting Report Data

Confidential Property of Schneider Electric | Page 306

Internal
Enhanced Diagnostic Monitor Software

Confidential Property of Schneider Electric | Page 307

Internal
 Enhanced Diagnostic Monitor
The Enhanced Diagnostic Monitor allows you to view various status indicators that provide an “at-a-
glance” health status for both the overall system and individual modules.
You can also monitor the OVD status of Tricon digital output (DO) and Tricon CX supervised digital
output (SDO) modules, monitor the OVD and supervision status of Trident or Tri-GP supervised DO
modules, and display the firmware version numbers for all types of modules
The Enhanced Diagnostic Monitor allows you to view additional hardware and firmware information
for supported modules in supported Tricon controllers.

Confidential Property of Schneider Electric | Page 308

Internal
 Enhanced Diagnostic Monitor
Additionally, the Enhanced Diagnostic Monitor allows you to view and monitor real-time communication
status information, including network loading and traffic levels. Using the Triconex Field Device Tool
(FDT) Container associated with the Enhanced Diagnostic Monitor, you can view DTMs, associate a
HART-enabled device with a DTM, and configure device parameters. A Device Type Manager (DTM)
stores data specific to HART-enabled devices.
This figure shows the main steps for using the Enhanced Diagnostic Monitor to supervise Triconex
controllers on a network.

Confidential Property of Schneider Electric | Page 309

Internal
 Enhanced Diagnostic Monitor

Confidential Property of Schneider Electric | Page 310

Internal
 Enhanced Diagnostic Monitor
A user name and password is required to open the Enhanced Diagnostic Monitor. Depending on the
current security mode, you may need to log in using your Windows user name and password.
If Standard Security is enabled, there is no limit on the number of times you can attempt to enter your
user name and password. This is the default setting after installation. If Enhanced Security is enabled,
the number of times you can attempt to enter your user name and password is determined by your
Windows domain setting.
For example, if your Windows domain setting is limited to three logon attempts, after three
unsuccessful attempts to log in to the Enhanced Diagnostic Monitor, your user account will be locked
out. If this occurs, ask your network administrator to reset your Windows account.
You do not need to be a Windows administrator or a user with administrator privileges to open the
Enhanced Diagnostic Monitor or monitor controllers.

Confidential Property of Schneider Electric | Page 311

Internal
 Logging on for the First Time
The first time you log in to the Enhanced Diagnostic Monitor after installation, Standard Security is
enabled. Use the default user name (MANAGER) and password (PASSWORD) to log in.
When you log in using the default password, you are required to change the password immediately
upon logon. This is to help prevent unauthorized users from accessing the Enhanced Diagnostic
Monitor.
For additional security, you should create additional user names and passwords — including at least
two different level 01 users — before creating network configurations, and not allow multiple users to
access the Enhanced Diagnostic Monitor using the default user information.
4. Enter the logon credentials as applicable:
When Standard Security is enabled: Enter your username and password
When Enhanced Security is enabled: Enter your Windows user name (including domain, if necessary)
and password.

Confidential Property of Schneider Electric | Page 312

Internal
 Logging on for the First Time
5. Click OK.
The Diagnostic Monitor application opens in the Diagnostic Expert workspace.
6. To close the application, click Exit in the Home group. A confirmation message appears. Click Yes
to close the Enhanced Diagnostic Monitor.

Confidential Property of Schneider Electric | Page 313

Internal
 Logging On When Standard Security Is Enabled
When Standard Security is enabled, you must use your Enhanced Diagnostic Monitor user name and
password to log on.
1. On the Start menu, select Programs > Triconex > Enhanced Diagnostic Monitor. The Logon dialog
box appears.
2. Enter your username and password, and click OK.

Confidential Property of Schneider Electric | Page 314

Internal
 Setting Up a Network Configuration
A network configuration is an XML file which includes the Tricon, Trident, and Tri-GP controllers you
want to monitor. You can create network configurations for Ethernet networks, and for serial links.
You can add controllers (nodes) to a network configuration, and edit their properties as often as
needed.
To begin monitoring controllers, you must connect the diagnostic PC to the network and add each
controller node to the network configuration.
When you launch the Enhanced Diagnostic Monitor, a default network configuration file opens. You
can use this as a basis for creating your own network configuration, customized for the controllers
you want to monitor. This network configuration file is located in the path
C:\Users\Public\Documents\Triconex\Enhanced Diagnostic Monitor\Data.

Confidential Property of Schneider Electric | Page 315

Internal
 Opening a Network Configuration File
To configure and connect to the nodes (controllers) in a network configuration, a network configuration file
must be open in the Enhanced Diagnostic Monitor.
Each time you start the Enhanced Diagnostic Monitor, the default network configuration (EnDMConfig.xml)
is automatically opened. If a network configuration file is not open, it may be because it was closed using
the Close Network Configuration Command.

Confidential Property of Schneider Electric | Page 316

Internal
 Opening a Network Configuration File
This procedure open a network configuration file.
1. On the File menu, click Open Network Configuration.
The Open Network Configuration dialog box appears.
2. Browse to locate the network configuration file associated with the node (controller) you want to open.
3. Select the desired configuration file, and then click Open.
The Network Nodes tree appears, displaying a list of nodes you can configure and connect to.

Confidential Property of Schneider Electric | Page 317

Internal
 Opening a Network Configuration File

Confidential Property of Schneider Electric | Page 318

Internal
 Updating the Network Node Configuration
Updating the Network Node Configuration to Enable Secure Communication for a Tricon 11.4.x
Before you begin, verify that the controller has already been added to the network configuration, as
described in Add a Tricon Controller.
1. Open the network configuration file containing the node (controller) you want to configure secure
communication for.
2. If you are using the default network configuration file (EnDMConfig.xml), it may already be open.
3. Right-click the node name of the controller you want to configure secure communication for, and
then click Edit.
The Network Node Configuration dialog box appears.

Confidential Property of Schneider Electric | Page 319

Internal
 Setting Up a Network Configuration
4. Select the Use Secure Communication checkbox. The Secure Communication Configuration
section appears.
5. Click the browse button to search for a certificate. The Select Windows Certificate Store dialog
box appears.
You must have already added the client and server certificates to the Windows certificate store
before you can continue.
6. Select one of the options, and then click OK

Confidential Property of Schneider Electric | Page 320

Internal
 Monitoring Controller Hardware: Overview
The Enhanced Diagnostic Monitor allows you to identify alarms on Tricon chassis and Trident or Tri-
GP IOPs, and faults detected on power supplies, modules, and points.
You can also monitor the OVD status of Tricon digital output (DO) and Tricon CX supervised digital
output (SDO) modules, monitor the OVD and supervision status of Trident or Tri-GP supervised DO
modules, and display the firmware version numbers for all types of modules.

Confidential Property of Schneider Electric | Page 321

Internal
 Displaying Firmware Versions
This procedure explains how to display the firmware version numbers of all modules in a Tricon
chassis or Trident/Tri-GP IOP. Typically, you only need to know the firmware version numbers when
requested by a Customer Support Engineer for diagnostic purposes.
When you open an event file, the firmware version information saved in that event file is displayed in
the Messages pane, even if you are not actively connected to the controller.
On the Commands menu, click Display Firmware Versions.
The list of module firmware version numbers with module description appears in the Messages pane
at the bottom of the Enhanced Diagnostic Monitor window.

Confidential Property of Schneider Electric | Page 322

Internal
 Displaying Firmware Versions
The Slot column displays the location of a module using logical, not physical, slots. The default format
is Chassis.slot. In this format, board addresses are provided as decimal values, where the character
to the left of the decimal is the chassis number, and the characters to the right of the decimal is the
logical slot location. For example, the board address 7.2L refers to chassis 7, logical slot 2 Left.
To copy, print, or save the firmware version information, right-click anywhere in the Messages pane,
and then select the desired command from the shortcut menu that appears.

Confidential Property of Schneider Electric | Page 323

Internal
 Displaying Extended Module Information
The Enhanced Diagnostic Monitor allows you to view additional hardware and firmware information for
supported modules in Tricon 11.2.x and later controllers.
Extended module information includes the location, name, hardware revision, and firmware revision
for each supported module. For Tricon 11.3.x and later CX controllers, it also includes details about
additional hardware components that are installed on the same board as the module you are viewing
information for.
The Slot column displays the location of a module using logical, not physical, slots. The default format
is Chassis.slot. In this format, board addresses are provided as decimal values, where the character
to the left of the decimal is the chassis number, and the characters to the right of the decimal is the
logical slot location. For example, the board address 7.2L refers to chassis 7, logical slot 2 Left

Confidential Property of Schneider Electric | Page 324

Internal
 Displaying Extended Module Information
In Tricon 11.4 and later controllers, when the diagnostic PC is connected via a serial connection,
extended module information is available only for modules installed in chassis 0–15. This information
is not available for modules installed in chassis 16–32 as the Enhanced Diagnostic Monitor does not
display these chassis when connected via serial. To view this information for modules in chassis 16–
32, connect to the controller via a network connection.
Customer support may request detailed hardware and firmware information as they assist in
troubleshooting issues with your Tricon system. The extended module information allows you to easily
obtain this information, without having to check the physical module.

Confidential Property of Schneider Electric | Page 325

Internal
 Displaying Extended Module Information
Procedure
On the Commands menu, click Display Extended Module Information.
The extended module information for each module appears in the Messages pane at the bottom of the
Enhanced Diagnostic Monitor window.
If the Display Extended Module Information command is unavailable, it may be because the controller
is either not supported, or does not have a supported module installed.
To copy, print, or save the information, right-click anywhere in the Messages pane, and then select the
desired command from the shortcut menu that appears.
You can also generate a report that includes this module information.

Confidential Property of Schneider Electric | Page 326

Internal
 Viewing Controller Status
1. Connect to the node (controller) you want to monitor.
2. If you are connected to multiple nodes, in the Network Nodes tree, double-click the node you want
to monitor.
3. View the performance and project information for the controller in the right pane.

Confidential Property of Schneider Electric | Page 327

Internal
 Viewing Controller Status

Confidential Property of Schneider Electric | Page 328

Internal
 Viewing Controller Status

Confidential Property of Schneider Electric | Page 329

Internal
 Configuring Periodic Data Collection
1. On the Network Node menu, click Configure Periodic Data Collection.
The Configure Periodic Data Collection dialog box appears.
2. If the Enable Periodic Data Collection checkbox is not already selected, select it.
3. Depending on how often you want to collect system status data for the connected nodes, select
one of the following:
To collect data on a daily basis, click Daily, and then specify the time when you want the data to be
collected each day.
To collect data on a weekly basis, click Weekly, and then specify the time and day of the week when
you want the data to be collected.
To collect data on a monthly basis, click Monthly, and then specify the date and time you want the
data to be collected each month.

Confidential Property of Schneider Electric | Page 330

Internal
 Configuring Periodic Data Collection
4. Click OK to save the settings.
5. On the File menu, click Save Network Configuration.
Changes to the periodic data collection settings are added to the network configuration. You must
save the network configuration file before closing the Enhanced Diagnostic Monitor to confirm that
the settings are retained for future Enhanced Diagnostic Monitor sessions.

Confidential Property of Schneider Electric | Page 331

Internal
 Viewing System Status Reports
1. Open the default event log file directory associated with the network configuration file.
2. Depending on the report type and the number of nodes for which the report was generated, do one
of the following:

Confidential Property of Schneider Electric | Page 332

Internal
 Disabling Periodic Data Collection
1. On the Network Node menu, click Configure Periodic Data Collection. The Configure Periodic Data
Collection dialog box appears.
2. Clear the Enable Periodic Data Collection checkbox, and then click OK. Periodic system status
reports will no longer be generated.
3. On the File menu, click Save Network Configuration.

Confidential Property of Schneider Electric | Page 333

Internal
 Monitoring the Scan Time
1. Connect to the node (controller) you want to monitor.
If you are connected to multiple nodes, in the Network Nodes tree, double-click the node you want to
monitor.
2. In the System Overview tree, click System Overview.
3. In the right pane, view these properties, which are related to the scan time.

Confidential Property of Schneider Electric | Page 334

Internal
7 Basic Principle of Wonderware Intouch

Internal
Wonderware - General Introduction

Confidential Property of Schneider Electric | Page 336

Internal
 Wonderware System Platform
Wonderware System Platform is an industrial software platform that uses ArchestrA technology for
human machine interface (HMI), operations management, SCADA, and production and performance
management.
System Platform contains an integrated set of services and an extensible data model to manage plant
control and information management systems. System Platform supports both the supervisory control
layer and the manufacturing execution system (MES) layer, presenting them as a single information
source.
Modular applications sit on top of System Platform. Other third-party integrators are delivering a
growing inventory of application components that use System Platform services.

Confidential Property of Schneider Electric | Page 337

Internal
 Wonderware System Platform
System Platform Functional Components:
The following figure shows a functional representation of System Platform, which incorporates the
ArchestrA framework.
The ArchestrA Framework consists of server-side configuration- and deployment related components.
In System Platform, these components include a centralized
object repository called Galaxy Repository, an integrated development environment, and a database
to store historical data.

Confidential Property of Schneider Electric | Page 338

Internal
 Wonderware System Platform

Confidential Property of Schneider Electric | Page 339

Internal
 Wonderware System Platform
➢ Development Studio
Development Studio is your development environment to build applications. The Development Studio
consists of the ArchestrA Integrated Development Environment (IDE) and InTouch WindowMaker.
Both components include graphic tools, an extensive set of industrial symbols, and program functions
that can be included in application scripts.
➢ Visualization and Analysis Clients
Visualization and analysis clients enable you to visualize real-time and historical data from System
Platform.
InTouch HMI visualization clients show Human Machine Interface (HMI) applications.

Confidential Property of Schneider Electric | Page 340

Internal
 Wonderware System Platform
Development Environment
The ArchestrA IDE and InTouch HMI WindowMaker are typically installed on the same computer. The
ArchestrA IDE is the Integrated Development Environment provided with
System Platform. You use the ArchestrA IDE to build your InTouch OMI ViewApps and InTouch HMI
managed applications.
The IDE includes a set of editors to create and manage:
➢ Graphics
➢ Screen Profiles
➢ Layouts
➢ ViewApps
➢ Objects
➢ ViewApp Namespaces
➢ External Content
Confidential Property of Schneider Electric | Page 341
Internal
 Wonderware System Platform

Confidential Property of Schneider Electric | Page 342

Internal
 Start the ArchestrA IDE
You start the ArchestrA IDE by selecting the System Platform IDE icon from the Windows Apps
window.
1. Click the Apps icon on the Windows Start window to show the Apps window.
2. Locate the System Platform app group.
3. Click the System Platform IDE icon.
The Connect to Galaxy dialog box appears without a Galaxy name the first time it is opened.

Confidential Property of Schneider Electric | Page 343

Internal
 Start the ArchestrA IDE
➢ You must create a Galaxy before starting the ArchestrA IDE for the first time.
➢ Your Wonderware product licenses must be activated before starting the ArchestrA IDE
➢ Users must be a member of the OS group aaConfigTools to connect to a Galaxy from the IDE.
Assign users to this group through the Local Users and Groups utility of the Windows Control
Panel.

Confidential Property of Schneider Electric | Page 344

Internal
 Create a Galaxy
A Galaxy represents your entire production environment, including all computers and components that
run your application. A Galaxy is a collection of graphics, objects, engines, templates, and attributes
you define as a set of component parts of an InTouch HMI or OMI application.
Start the ArchestrA IDE. The Connect to Galaxy dialog box appears.

2. Click New Galaxy. The New Galaxy dialog box appears.

Confidential Property of Schneider Electric | Page 345

Internal
 Create a Galaxy

Confidential Property of Schneider Electric | Page 346

Internal
 Create a Galaxy
3. Complete the fields of the New Galaxy dialog box.
➢ The Wonderware System Platform places the Galaxy Repository on the computer that serves as
the Wonderware Development Studio. If you want, type the node name of the computer that hosts
your Galaxy Repository (GR) in the GR node name field.
➢ Type the name of the Galaxy that you are creating in the Galaxy name field.
➢ Select Default.cab as the type of Galaxy from the drop-down list of the Galaxy type box.
4. Click Create. The New Galaxy dialog box shows the progress of creating a new Galaxy.
5. Click Close after the new Galaxy is created.
6. Click Connect to open the ArchestrA IDE and show the Galaxy you created.

Confidential Property of Schneider Electric | Page 347

Internal
 Create a Galaxy

Confidential Property of Schneider Electric | Page 348

Internal
 Create a Galaxy
➢ Each ArchestrA IDE session requires a connection to a specified Galaxy.
➢ While you are building an InTouch OMI ViewApp or an InTouch HMI managed application, information
is stored in a database and file structure called the Galaxy Repository.
➢ You can delete a Galaxy from the Connect to Galaxy dialog box. or switch to another Galaxy by
selecting the Change Galaxy button on the menu bar of the ArchestrA IDE.

Confidential Property of Schneider Electric | Page 349

Internal
 Wonderware System Platform
The following figure summarizes the major workflows to create reusable standards you need to build
ViewApps. As shown in the figure, the ArchestrA IDE includes a set of editors to build
reusable symbols, objects, scripts, layouts, and screen profiles.

Confidential Property of Schneider Electric | Page 350

Internal
 Wonderware System Platform
System Platform provides a set of graphic tools and symbols to visualize data in a ViewApp. You can use
these tools within the Symbol Editor to create symbols from basic graphic elements, like rectangles, lines,
and text.
Standard ArchestrA symbols available from the Graphic Toolbox show reasonably realistic views of
process objects. You can embed an ArchestrA symbol in a template or instance of an object to visualize
object-specific information.

Situational Awareness Library symbols are protected symbols that include multiple visual and functional
configurations, which are enabled by selecting values from a set of Wizard Options associated with each
symbol. Incorporating multiple configurations in a single symbol reduces the types of symbols you need to
develop for an application.

Confidential Property of Schneider Electric | Page 351

Internal
 Wonderware System Platform
You can create a symbol in the Graphic Toolbox by the following methods:
➢ Keyboard shortcut: Press Ctrl + Shift + S
➢ Shortcut menu: Right-click on the Galaxy name, select New, and then select Symbol
➢ Galaxy Menu: Select Galaxy from the menu bar, select the New option, and then select Symbol from
the sub menu
You should see the symbol listed in the Graphic Toolbox as Symbol_001 with a blue background. The
symbol is selected and you can assign a new name by typing over the default name.

Confidential Property of Schneider Electric | Page 352

Internal
 Wonderware System Platform
After you create a symbol, you need to check it out to be able to edit it in the Symbol Editor. You also need
to check in the symbol after you are finished editing it.
Situational Awareness Library symbols are protected templates and cannot be directly edited. You must
embed an instance of a Situational Awareness Library symbol in another symbol to edit it and make
configuration changes.
1. Right-click on your symbol listed in the Graphic Toolbox and select Check Out.
A red check mark appears to the left of your symbol’s name to indicate that it is checked out.
2. Right-click on the checked-out symbol and select Open to show the symbol in the Graphic Editor.
3. After you have finished editing the symbol, click Save and Close from the task bar of the Graphic Editor.
4. Right-click on the symbol name shown in the Graphic Toolbox and select Check In.

Confidential Property of Schneider Electric | Page 353

Internal
 Wonderware System Platform
You can assemble and edit a set of graphic elements in the Symbol Editor to represent a visual
component of your ViewApp.

Confidential Property of Schneider Electric | Page 354

Internal
Wonderware –Start Windowmaker

Confidential Property of Schneider Electric | Page 355

Internal
 Starting WindowMaker from the ArchestrA IDE
You can edit a managed InTouch application by starting WindowMaker from within the ArchestrA IDE.
You can start WindowMaker from an InTouchViewApp template or an instance.
When opening a managed InTouch application created with a different screen resolution than your
current system resolution, a message appears.

Confidential Property of Schneider Electric | Page 356

Internal
 Start WindowMaker from the ArchestrA IDE
To start WindowMaker from an InTouchViewApp template
1. Open the ArchestrA IDE.
2. Locate the InTouchViewApp template that includes the managed InTouch application you want to modify.
3. Double-click the InTouchViewApp template. WindowMaker starts as the object’s default editor and opens
the InTouch application. You are ready to edit the managed application.
To start WindowMaker from an InTouchViewApp instance
1. Open the ArchestrA IDE.
2. Locate the InTouchViewApp object whose parent hosts managed InTouch application you want to modify.
3. Double-click the InTouchViewApp object. The InTouchViewApp Instance Edit dialog box appears.

Confidential Property of Schneider Electric | Page 357

Internal
Wonderware –Configuring of User Security Access

Confidential Property of Schneider Electric | Page 358

Internal
 Configuring of User Security Access
1. On the WindowMaker Special menu, point to Security, and then click Log On.
2. Log on with your InTouch administrator account.
3. On the Special menu, point to Security, then click Configure Users. The Configure Users dialog box
appears.
4. To add a security account, do the following:
a. In the User Name box, type the name that you want to assign to the operator.
b. In the Password box, type an operator password up to a maximum of 29 characters.
c. In the Access Level box, type the operator’s access level (lowest = 0 to highest = 9999).
d. Click Add to add the user name to the InTouch security list.
5. To change a user name, select the name, make any changes, and then click Update.
6. To delete a user name, select the name and then click Delete.
7. Click OK.

Confidential Property of Schneider Electric | Page 359

Internal
 Configuring of User Security Access

Confidential Property of Schneider Electric | Page 360

Internal
Wonderware –Tags Management

Confidential Property of Schneider Electric | Page 361

Internal
 Creating New Tags
You create tags with the WindowMaker Tagname Dictionary. Before you start, analyze your plant process to
determine the tags that you need to create in your InTouch application.
1. Open the InTouch application in WindowMaker.
2. On the Special menu, click Tagname Dictionary.
3. Do the following:
a. Click New. The Tagname box clears.
b. Enter a name for the new tag. For more information about tag naming requirements, see Tag Name
Conventions.
c. Optionally, type a comment about the new tag in the Comment box.
4. Click Type. The Tag Types dialog box appears with a list of supported InTouch tag types.

Confidential Property of Schneider Electric | Page 362

Internal
 TMC Naming Convention
A summary of the field device and signal tag prefix convention is included for reference.
All I/O are in a general format of “x#_AAAA”, where:
“x” is a lower case prefix, which refers to the I/O’s signal type
“#” is an abbreviation prefix, which represents to the ITCC system name
1 for 10-C/CT-2200 Cracked Gas Compressor (CGC)
2 for 10-C/CT-2800 Propylene Ref. Compressor (PRC)
3 for 10-C/CT-2850 Ethylene Ref. Compressor (ERC)
“AAAAA” refer to the I/O’s Tagname

Confidential Property of Schneider Electric | Page 363

Internal
 TMC Naming Convention

Confidential Property of Schneider Electric | Page 364

Internal
 TMC Naming Convention

Confidential Property of Schneider Electric | Page 365

Internal
 Access name (DDE setting)
Setting Up Access Names
You must associate InTouch I/O tags or remote tag references with an Access Name. An Access Name
defines a communication link with another I/O data source. Each Access Name specifies an I/O address
consisting of a node name, an application name, and a topic.
InTouchView shows the visual interface of HMI applications designed specifically for use in an ArchestrA
Application Server environment. InTouchView applications run as a client with Application Server acting
as a server that provides most HMI functionality.
InTouchView applications offer only some of the standard functions available from full-featured
InTouchapplications.

Confidential Property of Schneider Electric | Page 366

Internal
 Access name (DDE setting)
To create an Access Name
1. On the Special menu, click Access Names. The Access Names dialog box appears.
2. Click Add. The Add Access Name dialog box appears.
3. Set the properties of the Add Access Name dialog box. Do the following:
a. In the Access box, type a name that identifies this Access Name.
b. If the data resides on a network I/O Server, type the remote server’s node name in the Node
Name box.
c. In the Application Name box, type the actual program name of the I/O Server programfrom which
data will be acquired.
If the I/O data source is a DAServer, type the name of the DAServer program, do not include the .exe file
name extension of the program.

Confidential Property of Schneider Electric | Page 367

Internal
 Access name (DDE setting)

Confidential Property of Schneider Electric | Page 368

Internal
 Tagname Editor - Create a New Tag
To create a new tag
1. Open the InTouch application in WindowMaker.
2. On the Special menu, click Tagname Dictionary.
The first time you open the Tagname Dictionary, the definition for the $AccessLevel system tag
appears in the Tagname box. After saving a new tag, the Tagname Dictionary shows the most recently
saved tag definition.
3. Do the following:
a. Click New. The Tagname box clears.
b. Enter a name for the new tag. For tag naming requirements, see Tag Name Conventions.
c. Optionally, type a comment about the new tag in the Comment box.
4. Click Type. The Tag Types dialog box appears with a list of supported InTouch tag types.

Confidential Property of Schneider Electric | Page 369

Internal
 Tagname Editor
5. Select a type of tag from the list and click OK. The Tagname Dictionary reappears and shows the type
of tag you selected.
6. If needed, click Details to see the additional Tagname Dictionary options for the selected tag type.
7. Specify further tag options in the Tagname Dictionary dialog box.

Confidential Property of Schneider Electric | Page 370

Internal
 Tagname Editor

Confidential Property of Schneider Electric | Page 371

Internal
 Tagname Editor - Creating Discrete Tags
Creating Discrete Tags
You can specify discrete tags to show the binary state of internal processes running in an InTouch
application. A discrete tag must be assigned an initial value of on or off. Also, you can specify messages
that appear in the alarm event window when the process associated with the tag transitions into or out of
an alarm state.
The following steps show how to define a memory discrete tag. I/O discrete tags indicate the binary state
of all inputs and outputs from programmable controllers, process computers, and data from network
nodes.

Confidential Property of Schneider Electric | Page 372

Internal
 Tagname Editor

Confidential Property of Schneider Electric | Page 373

Internal
 Tagname Editor - Memory Tag Values
To define memory integer and real tag values
1. Assign memory integer or memory real as the type of tag in the Tag Types dialog box. The detail
portion of the Tagname Dictionary dialog box appears.
2. Set the properties for integer and real tags. Do the following:
a. In the Initial Value box, type the integer or real number associated with the tag when the
application starts.
b. In the Min Value box, type the minimum integer or real number for the tag.
c. The Min Value sets the minimum possible value for numbers associated with memory integer
and real tags.
d. In the Max Value box, type the maximum integer or real number for the tag.
e. The Max Value sets the maximum possible value for numbers associated with memory integer
and real tags.
f. In the Eng Units box, type the label you want to use for the tag's engineering units.
3. Save your changes to the tag.
Confidential Property of Schneider Electric | Page 374
Internal
 Tagname Editor

Confidential Property of Schneider Electric | Page 375

Internal
 Tagname Editor - Exporting Tag
Exporting Tag Definitions
The figure below shows the steps to export and import tag definitions between an interim export file and
an application’s Tagname Dictionary.
You use the DBDump utility within the Application Manager to export the contents of the Tagname
Dictionary to a Comma Separated Value (CSV) file. You can view and edit the exported file with Microsoft
Notepad or Microsoft Excel. After making edits, you then import the tag definitions to an InTouch
application with the DBLoad utility, which is also an Application Manager utility.
You must convert an application to the current version of the InTouch HMI software before you can export
the tag definitions.

Confidential Property of Schneider Electric | Page 376

Internal
 Tagname Editor

Confidential Property of Schneider Electric | Page 377

Internal
 Tagname Editor - Export Tagname
You use the DBDump utility within the Application Manager to export the contents of the Tagname
Dictionary to a Comma Separated Value (CSV) file. You can view and edit the exported file with Microsoft
Notepad or Microsoft Excel. After making edits, you then import the tag definitions to an InTouch
application with the DBLoad utility, which is also an Application Manager utility.
You must convert an application to the current version of the InTouch HMI software before you can
export the tag definitions.
To export tag definitions
1. Close WindowMaker and WindowViewer.
2. Start Application Manager. The Application Manager dialog box shows a list of InTouch applications.
3. Select the application from the list.
4. Click the DBDump icon. The CSV File to Dump To: dialog box appears.

Confidential Property of Schneider Electric | Page 378

Internal
 Tagname Editor – Delete Unused Tags
To delete multiple unused tags
1. Close WindowViewer if it is running.
2. Open an InTouch application in WindowMaker.
3. On the Special menu, click Delete Unused Tags.
The Delete Unused Tags dialog box appears with a list of unused tags.
The status bar at the bottom of the dialog box lists the Number of records, Number of Local tags,Number
of selected tags, Total number of tags and the Tag license count.

Confidential Property of Schneider Electric | Page 379

Internal
 Tagname Editor – Delete Unused Tags
4. Use the filter ( ) option to refine the list of unused tags. Select the filter option and enter a search term.
The tags matching the criteria are displayed.
5. Click the column headings to sort the columns.

Confidential Property of Schneider Electric | Page 380

Internal
 Tagname Editor – Delete Unused Tags
6. Select the tags you want to delete. To select all tags for the current filter criteria, click Select All.
7. Click Clear, to clear the tag selection for the current filter.
8. Click the Include all graphics from Graphic Toolbox checkbox to only see tags that are not used in any
graphics or windows. These tags are safe to delete as they are not referenced in graphics or windows
that contains graphics.
For example: 10 tags are configured in the tag dictionary, 4 are referenced in graphics in the
graphic toolbox (but not embedded on any windows), 4 tags are referenced on graphics placed on
windows. By default, 6 tags (2 unused tags + 4 tags from the graphics in the graphic toolbox not
embedded on any window) will be displayed. If the checkbox is selected, then only the 2 unused tags are
displayed.
9. Click Delete, to delete all tag selections independent of the filter criteria.
A confirmation message appears. The message will specify the number of tags that will be deleted.
10. Click OK to confirm.

Confidential Property of Schneider Electric | Page 381

Internal
Wonderware –Basic TMC Toolbar Introduction

Confidential Property of Schneider Electric | Page 382

Internal
 TMC Toolbar Summary

Confidential Property of Schneider Electric | Page 383

Internal
Wonderware –Basic Animation Link

Confidential Property of Schneider Electric | Page 384

Internal
 Basic animation link
Creating Value Displays
Use a value display text object to show the value of a tag. This lets you show things like fill levels, on/off
status, or alarm messages.
You can use up to 1023 characters in an expression. If you need a larger expression, create a
QuickFunction and call it in your expression.
Messages appear in the location of the original text object using the font, size, color, alignment, and
linked attributes set for that object. The original contents of the field have no effect on the message at run
time.

Confidential Property of Schneider Electric | Page 385

Internal
 Basic animation link
To create a discrete value display link
1. Right-click the text object and click Animation Links. The Animation Links dialog box appears.
2. In the Value Display area, click Discrete. The Output -> Discrete Expression dialog box appears.
3. In the Expression box, type the name of a discrete tag or an expression that equates to a discrete
value. For example: Cooling_Pump
4. In the On Message box, type the message to appear when the value of the expression equals 1, true,
on, or yes. For example: Pump is ON
5. In the Off Message box, type the message to appear when the value of the expression equals 0, false,
off, or no. For example: Pump is OFF
6. Click OK.

Confidential Property of Schneider Electric | Page 386

Internal
 Basic animation link
To create an analog value display link
1. Right-click the text object and click Animation Links. The Animation Links dialog box appears.
2. In the Value Display area, click Analog. The Output -> Analog Expression dialog box appears.
3. In the Expression box, type an analog (integer or real) tagname or an expression that equates to an
analog value. For example: Tank_CV*0.06
4. In the Formatting area, in the list, click each data type for which you want to configure run time
advanced formatting. The Fixed Width check box, Precision box, and Bits From and To boxes become
available based on the data type you select. For information on configuring these options,
5. Click OK.

Confidential Property of Schneider Electric | Page 387

Internal
 Basic animation link
To create a string value display link
1. Right-click the text object and click Animation Links. The Animation Links dialog box appears.
2. In the Value Display area, click String. The Output -> String Expression dialog box appears.
3. In the Expression box, type the name of a message tag or an expression that uses a message tag.
For example:
"The Tank Level is:" + Text(TankLevel,"#")
4. Click OK.

Confidential Property of Schneider Electric | Page 388

Internal
 Basic animation link
Enabling Visibility
You can create links to hide objects based on the values of various tags by using visibility links. Using
visibility links, you can:
➢ Create the impression that moving objects only move in one direction, by hiding them when they
move in the wrong direction.
➢ Create the impression that a moving object has stopped.
➢ Cause an object such as an alarm or error message to become visible only when it is activated.

Confidential Property of Schneider Electric | Page 389

Internal
 Basic animation link
To create a visibility link
1. Right-click the object and then select Animation Links. The Animation Links dialog box appears.
2. In the Miscellaneous area, click Visibility. The Object Visibility -> Discrete Value dialog box
appears.
3. In the Expression box, type the name of a discrete tag or an expression that equates to a discrete
value.
4. Select the Visible State for the object. If you select Off, the object is invisible when the value of the
expression is true. If you select On, the object is visible when the value of the expression is true.
5. Click OK.

Confidential Property of Schneider Electric | Page 390

Internal
Wonderware –Basic ArchestrA Graphic Import and Linking

Confidential Property of Schneider Electric | Page 391

Internal
 Basic ArchestrA Graphic Import and Linking
Importing Windows
Importing windows from an existing InTouch application into your current application allows you to reduce
development time because you can reuse your previously created windows, objects, and window scripts.
You must convert an application to the current version of the InTouch HMI software before you can
import windows.
When you import windows containing SmartSymbols and select to use existing tags, the InTouch HMI
still keeps placeholders for the recovered symbols, even though the tags are available in the target
application.
When you import a window from an application that contains SuperTags, only the SuperTag instances
actually used in the window are imported into the new application.

Confidential Property of Schneider Electric | Page 392

Internal
 Basic ArchestrA Graphic Import and Linking
To import a window
1. Close all windows in your current application.
2. On the File menu, click Import, and then click Windows and Scripts. The Import from directory dialog
box appears.
3. Select the folder for the application containing the windows to import.
4. Click OK. The Application Data Import Options dialog box appears.

Confidential Property of Schneider Electric | Page 393

Internal
 Basic ArchestrA Graphic Import and Linking

Confidential Property of Schneider Electric | Page 394

Internal
Wonderware –Alarm Viewers, Trending Configuration,
Alarm printer

Confidential Property of Schneider Electric | Page 395

Internal
 Alarm Viewers
Selecting the Alarms to Display
The Alarm Viewer control can show summaries of active alarms or listings of historical alarms.
To set general alarm query properties
1. Right-click the Alarm Viewer control and then click Properties. The AlarmViewerCtrl Properties dialog
box appears.
2. Click the General tab.
3. Select the Perform Query on Startup check box to automatically update the Alarm Viewer control using
default query properties when the application starts.
4. Select the Show Message check box to show a default message when there are no alarms. In the text
box, type the message to show.
5. Click Apply.

Confidential Property of Schneider Electric | Page 396

Internal
 Alarm Viewers
To configure the query default
1. Right-click the Alarm Viewer control and then click Properties. The AlarmViewerCtrl Properties dialog
box appears.
2. Click the Query tab.
3. In the From Priority box, type the minimum alarm priority value (1 to 999).
4. In the To Priority box, type the maximum alarm priority value (1 to 999).
5. Click the Query Type arrow and select either Historical or Summary as the default run-time alarm
display.
The default type of display can be changed during run time by running a QuickScript containing a
query function. For example, if the script includes the ApplyQuery() method with its Type
parameter set to “Summary,” then the grid shows a summary of current alarms. Conversely, if the
same grid has an ApplyQuery() method run against it with the Type parameter set to "Historical", it shows
historical alarms. The QueryType property reflects the current state of the alarm display.

Confidential Property of Schneider Electric | Page 397

Internal
 Alarm Viewers
6. In the Alarm Query box, type a valid alarm query. For example, type \InTouch!$System to query
for all alarms that belong to the default $System alarm group.
7. Click OK

Confidential Property of Schneider Electric | Page 398

Internal
 Alarm Viewers

Confidential Property of Schneider Electric | Page 399

Internal
 Alarm Viewers
The following describe the different priorities set in HMI application for alarm, trip and firstout trip

Confidential Property of Schneider Electric | Page 400

Internal
 Trending Configuration
Configuring Real-time Trend Display Options
To configure real-time trend display options
1. Run the Application windowsviewer
2. Double-click on the Hist trend object. The Real Time Trend Configuration dialog box appears.
3. In the Pen Configure Screen, select Pen 1, Pen 2…Pen 8 . Do any of the following:
a. Click ok to open the Tagname. Select the Tagname variable for the trend.
b. Click Ok to confirm the variable for the pen,
c. The screen will change back to the Pen Configure Screen

Confidential Property of Schneider Electric | Page 401

Internal
 Trending Configuration

Confidential Property of Schneider Electric | Page 402

Internal
 Trending Configuration

Confidential Property of Schneider Electric | Page 403

Internal
 Trending Configuration

Confidential Property of Schneider Electric | Page 404

Internal
 Alarm printer
Configuring Which Alarms to Print
The Alarm Printer queries the alarm memory to select records to print or save to a log file. The query
selects records from the internal alarm memory based upon:
➢ Alarm priority
➢ Current alarm state (unacknowledged/acknowledged)
➢ Alarm group membership
Each alarm has an assigned priority number that represents the severity of the alarm. An alarm priority
ranges from 1 to 999. The most severe alarm is assigned a priority of 1. The least severe alarm is
assigned a priority of 999.
If a network or printer connection fails, the Alarm Printer does not reprint all alarms. The Alarm Printer
only prints the alarms that have not been printed before the connection failure.

Confidential Property of Schneider Electric | Page 405

Internal
 Alarm printer
To configure which alarms to print
1. Open the Alarm Printer utility. Do the following:
a. In the WindowMaker Tools view, expand Applications.
b. Double-click Alarm Printer.
2. On the menu bar, click Configure. The Configuration Settings dialog box appears.
3. Click the Query tab.

Confidential Property of Schneider Electric | Page 406

Internal
Wonderware –Importing and Exporting Windows, Back up,
Publishing and Start Windowviewer

Confidential Property of Schneider Electric | Page 407

Internal
 Importing and Exporting Windows
To import a window
1. Close all windows in your current application.
2. On the File menu, click Import, and then click Windows and Scripts. The Import from directory dialog
box appears.
3. Select the folder for the application containing the windows to import.
4. Click OK. The Application Data Import Options dialog box appears.
5. Select the Windows check box and then click Select to select the individual windows to import.
6. Select the Use Existing Tags (Conserve Placeholders) check box if the tags associated with the
imported windows already exist in your application and you want to use them instead of
placeholders.
7. Click Import.

Confidential Property of Schneider Electric | Page 408

Internal
 Importing and Exporting Windows
8. Convert the placeholder tags to either local tags or remote tag references.
9. If an imported window contains one or more wizards, double-click on each wizard to open its
properties panel.
If an imported window contains one or more SmartSymbols, edit each SmartSymbol and create new
instances.

Confidential Property of Schneider Electric | Page 409

Internal
 Importing and Exporting Windows

Confidential Property of Schneider Electric | Page 410

Internal
 Importing and Exporting Windows
To export a window
1. Close all windows in your current application.
2. On the File menu, click Export, and then click Windows. The Export to directory dialog box appears.
3. Select the folder of the application to which to export the windows.
4. Click OK. The Windows to Export dialog box appears.

Confidential Property of Schneider Electric | Page 411

Internal
 Importing and Exporting Windows

5. Select the windows to export.

6. Click OK.
If a problem occurs, the Problem with Export Operation dialog box appears. Click the option for the
action you want to take and then click OK.

Confidential Property of Schneider Electric | Page 412

Internal
 Backup Windows
To Backup (object or all object)
1. In the Archestra, select Export All object to backup the application.
2. On the Galaxy menu, click Export and then click All Objects.
3. In the Export dialog box, browse to a path and type a name for the exported file.
4. Click Save. The file is saved with the specified name and an .aaPKG extension.
5. When the export is complete, click Close. Now you can import the .aaPKG file into another existing
Galaxy.

Confidential Property of Schneider Electric | Page 413

Internal
 Publish Application
Publishing Managed InTouch Applications
You can publish a managed InTouch application using the ArchestrA IDE. As part of this process, you
can create a compressed, self-extracting package file that contains all relevant files and set-up
procedures to install an InTouch application on another computer.

Confidential Property of Schneider Electric | Page 414

Internal
 Publish Application

Confidential Property of Schneider Electric | Page 415

Internal
 Publish Application
Select the folder of publish

Confidential Property of Schneider Electric | Page 416

Internal
 Start Windowviewer
1. Copy the application published (refer to the previous slide) to the workstation with runtime license.
2. Open Intouch Application manager and Import the application
3. Save the application manager.
4. Click Windowviewer from Start button of windows ,system can start the Windowviewer

Confidential Property of Schneider Electric | Page 417

Internal