Machining spare part intelligent inventory management method and system

Abstract

The application discloses a kind of machining spare parts intelligent inventory management method and system, solve the technical problems such as fuzzy inventory information in traditional spare parts management, blind spare, out-of-stock early warning is not timely and excessive capital occupation;The system includes spare parts information management module, inventory monitoring module, demand prediction module, early warning module and procurement management module, can realize the digitization of spare parts information filing, allocate unique code for each spare part, record its model, specification, applicable equipment, shelf life and other key information.The method includes spare parts filing, inventory monitoring, demand prediction, early warning triggering, procurement execution and inventory optimization and other steps, realize the intelligentization of machining spare parts inventory, fine management, balance spare supply and cost control, reduce the production downtime caused by spare shortage, improve spare parts inventory turnover rate, reduce capital occupation cost, provide reliable spare parts guarantee for machine tool operation.

Description

Technical Field

[0001] This invention relates to the field of machining spare parts inventory management technology, and more specifically, to an intelligent inventory management method and system for machining spare parts. Background Technology

[0002] In the practice of machining spare parts management, existing technologies mainly focus on replenishing key spare parts as soon as possible and reducing inventory occupation without interrupting the existing warehousing and procurement processes. In engineering, the spare parts information management module first completes the filing of information such as spare parts code, model specifications, applicable equipment and warranty period. Then, the inventory monitoring module continuously records the warehousing, outbound, inventory count and procurement in transit status. Subsequently, the demand forecasting module combines historical requisition records, maintenance frequency and replacement cycle to form subsequent demand judgments. The early warning module issues replenishment prompts according to changes in inventory balance. Based on this, the procurement management module initiates purchase requests and tracks the delivery progress. Taking a workshop with multiple CNC machining centers and grinding equipment operating continuously as an example, for spare parts such as spindle assemblies, servo drive boards, and ball screw assemblies, which have long procurement cycles and require verification of compatibility after delivery, the site cannot afford to shut down for extended periods while waiting for delivery, nor can it repeatedly insert orders and expedite delivery outside the existing procurement chain. In this usage scenario, a phenomenon that can be directly verified often occurs: after the system issues a purchase request, the supplier confirms it, or the goods are shipped, the inventory risk warning weakens, and the relevant spare parts are considered as resources that can be replenished later on the books. However, the target equipment will still shut down because there are no spare parts available for replacement before the spare parts arrive in the warehouse and are verified. This manifests as the procurement process showing normal progress and the inventory ledger showing a decrease in risk, but maintenance actions cannot be carried out on time. The reason for this result is that the existing processing method prematurely includes spare parts in transit that have not yet been delivered, accepted and adapted into the actual guaranteed inventory. The technical problem that this application aims to solve is: how to avoid prematurely considering in-transit purchases that have not yet been fulfilled as guaranteed inventory in the process of machining spare parts inventory management, so as to prevent inventory judgment distortion and reduce the risk of equipment downtime caused by misjudgment. Summary of the Invention

[0003] To overcome the aforementioned deficiencies of the prior art, embodiments of the present invention provide an intelligent inventory management method and system for machined spare parts. This method and system performs corresponding modeling based on spare parts definition information, procurement progress information, and inventory status information around the maintenance demand time point. It also determines whether the inventory can be guaranteed based on the fulfillment conditions of "arrived in the warehouse," "verified," and "batch-matched," and performs cause breakdown and procurement action write-back update for any unfulfilled gaps, thereby solving the problems mentioned in the background art.

[0004] To achieve the above objectives, the present invention provides the following technical solution: an intelligent inventory management method for machined spare parts, comprising: S1. Obtain the spare part code, model specifications, applicable equipment, compatible parts, supply method, warehouse verification items and batch compatibility items of the spare parts to be managed. Perform fixed-length filing for each field corresponding to the same spare part code and generate a spare part definition table. S2. Read the inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipping records, arrival records and review records corresponding to each spare part code, and perform serialization and organization of each record under the same spare part code according to the record time sequence to generate a purchase progress table and an inventory status table. S3. Match the applicable equipment, compatible parts, warehouse verification items and batch compatibility items in the spare parts definition table with the current inventory records, in-transit records and verification records in the inventory status table one by one. Combine the maintenance demand time points corresponding to each spare parts code to perform dynamic modeling, form a fulfillment status sequence, and determine whether each fulfillment status sequence has available spare parts that have arrived in the warehouse, have been verified and are compatible, and generate an unfulfilled gap table. S4. For each unfulfilled gap in the unfulfilled gap table, perform segmentation and splitting according to the order of the purchase application status: generated but not confirmed, confirmed but not shipped, shipped but not delivered to the warehouse, delivered to the warehouse but not approved, and approved but batch mismatched, and generate a gap cause table and a warning result table.

[0005] In a preferred embodiment, it further includes: S5. Based on the cause type in the gap cause table, the corresponding maintenance demand time point, and the corresponding procurement record in the procurement schedule table, generate supplementary procurement results, order insertion results, delivery reminder results, or alternative procurement results for each unfulfilled gap. Write the generated results into the inventory status table according to the spare parts code and write-back time to perform dynamic modeling and update of the corresponding fulfillment status sequence, and obtain the updated inventory control results.

[0006] In a preferred embodiment, S1 includes: S11. For the same spare part code, perform fixed-length partition expansion according to the predetermined field order for the model specifications, applicable equipment, matching parts, supply methods, warehouse verification items and batch matching items, write field values ​​and empty space markers for the field positions corresponding to each field, and generate spare part field position sequence. S12. Perform sequential pairing of applicable equipment and compatible parts in each spare parts field sequence, and perform corresponding linking of supply method with warehouse verification item and batch compatibility item to generate spare parts acceptance relationship sequence. S13. Merge and write each spare part acceptance relationship sequence according to the spare part code, and output a spare part definition table containing the spare part code, field bit sequence and spare part acceptance relationship sequence.

[0007] In a preferred embodiment, S2 includes: S21. For the same spare part code, the inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipment records, arrival records and review records are uniformly sorted according to the order of recording time. For records with the same recording time, the records are sequentially expanded according to the fixed order of purchase requisition, supply confirmation, shipment, arrival, review, inbound, outbound and inventory, to generate a spare part sequence record chain. S22. Perform a succession check on adjacent records in each spare parts time sequence record chain, identify the procurement progress segment between the purchase application and the review record, the inventory change segment between the warehousing and outbound records, and the pending acceptance segment between the arrival record and the review record, and generate a procurement progress sequence and an inventory status sequence. S23. Merge and write each procurement schedule sequence and each inventory status sequence according to spare parts code, and output a procurement schedule table and an inventory status table containing spare parts code, procurement schedule sequence and inventory status sequence.

[0008] In a preferred embodiment, S3 includes: S31. For the same spare part code, the applicable equipment, matching parts, warehouse verification items and batch matching items are expanded in the same position with the current inventory record, in-transit record and verification record according to the maintenance demand time point. For each maintenance demand time point, a candidate fulfillment group is constructed consisting of spare part arrival status, verification completion status and batch matching status. For each candidate fulfillment group, forward acceptance verification and reverse source verification are performed. Candidate corresponding edges with source break, time point reversal and part mismatch are deleted. The candidate fulfillment diagram is output. S32. Starting from the maintenance demand time point in each candidate fulfillment diagram and taking each candidate fulfillment group as the receiving node, perform constraint pathfinding in a fixed order of priority for already arrived at warehouse, priority for already reviewed, priority for batch adaptation, and priority for minimum time point difference. For multiple receiving paths corresponding to the same maintenance demand time point, perform first-to-last consistency check, path back-pointing check, and conflict occupancy resolution one by one. After each round of resolution, only retain the receiving paths that satisfy the conditions that the path length no longer shortens, the number of conflict nodes no longer decreases, and the first and second paths of the two rounds remain consistent, and output the fulfillment status sequence.

[0009] In a preferred embodiment, S3 further includes: S33. Perform a step-by-step comparison between each acceptance path in the fulfillment status sequence and the corresponding maintenance demand time point. For cases where there is no record of arrival at the warehouse, arrival at the warehouse but no record of verification approval, verification approval but no batch adaptation result, and the same available spare part cannot be accepted after being occupied by the previous maintenance demand time point, mark them as unfulfilled gaps, unverified gaps, adaptation failure gaps, and occupied conflict gaps respectively. Write them into the unfulfilled gap table according to spare part code, maintenance demand time point, gap type and corresponding source record.

[0010] In a preferred embodiment, S4 includes: S41. For each unfulfilled gap corresponding to the same spare part code in the unfulfilled gap table, perform positional expansion according to the maintenance demand time point, purchase record time point, shipment record time point, warehouse arrival record time point, and review record time point. Construct segmented cost groups based on the time point acceptance difference, status acceptance difference, and record back-pointing difference between the gap source record and the preceding purchase record. Under the constraints of ensuring that the purchase record time point is not later than the corresponding maintenance demand time point, the preceding and following states are not reversed, and the source record can be back-pointed, perform forward segment matching and reverse source verification for each unfulfilled gap, and output a gap candidate segment table.

