Session by session
- Session 66 · Ask & understandWeek 33
Device, gateway and dashboard roles
Evidence: a question, sketch or new vocabulary
- Session 67 · Build & designWeek 34
Specify JSON messages and status fields
Evidence: a design draft, dataset or build
- Session 68 · ImplementWeek 34
Simulate a connection using local files/loopback
Evidence: a working version, explained once
- Session 69 · Test & improveWeek 35
Test missing data and reconnect rules
Evidence: a test log with at least one failure
- Session 70 · Explain & reflectWeek 35
Explain what extra hardware real IoT needs
Evidence: an individual explanation
- Computer
- UNO optional
- local JSON/CSV files
Five normal and five failure messages.
A physical circuit, sensor or mechanism, built and tested on the bench.
Completion needs the artefact, an honest test log, an individual explanation and no open safety or privacy issue.
Projects in the same block
- RoboticsG11-P13
Track Experiment Platform
A reproducible robotics experiment with a baseline and condition comparison.
Sessions 61-65Innovation only - RoboticsG11-P14
Connected-System Simulator
A local connected-system simulator; no claim of built-in UNO Wi-Fi.
Sessions 66-70Innovation only - AIG11-P15
Reusable AI Skill Evaluation
A documented reusable AI workflow; trainer installation only on an eligible approved workspace.
Sessions 71-75Innovation only - IntegratedG11-P16
Responsible Smart-Automation Capstone
A bounded AI-assisted line-following/automation study with reproducible evidence.
Sessions 76-80Innovation only
For school leadersChoose a starting point.
Build from evidence.
Pick the classes and a plan. We map the timetable, kit and safety checks with you, then pilot one class first.
- Prospectus and class-wise plan
- Kit and readiness check
- Pilot one class first
- Evidence at every milestone
Let's plan your pilot.
Share a few details and we will send the right plan for your classes.