Recipe management¶

The recipe management module makes it possible to,

Promote standardization through the use and exchange of recipes,
document specific production processes,
Analyse warnings and limit value violations,
visualize unstable processes for machine operators at an early stage,
to incorporate the knowledge gained into further developed formulation versions and thus
to sustainably increase the quality of production.

The continuous improvement process consists of the following recurring steps:

Recipe optimisation
Visualisation during production with SPC charts
Data recording
Evaluation of the threshold analysis
Documentation (history)
Recipe optimisation
etc. …

Creating recipes¶

The recipe settings set default values for the dynamic belt speed fixed.

Entry point¶

Click path: Menu > recipe management > recipes

It opens the recipe settings page. Here you can use the default values for the dynamic belt speed.

These settings should be adjusted before creating a structureor creates a recipe with dynamic parameters.

Recipe structures¶

A recipe structure summarizes all production-relevant measuring points of a production step or a plant.

Entry point¶

Click path: Menu > recipe management > recipe structures

It opens the recipe structure overview page. This page is the central management point for your recipe structures. All existing recipe structures are displayed here.

Interaction possibilities¶

At the end of each line is a three-dot menu that allows you to edit metadata, copy and delete the recipe structure, and other functions.

Clicking in a line switches to the detail page of the selected recipe structure. On the details page, the composition of the structure can be edited by adding or deleting measurement points.

For a better overview, these can also be grouped into categories.

Creating recipe structures¶

Create a new entry point¶

A new recipe structure can be created from the recipe structure overview page.

Click path: Menu > recipe management > recipe structures

To create a new structure, click the + New structure button on the overview page*.* A dialog opens.

Functionality¶

Enter a name and optionally a short description for the new structure. After confirming the dialog, you will automatically be redirected to the detail page of the newly created structure.

If you want to navigate back to the overview page, you can use the back button of your browser or a corresponding keyboard shortcut.

Copy recipe structures¶

You can create a new recipe structure by copying an existing structure.

Entry points for this can be found on the overview and detail pages in the menu.

When copying, you can change the name and description of the structure and optionally copy the recipes based on the structure. You will then be redirected directly to the detail page of the newly created structure.

If you copy the recipes based on the structure, they will be

copied,
counted up in their version,
set to the Draft state, and
set the reference to the freshly copied structure.

Editing recipe structures¶

Add measuring points¶

On the detail page of a recipe structure, measuring points from the tree can be added via drag & drop. A new line entry will then appear with the language-dependent measuring point name and the unit of the measuring point.

Setpoint¶

The Setpoint dropdown can be used to make a setpoint mapping. This setpoint mapping shows the setpoint of a measuring point. on transfer to the selected setpoint measurement point.

Dynamic values¶

The Dynamic button determines whether the setpoint of a measuring point always remains constant, or with the change in the Belt speed also changes.

Remove measuring points¶

The measuring point can be removed via the trash can icon at the end of the line.

Status restrictions¶

These measurement point changes are only possible in the Draft status.

Regrouping via drag & drop and reorganizing into categories, on the other hand, is possible at any time, regardless of status.

Impact on recipes¶

The changes made automatically affect all recipes made on the basis of the changed structure. Therefore, it is not possible to transfer the structures to the draft status again if one of the recipes has already been transferred.

Deleting recipe structures¶

Entry point delete structures¶

Entry points for deleting recipe structures can be found in the overview and detail pages in the menu.

Deletion transfer to recipes¶

Recipe structures form the basis for recipes. If you want to delete a recipe structure for which undeleted recipes exist, the system will inform you how many recipes are affected. To prevent careless deletion, you must specify the name of the recipe structure to be deleted again in the delete dialog. Subsequently, first the dependent recipes are deleted, then the structure itself. Transaction data remains unaffected by the deletion process, they can still be viewed via the history.

States¶

Overview¶

Structures can be in five different states. These are:

Draft¶

The structure can only be edited in this status. The addition or deletion of measuring points is only possible in this status. This is the default status for new or copied structures.

Approved¶

The structure is approved. Recipes based on them can be approved and transferred to controllers.

Approved – transmitted¶

The structure has been approved and at least one of its recipes has already been transmitted to controllers.

Locked¶

The structure has been locked. It cannot be edited and recipes based on it cannot be transferreduntil the lock is released.

Locked – transmitted¶

The structure has been locked, at least one of its recipes has already been transmitted to controllers.

Influence of status on available functionality¶

Certain functionalities are only possible in a certain state.

	Draft	Approved	Approved transmitted	Locked	Locked – transmitted
Rename	✓	✓	✓	✓	✓
Copy	✓	✓	✓	✓	✓
Add categories	✓	✓	✓	✓	✓
Delete categories	✓
Add/delete measuring points	✓
Delete structure	✓	✓	✓	✓	✓
Status change to locked	✓	✓	✓
State change to draft		✓		✓
Status change to released	✓			✓	✓

State changes¶

Entry point state changes¶

Status changes can be triggered via the menus in the overview and detail pages. Only the permitted status transitions are offered in the interface.

Influence on recipes¶

Structures form the basis for a variety of recipes. The status of structures and recipes based on them are thus interwoven.

If the status change of a structure also has effects on recipes, a dialog will appear after the attempt of the status change and inform about the effects. The process can thus be confirmed or canceled by the user.

History¶

Each status change creates a record with a time stamp that can be viewed in the history and contains the original and target status.

Possible state transitions¶

Recipes¶

A recipe enriches the basic structure with concrete values for the production of a particular product.

Entry point recipes¶

Click path: Menu > recipe management > recipes

It opens the recipe overview page. This page is the central management point for your recipes. All existing recipes are displayed here.

Interaction possibilities¶

At the end of each line is a three-point menu that allows editing metadata, copying and deleting the recipe, and other functions.

Clicking on a line switches to the detail page of the selected recipe. On the detail page, the values of the recipe can be edited. For this purpose, these can be taken over from ResMa at a certain time or maintained manually.

In the lower area of the recipe detail page, comments can be stored to attach further information to a recipe or to obtain feedback from various process participants and to document it on the recipe.

Creating recipes¶

Entry point creating recipes¶

A new recipe can be created via the recipe overview page.

Click path: Menu > recipe management > recipes

To create a new recipe, click the button + New recipe on the overview page . A dialog opens.

Functionality¶

Name, article and recipe structure are mandatory. After confirming the dialog, you will automatically be redirected to the detail page of the newly created recipe.

If you want to navigate back to the overview page, you can use the back button of your browser or a corresponding keyboard shortcut.

After creation, recipes receive a version number 1 higher than all previously created recipes of the same name. This ensures a complete and unchangeable history as a basis for documentation and visual evaluation.

Copying recipes¶

You can create a new version of a recipe by copying an existing recipe. The version number of the new recipe is automatically determined by the system.

Entry point copying recipes¶

Entry points for copying can be found on the overview and detail page of the recipes in the menu. After copying, you will be redirected directly to the detail page of the newly created version of the recipe.

Edit recipes¶

On the detail page of a recipe, different values can be maintained for a specific version. Editing is only possible in the Draft status.

If the mouse is placed over one of the values, a tooltip appears, which value type it is. Starting from the left, these are the following value types:

Minimum limit¶

This value is displayed as a red boundary line in the SPC chart. If it is exceeded downwards, this leads to entries in the threshold analysis.

Minimum warning value¶

This value is displayed as a yellow warning line in the SPC chart. If it is exceeded downwards, this leads to entries in the threshold analysis.

Setpoint¶

This value is displayed as a green line in the SPC chart. When a recipe is transmitted, this is the relevant value that is transmitted to the controller.

Maximum warning value¶

This value is displayed as a yellow warning line in the SPC chart. If it is exceeded upwards, this leads to entries in the threshold analysis.

Maximum limit¶

This value is displayed as a red boundary line in the SPC chart. If it is exceeded upwards, this leads to entries in the threshold analysis.

Dynamic setpoint configuration¶

If a measuring point is configured as dynamic, it is located to the right o Setpoint is a small button with which you can set the dynamic Setpoint configuration opens.

Setpoint¶

Here you can create an X/Y table that allows you to specify at which belt speed which target value should apply. Right Next to it, this configuration is shown. Intermediate values are used at interpolates the transmission.

Evaluation of the threshold analysis¶

The warning and limit values can also be adjusted depending on the Configure belt speed (=Relative), or with a fixed value matured (=Absolut).

Y-Axis¶

For the graphical representation, the Y-axis at Needs will be adjusted.

Apply values from ResMa¶

The button Apply values can be used to set the fixed, i.e. not dynamic measuring points of the recipes, with values from ResMa.

Filter¶

The value transfer is only applied to the measuring points that are displayed on the recipe detail page. Existing filters, e.g. on a specific unit, can therefore be taken into account in order to pre-assign only a subset.

Entry point¶

The entry point is located on the recipe detail page. To do this, click the Apply values button. It opens a dialog where the details can be configured.

Time determination¶

Here you can accept a time at which the recipe management in ResMa should search for values. If no value entry is found at the specific point in time, the last valid predecessor value is determined and adopted.

Configuration option for warning and limit values¶

The warning and limit values can be preset via an arbitrarily adjustable percentage assignment. If a calculation is not desired, a dash [ – ] can be entered in the respective field.

Copying Values¶

On the details page of a recipe, you can use the kebab menu at the end of the measuring point line to copy the set dynamic target values to other dynamic measuring points using the copy function.

Changing values manually¶

Entry point changing values¶

The values can be changed inline in the detail page of a recipe. Changes are saved automatically. This is independent of whether the values have been preset by machine or not.

Status restrictions value changes¶

Value changes are only possible in the draft state. However, it is no longer possible to switch to these if the specific version of a recipe has been transferred at least once. This ensures that history and visual evaluations cannot be manipulated.

Copy after transmission¶

If the values of an already transmitted recipe are to be edited, a copy can be created. This creates a new version that is initially in the draft state and can be edited accordingly.

Delete recipes¶

Entry point deleting recipes¶

Entry points for deleting recipes can be found in the overview and detail pages in the menu.

No effect on evaluations¶

The value configuration of a concrete version of a recipe forms the basis for the visualizations in the SPC chart and threshold analysis for its activation periods. Therefore, the data in the system is not actually deleted, but marked as deleted if activation data is present.

The deleted recipes or versions no longer appear in the recipe overview, but the evaluations are still retained.

States¶

States of recipes¶

Recipes can be in eight different states. These are:

Draft state¶

The values of a recipe can only be edited in this status. This is the default status for new or copied recipes.

Draft – Structure not approved¶

Like draft, but the underlying structure is not Approved, so this recipe cannot be approved, too.

Approved¶

The recipe has been approved and can now be transmitted.

Approved – transmitted¶

The recipe has been approved and has already been transmitted at least once. Value changes are no longer possible because it is no longer possible to switch to the Draft status.

Locked¶

The recipe has been locked. Transmission or editing is not possible in this status.

Locked – transmitted¶

As locked, but the recipe has already been transmitted at least once. It is no longer possible to switch to the Draft status.

Approved – Structure locked¶

Although the recipe has been approved, the underlying structure has been locked. A transmission is therefore not possible.

Approved – Structure locked - transmitted¶

As Approved – Structure locked, but the recipe has already been transmitted at least once. It is no longer possible to switch to the Draft status.

Influence of status on functionality¶

Certain functionalities are only possible in a certain state.

	Draft	Structure locked	Approved	Approved – transmitted	Locked	Locked – transmitted	Approved – Structure locked	Approved – Structure locked
Rename	✓	✓	✓	✓	✓	✓	✓	✓
Copy	✓	✓	✓	✓	✓	✓	✓	✓
Delete	✓	✓	✓	✓	✓	✓	✓	✓
Changing values	✓	✓
Transmit			✓	✓
Stop activation (must be active)				✓		✓		✓
Comment	✓	✓	✓	✓	✓	✓	✓	✓
Status change to locked	✓	✓	✓	✓
Status change to draft			✓		✓		✓
Status change to released	✓				✓	✓

State changes¶

Entry point state changes¶

Status changes can be triggered via the menus in the overview and detail pages. Only the permitted status transitions are offered in the interface.

History¶

Each status change creates a record with a time stamp that can be viewed in the history and contains the original and target status.

Possible state transitions¶

The graph shows the statuses and the possible transitions between them. The colors reflect the coloring in the status display and provide information about the transferability of a recipe. This is only possible in green status.

Comments¶

Entry point comments¶

Comments can be found on the recipe detail page at the bottom of the page.

Comment¶

When commenting, the user data of the logged-in user from the connected system is used.

General Data Protection Regulation (GDPR)¶

The users are only referenced by the recipe management via anonymous IDs that cannot be assigned to a user. The user names are only resolved when the page is loaded. If a user is deleted centrally from the connected system, the recipe management no longer contains any reference to the user, his name is no longer displayed.

