How to Plan Spare Parts and Service for a Multi-Site Robot Fleet

A single robot can be supported with a phone call to the supplier and a parts order that arrives in a few days. A fleet of 30 robots across 5 sites cannot. As fleet size grows, the spare parts strategy shifts from reactive ordering to proactive planning—and the cost of getting it wrong shifts from a minor inconvenience to extended downtime across multiple sites. This article explains how to build a spare parts and service plan for a multi-site robot fleet, covering parts classification, stocking strategy, lead time management, and version control.

Why Spare Parts Planning Changes as Fleet Grows

With a small fleet, spare parts planning is straightforward: order parts when something breaks, keep common wear items on hand, and rely on the supplier’s standard lead time. The cost of downtime is limited because only a small number of robots are affected.

As fleet size grows, the dynamics change:

• The frequency of part failures increases proportionally with fleet size
• Different sites may have different failure patterns due to environment, usage, and age
• Shipping parts between sites takes time and costs money
• Customs and import processes may delay international parts shipments
• Multiple suppliers may mean multiple parts catalogs, ordering processes, and lead times
• The cost of a missing critical spare is multiplied by the number of robots that depend on it

The shift from reactive to proactive spare parts management becomes necessary as fleet size grows. When and how to transition depends on criticality, failure history, actual lead time, service SLA, site geography, and repair capability—not on a fixed robot count threshold.

Critical Spares vs Wear Parts vs Consumables

Not all parts are equal. A spare parts strategy should classify parts into three categories based on failure impact and replacement frequency:

Why Classification Matters

If a critical spare is not in stock when it fails, the robot is down until the part arrives. The impact on fleet capacity depends on the fleet size, the robot’s role, and the duration of downtime. The buyer should calculate the capacity impact of a missing critical spare based on their own fleet size and operational requirements, not assume a fixed percentage.

Illustrative example: if a critical part has an actual lead time of several weeks and the affected robot represents a significant share of fleet capacity, the downtime impact may be substantial. The exact figure depends on fleet size, redundancy, and operational requirements.

If a wear part is not in stock, the robot may continue to operate with degraded performance (e.g., worn wheels causing navigation inaccuracy) until the part arrives. This is not ideal, but it is not a hard stop.

If a consumable is not in stock, the robot cannot perform its task (e.g., a cleaning robot without cleaning solution). But consumables are typically easy to source locally and have short replenishment cycles.

Battery, Wheels, Brushes, Sensors, Grippers and Cables: Different Failure Profiles

Each part type has a different failure pattern, and the spare parts plan should account for these differences:

Batteries

Batteries are typically the most expensive wear item in a mobile robot fleet. Battery failure is not sudden—it is gradual capacity degradation. A battery that originally provided a certain runtime will degrade over time based on usage cycles, charging behavior, temperature, and battery chemistry.

• Failure trigger: capacity drops below the minimum required for a full shift
• Replacement indicator: runtime falls below the operational requirement (manufacturer-defined or buyer-defined threshold)
• Stocking: maintain spare batteries based on fleet size and failure history
• Planning: schedule battery replacement based on age, usage data, and manufacturer guidance—not on failure

Wheels and Tires

Wheels and tires wear based on distance traveled, floor surface, and load. A robot operating on rough epoxy floors will wear wheels faster than one on polished concrete.

• Failure trigger: reduced traction, navigation inaccuracy, or visible damage
• Replacement indicator: tread depth below manufacturer minimum or navigation drift exceeding tolerance
• Stocking: maintain spare sets based on fleet size and replacement frequency
• Planning: track wheel replacement dates per robot to identify high-wear sites

Brushes and Squeegees (Cleaning Robots)

Brushes and squeegees wear based on area cleaned, floor type, and debris load.

• Failure trigger: cleaning quality degradation or visible wear
• Replacement indicator: brush bristle length below manufacturer minimum
• Stocking: maintain spare sets based on cleaning frequency and area
• Planning: track replacement frequency per site to identify high-wear environments

Sensors

Sensors (LiDAR, cameras, safety scanners) typically do not have a predictable wear pattern. They either work or they fail. Sensor failure may be sudden (hardware failure) or gradual (accuracy drift).

• Failure trigger: navigation errors, safety system faults, or accuracy degradation
• Replacement indicator: sensor calibration fails or error codes indicate hardware failure
• Stocking: maintain spare sensors of each critical type at regional hub
• Planning: track sensor error codes to identify degradation trends

Grippers and End-Effectors

Gripper wear depends on the number of cycles, part weight, part surface, and gripping force.

