One platform. Different roles. Shared responsibility.
DRMS 2.0 is designed to complement the existing disaster-management structure, not replace it. Citizens, families, NGOs, volunteers, city command centres, district authorities, state agencies and national institutions can participate through role-based access.
Citizen / Supported User
Preparedness guidance, verified warnings, location-aware support and emergency actions adapted to the person's needs.
Support Circle
Family, caregiver, neighbour or trusted person who can receive alerts, acknowledge requests and help coordinate assistance.
NGO / DPO / Volunteer
Verified organisations and field workers receive geography-scoped access to support-demand clusters, assigned cases and local resources.
City / Command & Control Centre
Authorised city teams can monitor incident summaries, heatmaps, assistance requests, responder status, shelters and support resources.
District Authority
District administration can coordinate across cities/blocks, approve operational access, monitor unresolved needs and mobilise response partners.
State / National Authorities
Aggregated dashboards can support oversight, multi-district coordination, preparedness, policy and integration with official systems.
Mutual data ecosystem
Government and institutions can contribute verified population, hazard, shelter, facility and resource data. DRMS returns structured operational intelligence about emerging support demand, response status and unresolved needs.
Sensitive information is never open by default.
Public
Aggregate community snapshots, approved resources and published stories only.
Verified NGO / DPO
Jurisdiction-level heatmaps, support-demand clusters and assigned operational cases.
Authorised Responder
Exact case location and minimum necessary assistance information only for legitimate active-response tasks.
Government / Command
Jurisdiction-based operational dashboards covering incidents, assignments, escalation, resources and aggregate population/support-needs intelligence.
DRMS Response Map
The map architecture combines verified hazard zones, aggregate support-needs clusters, live assistance requests, available responders, shelters, hospitals and critical support resources. Exact personal locations are revealed only to authorised roles where necessary for active response.
Every sensitive action should be auditable.
Production DRMS should log who accessed a case, when, under which organisation, what role they had and what action they took. Temporary emergency access can be granted by geography, hazard and time window, then expire automatically.
Configurable government integration
DRMS is designed as a global core with country and organisation configuration. For India, roles and jurisdictions can be aligned to national, state, district and city structures. Existing command-centre, GIS, warning, MIS or emergency-response systems can later connect through secure APIs, webhooks, structured data exchange or approved adapters, without requiring an authority to replace its current systems.
Other countries can use country-specific governance packs covering administrative hierarchy, agencies, languages, emergency numbers, alert sources, privacy rules and local workflows.