Skip to content

Repairability

The scored design property of a physical artefact measuring how cheaply and reliably a failed instance can be restored by component replacement rather than whole-unit replacement — a conjunction of accessible disassembly, modularity, documentation, parts availability, and software support.

Core Idea

Repairability is the design property of a physical artefact determining how cheaply, quickly, and reliably a failed instance can be returned to function by replacing faulty components rather than the whole unit. It is not one choice but a conjunction: accessible, non-destructively removable fasteners; a modular architecture with standardized interfaces; diagnostics and service manuals; spare parts at a price ratio low enough to make repair rational; and tooling within the target repair population's reach. The canonical measure is France's/the EU's repairability index.

Scope of Application

Repairability applies wherever an artefact's geometry and material continuity permit disassembly and component replacement.

  • Design for X / serviceability — the home discipline, treating repair as a design constraint.
  • Consumer electronics — iFixit scoring, Fairphone's modular phone, the right-to-repair movement.
  • Circular-economy policy — the EU Right to Repair Directive and eco-modulated producer-responsibility fees.
  • Automotive — independent-repair access, OBD-II standardization, third-party parts ecosystems.
  • Aerospace and medical devices — line-replaceable units and MRO economics.

Clarity

Naming repairability collapses a diffuse conversation — "good build quality," "user-serviceable" — into measurable sub-criteria: disassembly step count, fastener type, spare-parts price ratio, documentation, software support. The index makes this operational and auditable. It also makes anti-repair design visible: a glued enclosure or software-locked part reads as deliberate optimization against repair, and it sharpens repairability against durability, fault tolerance, and modularity, with which it is constantly conflated.

Manages Complexity

Whether a failed product is worth repairing depends on a tangle of incommensurable particulars — joining method, disassembly path, tooling, parts economics, software locks — varying by device, component, and repairer. Repairability compresses that into a fixed scored vector, rolled into one auditable index. The regulator, designer, and buyer track a handful of axes instead of unbounded detail, reading the repair-versus-replace outcome, the anti-repair pattern, and the lifecycle and regulatory consequences off the same compressed measure.

Abstract Reasoning

All moves run on the small vector of scored axes. The property licenses an economic-rationality move (compute a repair-versus-replace verdict, indexed to the target repair population), a diagnostic move (read anti-repair intent off where scores were sacrificed), a boundary-drawing move (sort repairability from durability, fault tolerance, and modularity by which axis is in play, guarding the modular-but-glued error), and an interventionist move (each axis a lever with downstream lifecycle and regulatory effects).

Knowledge Transfer

Within engineering design-for-X and adjacent product and policy fields the property transfers as mechanism — the scored vector, the population-indexed verdict, the intent diagnostic, and the axis-as-lever treatment carry intact across electronics, automotive, aerospace, and infrastructure, because these are one substrate (physical artefacts) at many scales. Beyond physical artefacts it does not transfer: "disassemble/reassemble" has no matching content in software, tissue, or institutions, so those uses are metaphor. The genuine portable skeleton lives in the parent primes modularity, maintenance, accessibility, and design_for_lifecycle_adaptability; the index and right-to-repair political economy stay home.

Relationships to Other Abstractions

Local relationship map for RepairabilityParents appear above the current abstraction, mutual partners to the right, and children below. Node labels state whether each abstraction is prime or domain-specific; colors identify relation types.RepairabilityDOMAINPrime abstraction: Design for Lifecycle Adaptability — is part ofDesign for Life…PRIMEPrime abstraction: Maintenance — is part ofMaintenancePRIMEPrime abstraction: Modularity — is part ofModularityPRIME

Current abstraction Repairability Domain-specific

Parents (3) — more general patterns this builds on

  • Repairability is part of Design for Lifecycle Adaptability Prime

    Repairability contains lifecycle adaptability because the original design must preserve a feasible path for later diagnosis, access, replacement, and support.

  • Repairability is part of Maintenance Prime

    Repairability contains Maintenance as the intervention that restores intended function after degradation or component failure.

  • Repairability is part of Modularity Prime

    Repairability contains Modularity because a failed component must be independently identifiable, removable, replaceable, and reconnectable without replacing the whole artifact.

Hierarchy paths (5) — routes to 4 parentless roots

Neighborhood in Abstraction Space

Repairability sits in a sparse region of the domain-specific corpus (97th percentile for distinctiveness): few abstractions share its structure, so a faithful description tends to retrieve it precisely.

Family — Software Decay & Debugging (10 abstractions)

Nearest neighbors

Computed from structural-signature embeddings · 2026-07-12