1. WW HMI SCADA-07 Wonderware Best Practices Part 1-InTouch
Brian Martin & Jeff Tapia
Wonderware Technical Sales Consultants
Invensys Operations Management
Title slide [from Title Slide master]
The title slide is available as a Title Master and the background and graphic elements are fixed. Text is editable for the slide heading and presentation details but the small compliance text exists in editable form only on the Title Master itself. This type area should be used only for the purposes of compliance text and should not be replaced by other content.
Font, type size and colors are fixed for the Title Master style and should not be modified.
Footer details
Footer detail appear in the bottom-left corner of the slide and appear in fixed positions and order. Editing of the Footer details is done by accessing ‘Header and Footer’ under the ‘View’ menu in PowerPoint®.

2. Agenda InTouch Architectures Managed Applications
20-Apr-17
Agenda
InTouch Architectures
Managed Applications
Designing for today & tomorrow
Conclusions
(c) 2002 Invensys Systems, Inc.

3. Why Different Architectures?
20-Apr-17
Why Different Architectures?
Networks change over time
Processes changes over time
Needs change over time
Industrial Control systems have communications limits
(Pay Attention! This is the dirty little secret!)
Windows has communications limits
(But not too much anymore! Pay Attention to Data Provider limits)
(c) 2002 Invensys Systems, Inc.

4. Architectures Stand-alone Client Based File Server Based
20-Apr-17
Architectures
Stand-alone
Client Based
File Server Based
Database Server/Client (Master/Slave)
Database Server/Client (Three Tier Remote Tag Reference)
NAD (Network Application Development)
NAD is an Application Distribution Architecture!
(c) 2002 Invensys Systems, Inc.

5. Design Considerations
20-Apr-17
Design Considerations
Number of IO Devices (PLCs, RTUs, DCSs, etc.)
Number of Servers and Location
Number of View Nodes and Location
Physical/Logical LAN/WAN Network Architecture
Redundancy
Change Control
You should be thinking about System Platform
(c) 2002 Invensys Systems, Inc.

6. Stand-Alone Architecture
20-Apr-17
Stand-Alone Architecture
Stand-alone
KISS (Keep It Simple, Stupid)
Dev/RT/IO
I/O Server
Process
(c) 2002 Invensys Systems, Inc.

7. Client/Server - PLC Network
20-Apr-17
Client/Server - PLC Network
Client Based - PLC Server, PLC Network
Also KISS.
Inherently Redundant
Requires Multi-Master/Peer-Peer PLC Network
Application Distribution?
Can overwhelm proprietary PLC networks
But more importantly, THE INDIVIDUAL PLC!
Even on Ethernet!
This is the #1 cause of slow performance!!!
Dev/RT&I/O Server
RT&I/O Server
RT&I/O Server
RT&I/O Server
Process
Process
Process
Process
DH+, MB+, etc.
(c) 2002 Invensys Systems, Inc.

8. Client Server PLC/Ethernet
20-Apr-17
Client Server PLC/Ethernet
Client Based - PLC Server/Hybrid Network
Maximizes PLC Throughput
Also KISS. Good to 50 (200-v7) IO conversations. (5-10 PLC’s, 4-8 Nodes) (The Small Model)
Supports HBU RT
RT&I/O Server
Process
RT&I/O Server RT RT
Modem
Ethernet
(c) 2002 Invensys Systems, Inc.

9. Client/Server - File Server (Obsolete)
20-Apr-17
Client/Server - File Server (Obsolete)
File Server Based
KISS- Good to 50 (200-v7) IO conversations. (5-10 PLC’s, 4-8 Nodes) (Small Model)
A change on the server is seen everywhere
Client apps use server’s hard drive
App Development Restricted
Does Not Support HBU
All nodes must have same resolution.
Retentive Tags?
Many Terminal Services Apps inadvertently use this model – DON’T!
DEV/RT/IO
File Server
View Only RT
View Only RT
Process
Ethernet
(c) 2002 Invensys Systems, Inc.

10. Client/Server Master/Slave
20-Apr-17
Client/Server Master/Slave
Server/Client (Master/Slave)(Pre 7.0)
For LARGE Networks (20+ PLC’s or 15+ nodes) (Large Model)
Can be more complex in Distribution (Two Separate App’s)
Slave Access - Application=View, Topic=Tagname
Can support HBU
Thick Client
Dev/RT/IO
Database Server(s)
Factory
Focus RT RT RT RT RT RT
Process
Ethernet
(c) 2002 Invensys Systems, Inc.

