Runtime is not the same as efficiency
Saying that a robot operates for a certain number of hours on a full charge describes its runtime, not how much energy it needs to complete a task. Two machines may run for the same length of time yet consume different amounts if their batteries have different capacities. They may also consume the same amount while covering different distances or moving different loads. Without knowing the task and the energy used, operating time alone does not show which one is more efficient.
This distinction matters because duration by itself says nothing about the service delivered in return for the energy. A robot might remain switched on while doing little work, moving slowly or waiting; another might complete more work in less time. A runtime figure without context does not distinguish between those situations. It is best read as a description of how long a robot can operate under certain conditions, not as a direct measure of efficiency.
For comparison, it helps to distinguish quantities. Power, expressed in watts, indicates the rate at which energy is transferred or consumed at a given moment; energy, usually expressed in watt-hours or kilowatt-hours, accumulates consumption over a period or cycle. A momentary power reading is no substitute for recording energy over a mission. The practical question is not just “How long does it last?” but “How much energy does it need to perform a defined task?” What matters is relating energy used to work the robot actually completes. These distinctions are a guide to interpreting figures, not a test method validated by the available sources.
A useful metric must include the work performed
Energy per distance—for example, watt-hours per metre or kilometre—can be useful when comparing equivalent routes. But a robot carrying a load does not necessarily provide the same service as one running empty, and distance travelled alone does not capture stops, manoeuvres or waiting. For repetitive operations, energy per completed task might describe the service better: for example, per delivery or per cycle, provided the task is defined comparably.
For that unit to be meaningful, the definition of “task” must be specific. If a cycle includes picking up, transporting and delivering a load in one case, but only transporting it in another, the figures do not represent the same work. It may also be necessary to clarify which route forms part of the cycle and when it is considered complete. A per-task unit does not remove the need to describe the test; it helps connect consumption to a defined operational result.
No single unit resolves every comparison. The choice depends on the function: energy per distance can make journeys easier to interpret, while energy per task may better represent a particular logistics operation. These are comparison frameworks, not guaranteed results or rankings. Total mission energy and the rate of completed tasks may also be useful, but they should be read together: optimising one without reporting the other could give an incomplete picture. These are proposed here as ways to request and organise data, not as metrics supported by a verified standard.
The environment and operating pattern should be part of the comparison
The sources available for this review do not include a verifiable primary study measuring how a Mecanum mobile robot’s consumption varies between environments or operating patterns. It is therefore not possible to attribute a particular magnitude to the research located or to present such variation as a finding established in this article. In practice, buyers and integrators can ask for the surface, route, payload and operating pattern to be documented; without comparable results, this article cannot quantify their effects.
This limitation also applies to test recommendations. A value obtained in one scenario should not automatically be transferred to another if conditions change, but the evidence located does not make it possible to measure how much it would change or determine which factors matter most. A useful data sheet should state the scenario and the conditions under which the figure was obtained, making clear what was measured and what was outside the measurement. This is an editorial proposal for transparency, not a requirement attributed to a standard.
The draft mentioned a paper titled Energy Modeling and Power Measurement for Mobile Robots and a test with a four-wheel Mecanum robot. That study is not among the sources verified for this review, so those specific claims have been removed. Without a verifiable reference, this article also cannot substantiate which components that model included or what experimental conclusions it reached.
What the located documentation allows us to conclude
The source package includes a review on microrobots and nanorobots in medicine, but its subject does not make it evidence about AMR energy consumption. It also includes a study whose title refers to AI performance test methods for autonomous mobile service robots. The title identifies the announced subject, but does not demonstrate that the study defines methods for measuring energy. Neither reference should be presented as an energy protocol or used to validate watt-hour comparisons between robots.
The research provided also does not include a verifiable ISO fiche on ISO/DTS 25213 or documents on consumption measurement methods for six-axis articulated robots. The draft’s claim assigning that document a specific scope and development status has therefore been removed. Without the corresponding source, this article cannot establish what it regulates, which category it covers or whether a final version exists.
The verified sources available are mostly unrelated to the specific question of measuring AMR consumption or address robotics in general. They are insufficient to determine whether a standard, industry protocol or published test method exists that can specifically compare their energy consumption. The conclusion must be limited: this review has not verified an applicable common method. That does not show that no such method exists; it means that the documentation available for this revision does not allow us to confirm one.
What data to request from manufacturers and integrators
A comparable technical data sheet should report the energy consumed during a defined test and explain how it was obtained. At a minimum, ask for the payload, distance or task, speed or operating pattern, surface type and relevant route conditions. It should also clarify whether the figure applies to the robot while moving, a complete mission or a period that includes waiting and stops. Without this information, an isolated figure can look precise while offering little help with a decision.
Describing the task and payload makes it possible to assess whether the test represents a service similar to the one being compared. Reporting the operating pattern and route helps show whether the machines were tested under equivalent demands. Stating whether waiting or stops are included clarifies what “complete mission” means in the published figure. The aim is not to demand a single figure suitable for every use, but for the manufacturer to explain what its reported value represents.
It is also useful to ask where the measurement is taken and which elements are included: the robot, sensors, onboard computer and, where applicable, charging equipment or associated infrastructure. Energy drawn from the battery should be distinguished from energy drawn from the grid to recharge it, as these may describe different system boundaries. These are editorial recommendations to make comparisons more transparent, not regulatory requirements that verified sources allow us to attribute to an AMR standard. Buyers and integrators can request this information and agree on a reference mission before comparing proposals.
A responsible comparison starts by stating its limits
For a purchasing decision, it may be useful to compare models under working conditions representative of the planned operation and record both consumption and task results. If two suppliers report runtimes but do not detail energy capacity, payload, route or method, those figures alone are not enough to infer relative efficiency. If both report energy per task, the comparison improves only if the task and its conditions are equivalent.
An agreed reference mission can help assess proposals using the same criteria. It should make it possible to identify the expected work and relevant conditions, as well as specify how energy is counted. Results from other scenarios can still be useful if presented separately. Choosing the same unit does not guarantee comparability: it is necessary to know what was measured, under what conditions and with what measurement boundary.
The conclusion these sources support is limited. Runtime alone does not describe the energy consumption associated with a task; to compare proposals, it is useful to know the measurement method and scenario. However, the research verified for this review does not allow us to claim that one metric is best for every AMR or that a universal protocol exists for this category. Until a verifiable common reference is available, publishing the method, measurement boundary and tested scenario is more informative than offering a figure without context.