A full-process tracing management method and system for fabricated building components

Abstract

This invention discloses a method and system for full-process traceability management of prefabricated building components, relating to the field of component management technology. The method includes: generating a digital twin for each prefabricated building component; acquiring business and process data of the event through a data collection terminal, and dynamically associating and binding the data with the component's digital twin; sequentially migrating the component's state based on the completion of the previous state event, forming an irreversible traceability data chain; providing a unified traceability query interface, and generating quality analysis reports and risk warning information based on aggregated data. The advantages of this invention are: by constructing a hybrid identification system, it effectively solves the problems of traditional single identification being easily damaged and having limited information carrying capacity during the complex flow of components, ensuring the full-cycle effectiveness and information capacity of the traceability identification.

Description

Technical Field

[0001] This invention relates to the field of component management technology, specifically to a method and system for full-process traceability management of prefabricated building components. Background Technology

[0002] In the field of prefabricated buildings, traceability of prefabricated components throughout the entire production, transportation, and installation process has become an essential requirement for achieving quality control and accountability. Traditional management methods rely heavily on paper documents or simple spreadsheets, resulting in fragmented and slow information flow, which fails to meet the efficiency, accuracy, and transparency requirements of modern engineering projects. Therefore, building a component traceability system using information technology to ensure building quality and improve construction collaboration efficiency is a clear direction for technological development in this field.

[0003] Currently, common traceability technologies primarily use QR codes or RFID tags as component identification carriers, recording key node information through scanning. However, these methods often have significant limitations: the identification carriers are easily damaged or detached during transportation and installation, leading to interruptions in the traceability chain; each link, such as the factory, logistics, and on-site information systems, operates independently, forming "information silos," making it difficult to connect data into a complete component "lifecycle"; traceability content is mostly text and photographs, lacking deep integration with the component's 3D design information, resulting in unintuitive problem localization and weak support for analysis and decision-making. Therefore, existing technologies struggle to achieve truly comprehensive, real-time, interlocked, and visualized refined management that spans the entire lifecycle of design, production, logistics, and construction. Summary of the Invention

[0004] To address the aforementioned technical problems, this paper provides a method and system for full-process traceability management of prefabricated building components. This technical solution solves at least one of the technical problems mentioned in the background section.

[0005] To achieve the above objectives, the technical solution adopted by the present invention is as follows:

[0006] A method for full-process traceability management of prefabricated building components includes:

[0007] S1. Component Identification and Model Initialization: Assign a unique and unchangeable permanent identification code to each prefabricated building component and generate a lightweight three-dimensional digital model corresponding to the component, which together form the basis of the component's digital twin.

[0008] S2. Full-process event definition and data binding: The life cycle of a component is divided into a series of preset state events, including production, storage, transportation, arrival, installation and acceptance events; when each state event occurs, the business data and process data of the event are acquired through the acquisition terminal, and the data is dynamically associated and bound with the digital twin of the component.

[0009] S3. Event-driven chained state transition: The state of a component is sequentially transitioned based on the completion of the previous state event. When a new state event operation is initiated for a component, the system must verify that the previous state event has been confirmed as completed. Only after the verification is passed can the current event operation be executed and the overall state of the component be updated, forming an irreversible traceable data chain.

[0010] S4. Visualized Traceability and Decision-Making Based on Digital Twins: Provides a unified traceability query interface. Users can scan the component entity identifier or select the component model in the 3D visualization scene. The system will then integrate and display the full-process historical data bound to the digital twin of the component, and generate quality analysis reports and risk warning information based on the aggregated data.

[0011] Preferably, in step S1, the allocated identifier system is a hybrid identifier system, specifically including:

[0012] Assign a permanent identification code to a component, either engraved or embedded in the component entity, and this code remains unchanged throughout its entire lifespan;

[0013] Simultaneously, one or more temporary carrier codes that can be dynamically attached or replaced are assigned to the component, and the temporary carrier codes are carried on QR code tags, RFID tags or accompanying documents;

[0014] The permanent identification code and the temporary carrier code are associated and mapped in the system background, so that all traceability information indexed by the permanent identification code can be indirectly accessed and manipulated by scanning the temporary carrier code.

[0015] Preferably, the attachment, replacement, and information update of the temporary carrier code follow the following rules:

[0016] The temporary carrier code is generated and associated for the first time when the component rolls off the production line, and is used for circulation within the factory and tracking of outbound logistics.

[0017] Once the components are transported to the construction site and pass the acceptance inspection, they can be replaced with on-site installation codes that include information on the project, building, floor, and unit location.

