A task reliability modeling method and system

Abstract

The application provides a task reliability modeling method and system, and belongs to the technical field of reliability modeling. The method comprises the following steps: establishing a product structure tree based on different levels; constructing a virtual unit for a node corresponding to different reliability models with different working conditions, and adding the virtual unit to the product structure tree; establishing a reliability model set of each node under various working conditions in a hierarchical manner; selecting a reliability model of each level under a general working condition scene from the reliability model set according to a top-down principle of the product structure tree, and assembling the reliability model into a general working condition model under each working condition; dividing a task into different stages, establishing a reliability model of a task profile, and generating a reliability model file of the task profile. The application can not only realize effective reuse of the model, but also greatly improve the efficiency and accuracy of modeling, and provides a more efficient and convenient solution for reliability evaluation of a complex system.

Description

TECHNICAL FIELD

[0001] The application belongs to the technical field of reliability modeling, and more particularly relates to a task reliability modeling method and system. BACKGROUND

[0002] System reliability analysis, as a core link of system reliability engineering, plays a decisive role in identifying potential problems of a system, in-depth analyzing the root cause of the problems, and formulating targeted solutions. Reliability modeling, as the cornerstone of analysis work, its accuracy and effectiveness are directly related to the accuracy and reliability of the subsequent analysis results.

[0003] When facing large complex systems with multi-level complex structure and covering multiple working conditions, how to efficiently build a task reliability model has always been a major technical problem in the industry. At present, although many experiences and methods have been accumulated in the field of reliability modeling, most of them are still limited to single-condition, single-structure system modeling, and are difficult to be directly applied to multi-level, multi-condition complex systems.

[0004] Therefore, how to directly and effectively model the task reliability of such large complex systems has become a technical challenge that needs to be solved urgently in the current product design process. Not only can it help improve the reliability level of product design, but also can help enterprises gain an advantage in fierce market competition, and has important theoretical value and practical significance. SUMMARY

[0005] In view of the defects of the prior art, the purpose of the present application is to provide a task reliability modeling method and system, which aims to solve the problem that the existing task reliability modeling is mostly limited to single-condition, single-structure systems, resulting in that the task reliability model cannot be directly applied to multi-level, multi-condition complex systems, and to provide a direct and effective task reliability modeling method for large complex tasks.

[0006] To achieve the above purpose, in a first aspect, the present application provides a task reliability modeling method, comprising the following steps:

[0007] Step 1: dividing a product into different levels from a system to a device, and establishing a product structure tree based on different levels;

[0008] Step 2: constructing a virtual unit for nodes corresponding to different reliability models with different working conditions, and adding the virtual unit as a node to the product structure tree;

[0009] Step 3: establishing a reliability model under different working conditions for each node in each level with the virtual unit added, to form a reliability model set; wherein if there are multiple working conditions in a node, multiple reliability models are established, and each reliability model of the same node is independent of each other.

[0010] Step 4: According to the principle of top-down of the product structure tree, the reliability models of each level under the overall working condition scene are selected from the reliability model set to assemble into the overall working condition model under each working condition;

[0011] Step 5: The task is divided into different stages, the running time length ratio of each stage and the sequence between stages are defined, the overall working condition model used in each stage is selected from the overall working condition model under each working condition, and the reliability model of the task profile is established;

[0012] Step 6: According to the total task time length and the time length ratio of each task stage in the reliability model of the task profile, the running sequence and running time length of each overall working condition model in the task profile are obtained.

[0013] Further preferably, the nodes include overall, system, subsystem and virtual unit; the overall, system and / or subsystem contain equipment.

[0014] Further preferably, the specific steps of assembling the overall working condition model under each working condition in step 4 are:

[0015] First, the reliability model of the overall is selected from the reliability model set, then the reliability model of each system under the overall is selected, and then the reliability model of each subsystem under each system is selected; if the system or subsystem contains a virtual unit, the model of the virtual unit is selected.

[0016] Further preferably, step 6 specifically includes the following steps:

[0017] According to the total task time length and the time length ratio of each task stage in the reliability model of the task profile, the running time length of each stage is calculated;

[0018] According to the running time length ratio of the overall working condition model used in each stage and the running time length of each stage, the running time length of each overall working condition model is calculated, and the running sequence and running time length of each overall working condition model in the task profile are obtained.

[0019] Further preferably, step 6 further includes: using the running sequence and running time length of each overall working condition model in the task profile and the overall working condition model under each working condition in step 4 to constitute complete information describing the reliability model of the task profile, and writing the complete information into the reliability model file in XML format.

[0020] In a second aspect, the present application provides a task reliability modeling system, comprising:

[0021] A product structure tree construction module is configured to divide a product into different levels from system to equipment, and establish a product structure tree based on different levels;

[0022] a virtual unit construction module, configured to construct a virtual unit for a node corresponding to a different reliability model according to different working conditions, and add the virtual unit as the node into a product structure tree;

[0023] a model set acquisition module, configured to establish a reliability model under different working conditions for each node in each level after the virtual unit is added, and acquire a reliability model set; if there are multiple working conditions in a node, multiple reliability models are established, and each reliability model of the same node is independent of each other;

[0024] a general working condition model assembly module, configured to select a reliability model of each level under a general working condition scenario from the reliability model set according to a top-down principle of the product structure tree, and assemble the reliability model into a general working condition model under each working condition;

[0025] a task profile model establishment module, configured to divide a task into different stages, define a running time length ratio of each stage and an order between the stages, select a general working condition model used in each stage from the general working condition model under each working condition, and establish a reliability model of a task profile;

[0026] a running parameter acquisition module, configured to acquire a running order and a running time length of each general working condition model in the task profile according to a total task time length and a time length ratio of each task stage in the reliability model of the task profile.

[0027] Further preferably, the node in the virtual unit construction module comprises a general system, a system, a subsystem and a virtual unit; and the general system, the system and / or the subsystem comprise a device.

[0028] Further preferably, a specific method of assembling the general working condition model under each working condition by the general working condition model assembly module is as follows: firstly selecting a reliability model of the general system from the reliability model set, then selecting reliability models of each system under the general system, and then selecting reliability models of each subsystem under each system; if the system or the subsystem comprises a virtual unit, a model of the virtual unit is selected.

[0029] Further preferably, the running parameter acquisition module comprises:

[0030] a stage running time length calculation unit, configured to calculate a running time length of each stage according to a total task time length and a time length ratio of each task stage in the reliability model of the task profile;

[0031] a task profile running parameter acquisition unit, configured to calculate a running time length of each general working condition model according to a running time length ratio of the general working condition model used in each stage and the running time length of each stage, and acquire a running order and a running time length of each general working condition model in the task profile.

[0032] Further preferably, the task reliability modeling system further comprises a model file generating module, configured to write the complete information of the reliability model describing the task profile into a reliability model file in XML format.

[0033] In a third aspect, the present application provides an electronic device, comprising: at least one memory configured to store a program; and at least one processor configured to execute the program stored in the memory, and when the program stored in the memory is executed, the processor is configured to execute the method described in the first aspect or the implementation manner of the first aspect.

[0034] In a fourth aspect, the present application provides a computer readable storage medium, which stores a computer program, and when the computer program is run on a processor, the processor is caused to execute the method described in the first aspect or the implementation manner of the first aspect.

[0035] In a fifth aspect, the present application provides a computer program product, and when the computer program product is run on a processor, the processor is caused to execute the method described in the first aspect or the implementation manner of the first aspect.

[0036] It can be understood that the beneficial effects of the above-mentioned second aspect to fifth aspect can be referred to the related description in the first aspect, and will not be repeated here.

[0037] In general, compared with the prior art, the above technical solutions conceived by the present application have the following beneficial effects:

