Method, system and related device for managing the entire life cycle of equipment maintenance

Abstract

The application relates to the manufacturing field and provides a device maintenance full life cycle management method, a system and related devices. The method comprises the following steps: generating a maintenance work order associated with a specified worker based on a device maintenance plan and personnel assignment rules; identifying a barcode of a device corresponding to device information in the device maintenance work order and determining an identification result; if the identification result indicates that the device corresponding to the barcode and the device corresponding to the device information are the same device, obtaining at least one maintenance item corresponding to the device maintenance work order; generating field operation data based on maintenance result data corresponding to the at least one maintenance item; and updating device maintenance information displayed in real time according to the field operation data. The above method can realize dynamic management and control of the full life cycle of device maintenance, and improve the intelligent level and management efficiency of maintenance management.

Description

Technical Field

[0001] This application relates to the field of industrial manufacturing, specifically to a method, system, and related equipment for the full lifecycle management of equipment maintenance. Background Technology

[0002] In the electronics manufacturing industry, stable equipment operation is crucial for ensuring production capacity and quality. However, traditional maintenance management relies heavily on paper forms and Excel ledgers, resulting in data silos, lack of process visibility, delayed fault response, and significant downtime losses.

[0003] To address the aforementioned issues, existing solutions are mainly divided into two categories: reactive maintenance and periodic maintenance. However, both types of solutions have limitations. For example, reactive maintenance only initiates the process after equipment failure and downtime, resulting in slow response times and significant downtime losses. Periodic maintenance uses fixed-cycle maintenance, which is prone to missed maintenance or over-maintenance, and paper records are difficult to trace. Although some systems have introduced data acquisition functions, existing systems are generally limited in function and lack a unified digital platform. They still heavily rely on human experience and cannot achieve closed-loop management from data acquisition to intelligent analysis, making it difficult to meet the needs of preventative maintenance and continuous improvement. Summary of the Invention

[0004] This application provides a method, system, and related equipment for the full lifecycle management of equipment maintenance, in order to solve the technical problem that the existing technology cannot achieve closed-loop management from data collection to intelligent analysis, and is difficult to meet the needs of preventive maintenance and continuous improvement.

[0005] The first aspect of this application provides a method for full lifecycle management of equipment maintenance, applied to electronic devices. The method includes: generating maintenance work orders associated with designated personnel based on equipment maintenance plans and personnel assignment rules; identifying the barcode of the device corresponding to the equipment information in the equipment maintenance work order and determining the identification result; if the identification result indicates that the device corresponding to the barcode is the same device as the device corresponding to the equipment information, obtaining at least one maintenance item corresponding to the equipment maintenance work order; generating on-site operation data based on the maintenance result data corresponding to the at least one maintenance item; and updating the displayed equipment maintenance information in real time based on the on-site operation data.

[0006] In some embodiments, the method further includes: identifying the barcode corresponding to the faulty device, generating a repair work order based on the device information and fault symptoms corresponding to the barcode of the faulty device, and synchronizing the repair work order to the maintenance order center for display; the repair work order includes the location information of the faulty device, the repair time, the repair content, and the repair status.

[0007] In some embodiments, the method further includes: if the status of the maintenance work order or the repair work order does not change to a preset target status within a preset time, generating maintenance early warning information, wherein the maintenance early warning information includes maintenance content, maintenance equipment, faulty equipment, and fault phenomenon.

[0008] In some embodiments, the electronic device is equipped with a maintenance agent, which receives a description of a maintenance problem based on pre-imported maintenance history and technical data, and automatically matches and outputs corresponding maintenance and debugging guidance.

[0009] In some embodiments, updating the displayed equipment maintenance information in real time based on the on-site operation data includes: updating the displayed equipment maintenance information in real time using big data analysis and mining algorithms based on the on-site operation data.

[0010] A second aspect of this application provides a full lifecycle management system for equipment maintenance. The system includes a mobile maintenance platform for manual interaction and a web-based maintenance platform for displaying equipment maintenance information. The mobile maintenance platform and the web-based maintenance platform are communicatively connected. Based on real-time feedback of field operation data from the mobile maintenance platform, the system triggers synchronous updates of equipment maintenance information on the web-based maintenance platform. Specifically: the mobile maintenance platform generates and dispatches equipment maintenance work orders, receives field operation data generated from maintenance operations performed according to the work orders, and feeds the field operation data back to the web-based maintenance platform in real time; the web-based maintenance platform automatically updates and displays the equipment maintenance information based on the field operation data fed back from the mobile maintenance platform using a data mining algorithm. The equipment maintenance information includes repair requests, inspections, maintenance information, and equipment parameter information; and responds to user-inputted query conditions by displaying the equipment maintenance information corresponding to the query conditions.

[0011] In some embodiments, the mobile operation and maintenance platform includes an inspection module, a maintenance module, and a repair module, wherein: the inspection module is used to generate inspection work orders and send them to designated personnel according to a preset equipment inspection plan and personnel assignment rules, or to perform inspection operations based on the inspection work orders to generate the on-site operation data and transmit it back to the web-based operation and maintenance platform in real time; the maintenance module is used to generate maintenance work orders and send them to designated personnel according to a preset equipment maintenance plan and personnel assignment rules, or to perform maintenance operations based on the maintenance work orders to generate the on-site operation data and transmit it back to the web-based operation and maintenance platform in real time; the repair module is used to generate fault work orders and send them to repair personnel according to fault equipment information and fault phenomena, or to perform repair operations based on repair work orders to generate the on-site operation data and transmit it back to the web-based operation and maintenance platform in real time.

[0012] In some embodiments, the web-based platform includes an equipment maintenance module, a parameter control module, and an equipment panoramic display module. The equipment operation and maintenance information includes equipment maintenance information and equipment parameter information. Specifically: the equipment maintenance module monitors the equipment maintenance information, which includes equipment repair information, equipment inspection information, equipment maintenance information, inspection information from the mobile operation and maintenance platform, and abnormal item information; the parameter control module monitors the equipment parameter information, which includes basic equipment information, project maintenance data, production line parameter information, site equipment configuration, and equipment abnormal codes; the equipment panoramic display module includes a distribution map of all equipment on the production line, and displays the basic equipment information of the equipment corresponding to the target location in response to mouse pointer hovering over the target location.

[0013] A third aspect of this application provides an equipment maintenance lifecycle management device, comprising: a generation unit for generating maintenance work orders associated with designated personnel based on equipment maintenance plans and personnel assignment rules; a determination unit for identifying the barcode of the equipment corresponding to the equipment information in the equipment maintenance work order and determining the identification result; an acquisition unit for acquiring at least one maintenance item corresponding to the equipment maintenance work order if the identification result indicates that the equipment corresponding to the barcode is the same equipment as the equipment corresponding to the equipment information; a production unit for generating on-site operation data based on the maintenance result data corresponding to at least one maintenance item; and an update unit for updating the displayed equipment maintenance information in real time based on the on-site operation data.

