Engineering project management system and method based on general contracting document management system

Abstract

The application relates to the technical field of engineering project management, and provides an engineering project management system and method based on a general contracting file management system. The system comprises a file system management module, a task management module and an early warning management module. The file system management module is used for constructing a multistage file management system directory in stages according to management levels, forming file management systems corresponding to the management levels, and outputting an audited project file management system. The task management module is used for receiving the audited project file management system, generating a task list and distributing the task list to corresponding persons in charge. The early warning management module is connected with the task management module, is used for receiving completion state information, generating multistage early warning information according to the relationship between a task completion time and a preset threshold, and sending the multistage early warning information to persons in charge of the corresponding management levels. The system can take the file management system as a core link, realize the step-by-step transmission of management standards, the automatic scheduling of management tasks and the active early warning of project risks.

Description

Technical Field

[0001] This application relates to the field of engineering project management technology, specifically to an engineering project management system and method based on a general contracting document management system. Background Technology

[0002] Engineering, Procurement, and Construction (EPC) projects typically encompass multiple sectors, including water conservancy and hydropower, new energy, municipal transportation, and building construction. These projects are large-scale, involve numerous participating units, and have lengthy management cycles. With the rapid development of the construction industry, the business processes involved in project management have become increasingly complex. Management content has expanded from traditional schedule and cost control to comprehensive management activities covering more than ten areas, including safety management, quality supervision, contract performance, resource allocation, and document collection. Against this backdrop, various engineering project management information systems have emerged, aiming to improve the efficiency and standardization of project management through digital means.

[0003] However, existing project management systems still face several common problems in practical applications. First, most systems are horizontally divided according to business function modules, lacking a vertical management thread that runs through the entire project lifecycle, making it difficult to establish unified execution standards for management requirements at each stage of the project. Second, projects in different industries vary significantly in management granularity and focus, while existing systems often use a single management template, making it difficult to simultaneously meet the dual needs of standardized control and personalized adaptation. Third, large engineering companies often have multiple professional units and dozens of parallel projects under their jurisdiction, making it difficult for headquarters management to achieve real-time awareness of the execution status of remote projects; by the time problems are discovered, the optimal window for intervention has often passed.

[0004] In summary, existing project management technologies suffer from the following main shortcomings: First, the lack of a management framework that spans the entire project lifecycle and supports multi-level collaboration makes it easy for management requirements to be misinterpreted or overlooked during the transmission of information at each level. Second, the lack of a unified organization and scheduling mechanism for the process deliverables generated by each business segment results in management work relying primarily on manual follow-up, with insufficient automation. Third, the monitoring methods for project execution status are relatively passive, failing to establish proactive early warning capabilities based on management rhythms, leading to delayed risk identification and affecting the timeliness of management decisions. Therefore, there is an urgent need for a project management technology solution that can organically integrate the transmission of management standards, automatic task scheduling, and proactive risk early warning. Summary of the Invention

[0005] In view of this, the embodiments of this application provide an engineering project management system and method based on the general contracting document management system. It can use the document management system as the core link to realize the hierarchical transmission of management standards, the automatic scheduling of management tasks, and the proactive early warning of project risks, thereby effectively solving the technical problems in existing engineering project management technologies such as the lack of vertical integration of management architecture, reliance on manual task promotion, and passive and delayed risk identification.

[0006] The first aspect of this application provides an engineering project management system based on a general contracting document management system, including: a document system management module, a task management module, and an early warning management module; The document system management module is used to build a multi-level document management system directory according to the management level. Each management level can be customized and extended based on the document management system directory of the previous level to form a document management system corresponding to each management level, and output the approved project document management system. The task management module is connected to the file system management module and is used to receive the reviewed project file management system, generate a task list and assign it to the corresponding responsible person according to the preset time nodes and update cycles of each file item, and summarize the completion status information of each task. The early warning management module is connected to the task management module and is used to receive the completion status information, generate multi-level early warning information based on the relationship between the task completion time and a preset threshold, and send the multi-level early warning information to the person in charge of the corresponding management level.

[0007] In one embodiment, the multi-level document management system directory includes an enterprise-level document management system directory, a professional unit-level document management system directory, and a project department-level document management system directory; The enterprise-level document management system catalog is maintained by the enterprise's competent department in accordance with the engineering general contracting management specifications and distributed from top to bottom to various professional units; The professional unit-level document management system catalog is formed by customizing and expanding the received enterprise-level document management system catalog, taking into account the relevant industries and professional fields, and then distributed to the project departments under its jurisdiction. The project department-level document management system catalog is compiled based on the received professional unit-level document management system catalog and combined with the actual management needs of the project. It clarifies the responsible person and completion time for each document item. After compilation, it is submitted to the corresponding professional unit for review. After the review is approved, the document system management module outputs the project department-level document management system catalog as the reviewed project document management system, and the task management module generates the task list accordingly.

[0008] In one embodiment, the enterprise-level document management system directory includes multiple management categories, and each management category has several document items; the document items include preset basic management actions, which are standardized performance indicators that each management level should follow when performing project management; The document system management module is also configured to: synchronously configure corresponding template files for each document item, and the template files are distributed to each professional unit along with the enterprise-level document management system directory.

[0009] In one embodiment, the system further includes a template library management module; The template library management module is connected to the file system management module and is used to receive file output templates uploaded by each management level and perform standardized management to form a file system template library. The template library management module is also configured to: respond to the template selection request of the administrator, match and output the corresponding template from the document system template library to assist in the compilation of the results of each document item in the document management system; the templates in the document system template library support custom adjustment to adapt to the scale, complexity and industry characteristics of different projects.

[0010] In one embodiment, the system further includes a document generation and collection module; The document generation and collection module is connected to the document system management module. It is used to convert the content filled in the business form into standardized result documents according to the preset document template, and to collect the result documents to the corresponding positions in the multi-level document management system directory according to the document collection rules in the document management system. The information to be filled in the business form includes at least one of the following: project information, contract information, and security management information.

