1. Wonderware System Platform “Software Solutions for Real-Time Success”
Terence Tan
General Manager
Title Slide: Operations Software 3.4
This short presentation highlights the value propositions, the benefits and some of the capabilities of Wonderware Operations Software version 3.4.
Operations Software version 3.4 uses “Factelligence” software technology obtained from the 2007 Cimnet acquisition.
Operations Software version 3.4 has been designed to better integrate with the Wonderware System Platform 3.0 and the exciting InTouch 10.0 HMI application.
(c) 2002 Invensys Systems, Inc.
21-Apr-17

2. 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

3. Announcements We moved to Damansara Intan E-Business Park Jan/2009.
Area: 2088 sq feet
1 Training Room (max 12 participants)
2 Meeting Room

4. 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

5. Invensys Wonderware
Who is Invensys Wonderware?

6. 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
rd Party Product Providers
More than 500,000 installations!

7. Invensys Business Groups
Delivering leading brand solutions, from the production line to the bottom line.

8. Our Customers and more…
Mega Steel

9. Wonderware’s Application Space
This slide shows where in the Automation Pyramid model FactorySuite fits and how it is positioned with respect to the ERP (business planning software) and the Control Level (control hardware). Wonderware develops shrink wrapped production software products and that’s all. We don’t do hardware, we don’t do integration, and we don’t do ERP software.
The Planning Software companies (SAP, Marcam, Baan, etc.) have grown up in the transactional arena where events are driven by their relative Return on Investment or COGS. Their concept of manufacturing is driven by a financial model, not by the real issues occurring down on the plant floor that are happening in real time where events occur in fractions of seconds.
Extending the Planning Software products into the real time arena requires them to custom develop the models, methods and most importantly, engines that are productized in the factory suite. Control companies are in business to leverage control hardware. This is their area of expertise and historically, these companies have had minimal success in binding their structures to the real time information requirements of the factory floor.
(c) 2002 Invensys Systems, Inc.
21-Apr-17

10. Wonderware Software Solutions
Plant Historian
IndustrialSQL
Server
ActiveFactory
ERP
MES
MES Operations/Performance
InBatch
Batch Mgmt System
Web
Info
Server
Internet Publishing
GAP
HMI/SCADA
InTouch
RT SPC/SQC
InControl
Soft Logic Controllers
IO Servers
Connectivity
Devices
(Barcode Scanner, PLCs, DCS, AB, Siemens, Omron, etc…)

11. 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
(c) 2004 Invensys Systems, Inc.
21-Apr-17

12. Duplicated services and complex integration
Historian
Tracking
Batching
HMI
Quality
OEE
Reporting
History
History
History
History
History
History
Security
Security
Security
Security
Security
Visualization
Security
Visualization
Develop
Visualization
Visualization
Visualization
Security
Visualization
Events/Alarms
Develop
Develop
Develop
Develop
Connectivity
Events/Alarms
Develop
Events/Alarms
Visualization
Events/Alarms
Events/Alarms
Events/Alarms
activity
Develop
Connectivity
Events/Alarms
Connectivity
(c) 2002 Invensys Systems, Inc.
21-Apr-17

13. WHAT IF!! ERP (SAP / ORACLE / etc) CONTROL & MONITORING SCADA
ALARMS & EVENTS
TRACEABILITY
HISTORY & GENEALOGY
PRODUCTION
QUALITY
MODULE
DOWNTIME ANALYSIS
OEE &
CONNECTIVITIES
ERP
SOFTWARE PLATFORM
FOR
MANUFACTURING

14. IMAGINE!! ERP (SAP / ORACLE / etc) CONTROL & MONITORING SCADA
ALARMS & EVENTS
TRACEABILITY
HISTORY & GENEALOGY
PRODUCTION
QUALITY
MODULE
DOWNTIME ANALYSIS
OEE &
CONNECTIVITIES
ERP
SOFTWARE PLATFORM
FOR
MANUFACTURING

15. 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

16. Wonderware System Platform
MANUFACTURING
WONDERWARE INFORMATION SERVER
(Web-based Reporting System)
WONDERWARE INDUSTRIAL
APPLICATION
SERVER
(Application Engine)
WONDERWARE HISTORIAN
(Production Database - Time-series data, Alarms & Events)
DATA CONNECTIVITIES
(PLCs, DCS, Field Devices, Barcode Reader,
Existing HMI, Existing Quality Systems, etc)

17. Wonderware System Platform

18. How are these Objects Used? (Control Environment)
The $Valve Template has been used to create several instances of the device.
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.
$DiscreteDevice
$Valve
This slide introduces the concept of a Template. Here the important notion here is that the users can build their own standards and the reuse those standard templates to ensure consistency in their applications.

19. How are these Objects Used? (IT Environment)
The $ReportObject Template has been used to create several instances of the Report.
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.
$UserDefinedObject
$ReportObject
This slide introduces the concept of a Template. Here the important notion here is that the users can build their own standards and the reuse those standard templates to ensure consistency in their applications.

