Maintenance business document generation method and device, computer equipment, readable storage medium and program product

Abstract

The invention relates to the technical field of computers, in particular to a maintenance business document generation method and device, computer equipment, a readable storage medium and a program product. The method comprises the following steps: when a preset maintenance plan is called each time, obtaining a plurality of maintenance items included in the maintenance plan, and determining a current maintenance plan execution date of each maintenance item according to a previous maintenance actual execution date corresponding to each maintenance item and a maintenance strategy associated with each maintenance item; according to the current maintenance plan execution date of each maintenance project, obtaining the current receipt generation date of each maintenance project; and if the current receipt generation date of any maintenance item expires, generating the current maintenance business receipt of any maintenance item according to the maintenance standard package associated with any maintenance item and the current maintenance plan execution date. By adopting the method, the preparation efficiency of the maintenance business document can be improved, and the workload of maintenance planning personnel is reduced.

Description

Technical Field

[0001] The present application relates to the field of computer technology, and in particular to a method, device, computer equipment, computer-readable storage medium and computer program product for generating a maintenance service document. Background Art

[0002] As the demand for maintenance of power equipment increases day by day, maintenance data can be recorded through maintenance business documents during maintenance, which helps to establish a standardized maintenance process and ensure that each step is verified and recorded as necessary.

[0003] Currently, maintenance business documents for power equipment are mainly generated through Enterprise Resource Planning (ERP) software or Enterprise Asset Management (EAM) software.

[0004] However, the enterprise resource planning software or enterprise asset management software has not been reasonably optimized according to customer categories, and there is a problem of high learning costs. In addition, the hardware costs and software licensing fees required to run the enterprise resource planning software or enterprise asset management software are also relatively high. Updating and maintaining the enterprise resource planning software or enterprise asset management software will also incur additional costs. Summary of the invention

[0005] Based on this, it is necessary to provide a method, device, computer equipment, computer-readable storage medium and computer program product for generating a maintenance business document in response to the above technical problems.

[0006] In a first aspect, the present application provides a method for generating a maintenance service document, comprising:

[0007] Each time a preset maintenance plan is called, a number of maintenance items included in the maintenance plan are obtained, and the execution date of the current maintenance plan for each maintenance item is determined according to the actual execution date of the last maintenance corresponding to each maintenance item and the maintenance strategy associated with each maintenance item;

[0008] According to the execution date of the maintenance plan for each maintenance item, the date of generating the document for each maintenance item is obtained;

[0009] If the current document generation date of any maintenance item expires, a current maintenance business document for the maintenance item is generated according to the maintenance standard package associated with the maintenance item and the current maintenance plan execution date.

[0010] In one embodiment, determining the current maintenance plan execution date of each maintenance item according to the actual execution date of the last maintenance corresponding to each maintenance item and the maintenance strategy associated with each maintenance item includes:

[0011] For any maintenance item, according to the maintenance strategy associated with the maintenance item, obtain the execution date of the last maintenance plan corresponding to the maintenance item;

[0012] When the actual execution date of the last maintenance corresponding to any maintenance item is different from the execution date of the last maintenance plan, determining the last offset corresponding to any maintenance item;

[0013] The execution date of the current maintenance plan of any maintenance item is determined according to the size relationship between the last offset and the completion tolerance corresponding to any maintenance item.

[0014] In one embodiment, determining the last offset corresponding to any maintenance item includes:

[0015] According to the actual execution date of the last maintenance and the execution date of the last maintenance plan, the last offset date number is obtained;

[0016] Obtaining the maintenance period interval corresponding to any maintenance item;

[0017] According to the last offset date and the maintenance cycle interval, the last offset corresponding to any maintenance item is obtained.

[0018] In one embodiment, determining the execution date of the current maintenance plan of any maintenance item according to the size relationship between the last offset and the completion tolerance corresponding to any maintenance item includes:

[0019] Obtaining the maintenance period interval corresponding to any maintenance item;

[0020] Obtaining a completion offset corresponding to any maintenance item;

[0021] When the last offset is greater than the completion tolerance, determining the current maintenance plan execution date of any maintenance item according to the last actual maintenance execution date, the maintenance cycle interval and the completion offset;

[0022] When the last offset is less than the completion tolerance, the current maintenance plan execution date of any maintenance item is determined according to the last maintenance plan execution date and the maintenance cycle interval.

[0023] In one embodiment, obtaining the maintenance period interval corresponding to any maintenance item includes:

[0024] Obtaining a plan identifier corresponding to any maintenance item;

[0025] When the plan is identified as being based on the operation history, obtaining measurement information corresponding to any maintenance item;

[0026] A maintenance period interval corresponding to any maintenance item is obtained according to the measurement information.

[0027] In one embodiment, obtaining the current document generation date of each maintenance item according to the current maintenance plan execution date of each maintenance item includes:

[0028] According to the maintenance strategy associated with each maintenance item, the call period corresponding to each maintenance item is obtained;

[0029] According to the call-up period corresponding to each maintenance item and the execution date of this maintenance plan, the current document generation date of each maintenance item is obtained.

[0030] In a second aspect, the present application also provides a device for generating a maintenance service document, comprising:

[0031] A planned execution date acquisition module is used to obtain a number of maintenance items included in the maintenance plan each time a preset maintenance plan is called, and determine the current maintenance plan execution date of each maintenance item according to the actual execution date of the last maintenance corresponding to each maintenance item and the maintenance strategy associated with each maintenance item;