[0011] In a preferred embodiment, S4 further includes: S42. Perform multiple rounds of consistency resolution on each candidate segment in the gap candidate segmentation table according to the fixed order of procurement application generated but not confirmed, confirmed but not shipped, shipped but not delivered to the warehouse, delivered to the warehouse but not approved, and approved but batch mismatched. For the same unfulfilled gap, compare the consistency of the status order, the closure of the source record, and the convergence of adjacent time points for each candidate segment. Only retain the target segment with consistent status order, closure of the source record at the beginning and end, and no change in the retention results of adjacent two rounds. Generate a gap cause table. S43. Based on the target segments in the gap cause table, perform forward impact expansion on each unfulfilled gap under the same spare part code. Build a warning judgment sequence by combining the gap duration length, the number of times the maintenance demand is affected, and the number of times the same type of gap recurs, corresponding to the target segment. Perform cross-checking on each warning judgment sequence to distinguish between warnings pending confirmation, warnings pending shipment, warnings pending arrival at the warehouse, warnings pending review, and adaptation failure warnings. Write the warning results in the warning result table according to spare part code, maintenance demand time, cause segment, and warning type.

[0012] In a preferred embodiment, S5 includes: S51. For each unfulfilled gap in the gap cause table, perform a corresponding mapping with the corresponding procurement record in the procurement schedule table according to the spare parts code, maintenance demand time and cause type. Compare the maintenance demand time with the application time, confirmation time, shipment time and expected arrival time in the corresponding procurement record item by item to generate a procurement action candidate table containing supplementary procurement candidate, order insertion candidate, expedited delivery candidate and alternative procurement candidate. S52. Perform sequential screening on each procurement action candidate in the procurement action candidate table according to the cause type, time difference, and previous procurement relationship. When multiple procurement action candidates correspond to the same unfulfilled gap, prioritize the procurement action candidates that can make the expected arrival time in the warehouse earlier than the corresponding maintenance demand time and do not overlap with the previously retained procurement actions, and generate a procurement action result table. S53. Write the supplementary procurement results, order insertion results, delivery reminder results, or alternative procurement results from the procurement action results table into the inventory status table according to the spare parts code and write-back time. Perform synchronous updates on the procurement progress record and available inventory record for the corresponding spare parts code, and output the updated inventory control results.

[0013] A smart inventory management system for machined spare parts, the system comprising a spare parts information management module, an inventory monitoring module, a demand forecasting module, an early warning module, and a procurement management module: The spare parts information management module is used to obtain the spare parts code, model specifications, applicable equipment, compatible parts, supply method, warehouse verification items and batch compatibility items of the spare parts to be managed. It performs fixed-length filing for each field corresponding to the same spare parts code and generates a spare parts definition table. The inventory monitoring module is used to read the inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipment records, arrival records and review records corresponding to each spare part code. It performs serialization and sorting of records under the same spare part code according to the order of the record time to generate a purchase progress table and an inventory status table. The demand forecasting module is used to match the applicable equipment, compatible parts, warehouse verification items and batch compatibility items in the spare parts definition table with the current inventory records, in-transit records and verification records in the inventory status table. It performs dynamic modeling based on the maintenance demand time points corresponding to each spare parts code to form a fulfillment status sequence. It then determines whether each fulfillment status sequence has available spare parts that have arrived in the warehouse, have been verified and are compatible, and generates an unfulfilled gap table. The early warning module is used to segment and break down each unfulfilled gap in the unfulfilled gap table according to the order of the purchase application status: generated but not confirmed, confirmed but not shipped, shipped but not delivered to the warehouse, delivered to the warehouse but not approved, and approved but batch mismatched. It generates a gap cause table and an early warning result table. The procurement management module is used to generate supplementary procurement results, order insertion results, expedited delivery results, or alternative procurement results for each unfulfilled gap based on the cause type in the gap cause table, the corresponding maintenance demand time, and the corresponding procurement record in the procurement schedule table. The generated results are then written into the inventory status table according to the spare parts code and write-back time to perform dynamic modeling and updates on the corresponding fulfillment status sequence, resulting in updated inventory control results.

[0014] The technical effects and advantages of this invention are as follows: 1. This solution matches the applicable equipment, compatible parts, warehouse verification items, batch compatibility items with the current inventory records, in-transit records, and verification records according to the maintenance demand time. It only includes spare parts that have arrived in the warehouse, have been verified, and are compatible in the fulfillment status sequence. This avoids prematurely including in-transit purchases that have not yet been fulfilled in the guaranteed inventory. This can relatively suppress inventory judgment distortion and reduce the risk of equipment downtime caused by misjudgment. 2. The purchase application, supply confirmation, shipment, arrival at the warehouse, review, warehousing, outbound and inventory records are connected in a unified time sequence, and the purchase progress stage, inventory change stage and pending acceptance stage are identified, so as to separate the purchase status and inventory status, which can relatively improve the distinguishability of purchase progress and inventory occupancy, and reduce the misreading of status caused by the mixing of different records. 3. By constructing a candidate fulfillment diagram and performing forward acceptance verification, reverse source verification, constraint pathfinding, and conflict occupancy resolution on the candidate fulfillment group, a constrained acceptance path is formed between the maintenance demand point and the available spare parts. This can relatively improve the pertinence of the acceptance inventory determination and alleviate the problem of the same spare parts being repeatedly or incorrectly accepted. 4. The unfulfilled gaps are segmented and broken down according to the order of purchase application status: unconfirmed, confirmed but not shipped, shipped but not delivered to the warehouse, delivered to the warehouse but not approved, and approved but batch mismatched. A gap cause table and an early warning result table are generated to establish a correspondence between the unfulfilled results and the previous purchase status, which can relatively improve the traceability of gap cause identification and the interpretability of early warning output. 5. Based on the cause type, maintenance demand timing, and corresponding procurement records, generate supplementary procurement, order insertion, expedited delivery, or alternative procurement results, and write the procurement actions back to the inventory status table to update the fulfillment status sequence. This forms a complete process of gap identification, cause breakdown, procurement correction, and status update, which can relatively improve the linkage between procurement disposal and inventory control and alleviate the problem of the disconnect between disposal actions and actual needs. Attached Figure Description

[0015] Figure 1 This is a flowchart outlining the method steps of the present invention; Figure 2 This is a schematic diagram of the system module structure of the present invention. Detailed Implementation

[0016] The technical solutions of the embodiments of the present invention will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of the present invention, and not all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of the present invention.

