Fabricated component whole life cycle data chain construction lightweight tracking method

Abstract

This invention discloses a lightweight traceability method for constructing a data chain across the entire lifecycle of prefabricated components, relating to the field of data processing technology. The specific steps of this method are: encoding association, chain construction, cloud storage, request triggering, and hierarchical retrieval. This invention generates a unique digital identity code for each prefabricated component that spans its entire lifecycle, and associates this digital identity code with BIM model elements to generate associated data. Based on this associated data, a data chain is constructed according to the lifecycle time sequence and event nodes of the prefabricated component. Heterogeneous data from each event node are systematically linked to their corresponding event nodes, and the correlation degree between adjacent nodes is calculated to form a complete data chain. This allows the lifecycle data of prefabricated components to form an orderly and continuous association system around a unified code, achieving integrated data integration and node-based management at each stage, enabling full-process traceability of component data throughout its lifecycle.

Description

Technical Field

[0001] This invention relates to the field of data processing technology, specifically to a lightweight traceability method for constructing a data chain for the entire lifecycle of prefabricated components. Background Technology

[0002] With the accelerating pace of industrialization in the construction industry, prefabricated buildings, with their standardized production, high construction efficiency, and superior resource utilization, have become an important direction for the transformation and development of the construction industry. As the core component of prefabricated buildings, prefabricated components are involved in the entire life cycle of construction projects, from design and production to demolition. They are the key carrier for ensuring the quality of prefabricated building projects and achieving refined management. The industry's demand for traceability management of prefabricated component life cycle information is becoming increasingly urgent.

[0003] However, existing traceability methods for prefabricated components lack a systematic design. They fail to assign unique, life-cycle-long digital identification codes to components, nor do they construct a complete data chain organized by life-cycle event nodes based on these codes. Heterogeneous data is chaotically linked without unified identifiers. Furthermore, the storage of component data lacks dual retrieval indexes for component type and event time. Traceability requests are triggered by simply binding identification information, and data access scope is not defined according to user permissions during retrieval. There are no asynchronous loading or layered push processing methods, making accurate data matching and on-demand retrieval impossible. This results in a lack of effective integration and management of various types of data throughout the component's lifecycle, low data correlation, poor retrieval and matching efficiency, and a tendency for information loss and chaotic retrieval during traceability. Consequently, a complete traceability system is difficult to form, failing to meet the refined and standardized development requirements of prefabricated buildings and the industry's practical application needs for efficient traceability of prefabricated components throughout their entire lifecycle. Summary of the Invention

[0004] The purpose of this invention is to overcome the shortcomings of existing technologies and provide a lightweight traceability method for constructing a data chain for the entire lifecycle of prefabricated components. This invention generates a unique digital identity code for each prefabricated component that spans its entire lifecycle, and associates the digital identity code with BIM model elements to generate associated data. Based on this associated data, a data chain is constructed according to the lifecycle time sequence and event nodes of the prefabricated component. Heterogeneous data of each event node is orderly linked to the corresponding event node, and the correlation degree between adjacent nodes is calculated to form a complete data chain. This allows the lifecycle data of prefabricated components to form an orderly and continuous association system around a unified code, realizing the integrated integration and node-based management of data at each stage, and enabling full-process traceability of component data as the lifecycle progresses.

[0005] To solve the above-mentioned technical problems, this invention provides the following technical solution: a lightweight traceability method for constructing a full lifecycle data chain for prefabricated components, the specific steps of which are as follows:

[0006] Coding Association: A unique digital identity code is generated for each prefabricated component and is used throughout its entire life cycle. During the BIM design phase, the digital identity code is associated with the corresponding BIM model elements of the prefabricated component, forming a corresponding identity association between the prefabricated component entity and the BIM model, and generating BIM model association data with digital identity codes.

