Manufacturers constantly strive to serve their customers better and, at the same time, use customer insights to improve product performance and reduce costs. Thanks to falling costs of sensor technology and the cloud’s ability to store and analyze huge amounts of data, manufacturers have found new ways to gather insights into both the product and the customer. They have also started extending this to their own engineering and manufacturing operations, making it possible to create a digital thread of the products they conceive, produce, sell, and service. Blockchain allows us to capture, maintain, and share the huge amount of data as well as use it for any advanced analysis or simulation of past events or future scenarios.
This paper explains various components of the system and how organizations can use them effectively to become leaders in their field of operations.
Why digital thread?
Digital thread is a framework that integrates design, engineering, suppliers, manufacturing, maintenance, warehouse, transportation, warranty and service operations, and systems to provide a seamless flow of information. It leverages the captured data/digital thread of the product to perform key analytics across the complete product lifecycle in order to optimize processes capability, efficiency and effectiveness, product design, asset performance/OEE, manufacturing operations, service operations, customer satisfaction, and to improve and maintain brand reputation. Digital thread includes key traceability/genealogy attributes/records of the product and its parts and features the manufacturer’s name, part number, country of origin, manufacturing plant, production line information, date of manufacturing, actual process parameters applied during manufacturing and assembly of the individual product, process history, lot code/date code, and other relevant records. This helps OEMs, service providers, and stake holders to:
Isolate products in the field with potentially faulty components or certain traceability attributes (such as serial number, manufacturer’s name, date code/batch number)
Proactively recall/repair products assembled with faulty components
Track the complete history of the product (cradle to grave) during its lifecycle to better predict operational behavior and improve product reliability through better design and process capabilities
Effectively manage warranty and service to improve customer satisfaction and brand loyalty
Facilitate better supplier management process
Reduces liability costs.
Having a digital thread of any product improves product reliability, customer service, product design, and brand reputation. It also reduces the number of fraudulent warranty claims and leads to a better competitive position.
Key requirements for implementing digital thread projects
The implementation of a digital thread depends on the type of product and industry. It may be necessary in order to comply with regulatory requirements, bolster customer satisfaction, or serve as a competitive differentiator. Usually, the channel master/OEM leads the digital thread project implementation across the chain. Selecting a digital thread solution requires identifying the right use/business case. It is equally important that business KPIs be clearly mapped with the business problems/case or goals to be resolved or achieved. This approach will help business and IT teams to:
Determine data elements and records that need to be captured along the supply chain
Identify the source of data records
Determine how and how often (sampling plan, frequency) the data will have to be collected
Estabilsh which parts (along with their respective supplier/manufacturers) will be impacted since the genealogy records of identified parts will have to be associated with the serial number of the product during the manufacturing and assembly process of the product
Collect key stages of data record processing
Existing system capabilities (including desired system capabilities)
Need of AIDC (automatic identification and data capture) technologies such as RFID, bar code, IT system (e.g., MES, WMC, transport management system, IIoT, etc.) to capture the desired data along the supply chain.
Because multiple parties are involved in a supply chain to move the final product from raw material suppliers to the end consumer and because the product passes through various process stages, locations, and entities during its journey, it creates many transaction records in various systems. In order to build a digital thread, each system must capture, validate, and store the necessary data elements in real time and store the captured data for future reference and key operational analytics. Each party in the supply chain may have their own set of systems for storing data, or each party can send data to a centralized repository to maintain it securely. Below are the key requirements for implementing digital thread projects:
Supplier alignment and compliance: alignment of parts suppliers is essential in implementing the digital thread. The digital thread of any product includes the genealogy records of the parts (manufacture/supplier name, manufacturer/supplier part number, OEM part number, date of manufacturing/date code, batch/lot code, serial number of parts, etc.) that have been used to manufacture and assemble it. All the data elements should be standardized across suppliers. Moreover, OEM/manufacturing partners should continuously evaluate suppliers to ensure completeness and accuracy of the records as per the contractual requirements between the OEMs and the suppliers (smart contracts).
Manufacturing partners: If the manufacturing process is outsourced, the manufacturing partners also need to align their data collection (building a digital thread) strategy as per the OEM’s requirement. This would require that the digital thread of each unit of the product be sent from the manufacturing partner’s system to the OEM system.Too build a digital thread in real time, manufacturing partners must implement integrated information systems so they can collect the right data along the process (ERP, MES, DCS/OPC, test equipment, quality, WMS, etc.).
Genealogy records for parts supplied by suppliers can be captured in ERP at the receiving area. However, linking the genealogy records of parts with their upper-level assembly (serial number) will normally take place at the respective stages of the production process (as per the process flow/routing) through the MES/shop floor system followed by BOM validation. Similarly, process parameter records can be captured during the manufacturing phase (through OPC/DCS – MES) followed by validation with machine programs/process specification. Validation rules must be built at each stage of the production flow to ensure that the data/digital thread are correct and complete. In essence, a complete process history/digital thread of each unit has to be built as the product moves along the supply chain, touching different systems where each system will capture, associate, and store parameter/data elements (along with the time stamp) validated with specifications.
OEM: While receiving and updating digital thread records from the manufacturing partner’s location, the records have to be validated as per the SLAs/contractual requirements at the receiving server of the OEM. If the digital thread for any unit is incorrect, the system should raise an alert to the manufacturing partner so that they know which records need to be updated. These records are crucial to performing key analytics.
Sales organization: should associate the product serial number with the sales order to capture customer details (name, location, product installation site, etc.).
Transport: should capture the complete history of the product while it is in transit. Food, pharmaceuticals, and other perishable products that require specific temperature, humidity, or other packaging parameters should be monitored in real time and the data recorded in respective databases for future references.
Warranty and service: service teams should capture the date of installation, product performance parameters, and other details, such as actions taken to resolve issues when installing and repairing the product.
IT system: the IT system requirement depends on the supply chain party and on the role that party plays in the end-to-end supply chain. For example, tier-one suppliers have to provide genealogy records of the part they are supplying to the OEM/manufacturing partner. To capture genealogy records at batch level, suppliers at the very least need an ERP system to capture batch records of parts. Similarly, OEM/manufacturing partners must implement both ERP and MES systems to receive material in ERP and associate parts with upper level or top level assembly and capture process records from each production stage during production process. This is possible with MES or shop floor system. Therefore, the system required will depend on the supply chain party and their role.
Figure 1 – Digital thread implementation architecture with centralized database
Use of AIDC technologies in the digital thread – Automatic identification and data capture technologies provide the basis for implementing the digital thread and help identify objects for data needs be collected. This technology includes barcodes, scanners, and RFID tags. Technology helps to ensure that data elements are captured in an accurate and timely way into the system. Manual entries are mostly offline, sometimes biased, and easy to manipulate and this will always mislead and may have severe impact on business. Also, it is practically impossible to capture, validate, and send operational and tracking records manually in high-volume and complex manufacturing processes.
Infrastructure: Implementation of digital thread also requires the right infrastructure; the bandwidth of the network should be identified based on the operation’s complexity, product complexity, real-time vs batch processing of data, cost, etc. Database capacity is another critical need and data retention period needs, performance, analytics requirements, on-premises vs cloud, customer requirements, regulatory compliance, etc. should also be considered by each party in the supply chain when selecting the right size.
Audits: Digital thread systems should support quick audits to ensure supplier conformance, data quality , validation rules, etc.
Figure 1 indicates the high-level, digital thread solution architecture for a simple product from tier-one suppliers to tier-one customers. The solution depicts key data elements can be captured to build digital thread with single centralized data base and with basic reporting through a simple analytics engine (just for reference).
How can blockchain support the digital thread?
A blockchain is a distributed database technology that builds on a tamper-proof list of time-stamped transaction records. Its innovative power stems from allowing supply chain parties to transact with others they do not trust over a global network in which nobody is trusted. It enables by a combination of peer-to-peer networks, consensus-making, cryptography, and market mechanisms. Each constituent of this database represents a “block.”
We realized that blockchain has several capabilities that can be leveraged in building genealogy and digital threads for products across industry verticals (aerospace, defense, food, automotive, pharma, consumer electronics, communications, etc.) that will benefit OEMs, suppliers, service providers, consumers, and governments. In this paper, we discuss the feasibility of implementing the digital thread on blockchain technology for manufacturing industries. The objective of this section is to discuss how blockchain technology can support the implementation of digital threads
In essence, blockchain is a peer-to-peer database that offers access to the history of all previous states. Furthermore, Some of the blockchain’s characteristics that directly support digital thread solution implementation are:
Distributed data bases and peer-to-peer network: Blockchain can capture and link specific data blocks across all the stages, from suppliers, manufacturing, assembly, testing, etc. up until te final unit of the product reaches the customer. Also, from customer site product can send its operational data to the blockchain, so it eliminates the need for investment in data storage capacities to handle the millions of records generated during the manufacturing and assembly process.
Support smart contracts between supply chain stages (inter organization and within organization): Blockchain’s smart contract functionality enables validation rules that can be written between the supply chain stages (external and internal) to ensure that data is not missed and that data is accurate and complete. For example, in order to build the digital thread, association of genealogy records of key parts to upper level assembly/product, the respective suppliers must provide certain mandatory genealogy records of that part, which requires validation at the OEM end while receiving that part at the OEM end to ensure supplier compliances. Also, during the manufacturing and assembly process, genealogy records of parts have to be associated with product serial numbers. This requires validation from BOM and routing files to ensure that the correct part is being assembled at the correct stage and requires validation of actual process parameters from recipe or machine programs. Smart contracts can be specified along the manufacturing and assembly process. At each stage, validation will be performed and if anything does not meet the smart contract’s terms and conditions, the system will raise an alarm on a real-time basis to avoid any potential issues that may impact the business.
Build trust by ensuring data accuracies and authenticity: Through the use of smart contracts and validation scripts, blockchain provides excellent capabilities to ensure (right from the source of the data) that the right data is being captured from the right source in the right sampling plan at the right time across all the stages of the supply chain. Data blocks that consist of records become immutable once on the blockchain. This is key to ensuring trust between parties located thousands of miles apasrt in global and complex supply chains. Moreover, a copy of the entire blockchain is held on every node on the network and consensus is achieved either by proof-of-work or proof-of-stake algorithms or by forming smart contracts.
Easy to audit: A blockchain by design is perfectly auditable. Each individual operation’s records (for example part genealogy records from a supplier/manufacturer) can be easily recorded, validated, and archived. These can be easily audited for supplier non-compliance, therefore auditing is as simple as joining the blockchain network, as this allows one to replay past operations. It is combined with cost-effective guarantees of authenticity for every record.
Access to the right stakeholders/users – security: An interesting aspect is that blockchain can be used as an authentication provider. Using their key pair, users register their identity on the blockchain. Another way to enable security is to provide membership services to manage user identities on a permission blockchain network through the Certificate Authority peer. Membership services provide a distinction of roles by combining elements of public key infrastructure (PKI) and decentralization (consensus). By contrast, non-permission networks do not provide member-specific authority or a distinction of roles. With blockchain technology, monitoring transactions will be more secure and transparent. Digital thread is actually a series of transaction nodes that link to capture data while products move from one point to other. By utilizing this technology to capture and store data across the supply chain, companies can reduce time delays, cost, and human error.
Cost of implementation: Blockchain significantly lowers the cost of a transaction while ensuring data accuracy, completeness, transparency, and security. It eliminates the need for a centralized trusted party and the need for investments in data storage capacity (for example, in some of industries, the OEM is required to retain product data for more than 15 years (regulatory compliance)).
Architecture diagram – digital thread on blockchain
Challenges to implementing the digital thread on blockchain
Below are the challenges we should consider when considering blockchain for digital thread solutions:
New technology: Resolving challenges such as transaction speed, the verification process, and data limits will be crucial in making blockchain widely applicable.
Frequent configuration: Each product requires configuration and the development of validation rules/smart contacts to capture product-specific and accurate data along the supply chain – a time consuming but one-time activity.
Integration concerns: Blockchain applications offer solutions that require changes/modifications and the customization of existing IT systems. To implement digital thread projects on time, smoothly, and within budget, companies must strategize the system integration and customization. Also, it is not yet clear how integration between blockchain and other systems, such as ERP, MES, PLM, and WMS, will occur.
Higher energy consumption: Use substantial amounts of computer power to validate millions of records generated across the supply chain
Control, security, and privacy : While solutions exist, including private or permissioned blockchain and strong encryption, there are still cybersecurity concerns to be addressed before the general public will entrusts their personal data to a blockchain solution.
Blockchain represents a complete shift to a decentralized network which requires the buy-in of its users and operators. Conversely, the digital thread can easily be implemented on a centralized solution (on premises or cloud based).
Blockchain offers tremendous savings in transaction costs and time but the high initial capital costs could be a deterrent.
Blockchain provides an excellent platform for digital thread implementation. Its capability to validate each record captured along the supply chain, including production processes (i.e. in end-to end journey of product), helps OEMs ensure accurate and tamper-proof data that builds trust between the supply chain and external parties. The digital thread can meet the objectives of various stakeholders in the chain (design team, suppliers, OEM, warranty and service providers, etc.) and helps to improve product reliability, process capability, and plant capacity by eliminating unplanned downtime. It also enables effective warranty management and significantly improves brand reputation while keeping cost at optimum levels.
Implementing the digital thread on blockchain might be challenging initially since blockchain is a new technology. Therefore, it is highly recommended to go with a low-risk approach, i.e. a POC that uses blockchain internally (within the organization) with a couple of critical parts suppliers/manufacturers as a database for recording part and product genealogy data, supplier/manufacturer data, internal data, use of smart contracts at selected stages, i.e. from part supplier (supplier to OEM), inspection and test records of parts (based on smart contracts that may include verification of mandatory records and SLA,s), date of manufacturing, as-built records (where part is associated with product to create genealogy as per BOM validations), capture process parameter that influence product performance, etc. along with the validation scripts. Implementing and testing a smaller portion of digital thread use cases will help organizations develop the skills they need for full-scale implementation.
For successful implementation, the key is to select the right blockchain service provider. Doing so will help organizations achieve their targeted objectives. There are a few cloud-based blockchain services from both start-ups and large platforms (such as Amazon, IBM and Microsoft), that make implementation of business solutions much easier. It is highly recommended to have a collaborative model between blockchain service providers, parts suppliers, manufacturing partners, and other supply chain entities to achieve business objectives in a timely manner.