A demand matrix based automated distribution system and method for aircraft power distribution system test confirmation
The automated allocation system based on the demand matrix solves the problems of inconsistency and inefficiency in manual judgment in the airworthiness certification of civil aircraft power distribution systems, and achieves efficient and standardized test verification, meeting the requirements of auditability and data reuse in airworthiness review.
Patent Information
- Authority / Receiving Office
- CN · China
- Patent Type
- Applications(China)
- Current Assignee / Owner
- SHANGHAI CIVIL AVIATION POWER SYSTEM CO LTD
- Filing Date
- 2026-05-08
- Publication Date
- 2026-06-05
AI Technical Summary
In the airworthiness certification of civil aircraft power distribution systems, the testing and verification methods in the requirements confirmation phase rely on manual methods, which suffer from problems such as inconsistent subjective judgments, low efficiency, poor traceability, and non-reusability of data, and cannot meet the compliance and auditability requirements of airworthiness review.
An automated allocation system based on a demand matrix is adopted. Through a demand matrix construction module, a test verification demand identification module, and an airworthiness result output module, the system embeds the ARP4754B judgment rule base to automatically identify and allocate system-level or equipment-level test verifications, generate standardized reports, and support data reuse and version management.
It has achieved automation, standardization, and auditability of requirements verification, improved efficiency, ensured full coverage and consistency of test verification, reduced project iteration and maintenance costs, and met the auditability requirements of airworthiness review.
Smart Images
Figure CN122155755A_ABST
Abstract
Description
Technical Field
[0001] This application relates to the field of avionics technology, and in particular to an automated distribution system and method for testing and validating aircraft power distribution systems based on a demand matrix. Background Technology
[0002] The airworthiness certification process for civil aircraft power distribution systems involves both requirements confirmation and design verification. The Civil Aircraft and Systems Development Guideline ARP 4754B is the core definition of civil aircraft airworthiness standards and strictly distinguishes between requirements confirmation and requirements verification; the two are not to be confused or substituted for each other. Requirements confirmation primarily focuses on the requirements themselves, proving that the system or subsystem requirements meet user expectations, usage scenarios, and airworthiness requirements; it is a compliance proof of the correctness of the requirements. Requirements verification, on the other hand, focuses on design implementation, proving that the product design, hardware, or software meets the requirements specifications; it is an implementation proof of design conformity.
[0003] Understandably, for airworthiness certification of civil aircraft power distribution systems, requirements verification must be completed before design verification can proceed. For some requirements, verification can be achieved through testing. When testing is required, it can be performed at the system level or the equipment level. Furthermore, accurately allocating system-level or equipment-level testing to requirements directly determines the compliance and success rate of the airworthiness review.
[0004] The current method for confirming the requirements of civil aircraft power distribution systems relies entirely on manual labor, which poses a serious risk to airworthiness compliance. Specifically, (1) subjective judgment, which fails to meet airworthiness requirements. There are no standardized judgment rules, and engineers classify the test confirmation types based on experience. Different judgment results are likely to occur for the same requirement, which cannot meet the mandatory requirements of ARP4754B for consistency and reproducibility of confirmation. (2) extremely low manual efficiency and lengthy confirmation cycle. There are hundreds of requirements for power distribution systems. The workload of manually analyzing and marking the test confirmation types for each item is extremely large, and the confirmation cycle can last for several days, which seriously restricts the project progress. (3) lack of traceability and high risk of airworthiness audit. The requirement-test confirmation relationship sorted out manually is unstructured data with no complete traceability, which cannot meet the core procedures of auditability and traceability for airworthiness review. (4) data cannot be reused and maintenance costs are high. Model iteration and project reuse require repetitive work, which greatly increases management costs. Summary of the Invention
[0005] This application provides an automated allocation system and method for testing and verifying aircraft power distribution systems based on a demand matrix, which addresses issues such as ambiguity in the selection of testing and verification methods during the demand verification phase of civil aircraft airworthiness review, inefficiency of manual division, failure to meet auditability standards, and inability to reuse data.
[0006] Firstly, this application provides an automated allocation system for the test verification of an aircraft power distribution system based on a demand matrix. This system is applied to the requirements verification phase corresponding to the civil aircraft and system development guideline ARP4754B. The system includes a requirements matrix construction module, a test verification requirements identification module, a test verification hierarchy allocation module, and an airworthiness result output module. The demand matrix construction module is used to import the full demand of the power distribution system of civil aircraft and generate a demand matrix of the full demand of the power distribution system. The dimensions of the demand matrix include: demand number, demand content, module affiliation, demand type, number of devices involved in the demand, whether it involves system-level performance, whether it involves electronic communication interfaces, and whether the system and devices are bidirectionally traceable. The test confirmation requirement identification module is used to match the requirement matrix with the built-in confirmation test rule library, and respectively filter out the test confirmation items that need to be tested and confirmed and the test confirmation items that do not need to be tested and confirmed in the full requirements of the power distribution system. The test verification level allocation module is used to automatically assign the corresponding test verification level type to the test verification item according to the preset test verification level allocation rules when the requirement is a test verification item. The test verification level types include system-level test verification and equipment-level test verification. The airworthiness results output module is used to generate standardized test confirmation allocation reports, supporting multi-format export, visualization, and statistical analysis to meet airworthiness audit requirements.
[0007] Understandably, by using the aircraft power distribution system demand matrix as the core structured carrier and embedding the ARP4754B compliance judgment rule library, the system first automatically identifies the requirements that need to be tested and confirmed, and then accurately allocates system-level or equipment-level test confirmations according to the scope and functional complexity of the requirements. Finally, it generates an airworthiness standardization test confirmation allocation report, realizing full automation, standardization and auditability of the requirement confirmation process.
[0008] Understandably, this automated allocation system for aircraft power distribution system test verification based on a demand matrix can replace manual judgment, automatically matching the type of test verification required (including whether test verification is not required, system-level test verification, or equipment-level test verification), thereby significantly improving the efficiency of requirement verification. Furthermore, by establishing a corresponding airworthiness compliance judgment rule base (i.e., a verification test rule base) and test verification hierarchy allocation rules, it eliminates subjective human bias, ensuring full coverage, consistency, and accuracy of test verification. The generated standardized test verification allocation report supports structured storage and end-to-end traceability, thus meeting the auditability requirements of airworthiness reviews. In addition, the generated demand matrix also supports data reuse and version management, reducing the iteration and maintenance costs of civil aircraft projects and adapting to the requirement verification of power distribution systems for multiple models.
[0009] In one possible implementation of the first aspect mentioned above, the dimensions of the requirement matrix include: requirement number, requirement content, module affiliation, requirement type, number of devices involved in the requirement, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable. Module affiliation includes: primary power distribution, secondary power distribution, power conversion, and storage batteries. Requirement type includes: function, four properties, environment, interface, and design constraints. The four properties include reliability, maintainability, supportability, and testability.
[0010] In one possible implementation of the first aspect above, a demand matrix for the total demand of the power distribution system is generated, including: The total demand of the power distribution system is divided according to the dimensions of the demand matrix, and the results are mapped to obtain the demand matrix.
[0011] In one possible implementation of the first aspect above, the test verification item satisfies at least one test verification rule in the verification test rule base, and the test verification rule includes the following rule items: Meeting demand involves power supply safety; The requirements involve load management or fault refactoring; The requirement involves the linkage of multiple devices; The requirements involve system performance.
[0012] In one possible implementation of the first aspect above, when the requirement is a test-confirmation item, the test-confirmation item is automatically assigned a corresponding test-confirmation level type according to a preset test-confirmation level allocation rule, including: When the requirement is a test-confirmation item, a weighted score is applied based on the key parameters corresponding to the test-confirmation item in the requirement matrix. The corresponding test confirmation level is automatically assigned according to the scoring results. The key parameters include the number of devices involved in the requirement, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable.
[0013] In one possible implementation of the first aspect above, a weighted score is applied based on the key parameters corresponding to the items requiring test verification in the demand matrix, and the type of the corresponding test verification level is automatically assigned according to the scoring results, including: Based on the satisfaction of the parameters corresponding to the key parameters, a system-level score is obtained by scoring according to the preset system-level test score formula; When the system-level score reaches the preset system-level threshold, the test verification level is determined to be system-level test verification; when the system-level score is less than the preset system-level threshold, the test verification level is determined to be equipment-level test verification. The system-level test score formula is as follows: System-level score = w1*S1 + w2*S2 + w3*S3 + w4*S4; Where w1, w2, w3, and w4 are preset weights; S1 is used to represent the number of devices allocated. When the parameter value of the number of devices allocated is greater than or equal to 2, the value of S1 is 1, and when the parameter value of the number of devices allocated is equal to 1, the value of S1 is 0. S2 is used to indicate whether an electronic communication interface is involved. When the parameter value indicating whether an electronic communication interface is involved is yes, the value of S2 is 1; when the parameter value indicating whether an electronic communication interface is involved is no, the value of S2 is 0. S3 is used to indicate whether system-level performance is involved. When the parameter value indicates yes, the value of S3 is 1, and when the parameter value indicates no, the value of S3 is 0. S4 is used to indicate whether the system and equipment can be traced in both directions. When the parameter value indicates yes, the value of S4 is 1, and when the parameter value indicates no, the value of S4 is 0.
[0014] In one possible implementation of the first aspect above, the airworthiness result output module is also used to perform consistency verification on the allocation results of the total demand of the power distribution system to confirm that each demand in the total demand of the power distribution system has a corresponding allocation result.
[0015] In one possible implementation of the first aspect mentioned above, the validation test rule base and the test validation hierarchy allocation rules are constructed based on ARP4754B, FAA Advisory Circular FAA AC, and the Civil Aviation Administration Certification Guidelines.
[0016] In one possible implementation of the first aspect above, the test verification assignment report includes: requirement number, module affiliation, test verification type, and airworthiness test method recommendations, wherein the test verification type includes no test verification required, equipment-level test verification, and system-level test verification.
[0017] Secondly, this application provides an automated allocation method for test verification of aircraft power distribution systems based on a demand matrix, applied to the automated allocation system for test verification of aircraft power distribution systems based on a demand matrix as described in the first aspect and any one of the first aspects. The method includes: The demand matrix construction module imports the full demand of the power distribution system of civil aircraft and generates a demand matrix of the full demand of the power distribution system. The dimensions of the demand matrix include: demand number, demand content, module affiliation, demand type, number of devices involved in the demand, whether it involves system-level performance, whether it involves electronic communication interfaces, and whether the system and devices are bidirectionally traceable. The test confirmation requirement identification module matches the requirement matrix with the built-in confirmation test rule library, and respectively filters out the test confirmation items that need to be tested and the test confirmation items that do not ... When the requirement is a test confirmation item, the test confirmation level allocation module automatically assigns the corresponding test confirmation level type to the test confirmation item according to the preset test confirmation level allocation rules. The test confirmation level types include system-level test confirmation and equipment-level test confirmation. The airworthiness results output module generates standardized test confirmation allocation reports, supports multi-format export, visualization and statistical analysis, and meets airworthiness audit requirements; Specifically, when the requirement is a test-confirmation item, the test-confirmation item is automatically assigned the corresponding test-confirmation level type according to the preset test-confirmation level allocation rules, including: When a requirement is a test-and-confirmation item, a weighted score is applied based on the key parameters corresponding to the test-and-confirmation item in the requirement matrix. The corresponding test-and-confirmation level is then automatically assigned based on the scoring results. Key parameters include the number of devices involved in the requirements, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable.
[0018] The beneficial effects of the second aspect can be referred to the first aspect mentioned above, and will not be elaborated here. Attached Figure Description
[0019] To more clearly illustrate the technical solutions in this application or the prior art, the drawings used in the description of the embodiments or the prior art will be briefly introduced below. Obviously, the drawings described below are some embodiments of this application. For those skilled in the art, other drawings can be obtained based on these drawings without creative effort.
[0020] Figure 1 This application provides an automated allocation system for testing and verifying aircraft power distribution systems based on a demand matrix.
[0021] Figure 2 This application provides an automated allocation method for testing and verifying aircraft power distribution systems based on a demand matrix.
[0022] Figure 3 According to some embodiments of this application, a schematic diagram of the framework flow of an automated allocation method for test verification of an aircraft power distribution system based on a demand matrix is shown. Detailed Implementation
[0023] To make the objectives, technical solutions, and advantages of this application clearer, the technical solutions of this application will be clearly and completely described below with reference to the accompanying drawings. Obviously, the described embodiments are only some embodiments of this application, not all embodiments. Based on the embodiments of this application, all other embodiments obtained by those skilled in the art without creative effort are within the scope of protection of this application.
[0024] Figure 1 According to some embodiments of this application, an automated allocation system for test verification of aircraft power distribution systems based on a demand matrix is provided. This system is primarily applied to the requirements verification phase corresponding to Civil Aircraft and System Development Guideline ARP4754B. The system includes a requirements matrix construction module, a test verification requirements identification module, a test verification hierarchy allocation module, and an airworthiness result output module.
[0025] Understandably, the aircraft power distribution system test verification automated allocation system based on the demand matrix includes a demand matrix construction module, a test verification demand identification module, a test verification hierarchy allocation module, and an airworthiness result output module. It can realize the automated and standardized allocation of test verification methods during the demand verification phase. Furthermore, this system is mainly applied to the demand verification phase corresponding to the civil aircraft and system development guideline ARP4754B, thus meeting the stringent requirements of ARP4754B airworthiness review.
[0026] In some embodiments, the validation test rule base and test validation hierarchy allocation rules can be built based on ARP4754B, FAA Advisory Circulars (FAA AC), and CAAC certification guidelines. Understandably, all rules are derived from airworthiness standards and certification practices, not engineer experience. This facilitates quantifiable, reproducible, and auditable judgments. Furthermore, each requirement uniquely maps to a specific test type, allowing the system to automatically traverse the rules without omissions or mismatches. The rules can also be fixed and versioned, ensuring consistency across projects.
[0027] Specifically, the demand matrix construction module is used to import the full demand of the power distribution system of civil aircraft and generate a demand matrix of the full demand of the power distribution system.
[0028] The dimensions of the requirement matrix can include: requirement number, requirement content, module affiliation, requirement type, number of devices involved, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable. Module affiliation can be understood to include: primary power distribution, secondary power distribution, power conversion, and batteries. Requirement types can include: functionality, four properties (reliability, maintainability, supportability, and testability), environment, interfaces, and design constraints. For example, the four properties include reliability, maintainability, supportability, and testability.
[0029] The test confirmation requirement identification module is used to match the requirement matrix with the built-in confirmation test rule library to filter out the test confirmation items that need to be tested and the test confirmation items that do not ...
[0030] The test verification level allocation module is used to automatically assign the corresponding test verification level type to the test verification item according to the preset test verification level allocation rules when the requirement is a test verification item. The test verification level types include system-level test verification and equipment-level test verification. The airworthiness results output module is used to generate standardized test confirmation allocation reports, supporting multi-format export, visualization, and statistical analysis to meet airworthiness audit requirements.
[0031] For example, a test verification allocation report may include: requirement number, module affiliation, test verification type, and airworthiness test method recommendations. The test verification type includes no test verification required, equipment-level test verification, and system-level test verification. Multi-format export may support EXCEL / PDF export. Furthermore, the exported data is adapted for airworthiness review submissions, test planning, and resource allocation. For instance, during automatic allocation, the system can populate the "Test Verification Type" field according to rules, supporting manual review and adjustment.
[0032] In some embodiments, the test validation hierarchy allocation rules can be related to the scope and functional complexity of the requirements. Specifically, the test validation hierarchy allocation rules can be allocation rules corresponding to key parameters in the requirements matrix that are related to the scope and functional complexity of the requirements. For example, key parameters may include the number of devices involved in the requirement, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable.
[0033] Understandably, by using the aircraft power distribution system demand matrix as the core structured carrier and embedding the ARP4754B compliance judgment rule library, the system first automatically identifies the requirements that need to be tested and confirmed, and then accurately allocates system-level or equipment-level test confirmations according to the scope and functional complexity of the requirements. Finally, it generates an airworthiness standardization test confirmation allocation report, realizing full automation, standardization and auditability of the requirement confirmation process.
[0034] Understandably, this automated allocation system for aircraft power distribution system test verification based on a demand matrix can replace manual judgment, automatically matching the type of test verification required (including whether test verification is not required, system-level test verification, or equipment-level test verification), thereby significantly improving the efficiency of requirement verification. Furthermore, by establishing a corresponding airworthiness compliance judgment rule base (i.e., a verification test rule base) and test verification hierarchy allocation rules, it eliminates subjective human bias, ensuring full coverage, consistency, and accuracy of test verification. The generated standardized test verification allocation report supports structured storage and end-to-end traceability, thus meeting the auditability requirements of airworthiness reviews. In addition, the generated demand matrix also supports data reuse and version management, reducing the iteration and maintenance costs of civil aircraft projects and adapting to the requirement verification of power distribution systems for multiple models.
[0035] In some embodiments, for the demand matrix construction module, generating a demand matrix of the total demand of the power distribution system may specifically include: dividing the total demand of the power distribution system according to the dimensions of the demand matrix and mapping it according to the division results to obtain the demand matrix.
[0036] For example, requirements can be categorized into primary power distribution, secondary power distribution, power conversion, and batteries to determine their respective modules. Furthermore, they can be categorized according to function, four properties (performance, characteristics, environment, interface, and design constraints) to determine requirement types. Understandably, when certain requirements involve functionality, the specific experimental verification method may be related to the functional scope and complexity. In this case, further results can be obtained based on clearly defining the associated devices and input / output relationships of the requirements, such as the number of devices involved, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable. The number of devices involved in a requirement can indicate that the requirement involves multiple devices working collaboratively. For example, when the number of devices involved is greater than or equal to 2, it indicates that the requirement involves multiple devices working collaboratively (such as hard-wired interlocking of distribution panels and secondary power distribution communication). Whether a requirement involves system-level performance can be determined based on the overall system performance indicators corresponding to the requirement (such as load balancing, fault reconfiguration, and EMPC control). At this point, each requirement will have a mapping relationship with the dimensions of the requirement matrix, and the requirement matrix is obtained based on the mapping relationships corresponding to each requirement.
[0037] In some embodiments, for the test confirmation requirement identification module, the test confirmation item can satisfy at least one test rule in the confirmation test rule base. The test rule includes the following rule items: the requirement involves power supply safety; the requirement involves load management or fault reconstruction; the requirement involves multi-device linkage; the requirement involves system performance.
[0038] It is understandable that testing and verification of security, performance, and multi-device collaboration requirements are in accordance with the mandatory verification requirements of ARP4754B. For other requirements, such as single-device parameter calibration and documentation compliance requirements, only documentation verification is required, and testing and verification are not necessary.
[0039] In some embodiments, in the test confirmation level allocation module, when the requirement is a test confirmation item, the test confirmation item is automatically assigned the corresponding test confirmation level type based on the requirement matrix and according to the preset test confirmation level allocation rules. This may include: when the requirement is a test confirmation item, a weighted score is performed based on the key parameters corresponding to the test confirmation item in the requirement matrix, and the test confirmation level type is automatically assigned according to the score results. The key parameters include the number of devices involved in the requirement, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable.
[0040] Understandably, regarding the number of allocated devices, if only one device is allocated, it indicates that device-level testing and confirmation are required; if two or more devices are allocated, it indicates that system-level device testing is required. Regarding whether electronic communication interfaces are involved, if they are, it indicates that system-level testing and confirmation are required; otherwise, it indicates that device-level testing and confirmation are required. Regarding whether system-level performance is involved, if it is, it indicates that system-level testing and confirmation are required. Regarding whether the system and device are bidirectionally traceable, if not, it indicates that device-level testing and confirmation are required; if they are, it indicates that system-level testing and confirmation are required. Understandably, weights can be configured for key parameters. Based on historical experience of long-term manual system-level and device-level testing and confirmation of requirements, weights can be configured to assign weighted scores to the corresponding key parameters. Based on the scoring results, the corresponding testing and confirmation level type can be automatically assigned. This avoids the problem of ambiguous classifications when key parameters in a requirement meet both device-level and system-level testing and confirmation characteristics, thereby improving the accuracy of automatically assigning the corresponding testing and confirmation level type to the required testing and confirmation items.
[0041] Specifically, a weighted score is calculated based on the key parameters corresponding to the items requiring test verification in the demand matrix. The test verification level type is automatically assigned according to the scoring results. This can include: scoring the system-level score based on the parameter satisfaction status corresponding to the key parameters according to a preset system-level test score formula; when the system-level score reaches a preset system-level threshold, the test verification level type is determined to be system-level test verification; when the system-level score is less than the preset system-level threshold, the test verification level type is determined to be equipment-level test verification.
[0042] The following formula (1) shows a system-level test score formula: System-level score = w1*S1 + w2*S2 + w3*S3 + w4*S4 Formula (1); Wherein, w1, w2, w3, and w4 are preset weights; S1 represents the number of devices allocated; when the parameter value of the number of devices allocated is greater than or equal to 2, the value of S1 is 1; when the parameter value of the number of devices allocated is equal to 1, the value of S1 is 0; S2 represents whether an electronic communication interface is involved; when the parameter value of whether an electronic communication interface is involved is yes, the value of S2 is 1; when the parameter value of whether an electronic communication interface is involved is no, the value of S2 is 0; S3 represents whether system-level performance is involved; when the parameter value of whether system-level performance is involved is yes, the value of S3 is 1; when the parameter value of whether system-level performance is involved is no, the value of S3 is 0; S4 represents whether the system and devices can be traced bidirectionally; when the parameter value of whether the system and devices can be traced bidirectionally is yes, the value of S4 is 1; when the parameter value of whether the system and devices can be traced bidirectionally is no, the value of S4 is 0.
[0043] For example, the value of w1 can be 40, the value of w2 can be 30, the value of w3 can be 20, and the value of w4 can be 10. The preset system-level threshold is 60. When the system-level score is ≥60, a system-level test is assigned; when the system-level score is <60, a device-level test is assigned. It is understood that the selection of the example values of w1, w2, w3, and w4 is based on long-term human experience.
[0044] In some embodiments, the airworthiness result output module is further configured to perform consistency verification on the allocation results of all requirements of the power distribution system, to confirm that each requirement in the total requirements of the power distribution system has a corresponding allocation result. For example, for 1000 requirements, confirming that all 1000 requirements are allocated with corresponding requirement test types confirms that the requirements meet consistency. It is understandable that consistency verification verifies that no requirements are omitted and that there are no conflicts in test confirmation types, thus meeting the airworthiness integrity requirements.
[0045] It is understandable that the automated allocation system for aircraft power distribution system test verification based on the demand matrix provided in the embodiments of this application can achieve the following beneficial effects: (1) Significantly improved efficiency in demand verification: Automated allocation replaces manual work, completing hundreds of demand processing in 5 minutes, which is 99% more efficient than manual work and shortens the verification cycle; (2) 100% guarantee of airworthiness consistency: Unified rules eliminate subjective bias, demand verification coverage is 100%, with no omissions or mismatches, meeting the ARP4754B consistency requirements; (3) Fully compliant with auditability standards: Through structured matrix + full-link traceability, the core procedures of airworthiness review, which are traceable, reproducible, and auditable, can be met; (4) Precise matching of test verification: The system level focuses on multi-device collaboration, and the device level focuses on single-device parameters, making the verification more targeted; (5) Reduced cost through data reuse: Structured data supports model iteration and cross-project reuse, reducing the cost of civil aircraft R&D management.
[0046] Figure 2 According to some embodiments of this application, an automated allocation method for test verification of aircraft power distribution systems based on a demand matrix is shown. This method is applied to any of the aforementioned possible automated allocation systems for test verification of aircraft power distribution systems based on a demand matrix. The specific process is as follows: S201, the demand matrix construction module imports the full demand of the power distribution system of civil aircraft and generates a demand matrix of the full demand of the power distribution system.
[0047] For example, Figure 3 According to some embodiments of this application, a schematic flowchart of an automated allocation method for test verification of aircraft power distribution systems based on a demand matrix is shown. In step 1, demand matrix construction, the demand matrix construction module imports the full demand of the civil aircraft's power distribution system and generates a structured demand matrix.
[0048] S202, the test confirmation requirement identification module matches the requirement matrix with the built-in confirmation test rule library, and respectively filters out the test confirmation items that need to be tested and the test confirmation items that do not ... For example, Figure 3 In step 2, the automatic identification of test confirmation requirements is shown. The decision rule base (i.e., the test confirmation rule base) is loaded, and the requirement matrix is traversed according to the decision rule base to filter items requiring test confirmation. At this point, either items requiring test confirmation or items not requiring test confirmation can be obtained.
[0049] S203, When the requirement is a test confirmation item, the test confirmation level allocation module automatically assigns the corresponding test confirmation level type to the test confirmation item according to the preset test confirmation level allocation rules based on the requirement matrix. The test confirmation level types include system-level test confirmation and equipment-level test confirmation.
[0050] For example, Figure 3 In step 3, the automatic allocation of test verification levels is performed. Based on the preset test verification level allocation rules, it is determined whether each item requiring test verification has reached a preset system-level threshold. If it has, system-level test verification is allocated; otherwise, device-level test verification is allocated.
[0051] S204, the airworthiness results output module generates a standardized test confirmation allocation report, supports multi-format export, visualization and statistical analysis, and meets airworthiness audit requirements.
[0052] For example, Figure 3 In step 4, the results output and report generation process can be performed to verify the consistency of the allocation results, then an allocation report can be generated and exported using Excel or PDF.
[0053] Understandably, the test verification allocation report, unlike the traditional unstructured forms provided manually, can intuitively present the mapping relationship between requirements and test verification, and can serve as visual supporting material for airworthiness review.
[0054] It is understood that the various embodiments provided in this application are only applicable to the requirement confirmation stage in the airworthiness review of civil aircraft, and do not involve the requirement verification stage of design implementation. They are used to solve core problems in the requirement confirmation stage of civil aircraft airworthiness review, such as fuzzy selection of test methods, inefficient manual division, unacceptable auditability, and inability to reuse data.
[0055] The above embodiments are only used to illustrate the technical solutions of this application, and are not intended to limit them. Although this application has been described in detail with reference to the foregoing embodiments, those skilled in the art should understand that modifications can still be made to the technical solutions described in the foregoing embodiments, or equivalent substitutions can be made to some of the technical features. Such modifications or substitutions do not cause the essence of the corresponding technical solutions to deviate from the spirit and scope of the technical solutions of the embodiments of this application.
Claims
1. An automated allocation system for the test and verification of aircraft power distribution systems based on a demand matrix, applied to the requirements verification phase corresponding to Civil Aircraft and System Development Guideline ARP4754B, characterized in that, The system includes a requirement matrix construction module, a test verification requirement identification module, a test verification hierarchy allocation module, and an airworthiness result output module, wherein... The demand matrix construction module is used to import the full demand of the power distribution system of civil aircraft and generate a demand matrix of the full demand of the power distribution system. The test confirmation requirement identification module is used to match the requirement matrix with the built-in confirmation test rule library, and respectively filter out the test confirmation items that need to be tested and the test confirmation items that do not need to be tested and the test confirmation items that do not need to be tested and the test confirmation items in the full requirements of the power distribution system. The test confirmation level allocation module is used to automatically allocate the test confirmation level type to the test confirmation item according to the preset test confirmation level allocation rules when the requirement is the test confirmation item. The test confirmation level types include system-level test confirmation and equipment-level test confirmation. The airworthiness results output module is used to generate standardized test confirmation allocation reports, supporting multi-format export, visualization and statistical analysis to meet airworthiness audit requirements; Wherein, when the requirement is the item requiring test confirmation, automatically assigning the item requiring test confirmation to the corresponding test confirmation level type according to the preset test confirmation level allocation rule includes: When the requirement is the item requiring test confirmation, a weighted score is applied based on the key parameters corresponding to the item requiring test confirmation in the requirement matrix. The type corresponding to the test confirmation level is then automatically assigned based on the scoring results. The key parameters include the number of devices involved in the requirements, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable.
2. The system according to claim 1, characterized in that, The dimensions of the requirement matrix include: requirement number, requirement content, module affiliation, requirement type, number of devices involved in the requirement, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable. The module affiliation includes: primary power distribution, secondary power distribution, power conversion, and storage batteries. The requirement type includes: function, four properties, environment, interface, and design constraints. The four properties include reliability, maintainability, supportability, and testability.
3. The system according to claim 1, characterized in that, The process of generating the demand matrix for the full demand of the power distribution system includes: The total demand of the power distribution system is divided according to the dimensions of the demand matrix, and the division results are mapped to obtain the demand matrix.
4. The system according to claim 1, characterized in that, The test confirmation item satisfies at least one test confirmation rule in the confirmation test rule base, and the test confirmation rule includes the following rule items: Meeting demand involves power supply safety; The requirements involve load management or fault refactoring; The requirement involves the linkage of multiple devices; The requirements involve system performance.
5. The system according to claim 1, characterized in that, The process involves weighted scoring based on key parameters corresponding to the test confirmation items in the demand matrix, and automatic allocation of the test confirmation level type according to the scoring results, including: Based on the parameter satisfaction status corresponding to the key parameters, a system-level score is obtained by scoring according to the preset system-level test score formula; When the system-level score reaches a preset system-level threshold, the test confirmation level is determined to be the system-level test confirmation; when the system-level score is less than the preset system-level threshold, the test confirmation level is determined to be the device-level test confirmation. The system-level test score formula is as follows: System-level score = w1*S1 + w2*S2 + w3*S3 + w4*S4; Where w1, w2, w3, and w4 are preset weights; S1 is used to represent the number of devices allocated. When the parameter value of the number of devices allocated is greater than or equal to 2, the value of S1 is 1, and when the parameter value of the number of devices allocated is equal to 1, the value of S1 is 0. S2 is used to indicate whether an electronic communication interface is involved. When the parameter value indicating whether an electronic communication interface is involved is yes, the value of S2 is 1; when the parameter value indicating whether an electronic communication interface is involved is no, the value of S2 is 0. S3 is used to indicate whether system-level performance is involved. When the parameter value indicating whether system-level performance is involved is yes, the value of S3 is 1, and when the parameter value indicating whether system-level performance is involved is no, the value of S3 is 0. S4 is used to indicate whether the system and device are bidirectionally traceable. When the parameter value indicating whether the system and device are bidirectionally traceable indicates yes, the value of S4 is 1; when the parameter value indicating whether the system and device are bidirectionally traceable indicates no, the value of S4 is 0.
6. The system according to claim 1, characterized in that, The airworthiness result output module is also used to perform consistency verification on the allocation results of the total demand of the power distribution system to confirm that each demand in the total demand of the power distribution system has a corresponding allocation result.
7. The system according to claim 1, characterized in that, The validation test rule base and the test validation level allocation rules are constructed based on ARP4754B, FAA Advisory Circular FAA AC, and CAAC Certification Guidelines.
8. The system according to claim 1, characterized in that, The test confirmation assignment report includes: requirement number, module to which the test confirmation belongs, test confirmation type, and airworthiness test method recommendation. The test confirmation type includes no test confirmation required, equipment-level test confirmation, and system-level test confirmation.
9. An automated allocation method for testing and validating aircraft power distribution systems based on a demand matrix, characterized in that, The method, applied to the automated distribution system for testing and validating aircraft power distribution systems based on demand matrices as described in any one of claims 1-8, comprises: The demand matrix construction module imports the full demand of the power distribution system of civil aircraft and generates a demand matrix of the full demand of the power distribution system. The test confirmation requirement identification module matches the requirement matrix with the built-in confirmation test rule library, and respectively filters out the test confirmation items that need to be tested and the test confirmation items that do not ... When the requirement is the item that needs to be tested and confirmed, the test confirmation level allocation module automatically assigns the corresponding test confirmation level type to the item that needs to be tested and confirmed according to the preset test confirmation level allocation rules. The test confirmation level types include system-level test confirmation and equipment-level test confirmation. The airworthiness results output module generates standardized test confirmation allocation reports, supports multi-format export, visualization and statistical analysis, and meets airworthiness audit requirements; Wherein, when the requirement is the item requiring test confirmation, automatically assigning the item requiring test confirmation to the corresponding test confirmation level type according to the preset test confirmation level allocation rule includes: When the requirement is the item requiring test confirmation, a weighted score is applied based on the key parameters corresponding to the item requiring test confirmation in the requirement matrix. The type corresponding to the test confirmation level is then automatically assigned based on the scoring results. The key parameters include the number of devices involved in the requirements, whether system-level performance is involved, whether electronic communication interfaces are involved, and whether the system and devices are bidirectionally traceable.