Digital management system based on city update project propulsion node

Abstract

The invention relates to the technical field of city management, in particular to a digital management system based on city update project propulsion nodes, which comprises a node activation joint control module, a state cross check module, a path structure adjustment module, a field crossing retrieval module and a risk identification module. In the method, a state identification mechanism is established by combining field cross analysis in task state identification, behavior deviation identification is realized by comparing a node state with a task completion condition, and a stage process number and a responsibility role field are introduced during path archiving to construct a path structure. When the field information appears among a plurality of discontinuous nodes and process stages and task attributions are inconsistent, marking the field information as a path-crossing field, identifying field risk nodes and forming a risk prompt identifier; and the effects of improving the node task execution consistency, the document filing path clearness and the field information abnormity identification capability in the city updating project are achieved.

Description

Technical Field

[0001] This invention relates to the field of urban management technology, and in particular to a digital management system based on the progress nodes of urban renewal projects. Background Technology

[0002] The field of urban management technology involves the organization, coordination, and regulation of urban space, resources, facilities, and operational processes. Core aspects include the supervision of urban planning implementation, infrastructure operation and maintenance management, progress control and information coordination of urban project construction, collection and analysis of urban operational data, and node management in the urban renewal process. This field aims to support the efficient execution of various urban management behaviors through information technology, achieving urban space optimization, compliant project implementation, and scientific allocation of public resources. Traditional urban renewal project management refers to the systematic process control of key nodes in urban renewal construction, including planning, status monitoring, document collection, and data acquisition. Traditional urban renewal project node management relies on manual submission of schedules, tracking of project node status via telephone or offline meetings, manual organization of paper or scattered key documents, and periodic manual collection and summarization of important data items at each node to achieve project progress control and information recording.

[0003] Traditional project management relies on manual completion of plans, offline communication to confirm node status, manual organization of paper documents, and regular summarization of key data. In scenarios where node status changes frequently, document ownership is unclear, and task information is distributed across nodes, information misalignment and management oversights are likely to occur. In particular, when the task completion status is inconsistent with the node labeling results, the lack of an automatic verification mechanism can lead to node execution deviations going undetected for a long time. At the same time, the lack of clear responsibilities and stage procedures in document path organization makes it difficult to archive documents efficiently. When field information is interspersed among multiple non-continuous nodes, it is also difficult to achieve traceability and early warning, affecting the continuity and consistency of project management. Summary of the Invention

[0004] To address the technical problems inherent in existing technologies, such as frequent changes in node status, unclear document ownership, and task information distribution across nodes, which easily lead to information misalignment and management oversights, especially when task completion status differs from node annotation results, the lack of an automatic verification mechanism can cause node execution deviations to go undetected for extended periods. Furthermore, the lack of clear responsibilities and stages in document path organization results in inefficient document archiving, and the difficulty in tracing and issuing early warnings when field information is interspersed across multiple non-continuous nodes, thus affecting the continuity and consistency of project management, this invention provides a digital management system based on urban renewal project progress nodes. The technical solution is as follows: On the one hand, a digital management system based on the progress nodes of urban renewal projects is provided, the system including: The node activation and control module obtains the node task type field set in the urban renewal project, extracts the resource type list corresponding to the task type, determines whether the attendance status field is confirmed to be present, and generates a node activation status identifier. The status cross-verification module compares the status field with the task completion field based on the nodes in the node activation status identifier that are in the active state. It determines that nodes whose status field is completed but whose task identifier is not completed are conflicting nodes and generates a status behavior consistency label list. The path structure adjustment module calls the document corresponding to the state to be verified in the state behavior consistency label list, obtains the generation node process number field and the responsibility role identifier field in the document, uses the process number field as a stage marker and the role field as a responsibility attribution marker, and generates the document archive path segment content. The field traversal retrieval module, based on the path pending status documents recorded in the document archive path segment content, binds field values ​​and retrieves the occurrence positions within the project node range, filters field values ​​in non-contiguous nodes, and generates field node distribution recognition results.

[0005] As a further embodiment of the present invention, the node activation status identifier includes an activation probability marker, a time sequence verification marker, and a status evaluation label; the status behavior consistency label list includes a conflict status marker, a time difference threshold judgment result, and a list of nodes to be verified; the document archive path segment content includes a path structure matching result, an undefined path marker, and a responsibility attribution classification marker; and the field node distribution identification result includes a field process difference classification, a task type attribution deviation marker, and a path traversal type marker.

[0006] As a further aspect of the present invention, the node activation and control module includes: The task type extraction submodule obtains the node task type field set in the urban renewal project, calls multiple task type parameters in the node task type field, identifies the correspondence between the parameter mapping set set between task type and resource type, divides the successfully matched resource type set into list items, extracts and classifies the resource type items in the list with unique identifiers, and generates a resource type list. The resource list integration submodule calls the presence status field, registration presence time field and device integrity identifier field of the corresponding device according to the resource type list. It compares the device code in the device integrity identifier field with the resource item in the resource list, and establishes a binding relationship between the device registration record time in the registration presence time field and the resource item to generate a device registration corresponding set. The status judgment submodule calls the presence identification status field according to the device registration corresponding set, selects the device item whose field value is confirmed to be present, extracts the bound registration presence time field value, and performs an order judgment on the registration presence time field value and the node pre-start time field value according to the node plan setting. If the registration presence time field value is earlier than the node pre-start time field value, the record status is activated; otherwise, the record status is frozen, and a node availability judgment result is generated. The activation status submodule summarizes the node record status values ​​based on the node availability determination value, calculates the ratio of the number of active and frozen states, compares the ratio result with the activation threshold set in the node status field, and sets the node status field to active or frozen state according to the comparison result, generating a node activation status identifier.

