CN116070866A - Barrier reporting management system for business system - Google Patents
Barrier reporting management system for business system Download PDFInfo
- Publication number
- CN116070866A CN116070866A CN202310131464.5A CN202310131464A CN116070866A CN 116070866 A CN116070866 A CN 116070866A CN 202310131464 A CN202310131464 A CN 202310131464A CN 116070866 A CN116070866 A CN 116070866A
- Authority
- CN
- China
- Prior art keywords
- server
- client
- user
- execution
- processing result
- 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
- 230000004888 barrier function Effects 0.000 title description 2
- 238000012545 processing Methods 0.000 claims abstract description 93
- 238000004891 communication Methods 0.000 claims abstract description 15
- 230000008859 change Effects 0.000 claims description 26
- 238000012423 maintenance Methods 0.000 claims description 10
- 238000000034 method Methods 0.000 abstract description 24
- 230000008569 process Effects 0.000 abstract description 18
- 238000007726 management method Methods 0.000 description 15
- 230000009471 action Effects 0.000 description 3
- 238000012986 modification Methods 0.000 description 3
- 230000004048 modification Effects 0.000 description 3
- 230000032683 aging Effects 0.000 description 2
- 238000010586 diagram Methods 0.000 description 2
- 230000003203 everyday effect Effects 0.000 description 2
- 230000004075 alteration Effects 0.000 description 1
- 238000013523 data management Methods 0.000 description 1
- 238000011161 development Methods 0.000 description 1
- 230000018109 developmental process Effects 0.000 description 1
- 230000000750 progressive effect Effects 0.000 description 1
- 230000008439 repair process Effects 0.000 description 1
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/24—Querying
- G06F16/245—Query processing
- G06F16/2455—Query execution
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F16/00—Information retrieval; Database structures therefor; File system structures therefor
- G06F16/20—Information retrieval; Database structures therefor; File system structures therefor of structured data, e.g. relational data
- G06F16/28—Databases characterised by their database models, e.g. relational or object models
- G06F16/284—Relational databases
- G06F16/285—Clustering or classification
-
- 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
- G06Q10/063112—Skill-based matching of a person or a group to a task
Landscapes
- Engineering & Computer Science (AREA)
- Business, Economics & Management (AREA)
- Human Resources & Organizations (AREA)
- Theoretical Computer Science (AREA)
- Databases & Information Systems (AREA)
- Physics & Mathematics (AREA)
- General Physics & Mathematics (AREA)
- Economics (AREA)
- Strategic Management (AREA)
- General Engineering & Computer Science (AREA)
- Educational Administration (AREA)
- Data Mining & Analysis (AREA)
- Entrepreneurship & Innovation (AREA)
- General Business, Economics & Management (AREA)
- Game Theory and Decision Science (AREA)
- Tourism & Hospitality (AREA)
- Development Economics (AREA)
- Computational Linguistics (AREA)
- Quality & Reliability (AREA)
- Operations Research (AREA)
- Marketing (AREA)
- Debugging And Monitoring (AREA)
Abstract
The application provides a fault reporting management system for a business system, which comprises a server, a client and an execution end; the execution end is used for receiving the questions and the labels sent by the server and distributing the questions to the corresponding execution personnel through the labels; the execution end is used for generating a processing result after the execution personnel solve the problem and sending the processing result to the server; the execution end is used for receiving the real-time information corresponding to the user sent by the server and sending the reply information replied by the execution personnel to the server. The user is informed in the form of prompt information, namely short messages or mails, so that the user can pay attention to the processing process of the problem in real time, and can interact with executive personnel on line in real time to know the state of the communication problem and some doubt points encountered in the processing process of the problem in time.
Description
Technical Field
The application relates to the field of data management, in particular to a fault reporting management system for a business system.
Background
At present, the systems used in different types of companies are different, and various types of problems can occur in the use process of the systems, and fault reporting treatment is required for the problems.
For the fault reporting, the corresponding problems are generally solved by using the micro-community communication, but the aging and communication efficiency of the fault reporting system can not meet the current requirements obviously, so that a fault reporting system for processing the fault reporting is formed for the fault reporting in the existing system, and the fault reporting system is used for solving various system problems in combination with the actual conditions of the companies, each branch company and business department every day.
While the existing fault reporting system can solve the problems that the report problem entrance is scattered and the processing process cannot be recorded, in the processing process, a user wants to know the processing progress of the problem, and the user needs to log in the fault reporting system to check the progress and the state of the corresponding problem, and the real-time feedback of the state and the progress is the problem that the existing fault reporting system cannot solve.
Disclosure of Invention
In view of the problems, the present application has been made to provide a fault management system for a business system that overcomes the problems or at least partially solves the problems, including:
a fault reporting management system for a business system comprises a server, a client and an execution end;
the server is used for receiving the fault report problem set sent by the client;
the server is used for determining a label corresponding to the problem through the problem in the fault reporting problem set and sending the corresponding problem and the label to the execution end;
the server is used for receiving the processing information sent by the execution end and sending the processing information to the client;
the server is used for receiving the processing result sent by the execution end and sending the processing result to the client;
the server is used for generating state change information when the problem is changed in state and sending the state change information to the client corresponding to the problem;
the server is used for real-time communication between the executive of the executive end and the user corresponding to the problem in the client end.
Further, the server is further configured to generate a knowledge base with historical problems through the failure reporting problem set and the processing result, where the knowledge base is used for the execution end and the client to screen solutions of the historical problems.
Further, the server is configured to receive a first query request sent by the client, and query a first solution corresponding to the first query request in the knowledge base according to the first query request;
and/or the number of the groups of groups,
the server is used for receiving a second query request sent by the execution end and querying a second solution corresponding to the second query request in the knowledge base according to the second query request.
Further, the server is configured to receive the real-time information sent by the user and receive the reply information sent by the executive, and send the real-time information to the executive and send the reply information to the user.
A fault reporting management system for a business system comprises a server, a client and an execution end;
the execution end is used for receiving the questions and the labels sent by the server and distributing the questions to the corresponding execution personnel through the labels;
the execution end is used for generating a processing result after the execution personnel solve the problem and sending the processing result to the server;
the execution end is used for receiving the real-time information corresponding to the user sent by the server and sending the reply information replied by the execution personnel to the server;
the execution end is used for generating a second query request according to the execution personnel and sending the second query request to the server.
Further, the executing end is used for determining the problem type corresponding to the problem through the tag, and determining the executing personnel for solving the problem in the executing end according to the problem type.
Further, the problem type is one of an improper operation problem, a network problem, a data problem, and a system function logic problem.
Further, when the problem type is an improper operation problem, the execution end determines that the executive is a user corresponding to the problem, generates processing information according to the improper operation problem, and sends the processing information to the server;
or alternatively, the first and second heat exchangers may be,
when the problem type is a network problem, the execution end determines that the execution personnel is a network manager, distributes the problem to the network manager, generates a first processing result after the network manager performs network check and positioning to solve the network problem, and sends the first processing result to the server;
or alternatively, the first and second heat exchangers may be,
when the problem type is a data problem, the execution end determines that the execution personnel are operation and maintenance personnel, distributes the problem to the operation and maintenance personnel, generates a second processing result after the operation and maintenance personnel conduct data adjustment, and sends the second processing result to the server;
or alternatively, the first and second heat exchangers may be,
when the problem type is a system function logic problem, the execution end determines that the execution personnel is a system developer, distributes the problem to the system developer, establishes a corresponding task for tracking processing by the system developer, generates a third processing result after developing, repairing and upgrading the production environment, and sends the third processing result to the server.
A fault reporting management system for a business system comprises a server, a client and an execution end;
the client is used for the user to log in the client and upload a plurality of fault reporting problems in the client;
the client is used for generating the obstacle reporting problem set through a plurality of obstacle reporting problems and sending the obstacle reporting problem set to the server;
the client is used for receiving the processing result sent by the server and distributing the processing result to a corresponding target user;
the client is used for receiving the state change information sent by the server, generating prompt information through the state change information, and distributing the prompt information to the corresponding target user;
the client is used for sending the real-time information of the user to the server and receiving reply information corresponding to the reply of the executive sent by the server;
the client is used for generating a first query request according to the user and sending the first query request to the server.
Further, the client is configured to log in to the client by the user through a unique ID corresponding to the user.
The application has the following advantages:
in the embodiment of the present application, for the problem that in the prior art, "in the processing procedure, the user wants to know the processing progress of the problem, or need to log in the fault reporting system to check the progress and the state of the corresponding problem, and cannot realize the real-time feedback of the state and the progress", the present application provides a solution of "real-time reminding module, real-time communication module and history problem module", specifically: a failure reporting management system for a business system comprises a server, a client and an execution end; the server is used for receiving the fault report problem set sent by the client; the server is used for determining a label corresponding to the problem through the problem in the fault reporting problem set and sending the corresponding problem and the label to the execution end; the server is used for receiving the processing information sent by the execution end and sending the processing information to the client; the server is used for receiving the processing result sent by the execution end and sending the processing result to the client; the server is used for generating state change information when the problem is changed in state and sending the state change information to the client corresponding to the problem; the server is used for real-time communication between the executive of the executive and the user corresponding to the problem in the client. Generating state change information when the problem is changed, and transmitting the state change information to the client corresponding to the problem; the executive personnel of the executive end and the user corresponding to the problem in the client end carry out real-time communication, so that the problem that the user wants to know the processing progress of the problem in the processing process or needs to log in a fault reporting system to check the progress and state of the corresponding problem and cannot realize real-time feedback of the state and progress is solved, the problem that the user can pay attention to the processing process of the problem in real time by informing the user in the form of prompt information, namely a short message or mail, and the user can interact with the executive personnel in real time on line to know the state of the communication problem and some doubt points encountered in the processing process of the problem in time.
Drawings
In order to more clearly illustrate the technical solutions of the present application, the drawings that are needed in the description of the present application will be briefly described below, it being obvious that the drawings in the following description are only some embodiments of the present application, and that other drawings may be obtained according to these drawings without inventive effort to a person skilled in the art.
Fig. 1 is a block diagram of a fault management system for a service system according to an embodiment of the present application.
In the accompanying drawings: 110. a server; 120. an execution end; 130. and a client.
Detailed Description
In order to make the objects, features and advantages of the present application more comprehensible, the present application is described in further detail below with reference to the accompanying drawings and detailed description. It will be apparent that the embodiments described are some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art based on the embodiments herein without making any inventive effort, are intended to be within the scope of the present application.
The inventors found by analyzing the prior art that: for the fault reporting, the corresponding problems are generally solved by using the micro-community communication, but the aging and communication efficiency of the fault reporting system can not meet the current requirements obviously, so that a fault reporting system for processing the fault reporting is formed for the fault reporting in the existing system, and the fault reporting system is used for solving various system problems in combination with the actual conditions of the companies, each branch company and business department every day. The existing fault reporting system can solve the problems that the report problem entrance is scattered and the processing process cannot be recorded, but for the problems that the fault reporting system is used for solving or processing, a user wants to know the processing progress of the problems in the processing process, and the user needs to log in the fault reporting system to check the progress and state of the corresponding problems, and the real-time feedback of the state and the progress is the problem that the existing fault reporting system cannot solve.
Referring to fig. 1, a block diagram of a fault management system for a service system according to an embodiment of the present application is shown;
a fault reporting management system for a business system, the system comprising a server 110, a client 130 and an execution end 120;
the server 110 is configured to receive the failure report problem set sent by the client 130;
the server 110 is configured to determine a label corresponding to the problem through the problem in the fault report problem set, and send the corresponding problem and the label to the execution end 120;
the server 110 is configured to receive the processing information sent by the executing end 120, and send the processing information to the client 130;
the server 110 is configured to receive a processing result sent by the executing end 120, and send the processing result to the client 130;
the server 110 is configured to generate state change information when the problem occurs with a state change, and send the state change information to the client 130 corresponding to the problem;
the server 110 is configured to communicate in real time with the executive at the executive terminal 120 and the user corresponding to the problem at the client 130.
In the embodiment of the present application, for the problem that in the prior art, "in the processing procedure, the user wants to know the processing progress of the problem, or need to log in the fault reporting system to check the progress and the state of the corresponding problem, and cannot realize the real-time feedback of the state and the progress", the present application provides a solution of "real-time reminding module, real-time communication module and history problem module", specifically: "a fault reporting management system for a business system, the system includes a server 110, a client 130, and an execution end 120; the server 110 is configured to receive the failure report problem set sent by the client 130; the server 110 is configured to determine a label corresponding to the problem through the problem in the fault report problem set, and send the corresponding problem and the label to the execution end 120; the server 110 is configured to receive the processing information sent by the executing end 120, and send the processing information to the client 130; the server 110 is configured to receive a processing result sent by the executing end 120, and send the processing result to the client 130; the server 110 is configured to generate state change information when the problem occurs with a state change, and send the state change information to the client 130 corresponding to the problem; the server 110 is configured to communicate in real time with the executive at the executive terminal 120 and the user corresponding to the problem at the client 130. Generating state change information when a state change occurs through the question, and transmitting the state change information to the client 130 corresponding to the question; the real-time communication between the executive of the executive end 120 and the user corresponding to the problem in the client 130 "solves" the problem that the user wants to know the processing progress of the problem or needs to log in the fault reporting system to check the progress and state of the corresponding problem, and the problem that the real-time feedback of the state and progress cannot be realized "reaches the problem that the user can pay attention to the processing process of the problem in real time by informing the user in the form of prompt information, i.e. short messages or mails, and can enable the user to interact with the executive in real time online, so as to know the state of the communication problem and some doubt points encountered in the processing process of the problem in time.
Next, a fault management system for a service system in the present exemplary embodiment will be further described.
In one embodiment of the present invention, the server 110 is configured to generate state change information when the problem occurs with a state change, and send the state change information to the client 130 corresponding to the problem; in a specific embodiment, by adding a message reminding function, when the state of the problem changes, the user can be notified in the form of a prompt message, i.e. a short message or a mail, through the client 130, so that the processing process of the problem can be focused in real time.
In an embodiment of the present invention, the server 110 is configured to communicate in real time with the executive of the executive 120 and the user corresponding to the problem in the client 130; in an embodiment, by adding the instant messaging function, the user of the client 130 can interact with the executive of the executive 120 online in real time, so as to know the state of the communication problem and know some doubt points in the process of processing the problem in time.
In an embodiment of the present invention, the server 110 is further configured to generate a knowledge base with historical problems through the set of barrier-reporting problems and the processing result, where the knowledge base is used for the execution end 120 and the client 130 to screen solutions of the historical problems; in a specific embodiment, by enriching and optimizing the functions of the knowledge base, a relatively perfect knowledge base is established according to the accumulated common problems of each system and the operation guidance of the system functions, so that a user of the client 130 can solve a part of problems encountered by the user through the knowledge base, and an executive of the executive end 120 can quickly find out a processing scheme of some common problems through the knowledge base.
In an embodiment of the present invention, the server 110 is configured to receive a first query request sent by the client 130, and query, in the knowledge base, a first solution corresponding to the first query request according to the first query request;
and/or the number of the groups of groups,
the server 110 is configured to receive a second query request sent by the executing end 120, and query a second solution corresponding to the second query request in the knowledge base according to the second query request.
In one embodiment of the present invention, the server 110 is configured to receive the real-time information sent by the user and the reply information sent by the executive, and send the real-time information to the executive and the reply information to the user.
In an embodiment of the present invention, a fault reporting management system for a service system is also disclosed, where the system includes a server 110, a client 130, and an execution end 120;
the executing end 120 is configured to receive the question and the tag sent by the server 110, and distribute the question to the corresponding executing person through the tag;
the executing end 120 is configured to generate a processing result after the executing person solves the problem, and send the processing result to the server 110;
the executing end 120 is configured to receive real-time information corresponding to the user sent by the server 110, and send reply information replied by the executing person to the server 110;
the executing end 120 is configured to generate a second query request according to the executing person, and send the second query request to the server 110.
In an embodiment of the present invention, the executing end 120 is configured to determine, according to the type of the question, the type of the question corresponding to the question, and determine, according to the type of the question, the executing person for solving the question in the executing end 120.
In an embodiment of the present invention, the problem type is one of an improper operation problem, a network problem, a data problem, and a system function logic problem.
In an embodiment of the present invention, when the problem type is an improper operation problem, the executing end 120 determines that the executing person is a user corresponding to the problem, generates processing information according to the improper operation problem, and sends the processing information to the server 110;
or alternatively, the first and second heat exchangers may be,
when the problem type is a network problem, the executing end 120 determines that the executing person is a network administrator, distributes the problem to the network administrator, generates a first processing result after the network administrator performs network check and positioning to solve the network problem, and sends the first processing result to the server 110;
or alternatively, the first and second heat exchangers may be,
when the problem type is a data problem, the executing end 120 determines that the executing person is an operation and maintenance person, distributes the problem to the operation and maintenance person, generates a second processing result after the operation and maintenance person adjusts the data, and sends the second processing result to the server 110;
or alternatively, the first and second heat exchangers may be,
when the problem type is a system function logic problem, the execution end 120 determines that the executor is a system developer, distributes the problem to the system developer, establishes a corresponding task for tracking processing by the system developer, generates a third processing result after developing, repairing and upgrading the production environment, and sends the third processing result to the server 110.
In one embodiment, the problem type is an improper operation problem, and the correct operation step, i.e. the processing information, is directly fed back to the user through the server 110.
In a specific embodiment, the problem type is a network problem, and the first processing result is fed back to the user through the server 110 after the network check and positioning are performed to the corresponding network administrator.
In a specific embodiment, the problem type is a data problem, the operation and maintenance personnel performs operations such as several adjustments according to the data corresponding to the operation required, and after the operations are completed, the processed data is fed back to the user through the server 110.
In a specific embodiment, if the problem type is a system function logic problem, the corresponding problem is fed back to a corresponding system developer, the system developer establishes a corresponding task to perform tracking processing, and after the development, repair and upgrade production environment is completed, the solution process and the third processing result are fed back to the user through the server 110.
In an embodiment of the present invention, a fault reporting management system for a service system is also disclosed, where the system includes a server 110, a client 130, and an execution end 120;
the client 130 is configured to log in the client 130 by the user, and upload a plurality of fault reporting problems in the client 130;
the client 130 is configured to generate the failure reporting problem set through a plurality of failure reporting problems, and send the failure reporting problem set to the server 110;
the client 130 is configured to receive the processing result sent by the server 110, and distribute the processing result to a corresponding target user;
the client 130 is configured to receive the state change information sent by the server 110, generate a prompt message according to the state change information, and distribute the prompt message to the corresponding target user;
the client 130 is configured to send the real-time information of the user to the server 110, and receive reply information sent by the server 110 and corresponding to the reply of the executive;
the client 130 is configured to generate a first query request according to the user, and send the first query request to the server 110.
In one embodiment of the present invention, the client 130 is configured to log in the client 130 by the user through a unique ID corresponding to the user; in one embodiment, a user logs into client 130 using a unique ID, i.e., employee number, and submits a fault report issue that is found when using a corporate business system; various company business system problems submitted by users, such as: non-vehicle underwriting systems cannot be accessed normally, etc.
In this specification, each embodiment is described in a progressive manner, and each embodiment is mainly described by differences from other embodiments, and identical and similar parts between the embodiments are all enough to be referred to each other.
While preferred embodiments of the present embodiments have been described, additional variations and modifications in those embodiments may occur to those skilled in the art once they learn of the basic inventive concepts. It is therefore intended that the following claims be interpreted as including the preferred embodiments and all such alterations and modifications as fall within the scope of the embodiments of the present application.
Finally, it is further noted that relational terms such as first and second, and the like are 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. Moreover, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or terminal 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 terminal. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article or terminal device comprising the element.
The foregoing has described in detail a fault management system for a service system provided in the present application, and specific examples have been applied herein to illustrate the principles and embodiments of the present application, where the foregoing examples are only for aiding in understanding the method and core idea of the present application; meanwhile, as those skilled in the art will have modifications in the specific embodiments and application scope in accordance with the ideas of the present application, the present description should not be construed as limiting the present application in view of the above.
Claims (10)
1. The fault reporting management system for the business system is characterized by comprising a server, a client and an execution end;
the server is used for receiving the fault report problem set sent by the client;
the server is used for determining a label corresponding to the problem through the problem in the fault reporting problem set and sending the corresponding problem and the label to the execution end;
the server is used for receiving the processing information sent by the execution end and sending the processing information to the client;
the server is used for receiving the processing result sent by the execution end and sending the processing result to the client;
the server is used for generating state change information when the problem is changed in state and sending the state change information to the client corresponding to the problem;
the server is used for real-time communication between the executive of the executive end and the user corresponding to the problem in the client end.
2. The system of claim 1, wherein the server is further configured to generate a knowledge base with historical problems from the set of barrier-reporting problems and the processing results, the knowledge base being used by the execution side and the client to screen solutions to the historical problems.
3. The system of claim 2, wherein the server is configured to receive a first query request sent by the client, and query the knowledge base for a first solution corresponding to the first query request based on the first query request;
and/or the number of the groups of groups,
the server is used for receiving a second query request sent by the execution end and querying a second solution corresponding to the second query request in the knowledge base according to the second query request.
4. The system of claim 1, wherein the server is configured to receive real-time information sent by the user and to receive reply information sent by the executive, and to send the real-time information to the executive and the reply information to the user.
5. The fault reporting management system for the business system is characterized by comprising a server, a client and an execution end;
the execution end is used for receiving the questions and the labels sent by the server and distributing the questions to the corresponding execution personnel through the labels;
the execution end is used for generating a processing result after the execution personnel solve the problem and sending the processing result to the server;
the execution end is used for receiving the real-time information corresponding to the user sent by the server and sending the reply information replied by the execution personnel to the server;
the execution end is used for generating a second query request according to the execution personnel and sending the second query request to the server.
6. The system of claim 5, wherein the executive is configured to determine a type of question corresponding to the question via the tag, and determine the executive for solving the question in the executive based on the type of question.
7. The system of claim 6, wherein the problem type is one of an mishandling problem, a network problem, a data problem, and a system function logic problem.
8. The system of claim 7, wherein when the problem type is an improper operation problem, the executive determines that the executive is a user corresponding to the problem, generates processing information according to the improper operation problem, and transmits the processing information to the server;
or alternatively, the first and second heat exchangers may be,
when the problem type is a network problem, the execution end determines that the execution personnel is a network manager, distributes the problem to the network manager, generates a first processing result after the network manager performs network check and positioning to solve the network problem, and sends the first processing result to the server;
or alternatively, the first and second heat exchangers may be,
when the problem type is a data problem, the execution end determines that the execution personnel are operation and maintenance personnel, distributes the problem to the operation and maintenance personnel, generates a second processing result after the operation and maintenance personnel conduct data adjustment, and sends the second processing result to the server;
or alternatively, the first and second heat exchangers may be,
when the problem type is a system function logic problem, the execution end determines that the execution personnel is a system developer, distributes the problem to the system developer, establishes a corresponding task for tracking processing by the system developer, generates a third processing result after developing, repairing and upgrading the production environment, and sends the third processing result to the server.
9. The fault reporting management system for the business system is characterized by comprising a server, a client and an execution end;
the client is used for the user to log in the client and upload a plurality of fault reporting problems in the client;
the client is used for generating the obstacle reporting problem set through a plurality of obstacle reporting problems and sending the obstacle reporting problem set to the server;
the client is used for receiving the processing result sent by the server and distributing the processing result to a corresponding target user;
the client is used for receiving the state change information sent by the server, generating prompt information through the state change information, and distributing the prompt information to the corresponding target user;
the client is used for sending the real-time information of the user to the server and receiving reply information corresponding to the reply of the executive sent by the server;
the client is used for generating a first query request according to the user and sending the first query request to the server.
10. The system of claim 9, wherein the client is configured to log onto the client by the user with a unique ID corresponding to the user.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310131464.5A CN116070866A (en) | 2023-02-03 | 2023-02-03 | Barrier reporting management system for business system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202310131464.5A CN116070866A (en) | 2023-02-03 | 2023-02-03 | Barrier reporting management system for business system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN116070866A true CN116070866A (en) | 2023-05-05 |
Family
ID=86173007
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202310131464.5A Pending CN116070866A (en) | 2023-02-03 | 2023-02-03 | Barrier reporting management system for business system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN116070866A (en) |
Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106789271A (en) * | 2016-12-27 | 2017-05-31 | 中国建设银行股份有限公司 | One kind report barrier processing method and system |
| CN106790698A (en) * | 2017-02-22 | 2017-05-31 | 镇江康恒信息科技有限公司 | A kind of system of online interaction question and answer |
| CN108681980A (en) * | 2018-05-10 | 2018-10-19 | 西安壹云电力科技有限公司 | Interactive repair reporting system based on APP and method |
| CN108847953A (en) * | 2018-04-25 | 2018-11-20 | 合肥智圣新创信息技术有限公司 | A kind of O&M service system and method |
| CN111967975A (en) * | 2020-08-19 | 2020-11-20 | 中国银行股份有限公司 | Service problem processing system and working method |
| CN112085225A (en) * | 2020-08-19 | 2020-12-15 | 国家电网有限公司 | Operation and maintenance system and method for user side power equipment |
| CN113810457A (en) * | 2021-04-06 | 2021-12-17 | 北京京东拓先科技有限公司 | Method and device for reporting service access exception, readable storage medium and electronic equipment |
-
2023
- 2023-02-03 CN CN202310131464.5A patent/CN116070866A/en active Pending
Patent Citations (7)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN106789271A (en) * | 2016-12-27 | 2017-05-31 | 中国建设银行股份有限公司 | One kind report barrier processing method and system |
| CN106790698A (en) * | 2017-02-22 | 2017-05-31 | 镇江康恒信息科技有限公司 | A kind of system of online interaction question and answer |
| CN108847953A (en) * | 2018-04-25 | 2018-11-20 | 合肥智圣新创信息技术有限公司 | A kind of O&M service system and method |
| CN108681980A (en) * | 2018-05-10 | 2018-10-19 | 西安壹云电力科技有限公司 | Interactive repair reporting system based on APP and method |
| CN111967975A (en) * | 2020-08-19 | 2020-11-20 | 中国银行股份有限公司 | Service problem processing system and working method |
| CN112085225A (en) * | 2020-08-19 | 2020-12-15 | 国家电网有限公司 | Operation and maintenance system and method for user side power equipment |
| CN113810457A (en) * | 2021-04-06 | 2021-12-17 | 北京京东拓先科技有限公司 | Method and device for reporting service access exception, readable storage medium and electronic equipment |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| CN107358422B (en) | Payment system based on block chain technology | |
| US9774462B2 (en) | Methods and apparatus for requesting message gap fill requests and responding to message gap fill requests | |
| US20090037332A1 (en) | Systems and Methods for Processing Banking Transactions | |
| JP2018536245A (en) | Trademark information management system and method | |
| CN106537377B (en) | A kind of after-sale service platform based on cloud framework | |
| US20090043882A1 (en) | Systems and methods for consolidated service level agreements | |
| CN101919138A (en) | Presence enabled instance messaging for distributed energy management solutions | |
| KR101589160B1 (en) | A communication device | |
| CN115391758B (en) | Self-service business platform system | |
| CN101075969B (en) | Method, apparatus and system for controlling data transmission | |
| CN111832943A (en) | Hardware equipment fault management method and device, electronic equipment and storage medium | |
| EP1389328A2 (en) | Financial market trading system | |
| US10541556B2 (en) | System and approach to integrate and manage diverse demand response specifications for multi-site enterprises | |
| CN116070866A (en) | Barrier reporting management system for business system | |
| Wan et al. | Improving service management in campus IT operations | |
| US8117334B2 (en) | System and methods for workflow management | |
| US7810101B2 (en) | Task harmonization layer | |
| KR101518837B1 (en) | Method for Providing Equipment Maintanance Service, and Managing Server Used Therein | |
| CN111080197B (en) | Material performance system and method | |
| US20200226680A1 (en) | Financial market trading system | |
| KR20020087314A (en) | A guestion preparation system and method | |
| KR20200129254A (en) | Equipment maintenance service methods and systems on the network | |
| CN110825799A (en) | Fruit hatching method | |
| CN116843295B (en) | Method and system for processing interactive information on asset securitization line | |
| CN113191686A (en) | Parameter change processing method, device and 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 | ||
| RJ01 | Rejection of invention patent application after publication |
Application publication date: 20230505 |
|
| RJ01 | Rejection of invention patent application after publication |