A method and system for remote fault diagnosis and spare parts prediction of diesel generator sets

By generating fault analysis records, matching standard maintenance plans, calculating inventory quantities, and generating allocation requests, the problem of connecting fault diagnosis results with spare parts requirements and inventory status with maintenance task orders in remote fault diagnosis of diesel generator sets has been solved, realizing efficient remote fault diagnosis and spare parts preparation for diesel generator sets.

CN123118065APending Publication Date: 2026-11-17BEIJING BOHUA HENGYI CULTURE TECHNOLOGY CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202611285097.4
Authority / Receiving Office
CN · China
Patent Type
Applications(China)
Current Assignee / Owner
Filing Date
2026-08-24
Publication Date
2026-11-17

AI Technical Summary

Technical Problem

During the remote fault diagnosis and spare parts preparation process of diesel generator sets, there is a lack of structured correlation between fault diagnosis results and spare parts requirements, discontinuous connection between inventory status and current maintenance tasks, and insufficient linkage between missing parts handling and maintenance priority, resulting in inconsistent material code matching, delayed judgment of missing parts status, and incomplete maintenance task record recording.

Method used

By receiving fault information and equipment identification from diesel generator sets, a fault analysis record is generated. The fault knowledge base is called to match standard maintenance solutions, a spare parts requirement record is generated, and the available inventory quantity is calculated by combining local and collaborative warehouse inventory snapshot records. Inventory satisfaction status and missing parts status records are generated, replenishment prediction results are generated based on historical consumption data, and transfer request records are formed. Finally, a maintenance task order record is generated.

Benefits of technology

It achieves a structured association between fault information and spare parts demand, a continuous connection between inventory status and maintenance tasks, and a linkage between missing parts handling and maintenance priority, ensuring consistent material code matching, timely handling of missing parts status, and generating a complete maintenance task sheet.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN123118065A_ABST
    Figure CN123118065A_ABST
Patent Text Reader

Abstract

This invention relates to the field of remote operation and maintenance data processing technology for diesel generator sets, and particularly to a method and system for remote fault diagnosis and spare parts prediction of diesel generator sets. The method includes: receiving fault information, equipment identification, and maintenance priority; reading equipment files and mapping standard fault entities to generate fault analysis records; calling a fault knowledge base to match standard maintenance plans according to generator model compatibility, generating spare parts demand records; querying inventory snapshot records of local warehouses, branch warehouses, and collaborative warehouses based on spare parts demand records, calculating available inventory quantities, and generating shortage status records; generating replenishment prediction results or allocation request records based on shortage status records, forming spare parts supply plan records; binding the records to generate maintenance task order records and pushing them to the maintenance terminal. This invention integrates fault analysis, spare parts demand, inventory status, and shortage handling within the same maintenance task, improving the consistency of spare parts supply status records.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] This invention relates to the field of remote operation and maintenance and repair management data processing technology for diesel generator sets, and in particular to a method and system for remote fault diagnosis and spare parts prediction of diesel generator sets. Background Technology

[0002] In the field of remote operation and maintenance management data processing technology for diesel generator sets, existing solutions typically diagnose faults using unit operating parameters, fault codes, fault phenomenon descriptions, or sensor data, outputting fault types, faulty components, health indices, early warning information, or fault prevention strategies. Spare parts inventory is usually maintained independently by an inventory management system, including material codes, inventory quantities, warehouse locations, reserved quantities, and inbound / outbound records. Maintenance task orders are typically generated by a work order system based on repair requests, work assignments, and maintenance steps. While these solutions can handle basic processing such as fault identification, inventory recording, and task assignment in routine maintenance scenarios, they are prone to limitations in scenarios where remote fault diagnosis and spare parts preparation need to be synchronized. These limitations include a lack of structured correlation between fault diagnosis results and spare parts requirements, discontinuous connections between inventory status and current maintenance tasks, and insufficient linkage between missing parts handling and maintenance priorities.

[0003] Existing solutions largely rely on manual experience, fixed fault code tables, independent inventory ledgers, or on-site confirmation by maintenance personnel. When the sources of fault information for diesel generator sets are inconsistent, there are differences in the compatible models in the equipment files, spare parts inventory versions change, or maintenance priorities change, there is a lack of stable connection between the fault diagnosis, spare parts demand generation, inventory status query, and maintenance task order generation processes. This can easily lead to inconsistent material code matching, delayed determination of missing parts status, and incomplete spare parts supply status in the maintenance task order records.

[0004] For the joint processing of remote fault diagnosis, spare parts requirements, inventory snapshot records, missing parts status records, and maintenance task order records for diesel generator sets, existing technologies still have common shortcomings in cross-system record synchronization, generator model adaptation and matching, inventory status determination, and the connection of missing parts processing records. Therefore, it is necessary to address the problem of disconnect between fault information, spare parts requirements, inventory status, and maintenance task order records in the context of remote fault diagnosis of diesel generator sets. Summary of the Invention

[0005] To address the aforementioned technical problems, this invention provides a method for remote fault diagnosis and spare parts prediction of diesel generator sets, comprising:

[0006] S100: Receive fault information, equipment identification and maintenance priority of diesel generator set; read equipment file based on equipment identification; map fault information to standard fault entities; and generate fault analysis record.

[0007] S200. Based on the fault analysis record and the equipment file, call the fault knowledge base, match the standard maintenance plan according to the model compatibility relationship, and generate a spare parts requirement record containing material code, required quantity and compatible model.

[0008] S300: Based on the spare parts demand record, query the inventory snapshot records of the local warehouse, sub-warehouse and cooperative warehouse, calculate the available inventory quantity according to the existing quantity, locked quantity and reserved quantity, and generate inventory satisfaction status and shortage status records.

[0009] S400: Generate replenishment prediction results based on the missing parts status record and historical spare parts consumption data; when the maintenance priority meets the emergency allocation conditions, generate an allocation request record based on the available inventory quantity of the cooperative warehouse and the estimated arrival time, and generate a spare parts supply plan record.

[0010] S500: Bind the fault analysis record, the standard maintenance plan, the spare parts requirement record, the missing parts status record, and the spare parts supply plan record to generate a maintenance task order record and push it to the maintenance terminal.

[0011] Furthermore, the fault information includes fault codes or descriptions of fault phenomena;

[0012] When the fault information includes a fault code, the fault code is mapped to a standard fault entity according to the mapping rule version;

[0013] When the fault information includes a description of the fault phenomenon, the fault phenomenon description is segmented into words, identified as an entity, and normalized with synonyms to generate a standard fault entity.

[0014] Furthermore, the fault knowledge base includes standard fault entities, fault causes, standard repair solutions, repair procedures, spare parts materials, model compatibility relationships, and alternative parts relationships;

[0015] When matching a standard repair plan according to the model compatibility relationship, a repair plan record is generated using the standard fault entity in the fault analysis record and the compatible model in the equipment file as query conditions.