[0007] As a further aspect of the present invention, the state cross-verification module includes: The conflict node identification submodule, based on the nodes in the active state identifier, calls the status field and the task completion identifier field, matches and marks nodes whose status field is completed and whose corresponding task identifier field is incomplete, classifies the nodes that meet the conditions as conflict record items, records the unique identifier code of the node and the corresponding field combination value, and generates a conflict node identifier set. The period offset determination submodule extracts the corresponding status change time and task submission time field values ​​from each item according to the conflict node identifier set, calculates the time difference between the status change time and the task submission time, compares the calculated interval value with the node offset period threshold, and if the time interval is greater than the node offset period threshold, the node is marked as a pending verification state and a node time offset state is generated. The consistency labeling submodule summarizes the unique codes of nodes marked as pending verification based on the node time offset status, adds annotations to the conflict field combination values ​​of multiple types of nodes, binds the annotation content with the node information, and generates a status behavior consistency label list.

[0008] As a further aspect of the present invention, the path structure adjustment module includes: The field extraction submodule calls the document set corresponding to the status to be verified in the status behavior consistency label list, locates and extracts the generation node process number field and the responsibility role identifier field in the content of each document, identifies the stage number of the process number field and the attribution code of the role field, and classifies the two types of fields into the structured field set to obtain the basic data of field combination; The path segment construction submodule, based on the field combination basic data, places the responsibility role identifier field in the document first and the generated node process number field in the second position, concatenates the two field values ​​in sequence to form a path segment marker string, and embeds it into the archive path structure of the corresponding document, forming a sequential superposition structure of the path segment content, and generating a document archive path combination. The path status labeling submodule compares the path segment string with the index set of the real-time path segment content structure based on the document archive path combination. If no match is found, an undefined marker is inserted into the path segment, and the path pending status identifier is recorded for the document. The path combination content and status identifier information of all documents are integrated to generate the document archive path segment content.

[0009] As a further solution of the present invention, the document set corresponding to the state to be verified in the state behavior consistency label list is called, and the generation node process number field and the responsibility role identifier field in the content of each document are located and extracted. The stage number of the process number field and the belonging code of the role field are identified, and the two types of fields are respectively classified into the structured field set to obtain the basic data of field combination. The process of identifying the stage number of the process number field is as follows: the character sequence of the generated node process number field is split according to a preset format, and the field unit including the stage number prefix is ​​identified in the split character segment. If the prefix of the field unit is consistent with the set stage identification identifier, the field unit is included in the structured field set as the stage number field. The identification process for the attribution code of the responsibility role identifier field is as follows: perform character matching operation on the responsibility role identifier field, and extract the corresponding code item as the attribution code field and incorporate it into the structured field set according to the preset role attribution mapping dictionary.

[0010] As a further aspect of the present invention, the field traversal retrieval module includes: The field location submodule extracts the field values ​​bound to each document based on the path pending status documents recorded in the document archive path segment content, sets the search conditions for the field values ​​within the project node range, traverses and matches all field contents in the node data set, records the position of the field values ​​in the node and the node number information, and generates a field node location set. The node filtering submodule sorts the node numbers of the field values ​​in the nodes according to the field node location set, identifies whether the adjacent node numbers in the sorting result are continuous, filters and retains the field values ​​with skipped node numbers, and generates a non-continuous node field set. The traversal identification submodule compares the multiple generation node process number fields bound to each field value with the non-continuous node field set to determine whether there is a difference in the process stage code, and extracts the task type parameter to which the field value belongs. If the process stage code deviation of the field value is crossed, and the difference in the task type parameter value is greater than the task type set deviation threshold, then the field value is marked as a path traversal field, and the field node distribution identification result is generated.

[0011] As a further aspect of the present invention, the process for determining the process stage coding deviation that the field value crosses is as follows: each process stage code recorded in the process number field of the multiple generation nodes bound to the field value is arranged in ascending order according to the sequence number of the process stage codes, and the difference between the first and last process stage codes is calculated as the process stage coding deviation. Read the task type field content recorded in the field information bound to the field value, and determine the task type parameter to which the field value belongs based on the standard task type code in the task type field; The task type setting deviation threshold is set as follows: based on the attribute fit level between process task types, the task type setting deviation threshold is set to the attribute deviation value between task type combination pairs that are lower than the three fit levels.

[0012] As a further aspect of the present invention, the system also includes a risk identification module: The risk identification module calls the path-crossing field in the field node distribution identification result, extracts the order of appearance of the field value in the real-time node and adjacent nodes, and determines whether the order overlaps or intersects. If there is an abnormality in the structural relationship, the real-time node status is updated to field risk pending verification, and a list of node field risk identification is generated. The node field risk identifier list includes field order anomaly types, node status update flags, and risk verification pending processing flags.

[0013] As a further aspect of the present invention, the risk identification module includes: The path order extraction submodule calls the set of fields marked as path traversal fields in the field node distribution recognition result, extracts the positional order number information of the field value in the corresponding real-time node and adjacent front and rear nodes, and combines and arranges the order numbers of the same field value in the differentiated nodes to generate the field path order arrangement result; The structural relationship determination submodule compares the field value sequence number combination in adjacent nodes with the field path order arrangement result to determine whether there is a structural relationship with overlapping or intersecting numbers. If the field value number in the preceding and following nodes is earlier than or equal to the number in the real-time node, it is marked as a structural relationship abnormal node, and a field structure abnormality identification result is generated. Based on the field structure anomaly identification results, the risk status labeling submodule updates the real-time status value of nodes marked as having abnormal structural relationships, writes the field risk pending verification status identifier into the node status field, and pairs the updated node number with the field value to generate a list of node field risk identifiers.

