Aircraft release decision method and system based on mission objectives

Abstract

This invention provides a method and system for aircraft launch decision-making based on mission objectives. The method includes: S1, constructing an aircraft configuration state tree and an aircraft capability tree; S2, constructing a fault database and a damage database, and correcting the aircraft capability tree; S3, enumerating possible fault and damage states of the aircraft, and establishing an aircraft capability state database; S4, decomposing the mission objectives and obtaining the minimum capability requirements required to perform the mission objectives under each aircraft mission configuration; S5, conducting aircraft capability and mission objective matching analysis; S6, assessing the support resources required for aircraft launch; and S7, making a launch decision and formulating a launch implementation plan. By transforming the aircraft's design documents and using the probability of achieving the mission objectives as a guide, the boundaries of the aircraft's configuration components and immediate support are clearly defined, significantly shortening the decision-making time, deeply exploring the aircraft's capability potential, and making the decision-making process scientific and efficient, effectively supporting the completion of mission objectives.

Description

Technical Field

[0001] This invention belongs to the field of flight launch decision technology, and relates to a method and system for making aircraft flight launch decisions based on mission objectives. Background Technology

[0002] Aircraft launch decision refers to the decision made in an emergency based on the aircraft's system or equipment status to determine whether to launch the aircraft, ensuring that the launched aircraft possesses an acceptable level of safety and the technical capability to perform its mission. Aircraft launch depends on multiple factors, including the aircraft's status, mission objectives, and pre- and post-launch support conditions.

[0003] Currently, aircraft launch decisions primarily focus on two aspects: the extent of aircraft damage and system or equipment malfunctions beyond the aircraft damage. In the field of equipment support, various assessment methods exist for damage, but these methods focus on the maintenance of the equipment itself, lacking an assessment of the aircraft's ability to perform missions while in a state of battlefield damage. Regarding malfunctions beyond damage, the approach to establishing minimum launch conditions in emergency situations is similar to the Master Minimum Equipment List for civil aircraft, emphasizing safety-oriented analysis. This method is rather mechanical and insufficiently considers the necessity and urgency of the mission. Summary of the Invention

[0004] The problem that this invention aims to solve is that the existing technology lacks an aircraft launch decision-making method in emergency situations that comprehensively considers factors such as the aircraft's condition, mission objectives, and support conditions. Therefore, this invention provides an aircraft launch decision-making method and system based on mission objectives.

[0005] The first aspect of this invention provides an aircraft launch decision method based on mission objectives, comprising: S1. Construct the aircraft configuration state tree and the aircraft capability tree; S2. Construct a fault database and a damage database, and revise the aircraft capability tree; S3. Enumerate the possible fault and damage states of the aircraft and establish an aircraft capability status database. S4. Decompose the mission objectives and obtain the minimum capability requirements required to perform the mission objectives under each aircraft mission configuration; S5. Conduct aircraft capability and mission objective matching analysis; S6. Assess the support resources required for aircraft launch; S7. Make a decision on the flight and formulate a flight implementation plan.

[0006] Optionally, the aircraft configuration state tree is established by decomposing the aircraft product structure and using a standard numbering system; the aircraft configuration state tree includes: aircraft, system, subsystem, sub-subsystem and component levels.

[0007] Optionally, each node in the aircraft capability tree corresponds one-to-one with the relevant node in the configuration state tree. The aircraft capability tree includes aircraft capability indicators, system capability indicators, subsystem capability indicators, sub-subsystem capability indicators, and component capability indicators.

[0008] Optionally, the fault database records fault mode analysis data, including: fault causes, impact on the failure rate of related systems / components, fault effects, corrective requirements for flight operations, and troubleshooting solutions. The battlefield damage database records battlefield damage assessment and repair analysis data, including: battlefield damage type, impact on the failure rate of related systems / components, damage impact, correction requirements for flight operations, and troubleshooting solutions.