[0018] Each carrier code replacement operation is recorded as an independent status event and stored in the component's traceability data chain along with snapshots of the component's status before and after the replacement.

[0019] Preferably, in step S2, the data bound to the digital twin includes structured data and unstructured data, specifically:

[0020] Structured data should include at least: component production batch, material supplier information, key process parameters, inspection results, logistics trajectory coordinates, arrival time, installation location coordinates, and acceptance personnel;

[0021] Unstructured data includes at least: video recordings of key production stations, scanned copies of factory certificates of conformity, images captured during transportation of abnormal conditions, on-site acceptance photos, video clips of the installation process, and video recordings of grouting construction.

[0022] Preferably, the specific implementation of the chain-like state transition in step S3 includes:

[0023] The system pre-sets standardized operating procedures and templates for the data fields that must be uploaded for each type of status event;

[0024] When an operator attempts to confirm a status event via a mobile terminal, the terminal application guides them to complete standardized operations such as taking a photo, filling out a form, and selecting options, and automatically attaches the operation time, geographical location, and operator information;

[0025] Only after all the necessary data for the current event has been collected and submitted will the system mark the event as "complete" and automatically trigger the transition of the overall state of the component to the next preset state.

[0026] Preferably, the visual traceability and decision support in step S4 further includes:

[0027] Reverse tracing function: When a quality defect is discovered, the system can automatically locate all other components in the same production batch, raw material batch or process route by inputting the defective component information, and display their current status and location, so as to achieve rapid containment and recall.

[0028] Positive early warning function: Based on historical data models, it monitors key parameters of components under construction, in transit, and awaiting installation in real time. If the parameters deviate from the preset threshold or an abnormal pattern occurs, it proactively pushes early warning information to the preset responsible persons. The early warning information includes supplier quality fluctuation warnings, transportation time delay warnings, and installation progress lag warnings.

[0029] Furthermore, a full-process traceability management system for prefabricated building components is proposed to implement the aforementioned full-process traceability management method for prefabricated building components, including:

[0030] The identification management module is used to generate, assign, and manage the permanent identification code and temporary carrier code for each prefabricated building component, and maintain the mapping relationship between the two.

[0031] The digital twin engine module is responsible for the creation, storage, rendering and management of lightweight 3D models of components, and provides application programming interfaces for other modules to perform model and data binding operations.

[0032] The event flow-driven module is used to define the standard state event sequence for the entire lifecycle of a component, receive event data from various acquisition terminals, execute chained state verification and migration logic, and drive business processes.

[0033] The data aggregation and visualization module receives data from the event flow-driven module, integrates and associates it with the digital twins of the corresponding components, and provides interactive traceability queries and decision-making information displays in various forms such as 3D scenes, charts, and lists through web terminals, mobile terminals, or large-screen terminals.

[0034] Optionally, the system also includes intelligent data acquisition terminals deployed in different physical scenarios, including but not limited to:

[0035] Factory production data acquisition terminals are integrated into key workstations on the production line to automatically collect or have workers input production and inspection data.

[0036] Mobile handheld terminals are used by logistics personnel, on-site construction and supervision personnel to perform operations such as scanning codes, taking photos, filling out forms and confirming status events.

[0037] The Internet of Things (IoT) sensing terminals include GPS / BeiDou positioning units and attitude sensors integrated on transport vehicles, as well as monitoring equipment deployed on yards and tower cranes, for automatically collecting the location, environment, and image information of components.

[0038] Optionally, the event flow driving module includes a chained verification submodule, which is configured as follows:

[0039] Maintain a global component state mapping table to record the current state event nodes of each component in real time;

[0040] Whenever a new status event submission request is received, the current status of the component is queried and compared with the previous status required by the target event;

[0041] New event data will only be allowed to be submitted and the state mapping table updated if the comparison is consistent; otherwise, the request will be rejected and an error message will be returned, indicating the required prerequisite state.

[0042] Optionally, the data aggregation and visualization module embeds an intelligent analysis submodule, which is configured as follows:

[0043] Run the preset data analysis model to periodically mine the traceability data of the entire platform and generate multi-dimensional statistical analysis reports, including supplier performance evaluation reports, project schedule deviation reports, and common quality defect distribution reports;

[0044] It provides a configurable alert rule engine, allowing administrators to set alert rules based on data thresholds, trends, or logical combinations. When real-time data triggers a rule, an alert notification is automatically sent to a specified user or user group via a message queue.

