Intelligent generation method and system of work decomposition structure template and storage medium

Abstract

The invention provides an intelligent generation method and system of a work decomposition structure template and a storage medium, and belongs to the crossing field of information technology and engineering project management. In order to solve the problems that a work decomposition structure template is low in creation efficiency, inconvenient to adjust and poor in large-scale data processing performance, the method comprises the steps that initial input is responded, nodes are retrieved and combined from a preset multi-level WBS metadata standard library, a WBS template is automatically generated, and attributes are hooked; and carrying out persistent storage on the generated template by adopting a redundant data structure containing a pre-calculation hierarchical path. The corresponding system further comprises a memory cache layer of which the data access priority is higher than that of the database so as to improve the calling performance. The template generation efficiency and management fineness are improved, and high performance under large-scale application is guaranteed.

Description

TECHNICAL FIELD

[0001] The present application relates to the cross field of information technology and project management, and particularly relates to an intelligent generation method and system of work breakdown structure templates and a storage medium. BACKGROUND

[0002] In modern large-scale project management, work breakdown structure is the basis of project planning, cost accounting, progress control and resource allocation. A well-defined work breakdown structure with appropriate granularity is crucial to the success of a project.

[0003] In the prior art, project management software usually creates work breakdown structure in an artificial manner or based on a preset template library. For example, some solutions establish a standardized work breakdown structure library, predefine modules of different project types, and when creating a new project, the user selects and combines them to generate an initial work breakdown structure template for the project. However, such prior art solutions still have the following shortcomings: First, the decomposition standard of existing work breakdown structure usually stops at a relatively coarse level and fails to penetrate down to the smallest work unit directly bound to cost, man-hours, and quality acceptance standards, resulting in limited accuracy of cost estimation and progress control based thereon and failing to meet the needs of refined management. Second, the generated templates are usually static, and when project requirements change and partial adjustments to the templates are needed, the user must manually modify all affected subordinate nodes and their associated attributes, which is tedious, inefficient and prone to errors, and lacks an intelligent linkage update mechanism. In addition, as the project scale expands, the level of work breakdown structure deepens and the number of nodes increases dramatically, and the performance of traditional database tree structure query methods (such as recursive query) will decrease sharply, resulting in slow response of the system in generating and calling large-scale work breakdown structure templates, which seriously affects user experience and work efficiency. Finally, the prior art fails to fully exploit the data value contained in the work breakdown structure library, providing forward-looking decision support for project managers during the template generation phase, such as resource conflict warning or cost overrun risk alert. SUMMARY

[0004] The present application aims to provide an intelligent generation method and system of work breakdown structure templates and a storage medium, which aims to solve the problems of coarse decomposition granularity, inconvenient adjustment, low performance in large-scale data processing, and insufficient data value mining in the creation and management of work breakdown structure templates in the prior art.

[0005] To achieve the above object, the application provides an intelligent generation method of work breakdown structure template, comprising: in response to initial input of defining a new project scope, retrieving and combining matched WBS nodes from a preset multi-level work breakdown structure (WBS) metadata standard library, the WBS metadata standard library defining a hierarchical structure from a project macro unit to an atomic level job activity and storing standardized attribute information of each hierarchical node; based on the retrieved and combined WBS nodes, automatically generating a multi-level WBS template of the new project and attaching the standardized attribute information to nodes in the template; and persistently storing the generated WBS template by using a redundant data structure containing a pre-calculated hierarchical path.

[0006] Optionally, the hierarchical structure of the multi-level work breakdown structure (WBS) metadata standard library is a five-level structure of "work area - unit engineering - division - sub-item - sub-sub-item".

[0007] Optionally, the standardized attribute information at least includes a measurement unit, a budget unit price, a man-hour quota or a quality acceptance standard of a node.

[0008] Further, the redundant data structure containing a pre-calculated hierarchical path specifically adds a path field in a node table for storing WBS nodes, the path field being used for storing an ID path from a root node to a current node.

[0009] Optionally, after the multi-level WBS template is generated, the method further comprises: parsing attribute information of an atomic level job activity node in the template; combining preset project resource information to perform resource demand pre-analysis; and generating a warning information when a potential resource conflict or skill shortage is identified.