[0038] The present application provides a task reliability modeling method and system, which breaks through the limitations of traditional reliability modeling technology, successfully realizes the precise modeling of a multi-level complex system including a general system, a system, a subsystem, a device, etc., and assembles reliability models of different levels and different conditions to construct a general reliability model, completely abandoning the practice of stacking all models in a single reliability block diagram in the prior art. Through this method, the present application not only realizes the effective reuse of models and avoids repetitive labor, but also greatly improves the efficiency and accuracy of modeling, and provides a more efficient and convenient solution for reliability evaluation of complex systems.

[0039] The prior art is often limited to single-stage, single-condition simple scenarios in task profile modeling. However, the real-world complex system task profile usually has complex characteristics of multiple stages and variable conditions, which makes the prior art appear inadequate when facing such task profiles, and it is difficult to provide effective modeling support. The task reliability modeling method provided by the present application can directly model complex task profiles containing multiple stages and multiple conditions without complex conversion or simplification processing. This significant advantage makes the present application have a wider application prospect in production and scientific research practice, and can more accurately reflect the actual operation of complex systems, providing more accurate and reliable decision support for engineering practice. BRIEF DESCRIPTION OF DRAWINGS

[0040] Figure 1 is a task reliability modeling method flowchart provided by an embodiment of the present application;

[0041] FIG. 2(a) is a product structure tree diagram provided by an embodiment of the present application;

[0042] FIG. 2(b) is a product structure diagram provided by an embodiment of the present application, which adds a virtual unit;

[0043] Figure 3 is a schematic diagram of a general reliability model M1 provided by an embodiment of the present application;

[0044] FIG. 4(a) is a schematic diagram of a second reliability model M2 of the first system provided by an embodiment of the present application;

[0045] FIG. 4(b) is a schematic diagram of a third reliability model M3 of the first system provided by an embodiment of the present application;

[0046] FIG. 5(a) is a schematic diagram of a fourth reliability model M4 of the first virtual unit provided by an embodiment of the present application;

[0047] FIG. 5(b) is a schematic diagram of a fifth reliability model M5 of the first virtual unit provided by an embodiment of the present application;

[0048] Figure 6 is a schematic diagram of a sixth reliability model M6 of the second system provided by an embodiment of the present application;

[0049] FIG. 7(a) is a schematic diagram of a seventh reliability model M7 of the second virtual unit provided by an embodiment of the present application;

[0050] FIG. 7(b) is a schematic diagram of an eighth reliability model M8 of the second virtual unit provided by an embodiment of the present application;

[0051] FIG. 8(a) is a schematic diagram of a ninth reliability model M9 of the first subsystem provided by an embodiment of the present application;

[0052] Fig. 8(b) is a schematic diagram of a tenth reliability model M10 of the first subsystem according to an embodiment of the present application;

[0053] Figure 9 Fig. 8(b) is a schematic diagram of a tenth reliability model M10 of the first subsystem according to an embodiment of the present application;

[0054] Figure 10 Fig. 8(b) is a schematic diagram of a tenth reliability model M10 of the first subsystem according to an embodiment of the present application;

[0055] Figure 11 Fig. 8(b) is a schematic diagram of a tenth reliability model M10 of the first subsystem according to an embodiment of the present application;

[0056] Figure 12 Fig. 8(b) is a schematic diagram of a tenth reliability model M10 of the first subsystem according to an embodiment of the present application;

[0057] Figure 13 Fig. 8(b) is a schematic diagram of a tenth reliability model M10 of the first subsystem according to an embodiment of the present application;

[0058] Figure 14 Fig. 8(b) is a schematic diagram of a tenth reliability model M10 of the first subsystem according to an embodiment of the present application;

[0059] Figure 15 Fig. 8(b) is a schematic diagram of a tenth reliability model M10 of the first subsystem according to an embodiment of the present application;

[0060] Figure 16 Fig. 8(b) is a schematic diagram of a tenth reliability model M10 of the first subsystem according to an embodiment of the present application. DETAILED DESCRIPTION

[0061] In order to make the objects, technical solutions and advantages of the present application clearer, the present application will be further described in detail below with reference to the drawings and embodiments. It should be understood that the specific embodiments described herein are only used to explain the present application and should not be used to limit the present application.

