Project management method, device, electronic device and storage medium

By determining the pending projects and nodes of the project category and calculating the project progress, the problem of project requirements being ignored in multi-project management is solved, and better understanding and management of project requirements is achieved.

CN115049369BActive Publication Date: 2025-08-12GUANGDONG POWER GRID CO LTD +1
View PDF 2 Cites 0 Cited by

Patent Information

Application Number
CN202210731006.0
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2022-06-24
Publication Date
2025-08-12
Estimated Expiration
2042-06-24

AI Technical Summary

Technical Problem

The lack of uniformity in the management of multiple projects in the prior art has led to the neglect of the needs of some projects.

Method used

By determining the pending items and nodes associated with the project category, the project progress is calculated based on the node progress, and the information determination module, the node progress determination module, the completed node determination module and the project progress determination module are used for unified management.

Benefits of technology

It realizes unified management of multiple projects, and improves understanding and management efficiency of project requirements.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN115049369B_ABST
    Figure CN115049369B_ABST
Patent Text Reader

Abstract

The present invention discloses a project management method, device, electronic device and storage medium, wherein the method comprises: determining at least one pending project associated with a current project category and at least one pending node associated with the current project category; for each pending project, determining the current pending node progress of the current pending project at the current pending node; determining the completed nodes of the corresponding pending project based on the pending node progress of each pending node; and determining the project progress of the corresponding pending project based on the ratio of the number of completed nodes to the total number of pending nodes. The method solves the problem of lack of good management methods for multiple projects at the same time, resulting in the neglect of project requirements of some projects, and achieves the effect of unified management of multiple projects to better understand the project requirements of each project.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present invention relates to the field of information management technology, and in particular to a project management method, device, electronic equipment and storage medium. Background Art

[0002] With the increasing number of engineering construction projects, the information on various aspects of the construction projects is formed during the specific project construction process and can truly reflect the specific situation of the project construction.

[0003] As the scale of project companies continues to expand, each project company may undertake multiple projects at the same time and need to supervise multiple projects at the same time. However, the current way of supervising each project is usually to supervise a single project, which lacks unified management and may lead to the problem that the project requirements of some projects are ignored.

[0004] In order to facilitate the unified management of multiple project projects, it is necessary to improve the project management method. Summary of the Invention

[0005] The present invention provides a project management method, device, electronic device and storage medium to solve the problem that there is a lack of good management methods for multiple projects at the same time, resulting in the project requirements of some projects being ignored.

[0006] In a first aspect, an embodiment of the present invention provides a project management method, including:

[0007] Determining at least one to-be-processed project associated with a current project category and at least one to-be-processed node associated with the current project category;

[0008] For each pending item, determine the current pending item's progress at the current pending node;

[0009] Determine the completed nodes of the corresponding pending projects based on the pending node progress of each pending node;

[0010] The project progress of the corresponding to-be-processed project is determined based on the ratio of the number of each completed node to the total number of the to-be-processed nodes.

[0011] In a second aspect, an embodiment of the present invention further provides a project management device, comprising:

[0012] an information determination module, configured to determine at least one to-be-processed project associated with a current project category, and at least one to-be-processed node associated with the current project category;

[0013] A node progress determination module is used to determine the current to-be-processed node progress of the current to-be-processed project at the current to-be-processed node for each to-be-processed project;

[0014] A completed node determination module is used to determine the completed nodes of the corresponding pending items according to the pending node progress of each pending node;

[0015] The project progress determination module is used to determine the project progress of the corresponding pending project based on the ratio of the number of each completed node to the total number of the pending nodes.

[0016] In a third aspect, an embodiment of the present invention further provides an electronic device, including:

[0017] at least one processor; and

[0018] a memory communicatively connected to the at least one processor; wherein,

[0019] The memory stores a computer program that can be executed by the at least one processor. The computer program is executed by the at least one processor so that the at least one processor can execute the project management method described in any embodiment of the present invention.

[0020] In a fourth aspect, an embodiment of the present invention further provides a computer-readable storage medium, wherein the computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the project management method described in any embodiment of the present invention when executed.

