maintainability-engineering

name	maintainability-engineering
description	Maintainability engineering — MTTR prediction (MIL-HDBK-472, Procedure V), maintenance task analysis (MTA), level of repair analysis (LORA), built-in test (BIT/BITE), LRU/SRU design, maintenance manhours per flight hour (MMH/FH), operational availability (Ao), preventive vs. corrective maintenance ratio, human factors in maintenance (MEDA, error proofing), FMEA linkage to maintenance, and MIL-HDBK-470A/471A standards.
metadata	{"priority":7,"promptSignals":{"phrases":["maintainability","MTTR","maintenance task analysis","LRU design","maintainability engineering","operational availability"],"minScore":3}}

Maintainability Engineering — Complete Skill

Maintainability Definitions

Key Metrics

MTTR (Mean Time To Repair): Average time from failure detection to system returned to operational status Includes: diagnosis, access, removal, replacement, verification, reassembly MTTR = Σ(MTTR_i × λ_i) / Σλ_i [weighted average by failure rate; critical for systems with many failure modes]

MDT (Mean Down Time): MTTR + administrative/logistic delays (waiting for parts, personnel) MLDT (Mean Logistics Down Time): time waiting for parts, tools, test equipment (not repair time) MDT = MTTR + MLDT + administrative_delay_time

Maintenance Manhours per Flight Hour (MMH/FH): MMH/FH = Σ(task_frequency × task_manhours) / [flying_hours_per_year / calendar_year] Target for modern aircraft: MMH/FH = 10–25 (commercial); 30–100 (military) Comparison: F-117 Stealth: 100+ MMH/FH; F-35: target < 20 MMH/FH (controversial; actual higher)

Operational Availability (Ao): Ao = MTBF / (MTBF + MDT) [probability system operational when needed; includes logistics delays] Or: Ao = MTTF / (MTTF + MDT) [for non-repairable] Inherent availability: Ai = MTBF / (MTBF + MTTR) [excludes logistics; just repair time] Target: Ao ≥ 0.90 (military aircraft); Ao ≥ 0.995 (commercial airline)

---

MTTR Prediction (MIL-HDBK-472)

Procedure V (MTTR Prediction)

MIL-HDBK-472 Procedure V: Bottom-up method: analyze each maintenance task → estimate task time → weight by failure rate

Task time elements: T_task = T_diagnose + T_access + T_disengage + T_replace + T_reengage + T_verify + T_close Time estimation: from elemental time data tables (MTM — Methods Time Measurement) or task analysis

Task element times (typical examples from MIL-HDBK-472 tables): Diagnose via BIT/BITE: 2–5 min (fault isolated to LRU level) Diagnose without BIT: 15–45 min (technician with test equipment) Remove fastener (quick-disconnect): 0.1 min per fastener × N fasteners Remove threaded fastener: 0.3 min per fastener Access panel open/close: 0.5–2 min depending on type Replace LRU (connector + mount): 5–15 min Functional check (automated): 1–3 min; manual check: 5–30 min

MTTR system level: MTTR_system = Σ(λ_i × t_repair_i) / Σλ_i [where sum is over all failure modes/LRUs] Equivalent: if one LRU dominates λ_i, MTTR ≈ that LRU's repair time

---

Maintenance Task Analysis (MTA)

MTA Structure

MTA hierarchy:

1. Identify all maintenance significant items (MSIs) requiring scheduled maintenance
2. Define task steps and sequences: written procedure level
3. Determine time, tools, personnel, technical data, support equipment needed
4. Identify human factors concerns (access, visibility, force required, error risk)
5. Feed into: MMH/FH calculation; spare parts provisioning; training syllabus; maintenance manual

Task criticality: Safety effect: if task omitted → catastrophic/critical hazard → mandatory interval; controlled documentation Functional effect: if deferred → equipment failure → operational impact Economic effect: if deferred → increased cost → balance maintenance vs. failure cost

Reliability-Centered Maintenance (RCM)

RCM process (MSG-3 for aviation; MIL-HDBK-1797 for defense):

1. Define system functions and functional failures
2. Identify Failure Modes and their Effects (FMEA link)
3. Classify consequence: safety/hidden/operational/non-operational
4. Select maintenance task type:
   • Scheduled inspection: detect before failure (on-condition)
   • Life limit: replace at fixed interval (hard time)
   • Failure finding: find hidden failures (e.g., check backup power)
   • Redesign: if no effective maintenance task exists
5. Set task interval (optimized for cost, safety, reliability)

---

Level of Repair Analysis (LORA)

Repair vs. Discard Decision

Three levels of maintenance: Organizational (O-level): unit or ship; replace LRU; limited test capability; no repair of SRU Intermediate (I-level): depot-forward; repair LRU → replace SRU; moderate test capability Depot (D-level): full repair down to component level; complete overhaul; long-cycle

LORA decision factors:

1. Fault isolation capability at each level (BIT coverage %)
2. Repair time at each level → effect on Ao
3. Cost: cost to repair at each level vs. discard and replace
4. Maintenance footprint: size/weight of test equipment; personnel skill
5. Hazardous material handling

