Procedure Control Library

User Manual

EIO0000004853.02
04/2023

www.se.com
Legal Information
The Schneider Electric brand and any trademarks of Schneider Electric SE and its
subsidiaries referred to in this guide are the property of Schneider Electric SE or its
subsidiaries. All other brands may be trademarks of their respective owners.
This guide and its content are protected under applicable copyright laws and
furnished for informational use only. No part of this guide may be reproduced or
transmitted in any form or by any means (electronic, mechanical, photocopying,
recording, or otherwise), for any purpose, without the prior written permission of
Schneider Electric.
Schneider Electric does not grant any right or license for commercial use of the guide
or its content, except for a non-exclusive and personal license to consult it on an "as
is" basis. Schneider Electric products and equipment should be installed, operated,
serviced, and maintained only by qualified personnel.
As standards, specifications, and designs change from time to time, information
contained in this guide may be subject to change without notice.
To the extent permitted by applicable law, no responsibility or liability is assumed by
Schneider Electric and its subsidiaries for any errors or omissions in the informational
content of this material or consequences arising out of or resulting from the use of the
information contained herein.
Table of Contents
Safety Information ......................................................................................5
Before You Begin ..................................................................................5
Start-up and Test ..................................................................................6
Operation and Adjustments ...................................................................7
About the Book...........................................................................................8
Introduction ..................................................................................................9
Overview .................................................................................................10
List of Components .............................................................................10
Function Description ................................................................................. 11
Status and Commands..............................................................................12
Flow Diagram...........................................................................................14
Operating Modes......................................................................................16
Normal Phase.....................................................................................16
Exception Phase.................................................................................17
Exception Handling...................................................................................18
Strategy and Parameter Configuration .......................................................19
Initialization of Application .........................................................................20
HMI Compatibility .....................................................................................21
Phase Object .............................................................................................22
PhaseManager.........................................................................................23
Control ...............................................................................................23
Interface Representation ...............................................................23
Inputs...........................................................................................24
Outputs ........................................................................................24
Sequence .....................................................................................26
Offline Parametrization ..................................................................27
OPCUA ........................................................................................27
Supervision (EcoStruxure Automation Expert).......................................30
Symbols .......................................................................................30
Faceplate .....................................................................................33
Alarms..........................................................................................38
Supervision (Aveva System Platform)...................................................39
Supervision Functions ...................................................................39
Control/Supervision Relationship....................................................39
Parameters...................................................................................42
Symbols .......................................................................................47
Faceplate .....................................................................................48
Example of Use - PhaseManager...............................................................53
Configuration with Sequence Objects ...................................................54
Integration with AVEVA Batch Management ..........................................57
Customization ..........................................................................................64
Supporting Objects ...................................................................................69
Basics .....................................................................................................70
decodePhaseState .............................................................................70
Interface Representation ...............................................................70
Inputs...........................................................................................71
Outputs ........................................................................................71
encodePhasePara ..............................................................................72

EIO0000004853.02 3
 Interface Representation ...............................................................73
Inputs...........................................................................................73
Outputs ........................................................................................74
encodeProcedureState .......................................................................74
Interface Representation ...............................................................74
Inputs...........................................................................................75
Outputs ........................................................................................76
phaseExceptionHandling.....................................................................77
Interface Representation ...............................................................77
Inputs...........................................................................................78
Outputs ........................................................................................79
S88StateControl .................................................................................80
Interface Representation ...............................................................80
Inputs...........................................................................................81
Outputs ........................................................................................82
Composites..............................................................................................84
phaseCommandSel ............................................................................84
Interface Representation ...............................................................84
Inputs...........................................................................................85
Outputs ........................................................................................87
seqConnect........................................................................................88
Interface Representation ...............................................................88
Outputs ........................................................................................88
stateManager .....................................................................................88
Interface Representation ...............................................................89
Inputs...........................................................................................89
Outputs ........................................................................................90
Adapters ..................................................................................................92
IPhase ...............................................................................................92
Interface Representation ...............................................................92
Inputs...........................................................................................92
Outputs ........................................................................................93
Composite Automation Types ....................................................................95
PhaseInterface ...................................................................................95
Interface Representation ...............................................................95
Outputs ........................................................................................95
Offline Parametrization ..................................................................96
OPCUA ........................................................................................96
PhaseRealParam ...............................................................................98
Interface Representation ...............................................................99
Inputs...........................................................................................99
Outputs ...................................................................................... 100
Offline Parametrization ................................................................ 100
OPCUA ...................................................................................... 100

4 EIO0000004853.02
Safety Information

Safety Information
Important Information
Read these instructions carefully, and look at the equipment to become familiar
with the device before trying to install, operate, service, or maintain it. The
following special messages may appear throughout this documentation or on the
equipment to warn of potential hazards or to call attention to information that
clarifies or simplifies a procedure.

The addition of this symbol to a “Danger” or “Warning” safety label indicates that an
electrical hazard exists which will result in personal injury if the instructions are not
followed.

This is the safety alert symbol. It is used to alert you to potential personal injury
hazards. Obey all safety messages that follow this symbol to avoid possible injury or
death.

! DANGER
DANGER indicates a hazardous situation which, if not avoided, will result in death or serious
injury.

! WARNING
WARNING indicates a hazardous situation which, if not avoided, could result in death or
serious injury.

! CAUTION
CAUTION indicates a hazardous situation which, if not avoided, could result in minor or
moderate injury.

NOTICE
NOTICE is used to address practices not related to physical injury.

Please Note
Electrical equipment should be installed, operated, serviced, and maintained only
by qualified personnel. No responsibility is assumed by Schneider Electric for any
consequences arising out of the use of this material.
A qualified person is one who has skills and knowledge related to the construction
and operation of electrical equipment and its installation, and has received safety
training to recognize and avoid the hazards involved.

Before You Begin

Do not use this product on machinery lacking effective point-of-operation
guarding. Lack of effective point-of-operation guarding on a machine can result in
serious injury to the operator of that machine.

EIO0000004853.02 5
 Safety Information

WARNING
UNGUARDED EQUIPMENT
• Do not use this software and related automation equipment on equipment
which does not have point-of-operation protection.
• Do not reach into machinery during operation.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.

This automation equipment and related software is used to control a variety of

industrial processes. The type or model of automation equipment suitable for each
application will vary depending on factors such as the control function required,
degree of protection required, production methods, unusual conditions,
government regulations, etc. In some applications, more than one processor may
be required, as when backup redundancy is needed.
Only you, the user, machine builder or system integrator can be aware of all the
conditions and factors present during setup, operation, and maintenance of the
machine and, therefore, can determine the automation equipment and the related
safeties and interlocks which can be properly used. When selecting automation
and control equipment and related software for a particular application, you should
refer to the applicable local and national standards and regulations. The National
Safety Council's Accident Prevention Manual (nationally recognized in the United
States of America) also provides much useful information.
In some applications, such as packaging machinery, additional operator protection
such as point-of-operation guarding must be provided. This is necessary if the
operator's hands and other parts of the body are free to enter the pinch points or
other hazardous areas and serious injury can occur. Software products alone
cannot protect an operator from injury. For this reason the software cannot be
substituted for or take the place of point-of-operation protection.
Ensure that appropriate safeties and mechanical/electrical interlocks related to
point-of-operation protection have been installed and are operational before
placing the equipment into service. All interlocks and safeties related to point-of-
operation protection must be coordinated with the related automation equipment
and software programming.
NOTE: Coordination of safeties and mechanical/electrical interlocks for point-
of-operation protection is outside the scope of the Function Block Library,
System User Guide, or other implementation referenced in this
documentation.

Start-up and Test

Before using electrical control and automation equipment for regular operation
after installation, the system should be given a start-up test by qualified personnel
to verify correct operation of the equipment. It is important that arrangements for
such a check are made and that enough time is allowed to perform complete and
satisfactory testing.

WARNING
EQUIPMENT OPERATION HAZARD
• Verify that all installation and set up procedures have been completed.
• Before operational tests are performed, remove all blocks or other temporary
holding means used for shipment from all component devices.
• Remove tools, meters, and debris from equipment.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.

6 EIO0000004853.02
Safety Information

Follow all start-up tests recommended in the equipment documentation. Store all
equipment documentation for future references.
Software testing must be done in both simulated and real environments.
Verify that the completed system is free from all short circuits and temporary
grounds that are not installed according to local regulations (according to the
National Electrical Code in the U.S.A, for instance). If high-potential voltage
testing is necessary, follow recommendations in equipment documentation to
prevent accidental equipment damage.
Before energizing equipment:
• Remove tools, meters, and debris from equipment.
• Close the equipment enclosure door.
• Remove all temporary grounds from incoming power lines.
• Perform all start-up tests recommended by the manufacturer.

Operation and Adjustments

The following precautions are from the NEMA Standards Publication ICS 7.1-
1995:
(In case of divergence or contradiction between any translation and the English
original, the original text in the English language will prevail.)
• Regardless of the care exercised in the design and manufacture of equipment
or in the selection and ratings of components, there are hazards that can be
encountered if such equipment is improperly operated.
• It is sometimes possible to misadjust the equipment and thus produce
unsatisfactory or unsafe operation. Always use the manufacturer’s
instructions as a guide for functional adjustments. Personnel who have
access to these adjustments should be familiar with the equipment
manufacturer’s instructions and the machinery used with the electrical
equipment.
• Only those operational adjustments required by the operator should be
accessible to the operator. Access to other controls should be restricted to
prevent unauthorized changes in operating characteristics.

EIO0000004853.02 7
 About the Book

About the Book

Document Scope
This document describes the functionality and features of the control services,
Supervision services of procedure library's CAT objects.
This document only covers the functional aspects of control and supervision
services when engineering a system with EcoStruxureTM Automation Expert, and
it describes the dynamic objects visible during runtime.
It does not cover any operational aspects, nor does it provide information on how
to use the Supervision services to monitor and operate the control system.
To use Composite Automation Type (CAT) objects, you has to be knowledgeable
of EcoStruxure Automation Expert.

Validity Note
This document has been updated with the release of the EcoStruxure Automation
Expert V23.1.

Product Related Information

The application of this library, which is referred to as the product, requires
expertise in the design and operation of control systems.

WARNING
UNINTENDED EQUIPMENT OPERATION
• Allow only authorized personnel with expertise in the design and operation of
control systems to program, install, alter, and apply this product.
• Follow local and national safety codes and standards.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.

The examples described in this manual is provided for information only.

WARNING
UNINTENDED EQUIPMENT OPERATION
Adapt examples that are given in this manual to the specific functions and
requirements of your industrial application before you implement them.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.

8 EIO0000004853.02
Introduction
What’s in This Part
Overview .......................................................................................................10
Function Description....................................................................................... 11
Status and Commands ...................................................................................12
Flow Diagram.................................................................................................14
Operating Modes ...........................................................................................16
Exception Handling ........................................................................................18
Strategy and Parameter Configuration .............................................................19
Initialization of Application...............................................................................20
HMI Compatibility ...........................................................................................21

EIO0000004853.02 9
 Overview

Overview
What’s in This Chapter
List of Components .......................................................................................10

This document describes the operation of the function blocks that are available for
procedure control. These function blocks are included in the SE.AppProcedure
library and is used to monitor and manage control sequences.

List of Components
List of Functional Module
The following functional module object is described in this document:

Family Functional module name Description

Functional PhaseManager Phase Manager (see, page 23)

Module

List of Supporting Objects

The following table gives the list of supporting objects used in this document:

Object Name Description

Basics decodePhaseState Decode Phase State (see, page 70)

encodePhasePara Encode Phase Para (see, page 72)

encodeProcedureState Encode Procedure State (see, page 74)

phaseExceptionHandling Phase Exception Handling (see, page 77)

S88StateControl S88 State Control (see, page 80)

Composites phaseCommandSel Phase Command Select (see, page 84)

seqConnect Sequence Connect (see, page 88)

stateManager State Manager (see, page 88)

Adaptors IPhase IPhase (see, page 92)

Composite PhaseInterface PhaseInterface (see, page 95)

Automation
Types PhaseRealParam PhaseRealParam (see, page 98)

10 EIO0000004853.02
Function Description

Function Description
The PhaseManager and related function blocks are used to monitor and manage
phases and their associated sequences that are available in a process. This
library works in coordination with sequence control blocks from SE.AppSequence
library, thus the operation here is based on the ISA-S88 Standard, Part 1 (S88.01i)
and implements the status controller defined in this standard for controlling
procedure model components (phases, operations, and so on).
As per the process requirements, user can configure different process phases
with their sequences applicable as mentioned in ISA-S88 Standard, Part 1
(S88.01i) such as, Running, Holding & Restarting, Stopping, and Aborting.
The following table explains the functions that are available in SE.AppProcedure
library:

