Transcript Introducing the Industrial Application Server

Wonderware System Platform
“Software Solutions for Real-Time
Success”
Terence Tan
General Manager
Announcements
► New Release!! (End/March)
▪ InTouch 10.1
▪ System Platform 3.1
▪ Development Studio 3.1
▪ MES Performance 3.5
▪ MES Operations 3.5
▪ InBatch 9.0
▪ ArchestrA Object Toolkit 3.1
▪ Remote Response Objects 1.0
▪ Packaging Industry Pack
Announcements
► We moved to Damansara Intan E-Business
Park Jan/2009.
► Area: 2088 sq feet
▪ 1 Training Room (max 12 participants)
▪ 2 Meeting Room
Announcements
► Upcoming events:
▪ Full Product Training
• InTouch 10.1
• System Platform 3.1
• MES Operations & Performance
▪ Short Tech Seminars (FOC)
•
•
•
•
InTouch 10.1 Appreciation Training
InTouch 10.1 Hands-on Features Training
System Platform 3.1 Hands-on Features Training
InTouch – How To xxxxx
Invensys Wonderware
► Who is Invensys Wonderware?
Invensys Wonderware
 Establish in 1987
 Today – business unit of Invensys plc, FTSE-list
 Headquarters: Lake Forest, California
 4 Development Centers
 Asia-Pacific Office: Singapore, Australia, Japan,
Korea, China
 20 Distributor Offices in the Asia-Pacific
 600 + System Integrators worldwide
 350 + 3rd Party Product Providers
 More than 500,000 installations!
Invensys Business Groups
► Delivering leading brand solutions, from the
production line to the bottom line.
Our Customers and more…
Mega Steel
Wonderware’s Application Space
Wonderware Software Solutions
ActiveFactory
ERP
MES
InBatch
IndustrialSQL
Server
Web
Info
Server
InTouch
InControl
MES
Operations/Performance
IO Servers
Devices
(Barcode Scanner, PLCs, DCS, AB, Siemens, Omron, etc…)
Internet Publishing
Plant Historian
Batch Mgmt System
RT SPC/SQC
HMI/SCADA
Connectivity
Soft Logic Controllers
10
Software Integration
► In the OLD days, because of the available
“TECHNOLOGY”, Integration;
▪ Database connectivity
▪ Dynamic Library Link (DLL)
▪ Application Programming Interface (API)
▪ OPC (OLE for Process Control)
▪ Active-X Control, Active-X Exe, etc
Duplicated services and complex
integration
SOFTWARE PLATFORM
FOR
MANUFACTURING
ERP
CONNECTIVITIES
OEE &
DOWNTIME ANALYSIS
QUALITY
MODULE
PRODUCTION
HISTORY & GENEALOGY
TRACEABILITY
ALARMS & EVENTS
SCADA
CONTROL & MONITORING
WHAT IF!!
ERP
(SAP / ORACLE / etc)
SOFTWARE PLATFORM
FOR
MANUFACTURING
ERP
CONNECTIVITIES
OEE &
DOWNTIME ANALYSIS
QUALITY
MODULE
PRODUCTION
HISTORY & GENEALOGY
TRACEABILITY
ALARMS & EVENTS
SCADA
CONTROL & MONITORING
IMAGINE!!
ERP
(SAP / ORACLE / etc)
BENEFITS
► Project Successful Rate is HIGHER
► Shorter Development Time Frame
► Faster Time to Market
► Lower Investment Cost
► Project can be easily DUPLICATE to
promote Standardization
Wonderware System Platform
WONDERWARE SYSTEM PLATFORM
FOR
MANUFACTURING
WONDERWARE
INFORMATION SERVER
(Web-based Reporting
System)
WONDERWARE
HISTORIAN
(Production Database Time-series data, Alarms &
Events)
WONDERWARE
INDUSTRIAL
APPLICATION
SERVER
(Application Engine)
DATA CONNECTIVITIES
(PLCs, DCS, Field Devices, Barcode Reader,
Existing HMI, Existing Quality Systems, etc)
Wonderware System Platform
How are these Objects Used?
(Control Environment)
The $Valve Template has been
used to create several instances
of the device.
This is a base Template
that can be used to define
custom standards.
Here the template has
been configured as a
Valve.
CV101
CV201
$DiscreteDevice
$Valve
CV301
18
CV401
How are these Objects Used?
(IT Environment)
The $ReportObject Template has
been used to create several
instances of the Report.
This is a base Template
that can be used to define
custom standards.
Here the template has
been configured as a
ReportObject.
Dry_BatchReport_Start
Dry_BatchReport_Finish
$UserDefinedObject
$ReportObject
Wet_BatchReport_Start
19
Wet_BatchReport_Finish
Equipment centric objects:
Powerful and multi-faceted
Inputs/Outputs
Graphic symbols
Logic/Scripting
Faceplates
Historical Information
Alarms and events
Security
Assemble multiple pieces of equipment into a
process unit
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
This object is a template
for other objects
BK101
BK102
$BrewKettleTypeA
BK103
$GenericBrewKettle
$BrewKettleTypeB
BK104
Automatic historian configuration
Operator
Station
Operator
Station
Operator
Station
Operator
Station
Development Development
Station
Station
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.
Historian
–
InSQL
Automation
Object Server
–
AOS001
Automation
Object Server
–
AOS002
Automation
Object Server
–
AOS003
Galaxy
Repository
–
GRNode
Objects automatically configure the historian
and are responsible for data delivery
Evolution from tag-centric HMI to
equipment-centric System Platform
• One global name space
• Security at data level
History
Process Data History
Alarm History
Event History
CV101
• Thin presentation layer
SP – Solution:
• Encapsulation in objects
• Derivation from templates
CV102
CV103
One global and secure name
space for all process data.
Evolution from tag-centric HMI to
equipment-centric System Platform
SP – Solution:
• Encapsulation in objects
• Derivation from templates
• One global name space
• Security at data level
History
• Thin presentation layer
Process Data History
Alarm History
Event History
• Drag and drop
CV101
CV103
CV102
Easy creation of object
instances using “drag and drop” from
templates
System expansion and redistribution of loads
Operator
Station
Historian
–
InSQL
Operator
Station
Automation
Object Server
–
AOS001
Operator
Station
Automation
Object Server
–
AOS002
Operator
Station
Automation
More
Object Server
computing
–
power
AOS003
needed!
Development Development
Station
Station
Automation
Galaxy
Object
Repository
Server
––
GRNode
AOS004
Application layer availability
Non-redundant system
1.
The server handles all data.
2.
If the server is lost then the
clients lose connection to
data.
•
•
•
Client Server Architecture
InTouch
InTouch
InTouch
InTouch
InTouch
InSQL
Other AOS Nodes
Redundant System
1.
2.
3.
Redundant servers maintain
synchronized data through
dedicated network.
If the primary server is lost the
backup server will take over
where the primary left off. The
switch is transparent to the
clients.
Configuration is done through
a check box on the
AppEngine.
AOS
PLC
Historian
Architectural flexibility
1. Peer to Peer
Architecture
Primary
2. Each machine hosts a
different AppEngine
and AppObjects.
3. Platforms can host
more than one
AppEngine.
AE1
4. AE1 Backup is
assigned to
Workstation 2.
AE2
5. AE2 Backup is
assigned to
Workstation 1.
AE2
RMC
backup
AOS001
AE1
backup
AOS002
Software Solutions for Real-Time Success
SM