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.3.8.4 Equipment Prognostic Health Monitoring (PHM) systems.

The effectiveness of PHM systems (reference 5.2.6, Prognostic Health Monitoring planning.) shall be evaluated during component development and test. Equipment PHM systems used to support the sustainment of fielded equipment should be developed concurrently with the equipment and used throughout the sustainment portion of an aircraft program.

5.3.8.5 Obtain Original Equipment Manufacturer (OEM) data.

Obtain information from each OEM regarding recommended preventative maintenance tasks/intervals and time changes along with the technical data/analysis supporting those recommendations (reference 5.1.5). Retain the original data for future reference and include the recommendations in the weapon system maintenance publications. This data should be retained for reference for the life of the weapon system.

5.3.9 Flight Manual.

The subsystems data necessary for preparation of the flight manuals shall be developed. The data includes but not be limited to cautions and warnings, operational limitations and special pilot procedures.

5.3.10 Create Work Unit Code (WUC) Manual.

This manual must have a five-digit code for each component being monitored and the nomenclature must be in the language the technicians use (English for DoD technicians). When a component is to be time changed, serially tracked, or warranted, (i.e., in particular a safety- or mission-critical component) it will be identified with a special letter or asterisk.

5.3.11 Identify Technical Needs (Task III).

MECSIP Managers shall make a listing of Technical Needs encountered on an annual basis. A compiled list, from all programs, will be discussed/finalized at the MECSIP Technical Interchange Meeting and submitted into the Service-specific Research Laboratory as candidate developmental Technical Needs.

5.3.12 Update MECSIP Master Plan.

Update MECSIP Documents based on information learned during the analysis phase. Update any existing information which changed during Task 3 plus add:

a. OEM maintenance recommendations

b. Thermal/environmental analyses. (Reference 5.3.2.4, zoning of compartments.)