View
50
Download
4
Category
Tags:
Preview:
DESCRIPTION
FSA2-11 Designing and Architecting for Tomorrow. John Krajewski Functional Manager - Infrastructure Invensys - Wonderware. Agenda. Introduction Co-Existence Options High Level Analysis of Differences Detailed Analysis of Differences Recommendations for Today Migration Strategies. - PowerPoint PPT Presentation
Citation preview
FSA2-11 Designing and Architecting for Tomorrow
John KrajewskiFunctional Manager -
InfrastructureInvensys - Wonderware
2
Agenda
► Introduction► Co-Existence Options► High Level Analysis of Differences► Detailed Analysis of Differences► Recommendations for Today► Migration Strategies
3
Evolution of Wonderware
FactorySuite 2000 ►Functionally Rich ► Common Communications (SuiteLink) ►New Functionality (DT Analyst, QI Analyst, AF)
FactorySuite 1000 ►Introduces the Integrated Suite Concept ► Introduces IndustrialSQL Server Historian ►Introduces InControl PC-Based Control EnginePre - FactorySuite
►Best of Breed Products and Acknowledged Leader in Ease-of-Use ► Rapid Rise to Dominance in HMI Market ►Largest Breadth of I/O and Plant Floor Connectivity
FactorySuite A2
► Industrial Application Server► Plant Model► Centralized Administration► Object Based Paradigm► DA Servers► Multi-Developer IDE► Advanced System Diagnostics
Evolv
ing F
unctio
nality
to N
ew Arc
hitect
ure
Evolv
ing F
unctio
nality
to N
ew Arc
hitect
ure
FactorySuite1000
FactorySuite A2
FactorySuite2000
4
Concept Behind FactorySuite A2
Every System In Your Plant, Working In ConcertEvery System In Your Plant, Working In Concert
•A Unified Plant application Model
•Integration is More than Communication
Batc
hin
g
Fillin
g
Lab
elin
g
Palleti
zin
g
Bott
lin
g
Inven
sys
Hon
eyw
ell
Sie
men
s
Em
ers
on
AB
B
•Unifying Today’s “Islands of Automation”
•Empowering all Workers in a plant
The ArchestrA Vision
5
What are you trying to address?
FactorySuite2000
FactorySuite A2
Existing Units New Units
WorkstationWorkstation Workstation
Must Work Together
6
New Workstation Detail
Workstation
► If using InTouch 8.0 as the link to field devices there is no change from how applications are migrated.
► The rest of this presentation assumes that Industrial Application Server is being applied on the new workstation.
7
Agenda
► Introduction► Co-Existence Options► High Level Analysis of Differences► Detailed Analysis of Differences► Recommendations for Today► Migration Strategies
8
► New workstation co-exists with existing workstations. Existing workstation applications remain
unchanged. Existing Workstations continue to run the
same version of software.
Co-Existence #1
Existing WorkstationExisting Workstation New Workstation
Existing Units New Units
9
Existing WorkstationExisting Workstation New Workstation
Co-Existence #1
SuiteLink SuiteLink
FactorySuite 2000 Version SuiteLinkInTouch Version 7.11 or higher
10
► New workstation co-exists with existing workstations. Existing InTouch applications are converted
to version 8 (single button push). Industrial Application Server Platforms are
deployed to the Existing Workstations.
Co-Existence #2Existing WorkstationExisting Workstation New Workstation
11
Galaxy Repositor
y
Existing WorkstationExisting Workstation New Workstation
Co-Existence #2
Mx Mx
12
Agenda
► Introduction► Co-Existence Options► High Level Analysis of Differences► Detailed Analysis of Differences► Recommendations for Today► Migration Strategies
13
Current Architectures
► We will analyze common architectures that are applied today and then look at how these applications will be applied utilizing Industrial Application Server and FactorySuite A2. Single Node Peer to Peer Client Server
14
InTouch Workstation
Common Tags
Supervisory Scripts IO Server
Windows
Visualization Tags
Visualization Scripts
Single Node
What are the components that make up a single node?
Separate Applications
Mostly IO Tags
Memory Tags
15
FactorySuite A2 Single Node
InTouch Only Workstation
Common Tags
Supervisory Scripts IO Server
Windows
Visualization Tags
Visualization Scripts
InTouch and AppServer
AppEngine
Windows
Visualization Tags
Visualization Scripts Platform
DI Objects
ApplicationObjects
InTouch remains unchanged.
Common Tags and Supervisory Scripts replaced
by ApplicationObjects
16
Peer to Peer
Multiple workstations duplicate functionality.
InTouch Workstation
Common Tags
Supervisory Scripts IO Server
Windows
Visualization Tags
Visualization Scripts
InTouch Workstation
Common Tags
Supervisory Scripts IO Server
Windows
Visualization Tags
Visualization Scripts
17
InTouch and AppServer
Windows
Visualization Tags
Visualization Scripts
InTouch and AppServer
Windows
Visualization Tags
Visualization Scripts
AppEngine
DI Objects
ApplicationObjects
FactorySuite A2 Peer to Peer
Supervisory Control functionality is not duplicated.
AppEngine
New DI Objects
New AppObjects
PlatformPlatform
18
Tag Server
This is a recommended existing architecture.
Target Architecture?
InTouch Client
Tag Server
InTouch Client InTouch Client
Common Tags
Supervisory Scripts IO Server
Windows
Visualization Tags
Visualization Scripts
Windows
Visualization Tags
Visualization Scripts
Windows
Visualization Tags
Visualization Scripts
19
AppServer
AppEngine
Platform
FactorySuite A2 Client Server
New ApplicationObjectsNew DI Objects
InTouch Client
Windows
Visualization Tags
Visualization Scripts
Platform
InTouch Client
Windows
Visualization Tags
Visualization Scripts
Platform
InTouch Client
Windows
Visualization Tags
Visualization Scripts
Platform
AppServer
ApplicationObjects
DI Objects
AppEngine
Platform
20
Agenda
► Introduction► Co-Existence Options► High Level Analysis of Differences► Detailed Analysis of Differences► Recommendations for Today► Migration Strategies
21
MigrationExisting Units New Units
WorkstationWorkstation Workstation
PreviouslyIndustrial Application Server
Galaxy RepositoryThe rest of this presentation deals with
how to plan for this in current projects and what the migration process will be.
22
Tags versus ApplicationObjects
► What are the key differences?
Tags
Scripts
History
23
What is an ApplicationObject?
Logic/Scripting
Alarms/EventsInputs/Outputs
History Scheme
Security
Valve Application Object
Objects Contain All Configuration Elements
24
How are these objects used?
$Valve
This Object is a Template for Other
Objects
CV101
CV201
CV301
CV401
The $Valve Template can be used to create several instances of the device.
•Changes to Template Automatically Propagate to Instances
•New Templates can be Derived from Existing Templates
•Libraries of Standard Objects can be Developed
•Standard Templates Decrease Project-to-Project Costs
25
Industrial Application Server Naming
CV403
.Cmd.Qualit
yTagnam
e:
26
Hierarchical Naming
Tagname
Contained Name
TK400.Waste
.Cmd.Qualit
y
Hierarchical Name:
27
Agenda
► Introduction► Co-Existence Options► High Level Analysis of Differences► Detailed Analysis of Differences► Recommendations for Today► Migration Strategies
28
Building Today
► When building and maintaining your applications today there are practices which will facilitate the migration process.
► These practices are recommend for all InTouch applications regardless of their intent of migration.
29
Tagname Dictionary
► Structure, Structure, Structure…► Strict adherence to a naming
convention that is hierarchical.
Device
Type
Unique
Identifier
Attribute
Identifier
Area
Bldg32_
Sub-Area
Intake_FCV1834OLS
Example:
This convention is an example you are free to implement one that suits your purpose best.
Critical Information
30
Scripting
► Q: What is the script Language used in Industrial Application Server?
► A: QuickScript.NET. Same syntax as InTouch All relevant script functions supported Compiles to .NET Common Language
Runtime (CLR)
31
Scripting
► When migrating scripts, thought should be put into determining what script functionality has been (or can be) replaced by the infrastructure.
► Is re-use of the whole script practical?
IF $AccessLevel > 9000
THEN
StartSequence = 1;
ENDIF;
Security is now implemented at the
data level.
32
Scripting your Application
► Make use of Quick Functions for repeated script tasks.
► Segment script functionality into different scripts. Security Graphic Scripting Device Control System Error Detection
► Use condition scripts and data change scripts to perform this.
33
Windows/Graphics Scripting
► Keep these limited to graphic actions and simple command operations.
► Move conditional checks or cascade operations into data change or condition scripts.
34
Agenda
► Introduction► Co-Existence Options► High Level Analysis of Differences► Detailed Analysis of Differences► Recommendations for Today► Migration Strategies
35
Migration Tasks
► Create Templates Manually Defined
► Create Instances Option 1: Preserve Tag Data Option 2: Build into Templates
► Update InTouch Application Option 1: Replace All Links Option 2: Redirect Tags Delete Obsolete functionality.
36
Create Instances – Option 1
Map Tags to instances
CV101
CV101OLS
CV101CLS
CV101ALM
CV101OUT
InTouch Industrial Application Server
Best Option if:
Varying Alarm Thresholds
OR
Custom Scaling Per Tag
OR
IO Addresses Follow No Rule
37
Create Instances – Option 2
► Build Scaling Definitions Into Template
► Build Alarm Limits into Template► Build IO Addresses Into Template
References can be written through scripts.
If IO addresses have a mathematic relationship to their names or other criteria they can be set dynamically.
► Easier than Option 1
Best Option if:
Common Alarm Thresholds
OR
Common Scaling by Device
OR
IO Addresses Follow Rules
Many applications are likely to use parts from Option 1 and parts from
Option 2.
38
Update InTouch: Replace All Links
► Replace tag references with remote references: Galaxy:ObjectName.Attribute
► Edit All Windows and Scripts OR► Use InTouch Search and Replace
Functionality Available later this year.
► Delete Unused Tags
39
Update InTouch: Redirect Tags
► InTouch 8.0 has an Access Name called “Galaxy” built in.
► IO Tags can use this Access Name DBDump DBLoad.
► Items for these tags will be the object reference. Tagname Hierarchical name
► Remove scaling, alarm, and history definitions.► Little to no script and window editing required.
40
Questions?
Wonderware is committed to protecting your investment, preserving your engineering effort, and simplifying your
implementation of new technologies.
Recommended