RMS Modeling Method, Device, Computer Equipment and Storage Medium

Abstract

The present application relates to an RMS modeling method, apparatus, computer device, and storage medium. The method includes: obtaining analysis information of system tasks, where the analysis information includes: subtasks included in the system tasks, functions related to the subtasks, components corresponding to each function, and the logical relationships among the system tasks, subtasks, functions, and components; obtaining reconstruction strategies corresponding to functions that can be implemented through multiple execution paths among the functions; obtaining the fault characteristics, maintenance strategies, and support resources of each component; and describing the analysis information, reconstruction strategies, fault characteristics, maintenance strategies, and support resources based on a Petri net to obtain an RMS model corresponding to the system tasks. Using this method can characterize the reconstruction characteristics and is applicable to the construction of an RMS model for a reconfigurable system.

Description

Technical Field

[0001] This application relates to the technical field of general quality characteristics, and particularly to an RMS modeling method, device, computer device, and storage medium. Background Art

[0002] With the development of computer technology, communication technology, and military technology, intelligent network-centric warfare and space-air-ground integration supported by information systems have become the main combat patterns of future equipment. Typical electronic information systems such as early warning detection systems, command and control systems, integrated avionics systems, electronic countermeasure equipment, and ship dynamic positioning systems, as the core of the combat system, break through the geographical and spatial limitations in the traditional mode and seamlessly integrate different types of equipment, systems, and platforms distributed in different geographical locations and spaces through the information system, combining them into a more complex equipment system, greatly enhancing the ability and effect from target discovery to strike implementation.

[0003] As the link and key of the modern equipment system, the performance, reliability, maintainability, and supportability (RMS) of electronic information systems are crucial. If the early warning detection system fails and becomes paralyzed during the combat process, the entire fleet will lose its eyes and nerve center, unable to conduct overall combat, and the combat effectiveness will be sharply reduced. For this reason, the requirements for the RMS, function, performance, volume, weight, etc. of electronic information systems are much higher than those of general equipment. Under the existing equipment development and technological level, to meet the above requirements, advanced design methods need to be used for optimization design. The reconfiguration design technology is a design method that effectively solves the contradictions between the RMS index, function, performance, volume, weight, and other constraint conditions existing in system design. Therefore, reconfiguration design has been widely applied in the design of electronic information systems such as early warning detection systems, integrated avionics systems, electronic countermeasure equipment, and ship dynamic positioning systems.

[0004] Early warning detection systems, integrated avionics systems, electronic countermeasure equipment, ship dynamic positioning systems and other electronic information systems are generally reconfigurable systems, and such systems generally adopt reconfiguration fault tolerance technology. Fault tolerance technology refers to the technology of a system's tolerance to faults, that is, when one or more key parts of a system in the working state fail or make mistakes, the system can detect and diagnose, and can take corresponding measures to ensure that its specified function is maintained or its function is maintained within an acceptable range. Reconfiguration fault tolerance control is to set up a fault diagnosis mechanism on the basis of a conventional control system. According to the fault information provided by the fault diagnosis mechanism, the faulty components are quickly isolated, and the functional redundancy of the system is fully utilized to enable the redundant components of the system to work normally. Reconfiguration design has its own advantages and characteristics in improving system reliability and restoring system performance. It can not only implement good control over complex systems, but also ensure that the entire system remains stable when a fault occurs. At the same time, based on the functional redundancy of components, reconfiguration can be carried out quickly to keep the system maintain or appropriately reduce certain performances. Therefore, system reconfiguration has become a key technology to solve the RMS problems of complex equipment at present.

[0005] RMS refers to reliability, maintainability and supportability, which are design characteristics equally important as performance and have an important impact on the combat effectiveness, survivability, deployment mobility, maintenance manpower and usage support cost of equipment. System RMS modeling is to model the system, its components and the maintenance support activity process from the perspective of understanding the fault laws and maintenance support activities of the system, reflecting the main fault characteristics, maintenance support strategies and the timing of activity processes of the system, and is used to evaluate the availability, reliability, maintainability and supportability levels of the system. System RMS modeling is the basis for carrying out system RMS comprehensive demonstration, system RMS scheme design and optimization, and system RMS index comprehensive evaluation.

[0006] At present, an RMS modeling method based on Goal Tree - Success Tree - Dynamic Master Logic Diagram - Event Sequence Diagram (GTST - DMLD) has been formed. In this method, the equipment system consists of the main equipment and the support system. The main equipment is the part that directly executes combat or training tasks, and the support system is the part used to ensure the normal operation of the main equipment. The hierarchical decomposition of the top - level requirements of RMS is realized by using the Goal Tree (GT), and the logical hierarchies of equipment tasks, main equipment, and support system are established respectively. And through the Success Tree (ST), an association is established with the specific function level up to the product structure level, forming a mapping relationship between RMS and its influencing factors. To reduce the complexity of model description, the Dynamic Master Logic Diagram (DMLD) is used to divide the system functions into main functions and support functions and establish associations. In this way, various requirements, functions or sub - functions, devices, components, etc. all become interrelated model nodes in GTST - DMLD, and specific static or dynamic characteristics can be assigned to them, thus establishing a GTST - DMLD model that describes the interaction relationship among equipment tasks, main equipment, and support system. Based on the GTST - DMLD model, the Event Sequence Diagram (ESD) is used to model the maintenance support process, and the local GTST - DMLD model is extended to a specific maintenance support process model. ESD is more suitable for modeling maintenance support activities. For example, by using logic gates, process concurrency and competition can be simulated, parameters can simulate spare part inventory and the number of personnel, conditions can simulate waiting, and rules can express maintenance strategies, etc. The maintenance requirements of any node in the GTST - DMLD model can trigger the corresponding maintenance support ESD model to realize the simulation of the maintenance support process.