[0009] Optionally, decompose the mission objectives to obtain the minimum capability requirements needed to perform the mission objectives under each aircraft mission configuration, including: For the mission objectives, and based on the selected type of aircraft, propose multiple alternative mission configuration schemes under normal aircraft conditions; For each alternative mission configuration, distinguish between the capability requirements related to the mission profile and other capability requirements; For the capability requirements related to the mission profile, the mission objectives are decomposed into sub-mission objectives for different flight / mission phases of the aircraft according to the mission profile, and capability indicators corresponding to each sub-mission objective are proposed according to the capability indicator set. For other capability requirements, capability indicators corresponding to the objectives of each sub-task are proposed according to the set of capability indicators; The above capability indicators are the minimum requirements for an aircraft to accomplish its mission objectives.

[0010] Optionally, perform aircraft capability and mission objective matching analysis, including: Select projects from the set of failure modes and battlefield damage under different troubleshooting / repair schemes, extract the capability indicators corresponding to each project, and extract the mission capability requirements corresponding to each alternative mission configuration scheme. For each selected project, the aircraft capability indicators are compared one by one to see if they meet the mission capability requirements of each alternative mission configuration. Retrieve each item from the set one by one and perform the above comparison; For the selected troubleshooting / repair scheme that meets the requirements, calculate the probability that the aircraft configuration will complete the mission objective according to the matched alternative mission configuration scheme. The calculation process needs to take into account the damage events that may occur during the mission.

[0011] Optional, assess the support resources required for aircraft launch, including: Based on the aircraft configuration status and alternative mission configuration combinations obtained from the selected troubleshooting / repair scheme after matching analysis, assess the support requirements required to perform the mission objectives with this combination; Determine the revision requirements for aircraft flight operation procedures; Based on the support requirements, determine the maintenance work required before and after aircraft takeoff; Based on the scope of maintenance work, determine the requirements for facilities, equipment, tools, spare parts, consumables, personnel, and time.

[0012] Optionally, make a decision on whether to release the aircraft and develop a release implementation plan, including: Based on the existing support conditions, determine the aircraft configuration status and alternative mission configuration combinations under the practically feasible troubleshooting / repair schemes; Select the unique combination that meets the expectations from the above combinations based on the probability of task completion; Based on the above combination, formulate a flight release plan, clarifying the division of labor, steps, and time requirements; The maintenance work required before and after aircraft launch; Implement revisions to aircraft flight operation procedures.

[0013] Optionally, after S7, the method further includes: By executing the launch plan, the actual time spent on each item in the plan is obtained, forming a time database. This database is used to improve the accuracy of assessing the support resources required for aircraft launch and to develop launch implementation plans. Collect information on actual malfunctions during mission execution and assess the actual capabilities of aircraft, then update the capability database. Collect crew members' evaluations and suggestions on flight operation procedures during mission execution, and improve the requirements for correcting flight operation procedures in the event of malfunctions or combat damage.

[0014] A second aspect of the present invention also provides an aircraft launch decision system based on mission objectives, comprising: Aircraft configuration and capability database, used to store aircraft configurations and performance; The aircraft capability assessment subsystem is used to assess the actual capabilities of an aircraft based on its actual configuration status. The mission objective decomposition subsystem is used to determine the alternative aircraft mission configuration states and the corresponding mission objective decomposition schemes. The capability and mission objective matching analysis subsystem is used to analyze the matching of the implementation schemes for decomposing aircraft capabilities and mission objectives; The flight support assessment subsystem is used to assess the support requirements for aircraft flight. The flight decision-making subsystem is used to make flight decisions and formulate flight operation plans; The data update subsystem is used to collect and analyze data generated during launch-related support and mission execution, and to optimize decision-making methods and systems.

[0015] This invention provides a method and system for aircraft launch decision-making based on mission objectives. Considering the inherent uncertainty of mission objectives and the tight time requirements for aircraft launch, coupled with the unplanned and temporary relocation of aircraft to multiple bases, relying solely on manual decision-making based on paper manuals is time-consuming and lacks accuracy and scientific rigor. This invention transforms the aircraft's design documents, using the probability of achieving mission objectives as a guide, clearly defining the boundaries of aircraft configuration components and immediate support, significantly shortening decision-making time, deeply exploring the aircraft's capability potential, and making the decision-making process scientific and efficient, effectively supporting the completion of mission objectives. Detailed Implementation

