Building full life cycle monitoring management system and method

Abstract

The invention discloses a building full life cycle monitoring management system and method, and relates to the technical field of engineering management, and the method comprises the steps: constructing a digital thread topology, building an object passport and an object identifier, and forming a digital thread topology table; when a business document is formed in an engineering business link, uniformly packaging a thread event shell and associating the digital thread topology table to form a thread event flow, and updating object passport information at the same time; and according to the thread event flow, maintaining a full-cycle state record table compiled according to the object identifier, and executing permission check and precondition check to generate an instruction list and a gap exception list. According to the method, the full-cycle state record table is generated through the thread event flow, the ready item field and the event track field are compared and verified, the instruction list or the gap exception list is formed in combination with permission verification and precondition verification, and the certainty and interpretability of process propulsion are achieved.

Description

Technical Field

[0001] This invention relates to the field of engineering management technology, and in particular to a building life cycle monitoring and management system and method. Background Technology

[0002] Building lifecycle monitoring and management technologies typically revolve around the digitization and traceability of engineering business processes. Common practices include establishing a division of responsibilities based on project participants and job roles, using processes such as procurement ordering, goods receipt and warehousing, requisition and inspection, measurement and settlement, acceptance and handover, and operation and maintenance work orders to carry out the flow of business documents, and using business data such as component identification, equipment identification, work package code, contract and change number to support cross-stage information association, while using evidence document indexing and summary methods to achieve evidence retention and audit support for business documents.

[0003] Existing technologies are still prone to link breaks and inconsistencies in the unified association across processes, subjects, and data: the lack of a unified mapping between business documents and object identifiers makes it difficult to aggregate event trajectories by object; process triggering permissions and data submission preconditions rely heavily on manual verification, making it difficult to form deterministic constraints; the lack of topological constraints to support the association between evidence pointers and business documents' index summary leads to unstable tracing results, which in turn affects the continuity and integrity of the entire lifecycle status record. Summary of the Invention

[0004] In view of the aforementioned existing problems, the present invention is proposed.

[0005] Therefore, this invention provides a building lifecycle monitoring and management method to solve the problem that business documents across responsible entities and business processes are difficult to trace continuously and verify deterministically by object identifier.

[0006] To solve the above-mentioned technical problems, the present invention provides the following technical solution:

[0007] In a first aspect, the present invention provides a method for monitoring and managing the entire life cycle of a building, which includes constructing a digital thread topology and establishing object passports and object identifiers to form a digital thread topology table;

[0008] When business documents are generated in the engineering business process, the thread event shell is uniformly encapsulated and associated with the digital thread topology table to form a thread event stream, while updating the object passport information.

[0009] Based on the thread event flow, maintain a full-cycle status record table compiled by object identifier, and perform permission verification and precondition verification to generate instruction orders and gap exception orders;

[0010] Based on the instruction sheet, execute business orchestration and generate management tasks; based on the gap and anomaly sheet, locate the topological break relationship and initiate a completion request; generate execution result thread events and synchronously update the full-cycle status record table.

[0011] As a preferred embodiment of the building lifecycle monitoring and management method described in this invention, the specific steps for constructing the digital thread topology are as follows:

[0012] Register project participants and their roles, and generate responsible entity nodes and their identifiers;

[0013] Configure the engineering business process set and generate business process nodes and process node identifiers;

[0014] Configure the business dataset to merge and generate business data nodes and business data node identifiers;

[0015] Extract component identifiers, equipment identifiers, and work package codes from the business data set, and generate object identifiers according to unified coding rules;

[0016] The object identifier is registered as an object passport entry and bound to the responsible entity node identifier and job role to form a digital thread topology.

[0017] As a preferred embodiment of the building life cycle monitoring and management method described in this invention, the digital thread topology table is obtained by summarizing the allowed triggering relationship between the responsible entity node and the business process node, the required submission relationship between the business process node and the business data node, and the attribution relationship between the business data node and the object identifier.

[0018] As a preferred embodiment of the building lifecycle monitoring and management method described in this invention, the following steps are taken when business documents are generated during the engineering business process: a unified thread event shell is encapsulated and associated with a digital thread topology table to form a thread event stream, while simultaneously updating the object passport information.

[0019] The execution elements of the business document are parsed to generate a thread event shell. Evidence pointers are generated for the business document and an index summary association is established. The thread event shell is associated with the execution consistency of the digital thread topology table to form a thread event flow.

[0020] Write the business document identifier, process node identifier, responsible entity node identifier, and evidence pointer corresponding to the object identifier in the thread event stream into the object passport to form the object passport update result.

[0021] As a preferred embodiment of the building life cycle monitoring and management method of the present invention, the full life cycle status record table is formed by aggregating thread event streams according to object identifiers.

[0022] As a preferred embodiment of the building lifecycle monitoring and management method described in this invention, the specific steps for maintaining a lifecycle status record table compiled according to object identifiers based on thread event flow are as follows:

[0023] Register the request to submit the relationship as the ready item field, register the object passport mapping information as the object index field, and register the thread event stream aggregation information as the event trajectory field;

[0024] Perform a comparison and verification between the ready items field and the event trajectory field, and update the items to be satisfied and the items that have been satisfied.

[0025] Perform a consistency check between the object index field and the thread event stream object identifier, output the object association consistency result and write it to the full life cycle status record table.

[0026] As a preferred embodiment of the building lifecycle monitoring and management method described in this invention, the specific steps for the execution permission verification and precondition verification are as follows:

[0027] Extract the latest thread event shell from the thread event stream, and parse the responsible entity node identifier, job role, and process node identifier to form the permission verification elements;

[0028] The permission verification elements are matched with the allowed triggering relationships to obtain the permission verification results;

[0029] The process node identifier is used to retrieve the required submission relationship, and the results of the consistency between the ready item field, event trajectory field and object association are combined to generate a list of prerequisite conditions;

[0030] Verify the list of preconditions with the event trajectory field to obtain the precondition verification results;

