Intelligent database-driven construction site multidimensional collaborative management method and system

Abstract

This invention discloses an intelligent database-driven method and system for multi-dimensional collaborative management of construction sites, relating to the field of collaborative control technology for engineering projects. The method includes constructing an object, relationship, and evidence ledger in an intelligent database; automatically expanding the affected scope and solidifying it as a unified basis after an item is entered into the database; classifying and adjudicating on-site handling based on quality, safety, and resources within the affected scope, generating a gap list and evidence requirements; dispatching handling actions and recording receipts in the database, updating the gap closure status to form preconditions; generating effective adjudications for plans, costs, and changes, and pre-setting review requirements for adjudications of on-site conditions; and recording and updating the ledger once an adjudication meets a threshold. The method of this invention automatically expands and solidifies the affected scope through a database, supports multi-dimensional adjudication recording and effectiveness with gap closure and evidence gating, and allows for playback and reconciliation, thereby achieving consistency in the scope of collaborative management of construction sites, verifiable decisions, traceable processes, and rapid reconciliation of disputes.

Description

Technical Field

[0001] This invention relates to the field of collaborative control technology for engineering projects, specifically to an intelligent database-driven method and system for multi-dimensional collaborative management of construction sites. Background Technology

[0002] In recent years, with the development of smart construction sites and digital construction systems, construction site management has gradually shifted from experience-driven to data-driven and process-verifiable. Technologies such as project management information systems, BIM / CIM semantic modeling, IoT sensing, mobile inspection, electronic signatures, and online approvals have driven the online and structured accumulation of business chains related to planning, resources, quality, safety, cost, and changes. Simultaneously, infrastructure such as relational intelligent databases, graph data management, and data lake warehouses support the centralized management of project entity ledgers, dependency constraints, process records, and evidence materials, providing a calculable data foundation for cross-participant collaboration, process traceability, statistical analysis, and risk control.

[0003] Existing technologies are mostly based on stacked business modules, making it difficult to achieve unified and collaborative adjudication and verifiable closed-loop processes. Firstly, post-event impact analysis often relies on manual experience or static rules, lacking automatic scope expansion and solidification mechanisms based on dependency constraints. This leads to inconsistent understandings of the impact boundaries of the same event by different roles, resulting in fragmented collaborative interpretations. Secondly, on-site handling is often disconnected from management decisions regarding planning, costs, and changes. There is a lack of gating mechanisms based on gap lists and evidentiary requirements, easily leading to decisions being made even with incomplete evidence or execution decisions being made before the handling process is closed, resulting in weak decision-making basis and difficulty in verification. Thirdly, there is insufficient control over the threshold conditions for adjudication effectiveness, traceability constraints, and synchronized record updates, leading to inconsistencies in the state before and after adjudication, affecting subsequent recalculation and traceability. Fourthly, for adjudications that may change on-site conditions, such as alternative materials / processes, process rearrangements, resource additions, and window period adjustments, there is a lack of pre-set review and trigger verification mechanisms, making it difficult to ensure that quality, safety, and concurrent operation constraints are still met after the adjudication takes effect. Fifth, reconciliation audits often only cover report summarization and result archiving, making it difficult to replay the entire process from the event to evidence, handling, adjudication, effectiveness, and verification. This makes it impossible to achieve the comprehensive technical effects of consistent scope, closed-loop gate control, effectiveness, and traceability as proposed in this invention. Summary of the Invention

[0004] In view of the above-mentioned problems, the present invention is proposed.

[0005] Therefore, the technical problem solved by this invention is that existing construction site collaborative management methods have the following problems: the scope of impact after an event is triggered is difficult to expand automatically and the standards are inconsistent; on-site handling and the adjudication of planned cost changes lack a gate control mechanism with evidence and gap closure as prerequisites; the lack of record keeping of adjudication effectiveness and synchronous updating of ledgers makes it difficult to verify and trace; and how to achieve effective adjudication, review triggering and full-link reconciliation playback under multi-dimensional collaboration.

[0006] To address the aforementioned technical problems, this invention provides the following technical solution: a smart database-driven multi-dimensional collaborative management method for construction sites, comprising: constructing an object, relationship, and evidence ledger in a smart database; automatically expanding the scope of impact and solidifying it as a unified basis after items are entered into the database; classifying and adjudicating on-site handling based on quality, safety, and resources within the scope of impact, generating a gap list and evidence requirements; dispatching handling actions according to the gap list and recording receipts in the database, updating the gap closure status to form preconditions; after the preconditions are met, forming effective decisions for plans, costs, and changes, and presetting review requirements for decisions on on-site conditions; once a decision meets a threshold, it becomes effective and is recorded and updated synchronously in the ledger; verification is triggered according to review requirements, and the entire chain of output reconciliation materials is replayed when needed.

[0007] As a preferred embodiment of the intelligent database-driven multi-dimensional collaborative management method for construction sites described in this invention, the step of constructing an object, relationship, and evidence ledger in the intelligent database includes, when establishing the object ledger, registering and filing participating units, personnel teams, machinery and equipment, material batches, component locations, work areas, process tasks, acceptance items, and change orders respectively, generating and fixing a unique number for each object; and writing the object's responsible entity, location attribution, status, and effective time into the intelligent database.

[0008] As a preferred embodiment of the intelligent database-driven multi-dimensional collaborative management method for construction sites described in this invention, the following steps are taken: After an item is entered into the database, its affected scope is automatically expanded and solidified into a unified basis. This includes: using the unique object number in the item record as the starting point, sequentially searching for dependencies between processes to determine the preceding and subsequent processes; searching for work surface occupancy and parallel restriction relationships to identify conflicting work activities; searching for material batches and their inspection and usage locations to locate affected components and acceptance points; and searching for equipment and work group and work surface usage relationships to identify resource occupancy impacts. If the item involves changes or approvals, the corresponding relationship between changes, measurements, and approvals is searched to determine the affected scope and nodes. The retrieved objects are deduplicated, merged, and bound to an evidence index.

[0009] As a preferred embodiment of the intelligent database-driven multi-dimensional collaborative management method for construction sites described in this invention, the following steps are included: Classifying and adjudicating on-site handling based on quality, safety, and resources within the affected area. This includes determining whether to initiate handling based on key object elements, construction window status, completeness of evidence, risk statistics, and parallel constraints and conflicts between resources and work surfaces. After initiation, handling conclusions are formed based on quality, safety, and resources, and a gap list and evidence requirements are generated simultaneously, clearly defining the responsible party, completion deadline, and priority items for closure.

[0010] As a preferred embodiment of the intelligent database-driven multi-dimensional collaborative management method for construction sites described in this invention, the step of dispatching disposal actions and recording receipts in the database according to the gap list includes: converting each item in the gap list into disposal action items and sorting them according to their dependencies; dispatching the disposal actions to the corresponding units or positions according to the responsible entities registered in the object ledger; after the responsible party executes the action, writing the execution time, execution position, execution result, and evidence registration information corresponding to the execution result into the intelligent database to form a receipt; the intelligent database then updates the gap status based on the receipt content and the verification results against the evidence ledger, and performs separate verification on matters that must be prioritized for closure, outputting the status of whether the preconditions for the adjudication are met or not.

[0011] As a preferred embodiment of the intelligent database-driven multi-dimensional collaborative management method for construction sites described in this invention, the following steps are taken: after the preconditions are met, effective decisions are made for plans, costs, and changes. The pre-set review requirements for decisions on site conditions include verifying whether priority closed-loop items have been completed and whether the necessary evidence is complete before making an effective decision; when there are incomplete items or missing evidence, a list of preconditions is generated and kept waiting until the preconditions are met before proceeding to the classified decision on plans, costs, and changes; during the decision-making process, it is determined whether the proposed decision involves changes to site conditions, and if so, the categories and scope of verification to be verified are pre-recorded in the decision conclusion.