11. Three Tier Client/Server
20-Apr-17
Three Tier Client/Server
Remote Tag Reference (RTR)
For REALLY BIG Networks (20+ PLC’s or ’s+ nodes) (Large Model)
Simple to implement
Many Network Distribution Options
Can support HBU
Supports Thick/Thinner/Thin Clients
Dev/RT/IO
Database Server(s)
Factory
Focus RT RT RT RT RT RT
Process
Ethernet
(c) 2002 Invensys Systems, Inc.

12. Remote Tag Reference Three Tier Architecture
20-Apr-17
Remote Tag Reference Three Tier Architecture
Simplified Development for Large Systems
Can have Windows Only Nodes (Tag-less app)
A Client Node can be promoted to Server Node
Single Application for all Nodes!
Only the Server Nodes get IO data
Use GetNodeName() function for additional node specific customization
Can easily migrate to Industrial Application Server!
(c) 2002 Invensys Systems, Inc.

13. Three Tier Architecture Services
20-Apr-17
Three Tier Architecture Services
I/O Server Service
Tag Database Server Service
Client to the IO Server Service
Tag Client Service
Remote Reference Tags
Local Tags on Windows/Scripts
Are not part of Tag Database
Can have tag database-less Nodes
X-Ref’d in InTouch WindowMaker
Reduced Network Load
The Services may or may not run on the same PC !
Developer’s Choice
(c) 2002 Invensys Systems, Inc.

14. Three Tier Redundancy Server Client/Backup Client Dormant ! IO Server
20-Apr-17
Three Tier Redundancy
Server
Client/Backup
Client
Dormant !
IO Server
IO Server
Tag Server
Tag Server
Dormant !
Tag Server
Dormant !
Window/Script
Window/Script
Window/Script
(c) 2002 Invensys Systems, Inc.

15. Three Tier Redundancy Server Client/Backup Client IO Server IO Server
20-Apr-17
Three Tier Redundancy
Server
Client/Backup
Client
IO Server
IO Server
Dormant !
Dormant !
Tag Server
Tag Server
Tag Server
Window
Window
Window
(c) 2002 Invensys Systems, Inc.

16. Three Tier Redundancy Server Client/Backup Client IO Server IO Server
20-Apr-17
Three Tier Redundancy
Server
Client/Backup
Client
IO Server
IO Server
Dormant !
Tag Server
Tag Server
Tag Server
Window
Window
Window
(c) 2002 Invensys Systems, Inc.

17. Remote Tag Reference Window/Script Usage AccessName:TagName
20-Apr-17
Remote Tag Reference
Window/Script Usage
AccessName:TagName
Example: Server1:FI1033, Galaxy:TIC3071.SP
Usage is identical to a normal tag, it just looks different
Can use Tag Browser to browse and automatically insert Remote Reference Tags!
InTouch, InControl, Industrial Application Server etc.
(c) 2002 Invensys Systems, Inc.

18. Indirect Remote Tag Reference
20-Apr-17
Indirect Remote Tag Reference
Indirect Usage - Three Constructs
IndirectTag.Name = “AccessName:TagName”;
Explicit Reference using String type
IndirectTag.Name = “AccessName:”+ TagName.Name OR
IndirectTag.Name =AccessName:TagName.Name;
- Allows usage of local Tag Dictionary/Makes Tag Substitution a snap
AccessName:IndirectTag.Name = “AccessName:”+ TagName.Name;
Uses the Indirect tag on the Server node!
Clients can step on each other!
Note the different syntax in Indirect RTR vs an Animation link
Indirect naming uses strings!
The reference is not instantaneous, esp. on a remote node!
(c) 2002 Invensys Systems, Inc.

19. Converting an Existing App to RTR
20-Apr-17
Converting an Existing App to RTR
Two methods:
Select all tags in window or script and Index all tags. Then convert to Remote
Import windows and scripts. Then convert to Remote
Attention must be paid to Indirect Tags due to their unique function!
Decide where the Indirect needs to be invoked; Locally or Remotely
Understand the effect of invoking an indirect RTR on the Tag Server!
(c) 2002 Invensys Systems, Inc.

20. Converting an Existing App to RTR
20-Apr-17
Converting an Existing App to RTR 2 3 4 1
(c) 2002 Invensys Systems, Inc.

