System and apparatus for generating a visual progress of a municipal works

Abstract

The embodiment of the specification provides a system and device for generating visual progress of municipal engineering, the system comprising at least one processor, a storage device in communication with the at least one processor, and the at least one processor being configured to execute: obtaining parameter information of a primary area of the municipal engineering, the parameter information comprising basic parameters and core parameters; generating a secondary area list matched with the primary area based on the basic parameters and using a first preset rule base; generating a tertiary area list matched with the secondary area based on the core parameters and using a second preset rule base; and generating a plurality of progress units based on the secondary area list and the tertiary area list, each progress unit corresponding to a secondary area and a tertiary area. The system can automatically adapt the tertiary area division rule according to different municipal engineering tasks, reduce manual input errors and tedious operations, improve the division accuracy and efficiency, and make the visual progress generation of the municipal engineering more accurate and efficient.

Description

Technical Field

[0001] This specification relates to the field of project construction technology, and in particular to a system and apparatus for generating visual progress reports for municipal engineering projects. Background Technology

[0002] Municipal engineering projects, as the core carriers of urban infrastructure construction, are characterized by large investment scale, long construction period, numerous participating parties (such as construction, contracting, supervision, and government regulatory departments), and wide spatial span. Their progress management is directly related to the improvement of urban functions and the protection of people's livelihood. Traditional municipal engineering progress management relies heavily on abstract data such as fund disbursement ratios and bill of quantities calculations, which suffers from problems such as delayed information transmission, low visibility, and insufficient efficiency in multi-party collaboration. It is difficult to intuitively reflect the actual construction status of the project, which can easily lead to decision-making biases and a disconnect between supervision and management.

[0003] Therefore, the embodiments of this specification provide a system and apparatus for automatically generating the visual progress of municipal engineering projects, so as to reflect the visual progress of municipal engineering projects in an intuitive and visual way. Summary of the Invention

[0004] This specification provides one or more embodiments of a system for generating visual progress reports of municipal engineering projects, including at least one processor and a storage device communicating with the at least one processor. The at least one processor is configured to perform the following: acquiring parameter information of a primary area of ​​the municipal engineering project, wherein the primary area is a construction area included in the municipal engineering project, and the parameter information includes basic parameters and core parameters; generating a list of secondary areas matching the primary area based on the basic parameters using a first preset rule base, wherein the list of secondary areas reflects the construction sequence of the secondary areas included in the primary area; generating a list of tertiary areas matching the secondary area based on the core parameters using a second preset rule base, wherein the tertiary areas reflect the construction segments included in each secondary area; and generating multiple progress units based on the list of secondary areas and the list of tertiary areas, wherein each progress unit corresponds to one secondary area and one tertiary area; wherein different types of secondary areas correspond to different tertiary area generation rules.

[0005] This specification also provides one or more embodiments of a method for generating a visual progress chart of a municipal engineering project. The method includes: obtaining parameter information of a primary area of ​​the municipal engineering project, wherein the primary area is a construction area included in the municipal engineering project, and the parameter information includes basic parameters and core parameters; generating a list of secondary areas matching the primary area using a first preset rule base based on the basic parameters, wherein the list of secondary areas reflects the construction sequence of the secondary areas included in the primary area; generating a list of tertiary areas matching the secondary area using a second preset rule base based on the core parameters, wherein the tertiary areas reflect the construction segments included in each secondary area; and generating multiple progress units based on the list of secondary areas and the list of tertiary areas, wherein each progress unit corresponds to one secondary area and one tertiary area; wherein different types of secondary areas correspond to different tertiary area generation rules.

[0006] This specification provides one or more embodiments of another system for generating visual progress reports of municipal engineering projects, including at least one processor and a storage device communicating with the at least one processor. The at least one processor includes: an acquisition module configured to acquire parameter information of a primary area of ​​the municipal engineering project; the primary area being a construction area included in the municipal engineering project, and the parameter information including basic parameters and core parameters; a first generation module configured to generate a list of secondary areas matching the primary areas based on the basic parameters and using a first preset rule base; the list of secondary areas reflecting the construction sequence of the secondary areas included in the primary area; a second generation module configured to generate a list of tertiary areas matching the secondary areas based on the core parameters and using a second preset rule base; the tertiary areas reflecting the construction segments included in each secondary area; and a third generation module configured to generate multiple progress units based on the list of secondary areas and the list of tertiary areas; each progress unit corresponding to one secondary area and one tertiary area; wherein different types of secondary areas correspond to different tertiary area generation rules.

[0007] One or more embodiments of this specification also provide an apparatus for generating a visual progress report of a municipal engineering project. The apparatus includes at least one storage medium and at least one processor. The at least one storage medium is used to store computer instructions. The at least one processor is used to execute the computer instructions to implement the method for generating a visual progress report of a municipal engineering project.

[0008] The system and apparatus for generating the visual progress of municipal engineering projects described in the embodiments of this specification can automatically adapt to the three-level regional division rules according to different municipal engineering tasks, reduce manual input errors and tedious operations, improve the accuracy and efficiency of division, and make the generation of the visual progress of municipal engineering projects more accurate and efficient. Attached Figure Description

[0009] This specification will be further described by way of exemplary embodiments, which will be described in detail with reference to the accompanying drawings. These embodiments are not limiting; in these embodiments, the same reference numerals denote the same structures, wherein:

[0010] Figure 1 This is a schematic diagram of a system for generating visual progress of municipal engineering projects according to some embodiments of this specification;

[0011] Figure 2 This is an exemplary flowchart of a method for generating a visual progress chart of a municipal engineering project according to some embodiments of this specification;

[0012] Figure 3 This is a schematic diagram illustrating the creation of a primary region according to some embodiments of this specification;

[0013] Figure 4 This is a schematic diagram of the progress of a bridge project, based on some embodiments of this specification.

[0014] Figure 5 This is an exemplary flowchart illustrating the updating of an initial three-level region list according to some embodiments of this specification;

[0015] Figure 6 This is an exemplary flowchart illustrating the generation of a two-dimensional table of municipal image progress according to some embodiments of this specification;

[0016] Figure 7 This is an exemplary flowchart illustrating the updating of a two-dimensional table of municipal image progress according to some embodiments of this specification;

[0017] Figure 8 This is an exemplary block diagram of a processor for a system that generates visual progress charts of municipal engineering projects according to some embodiments of this specification. Detailed Implementation

[0018] To more clearly illustrate the technical solutions of the embodiments in this specification, the accompanying drawings used in the description of the embodiments will be briefly introduced below. Obviously, the drawings described below are merely some examples or embodiments of this specification. For those skilled in the art, these drawings can be applied to other similar scenarios without creative effort. Unless obvious from the context or otherwise specified, the same reference numerals in the drawings represent the same structures or operations.

[0019] It should be understood that the terms “system,” “device,” “unit,” and / or “module” used herein are one way to distinguish different components, elements, parts, sections, or assemblies at different levels. However, if other terms can achieve the same purpose, they may be replaced by other expressions.

[0020] As indicated in this specification and claims, unless the context clearly indicates otherwise, the words "a," "an," "an," and / or "the" are not specifically singular and may include the plural. Generally speaking, the terms "comprising" and "including" only indicate the inclusion of expressly identified steps and elements, which do not constitute an exclusive list, and the method or apparatus may also include other steps or elements.

[0021] Flowcharts are used in this specification to illustrate the operations performed by the system according to embodiments of this specification. It should be understood that the preceding or following operations are not necessarily performed in exact order. Instead, the steps can be processed in reverse order or simultaneously. Furthermore, other operations can be added to these processes, or one or more steps can be removed from them.

[0022] Figure 1 This is a schematic diagram of a system for generating visual progress charts of municipal engineering projects, as shown in some embodiments of this specification. For example... Figure 1 As shown, the system 100 for generating the visual progress of municipal engineering projects includes at least one processor 110, a storage device 120 communicating with the at least one processor 110, a network 130, and a terminal 140. For ease of explanation, the system 100 for generating the visual progress of municipal engineering projects will be referred to as system 100 in the embodiments of this specification. In some embodiments, system 100 may be a service platform for generating visual progress tables of municipal engineering projects.

[0023] The processor 110 is capable of processing information and / or data related to the system 100 to perform one or more functions described in this specification (e.g., generating a visual progress table for municipal engineering projects). In some embodiments, the processor 110 is configured to perform the following: obtain parameter information of a primary area of ​​the municipal engineering project, wherein the primary area is a construction area included in the municipal engineering project, and the parameter information includes basic parameters and core parameters; based on the basic parameters, using a first preset rule base, generate a list of secondary areas matching the primary areas, wherein the list of secondary areas reflects the construction sequence of the secondary areas included in the primary areas; based on the core parameters, using a second preset rule base, generate a list of tertiary areas matching the secondary areas, wherein the tertiary areas reflect the construction segments included in each secondary area; and based on the list of secondary areas and the list of tertiary areas, generate multiple progress units, each progress unit corresponding to one secondary area and one tertiary area; wherein different types of secondary areas correspond to different tertiary area generation rules.

[0024] In some embodiments, the basic parameters include the type of the primary region, and the core parameters include the length of the construction area of ​​the primary region and / or the number of construction projects.

[0025] In some embodiments, the processor 110 is further configured to perform: obtaining the type of the primary region and the municipal construction spatial logic (e.g., directly from the storage device 120, or based on input information from the user via the terminal 140); and, based on the type of the primary region and the municipal construction spatial logic, pre-setting the vertical axis order of each secondary region to generate a first preset rule base.

[0026] In some embodiments, the processor 110 is further configured to perform: obtaining municipal three-level zoning requirements (e.g., directly from storage device 120, or based on user input information via terminal 140); and setting three-level zoning generation rules for each secondary zoning zone based on the municipal three-level zoning requirements to generate a second preset rule base.

[0027] In some embodiments, the processor 110 is further configured to perform: generating an initial list of secondary regions matching the primary regions based on basic parameters and using a first preset rule base; and generating a secondary region list based on user input information and the initial list of secondary regions.

[0028] In some embodiments, the processor 110 is further configured to perform: generating an initial list of tertiary regions matching the secondary regions based on core parameters and utilizing a second preset rule base, and triggering a custom interval entry; obtaining a user-inputted custom interval based on the custom interval entry; and updating the initial list of tertiary regions based on the custom interval. The first and second preset rule bases are stored in a storage device, such as storage device 120.