[0016] The present invention will be further described in detail below with reference to specific embodiments.

[0017] This invention provides an aircraft launch decision method based on mission objectives, comprising: S100, Construct the aircraft configuration state tree and aircraft capability tree; S200, construct a fault database and a combat damage database, and revise the aircraft capability tree; S300: Enumerate possible fault and damage states of the aircraft and establish an aircraft capability status database; S400: Decompose mission objectives to obtain the minimum capability requirements required to perform mission objectives under each aircraft mission configuration; S500, analysis of the matching between aircraft capabilities and mission objectives; S600, assess the support resources required for aircraft launch; S700, make a decision on flight and formulate a flight implementation plan; The S800 collects and analyzes data generated during launch support and execution to optimize decision-making methods and systems.

[0018] Specifically, step S100 includes: Step S101: Based on the decomposition of the aircraft product structure, a structured aircraft configuration state tree is established using the standard numbering system, consisting of four levels: aircraft, system, subsystem, sub-subsystem, and component. Step S102: Based on the aircraft configuration state tree, construct the aircraft capability tree. Each node of the capability tree corresponds one-to-one with the relevant node in the configuration state tree, including aircraft capability index items, system capability index items, subsystem capability index items, sub-subsystem capability index items, and component capability index items, which are used to characterize specific functions. For example, typical aircraft capability index items include the aircraft's maximum range, maximum takeoff weight, and maximum flight altitude, while typical component capabilities include the maximum output force of the hydraulic booster, the system's rated working pressure, and the rocker arm control force. Step S103: Establish the calculation method of the capability index value corresponding to each level of capability index item through the working principle, design data and logical relationship of each system of the aircraft, obtain the component capability index value in the aircraft capability tree under normal conditions, and then calculate the capability index value of sub-system, sub-system, system and aircraft level by level. For example, the maximum usable volume of the cargo hold can be calculated by the size of each floor and wall panel of the cargo hold. In one implementation, the aircraft product structure decomposition in step S101 adopts the standard numbering system provided by the S1000D standard, uses the type identification code to distinguish different aircraft models, and uses the system difference code to distinguish the configuration differences between aircraft of the same model, thereby constructing a configuration state tree applicable to different models and different flights of aircraft.

[0019] In one implementation, step S101 stores the normal configuration state of the selected aircraft model under fault-free and damage-free conditions in the configuration state tree. The configuration state is stored in a structured manner using XML, and is stored in order of equipment, subsystem, subsystem, system, and whole aircraft. The storage reflects the relationships such as combination, mutual exclusion, and dependency between configuration states.

[0020] In one implementation, the capability tree in step S102 adopts a hierarchical structure. The capability indicators at the bottom level are independent of each other and are combined step by step through the mapping relationship of the configuration state tree to form higher-level capability indicators. Each top-level capability indicator represents the capability of an aircraft in a certain field, such as payload, navigation accuracy, and reconnaissance range.

