Documente Academic
Documente Profesional
Documente Cultură
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
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
Contributors
Eric Coudurier, Pascal Lavallee, Rodrigo Romero, Johnatan Feuillye, Warwick Black, Olivier Guthmann
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.
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.
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.
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.
Note:
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.
Operation and The following precautions are from the NEMA Standards Publication ICS 7.1-
Adjustments 1995 (English version prevails):
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.
Target The PlantStruxure PES Configuration training course is an integral part of the
Audience complete Educational Services curriculum. This course is designed for:
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.
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.
Day Topics
Introduce PlantStruxure PESt
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.
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.
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
Example -
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…
Horizontal and Text written this way indicates the Horizontal then the (Vertical) tab is to be
Vertical Tabs selected.
Example -
Appearance (General)
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.
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
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.
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.
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.
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.
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.
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.
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.
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)).
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:
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.
The Floating License Manager (installed alongside the PlantStruxure PES product)
is used to activate the software.
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.
Operation
1 Class discussion.
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.
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.
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.
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.
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.
Once this is done, the local Engineering Client will create a connection to that
remote computer.
The only field of interest is the use of local virtual machines. The
Instructor will advise whether to check or uncheck this option.
i. Double click the PES Server icon to launch the back-end server
component.
iii. As part of the startup sequence, a user must authenticate the client.
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?
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.
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.
Overview - The
Various The Library explorer is accessed via the Global Templates button on the main
Explorers menu tab and is responsible for:
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.
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).
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 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:
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.
The Project Explorer is the primary topic addressed in the chapter Create the
Project (page 6-1).
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.
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.
Restore the An option on the Tools menu may be used to import a database.
database
Note:
iii. This process will complete by closing the System Server window.
Re-start the System Server from the desktop icon.
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.
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.
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.
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.
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.
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.
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 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.
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.
See Also:
For further information about Database Migration, see PlantStruxure PES Help -
Installation Guide, Chapter 4.
What is a system?
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.
Client When the PlantStruxure PES Engineering Client is started, the main front page will
Components appear.
1 Toolbar
2 Tabs bar
3 Workspace toolbar
4 Workspace
5 Notification panel
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 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.
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.
ii. Right click the Systems Explorer object and select Create System.
iii. After a few moments, the new system (by default called System_1)
will be created.
Note:
iii. Click the close button in the upper right of the properties view
to save the change.
Note:
When an explicit save action is required PlantStruxure PES will warn the user if
they attempt to close an edit screen without saving.
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.
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.
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.
Engineering
Lifecycle
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.
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.
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.
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 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 Data Facet The Citect Data Facet may directly represent Citect data
(tags etc.) or it may be a composite, combining many such
objects.
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.
Also, it is possible to create as many projects as required that will use instances
from the same application in different combinations.
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:
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.)
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):
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.)
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.
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.
can be simplified to
S1.CT.T1.W.CV10001
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.
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.)
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.
An Application Explorer Tab will open with the Corsek item at its
root.
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.
Water
Agitation
Discharge
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.
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.
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.
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
iv. Click the Browser tab in the lower left corner to return to the
'normal' view.
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.
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.
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.
Template The Template Browser provides an organised list of pre-built templates which may
Browser be incorporated into a System under development.
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.
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:
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
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.
Instantiate four items into the Water object (in addition to the items
above, a Setpoint tool will also be included)
ii. Select the $AnalogInput1 template. This will represent the Flow
Indicator.
Note:
What has been added to the Water folder is a new Object which is based on the
$AnalogInput1 template.
Note:
Information button.
This will indicate the source of the error. In this particular instance,
the name is too long.
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 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.
Observe that the Link field remains invalid after updating the
Properties. This will be resolved later in the chapter.
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.
Security Area 1
Note:
Security Area 1
ii. Open the path Control » AnalogInput1 » Logic and select the
Range section. Set the values the same as the image below:
Note:
Security Area 1
ii. Select the Tags field in the left pane and set the field Name of the
Alarm Tag to be LAL1002.
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.
ii. Right-click in the Agitation pane title area and Paste the object.
Name LSH1002
Security Area 1
Security Area 1
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:
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.
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.
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.
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.
iii. The link editing tool will open with the object loaded.
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. 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.
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.
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.
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.
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.
Note:
Only the M580 Local Rack will be configured in this chapter. The remainder of
the architecture will be created in later chapters.
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.
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.
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.
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:
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.
Controller A controller may be created by selecting Create Controller from the right-click
Creation menu then choosing the type of controller to create.
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.
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.
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.
+
ii. Click the Validate tickbox to save the configuration changes in the
Control Participant.
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.
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.
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.
The Bottom-Up
Process (cont.)
Note:
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.
There is a template for everything including the rack, field bus, etc.
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).
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.
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.
Expected Work undertaken in this chapter will be confined to the Project Explorer.
Outcome (cont.)
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.
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:
ii. The Project Explorer will be opened on a new tab labelled Corsek.
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).
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.
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.
Unlink Remove the link between the Facet and the system, to modify what
the system has generated, directly from the participant.
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.
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
Here, all the facets of the instances of the application folder will be assigned to the
same container.
Option 4
Drag individual Instances from the instances pane to the Assignments pane.
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.
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.
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).
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.
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 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.
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 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.
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:
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.
iii. Right click the Agitation object in the MAST - Containers pane and
select Refine.
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.
Create an interlock such that the Agitator cannot operate when the
water level is below the Low Level switch.
Note:
Note:
A matching interlock on the High-level switch will be added later in the course
using a different method.
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.
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.
iii. Once the Control Participant interface opens, click the Check
Consistency button.
Summary of A Control Project was created and FBD Sections created to manage the
Activities organisation of the various pieces of PLC code.
Why might you need to refine a project? Give some specific examples.
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.
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.
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.
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.
iii. After a few moments (to permit the action to take place), the
Executables will display the newly created ControlExecutable_1.
Name it Exec.
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
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
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.
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.
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.
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.
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.
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.
ii. When the Hardware Mapping tool loads, observe that Physical
instances are in the left pane; Logical instances in the right.
iii. Drag the FI1001 object in the right pane to one of the DInputCh
entries in the left pane.
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.
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:
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.
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).
Digital Inputs:
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:
Analog Inputs:
Analog Outputs:
vi. Once there are no facets remaining in the list on the right, close the
Tank1_Control.Exec Hardware Mapping tab.
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
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.
An extended view of the Build status is available via the small down-
facing arrow-head beside the word 'Details.'
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.
The Variables:
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.
If the CPU does not respond to the Ping command, check the cabling
and settings, including the IP address of the PC.
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.
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.
Note:
If the Run engine after deployment is not ticked, there are options on the right-click
menu to Run and Stop the PAC.
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.
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.
If real hardware was available then the project was also deployed to the PAC.
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.
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.
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.
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:
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.
Three Station As was seen in the network diagram, three Station Nodes will be defined.
Nodes
Dual NICs
Vijeo Citect
Unity Pro
Dual NICs
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.
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
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.
Instance
Unity Pro The presence of Unity Pro advises PlantStruxure PES that
the Station Node is capable of emulating a PAC.
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.
Note:
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.
Area 1
Area 1
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.
Area 1
Area 1
Note:
Area 1
Area 1
Area 1
Area 1
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.
ii. Do this twice more, naming the additional Networks Field and
Operation.
ii. Link the CPU Ethernet connection to the Control network and the
other Ethernet connection to the Field network.
Note:
The various NICs were named to match their roles in the form
NIC_<Device>_<Network>, thus simplifying the management of the various
interfaces.
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.
What are the services that can be configured for a station node?
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.
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.)
Supervision In order to lay out the framework of the Supervision project, it is necessary to first
Components Create a 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.
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).
Note:
Further Training:
The implementation of multiple clusters and servers is a topic in the Vijeo Citect
Architecture and Redundancy Course.
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:
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.
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.
ii. A screen looking similar to the Tank1 facet assignment dialog (seen
in Exercise - Assign Control Facets (page 6-17)) will appear.
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.
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.
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.
iii. Right-click each of the servers to observe their properties. Leave the
servers with their default names.
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.
Of course the alternate is that multiple Client projects may be created to suit the
needs of multiple Operator Stations throughout the plant.
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.
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.
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.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
To summarise:
ii. When the Tank1_Supervision dialog opens, click the Add button.
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.
A new window will open displaying the Vijeo Citect Graphics Builder
interface.
WARNING
LOSS OF DATA
Do not use this interface to access elements in the Project Editor.
Failure to follow these instructions can result in death, serious injury, or
equipment damage.
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:
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.
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.
2 Add a genie.
i. Drag the FC1001 entry (WATER $PID) entry to the main graphics
page area.
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.
FI1001 RightAlignedPV
SP1001 SP_Real_10_CG
P1010 HorizontalRightPumpGenie
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.
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.
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.
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
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:
Privilege <blank>
Allow RPC False
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.
ii. From within the Vijeo Citect Project Editor, select the menu Tags »
Variable Tags.
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).
3 Create a User.
i. Select the menu System » Users.
ii. Create a new user as follows:
Password CT
Roles Operator
iii. Click the Add button to save the new user and then close the dialog
box.
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.
Note:
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).
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.
In either case, the Assignment Viewer is closed after the right-click is executed and
the Container view is opened.
Note:
vii. The Pages Container view will be displayed, indicating all the items
used in the page on which the VerticalLeftMotorGenie is placed.
A Control object
An unassigned Genie
Components of the Water and Discharge Containers
Any other items of interest.
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.
A simple Refinement saw the editing of the Operator role and the addition of a new
User.
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.
Expected In this chapter, the construction of the Supervision environment will be completed.
Outcome
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.
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.
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.
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 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.
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).
ii. For the item Alarm_1_P, click under the heading Engine.
iii. Select the SupervisionServer entry.
Alarm_1_P SupervisionServer
IOServer_1 SupervisionServer
OperationClient OperationStation
Report_1_P SupervisionServer
Trend_1_P SupervisionServer
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.
The Controller identifies the specific PAC which will exist at the opposite end of
the connection.
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.
The Impact of The Network Diagram previously introduced makes this clear.
TCP/IP Subnets
(cont.)
In this exercise, the previously created IO Device will be connected to the M580
CPU.
ii. Click in the field below Controller in the IODevice_1 drop-down and
select the M580_ePAC item.
iii. Set the Communication Module field to refer to the M580 CPU
module.
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.
Note:
The CTZ files will only be created if the Build completed successfully.
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)."
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.
By the completion of the next section, the Eng Supervision executable will have
been defined.
Relationship A second Executable will be created in parallel with the Tank1 Ops Executable.
between
Executables and
the Supervision
Project
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.).
Identifier Eng
Note:
Note:
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.
What is an executable?
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.
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.
Expected This Executable may then be deployed to the Unity Pro Simulator...
Outcome (cont.)
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.
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.
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.
IP Address 127.0.0.1
Note:
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."
This exercise will demonstrate that a single Control project may be mapped to
multiple hardware configurations.
Identifier Sim
Description Tank 1 Executable for Simulation
Execution Domain Simulation
v. Right-click the Sim item and select Map Service to Map to the
Sim_Server.
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.
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.
iv. Two outcomes will result. Firstly, the Simulator will display the
connection to the computer running the Control project.
vi. Leave the Simulator and Control Participant running in readiness for
a later step.
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.
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.
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.
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.
Observe that at no point was a PAC defined; neither was a Supervision Project.
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.
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.
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:
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.
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.
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).
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:
iii. A dialog box will open inviting the user to download all components
of the Supervision project.
Note:
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.
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.
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.
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.
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.
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).
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.
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.
Note:
It may be necessary to press the F2 key to see the expanded version of the dialog.
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:
v. Click Next.
vi. On the Startup Functions screen, use the Modify button to ensure
the Client is configured to run InitEvents.
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.
5 Run OFS.
ii. On the Login Form, use the credentials created in Exercise - Refine
the Supervision Project (page 9-38).
Name CT_operator
Password CT
Once done, the name of the logged in user will appear beside the
'little man' icon.
Popup Page The various features provided in the genie-linked popup pages (Faceplates) will be
Features extensively discussed in Supervision Standards (page 19-58).
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.
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.
In the image below, observe the value 55 on the PV pin to the upper
right.
Setpoint and The object's setpoint is managed via the interplay of three factors.
Owner
Functionality
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.
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.
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…)
Motor Control
(cont.)
When the feedback signal fails, an alarm is set (blinking Red/yellow bell)
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.
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:
The LP position:
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.
Only the first Interlock can be configured directly from the PES editors.
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.
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.
<need an image>
<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.
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.
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.
Observe that in the instance shown above, the Alarms had occurred
in the Agitation and Discharge sections.
2 Manage Alarms.
i. Right-click an Alarm and select Information.
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.
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.
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.
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.
2 Sort Alarms.
i. Select any column of the Alarm display and click on it three times
slowly in succession.
System Log The Sequence of Events log maintains an uneditable record of all actions that
occur on the running System.
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.
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.
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.
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.
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.
When the Supervision Simulation project was downloaded, why was there no
need to download the Include library? What about the XML?
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.
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.
The Operation Client runs on the Supervision Client computer and is accessed via
any genie object included via PlantStruxure PES.
Expected In addition, support for in-project documentation is provided via the same
Outcome (cont.) interface.
The Operation When defining Station Nodes (in Station Nodes (page 8-3)), there existed the
Client possibility of defining:
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.
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:
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.
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.
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.
iii. Confirm that all data elements on the Graphics Page are showing
valid information.
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. 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.
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.
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.
ii. This will open a new tab to display the Topological objects of the
Sim_Server. Expand the sub-item structure.
Note:
Only objects belonging to the same Execution Domain (page 7-4) (here,
'Simulation') may be traversed from within a single Cross References popup.
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.
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.
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
WARNING
MALICIOUS WEB SITES
Web links to external sites may expose the computer to malicious software.
Failure to follow these instructions can result in death, serious injury, or
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 :
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>
iii. Select the Sharing tab and click the Advanced Sharing button.
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.
S1CTT1A_AG1002
S1CTT1A_LSH1002
S1CTT1A_LSL1002
S1CTT1A_TI1002
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.
<Catalog>
<FileConfiguration url="Process Expert Navigation Services
User Guide.pdf"
name="Navigation Services"
description="Navigation Services User PDF"
arg="/A page=27"/>
</Catalog>
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).
Note:
Special contents in the Operation Client popup are only refreshed when the
Operations Client is started. The Vijeo Citect project may keep running.
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.
Summary of In this chapter, access was given to the Operation Client via the green rectangle
Activities displayed on any PlantStruxure PES-provided genie:
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.