Material state management and monitoring method and system based on manufacturing life cycle

Abstract

The invention discloses a material state management and monitoring method and system based on a manufacturing life cycle, and relates to the technical field of intelligent manufacturing. The method comprises the steps that a material state model is established based on a manufacturing life cycle and comprises state codes, and the state codes are used for representing state stages and state attributes of materials; key business events of materials of multiple business systems are obtained, business data of all the materials are obtained through cross-system synchronous analysis, state transition is executed in combination with a preset state transition rule, and a transition path is generated; state codes, service data and migration paths of all the materials are presented through a visual carrier, and the visual carrier comprises a multi-dimensional retrieval entry; and identifying the abnormal material based on the state transition rule, and generating an early warning notification. Through adoption of the method and the device, unification of material data and states of a plurality of business systems in a manufacturing life cycle is realized, consistency and real-time performance of material state information are ensured, and meanwhile, full-process visual monitoring and abnormal accurate identification of the material states are achieved.

Description

Technical Field

[0001] This application relates to the field of intelligent manufacturing technology, specifically to a method and system for material status management and monitoring based on the manufacturing lifecycle. Background Technology

[0002] In modern manufacturing, material usage spans multiple stages, from sales order initiation, procurement, warehousing, production and processing, quality inspection, inventory movement, finished goods warehousing, and shipment. Enterprises commonly deploy ERP systems for planning management, MES systems for production process control, and WMS systems for warehouse management. However, the data between these mainstream systems is currently fragmented, lacking a unified material status model that spans the entire manufacturing lifecycle.

[0003] The problem is particularly prominent in the following scenarios: the same material has multiple status descriptions in multiple systems, resulting in inconsistent information; it is impossible to grasp the current stage of a batch of materials in real time; when encountering quality problems or order abnormalities, it is difficult to quickly trace the material flow path; and there is a lack of early warning mechanisms for the efficiency of critical material usage and the risk of stagnation.

[0004] Therefore, there is an urgent need for a method that can break down data barriers between multiple systems, using the manufacturing lifecycle as the main thread, to achieve unified modeling, real-time monitoring, and intelligent analysis of material status. Summary of the Invention

[0005] This application provides a material status management and monitoring method and system based on the manufacturing lifecycle, which is used to solve the problem that data between mainstream systems is relatively fragmented and cannot run through the entire manufacturing lifecycle.

[0006] Firstly, this application provides a method for material status management and monitoring based on the manufacturing lifecycle, the method comprising: A material state model is established based on the manufacturing life cycle. The material state model includes a state code, which is used to characterize the state stage and state attributes of the material. The system acquires key business events of materials from multiple business systems, obtains business data of each material through cross-system synchronous parsing, and performs state migration in combination with preset state migration rules to generate migration paths. The status codes, business data, and migration paths of each material are presented through a visual medium, which includes a multi-dimensional search entry for querying status codes, business data, and migration paths. Abnormal materials are identified based on state transition rules, and early warning notifications are generated.

[0007] By adopting the above technical solutions, the material data and status of multiple business systems throughout the manufacturing lifecycle are unified, ensuring the consistency and real-time nature of material status information. At the same time, the full-process visual monitoring and accurate identification of anomalies in material status are achieved, effectively solving the problems of inconsistent material status descriptions, difficulty in tracing flow trajectories, and difficulty in early warning of abnormal risks in existing technologies.

[0008] In a specific feasible implementation, the status stages include pending procurement, procured, pending warehousing, warehousing, pending material requisition, material requisition in progress, production in progress, pending quality inspection, qualified warehousing, pending shipment, and shipped. Status attributes include available, unavailable, and locked; Business data includes material number, order number, supplier data, and customer data; The migration path includes the duration of material stay in each state stage, as well as the status codes and changes in business data during the state migration.

[0009] By adopting the above technical solutions, the specific composition of the material's entire process status stages, core attributes, key business data, and migration paths has been clarified, making the description of the material status model more standardized and the data more complete. This improves the accuracy of material status identification and the comprehensiveness of flow trajectory tracing, providing a clear data foundation for subsequent status migration and anomaly identification.

[0010] In a specific feasible implementation, state transition is performed in conjunction with preset state transition rules, and a transition path is generated, including: Receive business data and filter out the target triggering conditions to be activated from the set of triggering conditions; Based on the original state stage of the target material and the activated target triggering conditions, locate the next jump state stage as the migration target. Update the status code of the target material to a new code that represents the migration target, and generate a migration record. The migration record includes at least the original state stage, the event fingerprint of the target triggering condition, the migration target, the timestamp, and a summary of the original business data that triggered the migration. Migration paths are dynamically constructed based on migration records organized by time sequence.

[0011] By adopting the above technical solutions, the triggering logic and execution process of state transition are refined. Complete transition records are generated with the help of event fingerprints, timestamps and other information, ensuring the accuracy and verifiability of state transition. The dynamically constructed transition path can completely restore the flow trajectory of materials in the state space, further enhancing the traceability of material status.