[0062] The terms "first" and "second" and the like in the description and claims of the present application are used to distinguish different objects, and are not used to describe a specific order of the objects.

[0063] In the embodiments of the present application, the words "exemplary" or "for example" are used to mean serving as an example, instance, or illustration. Any embodiment or design presented as "exemplary" or "for example" in the embodiments of the present application is not necessarily to be construed as preferred or advantageous over other embodiments or design solutions. Rather, use of the words "exemplary" or "for example" is intended to present concepts in a concrete manner.

[0064] In the description of the embodiments of the present application, the meaning of "a plurality of" is two or more, unless otherwise specified.

[0065] As shown in the following table, the present application provides a task reliability modeling method, comprising the following steps: Figure 1

[0066] Step 1: Establishing a product structure tree: according to the hierarchy of the overall, system, subsystem and device, a product structure tree is established;

[0067] Step 2: Defining virtual units and adding them to the product structure tree;

[0068] The virtual unit refers to a group of devices or subsystems or systems that constitute a product. These devices or subsystems or systems change the connection relationship (i.e., series-parallel connection between devices or subsystems or systems) in the process of product task execution as the working condition changes. By analyzing the reliability model of the product under different working conditions, virtual units are extracted and added to the product structure tree. The extraction of virtual units is a kind of modular modeling idea, and the purpose is to increase the reusability of the reliability model and improve the modeling efficiency. According to the different complexity of the system and the different execution tasks, the extracted virtual units may be one or more, or there may be none;

[0069] Step 3: Hierarchical establishment of reliability models of each node (overall, system, subsystem and virtual unit) under various working conditions: according to the hierarchy of the overall, system, subsystem and virtual unit, the reliability models of each node under various different working conditions are established respectively. For a node, one model is established for one working condition. If there are multiple working conditions, multiple models are established. The models of the same node are independent of each other and have no dependency relationship. The models of all nodes under all working conditions form a set, which is used in the subsequent steps;

[0070] Step 4: Establishing the reliability model of the overall working condition (assembled from the reliability model set of each node under each working condition);

[0071] Specifically, according to the top-down principle, the models of each level (overall, system, subsystem and virtual unit) corresponding to the overall working condition scenario are selected from the reliability model set established in step 3 to assemble a complete reliability model of the overall working condition. When selecting the model, if there is only one model at this level, the model is automatically selected. More specifically, the model of the overall is selected first, then the models of each system under the overall are selected, and then the models of each subsystem under the system are selected. If the system or subsystem contains a virtual unit, the model of the virtual unit needs to be selected. Through this hierarchical model assembly method, the reliability model of the overall under various complex working conditions can be conveniently established;

[0072] ​Step 5: Establishing a reliability model of the task profile;

[0073] Specifically, for a complex task, first, the task is divided into different stages, and the running time length proportion of each stage and the sequence between stages are defined; then, for each stage, the overall working condition model used by the stage is selected from the overall working condition model set established in step 4, and if multiple overall working condition models are used, the running time length proportion and running sequence of each overall working condition model need to be defined;

[0074] Step 6: Generating a reliability model file of the task profile;

[0075] Specifically, according to the simulation total task time length and the time length proportion of each task stage in the reliability model of the task profile established in step 5, the running time length of each stage is calculated, and then according to the running time length proportion of each overall working condition model used by each stage, the running time length of each overall working condition model is calculated, and further the running sequence and running time length of each overall working condition model in the entire task profile can be obtained; the running sequence and running time length of each overall working condition model in the entire task profile and the reliability model of each overall working condition assembled in step 4 constitute the complete information describing a reliability model of a task profile, and these information is written into a reliability model file in the format of XML (eXtensible Markup Language, Extensible Markup Language); the XML file is a standard format file, which is convenient for data exchange with reliability simulation evaluation calculation software.

[0076] The task reliability modeling method provided by the present application will be described in detail in combination with specific embodiments; it should be pointed out that, in order to ensure the universal applicability of the present application, the complex system in the present embodiment is not derived from an actual system in real life, but is a fictitious system and device, which is designed to better explain the core principles and practical application value of the present application through this fictitious scenario.

