The Wonderware System

Wonderware’s System Platform
Presentation map
Wonderware System
Platform
Commercial information
Functional and technical

High level overview Concepts and benefits Information management
capabilities
What can Wonderware From tag-centric HMI to Configuration and

InTouch visualization
do for you? equipment-centric Storage
System Platform
The power of a single Troubleshooting and Multi-developer

platform Standards that enable analysis environment
continual improvement
Operational and
Delivery of information System scalability
financial benefits Information in context of
the plant model
Application Examples Secure runtime

Device integration environment
Protecting your
investment: High availability
From the past to the Software integration
future
High level overview
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
What can Wonderware do for you
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Wonderware Software Solutions
System Information/Plant
Production & Manufacturing Activities
Inter-operability Visibility
ERP
Device, Application, Enterprise Integration
(SAP, Oracle,
Microsoft..)
Industry Applications Industry Packs
Empowering All Roles in the Plant

Base Template Libraries
Database
Applications
Specific Function Specific Function Specific Function
Modules Modules Modules
Asset
Management
System
Clients
Platform
LIM Systems Microsoft Technology & Industry Standards
Devices
Enabling operational breakthroughs
IT & Infrastructure
Engineering
Operations
Issue: Needs:
Amount of information Visibility to disparate data sources

Empower
Robust operations personnel
& Reliable with actionable views of
Compatibility with Legacy system
Consistent enterprise-wide Clutter
information
free and intuitive
Limited screen size Built-in diagnostics and Status
Enabling engineering breakthroughs
IT & Infrastructure
Engineering
Issue: Needs:
Save valuable engineering time
Customization
Enable engineers to build intuitive, reliabledevelopment
Collaborative and maintainable
Amount of Scripting Reduce implementation errors
Maintaining many applications for operations
Adv. Graphics tools and reusability
applications Standardization, Secure & intuitive
Operations
Enabling IT breakthroughs
IT & Infrastructure
Issue: Needs:
Central Management Integrate with other IT apps

Make it much easier, less time-consuming
Extensibility
and less
Newer Technology costly
- .NET etc.do
Diagnostics this
Common tools, Application Integration
Large scale deployment High Availability, Security Patch Mgmt
Scalability on multiple dimensions
Engineering
Operations
Enabling interoperability breakthroughs
ERP Needs:
Device, Application, Enterprise Integration
(SAP, Oracle,
Microsoft..) Architecture Flexibility
Scalability
IT & Infrastructure Data Access,
Clients
Database
Applications Capability
Standardization
Asset
Management
Engineering Independent of hardware
Common Configuration
Engineering Reusability
Common platform for

Operations HMI, Supervisory,
LIM Systems SCADA, MES, EMI Apps.
Devices
The power of a single platform
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
The Good Old Days…
The 1990’s
Operator Operators:
► Immediate access to real-time
information
HMI ► Close to the process to do
Displays
something about it…
Rest of business:
PLC’s ► Run on paper (latency)…
Machines
Today…
Businesses are run so much faster
The 1990’s The 2000’s
Operator Plant Roles
Operations Engineering Maintenance Plant Mgt
HMI Displays Info Displays
Trends Web Based

HMI KPI Dashboards
Reports
PLC’s Data Sources
Maintenance
PLC’s Databases Planning Systems Lab Systems Applications
Machines Plant Assets
Machines Lines
Sites
Industrial information systems
The traditional-way 1 (Layers)
Production managers
Business Level – Plant Management and Scheduling –need
Levelaccess
4 to
information from both
Interface systems.
Demanding interface. Production Supervision – Level 3
High degree of real-time Equipment model
collaboration. Interface
must be defined at
Process Supervision – Level 2 both levels.
Operators need Interface
access to information
from both systems. Direct Control – Level 1
Interface
Manufacturing Process – Level 0

Down Time Analysis
Recipe Management
Industrial information systems
The traditional-way 2 (Silos)
Product Genealogy Manufacturing Process

Data Acquisition
ERP
Batch
Quality Control and SPC
Predictive Maintenance
Supervisory Control
Duplicated services and complex
integration
Wonderware:
Collapsing the Purdue model
Business Level – Management and Scheduling – Level 4
Interface
Production Supervision – Level 3
Wonderware System Platform Interface

for Production & Process Supervision
Process Supervision – Level 2
Interface
Direct Control – Level 1
Interface
Industrial Process – Level 0

Wonderware System Platform
System Platform Services
Not a Server, but a Provider of Services…
PDA
Tablets Browser
Panels
Terminal
Services
Device Integration Scripting

HMI Alarming .Net Framework
Historization Visualization
Trending SPC/SQC
Event Logging Telephonic Notification
Security Reporting
Redundancy Data Mining Phone
Configuration Management Downtime/OEE Pager
Software Deployment Statistical Analysis
Revision Control Business System Integration
Facility Model Deployment Model
Wonderware Software Solutions
One development environment,
One repository
InTouch
ERP
Terminal Services Web
/ PDA
InTouch
Terminal Services
/ Web
MES/P&PM
Application
Common Wonderware Server &
Development Studio Modules
HMI/Supervisory InTouch Historian
for Sys. Platform
InTouch
Common Bundled TPC
Repository for All
Managed Applications Plant Floor
Wonderware Compact
Panels
One System Platform Environment for all applications
Work Station Work Station

