Procedures and systems for managing data about a warehouse

Abstract

Computer-implemented method (200) for managing data (115, 305) about a warehouse (102) by the manufacturer or by third parties, in particular customers, wherein the bearing (102) comprises several bearing components, and wherein the bearing (102) is manufactured from the several bearing components in a production process, including the following steps: Recording (210) the data (115, 305) about the multiple bearing components and / or about the production process by the manufacturer, Storing (214) the data (115, 305) in a manufacturing database (315) by the manufacturer, Generating (220) a machine-readable identifier (165, 365) for the unique identification of the bearing (102) by the manufacturer, wherein the machine-readable identifier (165, 365) is assignable to the data (115, 305), and wherein the machine-readable identifier (165, 365) is arranged on the bearing (102), from the set of data (115, 305) of the manufacturing database (315), copying (230) of storage usage-relevant data (125, 335) into a customer database (325), Reading (250) the machine-readable identifier (165, 365) on the bearing (102) by third parties, in particular by the customer, Activating (254) access to the customer database (325) for the warehouse usage-relevant data (125, 335) assigned to the machine-readable identifier (165, 365), Retrieval (260) of some or all of the storage usage-relevant data (125, 335) from the customer database (325) by third parties, in particular by the customer, and Processing (264) the retrieved data for a warehouse-specific activity by third parties, in particular by the customer, wherein the retrieved data are usable for the warehouse-specific activity, and wherein the warehouse (102) is used for the warehouse-specific activity, the process further comprising: Collection (270) of operational data (395) about the warehouse during location-specific activity by third parties, in particular by the customer, Processing (274) the operational data (395), and / or Storing (276) the operational data (395) and / or the processed operational data in a client database (385) Sending (280) the operational data (395) and / or the processed operational data to a database, in particular to the customer database (325), and Storing (284) the sent data in the database, in particular in the customer database (325).

Description

Field of invention

[0001] The present invention relates to a system for the IT-integrated management of data about a warehouse, comprising a server system and a client system. The invention further relates to a computer-implemented method for managing data about a warehouse and a computer program product for executing the computer-implemented method. Background of the invention

[0002] For bearings, especially rolling bearings, it is common practice to use barcodes or Data Matrix codes for serialization purposes or to directly affix bearing-specific data to the product. It is also common to include slips of paper with bearing-specific data in the packaging. This data is generally only accessible to the customer on the corresponding slip. If the written information is lost, important details such as tolerances required for assembly are missing. Documentation of bearing service life data is also generally done by taking written notes and subsequently scanning them. However, these digitized notes are usually in a file format unsuitable for data processing. Furthermore, they must be manually matched to the manufacturer's bearing-specific data.New bearing-specific manufacturer information, which may result, for example, from the manufacturer's long-term tests, must also be manually transmitted, assigned and entered.

[0003] DE 102 56 260 A1 describes a method for product verification, e.g., for pharmaceutical and medical products, wherein each product item (1) is marked with a code (12). The code identifies the product in a remote database (15) and also contains an identifier for the database, which a verification device (17, 18) uses to address the database. An independent statement is made for a product verification device.

[0004] DE 102 01 021 A1 describes a method for maintaining a manufacturing plant with several field devices connected to a control system via a data bus D. This includes the electronic recording of the field devices in a manufacturer's database with a manufacturer-specific identification and manufacturer-specific information relevant for maintenance, the electronic recording in a customer database with a customer-specific identification and customer-specific information, and an electronic database query for maintenance criteria across both databases.

[0005] DE 11 2004 001 668 B4 describes a machine component with an IC marking attached to it, such as a rolling bearing arrangement with an IC marking attached to a component or accessory. DE 10 2009 010 022 A1 describes a machine element with a marking arranged on a surface, which includes a partial marking applied to a section of the surface, wherein the roughness in the area of ​​the partial marking is lower than in the section of the surface adjacent to the partial marking. Summary of the invention

[0006] The object of the invention is to enable the digital management of data concerning a warehouse, from production at the manufacturer to use at the customer's site, throughout the warehouse's entire lifespan. This involves ensuring that each specific warehouse can be uniquely assigned to its warehouse-specific data, and that the data is electronically available, searchable, editable, supplementable, and at least exchangeable between the manufacturer and the customer, or other third parties. In particular, the invention aims to prevent disruptions in the communication medium and data formats for the warehouse-specific data.

