Container Line Settings Versioning for Safe Commissioning Changes
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The container treatment system faces challenges in optimizing setting value data sets due to numerous interdependent parameters, leading to lengthy commissioning times and potential production downtimes, especially when introducing new products or dealing with environmental fluctuations, which requires cumbersome workarounds to maintain production quality and safety.
Innovation Solution
A container treatment system with a management device that creates and manages main and minor versions of setting value data records, assigning status and access rights based on operator authorization, ensuring safe and flexible operation by tracking changes and maintaining only one current data record.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If setting value data sets are optimized through multiple test runs during commissioning, then production quality is improved, but commissioning time increases significantly
Solution Approach 1:
The system performs preliminary optimization of setting value data sets through test runs during the commissioning phase before actual production begins. The management device stores multiple optimized versions of setting value data sets, so that once commissioning is complete, production can proceed without repeated test runs, thus improving quality while limiting time loss to the initial commissioning period only.
2Adaptability or versatility
If operators make permanent adjustments to setting value data sets to compensate for environmental fluctuations, then operational flexibility is improved, but risk of machine damage or quality impairment increases
Solution Approach 1:
The management device acts as an intermediary between operators and the setting value data sets. It provides a controlled interface that allows operators to load different pre-stored versions of setting value data sets adapted to various environmental conditions, while preventing direct unauthorized modifications that could damage the machine or compromise quality. This enables operational flexibility through selective loading of appropriate settings without the risks of arbitrary changes.
3Productivity
If multiple users work with setting value data sets simultaneously during commissioning and production, then system productivity is improved, but data integrity and tracking become difficult
Solution Approach 1:
The management device creates and manages multiple copies of setting value data sets, each with a unique version identifier. When users need to work with settings, they load specific versions rather than editing a single master copy. This allows multiple users to work simultaneously with different versions without interfering with each other, while the version tracking system maintains complete information about what settings are being used by whom, eliminating data integrity issues.
Data Source
Figure 1
Figure 2
Figure 3
AI summary
The invention relates to a container-processing system (1) and to a method having safety-oriented management of settings for a container-processing system. The container-processing system (1) comprises: at least one container-processing machine (10, 20, 30, 40) for processing containers (5), at least one container-processing machine (10, 30, 40) having a type memory (11, 31, 41), in which different data sets (111, 112; 311, 312, 313; 411, 412) for types of processing to be performed by the container-processing machine (10, 30, 40) are stored and can be selected for processing containers (5); and at least one management device (13; 130) for managing the storing of the data sets (111, 112; 311, 312, 313; 411, 412), the at least one management device (13; 130) being designed, in the event of the creation of one of the data sets (111, 112; 311, 312, 313; 411, 412), to produce a main version (V1_A to V1_D) of the data set (111, 112; 311, 312, 313; 411, 412) and to assign a status (A to D) to the main version (V1_A to V1_D), to retain the main version (V1_A to V1_D) if a change is made to the main version (V1_A to V1_D) without a change in the status (A to D) and to additionally create, for the change to the main version (V1_A to V1_D), a secondary version (V1.1_A to V1.N_A; V1.1_B to V1.N_B; V1.1_D to V1.N_D) having the status (A to D) of the main version (V1_A to V1_D), and to set the scope of the access to the main version (V1_A to V1_D) and to the at least one secondary version (V1.1_A to V1.N_A; V1.1_B to V1.N_B; V1.1_D to V1.N_D) by an operator (18, 38, 48) of the at least one container-processing machine (10, 20, 30, 40) in dependence on the status (A to D) and a predefined authorization of an operator (18, 38, 48).