1. A maintenance scheme generation method for a distributed system, the method comprising:

s1: acquiring a maintenance event signal; the service event signal includes: basic information, control information and decision information; the basic information includes: basic data, task data, monitoring data and detection data; the control information includes: maintenance costs, maintenance capabilities, safety requirements, and standard specifications; the decision information includes: fault diagnosis, resource allocation, a decision model, a project to be maintained and a timing maintenance plan;

s2: analyzing the attribute of the current event according to different health condition degrees of the maintenance object; the attributes of the event include: timing events, fault events, and degradation events;

s3: if the attribute of the current event is a timed event, recording the timed maintenance plan in the step S1;

s4: constructing a health degree threshold value table;

s5: determining whether a degradation/failure event can be retained based on the health threshold table;

s6: if the event can be reserved, the item to be maintained in the decision information is included;

s7: if the event is not retainable, recording a maintenance event;

s8: searching whether events to be maintained exist in all retainable events and non-retainable events;

s9: if so, recording a maintenance event;

s9: analyzing whether a subsequent schedule of a timed maintenance event exists;

s10: if yes, recording a maintenance event;

s11: analyzing the number of all maintenance events;

s12: a repair scenario is generated based on the number and attributes of the repair events.

2. The method for generating a maintenance plan for a distributed system according to claim 1, wherein analyzing the attributes of the current event according to different health status degrees of the maintenance object specifically includes:

if the event is a planned event, the event attribute is a timing event, and if the event is an emergency event, the event attribute is a fault event or a degradation event.

3. The method of generating a repair scenario for a distributed system of claim 1, wherein determining whether a degradation/failure event can remain based on the health threshold table specifically comprises:

a non-retainable event is a condition where a degradation/failure event results in product health being below a desired maintenance limit, and a retainable event is otherwise.

4. The method of generating a repair scenario for a distributed system according to claim 1, wherein the analyzing the number of all repair events specifically comprises:

if the number of the maintenance events is 1, determining the maintenance events to be single maintenance events;

and if the number of the maintenance events is more than 1, determining the maintenance events to be multiple maintenance events.

5. The method for generating a maintenance plan for a distributed system according to claim 4, wherein generating a maintenance plan based on the number and attributes of the maintenance events specifically comprises:

for a single maintenance event, directly searching the decision model obtained in the step S1, matching a proper maintenance model, and generating a maintenance scheme;

for multiple maintenance events, first determining whether there is a correlation between maintenance events;

if similar maintenance steps exist among fault events or similar functions exist among fault equipment, the correlation is considered to exist, group maintenance is carried out on the maintenance events with the correlation, a decision model is searched and matched, and a common maintenance scheme is generated;

and for the maintenance events without correlation, not performing group maintenance, sequentially searching the decision models and matching to generate respective maintenance schemes.

6. A maintenance plan generation system for a distributed system, the system comprising:

the maintenance event signal acquisition module is used for acquiring a maintenance event signal; the service event signal includes: basic information, control information and decision information; the basic information includes: basic data, task data, monitoring data and detection data; the control information includes: maintenance costs, maintenance capabilities, safety requirements, and standard specifications; the decision information includes: fault diagnosis, resource allocation, a decision model, a project to be maintained and a timing maintenance plan;

the event attribute analysis module is used for analyzing the attribute of the current event according to different health condition degrees of the maintenance object; the attributes of the event include: timing events, fault events, and degradation events;

if the attribute of the current event is a timing event, recording a timing maintenance plan in a maintenance event signal acquisition module;

the health degree threshold value table analysis module is used for constructing a health degree threshold value table;

a first determination module to determine whether a degradation/failure event can be retained based on the health threshold table;

if the event can be reserved, the item to be maintained in the decision information is included;

if the event is not retainable, recording a maintenance event;

the searching module is used for searching whether events to be maintained exist in all retainable events and non-retainable events;

if so, recording a maintenance event;

the first analysis module is used for analyzing whether a schedule of a timed maintenance event exists subsequently;

if yes, recording a maintenance event;

the second analysis module is used for analyzing the number of all maintenance events;

and the maintenance scheme generation module is used for generating a maintenance scheme based on the number and the attribute of the maintenance events.

7. The maintenance plan generating system of the distributed system according to claim 6, wherein the event attribute analyzing module specifically includes:

if the event is a planned event, the event attribute is a timing event, and if the event is an emergency event, the event attribute is a fault event or a degradation event.