[0012] In one specific feasible implementation, the method for identifying abnormal materials includes: By comparing the dwell time with the threshold duration of the corresponding stage in the state transition rule, abnormal dwell times can be identified. By comparing the migration path with the migration order of the corresponding stages in the state transition rules, jump anomalies can be identified. Based on the identification results of abnormal stay or abnormal jump, an early warning notification is generated.

[0013] By adopting the above technical solution, a dual anomaly identification mechanism based on dwell time and migration sequence has been established, which can accurately locate materials with abnormal dwelling and abnormal transfer, realize the timely detection of abnormal problems, and avoid risks such as production delays and inventory backlog caused by material flow stagnation or illegal transfer.

[0014] In one specific feasible implementation, the method further includes: Match the anomaly type and associated context in the early warning notification with the case handling mapping relationship in the preset rule base; Based on the matching results, a handling suggestion is generated and attached to the early warning notification output.

[0015] By adopting the above technical solution, intelligent matching and output of abnormal handling suggestions are realized based on the preset rule base, providing targeted solutions for staff, significantly shortening the decision-making cycle for abnormal handling, improving the efficiency of abnormal handling, and reducing the impact of material abnormalities on the production process.

[0016] In a specific feasible implementation, the method of presentation via a visual medium includes: Based on the status codes and migration paths of each material, statistical charts reflecting the distribution of each material in each state stage are generated. Based on the status code of a single material, its associated business data, and its complete migration path, a lifecycle flow map of the target material is generated. It receives query conditions based on status codes, business data, and migration paths, or any field or combination of fields, and returns statistical charts and lifecycle flow maps of the matching materials.

[0017] By adopting the above technical solutions, material status information is presented intuitively in the form of statistical charts and life cycle flow maps, supporting multi-dimensional combined queries. This allows users to quickly grasp the distribution of materials in each stage of the process and the complete flow trajectory of a single material, improving the convenience and traceability of material status monitoring and adapting to monitoring needs in different scenarios.

[0018] In a specific feasible implementation, the methods for parsing business data include: Construct a material event ontology model to standardize heterogeneous key business events from multiple business systems and map them as business facts, then reconcile and synchronize them with the intermediate layer cache. Output a set of business facts as business data.

[0019] By adopting the above technical solutions, the standardized processing of heterogeneous business events was achieved with the help of the material event ontology model. The consistency and accuracy of business data were ensured by reconciliation and synchronization with the intermediate layer cache, providing reliable data support for subsequent state migration, anomaly identification and other links, and significantly improving the collaborative capabilities and data interoperability of multiple business systems.

[0020] A second aspect of this application provides a material status management and monitoring system based on the manufacturing lifecycle, the system comprising: The lifecycle definition module is used to establish a material state machine model containing status codes and status attributes and to divide the lifecycle into stages; The event listening module is used to connect with multiple business systems to capture key business events and transform them into a unified event model; The state transition rule engine is used to preset state transition rules and custom rules, and to determine the legal transition path. The visualization monitoring module is used to present material status, migration path and statistical information, and provides multi-dimensional query entry points; The analysis and early warning module is used to identify stranded or abnormal materials and generate early warning notifications and handling suggestions.

[0021] A third aspect of this application provides an electronic device, comprising: a processor and a memory; wherein the memory stores a computer program adapted to be loaded by the processor and to execute the above-described method steps.

[0022] A fourth aspect of this application provides a computer storage medium storing a plurality of instructions adapted for loading by a processor and executing the method steps described above. Attached Figure Description

[0023] Figure 1 This is a flowchart illustrating a material status management and monitoring method based on the manufacturing lifecycle provided in an embodiment of this application; Figure 2 This is a schematic diagram of a state change processing method provided in an embodiment of this application; Figure 3 This is a schematic diagram of an analysis and early warning process provided in an embodiment of this application. Detailed Implementation

[0024] To enable those skilled in the art to better understand the technical solutions in this specification, the technical solutions in the embodiments of this specification will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, and not all embodiments.

[0025] In the description of the embodiments of this application, the words "for example" or "for instance" are used to indicate examples, illustrations, or explanations. Any embodiment or design that is described as "for example" or "for instance" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design options. Rather, the use of the words "for example" or "for instance" is intended to present the relevant concepts in a specific manner.

[0026] In the description of the embodiments of this application, the term "multiple" means two or more. For example, multiple systems means two or more systems, and multiple screen terminals means two or more screen terminals. Furthermore, the terms "first" and "second" are used for descriptive purposes only and should not be construed as indicating or implying relative importance or implicitly specifying the indicated technical features. Thus, a feature defined with "first" or "second" may explicitly or implicitly include one or more of that feature. The terms "comprising," "including," "having," and variations thereof all mean "including but not limited to," unless otherwise specifically emphasized.

