Planning priorities
Plan capacity around a whole class connecting together
Slower response when the whole class connects
Plan capacity around devices per class, applications and timing, and assess uplinks and internet connections.
Different identities need different permissions
Identify the resources accessible to staff, students, visitors and equipment, and assess authentication and separation methods.
Device Models Vary Widely
List representative clients and validate compatibility with bands, encryption and login workflows.
Installation only after school or during holidays
Stage cabling, installation, switchover and testing around the site's operating schedule.
User identity, content filtering and usage logs involve policy and privacy arrangements, which the institution must confirm separately under local requirements.
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.
- Classroom seating, concurrent devices and primary applications
- Floors, shared spaces and specified outdoor areas
- User roles, devices and access requirements
- Academic terms, training schedules and installation windows
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.
Classroom connectivity scenarios
Test concurrent connections under the agreed classroom scenarios
Login and access workflows
Validate login and usage workflows with representative devices
Access boundaries and separation
Check access restrictions for different roles and network segments
Management and handover responsibilities
Hand over administrative access, configuration backups and maintenance instructions
Observation points and illustrations
View illustrationClassroom connectivity scenarios
Classroom connectivity scenarios
Test concurrent connections under the agreed classroom scenarios
How to observe
Observe concurrent connectivity with representative devices and teaching applications in agreed classroom scenarios.
What to record
- Record student, teacher and teaching-device usage conditions, together with application requirements.
- Seat counts are not concurrent-device counts. Interpret results using actual devices and load conditions.
View illustrationLogin and access workflows
Login and access workflows
Validate login and usage workflows with representative devices
How to observe
Use agreed identities and representative devices to observe login, access and reconnection steps.
What to record
- Record login steps, reconnection behaviour and accessible resources.
- Check portals, identity services and network-segment policies together rather than signal alone.
View illustrationAccess boundaries and separation
Access boundaries and separation
Check access restrictions for different roles and network segments
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 illustrationManagement and handover responsibilities
Management and handover responsibilities
Hand over administrative access, configuration backups and maintenance instructions
How to observe
Check management access, configuration backups and follow-up arrangements against the agreed scope.
What to record
- Specify account ownership, backup methods, licensing information and contact arrangements.
- Agree maintenance scope, response times and site attendance separately. The illustration makes no service commitment.
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