Financial institution task management method and system, terminal and medium

Abstract

The invention belongs to the field of financial management, and particularly discloses a financial institution task management method and system, a terminal and a medium, and the method comprises the steps: storing the institution information of each financial institution through a cloud computing technology and a distributed file system; subtasks of the involved financial institutions are constructed through the task scheme information; constructing a process monitoring task for each sub-task, issuing the sub-tasks to the corresponding financial institutions, and starting the process monitoring tasks of the sub-tasks; obtaining subtask completion process information according to a monitoring result of the process monitoring task based on the number of task submission time nodes and the specific time; and according to the task scheme information and the subtask completion process information, determining a supervision reminding level of an uncompleted subtask, and according to the supervision reminding level, sending a supervision reminder to a submitter. According to the task scheme information and the feedback result of the monitoring task, different levels of reminding of completion conditions of different tasks are realized, and the task supervision and management efficiency is improved.

Description

Technical Field

[0001] The present invention belongs to the field of financial management, and particularly relates to a task management method, system, terminal and medium for financial institutions. Background Art

[0002] In the financial field, the relevant tasks responsible for by various financial institutions are different, and the relevant tasks are different in terms of indicators, etc. There are also differences in the task issuance and task supervision of the same management department for the same financial institution or different financial institutions. This requires the financial management institution to issue tasks to multiple financial institutions or different departments of the same financial institution separately. The tasks are numerous and it is inconvenient to monitor.

[0003] During the task execution process, the existing task management mode lacks effective monitoring and reminder mechanisms. Usually, it waits passively for the task results. When the task fails to be completed on time, there is no supervision and reminder system, and it is impossible to give targeted reminders according to the importance and urgency of the tasks, resulting in task delays. In addition, due to the different attributes and time requirements of different tasks, the existing reminder methods generally remind by displaying different colors on the interface. This method is too single and cannot meet the diverse management needs. Summary of the Invention

[0004] To solve the above problems, the present invention provides a task management method, system, terminal and medium for financial institutions, which pre-formulates task plan information, automatically distributes tasks to corresponding financial institutions according to the task plan information, and realizes different-level reminders for the completion status of different tasks according to the task plan information combined with the feedback results of monitoring tasks, improving the efficiency of task supervision and management.

[0005] In the first aspect, the technical solution of the present invention provides a task management method for financial institutions, including the following steps: Store the institutional information of each financial institution through cloud computing technology and distributed file system, and the institutional information includes institutional hierarchy information and bound personnel information at each level; Obtain the formulated task plan information, and construct subtasks of the involved financial institutions through the task plan information; the task plan information includes task plan identifier, management department, task name, involved financial institutions, task description, task type, number of task submission time nodes and each specific time, task attribute; Construct process monitoring tasks for each subtask and store the process monitoring tasks in the monitoring task pool; Distribute the subtasks to the corresponding financial institutions, and in response to the successful feedback of the distribution, start the process monitoring tasks of the subtasks; Based on the number of task submission time nodes and specific times, obtain the subtask completion process information according to the monitoring results of the process monitoring tasks; Determine the supervision reminder level of the unfinished subtasks according to the task plan information and the subtask completion progress information, and send a supervision reminder to the reporter according to the supervision reminder level.

[0006] In an optional implementation manner, construct the subtasks of the involved financial institutions through the task plan information, specifically including: Analyze the current task plan information to obtain the task plan identifier, the number of involved financial institutions, the number of task reporting time nodes, and the specific time; Expand the number of rows of the current subtask list according to the number of involved financial institutions, with each financial institution corresponding to one row; Construct the subtasks of the involved financial institutions through the task plan information, including associating the task plan information with the subtasks and constructing the unique identifier of the subtasks; Randomly sort the subtasks, and fill the task plan identifier into the first column of the corresponding row of the subtask list according to the sorting order, and fill the unique identifier of the subtask into the second column of the corresponding row of the subtask list to form the mapping relationship between the subtasks and the task plan; Configure the task completion status information of the subtasks in the fourth column of the corresponding row of the subtask list. The task completion status information is stored in the form of [subtask completion status identifier: subtask completion percentage]. The subtask completion status identifier is used to indicate whether the subtask is completed; Fill the number of task reporting time nodes of the subtasks in the fifth column of the corresponding row of the subtask list; Fill the task reporting information of the subtasks into the columns after the fifth column of the corresponding row of the subtask list in the order of the specific reporting time. The storage form of the task reporting information in the subtask list is [node i: specific time: actual time: node completion status identifier: node completion evaluation identifier]. Node i refers to the i-th node that should be completed. The actual time is used to identify the actual data reporting time of node i. The completion status identifier is used to indicate whether the node is completed. The completion evaluation identifier is used to indicate whether the node is completed before the specific time.

[0007] In an optional implementation manner, construct a process monitoring task for each subtask and store the process monitoring task in the monitoring task pool, specifically including: Construct a process monitoring task for each subtask, including constructing the unique identifier of the process monitoring task; Store the constructed process monitoring task in the monitoring task pool; Obtain the number of constructed process monitoring tasks; Expand the number of rows of the current process monitoring task list according to the number of obtained process monitoring tasks, with each process monitoring task corresponding to one row; Fill the unique identifier of the process monitoring task of each subtask into the third column of the corresponding row of the subtask list; Extract the first column and the third column of the corresponding rows in the subtask list and fill them into the first column and the second column of the corresponding rows expanded in the process monitoring task list respectively, that is, fill the unique identifier of the process monitoring task into the second column of the process monitoring task list, and fill the corresponding task plan identifier into the matching first column; Fill the monitoring task completion status identifier in the fourth column of the process monitoring task list.