[0010] Optionally, the method further comprises: when it is monitored that a user modifies a key attribute of any parent node in the WBS template, automatically triggering a linkage update.

[0011] Further, the linkage update comprises: retrieving a child node and its attribute matched with the modified key attribute from the WBS metadata standard library; recommending the linkage update to the user; and automatically completing batch modification of all related child nodes in response to a confirmation instruction of the user.

[0012] Optionally, the method further comprises: when data of the persistently stored WBS template is called, performing data caching through a memory cache layer; wherein the memory cache layer adopts a differentiated caching strategy, the differentiated caching strategy comprising: setting a longer validity period for standardized and high-frequency accessed template data; and setting a shorter validity period or a lower cache priority for non-standard template data generated after dynamic adjustment of the user.

[0013] The application further provides an intelligent generation system of a work breakdown structure template, comprising: a WBS metadata standard library, which is preset as a multi-level structure, the multi-level structure defining a hierarchical structure from a project macro unit to an atomic level work activity, and storing standardized attribute information of each hierarchical node; a WBS template generation module, configured to respond to initial input of defining a new project scope, retrieve and combine matched WBS nodes from the WBS metadata standard library to automatically generate a multi-level WBS template of the new project, and attach the standardized attribute information to nodes in the template; a data storage and calling module, configured to store and call the WBS template, the data storage and calling module comprising: a database, configured to persistently store a tree structure of the WBS template by using a redundant data structure containing pre-calculated hierarchical paths; and a memory cache layer, configured to cache frequently accessed WBS data, and the data access priority of the memory cache layer is higher than that of the database.

[0014] The application further provides a computer readable storage medium, which stores a computer program, and the computer program is executed by a processor to implement the intelligent generation method of the work breakdown structure template according to any one of the preceding.

[0015] Compared with the prior art, the application has the following beneficial effects: Firstly, by constructing the WBS metadata standard library sinking to the atomic level work activity and realizing the automatic generation of the template, the traditional manual creation work is shortened to the minute level, and meanwhile, the cost, progress, quality and other management elements can be accurately associated to the minimum work unit, so that the fineness and efficiency of project management are significantly improved.

[0016] Secondly, the scheme not only generates the WBS template, but also actively utilizes the data in the template to perform resource pre-analysis and risk pre-warning, so that the project manager can early discover potential problems and realize the change from passive management to active prevention.

[0017] In addition, through the intelligent linkage adjustment mechanism, when the attribute of the upper node is changed, the system can automatically recommend and execute batch update of the lower node, greatly simplifying the template maintenance work and ensuring the consistency of the data.

[0018] Finally, by combining the database structure of the pre-calculated hierarchical path with the differentiated intelligent cache strategy, the performance bottleneck in the calling of large-scale and high-dynamic WBS data is effectively solved, so that the system can still provide a smooth experience when processing complex projects, and the flexibility and high performance are taken into account. BRIEF DESCRIPTION OF DRAWINGS

[0019] Other features, objects, and advantages of the application will become more apparent from the following detailed description when read in conjunction with the accompanying drawings: Figure 1 An architecture diagram of a system for intelligent generation of a work breakdown structure template according to an embodiment of the present application; Figure 2 A flowchart of a method for intelligent generation of a work breakdown structure template according to an embodiment of the present application; Figure 3 A signaling interaction timing diagram of a WBS template generation and calling process according to an embodiment of the present application; Figure 4 A schematic diagram of a WBS data storage structure according to an embodiment of the present application; Figure 5 A flowchart of an intelligent linkage adjustment method according to an embodiment of the present application. DETAILED DESCRIPTION

[0020] The application will be described in detail below with specific embodiments. The following embodiments will help those skilled in the art to further understand the application, but do not limit the application in any form. It should be noted that for those skilled in the art, without departing from the concept of the present application, a number of changes and improvements can be made. These are within the scope of the present application.

[0021] Embodiment 1 The embodiments of the present application provide a method and system for intelligent generation of a work breakdown structure template, which is particularly suitable for large-scale project management fields such as municipal engineering and construction engineering. In an embodiment of the present application, the technical scheme constructs a fine work breakdown structure metadata standard library and combines an efficient template generation and data access mechanism to realize rapid, standardized and automated generation of a work breakdown structure template.