[0007] Chain construction: Based on the BIM model association data with digital identity codes, a data chain is constructed according to the life cycle time sequence of prefabricated components and event nodes. The heterogeneous data generated by each event node is orderly linked to the corresponding node to form a complete data chain.

[0008] Cloud storage: The complete data chain is stored on a cloud server, and a dual retrieval index is built for the complete data chain based on component type and event time, generating a cloud storage data chain with dual retrieval index;

[0009] Request triggering: Based on the digital identity code of prefabricated components, the digital identity code is bound to a QR code or RFID tag. At the prefabricated component site, a mobile terminal scans the QR code or RFID tag attached to the surface of the component to trigger a lightweight traceability request, which is then sent to the cloud server.

[0010] Layered retrieval: The cloud server receives lightweight traceability requests, matches the cloud storage data chain with dual retrieval indexes based on the digital identity code in the lightweight traceability requests, extracts the summary information of the prefabricated components and returns it to the mobile terminal, then defines the access scope of historical event data according to user permissions, asynchronously loads historical event data and pushes it in layers for the mobile terminal to view.

[0011] Furthermore, in the aforementioned coding association, a digital identity code is generated through a computer program. The digital identity code is generated in the form of a combination of prefabricated component type, production batch, production time, and unique serial number. During the BIM design phase, the association between the digital identity code and BIM model elements is completed through the secondary development interface of the BIM design software. The digital identity code is written into the inherent attribute field of the BIM model element. The digital identity code is stored synchronously with the attribute information of the BIM model element. The generated BIM model association data with the digital identity code is updated synchronously with the update of the BIM model, realizing the permanent binding of the digital identity code with the prefabricated component entity and BIM model element.

[0012] Furthermore, in the chain construction, the event nodes of the entire life cycle of the prefabricated component are first determined, including design, production, quality inspection, transportation, warehousing, hoisting, operation and maintenance, and dismantling. The event nodes are arranged in an orderly manner according to the actual occurrence time of each event, and an independent data storage unit is set up for each arranged event node. Each data storage unit uses a digital identity code as an association identifier. Then, the heterogeneous data generated by each event node is classified and organized according to the collection form, divided into structured data and unstructured data. A source identifier and collection timestamp are added to each category of heterogeneous data after classification. The heterogeneous data with source identifier and collection timestamp are uploaded to the data storage unit of the corresponding event node through a standardized data interface, completing the orderly connection of heterogeneous data under each event node. Each data storage unit forms a continuous data link based on the association identifier of the digital identity code according to the arrangement order of the event nodes. After the data link is formed, the node association degree between adjacent event nodes is calculated using the node association degree calculation formula, and the node association degree is synchronized to the node attributes of the data link, thereby forming a complete data link.

[0013] Furthermore, in the construction of the chain, the formula for calculating the node correlation degree is: ,in, For the first The and the first The degree of node correlation between adjacent event nodes For the first The and the first The overlap of heterogeneous data among adjacent event nodes is obtained by counting the number of identical data dimensions in the heterogeneous data stored by each event node. For the first The and the first The number of common data identifiers among adjacent event nodes is obtained by statistically analyzing the source identifiers of the heterogeneous data of each event node. For the first The total amount of heterogeneous data for each event node For the first The total amount of heterogeneous data for each event node is obtained by statistically analyzing the actual data storage volume in the data storage unit of each event node.

