Preparing the published article.
RFQ Guide: AMR Site Survey and Integration Inputs
Prepare AMR survey inputs for loads, routes, networks, handoffs and enterprise interfaces. Use an original editorial checklist to expose assumptions and make site integration proposals comparable.
Define what the survey must resolve
This original Zhilianhai editorial guide is a preparation checklist, not an issued RFQ or a completed engineering survey. Ask prospective AMR suppliers to explain whether the proposed load, route and handoff are feasible, which site changes are necessary and what remains uncertain. The deliverable should be a documented assessment with assumptions, rather than a demonstration alone.
State which building, zones and flows are included. Identify the operations contact and the people responsible for facilities, IT and integration. Agree how survey observations will be reviewed before a quotation is finalized.
Supply representative loads and handoffs
List every load family with dimensions, mass range, center of gravity information and packaging condition. Photograph pickup and delivery locations where authorized. Describe how loads arrive, how they are retained during travel and how the receiving process confirms completion.
The MiR250 range includes different handling add-ons. Request a drawing of the exact robot and load interface being proposed. Confirm compatibility with existing carts, shelves or stations instead of relying on a platform payload figure.
Empty and loaded carrier dimensions: to be measured.
Positioning tolerance and handoff height: to be confirmed.
Unavailable station and rejected load behavior: to be defined.
Survey routes under working conditions
Provide an annotated layout and visit routes during relevant operating periods. Ask the surveyor to record aisle restrictions, turning areas, floor joints, slopes, doors, lifts and mixed traffic. Distinguish permanent geometry from temporary storage or parked equipment.
Include charging, parking and maintenance access. Request evidence for the selected configuration's ability to operate within the observed conditions. Record any route changes, access controls or housekeeping dependencies that the proposal requires, together with their responsible owners.
Normal and peak traffic windows.
Restricted areas and shared crossings.
Alternative routes and approved recovery locations.
Define mission and software interfaces
Describe the full job lifecycle: request, eligibility check, assignment, pickup, delivery and confirmation. MiR Fleet documents task coordination and enterprise integration. Ask which software edition and deployment arrangement the respondent proposes, with responsibilities for hosting and support.
MiR's integration training outline includes REST communication. Request interface definitions covering identifiers, status updates, authentication, timeouts and repeated messages. Agree how duplicate delivery requests and interrupted confirmations will be detected during integration testing.
Request a testable findings report
The survey response should identify each assumption as verified, provisional or unresolved. Require supporting measurements, proposed modifications and the effect of remaining unknowns on cost, schedule or performance estimates. Ask the supplier to distinguish observed facts from simulated or estimated capacity.
Agree a later acceptance plan using representative loads, traffic and handoff conditions. Include recovery from approved exception scenarios, network interruptions and unavailable destinations under a reviewed test procedure. Report completed jobs, waiting and interventions with an explicit measurement period.
Turn findings into quotation boundaries
Request separate prices for survey work, site modifications, hardware, handling equipment, integration, software and support. Identify whether pilot equipment and temporary interfaces can be reused in a wider deployment. Assign an owner to every action required before installation.
Keep a revision record when layouts, loads or interfaces change. Use Write a Robotics Buyer Brief for the initial scope, the internal logistics pilot brief for trial gates and Robotics RFQ for related guidance. Editorial review: 10 September 2026.