[0008] In an alternative embodiment, based on the number of task reporting time nodes and the specific time, obtain the subtask completion progress information according to the monitoring results of the process monitoring tasks, specifically including: Obtain the monitoring results of the process monitoring tasks in real time, where the monitoring results include the actual time of the current received data report and the number of received data reports; Obtain the subtask completion progress information according to the monitoring results, including: (1) Detect whether the number of received data reports has reached the number of task reporting time nodes of the subtask, calculate the subtask completion percentage, update the information in the fourth column of the corresponding row in the subtask list according to the detection and calculation results, and update the information in the fourth column of the corresponding row in the process monitoring task list; (2) Update the task reporting information column in the corresponding row of the subtask list according to the actual time of the current received data report and the number of received data reports.

[0009] In an alternative embodiment, determine the supervision reminder level of the unfinished subtasks according to the task plan information and the subtask completion progress information, specifically including: Periodically extract the unfinished subtasks from the subtask list, denoted as the subtasks to be supervised; Obtain the task plan identifier of the subtasks to be supervised from the subtask list; Extract the task attributes from the task plan information according to the task plan identifier; Based on the pre-configured importance degree of the attributes, determine the first parameter evaluation value of the subtasks to be supervised according to the task attributes; the first parameter evaluation value is proportional to the importance degree of the attributes; Obtain the specific time of the next completion node of the subtasks to be supervised from the subtask list, and calculate the time difference between the current time and the specific time; Based on the pre-configured correspondence between the time difference interval and the evaluation value, determine the second parameter evaluation value of the subtasks to be supervised according to the calculated time difference; the second parameter evaluation value is inversely proportional to the length of the time difference; Determine the reminder level of the subtasks to be supervised according to the first parameter evaluation value and the second parameter evaluation value.

[0010] In an alternative embodiment, the method further includes the following steps: Periodically detect the monitoring task completion status of each process monitoring task in the process monitoring task list; If the monitoring task is in the completed state, delete the monitoring task from the monitoring task pool and the monitoring task list.

[0011] In an alternative embodiment, the financial institutions involved in the task plan information include the institutional levels of the institutions executing the tasks; When issuing a subtask to the corresponding financial institution, issue the subtask to the institutional level of the institution executing the task and obtain the personnel information bound to the institutional level of the institution executing the task; The monitoring result further includes the personnel information of the person reporting the data this time; Before obtaining the monitoring result of the process monitoring task in real time, the following steps are further included: Detect whether the personnel information of the person reporting the data this time is consistent with the bound personnel information; If they are consistent, determine that the monitoring result this time is valid; If they are inconsistent, determine that the monitoring result this time is invalid.

[0012] In a second aspect, the technical solution of the present invention provides a financial institution task management system, including: An institutional information storage module, configured to store the institutional information of each financial institution through cloud computing technology and a distributed file system, where the institutional information includes institutional level information and the bound personnel information of each level; A subtask construction module, configured to obtain the formulated task plan information and construct subtasks of the involved financial institutions through the task plan information; the task plan information includes a task plan identifier, a management department, a task name, the involved financial institutions, a task description, a task type, the number of task reporting time nodes and each specific time, and task attributes; A process monitoring task construction module, configured to construct a process monitoring task for each subtask and store the process monitoring task in the monitoring task pool; A subtask issuing module, configured to issue a subtask to the corresponding financial institution and, in response to a successful feedback of the issuance, start the process monitoring task of the subtask; A subtask completion process acquisition module, configured to obtain subtask completion process information based on the number of task reporting time nodes and specific times according to the monitoring result of the process monitoring task; A supervision reminder module, configured to determine the supervision reminder level of the uncompleted subtasks according to the task plan information and the subtask completion process information, and send a supervision reminder to the reporter according to the supervision reminder level.

[0013] In a third aspect, the technical solution of the present invention provides a terminal, including: A memory, configured to store a financial institution task management program; A processor for implementing the steps of the financial institution task management method as described in any one of the above when executing the financial institution task management program.

[0014] In a fourth aspect, the technical solution of the present invention provides a computer-readable storage medium, on which a financial institution task management program is stored. When the financial institution task management program is executed by a processor, it implements the steps of the financial institution task management method as described in any one of the above.

[0015] The financial institution task management method, system, terminal and medium provided by the present invention have the following beneficial effects compared with the prior art: storing the institutional information of financial institutions hierarchically provides an architectural support for task distribution. Pre-formulating task plan information, generating subtasks according to the task plan information and distributing them to the corresponding financial institution levels to achieve unified task distribution, improving task distribution efficiency. At the same time, constructing monitoring tasks for each distributed task to monitor the reporting situation of the tasks, realizing task process supervision, and determining the supervision reminder level for the uncompleted reporting nodes in combination with the formulated task plan information to achieve adaptive level reminder for tasks, improving the flexibility, efficiency and accuracy of task reminders. The present invention pre-formulates task plan information, automatically distributes tasks to the corresponding financial institutions according to the task plan information, and realizes different-level reminders for the completion situations of different tasks in combination with the feedback results of the monitoring tasks, improving task supervision and management efficiency. BRIEF DESCRIPTION OF THE DRAWINGS In order to more clearly illustrate the technical solutions of the present invention, the drawings required for description will be briefly introduced below. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, other drawings can be obtained based on these drawings without creative efforts.