[0045] Compared with the prior art, the beneficial effects of the present invention are as follows:

[0046] This invention effectively solves the problems of traditional single identifiers being easily damaged and having limited information capacity during complex component transfers by constructing a hybrid identification system, ensuring the full-cycle effectiveness and information capacity of traceability identifiers. By deeply integrating a lightweight 3D digital model with full-process business data, it achieves a precise mapping from abstract data to a visual model, enabling quality traceability to pinpoint specific locations and greatly improving the efficiency and accuracy of problem investigation. Simultaneously, this invention employs an event-driven chain-like state management mechanism, forcing business processes to proceed sequentially and interlocking with data, preventing information tampering and skipping steps, and ensuring the authenticity and integrity of traceability data. Finally, the system provides intelligent analysis and early warning based on aggregated full-chain data, enabling not only rapid reverse location of quality problems and containment of components in the same batch, but also proactive warning of potential risks. This significantly reduces quality and safety risks and operating costs while improving project management transparency and collaborative efficiency. Attached Figure Description

[0047] Figure 1 This is a flowchart of the whole-process traceability management method for prefabricated building components proposed in this invention. Detailed Implementation

[0048] The following description is intended to disclose the invention and enable those skilled in the art to implement it. The preferred embodiments described below are merely examples, and other obvious variations will occur to those skilled in the art.

[0049] Reference Figure 1 As shown, a method for full-process traceability management of prefabricated building components includes:

[0050] S1. Component Identification and Model Initialization: Each prefabricated building component is assigned a unique and unchangeable permanent identification code, and a corresponding lightweight 3D digital model is generated. Together, they form the foundation of the component's digital twin, establishing a unique and precise correspondence between the component in the physical and digital worlds. The permanent identification code, like an engraved or pre-embedded chip, ensures lifelong reliability of identification, overcoming the problem of traditional labels being easily damaged or detached. The lightweight 3D digital model originates from the design BIM, eliminating irrelevant details to ensure smooth visualization performance. The combined "digital twin foundation" provides the core carrier for the subsequent integration and visualization of massive amounts of data throughout the entire process, and is a prerequisite for achieving refined management.

[0051] S2. Full-Process Event Definition and Data Binding: The lifecycle of a component is divided into a series of pre-defined state events, including production, storage, transportation, arrival, installation, and acceptance events. When each state event occurs, business and process data for that event are acquired through a data collection terminal. This data is then dynamically associated and bound to the component's digital twin, deconstructing the continuous construction process into discrete, standardized "event" units, thus achieving structured management of complex processes. Each event clearly defines the scope and format of data collection, ensuring the integrity and standardization of information. By binding dynamically generated business data, such as "when and by whom to accept" and process data, such as "images during acceptance," to the static component digital twin in real time, the digital model is no longer merely a design graphic, but evolves into an intelligent entity carrying all key information of its "lifecycle," providing a data foundation for traceability and decision-making.

[0052] S3. Event-Driven Chained State Transition: The state of a component transitions sequentially based on the completion of the previous state event. When a new state event operation is initiated for a component, the system must verify that the previous state event has been confirmed as completed. Only after successful verification is the current event operation allowed to be executed and the overall state of the component updated, forming an irreversible traceability data chain. This introduces mandatory business logic constraints and is the core mechanism for ensuring the authenticity of the process and the integrity of the data chain. The system logic forces business operations to follow the predetermined sequence of "production → storage → transportation → arrival → installation," eliminating the possibility of data falsification such as "installing before production" or other process skipping or reversal. Each state transition strictly relies on the completion certificate of the preceding event, thus forming an interlocking, time-sensitive, and tamper-proof traceability data chain, greatly improving the credibility of the data and the authority of traceability.

[0053] S4. Visualized Traceability and Decision-Making Based on Digital Twins: Providing a unified traceability query interface, users can scan component entity identifiers or select component models in a 3D visualization scene. The system then integrates and displays the entire historical data bound to the component's digital twin, and generates quality analysis reports and risk warning information based on the aggregated data, elevating data value from mere "recording" to "insight." The unified query interface offers an excellent user experience, making traceability operations intuitive and convenient. By integrating and presenting full-dimensional data bound to the digital twin, the system transforms fragmented information into a complete "digital archive" of the component, achieving one-click, visualized, and precise traceability. Furthermore, through the aggregated analysis of the full archive data, the system can proactively generate reports and warnings, transforming passive querying into proactive management, thereby supporting quality improvement, risk prevention and control, and scientific decision-making, truly reflecting the value of data-driven intelligent management.

