A project process management method, device, equipment and medium

Abstract

The application discloses a project process management method, device, equipment and medium, and belongs to the technical field of project management. The method comprises the following steps: when a project establishment instruction is received, collecting project establishment application data, extracting a plurality of sub-delivery projects based on the project establishment application data, matching a corresponding sub-project approval link for each sub-delivery project, pushing an approval task of the corresponding sub-delivery project to each project manager bound thereto based on each sub-project approval link, and updating the project state to project establishment into effect after determining that all project managers corresponding to each sub-delivery project return approval opinions of agreeing to establish the project. The application can split the overall project into different sub-delivery projects, establish a binding relationship between the sub-delivery projects and corresponding project managers, match an independent sub-project approval link for each sub-delivery project, avoid the problems of unclear approval boundaries or cross of rights and responsibilities, improve the project establishment and approval efficiency, and strengthen the rigor of the approval process.

Description

Technical Field

[0001] This application relates to the field of project management technology, and in particular to a project process management method, apparatus, equipment and medium. Background Technology

[0002] In the current technology for implementing project initiation approval management, the overall project package approval model is generally adopted. For example, when submitting the project initiation application, all the deliverables of the entire project are packaged into a single project initiation unit, and then the approval task of the data of the single project initiation unit is uniformly pushed to all project managers, who then summarize and verify the overall project initiation information.

[0003] Because this model cannot establish a precise binding relationship between the delivered content and the corresponding responsible personnel, the approval authority and responsibility among multiple responsible persons are prone to confusion. Moreover, since all responsible persons share the same approval process, it is impossible to clearly define the approval scope and authority of each responsible person, which leads to problems such as missed approvals, incorrect approvals, or duplicate approvals. This not only causes low efficiency in project approval but also significantly reduces the rigor of the approval process, making it difficult to adapt to the actual needs of efficiency and precision in project approval in collaborative scenarios with multiple responsible persons. Summary of the Invention

[0004] The main purpose of this application is to propose a project process management method, apparatus, equipment and medium. By breaking down the overall project into sub-delivery projects of different delivery types and establishing a binding relationship between the sub-delivery projects and the corresponding project leaders, an independent sub-project initiation approval link can be matched for each sub-delivery project, avoiding the problems of unclear approval boundaries or overlapping responsibilities, effectively improving the efficiency of project initiation approval and strengthening the rigor of the approval process.

[0005] To achieve the above objectives, one aspect of this application proposes a project process management method, the method comprising: Upon receiving a project initiation instruction, the project initiation application data corresponding to the project is collected; wherein, the project initiation application data includes: project name, project type, project deliverables list, and several different project leaders; Extract sub-deliverable items of different delivery types from the project delivery list; wherein each sub-deliverable item corresponds to multiple project managers; For each of the aforementioned sub-deliverable projects, a sub-project approval chain corresponding to the sub-deliverable project is matched based on the project name, the project type, and the sub-deliverable project. Based on each of the sub-project approval links, the approval task for each sub-deliverable project is pushed to each of the project leaders, so that each of the project leaders can review and return the approval opinion; wherein, the approval opinion includes: agreeing to the project or disagreeing to the project. When it is determined that the approval opinions returned by all project leaders for each sub-deliverable project are "agree to initiate the project", the project status of the project is updated to "initiated and effective", and all the approval opinions of all the sub-deliverable projects and each sub-deliverable project are pushed to all the project leaders.

[0006] Furthermore, in some embodiments, the project application data further includes: the project applicant; The method further includes: When it is determined that the approval opinion corresponding to any of the project leaders is "disagree with project initiation", a project rejection notice is generated and sent to the project applicant.

[0007] Furthermore, in some embodiments, the step of matching the sub-project approval chain corresponding to the sub-delivery project based on the project name, the project type, and the sub-delivery project includes: Keyword extraction is performed on the project name to determine the corresponding business identifier; Based on the business identifier and the project type, a set of target approval nodes is selected; Based on the sub-delivery project and the delivery type of the sub-delivery project, several target approval nodes are matched from the target approval node set; The various target approval nodes are sequentially connected to output the sub-project approval chain.

[0008] Furthermore, in some embodiments, the project type includes: research project, engineering project, or delivery project; The process of filtering out the target approval node set based on the business identifier and the project type includes: Based on the business scenario corresponding to the business identifier, an approval node library corresponding to the business scenario is selected; wherein, the approval node library includes: several different sets of approval nodes to be matched; When the project type is determined to be scientific research, the set of approval nodes to be matched, which includes technical review nodes, technical achievement verification nodes, and technical acceptance nodes, will be used as the target approval node set. When the project type is determined to be an engineering project, the set of approval nodes to be matched, which includes safety review nodes, drawing review nodes, and funding review nodes, will be used as the target approval node set. When the project type is determined to be a delivery type, the set of approval nodes to be matched, which includes project confirmation nodes and project acceptance nodes, will be used as the target approval node set.

[0009] Furthermore, in some embodiments, the target approval node set includes several approval nodes to be matched; each approval node to be matched corresponds to an approval scope and a functional attribute tag; Based on the sub-delivery project and its delivery type, several target approval nodes are matched from the target approval node set, including: Iterate through each of the approval nodes to be matched in the target approval node set, and determine whether the functional attribute tag matches the delivery type; If so, when it is determined that the scope of review can cover the project content of the sub-delivery project, the approval node to be matched is marked as the target approval node; when it is determined that the scope of review cannot cover the project content of the sub-delivery project, the approval node to be matched is removed. If not, remove the pending approval node.

[0010] Furthermore, in some embodiments, the step of sequentially concatenating the various target approval nodes to output the sub-project approval chain includes: Traverse each target approval node and determine the approval priority corresponding to the target approval node based on the functional attribute tag of the target approval node; According to the approval priority from high to low, the target approval nodes are sorted to generate a node flow sequence; Based on the node flow sequence, each target approval node is sequentially associated, and the permissions of each target approval node are bound to the project leaders corresponding to the sub-delivery project, thereby generating and outputting the sub-project approval chain.

[0011] Furthermore, in some embodiments, after updating the project status to "project initiation effective" status, the method further includes: Collect the execution progress of each of the aforementioned sub-deliverables; When it is detected that the execution progress of any sub-delivery project is lagging behind the preset progress threshold, a progress warning message is generated and pushed to all project managers.

