How repair and maintenance are reshaped as AGI capability advances.

Read as an executable program — the work decomposed into Code, Generative, Agentic, and Human.
Repair and Maintenance sits inside a larger value-flow — 1 parent structure it composes into. The hierarchy is grounding, not the story: it tells you which aggregate exposure Repair and Maintenance inherits.
Repair and Maintenance links to 4 entities via `specializes` — a real edge on the economy graph, surfaced here so the claim stays grounded in data rather than assertion.
Repair and Maintenance is itself composed of 9 parts that flow up into it — the sub-units whose work, summed, is what AGI capability re-prices here first.
Which of this work becomes digital labor — performed under typed authority, promoted to autonomy on track record.
Repair and Maintenance employs 279 occupations — the workforce whose routine, information-shaped tasks an autonomous stack can take under typed authority.
+267 more via employs
Node-intrinsic problems read straight off the graph (exposesProblem) — the evergreen wedges a builder could take into this space.
+8 more problems on the graph
No capability events for this entity yet.
This sector encompasses independent shops and field service networks that fix everything from passenger vehicles to commercial refrigeration and enterprise electronics. The core pain lives in the friction between chaotic customer intake, which usually starts with vague descriptions of broken equipment, and the precise coordination required to match technician schedules with specific replacement parts. Margins are constantly bled dry by unbillable diagnostic time, manual catalog hunting, and phone tag with hardware suppliers.
This is highly fertile ground for voice agents and services-as-software. AI intake agents can ingest erratic customer reports, cross-reference them against digitized original equipment manufacturer manuals, and output standardized service tickets with probabilistic parts lists before a human technician even touches the machine. Meanwhile, services-as-software models can completely take over the tedious backend of warranty claims and supplier procurement, turning historically manual administrative bottlenecks into zero-touch automated workflows.
mindmap
root((NAICS 811 Repair))
Inclusions
Routine Servicing
Equipment Restoration
Consumer Electronics
Computer Repair
Characteristics
Crosses B2B and B2C
Process Based Classification
Focus on Efficiency
Exclusions
Manufacturing Sector
Remanufacturing
Rebuilding
Construction Sector
Building Repair
Plumbing and Electrical
Transportation Sector
Airport Facilities
Seaport Facilities
Retail Sector
After Sale Servicesflowchart TD
A([Customer Needs Repair]) --> B{Check Exceptions}
B -->|Building/Plumbing| C[Construction Sector]
B -->|Rebuilding/Remanufacturing| D[Manufacturing Sector]
B -->|Retail After-Sales| E[Retail Sector]
B -->|Transport Facility Based| F[Transportation Sector]
B -->|In-Scope Core NAICS 811| G[Intake & Diagnostics]
G --> H{Service Required}
H -->|Routine| I[Preventative Maintenance]
H -->|Breakdown| J[Active Restoration & Repair]
I --> K[Efficiency & Quality Testing]
J --> K
K --> L([Returned to Working Order])quadrantChart
title NAICS 811 Repair vs Exclusions
x-axis "Routine/Minor Fix" --> "Major Overhaul/Rebuild"
y-axis "Core NAICS 811" --> "Borderline/Excluded Sectors"
quadrant-1 "Manufacturing/Rebuilding"
quadrant-2 "Borderline Routine"
quadrant-3 "Core General Maintenance"
quadrant-4 "Core Machinery Restoration"
"Computer Tune-up": [0.2, 0.2]
"Preventative Servicing": [0.4, 0.3]
"Electronics Repair": [0.3, 0.4]
"Machinery Restoration": [0.8, 0.3]
"Heavy Equipment Repair": [0.9, 0.4]
"Equipment Remanufacturing": [0.9, 0.9]
"Retail After-Sales Service": [0.3, 0.8]
"Plumbing Repair": [0.4, 0.9]
"Airport Facility Repair": [0.8, 0.8]