Development & Humanitarian Infrastructure · Maintenance planning
How should spare parts and maintenance be planned for remote infrastructure?
Remote projects need a maintenance plan before shipment because the cost of one missing component can be dominated by freight and delay rather than part value. The goal is not to ship excessive spares; it is to identify components whose failure would stop the building or be difficult to replace locally.
Planning guidance — final supplied configuration remains project-specific.
01
Classify components by consequence and replacement difficulty
Identify items that can stop water, sanitation, access, power, HVAC, doors, windows or other essential building functions. Then distinguish locally available consumables from proprietary or imported components.
02
Create a commissioning spares pack
Allow for predictable installation loss or damage: selected fixings, seals, connectors, touch-up materials and other small items can avoid major delays during assembly. The exact pack should follow the manufacturer's system and project experience.
03
Create an operational spares strategy
For occupied buildings, record recommended spare quantities, part numbers, compatible alternatives, storage conditions and reorder lead times. Avoid undocumented substitutions that could compromise technical performance.
04
Hand over maintenance information people can use
Provide practical inspection intervals, cleaning requirements, adjustment procedures, isolation points, replaceable-part references and warranty conditions. Translate or adapt critical instructions where the operating team requires it.
05
Assign the long-term owner
Name who will hold records, approve replacements, manage warranties and fund ongoing maintenance after the project team leaves. Infrastructure without a maintenance owner can deteriorate even when the original product was appropriate.
Continue planning
Related Development & Humanitarian Infrastructure resources
Essential site functions work without analytics. With your permission, Apollo uses analytics to understand which products, guides and project pathways are useful. Analytics stays off until you allow it.