[0021] The technical solution of this embodiment determines at least one pending project associated with the current project category and at least one pending node associated with the current project category, determines the pending project corresponding to the current project category based on the project information table, and determines the pending node corresponding to the current project category based on the node information table. For each pending project, the current pending node progress of the current pending project at the current pending node is determined, and according to the project requirement table of the current pending node, the uploaded document information of the current pending project and whether there are any unuploaded documents are detected, so as to determine the current pending node progress based on the ratio of the number of documents to be used of the uploaded documents of the pending node to the total number of documents in the project requirement table. According to the pending node progress of each pending node, the completed node of the corresponding pending project is determined. If all the project documents associated with the current pending node have been uploaded, the current pending node is determined to be a completed node. Based on the ratio of the number of each completed node and the total number of the pending nodes, the project progress of the corresponding pending project is determined, so as to facilitate the relevant users to manage the pending projects according to the project progress of each pending project. It solves the problem of lack of good management methods for multiple projects at the same time, which leads to the neglect of project requirements of some projects, and achieves the effect of unified management of multiple projects to better understand the project requirements of each project.

[0022] It should be understood that the content described in this section is not intended to identify the key or important features of the embodiments of the present invention, nor is it intended to limit the scope of the present invention. Other features of the present invention will become readily understood through the following description. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] In order to more clearly illustrate the technical solutions in the embodiments of the present invention, the following briefly introduces the drawings required for use in the description of the embodiments. Obviously, the drawings described below are only some embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on these drawings without creative work.

[0024] Figure 1 This is a flowchart of a project management method provided according to the first embodiment of the present invention;

[0025] Figure 2 This is a flowchart of a project management method provided according to the second embodiment of the present invention;

[0026] Figure 3 This is a schematic diagram of the structure of a project management device provided according to the third embodiment of the present invention;

[0027] Figure 4 is a schematic structural diagram of an electronic device for implementing the project management method according to an embodiment of the present invention; DETAILED DESCRIPTION

[0028] In order to enable those skilled in the art to better understand the solutions of the present invention, the technical solutions in the embodiments of the present invention will be clearly and completely described below in conjunction with the drawings in the embodiments of the present invention. Obviously, the embodiments described are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without making creative efforts should fall within the scope of protection of the present invention.

[0029] It should be noted that the terms "first," "second," and the like in the description and claims of the present invention and the accompanying drawings are used to distinguish similar objects and are not necessarily used to describe a specific order or precedence. It should be understood that the terms used in this manner are interchangeable where appropriate, such that the embodiments of the present invention described herein can be practiced in an order other than that illustrated or described herein.

[0030] Example 1

[0031] Figure 1 A flowchart of a project management method is provided for the first embodiment of the present invention. This embodiment is applicable to the situation of unified management of multiple projects. The method can be executed by a project management device. The project management device can be implemented in the form of hardware and / or software. The project management device can be configured in a computing device that can execute the project management method.

[0032] like Figure 1 As shown, the method includes:

[0033] S110: Determine at least one to-be-processed project associated with a current project category, and at least one to-be-processed node associated with the current project category.

[0034] As the number of construction projects increases, to facilitate project management, it is necessary to roughly categorize each project based on characteristics such as business attributes or business execution nodes. For example, if multiple projects correspond to the same business execution node and the relevant documents required by each business execution node are consistent, these projects can be grouped into one project category. This allows subsequent project management to simply open a specific business execution node to view the execution status of each project under that business execution node. It is understood that when determining project categories based on project attributes or business execution nodes, multiple project categories can be obtained. When a user needs to view projects within a certain project category, they can click the corresponding project category.

[0035] The current project category can be understood as the project category that the user is currently viewing or about to view. The pending project can be understood as a business project belonging to the current project category. The pending node can be understood as a business execution node that matches the current project category.

[0036] It should be noted that there are usually multiple pending nodes associated with each project category. For example, the number of pending nodes associated with the current project category can be 5. The business documents required for different pending nodes may be different. When the business process flows to pending node 1, only when the business documents required by pending node 1 have been uploaded, the business process can continue to flow to pending node 2, and so on.

[0037] Specifically, the project category that the user needs to view or is viewing is taken as the current project category. When it is detected that the current project category is triggered, at least one pending project associated with the current project category is retrieved. At the same time, based on the pre-set business execution nodes associated with each project category, at least one pending node associated with the current project category is determined.

[0038] Optionally, determining at least one pending project associated with the current project category, and at least one pending node associated with the current project category, includes: when it is detected that the target control corresponding to the current project category is triggered, retrieving the project information table and node information table corresponding to the current project category; based on the project information table, determining at least one pending project corresponding to the current project category; and based on the node information table, determining at least one pending node corresponding to the current pending project.

[0039] Taking selecting the current project category through the project management system as an example, a control for selecting the project category can be set on the display interface of the project management system, such as a selection control. When the control is triggered, a corresponding drop-down pop-up window can be displayed so that the user can select the corresponding project category in the area as the current project category.