[0012] To achieve the above objectives, another aspect of this application proposes a project process management device, the device comprising: The project initiation response module is used to collect the project initiation application data corresponding to the project when a project initiation instruction is received; wherein, the project initiation application data includes: project name, project type, project deliverables list and several different project leaders; The delivery project extraction module is used to extract sub-delivery projects of different delivery types from the project delivery list; wherein each sub-delivery project corresponds to multiple project managers; The project approval link matching module is used to match the sub-project approval link corresponding to each sub-delivery project based on the project name, the project type and the sub-delivery project. The approval task push module is used to push the approval task of each sub-deliverable project to each project leader based on each sub-project approval link, so that each project leader can review and return the approval opinion; wherein, the approval opinion includes: agreeing to the project or disagreeing to the project. The project status update module is used to update the project status of the project to the effective status when it is determined that the approval opinions returned by all project leaders corresponding to each sub-deliverable project are "agree to initiate the project", and simultaneously push all sub-deliverable projects and all approval opinions of each sub-deliverable project to all project leaders.

[0013] To achieve the above objectives, another aspect of this application provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the project process management method described above.

[0014] To achieve the above objectives, another aspect of the embodiments of this application proposes a computer-readable storage medium storing a computer program that, when executed by a processor, implements the project process management method described above.

[0015] The embodiments of this application include at least the following beneficial effects: This application provides a project process management method, apparatus, device, and medium. When receiving a project initiation instruction, the method collects initiation application data including project name, project type, project delivery list, and several different project leaders. Then, it extracts sub-deliverable projects of different delivery types from the project delivery list and establishes a correspondence between each sub-deliverable project and multiple project leaders. Thus, for each sub-deliverable project, based on the project name, project type, and the sub-deliverable project, it can match the corresponding sub-initiation approval link. Then, based on each sub-initiation approval link, it pushes the approval task of the corresponding sub-deliverable project to each of its bound project leaders. After determining that all project leaders corresponding to each sub-deliverable project have returned approval opinions agreeing to the initiation, it updates the project status to "initiation effective" and synchronizes all sub-deliverable projects and corresponding approval opinions to all project leaders. Unlike existing technologies, this application breaks down the overall project into sub-delivery projects of different delivery types and establishes a binding relationship between each sub-delivery project and its corresponding project leader. This allows for the matching of an independent sub-project approval chain for each sub-delivery project, clearly defining that each sub-delivery project is only bound to its corresponding project leaders. The approval task for each sub-delivery project is pushed only to its designated leader for approval, ensuring a one-to-one correspondence between different approval processes, approval items, and leaders. This avoids the problem of all personnel approving the same overall project in the same process, preventing unclear approval boundaries or overlapping responsibilities. This solves the problem of chaotic approval authority and responsibility caused by the sharing of a single approval process in existing technologies. Therefore, this application clearly defines the approval scope and authority of each leader for sub-delivery projects through different sub-project approval chains, thus constructing a project approval mechanism adapted to multi-leader collaboration. This effectively improves project approval efficiency and strengthens the rigor of the approval process, meeting the actual needs for efficiency and accuracy in project approval under multi-leader collaboration scenarios. Attached Figure Description

[0016] Figure 1 This is a flowchart illustrating a project process management method provided in an embodiment of this application; Figure 2 This is a schematic diagram of the sub-project approval process generation flow provided in the embodiments of this application; Figure 3 This is provided in the embodiments of this application; Figure 4 This is a schematic diagram of the structure of a project process management device provided in an embodiment of this application; Figure 5 This is a schematic diagram of the hardware structure of the electronic device provided in the embodiments of this application. Detailed Implementation

[0017] To make the objectives, technical solutions, and advantages of this application clearer, the following detailed description is provided in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are merely illustrative of this application and are not intended to limit it. In the following description, when referring to the accompanying drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with those of this application; they are merely examples of apparatuses and methods consistent with some aspects of the embodiments of this application as detailed in the appended claims.

[0018] It is understood that the terms “first,” “second,” etc., used in this application may be used herein to describe various concepts, but unless otherwise stated, these concepts are not limited by these terms. These terms are only used to distinguish one concept from another. For example, without departing from the scope of the embodiments of this application, first information may also be referred to as second information, and similarly, second information may also be referred to as first information. Depending on the context, the words “if,” “when,” or “in response to a determination” as used herein may be interpreted as “when…” or “when…” or “in response to a determination.”

[0019] As used in this application, the terms "several", "each", etc., "several" include one, two or more, "each" refers to each of the corresponding plurality, and "any" refers to any one of the plurality.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application belongs. The terminology used herein is for the purpose of describing embodiments of this application only and is not intended to limit this application.

[0021] Before providing a detailed description of the embodiments of this application, some of the nouns and terms involved in the embodiments of this application will be explained first. The nouns and terms involved in the embodiments of this application are subject to the following interpretations.

[0022] (1) TF-IDF algorithm refers to TF-IDF (Term Frequency-Inverse Document Frequency), which is a natural language processing algorithm used to measure the importance of words in text and is used for keyword extraction from short texts.

[0023] Collaborative project approval by multiple responsible persons has become a major scenario for project process management. However, traditional project process management solutions often adopt a packaged approval model for the entire project without finely breaking down the project deliverables or matching specific approval processes to different delivery requirements. All project managers share the same set of approval processes; for example, approval tasks are pushed out uniformly.

[0024] Therefore, traditional technologies cannot establish a binding relationship between delivered projects and corresponding responsible persons, resulting in confusion of approval responsibilities among multiple responsible persons, making it difficult to clarify the approval scope and authority of each responsible person, thus leading to problems such as missed approvals, incorrect approvals, or duplicate approvals. Moreover, using the same approval standards for different types of projects and different deliverables results in low approval efficiency and insufficient rigor. At the same time, after the project is approved, there is a lack of effective monitoring of the execution progress of sub-deliverable projects, making it impossible to detect progress deviations in a timely manner, which can easily lead to overall project delays. It is difficult to meet the needs of efficient and precise project approval and execution control in multi-scenario and multi-responsible collaborative environments.

[0025] In view of this, this application provides a project process management method, apparatus, equipment, and medium. This solution first collects project initiation application data, extracts sub-delivery projects of different delivery types, establishes a correspondence between sub-delivery projects and project leaders, then matches a dedicated sub-initiation approval link for each sub-delivery project, pushes approval tasks based on the link and verifies approval opinions, and finally updates the project status and synchronizes approval information. Compared to the traditional overall packaged approval model, this application achieves refined decomposition of project initiation approval and precise adaptation of different approval links. It can clarify the approval responsibilities of multiple responsible persons, avoid problems such as missed approvals and incorrect approvals, improve approval efficiency and rigor, and meet the actual needs of different project process management in enterprise or hospital scenarios.