S.No. Function
1 Designed to control different states in a phase such as Idle, Running, Holding,
Held, Restarting, Pausing, Paused, Stopping, Stopped, Aborting, Aborted,
and Complete.

2 Accepts status and delivers appropriate commands to sequence blocks of SE.

AppSequence library.

3 Owner management, the PhaseManager can be controlled through external

entities such as Aveva InBatch or similar in Program Local Owner. While in
Operator Owner, it can be controlled via supervision subsystems.
NOTE: Owner change is not allowed when the PhaseManager is
operational.

4 Mode Management, normal operation i.e. Running sequence (Auto, Semi-

Auto, or Manual modes).

5 Mode Management, for exception sequence such as Holding & Restarting,

Stopping or Aborting (Auto or Semi-Auto modes).

6 Configuration Error detection for incorrect configurations of PhaseManager.

7 Exception Handling, exception sequences will be executed axiomatically during

a failure detection.
8 Alarm Management, Generates alarms for any exceptions such as detected
failures or unsatisfied initial conditions.
9 16 built-in user defined Strategies available for phase handling.

10 15 input and 15 output user defined parameters (real data type) are available as a
default configuration. More parameters can be configured by customizing the
PhaseManager. Refer Customization, page 64.

EIO0000004853.02 11
 Status and Commands

Status and Commands

Status
The following table describes the available phase status:

Phase Status/ Integer value Description

State
Idle (Config 0 Running sequence is not configured with the
Error) PhaseManager. No operations are possible.

Idle 1 The PhaseManager is waiting for a START command

which causes a transition to the Running state.

Running 2 Normal operation

Held 3 The PhaseManager has completed its Holding

sequence and is brought to a known or planned state.
This state is usually used for a long-term stop. The
PhaseManager waits for a command to proceed further.

Stopped 4 The PhaseManager has completed its Stopping

sequence. The PhaseManager then waits for a RESET
command to make transition to Idle state.
Paused 5 Once the PhaseManager has paused at the user
defined stable step (Offline Parameterization), the state
changes from Pausing to Paused. This state is usually
used for short-term stops. A RESUME command causes
transition to the Running state which resumes the
normal operation immediately following the stable step
location.
Aborted 6 The PhaseManager has completed its Aborting
sequence. The PhaseManager waits for a RESET
command to make transition to Idle state.
Complete 7 The normal operation is completed. The PhaseManager
waits for a RESET command to make transition to Idle
state.
Holding 8 The PhaseManager receives a HOLD command and
executes its Holding sequence that puts the
PhaseManager into a known state (Held). If no Holding
sequence is detected, then the PhaseManager makes a
transition immediately to the Held state.

Restarting 9 The PhaseManager receives a RESTART command

while it is in the Held state. The PhaseManager
executes its Restart sequence to return to the Running
state. If no Restarting sequence is detected, then the
PhaseManager entity makes a transition immediately to
the Running state.

Pausing 10 The PhaseManager receives a PAUSE command which

causes the PhaseManager to stop at the next defined
stable step location in its normal running logic. Once
stopped, the state automatically makes a transitions to
Paused state.
Stopping 11 The PhaseManager receives a STOP command and
executes its Stopping sequence, which facilitates a
controlled normal stop. If no Stopping sequence is
detected, then the PhaseManager makes a transition
immediately to the Stopped state.

Aborting 12 The PhaseManager receives an ABORT command and

executes its Abort sequence that facilitates a quicker,
but not necessarily controlled, abnormal stop. If no
Aborting sequence is detected, then the
PhaseManager makes a transition immediately to the
Aborted state.
Interlocked 13 Initial conditions for PhaseManager are not satisfied. No
operations are possible.

12 EIO0000004853.02
Status and Commands

Commands
The following table describes the possible sequence status:

Commands Integer Value Description

START 1 This command orders the PhaseManager to begin the

execution of normal Running phase. This command is
only valid when the PhaseManager is in the Idle state.

HOLD 2 This command orders the PhaseManager to execute

the Holding phase. This command is valid when the
PhaseManager is in the Running, Pausing, Paused,
or Restarting state.

RESTART 4 This command orders the PhaseManager to execute

the Restarting phase to safely return to the Running
state. This command is only valid when the
PhaseManager is in the Held state.

STOP 8 This command orders the PhaseManager to execute

the Stopping phase. This command is valid when the
PhaseManager is in the Running, Pausing, Paused,
Holding, Held, or Restart state.
NOTE: IF Auto Reset (Offline Parameter) is
enabled in operator owner, state transition from
final transient states such as Complete, Stopped
or Aborted to Idle state happens automatically.
This functionality is not available for program
owner selection.
RESET 16 This command causes a transition to the Idle state. It
is valid from the Complete, Aborted, and Stopped
states.
PAUSE 32 This command orders the PhaseManager to pause at
the next configured stable step in its sequencing logic
and await a RESUME command before proceeding.
This command is only valid if the following conditions
are satisfied:
1. At least one step in the Running sequence
should be defined as a Stable Step (offline
parameterization).
2. PhaseManager is in Running state.

RESUME 64 This command orders the PhaseManager that is in

Paused state at a stable step as a result of a PAUSE
command to resume execution. This command is only
valid when the PhaseManager is in the Paused state.

ABORT 128 This command orders the PhaseManager to execute

the Aborting phase. The command is valid in every
state except for Idle, Completed, Aborting, and
Aborted.
SEMI — In Semi-Auto mode, this command is used for step
transitions confirmation from the user.

EIO0000004853.02 13
 Flow Diagram

Flow Diagram
State Diagram
The following diagram describes the possible phase statuses and phase
commands that the PhaseManager component manages according to the ISA-
S88 standard:

Next to the transition arrows, the phase commands that the component receives
(from the Supervision system or another higher-level phase) are shown in bold
uppercase fonts and status/commands that phase obtains from other blocks (for
example, use logic) are shown in parenthesis.

Transition Matrix
The following table describes the state transitions of the PhaseManager:

Command Start Stop Hold Restart Abort Reset Pause Resume

Initial No
state Com-
State Transition Matrix
mand
End State

Idle Running

Run-
Complete Stopping Holding Aborting Pausing
ning

Com-
plete Idle

Paus-
Paused Stopping Holding Aborting Running
ing

Paus- Stopping Holding Aborting Running

ed

Hold-
Held Stopping Aborting
ing

Held Stopping Restarting Aborting

Re-
start- Running Stopping Holding Aborting
ing

Stop-
Stopped Aborting
ping

Stop-
Aborting Idle
ped

14 EIO0000004853.02
Flow Diagram

Command Start Stop Hold Restart Abort Reset Pause Resume

Initial No
state Com-
State Transition Matrix
mand
End State

Abort-
ing Aborted

Abor-
Idle
ted

EIO0000004853.02 15
 Operating Modes

Operating Modes
What’s in This Chapter
Normal Phase ...............................................................................................16
Exception Phase ...........................................................................................17

The user can select the required mode for Running sequence as well as for the
exception sequences via supervision systems.

Normal Phase
The following table provides the description of the operating modes for Running
sequence in PhaseManager:

Operating modes Integer Value Description

Auto Mode 0 Transition between the steps in the

Running sequence happens
automatically. Once the START
command is initiated, the phase
state will be Running and remains
in that state until HOLD, ABORT, or
STOP commands are initiated by
the user. Phase state is then
indicated as Completed once
execution of all steps are
completed.

Semi-Auto Mode 1 Transitions between the sequence

steps needs a confirmation from the
user. Once execution of a step is
completed, the sequence requests
a SEMI command from the user to
make a transition for next step. Until
then the sequence remains
suspended. Phase state will be
indicated as Running once START
command is initiated and remains in
that state until HOLD, ABORT, or
STOP commands are initiated by
the user. Phase state will be then
indicated as Completed once
execution of all steps are
completed.

Manual Mode 2 Required phase step in Running

sequence can be selected manually
upon requirement. The selection of
step is limited to one step at a time
for convenient execution of manual
mode. Phase state will be indicated
as Running once START
command is initiated and remains in
that state until RESET command is
initiated by the user. Once
execution of the selected step is
completed, the phase state will be
indicated as Completed.

NOTE: A START or RESUME command trigger is required to change the

mode of Running sequence (Auto ↔ Semi-Auto) .
Mode change to Manual operation and vise-versa are only allowed when the
PhaseManager is in the Idle state.

16 EIO0000004853.02
Operating Modes

Exception Phase
The following table provides the description of the operating modes for exception
sequences such as Holding, Stopping, or Aborting in PhaseManager:

Operating modes Integer Value Description

Auto Mode 0 Phase state will be Holding/

Stopping/Aborting once their
associated commands are initiated.
Transition between the sequence
steps in these phases happens
automatically.

Semi-Auto Mode 1 Phase state will be Holding/

Stopping/Aborting once their
associated commands are initiated.
Transitions between the sequence
steps in these phases needs a
confirmation from the user. Once
execution of a step is completed,
the sequence requests a SEMI
command from the user to make a
transition for next step. Until then
the sequence remains suspended.

NOTE: Mode changes are not allowed for exceptions while any one of the
exception sequences is activated.

EIO0000004853.02 17
 Exception Handling

Exception Handling
An event which occurs outside the normal or desired behavior of the procedure
control is commonly called an exception. Handling of these exceptions can occur
at all levels in the control activity model and can be a part of procedural, basic, and
coordination control.
Exception handling is an essential function of batch manufacturing. Exception
handling is an integral part of all controls and typically constitutes a very large
portion of the control definition.
Examples of events that indicates the need for exception handling are as follows:
• Unavailability of raw materials, utilities, or plant equipment when needed
• Product or process problems
• Control equipment malfunction
• Hazardous conditions such as fire or chemical spills
From the standpoint of control, exception handling is not different from desired
control strategies in which an event is detected, evaluated, and a response
generated.
Exception response functions can affect the modes and states of equipment
entities and procedural elements. For example, high pressure in a reactor could
lead to the exception response function which transfers the process to a Stopped
state, or an operator could detect some unusual condition and initiate similar
action.
Hence the user can configure the exception sequence (via Offline
Parameterization) to be executed once an exception (Failure) is detected.
Thus, once an exception (Failure) is detected in the PhaseManager, it
automatically executes the user configured sequence along with an alarm
indication.
Following table describes the Offline Parameter configuration values for
exception handling in PhaseManager:

S.No Exception Sequence Integer Value

1 Holding 0

2 Stopping 1

3 Aborting 2

NOTE: The exceptions are executed as per the exception mode defined by
the user. Refer Operating Modes, page 16 for more information.

18 EIO0000004853.02
Strategy and Parameter Configuration

Strategy and Parameter Configuration

As per the process requirement, the user can configure required process
Strategies with customized Strategy Name along with its associated
InputParameters (Real Data-type). As a result, configured InputParameters with
setpoint entry fields are listed in the Strategy Selection faceplates of supervision
systems. Users can utilize these InputParameters for their phase management.
Whereas, OutputParameters are the parameter feedbacks available from the
process such as Temperature, Pressure, Level etc.. All the available
OutputParameters are listed in the Output Parameter Faceplate of supervision
systems.
A maximum of 16 user defined Strategy selections are provided by default.
Whereas 15 user defined InputParameters and 15 user defined
OutputParameters are provided as a by default configuration. If more such
parameters are required, refer to Customization, page 64.
Total number of strategies to be listed in the Strategy Selection faceplates can be
limited via Total Strategy variable (Offline Parameterization) available in
PhaseManager. Similarly, if Total Strategy = 0, all available InputParameters
will be listed at the Strategy Selection faceplate.
The user selected Strategy and InputParameter set points are available as
output variables from the PhaseManager functional block where as,
OutputParameters are exposed as input variables. These variables can be
utilized for phase management operations. Refer Example of Use, page 53.

EIO0000004853.02 19
 Initialization of Application

Initialization of Application
SIFBs and IThis blocks are used in library objects, the initialization of which
required for normal operation. Libraries such as application, hardware, and
sequence have unique IDs that are responsible for identifying the library
application to be initialized. The different ids are APP_INIT for application
libraries, HW_INIT for hardware libraries, and SEQ_INIT for sequence libraries.
In the following example, the DPAC_FULLINIT block will initialize both the
hardware and application objects. The sequence object is initialized while the
block EVENTCHAINHEAD is running.
Since the initialization process is visible to the user, the DPAC_FULLINIT and
EVENTCHAINHEAD blocks must be triggered whenever the device is powered
on or after any on-line change for any application to function normally.
These initialization are mandatory for the user before developing any application.