[0021] Specifically, step S200 includes: Step S201: Construct a failure database through failure mode and effects analysis, and record failure mode analysis data, including failure causes, failure rate impact on related systems / components, failure impact, correction requirements for flight operations, troubleshooting solutions, etc. There can be multiple troubleshooting solutions, denoted as troubleshooting solution x. Step S202: Associate all failure mode analysis data in the failure database with the relevant components, subsystems, systems, and aircraft in the configuration state tree, and then associate them with the aircraft capability tree. For any failure mode, under all possible conditions such as no troubleshooting after occurrence, troubleshooting plan 1 after occurrence, troubleshooting plan 2 after occurrence, and troubleshooting plan 3 after occurrence, the component capability index values ​​are corrected respectively, and the calculation methods of subsystems, subsystems, systems, and aircraft capability index values ​​are corrected. The influencing factors of failure modes are introduced to form a new calculation method for capability index values, including the correction of relevant failure rates. Step S203: Construct a damage database through damage assessment and repair analysis, and record damage assessment and repair analysis data, including damage type, impact on failure rate of related systems / components, damage impact, correction requirements for flight operations, repair schemes, etc. There can be multiple repair schemes, denoted as repair scheme x. Step S204: Associate all damage assessment and repair analysis data in the combat damage database with relevant components, subsystems, and systems in the configuration state tree, and then associate them with the aircraft capability tree. For any damage, under all possible scenarios such as no repair after occurrence, repair plan 1 after occurrence, repair plan 2 after occurrence, and repair plan 3 after occurrence, the component capability index values ​​are corrected respectively. The calculation methods of subsystem, subsystem, system, and aircraft capability index values ​​are corrected. The influencing factors of damage are introduced to form a new calculation method for capability index values, including the correction of relevant failure rates.

[0022] It should be noted that the failure mode described in step S202 may have more than one troubleshooting solution. The impact of each troubleshooting solution on the aircraft's capabilities may be different. The failure mode and any troubleshooting solution should be combined as a whole for subsequent analysis.

[0023] It should be noted that the damage described in step S204 may have more than one repair option, and the impact of each repair option on the aircraft's capabilities may be different. The damage and any repair option should be combined as a whole for subsequent analysis.

[0024] It should be noted that when modifying the aircraft capability tree in steps S202 and S204, the correlation between failure modes and damage can be considered based on the aircraft's design principles.

[0025] Specifically, step S300 includes: Step S301: Obtain the aircraft model from step S101, and denote the first aircraft model as φ1, the second aircraft model as φ2, and so on, denote the xth aircraft model as φx.

[0026] Step S302: Obtain the actual aircraft corresponding to the xth aircraft type from step S101. The first aircraft is denoted as φxλ1, the second aircraft is denoted as φxλ2, and so on. The yth aircraft of the xth aircraft type is denoted as φxλy, and the normal configuration state corresponding to aircraft φxλy is denoted as φxλyc-0. Step S303: For aircraft φxλy, select all possible fault modes from step S201. The fault mode is denoted as Fn, where n is a natural number. The configuration state of aircraft φxλy when no troubleshooting is performed after fault mode Fn occurs is denoted as φxλyc-Fn0. The configuration state when troubleshooting scheme 1 is implemented after fault mode Fn occurs is denoted as φxλyc-Fn1. The configuration state when troubleshooting scheme 2 is implemented after fault mode Fn occurs is denoted as φxλyc-Fn2, and so on. The configuration state when troubleshooting scheme z is implemented after fault mode Fn occurs is denoted as φxλyc-Fnz. Step S304: For aircraft φxλy, select all possible damages from step S203, and denot the damage as Dm, where m is a natural number. The configuration state of aircraft φxλy without troubleshooting after damage Dm occurs is denoted as φxλyc-Dm0. The configuration state when troubleshooting scheme 1 is implemented after damage Dm occurs is denoted as φxλyc-Dm1. The configuration state when troubleshooting scheme 2 is implemented after damage Dm occurs is denoted as φxλyc-Dm2, and so on. The configuration state when troubleshooting scheme w is implemented after damage Dm occurs is denoted as φxλyc-Dmw. Step S305: Form a non-empty set A for the aircraft φxλyc-0, all φxλyc-Fnz, and all φxλyc-Dmw. Create multiple non-empty subsets Bi for set A, where i is a natural number. Bi records the possible actual configuration states of the aircraft φxλy. For example, B5 can be {φxλyc-F22, φxλyc-F30, φxλyc-D33}, indicating that the aircraft φxλy has experienced fault mode F2, fault mode F3, and damage D3. Troubleshooting plan 2 was implemented for fault mode F2, no troubleshooting plan was implemented for fault mode F3, and repair plan 3 was implemented for fault mode D3. For example, B0 can be {φxλyc-0}, indicating that the aircraft φxλy has not experienced any fault mode or battlefield damage. Step S306: For the configuration states recorded in set Bi, the capability index values ​​are calculated sequentially by unit, sub-system, subsystem, system, and aircraft using the aircraft capability tree modified in steps S202 and S204. Step S307: For all sets Bi, execute step S305 in sequence to obtain the capability index values ​​of each aircraft φxλy in the capability tree when all possible actual configuration states occur, and form the capability state library of aircraft φxλy. Perform operations on all aircraft φxλy in step S301 in sequence to form the capability state library of aircraft. It should be noted that when calculating the capability index value in step S305, the limitations of support conditions and resources are not taken into account. For example, support resources such as aviation fuel, bombs, tools, facilities, and personnel are considered to fully meet the requirements.