8. The maintenance plan generating system of the distributed system according to claim 6, wherein the first determining module specifically includes:

a non-retainable event is a condition where a degradation/failure event results in product health being below a desired maintenance limit, and a retainable event is otherwise.

9. The maintenance plan generating system of the distributed system according to claim 6, wherein the second analysis module specifically includes:

if the number of the maintenance events is 1, determining the maintenance events to be single maintenance events;

and if the number of the maintenance events is more than 1, determining the maintenance events to be multiple maintenance events.

10. The maintenance scheme generation system of the distributed system according to claim 6, wherein the maintenance scheme generation module specifically includes:

for a single maintenance event, directly searching the decision model obtained in the maintenance event signal obtaining module, matching a proper maintenance model, and generating a maintenance scheme;

for multiple maintenance events, first determining whether there is a correlation between maintenance events;

if similar maintenance steps exist among fault events or similar functions exist among fault equipment, the correlation is considered to exist, group maintenance is carried out on the maintenance events with the correlation, a decision model is searched and matched, and a common maintenance scheme is generated;

and for the maintenance events without correlation, not performing group maintenance, sequentially searching the decision models and matching to generate respective maintenance schemes.

Background

The distributed system is a task system composed of a plurality of subsystems with independent functions, and can be divided into a task execution system and a support auxiliary system. The system for executing the tasks comprises a task system, an execution system, a control system, a communication system and a power supply system, and the support auxiliary system comprises a transportation system, a maintenance test system, a system calibration system and a training system. The distributed system has the structural characteristics of 'decentralized deployment-cooperative work', so that more technical supports are required, such as a high-precision networking technology, a uniform control mode, an advanced task planning technology and the like. The distributed system has complex elements, extremely high precision requirement and special structure, so the maintenance difficulty is higher and the requirement on maintenance management is higher.

On one hand, the distributed system is complex in composition, and the maintenance and management requirements of different task systems are different. In general, since the distributed system has a plurality of task systems and execution systems, if a certain task system or execution system fails or degrades, the system can still degrade the use of the completed task. However, for subsystems without redundancy in the distributed system, such as a command center, a control system, a communication system, a power supply system, and the like, maintenance resource reservation work needs to be done on key components or key equipment in the distributed system, and maintenance technical training of the key equipment needs to be performed on operators, so that the complete operation of the distributed system is guaranteed.

On the other hand, the distributed system has the characteristics of scattered deployment and large working space when executing tasks, so that the maintenance management of the distributed system is limited by the region space to a great extent. Therefore, the problem caused by the failure that the communication link is interrupted needs to be considered in the maintenance management. In different situations, the maintenance management requirements due to the communication link interruption are different. If the communication link interruption occurs in the state of checking training and marching of the distributed system, the current state can be reserved to wait for the next preventive maintenance time to carry out group maintenance on the premise of not influencing the current or next task execution of the system; if the current task is influenced, the equipment can be subjected to repairability maintenance activities through fault positioning, equipment decomposition, disassembly, replacement or repair on the premise of maintaining resources, maintenance technical capability and the like; and if the current task is influenced but no maintenance resources, maintenance technical capacity and the like exist, keeping the current state until returning to camp maintenance. However, in the combat state, the interruption of the communication link directly affects whether the distributed system can accurately complete the combat mission, and the communication needs to be repaired to ensure the completion of the mission, and the equipment can be repaired by fault location, equipment decomposition, disassembly, replacement or repair on the premise of maintenance resources, maintenance technical capability and the like, and the communication needs to be ensured by connecting a wired link and the like if the maintenance resources, the maintenance technical capability and the like do not exist.

Based on the structural characteristics of 'decentralized deployment-cooperative work', the distributed system has more severe maintenance and management requirements on degraded use and communication links, and needs targeted maintenance technical support. However, currently, there is a lack of research on how to generate maintenance solutions for distributed systems. Therefore, a set of scientific and reasonable maintenance scheme generation method and system have important significance for improving the maintenance management level of the distributed system and improving the reliability of the distributed system in the whole life cycle.

Disclosure of Invention

The invention aims to provide a maintenance scheme generation method and a maintenance scheme generation system for a distributed system, wherein possible maintenance events of the distributed system are analyzed, on the basis of considering maintenance decision influence factors of the distributed system, the attributes of the maintenance events, the retention condition of the maintenance events, whether the maintenance events are accumulated, whether a timed maintenance plan exists, the number of the maintenance events, the types (single event and multiple events) of the maintenance events and possible event compositions are sequentially determined, and different method approaches are obtained according to the event types, so that the maintenance scheme is generated.