20. Equipment centric objects: Powerful and multi-faceted
Inputs/Outputs
Graphic symbols
System Platform promotes engineering re-use through application objects. Application Objects represent physical equipment or logical constructs, such as control loops.
These application objects contain all configuration elements, including I/O definitions, logic and scripting, history configuration, security and access controls, and alarm/event configuration. This approach differs from traditional tag-based approaches which segment all of the configuration information into different databases and require multiple editors to manage.
This self-contained approach dramatically reduces the engineering time associated with the initial creation and maintenance of objects. By keeping all object configuration tightly related and contained within the object itself, there is no need to use multiple editors to make sure that the alarming, I/O definitions, scripting, history, and security are consistent for an object.
Logic/Scripting
Faceplates
Historical Information
Alarms and events
Security
(c) 2002 Invensys Systems, Inc.
21-Apr-17

21. Assemble multiple pieces of equipment into a process unit
(c) 2002 Invensys Systems, Inc.
21-Apr-17

22. 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
This application object can then become a template for driving standards within the application. In our example, a valve object has been created as a template and now that template is used to create instances.
Here we take the standard valve object and create 4 instances, CV101-CV104. Templates are powerful tools and facilitate re-use of engineering.
Changes made to a template will automatically be propagated to the instances created from the template. This dramatically reduces the engineering associated with changes to the system. For example say a requirement for valve objects changed after creating and deploying 100 valves from this template (say, a new state “In Transition” were added). In this case the modification can be made to the template and all 100 instances would automatically be updated. The engineer would not be required to change each individual instance of the object.
New templates can be derived from existing templates, so in this example if there were 3 different types of valves in the application, the common elements could be defined first, and then 3 templates representing the variations could be derived.
Templates facilitate enforcement of standards and the development of project-independent object libraries, enabling objects to be used across projects and further promoting the re-use of engineering and decreasing costs from project-to-project.
BK103
$GenericBrewKettle
$BrewKettleTypeB
BK104
(c) 2004 Invensys Systems, Inc.
21-Apr-17

23. Automatic historian configuration
Operator Station
Operator Station
Operator Station
Operator Station
Development Station
Development 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
The Historian is an integrated component of the System Platform.
All history configuration is managed through the IDE and stored at the Galaxy Repository. History configuration can be done at the template level and replicated down to the object instances.
The objects automatically configure the historian when they are deployed. No other tag level configuration is needed.
The historical data is being pushed from the objects to the historian, ensuring that no data is lost.
Objects automatically configure the historian and are responsible for data delivery
(c) 2004 Invensys Systems, Inc.
21-Apr-17

24. Evolution from tag-centric HMI to equipment-centric System Platform
One global name space
Security at data level
Thin presentation layer
Process Data History
Alarm History
Event History
History
CV101
SP – Solution:
Encapsulation in objects
Derivation from templates
CV102
These objects can be part of a global and secure name space for all the process data.
CV103
One global and secure name space for all process data.
(c) 2004 Invensys Systems, Inc.
21-Apr-17

25. 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
Thin presentation layer
Drag and drop
Process Data History
Alarm History
Event History
History
CV101
CV103
CV102
Object instances can easily be created in the application (galaxy) by dragging and dropping them from object templates.
Actual “Benefit Quotes” are used throughout the presentation:
Quotes marked with TSD are used with the permission from Total System Design, Inc, a Wonderware FactorySuite A² Certified System Integrator.
The Quotes are relevant to a project that TSD have done for a major North American Pharmaceutical Company.
Easy creation of object instances using “drag and drop” from templates
(c) 2004 Invensys Systems, Inc.
21-Apr-17

26. System expansion and redistribution of loads
Operator Station
Operator Station
Operator Station
Operator Station
Development Station
Development Station
Automation Object Server – AOS004
Galaxy Repository – GRNode
Historian – InSQL
Automation Object Server – AOS001
Automation Object Server – AOS002
More computing power needed!
Automation Object Server – AOS003
The system can easily be expanded by adding more computers. This can be done without reconfiguring the application or clients.
(c) 2004 Invensys Systems, Inc.
21-Apr-17

27. Application layer availability
Non-redundant system
The server handles all data.
If the server is lost then the clients lose connection to data.
InTouch
InSQL
Other AOS Nodes
Redundant System
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.
Client Server Architecture
InTouch
InTouch
InTouch
InTouch
Historian
AOS
AOS
PLC
(c) 2004 Invensys Systems, Inc.
21-Apr-17

28. Architectural flexibility
Peer to Peer Architecture
Each machine hosts a different AppEngine and AppObjects.
Platforms can host more than one AppEngine.
AE1 Backup is assigned to Workstation 2.
AE2 Backup is assigned to Workstation 1.
Primary
AE1
AE2
RMC
AE2
backup
AE1
backup
AOS001
AOS002
(c) 2004 Invensys Systems, Inc.
21-Apr-17

29. Software Solutions for Real-Time SuccessSM
(c) 2002 Invensys Systems, Inc.
21-Apr-17