PlantStruxure PES Configuration v4.2 2016-09-28 Vol1

Manual Release 4
PlantStruxure PES Configuration

Training Manual
PlantStruxure PES V4.2
Volume 1
DISCLAIMER
Schneider Electric makes no representations or warranties with respect to this manual and, to the maximum extent permitted by law,
expressly limits its liability for breach of any warranty that may be implied to the replacement of this manual with another. Furthermore,
Schneider Electric reserves the right to revise this publication at any time without incurring an obligation to notify any person of the revision.
The information provided in this documentation contains general descriptions and/or technical characteristics of the performance of the
products contained herein. This documentation is not intended as a substitute for and is not to be used for determining suitability or reliability
of these products for specific user applications. It is the duty of any such user or integrator to perform the appropriate and complete risk
analysis, evaluation and testing of the products with respect to the relevant specific application or use thereof. Neither Schneider Electric nor
any of its affiliates or subsidiaries shall be responsible or liable for misuse of the information that is contained herein. If you have any
suggestions for improvements or amendments or have found errors in this publication, please notify us.
All pertinent state, regional, and local safety regulations must be observed when installing and using this product. For reasons of safety and
to help ensure compliance with documented system data, only the manufacturer should perform repairs to components.
When devices are used for applications with technical safety requirements, the relevant instructions must be followed.
Failure to use Schneider Electric software or approved software with our hardware products may result in injury, harm, or improper
operating results.
Failure to observe this information can result in injury or equipment damage.
© 2012 - 2016 Schneider Electric. All rights reserved.
The contents of this manual are proprietary to Schneider Electric and all rights, including copyright, are reserved by Schneider Electric. No
part of this document may be reproduced in any form or by any means, electronic or mechanical, including photocopying, without express
written permission of Schneider Electric.
PlantStruxure PES Configuration Training Manual
INTRODUCTION AND LEGAL NOTICE
Your purchase of this official PlantStruxure PES Configuration Training Manual entitles you to undertake the PlantStruxure PES
Configuration training course.
Satisfactory completion of the course evaluation is mandatory for you to obtain a Schneider Electric certificate of completion of the training
course.
Schneider Electric will not accept any liability for action taken in reliance on this training manual.
TRADEMARKS
Schneider Electric has made every effort to supply trademark information about company names, products and services mentioned in this
manual. Trademarks shown below were derived from various sources.
PlantStruxure PES, Vijeo Citect and Unity Pro are trademarks owned by Schneider Electric or its affiliated companies. All other trademarks
are the property of their respective owners.
Excel, Windows and Windows XP are either registered trademarks or trademarks of Microsoft® Corporation in the United States and/or
other countries.
VirtualBox is a registered trademark of Oracle Corporation in the United States and other countries.
General Notice:
Some product names used in this manual are used for identification purposes only and may be trademarks of their respective companies.
Validity Note
The present documentation is intended for qualified technical personnel responsible for the implementation, operation and maintenance of
the products described. It contains information necessary for the proper use of the products.
About Us
Members of Schneider Electric’s team of Instructional Designers have tertiary qualifications in Education, Educational Course Development
and are also experienced Instructors. Currently, the team is supporting a range of Schneider Electric courses in multiple languages and
multiple software environments.
Authors
David Heath, Richard Irons
Contributors
Eric Coudurier, Pascal Lavallee, Rodrigo Romero, Johnatan Feuillye, Warwick Black, Olivier Guthmann
November 2016 Edition for PlantStruxure PES V4.2

Manual Release 4
ii PlantStruxure PES V4.2 November 2016

Safety Information
Important PLEASE NOTE
Information
Read these instructions carefully, and look at the equipment to become familiar
with the device before trying to install, operate, 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 alert messages that
follow this symbol to avoid possible injury or death.
DANGER
DANGER indicates an imminently hazardous situation which, if not avoided,
will result in death or serious injury.
WARNING
WARNING indicates a potentially hazardous situation which, if not avoided,
could result in death or serious injury.
CAUTION
CAUTION indicates a potentially 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.
PlantStruxure PES Configuration Manual Release 4 iii

Safety Information (cont.)
Important PLEASE NOTE
Information
(cont.) 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.
iv PlantStruxure PES V4.2 November 2016

Before you Do not use this product on machinery lacking effective point-of-operation
Begin guarding. Lack of effective point-of-operation guarding on a machine can result in
serious injury to the operator of that machine.
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.
PlantStruxure PES Configuration Manual Release 4 v

Before you Ensure that appropriate safeties and mechanical/electrical interlocks related to
Begin (cont.) 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 Before using electrical control and automation equipment for regular operation
Test 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 be made and that enough time is allowed to perform complete and
satisfactory testing.
CAUTION
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 injury or equipment
damage.
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.
vi PlantStruxure PES V4.2 November 2016

Startup and Verify that the completed system is free from all short circuits and temporary
Test (cont.) 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 The following precautions are from the NEMA Standards Publication ICS 7.1-
Adjustments 1995 (English version prevails):
 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 actually required by the operator should
be accessible to the operator. Access to other controls should be restricted to
prevent unauthorized changes in operating characteristics.
PlantStruxure PES Configuration Manual Release 4 vii

Before the Course Begins
Scope of this This training manual is a supplement to the authorised training. In order to make
Training proper use of the software students should also refer to the documentation that has
Manual been provided with the product such as the Help Files, User Guides or Knowledge
Base.
The graphics displaying screen captures were taken using the Windows® 7
operating system. If students are running a different version of Windows then
screen images may differ slightly from those shown in the training manual.
Some screen captures may have been taken from beta versions of the software and
may vary slightly from release screen captures.
viii PlantStruxure PES V4.2 November 2016

Course Overview
Course By the completion of this training course the student will:
Objectives
 Be able to create a valid PlantStruxure PES System.
 Be able to deploy the project to the Control and Supervision participants and
execute them.
 Be able to modify existing Systems to add or remove features.
 Manage the backup and restoration of existing PlantStruxure PES projects
using the Import and Export tools along with the database backup utility.
Target The PlantStruxure PES Configuration training course is an integral part of the
Audience complete Educational Services curriculum. This course is designed for:
 Users who are new to PlantStruxure PES

 Users who have moderate PLC programming experience using Unity Pro and
who have some experience developing SCADA projects using Vijeo Citect
 Users who desire to integrate the development of control systems with a
single tool
Note:
This course is designed specifically for users with previous PLC programming
experience using Unity Pro, therefore the content is set at a level that is most
suited to reasonably moderately experienced programmers. In addition,
significant knowledge of Vijeo Citect is also expected.
Prerequisite It is expected that trainees will be familiar with:

Knowledge
 The concepts of PACs
 The concepts of industrial automation
 Microsoft Windows
 Unity Pro
 Vijeo Citect
Participants who have attended the Configuration courses for Unity Pro and Vijeo
Citect could reasonably be expected to have suitable pre-requisite knowledge.
Support If support or additional information about any concepts or products in the course
is required, students should ask the Instructor who will either address the question
or obtain additional technical assistance as required.
PlantStruxure PES Configuration Manual Release 4 ix

Course Overview (cont.)
Course The training course will take five days to complete. The following program
Program outlines the topics that will be covered on each day:
Day Topics
Introduce PlantStruxure PESt
1  Introduction to PlantStruxure PES

 Creation of a Simple System
 Create an Application
 Create a PAC Topology
 Create a Control Projec
2  Simulate a PAC
 Create the Computer Topology and Network
 Create a Supervision Project
 Deploy the Control Project
 Deploy a Supervision Project
 Runtime Services
Extend PlantStruxure PES
3  Online Modifications
 Add New Functionality
 Add New Hardware
 Redundant M580
4  Introduce the General Purpose Library
 Manage Changes
 Sequence Control
 Multi-User Configuration
5  Consolidation Workshop
 Additional Content
Course Assets For this course, in addition to the standard PlantStruxure PES software, the
following files are required.
SimpleSystem.dbk Backup for use in database backup/restore.
EmptyDatabase.dbk Backup of empty database
Training.ctz Common module for all PlantStruxure PES training

courses.
x PlantStruxure PES V4.2 November 2016

Conventions Used in this Manual
Objectives These are the skills to be achieved by the end of each chapter. An overview
providing a brief synopsis of the topic begins each section. Often, examples are
given to illustrate the conceptual overview.
Example -
The configuration environment consists of several toolbars, browser windows and
programming editors. This chapter introduces the user to the configuration
environment using an example project with pre-defined elements.
Exercises After a concept is explained students will be given exercises that practice the
skills just learned. These exercises begin by explaining the general concept of
each exercise and then step-by-step procedures are listed to guide students
through each exercise.
Example -
Paste an object from a library onto a test page called Utility.
1 Run the Milk_Upgrade project then trigger and view some

alarms.
i. Use the following template settings:
User Input Whenever information is to be typed into a field or dialog box it will be written in
this font:
KETTLE_TEMP/25
Note that some exercises will show a fragment of information already typed into a
PlantStruxure PES screen and then ask students to add extra lines of
configuration. In this instance, the previously entered material will be given to
the student as light grey italic text.
KETTLE_TEMP/25
OVEN_TEMP/5
PlantStruxure PES Configuration Manual Release 4 xi

Conventions Used in this Manual (cont.)
Hints & Tips This heading will provide students with useful or helpful information that will
make configuring the project easier.
Example -
Hints & Tips:
To go to the next field, use the mouse cursor or press the TAB key.
Note A note will refer to a feature which may not be obvious at first glance but
something that should always be kept in mind.
Example -
Note:
Any events named GLOBAL are enabled automatically when events are enabled.
Menus and Text separated by the double arrow symbol “»” indicates that students are to
Menu Options select a menu.
Example -
File » New…
Open a menu “File” then select the menu option “New…”
Horizontal and Text written this way indicates the Horizontal then the (Vertical) tab is to be
Vertical Tabs selected.
Example -
Appearance (General)
xii PlantStruxure PES V4.2 November 2016

Conventions Used in this Manual (cont.)
See Also Text written in this way indicates further references about the current topic.
Example -
See Also:
For further information about Templates, see PlantStruxure PES Help - Using
Page Templates.
Further This heading describes topics that are covered in more advanced courses.
Training
Example -
Further Training:
Trend Table Maths is a topic in the Customisation and Design Course.
PlantStruxure PES Configuration Manual Release 4 xiii

Table of Contents
CHAPTER 1: PLANTSTRUXURE PES AT A GLANCE ................................................... 1-1

Introduction ................................................................................................................ 1-1
What is PlantStruxure PES? ....................................................................................... 1-2
PlantStruxure PES Architecture ................................................................................. 1-4
Start the Software Package....................................................................................... 1-13
CHAPTER 2: MANAGE THE PLANTSTRUXURE PES ENVIRONMENT ......................... 2-1

Introduction ................................................................................................................ 2-1
What is a System? ...................................................................................................... 2-2
The Various Explorers ............................................................................................... 2-3
A Very Simple Implementation ................................................................................. 2-8
Manage the Underlying Database Environment ........................................................ 2-9
Upgrade from Previous Versions ............................................................................. 2-18
CHAPTER 3: DEVELOP THE SYSTEM STRUCTURE ..................................................... 3-1

Introduction ................................................................................................................ 3-1
The Engineering Client .............................................................................................. 3-2
Systems and Folders ................................................................................................... 3-3
Steps to Complete the Course .................................................................................. 3-12
CHAPTER 4: CREATE THE APPLICATION ................................................................... 4-1

Introduction ................................................................................................................ 4-1
A Structural View of the System................................................................................ 4-3
The Training Scenario ................................................................................................ 4-7
PlantStruxure PES Folder Structures ....................................................................... 4-13
Instantiation of Objects ............................................................................................ 4-22
Object Linkages........................................................................................................ 4-49
CHAPTER 5: CREATE THE PAC TOPOLOGY.............................................................. 5-1

Introduction ................................................................................................................ 5-1
The Scenario............................................................................................................... 5-3
Topology Folders ....................................................................................................... 5-5
Create Controllers ...................................................................................................... 5-9
Convert to PlantStruxure PES Objects ..................................................................... 5-16
CHAPTER 6: CREATE THE CONTROL PROJECT ......................................................... 6-1

Introduction ................................................................................................................ 6-1
Create a Control Project ............................................................................................. 6-4
Assign Facets............................................................................................................ 6-10
Generate ................................................................................................................... 6-22
Refine the Control Project ........................................................................................ 6-25
PlantStruxure PES Configuration Manual Release 4 xv

CHAPTER 7: FINALISE THE CONTROL PROJECT ....................................................... 7-1
Overview .................................................................................................................... 7-1
The Control Executable.............................................................................................. 7-3
Mapping ..................................................................................................................... 7-7
Build the Control Project.......................................................................................... 7-18
Deploy the Control Project ....................................................................................... 7-23
CHAPTER 8: DEFINE THE COMPUTERS AND NETWORKS .......................................... 8-1

Introduction ................................................................................................................ 8-1
Station Nodes ............................................................................................................. 8-3
Station Node Roles ..................................................................................................... 8-7
Networks .................................................................................................................. 8-15
CHAPTER 9: CREATE THE SUPERVISION PROJECT ................................................... 9-1

Introduction ................................................................................................................ 9-1
Create a Supervision Project ...................................................................................... 9-4
Assign Supervision Facets ......................................................................................... 9-7
Generate the Supervision Project ............................................................................. 9-16
Refine the Supervision Project ................................................................................. 9-35
CHAPTER 10: FINALISE THE SUPERVISION PROJECT................................................ 10-1

Introduction .............................................................................................................. 10-1
The Supervision Executable ..................................................................................... 10-3
Map the Supervision Services .................................................................................. 10-6
Map the I/O Devices .............................................................................................. 10-10
Build the Supervision Project................................................................................. 10-15
Construct the Engineering Station.......................................................................... 10-17
CHAPTER 11: THE SIMULATION ENVIRONMENT ...................................................... 11-1

Overview .................................................................................................................. 11-1
The Simulation Environment ................................................................................... 11-4
Deploy for Simulation .............................................................................................. 11-9
CHAPTER 12: DEPLOY AND RUN THE SUPERVISION PROJECT ................................. 12-1
Introduction .............................................................................................................. 12-1
Create a Supervision Simulation Environment ........................................................ 12-3
Run the System......................................................................................................... 12-7
Runtime Features ................................................................................................... 12-29
Alarm Templates .................................................................................................... 12-44
Sequence of Events ................................................................................................ 12-50
CHAPTER 13: RUNTIME SERVICES............................................................................. 13-1

Introduction .............................................................................................................. 13-1
Operation Client ....................................................................................................... 13-4
Project-based Documentation ................................................................................ 13-18
xvi PlantStruxure PES V4.2 November 2016

CHAPTER 14: IMPORT AND EXPORT .......................................................................... 14-1
Introduction .............................................................................................................. 14-1
Import/Export from the Application Explorer ......................................................... 14-3
Import/Export from the Topology Explorer ........................................................... 14-10
Import/Export from the Project Explorer ............................................................... 14-16
CHAPTER 15: ONLINE CHANGES ............................................................................... 15-1

Introduction .............................................................................................................. 15-1
Failures and Interlocks ............................................................................................. 15-3
Modify the Control Participant Logic at Runtime ................................................... 15-7
Deploy Changes ..................................................................................................... 15-20
CHAPTER 16: EXTEND THE SYSTEM .......................................................................... 16-1

Introduction .............................................................................................................. 16-1
Add a Second PAC................................................................................................... 16-3
Implement Supervision Redundancy ..................................................................... 16-15
CHAPTER 17: DISTRIBUTED I/O DEVICES ................................................................. 17-1

Introduction .............................................................................................................. 17-1
Modify the Architecture ........................................................................................... 17-4
Construct the Advantys Rack ................................................................................. 17-19
CHAPTER 18: CONFIGURE A REDUNDANT M580 ...................................................... 18-1

Introduction .............................................................................................................. 18-1
Redundant Architectures .......................................................................................... 18-4
Configure a M580 Redundant Architecture ............................................................. 18-5
Deploy to the Redundant CPUs ............................................................................. 18-10
Changes After Deployment .................................................................................... 18-14
CHAPTER 19: INTRODUCE THE GENERAL PURPOSE LIBRARY ................................. 19-1

Introduction .............................................................................................................. 19-1
Overview of the General Purpose Library ............................................................... 19-2
Global Objective ...................................................................................................... 19-4
Context of Templates ............................................................................................... 19-5
Library Content ........................................................................................................ 19-7
Vertical Industry Solutions .................................................................................... 19-15
Advanced Libraries ................................................................................................ 19-21
Template Fundamentals ......................................................................................... 19-25
Interfaces ................................................................................................................ 19-39
Supervision Standards ............................................................................................ 19-58
GPL General Functions .......................................................................................... 19-80
CHAPTER 20: MANAGE CHANGE ............................................................................... 20-1

Introduction .............................................................................................................. 20-1
Understand the Effect of Changes ............................................................................ 20-3
PlantStruxure PES Configuration Manual Release 4 xvii

CHAPTER 21: SEQUENCE CONTROL .......................................................................... 21-1
Introduction .............................................................................................................. 21-1
Manage a Sequence .................................................................................................. 21-2
CHAPTER 22: MULTI-USER CONFIGURATIONS ......................................................... 22-1

Introduction .............................................................................................................. 22-1
Computers have Separate Functionality................................................................... 22-3
Remote Engineering Client ...................................................................................... 22-7
Remote Operation Client ........................................................................................ 22-13
User Management .................................................................................................. 22-18
CHAPTER 23: CONSOLIDATION WORKSHOP ............................................................. 23-1

Introduction .............................................................................................................. 23-1
Self-Paced Workshop ............................................................................................... 23-2
APPENDIX A: ADDITIONAL EXERCISES ...................................................................... A-1

Introduction ............................................................................................................... A-1
Display and Sort ........................................................................................................ A-2
Workspace Management ......................................................................................... A-10
APPENDIX B: INSTALLATION GUIDE ........................................................................... B-1

Introduction ................................................................................................................B-1
Installation ..................................................................................................................B-2
APPENDIX C: SIMPLE IMPLEMENTATION................................................................... C-1

Introduction ................................................................................................................C-1
A Very Simple Implementation .................................................................................C-2
APPENDIX D: PLANTSTRUXURE PES IN THE ENGINEERING LIFECYCLE ................. D-1

Introduction ............................................................................................................... D-1
Steps to Complete the Course ................................................................................... D-2
Instantiation Stage ..................................................................................................... D-3
Configuration Stage................................................................................................... D-7
Projects Definition Stage......................................................................................... D-12
Assignment Stage .................................................................................................... D-16
Generation Stage ..................................................................................................... D-19
Refinement Stage .................................................................................................... D-21
Mapping Stage ........................................................................................................ D-24
Build Stage .............................................................................................................. D-27
Deployment Stage ................................................................................................... D-29
Execution Stage ....................................................................................................... D-32
APPENDIX E: GLOSSARY OF TERMS ............................................................................ E-1

Introduction ................................................................................................................ E-1
Glossary of Terms ...................................................................................................... E-2
xviii PlantStruxure PES V4.2 November 2016

Chapter 1: PlantStruxure PES at a Glance
Introduction
Introduction
PlantStruxure PES is the innovative Process Expert system developed by Schneider
Electric. It is the software that integrates the Control and Supervision applications
along with the field devices in a single environment.
This chapter will take an initial overview look at the product in order to set the
scene for the training.
By the completion of this chapter the student will be able to:
 Describe the purpose of PlantStruxure PES

 Launch the product
This Chapter Covers These Topics:
 What is PlantStruxure PES? .................................................. 1-2

 PlantStruxure PES Architecture............................................. 1-4
 Start the Software Package .................................................. 1-13
What is PlantStruxure PES?
Background Many pressures exist to impact upon the successful creation and maintenance of a
complex industrial plant management system. These pressures may include
competing priorities, they may depend upon changing priorities, but most
importantly, upon the actual complexity itself.
Designing and building complex systems requires the coordinated efforts of

multiple people - an activity often fraught with problems. To address this,
organisations are seeking tools which permit the strong imposition of rules and
procedures to limit the amount of "free spirit" which contributors may bring to the
project.
In addition, there are commonalities both within and between projects. For
instance, when defining a Pump (to take an item at random) within a project, there
is no reason to expect that the associated Tags defined in the Unity Pro
environment would be any different to those defined in the Vijeo Citect
environment. In fact such commonality should be encouraged.
Further, there is no reason to expect that, generically, the pumps within the
organisation should differ markedly from one to another. They will all support
various run, stop and estop commands, they will also export a variety of status
indicators (running etc.), they may also provide speed and flow numerical values
and so on. With this in mind, there's no reason why such a device couldn't be
abstracted and instantiated into a system as required.
1-2 PlantStruxure PES V4.2 November 2016

What is PlantStruxure PES? (cont.)
Identify the With the use of lower-level execution platforms for Control and Supervision
Problem almost always occurring in tight harmony on plant management projects, Schneider
Electric saw an opportunity to combine many of the common aspects of the two
and at the same time, develop a significant number of pre-built components which
would simplify the development and testing of complex systems.
Because such Control and Supervision projects shared a great deal of common
material - variable tags being an obvious point, the ability to define this common
material just once for propagation to both environments is important for both
saving time and also improving quality.
Further, by abstracting both the functionality and interfaces of standard objects

(e.g. Pumps or Valves) it becomes a much simpler matter to add such a standard
object to a project and merely instantiate it by providing details of the specific
usage in context.
In addition, by generating both Control and Supervision projects from a common

source base, the opportunity for mismatch errors between the two projects is
essentially eliminated.
PlantStruxure PES Configuration Manual Release 4 1-3

PlantStruxure PES Architecture
Structural View The following diagram indicates the inter-relationships of the various components
of the of a running PlantStruxure PES system. These are the System Server (containing
Components an instance of the Virtual Box virtual machine and the Cache database) and the
Engineering Client which directs the activities of the server.
The Virtual Box file (containing the Control and Supervision participants
installations, along with the various communications modules) is approximately
11GB in size. The Cache database (which contains the project configuration and
the elements of the configuration tool itself) will start at around 1GB, and may
grow into the tens of GB in a complex system.
Run-time client computers need access to the Virtual machine (this may occur
across the network) in order to make use of the additional services provided by the
PlantStruxure PES environment. In addition, Engineering client computers (these
are used to construct the various pieces of the on-site implementation) may access
the server-based virtual machine, or have their own instance installed locally.

PlantStruxure PES Architecture (cont.)
Introduce Constrained by today’s global economic environment, companies are constantly

PlantStruxure striving for more and more efficient means of production.
PES
As a consequence, and to answer such need in optimising plant’s productivity, the
following actions are often taken:
 Reduce the engineering, operation and maintenance costs.

 Improve the plant and production efficiency.
 Maintain the expected quality of the production.
 Protect people, assets and environment.
 Increase the return on investment.
With PlantStruxure PES as a collaborative system, Schneider Electric provides a
solution from the field devices at the plant floor level through to the enterprise
level:

Software There are four primary components installed as part of the PlantStruxure PES
components installation:
PlantStruxure PES Manages the interface between the Client and the back-end
System Server systems.
PlantStruxure PES This is the software PlantStruxure PES users work with to create
Engineering Client and maintain both Control and Supervision projects, along with the
organisational topology, in an integrated fashion.
PlantStruxure PES An Operations Client supports Unity Pro and Vijeo Citect in the
Operations Client production environment. In addition to the normal operation of
those software packages, an Operations Client provides an interface
to give access to various platform resources and also to permit 'on-
the-fly' configuration modifications and process monitoring.
InterSystems Cache This is the database manager to control storage and access to
projects and related information. In addition, the entire
configuration environment is contained here.
Virtual machine A virtual machine is used to provide access to the underlying
Control and Supervision participants along with OFS and
Advantys.
In addition, it is advised to include OFS, Unity Pro and Vijeo Citect in the
development environment to assist with testing.
To manage the entire engineering workflow for implementing automation systems,

the Process Expert platform integrates software tools, which are called Participants:
 A Control Participant: A set of editors and services that allow you to configure
controllers, refine, modify, and troubleshoot projects of automation systems.
 A Supervision Participant: A graphic builder that allows you to design the
operation environment and provide the operator with interfaces to conduct the
process.
1: Ready for other Schneider Electric Participants (an Historian for

example).
2: Future developments may include the integration of third-party
software tools.

Physical PlantStruxure PES draws together a number of specific components into a fully
Structure View interactive design and plant management system.
The various control devices (indicated at the bottom of the diagram above), along
with the Operation Server (typically a Vijeo Citect I/O, Alarm, Report and Trend
server) and the Operator Station form the operational control system, while the
System Server and Engineering Station are principally used to execute the design-
time environment.
With PlantStruxure PES V4.2, the various components may be distributed across
multiple computers; additionally the development environment provides support
for multiple concurrent developers on a single structure. This is covered in depth
in Multi-User Configurations (page 22-1).

The Roles of Working in a PlantStruxure PES environment, three phases of operation will be
PlantStruxure completed.
PES, Unity Pro
and Vijeo Citect
1 The PlantStruxure PES system is refined and built using the
various Explorers (The Various Explorers (page 2-3)).
2 The completed Unity Pro and Vijeo Citect components are

generated and built for their relevant environments
3 The separate projects are activated on their relevant platforms -

the Unity Pro application is deployed to the PACs and launched,
while the Vijeo Citect application is compiled and run on the
control PC and Station Nodes
In general, the development of either Unity Pro (Control) or Vijeo Citect

(Supervision) projects will be totally automated in this environment, projects may
be constructed that are amenable to later fine tuning using the various resources
provided within the PlantStruxure PES environment. Unity Pro projects are totally
developed in PlantStruxure PES. Unity facets are developed inside PlantStruxure
PES, while their Constituents are sourced externally. Vijeo Citect templates and
genies are built outside of PlantStruxure PES while Pages are developed inside.
However, with this in mind, it is strongly recommended that once the projects are
delivered to the various controllers and Control stations that they not be further
modified - all such changes should occur within the PlantStruxure PES framework.
Virtual Machine Installed as part of the product, a virtual machine, based on Oracle's VirtualBox
Environment technology is provided to host the participants managed by PlantStruxure PES. In
this version PlantStruxure PES manages the Control participant (Unity Pro),
Supervision (Vijeo Citect)), Remote IO (Advantys) and OPC communication
(OFS). It is by interacting with all of these that functioning projects may be
created.
The virtual machine has been built 'headless,' meaning that it has not been
configured to interact directly with the monitor of the host computer. This VM
instance should be left alone; no attempt should be made to connect to it as
PlantStruxure PES relies upon it remaining in an entirely controlled state.

System The minimum configuration required to successfully install and run PlantStruxure
Requirements PES is:
Operating System: Windows 7 Pro 64-bit

Windows 8.1 Pro 32-bit or 64-bit
Windows Server 2012 R2 (recommended)
Processor: Core i5 - quad core (minimum)

Core i7 - quad core (recommended)
RAM: 8GB for 64-bit OS (minimum)

16GB for 64-bit OS (recommended)
Hard Disk: 250GB SSD (recommended)

250GB / 7200 rpm (minimum)
70GB free
NTFS only
Optical Disk (optional) to install the software
Display XGA (1024x768) or higher, 24 bit colour

Second monitor recommended
Ethernet port Required for licensing and to communicate with plant

devices
Internet access Required only for temporary communication by the

Floating License Manager during the activation process
USB port For user data exchange and library updates
Peripheral device Mouse or similar pointing device
Only 64-bit installation files are provided for computers that will run the server and
development software components. The Operations Client (see Runtime Services
(page 13-1)) is the only part of PlantStruxure PES that is supported on a 32-bit
platform.

Product The licencing process is independent of the software installation process.

Licencing However, if no license is available, the Process Expert engineering software will be
installed but it will not run - the Server component will report an error and close.
With PlantStruxure PES V4.2, the various components (System Server,

Engineering Client and Operation Client) may be licensed separately.
The Floating License Manager (installed alongside the PlantStruxure PES product)
is used to activate the software.
The following methods are available for activating the license:
 By web
 By web portal
 By e-mail
Further information is available in the PDF User Guides section of the in-product
documentation. Licencing will not be significantly considered as part of this
training manual, however brief notes on applying a licence have been provided in
Licence PlantStruxure PES V4.2 (page B-7).
A full description of the various licencing options may be found in the document
"Process Expert Licencing Guide," however the following is a useful summary.
The current version of PlantStruxure PES effectively supports an unlimited number

of instances, PACs and Supervision stations. The document "Process Expert
Licencing Guide" will provide further information.
Licence Options Engineering Licences
Part Number Description Notes
EUSBEUCZZSPEZZ SW PE ENG SINGLE PES Engineering System including a

LICENSE System server & one Engineering client;
Permanent license; doesn't include any
application license.
EUSCLTCZZSPEZZ SW PE ENG CLIENT PES Engineering client single license
SINGLE LICENSE for System Server extension.
EUSCLTCZZGPEZZ SW PE ENG CLIENT PES Eng client group license (3x seats)
GROUP LICENSE for System Server extension
EUSCLTCZZTPEZZ SW PE ENG CLIENT PES Engineering client team license
TEAM LICENSE (10x seats) for System Server extension

Licence Options System Size

(cont.)
EUSAPPCZTSPEZZ SW PE APPL LICENSE PES Application Extra Small permanent

EXTRA SMALL license (500 process object instances
maximum). Applicable only for
configuration with Supervision based on
Vijeo Citect.
EUSAPPCZSSPEZZ SW PE APPL LICENSE PES Application Small permanent
SMALL license (1250 process object instances
maximum), allowing engineering and
permanent runtime services.
EUSAPPCZMSPEZZ SW PE APPL LICENSE PES Application Medium permanent
MEDIUM license (3000 process object instances
EUSAPPCZLSPEZZ SW PE APPL LICENSE PES Application Large permanent
LARGE license (7500 process object instances
EUSAPPCZXSPEZZ SW PE APPL LICENSE PES Application Extra Large permanent
EXTRA LARGE license (unlimited number of process
object instances), allowing engineering
and permanent runtime services.
Operation
EUSOPECZZSPEZZ SW PE OPER SERVER PES Operation server; permanent

LICENSE license, allowing runtime services on the
server.
EUSLCCCZZSPEZZ SW PE CTRL CLIENT PES Control Client; permanent license
LICENSE allowing runtime services from the
client.
EUSVCCCZZSPEZZ SW PE VIEW CLIENT PES View only Control Client;
LICENSE permanent license allowing runtime
services from the client.
EUSLRCCZZSPEZZ SW PE REDUNDANT PES Control client enabling access to a
CTRL CLIENT redundant Operation server. A regular
LICENSE control client must be ordered for each
redundant control client
EUSVRCCZZSPEZZ SW PE REDUNDANT PES View only client enabling access to
VIEW CLIENT a redundant Operation server. A regular
LICENSE view only client must be ordered for
each redundant view only client

Exercise - Determine Appropriate Licence
Learning By the completion of this exercise you will be able to:

Outcomes
 Determine the most appropriate licences for specific site use.
1 Class discussion.
For each of the following scenarios, determine all licencing

necessary.
i. A Schneider Electric Integration Partner with 6 project development

engineers. This company typically works on multiple projects
concurrently.
ii. A Cement manufacturing plant with around 20,000 variable tags, 5

operations servers and 20 operations staff. All development work is
done in-house by a team of three.
iii. A frozen vegetable processing facility. There is just one operation

server and 7 operator consoles. All project development work is
done by the company in point 1.
iv. A waste water treatment plant has a requirement for full redundancy
at all significant points of failure. This site has seven independent
control zones, each with their own Supervision server and 3 operator
screens. Development is done by a team of 10 at a central
corporate site with responsibility for this and many other near-
identical sites.

Start the Software Package
Server The PlantStruxure PES Server runs as a background service (with a visible logging
Components window) in order to act as a conduit between the Client and the underlying
databases and the virtual machines (generally hosted on a server) with the
Supervision and Control participants.
When started, the Server displays an initialisation page where various maintenance
tasks may be executed. The server must then be started from the Actions menu.
Observe that the product version number is reported as the last step in launching
the server.

Start the Software Package (cont.)
How to Launch  To launch the Engineering Client:

the
PlantStruxure
PES Engineering
Client Double click the Client icon on the Desktop.
Or
From the running System Server window, select the menu Action » Launch
engineering client.
A login page will appear. After successful authentication, the main Engineering
Client window will be displayed.

Authentication In order to open the Engineering Client, the user must be authenticated. This
and Activity authentication will be performed against either the Active Directory (AD) for a
Logging 'corporate' environment or the local WorkGroup if no Active Directory is present.
After starting the Engineering Client, a Log In dialog will be delivered.
By default, this will display the currently logged in Windows user and request the
password of that user. Should it be necessary, it is an easy matter to replace the
user name with any other locally valid name.
Note:
Although valid for Windows authentication, PlantStruxure PES will not permit the
use of a Windows account without a password.
Observe that the User Name is structured in the format Domain\User for AD, or
Local_Computer_Name\User for a WorkGroup authentication.

Activity Logging All authentication events (along with many other aspects of the operation of
PlantStruxure PES) are logged in the Notification area at the bottom of the
Engineering Client window.
Beyond authentication, the Notification panel also displays the various activities
undertaken by users of the Engineering Client.

Export the Any entries contained within the Notification panel may be exported.
Notification Log
This may be done by clicking the Export Historical Audit Data button.
This will open a dialog requesting a file name and location; along with a date/time
range for the exact records required.
Once saved, a CSV file of the saved name will be created.
This can then be opened using Excel or a text editor such as Notepad.

Multi-User By default, the Engineering Client is configured to use the loopback address to
Installations make a connection with the System Server. This means that it expects to find a
Server instance on the same computer.
By modifying the address in the Engineering Client Configuration Wizard, a new

target Server may be identified.
The level of licensing will determine the maximum number of concurrent

Engineering Client connections that may be made, although there is a practical
limit of four concurrent VBox instances on any Server.

Connect an To create a connection to a remote PlantStruxure PES server, the Engineering

Engineering Client Configuration Wizard is used to identify the IP address of the target
Client Computer.
Once this is done, the local Engineering Client will create a connection to that
remote computer.

(Optional) Exercise - Connect a Remote
Engineering Client

Outcomes
 Connect the Engineering Client to a remote PlantStruxure PES server.
This exercise is only required for a training course using a centralised System
Server. The Instructor will advise if this is required.
1 Configure the local Computer for remote access.

i. From the Start button, select All Programs » Schneider Electric »
Process Expert » Engineering Client Configuration Wizard.
ii. In the Address field, enter the IP address of the Computer hosting
the Server. This may be the Instructor's Computer, or possibly that
of another Student - the Instructor will advise.
iii. Click the Next > Button.

Exercise - Connect a Remote Engineering Client
(cont.)
The only field of interest is the use of local virtual machines. The
Instructor will advise whether to check or uncheck this option.
iv. Click the Save & Close Button.

Exercise - Launch PlantStruxure PES
Learning By the completion of this exercise you will:

Outcomes
 Be able to launch the PlantStruxure PES Server and Engineering Client
components.
 Be able to identify the major tools offered by the Client application.
1 Start the Server
i. Double click the PES Server icon to launch the back-end server
component.
This will deliver the System Server management window. At this

point, the back-end services have not been started.
ii. Select the menu Action » Start.

Exercise - Launch PlantStruxure PES (cont.)
After a period of time (perhaps as long as a couple of minutes) the

server startup logging screen will indicate Server is ready.
iii. The Server window may be minimised at this point if desired.
2 Start the Engineering Client

i. Once the server has fully started, launch the client application by
double clicking the Engineering Client icon.

ii. Alternately, the Engineering Client may be started from the Server's
Action menu. Select the menu Action » Launch engineering client.

Exercise - Launch PlantStruxure PES (cont.)
iii. As part of the startup sequence, a user must authenticate the client.
Once the startup sequence is complete, the client will open an

instance of the Systems Explorer.

Summary
Summary This chapter covered the following topics:
 What is PlantStruxure PES? (page 1-2)

 PlantStruxure PES Architecture (page 1-4)
 Start the Software Package (page 1-13)
Questions The following questions are used to check understanding.
 What are the primary tools available for selection on the Engineering Client
task bar?
 What indicates that the System Server has completed its start-up process?
 Under what circumstances would PlantStruxure PES be a good choice in the

development of control system projects?

Chapter 2: Manage the PlantStruxure PES Environment
Introduction
Introduction
In this chapter, a structural exploration will be undertaken. Here, students will
observe the primary configuration tools and will be taken on a brief tour of the
entire sequence of steps required to create a minimal configuration.
Additionally, the ability to explore multiple independent environments will be

investigated.
 Describe the various Explorers

 Understand the overall process of creating a complete system
 Manage multiple, independent, configuration environments
 What is a System? ................................................................. 2-2

 The Various Explorers ........................................................... 2-3
 A Very Simple Implementation............................................. 2-8
 Manage the Underlying Database Environment.................... 2-9
 Upgrade from Previous Versions ........................................ 2-18
What is a System?
System Defined In PlantStruxure PES, a System is the representation of an actual automation

system and is defined through 3 distinct parts:
 The Application: Defines the functions of the system and the corresponding
process hierarchy
 The Topology: Defines the hardware and software infrastructure of the system
- Controllers
- Devices connected to field buses
- Networks
- Station nodes (their hardware and software components)
 Projects: Define the Participant projects that implement the functions of the
system:
- Control Projects
- Supervision Projects
A System spans the extent of a single connected location where the Control and
Supervision aspects are clearly defined. This means, for instance, that a System
would be defined for a self-contained section of a plant. It is unlikely that a single
system would be defined that spanned either multiple unrelated processes at a
single site or multiple discrete sites.

The Various Explorers
Overview - The
Various The Library explorer is accessed via the Global Templates button on the main
Explorers menu tab and is responsible for:
 Browsing the various templates of the Global Template library

 Creating "empty" Global Templates
 Accessing the Global Template editors
Note:
The library explorer is not covered in this training course but is used extensively in
the PlantStruxure PES Create Library Templates course.
The other Explorers are available via a right click menu displayed on the root of
any System.
The Systems Explorer acts as a global manager with a general purpose folder
structure (as seen above) intended to map the corporate structure (either geo-
political or line-of-business based). The lowest nodes of this structure will be
individual Systems. A System represents a single integrated site control and
management environment.
Within PlantStruxure PES, the various aspects of a System are developed using the
Application, Topology and Project Explorers; each of which is described on the
following pages.

The Various Explorers (cont.)
Systems Explorer The Systems Explorer is the primary overview of the entire PlantStruxure PES
installation. It would be reasonable to have a high-level folder structure defined
here to describe the world-wide operations of a multi-national business; or
alternately a much simpler structure to reflect the single-site operations of a much
smaller entity.
In the image above (derived from the environment to be built during this course),
there are two layers of organisational hierarchy and two Systems defined for the
lower hierarchical level (Corsek and Casper). A System is the term used for the
PlantStruxure PES configuration and will eventually spawn a matching pair of
Control and Supervision participant projects.
The Systems Explorer is also the host of the other configuration explorers (the
Application, Topology and Project Explorers).
The Systems Explorer is addressed in the next chapter.

Application The Application Explorer allows the engineer to model the process application
Explorer according to the P&ID model description and then create instances of Object
Templates accordingly.
The Application Explorer is used to construct an abstract application which

embodies the concepts of re-use and simple encapsulation.
1 Templates Browser pane.

2 System root folder
3 Tree view of the expanded application folder structure
4 Closed application sub-folder with contents
5 Closed, empty application folder
6 Open application parent folder containing instances
7 Explorer layout settings button
The Application is the main focus of the chapter Create the Application (page 4-1).

Topology The Topology Explorer permits the user to model the entire topology of the
Explorer automation system, consisting of both the hardware and software infrastructure.
Various components of the topology may be isolated into a folder structure to
simplify the overview.
During the deployment phase, Control Projects are deployed from the Topology
Explorer.
An example Topology:

2 Topology folder tree view
3 Station node folder (expanded view to display contents)
4 Ethernet network device
5 Controller folder (collapsed view)
The Topology Explorer is addressed in the chapter Create the Topology (page 5-1).

Project Explorer The Project Explorer will be used to create the Control and Supervision projects.
In achieving that outcome, a number of standard objects are created to represent the
various components of the projects.
During the deployment phase, Supervision Projects are deployed from the Project
Explorer.
The image below demonstrates the appearance of the Control Project structures.

2 Control project (expanded view to show contents)
3 Control project (collapsed view)
4 Supervision project (collapsed view)
The Project Explorer is the primary topic addressed in the chapter Create the
Project (page 6-1).

A Very Simple Implementation
Product Walk- This part is a demonstration of how to create a very simple (and highly incomplete)
Through System in order to show the overall process and the major components of the
product. This will take the form of a very simple structure linking a Digital Input
with a Digital Output. Valid Control and Supervision projects will be created but
not implemented.
This is provided as a database backup that will be restored in the next exercise so
there is no need to recreate this during the demonstration.
In the next exercise this project will be restored for examination.

Manage the Underlying Database Environment
Back Up the Underlying the entire PlantStruxure PES environment is the Cache database.
Database Following the installation of PlantStruxure PES, this database manager is
configured to auto-start when Windows starts.
In previous versions of PlantStruxure PES, it was necessary to stop the cache

server in order to manually switch database file-sets. In the current version, this
functionality has been built into the Server utility. In addition, a dedicated
compressed file format (.dbk) is provided to store database backups.
Backed up databases may be stored wherever convenient.
Of course, it is not necessary to backup the current database if it already exists on

disk or it is no longer required.

Manage the Underlying Database Environment
(cont.)
Restore the An option on the Tools menu may be used to import a database.
database
This will load a .dbk file for configuration.
Note:
This is a destructive process. The Restore database command WILL overwrite

whatever is currently stored in the Cache database environment. If the existing
content is required for later use it must be backed up first.

Exercise - Restore the Simple Implementation

Outcomes
 Restore and view the Simple structure built previously by the Instructor.
1 Shut down the existing systems.

i. Close the Engineering Client.
ii. On the System Server, select the menu Action » Stop.
iii. This process will complete by closing the System Server window.
Re-start the System Server from the desktop icon.
2 Restore the database.

i. From the System Server window select the menu Tools » Restore
database.

(cont.)
ii. In the Open dialog, locate the SimpleProjBuilt.dbk backup file.
iii. Click the Open button to commence the restore.
The restore process will take a short while. Once completed, the
status screen of the System Server will report Done.
iv. Select the menu Action » Start to start the newly restored database.

(cont.)
3 View the restored content.

i. Open the Engineering Client and log in.
The Client will automatically start with the Systems Explorer view
opened. Other view may be accessed from the toolbar at the top-
left of the Window.
ii. In the System Explorer, right-click the system and select Open
Application.
This will make the Instances visible:.
Explore the configuration and don't worry about changing anything -

this configuration will be discarded at the end of the exercise.

(cont.)
iii. In the System Explorer, right-click the system and select Open
Topology to view the topology.
iv. In the System Explorer, right-click the system and select Open
Project to view the Project Configuration.
v. Click the Display Tabs button to view a drop down menu of all
currently opened tabs.
vi. Select various tabs to confirm they may be selected by this method.
vii. Spend a few moments reviewing the structure of Application,
Topology and Project.

(cont.)
4 Open the Information page.
i. Click the 'hammer-spanner' icon to open the About page.
The PlantStruxure PES version information displayed here will be the

same as was seen when the server started. Additional information
will be displayed for licensing and for the companion products.
ii. Select the Systems Details tab.
The above image may look different depending on which database is

loaded
iii. Close the System Details and About pages.

(cont.)
5 View the Help System.
i. Click the Question Mark icon. The list of available Help

information will be displayed.
ii. Open the various sub-folders and observe the variety of Help files
available. In particular, expand the item Process Expert PDF User
Guides.
Within this, the item Process Expert User Guide will be of great
assistance throughout this course. It is suggested that it be left
open and available.
iii. Close the PlantStruxure PES Help screen.
iv. Close the Engineering Client.

(cont.)
6 Restore the empty database

i. Stop the system server and select Tools » Restore database.
ii. In the Open dialog, locate the EmptyDatabase.dbk file and click the
Open button to commence the restore.
iii. Select the menu Action » Start to start the newly restored database.

Upgrade from Previous Versions
Previous PlantStruxure PES V4.2 may be installed either on a computer with no previous
Versions version installed or as an upgrade to an existing v4.1 installation. In the latter case,
an automatic upgrade will be executed.
Should an earlier version of PlantStruxure PES be installed, it must be manually

removed (along with all the accompanying components - Cache, VBox etc.) prior
to the installation of V4.2.
Upgrade Process If PlantStruxure PES V4.2 is installed on an existing v4.1 computer, the old version
will automatically be removed prior to the installation of the latest version.
However, this will not also address the migration of existing databases.
Previous version databases maybe upgraded to the current version, but the process
occurs in multiple steps and must be commenced on the earlier version of
PlantStruxure PES prior to the new version being installed.

Upgrade from Previous Versions (cont.)
Upgrade Process The migration from V4.1 to v4.2 must follow these steps:
(cont.)
1 Before installing V4.2, install the v4.1 Migration patch, located in the
MigrationPatches folder of the distribution media into the existing v4.1
installation.
2 Perform a backup of the existing database for migration. If there are

multiple databases in use, each will have to be restored and then backed
up for migration. Unlike the typical database backup with a .dbk
extension, the 'migration' backups have a .mdbk file extension.
3 Install PlantStruxure PES V4.2 according to the instructions in

Installation Guide (page B-1).
4 Install any necessary product extensions (generally not required in a

default installation).

Upgrade from Previous Versions (cont.)
Upgrade Process The migration from V4.1 to v4.2 must follow these steps (cont.):
(cont.)
5 In the new PlantStruxure PES installation, use the 'Restore database for
migration' command to import the backups created in step 2 above.
6 Start the System Server to execute the migration. Once done, start the
Engineering Client to check the conversion.
Steps 5 and 6 will be repeated for each database backed up in step 2.
See Also:
For further information about Database Migration, see PlantStruxure PES Help -
Installation Guide, Chapter 4.

Summary
 What is a System? (page 2-2)

 The Various Explorers (page 2-3)
 A Very Simple Implementation (page 2-8)
 Manage the Underlying Database Environment (page 2-9)
 Upgrade from Previous Versions (page 2-18)
 What is a system?
 Which tool is used to backup or restore a System?
 What is stored in a .dbk file?
 What is the easiest method to determine the version number of the

PlantStruxure PES installation?

Chapter 3: Develop the System Structure
Introduction
Introduction
The framework of a simple system hierarchy will be developed in this chapter. This
framework normally consists of a number of folders to organise the system(s) and
one or more systems to contain the PlantStruxure PES configuration.
 Create a Folder structure to host one or more Systems

 Create a system for the remainder of the course
 The Engineering Client .......................................................... 3-2

 Systems and Folders .............................................................. 3-3
 Steps to Complete the Course .............................................. 3-12
The Engineering Client
Client When the PlantStruxure PES Engineering Client is started, the main front page will
Components appear.
There are a number of significant zones on the Engineering Client:
1 Toolbar
2 Tabs bar
3 Workspace toolbar
4 Workspace
5 Notification panel

Systems and Folders
ISA-S88 The ISA-S88 standard for Batch control presents four essential concepts:
Standardisation
 The depiction of what exists in the plant (the physical model)
 The definition of intended outcomes in the plant (the recipe)
 Implementation of how the plant operates (equipment logic)
 Putting the pieces together in a sensible and reusable way.
Observe that the standard was developed especially for batch processes; however,
it has also been successfully applied to continuous and discrete processes that
require a certain amount of flexibility.
S88 offers standard terminology, with the objective of developing a common

framework for the sharing of information. Difficulties in communication can cost
time and money, or even worse, can cause failures in control systems.
In addition, S88 offers modularity, making process equipment and procedures

developed in one application reusable in another, potentially delivering savings in
both time and money.
PlantStruxure PES is fundamentally based on the principles of ISA-S88 and its

influence may be seen at a number of levels.
S88 Upper The upper layers of S88 generally define the organisation's sites and areas. Systems
Layers will generally be below these levels as they will apply to an individual area or
process cell.
For example, a system may exist for the treatment works but if all three sites are
the same then three systems will exist, one for each site. In the above example
there may also be systems for Supply and Manufacturing at all three sites i.e. nine
systems in all. Being able to find systems can become difficult in large hierarchies
so PlantStruxure PES allows the creation of a folder structure to make it easier to
locate components.

Systems and Folders (cont.)
Organisational A Folder is an organisational tool; a container, to allow for distinct units of

Hierarchies configuration to be isolated.
A System is the term used to describe the package of components built using
PlantStruxure PES which together comprise an Automation System.
Although this image displays a single folder (My_Folder) with two Systems,
multiple such folders may be created, each containing multiple systems.
It would be reasonable to expect that large organisations may want to manage their
entire world-wide fleet of sites through a single implementation of PlantStruxure
PES. To achieve this, a significantly complex array of folders containing multiple
Systems would be required.
How to Create a A new system is created using the Systems Explorer tool in PlantStruxure PES.
New System
 To create a new system:
Open the Systems Explorer tab in PlantStruxure PES and from the right click menu
of the Systems Explorer button, select Create System.

Exercise - Create a New System

Outcomes
 Be able to create and name a new system.
 Be able to design a folder structure to organise multiple systems.
1 Create a new System.

i. Open the PlantStruxure PES Engineering Client application (if not
already open).
ii. Right click the Systems Explorer object and select Create System.

Exercise - Create a New System (cont.)
iii. After a few moments, the new system (by default called System_1)
will be created.
Note:
Activities occurring in the back-end in support of these client-side actions may be

observed by viewing the Server window.
2 Give the new system a name.

i. The default name (System_1) will be automatically placed in rename
mode. Change the System name to Corsek.

ii. Right-click the Corsek object and select properties.
In addition to renaming a System, it is possible to include additional

information as seen in the image below.
No additional fields will be used at this point (although information

may be filled in as desired).
iii. Click the close button in the upper right of the properties view
to save the change.
Note:
In most cases, there is no concept of 'saving' changes. Whenever a screen is closed

(for instance when the System name was changed on the previous page) the current
state of the page is immediately written to the database. In those situations where a
save is required, Students will be instructed to use the appropriate tool.
When an explicit save action is required PlantStruxure PES will warn the user if
they attempt to close an edit screen without saving.

3 Create a folder structure.
A complex PlantStruxure PES environment may contain multiple

Systems and it is normal to organise these with some kind of folder
structure.
i. Right-click the System Explorer object and select Create Folder.
ii. Once the new folder is created, rename it as Worldwide Widget

Corp.

iii. Beneath Worldwide Widget Corp, create two other folders called
Infrastructure Services, and Manufacturing Services.
iv. Beneath Infrastructure Services, create two folders called WWW
Division and Transport Division.
4 Rearrange the structure.
Observe that the System (named Corsek) is currently an attribute of

the Systems Explorer root object. This should be changed.
i. Drag the Corsek object to the WWW Division folder.

ii. Once completed, the structure will look like this:
5 Add another System.
Additional Systems may be created at any level of the hierarchy. In

this instance, a second one will be created in parallel with the first.
i. Right-click the WWW Division folder object and select Create
System.

ii. Give the new System the name Casper.
6 Cannot delete a Folder with sub-objects.

i. Right-click the Worldwide Widget Corp object, observe that the
delete command is greyed out.
This is true at all levels. PlantStruxure PES will not permit the
deletion of any object that has daughter objects. Thus, the three
sub objects must be individually deleted before the parent object
may be deleted. In this instance, a usable structure has been
created which will not be deleted.

Steps to Complete the Course
Course The diagram on the next page indicates every major step undertaken in the
Progression construction of a working PlantStruxure PES solution.
This diagram will be referenced at each step to show the location of tasks being
performed in the wider context.
It is clear from the diagram that many development processes occur in parallel and
thus may be executed in any order - the only limitation being when these various
parallel streams are brought together (for instance in the Mapping stage).
Although specific to this training course (particularly in the specific use of M340
and M580 PACs) this diagram may easily be adapted to serve as a useful generic
overview of the tasks necessary to deliver any PlantStruxure PES System.

Steps to Complete the Course (cont.)
Engineering
Lifecycle

Summary
 The Engineering Client (page 3-2)

 Systems and Folders (page 3-3)
 Steps to Complete the Course (page 3-12)
 What are the steps required to create a new System?
 Why are Folders created?
 What is the standard conventionally used?

Chapter 4: Create the Application
Introduction
Introduction
The Application Explorer is used to specify the details of the plant operation to be
modelled. It does this by joining together pre-built objects to represent the various
plant components as was specified in the P&ID.
For each generic object (pump, valve, sensor) defined as a Template, the relevant
plant object will be created by instantiating the template into the application.
The course will be based on a simple Waste Water unit in the context of a larger
water treatment facility.
 Create a folder structure inside a system

 Instantiate Templates and Link Objects
 A Structural View of the System ........................................... 4-3

 The Training Scenario ........................................................... 4-7
 PlantStruxure PES Folder Structures................................... 4-13
 Instantiation of Objects........................................................ 4-22
 Object Linkages ................................................................... 4-49
Aim of this Chapter
Expected In the previous chapter, a simple version of the corporate hierarchy was created and
Outcome a system added. Next, the system hierarchy will be created to organise the
components of the plant. Again, this structure will be built in accordance with the
ISA-S88 standard.
With the hierarchy in place, the various physical components of the plant control
system will be instantiated and the attributes of each will be configured. In
addition, the links between objects will be defined.
Work undertaken in this chapter will be confined to the Application Explorer.

A Structural View of the System
Inter- In its simplest form, one might consider an electric motor in abstraction - it is either
relationships stopped, or it is running. However, whether it is running or stopped will have
wider implications subject to what exactly it is connected to.
Clearly this device will be part of a more complex system and in order to be
managed, modelled and controlled must have representation as abstract templates
within the PlantStruxure PES environment.
As indicated in the diagram below, it would be reasonable to expect this motor to

be directly managed by a PAC and for the overall view of the plant's operation to
be seen from some Supervisory screen.
The Template is the most fundamental structure in PlantStruxure PES. Templates

exist for all the expected objects that might exist in a plant (motors, switches,
valves, heaters etc., to name but a very few). Each template contains the
fundamental Control System programming (in the form of Derived Function
Blocks) and also the Supervisory management elements (in the form of genies).

A Structural View of the System (cont.)
Inter- Primary elements of a generic composite template:

relationships
(cont.)
Item Description
Control Module This is also referred to as a Template. This is the highest

level composite object and is referred to as a "control
module" as it provides both the Control and Supervision
functionalities that are required to manage the object that is
modelled by the composite template.
Unity Composite A Unity Composite (or UC) is the holding unit for all
Control components. It is a Control composite template
because it contains Control facet templates. It is also called a
composite reference as it is referenced inside the composite
template.
Unity Control A Unity Control Composite contains only Control Facets.

Composite However, as may be observed in the diagram, this object is
not the only holding structure for such Facets. Control
Composites are also referred to as UCs.
Unity Logic A Unity Logic Facet (UL) contains the fundamental DFB
Facet and related logic derived directly from Unity Pro. A group
of facets may be combined into a Control Composite, of they
may be combined with an existing Control Composite when
forming a Unity Composite.
Citect This object is used to represent all Supervision components

Supervision when constructing the Control Module.
Composite
Citect Data Facet The Citect Data Facet may directly represent Citect data
(tags etc.) or it may be a composite, combining many such
objects.
Citect Genie Genies are used as the pictorial representation of plant

Facet operation and (like ULs above) represent fundamental
configuration objects derived from the underlying
configuration tool.

Inter- Once templates are established, they may be used to construct an effective model
relationships of the plant.
(cont.)
Here, it may be observed that one or more templates may be instantiated into
Objects using the Application Explorer. These Objects may be incorporated into
Projects in all manner of interrelated ways. Once created, an Object may be re-used
as many times as needed.
The interrelationship between Projects is defined in the Project Explorer and the
final step is to deliver completed Systems to their destination systems, either Unity
logic to a PAC or SCADA logic and graphics pages to a Supervision system.
It is important to understand that the most important reasons for developing

customised templates is to embody site standards into the fundamental tools used
by all project developers.

Why a Three- Why is a system broken up in 3 distinct parts?

stage Design?
This is because PlantStruxure PES provides the flexibility to create an application
even if no decision has been made as to which controllers will be used.
Also, it is possible to create as many projects as required that will use instances
from the same application in different combinations.
Further, it is possible to create as many controllers as required in the Topology and

late, select the ones upon which the project will be run (through executables and
service mapping).
The key is flexibility at all layers of the configuration hierarchy.

The Training Scenario
Waste Water The Corsek Plant is a typical waste water treatment site:
Treatment Plant
The full network to support Corsek, with emphasis on the Chemical Treatment
section might look like this:

The Training Scenario (cont.)
Waste Water The initial scenario will create the simulation for this waste water treatment plant,
Treatment Plant focussed only on the Chemical Treatment process cell.
(cont.)
This P&ID represents the plant to be simulated during the course.
The Process Cell is composed of a tank with a mixer and containing two level
switches, along with a temperature sensor. Water is introduced to the tank via an
inlet valve; there is also a flow indicator and a PID to control this subsystem. On
the outlet side, there is a discharge pump and security valve.
For Tank 1, the three primary operational zones will be defined separately (Tank 2
will be treated separately):

Waste Water The devices will be connected as follows:

Treatment Plant
(cont.)
As these diagrams show, both Control and Supervision components will be created.
In the preceding diagram, the architecture of the plant is displayed. There will be
an operation server with a client (labelled Supervision Server and Supervision
Station at the top of the image) and a PES Engineering station with the PES Server.
In the control subsystem, there will be two controllers, one controller (a M580) to
control the logic of Tank 1, and a second controller to control the logic of Tank 2.
The initial architecture will be: water control modules wired and connected to the
in-rack IO Modules, and discharge and agitation control modules wired or
connected to the remote IO Modules.

The The intention is to deliver a "fully automatic solution." This environment permits
Implementation the system designer to define functional elements of the solution with the system
constructing everything required.
A functional hierarchy will be constructed to define the entire plant, although only
pieces of this will be developed to completion during the course.
PAC simulations will be constructed to define the precise hardware deployed to the
field. This functionality will be used to define the exact DFBs required to execute
the functionality of the system.

The Once devices have been defined, the network relationships between them must also
Implementation be specified.
(cont.)

The In order to give supervisory control and management of the system, a SCADA
Implementation environment will also be defined.
(cont.)

PlantStruxure PES Folder Structures
Structural In the previous chapter, a folder structure was created to represent the upper layers
Hierarchy for a of the S88 model. In a large organisation a more extensive structure might be
System required. However, the primary point to note was that the lowest nodes in this
structure were Systems.
A system represents the entirety of Control and Supervision functionality in a

single location.
Within a System, there is still an opportunity to create another folder structure to

identify the lower layers of the S88 model - these are created within the
Application Explorer.
Once this folder hierarchy is created, various configured objects will be placed
within it. Be aware that this organisational structure is for the benefit of the person
developing or reviewing the system and does not affect the way PlantStruxure PES
works.
Folder Name As well as a name, each Folder within a System may be given an Alias. This Alias
Aliases is typically composed of one or two letters / numbers and may be used as a short
but unique identifier for each layer in the hierarchy. Aliases will be chained
together to form hierarchically unique names for all objects (including Tag names)
within the System. This hierarchical naming can sometimes result in the name
becoming too long, so aliasing is a good way to reduce this length.
For example, the Hierarchical name:

Site1.ChemicalTreatment.Tank1.Water.CV10001
can be simplified to
S1.CT.T1.W.CV10001
This aliasing will be created during an exercise later in this chapter.

PlantStruxure PES Folder Structures (cont.)
Functional Level Functional Level icons are accessed from the Settings panel. Click the Explorer
Icons Layout Settings button to open this panel. This button is located in the
upper-right of the screen:
The Settings pane will open and icons may be allocated at each level:
Levels and Styles (as defined below) may be configured from this pane.
Icon Hierarchy Level Description
Site
1 Area
2 Process cell
3 Unit
4 Equipment Module

Characters There are some restrictions in the list of valid characters for Folder names. The full
Permitted in list may be found in the product documentation files shipped with PlantStruxure
Folder Names PES.
Edit Properties Properties may be configured for almost any object. These may be simply
descriptive (such as for a top-level System object), such as Market, Customer, Site,
Author etc.)
Or they may carry specific and significant configuration information:

Modeling the The Corsek Plant is a typical waste water treatment site:
Waste Water
Treatment Plant
A functional hierarchy will be constructed to define the entire plant, although only
pieces of this will be developed to completion during the course.

Exercise - Create the System Folder Structure

Outcomes
 Be able to create Folder objects to reflect the structure of the plant object being
modelled.
1 Create a structure to reflect the specific plant elements.

i. Right-click the Corsek object and open the Application Explorer.
An Application Explorer Tab will open with the Corsek item at its
root.

(cont.)
2 Create new Folders.

i. Beneath the Corsek object, create a folder called Site1, and beneath
that, the following folders which will represent the structure of the
plant:
Lifting
Screening
Grease and Sand
Primary Clarifier
Biological Treatment
Secondary Clarifier
Chemical Treatment
Note:
Only folder names (both root-level and nested) may contain spaces. All content
object names must be saved without spaces in their names.
ii. Beneath the Chemical Treatment folder, create folders Tank1 and
Tank2.

(cont.)
iii. Beneath Tank1 create these folders:
Water
Agitation
Discharge
3 Create folder aliases.

i. For each of the three folders created in the previous step, add an
Alias in the Properties view:
Folder Alias
Water W_
Agitation A_
Discharge D_
Note:
Most configurable items have a field called Area. Currently, this is implemented
only for Supervision projects but this functionality to identify and isolate discrete
sections of a plant will be extended across all aspects of a PlantStruxure PES
solution in future releases.

(cont.)
ii. Add alias values to the chain of folders back to the root at follows
Folder Alias
Tank1 T1
Chemical Treatment CT
Site1 S1
Other folders may also be given aliases but this is not required for
the course.
4 Add functional logos at each hierarchy level.
Logos will be allocated at each functional level to match the ISA-88

standard.
i. In the upper-right corner of the screen, click the Explorer Layout
Settings button to view the Settings pane on the left side of the
window.
Observe that the current Style icon (the opened folder symbol) is in
use on all objects beneath the System Object (Corsek). This will be
replaced with specific icons at each level.
Also observe that once the Settings Button has been used, the left
pane may be toggled between Settings and the Object Browser by
use of the Tabs at the bottom of the pane.
Note:
Icons should be allocated from the lowest level of the hierarchy to the top in order
to ensure that the layer closest to the hardware is given the Equipment Module
icon.

(cont.)
ii. In the Settings pane, select Level 4 in the sequence of seven folder
levels and click the right-most style ("Equipment Module").
This will change the Water, Agitation and Discharge objects to use
the Equipment Module icon.

iii. For each of the remaining levels (3, 2 and 1 in ascending order up
the structure) allocate Style icons progressively from the right,
skipping the Area icon leaving the Site1 object with the Site icon.
The Area icon will remain unused.
iv. Click the Browser tab in the lower left corner to return to the
'normal' view.

Instantiation of Objects
What is The word instantiation is derived from the word instance. It is used in the context
Instantiation? of PlantStruxure PES to create a specific instance of a template-derived object.
Once a system has been created, instances may be created from templates that are
available in the templates library. PlantStruxure PES permits the creation of
application and topological instances from the corresponding templates. Each such
instance may be further configured for specific uses in the application.
To access and configure their parameters, instances produce facets, which are
based on the facet templates that each control module template contains.
During the instantiation, it is possible to:
 Select services among those that the template provides. Some services are
mandatory (for example, Control logic) and some are optional.
 Edit the values of parameters (for example, provide a high limit value for an
analog level sensor).
 Link instances to each other (for example, link a motor instance to the instance
representing the functions of the variable speed drive that controls the motor).
When a service is selected, the software creates a facet, which is an instance of the
facet template that provides the service. This facet is associated to the instance of
the template that references the service.
Likewise, when a service is unselected, the software deletes the corresponding

facet.
This "configuration once" philosophy helps give consistent data across the various
participants and also assists to reduce the time needed to populate the same data in
multiple participants.

Instantiation of Objects (cont.)
Template The Template Browser provides an organised list of pre-built templates which may
Browser be incorporated into a System under development.
These Templates are displayed as an organised list, grouped by various functional

categories. Alternately, users may choose to display them as a purely alphabetical
listing.
The Grid View Button swaps from the default Tree View to the Alphabetical
listing; the Tree View Button returns the display to the hierarchical view.
Every Template displayed is provided with a version number. This helps to

manage changes to the template. It is possible to maintain multiple versions of a
single Template to permit the presence or absence of specific features.

Alternate In some circumstances, there are similarly-named Templates available in the

Template General Purpose Library.
Versions
For instance in the image above there are two AnalogInput Templates
($AnalogInput and $AnalogInput1).
Whenever this situation arises, it is recommended to use the Template with the
digit 1 at the end. In all cases, this is a newer Template, containing increased
functionality; the older version is retained for backward compatibility with earlier
projects built with previous versions of the software.

Template Types The various types of Templates can be recognised by observing the naming
convention, and also (when implemented) using the colours and symbols
(Standard Colour Palettes (page 4-25)):
Naming Convention:
$ A $ symbol at the beginning of a template name indicates that the

template has been provided by Schneider Electric.
The remainder of the indicators refer to naming suffixes.
_UL Unity Logic Facet Template
_UH Unity HMI Facet Template
_UC Unity Control (Logic and HMI) Composite Template
_CR Vijeo Citect Server Composite Template
_CC Vijeo Citect Client Composite Template
_CD Vijeo Citect Data Facet Template
_CG Vijeo Citect Genies Facet Template
_CS Vijeo Citect (Data and Genies) Composite Template
Standard Colour Entries in any part of a PlantStruxure PES configuration page that pertain directly
Palettes to the Control participant will be coloured pale blue, whereas those items of
relevance to the Supervision participant will be coloured orange/brown.
These are standard colours throughout Schneider Electric and will be seen in use
both on individual objects and as zone borders around sections of various
configuration pages.
Colour Usage
Orange Supervision components
Blue Control components
Green Mixed usage components

Edit Objects Whenever a template is instantiated into an Application, it may be customised to

suit that application. The various edit screens will differ depending on the exact
template being used and any editing will occur upon the instance, not the template
from which it was derived.
Default values from the template will become the starting position from which
edits may be made in order to best describe the actual control module being
modelled.
Selection of the various elements in the left-side hierarchical view will display
appropriate configuration views in the edit pane to the right. In addition, specific
features of the generic item may be activated via the various checkboxes in the
hierarchical view.
Observe the left pane in the image above - the numbers in brackets to the right of
each line represent the number of configurable elements and the number that have
actually been modified from their default. Additionally, each line in the hierarchy
represents a "rolled up" summary of all elements beneath it - the top line indicates
that there are 149 configurable elements in the entire object, of which just two have
been modified.

Invalid Objects Initially, this Instantiation is labelled 'Invalid' as there is a limit to the length of
various object names. PlantStruxure PES will issue warnings where necessary and
once a shorter name is applied (generally one that is not based on the template
name) the Status changes to 'Valid.'
An object can also be marked as invalid for other reasons such as object rules not
being met. These will be discussed later in the course.

Search and Filter A search and filtering tool is also provided and is discussed later in this course.
The search will operate in two modes. Firstly a simple search, where part of the
template name is typed into the search field. The search will commence after a
brief pause.
This tool will match any sub-string located at any point in a Template name. For
instance, val will return a list of templates that contain val anywhere in their
identifier, such as $HandValve_UC, $MValve, $ControlValve etc. The search text
is not case sensitive.
Alternately, there is an extended search, accessed using the small grey down-arrow
beneath the search field. Here, various status fields may be used to refine the
results.

Selection of Templates that will be used in the construction of a PlantStruxure PES System
Templates during this course will be found in the General Purpose Library (GPL). More
advanced applications will use additional sources - these will be provided as
separate industry-specific libraries.
Within that structure, the vast majority of such Templates will be found within the
Process folder (as indicated above). In general, the other folders will contain the
various Composites as described in Template Types (page 4-25).
The various templates may be accessed either by navigating the folder hierarchy or
by searching for specific names. In either case, users will quickly become familiar
with the names and locations of these Templates, particularly those which are used
frequently.
Selection of In the next few exercises, selected Templates will be used to model the plant in
Templates accordance with The Training Scenario (page 4-7).
During the design of this training course, appropriate Templates were selected to
properly achieve the desired outcome - these will be observed as the steps progress.
Later in the course (in Introduce the General Purpose Library (page 19-1)) a more
in-depth look will be taken to observe the various naming and design conventions
that these templates embody.

Model the The initial scenario will create the simulation for this waste water treatment plant,
Chemical focussed only on the Chemical Treatment process cell.
Treatment
Section The Process Cell is composed of a tank with a mixer and containing two level
switches, along with a temperature sensor. Water is introduced to the tank via an
inlet valve; there is also a flow indicator and a PID to control this subsystem. On
the outlet side, there is a discharge pump and security valve.
For Tank 1, the three primary operational zones will be defined separately (Tank 2
will be treated separately):
The folders to contain the equipment were created earlier. In the next few
exercises, objects will be instantiated to represent the equipment.

Exercise - Instantiate the Water Objects

Outcomes
 Be able to make use of existing template objects and apply them to specific
uses.
Instantiate four items into the Water object (in addition to the items
above, a Setpoint tool will also be included)
1 Configure the Water Equipment Module.

i. With the Browser tab selected in the lower left corner of the client
window, navigate to General Purpose Library » Process » Control
Modules » Signal Processing.

Exercise - Instantiate the Water Objects (cont.)
ii. Select the $AnalogInput1 template. This will represent the Flow
Indicator.
This will be used for the Flow Indicator object.

iii. Drag the $AnalogInput1 item to the Water folder in the right-side
pane.

Once the $AnalogInput1 template is dropped, the rectangle will

expand to display all enclosed items - only the $AnalogInput1
template instance in this case.
Note:
What has been added to the Water folder is a new Object which is based on the
$AnalogInput1 template.
Observe that the alias values previously assigned to all parent

objects (S1CTT1W_) have been added to the instance name and that
the item is marked as Invalid; this will be addressed in the next
step.
The item is marked as Unassigned (in blue). This indicates that

although this instantiation of the $AnalogInput1 template exists, it
has not been connected to an actual Control or Supervision project.
This will be done in Exercise - Assign Control Facets (page 6-17)
and in Exercise - Assign Facets to the Supervision Project
(page 9-10).
Note:
Only the $AnalogInput1 template should be used during this course.
iv. Right-click the item S1CTT1W_AnalogInput1_1 and select

Properties. Alternately, the item may be double-clicked.

v. In order to check the meaning of the Invalid status, click the
Information button.
This will indicate the source of the error. In this particular instance,
the name is too long.
The next step will replace the Template-derived name

(S1CTT1W_AnalogInput1_1) which is one character too long, with
the Equipment ID-derived name (S1CTT1W_FI1001).
vi. Close the Status Message dialog and complete the grey fields in the
lower right as follows:
Instance Name: FI1001

Instance Description: Flow Indicator 1001
Security Area: 1
vii. Configure the various check-boxes in the lower left pane to be as
follows (most will already be correctly selected):

Note:
These check boxes will enable / disable a variety of services defined in the
template, which may then be included in the Control and Supervision projects,
when they are created.
viii. Remove and then replace the check mark in the checkbox
"Hierarchical Name" to observe the alias prefix letters removed and
replaced. Observe that the name in the left pane is rebuilt, but the
one on the right is not.
ix. Save the properties view with the Save Button (located in the
upper right of the Properties view). Close the S1CTT1W_FI1001
tab.
Observe that the renamed FI1001 item is now labelled Valid.

2 Search for Items.
Sometimes, the location of a template in the hierarchy is not obvious

so the remainder of this exercise will rely on the searching tools in
the Client as a means of addressing this. The search tool is the
easiest way to find templates quickly.
The next item to be instantiated is the Control Valve, which will be

configured as an Analog Output.
i. Enter AnalogOutput in the Search field and pause briefly.
The system will display all results for the search.

Observe that there are four results. Referring to the list of Template
Types (Template Types (page 4-25)), it is clear that the
$AnalogOutput_UC, $AnalogOutput_CS and $AnalogOutput_CD are
sub-composites of the primary entry. Control modules have no
suffix - these are the ones to be used.
ii. Drag the $AnalogOutput item to the title bar of the Water object.
iii. Open the item and configure the Properties as follows:
Instance Name: CV1001

Description: Control Valve 1001
Security Area: 1
iv. Configure the various check-boxes in the lower left pane to be as

v. Save the Instance.
Observe that the Link field remains invalid after updating the
Properties. This will be resolved later in the chapter.
3 Add a PID controller.

i. Search for the $PID template and also drag it to the Water folder
title bar. Open the item and configure the following properties:
Instance Name: FC1001

Description: Flow Controller 1001
Security Area: 1
ii. Configure the various check-boxes in the lower left pane to be as
iii. Save and close the FC1001 item.
This item too has an invalid Link:

4 Add a SetPoint controller.

i. In the Browser, locate the template $SPReal and drag an instance to
the Water titlebar.
ii. Open the Properties of the new instance and configure as follows:
Instance Name: SP1001

Description: SetPoint Input Tool 1001
Security Area: 1
iii. Save and close the new instance. The completed configuration
should be similar to that shown below.

Labels When configuring the Low Level Switch in the next exercise, two Alarm
Configuration items are referenced.
The Privilege of Alarm Tag defines privilege level required by the currently
authenticated user in order to be able to enable the simulation mode of the object.
These Tags are defined as Labels within the Vijeo Citect environment. In this
instance, the Label may be dissected as SGC_PRIV_<type of
component>_<Type of action>. Type of Component (DI in this instance)
refers to a DigitalInput template; the action is obviously an Alarm.
See Also:
For further information about Labels, see PlantStruxure PES Help - Process
Supervision Services User Guide.

Exercise - Instantiate the Agitation Objects

Outcomes
 Be able to Instantiate template objects and configure them for specific uses.
Instantiate four items into the Agitation object.

(cont.)
1 Create the Agitator.

i. Create a new object in the Agitation folder:
Template Parameter Value

$Motor Name AG1002
Description Tank 1 Agitator 1002
Security Area 1
ii. Ensure that the checkboxes match the images below.

(cont.)
Note:
Running represents the running state
Fail provides a wired feedback signal
OPDOSignal is an optional Output signal to command the motor by wire
Maintenance is a separate utility to collect maintenance information (running

hours, starts & stops etc.).
iii. Select Supervision » Tags » InterlockTags. Set Interlock

Condition 1 Description to be Tank1 High - LSH1002 and Interlock
Condition 2 Description to be Tank1 Low - LSL1002 (the LSH1002
item will be created in the next step). Both Interlocks will be
implemented in later chapters of the course.
iv. Save and Close the item.
2 Create the temperature indicator.

i. Create a new object in the Agitation folder:

$AnalogInput1 Name TI1002
Description Tank 1 Temperature Indicator 1002
Security Area 1

(cont.)
ii. Open the path Control » AnalogInput1 » Logic and select the
Range section. Set the values the same as the image below:
Note:
For a variety of somewhat technical reasons the management of Supervision

information (Engineering Units etc.) is conducted in the Control portion of the
Instantiation. This will correctly be delivered to the Variable tag properties in the
resultant Vijeo Citect project.
3 Create the low-level switch.

i. Drag a $DigitalInput into the Agitation folder and configure it as
follows:

$DigitalInput Name LSL1002
Description Tank 1 Low Level Switch 1002
Security Area 1

(cont.)
ii. Select the Tags field in the left pane and set the field Name of the
Alarm Tag to be LAL1002.
iii. Save and close the LSL1002 item.
Note:
Almost every Template includes one or more alarms - the LAL1002 above being a
perfect example. Similarly the Agitator Motor includes a few alarms:
In order to keep the course simple, they will not be addressed further although
students are welcome to populate Alarm fields as they see fit.

(cont.)
4 Duplicate the object LSL1002 to create the High level Switch

LSH1002.
i. Right-click the LSL1002 instance and select Copy.
ii. Right-click in the Agitation pane title area and Paste the object.
iii. Edit the properties of the pasted item as follows:
Name LSH1002
Description Tank 1 High Level Switch 1002
Name of the Alarm Tag LAH1002
iv. Close and Save the completed object.

Exercise - Instantiate the Discharge Objects

Outcomes
 Be able to make use of existing template objects and apply them to specific
uses.
1 Configure the Discharge Equipment Module.

i. Instantiate the two Discharge items.

$Valve Name AV1010
Description Tank 1 Discharge Valve 1010
Security Area 1
$Motor Name P1010

Description Tank 1 Discharge Pump 1010
Security Area 1

Exercise - Instantiate the Discharge Objects
(cont.)
ii. While the properties pages of each of the two new instances are
open, ensure that the checkboxes match the images below (keep the
properties of the Pump open for the next step).
iii. For the Pump, expand Supervision » Tags in the left-side hierarchy.
iv. Select the entry InterlockTags. To the first message field, add the
message Pump stopped when Tank 1 valve closed.
Note:
This Interlock will be implemented later in the course.
v. Save the updated information.

Object Linkages
Edit Links Linking is used to establish relationships between instances.
Once the various discrete Instances have been instantiated and configured, an
Instance may be displayed with the link property marked as invalid. These must be
connected in such a way as to identify the correct interrelationships. This
connection is done using the Links Editor
Once the Links editor view has been loaded, the devices to be connected are
dragged into the edit view and the required interfaces are connected with a drag-
and-drop motion.
In the example a PID will always need a PV which will come from an Analog
Input. By dragging the PVRanged pin from the Flow Controller to the matching
pin of the Flow Indicator, the correct relationship will be established. Once a link
is completed, instances are re-aligned.

Object Linkages (cont.)
Def and Ref Any 'output' interface (generally referred to as a Def - for Definition - interface)
Defines the data to be used elsewhere. It is also known as a Producer and is
represented by a male-shaped interface or ball.
The 'input' is generally known as a Ref (for Reference) and Refers to data provided
elsewhere. It is also known as a Consumer and is represented by a female-shaped
interfaces or cup.
A link can only be made between a Producer and a Consumer although in some
cases multiple connections can be made at one or both ends of the link.
The 'channel' between the two interfaces may be considerably more complex than a
single data item and in all cases any degree of 'type mismatch' will cause the
connection to be refused.

Instance Link Whenever Links are needed but not yet built the status will show invalid and an
Status
Information Button will be displayed. This button will not be shown if the
Links are valid.
When this Information Button is clicked a Validation window will be displayed to

offer information regarding the required links.
Interface rule descriptions:
Required The link is required to satisfy the rule.

(green/yellow)
Prohibited Remove the link; otherwise the Status remains Invalid.

(red/yellow)
Required The link is made, which satisfies the rule.

(green/white)
Prohibited No link is made in accordance with the rule.

(Red/white)
Optional The link is optional and a link is made.

(Bold/white)
Optional The link is optional and no link is made.

(black/white)
In the image above, there are three rules, each of which is linked to a specific pin
name. The effect of this combination is that exactly one of the three pins must be
connected; the status will only be reassessed as 'valid' when that condition is
satisfied. If more than one pin is linked, the status will revert to 'invalid.'

Link Editor The Links Editor is only able to manage and create links for the Instance upon
Focus which the Editor was opened.
In images on previous pages, it may be observed that the PID Instance is given a
green border, while the AnalogInput Instance has a grey border. This indicates
that Links may only be established into or out of the PID.
Should a third Instance be dragged to the Links Editor canvas, it also may only be
connected to the PID Instance; it may not be connected to any other grey-border
Instance.
Here, an attempt is made to connect the AnalogInput PV signal to the

AnalogOutput RSP, which is refused.

Link Editor At any time, the Links Editor may be 're-focussed' onto a different Instance by
Focus (cont.) right-clicking the title area and selecting Edit Links. This will not delete any
existing links created for previous Instances - on exit, all Links created with any
Instance focus will be saved.
See Also:
For further information about the various pins on the blocks, see PlantStruxure
PES Help - Global Templates - Process » Process Templates - Description (the
$PID is discussed on p190). In addition, all pins provide a tooltip with a short
description.
Training Based on the previously described P&ID, the Links will implement this structure:
Scenario
This diagram demonstrates that two links are required for the PID (FC1001) to
operate. The first link will take the current value of the Flow Indicator (FI1001) as
a data source for the PID. In the second connection, the output of the PID will be
provided as an input to the Motorised valve.
Of course there is additional functionality to describe the parameters and control of

the PID - this will be managed via a popup page in the Supervision page. In
addition, a SetPoint was defined - this would not generally appear in the P&ID, but
a link will be constructed in the Links Editor to support this item.

Exercise - Link the Configured Objects

Outcomes
 Define the connections between instances.
1 Open the Link Editing tool.

i. Open the Water folder.
ii. Right-click the FC1001 object and select Edit Links.
iii. The link editing tool will open with the object loaded.

Exercise - Link the Configured Objects (cont.)
2 Examine the validation Status
i. Click the Information Button to open the Validation Status

dialog.
Observe that there are Required connections that are currently not
present.
ii. Select the Interface Element Rule tab. This gives greater detail of
exactly which data points are not being satisfied.
iii. Close the Status dialog.

3 Link the objects.

i. Drag the FI1001 object to the canvas (on the right) and drop it to
the left of the existing FC1001 object. This will remove it from the
tree view on the left.
ii. If necessary, drag the viewing pane to bring both the FC1001 and
FI1001 items are visible on either side of the screen. Alternately,
use the zoom tools at the bottom of the right-side pane.
iii. Click on the green interface to the left of the PVRanged line of the
FC1001 object; holding the mouse button down, drag to the female
interface beside PVRanged on the FI1001 object. As the mouse is
dragged, a line will be formed. When a validated connection is ready
to be made, a small black square will appear on the destination pin.
iv. Once the mouse button is released with the arrow in the 'cup', the
two objects are re-arranged and an orange-coloured connector is
drawn in place of the temporary arrow.
Observe that the "Status: Invalid" now shows "Status: Valid" as the
object is now properly connected.

4 Link the PID to the Control Valve.

i. Drag the CV1001 object onto the white panel (it will only be
permitted to drop on the left, even though it is best placed to the
right).
ii. Connect the RSPRanged pin on the CV1001 object to the
OUTRanged pin on the FC1001 object.
Once done, the CV1001 object will be re-positioned to the right of

the diagram.
iii. Finally, drag the SetPoint item to the canvas.

iv. Connect the SP1001 Real pin to the PID RSP input pin.
The completed structure will look like this:

5 Update the object.

i. Close the Links Editor tab.
All links associated with instantiated objects in the Water Equipment

are now marked Valid.
ii. Close the Water folder.

Chapter Outcome
Summary of All hierarchical components have been constructed and labelled according to ISA-
Activities S88 standard rules.
Objects have been instantiated from templates and configured for their individual
use.

Chapter Outcome (cont.)
Summary of Interconnections have also been defined.

Activities (cont.)

Summary
 The Training Scenario (page 4-7)

 System Folder Structure (page 4-13)
 Instantiation of Objects (page 4-22)
 Object Linkages (page 4-49)
 What is the difference between an Instance and a Template?
 When is Object Linking used?
 What does it mean to instantiate?
 What is the relevance of ISA-S88 to this chapter?

Chapter 5: Create the PAC Topology
Introduction
Introduction
The Topology Explorer is used to create the physical structure (the 'Topology') of
the control system. This includes the Controller and its modules and the
supervision stations (to be created in the next chapter) along with the remote I/O
and distributed I/O including drives, I/O islands and other network devices. It is
also used to define the networking infrastructure to connect these various devices
together.
 Construct a topological hierarchy

 Create M580 Controller representations in PlantStruxure PES
 The Scenario .......................................................................... 5-3

 Topology Folders................................................................... 5-5
 Create Controllers .................................................................. 5-9
 Convert to PlantStruxure PES Objects ................................ 5-16
Aim of this Chapter
Expected In this chapter, the precise configuration of the PAC equipment and the modules
Outcome they contain will be defined as well as the computers and networks.
 The first step will be to identify and configure the PACs to be used.
 Create a folder structure to accommodate all the equipment in the topology
 Create a M580, define the rack and configure networking
Work undertaken in this chapter will be confined to the Topology Explorer.

The Scenario
System The system architecture is represented in the following diagram:

Architecture
Three Operation, Control and Field networks will be established. These

Networks will be on separate Ethernet networks.
The Supervision Server and Engineering Station will be equipped

with two NICs to connect to Operation and Control networks.
Two M580_ePAC: M580. Control network on the CPU-integrated

Controllers Ethernet, Field network on the Device Network ports for Tank 1.
M340_PAC: M340: Control on CPU-integrated Ethernet; Field

network on the NOE for Tank 2.
Three Supervision Server: hosting the OFS server, one Vijeo Citect
Station Runtime server.
Nodes
Engineering station: hosting the OFS server, one Unity client and
one Vijeo Citect Runtime server.
Operation station: hosting a Vijeo Citect Runtime client and one

NIC.
Note:
Only the M580 Local Rack will be configured in this chapter. The remainder of
the architecture will be created in later chapters.

The Scenario (cont.)
Network PlantStruxure PES has a very strong basis in Ethernet and TCP/IP networking - this
Configuration will become very obvious as toe course develops.
This is the first point at which networking will be defined, so there is much in this
diagram that will not be encountered for some time, but is important to observe
very early in the course.
The training environment (as was noted on the previous page) comprises three
distinct networks.
Network IP Address Comments
Field 192.168.10.xxx The Field network will permit those field devices that are
Ethernet depended to connect to each other and to the
various controllers.
Control 192.168.50.xxx The Control network establishes connectivity between the
PACs and the various Supervision servers.
Operation 192.168.100.xxx The Operation network will distribute field data from the
Supervision Servers to the various Operation clients.
The various devices on the network will be given unique ID numbers - as noted in
the image above. In general, devices touching the Operation network will be given
IDs in the range 210 - 250, PAC devices are in the range 110 - 200 and field
devices are in the range 10 - 100.
For every interface, the IP address is constructed as 192.168.[Network ID].[device

ID]. This means that by simple inspection of any IP address, the role and location
of the interface may easily be determined.

Topology Folders
Manage the In PlantStruxure PES, the Topology refers to the physical infrastructure required to
Topology run the project - in particular, the Controllers and related equipment, along with the
Supervision station and network infrastructure.
The Topology Explorer is accessed from the right click menu on any system object
in the Systems Explorer view.
As was done within the Application configuration, separate folders are used to
isolate specific components. In this case they may be used to notionally separate
the configurations of multiple Controllers within a single system.
The Topology may be considered to represent the architecture of the system and
also, it becomes the entry-point for maintenance of the system.

Topology Folders (cont.)
The Folder As with the System Explorer and the Application Explorer, the Topological
Hierarchy Explorer, permits the creation of folders to organise the elements of the topology.
This will allow the creation control rooms, cabinets etc.
The following folder hierarchy will be created to reflect the real environment:
 OPERATIONS: this folder will contain the hardware description of the

supervision system. This section will be divided into sub folders as there are 3
station nodes.
- Project Development Room: this is the room from which the engineers
work, thus it contains the engineering station. It will contain the hardware
definition of the Engineering station node.
- Plant Control Room: this is the room from which operators control the
plant. Thus it contains the operation station. It will contain the hardware
definition of the Operation station node.
- Server Room: this is the data centre room in which the system servers are
located. It will contain the station node describing the hardware definition
of the system servers.
 NETWORK: this folder will contain the hardware description of the
communication networks existing across the plant.
 CONTROL: this folder will contain the hardware description of the control
systems. This part will be divided according to the plant control architecture
- M580 Equipment is used to contain definitions of M580 controllers
(mainly used for Tank 1)
- M340 Equipment is used to contain definitions of M340 controllers
(mainly used for Tank 2)

Exercise - Create the Topology Folder Structure

Outcomes
 Be able to create a folder representation of the topology to be used in the
project.
1 Create the Topology hierarchy.

i. In System Explorer, right click the Corsek object and select Open
Topology to launch the Topological Explorer.
ii. Create a folder beneath Corsek called Operations (default object

names may be changed in the same manner as was done in the
previous chapters).

Exercise - Create the Topology Folder Structure
(cont.)
iii. Continue to create folders as follows:
Parent Folder Sub Folder
Corsek Network
Control
Operations Server Room
Project Development Room
Plant Control Room
Control M580 Equipment
M340 Equipment
Note:
As previously suggested, folder structures do not affect the way the system works.
The completed structure will look like this:

Create Controllers
Controller A controller may be created by selecting Create Controller from the right-click
Creation menu then choosing the type of controller to create.
Available When a specific Controller is selected, PlantStruxure PES automatically restricts

Modules the available list of facets to match that Controller.
Restricted by
Usage For example, once the M580 Controller is chosen, the definition of the controller
hardware will be focused on M580 rack and hardware and only M580 relevant
hardware facets may be used.

Creating Controllers (cont.)
Configure Once a Controller has been created, PlantStruxure PES is able to spawn an instance
Controllers of Unity Pro inside the Virtual Machine to perform the detailed configuration.
The system will open the Control Participant.
Using the Unity Pro interface, the exact equipment rack to be used in the plant is
defined. This will include the definition of all modules and all communication.
In this case, rather than developing an entirely new tool to configure PAC
environments, a copy of Unity Pro is embedded into the system to handle this.

Exercise - Create the M580 Controller

Outcomes
 Be able to create a M580 ePAC controller for Tank 1.
1 Add a M580 Controller object.

i. Beneath the M580 Equipment folder, create a M580 Controller
entity.
ii. Name the controller M580_ePAC.

Exercise - Create the M580 Controller (cont.)
iii. On the properties dialog of the controller, configure the following

attributes:
Identifier M580_ePAC (already done)

Description Standard M580 Controller
Area 1
The Controller Family value (M580, in this instance) was

automatically configured when the option to create a M580 Controller
was selected.
iv. Close the dialog box.
Observe that the Controller is now present in the hierarchy, but is

currently labelled as Not Mapped. This indicates that there is no
Project mapped to the Controller. This mapping will be created in
Exercise - Map the Control Project (page 7-8).

Exercise - Define the M580 Rack

Outcomes
 Be able to configure a M580 rack.
1 Open the Control Participant.

i. Right-click the recently-created M580_ePAC and select Configure.
This request will take a few moments to execute as the

PlantStruxure PES software must establish a remote connection into
the VirtualBox VM which is hosting the Unity Pro installation. Observe
the message in the Notification Panel at the bottom of the screen,
indicating that Unity Pro is loading and the spinning wheel which will
remain until the Unity Pro software is fully loaded.
ii. Click the Extract Participant button to extract the control

participant, and then click the Maximise button to maximise to full
screen.

Exercise - Define the M580 Rack (cont.)
2 Configure the M580 Rack.

i. Use the Unity Pro interface to configure a M580 rack configuration as
follows:
Rack BME XBP 0400 4-slot rack
Power Supply CPS2000
Controller P582040 (V2.10) Slots 0 & 1
Digital I/O DDM16025 Slot 2
Analog I/O AMM0600 Slot 3
The completed configuration will look like the following:
3 Configure Security for the M580

i. Double-click the Ethernet port on the front of the M580 CPU

Exercise - Define the M580 Rack (cont.)
ii. Click the Unlock Security button to disable all security for the M580.
Note:
This would not be recommended for a live system but it makes it easier to
configure the M580.
4 Configure networking for the M580

i. Click the IPConfig tab and configure the IP addresses as below:
+
ii. Click the Validate tickbox to save the configuration changes in the
Control Participant.
5 Import the Configuration.

i. Click the Restore Participant button to return the Unity Pro
interface from full-screen.
ii. Click the Save Instance button to save the Unity Pro
configuration just built. Depending on the performance of the
computer, this may take a significant number of seconds to
complete.
iii. Once done, close the Unity Pro pane.
Note:
Do not close or re-open the Unity Pro interface prior to the completion of the save
process. Doing so will cancel ALL changes being saved.

Convert to PlantStruxure PES Objects
The Bottom-Up As was seen in the previous exercises, the Control Participant is opened to be used
Process as a tool to create a valid rack structure.
When the Save Button is clicked, the Bottom Up process is instigated.

PlantStruxure PES looks in the Foundation library for corresponding Templates
based on the configuration made in the Control participant, the corresponding
instances are created automatically and displayed in the Topological Explorer.
Once the bottom-up process is finished the system displays again the controller
window with the populated template that describes the chosen PAC configuration.
The outcome of this process is to create a validated list of Modules installed into a
PAC rack. Once this Module list is returned to PlantStruxure PES, it is converted
to a list of matching templates.

Convert to PlantStruxure PES Objects (cont.)
The Bottom-Up
Process (cont.)
Note:
At this point, it is only possible to construct the hardware Configuration and

Communication systems as these are the only components imported back to the
PlantStruxure PES environment. Should any other pieces be worked on while
Unity Pro is open, they will be lost when the Control Participant is closed.
Unknown Currently, PlantStruxure PES does not support all possible rack Modules (for
Modules instance the 140 NOC modules in a Quantum architecture) and will use a "place
marker" to indicate Modules that it cannot support.
Here, the second line indicates a 140NOC Module and has been instantiated with
the $UnknownModule template. This will be fine for creating the basic structure,
but must be manually addressed later in the development process.

Exercise - View the Configuration in
PlantStruxure PES

Outcomes
 Be able to observe M580 PAC configuration in PlantStruxure PES.
1 Expand the tree below the PAC representation.

i. Using the triangle symbols on the left side of each object, expand
the PriLocal tree structure as deep as it will allow.
Each of the entries in the lists represents an instantiation of the

relevant Template to match the equipment selected during the
construction of the rack. This includes rack slot numbers and all
related information required to recreate the rack. Should it have
been expanded, the EthRIO would appear similar.
ii. Confirm all entries are labelled valid in the State column.
There is a template for everything including the rack, field bus, etc.

Exercise - View the Configuration in
PlantStruxure PES (cont.)
2 View the Template details.

i. In the PriLocal pane, right-click the Mixed Digital object and choose
Properties.
ii. Expand the Module sub-section.
iii. Observe that all relevant information is available.

iv. Close the Mixed Digital object tab.
v. Optionally open other modules (perhaps the CPU module) to observe
their configuration.
vi. Close the tree structure back to the M580_ePAC object.

Chapter Outcome
Summary of At this point, the broad structure of the PAC hardware has been created.
Activities
The M580 rack configuration has been built but with no program or links to the
I/O. This will be created in the next chapter Create the Control Project (page 6-1).

Summary
 The Scenario (page 5-3)

 Topology Folders (page 5-5)
 Create Controllers (page 5-9)
 Convert to PlantStruxure PES Objects (page 5-16)
 Describe the relationship between the Application and Topological Explorers.
 Which Controllers are supported by the current version of PlantStruxure PES?
 What is the purpose of creating folders?

Chapter 6: Create the Control Project
Introduction
Introduction
The Project Explorer is intended to combine the previously built structures from
the Application and Topology, into the full Control and Supervision projects that
can be deployed into the field. In this chapter, the Control Projects will be
constructed. Supervision will be handled in later chapters.
 Access existing project components and successfully create a valid project

containing Control components.
 Generate the Control Project
 Refine the Control project to add extra functionality as required.
 Create a Control Project ........................................................ 6-4

 Assign Facets ....................................................................... 6-10
 Generate ............................................................................... 6-22
 Refine the Control Project ................................................... 6-25
Aim of this Chapter
Expected In this chapter, the programming for the Control environment will be developed.
Outcome
Earlier in the course, when the various templates were used to instantiate the
representation of physical objects, a set of Instances, Objects and Control modules
were defined for each device. In this chapter, these Facets will be drawn together
to create the control logic (variables, EFB, DFB, instances of DFB etc.) for the
Control project.
Once the Control project based on these components has been created, it may be
refined by manual configuration.

Aim of this Chapter (cont.)
Expected Work undertaken in this chapter will be confined to the Project Explorer.
Outcome (cont.)

Create a Control Project
Open the Project With the overall structure of the system now created, the next stage is to create the
Explorer actual Control project. This is done using the Project Explorer.
As with the Application and Topology Explorers, the Project Explorer is accessed
from the right click menu of the System object in the Systems Explorer view.
Once opened, there are a number of initial options available to configure the
project.

Create a Control Project (cont.)
Control Project Control projects may be created for Quantum, M340 and M580. In addition, an
Management existing STU file may be imported into the project.
Note:
The .stu file to be imported must have been created with the same version of Unity
Pro as is in the Virtual Machine (v11) to be able to use for import. Where this
cannot be guaranteed, it is recommended that .sta files be used instead.
Also at this point, a Unity Pro project may be created and developed. In addition,
the project may be exported (or imported), this will be shown in Import and Export.
Once a new Control Project is created, all of the major elements are visible in the
tree view:
There are also a number of options available for operation upon the control project
itself.

MAST and FAST The Master task (MAST) represents the cyclic processing of the PAC and will be
Tasks where most of the program is created and executed. The Fast Task (FAST) is used
for processing of events and code that is critical to the process and cannot be
handled by the slower Master Task. For this reason the FAST task should only be
used for critical program sections.
Note:
PlantStruxure PES only supports FBD program sections.

Exercise - Create the Control Project

Outcomes
 Create a Control logic project.
1 Open the Project Explorer.

i. On the Systems Explorer view, right-click the Corsek System and
select Open Project.
ii. The Project Explorer will be opened on a new tab labelled Corsek.
2 Create a M580 project.

i. Right-click the newly created Corsek object and select Create
Control Project » M580.
ii. Rename the new Control project as Tank1_Control.

Exercise - Create FBD Sections

Outcomes
 Create Control Project FBD sections.
1 Create the FBD section.

i. Expand the Tank1_Control object to reveal all components.
ii. Right-click the MAST object and select Create FBD Section.
The Containers view of the MAST object will be opened

automatically.

Exercise - Create FBD Sections (cont.)
iii. Rename the newly created FBD section as Water.
iv. Right click in the title section of the MAST dialog box to create two
additional FBD sections (the earlier step to create the first FBD
Section could have been used multiple times instead of using this
alternate method).
v. Rename the new FBD sections as Agitation and Discharge.
vi. Close the MAST dialog box.

Assign Facets
Blocking Point It is not possible to proceed beyond this point in the Project Editor unless the
various steps in Create the Application (page 4-1) have been completed.
The Assignment Viewed from the Application Explorer, it is clear that a number of Template items
Process have been instantiated.

Assign Facets (cont.)
The Assignment Each of these Instantiations contains a number of Facets - representing either
Process (cont.) Control (in blue) or Supervision (in orange) components.
the role of the Assignment Editor is to extract the relevant Facets from each
Instantiation and make them ready to be combined into a single (in the current
situation) Control Project; the Supervision will be treated in a later chapter.

The Assignment The engineer will use the Assignment Editor to take the Control facets from the
Editor instances defined in the application and Assign them to the Control project. This is
the only way to distribute the instances (as defined in the Topology) into the
various Control Project sections.
In order to draw together the relationship between Application Templates and FBD
Sections, the Assignment Editor provides a drag-and-drop tool to assign Instances
to Containers.
The Containers displayed in the lower-left pane above are direct references to the
MAST Sections created in Exercise - Create FBD Sections (page 6-8). Deleting
an item in either the Assignment Editor or in the MAST dialog will remove it
from both locations. These Containers may only be created as new FBD Sections.

Modify Any assigned facet may be modified using the right click menu.
Assignments
Unassign Remove the Facet Template from the Section before and after a
Generate. Before a Generate the Reassignment is done by Drag &
Drop of the Template, after a Generate use Reassign.
Reassign Reassign a Facet if it was Unassigned or Unlinked after a Generate.
Unlink Remove the link between the Facet and the system, to modify what
the system has generated, directly from the participant.
Relink Recreate a link that has been removed.
Go To In the Application Explorer, open the Instance linked to this specific

Instance Assignment.
The simple requirement of the Assignment Editor is to "put the correct code in the
correct container." In other words, it is important to be sure that each Container (or
MAST / FAST Section) is given the PLC code relevant to its operation.
At this point, only two further actions are required to have the system logic ready
to be generated.
 By default each assigned instance creates a section to execute the logic. If it is

