A method, apparatus, equipment and medium for automated project management

Abstract

This invention discloses a method, apparatus, device, and medium for automated project management. The method includes: creating a new task in a multidimensional table based on the task description returned by a first executor via a task collection card; verifying the task progress information returned by a second executor via a progress collection card, and updating each in-process task in the multidimensional table after successful verification; having a third executor submit an output link in a scoring and review card, transferring the scoring and review card to an auditor, and updating the target task in the multidimensional table based on the audit results filled in by the auditor in the scoring and review card; and updating the target project column in the visualization dashboard based on the updated target multidimensional table. Using the above technical solution, intelligent and efficient task progress collection can be achieved, the output confirmation process can be simplified, and the real-time project progress can be visualized, improving project processing efficiency.

Description

Technical Field

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

[0002] Project management is a core component of enterprise digital operations. With the popularization of distributed team collaboration models and the increase in project complexity, it is necessary to improve the efficiency, real-time nature, and intelligence of project management.

[0003] Currently, most projects rely on managers to manually complete the entire process of task assignment, progress collection, and output confirmation through instant messaging tools, emails, offline meetings, etc., or use semi-automated general project management tools that provide basic functions such as task progress recording and task dashboard display. However, data updates and process triggering still require active user operation, making it impossible to achieve automated management of the entire project process.

[0004] Existing project management solutions are inefficient, lack unified structured storage and management of task information, are highly fragmented, and require multiple rounds of communication at each stage of the project, significantly increasing the cost of ineffective communication. Summary of the Invention

[0005] This invention provides a method, apparatus, equipment, and medium for automated project management, which can achieve intelligent and efficient task progress collection, simplify the output confirmation process, and visualize the real-time progress of the project, effectively reducing ineffective communication between the executor and the manager, and improving project processing efficiency.

[0006] According to one aspect of the present invention, a method for automated project management is provided, comprising: When a task collection event is triggered, a task collection card is sent to the first executor, and a new task is created in a multidimensional table based on the task description returned by the first executor through the task collection card; wherein, each multidimensional table is used to maintain task information for a single item; When a task progress maintenance event is triggered, a progress collection card is sent to the second executor according to the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After the verification is successful, each in-process task in the multidimensional table is updated. When the target task's status is updated to "completed", a scoring review card is generated and sent to the third executor. After the third executor submits the output link in the scoring review card, the scoring review card is transferred to the reviewer. Based on the review results filled in by the reviewer in the scoring review card, the target task is updated in the multidimensional table. When an update to the target multidimensional table is detected, the target item column in the visualization dashboard is updated based on the updated target multidimensional table.

[0007] According to another aspect of the present invention, a project automation management device is provided, comprising: The new task creation module is used to send a task collection card to the first executor when a task collection event is triggered, and to create a new task in a multidimensional table based on the task description returned by the first executor through the task collection card; wherein each multidimensional table is used to maintain task information for a single project; The task progress update module is used to send a progress collection card to the second executor according to the multidimensional table when a task progress maintenance event is triggered, and to verify the task progress information returned by the second executor through the progress collection card. After the verification is successful, the module updates each in-process task in the multidimensional table. The task review module is used to generate a score review card and send it to the third executor when the task status of the target task is updated to the completed status. After the third executor submits the output link in the score review card, the score review card is transferred to the reviewer. Based on the review results filled in by the reviewer in the score review card, the target task is updated in the multidimensional table. The visualization dashboard update module is used to update the target item column in the visualization dashboard based on the updated target multidimensional table when a data update is detected in the target multidimensional table.

[0008] According to another aspect of the present invention, an electronic device is provided, the electronic device comprising: 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, which enables the at least one processor to perform the project automation management method according to any embodiment of the present invention.

[0009] According to another aspect of the present invention, a computer-readable storage medium is provided, the computer-readable storage medium storing computer instructions for causing a processor to execute and implement the project automation management method according to any embodiment of the present invention.

[0010] The technical solution of this invention involves the following steps: When a task collection event is triggered, a task collection card is sent to a first executor, and a new task is created in a multidimensional table based on the task description returned by the first executor through the task collection card; when a task progress maintenance event is triggered, a progress collection card is sent to a second executor based on the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After successful verification, each in-process task in the multidimensional table is updated; when the task status of the target task is detected to be updated to "completed," a scoring and review card is generated and sent to a third executor, who then submits the output link in the scoring and review card. The scoring and review cards are circulated to the auditors, and the target tasks are updated in the multidimensional table based on the audit results filled in by the auditors in the scoring and review cards. When the data update of the target multidimensional table is detected, the target project column in the visualization dashboard is updated according to the updated target multidimensional table. This method enables unified storage and structured management of task information, realizes intelligent and efficient task progress collection, automates the output confirmation process, and provides real-time visualization of task progress. It realizes automated management of the entire project process from task creation to task completion, effectively reduces ineffective communication between the executor and the auditor, and improves project execution efficiency.

[0011] It should be understood that the description in this section is not intended to identify key or essential features of the embodiments of the present invention, nor is it intended to limit the scope of the invention. Other features of the invention will become readily apparent from the following description. Attached Figure Description

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

