A work progress management method and system based on WBS

Abstract

The present application relates to the technical field of engineering management, and provides a construction progress management method and system based on WBS, which imports the contract plan, the board of directors annual plan and the execution plan, establishes the corresponding relationship among the plan task, the WBS unit and the BIM model, combines the quantity data, the resource consumption quota data and the process procedure data to calculate the resource demand, and forms the stage plan and the scheduling task after the approval of the execution plan; in the construction process, the actual quantity data and the actual resource consumption data are obtained according to the scheduling task, the actual execution progress of the execution plan is updated, and the execution result is summarized to the contract plan and the board of directors annual plan. Therefore, the on-site construction condition can be gradually fed back to each level plan, manual statistics and repeated arrangement are reduced, and the accuracy of progress management is improved.

Description

Technical Field

[0001] This invention relates to the field of engineering management technology, specifically to a construction progress management method and system based on WBS. Background Technology

[0002] The current project schedule management functions have significant shortcomings, failing to meet the needs of efficient collaboration and scientific decision-making. Existing online editing functions only provide basic data storage, lacking core algorithms for automated verification and scheduling of plan logic and critical paths. This leads to potential risks such as logical conflicts in the plan itself or unreasonable time estimates, creating hidden dangers for project execution. In the plan review stage, there is a lack of a clear comparison view between the current and original plans. Reviewers must manually cross-reference different documents or data, greatly increasing workload and time costs, making it difficult to quickly and accurately assess the impact of plan changes, thus affecting the efficiency and quality of approval decisions. Furthermore, the schedule preparation process cannot achieve flexible online allocation of personnel, materials, and equipment, and the general contractor cannot specify concrete personnel, material, and equipment configuration requirements when assigning schedule tasks to construction units. Summary of the Invention

[0003] The invention aims to solve the problem of low efficiency in the schedule management of construction projects in the prior art, and provides a construction schedule management method and system based on WBS, which enables the construction schedule management to form a management mode that connects the planning, on-site execution and progress feedback, improves the consistency of progress data and achieves the goal of efficient management.

[0004] To achieve the above objectives, the first aspect of this application provides a construction schedule management method based on WBS, comprising the following steps:

[0005] S1. Import the contract plan, the board's annual plan, and the execution plan. Bind each task in the execution plan to the corresponding WBS unit, establish the correspondence between the WBS unit and the BIM model, and establish the association between the contract plan, the board's annual plan, and the execution plan based on the WBS unit. S2. Retrieve the engineering quantity data, resource consumption quota data, and process data corresponding to each planned task, and calculate the human resource demand, material resource demand, and machinery resource demand corresponding to each planned task; wherein, the engineering quantity data includes the visual engineering quantity data and the physical engineering quantity data; S3. After the execution plan is approved, the execution plan is automatically divided into phase plans based on the image engineering quantity data and construction period data corresponding to each planned task; Based on the phase plan, the human resource requirements, the material resource requirements, the mechanical resource requirements, and the process data, each planned task is broken down into task units to generate a shift schedule, and the shift schedule is pushed to the corresponding work groups and equipment. S4. Based on the scheduling task, obtain the actual workload data and actual resource consumption data corresponding to each task unit, and associate the actual workload data and actual resource consumption data with the corresponding WBS unit, planned task and scheduling task respectively, so as to update the actual execution progress of the execution plan. S5. Based on the updated actual execution progress, and according to the relationship between the contract plan, the board's annual plan, and the execution plan, automatically summarize the execution results of the execution plan into the contract plan and the board's annual plan.

[0006] A second aspect of this application provides a WBS-based construction progress management system, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above-described method.

[0007] Based on the above technical solution, this application has the following beneficial effects: 1) By importing contract plans, board annual plans, and execution plans, and establishing the correspondence between planned tasks, WBS units, and BIM models, subsequent progress management can be carried out on a unified data basis. Resource requirements can then be calculated by combining engineering quantity data, resource consumption quota data, and process data. After the execution plan is approved, it can be further broken down into phase plans and shift tasks. During construction, actual engineering quantity data and actual resource consumption data are collected based on the shift tasks to update the actual execution progress of the execution plan, and the execution results are summarized in the contract plan and board annual plan. Using this method, construction progress management can form a seamless management process from planning, on-site execution to progress feedback, which is conducive to improving the consistency of progress data and achieving efficient management.

[0008] 2) After BIM is linked with the planning data, the model units related to the construction plan, i.e. the work parts, can be displayed in a visual interface. Based on the continuity between the work parts, the correctness and rationality of the plan can be judged. Attached Figure Description

[0009] To more clearly illustrate the technical solutions in the embodiments of this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0010] Figure 1 A schematic flowchart of a method according to an embodiment of this application is shown. Figure 2 A business logic flowchart according to an embodiment of this application is illustrated schematically. Detailed Implementation