[0014] The beneficial effects of the technical solutions provided in the embodiments of the present invention include at least the following: By establishing a status identification mechanism through field cross-analysis in task status identification, behavioral deviations are identified by comparing node status with task completion status. Statuses awaiting verification are marked based on time sequence. When archiving paths, stage process number and responsible role fields are introduced to construct the path structure. When field information appears across multiple non-continuous nodes and the process stage and task affiliation are inconsistent, it is marked as a path-crossing field. Risk nodes are identified and risk warning labels are generated, improving the structural accuracy of information collection and the sensitivity of task status identification. Simultaneously, it enhances the risk identification and document path adjustment capabilities during node data flow, addressing the lack of linkage between task status and document affiliation in node management. This achieves the effect of improving the consistency of node task execution, the clarity of document archiving paths, and the ability to identify abnormal field information in urban renewal projects. Attached Figure Description

[0015] To more clearly illustrate the technical solutions in the embodiments of the present invention, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the accompanying 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.

[0016] Figure 1 This is a system schematic diagram of the present invention; Figure 2 This is a schematic diagram of the system framework of the present invention; Figure 3 This is a flowchart of the node activation and control module in this invention; Figure 4 This is a flowchart of the state cross-verification module in this invention; Figure 5 This is a flowchart of the path structure adjustment module in this invention; Figure 6 This is a flowchart of the field traversal retrieval module in this invention; Figure 7 This is a flowchart of the risk identification module in this invention. Detailed Implementation

[0017] The technical solution of the present invention will now be described with reference to the accompanying drawings.

[0018] In embodiments of the present invention, words such as "exemplarily," "for example," etc., are used to indicate that something is an example, illustration, or description. Any embodiment or design described as "exemplary" in the present invention should not be construed as being more preferred or advantageous than other embodiments or designs. Specifically, the use of the word "exemplary" is intended to present the concept in a concrete manner. Furthermore, in embodiments of the present invention, the meaning expressed by "and / or" can be both, or either one.

[0019] In the embodiments of this invention, the terms "image" and "picture" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning. Similarly, the terms "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing the distinction between them, they convey the same meaning.

[0020] In this embodiment of the invention, sometimes a subscript such as W1 may be written in a non-subscript form such as W1. When the difference is not emphasized, the meaning they express is the same.

[0021] To make the technical problems, technical solutions and advantages of the present invention clearer, a detailed description will be given below in conjunction with the accompanying drawings and specific embodiments.

[0022] This invention provides a digital management system based on the progress nodes of urban renewal projects, such as... Figure 1-2 The diagram shown illustrates a digital management system based on urban renewal project progress nodes. This system includes: The node activation and control module obtains the node task type field set in the urban renewal project, extracts the resource type list corresponding to the task type, and combines the on-site identification status field, the registration on-site time field, and the equipment integrity identification field to determine whether the on-site identification status field is confirmed on-site. If it is true, the registration on-site time field is compared sequentially with the node pre-start time field in the node plan setting, and the node status field is set to an activatable or frozen state to generate a node activation status identifier. The status cross-verification module compares the status field with the task completion field of the node activation status identifier in the node activation status identifier. It determines that the node with the status field of completed and the task identifier of incomplete is a conflict node. It combines the status change time and the task submission time to determine whether the time interval is greater than the node offset cycle threshold. If it is true, the status is set to pending verification and a status behavior consistency label list is generated. The path structure adjustment module calls the document corresponding to the pending status in the status behavior consistency label list, obtains the process number field and the responsibility role identifier field of the generated node in the document, uses the process number field as the stage mark and the role field as the responsibility attribution mark, and combines them in the order of role first and stage second. When the combination of the two fields cannot be included in the real-time path segment content structure, an undefined mark is inserted and the document is marked as a pending status of the path, and the document archive path segment content is generated. The field traversal retrieval module is based on the path pending status documents recorded in the document archive path segment content. After binding the field values, it retrieves the occurrence positions within the project node range, filters the field values ​​in non-contiguous nodes, and extracts the node generation process number field of the node. It judges whether there are differences in the process stages. If the field value spans multiple process stages and the task type of the field is different, the field is marked as a path traversal field, and the field node distribution recognition result is generated. The risk identification module calls the path-crossing field in the field node distribution identification result, extracts the order of the field value in the real-time node and the adjacent nodes, and judges whether the order overlaps or crosses. If there is an anomaly in the structural relationship, the real-time node status is updated to field risk pending verification, and a list of node field risk identification is generated. The node activation status identifiers include activation probability markers, time sequence verification markers, and status assessment labels. The status behavior consistency label list includes conflict status markers, time difference threshold judgment results, and a list of nodes to be verified. The document archive path segment content includes path structure matching results, undefined path markers, and responsibility attribution classification markers. The field node distribution identification results include field process difference classification, task type attribution deviation markers, and path traversal type markers. The node field risk identifier list includes field order anomaly types, node status update markers, and risk verification pending processing markers.