[0032] The document generation date acquisition module is used to obtain the current document generation date of each maintenance project according to the current maintenance plan execution date of each maintenance project;

[0033] The maintenance business document generation module is used to generate the current maintenance business document of any maintenance project according to the maintenance standard package associated with the any maintenance project and the execution date of the current maintenance plan if the current document generation date of any maintenance project expires.

[0034] In a third aspect, the present application further provides a computer device, wherein the computer device comprises a memory and a processor, wherein the memory stores a computer program, and the processor executes the above method.

[0035] In a fourth aspect, the present application further provides a computer-readable storage medium, wherein a computer program is stored on the computer-readable storage medium, and the computer program is executed by a processor to execute the above method.

[0036] In a fifth aspect, the present application further provides a computer program product, wherein the computer program product comprises a computer program, and the computer program is executed by a processor to execute the above method.

[0037] The above-mentioned maintenance service document generation method, device, computer equipment, computer-readable storage medium and computer program product, each time a pre-set maintenance plan is called, obtains several maintenance items included in the maintenance plan, and determines the execution date of the current maintenance plan for each maintenance item based on the actual execution date of the last maintenance corresponding to each maintenance item and the maintenance strategy associated with each maintenance item; obtains the current document generation date for each maintenance item based on the current maintenance plan execution date for each maintenance item; if the current document generation date for any maintenance item expires, generates the current maintenance service document for any maintenance item based on the maintenance standard package associated with any maintenance item and the execution date of the current maintenance plan. The present application can call a pre-set maintenance plan to automatically generate a maintenance service document, thereby improving the efficiency of preparing maintenance service documents and reducing the workload of maintenance plan personnel. BRIEF DESCRIPTION OF THE DRAWINGS

[0038] In order to more clearly illustrate the technical solutions in the embodiments of the present application or related technologies, the drawings required for use in the embodiments of the present application or related technical descriptions will be briefly introduced below. Obviously, the drawings described below are only some embodiments of the present application. For ordinary technicians in this field, other related drawings can be obtained based on these drawings without paying creative work.

[0039] Figure 1 It is an application environment diagram of a method for generating a maintenance business document in one embodiment;

[0040] Figure 2 A schematic diagram of a process for generating a maintenance service document in one embodiment;

[0041] Figure 3 A schematic diagram of a configuration parameter interface for a maintenance item in an embodiment;

[0042] Figure 4 A schematic diagram of a configuration parameter interface of a maintenance plan type in an embodiment;

[0043] Figure 5 A schematic diagram of a configuration parameter interface of a single-cycle maintenance plan in an embodiment;

[0044] Figure 6 A schematic diagram of a configuration parameter interface of a maintenance standard package in an embodiment;

[0045] Figure 7 A schematic diagram of a configuration parameter interface of a maintenance strategy in an embodiment;

[0046] Figure 8 A schematic diagram of the process setting of a maintenance standard package in one embodiment;

[0047] Fig. 9A schematic diagram of a single-cycle plan in an embodiment;

[0048] Fig.10 A schematic diagram of a flow chart of a method for generating a maintenance service document in another embodiment;

[0049] Fig.11 Another schematic diagram of a process for generating a maintenance service document in one embodiment;

[0050] Fig.12 It is a structural block diagram of a device for generating a maintenance service document in one embodiment;

[0051] Fig.13 FIG. 4 is a diagram showing the internal structure of a computer device in one embodiment. DETAILED DESCRIPTION

[0052] In order to make the purpose, technical solution and advantages of the present application more clearly understood, the present application is further described in detail below in conjunction with the accompanying drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and are not used to limit the present application.

[0053] The present application embodiment provides a method for generating a maintenance service document, which can be executed by a computer device, such as Figure 1 As shown, the computer device can call a pre-set maintenance plan to generate a maintenance business document for any maintenance project. It is understandable that the computer device can be implemented through a server, a terminal, or an interactive system between a terminal and a server. In this embodiment, the method includes Figure 2 The steps shown are:

[0054] Step S201, each time a preset maintenance plan is called, a number of maintenance items included in the maintenance plan are obtained, and the current maintenance plan execution date of each maintenance item is determined according to the actual execution date of the last maintenance corresponding to each maintenance item and the maintenance strategy associated with each maintenance item.

[0055] A maintenance plan is a description of the maintenance or inspection tasks that need to be performed on the maintenance object (power equipment). The maintenance plan also describes the scope and date information of the maintenance tasks. A maintenance plan can include one or more maintenance items. The configuration parameter interface of the maintenance items is as follows: Figure 3 shown.

[0056] The maintenance task can be the preventive maintenance service of power equipment, which can include the following three business scenarios: regular maintenance of multiple power equipment at different times, each power equipment needs to generate a separate business document; regular maintenance of multiple power equipment at the same time, each power equipment needs to generate a separate business document; regular maintenance of multiple power equipment at the same time, multiple power equipment share one business document.

[0057] The configuration parameter interface of the maintenance plan type is as follows Figure 4 As shown, it mainly includes status, type code, maintenance plan type name and generated object. The status is used to control whether the maintenance plan type is enabled. Only maintenance plan types that are enabled can be used. Type code and maintenance plan type name are used to classify maintenance plans from a business perspective, such as regular maintenance plans, predictive maintenance plans and regular test maintenance plans. There are three options for generated objects, all of which are pre-made types, including maintenance notice, maintenance work order and maintenance notice + maintenance work order. This parameter is used to control what type of business document is generated when the corresponding type of maintenance plan is called.

