Fault data processing method and fault data processing platform

Abstract

The invention provides a fault data processing method and a fault data processing platform. The fault data processing method comprises the following steps: importing a maintenance work order into a fault processing interface; identifying the maintenance work order, determining fault information of the maintenance work order, and determining a fault type corresponding to the maintenance work order according to the fault information; receiving an operation which is executed on the fault processing interface and is used for querying order sending information corresponding to each maintenance work order; and in response to the operation, executing the following processing for each maintenance work order: determining a maintenance processing suggestion corresponding to the maintenance work order according to the fault type, generating first maintenance data corresponding to the work order number according to the maintenance processing suggestion, the work order number, the agricultural machine parameter information and the repair requesting personnel information, and storing the first maintenance data in a service database, and second maintenance data corresponding to the maintenance work order stored in the service database is called and displayed to provide order sending suggestions, and the second maintenance data comprises the first maintenance data and order sending data. According to the invention, the processing efficiency of the maintenance work order is improved.

Description

Technical Field

[0001] The present application relates to the technical field of work order processing, and in particular to a fault data processing method and a fault data processing platform. Background Art

[0002] At present, for agricultural machinery maintenance, the service personnel of the maintenance station will first obtain the original service work order data from the CC (Customer Service Center) system and CRM (Customer Relationship Management) system. These data include the customer's basic information, the specific content of the repair report, the agricultural machinery model and fault description, etc. Then, they will manually record the relevant information. After obtaining the service work order data, the service personnel will use their professional knowledge and experience to make a rough estimate of the working condition of the agricultural machinery, and preliminarily judge the type and severity of the agricultural machinery failure based on the repair report. The service personnel will allocate service resources according to the fault condition of the agricultural machinery.

[0003] Regarding the allocation of service resources, service personnel will first obtain the parts relationship through the parts system to find the parts information that matches the faulty agricultural machinery, and then query the available inventory of these parts in the inventory system. By comparing the inventory quantity of different parts, the degree of matching with agricultural machinery, the skill level of maintenance personnel, workload, and the urgency of agricultural machinery, etc., service personnel will make decisions and arrange maintenance tasks.

[0004] However, in the process of data collation, we need to manually extract data from the business interfaces of multiple end systems. These data may be distributed in different databases, files or systems. Therefore, obtaining data requires a lot of time and effort. Moreover, these data have not been cleaned and verified, and the accuracy and completeness of the data cannot be guaranteed. The data may be duplicated, erroneous or inconsistent. Summary of the invention

[0005] In view of this, the purpose of the present application is to provide a fault data processing method and a fault data processing platform to overcome at least one of the above-mentioned defects.

[0006] In a first aspect, an embodiment of the present application provides a fault data processing method, the method comprising: importing a maintenance work order into a fault processing interface, the maintenance work order comprising a work order number, fault information, agricultural machinery parameter information and repair personnel information; identifying the maintenance work order, determining the fault information of the maintenance work order, and determining the fault type corresponding to the maintenance work order based on the fault information; receiving an operation performed on the fault processing interface for querying the dispatch information corresponding to each maintenance work order; in response to the operation, performing the following processing for each maintenance work order: determining a maintenance processing suggestion corresponding to the maintenance work order based on the fault type, generating first maintenance data corresponding to the work order number based on the maintenance processing suggestion, the work order number, the agricultural machinery parameter information and the repair personnel information, storing the first maintenance data in a business database, retrieving and displaying second maintenance data corresponding to the maintenance work order stored in the business database to provide dispatch suggestions, the second maintenance data comprising first maintenance data and dispatch data.

[0007] In an optional embodiment of the present application, the fault type corresponding to the maintenance work order is determined in the following manner: the fault information is read, and the fault level of the maintenance work order is determined by classifying the fault information using predefined fault level determination rules; and based on the fault information and the fault level, the historical work order fault type data stored in the fault library is queried to determine the fault type corresponding to the maintenance work order.

[0008] In an optional embodiment of the present application, the maintenance processing suggestion corresponding to the maintenance work order is determined in the following manner: query all data in the fault library with the same fault type as that corresponding to the maintenance work order; for each piece of data, filter out target data with the same agricultural machinery model as that in the agricultural machinery parameter information through the agricultural machinery parameter information; determine the maintenance processing suggestion corresponding to the target data as the maintenance processing suggestion corresponding to the maintenance work order, and the maintenance processing suggestion includes replacing parts or repairing the agricultural machinery.

[0009] In an optional embodiment of the present application, the dispatch data includes parts data and service data, wherein the parts data is determined in the following manner: receiving an operation performed on the fault processing interface for querying the parts data corresponding to each repair work order; in response to the operation, performing the following processing for each repair work order: establishing a connection with the business database, filtering the sales records corresponding to the agricultural machinery model and the parts model information corresponding to the agricultural machinery model in the business database according to the agricultural machinery model corresponding to the agricultural machinery parameter information, determining the target part model information matching the fault part number according to the fault part number corresponding to the fault information, determining the agricultural machinery model and the target part model information as the parts data of the repair work order, and storing them together with the first maintenance data.