[0026] This application provides a project workflow management method, which relates to the field of project management technology. It can be applied to terminals or servers, and can also be project management software, hospital management office software, or enterprise management office software running on a terminal or server. In some embodiments, the terminal can be a smartphone, tablet, laptop, desktop computer, smart office device, etc., but is not limited to these. The server can be configured as an independent physical server, a server cluster or distributed system composed of multiple physical servers, or a cloud server providing basic services such as cloud services, cloud storage, and enterprise collaboration services. The software can be a project management system, collaborative office platform, etc., that implements the project workflow management method, but is not limited to the above forms.

[0027] Figure 1 This is an optional flowchart of a project process management method provided in an embodiment of this application. Figure 1 The method may include, but is not limited to, steps S1 to S5: Step S1: Upon receiving the project initiation instruction, collect the project initiation application data corresponding to the project; wherein, the project initiation application data includes: project name, project type, project deliverable list, and several different project leaders; Step S2: Extract sub-deliverable items of different delivery types from the project delivery list; wherein each sub-deliverable item corresponds to multiple project managers; Step S3: For each sub-deliverable project, based on the project name, the project type, and the sub-deliverable project, match the sub-project approval link corresponding to the sub-deliverable project; Step S4: Based on each of the sub-project approval links, push the approval task of each sub-deliverable project to each of the project leaders, so that each of the project leaders can review and return the approval opinion; wherein, the approval opinion includes: agreeing to the project or disagreeing to the project. Step S5: When it is determined that the approval opinions returned by all project leaders corresponding to each sub-deliverable project are "agree to initiate the project", the project status of the project is updated to "initiated and effective", and all the approval opinions of all the sub-deliverable projects and each sub-deliverable project are pushed to all the project leaders.

[0028] Steps S1 to S5 of this embodiment, based on the received project initiation instruction and the synchronously collected project application data, firstly extract the sub-delivery projects of different delivery types in the project delivery list. Then, based on the project name, the project type, and the sub-delivery project, match the sub-project initiation approval link corresponding to a certain sub-delivery project from the system node library, and establish a precise binding relationship between the sub-delivery project and the corresponding project leader. Match a dedicated sub-project initiation approval link for each sub-delivery project, thereby constructing a refined project initiation approval mechanism that can adapt to the collaboration of multiple leaders. This solves the problems of chaotic approval responsibilities and unclear approval scope and authority caused by all leaders sharing the same approval process in traditional technology. Through this embodiment, the efficiency of project initiation approval can be improved, and by matching a dedicated sub-project initiation approval link for each sub-delivery project, the rigor of the approval process is strengthened, which can meet the actual needs of project initiation approval for high efficiency and accuracy in multi-leader collaboration scenarios.

[0029] For step S1, in some embodiments, when initiating the project approval process, the project initiation instruction must first be captured. The project initiation instruction can be submitted by the project initiator through the project management system. After receiving the project initiation instruction, the present invention can automatically collect the project application data corresponding to the project. All data is entered into the system in advance by the project initiator and is initially verified to ensure data integrity before being used as the basis for subsequent processes.

[0030] Optionally, the data collection for project applications adopts an automated extraction method, eliminating the need for manual summarization. After collection, the data is automatically stored in the system database for quick retrieval later. It also supports real-time data updates to ensure data accuracy and timeliness.

[0031] For step S2, in some embodiments, the present invention can break down the overall delivery content according to the delivery type based on the project delivery list to obtain multiple independent sub-delivery projects. The delivery type can be divided according to the actual needs of the project. For example, scientific research projects can be divided into sub-delivery projects such as scheme design, prototype development and testing and acceptance. Engineering projects can be divided into sub-delivery projects such as drawing design, safety assessment and cost accounting. Delivery projects can be divided into sub-delivery projects such as project confirmation and result acceptance.

[0032] After the breakdown is completed, the correspondence between each sub-deliverable project and the project leader can be automatically established, ensuring that the approval requirements of each sub-deliverable project are covered by the corresponding person in charge. For example, for sub-deliverable projects related to technical solution design in scientific research projects, the technical leader and product leader can be bound to them. For sub-deliverable projects related to testing and acceptance, the testing leader and the technical leader can be bound to them. This can achieve accurate allocation of approval authority and responsibility and avoid confusion of authority and responsibility.

[0033] For step S3, in some embodiments, the present invention has the following detailed refinement process when deriving the approval chain for each sub-project: The process of matching the sub-project initiation approval chain corresponding to the sub-delivery project based on the project name, the project type, and the sub-delivery project includes: Keyword extraction is performed on the project name to determine the corresponding business identifier; Based on the business identifier and the project type, a set of target approval nodes is selected; Based on the sub-delivery project and the delivery type of the sub-delivery project, several target approval nodes are matched from the target approval node set; The various target approval nodes are sequentially connected to output the sub-project approval chain.

[0034] In illustrative terms, embodiments of the present invention can extract keywords from project names using natural language processing algorithms to identify keywords that characterize the core business of the project, thereby determining the corresponding business identifier. Optionally, a keyword extraction algorithm based on dictionary matching can be combined with a pre-set business domain dictionary to segment the project name and perform dictionary matching to quickly locate keywords related to the business identifier. Alternatively, the TF-IDF algorithm can be used to calculate the importance of words in the project name, filtering out core keywords that characterize the business type and project domain, thus realizing the short text keyword extraction of project names in this invention.

[0035] For example, when the project name is "Artificial Intelligence Algorithm R&D Project," the keywords "artificial intelligence," "algorithm," or "R&D" can be extracted, and then the business identifier can be determined as "artificial intelligence R&D." When the project name is "Engineering Construction Project," the keywords "engineering" or "construction" can be extracted, and then the business identifier can be determined as "engineering construction." When the project name is "Software Product Delivery Project," the keywords "software product" or "delivery" can be extracted, and then the business identifier can be determined as "software product delivery." It can be understood that the business identifier is used to filter the approval node library that matches the project's business scenario, ensuring that the approval nodes are consistent with the project's business requirements.

[0036] Furthermore, in some embodiments, different business scenarios correspond to different sets of approval nodes to be matched. For each sub-delivery project, the following specific implementation process is involved in determining the target set of approval nodes for that sub-delivery project: The project types include: research, engineering, or delivery-related. Therefore, the process of filtering out the target approval node set based on the business identifier and the project type includes: Based on the business scenario corresponding to the business identifier, an approval node library corresponding to the business scenario is selected; wherein, the approval node library includes: several different sets of approval nodes to be matched; When the project type is determined to be scientific research, the set of approval nodes to be matched, which includes technical review nodes, technical achievement verification nodes, and technical acceptance nodes, will be used as the target approval node set. When the project type is determined to be an engineering project, the set of approval nodes to be matched, which includes safety review nodes, drawing review nodes, and funding review nodes, will be used as the target approval node set. When the project type is determined to be a delivery type, the set of approval nodes to be matched, which includes project confirmation nodes and project acceptance nodes, will be used as the target approval node set.