[0040] The target control can be understood as the control corresponding to the current project category. The project information table can be understood as an information table for storing pending projects associated with the current project category, including at least one pending project associated with the current project category. The node information table can be understood as an information table for recording pending nodes corresponding to the current project category, including at least one pending node associated with the current project category.

[0041] Specifically, when it is detected that the target control is triggered, the project information table and the node information table corresponding to the current project category are called to determine the pending project corresponding to the current project category based on the project information table. At the same time, at least one pending node associated with the current project category is determined based on the node information table.

[0042] S120 : For each pending item, determine the current pending node progress of the current pending item at the current pending node.

[0043] The current project category may include one or more pending projects, and any pending project may be used as the current pending project. For example, the pending project that the user currently needs to view may be used as the current pending project. Each pending node associated with the corresponding current project category may be used as the current pending node. For example, the pending node that the user is currently viewing may be used as the current pending node. The current pending node progress may be understood as the project progress associated with the current pending project at the current pending node.

[0044] For example, if the currently pending project requires uploading five project documents at the currently pending node, and if the number of project documents uploaded at the current moment is five, then the currently pending project's progress at the currently pending node can be determined to be 100%. If the number of project documents uploaded at the current moment is two, then the currently pending project's progress at the currently pending node can be determined to be 40%.

[0045] Optionally, determining the current node progress of the current pending project at the current pending node includes: obtaining a project requirement table corresponding to the current pending node; based on the project requirement table, detecting the document name of the uploaded document of the current pending node to obtain the uploaded document information corresponding to the current pending node; based on the uploaded document information, determining the current node progress of the current pending node.

[0046] The project requirements table can be understood as an information table used to record the project documents that need to be uploaded for the current node to be processed. The project requirements table includes the project names corresponding to the project documents associated with the current node to be processed. The uploaded document information can be understood as information generated based on the uploaded documents of the current node to be processed, such as the file name information of each uploaded document.

[0047] Specifically, based on the project requirements table of the current pending node, the project documents required to be uploaded for the current pending node can be determined. In order to detect the completion status of the current pending project at the current pending node, the file names of the uploaded documents of the current pending project can be detected and the corresponding uploaded document information can be generated to determine the progress of the current pending node based on the uploaded document information.

[0048] Optionally, determining the current node progress to be determined of the current node to be processed based on the uploaded document information includes: determining the number of documents to be used of the uploaded documents based on the uploaded document information; determining the current node progress to be determined corresponding to the current node to be processed based on the ratio of the number of documents to be used and the total number of documents in the project requirement table.

[0049] The number of documents to be used can be understood as the number of uploaded documents of the current pending project at the current pending node. It should be noted that the number of documents to be used here refers to the number of documents that can match the names of the project documents in the project requirements table.

[0050] Specifically, for example, the project requirements table at the current pending node includes Document A, Document B, Document C, and Document D, i.e., the total number of documents in the project requirements table is 4. If the uploaded documents of the current pending project include Document A and Document B, i.e., the number of documents to be used in the current pending project is 2, then the progress of the current pending project at the current pending node is 50%.

[0051] In actual applications, in order to ensure the normal progress of the project, it is necessary to accurately control the execution time and actual execution status of each business node. Therefore, it is necessary to pay attention to the actual execution status of each business node.

[0052] Taking the current project to be processed as an example, determine at least one document to be uploaded associated with the current node to be processed, as well as the preset upload time of each document to be uploaded; for each document to be uploaded, if the upload time of the current document to be uploaded is greater than the corresponding preset upload time, determine that the current document to be uploaded is an unuploaded document; generate warning information corresponding to the unuploaded document, and send the warning information to the client associated with the current node to be processed.

[0053] Among them, the documents to be uploaded can be understood as the documents that need to be uploaded at the current node to be processed for the current project to be processed. The preset upload time can be understood as the latest time point set in advance for each document to be uploaded, such as 9:00 am on February 8. Unuploaded documents can be understood as project documents that have not been uploaded after the preset upload time. The early warning information can be understood as the prompt information sent to the client when there are unuploaded project documents beyond the preset upload time. The client can be understood as the mobile device of the person in charge associated with the current node to be processed, or it can be a monitoring platform device, such as, the corresponding early warning information can be sent to the mobile device of the person in charge of the current node to be processed.

