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

becomes the MAP and can be adjusted up or down, based on experience gained in MECSIP

execution and at the discretion of the MECSIP Manager. The WUC associated with each

safety- and mission-critical components shall be analyzed and a MAP assigned to it. If the MAP

is too high or too low to allow an alert, the RAT will recommend adjustments to it, using their best judgment.

The FSID shall provide periodic (typically, monthly) failure listing for each system to alert the MECSIP Manager of potential failures. The MECSIP Manager shall establish a priority schedule for each system, based on critical components analysis, classification and on current data. The MECSIP Manager should rely on the Material Deficiency Report/Quality Deficiency Report system for alerts for periods preceding the collection of MTBF data.

5.5.2.3 Identify items which fail to meet the MAP (alerts).

The Program Office shall develop a program which automatically provides an alert for any

safety-, or mission- critical component that fails to meet its MAP. The alert does not mean there is a problem; it means a problem may exist. Once the MECSIP Manager establishes the

component's MAP, an automatic alert can be set at any number or percentage below the MAP.

The program shall measure reliability at the 18-month MTBF mark. Any component that does not meet 80 percent (80%) of the MAP will be considered as failing the reliability test. To assist in making decisions, the most recent 5 (or more) years of data shall be compiled and used to show trends. If the data is susceptible to season variations, use a 12-month (or 4 quarter) rolling average approach. The trend data is not used for any computations. Like the MAP, the alert is adjustable by the MECSIP Manager. The alert begins the investigation process.

5.5.2.4 Facilitate Engineering communication with Field personnel.

The Program Office shall establish shop bulletin boards via the Internet to enhance communication between Engineering and Field shops (e.g., clarify a TO system; direct users to procedures in the TO). The bulletin boards will not be used by Base personnel to request waivers or technical details for a specific aircraft condition. The Internet address shall only be available to Mil-Net users and shall be secure (HTTPS).

5.5.2.5 Develop a Scheduled Inspection (e.g., HSC and ISO) Tracking Program.

The Program Office shall develop a Scheduled Inspection Tracking Program(SITP). Isochronal Inspections are the biggest expenditure of unit funds and visibility into the discrepancies discovered from one ISO to the next are not readily available to the Field shops and Program Engineering. Each Base will enter their ISO and HSC data into the MDC system. The SITP shall list the "Top Twenty" WUCs for the components which require the most maintenance. The SITP shall display individual aircraft tail number data and list the last five inspections on a common display screen. All discrepancy data found during a scheduled inspection shall be stored in the system indefinitely. The Program shall display the last five discrepancies for each tail number and display a "Top Twenty" WUC chart for the worst performers.

5.5.2.6 Develop a tail number part tracking program for serial-number-controlled parts.

The Program Office shall develop a tail number part tracking program for serial-number- controlled parts. The tail number part-tracking shall be composed of the following:

a. List all aircraft information, such as tail number, Base, model, last Program Depot

Maintenance (PDM), last ISO, and last HSC.

b. List all MSIs by serial number, date installed and location, hours remaining until time change, and other information as the MECSIP Manager may deem necessary.