MIL-STD-1798 Mechanical Equipment And Subsystems Integrity ProgramThe purpose of this standard is to describe the general process to achieve and maintain the physical and functional integrity of the mechanical elements of aircraft systems. The goal of this integrity program is to achieve the desired level of safety and aircraft availability at the most economic cost across the life cycle of the weapon system. This standard allows the process to be tailored in a competitive environment to meet specific equipment, subsystem, and/or system requirements. The Mechanical Equipment and Subsystems Integrity Program MECSIP is implemented in the planning process and continued until retirement of the system.

Pages 1 - 2 - 3 - 4 - 5 - 6 - 7 - 8 - 9 - 10 - 11 - 12 - 13 - 14 - 15 - 16 - 17 - 18 - 19 - 20 - 21 - 22 - 23 - 24 - 25 - 26 - 27 - 28 - 29 - 30 - 31 - 32 - 33 - 34 - 35 - 36 - 37 - 38 - 39 - 40 - 41 - 42 - 43 - 44 - 45 - 46 - 47 - 48 - 49 - 50 - 51 - 52 - 53 - 54 - 55 - 56 - 57 - 58 - 59 - 60 - 61 - 62 - 63 - 64 - 65 - 66 - 67 - 68 - 69 - 70 - 71 - 72 - 73 - 74 - 75 - 76 - 77 - 78 - 79 - 80 - 81 - 82 - 83 - 84 - 85 - 86 - 87 - 88 - 89 - 90 - 91 - 92 - 93 - 94 - 95 - 96 - 97

MIL-STD-1798C

5.4 (Task IV) Component Development and Systems Functional Tests.

These tests are intended to verify the sub-system integrity performance and to validate design verification analysis. Tests may be conducted on sub-systems or individual components, in simulated sub-system installation environments, or during flight and ground testing. All testing shall be planned, scheduled, and conducted in accordance with the overall sub-system test plan and specific requirements. Instrumentation should be provided when test is used to validate design analysis. All Task IV testing shall be conducted post-CDR with successful completion satisfying Milestone C exit criteria associated with test. Tests shall include, but not be limited to, those described in the following subparagraphs.

5.4.1 Component and rig test descriptions.

All controls and subsystems component and rig testing (including air vehicle integration) requirements shall be defined. Test descriptions will include, at a high level, test objectives, facility requirements and capabilities, and subsystem/component descriptions.

5.4.2 Testing risk mitigation.

To the maximum extent possible, controls and subsystems component and rig testing results shall be used to support the mitigation of known design risks. An assessment of known controls and subsystems design risks shall be accomplished in order to maximize the use of component and rig testing results in their mitigation. Examples of assessment activities include: evaluation

of design assumptions, trade studies, technology readiness levels (TRLs), production variations and component residual life. The risk assessment shall be updated in accordance with the

overall risk management plan.

5.4.3 Hardware and systems rig testing

5.4.3.1 Subsystem performance.

All controls and subsystem components (including air vehicle integration) shall be tested as necessary to resolve analytical uncertainty to verify performance and durability requirements are satisfied. Examples of these tests include: fuel/fuel delivery, lubrication, anti-ice, thermal management, sensing, electrical power, prognostic health management, and actuation.

5.4.3.2 Dry rig.

All electronic controls shall optimize the use of dry rig test facilities during development for hardware/software integration and software development. The extent of dry rig facilities shall be governed by factors such as system complexity, technology maturity, and simulation fidelity. Examples of dry rig testing include: electronic verification bench, performance model validation, mission simulation/pilot in loop, fault injection, fault detection, fault accommodation, etc.

5.4.3.3 Wet rig.

All controls and subsystems shall optimize the use of wet rig test facilities during development

for hardware/software integration and software development. The extent of wet rig facilities shall be governed by factors such as system complexity, technology maturity, and simulation fidelity.

Examples of wet rig tests include: controls system development, fuel system integration, iron

bird validation, fault injection, fault detection, fault accommodation, and lubrication systems development.