[0054] In step S1, the assigned identifier system is a hybrid identifier system, specifically including:

[0055] Assign a permanent identification code to a component, either engraved or embedded in the component entity, and this code remains unchanged throughout its entire lifespan;

[0056] At the same time, one or more temporary carrier codes that can be dynamically attached or replaced are assigned to the component. The temporary carrier codes are carried on QR code labels, RFID tags or accompanying documents.

[0057] The permanent identification code and the temporary carrier code are associated and mapped in the system backend, so that all traceability information indexed by the permanent identification code can be indirectly accessed and manipulated by scanning the temporary carrier code.

[0058] The attachment, replacement, and information updating of temporary carrier codes shall follow the following rules:

[0059] The temporary carrier code is generated and associated for the first time when the component rolls off the production line, and is used for internal circulation within the factory and for tracking outbound logistics.

[0060] Once the components are transported to the construction site and pass the acceptance inspection, they can be replaced with on-site installation codes that include information on the project, building, floor, and unit location.

[0061] Each carrier code replacement operation is recorded as an independent status event and stored in the component's traceability data chain along with snapshots of the component's status before and after the replacement.

[0062] In one specific embodiment of the present invention, the hybrid identification system operates as follows: First, during the component production stage, a unique permanent identification code consisting of "project code - component type - production batch - serial number" is assigned to non-critical structural parts such as the sides or ends via laser engraving or pre-embedded RFID chips. Simultaneously, the system automatically generates an initial temporary carrier code bound to this permanent code, typically in the form of a high-strength waterproof QR code label, affixed to a prominent position on the component surface. This temporary code serves as the primary data collection and status update entry point during internal factory circulation and outbound logistics. Once the component is transported to the designated construction site and passes on-site acceptance, on-site management personnel remove the initial logistics label and, based on the component's planned installation location in the BIM model (e.g., "Building A - 5th Floor - Unit 02"), apply to the system for and print a site installation code containing precise location information for replacement. The system records this "label replacement" operation as an independent status event, saving snapshots of the component's status before and after replacement, such as the component's acceptance status and geographical location at the time of replacement. Subsequently, on-site personnel can quickly verify component information and perform subsequent operations such as hoisting and grouting by scanning the installation code. Throughout the entire lifecycle, regardless of how the temporary carrier code is changed, all scanning operations and data entry are ultimately associated with and attributed to that unique permanent identity code through the mapping relationship in the system backend. This ensures the continuity of the digital identity of the component and the complete collection of traceability information, even in complex situations such as label damage or multiple replacements.

[0063] In step S2, the data bound to the digital twin includes both structured and unstructured data, specifically:

[0064] Structured data should include at least: component production batch, material supplier information, key process parameters, inspection results, logistics trajectory coordinates, arrival time, installation location coordinates, and acceptance personnel;

[0065] Unstructured data includes at least: video recordings of key production stations, scanned copies of factory certificates of conformity, images captured during transportation of abnormal conditions, on-site acceptance photos, video clips of the installation process, and video recordings of grouting construction.

[0066] In one specific embodiment of the present invention, the dynamic association and binding of step data and digital twins are achieved through a standardized data acquisition and association protocol. When a component experiences any preset state event, the operator or automated equipment responsible for that step will trigger the corresponding data acquisition process based on the event type. For example, in the production sub-event of "rebar cage placement," the system not only automatically retrieves structured rebar specifications, supplier batch numbers, and binding torques from the MES manufacturing execution system, but also automatically captures and saves image records of key parts of the component through industrial cameras deployed above the workstation. All data is automatically appended with the same timestamp and a permanent component identification code.

[0067] For logistics and transportation events, the system integrates IoT terminals on transport vehicles to periodically acquire and record structured data of logistics trajectory coordinates, including latitude, longitude, speed, and altitude, such as every 5 minutes. Simultaneously, when the onboard gyroscope detects abnormal vibration or tilt, it automatically triggers the onboard camera to capture unstructured images of the component's real-time status inside the vehicle. When a component arrives at the site and triggers an "entry acceptance" event, the on-site quality inspector scans the component's code using a mobile app. The system interface then guides them to fill in the acceptance results, select the responsible person for acceptance (structured data), and mandates that unstructured photos of the component's appearance be taken from multiple specified angles for inspection (unstructured data).