desired to assign the logic of various instances in the same section container, a
section may be manually created, and the facets later assigned to this section.
 Identify in the application the objects that are going to be managed by the
Control project logic. This step is called the facet assignment.
The containers can be created manually by the developer or automatically by the
system.

Four Ways to The Assignment Editor interface offers 4 subtly different ways to assign Facets.
Assign Facets
Option 1
Drag an individual Instance to the 'drop here' location at the head of the
assignments pane.
Option 2
Assign an application folder from the instances section directly to a container.
Here, all the facets of the instances of the application folder will be assigned to the
same container.

Four Ways to Option 3

Assign Facets
(cont.) Drag a folder of Instances (at any level) to the 'drop here' location. All objects
within that folder will be assigned.
Option 4
Drag individual Instances from the instances pane to the Assignments pane.
It is also possible to use the <SHFT>-click and <CTRL>-click functions to select

multiple entries.
Note:
If instances have already been assigned, only options 1 and 3 are available.

Four Ways to Focus for a moment on the assignment with automatic creation of containers. This
Assign Facets is the Option 3 on the previous page describing the assignment process.
(cont.)
The correct system approach is to use the intelligence of PlantStruxure PES to
automate the system in a consistent way according to the system definition done in
the Application Explorer.
Indeed, PlantStruxure PES will use the functional description of the system to
create functional modules corresponding to the equipment modules. Therefore it is
better not to create sections and instead use the Option 3 described previously. A
further option is to create sections corresponding to a functional entity (as will be
done in the exercise). This will be helpful for the maintenance as all the function
blocks controlling a part of the system will be in the same section.
The alternate, creating one section per Function Block will create many sections,
with multiple variables to do the links between the FB.
FBD Complexity As was observed above, any situation where FBD Sections are not created prior to
Assignment will lead to one new Section being created for each facet (with the
same name as the facet). This of course will lead to a large number of Program
Sections.
On the other hand, creating a minimal set of Sections to contain a significant

