One platform, because the failure is always at the seams
Disaster response rarely fails for want of effort. It fails at the joins — between the agency that knows where the casualties are and the one that holds the helicopters, between the clinic that treated someone and the hospital that receives them, between the funder who paid for a consignment and the community that never saw it arrive.
IIDAMS is built to close those joins. It is a single interoperable platform covering the whole response cycle: gathering and reconciling data, forecasting what comes next, allocating resources including air ambulances, managing aid requests through to confirmed receipt, and recording all of it in a form that can be audited afterwards.
It is organised as nine systems containing twenty-eight modules. That numbering is not a presentation device — it is the platform's own reference scheme, used in specification, procurement, training and support, and it is used consistently across this site.
The response chain
Every system on the platform sits at a stage of the same chain. The chain runs in one direction during a response and closes back on itself afterwards, because the accountability record from one event is the starting evidence for the next.
The nine systems
Architecture
The systems are layered rather than parallel. Intake feeds understanding, understanding feeds action, and assurance wraps all three — because security, accountability and integration are not a stage of the response, they are conditions on every stage of it.
Field modules queue locally, compress aggressively and reconcile on reconnection, with delivery state always visible. A platform that only works with good connectivity is a platform that stops working exactly when it is needed.
See how the systems are specified
Each of the twenty-eight modules has its own specification page covering purpose, capability and the systems it depends on.