[0010] In an optional embodiment of the present application, the service data is determined in the following manner: an operation performed on the fault handling interface to query the service data corresponding to each maintenance work order is received; in response to the operation, the following processing is performed for each maintenance work order: based on the repair personnel information, the repair location is identified to obtain the service site, service personnel and service vehicle around the repair location, and the service site, service personnel and service vehicle are determined as the service data of the maintenance work order, and stored together with the first maintenance data.

[0011] In an optional embodiment of the present application, the method also includes: receiving an operation performed on the fault handling interface for querying the maintenance node corresponding to each maintenance work order; in response to the operation, performing the following processing for each maintenance work order: determining the location of the service personnel and the location of the service vehicle based on the work order number to determine the maintenance node of the maintenance work order.

[0012] In an optional embodiment of the present application, the business database is constructed in the following manner: receiving full data for the first time and storing the full data in the business database; setting a preset storage time, and using the preset storage time as a time interval except for the first time receiving full data, receiving incremental data, and storing the incremental data in the business database to query dispatch data, wherein the incremental data is data added after receiving the full data for storage in the business database.

[0013] In the second aspect, the embodiment of the present application also provides a fault data processing platform, which includes: an import module, which is used to import a maintenance work order in a fault processing interface, and the maintenance work order includes a work order number, fault information, agricultural machinery parameter information and repair personnel information; a fault type determination module, which is used to identify the maintenance work order, determine the fault information of the maintenance work order, and determine the fault type corresponding to the maintenance work order based on the fault information; a receiving module, which is used to receive an operation performed on the fault processing interface to query the dispatch information corresponding to each maintenance work order; a second maintenance data display module, which is used to respond to the operation and perform the following processing for each maintenance work order: according to the fault type, determine the maintenance processing suggestion corresponding to the maintenance work order, generate first maintenance data corresponding to the work order number according to the maintenance processing suggestion, the work order number, the agricultural machinery parameter information and the repair personnel information, and store it in a business database, retrieve and display the second maintenance data corresponding to the maintenance work order stored in the business database to provide dispatch suggestions, and the second maintenance data includes first maintenance data and dispatch data.

[0014] In a third aspect, an embodiment of the present application further provides an electronic device, comprising: a processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and when the machine-readable instructions are executed by the processor, the steps of the method described above are performed.

[0015] In a fourth aspect, an embodiment of the present application further provides a computer-readable storage medium, on which a computer program is stored, and when the computer program is executed by a processor, the steps of the method described above are executed.

[0016] The fault data processing method and fault data processing platform provided in the embodiment of the present application import a maintenance work order into the fault processing interface; identify the maintenance work order, determine the fault information of the maintenance work order, and determine the fault type corresponding to the maintenance work order based on the fault information; receive an operation executed on the fault processing interface to query the dispatch information corresponding to each maintenance work order; in response to the operation, perform the following processing for each maintenance work order: determine the maintenance processing suggestion corresponding to the maintenance work order based on the fault type, generate the first maintenance data corresponding to the work order number based on the maintenance processing suggestion, the work order number, the agricultural machinery parameter information and the repair personnel information, store it in the business database, retrieve and display the second maintenance data corresponding to the maintenance work order stored in the business database to provide dispatch suggestions, the second maintenance data includes the first maintenance data and the dispatch data. Through this application, the processing efficiency of maintenance work orders is improved, the data barriers between business systems are broken, the data island phenomenon is eliminated, and the data can give full play to its due value, providing strong data support for the decision-making and business operations of enterprises.

[0017] In order to make the above-mentioned objects, features and advantages of the present application more obvious and easy to understand, preferred embodiments are specifically cited below and described in detail with reference to the attached drawings. BRIEF DESCRIPTION OF THE DRAWINGS

[0018] In order to more clearly illustrate the technical solutions of the embodiments of the present application, the drawings required for use in the embodiments will be briefly introduced below. It should be understood that the following drawings only show certain embodiments of the present application and therefore should not be regarded as limiting the scope. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0019] Figure 1 A flowchart of a fault data processing method provided in an embodiment of the present application;

[0020] Figure 2 A schematic diagram of the structure of the fault data processing platform provided in the embodiment of the present application;

[0021] Figure 3 A schematic diagram of the structure of an electronic device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0022] To make the purpose, technical scheme and advantages of the embodiments of the present application clearer, the technical scheme in the embodiments of the present application will be clearly and completely described below in conjunction with the drawings in the embodiments of the present application. Obviously, the described embodiments are only a part of the embodiments of the present application, rather than all of the embodiments. The components of the embodiments of the present application usually described and shown in the drawings here can be arranged and designed in various different configurations. Therefore, the following detailed description of the embodiments of the present application provided in the drawings is not intended to limit the scope of the application claimed for protection, but merely represents the selected embodiments of the present application. Based on the embodiments of the present application, each other embodiment obtained by those skilled in the art without making creative work belongs to the scope of protection of the present application.