[0014] Furthermore, in the cloud storage, the complete data chain is stored on a cloud server using a distributed storage architecture. Each complete data chain is individually archived and configured with a separate storage directory based on its digital identity code. Then, based on the digital identity code of the complete data chain and the attribute information of each event node, a dual retrieval index is established for the complete data chain. First, the complete data chain is classified into three levels according to the material, specifications, and building usage location of the prefabricated components to generate a component type index. Then, the operation time of each event node in the complete data chain is hierarchically marked by year, month, day, and hour to generate an event time index. Finally, an association mapping relationship is established between the component type index and the event time index. This association mapping relationship is based on... The digital identity encoding uniquely binds the two types of indexes to each event node of the complete data chain. The association mapping relationship is entered into the index management unit of the cloud server and synchronized to the corresponding complete data chain. Then, the node association degree of each adjacent event node in the complete data chain is retrieved. The index matching degree calculation formula is used to calculate the index matching degree between the component type index, the event time index and the complete data chain. The index matching degree is then synchronized to the index management unit and the corresponding complete data chain. Finally, the dual retrieval index is bound and integrated with the complete data chain stored on the cloud server. The integrated data chain is marked with a retrieval identifier according to the digital identity encoding, thereby generating a cloud storage data chain with dual retrieval indexes.

[0015] Furthermore, in the cloud storage, the formula for calculating the index matching degree is: ,in, For index matching degree, For the first The and the first The degree of node correlation between adjacent event nodes The classification dimension coefficients for the component type index are determined by the actual dimensional division of the three-level classification of prefabricated components. The time level coefficient for the event time index is determined by the time level marking of the event time index. This represents the total number of event nodes in the complete data chain.

[0016] Furthermore, during the request triggering process, the digital identity code is bound to a QR code or RFID tag, and the binding information is synchronized to the cloud server. The QR code or RFID tag is attached to the outer surface of the prefabricated component by printing or pasting. The QR code or RFID tag stores the plaintext information of the digital identity code. When the QR code or RFID tag on the surface of the prefabricated component is scanned by a mobile terminal, the stored plaintext information of the digital identity code is parsed, a lightweight traceability request containing the plaintext information of the digital identity code is generated, and the lightweight traceability request is sent to the cloud server through a wireless communication network.

[0017] Furthermore, in the hierarchical retrieval, the cloud server receives a lightweight traceability request, matches the corresponding cloud storage data chain with dual retrieval indexes based on the digital identity code in the lightweight traceability request, and then extracts the summary information of the prefabricated components from the matched cloud storage data chain with dual retrieval indexes and the event nodes of the cloud storage data chain. The summary information includes the component model, manufacturer, qualification status, and current process position. After extraction, the summary information is returned to the mobile terminal in the form of a data packet via a wireless communication network. Then, user permissions are configured hierarchically according to management permissions, construction permissions, operation and maintenance permissions, and quality inspection permissions. The access scope of the historical event data of prefabricated components is defined, and historical event data is asynchronously loaded in the background using a batch loading method. The historical event data is divided into multiple data levels according to reverse time or event importance. Then, the index matching degree in the index management unit is retrieved, and the push priority of each data level is calculated using the data push priority calculation formula. The push order of the data levels is determined according to the push priority, and the data levels are pushed to the mobile terminal for viewing.

[0018] Furthermore, in the hierarchical retrieval, the formula for calculating the data push priority is: ,in, For the first Push priority at each data level The larger the value, the higher the priority of the corresponding data level for push notifications, and the earlier the notification appears in the push order. For index matching degree, For the first The event importance coefficients at each data level are determined by assessing the importance of events at each data level based on the actual needs of prefabricated component lifecycle management. For the first The time decay coefficient for each data level is determined by the time difference between the collection time of the corresponding event and the trigger time of the trace request.

[0019] Compared with existing technologies, this lightweight traceability method for constructing a full lifecycle data chain for prefabricated components has the following advantages:

[0020] I. This invention generates a unique digital identity code for each prefabricated component that spans its entire lifecycle, and associates the digital identity code with BIM model elements to generate associated data. Based on this associated data, a data chain is constructed according to the lifecycle time sequence and event nodes of the prefabricated component. Heterogeneous data of each event node is orderly linked to the corresponding event node, and the correlation degree between adjacent nodes is calculated to form a complete data chain. This allows the lifecycle data of the prefabricated component to form an orderly and continuous associated system around a unified code, realizing the integrated integration and node-based management of data at each stage, and enabling the component data to be traced throughout the entire lifecycle.