[0007] However, the above - mentioned method lacks the ability to characterize the system reconfiguration characteristics, and is unable to characterize the reconfiguration behavior and process of the reconfigurable system, resulting in the inability to meet the RMS modeling and analysis requirements of the reconfigurable system. Summary of the Invention

[0008] Based on this, it is necessary to provide an RMS modeling method, device, computer device, and storage medium that can characterize the reconfiguration characteristics for the above - mentioned technical problems.

[0009] An RMS modeling method, the method includes:

[0010] Obtain the analysis information of the system task, where the analysis information includes: subtasks included in the system task, functions related to the subtasks, components corresponding to each function, and the logical relationships among the system task, subtasks, functions, and components;

[0011] Obtain the reconfiguration strategy corresponding to the function that can be realized through multiple execution paths among the functions;

[0012] Obtain the fault characteristics, maintenance strategies, and support resources of each component;

[0013] Describe the analysis information, the reconstruction strategy, the fault characteristics, the maintenance strategy, and the support resources based on Petri nets to obtain the RMS model corresponding to the system task.

[0014] An RMS modeling device, the device includes:

[0015] The first acquisition module is used to acquire the analysis information of the system task, and the analysis information includes: the subtasks included in the system task, the functions related to the subtasks, the components corresponding to each function, and the logical relationships between the system task, the subtasks, the functions, and the components;

[0016] The second acquisition module is used to acquire the reconstruction strategy corresponding to the function that can be implemented through multiple execution paths in the function;

[0017] The third acquisition module is used to acquire the fault characteristics, maintenance strategy, and support resources of each component;

[0018] The modeling module is used to describe the analysis information, the reconstruction strategy, the fault characteristics, the maintenance strategy, and the support resources based on Petri nets to obtain the RMS model corresponding to the system task.

[0019] A computer device includes a memory and a processor, the memory stores a computer program, and when the processor executes the computer program, the following steps are implemented:

[0020] Acquire the analysis information of the system task, and the analysis information includes: the subtasks included in the system task, the functions related to the subtasks, the components corresponding to each function, and the logical relationships between the system task, the subtasks, the functions, and the components;

[0021] Acquire the reconstruction strategy corresponding to the function that can be implemented through multiple execution paths in the function;

[0022] Acquire the fault characteristics, maintenance strategy, and support resources of each component;

[0023] Describe the analysis information, the reconstruction strategy, the fault characteristics, the maintenance strategy, and the support resources based on Petri nets to obtain the RMS model corresponding to the system task.

[0024] A computer-readable storage medium stores a computer program, and when the computer program is executed by a processor, the following steps are implemented:

[0025] Obtain the analysis information of the system task, where the analysis information includes: the subtasks included in the system task, the functions related to the subtasks, the components corresponding to each function, and the logical relationships among the system task, the subtasks, the functions, and the components;

[0026] Obtain the reconstruction strategy corresponding to the function that can be implemented through multiple execution paths among the functions;

[0027] Obtain the fault characteristics, maintenance strategies, and support resources of each component;

[0028] Describe the analysis information, the reconstruction strategy, the fault characteristics, the maintenance strategy, and the support resources based on Petri nets to obtain the RMS model corresponding to the system task.

[0029] The above RMS modeling method, device, computer device, and storage medium perform RMS modeling based on Petri nets. Petri nets have the characteristics of strict formal definitions, intuitive graphical representations, rich system behavior, and dynamic characteristic analysis techniques. They can integrate information such as personnel, equipment, space, and time for description, have the ability to characterize reconstruction characteristics, are suitable for constructing RMS models of reconfigurable systems, and through unified model representation capabilities, model the tasks, functions, components, reconstruction behaviors, fault processes, maintenance activities, and support resources of the system, which is beneficial to the development of work such as RMS analysis and RMS index simulation evaluation of reconfigurable systems. Description of the Drawings

[0030] Figure 1 It is a schematic flowchart of the RMS modeling method in an embodiment;

[0031] Figure 2 It is a schematic diagram of the business process model in an embodiment;

[0032] Figure 3 It is a schematic diagram of the reconfigurable business process model in an embodiment;

[0033] Figure 4 It is a schematic diagram of the transition priority setting in an embodiment;

[0034] Figure 5 It is a schematic diagram of the fault model in an embodiment;

[0035] Figure 6 It is a schematic diagram of the corrective maintenance model in an embodiment;

[0036] Figure 7 It is a schematic diagram of the preventive maintenance model in an embodiment;

[0037] Figure 8Schematic diagram of a resource model in an embodiment;

[0038] Figure 9 Schematic diagram of an RMS model in an embodiment;

[0039] Figure 10 Structural block diagram of an RMS modeling device in an embodiment;

[0040] Figure 11 Internal structure diagram of a computer device in an embodiment;

[0041] Figure 12 Internal structure diagram of a computer device in an embodiment. Detailed implementation manners

[0042] In order to make the objectives, technical solutions and advantages of the present application clearer and more understandable, the present application will be further described in detail below with reference to 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.

[0043] In one embodiment, as Figure 1 shown, an RMS modeling method is provided, including the following steps S102 to S108.

[0044] S102. Obtain the analysis information of the system tasks, where the analysis information includes: subtasks included in the system tasks, functions related to the subtasks, components corresponding to each function, and the logical relationships among the system tasks, subtasks, functions, and components.

[0045] The functions related to the subtasks include the functions realized when the subtasks are executed. The component corresponding to the function refers to the system structure used to realize the function, and the component can be a software structure, a hardware structure, or a software and hardware combined structure.

[0046] For example, taking the display control task of an electronic system as an example, this task includes two subtasks: control management and display management. The functions related to the control management subtask include data transceiver management function and control data processing function. The functions related to the two display management subtasks include data transceiver management function and screen drawing function. The components corresponding to the data transceiver management function include short-wave communication module, ultra-short wave communication module, and satellite communication module. The components corresponding to the control data processing function include data input module and data processing module. The component corresponding to the screen drawing function includes a display module.