[0007] This technical problem is solved according to the invention by the technical features of the independent claims in the form of a method that is at least partially computer-implemented, a computer program product, a server system, a client system, and a system comprising a client and server system.

[0008] Accordingly, the inventive method for managing data about a warehouse by the manufacturer or by third parties, in particular customers, wherein the warehouse comprises several warehouse components, and wherein the warehouse is manufactured from the several warehouse components in a production process, includes the acquisition of data about the several warehouse components and / or about the production process by the manufacturer.

[0009] In one embodiment, the bearing comprises the bearing components inner ring and outer ring and can be a rolling bearing or a plain bearing. Component-specific data is available for the bearing components. Furthermore, additional data, such as measurement data, is generated during the production process. For example, the inner ring and outer ring are paired, resulting in each bearing having specific tolerances. This tolerance data is relevant, for instance, for bearing assembly. Tolerance data is particularly important for spindle bearings used in high-precision machine tools.

[0010] The inventive method further comprises the storage of data in a manufacturing database by the manufacturer and the generation of a machine-readable identifier for the unique identification of the bearing by the manufacturer. The machine-readable identifier is associated with the data and is located on the bearing. For example, the machine-readable identifier can be located on the outer ring. This has the advantage that the machine-readable identifier is easily accessible for contactless reading. A machine-readable identifier can, for example, be a two-dimensional barcode, such as a Data Matrix code, which is applied laterally to the outer ring using a laser or etching process. An RFID chip, which is arranged in or embedded in a bearing component of the bearing, is also conceivable.

[0011] Furthermore, the inventive method comprises copying inventory-relevant data from the data set in the manufacturing database into a customer database. In other words, the inventive method comprises making inventory-relevant data available in a separate database, and thus withholding, for example, confidential production data from which conclusions about the production process could be drawn.

[0012] In an alternative embodiment, the manufacturing database and the customer database are the same database, with the relevant data being marked as retrievable. From a database perspective, this can be achieved, for example, by granting read access to specific database users. The only essential requirement is that it is ensured that confidential data, if any, can be kept confidential.

[0013] Furthermore, the inventive method comprises the reading of the machine-readable identifier by a third party, in particular by the customer, at the warehouse and the activation of access to the customer database for the warehouse usage-relevant data assigned to the machine-readable identifier. The reading of the machine-readable identifier can be carried out using a client system, such as a portable smartphone with a camera. The client system can be used at the customer's site, even if the customer does not yet have warehouse usage-relevant data available.

[0014] In an alternative embodiment, before granting access to the customer database, the inventive method can include storing the machine-readable identifier in an authentication database to verify its authenticity, thus enabling a prior verification of the warehouse's authenticity by querying the authentication database. If the machine-readable identifier is authentic, access to the customer database is granted. This has the advantage of enabling the detection of counterfeit warehouses. Authentication can be performed, for example, via trusted third-party providers. Alternatively, authentication can be implemented using the manufacturer's own system.

[0015] Furthermore, the inventive method comprises the retrieval of some or all bearing-related data by third parties, in particular by the customer, from the customer database and the processing of the retrieved data by third parties, in particular by the customer, for a bearing-specific activity, wherein the retrieved data is usable for the bearing-specific activity. For example, the customer can retrieve only specific bearing-related data, such as a measured value that the customer requires to calculate an assembly setting for the bearing in the machine.

[0016] When all data is retrieved, one embodiment of the method offers the option of storing the retrieved data in a client database. It is also possible to store only partially retrieved data or processed data in the client database.

[0017] The warehouse-specific activity is, for example, at least one of the following activities: - Mounting the bearing in a machine, - Use of the data in a computer-implemented warehouse management system, in particular for ordering new bearings or spare parts for the warehouse, - Commissioning of maintenance contracts, - Control or fine-tuning of the machine with the bearing to improve a production process, whereby the machine is used in the production process, or - Technical monitoring of warehouse operations.