Work Station
Work Station
Work Station
Work Station
System Platform:
Value and benefits
Standards
Integration
Flexibility &
Changeability
Operational and financial benefits
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
The benefits of using the Wonderware System
Platform
Planned Project Start
Completion
Project Start Go Live Change in Go Live
Contribution/ requirements
Value
Traditional System
Change
Requests
Faster
0$ Payback Faster
Hardware Time
Time-to-Market Software
Design
Engineering
TCO
Commission ROI
Change Orders
Investment/
Lower Optimize & Maintain
Cost
Time-to-Market Payback Optimization &Time-to-Market Cash Flow Value
Operational
Maintenance Significantly
Easier adoption
Contribution/
Value Cost lower cost and
of change
WW System Platform
Increased Return less time

= Increased ROI
Change Reduced Investment
Requests
0$ Better
Cash Flow Hardware Time
Software
Design
Build & Deploy
Commission
Change Orders
Optimize & Maintain
Investment/ Operational Value
Cost Re-use and Acc. Cash Flow with WW
extend Acc. Cash Flow Traditional Sys.
Using skilled A2 certified SI
But, is this really true?
• Faster Time-to-Market
• Better Cash Flow
• Faster Payback
• Lower TCO
TCO
• Increased ROI ROI
Time-to-Market Payback Time-to-Market Cash Flow
Let us take a look at what some of our customers are
saying.
Customers can attest to the benefits of using
the Wonderware System Platform
 Shorten the construction period

 Raise our total profits for our company
 Expand our SCADA system as the
pipeline grows
 Shorten time to completion and remain
flexible to operation’s changing needs
What is the value of “Faster time to Market”?
Deming Cycle for Continual Improvement
• Plan: Identify an opportunity and plan

for change.
• Do: Implement the change on a small
scale.
• Check: Use data to analyze the results
of the change and determine whether it
made a difference.
• Act: If the change was successful,
implement it on a wider scale and
continuously assess your results. If the
change did not work, begin the cycle
again.
Source: American Society for Quality
http://www.asq.org/learn-about-quality/continuous-improvement/overview/overview.html
Deming Cycle for Continual Improvement
PLAN DO CHECK ACT

Continual improvement with the Wonderware
System Platform
Contribution/
Value
Contribution/
Value
PLAN DO CHECK ACT
Traditional System
0$
Time
Investment/
Cost
Contribution/
Value
WW System
Platform
0$
Time
Investment/
Cost
Information system evolution
Traditional Small Project Traditional Large Project
Low risk Higher risk

Low initial cost High initial cost
Short implementation time Long implementation time
Difficult to functionally extend Functionally complete
Difficult to scale Full scale implementation
What if
we were able to start small
and grow to the size we need,
when we need it?
… but there is traditionally a problem with the
platform
Small system platform
Scale and Large system platform
functionality
of the Wonderware system platform
system
It is impossible to get from
here to there without replacing the
underlying platform
Investment in
the system
Increasing the number of sites
Cost
$ Value
Number of
sites
Application examples
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
End User – Success Story:
HMI Extension applying SYSTEM PLATFORM
FOOD & BEVERAGE: New infant formula
facility
► REQUIREMENTS
▪ Traceability of products and material
▪ Increase production capacity and
support maintenance decisions
▪ Develop reusable standards to unify plant control
► GOALS
▪ Effective plant operations
▪ Fulfill traceability requirements
▪ Faster implementation of changes
► RESULTS
▪ Automated Traceability and reports
▪ Reduced cost of Ownership by Plant wide defined standard
functionalities by keeping the existing InTouch landscape
▪ Foundation for future cost effective ERP integration and MES
functionality
End User Success story: Connectivity, Datamangement and
Analyses applying SYSTEM PLATFORM
► REQUIREMENTS:
▪ Eliminate high scrapping rate
▪ Better Quality management
▪ Understand downtime on the process
► GOALS:
▪ Increase Profitability
▪ Ensure quality in automotive demands
► RESULTS
▪ Improved product quality and less scrap
▪ after only 3 weeks scrapping rate.
▪ Cost savings by increased and
more consistent product quality.
▪ Foundation for continous improvements
End User success story:
Provide information from multiple systems applying
System Platform
► REQUIREMENTS
▪ Connect with different suppliers
(six OEM’s with different HW/SW systems)
▪ Centralize monitoring and engineering development MELT SHOP PLANT
▪ Reuse project for other similar plants
► GOALS
▪ Reduce cost of engineering and monitoring DRI PLANT
▪ Streamline multi plant operations
► RESULTS
 Saved costs and optimized previous investment
 Implementation in 4 Month
 Opportunity for futher expansion without incurring major costs
