Operation and maintenance affairs collection and management system
Through the design of the operation and maintenance transaction collection and management system, the to-do transactions of each business system are collected and analyzed in real time and pushed to the target user, solving the problem of operation and maintenance personnel missing or missing transaction processing when switching between multiple business systems. It realizes unified management of transactions and prompt prompts, and improves operation and maintenance efficiency.
Patent Information
- Application Number
- CN202011292614.3
- Authority / Receiving Office
- CN · China
- Patent Type
- Patents(China)
- Current Assignee / Owner
- Filing Date
- 2020-11-18
- Publication Date
- 2024-11-19
- Estimated Expiration
- 2040-11-18
AI Technical Summary
Operations and maintenance personnel are prone to missing transactions when switching between multiple business systems, resulting in adverse effects and lack of unified management and prompt mechanisms.
A system for collection and management of operations and maintenance transactions is designed, including transaction information collection module, transaction information processing module, batch information collection module, batch information management module and task display processing module to collect and analyze the to-do business of each business system in real time. , push to the corresponding target user to ensure timely processing.
It effectively avoids users missing to-do transactions or missing processing time limits, realizes unified management and timely prompts for transactions of multiple business systems, and improves operation and maintenance efficiency and accuracy.
Smart Images

Figure CN112396397B_ABST
Abstract
Description
Technical Field
[0001] The present invention relates to the field of computer technology, and in particular to an operation and maintenance affairs collection and management system. Background Art
[0002] As banking business continues to expand, the number and types of servers in bank data centers, the business functions of application systems, and the types of software technologies used are also growing rapidly. The number of transactions that need to be handled daily has increased exponentially, so data center operation and maintenance personnel often need to switch between multiple different business systems to handle transactions on each business system.
[0003] However, in this way of working, the operation and maintenance personnel are prone to miss some business system transactions or miss the prescribed transaction processing time limit, which will cause adverse effects. Therefore, it is necessary to provide a solution that can uniformly manage and prompt transactions on multiple business systems. Summary of the invention
[0004] In response to the needs of the above-mentioned prior art, the present application provides an operation and maintenance affairs collection and management system to provide a unified management solution for affairs of multiple business systems.
[0005] The present application provides an operation and maintenance affairs collection and management system, including:
[0006] A transaction information collection module is used to collect the transaction information of each pending transaction in each business system in real time; wherein the transaction information includes transaction attributes and transaction status;
[0007] A transaction information processing module, used to parse the transaction information of each pending transaction according to a preset task template, and obtain a pending task corresponding to each pending transaction; wherein each transaction state of the pending transaction corresponds to a pending task;
[0008] A batch information collection module, used to collect the identity information of each user in each of the business systems according to a preset update cycle; wherein the identity information is used to indicate the role and user group to which the user belongs in the corresponding business system;
[0009] A batch information management module, used to determine at least one corresponding target user for each of the pending tasks that is not configured with a corresponding target user, according to the identity information and the target roles or target user groups included in the pending tasks; wherein the target user corresponding to the pending tasks refers to a user who has processing authority for the pending tasks;
[0010] The task display processing module is used to push each of the pending tasks to the target user corresponding to the pending task, so as to prompt the target user to handle the pending affairs corresponding to the pending task.
[0011] Optionally, the transaction information processing module parses the transaction information of each of the pending transactions according to a preset task template to obtain a pending task corresponding to each of the pending transactions, specifically for:
[0012] Obtaining a task template; wherein the task template includes multiple task fields;
[0013] For each of the pending tasks, the field value corresponding to each task field of the task template is extracted from the task information of the pending task, and the field value is added to the task template to obtain the pending task corresponding to the pending task.
[0014] Optionally, the transaction information collection module is further used to:
[0015] Real-time collection of information update operations of each pending transaction in the current transaction state in each of the business systems;
[0016] or,
[0017] The information update operation of each pending transaction in the business system under the current transaction state is collected according to a preset collection period.
[0018] Optionally, the system further includes:
[0019] The custom task module is used to obtain the custom task information input by the user in the operation and maintenance affairs collection and management system, and generate corresponding custom tasks to be processed based on the custom task information.
[0020] Optionally, when the batch information management module determines at least one corresponding target user for each of the pending tasks that is not configured with a corresponding target user according to the identity information and the target roles or target user groups included in the pending tasks, it is specifically configured to:
[0021] For each pending task that is not configured with a corresponding target user, if the pending task contains a target role, determine each user belonging to the target role according to the identity information, and determine each user belonging to the target role as the target user corresponding to the pending task;
[0022] For each pending task that is not configured with a corresponding target user, if the pending task contains a target user group, each user belonging to the target user group is determined according to the identity information, and each user belonging to the target user group is determined as the target user corresponding to the pending task.
[0023] Optionally, when the task display processing module pushes each of the pending tasks to a target user corresponding to the pending tasks, it is specifically used to:
[0024] After the current user logs in to the operation and maintenance affairs collection and management system, it is determined that each corresponding target user includes the pending tasks of the current user; wherein the current user refers to any user;
[0025] A task display page is sent to the terminal device of the current user; wherein the task display page displays pending tasks for each corresponding target user including the current user.
[0026] Optionally, the task display processing module is further used to:
[0027] For any of the pending tasks, receiving a user's request for handling the pending affairs corresponding to the pending task;
[0028] If the business system to which the pending affairs corresponding to the pending task belongs provides a remote processing interface, the processing interface of the pending affairs corresponding to the pending task is pushed to the user who sent the processing request;
[0029] Taking the operation of the user who sent the processing request on the processing interface as the updating basis, calling the remote processing interface to update the pending affairs corresponding to the pending task;
[0030] If the business system to which the pending transaction corresponding to the pending task belongs does not provide a remote processing interface, a jump link to the business system to which the pending transaction corresponding to the pending task belongs is sent to the user who sent the processing request, so that the user who sent the processing request jumps to the business system to which the pending transaction corresponding to the pending task belongs.
[0031] Optionally, the system further includes:
[0032] The workload statistics module is used to calculate the workload of each user within a preset time period based on the number and weight of each category of pending tasks processed by the user within the preset time period; wherein the weight of each category of pending tasks is determined based on the complexity of the pending tasks of that category.
[0033] Optionally, the system further includes:
[0034] The task reminder module is used to determine a corresponding reminder rule for each of the pending tasks, and to periodically send a task processing reminder to a target user corresponding to the pending task based on the reminder rule.
[0035] Optionally, when the task reminder module sends a task processing reminder to a target user corresponding to the task to be processed, it is specifically used to:
[0036] Send a task reminder email, task reminder SMS or task reminder pop-up window to the target user corresponding to the pending task.
[0037] The present application provides an operation and maintenance affairs collection and management system, including: a transaction information collection module that collects the transaction information of each pending transaction in each business system in real time, a transaction information processing module that parses the transaction information of pending transactions according to task templates to obtain pending tasks corresponding to the pending transactions, a batch information management module that determines the corresponding target users for pending tasks that are not configured with corresponding target users according to the user's identity information and the target role or target user group of the pending tasks, and a task display processing module that pushes pending tasks to the target users corresponding to the pending tasks to prompt the target users to handle the pending transactions corresponding to the pending tasks. By collecting the transaction information of pending transactions of each business system and parsing them into corresponding pending tasks, this solution can push the user's pending transactions in each business system to the corresponding users, preventing users from missing pending transactions or missing the processing deadline. BRIEF DESCRIPTION OF THE DRAWINGS
[0038] In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings required for use in the embodiments or the description of the prior art will be briefly introduced below. Obviously, the drawings described below are only embodiments of the present invention. For ordinary technicians in this field, other drawings can be obtained based on the provided drawings without paying creative work.
[0039] Figure 1 A schematic diagram of the structure of an operation and maintenance affairs collection and management system provided in an embodiment of the present application;
[0040] Figure 2 A schematic diagram of the status of a to-do task provided in an embodiment of the present application;
[0041] Figure 3 A flowchart of a method for parsing transaction information into corresponding tasks to be processed provided in an embodiment of the present application;
[0042] Figure 4 A schematic diagram of the correspondence between a user and a role of a business system provided in an embodiment of the present application;
[0043] Figure 5 A schematic diagram of a display interface for tasks to be processed provided in an embodiment of the present application;
[0044] Figure 6 A schematic diagram of a processing flow of a task to be processed provided in an embodiment of the present application. DETAILED DESCRIPTION
[0045] The following will be combined with the drawings in the embodiments of the present invention to clearly and completely describe the technical solutions in the embodiments of the present invention. Obviously, the described embodiments are only part of the embodiments of the present invention, not all of the embodiments. Based on the embodiments of the present invention, all other embodiments obtained by ordinary technicians in this field without creative work are within the scope of protection of the present invention.
[0046] The present application embodiment provides an operation and maintenance affairs collection and management system, such as Figure 1 As shown, the system may include the following modules:
[0047] The transaction information collection module 101 is used to collect the transaction information of each pending transaction in each business system in real time.
[0048] The transaction information includes transaction attributes and transaction status.
[0049] The transaction information processing module 102 is used to parse the transaction information of each to-do transaction according to a preset task template to obtain a to-be-processed task corresponding to each to-do transaction.
[0050] The batch information collection module 103 is used to collect the identity information of each user in each business system according to a preset update period.
[0051] The identity information is used to indicate the role and user group to which the user belongs in the corresponding business system.
[0052] The batch information management module 104 is used to determine at least one corresponding target user for each task to be processed that is not configured with a corresponding target user according to the identity information and the target roles or target user groups included in the task to be processed.
[0053] The target user corresponding to the task to be processed refers to a user who has the processing authority for the task to be processed.
[0054] The task display processing module 105 is used to push each pending task to a target user corresponding to the pending task, so as to prompt the target user to handle the pending affairs corresponding to the pending task.
[0055] Optionally, the system provided in the embodiment of the present application may further include:
[0056] The custom task module 106 is used to obtain the custom task information input by the user in the operation and maintenance affairs collection and management system, and generate corresponding custom tasks to be processed based on the custom task information.
[0057] The workload statistics module 107 is used to obtain, for each user, the task weight of each pending task processed by the user within a preset time period, and accumulate all the obtained task weights to obtain the workload of the user within the preset time period.
[0058] The task weight of the task to be processed is determined according to the complexity of the task to be processed.
[0059] Optionally, the system further includes:
[0060] The task reminder module 108 is used to determine a corresponding reminder rule for each pending task, and to periodically send a task processing reminder to a target user corresponding to the pending task based on the reminder rule.
[0061] The operation and maintenance affairs collection and management system provided in this application can be considered as a computer program for unified management of pending affairs of multiple business systems, such as Figure 1 Each module in the system shown can be considered as a plurality of subroutines in the computer program for realizing corresponding functions.
[0062] Specifically, the programs involved in the back-end business logic processing in the operation and maintenance transaction collection and management system provided by this application can be developed using the Java-based application development framework SpringBoot. SpringBoot is an existing out-of-the-box JAVA application development framework. Using this development framework can simplify the software configuration process of application development, allowing developers to focus on business logic implementation. Therefore, SpringBoot is widely used in the field of rapid application development.
[0063] The front-end page in the operation and maintenance affairs collection and management system can utilize Vue and AntDesign. For example, the task display processing module 105 pushes the pending tasks to the corresponding target users, and it is necessary to display the front-end page containing several pending tasks on the target users' terminal devices for the target users to browse.
[0064] Vue is a progressive front-end Javascript framework with data-driven views, high degree of componentization, and fast running speed. It is suitable for front-end page logic development with high timeliness and high degree of componentization, and is suitable for the characteristics of fast data update and plug-in update of this system. AntDesign is an existing set of page UI component libraries with the characteristics of few invalid graphics, prominent key points, and strong significance. Using this component library allows users to focus on the effective information that needs attention in the page when using the system provided by this application.
[0065] The transaction information acquisition module 101 needs to obtain transaction information from each business system in real time. At the same time, the transaction information acquisition module needs to pass the collected transaction information to the transaction information processing module for analysis by the transaction information processing module. The above functions can be implemented specifically through the message system Kafka. Kafka is a distributed message system that supports partitioning and multiple replicas. Kafka is developed based on the open source distributed application coordination service Zookeeper. The biggest feature of Kafka is that it can process a large amount of data in real time to meet various demand scenarios, such as log collection, user activity tracking, streaming processing, etc. It has the characteristics of scalability, persistence, high concurrency, etc. Therefore, Kafka is suitable for the transaction information acquisition module 101 of this application to obtain transaction information from multiple business systems, and the subsequent transaction information processing module 102 to parse and process one by one and store continuously, while meeting the expansion requirements of the subsequent system.
[0066] The operation and maintenance affairs collection and management system provided by this application involves the collection and processing of a large amount of data, so it is necessary to use a database to store this data. Specifically, in this application, the database MySql can be used to store this data. MySql is an open source relational database management system. It has the characteristics of small size, high speed, and low cost. It can be well managed and maintained without a specific database administrator, meeting the data management requirements of this system.
[0067] The above are the development technologies and tools used to implement the operation and maintenance affairs collection and management system provided by this application. The following is a detailed description of each module in the operation and maintenance affairs collection and management system of this application.
[0068] As mentioned above, the transaction information collection module 101 in the present application is used to collect the transaction information of each pending transaction in each business system in real time. The collected transaction information of the pending transaction can be persistently stored in the database through the transaction information collection module.
[0069] The collection method may be that each business system pushes the transaction information of its own pending transactions to the transaction information collection module via the aforementioned message framework Kafka in real time.
[0070] In addition, the transaction information collection module can also collect in real time the information update operations of each pending transaction in each business system under the current transaction status.
[0071] In this application, to-do tasks (also referred to as tasks) are used to refer to various process work orders, routine operations and other work items that need to be handled in the operation and maintenance of the data center. Including but not limited to: various IT process work orders in the IT server management system (IT Service Management, ITSM), routine system inspections and emergency drills, temporary OA needs, sudden alarm handling, various single tasks assigned by department leaders verbally or by email, and work content completed by groups or virtual groups within a period of time. The business system refers to the work software or pages used to handle the corresponding tasks, such as: IT management service system, duty system, alarm system, drill system, etc. For example, to process IT process work orders, you need to log in to the IT management service system, and to perform routine system inspections, you need to log in to the duty system.
[0072] It should be noted that the operation and maintenance transaction collection and management system provided by this application (hereinafter referred to as this system) is intended to collect pending transactions of all other business systems in the data center, and then provide a unified display and reminder platform. As the work of the data center continues to be refined, the types and sources of transactions will continue to increase, so the real-time data collection achieved by the transaction information collection module must meet the ability of continuous horizontal expansion. This system publishes the transaction information of each pending transaction to this system in real-time push mode by each business system, and then the message consumers in the system (ie, the transaction information abstraction module) parse them one by one.
[0073] The transaction information of a pending transaction may include attribute information of the transaction, such as the creation time of the transaction, the business system to which it belongs, the content that needs to be processed, the person designated to handle the transaction (or the role or user group designated to handle the transaction), etc. It may also include status information of the transaction, and the status information is used to indicate the current transaction status of the transaction.
[0074] A transaction can have multiple transaction states, each of which is equivalent to a step in the process of handling the transaction. For example Figure 2In the state diagram of pending transactions shown, a transaction of type Z in business system A can have several transaction states: creation, transfer, execution, review, and end. This is equivalent to completing the steps of creation, transfer, execution, review, and end in sequence to complete a transaction of type Z in business system A. Each transaction state has corresponding specific work content. After the work content in the current transaction state is completed, the transaction will automatically switch to the next transaction state. For example, after the operation and maintenance personnel complete the work content corresponding to the creation state of a transaction of type Z, the transaction state of this transaction will change from creation to transfer. After the corresponding operation and maintenance personnel complete the work content in the transfer state, the transaction state of this transaction will change to execution state, and so on until the transaction is finally completed.
[0075] In any transaction state, the operation and maintenance personnel can update the corresponding information multiple times when handling the corresponding work content. For example, for transactions in the transfer state, the corresponding operation and maintenance personnel fill in the corresponding form to which (or which) operation and maintenance personnel the transaction needs to be transferred to handle, the handling time limit and guidance, etc. After filling in the above information for the first time, the operation and maintenance personnel can update the filled information multiple times until they are sure that the filled information is correct, and then confirm that the work of the current transaction state has been completed on the corresponding business system, and then the transaction will enter the next transaction state. For example, Figure 2 In the example, a transaction of type Z undergoes three information update operations while in the circulation state.
[0076] Correspondingly, the transaction information collected by the transaction information collection module may also include each information update operation occurring in the current transaction state.
[0077] The transaction information collected by the transaction information collection module can be filled in the message queue and transmitted to the subsequent transaction information processing module through the message queue. In addition, it can also be persisted in the database of this system. Among them, the database used for persistent storage of transaction information can be called the transaction pool of this system.
[0078] In this system, as mentioned above, the transaction information processing module is used to parse the transaction information of each to-do task according to the preset task template to obtain the to-do task corresponding to each to-do task. This process is equivalent to extracting the key content of each to-do task and abstracting and normalizing it into a task in this system. After passing through the transaction information processing module, each to-do task will be converted into a corresponding to-do task. The to-do tasks in this application can be understood as abstracted to-do tasks.
[0079] The abstraction of transactions can be understood as the process of extracting common and standardized information fields of transactions, such as: transaction source, content overview, start time, completion time, current status, processing personnel, workload weight, etc., so as to normalize transactions from different sources.
[0080] Since the to-do tasks collected by this system come from multiple business systems, their key fields and information content vary greatly. This system aims to display common information that users need to pay attention to on a single page. Therefore, a normalized and abstracted algorithm is used to extract key information from the transaction information of the original business system, and abstract the tasks with multiple sources and high degree of granularity into a unified data type in this system, namely, to-do tasks (also referred to as tasks).
[0081] It should be noted that in this system, each transaction status of a pending transaction corresponds to a different pending task. For example, a transaction in the previous article can have transaction statuses such as creation, circulation, execution, and review. Correspondingly, when the transaction is in the creation status, it corresponds to the creation task. When it is in the circulation status, execution status, and review status, the corresponding tasks are the circulation task, execution task, and review task respectively.
[0082] When any transaction switches from the previous transaction state to the next transaction state, the system will mark the task corresponding to the previous transaction state as completed. At the same time, the transaction information collection module will detect the new transaction state of the transaction, and the corresponding transaction information processing module will generate a new task for the new transaction state.
[0083] For example, when a transaction changes from a creation state to a circulation state, the original creation task of the transaction in the system will be marked as completed, and the transaction information processing module will generate a circulation task for the transaction.
[0084] In conjunction with the above discussion, please refer to Figure 3 In this system, the transaction information processing module parses the transaction information of each pending transaction according to the preset task template, and obtains the specific process of the pending task corresponding to each pending transaction as follows:
[0085] S301: Obtain task templates and task information of pending tasks.
[0086] The task template can be understood as a blank data structure predefined in the system, which includes multiple task fields. For example, the following Table 1 lists the task fields defined in an optional task template.
[0087] Table 1
[0088] Task Fields Field Value Source System Transaction Type Transaction Number Current transaction status Processing Transaction Summary Current processing group Current Processor Task Notes
[0089] In the above task template, the current processor and the current processing group are used to indicate which maintenance personnel or user group is assigned to process the pending task.
[0090] S302: extracting the field value corresponding to each task field of the task template from the task information of the to-do task.
[0091] For any task field, when the field value of this task field is clearly recorded in the transaction information of the to-do task, this field value can be directly copied from the transaction information; when the field value of this task field is not clearly recorded in the transaction information, the content in the transaction information can be cut, spliced and combined according to the preset processing rules to obtain the field value corresponding to this task field.
[0092] Taking the transaction summary field in Table 1 as an example, when the transaction information does not clearly state which part of the content is the transaction summary, the transaction reason, transaction details and other information in the transaction information can be cut according to the preset processing rules, and these information can be spliced to obtain the transaction summary.
[0093] If the field value of a task field still cannot be obtained through the above method, the field value of this task field can be set to empty (null). For example, when a transaction is an intra-group transaction, its transaction information does not contain a specific handler. Therefore, the field value of the "current handler" field in Table 1 cannot be obtained from the transaction information through the above method. Therefore, when generating the task corresponding to this intra-group transaction, the field value of the "current handler" can be set to empty.
[0094] S303: Fill the extracted field values into the task template one by one to obtain the pending tasks corresponding to the pending affairs.
[0095] For example, for each task field in Table 1 above, the corresponding field value can be extracted from the transaction information of the to-do transaction, such as the business system from which the to-do transaction comes and the transaction number field value, and then added to the above task template accordingly. In this way, the to-be-processed task corresponding to the to-do transaction can be obtained.
[0096] After adding corresponding field values to the task template shown in Table 1 above, a task to be processed can be obtained as shown in Table 2 below:
[0097] Table 2
[0098] Task Fields Field Value Source System Business System A Transaction Type Z Type Transaction Number ID000000 Current transaction status Review Status Processing Processing Transaction Summary Review completed forms Current processing group First user group Current Processor User X Task Notes none
[0099] Through Figure 3 The method shown can abstract each pending transaction into a corresponding task to be processed, and realize the correspondence between the task to be processed and the pending transaction.
[0100] The abstracted tasks of external to-do items and the custom to-do tasks maintained in this system (also referred to as custom tasks) are the full range of tasks that data center staff need to handle on a daily basis.
[0101] The batch information collection module 103 is used to collect the identity information of each user in each business system according to a preset update period.
[0102] Since the user's identity information generally does not change frequently, batch collection can be performed once every certain update period through the batch information collection module.
[0103] That is to say, the batch information collection module periodically imports batches of user information with low real-time performance in various business systems and persists it in the database.
[0104] The user's identity information may include the user's identification in the business system, permissions, the user group to which he belongs, the role he belongs, and other information.
[0105] It should be noted that each user has corresponding identity information in each business system, and the identity information of the same user in different business systems is generally different. For example, the same user may belong to different user groups and different roles in different business systems, and the corresponding permissions of the user in different business systems are also different. At the same time, a user may have multiple roles in a system, or may belong to multiple user groups.
[0106] like Figure 4 As shown, user 1 belongs to role a in business system A, and can handle work in the execution state of transaction type A, and work in the approval state of transaction type B. In business system B, user 1 belongs to role b and role c, and can handle work in the application state and implementation state of transaction type C. All of this information needs to be collected by the batch information collection module as user identity information and stored in the system database to be provided to the subsequent task display processing module for use.
[0107] The batch information management module 104 is used to determine at least one corresponding target user for each task to be processed that is not configured with a corresponding target user according to the identity information and the target roles or target user groups included in the task to be processed.
[0108] For any pending task, the corresponding business system can specify a corresponding target user for each state of the pending task, that is, it is stipulated that the task needs to be handled by a designated operation and maintenance personnel when it is in a specific state.
[0109] Correspondingly, the business system also has the following situations:
[0110] For a certain to-do item, the business system does not specify a specific operation and maintenance personnel as the person who handles this to-do item, but only specifies that the to-do item is executed by a certain role or a certain user group.
[0111] In the above case, the batch information management module is required to determine the target users of the pending tasks corresponding to this to-do transaction according to the specified role or user group, that is, to determine which users need to handle the pending tasks.
[0112] Optionally, when the batch information management module determines at least one corresponding target user for each pending task that is not configured with a corresponding target user according to the identity information and the target roles or target user groups included in the pending task, it is specifically used to:
[0113] For each pending task that is not configured with a corresponding target user, if the pending task contains a target role, each user belonging to the target role is determined according to the identity information, and each user belonging to the target role is determined as the target user corresponding to the pending task;
[0114] For each pending task that is not configured with a corresponding target user, if the pending task contains a target user group, each user belonging to the target user group is determined according to the identity information, and each user belonging to the target user group is determined as the target user corresponding to the pending task.
[0115] For example, the target role of a task is role a, and the users belonging to role a include user 1, user 2 and user 3. Therefore, the batch information management module can determine user 1, user 2 and user 3 as the target users of this pending task, that is, specify that the to-do items corresponding to this pending task are to be processed by any one of user 1, user 2 and user 3.
[0116] In other words, for a certain to-do task, the task processing process may not necessarily be assigned to a specific person, but may also flow to a user group or user role, each of which contains multiple users. In order to display the abstracted task to the user who needs to handle the task or has the authority to handle the task, this system associates the task type in the task with the user who belongs to the corresponding role or user group in the batch information management module, so that the task can be displayed to the users who are really interested in the task without screening and manual judgment. This is also the advantage of this system's transaction collection display over other full transaction collection display methods for order creation.
[0117] The task display processing module 105 is used to push each pending task to a target user corresponding to the pending task, so as to prompt the target user to handle the pending affairs corresponding to the pending task.
[0118] Optionally, when the task display processing module pushes each pending task to a target user corresponding to the pending task, it is specifically used to:
[0119] After the current user logs in to the operation and maintenance affairs collection and management system, it is determined that each corresponding target user includes the pending tasks of the current user; wherein the current user refers to any user;
[0120] A task display page is sent to the terminal device of the current user; wherein the task display page displays pending tasks for each corresponding target user including the current user.
[0121] An optional task display interface such as Figure 5 As shown, after normalization, three tasks 1, 2 and 3 can be obtained, among which the pending transactions corresponding to tasks 1 and 2 are type A transactions, and the business system to which the corresponding pending transactions belong is business system X. The pending transaction corresponding to task 3 is type B transaction of business system Y. The user groups specified by tasks 1, 2 and 3 are user groups h, i and j respectively. Among them: user group h includes users 1, 2 and 3; user group i includes users 1, 4 and 5; user group j includes users 1, 4 and 7.
[0122] For users, user 1's pending tasks are task 1, task 2, and task 3, user 2's pending tasks are task 1, user 4's pending tasks are task 2 and task 3, and so on. Through the above correspondence, the task display processing module can push tasks to users who need to process or want to pay attention to the task.
[0123] The task display processing module can generate Figure 5 The interface shown in the figure is sent to the corresponding user's terminal device when the user logs in to the system. Figure 5 The user can see how many tasks are currently pending. Figure 5 Click on the task numbers such as Task 1, Task 2, etc. in the interface shown to view the task details, that is, to view the detailed information of the corresponding to-do items.
[0124] Furthermore, in order to meet the one-stop processing requirements of transactions and realize the function of directly processing transactions in other business systems in this system, the task display processing module of this system can also support users to Figure 6 The process shown handles the corresponding to-do items:
[0125] S601: Receive a user's request for handling pending tasks.
[0126] The request for handling pending tasks can also be considered as the request for handling pending tasks corresponding to the pending tasks. Figure 4 In the display interface shown, click on the task box where any pending task is located to view the task details of the pending task, and after viewing, select the option to process the task, thereby inputting a processing request for the pending transaction corresponding to this pending task into the system.
[0127] S602: Determine whether the business system to which the pending task belongs provides a remote processing interface.
[0128] If the business system to which the pending task belongs provides a remote processing interface, step S603 is executed; otherwise, if the business system to which the pending task belongs does not provide a remote processing interface, step S604 is executed.
[0129] S603: Provide a processing interface for to-do tasks, and update the to-do tasks corresponding to the pending tasks based on the user's operations in the processing interface.
[0130] That is to say, if the business system to which the pending tasks belong provides a remote processing interface, users can handle the pending tasks directly in this system, such as filling in the required documents directly in this system, editing the corresponding documents, etc. The data needed in the process of handling can be obtained by this system directly from the business system to which the pending tasks belong by calling the aforementioned remote processing interface. After the user completes the handling, this system can access the business system to which the pending tasks belong through the remote processing interface provided by the business system, and then directly update the pending tasks in the business system based on the user's operations.
[0131] In this way, on the premise that the corresponding business system provides a remote processing interface, users do not need to repeatedly switch to multiple different business systems to handle multiple transactions. They only need to operate in the corresponding processing interface of this system to directly complete the processing of pending transactions in multiple business systems.
[0132] S604: Determine whether the business system to which the pending task belongs provides a jump link.
[0133] If the business system to which the pending task belongs provides a jump link, step S605 is executed; otherwise, if the business system to which the pending task belongs does not provide a jump link, step S606 is executed.
[0134] S605: Send a jump link to the business system to which the pending task belongs to the user, so that the user jumps to the processing interface of the business system to which the pending task belongs.
[0135] The jump link is the Uniform Resource Locator (URL) of the interface corresponding to the business system. If the business system provides a jump link to the corresponding processing interface, the system can directly send the jump link to the terminal device of the user who needs to process the pending affairs of the corresponding business system. The user can directly log in to the processing interface of the corresponding business system by clicking the jump link, so as to directly process the pending affairs in the business system to which the pending affairs belong.
[0136] For some business systems that are not convenient to provide remote processing interfaces, jump links can be provided for users to click. In this way, users can directly access the corresponding business systems through this system. There is no need to manually record which business system the to-do tasks are located in, nor do users need to manually log in to the corresponding business system. This significantly simplifies the process of users switching from this system to the business system to which the to-do tasks belong, thereby improving the efficiency of transaction processing.
[0137] S606: Output jump failure prompt information.
[0138] The jump failure prompt message is used to prompt the user to manually switch to the business system to which the pending transaction belongs to handle the corresponding transaction.
[0139] It should be understood that, according to the previous description of the transaction information collection module 101, the above three methods of handling pending transactions in the business system, involving the update of relevant information of the pending transactions (including changes in transaction status, and update records of data under a certain transaction status) will be automatically collected by the transaction information collection module 101 and synchronously collected into this system and automatically displayed to the user through the task display processing module, and there is no need to perform additional confirmation flow steps in this system.
[0140] As mentioned above, the system further includes a custom task module 106 for acquiring custom task information input by a user in the operation and maintenance affairs collection and management system, and generating corresponding custom tasks to be processed based on the custom task information.
[0141] In other words, the custom task module is mainly used for daily work items that are not circulated and handled in other business systems, with this system as the main body of record circulation, providing input and transfer functions. Such work items mainly include work arranged verbally or by email by supervisors, tracking tasks within the department, etc.
[0142] For example, after a supervisor verbally assigns a work item to an operation and maintenance personnel, the operation and maintenance personnel can log in to the system and fill in the custom task form in the custom task module according to the supervisor's description, thereby generating a custom pending task in the system through the custom task module.
[0143] It should be noted that in this system, the processing method of customized pending tasks is the same as that of pending tasks generated by the transaction information processing module in the previous article based on transaction information. That is to say, this system can use the same processing method as the aforementioned pending tasks to display customized pending tasks, as well as subsequent notification reminders and other management operations.
[0144] By setting up a custom task module, this system can achieve unified management of all transactions in the data center, that is, it can manage the transactions of multiple online business systems, and at the same time manage offline verbal transactions in the form of custom tasks.
[0145] The system further includes a workload statistics module 107 for obtaining, for each user, a task weight of each pending task processed by the user within a preset time period, and accumulating all the obtained task weights to obtain the user's workload within the preset time period.
[0146] That is to say, in this system, the workload statistics module is mainly used to quantify and display the tasks completed by each operation and maintenance personnel based on information such as the task weights of tasks corresponding to different types of transactions.
[0147] The task weight of the task to be processed is determined according to the complexity of the task to be processed.
[0148] Workload: For any operation and maintenance personnel, a weight is set for each task to be processed according to the difficulty and time taken by the operation and maintenance personnel. The sum of the weights of all tasks completed by the operation and maintenance personnel within a period of time is calculated to obtain the workload of the operation and maintenance personnel within a period of time.
[0149] Specifically, relevant information of each type of pending task (including pending tasks obtained by abstracting pending tasks in various business systems and custom pending tasks edited in this system) can be pre-saved in this system, where each type of task is assigned a weight based on the complexity of the task and the experience of experts in various fields.
[0150] Any operation and maintenance personnel handles N tasks within a period of time, and the weight of each task is recorded as W1, W2, ... W N , then the workload P of the operation and maintenance personnel during this period can be expressed by the following formula:
[0151]
[0152] In addition, if these N tasks are specifically composed of M types of tasks, the number of tasks in each type is recorded as A1, A2, ... A M, the corresponding weights of each type of task are recorded as W1, W2...W M , then the workload of the operation and maintenance personnel during this period can also be expressed as:
[0153]
[0154] For example, suppose an operation and maintenance personnel completes 2 pending tasks of category A, 1 pending task of category B, 3 pending tasks of category C, and 4 pending tasks of category D in one day. The weight of pending tasks of category A is recorded as W. a , the weight of the pending tasks of category B is recorded as W b , the weight of the C-type pending tasks is recorded as W c , the weight of the D-type pending tasks is recorded as W d , then the workload P of this operation and maintenance personnel in this day can be calculated as:
[0155] P = 2 × W a +1×W b +3×W c +4×W d
[0156] Through the above-mentioned workload statistics module, the system can obtain the workload statistics of users in any time period, including the number of tasks of a certain type completed, the total number of tasks completed, and the workload converted from all completed tasks, thereby realizing the vertical comparison of the workload of a single user in different time periods and the horizontal comparison of multiple different users in the same time period.
[0157] The system further includes a task reminder module 108 for determining a corresponding reminder rule for each pending task, and sending a task processing reminder to a target user corresponding to the pending task at regular intervals based on the reminder rule.
[0158] Optionally, when the task reminder module sends a task processing reminder to a target user corresponding to the task to be processed, it is specifically used to:
[0159] Send task reminder emails, task reminder text messages, or task reminder pop-up windows to the target users corresponding to the pending tasks.
[0160] Specifically, the task reminder module can be used to maintain pre-set reminder rules, and based on this, supervise and remind tasks with different timeliness according to the reminder rules.
[0161] Although the system can provide a collection of all transactions and display the tasks that users need to handle according to their role permissions, it does not rule out the possibility of transaction processing timeouts and omissions due to failure to log in to the system. In this regard, the system maintains a set of notification rules based on the importance of the transaction.
[0162] For pending tasks from other business systems, a fixed set of reminder rules can be set for each business system. Thus, for a specific business system, this system can remind each pending task from the business system according to the reminder rules corresponding to the business system, as a supplement to the original reminder function of the business system.
[0163] Furthermore, different types of transactions in some business systems may have different timeliness requirements. For example, the system change transaction and the problem ticket tracking transaction in the ITSM system have different timeliness requirements. Therefore, a set of default reminder rules can be set for different types of transactions with different timeliness requirements in the business system. For example, reminder rule 1 is set for the above-mentioned system change transaction, and reminder rule 2 is set for the problem ticket tracking transaction. On this basis, each pending task is reminded according to the reminder rule applicable to its corresponding transaction type. For example, the task corresponding to the system change transaction is reminded according to reminder rule 1.
[0164] Certain types of transactions may have different timeliness requirements in different transaction states. For example, the timeliness requirements for system change transactions in the approval state, implementation state, verification state and end state are different. In this case, different reminder rules can be set for different transaction states of a certain type of transaction. Then, for each task, reminders are given according to the corresponding reminder rules based on the transaction state corresponding to the task. For example, reminder rules a, b, c, and d are set for the approval state, implementation state, verification state and end state of the system change transaction respectively. If a task corresponds to a system change transaction in the approval state, reminder rule a is used for reminder. If a task corresponds to a system change transaction in the implementation state, reminder rule b is used for reminder.
[0165] Among them, the reminder rules corresponding to each business system can be designed according to the original reminder function of the business system. For the affairs with reminder functions in the original business system, this system can be used as a supplement and reinforcement to enhance the realization effect of the design purpose of this system (i.e., to prevent users from missing pending affairs or missing the processing time limit). For example, if business system A provides email reminders for pending affairs, then this system can add additional SMS reminders and pop-up reminders for tasks from business system A.
[0166] In particular, for custom pending tasks, since there are no other means of notification, this system can remind the operation and maintenance personnel who created each custom pending task to manually set the reminder rules applicable to this custom pending task when each custom pending task is created, and remind the operation and maintenance personnel corresponding to this custom pending task according to the set reminder rules before this custom pending task is processed.
[0167] Optionally, for each custom pending task, an operation and maintenance personnel who has the authority to modify reminder rules can also modify the corresponding reminder rule after the custom pending task is created.
[0168] That is to say, when the task reminder module is used to supervise and remind custom pending tasks, each custom pending task will correspond to a set of reminder rules.
[0169] When setting reminder rules, for tasks that need to be executed periodically, such as periodic restart of equipment, periodic extraction of data, and other custom pending tasks, a reminder cycle can be set according to needs, so that the task reminder module sends reminder information to the corresponding operation and maintenance personnel after each reminder cycle, that is, reminders are sent to the corresponding operation and maintenance personnel periodically.
[0170] For a one-time custom pending task, you can set the time node for this custom pending task, and then specify in the corresponding reminder rule that the task reminder module will remind you within a preset time before the time node is reached, for example, two days before the time node is reached.
[0171] In addition, for each pending task (including pending tasks from other business systems and custom pending tasks), you can set a reminder method according to the importance of the task. The optional reminder methods may include pop-up reminders (that is, a reminder window pops up when the corresponding operation and maintenance personnel opens the terminal device), email reminders, SMS reminders, phone reminders, etc.
[0172] The present application provides an operation and maintenance affairs collection and management system, including: a transaction information collection module that collects the transaction information of each pending transaction in each business system in real time, a transaction information processing module that parses the transaction information of pending transactions according to task templates to obtain pending tasks corresponding to the pending transactions, a batch information management module that determines the corresponding target users for pending tasks that are not configured with corresponding target users according to the user's identity information and the target role or target user group of the pending tasks, and a task display processing module that pushes pending tasks to the target users corresponding to the pending tasks to prompt the target users to handle the pending transactions corresponding to the pending tasks. By collecting the transaction information of pending transactions of each business system and parsing them into corresponding pending tasks, this solution can push the user's pending transactions in each business system to the corresponding users, preventing users from missing pending transactions or missing the processing deadline.
[0173] Finally, it should be noted that, in this article, relational terms such as first and second, etc. are only used to distinguish one entity or operation from another entity or operation, and do not necessarily require or imply any such actual relationship or order between these entities or operations. Moreover, the terms "include", "comprise" or any other variants thereof are intended to cover non-exclusive inclusion, so that a process, method, article or device including a series of elements includes not only those elements, but also other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise a ..." do not exclude the presence of other identical elements in the process, method, article or device including the elements.
[0174] It should be noted that the concepts such as "first" and "second" mentioned in the present invention are only used to distinguish different devices, modules or units, and are not used to limit the order or interdependence of the functions performed by these devices, modules or units.
[0175] The present application can be implemented or used by professionals and technicians. Various modifications to these embodiments will be apparent to professionals and technicians in the field, and the general principles defined herein can be implemented in other embodiments without departing from the spirit or scope of the present application. Therefore, the present application will not be limited to the embodiments shown herein, but will conform to the widest scope consistent with the principles and novel features disclosed herein.
Claims
1. A system for collecting and managing operation and maintenance affairs, characterized in that: include: A transaction information collection module is used to collect the transaction information of each pending transaction in each business system in real time; wherein the transaction information includes transaction attributes and transaction status; A transaction information processing module, used to parse the transaction information of each pending transaction according to a preset task template, and obtain a pending task corresponding to each pending transaction; wherein each transaction state of the pending transaction corresponds to a pending task; A batch information collection module, used to collect the identity information of each user in each of the business systems according to a preset update cycle; wherein the identity information is used to indicate the role and user group to which the user belongs in the corresponding business system; A batch information management module is used to determine a plurality of corresponding target users for each of the pending tasks that are not configured with corresponding target users, according to the identity information and the target roles or target user groups included in the pending tasks; wherein the target users corresponding to the pending tasks refer to users with processing rights for the pending tasks, the target roles include a plurality of users, and the target user groups include a plurality of users; A task display processing module is used to push each of the pending tasks to the target user corresponding to the pending task, so as to prompt the target user to handle the pending affairs corresponding to the pending task; When the task display processing module pushes each of the pending tasks to the target user corresponding to the pending tasks, it is specifically used to: After the current user logs in to the operation and maintenance affairs collection and management system, it is determined that each corresponding target user includes the pending tasks of the current user; wherein the current user refers to any user; Sending a task display page to the terminal device of the current user; wherein the task display page displays pending tasks for each corresponding target user including the current user, and the pending tasks are displayed on the terminal devices of the corresponding multiple target users; The transaction information processing module parses the transaction information of each pending transaction according to a preset task template to obtain a pending task corresponding to each pending transaction, specifically for: Obtaining a task template; wherein the task template includes multiple task fields; For each of the pending tasks, extract the field value corresponding to each task field of the task template from the task information of the pending tasks, and add the field value to the task template to obtain the pending task corresponding to the pending tasks; The step of extracting the field value corresponding to each task field of the task template from the task information of the to-do task includes: Copy the field value corresponding to the task field from the transaction information of the to-do transaction; Alternatively, the content of the transaction information is cut, spliced and combined according to a preset processing rule to obtain a field value corresponding to the task field.
2. The system according to claim 1, characterized in that The transaction information collection module is also used for: Real-time collection of information update operations of each pending transaction in the current transaction state in each of the business systems; or, The information update operation of each pending transaction in the business system under the current transaction state is collected according to a preset collection period.
3. The system according to claim 1, characterized in that The system further comprises: The custom task module is used to obtain the custom task information input by the user in the operation and maintenance affairs collection and management system, and generate corresponding custom tasks to be processed based on the custom task information.
4. The system according to claim 1, characterized in that The batch information management module determines at least one corresponding target user for each of the pending tasks that is not configured with a corresponding target user according to the identity information and the target roles or target user groups included in the pending tasks, specifically for: For each pending task that is not configured with a corresponding target user, if the pending task contains a target role, determine each user belonging to the target role according to the identity information, and determine each user belonging to the target role as the target user corresponding to the pending task; For each pending task that is not configured with a corresponding target user, if the pending task contains a target user group, each user belonging to the target user group is determined according to the identity information, and each user belonging to the target user group is determined as the target user corresponding to the pending task.
5. The system according to claim 1, characterized in that The task display processing module is also used for: For any of the pending tasks, receiving a user's request for handling the pending affairs corresponding to the pending task; If the business system to which the pending affairs corresponding to the pending task belongs provides a remote processing interface, the processing interface of the pending affairs corresponding to the pending task is pushed to the user who sent the processing request; Taking the operation of the user who sent the processing request on the processing interface as the updating basis, calling the remote processing interface to update the pending affairs corresponding to the pending task; If the business system to which the pending transaction corresponding to the pending task belongs does not provide a remote processing interface, a jump link to the business system to which the pending transaction corresponding to the pending task belongs is sent to the user who sent the processing request, so that the user who sent the processing request jumps to the business system to which the pending transaction corresponding to the pending task belongs.
6. The system according to claim 1, characterized in that The system further comprises: The workload statistics module is used to calculate the workload of each user within a preset time period based on the number and weight of each category of pending tasks processed by the user within the preset time period; wherein the weight of each category of pending tasks is determined based on the complexity of the pending tasks of that category.
7. The system according to claim 1, characterized in that The system further comprises: The task reminder module is used to determine a corresponding reminder rule for each of the pending tasks, and to periodically send a task processing reminder to a target user corresponding to the pending task based on the reminder rule.
8. The system according to claim 7, characterized in that When the task reminder module sends a task processing reminder to the target user corresponding to the task to be processed, it is specifically used to: Send a task reminder email, task reminder SMS or task reminder pop-up window to the target user corresponding to the pending task.
