Status Triggered by Meaning
Release for testing
(Page 316) menu
command
Release for produc‐
tion (Page 317)
The two releases differ only in that different permissions
and different user routines can be used.
Both releases can be started without first running the
validation check. In this case, a validation test is run
automatically in the background.
Revoke release
menu command
If a master recipe or library operation had already been
released for production, the release can be revoked (for
example to make modifications).
When updating the
process cell data
After updating, all the recipes (master recipes, library
operations) of this process cell that were "released for
production" and "released for testing" are changed to
the "Testing release" status. After updating the process
cell data, the recipes and library operations in the "Test‐
ing release" status are checked automatically. If the
check is successful, the master recipes and library op‐
erations are returned to their original status. If the test‐
ing is unsuccessful the elements will be transferred to
the status "Release invalid". They can now be edited
and depending on the project settings they can be re‐
leased again.
Difference between releasing for testing and releasing for production
In the validation for release of a recipe, you can include you own test routines. Due to the
distinction between release for testing and Release for production, separate test routines can
be processed. You could, for example, only allow water as the product for recipes released
for testing. Different user permissions can also be defined.
Recipes released for testing can also be edited directly after revoking the release. If recipes
are released for production, editing is possible only with certain settings in BatchCC (Options
> Settings > Project settings).
BATCH Control Center
9.5 Recipes
SIMATIC BATCH V8.2
314 Operating Manual, 02/2016, A5E35958174-AA
To Next Page
Loading...
Need help?
General
