Beruflich Dokumente
Kultur Dokumente
Part 1
Wonderware Training
8:30 AM
10:00 AM
At the lobby
1:00 PM
On every computer
3:00 PM
In the kitchen
4:30 PM
6:00 PM
Day 3
Day 2
Day 1
Contents
Module 1:
Introduction
Module 2:
Application
Infrastructure
Module 3:
Application Objects
Module 4:
Module 5:
Module 6:
Security
Module 7:
Galaxy Maintenance
Module 8:
Device Integration
Products
Module 9:
Multi-Node Applications
Contents
Section 1:
Course Introduction
Section 2:
Wonderware System
Platform
Lab 1
Creating a Galaxy
Section 3:
Section 4:
Automation Objects
Section 5:
System Requirements,
Licensing and Support
Section 6:
Lab 2
Application Planning
Identifying the Mixer
Course Description
The System Platform
Part 1 training course
is a 4-day instructorled course designed
to give the knowledge
necessary to develop
and support
applications with
Wonderware
Application Server.
Course Objectives
Create new projects
using ArchestrA
Integrated
Development
Environment
Model the plant floor
using automation
objects
Work with the alarm
and history
configuration in the
Galaxy
Configure ArchestrA
security in the Galaxy
Clients
Analysis Client
(ActiveFactory)
InTouch View
Reporting Client
(SuiteVoyager CAL)
Historian
(InSQL)
Information Server
(SuiteVoyager)
Device Integration
3rd Party
Data Sources
S/W
Applications
3rd Party
Controllers
IAS 2.0/2.1
ArchestrA
Galaxies
2000+
2000+
Supervisory
Execution
Engine
Time Propagation
Scan On Demand
Failover support
SCADA Support
Internationalization
Objects
Single Node
1000+
1000+
IAS 1.0
Scalability
Performance
Robustness
430+
430+
IAS 1.5
Application
Server 3.0
Application
Server 3.x
10,000+
Platfor
ms
Installe
d
Already
Application Server
Galaxy
Application Servers application, configuration
information and project database.
Galaxy Repository
Galaxy
Platform
Engine
Container App
Objects
App Objects
Attribu
tes
Wonderware Application
Server
Highlights
Intake
Production
Line 1
Line 2
Discharge
Self documenting
Advanced system maintenance and diagnostics
Oper.
Oper. Interface
Interface
Oper.
Oper. Interface
Interface Tags
Tags Process
Process Data
Data
Scripts
Scripts
Appl.
Appl.
History
History
Windows
Animation
Remote
Navigation Scripts
Trends/Alarms, etc.
Security
Tag names
Scaling
History Configuration
Engineering Units
Event Configuration
Alarm Configuration
Access Name Link
I/O Item names
Application Scripts
Data Change Scripts
Condition Scripts
Window Scripts
SQL Access, Files, etc.
Other Supervisory Logic
Alarm Groups
Access Names
Security & Users
Process Data History
Alarm History
Event History
Windows
Animation
Navigation Scripts
Trends/Alarms, etc.
Security
Windows
Animation
Navigation Scripts
Trends/Alarms, etc.
Security
Traditional HMI
Introduction of Remote
references
Tag server + Clients
references
IAS Solution:
CV101
OLS
Cmd
Encapsulation in objects
Derivation from
templates
LS_Alarm
Timeout_Alarm
PV
CLS
$Valve
CV102
OLS
Cmd
LS_Alarm
Timeout_Alarm
PV
CLS
OLS
Cmd
LS_Alarm
Timeout_Alarm
Represented by objects
Oper.
Oper. Interf.
Interf.
History
History
Oper.
Oper. Interf.
Interf.
Oper.
Oper. Interf.
Interf.
Windows
Animation
Navigation Scripts
Trends/Alarms, etc.
Windows
Animation
Navigation Scripts
Trends/Alarms, etc.
CV101
IAS Solution:
CV102
CV103
Encapsulation in objects
Derivation from
templates
History
History
Windows
Animation
Navigation Scripts
Trends/Alarms, etc.
Oper.
Oper. Interf.
Interf.
Oper.
Oper. Interf.
Interf.
Oper.
Oper. Interf.
Interf.
Windows
Animation
Navigation Scripts
Trends/Alarms, etc.
Windows
Animation
Navigation Scripts
Trends/Alarms, etc.
CV101
CV103
CV102
IAS Solution:
Encapsulation in objects
Derivation from
templates
One global name space
Object Oriented
Tag Based
Structure
Hierarchical
Flat
Graphics Development
Done Last
Done Early
Background Process
Development in Objects
Developed in Tags
Promotion of Standards
Strictly Enforced
Global Application
Change
Data Represented by
Physical Devices as
Objects
Scalability
Large System
Small System
Application Object
Server Only
Integrated
Single Node
Distributed
Peer to Peer
Single Server
Multi Client
Enhanced Communications
Intercommunications is no longer performed by either NetDDE or
SuiteLink.
New Communications Protocol LMX/NMX (Local/Network Message
Exchange):
Guaranteed Order of Delivery
Enhanced Diagnostics
Automation Objects
Graphics
Logic / Scripting
History Scheme
Documentation
Security
Automation Objects
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
CV101
CV101
ArchestrA Topology
Visualization Node
ArchestrA
Runtime
ArchestrA
Runtime
Galaxy
Repository
Historian
Information
Server
Workstation
ArchestrA Topology
Visualization Node
InTouch
InTouch
IDE
IDE
Platform
Platform
Platform
Platform
Bootstrap
Bootstrap
Bootstrap
Bootstrap
Galaxy Rep.
Historian
Workstation
Info Server
Platform
Platform
Platform
Platform
Bootstrap
Bootstrap
Bootstrap
Bootstrap
ArchestrA
Runtime
ArchestrA
Runtime
Galaxy
Repository
IO Server
Platform
Bootstrap
I/O Data Server
Historian
Information
Server
ArchestrA Topology
Visualization Node
InTouch
InTouch
IDE
IDE
Platform
Platform
Platform
Platform
Bootstrap
Bootstrap
Bootstrap
Bootstrap
Galaxy Rep.
Historian
Workstation
Info Server
Platform
Platform
Platform
Platform
Bootstrap
Bootstrap
Bootstrap
Bootstrap
ArchestrA
Runtime
ArchestrA
Runtime
Galaxy
Repository
Historian
IO Server
Platform
Bootstrap
I/O Data Server
Information
Server
System Requirements
Software
ArchestrA
IDE
ArchestrA
Runtime
Galaxy
Repository
Windows Vista
Business
Enterprise
Ultimate
Windows XP
Professional SP2
Tablet 2005
(Professional)
System Requirements
Hardware
Galaxy Repository
Minimum
Recommended
CPU
Single-Core 3 GHz
Dual-Core 2 GHz
RAM
1 Gb
2Gb
Single-Core 2 GHz
RAM
1 Gb
All Systems
Minimum
Hard Drive
30 Gb available
Display
SVGA (1024x768)
Optical
Drive
CD-ROM
Galaxy
IO Count
Platform Count
Number of PCs in the Galaxy that will be part of the
single namespace.
IDE
Integrated Development Environment for configuring
the Galaxy
Licensing
WW System Platform
IO
Count
Histo
ry
Platfor
ms
IO
Count
Histor
y
Platfor
ms
250
250
50,000
25,000
250
1,000
50,000
50,000
1,000
1,000
50,000
100,000
1,000
5,000
100,000
25,000
5,000
1,000
100,000
50,000
5,000
5,000
100,000
100,000
5,000
12,000
200,000
25,000
5,000
25,000
200,000
50,000
25,000
5,000
200,000
100,000
25,000
12,000
500,000
50,000
25,000
25,000
500,000
100,000
25,000
50,000
1,000,000
50,000
50,000
12,000
1,000,000
100,000
Licensing
WW Development Studio
Galaxy IO - Can Connect to a
Galaxy of this Size
InTouch Tags
History Tags
(24Hr data retrieval)
Unlimited
Any Size
60,000
500
Large
5,000
3,000
500
Medium
1,000
1,000
100
Small
250
500
100
Limited**
NA
64
NA
** Limited Includes InTouch Dev/RT (IDE) and Device Integration only; does not include AF, WIS, or
Historian Server. Just like the 64 Tag InTouch Development Today.
Unlimited includes ActiveFactory.
LAB 1
Creating a Galaxy
Plan Templates
LAB 2
Identifying the Mixer
LAB 2
Identifying the Mixer
Heat Exchanger
Mixer System
LAB 2
Identifying the Mixer
LAB 2
Identifying the Mixer
Contents
Section 1:
Lab 3
Creating the Plant
Model
Section 2:
Lab 4
Creating and
Deploying the Deployment
Model
Section 3:
The Runtime
Environment
Lab 5
Section 4:
Lab 6
Connecting to the
Field
Section
Section
Area
Production Line
Manufacturing Cell
Production Line
Area
Manufacturing
Production
Cell
Line
Manufacturin
LAB 3
Creating the Plant Model
Plant
Line1
Line2
ControlSystem
Discharge
Discharge
Intake
Intake
Production
AppEngine
Area
Area
Area
Area
DI Object
DI Object
DI Object
DI Object
Bootstrap
LAB 5
Using Object Viewer
Device
Driver
Field Device
LAB 6
Connecting to the Field
Galaxy
Device
Driver
Field Device
InControl
Contents
Section 1:
Section 2:
Lab 7
Heat Exchanger
Section 3:
Change Control and
Propagation
Lab 8
Change Control and
Propagation
Section 4:
The $AnalogDevice
Object
Lab 9
Meter
Section 5:
The $DiscreteDevice
Object
Lab 10
Valve, Pump and
Motor
Templates
Base Template
Derived Template
Read-Only configuration
Writeable configuration
Template
$CV101
$Inlet
$CV102
$DiscreteDevice
$Valve
$CV103
$Outlet
$CV104
LAB 7
Heat Exchanger
$Valve
$CV103
$Outlet
$CV104
Unlocked
Locked
Locked In Parent
LAB 9
Meter
$Meter
LAB 10
Valve, Pump and Motor
$Meter
$Valve
$Pump
$Motor
Containment
Containment
Allows more advanced structures to be modeled as a single
object.
Container and contained objects are still accessible as
individual objects.
Relationship can be build at the template or instance level.
$Tank
$Agitator
Agitator
$LevelMeter
Level Meter
$InletValve
Inlet Valve
$OutletValve
Outlet Valve
LAB 11
Mixer
$Meter
$Valve
$Pump
$Motor
$Mixer
Contents
Section 1:
UDAs
Section 2:
Extensions
Lab 12
Motor Speed
Section 3:
Introduction to
QuickScripts .NET
Lab 13
DDESuiteLinkClient
Auto Reconnect
Lab 14
Automatic Reference
Configuration
UDA Categories
Same
Object
Calculated
Calculated Retentive
Object Writeable
User Writeable
Other
Objects
External
Users
Extensions
LAB 12
Motor Speed
Relative References
Me
MyContainer
MyArea
MyEngine
MyPlatform
MyHost
Executing an Object
Inputs
Scripts
Behavior
Scripts
Outputs
Attributes
Scheduler 2.1
Read Inputs /
Idle
Execute App
Objects
Send changes to
other engines
Scheduler 3.0
Read Inputs /
Idle
Execute App
Objects
Read/Write
interrupts
Read/Write
interrupts
Send changes to
other engines
DDESuiteLinkClient Auto
Reconnect
Automatic Reference
Configuration
Contents
Section 1:
Lab 15
Section 2:
Lab 16
Alarms
Configuring Alarms
Historization
Configuring History
Alarms
Alarm Engine
Alarms are generate by the
objects.
Alarm providers make the
alarms available to external
alarm subscribers.
Available alarm subscribers
allows:
Visualization and
acknowledge of alarms
Logged alarms into a
SQL Server database
Alarms
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
WinPlatform
PROV
PROV
AppEngine
Alarm DB Logger
Alarms
\\BlueNode\Galaxy!Plant
Plant
\\RedNode\Galaxy!Plant
Intake
Discharge
Production
Line1
Line2
BlueNode
RedNode
Line1
Line2
Intake
Discharge
Production
Line1 Line2
LAB 15
Configuring Alarms
Historization
History Engine
CLIENT
CLIENT
Area
AppEngine
WinPlatform
Historian
Historization
InSQL
MDAS
Application
Server
IDAS
InTouch
IOS
LAB 16
Configuring History
Contents
Section 1:
Lab 17
Security Overview
Security
Security
Development
Security
Develoment
Testing
Troubleshooting
Environment
GENERAL
PERMISSIONS
Runtime Security
Security
ASSIGNED TO
Classifications ATTRIBUTES
Security Groups
OPERATIONAL
PERMISSIONS
Roles
BELONGS TO
ONE OR MORE
Users
LAB 17
Security
Contents
Section 1:
Exporting and Importing
Objects
Section 2:
Configuring Instances
Through a CSV File
Section 3:
System Management
Console (SMC)
Section 4:
Contents
Section 1:
I/O Servers
Section 2:
Section 3:
Device Integration
Objects
ArchestrA
Runtime
DDE
SuiteLink
DDE
SuiteLink
OPC
IO Server
DAS
DA Server
Engine
PLC Protocol
PLC Protocol
NIC
PLC_1
PLC_2
DHP
SLC_A
SLC_B
CNET
PLC5_A
PLC5_B
Contents
Section 1:
Application Redundancy
Lab 18
Configuring
Application Redundancy
Section 2:
DI Redundancy
Lab 19
Configuring the
Redundant DI Object
Section 3:
Multi-Node Application
Lab 20
Convert to Network
Environment
Application Redundancy
Non-Redundant System
The server handles all
the data.
If server if lost, client
lose connection to all
data:
InTouch
Historian
Other Application
Object Servers
Redundant System
Redundant server
maintain synchronized
data through dedicated
network.
If the primary server is
lost, the backup server
will take over.
The switch between the
servers is transparent to
the clients.
Client/Server Architecture
ArchestrA
Runtime
Application Redundancy
Characteristics
Currently supported only
in pairs
ArchestrA
Second network
connection (RMC)
necessary
Configuration
Terminology:
Primary AppEngine
Backup AppEngine
Runtime Terminology
Active AppEngine
Standby AppEngine
Active AppEngine refer to
Standby AppEngine as
Partner.
RMC
AppEngine1
AppEngine1
(Backup)
Platform1
Platform2
Primary
Backup
Standby
Active
Standby
Active
1.Current data
(Checkpoint)
ArchestrA
RMC
Active
Standby
Supported Configuration
Characteristics
Peer to peer architecture
ArchestrA
AppEngine1
RMC
AppEngine2
AppEngine2
(Backup)
AppEngine1
(Backup)
Platform1
Platform2
Redundancy Configuration
Windows Networking
nd network card.
1. Install 2nd
Configuring Application
Redundancy
DI Redundancy
Field Device Connectivity
ArchestrA
Runtime
The Redundant DI
Object allows
communications
through a Standby
network if the Active
is lost.
The Redundant DI
Object allows
Applications Objects
to subscribe to a
single object that in
turn can retrieve data
from either a Primary
or Backup DI object.
CIP
DH+
DI Redundancy
Application
Objects
RDIO
DIO_1
AppEngine1
DIO_2
Platform1
CIP
Control Networks
DH+
Configuring Redundant DI
Object
Convert to Network
Environment
Galaxy Master
Remote Node
Remote Node
Remote Node
ArchestrA IDE
ArchestrA IDE
ArchestrA IDE
ArchestrA IDE
AppEngine
AppEngine
AppEngine
AppEngine
Platform
Platform
Platform
Platform
MyTemplates.aaPKG
MyTemplates.aaPKG
MyTemplates.aaPKG
MyTemplates.aaPKG
InControl.aaPKG
1.
2.
3.
4.
5.
6.
Convert to Network
Environment
Galaxy Master
Remote Node
Remote Node
Remote Node
ArchestrA IDE
ArchestrA IDE
ArchestrA IDE
ArchestrA IDE
AE
AEDI
Platform
AE
AE
AE
Platform
Platform
Platform