[0021] II. This invention generates a cloud-stored data chain with dual retrieval indexes by storing the complete data chain on a cloud server and establishing dual retrieval indexes for component type and event time. Digital identity codes are then bound to QR codes or RFID tags. A traceability request is triggered by scanning the data chain on a mobile terminal. The cloud server matches the corresponding cloud-stored data chain, extracts the summary information, and returns it. At the same time, the data access scope is defined according to user permissions, historical event data is loaded asynchronously and pushed in layers, making the triggering of component traceability requests more standardized. Data retrieval can achieve accurate matching based on dual indexes, and data retrieval can achieve differentiated and on-demand acquisition according to different user permissions, forming a lightweight traceability system for the entire process from request triggering to data display.

[0022] Other advantages, objectives and features of the invention will be set forth in part in the description which follows, and in part will be apparent to those skilled in the art from the following examination or study, or may be learned from the practice of the invention. Attached Figure Description

[0023] To more clearly illustrate the technical solutions in the embodiments of the present invention or the prior art, the accompanying drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are merely some embodiments of the present invention. For those skilled in the art, other drawings can be obtained based on these drawings without any creative effort.

[0024] Figure 1 A flowchart illustrating a lightweight traceability method for building a data chain across the entire lifecycle of prefabricated components;

[0025] Figure 2 A framework diagram for constructing a lightweight traceability method for a data chain covering the entire lifecycle of prefabricated components;

[0026] Figure 3 A framework diagram of chain construction in a lightweight traceability method for building a data chain throughout the entire lifecycle of prefabricated components. Detailed Implementation

[0027] To further illustrate the technical means and effects of the present invention in achieving its intended purpose, the following detailed description of the specific implementation methods, structures, features, and effects of the present invention, in conjunction with the accompanying drawings and preferred embodiments, is provided below.

[0028] Example:

[0029] Taking the prefabricated concrete interior wall panels used in the 15th standard floor of Building 3 in a high-rise residential project as the specific implementation object, the lightweight traceability of the prefabricated interior wall panels throughout the entire life cycle from design to operation and maintenance is realized in actual engineering scenarios.

[0030] Coding Association: After completing the BIM model construction of the precast concrete interior wall panel, a unique digital identity code is generated through a computer program, lasting throughout its entire lifecycle. This digital identity code is a combination of the precast component type, production batch, production time, and a unique serial number, specifically HNQNB-202509-20250915-0289. This digital identity code is unique and unchanging throughout the entire process, becoming the exclusive identifier for the precast component. During the BIM design phase, through the secondary development interface of Revit software, this digital identity code is precisely associated with the corresponding BIM model element of the precast interior wall panel. The digital identity code is written into the inherent attribute field of the BIM model element, allowing it to be stored synchronously with the attribute information of the BIM model element, generating BIM model association data with the digital identity code, such as... Figure 1 As shown, the BIM model-related data will be updated synchronously with the design optimization of the BIM model, ultimately realizing the permanent binding of digital identity codes with prefabricated concrete interior wall panel entities and BIM model elements, forming a unique corresponding identity association between prefabricated interior wall panel entities and BIM models, laying a unified identity foundation for subsequent full life cycle data traceability.