[0011] In one embodiment, the early warning management module generates the multi-level early warning information in the following manner: The execution status of each task is classified and identified according to the preset warning level. The warning level includes at least normal status, risk status and lagging status. The normal status means that the task progress is in line with expectations or has been completed on time. The risk status means that the task is close to the completion date and there is a potential risk of delay. The lagging status means that the task progress has deviated significantly from the plan. The early warning management module is further configured to send an early warning reminder to the person in charge of the corresponding management level when the execution status of a task changes from the normal state to the risk state or the lagging state; the person in charge of the corresponding management level includes at least one of the heads of enterprise functional departments, heads of professional unit management, and heads of project department management.

[0012] In one embodiment, the system further includes an intelligent archiving module; The intelligent archiving module is connected to the document system management module and is used to receive the output documents in the document management system through an interface with the external document management system, and perform classification, volume assembly, numbering and archiving operations on the output documents to realize data connection between the document management system and the external document management system.

[0013] In one embodiment, the system adopts a front-end and back-end separation architecture and supports concurrent access of at least one application terminal through reverse proxy and load balancing; the application terminal includes a web terminal, a mobile terminal, and a large-screen display terminal.

[0014] A second aspect of this application provides an engineering project management method based on the engineering project management system of the first aspect, comprising: A multi-level document management system directory is constructed according to the management hierarchy. Each management level makes custom extensions based on the document management system directory of the previous level to form a document management system corresponding to each management level. The document management system is then reviewed and the reviewed project document management system is output. Based on the preset time nodes and update cycles of each document item in the audited project document management system, a task list is generated and assigned to the corresponding responsible persons; The completion status information of each task in the task list is collected, and multi-level early warning information is generated based on the relationship between the task completion time and a preset threshold. Based on the multi-level early warning information, early warning reminders are sent to the responsible persons at the corresponding management level.

[0015] In one embodiment, the process of constructing a multi-level document management system directory according to management hierarchy, with each management level customizing and extending the directory of the previous level to form a document management system corresponding to each management level, and then reviewing the document management system to output the reviewed project document management system, includes: Maintain the enterprise-level document management system catalog in accordance with the engineering general contracting management specifications, and distribute the enterprise-level document management system catalog to each professional unit from top to bottom; Based on the enterprise-level document management system catalog received, each professional unit will customize and expand it according to the industry and professional field involved, forming a professional unit-level document management system catalog, and then distribute it to the project departments under its jurisdiction. Based on the professional unit-level document management system catalog received, each project department shall compile a project department-level document management system catalog in accordance with the actual management needs of the project, and specify the responsible person and completion time for each document item; The completed project department-level document management system catalog is submitted to the corresponding professional unit for review. After the review is approved, the reviewed project document management system is output, and the task list is generated accordingly.

[0016] The first aspect of this application provides an engineering project management system based on a general contracting document management system. Through a document system management module, a multi-level document management system directory is constructed, transmitting management standards to each management level in the form of a document system, ensuring the standardization and consistency of management requirements. A task management module automatically generates task lists based on time nodes and update cycles in the document management system and assigns them to corresponding responsible persons, avoiding the inefficient mode of manually creating and following up on tasks item by item. An early warning management module monitors the completion status of each task and generates multi-level early warning information, enabling proactive perception and timely handling of project execution risks. The three modules form a closed data transmission chain through three data objects: the audited project document management system, completion status information, and multi-level early warning information. This organically connects the transmission of management standards, automatic task scheduling, and proactive risk early warning, effectively improving the efficiency and precision of engineering general contracting project management.

[0017] It is understandable that the beneficial effects of the second aspect mentioned above can be found in the relevant descriptions in the first aspect mentioned above, and will not be repeated here. Attached Figure Description

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

[0019] Figure 1 This is a schematic diagram of the overall structure of an engineering project management system based on a general contracting document management system provided in an embodiment of this application; Figure 2 This is a schematic diagram of the five-layer architecture deployment of an engineering project management system provided in one embodiment of this application; Figure 3 This is a schematic diagram of the directory structure of a multi-level file management system provided in an embodiment of this application; Figure 4 This is a schematic diagram of a three-tier management system provided in an embodiment of this application; Figure 5 This is a schematic diagram of the overall business architecture provided in one embodiment of this application; Figure 6 This is a schematic diagram of the general contracting document management business process provided in an embodiment of this application; Figure 7 This is a schematic diagram of the internal structure of an enterprise-level document management system directory provided in an embodiment of this application; Figure 8 This is a schematic diagram of the template library management module structure provided in one embodiment of this application; Figure 9 This is a schematic diagram of the workflow of the document generation and collection module provided in one embodiment of this application; Figure 10 This is a schematic diagram of the workflow of the early warning management module provided in one embodiment of this application; Figure 11 This is a schematic diagram of the intelligent archiving module structure provided in one embodiment of this application; Figure 12 This is a schematic diagram of a system multi-terminal architecture provided in an embodiment of this application; Figure 13 This is a schematic diagram of the development architecture design provided in one embodiment of this application; Figure 14 This is a schematic diagram of the deployment architecture provided in one embodiment of this application; Figure 15 This is a schematic diagram of a project management method based on a general contracting document management system provided in an embodiment of this application. Detailed Implementation

[0020] In the following description, specific details such as particular system architectures and techniques are set forth for illustrative purposes and not for limitation, in order to provide a thorough understanding of the embodiments of this application. However, those skilled in the art will understand that this application may also be implemented in other embodiments without these specific details. In other instances, detailed descriptions of well-known systems, apparatuses, circuits, and methods have been omitted so as not to obscure the description of this application with unnecessary detail.

[0021] It should be understood that, when used in this application specification and the appended claims, the term "comprising" indicates the presence of the described features, integrals, steps, operations, elements and / or components, but does not exclude the presence or addition of one or more other features, integrals, steps, operations, elements, components and / or a collection thereof.

