FSA 2 11 Designing and Architecting for Tomorrow

FSA 2 -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 1

Evolution of Wonderware Factory. Suite A 2 g in v ol v E y lit a n io t nc u F to w Ne e ur t c te i ch r A Factory. Suite A 2 ► Industrial Application Server ► Plant Model ► Centralized Administration ► Object Based Paradigm ► DA Servers ► Multi-Developer IDE ► Advanced System Diagnostics Factory. Suite 2000 ►Functionally Rich ► Common Communications (Suite. Link) ►New Functionality (DT Analyst, QI Analyst, AF) Factory. Suite 1000 ►Introduces the Integrated Suite Concept ► Introduces Industrial. SQL Server Historian ►Introduces In. Control PC-Based Control Engine Pre - Factory. Suite ►Best of Breed Products and Acknowledged ► Rapid Rise to Dominance in HMI Market ►Largest Leader in Ease-of-Use Breadth of I/O and Plant Floor Connectivity 2

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

What are you trying to address? Existing Units Workstation New Units Workstation Factory. Suite 2000 Workstation Must Work Together Factory. Suite A 2 4

New Workstation Detail ►If using In. Touch 8. 0 as the link to field devices there is no change from. Workstation how applications are migrated. ►The rest of this presentation assumes that Industrial Application Server is being applied on the new workstation. 5

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

Co-Existence #1 Existing Units New Units Existing Workstation ► New workstation co-exists with New existing workstations. § Existing workstation applications remain unchanged. § Existing Workstations continue to run the same version of software. 7

Co-Existence #1 Existing Workstation New Workstation Suite. Link Factory. Suite 2000 Version Suite. Link In. Touch Version 7. 11 or higher 8

Co-Existence #2 Existing Workstation New Workstation ►New workstation co-exists with existing workstations. § Existing In. Touch applications are converted to version 8 (single button push). § Industrial Application Server Platforms are deployed to the Existing Workstations. 9

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

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

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 Factory. Suite A 2. § Single Node § Peer to Peer § Client Server 12

Single Node What are the components that make up a single node? In. Touch Workstation Windows Memory Tags Visualization Scripts Mostly IO Tags Common Tags Supervisory Scripts IO Server Separate Applications 13

Factory. Suite A 2 Single Node In. Touch remains unchanged. In. Touch Only Workstation In. Touch and App. Server Windows Application. Objects Visualization Tags Visualization Scripts Windows DI Objects Common Tags Visualization Tags App. Engine Visualization Scripts Platform Supervisory Scripts IO Server Common Tags and Supervisory Scripts replaced by Application. Objects 14

Peer to Peer Multiple workstations duplicate functionality. In. Touch Workstation Windows Visualization Tags Visualization Scripts Common Tags Supervisory Scripts IO Server Supervisory Scripts 15 IO Server

Factory. Suite A 2 Peer to Peer Supervisory Control functionality is not duplicated. In. Touch and App. Server Application. Objects New App. Objects Windows DI Objects Windows New DI Objects Visualization Tags App. Engine Visualization Scripts Platform 16

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

Factory. Suite A 2 Client Server In. Touch Client Windows Visualization Tags Visualization Scripts Platform App. Server Application. Objects DI Objects New Application. Objects App. Engine Platform 18

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

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

Tags versus Application. Objects ► What are the key differences? Tags Scripts History 21

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

How are these objects used? The $Valve Template can be used to create several instances of the device. CV 101 This Object is a Template for Other Objects • Changes to Template Automatically Propagate to Instances CV 201 • New Templates can be Derived from Existing Templates • Libraries of Standard Objects can be Developed • Standard Templates Decrease Project-to-Project Costs $Valve CV 301 CV 401 23

Industrial Application Server Naming Tagname: CV 403. Cmd. Quality 24

Hierarchical Naming Hierarchical Name: TK 400. Waste. Cmd. Quality Contained Name Tagname 25

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

Building Today ► When building and maintaining your applications today there are practices which will facilitate the migration process. ► These practices are recommend for all In. Touch applications regardless of their intent of migration. 27

Tagname Dictionary ►Structure, Structure… ►Strict adherence to a naming convention that is hierarchical. Example: Bldg 32_ Intake_ FCV 1834 OLS Area Device Sub-Area Type Unique Critical Information Attribute Identifier This convention is an example you are free to implement one that suits your purpose best. 28

Scripting ►Q: What is the script Language used in Industrial Application Server? ►A: Quick. Script. NET. § Same syntax as In. Touch § All relevant script functions supported § Compiles to. NET Common Language Runtime (CLR) 29

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 $Access. Level > 9000 THEN Security is now implemented at the data level. Start. Sequence = 1; ENDIF; 30

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

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

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

Migration Tasks ► Create Templates § Manually Defined ► Create Instances § Option 1: Preserve Tag Data § Option 2: Build into Templates ► Update In. Touch Application § Option 1: Replace All Links § Option 2: Redirect Tags § Delete Obsolete functionality. 34

Create Instances – Option 1 In. Touch Industrial Application Server Best Option if: Varying Alarm Thresholds CV 101 OLS CV 101 CLS CV 101 ALM OR CV 101 Custom Scaling Per Tag CV 101 OUT OR Map Tags to instances IO Addresses Follow No Rule 35

Create Instances – Option 2 ► Build Scaling Definitions Into Template Best Option if: ► Build Alarm Limits into Template Common Alarm. Into Thresholds ► Build IO Addresses Template § References can be through Many applications are likely to ORwritten scripts. use parts from Option 1 and Scaling Device parts from Option 2. § If IO Common addresses have aby mathematic relationship to their ORnames or other criteria they can be set dynamically. IO Addresses Follow Rules ► Easier than Option 1 36

Update In. Touch: Replace All Links ► Replace tag references with remote references: Galaxy: Object. Name. Attribute ► Edit All Windows and Scripts OR ► Use In. Touch Search and Replace Functionality § Available later this year. ► Delete Unused Tags 37

Update In. Touch: Redirect Tags ► In. Touch 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. 38

Questions? Wonderware is committed to protecting your investment, preserving your engineering effort, and simplifying your implementation of new technologies. 39