Before you begin
Starting knowledge
- A repeatable single-robot task already works.
- Identify the operations owner and site constraints.
Equipment & environment
Use a test site or simulation first. Production rollout requires explicit site acceptance and stakeholder ownership.
No fixed completion time: use the evidence gates below to decide when to advance. Resource links open the botstest directory entry; check its publisher documentation for the exact version and configuration.
Beginner
Define a service unit and failure state
Know what one completed robot job means operationally.
Learn in this order
- Jobs, missions, handoffs and completion states
- Health signals and operator interventions
- Site constraints and manual fallback
Put it into practice
- Map one job from request to confirmed completion.
- Record normal, blocked and aborted jobs with reasons.
A mission-state map and baseline operations log.
Ready for the next step when…
Resources for this stage
Follow the official middleware learning path; use documentation matching your installed distribution.
Inspect recorded robot signals and build views that expose timing and system failures.
Investigate internal-transport AMRs, load carriers, top modules and handoff integration.
Intermediate
Plan fleet workload and observability
Understand capacity through real handoffs, not only motion speed.
Learn in this order
- Dispatch, contention and charging
- Structured event logs and diagnostic views
- Network loss and destination unavailability
Put it into practice
- Model jobs across a representative busy period.
- Test blocked destinations, charging conflicts and connectivity interruption in a controlled environment.
A capacity model, exception matrix and operations dashboard design.
Ready for the next step when…
Resources for this stage
Investigate a robot-data recording format and verify interoperability with your actual logging tools.
Visualize spatial observations and compare them with model and trajectory outputs.
Explore warehouse robotics and orchestration against a specific material-flow bottleneck.
Professional
Release and support changes deliberately
Keep the service recoverable as maps, software and hardware change.
Learn in this order
- Release gates, rollback and configuration inventory
- Monitoring, incident review and maintenance windows
- Support ownership and site expansion criteria
Put it into practice
- Rehearse rollout and restoration of a known-good release.
- Review incidents and define evidence required before adding another site.
A fleet operations manual and release/incident review pack.
Ready for the next step when…
Resources for this stage
Follow the official middleware learning path; use documentation matching your installed distribution.
Inspect recorded robot signals and build views that expose timing and system failures.
Investigate internal-transport AMRs, load carriers, top modules and handoff integration.
Common pitfalls
- Counting robot travel speed as service capacity.
- Expanding a fleet before measuring single-route exceptions.
Where to go next
Use the application-specific routes to define acceptance for each new site and task.
Explore other build paths →