[0022] It should also be understood that the term “and / or” as used in this application specification and the appended claims means any combination of one or more of the associated listed items and all possible combinations, and includes such combinations.

[0023] Furthermore, in the description of this application and the appended claims, the terms "first," "second," "third," etc., are used only to distinguish descriptions and should not be construed as indicating or implying relative importance.

[0024] References to "one embodiment" or "some embodiments" as described in this specification mean that one or more embodiments of this application include a specific feature, structure, or characteristic described in connection with that embodiment. Therefore, the phrases "in one embodiment," "in some embodiments," "in other embodiments," "in still other embodiments," etc., appearing in different parts of this specification do not necessarily refer to the same embodiment, but rather mean "one or more, but not all, embodiments," unless otherwise specifically emphasized. The terms "comprising," "including," "having," and variations thereof mean "including but not limited to," unless otherwise specifically emphasized.

[0025] like Figure 1 As shown in the embodiment of this application, an engineering project management system based on a general contracting document management system is provided, comprising: The document system management module 10 is used to build a multi-level document management system directory according to the management level. Each management level can be customized and extended based on the document management system directory of the previous level to form a document management system corresponding to each management level, and output the approved project document management system. The task management module 20 is connected to the file system management module 10. It is used to receive the approved project file management system, automatically generate a task list and assign it to the corresponding responsible person according to the preset time nodes and update cycles of each file item, and summarize the completion status information of each task. The early warning management module 30 is connected to the task management module 20. It is used to receive the completion status information, generate multi-level early warning information according to the relationship between the task completion time and the preset threshold, and send the multi-level early warning information to the person in charge of the corresponding management level.

[0026] The document management module 10 constructs a complete document management system catalog for EPC (Engineering, Procurement, and Construction) projects. This catalog refers to the structure formed by classifying and arranging all document deliverables that should be produced during project management according to management categories, based on EPC management standards. The management hierarchy refers to the vertical hierarchical relationship in the EPC project's organizational structure, typically including three levels in this solution: the enterprise level, the professional unit level, and the project department level. Custom expansion refers to each management level adding, adjusting, or refining document items in the catalog structure based on its industry characteristics, professional field, or actual project needs after receiving the standard document management system catalog from the superior level. The approved project document management system refers to the project document management system catalog that has been reviewed and confirmed by the superior management level; this data object is the core output transmitted from the document management module 10 to the task management module 20.

[0027] After receiving the approved project document management system, the task management module 20 automatically generates a corresponding task list based on the preset time nodes and update cycles for each document item in the system. The preset time nodes refer to the completion dates or phased deadlines set for each document item during the document management system's development. The update cycle refers to the update frequency set for certain document items that require periodic updates, such as monthly reports which are updated monthly. The task management module 20 automatically creates tasks based on these time parameters and assigns them to the designated responsible parties within the document management system. Simultaneously, the task management module 20 continuously summarizes the completion status information for each task. This completion status information refers to the current execution progress of each task, including whether the task has been completed and whether the completion time is within the preset timeframe. This status information is the core data that the task management module 20 transmits to the early warning management module 30.

[0028] After receiving the completion status information summarized by the task management module 20, the early warning management module 30 compares the actual completion time of each task with a preset threshold. The preset threshold refers to a pre-defined time threshold used to determine whether a task is progressing normally, is at risk, or is lagging behind. Based on the comparison results, the early warning management module 30 generates multi-level early warning information and sends it to the responsible persons at the corresponding management levels, enabling managers at different levels to be promptly informed of any abnormal situations in the tasks within their jurisdiction.

[0029] like Figure 2 As shown, this system adopts a five-layer architecture at the technical level, consisting of the infrastructure layer, data resource layer, support platform layer, business application layer, and comprehensive application layer, from bottom to top. The infrastructure layer provides computing, storage, and network security resources. The data resource layer stores basic engineering data, business management data, geospatial data, and system management data. The support platform layer provides common capabilities such as access control, authentication services, data resource services, process services, reporting services, message engine, map services, BIM collaboration services, thematic layer services, and data visualization services. The business application layer carries business functions such as project document management, design management, progress management, quality management, security management, resource management, meeting minutes management, project pre-management, information management, system management, and configuration management. The comprehensive application layer provides information services to higher-level management units, engineering construction units, and participating units through three forms: a single GIS map, a large-screen integrated display, and mobile applications. Network security and protection systems are configured on both sides to ensure the overall security and stability of the system.

[0030] The system in this embodiment uses a document management system as its core link, unifying business activities scattered across different management stages onto a structured directory tree. Through data chain transmission between the document management module 10, task management module 20, and early warning management module 30, it achieves organic integration of management standard transmission, automatic task scheduling, and proactive risk early warning. Compared to traditional engineering project management systems that are horizontally divided by functional modules, this solution uses document deliverables as the smallest unit of management, ensuring that each management action has clear output requirements, time constraints, and accountability. This effectively solves the problems of deviation and omission in the process of transmitting management requirements layer by layer, significantly improving the level of refined management in EPC projects.

[0031] In one embodiment, such as Figure 3 As shown, the multi-level document management system directory includes an enterprise-level document management system directory 100, a professional unit-level document management system directory 200, and a project department-level document management system directory 300.

[0032] The aforementioned enterprise-level document management system catalog 100 is maintained by the enterprise's competent department in accordance with the engineering general contracting management specifications and distributed from top to bottom to various professional units.

[0033] The professional unit-level document management system catalog 200 is formed by customizing and expanding the received enterprise-level document management system catalog 100 in combination with the relevant industry and professional field, and then distributed to the project departments under its jurisdiction.

[0034] The project department-level document management system catalog 300 is compiled based on the received professional unit-level document management system catalog 200, taking into account the actual management needs of the project. It clarifies the responsible person and completion time for each document item, and submits it to the corresponding professional unit for review after completion. After the review is approved, the document system management module 10 outputs the project department-level document management system catalog 300 as the reviewed project document management system, and the task management module 20 automatically generates the task list accordingly.