and re-engineering efforts.
OEM Success story:
Performance Improvements applying
SYSTEM PLATFORM
► REQUIREMENTS
▪ Real time data management and analyses
▪ Downtime analyses and KPI generation
▪ Automated Production reporting
▪ Enabled integration with business system
► GOALS
▪ Higher competitiveness
▪ Increased revenue and Customer satisfaction
► RESULTS
▪ End User - Through downtime analysis customers can optimize
maintenance and improve performance integration with business
system possible when required.
▪ OEM Competitiveness and Customer Satisfaction
OEM Success story:
Reusability & Standardization applying
SYSTEM PLATFORM
► REQUIREMENTS
▪ More functionalities in addition
to SCADA (Data collection,Downtime,
Performance, Quality…..)
▪ Standardization
► RESULTS
▪ Increased the presence and reliability on the market.
▪ Reduced time and installation cost.
Requirements of SI for GEO SCADA project: :
Reduce drammatically develop and implementation
effort appliyng SYSTEM PLATFORM
Real Time Condition Monitoring
► REQUIREMENTS
▪ Visibility of assets performance in real time
▪ Reduce deployment and maintenance engineers
Requirements of SI for GEO SCADA project: :
Reduce drammatically develop and implementation
effort appliyng SYSTEM PLATFORM
Real Time Condition Monitoring
► REQUIREMENTS
▪ Visibility of assets performance in real time
▪ Reduce deployment and maintenance engineers
► RESULTS
▪ Sytem Platform greatly dramatically reduces application
development time and TCO (Total Cost of Ownership).
▪ The biggest single benefit is “transparency”, that is our supervisors
can see all equipment in the system and make manpower allocation
based upon complete and real time information
System Integrator Success story:
Reduce cost and effort applying
SYSTEM PLATFORM
► REQUIREMENTS
▪ Short time to market
▪ Automated supply-chain process
from ERP to Production (!)
► Goals of ST Powder
▪ Competitiveness Customer satisfaction by rapid
response to customer orders in small lots
▪ Profitability by highly automated workflow
► RESULTS
 5 months for successful delivery, starting from Green-Field (MES solution)
 Reduced risk and competitiveness for System Integrators enabling their Customers to gain Value
and a secure investment
Protecting your investment
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Protecting your investment
► Your largest investment is in engineering
and customization.
► Broken upgrade paths creates costs far
beyond the cost of software.
► A broken upgrade path creates a barrier for
change – the system becomes stale.
► The underlying system should enable you
to leverage new hardware and software
without having to re-create the solution.
Technologies change
Win 2.0
1987 Win 3.0 WfW 3.1 WfW 3.11 Win 95 Win 98 Win Me
Clients
1990 1992 1993 1995 1998 2000
Win XP Vista
2001 2006/7
NT 3.1 NT 3.5 NT 3.51 NT 4 Win 2000

1993 1994 1995 1996 2000
Servers
Serv, 2003 2003 R2

2003 2005/6
80386 Intel486 Pentium Pentium Pentium Pentium

Pentium II Pentium 4 Pentium D
1985 1989 1993 Pro III M
1997 2000 2005
1995 1999 2003
Intel Core
2006
Hardware
Intel
Core 2
2006
Multi-core
Source: Wikipedia.org
Applications are preserved
InTouch and
InTouch the FactorySuite
System
Platform
Application
Protect your engineering investment Server
- while -
leveraging the underlying technology.
Source: Wikipedia.org
Concepts and benefits
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
From tag-centric HMI to equipment
centric System Platform
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Evolution from tag-centric HMI to
equipment-centric System Platform
Oper. Interface
Oper. Interface
Windows Windows
Symbols & Faceplates Symbols & Faceplates Tag-based HMI
Navigation Scripts Navigation Scripts
Trends/Alarms, etc. Trends/Alarms, etc. Introduction of Remote
references
Oper. Interface
Windows Security Security

Symbols & Faceplates
Remote
Navigation Scripts references Tag server + Clients
Trends/Alarms, etc.
Tag server – issues
Security
Tag names PV SP – Solution:
Tags – Process Data
CV101
Scaling CLS
History Configuration
• Encapsulation in objects
OLS
Engineering Units Cmd • Derivation from templates
Event Configuration LS_Alarm
Alarm Configuration Timeout_Alarm
Access Name Link PV
CV102 $Valve
I/O Item names CLS
Application Scripts OLS
Data Change Scripts Cmd
Scripts
Condition Scripts LS_Alarm

Window Scripts Timeout_Alarm
SQL Access, Files, etc.
PV
Equipment type is
Other Supervisory Logic CV103
CLS
defined by object
Alarm Groups
templates
Appl.
Access Names OLS

Derived from InTouch
Security & Users Cmd
application templates
Process Data History LS_Alarm
History
Timeout_Alarm
Alarm History
Event History Equipment is
represented by object
instances
Benefits:
• Simplified application management through
development of reusable standard objects.
• Re-use of object specifications.
• Re-use of object code and configuration.
• Re-use of object testing and validation.
Equipment Centric Objects
Text & Email Alerts

Inputs/Outputs Graphic Symbols/Faceplates
Logic/Scripting
Maintenance Systems
Asset Performance Alarms & Events

• Downtime
• Productivity
• OEE
Operational Discipline
• Track & Trace
• Work Orders Historical Information Security
• Inventory
Assemble multiple pieces of equipment into a
process unit
Extend the equipment with functionality
Increase efficiency
Decrease
variance
Increase discipline
Increase agility
Create, evolve and enforce standards through
multi-level derivation
Changes to template automatically propagate to instances
New templates can be derived from existing templates
Libraries of standard objects can be developed
Standard templates decrease project-to-project costs BK101
This object is a template

for other objects
BK102
$BrewKettleTypeA
BK103
$GenericBrewKettle
$BrewKettleTypeB
BK104
Create, evolve and enforce standards through
multi-level derivation
Benefits:
• Simpler and faster implementation of
changes throughout the application.
• One global name space