[0011] To facilitate understanding of this application, the following description will be more comprehensive and detailed in conjunction with the accompanying drawings and preferred embodiments, but the scope of protection of this application is not limited to the following specific embodiments.

[0012] Unless otherwise defined, all technical terms used herein have the same meaning as commonly understood by those skilled in the art. The technical terms used herein are for the purpose of describing particular embodiments only and are not intended to limit the scope of this application.

[0013] Please see Figure 1 , 2 An embodiment of the present invention provides a construction progress management method based on WBS, comprising the following steps: S1. Import the contract plan, board annual plan, and execution plan. Bind each task in the execution plan to the corresponding WBS unit, establish the correspondence between the WBS unit and the BIM model, and establish the association between the contract plan, board annual plan, and execution plan based on the WBS unit. S2. Retrieve the engineering quantity data, resource consumption quota data, and process data corresponding to each planned task, and calculate the human resource demand, material resource demand, and machinery resource demand corresponding to each planned task; among which, the engineering quantity data includes the visual engineering quantity data and the physical engineering quantity data; S3. After the execution plan is approved, based on the image engineering quantity data and schedule data corresponding to each planned task, the execution plan is automatically divided into phase plans; and based on the phase plans, the required human resources, required materials, required machinery, and the process data, each planned task is broken down into task units to generate a scheduling task. The scheduling task includes the work time, work location, work personnel, and work method, and the scheduling task is pushed to the corresponding work group and equipment. S4. The scheduling task obtains the actual workload data and actual resource consumption data corresponding to each task unit based on the established relationship with the plan and WBS, and feeds it back to the planning task to update the actual execution progress of the execution plan. S5. Based on the updated actual execution progress, and according to the relationship between the contract plan, the board's annual plan, and the execution plan, automatically summarize the execution results of the execution plan into the contract plan and the board's annual plan.

[0014] In this embodiment, the contract plan is used to characterize the overall progress target of the project at the contract performance level, the board annual plan is used to characterize the phased progress target of the project at the annual operation and management level, the execution plan is used to characterize the specific work arrangements at the project construction implementation level, the WBS unit is used to characterize the work breakdown structure unit after the project is decomposed into layers, and the BIM model is used to visualize the physical components, construction areas or work parts corresponding to each WBS unit.

[0015] Specifically, in step S1, the management system receives the contract plan, the board's annual plan, and the execution plan, and identifies and stores the plan nodes in each plan. The contract plan determines the overall progress nodes at the project contract performance level, the board's annual plan determines the phase progress nodes at the annual management level, and the execution plan determines the specific work tasks at the on-site construction level. The system binds each plan task in the execution plan to the corresponding WBS unit according to its corresponding construction location, work content, and engineering decomposition level, and establishes a correspondence between the WBS unit and the model components, construction areas, or work locations in the BIM model. Thus, each plan task can be associated with the corresponding model object through the corresponding WBS unit, providing a unified data foundation for the time information, quantity information, and spatial location information of the plan task. The system then uses the WBS unit as the association object to establish a hierarchical correspondence between the contract plan nodes, the board's annual plan nodes, and the execution plan tasks, so that the specific construction tasks in the execution plan can be mapped to the management nodes in the upper-level plan.

[0016] In step S2, the corresponding engineering quantity data, resource consumption quota data, and process operation data are retrieved for each planned task, and the corresponding human resource requirements, material resource requirements, and machinery resource requirements for each planned task are calculated accordingly. Specifically, the visual engineering quantity data represents the completed objects and degree of completion of the planned task at the progress level; the physical engineering quantity data represents the physical engineering quantity corresponding to the planned task; the resource consumption quota data represents the standard of human, material, and machinery resource consumption required to complete a unit of engineering quantity; and the process operation data represents the construction sequence, operation method, and process connection requirements of each planned task. By calculating the resource requirements of the planned tasks, resource allocation and process constraints are provided for subsequent stages of plan generation and task breakdown.

[0017] In step S3, after the execution plan is approved, it is automatically broken down into phase plans based on the project quantity and schedule data corresponding to each planned task. Based on the phase plans, human resource requirements, material resource requirements, machinery resource requirements, and process data, each planned task is further broken down into task units, generating corresponding shift schedules, which are then pushed to the corresponding work teams and equipment. The work time characterizes the planned implementation period of the shift schedule, the work location characterizes the corresponding construction area, the personnel characterize the work team or personnel configuration undertaking the shift schedule, and the work method characterizes the construction method or process requirements adopted for the shift schedule. By further transforming the execution plan into on-site shift schedules, the feasibility of the schedule plan can be improved.

