Reliability, Availability, Maintainability (RAM) Analysis

Input: $ARGUMENTS

Interpretations

Before executing, identify which interpretation matches the user’s input:

Interpretation 1 — Define RAM requirements for a new system: The user has a system concept and needs to establish quantitative RAM targets — MTBF, MTTR, availability goals — and allocate them to subsystems. Interpretation 2 — Predict RAM performance for an existing design: The user has a system architecture and wants to calculate expected reliability, availability, and maintainability from component data. Interpretation 3 — Improve RAM for a fielded system: The user has a system with known reliability or maintenance problems and wants to identify root causes and improvement strategies.

If ambiguous, ask: “I can help with setting RAM requirements for a new system, predicting RAM for an existing design, or improving RAM for a fielded system — which fits?” If clear from context, proceed with the matching interpretation.

Depth Scaling

Default: 2x. Parse depth from $ARGUMENTS if specified (e.g., “/ram 4x [input]”).

The Process

Step 1: Define the System and Operating Context

Establish what is being analyzed and under what conditions:

SYSTEM: [name]
MISSION: [primary function]
DESIGN LIFE: [expected operational lifespan]

OPERATING CONTEXT:
- Environment: [temperature, humidity, vibration, corrosion, etc.]
- Duty cycle: [continuous / intermittent / on-demand]
- Operating hours per year: [N]
- Mission duration: [typical mission length]
- Deployment: [fixed / mobile / shipboard / airborne / space]

CRITICALITY:
- Safety-critical: [Yes/No — failure could cause injury/death]
- Mission-critical: [Yes/No — failure causes mission abort]
- Economic impact of downtime: [$/hour or qualitative]

APPLICABLE STANDARDS:
- [MIL-STD-882, IEC 61508, ISO 26262, ARP4761, etc.]

Step 2: Define RAM Requirements

Establish quantitative targets:

RAM REQUIREMENTS:

RELIABILITY:
| Parameter | Target | Basis | Allocation Level |
|-----------|--------|-------|-----------------|
| System MTBF | [hours] | [customer spec / benchmark / derived] | System |
| Mission reliability R(t) | [probability] for [t hours] | [mission requirement] | System |
| Design life reliability | [probability] for [years] | [lifecycle requirement] | System |

AVAILABILITY:
| Parameter | Target | Definition Used |
|-----------|--------|----------------|
| Operational availability (Ao) | [%] | Ao = Uptime / (Uptime + Downtime) |
| Inherent availability (Ai) | [%] | Ai = MTBF / (MTBF + MTTR) |
| Achieved availability (Aa) | [%] | Includes preventive maintenance |

MAINTAINABILITY:
| Parameter | Target | Notes |
|-----------|--------|-------|
| MTTR (Mean Time To Repair) | [hours] | Corrective maintenance |
| MPMT (Mean Preventive Maintenance Time) | [hours] | Scheduled maintenance |
| MMH/OH (Maintenance Man-Hours per Operating Hour) | [ratio] | Total maintenance burden |
| Max corrective maintenance time (95th percentile) | [hours] | Worst-case repair |
| Fault detection coverage | [%] | Built-in test effectiveness |
| Fault isolation to LRU | [%] within [N] fault indications | Diagnostic capability |

Step 3: System Reliability Modeling

Model the system reliability architecture:

3A: Reliability Block Diagram (RBD)

RELIABILITY BLOCK DIAGRAM:

Configuration: [series / parallel / k-of-n / complex]

SERIES ELEMENTS (all must work):
  [A] → [B] → [C] → ... → [output]
  System R(t) = R_A(t) x R_B(t) x R_C(t)

PARALLEL/REDUNDANT ELEMENTS (at least one must work):
  ┌─ [A1] ─┐
  │        │
  ├─ [A2] ─┤  R_parallel = 1 - (1-R_A1)(1-R_A2)
  │        │
  └────────┘

K-OF-N ELEMENTS (at least k of n must work):
  [A1, A2, A3] — need [k] of [3] working

3B: Component Reliability Data

3C: Reliability Predictions

3D: Reliability Improvement Techniques

Step 4: Failure Mode Analysis

Connect to FMEA — identify critical failure modes:

CRITICAL FAILURE MODES:

| ID | Component | Failure Mode | Effect on System | Severity | Occurrence | Detection | RPN | Mitigation |
|----|-----------|-------------|-----------------|----------|------------|-----------|-----|------------|
| FM-1 | [component] | [how it fails] | [system impact] | [1-10] | [1-10] | [1-10] | [S*O*D] | [action] |
| FM-2 | [component] | [how it fails] | [system impact] | [1-10] | [1-10] | [1-10] | [S*O*D] | [action] |

SINGLE POINTS OF FAILURE:
| Component | Failure Effect | Criticality | Mitigation Strategy |
|-----------|---------------|-------------|---------------------|
| [name] | [what happens] | [CRITICAL/MAJOR] | [redundancy / monitoring / design-out] |