• Security at data level
• Thin presentation layer
Process Data History SP – Solution:
History
CV101
Alarm History
Event History • Encapsulation in objects
• Derivation from templates
CV102
CV103
One global and secure name

space for all process data.
SP – Solution:
Process Data History
History
Alarm History CV101 • Drag and drop

Event History
CV103 CV102
Easy creation of object

instances using “drag and drop” from
templates
Benefits:
• The solution can be assembled from
re-usable components.
• Significant reduction in project
implementation time once a base
library has been created.
SP – Solution:
Process Data History
History
Alarm History • Drag and drop

Event History
• Plant model
A plant model can be created to logically

organize the plant equipment
Operator Operator Operator Operator Development Development SP – Solution:
Station Station Station Station Station Station
• Drag and drop
• Plant model
• Centralized Management
• Multi-user development
Historian Automation Automation Automation Galaxy
– Object Server Object Server Object Server Repository • Scalable deployment
InSQL – – – –
AOS001 AOS002 AOS003 GRNode • Robust IT topology
Objects can be deployed in a scalable and

robust IT topology
Benefits:
• Develop and maintain a multi-node system as
one single application.
• Centralized management and local execution.
• Quick deployment of objects to their designated
node.
Standards that enable continual
improvement
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
The power of propagating standards
Wonderware Extended with
base product Wonderware
best practices
-
QuickStarts Extended with
SI & OEM Extended with
solutions end-customer
best practices
- Extended with
Corporate plant level best
standards practices
-
Plant level
standards
Runtime Runtime Runtime

instance instance instance
- - -
Inheriting all the Inheriting all the Inheriting all the
standards standards standards
The power of propagating standards
Benefits:
• Align your organization with your
corporate initiatives
• Create consistency and discipline
• Enable continual improvement through
change propagation
• Develop once and use many times
• Faster implmentation with reduced risk
Information in the context of the plant
model
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
The Power of Wonderware’s Integrated Production
Golden Batch
and Process History

Quality issue with beer
produced from batch
WBB-3172166
Changes to the
temperature set
point
Roasting Mashing Brewing Fermenting Storing Bottling

Alarm!
Roasting Mashing
The Power of WW’s Integrated Production
and Process History
Using the plant model to link ISA-95
Production Performance to process data
Production
Performance
Process
alarms
1..n
May correspond
Product
Production
to a Production
Rule Response
Process
Process
Corresponds
to a
1..n
Segment
events
Segment Response
Process
0..n
Production
0..n
Personnel Equipment
0..n 0..n
Produced
0..n
Consumed
0..n
Consumabl
history
Data Actual Actual Actual Actual e Actual
Device integration
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
I am doing device integration with InTouch
Tags- why would I want to change?
► Tag based integration is often hardware
dependent.
► Tag based integration complicates the creation of
corporate standards.
► Tag based integration is time consuming to
implement and hard to commission.
► Changing a tag based system is labor intensive.
Traditional Versus
ArchestrA Device Integration
ArchestrA Approach
Traditional Approach - Objects, Structured Name Space, managed
- Tags, Flat Name Space, managed globally, brings manageability and cost savings
individually, repetitive
SL DDE Communications Definition
Device Integration Object NODE and Application
SL DDE Communications Definition Topic(s)
Node
Application Access Name Item
Topic Alias Table
(Atribute.Item1)
Item Item Name (Attribute.Item2)
(---)
OPC Communications Definition OPC Communications Definition
Node Device Integration Object NODE and Application
Server Access Name
Scan Group ScanGroups(s), BlockRead, BlockWrites
Item Item Name Item

Alias Table
(Atribute.Item1)
(Attribute.Item2)
(---)
IO binding via galaxy model
Optional alias list: WinPlatform
B3:1/5 Tank041.Mixer.VFD.Start
B3:1/6 Tank041.Mixer.VFD.Stop
N7:11 Tank041.Mixer.VFD.Speed
SL/DDE OPC AppEngine

AppObject
DIO DIO
•Tank041
•Mixer
Area •VFD
•Start
•Stop
•Speed
•Tank041 •Level
•Mixer
•VFD
AppObject
•Start
•Stop
•Speed
•Level MxReference(Example)
DIOName.ScanGroup.Program.Symbol.Element
DASABCIP.TankPLC.Tank041.Mixer.VFD.Start
Benefits of Wonderware device
integration
► Create and utilize structures that allow
reuse – benefit from structures that already
exist in the PLC.
► Aliases can make one PLC type look like
another.
► Create standards for common SCADA and
HMI applications independent of PLC type.
► Abstract the application from the PLC code
with common naming conventions –
provides flexible implementation.
Software integration
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Device Integration Concepts for System
Platform
InTouch HMI Historian
Wonderware
Functional Modules
and other Products Information Server Portal
IAS IO Namespace
and Common
Application Services
• Application Objects
• Device Integration Objects
Device Integration Servers

Third Party Applications -OPC Servers
-IO Servers
-DA Servers
IO binding via Galaxy Model
Optional alias list: WinPlatform
B3:1/5 Tank041.Mixer.VFD.Start
B3:1/6 Tank041.Mixer.VFD.Stop
N7:11 Tank041.Mixer.VFD.Speed
SL/DDE OPC AppEngine

