Post on 09-Feb-2016
description
© 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-02Wonderware Information Server2012 R2
Elliott MiddletonProduct Manager
Slide 2
What We’ve Heard: You NeedAn integrated view of operations• Shown “in context”• One tool, multiple sourcesHigh-fidelity for troubleshooting & diagnostics• Adapted to your needs & business• Flexible to organize/adaptMinimizing the application-specific workWith low risk• Easy to make incremental improvements• Low cost to get startedDon’t give me something new to buy
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?
Slide 4
Wonderware Information Server
Slide 5
Information Server 5.0New “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 ModelOther Improvements• More robust installation & configuration• Support for SharePoint 2010 (64-bit)
Slide 6
Data from multiple sources
Drill through to details
“Breadcrumbs”
Quick access to related information
Slide 7
Breaking Down The ProblemPresentation
Navigation (“drill through”)
Well-known kinds of data
Finding related data
The “Information Model”
Data Access
Product
Product
Slide 8
Embellish with related data from multiple sources (lab, maintenance, etc. )
Trends in the time context of batch, job, shift, etc.
Slide 9
Perhaps use “halo” to indicate “phase” instead
Slide 10
Contrast With Historian Client
Limit
Alarm
How This Works1. Historian imports limits from InTouch2. Trend evaluates data against limits
LimitationsDoesn’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 11
Trends from database sources
Example: MES productionHighlights indicate “scrap”
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
Slide 13
About OverView TechnologyZero-configuration client“Smart Client” (ClickOnce)• Rich user experience, like a desktop application• Installable from Internet Explorer, like a plug-in• Automatically updates from source siteSame ArchestrA Client framework also used for• Wonderware MES Client• A standalone UI-toolkit• Likely used for an updated ArchestrA IDE in the future
Slide 14
Information Server 5.0
Information Model
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)
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 timeAccessed via web service (HTTP)
Information Model
Types of information(Data Items)
Relationships (subject-predicate-object)
Rules(How to retrieve)
Slide 16
Model Examples
Types of information(Data Items)
Relationships (subject-predicate-object)
Rules(How to retrieve a “triple”)
“Real” TypesBatch, Lot, PhaseShift, Operator, Alarm
“Building Blocks”Status IndicatorTime Series
Process EventState Transition“Triples”
Batch contains LotLot has AlarmsProcess Variable has Time SeriesBatch has prior Batch
ScriptSELECT…FROM v_AlarmHistoryWHERE TagName LIKE @EquipmentName+ '.%'
Slide 17
Basic GridAny SQL queryStandard actions• File open/save• Copy to clipboardAutomatically:• Uses regional settings• Displays in local timeUser preferences:• Sorting• Grouping• Column reordering & sizing
Slide 18
Drill ThroughAny SQL query• Can be parameterized based on context• Example: “@wo_id” parameter for “produced materials”Automatically• Maintains history• Included in file
Slide 19
Building Blocks
Well-known “contract” between OverView & query resultsBased on names in the Model
Slide 20
Building Block: Status Indicator
Required column: ImageURLOptional:• ImageHoverText (RTF)• Drill through relationship
Slide 21
Building Block: Time Series
Required columns:• Absolute Time• Value• OPCQuality
Optional: Subject DataInterpolation type• Stair step• Linear
Slide 22
Building Block: Process Event
Required columns:• ImageURL• TimestampOptional: HoverText (RTF)
Slide 23
Building Block: State Transition
Required columns:• StartTimeUTC• EndTimeUTC• State (implies ARGB Color)Optional: Additional Fields
Requires “Has Meta” relationship:• State• Color
Slide 24
Building Block: External Content
Required columns:• LinkURL• DisplayName
Slide 25
Special ParametersParameter 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.
Slide 26
Example Application “Evolution”Start with a list of batches with start/end timesAdd indication of alarms Add “tooltip” with more details Add drill-through to alarm detailsAdd summary of related comments Add drill-through to comment detailsAdd “related” Historian tags Add “related” Time Series data
Slide 27
Example Application “Evolution” (cont.)Start with a basic batch trendAdd indication of alarmsAdd operator comments
Slide 28
Breaking Down The ProblemPresentation
Navigation (“drill through”)
Well-known kinds of data
Finding related data
The “Information Model”
Data Access
Product
Product
Slide 29
But, how is this different than…?
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
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)
Slide 32
EMI Segmentation (Source: AMR 2006)
Wonderware
Historian
Wonderware MES
Wonderware
Information Server
WonderwareIntelligence
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
Slide 34
Complementary Solutions
Wonderware Historian Client
Wonderware Intelligence
Wonderware Information Server
Slide 35
What We’ve Heard: You NeedAn integrated view of operations• Shown “in context”• One tool, multiple sourcesHigh-fidelity for troubleshooting & diagnostics• Adapted to your needs & business• Flexible to organize/adaptMinimizing the application-specific work with low risk• Easy to make incremental improvements• Low cost to get startedDon’t give me something new to sell