[0016] Furthermore, the spare parts requirement record also includes mandatory identifiers, optional identifiers, alternative identifiers, requirement sourcing options, and requirement confidence levels;

[0017] When generating the spare parts requirement record, the spare parts materials in the standard maintenance plan are matched with the spare parts mapping rules, and the material codes are filtered according to the model compatibility relationship.

[0018] Furthermore, the inventory snapshot record includes warehouse identifier, inventory version, current quantity, locked quantity, reserved quantity, quantity in transit, and status validity period;

[0019] The available inventory quantity is obtained by subtracting the locked quantity and reserved quantity from the existing quantity, and then adding it to the quantity in transit that is within the validity period of the status.

[0020] Furthermore, before generating the maintenance task record, the inventory version of the inventory snapshot record is verified;

[0021] When the inventory version changes, the available inventory quantity is recalculated, and the inventory fulfillment status and the shortage status records are updated.

[0022] When the inventory snapshot record query is abnormal, the most recent valid inventory snapshot is read and an inventory satisfaction status to be confirmed is generated.

[0023] Furthermore, when generating the replenishment forecast result, the historical spare parts consumption data is read according to the material code, a moving average consumption is generated based on the historical consumption time window, and the expected replenishment date and recommended replenishment quantity are generated according to the moving average consumption, procurement lead time and safety stock.

[0024] Furthermore, the emergency allocation conditions consist of maintenance priority, the number of missing parts, the expected replenishment date, and the available inventory quantity in the cooperating warehouse;

[0025] The allocation request record includes the collaborative warehouse identifier, available quantity, estimated arrival time, allocation priority, and request status.

[0026] Furthermore, the maintenance task record includes the task status version, push status, and inventory binding version;

[0027] The system receives the actual spare parts consumption records written back from the maintenance terminal and updates the historical spare parts consumption data and mapping rule version based on the actual replaced spare parts, the actual quantity, and the quantity returned.

[0028] Furthermore, a remote fault diagnosis and spare parts prediction system for diesel generator sets includes: a fault information receiving module, a fault analysis module, a maintenance plan and spare parts demand generation module, an inventory status query module, a missing parts processing module, and a maintenance task order generation module; the system is used to implement the method described in any of the above-mentioned embodiments.

[0029] The key innovations of this invention include:

[0030] (1) Based on fault information, equipment identification and equipment file, a fault analysis record is formed, and the fault knowledge base is called with the standard fault entity in the fault analysis record and the model adaptation relationship in the equipment file to match the standard maintenance plan and generate a spare parts requirement record containing material code, required quantity and adapted model.

[0031] (2) Using the spare parts demand record as the input for inventory query, link the inventory snapshot records of local warehouse, sub-warehouse and cooperative warehouse, calculate the available inventory quantity based on the existing quantity, locked quantity and reserved quantity, and form inventory satisfaction status and shortage status records.

[0032] (3) Using the missing parts status record as the input for missing parts processing, and combining it with historical spare parts consumption data to generate replenishment prediction results, and when the maintenance priority meets the emergency transfer conditions, combining the available inventory quantity of the cooperative warehouse and the expected arrival time to generate a transfer request record, thereby forming a spare parts supply plan record and binding it to generate a maintenance task order record.

[0033] The following are its main beneficial effects:

[0034] (1) To address the lack of structured association between fault diagnosis results and spare parts requirements, continuous matching between fault analysis records, equipment files, machine model compatibility relationships and standard maintenance plans is used to generate spare parts requirement records that include material codes, required quantities and compatible machine models.

[0035] (2) To address the issue of discontinuity between inventory status and current maintenance tasks, multiple warehouses' inventory snapshot records are queried through spare parts demand records. The available inventory quantity is calculated based on the existing quantity, locked quantity, and reserved quantity, so that the inventory satisfaction status and spare parts shortage status records are kept on the same record link as the current spare parts demand.

[0036] (3) To address the problem of insufficient linkage between missing parts handling and maintenance priority, the combined processing of missing parts status records, historical spare parts consumption data, maintenance priority and collaborative warehouse inventory status enables replenishment forecast results, transfer request records and spare parts supply plan records to be entered into the same maintenance task record. Attached Figure Description

[0037] Figure 1 A flowchart illustrating a remote fault diagnosis and spare parts prediction method for a diesel generator set provided in this application embodiment;

[0038] Figure 2 This is a structural block diagram of a remote fault diagnosis and spare parts prediction system for diesel generator sets provided in an embodiment of this application. Detailed Implementation

[0039] Example 1: Refer to Figure 1This is a flowchart illustrating a remote fault diagnosis and spare parts prediction method for diesel generator sets provided in an embodiment of the present invention. The process may include at least steps S100-S500:

[0040] S100: Receive fault information, equipment identification and maintenance priority of diesel generator set; read equipment file based on equipment identification; map fault information to standard fault entities; and generate fault analysis record.

[0041] S200. Based on the fault analysis record and the equipment file, call the fault knowledge base, match the standard maintenance plan according to the model compatibility relationship, and generate a spare parts requirement record containing material code, required quantity and compatible model.

[0042] S300: Based on the spare parts demand record, query the inventory snapshot records of the local warehouse, sub-warehouse and cooperative warehouse, calculate the available inventory quantity according to the existing quantity, locked quantity and reserved quantity, and generate inventory satisfaction status and shortage status records.

[0043] S400: Generate replenishment prediction results based on the missing parts status record and historical spare parts consumption data; when the maintenance priority meets the emergency allocation conditions, generate an allocation request record based on the available inventory quantity of the cooperative warehouse and the estimated arrival time, and generate a spare parts supply plan record.

[0044] S500: Bind the fault analysis record, the standard maintenance plan, the spare parts requirement record, the missing parts status record, and the spare parts supply plan record to generate a maintenance task order record and push it to the maintenance terminal.

[0045] S100: Receive fault information, equipment identification, and maintenance priority of the diesel generator set; read the equipment file based on the equipment identification; map the fault information to a standard fault entity; and generate a fault analysis record.

[0046] This step is executed by the fault information receiving module and the fault analysis module. The fault information receiving module is located in the diesel generator set remote operation and maintenance platform and communicates with the generator set controller, the remote monitoring platform, and the maintenance terminal. The fault analysis module is connected to the equipment file database, the fault code mapping table, and the terminology mapping record. The fault information includes fault codes or fault phenomenon descriptions; the equipment identifier is a unique record identifier for the diesel generator set in the remote operation and maintenance platform; the maintenance priority is a status field used when a maintenance task enters subsequent missing parts processing, and its value can be written by the source of the repair request, the generator set service level, the fault shutdown status, and the result of manual selection.