[0037] It is understood that, in this embodiment of the invention, the approval node library corresponding to the business scenario is first selected from the system's preset approval node database based on the business scenario corresponding to the business identifier. Then, based on the project type, a target set of approval nodes matching the project type is determined from the selected business scenario approval node library. The specific determination process is as follows: If the project type is determined to be scientific research, a set of approval nodes to be matched, including technical review nodes, technical achievement verification nodes, and technical acceptance nodes, will be selected and marked as the target approval node set. It can be understood that technical review nodes can be used to review the technical feasibility of sub-delivery projects, technical achievement verification nodes can be used to verify the completeness of the results of sub-delivery projects, and technical acceptance nodes can be used to verify the compliance of the results of sub-delivery projects.

[0038] If the project type is determined to be engineering, a set of approval nodes to be matched, including security review nodes, drawing review nodes, and funding review nodes, will be filtered out and marked as the target approval node set. It can be understood that security review nodes can be used to review the security compliance of sub-delivery projects, drawing review nodes can be used to review the drawing standardization of sub-delivery projects, and funding review nodes can be used to review the funding rationality of sub-delivery projects.

[0039] If the project type is determined to be delivery type, a set of approval nodes to be matched, including project confirmation nodes and project acceptance nodes, will be filtered out and marked as the target approval node set. It can be understood that project confirmation nodes can be used to confirm the delivery scope of sub-delivery projects, and project acceptance nodes can be used to accept the delivery quality of sub-delivery projects.

[0040] Therefore, this embodiment of the invention first locks the approval node library corresponding to the business scenario based on the business identifier, ensuring that the approval nodes participating in the matching are highly relevant to the project's domain and business attributes, avoiding the introduction of approval nodes unrelated to the business scenario, and making the approval process more in line with actual business needs. For different project types such as research, engineering, and delivery, a dedicated set of approval nodes to be matched is configured, enabling different types of projects to achieve approval paths consistent with their own characteristics. Furthermore, approval nodes related to the functions of each project type are preset for each type; for example, research projects focus on technical review, results verification and acceptance, engineering projects focus on safety, drawing and funding review, and delivery projects focus on scope confirmation and quality acceptance, avoiding overlapping, redundant, or missing approval content, and facilitating project leaders to perform their respective duties.

[0041] This invention employs a two-layer rule-based filtering system to quickly and automatically locate the target approval node set without complex calculations or manual configuration. The matching logic is simple and the execution efficiency is high. Different business scenarios or project types can be independently configured and expanded with corresponding approval node sets. When adding new business areas or project types, only the corresponding set needs to be added to the node library without modifying the core matching logic, thus giving the project workflow management system better adaptability and scalability.

[0042] Furthermore, in some embodiments, after determining the target approval node set for each sub-deliverable project, when matching multiple relevant target approval nodes from the determined target approval node set for each sub-deliverable project, the following specific implementation process is also included: The target approval node set includes several approval nodes to be matched; each approval node to be matched corresponds to an approval scope and a functional attribute tag. Based on the sub-delivery project and its delivery type, several target approval nodes are matched from the target approval node set, including: Iterate through each of the approval nodes to be matched in the target approval node set, and determine whether the functional attribute tag matches the delivery type; If so, when it is determined that the scope of review can cover the project content of the sub-delivery project, the approval node to be matched is marked as the target approval node; when it is determined that the scope of review cannot cover the project content of the sub-delivery project, the approval node to be matched is removed. If not, remove the pending approval node.

[0043] In illustrative terms, in this embodiment of the invention, the target approval node set contains several approval nodes to be matched. Each approval node to be matched corresponds to an approval scope and a functional attribute label. It can be understood that the functional attribute label is used to characterize the approval function of the node. For example, the functional attribute label of the technical review node is technical review, and the functional attribute label of the security review node is security review. It corresponds to the delivery type of the sub-delivery project.

[0044] The specific matching process is as follows: Iterate through each approval node to be matched in the target approval node set. First, determine whether the functional attribute label of the node matches the delivery type of the current sub-delivery project. If the functional attribute label matches the delivery type, further determine whether the review scope of the approval node to be matched can cover the project content of the current sub-delivery project. If the review scope can cover the project content, mark the approval node to be matched as the target approval node. If the review scope cannot cover the project content, remove the approval node to be matched. If the functional attribute tag does not match the delivery type, the approval node to be matched will be removed directly.

[0045] For example, in a research project, a sub-deliverable project related to technical solution design has a delivery type of solution design. The target approval node set includes three matching approval nodes: a technical review node, a technical achievement verification node, and a technical acceptance node. Traversing these three matching approval nodes, the technical review node is marked as the target approval node because its functional attribute tag is "technical review," which matches the solution design category and its review scope covers the feasibility of the technical solution design. The technical achievement verification node's functional attribute tag is "achievement verification," which does not match the solution design category, so it is directly eliminated. The technical acceptance node's functional attribute tag is "achievement acceptance," which does not match the solution design category, so it is directly eliminated. The final matched target approval node is the technical review node.

[0046] Therefore, in this embodiment of the invention, by first determining whether the functional attribute tags of the approval node to be matched match the delivery type of the sub-delivery project, approval nodes that are irrelevant to the review requirements of the current sub-delivery project can be quickly eliminated, ensuring that the selected target approval nodes are all in line with the core attributes of the sub-delivery project. For example, for sub-delivery projects of the solution design type, only technical review nodes are retained, avoiding the introduction of approval nodes that are not related to the delivery type, reducing invalid approval steps, and improving the targeting of approval.

[0047] In this embodiment of the invention, in order to ensure that the approval content is highly consistent with the content of the sub-deliverable project and to avoid the approval being out of sync, based on the functional attribute tag matching, it is further determined whether the review scope of the approval node to be matched covers the specific content of the sub-deliverable project. This ensures that the review content of each target approval node corresponds to the actual needs of the sub-deliverable project, avoids the problem of mismatch between the review node and the sub-deliverable content, ensures that no part of the approval process is missed, and improves the rigor of the approval.

[0048] In some embodiments, please refer to Figure 2 The diagram shows the sub-project approval process. The matching process for the sub-project approval process is as follows: First, extract keywords from the current project name to obtain the current business identifier; based on the business identifier, identify the corresponding business scenario and then filter out the approval node library corresponding to that scenario. Next, based on the project type—such as research, engineering, or delivery—the invention can identify the target approval node set corresponding to the previously selected approval node library. For example, for research projects, the set containing technical review nodes, technical achievement verification nodes, and technical acceptance nodes can be defined as the target approval node set, thereby narrowing the scope of approval nodes to those highly matched to the project type.