[0031] The system combines the results of permission verification, object association consistency verification, and precondition verification to make a combined judgment. An instruction form is generated when all three are satisfied, and a gap exception form is generated when any one of them is not satisfied.

[0032] As a preferred embodiment of the building lifecycle monitoring and management method described in this invention, the specific steps for executing business orchestration and generating management tasks based on instruction sheets are as follows:

[0033] Analyze the next process node identifier, responsible entity node identifier, and job role in the instruction sheet to determine the corresponding engineering business process;

[0034] The next process node identifier is mapped to the engineering business link as an execution action, a management task is generated, and the task acceptance status and completion status are recorded to form a task status record.

[0035] As a preferred embodiment of the building lifecycle monitoring and management method described in this invention, the specific steps for initiating a completion request based on the single-location topological fracture relationship of the gap anomaly are as follows:

[0036] Analyze the missing data exception order to obtain the corresponding process node identifier and the missing data node identifier;

[0037] Submit the relationship according to the corresponding process node identifier search requirements, and locate the associated responsible entity node identifier according to the allowed triggering relationship to form the topological break relationship location result;

[0038] Combine the topological fracture relationship location results with the object passport binding information to generate a completion request and assign it to the corresponding job role.

[0039] Retrieve the management task identifier corresponding to the object identifier and process node identifier from the task status record, and write it into the completion request;

[0040] The request acceptance information and business document identifier are encapsulated into an execution result thread event shell and written into the thread event stream. At the same time, they are registered in the full-cycle status record table and the results of unmet items, met items and object association are updated.

[0041] Secondly, the present invention provides a building life cycle monitoring and management system, including a digital topology module, which constructs a digital thread topology and establishes object passports and object identifiers to form a digital thread topology table;

[0042] The event encapsulation module encapsulates thread events into shells and associates them with a digital thread topology table when business documents are generated in the engineering business process, forming a thread event stream and updating the object passport information at the same time.

[0043] The status verification module maintains a full-cycle status record table compiled by object identifier based on the thread event flow, and performs permission verification and precondition verification to generate instruction sheets and gap exception sheets.

[0044] The task completion module executes business orchestration and generates management tasks based on the instruction sheet, locates the topological break relationship based on the gap and anomaly sheet and initiates a completion request, forms an execution result thread event and synchronously updates the full-cycle status record table.

[0045] The beneficial effects of this invention are as follows: A digital thread topology is constructed using responsible entity nodes, business process nodes, and business data nodes. A digital thread topology table is formed by summarizing allowed trigger relationships, required submission relationships, and attribution relationships, ensuring that process triggering and data submission constraints have an enumerable topological basis. In the engineering business process, the execution elements of business documents are parsed and encapsulated into thread event shells. Evidence is verified and retained through the index digest association of evidence pointers. Simultaneously, consistent associations are executed using the digital thread topology table to form thread event flows and update object passports, ensuring that event trajectories can be aggregated by object identifiers. A full-cycle status record table is generated based on the thread event flow, and the ready item fields are compared and verified with the event trajectory fields. Combined with permission checks and precondition checks, instruction orders or gap / abnormality orders are formed, achieving certainty and interpretability in process advancement. Instruction orders drive management tasks, and gap / abnormality orders drive completion requests and write back execution results thread events, ensuring continuous synchronous updates to the full-cycle status record table, thereby improving cross-stage information coherence, compliance auditability, and anomaly location efficiency. Attached Figure Description

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

[0047] Figure 1 A flowchart for the building lifecycle monitoring and management method.

[0048] Figure 2 A flowchart for digital thread topology construction and event encapsulation.

[0049] Figure 3 A flowchart for the decision-making process of status record maintenance and verification.

[0050] Figure 4 This is a flowchart for task execution and closed-loop management. Detailed Implementation

[0051] To make the above-mentioned objects, features and advantages of the present invention more apparent and understandable, the specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings.

[0052] Many specific details are set forth in the following description in order to provide a full understanding of the invention. However, the invention may also be practiced in other ways different from those described herein, and those skilled in the art can make similar extensions without departing from the spirit of the invention. Therefore, the invention is not limited to the specific embodiments disclosed below.

[0053] Secondly, the term "one embodiment" or "embodiment" as used herein refers to a specific feature, structure, or characteristic that may be included in at least one implementation of the present invention. The phrase "in one embodiment" appearing in different places in this specification does not necessarily refer to the same embodiment, nor is it a single or selective embodiment that is mutually exclusive with other embodiments.

[0054] Reference Figures 1-4 As one embodiment of the present invention, this embodiment provides a method for monitoring and managing the entire life cycle of a building, including the following steps:

[0055] S1. Construct a digital thread topology and establish object passports and object identifiers to form a digital thread topology table.

[0056] S1.1. Collect the main information of the construction unit, design unit, general contractor, subcontractor, supervisor, supplier, and operation and maintenance service provider on a project basis, and register the corresponding job role list under each main information; generate a responsible main entity node for each project participant based on the main information and job role list, and assign a unique responsible main entity node identifier to each responsible main entity node.

[0057] Based on the job roles registered in the list of responsible entities, configure a set of engineering business processes covering purchase ordering, goods receipt and warehousing, requisition and inspection, measurement and settlement, acceptance and handover, and operation and maintenance work orders; define each engineering business process in the set of engineering business processes as a business process node, and assign a unique process node identifier to each business process node.

[0058] Based on the business record requirements of each engineering business process in the business process node list, configure a business data set covering component identifiers, equipment identifiers, work package codes, contract and change numbers, business document identifiers, and maintenance work order identifiers; define each business data in the business data set as a business data node, and assign a unique business data node identifier to each business data node.

[0059] S1.2. Locate the business data node identifiers corresponding to component identifiers, equipment identifiers, and work package codes in the business data node list, and perform consistency merging on records that appear in different engineering business processes for the same component identifier or the same equipment identifier; combine and encode the component identifier, equipment identifier, and work package code according to the unified coding rules to generate object identifiers that correspond one-to-one with the component identifier or equipment identifier, as well as a correspondence table between object identifiers, component identifiers, equipment identifiers, and work package codes.