[0016] Figure 1 It is a schematic flowchart of a financial institution task management method provided by an embodiment of the present invention.

[0017] Figure 2 It is a schematic block diagram of the structure of a financial institution task management system provided by an embodiment of the present invention.

[0018] Figure 3 It is a schematic diagram of the structure of a terminal provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0019] In order to make the objectives, features, and advantages of the present invention more obvious and understandable, the following will clearly and completely describe the technical solutions in the present invention in conjunction with the accompanying drawings in the specific embodiments. Obviously, the embodiments described below are only a part of the embodiments of the present invention, rather than all the embodiments. Based on the embodiments in this application, all other embodiments obtained by those of ordinary skill in the art without creative efforts belong to the scope of protection of this application.

[0020] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by those skilled in the technical field to which the present invention belongs. The terms used in the description of the present invention herein are only for the purpose of describing specific embodiments, and are not intended to limit the present invention.

[0021] Figure 1 It is a schematic flowchart of a method for task management of financial institutions provided by an embodiment of the present invention. Among them, Figure 1 The execution subject can be a task management system for financial institutions. The method for task management of financial institutions provided by the embodiment of the present invention is executed by a computer device. Correspondingly, the task management system for financial institutions runs in the computer device. According to different requirements, the order of the steps in this flowchart can be changed, and some can be omitted.

[0022] As Figure 1 shown, the method includes the following steps.

[0023] S1, storing the institutional information of each financial institution through cloud computing technology and a distributed file system.

[0024] In this embodiment, the institutional information of the financial institution includes institutional hierarchy information and the bound personnel information of each level.

[0025] S2, obtaining the formulated task plan information, and constructing subtasks of the involved financial institutions through the task plan information.

[0026] In this embodiment, the task plan information includes a task plan identifier, a management department, a task name, the involved financial institutions, a task description, a task type, the number of task submission time nodes and each specific time, and a task attribute.

[0027] S3, constructing a process monitoring task for each subtask, and storing the process monitoring task in a monitoring task pool.

[0028] S4, sending the subtasks to the corresponding financial institutions, and in response to the successful feedback of the sending, starting the process monitoring tasks of the subtasks.

[0029] S5, obtaining the subtask completion process information based on the number of task submission time nodes and specific times according to the monitoring results of the process monitoring tasks.

[0030] S6. Determine the supervision reminder level for the unfinished subtasks according to the task plan information and the subtask completion progress information, and send a supervision reminder to the reporter according to the supervision reminder level.

[0031] The financial institution task management method provided in this embodiment hierarchically stores the institution information of the financial institution, provides an architecture support for task distribution, formulates task plan information in advance, generates subtasks according to the task plan information and distributes them to the corresponding financial institution levels, realizes the unified distribution of tasks, improves the task distribution efficiency, and constructs a monitoring task for each distributed task to monitor the reporting situation of the task, realizes the task process supervision, and determines the supervision reminder level for the uncompleted reporting nodes in combination with the formulated task plan information, realizes the adaptive level reminder for tasks, and improves the flexibility, efficiency and accuracy of task reminders. The present invention formulates task plan information in advance, automatically distributes tasks to the corresponding financial institutions according to the task plan information, and realizes different-level reminders for the completion situations of different tasks in combination with the feedback results of the monitoring tasks according to the task plan information, improving the task supervision and management efficiency.

[0032] In this embodiment, the institution information of each financial institution is stored through cloud computing technology and a distributed file system. Relying on the network, storage, computing resources and capabilities of the cloud computing center, cloud computing technology and a distributed file system are used to efficiently extract and integrate the institution level information, and after being tightly bound with the personnel information, it is securely stored, providing data support for subsequent task management.

[0033] In some optional implementation manners, step S1 specifically includes the following steps.

[0034] S1.1. Perform resource preparation and environment setup.

[0035] Apply to the cloud computing center and plan a dedicated network to ensure the stability and security of data transmission. Specifically, configure a virtual private network (VPN) to securely connect the internal network of the financial institution to the cloud computing center network, ensuring that data is not illegally obtained during transmission.

[0036] S1.2. Allocate storage capacity in the cloud computing center according to the estimated data volume to be stored.

[0037] Specifically, use a distributed file system (such as Ceph, GlusterFS, etc.) to create a storage pool to provide a storage basis for subsequent data storage.

[0038] In some optional implementation manners, classify and manage the storage resources. Specifically, store the institution level information and the personnel information in different logical partitions or storage buckets respectively, and construct a logical association to facilitate subsequent data extraction and integration.

[0039] S1.3, Extract the institutional information data of financial institutions.

[0040] For the extraction of hierarchical information of institutions, the hierarchical information is extracted from the data source (which may be a database or a file system) storing the hierarchical information of institutions through a data extraction script of cloud computing technology. Exemplarily, SQL query statements are used to extract institutional type, institutional hierarchy, institutional name, institutional number, institutional region, and subordinate department information from a relational database.