[0035] like Figure 4 As shown, in a typical application scenario of this solution, the enterprise level is the design company, which oversees multiple specialized units such as the Water Conservancy Planning Institute, the Hub Institute, the Engineering Construction Consulting Company, and the New Energy Company. Each specialized unit further comprises several project departments. This tree-like organizational structure naturally corresponds to the three-tier management system in this solution.

[0036] like Figure 5As shown, in actual operation, the business architecture of the three-tier management system is divided into three business lines: indicator template management, document management, and statistical analysis. On the indicator template management line, the design company constructs a general contracting document standard system, carrying assessment indicator requirements, and automatically distributes it to each specialized company in the form of 81 basic management actions and 175 document items. The specialized companies then add custom items to form their own general contracting document standard system, which is then automatically distributed to each project department, ultimately creating a document standard folder at the project department level. On the document management line, project departments upload documents according to the update cycle, and the upload action is dynamically updated to the specialized company level and the design company level. On the statistical analysis line, the company level can perform multi-project statistical analysis, viewing detailed information about each specialized company and each project through multi-level penetration and data drill-down to meet the management requirements of the design company.

[0037] In this embodiment, the enterprise-level document management system directory 100 reflects the enterprise's top-level design and bottom-line requirements for EPC project management. Based on national standards and industry norms such as the "Code for Management of EPC Projects," and considering the industry sectors the enterprise operates in, the enterprise's competent department maintains a standardized directory structure covering multiple management categories. Once published, this directory structure is automatically distributed to all professional units through the system, ensuring that each professional unit receives a unified management baseline.

[0038] The Professional Unit-Level Document Management System Catalog 200 reflects the industry-specific implementation of enterprise management requirements by various professional units. Different professional units operate in different industries; for example, the Water Resources Planning Institute focuses on water conservancy and hydropower projects, while the New Energy Company focuses on new energy projects. The standards, specifications, technical requirements, and compliance conditions involved also differ. Therefore, after receiving the Enterprise-Level Document Management System Catalog 100, each professional unit, without compromising its basic requirements, adds industry-specific document items or adjusts the granularity of management requirements according to its own industry characteristics to form its own document management system catalog, which is then distributed to its subordinate project departments.

[0039] The project-level document management system catalog 300 reflects personalized adaptation and accountability at the project level. After receiving the professional unit-level document management system catalog 200, the project team compiles it based on the project's construction scale, contract requirements, regional characteristics, and other actual management needs, clearly defining the responsible person and completion time for each document item. Upon completion, the project manager submits the project-level document management system catalog 300 to the corresponding professional unit for approval by the unit's chief engineer or relevant supervisor. After approval, the system outputs the catalog as the approved project document management system. The task management module 20 then automatically generates a task list based on the time parameters of each document item in the system and assigns the tasks to the responsible persons. This mechanism ensures a closed-loop process from the establishment to the activation of the document management system.

[0040] like Figure 6 As shown, in the general contracting document management business process, the design company level is responsible for indicator template management, including document directory maintenance and file template entry; the professional unit level is responsible for project document content review, and after approval, it is automatically synchronized to multi-project reminders and multi-project statistical analysis; the project level is responsible for project information entry, project document management system compilation, document directory frequency and responsible person maintenance, custom document directory compilation, file upload cycle determination, and document upload, etc. When the file upload cycle determination result is overdue, the system triggers a color alarm for the file management item; if it is not overdue, it is marked as the file has been uploaded. The warning information is sent to each level through a message reminder mechanism, and reminder and multi-level query functions are supported.

[0041] The three-tier management system in this application implements a two-way flow mechanism that transmits management standards from top to bottom and approves project results from bottom to top, ensuring uniformity in management requirements while preserving individualized space at each level. The design that triggers automatic task generation upon approval avoids the tedious manual creation of tasks, significantly improving efficiency across the entire chain from system setup to task execution.

[0042] In one embodiment, such as Figure 7 As shown, the enterprise-level document management system directory 100 includes multiple management categories, and each management category has several document items. Each document item includes preset basic management actions, which are standardized performance indicators that each management level should follow when performing project management.

[0043] The document system management module 10 is also configured to: synchronously configure corresponding template files for each document item, and the template files are distributed to each professional unit along with the enterprise-level document management system directory 100.

[0044] In this embodiment, the management category refers to the broad classification of document items according to the business segments of EPC project management, such as safety management, quality management, schedule management, and contract management. In a typical scenario of this solution, the enterprise-level document management system directory 100 contains 14 management categories and 175 document items, comprehensively covering all business segments of EPC project management. Basic management actions refer to the standardized management operations extracted from the document items that must be completed by each management level during project execution; these are also the rigid assessment requirements for EPC project management by the enterprise. In this solution, the enterprise has identified 81 basic management actions from the 175 document items as assessment indicators for each professional unit and project department. These basic management actions represent the bottom-line requirements of enterprise management; regardless of the industry sector or professional unit undertaking the project, these actions must be executed effectively.

[0045] Template files refer to pre-prepared standardized document samples for management personnel to refer to. When maintaining the enterprise-level document management system catalog 100, the document system management module 10 synchronously configures corresponding template files for each document item. These template files are distributed to various professional units along with the catalog, enabling front-line project managers to have clear guidelines and evidence when preparing document deliverables, lowering the professional threshold for document preparation, and ensuring the quality and consistency of the output.

[0046] This application embodiment organizes project management content in a refined manner through a hierarchical structure of management categories and document items, establishes a rigid assessment baseline through basic management actions, and provides standardized references for deliverable preparation through template documents. Together, these three elements constitute the internal structure of an enterprise-level document management system, providing a solid foundational framework for subsequent custom expansion at each management level and project execution.

[0047] In one embodiment, such as Figure 8 As shown, the system also includes a template library management module 40.