AppObject
DIO DIO
•Tank041
•Mixer
Area •VFD
•Start
•Stop
•Speed
•Tank041 •Level
•Mixer
•VFD
AppObject
•Start
•Stop
•Speed
•Level
Information management
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Manufacturing intelligence is vital in…
► Process troubleshooting
► Optimizing plant performance
► Responding to market opportunities
► Regulatory compliance
► Establishing best practices

Take better, proactive decisions ….
Information - VISUALIZATION
OPERATORS ENGINEERS MANAGEMENT
Real-time Processes
Today’s challenges
► Collect real-time data from disparate plant
floor devices & systems
▪ One version of the truth
► Easily create & publish Manufacturing
Intelligence content
▪ Configuration versus coding
► Simplify troubleshooting & process
improvement efforts
▪ Accelerate results
► Deliver Manufacturing Intelligence via the web
▪ Best return on information
Configuration and storage
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
We want to simplify…
System Configuration
• Centralized management
• Intelligent Data Objects
• Standardized Graphical Objects
Troubleshooting & Process

Analysis
• Drill down Data Tables & Displays
• Dashboards
• Production Reporting
Delivery of Information
• Web-based Systems
• Configuration vs Coding
Automatic historian configuration
Operator Operator Operator Operator Development Development History configuration is
managed in the objects or
their templates.
The configuration is
deployed together with
the objects.
The objects automatically
configure the historian
when they are deployed.
Historical data is pushed
from the objects to the
historian.

– Object Server Object Server Object Server Repository
InSQL – – – –
AOS001 AOS002 AOS003 GRNode
Objects automatically configure the historian

and are responsible for data delivery
Automatic historian configuration
Benefit:
• Easy to configure and maintain.
• Reliable data delivery.
Standardized graphical objects
► Build once and use

everywhere
▪ Lower engineering costs
▪ Facilitates standards &
best practices
► Configure not code
▪ Linked to plant model
▪ Parameters passed at
runtime
► Accelerates Application
Development
Quick Assembly into KPI Dashboards
►Assemble graphical
objects to quickly build
KPI dashboards
►Easily link Graphical
Objects to Intelligent
Data Objects (KPI data
source)
►Track metrics across
all lines & equipment
►Useful in Web-based
applications or HMI
systems
Troubleshooting and analysis
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future

Analysis
• Dashboards
Drill Down Data Tables & Displays
Linked Data Tables and

Associated Displays allow a
broad range of data mining
opportunities
Dashboards – Operator
Dashboards – Production Manager
Simplifying Production Reporting
► Real-time & Historical
► Ad Hoc or Scheduled
► Leveraging of
Microsoft Technology
▪ MS Reporting Services
▪ Excel
► Extensible Reports
▪ Pre-configured
▪ Process Data
▪ Downtime
▪ Production Events
▪ More…
Powerful, Data Retrieval Modes
Optimize retrieval of continuous data from Historian
► “Best fit” for better trending

► Time-weighted average
► Integral (for rates)
► Slope (Rate-of-change)
► Counter
► Minimum/Maximum
► Interpolated
► Time-in-state
Helps generate more powerful data queries with less effort

• Faster results
• Helps reduce demand for scarce Plant IT resources
Example: Time-In-State: Pump Status
100%
1
Delta
0 Percent “On”
0%
Motor
Transforming Data into Information:
Rate  Quantity Using Integral Retrieval
Liters / Minute
Liters (linear)
Interpolation Mode
Raw data
Most analog
measurements
Setpoints,
analyzers, etc.
► Used as default setting on a trend

► Also used in integral & time-weighted average modes
Averages
Statistical Average
Second
s
Value  i 1 n
Xi
2 50.0 n
51 25.0
Time Weighted
4 50.0 Average

3 75.0
i 1 n
Xi  Ti
Average: 50.0 30.0
 T
Time-Weighted Average Data Retrieval
Calculate
midpoint Average using
“stair-step”
Average using
linear
► Much more efficient

► Uses tag’s interpolation mode
“Best Fit” Retrieval Improves Accuracy &
Performance
1-Week of 5-sec. data: 120,960 (delta) vs. ~300 (best fit)
Delta
Cyclic
New “Best Fit”
No gap indicated
Adds detail with more subintervals or smaller time periods

Delivery of information
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future

Analysis
• Dashboards
Web Information Delivery
Advantages
▪ Broad scalability (content & users)
▪ Role-based content
▪ Timely data availability (24/7)
▪ Cost effective licensing (concurrent)
▪ High user acceptance
Disadvantages
▪ Custom development (not always)
▪ Security concerns
▪ Site maintenance
Today’s Web Solutions…
Simpler to Implement & Maintain
► Designed for engineers
not programmers
▪ Configuration not coding
► New web technology
▪ Microsoft SharePoint
▪ Easy to customize with
Web Parts
► Faster deployments
▪ Days vs Months
► Focus on Content not
infrastructure
▪ HMI, Historian, Data
Analysis Applications
Example of “Assembled” Web Page
Web Based Manufacturing Intelligence
Content
► HMI Graphics
► HMI Reports
► Process Trends
► Drill-down Production Reports
► Production Totals & Events
► Equipment Downtime Data
► Real-time Statistical Process
Control Data
► Performance Dashboards
Functional and technical capabilities
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
The value of evolving your InTouch
application
Plant model
ArchestrA provides
symbols structure
= modular applications
Scalable
Automatic
Development and extensible
runtime
application qualitysystem
management information
Enables
.Net
Check in &corporate
Container
check outstandards
enables extensibility
WindowMaker Project OneView
platform
Symbol log for all information
library is included
Localized alarm viewerChange
Deployed & managed
Published
Transportable runtime
runtime applications
applications
Improved multi-monitor support packages
Vista, XP and 2003Published runtime applications
Server Support
Independent runtime application
InTouch 10 demo
Multi-developer environment
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Multi-developer configuration tools
Operator Operator Operator Operator Development Development All Configuration
Information is stored in a
central database.
The Engineering Stations
Request actions to be
performed by the Galaxy
Repository.
Objects that are being
edited are checked out to
the user performing the
operation.