[0027] Please refer to Figure 1 This paper presents a flowchart illustrating a material status management and monitoring method based on the manufacturing lifecycle. This method can be implemented using a computer program, a microcontroller, or run on a material status management and monitoring system based on the manufacturing lifecycle. The computer program can be integrated into a computer device or run as a standalone application. Specifically, the method includes steps S100 to S400, as follows: S100. Establish a material state model based on the manufacturing life cycle. The material state model includes a state code, which is used to characterize the state stage and state attributes of the material. In this embodiment of the application, the material state model is a structured data model used to uniformly describe various state information of materials in the entire manufacturing process, and to provide a standardized state benchmark for cross-system material state management.

[0028] A status code is a combination of characters used to uniquely identify the status of a material in a material status model. This combination of characters carries both the status stage information and the status attribute information of the material, enabling various business systems to quickly identify the current status characteristics of the material through the status code.

[0029] Status stages are the specific links in the material's lifecycle, divided according to the actual process of the manufacturing lifecycle. These links cover the entire chain from material procurement to final delivery. Each status stage is connected in sequence to form a complete path for material flow, ensuring that the flow of material status conforms to the actual logic of manufacturing business. Status attributes are descriptions of the available status of materials in the corresponding status stage.

[0030] Based on the above embodiments, as another optional embodiment, the status stages include pending purchase, purchased, pending warehousing, warehousing, pending material requisition, material requisition in progress, production in progress, pending quality inspection, qualified warehousing, pending shipment, and shipped.

[0031] In some embodiments, the status attributes include available, unavailable, and locked.

[0032] The available status indicates that the material can flow normally to the next stage according to the business process. The unavailable status indicates that the material cannot participate in the normal flow due to quality problems, damage, or other reasons. The locked status indicates that the material is restricted from flowing due to order binding, special use, or other needs, and can only continue to participate in the business process after being unlocked.

[0033] In some embodiments, the entire business process of the manufacturing lifecycle is analyzed, clarifying the business boundaries and connection conditions of each stage to ensure that the division of state stages aligns with actual manufacturing operations. Subsequently, a unique state code is assigned to each state stage. The design of the state code adopts a hierarchical coding rule to reflect the sequentiality of the state stages and includes identification information of state attributes, enabling the state code to intuitively reflect the core state characteristics of the material. Simultaneously, an association mapping relationship between state stages and state attributes is established, clarifying the allowed types of state attributes under each state stage to avoid mismatches between state attributes and state stages, ensuring the consistency and accuracy of the material state model.

[0034] S200: Obtain key business events of materials from multiple business systems, obtain business data of each material through cross-system synchronous parsing, and perform state migration in combination with preset state migration rules to generate migration paths; In some embodiments, the multiple business systems specifically include an Enterprise Resource Planning (ERP) system, a Manufacturing Execution System (MES) system, and a Warehouse Management System (WMS). These systems respectively undertake business management functions at different stages of the manufacturing lifecycle, and the key business events generated can comprehensively reflect the flow of materials.

[0035] In this embodiment of the application, key business events refer to core business actions that trigger state changes during the material flow process. These include purchase order confirmation, warehouse receipt posting, material requisition form issuance, production start, production completion, quality inspection completion, and warehouse entry / exit operations. These events are directly related to the state transition of materials in the manufacturing lifecycle and are the core triggering source for state migration.

[0036] In some embodiments, business data is core information related to materials obtained by parsing key business events, which may include material number, order number, supplier data, and customer data.

[0037] The material number is a character sequence used to uniquely identify the material, and each material corresponds to a unique material number; the order number is the identification information associated with the purchase order or sales order to which the material belongs, used to trace the order source of the material; the supplier data is the relevant information of the supplier providing the material, including supplier name, supplier code, contact information, etc.; and the customer data is the relevant information of the customer receiving the material, including customer name, customer code, delivery address, etc.

[0038] In some embodiments, the migration path is a complete trajectory that records the state transition process of a material during its manufacturing lifecycle. It may include the duration of the material's stay in each state stage, as well as the change data of status codes and business data when performing state transitions.

[0039] Among them, the dwell time is the time interval from when a material enters a certain state stage to when it leaves that stage, while the status code and business data change data record the changes in the status code and the updated information of the business data before and after each state transition.

[0040] refer to Figure 2 In some embodiments, the system connects to ERP, MES and WMS systems through preset interfaces to monitor key business events related to materials in each system in real time.

[0041] When a critical business event is detected, the event data is collected through a cross-system synchronization mechanism. This mechanism is based on a unified data interface and an intermediate layer cache. The unified data interface provides a standardized data transmission format for each business system, ensuring that event data from different systems can be received compatibly. The intermediate layer cache is used to temporarily store the collected event data to avoid loss or delay during data transmission.