[0012] As a preferred embodiment of the intelligent database-driven multi-dimensional collaborative management method for construction sites described in this invention, the following features are included: The adjudication meeting the threshold and thus becoming effective and synchronously updating the ledger includes forming an effective record by adding traces after the adjudication meets the threshold, and synchronously updating the status and dependencies of the object ledger and relationship ledger; when the effective record pre-includes on-site verification requirements, corresponding verification items are automatically generated and the verification scope is limited after effectiveness; for cases where verification fails, remedial measures are generated and restrictive statuses are written to the relevant processes or work surfaces until remediation is completed; in settlement, audit, or dispute scenarios, the entire process of item entry into the database, expansion of the affected scope, gap handling and closure, adjudication formation and effectiveness, verification and remediation is replayed using the unique number of the affected scope or object as the anchor point, and reconciliation materials containing evidence indexes and responsibility chains are output.

[0013] Another objective of this invention is to provide an intelligent database-driven multi-dimensional collaborative management system for construction sites. This system can generate a gap list and evidence requirements by classifying and adjudicating on-site handling based on quality, safety, and resources, around the affected area. This solves the problem that current construction site collaborative management methods lack a gating mechanism with evidence and gap closure as prerequisites for on-site handling and planned cost change adjudication.

[0014] As a preferred embodiment of the intelligent database-driven multi-dimensional collaborative management system for construction sites described in this invention, it includes: a ledger creation module, a site handling closed-loop module, and an effective adjudication module; the ledger creation module is used to establish object, relationship, and evidence ledgers in the intelligent database, and automatically expand and solidify the affected scope after the items are entered into the database; the site handling closed-loop module is used to complete the handling adjudication and gap management of quality, safety, and resources within the affected scope, dispatch handling actions, enter receipts into the database, and form verifiable closed-loop preconditions; the effective adjudication module is used to form planning, cost, and change adjudication after the preconditions are met, and record the effective adjudication, trigger site verification according to preset requirements, and replay the entire chain output reconciliation materials when necessary.

[0015] A computer device includes a memory and a processor, the memory storing a computer program, and the processor executing the computer program to implement a smart database-driven multi-dimensional collaborative management method for construction sites.

[0016] A computer-readable storage medium having a computer program stored thereon, wherein when the computer program is executed by a processor, the steps of implementing a smart database-driven multi-dimensional collaborative management method for construction sites are disclosed.

[0017] The beneficial effects of this invention are as follows: The intelligent database-driven multi-dimensional collaborative management method for construction sites provided by this invention establishes an engineering entity ledger, dependency constraint relationship, and evidence ledger in the intelligent database, and automatically expands the scope of impact after the matter is entered into the database. This achieves unified solidification of the impact boundary of the same matter, eliminating differences in interpretation and omissions in scope among multiple participating parties, thereby achieving the beneficial effects of consistent collaborative discussion benchmarks and the ability of subsequent handling and adjudication to be verified within the same scope. By conducting on-site handling classification and adjudication based on quality, safety, and resources around the scope of impact, it achieves domain-specific identification of on-site risks and resource conflicts and generates targeted handling conclusions, which are used to implement handling requirements into gap lists and evidence requirements, thereby achieving the beneficial effects of quantifiable handling objectives, assignable responsibilities, and traceable evidence. By dispatching handling actions based on the gap list and registering receipts and evidence into the database, a closed-loop traceability of the handling execution process is achieved. The system updates gap status to establish verifiable preconditions, preventing decisions from being made without complete evidence or before gaps are closed, thus improving process reproducibility. By establishing effective rulings on plans, costs, and changes after preconditions are met, and pre-setting review requirements for rulings that may alter site conditions, the system ensures consistency between management rulings and site constraints. This guarantees that alternative materials, process rearrangements, resource additions, or window adjustments still comply with quality, safety, and parallel operation restrictions, resulting in executable rulings and controllable risks. Furthermore, by recording the ruling's effectiveness upon threshold fulfillment and simultaneously updating the ledger, triggering verification according to review requirements, and replaying the entire chain of reconciliation materials when needed, the system ensures ruling effectiveness, status consistency, and replayable evidence chains. This supports settlement audits, dispute resolution, and accountability tracing, achieving a comprehensive technical effect of multi-dimensional collaborative management that is effective, verifiable, and traceable. Attached Figure Description

[0018] 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.

[0019] Figure 1 The first embodiment of the present invention provides an overall flowchart of a smart database-driven multi-dimensional collaborative management method for construction sites. Detailed Implementation

[0020] To make the above-mentioned objects, features, and advantages of the present invention more apparent and understandable, specific embodiments of the present invention will be described in detail below with reference to the accompanying drawings. Obviously, the described embodiments are only a part of the embodiments of the present invention, and not all of them. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the protection scope of the present invention.

[0021] Example 1, referring to Figure 1 As an embodiment of the present invention, a smart database-driven multi-dimensional collaborative management method for construction sites is provided, comprising:

[0022] S1: Build an object, relationship and evidence ledger in the intelligent database. After the event is entered into the database, the scope of impact is automatically expanded and solidified as a unified basis.

[0023] Furthermore, upon the commencement of a construction project or its initial inclusion in management, an object ledger is established in the intelligent database. This ledger centrally registers various objects involved in site management, including participating units and positions, personnel and work teams, machinery and equipment, materials and batches, components and locations, work areas and work zones, procedures and tasks, inspection and acceptance items, and change and approval matters. For each object record, at least the following basic information must be recorded: object category, object name or number, project or contract, location or work area, responsible unit or position, current status, and effective date. To ensure that all records consistently point to the same object, the object ledger generates and assigns a unique number to each object record. All subsequent business records are associated using this unique number, not by name, thus avoiding data merging issues caused by identical names, aliases, abbreviations, or differences in terminology used by different participating parties.

[0024] In this invention, the intelligent database refers to a data storage and processing platform used to support multi-dimensional collaborative management of construction sites. Based on an intelligent database management system, it combines capabilities such as rule calculation, association retrieval, version tracking, and evidence index management to achieve unified storage, unified association, unified verification, and traceable playback of multi-source data from the construction site. The intelligent database includes at least a data storage component, an index retrieval component, an association calculation component, and a consistency verification component.

[0025] The data storage component is used to store various structured and semi-structured data related to construction management, including information on participating units, personnel teams, machinery and equipment, material batches, component locations, work areas, work processes, inspection and acceptance, change orders, disposal receipts, approval confirmations, etc., and generates unique numbers and effective time information for each type of record; the index retrieval component is used to create retrieval indexes for key fields in the records, and to create referable index information for evidence materials such as image data, inspection reports, work permits, inspection records, on-site supervision records, and signed documents, so that any management conclusion can be located at the corresponding evidence registration; the association calculation component is used to... Based on pre-registered dependency constraints, the system performs related searches and scope expansion. For example, it calculates the set of potentially affected objects based on process dependencies, work surface occupancy and parallel constraints, material batch and usage location correspondence, equipment and work group usage relationship, and change, measurement and approval correspondence, and solidifies them into affected scope records. The consistency verification component is used to verify whether the preconditions are met when the disposal and adjudication are formed, including whether the necessary evidence is complete, whether the priority closed-loop matters are completed, whether there are conflicts between resources and parallel constraints, and whether the adjudication effective threshold is met. The verification results are written to the intelligent database in a traceable manner for subsequent review and reconciliation.