[0047] Specifically, when the unit-side controller reports a fault code, the fault information receiving module binds the fault code, reporting time, fault source, and equipment identifier to form an original fault reception record. When maintenance personnel input a fault phenomenon description through a maintenance terminal, the fault information receiving module binds the fault phenomenon description, input time, input terminal identifier, and equipment identifier to form an original fault reception record. The fault phenomenon description can be a textual description such as "start-up failure," "high water temperature alarm," "low oil pressure," or "unstable generator voltage." The fault code can be an alarm code, shutdown code, or protection code output by the unit controller. The original fault reception record retains the original fields and does not overwrite the original fault code or original text content.

[0048] After receiving the original fault reception record, the fault analysis module reads the equipment file based on the equipment identifier. The equipment file includes fields for unit model, engine model, generator model, controller model, factory configuration, service area, compatible model, and equipment status. The compatible model in the equipment file is used as an input field in S200 for standard maintenance scheme matching and spare parts requirement record generation; the equipment status field is saved as an additional field in this step of the fault analysis record. If the same equipment identifier corresponds to multiple historical file versions, the fault analysis module reads the equipment file currently in effect according to the equipment file version number and file effective time, and writes the equipment file version number into the fault analysis record.

[0049] When the fault information includes a fault code, the fault parsing module reads the fault code mapping table according to the mapping rule version and matches the fault code with the standard fault entities in the fault code mapping table. The mapping rule version is the version identifier of the mapping relationship between the fault code and the standard fault entity; the standard fault entity is a record field within the remote operation and maintenance platform that uniformly represents a fault object, and its content may include system startup fault entities, lubrication system pressure abnormal entities, cooling system temperature abnormal entities, generator voltage abnormal entities, and controller communication abnormal entities. When multiple matching items exist for a fault code, the fault parsing module uses the controller model and unit model in the equipment file as filter fields, selects the standard fault entity that matches the controller model and unit model, and writes the unselected matching items into the candidate parsing field.

[0050] When the fault information includes a description of the fault phenomenon, the fault parsing module performs word segmentation, entity recognition, and synonym normalization on the fault phenomenon description to generate standard fault entities. Word segmentation breaks down the fault phenomenon description into fault object words, action words, and state words; entity recognition maps fault object words to standard objects such as the starting system, cooling system, lubrication system, power generation output system, or control system; synonym normalization normalizes "cannot start," "cannot start," and "cannot start" into a starting failure description, and "high water temperature," "high temperature shutdown," and "high coolant temperature" into a cooling system temperature anomaly description. Word segmentation, entity recognition, and synonym normalization are all performed based on pre-maintained term mapping records, which contain mapping rule versions, and these versions are saved with the fault parsing records.

[0051] In one implementation, after generating a standard fault entity, the fault analysis module performs a consistency match between the standard fault entity and the compatible models in the device file. If the fault object corresponding to the standard fault entity does not belong to the configuration range recorded in the device file—for example, the device file does not configure the corresponding controller model or the corresponding sensor type—the fault analysis module marks the analysis status as pending review and retains the original fault information, candidate standard fault entities, and device file version. If the standard fault entity matches the compatible model in the device file, the fault analysis module marks the analysis status as resolved and generates a fault analysis record.

[0052] The fault analysis record includes equipment identifier, equipment file version, fault information, fault source, standard fault entity, mapping rule version, maintenance priority, and analysis status. The fault source distinguishes between reports from the unit-side controller, imports from the remote monitoring platform, and inputs from the maintenance terminal. The analysis status includes analyzed, pending review, and no match. If the fault code has no matching entry in the fault code mapping table, or if the fault phenomenon description cannot form a standard fault entity in the terminology mapping record, the fault analysis module generates a fault analysis record with no match and pushes the original fault information to the maintenance terminal for manual review. After the manual review result is written back, the fault analysis module updates the fault analysis record with the written-back standard fault entity and retains the original no-match status as a historical analysis status.

[0053] In one implementation scenario, the unit-side controller reports a low oil pressure fault code. The fault information receiving module receives the fault code, equipment identifier, and maintenance priority. The fault parsing module reads the equipment file corresponding to the equipment identifier to obtain the engine model and controller model. Subsequently, according to the mapping rule version, it maps the fault code to a lubrication system pressure abnormality entity in the fault code mapping table and generates a fault parsing record containing the equipment identifier, standard fault entity, fault source, and parsing status. The standard fault entity, equipment file version, and maintenance priority in this fault parsing record serve as inputs for matching the S200 standard maintenance plan.

[0054] S200. Based on the fault analysis record and the equipment file, call the fault knowledge base, match the standard maintenance plan according to the model compatibility relationship, and generate a spare parts requirement record containing material code, required quantity and compatible model.

[0055] This step is executed by the maintenance plan matching module and the spare parts requirement generation module. The maintenance plan matching module receives the fault analysis record generated by S100 and reads the standard fault entity, equipment identifier, equipment file version, and analysis status recorded in the fault analysis record. The spare parts requirement generation module receives the standard maintenance plan output by the maintenance plan matching module and calls the spare parts mapping rules to generate a spare parts requirement record. The fault knowledge base includes standard fault entities, fault causes, standard maintenance plans, maintenance steps, spare parts materials, model compatibility relationships, and replacement part relationships. The model compatibility relationship represents the compatibility records between the unit model, engine model, controller model, and the standard maintenance plan and spare parts materials.

[0056] Upon receiving a fault analysis record, the maintenance plan matching module first reads the analysis status of the record. If the analysis status is "analyzed," the module retrieves the fault knowledge base using the standard fault entity and the compatible model from the equipment file as query conditions. If the analysis status is "pending review" or "no match," the module writes the fault analysis record to the pending review queue, writes back the standard fault entity on the maintenance terminal, and then retrieves the fault knowledge base. The compatible models in the equipment file include the generator set model, engine model, generator model, and controller model. When matching standard maintenance plans, the module matches in the order of standard fault entity, compatible model, and plan version.

[0057] The standard maintenance plan is a maintenance plan data object recorded in the fault knowledge base. Its content includes the fault cause, maintenance steps, compatible models, spare parts, maintenance plan identifier, and plan version. The maintenance steps may include inspection items, disassembly / reassembly items, replacement items, and verification items. The spare parts describe the maintenance parts involved in the standard maintenance plan. The maintenance plan matching module matches the standard fault entities in the fault analysis record with the standard fault entity fields in the fault knowledge base, and compares the compatible models in the equipment file with the compatible model fields of the standard maintenance plan, generating a maintenance plan record. The maintenance plan record stores the standard maintenance plan, maintenance plan identifier, plan version, matching source, and matching status.

[0058] When the same standard fault entity corresponds to multiple standard repair solutions, the repair solution matching module filters the repair solutions according to the model compatibility relationship. If a standard repair solution exists that matches the engine model, controller model, and unit model in the equipment file, a repair solution record with a matching status of model matching is generated. If no completely matching standard repair solution exists, but a standard repair solution matches the engine model or controller model, a candidate repair solution record is generated, and the matching status is marked as candidate matching. If no corresponding standard repair solution exists, a repair solution record pending review is generated, retaining the standard fault entity, equipment file version, and reason for non-match. After confirmation at the repair terminal, the candidate repair solution record can enter the spare parts requirement generation module.