[0022] Referring to Figure 1 , an architecture diagram of a system for intelligent generation of a work breakdown structure template according to an embodiment of the present application is shown. As Figure 1 shown, the system can be logically divided into three layers, specifically including a user interface 10, a business logic layer 20 and a data persistence layer 30.

[0023] The user interface 10, as an entrance for the system to interact with the user, can be a graphical user interface, such as a web application or a desktop client running on a personal computer, a tablet computer or a mobile terminal. Project managers input initial project information, view generated templates, make template adjustments and receive system warning or recommendation information through the user interface 10.

[0024] The business logic layer 20 serves as the core processing hub of the system and is responsible for implementing the main logic of the technical solution of the present application. In the present embodiment, the business logic layer 20 at least includes a WBS template generation module 21, which is mainly responsible for generating a work breakdown structure template in response to a request from the user interface 10.

[0025] The data persistence layer 30 is used for data storage and management and provides data support for the business logic layer 20. Specifically, it mainly includes two parts: a WBS metadata standard library 31 and a memory cache layer 32. The WBS metadata standard library 31 is used to permanently store standardized work breakdown structure nodes and their attribute information and can be implemented using technologies such as relational databases (e.g., MySQL, PostgreSQL) or non-relational databases (e.g., MongoDB). The memory cache layer 32 is used to temporarily store frequently accessed data to improve data read speed and can be implemented using technologies such as high-speed memory databases (e.g., Redis, Memcached). As an optional implementation, the data access priority of the memory cache layer 32 is set to be higher than that of the WBS metadata standard library 31.

[0026] The working process of the intelligent generation method of a work breakdown structure template provided by the present embodiment will be described in detail below in conjunction with the flowchart shown in Figure 2

[0027] The method includes: step S101, constructing a WBS metadata standard library. It can be understood that this step is the foundation of the entire system. In the present embodiment, a WBS metadata standard library 31 containing five levels is constructed in view of the characteristics of municipal engineering project management. The five levels are, from top to bottom, “work area”, “unit project”, “division project”, “subdivision project”, and “sub-subdivision project”. The “sub-subdivision project” as the smallest granularity of decomposition represents an atomic-level work activity that can be independently metered, priced, arranged for a duration, and set with quality acceptance standards. This fine-grained hierarchical structure enables various indicators of project management to be sunk to the most basic execution unit, providing a data foundation for fine-grained management.

[0028] ​It is noted that for each level of nodes in the standard library, a rich set of standardized attribute information is pre-stored. These attribute information includes at least the unique identifier of the node, the node name, the node code, the unit of measurement, the budget unit price, the man-hour quota, the required main materials, the required main machinery, the quality acceptance standard, the safety specification requirement, and the skill level requirement of the required personnel, etc. For example, for a "sub-item work" node named "cement stabilized macadam base paving", its attributes can include: the unit of measurement is "cubic meter", the budget unit price is "350 yuan / cubic meter", the man-hour quota is "0.5 man·workday / cubic meter", and the quality acceptance standard refers to "CJJ 1-2008 Urban Road Engineering Construction and Quality Acceptance Standard" article X.X.X. These standardized data are pre-recorded and maintained in the WBS metadata standard library 31 by experienced engineering experts to ensure their authority and accuracy.

[0029] Subsequently, in step S102, the system receives the initial input of the project. When the project manager needs to create a work breakdown structure for a new municipal road project, he / she can start the template generation process through the user interface 10. The system will guide the project manager to input several key, macroscopic project scope information. For example, the project manager can need to select the project type as "municipal road engineering", and define the first "work zone" of the project as "work zone 1", and define an "unit work" under the work zone as "main line pavement work". These information constitutes the initial input to define the scope of the new project.

[0030] Correspondingly, in step S103, the system automatically generates an initial WBS template. The WBS template generation module 21 starts the automated process after receiving the initial input in step S102. Specifically, the WBS template generation module 21 takes the "main line pavement work" input by the user as the starting point, and queries the WBS metadata standard library 31 to find all standard "division work" nodes with "main line pavement work" as the parent node, assuming the query result is "pavement base" and "pavement surface". Then, the module continues to query the standard library with "pavement base" as the parent node to find its standard "item work" nodes, such as "cement stabilized macadam base", and so on. By level-by-level downward retrieval and matching, the WBS template generation module 21 automatically combines the complete hierarchical structure of "division-item-sub-item", for example, a hierarchical branch of "main line pavement work" -> "pavement base" -> "cement stabilized macadam base" -> "paver paving" can be generated.