In order to achieve the purpose, the invention provides the following scheme:

a maintenance plan generation method for a distributed system, the method comprising:

s1: acquiring a maintenance event signal; the service event signal includes: basic information, control information and decision information; the basic information includes: basic data, task data, monitoring data and detection data; the control information includes: maintenance costs, maintenance capabilities, safety requirements, and standard specifications; the decision information includes: fault diagnosis, resource allocation, a decision model, a project to be maintained and a timing maintenance plan;

s2: analyzing the attribute of the current event according to different health condition degrees of the maintenance object; the attributes of the event include: timing events, fault events, and degradation events;

s3: if the attribute of the current event is a timed event, recording the timed maintenance plan in the step S1;

s4: constructing a health degree threshold value table;

s5: determining whether a degradation/failure event can be retained based on the health threshold table;

s6: if the event can be reserved, the item to be maintained in the decision information is included;

s7: if the event is not retainable, recording a maintenance event;

s8: searching whether events to be maintained exist in all retainable events and non-retainable events;

s9: if so, recording a maintenance event;

s9: analyzing whether a subsequent schedule of a timed maintenance event exists;

s10: if yes, recording a maintenance event;

s11: analyzing the number of all maintenance events;

s12: a repair scenario is generated based on the number and attributes of the repair events.

Optionally, analyzing the attributes of the current event according to different health status degrees of the maintenance object specifically includes:

if the event is a planned event, the event attribute is a timing event, and if the event is an emergency event, the event attribute is a fault event or a degradation event.

Optionally, the determining whether the degradation/failure event can be retained based on the health threshold table specifically includes:

a non-retainable event is a condition where a degradation/failure event results in product health being below a desired maintenance limit, and a retainable event is otherwise.

Optionally, the analyzing the number of all the maintenance events specifically includes:

if the number of the maintenance events is 1, determining the maintenance events to be single maintenance events;

and if the number of the maintenance events is more than 1, determining the maintenance events to be multiple maintenance events.

Optionally, generating a maintenance scheme based on the number and the attributes of the maintenance events specifically includes:

for a single maintenance event, directly searching the decision model obtained in the step S1, matching a proper maintenance model, and generating a maintenance scheme;

for multiple maintenance events, first determining whether there is a correlation between maintenance events;

if similar maintenance steps exist among fault events or similar functions exist among fault equipment, the correlation is considered to exist, group maintenance is carried out on the maintenance events with the correlation, a decision model is searched and matched, and a common maintenance scheme is generated;

and for the maintenance events without correlation, not performing group maintenance, sequentially searching the decision models and matching to generate respective maintenance schemes.

The present invention additionally provides a maintenance plan generating system of a distributed system, the system comprising:

the maintenance event signal acquisition module is used for acquiring a maintenance event signal; the service event signal includes: basic information, control information and decision information; the basic information includes: basic data, task data, monitoring data and detection data; the control information includes: maintenance costs, maintenance capabilities, safety requirements, and standard specifications; the decision information includes: fault diagnosis, resource allocation, a decision model, a project to be maintained and a timing maintenance plan;

the event attribute analysis module is used for analyzing the attribute of the current event according to different health condition degrees of the maintenance object; the attributes of the event include: timing events, fault events, and degradation events;

if the attribute of the current event is a timing event, recording a timing maintenance plan in a maintenance event signal acquisition module;

the health degree threshold value table analysis module is used for constructing a health degree threshold value table;

a first determination module to determine whether a degradation/failure event can be retained based on the health threshold table;

if the event can be reserved, the item to be maintained in the decision information is included;

if the event is not retainable, recording a maintenance event;

the searching module is used for searching whether events to be maintained exist in all retainable events and non-retainable events;

if so, recording a maintenance event;

the first analysis module is used for analyzing whether a schedule of a timed maintenance event exists subsequently;

if yes, recording a maintenance event;

the second analysis module is used for analyzing the number of all maintenance events;

and the maintenance scheme generation module is used for generating a maintenance scheme based on the number and the attribute of the maintenance events.

Optionally, the event attribute analysis module specifically includes:

if the event is a planned event, the event attribute is a timing event, and if the event is an emergency event, the event attribute is a fault event or a degradation event.

Optionally, the first determining module specifically includes:

a non-retainable event is a condition where a degradation/failure event results in product health being below a desired maintenance limit, and a retainable event is otherwise.