• Failure trigger: dropped parts, grip failures, or mechanical play
• Replacement indicator: grip success rate drops below threshold or mechanical inspection shows wear
• Stocking: maintain spare gripper per site or regional hub
• Planning: track grip failure rates per robot to identify high-wear applications

Cables and Connectors

Cables fail due to bending fatigue, abrasion, and connector wear. The failure is often intermittent before it becomes permanent.

• Failure trigger: intermittent communication errors, power interruptions, or visible cable damage
• Replacement indicator: error frequency increases or visual inspection shows damage
• Stocking: maintain spare cables of each type per site
• Planning: track cable replacement dates to identify high-fatigue locations on the robot

Central Spare Pool vs Local Site Stock

The decision between a central spare parts pool and local site stock depends on the trade-off between inventory cost and response speed:

Recommended Hybrid Approach

For most multi-site fleets, a hybrid approach works best:

• Local site stock: wear parts and consumables that are replaced frequently and have low unit cost
• Regional hub stock: critical spares that are expensive, infrequently needed, and can be shipped to sites within a time frame that meets the fleet’s downtime tolerance
• Supplier stock: long-lead or specialized parts that are not worth stocking locally

Lead Time, Customs and Regional Service Coverage

Lead Time Management

The spare parts plan must account for the actual lead time from order to delivery, not the supplier’s quoted lead time. Actual lead time includes:

• Order processing time
• Manufacturing or procurement time (if not in stock)
• Shipping time (domestic vs. international)
• Customs clearance (for international shipments)
• Internal receiving and dispatch to site

The buyer should measure actual order-to-delivery time for each part type and use that data—not the supplier’s quoted lead time—to determine stocking levels. Actual lead time may be significantly longer than quoted lead time, especially for international shipments involving customs and import processes.

Illustrative example: a part with a quoted 2-week lead time may take several weeks longer to reach a site in another country once order processing, international shipping, customs clearance, and internal dispatch are included.

Customs and Import Considerations

For international deployments, spare parts may be subject to:

• Import duties and taxes
• Customs documentation requirements (commercial invoice, packing list, certificate of origin)
• Restricted item regulations (lithium batteries have specific shipping and import restrictions)
• Local certification requirements (some countries require local certification for electrical components)

These factors can add weeks to the delivery time and should be planned for in advance, not discovered when a part is urgently needed.

Regional Service Coverage

The buyer should assess the supplier’s regional service coverage:

• Does the supplier have a service team or partner in the buyer’s region?
• Where is the nearest spare parts warehouse?
• What is the typical response time for a parts order in the buyer’s country?
• Can the supplier provide a local-language support contact?

If the supplier does not have regional coverage, the buyer may need to maintain higher local stock levels or identify a third-party service provider for parts and maintenance.

Firmware, Software and Controller Version Management

Spare parts planning is not only about physical components. Firmware and software versions must also be managed across a multi-site fleet.

Version Management Challenges

• A new firmware version may fix bugs but introduce new behavior that affects site-specific configurations
• Different sites may be running different firmware versions if updates are not centrally managed
• A replacement controller may come with a different firmware version than the rest of the fleet
• Software updates may require configuration changes that need to be tested per site

Version Management Practices

• Maintain a version inventory: which robots are running which firmware/software versions
• Define a standard version: the approved version for the fleet
• Test updates at one site before pushing to all sites
• Document version-specific configuration changes
• Maintain rollback capability: if an update causes issues, can the robot be reverted to the previous version?

Failure Reporting and Root-Cause Feedback to Suppliers

A spare parts plan is only as good as the data that feeds it. Without systematic failure reporting, the buyer is guessing at stocking levels instead of calculating them.

Failure Data to Collect

Supplier Feedback Loop

Failure data should be shared with the supplier on a regular basis (monthly or quarterly). This serves two purposes:

1. The supplier can identify product quality issues and improve future versions
2. The supplier can recommend stocking levels based on actual failure data from the buyer’s fleet

Spare-Parts Planning Worksheet for Multi-Site Fleets

Research Sources Used

1. Source / organization: IEEE (5-step spare parts management decision framework) | URL: https://ieeexplore.ieee.org/ | Version/date: as cited in report_batch_b
2. Source / organization: IEEE (multi-site inventory allocation optimization, MOEA/D algorithm) | URL: https://ieeexplore.ieee.org/ | Version/date: as cited in report_batch_b
3. Source / organization: UN38.3 (lithium battery transport testing standard) | URL: https://www.unece.org/ | Version/date: as cited

Internal product/material source: report_batch_b (batch B research report) [TO VERIFY]: none