[0048] The template library management module 40 is connected to the document system management module 10 and is used to receive document result templates uploaded by each management level and perform standardized management to form a document system template library.

[0049] The template library management module 40 is further configured to: respond to the template selection request of the administrator, match and output the corresponding template from the document system template library to assist in the compilation of the results of each document item in the document management system; the templates in the document system template library support custom adjustment to adapt to the scale, complexity and industry characteristics of different projects.

[0050] In this embodiment, the template library management module 40 adopts a service-oriented design pattern, providing managers at all management levels with functions for uploading, managing, and retrieving document outcome templates. Managers at all management levels can upload excellent document outcome templates that have been proven in practice to the system, where the template library management module 40 will standardize them and incorporate them into the document system template library. The document system template library refers to a standardized template resource pool that is uniformly managed by the system and open to all management levels.

[0051] When an administrator needs to prepare a deliverable for a specific document item, they can send a template selection request to the template library management module 40. The template library management module 40 matches the document item based on its management category, industry, and project characteristics, and outputs the most suitable template to the administrator to assist in completing the deliverable preparation. The connection between the template library management module 40 and the document system management module 10 ensures that the scope of template selection remains consistent with the structure of the current document management system.

[0052] Furthermore, the templates in the document system template library support customization. Different projects vary in size, complexity, and industry characteristics, allowing managers to personalize selected templates based on the specific project needs. This ensures that the final deliverables meet standardized requirements while reflecting the project's unique features. Even those lacking professional management experience can quickly get started using the mature templates in the library, completing high-quality document deliverables according to template requirements. This lowers the professional barrier to document management and increases overall participation.

[0053] The template library management module 40 in this embodiment of the application lowers the professional threshold for document compilation by establishing a unified template resource pool and a standardized selection and matching mechanism; on the other hand, it ensures the flexibility and adaptability of templates through the ability to customize and adjust them, thus achieving a balance between standardization and personalization.

[0054] In one embodiment, such as Figure 9 As shown, the system also includes a document generation and collection module 50.

[0055] The document generation and collection module 50 is connected to the document system management module 10. It is used to automatically convert the information filled in the business form into standardized result documents according to the preset document template, and automatically collect the result documents to the corresponding positions in the multi-level document management system directory according to the document collection rules in the document management system.

[0056] The information to be filled in the business form includes at least one of the following: project information, contract information, and security management information.

[0057] In this embodiment, the document generation and aggregation module 50 addresses the conversion between business data and deliverables during project management. In traditional management models, after project managers fill out business forms, they still need to manually organize the form content into deliverables that meet archiving requirements and store the files in the correct directory location. This process is time-consuming, labor-intensive, and prone to errors.

[0058] The document generation and aggregation module 50 achieves two automated operations through preset document templates and aggregation rules in the file management system. Automatic conversion refers to the system automatically filling in the preset document templates with structured data filled in by managers in business forms, such as project names, contract numbers, and safety inspection conclusions, generating standardized deliverables with uniform format and content. Automatic aggregation refers to the system automatically storing the generated deliverables in the corresponding locations within the multi-level file management system directory according to pre-configured document aggregation rules. For example, it aggregates deliverables generated from safety management business forms into the corresponding file items under the safety management directory.

[0059] The connection between the document generation and collection module 50 and the document system management module 10 ensures that the collection rules are always synchronized with the structure of the document management system directory. When the document management system directory is adjusted, the collection rules are also updated accordingly, avoiding incorrect collection positions of the resulting documents.

[0060] This application embodiment utilizes the automation capabilities of the document generation and collection module 50 to seamlessly connect the two stages of business form filling and output document production, reducing repetitive work for managers in the document preparation and collection stages, while ensuring the uniformity of the output document format and the accuracy of collection, thereby improving the efficiency and standardization of project document management.

[0061] In one embodiment, such as Figure 10 As shown, the early warning management module 30 generates the multi-level early warning information in the following manner: The execution status of each task is classified and identified according to the preset warning level. The warning level includes at least normal status, risk status and lagging status. The normal status indicates that the task progress is in line with expectations or has been completed on time. The risk status indicates that the task is nearing the completion date and there is a potential risk of delay. The lagging status indicates that the task progress has seriously deviated from the plan.

[0062] The early warning management module 30 is further configured to send an early warning reminder to the person in charge of the corresponding management level when the execution status of the task changes from the normal state to the risk state or the lagging state; the person in charge of the corresponding management level includes at least one of the heads of enterprise functional departments, heads of professional units, and heads of project departments.

[0063] In this embodiment, the core function of the early warning management module 30 is to perform real-time monitoring and tiered early warning of the execution status of each task in the file management system. The early warning level refers to a set of predefined task status levels used to intuitively identify the health status of a task.

[0064] In a typical application scenario of this solution, the warning level is visually presented using color: the normal state is marked in green, indicating that the task is progressing normally or has been completed according to the time nodes set in the document management system; the risk state is marked in yellow, indicating that the actual progress of the task is close to the deadline, and delays may occur if measures are not taken in time; the lagging state is marked in red, indicating that the task has exceeded the preset completion deadline, the progress has seriously deviated from the plan, and immediate intervention is required.

[0065] like Figure 6 In the business process, when the system determines the file upload cycle, tasks that are deemed overdue will trigger a color-coded alert in the file management section. Simultaneously, the system will send notifications to the project management team, professional unit management teams, and functional departments. Upon receiving the alert, responsible personnel at each management level can use the system to expedite tasks and perform multi-level queries, quickly understanding the details of the issue and coordinating its resolution.

[0066] The multi-level, penetrating early warning mechanism of the early warning management module 30 ensures that abnormal task information does not remain at the project department level. When a project department's task experiences a delay warning, not only is the project department's management notified, but the management of professional units and functional departments of the enterprise are also simultaneously informed of the abnormal situation. This penetrating early warning path allows each management level to intervene promptly according to their respective management authority and responsibilities, avoiding the drawbacks of the traditional management model where "problems are reported layer by layer, and handling is delayed layer by layer." The system automatically summarizes the completion status of results each month and generates a monthly report, which is regularly submitted to professional units so that management can keep abreast of project progress and make management decisions.

