What to bring to the review
- Robot type and operating task
- Motion and auxiliary load profile
- Payload and operating conditions
- Docking, swap or charging routine
- Host interface and fault behavior
- Battery access and service constraints
Explain a representative working shift
Break the task into movement, lifting or manipulation, waiting and charging. State which operations can happen together. Distinguish a representative cycle from an exceptional condition the design must still address.
Include non-motion loads such as computing, sensing and communications. Provide the host configuration behind any measurements so later hardware changes can be assessed against the same baseline.
Describe how the robot returns to work
Explain whether charging is manual, docked or based on a removable pack. Record connector access, charger constraints and the required host states during connection and disconnection. Do not reduce this discussion to a charging-time target alone.
- What tells the host that the battery is connected and ready?
- What should happen when a charge or protection event occurs?
- Who can remove or service the battery, and what access is available?
Agree on system-level evaluation
Bench evaluation and robot evaluation answer different questions. Define how a prototype will be assessed in the actual product, including startup, load transitions, charging and host responses.
If the robot has multiple variants, identify the common interfaces and the differences in payload, available space or operating duty. An interface that is stable across variants can be a useful design objective, but should not be assumed before review.