[0018] According to the invention, the bearing is used for a bearing-specific activity, for example, the bearing can be monitored (condition monitoring), and the method according to the invention further comprises acquiring operating data about the bearing during this bearing-specific activity. The operating data, such as lubricant composition, are further processed according to the invention to, for example, calculate the remaining service life of the bearing, and / or the processed data are then stored in the client database. According to the invention, the acquired operating data are stored directly in the client database. It is conceivable, at least, that acquired and processed operating data are stored in the client database at each process step. Thus, it is possible to secure continuous documentation of the bearing's operation, which enables a subsequent evaluation of the bearing history.

[0019] In one embodiment, the method further includes sending and storing the operating data and / or the processed operating data in a database. This database can be the customer database. Other databases are also conceivable, which, for example, are connected to systems for specialized analysis of the operating data. Thus, it is possible that measured values ​​concerning the lubricant composition of the bearing can be better evaluated by the lubricant manufacturer than by the bearing manufacturer.

[0020] The data or operational data may include one or more of the following data types: - Measurement data about bearing components or bearings (bore diameter, outer diameter, width, pressure angle, protrusions, impact values, load ratings, rolling frequencies, weights, material specifications) - Production data about the warehouse (production date, serial number, description) - Tolerance data, - Calculation data, - Sales data via the warehouse, - Calculation data for assembly.

[0021] Another aspect of the present invention is a computer program product which, when loaded into a memory of a data processing system and executed by at least one processor of the data processing system, performs the steps of the computer-implemented method.

[0022] Further aspects of the present invention include a server system for processing data about a warehouse, a client system for processing warehouse-related data about the warehouse, and a system for managing this data, comprising a client system and a server system as described above and below. The system for managing data about a warehouse can therefore include the features of a client-server architecture and / or equivalent computer-to-computer connections, for example, a peer-to-peer architecture.

[0023] Further advantages, features and details of the invention will become apparent from the exemplary embodiments described below and from the drawings. Brief description of the drawings

[0024] Exemplary embodiments of the invention are illustrated below with reference to figures. The figures are unscaled drawings. They show: Fig. 1. An overview of an IT-integrated management of data about a warehouse, Fig. 2. A flowchart of a computer-implemented procedure for managing data about a warehouse, and Fig. 3. A block diagram for a system for managing data about a warehouse. Detailed description of the drawings

[0025] Fig. Figure 1 shows an overview diagram for an IT-integrated management system for data 105, 106, 107, 108, 115, 125, 185 via a warehouse 102. The overview diagram is divided into an area 100, which concerns the management and processing of data 105, 106, 107, 108, 115, 125 on the manufacturer's side, and an area 101, which concerns the management and processing of data 185 on the customer's side during warehouse use. Warehouse 102 is the same warehouse in both areas 100 and 101, once during production and at a later point in operation, for example, when used in a spindle bearing. Areas 100 and 101 are separated by the dashed line 142 in Figure 1. Fig. 1 separated. Areas 100 and 101 can be geographically separated, with a server system 110 in area 100 connected to a client system 160 in area 101 via a data connection 140 for data communication.

[0026] Fig. Figure 1 further shows various data items 105, 106, 107, 108, which are recorded as warehouse data 115 in server system 110. A Data Matrix code 165 is also stored in server system 110, which can be uniquely assigned to warehouse data 115, or conversely, warehouse data 115 can be uniquely assigned to Data Matrix code 165. Data Matrix code 165 is also applied to warehouse 102. Thus, warehouse 102 can be uniquely assigned to warehouse data 115, and vice versa. Server system 110 also includes warehouse usage-relevant data 125, which essentially represents a subset of warehouse data 115.

[0027] In Fig. Figure 1 shows client system 160 in area 100. Such a client system could be, for example, a portable smartphone 161 or tablet device. It could also consist of several individual devices, such as a scanner that transmits the scanned data to a laptop. Client system 160 is configured to scan the Data Matrix code 165 on warehouse 102 and evaluate it accordingly. Client system 160 can thus, for example, store data 185 about the operation of the warehouse in conjunction with the associated Data Matrix code 165. Client system 160 can also retrieve warehouse usage-relevant data 125 that is assigned to the Data Matrix code 165. Furthermore, client system 160 can process the data 185, including retrieved data 125, and save calculation results.Alternatively or additionally, the client system 160 can transmit the data 185 or calculation results back to the server system 110 via a data connection 140. The transmitted data can be stored together with the warehouse usage-relevant data 125.