Optionally, the second analysis module specifically includes:

if the number of the maintenance events is 1, determining the maintenance events to be single maintenance events;

and if the number of the maintenance events is more than 1, determining the maintenance events to be multiple maintenance events.

Optionally, the maintenance scheme generating module specifically includes:

for a single maintenance event, directly searching the decision model obtained in the maintenance event signal obtaining module, matching a proper maintenance model, and generating a maintenance scheme;

for multiple maintenance events, first determining whether there is a correlation between maintenance events;

if similar maintenance steps exist among fault events or similar functions exist among fault equipment, the correlation is considered to exist, group maintenance is carried out on the maintenance events with the correlation, a decision model is searched and matched, and a common maintenance scheme is generated;

and for the maintenance events without correlation, not performing group maintenance, sequentially searching the decision models and matching to generate respective maintenance schemes.

According to the specific embodiment provided by the invention, the invention discloses the following technical effects:

the method and the system analyze possible maintenance events of the distributed system on the basis of fully considering the structural characteristics and the maintenance management requirements of the distributed system, and are beneficial to pertinently improving the maintenance management level of the distributed system;

the process of generating the maintenance scheme is streamlined, which is beneficial to comprehensively considering all factors in the maintenance decision, so that the maintenance decision result is more scientific and reasonable;

when the maintenance signal is acquired, whether the maintenance event is reserved or not and whether the maintenance event is accumulated or not are judged, the health state information is fully utilized, and the improvement of the predicted maintenance level of the distributed system is facilitated.

Drawings

In order to more clearly illustrate the embodiments of the present invention or the technical solutions in the prior art, the drawings needed to be used in the embodiments will be briefly described below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art to obtain other drawings without inventive exercise.

FIG. 1 is a flowchart of a method for generating a maintenance plan of a distributed system according to an embodiment of the present invention;

fig. 2 is a schematic diagram of a logical relationship between event attributes and operating states according to an embodiment of the present invention.

Detailed Description

The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are only a part of the embodiments of the present invention, and not all of the embodiments. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.

The invention aims to provide a maintenance scheme generation method and a maintenance scheme generation system for a distributed system, wherein possible maintenance events of the distributed system are analyzed, on the basis of considering maintenance decision influence factors of the distributed system, the attributes of the maintenance events, the retention condition of the maintenance events, whether the maintenance events are accumulated, whether a regular maintenance plan is provided, the number of the maintenance events, the types (single event and multiple events) of the maintenance events and possible event compositions are sequentially determined, different method paths are obtained according to the types of the events, and therefore the maintenance scheme is generated

In order to make the aforementioned objects, features and advantages of the present invention comprehensible, embodiments accompanied with figures are described in further detail below.

Fig. 1 is a flowchart of a method for generating a maintenance plan of a distributed system according to an embodiment of the present invention, and as shown in fig. 1, the method includes:

s1: acquiring a maintenance event signal; the service event signal includes: basic information, control information and decision information; the basic information includes: basic data, task data, monitoring data and detection data; the control information includes: maintenance costs, maintenance capabilities, safety requirements, and standard specifications; the decision information includes: fault diagnosis, resource allocation, a decision model, a project to be maintained and a timing maintenance plan;

wherein the basic data includes: system/subsystem data (structural function, etc.), operating parameters, personnel technical data (organization structure, use data, etc.) and standard data;

the task data includes: task requirements, task start/end times;

the monitoring data includes: system data collected in real time;

the detecting data includes: and diagnosing effective data acquired by some means according to the management of the maintenance task, namely daily inspection, monthly inspection, annual inspection and the like of the distributed system.

Wherein, the control information, namely the limit and restriction that the maintenance activity receives, mainly include:

maintenance cost: indirect maintenance costs, direct maintenance costs;

maintenance capacity: the state of the existing maintenance technology, maintenance equipment and maintenance personnel;

safety requirements are as follows: safety guarantee of maintenance personnel and safety protection of system equipment;

standard specification: standards, protocols, etc.

Wherein, the decision information mainly includes:

fault diagnosis: judging results of system fault diagnosis;

resource allocation: the resources can be recombined and redistributed;

a decision model: a maintenance decision model taking time as a target, a maintenance decision model taking cost as a target, a maintenance decision model taking availability as a target and a multi-target maintenance decision model;

and (4) to-be-maintained items: maintenance items previously reserved for the system;

and (3) timing maintenance planning: scheduled maintenance schedule previously determined by the system.