20 EIO0000004853.02
HMI Compatibility

HMI Compatibility
HMI Compatibility allows the user to select respective operating system HMI. The
following are the two different HMI Compatibility options.
• Windows HMI - It supports in Windows platform only.
• Multi-OS HMI - It supports Multi OS platforms.
The user can be able to configure the Multi-OS HMI Compatibility by right clicking
the Solution (EAEApplicationLibraries) →Select HMI Compatibility →Multi-OS
HMI (as shown in the below image) for Multi-OS Compatibility. The case is similar
to convert from Multi-OS to Windows HMI. Where it will be in Multi-OS HMI before
conversion and you have to select Windows HMI.

EIO0000004853.02 21
Phase Object
What’s in This Part
PhaseManager ..............................................................................................23
Example of Use - PhaseManager ....................................................................53
Customization ................................................................................................64

22 EIO0000004853.02
PhaseManager

PhaseManager
What’s in This Chapter
Control .........................................................................................................23
Supervision (EcoStruxure Automation Expert) .................................................30
Supervision (Aveva System Platform) .............................................................39

General Description
This chapter describes the components that provide the functionality, control
services, and Supervision functions of the PhaseManager.

Overview
The PhaseManager functional module is used to monitor and manage the phase
control operation by accepting statuses and delivering appropriate commands to
the sequence blocks of SE.AppSequence library. Hence this module is based on
the ISA-S88 Standard, Part 1 (S88.01i) and implements the status controller
defined in this standard for controlling procedure model components (phases,
operations, and so on).

Control
This section describes the interface of PhaseManager.

Interface Representation
The following image represents the PhaseManager interface:

EIO0000004853.02 23
 PhaseManager

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

REQ_SUPPRESS_ALM SuppressAlarm Request to suppress the

alarm
REQ_OP OutputPara Request for output
parameters

Input Data Interface

The following table describes the input data interface:

Name Type Description

SuppressAlarm BOOL 1 = Suppress alarm

monitoring

OutputPara SE.AppProcedure. Output parameters

PhaseParameters (Feedback parameters)

Sockets
The following table describes the sockets:

Name Type Description

ISc SE.AppProcedure.IPhase Sequence control adapter

Adapter Inputs
The following table describes the adapters:

Name Type Description

IFail SE.AppCommonProcess.IOpFailS Condition summary chain

input from upstream blocks

IPerm SE.AppCommonProcess.IOpPermS Permission condition

summary chain input from
upstream blocks

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

CNF PhaseState Phase state confirmation

CNF_STRATEGY Strategy Phase strategy
confirmation

24 EIO0000004853.02
PhaseManager

Name With Description

CNF_IP InputPara Confirmation for input

parameters

CONFIG_ERROR ConfigError Configuration error

confirmation

Output Data Interface

The following table describes the output data interface:

Name Type Description

PhaseState SE.AppProcedure.PhaseStates Phase state:

0 = Undefined

1 = IdleState

2 = RunningState

3 = HeldState

4 = StoppedState

5 = PausedState

6 = AbortedState

7 = CompleteState

8 = HoldingState

9 = RestartingState

10 = PausingState

11 = StoppingState

12 = AbortingState

13 = InterlockedState
Strategy UINT Phase strategy

InputPara SE.AppProcedure. Input parameters

PhaseParameters (Setpoint)

ConfigError BOOL 1 = Configuration error

detected (Running
procedure is not
connected)

Adapter Outputs
The following table describes the adapter outputs:

Name Type Description

IRunning SE.AppSequence.ISeqChain Running procedure

connection
IHolding Holding procedure
connection
IRestarting Restarting procedure
connection
IStopping Stopping procedure
connection
IAborting Aborting procedure
connection

EIO0000004853.02 25
 PhaseManager

Sequence
The sequence variables are defined in the table below:

Variable Data type Description Access type

InstanceName. VTQ UINT Current mode of running Read

currentMode phase:

0 = Auto

1 = Semi-Auto

2 = Manual
InstanceName. VTQ UINT Current strategy selection
currentStrategy (user-defined)

InstanceName. SE. Current state of

currentState AppProce- PhaseManager:
dure.
PhaseStates 0 = Configuration Error

1 = Idle State

2 = Running State

3 = Held State

4 = Stopped State

5= Paused State

6 = Aborted State

7 = Complete State

8 = Holding State

9 = Restarting State

10 = Pausing State

11 = Stopping State

12 = Aborting State

13 = Interlocked State
InstanceName. VTQ BOOL 1 = Step exceeded
stepExceeded acknowledgement from
connected phases

InstanceName. SE. Output parameters

outputPara AppProce- (Feedback parameters)
dure.
PhaseParame-
ters
InstanceName.mode VTQ UINT Mode of running phase: Write

0 = Auto

1 = Semi-Auto

2 = Manual
InstanceName. VTQ UINT Strategy selection for phase
strategy operation (user defined)

InstanceName. SE. Phase command:

command AppProce-
dure. 0 = Undefined
Commands
1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

26 EIO0000004853.02
PhaseManager

Variable Data type Description Access type

128 = Abort
InstanceName. VTQ BOOL Semi Start command to the
semiStart phases in Semi-Auto mode

InstanceName. VTQ UINT Manual step id for running

manStepId phase

InstanceName. SE. Input parameters (Setpoint)

inputPara AppProce-
dure.
PhaseParame-
ters

Offline Parametrization
The following table describes the offline parametrization:

Path Type Default value Description

IThis. BOOL FALSE Exception mode:

ExceptionMode
0 = Auto

1 = Semi-Auto

Failures - For more details, refer to the EcoStruxure Automation Expert -

Common Process Reference Manual.
Owner - For more details, refer to the AppBaseLibrary Owner CAT Online Help
document.
InitCond - For more details, refer to the EcoStruxure Automation Expert -
Common Process Reference Manual.
InitialCondition - For more details, refer to the EcoStruxure Automation Expert -
Common Process Reference Manual.
FailueCondition - For more details, refer to the AppBaseLibrary Owner CAT
Online Help document.
Parameter - For more details, refer to the section PhaseRealParam, page 98.

OPCUA
The following table describes the OPCUA:

EIO0000004853.02 27
 PhaseManager

Path Type Access level Display name Min. Description

Sampl.
Interval
IThis. UInt16 Read-Only Current- 0 Current state of
CurrentState State PhaseManager:

0=
Configuration
Error

1 = Idle State

2 = Running
State

3 = Held State

4 = Stopped
State

5= Paused
State

6 = Aborted
State

7 = Complete
State

8 = Holding
State

9 = Restarting
State

10 = Pausing
State

11 = Stopping
State

12 = Aborting
State

13 = Interlocked
State
IThis. UInt16 Current- 0 Current mode
CurrentMode Mode of running
phase:

0 = Auto

1 = Semi-Auto

2 = Manual
IThis. UInt16 Current- 0 Current
CurrentStrat- Strategy strategy
egy selection (user-
defined)

IThis. UInt16 Current- 0 Current manual

CurrentMan- ManStep step id
Step

IThis. Float Runni- 0 Phase running

RunningTime ngTime time

IThis. Boolean Enable- 0 1 = Stable step

EnablePause Pause in running
phase is
detected, hence
pause
command is
enabled for
running phase

IThis. Boolean StepExcee- 0 1 = Step

StepExceeded ded exceeded
acknowledge-
ment from
connected
phases

28 EIO0000004853.02
PhaseManager

Path Type Access level Display name Min. Description

Sampl.
Interval
IThis. String MsgTotal- 0 Total step id
MsgTotalSte- StepId from running
pId phase

IThis.Command UInt16 ReadWrite Command 0 Phase

command:

0 = Undefined

1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

128 = Abort
IThis.Mode UInt16 Mode 0 Mode of
running phase:

0 = Auto

1 = Semi-Auto

2 = Manual
IThis. Boolean SemiStart 0 Semi Start
SemiStart command to
the phases in
Semi-Auto
mode
IThis. UInt16 ManStepId 0 Manual step id
ManStepId for running
phase

IThis. UInt16 Strategy 0 Strategy

Strategy selection for
phase
operation (user-
defined)

IThis. Boolean AutoReset 0 1 = Auto reset

AutoReset enabled, State
change from
final transient
states to Idle
happens
automatically

IThis. UInt16 Total- 0 Total strategies

TotalStrategy Strategy to be
considered for
phase
operation

IThis. UInt16 Exception- 0 Procedure to

ExceptionPro- Procedure execute while
cedure exception
active:

0 = Holding

1 = Stopping

2 = Aborting

IThis. Boolean Exception- 0 Exception

ExceptionMode Mode mode:

0 = Auto

1 = Semi-Auto

EIO0000004853.02 29
 PhaseManager

Failures - For more details, refer to the EcoStruxure Automation Expert -

Common Process Reference Manual.
Owner - For more details, refer to the AppBaseLibrary Owner CAT Online Help
document.
InitCond - For more details, refer to the EcoStruxure Automation Expert -
Common Process Reference Manual.
InitialCondition - For more details, refer to the EcoStruxure Automation Expert -
Common Process Reference Manual.
FailueCondition - For more details, refer to the AppBaseLibrary Owner CAT
Online Help document.
Parameter - For more details, refer to the section PhaseRealParam, page 98.

Supervision (EcoStruxure Automation Expert)

This section describes the supervision resources and runtime services that are
available for the PhaseManager.

Symbols
Symbol Representation
For more information, see the Supervision - EcoStruxure Automation Expert HMI
→ Graphics → Symbols section of the EcoStruxure Automation Expert - Common
Process Reference Manualdocument.

Icons
For more information, see the Supervision - EcoStruxure Automation Expert HMI
→ Graphics → Icons section of the EcoStruxure Automation Expert - Common
Process Reference Manual.

Symbols
The table describes the symbols of the PhaseManager control module:

Name Graphic symbol Description Security

Group

sDefault PhaseManager symbol with state, Setpoint

mode, strategy, phase running time,
failure, permissive and interlock
statuses, and command buttons for
PhaseManager operation.

— In Semi-Auto mode, the

SEMI-START command is used to
confirm step transitions from the
user.
NOTE: The SEMI-START
command button is designed
with a flashing brush color
(Grey/White) and will be visible
only when the execution of a
step is complete in Semi-Auto
mode. A flashing command
button (Grey/White) will be
visible, as shown.

30 EIO0000004853.02
PhaseManager

Symbol Properties
The symbol properties available for the user to configure the PhaseManager in
EcoStruxure Automation Expert are explained in this section.
The user can define a maximum of 16 Strategies with respective
ApplicableInputParameters. 15 InputParameters and 15 OutputParameters
are provided as default configuration of the library. Refer to Customization, page
64 for configuring more parameters.
The PhaseManager symbol attributes are shown in the image below:

Symbol properties Description

Permissive/Failure Visibility Enables the visibility of Permissive, Failure into

symbol

None – Hide the Permissive and Failure

symbols

All – Shows the Permissive and Failure symbols

Permissive – Displays the Permissive symbol

Failure – Displays the Failure symbol

InputParameters InputParameters are configured as an array of

string. To add a new parameter follow the
procedure given below:

EIO0000004853.02 31
 PhaseManager

Symbol properties Description

1. Click the button available on the right

most side of InputParameters tab of
Parameter Description category.
2. A dialogue box opens asking the user to
enter all the descriptions of
InputParameters (One parameter per line).
Parameter units can be entered as comma
separated along with the description. For
example Input Temperature,°C.
3. All parameters entered can be viewed as a

list by clicking on the button available

on the left most side of InputParameters
tab.
OutputParameters OutputParameters are configured as an array of
string. To add a new parameter follow the
procedure given below:

1. Click the button available on the right

most side of OutputParameters tab of
Parameter Description category.
2. A dialogue box opens asking the user to
enter all the descriptions of
OutputParameters (One parameter per
line). Parameter units can be entered as
comma separated along with the
description. For example Output
Temperature,°C.
3. All parameters entered can be viewed as a

list by clicking on the button available

on the left most side of OutputParameters
tab.
Strategy Configuration User can define required process Strategies with
customized Strategy Name and Applicable
Input Parameters. The Applicable Input
Parameters can be configured with the index
values (Order index of parameters defined at the
InputParameter section) separated by semi-
column as shown in the figure above..

AliasName The user can configure the application name

which has to be displayed on the sDefault
symbol.