[0041] For the extraction of personnel information, information such as personnel names, accounts, contact information, and affiliated departments is extracted from the personnel information management system. Specifically, structured data is obtained from the database using SQL queries, or data is obtained by docking with existing systems using specific interfaces and APIs.

[0042] S1.4, Integrate the institutional information of the extracted financial institutions.

[0043] Standardize the formats of the extracted hierarchical information of institutions and personnel information. Exemplarily, all date formats are unified into "YYYY - MM - DD", and the character encodings of institutional names and personnel names are unified into UTF - 8 to ensure the consistency of data in subsequent processing.

[0044] Normalize the data types. Exemplarily, fields such as institutional numbers and accounts are set to appropriate data types to avoid type - mismatch errors during data integration and storage.

[0045] Establish association fields. Specifically, through common association fields (such as affiliated departments), the hierarchical information of institutions is associated with personnel information. Exemplarily, there is a "subordinate department" field in the hierarchical information of institutions and an "affiliated department" field in personnel information, and a logical connection between the two is established using these two fields.

[0046] S1.5, Store the institutional information of financial institutions in the previously planned distributed file system.

[0047] Use cloud computing technology and distributed file system to store the hierarchical information of financial institutions and the personnel information bound to each level. Provide an architectural support for the accurate distribution of tasks, facilitate the rapid positioning of task execution objects, and improve the accuracy and efficiency of task allocation.

[0048] In some alternative embodiments, step S2 obtains the formulated task plan information, and constructs subtasks of the financial institutions involved through the task plan information, which specifically includes the following steps.

[0049] S2.1, Obtain the formulated task plan information.

[0050] According to the task requirements, the management part formulates the required task plan information, which includes the task plan identifier, management department, task name, involved financial institutions, task description, task type, number of task submission time nodes and specific times, and task attributes.

[0051] Among them, the involved financial institutions include the institutional levels for executing tasks, so as to directly distribute tasks to the corresponding levels of financial institutions.

[0052] S2.2, Parse the current task plan information to obtain the task plan identifier, the number of involved financial institutions, the number of task submission time nodes and specific times.

[0053] It should be noted that the number of involved financial institutions can include multiple ones, that is, the same task is distributed to multiple financial institutions.

[0054] S2.3, Expand the number of rows of the current subtask list according to the number of involved financial institutions, with each financial institution corresponding to one row.

[0055] It should be noted that a subtask list has been pre-constructed. The subtask list is used to manage all distributed subtasks. When there are new subtasks, the number of rows of the subtask list is expanded, with each financial institution corresponding to one row, so as to improve the task management efficiency.

[0056] Exemplarily, currently there are 3 new subtasks. Expand three rows at the bottom of the current subtask list. The information of the first new subtask is filled in the third row from the bottom, the information of the second new subtask is filled in the second row from the bottom, and the information of the third new subtask is filled in the last row.

[0057] S2.4, Construct subtasks for the involved financial institutions through the task plan information, including associating the task plan information with the subtasks and constructing unique identifiers for the subtasks.

[0058] Associate the task plan information with the subtasks and construct unique identifiers to clarify the source of the subtasks, so that each subtask has a corresponding task plan, which is convenient for subsequent management of all subtasks of the same task plan.

[0059] S2.5, Randomly sort the subtasks, fill the task plan identifier into the first column of the corresponding row of the subtask list according to the sorting order, and fill the unique identifier of the subtask into the second column of the corresponding row of the subtask list to form the mapping relationship between the subtasks and the task plan.

[0060] After random sorting, fill in the task plan identifier and the unique identifier of the subtask, construct a mapping relationship, and provide an index for the task management system to facilitate quick search and association of the task plan and the subtask.

[0061] S2.6. Configure the task completion status information of the subtask in the fourth column of the corresponding row in the subtask list. The task completion status information is stored in the form of [subtask completion status identifier: subtask completion percentage]. The subtask completion status identifier is used to indicate whether the subtask is completed.

[0062] Store the subtask completion status information in the fourth column, including the subtask completion status identifier and the subtask completion percentage. Subsequently, the subtask completion status can be directly known based on the subtask completion status identifier and the subtask completion percentage.

[0063] S2.7. Fill in the number of task reporting time nodes of the subtask in the fifth column of the corresponding row in the subtask list.

[0064] S2.8. Fill in the task reporting information of the subtask column by column in sequence after the fifth column of the corresponding row in the subtask list according to the chronological order of the specific reporting time. The storage form of the task reporting information in the subtask list is [node i: specific time: actual time: node completion status identifier: node completion evaluation identifier]. Node i refers to the i-th node that should be completed. The actual time is used to identify the actual data reporting time of node i. The completion status identifier is used to indicate whether the node is completed. The completion evaluation identifier is used to indicate whether the node is completed before the specific time.

[0065] Fill in the task reporting information in chronological order, record the specific time, actual time, completion status identifier, and completion evaluation identifier of each task node in detail, provide data for task monitoring and evaluation, and facilitate task management. Exemplarily, if there are 3 nodes, the task reporting information of the first node is filled in the sixth column, the task reporting information of the second node is filled in the seventh column, and the task reporting information of the third node is filled in the eighth column.

