Command Center

Choose where to send limited patrol teams next under fixed capacity.

fallback
Untouched Holdout Result
Top-10 captured 52.2% more recorded obstruction burden than historical density allocation.
Same patrol capacity. Same official BTP records. Retrospective recorded obstruction burden only, not measured congestion reduction.

Marga Top-10

19.2%

Density Top-10

12.6%

Capacity

K = 10

Mode

Recorded burden

Next Two-Hour Shift
Marga helps the TMC officer decide where to send limited patrol teams next under fixed capacity.

Shift window

12:00 am - 2:00 am

Forecast window: 2024-04-09

Available teams

K = 10

Decision mode

Fallback snapshot

Forecast Mode

Toggles between live machine-learning inference and retrospective holdout replay for baseline comparisons.

Patrol Capacity (K)

Configures the number of top-priority enforcement cells to be active for dispatches, based on available patrol units.

Patrol Strategy

Focused strictly assigns cells by risk score. Discovery scatters selections to sample under-observed traffic lanes.
1

Select a Grid Cell

Click any 200m cell on the map or select a row in the ranked queue.

2

Assign Patrol Team

Select an available team and click Assign team.💡 Try Rank #2+ to test override audits.

3

Telegram Sync

Sync via Telegram bot @marga_patrol_bot to accept, arrive, and close.

Ranked dispatch queue
Priority-ranked
Default demo setting is Top 10, but K can be changed based on available patrol teams.
Selected zone
Explainable, assignment-ready, and scoped to the next two-hour shift.
Rank #1

BTP058 - Subbanna Junction

Upparpet | 6489_38789 | CAR

Priority score is shown as Enforcement Priority Score is a within-shift percentile rank, not measured congestion reduction.

Decision view

Priority score

100.0/100

Within-shift dispatch percentile

Marga currently ranks this grid #1 because it combines forecasted workload, obstruction impact, actionability, and repeating local patterns. The score is shown as Enforcement Priority Score is a within-shift percentile rank, not measured congestion reduction..

Forecast confidence

98%

Expected actionable

9.84

Forecasted violation workload

14.1

Obstruction impact proxy

0.410

Why this zone?

  • high forecasted violation workload
  • recurring historical pattern

Assign team

Patrol strategy: Focused enforcement.

Officer brief

Priority score: 100.0/100 (Enforcement Priority Score is a within-shift percentile rank, not measured congestion reduction.). High predicted parking-violation activity in the next shift, repeated activity in similar time windows, and enough recent official records to keep confidence high.

Active assignments
Priority generated, team assigned, officer outcome recorded, dashboard updated, feedback stored.
No active assignments yet.
Feedback-ready learning loop
Priority generated, team assigned, officer action captured, and outcome retained for future validation.

Leakage-safe design

3 temporal folds plus untouched 28-day holdout

Proxy boundary

Recorded obstruction burden only. No measured congestion reduction claim.

Closed loop

Dispatch, officer outcome, cancellation, reset, and human override all preserved.

Ask AI