[0023] First, the application scenarios to which the present application is applicable are introduced. The present application can be applied to the technical field of work order processing.

[0024] Research has found that during the busy farming seasons such as summer and autumn, when faced with a large number of agricultural machinery service work orders, maintenance service and management personnel in various regions face a major challenge of quickly and efficiently mastering various complex information, including different models, different factory dates, agricultural machinery conditions in different locations, work order repair conditions, agricultural machinery failure conditions, spare parts inventory, etc. This information is crucial for making reasonable decision scheduling.

[0025] During the maintenance service process, in order to obtain real-time information, we need to constantly communicate with all parties, including customers, suppliers, internal teams, etc. This communication method is not only inefficient, but also prone to errors. In addition, service dispatch often relies on personal experience, which makes the dispatch process complicated and time-consuming, and it is difficult to guarantee the accuracy and fairness of the results.

[0026] Due to the complexity of the service dispatch process and the large number of people involved, the final result data granularity is very large, making it difficult to effectively analyze and utilize. This makes it impossible for us to grasp the actual situation of service resource allocation in real time and accurately, which in turn affects service quality and customer satisfaction.

[0027] What is more serious is that historical agricultural machinery service data are often idle or ignored and cannot play their due value. These data contain rich information and experience. If they can be effectively used, they will help us better understand service needs, optimize resource allocation, and improve service efficiency and quality.

[0028] Based on this, the embodiment of the present application provides a fault data processing method and a fault data processing platform, which imports a maintenance work order into a fault processing interface; identifies the maintenance work order, determines the fault information of the maintenance work order, and determines the fault type corresponding to the maintenance work order based on the fault information; receives an operation executed on the fault processing interface to query the dispatch information corresponding to each maintenance work order; in response to the operation, performs the following processing for each maintenance work order: determines the maintenance processing suggestion corresponding to the maintenance work order based on the fault type, generates the first maintenance data corresponding to the work order number based on the maintenance processing suggestion, the work order number, the agricultural machinery parameter information and the repair personnel information, stores it in the business database, retrieves and displays the second maintenance data corresponding to the maintenance work order stored in the business database, and provides dispatch suggestions, the second maintenance data includes the first maintenance data and the dispatch data. Through this application, the processing efficiency of maintenance work orders is improved, the data barriers between business systems are broken, and the data island phenomenon is eliminated.

[0029] See also Figure 1 , Figure 1 This is a flow chart of the fault data processing method provided in the embodiment of the present application. Figure 1 As shown in , the fault data processing method provided by the embodiment of the present application includes:

[0030] S101. Import a maintenance work order into the fault handling interface.

[0031] Here, the maintenance work order includes the work order number, fault information, agricultural machinery parameter information and repair personnel information.

[0032] When the person reporting the problem calls the 400 customer service number, he / she must provide fault information, agricultural machinery parameter information, and the person reporting the problem information.

[0033] Agricultural machinery parameter information includes key information such as agricultural machinery equipment number, agricultural machinery model, production date and purchase channel; the information of the person reporting the problem includes contact information such as name and contact number; when describing the fault information, it is necessary to be as detailed and specific as possible, including the time, frequency, phenomenon of the fault and whether you have tried to solve it yourself, etc. This will help to more accurately determine the problem and provide more professional solutions. In addition, in order to locate the repair location more quickly, you also need to provide specific address information or GPS positioning data so that the nearest maintenance personnel can be arranged to handle it.

[0034] Here, when the customer service staff receives a repair call from a customer, they will record the specific content of the repair in detail based on the problem description of the repair user, including key information such as the fault phenomenon, occurrence time, and device model. Then, the customer service staff will quickly create a maintenance work order in the system based on this information. This work order will record key information such as the customer's contact information and repair content in detail.

[0035] During the service process, this work order data will serve as an important basis for service tracking, ensuring that maintenance service personnel can promptly understand customer needs and problems and take appropriate measures to solve them. At the same time, customer service personnel will also track the progress of work orders in real time through the system, communicate with customers in a timely manner, inform them of the progress of maintenance, and ensure that customers can understand the service status at any time.

[0036] S102: Identify the maintenance work order, determine the fault information of the maintenance work order, and determine the fault type corresponding to the maintenance work order according to the fault information.

[0037] In this step, the fault type corresponding to the maintenance work order is determined in the following ways:

[0038] Read fault information, classify fault information using predefined fault level determination rules, and determine the fault level of the maintenance work order;

[0039] Read the fault information in the work order. After receiving the service work order, quickly and accurately classify the work order according to the fault information and the established fault level judgment rules. These rules are based on multiple dimensions such as the urgency of the fault, the scope of impact, and the difficulty of repair to ensure the fairness and rationality of the classification.

