Towards Blockchain-Integrated Enterprise Resource Planning: A Pre-Implementation Guide
Abstract
:1. Introduction
- RQ1: What impact does the integration of blockchain with ERP systems have on supply chain performance?
- RQ2: What approach should be employed to assist decision-makers in determining whether to integrate blockchain into their ERP systems?
- RQ3: What are the key decisions that need to be made prior to blockchain implementation?
2. Background
2.1. Blockchain Technology
- Public (permissionless);
- Private (permissioned);
- Federated (permissioned).
2.2. Blockchain for Consortium
2.3. Blockchain as a Service (BaaS) for Consortia
2.4. Synchronization of ERP System and Blockchain Functioning
- Transaction Initiation: A user can send a request to the database to initiate the transaction; however, the transaction can be initiated in different ways, such as using an oracle. This request is first processed by the database with pre-established management rules, including access control mechanisms, artificial intelligence algorithms, and neural networks to filter out erroneous information and users without access control. Selective data, important for the supply chain, are sent to the blockchain through the application interface. However, some companies choose to only store metadata on the blockchain to avoid storage problems [21].
- Preparation Stage: Once sent through the application interface to the blockchain, transactions are placed in the pool as unprocessed transactions. A second verification at the blockchain level is initiated to control access and the veracity of information transmitted to the blockchain. These transactions are grouped into packets of ‘N’ transactions and updated as blocks.
- Consensus and Propagation Stage: The block containing ‘N’ transactions is transmitted to the validator nodes. After the block is validated by a validator node, the validation is complete. The block is added to the blockchain and propagated to all nodes in the network.
- Database Update Stage: When the transaction is validated and placed in a block, the corresponding data in the ERP system database are updated in accordance with the validated transaction. The relevant parties then receive a notification of the transaction confirmation.
- Level 1: Transaction Journals or Data (Data Restoration). The first level provides the possibility of restoring data in the case of an error during a transaction. There might be a misconception about the immutable nature of the blockchain, amplifying the perception that errors are irreversible. Initially, it is advised to apply artificial intelligence algorithms and neural networks to filter the data and detect errors before they are introduced into the system [19]. However, in the event of an error, there is a way to restore the system’s integrity. Data reversibility in a blockchain can be achieved by restoring the system to a state prior to the error using the immutable information stored in the blockchain. The immutability of the blockchain ensures the permanence of the recorded data, preventing any alteration once they have been added to the chain. In the case of an error, it is not possible to directly delete the transaction from the blockchain. However, it is possible to restore the state preceding the erroneous transaction. This restoration can be performed by executing an inverse transaction, thereby canceling the effects of the incorrect transaction. However, it should be noted that companies have the flexibility to decide whether they store the entirety of transactions on the blockchain, including transaction journals, or only the corresponding metadata.
- Level 2: Access Management and Business Rules The second tier of the blockchain focuses on business rules and access management aspects. At this stage, we find information related to access rights granted to users within the ERP system and the activities of authorized users who have access to the system.
- Level 3: ERP Data Validation At this level, the integrity of transactions is ensured, and the same records are placed in the ERP and blockchain databases. This level establishes rules by which the ERP and blockchain can communicate with each other at any time for mutual synchronization.
2.5. Synthesis
3. Materials and Methods
4. Results and Discussions
4.1. Blockchain Technology Impact on the Supply Chain
- Reducing counterfeiting: Every node within the blockchain holds a copy of the entire transaction history, allowing for a complete audit trail of every transaction made within the system [4]. Furthermore, the immutability and availability of all transactions in the blockchain enable tracing the product’s origin, ownership, and storage details, effectively eliminating counterfeit products and ensuring that products meet the desired quality standards.
- Promoting digitalization: Product details and their life cycle are stored in the system in a digital format, eliminating any ambiguity about the product. This also encourages paper reduction and lowers administrative costs [8]. Moreover, advanced data analysis features are offered by blockchain solutions available on the market. For instance, SAP Leonardo provides advanced analytics tools to help businesses leverage data gathered from various sources and gain valuable insights for improved decision-making [26]. Leonardo’s analytics tools include solutions for data visualization, predictive analysis, and financial planning. This global leader in ERP systems integrates artificial intelligence and machine learning services to help businesses automate processes, enhance decision-making, and personalize customer experiences. Companies can harness these technologies to create virtual assistants, recommendation systems, and predictive analysis tools.
- Enhancing procurement: Implementing blockchain across all partners can be challenging, especially for multi-tiered and diverse suppliers, but it will yield long-term benefits in terms of transparency, sustained growth, and responsible sourcing. As an increasing number of enterprise systems and supply-generating systems, such as ERPs, MES, etc., become connected to the blockchain, data availability will become more transparent and function in real-time, enabling procurement that aligns with the lean philosophy [6].
4.2. Framework
- Step 1: Place the indicators in the rows and columns of the n × n AHP matrix.
- Step 2: Perform a pairwise comparison of the indicators in the matrix according to a set of criteria.
- Step 3: Sum the columns.
- Step 4: Normalize the sum of the rows.
- Step 5: Calculate the average of the rows; this average represents the weight of each indicator.
4.2.1. Need Quantification
- Do information silos exist between different partners in the supply chain?
- Do intermediaries exist in this particular use case? If they do, how advantageous would it be to remove these intermediaries?
- Is it necessary to include participants with similar common issues?
- Does this use case entail sharing information with other partners?
- Are multiple parties required to update the reports?
- Do you require information from other sources or stakeholders?
- Does this use case require the company to be accountable for the accuracy of transactions?
- Does this use case require transactions to be transparent?
- Does this use case require transaction confidentiality?
- How predictable is the input of data and the behavior of potential actors in the network?
4.2.2. The Favorable and Unfavorable Indicators
- Sustainable governance rules: Blockchain is a model and protocol for ensuring information security, tracking, and decentralization. If these rules remain consistent and stable over time, they can ensure reliable and efficient operations of the blockchain and ERP systems.
- Regulatory Authority: The presence of regulatory authorities can help companies implement blockchain because it will ensure compliance with regulations and laws and allow consortiums to cooperate more in a transparent and safe environment. In fact, blockchain allows transactions to be conducted transparently and securely, but in no way can it ensure compliance with regulatory requirements.
- Transaction throughput: Transaction throughput can prove whether the implementation of blockchain technology is appropriate because a too-low throughput can indicate that it is not necessary to implement blockchain technology and that ERP systems can handle the data; on the other hand, a very high throughput can prove costly, so it is more reasonable to consider other technologies.
- Similar use cases: To confirm the need to use blockchain, it is interesting to look at similar use cases in which blockchain has been implemented to obtain feedback. This is about benchmarking the successes and failures of previous blockchain implementation projects to learn from them. The successful implementation projects of similar cases are a favorable indicator.
- Top management commitments: Top management commitments are key elements of the integration of blockchain into ERP systems. This commitment means that the senior management is ready to support the project and provide the necessary resources to execute the project and support the integration project internally and externally while confirming the strategic vision of the project for the company and the consortium.
- Willingness to decentralize data storage: If organizations want to decentralize data storage, this may be a useful indicator for the integration of blockchain and ERP systems. It shows that organizations are open to the advantages of blockchain technology and that this integration can help improve the safety, tracking, integration, and management of business processes.
- Risk aversion: Blockchain technology is a new and complex technology that offers many risks but also many advantages. Therefore, risk aversion could be an obstacle to the implementation of blockchain.
- Knowledge and expertise of blockchain technology: Knowledge of blockchain technology is key to the implementation of this technology; the more foreknowledge of blockchain technology stakeholders in the implementation project, the more they are engaged in it and they will have less resistance to change.
- Asset detection: Being able to easily highlight assets, transactions, and events can help in the implementation of blockchains. In this case, supply chain partners can benefit from the advantages that blockchain brings in terms of tracking, automation, error reduction, fraud, delay, and cost reduction. Smart contracts can be easily implemented by identifying assets, transactions, and events, enabling processes to be simplified and automated.
- Asset digitization: The ease with which assets are digitized is an important factor in deciding whether to implement blockchains in the supply chain because blockchains work primarily with digital assets and digital information. The question here is whether there is an opportunity to implement blockchain in the supply chain. In fact, when assets are easily digitized, the blockchain is beneficial to supply chain management. Asset digitization can play a beneficial role in implementing blockchains.
- The willingness of stakeholders to collaborate: Since stakeholders in the supply chain may have different requirements, it is important to determine if these parties are willing to work together to address the use cases. Blockchain will only be beneficial to supply chains if all stakeholders decide to work together and cooperate transparently.
- The applicability of a consistent set of rules to achieve the process outcome: Blockchain is a technology that relies on a set of rules and protocols to ensure security, traceability, and decentralization. If the application of a consistent set of rules through blockchain can improve the outcome of the process within the consortium, this may be a sign that the integration of blockchain with ERP systems could be beneficial.
4.2.3. Critical Decision
- CD1: Blockchain Type
- CD2: Governance Type
- CD3: Deployment Choice
- CD4: Blockchain Platform Choice
- CD5: BaaS Choice
- CD6: Process Automation through Smart Contracts
- CD7: Technology Cost Allocation Among Partners
- CD8: Blockchain Project Duration
- CD9: Consensus Choice
- CD10: Tokenization
- CD11: Token Type
- CD12: Double Storage
- CD13: Interoperability with Other Blockchains
- CD14: Blockchain Interoperability Technology
5. Conclusions
5.1. Theoretical Implications
5.2. Practical Implications
5.3. Limitations and Future Research
Author Contributions
Funding
Data Availability Statement
Conflicts of Interest
Appendix A
References
- Imane, L.; Nourredine, M.; Driss, S.; Hanane, L. Fit-Gap Analysis: Pre-Fit-Gap Analysis Recommendations and Decision Support Model. Int. J. Adv. Comput. Sci. Appl. 2022, 13, 391–406. [Google Scholar] [CrossRef]
- Cotteleer, M.J.; Bendoly, E. Order Lead-Time Improvement following Enterprise Information Technology Implementation: An Empirical Study. MIS Q. 2006, 30, 643. [Google Scholar] [CrossRef]
- Gattiker, T.F.; Goodhue, D.L. Understanding the local-level costs and benefits of ERP through organizational information processing theory. Inf. Manag. 2004, 41, 431–443. [Google Scholar] [CrossRef]
- Hyperledger—Open Source Blockchain Technologies. Available online: https://www.hyperledger.org/ (accessed on 21 June 2023).
- Aslam, T.; Maqbool, A.; Akhtar, M.; Mirza, A.; Khan, M.A.; Khan, W.Z.; Alam, S. Blockchain Based Enhanced ERP Transaction Integrity Architecture and PoET Consensus. Comput. Mater. Contin. 2022, 70, 1089–1109. [Google Scholar] [CrossRef]
- Banerjee, A. Chapter Three—Blockchain Technology: Supply Chain Insights from ERP. In Advances in Computers; Raj, P., Deka, G.C., Eds.; Blockchain Technology: Platforms, Tools and Use Cases; Elsevier: Amsterdam, The Netherlands, 2018; Volume 111, pp. 69–98. [Google Scholar] [CrossRef]
- Lahlou, I.; Motaki, N. Integrating Blockchain with ERP systems for better supply chain performance. In Proceedings of the 2022 14th International Colloquium of Logistics and Supply Chain Management (LOGISTIQUA), El Jadida, Morocco, 25–27 May 2022; pp. 1–6. [Google Scholar] [CrossRef]
- Azzi, R.; Chamoun, R.K.; Sokhn, M. The power of a blockchain-based supply chain. Comput. Ind. Eng. 2019, 135, 582–592. [Google Scholar] [CrossRef]
- Christidis, K.; Devetsikiotis, M. Blockchains and Smart Contracts for the Internet of Things. IEEE Access 2016, 4, 2292–2303. [Google Scholar] [CrossRef]
- Faccia, A.; Petratos, P. Blockchain, Enterprise Resource Planning (ERP) and Accounting Information Systems (AIS): Research on e-Procurement and System Integration. Appl. Sci. 2021, 11, 6792. [Google Scholar] [CrossRef]
- Hughes, L.; Dwivedi, Y.K.; Misra, S.K.; Rana, N.P.; Raghavan, V.; Akella, V. Blockchain research, practice and policy: Applications, benefits, limitations, emerging research themes and research agenda. Int. J. Inf. Manag. 2019, 49, 114–129. [Google Scholar] [CrossRef]
- Pérez, T.E.; Rossit, D.A.; Tohmé, F.; Vásquez, Ó.C. Mass customized/personalized manufacturing in Industry 4.0 and blockchain: Research challenges, main problems, and the design of an information architecture. Inf. Fusion 2022, 79, 44–57. [Google Scholar] [CrossRef]
- Iansiti, M.; Lakhani, K. The Truth About Blockchain. Harv. Bus. Rev. 2017, 95, 118–127. [Google Scholar]
- Casino, F.; Dasaklis, T.K.; Patsakis, C. A systematic literature review of blockchain-based applications: Current status, classification and open issues. Telemat. Inform. 2019, 36, 55–81. [Google Scholar] [CrossRef]
- Deloitte. Deloitte’s 2019 Global Blockchain Survey: Blockchain Gets Down to Business. 2019. Available online: https://www2.deloitte.com/us/en/insights/topics/understanding-blockchain-potential/global-blockchain-survey.html (accessed on 10 January 2020).
- Aarikka-Stenroos, L.; Ritala, P. Network management in the era of ecosystems: Systematic review and management framework. Ind. Mark. Manag. 2017, 67, 23–36. [Google Scholar] [CrossRef]
- Helfat, C.E.; Raubitschek, R.S. Dynamic and integrative capabilities for profiting from innovation in digital platform-based ecosystems. Res. Policy 2018, 47, 1391–1399. [Google Scholar] [CrossRef]
- IBM Newsroom—Featured Stories. IBM Newsroom. Available online: https://newsroom.ibm.com/index.php?s=34222 (accessed on 20 November 2023).
- Kafeel, H.; Kumar, V.; Duong, L. Blockchain in supply chain management: A synthesis of barriers and enablers for managers. Int. J. Math. Eng. Manag. Sci. 2023, 8, 15–42. [Google Scholar] [CrossRef]
- Designing a Blockchain Enabled Supply Chain—ScienceDirect. Available online: https://www.sciencedirect.com/science/article/pii/S2405896319310183 (accessed on 16 November 2023).
- Rasi, R.Z.; Bin Rakiman, U.S.; Radzi, R.Z.R.M.; Masrom, N.R.; Sundram, V.P.K. A Literature Review on Blockchain Technology: Risk in Supply Chain Management. IEEE Eng. Manag. Rev. 2022, 50, 186–200. [Google Scholar] [CrossRef]
- Thantharate, P.; Thantharate, A. ZeroTrustBlock: Enhancing Security, Privacy, and Interoperability of Sensitive Data through ZeroTrust Permissioned Blockchain. Big Data Cogn. Comput. 2023, 7, 165. [Google Scholar] [CrossRef]
- Gonzalez-Amarillo, C.; Cardenas-Garcia, C.; Mendoza-Moreno, M.; Ramirez-Gonzalez, G.; Corrales, J.C. Blockchain-IoT Sensor (BIoTS): A Solution to IoT-Ecosystems Security Issues. Sensors 2021, 21, 4388. [Google Scholar] [CrossRef]
- Varriale, V.; Cammarano, A.; Michelino, F.; Caputo, M. Integrating blockchain, RFID and IoT within a cheese supply chain: A cost analysis. J. Ind. Inf. Integr. 2023, 34, 100486. [Google Scholar] [CrossRef]
- Charles, V.; Emrouznejad, A.; Gherman, T. A critical analysis of the integration of blockchain and artificial intelligence for supply chain. Ann. Oper. Res. 2023, 327, 7–47. [Google Scholar] [CrossRef]
- Les 7 Clefs Pour Comprendre SAP Leonardo. Available online: https://news.sap.com/france/2017/11/les-7-clefs-pour-comprendre-sap-leonardo/ (accessed on 21 June 2023).
- Kuo, T.-T.; Zavaleta Rojas, H.; Ohno-Machado, L. Comparison of blockchain platforms: A systematic review and healthcare examples. J. Am. Med. Inform. Assoc. 2019, 26, 462–478. [Google Scholar] [CrossRef]
- Llambias, R.; González, G.L.; Ruggia, R. Blockchain Interoperability: A Feature-based Classification Framework and Challenges Ahead. CLEI Electron.J. 2022, 25, 1–29. [Google Scholar] [CrossRef]
- Li, Y.; Qiao, L.; Lv, Z. An Optimized Byzantine Fault Tolerance Algorithm for Consortium Blockchain. Peer-To-Peer Netw. Appl. 2021, 14, 2826–2839. [Google Scholar] [CrossRef]
- Zhang, S.; Lee, J.-H. Analysis of the main consensus protocols of blockchain. ICT Express 2020, 6, 93–97. [Google Scholar] [CrossRef]
- Parthasarathy, S.; Daneva, M. Customer requirements based ERP customization using AHP technique. Bus. Process. Manag. J. 2014, 20, 730–751. [Google Scholar] [CrossRef]
- Acharya, V.; Yerrapati, A.E.; Prakash, N. Oracle Blockchain Quick Start Guide: A Practical Approach to Implementing Blockchain in Your Enterprise; Packt Publishing: Birmingham, UK, 2019. [Google Scholar]
- Li, X.; Zheng, Z.; Dai, H.N. When services computing meets blockchain: Challenges and opportunities. J. Parallel Distrib. Comput. 2021, 150, 1–14. [Google Scholar] [CrossRef]
- Lewis, A. A Gentle Introduction to Digital Tokens. 2015. Available online: https://bitsonblocks.net/2015/09/28/gentle-introduction-digital-tokens/ (accessed on 20 November 2023).
- Oliveira, L.; Bauer, I.; Zavolokina, L.; Schwabe, G. To Token or not to Token: Tools for Understanding Blockchain Tokens. In Proceedings of the International Conference of Information Systems (ICIS 2018), San Francisco, CA, USA, 12–16 December 2018. [Google Scholar]
- Belchior, R.; Vasconcelos, A.; Guerreiro, S.; Correia, M. Correia A Survey on Blockchain Interoperability: Past, Present, and Future Trends. ACM Comput. Surv. 2021, 54, 1–41. [Google Scholar] [CrossRef]
Decision Element | Questions |
---|---|
CD1 | What type of blockchain should be adopted? |
CD2 | What type of governance should be adopted? |
CD3 | What type of deployment should be done? |
CD4 | Which blockchain platform should be adopted? |
CD5 | In the context of a cloud deployment, which Blockchain as a Service (BaaS) should be chosen? |
CD6 | What processes will be automated by smart contracts? |
CD7 | How will the costs related to the implementation project be divided among the partners? |
CD8 | What is the estimated duration of the implementation project? |
CD9 | What consensus choice should be adopted? |
CD10 | Will tokens be used in the network? |
CD11 | If tokens are to be used, what types of tokens will be used? |
CD12 | Will dual storage be used? |
CD13 | Will the blockchain communicate with other blockchains? |
CD14 | How will the costs related to the implementation project be divided among the partners? |
Disclaimer/Publisher’s Note: The statements, opinions and data contained in all publications are solely those of the individual author(s) and contributor(s) and not of MDPI and/or the editor(s). MDPI and/or the editor(s) disclaim responsibility for any injury to people or property resulting from any ideas, methods, instructions or products referred to in the content. |
© 2023 by the authors. Licensee MDPI, Basel, Switzerland. This article is an open access article distributed under the terms and conditions of the Creative Commons Attribution (CC BY) license (https://creativecommons.org/licenses/by/4.0/).
Share and Cite
Imane, L.; Noureddine, M.; Driss, S.; Hanane, L. Towards Blockchain-Integrated Enterprise Resource Planning: A Pre-Implementation Guide. Computers 2024, 13, 11. https://doi.org/10.3390/computers13010011
Imane L, Noureddine M, Driss S, Hanane L. Towards Blockchain-Integrated Enterprise Resource Planning: A Pre-Implementation Guide. Computers. 2024; 13(1):11. https://doi.org/10.3390/computers13010011
Chicago/Turabian StyleImane, Lahlou, Motaki Noureddine, Sarsri Driss, and L’yarfi Hanane. 2024. "Towards Blockchain-Integrated Enterprise Resource Planning: A Pre-Implementation Guide" Computers 13, no. 1: 11. https://doi.org/10.3390/computers13010011
APA StyleImane, L., Noureddine, M., Driss, S., & Hanane, L. (2024). Towards Blockchain-Integrated Enterprise Resource Planning: A Pre-Implementation Guide. Computers, 13(1), 11. https://doi.org/10.3390/computers13010011