[0054] Specifically, a preset upload time is set for each document to be uploaded in the project requirements table. If the current document to be uploaded has not been uploaded after the preset upload time, it can be determined that the current document to be uploaded is not uploaded. In order to avoid the impact of the non-uploaded document on the entire project process, it is necessary to prompt the relevant person in charge as soon as possible so that the relevant person in charge can take appropriate measures as soon as possible. Therefore, it is necessary to generate corresponding warning information based on the non-uploaded document and send the generated warning information to the corresponding client, such as to the mobile device of the person in charge of the current node to be processed.

[0055] S130 , determining the completed nodes of the corresponding pending items according to the pending node progress of each pending node.

[0056] The completed node can be understood as a pending node with a pending node progress of 100%.

[0057] Specifically, when the to-be-processed item's to-be-processed node progress at a certain to-be-processed node is 100%, the to-be-processed node can be determined as a completed node.

[0058] In actual application, the completed nodes of the corresponding pending projects are determined based on the pending node progress of each pending node, including: for each pending node, if the project documents associated with the current pending node have been uploaded, the current pending node is determined to be a completed node.

[0059] S140: Determine the project progress of the corresponding pending project based on the ratio of the number of each completed node to the total number of the pending nodes.

[0060] Among them, project progress can be understood as the progress of the project to be processed.

[0061] For example, the pending project includes 5 pending nodes, and 3 nodes have been completed at the current moment, so the project progress is 60%.

[0062] In addition, in actual applications, based on the visualization plug-in, each of the to-be-processed items and the corresponding item-related information is visualized to obtain a visualization image, and the visualization image is displayed on the target display interface.

[0063] Among them, the visualization plug-in can be understood as a plug-in for visualization rendering, and the visualization plug-in can be installed in the project management system. The visualization image can be understood as an image processed by the visualization plug-in, such as a bar chart comparing the project progress of each pending project under the current project category, or a pie chart of the completion status of a pending project at each pending node, etc. The specific form of the visualization image can be determined according to actual conditions and is not specifically limited here. The target display interface can be understood as an interface for displaying visualization images, such as the display interface of the project management system.

[0064] Specifically, when a user needs to understand a pending project in detail, he or she can call up a visualization image corresponding to the pending project. The visualization image may include project-related information associated with the pending project that the user needs to view, such as the project-related information may include at least one of the project name, project progress, project responsible user, project start time, expected completion time, and actual completion time.

[0065] The technical solution of this embodiment determines at least one pending project associated with the current project category and at least one pending node associated with the current project category, determines the pending project corresponding to the current project category based on the project information table, and determines the pending node corresponding to the current project category based on the node information table. For each pending project, the current pending node progress of the current pending project at the current pending node is determined, and according to the project requirement table of the current pending node, the uploaded document information of the current pending project and whether there are any unuploaded documents are detected, so as to determine the current pending node progress based on the ratio of the number of documents to be used of the uploaded documents of the pending node to the total number of documents in the project requirement table. According to the pending node progress of each pending node, the completed node of the corresponding pending project is determined. If all the project documents associated with the current pending node have been uploaded, the current pending node is determined to be a completed node. Based on the ratio of the number of each completed node and the total number of the pending nodes, the project progress of the corresponding pending project is determined, so as to facilitate the relevant users to manage the pending projects according to the project progress of each pending project. It solves the problem of lack of good management methods for multiple projects at the same time, which leads to the neglect of project requirements of some projects, and achieves the effect of unified management of multiple projects to better understand the project requirements of each project.

[0066] Example 2

[0067] In a specific example, Figure 2 As shown, project creation is performed in advance in the project management system, such as setting different project categories according to the project attributes or project execution nodes of each project. Taking the project execution node (i.e., the node to be processed) as an example, when it is detected that the target control corresponding to the current project category is triggered, the pending projects and pending nodes associated with the current project category are retrieved, wherein the pending projects can be determined based on the project information table associated with the current project category, and the pending nodes can be determined based on the node information table associated with the current project category. It can be understood that each pending node can include multiple pending projects, but the pending nodes of the pending projects belonging to the same project category are the same, and the project documents in the project requirement table of each pending node are also the same. For the current pending node, the project requirement table of the current pending node can include the project document information that each pending project needs to upload under the current pending node. Taking the current pending project as an example, if the project documents that need to be uploaded in the project requirement table include Document 1, Document 2, Document 3, Document 4 and Document 5, and the document names of different project documents are different, the document names uploaded by the current pending project at the current pending node are detected according to the project requirement table to determine the uploaded documents and unuploaded documents of the current pending document. According to the ratio of the number of uploaded documents (i.e., the number of documents to be used) to the total number of documents in the project requirement table, the progress of the current pending node of the pending node can be determined. If all the project documents that need to be uploaded of the current pending node have been uploaded, it can be determined that the current pending node of the current pending node is a completed node. According to the ratio of the number of completed nodes to the total number of pending nodes of the current pending project, the project progress of the current pending project can be determined.

