Task-driven engine system

Abstract

The invention relates to a task-driven engine system, and belongs to the technical field of task management. The business architecture of the system comprises a task configuration layer, a task execution layer and a task statistics layer, the task configuration layer completes classification of various tasks and customization of task templates through modules in the task configuration layer, the task execution layer completes issuing, execution and tracking of the tasks through modules in the task execution layer, and the task statistics layer completes analysis and statistics of the tasks. According to the method, task driving is taken as a core, a customized task template is created, task detail contents are clarified, complex work is granulated, a complicated process is detailed, issuing, execution, tracking, reminding and statistical closed-loop management are realized, work items are prevented from being missed, an item which should be made at present is quickly and accurately found in fixed time, the time management capability of a user is improved, and the user experience is improved. The workload is reduced, the working quality is improved, and the working efficiency is enhanced.

Description

Technical Field

[0001] The present invention relates to the technical field of task management, and in particular to a task driving engine system. Background Art

[0002] At present, all kinds of information systems such as project management, business management, and process management are based on business management to carry out various information operations. Such systems built with business management as the core make it difficult for users to intuitively and effectively combine the functions of the system with daily work, which is not conducive to users' work planning and time arrangement. Especially when users are faced with multiple business systems or complex business workflows, they need to compare data across systems, sort out various work items, confirm the urgency of the work, and then enter each system to carry out business processing. With the increasing number of information systems, the workload of users facing these systems will gradually increase accordingly, affecting the efficiency of users' use of information systems and thus affecting the quality of work.

[0003] That is, there are technical problems such as heavy usage burden and low work efficiency when users currently use the management system. Summary of the invention

[0004] In view of the above technical problems, the present invention provides a task-driven engine system to solve the technical problems of heavy usage burden and low work efficiency when users currently use the management system.

[0005] In a first aspect, the present invention provides a task-driven engine system, wherein the business architecture of the task-driven engine system includes a task configuration layer, a task execution layer, and a task statistics layer; The task configuration layer includes a task type module and a task template module. The task type module is used to complete the management and configuration of task types and classify different types of tasks to determine the task type. The task template module is used to customize the task template according to the task type. The task execution layer includes a task publishing module, a task execution module and a progress tracking module. The task publishing module is used to publish corresponding tasks according to work items. The task execution module is used to complete task viewing, task filling, task submission and task splitting according to the current user's to-be-executed task list. The progress tracking module is used to track the task execution status according to the task list, count completed, in-progress and unfinished tasks, complete task inspection, task supervision and task reminder; The task statistics layer is used to complete task statistics, task execution analysis statistics, and construct an energy map corresponding to the task according to the type, template, and time dimension of the task to determine the distribution of energy expended by the current user in completing the task.

[0006] Optionally, the task types include standard type, data type, transaction type and business type; the customized content of the task template includes task type, priority, task content and task configuration items.

[0007] Optionally, the task execution layer further includes a task calendar module and a mobile application module, and the task configuration layer further includes an early warning strategy module; The task calendar module is used to construct a calendar chart of published or received tasks, showing the details of the published or received tasks; The mobile application module is used to provide users with mobile terminal query statistics functions, and the mobile terminal query statistics functions include task calendar, task execution, progress tracking, and energy map; The warning strategy module is used to define the reminder content of the task and determine the reminder strategy for the task during the process of task creation, expiration, overdue, withdrawal or closing.

[0008] Optionally, the reminder strategy includes a reminder form, a reminder frequency, and a reminder trigger condition, and the reminder form includes a text message reminder and an email reminder.

[0009] Optionally, corresponding to the business architecture, the application architecture of the task-driven engine system includes a basic service layer, a business management layer and a visualization layer; The business management layer is constructed based on other modules in the business architecture except the mobile application module; The visualization layer includes a desktop application module and a mobile application module in the business architecture. The desktop application module is used to provide users with a task publishing function and a desktop query and statistics function. The desktop query and statistics function includes task execution, progress tracking and task statistics. The basic service layer includes data storage services, file storage services, system integration services, SMS platforms and email systems.

[0010] Optionally, the task-driven engine system is constructed using front-end and back-end separation technology.