Compare recipes¶

Entry point compare recipes¶

The comparison function can be opened via the three-point-menu in theoverview of the recipes or in the details of a recipe.

Configure comparison¶

The recipe that was used to enter the comparison function is taken over directly for the comparison.

For comparison, a recipe can be selected in the right dropdown, which is based on the same structure as the first selected recipe.

The selection in the second dropdown is thus implicitly filtered through the structure of the first recipe.

If the structure has dynamic parameters, you can also use the slider here to set different speeds for comparison.

Visualization of value changes¶

In the left column, the setpoints of the recipe of the left dropdown are displayed. The right-hand column contains the setpoints of the recipe selected in the right-hand dropdown. In the middle is the delta, which is shown as an example as follows.

Value decreased by 2:↓ 2
Value increased by 5: ↑ 5
Value was not set before, but now has a value: ↑
Value was set before, but now has no value: ↓

Transmission and activation¶

Overview¶

Recipes can be used in two different ways:

Activation only in recipe management
Transfer to plants for active control of a process

If activated only in recipe management, a corresponding transaction data record is generated within recipe management. The activation can be evaluated accordingly in the visualization options of the recipe management. This has no influence on the process and is only used for evaluation.

When transferred to systems, setpoints and the ID of the recipe are actually transferred. Activation takes place at the control level via an HMI. The transaction data record is only generated after activation and confirmation of the changed recipe ID. The evaluation options are identical to the exclusive activation within the recipe management.

Entry point¶

The functions can be started via three-point menu in the recipe overview page or the recipe detail page. There are individual entry points for the two approaches.

Transfers of dynamic recipes¶

If a recipe has dynamic parameters, you can use the transfer / Select the desired belt speed. This belt speed is also stored in the history.

Prerequisites for transfer to PLCs¶

In order for setpoints to be transferred to the process, mappings for setpoints and recipe ID must be made within the recipe structure.

Setpoint mapping

Entry point: Structure detail page, three-point menu behind measuring point, setpoint link option
Setpoint data point: Data point to write to when the recipe is transferred.

Mapping for Recipe ID

Entry point: Edit dialog of a structure – accessible via three-point menu in structure overview page or structure detail page
Current value data point: Data point to which the recipe ID is transferred when activated by the HMI. The data point must be recorded when the value changes! Before the transfer, it is checked whether a connector connection is configured. If not, a transfer is not possible.

Setpoint data point: Data point to which the recipe ID is to be written during transmission. Must be available on controller and transferred to the actual data point when activated in the HMI! Before the transfer, it is checked whether a connector connection is configured. If not, a transfer is not possible.

Technical transfer overview¶

Effects of a transfer or activation¶

As soon as a recipe is transferred or activated for the first time, the recipe itself or its structure can no longer be changed. This results in a complete versioning and visual evaluation option for certain versions of a recipe.

Automatic measuring point creation after transmission and activation¶

When a recipe is transferred and activated, ResMa automatically creates a measuring point for the underlying recipe structure. The measuring point is initially flat below the first location in the object tree, but can be moved as desired. The measurement points are named according to the scheme Recipe_[RecipeStructureNameGoesHere]_History . They must not be renamed.

If the recipe ID in the LiveValueCache changes for this recipe (measuring point for reading out the recipe ID), another entry is written to the automatically created measuring point. An entry contains the timestamp of the change as well as the name and version of the activated recipe. The measuring point can be e.g. used for visualization in the ResMa Chart.

If recipes are only activated but not transferred to the controllers, no automatic measuring points are created.

Overview of recently activated recipes¶

Overview¶

The activation overview lists the most recent activations and thus allows a quick overview of the most recent activations. By default, the entries are sorted in such a way that the most recent activations are at the top of the list. It is sorted by time of activation.

Entry point¶

Click path: Menu > recipe management > overview

SPC Chart¶

Statistical Process Control Charts (SPC Charts) make it possible to display actual process values as well as setpoint, warning and limit values.

Entry point¶

Click path: Menu > recipe management > SPC chart

A placeholder page appears. After adding the first measurement point, the chart is shown.

Add measuring points¶

Measuring points can be dragged & dropped from the object tree into the chart.

Remove measuring points¶

Below the chart is the configuration legend. Via the trash can button, traces can be permanently removed from the chart.

Hide tracks temporarily¶