[0014] A fourth aspect of this application provides an electronic device, which includes: a memory, a processor, and a computer program stored in the memory and executable on the processor. When the processor executes the computer program, it implements the steps in the method provided in the first aspect described above.

[0015] The fifth aspect of this application provides a computer-readable storage medium storing a computer program, which, when executed by a processor, implements the steps of the method provided in the first aspect above.

[0016] In several embodiments of this application, maintenance work orders are generated based on equipment maintenance plans and personnel assignment rules, each associated with a designated worker. The barcode of the device corresponding to the equipment information in the work order is identified. If the device corresponding to the barcode is the same as the device corresponding to the equipment information, at least one maintenance item is determined for the work order. On-site operation data is generated based on the maintenance result data corresponding to at least one maintenance item. The displayed equipment maintenance information is updated in real time based on the on-site operation data. This method, through a closed-loop mechanism of planning, dispatching, execution, feedback, and updating, achieves dynamic management of the entire equipment maintenance lifecycle, improving the intelligence level and execution efficiency of maintenance management. Attached Figure Description

[0017] To more clearly illustrate the technical solutions of the embodiments of this application, the drawings used in the description of the embodiments of this application will be briefly introduced below. Obviously, the drawings described below are only some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.

[0018] Figure 1 This is an application scenario diagram of a method for implementing full lifecycle management of equipment maintenance provided in an embodiment of this application.

[0019] Figure 2 This is a flowchart of a method for managing the entire lifecycle of equipment maintenance provided in an embodiment of this application.

[0020] Figure 3 This is a schematic diagram illustrating the generation of inspection work orders according to an embodiment of this application.

[0021] Figure 4 This is a schematic diagram illustrating the generation of a maintenance work order according to an embodiment of this application.

[0022] Figure 5 This is a schematic diagram of processing inspection work orders provided in one embodiment of this application.

[0023] Figure 6 This is a schematic diagram of repeated inspection provided in an embodiment of this application.

[0024] Figure 7 This is a schematic diagram of maintenance status display provided in an embodiment of this application.

[0025] Figure 8 This is a schematic diagram of a processing and maintenance work order provided in an embodiment of this application.

[0026] Figure 9 This application provides a flowchart of maintenance operations for mobile electronic devices according to one embodiment.

[0027] Figure 10 This is a flowchart of the repair reporting process provided in one embodiment of this application.

[0028] Figure 11 This is a schematic diagram of inspection information provided in an embodiment of this application.

[0029] Figure 12 This is a schematic diagram of maintenance information provided in one embodiment of this application.

[0030] Figure 13 This is a schematic diagram of repair information provided in one embodiment of this application.

[0031] Figure 14 This is a schematic diagram of a dashboard interface provided in one embodiment of this application.

[0032] Figure 15 This is a schematic diagram of the inspection history of a mobile electronic device provided in an embodiment of this application.

[0033] Figure 16 This is a schematic diagram of abnormal item information provided in an embodiment of this application.

[0034] Figure 17 This is a schematic diagram illustrating the basic information of the device provided in one embodiment of this application.

[0035] Figure 18 This is a schematic diagram showing a panoramic view of the device provided in one embodiment of this application.

[0036] Figure 19 This is a functional architecture diagram of an equipment maintenance lifecycle management system provided in an embodiment of this application.

[0037] Figure 20 This is a functional block diagram of an equipment maintenance lifecycle management device provided in another embodiment of this application.

[0038] Figure 21 This is a schematic diagram of the structure of an electronic device for a method of full life cycle management of equipment maintenance provided in another embodiment of this application. Detailed Implementation

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

[0040] Hereinafter, 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 number of indicated technical features. Thus, a feature defined as "first" or "second" may explicitly or implicitly include one or more of that feature. In the description of embodiments of this application, words such as "exemplary" or "for example" are used to indicate examples, illustrations, or descriptions. Any embodiment or design described as "exemplary" or "for example" in the embodiments of this application should not be construed as being more preferred or advantageous than other embodiments or design solutions. Specifically, the use of words such as "exemplary" or "for example" is intended to present the relevant concepts in a specific manner.

[0041] Unless otherwise defined, all technical and scientific terms used herein have the same meaning as commonly understood by one of ordinary skill in the art to which this application pertains. The terminology used in this application's specification is for the purpose of describing particular embodiments only and is not intended to be limiting of the application. It should be understood that, unless otherwise stated, " / " in this application means "or". For example, A / B can mean A or B. "And / or" in this application is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A alone, A and B simultaneously, and B alone. "At least one" refers to one or more. "More than one" refers to two or more. For example, at least one of a, b, or c can represent: a, b, c, a and b, a and c, b and c, and a, b, and c (seven cases).

[0042] like Figure 1 The diagram shown is an application environment schematic of the method for implementing the full life cycle management of equipment maintenance provided in this application embodiment.

[0043] like Figure 1As shown, the equipment maintenance lifecycle management method is applied to the equipment maintenance lifecycle management system. The equipment maintenance lifecycle management system includes a mobile maintenance platform deployed on a mobile electronic device 110, a web-based maintenance platform deployed on a computer electronic device 120, and a large display screen 130 installed in the workshop to display equipment maintenance information. The mobile maintenance platform can be an application deployed on any type of mobile electronic device 110 that allows human-computer interaction, such as a smartphone, tablet, personal digital assistant (PDA) terminal, or smart wearable device. The web-based maintenance platform can be a maintenance access program running in a browser and installed on various computer electronic devices 120, such as a personal computer, desktop workstation, laptop, or industrial control host. The large display screen 130 is a centralized visual display terminal that can summarize and present equipment maintenance information, equipment status, alarm information, etc., in real time, providing a visually intuitive overview of the overall situation. In this embodiment, the term "equipment" refers only to workshop production equipment.

[0044] The mobile operation and maintenance platform, the web-based operation and maintenance platform, and the large display screen can establish communication connections through their respective mobile electronic devices 110, computer electronic devices 120, and large display screens 130 to complete data interaction and business collaboration. For example... Figure 1 As shown, the mobile electronic device 110 is communicatively connected to the computer electronic device 120, the computer electronic device 120 is communicatively connected to the large display screen 130, and the mobile electronic device 110 is communicatively connected to the large display screen 130. The mobile operation and maintenance platform is used for manual business interaction. Based on the on-site operation and maintenance data of the mobile operation and maintenance platform, it is transmitted back to the web-based operation and maintenance platform in real time, triggering the synchronous update of equipment operation and maintenance information on the web-based operation and maintenance platform, and synchronously updating the content displayed on the large display screen.