number of facets is also problematic for two reasons.
Firstly that the likely number of objects in a single Unity Pro Refinement screen
will make troubleshooting and additional editing rather complex and secondly,
without knowing the size and complexity of individual facets, it is not possible to
know in advance whether the maximum size of a DFB Section will be exceeded.

Exercise - Assign Control Facets

Outcomes
 Be able to assign facets to sections.
1 Assign Facets to the Sections.

i. Right click the Tank1_Control object and select Assign Facets.
The Assignment Editor will be displayed.

Exercise - Assign Control Facets (cont.)
ii. In the upper left pane, expand the Site1 » Chemical Treatment »
Tank1 tree to view all instance folders (there is no need to expand
the final levels).
Note:
These are the objects created in Instantiation of Objects (page 4-22). In the lower
left are the FBD Containers created earlier in the previous exercise. These will be
Sections in the Control Participant.

iii. Highlight the Agitation item in the lower left pane. This will give
focus to the next operation.
iv. Drag the Agitation folder in the upper left pane (Instances) toward
the lower right pane (Assignments).
Use this diagram as a guide:
v. As the Agitation folder is dragged, a green dotted box will appear

above the Assignments pane labelled "Drop here to assign drag
instances to Agitation."

vi. Release the mouse to complete the Assignment.
vii. Highlight the Discharge item in the lower left pane and drag the
Discharge item from the upper left pane to the lower right.
viii. Repeat for the Water Container.
ix. Selecting the Root object in the Containers pane (lower left) will
display all Assignments (for Agitation, Discharge and Water) in the
Assignments pane.
x. Close the Assignment Editor by using the close button on the

Tank1_Control tab.

2 Inspect the changes in the Application Explorer.

i. Return to the Application Explorer.
ii. Navigate to the Tank1 folder beneath Chemical Treatment and open
each of the three sub-folders.
iii. Observe that all Instances are now marked as Assigned.

Generate
Generate a The Generate function is available on the right click menu of any Control Project
Control Project and any Section.
The process of generating a PlantStruxure PES System will import all the
elementary Unity facets into the FBD section on which they have been assigned
and then create all of the Control logic needed.
The Generation will create an XML representation of a Unity Pro STU file. This
this may be used to populate Unity Pro with:
 The Sections and Instances configured

 All corresponding variables
 With an empty configuration
 No IO Mapping or Communication configuration

Exercise - Generate the Control Project

Outcomes
 Be able to Generate a Unity Pro project from the configured PlantStruxure PES
project.
1 Generate the project.

i. In the Project Explorer tab, right click the Tank1_Control object and
select Generate.
The Generate process will take some time; the Notification log will
record a pending event in the Notification Panel - observe the
spinning wheel to the left of the top-most entry.
If completed successfully, the system will mark the Generate line in

the Notification Panel as Completed. The spinning wheel will change
to a green check mark.

Exercise - Generate the Control Project (cont.)
2 View the generated project.

i. Right click the Tank1_Control object and select Refine.
The system will spawn an instance of Unity Pro.

ii. Once opened, use the Extract Participant button and maximise
the participant to gain a clearer view of the project
iii. In the Project Browser pane, expand Program » Tasks » MAST »
Sections and Double click the Water object to view the Function
Block Diagram for that component.
This is also the interface through which users may extend the
functionality beyond what is possible using the PlantStruxure PES
tools. This will be done later in this chapter.
iv. Restore the participant to the PlantStruxure PES main view and
close the Control Participant view.

Refine the Control Project
Refine the Once the relatively high-level configuration of the Control project is completed,
Project there are often situations where additional configuration is required. To this point,
the automatically-generated Control project has been inspected, but not modified.
It is obvious that PlantStruxure PES cannot be aware of the specific details of a

plant - what interlocks are in place, details of equipment (perhaps a particular
motor must be run in idle for 5 minutes before it is permitted to take a load) and so
on.
To open the project in the Control Participant, the Refine command should be
used.
When refining, the following aspects of the project may be operated upon:
 Derived Data Types

 Derived FB Types
 Variables & FB Instances
 Program (including all IEC languages - ST, LD, IL, SFC, FBD)
 Animation Tables
 Operator Screens
 Documentation
 Project settings
Manual refinements to the Control Project do not require Generation as they were
not created by PlantStruxure PES. These changes will be incorporated into the
deliverable project during the Build phase.

Refine the Control Project (cont.)
Refine Sections Users have the choice of refining either the full project or an individual section.
The ability to refine a single section is very important with the ability for
PlantStruxure PES to handle multi-user capabilities. Locking the entire Control
participant will not be a good idea.
During refinement, existing Sections may be checked and also new logic added.
Here, the specific knowledge of on-site Engineers may be used to ensure the plant
is modelled and controlled as accurately as possible.
Be aware that new Sections may be created using any IEC languages to implement
additional functionality.
Manual refinements to the Control project do not need to be generated as they were
not created by the system. Such changes will be incorporated into the final project
during the Build phase.
The FBD logic may be refined at the Project level or at the Section level. In the
case of the Section level, the Control Participant does not open the Project screen
but the only the Section screen:
In this particular scenario, the Agitation object is accessed from the MAST object
beneath the Tasks object.
Accessing the Control participant project in this manner will focus directly to the
FBD selected.

Exercise - Refine the Control Project

Outcomes
 Be able to modify and customise the project.
1 Directly access the Section in Unity Pro.

i. Open the Tank1_Control » Tasks » MAST folder.
ii. Select the Agitation object.
iii. Right click the Agitation object in the MAST - Containers pane and
select Refine.

Exercise - Refine the Control Project (cont.)
This will open the Unity Pro interface with the Agitation Function
Block Diagram already visible in a stripped-down interface containing
only the Function Block Diagram editor.
Be aware that in this image, the arrangement of the function blocks

has been changed in order to better display them for the training
manual. Laying out the FBs in a manner similar to that shown will
simplify the next step.
iv. Maximise the Unity Pro view.

Exercise - Refine the Control Project (cont.)
2 Refine the Control project.
Create an interlock such that the Agitator cannot operate when the
water level is below the Low Level switch.
i. Click the Link Button on the Unity Pro toolbar.

ii. Drag out a link from the PV pin on the S1CTT1AG_LSL1002
(DINPUT Block) to the COND02 pin on the S1CTT1AG_AG1002
block (CONDSUM1 Block).
Note:
CONDSUM1 is a system-supplied DFB to implement interlocks. CONDSUM

manages Failure functionality. Ensure CONDSUM1 is used in this step.
Note:
A matching interlock on the High-level switch will be added later in the course
using a different method.
iii. Save and Close the Unity Pro window.

Check PlantStruxure PES provides a tool to check the consistency of the Control project.
Consistency It is available from the right-side tool bar on the Control Participant in Refine
mode.
The Consistency Check will ensure that the logic Generated by the system is valid.
Thus, if any of the logic generated by PlantStruxure PES is removed, the
consistency check will fail.
Clicking the Check Consistency button will immediately launch the tool, which
will take a few moments to execute.
Consistency management consists of:
 Requesting the software to start the consistency check of a logical Control

Participant project or section of such project.
 Detecting if the constituents or facets that the software has generated in such
project or section are consistent with the related Facets that are assigned to the
Control project or section:
- If yes, displaying a message to inform that the Project is consistent
- If not, displaying a message to inform of the detected inconsistencies and
changing the Generation status of the related facets to Inconsistent
 Attempting to fix the detected inconsistencies by restoring the constituents
inside the logical Control Participant project or section to a state that is
consistent with the related facets of the Control project or section. Although
reporting such issues, the Consistency Checker does not instigate any repairs;
those are the responsibility of the user.

Check The purpose of consistency management is to provide means to determine whether

Consistency changes made during refinement affect the logic of the Control Participant project
(cont.) and, if desired to manually fix inconsistencies when it is possible without
modifying the refinements made.
The software automatically performs a consistency check when:
 a facet is re-linked with the status Unlinked

 the logical Control project is updated
Note:
The software does not perform consistency checks on facets with the status
Unlinked. This feature permits inconsistent fragments to be isolated for later work.

Exercise - Check Consistency

Outcomes
 Be able to execute and interpret the results of a consistency check.
1 Open the Control Project as if to Refine it.

i. Locate the Tank1_Control project item and right-click it.
ii. On the right-click menu, select Refine.
iii. Once the Control Participant interface opens, click the Check
Consistency button.
iv. After a few moments a results window will be displayed.
Observe that (assuming inconsistencies were detected) the results

are grouped according to the three MAST containers. There should
be no Errors.
v. Close the Check Consistency results window.

Chapter Outcome
Summary of A Control Project was created and FBD Sections created to manage the
Activities organisation of the various pieces of PLC code.
Next, the Facets were Assigned to each of the three sections.
The Control Project was then Generated and Refined.

Summary
 Create a Control Project (page 6-4)

 Assign Facets (page 6-10)
 Generate the Control Project (page 6-22)
 Refine the Control Project (page 6-25)
 What is a Control project?
 What does assigning facets do?
 Why might you need to refine a project? Give some specific examples.

Chapter 7: Finalise the Control Project
Overview
Introduction
Up to this point, the System has mainly been created using the three independent
explorers. This chapter will combine the configurations created in the three
explorers and create an executable that can be deployed to a PAC.
Chapter By the completion of this chapter you will be able to:

Objectives
 Create a Control executable
 Map the executable to real hardware
 Optionally deploy the executable to a real PAC
 The Control Executable ......................................................... 7-3

 Mapping ................................................................................. 7-7
 Build the Control Project ..................................................... 7-18
 Deploy the Control Project .................................................. 7-23
Aim of this Chapter
Expected In this chapter, the programming for the Control environment will be completed.
Outcome
A Control Executable - the framework for constructing a Control project ready to
be deployed to the PAC will be created. Next, the specific PAC (defined in the
Topological Explorer) will be linked and after that, the various logical IO data
points will be linked to the physical data points connected to the various IO
modules on the rack previously defined.
Subsequently, the Executable will be Built and then Deployed to the run-time
environment.

The Control Executable
Connect with the The process of 'Mapping' will take a logical Control project, such as has been
Real World constructed to this point in the course, and connect it to the real world by
identifying the specific PAC the project will run and the physical I/O addresses to
which logical I/O objects may be bound.
It is only at this point that the work done previously will be connected to physical
devices.
What is a A Control Executable permits the mapping of Services (topological entities),

Control Hardware (I/O modules) and Communication (Communication channels) to the
Executable? logical Control Participant project. A logical Control Participant may be mapped
to several Services - a separate Control Executable is required for each.
For example, a single logical Control project may be mapped to both:
 The controller that is in the plant, using executable_A.

 Another controller that is in the laboratory for test purposes by using
executable_B.
The Control Executable represents the complete set of components ready to deploy
to an execution platform.

