Patent ID: 12204305

DETAILED DESCRIPTION OF PREFERRED EMBODIMENTS

FIG.1shows a system1corresponding to the system according to the invention. For clarity of illustration reasons, one automation plant2, one cloud system3, one machine manufacturer4or manufacturer of industrial inspection systems and one blockchain network5are shown inFIG.1.

For simplicity of illustration, the automation plant is shown as a production plant2comprising a single production machine20and a single edge device21. The edge device21has a cloud interface to the cloud system3. The edge device21is an IoT (Internet of Things) device.

The production plant2(shop floor) can of course comprise a plurality of edge devices and a plurality of machines. Not infrequently, an automation plant comprises a machine network consisting of dozens or even hundreds of machines and an industrial inspection system comprising multiple (possibly also dozens or hundreds of) edge devices. The machines can be embodied for example as robots, machine tools, manufacturing machines, AGVs (autonomous guided vehicles), etc. The machines can be embodied as IoT devices or comprise such devices.

The edge device21is connected via a machine interface to the production machine21and/or to sensors attached to the production machine21in order to acquire operating data relating to the production machine21. Furthermore, the edge device21is configured to generate usage data on the basis of the operating data. The operating data can comprise for example the number of turned parts per hour, materials, etc. The usage data can comprise for example the number of operating hours, energy consumption, etc.

The differences between operating and usage data are now illustrated inFIG.2based on the example of a milling machine200.

FIG.2shows operating data generated by the milling machine200in the form of a time series201. In reality, the time series201maps by way of example how heavily a spindle of the milling machine200is loaded as a function of time T. It can be seen when and at what frequency (“RPM”—revolutions per minute) the spindle is put into operation—“On”, and when its operation is terminated—“Off”. An edge device202assigned to the milling machine200and connected to it is configured to acquire the operating data and to generate usage data from the operating data. The usage data can be present for example in the form of a series of time windows W1, . . . W37of a predetermined length (in this case 15 minutes). Each of the windows W1to W37can contain information about how long the spindle was in operation (“On”) within said time window and how long the spindle was subject to a predefined heavy load (“HL”). It can be seen from the window W36for example that the spindle was in operation the whole time (15 min) and of that was subject to the heavy load for 2 minutes. Of course, the length of the windows is not limited to 15 minutes. This length can also vary from window to window. A length of the window of 24 hours is entirely plausible. The load that is considered heavy can likewise be predefined. For example, a load of 3700 RPM can be regarded as heavy.

Moreover, the edge device21can be set up to ascertain its location and/or the location of the machine20. For this purpose, the edge device21can have for example a W3C API, in which case the location(s) can be determined by means of GPS, IP, GSM, WLAN, etc.

The edge device21can furthermore be set up to acquire KPIs (key performance indicators) and further production-related or -relevant data.

To sum up, the edge device21is set up to acquire production plant-related data, wherein the production plant-related data can comprise the usage data and in addition also further data, such as for example the location and/or the KPI and/or machine residual value data, etc. The edge device21possesses the capability to digitally sign data and optionally to encrypt said data.

It can also be seen fromFIG.1that the edge device21transmits the production plant-related data via its cloud interface to the cloud system3. On account of the integrity of the production plant-related data, the edge device21is furthermore configured to digitally sign the production plant-related data before it transmits the latter to the cloud system3. In this case the edge device21preferably communicates with a software module30which resides in the cloud system3.

The software module30is configured to determine at least a part of the digitally signed usage data and to form a checksum from the part of the digitally signed usage data. Preferably, the software module30forms the checksum based on a cryptographic method in order to generate what is termed a cryptographic checksum or a cryptographic hash or a hash value.

Furthermore, the software module30can be embodied to determine at least one further part of the further digitally signed production plant-related data and to encrypt said further part.

The part of the digitally signed usage data which the software module30determines and from which the software module30forms a checksum, preferably a hash value, can for example comprise data relevant to accounting and/or financially relevant data (for example data relevant to the leasing agreement) and/or legally relevant data (for example data relevant to a radio type approval) or consist of said data.

In addition, the software module30is set up and/or configured to communicate with at least one node51of the blockchain network5in order to transfer the checksum, preferably the hash value of the part of the digitally signed usage data, to the at least one node61. The node51then stores the corresponding transaction, which contains for example a timestamp and the checksum, in files and blocks and distributes the files and blocks further to the other nodes52,53,54.