[0068] It should be noted that the corresponding upload time (i.e., preset upload time) can be set for the documents to be uploaded for each pending project. If the document to be uploaded has not been uploaded after the preset upload time, it can be considered that the document to be uploaded is not uploaded, that is, the execution of the current pending node is unqualified, and an early warning message corresponding to the unuploaded document is generated, and the early warning message is sent to the corresponding client, such as the mobile device of the person in charge associated with the current pending node. In other words, only when all the project documents that need to be uploaded under each pending node of the pending project have been uploaded and meet the acceptance standards of the project materials, until all the pending nodes of the pending project are completed nodes, can the project progress of the pending project be determined to be completed, and when the project acceptance is carried out, it can be determined that the project acceptance of the pending project is qualified.

[0069] In addition, in actual application, in order to facilitate users to view and manage each pending project, the project progress of each pending project can also be visualized based on this technical solution. A JS+highcharts plug-in (i.e., a visualization plug-in) can be set in the project management system. Based on the visualization plug-in, the pending project and the project-related information related to each pending project are visualized to obtain a visualization image for the user to view. For example, taking the visualization of the planned completion time of the current project pending project as an example, until June 2022-the department expects to complete 14 projects, actually complete 13 projects, and postpone 1 project, it can be determined that the project completion rate in the current project category is the ratio of the actually completed projects to the expected completed projects, that is, project completion rate = 13 / 14 = 93%. The project completion rate can be displayed in a pie chart. At the same time, each pending project and the associated project-related information can be associated with the pie chart for display. Among them, the project-related letters include the project name, project type, project leader, project start time, project planned end time, and the content of each project node (content of the start-up preparation phase, construction site management content, completion acceptance content, project file archiving information, project node leader, planned start time of each node, planned end time, actual start time, and actual end time).

[0070] The technical solution of this embodiment determines at least one pending project associated with the current project category and at least one pending node associated with the current project category, determines the pending project corresponding to the current project category based on the project information table, and determines the pending node corresponding to the current project category based on the node information table. For each pending project, the current pending node progress of the current pending project at the current pending node is determined, and according to the project requirement table of the current pending node, the uploaded document information of the current pending project and whether there are any unuploaded documents are detected, so as to determine the current pending node progress based on the ratio of the number of documents to be used of the uploaded documents of the pending node to the total number of documents in the project requirement table. According to the pending node progress of each pending node, the completed node of the corresponding pending project is determined. If all the project documents associated with the current pending node have been uploaded, the current pending node is determined to be a completed node. Based on the ratio of the number of each completed node and the total number of the pending nodes, the project progress of the corresponding pending project is determined, so as to facilitate the relevant users to manage the pending projects according to the project progress of each pending project. It solves the problem of lack of good management methods for multiple projects at the same time, which leads to the neglect of project requirements of some projects, and achieves the effect of unified management of multiple projects to better understand the project requirements of each project.

[0071] Example 3

[0072] Figure 3 This is a schematic diagram of the structure of a project management device provided by the third embodiment of the present invention. Figure 3 As shown, the device includes: an information determination module 210 , a node progress determination module 220 , a completed node determination module 230 and a project progress determination module 240 .

[0073] The information determination module 210 is configured to determine at least one to-be-processed project associated with a current project category and at least one to-be-processed node associated with the current project category;

[0074] The node progress determination module 220 is used to determine the current node progress of the current pending project at the current pending node for each pending project;

[0075] The completed node determination module 230 is used to determine the completed nodes of the corresponding pending project according to the pending node progress of each pending node;

[0076] The project progress determination module 240 is configured to determine the project progress of the corresponding pending project based on the ratio of the number of each completed node to the total number of pending nodes.

[0077] The technical solution of this embodiment determines at least one pending project associated with the current project category and at least one pending node associated with the current project category, determines the pending project corresponding to the current project category based on the project information table, and determines the pending node corresponding to the current project category based on the node information table. For each pending project, the current pending node progress of the current pending project at the current pending node is determined, and according to the project requirement table of the current pending node, the uploaded document information of the current pending project and whether there are any unuploaded documents are detected, so as to determine the current pending node progress based on the ratio of the number of documents to be used of the uploaded documents of the pending node to the total number of documents in the project requirement table. According to the pending node progress of each pending node, the completed node of the corresponding pending project is determined. If all the project documents associated with the current pending node have been uploaded, the current pending node is determined to be a completed node. Based on the ratio of the number of each completed node and the total number of the pending nodes, the project progress of the corresponding pending project is determined, so as to facilitate the relevant users to manage the pending projects according to the project progress of each pending project. It solves the problem of lack of good management methods for multiple projects at the same time, which leads to the neglect of project requirements of some projects, and achieves the effect of unified management of multiple projects to better understand the project requirements of each project.