[0018] In step S4, based on the breakdown relationship between scheduling tasks and planned tasks, as well as the association relationship between planned tasks and WBS units, the actual workload data and actual resource consumption data corresponding to each task unit are obtained and fed back to the planned tasks to update the actual execution progress of the execution plan. The actual workload data characterizes the workload completed by each task unit during actual construction, while the actual resource consumption data characterizes the manpower, materials, and machinery resources invested or consumed by each task unit during actual construction. By associating the actual execution data on-site to the work breakdown layer, planning layer, and on-site execution layer respectively, the accuracy of progress feedback can be improved.

[0019] In step S5, after the actual execution progress of the execution plan is updated, based on the pre-established WBS unit-based relationships between the contract plan, the board's annual plan, and the execution plan, the execution results at the execution plan level are automatically aggregated into the corresponding contract plan and the board's annual plan to form a unified progress execution result across different levels of plans. By automatically aggregating the execution data from the construction site to the upper-level plan from bottom to top, the data problems caused by manual repetitive statistics and hierarchical reporting can be reduced, improving the efficiency of multi-level plan collaborative management.

[0020] By importing contract plans, board annual plans, and execution plans, and establishing the correspondence between planned tasks, WBS units, and BIM models, and then combining engineering quantity data, resource consumption quota data, and process data to calculate resource requirements, phased plans and work schedules can be generated after the execution plan is approved. During construction, actual engineering quantity data and actual resource consumption data are obtained based on the work schedules, the actual execution progress of the execution plan is updated, and the execution results are summarized in the contract plan and board annual plan. This allows on-site construction conditions to be progressively fed back to plans at each level, reducing manual statistics and repetitive data processing, and improving the accuracy of progress management.

[0021] In one embodiment, the method further includes the step of: visually verifying the execution plan based on the sequential logical relationships between the planned tasks in the execution plan and the continuity of the work locations in the BIM model corresponding to each WBS unit. Specifically, visually verifying the execution plan includes: displaying the construction locations corresponding to each planned task in the BIM model, and dynamically demonstrating the sequential connection relationships between the planned tasks according to the time sequence of each planned task and the spatial connection relationships between the construction locations.

[0022] Specifically, after the execution plan is formulated, the planned tasks are linked with the corresponding model units in the BIM model for display, making the construction locations corresponding to each planned task visually present in the model. Simultaneously, by combining the sequential logical relationships between planned tasks and the spatial continuity and connectivity between adjacent work locations, the construction sequence of planned tasks is dynamically demonstrated and verified. When there are inconsistencies between the time sequence and the spatial construction sequence, abnormal connections between preceding and following processes, or discontinuous work surface arrangements, staff can easily identify the corresponding problems in the visual interface. By linking the execution plan with the BIM model for verification, logical conflicts and spatial connectivity issues in the plan formulation can be more intuitively identified.

[0023] In one embodiment, in step S2, the human resource requirements, material resource requirements, and machinery resource requirements corresponding to each planned task are calculated based on the physical engineering quantity data and resource consumption quota data corresponding to each planned task; wherein, the resource consumption quota data is retrieved from the resource consumption quota library according to the project characteristics corresponding to the planned task, and the resource consumption quota data includes personnel quota data, material quota data, and machinery quota data.

[0024] Specifically, for each planned task, the project characteristics corresponding to that task are first determined, and then resource consumption quota data matching these characteristics are retrieved from the resource consumption quota database. Specifically, personnel quota data represents the standard manpower consumption required to complete a unit of physical work volume, material quota data represents the standard material consumption required to complete a unit of physical work volume, and machinery quota data represents the standard machinery consumption required to complete a unit of physical work volume. The physical work volume data corresponding to the planned task is then compared with the retrieved personnel, material, and machinery quota data to calculate the required human resources, materials, and machinery resources for that task. By calculating resources based on physical work volume data and standard quota data, the standardization of resource demand calculations can be improved, providing a quantitative basis for construction resource allocation.

[0025] In one embodiment, calculating the human resource requirements, material resource requirements, and machinery resource requirements corresponding to each planned task specifically includes: retrieving personnel quota data, material quota data, and machinery quota data corresponding to the planned task from the resource consumption quota database based on the project characteristics of the physical engineering quantity data corresponding to each planned task; and automatically generating the human resource requirements, material resource requirements, and machinery resource requirements corresponding to the planned task by combining the physical engineering quantity data with the retrieved personnel quota data, material quota data, and machinery quota data respectively.

[0026] Specifically, after acquiring the physical quantity data corresponding to each planned task, the system identifies the project characteristics corresponding to that physical quantity data, such as component type, construction technology category, work content category, or construction specialty category. Based on these project characteristics, the system automatically matches the corresponding personnel quota data, material quota data, and machinery quota data from the resource consumption quota library. The personnel quota data represents the man-hours or man-days required to complete a unit of physical quantity, the material quota data represents the material usage required to complete a unit of physical quantity, and the machinery quota data represents the machine-hours required to complete a unit of physical quantity. The system multiplies the physical quantity of the planned task by the corresponding personnel quota data, material quota data, and machinery quota data to obtain the required man-hours or man-days, material usage, and machine-hours for the planned task, and uses these as the human resource requirement, material resource requirement, and machinery resource requirement for the planned task, respectively.