– Object Server Object Server Object Server Repository
InSQL – – – –
AOS001 AOS002 AOS003 GRNode
Multi-developer configuration tools
Benefit:
• Project implementation time can be
reduced by having multiple
developers work in parallel.
• Better utilization of resources with
specific domain knowledge.
Collaborative development environment
► Roles determine what users
can do
► Checked out objects can be
modified externally and
checked back in with
changes
► Objects can be saved
without being checked in to
avoid deployment before the
objects are complete
► Check ins\Check outs are
tracked and can be
commented
Audit trail
Audit trail
Benefit:
• The Collaborative development
environment can control access to
the system and record development
activities.
System scalability
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Deployment scalability
Scale down for off-line

hosting and system
maintenance
Automation Object Integrated

Server Only Single Node Distributed
Peer to Peer
Single Server
Multi Client
Distributed Multi Server

Multi Client
Setting new standards in scalability
► Objective:
▪ Enable customers the freedom to grow
400 Clients
1 Million I/O
500 Nodes
Smallest System
1 Node
250 I/O license
Setting new standards in scalability
Benefits:
• Suitable for systems of all sizes:
• investments in training and development of
standard components can be utilized in all
systems.
System expansion and redistribution of loads
Operator Operator Operator Operator Development Development
Historian Automation Automation Automation Automation

Galaxy
More
– Object Server Object Server Object Server Object
Repository
Server
InSQL – –
computing
– –
AOS001 AOS002 power
AOS003 GRNode
AOS004
needed!
System expansion and redistribution of loads
Benefits:
• The system can scale as needed
without replacing existing hardware.
• Functionality can be redistributed
without application or client
reconfiguration.
Network scalability
► The ability to communicate, anywhere
▪ Optimize PLC communications
▪ Optimize to deliver only information needed
► Benefits:
▪ Regardless of communications technology,
your system operates predictably
Flexible, Enhanced Communications
► InTouch-like response
▪ Faster response to HMI, improved operator
experience
► Failover optimization
▪ System stability enhanced during critical periods
▪ Faster failover to standby systems when needed
► Backwards compatible and configurable
► Reduce network loads
▪ Between I/O Sources and Engines
▪ Between System Platform and visualization
clients
Enhanced Communications
Active InTouch Inactive
• in opened window • WViewer minimized
• in script • Window closed
• in trend
• alarmed Reduced load
• historized on DI Object
DI Object
Reduced
Network
App Object 1 App Object 2 load
Reduced Reduced
Network Network
load Reduce CPU Load &
load
DA server CPU usage
DA Server
Reduced
PLC Network load
SCADA Optimization
► Networking and Communications
infrastructure enables support for SCADA
architectures
▪ Typically these are geographically distributed
• Intermittent and slow networks are common
▪ Timestamp propagation is required
• System Platform supports this (3.1 enhancements)
• Delays in data delivery do not affect event timestamps
► Benefits
▪ Highly scalable systems can be built both from
I/O and geographic perspectives
Full timestamp propagation
Historian
Device Application
PLC Integration objects
InTouch
Secure runtime environment
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Powerful and easy to manage runtime
security model
Security can be defined down
OS User to the object attribute level.
Many The permission requirements
Many can be set for each of the
Role attributes. This can be done at
the object template level.
1
Many Object instances with the same
Operational Many access characteristics, are
Permissions grouped in Security Groups.
Many Roles can be given operational
1 permissions for each of the
Security Group Security Groups.
1 Users can have multiple Roles.
Many
OS User based authentication
Object PV allows user administration to
1 CLS be moved to the OS.
Many OLS
OS Group based authentication
Cmd
Attribute allows user groups (roles) to be
LS_Alarm
Many Timeout_Alarm
administered from the OS.
1
Permission
Requirement Many
Centrally managed and locally stored
runtime security model
Operator Operator Operator Operator Development Development Runtime Security Model
OS User is managed centrally.
Many Galaxy Membership
Many invitations can only be
Role sent from Galaxy
Repository.
1
Many Only Galaxy members get
Operational Many access to real time data in
Permissions the Galaxy.
Many Runtime Security Model
1 O
S
M
n
a
U
s
e
ar
M
yR
n
is stored in Global Cache
yo
1 l
Me
a
and distributed to all

nO M
yp a
Security Group
n
e y
M
r
aa
1
nt
yiS
e
1oc
n
M u
a
ar
l
nOi
ybt
1P
Galaxy Members
jy
Mee
arcG
nm trA
yiot
Mst
u
1spr
a
nii
yo b
P
nu
Historian 1
e M
rst a
e
m n
i y
Automation Automation Automation Application Domain

s
s
i
o
n
R
e
Many
q
–
u
i
Object Object Object Definition Controller