[0023] Specifically, such as Figure 2 , 3 As shown, the node activation and control module includes: The task type extraction submodule obtains the node task type field set in the urban renewal project, calls multiple task type parameters in the node task type field, identifies the correspondence between the parameter mapping set set between task type and resource type, divides the successfully matched resource type set into list items, extracts and classifies the resource type items in the list with unique identifiers, and generates a resource type list. The system needs to obtain a complete data structure containing task nodes from the urban renewal project management platform or engineering progress control equipment. The task type field records the construction task category related to each node, such as "site clearing," "foundation construction," "structural capping," "equipment installation," and "interior decoration." The system can parse the task node information table one by one, perform field matching and identification based on the task type field, and construct a task keyword mapping table to match different categories of tasks with their corresponding resource types. For example, the "structural capping" task requires the configuration of resources such as formwork steel, concrete, and pump trucks, while the "interior decoration" task requires the association of resources such as tiles, paint, lighting equipment, and construction personnel. During the identification process, natural language keyword extraction technology is used to extract keywords from the task fields and perform traversal matching in the mapping rules set by the system to find all resource items that match the task. Successfully matched resource items are recorded in the form of a resource list, with each resource having a unique identifier, such as material number, resource code, and supply batch number. The system classifies the matched resource items into resource list items under that task node and identifies and categorizes them through barcode recognition or material code extraction to form a resource type list.

[0024] The resource list integration submodule calls the presence status field, registration presence time field and equipment integrity field of the corresponding device according to the resource type list. It compares the corresponding device code in the equipment integrity identifier field with the resource item in the resource list, and establishes a binding relationship between the device registration record time in the registration presence time field and the resource item to generate the corresponding set of device registration. The system calls the arrival status field, registration arrival time field, and equipment integrity identifier field of the corresponding device at the node. During execution, it first loads the device information table associated with the node. This table records the planned deployment equipment items and their related status fields, including whether each device has been registered on-site, whether the registration time is clear, and whether the device status is complete and usable. The system binds the resource list and the equipment table at the field level, establishing a mapping relationship through device number, device name, or resource code. In the data structure, each resource list item is matched one-to-one with the device status. The system determines whether a device is "confirmed to be on-site" based on the arrival status field value. If the field value is "yes" or "confirmed," the system determines that the device is registered. The registration time field records the actual arrival time of the device, and the system records this field value under the corresponding resource item in the resource list. The equipment integrity identifier field records whether the current status of the device meets the usage standards, such as "intact," "minor damage," or "requires maintenance." The system integrates these fields to generate a registration data set where resources and device arrival status are bound one-to-one, resulting in the corresponding equipment registration set.

[0025] The status judgment submodule calls the on-site identification status field according to the corresponding set of equipment registration, selects the equipment item whose field value is confirmed to be on-site, extracts the bound registration on-site time field value, and performs an order judgment on the registration on-site time field value and the node pre-start time field value according to the node plan setting. If the registration on-site time field value is earlier than the node pre-start time field value, the record status is activated; otherwise, the record status is frozen, and a node availability judgment result is generated. The system calls the on-site status field and filters devices with a field value of "Confirmed On-site". The system identifies the status of each device record. Records with status fields marked as "Registered", "On-site Confirmed", or "Verified" will be filtered and enter the next process. The registration on-site time field is extracted as a reference time node and compared with the "Pre-start Time" field in the node task plan setting to determine the time order. The pre-start time comes from the node's project schedule or scheduling plan table and is a timestamp composed of year-month-day plus hour and minute. By comparing whether the device registration time is earlier than the pre-start time, it can be determined whether the device is ready for early deployment. If the device registration time is earlier than the preset time, the system will record the device status as "Active", otherwise it will be marked as "Frozen". This judgment process does not rely on complex algorithms, but only on basic time order logic to generate the node availability judgment result.

[0026] The activation status submodule summarizes the node record status values ​​based on the node availability judgment value, calculates the ratio of the number of active and frozen states, compares the ratio result with the activation threshold set in the node status field, sets the node status field to active or frozen state according to the comparison result, and generates a node activation status identifier. The system summarizes the node status values, classifying and statistically analyzing the active and frozen states of nodes, and counting their respective quantities. For example, in a city renewal project with 20 nodes, 14 are classified as "active" and 6 as "frozen." The system compares the proportion of nodes in these two states to determine the overall availability of nodes. It then compares the results against a pre-defined activation threshold, set by project administrators at the initial system configuration stage. This threshold, such as 0.6, 0.7, or 0.75, represents the percentage of nodes that must be active for the entire node group to be considered ready. The system compares the set value with the actual statistical value. If the active percentage equals or exceeds the threshold, the node group is marked as "active"; otherwise, it is marked as "frozen." The activation status is recorded in the system as structured data and synchronized to the task scheduling module for determining whether a node group meets the activation conditions. In a regional renewal project, if 80% of the nodes in a section's basic construction node group are active and meet the activation threshold of 0.75, a node activation status is generated.

[0027] Specifically, such as Figure 2 , 4 As shown, the status cross-verification module includes: The conflict node identification submodule, based on the nodes in the node activation status identifier that are in the active state, calls the status field and the task completion identifier field, matches and marks the nodes whose status field is completed and whose corresponding task identifier field is not completed, classifies the nodes that meet the conditions as conflict record items, records the unique identifier code of the node and the corresponding field combination value, and generates a conflict node identifier set. First, nodes marked as "activatable" are filtered from the active status set. These nodes are then used as the object set for conflict detection. The status field and task completion flag field of each node are called one by one. The status field records the current project status of the node and is set to "completed", "in progress", "not started", etc. The task completion flag field records the actual construction party's confirmation of the task progress and is set to "construction party not submitted" or "system not uploaded task results". During the matching process, the system filters out nodes whose status field is marked as "completed" but whose task completion flag field is still in the "not completed" state. This indicates that there is a risk of inconsistency in the information of the node. The system marks such nodes as conflict nodes and includes them in the conflict record item set. To ensure traceability and data accuracy, the system also needs to record the unique identifier code of each conflict node, such as "NODE-GS-0321", and combine its status field and task flag field current values ​​to form a field combination flag, set to "completed-not submitted", to generate a conflict node identifier set.