[0027] Preferably, various suggested resource usage quantities can be generated based on the product of the actual project quantity and the corresponding unit quota. The human resource demand, material resource demand, and machinery resource demand can serve as a reference for phase plan breakdown, shift task generation, and resource allocation adjustment. By automatically generating suggested resource usage quantities, the bias caused by relying on manual experience for resource estimation can be reduced, improving the automation and accuracy of resource allocation suggestions.

[0028] In one embodiment, step S3 involves automatically splitting the execution plan into phase plans, including: determining the phase time intervals corresponding to each planned task within the annual, quarterly, monthly, and weekly time periods based on the planned start time, planned end time, and planned duration of each planned task, and generating annual, quarterly, monthly, and weekly tasks corresponding to the phase time intervals respectively; and decomposing the visual engineering quantity data corresponding to each planned task into phase suggestion quantities corresponding to each annual, quarterly, monthly, and weekly task based on the phase duration corresponding to each phase time interval, to generate initial annual, quarterly, monthly, and weekly plans for phase plan submission and approval.

[0029] Specifically, after the implementation plan is approved, the specific implementation steps are as follows: Read the planned start time, planned end time, and planned duration for each planned task, and divide the time range covered by each planned task according to the time division rules of natural year, quarter, month, and week to determine the stage time interval corresponding to each planned task in the year, quarter, month, and week. For planned tasks that span years, quarters, months, or weeks, corresponding annual tasks, quarterly tasks, monthly tasks, and weekly tasks are formed according to the actual coverage of the time interval.

[0030] Based on the proportion of the phase duration to the total planned task duration within each time interval, the project's progress data is broken down into annual, quarterly, monthly, and weekly tasks, generating suggested quantities for each phase. Initial annual, quarterly, monthly, and weekly plans are then generated for approval by different management levels. By automatically splitting the execution plan according to different time periods (year, quarter, month, week) and simultaneously decomposing the progress data into suggested quantities for each phase, the efficiency of phase planning and the standardization of plan decomposition are improved.

[0031] In one embodiment, when generating the scheduling task in step S3, the approved weekly plan, process data, human resource requirements, material resource requirements, and mechanical resource requirements are used as inputs, and the construction team, working time period, and single process completion quantity are used as constraints to generate a schedule and scheduling task sheet corresponding to the weekly plan.

[0032] Specifically, after the weekly plan is approved, the system uses the planned work content, suggested quantities for each stage, and completion deadlines for each weekly task as input. It then combines this with corresponding process data, human resource requirements, material resource requirements, and machinery resource requirements to decompose each weekly task. The process data represents the sequence and overlap between construction operations, as well as the process requirements and duration of each operation. When generating the scheduling tasks, the availability of construction teams, available work periods, and the quantity of work completed per operation are used as constraints to match and allocate the weekly tasks in the weekly plan, thus forming corresponding schedules and task sheets. The schedules summarize and display multiple scheduling tasks, while the task sheets represent individual scheduling tasks and their subordinate processes. Using the approved weekly plan as a basis, and comprehensively considering process and on-site team constraints, to generate schedules and task sheets improves the operability and accuracy of converting the weekly plan into on-site execution tasks, reducing conflicts and deviations caused by manual scheduling.

[0033] In one embodiment, in step S3, the planned start time and planned end time of each scheduling task are automatically calculated based on the working time period and process data; the planned start time and planned end time of the corresponding process of each task order are automatically calculated based on the planned start time of the corresponding scheduling task and process data; after the corresponding process of any task order is completed, the planned start time and planned end time of subsequent unstarted processes are automatically updated based on the actual start time and actual end time of the process; a reminder is sent to the corresponding work group at a preset time before the corresponding task order starts; when a scheduling task exceeds the task cycle, the scheduling task is marked as overdue.

[0034] Specifically, after the scheduling tasks are generated, the system automatically determines the planned start and end times of each scheduling task based on the working time periods available to the corresponding construction teams and relevant process data, so that each scheduling task meets the requirements of work sequence and working time period in terms of time. When any scheduling task is completed, the system obtains the actual end time of the scheduling task and adjusts or extends the planned start and end times of subsequent scheduling tasks accordingly to maintain the continuity of the scheduling chain.

[0035] At the task order level, the planned start time and planned end time of each task order's corresponding process are automatically calculated based on the planned start time of the corresponding shift task and the process data. Once any process is completed, the planned start and end times of subsequent processes that have not yet started are automatically updated based on the actual start and end times of that process, thus forming a linkage time adjustment mechanism from scheduling tasks to specific processes. A reminder is sent to the corresponding work team 30 minutes before the start of the corresponding task order to remind relevant personnel to start construction work on time. When the execution time of a scheduled task exceeds its assigned task cycle, the scheduled task is marked as overdue to identify subsequent plan delays. By automatically calculating the planned times for scheduling tasks and task order processes, the dynamic adjustment capability of on-site scheduling can be improved, and the corrective effect during the execution of construction progress can be enhanced.