[0059] The spare parts requirement generation module generates spare parts requirement records based on standard maintenance plans and spare parts mapping rules in the maintenance plan record. The spare parts mapping rules include the correspondence between spare parts materials and material codes, the range of compatible models, substitute parts relationships, mandatory identifiers, optional identifiers, and requirement quantity rules. The spare parts requirement generation module reads spare parts materials from the standard maintenance plan, maps the spare parts materials to material codes according to the spare parts mapping rules, and filters the material codes according to model compatibility. If a spare parts material corresponds to multiple material codes, the spare parts requirement generation module uses the unit model, engine model, and controller model from the equipment file as filter fields to generate material codes consistent with the compatible models; if substitute parts relationships exist, the spare parts requirement generation module writes both the main material code and the substitute part identifier into the spare parts requirement record simultaneously.

[0060] The spare parts requirement record includes material code, required quantity, compatible model, mandatory identifier, optional identifier, replacement part identifier, requirement source scheme, and requirement confidence level. The required quantity can be generated from the fixed quantity field in the standard maintenance plan or from the configuration quantity field in the equipment file; for example, when multiple sensors of the same model are configured in the same unit, the required quantity can be generated based on the installed quantity of that sensor in the equipment file. The mandatory identifier indicates the spare parts that need to be prepared with the task when the maintenance plan is executed; the optional identifier indicates the spare parts used after the inspection results meet specific conditions; the requirement source scheme records which standard maintenance plan and version the spare parts requirement record originates from; the requirement confidence level is generated from the standard maintenance plan matching status, model compatibility consistency, and statistical fields of similar records in historical spare parts consumption data.

[0061] In one implementation, the spare parts demand generation module merges duplicate materials in the spare parts demand records. When multiple maintenance steps in the same maintenance plan reference the same material code, the spare parts demand generation module merges them according to the material code and the compatible model, accumulates the demand quantities, and retains the demand source plan for each maintenance step. In another implementation, the spare parts demand generation module extends the record of substitute parts relationships by writing the substitute part identifier, substitute material code, and substitute priority into the spare parts demand record; the substitute priority does not change the demand quantity of the main material code, but is used as an extended input for inventory query when querying the inventory snapshot record in S300.

[0062] In one implementation scenario, the fault analysis record generated by S100 records the standard fault entity as an abnormal pressure entity in the lubrication system, and the equipment file records the engine model as a specific diesel engine model. After the maintenance plan matching module calls the fault knowledge base, it matches a standard maintenance plan that is compatible with the engine model. The standard maintenance plan records the maintenance steps of checking the oil pressure sensor, checking the oil filter, and verifying the oil pressure signal. The spare parts requirement generation module reads the spare parts materials in the standard maintenance plan, generates the corresponding material codes for the oil pressure sensor and the oil filter, as well as their respective required quantities, according to the spare parts mapping rules, and forms a spare parts requirement record. The material codes, required quantities, and compatible engine models in the spare parts requirement record serve as input for S300 to query the inventory snapshot record.

[0063] S300: Based on the spare parts demand record, query the inventory snapshot records of the local warehouse, sub-warehouse and cooperative warehouse, calculate the available inventory quantity according to the existing quantity, locked quantity and reserved quantity, and generate inventory satisfaction status and shortage status records.

[0064] This step is executed by the inventory status query module. The inventory status query module receives spare parts requirement records generated by S200 and uses the material code, required quantity, compatible model, and substitute part identifier from these records as input for inventory queries. The inventory status query module connects to the inventory management interfaces of the local warehouse, sub-warehouses, and collaborative warehouses, and reads inventory snapshot records of the corresponding material codes in multiple warehouses. The local warehouse is the warehouse prioritized for use within the service area; the sub-warehouses are regional warehouses within the same operation and maintenance platform; and the collaborative warehouses are inventory nodes pre-registered within the warehouse service area.

[0065] The inventory snapshot record includes a warehouse identifier, inventory version, current quantity, locked quantity, reserved quantity, quantity in transit, and status validity period. The warehouse identifier indicates the warehouse where the inventory record is located; the inventory version indicates the version number of the inventory snapshot record; the current quantity indicates the currently available book inventory quantity in the warehouse; the locked quantity indicates the quantity occupied by other maintenance or outbound tasks; the reserved quantity indicates the quantity occupied by task orders that have been generated but not yet completed for outbound processing; the quantity in transit indicates the quantity that has been shipped or allocated but not yet stored; and the status validity period indicates the time range within which the inventory snapshot record can be referenced in subsequent calculations. After reading the inventory snapshot record, the inventory status query module writes the read time, inventory version, and warehouse identifier into the inventory availability record.

[0066] The available inventory quantity is obtained by subtracting the locked and reserved quantities from the existing quantity, and then adding it to the quantity in transit that is within the validity period of the status. Specifically, the inventory status query module reads inventory snapshot records from multiple warehouses for each material code and calculates the available inventory quantity corresponding to that material code under the same warehouse identifier. If the estimated arrival time of the quantity in transit is within the validity period of the status, the quantity in transit is included in the available inventory quantity; if the estimated arrival time is not within the validity period of the status, the quantity in transit is written to the "not included in transit" field in the inventory availability record. The inventory availability record is stored using the material code and warehouse identifier as an index for reference when generating inventory satisfaction status and shortage status records later.

[0067] The inventory fulfillment status is generated by the inventory status query module based on the available inventory quantity and the required quantity. If the available inventory quantity in the local warehouse is greater than or equal to the required quantity, the inventory fulfillment status is marked as "local fulfillment," and the local warehouse identifier, material code, required quantity, and available inventory quantity are recorded. If the available inventory quantity in the local warehouse is less than the required quantity, but the total available inventory quantity in the local warehouse and the branch warehouse is greater than or equal to the required quantity, the inventory fulfillment status is marked as "branch warehouse replenishment," and the quantity allocated to each warehouse is recorded. If neither the local warehouse nor the branch warehouse can meet the required quantity, but the cooperating warehouse has available inventory, the inventory fulfillment status is marked as "cooperating warehouse available for allocation," and the cooperating warehouse identifier and available allocation quantity are recorded. If the total available inventory quantity in multiple warehouses is less than the required quantity, a shortage status record is generated.

[0068] The spare parts shortage status record includes material code, required quantity, available quantity, missing quantity, warehouse query range, inventory version, and status generation time. The missing quantity is obtained by subtracting the available quantity from the required quantity; the available quantity is generated by summing the available inventory quantities of the local warehouse, sub-warehouses, and collaborative warehouses in a callable state. If the spare parts requirement record contains a substitute part identifier, the inventory status query module synchronously queries the inventory snapshot record of the substitute material code and writes the inventory availability status of the substitute material code into the substitute part field of the spare parts shortage status record. The substitute part field is saved as a callable field when the S400 generates the spare parts supply plan record.