[0028] The period offset determination submodule extracts the corresponding status change time and task submission time field values ​​from each item based on the conflict node identifier set, calculates the time difference between the status change time and the task submission time, compares the calculated interval value with the node offset period threshold, and if the time interval is greater than the node offset period threshold, the node is marked as a pending verification state and a node time offset state is generated. The system extracts the status change time and task submission time fields for each node in the set. These two fields record the time when the node was updated to the "completed" status and the timestamp generated by the task submission record in the project management system, respectively. The system reads these two time values ​​one by one, parses their time format through the time field reading mechanism, and analyzes their chronological relationship by comparing the text. The node status change time is set to "2025-08-01-10:00:00" and the task submission time is set to "2025-08-04-18:00:00". The system needs to determine the interval length. Without using formulas, the two times can be broken down into year, month, day, hour, and minute units through date and time structure parsing. The total interval length is derived according to the order of the time fields. The system automatically compares the calculated time interval length with the node offset cycle threshold set in the project configuration file. The offset cycle threshold is set to 72 hours. If the calculated interval is 80 hours, it is judged as "exceeding the threshold". The system marks such nodes as "pending verification" and generates a node time offset status.

[0029] The consistency annotation submodule summarizes the unique codes of nodes marked as pending verification based on the node time offset status, adds annotations to the conflict field combination values ​​of multiple types of nodes, binds the annotation content to the node information, and generates a status behavior consistency annotation list. The system filters out the unique codes of nodes marked "Pending Verification," outputs a list of node codes and their offset status values, imports and integrates them, summarizes the node codes in order, and counts the frequently occurring field combinations, i.e., the aggregation markers for similar conflict patterns. Field combination types such as "Completed - Not Submitted" and "Task Not Uploaded - Registration Confirmed" are set. The system attaches conflicting field combination values ​​as key annotation content to each node's information. Specifically, the system creates a new "Annotation Field" column in the node information table, writes the combination values ​​as tags, and establishes a binding relationship with the node code. Different types of annotation tags can also be generated for different types of nodes, such as construction, acceptance, and equipment nodes, for classification management and subsequent review. If a batch of "Completed - Task Not Uploaded" occurrences appear in equipment nodes, they can be marked as "Equipment Consistency Anomaly," generating a status behavior consistency annotation list.

[0030] Specifically, such as Figure 2 , 5As shown, the path structure adjustment module includes: The field extraction submodule calls the document set corresponding to the status to be verified in the status behavior consistency label list, locates and extracts the generation node process number field and responsibility role identifier field in the content of each document, identifies the stage number of the process number field and the attribution code of the role field, and classifies the two types of fields into the structured field set to obtain the basic data of field combination; The system needs to iterate through the node codes marked "Pending Verification" in the consistency list and retrieve the original record documents associated with the node codes from the system storage. These documents are in JSON format or database record form and contain descriptive information about the project task nodes. The system establishes a connection between the unique node code and the document index. When reading the document content, the "Generation Node Procedure Number" and "Responsibility Role Identifier" fields must be located sequentially. The former represents the execution sequence number of the project node, such as "PZ01-001", "PZ01-002", etc., while the latter records which construction or management unit the node belongs to, such as "General Contractor - Structure" or "Supervisor - The system uses field tag name matching technology to accurately extract the values ​​of the above two fields, such as "quality" and "subcontracting - water and electricity", and then classifies and manages the extraction results. The number of the "process number" field is decomposed into stage code and sequence number. For example, "PZ01" is the stage number and "001" is the sequence number. They are then classified into the stage number set. At the same time, the text content in the "responsibility role identifier" field is mapped to the role code set. For example, "supervision unit" can be marked as "JL-001" and "construction unit" can be marked as "SG-002". After completion, the system classifies the two types of fields into structured field sets to obtain the basic data of field combination.

[0031] The path segment construction submodule is based on the field combination basic data. It puts the responsibility role identifier field in the document first and the generated node process number field in the second position. The two field values ​​are concatenated in order to form a path segment mark string, which is then embedded into the archive path structure of the corresponding document. The path segment content forms a sequential superposition structure to generate the document archive path combination. The extracted "Responsibility Role Identifier" and "Node Process Number" fields need to be combined in a preset order to construct a path segment marker string. The system sets the path segment concatenation rule as "role identifier field first, process number field second," that is, the role code is used as the main entry prefix of the path, and the node process number is used as the suffix. If the role code is set to "SG-002" and the process number is set to "PZ01-003", then the complete path segment "SG-002-PZ01-003" will be constructed. This path segment string is embedded in the archive path of the corresponding document. The path structure is based on the basic hierarchical structure of "project number / task stage / responsibility role / process node". The path can be written as "2025-URB01 / construction stage / SG-002 / SG-002-PZ01-003". The system will add this segment content to the original path to form a nested path segment structure. If the document already has multiple node records, the system will generate multiple path segments and add them in sequence to form a sequential superposition structure. The path segments are integrated and arranged according to the document's ownership order to form a document archive path combination.

[0032] The path status labeling submodule compares the path segment string with the index set of the real-time path segment content structure based on the document archive path combination. If no match is found, an undefined marker is inserted into the path segment, and the path pending status identifier is recorded for the document. The path combination content and status identifier information of all documents are integrated to generate the document archive path segment content. The generated path segment content needs to be compared one by one with the system's real-time path segment content structure index set. This index set is periodically built by the platform backend and contains registered and valid path segment structure index items. The comparison process involves matching the path segment string with the standard paths in the index set item by item. If a path segment string is found not to appear in the index, the system will automatically add an "undefined" mark to that path segment, appending the annotation "[undefined]" to the end of the path segment. The system will also add a "path pending processing" flag to the status field of the document for subsequent archiving and correction processes. The system needs to integrate the generated path segments in the document. The system combines path segments with corresponding status markers. Each record includes the document number, path segment content, whether the path segment matches, whether it is marked as undefined, and whether the overall path is valid. For example, if a document's path segment is "SG-002-PZ01-008", but the system index does not contain this record, the system will output the record as: "Document ID: DOC-0054, Path segment: SG-002-PZ01-008, Status: Undefined, Mark: Path pending processing". This allows project document controllers or data administrators to supplement or register the path and generate document archive path segment content.