[0011] Optionally, the technical architecture of the task-driven engine system includes a security protection layer, an infrastructure layer, a business service layer, and a presentation layer; The security protection layer includes security management, security protection, data encryption and security monitoring functions; the infrastructure layer is built on a cloud platform and provides set cloud services for preset types of data sources; the business service layer is used to determine its service type based on the business architecture; the display methods of the display layer include web interface, mobile application and visual data display, and provide interface services.

[0012] Optionally, the preset type of data source includes a relational database, an in-memory database, an object storage service data, and an application server data, and the set cloud service includes a cloud server service, a load balancing service, a cloud hard disk service, and an elastic scaling service.

[0013] Optionally, the service types include task configuration service, task execution service, task statistics service, in-site message service, SMS notification service and email notification service.

[0014] Optionally, the technical architecture of the task-driven engine system also includes a microservice gateway, a microservice configuration center, and a microservice registration center; The presentation layer is connected to the business service layer through the microservice gateway, and the configuration of the microservice gateway is completed based on the microservice configuration center. The user sends a registration request for the microservice to the microservice registration center through the interface service of the presentation layer to complete the call of the service provided by the business service layer.

[0015] The above scheme has the following beneficial effects: The task-driven engine system of the present invention takes task-driven as the core and creates customized task templates. It can clearly define the publisher of the task, the content of the task, the executor of the task, the planned completion time of the task, etc. It can granulate complex work and detail complicated processes, realize closed-loop management of publishing, execution, tracking, reminders, and statistics, prevent omissions of work items, and quickly and accurately find the things that should be done most at a fixed time, thereby improving users' time management capabilities, reducing workloads, improving work quality, and enhancing work efficiency. BRIEF DESCRIPTION OF THE DRAWINGS

[0016] Figure 1 is a schematic diagram of the business architecture of a task-driven engine system provided by an embodiment of the present invention; Figure 2 is a schematic diagram of an application architecture of a task-driven engine system provided by another embodiment of the present invention; Figure 3 It is a schematic diagram of a front-end and back-end separation technology provided by a preferred embodiment of the present invention; Figure 4 It is a technical architecture diagram of a task-driven engine system provided by yet another embodiment of the present invention. DETAILED DESCRIPTION

[0017] In order to make the technical problems, technical solutions and beneficial effects solved by the present invention more clearly understood, the present invention is further described in detail below in conjunction with the accompanying drawings and embodiments.

[0018] It should be understood that the embodiments set forth below represent the necessary information to enable those skilled in the art to implement the embodiments and illustrate the best mode for implementing the embodiments. After reading the following description in light of the accompanying drawings, those skilled in the art will understand the concepts of the present disclosure and will recognize applications of these concepts not specifically mentioned herein. It should be understood that these concepts and applications fall within the scope of the present disclosure and the appended claims.

[0019] It should also be understood that, although the terms first, second, etc. may be used herein to describe various elements, these elements should not be limited by these terms. These terms are only used to distinguish one element from another element. For example, the first element may be referred to as the second element, and similarly, the second element may be referred to as the first element without departing from the scope of the present disclosure. As used herein, the term "and / or" includes any and all combinations of one or more related listed items.

[0020] It should also be understood that when an element is referred to as being "connected" or "coupled" to another element, it can be directly connected or coupled to the other element, or intervening elements may be present. Conversely, when an element is referred to as being "directly connected" or "directly coupled" to another element, there are no intervening elements.

[0021] It should also be understood that the terms "upper", "lower", "left", "right", "front", "back", "bottom", "middle", "middle", "top", etc. may be used herein to describe various elements, and the indicated orientation or position relationship is based on the orientation or position relationship shown in the accompanying drawings, which is only for the convenience of describing the present invention and simplifying the description, and does not indicate or imply that the referred device or element must have a specific orientation, be constructed and operated in a specific orientation, and therefore these elements should not be limited by these terms.

[0022] These terms are only used to distinguish one element from another element. For example, a first element can be referred to as an "upper" element, and similarly, a second element can be referred to as an "upper" element according to the relative orientation of these elements without departing from the scope of the present disclosure.

[0023] It is further understood that the terms “comprises,” “includes,” “including” and / or “comprising” when used herein specify the presence of stated features, integers, steps, operations, elements and / or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components and / or groups thereof.

[0024] Unless otherwise defined, all terms (including technical and scientific terms) used herein have the same meaning as commonly understood by one of ordinary skill in the art to which the present disclosure belongs. It will be further understood that the terms used herein should be interpreted as having a meaning consistent with their meaning in the context of this specification and the relevant technology, and will not be interpreted in an idealized or overly formal sense unless explicitly defined as such herein.