[0036] In one embodiment, in step S4, the actual engineering quantity data and actual resource consumption data are obtained through manual input or automatic collection by intelligent devices, associated with the corresponding WBS unit and scheduling task, and associated with the corresponding planned task after confirmation by the supervisor; wherein, the intelligent devices include positioning devices for obtaining construction progress in conjunction with the BIM model, image acquisition devices for obtaining transportation volume, and aerial surveying devices for obtaining filling or excavation volume; after the scheduling is completed, the corresponding engineering quantity and resource consumption status are automatically updated to the corresponding weekly task through task feedback, and the suggested quantity of the remaining weekly plan in the current monthly plan is dynamically updated according to the completion status of this week.

[0037] Specifically, during the execution of scheduling tasks, on-site management personnel can manually input actual engineering quantity data and actual resource consumption data through mobile terminals and management platforms, or they can automatically collect relevant data through smart devices. Positioning devices can be used to identify construction locations and progress using BIM models, image acquisition devices can be used to identify volume information during transportation, and aerial surveying equipment can be used to obtain changes in earthwork volume in filling or excavation areas. The acquired actual engineering quantity data and actual resource consumption data, after confirmation by the supervisor, are fed back to the planned tasks and scheduling tasks corresponding to the same WBS unit, thereby ensuring the validity of actual execution data at different management levels.

[0038] Furthermore, after scheduling is completed, the corresponding completed work volume, personnel input, material consumption, and machinery usage are automatically updated to the corresponding planned tasks through task feedback. Combined with the actual completion status of the week, the remaining weekly plan recommendations not yet implemented in the current monthly plan are dynamically adjusted. By using a combination of manual input and intelligent data collection to obtain actual execution data, and performing multi-level correlation and feedback updates after supervisor confirmation, the accuracy and timeliness of progress data collection can be improved, while enhancing the linkage between monthly and weekly plans.

[0039] In one embodiment, step S5, which involves automatically aggregating the execution results of the execution plan to the contract plan and the board's annual plan, specifically includes: automatically aggregating the execution results of the execution plan to the corresponding contract plan nodes and board's annual plan nodes, and updating the node duration, completion status, and plan execution status of the contract plan nodes and board's annual plan nodes.

[0040] Specifically, after the progress of each planned task and the results of resource execution in the execution plan are updated, the execution results at the execution plan level are automatically aggregated to the corresponding contract plan nodes and board annual plan nodes based on the pre-established WBS relationship between the contract plan, the board's annual plan, and the execution plan. Node duration represents the duration or completion time requirement of the corresponding plan node; completion status represents whether the corresponding plan node has been completed, is in progress, or is lagging behind; and plan execution status represents the degree or proportion of achievement of the plan's objectives corresponding to that node. By automatically aggregating and synchronously updating the execution results of the execution plan to the contract plan nodes and board annual plan nodes, the project's on-site execution status can be promptly reflected at the contract performance and annual operational management levels, reducing manual hierarchical aggregation and repetitive reporting work, and improving the efficiency and consistency of multi-level plan collaborative management.

[0041] A specific implementation example uses the tailrace tunnel project. The project schedule management involves three types of planning documents: contract plan, board annual plan, and execution plan. These three types of plans are then linked to the BIM model.

[0042] In this embodiment, the contract plan, board annual plan, and execution plan related to the tailrace tunnel are first imported into the management system. The contract plan includes control milestones such as the requirement for the water diversion system to be completed by November 16, 2027; the board annual plan includes important annual milestones; and the execution plan includes multiple construction tasks related to the tailrace tunnel.

[0043] The system binds each planned task in the execution plan to its corresponding WBS unit and establishes a correspondence between the WBS unit and the BIM model. Taking the tailrace tunnel as an example, the WBS can be divided into four levels: unit project, sub-project, itemized project, and unit project. The tailrace tunnel is a unit project, the tunnel body is a sub-project, the tunnel body excavation is an itemized project, and the excavation work at specific station sections can be considered a unit project. Contract plans, the board's annual plan, and the execution plan can all be linked within the same WBS system. Sub-level plan nodes must not exceed the parent-level node's timeframe, thus ensuring consistency in time constraints between different levels of plans.

[0044] For example, the execution plan task of "excavation of the upper layer of the main tailrace tunnel from 0+100.00 to 0+853.566" is associated with the corresponding WBS unit for the main tailrace tunnel excavation, and further mapped to the corresponding tunnel segment model unit in the BIM model. The planned start date for this task is May 1, 2026, the planned completion date is October 2, 2026, the planned duration is 155 days, and the planned excavation progress is 753.56m. Through this association, subsequent work volume, resources, scheduling, and progress feedback can all be uniformly linked to the same WBS node.

