Every case is anchored to a physical component on the booth schematic — the AI drafts the
classification, a human confirms with one tap. Data writes to Firestore now, to the
mWater asset & case registry once migration lands.
📞 New case
📋 Case queue
🌐 Fleet view
Incoming case
✦ AI classification — draft
Issue type—
Subcategory—
Priority—
Component—
On-device classifier v0, trained on 6 years of hotline subcategories.
v1 swaps in Claude via Cloud Run — same interface, no UI change.
▲
A case cannot be filed until a component is anchored on the schematic.
Booth schematic — standard DWASA configuration
Healthy
Watch
Open case
One master schematic serves the whole DWASA fleet — component IDs map 1:1 to the mWater asset registry. Tap any component to anchor the case. The layout below is the real room behind it: every ATM sits inside a Dhaka WASA pump house, and no two pump houses are alike.
Component record
No component selected
Tap the schematic or run the AI draft
—
open · this booth
—
12 mo · this booth
—
90 d · fleet-wide
—
resolved same-day
Recent history — this component
No history yet for this component.
→ Firestore bt_cases · component pending