[0013] Figure 1 This is a flowchart of a project automation management method provided in Embodiment 1 of the present invention; Figure 2 This is a flowchart of another automated project management method provided according to Embodiment 2 of the present invention; Figure 3 This is a schematic diagram of the structure of a project automation management device according to Embodiment 3 of the present invention; Figure 4 This is a schematic diagram of the structure of an electronic device that implements the project automation management method of this invention. Detailed Implementation

[0014] To enable those skilled in the art to better understand the present invention, the technical solutions of the present invention will be clearly and completely described below with reference to the accompanying drawings of the embodiments of the present invention. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort should fall within the scope of protection of the present invention.

[0015] It should be noted that the terms "first," "second," etc., in the specification, claims, and accompanying drawings of this invention are used to distinguish similar objects and are not necessarily used to describe a specific order or sequence. It should be understood that such terms can be used interchangeably where appropriate so that embodiments of the invention described herein can be implemented in orders other than those illustrated or described herein. Furthermore, the terms "comprising" and "having," and any variations thereof, are intended to cover a non-exclusive inclusion; for example, a process, method, system, product, or apparatus that comprises a series of steps or units is not necessarily limited to those steps or units explicitly listed, but may include other steps or units not explicitly listed or inherent to such processes, methods, products, or apparatus.

[0016] Example 1 Figure 1 This is a flowchart of a project automation management method provided in Embodiment 1 of the present invention. This embodiment is applicable to situations where the entire project processing flow is automated. The method can be executed by a project automation management device, which can be implemented in hardware and / or software, and is generally configured in a computer or processor with data processing capabilities. Figure 1 As shown, the method includes: S110. When a task collection event is triggered, a task collection card is sent to the first executor, and a new task is created in the multidimensional table based on the task description returned by the first executor through the task collection card.

[0017] Each multidimensional table is used to maintain task information for a single project.

[0018] Optionally, this solution can be integrated into an enterprise collaboration platform, reusing the platform's user system and data storage, and interacting with users in the form of an intelligent agent, thereby achieving automated management of the entire project process.

[0019] Optionally, a project may include multiple tasks, and the project is considered complete only when all multiple tasks are completed.

[0020] Optionally, a task collection event can refer to a task collection and creation event that is automatically triggered by the system according to preset rules or manually initiated by the user. The task collection event is triggered when either the task batch collection time point is met or a new task request is received.

[0021] Optionally, the first executor can refer to the task executor that needs to submit a new task. If the task collection event is triggered by the task batch collection time point, the first executor can be all task executors within a specified team or enterprise. If the task collection event is triggered by receiving a new task request, the first executor can be the task executor that initiated the new task request. There is no limitation here.

[0022] Optionally, the task collection card is an interactive form card generated based on the message card capabilities of an enterprise collaboration platform, which can be used by the first executor to fill in the task description and upload it.

[0023] Optionally, the task description can be in the form of natural language description, which may include, but is not limited to, information such as task name, executor, task deadline, initial task priority, and the parent task or related subtask of the current task.

[0024] Optionally, a multidimensional table is an online table used for structured storage of all task data for a single project. It is used to manage and maintain multiple information items for each task. Each multidimensional table corresponds to a specified project, and a row in a multidimensional table can maintain multiple information items for one task in that project.

[0025] The multidimensional table can maintain at least the following information items: task name, task priority, executor identifier, task deadline, task progress, output link, review score, task status, and associated tasks.

[0026] Optionally, the task name is a unique identifier for the task. Users can pre-define the task name when sending the task description. If the task name is found to be duplicated when parsing the task description, the user can be prompted to modify it until there is no duplicate task name with other tasks.

[0027] Optionally, task priority is a level field used to characterize the importance and urgency of a task. It can include three levels: high, medium, and low, or it can be customized according to needs. There are no restrictions here.

[0028] Optionally, the executor identifier can be used to uniquely identify the task executor. Information such as user accounts or employee IDs within the enterprise collaboration platform can be directly reused as the executor identifier.

[0029] Optionally, the task deadline can refer to the latest time when the task needs to be completed.

[0030] Optionally, task progress can refer to quantitative data used to characterize the current degree of task completion, which can be expressed as a percentage.

[0031] Optionally, the output link can refer to the address of the deliverable submitted after the task is completed, such as a document link, file link, or deliverable URL (Uniform Resource Locator).

[0032] Optionally, the audit score can refer to the quantitative score given by the auditor for the quality of the task output.

[0033] Optionally, the task status is a stage marker in the entire lifecycle of the task, which may include, but is not limited to: in progress, completed, accepted, and to be improved.

[0034] Optionally, associated tasks can refer to tasks that have a dependency relationship with the recording task. Tasks with a dependency relationship can include parent tasks or child tasks.

[0035] S120. When a task progress maintenance event is triggered, a progress collection card is sent to the second executor according to the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After the verification is successful, each in-process task in the multidimensional table is updated.

[0036] Optionally, a task progress maintenance event can refer to a task progress collection and update event that is automatically triggered by the system according to preset rules or manually initiated by the user. The task collection event is triggered when either the task progress maintenance time point is met or a task progress collection instruction is received.

[0037] Optionally, the second executor can be a task executor that currently has at least one unfinished task. That is, if a task executor currently has at least one unfinished task, it is designated as the second executor, and a progress collection card is sent to it.