[0077] As shown in Figure 1 , the present application provides a task reliability modeling method, which comprises the following steps:

[0078] Step 1: According to the principle and composition of the system, a product structure tree is established as shown in Fig. 2(a): the overall system is composed of a first system, a second system and a third system, the first system is composed of a first device, a second device, a third device, a fourth device and a fifth device; the second system is composed of a first sub-system, a second sub-system, a sixth device and a seventh device; the third system is composed of an eighth device and a ninth device; the first sub-system is composed of a tenth device, an eleventh device and a twelfth device; the second sub-system is composed of a thirteenth device and a fourteenth device.

[0079] Step 2: Analyze the reliability models of the components at each level (overall, system, subsystem) under various working conditions. Extract the parts that form different reliability models depending on the working conditions from the components at each level and define them as virtual units. Specifically, the fourth and fifth devices that constitute the first system are sometimes in series and sometimes in parallel depending on the working conditions. Therefore, the fourth and fifth devices are defined as the first virtual units under the first system. The first and second subsystems that constitute the second system are sometimes in series and sometimes in parallel depending on the working conditions. Therefore, the first and second subsystems that constitute the second system are defined as the second virtual units under the second system. Add the first virtual unit and the second required unit to the product structure tree, as shown in Figure 2(b).

[0080] Step 3: Establish the reliability model of each node (overall, system, subsystem and virtual unit) under various working conditions in a hierarchical manner; the overall reliability model is only Figure 3 The first system has two models as shown in FIG4 (a) and FIG4 (b), which are the second reliability model M2 of the first system and the third reliability model M3 of the first system respectively; the first virtual unit has two models as shown in FIG5 (a) and FIG5 (b), which are the fourth reliability model M4 of the first virtual unit and the fifth reliability model M5 of the first virtual unit respectively; the second system has only two models as shown in FIG5 (a) and FIG5 (b), which are the fourth reliability model M4 of the first virtual unit and the fifth reliability model M5 of the first virtual unit respectively. Figure 6 The second virtual unit 2 has two models as shown in FIG7 (a) and FIG7 (b), which are named as the seventh reliability model M7 of the second virtual unit and the eighth reliability model M8 of the second virtual unit respectively; the first subsystem has two models as shown in FIG8 (a) and FIG8 (b), which are named as the ninth reliability model M9 of the first subsystem and the tenth reliability model M10 of the first subsystem respectively; the second subsystem has only .... Figure 9 The model shown is named the eleventh reliability model M11 of the second subsystem; the third system has only Figure 10 One model shown is named the twelfth reliability model M12 of the third system;

[0081] Step 4: Establish a reliability model for the overall operating condition (assembled from the reliability model set of each node and each operating condition); specifically, according to the top-down principle, select the models of each level node (overall, system, subsystem and virtual unit) corresponding to the overall operating condition scenario to be established from the reliability model set generated in Step 3 and assemble them, thereby generating a complete overall operating condition model for the operating condition scenario; in this embodiment, using the reliability model set established in Step 3, it is theoretically possible to assemble 16 overall operating condition models as shown in Table 1, numbered ZGM1 to ZGM16;

[0082] Table 1

[0083]

[0084] In actual modeling, it is not necessary to assemble all models, but to select the models according to actual general working conditions; in the embodiment, general working condition models ZGM1, ZGM8 and ZGM13 are needed; the assembling methods of the three models are described in detail as follows.