[0040] After classifying work orders into major faults, serious faults, general faults, other faults and other levels, we will formulate corresponding order processing priorities according to the different fault levels; for major faults, we will immediately activate the emergency response mechanism to ensure that resources are deployed in the shortest time and organize professional service personnel to carry out emergency repairs to minimize the impact on agricultural machinery operations; for serious faults and general faults, we will reasonably arrange maintenance plans and personnel dispatch according to the specific circumstances to ensure that the faults are handled in a timely and effective manner. For other accidents, they will be handled in sequence.

[0041] Preferably, the fault level of the maintenance work order can be determined by keyword recognition. If there are words such as fire and explosion, it is considered a major fault. The recognition cases determined by historical human subjective consciousness are used as the standard and laid down as the judgment rules for the fault level.

[0042] According to the fault information and fault level, query the historical work order fault type data stored in the fault database to determine the fault type corresponding to the maintenance work order.

[0043] In an optional embodiment, by referring to the historical work order fault type data, a comprehensive fault library is constructed for various types of agricultural machinery. The fault library will cover various common fault types and their characteristics to accurately identify and solve problems.

[0044] The fault library includes specific handling opinions or steps corresponding to the fault categories.

[0045] On the basis of building the fault database, the fault types in the service tickets are further divided into detailed categories. This division helps to deeply understand the nature of the fault and provide targeted guidance for subsequent troubleshooting and processing.

[0046] In another optional embodiment, the fault type is accurately classified according to the fault information described in detail in the maintenance work order.

[0047] For example, the fault types are tensioning sprocket failure, RA series rice machine failure, RX series rotary tiller failure, electrical system failure, engine electrical assembly failure, reversing alarm failure, angle sensor bracket failure, engine electrical assembly failure, engine wiring harness assembly failure, threaded connecting rod failure, and tightening fuse 30A failure, etc.

[0048] S103: receiving an operation executed on the fault handling interface for querying dispatch information corresponding to each maintenance work order.

[0049] In response to the query button being clicked, a query request is triggered and sent to the business database.

[0050] S104. In response to the operation, the following processing is performed for each maintenance work order: based on the fault type, the maintenance processing suggestion corresponding to the maintenance work order is determined; based on the maintenance processing suggestion, the work order number, the agricultural machinery parameter information and the repair personnel information, the first maintenance data corresponding to the work order number is generated and stored in the business database; the second maintenance data corresponding to the maintenance work order stored in the business database is retrieved and displayed to provide dispatching suggestions.

[0051] Here, the second maintenance data includes the first maintenance data and dispatch data.

[0052] In this step, the maintenance processing suggestions corresponding to the maintenance work order are determined in the following ways:

[0053] Query all data in the fault database with the same fault type as the maintenance work order;

[0054] For each piece of data, the target data having the same agricultural machinery model as that in the agricultural machinery parameter information is screened out through the agricultural machinery parameter information, and the maintenance processing suggestion corresponding to the target data is determined as the maintenance processing suggestion corresponding to the maintenance work order.

[0055] Here, the maintenance treatment recommendation includes replacing parts or repairing the agricultural machinery.

[0056] Among them, the fault types are accurately divided, and the corresponding maintenance and processing suggestions can be determined according to the different fault types. These maintenance and processing suggestions will be based on rich experience and professional knowledge, aiming to help service personnel locate problems more quickly and take corresponding measures to repair them. In this way, the troubleshooting process can be significantly shortened, and service efficiency can be improved, thereby bringing a better service experience to the reporting users.

[0057] Here, the dispatch data includes parts data and service data.

[0058] The part data is determined by:

[0059] receiving an operation executed on the fault handling interface for querying parts data corresponding to each maintenance work order;

[0060] In response to the operation, the following processing is performed for each maintenance work order: a connection is established with the business database, and according to the agricultural machinery model corresponding to the agricultural machinery parameter information, the sales records corresponding to the agricultural machinery model and the parts model information corresponding to the agricultural machinery model in the business database are screened; according to the faulty part number corresponding to the fault information, the target part model information that matches the faulty part number is determined; the agricultural machinery model and the target part model information are determined as the parts data of the maintenance work order, and stored together with the first maintenance data.

[0061] When repairing agricultural machinery, it is necessary to comprehensively consider the type of fault and the parts that are easily damaged, and use intelligent analysis to accurately determine the parts that need to be replaced, combined with detailed data such as the agricultural machinery's factory date, installation file, and parts breakpoints provided in the sequential work order. This can improve maintenance efficiency and ensure that the replaced parts are fully matched to the agricultural machinery model and fault condition, thereby avoiding unnecessary waste and losses.

[0062] Specifically, the service data is determined in the following way:

[0063] receiving an operation executed on the fault handling interface for querying service data corresponding to each maintenance work order;

[0064] In response to the operation, the following processing is performed for each maintenance work order: the repair location is identified based on the repair personnel information to obtain the service sites, service personnel and service vehicles around the repair location, and the service sites, service personnel and service vehicles are determined as the service data of the maintenance work order and stored together with the first maintenance data.