[0078] Optionally, the information determination module includes: an information table retrieval submodule, configured to retrieve a project information table and a node information table corresponding to the current project category when detecting that a target control corresponding to the current project category is triggered; wherein the project information table includes at least one to-be-processed project associated with the current project category, and the node information table includes at least one to-be-processed node associated with the current project category;

[0079] a to-be-processed project determination submodule, configured to determine, based on the project information table, at least one to-be-processed project corresponding to the current project category; and

[0080] The to-be-processed node determination submodule is configured to determine, based on the node information table, at least one to-be-processed node corresponding to the current to-be-processed item.

[0081] Optionally, the node progress determination module includes: a project requirement table acquisition submodule, configured to acquire a project requirement table corresponding to the current node to be processed; wherein the project requirement table includes a project name corresponding to a project document associated with the current node to be processed;

[0082] An uploaded document information determination submodule is configured to detect the document name of the uploaded document of the current node to be processed based on the project requirement table, and obtain the uploaded document information corresponding to the current node to be processed;

[0083] The to-be-determined node progress determination submodule is configured to determine the current to-be-determined node progress of the current to-be-processed node based on the uploaded document information.

[0084] Optionally, the to-be-determined node progress determination submodule includes: a to-be-used document quantity determination unit, configured to determine the to-be-used document quantity of the uploaded documents based on the uploaded document information;

[0085] The unit for determining the progress of the node to be determined is used to determine the progress of the current node to be determined corresponding to the current node to be processed based on the ratio of the number of documents to be used and the total number of documents in the project requirement table.

[0086] Optionally, the node progress determination module further includes: a preset upload time determination submodule, configured to determine at least one to-be-uploaded document associated with the current to-be-processed node, and a preset upload time for each to-be-uploaded document;

[0087] a non-uploaded document determination submodule, configured to, for each of the to-be-uploaded documents, determine that the current to-be-uploaded document is a non-uploaded document if the upload time of the current to-be-uploaded document is greater than the corresponding preset upload time;

[0088] The warning information sending submodule is used to generate warning information corresponding to the unuploaded document and send the warning information to the client associated with the current node to be processed.

[0089] Optionally, the completed node determination module is configured to determine, for each node to be processed, if all project documents associated with the current node to be processed have been uploaded, that the current node to be processed is a completed node.

[0090] Optionally, the project management device also includes: a visualization module, which is used to visualize each of the pending projects and the corresponding project-related information based on a visualization plug-in to obtain a visualization image, and display the visualization image on a target display interface; wherein the project-related information includes at least one of the project name, project progress, project responsible user, project start time, expected completion time, and actual completion time.

[0091] The project management device provided by the embodiment of the present invention can execute the project management method provided by any embodiment of the present invention, and has the corresponding functional modules and beneficial effects of the execution method.

[0092] Example 4

[0093] Figure 4 A schematic diagram of the structure of an electronic device 10 of an embodiment of the present invention is shown. The electronic device is intended to represent various forms of digital computers, such as laptop computers, desktop computers, workstations, personal digital assistants, servers, blade servers, mainframe computers, and other suitable computers. The electronic device may also represent various forms of mobile devices, such as personal digital assistants, cellular phones, smart phones, wearable devices (such as helmets, glasses, watches, etc.) and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely examples and are not intended to limit the implementation of the present invention described and / or claimed herein.

[0094] like Figure 4 As shown, the electronic device 10 includes at least one processor 11 and a memory, such as a read-only memory (ROM) 12, a random access memory (RAM) 13, etc., which is communicatively connected to the at least one processor 11. The memory stores a computer program that can be executed by the at least one processor. The processor 11 can perform various appropriate actions and processes according to the computer program stored in the read-only memory (ROM) 12 or the computer program loaded from the storage unit 18 into the random access memory (RAM) 13. Various programs and data required for the operation of the electronic device 10 can also be stored in the RAM 13. The processor 11, ROM 12, and RAM 13 are connected to each other via a bus 14. An input / output (I / O) interface 15 is also connected to the bus 14.