[0025] In one embodiment, a task-driven engine system is provided, which implements the functions of task classification, template, warning, release, execution, tracking, statistics, etc., and its business architecture is as follows: Figure 1 shown.

[0026] In the process of building a management system, the business architecture is the foundation for building the application architecture, data architecture, and technical architecture. Therefore, this embodiment first builds the business architecture in task management based on the task-driven purpose. The business architecture of the task-driven engine system is as follows: Figure 1 The shown layer includes the task configuration layer, the task execution layer and the task statistics layer.

[0027] The task configuration layer includes a task type module and a task template module, and preferably also includes an early warning strategy module to improve the accuracy of task management.

[0028] The task type module is used to complete the management and configuration of task types, define the management characteristics, management processes, and business features of tasks, and classify different types of tasks to determine the task types. Task types include standard, data-based, transactional, and business types. The task template module is used to customize the task template according to the task type. The task template customization includes the task type, template authority, i.e., priority, task content, business configuration items, etc., and defines applicable task templates for different work management contents, i.e., task types. The task template is the basic parameter when the task is initiated, and different tasks correspond to specific task templates; The warning strategy module is used to define the reminder content of the task to complete the warning definition, and then determine the reminder strategy for the task during the task creation, expiration, overdue, withdrawal or closure process. The reminder strategy includes the reminder form, reminder number, reminder trigger conditions, etc. The reminder form includes but is not limited to SMS reminders and email reminders.

[0029] The task execution layer includes a task publishing module, a task execution module and a progress tracking module. In order to improve the convenience and efficiency of task management, it preferably also includes a task calendar module and a mobile application module.

[0030] The task publishing module is used to publish corresponding tasks according to specific work items through the publishing interface and form a task list. You can select task templates, executors, task contents, early warning strategies, etc. The task execution module is used to display the task list to be executed by the current user, and complete task execution related processing such as task viewing, task filling, task submission and task splitting according to the task list to be executed by the current user; The progress tracking module is used to track the task execution status according to the task list, count the completed, in-progress and unfinished tasks, complete task inspection, task supervision and task reminders. In order to improve the efficiency of progress tracking management, it is preferred to determine the task list corresponding to each task type and track the task execution status based on the task list under each task type; The task calendar module is used to display the calendar of published or received tasks, so that users can clearly understand the distribution of tasks and display the details of the published or received tasks. The task calendar is displayed in the form of a calendar chart to show the date plan for the current month. In the task calendar, the number of tasks on each date is displayed based on the distribution of tasks. According to the current date, unfinished tasks and overdue tasks are displayed in red in the planned completion date, tasks that are about to expire are displayed in yellow, tasks that are due for execution are displayed in gray, and completed tasks are displayed in green. The number of tasks is indicated by numbers. The task list can be displayed when the mouse is hovered. Click to display the task list, and you can open a specific task to view or execute related tasks. The task calendar can be divided into published tasks / received tasks, which display tasks that need to be tracked or executed from different roles. The mobile application module is used to provide mobile terminal query and statistical functions, including task calendar, task execution, progress tracking, energy map and other query functions.

[0031] The task statistics layer is used to complete task statistics, task execution analysis statistics, and energy map construction. It performs multi-dimensional analysis on tasks such as type, template, and time, determines the distribution of energy spent by the current user in completing the task, and displays the work to which the user's energy is mainly applied, helping users to monitor their energy allocation in a timely manner.

[0032] The task-driven engine system of this embodiment adopts a modular and componentized design concept, dividing different functions into independent modules or components. These modules or components communicate and collaborate through standardized interfaces to form a complete and flexible task-driven engine system. This design not only improves the scalability and maintainability of the system, but also reduces the coupling degree of the system and improves the overall performance.

[0033] Corresponding to the above business architecture of the task-driven engine system, such as Figure 2 As shown, in another embodiment, an application architecture of a task-driven engine system is provided. The application architecture of the task-driven engine system includes a basic service layer, a business management layer, and a visualization layer.

[0034] The business management layer is constructed based on other modules in the business architecture except the mobile application module; The visualization layer includes a desktop application module and a mobile application module in the business architecture. The desktop application module is used to provide users with a task publishing function and a desktop query and statistics function. The desktop query and statistics function includes task execution, progress tracking and task statistics. The basic service layer includes data storage services, file storage services, system integration services, SMS platforms and email systems.