[0065] After receiving the target part model information and the repair location information of the maintenance work order, it intelligently analyzes and obtains detailed information of surrounding service stations, including the geographical location, service scope, service time, etc. of the service stations. At the same time, it also intelligently matches and recommends nearby service personnel and service vehicles based on the repair location to ensure rapid response and problem resolution.

[0066] In order to more efficiently meet the needs of maintenance work orders, it is necessary to determine the target part model information based on the maintenance work order, including the model, specifications, quantity and any special requirements of the target part, so as to query and accurately locate the nearest central warehouse with inventory, service provider warehouse and spare parts service vehicle warehouse from the business database.

[0067] This application can accurately match the model, specification and quantity of the target parts to ensure that the inventory found fully meets the needs. It will also take into account multiple factors, such as traffic conditions, warehouse distribution capabilities and service response time, to provide the best parts supply plan. In this way, it can significantly improve service efficiency, reduce waiting time for users reporting repairs, and effectively avoid user dissatisfaction and cost increases caused by parts shortages or delays.

[0068] Specifically, receiving an operation executed on the fault handling interface for querying a maintenance node corresponding to each maintenance work order;

[0069] In response to the operation, the following processing is performed for each maintenance work order: according to the work order number, the location of the service personnel and the location of the service vehicle are determined to determine the maintenance node of the maintenance work order.

[0070] Service personnel will report data at multiple key nodes during the service process. These nodes include the time when the user reports the problem, the time when the service personnel confirms receipt of the task, the time of departure for the user's site, the actual time of arrival at the user's site, and the time when the service is completed. By recording these time nodes in real time, the overall process of the service can be clearly understood.

[0071] This application compares the actual progress of the service with the estimated arrival and completion time in advance, and calculates the deviation of the service progress. This deviation analysis helps us to promptly identify possible problems in the service process and take appropriate measures to make adjustments.

[0072] Establish a fault handling tracking mechanism to monitor and record the processing of each work order in real time. Keep abreast of the progress of fault handling and provide valuable data support for subsequent fault analysis and prevention.

[0073] In an optional embodiment, if the service progress lags behind, additional service personnel can be dispatched or the work plan can be adjusted in time to ensure that the service can be completed on time. Through data reporting and progress deviation analysis, the service process can be more accurately grasped to improve service efficiency and quality.

[0074] Specifically, for each maintenance work order, the customer service personnel in the repair area will conduct a preliminary assessment of the repair problem in the maintenance work order to understand the nature of the fault and possible solutions, and will communicate in detail with the user who reported the problem to understand the user's actual needs and expectations for maintenance services. The management personnel will also comprehensively consider the progress of crop operations in the area to ensure that the maintenance service will not affect the operation of agricultural machinery, and pay close attention to meteorological conditions, especially for weather changes that may affect maintenance work, and prepare countermeasures in advance. In terms of personnel allocation, the management personnel will reasonably allocate service personnel according to the complexity of the actual maintenance tasks and the required skill level to ensure that the maintenance work can be carried out efficiently and orderly. Taking all the above factors into consideration, the service management personnel will designate service personnel with corresponding skills and experience to go to the site for maintenance services.

[0075] This dispatching method not only improves service response speed and efficiency, but also ensures the stability of service quality and the improvement of customer satisfaction. It also makes the management of service resources more efficient and flexible, and can dynamically adjust personnel configuration and task allocation according to actual conditions.

[0076] Based on the extracted detailed information, including customer needs, service type, urgency, etc., combined with the real-time status of all current service personnel, such as real-time location (tracked by GPS), distance to the service target location, current service progress (completed tasks and remaining workload), skills and expertise, and customer evaluations, algorithms and machine learning technology are used to comprehensively evaluate and compare different dispatch strategies.

[0077] These strategies include nearest priority based on geographic location, optimal selection based on skill matching, load balancing based on service efficiency, etc. Through intelligent analysis and comparison, this application can quickly and accurately identify the service personnel who are most suitable to execute the current work order.

[0078] After the service personnel complete the maintenance on site, they complete the work order, archive the maintenance work order information, and store it in the fault database to provide reference for subsequent services.

[0079] Specifically, the business database is constructed in the following ways:

[0080] Receive all data for the first time and store it in the business database;

[0081] Set a preset storage time. In addition to receiving the full data for the first time, use the preset storage time as the time interval to receive incremental data, and store the incremental data in the business database to query the dispatch data.

[0082] Incremental data is data added after receiving the full data for storage in the business database.

[0083] According to the information of the maintenance work order, relevant data is obtained from various business subsystems in a synchronous / asynchronous manner, pre-processed in the dimensions of time and space, and multi-source data is integrated to support the development of service dispatch business.

[0084] In an optional embodiment, the business database obtains stored data from the following business subsystems:

[0085] IOV system (Internet of Vehicle): obtains agricultural machinery factory data, sales data, operation trajectory, real-time positioning, operation conditions, fault alarms, and cross-regional data;

