Project progress plan generation method and equipment based on basic data
By constructing a BIM model database and a schedule dictionary, and combining it with project spatial structure data, a project schedule is generated and displayed, solving the problem of low efficiency in the preparation of engineering project schedules in existing technologies, and realizing rapid and standardized preparation and management of project schedules.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- CHINA CONSTR THIRD ENG BUREAU GRP CO LTD
- Filing Date
- 2026-01-14
- Publication Date
- 2026-04-21
AI Technical Summary
In existing technologies, the preparation of engineering project schedules is inefficient and difficult to achieve in terms of speed and standardization. This is especially true in the field of construction engineering, where manual preparation tools such as Oracle P6 and MS Project are relied upon, resulting in high skill requirements for the preparers.
The project schedule generation method based on basic data constructs a BIM model database and a schedule dictionary, combines project spatial structure data, uses tree-structured data to design a task list library, and provides logical relationship connections, calendar settings, and schedule calculation functions to generate and display the project schedule.
It enables rapid and standardized project schedule planning, utilizes historical enterprise data to improve planning efficiency, and can more accurately guide project execution.
Smart Images

Figure CN121903302A_ABST
Abstract
Description
Technical Field
[0001] This invention belongs to the field of construction engineering, and specifically relates to a method and device for generating project schedule plans based on basic data. Background Technology
[0002] Currently, most engineering project schedules need to be prepared manually, typically using software such as Oracle P6 or MS Project. This method is inefficient and requires a high level of skill from the planners, making it difficult to achieve rapid and standardized schedule preparation. Summary of the Invention
[0003] The purpose of this invention is to provide a method and device for generating project schedule plans based on basic data.
[0004] To address the above problems, this invention provides a method for generating project schedules based on basic data, comprising: Build the enterprise's BIM model database, the enterprise's schedule dictionary, and the project's spatial structure data. In the enterprise's schedule dictionary, complete the association settings between the schedule task dictionary data and the BIM model data. The spatial structure of the project is linked to the schedule dictionary library to assign spatial structure attributes to the schedule task dictionary data; the required schedule task dictionary data is selected from the schedule dictionary library for each project, and the project schedule is generated based on the selected schedule task dictionary data and according to the spatial structure attributes. The generated project schedule is displayed in the form of a Gantt chart. It also provides functions such as logical relationship connection, logical relationship delay setting, task calendar setting, task constraint setting, and schedule calculation to assist in completing the time scheduling of the project schedule, for project schedule execution and analysis, and supports providing project schedule execution and analysis data to external parties.
[0005] Furthermore, in the above method, the spatial structure data of the project is designed in the form of tree-structured data, and the information of the project's partitions, buildings and floors is digitized, which is used to select the planned task dictionary data in the schedule dictionary library and link it with the spatial structure data of the project.
[0006] Furthermore, in the above method, the field content of the spatial structure data of the project includes: space ID, space parent ID, and space name; Build an enterprise schedule dictionary, including: The schedule dictionary is constructed in a multi-level tree structure to organize the schedule items from a professional perspective, forming a complete list of schedule task items that includes all construction content.
[0007] Furthermore, in the above method, the field content of the schedule dictionary includes: category ID, category parent ID, category name, task ID, task parent ID, task code, task name, module name, whether it is a milestone node, process category, and task description. The fields in the BIM model database include: Category ID, Category Parent ID, Category Name, Model ID, Model Code, Model Name, Name of Building Unit, Material, Main Material Density, Fire Resistance Rating, Mortar Strength Grade, Volume, Type, Corresponding 3D Model, Connection Method, Weight, Remarks, and Corresponding Plan Dictionary ID.
[0008] Furthermore, in the above method, the project schedule is a tree-structured schedule data, with the root node being the project name; the second-level nodes being the disciplines; the third, fourth, and fifth-level nodes being the spatial structure of the project; and lower-level nodes below the fifth-level node exist as child nodes located below the above levels according to their respective spatial structures.
[0009] Furthermore, the above method, after generating the project schedule, also includes: It provides functions for merging, splitting, and expanding project schedules by functional area, which are used to complete and improve the generated project schedule data, making the project schedule more in line with the actual management requirements of different projects.
[0010] Furthermore, in the above method, the time scheduling of the project schedule supports the following: The calendar supports custom calendars; Supports WBS maintenance; The job types supported include task-based jobs, start milestones, finish milestones, collaborative jobs, independent jobs, and WBS jobs. Logical relations support four types: FS, SS, SF, and FF. When connecting logical relationships, a delay setting is supported; the delay can be a positive or negative value. The job constraints support the following types: "As late as possible", "Start no earlier than", "Start no later than", "Finish no earlier than", "Finish no later than", "Force start", "Force finish", "Start at", and "Finish at". Supports the quick creation and deletion of logical relationship connections between multiple jobs; the default relationship type for quick connections is FS. Supports view functionality; The Gantt chart display supports the display of target Gantts and the simultaneous display of target Gantts and currently planned Gantts on the same screen. Supports forward lines, data date lines, and spotlight displays.
[0011] Furthermore, the above method provides functions for logical relationship connection, logical relationship delay setting, job calendar setting, job constraint setting, and progress calculation to assist in completing the time scheduling of the schedule plan, including: Record the date of the last data calculation and the date the current progress calculation is set; After the schedule is calculated, tasks with a total float less than the set time value can be defined as the critical path of the project schedule. After the schedule is calculated, all tasks on the logically connected work paths that run from the start of the project to the end of the project without interruption can be defined as the critical path of the project schedule. For out-of-order tasks, progress calculations are performed based on maintaining logical relationships, progress skipping methods, or actual dates; Jobs without any preceding logical relationship are scheduled for progress calculation in a way that either does not participate in the calculation or is moved to the data date. The calendar for calculating logical relationship delays is based on the methods of prior task calendar, subsequent task calendar, 24-hour calendar, or the default plan calendar.
[0012] According to another aspect of the present invention, a computer-readable storage medium is also provided, having stored thereon computer-executable instructions, wherein when executed by a processor, the computer-executable instructions cause the processor to perform the method described in any of the preceding claims.
[0013] According to another aspect of the present invention, a calculator device is also provided, comprising: processor, and A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform the method described in any of the preceding descriptions.
[0014] Compared with existing technologies, this invention can solve the problem of project schedule preparation for building construction projects. It can effectively utilize the historical data of similar projects accumulated by the company, including BIM models, planning dictionaries, and spatial divisions, to quickly generate project schedules and guide projects to be executed according to plan, thus standardizing the preparation and management of project schedules for building construction projects. Attached Figure Description
[0015] Figure 1 This is an architecture diagram of a project schedule generation method and device based on basic data according to an embodiment of the present invention; Figure 2 This is a flowchart of a project schedule generation method based on basic data according to an embodiment of the present invention; Figure 3 This is a schematic diagram of the prototype design of the planned dictionary library function according to an embodiment of the present invention; Figure 4 This is a schematic diagram of a prototype of the BIM model library function according to an embodiment of the present invention; Figure 5 This is a schematic diagram of a spatial structure functional prototype according to an embodiment of the present invention; Figure 6 This is a schematic diagram of a prototype of the planning dictionary and BIM model mapping function according to an embodiment of the present invention; Figure 7 This is a schematic diagram of a prototype of the function of selecting dictionary database data and attaching spatial structure according to an embodiment of the present invention; Figure 8 This is a schematic diagram of a prototype of the project plan generation function according to an embodiment of the present invention; Figure 9 This is a schematic diagram of a prototype of the plan merging function according to an embodiment of the present invention; Figure 10 This is a schematic diagram of the data after the planned merger according to an embodiment of the present invention; Figure 11 This is a schematic diagram of a prototype of the planning splitting function according to an embodiment of the present invention; Figure 12 This is a schematic diagram of a functional area segmentation prototype according to an embodiment of the present invention; Figure 13 This is a schematic diagram of the spatial sorting function according to an embodiment of the present invention; Figure 14 This is a schematic diagram of the logical relationship between regions according to an embodiment of the present invention; Figure 15 This is a schematic diagram of the plan splitting result according to an embodiment of the present invention; Figure 16 This is a schematic diagram of a prototype of the present invention unfolded according to functional areas; Figure 17 This is a schematic diagram showing the expanded functional area of an embodiment of the present invention; Figure 18 This is a schematic diagram of a prototype of the progress calculation and scheduling function according to an embodiment of the present invention. Detailed Implementation
[0016] The present invention will now be described in further detail with reference to the accompanying drawings.
[0017] In a typical configuration of this application, the terminal, the device of the service network, and the trusted party all include one or more processors (CPUs), input / output interfaces, network interfaces, and memory.
[0018] Memory may include non-persistent storage in computer-readable media, such as random access memory (RAM) and / or non-volatile memory, such as read-only memory (ROM) or flash RAM. Memory is an example of computer-readable media.
[0019] Computer-readable media includes both permanent and non-permanent, removable and non-removable media that can store information by any method or technology. Information can be computer-readable instructions, data structures, modules of programs, or other data. Examples of computer storage media include, but are not limited to, phase-change memory (PRAM), static random access memory (SRAM), dynamic random access memory (DRAM), other types of random access memory (RAM), read-only memory (ROM), electrically erasable programmable read-only memory (EEPROM), flash memory or other memory technologies, CD-ROM, digital versatile optical disc (DVD) or other optical storage, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other non-transferable medium that can be used to store information accessible by a computing device. As defined herein, computer-readable media does not include non-transitory computer-readable media, such as modulated data signals and carrier waves.
[0020] like Figure 1 and Figure 2 The present invention provides a method for generating project schedules based on basic data, the method comprising: Step S1, Building Basic Data: Organize the company's past project data and information to build the company's BIM model database, the company's schedule dictionary, and the spatial structure data of the projects. Among them, the spatial structure data of the projects is unique and needs to be divided before the project schedule is generated. In the company's schedule dictionary, complete the association settings between the schedule task dictionary data and the BIM model data to ensure that each schedule task dictionary data in the company's schedule dictionary has a corresponding BIM model. Preferably, the spatial structure data of the project is designed in the form of tree-structured data, and the information such as the project's partitions, buildings, and floors is digitized. This data is used to select the planned task dictionary data in the schedule dictionary library and link it with the spatial structure data of the project, so that the selected planned dictionary library data can be used to generate the project schedule plan in the established project spatial structure.
[0021] The main fields of the spatial structure data of the project are shown in Table 1:
[0022] like Figure 5 The diagram shown is a schematic of the functional prototype of the spatial structure.
[0023] The mapping between the schedule task dictionary and the BIM model library is used to map the task item list in the schedule task dictionary to the BIM model data, such as... Figure 6 The diagram shown is a prototype of the mapping function between the planning dictionary and the BIM model.
[0024] Preferably, the schedule dictionary is constructed in a multi-level tree structure data format to organize the schedule items from a professional perspective, forming a complete list of schedule task items containing all construction content, so that the required schedule items can be selected from the schedule dictionary for each project to generate the project schedule.
[0025] Ideally, the design of the schedule dictionary should fully consider the attributes of each item in the schedule list to facilitate structured storage and retrieval of the schedule task dictionary data. Its main fields are shown in Table 2.
[0026] Preferably, the BIM model database is integrated with BIM software to obtain the three-dimensional model information of the building project, and a mapping relationship is established with the schedule dictionary library to ensure that each schedule task dictionary data in the established schedule dictionary library has a corresponding three-dimensional BIM model, which is used to participate in the generation of project plans and to conduct three-dimensional simulation of the actual project.
[0027] Ideally, the BIM model database design should also use structured data storage for various information data of the BIM model, and design fields that map to the dictionary database to complete the mapping with the planning dictionary database, supporting subsequent functional expansion and use, as shown in Table 3:
[0028] like Figure 4 The other fields in the schematic diagram of the BIM model library function prototype shown are required to implement other supporting functions and are not required within the scope of this application.
[0029] like Figure 3 The other fields in the schematic diagram of the planned dictionary library function are required to implement other supporting functions and are not required within the scope of this application.
[0030] Step S2, Data Combination and Processing: Link the spatial structure of the project with the schedule dictionary library to assign corresponding spatial structure attributes to the schedule task dictionary data; select the required schedule task dictionary data (i.e., plan items) from the schedule dictionary library for each project, and generate the project schedule plan based on the selected schedule task dictionary data (i.e., plan items) and according to the spatial structure attributes.
[0031] Here, you can select the required project task list items, i.e., the project task dictionary data, from the project schedule dictionary library for subsequent plan generation: The planned task list items selected from the plan dictionary will be assigned to the project's spatial tree structure, which will be used to organize the project's planned task items primarily based on spatial structure. Figure 7 The diagram shown is a schematic of the prototype of the function of selecting dictionary database data and attaching spatial structure. Since the association settings between the schedule dictionary and BIM model data have been built in the basic database, a project schedule can be generated. The generated project schedule has spatial attributes and a corresponding BIM model. The project schedule is displayed according to spatial attributes, which can more clearly show the location of the corresponding tasks in the actual construction. The BIM model corresponding to the plan can support the display of the actual progress of the project schedule in a three-dimensional model.
[0032] This invention provides a project schedule generation function, which generates a project schedule based on the selected schedule dictionary data and project spatial structure data.
[0033] Preferably, the project schedule generated by this invention is a tree-structured plan data, with the root node being the project name; the second-level nodes being the disciplines; and the third, fourth, and fifth-level nodes being the spatial structure of the project (region, building, floor, etc.). Lower-level nodes below the fifth level exist as child nodes below the higher levels, depending on their specific spatial structure. Figure 8 The image shown is a schematic diagram of the generated project plan functional prototype.
[0034] Preferably, after generating the project schedule plan according to the above steps, the system provides functions for merging, splitting, and expanding the project schedule plan by functional area to complete and improve the generated project schedule plan data, making the project schedule plan more in line with the actual management requirements of different projects.
[0035] The software provides functions for merging, splitting, and expanding project plans by functional area, enabling data completion and improvement of the generated schedule.
[0036] like Figure 9 The image shown is a schematic diagram of the plan merging function prototype. Clicking the "Merge" function button will bring up the "Plan Item Merging" page; as shown... Figure 10 The image shown is a schematic diagram of the data after the planned merger. like Figure 11 The image shown is a schematic diagram of the prototype of the plan splitting function; clicking the "Split" function button will bring up the "Plan Item Split" page, which displays the construction plan data, with floor nodes collapsed by default; like Figure 12The diagram shown is a prototype diagram of the functional area division. After the spatial division and component collection are confirmed, the interface provided by the progress management is called to add the divided data (area and component collection BIM model, associated plan items) to the floor selected in the previous progress management. like Figure 13 The image shows a schematic diagram of the space sorting function; closing the "Space Segmentation Management" page will bring up the "Space Sorting" page.
[0037] The "Spatial Nodes" column on the "Spatial Sort" page only displays the previously selected floors and the areas pushed over after the division is completed. The drop-down menu in the "Subsequent Spatial Nodes" column allows you to select the area of the corresponding floor (multiple selections are possible). Example: -2F is divided into region A, region B, region C, and region D. Then, the logical relationship between the four regions is determined by selecting a subsequent spatial node in the prototype, such as... Figure 14 As shown.
[0038] like Figure 15 The diagram shown illustrates the planned splitting results.
[0039] Clicking the "Expand Ribbon" button will bring up the "Expand Ribbon" page (illustrated). Figure 1 The page is divided into two tables, left and right. The left table displays the construction plan (only showing up to the spatial hierarchy nodes), and the right table is a subordinate table of the left table. When a hierarchy node is selected on the left, the functional areas below it are displayed in the right table. like Figure 16 The diagram shown is a schematic of the prototype unfolded according to its functional areas; like Figure 17 The diagram shows the result after the functional area is expanded.
[0040] Step S3, Project Schedule Display and Execution: The generated project schedule is displayed in the form of a Gantt chart. It also provides functions such as logical relationship connection, logical relationship delay setting, task calendar setting, task constraint setting, and schedule calculation to assist software users in completing the time scheduling of the project schedule. It is used for project schedule execution and analysis results, and supports providing project schedule execution data to external parties.
[0041] Preferably, the present invention provides a function to improve the schedule plan after generating the project schedule plan list. This function can connect planned tasks and logical relationships between tasks in the project schedule plan and set delays, adjust the planned task calendar, set planned task constraints, and support schedule calculation using the CPM critical path method after the above settings are completed, thereby realizing schedule planning and time scheduling. The calendar supports customization, allowing users to define workdays on a weekly basis, add non-workdays in batches, and set workday times. It supports WBS maintenance. The WBS structure is a tree structure, which supports hierarchical movement and quick movement of nodes up, down, left, and right. The job types support six types: task-based jobs, start milestones, finish milestones, collaborative jobs, independent jobs, and WBS jobs. The logical relationships support four types: FS (Complete-Start), SS (Start-Start), SF (Start-Complete), and FF (Complete-Complete). When connecting logical relationships, a delay setting is supported. The delay can be a positive value (indicating a delay) or a negative value (indicating an advance). The task constraints support nine commonly used types: "As late as possible", "Start no earlier than", "Start no later than", "Finish no earlier than", "Finish no later than", "Force start", "Force finish", "Start at", and "Finish at". Supports the quick creation and deletion of logical relationship connections between multiple jobs. The default relationship type for quick connections is FS (Completion-Start). It supports view settings, and the system provides default edit and view views, while also allowing users to customize, save, and adjust views. The Gantt chart display must support the display of target Gantts and support the simultaneous display of target Gantts and currently planned Gantts on the same screen. Supports forward line, data date line, and spotlight display; like Figure 18 The diagram shown is a prototype of the progress calculation and scheduling function.
[0042] Preferably, the functions of logical relationship connection, logical relationship delay setting, job calendar setting, job constraint setting, and progress calculation assist software users in completing the time scheduling of the progress plan, including: 1) Data date: Last data date: The date of the last progress calculation; Current calculation date: The date on which this progress calculation is performed; 2) Critical tasks are defined as: Total float less than or equal to "h": The default value is 0, and the unit is h (hours). After the schedule is calculated, tasks with a total float less than the time value set here are defined as the critical path of the project schedule. Longest path: After schedule calculation, all tasks on a logically connected work path that runs from the start of the project to the end of the project without interruption are defined as the critical path of the project schedule. 3) Used during out-of-order operations: "Out-of-order tasks" refers to tasks in which the actual order of tasks differs from the planned order after the progress feedback data is entered (e.g., tasks A and B are in a FS relationship in the plan, but in reality, task A has not yet started while task B has started, then task B is called out-of-order task).
[0043] Maintaining logical relationships: When calculating the schedule, the remaining time for out-of-order tasks and the planned start time for remaining tasks are still calculated according to the preceding tasks with the already connected logical relationships. Progress skipping method: When calculating the schedule, the remaining time of out-of-sequence tasks and the planned start time of remaining work are no longer calculated based on the preceding tasks with connected logical relationships; Actual Date: When calculating the schedule, the remaining time and planned start time of out-of-order tasks are calculated based on the preceding tasks with connected logical relationships. The planned completion date of the preceding tasks is calculated by working backward from the actual start date of the out-of-order task. Generally, negative total float will occur.
[0044] 4) Tasks without prerequisite logical relationships: Not included in the calculation: When calculating the schedule, the start date and completion date of the work plan that have no prior logical relationship are not included in the calculation and are not modified in any way. Move to Data Date: When calculating the progress, the planned start date of a job with no preceding logical relationship is automatically modified to the current progress calculation date, the original schedule remains unchanged, and the planned completion date is automatically calculated and adjusted based on the modified planned start date and the original schedule. 5) Calculate the calendar for logical relationship delays: Preceding task calendar: When calculating progress, the delay days between logically related tasks are calculated according to the task calendar set in the preceding task. Post-job calendar: When calculating progress, the delay days between logically related jobs are calculated according to the job calendar set for the post-jobs; 24-hour calendar: When calculating progress, the delay days between logically connected tasks are calculated according to a 7-day 24-hour work calendar; Default calendar for the plan: When calculating the progress, the delay days between logically related jobs are calculated according to the default calendar of the current plan. The default calendar used by the current plan is set in the PBS definition. This invention can fully utilize and continuously accumulate enterprise project schedule management knowledge, effectively improve the efficiency of schedule planning for building construction projects in the engineering construction field, standardize the project schedule planning business, and enable the project schedule plan to more accurately guide the project construction work.
[0045] Here, the software architecture of this invention is designed with three layers: basic data layer, data processing layer, and schedule display layer, and is implemented in three steps according to the above three layers.
[0046] BIM Model Database: BIM software is a 3D modeling tool for building information. The BIM model data in this patent application is the 3D modeling data of building construction projects, including various information data such as beams, columns, and slabs, which are used to combine to form the 3D model of the project. Spatial structure data of the project: namely, the spatial composition information data of building construction projects, such as zoning, layering, and building, which is used to identify BIM model data and planning dictionary data, thereby combining the basic data into a schedule plan; Schedule dictionary: This refers to the components of the schedule for building construction projects. In this patent application, the schedule dictionary is categorized from a construction engineering perspective into two main categories: general and specialized. These categories are used to combine components into the project schedule. Examples of the categorization are shown in Table 4.
[0047] According to another aspect of the present invention, a computer-readable storage medium is also provided, having stored thereon computer-executable instructions, wherein when executed by a processor, the computer-executable instructions cause the processor to perform the method described in any of the preceding claims.
[0048] According to another aspect of the present invention, a calculator device is also provided, comprising: processor, and A memory configured to store computer-executable instructions, which, when executed, cause the processor to perform any of the methods described above.
[0049] This invention can solve the problem of project schedule preparation for building construction projects. It can effectively utilize the historical data of similar projects accumulated by the company, including BIM models, planning dictionary, and spatial division, to quickly generate project schedules and guide the project to be executed according to plan, thus standardizing the project schedule preparation and management of building construction projects.
[0050] For detailed descriptions of the various device embodiments of the present invention, please refer to the corresponding sections of the various method embodiments; they will not be repeated here.
[0051] Obviously, those skilled in the art can make various modifications and variations to this application without departing from the spirit and scope of this application. Therefore, if such modifications and variations fall within the scope of the claims of this application and their equivalents, this application also intends to include such modifications and variations.
[0052] It should be noted that the present invention can be implemented in software and / or a combination of software and hardware, for example, using an application-specific integrated circuit (ASIC), a general-purpose computer, or any other similar hardware device. In one embodiment, the software program of the present invention can be executed by a processor to implement the steps or functions described above. Similarly, the software program of the present invention (including associated data structures) can be stored in a computer-readable recording medium, such as RAM memory, a magnetic or optical drive, a floppy disk, or similar devices. Furthermore, some steps or functions of the present invention can be implemented in hardware, for example, as circuitry that works with a processor to perform the various steps or functions.
[0053] Furthermore, a portion of this invention can be applied as a computer program product, such as computer program instructions, which, when executed by a computer, can invoke or provide the methods and / or technical solutions according to the invention through the operation of the computer. The program instructions invoking the methods of the invention may be stored in a fixed or removable recording medium, and / or transmitted via a data stream in a broadcast or other signal-carrying medium, and / or stored in the working memory of a computer device operating according to the program instructions. Here, an embodiment of the invention includes an apparatus comprising a memory for storing computer program instructions and a processor for executing the program instructions, wherein, when the computer program instructions are executed by the processor, the apparatus is triggered to operate the methods and / or technical solutions based on the foregoing embodiments of the invention.
[0054] It will be apparent to those skilled in the art that the present invention is not limited to the details of the exemplary embodiments described above, and that the invention can be implemented in other specific forms without departing from the spirit or essential characteristics of the invention. Therefore, the embodiments should be considered illustrative and non-limiting in all respects, and the scope of the invention is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be embraced within the present invention. No reference numerals in the claims should be construed as limiting the scope of the claims. Furthermore, it is clear that the word "comprising" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices recited in the apparatus claims may also be implemented by a single unit or device in software or hardware. The terms "first," "second," etc., are used to indicate names and do not indicate any particular order.
Claims
1. A method for generating project schedules based on basic data, characterized in that, include: Build the enterprise's BIM model database, the enterprise's schedule dictionary, and the project's spatial structure data. In the enterprise's schedule dictionary, complete the association settings between the schedule task dictionary data and the BIM model data. Link the project's spatial structure to the schedule dictionary library to assign spatial structure attributes to the schedule task dictionary data. Based on the project schedule, the required schedule task dictionary data is selected from the schedule dictionary library, and the project schedule is generated according to the selected schedule task dictionary data and spatial structure attributes. The generated project schedule is displayed in the form of a Gantt chart. It also provides functions such as logical relationship connection, logical relationship delay setting, task calendar setting, task constraint setting, and schedule calculation to assist in completing the time scheduling of the project schedule, for project schedule execution and analysis, and supports providing the project schedule execution and analysis results data to external parties.
2. The project schedule generation method based on basic data as described in claim 1, characterized in that, The spatial structure data of the project is designed in a tree-structured data manner, and the information of the project's partitions, buildings and floors is digitized. This data is then used to select and link the planned task dictionary data in the schedule dictionary library with the spatial structure data of the project.
3. The project schedule generation method based on basic data as described in claim 1, characterized in that, The field content of the spatial structure data of the project includes: space ID, space parent ID, and space name; Build an enterprise schedule dictionary, including: The schedule dictionary is constructed in a multi-level tree structure to organize the schedule items from a professional perspective, forming a complete list of schedule task items that includes all construction content.
4. The project schedule generation method based on basic data as described in claim 1, characterized in that, The fields of the schedule dictionary include: category ID, category parent ID, category name, task ID, task parent ID, task code, task name, module name, whether it is a milestone node, process category, and task description. The fields in the BIM model database include: Category ID, Category Parent ID, Category Name, Model ID, Model Code, Model Name, Name of Building Unit, Material, Main Material Density, Fire Resistance Rating, Mortar Strength Grade, Volume, Type, Corresponding 3D Model, Connection Method, Weight, Remarks, and Corresponding Plan Dictionary ID.
5. The project schedule generation method based on basic data as described in claim 1, characterized in that, The project schedule is a tree-structured plan, with the root node being the project name; the second-level nodes being the disciplines; the third, fourth, and fifth-level nodes being the spatial structure of the project; and lower-level nodes below the fifth level existing as child nodes below the above levels according to their respective spatial structures.
6. The project schedule generation method based on basic data as described in claim 1, characterized in that, After generating the project schedule, it also includes: It provides functions for merging, splitting, and expanding project schedules by functional area, which can be used to complete and improve the generated project schedule data, making the project schedule more in line with the actual management requirements of different projects.
7. The project schedule generation method based on basic data as described in claim 1, characterized in that, The time scheduling of the project schedule supports the following: The calendar supports custom calendars; Supports WBS maintenance; The job types supported include task-based jobs, start milestones, finish milestones, collaborative jobs, independent jobs, and WBS jobs. Logical relations support four types: FS, SS, SF, and FF. When connecting logical relationships, a delay setting is supported, and the delay can be a positive or negative value; The job constraints support the following types: "As late as possible", "Start no earlier than", "Start no later than", "Finish no earlier than", "Finish no later than", "Force start", "Force finish", "Start at", and "Finish at". Supports the quick creation and deletion of logical relationship connections between multiple jobs; the default relationship type for quick connections is FS. Supports view settings functionality; The Gantt chart display supports the display of target Gantts and the simultaneous display of target Gantts and currently planned Gantts on the same screen. Supports forward lines, data date lines, and spotlight displays.
8. The project schedule generation method based on basic data as described in claim 7, characterized in that, It provides functions for logical relationship connection, logical relationship delay setting, job calendar setting, job constraint setting, and progress calculation to assist in completing the time scheduling of the schedule plan, including: Record the date of the last progress calculation and set the date of the current progress calculation; After the schedule is calculated, tasks with a total float less than the set time value can be defined as the critical path of the project schedule. After the schedule is calculated, all tasks on the logically connected work paths that run from the start of the project to the end of the project without interruption can be defined as the critical path of the project schedule. For out-of-order tasks, progress calculations are performed based on maintaining logical relationships, progress skipping methods, or actual dates; Jobs without any preceding logical relationship are scheduled for progress calculation in a way that either does not participate in the calculation or is moved to the data date. The calendar for calculating logical relationship delays is based on the methods of prior task calendar, subsequent task calendar, 24-hour calendar, or the default plan calendar.
9. A computer-readable storage medium having stored thereon computer-executable instructions, wherein, When the computer-executable instructions are executed by a processor, the processor causes the processor to perform the method as described in any one of claims 1 to 8.
10. A calculator device, wherein, include: A processor, and a memory arranged to store computer-executable instructions, which, when executed, cause the processor to perform the method as described in any one of claims 1 to 8.