Patent ID: 12238228

DETAILED DESCRIPTION

The above and other elements, features, steps, and concepts of the present disclosure will be more apparent from the following detailed description in accordance with exemplary embodiments of the invention, which will be explained with reference to the accompanying drawings.

It is to be understood that the following description of embodiments is not to be taken in a limiting sense. The scope of embodiments of the invention is not intended to be limited by the embodiments described hereinafter or by the drawings, which are taken to be illustrative only. The features of the various examples may be combined with each other, unless specifically noted otherwise.

The drawings are to be regarded as being schematic representations, and elements illustrated in the drawings are not necessarily shown to scale. Rather, the various elements are represented such that their function and general purpose become apparent to a person skilled in the art. Any connection or coupling between functional blocks, devices, components, or other physical or functional units shown in the drawings or described herein may also be implemented by an indirect connection or coupling. A coupling between components may also be established over a wireless connection. Functional blocks may be implemented in hardware, firmware, software, or a combination thereof.

Some examples of the present disclosure generally provide for a plurality of circuits, data storages, connections, or electrical devices such as e.g., processors. All references to these entities, other electrical devices, and the functionality provided by each are not intended to be limited to encompassing only what is illustrated, but to describe the inventive concept in the light of general knowledge of a person skilled in the art. While particular labels may be assigned to the various circuits or other electrical devices disclosed, such labels are not intended to limit the scope of operation for the circuits and the other electrical devices. Such circuits and other electrical devices may be combined with each other and/or separated in any manner based on the particular type of electrical implementation that is desired. It is to be appreciated that any circuit or other electrical device disclosed herein may include any number of microcontrollers, a graphics processor unit (GPU), integrated circuits, memory devices (e.g., FLASH, random access memory (RAM), read only memory (ROM), electrically programmable read only memory (EPROM), electrically erasable programmable read only memory (EEPROM), or other suitable variants thereof), and software which co-act with one another to perform operation(s) disclosed herein. In addition, any one or more of the electrical devices may be configured to execute program code that is embodied in a non-transitory computer readable medium programmed to perform any number of the functions as disclosed.

In the following, various techniques with respect to ensuring operational safety of a technical system using a distributed database, in accordance with aspects and embodiments of the invention, will be explained. In particular, techniques for an EHS Blockchain with Smart Contracts will be described.

Blockchains provide a decentralized protected mechanism of storing transactions in a decentralized environment. Examples vary from digital currency to storing data in an internet of things application. The blockchain mechanism protects from manipulations in the log of transactions by using cryptography. A block carries a set of transactions. Each block points to its previous block using an encrypted key. Because of this, no one can manipulate a block in between and change the information in an existing block chain.

In a process to make a machinery safe, many different stakeholders such as machine vendors, owners of a production chain including a certain machinery and different certification bodies are involved, wherein information, such as involved documentary material, may be provided, modified, or updated at various points of time, such that the generated documentary material may be a complex to analyze and huge dataset. Therefore, manipulation free data storage including a timely log when some information or action was taken is necessary in a transparent way, wherein data integrity must be ensured, in order to determine if a machinery is safe for operation.

Therefore, a distributed ledger system, based e.g. on blockchain technology, is beneficial when the need for data integrity and different stakeholders are involved.

Blockchains provide a decentralized protected mechanism of storing transactions in a decentralized environment. Examples vary from digital currency to storing data in an internet of things application. The blockchain mechanism protects from manipulations in the log of transactions by using cryptography. A block carries a set of transactions. Each block points to its previous block using an encrypted key. Because of this, no one can manipulate a block in between and change the information in an existing block chain. In industrial environments where measures are taken to protect personnel from injuries by machinery, distributed ledger systems such as blockchain technology is beneficial when the need for data integrity and different stakeholders are involved. Each action taken to make a production line safe to work with can transparently be stored in such a blockchain and can be checked at any time for insufficiencies and provides information about organizations involved.

Since such information and the involved documentary material can be a complex to analyze and huge dataset, we provide here a system that involves certificates that automates the check whether a certain production line includes all necessary steps to provide safety for the personnel involved.