[0067] This application embodiment transforms the identification of project risks from a passive response to an active perception by setting preset warning levels and a multi-level penetrating warning mechanism. This enables management to obtain warning information and take action when the risks are still under control, effectively reducing the probability of project delays and cost overruns.

[0068] In one embodiment, such as Figure 11 As shown, the system also includes an intelligent archiving module 60.

[0069] The intelligent archiving module 60 is connected to the document system management module 10 and is used to receive the output documents in the document management system through an interface with the external document management system, and automatically perform classification, volume assembly, numbering and archiving operations on the output documents to realize data connection between the document management system and the external document management system.

[0070] In this embodiment, the intelligent archiving module 60 addresses the issue of transferring project process deliverables from the management system to the archiving system. In traditional management models, after project completion, a dedicated person is required to classify, organize, compile, and number the large number of documents accumulated during the project. This process is labor-intensive, time-consuming, and prone to errors in classification or omissions in numbering.

[0071] The intelligent archiving module 60, through its interface with an external records management system, achieves four key automated operations. Classification refers to the system automatically categorizing output documents according to the classification structure of the document management system's catalog. File assembly refers to the system logically combining related documents within the same management category according to records management standards to form complete archive volumes. Numbering refers to the system automatically generating unique archive numbers for each archive volume and document according to archive numbering rules. Archiving refers to the system pushing the classified, assembled, and numbered documents to the external records management system for formal archiving and preservation.

[0072] The connection between the intelligent archiving module 60 and the file system management module 10 ensures that the data source for archiving is consistent with the file management system. The category structure of the file management system directory itself is the natural basis for archive classification. Therefore, the intelligent archiving module 60 can directly use the structural information of the file management system directory as the rules for classification and volume assembly, without the need to configure archiving rules separately, reducing manual intervention and lowering the probability of configuration errors.

[0073] This application embodiment utilizes the automation capabilities of the intelligent archiving module 60 to seamlessly connect the accumulation of project process results in the management phase with the storage in the archiving phase. This reduces the manual workload in the archiving process while ensuring the integrity and accuracy of the archiving results.

[0074] In one embodiment, such as Figure 12 As shown, the system adopts a front-end and back-end separation architecture and supports concurrent access of at least one application terminal through reverse proxy and load balancing; the application terminals include web terminal, mobile terminal and large screen display terminal.

[0075] like Figure 13As shown, the development architecture of this system is divided into five technical layers: front-end presentation layer, API gateway layer, application service layer, basic capability layer, and storage layer. The front-end presentation layer consists of two branches: a web client and an app client. The web client is based on the VueJS framework and integrates front-end technology components such as the Echarts chart library, AntDesign component library, H5 pages, Ajax communication, and PDF file preview. The app client supports both Android and iOS platforms and achieves cross-platform capabilities through the Cordova framework. The map display function is built based on two map engines: OpenLayers and Cesium. The API gateway layer uses Nginx as a reverse proxy server to provide a unified API service entry point. The application service layer deploys various back-end application services, including unified user service, reporting service, data service, SMS service, monitoring service, system management, workflow service, map service, and file service. The foundational capability layer is based on the Spring Boot framework, integrating fundamental components such as MyBatis-plus data persistence, Druid database connection pool, Activiti workflow engine, JWT authentication mechanism, Ureport reporting engine, and Shiro security framework. It also includes independent workflow and video platforms. The storage layer uses MySQL relational database and Redis caching database for structured data storage, a file server for unstructured file data storage, and a dedicated map server to provide geospatial data services.

[0076] like Figure 14 As shown in the deployment architecture, users access the system via either a web client or a WeChat mini-program. Requests are processed uniformly by the server, which then calls MySQL database services, Redis caching services, file services, and workflow services to complete business logic processing. The mobile application employs a hybrid development model combining WXML and native applications, utilizing the WeChat mini-program mobile development framework. WXML describes the page structure, WXS is the scripting language for WeChat mini-programs, and WXSS describes the page style. Components are the basic building blocks of the view and provide standard API bindings to access the native functions of each device. Since mobile applications frequently interact with mobile device sensors, plugins are used to extend and adapt capabilities based on the standard APIs provided by WeChat mini-programs.

[0077] In this embodiment, the front-end and back-end separation architecture ensures that the front-end display logic and back-end business logic are independent of each other. The back-end service can provide a unified interface service for the web, mobile, and large-screen display terminals simultaneously, and the interface development of each terminal does not interfere with each other. Reverse proxy means that client requests first reach the Nginx server, which then forwards them to the corresponding back-end service instance based on the request content. The client does not need to directly access the back-end server's address. Load balancing means that when multiple back-end service instances are running simultaneously, Nginx distributes requests to different instances according to a certain allocation strategy, avoiding performance bottlenecks caused by a single instance handling too many requests.

[0078] In terms of storage technology, storage is mainly divided into two categories: structured data storage and unstructured data storage. Structured data storage mainly includes the storage of basic data, business data, management data, and spatial vector data; unstructured storage mainly includes the storage of data such as files, images, and videos.

[0079] This application embodiment, through a front-end and back-end separation architecture and reverse proxy and load balancing technology, enables the system to support concurrent access from multiple application terminals simultaneously. It adapts to the actual needs of management personnel distributed in different workplaces such as offices, construction sites, and command centers in engineering project management scenarios, and ensures the stable operation of the system in high-concurrency scenarios.

[0080] In one embodiment, such as Figure 15 As shown, a second aspect of this application provides a project management method based on a general contracting document management system, comprising the following steps: S1. Construct a multi-level document management system directory according to the management level. Each management level makes custom extensions based on the document management system directory of the previous level to form a document management system corresponding to each management level. The document management system is then reviewed and the reviewed project document management system is output.

