Home › Technical articles

Đọc bằng tiếng Việt

AVEVA Batch Management and ISA-88: process model, recipes, phase logic in the PLC and System Platform

TDL Industrial Automation · Last updated:

From AVEVA's Batch Management 2023 R2 documentation: units, process classes, connections, transfer classes and trains; master and control recipes, formula and procedure; the programs and servers; phase blocks in the PLC with control and status bits; Tag Linker, IBCli and IBMX; System Platform and InTouch integration; redundancy, warm restart, batch history, SSRS reports and the PI Interface.

AVEVA Batch Management, formerly Wonderware InBatch, is AVEVA's batch management system. Its documentation describes it as consistent with ISA-88: the plant is modelled as units and connections grouped into classes, recipes are built against those classes, and the Batch Manager runs each batch by starting phase logic that lives in the PLC or DCS. This article follows the newest documentation set on docs.aveva.com, AVEVA Batch Management 2023 R2 (v13.1); the standard itself is explained in ISA-88 batch control.

AVEVA Batch Management: model, recipe and phase logicTwo columns at the top. Left, the process model built with the Process Model Editor and Train Editor: a process class groups units and process phases; a transfer class groups connections and transfer phases; a train is a process line of units on which batches are scheduled. Right, the recipe built with the Recipe Editor: a master recipe with equipment requirements, a formula, and unit procedures, operations and phases taken from the model, which becomes a control recipe at run time. Both columns lead down to the Batch Management Server, where the Batch Manager converts the master recipe into a control recipe, allocates units, downloads parameters and starts phases, and the History Queue Manager sends batch history to the History Server. A two-way arrow links the server to the PLC or DCS: commands and parameters go down, status and actual values come up. The controller holds one phase block for each automatic or semi-automatic phase on each unit or connection. Based on AVEVA Batch Management 2023 R2 documentation.AVEVA Batch Management: model, recipe and phase logicProcess modelProcess Model Editor, Train EditorRecipeRecipe EditorProcess classunits with the same processing capabilityUnitvessel that holds or processes materialProcess phaseautomatic, manual or data, withformula parametersTransfer classconnections between the same twoprocess classesConnectionpumps, valves, piping; optional segmentsTransfer phaseautomatic, semi-automatic, manual or dataTrainprocess line of units on which batchesare scheduledMaster recipeuses process classes, not specific units; scales tothe batch sizeEquipment requirementsthe process classes and attribute rangesit needsFormulainputs, outputs, process variablesUnit procedureprocedure step, assigned to a process instanceOperationgroups phasesPhasefrom the process model; parameter valuesfrom the formulaControl recipebuilt at run time from the units of the trainProcess Model, Recipe and Materials databasesAVEVA Batch Management ServerBatch Manager: master to control recipe, unit allocation, parameter download, phase startHistory Queue Manager: batch history to the History Server (SQL Server, SSRS reports)tags to the controller through IBCli (OPC, SuiteLink) or IBMX (Galaxy, Message Exchange)commands, parametersstatus, actual valuesController · PLC or DCSone phase block per automatic or semi-automatic phase, on each unit or connectioncontrol bits: Start, Hold, Restart, Abort, Resetstatus bits: Ready, Run, Held, Done, Interlocked, Abortedmanual and data phases: no phase logicRed outline: phases, where the recipe meets the phase logic in the controllerBased on AVEVA Batch Management 2023 R2 documentation (read 17 November 2026). Figure: drawn by TDL.
Figure 1: AVEVA Batch Management: model, recipe and phase logic. On a phone, swipe sideways to see the whole figure.

1. What the product is and which version the docs describe

AVEVA notes that InBatch is now AVEVA Batch Management, although "InBatch" still appears in upgrade paths, batch reports and program names. The batch engine handles unit-to-unit material tracking, short-term scheduling, batch and equipment management, and batch history and reporting.

The 2023 R2 release summary lists support for System Platform 2023 R2 SP1 shared components. A "New features and enhancements" page in the same set, updated in July 2026, adds support for System Platform 2026 and services running under Virtual Service Accounts, but gives no new version number.

The installer offers seven features: Batch Management Server, Remote Development Client, Remote Runtime Client, History Server, Reporting Content, Components for ArchestrA IDE and Documentation.

2. The process model

AVEVA's Process Modeling page says a batch plant is made up of units and connections, and names five main components: units, process classes, connections, transfer classes and processing capabilities. The table lists these and the other model components the Batch Management 2023 R2 pages describe:

Component What it is
Unit Any vessel that can hold or process material: storage tanks, reactors, mixers, dryers, fillers
Process class All units with the same processing capability; its phases define what those units can do
Connection Equipment that moves product from one unit to another, such as pumps, valves and flow meters
Segment Optional part of a connection, such as shared piping, valves or pumps
Transfer class All connections between the same two process classes, with their transfer phases
Phase An independent action with its own parameters, run by the control system or by an operator
Equipment status Optional states of units or segments, checked before they are allocated
Train A process line of one or more units on which batches are scheduled; a unit can belong to several trains