[0049] Then, each sub-deliverable project within the project is processed one by one. For each sub-deliverable project, this invention can find the truly matching approval node from the target approval node set; obtain the functional attribute tags of each approval node, such as the tag for the technical review node being "technical review," and check if it matches the delivery type of solution design; if it matches, then check the review scope of this node to see if it can cover the content of the sub-deliverable project, such as whether the technical review node can review the feasibility of the technical solution. Only when both conditions are met will this node be selected as the target approval node.

[0050] After selecting all the target approval nodes, this invention links these nodes in sequence according to their approval priority, such as first technical review, then results verification, and then acceptance, ultimately forming a sub-project approval chain specifically for this sub-delivery project.

[0051] The above process is executed cyclically, processing one sub-deliverable project before moving on to the next, until all sub-deliverable projects have been traversed, and each has generated its own dedicated approval chain. Finally, multiple different sub-project initiation approval chains are output, one for each sub-deliverable project. Therefore, thanks to this invention, the situation where all projects use the same approval process will not occur. The different sub-project initiation approval chains can clearly define the approval scope and authority of each responsible person for the sub-deliverable project.

[0052] Furthermore, in some embodiments, after selecting multiple target approval nodes based on the delivery type and content of the sub-delivery project, the process of forming the final sub-project approval chain also includes the following specific implementation processes: The step of sequentially connecting the various target approval nodes to output the sub-project approval chain includes: Traverse each target approval node and determine the approval priority corresponding to the target approval node based on the functional attribute tag of the target approval node; According to the approval priority from high to low, the target approval nodes are sorted to generate a node flow sequence; Based on the node flow sequence, each target approval node is sequentially associated, and the permissions of each target approval node are bound to the project leaders corresponding to the sub-delivery project, thereby generating and outputting the sub-project approval chain.

[0053] In illustrative terms, in this embodiment of the invention, each target approval node can be traversed to determine the approval priority corresponding to the target approval node. The approval priority is divided according to the importance of the review function. For example, the priority of core review nodes, such as technical review nodes and security review nodes, is higher than that of regular verification nodes. The priority of regular verification nodes is higher than that of process filing nodes, so as to ensure that important review links are executed first.

[0054] Next, the target approval nodes are sorted in descending order of approval priority to obtain the node flow sequence corresponding to the current sub-delivery project. For example, in the sub-delivery project of construction drawings in an engineering project, the target approval nodes are the drawing review node and the safety review node. The safety review node has a higher priority than the drawing review node, and the node flow sequence is from the safety review node to the drawing review node.

[0055] Based on the node flow sequence derived above, each target approval node is sequentially associated with another node. At the same time, permissions can be bound to each target approval node and the project manager corresponding to that sub-delivery project, generating and outputting the sub-project approval chain. It can be understood that after permission binding, only the person in charge of that sub-delivery project can view and approve the approval task of that node, ensuring the accurate correspondence between approval authority and responsibility.

[0056] Therefore, in this embodiment of the invention, the entire process automatically completes node sorting, association and permission binding based on preset priority rules, without the need for manual configuration of the approval process. It can quickly generate a dedicated link for each sub-delivery project, greatly reducing manual intervention and lowering the time cost and risk of human error in the configuration of the approval process in project management.

[0057] Optionally, the approval priority rules can be flexibly configured according to project type and industry standards. For example, scientific research projects can prioritize technical review, engineering projects can prioritize safety and funding review, and delivery projects can prioritize results acceptance. In this embodiment of the invention, the approval process can be tailored to the business logic of different projects, avoiding gaps in approval caused by generic processes, making the approval process more targeted, and effectively ensuring the compliance and feasibility of project initiation.

[0058] In a preferred embodiment, the following is a specific implementation scenario of the present invention applied to a hospital project management system. The scenario is set as follows: the project application data corresponding to the currently initiated project initiation instruction has the project name "Research on Intelligent Diagnostic Algorithm for Tumors Based on Brain Imaging"; the project type is scientific research; the project delivery list contains a sub-deliverable project, namely: Scientific Experiment Design; the resulting target approval node set includes the following approval nodes: ethics review node, scientific research plan review node, data security review node, and budget review node; the project leaders are: Dr. Liu, the scientific research leader; Dr. Zhou, the ethics specialist; Mr. Wu, the data security administrator; and Mr. Zheng, the financial specialist. Therefore, the link generation process in this embodiment of the invention is as follows: Traverse the nodes to determine the approval priority. Since scientific research projects follow the management logic of prioritizing ethical compliance, followed by scientific feasibility, with data security as a fallback, and funding verification as the final step, the priorities of each approval node are as follows: the ethical review node has the highest priority, the scientific research plan review node has the second highest priority, the data security review node has the third highest priority, and the funding budget review node has the lowest priority, which is fourth.

[0059] Node flow sequence is generated by prioritizing nodes; after prioritization, the following flow sequence can be obtained: [ethics review node, research proposal review node, data security review node, budget review node]; Based on the node flow sequence obtained in the previous step, serial association and permission binding are performed to form the final approval link; then, the ethics review node is bound to ethics specialist Dr. Zhou, the research plan review node is bound to research leader Dr. Liu, the data security review node is bound to data security administrator Engineer Wu, and the budget review node is bound to finance specialist Engineer Zheng.

[0060] Therefore, the final sub-project approval process is as follows: [Ethics review node (Dr. Zhou), Research proposal review node (Dr. Liu), Data security review node (Engineer Wu), Budget review node (Engineer Zheng)], as illustrated in the diagram below. Figure 3 As shown.

[0061] In a schematic illustration, within the research experiment design scenario of the aforementioned research projects, this invention can prioritize matching nodes such as ethics review, research plan evaluation, data security review, and budget review according to research project management standards. These nodes are then automatically sorted according to their priority, forming a node flow sequence. Each approval node is then linked to the corresponding responsible person's authority, ultimately generating a sub-project approval chain that conforms to research management standards. Therefore, this chain generation process requires no manual arrangement, satisfies research project compliance requirements, and achieves precise division of approval responsibilities, avoiding process errors, unauthorized approvals, or missing key review stages.

[0062] For step S4, in some embodiments, based on the completed sub-project approval chain, the present invention can automatically push the approval tasks of each sub-delivery project to the terminal devices of all project leaders corresponding to the sub-delivery project in the order of the approval nodes in the chain; optionally, the push method can be flexibly selected from internal messages of the project management system, emails or SMS, etc., to ensure that each leader can receive the approval task in a timely manner and avoid approval delays.