r
e
m
e
n
t
InSQL
Object Server Server Server –
Galaxy
1 Repository
Many
Attribute
Many
Security1 is managed centrally and stored locally.
Permission
The GalaxyManyis protected by only allowing data
Requirement
access to Galaxy members.
Enforcement of runtime security
Operator Operator Operator Operator Development Development Login at Node 1. Operator
login independent of PC
login.
Login is verified by the
Global Cache or Domain
Controller as required by
the Security Model.
Node 1 local cache is
updated with the user
credentials.
Galaxy Repository reads
Node 1 local cache and
updates global cache.
Historian Automation Automation Automation Application Domain
– Object Object Object Definition Controller Subsequent logins can be
InSQL Server Server Server – performed against cache
Galaxy if DC or GR is not
Repository available.
Can be fully integrated with OS Security.

Operate write request
CloseCmd:
False
True
?Pending
Operator Operator Operator Operator Development Development User accesses CV101.
Write request and user
credentials are sent to
CV101.
CV101: Operate
permission required.
Object verifies the
credentials.
The write is performed,
logged in the event sub-
CV101
system and reported back
to the operator station.
Historian Automation Automation Automation Application Domain The Security Model is not
– Object Object Object Definition Controller dependent on the Galaxy
InSQL Server Server Server – Repository or Domain
Galaxy Controller.
Repository
Control Network
PLC PLC PLC

Unrivalled data level security protecting the
control hardware layer.
Secured write request
CloseCmd:
?Security
?Pending
False
True
Operator Operator Operator Operator Development Development User accesses CV101.
Write request and user
credentials are sent to
CV101.
CV101: Secured write
permissions required.
The user is requested to
re-enter the password.
The user credentials are
CV101 sent to CV101.
CV101 verifies the
credentials and performs
Historian Automation Automation Automation Application Domain write.
– Object Object Object Definition Controller
InSQL Server Server Server – Verified write is similar,
Galaxy but with two signatures.
Repository
PLC PLC PLC

Unrivalled data level security protecting the
control hardware layer.
Secured write request
Benefits:
• Easily configure and maintain the runtime
security model.
• Robust security scheme enforced at the
object attribute level.
• Security system with no single point of
failure.
High availability
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
High availability: a system-wide issue
Thin Clients ` ` `
PC Workstations
Client Layer Mobile
High Availability
Development
TS - Visualization
Application Layer Data Storage

High Availability High Availability
Automation Config History/Alarms
Servers
Device Integration
High Availability
Application layer availability
Non-redundant system
1. The server handles all data.
2. If the server is lost then the Client Server Architecture
clients lose connection to InTouch InTouch InTouch InTouch Historian
data.
• InTouch
• InSQL
• Other AOS Nodes
Redundant System
1. Redundant servers maintain
synchronized data through AOS
dedicated network.
2. If the primary server is lost the
backup server will take over PLC
where the primary left off. The
switch is transparent to the
clients.
3. Configuration is done through
a check box on the
AppEngine.
System platform redundancy -
Terminology
► During Configuration
▪ Primary Engine LAN
▪ Backup Engine
► During Runtime
▪ Active Engine Primary Backup
▪ Standby Engine Active Standby
► RMC RMC
▪ Redundant Message Channel AE1 AE1_Bck
▪ Dedicated Network for Platform1 Platform2
Information Exchange and
Status Check AOS001 AOS002
Engines refer to each other as

Partners
Automatic synchronization
1. Deployed Objects
and Configuration
2. Current Data Primary
(Checkpoint)
3. History Store and
Forward Blocks
(when historian
connection lost)
RMC
4. Alarm states and
times (no duplicates)
5. Engine status
Active Standby
Architectural flexibility
1. Peer to Peer
Architecture
2. Each machine hosts a Primary
different AppEngine
and AppObjects.
3. Platforms can host AE1 AE2
more than one
AppEngine.
RMC
4. AE1 Backup is AE2
assigned to AE1
backup backup
Workstation 2.
5. AE2 Backup is
assigned to
Workstation 1. AOS001 AOS002
Redundancy configuration
► AppEngine
▪ Enable
Redundancy
▪ Set up parameters
Benefit:
• Easy to configure redundancy, based
on standard operating systems and
hardware.
High availability: a system-wide Issue
Thin Clients ` ` `
PC Workstations
Client Layer Mobile
High Availability
Development
TS - Visualization
Application Layer Data Storage

High Availability High Availability
Automation Config History/Alarms
Servers
Device Integration
High Availability
Field device connectivity
1. All Device References
Communications to the
field devices
are made also
toneeds
the
to be fault tolerant.
Redundant DI Object
AOS
2. Loss of the control PLC
network would cause the
server to lose connection PLC_ABCIP
to data. Redundant
3. The redundant DIDIObject
Object PLC_DHPLUS
will allow
communications through
a standby network if the
primary is lost.
4. A redundant DI Object will ABCIP ABDH+
allow ApplicationObjects
PLC
to subscribe to a single
object that in turn can RDI Failover optimization:
DA Server_1
retrieve data fromDAeither
Server_2
a
primary or backup DI •RDI subscribes items at both primary and backup
ABCIP
Object. ABDH+ servers
•RDI Scan mode does not need configuration. It
assumes the scan mode of the DI object it is connected
to
•Enhanced Network Communication mode will improve
failover reconnection response
Wonderware System
Platform

capabilities

System Platform

Operational and
the plant model