Display Type Allows you to select the display option of the

symbol.

Panel Only – Displays PhaseManager symbol

with State, Mode, Strategy and Running Time.
No command buttons will be available.

CommandButtonsWithPanel – Displays
PhaseManager symbol with State, Mode,
Strategy and Running Time along with
command buttons.
HideTagDisplayName • True: Hides the instance name on symbol.
• False: Shows the instance name on symbol.

NOTE: Parameter descriptions are designed with array of string data-type,

where the users can define 'n' number of Input and output parameters as per
the process requirements. Hence, first parameter (i.e., Input Parameter 1 or
Output Parameter 1) shown on the list is with array index value 0. Similarly,
the 15th parameter (Input Parameter 14 or Output Parameter 15) shown on the
list is with array index value 14. Refer to the InputParameters or
OutputParameters section above.

32 EIO0000004853.02
PhaseManager

Faceplate
Representation of Supervision Data
Refer SE.AppCommonProcess library for general description of the graphic
elements and element styles that are used in faceplates.

Available Tabs
During operation, clicking the symbol displays a faceplate with the following tabs:
• Operation
• Output Parameter
NOTE:
The Output Parameter faceplate can be accessed by clicking the output
parameter symbol ( ) in the operator faceplate.
• Owner
NOTE: The Owner faceplate can be accessed by clicking the owner

symbol ( ) in the operator faceplate. For more details, refer to the

AppBaseLibrary Owner CAT Online Help document.
• Parameter
NOTE:
The Parameter faceplate can be accessed by clicking the parameter

symbol ( ) in the operator faceplate.

• Failure - Refer to the EcoStruxure Automation Expert — Common Process
Library. .
• Permissive - Refer to the EcoStruxure Automation Expert — Common
Process Library. .
• Strategy Selection
NOTE:
The Strategy Selection faceplate can be accessed by clicking the start

symbol ( ) in the operator faceplate.

If no Strategy (Total Strategy = 0) as well as no Applicable Input
Parameters are available for phase operation, clicking the start symbol (

) initiates the START command for PhaseManager.

EIO0000004853.02 33
 PhaseManager

Operation Tab
The following image shows the Operator tab:

34 EIO0000004853.02
PhaseManager

The table describes the various functions of the Operator tab:

Label Description Security

Group

State Current state of PhaseManager: —

• 0 = Configuration Error (Running sequence not
connected)
• 1 = Idle State
• 2 = Running State
• 3 = Held State
• 4 = Stopped State
• 5 = Paused State
• 6 = Aborted State
• 7 = Complete State
• 8 = Holding State
• 9 = Restarting State
• 10 = Pausing State
• 11 = Stopping State
• 12 = Aborting State
• 13 = Interlocked State
Current Mode Current mode of Running sequence:
• 0 = Auto
• 1 = Semi-Auto
• 2 = Manual
Applied Strategy Current applied strategy (User-Defined).

Current Owner Current owner selected for operation. For more details,
refer to the AppBaseLibrary Owner CAT Online Help
document.
Owner Owner command (Program /Operator) Owner

Mode Operation modes of Running sequence: Setpoint

• Auto
• Semi-Auto
• Manual
For more details, refer to the Operating Modes, page 16.

Command Buttons
— START/OPEN
STRATEGY SELECTION FACEPLATE, HOLD,
PAUSE, RESUME, STOP, ABORT, RESET commands
for phase control operation.

— In Semi-Auto mode, the SEMI-START

command is used to confirm step transitions from the
user.
NOTE: The SEMI-START command button is
designed with a flashing brush color (Grey/White)
and will be visible only when the execution of a step
is complete in Semi-Auto mode. A flashing
command button (Grey/White) will be visible, as
shown.

EIO0000004853.02 35
 PhaseManager

Output Parameter Tab

The following image shows the Output Parameter tab:

This tab shows the list of user defined output parameters and their process values
configured at Symbol Properties, page 31 section.

36 EIO0000004853.02
PhaseManager

Parameter Tab
The following image shows the Parameter tab:

The table describes the various functions of the Parameter tab:

Label Description Security Group

Exception Mode Mode selection for exception phases such Parameter

as Holding & Restarting sequence,
Stopping or Aborting sequence (0 = Auto
Mode, 1 = Semi-Auto Mode).

NOTE: Exception mode change is not allowed when any of the exception
sequence is active.

EIO0000004853.02 37
 PhaseManager

Strategy Selection Tab

The following image shows the Strategy Selection tab:

NOTE: The Strategy Selection faceplate is not available if Total Strategy = 0

and Available Input Parameters = 0.
The table describes the various functions of the Strategy Selection tab:

Label Description Security Group

Strategy Strategy used for PhaseManager operation Setpoint

(User-Defined).

Step Selection Running sequence Step Selection in

Manual mode (Available when Manual
mode is selected for Running sequence).

Input Parameter List of user defined input parameters and Parameter

their process setpoints configured at Symbol
Properties, page 31 section.

Command Button Setpoint

— START command to start
PhaseManager operation.

Alarms
The alarms available in this block are listed in the following table:

Sl. No. Name Type Description

1 Failure condition Alarm PhaseManager detected failure.

detected
2 Initial condition Alarm Initial conditions are not satisfied.
detected

38 EIO0000004853.02
PhaseManager

Supervision (Aveva System Platform)

This section describes the supervision resources and runtime services that are
available for the $SEPhaseManager.

Supervision Functions
Function Description
The main functions of $SEPhaseManager template are described in the following
table:

Function Description

Owner The object can be switched to different modes of operation like Program
and Operator. It allows to configure the allowed owner and the normal
owner.
Failure Allows to monitor the detected failure status. It also provides an option to
bypass and rearm individual conditions from Failure tab.

Permissive Allows to monitor the permissive status It also provides an option to

bypass the individual condition from Permissive tab.

Process Parameter The user can configure the required number InputParameter,
OutputParameter, Strategyand applicable IP param for the strategy.

Control/Supervision Relationship
Control Resources
Supervision function is used to communicate with the control module function
PhaseManager in the SE.AppProcedure library.
Below are the attributes for which the data is exchanged through supervision:

Aveva System Platform EcoStruxure Automation Expert tag name paths

attribute names
Command <Instance Name Path>.IThis.Command
CurrentManStep <Instance Name Path>.IThis.CurrentManStep

CurrentMode <Instance Name Path>.IThis.CurrentMode

CurrentState <Instance Name Path>.IThis.CurrentState
CurrentStrategy <Instance Name Path>.IThis.CurrentStrategy

EnablePause <Instance Name Path>.IThis.EnablePause

ExceptionMode <Instance Name Path>.IThis.ExceptionMode

ExceptionProcedure <Instance Name Path>.IThis.ExceptionProcedure

ManStepId <Instance Name Path>.IThis.ManStepId

Mode <Instance Name Path>.IThis.Mode

MsgTotalStepId <Instance Name Path>.IThis.MsgTotalStepId

RunningTime <Instance Name Path>.IThis.RunningTime

SemiStart <Instance Name Path>.IThis.SemiStart

StepExceeded <Instance Name Path>.IThis.StepExceeded

Strategy <Instance Name Path>.IThis.Strategy

TotalStrategy <Instance Name Path>.IThis.TotalStrategy

FailureCondition. <Instance Name Path>.FailureCondition.IThis.

AlarmForce AlarmForce

EIO0000004853.02 39
 PhaseManager

Aveva System Platform EcoStruxure Automation Expert tag name paths

attribute names
FailureCondition. <Instance Name Path>.FailureCondition.IThis.
AlarmStatus AlarmStatus
FailureCondition. <Instance Name Path>.FailureCondition.IThis.
Suppressed Suppressed

PermissiveCondition. <Instance Name Path>.PermissiveCondition.IThis.

AlarmForce AlarmForce
PermissiveCondition. <Instance Name Path>.PermissiveCondition.IThis.
AlarmStatus AlarmStatus
PermissiveCondition. <Instance Name Path>.PermissiveCondition.IThis.
Suppressed Suppressed

Parameter01.IP01 <Instance Name Path>.Parameter01.IThis.IP01

Parameter01.IP02 <Instance Name Path>.Parameter01.IThis.IP02
Parameter01.IP03 <Instance Name Path>.Parameter01.IThis.IP03
Parameter01.IP04 <Instance Name Path>.Parameter01.IThis.IP04
Parameter01.IP05 <Instance Name Path>.Parameter01.IThis.IP05
Parameter01.IP06 <Instance Name Path>.Parameter01.IThis.IP06
Parameter01.IP07 <Instance Name Path>.Parameter01.IThis.IP07
Parameter01.IP08 <Instance Name Path>.Parameter01.IThis.IP08
Parameter01.IP09 <Instance Name Path>.Parameter01.IThis.IP09
Parameter01.IP10 <Instance Name Path>.Parameter01.IThis.IP10
Parameter01.IP11 <Instance Name Path>.Parameter01.IThis.IP11
Parameter01.IP12 <Instance Name Path>.Parameter01.IThis.IP12
Parameter01.IP13 <Instance Name Path>.Parameter01.IThis.IP13
Parameter01.IP14 <Instance Name Path>.Parameter01.IThis.IP14
Parameter01.IP15 <Instance Name Path>.Parameter01.IThis.IP15
Parameter01.OP01 <Instance Name Path>.Parameter01.IThis.OP01
Parameter01.OP02 <Instance Name Path>.Parameter01.IThis.0P02
Parameter01.OP03 <Instance Name Path>.Parameter01.IThis.OP03
Parameter01.OP04 <Instance Name Path>.Parameter01.IThis.OP04
Parameter01.OP05 <Instance Name Path>.Parameter01.IThis.OP05
Parameter01.OP06 <Instance Name Path>.Parameter01.IThis.OP06
Parameter01.OP07 <Instance Name Path>.Parameter01.IThis.OP07
Parameter01.OP08 <Instance Name Path>.Parameter01.IThis.OP08
Parameter01.OP09 <Instance Name Path>.Parameter01.IThis.OP09
Parameter01.OP10 <Instance Name Path>.Parameter01.IThis.OP10
Parameter01.OP11 <Instance Name Path>.Parameter01.IThis.OP11
Parameter01.OP12 <Instance Name Path>.Parameter01.IThis.OP12
Parameter01.OP13 <Instance Name Path>.Parameter01.IThis.OP13
Parameter01.OP14 <Instance Name Path>.Parameter01.IThis.OP14
Parameter01.OP15 <Instance Name Path>.Parameter01.IThis.OP15
Parameter01.IP16 Available only when the control parameter is extended to 30.
Parameter01.IP17
Parameter01.IP18
Parameter01.IP19
Parameter01.IP20
Parameter01.IP21
Parameter01.IP22
Parameter01.IP23
Parameter01.IP24

40 EIO0000004853.02
PhaseManager

Aveva System Platform EcoStruxure Automation Expert tag name paths

attribute names
Parameter01.IP25
Parameter01.IP26
Parameter01.IP27
Parameter01.IP28
Parameter01.IP29
Parameter01.IP30
Parameter01.OP16
Parameter01.OP17
Parameter01.OP18
Parameter01.OP19
Parameter01.OP20
Parameter01.OP21
Parameter01.OP22
Parameter01.OP23
Parameter01.OP24
Parameter01.OP25
Parameter01.OP26
Parameter01.OP27
Parameter01.OP28
Parameter01.0P29
Parameter01.OP30
Permissive. <Instance Name Path>.Permissive.IThis.
BypassDisabled BypassDisabled

Permissive. <Instance Name Path>.Permissive.IThis.

PermBypassMask PermBypassMask

Permissive.PermActive1 <Instance Name Path>.Permissive.IThis.PermActive1

Permissive.PermActive2 <Instance Name Path>.Permissive.IThis.PermActive2
Permissive.PermInfo <Instance Name Path>.Permissive.IThis.PermInfo
Permissive.PermOption1 <Instance Name Path>.Permissive.IThis.PermOption1

Permissive.PermOption2 <Instance Name Path>.Permissive.IThis.PermOption2

Permissive.PermPassive <Instance Name Path>.Permissive.IThis.PermPassive

Permissive. <Instance Name Path>.Permissive.IThis.PermSuppress
PermSuppress

Permissive.SignalInfo <Instance Name Path>.Permissive.IThis.SignalInfo

Permissive.Suppress <Instance Name Path>.Permissive.IThis.Suppress

Failure.BypassDisabled <Instance Name Path>.Failure.IThis.BypassDisabled

Failure.CondBypassMask <Instance Name Path>.Failure.IThis.CondBypassMask

Failure.CondResetCmd <Instance Name Path>.Failure.IThis.CondResetCmd

Failure.CondSignal <Instance Name Path>.Failure.IThis.CondSignal

Failure.CondSuppress <Instance Name Path>.Failure.IThis.CondSuppress

Failure.FirstCondInfo <Instance Name Path>.Failure.IThis.FirstCondInfo

Failure.ResetFirstCond <Instance Name Path>.Failure.IThis.ResetFirstCond
Failure.ResetInfo <Instance Name Path>.Failure.IThis.ResetInfo
Failure.SignalInfo <Instance Name Path>.Failure.IThis.SignalInfo

Failure.Supress <Instance Name Path>.Failure.IThis.Supress

Failure.ResetReq <Instance Name Path>.Failure.IThis.ResetReq

Failure. <Instance Name Path>.Failure.IThis.

ConditionPassive ConditionPassive

EIO0000004853.02 41
 PhaseManager

Aveva System Platform EcoStruxure Automation Expert tag name paths

attribute names
Failure. <Instance Name Path>.Failure.IThis.
ConditionActive1 ConditionActive1
Failure. <Instance Name Path>.Failure.IThis.
ConditionActive2 ConditionActive2
Failure.CondResetMask <Instance Name Path>.Failure.IThis.CondResetMask
Owner.IsNormal <Instance Name Path>.Owner.IThis.IsNormal
Owner.Target <Instance Name Path>.Owner.IThis.Target

Owner.Current <Instance Name Path>.Owner.IThis.Current

Owner.Valid <Instance Name Path>.Owner.IThis.Valid
Owner.Available <Instance Name Path>.Owner.IThis.Available
Owner.Notallowed <Instance Name Path>.Owner.IThis.Notallowed
Owner.NotAvailable <Instance Name Path>.Owner.IThis.NotAvailable
Owner.Normal <Instance Name Path>.Owner.IThis.Normal
Owner.Allowed <Instance Name Path>.Owner.IThis.Allowed
Owner.Requested <Instance Name Path>.Owner.IThis.Requested

NOTE: <Instance Name Path> – Referred to as <Device.Resource.Instance>

Supervision attributes exchanges data with EcoStruxure Automation Expert

variables on OPCUA. Each variable in EcoStruxure Automation Expert which is
exposed to OPCUA, generates the corresponding unique GUID with which
supervision attribute communicates.
For more information, see the Supervision - Aveva System Platform → Control
Resources and Communication section of the EcoStruxure Automation Expert -
Common Process Reference Manual.

Parameters
Configuration Parameter
The below table describes the configuration parameters:

Name Default Description

values
Param. #.## Formatting string to be used for numerical output representation (for
NumFormat example, 0.00)

InputParameters 0 The user can configure a maximum of 30 InputParameters. By

default only 16 is supported and rest can be used when the control
parameter is extended to 30. Refer the below example on how to
extend the parameters.
1. Add the required attributes following the datatype and other
formats as same as the existing attributes.
2. The name of the attribute should be prefixed with IP and
suffixed with the number. For example IP31 for the Input
parameter 31.

42 EIO0000004853.02
PhaseManager

Name Default Description

values

3. Extend the choice to the required number by clicking

from the object wizards.

4. Associate IP attributes and faceplate for the newly created

choice. The custom property InputParameter lists in the
settings of faceplate in the association window is mandatory.
This number indicates the selected InputParameter.

5. Follow the procedure below to extend the Inputparameter at

the instance level.

EIO0000004853.02 43
 PhaseManager

Name Default Description

values
• Use the wizard option Input Parameters as shown
below:

• Configure the description and engineering units in the

displayed attributes as shown below:

OutputParame- 0 The user can configure a maximum of 30 OutputParameters. By

ters default only 15 is supported and rest can be used when the control
parameter is extended to 30. Refer the below example on how to
extend the parameters.
Follow the procedure below to extend the parameters given in the
image below :
1. Add the required attributes following the datatype and other
formats as same as the existing attributes.
2. The name of the attribute should be prefixed with OP and
suffixed with the number. For example OP31 for the Output
parameter 31.

3. Extend the choice to the required number by clicking

from the object wizards.

44 EIO0000004853.02
PhaseManager

Name Default Description

values
4. Associate OP attributes and faceplate for the newly created
choice. The custom property OutputParameter lists in the
settings of faceplate in the association window is mandatory.
This number indicates the selected OutputParameter.

5. Follow the procedure below to extend the Outputparameter

at the instance level.
• Use the wizard option Output Parameters as shown
below:

• Configure the description and engineering units in the

displayed attributes as shown below:

Strategy 0 The user can configure a maximum of 30 Strategyand applicable

input parameter for the respective strategies.
Follow the procedure below to extend the parameters given in the
image below :
1. Add the required attributes following the datatype and other
formats as same as the existing attributes.
2. The name of the attribute should be prefixed with Startegy and
suffixed with the number. For example Strategy 31 for the
strategy 31.

EIO0000004853.02 45
 PhaseManager

Name Default Description

values

3. Extend the choice to the required number by clicking

from the object wizards.

4. Associate strategy attributes and faceplate for the newly

created choice. The custom property Strategy lists in the
settings of faceplate in the association window is mandatory.
This number indicates the selected Strategy.

5. Follow the procedure below to extend the Strategy at the

instance level.
• Use the wizard option Strategy as shown below:

• Configure the description and engineering units in the

displayed attributes as shown below:

46 EIO0000004853.02
PhaseManager

Name Default Description

values

For more information about Permissive/Failure configuration parameter, see the

Supervision - Aveva System Platform → Application Object Wizard Configuration
section of the EcoStruxure Automation Expert - Common Process Reference
Manual.

Symbols
Representation of Supervision Data
You can find a brief description of the graphic elements and element styles used in
faceplates. For more information, see the Supervision - EcoStruxure Automation
Expert HMI→ Graphics → Icons section of the EcoStruxure Automation Expert -
Common Process Reference Manual.

Symbol Description
The embedded and link symbols that are included in the $SEPhaseManager
master template for different objects choices are described below.

Embedded Symbol
Embedded symbols have a fixed shape and help users directly drag and drop the
symbol on their respective pages:

Name Graphic symbol Description

PanelWith- PhaseManager symbol with

Buttons state, mode, strategy, phase
running time, failure, permissive,
and statuses, and command
buttons for PhaseManager
operation.

— In Semi-Auto mode, the

SEMI-START command is used
to confirm step transitions from
the user.
NOTE: The SEMI-START
command button is designed
with a flashing brush color
(Grey/White) and will be
visible only when the
execution of a step is
complete in Semi-Auto
mode. A flashing command
button (Grey/White) will be
visible, as shown.

EIO0000004853.02 47
 PhaseManager

Link Symbol
Symbol Name: Link_PhaseManager
These symbols provide a wizard for the user to select while dragging and
dropping. The wizard option below provides the user with the option to select their
required symbol:

Wizard Option Description Choice

DisplayType Defines the information which • CommandButtonsWithPa-

user wants to see. nel: Panel along with the
buttons are displayed
• OnlyPanel : Only the panel
is dsiplayed

Label Label enables a descriptive • True

label to be displayed above the • False
symbol during run time

LabelType Defines how the label of the • Static Text - Static String
symbol is specified set by substitute string
function
• CustomPropertyLabel -
Define as dynamic name in
label custom property
• ObjectTagname - Display
tagname of the object

AlarmBorder Display the alarm border • True: Display alarm border

• False: Hides display alarm
border

Faceplate
Representation of Supervision Data
You can find a brief description of the graphic elements and element styles used in
faceplates. For more information, see the Supervision - EcoStruxure Automation
Expert HMI→ Graphics → Icons section of the EcoStruxure Automation Expert -
Common Process Reference Manual.

Available Tabs
During operation, clicking the symbol displays a faceplate with the following tabs:
• Operation
• Input
• Output
• Failure(Optional)
• Permissive(Optional)
• Engineering
• Alarm

48 EIO0000004853.02
PhaseManager

Operation Tab
The following image shows the Operator tab:

The table describes the various functions of the Operator tab:

Label Description Security

State Current state of PhaseManager: —

• 0 = Configuration Error (Running sequence not
connected)
• 1 = Idle State
• 2 = Running State
• 3 = Held State
• 4 = Stopped State
• 5 = Paused State
• 6 = Aborted State
• 7 = Complete State
• 8 = Holding State
• 9 = Restarting State
• 10 = Pausing State
• 11 = Stopping State
• 12 = Aborting State
• 13 = Interlocked State
Current Mode Current applied mode Running sequence:
• 0 = Auto
• 1 = Semi-Auto
• 2 = Manual
Applied Strategy Current applied strategy (User-Defined).

Current Owner Current owner selected for operation. For more details,
refer to the AppBaseLibrary Owner CAT Online Help
document.
Owner Owner command (Program /Operator) Operator

EIO0000004853.02 49
 PhaseManager

Label Description Security

Mode Running sequence modes in Program/Operator Owner:

• Auto
• Semi-Auto
• Manual
For more details, refer to the Operating Modes, page 16.

Command Buttons Operator

— START or OPEN
STRATEGY SELECTION FACEPLATE, HOLD,
PAUSE, RESUME, STOP, Abort, Reset commands for
phase control operation.

— In Semi-Auto mode, the SEMI-START

command is used to confirm step transitions from the
user.
NOTE: The SEMI-START command button will be
visible only when the execution of a step is
complete in Semi-Auto mode.

Output Parameter Tab

The following image shows the Output Parameter tab:

This tab shows the list of user defined output parameters and their process values
configured at Configuration Parameter, page 42 section.

50 EIO0000004853.02
PhaseManager

Parameter Tab
The following image shows the Parameter tab:

The table describes the various functions of the Parameter tab:

Label Description Security

Exception Mode Mode selection for exception phases such Tune

as Holding & Restarting sequence,
Stopping or Aborting sequence (0 = Auto
Mode, 1 = Semi-Auto Mode).

NOTE: Exception mode change is not allowed when any of the exception
sequence is active.

EIO0000004853.02 51
 PhaseManager

Strategy Selection Tab

The following image shows the Strategy Selection tab:

NOTE: The Strategy Selection faceplate is not available if Total Strategy = 0

and Available Input Parameters = 0.
The table describes the various functions of the Strategy Selection tab:

Label Description Security

Strategy Strategy used for PhaseManager operation Operator

(User-Defined).

Step Selection Running sequence Step Selection in

Manual mode (Available when Manual
mode is selected for Running sequence).

Input Param List of user defined input parameters and

their process setpoints configured at
Configuration Parameter, page 42 section.

Command Button

— START command to start

PhaseManager operation.

52 EIO0000004853.02
Example of Use - PhaseManager

Example of Use - PhaseManager

What’s in This Chapter
Configuration with Sequence Objects .............................................................54
Integration with AVEVA Batch Management ....................................................57

This chapter explains the configuration example of PhaseManager with multiple

objects such as:
1. Sequence objects in SE.AppSequence library.
2. Integration with AVEVATM Batch Management.

EIO0000004853.02 53
 Example of Use - PhaseManager

Configuration with Sequence Objects

Step Action

1 Create a new application (For example, ProcedureEm) under System tab as shown in the
image below:

2 Double-click the ProcedureEm to open it. Drag and drop the PhaseManager module from
SE.AppPreocedure library into the ProcedureEm and define the instance name in the
dialog box (for example, PhaseManager1). Click OK as shown in the image below:

3 To handle the output parameters, drag and drop the encodePhasePara basic block and
configure it with PhaseManager as shown in the image below . This basic block helps the
user to configure the process parameter feedbacks with the PhaseManager functional
block. As discussed earlier, by default 15 OutputParameters can be assigned to the
PhaseManager with a single instance of encodePhasePara.

For more informations refer encodePhasePara, page 72.

54 EIO0000004853.02
Example of Use - PhaseManager

4 Input parameter data for Phase Management can be extracted from InputParameters
output variable of the PhaseManager. The user can utilize the SPLIT block functionality on
the variable to convert the structured formats of parameter data. Right click on
InputParameters and select create SPLIT functional block as shown below:

Complete the connections to SPLIT block as shown below:

EIO0000004853.02 55
 Example of Use - PhaseManager

5 Drag and drop the required sequence objects from SE.AppSequence library such as
SeqStep, SeqTransition, SeqTerminate along with seqParallelAlloc and
seqTransJumpBack composites and sequence action blocks etc. as per the process
requirements.
NOTE: The SeqHead block configurations are not required for phase management
since, its functionally is already handled internally by Procedure Manager functional
block.
For more information on sequence objects, refer SE.AppSequence library.
For the current example, a simple process sequence with two steps configured for each of
the phases is shown in the image below:

6 Map all the functional blocks to their respective controllers as per the requirement.

7 Check PhaseManager and Sequence objects offline parameterization values which

enables the PhaseManager to run on preset conditions, then click Save.

8 Instantiate and configure DPAC_FULLLINIT and EVENTCHAINHEAD blocks for

application and sequence initialization respectively. Refer Initialization of Application, page
20 for more information.
9 Deploy the solution to the controller with required configurations.

56 EIO0000004853.02
Example of Use - PhaseManager

10 Check and confirm that the instances are created under the control module Instances in the
Application, as shown in the below image:

11 Create the Canvas screen for the PhaseManager with related sequence objects to operate
the PhaseManager in the visualization run time. Configure the symbol properties as per the
process requirement.

Refer EAE or ASP sections for more information on symbol properties.

Integration with AVEVA Batch Management

The PhaseInterface can be used to integrate PhaseManager with Aveva Batch
Manager, refer to the figure given below. The PhaseInterface is used to establish
the communication between Aveva Batch Manager and PhaseManager . The
PhaseInterface is designed in a generic way to make it possible to communicate
along with other Batch Management systems as well.

EIO0000004853.02 57
 Example of Use - PhaseManager

This section explains the integration procedure with Aveva Batch Management
System.
The states and commands that can be accessed from Aveva Batch Management
Systems are as follows:
• Batch States – READY, RUN, HELD, ABORTED, INTERLOCKED, DONE
• Batch Commands – START, HOLD, RESTART, ABORT
The figure given below shows the categorization of S88 state machine diagram
and Batch phase states.

58 EIO0000004853.02
Example of Use - PhaseManager

One batch consists of many phases. The user can create batch phase application
based on the process requirement.
To integrate the Batch Management system with EcoStruxure Automation Expert,
the user needs to use PhaseInterface, in which the interfacing attributes (States/
Commands) are exposed on OPCUA. The below figure shows the generic block
diagram representation:

The OI Gateway from System Platform Management Console is used to access

the tags from PhaseInterface.

EIO0000004853.02 59
 Example of Use - PhaseManager

The below table shows the steps to configure Aveva Batch Management to
communicate EcoStruxure Automation Expert over OPCUA protocol.

Step Action

1 Go to System Platform Management Console, and add the OPCUA device connection as
shown below:

Configure the OPCUA server node. The server node can be the IP address of the machine
from where the OPCUA attributes of the EcoStruxure Automation Expert is to be accessed.
In this case EcoStruxure Automation Expert is available in the same machine. Follow the
below steps to configure the OPCUA server node:
• Configure the OPCUA Server URL with its port number.
• Make sure the OPCUA Namespace appears in the bottom table.
• Define the name of alias. In this case it is configured as ‘EAE’.

2 Add OPCUA device group connection under OPCUA device connection as shown in the
image below:

60 EIO0000004853.02
Example of Use - PhaseManager

The user can see the device group name path, by clicking on the group as shown in the
image below:

3 Go to the Aveva Batch Management, Environment Display. Open the TagLinker >> Edit
>> Access. The Access Editor window is opened. Add a new access name, for example
OPCUA . Provide the computer path location where the OI Gateway is configured. In this
case OI Gateway is on the local host. The service name for the OI.GATEWAY.2 is
GATEWAY as shown in the image below:

Provide the topic name same as Device Group Name Path mentioned in the OI Gateway
server. Refer to figure 2 of step 2, page 60. Close the Access Editor window.

4 In TagLinker, go to View >> Filter and select the Units and Connections, with necessary
type of attribute as shown below:

EIO0000004853.02 61
 Example of Use - PhaseManager

5 In the below figure, the Tag Name column shows the tags created by the Batch
Management system and Item column shows the GUID variables from PhaseInterface.
The user has to configure every tag with the respective GUID of phase state and phase
command as shown in the below figure. The user has to change the access to the
GATEWAY which is created in step 3, page 61.

Prefix to the GUID is alias name of OPCUA Namespace, which is configured in step 1, page
60.

OPCUA GUID for each attribute can be found in “System.EcoRT_0.opcua.xml” file in

EcoStruxure Automation Expert application path – “<Folder Path>\<ApplicationName>
\IEC61499\bin\Deploy\SE.DPAC#Soft_dPAC”.
NOTE: Here EcoRT_0 is device name and SE.DPAC#Soft_dPAC is device type.

6 Link all the tags of each phase. After linking all the required tags, close the TagLinker.

7 Go to Environment Display and click on Environment… button. The Environment Editor

window is opened. Select IBCli service. Click on Assign Parms.. button and assign the
parameter Access Name with value as OPCUA, which is the access name added in
TagLinker in step 3, page 61. Close the Environment Editor window.

62 EIO0000004853.02
Example of Use - PhaseManager

8 In Environment Display, click on Update and update each component such as

Environment, Runtime, and Configuration one by one.

9 Now activate the OI.GATEWAY.2 server in System Platform Management Console.

10 Start all the services from Runtime in Environment Display. Now the user can
communicate Batch management system with PhaseManager.

EIO0000004853.02 63
 Customization

Customization
Customization of PhaseManager for expanding the input and output parameters
are explained in this chapter. Since input and output parameters are handled
through PhaseRealParam functional block, such parameters can be configured
by instantiating more PhaseRealParam blocks as per the requirement.
NOTE: One PhaseRealParam block supports 15 input and 15 output
Parameters. Customization of PhaseManager with more PhaseRealParam
blocks expands the parameters with an index value of 15.
For example, two PhaseRealParam blocks can introduce up to 30 input and
30 output parameters.
For current example, the process requirement is with 20 input parameters and 10
output parameters. Hence as discussed, the number of PhaseRealParam blocks
required are two. The procedure for configuring two PhaseRealParam blocks are
explained below:

Step Action

1 Select the PhaseManager in the SE.AppProcedure library. Right-click PhaseManager

→ Copy as shown below:

64 EIO0000004853.02
Customization

2 Expand the Solution (PhaseManagerCustomization) and CAT. Right-click

Application → Paste and define the name in Dialog box (for example,
MyPhaseManager) as shown below:

3 Double-click MyPhaseManager and the following interface appears:

EIO0000004853.02 65
 Customization

4 Navigate to the Composite tab of the MyPhaseManager equipment module and identify
the PhaseRealParam objects configured in the right-bottom corner. Instantiate the
required number of PhaseRealParam objects (two as per current process example) as
shown in the image below:
NOTE: It is required to maintain the consistency of naming philosophy for all
PhaseRealParam objects instances (Parameterx, where x = 01 to Required No.s
of PhaseRealParam objects in ascending order), as implemented in the
PhaseManager functional module.
For example, as per current process requirement two PhaseRealParam instances are
required. Thus the instance names should be configured as Parameter01 and
Parameter02 as shown in the image below.

5 Refer to the current connections of PhaseRealParam blocks that were previously

available in the library and repeat the procedure for the customized blocks. Following are
checklist for those connections:
• INIT Connections of PhaseRealParam blocks.
• Exposing of data and event variables of input and output parameters to the CAT
level.
• Owner selection information from Owner CAT.
NOTE: Sel 1 variable in PhaseRealParam block should be connected with
Target Operator variable where as Sel 2 should be connected with
TargetProgLocal variable from Owner CAT along with their event data.
• For interfacing with AVEVA™ Batch Management, connect InIP and OutIP
variables of the new PhaseRealParam block with IPhase (ISc) adapter.
NOTE: To support the customization, the IPhase adapter should be modified
with new input and output parameter variables. Refer to the steps 1, page 64
to 3, page 65 to duplicate and modify the IPhase adapter like
MyPhaseManager as shown below:

66 EIO0000004853.02
Customization

The below image shows the final model of customized PhaseManager composite layer:

6 Click Save. As shown in the image below, ensure that the MyPhaseManager interface is
updated with new asset connections:

EIO0000004853.02 67
 Customization

7 The MyPhaseManager CAT is now ready for operation. For more information on how to
configure PhaseManager blocks and their functional modules, see the Example of Use,
page 53.

68 EIO0000004853.02
Supporting Objects
What’s in This Part
Basics ...........................................................................................................70
Composites ...................................................................................................84
Adapters........................................................................................................92
Composite Automation Types..........................................................................95

EIO0000004853.02 69
 Basics

Basics
What’s in This Chapter
decodePhaseState ........................................................................................70
encodePhasePara.........................................................................................72
encodeProcedureState ..................................................................................74
phaseExceptionHandling ...............................................................................77
S88StateControl............................................................................................80

decodePhaseState
General Description
The decodePhaseState block allows to decode structured Phase State
information to boolean data. It can be interfaced with the PhaseManager as
shown in the below image:

Interface Representation
The following image represents the decodePhaseState interface:

70 EIO0000004853.02
Basics

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

REQ State PhaseManager state update

request

Input Data Interface

The following table describes the input data interface:

Name Type Description

State SE.AppProcedure. PhaseManager state

PhaseStates

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

CNF IdleState; RunningState; PhaseManager decoded

HeldState; StoppedState; state update confirmation
PausedState; AbortedState;
CompleteState; HoldingState;
RestartingState; PausingState;
StoppingState; AbortingState;
InterlockedState

EIO0000004853.02 71
 Basics

Output Data Interface

The following table describes the output data interface:

Name Type Description

IdleState BOOL 1 = Phase in idle state

RunningState 1 = Phase in running state

HeldState 1 = Phase in held state

StoppedState 1 = Phase in stopped state

PausedState 1 = Phase in paused state

AbortedState 1 = Phase in aborted state

CompleteState 1 = Phase in completed
state
HoldingState 1 = Phase in holding state

RestartingState 1 = Phase in restarting

state
PausingState 1 = Phase in pausing state

StoppingState 1 = Phase in stopping

state
AbortingState 1 = Phase in aborting state

InterlockedState 1 = Phase in interlocked

state

encodePhasePara
General Description
The encodePhasePara block is used to encode the parameters for phase
management (Real data type) to a structured format. The encodePhasePara
block can encode a maximum of 15 parameters . An example of configuring
OutputParameters with PhaseManager is shown in the below image:

72 EIO0000004853.02
Basics

Interface Representation
The following image represents the encodePhasePara interface:

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

REQ Para1; Para2; Para3; Phase parameter update

Para4; Para5; Para6; request
Para7; Para8; Para9;
Para10; Para11;
Para12; Para13;
Para14; Para15

Input Data Interface

The following table describes the input data interface:

Name Type Description

Para1 REAL Phase parameter 01

Para2 Phase parameter 02

Para3 Phase parameter 03

Para4 Phase parameter 04

Para5 Phase parameter 05

Para6 Phase parameter 06

Para7 Phase parameter 07

Para8 Phase parameter 08

Para9 Phase parameter 09

Para10 Phase parameter 10

EIO0000004853.02 73
 Basics

Name Type Description

Para11 Phase parameter 11

Para12 Phase parameter 12

Para13 Phase parameter 13

Para14 Phase parameter 14

Para15 Phase parameter 15

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

CNF Out Phase parameter encode

confirmation

Output Data Interface

The following table describes the output data interface:

Name Type Description

Out SE.AppProcedure. Phase parameter encoded

PhaseParameters data

encodeProcedureState
General Description
The encodeProcedureState block is used to encode the connected sequence
state of Phase management to a structured format. This block is used along with
phaseStateControl basic block for Phase state management.

Interface Representation
The following image represents the encodeProcedureState interface:

74 EIO0000004853.02
Basics

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

REQ HoldingState; Procedure state update

RestartingState; request
AbortingState;
StoppingState;
RunningState

Input Data Interface

The following table describes the input data interface:

Name Type Description

RunningState UINT Running procedure state:

0 = Not Connected

1 = Stopped State

2 = Running State

4 = Held State

8 = Finished State

16 = Pausing State

32 = Paused State
HoldingState Holding procedure state:

0 = Not Connected

1 = Stopped State

2 = Running State

4 = Held State

8 = Finished State

16 = Pausing State

32 = Paused State
RestartingState Restarting procedure state:

0 = Not Connected

1 = Stopped State

2 = Running State

4 = Held State

8 = Finished State

16 = Pausing State

32 = Paused State

EIO0000004853.02 75
 Basics

Name Type Description

AbortingState Aborting procedure state:

0 = Not Connected

1 = Stopped State

2 = Running State

4 = Held State

8 = Finished State

16 = Pausing State

32 = Paused State
StoppingState Stopping procedure state:

0 = Not Connected

1 = Stopped State

2 = Running State

4 = Held State

8 = Finished State

16 = Pausing State

32 = Paused State

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

CNF_STATE ProceduresState Procedures state

confirmation
CNF ProceduresConnected Procedures connected
confirmation

Output Data Interface

The following table describes the output data interface:

76 EIO0000004853.02
Basics

Name Type Description

ProceduresState SE.AppProcedure. All procedures state in

ProceduresStates data structure:

0 = Not Connected

1 = Stopped State

2 = Running State

4 = Held State

8 = Finished State

16 = Pausing State

32 = Paused State
ProceduresConnected WORD Bitwise procedure
connected status (1 =
Connected, 0 = Not
connected) (Bit0 =
Running procedure, Bit1 =
Holding procedure, Bit2 =
Restarting procedure, Bit3
= Aborting procedure, Bit4
= Stopping procedure)

phaseExceptionHandling
General Description
The phaseExceptionHandling basic functional block manages the key role of
automated exception sequence management for PhaseManager if a failure is
detected. It commands the PhaseManager to automatically execute the exception
sequences such as, Holding , Stopping or Aborting ( user definition) if a failure
is detected.

Interface Representation
The following image represents the phaseExceptionHandling interface:

EIO0000004853.02 77
 Basics

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

REQ_FAIL FailCond Request for fail condition

REQ_EXCEPTION ExceptionCond Request for exception

condition
REQ_STATE PhaseState Request for phase state

REQ_CMD PhaseCommand Request for command

execution

78 EIO0000004853.02
Basics

Input Data Interface

The following table describes the input data interface:

Name Type Description

FailCond BOOL 1 = Fail condition active

ExceptionCond UINT Procedure to execute while
exception active:

0 = Holding

1 = Stopping

2 = Aborting

PhaseState SE.AppProcedure. Phase state:

PhaseStates
0 = Undefined

1 = IdleState

2 = RunningState

3 = HeldState

4 = StoppedState

5 = PausedState

6 = AbortedState

7 = CompleteState

8 = HoldingState

9 = RestartingState

10 = PausingState

11 = StoppingState

12 = AbortingState

13 = InterlockedState
PhaseCommand SE.AppProcedure. Phase command:
PhaseCommands
0 = Undefined

1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

128 = Abort

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

CNF PhaseCmd Command execution

confirmation

EIO0000004853.02 79
 Basics

Output Data Interface

The following table describes the output data interface:

Name Type Description

PhaseCmd SE.AppProcedure.PhaseCommands Phase command

considering exception
selection:

0 = Undefined

1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

128 = Abort

S88StateControl
General Description
The S88StateControl basic function block is a state machine block of
PhaseManager functional module. This block makes transitions from one state to
another. When a new command with mode and a strategy (if available) is
provided, the process moves to Running state and performs its sequence
operations. Further a state transitions is made with respect to other commands
such as HOLD, PAUSE, STOP, ABORT etc. It executes the exception sequences
such as Holding, Stopping or Aborting (user defined) when a failure is detected.
For the above mentioned sequence operations, the S88StateControl block
converts all the commands received from PhaseManager to the operational
commands for the sequence library. Once the Running sequence is completed,
the state is confirmed as completed. When the user initiates a RESET command,
the phase is moved to Ready i.e, the PhaseManager is ready for the next
operation.

Interface Representation
The following image represents the S88StateControl interface:

80 EIO0000004853.02
Basics

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

INIT_COND InitialCond Initial condition request

REQ_CONFIG AutoReset Request for configuration

update

REQ_STATE ProceduresState Request for procedures

state
REQ_CMD PhaseCmd Request for command
execution

EIO0000004853.02 81
 Basics

Input Data Interface

The following table describes the input data interface:

Name Type Description

InitialCond BOOL 1 = Initial condition not

satisfied
AutoReset BOOL 1 = Auto reset enabled,
State change from final
transient states to Idle
happens automatically

ProceduresState SE.AppProcedure. All procedures state in data

ProceduresStates structure:

0 = Not Connected

1 = Stopped State

2 = Running State

4 = Held State

8 = Finished State

16 = Pausing State

32 = Paused State
PhaseCmd SE.AppProcedure. Phase command:
PhaseCommands
0 = Undefined

1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

128 = Abort

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

CNF PhaseState Phase state confirmation

CNF_CMD ProcedureName; ProcedureCmd Phase command
confirmation

Output Data Interface

The following table describes the output data interface:

82 EIO0000004853.02
Basics

Name Type Description

PhaseState SE.AppProcedure.PhaseStates Phase state:

0 = Undefined,

1 = IdleState

2 = RunningState

3 = HeldState

4 = StoppedState

5 = PausedState

6 = AbortedState

7 = CompleteState

8 = HoldingState,

9 = RestartingState

10 = PausingState

11 = StoppingState

12 = AbortingState,

13 = InterlockedState
ProcedureName STRING[40] Procedure name to be
executed
ProcedureCmd UINT Command to the
procedure:

1 = Start

2 = Stop

4 = Hold

8 = Resume

16 = Pause

EIO0000004853.02 83
 Composites

Composites
What’s in This Chapter
phaseCommandSel.......................................................................................84
seqConnect ..................................................................................................88
stateManager................................................................................................88

phaseCommandSel
General Description
The phaseCommandSel composite block manages the command, mode, and
strategy selections for the PhaseManager CAT, since the PhaseManager can
receive commands from both Operator owner as well as Program owners
(Program Local).

Interface Representation
The following image represents the phaseCommandSel interface:

84 EIO0000004853.02
Composites

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

INIT — Initialization Request

REQ_SEL Sel1; Sel2 Source selection request

REQ1_MODE Mode1 Source 1 request for mode

REQ2_MODE Mode2 Source 2 request for mode

REQ_STRATEGY1 Strategy1 Source 1 request for

strategy

REQ_STRATEGY2 Strategy2 Source 2 request for

strategy

REQ1_CMD PhaseCmd1 Source 1 request for

command
REQ2_CMD PhaseCmd2 Source 2 request for
command
REQ1_MAN ManStepId1 Source 1 request for manual
step selection

REQ2_MAN ManStepId2 Source 2 request for manual

step selection

REQ1_SEMISTART SemiStart1 Source 1 request for semi

start command
REQ2_SEMISTART SemiStart2 Source 2 request for semi
start command
REQ_PROCEDURE ProcedureName Request for procedure name

REQ_CONFIG ExceptionMode Request for phase

configuration update

Input Data Interface

The following table describes the input data interface:

Name Type Description

Sel1 BOOL 1 = Source 1 is selected

Mode1 UINT Mode selection from source
1:

0 = Auto

1 = Semi-Auto

2 = Manual
Strategy1 Strategy selection from
source 1

EIO0000004853.02 85
 Composites

Name Type Description

PhaseCmd1 Phase command from

source 1:

0 = Undefined

1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

128 = Abort
ManStepId1 Manual step id selection
from source 1
SemiStart1 BOOL Semi start command from
source 1
Sel2 1 = Source 2 is selected
Mode2 VTQUINT Mode selection from source
2:

0 = Auto

1 = Semi-Auto

2 = Manual
Strategy2 Strategy selection from
source 2
PhaseCmd2 SE.AppProcedure. Phase command from
PhaseCommands source 2:

0 = Undefined

1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

128 = Abort
ManStepId2 VTQUINT Manual step id selection
from source 2
SemiStart2 VTQBOOL Semi start command from
source 2
ProcedureName STRING[40] Procedure name to be
executed
AutoReset BOOL 1 = Auto reset enabled,
State change from final
transient states to Idle
happens automatically

ExceptionMode BOOL Mode selection for exception

procedure:

0 = Auto

1 = Semi-Auto

86 EIO0000004853.02
Composites

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

INITO — Initialization confirmation

CNF_MODE Mode Mode confirmation

CNF_STRATEGY Strategy Strategy selection

confirmation
CNF_CMD PhaseCmd Command execution
confirmation
CNF_MAN ManualStepId Confirmation for manual
step selection

CNF_STEPID MsgTotalStepId; EnablePause Confirmation for step id

CNF_TRANSID StepExceeded Confirmation for step

exceed condition
CNF_TIME RunningTime Confirmation for elapsed
time
CNF_RESET EnAutoReset Confirmation for Auto
Reset enable

Output Data Interface

The following table describes the output data interface:

Name Type Description

Mode UINT Mode selection:

0 = Auto

1 = Semi-Auto

2 = Manual
Strategy Phase strategy selection

PhaseCmd SE.AppProcedure.PhaseCommands Phase command:

0 = Undefined

1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

128 = Abort
ManualStepId UINT Manual step id selection

MsgTotalStepId STRING Total step id for manual

step selection (comma
separated)

StepExceeded BOOL Step exceed information

EnablePause 1 = Pause command

enable, Stable step is
detected

EIO0000004853.02 87
 Composites

Name Type Description

RunningTime REAL Procedure running time

EnAutoReset BOOL 1 = Auto Reset enabled

from source 1
(functionality is disabled
for source 2)

seqConnect
General Description
The seqConnect composite block connects with the objects in the SE.
AppSequence library, that accepts the status informations such as Sequence
States, Step Id, and Running Time information and in return it sends Sequence
Commands, Mode, and Manual Step Id . The seqConnect composite block is
the wrapper of basic SeqHead composite block.

Interface Representation
The following image represents the seqConnect interface:

Outputs
Adapter Outputs
The following table describes the adapter outputs:

Name Type Description

ISeqChain SE.AppSequence.ISeqChain Output interface for passing

sequence command
information

stateManager
General Description
The stateManager composite block acts a wrapper for phaseStateControl and
phaseExceptionHandling basic blocks. It receives commands from the
PhaseManager CAT and preforms sequence operations and state management.
It also provides the operational commands for the sequences configured with the
PhaseManager.

88 EIO0000004853.02
Composites

Interface Representation
The following image represents the stateManager interface:

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

INIT — Initialization Request

INIT_COND InitCond Initial condition request

REQ_FAIL Failure; InitCond Request for fail condition

REQ_CMD PhaseCmd Request for command

execution
REQ_EXCEPTION ExceptionProcedure Request for exception
condition
REQ_RESET AutoReset Request to update auto
reset functionality

EIO0000004853.02 89
 Composites

Input Data Interface

The following table describes the input data interface:

Name Type Description

Failure BOOL 1 = Fail condition active

InitCond 1 = Initial condition not
satisfied
PhaseCmd SE.AppProcedure. Phase command:
PhaseCommands
0 = Undefined

1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

128 = Abort
ExceptionProcedure UINT Procedure to execute while
exception active:

0 = Holding

1 = Stopping

2 = Aborting

AutoReset BOOL 1 = Auto reset enabled,

State change from final
transient states to Idle
happens automatically

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

INITO — Initialization confirm

CNF PhaseState Phase state confirmation
CNF_PROCEDURE ProcedureName Procedure name
confirmation
CONFIG_ERROR ConfigError Configuration error
confirmation

Output Data Interface

The following table describes the output data interface:

90 EIO0000004853.02
Composites

Name Type Description

PhaseState SE.AppProcedure.PhaseStates Phase state:

0 = Undefined

1 = IdleState

2 = RunningState

3 = HeldState

4 = StoppedState

5 = PausedState

6 = AbortedState

7 = CompleteState

8 = HoldingState

9 = RestartingState

10 = PausingState

11 = StoppingState

12 = AbortingState

13 = InterlockedState
ProcedureName STRING[40] Procedure name to be
executed
ConfigError BOOL 1 = Configuration error
detected (Running
sequence is not
connected)

EIO0000004853.02 91
 Adapters

Adapters
What’s in This Chapter
IPhase..........................................................................................................92

IPhase
General Description
The IPhase object enables the bidirectional transfer of phase mode, strategy,
command, and parameter informations from PhaseManager to upstream
functional bock PLI. This results in establishing a seamless communication
between them.

Interface Representation
The following image represents the IPhase interface:

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

CNF_MODE CurrentMode Phase mode confirmation

CNF_STRATEGY CurrentStartegy Phase strategy confirmation

CNF_STATE CurrentState Phase state confirmation

CNF_TRANSID StepExceeded Confirmation for step exceed

condition
CNF_OP OutputParameters Confirmation for output
parameters

92 EIO0000004853.02
Adapters

Input Data Interface

The following table describes the input data interface:

Name Type Description

CurrentMode VTQUINT Current phase mode for

running sequence (0 = Auto,
1 = SemiAuto, 2 = Manual)

CurrentStartegy Current phase strategy