[0042] The collected event data is parsed to extract core information such as material number, order number, supplier data, and customer data, forming structured business data. Then, preset state transition rules are invoked, combined with the material state model established by S100, to determine the current material's original state stage and the target state stage corresponding to the key business event. A state transition operation is then executed, updating the material's status code. Finally, based on the state transition execution results, the duration of the material's stay in the current state stage, as well as the changes to the status code and business data, are recorded, and the migration path for the material is generated by integrating these changes in chronological order.

[0043] S201. Based on the above embodiments, as another optional embodiment, the method for parsing business data includes: constructing a material event ontology model, standardizing heterogeneous key business events of multiple business systems, mapping them to business facts, reconciling and synchronizing them with the intermediate layer cache; and outputting a set of business facts as business data.

[0044] In this embodiment of the application, heterogeneous critical business events refer to critical business events with different formats and semantics from ERP systems, MES systems, and WMS systems. These events differ due to the different design logic and data specifications of each system and cannot be directly used for state transition judgment.

[0045] Business facts are standardized data that contain core information that can trigger material status transitions and are a core component of business data.

[0046] The intermediate layer cache is a cache module used to store standardized data and realize cross-system data reconciliation and synchronization. It can compare data with the data of various business systems in real time to ensure data consistency.

[0047] In some embodiments, the material event ontology model may include core fields such as event type, material identifier, trigger time, associated document number, operation subject, and event result.

[0048] The event type field identifies the specific type of the key business event, such as purchase order confirmation or production completion; the material identifier field corresponds to the material number in S100 and is used to associate specific materials; the trigger time field records the specific time when the key business event occurs; the associated document number field records the business document number related to the event, such as purchase order number or work order number; the operation subject field records the user or system module that executes the business event; and the event result field records the execution status of the business event, such as success or failure.

[0049] Furthermore, by combining message queue (RabbitMQ) and REST interface, it connects to ERP system, MES system, and WMS system to collect heterogeneous key business events generated by each system in real time.

[0050] The collected heterogeneous key business events are standardized. According to the field specifications of the material event ontology model, event data of different formats are mapped to the corresponding fields, missing core information is supplemented, data format inconsistencies are corrected, and business facts in a unified format are formed.

[0051] The generated business facts are reconciled with the historical business data stored in the intermediate layer cache. Key information such as material identifiers and associated document numbers in the business facts are compared to determine whether there are data conflicts or duplicates.

[0052] If data conflicts exist, they will be handled according to the preset conflict resolution rules, prioritizing the retention of the most recently generated business fact data; if duplicate data exists, the duplicate parts will be discarded directly.

[0053] The set of business facts that have been reconciled is output as the business data used in S200 for state transition judgment. At the same time, the standardized business facts are updated to the intermediate layer cache to ensure that the intermediate layer cache data is synchronized with the data of each business system.

[0054] S202. Based on the above embodiments, as another optional embodiment, state migration is performed in conjunction with preset state migration rules, and a migration path is generated, including: receiving business data, filtering out the activated target triggering conditions from the set of triggering conditions; locating the next hop state stage as the migration target based on the original state stage of the target material and the activated target triggering conditions; updating the status code of the target material to a new code representing the migration target, and generating a migration record, the migration record including at least the original state stage, the event fingerprint of the target triggering condition, the migration target, the timestamp, and the original business data summary that triggered this migration; and dynamically constructing a migration path based on the migration record organized by time sequence.

[0055] In this embodiment of the application, the trigger condition set includes a set of all condition information that can trigger material state transitions. Each trigger condition corresponds to a key business event and a state stage transition relationship. The activation status of the trigger condition is determined by whether the corresponding key business event occurs.

[0056] The target trigger condition is a set of trigger conditions selected from the set of trigger conditions that match the key business event that is currently occurring, and it directly determines the direction of the material state transition.

[0057] The original state stage is the state stage in which the material is before the state transition is performed. This state stage is determined by querying the material state model established by S100 and the business data generated by S200.

[0058] The migration target is the next state stage that the material will enter after the execution state migration, which is determined by the original state stage and the target triggering conditions.

[0059] An event fingerprint is a feature code used to uniquely identify the key business event corresponding to the target triggering condition. It is obtained by hashing the core information of the key business event, which can ensure that each key business event corresponds to a unique event fingerprint.

[0060] A timestamp records the time when a material status migration occurs, accurate to the second. The original business data summary is a compressed summary of the core information from the original business data that triggered the migration, retaining key content while reducing data storage.

[0061] Migration records are structured data that record complete information about a single state migration, integrating core information such as the original state stage, event fingerprint, migration target, timestamp, and original business data summary.

[0062] In some embodiments, business data parsed in S200 or S201 is received, and core information such as the type of key business events, trigger time, and material number of associated materials are extracted from the business data. Based on the extracted key business event information, a preset set of trigger conditions is traversed, and trigger conditions that match the key business event are selected as target trigger conditions. The selection process is achieved by comparing the key business event type with the preset event type in the trigger conditions. When the two match, it is determined that the trigger condition is activated.