[0038] Optionally, the progress collection card is an interactive form card generated based on the message card capability of the enterprise collaboration platform. It can be used by the second executor to fill in and upload task progress information. Each second executor receives a different progress collection card, which contains only all the ongoing tasks of that second executor.

[0039] Optionally, the task progress information may include: the percentage of completion, output links, difficulties encountered during task execution, and subsequent execution plans, etc., which are not limited here.

[0040] Optionally, after parsing the task progress information, a callback event can be triggered to perform an integrity check on the task progress information. After confirming that the integrity check has passed, the content in the multidimensional table can be updated using the parsed task progress information.

[0041] S130. When the target task's status is updated to "completed", a scoring review card is generated and sent to the third executor. The third executor submits the output link in the scoring review card and then forwards the scoring review card to the reviewer. Based on the review results filled in by the reviewer in the scoring review card, the target task is updated in the multidimensional table.

[0042] Optionally, the target task can refer to the task whose current task status has changed from in progress to completed.

[0043] Optionally, the scoring and review card can refer to an integrated process card that is automatically generated when the task is marked as completed. During the third-party completion stage, the scoring and review card only displays the output link input box. During the reviewer completion stage, the output link, scoring input box, and review comment input box can be displayed.

[0044] Optionally, the third executor can be the task executor of the target task. When the third executor updates the task progress of the target task to 100%, the task status of the target task will be automatically updated to "completed".

[0045] Optionally, the reviewer can be an enterprise collaboration platform user with task acceptance authority. The review results filled in by the reviewer in the scoring and review card may include the review score and review comments.

[0046] Optionally, if the review score is greater than the preset score threshold, the task status of the target task in the multidimensional table will be updated from "completed" to "accepted", and the review score will be entered in the review score item of the multidimensional table; if the review score is less than the preset score threshold, the task status of the target task in the multidimensional table will be updated from "completed" to "needs improvement", and the review score will be entered in the review score item of the multidimensional table, and the review comments will be pushed to the third executor.

[0047] S140. When an update to the target multidimensional table is detected, the target item column in the visualization dashboard is updated according to the updated target multidimensional table.

[0048] Optionally, the target multidimensional table can refer to any multidimensional table whose data has been updated.

[0049] Optionally, the visualization dashboard can be generated based on real-time data from multidimensional tables. It can display information such as task progress and overall project progress in various visualization formats, such as overall project progress bars, task status distribution charts, and time-dimensional statistical charts.

[0050] Optionally, the visualization dashboard can display visualization data for different projects through multiple project columns. Project managers or reviewers can select and view the corresponding project columns as needed. Furthermore, each project column can include multiple visualization modules, and each visualization module can display different visualization content.

[0051] Optionally, the target item column is the item column corresponding to the target multidimensional table.

[0052] Specifically, when a data update to the target multidimensional table is detected, the target item column in the visualization dashboard is updated based on the updated target multidimensional table. This may include: When a data update is detected in the target multidimensional table, a data synchronization event is triggered. Based on the updated target multidimensional table, the current progress of the target project is calculated, and an alert level is assigned to each task in the target project. Update the target project column in the visualization dashboard based on the current progress of the target project, the warning level of each task in the target project, and the task progress of each task in the target project.

[0053] Optionally, the overall project schedule can refer to the total project schedule calculated by weighting the progress of all tasks within the project.

[0054] Optionally, the warning level can refer to the risk level automatically matched based on the task deadline. The warning level can include a first warning and a second warning. A first warning can be marked in red on the visualization dashboard, and a second warning can be marked in yellow on the visualization dashboard. Tasks that do not fall within the scope of the first warning or the second warning are not marked separately.

[0055] Optionally, a warning level can be assigned to each task in the target project, which may include any of the following: If the task deadline is determined to be less than the current system time, the task is determined to be overdue, and the warning level for the task is determined to be Level 1 warning. If the current system time is less than 3 days away from the task deadline, the warning level for the task is determined to be Level 2. If the current system time is greater than or equal to 3 days away from the task deadline, the task is determined not to be within the scope of the warning, and no warning level matching is performed for the task.

[0056] Optionally, based on the current progress of the target project, the overall project progress bar in the target project column of the visualization dashboard can be updated, specifically including updating the length of the overall project progress bar and the progress percentage indicated after the overall project progress bar.

[0057] Optionally, based on the warning level of each task in the target project, warning labels can be added to each task in the target project column of the visualization dashboard. Then, based on the warning labels of each task, a task status distribution map can be generated, which can intuitively display information such as the number of tasks corresponding to each warning level.

[0058] Optionally, based on the task progress of each task in the target project, the task progress of each task in the target project column of the visualization dashboard can be marked separately.

[0059] The technical solution of this invention involves the following steps: When a task collection event is triggered, a task collection card is sent to a first executor, and a new task is created in a multidimensional table based on the task description returned by the first executor through the task collection card; when a task progress maintenance event is triggered, a progress collection card is sent to a second executor based on the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After successful verification, each in-process task in the multidimensional table is updated; when the task status of the target task is detected to be updated to "completed," a scoring and review card is generated and sent to a third executor, who then submits the output link in the scoring and review card. The scoring and review cards are circulated to the auditors, and the target tasks are updated in the multidimensional table based on the audit results filled in by the auditors in the scoring and review cards. When the data update of the target multidimensional table is detected, the target project column in the visualization dashboard is updated according to the updated target multidimensional table. This method enables unified storage and structured management of task information, realizes intelligent and efficient task progress collection, automates the output confirmation process, and provides real-time visualization of task progress. It realizes automated management of the entire project process from task creation to task completion, effectively reduces ineffective communication between the executor and the auditor, and improves project execution efficiency.

