Start with an operational question
An AMR pilot should answer a defined operational question. It is not simply a product demonstration inside a facility. A useful pilot connects one suitable material movement to clear site conditions, responsibilities and acceptance criteria.
The final scope depends on the selected vehicle, supplier configuration and verified site requirements. This guide provides a practical planning framework rather than a fixed commissioning procedure.
1. Define the operational problem
Document the load or pallet, pickup and delivery points, movement frequency, shifts, operating hours, interactions and the problem the pilot should evaluate. A narrowly defined, repeatable movement is easier to assess than a pilot attempting to automate an entire facility at once.
2. Confirm site readiness
Review floor condition, route width, turns, crossings, slopes, thresholds, pedestrian activity, forklift traffic, dust, liquids, debris, connectivity and charging location. Include the intended load when measuring routes and clearances. Assess realistic peak conditions—not only a quiet demonstration period.
3. Define the pilot boundary
Write down what is included
- Vehicle and approved load type
- Pickup and delivery points
- Route and operating area
- Charging approach and operating window
- Required equipment or system interfaces
- Manual fallback arrangements
- User and supervisor responsibilities
- Pilot duration and test schedule
Uncontrolled scope expansion makes results harder to interpret and can hide whether the original workflow was validated.
4. Assign owners and responsibilities
The customer and solution provider need named contacts for operational ownership, facility access, safety coordination, IT or system support, user training, daily checks, issue reporting and acceptance decisions. The pilot should have a decision-maker who can confirm priorities and approve the next stage.
5. Set measurable acceptance criteria
Acceptance criteria should describe what will be observed and how it will be assessed. Depending on the project, they may cover workflow completion, approved loads, route operation, repeatability at interfaces, agreed obstacle scenarios, charging behaviour, training, system communication and recorded interventions.
Targets must come from verified requirements. WFC should not promise generic throughput, uptime or return-on-investment figures without project evidence.
6. Test normal and exception conditions
The test plan should cover the intended workflow and realistic exceptions within the agreed scope, such as an occupied route, unavailable destination, interrupted task, low-battery condition or controlled manual intervention. Only approved and safely planned scenarios should be tested.
7. Record evidence and decisions
Maintain a test record containing the scenario, conditions, expected result, observed result, issue owner and decision. At completion, classify each criterion as met, not met or requiring further action. Record changes needed before rollout rather than relying on informal impressions.
8. Decide the next stage
A pilot can lead to refinement, additional testing, wider deployment planning or a decision not to proceed. The decision should be tied to evidence from the agreed workflow and site conditions.
WFC Systems can begin with an application discussion and site-readiness review before defining a suitable pilot scope.
Use the site-readiness guide →
Review the AMR deployment process →