[0063] Based on the material number in the business data, query the material state model established by S100 to determine the current state stage of the material. Combining the current state stage and the preset state transition rules in the target triggering conditions, locate the next state stage that the material will enter, and use this next state stage as the migration target.

[0064] Update the material status code and generate a migration record. Fill in the migration record with the specific name of the original status stage, the event fingerprint corresponding to the target trigger condition, the specific name of the migration target, the timestamp of the status migration, and the original business data summary that triggered the migration.

[0065] The generated migration records are serialized and organized according to the order of timestamps. All serialized migration records are then linked together in chronological order to dynamically construct the migration path of the material. This migration path fully reflects all state transitions of the material from the beginning of its manufacturing lifecycle.

[0066] In some embodiments, after locating the migration target, the method may further include verifying the legality of the migration target. The verification process is based on the legal transition paths of each state stage in the preset state transition rules. If the migration target belongs to the legal transition path of the original state stage, the status code update operation is performed. If the migration target does not belong to the legal transition path, the state transition is determined to be illegal, a migration exception prompt message is generated and fed back to the relevant personnel.

[0067] S300: Presents the status codes, business data, and migration paths of each material through a visual carrier. The visual carrier includes a multi-dimensional search entry for querying status codes, business data, and migration paths. Based on the above embodiments, as another optional embodiment, the method of presenting through a visualization carrier includes: generating statistical charts reflecting the distribution of each material in each state stage based on the status code and migration path of each material; generating a lifecycle flow map of the target material based on the status code of a single material, associated business data and its complete migration path; receiving query conditions based on any field or combination of fields in the status code, business data and migration path, and returning statistical charts and lifecycle flow maps of the matching materials.

[0068] In some embodiments, the visualization carrier is a software functional module used to display material status codes, business data, and migration paths. It can present the full lifecycle status information of materials to users in an intuitive form and support users to perform real-time monitoring and query operations on material status.

[0069] Statistical charts are data visualization charts used to reflect the distribution of materials in each state stage. They are generated by statistical analysis of the state information of multiple materials and can intuitively show the quantity distribution of materials in each state stage. The life cycle flow map is a visualization map generated for a single material. It uses the time axis as a clue to show the changes in the status code of the material, the associated business data and the complete migration path, clearly presenting the state flow trajectory of the material.

[0070] The multi-dimensional search entry point is the query function entry point set in the visualization carrier. It allows users to input query conditions based on any field or combination of fields from status codes, business data, and migration paths to quickly retrieve target materials. Query conditions are the filtering information entered by users according to their search needs. These can be single-field filtering conditions or combinations of multiple fields.

[0071] In some embodiments, the status code information in the material status model established in S100, the business data parsed in S200, and the migration path information generated in S200 or S202 are acquired and aggregated into the data processing module of the visualization carrier. The data processing module classifies and organizes the aggregated information, calculates the material quantity in each status stage for the status information of multiple materials, and generates statistical charts based on the statistical results. The type of statistical chart can be a bar chart, pie chart, or line chart. Different types of charts are suitable for different display needs. For example, a bar chart is used to compare the differences in the material quantity in each status stage, and a pie chart is used to show the proportion of the material quantity in each status stage to the total material quantity.

[0072] For a single material, the data processing module extracts the material's status code change records, associated business data, and complete migration path. Based on a timeline, this information is integrated to generate a lifecycle flow graph. The graph clearly marks the status code, business data changes, and current status stage for each time point. A multi-dimensional search entry is provided in the interactive interface of the visualization platform. Users can input search criteria through this entry, which can be any or a combination of fields such as status code, material number, order number, supplier name, and customer name.

[0073] Once the visualization platform receives the user's query criteria, the data processing module filters and matches the summarized material information according to the query criteria to find the target material that meets the query conditions. The statistical charts and lifecycle flow diagrams of the target material are then sent to the visualization platform's display interface. The display interface presents the query results to the user in an intuitive way, supporting user operations such as zooming and dragging on the lifecycle flow diagram, allowing users to easily view the detailed status and flow of the material.

[0074] In some embodiments, the visualization carrier may also include a production line-level view display. The production line-level view aggregates and analyzes the status information of all materials in the same production line to display the distribution of material status at each process stage of the production line, helping users to grasp the overall material flow efficiency of the production line.

[0075] In some embodiments, the update frequency of statistical charts can be set to once per minute to ensure that users can obtain real-time material status distribution information; the multi-dimensional search entry supports fuzzy search function, and users can match relevant materials by entering part of the field content.

[0076] S400 identifies abnormal materials based on state transition rules and generates early warning notifications.

[0077] Based on the above embodiments, as another optional embodiment, the method for identifying abnormal materials includes: comparing the dwell time with the threshold duration of the corresponding stage in the state transition rule to identify the dwelling abnormality; comparing the migration path with the migration order of the corresponding stage in the state transition rule to identify the jump abnormality; and generating an early warning notification based on the identification results of the dwelling abnormality or jump abnormality.