[0060] To further explain, consistency merging refers to performing format normalization processing on component identifiers and equipment identifiers. Format normalization processing includes removing spaces and delimiters, unifying uppercase and lowercase rules, unifying leading zero rules, and unifying coding prefix rules. Business data records are grouped using component identifiers or equipment identifiers as primary keys, and an association list is generated using work package codes as association keys within the groups. Multiple records corresponding to the same component identifier or the same equipment identifier and the same work package code in the association list are merged and registered, and the corresponding process node identifier set is retained.

[0061] Combined coding refers to separately counting the maximum number of digits for the work package code, the component identifier, and the device identifier in the business data set. The maximum number of digits for the work package code is determined as the work package code segment length, the maximum number of digits for the component identifier is determined as the component identifier segment length, and the maximum number of digits for the device identifier is determined as the device identifier segment length. Then, fixed-length processing is performed on the work package code, component identifier, and device identifier respectively. Fixed-length processing includes truncating to the right when the number of digits exceeds the corresponding code length and padding with zeros on the left when the number of digits is less than the corresponding code length. The object identifier is generated by concatenating the work package code segment, component identifier segment, and device identifier segment in the order of the work package code segment, component identifier segment, and device identifier segment.

[0062] When a component identifier exists and a device identifier is empty, the device identifier segment is written into a zero-padding segment with the same code length as the device identifier segment. When a device identifier exists and a component identifier is empty, the component identifier segment is written into a zero-padding segment with the same code length as the component identifier segment. The zero-padding segment consists of all zeros of the corresponding code length and is confirmed to be a non-existent value in the business data set through deduplication comparison. The zero-padding segment is a reserved value of the unified coding rule. Combining the object identifier and the associated list, a correspondence table of object identifier, component identifier, device identifier, and work package code is obtained.

[0063] Based on the object identifier and correspondence table, an object passport entry is created for each object identifier, and the correspondence between the object identifier, component identifier, equipment identifier, and work package code is registered in the object passport entry; based on the list of responsible entity nodes, the responsible entity node identifier and job role corresponding to the object identifier are bound in the object passport entry to form a digital thread topology.

[0064] In the digital thread topology, establish the allowed triggering relationship between the responsible entity node and the business process node, specifically as follows:

[0065] Extract the responsible entity node identifier and job role one by one from the list of responsible entity nodes; extract the process node identifier one by one from the list of business process nodes and determine the engineering business process corresponding to the process node identifier; configure a list of allowed triggering job roles for each process node identifier, which consists of the set of initiator job roles corresponding to the engineering business process; pair the responsible entity node identifier with the process node identifier, and when the job role corresponding to the responsible entity node identifier belongs to the list of allowed triggering job roles, register an allowed triggering relationship record item, which includes the responsible entity node identifier, the process node identifier, and the allowed triggering job role.

[0066] Establish the submission relationship between business process nodes and business data nodes, specifically as follows:

[0067] Extract business data node identifiers one by one from the business data node list and determine the business data corresponding to each business data node identifier; configure a set of required business data node identifiers for each process node identifier. The set of required business data node identifiers consists of business data node identifiers corresponding to at least one of the following: business document identifier, component identifier, equipment identifier, work package code, contract and change number, and maintenance work order identifier corresponding to the engineering business process; pair the process node identifiers with the set of required business data node identifiers one by one and register the required submission relationship record item. The required submission relationship record item includes the process node identifier, the business data node identifier, and the required submission type identifier. The required submission type identifier is used to indicate the submission requirement of the business data node identifier in the engineering business process corresponding to the process node identifier.

[0068] Establish the attribution relationship between business data nodes and object identifiers, specifically as follows:

[0069] Extract the business data node identifiers corresponding to the object identifier, component identifier, equipment identifier, and work package code from the correspondence table. Record the business data node identifiers corresponding to the object identifier, component identifier, equipment identifier, and work package code as one attribution relationship record, and record the business data node identifiers corresponding to the object identifier and work package code as one attribution relationship record. The attribution relationship record contains the business data node identifier, object identifier, and attribution type identifier. The attribution type identifier is used to indicate whether the corresponding source of the business data node identifier and object identifier is the component identifier, equipment identifier, or work package code.

[0070] The records that allow triggering relationships, require submission of relationships, and belong to relationships are merged and registered according to relationship type, and a relationship record identifier is uniformly configured for each record to form a digital thread topology table.

[0071] S2. When business documents are generated in the engineering business process, the thread event shell is uniformly encapsulated and associated with the digital thread topology table to form a thread event stream, while updating the object passport information.

[0072] S2.1. Locate the business process node corresponding to the business document in the business process node list and obtain the process node identifier. Locate the component identifier, equipment identifier, and work package code involved in the business document in the business data node list and obtain the object identifier. Locate the initiator role and recipient role of the business document in the responsible entity node list and obtain the responsible entity node identifier. Organize the object identifier, business document identifier, process node identifier, responsible entity node identifier, initiator role, and recipient role into a thread event shell field set.

[0073] For each evidence file in the on-site evidence materials, register the evidence file storage location identifier, and perform a message digest algorithm on the content of the evidence file to obtain a digest value, forming an evidence pointer and establishing an index digest association with the evidence file storage location identifier; write the evidence pointer into the thread event shell to obtain a thread event shell carrying the evidence pointer.

[0074] The expression for obtaining the digest value by performing a message digest algorithm on the content of the evidence document is as follows:

[0075] ;

[0076] ;

[0077] in, This indicates the contents of the evidence document; Represents a message digest algorithm; Indicates the summary value; Indicates a pointer to evidence; This indicates the location where the evidence file is stored.

[0078] S2.2. Based on the allowed triggering relationship in the digital thread topology table, verify the correspondence between the responsible entity node identifier and the process node identifier; based on the required submission relationship in the digital thread topology table, verify the correspondence between the process node identifier and the business data node identifier; based on the attribution relationship in the digital thread topology table, verify the correspondence between the business data node identifier and the object identifier; register the thread event shell carrying the evidence pointer that has passed the consistent association as a thread event stream.