[0033] Specifically, such as Figure 2 , 6 As shown, the field traversal retrieval module includes: The field location submodule extracts the field values ​​bound to each document based on the path status documents recorded in the document archive path segment content, sets the search conditions for the field values ​​within the project node range, traverses and matches all field contents in the node data set, records the position of the field value in the node and the node number information, and generates a field node location set. The system needs to identify each document record currently marked as "path pending" and extract the field values ​​of the generated but not yet mapped path segments from each document. The field values ​​mainly include the responsibility role identifier, node process number, and task key markers. After extracting the field values, the system will establish a binding relationship between the field values ​​and the document ID, set the search conditions for the field values ​​within the project node range, and set the condition to "the field value appears in the node attribute field". The system will also match whether the field value appears in fields such as "task description", "node process number", and "responsible person role code". The system will enter the project node data set and perform field-level traversal on all nodes. The field values ​​will be compared with the fields in the node table one by one through sequential scanning. If a field value match is found, the system will record the number information of the matching node and the location of the field. For example, if the field value "SG-002_PZ01-008" in the "task description" field appears in the node record with the number "ND-0045", then its position will be set as "task description field" and its number will be set as "ND-0045", generating a field node location set.

[0034] The node filtering submodule sorts the node numbers of the field values ​​in the nodes according to the field node location set, identifies whether the adjacent node numbers in the sorting result are consecutive, filters and retains field values ​​with skipped node numbers, and generates a set of non-consecutive node fields. The node numbers appearing for each field value need to be uniformly sorted according to the node numbering rules. If the format is set to "ND-0001", "ND-0002", "ND-0003", etc., then the numbers are arranged from smallest to largest according to the ordinal part. After sorting, the continuity of the node number list corresponding to the same field value is judged. The judgment criterion is whether there is a continuous structure with a natural ordinal interval of 1 between adjacent numbers. If discontinuous jumps are found between numbers, such as the field value "SG-002-PZ01-008" appearing in the numbers "ND-0021", "ND-0023", "ND-0026", then it is identified that "0022" is missing between "0021" and "0023", and "0024" and "0025" are missing between "0023" and "0026". This indicates that there is a distribution breakpoint in the node sequence for this field value. The system filters and retains such field values ​​with non-continuous number distribution characteristics to generate a set of non-continuous node fields.

[0035] The traversal identification submodule compares the multiple generation node process number fields bound to each field value based on the set of non-continuous node fields, determines whether there is a difference in the process stage code, and extracts the task type parameter to which the field value belongs. If the process stage code deviation of the field value is crossed, and the difference in the task type parameter value is greater than the task type set deviation threshold, then the field value is marked as a path traversal field, and the field node distribution identification result is generated. For each field value, the system identifies and compares the process stages of multiple generated node process number fields. During analysis, the system needs to obtain the "generated node process number" field bound to each node when the field value appears. For example, the process number bound to the field value "SG-005" in node "ND-015" is "PZ01-005", and in node "ND-018" it is "PZ02-001". The system will extract the process stage codes "PZ01" and "PZ02" and determine if there is a difference in stage codes. If the stage codes are different, it indicates that the field value spans different construction stages, and the system will record the process stages in that spanned segment. The system encodes and assigns the field value to the task type parameter in each node based on the sequence stage's coding and node location. For example, "ND-015" is "structural formwork support" and "ND-018" is "equipment installation and commissioning". The system encodes the task types separately and analyzes the differences between them. If the difference between the task types exceeds the task type deviation threshold set by the system, or if the coding span or the span of the professional classification is too large, the system marks the field value as a path-crossing field, indicating that the field cannot be stably assigned to a single construction stage or task area. The system outputs such fields along with the node numbers they involve, generating the field node distribution identification results.

[0036] Specifically, such as Figure 2 , 7 As shown, the risk identification module includes: The path order extraction submodule calls the set of fields marked as path traversal fields in the field node distribution recognition results, extracts the positional order number information of the field values ​​in the corresponding real-time nodes and adjacent front and rear nodes, and combines and arranges the order numbers of the same field values ​​in the differentiated nodes to generate the field path order arrangement result; The system needs to iterate through the field values ​​marked as "path traversal type". The system will use the field value as the primary key to call all occurrences of it in the project node data set, focusing particularly on the real-time node where the field value is located and its two adjacent nodes. The system will extract the "node sequence number" field information recorded in these three nodes. This number is the execution sequence number in the task plan, reflecting the relative position of the node in the project process sequence, such as "node sequence number: 005" and "node sequence number: 006". The system needs to collect the sequence numbers of the field values ​​in the above nodes and combine and arrange them by the field value to form a sequence trajectory sequence. If the field value appears in multiple adjacent nodes, the system will arrange them in ascending order of node number. If the field value "SG-003" appears in the three nodes "ND-018", "ND-020", and "ND-021", with corresponding sequence numbers "008", "010", and "011", then the field path sequence arrangement is "008-010-011", which is used to represent the node distribution trajectory of the field value and generate the field path sequence arrangement result.