[0058] Maintenance plans can be divided into three categories: single-cycle plans, strategic plans, and multi-counter plans. In single-cycle plans and strategic plans, you can use time-based or operation history-based maintenance cycles. Multi-counter plans are suitable for periodic maintenance based on operation history. To meet different business needs, you can provide some configuration parameters to define the rules for generating business documents for maintenance plans.

[0059] like Figure 5 As shown, the single-cycle maintenance plan contains the following control parameter information: maintenance plan type, cycle / unit, delayed completion tolerance, delayed completion offset, early completion tolerance, early completion offset, plan period / unit, plan identifier, calendar, and check whether the previous work order is completed. The input value of delayed completion offset is a percentage. In the maintenance plan, the offset parameter can be used to affect the calculation logic of the next due date. The offset is only effective when the difference in the completion date meets the setting of delayed completion tolerance; similarly, when the work order generated by the maintenance plan is executed in advance and the difference in the early execution meets the set early completion tolerance, the early completion offset parameter can be used to affect the calculation logic of the next due date; the parameter of checking whether the previous work order is completed is used to control whether the maintenance plan should check the completion status of the previous maintenance business document when generating the maintenance business document. If this parameter is checked, the maintenance plan will only generate the next maintenance business document when the previous maintenance business document is completed.

[0060] In addition to the common control parameters in a single-cycle maintenance plan, the control parameter information of a strategic plan also includes the following special information: maintenance strategy, maintenance items, and maintenance standard packages. A strategic plan must be created with reference to a maintenance strategy, and the maintenance items and maintenance standard packages associated with the strategic plan must use the same maintenance strategy.

[0061] The multi-counter plan contains the following control parameter information: maintenance cycle set, maintenance interval sequence number, measurement point, advance buffer days and operation type. The maintenance cycle set is a collection of multiple maintenance cycle intervals, including the maintenance cycle set code, name, cycle number, cycle length and cycle unit. You can create a multi-counter plan with reference to the maintenance cycle set to facilitate the maintenance of the maintenance cycle intervals in the multi-counter plan. In the multi-counter plan, you can delete unused maintenance cycles or add new maintenance cycles. The maintenance interval sequence number is used to number the maintenance cycle interval, which will be assigned to the maintenance project. The measurement point is used to associate the maintenance cycle interval. The multi-counter plan determines whether to generate a maintenance business document by monitoring whether the measurement record corresponding to the measurement point meets the maintenance cycle interval. The advance buffer days are used to control the generation of maintenance business documents a few days in advance before the actual execution date of the maintenance. The operation type includes "or" and "and", which are used to control the generation of maintenance business documents when one or all conditions in the maintenance cycle set are met.

[0062] The maintenance strategy and maintenance standard package associated with each maintenance item in the maintenance task can be used to obtain a pre-set maintenance plan. The maintenance strategy defines the priority order of the maintenance tasks, the frequency of the maintenance tasks, and the adjustment parameters. The maintenance strategy also contains parameter information about the relevant execution date. The maintenance strategy can be assigned to multiple maintenance standard packages and maintenance plans. Figure 6 As shown in the figure, the maintenance standard package defines the specific process, spare parts, tools, risk and safety measures and drawings and documents of the maintenance work item. The maintenance work item describes which regular preventive maintenance work needs to be performed. In a certain technical object or a group of technical objects, the maintenance standard package can be assigned to the maintenance project.

[0063] like Figure 7 As shown, the maintenance strategy includes plan identification, cycle unit, call period, delayed completion tolerance, early completion tolerance, cycle length and priority information. The cycle unit is the unit of the execution interval of the regular maintenance task, usually a time unit, such as day, week, month or hour, or a kilometer; the cycle length is used to set the execution interval of the regular maintenance task, such as every 30 days; the priority is used to define the priority of the corresponding periodic maintenance task, which determines how many maintenance business documents should be generated during the corresponding cycle interval.

[0064] When a maintenance standard package is associated with a maintenance strategy, you can set an execution interval for the process in the maintenance standard package. The execution interval information comes from the cycle length information defined in the maintenance strategy. Figure 8 As shown in the figure, in the actual preventive maintenance of the pump, an appearance inspection is required every month, an internal inspection is required every three months, and a gear wear inspection is required every 12 months. When this maintenance standard package is applied to the maintenance plan, the maintenance plan can generate work orders containing different processes according to different cycle intervals, that is, a work order containing the first two processes in the figure below is generated every month, a work order containing the first three processes in the figure below is generated every three months, and a work order containing all the processes in the figure below is generated every 12 months.

[0065] Each maintenance item needs to be maintained periodically, so each maintenance item has several corresponding actual maintenance execution dates and maintenance plan execution dates. The current maintenance plan execution date of each maintenance item can be determined based on the actual last maintenance execution date corresponding to each maintenance item and the maintenance strategy associated with each maintenance item.

[0066] The steps involved in obtaining the execution date of the maintenance plan can be called maintenance plan scheduling. Maintenance plan scheduling can be performed based on the maintenance cycle interval defined in the maintenance plan, the start date, or the initial readings of the measurement points associated with the multi-counter plan, and calculate the day in the future when the maintenance business document should be generated.