[0078] In this embodiment of the application, "stagnation anomaly" refers to the fact that the duration of material stay in a certain state stage exceeds the corresponding threshold duration, indicating that there is an abnormal situation of material stagnation in that stage; "jump anomaly" refers to the fact that the migration order of the material is inconsistent with the migration order of the corresponding stage in the state migration rules, indicating that there is an illegal state jump of the material.

[0079] In some embodiments, the dwell time of each material in each state stage is extracted from the migration path generated in S200 or S202, and the threshold duration corresponding to each state stage in the preset state migration rule is obtained.

[0080] refer to Figure 3 The process compares the dwell time of each material in each state stage with the corresponding threshold duration. If the dwell time of a material in a certain state stage exceeds the threshold duration for that stage, it is determined that the material has a dwell anomaly in that state stage. Then, the migration path of each material is extracted, and the flow order of the material in each state stage within the migration path is obtained. This flow order is compared with the preset legal migration order of each stage in the state migration rules. If the actual flow order of the material is inconsistent with the preset migration order, and a necessary state stage is skipped, it is determined that the material has a jump anomaly.

[0081] Materials exhibiting abnormal retention or jump behavior are marked and identified as abnormal materials. Key information about the abnormal materials is collected, including material number, abnormality type (retention or jump), stage of the abnormality, time of occurrence, and current status code. An early warning notification is generated based on this information. Once generated, the notification is sent to relevant personnel via a pre-defined push notification method, allowing them to promptly understand the situation of the abnormal materials and take appropriate action.

[0082] In some embodiments, the threshold duration can be dynamically adjusted based on the type of different materials and the urgency of the production plan, with the adjustment process based on historical flow data and real-time production status.

[0083] S401. Based on the above embodiments, as another optional embodiment, it includes: matching the anomaly type and associated context in the warning notification with the case handling mapping relationship in the preset rule base; generating handling suggestions based on the matching results and attaching them to the warning notification output.

[0084] In this embodiment, the anomaly type is the stagnation anomaly or jump anomaly identified in S400; the associated context is supplementary information related to the abnormal material, including the business scenario when the anomaly occurred, the associated order information, supplier or customer information, the current status attributes of the material, etc., which can provide a basis for generating handling suggestions.

[0085] The default rule base is a database that stores exception handling cases and handling rules. It includes the mapping relationship between exception types, associated context characteristics, and handling suggestions. These mapping relationships are established based on historical handling experience and business process specifications. The case handling mapping relationship is the core content stored in the default rule base, which clarifies the standard handling suggestions corresponding to different exception types and associated context combinations.

[0086] The handling recommendations are specific solutions proposed for abnormal situations involving abnormal materials, guiding staff to take appropriate measures to resolve the issues. The early warning notification, generated in S400, contains information about abnormal materials. Attaching the handling recommendations to the early warning notification provides staff with a more comprehensive reference for handling abnormalities.

[0087] In some embodiments, an early warning notification generated by S400 is obtained, the anomaly type of the abnormal material is extracted from the early warning notification, and the associated context information of the abnormal material is collected, including the stage of the anomaly occurrence, the associated order number, supplier data, customer data, and the current status attributes of the material. The extracted anomaly type and associated context information are input into a preset rule base, and the case handling mapping relationship is traversed in the preset rule base to find a mapping relationship that matches the current anomaly type and associated context features.

[0088] Once a matching case handling mapping relationship is found, the corresponding handling suggestions are extracted from that mapping relationship. The types of handling suggestions include return to inventory, manual investigation, and re-purchase suggestions. Different abnormal situations correspond to different handling suggestions. For example, for materials that are stuck in the inventory and are in the waiting-to-be-received stage, if the associated order has been cancelled, a return to inventory suggestion is generated; for cases of jump abnormalities involving key production materials, a manual investigation suggestion is generated.

[0089] The extracted handling suggestions are integrated with the early warning notification generated by the S400 system, and the handling suggestions are appended to the end of the early warning notification to form a complete early warning notification message. Finally, the early warning notification containing the handling suggestions is sent to relevant personnel through a preset push method. Based on the abnormal information and handling suggestions in the early warning notification, the personnel can quickly take targeted measures to improve the efficiency of abnormality handling.

[0090] To improve the accuracy and adaptability of handling recommendations, the preset rule base supports a self-learning update function, which can continuously optimize the case handling mapping relationship based on new anomaly handling cases.

[0091] Specifically, after staff handle abnormal materials, the system records the type of abnormality, associated context, handling suggestions, and handling effect. If the handling effect is good, the case is added to the preset rule library and the corresponding case handling mapping relationship is updated; if the handling effect is poor, the original mapping relationship is adjusted and optimized.