[0017] Refer to the instruction manual appendix Figure 1-2 The present invention provides an intelligent inventory management method for machined spare parts, comprising: S1. Obtain the spare part code, model specifications, applicable equipment, compatible parts, supply method, warehouse verification items and batch compatibility items of the spare parts to be managed. Perform fixed-length filing for each field corresponding to the same spare part code and generate a spare part definition table. In this embodiment, S1 is used to organize the scattered model specifications, applicable equipment, compatible parts, supply methods, warehouse verification items, and batch compatibility items under the same spare part code into a unified structure that can directly participate in subsequent serialization, correspondence, and acceptance judgment. The purpose is to first eliminate the problems of inconsistent field lengths, inconsistent value formats, and difficulty in aligning multi-value fields, and then fix the equipment-part relationship and the supply-verification-compatibility relationship under the same spare part code, ensuring that subsequent procurement progress organization, fulfillment status modeling, and gap judgment are all based on reading the same field position and the same relationship order. This implementation process includes the following steps: For S11, the purpose is to organize the original fields corresponding to the same spare part code into a field sequence with fixed position, fixed length, and identifiable gaps, so as to serve as the sole reading basis for subsequent sequential matching and corresponding connection; the input quantity is the original record of model specification, applicable equipment, adaptable part, supply method, warehouse verification item, and batch adaptable item corresponding to the same spare part code. Among them, model specification and supply method are read as single-value fields, while applicable equipment, adaptable part, warehouse verification item, and batch adaptable item are read as multi-value fields; during processing, the fields are first placed according to the predetermined field order. The predetermined field order adopts the fixed order given by the preset configuration table, which is model specification, applicable equipment, adaptable part, supply method, warehouse verification item, and batch adaptable item in sequence; Next, perform fixed-length position expansion on each field. The fixed-length value is taken as the maximum number of positions that the field is allowed to appear in the current spare parts master data. The maximum number of positions comes from the larger of the historical filing statistics and the current rule constraints. For example, if the applicable equipment field is allowed to appear in four positions, then if there are fewer than four positions, write a space marker in the empty field position. If there are more than four positions, retain the first four positions according to the field value registration order and write the remaining positions into the abnormal extended record. Write the field value, field position number and space marker for each field position to obtain a spare parts field position sequence containing spare parts code, field category, field position number, field value and space marker, and write it into a temporary field position table for S12 to read. When a field is missing in the original record, write a space marker in all field positions of that field and register the missing field type at the same time, as the source of null values ​​when generating subsequent relations. For S12, the purpose is to convert the field values ​​that can exist independently in the spare part field bit sequence into acceptable and verifiable relational items, so that what is read in subsequent steps is no longer an isolated field, but a sequence of acceptable relations with a fixed corresponding direction; the input is the spare part field bit sequence output by S11; during processing, the applicable equipment field bit and the matching part field bit are read first, and the applicable equipment field bit and the matching part field bit with the same position number and non-empty field value under the same spare part code are matched sequentially to generate equipment part acceptable items; when the applicable equipment field bit exists but the corresponding matching part field bit is empty, the applicable equipment field bit is used as the main bit and the empty bit mark is used as the part value to generate the part acceptable item to be supplemented, and the part missing mark is written in the acceptable status; When the matching part field exists but the corresponding applicable equipment field is empty, no equipment part acceptance item is generated. Instead, the field is written to the isolated part record to prevent subsequent incorrect acceptance without equipment ownership. Then, the supply method field, warehouse verification item field, and batch adaptation item field are read. Using the supply method field as the attachment master, the warehouse verification item field and batch adaptation item field are attached to the corresponding supply method field one by one according to the fixed position order within the same spare part code, generating a supply verification and adaptation acceptance item. When the supply method field is empty but the warehouse verification item or batch adaptation item exists, this part of the field does not participate in the attachment and is written separately to the pending supply record. Finally, a spare part acceptance relationship sequence containing spare part code, equipment part acceptance item, supply verification and adaptation acceptance item, acceptance status, and abnormality identifier is output and written to the acceptance relationship cache table for S13 to read. For S13, the purpose is to merge the fixed-structure field bit sequence and inheritance relationship sequence under the same spare part code into a spare part definition table that can be directly called in subsequent steps, thereby forming a basic object with unique ownership, fixed field position and fixed relationship order; the input is the spare part field bit sequence output by S11 and the spare part inheritance relationship sequence output by S12; during processing, the two types of results are merged first according to the spare part code. If there are multiple field bit sequences or multiple inheritance relationship sequences for the same spare part code, they are sorted according to the time of filing and then merged and written according to the same code. When merging, the original order of field bit number and inheritance item number is retained and no re-numbering is performed; Next, write the spare part code, field sequence, spare part acceptance relationship sequence, missing field type, isolated part record, and pending supply record into the spare part definition table. The field sequence is used for subsequent same-position correspondence reading, the spare part acceptance relationship sequence is used for subsequent acceptance judgment reading, and the missing field type and abnormal record are used for subsequent abnormal filtering and manual supplementation. When the same spare part code has a model specification conflict during merging, that is, when multiple model specification fields under the same code are not empty and the field values ​​are inconsistent, only the model specification field corresponding to the earliest file record is written into the spare part definition table, and the remaining model specification field is written into the code conflict record to prevent different spare part objects from being mistakenly mixed according to the same spare part code in the future. In practical applications: For example, when a spindle bearing spare part code corresponds to one model specification, two applicable equipment, two compatible parts, one supply method, three warehouse arrival verification items, and two batch compatibility items, the above fields are first expanded into fixed field positions according to a predetermined field order, and empty positions are marked. Then, the first applicable equipment and the first compatible part, and the second applicable equipment and the second compatible part are formed into equipment part acceptance items. The supply method, the three warehouse arrival verification items, and the two batch compatibility items are linked according to their positions to form supply verification and compatibility acceptance items. Finally, the spare part code is uniformly written into the spare part definition table. When reading the spare part definition table in subsequent steps, the applicable equipment and compatible parts can be located directly by field position number, and the supply method, warehouse arrival verification item, and batch compatibility item can be located by acceptance item number. This avoids the problems of misaligned multi-value fields, mixed empty values, and unclear relationship linkage under the same spare part code, thereby providing directly executable basic data for subsequent procurement progress sorting, fulfillment status sequence generation, and non-fulfillment gap judgment.

[0018] S2. Read the inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipping records, arrival records and review records corresponding to each spare part code, and perform serialization and organization of each record under the same spare part code according to the record time sequence to generate a purchase progress table and an inventory status table. In this implementation, S2 is used to organize the scattered inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipment records, arrival records, and review records under the same spare part code into a spare part time sequence record chain with a unified sequential relationship. Based on this, the procurement progress segment, inventory change segment, and pending acceptance segment are further extracted to form a procurement progress sequence and an inventory status sequence that can be read for subsequent fulfillment status modeling. This implementation process first resolves the time sequence ambiguity caused by the parallel appearance of records from different sources, the same record time, and overlapping record categories. Then, the start and end boundaries of various status segments are determined through the acceptance verification between adjacent records. Finally, the records are merged and written into the procurement progress table and inventory status table according to the spare part code, providing a unified input for subsequent maintenance demand timing, unfulfilled gap determination, and procurement action generation. This implementation process includes the following steps: For S21, the goal is to organize multi-source records corresponding to the same spare part code into a unique and readable spare part sequence record chain, so as to eliminate the unclear relationship caused by parallel record times and mixed record types. The input includes inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipment records, arrival records, and review records corresponding to the same spare part code. Each record must include at least the spare part code, record type, record time, and source identifier. During processing, the records are first grouped according to the spare part code, and then the records in the same group are uniformly sorted according to the order of record time. The record time is the consistent time that can be pointed back to between the system write time and the business occurrence time. If the two are inconsistent, the business occurrence time is the main time and the system write time is the secondary time. For records with the same recording time, sequential expansion is performed according to a fixed order: purchase application, supply confirmation, shipment, arrival at warehouse, verification, warehousing, outbound, and inventory count. This fixed order is determined by business constraints that purchase fulfillment precedes inventory display, inventory display precedes inventory consumption, and inventory consumption precedes inventory count correction, ensuring a unique arrangement of records at the same time. After sorting, each record is sequentially written with an intra-chain sequence number according to the sorting result, generating a spare part time sequence record chain containing spare part code, record type, record time, intra-chain sequence number, and source identifier, and written to the time sequence chain cache table for S22 to read. When a record time is missing, the record is written to the missing time record table and does not participate in the generation of the current spare part time sequence record chain. When the same source identifier, the same record type, and the same record time appear repeatedly, only the record with the highest field completeness is retained and written to the spare part time sequence record chain, and the remaining records are written to the duplicate record table. For S22, the purpose is to identify the procurement progress segment, inventory change segment, and pending inspection segment by identifying the continuity relationship between adjacent records, so that the spare parts timing record chain is transformed from a simple arrangement result into a structured sequence that can directly participate in subsequent status judgment; the input is the spare parts timing record chain output by S21; during processing, adjacent records in the chain are read one by one according to the same spare parts code. Adjacent records refer to two records in the chain whose sequential number differs by one position under the same spare parts code; first, continuity verification is performed on adjacent records. Continuity verification includes type continuity verification, time continuity verification, and source continuity verification. Among them, type continuity verification is used to determine whether the type of the previous record and the type of the next record conform to the allowed order of the procurement progress chain, inventory change chain, or pending inspection chain; time continuity verification is used to determine whether the time of the next record is earlier than the time of the previous record; and source continuity verification is used to determine whether two records can establish a continuous source relationship through the same spare parts code and corresponding source identifier. When adjacent record types are sequentially from purchase request to supply confirmation, supply confirmation to shipment, shipment to warehouse arrival, or warehouse arrival to verification, the corresponding record pair is written to the purchase progress segment. When adjacent record types are sequentially from warehousing to outbound or from inventory correction to outbound, the corresponding record pair is written to the inventory change segment. When adjacent record types are from warehouse arrival to verification, the record pair is simultaneously written to the pending acceptance segment. During the segment formation process, adjacent records that can be continuously accepted are continuously extended backward until a type of non-acceptance, time point reversal, or source break occurs. The extension results are written as a purchase progress sequence and an inventory status sequence, respectively. The purchase progress sequence includes at least the purchase... The inventory status sequence includes at least the following: purchase start record, purchase end record, record order within the segment, and current purchase status. When a warehouse arrival record is found but no verification record is found, the warehouse arrival record is retained as the start of the pending inspection segment and the end is marked as empty. When an inbound record is found but no outbound record is found, the inbound record is retained as the start of the inventory change segment and the inventory status is marked as in stock and not consumed. When a purchase request record is found but no subsequent purchase record is found, the purchase request record is retained as the start of the purchase progress segment and the purchase status is marked as requested but not progressed. For S23, the purpose is to merge the procurement progress sequence and inventory status sequence formed under the same spare part code into the procurement progress table and inventory status table respectively, forming a unified table structure that S3 can directly read later; the input is the procurement progress sequence and inventory status sequence output by S22; during processing, the procurement progress sequence is first merged and written according to the spare part code. During merging, the original order of each procurement progress segment under the same spare part code is retained, and the segments are not reordered. The spare part code, the starting record of the procurement progress segment, the ending record of the procurement progress segment, the current procurement status, the segment length, and the source identifier are written into the procurement progress table; then, the inventory status sequence is merged and written according to the spare part code. During merging, the original order of each inventory change segment and the acceptance segment under the same spare part code is retained. The spare part code, the starting record of the inventory change segment, the ending record of the inventory change segment, the starting record of the acceptance segment, the ending record of the acceptance segment, the current inventory status, and the source identifier are written into the inventory status table. Among them, the records that have arrived at the warehouse but have not been verified are also used as the source basis for the records in transit and the records awaiting verification for subsequent steps to distinguish and read. After writing, the output includes a procurement schedule table containing spare part codes and procurement schedule sequences, and an inventory status table containing spare part codes and inventory status sequences, which can be read item by item in the current inventory record, in-transit record, and review record in S3. When a spare part code only forms a procurement schedule sequence but not an inventory status sequence, an empty sequence mark is written in the inventory status table. When a spare part code only forms an inventory status sequence but not a procurement schedule sequence, an empty sequence mark is written in the procurement schedule table, thus ensuring that the corresponding table entry always exists when reading by spare part code in the future. In practical applications: For example, when a spare part code for a certain lead screw assembly generates purchase requisition, supply confirmation, shipment, arrival, review, warehousing, and subsequent outbound records on the same day, these records are first sorted by recording time. Records at the same time are then expanded according to a fixed order: purchase requisition, supply confirmation, shipment, arrival, review, warehousing, outbound, and inventory, resulting in a spare part code's time-series record chain. Next, a succession check is performed on adjacent records within the chain. The continuous records from purchase requisition to review are identified as the procurement progress segment, the records from arrival to review are identified as the pending inspection segment, and the records from arrival to review are identified as the pending inspection segment. The process begins with identifying the outbound shipment as an inventory change segment, generating a procurement progress sequence and an inventory status sequence. Finally, the procurement progress sequence is written to the procurement progress table based on the spare part code, and the inventory status sequence is written to the inventory status table. After this processing, subsequent steps, when determining whether there is available inventory to accept a certain maintenance request, can directly read from the procurement progress table whether the spare part code is currently in the applied, confirmed, shipped, warehouse-delivered, or reviewed status, and from the inventory status table whether it has been put into storage or is still in the pending acceptance status. This avoids mixing records from different sources, inverting records at the same time, and misjudging the inventory status.

[0019] S3. Match the applicable equipment, compatible parts, warehouse verification items and batch compatibility items in the spare parts definition table with the current inventory records, in-transit records and verification records in the inventory status table one by one. Combine the maintenance demand time points corresponding to each spare parts code to perform dynamic modeling, form a fulfillment status sequence, and determine whether each fulfillment status sequence has available spare parts that have arrived in the warehouse, have been verified and are compatible, and generate an unfulfilled gap table. In this implementation, S3 is used to establish a verifiable correspondence between the spare parts definition table and the inventory status table, oriented towards the maintenance demand time point. It maps the applicable equipment, compatible parts, arrival verification items, and batch adaptation items under the same spare parts code to the current inventory records, in-transit records, and verification records, uniformly to each maintenance demand time point. Based on this, a candidate fulfillment diagram, fulfillment status sequence, and unfulfilled gap table are formed. Its working mechanism is as follows: First, the static definition information and dynamic inventory information are aligned according to the maintenance demand time point to obtain a candidate fulfillment group that can participate in the acceptance judgment. Then, starting from the maintenance demand time point, constrained acceptance path finding and conflict resolution are performed on the candidate fulfillment group to obtain a unique or parallel controlled acceptance path under each maintenance demand time point. Finally, the acceptance path is checked item by item against the maintenance demand time point to identify the sources of unfulfilled fulfillment in the four stages of arrival, verification, adaptation, and occupancy. This implementation process includes the following steps: For S31, the purpose is to expand the fields in the spare parts definition table and inventory status table that can affect the fulfillment judgment into comparable candidate fulfillment groups according to the maintenance demand time point, and delete invalid candidate corresponding edges through forward acceptance verification and reverse source verification to ensure that subsequent pathfinding is only carried out within the candidate range with continuous source, ordered time point and consistent location; the input quantities are the applicable equipment, matching location, warehouse verification item and batch matching item corresponding to the same spare parts code, as well as the current inventory record, in-transit record and verification record corresponding to the same spare parts code, and also include the maintenance demand time point sequence corresponding to the spare parts code; among them, the maintenance demand time point comes from the maintenance work order, planned replacement record or demand record derived from the replacement cycle. If the same spare parts code corresponds to multiple maintenance demand time points, they are sorted according to the order of demand occurrence. During processing, firstly, for each maintenance request point in time, all current inventory records, in-transit records, and verification records associated with the spare part code are read. Then, the applicable equipment is compared with the equipment requiring maintenance item by item, the matching part is compared with the part requiring maintenance item by item, the warehouse arrival verification item is compared with the completed verification items in the verification record by item, and the batch matching item is compared with the batch matching result by item. After that, a candidate fulfillment group is constructed for each maintenance request point in time. The candidate fulfillment group includes at least the spare part code, maintenance request point in time, candidate inventory source record, spare part arrival status, verification completion status, batch matching status, applicable equipment matching result, and matching part matching result. Among them, the spare part arrival status is determined by the record type. If there is a warehouse arrival record, it is recorded as "arrived". If there is only a shipment or confirmation record, it is recorded as "not arrived". The verification completion status is determined by whether there is a verification pass record that meets the warehouse arrival verification item. The batch matching status is determined by whether all batch matching items are matched. After constructing the candidate fulfillment groups, candidate corresponding edges are established for each candidate fulfillment group. The prerequisites for establishing edges are that they are for the same spare part code, the maintenance demand time is not earlier than the candidate inventory source record time, and the applicable equipment and the matching parts are both valid. Then, forward acceptance verification and reverse source verification are performed. Forward acceptance verification is used to check whether there is a time reversal or state reversal between the candidate inventory source record and the maintenance demand time. If the later time is earlier than the previous source record time, it is determined to be a time reversal and the corresponding candidate corresponding edge is deleted. Reverse source verification is used to check whether the candidate inventory source record can point back to the procurement progress. If the source record in the table or inventory status table cannot be pointed back, it is determined that the source is broken and the corresponding candidate edge is deleted. At the same time, if the applicable equipment is matched but the matching parts are inconsistent, the candidate fulfillment group is determined to be part mismatched and the corresponding candidate edge is deleted. After processing, the candidate fulfillment map is output. The candidate fulfillment map includes the maintenance demand time node, the candidate fulfillment group node and the candidate corresponding edge, and is written to the candidate fulfillment map cache table for S32 to read. When there are no candidate fulfillment groups under a certain maintenance demand time point, the maintenance demand time point node is retained and an empty candidate mark is written so that S33 can directly form the unfulfilled gap. For S32, the goal is to obtain the receiving path that satisfies the constraints of arrival, verification, adaptation, and occupancy for each maintenance demand time point from the candidate fulfillment diagram, and to obtain a stable fulfillment state sequence through multiple rounds of resolution; the input is the candidate fulfillment diagram output by S31; during processing, a path search space is established with each maintenance demand time point as the starting point and each candidate fulfillment group as the receiving node, and constraint pathfinding is performed sequentially for all candidate fulfillment groups under the same maintenance demand time point; constraint pathfinding adopts a fixed order comparison rule, first comparing the arrival at the warehouse first, then comparing the verification first, then comparing the batch adaptation first, and when the first three comparisons are the same, the minimum time point difference is compared first; where the time point difference is the absolute value of the difference between the maintenance demand time point and the candidate inventory source record time point, the smaller the difference, the higher the priority. After generating a set of candidate service paths for each maintenance request time point according to the above fixed order, the first and last consistency checks, path back-pointing checks, and conflict resolutions are performed on each of the multiple service paths corresponding to the same maintenance request time point: The first and last consistency check is used to check whether the starting maintenance request time point and the ending candidate inventory source record of the service path always maintain the same spare part code, the same applicable equipment range, and the same adapted part range; The path back-pointing check is used to check whether each candidate fulfillment group in the path can be back-pointed to the current inventory record, in-transit record, or review record in the inventory status table through the source record level by level; The conflict resolution is used to check whether the same available spare part is occupied by multiple maintenance request time points at the same time. If there is duplicate occupation, it is first retained according to the order of maintenance request time points, then retained according to the fixed priority order. If they are still tied, the earlier candidate inventory source record time point is retained. After completing one round of resolution, for each maintenance request point in time, only the current first path and its parallel valid paths are retained before proceeding to the next round of review. When the path length no longer shortens, the number of conflicting nodes no longer decreases, and the first path in the previous and next rounds remains consistent, it is determined that the receiving path corresponding to the maintenance request point in time has converged, and resolution stops. If the convergence condition is not met simultaneously even after reaching the preset maximum number of rounds, the current first path is retained as the receiving path for the maintenance request point in time. The preset maximum number of rounds is three to five rounds, derived from the rule constraint configuration. After processing, the fulfillment status sequence is output. The fulfillment status sequence includes at least the spare part code, maintenance request point in time, receiving path number, candidate inventory source record in the receiving path, arrival status, review completion status, batch adaptation status, and occupancy status, and is written into the fulfillment status sequence table for S33 to read. When a certain maintenance request point in time has a node in the candidate fulfillment graph but there is no valid receiving path after all resolutions, an empty path mark is written into the fulfillment status sequence for the maintenance request point in time. For S33, the purpose is to transform the acceptance results in the fulfillment status sequence into an unfulfilled gap table that can directly drive subsequent cause breakdown and procurement actions, clarifying the specific type and source of unfulfilled obligations at each maintenance demand point in time; the input is the fulfillment status sequence output by S32 and the corresponding maintenance demand point in time; during processing, the acceptance path in the fulfillment status sequence is read item by item according to the spare parts code and maintenance demand point in time, and the arrival verification, re-verification verification, adaptation verification and occupancy verification are performed sequentially for each acceptance path; the arrival verification is used to check whether there is an arrival record in the acceptance path, and if there is no arrival record, it is marked as an unfulfilled gap; the re-verification verification is performed on the premise that there is an arrival record, and if there is no re-verification pass record that meets the arrival re-verification item, it is marked as an unre-verified gap; Adaptation verification is performed only after the verification has been passed. If no batch adaptation result meets the batch adaptation criteria, it is marked as an adaptation failure gap. Occupancy verification is performed only after the item has arrived in the warehouse, has been verified, and the batch adaptation is successful. If the available spare part has been occupied by a previous maintenance request and the current maintenance request no longer retains the receiving path after conflict occupancy resolution, it is marked as an occupancy conflict gap. Gap determination is performed in the above fixed order. The first gap type that is established under the same maintenance request is taken as the main gap type for that maintenance request. If it is necessary to retain compound reasons, a secondary gap mark is appended to the main gap type and written into the extended field. After the judgment is completed, the spare parts code, maintenance request time, gap type, corresponding source record, corresponding acceptance path number, and gap formation time are written into the unfulfilled gap table. Among them, the corresponding source record is the most recent inventory source record or purchase source record that caused the current gap to be established. When the fulfillment status sequence writes an empty path mark for a certain maintenance request time, the maintenance request time is directly written into the unfulfilled gap. When the source record is missing, the source record field is written with an empty mark and the source missing identifier is registered at the same time for use when S4 performs reverse source verification. In practical applications: For example, a spindle assembly spare part code corresponds to two maintenance request times, with the first maintenance request time being earlier than the second. The inventory status table contains one record of shipped but not yet received, one record of received but awaiting verification, and one record of verified but batch adaptation failed. First, at both the first and second maintenance request times, the applicable equipment, adaptation location, arrival verification item, and batch adaptation item are expanded in the same position as these three types of records to construct candidate fulfillment groups. Candidate corresponding edges with equipment mismatch, inconsistent locations, or sources that cannot be referenced back are deleted. Then, constraint pathfinding is performed for each of the two maintenance request times, prioritizing the retention of the "received but awaiting verification" record for the first maintenance request time. The established acceptance path is recorded. If the second maintenance request still attempts to occupy the same available spare part, the acceptance path of the first maintenance request is retained in the conflict resolution process according to the order of the maintenance request times. Finally, the first maintenance request time is marked as an unverified gap because it has arrived at the warehouse but has not been verified. The second maintenance request time is marked as an occupied conflict gap because the available spare part has been occupied by the previous maintenance request time and cannot continue to be accepted. Both gap records are written into the unfulfilled gap table. Through this implementation process, subsequent steps can directly distinguish whether it is an arrival problem, a verification problem, an adaptation problem, or an occupation problem according to the unfulfilled gap table, thereby avoiding the confusion of all unfulfilled situations into a single shortage state.

