Batch definition

Basic configuration

A name must be assigned here. The description text is optional. The group and path are filled automatically. Tags for faster searching or grouping of objects can be selected or added here.

Start-/ Stop settings

In this setting, you must select how the batch start and batch stop are defined. It is also possible to allow parallel batches. In this case, several batches can be started simultaneously with one batch definition.

To activate the release function, the check mark above must be set. A release signal is then selected. The release value, e.g., “1,” is set as the target value when the batch has been released in the Widget: Batch control. For a new batch run, this signal must be reset to the initial value, e.g., “0,” via the control (PLC) or script.

• Raised→ Event occurs

• Dropped → Event falls off

Metadata

In the metadata of the batch, freely selectable inputs can be defined. These must be entered in the Widget: Batch control at the start, at the stop, for release or during the run of a batch.

Entering metadata requires a “Type” (see table below), a “Source” (signal, manual, incremental) with information on when this query should be made (start, stop, enable), whether this entry is “Optional” or mandatory, and whether it should be “Editable” after entry. It is also possible to enter metadata validated according to “Type” and to allow only certain entries. The “Order-specific” field is selected if multi-batches are required. These metadata entries then apply only to one order, not to the entire batch.

• Signal → Metadata type is recorded by signal

• Trigger manuelly → Metadata type is entered via dashboard

• Incremental → Adds +1 to each batch start. Does not appear in the input field.

Further down in the field, you can select a “write-back signal” and define a “write-back reset value.” The write-back signal is a setpoint signal that is written as soon as the metadata field is filled in. This means that, for example, when using the “number box,” an order number can be written to a setpoint signal. The write-back reset value is written to the write-back signal when the batch is stopped.

Signals

All signals or formulas added here are assigned to the batch during the run of a batch.

Events and conditions

All events or conditions added here will be assigned to the batch during the process and can be displayed in the report.

Batch review

This setting can be used to decide whether or not a batch review is "enabled" for the batch. The batch review can be done after the batch is finished in the "Widget: Batch Archive."

New reviews can be added using the "plus symbol." The "name" and "instructions" can be freely defined and appear during the batch review.

Each reviews (line in the screenshot below) must be approved by an reviewer . The persons entered can approve in parallel. For example, representatives or persons with the same expertise could be entered here.

If the "Enforce review order" button is checked, the reviews (lines in the screenshot below) are performed one after the other. If it is not checked, the reviews can be done in parallel.

Report and export settings

By adding one or more reports, the batch can be viewed in a customized design depending on the report. In addition, it is possible to send batch reports automatically event-based in different formats by mail or to save them in a directory.

Chargenarchiv

Im Chargenarchiv werden die gleichen Informationen wie im Widget: Chargenarchiv angezeigt, inkl. aller Kopfdatenfelder.

References

All references to the batch definition are displayed in the references.

AuditLog

The AuditLog is a change log that transparently shows how the object was changed. For some objects, it also shows which target values were set by a specific person. Power users can use the button on the right-hand side to get a detailed view of exactly what has been changed in the configuration.