The Autonomous Mobile Robot Task Capacity Estimator estimates how many repeatable missions an AMR fleet can complete during a day. It combines robot count, average tasks completed per robot-hour, productive hours, and expected utilization to produce an operational throughput estimate that can be compared directly with planned workload.
This is useful when a facility already has a proposed fleet size and wants to test whether that fleet can support material moves, deliveries, inspection rounds, or another consistent mission type. The task-rate input should be based on complete missions and should reflect representative travel distance and handling time. Utilization then reduces the theoretical maximum for normal idle periods, traffic, dispatch gaps, and other losses. The model does not simulate route conflicts or time-of-day queues, so it is most useful for rough capacity planning, scenario comparison, and a cross-check against more detailed fleet simulations.
AMR throughput inputs
robots
tasks/hr
hr/day
%
Result
—
Estimated tasks per day
Capacity per AMR—
Effective fleet rate—
Theoretical capacity at 100%—
1. Enter the AMR count Use the number of robots expected to be available for the task.
2. Set completed tasks per hour Use an average rate based on complete missions, not individual travel legs unless that is your defined task.
3. Enter productive daily hours Use hours in which each AMR can perform the counted work.
4. Apply expected utilization Reduce theoretical throughput for typical idle time, dispatch delay, congestion, and operational losses.
5. Review estimated capacity Compare the daily task result with forecast demand and test different fleet or utilization scenarios.
Daily task capacity = Number of AMRs × Tasks per AMR per hour × Productive hours per day × Utilization
Utilization is entered as a percentage and converted to a decimal. Theoretical 100% capacity is shown separately for comparison.
The model assumes one representative average task rate across the fleet and does not explicitly model route mix, congestion, charging queues, or task priority.
What the result means
The main result is the estimated number of completed AMR tasks the fleet can support per day under the selected utilization level.
If task durations vary widely or the system has pronounced hourly peaks, use measured mission data or simulation to validate the average-rate estimate.
Given
14 AMRs
8.5 tasks per AMR per hour
16 productive hours per day
80% utilization
Calculation 14 × 8.5 × 16 × 0.80 = 1,523.2 tasks per day
Result 1,523 tasks per day, approximately
The fleet can support roughly 1,523 complete tasks on a day that matches these average assumptions.
What should I use for tasks per hour?
Use a measured or engineered average for complete missions that resemble the work being planned. A rate from short, easy routes can overstate capacity if the future route mix is longer or more complex.
Is utilization the same as robot availability?
Not exactly. Availability usually describes whether equipment is ready for service, while utilization describes how much of the available productive time is actually used for the counted work.
Should charging reduce the task rate, hours, or utilization?
Represent charging once in the model to avoid double counting. If the measured task rate already includes normal charging interruptions, do not necessarily subtract them again from productive hours.
Why does this estimate not round to whole tasks internally?
The calculation uses continuous average throughput so scenario comparisons remain smooth. The displayed total can be interpreted as an approximate whole-task capacity over the planning period.
When is fleet sizing more useful than task capacity?
Use fleet sizing when the required workload is fixed and the unknown is how many robots are needed. Use task capacity when robot count is already known and you want to estimate achievable throughput.