Learn about batch interface overview

PI Interface for ABB 800xA Batch is classified as a PI interface for Batch Execution Systems (BES) and Manufacturing Execution Systems (MES), which are based on a common framework.

Note: If you record batch process data directly to PI tags and do not use a BES, you can generate batch data from PI tag data using the PIEFGEN utility,

PI Batch Interfaces are scan-based interfaces that populate the PI Asset Framework (PI AF) database with event frames and elements.

Note: To use event frames, your PI batch interface must be version 3.x or higher.

Batch interfaces can read data from multiple data sources, which enables the PI server to handle scenarios in which different overlapping batch recipes can access the same unit in different stages of the production cycle. By acquiring data for the same time frame from multiple sources and collating it into a single time-ordered sequence, a single interface instance can capture the complete history of the batch process.

Note: These interfaces are designed for recipes that constrain a unit to run only one unit procedure at a time.

Two different models are used to describe batch processes:

1. The equipment model describes the physical equipment necessary to create a batch.

2. The recipe model describes the procedures that are performed during the execution of a recipe.

There is no intrinsic or direct relationship between the models. With the exception of arbitration events, journal files contain only recipe model event information.

The interface is compliant with the ISA S88.01 standard and uses the S88 process model, which is composed of the following hierarchy:

• Procedure (recipe)

• Unit procedures

• Operations

• Phases

• Phase steps

• Phase states

  Note: According to the ISA S88.01 standard, procedures and unit procedures are optional. A recipe can be composed solely of operations and phases.

The physical model is composed of the following equipment-oriented hierarchy:

• Enterprise

• Site

• Area

• Process cell

• Unit

• Equipment module

• Control module

Unit procedures from the data source are mapped to Unit Procedure level event frames. Event frames support parallel unit procedures natively. Only a single unit procedure can be active in a unit at any given time, which restricts the configuration of recipes that can be run by the batch execution system if batch data is to be captured by the interface in a reliable and meaningful way. By contrast, event frames support parallel unit procedures natively.

You can configure the interface to create PI points and properties by defining templates, which specify the events that trigger creation, configure how the property or tag is named, and define the data to be stored.