Tracks can be temporarily hidden to make the chart clearer. To do this, click on the legend entry of the track, no matter in which legend.

If you click again, the track will be displayed again.

However, traces that are permanently no longer needed should be deleted, as the hidden traces still have to be determined by the server in terms of data. This increases server load, network load, and makes legends confusing.

Highlight traces¶

Individual tracks can be highlighted for a short time if the mouse pointer is positioned over the track in the chart directly or above the legend entry of the track in the simple legend.

Datazoom¶

Below the chart is a bar that is a preview of the top track in the configuration legend. The data zoom of the bar can be reduced and moved to see details in the chart. The data is not requested again from the server. The entire available period is defined via the Time Range Chooser above the chart.

Time Selection¶

The selected time range via the Time Range Chooser above the chart determines which data is requested from the server when the chart is called. Therefore, the period should be kept as large as necessary but as small as possible. Unnecessary data requests increase server and network load, as well as wait times for the chart to load.

Live Data¶

The chart automatically switches to live mode if the following conditions are met:

The selected period in the Time Range Chooser is less than or equal to one hour
The endpoint is no earlier than 5 minutes before the current server time
The aggregation of the track is based on raw data

The easiest way to meet the time limits is to select the Last Hour quick option in the Time Range Chooser.

View limit values¶

Limit consideration can be enabled by doing the following in the configuration legend for a track:

Click path: Menu > Recipe > activate

One limit view can be active for each chart group.

Split traces on charts¶

Using the grouping function, the traces can be distributed to up to three charts. To do this, the chip must be set accordingly in the Group column of the configuration legend.

Hide configuration legend¶

Between the Datazoom element and the configuration legend there is a small grey bar in the middle. Here, the height of the configuration legend can be determined by clicking and dragging and the legend can even be hidden completely.

Threshold analysis¶

Threshold analysis make it possible to quickly record the exceedance of warning and limit values and to branch them into a detailed analysis. The evaluation is available on a daily and monthly basis.

Entry point¶

Click path: Menu > recipe management > threshold analysis

A placeholder page appears. After adding the first measurement point, the analysis is shown.

Add measuring points¶

Measuring points can be dragged & dropped from the object tree to the analysis.

Remove measuring points¶

Measuring points can be removed from the threshold analysis via a dialog. The dialogue can be achieved as follows:

Click path: Threshold analysis > Three-dot menu > Data

Sort measuring points¶

The order can be defined by drag & drop in the data dialog. The dialogue can be achieved as follows:

Click path: Threshold analysis > Three-dot menu > Data

Temporarily hide value ranges¶

Individual areas such as warning values can be hidden by clicking on the legend entry for warning values. With a second click, the values are displayed again.

Highlight ranges of numbers¶

Individual number ranges can be temporarily highlighted by positioning the mouse over the range selector next to the legend on the desired number. All occurrences of this number in the limit analysis are then highlighted.

Restrict Number Ranges¶

The range selector next to the legend can be changed in its boundaries to display only a certain interval of numbers in the limit analysis. For example, the view can be focused on very frequent transgressions.

Open detailed chart¶

A detailed view can be opened for each tile display by clicking in the corresponding tile. Below the threshold analysis, an SPC chart opens for the clicked tile, which automatically determines the data point and time series.

By clicking on the tile again, the SPC chart is closed again.

Time Selection¶

The time selection is done via the Time Range Chooser above the threshold analysis. Due to the structure and the amount of data, the selection is limited to months and days.

By means of the offset, a temporal shift reference can be established for daily or monthly evaluations by starting the evaluation at 6 o’clock in the morning or with an offset of 6 hours.

History¶

The history is a table-based view that makes it possible to trace logged events in a tamper-proof manner.

Entry point¶

The history can be opened in different ways. The general way is via the menu.

Click path: Menu > recipe management > history

If you want to see the history entries of a certain structure or recipe, you can also branch to the history via the context menus in the respective overview or detail pages. A filter is given directly to the respective structure or recipe.

Types of entries¶

Four types of entries are logged and displayed:

Status change of structures
Status change of recipes
Transfers of recipes
Activation of recipes

Permissions¶

When the service is started, recipe management logs on various authorizations to the base system, which can be assigned via the familiar interface.

Permission enforcement is achieved at two levels:

Unauthorized entry points are not displayed to the user
The user’s API calls for this function are rejected by the server