[0086] CC system (Customer Care System, Customer Service Center System): obtains historical repair data of users, historical repair data of agricultural machinery, and historical repair data of agricultural machinery models;

[0087] CRM system (Customer Relationship Management System): obtain service personnel data, personnel location data, service vehicle location data, dealer data, and service station data;

[0088] SES system (Service Engine System, service engineering support system): obtains primary assembly data and component data;

[0089] MES system (Manufacturing Execution System): obtain agricultural machinery installation files;

[0090] WMS system (Warehouse Management System): obtains spare parts storage data;

[0091] Third-party system: obtain meteorological data, satellite remote sensing data, etc.

[0092] Specifically, after receiving the above data, the following processing is performed:

[0093] Data preprocessing: Obtain data through active pulling or passive receiving and perform data standardization and formatting;

[0094] Data cleaning: Before data is stored in the database, the data quality and abnormal information are identified and cleaned;

[0095] Data event-driven dissemination: After data is stored in the database, it provides information query channels, and the data is disseminated by external application events;

[0096] Data business integration: The business module obtains the required specific data around a work order through the information query interface and performs business integration.

[0097] In an optional embodiment, if the business subsystem provides an interface, and after calling the interface, the data obtained from the business subsystem is stored in the business database, it is considered to be active pulling; if the business database provides an interface, and the business subsystem stores the obtained data in the business database by calling the interface, it is considered to be passive reception.

[0098] Here, data standardization and formatting are to verify whether the data is complete and to complete some basic data. If the agricultural machinery number does not exist in the sales record, it will not be processed; if the maintenance work order is sent to other suppliers, it will not be processed either.

[0099] Data cleaning is to filter out unclear data. External application events are maintenance work orders composed of data provided by calling the 400 customer service phone number. Business integration is to query data from multiple business subsystems in the business database from the fault handling interface.

[0100] Based on the information obtained intelligently, detailed dispatch suggestions are further generated, including recommended service sites, service personnel, service vehicles, estimated arrival time and service process, etc. These dispatch suggestions will be used as a reference for service managers in the area to make decisions and dispatch orders.

[0101] The fault data processing method and fault data processing platform provided in the embodiment of the present application import a maintenance work order into the fault processing interface; identify the maintenance work order, determine the fault information of the maintenance work order, and determine the fault type corresponding to the maintenance work order based on the fault information; receive an operation executed on the fault processing interface to query the dispatch information corresponding to each maintenance work order; in response to the operation, perform the following processing for each maintenance work order: determine the maintenance processing suggestion corresponding to the maintenance work order based on the fault type, generate the first maintenance data corresponding to the work order number based on the maintenance processing suggestion, the work order number, the agricultural machinery parameter information and the repair personnel information, store it in the business database, retrieve and display the second maintenance data corresponding to the maintenance work order stored in the business database to provide dispatch suggestions, the second maintenance data includes the first maintenance data and the dispatch data. Through this application, the processing efficiency of maintenance work orders is improved, the data barriers between business systems are broken, the data island phenomenon is eliminated, and the data can give full play to its value.

[0102] This application integrates the original data of multiple independent business systems, conducts in-depth analysis and modeling, and builds a unified set of service dispatch rules. This rule not only simplifies the business process, but also greatly reduces the complexity of statistical data for staff and improves the accuracy of data results.

[0103] In addition, this application also focuses on directly and effectively displaying the analysis results to the staff. Through the intuitive display of results, they can quickly understand the overall situation of the current agricultural machinery services, and thus make more accurate and efficient decision-making. This processing method not only improves work efficiency, but also reduces the possibility of human errors, and provides a strong guarantee for the smooth progress of agricultural machinery services and agricultural machinery operations.

[0104] This application uses a series of efficient data processing processes to deeply mine and integrate the scattered data originally scattered in multiple independent business systems, and uses advanced extraction, analysis, and processing technologies to transform these data into structured data that is easy to understand, has a clear structure, and can directly support service dispatch business processing. This transformation not only breaks down the data barriers between business systems and eliminates the phenomenon of data silos, but also enables data to fully realize its due value, providing strong data support for corporate decision-making and business operations.

[0105] In the specific implementation process of service dispatch, this application focuses on the spatiotemporal coordination and optimal allocation of resources. By abstracting various resources in reality (such as agricultural machinery, service vehicles, service personnel, service stations, and parts warehouses, etc.), it is possible to obtain accurate positioning information of these resources in real time. At the same time, it also uses big data analysis technology to deeply mine the historical fault information of various agricultural machinery, analyze the fault type, summarize the fault cause, and realize the rapid diagnosis and accurate positioning of agricultural machinery faults.

[0106] Based on these rich data resources, this application can guide service personnel in real time to carry out agricultural machinery maintenance services. By comprehensively analyzing resource spatiotemporal data, it can develop the best service plan to ensure that service personnel can respond quickly to customer needs and complete maintenance tasks efficiently. In addition, it will promptly feedback maintenance progress information to the reporting user, so that the user can understand the progress of their reported repair work order in real time, thereby effectively alleviating the user's anxiety and improving the user's product experience. It breaks down the data barriers between business systems, eliminates the data island phenomenon, and enables data to fully realize its due value, providing strong data support for the company's decision-making and business operations.

