Robot Fleet Task Capacity Estimator

The Robot Fleet Task Capacity Estimator calculates how many completed tasks a fleet can deliver over a selected operating period. It combines fleet size, productive operating time, average task duration, and an optional utilization factor so planners can translate robot availability into a practical throughput estimate.

Use it for warehouse AMRs, service robots, inspection platforms, or other fleets where a task has a repeatable average cycle time. The result is especially useful when comparing staffing assumptions, evaluating whether an existing fleet can absorb demand, or estimating the capacity effect of adding robots or improving utilization.

Inputs

hr
min
%
Result
Estimated tasks
Productive fleet hours
Tasks per robot
Theoretical tasks at 100% utilization

1. Enter fleet size
Use the number of robots expected to be available during the period.

2. Set operating time
Enter scheduled operating hours for each robot over the same period.

3. Add cycle time
Enter the average minutes required to complete one task, including normal travel or handling time.

4. Apply utilization
Use productive utilization to account for charging, waiting, congestion, maintenance, and other non-task time.

5. Review capacity
The main result estimates completed tasks for the period; the breakdown shows productive hours and per-robot throughput.

Theoretical task capacity = Robots × Operating hours × 60 ÷ Minutes per task Estimated task capacity = Theoretical task capacity × Utilization ÷ 100

Where:

  • Robots — number of active robots
  • Operating hours — scheduled hours per robot in the chosen period
  • Minutes per task — average complete task cycle time
  • Utilization — share of scheduled time spent productively completing tasks

Assumptions: Every robot is modeled with the same average cycle time and utilization. The estimate does not model queueing, traffic interactions, task mix, charging schedules, or downtime separately.

What the result means

Under these average assumptions, the fleet can complete about 1,152 tasks during the selected operating period.

Capacity is an average throughput estimate, not a queueing or dispatch simulation.

Given:

  • 12 robots
  • 16 operating hours per robot
  • 8 minutes per task
  • 80% productive utilization

Calculation:
Theoretical capacity = 12 × 16 × 60 ÷ 8 = 1,440 tasks
Estimated capacity = 1,440 × 0.80 = 1,152 tasks

Result:
1,152 tasks

Interpretation:
Under these average assumptions, the fleet can complete about 1,152 tasks during the selected operating period.

Should I use scheduled hours or actual productive hours?

Enter scheduled operating hours and use the utilization field to reduce them to productive time. If your hours are already measured as productive task time, set utilization to 100% to avoid double-counting losses.

What should be included in average task time?

Use the full repeatable cycle that limits throughput, such as travel, pickup, processing, drop-off, and ordinary repositioning. Excluding routine components can overstate capacity.

Why might real throughput be lower than the estimate?

Congestion, uneven task locations, charging constraints, failures, operator delays, and peak demand can all reduce realized throughput. Treat the result as an average planning capacity rather than a guaranteed service level.

Can this estimate mixed task types?

Yes, if you first calculate a weighted-average task duration based on the expected task mix. For highly variable tasks, separate scenario calculations usually give a clearer range.

How can I use the result for fleet planning?

Compare estimated capacity with expected demand for the same period. A persistent shortfall can indicate a need for more robots, shorter task cycles, higher availability, or process changes.