+1 (978) 955-4300 · [email protected] EN · Fleet RFQ desk
AMR fleet site review and commissioning planning
Lifecycle engineering services

Locus Robotics defines the AMR handover before robots enter live aisles

Project support follows a visible chain from payload validation and route review through FAT, SAT, operator readiness and the post-handover recovery path.

Three controlled workstreams

Separate design inputs, delivery evidence and operating support

01

Application definition

We structure payload dimensions, maximum mass, aisle class, floor quality, SKU velocity, order profile, peak windows and required associate interaction rules. Site inputs cover charging power, network readiness, pedestrian crossings, dock interfaces and maintenance routes. The result is an assumption register, not a generic robot-count claim.

02

Delivery verification

Drawing and simulation review establish traffic rules, zone ownership and excluded areas. Factory acceptance covers functions that can be represented before shipment. Site acceptance adds installed geometry, safety fields, integrated WMS/WCS behavior and repeatable exception scenarios. Any test rate is recorded with the SKU/order profile and run duration.

03

Operational readiness

Handover packages identify inspection points, prohibited modifications, critical spares, isolation steps and escalation contacts. The responsibility matrix distinguishes WMS tasking, fleet orchestration, PLC safety chains and site network services. Recovery ownership is assigned before a live aisle blockage occurs.

Stage gates

A service path with evidence at each release

1

Input freeze

Issue the payload schedule, demand window and facility constraint register. Open items retain owners and due dates.

2

Concept review

Compare fleet size against aisle congestion, charging dwell, pedestrian rules and phased expansion without hiding dependencies.

3

Design release

Approve routes, safety fields, interfaces, control responsibility and acceptance scenarios for the live cutover plan.

4

FAT and SAT

Record test conditions, deviations, closure evidence and the installed baseline used for service support.

A FAT cannot prove site floor flatness, live Wi-Fi behavior or integrated upstream demand. A SAT cannot compensate for undefined operating data. Each gate therefore states what was tested, what remained outside the test boundary and which party owns the next verification.

Scope boundary

Availability is measured against an agreed fleet boundary

Fleet availability is meaningful only when planned maintenance, upstream starvation, downstream blocking, excluded utilities and operator intervention are classified. The agreement should also define the observation period and the event log used for review.

Included robots & docksExcluded causesResponse clockReturn-to-service evidence

Request a defined AMR service scope

Identify the installed assets, shift pattern, support window and present fault history. We will organize the information into a reviewable service boundary.

  • Robot and dock list with software baseline
  • Operating calendar and escalation coverage
  • Critical spares held on site
  • Remote-access and site-access conditions

Share the service baseline