[0027] Specifically, step S400 includes: Step S401: For the aircraft φxλy and its corresponding normal configuration state φxλyc-0 in step S302, the mission objective is decomposed into profile mission objective and non-profile mission objective based on whether it is related to the flight profile of the mission performed by the aircraft. Step S402: For the profile mission objective, decompose it into sub-mission objectives for different flight phases of the aircraft. The decomposition process needs to consider the geographical and environmental characteristics of the aircraft takeoff, outbound flight, operation in the target scenario, return flight and landing. Step S403: For non-profile mission objectives, classify them into mission types such as reconnaissance, transportation, ground attack, and medical rescue according to the category of the mission being performed. Further decompose different mission types. For example, for the reconnaissance mission type, further decompose it into sub-mission objectives such as reconnaissance duration, reconnaissance range, and reconnaissance accuracy. Step S404: Select sub-task objectives in sequence. In step S102, check whether there is a corresponding whole-aircraft level capability indicator item in the capability indicator set of configuration state φxλyc-0. If it exists, calculate the capability indicator value corresponding to the sub-task objective. This value is the minimum capability indicator value proposed by the sub-task objective for the aircraft φxλy. If it does not exist, further decompose the sub-task objective to form a secondary-level task objective. Step S405: Select the next level mission objective and perform the operation step by step using the method in step S404 until a mission objective capability index tree is formed. Each capability index item on the tree corresponds one-to-one with the aircraft-level capability index items in the capability index set in step S102. The capability index values ​​on the mission objective tree constitute the minimum set of capability index values ​​required for the aircraft φxλy to complete the mission objective in the configuration state φxλyc-0. Step S406: For all aircraft φxλy from step S302, execute steps S302, S303, and S304 to obtain a set of minimum capability index values ​​required for each aircraft to perform its mission objectives.

[0028] Specifically, step S500 includes: In step S501, for the aircraft φxλy that has actually experienced n failure modes and m damages in step S301 and has not implemented any troubleshooting or repair plans, in step S304, subsets R0 and Ri are screened out from all subsets of set A, where i is a natural number. Subset R0 indicates that no troubleshooting or repair plans have been implemented for aircraft φxλy. Any element in subset Ri is related to all n failure modes and m damages that actually occurred in aircraft φxλy. Subsets R0 and Ri represent the configuration state of aircraft φxλy to be evaluated. Step S502: Starting from subset R0, select subset Ri in order of implementing troubleshooting solutions from few to many and implementing repair solutions from few to many. Obtain the corresponding aircraft capability item values ​​from the aircraft capability tree in the aircraft capability status database in step S306. Compare the obtained aircraft capability item values ​​with the minimum capability index values ​​required for aircraft φxλy to perform mission objectives in step S404 item by item. Step S503: For each configuration state to be evaluated in which all aircraft capability values ​​in step S502 are greater than the minimum capability index value required to perform the mission objective, evaluate whether the probability of completing the mission objective is greater than the expected probability of the mission objective. The evaluation needs to take into account any additional damage events that may occur during the mission. Step S504: For each aircraft that actually experienced multiple failure modes and multiple damages in step S301 and for which no troubleshooting or repair plans were implemented, the above comparison is performed one by one to obtain the configuration status of each aircraft whose probability of completing the mission objective is greater than the expected probability of the mission objective.

[0029] In one implementation, step S503 can involve obtaining the expected probability of completing the task from the command system for automatic decision-making, or a human-computer interaction interface can be provided for manual decision-making by personnel with decision-making authority.

[0030] It should be noted that the influencing factors and calculation methods of the task completion probability in step S503 should be determined according to the needs of the emergency response agency and the type of task.

[0031] Specifically, step S600 includes: Step S601: For each aircraft configuration state obtained in step S504, evaluate the support requirements required to perform the mission objective in the selected configuration state. Step S602: For each aircraft configuration state obtained in step S504, evaluate the aircraft flight operation procedure modification requirements required to perform the mission objective in the selected configuration state. Step S603: Based on the support requirements corresponding to each aircraft configuration state in step S601, determine the maintenance work required before and after the aircraft is launched. Step S604: Based on the maintenance work content corresponding to each aircraft configuration status in step S603, determine the support requirements for facilities, equipment, tools, spare parts, consumables, personnel, and time.

[0032] In one implementation, the support requirements in step S601 include requirements for routine pre-flight checks, pre-flight configuration conversion, implementation of troubleshooting plans, implementation of repair plans, and preparations for return to base after flight. These support requirements can be managed using a maintenance support information system.

[0033] In one implementation, in step S602, the modification requirements for the aircraft flight operation procedures refer to the adjustment targets of the flight operation procedures based on the fault mode and damage conditions, including the requirements for the number and skills of the crew, and the superimposed impact on the operation procedures when multiple faults or damages exist simultaneously should be considered.

[0034] In one implementation, the maintenance work in step S603 exists as separate maintenance procedures, which may involve: Please provide logistical support for tasks such as filling, adding, and attaching items required for mission execution. Routine pre-flight checks; Post-mission support preparations; Isolation / shielding of faulty equipment and redistribution of functions; Temporary repair of damage.

[0035] In one implementation, step S604 involves extracting and integrating information from the structured maintenance procedure in step S603 to obtain the requirements for support facilities, equipment, tools, spare parts, consumables, personnel, and time, with the support requirements provided in numerical form.

[0036] Specifically, step S700 includes: Step S701: Compare the existing support conditions with the support requirements corresponding to each aircraft configuration state in step S604, and select the optimal aircraft configuration state that requires the least support resources and has the highest probability of completing the mission objective. Step S702: Based on the optimal aircraft configuration selected in step S701, formulate a flight launch plan, clarifying the division of labor, step breakdown, and time requirements. Step S703: According to the flight launch work plan in step S702, the maintenance and support personnel shall carry out the maintenance work required before and after the aircraft launch according to their division of labor, implement troubleshooting and repair plans as needed, and record the work process. Step S704: Modify the aircraft flight operation procedure for the aircraft configuration state selected in step S702.

[0037] In one implementation, step S703 involves the maintenance work content specified in the technical publication under normal configuration, as well as the maintenance work content introduced by the implementation of troubleshooting and repair plans. The maintenance work content of the two is integrated, support resources including maintenance personnel are prepared, and the maintenance work content is refined into executable steps, clarifying the process and time.

[0038] In one implementation, step S704 involves refining the flight operation procedures based on the faults and damages in the combination, ensuring that the workload of the flight crew is adjusted to the minimum extent possible under the premise of ensuring safety in the event of faults and damages.

[0039] Specifically, step S800 includes: Step S801: By executing the flight launch work plan, the actual time spent on each item in the work plan is obtained to form a time consumption database, which is used to improve the accuracy of the assessment of the support resources required for aircraft flight launch, and is also used to formulate flight launch implementation plans. Step S802: Collect information on the actual occurrence of faults during mission execution and assess the actual capabilities of the aircraft; update the aircraft capability tree, fault database, and combat damage database. Step S803: Collect the crew members' evaluations and suggestions on the flight operation procedures during the mission, and improve the correction requirements for the flight operation procedures in the event of fault modes and damage.

[0040] In one implementation, step S801 uses XML elements to describe a structured maintenance procedure, and the time taken to implement the maintenance procedure is recorded in the XML elements of the maintenance procedure.

[0041] In one implementation, step S802 establishes an automatic update mechanism for fault mode and impact analysis data. In response to new understandings of fault modes generated during aircraft use, incremental packages of fault mode and impact analysis data are provided. The data structure of the incremental packages conforms to the requirements of the fault database to avoid re-analyzing the unchanged parts of the fault mode and impact analysis data.

[0042] In one implementation, step S802 can be performed by simulating and practically verifying the modification requirements of the flight operation procedure through a simulation and exercise system.

[0043] This embodiment also provides an aircraft launch decision system based on mission objectives, which may include the following components: Aircraft configuration tree and capability data tree 100 are used to store aircraft configuration status and performance indicators; The Fault Database and Battle Damage Database 200 are used to record Fault Mode and Effects Analysis data, Damage Assessment and Repair Analysis data, and provide corrections to the aircraft capability tree. Aircraft Capability Status Library 300 is used to enumerate possible fault and damage states of aircraft and establish the capability status of aircraft under different fault modes and battlefield damage. The mission objective decomposition subsystem 400 is used to decompose mission objectives and obtain the minimum capability requirements required to perform mission objectives under normal aircraft configurations. The Aircraft Capability and Mission Objective Matching Analysis Subsystem 500 is used to analyze the matching between aircraft capabilities and mission objectives. The Flight Support Assessment Subsystem 600 is used to assess the support requirements for aircraft launch. The 700-level flight decision-making subsystem is used to make flight decisions and formulate flight operation plans. The data update subsystem 800 is used to collect and analyze data generated during launch-related support and mission execution, and to optimize decision-making methods and systems.

[0044] The implementation method of the mission objective-based aircraft launch decision system in this embodiment can be found in the working principle of the aforementioned mission objective-based aircraft launch decision method, and will not be repeated here.

[0045] For ease of description, the above methods or systems are described separately as various steps or modules based on their functions. Of course, in implementing this application, the functions of each step or module can be implemented in one or more software and / or hardware.

[0046] The above description discloses only one preferred embodiment of the present invention, and should not be construed as limiting the scope of the present invention. Those skilled in the art will understand that all or part of the processes of the above embodiments can be implemented, and equivalent changes made in accordance with the claims of the present invention are still within the scope of the invention.

Claims

1. A method for aircraft launch decision based on mission objectives, characterized in that, include: S1. Construct the aircraft configuration state tree and the aircraft capability tree; S2. Construct a fault database and a damage database, and revise the aircraft capability tree; S3. Enumerate the possible fault and damage states of the aircraft and establish an aircraft capability status database. S4. Decompose the mission objectives and obtain the minimum capability requirements required to perform the mission objectives under each aircraft mission configuration; S5. Conduct aircraft capability and mission objective matching analysis; S6. Assess the support resources required for aircraft launch; S7. Make a decision on the release and formulate a release implementation plan.

2. The aircraft launch decision method based on mission objectives according to claim 1, characterized in that, The aircraft configuration state tree is established by decomposing the aircraft product structure and using a standard numbering system; the aircraft configuration state tree includes: aircraft, system, subsystem, sub-subsystem and component levels.

3. The aircraft launch decision method based on mission objectives according to claim 1, characterized in that, Each node in the aircraft capability tree corresponds one-to-one with the relevant node in the configuration state tree. The aircraft capability tree includes aircraft capability indicators, system capability indicators, subsystem capability indicators, sub-subsystem capability indicators, and component capability indicators.

4. The aircraft launch decision method based on mission objectives according to claim 1, characterized in that, The fault database records fault mode analysis data, including: fault causes, impact on the failure rate of related systems / components, fault effects, corrective requirements for flight operations, and troubleshooting solutions; The battlefield damage database records battlefield damage assessment and repair analysis data, including: battlefield damage type, impact on the failure rate of related systems / components, damage impact, correction requirements for flight operations, and troubleshooting solutions.

5. The aircraft launch decision method based on mission objectives according to claim 1, characterized in that, Decompose the mission objectives to obtain the minimum capability requirements needed to execute the mission objectives under each aircraft mission configuration, including: For the mission objectives, and based on the selected type of aircraft, propose multiple alternative mission configuration schemes under normal aircraft conditions; For each alternative mission configuration, distinguish between the capability requirements related to the mission profile and other capability requirements; For the capability requirements related to the mission profile, the mission objectives are decomposed into sub-mission objectives for different flight / mission phases of the aircraft according to the mission profile, and capability indicators corresponding to each sub-mission objective are proposed according to the capability indicator set. For other capability requirements, capability indicators corresponding to the objectives of each sub-task are proposed according to the set of capability indicators; The above capability indicators are the minimum requirements for an aircraft to accomplish its mission objectives.

6. The aircraft launch decision method based on mission objectives according to claim 1, characterized in that, Conduct aircraft capability and mission objective matching analysis, including: Select projects from the set of failure modes and battlefield damage under different troubleshooting / repair schemes, extract the capability indicators corresponding to each project, and extract the mission capability requirements corresponding to each alternative mission configuration scheme. For each selected project, the aircraft capability indicators are compared one by one to see if they meet the mission capability requirements of each alternative mission configuration. Retrieve each item from the set one by one and perform the above comparison; For the selected troubleshooting / repair scheme that meets the requirements, calculate the probability that the aircraft configuration will complete the mission objective according to the matched alternative mission configuration scheme. The calculation process needs to take into account the damage events that may occur during the mission.

7. The aircraft launch decision method based on mission objectives according to claim 6, characterized in that, Assess the support resources required for aircraft launch, including: Based on the aircraft configuration status and alternative mission configuration combinations obtained from the selected troubleshooting / repair scheme after matching analysis, assess the support requirements required to perform the mission objectives with this combination; Determine the revision requirements for aircraft flight operation procedures; Based on the support requirements, determine the maintenance work required before and after aircraft takeoff; Based on the scope of maintenance work, determine the requirements for facilities, equipment, tools, spare parts, consumables, personnel, and time.

8. The aircraft launch decision method based on mission objectives according to claim 7, characterized in that, Make a decision to release the aircraft and formulate a release implementation plan, including: Based on the existing support conditions, determine the aircraft configuration status and alternative mission configuration combinations under the practically feasible troubleshooting / repair schemes; Select the unique combination that meets the expectations from the above combinations based on the probability of task completion; Based on the above combination, formulate a flight release plan, clarifying the division of labor, steps, and time requirements; The maintenance work required before and after aircraft launch; Implement revisions to aircraft flight operation procedures.

9. The aircraft launch decision method based on mission objectives according to claim 1, characterized in that, Following S7, the method further includes: By executing the launch plan, the actual time spent on each item in the plan is obtained, forming a time database. This database is used to improve the accuracy of assessing the support resources required for aircraft launch and to develop launch implementation plans. Collect information on actual malfunctions during mission execution and assess the actual capabilities of aircraft, then update the capability database. Collect crew members' evaluations and suggestions on flight operation procedures during mission execution, and improve the requirements for correcting flight operation procedures in the event of malfunctions or combat damage.

10. An aircraft launch decision system based on mission objectives, characterized in that, include: Aircraft configuration and capability database, used to store aircraft configurations and performance; The aircraft capability assessment subsystem is used to assess the actual capabilities of an aircraft based on its actual configuration status. The mission objective decomposition subsystem is used to determine the alternative aircraft mission configuration states and the corresponding mission objective decomposition schemes. The capability and mission objective matching analysis subsystem is used to analyze the matching of the implementation schemes for decomposing aircraft capabilities and mission objectives; The flight support assessment subsystem is used to assess the support requirements for aircraft flight. The flight decision-making subsystem is used to make flight decisions and formulate flight operation plans; The data update subsystem is used to collect and analyze data generated during launch-related support and mission execution, and to optimize decision-making methods and systems.