The Control Executable (cont.)
Execution The Execution Domain is a free-text property of all Executables (both Control and
Domain Supervision) that may be used to arbitrarily define the boundary of a common
domain. This fully customisable domain might be defined as a physical network
or may be defined in a more logical fashion. Once typed into an Execution
Domain field, the value is available in the drop-down list of all other Executables.
The Execution Domain serves as a filter for selecting applicable services, for
example, to define the boundaries for navigation services, or peer to peer
communication. Variables may be exchanged through peer to peer communication
or use Navigation services between projects only if their Control Executable and/or
Executable have the same Execution Domain value. The restrictions imposed by
the use of an Execution Domain may be observed when Peer-to-Peer Services are
configured in the PlantStruxure PES Advanced Training Course.
The Execution Domain parameter may be modified at any time during the
engineering lifecycle.
Note:
Leaving the Execution Domain parameter empty is considered as a value with the
effect of creating a single Execution Domain across the entire System.
The restrictions imposed by Execution Domains apply in two specific instances - in

both situations, communication will only occur between entities that share a
common Execution Domain:
 Run-time services navigation (allows access to services defined for the

execution domain)
 Peer-to-Peer communications.
The Execution Domain parameter may be modified at any time during the
engineering lifecycle.

Exercise - Create the Control Executable

Outcomes
 Be able to build the Control Project to be deployed in the real Controller.
1 Create the Control Executable.

i. Expand the Tank1_Control tree.
ii. Right click Executables and select Create Executable.
iii. After a few moments (to permit the action to take place), the
Executables will display the newly created ControlExecutable_1.
Name it Exec.

Exercise - Create the Control Executable (cont.)
iv. Configure the new ControlExecutable as follows:
Identifier Exec (already done)

Description Tank1 Control Executable
Execution Domain Site
v. Close the Exec Properties view.

Mapping
Map a Control Within the Executables, a ControlExecutable item will provide access to the
Project to a mapping Services and the mapping hardware for the current ControlProject.
Controller
The ControlExecutable (here named Exec) object provides services to:
 Create the executable code of the project that run in the Controller
 Map logical I/Os to physical I/Os that are described in the Hardware
configuration
 Create communications between the controller and external devices or remote
I/Os
 Add peer-to-peer and third party device communications

Exercise - Map the Control Executable

Outcomes
 Be able to build the Control Project to be deployed in the real Controller.
1 Map to the Controller.

i. Right-click the newly created Exec executable and select Map
Service.
ii. Once the Exec dialog box opens, click on the drop-down to the right
of the Engine field to open the list of available services. This will
display all controllers defined previously.
iii. Select the M580_ePAC item.
Note:
If there are multiple controllers in the list, only one may be linked to a
ControlExecutable - multiple executables must be created to be able to deploy the
project to other controllers.
iv. Close the Dialog box.

Mapping (cont.)
Elements of The zone to the left of the screen represents the physical IO modules configured
Mapping previously (see Exercise - Build the M580 Rack (page 5-13)). In particular,
Hardware observe the column HW Mapping; this clearly contains a separate entry for each
physical channel on each of the IO modules configured for the PAC. To the right
is a list of the facets that may be mapped to real channels.
Hardware mapping allow the user to map instances to available channels defined in
the hardware configuration of the controllers. It's also the perfect view of channels
used, and a quick view of the free channels than may be used for future maps.
The hardware mapping is also an abstract way to physically map the facet. The
engineer doesn't have to deal with the naming convention imposed on the
participant. It means that the user doesn't have to remember the topological
address to be used because the system is sufficiently smart to provide an
appropriate address.
By performing this configuration, the system will automatically configure the

correct address for each variable.

Mapping (cont.)
Display When mapping the Control hardware, the overall intention is to link the abstractly
Compatible defined data elements that were defined in Templates (and then instantiated into
Interfaces various plant representations) to the physical wire connectors on the various PAC-
hosted data modules.
It is clear that a data point in the system has a data type; it is equally clear that such
a data point can only be reasonably connected to a physical connection of the same
data type.
Control Hardware Mapping tool provides a check-box (enabled by default) that

will take notice of the items selected on one side of the process and only provide
visibility to matches on the other side. This is the checkbox to the upper-right of
the window called, "Display only compatible interfaces on filtering."
With no filter in place, all possible matches are provided, but as soon as some form
of filter is applied - perhaps for an Analog Output Facet Instance, then ONLY
Analog Outputs on the hardware definitions will be visible.
This checkbox delivers two related advantages. Firstly, it becomes impossible to

connect facet Instances to Hardware Instances of a different data type. Secondly, it
dramatically speeds up the mapping process as, as soon as a filter is applied to one
side of the tool, it is also implicitly applied to the other side.

Mapping (cont.)
Sort and Filter Having defined data points, both in the physical connections to field devices and in
the logical definition of the PlantStruxure PES System, the next step is to map one
to the other.
Clearly it is important to ensure that all data types match during this process, and
although PlantStruxure PES will refuse to allow a mismatch, it is easier to create
the situation where it is not possible.
By using a variety of filtering techniques, it is possible to display just one type of

logical or physical item - an Analog Input for example. With this only displayed it
is a simple matter to map the correct data types together.

Exercise - Map the Control Hardware

Outcomes
 Be able to link the Control Project to specific terminals in the real Controller.
1 Map the Hardware.

i. Right-click the Exec Executable again. Map Hardware is no longer
greyed out as the controller together with its I/O configuration is
now known. Select Map Hardware.
ii. When the Hardware Mapping tool loads, observe that Physical
instances are in the left pane; Logical instances in the right.

Exercise - Map the Control Hardware (cont.)
iii. Drag the FI1001 object in the right pane to one of the DInputCh
entries in the left pane.
This will not be permitted by PlantStruxure PES as the operation is

asking the system to map a Logical Analog channel to a physical
Digital channel.
iv. Click the Filter button at the head of the Instance column (in the
left pane). This will display the filter tool.
Observe that an entry is displayed for each of the various IO

modules previously configured.

v. Select the item $AIChannel/HO; and click the Filter button at the
bottom of the dialog. This will show only the 4 Analog Input
channels in the left pane.
vi. Click anywhere outside the filter dialog to close it.
This will force the window to display only matching data types on
either side of the dividing line.
The checkbox to the upper right, "Display only compatible interfaces

on filtering" governs whether or not the filters applied on one side of
the window will have an effect on the other. Remove the check
mark.
Observe that as well as re-populating the entries on the right side,

removing the check mark will reset any filters currently applied.
vii. Replace the check mark but do not re-apply the AIChannel/HO filter.
To assist with enforcing the proposed connection arrangement,

further filters may be applied to limit the visibility of both the Project
Facets and the Hardware Instances.
2 Add filters to limit Facets and Instances.

i. The best way to uniquely identify Facets belonging to the Water
equipment module is to note that all names start with S1CTT1W.
Apply this filter to the Instance column in the right side of the
window.
Click the Filter Button in the dialog box to complete the filter.

ii. The filter will identify one Analog Input and one Analog Output
instance in the right side and on the left, a set of eight Analog Input
and four Analog Output hardware interfaces suitable for them to be
connected to.
Note:
In a more complex environment it may be necessary to apply multiple concurrent

filters to simplify the process of hardware Mapping.
iii. Drag the CV1001 Instance on the right to a suitable entry in the left
pane. As it hovers over the Input channels, PlantStruxure PES will
refuse a connection, but as soon as it reaches an Output channel, it
may be validly connected.

iv. Scroll toward the right in the left pane. The instance columns will be
populated with information related to the item just dragged over.
Should an item be incorrectly mapped, it may easily be dragged back

from the left pane to the right to un-map that item.
Note:
The third Water Instance (FC1001) will not appear as it is a PID unit which is
(obviously) not directly connected with the hardware - its connections were created
when it was Linked to the other objects in Object Linkages (page 4-49).
v. Map the Water, Agitator and Discharge sections to appropriate

hardware instances using the following tables.
Digital Inputs:
HW Mapping Interface Instance

MPDInputCh_1 S1CTT1A_AG1002_Motor_FAIL
MPDInputCh_2 S1CTT1A_AG1002_Motor_ZSH
MPDInputCh_3 S1CTT1A_LSH1002_DINPUT_DIS
MPDInputCh_4 S1CTT1A_LSL1002_DINPUT_DIS
MPDInputCh_5 S1CTT1D_AV1010_ZSL
MPDInputCh_6 S1CTT1D_AV1010_ZSH
MPDInputCh_7 S1CTT1D_P1010_Motor_Fail
MPDInputCh_8 S1CTT1D_P1010_Motor_ZSH

Digital Outputs:

MPDOutputCh_1 S1CTT1A_AG1002_Motor_OP
MPDOutputCh_2 S1CTT1D_P1010_Motor_OP
MPDOutputCh_3 S1CTT1D_AV1010_VALVE_OP
Analog Inputs:

MPAInputCh_1 S1CTT1W_FI1001_AINPUT1_AIS
MPAInputCh_2 S1CTT1A_TI1002_AINPUT1_AIS
Analog Outputs:

MPAOutputCh_1 S1CTT1W_CV1001_AOUTPUT_AOS
vi. Once there are no facets remaining in the list on the right, close the
Tank1_Control.Exec Hardware Mapping tab.

Build the Control Project
Build The build process creates an executable that can be downloaded to the PAC. This is
very similar to the Build process in Unity Pro and a project cannot be downloaded
to the PAC unless it has been built.
In PlantStruxure PES the executable must also be built before it can be deployed to
a PAC and an indication of the executable's build state is displayed

Exercise - Build the Control Project

Outcomes
 Build the Control Project.
1 Build the Control Project.

i. Right-click the Exec Executable and select Build All.
This process to merge the logical control project with the hardware
mapping defined previously will now occur. Students may wish to
observe the Server status window to track progress.
Once done, a status screen will display the success (or otherwise) of
the process.

Exercise - Build the Control Project (cont.)
An extended view of the Build status is available via the small down-
facing arrow-head beside the word 'Details.'
ii. Confirm that the main message states "Build Successful!"
Note:
If the message is not "Build Successful," then the number of errors shown on the
final line will be one more than the actual error count - the additional error is
essentially, "I didn't successfully complete the process." If any errors are present,
scroll back through the listing on the Results dialog and determine where they are
located. Repair and re-build the project. The assistance of the Instructor may be
required.
iii. Click the OK button to close the dialog.

Exercise - Inspect the Built Control Project

Outcomes
 Determine the changes made to Unity Pro as part of the Build process.
1 Check the Built project.

i. Right-click Exec and select Open Built Project.
The Control project will open in Unity Pro.

ii. In the Variables & FB instances folder of the Structural view,
observe the following pages. All of these represent items built into
Unity Pro by PlantStruxure PES.
 The Variables:

Exercise - Inspect the Built Control Project
(cont.)
 The DDT Types:
 The Function Blocks
iii. Close the Unity Pro view.

iv. Close the Executables tab.
v. Contract the Tank1_Control tree.

Deploy the Control Project
Deploy The Deploy process will send the Built executable to the appropriate controller.
When the executable was mapped to a controller it created a link to that controller
in the Topology. This means that the executable can now be deployed to the
controller from the Topology Explorer.
When a project is deployed to a controller a dialog box allows the selection of the
executable to deploy, this dialog box will contain a list of all the control projects
and executables that have been mapped (services) to that controller.
When the Executable has been selected, a dialog will be displayed to allow the IP
address if the controller to be selected.
If a valid IP address is entered and the controller is found, PlantStruxure PES will
display the state of the controller and allow the project to be deployed.

(Optional) Exercise - Deploy the Control Project

Outcomes
 Deploy the control project to the M580
This exercise is optional as it is only possible to do this if the M580 hardware is
available. If the hardware is not available, then the control project will be deployed
into the simulation environment in a later chapter.
1 Connect the PAC.

i. Connect an Ethernet cable between the PC and the service port of
the PAC.
ii. Open a command prompt and Ping the CPU using the command Ping
192.168.50.110.
If the CPU does not respond to the Ping command, check the cabling
and settings, including the IP address of the PC.
2 Deploy the project to the PAC.

i. In the Topology Explorer, right-click the M580_ePAC and select
Deploy Built Project from the menu.
ii. The following dialog box allows the selection of the control project
and executable. At the moment there is only one control project and
one executable. Click the OK button to continue.

Exercise - Deploy the Control Project (cont.)
iii. Select the IP address of the M580 ePAC. The status display will
change from "not found" to the state of the CPU - either running or
stopped.
iv. Tick the box Start engine after deployment.
Note:
If the Run engine after deployment is not ticked, there are options on the right-click
menu to Run and Stop the PAC.
v. Click the OK Button to deploy the project to the PAC

vi. In the confirmation box that is displayed, click the OK button to
deploy to the PAC.

3 View the deployed project

i. Right-click the M580_ePAC and select Refine Online from the menu.
ii. When the Control Participant opens, maximise the window.

iii. Open the Agitation Program Section.

iv. Arrange the window so that the CONDSUM and DEVCTL blocks are
visible.
v. Operate the switch for Input 0 - Motor Fail and observe the effect.
vi. Open the Water section and ensure the AINPUT1 block is visible.
Operate the first potentiometer and observe the effect on the
Channel Input (CHIN) pin.

vii. Examine the various sections and note the effect of changing
switches and analog values. Refer back to the mapping tables in the
Exercise - Map the Control Hardware (page 7-12).
Note:
Some parts of the program will not work as they rely on parts of the configuration
that have not been completed yet. These will be implemented in later chapters.

Chapter Outcome
Summary of Control Project that was Built in the previous chapter was linked to a controller and
Activities the virtual I/O from the application was mapped to the real I/O from the Topology.
The executable was then built ready for deployment.
If real hardware was available then the project was also deployed to the PAC.

Summary
 Combine the Components (page 7-1)

 Mapping (page 7-7)
 Build the Control Project (page 7-18)
 Deploy the Control Project (page 7-23)
 What is the result of Building a project?
 Can a project be deployed if the IP address of the PAC is not known?
 Can a project be mapped to more than on PAC?

End Day One - Summary
Summary At the end of day one, students should:
 Understand the setting of PlantStruxure PES:

- What it is and what problems it is attempting to solve
- How to manage the software and the environment in which it operates
 Describe the core components of PlantStruxure PES
- The four Explorers
- Folders and Systems
 The Application Explorer:
- System folders
- Instantiation
- Object linkages
 The Topology Explorer:
- Topology folders
- Create and Configure a Controller
 The Project Explorer
- Create a control project
- Configure a control project
- Map and build the Control Project
- Additionally, if hardware is available, deploy the control project
If hardware is not available to be able to deploy the Control Project then it will be
deployed to the Simulation Environment during day 2.

Chapter 8: Define the Computers and Networks
Introduction
Introduction
In a previous chapter the Topology Explorer was used to define a PAC to run a
control project. In addition to this it can be used to define the various computers (or
'Stations') in the system. The Topology Explorer will also specify the exact
software to be used on these machines.
This chapter also describes how networks can be created to link the various PACs
and Station Nodes.
This defines the real architecture of the plant.

Objectives
 Create Station Nodes to run the Supervision Software
 Define networking infrastructure
 Attach devices to the networks
 Station Nodes ......................................................................... 8-3

 Station Node Roles ................................................................ 8-7
 Networks .............................................................................. 8-15
Aim of this Chapter
Expected In this chapter, the physical management computers of the environment will be
Outcome defined along with their various roles.
The various computers within the environment are referred to as Station Nodes and
these must be defined to specify both their roles (and the software components they
will execute) and also the network interactions they will have.
Finally, the networking connections will be completed.
Work undertaken in this chapter will be confined to the Topology Explorer.

Station Nodes
Create Station A Station Node is used to define a computer and its role in the architecture. It can
Nodes be a Supervision Server, Supervision Client or Engineering Workstation. The
configuration in the Topology Explorer defines the services that will run on the
computer.
The main topology creation commands on the right-click menu are as follows:
Open Display the modules configured for inclusion in the Station

Node
Create NIC Create another Network Interface Card on the station node (the
first is created automatically)
Create OFS The Station node includes an OFS Server
Create UnityPro The Station node includes Unity Pro (may be used in
conjunction with the Unity Simulator as a source of field data).
Create VJC The Station node includes Vijeo Citect Servers and/or a Vijeo
Citect Client
Physical connections Connect the Station node to one physical Network
This is a very dynamic environment and that many elements in the right-click are
greyed out, depending on the items configured in the station node.

Station Nodes (cont.)
Three Station As was seen in the network diagram, three Station Nodes will be defined.
Nodes
Station Node Purpose Installed Features
Supervision Server Run the server tasks to OFS

support the Supervision
project Vijeo Citect
Dual NICs
Engineering Station Development station OFS
Vijeo Citect
Unity Pro
Dual NICs
Operation Station Operator's computer Vijeo Citect
Single NIC
In order to demonstrate a working system for the exercises that follow, the
Engineering Station will also include Unity Pro and OFS simulators.

Exercise - Create the Station Nodes

Outcomes
 Create a Supervision station.
1 Create and configure the Supervision server.

i. Expand the Operations folder.
ii. Right click the Server Room folder and select Create Station Node.

Exercise - Create the Station Nodes (cont.)
iii. Name the new Station Node as SupervisionServer.

iv. Right-click the SupervisionServer and configure as follows:
Description Supervision Station Server

Area 1
The completed dialog will look like this:
v. Close the SupervisionServer Properties pane.
2 Create the other Station Nodes.

i. Under the Plant Control Room folder object, create a new Station
Node as follows:
Identifier OperationStation
Description Supervision Operation Client
Area 1
ii. Under the Project Development Room folder, create another new
station node:
Identifier EngineeringStation
Description Engineering Station
Area 1

Station Node Roles
Specific Roles By configuring a Station Node to have the various Instance components, the User
is telling PlantStruxure PES how this computer will be configured and is giving
guidance on what its role in the final solution will be.
It is possible to link to a Station Node an unlimited number of NICs and one each
of OFS, Unity Pro and VJC.
Be aware that configuring any of these instances does not cause that software to
be installed, it is merely advising PlantStruxure PES that the package will be
present on the identified computer.

Station Node Roles (cont.)
Specific Roles The four possibles Station Node roles:

(cont.)
Instance
NIC Defines a network interface. This may be configured with

a name and an IUP Address / Subnet mask.
OFS Configures the Station Node to communicate on the

network using OFS.
Unity Pro The presence of Unity Pro advises PlantStruxure PES that
the Station Node is capable of emulating a PAC.
Vijeo Citect The presence of Vijeo Citect is a requirement for any

Station Node to act as either an Operation Server or an
Operation Client.

Exercise - Configure the Station Nodes

Outcomes
 Implement the components of a Supervision station.
1 Configure the Supervision Server.

i. Right click the SupervisionServer entity and select Open.
Note:
The first NIC instance is created by default as obviously a Station Node must be
able to communicate on a network. Subsequent NICs may be created for stations
with multiple network interfaces.

Exercise - Configure the Station Nodes (cont.)
The SupervisionServer details screen will open.
ii. Right-click the NIC_1 entry and select Properties.

iii. Expand the NIC Parameters section to make visible the IP
addressing details.
iv. Set the Instance Name to be NIC_Server_Ctrl.
v. Set the Security Area to be 1.
vi. Configure the IP address to be 192.168.50.210, 255.255.255.0.
vii. Close the NIC_Server_Ctrl tab.
Note:
Object names must be unique throughout the System.
viii. Right-click on the grey SupervisionServer titlebar and select Create

NIC to create a second NIC entry.
ix. Configure the second NIC:
Instance Name NIC_Server_Op

Area 1
IP Address 192.168.100.210
Subnet Mask 255.255.255.0
x. Close the NIC_Server_Op configuration tab.

xi. Right-click the grey SupervisionServer titlebar and select Create

OFS.
xii. Configure the OFS entry as follows:
Instance Name OFS_Server
Description OFS Server
Area 1
Note:
Any Station Node acting as a Vijeo Citect IO Server is required to implement OFS
as a means of communicating with the PACs.
xiii. Create a VJC server as follows:
Instance Name VJC_Server
Description VJC Runtime Server
Area 1
The completed configuration will look like this:
xiv. Close the SupervisionServer configuration page.

2 Configure the Plant Control station node.

i. Open the feature list of the OperationStation (in the Plant Control
Room folder).
ii. Configure the NIC:
Instance Name NIC_Client_Op
Area 1
NIC IP Address 192.168.100.230
Note:
If the initial NIC (created by default) is named NIC_2 (or some higher number)
then previously created NICs have not been re-named. All NICs throughout the
System will be provided with unique names. These names will be constructed so
as to provide both location and usage references.
iii. Configure a Vijeo Citect instance.
Instance Name VJC_Op
Description VJC Runtime Client
Area 1
iv. Close the OperationStation tab.

3 Configure the Engineering station node.

i. Open the EngineeringStation properties.
ii. Configure the first NIC:
Instance Name NIC_Eng_Ctrl
Area 1
Note:
The Engineering Station represents a site development computer. In terms of this

course, this is the Student's computer.
iii. Configure a second NIC.
Instance Name NIC_Eng_Op
Area 1
iv. Configure a VJC instance.
Instance Name VJC_Eng
Description VJC Test Environment
Area 1
v. Create an OFS instance.
Instance Name OFS_Eng
Description Engineering OFS
Area 1
vi. Configure Unity Pro.
Instance Name Unity_Eng
Description Unity Pro Development
Area 1

The final result should look like this:
vii. Close the EngineeringStation tab.
At this point, each of the folders beneath Operations contains a

Station Node.

Networks
Physical Having identified and configured the various Station Nodes, it is now necessary to
Connections define the interconnections between them and the equipment with which they will
interact. This is done by defining networks and connecting station nodes (and
PACs) to the networks.
The network will form the core component of all interconnection structures.
The Physical Connections menu is used to define interfaces between instances of

controllers (created in a previous chapter) and supervision node NICs with the
Ethernet Network(s).

Exercise - Link the Networked Devices

Outcomes
 Be able to connect hardware equipment to defined networks.
1 Create the Ethernet networks.

i. Right-click the Network folder object and create an Ethernet
Network. Name it Control.

Exercise - Link the Networked Devices (cont.)
ii. Do this twice more, naming the additional Networks Field and
Operation.
iii. Place each Network in Area 1.

iv. Close the Network tab.
2 Create physical connections.

i. Navigate to the M580_ePAC object, right-click and select Physical
Connections.
The Physical Connection(s) popup will be displayed showing all the

communications modules configured in the M580 rack.

Exercise - Link the Networked Devices (cont.)
ii. Link the CPU Ethernet connection to the Control network and the
other Ethernet connection to the Field network.
iii. Click the OK button to close the dialog.
3 Create connections for the Station Nodes

i. Right-click the SupervisionServer object (in the Server Room
folder) and select Physical Connection(s).
Note:
The various NICs were named to match their roles in the form
NIC_<Device>_<Network>, thus simplifying the management of the various
interfaces.
ii. Connect the Control and Operation networks.
iii. Close the SupervisionServer dialog.

iv. Repeat for the Engineering (two connections) and Operation (one
connection) Stations.

Chapter Outcome
Summary of The various station Nodes (or computers) have been created and their roles on the
Activities network have been defined. Additionally, the networking of Control devices and
the various Stations in the system has also been defined.
The various computers intended to execute the Supervision environment and

configured in PlantStruxure PES to identify the software components that will be
installed on them - this gives PlantStruxure PES sufficient information to guide
later configuration. For instance, it will only permit a Station Node to act as a
Vijeo Citect Server if Vijeo Citect was added to the Station Node configuration);
similarly, that Computer may only be an I/O Server if OFS was included in the
configuration.

Summary
 Station Nodes (page 8-3)

 Station Node Roles (page 8-7)
 Networks (page 8-15)
 What is a Station Node?
 What are the services that can be configured for a station node?
 How many networks can be connected to a station node?

Chapter 9: Create the Supervision Project
Introduction
Introduction
In this chapter the Project Explorer will be used to encapsulate the previously built
structures into the Supervision project. Pages will be created for the Supervision
project which will then be refined to add users.
 Create a Supervision Project

 Access existing project components and successfully compose a valid
Supervision project.
 Add display pages
 Refine the supervision project to add other configuration items such as users
 Create a Supervision Project ................................................. 9-4

 Assign Supervision Facets ..................................................... 9-7
 Generate the Supervision Project ........................................ 9-16
 Create Graphics Pages ......................................................... 9-21
 Refine the Supervision Project ............................................ 9-35
Aim of this Chapter
Expected In this chapter, the Supervision project will be developed.

Outcome
Earlier in the course, when the various templates were used to instantiate the
representation of physical objects, a set of Instances, Objects and Control modules
were identified for each device. Similarly, the Supervision project will be created
based on the components derived from the equipment instantiated in the
Application Explorer.
Here a simple Supervision project will be created that contains a Tag database
based on the named equipment, along with a customised graphics page. This page
will be populated with genies contained in the objects created for the application

Expected Work undertaken in this chapter will be confined to the Project Explorer.
Outcome (cont.)

Create a Supervision Project
Supervision In order to lay out the framework of the Supervision project, it is necessary to first
Components Create a Supervision Project.
This will create the structure of the Supervision project.
Once the Supervision Project has been created, three actions are required.
 Create tag containers that will contain the data objects from the database. This
is an optional step as a tag container will be created automatically when the
first objects are assigned if one does not already exist. Tag containers must be
manually created for subsequent Clusters or I/O Devices.
 Assign facets. This will store all the system data into the tag containers(s). In a
multi-cluster environment, the user may select which Supervision data goes
into which container.
 Create Pages. Pages are defined as “genie containers”. They contain the
graphical representation of the objects defined in the application.
Control vs. In all cases, dialog panes related to Control aspects of a system will contain header
Supervision bars painted blue:
Management
Panes
Whereas those panes that deal with Supervision components will use an orange
colour:
These are the standard colours used to uniquely identify these products throughout
the Schneider Electric environment.

Exercise - Create a Supervision Project

Outcomes
 Create a Supervision project to monitor the operation of the pumping system.
1 Create a Supervision Project.

i. In the Project Explorer, right click the Corsek object and select
Create Supervision Project.
ii. Name the new Supervision object as Tank1_Supervision.
Note:
All necessary Supervision components (such as IO, Alarm, Report and Trend
servers) will be created automatically when the Facets are Assigned (in the next
exercise).

Exercise - Create a Supervision Project (cont.)
2 Inspect the Cluster.

i. Expand the structure beneath Tank1_Supervision.
Note:
By default, a Cluster (called Cluster_1) was created. Additional clusters may be

created from the right click menu if needed (not required for this exercise).
A likely use for the creation of additional Clusters would be where

there is sufficient complexity in the Supervision environment that
additional Alarm, Report or Trend servers are required.
Further Training:
The implementation of multiple clusters and servers is a topic in the Vijeo Citect
Architecture and Redundancy Course.

Assign Supervision Facets
Assign Facets to In the same manner as was seen for the Control project, objects managed by the
the Supervision supervision project have to be assigned. This process will assign to the project all
Project of the Supervision facets related to the instances already instantiated in the System
(data, tags, genies and so on).
Tags are assigned to tag containers during the generation process but genies and
other items such as users must be added manually.
Note:
A Tag Container (called TagContainer_1) will be created automatically as part of

the first assignment of facets. Tag containers will be covered in more detail in the
chapter System Evolution (page 16-1), where they will be used to extend the
architecture.
The assignment philosophy is exactly the same as for the Control project and the
same assignment methods are available: drag and drop an object, a group of object
or one facet inside one instance.

Assign Supervision Facets (cont.)
Facet Assignment Viewed from the Application Explorer, it is clear that a number of Template items
have been instantiated.

Facet Assignment Each of these Instantiations contains a number of Facets - representing either
(cont.) Control (in blue) or Supervision (in orange) components.
The role of the Assignment Editor is to extract the relevant Facets from each
Instantiation and make them ready to be combined into a single Supervision
Project.

Exercise - Assign Facets to the Supervision
Project

Outcomes
 Be able to assign facets to the Supervision project.
1 Assign project facets.

i. Right click the Tank1_Supervision object and select Assign Facets.
ii. A screen looking similar to the Tank1 facet assignment dialog (seen
in Exercise - Assign Control Facets (page 6-17)) will appear.

Exercise - Assign Facets to the Supervision
Project (cont.)
iii. Select the root object (.\) in the lower left pane to give focus to the
lower right pane.
iv. Drag the entire Site1 folder from the upper left pane to the lower
right pane. This will create the full assignment in one step and may
be used when all the facets will be assigned in their existing
configuration.
Observe that an automated part of this action was to create a