[0020] S4. For each unfulfilled gap in the unfulfilled gap table, perform segmentation and splitting according to the order of the purchase application being generated but not confirmed, confirmed but not shipped, shipped but not delivered to the warehouse, delivered to the warehouse but not approved, and approved but batch mismatched, and generate a gap cause table and a warning result table. In this implementation, S4 is used to further decompose the gap results in the unfulfilled gap table into executable cause segments, and generate early warning results that can directly drive procurement actions and status updates based on the cause segments. Its mechanism is as follows: First, unfulfilled gaps under the same spare part code are re-aligned with preceding records such as procurement requests, shipments, arrivals, and reviews according to the maintenance demand time points, to obtain candidate cause segments corresponding to each gap; then, through multi-round consistency resolution under a fixed state order, a unique or controlled parallel target segment is converged from multiple candidate cause segments; finally, the impact range is expanded along the target segment, and the gap duration, the number of time points affecting maintenance demands, and the number of times the same type of gap recurs are statistically analyzed to form an early warning judgment sequence and output an early warning result table. This implementation process includes the following steps: For S41, the goal is to construct candidate gap segments for each unfulfilled gap that are continuous in origin, ordered in time, and have a consistent status, so that subsequent consistency resolution is based on a traceable cause chain. The inputs are each unfulfilled gap corresponding to the same spare part code in the unfulfilled gap table, as well as the purchase records, shipment records, arrival records, and review records corresponding to the spare part code in the purchase schedule table and inventory status table. Among them, the preceding purchase record is defined as the purchase record under the same spare part code whose record time is no later than the corresponding maintenance demand time and whose record time is closest to the corresponding maintenance demand time. If there are multiple parallel records, the record with the later status is selected as the preceding purchase record according to the fixed order of purchase application, supply confirmation, shipment, arrival, and review. During processing, first, perform a parallel expansion based on the maintenance request time, purchase record time, shipment record time, warehouse arrival record time, and review record time. Then, form a candidate segment chain with each unfulfilled gap and its preceding purchase record and subsequent status record. Next, calculate the segment cost group for each candidate segment chain. The segment cost group includes the time point acceptance difference, status acceptance difference, and record retracement difference. Among them, the time point acceptance difference is the difference between the maintenance request time and the candidate record time, expressed in absolute duration. The smaller the difference, the better. The status acceptance difference is the difference in position between the current unfulfilled gap status and the candidate record status in a fixed status chain. The fixed status chain is as follows: purchase application generated but not confirmed, confirmed but not shipped, shipped but not delivered to warehouse, delivered to warehouse but not approved, and approved but batch mismatched. The smaller the position difference, the better. The record back-index difference is the difference in back-index level between the gap source record and the previous purchase record. The minimum value is used for direct back-indexing, and the larger value is used for back-indexing across one or more intermediate records. Records that cannot be back-indexed are considered invalid. After completing the segmented cost group calculation, under the constraints of ensuring that the procurement record time is no later than the corresponding maintenance requirement time, the preceding and following states are not reversed, and the source records are referential, forward segment matching and reverse source verification are performed on each unfulfilled gap. Forward segment matching is used to search for candidate state records that satisfy the current gap state from the preceding procurement record along the fixed state chain. Reverse source verification is used to trace back from the gap source record to the preceding procurement record to verify the source closure relationship. For procurement records with a time later than the maintenance requirement time and candidate state positions earlier than the preceding state, the following conditions must be met. Candidate segments whose status or source records cannot be traced back to previous procurement records are not retained; after processing, a gap candidate segment table is output, which includes at least spare parts code, maintenance demand time point, candidate segment start record, candidate segment end record, segment cost group, and source retrieval result, and is written to the candidate segment cache table for S42 to read; when there are no candidate segments that meet the constraints for an unfulfilled gap, an empty accepting candidate segment is constructed with the gap source record corresponding to the unfulfilled gap itself, and a source breakage identifier is written; For S42, the goal is to remove candidate segments from the gap candidate segment table that have disordered state order, unclosed source beginnings and ends, or unstable iteration results, and converge to obtain the target segment that can be used as the basis for cause identification; the input is the gap candidate segment table output by S41; during processing, each candidate segment is first classified according to a fixed state order, which is still arranged in the following order: purchase application generated but not confirmed, confirmed but not shipped, shipped but not delivered, delivered but not approved, and approved but batch mismatched; then, multiple rounds of consistency resolution are performed on multiple candidate segments corresponding to the same unfulfilled gap; in each round of consistency resolution, the state order is first calculated. Consistency, source record closure, and adjacent time point convergence are evaluated. Among them, state order consistency is determined by whether each state record in the candidate segment progresses unidirectionally along a fixed state order. The highest consistency is achieved when all state records are consistent, and a reversal at any point results in a downgrade. Source record closure is determined by whether the starting and ending records of the candidate segment can be closed from beginning to end through the same spare part code and continuous source identifier. The highest consistency is achieved when both the beginning and end can be pointed back to each other and there are no breaks in the middle. Adjacent time point convergence is determined by the change in the time point difference between the current round's retention result and the previous round's retention result for the corresponding candidate segment. A change of zero indicates that the segment is stable, a decrease in the change indicates that the segment is converging, and an increase in the change indicates that the segment is unstable. Then, the segments are screened out one by one in a fixed comparison order, prioritizing consistency of state order, followed by closure of source records, and then convergence of adjacent time points. For the same unfulfilled gap, only the target segments with consistent state order, closure of the beginning and end of the source records, and no change in the retention results between adjacent rounds are retained. When multiple candidate segments are still tied in the three comparisons, they are further eliminated in parallel in the order of smaller time point acceptance difference in the segment cost group, smaller state acceptance difference, and smaller record retracement difference. If they are still tied, the candidate segments with earlier record time points are retained. The stopping condition for multi-round consistency resolution is: the target segment number of the same unfulfilled gap is consistent in two consecutive rounds, and the start and end records of the corresponding segment no longer change; if the stopping condition is not met after reaching the preset maximum number of rounds, the first candidate segment of the current round is retained as the target segment. The preset maximum number of rounds is given by the rule constraint configuration, ranging from three to five rounds; after processing, a gap cause table is generated. The gap cause table includes at least the spare part code, maintenance demand time, target segment, cause type, target segment start record, target segment end record, and segment retention basis, and is written into the gap cause table for S43 to read; when the target segment is directly converted from an empty accepting candidate segment, the source breakage cause identifier is written in the cause type field; For S43, the purpose is to convert the target segments in the gap cause table into early warning results for subsequent procurement actions, and to clarify the impact range of each type of cause segment on the timing of subsequent maintenance needs; the input is the gap cause table output by S42; during processing, each target segment is read according to the same spare part code, and forward impact expansion is performed on each target segment. The starting point of the forward impact expansion is the maintenance need timing corresponding to the current target segment, and the ending point is the last maintenance need timing before the first occurrence of subsequent maintenance needs for status recovery, source replenishment, or adaptation under the same spare part code; within this expansion range, the gap duration, the number of maintenance need timings affected, and the number of times the same type of gap recurs are calculated. Among them, the gap duration is the duration between the maintenance need timing at the starting point of the current target segment and the maintenance need timing at the end point of the expansion, the number of maintenance need timings affected is the number of maintenance need timings affected by the same target segment within this expansion range, and the number of times the same type of gap recurs is the number of times the same cause type of target segment appears under this spare part code; The above three results are then combined into an early warning judgment sequence, and cross-checking is performed on each early warning judgment sequence. The cross-checking adopts the correspondence rule between cause type and status chain position: if the target segment terminates at the state of "purchase application generated but not confirmed", it is classified as "pending confirmation early warning"; if it terminates at the state of "confirmed but not shipped", it is classified as "pending shipment early warning"; if it terminates at the state of "shipped but not delivered", it is classified as "pending delivery early warning"; if it terminates at the state of "delivered but not approved", it is classified as "pending review early warning"; if it terminates at the state of "approved but batch incompatible", it is classified as "incompatibility failure early warning". During cross-checking, the cause type, target segment endpoint state and forward impact expansion range in the early warning judgment sequence are checked for consistency. If the three are consistent, the corresponding early warning type is directly generated. If the cause type and endpoint state are inconsistent, the early warning type corresponding to the endpoint state is taken as the main type, and the cause deviation information is written in the extended field. After processing, the spare part code, maintenance demand time point, cause segment, warning type, gap duration, number of maintenance demand time points, and number of times the same gap recurs are written into the warning result table and read by S5. When the forward influence expansion range corresponding to a certain target segment only covers the current maintenance demand time point, it is still written into the warning result table, but a "1" is written into the number segment of the maintenance demand time point to distinguish between single-point warnings and continuous warnings in the future. In practical applications: For example, if a servo drive board spare part code has three consecutive maintenance demand points resulting in unfulfilled gaps (confirmed but not shipped, shipped but not delivered, and shipped but not delivered), then firstly, these three unfulfilled gaps are expanded according to the maintenance demand point in relation to the corresponding purchase requisition records, supply confirmation records, shipment records, and delivery records. The timing difference, status difference, and record retrieval difference of each candidate segment are calculated to screen out candidate gap segments that meet the condition that the purchase record time is no later than the maintenance demand point and the source can be retrievald. Then, multiple rounds of consistency resolution are performed on the multiple candidate segments corresponding to the three maintenance demand points. If the second and third maintenance demand points are both stably retained as the target segment of "shipped but not delivered," then... If a segment is identified, the cause type is entered into the gap cause table. Finally, the impact range is expanded along these two target segments, and the consecutive occurrence of similar gaps at subsequent maintenance demand points is statistically analyzed. If two target segments consecutively cover the subsequent two maintenance demand points, a waiting warehouse warning is generated, and the corresponding gap duration, number of maintenance demand points affected, and number of times similar gaps recur are entered into the warning result table. Through this implementation process, subsequent procurement actions are no longer based solely on a single gap type, but can be differentiated based on the formation chain and impact range of the cause segments to determine whether to expedite delivery, insert orders, or supplementary procurement, thereby avoiding the mixing of gaps from different sources but with similar surface conditions. S5. Based on the cause type in the gap cause table, the corresponding maintenance demand time point, and the corresponding procurement record in the procurement schedule table, generate supplementary procurement results, order insertion results, delivery reminder results, or alternative procurement results for each unfulfilled gap. Write the generated results into the inventory status table according to the spare parts code and write-back time to perform dynamic modeling and update of the corresponding fulfillment status sequence, and obtain the updated inventory control results. In this implementation, S5 is used to convert the cause types in the gap cause table into executable procurement actions, and write the procurement actions back to the inventory status table and the procurement schedule table, forming an updated result for the next round of fulfillment status modeling. Its mechanism is as follows: First, each unfulfilled gap is matched with a procurement record that can accommodate the gap according to spare parts code and maintenance demand time point, forming procurement action candidates; then, the procurement action candidates are sequentially screened based on cause type, time point difference, and previous procurement acceptance relationship to determine the procurement actions that should be retained under each unfulfilled gap; finally, the retained procurement actions are written back to the inventory status table according to a unified write-back rule, and the procurement schedule record and available inventory record are simultaneously rewritten, enabling subsequent steps to re-execute the fulfillment status sequence modeling based on the updated status. This implementation process includes the following steps: For S51, the purpose is to generate procurement action candidates with clear sources, comparable timing, and selectable actions for each unfulfilled gap, providing a unified input for subsequent action screening. The input includes each unfulfilled gap in the gap cause table, the corresponding procurement record in the procurement schedule table, and the supply method and batch matching item in the spare parts definition table. The corresponding procurement record is defined as a procurement record under the same spare parts code whose record time is no later than the maintenance demand time and whose source chain can point back to the unfulfilled gap. If there are multiple procurement records that meet the conditions, the one whose record time is closest to the maintenance demand time is selected first. Then, in the case of ties, they are retained in a fixed order of priority: existing confirmation time, existing shipment time, and existing expected arrival time. During processing, first, each unfulfilled gap is matched with the corresponding procurement record according to the spare part code, repair request time, and cause type. Then, the repair request time is compared item by item with the application time, confirmation time, shipment time, and expected arrival time in the corresponding procurement record to form a time comparison result. Among them, the application time, confirmation time, shipment time, and expected arrival time are all taken from the currently valid record values ​​in the procurement schedule. If the expected arrival time is missing, it is obtained by adding the standard transportation time corresponding to the supply method to the shipment time. The input time is derived from the supply method rules in the preset configuration table; then, procurement action candidates are generated according to the reason type: when the reason type is "Pending Confirmation Warning", supplementary procurement candidate and order insertion candidate are generated; when the reason type is "Pending Shipment Warning", delivery reminder candidate and order insertion candidate are generated; when the reason type is "Pending Warehouse Arrival Warning", delivery reminder candidate and alternative procurement candidate are generated; when the reason type is "Pending Review Warning", delivery reminder candidate and supplementary procurement candidate are generated; when the reason type is "Adaptation Failure Warning", alternative procurement candidate and supplementary procurement candidate are generated. Alternative procurement candidates are extracted from other spare parts codes in the spare parts definition table that are applicable to the same equipment, the same compatible part, and whose batch compatibility can be satisfied. During extraction, priority is given to those with the same model and specifications, and those with the same supply method. After processing, a procurement action candidate table is output. The procurement action candidate table includes at least the spare parts code, the time point of maintenance requirement, the cause type, the corresponding procurement record, the action type, the time point comparison result, and the source gap record. It is also written to the procurement action candidate cache table for S52 to read. When there is no corresponding procurement record for a certain unfulfilled gap, a supplementary procurement candidate is directly generated, and a blank mark is written in the field of the corresponding procurement record. For S52, the goal is to filter out procurement action results from the procurement action candidate table that can truly alleviate the current unfulfilled gap and will not cause duplicate occupation of previously reserved procurement actions. The input is the procurement action candidate table output by S51 and the results of previously reserved procurement actions. During processing, all procurement action candidates are read for the same unfulfilled gap, and the time difference and previous procurement acceptance relationship are calculated for each procurement action candidate. The time difference is the difference between the expected arrival time and the maintenance demand time. If the expected arrival time is earlier than the maintenance demand time, it is recorded as early acceptance, and if it is later than the maintenance demand time, it is recorded as delayed acceptance. The previous procurement acceptance relationship is used to determine whether the current procurement action candidate and the previously reserved procurement action point to the same procurement resource, the same expected arrival batch, or the same alternative procurement resource. If so, it is recorded as having an acceptance relationship. Then, a priority screening is performed based on cause type, time difference, and prior procurement acceptance relationship. The screening order is as follows: first, compare the action adaptation order corresponding to the cause type; second, compare whether the time difference allows for advance acceptance; and finally, compare whether there is duplication with previously retained procurement actions. The action adaptation order is determined by rule constraints: pending confirmation warnings prioritize re-procurement candidates; pending shipment warnings prioritize expedited delivery candidates; pending arrival warnings prioritize expedited delivery candidates; pending review warnings prioritize re-procurement candidates; and adaptation failure warnings prioritize alternative procurement candidates. When multiple procurement action candidates correspond to the same unfulfilled gap, priority is given to procurement action candidates that can ensure the expected arrival time is earlier than the corresponding maintenance requirement time and do not overlap with previously reserved procurement actions. If multiple candidates meet this condition, they are further screened in a fixed order: earlier expected arrival time, earlier source gap record time, and earlier action type. If none of the candidates can ensure the expected arrival time is earlier than the maintenance requirement time, the procurement action candidate with the expected arrival time closest to the maintenance requirement time and which does not overlap with the maintenance requirement time is retained. Duplicate acceptance is defined as the same procurement resource, the same expected delivery batch, or the same alternative resource being occupied by two or more procurement actions simultaneously. After processing, a procurement action result table is generated, which includes at least the spare parts code, the time of maintenance request, the type of retained action, the basis for retention, the corresponding procurement record, and the expected write-back status. This information is then written into the procurement action result table for S53 to read. When all procurement action candidates under a certain unfulfilled gap are duplicated, only the first candidate is retained and a duplicate acceptance flag is written for subsequent manual review. For S53, the purpose is to translate the procurement actions in the procurement action result table into status update results in the inventory status table and procurement progress table, and form updated inventory control results that can be directly read by subsequent dynamic modeling. The inputs are the procurement action result table, current inventory status table, and procurement progress table output by S52. During processing, the supplementary procurement results, insertion results, expedited delivery results, or alternative procurement results in the procurement action result table are written in the order of execution according to the spare parts code and write-back time. The write-back time is taken as the time when the procurement action is generated and completed. Then, the procurement progress record and available inventory record of the corresponding spare parts code are updated synchronously according to the action type. Among them, the supplementary procurement result is written into a new procurement application record and the procurement progress status is updated to "supplemented and awaiting confirmation". The insertion result is written into a new priority procurement identifier and the procurement progress status is updated to "inserted and awaiting confirmation". The expedited delivery result is written into an expedited delivery identifier and the procurement progress status is updated to "expedited and awaiting shipment" or "expedited and awaiting arrival at warehouse". The alternative procurement result is written into the alternative spare parts code and alternative source record and the available inventory record is updated to "alternative available status". During synchronous updates, the procurement schedule is rewritten first, followed by the inventory status table. Finally, the availability of new available inventory is recalculated for the same spare part code. The recalculation rule is to read the updated procurement schedule record, the current inventory record, and the alternative available status record, and verify, review, and adapt each item according to the maintenance requirement time. After processing, the updated inventory control result is output. The updated inventory control result includes at least the spare part code, the updated procurement schedule status, the updated available inventory status, and the corresponding write-back time, and is used for the next round of status sequence modeling. When a procurement action result lacks a corresponding spare part code or corresponding procurement record during the write-back process, the status update is not performed. Instead, the procurement action result is written to the abnormal action table, and the original status is retained in the updated inventory control result. In practical applications: For example, if a spare part code for a certain ball screw assembly corresponds to an unfulfilled gap that is awaiting warehouse arrival, and the procurement schedule contains a shipped record with an estimated arrival time one day later than the maintenance requirement, while the spare part definition table contains a substitute spare part code for the same applicable equipment and compatible part, then first, the unfulfilled gap is matched with the shipped record to form a expedited delivery candidate, and a substitute procurement candidate is formed from the substitute spare part code. Then, the time difference between the two candidates is compared with the preceding procurement succession relationship. If, after expediting, the estimated arrival time is still later than the maintenance requirement, and the substitute procurement can be directly formed... If the inventory becomes available for acceptance, alternative procurement candidates are prioritized and procurement action results are generated. Finally, the alternative procurement results are written to the inventory status table according to the spare parts code and write-back time. At the same time, the original procurement progress record is retained as "shipped and awaiting arrival at the warehouse," and the available inventory record corresponding to the alternative spare parts code is updated to the alternative available status. The updated inventory control results are then output. Through this implementation process, the subsequent dynamic modeling no longer reads the original unfulfilled state, but rather the procurement progress status and available inventory status after the procurement action has been corrected. This allows for a continuous reflection of the actual inventory acceptance capacity after procurement disposal.