Blockchain is a replicated distributed ledger that verifies and stores transactions occurring in a peer-to-peer network, as described for example in the document Swan, Melanie. Blockchain: Blueprint for a new economy. “O'Reilly Media, Inc.”, 2015, the document Rimba, Paul, et al. “Comparing blockchain and cloud services for business process execution.” 2017 IEEE International Conference on Software Architecture (ICSA). IEEE, 2017, and the document Tschorsch, Florian, and Bjorn Scheuermann. “Bitcoin and beyond: A technical survey on decentralized digital currencies.” IEEE Communications Surveys & Tutorials 18.3 (2016): 2084-2123.

Despite some drawbacks regarding performance, as described for example in the document Yasaweerasinghelage, Rajitha, Mark Staples, and Ingo Weber. “Predicting latency of blockchain-based systems using architectural modelling and simulation.” 2017 IEEE International Conference on Software Architecture (ICSA). IEEE, 2017, a blockchain system does not rely on the business operations of any central trusted authority. Instead, its trustworthiness is derived from the blockchain software and incentive mechanisms for processing nodes in the network.

FIG.1schematically illustrates a blockchain technique, as known in the art.

An example of a distributed ledger is the Blockchain. Hereinafter, various techniques will be primarily described with respect to an implementation using the Blockchain, for sake of simplicity. However, similar techniques may be readily applied to other kinds and types of distributed databases or distributed ledgers.

A distributed database may be any database implemented in a network, which is at least partly stored redundantly on several network nodes remote from each other. Blockchain technology may comprise a plurality of blocks comprising data related to transactions and/or smart contracts. Chaining of different blocks may be implemented by cryptographic hash values stored in each block, wherein each hash value may refer to data of a previous block.

Referring toFIG.1, a blockchain comprises a plurality of blockchain data blocks1. As depicted inFIG.1, each data block1may, for example, comprise a hash value3build using a current (receiving) owner's public key2and the directly adjacent previous data block1. Each data block1further may include a signature4of the hash value3by the owner of the previous data block1using a previous owner's private key5.

According to various examples, certificating operational safety of the technical system may be implemented using smart contracts implemented in a Blockchain. The smart contracts may define executable program logic. The smart contracts may obtain the transport measurement data indicative of the one or more environmental conditions of the field devices during the shipment as an input.

FIG.1shows how the general principle of a blockchain is typically implemented. A transaction is stored in a block1. Each block1is pointing to the previous block1using its cryptographic hash3. A hash3is a digital signature of a block1, wherein it is easy to generate a hash3for a block1, but it is hard to generate a block1to a hash3. In this way, it is easy to check if a hash3provided for block1is valid by simply generating it again and comparing the hash3to the result of the calculation. A transaction stored in a block1is signed by the owner of the transaction. This signature4becomes part of the block1and accordingly also becomes part of the next hash, as describe for example in the document Nakamoto, Satoshi. “Bitcoin: A peer-to-peer electronic cash system.” (2017).

Using this mechanism, it is very hard to change data in an existing block. Changing data in a block, for example the transaction data, would change its hash and would invalidate the blockchain since the block after the manipulated block would have an invalid hash for the previous block.

Generating a block in a way so that it has the same hash as an existing block is possible, since the number of hashes is finite and the number of blocks is infinite, but this is mathematical hard, as described for example in the document Tschorsch, Florian, and Bjorn Scheuermann. “Bitcoin and beyond: A technical survey on decentralized digital currencies.” IEEE Communications Surveys & Tutorials 18.3 (2016): 2084-2123.

A blockchain has different applications and can be used as a database, or as a software connector, as described for example in the document Xu, Xiwei, et al. “The blockchain as a software connector.” 2016 13th Working IEEE/IFIP Conference on Software Architecture (WICSA). IEEE, 2016.

A distributed database may be used with smart contracts, as described for example in the document Omohundro, Steve. “Cryptocurrencies, smart contracts, and artificial intelligence.” AI matters 1.2 (2014): 19-21, that allow programmable business logic or conditional transactions, as further disclosed for example in the document Weber, Ingo, et al. “Untrusted business process monitoring and execution using blockchain.” International Conference on Business Process Management. Springer, Cham, 2016. Smart contracts, which are described for example in the document Tschorsch, Florian, and Bjorn Scheuermann. “Bitcoin and beyond: A technical survey on decentralized digital currencies.” IEEE Communications Surveys & Tutorials 18.3 (2016): 2084-2123, are semi-autonomous programs running on the blockchain. They can store and update variables and instantiate and invoke other smart contracts. Ethereum, as described for example in the document Wood, Gavin. “Ethereum: A secure decentralized generalized transaction ledger (eip-150 revision).” Online] Available: http://gavwood.com/paper.pdf (2016), is the most widely used blockchain that supports a Turing-complete scripting language (Solidity) for smart contracts. Trust in the valid execution of the code arises from trust in the integrity of the blockchain.

Summarizing, a distributed database may be used with smart contracts that allow programmable autonomous business logic or conditional transactions to be implemented in the distributed ledger400. Smart contracts, as known in the art, may be described, for example, as semi-autonomous programs implemented in a Blockchain. They may, when invoked, store and update variables and instantiate and invoke other smart contracts. Ethereum is the most widely used Blockchain that supports a Turing-complete scripting language (Solidity) for smart contracts. Trust in the valid execution of the code arises from trust in the integrity of the Blockchain.

FIG.2illustrates a schematic drawing of a device100, according to embodiments of the invention.

A device100includes at least one processor110, the memory120and an interface130. The device is connected to a distributed database400including a plurality of nodes401. The memory120contains program code executable by said at least one processor110, wherein execution of the program code causes the device100to execute the steps of a method according to the present disclosure.

A distributed database400generally may be a database that is distributed over a multitude of infrastructure nodes410of a corresponding infrastructure network, wherein transactions are selectively deposited in the distributed database400depending on a consensus between the infrastructure nodes410. The infrastructure nodes410may be geo-graphically spread across multiple sites, locations, countries, or organizations. Such a consensus may be established by an algorithm like proof of work, proof of stake, or a voting system. In particular, the distributed database may be implemented as a blockchain.

The distributed database400may be implemented using a distributed ledger. An example of a distributed ledger is the blockchain. Hereinafter, various techniques will be primarily described with respect to an implementation using the blockchain, for sake of simplicity. However, similar techniques may be readily applied to other kinds and types of distributed ledgers. A blockchain is a replicated distributed ledger that verifies and stores transactions occurring in a peer-to-peer network. A blockchain does normally not rely on the operations of any central trusted authority. Instead, its trustworthiness is derived from the blockchain algorithm and optionally incentive mechanisms for processing nodes in the network. Blockchains provide a decentralized protected mechanism of storing transactions. Examples of transactions include crypto currency, smart contracts, and data in an internet of things application. The blockchain protects its entries in the respective distributed database (blocks) and the corresponding log of transactions against manipulations by using cryptography. A block carries a set of transactions. Each block points to its previous block by using a hash of the previous block. Because of this, manipulating a block by changing the information is not possible or only possible to a limited degree.

FIG.3schematically illustrates a technical system200, according to embodiments of the invention.

The technical system200comprises a number of technical subsystems201,202,203. Each of the technical system200and the technical subsystems201,202,203may comprise one or a plurality of safety hazards, which may also be referred to as hazard elements230, when stored in a distributed ledger. A safety hazard may refer to a hazard to the health of a person near the technical system200.

FIG.4illustrates a technique for storing a smart contract410and technical data220in a distributed ledger400, according to embodiments of the invention.

Referring toFIG.4, a Blockchain400is schematically illustrated. For example, the Blockchain400may be stored in a distributed manner on multiple mining nodes401(as depicted inFIG.2) of the Blockchain infrastructure. The Blockchain400includes multiple data blocks1. The data blocks1may include transactions. For example, a data block1includes a checksum or hash value3that in some examples may be determined, at least partly, based on a directly preceding data block1of the Blockchain400—e.g., a chaining checksum. Thereby, modification or tampering with the content of the Blockchain400becomes difficult.

It is possible to implement a smart contract410on the Blockchain400. For this, the data blocks1and may store the smart contract410including a condition210and that can include further program code or functions. When the smart contract210is provided with an input, one or more of the functions of the smart contract410may be executed based on the input. One or more result variables may be stored in the smart contract410, as newly inserted technical data220or a newly inserted hazard element230(as depicted inFIG.3) of the Blockchain200associated with the smart contract410.

A smart contract410is a computer program or a computer protocol that gets as an input a set of data and provides the answer whether the given technical data220fulfills the smart contract410or not. Without the need for trust, one may simply write down the measures taken to provide a safe technical system200in a digital way and a smart contract410would check whether all requirements, i.e., conditions210, for a safe technical system, i.e. machinery, are fulfilled and answer yes or no.

Since in the process to make a machinery safe, many different organizations such as machine vendors, owners of a production chain including a certain machinery and different certification bodies are involved, manipulation free data storage including a timely log when some information or action was taken are necessary in a transparent and decentralized way are necessary, a decentralized ledger400is selected here a base technology.

A smart contract410for a safe machinery would simply consist of a container that can hold subcontracts411and the contract410is fulfilled if all subcontracts411are fulfilled. A production line, or technical system200, may then be represented as a set of subcontracts411that model all the equipment, i.e., technical subsystems210,202,203, involved in the production line. Each equipment contract can consist of other equipment contracts that model a hierarchy of equipment.

Furthermore, an equipment contract, i.e., subcontract411, may consist of a set of hazard elements230that can appear when working with that specific equipment. For example, a robot arm can harm personnel. For each hazard element230, measure contracts412can be associated and measure contracts412document which actions, i.e., measures, were taken to protect from the corresponding safety hazard.

With this simple setup, a production line can be modeled and stored within a blockchain. Each modeling step can be stored in the distributed ledger and it can be traced who had provided information at which time. After this process of modeling, people can sign contracts and verify the measure contracts. When all measure contracts that are related to a hazard element are signed to be valid, the hazard is certified, which means its risk is mitigated to an acceptable level. A quantification can also be part of the smart contract.

After all hazard elements230of an equipment contract411are certified to be mitigated to an acceptable level, the equipment is certified as a safe equipment. If all equipment contracts411are certified as safe, the root contract for a safe machinery, i.e., smart contract410for the technical system200, is valid and the machinery is certified to be safe.

The action of certification is realized by cryptographic tokens that identify digitally all certification bodies that all participants in this process agree to.

The contracts410,411,412may be stored separately in an external data source that is available to all participants in this process. When stored externally, the smart contracts410,411,412are addressed manipulation free by cryptographic hashes and are just referenced in the blockchain by respective smart contract data, respectively smart subcontract data, and smart measure contract data. With this mechanism, different types of smart contracts can be addressed, for example, one type of contracts can be used for the certification process in Germany and another one for the certification process in the United States. Further, a mix is possible where measure contracts are universal and used for the certification process for two countries.

Another option is to store the contracts410,411,412as computer source code directly in the distributed ledger, which also would protect the contracts410,411,412from manipulation.

Referring toFIG.4schematically illustrates a Blockchain400. For example, the Blockchain400may be stored in a distributed manner on multiple mining nodes401(as depicted inFIG.2) of the Blockchain infrastructure. The Blockchain400includes multiple data blocks1. The data blocks1may include transactions. For example, a data block1includes a checksum or hash value3that in some examples may be determined, at least partly, based on a directly preceding data block1of the Blockchain400—e.g., a chaining checksum. Thereby, modification or tampering with the content of the Blockchain400becomes difficult.

It is possible to implement a smart contract410on the Blockchain400. For this, the data blocks1and may store the smart contract410including a condition210and that can include further program code or functions. When the smart contract210is provided with an input, one or more of the functions of the smart contract410may be executed based on the input. One or more result variables may be stored in the smart contract410, as newly inserted technical data220or a newly inserted hazard element230(as depicted inFIG.3) of the Blockchain200associated with the smart contract410.

FIG.5illustrates a flow chart of a method for ensuring safe operation of a technical system, according to embodiments of the invention.

The method starts in step S10. In step S20, a smart contract410is generated including a condition210to be fulfilled for safe operation of a technical system200. In step S30, smart contract data, which may uniquely identify the smart contract410, of the smart contract410is stored in a distributed ledger400. In step S40, it is determined if the technical system200fulfills the condition210using the smart contract410. The method ends in step S50.

In the following examples for safe and self-supervising application of the techniques according to embodiments of the invention are explained.

Without a process involved, the aforementioned technology would not provide a sound certification process. In a practical implementation, a production line owner would open a smart contract410for a safe technical system200(i.e., a machinery, or production line) and add the digital identities of engineering personnel to the smart contract410. Engineering would then model for example the first layer of technical subsystems201,202,203(i.e., equipment) involved in the technical system200. This can be already certified equipment or new equipment that is not already certified safe.

Next, people that are responsible for the safe service of the technical system200would check in new unfulfilled hazard elements230and order the vendors engineering personnel to provide technical data220(i.e., documentation or documentary material of the technical system220) how these hazard elements230are prevented. If additional technical subsystems (i.e., other equipment, or safety equipment) is necessary, it is also checked in into the smart contract410and also can have unfulfilled hazard elements230. After the hazard elements230are marked as covered with measures240, independent certification bodies can sign these measures240(i.e., actions) to be completed or safe. If anything changes, these signatures of certification bodies automatically become invalid, since changes are applied by adding new information, for example new technical data220, new technical subsystems, or new hazard elements230, to the blockchain and are put into the blockchain after the signature of the certification body.

Additionally, all information that is required by the certification body (e.g., technical data220) can be provided by the blockchain and signed separately so that every document and every piece of information is included in the certification process. Changes cannot be made and if changes are required, new documentation evidence has to be checked into the blockchain and signed again.

In addition, if new safety hazards are discovered during the design phase or even during the phase, in which a machinery is in service, they can be checked in the blockchain and will invalidate the entire smart contract for the safe operation of the machinery. If multiple different contracts for safe machinery refer to a common set of equipment and if one of these commonly used equipment contracts loses its validity, all root contracts for safe machinery become invalid automatically.

This mechanism can, for example in very sensitive applications such as healthcare or nuclear power plants, be used so that every startup or every time sensitive equipment is used the equipment itself checks whether its contracts is still valid. If evidence was checked in the blockchain that a safe operation can no longer guaranteed, the machinery would start and would not provide any service until the smart contract is valid again.

From the above said, some general conclusions may be drawn:

The technical system may comprise multiple technical subsystems, wherein each of the technical subsystems is to be operated safely for the technical system to be operated safely. The Multiple technical subsystems may comprise at least one subsystem and are not limited to any specific number of subsystems. The device may further be configured to perform the following steps.

In a step, the device may receive a subcondition for a technical subsystem, wherein the step condition is to be fulfilled for safe operation of the technical subsystem. In various examples, the device may receive at least one sub one condition, or a plurality of step conditions, for a technical subsystem.

In a further step, the device generates a smart subcontract including the subcondition, which is to be fulfilled, in order that the smart contract is fulfilled. In other words, a smart contract may include one or more smart subcontracts, wherein the smart contract may only be fulfilled, when all smart subcontracts are fulfilled. In various examples, a plurality of smart subcontracts may be generated, each including a subcondition for a technical subsystem. A smart subcontract may be defined with a subcondition in a similar manner as the smart contract is defined with the condition.

In a further step, the device stores smart subcontract data of the smart subcontract in the distributed ledger. Like the smart contract data, the smart subcontract data may identify the smart subcontract.

In a further step, the device determines if the technical subsystem fulfills the subcondition using the smart subcontract, respectively each of the plurality of smart subcontracts. Accordingly, the device may determine if the smart contract is fulfilled, by determining if each of the smart subcontracts is fulfilled.

The device may be further configured to store technical data of the technical system in the distributed ledger. Technical data may comprise e.g., technical documentation of the technical system. Further, the device may be configured to determine, if a smart contract or subcontract is fulfilled using the respective smart contract and using the technical data stored in the distributed ledger. Accordingly, the device determines if the technical system or subsystem fulfills the condition respectively subcondition, by executing the respective smart contract, wherein it is determined if the condition or subcondition included in the smart contract is fulfilled by the technical data stored in the distributed ledger.

In various examples, determining if the condition is fulfilled by the smart contract comprises determining if each of a plurality of subconditions is fulfilled by the smart subcontracts by comparing technical data stored in the distributed ledger with the subcondition.

The smart contract, and the smart subcontract, may comprise at least one hazard element, wherein the hazard element identifies a safety hazard of the technical system, respectively technical subsystem.

The at least one hazard element may be associated with a measure to be completed for safe operation of the technical system. In other words, the measure may define an action to be completed before safe operation of the technical system is ensured. In various examples, the at least one hazard element comprises a plurality of hazard elements. Therein, one or more measures may be defined for each of the at least one hazard element.

The device may be configured to generate a smart measure contract including the measure. In some examples, the smart measure contract may be regarded as a smart subcontract of the smart contract. In various examples, each of a plurality of smart measures may be included in a respective smart measure contract, which are to be fulfilled for the smart contract to be fulfilled. The smart measure contract may be defined, such that it is fulfilled if the measure is completed.

In a similar manner as smart contract data may be stored in the distributed ledger, smart measure contract data may be stored in the distributed ledger identifying each smart measure contract.

In a further step, the device may determine if a measure is completed, using the smart measure contract.

In general, each of the smart contract, the smart subcontract and the smart measure contract, may be referred to and function as a smart contract known in the art.

The device may further be configured to store a new hazard in the smart contract, or smart subcontract, in the distributed ledger. The new hazard element may be checked in, in other words stored, and associated with the technical system or subsystem. The new hazard element may be checked in by an entity, which may be a person or machine, wherein the new hazard element may be comprised in an external database and may be automatically checked in the distributed database.

For example, a smart contract representing operational safety of a technical system may be checked in by at least one certification body, which or participants have agreed on. The smart contract may be used to automatically certify operational safety, if all conditions, subconditions, and measures have been fulfilled respectively completed, and the smart contract may additionally be certified by at least one certification body after it is fulfilled. In this regard, certifying may refer to signing the smart contract.

Likewise, a smart subcontract may be checked in by an entity made responsible by a certification body for creating the smart contract and may additionally certified or signed by at least one certification body. Accordingly, the device may be configured to sign the smart measure contract by an entity responsible for performing, i.e., completing, the measure. An entity may be a human person or a machine.

The device may be configured to sign the at least one smart contract, or smart subcontract, or smart measure contract by a certification entity, after the respective smart contract has been determined to be fulfilled. A certification entity may refer to an entity, which is responsible for the certification of safety of the technical system.

For example, a smart measure contract may be checked in and signed by an entity made responsible for completing the task, or measure, wherein the smart measure contract may be assigned by the responsible entity and may additionally be signed by the certification body.

For example, a hazard element may be checked in by any of an operator, an owner, a vendor, and a certification body, of a technical subsystem.

The device may be configured to invalidate a signature of the smart contract, smart subcontract, or smart measure contract, when new technical data or a new hated element has been stored in the distributed ledger.

The at least one condition for the technical system or a technical subsystem may be a requirement according to an Environmental Health and Safety (EHS) industry standard applicable to the technical system, wherein and the smart contract may be an operating permission of the technical system.

A smart contract, or smart subcontract may comprise a risk quantification threshold, wherein fulfillment of the smart contract is determined based on a comparison of a risk quantification value associated with a hazard element, which is included in the smart contract, with the risk quantification threshold. A risk quantification value may be a risk priority value, as known in the art, for the safety hazard. If the risk quantification value of a hazard element is below one the risk quantification threshold, for example because a measure for the hazard element may be completed, the smart contract may be fulfilled.

The technical system may be a production line, or machinery, and the technical subsystems may be machines, or equipment, of the production line.

A smart contract itself may not be stored, i.e., directly stored, in the distributed ledger, i.e. may be stored outside the distributed ledger, and the smart contract data may comprise an identifier referring to the smart contract, which may be a hashing function value of the smart contract or a pointer to the smart contract stored outside the distributed ledger. In various other embodiments, the smart contract data may comprise the smart contract, i.e., the smart contract may be stored in the distributed ledger.

In the same way, the smart subcontract or smart measure contract may not be directly stored in the in the distributed ledger, wherein the above description applies likewise for the smart subcontract data, and smart measure contract data. In other words, the smart subcontract and smart measure contract may be stored outside the distributed ledger, and the smart subcontract data and the smart measure contract data may comprise an identifier referring to the the smart subcontract respectively smart measure contract, which may be a hashing function value or a pointer. The smart subcontract data may comprise the smart subcontract, i.e., the smart subcontract may be stored in the distributed ledger. The smart measure contract data may comprise the smart measure contract, i.e., the smart measure contract may be stored in the distributed ledger.

Likewise, technical information, in other words specifications, of the technical system and/or the technical subsystems, i.e. defining the technical system and/or the technical subsystems, which may necessary to decide if a condition or subcondition or measure is fulfilled, may not be stored in the distributed ledger, i.e. may be stored outside the distributed ledger, and the technical data stored in the distributed ledger may comprise an identifier referring to the technical information of the technical system and/or the technical subsystems, which may be a hashing function value of the technical information or a pointer to the technical information. The technical data may comprise the technical information or specifications of the technical system and/or the technical subsystems, i.e., the technical information or specifications of the technical system and/or the technical subsystems may be stored in the distributed ledger.

In a similar way as the smart contract for the technical system may contain hazard elements, a smart subcontract may comprise at least one hazard element of the corresponding technical subsystem, which identifies a safety hazard of the corresponding technical subsystem that may appear when operating the corresponding technical subsystem. The at least one hazard element may be associated with a corresponding measure to be completed for safe operation of the technical subsystem, and therefore the technical system. Accordingly, the device may be further configured to generate a smart measure contract for the at least one hazard element of the smart subcontract to be fulfilled for safe operation of the technical subsystem, and therefore the technical system, to store smart measure contract data in the distributed ledger, and to determine if the measure is completed using the smart measure contract.

Each storing operation in the distributed ledger, in particular each of storing of smart contract/subcontract data, technical data, or smart measure contract data, comprises storing the current time, specifically a timestamp, in the distributed ledger, and/or storing an identity of the entity, i.e. a person or machine responsible for the data or the contracts and initiating the storing operation.

Summarizing, in the field of operating technical systems according to industry safety standards, techniques for protecting a person from safety hazards of a technical system are provided, wherein the improved method according to the present disclosure provides a simple setup, how a production line can be modeled and stored within a blockchain. Each modeling step can be stored in the distributed ledger and it can be traced who had provided information at which time. After this process of modeling, people can sign contracts and verify the measure contracts. When all measure contracts that are related to a hazard element are signed to be valid, the hazard is certified, which means its risk is mitigated to an acceptable level.

Since in the process to make a machinery safe, many different organizations such as machine vendors, owners of a production chain including a certain machinery and different certification bodies are involved, manipulation free data storage including a timely log when some information or action was taken are necessary in a transparent and decentralized way are necessary, a decentralized ledger is selected here a base technology. This mechanism can, for example in very sensitive applications such as healthcare or nuclear power plants, be used so that every startup or every time sensitive equipment is used the equipment itself checks whether its contracts is still valid. And if evidence was checked in the blockchain that a safe operation can no longer guaranteed, the machinery would start and would not provide any service until the contract is valid again.

Although the present invention has been disclosed in the form of preferred embodiments and variations thereon, it will be understood that numerous additional modifications and variations could be made thereto without departing from the scope of the invention.

For the sake of clarity, it is to be understood that the use of “a” or “an” throughout this application does not exclude a plurality, and “comprising” does not exclude other steps or elements.