This application claims the benefit of European Patent Application No. EP 22151276.7, filed on Jan. 13, 2022, which is hereby incorporated by reference in its entirety.
The present embodiments relate to production systems and higher-level information systems.
Industrial connectors establish a connection between a production system and a higher-level information system based on a gateway solution. SiemensĀ® provides a standard way to gather machine data from control systems, third-party CNC controls, and automation technology. The service consists of consulting, implementation, and maintenance to provide seamless data transfer. The connectivity management and monitoring software running inside a gateway connecting the production system with the higher level information system may be hosted on any IPC or Virtual Machine that, for example, runs Linux Debian 9 or 10 and Docker CE. The service may also run in a virtual machine. To run the service in a virtual machine, a VMware server (e.g., supporting Debian 10) is used.
The scope of the present invention is defined solely by the appended claims and is not affected to any degree by the statements within this summary.
Process data on a manufacturing device of a production system may be continuously recorded by a gateway. This process data may be stored in a database as a time series (e.g., using InfluxDB). However, the process sequences of a manufacturing device, such as a machine tool, is not continuous, but divided into individual orders, workpieces, and processing steps. In addition, individual operations are performed with different components (e.g., different machine tools). In order to optimizations the operation of the production system and the manufacturing device, for example, and to carry out predictive maintenance or to detect wear, etc., operational data relating to a specific processing step and/or to a specific component and an indication relating to quality, component, and the like are to be provided.
Currently, the operational data may be recorded directly as individual measurements edge (e.g., using NC-trace). But then, no further adjustments may be made afterwards. Alternatively, a user may continuously store the operational data on his preferred storage platform. Then, it is possible to search for trigger values within the operational data and visualize the data for a time period selected. However, this requires manual work and is to be implemented for each manufacturing device individually. Collecting operational data of similar processes is thus not possible or becomes very tedious.
It is an object of the present invention to prepare operational data in such a way that individual process sections or stages can be selected, visualized and/or used as input data for machine learning models.
The present embodiments may obviate one or more of the drawbacks or limitations in the related art. For example, a computer-implemented method for quality inspection of a component of a manufacturing device is provided. The method includes the act of obtaining operational data relating to the operation of the manufacturing device, the operational data including a time series of one or more physical properties of the manufacturing device. The method includes the act of obtaining status data relating to a component of the manufacturing device, the status data including events relating to and/or characteristic properties relevant for the utilization of the component within the manufacturing device. The method includes the act of labelling one or more subsets of the operational data by associating one or more of the events and/or characteristic properties to the one or more subsets. The method includes the act of providing the one or more subsets as labelled training data for training a machine learning model. The machine learning model serves for outputting a quality indicator based on the labelled training data input. The method includes the act of providing the trained machine learning model for quality inspection.
As another example, an apparatus operative to perform the method acts is provided. The apparatus may include a processor and a memory.
As shown in
The tool storage device 3 includes at least one tool storage element (e.g., a depository, a suspension, a clip, a stand, or the like) for a storage (e.g., a temporary fixation) of the tool 1.
In a loading and processing step, the machine tool 4 is loaded (e.g., from tool storage device 3 or presetting and/or tool measuring apparatus 2) with the tool 1, and then, a workpiece, not shown, is processed with the machine tool 4 and the tool 1 (e.g., in one or more process sections or stages or steps). After completion of processing of the workpiece with the tool 1, the tool 1 is unloaded from the machine tool 4 and stored in storage device 3, and/or measured, and/or preset by tool presetting and/or measuring device 2. Alternatively, after completion of processing of the one or more workpieces, the tool remains in the machine tool 4 until the next usage (e.g., for processing of another workpiece).
Turning to
The gateway 21 may thus include a server that enables communication with manufacturing devices in the production system. In other words, a gateway 21 may be connected to a plurality of manufacturing devices of a production system. Hence, multiple data sources such as SINUMERIK 840D control systems, of a machine tool, or other third-party control systems may be provided, as shown in
High-frequency data acquisition in the interpolation or servo cycle of the control system of the manufacturing device may be provided (e.g., according to a configuration about every 10 ms and 2 ms). For example, the following variables may be recorded: NC-/PLC-variables, Global user data, Servo variables. This operational data may be recorded continuously or at specific points of the NC program (e.g., triggered by a start and stop condition). These conditions may be configured for data acquisition with the client C1, C2.
The gateway's 21 file transfer provides an application interface to access files located on connected manufacturing device 2, 4. This interface may be based on the standard protocol such as WebDAV. This interface allows to create, write, delete, rename, and read files and directories. This interface also allows to estimate file attributes: file size and date/time of the last change. The gateway 21 does not require a local storage for file transfer. The gateway 21 may accesses files directly on the machines. The WebDAV protocol is, for example, based on the HTTP protocol and/or is encrypted (e.g., with TLS 1.2/1.3). Thus, it is possible to access files of the connected manufacturing devices, such as machine tool 4 or apparatus 2. For the control system, it is possible to access the files from the NC as well as files from the HMI component. Thus, a software may be provided to perform inventory management on the server S1, S2 on the gateway that is connected to the one or more manufacturing device (e.g., machine tool 4). For machine tools, such a software may manage the complete tool circuit within a production system, as described in connection with
For example, as soon as an instance of a tool is created using the presetting and/or measurement device 2, the tool may be placed in the assembly container 3. The assembly state of a tool 1 may be, for example, to be obtained, to be overhauled, to be assembled, to be measured, or to be provided. Tools 1 may also be unloaded from a machine tool 4 to a container or be discarded from further usage. Further, the assembly state of a tool may be set to a state that prevents further usage of the tool. Further, an indication may be obtained that prevents further usage of the workpiece (e.g., because the workpiece is faulty and/or does not match the required quality, because the workpiece has been produced using a certain tool).
Previous solutions often only provide raw operational data. However, analyzing the operation of a manufacturing device requires a lot of pre-processing of the raw data. The present embodiments are intended to close this gap. For example, it is intended to overcome the drawbacks that the recording of operational data was only possible in an uninterrupted and continuous manner and that the operational data thus was not prepared for, for example, training a machine learning model. Further, it was not possible to assign quality data, measuring or pre-setting data, and/or tool data, or status data, in general retrospectively. Further, it was not possible to change a once set trigger or status data. Rather, the processing step (e.g., measurement) was to be re-performed in order to gain the desired augmented (e.g., labelled) operational data.
It is thus proposed as, for example, shown in
Turning to
The status data may include a tool ID, identifying the instance of a tool. The status data may include master data of the tool, the name of the tool (e.g., in the NC program). The status data may include the location of the tool (e.g., whether the tool is located in a cabinet such as the storage device or assembly container). The status data may include user defined attributes.
Turning to
Turning to
Turning to
It is an advantage of the present embodiments that the operational data is divided into individual measurements according to individual triggers. Such triggers may be introduced by a user. A trigger may be an event such as, for example, a tool insertion, and marked by tags. Additional results (e.g., on quality, events, and tool instances) may also be assigned to the individual measurements manually and automatically.
Hence, a computer program (e.g., a software) may include a function to record tool related events that may be used for tool lifecycle management. These recorded events may be used as status data. Hence, the status data may include the start and/or end of an NC program. The status data may include error data (e.g., when a NC program is interrupted). The status data may further include loading and/or unloading of a tool (e.g., in a machine tool). The status data may include a tool change (e.g., when a tool loaded in a spindle of a machine tool is successfully moved). The status data may also include one or more timestamps that are recorded when any of the above events occur. The timestamps are then assigned to the status data.
Filters may be used for limiting the amount of received tool data: The following shows the characters as they are used in the filter options described below. For example, a filter that specifies the time range within which the operational data is recorded. The general format of this filter is: Timestamp<Start time> and Timestamp <End time>.
The operational data may include sensor data, such as data reflecting the operating temperature of a machine tool.
The elements and features recited in the appended claims may be combined in different ways to produce new claims that likewise fall within the scope of the present invention. Thus, whereas the dependent claims appended below depend from only a single independent or dependent claim, it is to be understood that these dependent claims may, alternatively, be made to depend in the alternative from any preceding or following claim, whether independent or dependent. Such new combinations are to be understood as forming a part of the present specification.
While the present invention has been described above by reference to various embodiments, it should be understood that many changes and modifications can be made to the described embodiments. It is therefore intended that the foregoing description be regarded as illustrative rather than limiting, and that it be understood that all equivalents and/or combinations of embodiments are intended to be included in this description.
Number | Date | Country | Kind |
---|---|---|---|
22151276.7 | Jan 2022 | EP | regional |