[0031] While the node structure is being combined, the WBS template generation module 21 also automatically links all the attribute information (such as budget unit price, man-hour quota, etc.) preset in the WBS metadata standard library 31 for each standard node to the corresponding nodes in the newly generated template. Finally, a complete, detailed, and attribute-complete multi-level WBS initial template is generated and presented on the user interface 10. The entire process does not require human intervention and is usually completed within a few seconds, thereby greatly improving work efficiency.

[0032] To solve the performance bottleneck problem of large-scale WBS data calling, the embodiment adopts an optimized data storage and calling mechanism. Please refer to Figure 4 , which shows a schematic diagram of the WBS data storage structure in the embodiment. In the embodiment, the tree structure 40 of the WBS is persistently stored in the WBS metadata standard library 31 (for example, a MySQL database). The storage method adopts a modified adjacency list model. Specifically, in a node table 41 for storing WBS nodes, in addition to the conventional fields such as node ID and node name, a redundant path field 411 is additionally added. The field is used to store the complete ID path from the root node to the current node, and the IDs are connected by a specific separator (such as "-"). For example, for the "unit project X" node with ID 120, the ID of its parent node "work area 1" is 15, and the ID of the root node "project A" is 1, so the value stored in the path field 411 of the node is "1-15-120".

[0033] It can be understood that this redundant data structure containing pre-computed hierarchical paths has the technical advantage of being able to greatly speed up hierarchical queries. Traditional recursive queries or common table expressions will have a sharp decline in performance when the hierarchy is deep and the nodes are many. In contrast, using the present solution, only one fuzzy matching query based on the path field (for example, SELECT * FROM wbs_node_table WHERE path LIKE '1-15-%') needs to be executed, and all nodes that meet the conditions can be retrieved efficiently at one time, and the query efficiency can be improved by several orders of magnitude. After generating the WBS template (step S103), the system will persistently store the template data containing complete node and attribute information according to the structure shown in Figure 4 .

[0034] In addition, please refer to Figure 3which shows the signaling interaction timing diagram of the WBS template generation and invocation process. To further improve performance, this embodiment introduces a memory cache layer 32. When the WBS template generation module 21 needs to obtain WBS node data (for example, when step S103 is executed), it will first initiate a query request to the memory cache layer 32. If the required data exists in the cache (i.e. "cache hit"), the memory cache layer 32 will directly return the data for the WBS template generation module 21 to use immediately, and the entire process takes very little time (usually in milliseconds). If the required data does not exist in the cache (i.e. "cache miss"), the WBS template generation module 21 will only then initiate a database query to the backend WBS metadata library 31. After obtaining the data from the database, the WBS template generation module 21 uses it to assemble the template on the one hand, and asynchronously writes the query result to the memory cache layer 32 on the other hand, so that the next same request can hit the cache. Through this "cache first" strategy, the system can provide extremely fast response experience for frequently accessed standard templates and node data.

[0035] Finally, at step S107, the generated WBS template can be output for subsequent project cost budgeting, schedule planning, resource allocation, and a series of project management activities.

[0036] Embodiment 2 As an optional implementation, this embodiment further demonstrates the extended application of the technical solution of the present application in intelligent decision support on the basis of embodiment 1. Specifically, this embodiment adds a step of intelligent analysis and early warning after the generation of the WBS template, aiming to use the refined data in the template to provide forward-looking resource conflict risk prompts for project managers.

[0037] Please refer again to Figure 1 In the system architecture of this embodiment, the business logic layer 20 also contains an intelligent analysis and early warning module 22. This module is connected to the WBS template generation module 21 and is activated after the generation of the WBS template.

[0038] Referring to Figure 2 the flowchart, after executing step S103 (automatically generating an initial WBS template), this embodiment will continue to execute step S104: performing intelligent analysis and early warning. This step is executed by the intelligent analysis and early warning module 22.