[0021] Furthermore, the present invention also includes an intelligent inventory management system for machined spare parts, the system comprising a spare parts information management module, an inventory monitoring module, a demand forecasting module, an early warning module, and a procurement management module: The spare parts information management module is used to obtain the spare parts code, model specifications, applicable equipment, compatible parts, supply method, warehouse verification items and batch compatibility items of the spare parts to be managed. It performs fixed-length filing for each field corresponding to the same spare parts code and generates a spare parts definition table. The inventory monitoring module is used to read the inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipment records, arrival records and review records corresponding to each spare part code. It performs serialization and sorting of records under the same spare part code according to the order of the record time to generate a purchase progress table and an inventory status table. The demand forecasting module is used to match the applicable equipment, compatible parts, warehouse verification items and batch compatibility items in the spare parts definition table with the current inventory records, in-transit records and verification records in the inventory status table. It performs dynamic modeling based on the maintenance demand time points corresponding to each spare parts code to form a fulfillment status sequence. It then determines whether each fulfillment status sequence has available spare parts that have arrived in the warehouse, have been verified and are compatible, and generates an unfulfilled gap table. The early warning module is used to segment and break down each unfulfilled gap in the unfulfilled gap table according to the order of the purchase application status: generated but not confirmed, confirmed but not shipped, shipped but not delivered to the warehouse, delivered to the warehouse but not approved, and approved but batch mismatched. It generates a gap cause table and an early warning result table. The procurement management module is used to generate supplementary procurement results, order insertion results, expedited delivery results, or alternative procurement results for each unfulfilled gap based on the cause type in the gap cause table, the corresponding maintenance demand time, and the corresponding procurement record in the procurement schedule table. The generated results are then written into the inventory status table according to the spare parts code and write-back time to perform dynamic modeling and updates on the corresponding fulfillment status sequence, resulting in updated inventory control results.