[0026] In practical implementation, the intelligent database can be implemented using a relational intelligent database, graph data management, or a combination of both. It can also be used in conjunction with time-series data storage, file storage, or object storage to meet the needs of multi-source data access and evidence material indexing management at construction sites. This invention does not limit the specific software product or deployment form of the intelligent database. Its key lies in: through the association calculation and verification / tracking mechanism on the intelligent database side, forming a unified scope of impact that can be used for collaborative adjudication, verifiable gap-closing preconditions, and a basis for replayable reconciliation material output.

[0027] It should be noted that, to enable the intelligent database to accurately locate objects and their status across management dimensions such as progress, resources, quality, safety, cost, environment, and changes, the object ledger simultaneously embeds basic constraint information related to location and time during registration. For work surfaces and work areas, the database records spatial boundary descriptions, floor or axis ranges, and parallel operation restrictions; for processes and tasks, it records planned start and finish times, prerequisites, and associated acceptance and inspection points; for personnel and work teams, it records job types, qualification validity periods, and available work time windows; for machinery and equipment, it records equipment models, key capability parameters, availability, and inspection cycles; and for materials and batches, it records supply information, batch numbers, inspection status, applicable scope, and limitations. All of this information is written into the intelligent database as structured fields for subsequent scope expansion, conflict identification, and evidence verification, rather than simply being saved as text comments.

[0028] It should also be noted that, based on the object ledger, a relationship ledger is established to register the dependencies and constraints between objects, enabling the intelligent database to automatically deduce other objects that may be affected by a single event. The relationship ledger should include at least the following common relationship types: pre- and post-process dependencies; occupancy and parallel restriction relationships within the same work surface or spatial range; binding relationships between components and processes; correspondences between material batches and inspection records / usage locations; usage relationships between equipment and work groups / work surfaces; correspondences between acceptance items and process nodes; and correspondences between change items and list measurement / approval processes. Each relationship record should at least include the unique IDs of the objects at both ends of the relationship, the relationship type, the relationship direction (e.g., pre- to post-, occupied to occupied), the relationship's effective and ineffective times (if any), and a description of the relationship constraints (e.g., must be met, adjustment allowed, mutually exclusive, parallelizable but subject to conditions). By consistently registering these elements, the relationship ledger ensures that it can not only be used for display but also for associative retrieval and scope expansion during intelligent database calculations.

[0029] Furthermore, an evidence ledger should be established to centrally register various evidentiary materials generated during the construction process, including video footage, test reports, experimental records, work permits, inspection records, on-site monitoring records, patrol records, meeting minutes, and signed documents. For each piece of evidence, at least the evidence type, creation time, providing unit or source, corresponding object unique number, corresponding work process or work area, and the storage location or access path of the evidence file should be recorded. In cases where evidence is supplemented or replaced multiple times for the same matter, the version and replacement relationships of the evidence should be recorded, retaining the differences in creation time and source, so that the order and scope of application can be distinguished during subsequent review. The association between evidence and object must be established using the object's unique number, avoiding matching based solely on filenames or descriptive text, thereby ensuring the traceability and verifiability of the evidence chain.

[0030] It should be noted that when on-site issues arise such as plan adjustments, quality defects, safety hazards, material replacements, resource conflicts, or visa changes, these issues will be recorded as a single event in the intelligent database. Each event record must include at least the event's occurrence time, event category, a set of unique identifiers for involved parties, an event description, the responsible unit or position, and a set of available evidence identifiers. For events requiring follow-up, the processing status and deadline should also be recorded. These mandatory elements ensure that the intelligent database not only stores event descriptions but also performs subsequent scope expansion, evidence completeness verification, and related queries based on the unique identifiers of the parties and the evidence identifiers.

[0031] It should also be noted that after an item is recorded and entered into the database, the intelligent database uses the unique number of the object directly involved in the item as the starting point, performs a correlation search based on the relationship ledger, automatically obtains the set of potentially affected objects, and generates an affected scope record. Specifically, the process is as follows: First, it searches for the preceding and following processes and their corresponding acceptance points related to the item along the process dependency relationship; second, it searches for other work activities that may have space conflicts or parallel restrictions along the work surface occupancy relationship; third, it searches for the component parts, inspection and acceptance items related to the material batch along the material batch and usage location relationship; fourth, it searches for the tasks and work surfaces related to the equipment occupancy or work team arrangement along the equipment and team usage relationship; if the item involves changes and approvals, it searches for the affected measurement standards and approval nodes along the relationship between the changed item and the list measurement and approval process. After deduplicating the retrieved object set, a list of affected objects is formed, and the management dimension category involved in the item (e.g., involving quality, safety, resources, planning, cost, changes, etc.) is simultaneously marked in the affected scope record, and the set of evidence numbers related to this scope is also bound together. Once the affected scope is recorded in the intelligent database, it serves as the unified basis for subsequent collaborative processing. Discussions, actions, receipts, and audits in subsequent steps are all based on this affected scope for retrieval and verification, thereby ensuring that all participating parties collaborate under the same scope and reducing repeated verifications and disputes caused by different scopes.

[0032] S2: Based on the affected area, classify and adjudicate on-site handling according to quality, safety, and resources, and generate a gap list and evidence requirements.

[0033] Furthermore, after generating the affected scope record, this record serves as the judgment object and scope for on-site handling classification decisions. The information used for the judgment comes from the fixed object ledger, relationship ledger, evidence ledger, and the event records themselves in the intelligent database. This includes a list of affected objects, the management dimension categories involved, key attributes of the objects (such as whether they belong to key processes or key parts), current status information (such as whether they are under construction, about to start construction, or awaiting acceptance), parallel operation restriction information, and evidence registration information associated with that scope. By clearly limiting the judgment scope to the affected scope record, it ensures that subsequent handling discussions are not expanded or omitted, and that all participating parties use the same scope criteria for on-site handling.

[0034] It should be noted that when the affected area includes critical processes, critical component parts, critical material batches, or special operation points, on-site handling classification decisions should be initiated. Critical processes can be determined by the critical path attributes, pre- and post-constraint strengths, and binding relationships with important node acceptance points recorded in the process log; critical component parts can be determined by the structural criticality, subsequent non-reinspectionability of coverage, or relevance to safety functions recorded in the component and part log; critical material batches can be determined by the main material attributes, mandatory inspection requirements, and substitution restrictions recorded in the material log; special operation points can be determined by the permit requirements for height work, hot work, temporary electricity, and lifting operations recorded in the work area log. If any of the above critical situations are met, and the event record or dimension label indicates involvement of any dimension related to quality, safety, or resources, it is considered necessary to complete classification and handling discussions at the on-site level first to prevent critical objects from entering subsequent plans or change decisions without completing on-site verification and pre-handling.

[0035] Furthermore, when the affected area is under construction, about to commence, or awaiting acceptance—requiring immediate decision-making—and an evidence registry search indicates that the essential evidence related to that area is incomplete, a site-specific ruling is initiated. Essential evidence refers to the minimum evidentiary requirements matching the object and matter category, such as inspection reports before material use, on-site monitoring or inspection records of key process nodes, special operation permits, pre-use inspection records of equipment, and measurement records of quality defect re-inspections. The completeness of evidence is directly verified by checking the registration information in the evidence registry regarding evidence type, related objects, formation time, and scope of application, without relying on verbal statements. This ruling is used to address common situations where decisions are needed but evidence is incomplete, requiring a clear strategy for supplementing evidence or suspending operations in the site-specific ruling to avoid proceeding with subsequent collaborative actions due to missing evidence.