[0045] The mobile-based operations and maintenance (O&M) platform is used to generate and dispatch equipment maintenance work orders, and to receive on-site operation data generated from the maintenance operations performed according to the equipment maintenance work orders, and to feed the on-site operation data back to the web-based O&M platform in real time. The web-based O&M platform is used to automatically update and display equipment O&M information based on the on-site operation data fed back from the mobile O&M platform using data mining algorithms. The equipment O&M information includes repair information, inspection information, maintenance information, and equipment parameter information; and responds to user-input query conditions to display the equipment O&M information corresponding to the query conditions.

[0046] The mobile maintenance platform receives equipment maintenance plans and designated personnel input by administrators, generates maintenance work orders associated with the designated personnel, and sends these work orders to the designated personnel's mobile devices. Based on the equipment information in the work order, it identifies the barcode of the corresponding device. If the device corresponding to the barcode matches the device in the equipment information, it retrieves the maintenance items corresponding to the work order. Based on the maintenance results data corresponding to the maintenance items, it generates on-site operation data. The mobile maintenance platform transmits this on-site operation data back to the web-based maintenance platform in real time. The web-based maintenance platform uses multi-dimensional intelligent analysis and mining algorithms based on maintenance big data to automatically update and display the maintenance information, and simultaneously updates the equipment maintenance information displayed on the large screen.

[0047] The inspection module generates inspection work orders based on preset equipment inspection plans and personnel assignment rules, sending them to designated personnel, or performs inspection operations based on inspection work orders to generate on-site operation data and transmits it back to the web-based operation and maintenance platform in real time. The maintenance module generates maintenance work orders based on preset equipment maintenance plans and personnel assignment rules, sending them to designated personnel, or performs maintenance operations based on maintenance work orders to generate on-site operation data and transmits it back to the web-based operation and maintenance platform in real time. The repair module generates fault work orders based on faulty equipment information and fault symptoms, sending them to repair personnel, or performs repair operations based on repair work orders to generate on-site operation data and transmits it back to the web-based operation and maintenance platform in real time.

[0048] like Figure 2 The diagram shown is a flowchart of the equipment maintenance lifecycle management method provided in this application embodiment. The equipment maintenance lifecycle management method can be applied to electronic devices (such as...) Figure 1 The mobile electronic device 110 or computer electronic device 120 shown. The equipment maintenance lifecycle management method can be applied to an equipment maintenance lifecycle management system (such as...). Figure 1 The equipment maintenance lifecycle management system shown in the flowchart can be modified in order of steps, and some steps can be omitted, depending on different needs.

[0049] S201, based on the equipment maintenance plan and personnel assignment rules, generates maintenance work orders associated with the designated personnel.

[0050] In at least one embodiment of this application, the equipment maintenance plan includes an equipment inspection plan and an equipment maintenance plan. Maintenance work orders correspond to the equipment maintenance plan, including inspection work orders corresponding to the equipment inspection plan and maintenance work orders corresponding to the equipment maintenance plan. The equipment maintenance plan can be set and adjusted according to actual conditions, and the personnel assignment rules can also be adjusted according to actual conditions. For example, the equipment maintenance plan may be a daily routine equipment inspection plan, and the personnel assignment rule may be to assign corresponding inspection personnel according to the shift order of the maintenance team. Another example is that for periodic equipment maintenance tasks, the personnel assignment rule may prioritize assigning tasks to staff whose current number of tasks is less than a preset threshold.

[0051] In some embodiments, the system is configured with functional control permissions, employing a role-based permission matching mechanism. Different user roles correspond to different functional usage permissions and operation scope permissions, with different user roles having different functional usage permissions. User roles include administrators and staff. Administrators can publish maintenance plans through the system and generate corresponding maintenance work orders for designated staff. Staff can view maintenance work orders through the system and perform maintenance operations according to the maintenance items in the work orders. Specifically, administrators can publish maintenance plans through a mobile maintenance platform, and staff can view maintenance work orders through a mobile maintenance platform to perform maintenance operations.

[0052] In some embodiments, maintenance work orders associated with specific personnel are generated based on equipment maintenance plans and personnel assignment rules. In one example, an administrator (e.g., a supervisor) can add a maintenance plan via a mobile operations and maintenance platform based on the equipment maintenance plan and personnel assignment rules. Based on the newly added maintenance plan and the specified personnel, a maintenance work order associated with the specified personnel is generated and sent to the mobile operations and maintenance platform bound to the specified personnel. The mobile operations and maintenance platform provides a maintenance interface, which includes inspection plan controls and maintenance plan controls (such as...). Figure 3 (See Figure a for the maintenance interface diagram).

[0053] In one example, the maintenance plan is used as the inspection plan for illustration. (Refer to...) Figure 3 As shown, Figure 3 This is a schematic diagram illustrating the generation of inspection work orders according to an embodiment of this application. Managers can access the inspection plan creation interface (e.g., by clicking the inspection plan control on the maintenance interface) Figure 3 As shown in Figure b), the interface for adding an inspection plan includes a "Add Plan" control. You can add a plan by clicking the "Add Plan" control (e.g., ...). Figure 3 The controls shown in the solid box in Figure b) enter the planning configuration interface to configure the inspection plan. Configuring the inspection plan includes configuring the inspection shift (e.g., day shift, night shift), inspection production line, inspection personnel, etc. Figure 3(As shown in Figures C and D). When the administrator completes the configuration and clicks the submit control, a prompt interface is displayed, which may include "Confirm Submission?". In response to the click of the confirm submit control, the mobile operations and maintenance platform generates an inspection work order based on the inspection plan submitted by the administrator and sends it to the mobile operations and maintenance platform corresponding to the inspection personnel (e.g., ...). Figure 3 (As shown in Figure e).

[0054] The steps for generating maintenance work orders are similar to those for generating inspection work orders, and will not be repeated here. Please refer to [link / reference needed]. Figure 4 As shown, Figure 4 This is a schematic diagram illustrating the generation of a maintenance work order according to an embodiment of this application.

[0055] In some embodiments, before publishing or viewing maintenance work orders, administrators and staff need to log in using their own login information for authentication. After successful authentication, they can access the operation and maintenance platform and perform operations such as publishing, viewing, and executing maintenance work orders. Login information includes username and password. The system matches and verifies the user's entered login information with pre-stored user information to confirm the legitimacy of the user's identity, thereby ensuring secure access to platform information, preventing unauthorized users from illegally obtaining or tampering with platform data, and ensuring the controllability and security of the information interaction process.

