DDMS at Kanwar Yatra

As reported for Kanwar Yatra 2026, Muzaffarnagar deployed more than 4,000 police personnel across 9 super zones, 16 zones, and 230 sub-sectors, alongside specialist units, drone teams, and more than 2,500 planned AI-enabled cameras. More than 50 lakh Kanwariyas had passed through the district by 5 August. Rosters on paper and over the radio go stale within hours, so DDMS was deployed to answer one question continuously: is every duty point actually held right now?

In the field, DDMS ran as the duty layer behind the control room. Supervisors saw the current posting picture instead of calling down the chain. Officers received a clear assignment, relief teams inherited the same record, and an unauthorised departure raised an alert while the shift was still running. The control room could close a gap while it mattered, not discover it in a notebook after the route had moved on.

We built DDMS for the places where ordinary workforce software fails: long routes, overloaded networks, changing shifts, and officers who cannot stop to maintain a dashboard. Core field workflows keep working through low or no connectivity and reconcile when a link returns. The force can run it on sovereign or on-prem infrastructure, and every posting, relief, acknowledgement, and alert carries a reviewable audit trail from field device to control room.

Across a deployment of more than 4,000 personnel and 230 sub-sectors, DDMS turned a static roster into an operational loop. Field activity became visible to command, command decisions returned to the field, and the complete history remained available for handover and after-action review. That is the difference between documenting a plan and actively holding coverage.