CurrentState SE.AppProcedure. Current phase state:

PhaseStates
0 = Undefined

1 = IdleState

2 = RunningState

3 = HeldState

4 = StoppedState

5 = PausedState

6 = AbortedState

7 = CompleteState

8 = HoldingState

9 = RestartingState

10 = PausingState

11 = StoppingState

12 = AbortingState

13 = InterlockedState
StepExceeded VTQBOOL Step exceed information

OutputPara SE.AppProcedure. Output parameters

PhaseParameters (Feedback parameters)

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

REQ_MODE Mode Request to update mode

REQ_STRATEGY Strategy Request to update

strategy

REQ_CMD Command Request to update

command
REQ_SEMISTART SemiStart Request for semi start
command
REQ_MAN ManStepId Request to update manual
step id command

REQ_IP InputPara Request to update input

parameter setpoint

Output Data Interface

The following table describes the output data interface:

EIO0000004853.02 93
 Adapters

Name Type Description

Mode VTQUINT Phase mode selection for

running sequence:

0 = Auto

1 = Semi-Auto

2 = Manual
Strategy Phase strategy selection

Command SE.AppProcedure.PhaseCommands Phase command:

0 = Undefined

1 = Start

2 = Hold

4 = Restart

8 = Stop

16 = Reset

32 = Pause

64 = Resume

128 = Abort
SemiStart VTQBOOL Semi start command
ManStepId VTQUINT Manual step id selection

InputPara SE.AppProcedure. Input parameters

PhaseParameters (Setpoint)

94 EIO0000004853.02
Composite Automation Types

Composite Automation Types

What’s in This Chapter
PhaseInterface..............................................................................................95
PhaseRealParam ..........................................................................................98

PhaseInterface
General Description
This chapter describes the components that provide the functionality, control
services, and Supervision functions of the PhaseInterface functional block.

Overview
The PhaseInterface functional module is used to interface the PhaseManager
CAT with external batching interfaces such as AVEVATM Batch Management.
The PhaseInterface accepts commands from external interfaces and transfer it to
the PhaseManager and in return it updates statuses from the PhaseManager to
external batching interfaces.

Interface Representation
The following image represents the PhaseInterface interface:

Outputs
Output Event Interface
No output event interface.

Output Data Interface

No output data interface.

EIO0000004853.02 95
 Composite Automation Types

Plugs
The following table describes the plugs:

Name Type Description

ISc SE.AppProcedure.IPhase Sequence control adapter

Offline Parametrization
No offline parametrization.

OPCUA
The following table describes the OPCUA:

Path Type Access level Display name Min. Description

Sampl.
Interval
IThis. UInt16 Read-Only Current- 0 Current mode
CurrentMode Mode of phase:

0 = Auto

1 = Semi-Auto

2 = Manual
IThis. UInt16 Current- 0 Current phase
CurrentStart- Startegy strategy
egy selection

IThis. Boolean IdleState 0 1 = Phase in

IdleState idle state
IThis. Boolean Runni- 0 1 = Phase in
RunningState ngState running state

IThis. Boolean HeldState 0 1 = Phase in

HeldState held state
IThis. Boolean Stopped- 0 1 = Phase in
StoppedState State stopped state

IThis. Boolean Paused- 0 1 = Phase in

PausedState State paused state

IThis. Boolean Aborted- 0 1 = Phase in

AbortedState State aborted state
IThis. Boolean CompleteS- 0 1 = Phase in
CompleteState tate completed state

IThis. Boolean Holding- 0 1 = Phase in

HoldingState State holding state

IThis. Boolean Restar- 0 1 = Phase in

Restarting- tingState restarting state
State
IThis. Boolean Pausing- 0 1 = Phase in
PausingState State pausing state

IThis. Boolean Stopping- 0 1 = Phase in

StoppingState State stopping state

IThis. Boolean Aborting- 0 1 = Phase in

AbortingState State aborting state

IThis. Boolean Interloc- 0 1 = Phase in

Interlocked- kedState interlocked
State state
IThis. Boolean StepExcee- 0 Step exceeded
StepExceeded ded information
(Can be used

96 EIO0000004853.02
Composite Automation Types

Path Type Access level Display name Min. Description

Sampl.
Interval
for semi
commands in
Semi-Auto
mode)

IThis.OP01 Float OP01 0 Output

parameter 01

IThis.OP02 Float OP02 0 Output

parameter 02

IThis.OP03 Float OP03 0 Output

parameter 03

IThis.OP04 Float OP04 0 Output

parameter 04

IThis.OP05 Float OP05 0 Output

parameter 05

IThis.OP06 Float OP06 0 Output

parameter 06

IThis.OP07 Float OP07 0 Output

parameter 07

IThis.OP08 Float OP08 0 Output

parameter 08

IThis.OP09 Float OP09 0 Output

parameter 09

IThis.OP10 Float OP10 0 Output

parameter 10

IThis.OP11 Float OP11 0 Output

parameter 11

IThis.OP12 Float OP12 0 Output

parameter 12

IThis.OP13 Float OP13 0 Output

parameter 13

IThis.OP14 Float OP14 0 Output

parameter 14

IThis.OP15 Float OP15 0 Output

parameter 15

IThis. Boolean Read- Write CmdStart 0 1 = Phase start

CmdStart command
IThis.CmdHold Boolean CmdHold 0 1 = Phase hold
command
IThis. Boolean CmdRestart 0 1 = Phase
CmdRestart restart
command
IThis.CmdStop Boolean CmdStop 0 1 = Phase stop
command
IThis. Boolean CmdReset 0 1 = Phase reset
CmdReset command
IThis. Boolean CmdPause 0 1 = Phase
CmdPause pause
command
IThis. Boolean CmdResume 0 1 = Phase
CmdResume resume
command
IThis. Boolean CmdAbort 0 1 = Phase abort
CmdAbort command
IThis.CmdSemi Boolean CmdSemi 0 1 = Phase semi
command
IThis. UInt16 Strategy 0 Strategy for
Strategy phase
operation (Upto

EIO0000004853.02 97
 Composite Automation Types

Path Type Access level Display name Min. Description

Sampl.
Interval
a max of 16
strategies are
allowed)

IThis.Mode UInt16 Mode 0 Mode selection:

0 = Auto

1 = Semi-Auto

2 = Manual
IThis. UInt16 ManualSte- 0 Step ID for
ManualStepId pId manual
operation

IThis.IP01 Float IP01 0 Input parameter

01
IThis.IP02 Float IP02 0 Input parameter
02
IThis.IP03 Float IP03 0 Input parameter
03
IThis.IP04 Float IP04 0 Input parameter
04
IThis.IP05 Float IP05 0 Input parameter
05
IThis.IP06 Float IP06 0 Input parameter
06
IThis.IP07 Float IP07 0 Input parameter
07
IThis.IP08 Float IP08 0 Input parameter
08
IThis.IP09 Float IP09 0 Input parameter
09
IThis.IP10 Float IP10 0 Input parameter
10
IThis.IP11 Float IP11 0 Input parameter
11
IThis.IP12 Float IP12 0 Input parameter
12
IThis.IP13 Float IP13 0 Input parameter
13
IThis.IP14 Float IP14 0 Input parameter
14
IThis.IP15 Float IP15 0 Input parameter
15

PhaseRealParam
General Description
This chapter describes the components that provide the functionality, control
services, and Supervision functions of the PhaseRealParam functional block.

Overview
The PhaseRealParam functional block handles the parameter management
functionalities for PhaseManager CAT. It accepts the input parameter setpoints
from Strategy Selection faceplates and expose at PhaseManager CAT. The

98 EIO0000004853.02
Composite Automation Types

users can utilize these data for the phase management operations. In return,
PhaseRealParam reads the output parameter process values for the data
management at the supervision levels as well as external interfaces.

Interface Representation
The following image represents the PhaseRealParam interface:

Inputs
Input Event Interface
The following table describes the input event interface:

Name With Description

INIT — Initialization Request

REQ_SEL Sel1; Sel2 Request to update selection

parameters

REQ_IP InIP Request to update input

parameters

REQ_OP InOP Request to update output

parameters

Input Data Interface

The following table describes the input data interface:

Name Type Description

Sel1 BOOL 1 = Selection of

InputParameters from
operator owner

Sel2 BOOL 1 = Selection of

InputParameters from
program owner

InIP SE.AppProcedure. Incoming InputParameters

PhaseParameters from program owner

InOP SE.AppProcedure. Incoming OutputParameters

PhaseParameters

EIO0000004853.02 99
 Composite Automation Types

Outputs
Output Event Interface
The following table describes the output event interface:

Name With Description

INITO — Initialization confirmation

CNF_IP OutIP Confirmation of updates in
InputParameters

CNF_OP OutOP Confirmation of updates in

OutputParameters

Output Data Interface

The following table describes the output data interface:

Name Type Description

OutIP SE.AppProcedure. Outgoing InputParameters

PhaseParameters
OutOP Outgoing
OutputParameters

Offline Parametrization
The following table describes the offline parametrization:

Path Type Default value Description

IThis.IP01 REAL 0.0 Input Parameter 1

IThis.IP02 REAL 0.0 Input Parameter 2

IThis.IP03 REAL 0.0 Input Parameter 3

IThis.IP04 REAL 0.0 Input Parameter 4

IThis.IP05 REAL 0.0 Input Parameter 5

IThis.IP06 REAL 0.0 Input Parameter 6

IThis.IP07 REAL 0.0 Input Parameter 7

IThis.IP08 REAL 0.0 Input Parameter 8

IThis.IP09 REAL 0.0 Input Parameter 9

IThis.IP10 REAL 0.0 Input Parameter 10

IThis.IP11 REAL 0.0 Input Parameter 11

IThis.IP12 REAL 0.0 Input Parameter 12

IThis.IP13 REAL 0.0 Input Parameter 13

IThis.IP14 REAL 0.0 Input Parameter 14

IThis.IP15 REAL 0.0 Input Parameter 15

OPCUA
The following table describes the OPCUA:

100 EIO0000004853.02
Composite Automation Types

Path Type Access level Display name Min. Description

Sampl.
Interval
IThis.OP01 Float Readonly OP01 0 Output
parameter 01

IThis.OP02 Float OP02 0 Output

parameter 02

IThis.OP03 Float OP03 0 Output

parameter 03

IThis.OP04 Float OP04 0 Output

parameter 04

IThis.OP05 Float OP05 0 Output

parameter 05

IThis.OP06 Float OP06 0 Output

parameter 06

IThis.OP07 Float OP07 0 Output

parameter 07

IThis.OP08 Float OP08 0 Output

parameter 08

IThis.OP09 Float OP09 0 Output

parameter 09

IThis.OP10 Float OP10 0 Output

parameter 10

IThis.OP11 Float OP11 0 Output

parameter 11

IThis.OP12 Float OP12 0 Output

parameter 12

IThis.OP13 Float OP13 0 Output

parameter 13

IThis.OP14 Float OP14 0 Output

parameter 14

IThis.OP15 Float OP15 0 Output

parameter 15

IThis.IP01 Float Read- Write IP01 0 Input parameter

01
IThis.IP02 Float IP02 0 Input parameter
02
IThis.IP03 Float IP03 0 Input parameter
03
IThis.IP04 Float IP04 0 Input parameter
04
IThis.IP05 Float IP05 0 Input parameter
05
IThis.IP06 Float IP06 0 Input parameter
06
IThis.IP07 Float IP07 0 Input parameter
07
IThis.IP08 Float IP08 0 Input parameter
08
IThis.IP09 Float IP09 0 Input parameter
09
IThis.IP10 Float IP10 0 Input parameter
10
IThis.IP11 Float IP11 0 Input parameter
11
IThis.IP12 Float IP12 0 Input parameter
12
IThis.IP13 Float IP13 0 Input parameter
13

EIO0000004853.02 101
 Composite Automation Types

Path Type Access level Display name Min. Description

Sampl.
Interval
IThis.IP14 Float IP14 0 Input parameter
14
IThis.IP15 Float IP15 0 Input parameter
15

102 EIO0000004853.02
 Printed in:
Schneider Electric
35 rue Joseph Monier
92500 Rueil Malmaison - France
+ 33 (0) 1 41 29 70 00

Schneider Electric
35 rue Joseph Monier
92500 Rueil Malmaison
France
+ 33 (0) 1 41 29 70 00
www.se.com

As standards, specifications, and design change from time to time,

please ask for confirmation of the information given in this publication.

© 2023 – 2023 Schneider Electric. All rights reserved.

EIO0000004853.02