[0036] It should be noted that when the intelligent database, based on records of hidden dangers, defects, boundary violations, or recurring similar problems within the affected area, determines that the risk level reaches a preset high-risk condition, a site-specific classification decision will be initiated. The risk level can be determined based on factors such as a concentrated number of hidden dangers on the same work surface within a short period, repeated occurrences of quality defects in the same location or process, multiple occurrences of the same type of violation or boundary violation, or defects reaching a severity level requiring immediate action. This rule emphasizes relying on historical and current records in the intelligent database, requiring that risk control and handling paths be clearly defined at the site level before proceeding with subsequent resource allocation or plan adjustments, thereby reducing the chain reaction risks caused by proceeding with problems.

[0037] Furthermore, when clear resource or space occupancy conflicts exist within the affected area, on-site handling-based classification and adjudication are initiated. Resource conflicts include critical equipment being occupied by multiple tasks within the same time window, the same work team being concurrently assigned to different work areas, and a mismatch between material supply capacity and planned demand. Space occupancy conflicts include mutually exclusive restrictions on parallel operations within the same work area, multiple trades simultaneously conducting cross-operations in the same high-risk area, and concurrent occupancy despite permit conditions requiring site clearing. Conflict identification is based on available time windows and occupancy boundaries registered in the object ledger, parallel restrictions in the work area ledger, and occupancy relationship records in the relationship ledger. This rule is used to classify and handle conflicts at the on-site level, determining whether parallel operations are possible, how to avoid conflicts, and whether relocation is necessary, to prevent conflicts from escalating into plan failures or safety incidents in subsequent steps.

[0038] It should be noted that once a case involving on-site handling is triggered, the intelligent database automatically summarizes the status of key objects within the affected scope, the list of existing evidence, missing evidence items, identified conflict items, and risk record summaries based on the list of affected objects, forming an input list for handling discussions. The handling discussions are conducted item by item, bounded by the affected scope, and deviations from this scope are not permitted. Furthermore, each handling conclusion must be linked to a unique object number and evidence number to ensure traceability and verifiability, preventing conclusions based solely on experience that cannot be traced back to the intelligent database.

[0039] Furthermore, when the affected scope involves quality dimensions or categories such as quality defects, material problems, or abnormal process quality, it enters a quality branch for categorized handling. The quality branch must include at least: confirming the location of the defect and related component parts, verifying the batch and inspection status of related materials, verifying whether the inspection and acceptance items corresponding to the process node are met, determining whether supplementary testing or re-inspection is needed, and determining whether rework or suspension of subsequent covered processes is required. The output of the quality branch must be written into the intelligent database and must at least specify: the supplementary testing or re-inspection items, the corresponding evidence type requirements, the responsible party, the completion deadline, and whether subsequent process progress is restricted if the preconditions are not met. The output content is fixed based on the object's unique number and evidence ledger registration, ensuring that subsequent steps can directly verify whether the quality handling has been completed.

[0040] It should be noted that when the affected scope involves safety dimensions or categories such as hidden dangers, violations, missing permits, or risk source handling, it should be categorized and handled within the safety branch. The safety branch should at least include: verifying the registration and control measures for risk sources at the work site; verifying the completeness and validity of special operation permits; verifying that on-site protective measures meet the restrictions on parallel operations; verifying that personnel qualifications are valid and meet job requirements; and, if necessary, specifying clearing, work stoppage, or isolation measures. The safety branch output should be written into the intelligent database and should at least specify: the permits required or supplementary handover records needed, the protective and isolation measures to be implemented, the responsible party, the completion deadline, and whether work commencement or parallel operations are prohibited until the conditions are met. The output should also be bound to a unique object number and evidence number for subsequent verification and reconciliation.

[0041] Furthermore, when the affected scope involves resource conflicts, equipment unavailability, work group scheduling conflicts, or material supply mismatches, the issue is categorized and handled through a resource branch. The resource branch should include at least: verifying the available time windows and parallel occupancy of personnel and work groups; verifying the availability and inspection status of key equipment; verifying whether material arrival and batch inspection status meet planned requirements; verifying the work area space occupancy boundaries and parallel constraints; and determining whether the conflict can be resolved through time-shifting, space avoidance, alternative resources, or adjusting task order. The resource branch output is written to the intelligent database and should at least specify: the conflicting entity, the conflict time window or occupancy boundary, the suggested allocation method or alternative resources, the responsible party and execution deadline, and whether it is necessary to restrict the initiation of related processes or limit parallel operations before resources are secured.

[0042] It should be noted that the handling conclusions from the three branches—quality, safety, and resources—are uniformly written into the intelligent database and linked by the scope of impact. For items that would prevent subsequent plan adjustments, cost processing, or changes from taking effect, they are clearly marked as items that must be prioritized for closure in the handling conclusions. Examples include incomplete material inspection, incomplete special operation permits, failed key equipment inspections, and incomplete re-inspections of critical defects.

[0043] S3: Dispatch handling actions according to the gap list and return receipts to the database, update the gap closure status to form the prerequisites.

[0044] Furthermore, after completing the resolutions for the quality, safety, and resource branches, the intelligent database summarizes and organizes the gaps output from each branch, forming an actionable gap list, and converts each gap into a corresponding action item. Each action item is linked based on a unique number in the object ledger and includes at least the object to which the gap belongs, the type of gap, a description of the required action, the type of evidence needed, the responsible unit or position, the completion deadline, and necessary preconditions. In cases where multiple gaps exist for the same object within the same affected area, the intelligent database merges them by the object's unique number and sorts the action items according to their order and dependencies, preventing the responsible party from performing subsequent actions without preconditions.

[0045] It should be noted that after a disposal action item is generated, the intelligent database determines the recipient of each disposal action item based on the responsible unit, responsible position, or management responsibility attribution information registered in the object ledger. For disposal actions that require multi-party collaboration, the intelligent database identifies the collaborating parties based on the binding and dependency relationships registered in the relationship ledger and breaks down the action into independently executable sub-actions, which are then dispatched to the corresponding responsible parties. At the same time, the database retains the dependency relationships and summary requirements between the sub-actions under the same gap issue.

[0046] Furthermore, when carrying out disposal actions, the responsible party should record the execution process and results in the intelligent database in the form of a receipt. The receipt should include at least: the actual execution time, the executor or their position, a description of the execution result, the unique identifier of the object involved, the corresponding disposal action item, and the evidence number or evidence material registration information matching the execution result. For quality-related disposal actions, the receipt should at least include the registration points of the re-inspection or testing results and link them to the corresponding test report or record; for safety-related disposal actions, the receipt should at least include the permit processing status, a description of the implementation of protective measures, and link them to the permit certificate or on-site record; for resource-related disposal actions, the receipt should at least include the personnel team allocation results, confirmation of equipment availability, or updates to the arrival and inspection status of materials, and link them to the corresponding ledger records or evidence registration. By specifying the minimum elements of the receipt, the intelligent database can complete gap status updates and closed-loop determination based on these elements, without relying on verbal confirmation.

[0047] It should be noted that when supplementary evidence is required for a handling action, the responsible party should first register the evidence in the evidence ledger, and then cite that ledger record in the receipt. Evidence registration must include the evidence type, creation time, source unit, unique identifier of the related party, and a description of the scope of application; if the evidence is replacement or supplementary material, its version or replacement relationship with existing evidence must also be registered. The receipt and evidence are linked through a smart database, enabling subsequent verification to directly locate the evidence from the handling action, avoiding the problem of scattered evidence making verification impossible.

[0048] Furthermore, upon receiving a receipt, the intelligent database updates the status of any gaps. This status update follows a unified standard: when the execution result registered in the receipt meets the requirements of the action item, and all required evidence types are registered in the evidence ledger and cited in the receipt, the gap is updated to "completed." When the receipt does not contain necessary evidence citations or the execution result does not meet the explicit requirements of the action item, the gap remains "incomplete," and a supplementary requirement prompt is generated in the intelligent database. When the object or relationship corresponding to the gap changes, rendering the original action inapplicable (e.g., material batch replacement, process sequence adjustment, or change of work area), the intelligent database updates the gap to "invalid," and requires the regeneration of applicable actions within the affected area after the update, ensuring that subsequent collaboration is always consistent with the actual situation on site.

[0049] It should be noted that for gaps marked as requiring priority closure, the intelligent database performs a separate closure check: if the critical gap is still incomplete, the critical gap is kept marked as not cleared in the affected scope record, and the status information of unmet preconditions is output, so that subsequent effective rulings can directly identify and enter the waiting state during the judgment stage; if the critical gap is completed and the evidence is complete, the critical gap clearing status is written into the affected scope record, and the status information of met preconditions is output, allowing subsequent steps to enter the adjudicable state.

[0050] Furthermore, during subsequent execution, if the intelligent database receives another anomaly or inspection record similar to the completed gap, or if evidence shows that the handling result no longer meets the requirements, the intelligent database will restore the gap status from completed to incomplete, record the rebound time and trigger source, and simultaneously re-include it in the gap list and generate a new handling action item. For gaps with a high number of rebounds or those that recur within a short period, the intelligent database will include them in high-risk statistics for subsequent step determination, prompting collaborative management to prioritize recurring issues and preventing similar issues from being repeatedly bypassed in multi-party collaboration.

[0051] It should be noted that when the action involves suspending, rescheduling, allocating resources, or adjusting space occupancy, the responsible party's response should simultaneously update the status fields related to that object. For example, the process status should change from pending to suspended, the equipment status from available to occupied or under maintenance, and the work surface status from parallelizable to restricted parallelizable. The intelligent database ensures that subsequent queries and scope expansions reflect the latest facts through these status field updates, thereby providing accurate input for subsequent effective rulings and avoiding misjudgments or duplicate assignments due to outdated status information.

[0052] Furthermore, the intelligent database links and archives gap items, handling action items, dispatched objects, receipt records, and evidence ledger records by object unique number and affected scope record, so that any handling action can be traced back to why it occurred, who is responsible, when it was dispatched, how it was executed, what the evidence is, whether it is closed-loop, and whether it has rebounded.

[0053] S4: After the preconditions are met, effective decisions are made regarding plans, costs, and changes, and pre-review requirements are set for decisions regarding on-site conditions.

[0054] Furthermore, when the affected scope record shows that the matter involves any management dimension of planning, cost, or change, the triggering and execution process for an effective ruling category is initiated. The discussion scope of effective ruling category decisions is strictly limited to the object list, relationship list, and evidence index list included in the affected scope record. Any discussion regarding the effectiveness of plan adjustments, cost processing, or changes should be based on the unique object number within this scope for correlation retrieval and verification, and expansion or reduction outside this scope is not allowed. By fixing the discussion scope to the affected scope record already formed in the intelligent database, it ensures that different participating parties use the same scope caliber to make rulings on the same matter, and facilitates subsequent follow-up reconciliation and accountability based on scope.

[0055] It should be noted that before entering the adjudication discussion, the current status of the existing adjudication conclusions and gap lists for on-site handling categories is first verified. Special attention is paid to verifying whether items explicitly designated as priority closures have been completed, and whether their corresponding essential evidence has been registered and effectively linked in the evidence ledger. If the intelligent database shows that there are still incomplete priority closure items, or if the evidence ledger verification indicates that essential evidence is still missing, mismatched, or expired, the adjudication discussion will not proceed; instead, the process will enter a waiting state, and only a list of prerequisites that must be met will be output. This list of prerequisites must include at least: a list of incomplete items, the responsible party, the required types of supplementary evidence, the completion deadline, and the criteria for resuming adjudication discussions upon completion. The waiting status and the list of prerequisites are written into the intelligent database for continuous tracking until the prerequisites are met before entering the adjudication discussion, avoiding delays, increased costs, or changes to the adjudication when basic on-site conditions are not met.

[0056] Furthermore, once the intelligent database indicates that priority closed-loop matters have been completed and the evidence is complete, the process proceeds to adjudication discussion. However, before a ruling is reached, it is necessary to determine whether the proposed ruling action will change the on-site conditions, thus requiring another on-site-level handling verification. This determination is based on the subsequent actions that trigger review, clearly recorded in the on-site handling category ruling conclusions. Examples include the use of alternative materials or processes, rearrangement of key process sequences, addition of key equipment or key teams, changes in work windows leading to changes in parallel operation relationships, and adjustments to the work area occupancy boundaries. If the proposed ruling action includes any of the above situations, the ruling is marked as a ruling requiring review during the judgment stage, and the categories and scope of verification required for review are pre-registered in the intelligent database. This ensures that on-site handling verification is triggered within a predetermined scope after the ruling takes effect, rather than relying on ad hoc communication or verbal reminders.

[0057] It should be noted that when the affected scope involves the planning dimension, the decision-making process is initiated in the planning branch. The decision-making input for the planning branch includes at least: a list of processes and tasks within the affected scope, the planned start and finish times for each process, pre- and post-process dependencies, critical path attributes, job surface occupancy and parallel constraints, available time windows for personnel, shifts, and equipment, and the latest object status updates in the intelligent database (e.g., whether processes are paused, equipment is occupied, and whether parallelism is restricted on job surfaces). During decision-making, the planning branch must at least: identify the affected critical path segments and preconditions; determine whether task order, window periods, task splitting, or merging needs to be adjusted; verify whether parallel operations still meet job surface and safety constraints; and, if necessary, specify temporary pause and recovery conditions. The planning branch output is written to the intelligent database and must at least specify: the adjusted plan arrangement, the unique IDs of the affected processes and tasks, the adjusted time windows, a description of dependency changes, and synchronization requirements related to resource and job surface occupancy, enabling subsequent execution to proceed accordingly and verification within the intelligent database.

[0058] Furthermore, when the affected scope involves cost dimensions, the decision is made through a cost branch. The cost branch's decision inputs include at least: related list items, visa matters, material and equipment usage records, process completion receipts, and approval or signature records related to cost confirmation within the affected scope. During the decision-making process, the cost branch must at least: determine whether the measurement caliber and pricing basis are consistent; determine the cost attribution boundary caused by rework, re-inspection, or additional resources; clarify the supporting materials and responsible parties for disputed cost items; and clarify the handling method for provisional estimation or non-measurement and subsequent confirmation conditions for cost items requiring prior handling before confirmation. The cost branch output is written into the intelligent database, and at least the following must be clearly defined: cost item list, supporting caliber, attribution principles, required supporting evidence or signature materials, and threshold conditions, ensuring the cost processing process is traceable and verifiable.

[0059] It should be noted that when the affected scope involves a change dimension, a classification and adjudication process is initiated in the change branch. The adjudication inputs for the change branch must include at least: change item records, a list of affected objects, the relationship between the change and the process or component, approval process records, a description of the applicable scope of alternative solutions or materials, and the completion status and evidence completeness of quality and safety-related prerequisites. During adjudication, the change branch must at least: clarify whether the change requires approval before implementation; clarify the necessary confirmation process and required signature materials; when alternative materials or processes are involved, clarify the required inspection, verification, or demonstration materials and applicable scope limitations; and clarify the change's effective date and its impact on existing plans, resource allocation, and acceptance projects. The change branch outputs are written into the intelligent database, and must at least clarify: the change's effective conditions, required approvals and evidence materials, applicable scope and limitations, and the content of the object or relationship ledger that needs to be updated synchronously after the change takes effect, ensuring that the change can be continuously tracked by the intelligent database and used for subsequent expansion of the affected scope.