[0085] The method for assembling the general working condition model ZGM1 is shown in Figure 11 According to the top-down principle, first, the reliability model of the first level node (general) in the product structure tree is selected; since the general has only one model M1, the reliability model M1 of the general is directly used for assembly without selection; then, the reliability model of the second level node (system) in the product structure tree is selected; since the model of the first level node uses the first system, the second system and the third system, the reliability models of the three systems are needed to be selected; the second reliability model M2 is selected for the first system; the sixth reliability model M6 and the twelfth reliability model M12 are directly used for assembly without selection for the second system and the third system; finally, the reliability model of the third level node (subsystem and virtual unit) in the product structure tree is selected; since the model of the selected second level node uses the first virtual unit, the second virtual unit, the first subsystem and the second subsystem, the reliability models of the above nodes are needed to be selected; the fourth reliability model M4 is selected for the first virtual unit; the seventh reliability model M7 is selected for the second virtual unit; the ninth reliability model M9 is selected for the first subsystem; the eleventh reliability model M11 is directly used for assembly without selection for the second subsystem; thus, the selection of all models for assembly is completed, i.e. Figure 11 The models marked in gray (the first reliability model M1, the second reliability model M2, the fourth reliability model M4, the sixth reliability model M6, the seventh reliability model M7, the ninth reliability model M9, the eleventh reliability model M11 and the twelfth reliability model M12) in

[0086] According to the same method, the models marked in gray (the first reliability model M1, the second reliability model M2, the fifth reliability model M5, the sixth reliability model M6, the eighth reliability model M8, the tenth reliability model M10, the eleventh reliability model M11 and the twelfth reliability model M12) in Figure 12 are selected; the above models are assembled to constitute the general working condition model numbered AGM8;

[0087] According to the same method, the models marked in gray (the first reliability model M1, the second reliability model M2, the fifth reliability model M5, the sixth reliability model M6, the eighth reliability model M8, the tenth reliability model M10, the eleventh reliability model M11 and the twelfth reliability model M12) inFigure 13 The models marked in gray (the first reliability model M1, the third reliability model M3, the fifth reliability model M5, the sixth reliability model M6, the seventh reliability model M7, the ninth reliability model M9, the eleventh reliability model M11, and the twelfth reliability model M12) are assembled to form the overall working condition model numbered ZGM13;

[0088] Step 5: Establish a reliability model of the task profile;

[0089] After analysis, the task profile can be divided into two task stages, namely, a first stage and a second stage, and the running time ratio of the first stage and the second stage is 1:3; the first stage contains two overall working condition models in step 4, and the running order is ZGM1 and ZGM8 in turn, and the running time ratio of ZGM1 and ZGM8 is 1:1; the second stage only contains one overall working condition model ZGM13 in step 4;

[0090] Step 6: Generate a reliability model file of the task profile;

[0091] Based on the data set in step 5, the task duration is preset to be 1000 hours; according to this duration, the detailed model running order and time allocation are calculated: the task profile first executes the ZGM1 model running for 125 hours, then executes the ZGM8 model running for 125 hours, and finally executes the ZGM13 model running for 750 hours;

[0092] To ensure the feasibility of simulation evaluation, the ZGM1, ZGM8 and ZGM13 models are hierarchically and recursively disassembled until the detailed degree of the equipment level is reached, so as to generate a refined model of complete model definition data; the reliability block diagram model of ZGM1 disassembled to the equipment level is as shown in Figure 14 ; the reliability block diagram model of ZGM8 disassembled to the equipment level is as shown in Figure 15 ; and the reliability block diagram model of ZGM13 disassembled to the equipment level is as shown in Figure 16

[0093] Finally, the running order of the integrated models, the accurate running time, and the complete model definition data obtained after disassembly are written into the reliability model XML file, which will be used as the key input of the reliability simulation evaluation calculation software for detailed and accurate reliability simulation evaluation work.

[0094] ​The application provides a task reliability modeling method and system, which breaks through the limitations of traditional reliability modeling technology, successfully realizes accurate modeling of a multi-level complex system including a whole, a system, a subsystem, equipment and the like, and assembles reliability models of different levels and different working conditions to construct a whole reliability model, thereby completely abandoning the practice of stacking all models in a single reliability block diagram in the prior art. Through the method, the application can not only realize effective reuse of models and avoid repetitive work, but also greatly improve the efficiency and accuracy of modeling, thereby providing a more efficient and convenient solution for reliability evaluation of a complex system.