[0079] Locate the object passport entry corresponding to the object identifier in the object passport entry, and write the business document identifier, process node identifier, responsible entity node identifier, initiator role, recipient role, and evidence pointer from the thread event stream into the object passport entry to obtain the object passport update result.

[0080] S3. Based on the thread event flow, maintain a full-cycle status record table compiled by object identifier, and perform permission verification and precondition verification to generate instruction sheets and gap exception sheets.

[0081] S3.1. Extract the object identifier list from the object passport entry set; locate the thread event flow record item set corresponding to each object identifier in the object identifier list, and organize the thread event flow record item set into the event trajectory field; summarize the submission relationship according to the process node identifier in the digital thread topology table and organize it into the ready item field; extract the correspondence between object identifier and component identifier, equipment identifier, work package code, contract and change number from the object passport entries and organize it into the object index field; write the ready item field, object index field and event trajectory field into the full life cycle status record table corresponding to the object identifier to obtain the initial record item set of the full life cycle status record table.

[0082] S3.2. Locate the ready item field and event trajectory field corresponding to the object identifier in the initial record item set of the full cycle status record table one by one, and filter the required submission relationship in the digital thread topology table with the process node identifier as the search condition. The required submission relationship meets the condition that the process node identifier is the same and the relationship type is required submission relationship. Extract the business data node identifier from the required submission relationship and summarize it to obtain the set of required submission business data node identifiers.

[0083] Extract the business data node identifiers from the event trajectory field and remove duplicates to obtain the set of business data node identifiers that have appeared; perform a set comparison between the set of business data node identifiers to be submitted and the set of business data node identifiers that have appeared. The set comparison includes calculating the intersection of the sets to obtain the satisfied items and calculating the difference of the sets to obtain the unsatisfied items, and write the satisfied items and unsatisfied items into the full-cycle status record table.

[0084] Extract the object identifier from the object index field and extract the object identifier from the thread event stream record item set corresponding to the event trajectory field. Perform a consistency check based on whether all object identifiers are consistent. If the consistency check satisfies that the object identifier in the object index field and the object identifier in the thread event stream record item set are equal one by one, output the object association consistency result as consistent. If any are not equal, output the object association consistency result as inconsistent. Write the object association consistency result to the full-cycle state record table to obtain the updated full-cycle state record table.

[0085] It should be noted that by comparing the intersection / difference of the set between the required submission relationship defined by the digital thread topology table and the event trajectory field obtained by the aggregation of thread event streams, satisfied / unsatisfied items are generated in a deterministic manner. Furthermore, the object association consistency result is output by the full consistency check of the object index field—the set of thread event stream record items. This enables the full-cycle status record table to simultaneously complete data integrity verification and cross-process consistency verification at the object identifier granularity, significantly reducing rework and risk diffusion caused by missing document chains, order mix-ups, and mismatched objects in business processes, and improving cross-stage traceability and status updates. The real-time nature of the solution; compared with the common practices of existing technologies (relying on decentralized business ledgers or hard-coded verification rules for each process node, manual verification of documents, and lack of unified state aggregation and consistency determination driven by object identifiers), the above solution will require the submission of relational structures into searchable topological constraints, and use set operations to achieve comparison verification and full consistency to achieve object-level closed-loop determination, forming a reusable computation link of topological constraints - event facts - state results. It has the technical effect of migration and reuse under different engineering business processes and does not rely on the stacking of empirical manual rules, reflecting the improvement of combining structured constraints and set operations.

[0086] S3.3. Locate the object identifier to be verified in the updated full-cycle status record table; filter the set of thread event shells in the thread event stream where the object identifier is equal to the object identifier to be verified, sort them in descending order by occurrence timestamp, and select the thread event shell with the largest occurrence timestamp as the latest thread event shell; read the responsible entity node identifier, initiator role, recipient role, and process node identifier by field name in the latest thread event shell to form the permission verification elements; retrieve the allowed triggering relationship in the digital thread topology table and match the permission verification elements with the allowed triggering relationship to obtain the permission verification result, represented as:

[0087] ;

[0088] in, Indicates the node identifier of the responsible entity; Indicates the process node identifier; This represents the allowed triggering relationships in the numeric thread topology table; Indicates an indicator function; This indicates the value of the permission verification result. This indicates that the permission verification result is passed. This indicates that the permission verification result is unsuccessful.

[0089] In the updated full-cycle status record table, locate the ready item field and event trajectory field corresponding to the object identifier and ensure consistency with the object association. Use the process node identifier obtained from the latest thread event shell parsing as the search condition to filter the submission requirement relationship in the digital thread topology table and extract the set of submission requirement business data node identifiers. Register each submission requirement business data node identifier as a precondition list item and verify the existence of each precondition list item in the business data node identifier set corresponding to the event trajectory field. If it exists, mark it as satisfied; if it does not exist, mark it as missing to obtain the precondition verification result.

[0090] A combined judgment is performed on the permission verification result, the object association consistency result, and the precondition verification result. When the permission verification result is passed, the precondition verification result is passed, and the object association consistency result is consistent, the next process node identifier is determined according to the arrangement order of the engineering business process set, and an instruction sheet is generated. The instruction sheet registers the next process node identifier, the responsible entity node identifier, the recipient's job role, and the required set of business data node identifiers corresponding to the next process node identifier. When the permission verification result is failed, the precondition verification result is failed, or the object association consistency result is inconsistent, a gap anomaly form is generated. The gap anomaly form registers the process node identifier, the responsible entity node identifier, the object identifier, and the set of missing business data node identifiers.