Economic LORA model: Repair at O-level: C_repair_O = labor_cost + overhead − avoid_purchase_new Discard at O-level: C_discard = purchase_replacement Choose repair if C_repair_O < C_discard AND T_repair acceptable

---

Built-In Test (BIT/BITE)

Design for Testability

BIT (Built-In Test): On-board diagnostic capability; detects and isolates faults to LRU level BIT fault coverage: % of fault modes detectable by BIT; target > 90% for avionics BIT false alarm rate: % of BIT indications with no fault found (NFF); target < 5%

Types: Initiated BIT (IBIT): triggered by technician; comprehensive but takes equipment offline Continuous BIT (CBIT): runs continuously during operation; limited scope; no operational interruption Power-up BIT (PUBIT): runs at startup; detects gross faults

BITE (Built-In Test Equipment): More sophisticated than simple BIT; dedicated test circuitry; typically for complex avionics Includes: self-test of BITE itself; fault logging; download capability

BIT coverage calculation: BIT_coverage = (fault_modes_detected_by_BIT / total_fault_modes) × 100% Effect on MTTR: MTTR_with_BIT = t_BIT_diagnose (2–5 min) << MTTR_without_BIT (15–60 min) → significant Ao improvement

---

LRU Design Principles

Design for Maintainability

LRU (Line Replaceable Unit): assembly replaced at organizational level without repair Design principles:

1. One-screw access: single tool; single type of fastener; quick-disconnect preferred
2. Accessibility: 30-inch reach; two-handed access; not behind other components
3. Weight limit: ≤ 15 kg for one-person unassisted removal (MIL-HDBK-759)
4. Foolproofing: asymmetric connectors; captive screws; keyed interfaces → prevents mis-installation
5. Self-locating: pilot pins guide LRU to correct position; no alignment adjustment needed
6. Visual inspection: critical items visible during pre-departure inspection without tools

Accessibility standards: MIL-HDBK-759C: human engineering design criteria; panel force, reach envelope, clearance Access opening minimum: 150 mm × 150 mm for one hand; 230 mm × 460 mm for two hands Torque tool access: 150 mm clearance above fastener for standard torque wrench

---

Maintenance Human Factors

Maintenance Error Decision Aid (MEDA)

MEDA: Boeing-developed process for investigating and preventing maintenance errors Root causes of maintenance errors (MEDA categories):

1. Information: wrong, missing, or unclear documentation
2. Equipment/tools: unavailable, wrong, uncalibrated
3. Aircraft design: poor access, poor labeling, complexity
4. Job/task: complex, unusual, time pressure
5. Technical knowledge/skills: training gap, experience
6. Individual factors: fatigue, distraction, norms

Dirty Dozen (FAA maintenance error factors): Lack of communication, complacency, lack of knowledge, distraction, lack of teamwork, fatigue, lack of resources, pressure, lack of assertiveness, stress, lack of awareness, norms

Error proofing for maintenance: Color coding connectors/hoses; clearly visible orientation marks; torque stripe after tightening; lockwire for safety-critical fasteners; checklists; two-person inspection for critical tasks

---

Standards and References

Standard	Scope
MIL-HDBK-470A	Designing and developing maintainable products and systems
MIL-HDBK-471A	Maintainability verification/demonstration
MIL-HDBK-472	Maintainability prediction (MTTR)
MIL-HDBK-759C	Human factors engineering for military systems
ATA iSpec 2200	Aviation maintenance documentation standards
MSG-3	Maintenance Steering Group — RCM for civil aviation
SAE JA1011	RCM criteria for processes and results

Output

Provide: system description (system name; criticality; mission type; operating environment), availability analysis (MTBF [hours]; MTTR prediction [hours] from MIL-HDBK-472; MLDT [hours]; MDT = MTTR+MLDT; Ao = MTBF/(MTBF+MDT) [%]; Ai = MTBF/(MTBF+MTTR) [%]), MTTR task breakdown (diagnose: BIT? [min]; access: panel type, fasteners [min]; remove LRU [min]; replace [min]; verify [min]; total MTTR [min]; weighted MTTR_system = Σ(λ_i×t_i)/Σλ_i [hours]), BIT design (fault coverage [%]; false alarm rate [%]; IBIT/CBIT/PUBIT; diagnosis time with BIT [min] vs. without BIT [min]), LRU design assessment (weight [kg] ≤ 15 kg?; access opening [mm×mm]; fastener type; keyed connector: yes/no; one-hand vs. two-hand; foolproofing measures), maintenance task analysis (scheduled tasks: description, interval [hours/cycles], manhours; MMH/FH = [value]; comparison to target), LORA recommendation (O/I/D level assignment; economic comparison [$/repair vs. $/replace]; test equipment required; personnel skill), human factors (access rating per MIL-HDBK-759C; MEDA risk areas; error-proofing implemented), and applicable standard (MIL-HDBK-472 for MTTR prediction; MIL-HDBK-470A for design; MSG-3 / SAE JA1011 for RCM).