1. Disaster Management Information System

2. Me Name : Muhammad Helmi Zain Nuri, S.T., M.T.
Phone : (Whatsapp, Telegram)
YM :
Status: Married, One Wife and 4 Sons
Qualification : Programmer, Network Designer, Project Manager, IT O&M, System Analyst, Solution Architect.
Hobbies: Listening Audiophile Music, Strategy Game, Coffee Lover, Photography, learning Hypnosis

3. Chief Operation Officer @ PT.SATNet
2008
Kuliah S2 ITB : Computer Engineering
1999
Teaching FoIT
2014
Development Manager PT. MSP
2002
Development PT. SATNet
2007
Head of Engineering and PT. IMS
2012
System Developer PT. MSP
2000
Development PT. SATNet
2006
Head of Information Technology Department UMY
2010
EE UMY
2004
1994
1997
2000
2003
2006
2009
2012
2014
Kuliah S1 TB : Electronic Engineering
1994
Lulus S.T. ITB
1999
Head of EE UMY
Okt 2007
Chief Technology PT. GreenLink
2010
IT Business PT. AsiaTeach
2011
Lulus M.T. ITB
2002
MSP
SATNet
Designing SIMLIK
Building DataCenter Ternate &
Developt MobileSolution for Suara Muhammadiyah

4. disaster

5. General Characteristics of Disasters
In general, disaster events will usually
be relatively unexpected
involve substantial distress and trauma
have a potentially overwhelming scale of effects
have a strong potential for becoming worse if there is no appropriate intervention.

6. The biggest problem for disaster managers to respond to disasters is quickly mobilizing equipments, human resources and critical supplies to the emergency spot.

7. When disasters strike:
Disaster managers needs lot of specialized equipments and skilled human resources for quick response.

8. When disasters strike:
Delay in response may result in increased loss of lives and livelihoods.

9. When disasters strike:
There is a lack of knowledge of whereabouts of these resources either in the neighboring District or State.

10. What is Disaster Management?
Preparedness -- activities prior to a disaster. Examples: preparedness plans; emergency exercises/training; warning systems.
Response -- activities during a disaster. Examples: public warning systems;
emergency operations; search and
rescue.
Recovery -- activities following a disaster. Examples: temporary housing; claims
processing and grants; long-term medical
care and counseling.
Mitigation - activities that reduce the effects of disasters. Examples: building codes and zoning; vulnerability analyses; public education.

11. Role of Information & Communication Technology in Disaster Management
To catalyze the process of preparedness, response and mitigation.
Providing access to vital information on Disaster preparedness to citizens.
GIS based decision support system for planning.
Designing early warning system.
Emergency communication for timely relief & response measures.
Building Knowledge Warehouses to facilitate planning and policy making.

12. Role of Disaster information system in various phases of Disaster Management
Risk & vulnerability identification
Preparedness for response & recovery
Database of existing skilled human & material resources for emergency response.
Database on human resources trained on various aspects of disaster management.
Develop preparedness plans based on risk, available skill & resources.
Converting Disaster Management plans into electronic documents for easy accessibility and easy updating.
Identify
Prepare
A database of past disasters effects to determine the risks in particular geographic location.
Zoning of hazards using GIS.
Validating the disaster history database with hazard maps and other external data for accuracy in risk assessment.
Prevent
Mitigation strategies and policies
Mitigation strategies, policies and legislation based on statistical facts & figures from various databases.
Development of a virtual knowledge net for creation of a network of institutions, developmental organizations and Government dept. for information sharing and preserving the research efforts.

13. Information systems framework for Disaster Management
Reducing disaster losses & conserving developmental gains
Planning & Policy decision for disaster preparedness & mitigation
Hazard mapping &
Vulnerability Assessment
Database of disaster history
for trend & pattern analysis
Database of disaster
management plan.
Awareness & training
materials
Inventory of legal,
techno legal, administrative
and institutional framework
Quick emergency response & recovery
Human & material response
resources database
Database of Infrastructure,
lifelines & critical facilities.
Database of trained human
resources.
Demographic information
GIS based information
system
Facilitating 1 1 2 2 3
elements 3 4 5 4 5
Knowledge base for disaster management

14. Information systems Architecture for Disaster Management

15. InaTEWS Data Flow

22. Tide monitoring

23. Geodetic GPS

24. GPS Network

25. Tsunami early Warning equipment

26. Indonesia Buoy Network

29. Utilizing and intergrating GIS technology In DMIS
Develop nature disaster GIS based on base map layers (administrative border, hydrography, transportation) and some disaster map layer (hazard map, historical landslide,...)

30. Geography Information System in Disaster Management
GIS allows disaster managers to quickly access and visually display critical information by location.
This information can be easily shared with disaster response personnel for the coordination and implementation of emergency efforts

31. GIS usage in Disaster Management
Pre disasters
Preparedness
Risk Analysis
Hazard zonation
Vulnerability mapping
Response planning
Spatial/ non-spatial database
Administrative boundaries(state, district, block/ taluka)
River network
Road network
Railway network
Airports
Prediction
Forecast Models (disaster wise)
Vigilance system (observation & warning)
Post Disasters
Relief
Disaster identification
Immediate response
Recovery
Rehabilitation
Impact study

34. What are the Challenges in Implementing IT Solutions for Disaster Management?

35. Getting people to use it is hard!
Challenges
Uncertain and changing conditions.
Communication Gap:
NPOs/Government  IT Providers
Limited time and resources
Technology is Easy
Getting people to use it is hard!

