1. Could have
1.1. Mobile APP
1.1.1. offline
1.1.2. situation information
1.1.3. wake up feature (alerts)
1.2. ICCS Ad-Ons
1.3. Volunteer management
1.4. Services
1.4.1. Contractors
1.5. Missing Persons Registry
1.5.1. tourism
1.5.2. track loved ones
2. Should NOT have
2.1. duplication
2.2. complicated
2.3. irrelevant information
2.4. crash when overloaded
2.5. social use
2.6. changes often
3. Must have
3.1. incident reporting
3.1.1. payments
3.1.1.1. budget
3.1.1.2. settlements
3.1.1.3. procurements
3.1.1.4. MOUs
3.1.2. requests
3.1.2.1. resources
3.1.2.1.1. assets
3.1.2.1.2. goods
3.1.2.2. within incidents
3.1.3. reporting
3.1.3.1. situational-reports
3.1.3.1.1. field-observation
3.1.3.1.2. casualty-illness
3.1.3.1.3. completion
3.1.3.1.4. postmotem
3.1.3.1.5. summary
3.1.3.2. statistics
3.1.3.2.1. silver
3.1.3.2.2. gold
3.1.3.2.3. platimum
3.1.4. notifications
3.1.4.1. alert responders
3.1.4.1.1. email
3.1.4.1.2. SMS
3.1.4.2. push messaging
3.1.5. MACS
3.1.5.1. multi-agency
3.1.5.1.1. emergency medicine
3.1.5.1.2. police, law enforcement
3.1.5.1.3. red cross society
3.1.5.1.4. fire, search n rescue
3.1.5.2. coordination
3.1.5.3. data sharing
3.1.5.4. common operating picture
3.2. usability
3.2.1. user friendly
3.2.2. easily customizable
3.2.2.1. coding by Sahana
3.2.2.2. build report & forms
3.2.2.3. SLA for ad-hoc devs
3.3. implementation
3.3.1. owned & operated by local Org
3.3.2. organizational administrators
3.3.3. zero down time (MTTF=0)
3.3.4. integrity & conitnuity
3.3.4.1. Gov Privacy Act
3.3.5. languages
3.3.5.1. Creole
3.3.5.2. English
3.3.6. Use codes
3.3.6.1. incidents