1. FSA2-11 Designing and Architecting for Tomorrow John Krajewski Functional Manager - Infrastructure Invensys - Wonderware

2. 1 Agenda ► Introduction ► Co-Existence Options ► High Level Analysis of Differences ► Detailed Analysis of Differences ► Recommendations for Today ► Migration Strategies

3. 2 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 Engine Pre - 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 A 2 ► Industrial Application Server ► Plant Model ► Centralized Administration ► Object Based Paradigm ► DA Servers ► Multi-Developer IDE ► Advanced System Diagnostics Evolving Functionality to New Architecture FactorySuite 1000 FactorySuite A 2 FactorySuite 2000

4. 3 Concept Behind FactorySuite A 2 Every System In Your Plant, Working In Concert A Unified Plant application Model Integration is More than Communication Batching Filling Labeling Palletizing Bottling Invensys Honeywell Siemens Emerson ABB Unifying Today’s “Islands of Automation” Empowering all Workers in a plant The ArchestrA Vision

5. 4 What are you trying to address? FactorySuite 2000 FactorySuite A 2 Existing UnitsNew Units Workstation Must Work Together

6. 5 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. 6 Agenda ► Introduction ► Co-Existence Options ► High Level Analysis of Differences ► Detailed Analysis of Differences ► Recommendations for Today ► Migration Strategies

8. 7 ► 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 Workstation New Workstation Existing UnitsNew Units

9. 8 Existing Workstation New Workstation Co-Existence #1 SuiteLink FactorySuite 2000 Version SuiteLink InTouch Version 7.11 or higher

10. 9 ► 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 #2 Existing Workstation New Workstation

11. 10 Galaxy Repository Existing Workstation New Workstation Co-Existence #2 Mx

12. 11 Agenda ► Introduction ► Co-Existence Options ► High Level Analysis of Differences ► Detailed Analysis of Differences ► Recommendations for Today ► Migration Strategies

13. 12 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 A 2.  Single Node  Peer to Peer  Client Server

14. 13 InTouch Workstation Common Tags Supervisory ScriptsIO 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. 14 FactorySuite A 2 Single Node InTouch Only Workstation Common Tags Supervisory ScriptsIO Server Windows Visualization Tags Visualization Scripts InTouch and AppServer AppEngine Windows Visualization Tags Visualization ScriptsPlatform DI Objects ApplicationObjects InTouch remains unchanged. Common Tags and Supervisory Scripts replaced by ApplicationObjects

16. 15 Peer to Peer Multiple workstations duplicate functionality. InTouch Workstation Common Tags Supervisory ScriptsIO Server Windows Visualization Tags Visualization Scripts InTouch Workstation Common Tags Supervisory ScriptsIO Server Windows Visualization Tags Visualization Scripts

17. 16 InTouch and AppServer Windows Visualization Tags Visualization Scripts InTouch and AppServer Windows Visualization Tags Visualization Scripts AppEngine DI Objects ApplicationObjects FactorySuite A 2 Peer to Peer Supervisory Control functionality is not duplicated. AppEngine New DI Objects New AppObjects Platform

18. 17 Tag Server This is a recommended existing architecture. Target Architecture? InTouch Client Tag Server InTouch Client Common Tags Supervisory ScriptsIO Server Windows Visualization Tags Visualization Scripts Windows Visualization Tags Visualization Scripts Windows Visualization Tags Visualization Scripts

19. 18 AppServer AppEngine Platform FactorySuite A 2 Client Server New ApplicationObjects New 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. 19 Agenda ► Introduction ► Co-Existence Options ► High Level Analysis of Differences ► Detailed Analysis of Differences ► Recommendations for Today ► Migration Strategies

21. 20 Migration Existing UnitsNew Units Workstation PreviouslyIndustrial Application Server Galaxy Repository The rest of this presentation deals with how to plan for this in current projects and what the migration process will be.

22. 21 Tags versus ApplicationObjects ► What are the key differences? Tags Scripts History

23. 22 What is an ApplicationObject? Logic/Scripting Alarms/Events Inputs/Outputs History Scheme Security Valve Application Object Objects Contain All Configuration Elements

24. 23 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. 24 Industrial Application Server Naming CV403.Cmd.Quality Tagname:

26. 25 Hierarchical Naming Tagname Contained Name TK400.Waste.Cmd.Quality Hierarchical Name:

27. 26 Agenda ► Introduction ► Co-Existence Options ► High Level Analysis of Differences ► Detailed Analysis of Differences ► Recommendations for Today ► Migration Strategies

28. 27 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. 28 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. 29 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. 30 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. 31 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. 32 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. 33 Agenda ► Introduction ► Co-Existence Options ► High Level Analysis of Differences ► Detailed Analysis of Differences ► Recommendations for Today ► Migration Strategies

35. 34 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. 35 Create Instances – Option 1 Map Tags to instances CV101 CV101OLS CV101CLS CV101ALM CV101OUT InTouchIndustrial Application Server Best Option if: Varying Alarm Thresholds OR Custom Scaling Per Tag OR IO Addresses Follow No Rule

37. 36 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. 37 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. 38 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. 39 Questions? Wonderware is committed to protecting your investment, preserving your engineering effort, and simplifying your implementation of new technologies.