Transcript Wonderware Information Server 2012 R2 (5.0)

WW HMI SCADA-02
Wonderware Information Server
2012 R2
Elliott Middleton
Product Manager
© 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.
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
Slide 2
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?
Slide 3
Wonderware
Information Server
Slide 4
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)
Slide 5
Quick access to
related information
Drill through to details
“Breadcrumbs”
Data from multiple
sources
Slide 6
Breaking Down The Problem
Presentation
Product
Navigation (“drill through”)
Well-known kinds of data
Finding related data
The “Information Model”
Data Access
Product
Slide 7
Trends in the time context of batch, job, shift, etc.
Embellish with related data
from multiple sources (lab,
maintenance, etc. )
Slide 8
Perhaps use “halo” to
indicate “phase” instead
Slide 9
Contrast With Historian Client
Alarm
Limit
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.
Slide 10
Trends from database sources
Example: MES production
Highlights indicate “scrap”
Slide 11
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
Slide 12
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
Slide 13
Information Model
OverView
(based on ArchestrA Client)
Information Server 5.0
Information Model
Types of information
(Data Items)
Pre-defined Content
• Wonderware MES
• Historian
• Alarm History
(WWALMDB)
Relationships
(subject-predicate-object)
Rules
(How to retrieve)
Slide 14
Data Adapter Technology
Shared With Intelligence
• SQL Server
• Historian
• Oracle
• OSIsoft PI
• Text File
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)
Slide 15
Information Model
Types of information
(Data Items)
Relationships
(subject-predicate-object)
Rules
(How to retrieve)
Model Examples
Types of information
(Data Items)
Relationships
(subject-predicate-object)
Rules
(How to retrieve a “triple”)
Slide 16
“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+ '.%'
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
Slide 17
Drill Through
Any SQL query
• Can be parameterized based on context
• Example: “@wo_id” parameter for “produced materials”
Automatically
• Maintains history
• Included in file
Slide 18
Building Blocks
Well-known “contract” between OverView & query
results
Based on names in the Model
Slide 19
Building Block: Status Indicator
Required column: ImageURL
Optional:
• ImageHoverText (RTF)
• Drill through relationship
Slide 20
Building Block: Time Series
Required columns:
• Absolute Time
• Value
• OPCQuality
Optional: Subject Data
Interpolation type
• Stair step
• Linear
Slide 21
Building Block: Process Event
Required columns:
• ImageURL
• Timestamp
Optional: HoverText (RTF)
Slide 22
Building Block: State Transition
Required columns:
• StartTimeUTC
• EndTimeUTC
• State (implies ARGB Color)
Optional: Additional Fields
Requires “Has Meta”
relationship:
• State
• Color
Slide 23
Building Block: External Content
Required columns:
• LinkURL
• DisplayName
Slide 24
Special Parameters
Slide 25
Parameter
Usage
@aaServerHostName
Hostname used to access the Information Server
site from the client. Use for self-referencing URLs.
@aaVirtualFolderName
Virtual directory name used by Information Server.
Use for creating URLs to other content.
@aaClientHostName
The Fully Qualified Name (FQN) of the machine
running the OverView client. Use to filter results
based on the machine or subnet.
@aaClientUserName
The domain\account name of user running the
OverView client. Use to filter content based on a
user context.
@aaClientLCID
The LCID (e.g. 1033) corresponding to the Regional
Settings on the OverView client system. Use to
select localized content from source systems.
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
Slide 26
Example Application “Evolution” (cont.)
Start with a basic batch trend
Add indication of alarms
Add operator comments
Slide 27
Breaking Down The Problem
Presentation
Product
Navigation (“drill through”)
Well-known kinds of data
Finding related data
The “Information Model”
Data Access
Product
Slide 28
But, how is this different than…?
Slide 29
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
Slide 30
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)
Slide 31
EMI Segmentation (Source: AMR 2006)
Wonderw
Wonderware
are MES
Informatio
Wonderwar
n Server
e
Historian
Slide 32
Wonderware
Intelligence
Information Server: Table Weaver
Table Weaver Strengths
•Support for symbols
•Pure HTML tables
OverView Strengths
•Richer formatting
•Scalable, sustainable technology
•Model-based extensibility
Slide 33
Complementary Solutions
Wonderware
Historian Client
Slide 34
Wonderware
Intelligence
Wonderware
Information Server
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
Slide 35