[0095] The prior art is often limited to a single stage and a single working condition in task profile modeling, however, a complex system task profile in the real world usually has complex characteristics of multiple stages and variable working conditions, which makes the prior art appear inadequate when facing such a task profile and difficult to provide effective modeling support. The task reliability modeling method provided by the application can directly model a complex task profile including multiple stages and multiple working conditions without complex conversion or simplification processing. This significant advantage makes the application have a wider application prospect in production and scientific research practice and can more accurately reflect the actual operation of a complex system to provide more accurate and reliable decision support for engineering practice.

[0096] It should be understood that the above system is used to execute the method in the above embodiments, the corresponding program modules in the system, the implementation principles and technical effects are similar to the description in the above method, and the working process of the system can refer to the corresponding process in the above method, which will not be described here.

[0097] Based on the method in the above embodiments, an electronic device is provided by the embodiments of the application. The device can include at least one memory for storing programs and at least one processor for executing the programs stored in the memory. When the programs stored in the memory are executed, the processor is used to execute the method described in the above embodiments.

[0098] Based on the method in the above embodiments, a computer readable storage medium is provided by the embodiments of the application, and the computer readable storage medium stores a computer program. When the computer program runs on the processor, the processor executes the method in the above embodiments.

[0099] Based on the method in the above embodiments, a computer program product is provided by the embodiments of the application, and when the computer program product runs on the processor, the processor executes the method in the above embodiments.

[0100] It is to be understood that the processor in the embodiments of the present application can be a central processing unit (CPU), and can also be other general-purpose processors, digital signal processors (DSP), application specific integrated circuits (ASIC), field programmable gate arrays (FPGA) or other programmable logic devices, transistor logic devices, hardware components, or any combination thereof. The general-purpose processor can be a microprocessor, or any conventional processor.

[0101] The method steps in the embodiments of the present application can be implemented by means of hardware, or by means of a processor executing software instructions. The software instructions can be composed of corresponding software modules, and the software modules can be stored in a random access memory (RAM), a flash memory, a read-only memory (ROM), a programmable read-only memory (PROM), an erasable PROM (EPROM), an electrically EPROM (EEPROM), a register, a hard disk, a mobile hard disk, a CD-ROM, or any other form of storage medium well known in the art. An exemplary storage medium is coupled to the processor, so that the processor can read information from, and write information to, the storage medium. Of course, the storage medium can also be a component of the processor. The processor and the storage medium can be located in an ASIC.