[0031] Chain construction: Based on BIM model association data with digital identity codes, such as... Figure 2As shown, the data chain construction work for precast interior wall panels was carried out. First, the event nodes of the entire life cycle of the precast concrete interior wall panels were determined as design, production, quality inspection, transportation, warehousing, hoisting, operation and maintenance, and demolition. The event nodes were arranged in an orderly manner according to the chronological order of their occurrence in the actual project, and an independent data storage unit was set up for each arranged event node. Each data storage unit used a digital identity code HNQNB-202509-20250915-0289 as a unique identifier to ensure that data from each node was collected around a unified code. In each stage of component production, quality inspection, and transportation, the heterogeneous data generated by each event node was classified and organized according to the collection format, divided into structured data and unstructured data. Among these, design parameters... Data such as numbers, production team records, and strength test values ​​are structured data, while images of hoisting sites, scanned copies of quality inspection reports, and screenshots of transportation GPS tracks are unstructured data. Each category of heterogeneous data is assigned a unique source identifier and collection timestamp. Through a standardized data interface for the construction industry, this heterogeneous data with source identifiers and collection timestamps is uploaded to the data storage unit of the corresponding event node, completing the orderly connection of heterogeneous data under each event node and effectively avoiding data chaos and mismatch issues. Each data storage unit forms a continuous data link based on the association identifier of its digital identity code, arranged in the order of the event nodes. After the data link is formed, the node association degree between adjacent event nodes is calculated using the node association degree calculation formula: ,in, For the first The and the first The degree of node correlation between adjacent event nodes For the first The and the first The overlap of heterogeneous data among adjacent event nodes is obtained by counting the number of identical data dimensions in the heterogeneous data stored by each event node. For the first The and the first The number of common data identifiers among adjacent event nodes is obtained by statistically analyzing the source identifiers of the heterogeneous data of each event node. For the first The total amount of heterogeneous data for each event node For the first The total heterogeneous data volume of each event node is obtained by statistically analyzing the actual data storage volume in the data storage unit of each event node; and the node correlation is synchronized to the node attributes of the data chain, ultimately forming a complete data chain for the prefabricated interior wall panel, such as... Figure 3 As shown, this enables continuous and node-based management of component lifecycle data.

[0032] Cloud Storage: The complete data chain of prefabricated concrete interior wall panels is uploaded and stored on a cloud server using a distributed storage architecture. Each complete data chain is individually archived and configured with a separate storage directory using the digital identity code HNQNB-202509-20250915-0289, ensuring that the data chain for each component is stored independently and without interference. Based on the digital identity code of the complete data chain and the attribute information of each event node, a dual retrieval index is established for the complete data chain. First, the complete data chain is classified into three levels according to the material, specifications, and building usage location of the prefabricated components, generating a component type index. Then, each event in the complete data chain is indexed... The operation time of nodes is hierarchically marked by year, month, day, and hour to generate an event time index. Then, an association mapping relationship is established between the component type index and the event time index. This association mapping relationship uniquely binds the two types of indexes to each event node in the complete data chain based on digital identity encoding. The association mapping relationship is entered into the index management unit of the cloud server and synchronized to the corresponding complete data chain, achieving a precise correspondence between the index and the data chain. Next, the node association degree of each adjacent event node in the complete data chain is retrieved, and the index matching degree between the component type index, the event time index, and the complete data chain is calculated using the index matching degree calculation formula: ,in, For index matching degree, For the first The and the first The degree of node correlation between adjacent event nodes The classification dimension coefficients for the component type index are determined by the actual dimensional division of the three-level classification of prefabricated components. The time level coefficient for the event time index is determined by the time level marking of the event time index. The total number of event nodes in the complete data chain is calculated; then the index matching degree is synchronized to the index management unit and the corresponding complete data chain to optimize the matching effect between the index and the data chain; finally, the dual retrieval index is bound and integrated with the complete data chain stored on the cloud server, and the integrated data chain is marked with a retrieval identifier according to the digital identity code, and finally a cloud storage data chain with dual retrieval index is generated, laying the foundation for subsequent fast retrieval and accurate data matching.

[0033] Request Triggering: Based on the digital identity code HNQNB-202509-20250915-0289 of the precast concrete interior wall panel, this digital identity code is bound to a customized QR code, and the binding information is synchronized to the cloud server. The QR code is attached to the non-load-bearing outer surface of the precast interior wall panel using industrial inkjet printing. The QR code stores the plaintext information of the digital identity code, and the surface of the QR code is treated to be scratch-resistant and wear-resistant, adapting to the complex transportation and stacking environment of the construction site. When the precast interior wall panel is transported and stored and then delivered to the construction site, and on-site construction personnel need to verify component information and confirm construction parameters, they scan the QR code on the surface of the precast interior wall panel using an industrial-grade mobile terminal at the construction site. The mobile terminal quickly parses the plaintext information of the digital identity code stored in the QR code, and then automatically generates a lightweight traceability request containing the plaintext information of the digital identity code. The lightweight traceability request is quickly sent to the cloud server through the wireless communication network. The entire operation is convenient and adaptable to the mobile operation needs of the construction site.

[0034] Layered retrieval: Upon receiving a lightweight traceability request from a mobile terminal, the cloud server immediately uses the digital identity code HNQNB-202509-20250915-0289 in the request to precisely match the corresponding cloud storage data chain with dual retrieval indexes in the cloud server's database. Leveraging the matching advantage of dual retrieval indexes, the data chain is quickly located without redundant data traversal. Subsequently, from the matched cloud storage data chain with dual retrieval indexes and its event nodes, the summary information of the precast concrete interior wall panel is precisely extracted. This summary information specifically includes the component model, manufacturer, qualification status, and current process location. After extraction, the summary information is instantly returned to the mobile terminal via wireless communication network in the form of a data packet. Construction personnel can directly view the information on the mobile terminal screen. Viewing core summary information allows for quick access to key component information without waiting for large amounts of data to load. The cloud server simultaneously configures user permissions according to management, construction, operation and maintenance, and quality inspection levels. For on-site construction personnel performing this operation, the system automatically defines their access scope for historical event data related to prefabricated components, granting access only to production, quality inspection, and hoisting-related data while blocking irrelevant management data. Historical event data within this access scope is asynchronously loaded in the background using a batch loading method, without consuming front-end resources and ensuring smooth operation on mobile devices. The loaded historical event data is then divided into multiple data levels in reverse chronological order. The index matching degree in the cloud server's index management unit is then retrieved, and the push priority for each data level is calculated using the data push priority calculation formula: ,in, For the first Push priority at each data level The larger the value, the higher the priority of the corresponding data level for push notifications, and the earlier the notification appears in the push order. For index matching degree, For the first The event importance coefficients at each data level are determined by assessing the importance of events at each data level based on the actual needs of prefabricated component lifecycle management. For the first The time decay coefficient of each data level is determined by the time difference between the collection time of the corresponding event and the trigger time of the traceability request. The push order of the data levels is determined by the value of the push priority. The larger the value, the earlier the push order, ensuring that construction personnel can view the latest and most relevant component data first. The cloud server pushes the data levels to the mobile terminal in this order. Construction personnel can view the historical event data of the corresponding level through the mobile terminal, realizing the lightweight traceability of the precast interior wall panel and fully adapting to the rapid operation needs of the construction site.

[0035] In summary, taking prefabricated concrete interior wall panels as the implementation object, the entire process of coding association, chain construction, cloud storage, request triggering, and hierarchical retrieval is completed sequentially. Coding association establishes the corresponding identity association between the component entity and the BIM model; chain construction forms a complete data chain; cloud storage generates a cloud storage data chain with dual retrieval indexes; lightweight traceability request triggering is achieved through barcode scanning; and finally, hierarchical retrieval enables rapid return of component summary information and on-demand retrieval of historical event data. This effectively realizes lightweight traceability throughout the entire lifecycle of prefabricated components, adapting to the traceability application needs of actual prefabricated building engineering scenarios.

[0036] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention in any way. Although the present invention has been disclosed above with reference to preferred embodiments, it is not intended to limit the present invention. Any person skilled in the art can make some modifications or alterations to the above-disclosed technical content to create equivalent embodiments without departing from the scope of the present invention. Any simple modifications, equivalent changes and alterations made to the above embodiments based on the technical essence of the present invention without departing from the scope of the present invention shall still fall within the scope of the present invention.

Claims

1. A lightweight traceability method for constructing a data chain across the entire lifecycle of prefabricated components, characterized in that, The specific steps of this method are as follows: Coding Association: A unique digital identity code is generated for each prefabricated component and is used throughout its entire life cycle. During the BIM design phase, the digital identity code is associated with the corresponding BIM model elements of the prefabricated component, forming a corresponding identity association between the prefabricated component entity and the BIM model, and generating BIM model association data with digital identity codes. Chain construction: Based on the BIM model association data with digital identity codes, a data chain is constructed according to the life cycle time sequence of prefabricated components and event nodes. The heterogeneous data generated by each event node is orderly linked to the corresponding node to form a complete data chain. Cloud storage: The complete data chain is stored on a cloud server, and a dual retrieval index is built for the complete data chain based on component type and event time, generating a cloud storage data chain with dual retrieval index; Request triggering: Based on the digital identity code of prefabricated components, the digital identity code is bound to a QR code or RFID tag. At the prefabricated component site, a mobile terminal scans the QR code or RFID tag attached to the surface of the component to trigger a lightweight traceability request, which is then sent to the cloud server. Layered retrieval: The cloud server receives lightweight traceability requests, matches the cloud storage data chain with dual retrieval indexes based on the digital identity code in the lightweight traceability requests, extracts the summary information of the prefabricated components and returns it to the mobile terminal, then defines the access scope of historical event data according to user permissions, asynchronously loads historical event data and pushes it in layers for the mobile terminal to view.

2. The lightweight traceability method for constructing a full lifecycle data chain for prefabricated components according to claim 1, characterized in that, In the aforementioned coding association, a digital identity code is generated through a computer program. The digital identity code is generated in the form of a combination of prefabricated component type, production batch, production time, and unique serial number. During the BIM design phase, the association between the digital identity code and BIM model elements is completed through the secondary development interface of the BIM design software. The digital identity code is written into the inherent attribute field of the BIM model element. The digital identity code is stored synchronously with the attribute information of the BIM model element. The generated BIM model association data with the digital identity code is updated synchronously with the update of the BIM model.

3. The lightweight traceability method for constructing a full lifecycle data chain for prefabricated components according to claim 1, characterized in that, In the chain construction, the event nodes of the entire life cycle of the prefabricated component are first determined, including design, production, quality inspection, transportation, warehousing, hoisting, operation and maintenance, and dismantling. The event nodes are arranged in an orderly manner according to the actual occurrence time of each event, and an independent data storage unit is set up for each arranged event node. Each data storage unit uses a digital identity code as an association identifier. Then, the heterogeneous data generated by each event node is classified and organized according to the collection form, and divided into two categories: structured data and unstructured data. A source identifier and collection timestamp are added to each category of heterogeneous data after classification. The heterogeneous data with source identifier and collection timestamp are uploaded to the data storage unit of the corresponding event node through a standardized data interface, completing the orderly connection of heterogeneous data under each event node. Each data storage unit forms a continuous data link based on the association identifier of the digital identity code and arranged in the order of event nodes. After the data link is formed, the node association degree between adjacent event nodes is calculated by the node association degree calculation formula, and the node association degree is synchronized to the node attributes of the data link, thereby forming a complete data link.

4. The lightweight traceability method for constructing a full lifecycle data chain for prefabricated components according to claim 3, characterized in that, In the chain construction, the formula for calculating the node correlation degree is: ,in, For the first The and the first The degree of node correlation between adjacent event nodes For the first The and the first The degree of overlap of heterogeneous data between adjacent event nodes For the first The and the first The number of common data identifiers among adjacent event nodes. For the first The total amount of heterogeneous data for each event node For the first The total amount of heterogeneous data for each event node.