[0095] Multiple components in the electronic device 10 are connected to the I / O interface 15, including an input unit 16, such as a keyboard, a mouse, etc.; an output unit 17, such as various types of displays, speakers, etc.; a storage unit 18, such as a magnetic disk, an optical disk, etc.; and a communication unit 19, such as a network card, a modem, a wireless communication transceiver, etc. The communication unit 19 allows the electronic device 10 to exchange information / data with other devices via a computer network such as the Internet and / or various telecommunication networks.

[0096] The processor 11 may be any general-purpose and / or specialized processing component with processing and computing capabilities. Examples of the processor 11 include, but are not limited to, a central processing unit (CPU), a graphics processing unit (GPU), various specialized artificial intelligence (AI) computing chips, various processors for running machine learning model algorithms, a digital signal processor (DSP), and any suitable processor, controller, microcontroller, etc. The processor 11 executes the various methods and processes described above, such as the project management method.

[0097] In some embodiments, the project management method can be implemented as a computer program tangibly embodied in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program can be loaded and / or installed on electronic device 10 via ROM 12 and / or communication unit 19. When the computer program is loaded into RAM 13 and executed by processor 11, one or more steps of the project management method described above can be performed. Alternatively, in other embodiments, processor 11 can be configured to perform the project management method in any other suitable manner (e.g., via firmware).

[0098] Various embodiments of the systems and techniques described herein can be implemented in digital electronic circuit systems, integrated circuit systems, field programmable gate arrays (FPGAs), application specific integrated circuits (ASICs), application specific standard products (ASSPs), system-on-chip systems (SOCs), programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments can include being implemented in one or more computer programs that are executable and / or interpreted on a programmable system that includes at least one programmable processor, which can be a special purpose or general purpose programmable processor that can receive data and instructions from a storage system, at least one input device, and at least one output device, and transmit data and instructions to the storage system, the at least one input device, and the at least one output device.

[0099] Computer programs for implementing the project management method of the present invention can be written in any combination of one or more programming languages. These computer programs can be provided to a processor of a general-purpose computer, a special-purpose computer, or other programmable data processing device, such that when executed by the processor, the computer programs implement the functions / operations specified in the flowcharts and / or block diagrams. The computer programs can be executed entirely on the machine, partially on the machine, as a stand-alone software package, partially on the machine and partially on a remote machine, or entirely on a remote machine or server.

[0100] In the context of the present invention, computer-readable storage media can be tangible media that can contain or store a computer program for use with an instruction execution system, device or equipment or used in combination with an instruction execution system, device or equipment. Computer-readable storage media can include but are not limited to electronic, magnetic, optical, electromagnetic, infrared or semiconductor systems, devices or equipment, or any suitable combination of the foregoing. Alternatively, computer-readable storage media can be machine-readable signal media. More specific examples of machine-readable storage media can include electrical connections based on one or more lines, portable computer disks, hard disks, random access memories (RAM), read-only memories (ROM), erasable programmable read-only memories (EPROM or flash memory), optical fibers, portable compact disk read-only memories (CD-ROM), optical storage devices, magnetic storage devices, or any suitable combination of the foregoing.

[0101] To provide interaction with a user, the systems and techniques described herein can be implemented on an electronic device having: a display device (e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor) for displaying information to the user; and a keyboard and pointing device (e.g., a mouse or trackball) through which the user can provide input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, the feedback provided to the user can be any form of sensory feedback (e.g., visual feedback, auditory feedback, or tactile feedback); and input from the user can be received in any form (including acoustic input, voice input, or tactile input).

[0102] The systems and techniques described herein can be implemented in a computing system that includes back-end components (e.g., as a data server), or a computing system that includes middleware components (e.g., an application server), or a computing system that includes front-end components (e.g., a user computer with a graphical user interface or web browser through which a user can interact with implementations of the systems and techniques described herein), or a computing system that includes any combination of such back-end components, middleware components, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication (e.g., a communication network). Examples of communication networks include: a local area network (LAN), a wide area network (WAN), a blockchain network, and the Internet.

[0103] A computing system may include clients and servers. The clients and servers are typically remote from each other and typically interact via a communication network. This client-server relationship arises through computer programs running on the respective computers, creating a client-server relationship. The server may be a cloud server, also known as a cloud computing server or cloud host. This server is a hosting product within the cloud computing service ecosystem that addresses the management difficulties and limited scalability of traditional physical hosting and VPS services.

[0104] It should be understood that the various forms of the processes shown above can be used to reorder, add, or delete steps. For example, the steps described in the present invention can be performed in parallel, sequentially, or in a different order, as long as the desired results of the technical solution of the present invention can be achieved. This is not limited herein.

