CN112396397A - Operation and maintenance affair collection and management system - Google Patents
Operation and maintenance affair collection and management system Download PDFInfo
- Publication number
- CN112396397A CN112396397A CN202011292614.3A CN202011292614A CN112396397A CN 112396397 A CN112396397 A CN 112396397A CN 202011292614 A CN202011292614 A CN 202011292614A CN 112396397 A CN112396397 A CN 112396397A
- Authority
- CN
- China
- Prior art keywords
- task
- processed
- transaction
- user
- handled
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/109—Time management, e.g. calendars, reminders, meetings or time accounting
- G06Q10/1093—Calendar-based scheduling for persons or groups
- G06Q10/1097—Task assignment
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
- G06Q10/063—Operations research, analysis or management
- G06Q10/0631—Resource planning, allocation, distributing or scheduling for enterprises or organisations
- G06Q10/06311—Scheduling, planning or task assignment for a person or group
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q10/00—Administration; Management
- G06Q10/10—Office automation; Time management
- G06Q10/103—Workflow collaboration or project management
Abstract
The application provides an operation and maintenance affair collection and management system, including: the system comprises a transaction information acquisition module for acquiring transaction information of each to-be-handled transaction in each service system in real time, a transaction information processing module for analyzing the transaction information of the to-be-handled transaction according to a task template to obtain a to-be-processed task corresponding to the to-be-handled transaction, a batch information management module for determining a corresponding target user for the to-be-processed task of a target user who is not configured with the corresponding to-be-processed task according to the identity information of the user and the target role or target user group of the to-be-processed task, and a task display processing module for pushing the to-be-processed task to the target user corresponding to the to-be-processed task to prompt the target user to handle the to-be-. By collecting the transaction information of the to-be-handled transactions of each service system and analyzing the transaction information into the corresponding to-be-processed tasks, the scheme can push the to-be-handled transactions of the user in each service system to the corresponding user, and avoids the user from missing the to-be-handled transactions or missing the handling time limit.
Description
Technical Field
The invention relates to the technical field of computers, in particular to an operation and maintenance transaction collection and management system.
Background
With the continuous expansion of banking business, the number and types of servers, application system business functions, and the types of software technologies used in banking data centers are also rapidly increasing, and daily transactions to be processed are multiplied, so that operation and maintenance personnel of the data centers often need to switch among a plurality of different business systems to process the transactions on each business system.
However, in this operation mode, the operation and maintenance staff easily miss part of the business system transactions that are not handled, or miss the transaction time limit specified by the transactions, which may cause adverse effects. Therefore, it is desirable to provide a solution that can uniformly manage and prompt transactions on multiple business systems.
Disclosure of Invention
In view of the above needs in the prior art, the present application provides an operation and maintenance transaction aggregation and management system to provide a unified management scheme for transactions of a multi-service system.
The application provides an operation and maintenance affair collection and management system, including:
the transaction information acquisition module is used for acquiring the transaction information of each to-be-handled transaction in each service system in real time; wherein the transaction information comprises transaction attributes and transaction states;
the transaction information processing module is used for analyzing the transaction information of each to-be-handled transaction according to a preset task template to obtain a to-be-processed task corresponding to each to-be-handled transaction; each transaction state of the to-be-handled transaction corresponds to one to-be-processed task;
the batch information acquisition module is used for acquiring the identity information of each user in each service system according to a preset updating period; the identity information is used for indicating the role and the user group to which the user belongs in the corresponding service system;
the batch information management module is used for determining at least one corresponding target user for the task to be processed of each target user which is not configured with the corresponding target user according to the identity information and the target role or the target user group contained in the task to be processed; the target user corresponding to the task to be processed refers to a user with the processing authority of the task to be processed;
and the task display processing module is used for pushing each task to be processed to a target user corresponding to the task to be processed so as to prompt the target user to handle the transaction to be processed corresponding to the task to be processed.
Optionally, the transaction information processing module is configured to, when analyzing the transaction information of each to-be-handled transaction according to a preset task template to obtain a to-be-processed task corresponding to each to-be-handled transaction, specifically:
acquiring a task template; wherein the task template comprises a plurality of task fields;
and aiming at each item of the to-be-handled affair, extracting a field value corresponding to each item of task field of the task template from the affair information of the to-be-handled affair, and supplementing the field value into the task template to obtain a to-be-processed task corresponding to the to-be-handled affair.
Optionally, the transaction information collection module is further configured to:
acquiring information updating operation of each to-be-handled transaction in each service system in real time under the current transaction state;
alternatively, the first and second electrodes may be,
and acquiring information updating operation of each to-be-handled transaction in each service system in the current transaction state according to a preset acquisition period.
Optionally, the system further includes:
and the custom task module is used for acquiring custom task information input by a user in the operation and maintenance transaction collection and management system and generating a corresponding custom task to be processed based on the custom task information.
Optionally, when the batch information management module determines at least one corresponding target user for the to-be-processed task not configured with a corresponding target user according to the identity information and the target role or the target user group included in the to-be-processed task, the batch information management module is specifically configured to:
for each task to be processed of which the corresponding target user is not configured, if the task to be processed comprises a target role, determining each user belonging to the target role according to the identity information, and determining each user belonging to the target role as the target user corresponding to the task to be processed;
and aiming at each to-be-processed task which is not configured with a corresponding target user, if the to-be-processed task comprises a target user group, determining each user belonging to the target user group according to the identity information, and determining each user belonging to the target user group as the target user corresponding to the to-be-processed task.
Optionally, when the task display processing module pushes each to-be-processed task to a target user corresponding to the to-be-processed task, the task display processing module is specifically configured to:
after a current user logs in the operation and maintenance transaction collection and management system, determining that each corresponding target user contains a task to be processed of the current user; wherein the current user refers to any one user;
sending a task display page to the terminal equipment of the current user; and each corresponding target user is displayed on the task display page and comprises the task to be processed of the current user.
Optionally, the task display processing module is further configured to:
aiming at any one task to be processed, receiving a transaction request of a user for a transaction to be processed corresponding to the task to be processed;
if the business system to which the to-be-handled affair corresponding to the to-be-processed task belongs provides a remote processing interface, pushing the handling interface of the to-be-handled affair corresponding to the to-be-processed task to the user sending the handling request;
taking the operation of the user sending the transaction request on the transaction interface as an updating basis, and calling the remote processing interface to update the to-be-processed affairs corresponding to the to-be-processed task;
and if the service system to which the to-be-handled affair corresponding to the to-be-processed task belongs does not provide a remote processing interface, sending a jump link of the service system to which the to-be-processed affair corresponding to the to-be-processed task belongs to a user sending the handling request, and jumping the user sending the handling request to the service system to which the to-be-processed affair corresponding to the to-be-processed task belongs.
Optionally, the system further includes:
the workload counting module is used for calculating the workload of each user in a preset time period according to the number and the weight of the tasks to be processed of each category processed by the user in the preset time period; and determining the weight of each category of tasks to be processed according to the complexity of the category of tasks to be processed.
Optionally, the system further includes:
and the task reminding module is used for determining a corresponding reminding rule for each task to be processed and sending task processing reminding to a target user corresponding to the task to be processed at regular time based on the reminding rule.
Optionally, when the task reminding module sends a task processing reminder to the target user corresponding to the task to be processed, the task reminding module is specifically configured to:
and sending a task reminding mail, a task reminding short message or a task reminding popup to a target user corresponding to the task to be processed.
The application provides an operation and maintenance affair collection and management system, including: the system comprises a transaction information acquisition module for acquiring transaction information of each to-be-handled transaction in each service system in real time, a transaction information processing module for analyzing the transaction information of the to-be-handled transaction according to a task template to obtain a to-be-processed task corresponding to the to-be-handled transaction, a batch information management module for determining a corresponding target user for the to-be-processed task of a target user who is not configured with the corresponding to-be-processed task according to the identity information of the user and the target role or target user group of the to-be-processed task, and a task display processing module for pushing the to-be-processed task to the target user corresponding to the to-be-processed task to prompt the target user to handle the to-be-. By collecting the transaction information of the to-be-handled transactions of each service system and analyzing the transaction information into the corresponding to-be-processed tasks, the scheme can push the to-be-handled transactions of the user in each service system to the corresponding user, and avoids the user from missing the to-be-handled transactions or missing the handling time limit.
Drawings
In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings used in the description of the embodiments or the prior art will be briefly described below, it is obvious that the drawings in the following description are only embodiments of the present invention, and for those skilled in the art, other drawings can be obtained according to the provided drawings without creative efforts.
Fig. 1 is a schematic structural diagram of an operation and maintenance transaction aggregation and management system according to an embodiment of the present application;
fig. 2 is a schematic diagram illustrating a status of a pending transaction according to an embodiment of the present application;
fig. 3 is a flowchart of a method for parsing transaction information into corresponding to-be-processed tasks according to an embodiment of the present application;
fig. 4 is a schematic diagram illustrating a correspondence relationship between a user and a role of a service system according to an embodiment of the present application;
FIG. 5 is a schematic diagram of a display interface of a task to be processed according to an embodiment of the present disclosure;
fig. 6 is a schematic diagram of a processing flow of a task to be processed according to an embodiment of the present application.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
An embodiment of the present application provides an operation and maintenance transaction aggregation and management system, as shown in fig. 1, the system may include the following modules:
the transaction information collecting module 101 is configured to collect, in real time, transaction information of each to-be-handled transaction in each service system.
Wherein the transaction information includes transaction attributes and transaction states.
The transaction information processing module 102 is configured to analyze the transaction information of each to-be-handled transaction according to a preset task template, so as to obtain a to-be-processed task corresponding to each to-be-handled transaction.
And the batch information acquisition module 103 is configured to acquire identity information of each user in each service system according to a preset update period.
The identity information is used for indicating the role and the user group to which the user belongs in the corresponding service system.
And the batch information management module 104 is configured to determine at least one corresponding target user for each to-be-processed task not configured with a corresponding target user according to the identity information and the target role or the target user group included in the to-be-processed task.
The target user corresponding to the task to be processed refers to a user with the processing authority of the task to be processed.
The task display processing module 105 is configured to push each to-be-processed task to a target user corresponding to the to-be-processed task, so as to prompt the target user to handle a to-be-handled transaction corresponding to the to-be-processed task.
Optionally, the system provided in this embodiment of the present application may further include:
and the custom task module 106 is configured to obtain custom task information input by a user in the operation and maintenance transaction aggregation and management system, and generate a corresponding custom task to be processed based on the custom task information.
The workload statistics module 107 is configured to, for each user, obtain a task weight of each to-be-processed task processed by the user within a preset time period, and accumulate all the obtained task weights to obtain a workload of the user within the preset time period.
The task weight of the task to be processed is determined according to the complexity of the task to be processed.
Optionally, the system further comprises:
and the task reminding module 108 is configured to determine a corresponding reminding rule for each to-be-processed task, and send a task processing reminder to a target user corresponding to the to-be-processed task at regular time based on the reminding rule.
The operation and maintenance transaction aggregation and management system provided by the present application may be regarded as a computer program for uniformly managing to-be-handled transactions of a plurality of business systems, and each module in the system shown in fig. 1 may be regarded as a plurality of sub-programs for implementing corresponding functions in the computer program.
Specifically, in the operation and maintenance transaction collection and management system provided by the application, a program related to back-end service logic processing can be developed by using a Java language-based application development framework, namely, SpringBoot, which is an existing Java application development framework that is used when opening a box, and the software configuration process of application development can be simplified by using the development framework, so that developers can concentrate on service logic implementation, and therefore SpringBoot is widely applied to the field of rapid application development (rapid application development).
The front-end page in the operation and maintenance transaction aggregation and management system may utilize Vue and AntDesign, for example, the task presentation processing module 105 pushes the task to be processed to the corresponding target user, and the front-end page including several items of tasks to be processed needs to be displayed on the terminal device of the target user for the target user to browse.
Vue is a progressive front-end JavsScript framework, has the characteristics of data-driven view, high componentization degree, high running speed and the like, is suitable for front-end page logic development with high timeliness and componentization degree, and is suitable for the characteristics of quick data update and plug-in update of the system. The AntDesign is an existing page UI component library, has the characteristics of few invalid graphs, prominent key points, strong significance and the like, and can be used for enabling a user to focus on effective information needing attention in a page when using the system provided by the application.
The transaction information acquisition module 101 needs to acquire transaction information from each service system in real time, and meanwhile, the transaction information acquisition module needs to transmit the acquired transaction information to the transaction information processing module for the transaction information processing module to analyze. Kafka is a distributed, partition-enabled, multi-copy (replenisher) messaging system. Kafka is developed based on a Zookeeper service of an open-source distributed application program, and the biggest characteristic of Kafka is that a large amount of data can be processed in real time to meet various demand scenarios, such as log collection, user activity tracking, streaming processing and the like. The method has the characteristics of expandability, durability, high concurrency and the like. Therefore, Kafka is suitable for the requirement that the transaction information acquisition module 101 acquires the transaction information from a plurality of service systems, and the subsequent transaction information processing module 102 analyzes, processes and persistently stores the transaction information one by one, and meets the expansion requirement of the subsequent systems.
The operation and maintenance transaction collection and management system provided by the application relates to collection and processing of a large amount of data, so that the data needs to be stored by using a database, and particularly, the database MySql can be used for storing the data in the application. MySql is an open source relational database management system. Has the characteristics of small volume, high speed, low cost and the like. And a specific database manager is not needed, so that better management and maintenance can be realized, and the management requirements of the system on data are met.
In order to implement the development techniques and tools used by the operation and maintenance transaction collection and management system provided by the present application, each module in the operation and maintenance transaction collection and management system of the present application is specifically described one by one.
As described above, the transaction information collection module 101 in the present application is configured to collect the transaction information of each to-be-handled transaction in each business system in real time, and the collected transaction information of the to-be-handled transaction may be persistently stored in the database through the transaction information collection module.
The collection mode may be that each service system pushes the transaction information of the to-be-handled transaction of each service system to the transaction information collection module in real time through the message framework Kafka.
In addition, the transaction information acquisition module can also acquire the information updating operation of each to-be-handled transaction in each service system in the current transaction state in real time.
In the present application, the to-do business (also referred to as a business) is used to refer to various work items such as flow work orders, routine operations, and the like that need to be processed in the operation and maintenance work of the data center. Including but not limited to: various IT process work orders and routine system check and emergency drilling in an IT server Management system (ITSM), temporary OA requirements, burst alarm handling, various single affairs dispatched by department leaders or mails, work contents completed by cooperation of groups or virtual groups within a period of time, and the like, wherein a business system refers to work software or pages for handling corresponding affairs, such as: an IT management service system, an on-duty system, an alarm system, a drilling system and the like. For example, to process an IT flow order requires logging into an IT management service system, and to perform a routine system check requires logging into a system on duty.
It should be noted that the operation and maintenance transaction collection and management system (hereinafter referred to as the system) provided by the present application aims to collect the to-be-handled transactions of all other service systems of the data center, and further provides a unified display reminding platform, and as the work of the data center is continuously refined, the types and sources of the transactions are continuously increased, so that the real-time data collection realized by the transaction information collection module must meet the capability of horizontal continuous expansion.
The transaction information of the pending transaction may include attribute information of the transaction, such as creation time of the transaction, a business system to which the transaction belongs, content to be processed, a person who is designated to process the transaction (or a role or a user group that is designated to process the transaction), and may further include status information of the transaction, where the status information is used to indicate a current transaction status of the transaction.
For example, in the state diagram of the to-be-handled transaction shown in fig. 2, the Z-type transaction in the service system a may have several transaction states, which are equivalent to the completion of the Z-type transaction in the service system a and need to complete the several steps of creation, circulation, execution, audit and completion in sequence, each transaction state has corresponding specific work content, and 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 completes the work content corresponding to the creation state of a Z-type transaction, the transaction state of the transaction is changed from creation to circulation, after the corresponding operation and maintenance personnel completes the work content in the circulation state, the transaction state of the transaction is changed to an execution state, and so on until the transaction is finally handled.
In any transaction state, the operation and maintenance staff can update corresponding information for multiple times when processing corresponding work content, for example, for a transaction in a circulation state, the corresponding operation and maintenance staff fill in information such as which operation and maintenance staff (or which operation and maintenance staff) to which the transaction needs to be circulated to handle, handling time limit, guidance opinions and the like in a corresponding form, the operation and maintenance staff can update the filled information for multiple times after filling the information for the first time until the filled information is determined to be correct, the work of the current transaction state is determined to be finished on the corresponding business system, and then the transaction can not enter the next transaction state. For example, in fig. 2, a certain transaction of Z type goes through three information update operations while in the circulation state.
Correspondingly, the transaction information collected by the transaction information collection module may further include each information update operation that occurs in the current transaction state.
The transaction information acquired by the transaction information acquisition module can be filled in the message queue and transmitted to the subsequent transaction information processing module through the message queue, and in addition, the transaction information can be durably stored in a database of the system. Wherein, the database for storing transaction information in a persistent mode can be called a transaction pool of the system.
In the system, as described above, the transaction information processing module is configured to analyze the transaction information of each to-be-handled transaction according to the preset task template to obtain the to-be-processed task corresponding to each to-be-handled transaction, and this process is equivalent to extracting the key content in each to-be-handled transaction and abstracting and normalizing the key content into the task in the system. After the transaction information processing module, each to-be-handled transaction is converted into a corresponding to-be-processed task. The to-be-processed task in the present application can be understood as an abstracted to-be-processed transaction.
Abstracting a transaction may be understood as extracting common and standardized information fields of the transaction, such as: transaction sources, content summaries, start times, finish times, current states, processing personnel, workload weights, etc., thereby normalizing the different transactions from different sources.
Because the to-be-handled transactions collected by the system are from a plurality of business systems, key fields and information contents of the to-be-handled transactions are different, and the system aims to show common information which needs to be concerned by a user on a single page, the key information in the original business information of the business system is extracted by using a normalized abstraction algorithm, and the transactions with multiple sources and high grain refinement degree are abstracted into a uniform data type in the system, namely, a to-be-processed task (also referred to as a task for short).
It should be particularly noted that, in the system, each transaction state of one to-be-handled transaction corresponds to different to-be-processed tasks, for example, a previous transaction may have transaction states of creation, circulation, execution, audit, and the like, and accordingly, the transaction is a creation task when in the creation state, and corresponding tasks are a circulation task, an execution task, and an audit task in sequence when in the circulation state, the execution state, and the audit state.
When any transaction is switched from a previous transaction state to a next transaction state, the system marks a task corresponding to the previous transaction state as completed, meanwhile, the transaction information acquisition module detects a new transaction state of the transaction, and the corresponding transaction information processing module generates a new task aiming at the new transaction state.
For example, when a transaction changes from the creation state to the circulation state, the original creation task of the transaction in the system is marked as completed, and the transaction information processing module generates the circulation task of the transaction.
With reference to fig. 3, the transaction information processing module in the system analyzes the transaction information of each to-be-handled transaction according to the preset task template, and obtains a specific flow of the to-be-processed task corresponding to each to-be-handled transaction as follows:
s301, acquiring the task template and the transaction information of the to-be-handled transaction.
A task template may be understood as a predefined blank data structure in the system that includes a plurality of task fields, for example, table 1 below lists the task fields defined in an alternative task template.
TABLE 1
| Task field | Field value |
| Source system | |
| Transaction type | |
| Transaction numbering | |
| Current transaction state | |
| Handling of conditions | |
| Transaction summary | |
| Current processing group | |
| Current person of treatment | |
| Task remark |
In the task template, the current handler and the current handling group are used to indicate to which maintenance person the task to be handled is assigned or to which user group the task to be handled is assigned.
S302, extracting field values corresponding to each task field of the task template from the transaction information of the to-be-handled transaction.
For any task field, when the field value of the task field is explicitly recorded in the transaction information of the to-be-handled transaction, the field value can be directly copied from the transaction information; when the field value of the task field is not explicitly recorded in the transaction information, the content in the transaction information can be cut, spliced and combined according to the preset processing rule, so that the field value corresponding to the task field is obtained.
Taking the transaction summary field in table 1 as an example, when it is not explicitly stated which part of the content in the transaction information is the transaction summary, the transaction summary can be obtained by cutting information such as the transaction reason and the transaction detailed description in the transaction information according to the preset processing rule and splicing the information.
If the field value of a task field cannot be obtained by the above method, the field value of the task field may be set to null (null), for example, when a certain transaction is an intra-group transaction, the transaction information does not include a specific handler, so the field value of the field of "current handler" in table 1 cannot be obtained from the transaction information by the above method, and thus, when a task corresponding to the intra-group transaction is generated, the field value of the "current handler" may be set to null.
And S303, filling the extracted field values into the task template in a one-to-one correspondence manner to obtain the to-be-processed tasks corresponding to the to-be-processed affairs.
For example, for each task field in table 1, a corresponding field value may be extracted from the transaction information of the to-be-handled transaction, for example, a service system from which the to-be-handled transaction originates, and the field value of the transaction number is extracted and correspondingly supplemented in the task template, so that a to-be-processed task corresponding to the to-be-handled transaction may be obtained.
After supplementing the corresponding field value to the task template shown in table 1 above, a task to be processed as exemplified in table 2 below can be obtained:
TABLE 2
| Task field | Field value |
| Source system | Service system A |
| Transaction type | Z type |
| Transaction numbering | ID000000 |
| Current transaction state | Audit status |
| Handling of conditions | In the process of |
| Transaction summary | Reviewing filled forms |
| Current processing group | First user group |
| Current person of treatment | User X |
| Task remark | Is free of |
By the method shown in fig. 3, each to-be-handled transaction can be abstracted into a corresponding to-be-handled task, and the to-be-handled task and the to-be-handled transaction are corresponding to each other.
Tasks after external to-be-handled transactions are abstracted, and custom tasks to be processed (also referred to as custom tasks for short) maintained in the system are all tasks which are required to be processed by data center workers in daily life.
And the batch information acquisition module 103 is configured to acquire identity information of each user in each service system according to a preset update period.
Because the identity information of the user is generally not changed frequently, batch collection can be performed once at regular update cycles by the batch information collection module.
That is to say, the batch information collection module conducts periodic batch import aiming at user information with low real-time performance in each service system and persists the user information to the database.
The identity information of the user may specifically include an identifier, a right, a group of the user group to which the user belongs, and information of the role to which the user belongs in the service system.
It should be noted that each user has corresponding identity information in each service system, and the identity information of the same user in different service systems is generally different, for example, the same user in different service systems may belong to different user groups and different roles, and the corresponding user has different rights in different service systems. Meanwhile, one user may have a plurality of roles in one system or may belong to a plurality of user groups.
As shown in fig. 4, the user 1 belongs to a role a in the business system a, and can process the work of the transaction type a in the execution state, and process the work of the transaction type B in the approval state, and belongs to a role B and a role C in the business system B, and can perform the work of the application state and the implementation state of the transaction type C. All the information needs to be used as identity information of the user, collected by the batch information collection module and stored in the database of the system, so as to be provided for the subsequent task display processing module for use.
And the batch information management module 104 is configured to determine at least one corresponding target user for each to-be-processed task not configured with a corresponding target user according to the identity information and the target role or the target user group included in the to-be-processed task.
For any one to-be-handled transaction, the corresponding service system can designate a corresponding target user for each state of the to-be-handled transaction, that is, it is specified that the transaction needs to be processed by a designated operation and maintenance person when the transaction is in a specific state.
Correspondingly, the business system also has the following conditions:
for a pending item, the service system does not designate a specific operation and maintenance person as a processing person of the pending item, but only designates the pending item to be executed by a certain type of role or a certain user group.
In the above situation, the batch information management module is required to determine the target user of the to-be-processed task corresponding to the to-be-handled transaction, that is, determine which users need to process the to-be-processed task, according to the designated role or user group.
Optionally, when the batch information management module determines at least one corresponding target user for the to-be-processed task of each non-configured corresponding target user according to the identity information and the target role or the target user group included in the to-be-processed task, the batch information management module is specifically configured to:
for each task to be processed of the target user which is not configured with the corresponding target user, if the task to be processed contains the 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 task to be processed;
and aiming at each task to be processed which is not configured with a corresponding target user, if the task to be processed comprises a target user group, determining each user belonging to the target user group according to the identity information, and determining each user belonging to the target user group as the target user corresponding to the task to be processed.
For example, the target role of a certain task is role a, and the users belonging to role a include user 1, user 2, and user 3, so that the batch information management module may determine user 1, user 2, and user 3 as the target users of the task to be processed, that is, specify that the to-be-handled transaction corresponding to the task to be processed is processed by any one of user 1, user 2, and user 3.
In other words, for a certain to-do transaction, the transaction process may not be specific to people, and may also be transferred to user groups or user roles, each group or role including multiple users. In order to show the abstracted task to the user who needs to process the task or has the authority to process the task, the system associates the transaction type in the task with the user belonging to the corresponding role or user group in the batch information management module, and can show the task to the user who really concerns the task without screening and manual judgment. The transaction collection display of the system has the advantage over other established order full-volume transaction collection display modes.
The task display processing module 105 is configured to push each to-be-processed task to a target user corresponding to the to-be-processed task, so as to prompt the target user to handle a to-be-handled transaction corresponding to the to-be-processed task.
Optionally, when the task display processing module pushes each task to be processed to the target user corresponding to the task to be processed, the task display processing module is specifically configured to:
after a current user logs in an operation and maintenance transaction collection and management system, determining that each corresponding target user contains a task to be processed of the current user; wherein, the current user refers to any one user;
sending a task display page to the terminal equipment of the current user; and each corresponding target user is displayed on the task display page and contains the task to be processed of the current user.
An optional task display interface is shown in fig. 5, where three tasks 1,2, and 3 can be obtained through normalization processing, where the to-be-handled transactions corresponding to the task 1 and the task 2 are type a transactions, the service system to which the corresponding to-be-handled transactions belong is a service system X, the to-be-handled transactions corresponding to the task 3 are type B transactions of a service system Y, and the user groups specified by the tasks 1,2, and 3 are user groups h, i, and j, respectively. Wherein: the user group h comprises users 1,2, 3; the user group i comprises users 1, 4, 5; user group j includes users 1, 4, 7.
For the user, the tasks to be processed of the user 1 are the task 1, the task 2 and the task 3, the tasks to be processed of the user 2 are the task 1, the tasks to be processed of the user 4 are the task 2 and the task 3, and so on, and the task display processing module can push the tasks to the user who needs to process or wants to pay attention to the tasks through the corresponding relation.
The task display processing module may generate an interface as shown in fig. 5, and when a user logs in the system, the interface is sent to the terminal device of the corresponding user, and the user can know how many to-do transactions are currently available through the interface shown in fig. 5. In addition, the user can click on the task numbers such as task 1, task 2 and the like in the interface shown in fig. 5, so as to view the task details, that is, view the detailed information of the corresponding to-be-handled transaction.
Further, in order to meet the one-stop processing requirement of the transaction, and realize the function of directly processing the transaction in other business systems in the system, the task display processing module of the system may also support the user to process the corresponding to-be-handled transaction through the flow shown in fig. 6:
s601, receiving a transaction request of a user for a to-be-handled transaction.
The transaction request of the to-be-handled transaction may also be regarded as a processing request of a to-be-processed task corresponding to the to-be-handled transaction. Optionally, the user may click on a task box where any one to-be-processed task is located in the display interface shown in fig. 4 to view the task details of the to-be-processed task, and select an option for processing the task after the task details are viewed, so as to input an office request for the to-be-handled transaction corresponding to the to-be-processed task to the system.
S602, judging whether the service system to which the to-do affair belongs provides a remote processing interface.
If the service system to which the to-do transaction belongs provides the remote processing interface, step S603 is executed, otherwise, if the service system to which the to-do transaction belongs does not provide the remote processing interface, step S604 is executed.
S603, providing an office interface of the to-be-handled affairs, and updating the to-be-handled affairs corresponding to the to-be-processed task based on the operation of the user in the office interface.
That is to say, under the condition that the service system to which the to-be-handled transaction belongs provides the remote processing interface, the user can directly handle the to-be-handled transaction in the system, for example, documents to be filled are directly filled in the system, corresponding documents are edited, and the like, data required to be used in the handling process can be directly acquired from the service system to which the to-be-handled transaction belongs by calling the remote processing interface through the system, after the user finishes handling, the system can access the service system to which the to-be-handled transaction belongs through the remote processing interface provided by the service system, and then the to-be-handled transaction in the service system is directly updated based on the operation of the user.
By the mode, on the premise that the corresponding service system provides the remote processing interface, a user does not need to repeatedly switch to a plurality of different service systems to handle a plurality of transactions, and can directly complete the handling of the to-be-handled transactions in the plurality of service systems only by operating the corresponding handling interface in the system.
S604, judging whether the business system to which the to-do business belongs provides jump links.
If the business system to which the to-do transaction belongs provides the jump link, step S605 is executed, otherwise, if the business system to which the to-do transaction belongs does not provide the jump link, step S606 is executed.
S605, sending the business system skip link to which the to-be-handled business belongs to the user, and enabling the user to skip to a handling interface of the business system to which the to-be-handled business belongs.
A jump link, i.e. a Uniform Resource Locator (url) of an interface corresponding to the service system. Under the condition that the business system provides the jump link of the corresponding transaction interface, the system can directly send the jump link to the terminal equipment of the user needing to transact the to-be-handled business of the corresponding business system, and the user can directly log in the transaction interface of the corresponding business system by clicking the jump link, so that the to-be-handled business is directly transacted in the business system to which the to-be-handled business belongs.
For some service systems which are inconvenient to provide remote processing interfaces, jump links can be provided for users to click, the users are allowed to directly access the corresponding service systems through the system in the mode, the service systems in which the to-be-handled transactions are located do not need to be recorded manually, the users do not need to log in the corresponding service systems manually, the process of switching the users from the system to the service systems to which the to-be-handled transactions belong is obviously simplified, and the processing efficiency of the transactions is improved.
And S606, outputting the skip failure prompt information.
And the skip failure prompt information is used for prompting the user to manually switch to the service system to which the to-be-handled transaction belongs to handle the corresponding transaction.
It should be understood that, according to the foregoing description of the transaction information collection module 101, in the above three ways of transacting the pending transactions in the business system, the related updates of the related information of the pending transactions (including the change of the transaction state and the update record of the data in a certain transaction state) are all automatically collected by the transaction information collection module 101 in the system synchronously and automatically displayed to the user through the task display processing module, and no additional confirmation circulation step is required in the system.
As described above, the system further includes a custom task module 106, configured to obtain custom task information input by the user in the operation and maintenance transaction aggregation and management system, and generate a corresponding custom task to be processed based on the custom task information.
That is to say, the custom task module mainly uses the system as a record circulation main body for daily work matters which are not circulated and handled in other business systems, and provides the functions of recording and transferring. The work items mainly comprise work scheduled by oral or mail of a supervisor, tracking tasks inside departments and the like.
For example, after a supervisor verbally arranges a work item for a certain operation and maintenance person, the operation and maintenance person can log in the system, and fill in a form of a custom task in the custom task module according to the description of the supervisor, so that a custom task is generated in the system through the custom task module.
It should be noted that, in the system, the processing mode of the custom task to be processed is the same as that of the task to be processed generated by the transaction information processing module in the foregoing, that is, the system can use the same processing mode as that of the task to be processed to display the custom task to be processed and perform subsequent management operations such as notification and reminding.
By setting the custom task module, the system can realize the unified management of the whole transactions of the data center, namely, the transactions of a plurality of service systems on the line can be managed, and simultaneously, the transactions handed over from the lower port can be managed in the form of the custom task.
The system further includes a workload statistics module 107, configured to, for each user, obtain a task weight of each to-be-processed task processed by the user within a preset time period, and accumulate all the obtained task weights to obtain a workload of the user within the preset time period.
That is to say, in the system, the workload statistics module is mainly used for performing quantitative statistics and presentation on the tasks processed and completed by each operation and maintenance worker according to the information such as the task weight of the tasks corresponding to different types of transactions.
The task weight of the task to be processed is determined according to the complexity of the task to be processed.
And for any operation and maintenance personnel, setting a weight for each task to be processed according to the difficulty and the used time of various tasks processed by the operation and maintenance personnel, and counting the sum of the weights of all tasks processed and completed by the operation and maintenance personnel within a period of time to obtain the workload of the operation and maintenance personnel within a period of time.
Specifically, the relevant information of each type of task to be processed (including the task to be processed obtained after abstracting the transaction to be processed in each business system and the custom task to be processed edited in the system) may be pre-stored in the system, where each type of task determines a weight for the type of task according to the complexity of the task and expert experience analysis in each field.
Any one operation and maintenance personnel processes N tasks within a period of time, and the weight of each task is recorded as W in turn1，W2,……WNThen the workload P of the operation and maintenance personnel in this period of time can be represented by the following formula:
in addition, if the N tasks are specifically composed of M types of tasks, the number of each type of task is sequentially marked as a1，A2……AMThe weight of each corresponding task is sequentially marked as W1，W2……WMThen, the workload of the operation and maintenance personnel in this period of time can also be expressed as:
for example, suppose an operation and maintenance worker completes 2 class a tasks to be processed, 1 class B tasks to be processed, 3 class C tasks to be processed, and 4 class D tasks to be processed within one day, wherein the weight of the class a tasks to be processed is recorded as WaThe weight of B-class task is marked as WbAnd the weight of the C-type task to be processed is recorded as WcAnd the weight of the D-class task to be processed is recorded as WdThen the workload P of the operation and maintenance personnel in the day can be summarized as:
P＝2×Wa+1×Wb+3×Wc+4×Wd
through the workload statistical module, the system can obtain the workload statistical data of the user in any time period, including the number of tasks completing a certain class, the total number of tasks completing and the workload converted by all the tasks completing, thereby realizing the longitudinal comparison of the workload of a single user in different time periods and the transverse comparison of the workload of different users in the same time period.
The system further includes a task reminding module 108, configured to determine a corresponding reminding rule for each to-be-processed task, and periodically send a task processing reminder to a target user corresponding to the to-be-processed task based on the reminding rule.
Optionally, when the task reminding module sends the task processing reminder to the target user corresponding to the task to be processed, the task reminding module is specifically configured to:
and sending a task reminding mail, a task reminding short message or a task reminding popup to a target user corresponding to the task to be processed.
Specifically, the task reminding module can be used for maintaining preset reminding rules and supervising and reminding tasks with different timeliness according to the reminding rules based on the preset reminding rules.
Although the system can provide the collection of the whole transaction and show the tasks which need to be processed by the user according to the user role authority, the situations of transaction processing timeout and omission caused by not logging in the system are not excluded. For which the system maintains a set of notification rules according to the importance of the transaction.
For the tasks to be processed from other business systems, a set of fixed reminding rules can be set for each business system. Therefore, for a specific service system, the system can remind each task to be processed from the service system according to the reminding rule corresponding to the service system, so as to supplement the original reminding function of the service system.
Furthermore, different types of transactions in part of the service systems may have different requirements on timeliness, for example, the requirements on timeliness of a system change transaction and a question sheet tracking transaction in the ITSM system are different, so that a set of default reminding rules may be set for different types of transactions having different timeliness requirements in the service system, for example, a reminding rule 1 is set for the system change transaction, a reminding rule 2 is set for the question sheet tracking transaction, and on this basis, each task to be processed is reminded according to the reminding rule applicable to the corresponding transaction type. For example, the task corresponding to the system change transaction is reminded according to the reminding rule 1.
In different transaction states, requirements on timeliness may be different for some types of transactions, for example, timeliness requirements for a system change transaction in an approval state and an implementation state are different, and in this case, different reminding rules may be set for different transaction states of a certain type of transaction, and then, for each task, a reminder is given according to a corresponding reminding rule according to the transaction state corresponding to the task, for example, a reminding rule a is set according to the approval state and the implementation state of the system change transaction, and reminding rules a, b, c, and d are set for the verification state and the implementation state of the system change transaction, if one task corresponds to the system change transaction in the approval state, a reminder is given according to a reminding rule a, and if one task corresponds to the system change transaction in the implementation state, a reminder is given according to a reminding rule b.
The reminding rule corresponding to each service system can be designed according to the original reminding function of the service system, and for the affairs with the reminding function in the original service system, the system can be used as supplement and enhancement to enhance the implementation effect of the design purpose of the system (namely, the user is prevented from missing the affairs to be handled or missing the handling time limit). For example, if the service system a provides a mail reminder for a transaction, the system may additionally add a higher-strength reminder rule such as a short message reminder and a pop-up window reminder to the task from the service system a.
Particularly, for the user-defined task to be processed, because no other notification means exists, the system can remind the operation and maintenance personnel who create the user-defined task to be processed to manually set a reminding rule suitable for the user-defined task to be processed when each user-defined task to be processed is created, and remind the operation and maintenance personnel corresponding to the user-defined task to be processed according to the set reminding rule before the user-defined task to be processed is processed.
Optionally, for each user-defined task to be processed, the operation and maintenance personnel having the reminding rule modification authority may also modify the reminding rule corresponding to the user-defined task to be processed after the user-defined task to be processed is created.
That is to say, when the task reminding module is used for supervising and reminding the user-defined tasks to be processed, each user-defined task to be processed corresponds to a group of reminding rules.
When the reminding rule is set, a reminding period can be set according to requirements for tasks needing to be executed periodically, such as periodic restarting of equipment, periodic extraction of data and other self-defined tasks to be processed, so that the task reminding module sends reminding information to corresponding operation and maintenance personnel every time the reminding period passes, namely, the reminding is sent to the corresponding operation and maintenance personnel periodically.
For a one-time custom task to be processed, a time node of the custom task to be processed can be set, and then a task reminding module is specified in a corresponding reminding rule to remind within a preset time length before the time node is reached, for example, reminding is carried out two days before the time node is reached.
In addition, for each task to be processed (including tasks to be processed from other business systems and custom tasks to be processed), a reminding mode can be set according to the importance degree of the task, and the selectable reminding modes can include pop-up window reminding (that is, popping up a reminding window when the corresponding operation and maintenance personnel open the terminal device), mail reminding, short message reminding, telephone reminding and the like.
The application provides an operation and maintenance affair collection and management system, including: the system comprises a transaction information acquisition module for acquiring transaction information of each to-be-handled transaction in each service system in real time, a transaction information processing module for analyzing the transaction information of the to-be-handled transaction according to a task template to obtain a to-be-processed task corresponding to the to-be-handled transaction, a batch information management module for determining a corresponding target user for the to-be-processed task of a target user who is not configured with the corresponding to-be-processed task according to the identity information of the user and the target role or target user group of the to-be-processed task, and a task display processing module for pushing the to-be-processed task to the target user corresponding to the to-be-processed task to prompt the target user to handle the to-be-. By collecting the transaction information of the to-be-handled transactions of each service system and analyzing the transaction information into the corresponding to-be-processed tasks, the scheme can push the to-be-handled transactions of the user in each service system to the corresponding user, and avoids the user from missing the to-be-handled transactions or missing the handling time limit.
Finally, it should also be noted that, herein, relational terms such as first and second, and the like may be used solely to distinguish one entity or action from another entity or action without necessarily requiring or implying any actual such relationship or order between such entities or actions. Also, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising an … …" does not exclude the presence of other identical elements in a process, method, article, or apparatus that comprises the element.
It should be noted that the terms "first", "second", and the like in the present invention are only used for distinguishing different devices, modules or units, and are not used for limiting the order or interdependence relationship of the functions performed by the devices, modules or units.
Those skilled in the art can make or use the present application. Various modifications to these embodiments will be readily apparent to those skilled in the art, and the generic principles defined herein may be applied to other embodiments without departing from the spirit or scope of the application. Thus, the present application 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 (10)
1. An operation and maintenance transaction aggregation and management system, comprising:
the transaction information acquisition module is used for acquiring the transaction information of each to-be-handled transaction in each service system in real time; wherein the transaction information comprises transaction attributes and transaction states;
the transaction information processing module is used for analyzing the transaction information of each to-be-handled transaction according to a preset task template to obtain a to-be-processed task corresponding to each to-be-handled transaction; each transaction state of the to-be-handled transaction corresponds to one to-be-processed task;
the batch information acquisition module is used for acquiring the identity information of each user in each service system according to a preset updating period; the identity information is used for indicating the role and the user group to which the user belongs in the corresponding service system;
the batch information management module is used for determining at least one corresponding target user for the task to be processed of each target user which is not configured with the corresponding target user according to the identity information and the target role or the target user group contained in the task to be processed; the target user corresponding to the task to be processed refers to a user with the processing authority of the task to be processed;
and the task display processing module is used for pushing each task to be processed to a target user corresponding to the task to be processed so as to prompt the target user to handle the transaction to be processed corresponding to the task to be processed.
2. The system of claim 1, wherein the transaction information processing module is configured to, when analyzing the transaction information of each to-be-handled transaction according to a preset task template to obtain a to-be-processed task corresponding to each to-be-handled transaction, specifically:
acquiring a task template; wherein the task template comprises a plurality of task fields;
and aiming at each item of the to-be-handled affair, extracting a field value corresponding to each item of task field of the task template from the affair information of the to-be-handled affair, and supplementing the field value into the task template to obtain a to-be-processed task corresponding to the to-be-handled affair.
3. The system of claim 1, wherein the transaction information collection module is further configured to:
acquiring information updating operation of each to-be-handled transaction in each service system in real time under the current transaction state;
alternatively, the first and second electrodes may be,
and acquiring information updating operation of each to-be-handled transaction in each service system in the current transaction state according to a preset acquisition period.
4. The system of claim 1, further comprising:
and the custom task module is used for acquiring custom task information input by a user in the operation and maintenance transaction collection and management system and generating a corresponding custom task to be processed based on the custom task information.
5. The system according to claim 1, wherein the batch information management module, when determining at least one corresponding target user for the task to be processed, for which no corresponding target user is configured, according to the identity information and a target role or a target user group included in the task to be processed, is specifically configured to:
for each task to be processed of which the corresponding target user is not configured, if the task to be processed comprises a target role, determining each user belonging to the target role according to the identity information, and determining each user belonging to the target role as the target user corresponding to the task to be processed;
and aiming at each to-be-processed task which is not configured with a corresponding target user, if the to-be-processed task comprises a target user group, determining each user belonging to the target user group according to the identity information, and determining each user belonging to the target user group as the target user corresponding to the to-be-processed task.
6. The system of claim 1, wherein when the task display processing module pushes each to-be-processed task to a target user corresponding to the to-be-processed task, the task display processing module is specifically configured to:
after a current user logs in the operation and maintenance transaction collection and management system, determining that each corresponding target user contains a task to be processed of the current user; wherein the current user refers to any one user;
sending a task display page to the terminal equipment of the current user; and each corresponding target user is displayed on the task display page and comprises the task to be processed of the current user.
7. The system of claim 1, wherein the task exposure processing module is further configured to:
aiming at any one task to be processed, receiving a transaction request of a user for a transaction to be processed corresponding to the task to be processed;
if the business system to which the to-be-handled affair corresponding to the to-be-processed task belongs provides a remote processing interface, pushing the handling interface of the to-be-handled affair corresponding to the to-be-processed task to the user sending the handling request;
taking the operation of the user sending the transaction request on the transaction interface as an updating basis, and calling the remote processing interface to update the to-be-processed affairs corresponding to the to-be-processed task;
and if the service system to which the to-be-handled affair corresponding to the to-be-processed task belongs does not provide a remote processing interface, sending a jump link of the service system to which the to-be-processed affair corresponding to the to-be-processed task belongs to a user sending the handling request, and jumping the user sending the handling request to the service system to which the to-be-processed affair corresponding to the to-be-processed task belongs.
8. The system of claim 1, further comprising:
the workload counting module is used for calculating the workload of each user in a preset time period according to the number and the weight of the tasks to be processed of each category processed by the user in the preset time period; and determining the weight of each category of tasks to be processed according to the complexity of the category of tasks to be processed.
9. The system of claim 1, further comprising:
and the task reminding module is used for determining a corresponding reminding rule for each task to be processed and sending task processing reminding to a target user corresponding to the task to be processed at regular time based on the reminding rule.
10. The system of claim 9, wherein when the task reminding module sends the task processing reminder to the target user corresponding to the task to be processed, the task reminding module is specifically configured to:
and sending a task reminding mail, a task reminding short message or a task reminding popup to a target user corresponding to the task to be processed.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011292614.3A CN112396397A (en) | 2020-11-18 | 2020-11-18 | Operation and maintenance affair collection and management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202011292614.3A CN112396397A (en) | 2020-11-18 | 2020-11-18 | Operation and maintenance affair collection and management system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN112396397A true CN112396397A (en) | 2021-02-23 |
Family
ID=74606417
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202011292614.3A Pending CN112396397A (en) | 2020-11-18 | 2020-11-18 | Operation and maintenance affair collection and management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN112396397A (en) |
Cited By (5)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113191927A (en) * | 2021-04-20 | 2021-07-30 | 上海市环境科学研究院 | Intelligent pushing method and system for environmental protection data and readable storage medium |
| CN113298369A (en) * | 2021-05-17 | 2021-08-24 | 河南黄科工程技术检测有限公司 | Information processing method and system for engineering quality detection and detection terminal |
| CN113836579A (en) * | 2021-09-26 | 2021-12-24 | 多点生活(成都)科技有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN114091914A (en) * | 2021-11-19 | 2022-02-25 | 中国建设银行股份有限公司 | Work order processing method and device |
| CN116108420A (en) * | 2023-02-23 | 2023-05-12 | 国核信息科技有限公司 | Enterprise intranet portal system based on multi-service system integration and working method thereof |
-
2020
- 2020-11-18 CN CN202011292614.3A patent/CN112396397A/en active Pending
Cited By (6)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113191927A (en) * | 2021-04-20 | 2021-07-30 | 上海市环境科学研究院 | Intelligent pushing method and system for environmental protection data and readable storage medium |
| CN113298369A (en) * | 2021-05-17 | 2021-08-24 | 河南黄科工程技术检测有限公司 | Information processing method and system for engineering quality detection and detection terminal |
| CN113836579A (en) * | 2021-09-26 | 2021-12-24 | 多点生活(成都)科技有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN113836579B (en) * | 2021-09-26 | 2024-04-09 | 多点生活(成都)科技有限公司 | Data processing method and device, electronic equipment and storage medium |
| CN114091914A (en) * | 2021-11-19 | 2022-02-25 | 中国建设银行股份有限公司 | Work order processing method and device |
| CN116108420A (en) * | 2023-02-23 | 2023-05-12 | 国核信息科技有限公司 | Enterprise intranet portal system based on multi-service system integration and working method thereof |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN112396397A (en) | Operation and maintenance affair collection and management system | |
| US10073837B2 (en) | Method and system for implementing alerts in semantic analysis technology | |
| US8700414B2 (en) | System supported optimization of event resolution | |
| US20190066013A1 (en) | Robotic operations control system for a blended workforce | |
| US7657453B2 (en) | System, computer-readable medium and method for filtering exceptions generated by forecasting and replenishment engine | |
| US9026647B2 (en) | Systems and methods for a social media network/business platform interface | |
| CN111192004A (en) | Method for displaying current to-do task and subsequent to-do workflow | |
| US8825798B1 (en) | Business event tracking system | |
| CN106548324A (en) | A kind of IT system O＆M service management system | |
| EP2063384A1 (en) | Information processing method and device for work process analysis | |
| CN108874638B (en) | Intelligent cloud management based on portrait information | |
| US20100332509A1 (en) | Systems and methods for integrated management of governmental projects | |
| CN111400465B (en) | Generation method and device of customer service robot, electronic equipment and medium | |
| US20110161215A1 (en) | Method and System for Tracking Billing Information | |
| CN114119315A (en) | Enterprise-level intelligent security elimination management system and management method thereof | |
| US20100030596A1 (en) | Business Process Intelligence | |
| US20240054013A1 (en) | Systems and methods for maintaining data objects to manage asynchronous workflows | |
| CN114416769A (en) | To-do task query method and device and electronic equipment | |
| CN113537943A (en) | Universal workflow engine and construction method thereof | |
| US20130041712A1 (en) | Emerging risk identification process and tool | |
| CN110751452B (en) | Workflow management system, method and storage medium | |
| CN112364145A (en) | Work order processing method and device, electronic equipment and storage medium | |
| US11657063B2 (en) | Behavioral analytics in information technology infrasturcture incident management systems | |
| CN115719207A (en) | Super-automation platform system | |
| CN113869853A (en) | Office management system |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |