Maintenance information management method and system based on multi-application software system

Abstract

The invention relates to the field of maintenance information management methods of a multi-application software system, in particular to a maintenance information management method and system based on the multi-application software system, and the method comprises the steps: compiling a maintenance work task book; counting a material list according to the maintenance work task book; matching the work ticket management with the maintenance work task book, and counting the maintenance progress; the maintenance progress is visualized, and maintenance progress defects are fed back; the overall planning and coordination of the maintenance work are improved through standardized compiling of the maintenance work task book, the maintenance efficiency is improved through association of the task book, automatic statistics and generation of the bill of materials, on-schedule promotion of the task is effectively supported, the transparency of the maintenance progress is improved through association of the work ticket management system and the task book, and the maintenance efficiency is improved. The maintenance task is ensured to be propelled according to the plan, and the management and control capability of the maintenance progress is improved by generating a Gantt chart or a Gantt chart and other visual tools.

Description

Technical Field

[0001] The present invention relates to the field of maintenance information management methods for multi-application software systems, and specifically to a maintenance information management method and system based on multi-application software systems. Background Art

[0002] With the rapid development of modern industrial technology, the production equipment of enterprises has become increasingly complex, and the reliability and availability of equipment have become important components of the core competitiveness of enterprises. As an important part of equipment management, maintenance management plays an indispensable role in ensuring equipment operation efficiency and reducing operation costs. In traditional maintenance management, manual records and the application of single software tools are the main modes. However, with the wide popularization of information technology, the integrated management of multi-application software systems has gradually emerged, laying a foundation for the digital and intelligent development of maintenance management.

[0003] Early maintenance management methods mainly relied on paper records and stand-alone application software. Although these methods can achieve basic recording and statistics, due to isolated information and difficult retrieval, the data utilization rate is low and human errors are prone to occur. With the increasing urgency of the demand for enterprise management digitization, maintenance management has gradually evolved towards the direction of an information-based platform. In recent years, project management systems (such as Project), enterprise resource planning systems (ERP), and computerized maintenance management systems (CMMS) have been widely used in enterprise maintenance management. These systems show good management capabilities in task assignment, progress tracking, resource planning, etc. However, these systems are usually modular and it is difficult to achieve data integration across systems. For example, the correlation processing of maintenance tasks, material usage, and progress feedback still requires manual intervention.

[0004] Although the existing maintenance management technologies have made great progress, there are still many deficiencies, especially the problems in system integration, data sharing, and intelligent feedback are particularly prominent. Most of the existing maintenance management systems are modular single applications, such as material management systems, work order management systems, and progress management systems. These systems operate independently and information cannot be shared, resulting in difficult data interaction between multiple systems. For example, the compilation information of maintenance task sheets cannot be directly associated with the material management module, and managers need to manually import material requirements, which is extremely prone to misoperations or omissions. Summary of the Invention

[0005] In view of the above existing problems, the present invention is proposed.

[0006] Therefore, the technical problem solved by the present invention is: aiming to solve the singularity of the existing maintenance management system; a maintenance information management method based on multi-application software systems reads relevant data by writing specific communication interface software to achieve data sharing between multiple software, so as to achieve the management of the entire maintenance project.

[0007] To solve the above technical problems, the present invention provides the following technical solutions: A maintenance information management method based on a multi-application software system, including: preparing a maintenance work task sheet; according to the maintenance work task sheet, counting the material list; matching the work ticket management with the maintenance work task sheet to count the maintenance progress; visualizing the maintenance progress and feedbacking the defects in the maintenance progress.

[0008] As a preferred solution of the maintenance information management method based on a multi-application software system described in the present invention, wherein: the preparation of the maintenance work task sheet includes preparing the maintenance specialty, maintenance system, maintenance equipment, maintenance content, and maintenance duration.

[0009] As a preferred solution of the maintenance information management method based on a multi-application software system described in the present invention, wherein: the counting of the material list includes counting the material name, material code, material price, material arrival status, and material usage according to the maintenance content in the maintenance work task sheet.

[0010] As a preferred solution of the maintenance information management method based on a multi-application software system described in the present invention, wherein: the matching of the work ticket management with the maintenance work task sheet includes selecting the work content at the end of the maintenance task sheet for the work content items during the process of handling the maintenance work ticket.

[0011] As a preferred solution of the maintenance information management method based on a multi-application software system described in the present invention, wherein: the counting of the maintenance progress includes the work ticket management obtaining the completed maintenance work, the ongoing maintenance work, and the unmaintained work, comparing with the maintenance duration in the maintenance task sheet, counting the maintenance progress, and listing the list of lagging works.

[0012] As a preferred solution of the maintenance information management method based on a multi-application software system described in the present invention, wherein: the visualization of the maintenance progress includes automatically generating a Gantt chart for the maintenance work according to the maintenance duration and maintenance progress in the maintenance task sheet.

[0013] As a preferred solution of the maintenance information management method based on a multi-application software system described in the present invention, wherein: the feedback of the defects in the maintenance progress includes retrieving the defects of the maintenance unit in the defect management system, and if it is determined that the defect belongs to the current maintenance work scope, it is marked as a defect to be processed;

[0014] If it does not belong to the current maintenance scope, it is marked as out of the maintenance scope;

[0015] Among the defects to be processed, if the status of the work ticket associated with the defect is already terminated, it is automatically marked as the defect has been terminated, and the defect handling completion time is feedbacked;

[0016] If the work ticket status is "under construction", mark it as "defect under construction".

[0017] If the task progress during defect handling is within the maintenance period, continuously track it.

[0018] If the task progress during defect handling exceeds the maintenance period, the system triggers an exception alarm, lists the overdue tasks for defect handling in the lag list, analyzes the reasons in combination with the material list, and notifies the on-site personnel for technical supervision.

[0019] Another object of the present invention is to provide an overhaul information management system based on a multi-application software system, which can optimize the scientific and technological achievement transformation mechanism and break through the obstacles to the innovative development of enterprises.

[0020] To solve the above technical problems, the present invention provides the following technical solutions: An overhaul information management system based on a multi-application software system, characterized in that it includes: a task book compilation module, a material list statistics module, an overhaul progress statistics module, a defect feedback module, and a technical supervision module;

[0021] The task book compilation module compiles an overhaul work task book.

[0022] The material list statistics module statistics the material list according to the overhaul work task book.

[0023] The overhaul progress statistics module matches the work ticket management with the overhaul work task book and statistics the overhaul progress.

[0024] The defect feedback module visualizes the overhaul progress and feedbacks the overhaul progress defects.

[0025] The technical supervision module automatically associates the problems found in the annual technical supervision and the technical supervision plan related to the current overhaul, and generates the technical supervision content, unit, responsible person, completion status, and existing problems of the current overhaul.

[0026] A computer device includes a memory and a processor. The memory stores a computer program, and when the processor executes the computer program, the steps of the above-mentioned overhaul information management method based on a multi-application software system are implemented.

[0027] A computer-readable storage medium stores a computer program thereon, and when the computer program is executed by a processor, the steps of the above-mentioned overhaul information management method based on a multi-application software system are implemented.

[0028] The beneficial effects of the present invention: By standardizing the compilation of the overhaul work task book, the overall planning and coordination of the overhaul work are improved, and the construction period delay and resource waste caused by improper task planning are avoided.

[0029] By associating with the task book, automatically counting and generating a material list, which improves the maintenance efficiency, reduces the cost waste caused by material shortage or redundancy, and effectively supports the progress of the task on schedule.

[0030] By associating the work ticket management system with the task book, the transparency of the maintenance progress is improved, ensuring that the maintenance tasks are carried out according to the plan, and at the same time effectively reducing the impact of task lag on the overall project duration.

[0031] By generating visualization tools such as Gantt charts or bar charts to dynamically display the maintenance progress, and combining data feedback to identify task lags, the control ability of the maintenance progress is improved, effectively reducing the project duration delay and resource waste caused by information asymmetry or delayed feedback. BRIEF DESCRIPTION OF THE DRAWINGS

[0032] In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the following will briefly introduce the drawings required for the description of the embodiments. Obviously, the drawings in the following description are only some embodiments of the present invention. For those of ordinary skill in the art, without creative efforts, other drawings can also be obtained based on these drawings.

[0033] Figure 1 It is a flowchart of a maintenance information management method based on a multi-application software system provided by an embodiment of the present invention. DETAILED DESCRIPTION OF THE EMBODIMENTS

[0034] In order to make the above objects, features, and advantages of the present invention more obvious and understandable, the following will make a detailed description of the specific embodiments of the present invention in conjunction with the drawings of the specification. Obviously, the described embodiments are some embodiments of the present invention, rather than all embodiments. Based on the embodiments of the present invention, all other embodiments obtained by those of ordinary skill in the art without creative efforts shall fall within the protection scope of the present invention.

[0035] Many specific details are set forth in the following description in order to provide a thorough understanding of the present invention, but the present invention may be practiced in other ways different from those described herein. Those skilled in the art can make similar extensions without departing from the connotation of the present invention. Therefore, the present invention is not limited by the specific embodiments disclosed below.

[0036] Embodiment 1

[0037] Refer to Figure 1 , which is an embodiment of the present invention, a maintenance information management method based on a multi-application software system, includes:

[0038] S1: Compile a maintenance work task book.

[0039] It should be noted that the preparation of the maintenance work task sheet includes the preparation of the maintenance specialty, maintenance system, maintenance equipment, maintenance content, and maintenance duration.

[0040] Furthermore, standardization is carried out when preparing the maintenance task sheet to facilitate the import and export of the task sheet and at the same time facilitate the statistics of the completion of the maintenance tasks. The content of the task sheet shall at least include: maintenance specialty, maintenance system, maintenance equipment, maintenance content, the percentage of the workload of this item in the total workload of this work or the number of man-days (actual working days) required for maintenance, planned start date (which can also be the number of working days after the start of maintenance). Among them, under the same specialty, it can be divided into multiple maintenance systems, within the same maintenance system, it can be divided into multiple maintenance equipment, and under the same maintenance equipment, it can be divided into multiple maintenance contents. For multiple maintenance systems, multiple maintenance equipment, and maintenance contents below the specialty, the percentage of the workload is filled in. The sum of the workload percentages of multiple maintenance systems is 100%, the sum of the workload percentages of multiple maintenance equipment is 100%, and the sum of the workload percentages of multiple maintenance contents is 100%. If the workload is calculated in man-days, it is calculated based on the man-days of each work, and 100% is the sum of the man-days of the work below this item. The calculation method for the percentage of each work is the man-days divided by the sum of the man-days.

[0041] When the maintenance work task needs to be carried out in association with other professional work tasks, after importing the data information of this task into the management platform, select the associated other professional work tasks in the platform to achieve work association. The association methods are divided into carried out before, carried out synchronously, and carried out after.

[0042] Furthermore, the previous expansion includes that a certain maintenance task must be completed before another task starts. It is usually used for tasks that need to provide basic conditions for subsequent work. For example, basic inspections or equipment disassembly in the maintenance system must be completed before specific repairs or component replacements of the equipment can be carried out. For example, equipment cleaning and inspection need to be completed before maintenance operations to ensure that the working environment meets the requirements and avoid secondary damage. After the task book is imported into the information management platform, the priority order of this task is clearly marked through the system to prevent subsequent tasks from being blocked due to insufficient conditions; The synchronous expansion includes that two or more maintenance tasks need to be carried out simultaneously within the same time period. This method is usually used for work that does not interfere with each other but needs to be completed within the same time window. For example, the lubrication and maintenance of mechanical equipment and the inspection of the electrical control part can be carried out synchronously. When it comes to tasks involving large equipment, such as turbine maintenance, the inspection of mechanical components and instrument monitoring equipment is carried out simultaneously. In the information management platform, by setting the association between tasks to be carried out synchronously, the division of labor of each specialty is clarified and a unified schedule is provided to ensure coordinated completion; The subsequent expansion includes that a certain task must be started after another task is completed. This method is usually used for tasks with logical dependencies. The installation of maintenance equipment must be carried out after the previous equipment maintenance and inspection are completed. For example, the load test of the equipment needs to be carried out after its maintenance and safety verification. The sequence of tasks is clearly set in the platform, and the platform automatically notifies relevant personnel to start subsequent work through real-time progress monitoring.

[0043] S2: According to the maintenance work task book, count the material list.

[0044] It should be noted that counting the material list includes counting the material name, material code, material price, material arrival situation, and material usage situation according to the maintenance content in the maintenance work task book.

[0045] Furthermore, the maintenance material plan list includes the material name, material code, material price, the corresponding maintenance work content for material usage, material arrival situation, and material usage situation. The maintenance material list can be imported into the system through the import method. The material arrival situation and material usage situation can be imported through the import method, or the arrival situation and usage situation can be selected in the system according to the maintenance progress. The arrival situation is only divided into two situations: arrived and not arrived. The material usage situation is divided into used, not used, and usage location. Each material in the material plan list is on a separate line, and the quantity is only 1. When there are multiple of the same material, they are separately divided into multiple lines, and the corresponding work content for usage and the usage and arrival situations are listed separately.

[0046] S3: Match the work ticket management with the maintenance work task book and count the maintenance progress.

[0047] It should be noted that matching the work ticket management with the maintenance work task sheet includes selecting the work content at the end of the maintenance task sheet for the work content items during the process of handling the maintenance work ticket.

[0048] When handling a maintenance work ticket, it is necessary to select the imported maintenance task sheet from the information management platform and associate it with the work content (specific maintenance task) at the end of the task sheet. This association method ensures that each work ticket can be accurately corresponding to a clear maintenance task. The system automatically verifies the uniqueness of the selected work content to avoid duplicate handling of work tickets or omission of tasks. If the selected work content has been completed, the system will prompt the task status to prevent duplicate operations; if the work content has not been started, the system will mark it as the to-be-maintained status, and the work ticket is linked with the maintenance information management platform in real time. After handling the work ticket, the associated maintenance task is automatically marked as the "underway" status. When the work ticket is terminated, the system automatically marks the work content it contains as "terminated" and updates the statistical data of the task completion situation. This automated function effectively reduces the workload of manual statistics and improves data accuracy at the same time. The platform dynamically tracks the unmaintained work content, and through the task list of unhandled work tickets, it timely prompts the management personnel to pay attention to the uncompleted maintenance tasks. By comparing the planned duration in the task sheet with the handling situation of the work ticket, the system can generate a report on lagging tasks to provide data support for work coordination.

[0049] Furthermore, the statistics of the maintenance progress include that the work ticket management obtains the maintained work, the ongoing maintenance work, and the unmaintained work, compares the maintenance duration in the maintenance task sheet, statistics the maintenance progress, and lists the lagging work list.

[0050] The system collects the status data of the work ticket in real time, including the start time, end time, actual working days, etc. According to the weight of each task in the task sheet (the proportion of man-days or the percentage of workload), it automatically calculates the completion percentage of the overall task, statistically calculates the completion progress by specialty, system or equipment respectively, dynamically updates the progress status of each task, and automatically summarizes the data to generate the latest statistical results. The system compares the actual work progress with the planned duration in the task sheet to generate a difference analysis of the planned completion progress and the actual completion progress, and analyzes the task completion situation according to time nodes, such as the daily completion volume, the weekly progress target achievement rate, etc.; for the tasks with lagging progress, the system automatically identifies and lists the lagging list, including the task name, planned completion time, number of lagging days, main hindering reasons, etc., and analyzes the lagging reasons in combination with factors such as material supply, personnel allocation, technical problems, etc., to generate a classification report on lagging reasons.

[0051] S4: Visualize the maintenance progress and feedback the defects in the maintenance progress.

[0052] It should be noted that visualizing the maintenance progress includes automatically generating a Gantt chart for maintenance work based on the maintenance duration and progress in the maintenance task book.

[0053] The system automatically draws a detailed Gantt chart based on the work plan, correlation relationships in the imported maintenance task book, and the task completion status updated in real time. The data includes task name, planned start time, planned completion time, actual start time, actual completion time, task duration, and status, showing the overall arrangement of all maintenance tasks, including the task distribution and time nodes of each specialty (such as electrical, mechanical, thermal engineering, etc.). The task status (not started, in progress, completed) is distinguished by color or marking, intuitively reflecting the overall progress. The task progress chart generated for specific equipment or systems is refined to individual tasks or subtasks, facilitating professionals to accurately track the execution of each work. The Gantt chart is linked to the system database in real time, and any change in task status (such as task completion, duration adjustment, etc.) will automatically update the chart to ensure the accuracy and timeliness of information; by comparing the planned work progress with the actual work progress, the Gantt chart includes marking the planned time range of tasks in the form of bar charts, and the color depth or line style indicates the importance or priority of tasks, which is displayed side by side with the planned progress, intuitively reflecting whether the tasks are ahead of schedule, on time, or behind schedule. The deviation between the actual start time and completion time will be highlighted in color to prompt potential problems; the dependency relationships between tasks are marked by arrows or lines in the Gantt chart, such as "preceding task", "synchronous task", "subsequent task", helping managers quickly understand the logical sequence of tasks; users can click on the work content icon in the Gantt chart to directly jump to the detailed information page of the task, including material usage, work progress, technical supervision progress, and defect elimination situation. The condition filtering function can be used to quickly locate specific tasks (such as lagging tasks, high-priority tasks), and the search function supports quick retrieval by fields such as task name, equipment number, and specialty classification.

[0054] Furthermore, the feedback on maintenance progress defects includes retrieving the defects of the maintenance unit in the defect management system. If it is determined that the defect belongs to the current maintenance work scope, it is marked as a defect to be processed;

[0055] If it does not belong to the current maintenance scope, it is marked as out of the maintenance scope;

[0056] Among the defects to be processed, if the work ticket status associated with the defect is ended, it is automatically marked as the defect being ended, and the defect handling completion time is feedback;

[0057] If the work ticket status is in progress, it is marked as the defect having started;

[0058] If the task progress in defect handling is within the maintenance duration, continuous tracking is carried out;

[0059] If the task progress in defect handling exceeds the maintenance duration, the system triggers an exception alert, lists the overdue tasks in defect handling in the lag list, analyzes the reasons in combination with the material list, and notifies the on-site personnel for technical supervision.

[0060] The system automatically retrieves the defect data in the defect management system and determines each defect. If the defect matches the current maintenance work scope, it is marked as a "defect to be processed" and associated with the corresponding maintenance task. If the defect does not belong to the current maintenance scope, it is marked as "out of maintenance scope", but the system will record its status for reference in subsequent maintenance plans.

[0061] The system retrieves the status of the work ticket associated with the defect in real time. If the status of the work ticket is "completed", the defect is automatically marked as "defect completed", and the actual completion time of the defect handling is recorded and fed back to ensure the closed-loop management of the task. When the status changes, the system verifies the content of the work ticket to ensure that the task items related to the associated defect have been completed. For example: check whether the detailed results of defect handling have been recorded, verify whether the repair or replacement of relevant equipment has been completed, and the system automatically writes the relevant information of defect handling into the log, including: defect number, associated work ticket number, actual completion time, handling responsible person, specific defect repair measures or alternative solutions. The log data can be used as the basis for subsequent audits and optimizations.

[0062] If the status of the associated work ticket is "in progress", the system marks the defect as "defect in progress". At this time, the system continuously tracks the progress of the defect handling task and updates its status in real time. The system dynamically tracks the progress of the tasks in defect handling and judges whether they are completed within the maintenance duration. If the progress of the defect handling task is within the maintenance duration, the system continues to track and update the status; if the progress of the defect handling task exceeds the maintenance duration, an exception alert is triggered. After the system detects that the defect handling task is overdue, it immediately triggers an alert, sends a notice to relevant management personnel, and automatically lists the overdue tasks in the "lag list". The system combines the material list to conduct a multi-dimensional analysis of the reasons for the overdue defect handling, including but not limited to: material arrival situation, material usage situation, personnel configuration situation. After the task is overdue, the overdue tasks are counted through the technical supervision management system; the responsible person information for each supervision task is recorded, including name, contact information, and responsibility description; the technical supervision management system supports an automatic reminder function to send notices to the responsible person when the task is approaching the deadline; and provides a dynamic display of the task completion progress to ensure that the responsible person clearly understands the current task status. The technical supervision management system automatically classifies the problems found in the technical supervision process and sorts them by priority according to severity, frequency, and impact scope; supports exporting the problem list for generating monthly or quarterly technical supervision reports; analyzes the recurring problems and proposes solutions.

[0063] Embodiment 2

[0064] For an embodiment of the present invention, the following technical solutions are provided: A maintenance information management system based on a multi-application software system, including: a task book compilation module, a material list statistics module, a maintenance progress statistics module, a defect feedback module, and a technical supervision module;

[0065] The task book compilation module compiles a maintenance work task book;

[0066] The material list statistics module statistics the material list according to the maintenance work task book;

[0067] The maintenance progress statistics module matches the work ticket management with the maintenance work task book and statistics the maintenance progress;

[0068] The defect feedback module visualizes the maintenance progress and feedbacks the defects in the maintenance progress;

[0069] The technical supervision module automatically associates the problems found in the annual technical supervision and the technical supervision plan related to the current maintenance, and generates the technical supervision content, unit, responsible person, completion status, and existing problems of the current maintenance.

[0070] This embodiment also provides a computing device applicable to a situation of a maintenance information management method based on a multi-application software system, including:

[0071] A memory and a processor; the memory is used to store computer-executable instructions, and the processor is used to execute the computer-executable instructions to implement a maintenance information management method based on a multi-application software system as proposed in the above embodiment.

[0072] The storage medium proposed in this embodiment and a maintenance information management method based on a multi-application software system proposed in the above embodiment belong to the same inventive concept. The technical details not described in detail in this embodiment can be referred to the above embodiment, and this embodiment has the same beneficial effects as the above embodiment.

[0073] When the above-mentioned functions are implemented in the form of software function units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on such understanding, the technical solution of the present invention, in essence, or the part that contributes to the prior art, or a part of this technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions for causing a computer device (which may be a personal computer, a server, or a network device, etc.) to execute all or part of the steps of the methods described in various embodiments of the present invention. The foregoing storage medium includes: various media that can store program codes, such as USB flash drives, mobile hard disks, read-only memories (ROM, Read-Only Memory), random access memories (RAM, Random Access Memory), magnetic disks, or optical discs.

[0074] The logic and / or steps described otherwise herein, for example, can be considered as a definite sequence list of executable instructions for implementing logical functions, and can be specifically implemented in any computer-readable medium for use by an instruction execution system, apparatus, or device (such as a computer-based system, a system including a processor, or other systems that can fetch and execute instructions from the instruction execution system, apparatus, or device), or used in combination with these instruction execution systems, apparatus, or devices. For the purposes of this specification, a "computer-readable medium" can be any device that can contain, store, communicate, propagate, or transport a program for use by or in connection with an instruction execution system, apparatus, or device.

[0075] It should be understood that each part of the present invention can be implemented by hardware, software, firmware, or a combination thereof. In the above embodiments, multiple steps or methods can be implemented by software or firmware stored in a memory and executed by a suitable instruction execution system. For example, if implemented by hardware, as in another embodiment, any one or a combination of the following well-known technologies in the art can be used: discrete logic circuits having logic gate circuits for implementing logical functions on data signals, application-specific integrated circuits having appropriate combinational logic gate circuits, programmable gate arrays (PGA), field-programmable gate arrays (FPGA), etc.

[0076] It should be noted that the above embodiments are only used to illustrate the technical solutions of the present invention and not to limit them. Although the present invention has been described in detail with reference to the preferred embodiments, those of ordinary skill in the art should understand that the technical solutions of the present invention can be modified or equivalently replaced without departing from the spirit and scope of the technical solutions of the present invention, and they should all be covered by the scope of the claims of the present invention.

Claims

1. A maintenance information management method based on a multi-application software system, characterized in that: include: Prepare maintenance work task book; Count the materials list according to the maintenance work task book; Match work ticket management with maintenance work task book and count maintenance progress; Visualize the maintenance progress and provide feedback on maintenance progress defects.

2. A maintenance information management method based on a multi-application software system as claimed in claim 1, characterized in that: The preparation of the maintenance work task book includes preparation of the maintenance specialty, maintenance system, maintenance equipment, maintenance content, and maintenance period.

3. A maintenance information management method based on a multi-application software system as claimed in claim 2, characterized in that: The statistical material list includes, according to the maintenance content in the maintenance work task book, the statistical material name, material code, material price, material arrival status, and material usage status.

4. A maintenance information management method based on a multi-application software system as claimed in claim 3, characterized in that: The matching of work ticket management with the maintenance work task book includes selecting the work content at the end of the maintenance task book as the work content item during the maintenance work ticket processing.

5. A maintenance information management method based on a multi-application software system as claimed in claim 4, characterized in that: The maintenance progress statistics include obtaining the work that has been maintained, the work that is being maintained, and the work that has not been maintained through work ticket management, comparing the maintenance period in the maintenance task book, counting the maintenance progress, and listing the delayed work list.

6. A maintenance information management method based on a multi-application software system as claimed in claim 5, characterized in that: The visualization of the maintenance progress includes automatically generating a Gantt chart of the maintenance work according to the maintenance duration and maintenance progress in the maintenance task book.

7. A maintenance information management method based on a multi-application software system as claimed in claim 6, characterized in that: The feedback of maintenance progress defects includes searching for defects of the maintenance unit in the defect management system, and if it is determined that the defect belongs to the current maintenance work scope, marking it as a defect to be processed; If it does not belong to the current maintenance scope, it will be marked as non-maintenance scope; For defects that need to be processed, if the status of the work ticket associated with the defect is ended, the defect is automatically marked as ended, and the completion time of defect processing is fed back; If the work ticket status is Started, mark the defect as Started; If the progress of the task in defect handling is within the maintenance period, continue to track; If the progress of the defect handling task exceeds the maintenance period, the system will trigger an abnormal alarm, add the overdue defect handling task to the delay list, analyze the reasons in combination with the material list, and notify the on-site personnel to conduct technical supervision.

8. A maintenance information management system based on a multi-application software system according to any one of claims 1 to 7, characterized in that: include: Modules for writing task orders, statistical material lists, statistical maintenance progress, defect feedback and technical supervision; The task book writing module is used to write the maintenance work task book; The material list statistics module counts the material list according to the maintenance work task book; The maintenance progress statistics module matches the work ticket management with the maintenance work task book and counts the maintenance progress; The defect feedback module visualizes the maintenance progress and provides feedback on maintenance progress defects; The technical supervision module automatically associates the annual technical supervision findings and technical supervision plan related to this maintenance, and generates the technical supervision content, unit, responsible person, completion status and existing problems of this maintenance.

9. A computer device comprising a memory and a processor, wherein the memory stores a computer program, wherein: When the processor executes the computer program, the steps of a maintenance information management method based on a multi-application software system as described in any one of claims 1 to 7 are implemented.

10. A computer-readable storage medium having a computer program stored thereon, characterized in that: When the computer program is executed by a processor, the steps of a maintenance information management method based on a multi-application software system as described in any one of claims 1 to 7 are implemented.

Images