Three model types are documented. A comprehensive model defines units and connections, so the batch engine coordinates transfers; AVEVA calls it the preferred technique. A connectionless model defines units only and moves material with complementary discharge and charge phases, leaving coordination to the operator or the control system. A hybrid model defines connections only for fixed paths.

For large plants AVEVA suggests several smaller installations, each area modelled separately, logging to one History Server; each Batch Server then needs its own Batch Server Name and one-letter Batch Server ID.

3. Recipes: master, control, formula and procedure

A recipe has four parts: header, equipment requirements, formula and procedure.

  • Equipment requirements name the process classes the recipe needs, with attribute ranges; AVEVA's example is a reactor capacity from 500 to 1000. The recipe can only use the phases of those classes.
  • Formula lists inputs, outputs and process variables. Inputs and outputs can be actual quantities or a percentage of the batch size; process variables are actual values.
  • Procedure is built from unit procedures, each assigned to a process instance, operations that group phases, and phases taken from the process model, linked by transition logic, branches and loops. Two special phases, Allocate and Release, reserve units or connections for a batch and free them.

A master recipe uses classes, not specific units, and scales to the batch size set in the schedule. When the batch runs, the Batch Manager converts it into a control recipe from the units of the assigned train. Once a batch is initialized, recipe edits no longer reach it; changes to the materials database or the model can, so AVEVA recommends ending all batches before updating the model to runtime.

AVEVA advises re-evaluating the design when more than 50 Boolean transition expressions use tags, and moving that evaluation into the control system.

4. Programs and servers

Program Role in Batch Management 2023 R2
Environment Editor and Environment Manager define, then manage, the batch run-time applications
Environment Display one interface to start and stop the batch applications
Process Model Editor builds the process model; only one runs in a system at a time
Tag Linker links model tags to control system or InTouch addresses
Train Editor, Materials Editor, Recipe Editor trains, materials and recipes; several Materials and Recipe Editors can run together
Batch Manager processes recipes, allocates units, queues history, triggers reports
Batch Scheduler and Batch Display the schedule of batches, and run-time detail of one batch
InBatch Client (IBCli) link to I/O servers over OPC or SuiteLink
InBatch Message Exchange (IBMX) link to Galaxy data in Application Server over Message Exchange
Simulation Manager replaces the communication drivers to run without control hardware

A web client gives a read-only view of active batches, phases, transitions and reports, without a client licence.

5. The controller side: phase blocks and tags

Phase logic runs in the control system. Every automatic phase, and every semi-automatic transfer phase, needs a phase logic block for each unit of the process class or each connection of the transfer class; manual and data phases have none. A phase block has eight components: control bits, status bits, control inputs, control outputs, formula parameters, control buttons, interlocks and alarms.

The control bits are Start, Hold, Restart, Abort and Reset, and the status bits Ready, Run, Held, Done, Interlocked and Aborted; only Start, Reset, Ready and Done are required. Commands are usually packed into a word and read as one-shots. The Batch Manager downloads the formula parameters, then sends Start; the block runs, can be held by command or by a critical alarm, and ends Done or Aborted until a Reset returns it to Ready. AVEVA's rules say a running phase should continue to Done if communication with the batch system fails. Unit control bits carry Hold, Restart and Abort for a whole unit.

The Model Editor creates tags for units, connections, segments, phases and parameters, and the Tag Linker links them to addresses. It has three default access names, Galaxy, ControlSystem and InTouch, with one IBCli instance per access name; IBCli can switch to a backup I/O server. AVEVA's pages differ on protocols: the IBCli page names OPC and SuiteLink, while the Tag Linker overview requires SuiteLink I/O Servers. The PhaseLogic tool tests the handshake and is not meant for normal operation.

6. With System Platform and InTouch

Batch Management ships ApplicationObject packages for a Galaxy: $InBatchUnit, $InBatchConnection, $InBatchPhase and $InBatchSegment. The Import AVEVA Batch Management Model utility in the IDE reads the process model, creates templates for each process and transfer and instances for each unit and connection, and links the batch tags to the object attributes, which IBMX then reads. The generated phase tagname, unit plus phase name, must stay within 32 characters, and after an upgrade the packages and the model must be imported again.

Imported attributes are only memory locations until they are extended to I/O, simulated or scripted. AVEVA's IBMX recommendations (Advise All, dedicated DI objects or a registry setting) exist because otherwise batch history can receive stale values.