TagContainer_1 container (in the image above, it is visible at the
bottom of the lower left pane).
v. Close the Assignment Editor tab.
vi. Expand the Tags object (beneath the Cluster_1 object) to directly
observe the tags list noted previously.
vii. Close the Tags Container view.

Structure of a A typical Vijeo Citect environment contains various entities; generally referred to
Vijeo Citect as servers. These Alarm, Report, Trend and IO Servers may reside on a single
Environment physical computer or be scattered across multiple computers.
Display Clients (often referred to as Operator Stations) are generally stand-alone

computers physically located in the plant. Every Vijeo Citect computer may act as
a display client, but in general this functionality is not used on server computers.
Observe also that the IO Server may connect to multiple IO Devices.

Exercise - Inspect the Server Components

Outcomes
 Analyse the Supervision Server components automatically built by the system.
1 Open the IOServer

i. Expand the Services object (beneath Cluster_1) to expose the
IOServer object created automatically during the Assignment
exercise.
ii. Expand the IOServer_1 object to observe that additional structures

now exist. These include the Boards and Ports along with an
IO_Device.
iii. Expand and inspect the various IOServer components.

(cont.)
2 View the Servers.

i. Click the Open Button on the Services object.
This will display the various Servers that were created automatically.
The servers created relate to the exact requirements of the various
Facets that were Assigned previously.
ii. Right-click the title bar of the Services Folder to observe that the full
range of Supervision server objects may be manually created as
required.
Do not create anything at this time.
Observe on the previous page that the IO Server is created as a

separate object, while the others are attributes of the Services
object.

(cont.)
iii. Right-click each of the servers to observe their properties. Leave the
servers with their default names.
Observe that this structure only permits the creation of standby

servers for Alarm, Report and Trend (not IO) servers. This topic will
be re-visited in Implement Supervision Redundancy (page 16-
15).
iv. Close the various properties tabs.
v. View the properties of the IOServer object.
vi. Below the IOServer object, expand the path IODevices »

IODevice_1. Observe that this structure is typical of a default Vijeo
Citect IO Device construction.
vii. Close the IODevices tabs.

Generate the Supervision Project
Clients Although every Supervision computer may act as a client, it is normal practice to
isolate Supervision servers in some kind of "server room" and configure Operators'
stations to execute only the Client tasks. The Client delivers the Mimic and Alarm
pages to the Operator, permitting supervisory control of the plant.
Clearly a Client may be defined to execute the main deployed Vijeo Citect project
although it may be necessary to create a separate version to support local execution
of Events etc. A Client is defined in the same list of objects as the Alarm, Report
and Trend servers.
As noted above, te creation of a specific Client project is entirely optional - there

are specific reasons to do so which may or may not be appropriate for a given
installation. Should only one Project be created, this may be deployed to all
Station Nodes. On startup, each Node will check its own IP address against the list
of Project addresses and roles to determine how it should start - if its IP address
matches with a server role (e.g. IO Server, Alarm, etc.) it will launch that role; if
there is no match, it will launch as a client only.
Of course the alternate is that multiple Client projects may be created to suit the
needs of multiple Operator Stations throughout the plant.

Exercise - Create a Vijeo Citect Client

Outcomes
 Create a Vijeo Citect client instance.
As no other services will run on the Operation Station, a specific client must be
created to represent this Station.
1 Create a Supervision Client.

i. Ensure the path Tank1_Supervision » Cluster_1 » Services is open.
ii. Click the down-facing arrow to the right of the Services item to view
its contents.
iii. Right-click the Services title-bar and select Create Client.
The new Client will be included in the list of Services.
iv. Name this Client as OperationClient.
v. Close all opened levels of the Tank1_Supervision structure.

Generate the Supervision Project (cont.)
Generate a For Supervision projects, the generation process creates an XML file which may be
Supervision used to populates the native Supervision Participant database files with:
Project
 Tags from Supervision data facets
 Report events from Supervision server event facets
 Events from Supervision client event facets
 Supervision project components including network addresses
 User interface messages
 Equipment hierarchy
These actions make the underlying Supervision components available to the
various construction tools within the Supervision Participant interface. Probably
the most important of these is the delivery of all Tags derived from the Instantiated
templates, permitting the construction of active Graphics pages.
The Generate command is available on the right-click menu of the Supervision

Project.

Exercise - Generate the Supervision Project

Outcomes
 Be able to Generate the Supervision project.
1 Generate the Supervision Project.

i. Generate the Tank1_Supervision project.
Once done, a message of success will be displayed.

Exercise - Generate the Supervision Project
(cont.)
ii. Click the small down arrow symbol beside the word Details to see an
extended version of the dialog.
Informational message will be seen noting that the fully qualified tag
names are too long for Vijeo Citect and were truncated to fit.
Observe that the truncation process has identified the longest sub-
clause (in this case "ChemicalTreatment") and has shortened it
sufficiently to satisfy the maximum tag length attribute of a Vijeo
Citect tag. Students may wish to note that this is a good argument
to keep folder names short.
iii. Click OK to acknowledge the message.

Create Graphics Pages
Edit Graphics Graphics pages must ONLY be edited using the Supervision Participant of
Pages PlantStruxure PES.
WARNING
LOSS OF DATA
Do not move the Genies on the Graphics page outside of the control of
PlantStruxure PES. This location information is used to link the Genie to its
supporting code and is only updated when modifications are performed from
within the PlantStruxure PES environment.
equipment damage.
To summarise:
PlantStruxure PES does not:
 Save changes to Include projects

 Pay any attention to new projects created by the user within the Vijeo Citect
environment
In addition, do not:
 Modify Graphics Pages outside the control of PlantStruxure PES

 Create pages within Vijeo Citect
 Modify names or network addresses of ANY object
 Edit pre-defined PlantStruxure PES Cicode files

Exercise - Create a Supervision Graphics Page

Outcomes
 Be able to create Supervision pages.
 Be able to import pre-existing Supervision Participant Include projects.
1 Create the Page for Tank1_Supervision.

i. Right click the Pages object and select Create Page.
ii. Rename this Page to be called CT_Tank1 (for Chemical Treatment,

Tank1).

(cont.)
2 Include the Training project.

i. Right-click the Tank1_Supervision object and select Include
Projects.
ii. When the Tank1_Supervision dialog opens, click the Add button.

(cont.)
iii. An Open dialog will appear. The Instructor will advise the location of
the file Training.ctz. Navigate to this location.
iv. Select the file and then click the Open Button to open it.
PlantStruxure PES will take a few moments to analyse and import

the contents of this file.
v. Once done, close the Tank1_Supervision dialog.
3 Edit the Graphics Page.

i. Right-click the CT_Tank1 item in the Pages - Containers list and
select Edit to open the Vijeo Citect development interface.

(cont.)
A new window will open displaying the Vijeo Citect Graphics Builder
interface.
In this specific interface, PlantStruxure PES is configured to only

interact with the Vijeo Citect Graphics Builder. This means that any
work performed in the Graphics Builder will be incorporated into the
underlying PlantStruxure PES configuration databases, but changes
made via the Project Editor, the Cicode Editor or the Citect Explorer
will be lost.
WARNING
LOSS OF DATA
Do not use this interface to access elements in the Project Editor.
equipment damage.

Exercise - Import the Supervision Graphics
Page Static Elements

Outcomes
 Be able to locate and use pre-built graphics pages.
1 Open the pre-built graphics page.

i. In the Graphics Builder window, select the menu File » Open...
ii. In the Open dialog, select the Training project and the page
CT_Tank_Source.
iii. Click OK to open the page.

Exercise - Import the Supervision Graphics
Page Static Elements (cont.)
iv. Right-click anywhere in the pale blue area of the page and select
Page Properties from the menu.
v. Change the Style to tab_style_1 and the Resolution to XGA.
vi. Click OK to save the change.
Note:
PlantStruxure PES provides a standard Supervision page style (called SXW_style)

however this generally takes up a lot of screen space. There is an additional style,
called sg2_style, which looks very similar to tab_style, but this is not available
until after the genies have been added to the page (in the next exercise).
vii. Select the menu File » Save As...

viii. On the Save As dialog, select the Tank1_Supervision project and
the CT_Tank1 page.
ix. Click OK to save the page - this will over-write the initial version of
the graphics page.
x. Click the Yes button to acknowledge the warning.

Create Graphics Pages (cont.)
Select Genies For each object instantiated, the Supervision participant will display all items that
have been selected for Supervision and display them in a browser interface.
In the image above, an entry exists for each of the components which may be
included on the Graphics Page. Any of the items in the Browser may be dragged to
the Graphics Page; when the mouse is released a list of appropriate Genies is
provided. It is a simple matter to select the most appropriate.
These graphical representations are embedded inside the object. Thus all those
representations are automatically made available with the object.
In addition, user design elements (such as piping, static symbols etc.) may also be
incorporated to improve the appearance of the page. The intention is to create a
representation of the P&ID such that a plant operator will have a clear
understanding of the process being displayed.

Exercise - Complete the Supervision Graphics
Page

Outcomes
 Be able to select suitable graphical representations of objects for use on pages.
The following graphics page will be created:

Page (cont.)
1 Open the Genie Browser.

i. Observe that a Browser pane is positioned to the left of the Graphics
Builder window. Open the sections to display the objects.
2 Add a genie.
i. Drag the FC1001 entry (WATER $PID) entry to the main graphics
page area.

Page (cont.)
ii. When the mouse button is released, a menu of available genies is

displayed. Pause over each entry to see the genie in detail.
iii. Click on the second item PresentValueSetpointOutputGenie to

select that item.
The first time this is done, an external resource will be loaded. This
may take some time.
Note:
Do not attempt to drag the same item multiple times while SGC_Include2 is
loading; multiple copies will (eventually) be created.
iv. Once completed, the chosen Genie will be placed as desired with the
object name automatically placed in the Genie's title block.

Page (cont.)
v. Drag the following genies to the Graphics page; position them in

accordance with the image on the first page of the exercise.
Folder Object Genie

Water CV1001 2WayHorizontalControlValve
FI1001 RightAlignedPV
SP1001 SP_Real_10_CG
Discharge AV1010 2WayValveHorizontal
P1010 HorizontalRightPumpGenie
Agitation AG1002 VerticalLeftMotorGenie
LSH1002 Hoz1PositionDetectorGenie
LSL1002 Hoz1PositionDetectorGenie
TI1002 LeftAlignedPV
Note:
Do not duplicate (copy / paste) existing genie objects when populating additional
items as the tag associations will be incorrect.
Note:
Any genie object that had not already been assigned (for instance, during the
Exercise - Assign Facets to the Supervision Project (page 9-10)) will be
automatically assigned when dragged onto the Graphics Page.

Page (cont.)
3 Animate the Agitator.

i. Double-click to open the Agitator Symbol-set.
ii. On the Appearance tab, configure the Animate when property to

be:
(S1CTT1A_AG1002_DEVCTL_STW BITAND 0x0001) > 0

iii. In order to avoid typing errors, the Tag Wizard may be used. Click
on the Tag Wizard button.
iv. Select Insert Tag.

v. Locate the tag S1CTT1A_AG1002_DEVCTL_STW in the list and
select it.
vi. Click OK to copy the tag to the Animate when field.

Page (cont.)
vii. Add the remainder of the text to complete the command.

viii. Click OK to save the changes.
During the save process, the location of the genie on the graphics
page is used to link the genie to its supporting code, which in turn
links the Genie to the tag used for its animation. This information is
only updated when modifications are performed from within the
PlantStruxure PES environment.
Note:
If Folder Aliases were not used (this was determined in Exercise - Create the
System Folder Structure (page 4-17)), the tag name will instead be
S1AG1002_DEVCTL_STW.
The STW component of the expression above is based on a

standardised set of communicating bits incorporated as part of the
customised genies in PlantStruxure PES. These bits convey a wide
variety of standardised information - the least significant bit (as used
above) carries the Boolean state of the linked physical object.
4 Save the page and close.

i. Close the CT_Tank1 tab and save the changes.

Refine the Supervision Project
Typical Supervision Refinement permits two activities. Firstly to review project data
Supervision created by the generation process and secondly to modify elements of the project
Refinements within the described limits.
For example, users and roles may be added, which will be deployed to station
nodes as part of the Supervision project rather than creating them locally after
deployment (an action which would have to be repeated every time the project was
re-deployed).
In addition, extra site management graphics pages might be added, along with
customised Cicode fragments and other functionality not directly related to the
P&ID being modelled by the Application Explorer.
Limitations Any action performed in a Refine view that seeks to modify a object created by the
PlantStruxure PES development process will be lost when a subsequent Generation
is performed. The following changes are typical of the set that will be lost in this
situation.
VJC Project Editor Menu Menu item
Equipment Equipment
Tags Variable Tags
Local Variables
Trend Tags
Alarms Digital Alarms
Time Stamped Alarms
Advanced Alarms
System Reports
Events
Users
Roles
Parameters
Included Projects
Communication I/O Devices
Boards
Ports
Servers Clusters
Network Addresses
Alarm Servers
Trend Servers
Report Servers
I/O Severs

Refine the Supervision Project (cont.)
Other Refining a Vijeo Citect project makes the project inconsistent at the platform level.
Considerations For example, a variable tag added in the Refine view cannot be seen in the tag
container of the Supervision Participant project in the Project Explorer.
In addition, PlantStruxure PES will not save changes to Include projects. Any such
changes must be performed outside of Process Expert by using Vijeo Citect after
the projects downloaded from PlantStruxure PES have been Restored. Also,
although it is possible to create new projects in the Refine view, these will be lost
upon return to PlantStruxure PES.
Default Users By default, Process Expert creates one user for the Supervision project with the
following properties:
User Name operator

Roles operator
Password <none>
The Operator role is configured:
Privilege <blank>
Allow RPC False

PlantStruxure PlantStruxure PES is configured with a set of default privileges implemented

PES Default User within Vijeo Citect.
Permissions
Privilege Use
1 Enables the acknowledgement of detected alarms associated to

Supervision components.
Alarm acknowledgement is also conditioned by the

[Privilege]AckAlarms parameter (set to 1 by default). If a
privilege level that is different from that configured in the
[Privilege]AckAlarms parameter is configured in the alarm
tag, both privilege levels are required to acknowledge the detected
alarm.
2 Operator actions: Operator setpoint changes (including parameters and

commands regarding sequences).
3 First-level supervisor actions:
 Changes to detected alarm setpoints and enabling/disabling first-

level alarms (HI, LO, DEV).
 Adjustments to control parameters.
4 Second-level supervisor actions: Change of owner (Operator/Program)
5 Engineering and/or maintenance personnel actions:
 Set-point changes and enabling/disabling second-level alarms

(HIHI, LOLO, digital).
 Interlock bypassing.
 Enabling/disabling the simulation mode.
6, 7, 8 Not used.

Exercise - Refine the Supervision Project

Outcomes
 Configure project attributes for the Supervision Project.
1 Refine the Project.

i. Right click the Tank1_Supervision object and select Refine to enter
the full Vijeo Citect development environment.
Using this method, the three components of the Vijeo Citect interface
are presented in a tiled view and changes may be made in all three
editors.
Note:
In a similar fashion to the Control Participant, opening the Refine process via the
individual page entries will launch the Graphics Builder to edit those pages
directly, whereas accessing Refine via the top-level object will open the full Vijeo
Citect interface. The Refine stage is the correct point to add Users, modify
permissions etc.

Exercise - Refine the Supervision Project (cont.)
ii. From within the Vijeo Citect Project Editor, select the menu Tags »
Variable Tags.
iii. Scroll through the list of automatically configured tags to observe

what has been created.
iv. Close the variable tag dialog box using the Close button in the top
right corner. Do not change anything; do not use the buttons at the
bottom of the dialog.
v. Observe other features, such as the Server configuration.
2 Configure Roles.
i. From within the Project Editor, select the menu System » Roles.
ii. The system has automatically created the Operator role. Configure
its Global Privilege to be 1..8 (all areas).
iii. Click the Replace button to update the Role definition.

iv. Close the Roles dialog.

3 Create a User.
i. Select the menu System » Users.
ii. Create a new user as follows:
User Name CT_operator
Full Name {optional}
Password CT
Roles Operator
iii. Click the Add button to save the new user and then close the dialog
box.
If desired, spend some moments to observe those additional

components that have been created as part of this process.
iv. Close the Supervision Participant pane and click the Yes button to
confirm saving the changes.
When the Graphics page in the Training Include project was used,
the end result was to save it into the main Tank1_Supervision
project. This means that the Training Include project contains
nothing that will be required in the final project. In order to keep
the final project as small as possible, it is best to remove the
Training Include.

4 Remove the Training Include project.
i. Right-click the Tank1_Supervision object and select Include

Projects.
ii. On the Tank1_Supervision dialog, select the Training Include

project and click the Remove button.
iii. After a few moments, the Training Include will be removed.
Note:
Do not remove the SGC_Include project.
iv. Close the Tank1_Supervision dialog.

v. Generate the Supervision Project.

The Assignment The Assignment Viewer may be used to verify the state of Control and Supervision
Viewer facets. These facets might be Assigned or Unassigned within a system.
In the image above, all Unity Pro items (shown with pale blue logos in the Name
column) have been assigned while only one Genie is Assigned. This matches with
the specific Genie added to the Graphics page in Exercise - Complete the
Supervision Graphics Page (page 9-29).
Scrolled down, the Tags will be seen to all be assigned.
For each facet, a right-click will:
If the facet is not yet Open the corresponding Assignment Editor for any
assigned existing project of the system. For genie facets, the
Pages container of any existing Supervision project
will open.
If the facet is already Open each container to which it is assigned and locate
assigned the facet.

Viewing The right-click menu:

Assignments
In either case, the Assignment Viewer is closed after the right-click is executed and
the Container view is opened.
Note:
The Assignment Viewer cannot be accessed if the Assigned status is Unassigned

and the Data or Link status is Invalid.

Exercise - View Assignments

Outcomes
 Inspect and identify the interrelationship between instantiated objects and their
usage throughout the System.
1 Open the Assignment Viewer.

i. Return to the Application Explorer.
ii. Open the Tank1 » Agitation folder.
iii. Right-click the first item (S1CTT1AGAG1002 - the Agitator motor)
and select View Assignments.
iv. The Assignment Viewer will be displayed.

Exercise - View Assignments (cont.)
v. Scroll down to the Supervision section of the page.

vi. Right-click the first assigned Genie entry (VerticalLeftMotorGenie)
and select the Tank1.Supervision.CT_Tank1 option.
vii. The Pages Container view will be displayed, indicating all the items
used in the page on which the VerticalLeftMotorGenie is placed.
2 View other components.

i. Re-open the Assignment Viewer and investigate these items:
 A Control object
 An unassigned Genie
 Components of the Water and Discharge Containers
 Any other items of interest.

Chapter Outcome
Summary of With the Control project completed in previous chapter, attention turned to the
Activities Supervision project, where the various Client and Server components were defined
and mapped to Station nodes.
Relevant graphical representations of the instances were identified and added to a

newly created Graphics page, along with static elements to enhance the overall
appearance.
A simple Refinement saw the editing of the Operator role and the addition of a new
User.

Summary
 Create a Supervision Project (page 9-4)

 Assign Supervision Facets (page 9-7)
 Generate the Supervision Project (page 9-16)
 Create Graphics Pages (page 9-21)
 Refine the Supervision Project (page 7-3)
 What is a Supervision Project; what elements does it contain?
 Is it possible to modify pages outside the PlantStruxure PES environment?
 What process populates the Tag Database in the Supervision Participant?

Chapter 10: Finalise the Supervision Project
Introduction
Introduction
With the Supervision Project created, facets mapped and pages built, the final part
is to map the Supervision Project to station nodes and build the executables for
deployment to those nodes.
This is similar to the mapping and build processes for the Control Project.

Objectives
 Map the Supervision Project to the appropriate Station Nodes
 Download the VJC executables
 Download the OFS Configuration file
 The Supervision Executable ................................................ 10-3

 Map the Supervision Services.............................................. 10-6
 Map the I/O Devices .......................................................... 10-10
 Build the Supervision Project ............................................ 10-15
 Construct the Engineering Station ..................................... 10-17
Aim of this Chapter
Expected In this chapter, the construction of the Supervision environment will be completed.
Outcome
With multiple run-time environments defined (the Supervision Server, the

Engineering Station etc) defined in the training scenario, multiple Supervision
executables must be created.
For each executable, the location of the various server tasks (IO Server, Alarm
Server etc.) is identified and in addition, the source of IO data is linked to the IO
Server.
In the next chapter, the completed executable will deployed to the run-time
environment.

The Supervision Executable
What is a A Supervision Executable is the completed and functional Vijeo Citect project
Supervision ready to be deployed to the target Station Node. In addition, the Executable carries
Executable? OFS configuration information ready to create a valid OFS connector between the
Control and Supervision environments.
A Supervision Executable will be created for every targeted Station Node defined
in the PlantStruxure PES System.

Exercise - Create the Supervision Executable

Outcomes
 Be able to build the Supervision Project.
1 Create the Supervision executable.

i. Expand the Tank1_Supervision structure and right-click
Executables.
ii. Select Create Executable and name it as Ops.

Exercise - Create the Supervision Executable
(cont.)
iii. Set the Properties of the Executable to be:
Description Tank1 VJC Server Executable

Note:
In the equivalent exercise for the Control Executable, the Execution Domain name
was typed into the field. Once it was created there, it became available for
selection via the drop-down list.

Map the Supervision Services
Relationship Networks were defined within the Topological Explorer in Exercise - Link the
between Networked Devices (page 8-16). Here, abstract Networks were defined and
Networks, relevant devices declared to be members.
Services and
Communication
In addition, all three Station Nodes were configured for Vijeo Citect and both the
Supervision Server and Engineering Station had OFS defined.
Note:
The act of defining OFS or VJC (or any other service) on a Station Node does not
automatically create or configure that service on the Station Node. It is merely
identifying to PlantStruxure PES that the Computer will have those components
installed as part of the completed system.
In order to properly create the Vijeo Citect project that will be deployed to and
executed upon the various Station Nodes, the various roles must be identified and
the connectivity to data sources defined.

Map the Supervision Services (cont.)
Map Services The first step is to Map Services. In this step, the Station Nodes which will act as
the various Vijeo Citect Servers and Clients are identified.
The Alarm, Report, Trend and Client roles may be connected with any Station
Node that has Vijeo Citect configured.
The IO Server may only be connected to a Station Node which has both Vijeo
Citect and OFS configured.
Here it may be observed that although available as the Alarm Server, the Operation
Station cannot be configured to be the IO Server as it was not configured for OFS.
OFS is the only method supported by PlantStruxure PES for communication
between the IO Server and the IO Devices.
At a minimum, only the IO Server must be configured in this screen, although it

would be highly unusual to not also configure the other servers.

Exercise - Map the Supervision Services

Outcomes
 Be able to specify the roles of all Supervision computers.
1 Map the Services.

i. Right-click the new Ops Executable object and select Map Service.
The Service Mapping dialog will open. This will be used to identify
the Station Nodes upon which each of the Services will be run.
The station nodes will only appear in the drop-down lists if Citect
Runtime has been defined for them. Further, the IOServer list will
only contain Station Nodes for which OFS was defined in Exercise -
Configure the Station Nodes (page 8-9).

Exercise - Map the Supervision Services (cont.)
ii. For the item Alarm_1_P, click under the heading Engine.
iii. Select the SupervisionServer entry.
iv. Repeat for all other Services as follows:
Alarm_1_P SupervisionServer
IOServer_1 SupervisionServer
OperationClient OperationStation
Report_1_P SupervisionServer
Trend_1_P SupervisionServer
v. Close the Service Mapping dialog.

Map the I/O Devices
Communication Once the Services are Mapped, attention turns to the Communication Mapping.
Mapping Here, the various data sources from which the I/O Server will obtain plant data are
identified. Configuration Mapping is not available (greyed out on the right-click
menu) until the I/O Server has been defined.
When selecting a data source for an I/O Device, PlantStruxure PES will offer a list
containing all valid data sources - both PACs and Station Nodes with OFS
configured.
However, this list is also restricted to only those devices configured to be on

networks to which the IO Server is directly connected. If an additional PAC was
constructed and configured to be on the Field network, it would not be offered in
the list in the image above as the NICs in the IO Server are defined to be on the
Operation and Control networks only.
The Controller identifies the specific PAC which will exist at the opposite end of
the connection.

Map the I/O Devices (cont.)
Communication As each Controller is selected, the Communication Modules drop-down list is

mapping (cont.) populated with all interfaces defined for networks with connectivity to the IO
Server.
As may be seen from the image below, only the CPU interface is on a network
visible to the IO Server (the Control network); the Field network is invisible to the
IO Server as it is on "the other side" of the PAC, thus only the CPU interface was
offered in the image above.
The Impact of When linking a Supervision Project to a Physical Station (as was discussed in Link
TCP/IP Subnets a Supervision Project to a Physical Station), it is essential that the various devices
must be able to physically communicate with each other.
With this in mind, rules are imposed to ensure that the Communication Mapping
dialog will only propose PAC devices on the same TCP/IP subnet as the Vijeo
Citect IO Server.

Map the I/O Devices (cont.)
The Impact of The Network Diagram previously introduced makes this clear.
TCP/IP Subnets
(cont.)

Exercise - Map the Supervision
Communications

Outcomes
 Be able to connect the Controller with the Supervision IO Device.
In this exercise, the previously created IO Device will be connected to the M580
CPU.
1 Map the Communications.

i. Right-click the Ops executable and select Map Communication.
The Communication Mapping dialog will open.
ii. Click in the field below Controller in the IODevice_1 drop-down and
select the M580_ePAC item.

Exercise - Map the Supervision Communication
(cont.)
iii. Set the Communication Module field to refer to the M580 CPU
module.
iv. Close the Communication Mapping dialog.

Build the Supervision Project
Build the When these steps are completed, the project may be Built.
Supervision
Project Building is the process of drawing together all the elements created in previous
steps (recall the comment earlier about everything done thus far being nothing
more than the creation of a script) and creating a viable Supervision project ready
to be deployed to its execution environment.
At this point, the system has:
 Configured the address of the Supervision station(s) in the Server configuration

tables.
 Created the OFS Alias file (named DeviceConfig.XML) containing the address
of the Control station and other information.
 Compiled the Supervision project and created the various CTZ files:
- <Supervision_Project_Executable>.CTZ (the primary project file)
- SGC_Include2.CTZ (containing the relevant genie libraries)
Note:
The CTZ files will only be created if the Build completed successfully.
This process will take a couple of minutes to complete.

Exercise - Build the Supervision Project

Outcomes
 Be able to build the Supervision project.
1 Build the Supervision project.

i. Right-click the Ops Executable object and select Build.
ii. While the process continues, a green 'spinning wheel' will appear to
the right of the dialog's title bar.
iii. When done, the wheel will disappear and the Notification Panel entry
will indicate Build Executable (Completed)."
iv. Close the Executables tab.

Construct the Engineering Station
Similar Structure By referencing the same underlying PAC infrastructure, there is no additional
as the Control work to be done in order to define the Engineering Station.
Supervision
Server In this scenario, the environment will be configured to run on the Engineering
Station. This means that the Engineering Executable will have a near-identical
structure to the Supervision Server.
It would, however be possible for the Engineering Station to be configured as a

Standby Server, but this will not be done at the current point of the course; instead
the Executable will be configured to show the same Supervision server
configuration as the Supervision Server. The Engineering Station might be
considered as a development or test environment.
Alternately, it might be considered that the Engineering Station represents the

actual development and testing environment to one side of the production
equipment.
By the completion of the next section, the Eng Supervision executable will have
been defined.

Construct the Engineering Station (cont.)
Relationship A second Executable will be created in parallel with the Tank1 Ops Executable.
between
Executables and
the Supervision
Project
As was outlined in What is a Control Executable? (page 7-3), separate

Executables are required to support specific hardware instances, particularly when
they re significantly different. In the case of Supervision Executables, this means
that each Station Node may have its own Executable, although in this specific
instance, it is not absolutely necessary.
Since the Executable resides within the larger Supervision (or Control) Project, the
Build process will take the specific Executable and link it with all of the associated
configuration elements defined throughout the Project (Assignments, Pages, Tags,
Clusters etc.).

Exercise - Construct the Engineering Station