[0060] Example 2 Figure 2 This is a flowchart illustrating an automated project management method according to Embodiment 2 of the present invention. Based on the above embodiments, this embodiment specifically describes the automated project management method. Figure 2 As shown, the method includes: S210. When a task collection event is triggered, a task collection card is sent to the first executor, and a new task is created in the multidimensional table based on the task description returned by the first executor through the task collection card.

[0061] Specifically, when a task collection event is triggered, a task collection card is sent to the first executor, and a new task is created in a multidimensional table based on the task description returned by the first executor through the task collection card. This may include: When the task batch collection time point is reached or a new task request is received, the task collection event is triggered and a task collection card is sent to the first executor. Extract at least one new task description from the task collection card returned by the first executor, and call the large language model to parse the task description of each new task to obtain the task elements of each new task. Based on the task elements of each new task, determine whether there are any relationships between the new tasks, and perform any of the following: If there is no correlation between the target new task and other new tasks, then the target new task is created in a multidimensional table based on the task elements of the target new task; If there is a relationship between multiple new target tasks, then in each new target task, determine the parent task and child tasks, create the parent task in a multidimensional table based on the task elements of the parent task, and after the parent task is created, create the child tasks in batches in the multidimensional table based on the task elements of each child task, and establish the relationship between the parent task and each child task.

[0062] Optionally, the task batch collection time point can be specified in advance. For example, the first working day of each month or 10:00 AM of every Monday can be specified as the task batch collection time point. There is no limitation here. If the task collection event is determined to be triggered when the task batch collection time point is reached, then the first executor is all task executors within the specified user scope.

[0063] Optionally, a new task request can be initiated by any task executor. The task executor can directly input a natural language description of the task to be created into the intelligent agent used for project automation management within the enterprise collaboration platform. The intelligent agent can call the AI ​​task parsing engine to parse the natural language description of the task executor. When it is determined that the natural language description sent by the task executor matches the new task request, the task executor that initiated the new task request is identified as the first executor, and a task collection card is sent to it.

[0064] Optionally, the first executor can submit multiple new tasks at once in the task collection card, providing a task description for each new task. The AI ​​task parsing engine can be called to parse the task descriptions of each new task and extract the task elements of each new task.

[0065] Optionally, task elements can refer to the structured information extracted from the task description by the AI ​​task parsing engine. Task elements may include information such as task name, executor identifier, task deadline, initial priority, and task relationships.

[0066] Optionally, the target new task can be a new task for which task association is currently being determined. If there is no association between the target new task and other new tasks currently added by the first executor, the target new task is created directly in the multidimensional table, and multiple information items of the target new task are filled in the multidimensional table according to the task elements of the target new task.

[0067] Optionally, if the target new task has no relationship with other new tasks, but has a relationship with an already created task, then after creating the target new task in the multidimensional table, you can mark the relationship between the target new task and the already created task.

[0068] Optionally, if there is a relationship between multiple new target tasks, then based on the description of the task relationship in the task elements, determine the parent task and child tasks among the multiple new target tasks, and first create the parent task in the multidimensional table, then fill in the information items of the parent task according to the task elements of the parent task, then create the child tasks in batches, fill in the information items of each child task according to the task elements of each child task, and finally establish the relationship between each child task and the parent task.

[0069] Optionally, a parent task can contain multiple child tasks, and the completion status of the child tasks will affect the overall progress of the parent task.

[0070] S220. When a task progress maintenance event is triggered, a progress collection card is sent to the second executor according to the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After the verification is successful, each in-process task in the multidimensional table is updated.

[0071] Specifically, when a task progress maintenance event is triggered, a progress collection card is sent to the second executor based on the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After successful verification, the in-process tasks in the multidimensional table are updated, which may include: When the task progress maintenance time point is reached or a task progress collection instruction is received, the task progress maintenance event is triggered, and the tasks in progress are identified based on the current task status of each task in the multidimensional table. Based on the deadlines of ongoing tasks, the priorities of ongoing tasks are updated in the multidimensional table, and each ongoing task is grouped according to its executor. Based on the multidimensional table, generate progress collection cards corresponding to each task group, and send each progress collection card to the corresponding second executor. Upon receiving task progress information returned by the second executor through the progress collection card, perform an integrity check on the task progress information and execute any of the following: If the verification is successful, the multidimensional table is updated according to the task progress information, and a confirmation message is returned to the second executor. If the verification fails, an error message is returned to the second executor.

[0072] Optionally, the task progress maintenance time point can be specified in advance, such as maintaining the task progress once a week; the task progress collection instruction can be sent by the administrator or the reviewer, which can be understood as the administrator needing to obtain the current task progress of all task executors in batches.

[0073] Optionally, the second executor is all task executors with tasks in progress, and the tasks in progress are those whose current task status is in progress in the multidimensional table.