[0035] In a preferred embodiment, the task-driven engine system of this embodiment is as follows Figure 3 It is built using front-end and back-end separation technology, so that the front-end and back-end can be developed and deployed independently, thereby improving the development efficiency and application flexibility of the task-driven engine system.

[0036] And, corresponding to the above business architecture of the task-driven engine system, such as Figure 4 As shown, in yet another embodiment, an overall technical architecture of a task-driven engine system is provided. The overall technical architecture of the task-driven engine system includes a security protection layer, an infrastructure layer, a business service layer, and a presentation layer.

[0037] The security protection layer includes security management, security protection, data encryption and security monitoring functions; The infrastructure layer is developed and built based on the cloud platform, and the connected data source provides set cloud services for the preset type of data source. Figure 4 The data sources of the preferred preset types include relational databases (MySql), memory databases (Redis), OBS file storage service data, i.e., object storage service data, and application server data based on Tomcat, and the preferred cloud services include cloud server services (ECS), load balancing services (ELB), cloud disk services (EVS), and elastic scaling services (AS); of course, in other embodiments, the preset types of data sources and the content of cloud services can also be set according to other types of task data; The business service layer is used to determine its service type based on the business architecture. Figure 4 Preferably, the service types include task configuration service, task execution service, task statistics service, in-site message service, SMS notification service and email notification service.

[0038] The display methods of the presentation layer include web interfaces under the VUE framework, mobile applications built based on HTMLS technology, and visual data displays based on open source visualization libraries such as Echarts, and provide interface services under the REST software architecture style.

[0039] The task-driven engine system of this embodiment adopts an efficient data synchronization mechanism to ensure that key information such as task progress and execution status can be updated and synchronized in real time between multiple users and multiple roles. Through database technology and network communication technology (such as HTTP), the system can capture and propagate all changes related to the task to ensure the accuracy and consistency of information. Standardized data interfaces and exchange protocols are designed. Through technical means such as API gateways and middleware, seamless integration and data interoperability with other business systems are achieved. In this way, the task-driven engine system can easily exchange task-related data with other systems.

[0040] Preferably, the overall technical architecture of the task-driven engine system of this embodiment is implemented based on the microservice architecture, so Figure 4 As shown, the overall technical architecture of the task-driven engine system also includes a microservice gateway, a microservice configuration center, and a microservice registration center.

[0041] The microservice gateway is used to connect the presentation layer and the business service layer. The microservice configuration center is a central service for managing application or system configuration information. It stores the configuration information of all microservices in a centralized service and distributes the configuration files to each microservice through the HTTP interface, thereby completing the configuration of the microservice gateway. The microservice registration center receives registration requests for microservice instances and saves instance information in the registry. Through the registration center, service consumers, that is, users, can find and call required services based on service names or other identifiers. The registration center can also implement load balancing and failover to ensure high availability of services. When users call task-related services, they send registration requests for microservices to the microservice registration center through the interface service provided by the presentation layer to complete the call to the service provided by the business service layer.

[0042] The task-driven engine system of the present invention can be integrated into a third-party business system and configured in a task management module of the third-party business system. The third-party business system can be a project management system, and it is necessary to issue task messages to corresponding persons for project management process nodes. The third-party business system includes but is not limited to functional items such as execution supervision, acceptance supervision, online approval, and centralized internal audit. Each functional item involves the use of a task-driven engine to complete the management of related tasks. The third-party business system encapsulates the task data at the required time node and sends it to the task management module through the interface defined by the network protocol. The task management module completes the creation, execution, tracking and other operations of the task with the help of the task-driven engine. During this period, the third-party business system can also call the interface defined by the task-driven engine at the same time to query and display all task information, and complete the data interoperability function of the third-party business system and the task-driven engine.

[0043] The task-driven engine system of the present invention takes task-driven as the core, creates customized task templates, clarifies the publisher of the task, the content of the task, the executor of the task, the planned completion time of the task, etc., granulates the complex work, and details the complicated processes, realizes the closed-loop management of publishing, execution, tracking, reminding, and statistics, realizes the "PDCA" cycle of tasks, prevents the omission of work items, and quickly and accurately finds the most important things to do at a fixed time, improves the user's time management ability, reduces the workload, improves the work quality, and enhances work efficiency.

