1. © 2012 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of Invensys or its subsidiaries. All third party trademarks and service marks are the proprietary marks of their respective owners. WW HMI SCADA-02 Wonderware Information Server 2012 R2 Elliott Middleton Product Manager

2. Slide 2 What We’ve Heard: You Need An integrated view of operations Shown “in context” One tool, multiple sources High-fidelity for troubleshooting & diagnostics Adapted to your needs & business Flexible to organize/adapt Minimizing the application-specific work With low risk Easy to make incremental improvements Low cost to get started Don’t give me something new to buy

3. Slide 3 Example: Batch Information How would you build this in InTouch (or.NET, etc.)? Once you had it, what else would you want to do? How would you re-use that to create a similar report?

4. Slide 4 Wonderware Information Server

5. Slide 5 Information Server 5.0 New “OverView” Feature Integrated view of process, alarm & production history Overlays, drill-through Direct access to source data (high fidelity, low latency) Built on an Information Model Other Improvements More robust installation & configuration Support for SharePoint 2010 (64-bit)

6. Slide 6 Data from multiple sources Drill through to details “Breadcrumbs” Quick access to related information

7. Slide 7 Breaking Down The Problem Presentation Navigation (“drill through”) Well-known kinds of data Finding related data The “Information Model” Data Access Product

8. Slide 8 Embellish with related data from multiple sources (lab, maintenance, etc. ) Trends in the time context of batch, job, shift, etc.

9. Slide 9 Perhaps use “halo” to indicate “phase” instead

10. Slide 10 Contrast With Historian Client Limit Alarm How This Works 1.Historian imports limits from InTouch 2.Trend evaluates data against limits Limitations Doesn’t work for Application Server tags (not imported) Alarm heuristics must be in Trend (e.g. missing ROC) Heuristics can’t be re-used in reports, etc.

11. Slide 11 Trends from database sources Example: MES production Highlights indicate “scrap” Example: MES production Highlights indicate “scrap”

12. Slide 12 Why Does This Approach Matter? User interface, especially good user interface: Is expensive to develop & inflates solution costs Needs consistent user experience Proper “separation of concerns”: Helps break down complex problems into simpler parts Allows application developers to focus on what is specific to their needs “Building blocks” that enable an incremental approach

13. Slide 13 About OverView Technology Zero-configuration client “Smart Client” (ClickOnce) Rich user experience, like a desktop application Installable from Internet Explorer, like a plug-in Automatically updates from source site Same ArchestrA Client framework also used for Wonderware MES Client A standalone UI-toolkit Likely used for an updated ArchestrA IDE in the future

14. Slide 14 Information Server 5.0 Information Model Types of information (Data Items) Relationships (subject-predicate-object) Rules (How to retrieve) OverView (based on ArchestrA Client) Data Adapter Technology Shared With Intelligence SQL Server Historian Oracle OSIsoft PI Text File Pre-defined Content Wonderware MES Historian Alarm History (WWALMDB)

15. Slide 15 Information Model Details Easily tailor display names (single language) Simple time zone conversion Internally, all UTC Optionally convert from data source’s local time Displayed in client’s local time Accessed via web service (HTTP) Information Model Types of information (Data Items) Relationships (subject-predicate-object) Rules (How to retrieve)

16. Slide 16 Model Examples Types of information (Data Items) Relationships (subject-predicate-object) Rules (How to retrieve a “triple”) “Real” Types Batch, Lot, Phase Shift, Operator, Alarm “Building Blocks” Status Indicator Time Series Process Event State Transition “Triples” Batch contains Lot Lot has Alarms Process Variable has Time Series Batch has prior Batch Script SELECT…FROM v_AlarmHistory WHERE TagName LIKE @EquipmentName+ '.%'

17. Slide 17 Basic Grid Any SQL query Standard actions File open/save Copy to clipboard Automatically: Uses regional settings Displays in local time User preferences: Sorting Grouping Column reordering & sizing

18. Slide 18 Drill Through Any SQL query Can be parameterized based on context Example: “@wo_id” parameter for “produced materials” Automatically Maintains history Included in file

19. Slide 19 Building Blocks Well-known “contract” between OverView & query results Based on names in the Model

20. Slide 20 Building Block: Status Indicator Required column: ImageURL Optional: ImageHoverText (RTF) Drill through relationship

21. Slide 21 Building Block: Time Series Required columns: Absolute Time Value OPCQuality Optional: Subject Data Interpolation type Stair step Linear

22. Slide 22 Building Block: Process Event Required columns: ImageURL Timestamp Optional: HoverText (RTF)

23. Slide 23 Building Block: State Transition Required columns: StartTimeUTC EndTimeUTC State (implies ARGB Color) Optional: Additional Fields Requires “Has Meta” relationship: State Color

24. Slide 24 Building Block: External Content Required columns: LinkURL DisplayName

25. Slide 25 Special Parameters ParameterUsage @aaServerHostNameHostname used to access the Information Server site from the client. Use for self-referencing URLs. @aaVirtualFolderNameVirtual directory name used by Information Server. Use for creating URLs to other content. @aaClientHostNameThe Fully Qualified Name (FQN) of the machine running the OverView client. Use to filter results based on the machine or subnet. @aaClientUserNameThe domain\account name of user running the OverView client. Use to filter content based on a user context. @aaClientLCIDThe LCID (e.g. 1033) corresponding to the Regional Settings on the OverView client system. Use to select localized content from source systems.

26. Slide 26 Example Application “Evolution” Start with a list of batches with start/end times Add indication of alarms Add “tooltip” with more details Add drill-through to alarm details Add summary of related comments Add drill-through to comment details Add “related” Historian tags Add “related” Time Series data

27. Slide 27 Example Application “Evolution” (cont.) Start with a basic batch trend Add indication of alarms Add operator comments

28. Slide 28 Breaking Down The Problem Presentation Navigation (“drill through”) Well-known kinds of data Finding related data The “Information Model” Data Access Product

29. Slide 29 But, how is this different than…?

30. Slide 30 Historian Client Historian Client Strengths Ad hoc selection (Tag & Time Pickers, “Live”) Flexible, detailed view of process history Reporting (via Excel add-in & Reporting Web Site) OverView Strengths Contextualized process history Ad hoc exploration of related contexts Model-based extensibility

31. Slide 31 Wonderware Intelligence Wonderware Intelligence Strengths Rich ad hoc analysis, discovering correlations (new questions) Self service calculations & dashboards from operational systems High-performance, long-term analysis OverView Strengths High-fidelity, pass through access to source data Evolutionary approach to contextualizing information Ad hoc navigation of related contexts (well-defined questions)

32. Slide 32 EMI Segmentation (Source: AMR 2006) Wonderwar e Historian Wonderwar e Historian Wonderw are MES Wonderw are Informatio n Server Wonderw are Informatio n Server Wonderware Intelligence Wonderware Intelligence

33. Slide 33 Information Server: Table Weaver Table Weaver Strengths Support for symbols Pure HTML tables OverView Strengths Richer formatting Scalable, sustainable technology Model-based extensibility

34. Slide 34 Complementary Solutions Wonderware Historian Client Wonderware Intelligence Wonderware Information Server

35. Slide 35 What We’ve Heard: You Need An integrated view of operations Shown “in context” One tool, multiple sources High-fidelity for troubleshooting & diagnostics Adapted to your needs & business Flexible to organize/adapt Minimizing the application-specific work with low risk Easy to make incremental improvements Low cost to get started Don’t give me something new to sell