[0039] To achieve resource pre-analysis, the system usually maintains a "project available resource library" in addition to the WBS metadata standard library 31. This resource library can be a separate database table or service that records information about various resources that the project currently or will have in the future plan, especially human resources. For example, it stores information about the number of workers of various types available on the project, their skill levels (e.g., junior, intermediate, and senior), and their available time periods.

[0040] The specific working process of step S104 is as follows: First, the intelligent analysis and early warning module 22 receives the complete WBS template generated by the WBS template generation module 21 as input. Subsequently, the module traverses the entire tree structure of the WBS template, focusing on and parsing the attribute information of the atomic-level work activity nodes (i.e., "sub-divisional engineering" nodes) at the bottom level, from which it extracts two key attributes: "labor quota" and "personnel skill level requirement". At the same time, it also combines the start and end times of each node planned in the template, which can be initially estimated based on the standard duration and dependency relationships when the template is generated, or initially set by the user after generation.

[0041] Next, the intelligent analysis and early warning module 22 performs resource demand summary calculation. Specifically, this calculation logic can include: traversing in a fixed time unit (e.g., "week") as a period, for each week in the project period, initializing a mapping table for recording resource demand in the week. Subsequently, traverse all tasks (i.e., sub-divisional engineering) in the WBS template, and determine whether the execution period of each task intersects with the current week. If there is an intersection, obtain the personnel skill level required by the task and its weekly labor demand (which can be obtained by dividing the "labor quota" by the number of weeks of the task), and add the weekly labor demand to the total demand of the corresponding skill level in the mapping table. After traversing all tasks, the detailed resource demand distribution for each week in the project period is obtained.

[0042] Then, the intelligent analysis and early warning module 22 compares the calculated weekly resource demand with the available supply of the corresponding resource in the "project available resource library". The available supply can be calculated by "resource quantity × weekly available working hours of a single resource".

[0043] Finally, the system generates a warning message when a potential resource conflict or skill shortage is identified. When the total demand for a certain resource exceeds the total supply within a certain time period, the system determines that there is a resource conflict. For example, after analysis, the intelligent analysis and warning module 22 finds that in the 5th week of the project plan, three different sub-projects in the template (such as "steel structure A welding", "pipe B butt joint", and "pre-embedded part C installation") all require "senior welder", and the total man-hour demand is 300 standard man-hours. At this time, the system queries the "project available resource library" and finds that there are only 2 senior welders on the project, and assuming that they can provide a total of 80 hours of effective working hours per week, the system will automatically generate a warning message.

[0044] The warning message is clearly displayed to the project manager through the user interface 10, and the content may be: "Warning: there is a serious shortage of'senior welder' resources in the 5th week of the project, and the expected gap is 220 man-hours. Please check the progress plan of the relevant sub-projects or consider increasing resource allocation." At the same time, the system can also highlight the three sub-projects nodes that cause the resource conflict in the WBS tree view of the user interface 10 and provide links to facilitate the user to quickly locate and analyze the problem.

[0045] Through the scheme provided by the embodiment, the WBS template is no longer just a static and passive work structure list, but is transformed into an active and intelligent decision support tool. It enables project managers to foresee potential resource bottleneck problems in advance before the project actually starts, so that there is enough time to make plan adjustments, resource coordination or personnel recruitment, achieving "prevention" rather than "remedy" of project risks, and providing great guarantee for the smooth progress of the project.

[0046] Embodiment 3 This embodiment is based on embodiment 1 and focuses on how the technical scheme of the present application solves the problem of low efficiency and inconvenience of WBS template adjustment in the prior art. By introducing an intelligent linkage adjustment mechanism, the embodiment realizes automatic and intelligent response to template modification, thereby greatly improving the maintenance efficiency and data consistency of the template.

[0047] Please refer again to Figure 1 In the system architecture of the embodiment, the business logic layer 20 also includes an intelligent linkage adjustment module 23. The module also works with the WBS template generation module 21 and monitors the user's modification operation on the WBS template on the user interface 10 in real time.

[0048] Refer to Figure 2The flowchart shows that when the user adjusts the template in step S105, if the adjustment meets certain conditions, step S106 will be triggered, i.e., intelligent linkage update will be performed. This step is handled by the intelligent linkage adjustment module 23.

[0049] Please combine Figure 5 The flowchart of the intelligent linkage adjustment method shown below provides a detailed explanation of the working process of this embodiment.