[0044] The embodiments described above are only used to illustrate the technical solutions of the present invention, rather than to limit the same. Although the present invention has been described in detail with reference to the aforementioned embodiments, those skilled in the art should understand that the technical solutions described in the aforementioned embodiments may still be modified, or some of the technical features may be replaced by equivalents. Such modifications or replacements do not deviate the essence of the corresponding technical solutions from the spirit and scope of the technical solutions of the embodiments of the present invention, and should all be included in the protection scope of the present invention.

Claims

1. A task-driven engine system, characterized in that: The business architecture of the task-driven engine system includes a task configuration layer, a task execution layer, and a task statistics layer; The task configuration layer includes a task type module and a task template module. The task type module is used to complete the management and configuration of task types and classify different types of tasks to determine the task type. The task template module is used to customize the task template according to the task type. The task execution layer includes a task publishing module, a task execution module and a progress tracking module. The task publishing module is used to publish corresponding tasks according to work items. The task execution module is used to complete task viewing, task filling, task submission and task splitting according to the current user's to-be-executed task list. The progress tracking module is used to track the task execution status according to the task list, count completed, in-progress and unfinished tasks, complete task inspection, task supervision and task reminder; The task statistics layer is used to complete task statistics, task execution analysis statistics, and construct an energy map corresponding to the task according to the type, template, and time dimension of the task to determine the distribution of energy expended by the current user in completing the task.

2. The task-driven engine system according to claim 1, characterized in that: The task types include standard type, data type transaction type and business type; the customized content of the task template includes task type, priority, task content and task configuration items.

3. The task-driven engine system according to claim 1 or 2, characterized in that: The task execution layer also includes a task calendar module and a mobile application module, and the task configuration layer also includes an early warning strategy module; The task calendar module is used to construct a calendar chart of published or received tasks, showing the details of the published or received tasks; The mobile application module is used to provide users with mobile terminal query statistics functions, and the mobile terminal query statistics functions include task calendar, task execution, progress tracking, and energy map; The warning strategy module is used to define the reminder content of the task and determine the reminder strategy for the task during the process of task creation, expiration, overdue, withdrawal or closing.

4. The task-driven engine system according to claim 3, characterized in that: The reminder strategy includes reminder form, reminder times, and reminder triggering conditions. The reminder form includes SMS reminder and email reminder.

5. The task-driven engine system according to claim 3, characterized in that: Corresponding to the business architecture, the application architecture of the task-driven engine system includes a basic service layer, a business management layer and a visualization layer; The business management layer is constructed based on other modules in the business architecture except the mobile application module; The visualization layer includes a desktop application module and a mobile application module in the business architecture. The desktop application module is used to provide users with a task publishing function and a desktop query and statistics function. The desktop query and statistics function includes task execution, progress tracking and task statistics. The basic service layer includes data storage services, file storage services, system integration services, SMS platforms and email systems.

6. The task-driven engine system according to claim 1, characterized in that: The task-driven engine system is constructed using front-end and back-end separation technology.

7. The task driven engine system according to claim 1 or 6, characterized in that: The technical architecture of the task-driven engine system includes a security protection layer, an infrastructure layer, a business service layer, and a presentation layer; The security protection layer includes security management, security protection, data encryption and security monitoring functions; the infrastructure layer is built on a cloud platform and provides set cloud services for preset types of data sources; the business service layer is used to determine its service type based on the business architecture; the display methods of the display layer include web interface, mobile application and visual data display, and provide interface services.

8. The task-driven engine system according to claim 7, characterized in that: The preset types of data sources include relational databases, in-memory databases, object storage service data, and application server data. The set cloud services include cloud server services, load balancing services, cloud hard disk services, and elastic scaling services.

9. The task driven engine system according to claim 7, characterized in that: The service types include task configuration service, task execution service, task statistics service, in-site message service, SMS notification service and email notification service.

10. The task driven engine system according to claim 7, characterized in that: The technical architecture of the task-driven engine system also includes a microservice gateway, a microservice configuration center, and a microservice registration center; The presentation layer is connected to the business service layer through the microservice gateway, and the configuration of the microservice gateway is completed based on the microservice configuration center. The user sends a registration request for the microservice to the microservice registration center through the interface service of the presentation layer to complete the call of the service provided by the business service layer.

Images