Cloud Manufacturing Architecture Based on Public Blockchain Technology

With Industry 4.0, IT infrastructure has started to be used more effectively in the manufacturing sector. Cyber physical systems, IoT, cloud manufacturing, big data are some of the technologies that make up the concept of Industry 4.0. These technologies have solved many problems in the manufacturing sector. One of these technologies, cloud manufacturing technology, has emerged with the idea of pay as you go. This technology has enabled manufacturing resources to be leased and shared on a global scale. However, it has problems arising from its central structure and the need for a reliable 3rd party. Reliability, security, continuity, scalability, data lock-in, single point failure, data manipulation are some of the main problems. Blockchain (BC) is a decentralized and distributed technology. The data stored on the BC network cannot be altered in any way. With these features, we believe that BC-supported cloud manufacturing systems can overcome the aforementioned problems and eliminates the need for a reliable 3rd party. Based on this belief, in this study the agreements and communication between the resource provider and the customer, which is one of the basic functions of cloud manufacturing platforms, are realized with a decentralized application using BC-based smart contracts (SCs). The designed application is called the decentralized cloud manufacturing application (DCMApp). DCMApp does not operate on a fully public BC network, it has a hybrid structure and uses the Ethereum network as a public BC network. These features make DCMApp different from other BC-based cloud manufacturing applications. DCMApp's hybrid structure has enabled more transparent, economic and safe manufacturing agreements. It is also possible to store agreements on the BC network at a low cost without installing any server infrastructure. The use of Ethereum network makes it almost impossible to manipulate agreements.

Abstract licence: CC BY-NC-ND

A person counts once a day per paper. We keep no cookie and no address: a reader is a hash that changes every day. Any month under five reads shows no number.