[0028] Fig. Figure 2 shows a flowchart of a computer-implemented method 200 for managing data about a warehouse, wherein the warehouse comprises several warehouse components and wherein the warehouse is manufactured from the several warehouse components in a production process. The method comprises: capturing 210 the data about the several warehouse components and / or about the production process, storing 214 the data in a manufacturing database, generating 220 a machine-readable identifier for the unique identification of the warehouse, wherein the machine-readable identifier is associated with the data, and wherein the machine-readable identifier is located at the warehouse.The procedure further comprises copying 230 warehouse usage-relevant data from the set of data into a customer database, reading 250 the machine-readable identifier on the warehouse, enabling 254 access to the customer database for the warehouse usage-relevant data assigned to the machine-readable identifier, retrieving 260 some or all of the warehouse usage-relevant data from the customer database, and processing 264 the retrieved data for a warehouse-specific activity, wherein the retrieved data is usable for the warehouse-specific activity.

[0029] Furthermore, the procedure comprises 200 optional process steps, which are described in Fig. 2 are shown with dashed lines. Thus, the procedure includes storing 262 of the retrieved and / or processed data in a client database.

[0030] Optionally, when using the warehouse for warehouse-specific activities, procedure 200 includes the acquisition 270 of operational data about the warehouse during the warehouse-specific activity and the processing 274 of this operational data. The processed operational data can then be stored 276 in the client database or alternatively sent directly to another database 280. Another option is to store the acquired operational data unprocessed in the client database 276, or to send it unprocessed to another database 280. The sent data is then stored in the other database 284. This other database could, for example, be the customer database, allowing for further evaluation of the acquired and / or processed operational data on a server system. The other database could also be part of a separate server system used solely for evaluating the sent data.

[0031] Optionally, the procedure 200 further includes storing 225 the machine-readable identifier in an authentication database to verify the authenticity of the machine-readable identifier (and thus the warehouse), verifying 227 the authenticity by querying the authentication database, and, if the machine-readable identifier is authentic, proceeding with activating 254 access to the customer database. The storage 225 and verification 227 steps can be separated in time. In particular, it is possible that the storage 225 of the machine-readable identifier takes place on a trusted third-party server, and the verification 227 of the authenticity of the machine-readable identifier (and thus the warehouse) is carried out directly with this third-party server.In other words, the third-party provider can act as a trusted entity between a manufacturer and a customer to execute these optional procedural steps of the computer-implemented process.

[0032] Fig. Figure 3 shows a block diagram for a system 300 for managing data 305, 335, 395 about a warehouse. The system 300 comprises a server system 310 and a client system 360, with the server system 310 and the client system 360 connected via a data link 340 for data communication. The server system 310 and the client system 360 can be located in geographically different locations. It is also possible for multiple client systems to communicate with the server system 310 and exchange data. A client system 360 can also contact multiple server systems 310. This can be useful, for example, when evaluating measurement data from warehouse operations, such as one server system for evaluating lubricant measurements and another server system for evaluating slip measurements in a rolling bearing.

[0033] The server system 310 for processing data 305 about the warehouse, wherein the warehouse comprises several warehouse components, and wherein the warehouse is manufactured from the several warehouse components in a production process, comprises a first interface component 312 configured for capturing the data 305 about the several warehouse components and / or about the production process, a data storage component 314 configured for storing the data in a manufacturing database 315, and at least one processor component 322 configured for the following processing steps: generating a machine-readable identifier 365 for the unique identification of the warehouse, wherein the machine-readable identifier 365 is assignable to the data 305, and wherein the machine-readable identifier 365 is located at the warehouse, identifying warehouse usage-relevant data 335 from the data 305, and copying the warehouse usage-relevant data into a customer database 325.

[0034] Furthermore, the server system 310 can have a second interface component 332, as shown in Fig. 3 shown, include, which is configured to send the machine-readable identifier 365 to an authentication system 350 with an authentication database 355.