[0105] The above specific embodiments do not limit the scope of protection of the present invention. Those skilled in the art will appreciate that various modifications, combinations, sub-combinations, and substitutions may be made based on design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of the present invention are intended to be included within the scope of protection of the present invention.

Claims

1. A project management method, suitable for unified management of multiple projects, characterized by: include: Determining at least one to-be-processed project associated with a current project category, and at least one to-be-processed node associated with the current project category; wherein the to-be-processed node is a business execution node that matches the current project category; For each pending item, determine the current pending item's progress at the current pending node; Determine the completed nodes of the corresponding pending projects based on the pending node progress of each pending node; The project progress of the corresponding to-be-processed project is determined based on the ratio of the number of each completed node to the total number of the to-be-processed nodes.

2. The method according to claim 1, characterized in that The determining of at least one to-be-processed project associated with the current project category and at least one to-be-processed node associated with the current project category includes: When it is detected that the target control corresponding to the current project category is triggered, the project information table and the node information table corresponding to the current project category are retrieved; wherein the project information table includes at least one to-be-processed project associated with the current project category, and the node information table includes at least one to-be-processed node associated with the current project category; Determining at least one to-be-processed project corresponding to the current project category based on the project information table; and At least one to-be-processed node corresponding to the current to-be-processed item is determined based on the node information table.

3. The method according to claim 1, characterized in that Determining the current to-be-processed node progress of the current to-be-processed project at the current to-be-processed node includes: Obtaining a project requirement table corresponding to the current node to be processed; wherein the project requirement table includes a project name corresponding to a project document associated with the current node to be processed; Based on the project requirement table, the document name of the uploaded document of the current node to be processed is detected to obtain the uploaded document information corresponding to the current node to be processed; Based on the uploaded document information, the current to-be-determined node progress of the current to-be-processed node is determined.

4. The method according to claim 3, characterized in that The determining, based on the uploaded document information, the current to-be-determined node progress of the current to-be-processed node includes: Determining the number of documents to be used of the uploaded documents based on the uploaded document information; Based on the ratio of the number of documents to be used and the total number of documents in the project requirement table, the progress of the current node to be determined corresponding to the current node to be processed is determined.

5. The method according to claim 3, characterized in that Also includes: Determining at least one to-be-uploaded document associated with the current node to be processed, and a preset upload time for each to-be-uploaded document; For each of the documents to be uploaded, if the upload time of the current document to be uploaded is greater than the corresponding preset upload time, determining that the current document to be uploaded is a non-uploaded document; Generate warning information corresponding to the unuploaded document, and send the warning information to a client associated with the current node to be processed.

6. The method according to claim 1, characterized in that Determining the completed nodes of the corresponding pending items according to the pending node progress of each pending node includes: For each node to be processed, if all project documents associated with the current node to be processed have been uploaded, the current node to be processed is determined to be a completed node.

7. The method according to claim 1, characterized in that Also includes: Based on the visualization plug-in, each of the pending projects and the corresponding project-related information is visualized to obtain a visualization image, and the visualization image is displayed on the target display interface; wherein the project-related information includes at least one of the project name, project progress, project responsible user, project start time, expected completion time and actual completion time.

8. A project management device, suitable for unified management of multiple projects, characterized in that: include: An information determination module, configured to determine at least one pending project associated with a current project category and at least one pending node associated with the current project category; wherein the pending node is a business execution node that matches the current project category; A node progress determination module is used to determine the current to-be-processed node progress of the current to-be-processed project at the current to-be-processed node for each to-be-processed project; A completed node determination module is used to determine the completed nodes of the corresponding pending items according to the pending node progress of each pending node; The project progress determination module is used to determine the project progress of the corresponding pending project based on the ratio of the number of each completed node to the total number of the pending nodes.

9. An electronic device, characterized in that: The electronic device comprises: at least one processor; and a memory communicatively connected to the at least one processor; wherein, The memory stores a computer program that can be executed by the at least one processor. The computer program is executed by the at least one processor to enable the at least one processor to perform the project management method according to any one of claims 1 to 7.

10. A computer-readable storage medium, characterized in that The computer-readable storage medium stores computer instructions, and the computer instructions are used to enable a processor to implement the project management method according to any one of claims 1 to 7 when executed.

Citation Information

Patent Citations

  • Resource management method and device thereof

    CN113177749A

  • Task management method and device, computer equipment and storage medium

    CN113570220A