1 / 40

FSA2-11 Designing and Architecting for Tomorrow

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.

teenie
Download Presentation

FSA2-11 Designing and Architecting for Tomorrow

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  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. FactorySuite A2 • ► Industrial Application Server • ► Plant Model • ► Centralized Administration • ► Object Based Paradigm • ► DA Servers • ► Multi-Developer IDE • ► Advanced System Diagnostics FactorySuite A2 FactorySuite 2000 FactorySuite 2000 ►Functionally Rich ► Common Communications (SuiteLink) ►New Functionality (DT Analyst, QI Analyst, AF) FactorySuite 1000 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 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 Today’s “Islands of Automation” Palletizing Invensys Bottling Honeywell Siemens Labeling Emerson Filling Batching ABB Every System In Your Plant, Working In Concert

  5. Existing Units New Units FactorySuite A2 FactorySuite 2000 Workstation Workstation Workstation Must Work Together What are you trying to address?

  6. Workstation 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. Existing Units New Units Existing Workstation Existing Workstation New Workstation 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. Existing Workstation Existing Workstation New Workstation Co-Existence #1 SuiteLink SuiteLink FactorySuite 2000 Version SuiteLink InTouch Version 7.11 or higher

  10. Existing Workstation Existing Workstation New Workstation 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. Galaxy Repository Existing Workstation Existing 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 Windows Visualization Tags Visualization Scripts Common Tags Mostly IO Tags Memory Tags Supervisory Scripts IO Server Separate Applications Single Node What are the components that make up a single node?

  15. InTouch Only Workstation InTouch and AppServer Windows Visualization Tags ApplicationObjects Windows Visualization Scripts DI Objects Common Tags AppEngine Visualization Tags Supervisory Scripts IO Server Visualization Scripts Platform Common Tags and Supervisory Scripts replaced by ApplicationObjects FactorySuite A2 Single Node InTouch remains unchanged.

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

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

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

  19. InTouch Client InTouch Client InTouch Client Windows Windows Windows Visualization Tags Visualization Tags Visualization Tags Visualization Scripts Visualization Scripts Visualization Scripts Platform Platform Platform AppServer AppServer ApplicationObjects DI Objects AppEngine AppEngine Platform Platform 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. Existing Units New Units Workstation Workstation Workstation 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 Scripts History Tags versus ApplicationObjects • What are the key differences?

  23. Inputs/Outputs Security Alarms/Events Logic/Scripting History Scheme 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: .Quality CV403 .Cmd

  26. Contained Name Tagname 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. Critical Information Bldg32_ Intake_ Area Sub-Area 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 > 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. InTouch Industrial Application Server CV101 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: 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.

More Related