[0060] Furthermore, the adjudication conclusions of the three branches—planning, cost, and change—are uniformly written into the intelligent database and linked to the affected scope record. At a minimum, the list of objects involved in the adjudication, the content of the adjudication action, the threshold conditions, the responsible party, and the execution period are recorded. For adjudications identified as requiring review during the judgment stage, the review requirements are also recorded in the adjudication conclusion, including the categories and scope of verification, ensuring that the on-site verification process can be triggered based on the intelligent database record after the adjudication takes effect. If the adjudication is in a pending state, the reasons for the pending state and the list of preconditions are written into the intelligent database, along with the basis for restoring the adjudication, so that it can resume adjudication discussion once the conditions are met, ensuring the entire process is traceable and reproducible.

[0061] It should be noted that after an adjudicable conclusion is reached, the intelligent database performs a consistency check on the conclusion. This check includes at least the following: whether the scope of impact cited in the ruling is consistent; whether key evidence has been registered and is in a valid state; whether the ruling action conflicts with the latest object status in the intelligent database; whether the plan adjustment violates parallel work restrictions or permit restrictions; and whether the conditions for the change to take effect conflict with unresolved issues or missing evidence. If the check passes, the ruling is used as input for subsequent submission to take effect. If the check fails, the reasons for the failure and the required supplementary information are written into the intelligent database, and corrections or supplementation are requested to ensure that the ruling entering the submission stage is enforceable and verifiable.

[0062] S5: Once the adjudication meets the threshold, it becomes effective and the ledger is updated synchronously. Verification is triggered according to the review requirements, and the entire chain of output reconciliation materials is replayed when needed.

[0063] Furthermore, once any branch of planning, cost, or change results in an adjudicable conclusion, the intelligent database uses the affected scope records bound to that conclusion as the submission boundary to conduct a final verification of the preconditions for effective submission. The verification includes at least the following: priority closed-loop items have been completed and their corresponding evidence is complete and valid in the evidence ledger; the threshold conditions listed in the adjudication conclusion have been met, such as necessary confirmation records, signature records, or approval records being registered and correctly associated with the object's unique number; and the process dependencies, work area occupancy restrictions, personnel qualifications, and equipment availability involved in the adjudication conclusion are consistent with and do not conflict with the latest status of the intelligent database. If the verification passes, the adjudication conclusion is determined as an object eligible for effective submission; if the verification fails, the intelligent database writes the reason for the failure and the required supplementary content into the record and keeps it in a pending submission state until the supplementary content is completed before proceeding with submission.

[0064] It should be noted that for submissions that are eligible for effectiveness, the intelligent database generates an effectiveness record through append-based logging, and links this record with records of the affected scope, a list of objects involved in the ruling, an evidence index list, and proof of fulfillment of threshold conditions. The effectiveness record must include at least the effective date, scope of effectiveness, a summary of the effective content, the responsible party, the execution period, and key constraints for subsequent verification. For effectiveness records involving plan adjustments, the adjusted plan time window and changes in dependencies should also be recorded simultaneously; for effectiveness records involving cost processing, the basis for the calculation and the boundary of cost attribution should also be recorded simultaneously; for effectiveness records involving changes, the applicable scope restrictions, necessary verification or review requirements, and object relationship information that needs to be updated simultaneously should also be recorded simultaneously. Through these recording methods, it is ensured that after effectiveness, anyone can trace back to the intelligent database when it took effect, its basis, its scope, and its constraints.

[0065] Furthermore, after the ruling takes effect, the intelligent database synchronously updates the object ledger and relationship ledger based on the effective record content, ensuring that subsequent queries and the expansion of the affected scope reflect the latest facts. For planned adjustments, the system updates the planned start and completion times, status fields, and necessary dependencies for processes or tasks; for resource allocation, it updates the occupancy time windows, availability status, and work surface occupancy relationships for personnel teams and equipment; for material or process substitutions, it updates the correspondence between material batches and usage locations, inspection status constraints, and applicable scope limitations; and for changes taking effect, it updates the status of the change, approval completion markers, and association with list measurement or acceptance items. All of the above synchronous updates use the object's unique number as the association basis and retain status traces before and after the update to avoid inconsistencies in subsequent judgments and reconciliations due to status lag.

[0066] It should be noted that when an award is identified as potentially altering site conditions during the adjudication phase, and the category and scope of review are clearly recorded in the award conclusion, the intelligent database automatically triggers the review process after the award takes effect. The triggering method is as follows: a new record is generated in the intelligent database, its category is set to site condition review, and its associated objects are limited to the list of review objects registered in the award conclusion. Simultaneously, the award's effective record is automatically referenced as the trigger source. The key points of the review process include at least: whether the required inspection or review evidence for alternative materials or processes has been supplemented; whether the parallel restrictions and permitting conditions for work surfaces are still met after process rearrangement; whether personnel qualifications and equipment inspections still meet requirements after additional resources; and whether space occupancy conflicts have been eliminated or effectively controlled after work window adjustments. The review conclusion is written into the intelligent database and bound to the effective record to prove that site conditions have been verified and met as required after the award takes effect, or, if not, to record the reasons for non-compliance and the necessary remedial measures.

[0067] Furthermore, if the review conclusion indicates that the on-site conditions are not met, the intelligent database marks the effective record as having unmet requirements and generates corresponding handling requirements. These requirements include a list of unmet requirements, the responsible party, remedial measures, types of supplementary evidence, and a completion deadline. For unmet requirements involving safety or quality baseline requirements, the intelligent database simultaneously generates restrictive status information, such as restricting the continuation of related processes, restricting parallel operations, or restricting the continued use of alternative materials. This restrictive status is written to the status field of the object ledger to ensure that subsequent execution does not bypass the review failure conclusion. After the remedial handling is completed and a receipt and evidence are generated, a review item record is generated again for verification until the review is passed. Once passed, the restrictive status is removed and the effective record's satisfaction status is updated.

[0068] It should be noted that when reconciliation materials are required in scenarios such as settlement, auditing, claims, dispute resolution, or internal review, the scope of reconciliation playback should be determined by using the affected scope record or the unique object number as the retrieval anchor. The scope of reconciliation playback should at least cover: event records, affected scope records, on-site handling classification and gap list, gap handling actions and receipt records, evidence ledger registration records, planned cost change rulings, effective records, object status and relationship update records, and review item records and review conclusions. By limiting the playback scope to the scope and object number links already fixed in the intelligent database, the reconciliation materials are guaranteed to be repeatable and verifiable.

[0069] When the intelligent database outputs reconciliation materials according to the scope of reconciliation playback, it should at least include: the time and source of the event, a list of involved objects and their locations, the basis for the expansion path of the affected scope, a list of key evidence and its source and formation time, a gap list and the closed-loop process, the process of forming the ruling and proof of meeting the threshold conditions, the effective time and scope of the ruling, records of changes in the status and relationships of objects after the ruling takes effect, the review conclusion and the basis for the review, and the remedial handling chain in case of non-compliance or backlash. Each key conclusion in the output materials should be able to be located to the object number and evidence number in the intelligent database, so that third parties can review why the ruling was made, what the basis is, whether it is closed-loop, and whether the review is passed without relying on verbal explanations, thereby supporting the traceability, verifiability, and reconciliation of multi-dimensional collaborative management.

[0070] To ensure data consistency throughout long-term operation, the intelligent database maintains append traces and version relationship registration for key table records. Updates to the object ledger, relationship ledger, and evidence ledger retain the differences before and after the update and bind the update source, enabling subsequent reconciliations to distinguish the factual status at different points in time. For situations affecting verifiability, such as missing evidence, incorrect object associations, or expired relationships, the intelligent database simultaneously outputs missing item prompts and key registration points that need to be supplemented when generating reconciliation materials. This ensures that collaborative management not only reaches conclusions but also clearly identifies the data foundation upon which those conclusions are based and their completeness.

[0071] Example 2, one embodiment of the present invention, provides a smart database-driven multi-dimensional collaborative management method for construction sites. To verify the beneficial effects of the present invention, scientific demonstration is carried out through economic benefit calculation and simulation experiments.

[0072] First, the basement and main structure construction phases of a certain urban complex project were selected as the verification scenario. The site simultaneously involved high-frequency collaborative tasks such as concrete pouring, tower crane hoisting, edge protection, high-altitude work permits, material batch substitution, adjustments to rainy season construction windows, and verification of visa measurements. The project's construction data was run in parallel using two methods: one was a comparative technique (a traditional approach relying on decentralized project management software, group communication, and manual report compilation), and the other was the method of this invention. Data sources included: work process and task plans, work area occupancy restrictions, shift scheduling and qualification validity periods, equipment availability and inspection records, material batch arrival and inspection records, inspection hazard and quality defect records, approval and signature records, and registration information for video or report-based evidence.

[0073] During implementation, the database first establishes an engineering entity ledger, dependency and constraint relationship ledger, and evidence ledger. Six typical items, A-F, are then entered sequentially as test objects. Each entry includes information such as the time of occurrence, involved parties, location range, responsible party, and existing evidence registration. Subsequently, based on pre-registered process dependencies, work area occupancy and parallel restrictions, material batch and usage location correspondence, equipment and work team usage relationship, and change and measurement / approval correspondence, the database automatically expands the affected scope and solidifies it as the sole basis for subsequent processing of the item, ensuring that all parties involved collaborate within the same scope.

[0074] Once the affected area is solidified, on-site handling classification and adjudication are triggered: for quality-related matters, the status of material inspection, re-inspection requirements, and acceptance correlation are verified; for safety-related matters, permits, edge protection, parallel operation restrictions, and personnel qualifications are verified; for resource-related matters, equipment occupancy, shift scheduling conflicts, and the feasibility of alternative resources are verified. The classification and adjudication outputs a gap list and evidence requirements, clearly defining the responsible party and completion deadline, while also marking items that must be prioritized for closure. Then, handling actions are dispatched according to the gap list. After the responsible party completes re-inspection, supplementary certification, rectification, allocation, or staggered work, the receipt and evidence registration are written back to the database. The system updates the gap closure status accordingly and forms verifiable preconditions.

[0075] Once the database indicates that the preconditions are met, the effective adjudication for planning, cost, and changes proceeds: for example, adjudication for planning adjustments to the rainy season window, adjudication for changes related to material substitution, and cost adjudication for differences in visa measurement standards. During the adjudication formation stage, it is simultaneously determined whether there are any elements that could change on-site conditions (such as the activation of alternative materials, rearrangement of key processes, adjustment of key equipment / teams, or changes in parallel relationships due to changes in work windows). If so, verification requirements and scope are pre-defined in the adjudication conclusion. Finally, when the adjudication meets the threshold conditions (approval, confirmation, complete evidence, etc.), it becomes effective and the ledger is updated synchronously. Adjudications with pre-defined verification requirements automatically trigger on-site verification, and remedial actions are taken when necessary. In settlement or dispute scenarios, the process of replaying the events, scope, evidence, actions, adjudication, effectiveness, and verification chain from the database is reviewed, and reconciliation materials are output. Six test subjects were statistically analyzed under two different methods to verify the advantages of this invention in terms of scope consistency, closed-loop gating, effective adjudication, and reconciliation playback.

[0076] Table 1 Experimental Data

[0077]

[0078] As can be seen from the time taken to expand the affected scope, the present invention is significantly slower than the comparative technology in all six test subjects (e.g., 9 seconds for subject F versus 40 seconds, and 18 seconds for subject E versus 70 seconds). This indicates that by automatically retrieving and solidifying the scope based on dependency constraints in the database, the time consumed by traditional methods relying on multi-party communication and manual boundary delineation is reduced. This directly benefits the rapid handling of high-frequency on-site matters, especially in time-sensitive scenarios such as rainy season window adjustments and conflicts caused by tower crane maintenance. Furthermore, regarding the coverage rate of affected object identification, the present invention achieves 92%–97%, while the comparative technology achieves 73%–82%. This demonstrates that the scope expansion is not only faster but also more complete, reducing secondary rework and repeated collaboration caused by missing related processes, parallel work restrictions, or associated acceptance points.

[0079] In terms of evidence, the present invention generally improves the required evidence completeness rate by approximately 25-35 percentage points (e.g., 92% for object A compared to 63%, and 95% for object C compared to 66%). This difference reflects that the present invention binds evidence registration with a gap list and establishes a precondition based on the gap closure state, thus suppressing the traditional shortcomings of proceeding with incomplete evidence. This also explains the overall reduction in the total time required for gap closure (e.g., 12 hours for object C compared to 20 hours, and 10.5 hours for object A compared to 18 hours), because gaps are itemized, responsibilities are clearly defined, and receipts can be checked immediately after being entered into the database, reducing the cycle of repeated confirmation and supplementary materials.

[0080] Regarding decision quality, the efficiency of this invention in submitting decisions is significantly higher than that of the comparative technology (e.g., 82% vs. 47% for object E, and 86% vs. 52% for object B). This indicates that by using pre-condition gating and consistency verification before formulating plans, costs, and change decisions, the probability of submissions being rejected is significantly reduced, thus improving the first-time decision-making rate. Meanwhile, the review trigger hit rate shows that this invention has higher review effectiveness for decisions that change on-site conditions (e.g., 90% vs. 45% for object A, and 92% vs. 48% for object C). This indicates that pre-defined verification requirements can move issues of non-compliance with constraints discovered after changes to a controllable verification process, avoiding missed detections caused by relying on experience-based spot checks in traditional methods.

[0081] The differences in reconciliation and dispute dimensions are even more pronounced: the preparation time for reconciliation materials using this invention is significantly reduced (e.g., 18 minutes for object F versus 140 minutes for object C, 30 minutes versus 110 minutes), and the number of disputed items is significantly reduced (1 item for object F versus 7 items, 1 item for object A versus 5 items). This indicates that by ensuring the effectiveness of record keeping, synchronous updating of ledgers, and link playback, verifiable materials can be quickly provided, reducing repeated reconciliations caused by disputes over standards and missing evidence. Finally, the cumulative on-site downtime is significantly reduced for most objects (e.g., 2 hours for object A versus 6.5 hours for object C, 3 hours versus 7.5 hours), demonstrating that this invention reduces conservative waiting and passive downtime caused by uncertainty through faster scope confirmation, evidence gating, and closed-loop processing. In summary, the data proves that this invention achieves systematic improvements in scope consistency, evidence verifiability, gap closure efficiency, submittable and reviewable adjudication, and reconciliation playback, making it able to compensate for the shortcomings of existing technologies in simultaneously achieving collaborative efficiency and audit verifiability, demonstrating outstanding practical value and innovative advantages.

[0082] Example 3, an embodiment of the present invention, provides an intelligent database-driven multi-dimensional collaborative management system for construction sites, including a ledger database creation module, an on-site handling closed-loop module, and an effective adjudication module.

