Which differences matter to a laboratory project?
| Decision | Defined-route approach | More flexible route-planning approach |
|---|---|---|
| Route changes | Review what guidance or configuration must change. | Review remapping, permitted areas and approval of new routes. |
| Unexpected obstruction | Define stopping and operator recovery behavior. | Define whether an alternative route is allowed and when to stop. |
| Predictability | Check how fixed route occupancy affects other users. | Check how route selection and traffic rules affect repeatability. |
| Endpoint transfer | Needs a defined docking and handoff method. | Still needs a defined docking and handoff method. |
| Change management | Control route and station configuration. | Control maps, permissions, stations and software configuration. |
Is flexibility useful in this particular facility?
Consider a laboratory with a single permitted transfer corridor and strict access boundaries. Alternative routes may add little value if the approved path is blocked. In a different facility with several usable paths, route flexibility may help—but only if the alternative paths are approved for the load and operating conditions.
Ask for the actual behavior when a person stands in the corridor, a door is closed or another robot occupies the destination. “Obstacle avoidance” should not be used as shorthand for successful task recovery.
Does either label guarantee precise docking?
No. The final transfer depends on the workstation reference, carrier geometry and the handoff mechanism. Define where position is measured and which error matters to the task. A base stopping near a station and a mechanism aligning a rack are different requirements.
Request a demonstration or test plan that uses the intended load and station interface. Record arrival position, successful handoff and exception handling separately.
What should the facility survey include?
- Loaded robot envelope and the narrowest approved route.
- Door access, elevators, thresholds, slopes and floor transitions.
- People, trolleys, other vehicles and temporary route obstructions.
- Wireless coverage and behavior after a connection is lost.
- Charging locations and the effect of charging on mission availability.
- Who may change routes, maps and workstation definitions.
How can two navigation proposals be compared fairly?
Use the same representative load, permitted route and start and end conditions. Ask each supplier to identify setup work and restrictions before the trial. Record software configuration and facility conditions so a later result can be compared meaningfully. Compare loaded end-to-end cycles; an unloaded travel-speed figure answers a different question.
| Comparison item | Record under the same conditions | Decision supported |
|---|---|---|
| Normal transfer | Completed handoffs, elapsed time and any human intervention. | Whether the whole workflow meets the stated target. |
| An unavailable route segment | The specified waiting, rerouting or escalation response in an approved controlled scenario. | Whether the proposed behavior matches facility rules. |
| Destination occupied | Queue location, task status and how a task resumes. | Whether station availability has been included in capacity planning. |
| Layout change | The permitted change, required remapping or reconfiguration and who performs it. | Whether flexibility has a practical operational benefit. |
| Recovery | Trigger, authorized operator action and the resulting task record. | Whether interventions are understandable and traceable. |
Report the number of attempted and completed transfers as well as interventions. State why attempts were excluded, and examine typical and slow cycles rather than showing only the fastest journey. A simple throughput average can hide queueing at shared stations.
NIST’s navigation test demonstration illustrates evaluating a vehicle within defined spaces. Use it as measurement background; it does not establish performance for a laboratory installation.
What is included in each proposal?
Once the route trial is defined, compare the work included in each OEM proposal: base supply, carrier hardware, station interfaces, commissioning and support. Keep those items separate from measured transfer performance. This makes it easier to see whether a price difference comes from the hardware or an omitted work package.
We source the selected mobile base with its supplier system, manufacture the body and carrier hardware, and complete device connections, the platform interface and calibration. Your team connects its scheduling software. We record the base configuration so both teams can distinguish navigation settings from laboratory task scheduling.
Common questions
Is an AMR always the better choice?
No. Suitability depends on the permitted routes, handoff, environment and support requirements. Compare a defined workflow rather than a category name.
Can a fixed route still serve multiple instruments?
Yes, if the route and station arrangement support the intended task sequence. Endpoint interfaces still require definition.
Does a route-planning system remove the need for site testing?
No. Actual access, communications, station availability and recovery behavior need verification in the intended environment.
Is rerouting always preferable to waiting?
No. A facility may restrict alternate routes because of access control, process separation or other operating rules. Specify where rerouting is permitted and what happens when no permitted route is available.
Should price be compared before the site evaluation?
A preliminary comparison can be useful, but normalize the scope. Include route setup, station interfaces, required infrastructure, commissioning and support assumptions so a lower hardware price does not conceal a different delivery boundary.