[0067] When scheduling the maintenance plan for the first time, the periodic maintenance work can be triggered based on the start date of the maintenance plan or the initial reading of the measurement point with the time axis as the core. For each maintenance plan scheduling, the planned start date of the maintenance business document can be calculated based on the control parameters in the maintenance plan and the cycle number associated with the maintenance project, and the corresponding maintenance business document can be generated when it expires. The specific maintenance business document type depends on the type of maintenance plan. The planning and scheduling of a single-cycle plan is as follows: Fig. 9 shown.

[0068] You can define periodic scheduled jobs, such as calling a pre-set maintenance plan regularly every day or every week.

[0069] Step S202, obtaining the current document generation date of each maintenance item according to the current maintenance plan execution date of each maintenance item.

[0070] Maintenance business documents can be generated a few days in advance of the maintenance plan execution date, so the document generation date of each maintenance project can be obtained based on the maintenance plan execution date of each maintenance project.

[0071] Step S203: if the current document generation date of any maintenance item is due, a current maintenance business document of any maintenance item is generated according to the maintenance standard package associated with any maintenance item and the current maintenance plan execution date.

[0072] When the document generation date of the maintenance project expires, it indicates that the maintenance business document of the maintenance project can be generated.

[0073] Maintenance business documents may include maintenance notifications and maintenance work orders. Maintenance notifications are used to report abnormal conditions of power equipment to the maintenance department, and also record the execution results of maintenance tasks for future analysis. Maintenance work orders are used to prepare detailed information and corresponding documents for maintenance tasks, including the maintenance task process, spare parts, tools, risk safety measures, responsible departments, responsible personnel and planned costs.

[0074] When generating the current maintenance business document for any maintenance project, the maintenance standard package associated with any maintenance project and the execution date of the current maintenance plan will be automatically brought into the generated current maintenance business document.

[0075] In the above-mentioned maintenance business document generation method, a pre-set maintenance plan can be called to automatically generate maintenance business documents, which improves the preparation efficiency of maintenance business documents and reduces the workload of maintenance planners. In addition, the maintenance standard package standardizes the maintenance work, spare parts, tools, risks and safety measures and drawing documents of specific maintenance scenarios, reduces unnecessary trial and error and rework, realizes one-stop maintenance and multiple calls, reduces the workload of maintenance preparation personnel, and also speeds up the preparation efficiency of maintenance business documents.

[0076] In one of the embodiments, the current maintenance plan execution date of each maintenance project is determined based on the actual execution date of the last maintenance corresponding to each maintenance project and the maintenance strategy associated with each maintenance project. The specific steps are as follows: for any maintenance project, the last maintenance plan execution date corresponding to any maintenance project is obtained based on the maintenance strategy associated with any maintenance project; when the actual execution date of the last maintenance corresponding to any maintenance project is different from the last maintenance plan execution date, the last offset corresponding to any maintenance project is determined; based on the relationship between the last offset and the completion tolerance corresponding to any maintenance project, the current maintenance plan execution date of any maintenance project is determined.

[0077] The maintenance strategy contains parameter information of the relevant execution date, so the last maintenance plan execution date corresponding to any maintenance item can be obtained from the maintenance strategy associated with any maintenance item.

[0078] The completion tolerance corresponding to each maintenance project can be determined according to the actual situation. The completion tolerance includes delayed completion tolerance and early completion tolerance.

[0079] The delayed completion tolerance is used to set the value by which the planned execution date of subsequent maintenance business documents will be affected when the offset of the delayed completion maintenance business document reaches a certain value. The percentage of the delayed completion tolerance is calculated based on the minimum interval time in the maintenance strategy. For example, for a maintenance project that is executed every 30 days, the delayed completion tolerance is set to 50%, that is, 15 days. When the actual execution date of the maintenance project minus the planned execution date is greater than 15 days, it exceeds the set delayed completion tolerance parameter. At this time, the delayed completion offset can be combined to calculate the next planned execution date of the maintenance project.

[0080] The early completion tolerance is used to set the impact on the planned execution date of subsequent maintenance business documents when the offset of the early completion maintenance business document reaches a certain value. The impact on the planned execution date of subsequent maintenance business documents depends on the parameter setting of the early completion offset. The percentage of the early completion tolerance is calculated based on the minimum interval time in the maintenance strategy.

[0081] When the actual execution date of the last maintenance corresponding to any maintenance item is different from the execution date of the last maintenance plan, it indicates that the last maintenance plan was not executed on the execution date of the last maintenance plan. At this time, the last offset corresponding to any maintenance item can be determined based on the actual execution date of the last maintenance and the execution date of the last maintenance plan; the last offset can be a delayed offset or an early offset; the current maintenance plan execution date of any maintenance item can be determined based on the relationship between the last offset and the completion tolerance corresponding to any maintenance item.

[0082] In this embodiment, when the actual execution date of the last maintenance corresponding to any maintenance item is different from the execution date of the last maintenance plan, the last offset corresponding to any maintenance item is determined; based on the size relationship between the last offset and the completion tolerance corresponding to any maintenance item, the current maintenance plan execution date of any maintenance item is determined, which can make the interval between the maintenance plan execution dates more reasonable and improve the inspection effect of the maintenance task.

[0083] In one of the embodiments, the last offset corresponding to any maintenance item is determined, and the specific steps are as follows: according to the actual execution date of the last maintenance and the execution date of the last maintenance plan, the last offset date number is obtained; the maintenance cycle interval corresponding to any maintenance item is obtained; according to the last offset date number and the maintenance cycle interval, the last offset corresponding to any maintenance item is obtained.

[0084] Exemplarily, for maintenance project A, according to the actual execution date of the last maintenance corresponding to maintenance project A on June 21, 2024 and the last planned execution date of maintenance on June 1, 2024, the last offset date number is 21 days; the maintenance cycle interval corresponding to maintenance project A is 30 days; the last offset date number 21 days is divided by the maintenance cycle interval of 30 days, and the last offset amount corresponding to maintenance project A is 70%.

[0085] In this embodiment, the last offset date is obtained according to the actual execution date of the last maintenance and the execution date of the last maintenance plan; and the last offset value corresponding to any maintenance item is obtained according to the last offset date and the maintenance cycle interval.

[0086] In one of the embodiments, the execution date of the current maintenance plan for any maintenance project is determined based on the size relationship between the last offset and the completion tolerance corresponding to any maintenance project, and the specific steps are as follows: obtain the maintenance cycle interval corresponding to any maintenance project; obtain the completion offset corresponding to any maintenance project; when the last offset is greater than the completion tolerance, the execution date of the current maintenance plan for any maintenance project is determined based on the actual execution date of the last maintenance, the maintenance cycle interval and the completion offset; when the last offset is less than the completion tolerance, the execution date of the current maintenance plan for any maintenance project is determined based on the last maintenance plan execution date and the maintenance cycle interval.

[0087] The completion offset corresponding to the maintenance project can be preset according to actual conditions.

[0088] When the last offset is greater than the completion tolerance, the current maintenance plan execution date of any maintenance item can be determined based on the actual execution date of the last maintenance, the maintenance cycle interval and the completion offset; when the last offset is equal to the completion tolerance, the current maintenance plan execution date of any maintenance item can also be determined based on the actual execution date of the last maintenance, the maintenance cycle interval and the completion offset; when the last offset is less than the completion tolerance, the current maintenance plan execution date of any maintenance item can be determined based on the last maintenance plan execution date and the maintenance cycle interval.

[0089] Exemplarily, the maintenance cycle interval corresponding to maintenance project A is 30 days. When the last offset is 70%, which is greater than the completion tolerance of 50%, according to the actual execution date of the last maintenance on June 20, 2024, the maintenance cycle interval of 30 days and the completion offset of 50%, the current maintenance plan execution date of maintenance project A is determined as: the actual execution date of the last maintenance on June 20, 2024 + the maintenance cycle interval of 30 days × the completion offset of 50% = July 5, 2024. When the last offset is 50%, which is equal to the completion tolerance of 50%, according to the actual execution date of the last maintenance on June 20, 2024, the maintenance cycle interval of 30 days and the completion offset of 50%, the current maintenance plan execution date of maintenance project A is determined as: the actual execution date of the last maintenance on June 20, 2024 + the maintenance cycle interval of 30 days × the completion offset of 50% = July 5, 2024. When the last offset is 40%, which is less than the completion tolerance of 50%, the execution date of the current maintenance plan for maintenance project A is determined to be July 1, 2024, based on the execution date of the last maintenance plan on June 1, 2024 and the maintenance cycle interval of 30 days.

[0090] In this embodiment, based on the size relationship between the last offset and the completion tolerance, it is determined whether to use the actual execution date of the last maintenance or the last planned execution date of the maintenance to determine the current maintenance plan execution date of any maintenance item. This can make the interval between the maintenance plan execution dates more reasonable and improve the inspection effect of the maintenance task.

[0091] In one of the embodiments, the maintenance cycle interval corresponding to any maintenance item is obtained, and the specific steps are as follows: obtain a plan identifier corresponding to any maintenance item; when the plan identifier is based on the operation history, obtain measurement information corresponding to any maintenance item; and obtain the maintenance cycle interval corresponding to any maintenance item based on the measurement information.

[0092] The plan identification corresponding to each maintenance item can be obtained according to the maintenance strategy associated with each maintenance item.

[0093] The plan identifier can include four types: "by natural day", "by fixed date", "by office calendar" and "by operation history". The "by natural day" plan identifier indicates that the maintenance cycle of the maintenance project is based on natural days, for example, a maintenance inspection is performed every 30 days. The "by fixed date" plan identifier indicates that a regular maintenance inspection is performed on the fixed Nth day of each month, for example, a maintenance inspection is performed on the 1st of each month. Since the number of days in February may be 28 or 29 days, and March is 31 days, when the fixed date is greater than the 28th of each month, an option of the last day of each month can be provided, that is, regular maintenance inspections are performed on the last day of each month. The "by office calendar" plan identifier indicates that an office calendar is formulated according to actual business needs. The office calendar defines which days are working days and which days are rest days. According to the defined rules, only regular inspection tasks with maintenance plan start dates on working days are generated. As a type of master data, the office calendar can be edited and published by business users and then associated with the maintenance strategy. The "by operation history" plan logo indicates that regular inspection tasks are carried out according to the operation history of the power equipment or maintenance object. For example, a maintenance inspection is carried out every 5,000 kilometers of a vehicle or every 2,000 hours of operation of a pump.

[0094] When the plan is marked as being based on the operation history, the measurement information corresponding to any maintenance item can be obtained; based on the measurement information, the maintenance cycle interval corresponding to any maintenance item can be obtained.

[0095] When the plan indicator corresponding to the maintenance item is based on the operation history, the maintenance cycle interval corresponding to the maintenance item is not a fixed number of days. In this case, the maintenance cycle will change according to the measurement information.

[0096] For example, when the plan is marked as according to the operating history, the measurement information corresponding to maintenance item B can be obtained: the vehicle has traveled 1,000 kilometers, the pump has run for 400 hours, and the current measurement time is March 1, 2024; the vehicle has traveled 6,000 kilometers, the pump has run for 2,400 hours, and the current measurement time is July 1, 2024. Based on the measurement information, it can be obtained that the maintenance cycle interval corresponding to maintenance item B is 120 days.

[0097] In this embodiment, when the plan identification corresponding to the maintenance item is based on the operation history, the measurement information corresponding to the maintenance item can be used to obtain a relatively accurate maintenance cycle interval corresponding to the maintenance item.

[0098] In one of the embodiments, the document generation date of each maintenance project is obtained according to the execution date of the current maintenance plan of each maintenance project. The specific steps are as follows: according to the maintenance strategy associated with each maintenance project, the call period corresponding to each maintenance project is obtained; according to the call period corresponding to each maintenance project and the execution date of the current maintenance plan, the document generation date of each maintenance project is obtained.

[0099] The maintenance strategy includes the call period corresponding to each maintenance item, so the call period corresponding to each maintenance item can be obtained according to the maintenance strategy associated with each maintenance item.

[0100] The call period is used to control how many days in advance of the maintenance plan execution date the maintenance business document is generated. The call period can be a percentage. For example, for a regular maintenance project that is executed every 30 days, if the call period is set to 50%, the maintenance business document of the maintenance project will be generated 15 days in advance of the corresponding maintenance plan execution date.

[0101] In this embodiment, according to the call period corresponding to each maintenance item and the execution date of this maintenance plan, a relatively accurate current document generation date of each maintenance item can be obtained.

[0102] In order to better understand the above method, an application example of the method for generating a maintenance service document of the present application is described in detail below.

[0103] like Fig.10 and Fig.11 As shown, a pre-set maintenance plan is obtained based on the maintenance strategy and maintenance standard package (maintenance standard package) associated with each maintenance project. When the maintenance plan is initially scheduled, the planned start date of the maintenance business document can be calculated based on the control parameters in the maintenance plan and the cycle sequence number associated with the maintenance project. After the maintenance plan is initially scheduled, periodic scheduled jobs (which can be called maintenance plan calls) can be defined, such as calling the pre-set maintenance plan regularly every day or every week.

[0104] Each time a preset maintenance plan is called, several maintenance items included in the maintenance plan are obtained. For any maintenance item, the last maintenance plan execution date corresponding to any maintenance item is obtained according to the maintenance strategy associated with any maintenance item; when the actual execution date of the last maintenance corresponding to any maintenance item is different from the last maintenance plan execution date, the last offset date number is obtained according to the actual execution date of the last maintenance and the last maintenance plan execution date; the maintenance cycle interval corresponding to any maintenance item is obtained; the last offset corresponding to any maintenance item is obtained according to the last offset date number and the maintenance cycle interval; the maintenance cycle interval corresponding to any maintenance item is obtained; when the last offset is greater than the completion tolerance, the current maintenance plan execution date of any maintenance item is determined according to the actual execution date of the last maintenance and the maintenance cycle interval; when the last offset is less than the completion tolerance, the current maintenance plan execution date of any maintenance item is determined according to the last maintenance plan execution date and the maintenance cycle interval.

[0105] According to the maintenance strategy associated with each maintenance project, the call period corresponding to each maintenance project is obtained; according to the call period corresponding to each maintenance project and the execution date of this maintenance plan, the current document generation date of each maintenance project is obtained. If the current document generation date of any maintenance project expires, the current maintenance business document of any maintenance project is generated according to the maintenance standard package associated with any maintenance project and the execution date of this maintenance plan. The maintenance business document may include a maintenance notice and a maintenance work order. In this embodiment, through the scheduled call function of the maintenance plan, a maintenance business document that meets the business needs can be automatically generated according to the maintenance plan, thereby reducing the workload of the maintenance planner.

[0106] It should be understood that, although the various steps in the flowcharts involved in the above-mentioned embodiments are displayed in sequence according to the indication of the arrows, these steps are not necessarily executed in sequence according to the order indicated by the arrows. Unless there is a clear explanation in this article, the execution of these steps does not have a strict order restriction, and these steps can be executed in other orders. Moreover, at least a part of the steps in the flowcharts involved in the above-mentioned embodiments can include multiple steps or multiple stages, and these steps or stages are not necessarily executed at the same time, but can be executed at different times, and the execution order of these steps or stages is not necessarily to be carried out in sequence, but can be executed in turn or alternately with other steps or at least a part of the steps or stages in other steps.

[0107] Based on the same inventive concept, the embodiment of the present application also provides a device for generating a maintenance service document for implementing the above-mentioned method for generating a maintenance service document. The implementation scheme for solving the problem provided by the device is similar to the implementation scheme recorded in the above-mentioned method, so the specific limitations in the embodiments of one or more maintenance service document generation devices provided below can refer to the limitations of the maintenance service document generation method above, and will not be repeated here.

[0108] In an exemplary embodiment, Fig.12 As shown, a device for generating a maintenance service document is provided, wherein:

[0109] The planned execution date acquisition module 1201 is used to acquire several maintenance items included in the maintenance plan each time a preset maintenance plan is called, and determine the current maintenance plan execution date of each maintenance item according to the actual execution date of the last maintenance corresponding to each maintenance item and the maintenance strategy associated with each maintenance item;

[0110] The document generation date acquisition module 1202 is used to obtain the current document generation date of each maintenance item according to the current maintenance plan execution date of each maintenance item;

[0111] The maintenance business document generation module 1203 is used to generate a maintenance business document for any maintenance project according to the maintenance standard package associated with the maintenance project and the execution date of the maintenance plan if the document generation date of the maintenance project expires.

[0112] In one of the embodiments, the planned execution date acquisition module 1201 is also used to: for any maintenance project, obtain the last maintenance planned execution date corresponding to any maintenance project according to the maintenance strategy associated with the any maintenance project; when the last maintenance actual execution date corresponding to any maintenance project is different from the last maintenance planned execution date, determine the last offset corresponding to any maintenance project; determine the current maintenance planned execution date of any maintenance project according to the relationship between the last offset and the completion tolerance corresponding to any maintenance project.

[0113] In one embodiment, the planned execution date acquisition module 1201 is also used to: obtain the last offset date number based on the actual execution date of the last maintenance and the planned execution date of the last maintenance; obtain the maintenance cycle interval corresponding to any maintenance item; and obtain the last offset amount corresponding to any maintenance item based on the last offset date number and the maintenance cycle interval.

[0114] In one embodiment, the planned execution date acquisition module 1201 is also used to: obtain the maintenance cycle interval corresponding to any one of the maintenance items; obtain the completion offset corresponding to any one of the maintenance items; when the last offset is greater than the completion tolerance, determine the current maintenance planned execution date of any one of the maintenance items based on the actual execution date of the last maintenance, the maintenance cycle interval and the completion offset; when the last offset is less than the completion tolerance, determine the current maintenance planned execution date of any one of the maintenance items based on the last maintenance planned execution date and the maintenance cycle interval.

[0115] In one embodiment, the planned execution date acquisition module 1201 is also used to: obtain the plan identifier corresponding to any maintenance item; when the plan identifier is according to the operation history, obtain the measurement information corresponding to any maintenance item; and obtain the maintenance cycle interval corresponding to any maintenance item based on the measurement information.

[0116] In one embodiment, the document generation date acquisition module 1202 is also used to: obtain the call period corresponding to each maintenance project according to the maintenance strategy associated with each maintenance project; and obtain the current document generation date of each maintenance project according to the call period corresponding to each maintenance project and the execution date of this maintenance plan.

[0117] Each module in the above maintenance service document generation device can be implemented in whole or in part by software, hardware, or a combination thereof. Each module can be embedded in or independent of a processor in a computer device in the form of hardware, or can be stored in a memory in a computer device in the form of software, so that the processor can call and execute operations corresponding to each module.

[0118] In an exemplary embodiment, a computer device is provided. The computer device may be a server, and its internal structure diagram may be as shown in FIG. Fig.13 As shown. The computer device includes a processor, a memory, an input / output interface (Input / Output, referred to as I / O) and a communication interface. The processor, the memory and the input / output interface are connected through a system bus, and the communication interface is connected to the system bus through the input / output interface. The processor of the computer device is used to provide computing and control capabilities. The memory of the computer device includes a non-volatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program and a database. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The database of the computer device is used to store data on a method for generating maintenance business documents. The input / output interface of the computer device is used to exchange information between the processor and an external device. The communication interface of the computer device is used to communicate with an external terminal through a network connection. When the computer program is executed by the processor, a method for generating a maintenance business document is implemented.

[0119] Those skilled in the art will understand that Fig.13 The structure shown in the figure is only a block diagram of a part of the structure related to the solution of the present application, and does not constitute a limitation on the computer device to which the solution of the present application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine certain components, or have a different arrangement of components.

[0120] In one embodiment, a computer device is further provided, including a memory and a processor, wherein a computer program is stored in the memory, and the processor implements the steps in the above method embodiments when executing the computer program.

[0121] In one embodiment, a computer-readable storage medium is provided, on which a computer program is stored. When the computer program is executed by a processor, the steps in the above-mentioned method embodiments are implemented.

[0122] In one embodiment, a computer program product is provided, including a computer program, which implements the steps in the above method embodiments when executed by a processor.

[0123] It should be noted that the user information (including but not limited to user device information, user personal information, etc.) and data (including but not limited to data used for analysis, stored data, displayed data, etc.) involved in this application are all information and data authorized by the user or fully authorized by all parties, and the collection, use and processing of relevant data must comply with relevant regulations.