[0063] Understandably, after receiving a task, the project manager can view the detailed information, review standards, and review scope of the corresponding approval nodes for the sub-deliverable project through the project management system. Based on their own responsibilities, they can assess the feasibility of the sub-deliverable project and submit an approval opinion of either approving or disapproving it. Optionally, if they choose to disapprove, the manager can attach a brief rejection explanation, clearly informing the applicant of the reasons for rejection, providing clear guidance for subsequent project modifications and improvements. Simultaneously, the project management system records the approval status of each node in real time, including unapproved, under approval, approved, and corresponding approval opinions, allowing the project initiator and relevant personnel to view the approval progress in real time and promptly follow up on incomplete approval tasks.

[0064] In some embodiments, for step S5, the present invention can summarize the approval opinions of all project leaders corresponding to each sub-deliverable project in real time, adopting a unanimous approval verification rule. Only when all leaders corresponding to a sub-deliverable project submit their approval opinions is the sub-deliverable project considered approved. For example, once all sub-deliverable projects have been approved, the system automatically updates the project status from "Project Approval" to "Project Effective," formally completing the project initiation process. Simultaneously, the system automatically summarizes detailed information on all sub-deliverable projects, as well as all approval opinions corresponding to each sub-deliverable project, and pushes this information to all project leaders. This ensures that each leader clearly understands the project initiation results and the approval details of each sub-deliverable project, avoiding execution deviations caused by information asymmetry, thereby guaranteeing the coordination and efficiency of the overall project progress.

[0065] In some embodiments, the project application data may further include: the project applicant; The method further includes: When it is determined that the approval opinion corresponding to any of the project leaders is "disagree with project initiation", a project rejection notice is generated and sent to the project applicant.

[0066] In this embodiment, as an illustration, a project applicant is added to the project application data, and when any project leader disagrees with the approval, a project rejection message is automatically generated and pushed to the project applicant.

[0067] Therefore, this solution directly pushes rejection information to the project applicant, enabling the initiator to obtain the approval result immediately, avoiding information delays, and significantly improving the efficiency of the project initiation process.

[0068] Optionally, the rejection message can directly point to the specific approval failure result, allowing the project applicant to quickly identify the problems in the current project application and make targeted modifications and improvements to the sub-deliverables, project materials, or application content, without having to blindly investigate the entire project, thus speeding up the process of resubmitting the project application.

[0069] Furthermore, after updating the project status to "Project Initiation Effective," this method also includes a step to monitor the execution progress of sub-deliverable projects, as follows: After updating the project status to "project approved and effective", the method further includes: Collect the execution progress of each of the aforementioned sub-deliverables; When it is detected that the execution progress of any sub-delivery project is lagging behind the preset progress threshold, a progress warning message is generated and pushed to all project managers.

[0070] In illustrative terms, this invention can collect the execution progress of each sub-deliverable project in real time. The execution progress can be entered periodically by the corresponding project leader, such as updated daily or weekly, or it can be automatically extracted through the associated project execution system, such as the code submission progress of scientific research projects or the construction progress of engineering projects. Optionally, the progress threshold can be flexibly configured according to the overall project cycle and the importance of the sub-deliverable project. For example, if a sub-deliverable project is planned to be completed in 10 days, the preset progress threshold is that the daily progress threshold is not less than 10%. This invention can compare the actual execution progress of each sub-delivery project with a preset progress threshold in real time. When it is detected that the actual execution progress of any sub-delivery project is lagging behind the preset progress threshold, a progress warning message is immediately generated. The warning message includes the name of the lagging sub-delivery project, the current actual progress, the preset progress threshold, and the duration of the lag. It can also be pushed to all project managers in a timely manner to remind them to investigate the cause of the lag and take remedial measures to avoid delays in the sub-delivery project leading to overall project delays.

[0071] In one embodiment, taking a scientific research project as a specific application scenario, the complete execution process of this application is illustrated by way of example.

[0072] An applicant, Zhang, initiated a project proposal for an artificial intelligence algorithm research and development project. The project type is research-based, and the deliverables include three sub-deliverables: technical solution design, algorithm prototype development, and algorithm testing and acceptance. The project leaders include technical lead Li, testing lead Wang, and product lead Zhao. In a pre-defined approval node database, the set of approval nodes to be matched for research-based projects includes technical review nodes, technical achievement verification nodes, and technical acceptance nodes. The functional attribute tags and review scope of each approval node to be matched are as follows: Technical review node, whose functional attribute tag is technical review, and whose review scope is the feasibility of technical solutions and algorithms; Technical achievement verification node, whose functional attribute tag is achievement verification, and whose review scope is the completeness of R&D prototypes and test reports; Technical acceptance node, whose functional attribute tag is achievement acceptance, and whose review scope is the compliance of test acceptance results; The preset progress threshold is: the progress of each sub-delivery project shall not be less than 25% per week.

[0073] Therefore, the complete execution flow of this invention embodiment is as follows: Zhang submitted a project initiation request through the project management system. After receiving the corresponding initiation instruction, the system collected the project application data, which included: Project Name: Artificial Intelligence Algorithm Research and Development Project; Project Type: Scientific Research; Project Deliverables: Technical Solution Design, Algorithm Prototype Development, Algorithm Testing and Acceptance; Project Leaders: Li, Wang, Zhao; Project Applicant: Zhang. Extract the sub-deliverables from the project deliverable list and break them down by delivery type into technical solution design (corresponding delivery type: solution design class), algorithm prototype development (corresponding delivery type: prototype development class), and algorithm testing and acceptance (corresponding delivery type: testing and acceptance class). Establish the correspondence between sub-deliverables and responsible persons: technical solution design is bound to Li and Zhao; algorithm prototype development is bound to Li; and algorithm testing and acceptance is bound to Li and Wang. For each sub-deliverable project, a sub-project approval process is matched. First, the project name keywords are extracted as: artificial intelligence, algorithm, and R&D. The business identifier is determined to be artificial intelligence algorithm R&D. Based on the above business identifiers and project types (scientific research), a set of target approval nodes is selected, which includes: technical review nodes, technical achievement verification nodes, and technical acceptance nodes. For technical solution design (solution design category), iterate through each approval node to be matched. If the functional attribute tags of the technical review node match the delivery type and the review scope covers the technical solution design, mark it as the target approval node; if the other two nodes do not match, they are removed. For algorithm prototype development (prototype development type), since the functional attribute tags of the technical achievement verification node match the delivery type and the review scope covers the prototype development results, it is marked as the target approval node; the other two nodes do not match and are removed. For algorithm test acceptance (test acceptance category), if the functional attribute tags of the technical acceptance node match the delivery type and the review scope covers the test acceptance results, it is marked as the target approval node; if the other two nodes do not match, they are removed. It is not difficult to conclude that the target approval nodes of the above three sub-delivery projects are all single nodes, which do not need to be sorted. They are directly connected into a sub-project approval chain and bound to the corresponding responsible person's permissions. Based on the sub-project approval links of each of the above items, the approval task for the technical solution design can be pushed to Li and Zhao; the approval task for the algorithm prototype development can be pushed to Li; and the approval task for the algorithm testing and acceptance can be pushed to Li and Wang. Furthermore, since Li and Zhao both submitted their approval for the technical solution design, Li submitted his approval for the algorithm prototype development, and Li and Wang both submitted their approval for the algorithm testing and acceptance, it can be determined that all responsible persons for all sub-deliverable projects have approved the project. The project status will be updated to "Project Approval Effective," and all sub-deliverable projects and their corresponding approval opinions will be pushed to Li, Wang, and Zhao. The execution progress of the three sub-delivery projects is collected in real time. If it is detected that the progress of the sub-delivery project for algorithm prototype development is only 15% after one week, which is lower than the preset progress threshold of 25%, a progress warning message is generated and pushed to Li, Wang, and Zhao to remind the relevant person in charge to speed up the prototype development progress.