[0081] S2, based on the preset time nodes and update cycles of each document item in the audited project document management system, automatically generate a task list and assign it to the corresponding responsible person.

[0082] S3, collect the completion status information of each task in the task list, and generate multi-level early warning information based on the relationship between the task completion time and the preset threshold.

[0083] S4. Based on the multi-level early warning information, send early warning reminders to the responsible persons at the corresponding management level.

[0084] In this embodiment, steps S1 to S4 constitute the main flow of the method. The four steps are connected by four data objects: the audited project file management system, the task list, the completion status information, and the multi-level early warning information. These correspond to the functions of the file system management module 10, the task management module 20, and the early warning management module 30 in the system embodiment.

[0085] In step S1, the system first constructs a multi-level document management system directory. This hierarchical construction means that each management level does not independently create its own document management system from scratch, but rather incrementally expands upon the document management system directory received from the previous level. This hierarchical construction method ensures that the document management system of lower-level management levels always includes the management requirements of higher-level management levels, preventing any omissions of standards. After the constructed document management system is reviewed, it is output as the reviewed project document management system; this data object is the output passed from step S1 to step S2.

[0086] In step S2, the system automatically generates a task list and assigns it to the responsible personnel based on the preset time parameters of each document item in the audited project document management system. The significance of this step is to transform the document management system from a static standard into dynamic tasks, so that management requirements can be specifically executed and tracked in the form of tasks.

[0087] In step S3, the system continuously collects the completion status information of each task and compares the actual completion progress of each task with a preset threshold. No warning is triggered when a task is progressing normally; different levels of warning information are generated when a task is nearing its deadline or has exceeded its deadline.

[0088] In step S4, the system sends the generated multi-level early warning information to the responsible persons at the corresponding management levels. This step enables targeted distribution of early warning information, ensuring that responsible persons at each management level only receive early warning content relevant to their management authority, thus avoiding information overload.

[0089] The management method of this application embodiment achieves full-link coverage from management standard construction to task execution monitoring through a four-step closed-loop process from S1 to S4. The data transmission direction between each step is clear and logically progressive, ensuring the continuity and traceability of the management process.

[0090] In one embodiment, step S1, which involves constructing a multi-level file management system directory according to management hierarchy, specifically includes: S1.1 Maintain the enterprise-level document management system catalog in accordance with the engineering general contracting management specifications, and distribute the enterprise-level document management system catalog to each professional unit from top to bottom.

[0091] S1.2 Based on the enterprise-level document management system catalog received, each professional unit shall customize and expand it according to the industry and professional field involved, form a professional unit-level document management system catalog, and distribute it to the project departments under its jurisdiction.

[0092] S1.3 Based on the professional unit-level document management system catalog received, each project department shall compile a project department-level document management system catalog in accordance with the actual management needs of the project, and specify the responsible person and completion time for each document item.

[0093] S1.4 Submit the completed project department-level document management system catalog to the corresponding professional unit for review. After the review is approved, the reviewed project document management system is output, and the task list is automatically generated accordingly.

[0094] In this embodiment, steps S1.1 to S1.4 expand the directory construction process of step S1 into four specific sub-steps from the enterprise level to the project department level.

[0095] In step S1.1, the enterprise's competent department is the top-level designer of the multi-level document management system. Based on engineering general contracting management standards such as the "Construction Project General Contracting Management Standard," the competent department maintains an enterprise-level document management system directory. This directory covers all standardized requirements for the enterprise's general contracting project management. After maintenance, the system distributes this directory from top to bottom to each professional unit, serving as the starting point and baseline for each unit to build its own document management system.

[0096] In step S1.2, after receiving the enterprise-level document management system catalog, each professional unit customizes and expands it according to the specific requirements of its respective industry and professional field, while retaining the enterprise's basic requirements. For example, professional units in the water conservancy and hydropower field may need to add document items related to hydraulic structure safety monitoring, while professional units in the new energy field may need to add document items related to equipment selection and performance testing. The expanded professional unit-level document management system catalog includes both the enterprise-level standardized requirements and the industry characteristics of each professional unit, and is then distributed to the relevant project departments.

[0097] In step S1.3, after receiving the professional unit-level document management system catalog, each project department carries out the final-level compilation work according to the specific circumstances of each project. During this process, the project department assigns specific responsible persons and completion times to each document item in the document management system, transforming the document management system from an abstract standard structure into an executable work arrangement.

[0098] In step S1.4, the completed project-level document management system catalog is submitted to the corresponding professional unit for review. After approval, the system outputs the catalog as the approved project document management system and automatically triggers the task management module to generate a task list. This step ensures that the document management system compiled by the project department is officially used only after being reviewed and confirmed by the professional unit, and that task scheduling is automatically initiated upon approval, achieving a seamless connection from standard confirmation to task execution.

[0099] This application embodiment clearly describes the hierarchical construction path of the multi-level document management system directory from the enterprise level to the project department level through a four-step process from S1.1 to S1.4, as well as the complete closed loop of automatic generation of tasks triggered by review after construction. This process ensures the unified transmission of management standards while reserving sufficient personalization space for each management level, ensuring that the document management system can reflect both the top-level management requirements of the enterprise and the actual management needs of each project.

[0100] In summary, the project management system and methodology based on the general contracting document management system provided in this application, with the document management system as the core link, achieves hierarchical transmission of management standards, automatic scheduling of management tasks, and proactive early warning of project risks through chain-like data transfer between the document system management module, task management module, and early warning management module. The three-tier management system ensures the uniformity and adaptability of management requirements across the enterprise, professional units, and project departments; the template library management module and document generation and collection module reduce the workload of management personnel from the two dimensions of deliverable preparation and document circulation, respectively; the early warning management module enables each management level to promptly learn of abnormal situations during project execution through a multi-level penetrating early warning mechanism; and the intelligent archiving module connects project process deliverables with external document management systems, achieving end-to-end automation from project management to document storage. The entire system adopts a front-end and back-end separation architecture, supporting concurrent access from multiple terminals including web, mobile, and large-screen display terminals, adapting to the actual needs of multiple scenarios and roles in project management.