[0068] All the heterogeneous data collected at the time of the event is doubly associated with the event serial number and the permanent identification code of the component, and stored and indexed in the backend database as a data packet for the event record. The digital twin engine then dynamically loads and binds these data packets to the 3D model of the corresponding component by calling standard APIs. During visualization and tracing, users can click on a specific event node on the model to view all related data of that event in an integrated view. For example, when viewing the "Installation" event, the left-hand list displays structured information such as the installation location coordinates and the responsible person, while the right-hand window simultaneously plays video clips of the installation process, achieving deep integration and unified presentation of data in the spatiotemporal dimensions.

[0069] The specific implementation methods of the chained state transitions in step S3 include:

[0070] The system pre-sets standardized operating procedures and templates for the data fields that must be uploaded for each type of status event;

[0071] When an operator attempts to confirm a status event via a mobile terminal, the terminal application guides them to complete standardized operations such as taking a photo, filling out a form, and selecting options, and automatically attaches the operation time, geographical location, and operator information;

[0072] Only after all the necessary data for the current event has been collected and submitted will the system mark the event as "complete" and automatically trigger the transition of the overall state of the component to the next preset state.

[0073] In one specific embodiment of the invention, chained state transitions are implemented through a business engine with mandatory logical constraints. The system predefines a unique standardized electronic form for each state event, such as "Concrete Curing Completed," "Factory Release," and "On-site Acceptance Passed," which clearly lists the required operations and data fields to be collected. For example, the form template for the "Factory Release" event mandates: filling in the structured fields of the vehicle license plate number and planned shipment time; uploading unstructured data of a photo showing the components loaded onto the vehicle alongside the license plate; and electronic signature confirmation by the quality control supervisor.

[0074] Once a component has completed "production inspection" and is in the "in-warehouse" state, the warehouse manager can use a mobile terminal to scan the component code and initiate the "release from factory" event. The terminal application will guide the user through the above form requirements. When the system backend receives the submission request, it first calls the chained verification submodule to check if the component's current status is "in-warehouse". If the verification passes, the data is received and temporarily stored; if the verification fails, for example, if the component status is still "in production", the request is immediately rejected, and the terminal interface displays the message "Operation failed: This component has not completed production inspection and cannot be released from factory".

[0075] Only after all required fields in the event form, including the automatically appended operation time, GPS location, and operator ID, are submitted completely and verified by the system, will the business engine officially mark the "Factory Release" event as "Completed." Immediately, the engine automatically updates the component's global status to "Out of Factory" and unlocks the next operable event, such as "In Transit." The status change record generated during this process, along with the complete data packet, is immediately packaged and encrypted, forming an undeletable and sequentially ordered node in the traceability data chain. This technically eliminates the possibility of process reversal or data retroactive addition, ensuring the authenticity and rigor of the entire process.

[0076] Step S4, visual traceability and decision support, further includes:

[0077] Reverse tracing function: When a quality defect is discovered, the system can automatically locate all other components in the same production batch, raw material batch or process route by inputting the defective component information, and display their current status and location, so as to achieve rapid containment and recall.

[0078] Positive early warning function: Based on historical data models, it monitors key parameters of components in production, in transit, and awaiting installation in real time. If the parameters deviate from the preset threshold or an abnormal pattern occurs, it proactively pushes early warning information to the preset responsible persons. The early warning information includes supplier quality fluctuation warnings, transportation time delay warnings, and installation progress lag warnings.

[0079] In one specific embodiment of the present invention, the visualization traceability and decision support functions are implemented through the system's intelligent analysis submodule. This submodule incorporates two core engines: reverse traceability and forward early warning.

[0080] The reverse traceability function works as follows: When a quality inspector records a defect in a component on a mobile terminal, the event automatically triggers a reverse traceability query. The system first uses the defective component's permanent identification code as an index to extract all its original production data with a single click. Then, based on the association rules configured in the backend (e.g., the same production line, same batch of concrete, same day of curing kiln operation), it automatically retrieves all matching "related components" from the global database. For example, another 23 composite slabs produced in the same batch. After the retrieval, the system immediately highlights the real-time location of all related components on the global 3D map in the project management dashboard with a bright color such as red—the status and specific coordinates of components awaiting shipment from the factory, already in transit, already arrived at the project yard, and even already installed are clearly displayed. Simultaneously, the system automatically generates an "Emergency Handling List of Defective Components from the Same Batch," listing the current location of each component, the responsible person, and recommended actions such as "suspend shipment" or "on-site re-inspection." This list is then pushed to the production manager, logistics dispatcher, and project manager with a single click through the message center, achieving precise containment and risk control within minutes.