[0069] In one implementation, the inventory status query module verifies the inventory version of the inventory snapshot record before generating the maintenance task order record. If the inventory version has not changed, the inventory status query module transmits the inventory availability status and shortage status records to S400; if the inventory version has changed, the inventory status query module rereads the inventory snapshot record for the corresponding material code, recalculates the available inventory quantity, and updates the inventory availability status and shortage status records. The inventory version change record stores the old inventory version, the new inventory version, the recalculation time, and the recalculation result. This inventory version change record is written into the subsequent spare parts supply plan record along with the shortage status record.

[0070] In another implementation, when an inventory snapshot record query for a local warehouse, sub-warehouse, or collaborative warehouse is abnormal, the inventory status query module reads the most recent valid inventory snapshot and generates an inventory fulfillment status to be confirmed. The query abnormality includes no response from the inventory management interface, missing returned fields, an empty inventory version, or an expired status validity period. The most recent valid inventory snapshot is an inventory snapshot record with the same material code, the same warehouse identifier, and whose status validity period is still being recorded. If no most recent valid inventory snapshot exists, the inventory status query module marks the corresponding inventory status for that warehouse as not obtained and writes an inventory query abnormality field into the missing parts status record. The inventory fulfillment status to be confirmed does not directly generate a transfer request record in S400; it requires a confirmation status write-back from the maintenance terminal or warehouse terminal before proceeding to subsequent processing.

[0071] In one implementation scenario, the spare parts requirement record generated by S200 includes the oil pressure sensor material code, the required quantity of 1 unit, and the compatible model. The inventory status query module first queries the local warehouse inventory snapshot record. The local warehouse currently has 1 unit, is locked 1 unit, and has 0 units reserved, meaning the available inventory in the local warehouse is 0 units. Next, it queries the branch warehouse inventory snapshot record, finding that the branch warehouse currently has 0 units. Then, it queries the collaborative warehouse inventory snapshot record, finding that the collaborative warehouse currently has 2 units, is locked 0 units, and has 0 units reserved. The inventory status query module generates a shortage status record and writes the available quantity from the collaborative warehouse into the inventory satisfies status. The shortage status record and the inventory satisfies status serve as inputs for S400 to generate replenishment forecast results, transfer request records, and spare parts supply plan records.

[0072] S400: Generate replenishment prediction results based on the missing parts status record and historical spare parts consumption data; when the maintenance priority meets the emergency allocation conditions, generate an allocation request record based on the available inventory quantity of the cooperative warehouse and the estimated arrival time, and generate a spare parts supply plan record.

[0073] This step is executed by the shortage parts processing module and the transfer request generation module. The shortage parts processing module receives the shortage parts status record and inventory satisfaction status generated by S300, and reads historical spare parts consumption data; the transfer request generation module receives the replenishment forecast result, maintenance priority, and available inventory quantity in the cooperating warehouse output by the shortage parts processing module, and generates a transfer request record when the emergency transfer conditions are met. The historical spare parts consumption data comes from maintenance task records, spare parts requisition records, return records, and inbound / outbound records, and is stored according to material code, compatible model, standard fault entity, and time window.

[0074] The shortage processing module first reads the material code, shortage quantity, required quantity, available quantity, warehouse query range, and inventory version from the shortage status record. For material codes with a shortage quantity greater than 0, the module reads historical spare parts consumption data according to the material code and generates a moving average consumption rate based on the historical consumption time window. The historical consumption time window can be configured for the past 30 days, 60 days, or 90 days; in one implementation, different material codes can be configured with different historical consumption time windows. The moving average consumption rate is the average consumption result after deducting the returned quantity from the actual replacement quantity within the historical consumption time window.

[0075] The replenishment forecast result is generated based on moving average consumption, procurement lead time, and safety stock. The procurement lead time is the time field from the generation of the corresponding material code from the procurement suggestion record to the expected receipt of the goods; the safety stock is the inventory minimum field configured according to the material code. The shortage handling module reads the current available inventory quantity and the shortage quantity, writes the moving average consumption, procurement lead time, and safety stock into the replenishment forecast calculation record, and generates the expected replenishment date and suggested replenishment quantity. The expected replenishment date can be obtained by adding the procurement lead time to the current date; the suggested replenishment quantity can be formed by the safety stock, moving average consumption, and shortage quantity, and is written into the replenishment forecast result. The replenishment forecast result includes the material code, shortage quantity, moving average consumption, procurement lead time, safety stock, expected replenishment date, and suggested replenishment quantity.

[0076] The emergency allocation conditions consist of maintenance priority, missing parts quantity, estimated replenishment date, and available inventory quantity in the collaborating warehouse. Specifically, the allocation request generation module reads the maintenance priority. When the maintenance priority is emergency, the missing parts quantity in the missing parts status record is greater than 0, the estimated replenishment date in the replenishment forecast result is later than the planned processing date of the current maintenance task, and there is available inventory quantity in the collaborating warehouse, an allocation request record is generated. If the maintenance priority is not emergency, the allocation request generation module does not generate an allocation request record, but only writes the replenishment forecast result into the spare parts supply plan record. If the maintenance priority is emergency but the available inventory quantity in the collaborating warehouse is 0, the allocation request generation module marks the allocation status as no transferable inventory and retains the replenishment forecast result.

[0077] The allocation request record includes a cooperating warehouse identifier, available quantity, estimated arrival time, allocation priority, and request status. The cooperating warehouse identifier is derived from a snapshot of the cooperating warehouse inventory in the S300 inventory satisfaction state; the available quantity is generated by the smaller of the cooperating warehouse's available inventory quantity and the number of missing parts; the estimated arrival time is generated by the cooperating warehouse's service area, warehouse location record, and delivery time slot configuration; the allocation priority is generated by the maintenance priority and the number of missing parts; the request status includes pending, sent, responded to, rejected, and timeout statuses. After the allocation request record is generated, the allocation request generation module writes the request status into the spare parts supply plan record and sends the allocation request record to the cooperating warehouse interface or cooperating warehouse terminal.

[0078] In one implementation, when multiple collaborative warehouses have available inventory, the allocation request generation module filters based on estimated arrival time, available allocation quantity, and warehouse service range, generating a primary allocation request record and a candidate allocation request record. The primary allocation request record is first sent to the corresponding collaborative warehouse; if the primary allocation request record does not receive a response within a preset response time, the allocation request generation module marks the request status of the primary allocation request record as timed out and changes the candidate allocation request record to a pending state. Both the response time and the candidate allocation request record are written into the spare parts supply plan record.

[0079] In another implementation, when the shortage status record includes a substitute part field, the shortage processing module reads the substitute part inventory status. If the primary material code is out of stock but the substitute material code has available inventory in the local warehouse or a sub-warehouse, the shortage processing module writes the substitute part supply status to the spare parts supply plan record, while retaining the primary material code in the replenishment forecast result. The substitute part supply status includes the substitute material code, substitute part identifier, substitute quantity, and substitute source warehouse. In this implementation, the spare parts supply plan record simultaneously includes the primary material code replenishment forecast result and the substitute material code supply status.

