Problem event data processing method and device, computer equipment and storage medium
By generating structured event basic data and automatically generating event traceability diagrams, the problem of low data analysis efficiency in the event traceability link in vehicle research and development and manufacturing is solved, data sharing and collaborative analysis are realized, and problem analysis efficiency is improved.
Patent Information
- Application Number
- CN202411114616.1
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- Filing Date
- 2024-08-14
- Publication Date
- 2024-11-15
AI Technical Summary
In the field of vehicle research and development and manufacturing, data analysis is inefficient in the event traceability process, lack of clear data splitting rules and intelligent image generation, resulting in low efficiency in problem analysis.
By receiving event data submitted by the user, structured event basic data is generated and event traceability maps are automatically generated, supporting data editing and image adjustment, and data sharing and collaborative analysis are realized.
It improves the efficiency of problem analysis, solves the data island problem, and promotes collaborative work among engineers.
Smart Images

Figure CN118964465A_ABST
Abstract
Description
Technical Field
[0001] The present application relates to the technical field of vehicle R&D and manufacturing, and in particular to a method, device, computer equipment and storage medium for processing problem event data. Background Art
[0002] Double Zeroing is a systematic problem-solving and management strategy. Its core is to thoroughly solve problems from both the technical and management levels to ensure that problems do not recur, thereby improving overall operational efficiency and quality levels. At present, Double Zeroing has been widely used in multiple industries and fields. For example, in the field of vehicle R&D and manufacturing, by implementing Double Zeroing, problems in the vehicle design and manufacturing process can be thoroughly analyzed and solved, thereby improving the overall performance of the vehicle and user satisfaction.
[0003] Double zeroing of problems includes technical zeroing and management zeroing. In the event tracing link of the management zeroing step, engineers usually use office software such as Excel, PPT, Visio, etc. to create event information and then analyze the problem. The inventors noticed that there are no clear rules for the data splitting logic when performing data analysis in the event tracing link, and the relevant data is mainly presented in text, without intelligent image generation, and the element data of the image has no clear content, resulting in low efficiency of problem analysis. Summary of the invention
[0004] In response to the above-mentioned deficiencies or shortcomings, the present application provides a method, apparatus, computer device and storage medium for processing problem event data. The embodiments of the present application can split and convert data according to clear rules, and automatically generate an event tracing diagram using the converted data, which is conducive to improving the efficiency of problem analysis.
[0005] The present application provides a method for processing problem event data according to a first aspect. In some embodiments, the method includes:
[0006] Receive problem event data submitted by the first user end; the problem event data includes event description information filled in by an engineer associated with the first user end when performing problem management reset for a target problem that has occurred;
[0007] Generate a target problem identifier, convert the event description information into structured event basic data, and store the event basic data in association with the target problem identifier; the event basic data includes multiple event elements;
[0008] In response to an event tracing instruction carrying a target problem identifier, event basic data associated with the target problem identifier is obtained, and an event tracing graph is generated and displayed based on the obtained event basic data.
[0009] In some embodiments, the multiple event elements include event occurrence time, event object, event content, generation point, escape point and sequential flow of event occurrence; the event tracing diagram includes icons and explanatory information corresponding to the event occurrence time, event object, event content, generation point, escape point, and arrow lines connecting the event contents generated based on the sequential flow of event occurrence.
[0010] In some embodiments, after storing the event basic data in association with the target problem identifier, the method further includes:
[0011] Sharing event basic data with a second user terminal; the number of the second user terminals is one or more;
[0012] In response to a data editing request sent by the first user terminal or the second user terminal, the event basic data is modified according to the operation information carried in the data editing request.
[0013] In some embodiments, after generating and displaying an event tracing graph based on the acquired event basic data, the method further includes:
[0014] In response to a traceability graph editing request sent by the first user terminal or the second user terminal, the description information of the relevant event elements in the event traceability graph is adjusted according to the operation information carried in the traceability graph editing request, and the latest event traceability graph is displayed.
[0015] In some embodiments, after adjusting the description information of the relevant event elements in the event tracing graph according to the operation information carried in the tracing graph editing request, the method further includes:
[0016] The event basic data is synchronously updated according to the operation information carried in the traceability diagram editing request.
[0017] In some embodiments, converting the event description information into structured event basic data includes:
[0018] Split the event description information into multiple data items based on a preset analysis method;
[0019] Event element extraction is performed based on the multiple data items to obtain event basic data.
[0020] In some embodiments, generating an event traceability graph based on event basic data includes:
[0021] Format the event basic data;
[0022] Generate an event traceability graph based on the formatted event basic data.
[0023] The present application provides a problem event data device according to a second aspect. In some embodiments, the device includes:
[0024] A receiving module, configured to receive problem event data submitted by a first user terminal; the problem event data includes event description information filled in by an engineer associated with the first user terminal when performing problem management reset for a target problem that has occurred;
[0025] A data entry module, used to generate a target problem identifier, convert the event description information into structured event basic data, and store the event basic data in association with the target problem identifier; the event basic data includes a plurality of event elements;
[0026] The tracing diagram generation module is used to respond to the event tracing instruction carrying the target problem identifier, obtain the event basic data associated with the target problem identifier, generate an event tracing diagram based on the obtained event basic data, and display it.
[0027] According to a third aspect, the present application provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the problem event data processing method provided in any of the above embodiments are implemented.
[0028] According to a fourth aspect, the present application provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the problem event data processing method provided in any of the above embodiments are implemented.
[0029] In the above-mentioned embodiment of the present application, when the problem event data submitted by the first user terminal is received, a target problem identifier is generated, the event description information in the problem event data is converted into structured event basic data, and the event basic data is stored in association with the target problem identifier. Then, in response to an event tracing instruction carrying the target problem identifier, the currently stored event basic data associated with the target problem identifier is obtained, and an event tracing graph is generated and displayed based on the obtained event basic data. The embodiment of the present application can split the data and perform data conversion according to clear rules, and automatically generate an event tracing graph using the converted data, which is conducive to improving the efficiency of problem analysis.
[0030] In order to address the problem of data not being linked and information islands existing during problem analysis in the past, the embodiment of the present application shares the basic event data so that other engineers can edit the basic event data and the time tracing diagram generated based on the basic event data, so that engineers can collaborate on problem analysis, further improving the efficiency of problem analysis. BRIEF DESCRIPTION OF THE DRAWINGS
[0031] Figure 1 A flowchart of a method for processing problem event data provided by the present application according to one or more embodiments;
[0032] Figure 2 A structural block diagram of a problem event data device provided by the present application according to one or more embodiments;
[0033] Figure 3 This is a diagram of the internal structure of a computer device provided by the present application according to one or more embodiments. DETAILED DESCRIPTION
[0034] In order to make the purpose, technical solutions and advantages of the present application clearer, the embodiments of the present application will be further described in detail below in conjunction with the accompanying drawings. It should be clear that the described embodiments are only part of the embodiments of the present application, rather than all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in the field without creative work are within the scope of protection of the present application.
[0035] When the following description refers to the drawings, unless otherwise indicated, the same numbers in different drawings represent the same or similar elements. The embodiments described in the following exemplary embodiments do not represent all embodiments consistent with the present application. Instead, they are only examples of devices and methods consistent with some aspects of the present application as detailed in the attached claims.
[0036] In the description of the present application, it should be understood that the terms "first", "second", "third", etc. are only used to distinguish similar objects, and are not necessarily used to describe a specific order or sequence, nor can they be understood as indicating or implying relative importance. For those of ordinary skill in the art, the specific meanings of the above terms in the present application can be understood according to the specific circumstances. In addition, in the description of the present application, unless otherwise specified, "multiple" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships may exist. For example, A and / or B can represent: A exists alone, A and B exist at the same time, and B exists alone. The character " / " generally indicates that the objects associated before and after are in an "or" relationship.
[0037] In view of the shortcomings or defects of the prior art, the present application provides a method for processing problem event data. In some embodiments, the method includes: Figure 1 The steps shown are described below by taking the method applied to a data processing system (hereinafter referred to as the system, which may be implemented in the form of a single server, a cluster server, etc.) as an example.
[0038] S110: Receive problem event data submitted by the first user end, where the problem event data includes event description information filled in by an engineer associated with the first user end when performing problem management reset for a target problem that has occurred.
[0039] In the event tracing link of the problem management zeroing step, the engineer fills in various information related to the target problem that has occurred, such as a description of the problem (basic information about the problem), a description of the event (event description information), etc., and submits it to the system through the user terminal. Among them, the target problem refers to a problem that occurs during the research and development and manufacturing process of the whole vehicle, such as a product design problem that occurs during the research and development and manufacturing of the whole vehicle. The engineer can be any engineer responsible for the event tracing of the target problem, and the user terminal used by the engineer can be called the first user terminal to distinguish it from the user terminals used by other engineers that will appear below. The user terminal can be a computing device such as a computer, a laptop, or a smart phone.
[0040] In some embodiments, the problem event data may be information obtained by engineers using the 5W1h analysis method to describe the target problem. The 5W1H analysis method is an analysis method widely used in enterprise management, daily work life and learning. This analysis method helps the person conducting the analysis to systematically analyze and solve the problem by answering six questions, thereby improving work efficiency and decision-making quality. The six questions are Why, What, Where, When, Who and How. By allowing engineers to use the 5W1h analysis method to describe the problem, the accuracy of the description of the problem can be standardized at the early stage of event tracing, and the quality of the basic data of the problem can be improved.
[0041] S120: Generate a target problem identifier, convert the event description information into structured event basic data, and store the event basic data in association with the target problem identifier; the event basic data includes multiple event elements.
[0042] After receiving the problem event data, the system generates a unique problem identifier, namely the target problem identifier, for subsequent retrieval and search. In order to facilitate subsequent data processing, the system also converts the event description information into structured data.
[0043] In some embodiments, the operation of converting event description information into structured event basic data includes: splitting the event description information into multiple data items based on a preset analysis method; and performing event element extraction processing based on the multiple data items to obtain event basic data.
[0044] The preset analysis method may be the 5W1H analysis method mentioned above.
[0045] In this embodiment, the 5W1H analysis method can be used as the data splitting standard. The multiple data items can correspond to each question respectively, and then the event description information as a whole can be split into answer information related to each question during data splitting, and then the element information of multiple event elements can be extracted from it. The multiple event elements can be a pre-set data structure, such as a data field. In some embodiments, the multiple event elements can at least include event elements such as event occurrence time, event object, event content, generation point, escape point, and sequential flow direction of event occurrence.
[0046] This embodiment converts the event description data into data such as the event occurrence time, event object, event content, generation point, escape point, and the sequential flow of event occurrence. The split data facilitates engineers to conduct further event analysis, understand the process between events, and analyze the causes of problems.
[0047] The time of event occurrence refers to the specific time point or time period when the event actually occurs. The event object refers to the object affected or involved by the event, which can be personnel, equipment, system, organization, etc. Understanding the event object helps to determine the scope of impact and related responsibilities of the event. The event content is used to describe the specific circumstances and details of the event, such as what happened, the nature (or type) of the event, the results of the event, etc. The event content is the basis for engineers to analyze and handle the event. The generation point refers to the location or link where the event first occurred. Engineers who understand the generation point of the event can help identify the source of the event and conduct root cause analysis. The escape point refers to the location or link where the event is detected or discovered. Engineers who understand the escape point can help evaluate the propagation path and scope of impact of the event, as well as identify the deficiencies of the monitoring and detection system. The sequential flow of event occurrence is used to describe the order and flow of each link in the entire process from the generation of the event to its discovery or resolution. It can help engineers understand the development process of the event and analyze the propagation mechanism and impact path of the event.
[0048] In some embodiments, after the event basic data is stored in association with the target problem identifier, the method also includes: sharing the event basic data with a second user terminal; and, in response to a data editing request sent by the first user terminal or the second user terminal, modifying the event basic data according to the operation information carried in the data editing request.
[0049] In this embodiment, when the problem event data of the target problem is submitted to the system by an engineer and after the system completes the entry, the system will share the event basic data converted based on the problem event data with other engineers, so that other engineers can work together with the engineer to analyze problems and events together.
[0050] The second user terminal refers to a user terminal used by other engineers. The system can share the event basic data with one or more other engineers, so the number of the second user terminals can be one or more.
[0051] After the system shares the event basic data of the target problem, the engineer and other engineers can adjust the event basic data, specifically, they can adjust the element information of one or more event elements included in the event basic data (for example, modify the existing element information). For example, each engineer can query the event basic data of the target problem through the user end, and the event basic data can be presented on the user end through a visual operation interface, so that each engineer can determine the event element that needs to be modified through the visual operation interface and input new element information. The user end generates a data editing request in response to the operation performed by the engineer and sends it to the system. After the system receives the data editing request, it can modify the event basic data according to the operation information (such as new element information) carried in the data editing request.
[0052] S130: In response to an event tracing instruction carrying a target problem identifier, basic event data associated with the target problem identifier is obtained, and an event tracing graph is generated and displayed according to the obtained basic event data.
[0053] The event tracing instruction can be automatically triggered by the system or actively triggered by the engineer. After generating the basic event data, the system automatically generates an event tracing diagram in response to the instruction and sends the event tracing diagram to the engineer's user terminal. The engineer's user terminal will display the event tracing diagram. The event tracing diagram may include icons and description information corresponding to the event occurrence time, event object, event content, generation point, and escape point, as well as arrow connections between event contents generated based on the sequential flow of event occurrence. Through the visualized event tracing diagram, engineers can intuitively understand the process of event occurrence and thus more efficiently analyze the cause of the problem.
[0054] When an event tracing diagram is generated based on event basic data, corresponding icons can be generated for event elements such as event occurrence time, event object, event content, generation point, and escape point, and corresponding explanatory information can be generated for each of these event elements based on their corresponding element information. The explanatory information can be a text description.
[0055] In some embodiments, the operation of generating an event tracing graph based on event basic data includes: formatting the event basic data; and generating the event tracing graph based on the formatted event basic data.
[0056] Before generating an event tracing graph based on event basic data, this embodiment first processes the event basic data into data that conforms to a specified format to facilitate subsequent data visualization processing.
[0057] In some embodiments, after generating and displaying an event tracing graph based on the acquired event basic data, the method further includes: responding to a tracing graph editing request sent by the first user terminal or the second user terminal, adjusting the description information of relevant event elements in the event tracing graph according to the operation information carried in the tracing graph editing request, and displaying the latest event tracing graph.
[0058] In this embodiment, after the system generates the event traceability diagram, it can share the event traceability diagram, so that other engineers can also see the event traceability diagram through their own user terminals and edit the data in the event traceability diagram according to actual needs. Other engineers can specifically modify the description information of one or more event elements in the event traceability diagram, and can also adjust the arrow connections between event contents.
[0059] This embodiment enables engineers to work collaboratively by sharing the event traceability diagram and accepting editing of the event traceability diagram by other engineers, which is beneficial to improving the efficiency of problem analysis.
[0060] Furthermore, in some embodiments, after adjusting the description information of relevant event elements in the event traceability graph according to the operation information carried in the traceability graph editing request, the method further includes: synchronously updating the event basic data according to the operation information carried in the traceability graph editing request.
[0061] In this embodiment, when the data in the event tracing graph changes, the content of the event basic data associated with the event tracing graph will also be synchronously updated to ensure that the event basic data is consistent with the content of the event tracing graph.
[0062] It should be noted that, with respect to the various steps included in the problem event data processing method provided in any of the above embodiments, unless otherwise clearly stated in this document, there is no strict order restriction on the execution of these steps, and these steps can be executed in other orders. Moreover, at least a part of these steps can include multiple sub-steps or multiple stages, and these sub-steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these sub-steps or stages is not necessarily sequential, but can be executed in turn or alternately with other steps or at least a part of the sub-steps or stages of other steps.
[0063] Based on the same inventive concept, the present application also provides a problem event data processing device. In some embodiments, Figure 2 As shown, the problem event data processing device includes the following modules:
[0064] The receiving module 110 is used to receive the problem event data submitted by the first user end; the problem event data includes event description information filled in by the engineer associated with the first user end when performing problem management reset for the target problem that has occurred;
[0065] The data entry module 120 is used to generate a target problem identifier, convert the event description information into structured event basic data, and store the event basic data in association with the target problem identifier; the event basic data includes a plurality of event elements;
[0066] The tracing diagram generating module 130 is used to respond to the event tracing instruction carrying the target problem identifier, obtain the event basic data associated with the target problem identifier, generate an event tracing diagram according to the obtained event basic data, and display it.
[0067] In some embodiments, the multiple event elements include event occurrence time, event object, event content, generation point, escape point and sequential flow of event occurrence; the event tracing diagram includes icons and explanatory information corresponding to the event occurrence time, event object, event content, generation point, escape point, and arrow lines connecting the event contents generated based on the sequential flow of event occurrence.
[0068] In some embodiments, the apparatus further comprises:
[0069] A sharing module, used to share event basic data with a second user terminal; the number of the second user terminals is one or more;
[0070] The first editing module is used to respond to a data editing request sent by the first user terminal or the second user terminal, and modify the event basic data according to the operation information carried in the data editing request.
[0071] In some embodiments, the apparatus further comprises:
[0072] The second editing module is used to respond to the traceability diagram editing request sent by the first user terminal or the second user terminal, adjust the description information of the relevant event elements in the event traceability diagram according to the operation information carried in the traceability diagram editing request, and display the latest event traceability diagram.
[0073] In some embodiments, the apparatus further comprises:
[0074] The synchronous update module is used to synchronously update the event basic data according to the operation information carried in the traceability diagram editing request.
[0075] In some embodiments, the operation of the data entry module 120 converting the event description information into structured event basic data includes: splitting the event description information into multiple data items based on a preset analysis method; performing event element extraction processing based on the multiple data items to obtain the event basic data.
[0076] In some embodiments, the operation of the traceability graph generation module 130 generating an event traceability graph according to event basic data includes: formatting the event basic data; and generating an event traceability graph based on the formatted event basic data.
[0077] For the specific definition of the problem event data processing device, please refer to the definition of the problem event data processing method above, which will not be repeated here. The various modules in the above-mentioned problem event data processing device can be implemented in whole or in part by software, hardware and their combination. The above-mentioned modules can be embedded in or independent of the processor in the computer device in the form of hardware, or can be stored in the memory of the computer device in the form of software, so that the processor can call and execute the operations corresponding to the above modules.
[0078] In some embodiments, the present application provides a computer device, whose internal structure diagram can be as follows: Figure 3 As shown. The computer device includes a processor, a memory, a network interface and a database connected via a system bus. Among them, the processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data such as basic event data related to vehicle R&D and manufacturing problems that have occurred. The specific stored data can also be found in the definitions in the above method embodiments. The network interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for processing problem event data is implemented.
[0079] Those skilled in the art will understand that Figure 3 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.
[0080] This embodiment also provides a computer device, including a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, the steps of the problem event data processing method provided in any of the above embodiments can be implemented.
[0081] Specifically, when the processor executes the computer program, the following steps can be implemented:
[0082] Receive problem event data submitted by a first user end; the problem event data includes event description information filled in by an engineer associated with the first user end when performing problem management reset for a target problem that has occurred; generate a target problem identifier, convert the event description information into structured event basic data, and store the event basic data in association with the target problem identifier; the event basic data includes multiple event elements; in response to an event tracing instruction carrying a target problem identifier, obtain the event basic data associated with the target problem identifier, generate an event tracing diagram based on the obtained event basic data and display it.
[0083] In some embodiments, the multiple event elements include event occurrence time, event object, event content, generation point, escape point, and sequential flow of event occurrence; the event tracing diagram includes icons and explanatory information corresponding to the event occurrence time, event object, event content, generation point, escape point, and arrow lines connecting the event contents generated based on the sequential flow of event occurrence.
[0084] In one embodiment, after the processor executes the computer program to associate and store the event basic data with the target problem identifier, the processor further implements the following steps:
[0085] The event basic data is shared with a second user terminal; the number of the second user terminals is one or more; in response to a data editing request sent by the first user terminal or the second user terminal, the event basic data is modified according to the operation information carried in the data editing request.
[0086] In one embodiment, after the processor executes the computer program to generate and display an event tracing diagram based on the acquired event basic data, the processor further implements the following steps:
[0087] In response to a traceability graph editing request sent by the first user terminal or the second user terminal, the description information of the relevant event elements in the event traceability graph is adjusted according to the operation information carried in the traceability graph editing request, and the latest event traceability graph is displayed.
[0088] In one embodiment, after the processor executes the computer program to adjust the description information of the relevant event elements in the event traceability graph according to the operation information carried in the traceability graph editing request, the processor further implements the following steps:
[0089] The event basic data is synchronously updated according to the operation information carried in the traceability diagram editing request.
[0090] In one embodiment, when the processor executes the computer program to convert the event description information into structured event basic data, the processor also implements the following steps:
[0091] The event description information is split into multiple data items based on a preset analysis method; event element extraction and processing are performed based on the multiple data items to obtain event basic data.
[0092] In one embodiment, when the processor executes the computer program to generate an event traceability graph according to the event basic data, the processor further implements the following steps:
[0093] The event basic data is formatted; and an event tracing diagram is generated based on the formatted event basic data.
[0094] In some embodiments, the present application further provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the steps of the problem event data processing method provided in any of the above embodiments are implemented.
[0095] Specifically, when the computer program is executed by a processor, the following steps can be implemented:
[0096] Receive problem event data submitted by a first user end; the problem event data includes event description information filled in by an engineer associated with the first user end when performing problem management reset for a target problem that has occurred; generate a target problem identifier, convert the event description information into structured event basic data, and store the event basic data in association with the target problem identifier; the event basic data includes multiple event elements; in response to an event tracing instruction carrying a target problem identifier, obtain the event basic data associated with the target problem identifier, generate an event tracing diagram based on the obtained event basic data and display it.
[0097] In some embodiments, the multiple event elements include event occurrence time, event object, event content, generation point, escape point, and sequential flow of event occurrence; the event tracing diagram includes icons and explanatory information corresponding to the event occurrence time, event object, event content, generation point, escape point, and arrow lines connecting the event contents generated based on the sequential flow of event occurrence.
[0098] In one embodiment, the computer program is executed by a processor, and after storing the event basic data in association with the target problem identifier, the computer program further implements the following steps:
[0099] The event basic data is shared with a second user terminal; the number of the second user terminals is one or more; in response to a data editing request sent by the first user terminal or the second user terminal, the event basic data is modified according to the operation information carried in the data editing request.
[0100] In one embodiment, the computer program is executed by a processor, and after generating and displaying an event traceability graph based on the acquired event basic data, the computer program further implements the following steps:
[0101] In response to a traceability graph editing request sent by the first user terminal or the second user terminal, the description information of the relevant event elements in the event traceability graph is adjusted according to the operation information carried in the traceability graph editing request, and the latest event traceability graph is displayed.
[0102] In one embodiment, the computer program is executed by a processor, and after adjusting the description information of the relevant event elements in the event traceability graph according to the operation information carried in the traceability graph editing request, further implements the following steps:
[0103] The event basic data is synchronously updated according to the operation information carried in the traceability diagram editing request.
[0104] In one embodiment, when the computer program is executed by a processor to convert the event description information into structured event basic data, the following steps are also implemented:
[0105] The event description information is split into multiple data items based on a preset analysis method; event element extraction and processing are performed based on the multiple data items to obtain event basic data.
[0106] In one embodiment, when the computer program is executed by a processor to generate an event traceability graph according to event basic data, the following steps are further implemented:
[0107] The event basic data is formatted; and an event tracing diagram is generated based on the formatted event basic data.
[0108] In the above embodiments of the present application, the description of each embodiment has its own emphasis. For parts that are not described in detail in a certain embodiment, please refer to the relevant description of other embodiments.
[0109] Those skilled in the art can understand that all or part of the processes in the above method embodiments can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above methods. Among them, any reference to memory, storage, database or other media used in the embodiments provided in this application can include non-volatile and / or volatile memory. Non-volatile memory can include read-only memory (ROM), programmable ROM (PROM), electrically programmable ROM (EPROM), electrically erasable programmable ROM (EEPROM) or flash memory. Volatile memory can include random access memory (RAM) or external cache memory. As an illustration and not limitation, RAM is available in many forms, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate SDRAM (DDRSDRAM), enhanced SDRAM (ESDRAM), synchronous link (Synchlink), DRAM (SLDRAM), memory bus (Rambus), direct RAM (RDRAM), direct memory bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
[0110] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this specification.
[0111] The above-mentioned embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the invention patent. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application shall be subject to the attached claims.
Claims
1. A method for processing problem event data, characterized in that: The method comprises: Receive problem event data submitted by the first user end; the problem event data includes event description information filled in by an engineer associated with the first user end when performing problem management reset for a target problem that has occurred; Generate a target problem identifier, convert the event description information into structured event basic data, and store the event basic data in association with the target problem identifier; the event basic data includes a plurality of event elements; In response to an event tracing instruction carrying the target problem identifier, event basic data associated with the target problem identifier is obtained, and an event tracing graph is generated and displayed based on the obtained event basic data.
2. The method according to claim 1, characterized in that The multiple event elements include event occurrence time, event object, event content, generation point, escape point and sequential flow of event occurrence; the event tracing diagram includes icons and explanatory information corresponding to the event occurrence time, event object, event content, generation point, escape point, and arrow lines connecting the event contents generated based on the sequential flow of event occurrence.
3. The method according to claim 1, characterized in that After storing the event basic data in association with the target problem identifier, the method further includes: Sharing the event basic data with a second user terminal; the number of the second user terminals is one or more; In response to a data editing request sent by the first user terminal or the second user terminal, the event basic data is modified according to operation information carried in the data editing request.
4. The method according to claim 3, characterized in that After generating and displaying an event tracing graph based on the acquired event basic data, the method further includes: In response to a traceability graph editing request sent by the first user terminal or the second user terminal, the description information of the relevant event elements in the event traceability graph is adjusted according to the operation information carried in the traceability graph editing request, and the latest event traceability graph is displayed.
5. The method according to claim 4, characterized in that After adjusting the description information of the relevant event elements in the event tracing graph according to the operation information carried in the tracing graph editing request, the method further includes: The event basic data is synchronously updated according to the operation information carried in the traceability diagram editing request.
6. The method according to claim 1, characterized in that Convert the event description information into structured event basic data, including: Splitting the event description information into multiple data items based on a preset analysis method; Event element extraction is performed based on the multiple data items to obtain the event basic data.
7. The method according to claim 1, characterized in that Generate an event traceability graph based on the event basic data, including: Formatting the event basic data; Generate an event traceability graph based on the formatted event basic data.
8. A problem event data processing device, characterized in that: The device comprises: A receiving module, configured to receive problem event data submitted by a first user terminal; the problem event data includes event description information filled in by an engineer associated with the first user terminal when performing problem management reset for a target problem that has occurred; A data entry module, used to generate a target problem identifier, convert the event description information into structured event basic data, and store the event basic data in association with the target problem identifier; the event basic data includes a plurality of event elements; The tracing diagram generation module is used to respond to the event tracing instruction carrying the target problem identifier, obtain the event basic data associated with the target problem identifier, generate an event tracing diagram based on the obtained event basic data, and display it.
9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, characterized in that: When the processor executes the computer program, the steps of the method according to any one of claims 1 to 7 are implemented.
10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 7 are implemented.
Citation Information
Patent Citations
Complex product quality problem tracing method and system
CN112395424A
Associated event tracing method based on data dictionary and adjacent storage in cloud service
CN115757021A
