Inbatch Getting Started Guide: Invensys Systems, Inc
Inbatch Getting Started Guide: Invensys Systems, Inc
Inbatch Getting Started Guide: Invensys Systems, Inc
Revision A
Last Revision: 8/18/08
Copyright
© 2008 Invensys Systems, Inc. All Rights Reserved.
All rights reserved. No part of this documentation shall be reproduced, stored in a
retrieval system, or transmitted by any means, electronic, mechanical,
photocopying, recording, or otherwise, without the prior written permission of
Invensys Systems, Inc. No copyright or patent liability is assumed with respect to
the use of the information contained herein. Although every precaution has been
taken in the preparation of this documentation, the publisher and the author
assume no responsibility for errors or omissions. Neither is any liability assumed
for damages resulting from the use of the information contained herein.
The information in this documentation is subject to change without notice and does
not represent a commitment on the part of Invensys Systems, Inc. The software
described in this documentation is furnished under a license or nondisclosure
agreement. This software may be used or copied only in accordance with the terms
of these agreements.
Trademarks
All terms mentioned in this documentation that are known to be trademarks or
service marks have been appropriately capitalized. Invensys Systems, Inc. cannot
attest to the accuracy of this information. Use of a term in this documentation
should not be regarded as affecting the validity of any trademark or service mark.
Alarm Logger, ActiveFactory, ArchestrA, Avantis, DBDump, DBLoad, DT Analyst,
Factelligence, FactoryFocus, FactoryOffice, FactorySuite, FactorySuite A2, InBatch,
InControl, IndustrialRAD, IndustrialSQL Server, InTouch, MaintenanceSuite,
MuniSuite, QI Analyst, SCADAlarm, SCADASuite, SuiteLink, SuiteVoyager,
WindowMaker, WindowViewer, Wonderware, Wonderware Factelligence, and
Wonderware Logger are trademarks of Invensys plc, its subsidiaries and affiliates.
All other brands may be trademarks of their respective owners.
3
Contents
Welcome............................................ 7
Documentation Conventions ..............................................7
Technical Support ...............................................................8
Welcome
Documentation Conventions
This documentation uses the following conventions:
Technical Support
Wonderware Technical Support offers a variety of support
options to answer any questions on Wonderware products
and their implementation.
Before you contact Technical Support, refer to the relevant
section(s) in this documentation for a possible solution to the
problem. If you need to contact technical support for help,
have the following information ready:
• The type and version of the operating system you are
using.
• Details of how to recreate the problem.
Chapter 1
InBatch Overview
System Requirements
InBatch system requirements are listed in Chapter 2, System
Installation in the InBatch User’s Guide.
Installing InBatch
You install from its product CD-ROM. The installation
program provides the capability to install various InBatch
server and client configurations.
For detailed information about installing InBatch, see the
InBatch User’s Guide.
Overview of Capabilities
Wonderware InBatch is flexible batch management software
designed to automate and provide a complete production
history for batch processes. InBatch is consistent with the
ISA-88 standard. InBatch enables you to quickly and easily
create recipes and simulate their execution against a model
of the process—all before you write one line of control code.
InBatch also provides complete production history and
materials genealogy. The powerful batch engine means that
you can reduce the cost and time to implement your
batch-related processes by up to 40 to 60% over competitive
solutions.
InBatch provides out of the box batch management
functionality that eliminates the need for unsustainable
custom code in the PLC or distributed control system (DCS)
and dramatically reduces the life-cycle engineering effort.
The sophisticated batch engine is responsible for unit-to-unit
material tracking, short term scheduling, dynamic batch and
equipment management, and batch history and reporting.
The InBatch management system also supports redundancy
for mission-critical applications.
Process Modeling
A batch processing plant is made up of units and connections.
The five main components of the process model are:
• Units
• Processing capabilities.
Units
A unit is any vessel that can hold or process materials. Some
units have no processing capabilities, such as bulk storage
vessels, manual add stations, and hold tanks. Other units
have significant processing capabilities, such as reactors,
blenders, mixers, dryers, retorts, and washers. Examples of
processing capabilities are agitating, mixing, heating,
cooling, blending, and packaging. Other examples of units
are storage tanks, silos, ovens, fillers, washers, retorts,
molders, bottlers, wrappers, cartoners, and palletizers.
Connections
Connections are the equipment that is necessary for
transferring a product from one unit to another. Examples
are pumps, valves, separators, condensers, and flow meters,
Many plants have units that are connected to more that one
unit and some plants have multiple connections between the
same two units.
Phases
Processing and transferring capabilities are defined by
phases. Each phase is an independent action that can contain
a unique set of parameters. Parameters configure the phase
based on recipe requirements. Phases can be automatically
processed by the control system or manually run by an
operator.
Recipe Management
The batch control system manages and constructs recipes
according to the guidelines outlined in the ISA-88 Flexible
Batch Specification.
Master Recipes
You can construct and edit master recipes. Master recipes
are not specific to process lines, but are independent of
equipment. You can assign master recipes to any process line
(train) that has units belonging to the classes of process
equipment defined in the recipe.
A master recipe is not size specific, but is scalable to the
batch size defined by production scheduling. You can enter
all formula quantities for ingredients, intermediates,
by-products, and finished goods as either actual quantities or
as a percent of the total batch size. Quantities expressed in
percentages are scaled by the batch management system
when the batch runs.
Control Recipes
A master recipe becomes a control recipe as the units defined
in the train are dynamically allocated and used in producing
a batch.
Recipe Editor
Use the Recipe Editor to construct and alter recipes. You can
save, retrieve, and print recipes. A revision control system
provides you with an accurate time-stamped history of all
changes and revisions that have been made to the recipe.
Batch Management
Batch management consists of scheduling batches,
initializing batches, coordinating the execution of batches
with the control system, interfacing with operators, and
storing all batch activity. You perform these tasks using the
Batch Manager, Batch Scheduler, and Batch Display
programs.
Batch Scheduling
Use Batch Manager to dispatch to plant floor operators the
batches that are ready to run. To schedule a batch, you
manually enter the batch identification, master recipe, batch
size, and train (process line) into the Batch Scheduler. After
you enter the batch, you can initialize it.
Batch Initialization
You must initialize each batch before you can run it. The
initialization process involves validating the recipe, checking
if the train exists, checking if the bulk materials defined in
the recipe are available in the train, ensuring that the recipe
equipment requirements are satisfied by the train, and
verifying that the Process Model database is compatible with
the recipe.
History
Batch Manager captures and stores all processing and
operator activity when a batch runs.
Batch History
InBatch uses Microsoft SQL Server for its historical
database.
The batch management system logs all information related to
the production of a batch to the history database. This data
includes all the events, process data, production information,
material usage, operator comments, operator actions,
equipment used to produce the associated batch, and all
batch-related process alarms.
Batch Reports
InBatch uses Wonderware® Information Server (WIS) for
reporting. WIS provides a flexible and open platform so that
you can easily build custom reports. You can use a set of
pre-defined report templates to design reports.
You can retrieve batch reports using the run-time reporting
system. You can automatically trigger reports while a batch
runs or at the end of a batch.
InBatch Integration
InBatch integrates with a number of other Wonderware
applications.
Tag Management
InBatch interfaces to other Wonderware components like
InControl™, I/O servers, DAServers, and InTouch® software
through tags. Also, you can integrate InBatch with the
Wonderware Application Server and leverage the full
capabilities of both components to extend the boundaries of
the implementation.
Model Editor
Use the Model Editor to construct the plant model consisting
of units, connections, phases, phase parameters, and
segments. Tags are automatically created using these names
and are used by InBatch to communicate with PLC or DCS
systems.
TagLinker
Use the InBatch TagLinker to link the tags you create in the
Model Editor to control system addresses. The TagLinker
provides capabilities to link tags automatically using default
links, manually through the graphical user interface, or by
external interfaces using a comma separated variable format
import or export file. The TagLinker also validates model
tags.
Tag Communications
InBatch communicates with other applications or
components through OPC, Suitelink or Message Exchange
(MX). Tag communications are used to interface to unit
control logic, phase logic, and operator displays. The Phase
Logic and TagView tools are available to diagnose,
troubleshoot, and exercise tags communications.
TagView Tool
Use the TagView tool to monitor InBatch tags at run time.
Batch Alarms
Batch alarms are captured, associated with a batch, and
stored in the history database. The Unit or Connection Name
parameter of the tag is the key in accomplishing this. All
alarms from a designated InTouch application are monitored
by the batch control system. If the first portion of the tag
name corresponds to a unit, connection, or segment name in
the InBatch model, the alarm is automatically logged to the
InBatch history and associated to the batch that was active
in the named equipment at the time of the alarm.
Extensibility
InBatch provides you with a rich set of ActiveX objects and
API functions for integrating external applications such as
enterprise resource planning (ERP) or scheduling systems
and allowing exchange of formulas and recipes, materials,
and production results.
InBatch uses Microsoft SQL Server as its historical database.
These features make it easy for you to integrate with ERP
and Advanced Planning Systems by allowing InBatch to be a
key link in a successful supply chain management initiative.
Configuration Modules
You can use the following modules to develop and manage
your batch system:
Run-Time Modules
The following run-time programs are used by the InBatch
system during batch processing.
Log Viewer
(Optional) The Log Viewer displays messages for all system
activity, including the InBatch server, run-time clients and
development clients such as startup, shutdown, warnings
and errors, as well as time and date stamps.
Tools
Use the following tools to assist your development and
run-time processes.
Chapter 2
InBatch Tutorial
Tutorial Overview
This tutorial guides you through the following topics:
• The Breading Plant Process Area
• Hardware Architecture
• Configuration Steps
• Viewing a Report
Bulk1 Bulk2
Flour Salt
Mix1_Chg Mix2_Chg
Mixer1 Mixer2
Hold1 Hold2
Hardware Architecture
The example architecture is shown in the following figure.
Mercury is the node name of the InBatch server. Mixer1 is
the node name of the InBatch run-time client.
Note The Mixer1 node is used for illustration purposes only. This
node is portrayed as an InBatch development client. You can
perform all configuration information presented here from the
InBatch server or the InBatch development client. This example
refers to the server.
Configuration Steps
Use the following steps to configure the InBatch Server:
1 Model the process
2 Use the Tag Linker
3 Update the run-time databases
4 Define the process trains
5 Defining the materials and material locations
6 Build a recipe
7 Create an InBatch run-time client (InTouch) application
8 Start the InBatch runtime system
9 Schedule and execute batches
10 Execute an end-of-batch report
Defining Units
Units are equipment entities that hold, process, or package
materials.
To define units
1 Click the Units tab.
2 In the Name box, type Bulk1.
3 Click Add.
4 Use the same process to enter the following units:
• Bulk2
• Hold1
• Hold2
• Mixer1
• Mixer2
The following figure shows the result of adding the units.
Defining Connections
Connections are defined by a source unit and a destination
unit. If materials can move between two units, you must
define the connection. The way in which materials move is
not important at this time.
To define connections
1 Click the Connections tab.
2 In the Name box, type Blk1Mix1.
3 Click Source Unit.
4 In the Select Source Unit dialog box, click Bulk1.
5 Click Apply.
6 Click Destination Unit.
7 In the Select Destination Unit dialog box, click Mixer1.
8 Click Apply.
9 In the Connections tabbed dialog box, Click Add.
10 Repeat steps 1 through 8 for the items shown in the
following table.
ManAdd Manual
Instruct Manual
7 Click Close.
Note You do not have to create tags for the ManAdd phase.
Transfer Class
Name Source Process Destination Process
Note You must click the Change button following any phase
modifications.
Defining Segments
A segment is a subsection (part of a connection). Segments
are the lowest equipment entities that are managed by
InBatch. When a transfer is processed, the segments that
make up a connection are allocated to a batch. This action
prevents other transfers from using the same segments
associated with their connection and enables the batch
engine to provide automatic process interlocking.
To define segments
1 Click the Segments tab.
2 In the Name box, type the following segment name:
Blk1_Dis.
3 Click Add.
4 Repeat the process for the following segment names:
• Blk2_Dis
• Common
• Mix1_Chg
• Mix2_Chg
The following figure shows the completed tabbed dialog box.
Defining Materials
First, define the materials used in the breading process.
To define materials
1 On the Material Editor dialog box, click Edit > Materials
Editor.
The Materials Editor dialog box appears.
2 In the Materials area, define the following ingredients.
3 In the Materials area, click the arrow for the list and
select Finished Goods.
4 Define the following Finished Goods.
5 Click Close.
4 Click Add.
The Unit Selection dialog box appears.
Building a Recipe
After you have defined the process, process trains, materials,
and material locations, you are ready to build a recipe with
the Recipe Editor.
10 Click Close.
7 Click Close.
14 Click the double line just above the ManAdd Mixers block.
17 Click OK.
18 Close the Transition Properties dialog box.
25 Click Change.
26 Select the Instructions tab.
27 In the Instructions box, type the following text:
Enter Speed and Time, then Acknowledge.
28 Click Change and then click Close.
Note You cannot schedule and process the batch unless the
recipe is valid.
3 Click Close.
4 Close the Recipe Editor dialog box.
To configure a report
1 On the root of the C:\ drive, create a folder named
Reports.
2 Share the folder with full permissions. If you do not share
the folder, you cannot see reports.
3 On the Environment Display dialog box, double-click the
BatchReport icon.
The Wonderware Information Server home page appears.
To schedule a report
1 On the Launch Pad pane, expand Administration > InBatch
Manager > Reports.
2 Click Schedule.
In the right pane, the Schedule page appears.
3 Click Schedule New Report.
The Add New Report form appears.
To schedule a batch
1 On the Environment Display dialog box, double-click the
BatchSched icon.
The Batch Scheduler dialog box appears.
Note You can also change the status of one batch from the
Initialize menu.
Notice that the Status column now indicates that all the
batches are Ready.
To run a batch
1 On the Environment Display dialog box, click the BatchDspl
icon.
The Batch Display dialog box appears.
Notice that the first scheduled batch appears by default
in the upper area.
c Click Yes.
When the recipe completes processing, the Status
indicator in the upper area of the Batch Display dialog box
changes to Done.
Viewing a Report
You can run and view reports that have been automatically
generated by InBatch. That is, these are reports that you
configured and scheduled to run at a specific time.
To view a report
1 Click the View button associated with the report that you
want to view. In this case, only the End of Batch report is
available.
Note If you are running InTouch on the InBatch server, you do not
need to configure the control for the host name.
Note The Recipe and Train fields can be populated from the
Recipe List and Train List BatchList controls respectively. These
can be added on this window or as a separate pop-up window.
To start a batch
1 On the Environment Display dialog box, double-click the
BatchDspl icon. The Batch Display dialog box appears.
Campaign C001
Lot L002
Batch 1
Recipe CB1000
Quantity 5000
Train Mixer 1 Train