[0047] Specifically, by analyzing the system tasks, the subtasks, related function, and component information included in the system typical task profile are determined. For example, an electronic information system mainly executes N-stage tasks, which are respectively denoted as: S1, S2, …, S N, stage task S i There are p related subtasks, which are respectively denoted as: Subtask There are q related functions or components, which are respectively denoted as:

[0048] By analyzing the system tasks, the logical relationships among different stage tasks, subtasks, functions, and components are determined. The logical relationships can include: serial dependence relationship (with time constraint relationship), serial independent relationship (simple series relationship), parallel independent relationship (completely parallel without mutual influence), redundant backup relationship (starting another one under certain scenarios and trigger conditions for path or function reconstruction), voting relationship (denoted as k out of n, indicating that as long as k out of n devices are normal, the normal execution of system functions or system tasks can be guaranteed).

[0049] In one embodiment, the different stage tasks are in a serial dependence relationship, that is, only after stage task S i is executed, will stage task S i+1 be executed, where i ≤ N - 1. For subtasks, functions, and components, the above several logical relationships may all exist.

[0050] S104. Obtain the reconstruction strategy corresponding to the function that can be implemented through multiple execution paths in the function.

[0051] A reconfigurable system refers to a system that can re-adjust the internal structure of the system in the form of path switching, enabling redundant backups, etc. according to a certain strategy when the system tasks change or a failure occurs, so as to ensure the normal execution of system tasks. Reconstruction refers to re-adjusting the internal structure of the system without changing the system function to meet the needs of system tasks or users.

[0052] Specifically, by analyzing the working principle of the system, it is judged whether there are multiple paths for the execution of each function. If a certain function can be implemented through multiple execution paths, it is determined that the function is reconfigurable, and the reconstruction strategy corresponding to the function is obtained. The reconstruction strategy can include but is not limited to reconstruction scenarios, reconstruction paths, and trigger conditions. In one embodiment, if a certain device module fails during the operation of the system, resulting in the initial execution path of the corresponding function being blocked, the backup can be enabled or the system structure can be adjusted to enable other paths that can implement the same function to continue the task.

[0053] S106. Obtain the fault characteristics, maintenance strategies, and support resources of each component.

[0054] By analyzing the state changes, maintenance activities, related maintenance tools, spare parts, and personnel after a failure occurs in each component, the failure characteristics, maintenance strategies, and support resources of the component are obtained. The failure characteristics may include failure features and patterns. Maintenance strategies can be classified into corrective maintenance and preventive maintenance according to categories. Support resources may include consumable items (such as spare parts) and reusable resources (such as maintenance tools and maintenance personnel).

[0055] S108, describe the analysis information, reconstruction strategy, failure characteristics, maintenance strategy, and support resources based on Petri nets to obtain the RMS model corresponding to the system task.

[0056] Petri nets have a strict mathematical representation, an intuitive graphical expression, rich system description means, and system behavior analysis techniques, and are suitable for describing asynchronous and concurrent computer system models. The elements in Petri nets include places, transitions, arcs, tokens, capacities, etc. Among them, places represent circular nodes, transitions represent square nodes, arcs represent directed arcs between places and between places and transitions, tokens represent dynamic objects in places and can move from one place to another, and capacities represent the specific values of tokens.

[0057] In one embodiment, establish the mapping relationship between the elements in Petri nets and the relevant elements in the system; according to the mapping relationship, describe the analysis information, reconstruction strategy, failure characteristics, maintenance strategy, and support resources to obtain the RMS model corresponding to the system task.

[0058] The elements such as places, transitions, and arcs in Petri nets correspond to the relevant elements such as tasks (including stage tasks and subtasks), functions, states, and rules in the system. The specific mapping relationship can be as shown in Table 1 below.

[0059] Table 1

[0060] Relevant elements in the system Petri net Task and functional structure status, resource status Place Resource limit, status limit Capacity Start and end of the process, execution and implementation of task functions Transition Resources, status Token Systems, rules, operation sequence Arc, arc weight function

[0061] According to the above mapping relationship, Petri nets can be used to characterize the execution process, state transformation, timing and time consumption, and dynamic resource change process of system tasks. It not only has the ability to characterize the reconstruction characteristics but also can describe the timing and time elements of a series of maintenance support activities after a failure occurs, realizing the modeling of business processes, reconstruction behaviors, failure behaviors, maintenance activities, and support resources, and solving the RMS modeling problem of reconfigurable systems.

[0062] In the above RMS modeling method, Petri nets are used for RMS modeling. Petri nets have the characteristics of strict formal definitions, intuitive graphical representations, rich system behavior, and dynamic characteristic analysis techniques. They can integrate information such as personnel, equipment, space, and time for description, have the ability to characterize reconfiguration characteristics, and are suitable for constructing RMS models of reconfigurable systems. Through unified model representation capabilities, the tasks, functions, components, reconfiguration behaviors, fault processes, maintenance activities, and support resources of the system are modeled, which is conducive to the development of work such as RMS analysis and RMS index simulation evaluation of reconfigurable systems.

[0063] In one embodiment, the steps of obtaining the RMS model corresponding to the system task by describing the analysis information, reconfiguration strategy, fault characteristics, maintenance strategy, and support resources based on Petri nets may specifically include: describing the analysis information based on Petri nets to obtain a business process model; on the basis of the business process model, adding the descriptions of the reconfiguration strategy, fault characteristics, maintenance strategy, and support resources based on Petri nets to obtain the RMS model corresponding to the system task.

[0064] The steps of describing the analysis information based on Petri nets to obtain a business process model may specifically include: using places to describe the states of system tasks, subtasks, functions, and components, using transitions to describe the execution processes of system tasks, subtasks, and functions, and using connection arcs to describe the logical relationships between system tasks, subtasks, functions, and components to obtain a business process model.