[0081] The positive early warning function relies on a configurable early warning rule engine and a real-time data pipeline. Administrators can pre-set complex monitoring rules in the engine, such as: "Rule A: If a supplier's 'first-pass acceptance rate' is below 95% for three consecutive batches of components, trigger a 'supplier quality fluctuation early warning'"; "Rule B: If a component in the 'shipped out' state fails to update to 'arrived' within the preset transportation time limit (e.g., 72 hours), trigger a 'transportation time delay early warning'." The system's backend real-time computing service continuously monitors the status event stream and key indicators of all components. Once the real-time data of a batch of components triggers Rule A, the intelligent analysis submodule immediately performs the following actions: automatically aggregates and analyzes all relevant recent quality data of the supplier, generating a root cause analysis chart; pushes the early warning information, including the component list, data trend chart, and recommended measures, to the purchasing manager and quality director via system in-app messages, emails, and SMS according to a preset contact list; and automatically changes the supplier's status light to "yellow warning" on the supply chain management dashboard. This proactive, data-driven insight allows management teams to intervene before problems escalate, ensuring project quality and schedule from the root.

[0082] Furthermore, based on the same inventive concept as the above method, this solution proposes a full-process traceability management system for prefabricated building components, including:

[0083] The identification management module is used to generate, assign, and manage the permanent identification code and temporary carrier code for each prefabricated building component, and maintain the mapping relationship between the two.

[0084] The digital twin engine module is responsible for the creation, storage, rendering and management of lightweight 3D models of components, and provides application programming interfaces for other modules to perform model and data binding operations.

[0085] The event flow-driven module is used to define the standard state event sequence for the entire lifecycle of a component, receive event data from various acquisition terminals, execute chained state verification and migration logic, and drive business processes.

[0086] The data aggregation and visualization module receives data from the event flow-driven module, integrates and associates it with the digital twins of the corresponding components, and provides interactive traceability queries and decision-making information displays in various forms such as 3D scenes, charts, and lists through web terminals, mobile terminals, or large-screen terminals.

[0087] Specifically, the system also includes intelligent data acquisition terminals deployed in different physical scenarios, including but not limited to:

[0088] Factory production data acquisition terminals are integrated into key workstations on the production line to automatically collect or have workers input production and inspection data.

[0089] Mobile handheld terminals are used by logistics personnel, on-site construction and supervision personnel to perform operations such as scanning codes, taking photos, filling out forms and confirming status events.

[0090] The Internet of Things (IoT) sensing terminals include GPS / BeiDou positioning units and attitude sensors integrated on transport vehicles, as well as monitoring equipment deployed on yards and tower cranes, for automatically collecting the location, environment, and image information of components.

[0091] The event flow-driven module contains a chained verification submodule, which is configured as follows:

[0092] Maintain a global component state mapping table to record the current state event nodes of each component in real time;

[0093] Whenever a new status event submission request is received, the current status of the component is queried and compared with the previous status required by the target event;

[0094] New event data will only be allowed to be submitted and the state mapping table updated if the comparison is consistent; otherwise, the request will be rejected and an error message will be returned, indicating the required prerequisite state.

[0095] The data aggregation and visualization module embeds an intelligent analysis submodule, which is configured as follows:

[0096] Run the preset data analysis model to periodically mine the traceability data of the entire platform and generate multi-dimensional statistical analysis reports, including supplier performance evaluation reports, project schedule deviation reports, and common quality defect distribution reports;

[0097] It provides a configurable alert rule engine, allowing administrators to set alert rules based on data thresholds, trends, or logical combinations. When real-time data triggers a rule, an alert notification is automatically sent to a specified user or user group via a message queue.

[0098] The system's operation begins in the design and production phase. Once the component design model is finalized, the digital twin engine module automatically converts it into a lightweight 3D model and stores it. Simultaneously, the identification management module generates a globally unique permanent identification code for the component, such as through chip embedding or stamping, linking it to a temporary carrier code (e.g., a QR code), and establishes a mapping between the two in the background. Within the factory, factory production data acquisition terminals, such as workstation tablets, sensors, and event-driven modules work collaboratively: workers scan temporary codes at key processes, and the module guides them to complete standardized data entry, such as rebar specifications and concrete pouring data, automatically binding relevant image records to the component's digital twin. When the component completes production inspection and is ready for shipment, the operator initiates a "shipment" event via a mobile handheld terminal. The chain verification submodule verifies whether all preceding production events, such as "curing completed" and "quality inspection passed," have been closed-loop. Only after successful verification does the system allow submission and update the component's status to "shipped," synchronizing the data to the cloud.