S2: analyzing the attribute of the current event according to different health condition degrees of the maintenance object; the attributes of the event include: timing events, fault events, and degradation events;

the attributes of the current event are analyzed according to different health condition degrees of the maintenance object, and the attributes are mainly divided into three types.

If the system has an event with a scheduled maintenance requirement which is specified in advance due to technical requirements or regulatory rules, the event is defined as a timing event and is counted into a 'timing maintenance plan' in the maintenance event signal obtained in the step one;

for the condition that the distributed system/subsystem has a fault, if an event with a post-maintenance requirement exists, defining the event as a fault event;

for the case that the system has performance deterioration, namely the system performance parameter is lower than the specified health value, the event of the predictive maintenance requirement is defined as the degradation event.

S3: if the attribute of the current event is a timed event, the timed maintenance schedule in step S1 is included.

S4: and constructing a health degree threshold value table.

S5: determining whether a degradation/failure event can be retained based on the health threshold table.

S6: and if the event is a retainable event, recording the item to be maintained in the decision information.

S7: if the event is not retainable, the maintenance event is counted.

S8: and searching whether an event to be maintained exists in all the retainable events and the non-retainable events.

S9: if so, a maintenance event is logged.

For a fault event that can be retained, the maintenance process can be made more difficult as the retention time increases after the fault, thereby incurring additional maintenance costs, maintenance resources, and possibly increased maintenance time. Therefore, the corresponding values of the product status and the health degree need to be obtained through historical data statistics in advance, and a health degree threshold judgment table is constructed, as shown in table 1.

TABLE 1 health threshold judgment Table

The construction method comprises the following steps:

the health degree of the product reflects the health state of the product, and the value range is [0,1 ]. When the product state meets all the specified capability requirements (such as functional integrity, environmental adaptability and time duration requirements), the health degree is 1, which indicates that the product is in a complete health state; when the product state does not meet all the specified capacity requirements, the health degree is 0, and the product is in a complete fault state; while when the health is between (0,1), the product may be classified as dangerous, sub-healthy, etc. according to different ranges of health thresholds (table 1 exemplifies a total of 4 levels).

Therefore, the product health degree is actually a deviation between the product state and the full health state at a certain moment, and is obtained from parameter data of parameters (such as temperature, pressure, flow rate and the like of equipment) capable of reflecting the product state at the moment and parameter data in the full health state.

Assuming that n-dimensional parameters of a product can reflect the state of the product, at time t, the data of the parameters areMeasure of the extent of deviation of the product state from the full health state at time tCan be expressed as

Wherein the content of the first and second substances,n-dimensional parameter data representing time t;

parametric data representing n dimensions in a fully healthy state;

a measure function of the degree of health deviation;

therefore, according to the parameter data of the product historical state, the health degree of the product in a certain historical state can be obtained, and the corresponding relation between the product state and the health degree is obtained.

Since some products allow degraded use or do not affect the system's performance to perform the specified functions even if performance degradation occurs, the health of the product, and therefore the expected limits of repair for the product, at the time the product must be repaired is determined based on historical data.

Then, it is determined whether the degradation/failure event can be retained according to the health threshold determination table. For the case where the degradation/failure event results in product health being below the desired maintenance limit, immediate maintenance, defined as a non-retainable event, is necessary; otherwise, the maintenance may not be performed immediately, and the event is defined as a retainable event.

For the current events which cannot be reserved, the maintenance events in the step five need to be counted and analyzed; and for the current retainable event, counting into the 'event item to be maintained' in the maintenance event signal obtained in the step one, but not analyzing currently.

S9: analyzing whether a scheduled maintenance event is planned subsequently.

S10: if so, a maintenance event is logged.

Fault and degradation events are dynamic events and are unpredictable, but timed events are static events and are pre-planned. Therefore, the combination of the two results in either disturbing the scheduled maintenance or requiring a certain time for maintaining the failure state of the component. However, if the failure/degradation is combined with an imminent timing event to form a system maintenance solution, maintenance costs can be effectively reduced.

Therefore, it is determined whether there is a subsequent scheduled maintenance event based on the "scheduled timed event" in the maintenance event signal acquired at step S1 and the timed event possibly determined at step S2. And for the subsequent case that a scheduled maintenance is planned, counting the scheduled maintenance into the maintenance event of the step five, and not counting the scheduled maintenance into the maintenance event of the step five. Whether a scheduled maintenance event is planned or not is followed, the next analysis is performed.

S11: the number of all maintenance events is analyzed.