[0065] The state of a task may include task start, task execution, and task end. The state of a function may include function start, function operation, and function end. The state of a component may include normal and faulty. The execution process of a task may include the start time of the process, the specific task content executed at each time point, the duration, and the end time. The execution process of a function may include the function start time, the specific function points executed at each time point, the duration, and the end time. The logical relationships between tasks, functions, and components may include execution systems, rules, and time sequences.

[0066] Taking the display control task of a certain electronic system as an example, this task is divided into two subtasks: control management and display management. The related functions include data transceiver management function, control data processing function, and screen drawing function. The corresponding main software and hardware structures include a data input module, a data processing module, a short-wave communication module, a ultra-short-wave communication module, a satellite communication module, and a display module. Among them, the control management subtask and the display management subtask are independent at the task level, and their specific execution processes both depend on the realization of the data transceiver management function.

[0067] The business process model corresponding to the above display control task is established using Petri nets, as Figure 2 shown. Among them, circular nodes represent places, square nodes represent transitions, and arrows represent connecting arcs. Double-headed arrows are located between reusable resources (equipment, tools, personnel, etc.) and the places they support, indicating that the resources can be reused. Single-headed arrows are located between places and transitions, indicating the logical relationship of system state changes. The numbers on the connecting arcs represent the number of resources required for the occurrence or the number of state changes caused after the occurrence of the transition. By default, it is 1, indicating that the number of resources required for the occurrence of an event is 1 or there is only 1 change caused by the state change. Figure 2 The types, meanings, and parameter descriptions of each place and transition in Figure 2 are shown in Table 2 below.

[0068] Table 2

[0069]

[0070]

[0071] An initial token of 1 or greater than 1 is the basic condition for triggering the transition behind the place. When the initial token is 0, the transition behind the place will not execute. The initial token of the first place in the model is 1 to ensure that the model can execute. After the transition corresponding to the first place is executed, the corresponding token becomes 0 and transfers to the subsequent place, promoting the subsequent transitions to execute in a certain time sequence. Therefore, the initial token of the subsequent places is 0, otherwise the entire model will execute simultaneously.

[0072] In one embodiment, based on the business process model, the steps of adding descriptions of the reconfiguration strategy, fault characteristics, maintenance strategy, and support resources based on Petri nets to obtain the RMS model corresponding to the system task may specifically include: based on the business process model, adding a description of the reconfiguration strategy based on Petri nets to obtain a reconfigurable business process model; based on the reconfigurable business process model, adding descriptions of the fault characteristics, maintenance strategy, and support resources based on Petri nets to obtain the RMS model corresponding to the system task.

[0073] Based on the above business process model, according to the system working principle, analyze the reconfiguration scenario, use Petri nets for system reconfiguration modeling, and clarify the reconfiguration trigger conditions, thereby forming a reconfigurable business process model, that is, a complete system business process model. Specifically, the reconfiguration strategy includes the reconfiguration path and trigger conditions. The reconfiguration path includes the reconfigured subtasks, functions, and components, as well as the logical relationships between the reconfigured subtasks, functions, and components. The places, transitions, arcs, etc. in Petri nets correspond to the relevant functions, states, rules, etc. in the reconfiguration path.

[0074] In one embodiment, based on the business process model, the steps of adding a description of the reconstruction strategy based on Petri nets to obtain a reconfigurable business process model may specifically include: using places to describe the states of the reconstructed functions and components, using transitions to describe the execution processes of the reconstructed subtasks and functions, using connection arcs to describe the logical relationships between the reconstructed subtasks, functions, and components, using transition priorities to describe the triggering conditions for reconstruction, and obtaining a reconstruction model; adding the reconstruction model to the business process model to obtain a reconfigurable business process model.

[0075] Taking Figure 2 the display control task of an electronic system as an example, in order to ensure the normal realization of the control management function during the task execution process, during system design, the information receiving and transmitting module and the comprehensive processing module in the comprehensive processing subsystem in the system are coordinated and utilized to implement the control management function. The relevant modules are the comprehensive information receiver and the signal processor. Only when the data receiving and transmitting management function cannot be realized will the system reconstruction be triggered and the comprehensive information receiver be enabled; only when the control data processing function cannot be realized will the system reconstruction be triggered and the signal processor be enabled.

[0076] Taking the control data processing function failure as an example, based on the business process model shown in Figure 2 , 3 places and 3 transitions are added, and the triggering conditions for reconstruction are determined by setting transition priorities, and a business process model considering the reconstruction of the control data processing function is established, as shown in Figure 3 . Figure 3 The model shown is based on Figure 2 , with 3 ordinary places (P_4*, P_8*, P_30), 1 timed transition (T_5*), and 2 instantaneous transitions (T_2*, T_7*) added. Among them, P_4* represents the start of the reconstructed control data processing function; P_8* represents the end of the reconstructed control data processing function; P_30 represents the signal processor, with an initial token of 1; T_5* represents the execution of the reconstructed control data processing function, with the time being a fixed time or a Gaussian distribution time, and the time represents the execution time of the reconstructed control data processing function; T_2* represents the arrival of the reconstructed control management subtask, with the time representing the arrival time of the reconstructed control management subtask, occurring instantaneously, and the time can be ignored; T_7* represents the completion of the execution of the reconstructed control management subtask, with the time representing the time taken for this activity of the completion of the execution of the reconstructed control management subtask, occurring instantaneously, and the time can be ignored.