[0050] The process begins with step S501: monitoring changes to parent node attributes. When a user edits a generated WBS template through user interface 10, a "change monitoring and recommendation engine" within the intelligent linkage adjustment module 23 is activated. This engine specifically monitors modifications made by the user to certain fields defined as "key attributes" of non-leaf nodes (such as "sub-projects" and "items") in the WBS template. These key attributes typically determine the composition of their subordinate child nodes, such as material type, construction process, and applicable standards.

[0051] Taking a generated municipal road engineering WBS template as an example, suppose the project manager needs to change the base material of a section of the roadbed from "cement-stabilized crushed stone" to "asphalt-stabilized crushed stone" based on design changes. The project manager finds the corresponding "sub-item" node in the WBS tree view of user interface 10, whose original name or key attribute is "cement-stabilized crushed stone base", and modifies it to "asphalt-stabilized crushed stone base".

[0052] When the user completes this modification, the change monitoring and recommendation engine will immediately capture the change event, and the process will then proceed to step S502: query the standard library to match the child nodes.

[0053] In step S502, the intelligent linkage adjustment module 23 receives change information, including the modified node ID, the changed attribute fields, and the new attribute value ("asphalt-stabilized crushed stone base course"). The module performs the following actions: First, it identifies all direct or indirect "sub-sub-item" nodes under the modified "sub-item" node; then, using the new key attribute "asphalt-stabilized crushed stone base course" as the query keyword, it searches the WBS metadata standard library 31 to find a complete set of standard "sub-sub-item" and its complete attribute information that matches the construction process of "asphalt-stabilized crushed stone base course". For example, the standard library may define that the sub-sub-item activities corresponding to "asphalt-stabilized crushed stone base course" should include "asphalt material heating", "mixture mixing", "paving", and "compaction", and the budget unit price, time quota, and quality acceptance standards of these activities are different from those of the sub-sub-item activities of "cement-stabilized crushed stone base course".

[0054] The flow then proceeds to step S503: generating an update recommendation. The intelligent linkage adjustment module 23 compares the query result of step S502 with the old child nodes and their attributes in the current template, and generates a clear and easy-to-understand update recommendation based on this. The recommendation is presented to the user in the form of a dialog box or prompt information through the user interface 10, clearly informing the user of the specific linkage modifications recommended for the subordinate nodes due to the changes in the superior nodes. For example, the pop-up dialog box may display the following content: “The system detects that you have changed the type of the sub-project ‘cement stabilized macadam base’ to ‘asphalt stabilized macadam base’. This will usually affect the composition and attributes of its subordinate sub-items. The system recommends the following linkage updates: 1. Delete the atomic sub-item: ‘cement curing’. 2. Add atomic sub-items: ‘asphalt material heating’, ‘mixture mixing’. 3. Update the budget unit price of atomic sub-item ‘paving’: from 350 yuan / cubic meter to 480 yuan / cubic meter. 4. Update the quality acceptance standard of atomic sub-item ‘rolling’: from specification A.1.2 to specification B.3.4. Do you confirm to perform this linkage update?” Next is decision step S504: user confirmation. The user can choose “yes” or “no” according to his own judgment. This design of human-computer interaction not only plays the intelligence of the system, but also retains the user's final decision-making power to avoid incorrect automatic modifications.

[0055] If the user chooses “yes” to confirm the linkage update, the flow proceeds to step S505: batch updating child node attributes. The intelligent linkage adjustment module 23 will immediately perform a transactional batch database operation to apply all the recommended changes (including deleting nodes, adding nodes, and modifying node attributes) to the WBS template data of the current project at once. After the operation is completed, the WBS tree on the user interface 10 will be refreshed to display the updated new child node structure and attributes that fully match the superior nodes. If the user chooses “no”, the flow ends and the template will remain in the state after the user manually modifies the parent node, without any changes to the child nodes.

[0056] Through the intelligent linkage adjustment mechanism provided by this embodiment, the tedious, time-consuming and error-prone work of manually finding, checking and modifying multiple subordinate nodes one by one by the project manager is simplified to a “confirmation” click. This not only greatly improves the efficiency of dynamic adjustment of the WBS template during the project cycle, but more importantly, it ensures the high consistency and accuracy of the internal data of the WBS structure, avoiding the confusion of cost, schedule, quality and other management data due to manual modification omissions.