[0056] S202, Based on the equipment information in the equipment maintenance work order, identify the barcode of the equipment corresponding to the equipment information and determine the identification result.

[0057] In at least one embodiment of this application, the maintenance work order includes information such as maintenance type, maintenance equipment, maintenance date, and maintenance personnel. In one example, the inspection work order includes information such as inspection type, equipment information of the inspection equipment, inspection date, inspection shift, and inspection personnel. In another example, the maintenance work order includes information such as maintenance type, equipment information of the maintenance equipment, maintenance date, and maintenance personnel. Maintenance work orders are divided into three states: pending acceptance, pending processing, and processed. The pending acceptance state indicates that the maintenance work order has been sent to a designated worker, but the designated worker has not yet accepted the order. The pending processing state indicates that the designated worker has accepted the maintenance work order but has not yet performed the maintenance operation. The processed state indicates that the maintenance work order has completed the maintenance operation. Each maintenance work order is configured with a matching maintenance control, and the maintenance operation begins in response to clicking the matching maintenance control. The matching maintenance control includes a matching inspection control and a matching maintenance control. The inspection work order is configured with a matching inspection control, and the maintenance work order is configured with a matching maintenance control.

[0058] In some embodiments, after clicking the matching maintenance control, maintenance operations can be performed by recognizing the barcode of the device corresponding to the device information. The barcode can be a QR code, barcode, etc. The system pre-stores information such as the barcode, basic parameters, installation location, maintenance records, and ledger information for each device. Each production device (one machine) corresponds to a unique barcode (one code), which is bound to the physical device (one item). The barcode is also associated with the basic parameters, installation location, maintenance records, and ledger information of the corresponding device in the system to form a complete electronic file. This establishes a management model of one machine, one code, one item, and one file, realizing the digitization of device identity. It can track and monitor the entire life cycle of the device from its entry into the warehouse to its scrapping and replacement. Users can automatically obtain and associate the corresponding complete device file and related information by recognizing the device barcode.

[0059] In one example, taking the inspection plan as an example, refer to Figure 5 As shown, Figure 5 This is a schematic diagram illustrating the processing of inspection work orders according to an embodiment of this application. It involves staff (inspection personnel) verifying their identity based on login information (e.g., ...). Figure 5 (As shown in Figure a), after successful verification, you will enter the homepage interface of the operation and maintenance platform (e.g., Figure a). Figure 5 (As shown in Figure b). You can access the on-site operation interface by clicking the maintenance control on the homepage (e.g., ...). Figure 5 (as shown in Figure c), where, reference Figure 5 As shown, the on-site operation interface can display two types of maintenance work orders: inspection work orders and maintenance work orders. These are displayed in three statuses: pending order, pending processing, and processed.

[0060] In response to a click on the matching inspection control, an inspection operation is performed. The mobile electronic device's camera scans the barcode corresponding to the device information. The scanned barcode information is compared with the device information in the inspection work order to determine the recognition result. If the device corresponding to the barcode and the device corresponding to the device information are the same device, the recognition is considered successful, and a recognition success prompt window is generated (e.g., ...). Figure 5 (As shown in Figure d). If the device corresponding to the barcode is not the same device as the device information, the identification is determined to have failed, and an identification error prompt is generated to prevent maintenance operation errors caused by device confusion, ensure that maintenance personnel perform the corresponding maintenance items on the correct device, and guarantee the accuracy and traceability of maintenance operations.

[0061] S203, if the identification result indicates that the device corresponding to the barcode is the same device as the device information, obtain at least one maintenance item corresponding to the device maintenance work order.

[0062] In at least one embodiment of this application, if the device corresponding to the barcode and the device corresponding to the device information are the same device, a successful identification prompt window is generated. The prompt window includes a confirmation control (such as...). Figure 5 As shown in Figure d), clicking the "OK" button in the prompt window will automatically redirect you to the maintenance item interface corresponding to the maintenance work order. The maintenance item interface includes at least one maintenance item, which includes inspection items corresponding to the inspection work order and maintenance items corresponding to the maintenance work order. In one example, the inspection item interface includes at least one inspection item, which includes tidying up the wiring in the electrical control box, checking for loose screws, cleaning and greasing the moving lead screw, checking for abnormal noises during equipment operation, checking the heating element, and cleaning the inside of the main unit chassis, etc. (Refer to...) Figure 5 As shown in Figure e, Figure 5 The diagram in Figure e is a schematic diagram of the inspection items.

[0063] S204, Generate on-site operation data based on maintenance result data corresponding to at least one maintenance project.