[0066] In some alternative embodiments, step S3 constructs a process monitoring task for each subtask and stores the process monitoring task in the monitoring task pool, which specifically includes the following steps.

[0067] S3.1. Construct a process monitoring task for each subtask, including constructing a unique identifier for the process monitoring task.

[0068] S3.2. Store the constructed process monitoring task in the monitoring task pool.

[0069] S3.3. Obtain the number of constructed process monitoring tasks.

[0070] It can be understood that the number of monitoring tasks is the same as the number of subtasks.

[0071] S3.4, expand the number of rows of the current process monitoring task list according to the obtained process monitoring tasks, with each process monitoring task corresponding to one row.

[0072] Similar to the subtask list, a process monitoring task list has been pre-constructed to manage the monitoring tasks of all dispatched subtasks.

[0073] S3.5, fill the unique identifier of the process monitoring task of each subtask into the third column of the corresponding row in the subtask list.

[0074] Filling the unique identifier of the process monitoring task of each subtask into the third column of the corresponding row in the subtask list can establish the mapping relationship between the process monitoring task and the corresponding subtask. According to this mapping relationship, update the subtask information in the corresponding row of the subtask list with the monitoring result of the process monitoring task.

[0075] S3.6, extract the first column and the third column of the corresponding row in the subtask list and fill them into the first column and the second column of the corresponding expanded row in the process monitoring task list, that is, fill the unique identifier of the process monitoring task into the second column of the process monitoring task list, and fill the corresponding task plan identifier into the matching first column.

[0076] S3.7, fill the monitoring task completion status identifier in the fourth column of the process monitoring task list.

[0077] In some optional embodiments, periodically detect the monitoring task completion status of each process monitoring task in the process monitoring task list; if the monitoring task is in the completed state, delete the monitoring task from the monitoring task pool and the monitoring task list to reduce memory and resource occupancy and ensure overall performance.

[0078] Dispatch the subtask to the corresponding financial institution, and in response to the successful feedback of the dispatch, start the process monitoring task of the subtask. In some optional embodiments, when dispatching the subtask to the corresponding financial institution, dispatch the subtask to the institutional level where the task is executed and obtain the personnel information bound to the institutional level where the task is executed, so as to subsequently monitor whether the correct personnel report according to the bound personnel information.

[0079] In these alternative embodiments, a process monitoring task with a unique identifier is constructed for each subtask, the constructed monitoring tasks are stored in a monitoring task pool, and the number of them is obtained. The number of rows in the process monitoring task list is expanded according to the number of monitoring tasks. At the same time, corresponding identifiers are filled in the subtask list and the process monitoring task list to establish a mapping relationship between the tasks, and a monitoring task completion status identifier is filled in the process monitoring task list. These alternative embodiments construct independent process monitoring tasks for each subtask to ensure comprehensive tracking of the task execution process. The establishment of unique identifiers facilitates accurate distinction and management of each monitoring task, avoiding task confusion and improving the accuracy of monitoring. At the same time, storing the monitoring tasks in the task pool enables unified management and scheduling, improving the task processing efficiency. And by obtaining the number of monitoring tasks to expand the corresponding number of list rows, the task management efficiency is enhanced. Filling identifiers in the subtask list and the process monitoring task list to establish a mapping relationship enables the monitoring results to be accurately corresponding to the corresponding subtasks, so as to update the subtask information in a timely manner.

[0080] In some alternative embodiments, step S5 obtains the subtask completion progress information according to the monitoring results of the process monitoring tasks based on the number of task reporting time nodes and the specific time, which specifically includes the following steps.

[0081] S5.1, Obtain the monitoring results of the process monitoring tasks in real time. The monitoring results include the actual time of receiving the data report this time and the number of received data reports.

[0082] In some alternative embodiments, the monitoring results further include the personnel information of the person who conducts the data report this time. Before obtaining the monitoring results of the process monitoring tasks in real time, it is detected whether the personnel information of the person who conducts the data report this time is consistent with the bound personnel information. If they are consistent, it is determined that the monitoring results this time are valid; if they are inconsistent, it is determined that the monitoring results this time are invalid. It can be understood that based on the valid monitoring results, the relevant content in the subtask list and the monitoring task list is updated.

[0083] S5.2, Obtain the subtask completion progress information according to the monitoring results, including (1) Detect whether the number of received data reports has reached the number of task reporting time nodes of the subtask, calculate the subtask completion percentage, and update the information in the fourth column of the corresponding row in the subtask list and the information in the fourth column of the corresponding row in the process monitoring task list according to the detection and calculation results.

[0084] Specifically, if the number of task reporting time nodes of the subtask is reached, update the process monitoring task status and the subtask status to completed; if not, keep them unchanged.

[0085] Specifically, obtain the subtask completion percentage by dividing the number of completed ones by the total number.

[0086] (2) Update the task reporting information column in the corresponding row of the subtask list according to the actual time of this received data report and the number of received receipt reports.

[0087] Specifically, first locate the corresponding row in the subtask list according to the process monitoring task identifier, and then update the fourth column of the current subtask and the column corresponding to the current node in the subtask list according to the actual time of this received data report and the number of received receipt reports.

[0088] In some alternative embodiments, step S6 determines the supervision reminder level of the unfinished subtasks according to the task plan information and the subtask completion progress information, which specifically includes the following steps.