[0045] After the plan is imported, the system performs a visual verification of the plan based on the preceding and following logical relationships of each task in the execution plan and the spatial continuity of each work area in the BIM model.

[0046] For example, during tailrace tunnel construction, the system can display the bound excavation locations of tunnel sections in the model and check for skipped sections, reversed order arrangements, or logical conflicts between preceding and following sections. If the planned start time of a subsequent tunnel section's excavation task is earlier than the completion time of its preceding task, or if the model shows discontinuities in the work area, it facilitates review and modification by the planning personnel. This reduces omissions that are prone to occur when relying solely on manual experience for review, improving the rationality of the planning process.

[0047] After the plan verification is completed, the system retrieves the engineering quantity data, resource consumption quota data and process operation data corresponding to the task, and binds them to the corresponding planned task and WBS unit.

[0048] In this embodiment, the excavation of the upper layer of the main tailrace tunnel from 0+100.00 to 0+853.566 is used as an example. The corresponding visual engineering quantity for this task is an excavation advance of 753.566m, and the corresponding physical engineering quantity is 49410m³ of rock excavation. The project characteristics of this task include: rock grades of Class II accounting for 50%, Class III1 accounting for 20%, Class III2 accounting for 18%, Class IV accounting for 7%, and Class V accounting for 5%; the excavation cross-sectional area is 135.8m²; the internal transportation distance is 2.5km and the external transportation distance is 1km; the drilling equipment is a YT-28 hand drill; the excavation equipment is a drill and blasting trolley; and the transportation equipment is a 20t dump truck.

[0049] Based on the physical engineering quantities and project characteristics mentioned above, the system retrieves the corresponding quota data from the resource consumption quota database and automatically calculates the human resource requirements, material resource requirements, and machinery resource requirements corresponding to the task.

[0050] For example, this task can calculate the following quantities: 39,034 kg of emulsion explosives, 988 man-hours of a BOOMER282 hydraulic boom drilling rig, 4,941 man-hours of semi-skilled workers, 2,964 man-hours of skilled workers, 3,458 man-hours of 20t dump trucks, and 494 man-hours of loaders. These resource requirements are automatically linked to the corresponding task nodes for subsequent phase planning and scheduling.

[0051] Simultaneously, the system also associates this task with the excavation construction process. In this embodiment, the single excavation construction process involves a depth of 3.6 meters, and the procedures include excavation preparation, surveying and setting out, drilling, charging and blasting, safety procedures, muck removal and bottom cleaning, surrounding rock support, and safety inspection. Each procedure has its corresponding working hours, intervals between procedures, and work team information pre-entered. After the plan is officially issued, the system can automatically generate a work schedule and task sheet based on the process rules.

[0052] After the execution plan is approved, the system automatically breaks it down into annual, quarterly, monthly, and weekly plans based on the project size and schedule of each task.

[0053] The system automatically decomposes the total task of 753.56m and 155 days into tasks for 2026, tasks for the second quarter, tasks for the third quarter, and tasks for the fourth quarter according to the natural time interval and the proportion of the work period. It further decomposes these tasks into monthly plans and corresponding weekly plans for May, June, July, August, September, and October.

[0054] For example, the system can form the following phased tasks: The recommended volume for the second quarter of 2026 is 296.46m, including 150.66m for May and 145.8m for June; The recommended volume for the third quarter of 2026 is 447.36m, including 150.66m in July, 150.66m in August, and 146.04m in September. The recommended volume for the fourth quarter of 2026 is 9.74m, which corresponds to completion in the first two days of October.

[0055] At the weekly planning level, the system further automatically calculates the weekly recommended completion amount, such as the recommended amount of 34.02m for the second week of May 2026, the recommended amount of 34.02m for the third week, and the recommended amount of 34.02m for the fourth week.

[0056] This approach doesn't simply distribute the total amount equally; instead, it automatically generates plans based on task duration, natural week / month boundaries, and stage reporting requirements. Managers can directly use the system-generated annual, quarterly, monthly, and weekly plans as the basis for stage plan reporting, thus reducing the workload of manual, layer-by-layer breakdowns.

[0057] After the phase plan is formed, the system combines the weekly plan submission volume, resource demand, and process data to further break down the planned tasks into the smallest task units, generating a scheduling task that includes work time, work location, workers, and work methods.

[0058] In this embodiment, the shift schedule is configured as three working periods per day: 08:00–12:00, 14:00–18:00, and 20:00–23:00, with a process interval of 2 hours. Based on the weekly plan submission volume and the single-process completion volume of 3m, the system automatically determines the number of shifts to be generated and calculates the planned start and end times for each shift.