[0057] Embodiment 4 This embodiment introduces a more refined and intelligent differentiated caching strategy on the basis of the caching mechanism described in Embodiment 1. The strategy aims to optimize the resource utilization efficiency of the memory cache layer 32 to better adapt to the complex scenario of coexistence of standard templates and dynamically customized templates in actual applications, thereby improving the overall throughput capacity and scalability of the system while ensuring high performance of the system.

[0058] In Embodiment 1, the basic principle of using a memory cache layer 32 (such as a Redis cluster) to accelerate data access is described. However, a simple caching strategy can cause a problem: when users frequently personalize WBS templates (as described in Embodiment 3), a large number of one-time, non-standard "customized" WBS templates will be generated. If these customized template data are all stored in the cache without distinction, they can quickly fill up the valuable cache space and, according to the general eviction policy (such as least recently used), push out those "standard template" data that are more widely and frequently accessed, thereby causing the overall cache hit rate to drop and the system performance to fluctuate.

[0059] To solve this problem, the data storage and calling module of this embodiment adopts a differentiated caching strategy for the management of the memory cache layer 32. The core idea of this strategy is to set different caching behaviors, especially different valid periods and eviction priorities, for WBS data of different types and different access frequencies.

[0060] The specific working process of this strategy is as follows: First, the cache module will classify and mark the data when storing WBS data in the memory cache layer 32. The system can clearly identify the source and nature of the data, which can be mainly divided into two categories: 1. Standard template data: refers to standard WBS nodes or templates that are read directly from the WBS metadata standard library 31 without any user modification and can be reused by multiple projects. For example, a complete "standard two-level highway WBS template" or a commonly used "box culvert structure division engineering" node set. 2. Dynamic template data (or non-standard template data): refers to WBS templates that are generated after user dynamic adjustment and are usually unique to a specific project. For example, the specific WBS template generated after the user modifies the base material to "asphalt stabilized gravel" in Embodiment 3.

[0061] After classifying the data, the system adopts different strategies when caching these data: For standard template data, due to its high reusability and high access frequency, the system sets a longer cache expiration period and a higher cache priority for it. For example, when the system loads the complete data of a "standard municipal road template" into the memory cache layer 32, the system can call the corresponding cache setting instruction and set a longer cache expiration period, for example, 24 hours. At the same time, when the priority-based eviction strategy is configured, this type of data is assigned a high priority, so that it is not easily evicted when the memory is tight.

[0062] For dynamic template data, due to its usually one-time or low-frequency access, the system sets a shorter cache expiration period and a lower cache priority for it. For example, after the user completes an intelligent linkage adjustment and generates a "customized" WBS template, the system sets a very short cache expiration period when storing it in the cache, for example, 10 minutes or less. Setting a shorter expiration period means that even if this customized template is not accessed again in a short period of time, it will automatically expire and be cleared from the cache, thereby actively releasing cache space. At the same time, the lower priority ensures that when the cache memory reaches the upper limit and needs to perform data eviction, the system will preferentially select these low-priority, temporary dynamic template data for removal.

[0063] It can be understood that this differentiated caching strategy ultimately achieves intelligent and efficient allocation of cache resources. It ensures that the standard template data that has the greatest impact on the overall performance of the system and is frequently called can be long-term and stable in the cache, thereby guaranteeing the extreme performance and millisecond-level response of core business scenarios (such as creating a new project, calling a standard module). At the same time, it also takes into account the response speed of low-frequency businesses (such as reviewing a certain historical customized template), because these data can still be quickly obtained from the cache in a short period of time. More importantly, the strategy effectively avoids the long-term occupation and pollution of cache space by a large number of one-time customized template data through the active expiration and preferential eviction mechanism, maintains the high hit rate and healthy state of the cache system, and significantly improves the resource utilization, stability and scalability of the entire system.

[0064] The application also provides a computer readable storage medium having a computer program stored thereon, wherein the computer program, when executed by a processor, can implement the method of any one of embodiments 1 to 4 or a combination thereof. The storage medium can be any electronic, magnetic, optical or other physical device capable of storing program codes, such as read-only memory, random access memory, flash memory, hard disk, optical disc, etc.