[0089] S6.1, Periodically extract the unfinished subtasks from the subtask list and record them as the subtasks to be supervised.

[0090] S6.2, Obtain the task plan identifier of the subtask to be supervised from the subtask list.

[0091] S6.3, Extract the task attributes from the task plan information according to the task plan identifier.

[0092] S6.4, Based on the pre-configured importance level of the attributes, determine the first parameter evaluation value of the subtask to be supervised according to the task attributes; the first parameter evaluation value is proportional to the importance level of the attributes.

[0093] It should be noted that the pre-configured importance levels of various attributes can be an importance level range, and different importance level ranges correspond to different first parameter evaluation values. The higher the task importance level, the larger the first parameter evaluation value.

[0094] S6.5, Obtain the specific time of the next node to be completed for the subtask to be supervised from the subtask list, and calculate the time difference between the current time and the specific time.

[0095] S6.6, Based on the pre-configured correspondence between the time difference range and the evaluation value, determine the second parameter evaluation value of the subtask to be supervised according to the calculated time difference; the second parameter evaluation value is inversely proportional to the length of the time difference.

[0096] Pre-configure different evaluation values corresponding to different time difference ranges, and then match the corresponding second parameter evaluation value based on the specifically calculated time difference. The shorter the time difference, the larger the second parameter evaluation value.

[0097] S6.7, Determine the reminder level of the subtask to be supervised according to the first parameter evaluation value and the second parameter evaluation value.

[0098] In some alternative embodiments, weights are configured for the first parameter evaluation value and the second parameter evaluation value, and the two are weighted and summed to obtain a comprehensive evaluation value. Then, based on the pre-established correspondence between the comprehensive evaluation value and the reminder level, the final reminder level is determined. The higher the reminder level, the greater the reminder given. For example, the first reminder level is an email reminder, the second reminder level is a text message reminder, and the third reminder level is a phone call reminder, so as to remind the person in charge in a timely manner and improve management efficiency.

[0099] When performing supervision and reminder, first, incomplete subtasks are periodically extracted. Then, their task plan identifiers are obtained and task attributes are extracted, and the first parameter evaluation value is determined according to the pre-configured importance level of the attributes. Next, the time difference between the current time and the next due time node of the subtask is calculated, and the second parameter evaluation value is determined according to the pre-configured correspondence between the time difference interval and the evaluation value. Finally, a comprehensive evaluation value is obtained by configuring weights for the two parameter evaluation values and performing weighted summation, and the final reminder level is determined based on the correspondence between the comprehensive evaluation value and the reminder level. By comprehensively considering the importance level of task attributes and the urgency of task completion time to determine the reminder level, for example, high-level reminders are given for important and time-sensitive tasks, ensuring that tasks can receive timely attention and processing, improving the accuracy of reminders, and avoiding resource waste and ineffective reminders. Timely and targeted reminders can effectively urge the person in charge to speed up the task progress and avoid task delays. Taking reminders in different ways as an example, a phone call reminder is suitable for urgent and important tasks, which can quickly attract the attention of the person in charge and prompt them to handle the task immediately, thereby improving the overall task management efficiency. In addition, by pre-configuring the correspondence between the importance level interval of attributes, the time difference interval and the evaluation value, and setting weights for the two parameter evaluation values, etc., the determination of the reminder level is made more flexible. Financial management institutions can adjust according to business characteristics and management requirements to meet the task management requirements in different scenarios and adapt to the complex and changeable business environment.

[0100] In the above text, embodiments of a task management method for a financial institution are described in detail. Based on the task management method for a financial institution described in the above embodiments, an embodiment of the present invention also provides a task management system for a financial institution corresponding to this method.

[0101] Figure 2 FIG. 10 is a schematic block diagram of the structure of a task management system for a financial institution provided by an embodiment of the present invention. In this embodiment, the task management system 200 for a financial institution can be divided into multiple functional modules according to the functions it performs. The module referred to in the present invention means a series of computer program segments that can be executed by at least one processor and can complete fixed functions, and are stored in the memory.

[0102] The institutional information storage module 210 is used to store the institutional information of each financial institution through cloud computing technology and a distributed file system. The institutional information includes institutional hierarchy information and the bound personnel information of each level.

[0103] The subtask construction module 220 is used to obtain the formulated task plan information and construct subtasks of the involved financial institutions through the task plan information. The task plan information includes a task plan identifier, a management department, a task name, the involved financial institutions, a task description, a task type, the number of task submission time nodes and each specific time, and task attributes.

[0104] The process monitoring task construction module 230 is used to construct process monitoring tasks for each subtask and store the process monitoring tasks in a monitoring task pool.

[0105] The subtask distribution module 240 is used to distribute subtasks to the corresponding financial institutions, and in response to the feedback of successful distribution, start the process monitoring tasks of the subtasks.

[0106] The subtask completion process acquisition module 250 is used to obtain subtask completion process information based on the number of task submission time nodes and specific times according to the monitoring results of the process monitoring tasks.

[0107] The supervision and reminder module 260 is used to determine the supervision and reminder level of uncompleted subtasks according to the task plan information and the subtask completion process information, and send a supervision and reminder to the submitter according to the supervision and reminder level.