[0074] Optionally, in-process tasks can be grouped according to their respective executors, with each task group corresponding to a unique task executor.

[0075] Optionally, the priority of the tasks in progress can be updated in the multidimensional table based on their deadlines. This can include: determining whether the deadline of the task in progress is the current calendar day based on the task's deadline and the current system time; if so, updating the priority of the task in progress to a higher priority in the multidimensional table; otherwise, keeping the original priority of the task in progress unchanged.

[0076] Optionally, progress collection cards can be generated by task group. The progress collection card can include a task progress reporting area, an output link reporting area, and optional reporting areas such as risk points and remarks for each ongoing task. The priority of each ongoing task in the task group can also be marked according to the priority-updated multidimensional table.

[0077] Optionally, after generating the progress collection cards, the progress collection cards can be sent in batches to the corresponding second executor.

[0078] Optionally, after receiving the task progress information returned by the second executor through the progress collection card, the task progress information is parsed to determine whether the information items filled in the task progress information can cover the preset required information items; if so, the integrity check is passed; otherwise, the integrity check is not passed.

[0079] Optionally, if the integrity check passes, the information items contained in the progress information are synchronized to the multidimensional table, and the multidimensional table is updated; if the integrity check fails, a clear error message is returned to the second executor, guiding the second executor to resubmit.

[0080] Optionally, the task progress collection instruction can also be sent by any task executor. In this case, it can be understood that a task executor is currently processing a task that has made some progress and needs to actively submit the task progress. The second executor is the task executor that currently sends the task collection instruction.

[0081] Optionally, if a task progress maintenance event is triggered by a task progress collection instruction sent by a specified task executor, the ongoing task corresponding to the task executor can be directly identified through a multidimensional table, and a progress collection card can be generated for the task executor. Compared with batch task progress collection, this reduces one task grouping operation.

[0082] S230. When the target task's status is updated to "completed", a scoring review card is generated and sent to the third executor. The third executor submits the output link in the scoring review card and then forwards the scoring review card to the reviewer. Based on the review results filled in by the reviewer in the scoring review card, the target task is updated in the multidimensional table.

[0083] The updating of the target task in the multidimensional table based on the review results filled in by the reviewer in the scoring review card may include: Based on the audit results filled in by the auditor in the scoring review card, obtain the audit score and audit comments, and determine whether the audit score is greater than the preset standard score; If so, a notification of approval is sent to the third executor, and the task status of the target task is updated to "accepted" in the multidimensional table; If not, the review comments will be sent to the third executor, and the task status of the target task will be updated to "to be improved" in the multidimensional table.

[0084] Optionally, if the task status of the target task is updated to "accepted", it means that the task has passed the review and can be officially closed; if the task status of the target task is updated to "to be improved", it means that the target task has entered the rework state and needs to be modified and resubmitted for acceptance.

[0085] S240. When a data update is detected in the target multidimensional table, a data synchronization event is triggered. Based on the updated target multidimensional table, the current progress of the target project is calculated, and a warning level is matched for each task in the target project.

[0086] S250. Update the target project column in the visualization dashboard based on the current progress of the target project, the warning level of each task in the target project, and the task progress of each task in the target project.

[0087] The automated project management method may further include: If any data update of any multidimensional table is detected, then based on each multidimensional table, determine the total number of tasks, the total number of completed tasks, and the total number of incomplete tasks under multiple time dimensions; The calendar bar in the visualization dashboard is updated based on the total number of tasks, the total number of completed tasks, and the total number of incomplete tasks across multiple time dimensions.

[0088] Optionally, multiple time dimensions can refer to the statistical dimensions preset by the system, which may include time dimensions such as day, week, month, quarter, and year.

[0089] Optionally, the calendar bar can serve as a global statistics module in a visualization dashboard, displaying the task distribution and completion status of a specified project at different time points in a calendar view, so that managers or auditors can view the overall workload and task completion status of the project from a global perspective.

[0090] Optionally, it may also include: when the task reminder time point is reached, determining to trigger the task reminder event, and determining the tasks to be reminded within the preset reminder period based on the current task status and deadline of each task in the multidimensional table; Based on the multidimensional table, generate task reminder cards corresponding to each group of tasks to be reminded, and send each task reminder card to the corresponding fourth executor.

[0091] Optionally, the task reminder time can be a fixed time for each calendar day or workday, such as 8:00 AM. The task reminder event can be used to push the task to be reminded to the corresponding executor in the form of a task reminder card.

[0092] Optionally, the preset reminder period can be set according to the average task completion time, such as 3 days, 1 day, etc., without limitation here.

[0093] Optionally, a task to be reminded can refer to a task that is currently incomplete and whose deadline is within the reminder period.

[0094] Optionally, the task reminder card may include information such as the task identifier and deadline of the task to be reminded.

[0095] Optionally, the fourth executor can refer to the executor corresponding to the task to be reminded.