[0080] The spare parts supply plan record is generated jointly by the inventory availability status, replenishment forecast results, and transfer request records. If all spare parts demand records are covered by the inventory availability status, the spare parts supply plan record records the supply path from the local warehouse or a branch warehouse; if there is a shortage of parts and no transfer request record has been generated, the spare parts supply plan record records the replenishment forecast results; if there is a shortage of parts and a transfer request record has been generated, the spare parts supply plan record records the request status, cooperating warehouse identifier, available quantity, and estimated arrival time of the transfer request record. The spare parts supply plan record is bound by equipment identifier, standard fault entity, and maintenance plan identifier, and is used by the S500 to generate maintenance task order records.

[0081] In one implementation scenario, the S300-generated spare parts status record shows that the starter battery material code is missing 1 unit, the available inventory in the local warehouse and branch warehouse is 0 units, and the available inventory in the collaborative warehouse is 2 units; the maintenance priority is "emergency". The spare parts processing module reads the historical spare parts consumption data of the starter battery material code, generates a moving average consumption based on the historical consumption time window of the past 60 days, and generates the expected replenishment date and recommended replenishment quantity by combining the procurement lead time and safety stock. The allocation request generation module compares the maintenance priority, the number of missing parts, the expected replenishment date, and the available inventory in the collaborative warehouse to generate an allocation request record, and writes the collaborative warehouse identifier, the available allocation quantity, the expected arrival time, and the request status into the spare parts supply plan record. The spare parts supply plan record serves as the input for the S500 to generate the maintenance task order record.

[0082] S500: Bind the fault analysis record, the standard maintenance plan, the spare parts requirement record, the missing parts status record, and the spare parts supply plan record to generate a maintenance task order record and push it to the maintenance terminal.

[0083] This step is executed by the maintenance task order generation module. The maintenance task order generation module receives the fault analysis record generated by S100, the standard maintenance plan and spare parts requirement record matched by S200, the inventory fulfillment status and spare parts shortage status record generated by S300, and the spare parts supply plan record generated by S400. The maintenance task order generation module uses equipment identifier, standard fault entity, maintenance plan identifier, and task generation time as binding fields to write the above records into the same maintenance task order record. The maintenance terminal is the terminal for maintenance personnel to receive maintenance tasks, view maintenance steps, confirm spare parts retrieval, and write back the actual spare parts consumption record.

[0084] The maintenance task record includes equipment identification, equipment file version, standard fault entity, fault diagnosis result, standard maintenance plan, maintenance steps, spare parts requirement record, inventory availability status, spare parts shortage status record, spare parts supply plan record, task status version, push status, and inventory-bound version. The fault diagnosis result is formed by the standard fault entity in the fault analysis record and the fault cause in the maintenance plan record; the maintenance steps are derived from the standard maintenance plan; the spare parts requirement record records the material code, required quantity, and compatible model; the inventory availability status and spare parts shortage status records record the spare parts supply status; the spare parts supply plan record records the replenishment forecast result or transfer request record; and the inventory-bound version is written by the inventory version recorded in the inventory snapshot record read by S300.

[0085] Before generating a maintenance task order record, the maintenance task order generation module performs consistency matching on the fault analysis record, standard maintenance plan, spare parts requirement record, missing parts status record, and spare parts supply plan record. This consistency matching includes equipment identifier consistency matching, standard fault entity consistency matching, maintenance plan version consistency matching, and inventory binding version consistency matching. If the equipment identifiers in the above records are inconsistent, the maintenance task order generation module generates a task order exception record and writes the exception type into the task order status version. If the maintenance plan version is inconsistent with the requirement source plan in the spare parts requirement record, the maintenance task order generation module calls S200 to regenerate the spare parts requirement record. If the inventory binding version is inconsistent with the current inventory snapshot record version, the maintenance task order generation module calls S300 to recalculate the available inventory quantity and update the inventory fulfillment status and missing parts status records.

[0086] The task order status version is used to record the status changes of maintenance task orders during generation, push, receipt, execution, completion, and write-back. When a maintenance task order is generated for the first time, the task order status version is written to the initial version; after being pushed to the maintenance terminal, the push status is written to "pushed"; after the maintenance terminal receives it, the push status is written to "received". If the maintenance terminal does not return the receiving result within a preset time, the maintenance task order generation module writes the push status to "pending retry" and retains the last push time and the push terminal identifier. In one embodiment, the maintenance task order generation module performs idempotency verification according to the task order status version; if the same device identifier, the same standard fault entity, and the same maintenance plan identifier are not terminated in the task order status version, a new maintenance task order record will not be generated repeatedly.

[0087] When the maintenance task order record is pushed to the maintenance terminal, the maintenance task order generation module encapsulates the maintenance steps, spare parts requirement records, and spare parts supply plan records into a terminal display record. In the terminal display record, the maintenance steps are arranged in the order of steps in the standard maintenance plan; spare parts requirement records are grouped according to mandatory and optional identifiers; inventory availability status is displayed in the order of local warehouse, sub-warehouse, and collaborative warehouse; the shortage status record displays the material code, shortage quantity, and replenishment forecast result; and the transfer request record displays the collaborative warehouse identifier, available transfer quantity, estimated arrival time, and request status. After receiving the terminal display record, maintenance personnel can write back the spare parts receipt, transfer arrival, and actual replacement status.

[0088] In one implementation, after a maintenance task order record is generated, the maintenance task order generation module sends the inventory binding version to the inventory status query module. The inventory status query module generates a reservation record for the corresponding material code based on the inventory binding version and writes the reserved quantity into subsequent versions of the inventory snapshot record. If the inventory status query module returns a reservation failure status, the maintenance task order generation module marks the inventory binding version of the maintenance task order record as a reservation exception and re-calls S300 to query the inventory snapshot record. If the reservation is successful, the maintenance task order generation module writes the reservation status into the maintenance task order record.

[0089] In another implementation, the maintenance terminal writes back the actual spare parts consumption record after maintenance is completed. The actual spare parts consumption record includes the actual replaced spare parts, the actual quantity, the returned quantity, the maintenance completion time, and the maintenance result. After receiving the actual spare parts consumption record, the maintenance task order generation module compares it with the spare parts requirement record in the original maintenance task order. If the material code of the actually replaced spare parts matches the material code in the spare parts requirement record, the historical spare parts consumption data is updated based on the actual quantity and the returned quantity. If the material code of the actually replaced spare parts does not match the material code in the spare parts requirement record, a consumption difference record is generated, and the actual replaced spare parts, the original required material code, the difference quantity, and the maintenance result are written into the mapping rule version update record. The mapping rule version update record is then entered into the subsequent spare parts mapping rule maintenance process.