[0108] The financial institution task management system of this embodiment is used to implement the foregoing financial institution task management method. Therefore, the specific implementation manners in this system can be seen in the embodiment part of the financial institution task management method in the foregoing text. Therefore, its specific implementation manners can be referred to the descriptions of the corresponding various part embodiments and will not be elaborated here.

[0109] In addition, since the financial institution task management system of this embodiment is used to implement the foregoing financial institution task management method, its functions correspond to those of the above method and will not be elaborated here.

[0110] Figure 3 The following is a schematic structural diagram of a terminal 300 provided by an embodiment of the present invention, including: a processor 310, a memory 320, and a communication unit 330. When the processor 310 implements the financial institution task management program stored in the memory 320, the following steps are implemented: Store the institutional information of each financial institution through cloud computing technology and a distributed file system. The institutional information includes institutional hierarchy information and the bound personnel information of each level; Obtain the specified task plan information, and construct subtasks of the involved financial institutions through the task plan information; the task plan information includes a task plan identifier, a management department, a task name, the involved financial institutions, a task description, a task type, the number of task submission time nodes and each specific time, and task attributes. Construct a process monitoring task for each subtask, and store the process monitoring task in the monitoring task pool. Send the subtasks to the corresponding financial institutions, and in response to the successful feedback of the sending, start the process monitoring tasks of the subtasks. Based on the number of task submission time nodes and the specific time, obtain the subtask completion process information according to the monitoring results of the process monitoring tasks. Determine the supervision reminder level of the unfinished subtasks according to the task plan information and the subtask completion process information, and send a supervision reminder to the submitter according to the supervision reminder level.

[0111] The present invention also provides a computer storage medium, and the storage medium here may be a magnetic disk, an optical disk, a read-only memory (English: read-only memory, abbreviated as: ROM), or a random access memory (English: random access memory, abbreviated as: RAM), etc.

[0112] The computer storage medium stores a financial institution task management program, and when the financial institution task management program is executed by a processor, the following steps are implemented: Store the institutional information of each financial institution through cloud computing technology and a distributed file system, and the institutional information includes institutional hierarchy information and the bound personnel information of each level. Obtain the specified task plan information, and construct subtasks of the involved financial institutions through the task plan information; the task plan information includes a task plan identifier, a management department, a task name, the involved financial institutions, a task description, a task type, the number of task submission time nodes and each specific time, and task attributes. Construct a process monitoring task for each subtask, and store the process monitoring task in the monitoring task pool. Send the subtasks to the corresponding financial institutions, and in response to the successful feedback of the sending, start the process monitoring tasks of the subtasks. Based on the number of task submission time nodes and the specific time, obtain the subtask completion process information according to the monitoring results of the process monitoring tasks. Determine the supervision reminder level of the unfinished subtasks according to the task plan information and the subtask completion process information, and send a supervision reminder to the submitter according to the supervision reminder level.

[0113] The foregoing description of the disclosed embodiments enables those skilled in the art to practice or use the present invention. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the general principles defined herein may be implemented in other embodiments without departing from the spirit or scope of the present invention. Thus, the present invention is not intended to be limited to the embodiments shown herein but is to be accorded the widest scope consistent with the principles and novel features disclosed herein.

Claims

1. A task management method for a financial institution, characterized in that: The following steps are involved: The institutional information of each financial institution is stored through cloud computing technology and distributed file system, wherein the institutional information includes the institutional level information and the binding personnel information of each level; Obtaining the formulated task plan information, and constructing the subtasks of the financial institutions involved through the task plan information; the task plan information includes the task plan identifier, management department, task name, financial institutions involved, task description, task type, number of task submission time nodes and each specific time, and task attributes; Build a process monitoring task for each subtask and store the process monitoring task in the monitoring task pool; Send the subtask to the corresponding financial institution, and in response to the feedback of successful sending, start the progress monitoring task of the subtask; Based on the number and specific time of task submission time nodes, obtain subtask completion process information according to the monitoring results of the process monitoring task; Determine the supervision reminder level of unfinished subtasks based on the task plan information and subtask completion progress information, and issue a supervision reminder to the reporter based on the supervision reminder level.

2. The task management method of a financial institution according to claim 1, characterized in that: The subtasks of the financial institutions involved are constructed through the task plan information, including: Parse the current task plan information to obtain the task plan identifier, the number of financial institutions involved, the number of task submission time nodes and the specific time; Expand the current subtask list by the number of financial institutions involved, with one row for each financial institution. Constructing subtasks of the financial institutions involved through the task plan information, including associating the task plan information with the subtasks and constructing unique identifiers of the subtasks; Randomly sort the subtasks, fill the task solution identifier into the first column of the corresponding row of the subtask list according to the sorting order, and fill the subtask unique identifier into the second column of the corresponding row of the subtask list to form a mapping relationship between the subtask and the task solution; In the fourth column of the corresponding row of the subtask list, configure the task completion status information of the subtask. The task completion status information is stored in the form of [subtask completion status indicator: subtask completion percentage]. The task completion status indicator is used to indicate whether the subtask is completed; Fill in the fifth column of the corresponding row in the subtask list with the number of task submission time nodes of the subtask; The task submission information of the subtask is filled in the columns after the fifth column of the corresponding row in the subtask list in the order of the specific submission time. The task submission information is stored in the subtask list in the form of [node i: specific time: actual time: node completion status identifier: node completion evaluation identifier], where node i refers to the i-th node to be completed, the actual time is used to identify the actual data reporting time of node i, the completion status identifier is used to indicate whether the node is completed, and the completion evaluation identifier is used to indicate whether the node is completed before the specific time.