Analyzing the number of maintenance events, and determining the maintenance events as single maintenance events under the condition that the number of the maintenance events is 1; for the case where the number of maintenance events is greater than "1", then it is determined to be a multiple maintenance event.

Because different events have different influences on the working state of the distributed system, when the subsystems corresponding to the timing event, the degradation event and the fault event do not influence the use, the shutdown cannot be caused; delayed shutdown may result when timing events, degradation events, and non-critical faults affect use; when critical faults occur, the use is affected, and shutdown is caused. The logical relationship between the event attribute and the working state is shown in fig. 2.

Therefore, for multiple maintenance events, it is further determined which combination of maintenance events to combine.

S12: a repair scenario is generated based on the number and attributes of the repair events.

Decision models are divided into four classes according to decision objectives. Decision goals include reliability goals, maintainability goals, availability goals, economic goals, technical goals, and the like. Because different maintenance decision objectives have large influence differences on the optimization result, the distributed system focuses on the maintainability objective, the economic objective and the availability objective.

Among the most immediate concerns for serviceability goals are maintenance-induced down-time, including system logistics supply time, system repair time, and test time, as well as initial delay in actual maintenance. Maintenance decisions need to meet the goals of quick repairs because distributed systems have stringent requirements for repair down time.

The economic objective is primarily concerned with direct maintenance costs, lost to failure costs and lost to shutdown costs. Since the actual maintenance costs are related to the real-time status of the distributed system, it is not possible to determine whether the economic objective is achieved simply by the amount of the costs. Therefore, maintenance cost rate is defined to calculate the ratio of decision-making expectation cost and expectation time, thereby measuring the economy of maintenance.

The availability objective is measured in availability, reflecting the ratio of the time that the distributed system is operating properly over a period of time to the total time.

And selecting different decision models according to the number of the events judged in the last step to generate a maintenance scheme.

For a single maintenance event, the maintenance event signal, namely the decision model, obtained in the step S1 is directly searched, and a suitable maintenance model is matched to generate a maintenance scheme.

For multiple maintenance events, it is first determined whether there is a correlation between the maintenance events. The method specifically comprises the following steps: similar maintenance steps exist between fault events or similar functions exist between faulty devices. For maintenance events with correlation, group maintenance is carried out, a decision model is searched and matched, and a common maintenance scheme is generated;

and for the maintenance events without correlation, group maintenance is not carried out, and the decision models are sequentially searched and matched to generate respective maintenance schemes.

The present invention further provides a maintenance plan generation system for a distributed system, the system including:

the maintenance event signal acquisition module is used for acquiring a maintenance event signal; the service event signal includes: basic information, control information and decision information; the basic information includes: basic data, task data, monitoring data and detection data; the control information includes: maintenance costs, maintenance capabilities, safety requirements, and standard specifications; the decision information includes: fault diagnosis, resource allocation, a decision model, a project to be maintained and a timing maintenance plan;

the event attribute analysis module is used for analyzing the attribute of the current event according to different health condition degrees of the maintenance object; the attributes of the event include: timing events, fault events, and degradation events;

if the attribute of the current event is a timing event, recording a timing maintenance plan in a maintenance event signal acquisition module;

the health degree threshold value table analysis module is used for constructing a health degree threshold value table;

a first determination module to determine whether a degradation/failure event can be retained based on the health threshold table;

if the event can be reserved, the item to be maintained in the decision information is included;

if the event is not retainable, recording a maintenance event;

the searching module is used for searching whether events to be maintained exist in all retainable events and non-retainable events;

if so, recording a maintenance event;

the first analysis module is used for analyzing whether a schedule of a timed maintenance event exists subsequently;

if yes, recording a maintenance event;

the second analysis module is used for analyzing the number of all maintenance events;

and the maintenance scheme generation module is used for generating a maintenance scheme based on the number and the attribute of the maintenance events.

The embodiments in the present description are described in a progressive manner, each embodiment focuses on differences from other embodiments, and the same and similar parts among the embodiments are referred to each other. For the system disclosed by the embodiment, the description is relatively simple because the system corresponds to the method disclosed by the embodiment, and the relevant points can be referred to the method part for description.

The principles and embodiments of the present invention have been described herein using specific examples, which are provided only to help understand the method and the core concept of the present invention; meanwhile, for a person skilled in the art, according to the idea of the present invention, the specific embodiments and the application range may be changed. In view of the above, the present disclosure should not be construed as limiting the invention.