Section 01
Problem Statement
A modular building needs its grid, connections, transport, and crane plan checked by a site engineer on the walk-around. The phone can drive an AR + parametric viewer (.glb in three.js/Filament), and the team prints a paper plan — the only printable output is the phone's PDF export — so the worker can assemble modules from paper/cardboard on a real table, an assembly validation checked by an AR marker. No 3D printing required. The phone can also use ARCore Spatial Anchors for a crane path on real ground.
Section 02
Solution Requirements
Phone parametric module-split generator
Select a room layout from presets, or draw on paper and capture it with ML Kit DocumentScanner to extract wall/boundary polygons; split into 2.4×4m modules (Shapely server or on-phone geometry) and display a grid in the three.js viewer.
Transport-envelope check
For each 2.4×12×2.8m module, the Maps SDK computes truck-route clearance from a road/bridge-height DB; modules over-height are flagged red with an alert such as "3.2m clearance — your 3.4m module cannot pass."
Connection detailing viewer
Tapping a joint on the three.js viewer opens a 2D connection SVG (bolt pocket, shear stud, connector) with a short spec text.
ARCore crane sequence validation
On real open ground, an ARCore anchor placed on the ground shows the next module as a ghost; the worker places a printed marker and the app checks the placement order via ARCore hit-test, displaying total on-site assembly time.
Structural feasibility check
The module is sent to a lightweight solver (Firebase function / Retrofit call); the phone shows the pass/fail result and load.
Cost / handover export
Compute prefab vs. traditional cost, waste %, and speed gain (e.g. "prefab 85K; traditional 125K; 40% faster") and export a PDF BOM + JSON handover package.
Section 03
Expected Solution / Outcomes
- The app shows modules split from a drawn/selected layout.
- A transport alert is visible for an over-height module.
- Tapping a joint shows the connection detail.
- In a parking lot, AR shows the next ghosted module and a printed cardboard marker is placed correctly (or flagged as wrong order).
- A handover PDF opens on the phone.
Section 04
Technology & Hardware Constraints
Section 05
Scoring
Requirements Completeness
50
Each requirement (R-id) is worth 3–12 marks. A hard-coded or mocked claim earns 0 — only working code counts.
Presentation & Demo
50
3-slide pitch + video ≤ 7 min + live demo. Judges must understand the problem in ≤ 90 seconds.
Real-world Implementation & Feasibility
50
Would a PM, engineer, or worker install this with only a phone on Day 1 of the next project? Must work offline and cheaply. Field-trial videos prove real-environment execution (20+ pts of this score is the field video).
Innovation & Disruption
50
A novel fusion of phone sensors (e.g. IMU + camera + barometer = scaffold-instability detector) is rewarded over simple API-calling. Re-skinning an existing SaaS scores low.
Section 06
Bonus (+10)
Material-aware splitting: CLT vs. steel produces different module dimensions and joints, with AR showing the corresponding CLT joint instead.
Section 07
Deliverables
| Item | Format |
|---|---|
| Video Demo | ≤ 7 min showing the paper split, AR walk, and cost. |
| Field Trial Videos | (a) Real AR ground walk in an outdoor space. (b) A real cardboard 3×3 module grid assembled from the app's paper plan, photographed as "as-built" vs. design. |
| Demo Link | Android APK download link (installed on the reviewer's own phone) or a mobile-optimised web app URL. |
| GitHub | module_splitter/, route_validator/, arcore_assembly/, handover/, cost_engine/. |
| Pitch Deck | 3-slide PDF (Problem → Solution → Field-Proof & Impact). |
| Technical Brief | 2-page PDF: architecture diagram, phone-sensor map, tech stack, limitations, PRIVACY.md. |
Section 08
Field-Trial Requirements
- Real AR ground-walk crane sequence demo.
- Real cardboard module assembly checked against the design.
Section 09
Privacy Requirements
Any human face captured in a field video must be consented or blurred. A PRIVACY.md file is required in every repository.