Prepare
Personnel readiness, role requirements, posts, sectors, and command constraints are settled before a single order is drafted.
Flagship operational product · Dynamic Duty Management System
DDMS
Deployment discipline for complex public safety operations.
We build DDMS, we deploy it, and we upgrade it alongside the departments that run it. One system carries personnel readiness, roster planning, duty orders, field acknowledgement, live command, and deployment review. It has been in departmental service for more than five years.
5+ yearsin departmental service, upgraded continuously
Offline-firstfield operation where connectivity is intermittent or absent
In the fieldShri Amarnath Ji Yatra operations and Bareilly district work
Duty management is not calendar scheduling. It is the controlled allocation of trained people against geography, risk, availability, fatigue, equipment, and command intent. We built DDMS for that problem and we maintain it as institutional infrastructure, with more than five years of upgrades shaped by the departments that use it every day.
Paper to live command
See the duty picture change.
Move the divider from a duty room built around registers and pinned sheets to one live board for rosters, coverage, and acknowledgement.
The operating picture
From assignment to the control room.
These diagrams show how DDMS holds the same duty record in the field and at command. They are explanatory pictures, not a live dashboard.
01 · How it works
Prepare, allocate, command, account.
Four stages, one operating record. Every duty moves from plan to relief without leaving the system, and nothing depends on a register that only one person can read.
Allocate
The duty plan is built and reviewed against skills, availability, rest intervals, workload, and operational priority.
Command
Orders go out with an owner attached, acknowledgements come back, substitutions are handled, and command holds a live picture.
Account
The final roster, exceptions, approvals, and attendance stay on the record for supervision and after-action review.
02 · Capabilities
Deployment discipline end to end.
Unified personnel record
Rank, unit, skills, training, availability, restrictions, and service context in one authorised view, so allocation starts from facts instead of memory.
Deployment planning
Duties built against posts, sectors, shifts, role requirements, and operational priority, for routine days and for event-scale operations alike.
Readiness and fatigue checks
Availability conflicts, excessive duty, missing qualifications, and coverage gaps surface before orders are issued, not after a shift fails.
Duty orders
Every order carries the assignment, reporting point, shift, supervisor, and acknowledgement status, and it reaches the officer who has to act on it.
Live command view
Planned, acknowledged, reported, relieved, and exception states tracked across the whole operation from one command surface.
After-action record
Substitutions, delays, absences, handoffs, and command changes can be read back against the final deployment, each entry timestamped.
03 · What changes
From the duty register to the duty record.
Most departments still run deployment on paper registers, spreadsheets, and message groups. This is what each part of the job looks like on either side of that change.
| Operational task | Registers and spreadsheets | With DDMS |
|---|---|---|
| Roster preparation | Built by hand each cycle, checked against whatever the planner remembers. | Drafted against skills, leave, duty limits, and rotation, then put to a supervisor for review. |
| Issuing orders | Circulated on paper, by phone, and through message groups. | Issued to the named officer with post, shift, reporting point, and supervisor attached. |
| Acknowledgement | Assumed once the order has been sent. | Recorded the moment the officer accepts the order. |
| Substitutions | Agreed informally between officers and rarely written down. | Logged with the authority who approved it, the reason, and the time. |
| Rest and fatigue | Visible only to whoever is holding the register. | Checked against duty limits and rest intervals before the order goes out. |
| Weak connectivity | Updates stop when the signal stops. | Field nodes keep working offline and reconcile with command on reconnect. |
| Exceptions | Surface after the shift, if they surface at all. | Flagged to command while the shift is still running. |
| After-action review | Reconstructed from scattered paper and personal recollection. | Read straight off the deployment record. |
04 · Roster intelligence
AI-assisted scheduling, under human authority.
Roster preparation that used to take hours of register work becomes a review task. DDMS drafts the allocation against force size, skill tags, leave status, duty limits, mandatory rest, and fair rotation, then hands the supervisor a plan with the conflicts already flagged.
Command keeps full override. Every override, substitution, and approval is written down with a timestamp and the authority behind it, so who is deployed where is a matter of record, and an unaccounted absence is visible instead of quietly absorbed.
- Skill and role match
- Rest interval and duty limits
- Leave and availability status
- Fatigue and rotation equity
- Supervisory approval
05 · Offline and edge
Built for the network you actually have.
Duty does not pause when the signal drops. DDMS field nodes hold structured records locally, queue updates, and synchronise the moment any path back to command appears. Acknowledgements, reports, and exceptions reconcile instead of disappearing.
We proved this in the field. The same offline-first architecture carried Trinetra through Shri Amarnath Ji Yatra operations, where a mobile workforce reported across high-altitude corridors with intermittent signal and long stretches of none.
06 · Command view
Five states. One truthful picture.
Command dashboards follow every duty through an explicit lifecycle. Supervisors see coverage, acknowledgement, and exceptions across sectors as they happen, not at the end of the shift.
Planned
The duty exists in the approved plan, with its post, shift, and role requirement.
Acknowledged
The assigned officer has received the order and accepted it, on the record.
Reported
Presence at the reporting point is confirmed and visible to command.
Relieved
Handover is complete and the next assignment holds the post.
Exception
An absence, delay, or substitution is raised for supervisory action rather than lost.
07 · Deployment record
In production, on the record.
DDMS is not a pilot. It runs in live police operations, from a national pilgrimage corridor to everyday district duty.
Trinetra · J&K Police
Shri Amarnath Ji Yatra
DDMS deployed for personnel discipline and multi-zone coordination at corridor scale, with offline field nodes and auditable duty records under constrained connectivity.
Read the deployment recordBareilly · District operationsBareilly Police and Traffic Police
Duty allocation, personnel visibility, and supervisory coordination on one shared operational record, in place of fragmented registers and message threads in daily district work.
Read the deployment note08 · Upgrade path
Five plus years of upgrades, and counting.
Institutions do not buy software once, they live with it. We maintain DDMS as long-term infrastructure: we carry the engineering, departments carry only the operation.
The register becomes a record
We replaced manual duty registers and spreadsheet rosters with one current, defensible deployment record for the department.
Orders reach the workforce
We moved duty orders, acknowledgement, and reporting onto mobile devices in the hands of a distributed field workforce.
Connectivity stops being a precondition
We built offline-first field nodes with local records and reconciliation, and hardened them during Trinetra operations on high-altitude Yatra routes.
Allocation gets assistance
We added AI-assisted scheduling that drafts constraint-checked rosters for supervisory review, with human authority over every issued order.
Co-evolution with departments
Every operational season returns requirements to our engineering team. We upgrade DDMS rather than replace it, so departments carry no migration burden.
Departmental evaluation
Bring deployment discipline to your department.
A briefing covers your duty environment, hierarchy, connectivity conditions, and the configuration and upgrade path we would follow in your context.