[0029] In some embodiments, the processor 110 is further configured to perform: obtaining a list of existing tertiary regions under the same secondary region based on the secondary region identifier; comparing the existing list of tertiary regions with the updated initial list of tertiary regions; and generating a list of non-overlapping tertiary regions based on the comparison result.

[0030] In some embodiments, before generating a progress unit, the processor 110 is further configured to perform: mapping segment identifiers in a non-overlapping list of three-level regions based on the identifier type; and sorting based on the mapping results to generate a sorted list of three-level regions.

[0031] In some embodiments, the processor 110 is further configured to perform: determining the horizontal axis width corresponding to each third-level region based on the system interface's preset total horizontal axis length and the sorted list of third-level regions; arranging the segment identifiers of each third-level region sequentially based on the horizontal axis width; arranging the identifiers of each second-level region based on the list of second-level regions; and intersecting the segment identifiers of each third-level region and the identifiers of each second-level region sequentially to generate multiple progress units, thereby generating a two-dimensional table of municipal image progress.

[0032] In some embodiments, the processor 110 is further configured to: obtain a list of pending task orders; in response to the pending task order list including the acceptance of a new task order, extract the task order information of the new task order; split the new task order based on the task order information; update the two-dimensional table of municipal image progress based on the splitting result, and obtain the updated two-dimensional table of municipal image progress.

[0033] In some embodiments, the processor 110 is further configured to perform: in response to the pending task list including mid-term entry task list supplementation, obtaining a historical task list to be supplemented based on the primary area identifier of the mid-term entry task list and the time range before the entry time; determining the matching result between the historical task list and the tertiary area based on a preset algorithm; updating the information of the corresponding progress unit based on the matching result and the acceptance status of the mid-term entry task list, and obtaining a two-dimensional table of municipal image progress and / or supplementation report of batch supplementation completion.

[0034] For further explanation regarding the processor 110 performing the above functions, please refer to the relevant sections below, such as... Figures 2-8 .

[0035] In some embodiments, processor 110 may include a central processing unit (CPU), a digital signal processor (DSP), a microcontroller unit (MCU), a computer, a user console, or any combination thereof. In some embodiments, processor 110 may include a single server or a group of servers. The server group may be centralized or distributed. In some embodiments, processor 110 may be local or remote. In some embodiments, processor 110 may be implemented on a cloud platform. By way of example only, a cloud platform may include a private cloud, a public cloud, a hybrid cloud, a community cloud, a distributed cloud, an internal cloud, a multi-tiered cloud, or any combination thereof.

[0036] Storage device 120 is capable of storing data, instructions, and / or any other information. For example, storage device 120 may store parameter information of a primary region, a first preset rule base, a second preset rule base, etc. In some embodiments, storage device 120 may include a mass storage device, a removable storage device, a volatile read-write memory, a read-only memory (ROM), etc., or any combination thereof. In some embodiments, storage device 120 may be executed on a cloud platform.

[0037] Network 130 can connect the components within system 100 and / or other components outside system 100. In some embodiments, one or more components of system 100 (e.g., processor 110, storage device 120, and terminal 140, etc.) can be connected to and / or communicate with each other through network 130.

[0038] Terminal 140 can provide functional components related to user interaction and enable user interaction functions (such as providing or displaying information and data to the user). By way of example only, terminal 140 can be one or any combination of other devices with input and / or output functions, such as mobile devices, tablet computers, laptop computers, and desktop computers. By way of example only, output functions include, but are not limited to, one or more combinations of sound output such as voice, display screen, haptic transmission such as vibration, and electromagnetic wave signals such as light. By way of example only, input functions can include, but are not limited to, one or more combinations of keyboard input, touchscreen input, voice input, motion event input such as device tilt / shake / rotation / swing, and electromagnetic wave signal input such as light.

[0039] In some embodiments, the terminal 140 includes a visual interface that provides display and input functions for the user. For example, the visual interface can display the progress of municipal engineering projects (such as a two-dimensional table of municipal progress); or, for example, the user can input adjustment requests for the secondary list and custom intervals for the tertiary area list through the visual interface.

[0040] It should be noted that System 100 is provided for illustrative purposes only and is not intended to limit the scope of this application. Those skilled in the art can make various modifications or variations based on the description in this specification. For example, System 100 can implement similar or different functions on other devices. However, these changes and modifications will not depart from the scope of this application.

[0041] Figure 2 This is an exemplary flowchart of a method for generating a visual progress chart of a municipal engineering project according to some embodiments of this specification. In some embodiments, process 200 may be executed by system 100 (e.g., processor 110). Figure 2 As shown, process 200 includes the following steps.

[0042] Step 210: The processor can obtain parameter information of the first-level area of ​​the municipal engineering project.

[0043] Municipal engineering refers to the construction, renovation, and maintenance of infrastructure and public service facilities led or supervised by city governments, aimed at improving urban public functions and the quality of life for residents. Municipal engineering, through systematic engineering, improves the urban operating system, focusing on urban space and public needs. For example, municipal engineering includes urban infrastructure construction (e.g., transportation facilities, municipal pipe networks), public space and environmental construction, public service facility construction, and urban safety and disaster prevention facility construction. Exemplary examples include roadbed engineering, pavement paving engineering, bridge construction engineering, underground utility tunnel engineering, tunnel excavation engineering, and urban drainage pipeline engineering. Transportation facilities include roads, bridges, tunnels, subways, bus stops, parking lots, and traffic signal systems. Municipal pipe networks include water supply and drainage systems (such as waterworks, sewage pipes, and rainwater drainage systems), gas pipelines, and heating networks.

[0044] The visual progress of municipal engineering projects refers to the description of the actual completion status and progress of the physical parts of municipal engineering projects in an intuitive and visual way (such as text descriptions, pictures, and charts).

[0045] A primary zone refers to the construction area encompassed by a municipal engineering project. A municipal project is generally divided into multiple sections for construction, and the primary zones are the different construction areas within a municipal project. For example, in a road construction project, a 20km road can be divided into 5 sections for construction: 0-4km, 4-8km, 8-12km, 12-16km, and 16-20km, which are also divided into 5 primary zones.

[0046] The parameter information of a primary region refers to the key information describing the core attributes of that primary region. In some embodiments, the parameter information of a primary region includes basic parameters and core parameters.

[0047] Basic parameters refer to data describing the type of a primary region. In some embodiments, basic parameters include the type of the primary region. In some embodiments, basic parameters may also describe the type of municipal engineering project, such as roadbed, pavement, bridge, utility tunnel, tunnel, etc. For example, the basic parameter for the primary region "XX Mountain Tunnel Roadbed Project" is "Roadbed"; the basic parameter for the primary region "Urban Integrated Utility Tunnel Laying Section" is "Utility Tunnel", etc.

[0048] Core parameters refer to data describing the construction scale of a primary area. In some embodiments, core parameters include the length of the construction area and / or the number of construction projects within the primary area. For example, the core parameter for a primary area in roadbed / tunnel engineering is the mileage segment, i.e., the length of the construction area, such as K0+10~K0+400. Here, K0 represents the starting point of the primary area, "10" and "400" represent the distances from the starting point of the primary area, and K0+10~K0+400 represents a construction area of ​​390m from 10m to 400m from the starting point of the primary area. As another example, the core parameter for a primary area in bridge engineering could be the number of construction projects (such as the number of pier caps), such as including 5 pier caps.

[0049] The length of a construction zone refers to the linear span of a primary zone in space. For example, the length of the construction zone can be a core parameter for primary zones of municipal engineering projects such as roadbeds, tunnels, utility tunnels, and road surfaces, which are linearly distributed.

[0050] The number of construction projects refers to the total number of physical components or work units within a primary area that can be constructed independently and measured separately. For example, the core parameters of a primary area for municipal engineering projects such as bridges and culverts, which are based on discrete components, may include the number of construction projects such as pier caps.

[0051] In some embodiments, primary zones can be created by users through a visual interface of a system that generates visual progress reports for municipal engineering projects. In some embodiments, parameter information for primary zones of municipal engineering projects can be obtained through user input. Figure 3 This is a schematic diagram illustrating the creation of a primary region according to some embodiments of this specification. For example... Figure 3 As shown, users can create a visual interface for a primary area and input basic and core parameters using various methods such as voice, text, images, and remote control. For example, users can select to input or input characters for the basic parameters of the primary area through the "Single Project" window in the visual interface. In some embodiments, users can also input parameters through methods such as... Figure 3 The visual interface shown allows you to input other parameters for the primary area, such as core parameters (not shown in the figure), the project, unit project, sub-item, construction management personnel, and construction acceptance personnel.

[0052] In some embodiments, when creating a primary area, the user can directly input images, documents, tables, and other files related to the municipal engineering project, and the processor automatically extracts the parameter information of the primary area from the files. In some embodiments, the processor (e.g., processor 110) can obtain the parameter information of the primary area from a storage device (e.g., storage device 120). For example, for a municipal engineering project that has already created some primary areas, the parameter information of the primary area to be created can be referenced from the parameter information of the already created primary areas.

[0053] Step 220: The processor can generate a list of secondary regions that match the primary regions based on the basic parameters and using the first preset rule base.

[0054] A secondary area refers to multiple sub-construction areas obtained by dividing a primary area according to specific construction tasks. For example, if the primary area type is roadbed, and the construction sequence from bottom to top (gradually constructing upwards from the ground surface) is: foundation treatment, earthwork excavation, earthwork filling, slope protection, etc., then the corresponding secondary areas are the areas corresponding to the construction tasks of foundation treatment, earthwork excavation, earthwork filling, and slope protection. In some embodiments, secondary areas can be obtained by user input. For example, the user can obtain them through input such as... Figure 3 The "Sub-items" window shown indicates the input area for the second-level region.

[0055] In some embodiments, the processor may also generate a list of secondary regions that match the primary regions based on basic parameters and using a first preset rule base.

[0056] The secondary area list refers to a list formed by sorting the multiple secondary areas, which are divided into primary areas according to the construction sequence, along the vertical axis in the visualization interface from bottom to top (or from top to bottom). Here, the vertical axis refers to the vertical axis in the visualization interface, such as... Figure 4 The Y direction is shown. In some embodiments, the list of secondary zones reflects the construction sequence of the secondary zones contained in the primary zone.