[0074] This embodiment is illustrative, using a scientific research project as the core scenario. Those skilled in the art can flexibly adapt the technical solution of this invention to other project types such as engineering and delivery projects. All adaptations and adjustments based on the core technical ideas of this invention are within the protection scope of this invention.

[0075] In summary, this invention achieves refined management of project initiation and approval, and compared with traditional technologies, it has the following beneficial effects: This invention enables refined breakdown and precise adaptation of project initiation approval. By splitting projects into sub-delivery projects according to delivery type, a dedicated sub-initiation approval link is matched for each sub-delivery project, ensuring that the approval process accurately corresponds to the delivery requirements, project type, and business scenario of the sub-delivery project, and avoiding the disconnect between approval content and actual needs. This invention solves the problems of unclear responsibilities and ambiguous approval scope caused by all responsible persons sharing the same approval process in traditional technology by establishing a precise binding relationship between sub-delivery projects and their corresponding responsible persons, and by binding approval nodes with the permissions of responsible persons. This avoids missed approvals, incorrect approvals, or duplicate approvals, and improves the rigor of the approval process. This invention reduces manual intervention and shortens the approval cycle by automating the collection of project application data, splitting sub-projects, matching approval links, pushing approval tasks, and verifying approval opinions. At the same time, it achieves automatic synchronization of approval information, avoiding the time-consuming and error-prone process of manual summarization and transmission. After project initiation, this invention enables dynamic monitoring of the execution progress of sub-deliverable projects. By setting preset progress thresholds and collecting progress data in real time, it can promptly detect progress deviations, remind the person in charge to handle them in a timely manner, avoid overall project delays, and ensure efficient project progress. This invention is adaptable to various project types, including scientific research, engineering, and delivery projects. Sub-delivery projects with different business scenarios and delivery types can all achieve accurate approval through this method, eliminating the need to customize approval processes for different projects. This reduces the adaptation cost of project process management and meets the needs for efficient and accurate project process management in multi-collaboration scenarios.

[0076] Please see Figure 4 This application also provides a project process management device that can implement the above-described project process management method. The device includes: The project initiation response module 601 is used to collect the project initiation application data corresponding to the project when a project initiation instruction is received; wherein, the project initiation application data includes: project name, project type, project delivery list and several different project leaders; The delivery item extraction module 602 is used to extract sub-delivery items of different delivery types from the project delivery list; wherein each sub-delivery item corresponds to multiple project managers; The project approval link matching module 603 is used to match the sub-project approval link corresponding to each sub-delivery project based on the project name, the project type and the sub-delivery project. The approval task push module 604 is used to push the approval task of each sub-delivery project to each project leader based on each sub-project approval link, so that each project leader can approve and return the approval opinion; wherein, the approval opinion includes: agreeing to the project or disagreeing to the project. The project status update module 605 is used to update the project status of the project to the effective status when it is determined that the approval opinions returned by all project leaders corresponding to each sub-deliverable project are "agree to initiate the project", and simultaneously push all sub-deliverable projects and all approval opinions of each sub-deliverable project to all project leaders.

[0077] It is understood that the content of the above method embodiments is applicable to the present device embodiments. The specific functions implemented by the present device embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0078] It should be noted that the device embodiments described above are merely illustrative. The modules described as separate components may or may not be physically separate, and the components shown as modules may or may not be physical modules; they may be located in one place or distributed across multiple network modules. Some or all of the modules can be selected to achieve the purpose of this embodiment according to actual needs. Furthermore, in the accompanying drawings of the device embodiments provided by this invention, the connection relationships between modules indicate that they have communication connections, which can be specifically implemented as one or more communication buses or signal lines. Those skilled in the art can understand and implement this without any creative effort.

[0079] Those skilled in the art will clearly understand that, for convenience and simplicity, the specific working process of the device described above can be referred to the corresponding process in the foregoing method embodiments, and will not be repeated here.

[0080] This application also provides an electronic device, which includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement the project workflow management method described above. This electronic device can include any smart terminal such as a tablet computer or an in-vehicle computer.

[0081] It is understood that the content of the above method embodiments is applicable to this device embodiment. The specific functions implemented by this device embodiment are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0082] Please see Figure 5 , Figure 5 This illustrates the hardware structure of an electronic device according to another embodiment, the electronic device comprising: The processor 701 can be implemented using a general-purpose CPU (Central Processing Unit), microprocessor, application-specific integrated circuit (ASIC), or one or more integrated circuits, and is used to execute relevant programs to implement the technical solutions provided in the embodiments of this application. The memory 702 can be implemented as a read-only memory (ROM), a static storage device, a dynamic storage device, or a random access memory (RAM). The memory 702 can store the operating system and other application programs. When the technical solutions provided in the embodiments of this application are implemented through software or firmware, the relevant program code is stored in the memory 702 and is called and executed by the processor 701. The input / output interface 703 is used to implement information input and output; The communication interface 704 is used to enable communication and interaction between this device and other devices. Communication can be achieved through wired means (such as USB, Ethernet cable, etc.) or wireless means (such as mobile network, Wi-Fi, Bluetooth, etc.). Bus 705 transmits information between various components of the device (e.g., processor 701, memory 702, input / output interface 703, and communication interface 704); The processor 701, memory 702, input / output interface 703 and communication interface 704 are connected to each other within the device via bus 705.

[0083] The processor 701 may be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor may be a microprocessor or any conventional processor. This processor is the control center of the terminal device, connecting various parts of the terminal device via various interfaces and lines.