[0096] The technical solution of this invention involves the following steps: When a task collection event is triggered, a task collection card is sent to a first executor, and a new task is created in a multidimensional table based on the task description returned by the first executor through the task collection card; when a task progress maintenance event is triggered, a progress collection card is sent to a second executor based on the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After successful verification, each in-process task in the multidimensional table is updated; when the task status of the target task is detected to be updated to "completed," a scoring and review card is generated and sent to a third executor, who then submits the output link in the scoring and review card. The scoring and review cards are circulated to the auditors, and the target tasks are updated in the multidimensional table based on the audit results filled in by the auditors in the scoring and review cards. When the data update of the target multidimensional table is detected, the target project column in the visualization dashboard is updated according to the updated target multidimensional table. This method enables unified storage and structured management of task information, realizes intelligent and efficient task progress collection, automates the output confirmation process, and provides real-time visualization of task progress. It realizes automated management of the entire project process from task creation to task completion, effectively reduces ineffective communication between the executor and the auditor, and improves project execution efficiency.

[0097] Example 3 Figure 3 This is a schematic diagram of a project automation management device provided in Embodiment 3 of the present invention. Figure 3 As shown, the device includes: a new task creation module 310, a task progress update module 320, a task review module 330, and a visual dashboard update module 340.

[0098] The new task creation module 310 is used to send a task collection card to the first executor when a task collection event is triggered, and to create a new task in a multidimensional table based on the task description returned by the first executor through the task collection card; wherein each multidimensional table is used to maintain task information for a single project.

[0099] The task progress update module 320 is used to send a progress collection card to the second executor according to the multidimensional table when a task progress maintenance event is triggered, and to verify the task progress information returned by the second executor through the progress collection card. After the verification is successful, the module updates each in-process task in the multidimensional table.

[0100] The task review module 330 is used to generate a score review card and send it to the third executor when the task status of the target task is updated to the completed status. After the third executor submits the output link in the score review card, the score review card is transferred to the reviewer. Based on the review results filled in by the reviewer in the score review card, the target task is updated in the multidimensional table.

[0101] The visualization dashboard update module 340 is used to update the target item column in the visualization dashboard according to the updated target multidimensional table when a data update of the target multidimensional table is detected.

[0102] The technical solution of this invention involves the following steps: When a task collection event is triggered, a task collection card is sent to a first executor, and a new task is created in a multidimensional table based on the task description returned by the first executor through the task collection card; when a task progress maintenance event is triggered, a progress collection card is sent to a second executor based on the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After successful verification, each in-process task in the multidimensional table is updated; when the task status of the target task is detected to be updated to "completed," a scoring and review card is generated and sent to a third executor, who then submits the output link in the scoring and review card. The scoring and review cards are circulated to the auditors, and the target tasks are updated in the multidimensional table based on the audit results filled in by the auditors in the scoring and review cards. When the data update of the target multidimensional table is detected, the target project column in the visualization dashboard is updated according to the updated target multidimensional table. This method enables unified storage and structured management of task information, realizes intelligent and efficient task progress collection, automates the output confirmation process, and provides real-time visualization of task progress. It realizes automated management of the entire project process from task creation to task completion, effectively reduces ineffective communication between the executor and the auditor, and improves project execution efficiency.

[0103] Based on the above embodiments, the new task creation module 310 can be specifically used for: When the task batch collection time point is reached or a new task request is received, the task collection event is triggered and a task collection card is sent to the first executor. Extract at least one new task description from the task collection card returned by the first executor, and call the large language model to parse the task description of each new task to obtain the task elements of each new task. Based on the task elements of each new task, determine whether there are any relationships between the new tasks, and perform any of the following: If there is no correlation between the target new task and other new tasks, then the target new task is created in a multidimensional table based on the task elements of the target new task; If there is a relationship between multiple new target tasks, then in each new target task, determine the parent task and child tasks, create the parent task in a multidimensional table based on the task elements of the parent task, and after the parent task is created, create the child tasks in batches in the multidimensional table based on the task elements of each child task, and establish the relationship between the parent task and each child task.

[0104] Based on the above embodiments, the task progress update module 320 can be specifically used for: When the task progress maintenance time point is reached or a task progress collection instruction is received, the task progress maintenance event is triggered, and the tasks in progress are identified based on the current task status of each task in the multidimensional table. Based on the deadlines of ongoing tasks, the priorities of ongoing tasks are updated in the multidimensional table, and each ongoing task is grouped according to its executor. Based on the multidimensional table, generate progress collection cards corresponding to each task group, and send each progress collection card to the corresponding second executor. Upon receiving task progress information returned by the second executor through the progress collection card, perform an integrity check on the task progress information and execute any of the following: If the verification is successful, the multidimensional table is updated according to the task progress information, and a confirmation message is returned to the second executor. If the verification fails, an error message is returned to the second executor.

[0105] Based on the above embodiments, the task review module 330 can be specifically used for: Based on the audit results filled in by the auditor in the scoring review card, obtain the audit score and audit comments, and determine whether the audit score is greater than the preset standard score; If so, a notification of approval is sent to the third executor, and the task status of the target task is updated to "accepted" in the multidimensional table; If not, the review comments will be sent to the third executor, and the task status of the target task will be updated to "to be improved" in the multidimensional table.

[0106] Based on the above embodiments, the visualization dashboard update module 340 can be specifically used for: When a data update is detected in the target multidimensional table, a data synchronization event is triggered. Based on the updated target multidimensional table, the current progress of the target project is calculated, and an alert level is assigned to each task in the target project. Update the target project column in the visualization dashboard based on the current progress of the target project, the warning level of each task in the target project, and the task progress of each task in the target project.