[0083] The ledger building module is used to establish ledgers of objects, relationships, and evidence in the intelligent database, and automatically expands and solidifies the affected scope after the items are entered into the database; the on-site handling closed-loop module is used to complete the handling decisions and gap management of quality, safety, and resources within the affected scope, dispatch handling actions, enter receipts into the database, and form verifiable closed-loop preconditions; the effective decision module is used to form plan, cost, and change decisions after the preconditions are met and leave a record of their effectiveness, trigger on-site verification according to preset requirements, and replay the entire chain of output reconciliation materials when needed.

[0084] If a function is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this invention, or the part that contributes to the prior art, or a part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this invention. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0085] The logic and / or steps represented in the flowchart or otherwise described herein, for example, can be considered as a sequenced list of executable instructions for implementing logical functions, and can be embodied in any computer-readable medium for use by, or in conjunction with, an instruction execution system, apparatus, or device (such as a computer-based system, a processor-including system, or other system that can fetch and execute instructions from, an instruction execution system, apparatus, or device). For the purposes of this specification, "computer-readable medium" can be any means that can contain, store, communicate, propagate, or transmit programs for use by, or in conjunction with, an instruction execution system, apparatus, or device.

[0086] More specific examples (a non-exhaustive list) of computer-readable media include: electrical connections (electronic devices) having one or more wires, portable computer disk drives (magnetic devices), random access memory (RAM), read-only memory (ROM), erasable and editable read-only memory (EPROM or flash memory), fiber optic devices, and portable optical disc read-only memory (CDROM). Furthermore, computer-readable media can even be paper or other suitable media on which programs can be printed, because programs can be obtained electronically, for example, by optically scanning the paper or other media, followed by editing, interpreting, or otherwise processing as necessary, and then stored in computer memory.

[0087] It should be understood that various parts of the present invention can be implemented using hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented using software or firmware stored in memory and executed by a suitable instruction execution system. For example, if implemented in hardware, as in another embodiment, it can be implemented using any one or a combination of the following techniques known in the art: discrete logic circuits having logic gates for implementing logical functions on data signals, application-specific integrated circuits (ASICs) having suitable combinational logic gates, programmable gate arrays (PGAs), field-programmable gate arrays (FPGAs), etc. 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.

[0088] 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 smart database-driven construction site multidimensional collaborative management method, characterized in that, include: In the intelligent database, an object, relationship and evidence ledger is built. After an item is entered into the database, the scope of the impact is automatically expanded and solidified as a unified basis. After an item is entered into the database, its affected scope is automatically expanded and solidified into a unified basis. This includes using the unique number of the object involved in the item record as the starting point, sequentially searching for the dependencies between processes to determine the preceding and subsequent processes, searching for the relationship between work surface occupancy and parallel restriction to identify conflicting work activities, searching for the relationship between material batches and inspection and usage locations to locate affected components and acceptance points, and searching for the relationship between equipment and work groups and work surface usage to identify the impact of resource occupancy. If the matter involves changes or visas, the relationship between the changes and the measurement and approval processes should be retrieved to determine the affected scope and key points. De-duplication and merging of the retrieved objects and binding of evidence indexes; Based on the affected area, on-site handling decisions are classified and adjudicated according to quality, safety, and resources, generating a gap list and evidence requirements; The on-site disposal classification and adjudication based on quality, safety, and resources, which is carried out within the affected area, includes determining whether to initiate disposal based on key object elements, construction window status, completeness of evidence, risk statistics results, and conflicts between parallel constraints of resources and work surfaces. Once initiated, disposal conclusions are formed based on quality, safety, and resources, and a gap list and evidence requirements are generated simultaneously, clarifying the responsible parties, completion deadlines, and priority items for closure. Dispatch and process actions according to the gap list and return receipts to the database, and update the gap closure status to form the prerequisite conditions; The process of dispatching and recording disposal actions based on the gap list includes converting each item in the gap list into disposal action items, sorting them by dependency, and dispatching the disposal actions to the corresponding units or positions according to the responsible entities registered in the object ledger. After the responsible party performs the task, it writes the execution time, the execution position, the execution result, and the evidence registration information corresponding to the execution result into the intelligent database to form a receipt; The intelligent database then updates the gap status based on the content of the receipt and the verification results of the evidence ledger, and performs separate verification on matters that must be prioritized for closure, outputting the status of whether the preconditions for the adjudication are met or not. Once the preconditions are met, effective decisions are made regarding plans, costs, and changes, and pre-review requirements are set for decisions concerning on-site conditions. After the preconditions are met, an effective ruling is made on the plan, cost, and change. The pre-review requirements for the ruling on the site conditions include verifying whether the priority closed-loop items have been completed and whether the necessary evidence is complete before the effective ruling is made. When there are outstanding items or missing evidence, a list of preconditions is generated and the process remains pending until the preconditions are met, at which point the process proceeds to the classification and adjudication of plans, costs, and changes. During the adjudication process, it is determined whether the proposed adjudication involves changes to the on-site conditions. If so, the categories and scope of verification that need to be checked are recorded in advance in the adjudication conclusion. Once the ruling meets the threshold, it becomes effective and the ledger is updated synchronously. Verification is triggered according to the review requirements, and the entire chain of output reconciliation materials is replayed when necessary.

2. The intelligent database-driven multi-dimensional collaborative management method for construction sites as described in claim 1, characterized in that: The construction of an object, relationship and evidence ledger in the intelligent database includes, when establishing the object ledger, registering and filing the participating units, personnel teams, machinery and equipment, material batches, component parts, work areas, process tasks, acceptance items and change orders respectively, and generating and fixing a unique number for each object; Write the responsible party, location, status, and effective time of the object into the intelligent database.

3. The intelligent database-driven multi-dimensional collaborative management method for construction sites as described in claim 2, characterized in that: The decision becomes effective upon meeting the threshold and the ledger is updated synchronously. This includes creating an effective record by adding additional traces after the decision meets the threshold and synchronously updating the status and dependencies of the object ledger and the relationship ledger. When the effective record includes on-site verification requirements in advance, the corresponding verification items will be automatically generated and the verification scope will be limited after the record becomes effective. If the verification fails, remedial measures will be generated and a restrictive status will be written to the relevant process or work surface until the remediation is completed. In settlement, audit, or dispute scenarios, the entire process of recording the entry of matters into the database, expansion of the scope of impact, handling and closure of gaps, formation and effectiveness of rulings, and verification and remediation is replayed using the unique number of the affected scope or object as the anchor point. The output includes reconciliation materials containing evidence indexes and chains of responsibility.

4. A system employing the intelligent database-driven multi-dimensional collaborative management method for construction sites as described in any one of claims 1 to 3, characterized in that: This includes a ledger and database creation module, an on-site handling closed-loop module, and an effective ruling module; The ledger building module is used to establish ledgers of objects, relationships, and evidence in the intelligent database, and automatically expand and solidify the scope of impact after the items are entered into the database; The on-site handling closed-loop module is used to complete the handling decisions and gap management of quality, safety and resources within the affected area, dispatch handling actions, store receipts and form verifiable closed-loop prerequisites; The effective decision module is used to generate and record effective decisions on plans, costs, and changes after the preconditions are met, trigger on-site verification according to preset requirements, and replay the entire chain of output reconciliation materials when needed.

5. A computer device comprising a memory and a processor, wherein the memory stores a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the intelligent database-driven multi-dimensional collaborative management method for construction sites as described in any one of claims 1 to 3.

6. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the intelligent database-driven multi-dimensional collaborative management method for construction sites as described in any one of claims 1 to 3.

Images