Step 5: Maintainability Analysis

Analyze ease of maintenance:

5A: Maintenance Concept

MAINTENANCE LEVELS:
| Level | Location | Capability | Typical Actions |
|-------|----------|------------|-----------------|
| Organizational (O-level) | [field/user site] | [tools, skills] | [remove & replace, operational checks] |
| Intermediate (I-level) | [depot/shop] | [test equipment] | [diagnose, repair assemblies] |
| Depot (D-level) | [factory/OEM] | [full capability] | [overhaul, remanufacture] |

5B: Maintenance Task Analysis

5C: Maintainability Design Features

Step 6: Availability Calculation

AVAILABILITY MODEL:

INPUTS:
- MTBF: [hours] (from Step 3)
- MTTR: [hours] (from Step 5)
- MPMT (Mean Preventive Maintenance Time): [hours]
- Preventive maintenance interval: [hours]
- Mean Logistics Delay Time (MLDT): [hours]
- Mean Administrative Delay Time (MADT): [hours]

CALCULATIONS:

Inherent Availability:
  Ai = MTBF / (MTBF + MTTR)
  Ai = [value] / ([value] + [value]) = [result]

Achieved Availability:
  Aa = MTBM / (MTBM + M_bar)
  where MTBM includes preventive maintenance
  Aa = [result]

Operational Availability:
  Ao = MTBM / (MTBM + MDT)
  where MDT = MTTR + MLDT + MADT
  Ao = [result]

AVAILABILITY COMPARISON:
| Metric | Target | Predicted | Margin | Status |
|--------|--------|-----------|--------|--------|
| Ai | [%] | [%] | [+/- %] | [MEETS/SHORTFALL] |
| Aa | [%] | [%] | [+/- %] | [MEETS/SHORTFALL] |
| Ao | [%] | [%] | [+/- %] | [MEETS/SHORTFALL] |

SENSITIVITY ANALYSIS:
| Parameter Changed | Change | Effect on Ao | Elasticity |
|-------------------|--------|-------------|------------|
| MTBF +10% | [new MTBF] | [new Ao] | [% change in Ao / % change in MTBF] |
| MTTR -10% | [new MTTR] | [new Ao] | [% change] |
| MLDT -50% | [new MLDT] | [new Ao] | [% change] |

Step 7: RAM Improvement Opportunities

RAM IMPROVEMENT PLAN:

| # | Opportunity | RAM Parameter Improved | Current | Target | Action Required | Cost Estimate | Priority |
|---|-------------|----------------------|---------|--------|----------------|---------------|----------|
| 1 | [description] | [MTBF/MTTR/Ao/etc.] | [current value] | [improved value] | [specific action] | [cost] | HIGH/MED/LOW |
| 2 | [description] | [parameter] | [current] | [improved] | [action] | [cost] | HIGH/MED/LOW |

IMPROVEMENT CATEGORIES:
- Design improvements: [list actions that change the design]
- Process improvements: [list actions that change maintenance processes]
- Logistics improvements: [list actions that reduce supply delays]
- Training improvements: [list actions that improve technician capability]

ROI ANALYSIS:
| Improvement | Implementation Cost | Annual Savings (reduced downtime) | Payback Period |
|-------------|--------------------|---------------------------------|----------------|
| [action] | [$] | [$] | [months] |

Output Format

## RAM ANALYSIS REPORT: [System Name]

### System & Operating Context
[Environment, duty cycle, criticality, standards]

### RAM Requirements
[Targets for MTBF, MTTR, Ao with rationale]

### Reliability Model
[RBD, component data, predictions vs. requirements]

### Critical Failure Modes
[Top failure modes with RPN, single points of failure]

### Maintainability Assessment
[Maintenance concept, task analysis, design features]

### Availability Predictions
[Ai, Aa, Ao calculations with sensitivity analysis]

### RAM Shortfalls & Improvements
[Gaps between predicted and required, improvement plan with ROI]

### Open Items
[Data gaps, assumptions requiring validation, trades to resolve]

Quality Checklist

Before completing:

• Operating context and duty cycle defined
• Quantitative RAM requirements established with rationale
• Reliability block diagram constructed
• Component failure rates sourced and documented
• System reliability predicted and compared to requirements
• Single points of failure identified
• Maintenance concept defined (levels, tasks, intervals)
• MTTR predicted from task analysis
• Availability calculated (Ai, Aa, Ao) and compared to targets
• Sensitivity analysis performed
• Improvement opportunities identified with ROI
• Data source confidence levels noted

Next Steps

After RAM analysis:

1. Use /riskmgmt to manage risks from RAM shortfalls
2. Use /tradestudy to evaluate redundancy vs. cost trade-offs
3. Use /testplan to define reliability demonstration tests
4. Use /lcca to incorporate maintenance costs into lifecycle cost
5. Use /hsi to ensure maintenance tasks match human capabilities
6. Use /tpm to track RAM parameters during development