21. Preferred Topology Isolate Industrial Networks from Office Networks
20-Apr-17
Preferred Topology
Isolate Industrial Networks from Office Networks
Isolate via Routers, Switches, Dual NICs
Office Networks have large “blobs” of data packets irregular in time and are not time critical
Industrial Networks have small packets very regular in time, and are time critical!
You WILL have problems if you mix the two data types!!! (only a question of when)
(c) 2002 Invensys Systems, Inc.

22. Agenda InTouch Architectures Managed Applications
20-Apr-17
Agenda
InTouch Architectures
Managed Applications
Designing for today & tomorrow
Conclusions
(c) 2002 Invensys Systems, Inc.

23. How Architectures Have Evolved
Pre-Historic
DEV on all PCs (license change)
Sneaker Net
Historic
Development Copying
File Server
Present Day
Network Application Development (NAD)
Central Development

24. Upgrade Existing Applications InTouch 2012 InTouch 2012 Standalone
IDE Managed
Applications
InTouch 2012
Published
Applications

25. HMI Application Management
Central Management - Galaxy
Check in, Check out
Template, Propagation
Standardization, Multi User
Reduce Total Cost
Engineering Efficiency
ArchestrA Graphics
Smart & Intelligent
Built-in Diagnostics & Status
Runtime & Dev. Features
Universal Platform
Platform for Collaborative Apps
Advanced Applications
Rich Extensibility
Standard Form Factor

26. Development
WindowMaker\IDE
(Derry)
Galaxy Repository
(Derry)
InTouch Client
Water
(Antrim)
InTouch Client
Reactor
(Deering)
InTouch Client
MagTape
(Seabrook)
InTouch Client
Reactor\HVAC
(Epping)

27. Now Let’s Do The Rest Prior To This Session
Created Galaxy Created and Deployed Platforms For View Clients Created and Deployed ViewEngines For View Clients
Now Let’s Do
The Rest

28. The Rest
Import Applications Derive Instances of InTouch Applications Convert Smart Symbol to ArchestrA Graphic Replace Graphic in Application Look at Check-In \ Check-Out Capability Look at Versioning and Comments Publishing an Application Export Application

29. Our Applications

30. Tools and Deployment

31. Let’s Do it
ArchestrA IDE

32. Agenda InTouch Architectures Managed Applications
20-Apr-17
Agenda
InTouch Architectures
Managed Applications
Designing for today & tomorrow
Conclusions
(c) 2002 Invensys Systems, Inc.

33. Developing for today and tomorrow
20-Apr-17
Developing for today and tomorrow
Demonstration using InTouch in today’s development environment…
Let’s do more!
Importing into IDE, Browsing, InTouch Proxy,
Importing InTouch Graphics into A2,
Placing imported graphics back in InTouch apps,
Importing multiple InTouch apps (common library across apps),
Alarms, Trend,
Managing InTouch Apps, Deploy,
Don’t drop on InTouch Windows and why
Bulk Import for moving forward
etc.
(c) 2002 Invensys Systems, Inc.

34. ArchestrA Graphics in InTouch
Avoid Assembling ArchestrA Graphics in the InTouch Window
Create an ArchestrA Graphics Toolset For InTouch “Windows”
For Each InTouch Window Create an ArchestrA Symbol For It
Assemble the Graphics in the Symbol for the Window
It is now reusable across InTouch Applications and WIS
You will be Better Prepared for the ArchestrA Window Object
Object Graphics must be Assembled in an Object
Candidate Objects for this organization
Area Objects
View Engine Objects
Once Laid out the InTouch app does not need to be opened in WindowMaker
InTouch View Application Instances
Provide a DI Gateway to the InTouch Tag Dictionary
InTouch: is the Relative name from ArchestrA Graphics
Galaxy: is the Relative name from InTouch
Text slide, with title and body text [from Slide Master]
This slide exists as a Slide Master and all type specifications and graphic elements are fixed. Simply type into the prompt boxes.
The layout is set as a Title Box and Text Box – within the Text Box there are five levels of type:
Level 1 – Body text set in Verdana Regular (18pt on 24pt linefeed) with ‘0.5 line’ space below each paragraph.
Level 2 – Bulleted body text set in Verdana Regular (18pt on 24pt linefeed) with ‘0.5 line’ space below each paragraph.
Level 3 – Bulleted body text (using a horizontal dash) set in Verdana Regular (16pt on 20pt linefeed) with ‘0.5 line’ space below each paragraph.
Level 4 – Bulleted body text set in Verdana Regular (15pt on 18pt linefeed) with ‘0.5 line’ space below each paragraph.
Level 5 – Bulleted body text (using a horizontal dash) set in Verdana Regular (14pt on 17pt linefeed) with ‘0.5 line’ space below each paragraph.
Within standard body text, subheads are set in Verdana Bold at the same size as the body text.
Advancing through the text levels
To advance to each text level from the previous one you can use the ‘Increase Indent’ and ‘Decrease Indent’ buttons on the ‘Formatting’ toolbar in PowerPoint®.
While the text position is fixed, the text box will grow as you enter further content in the slide – therefore, care should be taken to keep within the present text box margins.

