Section 01
Problem Statement
On a congested site, a mixer arrives too early, trucks queue, and lay-down areas overflow. With only the phone's camera, GPS, barometer, and notifications, the team must build a mobile logistics control tower: forecast when a batch should leave the supplier; plan truck-arrival windows by checking the site's phone-reported readiness; track high-value materials by scanning the QR sticker on the delivery label plus the phone's location updates every 30 seconds; and use the phone's notification + map as the routing and alert surface. No RFID, no hardware, no beacons.
Section 02
Solution Requirements
Predictive material schedule on phone
Given a task list loaded from an in-app JSON/CSV schedule (e.g. "Pour slab Level 2 — day 45"), a lead-time database computes "order cement on Day 38" and shows it in an in-app calendar with a local reminder (AlarmManager).
QR / barcode material check-in
The driver scans a QR on the waybill (ML Kit BarcodeScanner) → status updates to "delivered to Zone 5, GPS (lat, lon)" on the web panel/Firebase; the worker confirms or rejects, triggering "site not ready" if a readiness checkbox is unticked.
On-site readiness gate
Before a truck is dispatched, the site engineer marks formwork-done / rebar-inspected flags on the phone; the app blocks dispatch on the driver's screen (status turns amber) until flags are set.
Dynamic slot assignment (solver)
Load 6 pending deliveries with truck GPS + site laydown capacity; solve with OR-Tools / CP-SAT (server-side allowed, phone just receives the plan) and push a time-slot schedule to the driver's phone with an in-app map.
Live truck tracking on phone map
The driver's phone location is polled via FusedLocationProvider (start/arrival taps, no background service); a map on the supervisor's phone shows the truck moving.
Cost / wait-time KPI dashboard
The phone view shows KPIs such as "Idle labor hours saved this week: 32h; truck queue reduced 48% vs last week" with a simple bar/pie chart.
Full offline mode
The QR scanner works without internet; location and check-in events queue to Firestore once connectivity returns.
Section 03
Expected Solution / Outcomes
- A paper waybill with a QR is scanned on a street or workshop and the "Delivered" stamp pops up.
- The engineer taps "not ready" and the driver's screen shows a red block.
- A map on the phone shows 2 moving blue-dot trucks driven from their real GPS.
- "Save 3.5h vs last week" is shown on the KPI dashboard.
- A QR scan in airplane mode is still logged to the local DB.
Section 04
Technology & Hardware Constraints
Data: Sample schedule CSV, laydown capacity data, waybill PDFs.
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)
"Blockchain-inspired provenance": each rebar bundle has a paper QR containing a SHA-256 hash of the mill certificate; scanning it loads the certificate PDF from app assets / Firebase storage.
Section 07
Deliverables
| Item | Format |
|---|---|
| Video Demo | ≤ 7 min, YouTube/Vimeo unlisted link. Must open with the phone alone on a table (no external hardware). |
| Field Trial Videos | (a) Outdoors, scan a QR printed on cardboard and show on-screen GPS. (b) A driver-like walk carrying a mock waybill from a laydown area, tracked live on the supervisor's map. |
| Demo Link | Android APK download link (installed on the reviewer's own phone) or a mobile-optimised web app URL. |
| GitHub | tracking_app/, solver/, waybill_generator/ (python script for sample QR waybills), README with sample CSV/schedule. |
| 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 outdoor QR scan of a printed waybill.
- Real driver-style walk tracked on a supervisor map.
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.