| Business Fit |
Primary workflow |
High |
The cart should be designed for the intended task, such as material delivery, order picking, linen transport, food service, or warehouse replenishment. |
Provide the supplier with actual routes, load types, delivery frequency, elevator usage, door widths, floor surfaces, and peak-hour requirements. Request a workflow demonstration using comparable conditions. |
| Payload & Design |
Rated payload capacity |
High |
Select a rated capacity at least 20% above the normal operating load. Typical indoor carts are commonly specified in the approximately 50–300 kg range, depending on configuration. |
Check the technical datasheet for payload, shelf load, load-center assumptions, ramp limits, and whether the rating applies while the robot is moving or stationary. |
| Navigation |
Navigation method |
High |
Autonomous navigation should support the site layout without requiring permanent floor markers wherever possible. Common technologies include LiDAR-based mapping, visual navigation, or hybrid systems. |
Confirm performance near reflective surfaces, glass, changing lighting, temporary obstacles, crowded aisles, and frequently relocated equipment. |
| Navigation |
Positioning accuracy |
High |
For docking, handoff, or shelf alignment, request a repeatable stopping accuracy of approximately ±10–30 mm, subject to site conditions and the supplier's stated test method. |
Ask for a live docking test at the actual pickup and drop-off points. Confirm whether accuracy changes on slopes, uneven floors, or after route updates. |
| Capacity |
Battery runtime and charging |
High |
Plan for a full operating shift or use automatic opportunity charging. Lithium-ion battery systems commonly provide several hours of operation, but runtime varies significantly with payload, speed, and traffic. |
Request runtime data under your expected payload and duty cycle. Review charging time, charging location, battery replacement procedure, and whether the cart can resume work automatically. |
| Safety |
Obstacle detection and emergency controls |
High |
The cart should detect people and objects, reduce speed in shared areas, stop safely, and provide visible and audible status indicators. Safety functions should be independently testable. |
Conduct demonstrations with stationary and moving obstacles. Review risk assessments, emergency-stop locations, restart behavior, safety zones, and applicable local requirements. |
| Safety |
Human-robot interaction |
High |
Controls should be intuitive for non-technical staff, with clear indicators for loading, unloading, low battery, faults, and manual operation. |
Ask representative employees to complete basic tasks without training from the supplier. Measure the time needed to understand alerts and safely recover from a stopped-cart event. |
| Customization |
Cart body and payload interface |
High |
Available options may include shelves, bins, drawers, enclosed cabinets, trays, towing interfaces, conveyors, barcode readers, or temperature-controlled compartments. |
Request drawings showing usable dimensions, maximum shelf load, center of gravity, cleaning requirements, access height, and the impact of modifications on navigation and safety. |
| Customization |
Software and system integration |
High |
The solution should support documented APIs or standard interfaces for task dispatch, fleet management, warehouse systems, order systems, elevator controls, doors, and charging stations where required. |
Request API documentation, authentication details, event logs, integration responsibilities, test-environment access, and a written statement of included versus paid integration work. |
| Customization |
Site mapping and route changes |
Medium |
Operations staff should be able to update destinations, restricted areas, speed zones, and schedules without rebuilding the entire system. |
Ask who can edit maps, how changes are approved, whether remote support is required, and how the system handles temporary closures or construction areas. |
| Service Support |
Installation and commissioning |
High |
A complete deployment plan should include site survey, mapping, integration, safety validation, user training, acceptance testing, and documented handover. |
Require a project schedule with named deliverables, acceptance criteria, responsibilities, downtime assumptions, and escalation contacts. |
| Service Support |
Preventive maintenance |
Medium |
Maintenance should cover wheels, drive units, sensors, batteries, charging equipment, safety devices, software updates, and cleaning of sensor surfaces. |
Request the maintenance interval, expected service hours per year, spare-parts list, recommended stock levels, and whether technicians are locally available. |
| Service Support |
Remote monitoring and support |
High |
The support platform should provide fault alerts, battery status, mission history, utilization data, and diagnostic logs with role-based access. |
Review a sample dashboard and confirm support hours, response targets, remote-access controls, data ownership, and the process for resolving recurring faults. |
| Service Support |
Service-level agreement |
High |
The contract should define response time, restoration target, uptime measurement, replacement policy, planned maintenance windows, and remedies for repeated service failures. |
Compare the proposed service terms with the operational cost of downtime. Ensure uptime exclusions and customer obligations are clearly written. |
| Commercial |
Total cost of ownership |
High |
Evaluate purchase or lease price together with integration, installation, training, software subscriptions, batteries, maintenance, spare parts, connectivity, and end-of-life costs over a 3–5 year period. |
Request an itemized commercial proposal with one-time and recurring fees. Model costs for different fleet sizes, utilization levels, and expected downtime. |
| Commercial |
Pilot project structure |
High |
A pilot should run in the real operating environment for long enough to cover normal demand variation, with measurable targets for safety, successful missions, availability, labor impact, and user acceptance. |
Define baseline performance, pilot duration, test routes, pass/fail criteria, data access, training scope, and the conditions for scaling to additional carts. |
| Scalability |
Fleet management |
Medium |
The platform should support task prioritization, traffic management, charging coordination, user permissions, and expansion without requiring a separate control system for each cart. |
Ask the supplier to demonstrate fleet behavior with multiple simultaneous tasks, blocked routes, low-battery carts, and priority deliveries. |
| Data & Security |
Cybersecurity and data governance |
High |
The solution should use secure authentication, encrypted communications, controlled software updates, audit logs, backup procedures, and defined data retention rules. |
Request security documentation, vulnerability-management procedures, access-control details, incident-notification terms, hosting locations, and data-deletion procedures. |
| Usability |
Training and change management |
Medium |
Training should cover daily operation, loading, exception handling, emergency stops, cleaning, basic troubleshooting, and escalation procedures for supervisors and maintenance staff. |
Request training materials, competency checklists, refresher-training options, multilingual support, and the expected training time per employee. |
| Reliability |
Performance evidence |
High |
Suppliers should provide operating data from comparable environments, including mission-completion rate, availability, charging performance, incident frequency, and average recovery time. |
Ask for references from similar applications and permission to speak with current users. Distinguish measured field data from laboratory or marketing claims. |