Outcomes
 Construct Supervision Executables for the Engineering and Operation Stations.
1 Create a new Supervision Executable.

i. Right-click the Tank1_Supervision Executables folder and add a new
Executable.
ii. Configure the Executable as follows:
Identifier Eng
Description Project Engineering Station

(cont.)
iii. Close the Eng tab.
2 Map the Supervision Services.

i. Right-click the new Eng item and select Map Service.
ii. Map all Services to the EngineeringStation.
Note:
In order to create a single Supervision project that might be distributed to multiple

Client stations, it would be preferable to leave the OperationClient field blank.
iii. Close the Eng tab.

(cont.)
iv. Right-click the Eng item and select Map Communication.
v. Map to the M580_ePAC and CPU ports as before.

vi. Close the Eng tab.
3 Build the Eng Executable.

i. Right-click the Eng item and select Build. This will complete after a
short while.
ii. Close the Executables dialog.
Note:
It may be desirable to create a third Supervision executable for specific deployment

to the Operations Client. Generally, this would only be necessary if it was intended
that there be client-side Events run specifically on the Client station. This will not
be done in the course, but may be left as an exercise for the student.

Chapter Outcome
Summary of The primary Supervision executables were created and Services Mapped.
Activities
Once the Station Nodes' roles were defined, the IO Server connection to the PAC
data source was defined.
Finally, a second Supervision Executable was created to support the Engineering

Station.

Summary
 The Supervision Executable (page 10-3)

 Map the Supervision Services (page 10-6)
 Map the I/O Devices (page 10-10)
 Build the Supervision Project (page 10-15)
 Build the Engineering and Operation Stations (page 10-17)
 What is the result of Building a project?
 What is an executable?
 Why were multiple Executables created?

Chapter 11: The Simulation Environment
Overview
Introduction
It is not always possible to directly deploy to a real PAC during the development of
a system as the real hardware may not be available. Also, the engineer may wish to
test some features of the configuration without deploying to a PAC.
The simulation environment allows features to be tested without using the actual
hardware.
In the context of the training course, it will allow each student to test their
configuration without the hardware.

Objectives
 Configure a simulation PAC to run the control project.
 The Simulation Environment ............................................... 11-4

 Deploy for Simulation ......................................................... 11-9
Aim of this Chapter
Expected In this chapter it is recognised that the broad range of hardware defined for the
Outcome various execution locations doesn't exist in the training room.
There may have been a simple M580 rack (depending on the class location and
Instructor) but nothing else.
In order to observe the Control project operating, at least for testing, it is necessary
to construct a simulation environment.
To achieve this, a new Station Node (called Sim_Server) will be created to act as a
PAC. In later chapters, it will be extended to include Supervision functionality.
Subsequently, a new Control Executable will be created to manage this emulated

PAC.

Expected This Executable may then be deployed to the Unity Pro Simulator...
Outcome (cont.)
...where it may be seen in a running state:

The Simulation Environment
Simulate the Because the Topology Explorer is independent from the Project Explorer, it is
Control System possible to define a topology independently from any logic and vice versa.
If there is a testing lab with a simple controller that is intended for simulation
purposes this might be used during the development stages or during the
commissioning before implementing changes to the process controller.
A single Station Node may be created to handle all the roles described in the image
above; similarly, a single entry in the hierarchy will contain it. The Sim_Server is
intended as Supervision functionality on a local PC. In the next few pages, the
simulated Control functionality will be built; the Supervision simulation will be
constructed in Deploy and Run the System (page 12-1).
However, for the training course, although the Sim_PAC is drawn as a real PAC, it
will actually be Unity's simulator running on the Sim_Server computer. This is
started by running the program sim.exe.
Note:
If Unity Pro is also installed on the computer there will be two versions of the
sim.exe program; one supplied with PlantStruxure PES and one supplied with
Unity Pro. The one supplied with PlantStruxure PES should be used to ensure
compatibility with the deployed project executable.

The Simulation Environment (cont.)
Multiple When a control project is created it may contain multiple executables. These can
Executables then be deployed to different PACs that have been created in the Topology
Explorer.
In this chapter, the topology explorer will be used to configure a computer station
node to act as a simulator for the PAC.
In an earlier chapter, an executable was created and deployed to the real PAC. In
this chapter, an executable will be created and deployed to the simulation PAC
located on the computer.
If there are multiple Control Projects configured in the Project Explorer then
multiple executables can be configured for each to allow a single simulation station
to execute different control projects. This is the reason why PlantStruxure PES asks
for the Control Project and Executable before deployment.

The Simulation Environment (cont.)
Implied In the following pages, a Station Node (to be called Sim_Server) will be created to
Simulation encapsulate all the functionality of a simulation environment.
Subsequent to that, a Control Executable is created and Mapped to the Sim_Server

and will run in the PAC simulator on that server.
At no point will a PAC be defined for simulation.

Exercise - Implement a Simulation Topology

Outcomes
 Be able to implement a simulation environment.
1 Create a simulation folder.

i. Open the Topology Explorer.
ii. Beneath the Corsek System object, create a new Folder called
Simulate.
2 Configure a Station Node.

i. In the Simulate folder, create a new Station Node called Sim_Server
and (from the right-click menu of the Station Node) ensure it
contains the following items; edit each of them to configure the
desired name; descriptions may be added if desired. Set all items to
be in Area 1.
Item Property Value
NIC Name NIC_Sim
IP Address 127.0.0.1
Unity Pro Name Unity_Sim
OFS Name OFS_Sim
VJC Name VJC_Sim

Exercise - Implement a Simulation Topology
(cont.)
The completed configuration will look like this:
ii. Close the Sim_Server tab.
3 Create a Physical Connection.

i. Right-click the Sim_Server object and select Physical Connections.
ii. Select the Control network from the drop-down list of Allowed
Networks.
Note:
To create a simple simulation, it is not necessary to link NIC_Sim to the Control

network; however this linkage is needed to demonstrate the full features of
Runtime Services (page 13-1).
iii. Click OK.

Deploy for Simulation
The Control Having previously built a full Control Participant project and identified the exact
Simulator wiring and specific devices to which it is connected, it is obvious that such a
configuration may only exist in the "real world."
In order to test functionality for this training course, it is necessary to create a

similar duplicate system which has no such real world connectivity but instead may
be connected to the Unity pro simulator for testing.
All services are mapped to the single Station Node.
Of course, being a simulation environment, there is no need (nor opportunity) to

map Communications.

Exercise - Create a Control Simulator

Outcomes
 Be able to map the Control project to a simulation environment.
This exercise will demonstrate that a single Control project may be mapped to
multiple hardware configurations.
1 Create the simulation Control Executable.

i. Open the Project Explorer.
ii. Create a new Control Executable.
iii. Configure as below:
Identifier Sim
Description Tank 1 Executable for Simulation
Execution Domain Simulation
iv. Close the Sim tab.

Exercise - Create a Control Simulator (cont.)
v. Right-click the Sim item and select Map Service to Map to the
Sim_Server.
This is a simulation environment and thus it is not possible to map

either Communications OR hardware on a single computer.
vi. Close the Service Mapping tab.
vii. Right-click the Sim Executable and select Build All.

Exercise - Deploy a Control System Simulator

Outcomes
 Be able to deploy the Control project to a simulation environment.
1 Start the Simulator
The Control System simulator is included part of the courses

resources - locate the file sim.exe and launch it.
i. Once the simulator is running, an icon showing no configuration will
be displayed in the system tray.
2 Deploy the Control project to the Simulation Station.

i. Open the Topology Explorer and locate the Sim_Server in the
Simulate folder.
ii. Right-click the Sim_Server and select Deploy Built Project.

(cont.)
The system will ask for confirmation of the Project and Executable;
the pre-filled values will be correct (currently, they are the only
possible options on each of the drop-down lists).
Note:
This dialog permits the user to identify the Control project and the Control
Executable, which defines the Station Node upon which the project will be run.
Because the Project has already been mapped to one or more Executables, only
valid entries (one for each field in this case) will be offered in this dialog.
iii. Click the OK button to proceed.
The Confirm Deploy Built Project dialog will appear.
iv. Click the small down-arrow beside IP Address in the Engine

Information section. There should be just one entry - the Loopback
address 127.0.0.1.

(cont.)
v. Once the IP address is selected, the Status will change to No

Configuration. This simply means that there is no configuration
currently loaded in the Simulator. Ensure Start engine after
deployment is checked.
vi. Click OK.

vii. There will be one final confirmation message; click OK to continue.
The Simulator will be running in the System Tray.

(cont.)
Once correctly configured, the Simulator Panel will be displayed by

double-clicking the Simulator tray icon.
viii. Confirm the Simulator may be Stopped and Started at will.

(cont.)
A confirmation dialog will be displayed.
ix. Click OK to Stop the Simulation. A Reconfirm dialog will be

displayed.
x. Click OK again to confirm the Stop request. The Simulator panel will
indicate that the simulation has been stopped.
xi. Right-click the Sim_Server and select Start to restart the Simulator.

(cont.)
3 Open the Unity Pro project for on-line refinement.

i. Right-click the Sim_Server node and select Refine Online.
ii. Click OK to agree to the confirmation message.

(cont.)
iii. Reconfirm the action.
iv. Two outcomes will result. Firstly, the Simulator will display the
connection to the computer running the Control project.
In addition, the Control Participant screen will open, displaying the

project being executed (a fragment of which - from the Water
section - is displayed on the next page).

(cont.)
v. To open this (or any other) section, navigate to the appropriate

section in the MAST section and open the desired Section.
vi. Leave the Simulator and Control Participant running in readiness for
a later step.

Chapter Outcome
Summary of A Simulation Station Node was created to host all of the functionality required to
Activities execute the simulated systems.
Next, a Control Executable was created to host the necessary Control code ready
for simulation.
Finally the competed Control project was deployed to the Unity Pro Simulation
environment.

Summary
 The Simulation Environment (page 11-4)

 Deploy for Simulation (page 11-9)
 Can a project be deployed to multiple PACs?
 Can multiple projects be deployed to a single PAC?
 In the topology, does a controller need to be created for simulation?

Chapter 12: Deploy and Run the Supervision Project
Introduction
Introduction
Having constructed the Supervision project and deployed the Control Project to the
simulator, the final stage is to connect the Supervision Project to the Simulator and
deploy it to the run-time environments.
If the training machines are being used, the Supervision project can be deployed
directly to the laptop. If other machines are being used then the Supervision node
may need to be simulated.
 Create a Simulation environment to emulate the previously-created physical

structure.
 Deliver the Supervision projects to their correct locations - either real or
simulated - and execute them.
 Create a Supervision Simulation Environment ................... 12-3

 Run the System .................................................................... 12-7
 Runtime Features ............................................................... 12-29
 Alarm Templates ............................................................... 12-44
 Sequence of Events............................................................ 12-50
Aim of this Chapter
Expected Throughout the construction of the System, the assumption was that it was being
Outcome built to operate on a ‘real-world’ configuration containing PACs, multiple
networks, various computers and other resources. Clearly this is not present in the
training room.
In order to test the configuration that has been built, a simulation environment must
be constructed to allow a single computer to play all of the defined roles (as much
as possible). This was started in the previous chapter with the creation of the
Sim_Server and the deployment of the simulated Control project to the Unity Pro
simulator.
In addition to creating the simulation, this section will also demonstrate the
flexibility of the environment by revealing just how little re-configuration is
required to achieve this outcome; and by implication, how a single low-level
construction may be re-implemented on a variety of platforms with little or no
modification.
As the new simulation environment is built, it will quickly be observed that the
ability to deliver simulation is intrinsic to the PlantStruxure PES environment.
When limited configuration is performed, PlantStruxure PES will "fill in the
blanks."
Course Following the creation of the Simulation environment, work undertaken in this
Progression chapter will be mainly confined to the Topology Explorer.

Create a Supervision Simulation Environment
Implied Previously (in Deploy the Control Project (page 11-4)), a Station Node (called
Simulation Sim_Server) was created to encapsulate all the functionality of a simulation
environment.
Subsequent to that, a Control Executable was created. At this point, a matching

Supervision Executable will be created and also Mapped to the Sim_Server.
There is no ability to perform Communication Mapping for either Control or

Supervision.
Observe that at no point was a PAC defined; neither was a Supervision Project.

Create a Supervision Simulation Environment
(cont.)
Map the The Student's Computer will be used to simulate all aspects of the Control and
Supervision Supervision projects.
Project
In the case of the Supervision components, this Computer was earlier created as a
Station Node with an IP Address of 127.0.0.1 (the Loopback address) in Exercise -
Implement a Simulation Topology (page 11-7). Next, the Sim_Server must be
configured to appear identical to the genuine Supervision Server defined in the
previous chapter.
Once completed, the Simulation Executable will take its place alongside the other
three Supervision Executables.

Exercise - Create a Supervision Simulator

Outcomes
 Be able to map the Supervision project to a simulation environment.
1 Create the Simulation Supervision Executable.

i. Open the Project Explorer.
ii. Create a new Supervision Executable as below:
Identifier Sim
Description Tank1 Supervision simulation
Execution Domain Simulation
2 Map Services
i. Right-click the new Sim Executable and select Map Service.
ii. Map all Services to the Sim_Server Service.
iii. Close the Service Mapping tab.

Exercise - Create a Supervision Simulator
(cont.)
3 Map Communication.
i. Right-click the Sim Executable and select Map Communication.
ii. Open the Communication Mapping tab and Map IODevice_1 to the
Sim_Server and to NIC_Sim.
Note:
As was noted previously (in Exercise - Implement a Simulation Topology (page

11-7)), Communication Mapping in a Simulation environment is only required to
support Runtime Navigation Services (page 13-1).
iii. Close the Sim tab.

iv. Right-click the Sim Executable and select Build All.
After a few moments, the build will be completed.

Run the System
Draw Together At this point, all of the components necessary for a runnable system have been
the Resultant built. They now need to be delivered to their run-time locations.
Components
The Control Participant:
As soon as the control executable has been deployed (from the Topology
Explorer), PlantStruxure PES can open a connected session with the controller.
This means that the system will open an online session from the embedded
participant of the application running inside the controller.
Of course, from this point, the user has the ability to view the program but also to
modify it online. This will be discussed later in the course.
In the following exercise the control logic will be deployed in the Unity Simulator.
This hardware instance is hosted in the Station Node containing the Unity client.
The Supervision Participant:
Supervision projects are intended to be deployed from the Topology Explorer, from
within the hardware instance in which they have to run, however this functionality
is not yet available for PlantStruxure PES V4.2. Currently, the only method to
proceed is to download the projects from the Project Explorer in order to restore
them on an external instance of Vijeo Citect.
In this instance, the supervision project would be deployed from the engineering
station hosting the Vijeo Citect Runtime Server. By right clicking on this hardware
instance then on deployed, the deployment editor would be opened. It would then
be possible to choose the supervision executable.
In summary:
This means that both the Supervision and Control applications would be deployed
from the same point in the hierarchy.
Testing:
Once both of the components are deployed and running, the system will function as
if it is a fully deployed Control and Supervision environment. The exercises in this
chapter will deploy and execute both components and demonstrate the more
important aspects of the PlantStruxure PES solution.

Run the System (cont.)
Deployment Once the Executables are Built, they may be deployed to appropriate locations.
Targets
In the image below, it is clear that the Supervision Executable Ops would be
deployed to all production Supervision Station Nodes while the role of the
Engineering Station would vary depending on whether it was to be connected with
the live environment (using Eng) or the simulation environment (using Sim).
In fact, the Sim_Server station node would exist on the EngineeringStation,

although logically, they are different. When in Simulation mode, the Sim Control
executable would be deployed to the Sim_Server whereas the M580 would be
executing the Exec project in a live environment.

Download the Once fully built, the Supervision Project may be downloaded ready for
Supervision deployment.
Project
This process will identify the various components and make them available for
execution.
In the future, the deployment of the Supervision project will be done in the
Topology Explorer however in the current version, the only method available is to
download to the local drive and restore manually on the Station Nodes.
Note:
The Deploy Built Project option will directly insert the project into Vijeo Citect.
However, this requires that the installed version of Vijeo Citect is an identical
version. Although available, this method will not be used in the course as in most
situations, Service Packs or other updates will render the target version to be
different. In addition, this will currently only work after the first (manual)
deployment as until then, the project folder and links to the Vijeo Citect
environment have not been created.

Download the The Tank1_Supervision_Server and SGC_Include2 Vijeo Citect projects will be
Supervision restored into Vijeo Citect on the System Server:
Project (cont.)
While the DeviceConfig.xml file will be used to configure the System Server's
OPC interface via the OFS Configuration Tool:

Exercise - Download the Supervision Project

Outcomes
 Describe the process of downloading the completed Supervision Project to the
Supervision station.
1 Download and test the project.

i. Open the Project Explorer and expand the Supervision Executables
folder.
ii. Right-click Ops and select Download Projects.
iii. A dialog box will open inviting the user to download all components
of the Supervision project.
Note:
Tank1_Supervision_Ops is the actual Supervision project; SGC_Include2 is the

common resources project; DeviceConfig.xml is the OFS alias configuration file.

(cont.)
iv. In turn, select each of the three file entries and click the Download
button to export it.
v. Select or create a suitable folder for the files then simply click the
Save button when exporting each file.
Note:
Each file export will take a few seconds to complete, but there is no on-screen
indication that the export has completed. Students should wait (perhaps) ten
seconds after clicking Save before initiating the next export; particularly for the
SG2_Include2 item, which is the largest of the three files.

(cont.)
Note:
The SGC_Include2 file need only ever be downloaded once. It contains supporting
code for the environment and is never modified by any configuration activity
conducted within PlantStruxure PES.
vi. Close the Download pane.
2 Download the Simulation project.

i. Right-click the Sim executable and select Download Projects.
Observe that two of the three items seem identical to the previous
download session - but only one actually is. As was mentioned in
the note above, SGC_Include2 need only be downloaded once, but
DeviceConfig contains specific IP addressing for connection to the
simulated Control project, along with details of the tags to be
connected; the version downloaded on the earlier page contained IP
addresses for the 'real' environment.
ii. Download the Tank1_Supervision_Sim and DeviceConfig.xml
items.
iii. Close the download pane.

Manage Should the implementation environment include multiple computers acting as

Supervision Supervision clients, the deployed project may be distributed to all such computers
Clients without change.
On start-up, a VJC project will query the IP address of the computer upon which it
is running and compare it with the list of IP addresses and the roles associated with
that IP address embedded in the project. If no match is found, the computer will
simply start as a Supervision client.
As a general rule, whether or not a computer is configured as one of the various

Server modes, it will always be able to operate as a Client.

The Computer Practitioners ought to be familiar with the use of the Computer Setup Wizard to
Setup Wizard configure individual computers ready to execute the Vijeo Citect project.
To prepare a computer for a 'normal' project execution, little needs to be done in

the Wizard. The only requirements are that Events be enabled and that any Client
computers be configured to run the Cicode Function InitEvents() on startup.
This Function initialises user management tasks, such as idle time-out.

Exercise - Connect and Run the Control and
Supervision Components

Outcomes
 Confirm that the Control and Supervision projects work as expected.
1 Restore the Supervision components.

i. Launch the Vijeo Citect software. If there is no desktop icon, the
Instructor will advise how to launch it.
ii. From the Citect Explorer window, click the Restore Button.
iii. Click the Browse button to navigate to the location where the files
were saved in Exercise - Download the Supervision Project
(page 12-11).
iv. Restore the file SGC_Include2.ctz.

Exercise - Connect and Configure the Control
and Supervision Components (cont.)
Note:
If Vijeo Citect has an existing version of SGC_Include2 restored into it, this
should be removed and the version downloaded in the previous exercise used
instead. Although there is no evidence in the name of the file, the version included
with PlantStruxure PES V4.2 is newer than that shipped with previous versions of
PlantStruxure PES.
v. Repeat the process to restore the files Tank1_Supervision_Ops

and Tank1_Supervision_Sim.ctz
Note:
The three CTZ files may be restored in any order, but since the Tank1 projects rely
on components in the SGC project, multiple error messages will appear if the
Tank1 projects are restored first. These errors are transitory and are nothing more
than a temporary irritation.
2 (Optional) Examine the differences between the two Supervision

projects.
This step is of value to students familiar with Vijeo Citect.

i. Open various aspects of the two versions of the Tank1 Supervision
project and seek to identify where they differ.
ii. In the Variable Tags list, locate the tag
Site1.ChemicalTrea.Tank1.Agitation.S1CTT1A_TI1002 - it should
be (approximately) the 35th item in the list. Confirm that the
auxiliary information configured in Exercise - Instantiate the
Agitation Objects (page 4-41) (such as Engineering Units etc.) is
present.
Note:
It may be necessary to press the F2 key to see the expanded version of the dialog.
3 Configure the project.

i. In the Citect Explorer, ensure the project Tank1_Supervision_Sim
is selected and click the Computer Setup Wizard button.

Note:
If the Student's computer is to be connected to the physical M580 rack, the _Ops
project should be used instead at this point.

Note:
The Tank1_Supervision_Sim project is delivered out of PlantStruxure PES pre-

compiled; it is not necessary to compile prior to running the Setup Wizard.
However, if the target computer has VJC v7.50 without SP1 installed, a re-compile
will be required.
ii. Select Custom Setup and ensure the Tank1_Supervision_Sim

project is selected in the next screen (if it is not visible, a recompile
will be required; check with the Instructor if assistance is required).
iii. Click the Next button a number of times (the default settings are
fine) to advance to the Events page.
iv. Ensure Events are enabled for the Client.
v. Click Next.

vi. On the Startup Functions screen, use the Modify button to ensure
the Client is configured to run InitEvents.
vii. Click Next twice.

viii. On the Server Authentication screen, set the password to be
Corsek.
ix. Advance to the General Options screen and make the Startup page
sgc_StartupXGA (this may be different if a lower or higher
resolution page was configured in Exercise - Complete the
Supervision Graphics Page (page 9-29)).
x. Step through to the end of the Setup Wizard and click the Finish
Button to complete the process.

4 Configure OFS.
i. Run the OFS Configuration Tool. If it is not on the Desktop, the
Instructor will advise how to execute this program.
ii. Select the menu File » Open Archive.
iii. Navigate to the file location where the Supervision files were
downloaded.
iv. Select the file DeviceConfig and click the Open button.
Note:
If the Student's computer is to be connected to the physical M580 rack, the _Ops
version of the DeviceConfig file should be used instead at this point.
The contents of the file will be imported after a brief moment.

v. Close the OFS Configuration Tool. Confirm the save.

5 Run OFS.
This step is optional - if not already running, OFS will launch

automatically as part of the Vijeo Citect start-up.
i. Run the OPC Factory Server software. If it is not on the Desktop,
the Instructor will advise how to execute this program.
ii. After a few moments, the Server Status screen will be displayed.
iii. No further action is required. Minimise this window.

Exercise - Launch the Supervision Project

Outcomes
 Run the project and observe it in operation.
1 Run the Supervision project.

i. Return to the Citect Explorer window.
ii. Click the Run Button to launch the Supervision project.
2 Log in to the running project.

i. Once the project has started, click the down arrow button beside the
'little man' icon to access the login command.

Exercise - Launch the Supervision Project
(cont.)
ii. On the Login Form, use the credentials created in Exercise - Refine
the Supervision Project (page 9-38).
Name CT_operator
Password CT
iii. Click OK to login.
Once done, the name of the logged in user will appear beside the
'little man' icon.
3 Open the main graphics page.
i. Click the Page Select Button.

ii. Select the page CT_Tank1 from the drop-down list.
iii. Click OK to navigate to that page.

Popup Page The various features provided in the genie-linked popup pages (Faceplates) will be
Features extensively discussed in Supervision Standards (page 19-58).

Exercise - Execute the Projects

Outcomes
 Observe the Projects in operation.
1 Validate that the project is working correctly.