[0059] For example, for the construction task of "excavation of the upper layer of the main tunnel section from tailwater 0+100.00 to tailwater 0+853.566" in the third week of March 2026, the system can automatically generate multiple consecutive shift schedules.

[0060] One of the scheduling tasks corresponds to the image project volume range of 0-3m, with a planned start time of 08:00 on March 9, 2026 and a planned end time of 16:00 on March 10, 2026; The next shift assignment corresponds to 4-6m, with a planned start time of 20:00 on March 10, 2026, and a planned end time of 12:00 on March 12, 2026. The next shift corresponds to 7-9m, with a planned start time of 14:00 on March 12, 2026, and a planned end time of 22:00 on March 13, 2026.

[0061] The above schedules are automatically pushed to the corresponding work groups and equipment.

[0062] Under each scheduling task, the system continues to generate task sheets. Taking a specific scheduling task as an example, its task sheet may include the following in sequence: Excavation preparation, timeframe 1 hour; Surveying and setting out, timeframe 2 hours; Drilling, time required: 2 hours; Safety procedures to be completed within 2 hours; Slag removal and bottom cleaning, timeframe 2 hours; Surrounding rock support, construction period 2 hours; Safety inspection, timeframe 2 hours.

[0063] The tasks are automatically extended according to the preset interval, and the system sends a reminder to the corresponding work group 30 minutes before the start of work. If the actual start or end time of a certain process changes, the system can automatically recalculate the planned time of subsequent processes that have not yet started; if the entire schedule exceeds the task cycle of its own week, the system will mark it as overdue so that managers can organize rush work by rescheduling or increasing working hours.

[0064] After the scheduling tasks are issued, on-site personnel can provide feedback on the actual workload and resource consumption data either manually or automatically through smart devices. The system then aggregates the feedback data to the planned tasks to update the actual progress of the execution plan.

[0065] For example, for the task of "excavation of the upper layer of the main tailrace tunnel from 0+100.00 to 0+853.566", in a certain shift feedback, the process name is excavation construction process, and the single-shift completion volume is 3m. The system will simultaneously display the visual project quantity, physical project quantity, and resource feedback items for this task.

[0066] Regarding the amount of landscaping work, the total volume is 753.566m, the planned volume for this week is 35m, and the planned volume for this project is 3m. In terms of physical engineering volume, the total excavation volume of the rock tunnel is 49,410 m³, the planned volume for this week is 3,812.75 m³, and the planned volume for this project is 326.81 m³. In terms of resources, for example, the planned quantity of rock drilling rigs this week is 76 unit hours, while the planned quantity for this operation is 6.5 unit hours; the planned quantity of emulsion explosives this week is 2821 kg, while the planned quantity for this operation is 241.8 kg.

[0067] After on-site personnel complete the form, the system automatically adds the completed amount to the corresponding weekly task and dynamically adjusts the suggested amounts for the remaining weeks of the month. Once the supervisor confirms the measurement, the actual completion status is then updated in the main task of the execution plan.

[0068] If the actual completion volume in a certain week is lower than the planned value, the system will retain the completed volume and reallocate the remaining work volume to the subsequent weekly plans for the month. If the intelligent equipment has collected data such as tunnel advance and transport volume, the system can also compare the automatically collected values ​​with the manually entered values ​​to improve the timeliness and accuracy of progress feedback.

[0069] Once the actual progress of the execution plan is updated, the system automatically summarizes the execution results of the execution plan into the contract plan and the board's annual plan according to the relationship established based on WBS between the contract plan, the board's annual plan and the execution plan.

[0070] For example, as the excavation progress of a certain section of the tailrace tunnel continues to increase, the system not only updates the completed footage, remaining footage, and due date status of the task, but also simultaneously updates the completion status of its annual and contractual milestones. If the actual progress of a key task lags behind and affects important annual milestones, the corresponding milestone in the board's annual plan can be automatically displayed as delayed; if the execution plan has been completed to the specified control depth or control mileage, the corresponding milestone in the upper-level plan can be updated to completed or completed on schedule. In this way, data between different levels of plans does not need to be repeatedly entered, and managers can directly view the actual progress automatically summarized from the lower-level execution tasks in the upper-level plan.

[0071] In one embodiment, this application also provides a WBS-based construction progress management system, including a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the steps of the above method.

[0072] The above are merely preferred embodiments of this application. It should be noted that this application is not limited to the above embodiments. For those skilled in the art, several improvements and modifications can be made without departing from the principles of this application. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of this application should also be considered within the scope of protection of this application.

Claims