[0077] The setting of the transition priorities is as shown in Figure 4 . The priority of the instantaneous transition T_2* is after the instantaneous transition T_2. When a failure occurs in the path where the instantaneous transition T_2 is located, the path where the instantaneous transition T_2* is located is triggered. That is to say, althoughFigure 3 There are two paths in the model shown from the start state (P_2) of the control and management subtask to the end state (P_10) of the control and management subtask, namely through the instantaneous transition T_2 and the instantaneous transition T_2*. However, the path where T_2* is located is the reconstructed path, and this path switch will only be triggered when the control data processing function supported by P_16 and P_17 cannot be realized (it may be that the device module corresponding to P_16 fails, or the device module corresponding to P_17 fails, or both P_16 and P_17 fail simultaneously). Under normal circumstances, this path plays the role of information reception, transmission, and comprehensive information processing in the integrated processing subsystem.

[0078] In one embodiment, based on the reconfigurable business process model, the steps of adding the description of fault characteristics, maintenance strategies, and support resources based on Petri nets to obtain the RMS model corresponding to the system task may specifically include: using transitions to describe the interval time of component failures, using places to describe the fault states of components, using connecting arcs to describe the component state changes and fault impacts to obtain a fault model; using transitions to describe the execution process of component maintenance activities, using places to describe the states of component maintenance activities, using connecting arcs to describe the state changes of maintenance activities to obtain a maintenance model; using places to describe support resources, using connecting arcs to describe the logical relationship between support resources and corresponding maintenance activities to obtain a support resource model; adding the fault model, maintenance model, and support resource model to the reconfigurable business process model to obtain the RMS model corresponding to the system task.

[0079] Based on the above reconfigurable business process model, according to the fault characteristics and laws of relevant components (devices or modules), pre-determined maintenance support strategies, and available support resources, use Petri nets to model the fault process, maintenance activities, and support resources.

[0080] According to the fault characteristics and laws of relevant components, use elements such as transitions, places, and connecting arcs in Petri nets to describe the fault process and establish the fault models of each component. Taking Figure 2 the P_12 display module in as an example, this module may fail. If it fails, the screen drawing function needs to stop and can only resume until the device maintenance is completed. Accordingly, the fault model corresponding to the P_12 display module is established as shown in Figure 5 . Figure 5 The model shown is in Figure 2Based on this, one time transition (T_9), one ordinary place (P_18), and one inhibitory arc are added. Among them, T_9 represents the interval time of the module represented by P_12 failing, and the time is exponentially distributed or a fixed value; P_18 represents the failure state of the module represented by P_12; the arc from P_18 to P_3 is an inhibitory arc, indicating the failure impact, specifically that the failure occurrence state will cause the state where P_3 is located to pause.

[0081] According to the maintenance strategies of relevant components, elements such as transitions, places, and connecting arcs in the Petri net are used to describe the maintenance activities. According to the type of maintenance, it can be divided into corrective maintenance and preventive maintenance, and the model is characterized according to the actual situation of the analysis object. If preventive maintenance is not carried out, only corrective maintenance needs to be considered. If it has been determined in advance that preventive maintenance is required and the preventive maintenance cycle is given, then both corrective maintenance and preventive maintenance are modeled.

[0082] For corrective maintenance modeling, based on the above failure model, elements such as places, transitions, and connecting arcs in the Petri net are used to describe the corrective maintenance process, and the corrective maintenance models of each component are established. Taking Figure 5 the P_12 display module in as an example, after this module fails, it can be repaired, and after the repair is completed, it continues to support the realization of the screen drawing function. Accordingly, the corrective maintenance model corresponding to the P_12 display module is established, as shown in Figure 6 shown. Figure 6 The model shown is based on Figure 5 and adds one time transition (T_10), one instantaneous transition (T_11), and one ordinary place (P_19). Among them, T_10 represents the execution of the corrective maintenance activity, and the corresponding time is a fixed time or a Gaussian distribution time, representing the failure repair time; T_11 represents the instantaneous process of the completion of the corrective maintenance activity, and the time can be ignored; P_19 represents the state of the completion of the corrective maintenance activity.

[0083] For preventive maintenance modeling, after reaching the specified time when preventive maintenance is required, after the relevant tasks are completed, preventive maintenance is immediately implemented. During preventive maintenance, it is also unable to work, and it will not work normally again until preventive maintenance is completed. Considering the actual situation, when the preventive maintenance cycle arrives, the task execution will not be terminated immediately, but preventive maintenance will be implemented after the relevant tasks are completed. Therefore, a control place is added to the above process, and the system, according to the actual situation, uses software enabling to trigger and decide whether to implement preventive maintenance. Based on the above failure model and corrective maintenance model, elements such as transitions, places, and connecting arcs in the timed Petri net are used to describe the preventive maintenance process, and the preventive maintenance models of each component are established.

[0084] Taking Figure 6 the P_12 display module in Figure 7 as an example, after the module has worked for a certain time t, preventive maintenance is required. After the maintenance is completed, it continues to support the realization of the screen drawing function. Accordingly, a preventive maintenance model corresponding to the P_12 display module is established, as shown in Figure 7 The model shown is based on Figure 6 On this basis, 3 time transitions (T_12, T_13, T_14), one instantaneous transition (T_15), 3 ordinary places (P_20, P_22, P_23), one logical control place (P_21), and one inhibitory arc are added. Among them, T_12 represents the preventive maintenance cycle of the P_12 module, and the time is exponentially distributed or a fixed value, representing the preventive maintenance time interval; T_13 represents whether to trigger preventive maintenance, and the time is judged and generated by P_21 according to the progress of system task execution; T_14 represents the execution of preventive maintenance activities, and the corresponding time is a fixed time or a Gaussian distribution time, representing the preventive maintenance time; T_15 represents the instantaneous process of the completion of preventive maintenance activities, and the time can be ignored; P_20 represents the state of reaching the preventive maintenance cycle time; P_21 represents the logical control of whether to immediately perform preventive maintenance after the preventive maintenance cycle arrives; P_22 represents the start state of preventive maintenance activities; P_23 represents the completion state of preventive maintenance activities; the arc from P_22 to P_3 is an inhibitory arc, indicating that the corresponding function is suspended after the start of preventive maintenance activities.

[0085] According to the maintenance work requirements of relevant components, build a support resource model, and use places, tokens, and arcs in Petri nets to establish the mapping relationship between the execution processes of corrective maintenance and preventive maintenance activities and relevant support resources, so as to establish a support resource model corresponding to each maintenance activity.

[0086] Taking Figure 7 the P_12 display module in Figure 8 as an example, when this module performs corrective maintenance, it requires 1 display module spare part, 1 screwdriver for disassembling the display module, 1 pair of pliers, and 1 professional. Accordingly, a support resource model for the corrective maintenance activities corresponding to the P_12 display module is established, as shown in Figure 8 The model shown is based on Figure 7On this basis, 4 ordinary places (P_24, P_25, P_26, P_27), 3 bidirectional arcs and 1 unidirectional arc are added. Among them, P_24 represents the spare parts of the display module, and the initial token is 1; P_25 represents the maintenance tool (screwdriver) required for corrective maintenance, and the initial token is 1; P_26 represents the maintenance tool (pliers) required for corrective maintenance, and the initial token is 1; P_27 represents the professional maintenance personnel required for corrective maintenance, and the initial token is 1; Since the spare parts are consumable items and the maintenance tools and personnel can be reused, a unidirectional arc is used between the spare parts and the corrective maintenance activities, and bidirectional arcs are used between the maintenance tools and personnel and the corrective maintenance activities.

[0087] Through the above modeling of business processes, reconstruction behaviors, fault processes, maintenance activities, and support resources, a complete system RMS model can be established, as Figure 9 shown, which provides an RMS model for the display control task of an electronic system in an embodiment. Subsequently, with the help of the dynamic simulation function of the Petri net, the system RMS simulation analysis can be carried out.

[0088] In the above embodiment, through system task analysis and system structure modeling, using elements such as places, tokens, and transitions in the time-constrained Petri net, the mapping relationships among system tasks, functions, and components under system task constraints are established. According to the fault characteristics and maintenance support strategies of each component in the system, fault modeling, maintenance activity modeling, and support resource modeling are carried out, and according to the switching scenarios and triggering conditions between different paths in the system, system reconstruction modeling is carried out, and finally a system RMS model that can characterize the reconstruction characteristics is formed. This modeling method is of great significance for solving the RMS modeling problems of electronic information systems with reconstruction functions such as early warning detection systems, command and control systems, integrated avionics systems, electronic countermeasure equipment, and ship dynamic positioning systems. It solves the problems of functional reconstruction characteristic analysis and graphical representation of electronic information systems, as well as the unified representation problem of the RMS model of reconfigurable systems, including system task decomposition, structural logical relationship representation, fault impact relationship transmission, maintenance activity execution process, support resource call and consumption process, etc. It can effectively guide the development of work such as task and function structure representation, reconstruction behavior representation, fault behavior, maintenance activity, and support resource modeling of reconfigurable systems, and can effectively support the development of work such as RMS analysis and RMS index simulation evaluation of reconfigurable systems.

[0089] It should be noted that the Petri net in the above embodiment can adopt a general time Petri net, a transition delay Petri net, a place delay Petri net, or other improved Petri nets, as long as it can represent the system task execution process, state transformation, timing and time consumption, and resource dynamic change process.

[0090] It should be noted that when establishing a business process model, in addition to directly using Petri nets to establish the corresponding business process model based on the analysis of system tasks and functional structures, it is also possible to first use the activity diagram in UML to describe the business process, and then convert it into a Petri net-based business process model through the mapping relationship between the relevant elements in the UML activity diagram and the relevant elements in Petri nets.

[0091] It should be noted that in the above embodiments, business process modeling is first carried out based on the analysis of system tasks and functional structures, then the reconstruction behavior is modeled according to the system reconstruction strategy, and finally, fault modeling, maintenance activity modeling, and support resource modeling are carried out according to the fault laws of system equipment modules and maintenance support strategies, and finally a system RMS model is formed. In addition, it is also possible to first carry out business process modeling, then carry out fault modeling, maintenance activity modeling, and support resource modeling, and finally carry out reconstruction behavior modeling, as long as the construction effect of the system RMS model can be finally achieved.

[0092] It should be understood that although the steps in each flowchart involved in the above embodiments are displayed in sequence according to the arrows, these steps are not necessarily executed in the order indicated by the arrows. Unless there is a clear description in this article, the execution of these steps has no strict order limit, and these steps can be executed in other orders. Moreover, at least a part of the steps in each flowchart involved in the above embodiments may include multiple steps or multiple stages. These steps or stages are not necessarily executed at the same time, but can be executed at different times. The execution order of these steps or stages is not necessarily sequential, but can be executed alternately or alternately with at least a part of other steps or steps or stages in other steps.

[0093] In one embodiment, as Figure 10 shown, an RMS modeling device 1000 is provided, including: a first acquisition module 1010, a second acquisition module 1020, a third acquisition module 1030, and a modeling module 1040, where:

[0094] The first acquisition module 1010 is configured to acquire analysis information of system tasks, and the analysis information includes: subtasks included in the system tasks, functions related to the subtasks, components corresponding to each function, and the logical relationships between the system tasks, subtasks, functions, and components.

[0095] The second acquisition module 1020 is configured to acquire the reconstruction strategy corresponding to the function that can be implemented through multiple execution paths in the function.

[0096] The third acquisition module 1030 is configured to acquire the fault characteristics, maintenance strategies, and support resources of each component.

[0097] A modeling module 1040, configured to describe analysis information, reconfiguration strategies, fault characteristics, maintenance strategies, and support resources based on a Petri net, and obtain an RMS model corresponding to a system task.

