Breadcrumbs

Custom mappings

With Custom mapping, it is possible to map text and values in the form of a table. It can be selected as a Metadata within the Batch definition. The function is required for the end user in the Widget: Batch control (for multi-batches).

Use Case Multi-batches:

In a multi-batch, a program run generates several different order-specific batch entries in the archive at the same time. Each batch entry in the archive that was generated by a multi-batch contains order-specific metadata. This can be entered line by line at the start of the batch. If the metadata field of the user-defined assignment is selected, the user sees the text of this assignment list as a dropdown menu. For the example below, these would be the following selection items: Drive shaft - Audi, Drive shaft - BMW, Connecting rod - Audi, Connecting rod - BMW. When the first order is added, all 4 selection fields are available. When adding the second order, the system checks whether the selection items in the list correspond to the same value as the one previously entered. If Drive shaft - BMW (value: 1) is selected, only a selection item that has the same value in the user-defined assignment can then be selected. The value of the assignment list is written to a signal as the target value when the metadata field is selected. This allows a corresponding program to be selected on the controller.

In this use case, the value of the custom mapping corresponds to a defined program on the controller. This function therefore prevents incorrect entries when selecting programs. Only orders with the same program can run within a multicharge.

What is a multi-batch? - An example:

A company called “We harden metal” wants to process several orders from its end customers (e.g., Audi, VW, Porsche) in one furnace. It uses its furnaces to harden drive shafts for its end customers.

To do this, a factory worker places several orders (drive shafts to be hardened) from its customers in the same furnace and starts the corresponding program, which hardens all drive shafts in the same way. However, the company “We harden metal” wants to store each order in the batch archive with a separate batch log, including different end customer-specific batch data. For example, the end customer Audi refers to the drive shaft that is currently being hardened as “Drive Shaft Deluxe” with order number 1234, while VW wants the metadata “Drive Shaft 42” with order number “A-W-1” to be recorded. “We harden metal” only wants to provide its end customers with their batch reports. Accordingly, each batch report may only contain the order-specific batch data of one end customer, not that of all end customers.

A program run therefore generates several different order-specific batch entries simultaneously in the archive (multi-batch).

image-20260126-074352.png
image-20260126-074456.png

Example of implementation in Widget: Batch control:

image-20260126-093617.png
Widget: Batch Control - First Order
image-20260126-093740.png
Widget: Batch Control - Second Order



Example of implementation within the Batch definition:

image-20260126-094412.png