3. The task management method of a financial institution according to claim 2, characterized in that: Build a process monitoring task for each subtask and store the process monitoring task in the monitoring task pool, including: Build a process monitoring task for each subtask, including building a unique identifier for the process monitoring task; Store the constructed process monitoring task into the monitoring task pool; Get the number of built process monitoring tasks; Expand the current number of process monitoring task lists according to the number of process monitoring task builds obtained, with each process monitoring task corresponding to one line; Fill the third column of the corresponding row in the subtask list with the unique ID of each subtask's process monitoring task; The first column and the third column of the corresponding row of the extracted subtask list are respectively filled into the first column and the second column of the corresponding row expanded by the process monitoring task list, that is, the unique identifier of the process monitoring task is filled into the second column of the process monitoring task list, and the corresponding task scheme identifier is filled into the matching first column; The fourth column of the process monitoring task list is filled with the monitoring task completion status indicator.

4. The task management method of a financial institution according to claim 3, characterized in that: Based on the number and specific time of task submission time nodes, the subtask completion process information is obtained according to the monitoring results of the process monitoring task, including: Obtain the monitoring results of the process monitoring task in real time, including the actual time of receiving the data report and the number of received data reports; Obtain subtask completion progress information based on monitoring results, including: (1) Check whether the number of received data reports reaches the number of task reporting time nodes of the subtask, and calculate the completion percentage of the subtask. Update the fourth column information of the corresponding row in the subtask list according to the detection and calculation results, and update the fourth column information of the corresponding row in the process monitoring task list; (2) Update the task submission information column of the corresponding row in the subtask list based on the actual time of the received data report and the number of received receipt reports.

5. The task management method of a financial institution according to claim 4, characterized in that: The supervision reminder level of unfinished subtasks is determined based on the task plan information and subtask completion progress information, including: Periodically extract unfinished subtasks from the subtask list and record them as subtasks to be supervised; Get the task plan identifier of the subtask to be supervised from the subtask list; Extracting task attributes from task plan information according to the task plan identifier; Based on the pre-configured attribute importance, determining the first parameter evaluation value of the subtask to be supervised according to the task attribute; the first parameter evaluation value is proportional to the attribute importance; Get the specific time of the next node to be completed of the supervised subtask from the subtask list, and calculate the time difference between the current time and the specific time; Based on the pre-configured correspondence between the time difference interval and the evaluation value, the second parameter evaluation value of the subtask to be supervised is determined according to the calculated time difference; the second parameter evaluation value is inversely proportional to the length of the time difference; The reminder level of the subtask to be supervised is determined according to the first parameter evaluation value and the second parameter evaluation value.

6. The task management method of a financial institution according to claim 5, characterized in that: The method further comprises the following steps: Periodically checking the monitoring task completion status of each process monitoring task in the process monitoring task list; If the monitoring task is in the completed state, the monitoring task will be deleted from the monitoring task pool and the monitoring task list.

7. The task management method of a financial institution according to any one of claim 6, characterized in that: The financial institutions involved in the mission plan information include the institutional level at which the mission is to be executed; When issuing a subtask to a corresponding financial institution, issue the subtask to the institution level that executes the task, and obtain the personnel information bound to the institution level that executes the task; The monitoring results also include the information of the person who reported the data; Before obtaining the monitoring results of the process monitoring task in real time, the following steps are also included: Check whether the personnel information reported in this data is consistent with the bound personnel information; If they are consistent, the monitoring result is determined to be valid; If they are inconsistent, the monitoring result is deemed invalid.

8. A task management system for a financial institution, characterized in that: include, An institution information storage module is used to store the institution information of each financial institution through cloud computing technology and distributed file system, wherein the institution information includes the institution level information and the binding personnel information of each level; A subtask construction module is used to obtain the formulated task plan information and construct the subtasks of the financial institutions involved through the task plan information; the task plan information includes the task plan identifier, management department, task name, financial institutions involved, task description, task type, number of task submission time nodes and each specific time, and task attributes; A process monitoring task building module is used to build a process monitoring task for each subtask and store the process monitoring task in a monitoring task pool; A subtask issuing module is used to issue the subtask to the corresponding financial institution, and in response to feedback of successful issuance, start the progress monitoring task of the subtask; The subtask completion process acquisition module is used to obtain the subtask completion process information based on the number of task reporting time nodes and specific time and the monitoring result of the process monitoring task; The supervision reminder module is used to determine the supervision reminder level of unfinished subtasks based on the task plan information and the subtask completion process information, and send supervision reminders to the reporter based on the supervision reminder level.

9. A terminal, characterized in that: include: A memory for storing a financial institution task management program; A processor is used to implement the steps of the financial institution task management method as described in any one of claims 1-7 when executing the financial institution task management program.

10. A computer-readable storage medium, characterized in that: The readable storage medium stores a financial institution task management program, and when the financial institution task management program is executed by the processor, the steps of the financial institution task management method according to any one of claims 1 to 7 are implemented.

Images