[0124] A person of ordinary skill in the art can understand that all or part of the processes in the above-mentioned embodiment method can be completed by instructing the relevant hardware through a computer program, and the computer program can be stored in a non-volatile computer-readable storage medium. When the computer program is executed, it can include the processes of the embodiments of the above-mentioned methods. Among them, any reference to the memory, database or other medium used in the embodiments provided in the present application can include at least one of non-volatile memory and volatile memory. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, optical memory, high-density embedded non-volatile memory, resistive random access memory (ReRAM), magnetic random access memory (MRAM), ferroelectric random access memory (FRAM), phase change memory (PCM), graphene memory, etc. Volatile memory can include random access memory (RAM) or external cache memory, etc. As an illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM). The database involved in each embodiment provided in this application may include at least one of a relational database and a non-relational database. Non-relational databases may include distributed databases based on blockchains, etc., but are not limited to this. The processor involved in each embodiment provided in this application may be a general-purpose processor, a central processing unit, a graphics processor, a digital signal processor, a programmable logic device, a data processing logic device based on quantum computing, an artificial intelligence (AI) processor, etc., but are not limited to this.

[0125] The technical features of the above embodiments may be combined arbitrarily. To make the description concise, not all possible combinations of the technical features in the above embodiments are described. However, as long as there is no contradiction in the combination of these technical features, they should be considered to be within the scope of this application.

[0126] The above-described embodiments only express several implementation methods of the present application, and the descriptions thereof are relatively specific and detailed, but they cannot be understood as limiting the scope of the present application. It should be pointed out that, for a person of ordinary skill in the art, several variations and improvements can be made without departing from the concept of the present application, and these all belong to the protection scope of the present application. Therefore, the protection scope of the present application shall be subject to the attached claims.

Claims

1. A method for generating a maintenance service document, characterized in that: The method comprises: Each time a preset maintenance plan is called, a number of maintenance items included in the maintenance plan are obtained, and the execution date of the current maintenance plan for each maintenance item is determined according to the actual execution date of the last maintenance corresponding to each maintenance item and the maintenance strategy associated with each maintenance item; According to the execution date of the maintenance plan for each maintenance item, the date of generating the document for each maintenance item is obtained; If the current document generation date of any maintenance item expires, a current maintenance business document for the maintenance item is generated according to the maintenance standard package associated with the maintenance item and the current maintenance plan execution date.

2. The method according to claim 1, characterized in that The step of determining the current maintenance plan execution date of each maintenance item according to the actual execution date of the last maintenance corresponding to each maintenance item and the maintenance strategy associated with each maintenance item includes: For any maintenance item, according to the maintenance strategy associated with the maintenance item, obtain the execution date of the last maintenance plan corresponding to the maintenance item; When the actual execution date of the last maintenance corresponding to any maintenance item is different from the execution date of the last maintenance plan, determining the last offset corresponding to any maintenance item; The execution date of the current maintenance plan of any maintenance item is determined according to the size relationship between the last offset and the completion tolerance corresponding to any maintenance item.

3. The method according to claim 2, characterized in that Determining the last offset corresponding to any maintenance item includes: According to the actual execution date of the last maintenance and the execution date of the last maintenance plan, the last offset date is obtained; Obtaining the maintenance period interval corresponding to any maintenance item; According to the last offset date and the maintenance cycle interval, the last offset corresponding to any maintenance item is obtained.

4. The method according to claim 2, characterized in that: The determining the execution date of the current maintenance plan of any maintenance item according to the size relationship between the last offset and the completion tolerance corresponding to any maintenance item includes: Obtaining the maintenance period interval corresponding to any maintenance item; Obtaining a completion offset corresponding to any maintenance item; When the last offset is greater than the completion tolerance, determining the current maintenance plan execution date of any maintenance item according to the last actual maintenance execution date, the maintenance cycle interval and the completion offset; When the last offset is less than the completion tolerance, the current maintenance plan execution date of any maintenance item is determined according to the last maintenance plan execution date and the maintenance cycle interval.

5. The method according to claim 4, characterized in that The obtaining of the maintenance period interval corresponding to any maintenance item includes: Obtaining a plan identifier corresponding to any maintenance item; When the plan is identified as being based on the operation history, obtaining measurement information corresponding to any maintenance item; A maintenance period interval corresponding to any maintenance item is obtained according to the measurement information.

6. The method according to claim 1, characterized in that The method of obtaining the current document generation date of each maintenance item according to the current maintenance plan execution date of each maintenance item includes: According to the maintenance strategy associated with each maintenance item, the call period corresponding to each maintenance item is obtained; According to the call-up period corresponding to each maintenance item and the execution date of this maintenance plan, the current document generation date of each maintenance item is obtained.

7. A device for generating maintenance service documents, characterized in that: The device comprises: A planned execution date acquisition module is used to obtain a number of maintenance items included in the maintenance plan each time a preset maintenance plan is called, and determine the current maintenance plan execution date of each maintenance item according to the actual execution date of the last maintenance corresponding to each maintenance item and the maintenance strategy associated with each maintenance item; The document generation date acquisition module is used to obtain the current document generation date of each maintenance project according to the current maintenance plan execution date of each maintenance project; The maintenance business document generation module is used to generate the current maintenance business document of any maintenance project according to the maintenance standard package associated with the any maintenance project and the execution date of the current maintenance plan if the current document generation date of any maintenance project expires.

8. 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 the method according to any one of claims 1 to 6 are implemented.

9. 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 the method according to any one of claims 1 to 6 are implemented.

10. A computer program product, comprising a computer program, characterized in that When the computer program is executed by a processor, the steps of the method according to any one of claims 1 to 6 are implemented.

Images