How do you configure a school robotics lab?

The classic mistake with an equipment list is treating it as a purchase order instead of a teaching tool. The same money, allocated differently, produces wildly different utilisation three years later. Below is a three-tier configuration: what to buy in each layer, how much, the order to buy in, and what to postpone.

Three tiers: entry, standard, advanced

Tier	Terminals	Robot platforms	Sensors & kits	Platform & software	Curriculum & training
Entry (get classes running)	20-30 student machines + 1 teacher machine	Several desktop / entry-level units	Basic vision and sensor kits	Teaching management and simulation	Courseware + demo lessons + teacher training
Standard (projects and competitions)	As above, sized to the class	+1 showcase-grade unit (humanoid or quadruped)	Full sensor kits + data collection	Platform + model and data tooling	Grade-level course packs + competition coaching
Advanced (public showcase / industry-education)	As above + teacher prep machine	Multiple units + scenario equipment	Multimodal kits + interactive display	Platform + dashboards and operations	Full curriculum + open-day and showcase content

One principle governs the choice: first make sure every student gets hands-on time, then make sure you have one unit worth showing. Reverse it and you get an expensive unit surrounded by 30 spectators with zero hands-on time.

How much of each layer, and why

1. Student terminals

Size them to the class, not to the number of rooms. 20-30 student workstations is a normal reference. Terminals only need to run simulation and training comfortably — top specification is rarely worth it, and the budget is better spent on layer 2 and layer 5.

2. Robot platforms

• Desktop / entry-level: prioritise quantity so students can rotate through projects. Lower unit price, easy consumables.
• Showcase-grade (humanoid / quadruped): one is enough to start. Its job is public demonstration, competitions and "seeing the future" — not one per student.
• Arms and scenario equipment: choose by course direction; only needed when tied to workshop or line-simulation training.

3. Sensors and kits

Vision, voice, distance and environmental modules, plus cables, mounts and power supplies — the low-value consumables. This layer decides whether a course moves from demonstration to student projects, and it is the layer most often merged away.

4. Platform and software

Check four things: student accounts and progress tracking, simulation support, data and model tooling, and upgrade path. The worst outcome for a school is a platform frozen at the version you bought — two years later the course cannot be taught.

5. Curriculum and training

Courseware, demonstration lessons, teacher training, competition coaching. Without this layer the other four are idle assets.

Purchase order (this matters)

1. Platform + curriculum + teacher training (so teachers can teach)
2. Student terminals (the baseline)
3. Sensors and kits (so courses can go deeper)
4. Showcase-grade robot unit (results and public display)
5. Scenario and expansion equipment (training, competitions, industry-education)

Swapping steps 1 and 4 is the single most common way projects go wrong.

Four things not to buy yet

• High-specification kit with no courseware — impressive on paper, nobody knows how to teach it.
• Models whose spare parts cannot be sourced — one missing part can stall a whole lab.
• Every robot unit at once — if the timetable is not settled, buying early only means sitting idle early.
• Display equipment bought for the open day — without a course attached, it is used twice a year.

What we bring

Hengyu's tech-education practice spans 7 major categories with 25 leading brands supplied direct — hardware is never locked to a single brand, so one course can use the best combination rather than whatever one catalogue offers. Send us the grades, class size and course goals and we will come back with a configuration and budget at no cost.