[0107] Based on the same inventive concept, a fault data processing platform corresponding to the fault data processing method is also provided in the embodiment of the present application. Since the principle of solving the problem by the device in the embodiment of the present application is similar to the above-mentioned fault data processing method in the embodiment of the present application, the implementation of the device can refer to the implementation of the method, and the repeated parts will not be repeated.

[0108] See also Figure 2 , Figure 2 This is a schematic diagram of the structure of the fault data processing platform provided in the embodiment of the present application. Figure 2As shown in , the fault data processing platform 200 includes:

[0109] The import module 201 is used to import a maintenance work order in the fault handling interface, wherein the maintenance work order includes a work order number, fault information, agricultural machinery parameter information, and repair personnel information;

[0110] A fault type determination module 202 is used to identify the maintenance work order, determine the fault information of the maintenance work order, and determine the fault type corresponding to the maintenance work order according to the fault information;

[0111] A receiving module 203, configured to receive an operation performed on the fault handling interface for querying dispatch information corresponding to each maintenance work order;

[0112] The second maintenance data module 204 is displayed, and is used to respond to the operation and perform the following processing for each maintenance work order: determine the maintenance processing suggestion corresponding to the maintenance work order according to the fault type, generate the first maintenance data corresponding to the work order number according to the maintenance processing suggestion, the work order number, the agricultural machinery parameter information and the repair personnel information, store it in the business database, retrieve and display the second maintenance data corresponding to the maintenance work order stored in the business database to provide dispatching suggestions, and the second maintenance data includes the first maintenance data and dispatching data.

[0113] See also Figure 3 , Figure 3 This is a schematic diagram of the structure of the electronic device provided in the embodiment of the present application. Figure 3 As shown in , the electronic device 300 includes a processor 310 , a memory 320 and a bus 330 .

[0114] The memory 320 stores machine-readable instructions executable by the processor 310. When the electronic device 300 is running, the processor 310 communicates with the memory 320 via the bus 330. When the machine-readable instructions are executed by the processor 310, the above-mentioned Figure 1 The steps of the fault data processing method in the method embodiment shown and the specific implementation methods can be found in the method embodiment, which will not be described in detail here.

[0115] The present application also provides a computer-readable storage medium on which a computer program is stored. When the computer program is executed by a processor, the computer program can execute the above-mentioned Figure 1 The steps of the fault data processing method in the method embodiment shown and the specific implementation methods can be found in the method embodiment, which will not be described in detail here.

[0116] Those skilled in the art can clearly understand that, for the convenience and brevity of description, the specific working processes of the systems, devices and units described above can refer to the corresponding processes in the aforementioned method embodiments and will not be repeated here.

[0117] In the several embodiments provided in the present application, it should be understood that the disclosed systems, devices and methods can be implemented in other ways. The device embodiments described above are merely schematic. For example, the division of the units is only a logical function division. There may be other division methods in actual implementation. For example, multiple units or components can be combined or integrated into another system, or some features can be ignored or not executed. Another point is that the mutual coupling or direct coupling or communication connection shown or discussed can be through some communication interfaces, and the indirect coupling or communication connection of devices or units can be electrical, mechanical or other forms.

[0118] The units described as separate components may or may not be physically separated, and the components shown as units may or may not be physical units, that is, they may be located in one place or distributed on multiple network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

[0119] In addition, each functional unit in each embodiment of the present application may be integrated into one processing unit, or each unit may exist physically separately, or two or more units may be integrated into one unit.

[0120] If the functions are implemented in the form of software functional units and sold or used as independent products, they can be stored in a non-volatile computer-readable storage medium that is executable by a processor. Based on this understanding, the technical solution of the present application can essentially be embodied in the form of a software product, or in other words, the part that contributes to the prior art or the part of the technical solution. The computer software product is stored in a storage medium, including several instructions for a computer device (which can be a personal computer, a server, or a network device, etc.) to perform all or part of the steps of the method described in each embodiment of the present application. The aforementioned storage medium includes: various media that can store program codes, such as a USB flash drive, a mobile hard disk, a read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0121] Finally, it should be noted that the above-described embodiments are only specific implementation methods of the present application, which are used to illustrate the technical solutions of the present application, rather than to limit them. The protection scope of the present application is not limited thereto. Although the present application is described in detail with reference to the above-mentioned embodiments, ordinary technicians in the field should understand that any technician familiar with the technical field can still modify the technical solutions recorded in the above-mentioned embodiments within the technical scope disclosed in the present application, or can easily think of changes, or make equivalent replacements for some of the technical features therein; and these modifications, changes or replacements do not make the essence of the corresponding technical solutions deviate from the spirit and scope of the technical solutions of the embodiments of the present application, and should be included in the protection scope of the present application. Therefore, the protection scope of the present application shall be based on the protection scope of the claims.