[0099] During the logistics and construction phase, the system's IoT sensing terminals, including vehicle-mounted GPS and sensors, automatically collect transportation trajectory and vehicle attitude data, uploading and binding them in real time to the component's digital twin. Upon arrival at the site, acceptance personnel use mobile terminals to scan a temporary code for "entry acceptance." At this point, the event flow-driven module re-verifies the "factory-delivered" status and guides the completion of the acceptance process. After acceptance, the temporary code can be replaced with a "site installation code" containing installation location information. Subsequent events such as "hoisting" and "grouting" follow this chain-like verification and data binding logic, ensuring that each operation is based on a preceding valid state, thus constructing an irreversible traceability data chain.

[0100] All aggregated data is processed by the data aggregation and visualization module. This module deeply integrates end-to-end data with 3D models, allowing users to intuitively view the entire lifecycle of any component by clicking on it in the 3D scene via web or mobile devices. The embedded intelligent analysis submodule runs continuously, supporting both "reverse tracing" (inputting a quality issue instantly locates the position and status of all components in the same batch) and "positive early warning" (based on preset rules such as transportation delays or declining acceptance rates, pushing real-time alerts to responsible personnel), thus achieving a shift from passive recording to proactive decision-making and ultimately realizing the goal of refined end-to-end management with controllable quality, transparent processes, and intelligent decision-making.

[0101] In summary, the advantages of this invention are: by constructing a hybrid identification system, it effectively solves the problems of traditional single identification being easily damaged and having limited information carrying capacity during the complex circulation of components, thus ensuring the full life-cycle effectiveness and information capacity of traceability identification.

[0102] The foregoing has shown and described the basic principles, main features, and advantages of the present invention. Those skilled in the art should understand that the present invention is not limited to the above embodiments. The embodiments and descriptions in the specification are merely principles of the invention. Various changes and modifications can be made to the invention without departing from its spirit and scope, and all such changes and modifications fall within the scope of the claimed invention. The scope of protection claimed by the appended claims and their equivalents is defined.

Claims

1. A method for full-process traceability management of prefabricated building components, characterized in that, include: S1. Component Identification and Model Initialization: Assign a unique and unchangeable permanent identification code to each prefabricated building component and generate a lightweight three-dimensional digital model corresponding to the component, which together form the basis of the component's digital twin. S2. Full-process event definition and data binding: The life cycle of a component is divided into a series of preset state events, including production, storage, transportation, arrival, installation and acceptance events; when each state event occurs, the business data and process data of the event are acquired through the acquisition terminal, and the data is dynamically associated and bound with the digital twin of the component. S3. Event-driven chained state transition: The state of a component is sequentially transitioned based on the completion of the previous state event. When a new state event operation is initiated for a component, the system must verify that the previous state event has been confirmed as completed. Only after the verification is passed can the current event operation be executed and the overall state of the component be updated, forming an irreversible traceable data chain. S4. Visualized Traceability and Decision-Making Based on Digital Twins: Provides a unified traceability query interface. Users can scan the component entity identifier or select the component model in the 3D visualization scene. The system will then integrate and display the full-process historical data bound to the digital twin of the component, and generate quality analysis reports and risk warning information based on the aggregated data.

2. The method for full-process traceability management of prefabricated building components according to claim 1, characterized in that, In step S1, the assigned identifier system is a hybrid identifier system, specifically including: Assign a permanent identification code to a component, either engraved or embedded in the component entity, and this code remains unchanged throughout its entire lifespan; Simultaneously, one or more temporary carrier codes that can be dynamically attached or replaced are assigned to the component, and the temporary carrier codes are carried on QR code tags, RFID tags or accompanying documents; The permanent identification code and the temporary carrier code are associated and mapped in the system background, so that all traceability information indexed by the permanent identification code can be indirectly accessed and manipulated by scanning the temporary carrier code.

3. The method for full-process traceability management of prefabricated building components according to claim 2, characterized in that, The attachment, replacement, and information updating of the temporary carrier code follow these rules: The temporary carrier code is generated and associated for the first time when the component rolls off the production line, and is used for circulation within the factory and tracking of outbound logistics. Once the components are transported to the construction site and pass the acceptance inspection, they can be replaced with on-site installation codes that include information on the project, building, floor, and unit location. Each carrier code replacement operation is recorded as an independent status event and stored in the component's traceability data chain along with snapshots of the component's status before and after the replacement.