35. Element Grouping
When using the Grouping mechanism in graphics there is an optimization done for groups with no animation. The group is handled as an image.
The Tank on the right opens in half the time with half the static CPU load of the tank on the right.
Retrieve
Render
Bind
Continuous
Close

36. Agenda InTouch Architectures Managed Applications
20-Apr-17
Agenda
InTouch Architectures
Managed Applications
Designing for today & tomorrow
Conclusions
(c) 2002 Invensys Systems, Inc.

37. Using System Platform - Introduction
20-Apr-17
Using System Platform - Introduction
Typical AppServer Projects are Hybrid
InTouch is the Front End
Existing InTouch Apps can provide Galaxy Data via an InTouch Proxy Object
Automation Object Server
InTouch View
Platform
WW Historian
Galaxy Repository
IDE A² Development Workstation
(c) 2002 Invensys Systems, Inc.

38. Tag Server vs. App Server
20-Apr-17
Tag Server vs. App Server
Remote Tag References
Client-Server
Client-Server or Peer-to Peer
Multiple namespaces
Single Namespace
Event-based
Scan-based
Limited to 60K Tags (I/O and Memory)
1MM I/O + Memory/Calc attributes
No feedback writes
Confirmed writes
Display links have no comm status built-in
Links can have comm status (.#VString)
Per-server admin
Central admin via IDE
(c) 2002 Invensys Systems, Inc.

39. Designing Easy to Migrate Applications
20-Apr-17
Designing Easy to Migrate Applications
AppServer
AppEngine
Platform
New ApplicationObjects
New DI Objects
InTouch Client
Windows
Visualization Tags
Visualization Scripts
ApplicationObjects
DI Objects
Classic InTouch Application
Separation of Tags and scripts.
Tag Server Architecture
IAS Architecture – Natural Evolution
InTouch Application
Windows
Tags
Scripts
Single node InTouch Application
Windows
Visualization Tags
Visualization Scripts
Common Tags
Supervisory Scripts
Target Architecture?
InTouch Client
Tag Server
Common Tags
Supervisory Scripts
IO Server
Windows
Visualization Tags
Visualization Scripts
We will now look at the architecture applied get an Idea of what will be required to migrate a system.
(c) 2002 Invensys Systems, Inc.

40. Tagname Dictionary InTouch tag name dictionary is a flat namespace.
20-Apr-17
Tagname Dictionary
InTouch tag name dictionary is a flat namespace.
Industrial Application Server namespace is hierarchical, based on plant model.
The key point here is that it will be much easier to determine the what tags will be replaced by what objects if it is easy to determine what a group of tags represent and to then be able to filter them.
Device Type – This will tell the user what template to use.
Unique Identifier – This will map to the object tagname.
Attribute Identifier – Object attribute are the most equivalent piece of an ApplicationObject to a tag. This information will determine what attribute of the object this tag maps to.
(c) 2002 Invensys Systems, Inc.

41. Bldg32_ Intake_ FCV 1834 OLS GALAXY:Bldg32.Intake.FCV1834.OLS
20-Apr-17
Tagname Dictionary
Structure, Structure, Structure…
Strict adherence to a naming convention that is hierarchical.
Example:
Critical Information
Area
Bldg32_
Sub-Area
Intake_
FCV
1834
OLS
GALAXY:Bldg32.Intake.FCV1834.OLS
Device
Type
Unique
Identifier
Attribute
Identifier
The key point here is that it will be much easier to determine the what tags will be replaced by what objects if it is easy to determine what a group of tags represent and to then be able to filter them.
Device Type – This will tell the user what template to use.
Unique Identifier – This will map to the object tagname.
Attribute Identifier – Object attribute are the most equivalent piece of an ApplicationObject to a tag. This information will determine what attribute of the object this tag maps to.
This convention is an example. Implement the one that best suits your project.
(c) 2002 Invensys Systems, Inc.

42. Industrial Application Server
20-Apr-17
Migration
Existing Units
New Units
Workstation
Galaxy Repository
Returning to our earlier example, here if a FS200 system were implemented. There would be three separate applications defined to perform similar functions.
Industrial application server will define a single application that spans multiple machines.
We will now explore how to plan for this in current InTouch applications.
Industrial Application Server
Previously
(c) 2002 Invensys Systems, Inc.

43. Tags versus ApplicationObjects
20-Apr-17
Tags versus ApplicationObjects
What are the key differences?
Tags
Scripts
History
ArchestrA
System
Platform
Wonderware
InTouch
FS2000 based application are primarily tag based.
These application are define ed by multiple tags scripts and other types of definitions.
These definitions are separated from each other with one central management.
FSA2 systems utilized ArchestrA technology.
ArchestrA is an object based technology.
This groups the tags, scripts and other definitions onto packages that can be centrally managed.
(c) 2002 Invensys Systems, Inc.

44. Take Advantage IAS Reduce Lifecycle Cost of Ownership
Standards
Architectural Freedom
Scalability
High Availability
Security
Software Management
Provide Real-time and Historical Plant Intelligence
Basis for Future Production System Requirements
Wonderware platform for now and the future

45. Migration Strategies Migrate Entire System
Migrate Systems Area by Area
You do not need to migrate the old system all at once
IAS can run with InTouch and other legacy systems
Exchange information with these systems
Use ArchestrA on new Plant Areas and Migrate old Areas Later

46. Bulk Import Utility Introducing the Bulk Import Utility
Want to move to Industrial Application Server (IAS) ……. But are heavily invested with InTouch applications …. Or Intellution or GE or Rockwell or Siemens or ….. ????
Introducing the Bulk Import Utility
reads InTouch tag database
or other CSV output from existing apps
or XML output from existing apps
easily creates Object templates and instances for import into IAS

47. Create Hierarchical Namespace from Flat Tag names
20-Apr-17
Create Hierarchical Namespace from Flat Tag names
Run Import Tag Wizard
Filter resulting Mapped tags to create objects
Connect & Download Templates from Galaxy
Create New Project
Validate and Upload New Objects and Instances to Galaxy
The work flow for the utility is as follows:
Create a project or open an existing one
Import the tags from a file using the Import Tag Wizard
Filter the resulting tags to find possible objects based off structured naming by the application
Connect to the Galaxy, download templates to map the structured objects defined early. Note that both templates and instances are created.
Repeat until all tags that are important are assigned to an object.
(c) 2002 Invensys Systems, Inc.

48. Mappings from Import Tag Wizard
20-Apr-17
Mappings from Import Tag Wizard
Mapping for InTouch is provided.
BIU can import other CSV files from all the major HMI and PLC vendors.
Mappings to be provided separately by application engineers.
BIU can also read most well formed XML which is used in many Enterprise applications!
(c) 2002 Invensys Systems, Inc.

49. Modify InTouch App Replace Tags with Galaxy References
20-Apr-17
Modify InTouch App
Replace Tags with Galaxy References
Access names to I/O Servers are dropped
Review Scripting
Remove scripts that are now handled in Objects
Point Alarm View Objects to ArchestrA
Point Historical Trend to Historian
In most cases the InTouch Application becomes simpler
(c) 2002 Invensys Systems, Inc.

50. Related sessions See sessions:
WW TSS 03 ArchestrA Graphics: Designs Guidelines for Top Performance
{and thank them for some content}
WW HMI SCADA 08 - Best Practices Part 2 – System Platform
WW HMI SCADA 09 - Best Practices Part 3 – Historian
WW HMI SCADA 10 - Best Practices Part 4 – Wonderware Remote Access

51. Thank You

52. Session Description
In this session we will discuss design considerations to achieve the best performance from your Wonderware ArchestrA Graphics. Topics include but not limited to: Performance considerations, Best Practices, common mistakes and Optimization. Duration: 90 Minutes