[0091] It should be noted that the latest fact source for identifying the object to be verified is the thread event shell with the largest timestamp in the thread event stream. The allowed triggering relationship and required submission relationship of the digital thread topology table are used to perform deterministic matching and item-by-item verification of the sets of responsible entity node identifiers—process node identifiers and process node identifiers—business data node identifiers, respectively. Furthermore, the permission verification results, object association consistency results, and precondition verification results are combined for judgment, automatically generating instruction orders or gap / abnormality orders. This achieves an integrated closed loop for access control, process advancement, and gap location in engineering business processes, avoiding issues caused by role overstepping boundaries. Compared to common manual approvals or simple permission controls based on static fields in business documents, and precondition verification relying on empirical rules or hard-coded processes, this approach abstracts permission constraints and data completeness constraints into a set of relationships in a digital thread topology table. Permission judgments are formally expressed using indicator functions. Then, a set of business data node identifiers driven by process node identifiers is submitted to generate a list of preconditions, which is verified in the event trajectory field. This makes permission and precondition verification reusable, auditable, traceable, and strictly aligned with the granularity of object identifiers.

[0092] S4. Execute business orchestration and generate management tasks according to the instruction sheet, locate the topological break relationship according to the gap and anomaly sheet and initiate a completion request, form an execution result thread event and synchronously update the full-cycle status record table.

[0093] S4.1. Read the object identifier, next process node identifier, responsible entity node identifier, and recipient role one by one from the instruction sheet; locate the business process node with the next process node identifier in the business process node list, and read the corresponding engineering business process to obtain the engineering business step; filter the required submission relationship record items with the next process node identifier in the digital thread topology table and extract the business data node identifier to obtain the set of required submission business data node identifiers corresponding to the next process node identifier.

[0094] The set of identifiers for object, engineering business process, next process node, responsible entity node, recipient role and required submission of business data node is registered as a management task. A unique management task identifier is assigned to each management task, and the task acceptance status and completion status are recorded. The task acceptance status is used to confirm the acceptance result of the management task corresponding to the management task identifier, and the completion status is used to confirm the completion result of the management task corresponding to the management task identifier, thus forming a task status record.

[0095] S4.2. Read the object identifier, process node identifier, set of missing business data node identifiers, and responsible entity node identifier one by one from the gap exception form; filter the required submission relationship record items by process node identifier in the digital thread topology table and extract the business data node identifier to obtain the set of required submission business data node identifiers corresponding to the process node identifier; perform an inclusion check between the set of missing business data node identifiers and the set of required submission business data node identifiers. If the inclusion check satisfies that the set of missing business data node identifiers belongs to the set of required submission business data node identifiers, it is determined that there is a missing submission in the required submission relationship corresponding to the process node identifier.

[0096] In the digital thread topology table, filter the allowed trigger relationship records by process node identifier and extract the responsible entity node identifier to obtain the set of allowed trigger responsible entity node identifiers corresponding to the process node identifier; perform a consistency check between the set of allowed trigger responsible entity node identifiers and the responsible entity node identifiers read from the gap anomaly report to obtain the associated responsible entity node identifiers; register the process node identifier, the set of missing business data node identifiers and the associated responsible entity node identifiers as the topology break relationship location results.

[0097] S4.3. Locate the object passport entry using the object identifier, and extract the responsible entity node identifier and job role registered in the object passport entry to obtain the object passport binding information; combine the topological break relationship location result with the object passport binding information to register as a completion request, and assign a unique completion request identifier to the completion request; locate the job role in the responsible entity node list using the responsible entity node identifier, determine the assigned job role corresponding to the completion request identifier, and complete the completion request assignment.

[0098] In the task status record, the task status record is filtered by the object identifier and the process node identifier, and the management task identifier is extracted; the management task identifier is written into the completion request to form a task association between the completion request and the management task identifier.

[0099] S4.4. Extract the completion request acceptance information and completion submission business document identifier from the completion request, and combine them with the object identifier, process node identifier, responsible entity node identifier and assigned job role to generate the execution result thread event shell; register the execution result thread event shell as a thread event flow record item of the thread event flow.

[0100] In the full-cycle status record table, the event trajectory field is located by object identifier, and the business document identifier and process node identifier corresponding to the execution result thread event shell are appended and registered. In the digital thread topology table, the required submission relationship record items are filtered by process node identifier, and the business data node identifier is extracted to obtain the set of required submission business data node identifiers. The business data node identifier is extracted from the event trajectory field to obtain the set of already appearing business data node identifiers. The required submission business data node identifier set and the already appearing business data node identifier set are compared and the pending and fulfilled items are updated. In the full-cycle status record table, the object identifier in the object index field and the object identifier in the thread event flow record item are checked for consistency and the object association consistency result is updated to form a synchronized updated full-cycle status record table.

[0101] This embodiment also provides a building lifecycle monitoring and management system, including:

[0102] The digital topology module constructs the digital thread topology and establishes object passports and object identifiers to form a digital thread topology table.

[0103] The event encapsulation module encapsulates thread events into shells and associates them with a digital thread topology table when business documents are generated in the engineering business process, forming a thread event stream and updating the object passport information at the same time.

[0104] The status verification module maintains a full-cycle status record table compiled by object identifier based on the thread event flow, and performs permission verification and precondition verification to generate instruction sheets and gap exception sheets.

[0105] The task completion module executes business orchestration and generates management tasks based on the instruction sheet, locates the topological break relationship based on the gap and anomaly sheet and initiates a completion request, forms an execution result thread event and synchronously updates the full-cycle status record table.

[0106] This embodiment also provides a computer device applicable to the building life cycle monitoring and management method, including: a memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to realize the building life cycle monitoring and management method proposed in the above embodiment.

[0107] The computer device can be a terminal, comprising a processor, memory, communication interface, display screen, and input devices connected via a system bus. The processor provides computing and control capabilities. The memory includes non-volatile storage media and internal memory. The non-volatile storage media stores the operating system and computer programs. The internal memory provides an environment for the operation of the operating system and computer programs stored in the non-volatile storage media. The communication interface is used for wired or wireless communication with external terminals; wireless communication can be achieved through Wi-Fi, carrier networks, NFC (Near Field Communication), or other technologies. The display screen can be an LCD screen or an e-ink screen. The input devices can be a touch layer covering the display screen, buttons, a trackball, or a touchpad on the computer device's casing, or an external keyboard, touchpad, or mouse.