Protecting your
future
Example system diagram
TSE Clients
Galaxy Analysis and

Repository Visualization Trending Terminal Server
Development Station Nodes (ActiveFactory)
Application Historian Information

Object Server Server Server
Ordering System Platform
Step 1: System Platform- Select the appropriate
Galaxy IO with History level for the System Platform.
Step 2: System Platform Options-Additional

Platforms, Historians, DA Servers
Step 3: Select Modules
Step 4: Wonderware Client Parts Choose One or

More
Step 5:….Select Customer Support

Order Wonderware Clients
► InTouch for System Platform Visualization Client

▪ With Trending
▪ Without Trending
▪ Read-only
► Web Information Client

▪ Information Server v3.0 Advanced Reporting and
Analysis Client License
► Reporting and Analysis Client

▪ ActiveFactory 9.2- Trend, Excel, Reports
License Packaging Overview
► System Platform
▪ Platforms –Distribution per PC
▪ I/O
► Modules
▪ Equipment based
► Traditional InTouch
▪ Tags
► Wonderware Clients
▪ Per Seat , Named User , Concurrent Server
Levels of Wonderware software license
management and enforcement
1) EULA stating software use (paper)
2) License certificate for individual products
(paper)
3) Local and Server/Network-based License
Manager (Soft License) enabled by License File
4) Paper License (CALs, TSE,)
5) USB Keys containing unique serial numbers to
lock soft license (Dongle)
All software is Soft License Protected
USB Keys are required in certain countries and also
available for any Distributor to use at their discretion
Wonderware Licensing Progression
1989 1999 2002 2007

Life Cycle of a License File
License
Certificate
EULA
► End User License Agreement (EULA)

► References License Certificate and Order
► Click-wrap – View and accept upon install
of software
► Hard copy booklet included with Product
CDs is replaced by EULA .pdf file burned
onto License mini CDs
License certificate
► Shipped with every order
► Key Detailed Licensing information
► Foil on paper, like some International currencies
► Legal licensing extension of EULA
► Very important for customer to keep.
Licensing Types
► Local Device
▪ Independent Local (on same device as product
software enables one product)
▪ Per Device local (on same device as product software
enables one product on only that device)
► Served License
▪ Per Named Device (on Server as product software
enables one product on only that device)
▪ Per Named User Server (on Server as product
software enables one product on only that User)
▪ TSE
▪ Per Server/Concurrent
End of presentation
Wonderware System
Platform

capabilities
What can Wonderware From tag-centric HMI to Wonderware Historian InTouch visualization
do for you? equipment-centric
System Platform
The power of a single Wonderware Multi-developer

platform Standards that enable Information Server environment
Operational and Wonderware

System scalability
financial benefits Information in context of Information Clients
the plant model
Protecting your Secure runtime

investment: environment
From the past to the
future
High availability
Thank you
www.wonderware.com

The Wonderware System

Загружено:

Сведения о документе

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

The Wonderware System

Загружено:

Авторское право:

Доступные форматы

Wonderware’s System Platform

Functional and technical

What can Wonderware From tag-centric HMI to Configuration and

The power of a single Troubleshooting and Multi-developer

Application Examples Secure runtime

Functional and technical

What can Wonderware From tag-centric HMI to Configuration and

The power of a single Troubleshooting and Multi-developer

Application Examples Secure runtime

Functional and technical

What can Wonderware From tag-centric HMI to Configuration and

The power of a single Troubleshooting and Multi-developer

Application Examples Secure runtime

Empowering All Roles in the Plant

LIM Systems Microsoft Technology & Industry Standards

Amount of information Visibility to disparate data sources

Central Management Integrate with other IT apps

Common platform for

Functional and technical

What can Wonderware From tag-centric HMI to Configuration and

The power of a single Troubleshooting and Multi-developer

Application Examples Secure runtime

Operations Engineering Maintenance Plant Mgt

HMI Displays Info Displays

Trends Web Based

PLC’s Data Sources

Manufacturing Process – Level 0

Product Genealogy Manufacturing Process

Business Level – Management and Scheduling – Level 4

Production Supervision – Level 3

Wonderware System Platform Interface

Process Supervision – Level 2

Direct Control – Level 1

Industrial Process – Level 0

Device Integration Scripting

Work Station Work Station

Functional and technical

What can Wonderware From tag-centric HMI to Configuration and

The power of a single Troubleshooting and Multi-developer

Application Examples Secure runtime

Increased Return less time

 Shorten the construction period

• Plan: Identify an opportunity and plan

PLAN DO CHECK ACT

Low risk Higher risk

Functional and technical

What can Wonderware From tag-centric HMI to Configuration and

The power of a single Troubleshooting and Multi-developer

Application Examples Secure runtime

▪ Reuse project for other similar plants

▪ Streamline multi plant operations

Functional and technical

What can Wonderware From tag-centric HMI to Configuration and

The power of a single Troubleshooting and Multi-developer

Application Examples Secure runtime

1990 1992 1993 1995 1998 2000

NT 3.1 NT 3.5 NT 3.51 NT 4 Win 2000

Serv, 2003 2003 R2

80386 Intel486 Pentium Pentium Pentium Pentium

leveraging the underlying technology.

Functional and technical

What can Wonderware From tag-centric HMI to Configuration and

The power of a single Troubleshooting and Multi-developer

Application Examples Secure runtime