Claims

1. A method for processing fault data, characterized in that: include: Importing a maintenance work order in the fault handling interface, wherein the maintenance work order includes a work order number, fault information, agricultural machinery parameter information, and repair personnel information; Identify the maintenance work order, determine fault information of the maintenance work order, and determine the fault type corresponding to the maintenance work order according to the fault information; Receiving an operation performed on the fault handling interface for querying dispatch information corresponding to each maintenance work order; In response to the operation, the following processing is performed for each maintenance work order: based on the fault type, a maintenance processing suggestion corresponding to the maintenance work order is determined; based on the maintenance processing suggestion, the work order number, the agricultural machinery parameter information and the repair personnel information, first maintenance data corresponding to the work order number is generated and stored in a business database; second maintenance data corresponding to the maintenance work order stored in the business database is retrieved and displayed to provide dispatching suggestions, wherein the second maintenance data includes first maintenance data and dispatching data.

2. The method according to claim 1, characterized in that Determine the fault type corresponding to the maintenance work order in the following way: Read the fault information, classify the fault information using a predefined fault level determination rule, and determine the fault level of the maintenance work order; According to the fault information and the fault level, the historical work order fault type data stored in the fault database is queried to determine the fault type corresponding to the maintenance work order.

3. The method according to claim 2, characterized in that Determine the maintenance processing suggestion corresponding to the maintenance work order in the following way: Querying all data in the fault database having the same fault type as that corresponding to the maintenance work order; For each piece of data, the target data with the same agricultural machinery model as the agricultural machinery parameter information is filtered out through the agricultural machinery parameter information, and the maintenance processing suggestion corresponding to the target data is determined as the maintenance processing suggestion corresponding to the maintenance work order, and the maintenance processing suggestion includes replacing parts or repairing the agricultural machinery.

4. The method according to claim 1, characterized in that: The dispatch data includes parts data and service data. The part data is determined in the following manner: receiving an operation performed on the fault handling interface for querying parts data corresponding to each maintenance work order; In response to the operation, the following processing is performed for each maintenance work order: a connection is established with the business database, and according to the agricultural machinery model corresponding to the agricultural machinery parameter information, the sales records corresponding to the agricultural machinery model and the part model information corresponding to the agricultural machinery model in the business database are screened; according to the fault part number corresponding to the fault information, the target part model information matching the fault part number is determined; the agricultural machinery model and the target part model information are determined as the parts data of the maintenance work order, and stored together with the first maintenance data.

5. The method according to claim 4, characterized in that The service data is determined by: receiving an operation performed on the fault handling interface for querying service data corresponding to each maintenance work order; In response to the operation, the following processing is performed for each maintenance work order: based on the information of the repair person, the repair location is identified to obtain the service site, service personnel and service vehicle around the repair location, and the service site, service personnel and service vehicle are determined as the service data of the maintenance work order, and stored together with the first maintenance data.

6. The method according to claim 5, characterized in that The method further comprises: Receiving an operation performed on the fault handling interface for querying a maintenance node corresponding to each maintenance work order; In response to the operation, the following processing is performed for each maintenance work order: according to the work order number, the location of the service personnel and the location of the service vehicle are determined to determine the maintenance node of the maintenance work order.

7. The method according to claim 1, characterized in that The business database is constructed in the following manner: Receiving full data for the first time, and storing the full data in the business database; A preset storage time is set. Except for the first time receiving the full data, the preset storage time is used as the time interval to receive incremental data, and the incremental data is stored in the business database to query the dispatch data. The incremental data is the data added after receiving the full data for storage in the business database.

8. A fault data processing platform, characterized in that: include: An import module is used to import a maintenance work order in the fault handling interface, wherein the maintenance work order includes a work order number, fault information, agricultural machinery parameter information, and repair personnel information; A fault type determination module, used to identify the maintenance work order, determine the fault information of the maintenance work order, and determine the fault type corresponding to the maintenance work order according to the fault information; A receiving module, used for receiving an operation performed on the fault handling interface for querying dispatch information corresponding to each maintenance work order; A second maintenance data module is displayed, which is used to respond to the operation and perform the following processing for each maintenance work order: according to the fault type, a maintenance processing suggestion corresponding to the maintenance work order is determined; according to the maintenance processing suggestion, the work order number, the agricultural machinery parameter information and the repair personnel information, first maintenance data corresponding to the work order number is generated and stored in a business database; second maintenance data corresponding to the maintenance work order stored in the business database is retrieved and displayed to provide dispatching suggestions, wherein the second maintenance data includes first maintenance data and dispatching data.

9. An electronic device, characterized in that: include: A processor, a memory and a bus, wherein the memory stores machine-readable instructions executable by the processor, and when the electronic device is running, the processor and the memory communicate via the bus, and the processor executes the machine-readable instructions to perform the steps of any method as claimed in claims 1 to 7.

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

Images