i. Click the temperature display object to the immediate right of the
tank (assuming that's where it was placed). A dialog similar to the
one below will open.
Note:
As it currently exists, several things must be done in the Control logic to be able to
run the project correctly. For instance, the SP value is set by default on local and
must be set to remote to be able to handle the PID loop with the analog input and
output. In order to avoid dwelling excessively on project completeness /
correctness these steps will not be undertaken.

Exercise - Execute the Projects (cont.)
ii. Select the Tools tab, click the Simulation button and then hover
over the Simulated PV field. Change the temperature to some new
value (this example uses 55 degrees).
Observe that the value in the dialog box has changed, also that the
main display in the graphics page is updated too.
iii. Click the close button in the upper-right of the dialog to close it.
Note:
If all of the buttons on any of these Popup pages are covered with black stippling,
the normal reason is that the inactivity timeout has been triggered on the current
user (CT_operator), and the user has been logged out - observe that the name is no
longer written in the current user field to the upper-left of the window. Simply
return to the 'little man' icon and re-login; the stippling will be removed.

Exercise - Execute the Projects (cont.)
2 Observe the matching change in the Control participant window.

i. Return attention to the Control Participant (this was set up for
viewing at the end of Exercise - Deploy a Control System
Simulator (page 11-12)).
ii. Observe that the same change has also been migrated back to this
view.
In the image below, observe the value 55 on the PV pin to the upper
right.
3 Continue to observe the running project.

i. Spend time opening the various dialogs and note the effect of any
changes in the matching Control project view.
ii. For instance, attempt the following changes:
 Change the high and low set points

 Activate or deactivate the Agitator.
iii. Determine a suitable method to test the functionality of the LSL
Interlock created in Exercise - Refine the Control Project (page
6-27).
4 How to shut the project down.
Although not required at this point of the course, Students should be

aware that there is a Shutdown command on the Tools menu at the
top of the running project. This command is only available once the
CT_operator is logged in.

Runtime Features
Setpoint and The object's setpoint is managed via the interplay of three factors.
Owner
Functionality
Owner Operator : Manual Mode (Owner=1)
 Set Point from Supervision Faceplate.
Owner Program: Automatic Mode (Owner=0)
 2 Modes managed by Remote value REM

- Sequential Control (REM=0)
Set point from Public variable Motor.SC.LSP
- Continuous Control (REM=1)

Set point from DFB Input interface RSP
By default, both 'Program Mode' and 'Sequential Control' are validated.

Runtime Features (cont.)
Setpoint and
Each object has a public structure (SC)
Owner
which may be used to monitor and
Functionality
control the object from other program
(cont.)
objects or sections.
Set point can be controlled from the

public variable SC or directly from its
RSP pin. The selection is done using
remote control bit SC.REM.
When an object is linked to its RSP

interface in PES, User has to set its
SC.REM to 1 to take into account the
value connected to its pin.
By Default SC.REM = 0 So the RSP

information is not taken into account.

Motor Control There are various aspects to the way in which a Motor (such as the one driving the
tank agitator - AG1002) might be controlled.
This is the representation of a motor controlled by wire. 3 signals are used:
 OP: Digital output command

 Running: Motor Cmd feedback
 Fail: Motor Protection
(Set Point depends of the operating mode)
When the Set Point is set to 1 in normal operation, the OP signal is set to 1 and the
feedback Motor Running returns 1 when the contactor is activated (auxiliary
contact, rotation detector…)
A timeout is configurable to take into account the feedback signal.

Motor Control
(cont.)
When the feedback signal fails, an alarm is set (blinking Red/yellow bell)
OP command may be maintained or reset to 0 when Rearm function is activated.
In that case a manual rearm is necessary to restart the Motor after a failure.
When the motor fails (Thermal overload, Over current, etc.) the Fail signal is
activated, indicated by a Warning panel near the Motor.
As for the Feedback signal, a rearm can be configured.
When the motor is controlled by communication, all the wiring signals must be
deactivated from the instance properties configuration. All necessary information
is derived from the communication in that case, but the motor functions remain
exactly the same.

External Control
Electrical wiring may be use to locally control the motor. In that case an input
Externally controlled EXTCTLD may be used to inform the Motor instance to not
take into account the "Motor running" feedback, as, discrepancies may occur
between the OP command and the feedback.

Local Panel A local panel may be used to control the motor directly from the field. The local
Control control interacts with the control system in a manner depending the configuration
done for the Local panel function:
 Local control: 2 or 3 positions button (zero is optional)

- CS / LP : Control System / Local Panel
- CS / 0 / LP : Control System / Zero / Local Panel
 Start / Stop
- Button 2 positions
- Push buttons PBSIGNALSEN
- Possibility to enable the Operator control directly from the push buttons
On CS position the Control System controls the operating

mode (Operator / Program, RSP, LSP)

Local Panel The 'zero' position:

Control (cont.)
On Zero position, motor control is deactivated. Motor

cannot be run neither from the control system nor the
Local panel.
A Yellow cross indicates that the motor cannot be

controlled from the control system.
The LP position:

On Local Panel position, the control comes from the Local
panel start / stop buttons.
A Yellow cross indicates that the motor cannot be

controlled from the control system.

Maintenance The maintenance function allows for 2 counters to determine the motor preventive
maintenance.
An alarm is set when the counter overflow, but it is possible to modify alarm
triggering in the supervision to have an alarm on a determined value.
Interlocks 7 interlocks are available.
Only the first Interlock can be configured directly from the PES editors.
Others must be programmed in refine mode.

Interlocks (cont.) Safe State:
For each interlock, a Safe state may be determined (SAFESTATE) with a highest
priority for the lowest interlock number.
It will force the motor Output command (OP) to the corresponding position.
For example if the need is to extract smoke on a fire alarm, safe state will be set to
one forcing the motor to start, if it's stopped.

Failures When using Failures function the Motor protections are linked automatically to the
first Failure Condition.
The CONDSUM block RESULT output pin is linked to the Fail input of the
DEVCTL block.
Up to 15 failures can be connected to one motor. The condition must be 1 to take

the failure into account.
Failures can be displayed in the faceplate from the Failure Tab.

Exercise - View Motor Control in Operation

Outcomes
 View the Motor Template in operation on a Vijeo Citect graphics page.
When the Agitator Motor was instantiated, only Alarm and Failures were enabled.
Checkboxes were not ticked for ExternalControl or Local Panel.

(cont.)
1 Open the Agitator Motor genie.

i. Double-click the Agitator Motor genie to open the faceplate.
ii. If the Student's computer is running the Simulation project, click the
Operator button to take manual control of the motor. If the
computer is connected to the M580, this step is not required.
Refer to Setpoint and Owner Functionality (page 12-29) - setting

the Operator mode will permit the setpoint to be managed from the
Faceplate.

(cont.)
This exercise will work best if the student computer remains

connected to the M580 rack in the training room. If that is not
possible, the physical switch actions in the steps below may be
emulated via the running Unity Pro in the Refine Online interface.
iii. Identify the physical switches labelled A_AG1002_Motor_Fail and
A_AG1002_Motor_ZSH (the running feedback signal). They should
be the first two switches on the block.
2 Use the Fail signal.

i. Ensure both switches are in the ON position.
ii. Start the motor from the Faceplate.
<need an image>
iii. Turn OFF the A_AG1002_Motor_Fail switch (this may indicate a

thermal overload for instance), the motor will stop and the failure is
displayed.
<image of failure>
iv. Turn ON the FAIL switch, ACKnowledge the failure and click the
rearm button, the motor will restart.
v. Turn OFF the ZSH switch - the motor will stop, an alarm is displayed.
vi. Restart the motor and then turn ON ZSH, normal behaviour will
resume.
vii. Close the Motor Faceplate.

(cont.)
3 Use a Remote Setpoint.
The Remote Set point will be shown on the motorised valve in the
Water section.
i. Open the PID Faceplate and set it to Manual mode, then set the
output to 60%. The PID output indicates 60% but the motorised
valve remains on the same value even if it is in program mode.
ii. From the Online Refine view, open the section where the valve is
used and set the SC.REM to 1, immediately the Motorised valve
output is set to 60%.
iii. Close all views.

Alarm Templates
Organise Alarms As part of the creation of the System, an Alarm Management structure was
automatically included, containing definitions for all the Alarms most likely to
occur in the running project.
This Alarm infrastructure was constructed to match the plant hierarchy defined in
the Application Explorer.
Every Alarm has a right-click menu which allows the (properly authenticated)
operator to either acknowledge or disable that Alarm.
In addition, anyone may view more detailed information about an Alarm.

Exercise - View and Manage Alarms

Outcomes
 Observe Alarms and the hierarchy in which they are managed.
1 Open the Active Alarms page.

i. From any page in the project, select the Alarms tab at the top of the
page and click the Active Alarms button.
The Active Alarms page will open.

ii. Adjust the column widths to display all information.
iii. Expand the hierarchy on the left to see the position of all current
Alarms (they are shown with blue numbers in parentheses).
Observe that in the instance shown above, the Alarms had occurred
in the Agitation and Discharge sections.
More importantly, observe that the Equipment Hierarchy in the left

pane exactly mirrors the hierarchical folder structure built during the
creation of the System in PlantStruxure PES. Further, that none of
this required any additional configuration during the creation of the
project.

Exercise - View and Manage Alarms (cont.)
2 Manage Alarms.
i. Right-click an Alarm and select Information.
The Alarm information dialog will be displayed.
ii. View the information displayed. When done, click Close Button
in the upper-right corner of the dialog to close it.
iii. Students may optionally also use the Acknowledge and Disable
options on the right-click menu.

Alarm Templates (cont.)
Sort and Filter One or more checkmarks may be placed in the hierarchy display to the left of the
Alarms Alarm display. When no checkmarks are in use, all Alarms will be displayed (this
is the same as if every checkbox was ticked). Whenever any checkbox is ticked,
only Alarms related to the checked item will be displayed.
Observe the message at the top of the hierarchy noting "Alarms Filtered." This is
in contract to the message "All Equipment" which will be displayed when no filters
are in place.
In addition, the list of displayed Alarms may be sorted on any column.
Clicking on the column header will cycle through three options:
 No sorting
 Top-to-bottom sorting
 Bottom-to-top sorting
The small blue triangle (seen on the right-most column in the image above)
indicates the column and order.

Exercise - Filter and Sort Alarms

Outcomes
 Be able to manage the presentation of Alarms in the Supervision pages.
1 Filter Alarms.
i. In the hierarchy view on the left side of the Alarm page, ensure the
levels are fully expanded.
ii. Place a check mark in a box for which it is indicated that an Alarm
exists (with the blue number in parentheses).
In the image above, two Alarms were present (one in each of the
Agitation and Discharge sections). The checkmark was placed
against the Agitation Alarm and once selected, only this Alarm is
displayed, the Discharge Alarm is now hidden.
iii. Place a checkmark beside another Alarm to make it visible.
iv. Remove all checkmarks to return to having all Alarms displayed.
Observe that checkmarks may be placed higher up the hierarchy in

order to address multiple groupings of Alarms in a single action.

Exercise - Filter and Sort Alarms (cont.)
2 Sort Alarms.
i. Select any column of the Alarm display and click on it three times
slowly in succession.
The first time it is clicked, a small blue inverted triangle will be

displayed to the right of the column, indicating that Alarms being
displayed are sorted by that column and are being shown highest to
lowest. The triangle will be reversed on the second click, and the
order of display also reversed. After the third click, the triangle will
vanish and the Alarms displayed in whatever order they were in prior
to the first click.

Sequence of Events
System Log The Sequence of Events log maintains an uneditable record of all actions that
occur on the running System.
This includes (but is not limited to) the following:
 Server startup
 User authentication (failed attempts are not recorded) Operators may
 User actions (start a motor, stop a pump etc.)
 Alarms
All of these may be seen in the image above.
In addition three options are available on the right-click menu.
 Comment: creates a new entry with the same timestamp as the entry upon
which the right-click was selected. This option permits the annotation of
existing entries in the Log.
 Add Event: will create a new entry in the Log with the current date and time.
 Information: will display a static dialog of information in much the same
fashion as the Alarm Information dialog.

Exercise - Access the Sequence of Events Log

Outcomes
 Open and view system log entries for the running project.
1 Open the Sequence of Events Log.

i. On the Alarms Menu tab, click the Sequence of Events button.
ii. This will open the full log of all events stored since the Log was
started.
iii. View the items listed and consider the actions already undertaken
which might have caused the entries displayed in the list.
iv. Right-click any item in the list and view the information dialog
shown.

Exercise - Access the Sequence of Events Log
(cont.)
2 Manually add log entries.

i. Right-click any item on the Sequence of Events list. Select
Comment...
ii. Add some easily-identifiable text and click the OK button to save the
message.
Observe that the new message has been given the identical time and
date as the message which was right-clicked. This permits operators
to add their own annotations to existing entries added automatically
by the system (for instance, "it wasn't me!").
iii. Right-click and add an Event.
iv. Once saved, it may be observed that the new event is given the date
and time true at the moment the comment was saved.
Note:
In neither case does the operator have the ability to remove self-created entries.

Chapter Outcome
Summary of A Vijeo Citect project will run on any computer as long as the local IP address is
Activities the same as the addressed configured in the project.
Thus, to configure the project to run in the simulation environment it need only be
linked to the Sim_Server (which was previously given Loopback as its IP address).
Having Built this Supervision project, it was deployed to the local computer and
executed.

Summary
 Create a Simulation Environment (page 12-3)

 Run the System (page 12-7)
 Runtime Features (page 12-29)
 Alarm Templates (page 12-44)
 Sequence of Events (page 12-50)
 Why are the Control and Supervision projects distributed separately?
 When the Supervision Simulation project was downloaded, why was there no
need to download the Include library? What about the XML?
 What task does the OFS package perform?

Chapter 13: Runtime Services
Introduction
Introduction
Once the system is constructed and operational, there are a number of features that
may be utilised to enhance the operational aspects of the environment.
 Utilise in-project run-time services
 Operation Client .................................................................. 13-4

 Project-based Documentation ............................................ 13-18
Aim of this Chapter
Expected In addition to the 'normal' services provided by both Unity Pro and Vijeo Citect for
Outcome a running environment, PlantStruxure PES provides additional infrastructure over
and above this support.
This is why the Engineering Lifecycle diagram includes a separate 'Execution'

phase.
The Operation Client runs on the Supervision Client computer and is accessed via
any genie object included via PlantStruxure PES.
This gives access to the cross-reference tool.

Expected In addition, support for in-project documentation is provided via the same
Outcome (cont.) interface.

Operation Client
The Operation When defining Station Nodes (in Station Nodes (page 8-3)), there existed the
Client possibility of defining:
Supervision Servers To coordinate the collection of field data from the

devices (defined in The Topological Explorer (page 5-
5)) and to make such data available for the use of
Operation Clients.
Operation Clients To provide a graphical representation of the Plant for

the site Operators in order for them to view and manage
the system.
In the image above (taken from The Scenario (page 5-3)), it is clear that three
station nodes have been defined; however ignore, for the moment, the Engineering
Station - it as an arbitrary representation of the computer upon which the
configuration was constructed.
The Supervision Server will execute all Vijeo Citect server tasks (it may also act as
an Operation Client, but that option will be ignored for the moment) while the
Operation Station will be the site management station.

Operation Client (cont.)
The Operation In order for the Operation Station to take advantage of the various additional
Client (cont.) services provided by PlantStruxure PES, it must have access to the resources
included in that software. This means that, in addition to being a Vijeo Citect
client, it must also connect to the various PlantStruxure PES resources - this is
done by authenticating as an Operation Client.
This chapter will explore the services available to an Operation Client and expand
upon the glimpse provided in Exercise - Examine the Running Project (page 12-
23).
System The Runtime Services interface permits the real-time tracking of actions in the
Diagnostics plant by displaying a live view of the Control project which is able to respond to
changes in the actual plant.
Every object added to a Graphics page from the system-supplied Toolbox included
access to this management interface.
Here a change to the running Supervision project was reflected immediately in the
view displayed in the Control Participant.
This immediate view of the system permits the rapid analysis and diagnosis of
plant control issues.

Execution The Operation Client will only display objects that are assigned to projects or
Domain mapped to executables that have the same Execution Domain (page 7-4).
Advantages Runtime navigation services describe the services that Process Expert provides
during runtime, and which permits the viewing of:
 Information on an instance of the application, such as system-based, and/or

user-based data, for example:
- The section of the Control project that contains the constituents to perform
troubleshooting.
- The controller.
- Hardware information through Web diagnostic.
- Documentation on equipment to perform maintenance and repair.
- Pictures, providing additional information on the process.
 Related instances and their information.
 Information on the controllers and station nodes to which the project is
deployed.
Following the deployment and execution of the Control and Supervision projects of
a system, runtime navigation services are provided by the Process Expert Operation
Client and the Operation Client Viewer. The Operation Client is the entry point to
access instance-related information, which is grouped in different sections.
Information may be displayed in the Operation Client by acting on the Supervision

runtime. More detailed information may be viewed in the Operation Client
Viewer, which is a read-only user interface.
Further, the information displayed may be customised for each instance by adding
various files, which may be opened from the Operation Client.

How to Open the The Cross References dialog is linked to the Engineering Client window.
Cross References
Interface  To open the Cross References interface
In the runtime Supervision view, <ALT> + click any genie object.
When the <ALT> key is pressed, a green rectangle will appear if the function is
valid for the object under the mouse.
When the mouse is clicked, the Cross References dialog will appear.

Exercise - Operation Client

Outcomes
 Be able to diagnose run-time issues.
1 Launch the Operations Client.

i. From the Start Button, run the program Schneider Electric »
StruxureWare » Process Expert » Operation Client.
A link to the Operation Client may also be on the desktop.

ii. Log into the system in the same manner as was done for the
Engineering Client.
iii. Click on the Supervision text object to launch the Supervision

Runtime Services.
Observe that the Operation Client may be run before (or after) the
launch of the Control and Supervision projects.
iv. Double-click the Operation Client titlebar to convert the window to
'translucent' mode.

Exercise - Operation Client (cont.)
v. Drag the window across some other part of the screen to confirm
translucency.
vi. Again double-click the titlebar to return to opaque mode.
2 Ensure all projects are running.

i. Ensure the current Control project has been deployed to the
simulator.
Do not enable Refine Online. If it is currently running, close it.

ii. Ensure that the Supervision project is also running.
iii. Confirm that all data elements on the Graphics Page are showing
valid information.

3 Launch the Cross References tool.

i. Ensure that the Supervision project has the focus.
ii. Hover over the Agitator Motor at the top of the graphics page. A
white box will be drawn around this item.
iii. Hold down the <ALT> key and a green outline will be drawn around
the entire genie object.
Note:
The location in which the green rectangle is drawn is only saved in association with
the genie from within PlantStruxure PES; any updates completed within the
Supervision participant independently of PlantStruxure PES will not preserve this
information. This is the reason for the warning included in Create a Graphics
Page (page 9-28).

iv. Click the mouse button once and a Cross References dialog will
appear.
v. Expand all levels.

vi. Hover over any item to see the previously configured Description
displayed as a tooltip (the Low Level Switch in the image below).

4 View Object Services.

i. In the Application folder, double-click any one of the three items
displayed.
ii. Expand the folder Object Services » Control.
iii. Double-click the Agitation entry. After a few moments, this will
open the Agitation Section of the Control project in a local view
window.
Although difficult to see in this view, this screen may be maximised

for a clearer inspection of the FBD section.
By opening this view, it is an easy matter to troubleshoot issues with

the running environment as changes made in the Supervision project
will immediately be seen in the matching Control project.

iv. Open the Agitator Motor genie.
v. Locate the AG1002 FBD entries in the Agitator view of the Control
participant.

vi. Set the Genie buttons to be Owner: OPERATOR and SetPoint: ON.
vii. Click the REARM button.
Note:
The Agitator will have to be in an Alarm state in order for the REARM to execute,
which it ought to be since the level is currently zero and the interlock should be in
effect. If it is not in Alarm, modify the level to cause the Agitator to be in Alarm
then resume with the step above.
It is suggested that the Agitator be set to running, and the Low level switch ON and
the High level switch OFF.
viii. Immediately the button is clicked, take note of the Control

Participant view.
The OP pin on the AG1002 DEVCTL FBD will become TRUE for
approximately 3 seconds (this is as a result of the value attached to
the TIMEOUT Pin). Immediately, the line connecting this pin with
the two adjacent FBDs also becomes TRUE.

Observe also that the start count on pin MCNT of the AG1002
DEVMNT FBD will increment with each successive press of the
REARM button.
Note:
This is a simple example of how the Supervision and Control projects are able to
interact at run-time. Students are encouraged to spend further time investigating
the richness of this interface.
ix. Close the Agitation Section viewer.
5 View the Linked Topological Objects.

i. Double-click the Sim_Server object.
ii. This will open a new tab to display the Topological objects of the
Sim_Server. Expand the sub-item structure.

iii. In the simulation environment, the system cannot open any

configuration information for the NIC entry as it is linked to the
Loopback address. Students are invited to re-attempt this step
when using a live environment.
Note:
Only objects belonging to the same Execution Domain (page 7-4) (here,
'Simulation') may be traversed from within a single Cross References popup.
iv. Close the Sim_Server tab.
6 Investigate the Application View.
Observe that the list of entries does not include the item on the
Supervision page from which the Cross Reference view was launched
(in this instance, the AG1001 item).
i. Double-click one of the Application View items (the steps below use
the low-level switch).

ii. A new tab will open in the Cross References dialog showing
information for the Low Level switch. Expand all hierarchical levels.
This method permits the changing of the selection made via the
<Alt>-click method used in Step 2 above, which originally selected
the Agitator Motor. Observe that this method remains confined to
the originally selected FBD section (Agitation) - there is no method
provided to switch attention to (for instance) the Water objects aside
from returning to the Graphics Page and <Alt>-clicking a new object.
Note:
Further functionality in this view will require a 'real' configuration - the simulator
is unable to deliver the information requested by any further requests.
iii. Close the Operation Client dialog.

Project-based Documentation
In-Project The creation and use of an Operation Client permits the customisation of the
Documentation Runtime Popup page to display equipment-relevant documentation.
This interface permits the linking and display of PDF documents, .zip, .xml and .txt
files along with JPEG images. In addition, web-page links may be established.
All content is linked to the name of each individual Instantiation; in addition there
is scope for a global shared repository. In the example above, the reference to the
navigation Services PDF and to the web page are local to the currently selected
Instance (S1CTT1AG_AG1002 - the Agitator Pump Motor), while the Process
Expert User Guide entry is sourced from the shared location.

Project-based Documentation (cont.)
In-Project To reference a web link, create a file named WebDiagnostics.xml with the
Documentation following content:
(cont.)
<Catalog>
<WebDiagnostic url="Web_Page_Address"
name="Web_Page_Name"
description="Web_Page_Description"/>
</Catalog>
Where:
Web_Page_Address Url of the Web page that you want to open in the
default browser
Web_Page_Name Name of the Web page that is displayed in the

operation client menu list
Web_Page_Description Description that appears in the tooltip
WARNING
MALICIOUS WEB SITES
Web links to external sites may expose the computer to malicious software.
equipment damage.
It is wise to ensure both the validity of the web pages being referenced through this
method and also that corporate security systems will permit the connection.

In-Project To reference a PDF (or many other file formats) create a file called
Documentation FilesConfiguration.xml with the following content:
(cont.)
<Catalog>
<FileConfiguration url="PDF_File_Name"
name="Document_Name"
description="Document_Description"
arg="/A page=X"/>
</Catalog>
Where :
PDF_File_Name Name of the file with the .pdf file extension
Document_Name Name of the document that is displayed in the

operation client menu list
Document_Description Description that appears in the tooltip
X Number of the page to open

In-Project Other files, such as an image file may be referenced by using the following syntax:
Documentation
(cont.) <Catalog>
<FileConfiguration url="File_Name.Extension"
name="Document_Name"
description="Document_Description"/>
</Catalog>
If it is possible to create several document references In a single file, simply enter

each command line between the <Catalog> and </Catalog> identifiers.

Exercise - Create In-Project Documentation

Outcomes
 Add documentation links to the Operations Client.
1 Create the Content location.

i. Open Windows Explorer and create a folder in the root of C:\ drive
called Content.
ii. Right-click the new Content folder and select Properties.

(cont.)
iii. Select the Sharing tab and click the Advanced Sharing button.
iv. Check the box Share this Folder.

(cont.)
v. Click the Permissions button. Set this dialog to Allow Full Control
for Everyone.
vi. Click Apply and OK for each dialog to close them all.
2 Create Instance Folders.

i. Navigate to and open the Content folder.
ii. Create a folder for each Instance used in the Agitator FBD section
(these are the exact names given to the Instances in Exercise -
Instantiate the Agitation Objects (page 4-41)):
S1CTT1A_AG1002
S1CTT1A_LSH1002
S1CTT1A_LSL1002
S1CTT1A_TI1002

(cont.)
3 Populate a Folder.
i. Open the S1CTT1A_AG1002 folder.
ii. Right-click a blank area of Windows Explorer and select New » Text
Document.
iii. Name the new document WebDiagnostics.xml.
iv. Right-click and Edit the new text file to insert the contents:
<Catalog>
<WebDiagnostic url="http:\\www.schneider-electric.com"
name="Schneider Electric"
description="SE's Web Site"/>
</Catalog>
v. Save the file.
vi. Create another new file in the same folder.

vii. Rename it as FilesConfiguration.xml.
viii. Open the new file and edit it to contain this text:
<Catalog>
<FileConfiguration url="Process Expert Navigation Services
User Guide.pdf"
name="Navigation Services"
description="Navigation Services User PDF"
arg="/A page=27"/>
</Catalog>
ix. Save the file.

(cont.)
x. Navigate to the location C:\Program Files\Schneider

Electric\StruxureWare\Process Expert\User Guides.
xi. Copy the file Process Expert navigation Services User Guide.pdf
to the folder C:\Content\S1CTT1A_AG1002.
xii. Copy the file Process Expert User Guide.pdf to the folder
C:\Content.
xiii. Copy the FilesConfiguration.xml file from the S1CTT1A_AG1002
folder to the C:\Content folder.
xiv. Edit the file to reflect the needs of the User Guide (not the
Navigation Services, as it currently does).
4 Launch the Client.

i. Re-launch the Operation Client.

(cont.)
5 Open the informational dialog.

i. Hover over the Agitator motor and hold the keyboard <ALT> key
down. Click on the Motor.
ii. Expand the Object Services tree and observe there are new entries.
iii. Open the Diag Web Server and Documents folders to observe
entries matching the structures created previously.
Observe that both PDF documents are visible.

iv. Double-click the Navigation Services item to open the linked
document. Similarly, test the User Guide.
v. Close the PDF documents and close the browser instance.
Note:
Special contents in the Operation Client popup are only refreshed when the
Operations Client is started. The Vijeo Citect project may keep running.

(cont.)
6 Test documentation for a different Instance.

i. Open the Application View folder in the Operations Client and
double-click the S1CTT1A_LSL1002 item.
Recall that the Web and Navigation items were configured to exist
only in the S1CTT1A_AG1002 folder; thus they are not visible from
this view. Only the User Guide, which was configured as a global
item may be seen.
7 (optional) Extended experimentation.

i. Explore the relationship between file location and accessibility
further. Design a test to ensure it is fully understood.
ii. Create a new FilesConfiguration.xml file that is configured to
create multiple menu entries on the Operations Client menu.
8 Complete the exercise.

i. Close the running Vijeo Citect project (on the Tools menu).

Chapter Outcome
Summary of In this chapter, access was given to the Operation Client via the green rectangle
Activities displayed on any PlantStruxure PES-provided genie:
In addition, exercises were provided to demonstrate the inclusion of custom

documentation links to either local files and images or to web pages located inside
or outside the organisation.

Summary
 Runtime Services (page 13-4)

 In-Project Documentation (page 13-18)
 When would the Runtime Services interface be useful?
 How is the Cross References tool opened?
 Why would the Object Services view be useful?

End Day Two - Summary
Summary At the end of day two, students should:
 Topology Explorer:
- Define Computers (Station Nodes) and other devices
- Define networking
 Project Explorer - Supervision:
- Create and Refine a Supervision Project
- Map and Build the Supervision project
 Project Explorer - Control:
- Create a Control simulation environment
- Link the Simulation to the existing hardware and template instantiations
- Deploy the Control project to the simulator
 Create and deploy the simulation environment
- Build the simulation
- Deploy the Supervision project to the SCADA system
- Test the Control and Supervision components
 Runtime Services
- Examine how Runtime Services help with debugging
- View program sections
- View documentation.

PlantStruxure PES Configuration v4.2 2016-09-28 Vol1

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

PlantStruxure PES Configuration v4.2 2016-09-28 Vol1

Uploaded by

Copyright:

Available Formats

Manual Release 4

PlantStruxure PES Configuration

INTRODUCTION AND LEGAL NOTICE

David Heath, Richard Irons

November 2016 Edition for PlantStruxure PES V4.2

ii PlantStruxure PES V4.2 November 2016

The addition of this symbol to a "Danger" or "Warning" safety

This is the safety alert symbol. It is used to alert you to potential

PlantStruxure PES Configuration Manual Release 4 iii

iv PlantStruxure PES V4.2 November 2016

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

In some applications, such as packaging machinery, additional operator protection

PlantStruxure PES Configuration Manual Release 4 v

Coordination of safeties and mechanical/electrical interlocks for point-of-

Software testing must be done in both simulated and real environments.

vi PlantStruxure PES V4.2 November 2016

Before energizing equipment:

 Remove tools, meters, and debris from equipment.

 Regardless of the care exercised in the design and manufacture of equipment

PlantStruxure PES Configuration Manual Release 4 vii

viii PlantStruxure PES V4.2 November 2016

 Users who are new to PlantStruxure PES

Prerequisite It is expected that trainees will be familiar with:

PlantStruxure PES Configuration Manual Release 4 ix

1  Introduction to PlantStruxure PES

SimpleSystem.dbk Backup for use in database backup/restore.

EmptyDatabase.dbk Backup of empty database

Training.ctz Common module for all PlantStruxure PES training

x PlantStruxure PES V4.2 November 2016

1 Run the Milk_Upgrade project then trigger and view some

PlantStruxure PES Configuration Manual Release 4 xi

Hints & Tips:

Open a menu “File” then select the menu option “New…”

xii PlantStruxure PES V4.2 November 2016

PlantStruxure PES Configuration Manual Release 4 xiii

CHAPTER 1: PLANTSTRUXURE PES AT A GLANCE ................................................... 1-1

CHAPTER 2: MANAGE THE PLANTSTRUXURE PES ENVIRONMENT ......................... 2-1

CHAPTER 3: DEVELOP THE SYSTEM STRUCTURE ..................................................... 3-1

CHAPTER 4: CREATE THE APPLICATION ................................................................... 4-1

CHAPTER 5: CREATE THE PAC TOPOLOGY.............................................................. 5-1

CHAPTER 6: CREATE THE CONTROL PROJECT ......................................................... 6-1

PlantStruxure PES Configuration Manual Release 4 xv

CHAPTER 8: DEFINE THE COMPUTERS AND NETWORKS .......................................... 8-1

CHAPTER 9: CREATE THE SUPERVISION PROJECT ................................................... 9-1

CHAPTER 10: FINALISE THE SUPERVISION PROJECT................................................ 10-1

CHAPTER 11: THE SIMULATION ENVIRONMENT ...................................................... 11-1

CHAPTER 13: RUNTIME SERVICES............................................................................. 13-1

xvi PlantStruxure PES V4.2 November 2016

CHAPTER 15: ONLINE CHANGES ............................................................................... 15-1

CHAPTER 16: EXTEND THE SYSTEM .......................................................................... 16-1

CHAPTER 17: DISTRIBUTED I/O DEVICES ................................................................. 17-1

CHAPTER 18: CONFIGURE A REDUNDANT M580 ...................................................... 18-1

CHAPTER 19: INTRODUCE THE GENERAL PURPOSE LIBRARY ................................. 19-1

CHAPTER 20: MANAGE CHANGE ............................................................................... 20-1

PlantStruxure PES Configuration Manual Release 4 xvii

CHAPTER 22: MULTI-USER CONFIGURATIONS ......................................................... 22-1

CHAPTER 23: CONSOLIDATION WORKSHOP ............................................................. 23-1

APPENDIX A: ADDITIONAL EXERCISES ...................................................................... A-1

APPENDIX B: INSTALLATION GUIDE ........................................................................... B-1

APPENDIX C: SIMPLE IMPLEMENTATION................................................................... C-1

APPENDIX D: PLANTSTRUXURE PES IN THE ENGINEERING LIFECYCLE ................. D-1

APPENDIX E: GLOSSARY OF TERMS ............................................................................ E-1

xviii PlantStruxure PES V4.2 November 2016

By the completion of this chapter the student will be able to: