Wonderware System Platform

“Software Solutions for Real-Time Success”

Terence TanGeneral 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

11

Wonderware Software SolutionsWonderware Software Solutions

Devices(Barcode Scanner, PLCs, DCS, AB, Siemens, Omron, etc…)

ERP

InBatchInBatch

Batch Mgmt SystemBatch Mgmt System

MESMES MES MES Operations/PerformanceOperations/Performance

IO ServersIO Servers

ConnectivityConnectivity

InControlInControl

Soft Logic ControllersSoft Logic Controllers

WebWeb InfoInfo

ServerServer

Internet PublishingInternet Publishing

HMI/SCADAHMI/SCADA

InTouchInTouch

RT SPC/SQCRT SPC/SQC

Plant HistorianIndustrialSQLIndustrialSQLServerServer

ActiveFactoryActiveFactory

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

WHAT IF!!

SOFTWARE PLATFORMFOR

MANUFACTURING

TR

AC

EA

BIL

ITY

PR

OD

UC

TIO

NH

IST

OR

Y &

GE

NE

ALO

GY

OE

E &

D

OW

NT

IME

AN

ALY

SIS

SC

AD

AC

ON

TR

OL

& M

ON

ITO

RIN

G

ALA

RM

S &

EV

EN

TS

QU

ALI

TY

M

OD

ULE

ER

P

CO

NN

EC

TIV

ITIE

S

ERP(SAP / ORACLE / etc)

IMAGINE!!

SOFTWARE PLATFORMFOR

MANUFACTURING

TR

AC

EA

BIL

ITY

PR

OD

UC

TIO

NH

IST

OR

Y &

GE

NE

ALO

GY

OE

E &

D

OW

NT

IME

AN

ALY

SIS

SC

AD

AC

ON

TR

OL

& M

ON

ITO

RIN

G

ALA

RM

S &

EV

EN

TS

QU

ALI

TY

M

OD

ULE

ER

P

CO

NN

EC

TIV

ITIE

S

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 PLATFORMFOR

MANUFACTURING

DATA CONNECTIVITIES(PLCs, DCS, Field Devices, Barcode Reader,Existing HMI, Existing Quality Systems, etc)

WONDERWARE HISTORIAN

(Production Database - Time-series data, Alarms &

Events)

WONDERWARE INFORMATION SERVER

(Web-based Reporting System)

WONDERWARE INDUSTRIAL

APPLICATIONSERVER

(Application Engine)

Wonderware System Platform

19

How are these Objects Used? (Control Environment)

$DiscreteDevice $Valve

CV101

CV201

CV301

CV401

This is a base Template that can be used to define

custom standards.

Here the template has been configured as a

Valve.

The $Valve Template has been used to create several instances

of the device.

20

How are these Objects Used? (IT Environment)

$UserDefinedObject $ReportObject

Dry_BatchReport_Start

Dry_BatchReport_Finish

Wet_BatchReport_Start

Wet_BatchReport_Finish

This is a base Template that can be used to define

custom standards.

Here the template has been configured as a

ReportObject.

The $ReportObject Template has been used to create several

instances of the Report.

Alarms and events

Graphic symbols

Faceplates

Inputs/Outputs

Logic/Scripting

Historical Information

Security

Equipment centric objects:Powerful and multi-faceted

Assemble multiple pieces of equipment into a process unit

$GenericBrewKettle

This object is a template for other objects

BK101

BK102

BK103

BK104

Create, evolve and enforce standards through multi-level derivation

$BrewKettleTypeB

$BrewKettleTypeA

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

Galaxy Repository

–GRNode

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

Automatic historian configuration

Objects automatically configure the historian and are responsible for data delivery

OperatorStation

OperatorStation

OperatorStation

OperatorStation

DevelopmentStation

DevelopmentStation

Evolution from tag-centric HMI to equipment-centric System Platform

CV101

CV102

CV103

Process Data History

Alarm History

Event History

History

SP – Solution:

• Encapsulation in objects

• Derivation from templates

• One global name space

• Security at data level

• Thin presentation layer

One global and secure name space for all process data.

CV103

Evolution from tag-centric HMI to equipment-centric System Platform

Easy creation of objectinstances using “drag and drop” from

templates

CV102

CV101

Process Data History

Alarm History

Event History

History

SP – Solution:

• Encapsulation in objects

• Derivation from templates

• One global name space

• Security at data level

• Thin presentation layer

• Drag and drop

Galaxy Repository

–GRNode

Automation Object Server

–AOS004

Historian –

InSQL

Automation Object Server

–AOS001

Automation Object Server

–AOS002

Automation Object Server

–AOS003

System expansion and redistribution of loadsOperatorStation

OperatorStation

OperatorStation

OperatorStation

DevelopmentStation

DevelopmentStation

More computing

power needed!

AOS

Application layer availability

AOS

InTouch InTouch InTouch InTouch Historian

Client Server Architecture

PLC

Non-redundant system

1. The server handles all data.

2. If the server is lost then the clients lose connection to data.

• InTouch• InSQL• Other AOS Nodes

Redundant System

1. Redundant servers maintain synchronized data through dedicated network.

2. If the primary server is lost the backup server will take over where the primary left off. The switch is transparent to the clients.

3. Configuration is done through a check box on the AppEngine.

Architectural flexibility

RMC

Primary

AOS001 AOS002

AE1AE1

AE1AE1backupbackup

AE2AE2

AE2AE2backupbackup

1. Peer to Peer Architecture

2. Each machine hosts a different AppEngine and AppObjects.

3. Platforms can host more than one AppEngine.

4. AE1 Backup is assigned to Workstation 2.

5. AE2 Backup is assigned to Workstation 1.

Software Solutions for Real-Time SuccessSM