Wonderware
System Platform 2017
1 Day Workshop
Presented by Gigih
1 © 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
Announcement
As 1 March 2018, where the merger will take effect and we will become one organisation, AVEVA Group
plc.
The teams involved will continue to work on plans to ensure a smooth migration and enable business
continuity following the close of the transaction. Please refer to the various housekeeping emails that have
been sent out should you have questions relating to IT, Marketing, Real Estate, Communications and HR.
We will continue to keep all of you updated as we progress through the various phases of this transaction
and subsequent integration.
© 2018 AVEVA Solutions Limited and its subsidiaries. All rights reserved.
Schedule
9:00 AM
10:15 AM
12:00 PM
1:00 PM
3:00 PM
5:00 PM
Course Description
> Designed to provide a fundamental understanding of the basic principles of
ArchestrA and supply the knowledge necessary to develop and support
applications for Wonderware Application Server 2017.
> The focus of this course is to illustrate the use of ArchestrA tools and services
in the System Platform to develop a project utilizing connectivity to the field,
data processing, scripts, alarms and history, using features and functionality
such as Automation Objects, templates, instances, ArchestrA Integrated
Development Environment and QuickScript .NET.
System Platform 2017
Agenda
▲ Module 1: Introduction
▲ Module 2: Application Planning
▲ Module 3: Application Infrastructure
▲ Module 4: Application Objects
▲ Module 5: Connecting to the Device
▲ Module 6: Alarm and History
▲ Module 7: Graphic
Click icon
to add
picture
1. Introduction
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
System Platform Overview
Topology
Workstations
Visualization Nodes Engineering Stations
IDE IDE
Hist. Client Hist. Client Hist. Client Hist. Client
InTouch InTouch InTouch InTouch
WinPlatform WinPlatform WinPlatform WinPlatform
Bootstrap Bootstrap Bootstrap Bootstrap
Galaxy Historian Information
IO Server DA Server Repository Server Server
WinPlatform* WinPlatform WinPlatform WinPlatform WinPlatform WinPlatform* WinPlatform
Bootstrap Bootstrap Bootstrap Bootstrap Bootstrap Bootstrap Bootstrap
Device Integration Automation Object Galaxy Historian License Information
Servers Servers Repository Server Server Server
Controllers
Topology
Workstations
Visualization Nodes Engineering Stations
IDE IDE
Hist. Client Hist. Client Hist. Client Hist. Client
InTouch InTouch InTouch InTouch
WinPlatform WinPlatform WinPlatform WinPlatform
Bootstrap Bootstrap Bootstrap Bootstrap
Galaxy Historian Information
IO Server DA Server Repository Server Server
WinPlatform* WinPlatform WinPlatform WinPlatform WinPlatform WinPlatform* WinPlatform
Bootstrap Bootstrap Bootstrap Bootstrap Bootstrap Bootstrap Bootstrap
Device Integration Automation Object Galaxy Historian License Information
Servers Servers Repository Server Server Server
Controllers
Lab 1 15 min
Creating a New Galaxy
System Requirement
> For Distributed Configuration
> For all in one (single node) – 1K IO max
Licensing
> Use new licensing mechanism – activated licensing
> License is based on:
▲ Numbers of IO (250, 1K, 5K, 25K, 50K, etc)
▲ Historian Tag Size (1K, 5K, 12K, 25K, etc)
▲ Client license (Supervisory Client, HistorianClient, InSight) must be purchased separately
Automation Objects
Inputs/Outputs Graphic symbols
Logic/Scripting Documentation
Historical Information Alarms and events
Security
Template and Instance
Templates and Instances
• Instances derived from templates and inherit all the configuration
• New templates can be derived from existing templates
• Changes to templates can be propagated to derived objects
• Templates allow the development of a library of standard objects
CV101
$Valve CV102
CV103
Template and Instance
CV101
$Inlet
CV102
$DiscreteDevice $Valve
CV103
$Outlet
CV104
Built In Template
▲ _Default Templates
▲ A standard set of templates, you can derive your
own template from this
▲ My Templates
▲ A custom template of your own, derive a template
from _Default Templates to create it
▲ System
▲ A read only templates that does not intended to
be edited. Use this for reference only. All objects
here have padlock icon, meaning that it cannot
be edited
▲ Notes: Version prior to 2017 DOES NOT have this, you are advised to create your own set of derived template
before starting to design the project!
Click icon
to add
picture
2. Application Planning
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
Factory Layout
Heat Exchanger
Invensys proprietary & confidential
Mixer
Mixer System Details
Click icon
to add
picture
3. Application
Infrastructure
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
Area Modeling
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
The Deployment Model
Object
Object
DI Object
DI Object
Area Area
DI
DI
AppEngine
WinPlatform
Bootstrap
The Deployment Model
Object
Object
Object
Object
DI Object
DI Object
DI Object
DI Object
Area Area Area Area
DI
DI
DI
DI
AppEngine AppEngine
WinPlatform
Bootstrap
Lab 2 15 min
Creating Plant and Deployment Models
Runtime Environment
> To view the runtime value, we can use a tool called Object Viewer.
> ObjectViewer can be launched in 2 ways:
• From ArchestrA IDE, right click on the any instance and select “View in Object
Viewer”
Runtime Environment
• From System Platform Management Console, go to Platform Manager. Expand
into one Platform. Right click on App Engine object on the right pane and select
“Launch Object Viewer”
Lab 3 15 min
Using Object Viewer
Click icon
to add
picture
4. Application Objects
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
Application Objects
> AnalogDevice: represents basic analog
equipment or PID.
> DiscreteDevice: represents discrete
equipment such as valve, pump, etc. Can
have multiple inputs and output
> Sequencer: simple flowchart object
> SQLData: read and write to SQL Server
database
> UserDefined: the most flexible object, can
have any numbers of input and output. Does
not have any internal behaviour
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
Heat Exchanger
▲ This device has 4 temperature
transmitters
▲ TT1 (Product In)
▲ TT2 (Product Out)
▲ TT3 (Service In)
▲ TT4 (Service Out)
▲ We will use UserDefined
object to create this
Lab 4 15 min
Heat Exchanger
Mixer
▲ 3 valves are identical, so we will
create a template for valve
$Valve $Pump ▲ 2 pumps are identical, so we will
create a template for pump
▲ Agitator, Level and Temperature
Transmitter can be embedded
directly into the mixer since they
do not have any duplicate
▲ Notes:
▲ There is no 100% correct and 100%
wrong, any design can have its own
benefit and disadvantage
▲ When you design it efficiently, you
will save a lot of time later
Lab 5 15 min
Mixer
Click icon
to add
picture
5. Connecting To The
Field Device
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
Section 4 – Device Integration Product
Allen Bradley
Allen Bradley’s protocol
App Server
Omron
Omron’s protocol
Siemens
Siemens’s protocol
Connecting to the Field
Device Field Device
Driver
Legacy InTouch Node
Lab 6 15 min
Connect to Device
Click icon
to add
picture
6. Alarm and History
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
Alarms Overview
Alarm Provider
• $WinPlatform object as the InTouch Alarm Provider for the galaxy.
• A single $WinPlatform can provide alarms from the whole galaxy.
• Alarm providers can be limited to provide alarms for specific areas of the galaxy.
Alarm Viewer
Area
AppEngine
PROV
PROV
WinPlatform
Historian
Historian
History Engine
• $AppEngine object as the Historian client for the objects.
• An $AppEngine historize only the objects that it host.
• Native support for Store & Forward.
Area
CLIENT
CLIENT
AppEngine
WinPlatform
Historian
Lab 7 15 min
Alarm and History
Click icon
to add
picture
7. Graphic
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
QUESTIONS?
© 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
This presentation may include predictions, estimates, intentions, beliefs and other
statements that are or may be construed as being forward-looking. While these forward-
looking statements represent our current judgment on what the future holds, they are
subject to risks and uncertainties that could result in actual outcomes differing materially
from those projected in these statements. No statement contained herein constitutes a
commitment by AVEVA to perform any particular action or to deliver any particular product
or product features. Readers are cautioned not to place undue reliance on these forward-
looking statements, which reflect our opinions only as of the date of this presentation.
The Company shall not be obliged to disclose any revision to these forward-looking
statements to reflect events or circumstances occurring after the date on which they are
made or to reflect the occurrence of future events.
46 © 2018 AVEVA Group plc and its subsidiaries. All rights reserved.