[0037] The structural relationship determination submodule arranges the results according to the field path order, compares the sequential numbering combination of field values ​​in adjacent nodes, and determines whether there is a structural relationship with overlapping or intersecting numbers. If the number of field values ​​in the preceding and following nodes is earlier than or equal to the number in the real-time node, it is marked as a structural relationship abnormal node, and a field structure abnormality identification result is generated. The system needs to perform pairwise comparisons of the sequential numbers of each field value across multiple nodes. Using the current node as the center, the system identifies the sequential number of the field value in the preceding and following nodes, determining whether the "sequential number is less than or equal to the center node". If the sequential number of the field value in the preceding node is equal to or greater than the sequential number of the current node, the path order is normal; otherwise, there is a risk of path reversal or information overwriting. In particular, cases where the sequential number in the following node is less than the sequential number of the current node will be identified as cross-over issues. If the field value "SG-008" appears in nodes "ND-025", "ND-026", and "ND-028", with corresponding sequential numbers "020", "019", and "022" respectively, it is found that the sequential number of the intermediate node is greater than that of the preceding node, indicating a reversed order. The system records this node as a structural relationship anomaly and includes it in the anomaly identifier list. Records that meet the condition that "the number of the preceding or following node is less than the number of the current node" will be marked as structural relationship anomaly nodes, generating field structure anomaly identification results.

[0038] The risk status labeling submodule updates the real-time status value of nodes marked as having abnormal structural relationships based on the field structure anomaly identification results, writes the field risk to be verified status identifier into the node status field, and pairs the updated node number with the field value to generate a list of node field risk identifiers. For each node marked as having an abnormal structural relationship, a status update operation needs to be performed. The system iterates through the abnormal node numbers in the identification results and adds or modifies a status item in the node status field to identify field risks. This item is named "Field Status Identifier" or "Path Risk Status" and the status value is set to "Field Risk Pending Verification". This is used to alert project managers or the data review system that the node has an abnormal data distribution in terms of structural location. When writing, the system locates the original node information record using the node's unique number and adds or updates an existing status row in the status field. After the status update, the system needs to pair the update result with the field value to ensure that the risk identifier not only applies to the node itself but also forms a one-to-one binding relationship with the corresponding field value. The system outputs the node number with the updated status and its bound field value to generate a list of node field risk identifiers.

[0039] The above are merely specific embodiments of the present invention, but the scope of protection of the present invention is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the technical scope disclosed in the present invention should be included within the scope of protection of the present invention. Therefore, the scope of protection of the present invention should be determined by the scope of the claims.

Claims

1. A digital management system based on the progress nodes of urban renewal projects, characterized in that, The system includes: The node activation and control module obtains the node task type field set in the urban renewal project, extracts the resource type list corresponding to the task type, determines whether the attendance status field is confirmed to be present, and generates a node activation status identifier. The status cross-verification module compares the status field with the task completion field based on the nodes in the node activation status identifier that are in the active state. It determines that nodes whose status field is completed but whose task identifier is not completed are conflicting nodes and generates a status behavior consistency label list. The path structure adjustment module calls the document corresponding to the state to be verified in the state behavior consistency label list, obtains the generation node process number field and the responsibility role identifier field in the document, uses the process number field as a stage marker and the role field as a responsibility attribution marker, and generates the document archive path segment content. The field traversal retrieval module, based on the path pending status documents recorded in the document archive path segment content, binds field values ​​and retrieves the occurrence positions within the project node range, filters field values ​​in non-contiguous nodes, and generates field node distribution recognition results.

2. The digital management system based on urban renewal project progress nodes according to claim 1, characterized in that: The node activation status identifier includes an activation probability marker, a time sequence verification marker, and a status evaluation label. The status behavior consistency label list includes a conflict status marker, a time difference threshold judgment result, and a list of nodes to be verified. The document archive path segment content includes a path structure matching result, an undefined path marker, and a responsibility attribution classification marker. The field node distribution identification result includes a field process difference classification, a task type attribution deviation marker, and a path traversal type marker.

3. The digital management system based on urban renewal project progress nodes according to claim 1, characterized in that: The node activation and control module includes: The task type extraction submodule obtains the node task type field set in the urban renewal project, calls multiple task type parameters in the node task type field, identifies the correspondence between the parameter mapping set set between task type and resource type, divides the successfully matched resource type set into list items, extracts and classifies the resource type items in the list with unique identifiers, and generates a resource type list. The resource list integration submodule calls the presence status field, registration presence time field and device integrity identifier field of the corresponding device according to the resource type list. It compares the device code in the device integrity identifier field with the resource item in the resource list, and establishes a binding relationship between the device registration record time in the registration presence time field and the resource item to generate a device registration corresponding set. The status judgment submodule calls the presence identification status field according to the device registration corresponding set, selects the device item whose field value is confirmed to be present, extracts the bound registration presence time field value, and performs an order judgment on the registration presence time field value and the node pre-start time field value according to the node plan setting. If the registration presence time field value is earlier than the node pre-start time field value, the record status is activated; otherwise, the record status is frozen, and a node availability judgment result is generated. The activation status submodule summarizes the node record status values ​​based on the node availability determination value, calculates the ratio of the number of active and frozen states, compares the ratio result with the activation threshold set in the node status field, and sets the node status field to active or frozen state according to the comparison result, generating a node activation status identifier.