[0107] Based on the above embodiments, a visual calendar bar update module may also be included, for: If any data update of any multidimensional table is detected, then based on each multidimensional table, determine the total number of tasks, the total number of completed tasks, and the total number of incomplete tasks under multiple time dimensions; The calendar bar in the visualization dashboard is updated based on the total number of tasks, the total number of completed tasks, and the total number of incomplete tasks across multiple time dimensions.

[0108] Based on the above embodiments, the multidimensional table maintains at least the following information items: Task name, task priority, executor identifier, task deadline, task progress, output link, review score, task status, and related tasks.

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

[0110] Example 4 Figure 4 A schematic diagram of an electronic device 10, which can be used to implement embodiments 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 can also represent various forms of mobile devices, such as personal digital processors, cellular phones, smartphones, wearable devices (e.g., helmets, glasses, watches, etc.), and other similar computing devices. The components shown herein, their connections and relationships, and their functions are merely illustrative and are not intended to limit the implementation of the invention described and / or claimed herein.

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

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

[0113] Processor 11 can be various general-purpose and / or special-purpose processing components with processing and computing capabilities. Some examples of processor 11 include, but are not limited to, central processing unit (CPU), graphics processing unit (GPU), various special-purpose artificial intelligence (AI) computing chips, various processors running machine learning model algorithms, digital signal processors (DSPs), and any suitable processor, controller, microcontroller, etc. Processor 11 performs the various methods and processes described above, such as the project automation management method described in the embodiments of the present invention. That is: When a task collection event is triggered, a task collection card is sent to the first executor, and a new task is created in a multidimensional table based on the task description returned by the first executor through the task collection card; wherein, each multidimensional table is used to maintain task information for a single item; When a task progress maintenance event is triggered, a progress collection card is sent to the second executor according to the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After the verification is successful, each in-process task in the multidimensional table is updated. When the target task's status is updated to "completed", a scoring review card is generated and sent to the third executor. After the third executor submits the output link in the scoring review card, the scoring review card is transferred to the reviewer. Based on the review results filled in by the reviewer in the scoring review card, the target task is updated in the multidimensional table. When an update to the target multidimensional table is detected, the target item column in the visualization dashboard is updated based on the updated target multidimensional table.

[0114] In some embodiments, the project automation management method may be implemented as a computer program tangibly contained in a computer-readable storage medium, such as storage unit 18. In some embodiments, part or all of the computer program may 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 automation management method described above may be performed. Alternatively, in other embodiments, processor 11 may be configured to perform the project automation management method by any other suitable means (e.g., by means of firmware).

[0115] Various embodiments of the systems and techniques described above 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-a-chip (SoCs), complex programmable logic devices (CPLDs), computer hardware, firmware, software, and / or combinations thereof. These various embodiments may include implementations in one or more computer programs that can be executed and / or interpreted on a programmable system including at least one programmable processor, which may be a dedicated or general-purpose programmable processor, capable of receiving data and instructions from a storage system, at least one input device, and at least one output device, and transmitting data and instructions to the storage system, the at least one input device, and the at least one output device.

[0116] Computer programs used to implement the methods of the present invention may be written in any combination of one or more programming languages. These computer programs may 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 cause the functions / operations specified in the flowcharts and / or block diagrams to be performed. The computer programs may be executed entirely on a machine, partially on a machine, or as a standalone software package, partially on a machine and partially on a remote machine, or entirely on a remote machine or server.

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

[0118] 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 provides input to the electronic device. Other types of devices can also be used to provide interaction with the user; for example, 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 sound input, voice input, or tactile input).

[0119] The systems and technologies described herein can be implemented in computing systems that include backend components (e.g., as data servers), or middleware components (e.g., application servers), or frontend components (e.g., user computers with graphical user interfaces or web browsers through which users can interact with implementations of the systems and technologies described herein), or any combination of such backend, middleware, or frontend components. The components of the system can be interconnected via digital data communication of any form or medium (e.g., communication networks). Examples of communication networks include local area networks (LANs), wide area networks (WANs), blockchain networks, and the Internet.

[0120] A computing system can include clients and servers. Clients and servers are generally located far apart and typically interact through communication networks. The client-server relationship is created by computer programs running on the respective computers and having a client-server relationship with each other. The server can be a cloud server, also known as a cloud computing server or cloud host, which is a hosting product within the cloud computing service system to address the shortcomings of traditional physical hosts and VPS services, such as high management difficulty and weak business scalability.

[0121] It should be understood that the various forms of processes shown above can be used, with steps reordered, added, or deleted. For example, the steps described in this invention can be executed in parallel, sequentially, or in different orders, as long as the desired result of the technical solution of this invention can be achieved, and this is not limited herein.

[0122] The specific embodiments described above do not constitute a limitation on the scope of protection of this invention. Those skilled in the art should understand that various modifications, combinations, sub-combinations, and substitutions can be made according to design requirements and other factors. Any modifications, equivalent substitutions, and improvements made within the spirit and principles of this invention should be included within the scope of protection of this invention.

Claims