[0084] The memory 702 can be used to store the computer program. The processor implements various functions of the terminal device by running or executing the computer program stored in the memory and calling data stored in the memory. The memory may mainly include a program storage area and a data storage area. The program storage area may store the operating system, at least one application program required for a function, etc.; the data storage area may store data created based on the use of the mobile phone, etc. In addition, the memory may include high-speed random access memory, and may also include non-volatile memory, such as hard disk, RAM, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device or other volatile solid-state storage device.

[0085] This application also provides a computer-readable storage medium storing a computer program that, when executed by a processor, implements the above-described project workflow management method.

[0086] It is understood that the content of the above method embodiments is applicable to the present computer storage medium embodiments. The specific functions implemented by the present computer storage medium embodiments are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0087] This application also provides a computer program product, including a computer program that, when executed by a processor, implements the above-described project process management method.

[0088] It is understood that the content of the above method embodiments is applicable to the embodiments of this computer program product. The specific functions implemented by the embodiments of this computer program product are the same as those of the above method embodiments, and the beneficial effects achieved are also the same as those achieved by the above method embodiments.

[0089] Those skilled in the art will understand that all or some of the steps, apparatuses, or functional modules / units in the methods disclosed above can be implemented as software, firmware, hardware, or suitable combinations thereof.

[0090] The preferred embodiments of the present application have been described above with reference to the accompanying drawings, but this does not limit the scope of the claims of the present application. Any modifications, equivalent substitutions, and improvements made by those skilled in the art without departing from the scope and substance of the embodiments of the present application shall be within the scope of the claims of the present application.

Claims

1. A project process management method, characterized in that, The method includes: Upon receiving a project initiation instruction, the project initiation application data corresponding to the project is collected; wherein, the project initiation application data includes: project name, project type, project deliverables list, and several different project leaders; Extract sub-deliverable items of different delivery types from the project delivery list; wherein each sub-deliverable item corresponds to multiple project managers; For each of the aforementioned sub-deliverable projects, a sub-project approval chain corresponding to the sub-deliverable project is matched based on the project name, the project type, and the sub-deliverable project. Based on each of the sub-project approval links, the approval task for each sub-deliverable project is pushed to each of the project leaders, so that each of the project leaders can review and return the approval opinion; wherein, the approval opinion includes: agreeing to the project or disagreeing to the project. When it is determined that the approval opinions returned by all project leaders for each sub-deliverable project are "agree to initiate the project", the project status of the project is updated to "initiated and effective", and all the approval opinions of all the sub-deliverable projects and each sub-deliverable project are pushed to all the project leaders.

2. The project process management method according to claim 1, characterized in that, The project application data also includes: the project applicant; The method further includes: When it is determined that the approval opinion corresponding to any of the project leaders is "disagree to project initiation", a project rejection notice is generated and sent to the project applicant.

3. The project process management method according to claim 1, characterized in that, The process of matching the sub-project initiation approval chain corresponding to the sub-delivery project based on the project name, the project type, and the sub-delivery project includes: Keyword extraction is performed on the project name to determine the corresponding business identifier; Based on the business identifier and the project type, a set of target approval nodes is selected; Based on the sub-delivery project and the delivery type of the sub-delivery project, several target approval nodes are matched from the target approval node set; The various target approval nodes are sequentially connected to output the sub-project approval chain.

4. The project process management method according to claim 3, characterized in that, The project types include: research, engineering, or delivery-related. The process of filtering out the target approval node set based on the business identifier and the project type includes: Based on the business scenario corresponding to the business identifier, an approval node library corresponding to the business scenario is selected; wherein, the approval node library includes: several different sets of approval nodes to be matched; When the project type is determined to be scientific research, the set of approval nodes to be matched, which includes technical review nodes, technical achievement verification nodes, and technical acceptance nodes, will be used as the target approval node set. When the project type is determined to be an engineering project, the set of approval nodes to be matched, which includes safety review nodes, drawing review nodes, and funding review nodes, will be used as the target approval node set. When the project type is determined to be a delivery type, the set of approval nodes to be matched, which includes project confirmation nodes and project acceptance nodes, will be used as the target approval node set.

5. The project process management method according to claim 3, characterized in that, The target approval node set includes several approval nodes to be matched; each approval node to be matched corresponds to an approval scope and a functional attribute tag. Based on the sub-delivery project and its delivery type, several target approval nodes are matched from the target approval node set, including: Iterate through each of the approval nodes to be matched in the target approval node set, and determine whether the functional attribute tag matches the delivery type; If so, when it is determined that the scope of review can cover the project content of the sub-delivery project, the approval node to be matched is marked as the target approval node; when it is determined that the scope of review cannot cover the project content of the sub-delivery project, the approval node to be matched is removed. If not, remove the pending approval node.

6. The project process management method according to claim 5, characterized in that, The step of sequentially connecting the various target approval nodes to output the sub-project approval chain includes: Traverse each target approval node and determine the approval priority corresponding to the target approval node based on the functional attribute tag of the target approval node; According to the approval priority from high to low, the target approval nodes are sorted to generate a node flow sequence; Based on the node flow sequence, each target approval node is sequentially associated, and the permissions of each target approval node are bound to the project leaders corresponding to the sub-delivery project, thereby generating and outputting the sub-project approval chain.

7. The project process management method according to claim 1, characterized in that, After updating the project status to "project approved and effective", the method further includes: Collect the execution progress of each of the aforementioned sub-deliverables; When it is detected that the execution progress of any sub-delivery project is lagging behind the preset progress threshold, a progress warning message is generated and pushed to all project managers.

8. A project process management device, characterized in that, The device includes: The project initiation response module is used to collect the project initiation application data corresponding to the project when a project initiation instruction is received; wherein, the project initiation application data includes: project name, project type, project deliverables list and several different project leaders; The delivery project extraction module is used to extract sub-delivery projects of different delivery types from the project delivery list; wherein each sub-delivery project corresponds to multiple project managers; The project approval link matching module is used to match the sub-project approval link corresponding to each sub-delivery project based on the project name, the project type and the sub-delivery project. The approval task push module is used to push the approval task of each sub-deliverable project to each project leader based on each sub-project approval link, so that each project leader can review and return the approval opinion; wherein, the approval opinion includes: agreeing to the project or disagreeing to the project. The project status update module is used to update the project status of the project to the effective status when it is determined that the approval opinions returned by all project leaders corresponding to each sub-deliverable project are "agree to initiate the project", and simultaneously push all sub-deliverable projects and all approval opinions of each sub-deliverable project to all project leaders.

9. An electronic device, characterized in that, The electronic device includes a memory and a processor. The memory stores a computer program, and the processor executes the computer program to implement a project process management method according to any one of claims 1 to 7.

10. A computer-readable storage medium storing a computer program, characterized in that, When the computer program is executed by the processor, it implements a project process management method according to any one of claims 1 to 7.

Images