4. The digital management system based on urban renewal project progress nodes according to claim 3, characterized in that: The state cross-verification module includes: The conflict node identification submodule, based on the nodes in the active state identifier, calls the status field and the task completion identifier field, matches and marks nodes whose status field is completed and whose corresponding task identifier field is incomplete, classifies the nodes that meet the conditions as conflict record items, records the unique identifier code of the node and the corresponding field combination value, and generates a conflict node identifier set. The period offset determination submodule extracts the corresponding status change time and task submission time field values ​​from each item according to the conflict node identifier set, calculates the time difference between the status change time and the task submission time, compares the calculated interval value with the node offset period threshold, and if the time interval is greater than the node offset period threshold, the node is marked as a pending verification state and a node time offset state is generated. The consistency labeling submodule summarizes the unique codes of nodes marked as pending verification based on the node time offset status, adds annotations to the conflict field combination values ​​of multiple types of nodes, binds the annotation content with the node information, and generates a status behavior consistency label list.

5. The digital management system based on urban renewal project progress nodes according to claim 4, characterized in that: The path structure adjustment module includes: The field extraction submodule calls the document set corresponding to the status to be verified in the status behavior consistency label list, locates and extracts the generation node process number field and the responsibility role identifier field in the content of each document, identifies the stage number of the process number field and the attribution code of the role field, and classifies the two types of fields into the structured field set to obtain the basic data of field combination; The path segment construction submodule, based on the field combination basic data, places the responsibility role identifier field in the document first and the generated node process number field in the second position, concatenates the two field values ​​in sequence to form a path segment marker string, and embeds it into the archive path structure of the corresponding document, forming a sequential superposition structure of the path segment content, and generating a document archive path combination. The path status labeling submodule compares the path segment string with the index set of the real-time path segment content structure based on the document archive path combination. If no match is found, an undefined marker is inserted into the path segment, and the path pending status identifier is recorded for the document. The path combination content and status identifier information of all documents are integrated to generate the document archive path segment content.

6. The digital management system based on urban renewal project progress nodes according to claim 5, characterized in that: The document set corresponding to the status to be verified in the status behavior consistency label list is called, and the generation node process number field and responsibility role identifier field in the content of each document are located and extracted. The stage number of the process number field and the belonging code of the role field are identified, and the two types of fields are respectively classified into the structured field set to obtain the basic data of field combination. The process of identifying the stage number of the process number field is as follows: the character sequence of the generated node process number field is split according to a preset format, and the field unit including the stage number prefix is ​​identified in the split character segment. If the prefix of the field unit is consistent with the set stage identification identifier, the field unit is included in the structured field set as the stage number field. The identification process for the attribution code of the responsibility role identifier field is as follows: perform character matching operation on the responsibility role identifier field, and extract the corresponding code item as the attribution code field and incorporate it into the structured field set according to the preset role attribution mapping dictionary.

7. The digital management system based on urban renewal project progress nodes according to claim 5, characterized in that: The field traversal retrieval module includes: The field location submodule extracts the field values ​​bound to each document based on the path pending status documents recorded in the document archive path segment content, sets the search conditions for the field values ​​within the project node range, traverses and matches all field contents in the node data set, records the position of the field values ​​in the node and the node number information, and generates a field node location set. The node filtering submodule sorts the node numbers of the field values ​​in the nodes according to the field node location set, identifies whether the adjacent node numbers in the sorting result are continuous, filters and retains the field values ​​with skipped node numbers, and generates a non-continuous node field set. The traversal identification submodule compares the multiple generation node process number fields bound to each field value with the non-continuous node field set to determine whether there is a difference in the process stage code, and extracts the task type parameter to which the field value belongs. If the process stage code deviation of the field value is crossed, and the difference in the task type parameter value is greater than the task type set deviation threshold, then the field value is marked as a path traversal field, and the field node distribution identification result is generated.

8. The digital management system based on urban renewal project progress nodes according to claim 7, characterized in that: The process for determining the deviation of the process stage code across the field value is as follows: Each process stage code recorded in the process number field of the multiple generation nodes bound to the field value is arranged in ascending order according to the sequence number of the process stage code, and the difference between the first and last process stage codes is calculated as the process stage code deviation. Read the task type field content recorded in the field information bound to the field value, and determine the task type parameter to which the field value belongs based on the standard task type code in the task type field; The task type setting deviation threshold is set as follows: based on the attribute fit level between process task types, the task type setting deviation threshold is set to the attribute deviation value between task type combination pairs that are lower than the three fit levels.

9. The digital management system based on urban renewal project progress nodes according to claim 1, characterized in that: The system also includes a risk identification module: The risk identification module calls the path-crossing field in the field node distribution identification result, extracts the order of appearance of the field value in the real-time node and adjacent nodes, and determines whether the order overlaps or intersects. If there is an abnormality in the structural relationship, the real-time node status is updated to field risk pending verification, and a list of node field risk identification is generated. The node field risk identifier list includes field order anomaly types, node status update flags, and risk verification pending processing flags.

10. The digital management system based on urban renewal project progress nodes according to claim 9, characterized in that: The risk identification module includes: The path order extraction submodule calls the set of fields marked as path traversal fields in the field node distribution recognition result, extracts the positional order number information of the field value in the corresponding real-time node and adjacent front and rear nodes, and combines and arranges the order numbers of the same field value in the differentiated nodes to generate the field path order arrangement result; The structural relationship determination submodule compares the field value sequence number combination in adjacent nodes with the field path order arrangement result to determine whether there is a structural relationship with overlapping or intersecting numbers. If the field value number in the preceding and following nodes is earlier than or equal to the number in the real-time node, it is marked as a structural relationship abnormal node, and a field structure abnormality identification result is generated. Based on the field structure anomaly identification results, the risk status labeling submodule updates the real-time status value of nodes marked as having abnormal structural relationships, writes the field risk pending verification status identifier into the node status field, and pairs the updated node number with the field value to generate a list of node field risk identifiers.

Images