[0022] Working Principle: This solution first clarifies the basic information of each spare part, including spare part code, applicable equipment, compatible location, supply method, arrival verification items, and batch compatibility items, forming a unified spare part definition. Then, it strings together the process records of warehousing, outbound, purchase requisition, shipment, arrival at warehouse, and verification according to time, obtaining the procurement progress and inventory status. Based on this, around each maintenance demand point in time, it checks item by item whether the spare part has arrived, whether it has passed verification, whether it is batch compatible, and whether it has been used by previous demands, determining whether a usable spare part can truly be obtained at each maintenance demand point in time, thus forming a... The system first identifies the fulfillment status sequence and then the unfulfilled gaps. Next, it traces these gaps back to the procurement chain, distinguishing whether they are caused by non-confirmation, non-shipment, non-delivery, non-verification, or compatibility failure, and generates corresponding alerts accordingly. Finally, based on the cause of the gap, it selects to replenish stock, insert orders, expedite delivery, or substitute procurement, and writes the procurement actions back to the inventory status so the system can proceed to the next round of update judgment. Overall, this is a complete chain: first defining spare parts, then organizing the process, then determining whether fulfillment is possible, then tracing the cause, and finally executing procurement corrections. Each step is interconnected, with the output of the previous step directly becoming the input of the next. For example, in a machining workshop, a CNC machining center's spindle assembly is scheduled to be replaced on Wednesday. The system first checks the corresponding spare part code, compatible part, and verification requirements for the spindle assembly. Then, it checks the current inventory and procurement progress. It finds that although there is no readily available stock in the warehouse, there is a batch of similar spare parts that have already been shipped. The system then continues to determine whether this batch of spare parts can arrive at the warehouse before Wednesday, whether verification can be completed after arrival, and whether the batch matches after verification. If it finds that the expected arrival time is later than Wednesday, it will not directly treat this batch of spare parts in transit as guaranteed. Instead, it will identify this situation as an unfulfilled gap and further determine that it is due to being shipped but not yet arrived at the warehouse. Based on this, the system will issue a warning for the parts awaiting arrival at the warehouse and decide, based on the existing procurement records, whether to expedite the original order, change to a supplementary order, or call for another alternative spare part. In this way, managers no longer see simply how much inventory they have, but whether there are parts available for replacement during this maintenance, where the gap is at, and how to fill it in the next step, which is more in line with the actual situation.

[0023] The above description is merely a preferred embodiment of the present invention and is not intended to limit the present invention. Any modifications, equivalent substitutions, improvements, etc., made within the spirit and principles of the present invention should be included within the protection scope of the present invention.

Claims

1. A method for intelligent inventory management of machined spare parts, characterized in that, include: S1. Obtain the spare part code, model specifications, applicable equipment, compatible parts, supply method, warehouse verification items and batch compatibility items of the spare parts to be managed. Perform fixed-length filing for each field corresponding to the same spare part code and generate a spare part definition table. S2. Read the inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipping records, arrival records and review records corresponding to each spare part code, and perform serialization and organization of each record under the same spare part code according to the record time sequence to generate a purchase progress table and an inventory status table. S3. Match the applicable equipment, compatible parts, warehouse verification items and batch compatibility items in the spare parts definition table with the current inventory records, in-transit records and verification records in the inventory status table one by one. Combine the maintenance demand time points corresponding to each spare parts code to perform dynamic modeling, form a fulfillment status sequence, and determine whether each fulfillment status sequence has available spare parts that have arrived in the warehouse, have been verified and are compatible, and generate an unfulfilled gap table. S4. For each unfulfilled gap in the unfulfilled gap table, perform segmentation and splitting according to the order of the purchase application status: generated but not confirmed, confirmed but not shipped, shipped but not delivered to the warehouse, delivered to the warehouse but not approved, and approved but batch mismatched, and generate a gap cause table and a warning result table.

