Transcript PPT Template

Slide 1
WW OPS-02
Wonderware InBatch
Software Update
Dirk Kozian
Sr. Product Manager,
Batch & Workflow Software
© 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.
What is InBatch?
InBatch is Flexible Batch Management Software Designed to Model and
Automate Batch Processes
• Model-based - Consistent with ISA-88
• Comprehensive production history - Electronic Batch Record
• Easy recipe creation
• “Out-of-the-box” batch simulation
• Scalable System Architecture – single node to large systems,
integrated to System Platform/InFusion
• Built-in Redundancy concepts
• Beyond ISA-88:
– Material genealogy
– Connection & Transfer Management
Slide 3
Generally Speaking…
InBatch is specifically made for the process industry, in other words it
can be used
“to manage the production wherever
free fluent materials are processed”
InBatch allows managing complex, networked process equipment and
is usually seen as Process MES
InBatch provides ISA 88 conformity and allows going beyond ISA 88
with its Transfer Classes and Material Management capabilities
InBatch is used more than 1000 times around the globe, often for
more than 10 years
Slide 4
InBatch Value - Proposition & Benefits
InBatch provides unmatched capabilities:
• Batch execution management for multiple batches at the same time
• Equipment allocation and arbitration
• Comprehensive electronic batch record (EBR) and reporting capabilities out of
the box
• 21 CFR Part 11 compliance
InBatch provides increased production flexibility and tracking
• Recipe procedure changes
• Material formulation changes
• Complete material genealogy
– International Food Standard (IFS), US and EU standards, Bio-terrorism
InBatch & InFusion – a unique solution
Slide 5
About I/A Batch, InBatch, and
Wonderware InBatch
Slide 6
• 1987
BPM Batch Manager (UNIX) (Foxboro – The Netherlands)
• 1989
RBatch 1 Batch Manager (Foxboro – The Netherlands)
• 1992
RBatch 2 Batch Manager (Soft Systems/Foxboro)
• 1994
FoxBatch Batch Manager (Soft Systems/Foxboro)
• 1996
InBatch (Soft Systems/Wonderware – WINDOWS port)
• 1999
I/A Batch/InBatch (Foxboro/Wonderware) Unix/Windows
• 2003
I/A Batch 8.1 – InBatch 8.1 (Wonderware)
• 2005
I/A Batch 8.1 SP1 – InBatch 8.1 SP1 (Wonderware)
• 2009
Code alignment + New Features = “Wonderware InBatch 9.0” (Invensys
Operations Management)
• 2010
Wonderware InBatch 9.1
• 2012
Wonderware InBatch 2012
InBatch – Process Model
The Plant contains
• People, Equipment & Materials
The Process Model defines
• Equipment Resources
• Capabilities
• Relationships to other Equipment
Resources
The Recipe combines
• Equipment
• Formula
• Procedure
Slide 7
Single or Many Relationships
Process Units
Products/Product Variations
Processes/Process Variations
Production Facilities/Lines/Sites
Slide 8
Batch Management
Recipe Management
Batch Management Systems
are traditionally composed
of two subparts:
One assuring the creation
and configuration of the
recipes, and;
Batch Execution
Management
Batch Management
Slide 9
The other assuring the
execution of the recipes,
i.e., driving the equipment
to make a product.
Master Recipe Contents
Header
Recipe ID:
Recipe Name:
Version #:
Version Date:
Author:
Min. Batch Size:
Max. Batch Size:
Def. Batch Size:
Formula
Material Inputs:
Tomato Sauce
Cajun Spices
Material Outputs:
Cajun #2
Process Variables:
Mix Time
Slide 10
Equipment
F123134544
Cajun #2
3
12/20/03
L.G. White
100
1000
500
Recipe
Class
Attribute
Blenders
Reactors
Bulk Tanks
Finish Tanks
Hold Tanks
Pack Line
Capacity: 500
Lining: 1
Procedure
Add
Heat
Cool
Mix
Describing the Process:
Using the Recipe Editor
Slide 11
InBatch Release Timeline
Slide 12
• 1999 I/A Batch/InBatch
(Foxboro/Wonderware)
Unix/Windows
• 2003 I/A Batch 8.1 –
InBatch 8.1 (Foxboro Wonderware)
• 2005 I/A Batch 8.1 SP1
– InBatch 8.1 SP1
(Foxboro Wonderware)
• Message
eXchange (MX)
Communication
• ArchestrA
Security
• Update to
Reporting
framework
• Consolidate
InBatch code for
multiple offerings
2011
• Extensibility
and
Maintenance
• Extensibility
• Overall
Improvements
• Technology
update
InBatch 9.5
• 1996 InBatch (Soft
Systems/Wonderware
– WINDOWS port)
• Integration
to ArchestrA
System
Platform
2010-11
InBatch 9.0 SP1 - SP2
and SP2
• 1994 FoxBatch Batch
Manager (Soft
Systems/Foxboro)
2009
InBatch 9.0
InBatch 4.2 - 8.1
1994 - 2003
• Single Historian
for multiple batch
servers
• Import/Export
recipes to
BatchML format
• Stateless API
• Improved
reliability ClientServer
communication
• Cyber Security
Slide 13
2012
2012
• Maintenance and
Cyber Security
• Maintenance and
Cyber Security
•
•
•
•
Cyber Security
Technology update
MX Communication
VSphere 5.0 Basic
Testing
InBatch 2012 (9.6)
InBatch 9.5 SP1
InBatch Release timeline
• ScanOnDemand
improvements
• AIM API vs. FOX API
• Enable (shared)
equipment management
outside InBatch
InBatch Release timeline
InBatch 2012 R2 v10.0
2013
• Recipe Management
(Proposed Features)
• Recipe – Recipe
comparison
• Batch Eventing
Framework to enable
e.g. Multi - Recipe
Coordination
• InBatch Objects in
AppServer
• Technology update
Slide 14
InBatch 9.0
Provides tight integration to System Platform
• MX communication between InBatch and Application Server 3.x
• Leverages the ArchestrA security platform
• Incorporates Wonderware Information Server as Reporting Portal for Batch
Reports
– Uses MS Reporting Services as reporting framework
– Removes support for Crystal Reports
Updates InBatch Automation Servers to support Visual Studio 2005
Invensys Internal -Merge code of IA Batch and InBatch
Slide 15
Flexible and powerful batch management
capabilities
InBatch
Server
MX communication
Phases modeled
within Control System
PHASE 4
PHASE 1
PHASE 5
Device Integration Device
PHASE 6
Phases modeled
within System
Platform
Slide 16
System
Platform
PHASE 2
PHASE 3
Flexible and powerful platform and
plant model
InBatch 9.0 with SP1
I/O Server Failover Indicator
• Indication of I/O server failover status through InBatch tags
• White Paper: Best Practices and Considerations for Designing Reliable InBatch
Solutions
Support for Infusion CE 2.0 and I/A Series software 8.5
Technology Update
• Windows XP Professional SP3
• Windows 2003 R2 Server (32 bit only)
• Windows Vista SP1 (32 and 64 bit)
• Windows 2008 Server SP1 (32 and 64 bit)
• Microsoft SQL Server 2005 SP3 (32 bit) and SQL Server 2008 SP1 (32 bit)
Slide 17
InBatch 9.0 with SP2
Support for History Hook interface
• Enable users to customize the storage of InBatch History data. E.g. store Bath
history data in Oracle DBs
Support for Programmatic access to Connection and Segment data
• Existing interfaces extended to allow access to connection and segment data
from the Process Model
Import Recipes to the Recipe DB
• Recipe Editor and the Recipe Automation Server extended to support the import
of recipes from an XML file
• The format for the XML documents is based on the Batch ML Batch Information
Schema (S88 Part 2)
R-Batch Recipe Conversion Tool
• A tool was created to convert legacy Foxboro RBatch recipes into InBatch recipes
Slide 18
InBatch 9.5
Ability to use a single Batch History Server as the central historian repository for multiple
InBatch Servers.
InBatch
Server
“Alpha”
S
InBatch
Server
“Charlie”
InBatch
Historian
InBatch
Server
“Piper”
Slide 19
Single Historian: Configuration & Reports
Slide 20
InBatch 9.5 – Recipe Import/Export
to BatchML format
Recipe Export and Recipe Import using XML documents based upon BML
(Batch Markup Language) as defined by the World Batch Forum
Slide 21
InBatch 9.5
Stateless API Support
• Addition of a new stateless API suite which allows users to perform various
operations against a Batch Server at runtime
• This API is callable from Application Server Object scripting
• Can be invoked from any .NET application
Recipe name lengths greater > 16 Characters
• Support recipes with names greater than 16 characters.
Local Regional Settings for reports
• Enable users to retrieve Date/time information in InBatch Reports as per the
date/time OS settings
• The reports will use the localization date/times used in German, French,
Japanese and Chinese
Slide 22
InBatch 9.5
Technology Update
• Provide support for using InBatch Client Components on Windows 7 SP1
• Provide support for the Windows 2008 Server R2
Slide 23
InBatch 9.5 SP1
Maintenance of Line focused on:
Issues reported by key customers
•
Cyber Security:
• Technology update to support SDL (Security Development lifecycle) initiative
Technology Update:
•
Compatibility with FCS 3.1
•
Microsoft Hyper-V HA (High Availability) and DR (Disaster Recovery) features
•
VMware VSphere 5.0 Basic compatibility
•
SQL Server 2008 SP3 Support
Minor enhancements:
•
Improve diagnostics by enhancing error and warning messages
•
Other minor backlog items
Updated Performance Benchmark by testing in “Real Systems”
Slide 24
InBatch 2012 (v9.6)
Beta-Live – GA: End of October 2012
Maintenance of Line focused on:
Issues reported by key customers
•
Cyber Security:
Technology update to support SDL (Security Development lifecycle) initiative
•
Technology Update:
•
AIM API vs. FOX API for direct DCS communications
Minor enhancements:
•
Improve the ability to handle shared equipment outside of InBatch more
appropriately
Slide 25
InBatch 2012 R2 (v10.0)
Planned for Q2/2013
Common Install, Licensing, Configuration for InBatch
Slide 26
InBatch 2012 R2 (v10.0)
Planned for Q2/2013
Replication of the InBatch Process Model in App Server through InBatch
App Objects
• On demand synchronization of InBatch Process Model into AppObjects Model
Slide 27
InBatch 2012 R2 (v10.0)
Planned for Q2/2013
Recipe to recipe Comparison
• Ability to easily identify differences between two recipe versions, leveraging
BatchML as introduced with InBatch 9.5
Batch Eventing Framework
• Ability to raise events on certain batch relevant situations such as “End Of
Batch” to (for example) coordinate the execution of batches using multiple
recipes though e.g. Wonderware Application Server or ArchestrA Workflow
Software. Leveraging ASB (ArchestrA Service Bus)
Slide 28
Example Scenarios
1. Run Phases that are complex to manage
from PLC or DCS
For example, an Operator received pre-packaged materials for the
process he’s running. He scans the bar code on the big-pack and the
system must tell whether he can make use of it or not. The solution
executes database queries to support the Operator interaction.
System
Platform
Slide 29
Example Scenarios
2. Dynamically adjust target values through phases in ArchestrA
System Platform
For example, use the measured fat content to adjust following material
additions to result in a defined overall fat content for the product.
PHASE 5
PHASE 6
Slide 30
System
Platform
InBatch
Server
Example Scenarios
3. Abstract S88 Phase interface to sustain existing DCS/PLC
control code from changes.
E.g. Existing validated DCS control code must not be changed when
using Application Server as the interface that manages parameters
and set points in conjunction with InBatch.
InBatch 9.0
RBatch II
RBatch II
RBatch II
DEP
EXP
MON
Control Param.
Control Param.
START
Activate
HOLD
Activate
RESTART
Activate
ABORT
RESET
Phase Status
Ready
Run
Held
Done
Aborted
Interlocked
Slide 31
RBatch II
Translation
Logic
for every Phase
Same script for every
(Phase)
Activate
Activate
Phase Status
Active
Paused
Success
InFusion
InBatch
Server
Example Scenarios
4. Make use of InBatch’s Stateless API and COM Server
components within InFusion.
E.g. Material reconciliation scenarios to align MES and Business
System’s materials
PHASE 4
PHASE 5
PHASE 6
Slide 32
InFusion
InBatch
Server