4. The method for full-process traceability management of prefabricated building components according to claim 3, characterized in that, In step S2, the data bound to the digital twin includes structured data and unstructured data, specifically: Structured data should include at least: component production batch, material supplier information, key process parameters, inspection results, logistics trajectory coordinates, arrival time, installation location coordinates, and acceptance personnel; Unstructured data includes at least: video recordings of key production stations, scanned copies of factory certificates of conformity, images captured during transportation of abnormal conditions, on-site acceptance photos, video clips of the installation process, and video recordings of grouting construction.

5. The method for full-process traceability management of prefabricated building components according to claim 4, characterized in that, The specific implementation methods of the chained state transition in step S3 include: The system pre-sets standardized operating procedures and templates for the data fields that must be uploaded for each type of status event; When an operator attempts to confirm a status event via a mobile terminal, the terminal application guides them to complete standardized operations such as taking a photo, filling out a form, and selecting options, and automatically attaches the operation time, geographical location, and operator information; Only after all the necessary data for the current event has been collected and submitted will the system mark the event as "complete" and automatically trigger the transition of the overall state of the component to the next preset state.

6. The method for full-process traceability management of prefabricated building components according to claim 5, characterized in that, The visual traceability and decision support in step S4 further includes: Reverse tracing function: When a quality defect is discovered, the system can automatically locate all other components in the same production batch, raw material batch or process route by inputting the defective component information, and display their current status and location, so as to achieve rapid containment and recall. Positive early warning function: Based on historical data models, it monitors key parameters of components under construction, in transit, and awaiting installation in real time. If the parameters deviate from the preset threshold or an abnormal pattern occurs, it proactively pushes early warning information to the preset responsible persons. The early warning information includes supplier quality fluctuation warnings, transportation time delay warnings, and installation progress lag warnings.

7. A full-process traceability management system for prefabricated building components, characterized in that, The method for implementing the end-to-end traceability management of prefabricated building components as described in any one of claims 1-6 includes: The identification management module is used to generate, assign, and manage the permanent identification code and temporary carrier code for each prefabricated building component, and maintain the mapping relationship between the two. The digital twin engine module is responsible for the creation, storage, rendering and management of lightweight 3D models of components, and provides application programming interfaces for other modules to perform model and data binding operations. The event flow-driven module is used to define the standard state event sequence for the entire lifecycle of a component, receive event data from various acquisition terminals, execute chained state verification and migration logic, and drive business processes. The data aggregation and visualization module receives data from the event flow-driven module, integrates and associates it with the digital twins of the corresponding components, and provides interactive traceability queries and decision-making information displays in various forms such as 3D scenes, charts, and lists through web terminals, mobile terminals, or large-screen terminals.

8. A full-process traceability management system for prefabricated building components according to claim 7, characterized in that, It also includes intelligent data acquisition terminals deployed in different physical scenarios, including but not limited to: Factory production data acquisition terminals are integrated into key workstations on the production line to automatically collect or have workers input production and inspection data. Mobile handheld terminals are used by logistics personnel, on-site construction and supervision personnel to perform operations such as scanning codes, taking photos, filling out forms and confirming status events. The Internet of Things (IoT) sensing terminals include GPS / BeiDou positioning units and attitude sensors integrated on transport vehicles, as well as monitoring equipment deployed on yards and tower cranes, for automatically collecting the location, environment, and image information of components.

9. A full-process traceability management system for prefabricated building components according to claim 7, characterized in that, The event flow driving module contains a chained verification submodule, which is configured as follows: Maintain a global component state mapping table to record the current state event nodes of each component in real time; Whenever a new status event submission request is received, the current status of the component is queried and compared with the previous status required by the target event; New event data will only be allowed to be submitted and the state mapping table updated if the comparison is consistent; otherwise, the request will be rejected and an error message will be returned, indicating the required prerequisite state.

10. A full-process traceability management system for prefabricated building components according to claim 7, characterized in that, The data aggregation and visualization module embeds an intelligent analysis submodule, which is configured as follows: Run the preset data analysis model to periodically mine the traceability data of the entire platform and generate multi-dimensional statistical analysis reports, including supplier performance evaluation reports, project schedule deviation reports, and common quality defect distribution reports; It provides a configurable alert rule engine, allowing administrators to set alert rules based on data thresholds, trends, or logical combinations. When real-time data triggers a rule, an alert notification is automatically sent to a specified user or user group via a message queue.

Images