[0092] In some embodiments, the default rule base update cycle can be set to once a month to ensure that the rule base can adapt to changes in business processes in a timely manner.

[0093] Based on the above embodiments, as another optional embodiment, this application also provides a material status management and monitoring system based on the manufacturing lifecycle, including: The lifecycle definition module is used to establish a material state machine model with status codes and status attributes and to divide the lifecycle into stages; the event monitoring module is used to connect with multiple business systems to capture key business events and transform them into a unified event model; the state transition rule engine is used to preset state transition rules and custom rules and to provide legal flow path determination; the visualization monitoring module is used to present material status, migration path and statistical information and provide multi-dimensional query entry points; the analysis and early warning module is used to identify stuck or abnormal materials and generate early warning notifications and handling suggestions.

[0094] Based on the above embodiments, as another optional embodiment, the system further includes: a state processing module, used to receive event signals, perform state transitions, and update the state cache and flow records; and a historical data module, used to store the material's entire lifecycle state flow records and support multi-dimensional retrieval.

[0095] It should be noted that the system provided in the above embodiments is only illustrated by the division of the above functional modules. In actual applications, the above functions can be assigned to different functional modules as needed, that is, the internal structure of the device can be divided into different functional modules to complete all or part of the functions described above. In addition, the system and method embodiments provided in the above embodiments belong to the same concept, and the specific implementation process can be found in the method embodiments, which will not be repeated here.

[0096] Based on the above embodiments, as another optional embodiment, the present application embodiment may further include a computer storage medium, which may store multiple instructions adapted for loading by a processor and executing a method of the above embodiments. For the specific execution process, please refer to the detailed description of the above embodiments, which will not be repeated here.

[0097] Based on the above embodiments, as another optional embodiment, this application embodiment may further include an electronic device. The electronic device may include: at least one processor, at least one communication bus, a user interface, at least one network interface, and a memory.

[0098] The communication bus is used to enable communication between these components.

[0099] The user interface may include a display screen and a camera. Optional user interfaces may also include standard wired interfaces and wireless interfaces.

[0100] The network interface may include standard wired interfaces and wireless interfaces (such as Wi-Fi interfaces).

[0101] The processor may include one or more processing cores. It connects to various parts of the server via various interfaces and lines, executing instructions, programs, code sets, or instruction sets stored in memory, and accessing data stored in memory to perform various server functions and process data. Optionally, the processor may be implemented using at least one of the following hardware forms: Digital Signal Processing (DSP), Field-Programmable Gate Array (FPGA), and Programmable Logic Array (PLA). The processor may integrate one or more of the following: Central Processing Unit (CPU), Graphics Processing Unit (GPU), and modem. The CPU primarily handles the operating system, user interface, and applications; the GPU is responsible for rendering and drawing the content displayed on the screen; and the modem handles wireless communication. It is understood that the modem may also be implemented as a separate chip without being integrated into the processor.

[0102] The memory may include random access memory (RAM) or read-only memory. Optionally, the memory may include a non-transitory computer-readable storage medium. The memory can be used to store instructions, programs, code, code sets, or instruction sets. The memory may include a program storage area and a data storage area, wherein the program storage area may store instructions for implementing an operating system, instructions for at least one function (such as touch function, sound playback function, image playback function, etc.), instructions for implementing the above-described method embodiments, etc.; the data storage area may store data involved in the above-described method embodiments, etc. Optionally, the memory may also be at least one storage device located remotely from the aforementioned processor. As a computer storage medium, the memory may include an operating system, a network communication module, a user interface module, and an application program of one method.

[0103] In electronic devices, the user interface is primarily used to provide an input interface for users and to acquire user input data; while the processor can be used to call an application program stored in memory that represents a method. When executed by one or more processors, this causes the electronic device to perform one or more methods as described in the above embodiments. It should be noted that, for the sake of simplicity, the foregoing method embodiments are all described as a series of actions. However, those skilled in the art should understand that this application is not limited to the described order of actions, as some steps can be performed in other orders or simultaneously according to this application. Furthermore, those skilled in the art should also understand that the embodiments described in the specification are preferred embodiments, and the actions and modules involved are not necessarily essential to this application.

[0104] In the above embodiments, the descriptions of each embodiment have different focuses. For parts not described in detail in a certain embodiment, please refer to the relevant descriptions in other embodiments.

[0105] In the various embodiments provided in this application, it should be understood that the disclosed apparatus can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some service interface; the indirect coupling or communication connection between apparatuses or units may be electrical or other forms.

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

[0107] Furthermore, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit. The integrated unit can be implemented in hardware or as a software functional unit.

[0108] If the integrated unit is implemented as a software functional unit and sold or used as an independent product, it can be stored in a computer-readable storage device (CMD). Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or all or part of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a memory and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods of the various embodiments of this application. The aforementioned memory includes various media capable of storing program code, such as USB flash drives, portable hard drives, magnetic disks, or optical disks.