[0108] This embodiment also provides a storage medium storing a computer program, which, when executed by a processor, implements the building lifecycle monitoring and management method proposed in the above embodiments. The storage medium can be implemented by any type of volatile or non-volatile storage device or a combination thereof, such as Static Random Access Memory (SRAM), Electrically Erasable Programmable Read-Only Memory (EEPROM), Erasable Programmable Read Only Memory (EPROM), Programmable Red-Only Memory (PROM), Read-Only Memory (ROM), magnetic storage, flash memory, magnetic disk, or optical disk.

[0109] In summary, this invention constructs a digital thread topology using responsible entity nodes, business process nodes, and business data nodes. It then summarizes these into a digital thread topology table based on allowed triggering relationships, required submission relationships, and attribution relationships, providing enumerable topological basis for process triggering and data submission constraints. In the engineering business phase, business document execution elements are parsed and encapsulated into thread event shells. Evidence is verified and retained through indexed summary associations of evidence pointers. Simultaneously, consistent associations are executed using the digital thread topology table to form thread event flows and update object passports, ensuring that event trajectories can be aggregated by object identifiers. A full-cycle status record table is generated based on the thread event flow, and the ready item fields are compared and verified with the event trajectory fields. Combined with permission checks and precondition checks, instruction orders or gap / abnormality orders are generated, achieving certainty and interpretability in process advancement. Instruction orders drive management tasks, and gap / abnormality orders drive completion requests and write back execution results as thread events, ensuring continuous synchronous updates to the full-cycle status record table. This improves cross-stage information coherence, compliance auditability, and anomaly location efficiency.

[0110] Example 2, referring to Table 1, is the second embodiment of the present invention. To further verify the technical solution of the present invention, experimental simulation data of the building life cycle monitoring and management method are given.

[0111] This embodiment selects a "New Construction Project of a 220kV Substation in a Certain Province" as the verification project. This project involves one construction unit (provincial power grid company), one design unit (power design institute), one general contractor (an engineering bureau), three major equipment suppliers (TBEA, Pinggao Electric, and NARI Group), and subsequent operation and maintenance units. To verify this solution, a digital thread management platform based on this invention was deployed and its data interface was integrated with the project's existing ERP (Enterprise Resource Planning) system and PMS (Project Management System).

[0112] First, the platform records the main information of all participating parties, taking "substation" projects as units, and registers job roles under each entity, such as "project specialist" of the provincial power grid company, "structural designer" of the design institute, "purchasing agent" and "warehouse manager" of the general contractor, "sales manager" and "shipping agent" of the supplier, and "inspection team leader" of the operation and maintenance unit, etc. A unique identifier is generated for each responsible entity, such as "EP-OWNER-001" and "EP-DESIGN-001".

[0113] Subsequently, the system configures six core business process nodes covering the project: Purchase Order (PO), Goods Receipt and Warehousing (GR), Initial Quality Control (IQC), Installation Inspection (IR), Commissioning and Handover (COM), and Work Order (WO), assigning process node identifiers such as "PROC-PO" and "PROC-GR". Then, it configures the required business data nodes for each business process. For example, the Purchase Order process requires the submission of "Purchase Order Number (PO_ID)", "Equipment Identifier (EQUIP_ID)", and "Contract Number (CONTRACT_ID)"; the Goods Receipt and Warehousing process requires the submission of "Delivery Order Number (GR_ID)", "Equipment Identifier", and "Material Document Number", generating unique node identifiers for each business data field, such as "DATA-PO_ID" and "DATA-EQUIP_ID".

[0114] Within the business data nodes, the "Equipment Identifier (EQUIP_ID)" and "Work Package Code (WBS)" were located. During historical data cleaning, it was discovered that the same main transformer was identified as "TR-220-001," "BYQ-220-001," and "Transformer Phase A" in the design drawings, purchase contracts, and supplier delivery notes, respectively. Using the "consistency merging" rules described in the invention (such as uniformly converting to uppercase and removing spaces and separators), these were normalized to "TR220001." Simultaneously, its associated work package code is "WBS-ELEC-01." Statistical analysis shows that the maximum length of EQUIP_ID in this project is 20 characters, and the maximum length of WBS is 15 characters. Subsequently, the "combined coding" rule is applied: "WBS-ELEC-01" is fixed-length to 15 characters "WBS-ELEC-01-", and "TR220001" is fixed-length to 20 characters "TR220001-", concatenating them to generate the object identifier "WBS-ELEC-01-TR220001-". This identifier is globally unique and is mapped to the normalized source equipment identifiers and work package codes, recorded in the object's "passport". Similarly, object identifiers are generated for all critical equipment such as switchgear and relay protection devices. Finally, based on the invention's content, permission triggering relationships (e.g., only the "purchasing agent" role can trigger the purchase order process), submission requirement relationships (e.g., the arrival and warehousing process must submit the "delivery order number" and "equipment identifier"), and attribution relationships (associating the business data "equipment identifier: TR220001" with its object identifier) ​​are established to form a complete digital thread topology table.

[0115] When actual business operations occur during the project, a thread event is triggered. For example, a dispatcher from the supplier "TBEA" initiates a goods arrival and warehousing process, creating a goods arrival note GR-2023-0801 in the system, associated with the equipment identifier "TR220001". The platform automatically encapsulates the thread event shell: the object identifier is "WBS-ELEC-01-TR220001-", the process node identifier is "PROC-GR", the responsible entity identifier is the supplier node identifier, and the storage path of the goods arrival note photo and the SHA-256 digest value are attached as evidence pointers. After verifying the relationship with the digital thread topology table, the event is registered as a thread event stream, and the main transformer object "passport" is updated synchronously to record this goods arrival event.

[0116] The system automatically maintains a full-cycle status record table for all objects in this project. Taking object identifier "WBS-ELEC-01-TR220001-" as an example, the system aggregates all its thread events (procurement, arrival, unpacking) to form an event trajectory; it extracts business data nodes such as "commissioning report number" and "acceptance signature sheet" required by the commissioning and handover process from the topology table to form ready items. Through set operations, the system automatically determines "commissioning report" and other items as "items to be satisfied". When the general contractor attempts to initiate the commissioning and handover process for this main transformer, the system automatically performs verification:

[0117] (1) Permission verification: Whether the initiator role "Debugging Engineer" is allowed by the topology table to trigger the "PROC-COM" process;

[0118] (2) Precondition verification: Check whether there is a record of "Installation inspection completed" in the "Event Track" (i.e., the business data node corresponding to the installation inspection process);

[0119] (3) Object Consistency Verification: Verify whether the identification of the transformer is consistent in all historical processes. In the comparative test of this embodiment, a scenario was simulated where the "Installation Inspection Report" document was missing due to human error. Under the traditional method, this missing document may only be discovered in the later stages of commissioning or even during handover, resulting in rework. However, this solution can detect the missing document through precondition verification the moment the commissioning process is initiated, and automatically generate a missing document.

[0120] For cases where the verification is successful, the system automatically generates an instruction sheet pointing to the next stage (such as a maintenance work order). For the "missing installation inspection record" anomaly identified above, the system generates a gap anomaly report and locates the break in the data based on the topology table: the missing business data node is the "Installation Inspection Record (IR_ID)," and the responsible party for supplementing it is the general contractor's "Quality Engineer." The system automatically sends a supplementation request to the engineer and associates it with the corresponding management task. Once the engineer submits the supplementary inspection record, a new execution result thread event is generated, and the system synchronously updates the full-cycle status record table of the main transformer. "Items to be satisfied" is updated, and "Installation Inspection" becomes "Items satisfied," clearing obstacles for subsequent process advancement.

[0121] To quantify the results, during the project's trial operation, six typical equipment / components covering the procurement, construction, and commissioning phases were selected. Parallel tracking and data recording were conducted using both the traditional manual ledger management method (control group) and this digital thread topology management method (experimental group). Key comparisons are shown in the table below.

[0122] Table 1 Comparison of Project Management Effectiveness

[0123] Trial phase object type Average verification time (minutes) Average time (days) to detect anomalies in prerequisite conditions Status update delay (hours) Data inconsistency rate (%) Automatic process breakpoint location rate (%) Average time (in days) for exception handling closed loop Traditional methods - procurement main transformer 45.2 14.5 48.2 8.3 0 7 This plan - Procurement main transformer 0.5 0.02 0.1 0 100 1.5 Traditional method - delivery High voltage switchgear 38.7 7.2 36.5 5.6 0 5.5 This plan - upon delivery High voltage switchgear 0.3 0.01 0.1 0 100 1 Traditional method - installation Relay protection panel 120.5 21 72 12.5 0 10.5 This solution - installation Relay protection panel 0.8 0.03 0.2 0 100 2 Traditional methods - debugging Power cable (km) 90.3 10.8 60.5 9.8 0 8.8 This solution - debugging Power cable (km) 1.2 0.05 0.3 0 100 2.5 Traditional method - handover GIS Combined Electrical Appliances 150 28 96 15 0 14 This plan - handover GIS Combined Electrical Appliances 2 0.1 0.5 0 100 3 Traditional methods - Operations and maintenance Smart meters (100 units) 60.8 5.5 24 3.2 0 4.2 This solution - Operations and Maintenance Smart meters (100 units) 0.2 0 0.1 0 100 0.5

[0124] First, this solution demonstrates advantages in management efficiency and real-time performance. As shown in the table, the "average verification time" has been drastically reduced from tens of minutes to several hours (38.7~150.0 minutes) in traditional methods to seconds or minutes (0.2~2.0 minutes) in this solution. This is directly attributed to the automated verification mechanism: business rules are abstracted into a set of "required submission relationships" and "allowed triggering relationships" in a digital thread topology table, and instant matching and judgment are performed through set operations (intersection / difference) and indicator functions, replacing the tedious process of manually reviewing multiple documents and cross-departmental communication in the traditional way. At the same time, the "status update latency" has been reduced from tens of hours (24.0~96.0 hours) to near real-time (0.1~0.5 hours), thanks to the automatic drive mechanism of thread event stream. Once any business event occurs, the thread event shell it encapsulates automatically triggers the update of the object passport and the full-cycle status record table, achieving "zero" latency in status synchronization and ensuring the timeliness of the management view.

[0125] Secondly, the innovation of this solution is particularly prominent in the dimensions of quality control and risk prevention. The "average time for detecting anomalies in preconditions" has been shortened from several days or even weeks (5.5~28.0 days) under traditional methods to minutes or hours (0.0~0.1 days) under this solution. Traditional methods rely on manual review at the end of each stage, resulting in delayed anomaly detection and high rework costs. This solution, through "precondition verification," automatically checks whether the event trajectory field has completely contained the precondition business data nodes required by the topology table during each process advancement attempt. This deterministic, real-time verification based on topology relationships intercepts problems before the process starts, fundamentally changing the post-event error correction management model and achieving real-time prevention and control during the process. The "data inconsistency rate" is as high as 3.2%~15.0% in traditional methods, while it is reduced to 0% in this solution. This is entirely thanks to the "consistent merging" and "combined coding to generate object identifiers" mechanisms, which unify object identifiers across businesses and systems from the source, and ensure the uniqueness and consistency of objects throughout their entire lifecycle through "object association consistency result" verification, thus completely solving the "single-item mismatch" problem caused by coding chaos.

[0126] Finally, this solution achieves a breakthrough in closed-loop management and decision support capabilities, going from nothing to something. Traditional methods have a 0% automatic process breakpoint location rate, and anomaly handling relies on manual investigation, resulting in low efficiency. This solution, through linkage, not only generates a "gap anomaly report" when verification fails, but also accurately locates the "set of missing business data node identifiers" and the "identifiers of associated responsible entity nodes," achieving 100% automatic location. This stems from abstracting process breakpoints as the difference between the "set of required submission relationships" and the "set of event trajectories that have appeared," and mapping this difference to the responsibility relationships in the topology. The significant reduction in the "average time for anomaly handling closed loop" (from 4.2-14.0 days to 0.5-3.0 days) verifies the effectiveness of the closed-loop management mechanism that automatically initiates "fill-in requests" and forms task associations based on gap anomaly reports.