[0035] The client system 360 for processing warehouse usage-relevant data 335 about the warehouse comprises a read component 362 configured for reading a machine-readable identifier 365 on the warehouse, an interface component 372 configured for sending an access request for access to a customer database 325, wherein the access request includes the machine-readable identifier 365, and at least one processor component 374 configured for the following processing steps: retrieving some or all warehouse usage-relevant data 335 from the customer database 325, and processing the retrieved data for a warehouse-specific activity, wherein the retrieved data is usable for the warehouse-specific activity.

[0036] Furthermore, the client system can 360, as in Fig. Figure 3 shows a data storage component 382 that is configured to store the retrieved and / or processed data in a client database 385.

[0037] Furthermore, the interface component 372 of the client system 360, as described in Fig. As shown in Figure 3, it should be configured so that the access request is sent directly to the server system 310 with the customer database 325. In this case, the authentication system 350 will not communicate with the client system 360. Alternatively, also in Fig. Figure 3 illustrates that the access request can be sent to the authentication system 350 with the authentication database 355 to verify the authenticity of the machine-readable identifier (and thus of the warehouse).

[0038] Furthermore, the client system can 360, as in Fig. Figure 3 shows a further interface component 392 that is configured to acquire operational data 395 about the warehouse during the location-specific activity, and at least one processor component 374 can be further configured to process the operational data 395.

[0039] The data storage component 382 of the client system 360, as in Fig. As shown in 3, it can be further configured to store the operational data 395 and / or the processed operational data in the client database 385.

[0040] The interface component 372 of the client system 360, as described in Fig. 3 shown, can be further configured to send the operational data 395 and / or the processed operational data to a database, in particular to the customer database 325.

[0041] Databases 315, 325, 355, and 385 are in Fig.Figure 3 shows the system boundaries of the corresponding systems 310, 350, and 360. This is intended to illustrate that databases 315, 325, 355, and 385 do not necessarily have to be integrated into the systems or implemented as part of the system. It is also possible for the databases to be implemented in a physically separate system, for example, as cloud storage. This has the advantage that the stored data can be easily backed up, for example, using data mirroring or automated data backups. It also allows multiple systems to access the data. Furthermore, losing or damaging the client system in the field is less critical, as the data is not lost, or not completely lost. Reference symbol list 100, 101, 142 Principled areas of data administration and processing 102 warehouses 105, 106, 107, 108, 115, 125, 185 Data 110 server systems 140 data connection 160 Client System 161 Smartphone 162 Scans 165 Data Matrix Code 200 Computer-implemented method for managing data about a warehouse 210, 214, 220, 225, 227, 230, 250, 254, 260, 262, 264, 270, 274, 276, 280, 284 Procedure steps of the computer-implemented procedure 200 300 System for managing data about a warehouse 305, 335, 395 data 310 Server System 312, 314, 322, 332 Components of the server system 310 315, 325, 355, 385 databases 340 data connection 350 authentication system 360 Client System 365 machine-readable identifier 362, 372, 374, 382, ​​392 Components of the Client System 360

Claims

[1] Computer-implemented method (200) for managing data (115, 305) on a warehouse (102) by the manufacturer or by third parties, in particular customers, wherein the bearing (102) comprises a plurality of bearing components, and wherein the bearing (102) is manufactured from the plurality of bearing components in a production process, comprehensively the following steps: Recording (210) of the data (115, 305) about the plurality of bearing components and / or about the production process by the manufacturer, Storing (214) the data (115, 305) in a manufacturing database (315) by the manufacturer, generating (220) a machine-readable identifier (165, 365) for the unique identification of the bearing (102) by the manufacturer, wherein the machine-readable identifier (165, 365) is assignable to the data (115, 305), and wherein the machine-readable identifier (165, 365) is arranged on the bearing (102), from the set of data (115, 305) of the manufacturing database (315), copying (230) of warehouse usage-relevant data (125, 335) into a customer database (325), Reading (250) of the machine-readable identifier (165, 365) on the warehouse (102) by third parties, in particular by the customer, Activating (254) access to the customer database (325) for the warehouse usage-relevant data (125, 335) assigned to the machine-readable identifier (165, 365), Retrieval (260) of some or all warehouse usage-relevant data (125, 335) from the customer database (325) by third parties, in particular by the customer, and Processing (264) the retrieved data for a warehouse-specific activity by third parties, in particular by the customer, wherein the retrieved data can be used for the warehouse-specific activity, and wherein the warehouse (102) is used for the warehouse-specific activity, the method further comprising: Collection (270) of operational data (395) about the warehouse during the location-specific activity by third parties, in particular by the customer, Processing (274) of the operating data (395), and / or Storing (276) the operating data (395) and / or the processed operating data in a client database (385) Sending (280) the operating data (395) and / or the processed operating data to a database, in particular to the customer database (325), and Storing (284) the sent data in the database, in particular in the customer database (325). [2] The computer-implemented method (200) of claim 1, further comprising storing (262) the retrieved warehouse usage-relevant data and / or processing the retrieved data in a client database (385). [3] Computer-implemented method (200) according to one of claims 1 to 2, wherein the following method steps are required to enable access to the customer database: Storing (225) the machine-readable identifier (165, 365) generated by the manufacturer in an authentication database (355) to verify the authenticity of the bearing (102), Verifying (227) the authenticity by querying the authentication database (355), and if the machine-readable identifier (165, 365) is authentic, enabling (254) access to the customer database (325). [4] A computer program product which, when loaded into a memory of a data processing system and executed by at least one processor of the data processing system, carries out the steps of the computer-implemented method (200) according to any one of claims 1 to 3. [5] System (300) for managing data (305, 335, 395) about a warehouse (102), comprising: a server system (310) and a client system (360), wherein the bearing (102) comprises a plurality of bearing components, and wherein the bearing (102) is manufactured from the plurality of bearing components in a production process, wherein the server system (310) and the client system (360) are connected via a data connection (140, 340) for data communication, wherein the server system (310) for processing data (305) via a warehouse (102) comprises: a first interface component (312) configured to acquire data (115, 305) about the plurality of bearing components and / or about the production process, a data storage component (314) configured to store the data (115, 305) in a manufacturing database (315), and at least one processor component (322) configured for: o generating a machine-readable identifier (165, 365) for the unique identification of the bearing (102), wherein the machine-readable identifier (165, 365) is assignable to the data (115, 305), and wherein the machine-readable identifier (165, 365) is arranged on the bearing (102), o Identification of storage use-relevant data (125, 335) from the data (115, 305), and o Copying the warehouse usage-relevant data (125, 335) into a customer database (325) wherein the client system (360) for processing warehouse usage-relevant data (335) about a warehouse comprises: a reading component (362) configured to read a machine-readable identifier (165, 365) on the bearing (102), an interface component (372) configured to send an access request for access to a customer database (325), the access request comprising the machine-readable identifier (165, 365), at least one processor component (374) configured for: o Retrieving some or all warehouse usage-relevant data (125, 335) from the customer database (325), and o processing the retrieved data for a warehouse-specific activity, wherein the retrieved data is usable for the warehouse-specific activity, a further interface component (392) configured to collect operational data (395) about the warehouse (102) during the warehouse-specific activity, and the at least one processor component (374) is further configured to process (274) the operating data (395), wherein the interface component (372) is further configured to send (280) the operating data (395) and / or the processed operating data to a database, in particular to the customer database (325). [6] The system (300) of claim 5, wherein the server system (310) comprises a second interface component (332) configured to send the machine-readable identifier (165, 365) to an authentication system (350) having an authentication database (355). [7] The system (300) of claim 5, wherein the client system (360) comprises a data storage component (382) configured to store the retrieved data and / or processed data in a client database (385). [8] System (300) according to claim 5, wherein the interface component (372) of the client system (360) is further configured to send the access request to a server system (310) having the customer database (325) or to send the access request to an authentication system (350) having an authentication database (355) for verifying the authenticity of the warehouse (102). [9] System (300) according to claim 5, wherein the interface component (372) of the client system (360) is further configured to send (280) the operational data (395) and / or the processed operational data to a database, in particular to the customer database (325).

Images