[0109] The above are merely exemplary embodiments of this disclosure and should not be construed as limiting the scope of this disclosure. Any equivalent changes and modifications made in accordance with the teachings of this disclosure shall still fall within the scope of this disclosure. Other embodiments of this disclosure will readily conceive of those skilled in the art upon consideration of the specification and the disclosure of practical truths.

[0110] This application is intended to cover any variations, uses, or adaptations of this disclosure that follow the general principles of this disclosure and include common knowledge or customary techniques in the art not described in this disclosure. The specification and embodiments are to be considered exemplary only, and the scope and spirit of this disclosure are defined by the claims.

Claims

1. A method for material status management and monitoring based on the manufacturing lifecycle, characterized in that, The method includes: A material state model is established based on the manufacturing life cycle. The material state model includes a state code, which is used to characterize the state stage and state attributes of the material. The system acquires key business events of materials from multiple business systems, obtains business data of each material through cross-system synchronous parsing, and performs state migration in combination with preset state migration rules to generate migration paths. The status codes, business data, and migration paths of each material are presented through a visual carrier, which includes a multi-dimensional search entry for querying the status codes, business data, and migration paths. Abnormal materials are identified based on the state transition rules, and early warning notifications are generated.

2. The material status management and monitoring method based on the manufacturing lifecycle as described in claim 1, characterized in that, The status stages include: pending purchase, purchased, pending warehousing, warehousing, pending material requisition, material requisition in progress, production in progress, pending quality inspection, qualified warehousing, pending shipment, and shipped. The status attributes include available, unavailable, and locked; The business data includes material number, order number, supplier data, and customer data; The migration path includes the duration of the material's stay in each of the aforementioned state stages, and the change data of the status code and business data when the state migration is performed.

3. The material status management and monitoring method based on the manufacturing lifecycle as described in claim 2, characterized in that, The step of performing state transitions in accordance with preset state transition rules and generating transition paths includes: Receive the service data and filter out the activated target triggering conditions from the set of triggering conditions; Based on the original state stage of the target material and the activated target triggering condition, the next jump state stage is located as the migration target. The status code of the target material is updated to a new code representing the migration target, and a migration record is generated. The migration record includes at least the original state stage, the event fingerprint of the target triggering condition, the migration target, the timestamp, and a summary of the original business data that triggered the migration. The migration path is dynamically constructed based on the migration records organized by time sequence.

4. The material status management and monitoring method based on the manufacturing lifecycle as described in claim 3, characterized in that, The method for identifying abnormal materials includes: By comparing the dwell time with the threshold duration of the corresponding stage in the state transition rule, abnormal dwelling can be identified. By comparing the migration path with the migration order of the corresponding stage in the state transition rule, jump anomalies are identified; Based on the identification results of the aforementioned lingering anomaly or redirection anomaly, the warning notification is generated.

5. The material status management and monitoring method based on the manufacturing lifecycle as described in claim 4, characterized in that, include: The abnormal type and associated context in the warning notification are matched with the case handling mapping relationship in the preset rule base; Based on the matching results, a handling suggestion is generated and attached to the warning notification output.

6. The material status management and monitoring method based on the manufacturing lifecycle as described in claim 2, characterized in that, The method of presenting through a visual medium includes: Based on the status code and migration path of each material, a statistical chart reflecting the distribution of each material in each state stage is generated. Based on the status code of a single material, the associated business data, and its complete migration path, a lifecycle flow map of the target material is generated. Receive query conditions based on any field or combination of fields in the status code, business data, and migration path, and return the statistical charts and lifecycle flow maps of the matching materials.

7. The material status management and monitoring method based on the manufacturing lifecycle as described in claim 1, characterized in that, The methods for parsing the business data include: Construct a material event ontology model, standardize the heterogeneous key business events of the multiple business systems, map them into business facts, and reconcile and synchronize them with the intermediate layer cache; The set of business facts is output as the business data.

8. A material status management and monitoring system based on the manufacturing lifecycle, characterized in that, include: The lifecycle definition module is used to establish a material state machine model containing status codes and status attributes and to divide the lifecycle into stages; The event listening module is used to connect with multiple business systems to capture key business events and transform them into a unified event model; The state transition rule engine is used to preset state transition rules and custom rules, and to determine the legal transition path. The visualization monitoring module is used to present material status, migration path and statistical information, and provides multi-dimensional query entry points; The analysis and early warning module is used to identify stranded or abnormal materials and generate early warning notifications and handling suggestions.

9. An electronic device, characterized in that, It includes a processor, a memory, a user interface, and a network interface. The memory is used to store instructions, the user interface and the network interface are used to communicate with other devices, and the processor is used to execute the instructions stored in the memory to cause the electronic device to perform the method as described in any one of claims 1-7.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a plurality of instructions adapted to be loaded by a processor and executed as described in any one of claims 1-7.

Images