[0098] In one embodiment, the modeling module 1040 is specifically configured to: establish a mapping relationship between elements in the Petri net and relevant elements in the system; and describe the analysis information, reconfiguration strategies, fault characteristics, maintenance strategies, and support resources according to the mapping relationship, so as to obtain an RMS model corresponding to the system task.

[0099] In one embodiment, the modeling module 1040 is specifically configured to: describe the analysis information based on the Petri net to obtain a business process model; and on the basis of the business process model, add descriptions of the reconfiguration strategies, fault characteristics, maintenance strategies, and support resources based on the Petri net, so as to obtain an RMS model corresponding to the system task.

[0100] In one embodiment, the elements in the Petri net include places, transitions, and arcs; when the modeling module 1040 describes the analysis information based on the Petri net to obtain a business process model, it is specifically configured to: use places to describe the states of system tasks, subtasks, functions, and components, use transitions to describe the execution processes of system tasks, subtasks, and functions, and use arcs to describe the logical relationships between system tasks, subtasks, functions, and components, so as to obtain a business process model.

[0101] In one embodiment, when the modeling module 1040 adds descriptions of the reconfiguration strategies, fault characteristics, maintenance strategies, and support resources based on the Petri net on the basis of the business process model to obtain an RMS model corresponding to the system task, it is specifically configured to: on the basis of the business process model, add a description of the reconfiguration strategy based on the Petri net to obtain a reconfigurable business process model; and on the basis of the reconfigurable business process model, add descriptions of the fault characteristics, maintenance strategies, and support resources based on the Petri net, so as to obtain an RMS model corresponding to the system task.

[0102] In one embodiment, the reconstruction strategy includes a reconstruction path and a trigger condition. The reconstruction path includes the reconstructed subtasks, functions, and components, as well as the logical relationships between the reconstructed subtasks, functions, and components. When adding a description of the reconstruction strategy based on Petri nets to the business process model to obtain a reconfigurable business process model, the modeling module 1040 is specifically configured to: use places to describe the states of the reconstructed functions and components, use transitions to describe the execution processes of the reconstructed subtasks and functions, use connecting arcs to describe the logical relationships between the reconstructed subtasks, functions, and components, use transition priorities to describe the trigger conditions for reconstruction, and obtain a reconstruction model; add the reconstruction model to the business process model to obtain a reconfigurable business process model.

[0103] In one embodiment, when adding a description of fault characteristics, maintenance strategies, and support resources based on Petri nets to the reconfigurable business process model to obtain an RMS model corresponding to the system task, the modeling module 1040 is specifically configured to: use transitions to describe the time intervals between component failures, use places to describe the fault states of components, use connecting arcs to describe component state changes and fault impacts, and obtain a fault model; use transitions to describe the execution processes of component maintenance activities, use places to describe the states of component maintenance activities, use connecting arcs to describe changes in maintenance activity states, and obtain a maintenance model; use places to describe support resources, use connecting arcs to describe the logical relationships between support resources and corresponding maintenance activities, and obtain a support resource model; add the fault model, maintenance model, and support resource model to the reconfigurable business process model to obtain an RMS model corresponding to the system task.

[0104] For specific limitations on the RMS modeling device, reference can be made to the limitations on the RMS modeling method described above, which will not be elaborated here. Each module in the above RMS modeling device can be implemented in whole or in part by software, hardware, and their combinations. The above modules can be embedded in the processor of the computer device in hardware form or be independent of it, or can be stored in the memory of the computer device in software form for the processor to call and execute the operations corresponding to the above respective modules.

[0105] In one embodiment, a computer device is provided. The computer device can be a server, and its internal structure diagram can be as Figure 11As shown in the figure. The computer device includes a processor, a memory, and a network interface connected through a system bus. Among them, 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 network 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, it implements an RMS modeling method.

[0106] In one embodiment, a computer device is provided. The computer device may be a terminal, and its internal structure diagram may be as Figure 12 shown in the figure. The computer device includes a processor, a memory, a communication interface, a display screen, and an input device connected through a system bus. Among them, 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 and a computer program. The internal memory provides an environment for the operation of the operating system and the computer program in the non-volatile storage medium. The communication interface of the computer device is used to communicate with an external terminal in a wired or wireless manner. The wireless manner can be implemented through WIFI, a carrier network, NFC (Near Field Communication), or other technologies. When the computer program is executed by the processor, it implements an RMS modeling method. The display screen of the computer device may be a liquid crystal display screen or an electronic ink display screen. The input device of the computer device may be a touch layer covering the display screen, or may also be a button, a trackball, or a touchpad provided on the computer device housing, or may also be an external keyboard, touchpad, or mouse, etc.

[0107] Those skilled in the art can understand that Figure 11 or Figure 12 the structure shown in the figure is only a block diagram of some structures related to the solution of this application, and does not constitute a limitation on the computer device to which the solution of this application is applied. The specific computer device may include more or fewer components than those shown in the figure, or combine some components, or have different component arrangements.

[0108] In one embodiment, a computer device is further provided, including a memory and a processor. A computer program is stored in the memory, and when the processor executes the computer program, it implements the steps in the above method embodiments.

[0109] In one embodiment, a computer-readable storage medium is provided, storing a computer program, and when the computer program is executed by the processor, it implements the steps in the above method embodiments.

[0110] In one embodiment, a computer program product or a computer program is provided. The computer program product or the computer program includes computer instructions stored in a computer-readable storage medium. A processor of a computer device reads the computer instructions from the computer-readable storage medium, and the processor executes the computer instructions, causing the computer device to perform the steps in the above method embodiments.

[0111] It should be understood that the terms "first", "second", etc. in the above embodiments are only used for descriptive purposes and cannot be construed as indicating or implying relative importance or implicitly specifying the quantity of the indicated technical features. In addition, in the description of the present application, unless otherwise stated, the meaning of "a plurality of" refers to at least two.

