Real-Time Analytics & Crew Telemetry

Live Telemetry Feeds

• GPS updates from mobile and vehicle gateways (5–60s cadence)
• State changes synced to workflow: dispatch → en-route → on-site → completed
• Photo & form payloads geotagged with AI auto-labels (damage class, confidence)
• Comms acknowledgements (SMS/Slack) to verify dispatch receipt and arrival

All streams land in the events bus and are persisted to MySQL for analytics and audit.

Operational KPIs (live)

• Coverage ratio: active crews ÷ assigned incidents
• Median response time: dispatch → arrival (en_route_started → arrived_at)
• Median repair time: arrival → completion (arrived_at → completed_at)
• Backlog aging: 50/95th percentile by severity and district
• Velocity: incidents closed/hour and day-over-day trend
• SLA compliance: by owner, contract, and vendor

Examples of Derived Metrics

• Route efficiency: shortest feasible path vs. actual trail; idle/dwell penalties
• Hotspot detection: clusters of severe incidents without nearby crews
• Vendor scorecards: response and resolution SLAs by subcontractor
• Risk overlays: NOAA radar, flood polygons, wildfire hotspots relative to crew locations

These analytics sit on top of the same geo schema as mapping: each crew ping and incident is a feature with timestamps.

Data Flow (High Level)

1. Ingest: mobile/vehicle GPS, incident updates, photos/forms, partner feeds
2. Normalize: ETL to unified geo schema (.lat/.lng, timestamps, state)
3. Analyze: rolling windows for KPIs (MTTA/MTTR, velocity, utilization)
4. Visualize: Mapbox layers + live dashboards for execs & dispatch
5. Act: auto-dispatch or re-route based on priority and proximity

• Real-time dashboards (role-based)
• CSV / PDF exports for regulators & ICs
• Webhooks for downstream systems (OMS, ETR portals)

Need a sample export or regulator-ready report format? We can enable read-only access or schedule automated deliveries.