[0057] Figure 4 This is a schematic diagram illustrating the progress of a bridge project, based on some embodiments of this specification. For example... Figure 4 As shown, the secondary area list 410 includes multiple secondary area types such as bridge deck paving, beam erection, beam prefabrication, cap beams, piers, abutments, pile caps, and pile foundations, as well as the sorting of multiple secondary areas according to the construction sequence (e.g., Figure 4 (Sorting in the Y direction as shown).

[0058] The first preset rule base refers to the rules for dividing the second-level regions corresponding to the first-level regions. In some embodiments, the first preset rule base can be used to generate a list of second-level regions. For example, the first preset rule base may be a database including mapping rules such as "roadbed engineering: foundation treatment, earthwork excavation, earthwork filling, slope protection" and "bridge engineering: pier cap construction, pier pouring, bridge deck erection". The first preset rule base can be pre-stored in a database or storage device.

[0059] In some embodiments, the processor (e.g., processor 110) may also obtain the type of the primary region and the municipal construction space logic; based on the type of the primary region and the municipal construction space logic, the vertical axis sorting of each secondary region is preset to generate a first preset rule base.

[0060] The type of a primary region can be obtained based on the parameter information of the primary region (such as the basic parameters of the primary region).

[0061] The spatial logic of municipal construction refers to the inherent construction sequence of municipal engineering projects in space. It typically follows the industry standard of "from bottom to top, from foundation to ancillary structures." For example, the spatial logic for road construction is "foundation treatment → earthwork excavation → base course → surface course," while for bridge construction it is "pile foundation → abutment → pier → cap beam → bridge deck paving," and so on.

[0062] In some embodiments, the municipal construction spatial logic can be obtained directly through user input, or by the user inputting relevant municipal construction documents (such as survey reports, construction design drawings, and site plans), from which the processor extracts the municipal construction spatial logic. In some embodiments, the processor can automatically retrieve relevant municipal construction documents from a database (e.g., based on the type of municipal project) and extract the municipal construction spatial logic from these documents.

[0063] The vertical axis sorting of secondary regions refers to the order in which the secondary regions are arranged along the vertical axis according to construction spatial logic. For example, the processor can sort the secondary regions along the vertical axis according to construction spatial logic, "from bottom to top, from foundation to ancillary" (e.g., as shown in the image). Figure 4 The order is as shown in the Y direction.

[0064] In some embodiments, the processor can determine the type of the secondary region based on the type of the primary region (e.g., if the primary region type is bridge engineering, the corresponding secondary region types include bridge deck paving, beam erection, beam prefabrication, cap beams, piers, abutments, pile caps, and pile foundations); and arrange the secondary region types from bottom to top according to the construction sequence in the construction space logic (i.e., ...). Figure 4The system assigns sorting numbers (e.g., 1. pile foundation, 2. pile cap, 3. bridge abutment, etc.) in the Y direction; and generates a first preset rule base based on the first-level region ID, first-level region type, second-level region type, second-level region sorting number, and second-level region sorting. For example, the processor can generate a second-level region sorting based on the second-level region sorting number (e.g., sorting multiple second-level regions based on the second-level region sorting number to generate a second-level region sorting), and uses the first-level region ID, first-level region type, second-level region type, second-level region sorting number, and second-level region sorting as a table structure to generate the first preset rule base. An exemplary data entry in the first preset rule base includes "First-level region type: roadbed, first-level region ID: 001, second-level region sorting number: 1-6, second-level region sorting: foundation treatment → earthwork excavation → earthwork filling → slope support → base course → surface course".

[0065] In some embodiments, the first preset rule base is generated before the first-level region is built; that is, the first preset rule base is pre-generated and stored by the processor (e.g., stored in storage device 120). The processor may pre-generate the first preset rule base and store it locally or upload it to a cloud server for storage.

[0066] In some embodiments, the processor (e.g., processor 110) can match the basic parameters of a primary region (such as "roadbed") with the primary region type in a first preset rule base, and use multiple secondary regions in the first preset rule base obtained by matching as secondary regions that match the primary region, and generate a list of secondary regions corresponding to the primary region based on the sorting of the secondary regions.

[0067] In some embodiments, the processor (e.g., processor 110) may also generate an initial list of secondary regions that match the primary regions based on basic parameters and using a first preset rule base; and generate a secondary region list (also called an updated secondary region list) based on user input information (e.g., input via terminal 140) and the initial secondary region list.

[0068] The initial secondary region list refers to the list of secondary regions automatically generated based on basic parameters and the first preset rule base.

[0069] In some embodiments, the processor may determine the type of a primary region based on basic parameters, and generate an initial list of secondary regions by querying a first preset rule base according to the type of the primary region.

[0070] User input refers to the user's request to adjust the order of the secondary areas in the secondary area list. For example, a tunnel construction project requires "slope protection" to be carried out before "earthwork filling".

[0071] The initial list of secondary regions automatically generated by System 100 is displayed in a visual interface for the user. In some embodiments, the visual interface of System 100 may provide buttons such as "Move Up," "Move Down," and "Delete" next to each secondary region in the list. Users can click the button corresponding to each secondary region in the initial list to adjust the order of the secondary regions. For example, a user can click the "Move Up" button next to "Slope Support" to move it from the 4th position to the 3rd position. The adjusted secondary region list will be: Foundation Treatment → Earthwork Excavation → Slope Support → Earthwork Filling → Base Layer → Surface Layer. After adjusting the secondary regions, the user can save the adjustment by clicking the "Save" button. After all secondary regions in the initial list have been adjusted, the processor updates the initial secondary region list corresponding to the primary region to obtain the custom secondary region list, which is the updated secondary region list.

[0072] In some embodiments, the processor can also automatically update the initial secondary region list based on user input. For example, the processor can update the initial secondary region list based on the order of secondary regions input by the user to obtain a custom secondary region list, i.e., the updated secondary region list.

[0073] In some embodiments of this specification, the initial secondary region list is updated based on user input information to generate a new secondary region list, which is more flexible and can generate a custom secondary region list that meets user needs.

[0074] Step 230: The processor can generate a list of tertiary regions that match the secondary regions based on the core parameters and using the second preset rule base.

[0075] A third-level region list refers to a list formed by arranging multiple third-level regions within each second-level region along the horizontal axis. The horizontal axis is the axis perpendicular to the vertical direction in the visual interface, such as... Figure 4 The X direction is shown.

[0076] A third-level area refers to a specific construction segment divided from a second-level area according to construction needs. In some embodiments, a third-level area reflects the construction segments contained within each second-level area. A construction segment refers to an independent work unit obtained by breaking down a second-level area. For example, a third-level area could be "pier #3 abutment" in bridge pier abutment construction, "section K0+200~K0+300" in roadbed earthwork filling, or "sections 5-8 of the utility tunnel" in utility tunnel installation, etc.

[0077] like Figure 4As shown, the three-level area list 420 includes the three-level areas contained in each two-level area and the order of the three-level areas. For example, the three-level areas corresponding to the bridge deck pavement in the two-level area include the pavement areas of bridge decks 0-2, 2-4, 4-6, 6-8, and 8-9. Another example is the three-level areas corresponding to the cap beams in the two-level area, which include abutment 0, piers 1 through 8, and abutment 9.

[0078] In some embodiments, the tertiary regions can be obtained through user input. For example, a user can manually divide each secondary region into multiple tertiary regions through a terminal 140, and generate a visual progress chart of a municipal engineering project by sequentially inputting the multiple tertiary regions through a visual interface.

[0079] In some embodiments, the processor (e.g., processor 110) may also generate a list of tertiary regions that match the secondary regions based on core parameters and using a second preset rule base.

[0080] The second preset rule base reflects the default generation rules for the tertiary region corresponding to each secondary region.

[0081] In some embodiments, the processor (e.g., processor 110) can obtain the municipal three-level area division requirements; based on the municipal three-level area division requirements, set three-level area generation rules for each second-level area to generate a second preset rule base.

[0082] The requirement for municipal three-level zoning refers to the need for dividing specific construction sections in municipal engineering projects. For example, this requirement includes dividing roadbeds / tunnels by mileage intervals, bridge piers by pier number, beams and slabs by slab number, and utility tunnels by segment. It also includes the intervals between divisions. For example, roadbeds / tunnels might be divided at 100m intervals; bridge piers might be divided by pier number. In some embodiments, the municipal three-level zoning requirement can be extracted from municipal construction documents or obtained through manual user input.

[0083] Level 3 area generation rules refer to the preset construction segmentation rules for different types of Level 2 areas. Level 3 area generation rules include division dimensions (such as mileage, numbering, etc.) and default parameters (such as mileage intervals, numbering intervals, etc.). Different types of Level 2 areas correspond to different Level 3 area generation rules. For example, "Level 1 area: roadbed, Level 2 area: earthwork excavation → Level 3 area generation rule: divided by 100m mileage intervals"; "Level 1 area: bridge, Level 2 area: pier construction → Level 3 area generation rule: divided by pier sequence (pier #1, pier #2, etc.)", etc.

[0084] In some embodiments, the processor (e.g., processor 110) can set corresponding tertiary region generation rules for each secondary region type in the first preset rule base to generate a second preset rule base. For example, when the core parameter includes the length of the construction area of ​​the primary region (e.g., roadbed mileage), the processor can set a "mileage interval division rule" for each secondary region (e.g., earthwork excavation, base course construction) and set a default interval (e.g., 50m, 100m, etc.). When the core parameter includes the number of construction projects in the primary region (e.g., the number of bridge piers), the processor can set a "numbering interval division rule" for each secondary region (e.g., each pier) and set a default interval (e.g., interval by 1 number, interval by 2 numbers, etc.). The processor can add tertiary region generation rules corresponding to each secondary region type to the first preset rule base to generate a second preset rule base. An example data entry in the second preset rule base includes "Level 1 area type: roadbed, Level 1 area ID: 001, Level 2 area sorting number: 1-6, Level 2 area sorting: foundation treatment (Level 3 area generation rule: divided by 100m mileage interval) → earthwork excavation (Level 3 area generation rule: divided by 100m mileage interval) → ...".

[0085] In some embodiments, the second preset rule base is generated after the first preset rule base is generated and before the first-level region is constructed. That is, the processor can first generate the first preset rule base and then generate the second preset rule base based on the first preset rule base. The processor can store the second preset rule base locally or upload it to a cloud server for storage.

[0086] In some embodiments, after generating the secondary region list, the processor can generate a tertiary region list matching each secondary region based on the core parameters of each secondary region in the secondary region list and the corresponding tertiary region generation rules in the second preset rule base. In some embodiments, the processor can generate a tertiary region list matching each secondary region based on the core parameters and using the second preset rule base. For example, if the core parameters of the secondary region "foundation treatment" are K0+10~K0+400, and the corresponding tertiary region generation rule in the second preset rule base is "divided according to 100m mileage intervals", then the processor can determine the tertiary region list of the secondary region "foundation treatment" as: K0+10~K0+110, K0+110~K0+210, K0+210~K0+310, K0+310~K0+400.

[0087] In some embodiments, the processor may also generate an initial list of tertiary regions matching the secondary regions, and update the initial list of tertiary regions based on a user-inputted custom interval. Further details can be found in [link to relevant documentation]. Figure 4 .

[0088] In some embodiments of this specification, by pre-setting the generation rules for the tertiary areas corresponding to each secondary area of ​​the municipal engineering project (such as roadbed by mileage and bridge by pier number), the random manual input is avoided, thereby improving the efficiency and effectiveness of the image progress generation of the municipal engineering project.

[0089] Step 240: The processor can generate multiple progress units based on the secondary region list and the tertiary region list.

[0090] A schedule unit refers to the smallest unit of schedule management for municipal engineering projects. A schedule unit corresponds to a single cell in a two-dimensional table of municipal progress. For example... Figure 4 As shown, Figure 4 Each cell in the table can correspond to a progress unit.

[0091] A two-dimensional table representing the progress of municipal engineering projects is a table that uses two dimensions to depict the progress of municipal engineering projects. For example... Figure 4 The diagram showing the progress of a bridge can also be described as a two-dimensional table illustrating the bridge's progress. The horizontal axis of this two-dimensional progress table (e.g., ...) represents the bridge's progress. Figure 4 The X-axis (as shown) corresponds to the division of three-level regions (i.e., a list of three-level regions), and the vertical axis (as shown) Figure 4 The Y-direction shown corresponds to the division of the secondary region (i.e., the secondary region list), and each cell is the progress unit formed by the intersection of the secondary region list and the tertiary region list.

[0092] In some embodiments, the two-dimensional progress table for municipal projects can highlight (e.g., background highlighting, font highlighting, font bolding, etc.) the progress of municipal engineering projects. For example, white progress cells in the two-dimensional table indicate that construction has not started; green progress cells indicate that construction is in progress, and the darker the green, the greater the progress (i.e., the higher the completion rate); red progress cells indicate that construction is overdue, etc. The two-dimensional progress table for municipal projects can also display the progress of municipal engineering projects in other ways, such as through percentages, progress bars, etc.

[0093] In some embodiments, the processor (e.g., processor 110) can also generate multiple progress units based on a custom list of secondary zones and a sorted list of tertiary zones, thereby generating a two-dimensional table of municipal image progress. Further details can be found in [link to relevant documentation]. Figure 6 .

[0094] The method for generating the visual progress of municipal engineering projects described in the embodiments of this specification can automatically adapt to the three-level regional division rules according to different municipal engineering tasks, reduce manual input errors and tedious operations, improve the accuracy and efficiency of division, and make the generation of the visual progress of municipal engineering projects more accurate and efficient.

[0095] Figure 5This is an exemplary flowchart illustrating the updating of an initial three-level region list according to some embodiments of this specification. In some embodiments, process 500 may be executed by system 100 (e.g., processor 110). Figure 5 As shown, process 500 includes the following steps.

[0096] In step 510, the processor can generate an initial list of third-level regions that match the second-level regions based on the core parameters and using the second preset rule base, and trigger a custom interval entry.

[0097] The initial three-level region list refers to the three-level region list automatically generated based on the second preset rule base.

[0098] A custom interval entry point refers to an interface that allows users to adjust the division rules of the tertiary regions corresponding to each secondary region (e.g., mileage interval, quantity division method, etc.). For example, a custom interval entry point could be an input box, button, or similar element that allows users to adjust the division interval of the tertiary regions corresponding to each secondary region.

[0099] In some embodiments, the processor may determine an initial list of three-level regions by means of the method described in step 230.

[0100] In some embodiments, the system 100 can present the generated initial three-level region list in a visualization interface and trigger a custom interval entry. For example, the visualization interface can simultaneously display the initial three-level region list and the custom interval entry.

[0101] Step 520: The processor can obtain the user-inputted custom interval based on the custom interval entry.

[0102] Custom intervals refer to the intervals set by the user to divide the three-level areas.

[0103] For example, when a user clicks the "Custom Interval" button, a pop-up input window appears on the visual interface, allowing the user to input a custom interval in character form. Alternatively, after the user clicks the "Custom Interval" button, the system 100 can present multiple candidate intervals for the user to choose from on the visual interface, allowing the user to input a custom interval by selecting one of the candidate intervals.

[0104] In step 530, the processor can update the initial three-level region list based on a custom interval.

[0105] In some embodiments, the processor may re-divide the initial tertiary region based on a custom interval to update the initial tertiary region list and obtain the updated initial tertiary region list.

[0106] In some embodiments, before updating the initial three-level region list, the processor can also display a preview of the updated initial three-level region list through a visual interface. The initial three-level region list is then updated only after the user confirms (e.g., by clicking the confirmation button). Alternatively, the user can click the back or cancel button displayed in the visual interface to return to the previous menu and adjust the custom interval. The processor then updates the initial three-level region list based on the adjusted custom interval.

[0107] In some embodiments, the intervals between the multiple tertiary regions corresponding to each secondary region can be the same or different. For example, the user-inputted custom intervals between the multiple tertiary regions corresponding to each secondary region can be the same. For instance, the intervals between the tertiary regions corresponding to the secondary region "base construction" can be the same, such as the corresponding tertiary regions being: K0~K0+100 (interval of 100m), K0+100~K0+200 (interval of 100m), K0+200~K0+300 (interval of 100m), K0+300~K0+400 (interval of 100m). For example, the custom intervals of multiple tertiary regions corresponding to each secondary region input by the user can be different. For instance, the tertiary regions corresponding to the secondary region "earthwork excavation" can be: K0+10~K0+90 (interval of 80m), K0+90~K0+190 (interval of 100m), K0+190~K0+260 (interval of 70m), and K0+260~K0+400 (interval of 140m).

[0108] In some embodiments, the intervals for dividing tertiary regions corresponding to different secondary regions can be the same or different. That is, for multiple secondary regions under the same primary region (such as "roadbed earthwork excavation", "roadbed base construction", "slope protection"), the intervals for dividing tertiary regions can be consistent (e.g., all divided at 100m intervals), or they can be set independently according to the characteristics of the process (e.g., "earthwork excavation" divided at 80m intervals, "base construction" divided at 150m intervals, and "slope protection" divided at 50m intervals).

[0109] In some embodiments of this specification, the intervals of multiple three-level zones can be flexibly set to cope with the terrain / geological differences of linear municipal engineering projects and match the construction efficiency of different processes (such as "surface paving" which has high efficiency and can expand the interval, while "slope support" which has a complex process and needs to reduce the interval), so as to obtain a better visual progress generation effect for municipal engineering projects.

[0110] In some embodiments, system 100 may store and record user adjustment information for secondary and tertiary areas, for example, in storage device 120. When a user constructs a new progress table for a primary area, system 100 can retrieve the stored adjustment information and automatically generate a two-dimensional table of municipal progress that meets the user's needs based on the user's historical adjustment information for secondary and tertiary areas.

[0111] For example, when the same user constructs multiple primary areas of a municipal project, the processor can use parameters similar to the adjustment information (such as similar sorting methods, intervals, etc.) to generate a list of secondary areas and / or a list of tertiary areas when generating a two-dimensional table of the municipal progress of each subsequent primary area, based on the user's adjustment information such as the order of secondary areas and the interval of tertiary areas when constructing the first primary area.

[0112] In some embodiments, the processor can also acquire the user's adjustment habits for secondary and tertiary areas, and generate corresponding two-dimensional tables of municipal progress based on the user's adjustment habits. For example, different construction units may have different sorting rules for secondary areas and different intervals for dividing tertiary areas, and correspondingly, the generated two-dimensional tables of municipal progress will also be different.

[0113] In some embodiments, the processor (e.g., processor 110) may also obtain a list of existing tertiary regions under the same secondary region based on the secondary region identifier; compare the existing list of tertiary regions with the updated initial list of tertiary regions; and generate a final list of tertiary regions without overlap based on the comparison result.

[0114] A secondary area identifier is a label used to identify a specific secondary area. Secondary area identifiers can include the area's name (e.g., foundation treatment, pier cap construction), ID identifier, etc.

[0115] The list of existing tertiary regions under the same secondary region refers to the collection of all tertiary region lists that have been constructed and belong to the same secondary region.

[0116] In some embodiments, the processor can retrieve all stored (i.e., constructed) tertiary region information under a secondary region by searching a secondary region identifier in a secondary region identifier retrieval system database. The secondary region identifier retrieval system database is a pre-generated database containing the mapping relationships between secondary and tertiary regions. For example, the processor can retrieve all stored tertiary region information under a secondary region (K0+50~K0+150, K0+150~K0+250, K0+250~K0+350) by searching a secondary region identifier "a tunnel-roadbed" in the secondary region identifier retrieval system database.

[0117] In some embodiments, the processor can compare an existing list of level-3 regions with an updated initial list of level-3 regions to determine whether there is any overlap. For example, the level-3 regions “K0+10~K0+90” in the updated initial list of level-3 regions overlap with the level-3 regions “K0+50~K0+150” in the existing list of level-3 regions (K0+50~K0+90).

[0118] In some embodiments, the processor can compare the existing list of level-3 regions and the updated initial list of level-3 regions using a hash table index to determine if there is any overlap. For example, the processor can convert the existing list of level-3 regions into hash values ​​for storage, calculate the hash value of the updated initial list of level-3 regions, and compare the two hash values. If the hash table contains the same / overlapping hash values, it is determined that there is a conflict between the existing list of level-3 regions and the updated initial list of level-3 regions, thereby further improving the efficiency of overlap detection (especially suitable for large projects with a large number of level-3 regions).

[0119] In some embodiments, when the comparison result shows that the existing list of third-level regions and the updated initial list of third-level regions do not overlap, the processor can store the updated initial list of third-level regions as a non-overlapping list of third-level regions, serving as the basis for subsequent generation of progress units. When the comparison result shows that the existing list of third-level regions and the updated initial list of third-level regions overlap, the processor can also mark the overlapping areas on the visualization interface (e.g., highlighting the overlapping area K0+50~K0+90 in red) and provide a prompt (e.g., the text prompt "This mileage segment overlaps with an existing third-level region; please adjust the interval or modify the existing third-level region"). Adjusting the interval refers to adjusting the interval between the third-level regions in the updated initial list of third-level regions. Modifying an existing third-level region refers to adjusting the interval corresponding to the existing list of third-level regions. Taking the user selecting "Adjust Interval" as an example, if the user re-enters "interval is 70m," the processor can adjust the updated initial list of third-level regions based on this interval (e.g., generating a list of third-level regions: K0+10~K0+80, K0+80~K0+150, etc.). In some embodiments, after adjusting the interval or modifying the existing three-level regions, the processor can compare the existing three-level region list and the updated initial three-level region list again until there is no overlap between the two.

[0120] In some embodiments of this specification, users are allowed to adjust the interval of the three-level area division, increasing the flexibility of the three-level area construction and meeting user needs; in addition, by performing overlap / conflict detection on the three-level areas under the same two-level area, overlapping road segments or pier numbers in multiple three-level areas are avoided, thereby improving the accuracy of the two-dimensional table of municipal progress.

[0121] Figure 6This is an exemplary flowchart illustrating the generation of a two-dimensional table of municipal image progress according to some embodiments of this specification. In some embodiments, process 600 may be executed by system 100 (e.g., processor 110). Figure 6 As shown, process 600 includes the following steps.

[0122] Step 610: The processor can determine the width of the horizontal axis corresponding to each third-level region based on the preset total length of the horizontal axis and the sorted list of third-level regions in the system interface.

[0123] The sorted list of third-level regions refers to the list of third-level regions after sorting multiple third-level regions.

[0124] In some embodiments, before generating progress units, the processor may also map segment identifiers in a non-overlapping list of three-level regions based on identifier type; and sort the segments based on the mapping results to generate a sorted list of three-level regions.

[0125] The identification type refers to the category by which the segmentation identification of the three-level area is divided. For example, the identification types include mileage segment type (e.g., K0+10~K0+80), single number with suffix type (e.g., 1#-1), bridge abutment number type (e.g., 0# abutment), and continuous number segment type (e.g., 1#-1~1#-4), etc.

[0126] Segment identifiers refer to the original names of tertiary regions obtained by dividing secondary regions. The segment identifiers for tertiary regions obtained from different secondary region divisions may differ. For example, refer to... Figure 4 The secondary area bridge deck pavement is segmented by markings such as "0-2" and "2-4"; the secondary area bridge abutments are segmented by markings such as "0# abutment" and "9# abutment".

[0127] Mapping refers to the process of converting non-standardized segment identifiers into standardized numerical values ​​or numerical ranges.

[0128] In some embodiments, the processor can traverse a list of non-overlapping three-level regions and determine the identifier type through keyword matching, format validation, and other methods. For example, a segment identifier containing "K+" or "~" and conforming to a mileage format (e.g., Kxx+xx~Kxx+xx) is a mileage segment identifier; a segment identifier containing "#" and a hyphen suffix (e.g., x#-x) is a single-number suffix identifier; a segment identifier containing "#" is a bridge abutment number identifier; and a segment identifier containing "#" and "~" (e.g., x#-x~x#-x) is a consecutive number segment identifier. In some embodiments, the user can also manually input the identifier type of the segment identifier.

[0129] In some embodiments, the processor can map segment identifiers in a non-overlapping three-level region list based on the identifier type using a preset mapping rule base.

[0130] The preset mapping rule base is a set of preset rules that convert segmented identifiers into standardized numerical values ​​or numerical ranges based on the identifier type.

[0131] For example, if the processor determines that the identifier type of the third-level region is a mileage segment type (e.g., K0+10~K0+80), the processor can extract mileage segment type mapping rules from a preset mapping rule library. For example, the mileage segment type mapping rules include extracting the starting mileage value (10) and the ending mileage value (80), mapping them to the format "starting value-ending value" (10-80). Another example is if the identifier type is a single-number with a suffix type (e.g., 1#-1), the single-number with a suffix type mapping rules include taking the main number as an integer (1), converting the suffix to a decimal (1÷10=0.1), and mapping the result to "1.1". Yet another example is if the identifier type is a bridge abutment number type (e.g., 0# abutment), the bridge abutment number type abutment mapping rules include taking the number as an integer (0), adding a fixed offset (0.5), mapping it to "0.5", and if the segment identifier is 1# abutment, then it is mapped to "1.5", etc. For other numbered identifier types (such as piers, columns, slabs, etc.), a similar mapping method to that used for bridge abutment numbering can be used, requiring only modification of the fixed offset. For example, pier #1 can be mapped to "1.1", column #1 to "1.2", slab #1 to "1.3", etc., with a corresponding fixed offset of 0.1. As another example, for identifier types with consecutive numbered segments (such as 1#-1 to 1#-4), the mapping rule includes splitting the starting identifier (1#-1→1.1) and the ending identifier (1#-4→1.4), mapping it to "1.1-1.4". It should be noted that the above descriptions of mapping rules are merely examples; those skilled in the art can also use other suitable mapping rules to map segmented identifiers.

[0132] In some embodiments, the processor can sort the three-level regions in ascending order of the mapped values ​​(or the start / end values ​​of the value range) to generate a sorted list of three-level regions. For example, 10-80 < 80-150 < 150-220 < 220-290 < 290-400.

[0133] In some embodiments, after sorting, the processor can also retain the segment identifiers of the three-level regions to obtain a sorted list of three-level regions. That is, the mapped values ​​are only used to determine the horizontal axis position, and the segment identifiers of the three-level regions are still displayed in the two-dimensional table of municipal image progress. For example, the sorted list of three-level regions is (K0+10~K0+80, K0+80~K0+150, K0+150~K0+220, K0+220~K0+400).

[0134] Understandably, since segmentation identifiers are usually non-standardized, it is generally difficult to directly sort the three-level areas using segmentation identifiers. In the embodiments of this specification, non-standardized classification identifiers are converted into standard numerical values ​​or numerical ranges through mapping, which can quickly and conveniently sort the three-level areas according to the size of the numerical values ​​or numerical ranges. The progress of municipal image display is more intuitive, making it convenient for users to view and record information.

[0135] The system interface's preset total horizontal axis length refers to the preset total length of the horizontal axis corresponding to all three levels of areas in the visual interface. Figure 4 For example, the system interface can preset the total length of the horizontal axis as the horizontal axis of a two-dimensional table representing the progress of the municipal image (i.e., Figure 4 The total length along the horizontal axis (in the Y direction). For example, the preset total length of the horizontal axis in the system interface can be 1200 pixels, 1500 pixels, 1800 pixels, etc. The system interface refers to the visual interface of system 100.

[0136] The horizontal width corresponding to each level 3 area refers to the display width of a single level 3 area on the horizontal axis. See also... Figure 4 The horizontal axis width corresponding to a level 3 region can refer to the width of a single level 3 region on the horizontal axis (i.e., Figure 4 The width of a tertiary region (in the Y direction) is the width of a single cell in the Y direction. Different types of secondary regions correspond to different numbers of tertiary regions; therefore, the horizontal width of a single tertiary region corresponding to a different secondary region may also differ. For example, the horizontal width of a single tertiary region corresponding to bridge deck paving in the secondary region is different from the horizontal width of a single tertiary region corresponding to beam erection in the secondary region.

[0137] In some embodiments, the processor may determine the horizontal axis width corresponding to each tertiary region by: calculating the total numerical span of the primary region; calculating the regional numerical span of each tertiary region; and determining the horizontal axis width corresponding to each tertiary region based on the total numerical span of the primary region, the regional numerical span of each tertiary region, and the system interface preset total horizontal axis length.

[0138] The total numerical span of a primary region refers to the total span of standardized values ​​after mapping. In some embodiments, the processor can determine the starting and ending values ​​of a primary region based on the mapping results of a sorted list of tertiary regions, and determine the total numerical span of the primary region based on the difference between the starting and ending values. The starting value of a primary region is the minimum value in the sorted list of tertiary regions; the ending value is the maximum value in the sorted list of tertiary regions. For example, if the tertiary region mapping results for a primary region roadbed are (10-80, 80-150, 150-220, 220-400), with a starting value of 10 and an ending value of 400, the total numerical span is 400-10=390. As another example, if the tertiary region mapping results for a primary region bridge abutment are (1, 2, 3, 4, 5), with a starting value of 1 and an ending value of 5, the total numerical span is 5-1=4.

[0139] The regional numerical span of a Level 3 region refers to the span of the standardized numerical values ​​of a single Level 3 region after mapping. For example, the mapping result of the mileage segment type Level 3 region "K0+10~K0+80" is (10-80), and the regional numerical span is 80-10=70; the numerical span of the single-number type Level 3 region (such as Pier 1) is 1; the mapping result of the continuous number segment type Level 3 region "1#-1~1#-4" is (1.1-1.4), and the regional numerical span is 1.4-1.1=0.3.

[0140] In some embodiments, the horizontal axis width corresponding to a single level-3 region can be determined based on the total numerical span of the level-1 regions, the numerical span of each level-3 region, and the system interface's preset total horizontal axis length. For example, the horizontal axis width corresponding to a single level-3 region = (regional numerical span ÷ total numerical span of the level-1 regions) × system interface's preset total horizontal axis length. For instance, if the total numerical span of the level-1 regions is 390m, the system's preset total horizontal axis length is 1200 pixels, and the numerical span of a certain level-3 region is 70m, its horizontal axis width = (70 ÷ 390) × 1200 ≈ 215.4 pixels. The processor can determine the horizontal axis width corresponding to each level-3 region based on the above method.

[0141] Step 620: The processor can arrange the segment identifiers of each third-level region sequentially based on the horizontal axis width.

[0142] In some embodiments, the processor can render and arrange the segment identifiers of each tertiary region in a visual interface based on the horizontal axis width of each tertiary region and the order of the tertiary regions in the sorted tertiary region list.

[0143] Step 630: The processor can arrange each secondary region identifier based on the secondary region list.

[0144] Second-level area identifiers refer to the name identifiers of second-level areas. For example, see... Figure 4 Secondary area markings may include bridge deck paving, beam erection, and beam prefabrication.

[0145] In some embodiments, the processor (e.g., processor 110) can also render and arrange each secondary region sequentially according to the order of the secondary regions in the secondary region list in a visualization interface. The secondary region list can be an updated secondary region list or an initial secondary region list.

[0146] In step 640, the processor can intersect the segment identifiers of each third-level area and the identifiers of each second-level area to generate multiple progress units, thereby generating a two-dimensional table of municipal image progress.

[0147] In some embodiments, the processor (e.g., processor 110) can use the segment identifiers of each sequentially arranged tertiary region as the horizontal axis and the identifiers of each sequentially arranged secondary region as the vertical axis to intersect and form multiple progress units. A single progress unit corresponds to a single cell in a two-dimensional table and is the smallest visual unit for progress management, associated with the progress data of "process-construction segment" (i.e., secondary region-a certain tertiary region).

[0148] In some embodiments, users can also click on the progress cells in the two-dimensional table of municipal image progress. The progress cells clicked by the user will be highlighted in the visualization interface so that the user can quickly locate the spatial location of the selected project.

[0149] In some embodiments, the processor can also use the segmentation identifiers of each tertiary region arranged in sequence as the vertical axis and the identifiers of each secondary region arranged in sequence as the horizontal axis to generate a two-dimensional table of municipal image progress.

[0150] In some embodiments, for projects with "linear extension" such as tunnels and utility tunnels, the processor can also change the horizontal and / or vertical axes to a "scroll bar display". For example, when the number of tertiary areas contained in a secondary area is large (e.g., more than 10 segments), a scroll bar is displayed on the right side of the horizontal axis, allowing users to scroll left and right to view all tertiary areas. In this case, the horizontal axis width corresponding to each tertiary area can also be determined using the same method as in step 610, improving the display compatibility of large projects.

[0151] In some embodiments of this specification, determining the horizontal axis width of each third-level area and rendering a two-dimensional table of municipal progress can achieve a ratio match between the physical length of the construction area and the horizontal axis width, thereby improving the visualization effect of municipal progress.

[0152] Figure 7This is an exemplary flowchart illustrating the updating of a two-dimensional table of municipal image progress according to some embodiments of this specification. In some embodiments, process 700 may be executed by system 100 (e.g., processor 110). Figure 7 As shown, process 700 includes the following steps.

[0153] Step 710: The processor can obtain a list of tasks to be processed.

[0154] The pending task list refers to the collection of all task orders awaiting progress-related processing. The pending task list includes different types of task orders, such as new task order acceptance and mid-term task order supplementation.

[0155] In some embodiments, the list of tasks to be processed can be obtained by a user through a visual interface. The list of tasks to be processed can also be pre-stored in a storage device (such as storage device 120), and the processor (e.g., processor 110) reads the list of tasks to be processed from the storage device through an interface.

[0156] In some embodiments, the processor can also determine the type of task in the task list to be processed; in response to the task list to be processed including new task acceptance, the processor executes steps 720 to 740; in response to the task list to be processed including mid-term entry of task supplement, the processor executes steps 750 to 770; in response to the task list to be processed including both new task acceptance and mid-term entry of task supplement, the processor can execute steps 720 to 740 and steps 750 to 770 simultaneously (or based on a preset order).

[0157] In some embodiments, the processor can parse the list of tasks to be processed to determine the type of tasks in the list. For example, the processor can iterate through the list of tasks to be processed and filter based on the "Task Type" field to see if it includes tasks marked as "New Task Acceptance" and / or "Mid-term Inbound Task Supplement".

[0158] Step 720: The processor can extract the task order information of the new task order.

[0159] New task order acceptance refers to the process by which a user enters an acceptance task order into the system after a construction task has been completed and manually inspected within a primary area of ​​the municipal progress two-dimensional table already generated in System 100. A new task order is a task order entered into System 100 by the user after a construction task has been completed and inspected.

[0160] The task information for a new task order refers to information related to the acceptance of the new task order. For example, the task information for a new task order includes the construction location (associated with secondary and tertiary areas), acceptance status (e.g., accepted, partially accepted, failed, etc.), acceptance percentage (e.g., 100%, 70%, etc.), acceptance time, and the person responsible for acceptance.

[0161] In some embodiments, the task information for a new task can be manually entered into the system 100 by the user, or it can be extracted directly from the new task by the processor.

[0162] Step 730: The processor can split the new task order based on the task order information.

[0163] Breaking down a new task order refers to the process of dividing the "construction location" information of the new task order into corresponding secondary and tertiary areas, and task status. Breaking down a new task order clarifies the progress unit corresponding to the task order and the relationship between the new task order and the two-dimensional table of municipal progress.

[0164] In some embodiments, the processor can split a new task order into secondary and tertiary regions according to preset splitting rules, and extract the corresponding secondary and tertiary region information. For example, if a new task order is "a certain tunnel subgrade - K0+10~K0+80-foundation treatment, task status: accepted", then the task order can be split into: secondary region = foundation treatment, tertiary region = K0+10~K0+80, status = accepted.

[0165] Step 740: The processor can update the two-dimensional table of municipal image progress based on the splitting results to obtain the updated two-dimensional table of municipal image progress.

[0166] The splitting result refers to the result obtained by splitting the new task order.

[0167] In some embodiments, the processor can systematically locate the vertical axis position of the two-dimensional table of municipal progress corresponding to the new task order based on the secondary area information (e.g., "secondary area = foundation treatment") in the splitting results, and locate the horizontal axis position of the two-dimensional table of municipal progress corresponding to the new task order based on the tertiary area information (e.g., "tertiary area = K0+10~K0+80") in the splitting results; determine the progress cell where the secondary and tertiary areas intersect (e.g., the progress cell for "foundation treatment - K0+10~K0+80") based on the located vertical and horizontal axis positions; update the status of the determined progress cell where the secondary and tertiary areas intersect based on the acceptance status and acceptance ratio in the splitting results, for example, highlighting the background in green, displaying "accepted" and the progress percentage "100%", thus obtaining the updated progress table.

[0168] In some embodiments of this specification, the progress of accepted task orders is automatically updated, improving the efficiency of progress updates. The construction progress of each task and each area can be displayed in a timely and intuitive way in the two-dimensional table of municipal image progress.

[0169] Step 750: The processor can obtain a list of historical task orders to be supplemented based on the primary region identifier of the task order that is entered midway and the time range before the entry time.

[0170] Mid-term task entry refers to the process of adding completed or partially completed construction tasks to the municipal engineering project's system 100 after a two-dimensional progress table of municipal engineering projects has been generated during construction (excluding the initial project phase). A mid-term task entry form is a task sheet added during the middle of a municipal engineering project's construction process, corresponding to completed or partially completed construction tasks. The mid-term task entry form includes information such as the primary area identifier, entry time, and acceptance status.

[0171] A primary area identifier is a label that identifies a specific primary area. Primary area identifiers can include type identifiers (such as roadbed, pavement, bridge, culvert, tunnel, etc.) and ID identifiers for the primary area.

[0172] The entry time refers to the period from the actual start of construction of a municipal engineering project to its entry into the system (up to 100 records). The entry time can limit the filtering scope of historical task orders, ensuring that only construction tasks of municipal engineering projects before their entry into the system (up to 100 records) are added, thus avoiding duplicate entries.

[0173] The list of historical task orders to be added refers to the collection of 100 historical construction task orders that need to be added to the system.

[0174] In some embodiments, users can select a primary area identifier (such as "bridge") and set an entry time (such as September 2025) through a visual interface. The system automatically generates a time range prior to the entry time (such as January 2025 to September 2025). Users can also manually adjust the time range prior to the entry time through the visual interface. In some embodiments, the processor can search a preset historical task order database for task orders whose primary area identifier matches the user-input primary area identifier, whose creation time falls within the time range prior to the entry time, and whose task status is pending acceptance / accepted. These task orders are then used as a list of historical task orders to be added. The primary area identifier in the list of historical task orders to be added is the same as the primary area identifier of the current municipal project. In some embodiments, the entry time can be the time when the municipal project enters the system 100. The entry time can be obtained directly; for example, when a user performs a municipal project creation operation in system 100, the processor 110 obtains the time corresponding to the creation operation, which is the entry time. The time range prior to the entry time refers to the time range between the start time of the municipal project and the time when the municipal project enters the system 100. The time range prior to the entry time can be obtained by the user through terminal 140 input, or extracted based on the information input by the user through terminal 140.

[0175] Step 760: The processor can determine the matching result between the historical task list and the third-level region based on a preset algorithm.

[0176] The preset algorithm refers to the algorithm used to calculate the three-level regional similarity between historical task orders and current municipal projects. For example, the preset algorithm may include Levenshtein edit distance and Jaccard similarity.

[0177] The matching result refers to the association result between the historical task order and the third-level area. For example, the matching result includes single-area matching success, multi-area matching success, and matching failure. Among them, single-area matching success means that the historical task order is matched with only one third-level area, and the historical task order is automatically associated with the corresponding third-level area (such as "1# Pier Abutment" matching only one third-level area); multi-area matching success means that the historical task order is matched with multiple third-level areas, and the system can prompt the user to manually select the third-level areas to be associated through a pop-up window (such as "K0+10~K0+100" matching "Subgrade-K0+10~K0+100" and "Base-K0+10~K0+100"); matching failure means that the similarity between the historical task order and all the third-level areas of the current municipal project is less than the similarity threshold, and it is marked "Pending manual matching" and the "Construction Location" input box is displayed.

[0178] Taking a preset algorithm including Levenshtein edit distance and Jaccard similarity as an example, the processor can calculate the Jaccard similarity between each historical task order and the corresponding third-level regions in the list of third-level regions for the current municipal engineering first-level region (e.g., calculating the Jaccard similarity between the task order "Construction of Pier #1" and the third-level region "Pier #1"). It then filters out third-level regions whose Jaccard similarity is greater than or equal to a first threshold (e.g., 80%). Next, it calculates the Levenshtein edit distance between the historical task order and the filtered third-level regions. When the Levenshtein edit distance meets preset conditions, it determines that the historical task order and the filtered third-level region have successfully matched. Exemplary preset conditions include the Levenshtein edit distance between the historical task order and the third-level region being less than a second threshold.

[0179] In some embodiments, the preset algorithm may further include a cosine similarity algorithm. For example, the processor can convert the construction location and level-3 area identifier of the historical task order into text vectors (e.g., "1# pier cap" is converted into vector [1,0,1,0]), calculate the cosine similarity between the text vectors, and determine that the historical task order and the level-3 area of ​​the current municipal project are successfully matched when the cosine similarity between the text vectors is greater than a first threshold. The cosine similarity algorithm is more efficient in matching long texts (e.g., construction locations containing multiple descriptive words).

[0180] Step 770: Based on the matching results and the acceptance status of the intermediate entry task orders, the processor can update the information of the corresponding progress unit and obtain a two-dimensional table of the municipal image progress and / or a supplementary entry report for the batch completion of supplementary entry.

[0181] In some embodiments, the processor can classify and process historical task orders to be supplemented based on different matching results. It automatically associates the historical task orders to be supplemented with progress units, updates the progress status of the progress units, and finally generates a two-dimensional table of municipal image progress and a supplementation report, ensuring complete synchronization of historical progress.

[0182] For example, for automatically associated historical task orders (i.e., the matching result is a successful match for a single region), the processor updates the corresponding progress cell (e.g., green for accepted, yellow for pending acceptance) according to the acceptance status of the historical task order; for historical task orders requiring manual matching (i.e., the matching result is a successful match for multiple regions or a failed match), the processor displays multiple matched third-level regions through a visual interface pop-up. The user manually selects the third-level regions to be associated with the historical task order, and the system updates the corresponding progress cell according to the acceptance status of the historical task order (or the user directly enters the corresponding third-level region through the construction location input box). In some embodiments, for historical task orders requiring manual matching, in addition to manual selection by the user, the processor can also determine the final associated third-level regions based on preset automatic matching rules. For example, users can pre-set priority rules for associating historical task orders with third-level regions. The system combines the user's historical operation data when handling similar task orders with preset rules derived from statistical analysis of the entire project data. For task orders that successfully match multiple regions (e.g., "K0+10~K0+100 construction" matching "subgrade-K0+10~K0+100" and "base course-K0+10~K0+100"), the system automatically selects the subgrade-level third-level region according to the priority rules. For task orders that fail to match (e.g., "1# pier pouring" with no direct match), the system automatically associates the third-level region "1# pier" with the highest similarity and that conforms to the user's habits, based on historical operation data and statistical rules, achieving accurate association between historical task orders and third-level regions without manual intervention.

[0183] In some embodiments, after the construction progress of all progress cells in the municipal progress two-dimensional table is updated, a municipal progress two-dimensional table with batch supplementary data is obtained and / or a supplementary data report is generated. The supplementary data report refers to a structured report generated after the batch supplementary data entry of intermediate task orders is completed. The supplementary data report records the overall supplementary data entry status of historical task orders, including information such as the number of task orders supplemented, the number of successful supplementary data entries, and the number of failed supplementary data entries.

[0184] In some embodiments of this specification, for projects that are added midway through the project, a preset algorithm is used to determine the matching result between the historical task list to be supplemented and the current municipal project, so as to realize the automatic batch supplementation of the historical progress of projects that are added midway through the project, which greatly shortens the supplementation time, meets the batch supplementation needs of projects that are added midway through the project, and makes the two-dimensional table of municipal image progress closer to the actual progress of municipal projects.

[0185] In some embodiments, the processor can also query all associated data based on the secondary and tertiary region identifiers of the progress unit; and generate a structured progress details page based on the all associated data and the details page display requirements.

[0186] A level 3 area identifier is a label that identifies a specific level 3 area. Level 3 area identifiers may include segmentation identifiers and ID identifiers for the level 3 area.

[0187] Full-scale associated data refers to all structured data related to the target progress unit. The target progress unit is the progress unit that the user wants to view; for example, the target progress unit could be the progress unit that the user clicks on.

[0188] In some embodiments, the full-volume associated data includes at least one of progress information, associated documents, resource data, and risk information.

[0189] Progress information refers to data reflecting the construction progress status of a progress unit. For example, progress information includes acceptance status (such as accepted, partially accepted, pending acceptance, and failed acceptance), progress percentage (such as 100% and 70%), planned completion time, and actual completion time.

[0190] Related documents refer to various documents associated with a progress unit. For example, related documents include task sheets (including number and inspector), inspection records (e.g., the last 3, arranged in reverse chronological order), rectification orders (e.g., 1 item not yet completed), and acceptance reports. A task sheet is a document that clearly defines the scope, requirements, and acceptance responsibilities of a construction task, including its number and inspector information. Inspection records are recent (e.g., the last 3) inspection records related to construction quality and safety, arranged in reverse chronological order. A rectification order is a document that specifies rectification requirements, deadlines, and incomplete status for problems discovered during inspections. An acceptance report is a document that records the acceptance process and results after the construction task is completed.

[0191] Resource data refers to the quantified data set of resources consumed during the construction process of a schedule unit, such as manpower, working hours, and costs. For example, resource data includes the number of workers with normal attendance, planned man-days consumed, actual man-days consumed, and confirmed work-day amounts.

[0192] Risk information refers to data related to safety risks involved in the construction of a progress unit. For example, risk information includes critical and major projects (such as project name, filing status, and special construction plan number), hazard sources (such as hazard source name, risk level, and identification time), risk control measures (such as specific protection requirements, inspection frequency, and responsible personnel), and risk warning records.

[0193] In some embodiments, the full associated data can be stored in a storage device (such as storage device 120), and the processor can query the full associated data corresponding to the progress unit from the storage device based on the secondary region identifier and the tertiary region identifier of the progress unit.

[0194] The requirements for the progress details page refer to the user's visualization and functional needs for the progress details page. The progress details page is a page that displays all related data for each progress unit. For example, the requirements for the details page include displaying data by section, supporting document downloads, analyzing related resources, and viewing risk control measures.

[0195] In some embodiments, the processor can render the progress detail page based on the full set of associated data and the display requirements of the detail page, generating a structured progress detail page. A structured progress detail page refers to a visual page rendered according to preset partitions (such as progress information area, associated document area, resource data area, and risk information area).

[0196] For example, the processor can render the details page into four sections: progress information, related documents, resource data, and risk information. For instance, the progress information section can be rendered at the top of the page, displaying data such as acceptance status, progress percentage, and construction task completion time; the related documents section can be rendered on the left side of the page, displaying relevant documents such as task orders, inspection records, rectification orders, and acceptance reports, which users can click to view detailed information; the resource data section can be rendered on the right side of the page, displaying data such as the number of workers, planned workdays, actual workdays, and recorded wages, and also includes a "Resource Analysis" jump button, which users can click to obtain a detailed resource analysis report; and the risk information section can be rendered at the bottom of the page, displaying critical and major projects, hazard sources, risk control measures, and risk warning records.

[0197] In some embodiments of this specification, the details page integrates all related data such as progress information, associated documents, resource data, and risk information, which facilitates the management of project progress, resources, and risks and supports multi-party collaborative decision-making.

[0198] It should be noted that the above descriptions of processes 200, 500, 600, and 700 are for illustrative purposes only and do not limit the scope of this specification. Those skilled in the art can make various modifications and changes to processes 200, 500, 600, and 700 under the guidance of this specification. However, these modifications and changes remain within the scope of this specification.

[0199] Figure 8 This is an exemplary block diagram of a processor for a system that generates visual progress charts of municipal engineering projects according to some embodiments of this specification. Figure 8 As shown, the processor 110 includes an acquisition module 111, a first generation module 112, a second generation module 113, and a third generation module 114.

[0200] The acquisition module 111 is configured to acquire parameter information of the primary area of ​​the municipal engineering project. The primary area is the construction area included in the municipal engineering project, and the parameter information includes basic parameters and core parameters. In some embodiments, the basic parameters include the type of the primary area, and the core parameters include the length of the construction area of ​​the primary area and / or the number of construction projects.

[0201] The first generation module 112 is configured to generate a list of second-level regions that match the first-level regions based on basic parameters and using a first preset rule base. The list of second-level regions reflects the construction sequence of the second-level regions contained in the first-level regions.

[0202] In some embodiments, the first generation module 112 is further configured to generate an initial list of secondary regions matching the primary regions based on basic parameters and using a first preset rule base; and to generate a secondary region list based on user input information and the initial list of secondary regions.

[0203] The second generation module 113 is configured to generate a list of tertiary regions that match the secondary regions based on core parameters and using a second preset rule base; the tertiary regions reflect the construction sections contained in each secondary region.

[0204] In some embodiments, the second generation module 113 is further configured to generate an initial list of tertiary regions matching the secondary regions based on core parameters and using a second preset rule base, and trigger a custom interval entry; obtain a custom interval input by the user based on the custom interval entry; and update the initial list of tertiary regions based on the custom interval.

[0205] In some embodiments, the second generation module 113 is further configured to obtain a list of existing tertiary regions under the same secondary region based on the secondary region identifier; compare the existing list of tertiary regions with the updated initial list of tertiary regions; and generate a list of non-overlapping tertiary regions based on the comparison result.

[0206] In some embodiments, the second generation module 113 is further configured to map segment identifiers in a non-overlapping list of three-level regions based on the identifier type; and to sort the regions based on the mapping results to generate a sorted list of three-level regions.

[0207] The third generation module 114 is configured to generate multiple progress units based on the secondary region list and the tertiary region list; each progress unit corresponds to one secondary region and one tertiary region. Different types of secondary regions correspond to different tertiary region generation rules.

[0208] In some embodiments, the third generation module 114 is further configured to determine the horizontal axis width corresponding to each third-level region based on the total length of the horizontal axis preset in the system interface and the sorted list of third-level regions; arrange the segment identifiers of each third-level region in sequence based on the horizontal axis width; arrange the identifiers of each second-level region based on the list of second-level regions; and intersect the segment identifiers of each third-level region and each second-level region identifier in sequence to generate multiple progress units, thereby generating a two-dimensional table of municipal image progress.

[0209] In some embodiments, the third generation module 114 is further configured to obtain a list of pending task orders; in response to the pending task order list including the acceptance of new task orders, extract the task order information of the new task orders; split the new task orders based on the task order information; and update the two-dimensional table of municipal image progress based on the splitting result to obtain the updated two-dimensional table of municipal image progress.

[0210] In some embodiments, in response to the pending task list including mid-term entry task lists for supplementation, the third generation module 114 is further configured to obtain a list of historical task lists to be supplemented based on the primary area identifier of the mid-term entry task list and the time range before the entry time; determine the matching result between the historical task list and the tertiary area based on a preset algorithm; and update the information of the corresponding progress unit based on the matching result and the acceptance status of the mid-term entry task lists to obtain a two-dimensional table of municipal image progress and / or a supplementation report for the batch supplementation completion.

[0211] In some embodiments, the processor 110 further includes a preset rule base generation module (not shown in the figure). The preset rule base generation module is configured to generate a first preset rule base and / or a second preset rule base.

[0212] In some embodiments, the preset rule base generation module is configured to obtain the type of the primary area and the municipal construction spatial logic; based on the type of the primary area and the municipal construction spatial logic, preset the vertical axis sorting of each secondary area to generate a first preset rule base.

[0213] In some embodiments, the preset rule base generation module is configured to obtain the municipal three-level area division requirements; based on the municipal three-level area division requirements, set three-level area generation rules for each second-level area to generate a second preset rule base.

[0214] This specification also provides an apparatus for generating a visual progress report of a municipal engineering project. The apparatus includes at least one storage medium and at least one processor. The at least one storage medium is used to store computer instructions. The at least one processor is used to execute the computer instructions to implement the method for generating a visual progress report of a municipal engineering project as described in any of the above embodiments.

[0215] The basic concepts have been described above. Obviously, for those skilled in the art, the detailed disclosure above is merely illustrative and does not constitute a limitation of this specification. Furthermore, this specification uses specific terms to describe embodiments thereof. For example, "an embodiment," "one embodiment," and / or "some embodiments" refer to a particular feature, structure, or characteristic related to at least one embodiment of this specification. Therefore, it should be emphasized and noted that "an embodiment," "one embodiment," or "an alternative embodiment" mentioned twice or more in different locations in this specification do not necessarily refer to the same embodiment.

[0216] It should be noted that, in order to simplify the descriptions disclosed herein and thus aid in the understanding of one or more embodiments, the foregoing description of embodiments in this specification sometimes combines multiple features into a single embodiment, drawing, or description thereof. However, this method of disclosure does not imply that the subject matter of this specification requires more features than those mentioned in the claims. In fact, the embodiments contain fewer features than all the features of the single embodiments disclosed above.

Claims

1. A system for generating visual progress reports for municipal engineering projects, characterized in that, Includes at least one processor and a storage device communicating with said at least one processor, said at least one processor being used to perform: Obtain parameter information for the primary area of ​​the municipal engineering project, wherein the primary area is the construction area included in the municipal engineering project, and the parameter information includes basic parameters and core parameters; Based on the aforementioned basic parameters, a list of secondary regions matching the primary region is generated using a first preset rule base. This list of secondary regions reflects the construction sequence of the secondary regions included in the primary region. The first preset rule base is generated in the following manner: Obtain the type of the primary area and the spatial logic of municipal construction; Based on the type of the primary region and the municipal construction space logic, the vertical axis sorting of each secondary region is preset to generate the first preset rule base; Based on the core parameters, a list of tertiary regions matching the secondary regions is generated using a second preset rule base. The tertiary regions reflect the construction sections contained within each secondary region. The second preset rule base is generated in the following manner: Obtain the municipal three-level regional division requirements; Based on the aforementioned municipal three-level regional division requirements, three-level regional generation rules are set for each of the two-level regions to generate the second preset rule library; Based on the secondary area list and the tertiary area list, multiple progress units are generated, each progress unit corresponding to one secondary area and one tertiary area; the progress unit is the smallest progress management unit of the municipal project; the progress unit corresponds to a single cell in the two-dimensional table of municipal image progress. Different types of secondary regions correspond to different tertiary region generation rules; the at least one processor is further configured to execute: Based on the core parameters, using the second preset rule base, an initial list of tertiary regions matching the secondary regions is generated, and a custom interval entry is triggered; Based on the custom interval entry, obtain the user-inputted custom interval; Update the initial three-level region list based on the custom interval; Furthermore, the at least one processor is further configured to perform: Based on the system interface's preset total horizontal axis length and the sorted list of the three-level regions, the horizontal axis width corresponding to each of the three-level regions is determined. Based on the horizontal axis width, the segmentation identifiers of each of the three-level regions are arranged sequentially; Based on the list of secondary regions, arrange the identifiers of each secondary region; The segmentation identifiers of each of the three-level regions and the identifiers of each of the two-level regions are intersected to generate multiple progress units, thereby generating the two-dimensional table of the municipal image progress.

2. The system for generating visual progress reports for municipal engineering projects as described in claim 1, characterized in that, The basic parameters include the type of the primary region, and the core parameters include the length of the construction area and / or the number of construction projects in the primary region.

3. The system for generating visual progress reports for municipal engineering projects as described in claim 1, characterized in that, The at least one processor is also configured to perform: Based on the aforementioned basic parameters, an initial list of secondary regions matching the primary region is generated using the first preset rule base. The secondary region list is generated based on user input information and the initial secondary region list.

4. The system for generating visual progress reports for municipal engineering projects as described in claim 1, characterized in that, The at least one processor is also configured to perform: Based on the secondary region identifier, obtain a list of existing tertiary regions under the same secondary region; Compare the existing three-level region list with the updated initial three-level region list; Based on the comparison results, a list of non-overlapping three-level regions is generated.

5. The system for generating visual progress reports for municipal engineering projects as described in claim 4, characterized in that, Before generating the progress unit, the at least one processor is also configured to perform: Based on the identifier type, the segment identifiers in the non-overlapping three-level region list are mapped; The mapping results are sorted to generate a sorted list of the three-level regions.

6. The system for generating visual progress reports for municipal engineering projects as described in claim 5, characterized in that, The at least one processor is also configured to perform: Get the list of pending tasks; In response to the pending task list including new task acceptance, Extract the task information of the new task order; Based on the task order information, the new task order is split; The municipal image progress two-dimensional table is updated based on the splitting results to obtain the municipal image progress two-dimensional table with updated status.

7. The system for generating visual progress reports for municipal engineering projects as described in claim 6, characterized in that, The at least one processor is also configured to perform: In response to the pending task list including tasks added midway through processing, Based on the primary region identifier of the mid-term entry task order and the time range before the entry time, obtain the list of historical task orders to be supplemented. Based on a preset algorithm, the matching result between the historical task list and the third-level region is determined; Based on the matching results and the acceptance status of the intermediate entry task orders, update the information of the corresponding progress unit to obtain the two-dimensional table of the municipal image progress and / or the supplementary entry report after the batch supplementary entry is completed.

8. A system for generating visual progress reports for municipal engineering projects, characterized in that, Includes at least one processor and a storage device communicating with said at least one processor, said at least one processor comprising: The acquisition module is configured to acquire parameter information of the primary area of ​​the municipal engineering project; the primary area is the construction area included in the municipal engineering project, and the parameter information includes basic parameters and core parameters. The first generation module is configured to generate a list of secondary regions matching the primary region based on the aforementioned basic parameters and using a first preset rule base; the list of secondary regions reflects the construction sequence of the secondary regions included in the primary region; the first generation module is further configured to: Obtain the type of the primary area and the spatial logic of municipal construction; Based on the type of the primary region and the municipal construction space logic, the vertical axis sorting of each secondary region is preset to generate the first preset rule base; The second generation module is configured to generate a list of tertiary regions matching the secondary regions based on the core parameters and using a second preset rule base; the tertiary regions reflect the construction sections contained in each secondary region; the second generation module is further configured to: Obtain the municipal three-level regional division requirements; Based on the aforementioned municipal three-level regional division requirements, three-level regional generation rules are set for each of the two-level regions to generate the second preset rule library; The third generation module is configured to generate multiple progress units based on the secondary area list and the tertiary area list; each progress unit corresponds to one secondary area and one tertiary area; the progress unit is the smallest progress management unit of the municipal project; the progress unit corresponds to a single cell in the two-dimensional table of municipal image progress; the third generation module is further configured to: Based on the core parameters, using the second preset rule base, an initial list of tertiary regions matching the secondary regions is generated, and a custom interval entry is triggered; Based on the custom interval entry, obtain the user-inputted custom interval; Update the initial three-level region list based on the custom interval; Furthermore, the third generation module is further configured as follows: Based on the system interface's preset total horizontal axis length and the sorted list of the three-level regions, the horizontal axis width corresponding to each of the three-level regions is determined. Based on the horizontal axis width, the segmentation identifiers of each of the three-level regions are arranged sequentially; Based on the list of secondary regions, arrange the identifiers of each secondary region; The segmentation identifiers of each of the three-level regions and the identifiers of each of the two-level regions are intersected to generate multiple progress units, thereby generating the two-dimensional table of the municipal image progress; Different types of secondary regions correspond to different rules for generating tertiary regions.

9. A method for generating a visual progress chart of a municipal engineering project, characterized in that, The method includes: Obtain parameter information for the primary area of ​​the municipal engineering project, wherein the primary area is the construction area included in the municipal engineering project, and the parameter information includes basic parameters and core parameters; Based on the aforementioned basic parameters, a list of secondary regions matching the primary region is generated using a first preset rule base. This list of secondary regions reflects the construction sequence of the secondary regions included in the primary region. The first preset rule base is generated in the following manner: Obtain the type of the primary area and the municipal construction space logic; Based on the type of the primary region and the municipal construction space logic, the vertical axis sorting of each secondary region is preset to generate the first preset rule base; Based on the core parameters, a list of tertiary regions matching the secondary regions is generated using a second preset rule base. The tertiary regions reflect the construction sections contained within each secondary region. The second preset rule base is generated in the following manner: Obtain the municipal three-level regional division requirements; Based on the aforementioned municipal three-level regional division requirements, three-level regional generation rules are set for each of the two-level regions to generate the second preset rule library; Based on the secondary area list and the tertiary area list, multiple progress units are generated, each progress unit corresponding to one secondary area and one tertiary area; the progress unit is the smallest progress management unit of the municipal project; the progress unit corresponds to a single cell in the two-dimensional table of municipal image progress. Different types of secondary regions correspond to different tertiary region generation rules; the method further includes: Based on the core parameters, using the second preset rule base, an initial list of tertiary regions matching the secondary regions is generated, and a custom interval entry is triggered; Based on the custom interval entry, obtain the user-inputted custom interval; Update the initial three-level region list based on the custom interval; And, the method further includes: Based on the system interface's preset total horizontal axis length and the sorted list of the three-level regions, the horizontal axis width corresponding to each of the three-level regions is determined. Based on the horizontal axis width, the segmentation identifiers of each of the three-level regions are arranged sequentially; Based on the list of secondary regions, arrange the identifiers of each secondary region; The segmentation identifiers of each of the three-level regions and the identifiers of each of the two-level regions are intersected to generate multiple progress units, thereby generating the two-dimensional table of the municipal image progress.

10. A device for generating visual progress reports for municipal engineering projects, characterized in that, The device includes at least one storage medium and at least one processor; The at least one storage medium is used to store computer instructions; The at least one processor is used to execute the computer instructions to implement the method for generating a visual progress chart of a municipal engineering project as described in claim 9.

Images