FSA2-11 Designing and Architecting for Tomorrow

1
FSA2-11 Designing and Architecting for Tomorrow

• John Krajewski
• Functional Manager - Infrastructure
• Invensys - 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
Evolving Functionality to New Architecture
4
Concept Behind FactorySuite A2
The ArchestrA Vision

• Empowering all Workers in a plant

• A Unified Plant application Model

• Integration is More than Communication

• Unifying Todays Islands of Automation

Palletizing
Invensys
Bottling
Honeywell
Siemens
Labeling
Emerson
Filling
Batching
ABB
Every System In Your Plant, Working In Concert
5
What are you trying to address?
6
New Workstation Detail

• 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
Co-Existence 1

• New workstation co-exists with existing
  workstations.
• Existing workstation applications remain
  unchanged.
• Existing Workstations continue to run the same
  version of software.

9
Co-Existence 1
SuiteLink
SuiteLink
FactorySuite 2000 Version SuiteLink
InTouch Version 7.11 or higher
10
Co-Existence 2

• 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.

11
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
Single Node
What are the components that make up a single
node?
15
FactorySuite A2 Single Node
InTouch remains unchanged.
16
Peer to Peer
Multiple workstations duplicate functionality.
17
FactorySuite A2 Peer to Peer
Supervisory Control functionality is not
duplicated.
Platform
Platform
18
Tag Server
This is a recommended existing architecture.
19
FactorySuite A2 Client Server
New DI Objects
New ApplicationObjects
20
Agenda

• Introduction
• Co-Existence Options
• High Level Analysis of Differences
• Detailed Analysis of Differences
• Recommendations for Today
• Migration Strategies

21
Migration

• The rest of this presentation deals with how to
  plan for this in current projects and what the
  migration process will be.

Galaxy Repository
Previously
Industrial Application Server
22
Tags versus ApplicationObjects

• What are the key differences?

23
What is an ApplicationObject?
Objects Contain All Configuration Elements
Valve Application Object
24
How are these objects used?
The Valve Template can be used to create several
instances of the device.
CV101
This Object is a Template for Other Objects
CV201

• 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

CV301
Valve
CV401
25
Industrial Application Server Naming
Tagname
CV403
.Cmd
.Quality
26
Hierarchical Naming
Hierarchical Name
TK400.Waste
.Cmd
.Quality
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.

Example
FCV
1834
OLS
Attribute Identifier
Device Type
Unique Identifier
This convention is an example you are free to
implement one that suits your purpose best.
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 gt 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
Best Option if Varying Alarm Thresholds OR Custom
Scaling Per Tag OR IO Addresses Follow No Rule
CV101OLS CV101CLS CV101ALM CV101OUT
Map Tags to instances
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
  GalaxyObjectName.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.