1. A method for automated project management, characterized in that, include: When a task collection event is triggered, a task collection card is sent to the first executor, and a new task is created in a multidimensional table based on the task description returned by the first executor through the task collection card; wherein, each multidimensional table is used to maintain task information for a single item; When a task progress maintenance event is triggered, a progress collection card is sent to the second executor according to the multidimensional table, and the task progress information returned by the second executor through the progress collection card is verified. After the verification is successful, each in-process task in the multidimensional table is updated. When the target task's status is updated to "completed", a scoring review card is generated and sent to the third executor. After the third executor submits the output link in the scoring review card, the scoring review card is transferred to the reviewer. Based on the review results filled in by the reviewer in the scoring review card, the target task is updated in the multidimensional table. When an update to the target multidimensional table is detected, the target item column in the visualization dashboard is updated based on the updated target multidimensional table.

2. The method according to claim 1, characterized in that, When a task collection event is triggered, a task collection card is sent to the first executor, and a new task is created in a multidimensional table based on the task description returned by the first executor through the task collection card, including: When the task batch collection time point is reached or a new task request is received, the task collection event is triggered and a task collection card is sent to the first executor. Extract at least one new task description from the task collection card returned by the first executor, and call the large language model to parse the task description of each new task to obtain the task elements of each new task. Based on the task elements of each new task, determine whether there are any relationships between the new tasks, and perform any of the following: If there is no correlation between the target new task and other new tasks, then the target new task is created in a multidimensional table based on the task elements of the target new task; If there is a relationship between multiple new target tasks, then in each new target task, determine the parent task and child tasks, create the parent task in a multidimensional table based on the task elements of the parent task, and after the parent task is created, create the child tasks in batches in the multidimensional table based on the task elements of each child task, and establish the relationship between the parent task and each child task.

3. The method according to claim 1, characterized in that, When a task progress maintenance event is triggered, a progress collection card is sent to the second executor based on the multidimensional table. The task progress information returned by the second executor through the progress collection card is verified. After successful verification, each in-process task in the multidimensional table is updated, including: When the task progress maintenance time point is reached or a task progress collection instruction is received, the task progress maintenance event is triggered, and the tasks in progress are identified based on the current task status of each task in the multidimensional table. Based on the deadlines of ongoing tasks, the priorities of ongoing tasks are updated in the multidimensional table, and each ongoing task is grouped according to its executor. Based on the multidimensional table, generate progress collection cards corresponding to each task group, and send each progress collection card to the corresponding second executor. Upon receiving task progress information returned by the second executor through the progress collection card, perform an integrity check on the task progress information and execute any of the following: If the verification is successful, the multidimensional table is updated according to the task progress information, and a confirmation message is returned to the second executor. If the verification fails, an error message is returned to the second executor.

4. The method according to claim 1, characterized in that, Based on the review results filled in by the reviewer on the scoring review card, the target task is updated in the multidimensional table, including: Based on the audit results filled in by the auditor in the scoring review card, obtain the audit score and audit comments, and determine whether the audit score is greater than the preset standard score; If so, a notification of approval is sent to the third executor, and the task status of the target task is updated to "accepted" in the multidimensional table; If not, the review comments will be sent to the third executor, and the task status of the target task will be updated to "to be improved" in the multidimensional table.

5. The method according to claim 1, characterized in that, When an update to the target multidimensional table is detected, the target item columns in the visualization dashboard are updated based on the updated target multidimensional table, including: When a data update is detected in the target multidimensional table, a data synchronization event is triggered. Based on the updated target multidimensional table, the current progress of the target project is calculated, and an alert level is assigned to each task in the target project. Update the target project column in the visualization dashboard based on the current progress of the target project, the warning level of each task in the target project, and the task progress of each task in the target project.

6. The method according to claim 1, characterized in that, Also includes: If any data update of any multidimensional table is detected, then based on each multidimensional table, determine the total number of tasks, the total number of completed tasks, and the total number of incomplete tasks under multiple time dimensions; The calendar bar in the visualization dashboard is updated based on the total number of tasks, the total number of completed tasks, and the total number of incomplete tasks across multiple time dimensions.

7. The method according to any one of claims 1-6, characterized in that, The multidimensional table must maintain at least the following information items: Task name, task priority, executor identifier, task deadline, task progress, output link, review score, task status, and related tasks.

8. A project automation management device, characterized in that, include: The new task creation module is used to send a task collection card to the first executor when a task collection event is triggered, and to create a new task in a multidimensional table based on the task description returned by the first executor through the task collection card; wherein each multidimensional table is used to maintain task information for a single project; The task progress update module is used to send a progress collection card to the second executor according to the multidimensional table when a task progress maintenance event is triggered, and to verify the task progress information returned by the second executor through the progress collection card. After the verification is successful, the module updates each in-process task in the multidimensional table. The task review module is used to generate a score review card and send it to the third executor when the task status of the target task is updated to the completed status. After the third executor submits the output link in the score review card, the score review card is transferred to the reviewer. Based on the review results filled in by the reviewer in the score review card, the target task is updated in the multidimensional table. The visualization dashboard update module is used to update the target item column in the visualization dashboard based on the updated target multidimensional table when a data update is detected in the target multidimensional table.

9. An electronic device, characterized in that, The electronic device includes: 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 being executed by the at least one processor to enable the at least one processor to perform the project automation management method according to any one of claims 1-7.

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

Images