Furthermore, the software module30can be set up and/or configured to transfer the encrypted further part of the further digitally signed production plant-related data, for example KPIs and/or the GPS coordinates of the machine20, to the at least one node51.

To sum up, the software module30is set up to transfer a checksum of a specific part of the digitally signed usage data, for example the part of the usage data relevant to accounting, and optionally further encrypted data, to the at least one node51. The software module30has the capability to encrypt the received data.

In addition, the software module30is configured and/or set up to store the digitally signed usage data in a database40of the machine and/or edge device manufacturer4. Other usage data is also stored in the database. It can be advantageous for example to store the GPS data of the machines, the “Heavy Load” factor, which is subsequently well suited for correctly estimating above-average depreciations or defects, etc.

The manufacturer can graphically present usage data on a dashboard41and/or generate invoices42for the use of the machine20in the automation plant2. It is possible that the machine manufacturer4has for example leased the machine20to the owner of the automation plant2.

The blockchain network5additionally comprises at least one further node. For simplicity of illustration reasons, three further blockchain nodes52,53,54are shown inFIG.1. The blockchain network5can, of course, also comprise many more further nodes.

For example, the blockchain network is a private blockchain network5or a blockchain network referred to as a consortium blockchain network, in which participation in the blockchain network5is restricted to specific participants only. The participants may comprise for example a financial and/or licensing authority. In the industrial environment, for example, private blockchains are used in which the consensus method takes place within a consortium whose members are known to one another, for example, or to an administration authority or fulfill a particular trust level.

However, the blockchain network5can also be embodied as a public blockchain network, such as Ethereum for example.

It should be emphasized at this juncture that both the automation plant2and the cloud system3can belong to the machine manufacturer4(the owner of the automation plant2, the cloud system3and the machine manufacturer4can be the same juristic or natural person). However, it is also conceivable that the automation plant2, the cloud system3and the machine manufacturer4belong to different juristic or natural persons.

Furthermore, the software module30can be arranged in the edge device21and communicate with the at least one node51of the blockchain network5via the cloud system3or directly. It is also possible that the levels of the machine and/or edge device manufacturer4are arranged in their entirety (dashboard41, invoices42, database40) or partially (database40) in the cloud system3.

The database40is located outside of the blockchain network5. By this means it can be prevented for example that the blockchain network participants can view the usage data without an access authorization.

Nevertheless, the participants of the blockchain network5, which for example comprise one or more of the further nodes, can access the checksum of the usage data extract and, if present, the encrypted further data, for example the location data and/or machine residual value data.

An audit process is illustrated inFIG.3. In the audit process, a check is conducted to verify the correctness of the invoices42which the machine manufacturer4sends to the owner of the production plant2who uses the machine20on the shop floor of the plant20. The check can be carried out for example by a third party6on behalf of the owner of the production plant2, wherein the third party6can but does not have to have one or more nodes—in the present case the nodes53,54—of the blockchain network5. The third party6can have for example only a physical access and reading access to any of the nodes51,52,53,54.

First, the third party6applies to the machine manufacturer40for example by means of a message60for that usage data which is to be checked and for which the invoices are available. In addition, the auditor6can, if necessary, request a characterization of the method with which the checksum, in particular the hash value, was formed which has been transferred to the at least one node51of the blockchain network5. After the request of the auditor6has been fulfilled, the latter can form a checksum, preferably a hash value, from the provided usage data61and compare it with the checksum or hash value stored in the blockchain network5.

The aforesaid also applies analogously to the checking of the encrypted data that may be present in the node51. In this case the auditor6also receives a key from the machine manufacturer for decrypting the encrypted data transferred to the node51.

FIG.4shows a system100, which can be embodied for example as an extension of the system1ofFIGS.1and3.FIG.4shows the machine20, which has for example three sensors Z1, Z2, Z3. The data from the sensors Z1, Z2, Z3is acquired by the edge device21, the edge device21further being able to transform, digitally sign and optionally encrypt the acquired data. As already mentioned, the edge device21can additionally ascertain the geolocation of the operation site for example by means of a W3C Geolocation API210. The W3C Geolocation API can determine a correspondingly accurate geographical location using GPS, GSM, WLAN, or an IP address.