[0101] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application, and should all be included within the protection scope of this application.

Claims

1. A project management system based on a general contracting document management system, characterized in that, include: The system includes a document management module, a task management module, and an early warning management module. The document system management module is used to build a multi-level document management system directory according to the management level. Each management level can be customized and extended based on the document management system directory of the previous level to form a document management system corresponding to each management level, and output the approved project document management system. The task management module is connected to the file system management module and is used to receive the reviewed project file management system, generate a task list and assign it to the corresponding responsible person according to the preset time nodes and update cycles of each file item, and summarize the completion status information of each task. The early warning management module is connected to the task management module and is used to receive the completion status information, generate multi-level early warning information according to the relationship between the task completion time and the preset threshold, and send the multi-level early warning information to the person in charge of the corresponding management level.

2. The project management system based on the general contracting document management system as described in claim 1, characterized in that, The multi-level document management system catalog includes an enterprise-level document management system catalog, a professional unit-level document management system catalog, and a project department-level document management system catalog. The enterprise-level document management system catalog is maintained by the enterprise's competent department in accordance with the engineering general contracting management specifications and distributed from top to bottom to various professional units; The professional unit-level document management system catalog is formed by customizing and expanding the received enterprise-level document management system catalog, taking into account the relevant industry and professional fields, and then distributed to the project departments under its jurisdiction. The project department-level document management system catalog is compiled based on the received professional unit-level document management system catalog and combined with the actual management needs of the project. It clarifies the responsible person and completion time for each document item and submits it to the corresponding professional unit for review after completion. After the review is approved, the document system management module outputs the project department-level document management system directory as the approved project document management system, and the task management module generates the task list accordingly.

3. The project management system based on the general contracting document management system as described in claim 2, characterized in that, The enterprise-level document management system directory contains multiple management categories, and each management category has several document items; the document items include preset basic management actions, which are standardized performance indicators that each management level should follow when performing project management; The document system management module is also configured to: synchronously configure corresponding template files for each document item, and the template files are distributed to each professional unit along with the enterprise-level document management system directory.

4. The project management system based on the general contracting document management system as described in claim 1, characterized in that, The system also includes a template library management module; The template library management module is connected to the file system management module and is used to receive file output templates uploaded by each management level and perform standardized management to form a file system template library. The template library management module is also configured to: in response to a template selection request from an administrator, match and output a corresponding template from the document system template library to assist in the compilation of results for each document item in the document management system; The templates in the document system template library support customization to adapt to the scale, complexity, and industry characteristics of different projects.

5. The project management system based on the general contracting document management system as described in claim 1, characterized in that, The system also includes a document generation and collection module; The document generation and collection module is connected to the document system management module. It is used to convert the content filled in the business form into standardized result documents according to the preset document template, and to collect the result documents to the corresponding positions in the multi-level document management system directory according to the document collection rules in the document management system. The information to be filled in the business form includes at least one of the following: project information, contract information, and security management information.

6. The project management system based on the general contracting document management system as described in claim 1, characterized in that, The early warning management module generates the multi-level early warning information in the following ways: The execution status of each task is classified and identified according to the preset warning level. The warning level includes at least normal status, risk status and lagging status. The normal status means that the task progress is in line with expectations or has been completed on time. The risk status means that the task is close to the completion date and there is a potential risk of delay. The lagging status means that the task progress has deviated significantly from the plan. The early warning management module is further configured to send an early warning reminder to the person in charge of the corresponding management level when the execution status of a task changes from the normal state to the risk state or the lagging state; the person in charge of the corresponding management level includes at least one of the heads of enterprise functional departments, heads of professional unit management, and heads of project department management.

7. The project management system based on the general contracting document management system as described in claim 1, characterized in that, The system also includes an intelligent archiving module; The intelligent archiving module is connected to the document system management module and is used to receive the output documents in the document management system through an interface with the external document management system, and perform classification, volume assembly, numbering and archiving operations on the output documents to realize data connection between the document management system and the external document management system.

8. The project management system based on the general contracting document management system as described in claim 1, characterized in that, The system adopts a front-end and back-end separation architecture and supports concurrent access of at least one application terminal through reverse proxy and load balancing; the application terminals include web terminal, mobile terminal and large screen display terminal.

9. A project management method based on the project management system as described in any one of claims 1 to 8, characterized in that, include: A multi-level document management system directory is constructed according to the management hierarchy. Each management level makes custom extensions based on the document management system directory of the previous level to form a document management system corresponding to each management level. The document management system is then reviewed and the reviewed project document management system is output. Based on the preset time nodes and update cycles of each document item in the audited project document management system, a task list is generated and assigned to the corresponding responsible persons; The completion status information of each task in the task list is collected, and multi-level early warning information is generated based on the relationship between the task completion time and a preset threshold. Based on the multi-level early warning information, early warning reminders are sent to the responsible persons at the corresponding management level.

10. The project management method as described in claim 9, characterized in that, The document management system directory is constructed hierarchically according to management levels. Each management level expands upon the directory of the previous level to form a corresponding document management system. The document management system is then reviewed, and the reviewed project document management system is output, including: Maintain the enterprise-level document management system catalog in accordance with the engineering general contracting management specifications, and distribute the enterprise-level document management system catalog to each professional unit from top to bottom; Based on the enterprise-level document management system catalog received, each professional unit will customize and expand it according to the industry and professional field involved, forming a professional unit-level document management system catalog, and then distribute it to the project departments under its jurisdiction. Based on the professional unit-level document management system catalog received, each project department shall compile a project department-level document management system catalog in accordance with the actual management needs of the project, and specify the responsible person and completion time for each document item; The completed project department-level document management system catalog is submitted to the corresponding professional unit for review. After the review is approved, the reviewed project document management system is output, and the task list is generated accordingly.

Images