[0112] Those of ordinary skill in the art can understand that all or part of the processes of implementing the methods in the above embodiments can be completed by instructing relevant hardware through a computer program. 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 methods. Among them, any reference to a memory, storage, database, or other medium used in the embodiments provided in the present application can include at least one of non-volatile and volatile memories. Non-volatile memory can include read-only memory (ROM), magnetic tape, floppy disk, flash memory, or optical memory, etc. Volatile memory can include random access memory (RAM) or external cache memory. By way of illustration and not limitation, RAM can be in various forms, such as static random access memory (SRAM) or dynamic random access memory (DRAM), etc.

[0113] The technical features of the above embodiments can be combined arbitrarily. For the sake of brevity of description, 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, it should be considered as the scope described in this specification.

[0114] The above-described embodiments only represent several implementation manners of the present application. Their descriptions are relatively specific and detailed, but they should not be construed as limiting the scope of the invention patent. It should be noted that for those of ordinary skill in the art, without departing from the concept of the present application, several modifications and improvements can still be made, and these all belong to the protection scope of the present application. Therefore, the protection scope of the patent of the present application should be subject to the appended claims.

Claims

1. An RMS modeling method, characterized in that, The method includes: Obtaining analysis information of system tasks, where the analysis information includes: subtasks included in the system tasks, functions related to the subtasks, components corresponding to each function, and logical relationships among the system tasks, subtasks, functions, and components; Obtaining a reconstruction strategy corresponding to a function that can be implemented through multiple execution paths among the functions; Obtaining the fault characteristics, maintenance strategies, and support resources of each component; Describing the analysis information, the reconstruction strategy, the fault characteristics, the maintenance strategies, and the support resources based on Petri nets to obtain an RMS model corresponding to the system tasks; Describing the analysis information based on Petri nets to obtain a business process model; On the basis of the business process model, adding a description of the reconstruction strategy based on Petri nets to obtain a reconfigurable business process model; where the reconstruction strategy includes a reconstruction path and a trigger condition, and the reconstruction path includes reconstructed subtasks, functions, and components, and logical relationships among the reconstructed subtasks, functions, and components; On the basis of the reconfigurable business process model, adding a description of the fault characteristics, the maintenance strategies, and the support resources based on Petri nets to obtain an RMS model corresponding to the system tasks.

2. The method according to claim 1, wherein Describing the analysis information, the reconstruction strategy, the fault characteristics, the maintenance strategies, and the support resources based on Petri nets to obtain an RMS model corresponding to the system tasks, including: Establishing a mapping relationship between elements in Petri nets and relevant elements in the system; According to the mapping relationship, describing the analysis information, the reconstruction strategy, the fault characteristics, the maintenance strategies, and the support resources to obtain an RMS model corresponding to the system tasks.

3. The method according to claim 1, characterized in that, Elements in the Petri nets include places, transitions, and connecting arcs; Describing the analysis information based on Petri nets to obtain a business process model, including: Using places to describe the states of the system tasks, subtasks, functions, and components, using transitions to describe the execution processes of the system tasks, subtasks, and functions, and using connecting arcs to describe the logical relationships among the system tasks, subtasks, functions, and components to obtain a business process model.

4. The method according to claim 1, wherein On the basis of the business process model, adding a description of the reconstruction strategy based on Petri nets to obtain a reconfigurable business process model, including: Using places to describe the states of the reconstructed functions and components, using transitions to describe the execution processes of the reconstructed subtasks and functions, using connecting arcs to describe the logical relationships among the reconstructed subtasks, functions, and components, and using transition priorities to describe the trigger conditions for reconstruction to obtain a reconstruction model; Adding the reconstruction model to the business process model to obtain a reconfigurable business process model.

5. The method according to claim 4, wherein Based on the reconfigurable business process model, add the descriptions of the fault characteristics, the repair strategy, and the support resources based on Petri nets to obtain the RMS model corresponding to the system task, including: Describe the time interval between component failures using transitions, describe the fault states of components using places, and describe the changes in component states and the impact of faults using connecting arcs to obtain a fault model; Describe the execution process of component repair activities using transitions, describe the states of component repair activities using places, and describe the changes in repair activity states using connecting arcs to obtain a repair model; Describe the support resources using places, and describe the logical relationship between the support resources and the corresponding repair activities using connecting arcs to obtain a support resource model; Add the fault model, the repair model, and the support resource model to the reconfigurable business process model to obtain the RMS model corresponding to the system task.

6. An RMS modeling device, characterized in that, The device includes: A first acquisition module for acquiring analysis information of a system task, where the analysis information includes: subtasks included in the system task, functions related to the subtasks, components corresponding to each function, and the logical relationships between the system task, the subtasks, the functions, and the components; A second acquisition module for acquiring the reconfiguration strategy corresponding to the function that can be implemented through multiple execution paths; A third acquisition module for acquiring the fault characteristics, repair strategies, and support resources of each component; A modeling module for describing the analysis information based on Petri nets to obtain a business process model; on the basis of the business process model, add the description of the reconfiguration strategy based on Petri nets to obtain a reconfigurable business process model; where the reconfiguration strategy includes a reconfiguration path and a trigger condition, and the reconfiguration path includes the reconfigured subtasks, functions, and components, and the logical relationships between the reconfigured subtasks, functions, and components; on the basis of the reconfigurable business process model, add the descriptions of the fault characteristics, the repair strategy, and the support resources based on Petri nets to obtain the RMS model corresponding to the system task.

7. A computer device, comprising a memory and a processor, the memory storing a computer program, characterized in that, When the processor executes the computer program, it implements the steps of the method according to any one of claims 1 to 5.

8. A computer-readable storage medium having a computer program stored thereon, characterized in that, When the computer program is executed by the processor, it implements the steps of the method according to any one of claims 1 to 5.

Images