2. The intelligent inventory management method for machined spare parts according to claim 1, characterized in that: Also includes: S5. Based on the cause type in the gap cause table, the corresponding maintenance demand time point, and the corresponding procurement record in the procurement schedule table, generate supplementary procurement results, order insertion results, delivery reminder results, or alternative procurement results for each unfulfilled gap. Write the generated results into the inventory status table according to the spare parts code and write-back time to perform dynamic modeling and update of the corresponding fulfillment status sequence, and obtain the updated inventory control results.

3. The intelligent inventory management method for machined spare parts according to claim 2, characterized in that: S1 includes: S11. For the same spare part code, perform fixed-length partition expansion according to the predetermined field order for the model specifications, applicable equipment, matching parts, supply methods, warehouse verification items and batch matching items, write field values ​​and empty space markers for the field positions corresponding to each field, and generate spare part field position sequence. S12. Perform sequential pairing of applicable equipment and compatible parts in each spare parts field sequence, and perform corresponding linking of supply method with warehouse verification item and batch compatibility item to generate spare parts acceptance relationship sequence. S13. Merge and write each spare part acceptance relationship sequence according to the spare part code, and output a spare part definition table containing the spare part code, field bit sequence and spare part acceptance relationship sequence.

4. The intelligent inventory management method for machined spare parts according to claim 3, characterized in that: S2 includes: S21. For the same spare part code, the inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipment records, arrival records and review records are uniformly sorted according to the order of recording time. For records with the same recording time, the records are sequentially expanded according to the fixed order of purchase requisition, supply confirmation, shipment, arrival, review, inbound, outbound and inventory, to generate a spare part sequence record chain. S22. Perform a succession check on adjacent records in each spare parts time sequence record chain, identify the procurement progress segment between the purchase application and the review record, the inventory change segment between the warehousing and outbound records, and the pending acceptance segment between the arrival record and the review record, and generate a procurement progress sequence and an inventory status sequence. S23. Merge and write each procurement schedule sequence and each inventory status sequence according to spare parts code, and output a procurement schedule table and an inventory status table containing spare parts code, procurement schedule sequence and inventory status sequence.

5. The intelligent inventory management method for machined spare parts according to claim 4, characterized in that: S3 includes: S31. For the same spare part code, the applicable equipment, matching parts, warehouse verification items and batch matching items are expanded in the same position with the current inventory record, in-transit record and verification record according to the maintenance demand time point. For each maintenance demand time point, a candidate fulfillment group is constructed consisting of spare part arrival status, verification completion status and batch matching status. For each candidate fulfillment group, forward acceptance verification and reverse source verification are performed. Candidate corresponding edges with source break, time point reversal and part mismatch are deleted. The candidate fulfillment diagram is output. S32. Starting from the maintenance demand time point in each candidate fulfillment diagram and taking each candidate fulfillment group as the receiving node, perform constraint pathfinding in a fixed order of priority for already arrived at warehouse, priority for already reviewed, priority for batch adaptation, and priority for minimum time point difference. For multiple receiving paths corresponding to the same maintenance demand time point, perform first-to-last consistency check, path back-pointing check, and conflict occupancy resolution one by one. After each round of resolution, only retain the receiving paths that satisfy the conditions that the path length no longer shortens, the number of conflict nodes no longer decreases, and the first and second paths of the two rounds remain consistent, and output the fulfillment status sequence.

6. The intelligent inventory management method for machined spare parts according to claim 5, characterized in that: S3 also includes: S33. Perform a step-by-step comparison between each acceptance path in the fulfillment status sequence and the corresponding maintenance demand time point. For cases where there is no record of arrival at the warehouse, arrival at the warehouse but no record of verification approval, verification approval but no batch adaptation result, and the same available spare part cannot be accepted after being occupied by the previous maintenance demand time point, mark them as unfulfilled gaps, unverified gaps, adaptation failure gaps, and occupied conflict gaps respectively. Write them into the unfulfilled gap table according to spare part code, maintenance demand time point, gap type and corresponding source record.

7. The intelligent inventory management method for machined spare parts according to claim 6, characterized in that: S4 includes: S41. For each unfulfilled gap corresponding to the same spare part code in the unfulfilled gap table, perform positional expansion according to the maintenance demand time point, purchase record time point, shipment record time point, warehouse arrival record time point, and review record time point. Construct segmented cost groups based on the time point acceptance difference, status acceptance difference, and record back-pointing difference between the gap source record and the preceding purchase record. Under the constraints of ensuring that the purchase record time point is not later than the corresponding maintenance demand time point, the preceding and following states are not reversed, and the source record can be back-pointed, perform forward segment matching and reverse source verification for each unfulfilled gap, and output a gap candidate segment table.

8. The intelligent inventory management method for machined spare parts according to claim 7, characterized in that: S4 also includes: S42. Perform multiple rounds of consistency resolution on each candidate segment in the gap candidate segmentation table according to the fixed order of procurement application generated but not confirmed, confirmed but not shipped, shipped but not delivered to the warehouse, delivered to the warehouse but not approved, and approved but batch mismatched. For the same unfulfilled gap, compare the consistency of the status order, the closure of the source record, and the convergence of adjacent time points for each candidate segment. Only retain the target segment with consistent status order, closure of the source record at the beginning and end, and no change in the retention results of adjacent two rounds. Generate a gap cause table. S43. Based on the target segments in the gap cause table, perform forward impact expansion on each unfulfilled gap under the same spare part code. Build a warning judgment sequence by combining the gap duration length, the number of times the maintenance demand is affected, and the number of times the same type of gap recurs, corresponding to the target segment. Perform cross-checking on each warning judgment sequence to distinguish between warnings pending confirmation, warnings pending shipment, warnings pending arrival at the warehouse, warnings pending review, and adaptation failure warnings. Write the warning results in the warning result table according to spare part code, maintenance demand time, cause segment, and warning type.

9. The intelligent inventory management method for machined spare parts according to claim 8, characterized in that: S5 includes: S51. For each unfulfilled gap in the gap cause table, perform a corresponding mapping with the corresponding procurement record in the procurement schedule table according to the spare parts code, maintenance demand time and cause type. Compare the maintenance demand time with the application time, confirmation time, shipment time and expected arrival time in the corresponding procurement record item by item to generate a procurement action candidate table containing supplementary procurement candidate, order insertion candidate, expedited delivery candidate and alternative procurement candidate. S52. Perform sequential screening on each procurement action candidate in the procurement action candidate table according to the cause type, time difference, and previous procurement relationship. When multiple procurement action candidates correspond to the same unfulfilled gap, prioritize the procurement action candidates that can make the expected arrival time in the warehouse earlier than the corresponding maintenance demand time and do not overlap with the previously retained procurement actions, and generate a procurement action result table. S53. Write the supplementary procurement results, order insertion results, delivery reminder results, or alternative procurement results from the procurement action results table into the inventory status table according to the spare parts code and write-back time. Perform synchronous updates on the procurement progress record and available inventory record for the corresponding spare parts code, and output the updated inventory control results.

10. A machined spare parts intelligent inventory management system, used to implement the machined spare parts intelligent inventory management method according to any one of claims 1-9, the system comprising a spare parts information management module, an inventory monitoring module, a demand forecasting module, an early warning module, and a procurement management module, characterized in that: The spare parts information management module is used to obtain the spare parts code, model specifications, applicable equipment, compatible parts, supply method, warehouse verification items and batch compatibility items of the spare parts to be managed. It performs fixed-length filing for each field corresponding to the same spare parts code and generates a spare parts definition table. The inventory monitoring module is used to read the inbound records, outbound records, inventory records, purchase requisition records, supply confirmation records, shipment records, arrival records and review records corresponding to each spare part code. It performs serialization and sorting of records under the same spare part code according to the order of the record time to generate a purchase progress table and an inventory status table. The demand forecasting module is used to match the applicable equipment, compatible parts, warehouse verification items and batch compatibility items in the spare parts definition table with the current inventory records, in-transit records and verification records in the inventory status table. It performs dynamic modeling based on the maintenance demand time points corresponding to each spare parts code to form a fulfillment status sequence. It then determines whether each fulfillment status sequence has available spare parts that have arrived in the warehouse, have been verified and are compatible, and generates an unfulfilled gap table. The early warning module is used to segment and break down each unfulfilled gap in the unfulfilled gap table according to the order of the purchase application status: generated but not confirmed, confirmed but not shipped, shipped but not delivered to the warehouse, delivered to the warehouse but not approved, and approved but batch mismatched. It generates a gap cause table and an early warning result table. The procurement management module is used to generate supplementary procurement results, order insertion results, expedited delivery results, or alternative procurement results for each unfulfilled gap based on the cause type in the gap cause table, the corresponding maintenance demand time, and the corresponding procurement record in the procurement schedule table. The generated results are then written into the inventory status table according to the spare parts code and write-back time to perform dynamic modeling and updates on the corresponding fulfillment status sequence, resulting in updated inventory control results.

Images