01
Context and challenge
Who the project serves, what problem is being addressed and which operational, educational or technical constraints matter.

Applied AI, robotics and education case portfolio
The cases below represent CIRC’s core delivery models across schools, student teams, enterprises, robotics development and international collaboration. Where a client or institution is not named, the case is presented as an anonymised project type or an implementation framework—not as a claim of a specific public commission or verified numerical impact.

Education
Enterprise AI
Robotics development
International collaboration
01 / How to read the cases
01
Who the project serves, what problem is being addressed and which operational, educational or technical constraints matter.
02
How discovery, programme design, development, testing, governance and capability building are combined.
03
The tangible artefacts and review methods used to show what was built, learned or validated.
04
The conditions required to refine, repeat, integrate or scale the project responsibly.
Case 01 / Primary education
A representative primary programme for pupils aged 7–11. Children design a robot or interactive model that supports a familiar classroom routine while learning that useful technology depends on clear instructions, testing and human responsibility.
Challenge
The programme needs to build confidence in coding and engineering without reducing learning to disconnected block-programming exercises.
Delivery
Pupils interview a classroom user, define a simple task, create a mechanism, program inputs and outputs and improve the design through repeated trials.
Evidence
Design sketches, annotated code, test records, pupil explanations and a user demonstration reveal both technical understanding and collaboration.
Result
The working prototype becomes evidence for sequencing, events, sensors, debugging, responsible decision-making and future robotics study.
Case 02 / Secondary education
A scalable secondary project in which student teams develop a rover for a model urban inspection task. The technical level can progress from fixed-route visual coding to Python, computer vision and autonomous navigation.
Challenge
Students may be able to make a robot move but need a structured route to requirements, system integration, repeatable testing and technical explanation.
Delivery
Product, software, hardware, data and test leads develop modules, maintain a shared plan and integrate against a common mission specification.
Evidence
Standard routes, altered lighting, obstacles, sensor noise and repeated trials reveal failure modes and the need for safe human intervention.
Result
Teams produce requirements, architecture, code, test data, risk controls, demonstration and reflection rather than only a finished vehicle.
Case 03 / High-school research
An advanced project for students aged 16–18. Teams build a bounded image-classification or detection pipeline and investigate dataset quality, model performance and the consequences of error.
Question
Students must decide which errors matter, whether the dataset represents the intended environment and when a human must review the output.
Method
Teams document data provenance, separate training and test data, control variables and compare model behaviour using suitable metrics.
Evidence
Confusion analysis and targeted out-of-condition tests examine lighting, viewpoint, background, class imbalance or other relevant limitations.
Result
Outputs can include a paper, model card, code repository, dataset documentation, demonstration and viva-style defence.
Case 04 / China · Enterprise AI enablement
An anonymised enterprise project type for organisations in China. The engagement identifies practical AI opportunities, selects a controlled use case and creates evidence for an informed implementation decision.
Challenge
Leaders need to distinguish useful workflows from high-risk, data-poor or weakly owned ideas before committing to a larger programme.
Delivery
Interviews and working sessions identify bottlenecks, source information, permissions, quality requirements and points where human judgement remains essential.
Prototype
A bounded proof of concept may support internal knowledge search, document analysis, content preparation, classification or workflow coordination.
Result
The organisation receives an opportunity map, prototype, user feedback, risk and governance actions, adoption needs and a defined next-stage plan.
Case 05 / China · Quadruped robotics
An anonymised development model in which a commercial quadruped platform is extended through software, sensors, interfaces and operating procedures for an education, inspection, demonstration or research scenario.
Challenge
The robot must operate against a clear mission, environment, payload, supervision and safety boundary rather than remain a generic technology demonstration.
Development
Supported SDKs and APIs connect movement, telemetry, task logic and appropriate perception modules through a documented architecture.
Validation
Simulation, bench tests and supervised field trials examine stability, latency, connection loss, obstacle response, battery limits and manual override.
Result
Outputs include modules, interface or dashboard, configuration records, safety procedures, test evidence, documentation and recommendations for iteration.
Case 06 / Student product development
A project-based learning model in which secondary or high-school students work as product teams to research, design, develop and demonstrate a mobile or web application.
Challenge
Students need to understand users, priorities, data, accessibility and testing—not simply add features or copy a tutorial.
Delivery
Product, UX, development, data and quality roles move through discovery, user stories, wireframes, build, testing and review.
Possible briefs
Themes can include campus services, learning support, sustainability, accessibility or multilingual community information.
Result
The portfolio contains research, backlog, prototype, code or build logic, test record, responsible-AI decisions, pitch and individual reflection.
Case 07 / International student teams
A feasible international project framework connecting two or more schools. Teams investigate an environmental issue locally using a common protocol, exchange evidence and develop context-sensitive AI, data or robotics proposals.
Challenge
Schools need comparable evidence and a shared purpose while preserving differences in climate, infrastructure, curriculum and student experience.
Delivery
Students investigate heat, air quality, energy, water or biodiversity and share approved data summaries, design reviews and questions.
Integration
Teams may produce a comparative dashboard, bilingual exhibition, technical briefing or combined showcase with clearly stated limitations.
Result
Assessment captures research quality, responsible data use, communication, response to peer feedback and understanding of context.
Case 08 / International robotics
An advanced collaboration model in which school teams develop compatible components or contextual variants for one robotics mission using common interfaces and acceptance tests.
Challenge
Students must create clear interfaces and documentation because collaborators cannot rely on informal, same-room problem solving.
Delivery
Partners may own navigation, perception, mapping, payload, operator interface or mission planning while maintaining a shared architecture.
Verification
One team attempts to reproduce, simulate or validate another team’s module using the supplied files, test cases and instructions.
Result
The final review shows what integrated successfully, which assumptions failed and how technical and cultural communication affected the system.
Case 09 / Applied international research
An illustrative future research framework—not a claim of a currently commissioned study. UK and Chinese schools, universities or research partners could investigate how student-designed intelligent systems support campus sustainability.
Research
Partners agree core measures and instruments while each site selects a meaningful issue and adapts delivery to curriculum, language and environment.
Technical work
Students or researchers develop sensors, data analysis, dashboards or robotic interventions and document model and measurement limitations.
Governance
Institutional review, participation, ownership, storage, access, transfer, intellectual property and publication arrangements are agreed in advance.
Potential outputs
Outputs could include comparative data, research papers, student portfolios, educator cases, prototypes and a joint bilingual briefing.
10 / Delivery framework
01
Define users, need, context, constraints, data, risks, ownership and measurable success.
02
Select a bounded scope, agree roles and architecture, establish responsible-use rules and plan evidence.
03
Build early, test important assumptions and make limitations visible before increasing complexity.
04
Review evidence, document the system, develop user or staff capability and define the next decision.
11 / Evidence standards
01
Outputs and evaluation connect directly to the original educational, user or operational need.
02
Requirements, decisions, versions, tests, feedback and changes show how the outcome was reached.
03
Failures, uncertainty, constraints and unresolved risks are reported rather than hidden behind a successful demonstration.
04
Quantitative outcomes are published only when the measure, sample, baseline and source can be explained.
12 / Ways to work with CIRC
Schools
Select an age-appropriate brief, delivery period, equipment level, assessment model and teacher-support package.
Companies
Begin with opportunity discovery and a bounded proof of concept before making a larger implementation commitment.
Partners
Co-design a challenge, student team, school connection or comparative research project with clear governance.
Networks
Establish common standards, local flexibility, facilitator development and an evidence framework for responsible scale.
Build the next programme
We can shape a class project, school pilot, international team or multi-school pathway around your learners.