36. Implementing Information Management Systems
Think about:
Value
People
Locations
Activities
Inputs
Outputs
Existing Systems and Processes

37. The Sahana Project: What is it in a nutshell? Foundation Mission
Free and Open Source
Global Community Built
Disaster Management
RAD Platform
Foundation Mission
To save lives by providing information management solutions that enable organizations and communities to better prepare for and respond to disasters

38. Called Humanitarian-FOSS or H-FOSS
Why does Open Source make this better? This was a natural alignment to Humanitrian Values
Freely Available to deploy
No discrimination on access (Red Cross CC #2)
Ability to “leave technology behind” (RC CC #6)
Rapid customization to actual needs with code
L10N and integration (RC CC #5)
Building local capacities & self-reliance (RC CC #6)
Open system => Transparent and trustworthy
Better acceptance than “foreign” proprietary systems
Countries/NGOs can collaborate to develop
Get the best minds from the world to participate in building the software
This should be a global public good
Build on each others work by including it in project
Called Humanitarian-FOSS or H-FOSS

39. Typical Enterprise Software Disaster Management App
Slightly different design goals than what we were used to at the time
Typical Enterprise Software
Disaster Management App
Network
LAN/WAN connected high bandwidth expected
Intermittently connected, low bandwidth, most often WIFI
User Interface
Highly interactive, Chatty AJAX lookups, graphics rich and engaging
Low throughput, Simple, highly intuitive, low size graphics if any
Deployment
Designed for one particular deployment environment in Cloud or Data Center
Designed for any available environment from cloud, server, to portable app
Dependencies
Dependent on 3rd party internal and external web services
Minimize dependencies, and potential point of failure, caching when needed
Development
Well typed, compiled, security manager, clear interface definitions
Easy to pickup and dynamically modifiable scripting language

40. zone of trust (legislation)
Collaborative Virtual Helpdesk
zone of trust (legislation)

41. The Missing People Registry helps track and find missing, people
Tracking Missing People / Casualties
Shared Bulletin Board of lost / found
Computer based search heuristics
Tracking Family units
Analyzing networks of connections
The Missing People Registry helps track and find missing, people

42. Who is doing What, Where & When?
Registry of operating relief organizations
Coverage of Services
Self-Allocation and Reporting
Contact Information
The Organization Registry helps maintain data
(contact, services, region, etc) of organizations
groups and volunteers working in the disaster

43. Matching Aid to Ground Realities
Estimating Needs
Matching Aid to Ground Needs
Inventories/Catalog
Quantities
Expiration dates
Re-order levels
Tracking Allocation
The Request Management System tracks all requests and
helps match pledges for support, aid and supplies to fullfilment

44. Collaborative Situation Mapping
Collaborative Map of
Hazards / Incidents
Shelters (IDPs)
(field) Hospitals
Organizations
Responders
Stores
etc
The Shelter Registry helps track data on all
shelters setup following the Disaster

46. Learned how I.T. Fail in a disaster
Comms can be saturated or not accessible
Systems have to be able to work disconnected
User familiarity can be low
Systems has to be as intuitive as possible
Data centers can get impacted
Systems have to be resilient (simple), mobile and self-sufficient
Functionality can be inadequate
System has to be quickly customizable

47. Sahana consists of several modules
Situation Mapping - Allows you to locate activities on a map providing current situation awareness.
Missing Person Registry - Helps to report and search missing person.
Disaster Victim Registry - Traces internally displaced people (IDPs a sort of refugee) and their needs.
Organization Registry - Lists 'who is doing what & where'. Allows relief agencies to self organize the activities rendering fine coordination among them.
Request/Aid Management - Tracks requests for aid and matches them against donors who have pledged aid.
Shelter Registry - Tracks the location, distribution, capacity and breakdown of victims in shelter.

48. Sahana consists of several modules
Downer - Effectively and efficiently manage relief aid, enables transfer of inventory items to different inventories and notify when items are required to refill.
Messaging Module - Allows communication by and SMS text messaging to groups.
Volunteer Management - Allows managing volunteers by capturing their skills, availability and allocation.
Reporting System - Allows system to generate reports based on sahana database. It aggregates all the module reports in one place for making easier the user to view, search reports and charts.
User Preferences - Allows you to set any preferred configuration. Which will help you to customize Sahana to your preference.
Administration - Allows you to configure and customize Sahana based on your requirements.

49. Sahana integration Modul Project

50. Beneficiaries of DMIS ONE action plan SAVE money
Store data and map in database
SAVE time
Response activity for disaster event will be delivered quicker
SAVE lives?

51. TERIMA KASIH THANK YOU MATUR NUWUN
The journey of a thousand miles begins with one step.
Lao Tzu
THANK YOU
TERIMA KASIH
MATUR NUWUN
Creativity 3C
Communication
Continuous Change

54. Methods Tools People Probabilistic Analysis Hazard & Exposure
Risk & loss analysis
Methods
Data repositories
GIS & Visualization
Maps & Applications
Tools
Open architecture
User communities
Multi-platform / API
People

56. “Sahana” – Relief in Sinhalese Rapidly custom build for SL Gov to handle Tsunami
Software
Rapidly Builds
CNO Urgent
Requirements
Sahana Phase I
Sri Lankan IT Community =
LSF/LKLUG + SL IT Industry + Academia

57. LSF Team = FOSS Geeks on Fellowships
Sahana Generic Platform Rebuild A generic disaster management platform
A Global Need (2005)
Builds and Donates
Tsunami
Requirements
LSF
Team
(+ SIDA)
Sahana
Software
Sahana Phase II
LSF Team = FOSS Geeks on Fellowships