[0127] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and are not intended to limit it. Although the present invention has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of the present invention without departing from the spirit and scope of the technical solutions of the present invention, and all such modifications or substitutions should be covered within the scope of the claims of the present invention.

Claims

1. A method for monitoring and managing the entire life cycle of a building, characterized in that: include, Construct a digital thread topology and establish object passports and object identifiers to form a digital thread topology table; When business documents are generated in the engineering business process, the thread event shell is uniformly encapsulated and associated with the digital thread topology table to form a thread event stream, while updating the object passport information. Based on the thread event flow, maintain a full-cycle status record table compiled by object identifier, and perform permission verification and precondition verification to generate instruction orders and gap exception orders; Based on the instruction sheet, execute business orchestration and generate management tasks; based on the gap and anomaly sheet, locate the topological break relationship and initiate a completion request; generate execution result thread events and synchronously update the full-cycle status record table.

2. The building life cycle monitoring and management method as described in claim 1, characterized in that: The specific steps for constructing the digital thread topology are as follows. Register project participants and their roles, and generate responsible entity nodes and their identifiers; Configure the engineering business process set and generate business process nodes and process node identifiers; Configure the business dataset to merge and generate business data nodes and business data node identifiers; Extract component identifiers, equipment identifiers, and work package codes from the business data set, and generate object identifiers according to unified coding rules; The object identifier is registered as an object passport entry and bound to the responsible entity node identifier and job role to form a digital thread topology.

3. The building life cycle monitoring and management method as described in claim 1, characterized in that: The digital thread topology table is obtained by summarizing the allowed triggering relationship between the responsible entity node and the business process node, the required submission relationship between the business process node and the business data node, and the attribution relationship between the business data node and the object identifier.

4. The building life cycle monitoring and management method as described in claim 1, characterized in that: When business documents are generated during the engineering process, a unified thread event shell is encapsulated and associated with a digital thread topology table to form a thread event stream. Simultaneously, object passport information is updated. The specific steps are as follows. The execution elements of the business document are parsed to generate a thread event shell. Evidence pointers are generated for the business document and an index summary association is established. The thread event shell is associated with the execution consistency of the digital thread topology table to form a thread event flow. Write the business document identifier, process node identifier, responsible entity node identifier, and evidence pointer corresponding to the object identifier in the thread event stream into the object passport to form the object passport update result.

5. The building life cycle monitoring and management method as described in claim 1, characterized in that: The full-cycle state record table is formed by aggregating thread event streams according to object identifiers.

6. The building life cycle monitoring and management method as described in claim 1, characterized in that: The steps for maintaining a full-lifecycle state record table based on object identifiers, according to the thread event flow, are as follows: Register the request to submit the relationship as the ready item field, register the object passport mapping information as the object index field, and register the thread event stream aggregation information as the event trajectory field; Perform a comparison and verification between the ready items field and the event trajectory field, and update the items to be satisfied and the items that have been satisfied. Perform a consistency check between the object index field and the thread event stream object identifier, output the object association consistency result and write it to the full life cycle status record table.

7. The building life cycle monitoring and management method as described in claim 1, characterized in that: The specific steps for execution permission verification and precondition verification are as follows. Extract the latest thread event shell from the thread event stream, and parse the responsible entity node identifier, job role, and process node identifier to form the permission verification elements; The permission verification elements are matched with the allowed triggering relationships to obtain the permission verification results; The process node identifier is used to retrieve the required submission relationship, and the results of the consistency between the ready item field, event trajectory field and object association are combined to generate a list of prerequisite conditions; Verify the list of preconditions with the event trajectory field to obtain the precondition verification results; The system combines the results of permission verification, object association consistency verification, and precondition verification to make a combined judgment. An instruction form is generated when all three are satisfied, and a gap exception form is generated when any one of them is not satisfied.

8. The building life cycle monitoring and management method as described in claim 1, characterized in that: The specific steps for executing business orchestration and generating management tasks based on instruction sheets are as follows: Analyze the next process node identifier, responsible entity node identifier, and job role in the instruction sheet to determine the corresponding engineering business process; The next process node identifier is mapped to the engineering business link as an execution action, a management task is generated, and the task acceptance status and completion status are recorded to form a task status record.

9. The building life cycle monitoring and management method as described in claim 1, characterized in that: The specific steps for initiating a completion request based on the topological fracture relationship of the gap anomaly are as follows: Analyze the missing data exception order to obtain the corresponding process node identifier and the missing data node identifier; Submit the relationship according to the corresponding process node identifier search requirements, and locate the associated responsible entity node identifier according to the allowed triggering relationship to form the topological break relationship location result; Combine the topological fracture relationship location results with the object passport binding information to generate a completion request and assign it to the corresponding job role. Retrieve the management task identifier corresponding to the object identifier and process node identifier from the task status record, and write it into the completion request; The request acceptance information and business document identifier are encapsulated into an execution result thread event shell and written into the thread event stream. At the same time, they are registered in the full-cycle status record table and the results of unmet items, met items and object association are updated.

10. A building life cycle monitoring and management system, based on the building life cycle monitoring and management method according to any one of claims 1 to 9, characterized in that: include, The digital topology module constructs the digital thread topology and establishes object passports and object identifiers to form a digital thread topology table. The event encapsulation module encapsulates thread events into shells and associates them with a digital thread topology table when business documents are generated in the engineering business process, forming a thread event stream and updating the object passport information at the same time. The status verification module maintains a full-cycle status record table compiled by object identifier based on the thread event flow, and performs permission verification and precondition verification to generate instruction sheets and gap exception sheets. The task completion module executes business orchestration and generates management tasks based on the instruction sheet, locates the topological break relationship based on the gap and anomaly sheet and initiates a completion request, forms an execution result thread event and synchronously updates the full-cycle status record table.

Images