[0090] In one implementation scenario, fault analysis records for startup failures, standard maintenance plans for the startup system, spare parts demand records for startup batteries, records of startup battery shortage status, and records of transfer requests from collaborative warehouses have all been generated. After reading these records, the maintenance task order generation module generates a maintenance task order record using the equipment identifier and standard fault entity as binding fields. It also writes the startup system inspection steps, startup battery material code, shortage quantity, collaborative warehouse identifier, estimated arrival time, and transfer request status into the same maintenance task order record. Once this maintenance task order record is pushed to the maintenance terminal, maintenance personnel can view the maintenance steps and spare parts supply plan on the terminal. After maintenance is completed, the maintenance terminal writes back the actual number of startup batteries replaced and returned, and the maintenance task order generation module updates the historical spare parts consumption data and mapping rule version accordingly.

[0091] Example 2: Figure 2 A structural block diagram of a remote fault diagnosis and spare parts prediction system for diesel generator sets according to an embodiment of the present invention is shown. Figure 2 As shown, the structure may include:

[0092] The fault information receiving module 01 is used to receive fault information, equipment identification, and maintenance priority of the diesel generator set, and output a fault reception record. Specifically, the fault information receiving module receives fault information from the diesel generator set, maintenance terminal, or remote operation and maintenance platform. The fault information includes a fault code or a description of the fault phenomenon. The equipment identification is received along with the fault information, and the maintenance priority is input by the maintenance terminal or written by the remote operation and maintenance platform according to the service status in the equipment file. The fault information receiving module performs field integrity verification on the fault information, the equipment identification, and the maintenance priority. When the equipment identification is missing, a pending record status is generated; when the fault information is empty, a pending review status is generated. After the field verification is completed, the fault information receiving module writes the fault source, reception time, fault code, fault phenomenon description, equipment identification, and maintenance priority into the fault reception record. The fault reception record retains the original fault information fields and provides the fault information, the equipment identification, and the maintenance priority to the fault parsing module.

[0093] The fault analysis module 02, connected to the fault information receiving module, is used to read the equipment file based on the fault reception record and the equipment identifier, map the fault information to standard fault entities, and generate a fault analysis record. Specifically, the fault analysis module receives the fault reception record from the fault information receiving module and reads the equipment file based on the equipment identifier. The equipment file includes the unit model, engine model, controller model, compatible model, and equipment file version. When the fault information includes a fault code, the fault analysis module reads the corresponding record between the fault code and the standard fault entity according to the mapping rule version, mapping the fault code to a standard fault entity. When the fault information includes a description of the fault phenomenon, the... The fault analysis module performs word segmentation, entity recognition, and synonym normalization on the fault phenomenon description, and maps the normalization results to standard fault entities. When multiple standard fault entities match simultaneously, the fault analysis module filters them based on the compatible machine model and controller model in the equipment file and records the candidate analysis fields. When no standard fault entity is matched, the fault analysis module retains the fault reception record and generates a pending review analysis status. After analysis is completed, the fault analysis module generates a fault analysis record, which includes the equipment identifier, equipment file version, standard fault entity, mapping rule version, maintenance priority, and analysis status. The fault analysis record is then provided to the maintenance plan and spare parts requirement generation module for invocation.

[0094] The maintenance plan and spare parts requirement generation module 03, connected to the fault analysis module, is used to call the fault knowledge base based on the fault analysis record and the equipment file, match standard maintenance plans according to the model compatibility relationship, and generate spare parts requirement records containing material codes, required quantities, and compatible models. Specifically, the maintenance plan and spare parts requirement generation module receives fault analysis records from the fault analysis module and reads the standard fault entity, equipment identifier, and equipment file version from the fault analysis record. The maintenance plan and spare parts requirement generation module calls the corresponding equipment file based on the equipment file version and calls the fault knowledge base using the standard fault entity and the compatible models in the equipment file as query conditions. The fault knowledge base includes standard fault entities, fault causes, standard maintenance plans, maintenance steps, spare parts materials, model compatibility relationships, and... Replacement parts relationships; when matching standard maintenance plans, the maintenance plan and spare parts requirement generation module compares the standard fault entity with the standard fault entity field in the fault knowledge base, and compares the compatible models in the equipment file with the model compatibility relationships in the standard maintenance plan to generate a standard maintenance plan; when multiple standard maintenance plans exist, the maintenance plan and spare parts requirement generation module filters the standard maintenance plans according to the equipment file version, compatible models, and plan version, and records the maintenance plan record; subsequently, the maintenance plan and spare parts requirement generation module matches the spare parts materials in the standard maintenance plan with the spare parts mapping rules, filters the material codes according to the model compatibility relationships, and generates a spare parts requirement record containing the material code, required quantity, and compatible model; the spare parts requirement record is provided to the inventory status query module along with the standard maintenance plan.

[0095] The inventory status query module 04, connected to the maintenance plan and spare parts requirement generation module, is used to query the inventory snapshot records of the local warehouse, branch warehouse, and cooperative warehouse based on the spare parts requirement records. It calculates the available inventory quantity based on the current quantity, locked quantity, and reserved quantity, and generates inventory fulfillment and shortage status records. Specifically, the inventory status query module receives spare parts requirement records from the maintenance plan and spare parts requirement generation module and reads the material code, required quantity, and compatible model from the spare parts requirement records. The inventory status query module queries the inventory snapshot records of the local warehouse, branch warehouse, and cooperative warehouse sequentially according to the material code. The inventory snapshot records include warehouse identifier, inventory version, current quantity, locked quantity, reserved quantity, in-transit quantity, and status validity period. The inventory status query module also queries the current quantity of the same material code under the same warehouse identifier. The system calculates the available inventory quantity by considering the locked quantity and the reserved quantity. When the inventory snapshot record contains a quantity in transit that is within the validity period of its status, the inventory status query module writes the quantity in transit into the available inventory quantity calculation record. When the inventory snapshot record query is abnormal, the inventory status query module reads the most recent valid inventory snapshot and marks the inventory fulfillment status as pending confirmation. When the inventory version changes, the inventory status query module recalculates the available inventory quantity and updates the inventory fulfillment status and shortage status records. The inventory fulfillment status record records the matching result between the material code, warehouse identifier, available inventory quantity, and required quantity. The shortage status record records the material code, required quantity, fulfillable quantity, shortage quantity, and inventory version. The inventory status query module provides the inventory fulfillment status and the shortage status records to the shortage processing module.

