Planning priorities
Walk the actual operating route during acceptance
Poor Reception Behind Shelves or at the Ends of Aisles
Plan APs and suitable antenna orientation around rack layouts, stock heights and goods materials.
Reconnection while scanning on the move
Use the actual scanners to validate roaming between aisles and operational workflows; a phone alone is not a substitute.
Fully stocked results differ from an empty warehouse
Record stock conditions during testing and validate in a representative full-stock environment where necessary.
High Ceilings Make Maintenance Difficult
Consider mounting, cable lengths, power and access for future maintenance together.
A heat map is one reference; completing receiving, put-away, picking and dispatch workflows successfully is closer to actual operational needs.
What should be prepared before a survey?
These details make the discussion more specific. It is fine if some answers are unknown; mark them as ‘to be confirmed’ in the requirements summary.
- Shelf heights, aisle widths and floor plans
- Common goods materials, stacking methods and full-stock conditions
- Handheld client models and main movement routes
- Work-at-height restrictions, installation and maintenance arrangements
Acceptance should reflect actual use
Agree test clients, scope, applications and assessment criteria first, then record results and exceptions. Do not use one speed test to represent the entire site.
VALIDATION / FIELD NOTES
Choose an item to explore its test context
Select a card to see its illustration and observation points. Illustrations do not replace agreed test conditions.
Scanning and operational routes
Complete representative work routes with the specified scanning terminal
Racks and stock conditions
Review coverage and retries under the agreed stock conditions
Walking routes and reconnection
Check application continuity when moving between aisles
Site records and labels
Record antenna orientation, AP heights and cable labels
Observation points and illustrations
View illustrationScanning and operational routes
Scanning and operational routes
Complete representative work routes with the specified scanning terminal
How to observe
Use specified scanning clients to observe real applications along representative operational routes.
What to record
- Record problem locations during receiving, put-away, picking or dispatch steps.
- Record rack, stock and client conditions. This diagram is not a warehouse survey result.
View illustrationRacks and stock conditions
Racks and stock conditions
Review coverage and retries under the agreed stock conditions
How to observe
Observe specified areas under agreed stock conditions, distinguishing obstruction, coverage and retransmission issues.
What to record
- Record rack heights, stock materials and test positions to compare environmental changes.
- An empty warehouse does not represent a full warehouse. Ring sizes and packet motion are not measurements.
View illustrationWalking routes and reconnection
Walking routes and reconnection
Check application continuity when moving between aisles
How to observe
Use representative clients along an agreed route to observe connectivity and application behaviour while moving.
What to record
- Record where and when disconnections, reconnections or application interruptions occur, together with the client model.
- Clients and the network both affect roaming. The illustrated route does not guarantee seamless transitions.
View illustrationSite records and labels
Site records and labels
Record antenna orientation, AP heights and cable labels
How to observe
Cross-check agreed installation, cabling, configuration and test records so issues can be traced later.
What to record
- Check positions, orientations, heights, labels or power information as required by the project scope.
- Agree record types, formats and deliverables. The illustrated documents are conceptual.
Concept illustration, not a measurement, completed project or acceptance promise. Device counts, lines and ring sizes do not specify equipment configurations or coverage.
These are acceptance items for discussion, not contract deliverables already included or commitments about performance. Installation arrangements, local requirements and the actual service scope must be confirmed separately.
Questions Before Getting Started
Do I Need a Floor Plan Before Starting the Discussion?
A floor plan can help explain spaces, walls and usage locations. Without complete drawings, you can still outline the scenario, area, devices and problems. Confirm the receiving channel and sharing scope before sending any sensitive floor plans.
Can only selected areas be improved?
We can start with localised problems and existing equipment, but need to understand neighbouring APs, network segments, power and management arrangements to check compatibility with the existing environment. The project scope must be confirmed separately.
EXPLORE MORE SPACES