Planning priorities
Assess busy periods before deciding capacity
A Full Meeting Room Slows the Network
First distinguish bottlenecks in wireless capacity, Internet bandwidth, conferencing platforms and wired uplinks, rather than relying only on extra APs.
Unstable calls while moving
Test roaming routes with the actual laptops and phones, examining neighbouring AP coverage, authentication and client support.
Visitors and company devices share access
Separate the access needs of staff, visitors and meeting equipment when planning subnets and access policies.
Existing Locations No Longer Suit a Refurbished Site
Update floor plans, wall and ceiling information, then reassess AP placement, cabling and PoE power.
Meeting-room seat counts are not the same as simultaneous device counts; one person may use a computer and phone together, so estimate according to actual applications.
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.
- Seats in each meeting room and busy-period occupancy
- Video meetings, cloud desktops or large-file transfer requirements
- Connection methods for staff devices, meeting systems and visitors
- Installation windows and relocation / refurbishment schedules
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.
Meeting-room devices and applications
Test connections in meeting rooms using the specified devices and applications
Walking routes and reconnection
Test calls, roaming and reconnection along everyday movement routes
Access boundaries and separation
Check that guests cannot access specified internal resources
Site records and labels
Record AP locations, cable labels and the handover of administrative access
Observation points and illustrations
View illustrationMeeting-room devices and applications
Meeting-room devices and applications
Test connections in meeting rooms using the specified devices and applications
How to observe
Observe connectivity with agreed devices and meeting applications at specified positions and under agreed test conditions.
What to record
- Record devices, applications, positions and the current load so the conditions can be reproduced.
- Distinguish wireless, uplink, internet and application-service effects rather than relying on one speed test.
View illustrationWalking routes and reconnection
Walking routes and reconnection
Test calls, roaming and reconnection along everyday movement routes
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 illustrationAccess boundaries and separation
Access boundaries and separation
Check that guests cannot access specified internal resources
How to observe
Check permitted and restricted resource access for agreed identities and network segments.
What to record
- Specify both permitted and denied scenarios; record target resources and the identity used for each test.
- Different Wi-Fi names do not establish isolation, and this illustration is not a security certification.
View illustrationSite records and labels
Site records and labels
Record AP locations, cable labels and the handover of administrative access
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