[0065] Those skilled in the art know that, in addition to implementing the system provided by the present application and each device, module and unit thereof in the form of pure computer readable program code, the system provided by the present application and each device, module and unit thereof can also be implemented in the form of logic gates, switches, application specific integrated circuits, programmable logic controllers and embedded microcontrollers, etc. by logically programming the method steps to achieve the same functions. Therefore, the system provided by the present application and each device, module and unit thereof can be considered as a hardware component, and the devices, modules and units included therein for achieving various functions can also be considered as structures within the hardware component; the devices, modules and units for achieving various functions can also be considered as both software modules implementing methods and structures within hardware components.

[0066] The specific embodiments of the present application are described above. It needs to be understood that the present application is not limited to the specific embodiments described above, and various changes or modifications can be made by those skilled in the art within the scope of the claims, which does not affect the essential content of the present application. The embodiments of the present application and the features in the embodiments can be combined with each other in any manner without conflict.

Claims

1. An intelligent generation method of a work breakdown structure template, characterized by, The method comprises: in response to initial input defining a new project scope, retrieving and combining matching WBS nodes from a preset multi-level WBS metadata standard library, the WBS metadata standard library defining a hierarchical structure from a project macro unit to an atomic level job activity and storing standardized attribute information of each hierarchical node; based on the retrieved and combined WBS nodes, automatically generating a multi-level WBS template for the new project and attaching the standardized attribute information to nodes in the template; and persistently storing the generated WBS template in a redundant data structure containing pre-calculated hierarchical paths.

2. The method of claim 1, wherein, The hierarchical structure of the multi-level WBS metadata standard library is a five-level structure of "work area-unit project-part-sub-part-sub-part".

3. The method of claim 1, wherein, The standardized attribute information at least includes the unit of measurement, budget unit price, man-hour quota or quality acceptance standard of the node.

4. The method of claim 1, wherein, The redundant data structure containing pre-calculated hierarchical paths specifically adds a path field in the node table used to store WBS nodes, and the path field is used to store the ID path from the root node to the current node.

5. The method of claim 1, wherein, After generating the multi-level WBS template, the method further comprises: parsing the attribute information of the atomic level job activity node in the template; combining the preset project resource information to perform resource demand pre-analysis; and generating a warning information when a potential resource conflict or skill shortage is identified.

6. The method of claim 1, wherein, The method further comprises: when it is monitored that a user modifies a key attribute of any parent node in the WBS template, automatically triggering a linkage update.

7. The method of claim 6, wherein, The linkage update comprises: retrieving from the WBS metadata standard library the child nodes and their attributes that match the modified key attribute; recommending to the user to perform the linkage update; and in response to the user's confirmation instruction, automatically completing batch modification of all related child nodes.

8. The method of claim 1, wherein, The method further comprises: when data of the persistently stored WBS template is called, data is cached through a memory cache layer; wherein the memory cache layer adopts a differentiated caching strategy, and the differentiated caching strategy comprises: setting a longer validity period for standardized and high-frequency access template data; and setting a shorter validity period or a lower cache priority for non-standard template data generated after user dynamic adjustment.

9. An intelligent generation system of a work breakdown structure template, characterized by, The method comprises: a WBS metadata standard library, preset as a multi-level structure, the multi-level structure defining a hierarchical structure from a project macro unit to an atomic level job activity and storing standardized attribute information of each hierarchical node; a WBS template generation module for retrieving and combining matching WBS nodes from the WBS metadata standard library in response to initial input defining a new project scope, to automatically generate a multi-level WBS template for the new project and attach the standardized attribute information to nodes in the template; a data storage and calling module for storing and calling the WBS template, the data storage and calling module comprising: a database for persistently storing a tree structure of the WBS template in a redundant data structure containing pre-calculated hierarchical paths; And a memory cache layer is used to cache the high frequency accessed WBS data, and the data access priority of the memory cache layer is higher than the database.

10. A computer-readable storage medium, characterized in that, A computer program is stored on the computer readable medium, and the computer program is executed by the processor to implement the method of any one of claims 1 to 8. A computer program is stored on the computer readable medium, and the computer program is executed by the processor to implement the method of any one of claims 1 to 8.

Images