5. A lightweight traceability method for constructing a full lifecycle data chain for prefabricated components according to claim 1, characterized in that, In the cloud storage, the complete data chain is stored on a cloud server using a distributed storage architecture. Each complete data chain is individually archived and configured with a separate storage directory based on its digital identity code. Then, based on the digital identity code of the complete data chain and the attribute information of each event node, a dual retrieval index is established for the complete data chain. First, the complete data chain is classified into three levels according to the material, specifications, and building usage location of the prefabricated components to generate a component type index. Then, the operation time of each event node in the complete data chain is hierarchically marked with year, month, day, and hour to generate an event time index. Finally, a mapping relationship is established between the component type index and the event time index. This mapping relationship is based on digital identity codes. The identity code uniquely binds the two types of indexes to each event node of the complete data chain. The association mapping relationship is entered into the index management unit of the cloud server and synchronized to the corresponding complete data chain. Then, the node association degree of each adjacent event node in the complete data chain is retrieved. The index matching degree calculation formula is used to calculate the index matching degree between the component type index, the event time index and the complete data chain. The index matching degree is then synchronized to the index management unit and the corresponding complete data chain. Finally, the dual retrieval index is bound and integrated with the complete data chain stored on the cloud server. The integrated data chain is marked with a retrieval identifier according to the digital identity code, thereby generating a cloud storage data chain with dual retrieval indexes.

6. A lightweight traceability method for constructing a full lifecycle data chain for prefabricated components according to claim 5, characterized in that, In the cloud storage, the formula for calculating the index matching degree is: ,in, For index matching degree, For the first The and the first The degree of node correlation between adjacent event nodes The classification dimension coefficient for the component type index. The time hierarchy coefficient for the event time index. This represents the total number of event nodes in the complete data chain.

7. A lightweight traceability method for constructing a full lifecycle data chain for prefabricated components according to claim 1, characterized in that, In the request triggering process, a digital identity code is bound to a QR code or RFID tag, and the binding information is synchronized to a cloud server. The QR code or RFID tag is attached to the outer surface of the prefabricated component by printing or pasting. The QR code or RFID tag stores the plaintext information of the digital identity code. When the QR code or RFID tag on the surface of the prefabricated component is scanned by a mobile terminal, the stored plaintext information of the digital identity code is parsed, a lightweight traceability request containing the plaintext information of the digital identity code is generated, and the lightweight traceability request is sent to the cloud server through a wireless communication network.

8. A lightweight traceability method for constructing a full lifecycle data chain for prefabricated components according to claim 1, characterized in that, In the hierarchical retrieval process, the cloud server receives a lightweight traceability request. Based on the digital identity code in the lightweight traceability request, it matches the corresponding cloud storage data chain with dual retrieval indexes. Then, it extracts summary information of the prefabricated components from the matched cloud storage data chain with dual retrieval indexes and the event nodes of the cloud storage data chain. The summary information includes the component model, manufacturer, qualification status, and current process position. After extraction, the summary information is returned to the mobile terminal in the form of a data packet via a wireless communication network. Then, user permissions are configured hierarchically according to management permissions, construction permissions, operation and maintenance permissions, and quality inspection permissions. The access scope of historical event data of prefabricated components is defined. Historical event data is asynchronously loaded in the background using a batch loading method. The historical event data is divided into multiple data levels according to reverse chronological order or event importance. Then, the index matching degree in the index management unit is retrieved. The push priority of each data level is calculated using the data push priority calculation formula. The push order of the data levels is determined according to the push priority, and the data levels are pushed to the mobile terminal for viewing.

9. A lightweight traceability method for constructing a full lifecycle data chain for prefabricated components according to claim 8, characterized in that, In the hierarchical retrieval, the formula for calculating the data push priority is: ,in, For the first Push priority at each data level The larger the value, the higher the priority of the corresponding data level for push notifications, and the earlier the notification appears in the push order. For index matching degree, For the first Event importance coefficients at each data level. For the first The time decay coefficient for each data level.

Images