[0064] In at least one embodiment of this application, the maintenance result data includes inspection result data and maintenance result data. Taking inspection as an example, the inspection items are selected sequentially, the inspection operation is performed, and the inspection result data for each inspection item is determined. The inspection results include normal, abnormal, not in production, down / under maintenance, no such inspection, etc. (e.g., Figure 5 (As shown in Figure f). Once the inspection results for all inspection items are determined, the overall inspection result is calculated based on all inspection results. The overall inspection result includes NG (Not Good) and OK (Good) items (e.g., ...). Figure 5 (As shown in Figure g). Based on the overall inspection results, the project inspection is completed upon submission (e.g., ...). Figure 5 (As shown in the middle h figure).

[0065] Electronic devices acquire on-site operation data based on each device's inspection status, inspection type, planned inspection time, inspection start time, inspection end time, all inspection result data, total inspection result, and inspection details. Specifically, mobile electronic devices transmit the on-site operation data for each device obtained from the mobile operation and maintenance platform back to the web-based operation and maintenance platform.

[0066] In some embodiments, after any inspection device completes an inspection of a project, if the same inspection device is matched again, a notification indicating that the inspection has been completed is output to avoid duplicate inspections. If the initial inspection result data for any inspection item is abnormal, warranty service can be provided for the inspection item corresponding to the abnormal initial inspection result data. After the warranty service is completed, the initial inspection result data is updated to be normal. Figure 6 As shown, Figure 6This is a schematic diagram of a repetitive inspection provided in one embodiment of this application. The inspection item in the diagram is "checking whether the screws in each part are loose". When the initial inspection result data is abnormal, it indicates that the screws are loose. The loose screws are repaired under warranty. After the warranty repair is completed, the inspection and matching are repeated, and the initial inspection result data is updated to normal.

[0067] In some embodiments, the system can use preset colors to distinguish and display the maintenance status of all devices. These preset colors can be set and adjusted according to actual conditions. For example... Figure 7 As shown, Figure 7 This is a schematic diagram of maintenance status display provided in one embodiment of this application. Green indicates that the inspection / maintenance is completed, and gray indicates that the inspection / maintenance is not completed. Clicking on any device will display the basic information of that device, which helps to quickly identify the specific location of the unmaintained device, perform maintenance operations, and improve maintenance efficiency.

[0068] In some embodiments, if the status of a maintenance work order or repair request does not change to a preset target status within a preset time, a maintenance warning message is generated. The preset target status indicates that the maintenance work order or repair request has been completed, such as a "processed" status. The maintenance warning message includes the maintenance content, the equipment being maintained, the faulty equipment, and the fault symptom. Figure 9 As shown, Figure 9 This application provides a flowchart of maintenance operations for mobile electronic devices according to one embodiment. Figure 9 The description can be found in the description of steps S201-S204 above.

[0069] The processing method for maintenance work orders is similar to that for inspection work orders, and will not be described again here. After determining the maintenance results for each maintenance item, if the equipment involves modifications to key dimensional data, the equipment parameter information can be updated in real time by having staff enter the new dimensional data. (See reference...) Figure 8 As shown, Figure 8 This is a schematic diagram of a processing and maintenance work order provided in an embodiment of this application.

[0070] In other embodiments, when a device malfunctions, the barcode corresponding to the malfunctioning device is identified, and a repair work order is generated based on the device information and malfunction symptoms corresponding to the malfunctioning device barcode. The repair work order is then synchronized to the maintenance order center for display. The repair work order includes the location information of the malfunctioning device, the repair time, the repair content, and the repair status.

[0071] Maintenance personnel can view the status of repair work orders through the mobile maintenance platform's repair request page or a large display screen. The status of a repair work order includes "Pending," "Under Repair," and "Completed." Newly generated repair work orders that identify the barcode corresponding to the faulty equipment will be displayed as "Pending." Whether a work order can be accepted is determined based on whether the location of the faulty equipment in the work order is within the preset maintenance range. If the location of the faulty equipment in the work order is within the preset maintenance range, the personnel can accept the pending work order and add it to their own maintenance order. Specifically, maintenance personnel can view repair work orders in the "Pending" status, see the specific location of the faulty equipment through the work order information, determine whether it is within the maintenance personnel's maintenance range, and then click to accept the order to enter their own maintenance field. In another example, a supervisor can assign work orders to the appropriate maintenance personnel based on their expertise and the fault symptoms.

[0072] In other implementations, the fault is identified based on the location of the faulty equipment in the repair work order. The barcode of the faulty equipment is then scanned to initiate repair operations. Once the repair is complete, clicking "Repair Complete and Submit" displays a pop-up with preset options for the repair personnel to choose from. These options can include fault type, line outage, and non-line outage, allowing users to clearly distinguish the fault attribute and its impact range. After selecting the preset options and confirming submission, the repair work order status is updated to "Completed," and the relevant data is synchronously archived and stored for subsequent data statistics and information retrieval. If the repair does not involve modifications to product processing dimensions, the repair work order is automatically closed.

[0073] If the repair involves modifying the product's processing dimensions, a repair first-piece order is generated. The production operator uses the repaired equipment to produce the product based on this order and then tests it. If the product's test results indicate that the measured values ​​are acceptable, the repair order is automatically closed. If the product's test results indicate that the measured values ​​are unacceptable, the repair order's completed status reverts to "under repair," and the repair continues until the product's test results indicate that the measured values ​​are acceptable, at which point the repair order is automatically closed. (Reference) Figure 10 As shown, Figure 10 This is a flowchart of the repair reporting process provided in one embodiment of this application.

[0074] In some embodiments, on-site operation data is generated based on maintenance data and transmitted back to the web-based maintenance platform in real time for statistical display. Maintenance data includes maintenance duration, maintenance frequency, maintenance details, etc.

[0075] In some embodiments, the electronic device is equipped with a maintenance agent. The maintenance agent receives a description of the maintenance problem based on pre-imported maintenance history and maintenance technical data, and automatically matches and outputs corresponding maintenance and debugging guidance.

[0076] S205 updates and displays equipment maintenance information in real time based on on-site operation data.

[0077] In at least one embodiment of this application, on-site operation data is transmitted back to the web-based operation and maintenance platform in real time, and the equipment maintenance information on the web-based operation and maintenance platform is dynamically refreshed in real time using big data analysis and mining algorithms.

[0078] In some embodiments, the web-based platform includes an equipment maintenance module for monitoring equipment maintenance information. This equipment maintenance information includes equipment repair requests, equipment inspection information, equipment upkeep information, mobile maintenance platform inspection information, and anomaly information. (See reference...) Figure 11 As shown in Figure a, the equipment maintenance module includes inspection analysis, inspection history, maintenance analysis, maintenance history, repair analysis, repair history, repair dashboard, maintenance report, mobile electronic device inspection (as shown in the PDA inspection module), and abnormal items (as shown in the Top Lssue module).

[0079] Using big data analytics and mining algorithms, the system automatically compiles equipment repair reports, equipment inspection reports, equipment maintenance reports, mobile maintenance platform inspection reports, and anomaly reports based on on-site operational data. It can also rank staff members based on the number of work orders they handle and their work order processing efficiency.

[0080] In one example, inspection information can be statistically analyzed based on the inspection operation, such as... Figure 11 As shown, Figure 11 This is a schematic diagram of inspection information provided in an embodiment of this application. The inspection information includes inspection analysis information and inspection history information.

[0081] Inspection analysis information includes ranking analysis of production line inspection completion rates, and statistical analysis of daily inspection completion rates for each production line; (Reference) Figure 11 As shown in Figure a. Figure 11 Figure a is a schematic diagram of inspection analysis information provided in an embodiment of this application. Figure 11 The system shown in Figure a statistically analyzes the inspection completion rate of each production line's equipment, generating bar charts and sorting and displaying the completion rates. The information displayed in the bar charts in the diagram can be toggled using a switching control, for example, switching to a trend chart display, and images can be downloaded using a download control. Each display interface also provides a query function, allowing users to query and analyze based on fields such as floor, production line, equipment, and time period. Each display interface also provides a download function, allowing users to download analysis files, image analyses, maintenance details, and other documents using a download control.

[0082] The inspection record information includes the name of the equipment inspected, the equipment number, the workstation where the equipment was located, the inspection time, the inspection type, the inspection progress, and the inspection details. (Reference) Figure 11 As shown in Figure b. Figure 11Figure b shows the inspection history information. Each inspection history entry includes the inspection number, inspection type, inspection creation time, inspection content, inspection completion rate, planned inspection time, planned end time, actual start time, equipment name, equipment location, workstation where the equipment is located, inspection status, and inspection details. Clicking a preset icon expands the display of detailed inspection information. Inspections can be sorted by status, with those marked "completed" appearing last.

[0083] Maintenance information can be statistically analyzed based on maintenance operations, such as... Figure 12 As shown, Figure 12 This is a schematic diagram of maintenance information provided in one embodiment of this application, including maintenance analysis information and maintenance history information. The maintenance analysis information includes weekly maintenance completion rate analysis and monthly maintenance completion rate statistical analysis for each production line; the maintenance history includes the name of the maintained equipment, the equipment number, the workstation where the maintained equipment is located, the maintenance time, the maintenance type, the maintenance progress, and the maintenance details. (Reference) Figure 12 The maintenance analysis information shown in Figure a is based on weekly and monthly maintenance statistics, including maintenance completion rate, planned maintenance count, and actual maintenance count for each production line. (See also: [reference needed]) Figure 12 The maintenance history information shown in Figure b is as follows: Figure 12 As shown in Figure b, each maintenance record may include maintenance number, maintenance type, maintenance creation time, maintenance content, maintenance completion rate, planned maintenance time, planned end time, actual start time, equipment name, equipment location, equipment workstation, maintenance status, and maintenance details. Clicking a preset icon will expand to display detailed maintenance information. Maintenance records can be sorted by status, with those marked "completed" appearing last. Measurement data can also be displayed by clicking key dimension controls.

[0084] Repair information can be statistically analyzed based on the repair requests, such as... Figure 13 As shown, Figure 13 This is a schematic diagram of repair information provided in an embodiment of this application, including repair analysis information and repair history information. The repair analysis information includes repair statistics and statistical analysis information. The repair statistics include repair order information, equipment repair frequency graphs, equipment repair duration graphs, production line repair status, and repair worker ranking; the statistical analysis information includes analysis of a preset number of equipment with repair frequencies and analysis of equipment whose repair duration is within a preset threshold; (Reference) Figure 13 The diagram in Figure a illustrates the repair request analysis information. (See Figure a for example.) Figure 13 As shown in Figure a, statistical analysis and ranking are performed based on repair time, repair frequency, and repair details. The top 10 devices by repair time and the top 10 devices by repair frequency can be displayed using bar charts for statistical analysis.

[0085] Repair history information includes the repair time, repair details, repair type, cause of the malfunction, repair duration, and number of repairs. (Reference) Figure 13 Figure b shows a schematic diagram of the repair history information. As shown, each repair history entry can include equipment number, equipment name, equipment location, workstation where the equipment is located, equipment model, control number, repair frequency, repair duration, urgency level, processing result, person reporting the repair, repair number, repair time, repair type, repair content, fault type, repair result and cause, repair start time and repair end time, and repair details. Clicking the preset icon will expand to display the detailed repair information.

[0086] The web-based operations and maintenance platform also provides dashboard interfaces, including maintenance dashboards and repair reporting dashboards. For example... Figure 14 As shown, Figure 14 This is a schematic diagram of a dashboard interface provided according to an embodiment of this application. (See reference) Figure 14 As shown in Figure a. Figure 14 Figure a is a schematic diagram of a maintenance dashboard interface provided in an embodiment of this application. As shown, the maintenance dashboard interface can be used for an overview of workshop operation and maintenance data, including daily inspection completion rate, weekly maintenance completion rate, maintenance task warnings, weekly daily inspection frequency trend analysis, weekly daily maintenance frequency trend analysis, total inspection time, and total inspection frequency. Maintenance task warnings include alerts for incomplete daily, weekly, and monthly maintenance tasks. See also... Figure 14 The diagram in Figure b shows a repair dashboard interface. As shown, the repair dashboard interface can be used to provide an overview of repair-related information, including repair orders, repair duration, repair frequency, repair sorting, maintenance personnel ranking, and production line stability ranking.

[0087] Equipment maintenance information also includes the inspection history of mobile electronic devices. Inspection content will pop up when the mobile electronic device is used for the first time each day. The inspection content will remain displayed for a preset duration, responding to a "Read and confirm, agree to use" confirmation action, allowing access to the platform to perform the inspection. The inspection history of the mobile electronic device includes inspection content, inspector, inspection date, administrator, and user unit, etc. Figure 15 As shown, Figure 15 This is a schematic diagram of the inspection history of mobile electronic devices.

[0088] refer to Figure 16 As shown, Figure 16 This is a schematic diagram illustrating the abnormal item information presented in this application. Equipment maintenance information also includes abnormal item information, which includes inspection abnormalities and maintenance abnormalities. The diagram shows the top 10 inspection abnormalities and the top 10 maintenance abnormalities.

[0089] The web-based operations and maintenance platform also includes a central parameter control module. This module monitors and manages equipment parameter information, including basic equipment information, project maintenance data, production line parameter information, site equipment configuration, and equipment exception codes. (Reference) Figure 17 As shown, Figure 17 This is a schematic diagram illustrating basic equipment information provided in one embodiment of this application. Basic equipment information may include equipment name, type, control number, machine model, production line, workstation, and other basic information. Thus, once a new piece of equipment is introduced, its maintenance history, repair history, and other relevant information can be traced throughout its entire lifecycle until it is scrapped, improving management efficiency. This achieves a closed-loop management system where tasks can be assigned, processes can be monitored, results can be recorded, anomalies can be alerted, and responsibility can be traced, significantly improving equipment maintenance efficiency.

[0090] The web-based operations and maintenance platform also includes a panoramic equipment display module. This module displays a distribution map of all equipment on the production line and, in response to mouse pointer hovering over a target location, displays basic equipment information for the corresponding device at that location. Figure 18 As shown, Figure 18 This is a panoramic view of the device provided in one embodiment of this application.

[0091] In several embodiments of this application, maintenance work orders are generated based on equipment maintenance plans and personnel assignment rules, each associated with a designated worker. The barcode of the device corresponding to the equipment information in the work order is identified. If the device corresponding to the barcode is the same as the device corresponding to the equipment information, at least one maintenance item is determined for the work order. On-site operation data is generated based on the maintenance result data corresponding to at least one maintenance item. The displayed equipment maintenance information is updated in real time based on the on-site operation data. This method, through a closed-loop mechanism of "planning—assignment—execution—feedback—update," achieves dynamic management and control of the entire equipment maintenance lifecycle, improving the intelligence level and execution efficiency of maintenance management.

[0092] refer to Figure 19 As shown, an embodiment of this application provides a functional architecture diagram of an equipment maintenance lifecycle management system. Figure 19As shown, the equipment maintenance lifecycle management system comprises an operational decision-making layer, an intelligent application layer, and a data processing layer. The operational decision-making layer supports management decision-making scenarios, providing support for overall business coordination and global control, enabling managers to conduct overall operational coordination and global management. The intelligent application layer is used for inspection and maintenance management, repair management, data analysis, and basic management. Inspection and maintenance management includes inspection and maintenance plans, inspection and maintenance execution, and inspection and maintenance history; repair management includes repair requests, order grabbing / dispatch / repair execution / repair history; data analysis includes inspection analysis, maintenance analysis, and repair analysis; basic management includes user management, standard management, and basic system management. The data processing layer is used for data statistics, data analysis, and data visualization. User management can include permission management and menu management; standard management can include maintenance standards, equipment information, and standard procedures; basic system management includes data operations, import / export, and early warning prompts.

[0093] like Figure 20 The diagram shown is a functional block diagram of an equipment maintenance lifecycle management device provided in an embodiment of this application. The equipment maintenance lifecycle management device 12 includes a generation unit 120, a determination unit 121, an acquisition unit 122, a production unit 123, and an update unit 124. The module / unit referred to in this application refers to a module / unit that can be processed by a processor (e.g., ...). Figure 21 A series of computer-readable instruction segments acquired by the processor 102 shown, and capable of performing a fixed function, which are stored in memory (e.g., a memory processor 102). Figure 21 In the memory 101 shown.

[0094] The generation unit 120 is used to generate maintenance work orders associated with designated personnel based on equipment maintenance plans and personnel assignment rules; the determination unit 121 is used to identify the barcode of the equipment corresponding to the equipment information in the equipment maintenance work order and determine the identification result; the acquisition unit 122 is used to acquire at least one maintenance item corresponding to the equipment maintenance work order if the identification result indicates that the equipment corresponding to the barcode is the same equipment as the equipment corresponding to the equipment information; the production unit 123 is used to generate on-site operation data based on the maintenance result data corresponding to at least one maintenance item; and the update unit 124 is used to update the displayed equipment maintenance information in real time based on the on-site operation data.

[0095] The module / unit referred to in this application refers to a series of computer program segments that can be executed by at least one processor and perform a fixed function, and which are stored in memory. In this embodiment, the limitations of the equipment maintenance lifecycle management device 11 can be found in the above-described limitations of the equipment maintenance lifecycle management method, and will not be repeated here.

[0096] In several embodiments of this application, maintenance work orders are generated based on equipment maintenance plans and personnel assignment rules, each associated with a designated worker. The barcode of the device corresponding to the equipment information in the work order is identified. If the device corresponding to the barcode is the same as the device corresponding to the equipment information, at least one maintenance item is determined for the work order. On-site operation data is generated based on the maintenance result data corresponding to at least one maintenance item. The displayed equipment maintenance information is updated in real time based on the on-site operation data. This method, through a closed-loop mechanism of "planning—assignment—execution—feedback—update," achieves dynamic management and control of the entire equipment maintenance lifecycle, improving the intelligence level and execution efficiency of maintenance management.

[0097] like Figure 21 The diagram shown is a structural schematic of an electronic device for a device maintenance lifecycle management method provided in an embodiment of this application.

[0098] Electronic device 10 may include network devices and / or user devices. Among them, network devices include, but are not limited to, a single network electronic device, a group of electronic devices consisting of multiple network electronic devices, or a cloud based on cloud computing consisting of a large number of hosts or network electronic devices.

[0099] The network where electronic device 10 is located includes, but is not limited to: the Internet, wide area network, metropolitan area network, local area network, virtual private network (VPN), etc.

[0100] In the embodiments of this application, the electronic device 10 includes, but is not limited to, a memory 101, a processor 102, and computer-readable instructions stored in the memory 101 and executable on the processor 102, such as a device maintenance lifecycle management program.

[0101] Those skilled in the art will understand that the schematic diagram is merely an example of the electronic device 10 and does not constitute a limitation on the electronic device 10. It may include more or fewer components than shown, or combine certain components, or different components. For example, the electronic device 10 may also include input / output devices, network access devices, buses, etc.

[0102] Processor 102 can be a Central Processing Unit (CPU), or other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor, a processor, or any conventional processor. Processor 102 is the computational core and control center of electronic device 10, connecting various parts of the electronic device 10 through various interfaces and lines, and executing the operating system of electronic device 10 as well as various installed application programs and program code.

[0103] Processor 102 acquires the operating system and various installed applications of electronic device 10. Processor 103 acquires applications to implement the steps in the above-described display method embodiments, for example... Figure 2 The steps are shown.

[0104] For example, a computer program may be divided into one or more modules / units, one or more of which are stored in memory 101 and retrieved by processor 102 to complete this application. One or more modules / units may be a series of computer program instruction segments capable of performing a specific function, which describe the process of retrieving the computer program from electronic device 10.

[0105] The memory 101 can be used to store computer programs and / or modules. The processor 102 implements various functions of the electronic device 10 by running or retrieving the computer programs and / or modules stored in the memory 101, and by calling the data stored in the memory 101. The memory 101 may mainly include a program storage area and a data storage area. The program storage area may store the operating system, application programs required for at least one function (such as sound playback function, image playback function, etc.), etc.; the data storage area may store data created according to the use of the electronic device, etc. In addition, the memory 101 may include non-volatile memory, such as hard disk, memory, plug-in hard disk, smart media card (SMC), secure digital (SD) card, flash card, at least one disk storage device, flash memory device, or other non-volatile solid-state storage device.

[0106] The memory 101 can be the external memory and / or internal memory of the electronic device 10. Furthermore, the memory 101 can be a memory in physical form, such as a memory stick, a TF card (Trans-flash Card), etc.

[0107] Combination Figure 2 The memory 101 in the electronic device 10 stores computer-readable instructions, and the processor 102 can execute the computer-readable instructions stored in the memory 101 to achieve, for example... Figure 2 The multiple processes shown are designed to implement a full lifecycle management approach for equipment maintenance.

[0108] If the modules / units integrated in the electronic device 10 are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, all or part of the processes in the methods of the above embodiments can also be implemented by instructing related hardware through computer-readable instructions. The computer-readable instructions can be stored in a computer-readable storage medium, and when executed by a processor, they can implement the steps of the various method embodiments described above.

[0109] Computer-readable instructions include computer-readable instruction code, which can be in the form of source code, object code, executable file, or some intermediate form. Computer-readable media can include: any entity or device capable of carrying computer-readable instruction code, recording media, USB flash drive, portable hard drive, magnetic disk, optical disk, computer memory, read-only memory (ROM), and random access memory (RAM).

[0110] For example, computer-readable instructions can be divided into one or more modules / units, one or more of which are stored in memory 101 and executed by processor 102 to complete this application. One or more modules / units can be a series of computer-readable instruction segments capable of performing a specific function, which describe the execution process of the computer-readable instructions in electronic device 10. For example, computer-readable instructions can be divided into a generation unit 120, a determination unit 121, an acquisition unit 122, a production unit 123, and an update unit 124.

[0111] For detailed information on the functions of each module / unit, please refer to the above text. Figure 2The detailed description of the above will not be repeated here. It should be understood from the several embodiments provided in this application that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of modules is only a logical functional division, and other division methods may exist in actual implementation.

[0112] The modules described as separate components may or may not be physically separate. The components shown as modules 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 modules can be selected to achieve the purpose of this embodiment according to actual needs.

[0113] Furthermore, the functional modules 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 in the form of hardware plus software functional modules.

[0114] Therefore, the embodiments should be considered exemplary and non-limiting in all respects, and the scope of this application is defined by the appended claims rather than the foregoing description. Thus, all variations falling within the meaning and scope of equivalents of the claims are intended to be embraced within this application. No appended diagram markings in the claims should be construed as limiting the scope of the claims.

[0115] Furthermore, it is clear that the word "including" does not exclude other units or steps, and the singular does not exclude the plural. Multiple units or devices can also be implemented by a single unit or device through software or hardware. Terms such as "first," "second," etc., are used to indicate names and do not indicate any specific order.

[0116] Finally, it should be noted that the above embodiments are only used to illustrate the technical solutions of this application and are not intended to limit it. Although this application has been described in detail with reference to preferred embodiments, those skilled in the art should understand that modifications or equivalent substitutions can be made to the technical solutions of this application without departing from the spirit and scope of the technical solutions of this application.

Claims

1. A method for managing the entire lifecycle of equipment maintenance, applied to electronic equipment, characterized in that, The method includes: Based on the equipment maintenance plan and personnel assignment rules, a maintenance work order is generated that corresponds to the designated personnel. Based on the equipment information in the equipment maintenance work order, identify the barcode of the equipment corresponding to the equipment information and determine the identification result; If the identification result indicates that the device corresponding to the barcode is the same device as the device information, obtain at least one maintenance item corresponding to the device maintenance work order; Based on the maintenance result data corresponding to the at least one maintenance project, generate on-site operation data; Based on the on-site operation data, the displayed equipment maintenance information is updated in real time.

2. The equipment maintenance lifecycle management method according to claim 1, characterized in that, The method further includes: Identify the barcode corresponding to the faulty equipment, generate a repair work order based on the equipment information and fault symptoms corresponding to the barcode, and synchronize the repair work order to the maintenance order center for display; the repair work order includes the location information of the faulty equipment, the repair time, the repair content, and the repair status.

3. The equipment maintenance lifecycle management method according to claim 1 or 2, characterized in that, The method further includes: If the status of the maintenance work order or the repair work order does not change to the preset target status within a preset time, a maintenance warning message is generated. The maintenance warning message includes the maintenance content, the maintenance equipment, the faulty equipment, and the fault phenomenon.

4. The equipment maintenance lifecycle management method according to claim 1, characterized in that, The electronic device is equipped with a maintenance intelligence agent, which receives a description of the maintenance problem based on pre-imported maintenance history and maintenance technical data, and automatically matches and outputs corresponding maintenance and debugging guidance.

5. The equipment maintenance lifecycle management method according to claim 1, characterized in that, The real-time updating and display of equipment maintenance information based on the on-site operation data includes: Based on the on-site operation data, the equipment maintenance information displayed is updated in real time using big data analysis and mining algorithms.

6. A full lifecycle management system for equipment maintenance, characterized in that, The system includes a mobile-based operation and maintenance platform for human interaction and a web-based operation and maintenance platform for displaying equipment operation and maintenance information. The mobile-based operation and maintenance platform is communicatively connected to the web-based platform. Real-time transmission of on-site operation data from the mobile-based platform triggers the synchronous update of equipment operation and maintenance information on the web-based platform, wherein: The mobile terminal operation and maintenance platform is used to generate and dispatch equipment maintenance work orders, receive on-site operation data generated by performing maintenance operations according to the equipment maintenance work orders, and feed the on-site operation data back to the web terminal operation and maintenance platform in real time. The web-based operation and maintenance platform is used to automatically update and display the equipment operation and maintenance information based on the on-site operation data fed back by the mobile operation and maintenance platform using a data mining algorithm. The equipment operation and maintenance information includes repair information, inspection information, maintenance information, and equipment parameter information; and responds to user-input query conditions to display the equipment operation and maintenance information corresponding to the query conditions.

7. The equipment maintenance lifecycle management system according to claim 6, characterized in that, The mobile operation and maintenance platform includes an inspection module, a maintenance module, and a repair module, wherein: The inspection module is used to generate inspection work orders and send them to designated staff members according to the preset equipment inspection plan and personnel assignment rules, or to perform inspection operations based on the inspection work orders to generate the on-site operation data and transmit it back to the web-based operation and maintenance platform in real time. The maintenance module is used to generate maintenance work orders and send them to the designated staff members according to the preset equipment maintenance plan and personnel assignment rules, or to perform maintenance operations based on the maintenance work orders to generate the on-site operation data and transmit it back to the web-based operation and maintenance platform in real time. The maintenance module is used to generate a fault work order based on the faulty equipment information and fault symptoms and send it to the maintenance personnel, or to generate the on-site operation data based on the maintenance operation of the maintenance work order and transmit it back to the web-based operation and maintenance platform in real time.

8. The equipment maintenance lifecycle management system according to claim 6, characterized in that, The web-based platform includes an equipment maintenance module, a parameter control module, and an equipment panoramic display module. The equipment operation and maintenance information includes equipment maintenance information and equipment parameter information, wherein: The equipment maintenance module is used to monitor the equipment maintenance information, which includes equipment repair information, equipment inspection information, equipment maintenance information, inspection information from the mobile maintenance platform, and abnormal item information. The parameter control module is used to monitor the equipment parameter information, which includes basic equipment information, project maintenance data, production line parameter information, site equipment configuration, and equipment fault codes. The equipment panoramic display module includes a distribution map of all equipment on the production line, and is used to display the basic equipment information of the equipment corresponding to the target location in response to the operation of hovering the mouse pointer over the target location.

9. An electronic device, characterized in that, include: The device includes a memory, a processor, and a computer program stored in the memory and executable on the processor, wherein the processor executes the computer program to implement the device maintenance lifecycle management method as described in any one of claims 1 to 5.

10. A computer-readable storage medium, characterized in that, The computer-readable storage medium stores a computer program, which, when executed by a processor, implements the equipment maintenance lifecycle management method as described in any one of claims 1 to 5.

Images