On InTouch, batch tags come from a Tag Linker CSV loaded with DBLoad or are referenced remotely through the tag browser. Alarm reports work with the InTouch alarm database (WWALMDB) or the Historian alarm database (A2ALMDB); only alarms on tags whose names begin with a unit or connection name followed by ".", "-" or "#" can be tied to a batch. Whether a Galaxy is needed at all: InTouch HMI or System Platform.

7. Redundancy and warm restart

A redundant system has two Batch Management Servers, either of which can act as master; database changes are written to both. Each server needs two network cards on different networks, and a dedicated secondary network over a cross-over cable carries the heartbeat; the Redundancy TimeOut parameter sets the delay before failover. Failover follows a crash of a critical service, among them Batch Manager, IBCli, IBMX and the History Queue Manager, or an exit and shutdown of the master. After a network or power failure of the master, InTouch clients do not fail over and the InTouch View client must be restarted. When the backup starts, the status of running phases is read from the controller.

After an unexpected shutdown, the Batch Manager's warm restart reads the data files in its .BatchWR folder: allocated equipment stays allocated, batches that were running come back Held, and phases running in the controller keep running during the outage. Server redundancy on other platforms: SCADA server redundancy.

8. Batch history, reports and the PI Interface

Batch history lives on the History Server in Microsoft SQL Server: events, process data, material usage, operator comments and actions, the equipment used and batch-related alarms. The History Queue Manager on the Batch Management Server time-stamps the data and holds it locally when the link drops; near 1.9 GB of queue database it stops accepting data, which shuts the Batch Manager down.

Reports run on SQL Server Reporting Services (SSRS), on a schedule, during a batch or at its end. AVEVA supplies templates as examples for custom reports, among them BatchDetail, Batch Journal, Batches By Material, Material Inputs, Process Variables and Production By Lot. Configuration databases are copied with the DBCOPY utility while the system runs.

The PI Interface for AVEVA Batch Management 5.1.13 (September 2026), formerly the PI Interface for Wonderware InBatch, supports Batch Management 8.1 SP1 and later. It reads the batch history tables in SQL Server and creates event frames in PI AF, with PI points and an AF equipment hierarchy: one root event frame per batch and a child for each unit procedure. Timestamps come from Batch Management, and interface instances can fail over. How Historian and PI differ: AVEVA Historian vs PI System.

What we check first

This is TDL's practice, not an AVEVA requirement.

  • The Batch Management, System Platform and InTouch versions on every node, and whether the model and the object packages were imported again after the last upgrade.
  • The model type, the trains, and a phase block in the controller for every automatic or semi-automatic phase on every unit and connection.
  • What each phase block does on loss of communication, tested with Simulation Manager or PhaseLogic before start-up.
  • The tag path: IBCli access names and their I/O servers, or IBMX and the Galaxy, and whether parameter values arrive before the Done status.
  • On a redundant pair: the network cards, the heartbeat link and the server clocks.
  • The History Queue database size, DBCOPY copies and SQL Server backups of batch history; the Galaxy side is in Galaxy backup and restore.

How TDL approaches it

TDL Industrial Automation is a System Integrator member of the AVEVA Partner Ecosystem. Our AVEVA service page lists AVEVA Batch Management among the AVEVA software we build, extend and maintain applications on. Our batch project at P&G Vietnam Dong An runs on FactoryTalk Batch, engineered and commissioned by TDL since 2014. The same ISA-88 ideas on Ignition: Sepasoft Batch Procedure.

Frequently asked questions

Is AVEVA Batch Management the same as Wonderware InBatch?

Yes. AVEVA's documentation states that InBatch is now AVEVA Batch Management. The old name still appears in upgrade paths, batch reports and program names such as InBatch Client (IBCli) and InBatch Message Exchange (IBMX).

Does every phase need logic in the PLC?

No. Automatic phases and semi-automatic transfer phases need a phase logic block in the control system for each unit or connection they run on. Manual and data phases are run by the Batch Management system and need no phase logic.

What happens to a running batch if the batch server stops?

In a redundant pair the backup server takes over and reads the status of running phases from the controller. After an unexpected shutdown, warm restart brings the batches that were running back in the Held state, allocated equipment stays allocated, and phases running in the controller keep running during the outage.

Can AVEVA Batch Management use System Platform objects?

Yes. Its ApplicationObject packages and the Import AVEVA Batch Management Model utility recreate the process model in a Galaxy and link the batch tags to object attributes, which IBMX reads over Message Exchange. The packages and the model must be imported again after an upgrade.

How does batch data reach the PI System?

Through the PI Interface for AVEVA Batch Management. It reads the batch history tables in SQL Server and creates event frames in PI AF, one root event frame per batch with a child for each unit procedure, together with PI points and an equipment hierarchy.

Sources

Read 17 November 2026. This article paraphrases the sources and does not quote them; read the original documents before designing or working on a system.

Related services:
Batch control (FactoryTalk Batch) AVEVA (Wonderware)