Spaces:
Running
Running
| # PotholeIQ — Client Demo: Questions & Inputs to Collect | |
| Use this during the session. ⭐ = blocker (get it or we can't deploy). 📥 = a file/credential to collect. ✅ = a decision to confirm. | |
| --- | |
| ## 1. Box Access & Authentication ⭐ (blocks everything — token expires every 60 min) | |
| - ⭐ Who is your Box **enterprise admin**? Can they **authorize a custom app**? (needed for permanent auth) | |
| - ✅ Auth method: **CCG** (admin authorizes once → permanent, recommended) or **OAuth** (one user login → 60-day)? | |
| - 📥 Box **Enterprise ID** + the **folder** to use (intake folder, case-root folder). | |
| - ✅ Which Box features are **enabled/licensed**: Relay (Automate), **Sign**, **Doc Gen**, **Forms**, **Apps** (custom dashboards)? | |
| - 📥 A **service/bot Box account** to run the integration as (so it's not tied to a person)? | |
| ## 2. City, GIS & Department | |
| - ✅ Confirm **city / jurisdiction** (demo = Philadelphia). | |
| - ⭐📥 GIS boundary files for **districts** and **maintenance/service zones** — not just wards. Format? (GeoJSON / Shapefile). *(Today we only have ward polygons and derive the rest.)* | |
| - 📥 Official **ward → district → maintenance-zone** mapping, if it exists. | |
| - 📥 **Department name + logo / letterhead** for documents (work order, review sheet, closeout). | |
| ## 3. Roles, People & Crew Dispatch | |
| - 📥 **Reviewers / district engineers / supervisors** — names + **Box account emails**. | |
| - ✅ Who **approves** a case, and who **dispatches** the crew? | |
| - ✅ How is the **crew chosen per pothole**? (we built: reviewer types the crew email at approval — confirm) | |
| - ✅ Are **crews Box users**, or external (email only — affects Sign vs notifications)? | |
| - ✅ Who gets **notified** at each stage (new case / approved / dispatched / resolved)? | |
| ## 4. Metadata Template & Fields | |
| - ✅ Confirm the **case fields + dropdown values**. Known quirks to fix or keep: | |
| - `weatherRisk` = **Low / Medium / Large** (no "High" — typo?) | |
| - `duplicateStatus` = `new / "duplicate " / pending` (**trailing space** on "duplicate") | |
| - `status` includes **`In progress`** (odd capitalization) | |
| - ✅ Any **additional fields** they track today (asset ID, 311 reference, etc.)? | |
| ## 5. Severity Scoring, SLA & Cost | |
| - ✅ Agree with the **severity factors** (prior reports, traffic/road class, damage/size, weather) and **weights**? | |
| - ✅ **SLA targets** by severity (e.g. Critical = N days)? → drives "target completion" + days-to-resolve. | |
| - 📥 **Actual repair-cost** figures by size? (we use researched estimates: Small ~$90–180, Medium ~$250–450, Large ~$450–800). | |
| ## 6. Forms & Documents | |
| - ✅ Confirm **citizen intake** fields and **crew closeout** form fields (current closeout: Case ID, Repair completed?, Method, Materials, Labor hours, After photo, Crew name, Crew contact). | |
| - ✅ Confirm **Work Order / Review Sheet / Closeout** layouts — fields to add/remove? | |
| - ✅ **Box Sign** — how many signatures and who? (we set crew + supervisor). | |
| ## 7. Duplicates, Data & Volume | |
| - ✅ **Duplicate radius** (we use 80 m) — confirm. | |
| - ✅ OK with an **external DB** (Supabase / PostGIS) for fast geo/duplicate search, or **all-in-Box** only? | |
| - 📥 **Historical case data** to import? | |
| - ✅ Expected **volume** (reports/day) — for sizing. | |
| ## 8. AI / Detection | |
| - ✅ Is the **open-source YOLO** pothole detector + size classification acceptable, or a specific accuracy bar / different model? | |
| - ✅ Size thresholds (Small/Medium/Large) — tune to their definition? | |
| ## 9. Deployment & Infra | |
| - ⭐ Where will the **backend + portal + dashboard** be hosted? **Domain/URL**? | |
| - ⭐ **HTTPS + public endpoint** for Box callbacks/forms — who provides it? | |
| - ✅ Weather: use **our OpenWeather key** or **theirs** (their account/limits)? | |
| - ✅ Who can access the **supervisor dashboard** (login list)? | |
| ## 10. The Big Decision — Architecture | |
| - ✅ Which model do they want? | |
| 1. **Fully inside Box** (Relay + Sign + Doc Gen + Apps) | |
| 2. **Box as storage only** (our portal + backend do the logic) | |
| 3. **Hybrid (recommended)** — backend does geo/scoring/duplicate/weather + AI; Box does content, workflow, docs, sign, dashboard, governance | |
| --- | |
| ### Fast "must-leave-with" list (the 5 that unblock everything) | |
| 1. ⭐ Admin to authorize the app (permanent auth) — or schedule it. | |
| 2. ⭐ District + maintenance-zone GIS data (or confirm we derive from ward). | |
| 3. ⭐ Hosting + HTTPS endpoint owner. | |
| 4. 📥 Reviewer/supervisor Box emails + department name/logo. | |
| 5. ✅ Architecture option (1 / 2 / 3). | |