[0096] The shortage parts processing module 05, connected to the inventory status query module, is used to generate replenishment prediction results based on the shortage parts status records and historical spare parts consumption data. When the maintenance priority meets the emergency allocation conditions, it generates an allocation request record based on the available inventory quantity in the cooperating warehouse and the estimated arrival time, and generates a spare parts supply plan record. Specifically, the shortage parts processing module receives the shortage parts status records and inventory availability status from the inventory status query module, and reads the material code, shortage quantity, inventory version, and warehouse query range from the shortage parts status records. The shortage parts processing module reads historical spare parts consumption data according to the material code. The historical spare parts consumption data includes maintenance task records, spare parts requisition records, return records, and inbound / outbound records. The shortage parts processing module generates a moving average consumption amount based on the historical consumption time window, and generates a spare parts supply plan based on the moving average consumption amount, procurement lead time, and safety stock. The replenishment forecast results include the expected replenishment date and the suggested replenishment quantity. The shortage parts processing module reads the maintenance priority from the fault analysis record and matches the maintenance priority, shortage quantity, expected replenishment date, and available inventory in the collaborating warehouse with emergency allocation conditions. When the maintenance priority meets the emergency allocation conditions, the shortage parts processing module generates an allocation request record based on the available inventory in the collaborating warehouse and the expected arrival time. The allocation request record includes the collaborating warehouse identifier, available allocation quantity, expected arrival time, allocation priority, and request status. When the maintenance priority does not meet the emergency allocation conditions, the shortage parts processing module writes the replenishment forecast results into the spare parts supply plan record. The spare parts supply plan record is bound to the inventory satisfaction status, shortage status record, replenishment forecast results, and allocation request record, and is provided to the maintenance task order generation module for invocation.

[0097] The maintenance task order generation module 06, connected to the missing parts processing module, is used to bind the fault analysis record, the standard maintenance plan, the spare parts requirement record, the missing parts status record, and the spare parts supply plan record, generate a maintenance task order record, and push it to the maintenance terminal. Specifically, the maintenance task order generation module receives the fault analysis record from the fault analysis module, the standard maintenance plan and spare parts requirement record from the maintenance plan and spare parts requirement generation module, and the spare parts supply plan record from the missing parts processing module; the maintenance task order generation module reads the missing parts status record, replenishment forecast result, and allocation request record from the spare parts supply plan record, and generates a maintenance task order record using equipment identifier, standard fault entity, standard maintenance plan, and task generation time as binding fields; the maintenance task order record includes equipment identifier, equipment file version, standard fault entity, standard maintenance plan, maintenance steps, spare parts requirement record, missing parts status record, spare parts supply plan record, task order status version, push status, and inventory binding version; in generating maintenance task orders... Before recording a maintenance task order, the maintenance task order generation module performs a consistency match on the equipment identifier, standard fault entity, standard maintenance plan, and inventory binding version. When the inventory binding version is inconsistent with the current inventory version in the inventory snapshot record, the maintenance task order generation module calls the inventory status query module to regenerate the inventory fulfillment status and missing parts status records. When the standard maintenance plan is inconsistent with the demand source plan in the spare parts demand record, the maintenance task order generation module calls the maintenance plan and spare parts demand generation module to regenerate the spare parts demand record. After the maintenance task order record is generated, the maintenance task order generation module pushes the maintenance task order record to the maintenance terminal and receives the push status returned by the maintenance terminal. The push status and task order status version are saved with the maintenance task order record.

Claims

1. A method for remote fault diagnosis and spare parts prediction of diesel generator sets, characterized in that, include: S100: Receive fault information, equipment identification and maintenance priority of diesel generator set; read equipment file based on equipment identification; map fault information to standard fault entities; and generate fault analysis record. S200. Based on the fault analysis record and the equipment file, call the fault knowledge base, match the standard maintenance plan according to the model compatibility relationship, and generate a spare parts requirement record containing material code, required quantity and compatible model. S300: Based on the spare parts demand record, query the inventory snapshot records of the local warehouse, sub-warehouse and cooperative warehouse, calculate the available inventory quantity according to the existing quantity, locked quantity and reserved quantity, and generate inventory satisfaction status and shortage status records. S400: Generate replenishment prediction results based on the missing parts status records and historical spare parts consumption data; When the maintenance priority meets the emergency allocation conditions, an allocation request record is generated based on the available inventory quantity in the cooperative warehouse and the estimated arrival time, and a spare parts supply plan record is also generated. S500: Bind the fault analysis record, the standard maintenance plan, the spare parts requirement record, the missing parts status record, and the spare parts supply plan record to generate a maintenance task order record and push it to the maintenance terminal.

2. The method according to claim 1, characterized in that, The fault information includes fault codes or descriptions of fault phenomena. When the fault information includes a fault code, the fault code is mapped to a standard fault entity according to the mapping rule version; When the fault information includes a description of the fault phenomenon, the fault phenomenon description is segmented into words, identified as an entity, and normalized with synonyms to generate a standard fault entity.

3. The method according to claim 1, characterized in that, The fault knowledge base includes standard fault entities, fault causes, standard repair solutions, repair steps, spare parts and materials, model compatibility relationships, and alternative parts relationships; When matching a standard repair plan according to the model compatibility relationship, a repair plan record is generated using the standard fault entity in the fault analysis record and the compatible model in the equipment file as query conditions.

4. The method according to claim 1, characterized in that, The spare parts requirement record includes mandatory identifiers, optional identifiers, alternative identifiers, requirement source schemes, and requirement confidence levels; When generating the spare parts requirement record, the spare parts materials in the standard maintenance plan are matched with the spare parts mapping rules, and the material codes are filtered according to the model compatibility relationship.

5. The method according to claim 1, characterized in that, The inventory snapshot record includes warehouse identifier, inventory version, current quantity, locked quantity, reserved quantity, quantity in transit, and status validity period; The available inventory quantity is obtained by subtracting the locked quantity and reserved quantity from the existing quantity, and then adding it to the quantity in transit that is within the validity period of the status.

6. The method according to claim 1, characterized in that, Before generating a maintenance task record, the inventory version of the inventory snapshot record is verified. When the inventory version changes, the available inventory quantity is recalculated, and the inventory fulfillment status and the shortage status records are updated. When the inventory snapshot record query is abnormal, the most recent valid inventory snapshot is read and an inventory satisfaction status to be confirmed is generated.

7. The method according to claim 1, characterized in that, When generating replenishment forecast results, the historical spare parts consumption data is read by material code, a moving average consumption is generated based on the historical consumption time window, and the expected replenishment date and recommended replenishment quantity are generated based on the moving average consumption, procurement lead time and safety stock.

8. The method according to claim 1, characterized in that, The emergency allocation conditions consist of repair priority, number of missing parts, expected replenishment date, and available inventory in the cooperating warehouse; The allocation request record includes the collaborative warehouse identifier, available quantity, estimated arrival time, allocation priority, and request status.

9. The method according to claim 1, characterized in that, The maintenance task order record includes the task order status version, push status, and inventory binding version; The system receives the actual spare parts consumption records written back from the maintenance terminal and updates the historical spare parts consumption data and mapping rule version based on the actual replaced spare parts, the actual quantity, and the quantity returned.

10. A remote fault diagnosis and spare parts prediction system for diesel generator sets, characterized in that, include: Fault information receiving module, fault analysis module, maintenance plan and spare parts requirement generation module, inventory status query module, missing parts handling module, and maintenance task order generation module; The system is used to implement the method described in any one of claims 1-9.