The sensors Z1, Z2, Z3are preferably certified so that the measured value is already trustworthy and possess in particular a unique identification ID ex works, which determine operating data on site on the machine20or process (not shown). This operating data preferably satisfies a standardized data or machine model. Later, at the time of an assessment or verification of the operating data, this enables for example the general parameter name “rotational speed” or “energy consumption” to be uniquely assigned its meaning in a machine without knowing the individual machine topology.

In addition to the blockchain network5ofFIGS.1and3, the blockchain network500ofFIG.4comprises at least one smart contract5101,5102. Conditions under which a use of the machine20is possible can be mapped in the smart contract. For example, usage conditions, such as for example pay-per-use conditions, can be regulated in this case. Accordingly, the at least one smart contract5101,5102(executable on the blockchain network500) can govern the relationship between the parties of the system100, for example between the machine manufacturer4and the owner of the production plant2.

The smart contracts5101,5102can be generated and stored in the node510to which the software module30transfers the checksum or the hash value and the optionally encrypted further data. However, it is also conceivable that another random node executes the smart contract(s)5101,5102since any node is equally entitled to access all the blocks. In this case the software module30can communicate with the smart contract(s)5101,5102. In the process, the data transferred by the software module30can be supplemented by means of the at least one smart contract5101,5102by an officially certified and current time/date5103, for example from the time server of the PTB (Physikalisch-Technischen Bundesanstalt—the national metrology institute in Germany).

For example, the edge device21can acquire the ID or the software version, operating data and location of the sensors Z1, Z2, Z3and evaluate these against the criteria “ready for service” or “out of service”. The result can be digitally signed, encrypted, for example by means of the edge device21, and entered into the blockchain network500by means of the software module30.

The edge device21can therefore communicate with the at least one smart contract5101,5102in the blockchain5by way of the second module30(the service generating hash values).

A lessor7can now evaluate the data encrypted for him/her in his/her node52by means of the at least one smart contract5101,5102and be assured at which time, at which location and in which condition the machine20was. Advantageously, the lessor can digitally link the evaluation to his/her financial processes in order to make use of a completely digital execution.

Furthermore, this evaluation can be credibly verified to a regulator8, even years later, with reference to data which is also accessible to the regulator8in the latter's node53.

If, for example, the edge device21digitally signs and encrypts only the ID/software version and the location and transmits these to the software module30, which enters this data into the blockchain network500, the at least one smart contract5101,5102can automatically and preferably continuously check all the entered datasets by means of a comparison with the oracle of the machine vendor4(“this SW version is in compliance with the rules at this time in this country”) and prevent the use of a non-compliant machine by means of a corresponding feedback to the edge device21.

Advantageously, this can be credibly verified to an authority8, even years later, with reference to data which is also accessible to the authority8in its node53.

In addition or alternatively, the edge device21can digitally sign its ID/software version and a location at which it is installed and enter it preferably in encrypted into the blockchain5by way of the second module30.

The at least one smart contract5101,5102can continuously and automatically check all the entered datasets by means of a comparison with the oracle of the device vendor4(“this software version is in compliance with the rules at this time in this country”) and prevent the use of a non-compliant device by passing information to the edge device21. This implementation can be credibly verified to an authority, even years later, with reference to data which is also accessible to the authority in its nodes53,53,54“authority”6,7or8of the blockchain5.

In addition, the machine20itself can also form a node of the blockchain network500. In this case the at least one smart contract5101,5102can be executed as a function of a result of the check on the data. In response to a result of the execution of the at least one smart contract5101,5102, the machine20, which can communicate with the smart contract(s), can perform a corresponding action, for example shut itself down or block the communication with other machines in an automation plant network (arrow5104inFIG.4). The result of the execution of the smart contract(s)5101,5102is dependent on whether the rules specified there are observed or not. This can but does not have to be accomplished with the aid of the edge device21.

It is advantageous in this case that the mass data of the industrial process (the operating data) can remain on site at the plant2. Only that data is transferred into the distributed ledger network5, for example into the blockchain, which is directly relevant for rapid evaluation by a regulator or authority6,7,8(for example “device is compliant”) or which helps in the event of a dispute to prove the correctness of historical usage data and preferably the operating data (for example weekly hash on the usage data and preferably the operating data stored on site).

Although the invention has been illustrated and described in greater detail on the basis of exemplary embodiments, the invention is not limited by the disclosed examples. Variations hereon can be derived by the person skilled in the art without leaving the scope of protection of the invention as defined by the following claims. In particular, the features described in connection with the method can also find application in the system or complete the latter, and vice versa.