[0102] In the above embodiments, all or part of the embodiments can be implemented by software, hardware, firmware or any combination thereof. When implemented by software, all or part of the embodiments can be implemented in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer program instructions are loaded and executed on a computer, all or part of the processes or functions described in the embodiments of the present application are generated. The computer can be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions can be stored in or transmitted by a computer readable storage medium. The computer instructions can be transmitted from one website, computer, server or data center to another website, computer, server or data center through a wired (such as coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (such as infrared, wireless, microwave, etc.) manner. The computer readable storage medium can be any available medium accessible by a computer or a data storage device such as a server, data center, etc. integrated with one or more available media sets. The available media can be a magnetic medium (for example, a floppy disk, a hard disk, a magnetic tape), an optical medium (for example, a DVD), or a semiconductor medium (for example, a solid state disk (SSD)), etc.

[0103] It can be understood that various numerical numbers involved in the embodiments of the present application are only distinguished for convenience of description, and are not used to limit the scope of the embodiments of the present application.

[0104] Those skilled in the art readily understand that the above only describes the preferred embodiments of the present application and is not intended to limit the present application. Any modification, equivalent replacement and improvement made within the spirit and principle of the present application shall be included in the protection scope of the present application.

Claims

1. A method of mission reliability modeling, the method comprising: The method comprises the following steps: Step 1: dividing the product into different levels from the system to the device, and establishing a product structure tree based on the different levels; Step 2: constructing a virtual unit for a node corresponding to different reliability models with different working conditions, and adding the virtual unit as a node into the product structure tree; Step 3: establishing a reliability model under different working conditions for each node in each level with the virtual unit added, and obtaining a reliability model set; if there are multiple working conditions in a node, multiple reliability models are established, and each reliability model of the same node is independent of each other; Step 4: selecting a reliability model of each level under the overall working condition scenario from the reliability model set according to the top-down principle of the product structure tree, and assembling the overall working condition model under each working condition; Step 5: dividing the task into different stages, defining the running time length ratio of each stage and the sequence between stages, selecting the overall working condition model used in each stage from the overall working condition model under each working condition, and establishing a reliability model of the task profile; Step 6: obtaining the running sequence and running time length of each overall working condition model in the task profile according to the total task time length and the time length ratio of each task stage in the reliability model of the task profile; Step 6 specifically comprises the following steps: According to the total task time length and the time length ratio of each task stage in the reliability model of the task profile, the running time length of each stage is calculated; According to the running time length ratio of the overall working condition model used in each stage and the running time length of each stage, the running time length of each overall working condition model is calculated, and the running sequence and running time length of each overall working condition model in the task profile are obtained.

2. The task reliability modeling method of claim 1, wherein, The node comprises a total, a system, a subsystem and a virtual unit; the total, the system and / or the subsystem contain a device.

3. The task reliability modeling method of claim 2, wherein, The specific steps of assembling the overall working condition model under each working condition in step 4 are as follows: First, select the reliability model of the total from the reliability model set, then select the reliability model of each system under the total, and then select the reliability model of each subsystem under each system; if the system or the subsystem contains a virtual unit, the model of the virtual unit is selected.

4. The task reliability modeling method of claim 1, wherein, In step 6, the running sequence, running time length of each overall working condition model in the task profile and the complete information describing the reliability model of the task profile constituted by the overall working condition model under each working condition in step 4 are also included, and the complete information is written into a reliability model file in XML format.

5. A mission reliability modeling system, characterized by, The method comprises: A product structure tree construction module, configured to divide the product into different levels from the system to the device, and establish a product structure tree based on the different levels; A virtual unit construction module, configured to construct a virtual unit for a node corresponding to different reliability models with different working conditions, and add the virtual unit as a node into the product structure tree; A model set acquisition module, configured to establish a reliability model under different working conditions for each node in each level with the virtual unit added, and obtain a reliability model set; if there are multiple working conditions in a node, multiple reliability models are established, and each reliability model of the same node is independent of each other; The overall working condition model assembling module is configured to select reliability models of each level under overall working condition scenarios from the reliability model set according to the top-down principle of the product structure tree, and assemble the overall working condition models under each working condition. The task profile model establishing module is configured to divide the task into different stages, define the running time length proportion of each stage and the sequence between stages, select the overall working condition models used in each stage from the overall working condition models under each working condition, and establish the reliability model of the task profile. The running parameter acquisition module is configured to acquire the running sequence and running time length of each overall working condition model in the task profile according to the total task time length and the time length proportion of each task stage in the reliability model of the task profile. The running parameter acquisition module includes: The stage running time length calculation unit is configured to calculate the running time length of each stage according to the total task time length and the time length proportion of each task stage in the reliability model of the task profile. The task profile running parameter acquisition unit is configured to calculate the running time length of each overall working condition model according to the running time length proportion of the overall working condition model used in each stage and the running time length of each stage, and acquire the running sequence and running time length of each overall working condition model in the task profile.

6. The task reliability modeling system of claim 5, wherein, The nodes in the virtual unit construction module include the overall, system, subsystem and virtual unit; the overall, system and / or subsystem contain devices.

7. The task reliability modeling system of claim 6, wherein, The specific method of the overall working condition model assembling module for assembling the overall working condition models under each working condition is as follows: first, select the reliability model of the overall from the reliability model set, then select the reliability models of each system under the overall, and then select the reliability models of each subsystem under each system; if the system or subsystem contains a virtual unit, select the model of the virtual unit.

8. The task reliability modeling system of claim 5, wherein, The model file generation module is further configured to use the running sequence and running time length of each overall working condition model in the task profile and the overall working condition models under each working condition to constitute complete information describing the reliability model of the task profile, and write the complete information into the reliability model file in XML format.

Images