Contexts allow you to view plant units according to a certain viewpoint, e.g. according to a certain customer, product, job or shift.
Principle
Contexts always belong to a plant object. They are indicated as follows:
-
User-defined contexts:
Using a program created with the ODK API
-
System-generated contexts:
For installed Performance Insight and Calendar option packages: Automatically in Runtime
Example: When a shift starts in Calendar, an archived context value is created with the shift ID
Each time a context (e.g. "Product") is executed, a log entry is generated in the context log. The logged context saves:
-
The context value (e.g. "orange lemonade")
-
Start time and end time of the execution time
-
The quality code
Contexts in the trend control and alarm control
You can filter the content of these controls so that only data that has been generated in a specific plant unit and for the context you have selected is displayed. To do this, select a plant object, a context and one of its logged context values.
Example:
A press house produces juices for various beverage brands. Using contexts, employees can display in Runtime which alarms have occurred:
-
During the production of a specific product (e.g. natural apple juice, clear apple juice, pear juice)
-
For orders for a specific customer (e.g. Johnson, Smith or Miller).
-
During a specific shift (e.g. early shift, late shift, night shift).
Contexts in the "Reports" control
You have the option of linking the generation of reports to the execution of contexts.
If the templates are configured appropriately, the reports available in the control can also contain information about contexts. If a report was generated as an Excel file and reads both contexts and alarms or tag values, you can then use the Excel filter function to filter the alarms and tags by context.