Introduction to PI Interface for Siemens SIMATIC Batch

PI Interface for Siemens SIMATIC Batch uses Siemens PI CONNECT Simatic Batch API to collect batch data from the Siemens SIMATIC system. The interface can be configured to associate batch data with PI Tags or PI Batch properties.

This interface requires the Siemens PI CONNECT Simatic Batch API to function. You can obtain this API in the form of a DLL file (PIConnectSimatic64.dll) from Siemens.

The interface is based on a common framework discussed in this guide. See How PI interfaces for batch and manufacturing execution systems work for a detailed overview of AVEVA's batch interface operations.

Data collection options

PI Interface for Siemens SIMATIC Batch is a scan-based interface that can be configured to populate the PI Asset Framework (PI AF) database with event frames and elements.

This interface can be configured to create and update PI tags based on the data received. The interface cannot update the batch data source.

The following diagrams illustrate the options for configuring the interface, depending on the data source and the desired PI System output. The data from various data sources is targeted to a PI AF server.

In the first diagram, the Siemens SIMATIC data source server targets PI AF and populates it with event frames and elements.

Siemens SIMATIC populates PI AF

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

Multiple data sources

PI Interface for Siemens SIMATIC Batch can read data from multiple data sources, which enables the PI System 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.

Buffering and failover

PI Interface for Siemens SIMATIC Batch does not use PI buffering. Batch data is persistent in the data source and not in danger of being lost.

• If the interface loses its connection to the PI Data server, it continues to collect data from the data source, transmitting it to the server when the connection is reestablished.

You need not configure failover for batch interfaces. If for any reason the interface is unable to collect data, the data remains available in the database or event files and you can use recovery mode to fill in any data that was missed during the time the interface was down.

Processing models

Two different models are used to describe batch processes:

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

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

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

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

ISA S88.01 standard

PI Interface for Siemens SIMATIC Batch is compliant with the ISA S88.01 standard, under which procedures and unit procedures are optional. A recipe can be composed solely of operations and phases.

The S88 process model is composed of the following hierarchy:

• Procedure (recipe)

• Unit procedures

• Operations

• Phases

• Phase steps

• Phase states

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 PI UnitBatches. 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 interfaces to create PI tags 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. See Create and configure the interface instance for detailed information on configuring PI Interface for Siemens SIMATIC Batch.