1. A construction schedule management method based on WBS, characterized in that, Including the following steps: S1. Import the contract plan, the board's annual plan, and the execution plan. Bind each task in the execution plan to the corresponding WBS unit, establish the correspondence between the WBS unit and the BIM model, and establish the association between the contract plan, the board's annual plan, and the execution plan based on the WBS unit. S2. Retrieve the engineering quantity data, resource consumption quota data, and process data corresponding to each planned task, and calculate the human resource demand, material resource demand, and machinery resource demand corresponding to each planned task; wherein, the engineering quantity data includes the visual engineering quantity data and the physical engineering quantity data; S3. After the execution plan is approved, based on the image engineering quantity data and schedule data corresponding to each planned task, the execution plan is automatically divided into phase plans; and based on the phase plans, the human resource requirements, the material resource requirements, the mechanical resource requirements, and the process data, each planned task is broken down into task units to generate a shift schedule, and the shift schedule is pushed to the corresponding work group and equipment. S4. Based on the decomposition relationship between the scheduling tasks and the planned tasks, as well as the association relationship between the planned tasks and the WBS units, obtain the actual workload data and actual resource consumption data corresponding to each task unit, so as to update the actual execution progress of the execution plan. S5. Based on the updated actual execution progress, and according to the relationship between the contract plan, the board's annual plan, and the execution plan, automatically summarize the execution results of the execution plan into the contract plan and the board's annual plan.

2. The construction progress management method based on WBS according to claim 1, characterized in that, The method also includes the step of visually verifying the execution plan based on the preceding and succeeding logical relationships of each planned task in the execution plan and the continuity of the working parts of the BIM model corresponding to each WBS unit.

3. The construction progress management method based on WBS according to claim 1, characterized in that, In S2, the human resource requirements, material resource requirements, and machinery resource requirements corresponding to each planned task are calculated based on the physical engineering quantity data and resource consumption quota data corresponding to each planned task. The resource consumption quota data is retrieved from the resource consumption quota database according to the project characteristics corresponding to the planned task, and the resource consumption quota data includes personnel quota data, material quota data, and machinery quota data.

4. The construction progress management method based on WBS according to claim 3, characterized in that, The calculation of the human resource requirements, material resource requirements, and machinery resource requirements corresponding to each planned task specifically includes: based on the project characteristics of the physical engineering quantity data corresponding to each planned task, retrieving the personnel quota data, material quota data, and machinery quota data corresponding to the planned task from the resource consumption quota database; and automatically generating the human resource requirements, material resource requirements, and machinery resource requirements corresponding to the planned task by combining the physical engineering quantity data with the retrieved personnel quota data, material quota data, and machinery quota data respectively.

5. The construction progress management method based on WBS according to claim 1, characterized in that, In S3, the execution plan is automatically broken down into phase plans, including: determining the phase time intervals corresponding to each planned task in the annual, quarterly, monthly, and weekly time periods based on the planned start time, planned end time, and planned duration of each planned task, and generating annual, quarterly, monthly, and weekly tasks corresponding to the phase time intervals respectively; and decomposing the image engineering quantity data corresponding to each planned task into phase suggested quantities corresponding to each annual, quarterly, monthly, and weekly task based on the phase duration corresponding to each phase time interval, so as to generate initial annual, quarterly, monthly, and weekly plans for phase plan submission and approval.

6. The construction progress management method based on WBS according to claim 5, characterized in that, When generating the scheduling task in S3, the approved weekly plan, the process data, the human resource requirement, the material resource requirement, and the mechanical resource requirement are used as inputs, and the construction team, working time period, and single process completion quantity are used as constraints to generate the schedule and task sheet corresponding to the weekly plan.

7. The construction progress management method based on WBS according to claim 6, characterized in that, In S3, the planned start and end times of each scheduled task are automatically calculated based on the working time period and the process data; the planned start and end times of the corresponding process of each task order are automatically calculated based on the planned start time of the corresponding scheduled task and the process data; after the completion of the corresponding process of any task order, the planned start and end times of subsequent unstarted processes are automatically updated based on the actual start and end times of that process; a reminder is sent to the corresponding work group at a preset time before the start of the corresponding task order; when a scheduled task exceeds the task cycle, the scheduled task is marked as overdue.

8. The construction progress management method based on WBS according to claim 1, characterized in that, In S4, the actual engineering quantity data and the actual resource consumption data are obtained through manual input or automatic collection by intelligent devices, associated with the corresponding WBS unit and scheduling task, and associated with the corresponding planned task after confirmation by the supervisor; after the scheduling is completed, the corresponding engineering quantity and resource consumption are automatically updated to the corresponding weekly task through task feedback, and the suggested quantity of the remaining weekly plan in the current monthly plan is dynamically updated according to the completion status of this week.

9. The construction progress management method based on WBS according to claim 1, characterized in that, In S5, automatically summarizing the execution results of the execution plan to the contract plan and the board's annual plan specifically includes: automatically aggregating the execution results of the execution plan to the corresponding contract plan nodes and board's annual plan nodes, and updating the node duration, completion status, and plan execution status of the contract plan nodes and board's annual plan nodes.

10. A WBS-based construction progress management system, comprising a memory, a processor, and a computer program stored in the memory and executable on the processor, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 9.

Images