Difference between revisions of "Disaster tech support for NGOs"

From DevSummit
Jump to navigation Jump to search
Line 1: Line 1:
=Scenario:=
+
=Scenario Assumptions:=
  
* Earthquake, subsequent tsunami.
+
* Community-wide disaster (Earthquake, subsequent tsunami)- but not total devastation
* 5-10% of nonprofit org buildings collapse.  
+
* 5-10% of nonprofit org buildings collapse.
* Computer/technology/platform are down.
+
* Assume government resources are focused on gov't facilities
* Time period of 2nd day post crisis event through several weeks of recovery.
+
* Assume for-profit IT services are serving for profit businesses
* Not focused on preparation for orgs, instead focused on those who are not prepared.
+
* Computer/technology/platform are down at 300-600 non profit orgs
 +
 
 +
How can nonprofit sector (people) self-organize in an ad hoc way?
 +
 
 +
* Looking at day AFTER crisis through several weeks of recovery
 +
* Not focused on preparation, focused on recovery.
 
* Mobilizing those inclined and qualified to help.
 
* Mobilizing those inclined and qualified to help.
 +
 +
_Needs for Success_
 +
 +
* Means for gathering/listing orgs that need assistance (text based?/low bandwidth)
 +
* Means for finding/alerting/vetting(?) volunteer corps to assist nonprofits that are down
 +
* Triage process that works for volunteer lay-people, non-technical to
 +
  evaluate urgency cases.
 +
 +
 +
_Event Workflow:_
 +
 +
* OUTBOUND: who needs help
 +
* OUTBOUND: who can help
 +
* incoming requests for aid (provide location and best guess of need)
 +
* incoming offers to help (provide location and skills to offer)
 +
* go through triage matching process (below)
 +
 +
 +
_Triage Questions: Prioritization of Need_
 +
 +
(Automate triage questions if possible, Twillio, etc, have option to
 +
talk to people)
 +
 +
* Where are is the down technology/computer network?
 +
* Will lives be threatened if technology is not restored?
 +
* Power out? Internet out?
 +
* Damaged equipment? Type, how many, etc.
 +
* Building damaged/flooded/no access? Do you need to relocate?
 +
* Do you have other resources that can help you?
 +
* Are you the person normally in charge of this?
 +
    o Is there an IT person?
 +
    o Are they okay, can help?
 +
    o Can you get in touch with them to assess your needs?
 +
 +
 +
_ !!! IDEAS !!! _
 +
 +
* Build on existing ...
 +
* Coopt / adapt an existing platform that is up (assume electricity up, in general)
 +
  - Use a facebook page - rework 'I’m Safe feature'
 +
  - Make a google map with pins showing need
 +
  - Post needs on CraigsList in special category
 +
  - Other?: How would/could twitter, snap, instragram fit in.
 +
* Tech industry could set up platform something in advance (e.g., Zendesk, Salesforce)
 +
* Tech industry could set up employee 'community service' program in advance to allow employees to go out in their neighborhoods and help closest school, church, clinic
 +
 +
__ CHALLENGES __
 +
 +
* There are issues of liability, HIPAA data, etc.
 +
* NEED A ticket systems for assigning people are needed in order to avoid
 +
  duplication of efforts, appropriately escalate, indicate resolution.
  
 
=Needs for Success=
 
=Needs for Success=

Revision as of 16:38, 22 November 2017

Scenario Assumptions:

  • Community-wide disaster (Earthquake, subsequent tsunami)- but not total devastation
  • 5-10% of nonprofit org buildings collapse.
  • Assume government resources are focused on gov't facilities
  • Assume for-profit IT services are serving for profit businesses
  • Computer/technology/platform are down at 300-600 non profit orgs

How can nonprofit sector (people) self-organize in an ad hoc way?

  • Looking at day AFTER crisis through several weeks of recovery
  • Not focused on preparation, focused on recovery.
  • Mobilizing those inclined and qualified to help.

_Needs for Success_

* Means for gathering/listing orgs that need assistance (text based?/low bandwidth)
* Means for finding/alerting/vetting(?) volunteer corps to assist nonprofits that are down 
* Triage process that works for volunteer lay-people, non-technical to
  evaluate urgency cases.


_Event Workflow:_

* OUTBOUND: who needs help
* OUTBOUND: who can help
* incoming requests for aid (provide location and best guess of need)
* incoming offers to help (provide location and skills to offer)
* go through triage matching process (below)


_Triage Questions: Prioritization of Need_

(Automate triage questions if possible, Twillio, etc, have option to talk to people)

* Where are is the down technology/computer network?
* Will lives be threatened if technology is not restored?
* Power out? Internet out?
* Damaged equipment? Type, how many, etc.
* Building damaged/flooded/no access? Do you need to relocate?
* Do you have other resources that can help you?
* Are you the person normally in charge of this?
    o Is there an IT person?
    o Are they okay, can help?
    o Can you get in touch with them to assess your needs?


_ !!! IDEAS !!! _

* Build on existing ... 
* Coopt / adapt an existing platform that is up (assume electricity up, in general)
  - Use a facebook page - rework 'I’m Safe feature'
  - Make a google map with pins showing need
  - Post needs on CraigsList in special category
  - Other?: How would/could twitter, snap, instragram fit in. 
* Tech industry could set up platform something in advance (e.g., Zendesk, Salesforce)
* Tech industry could set up employee 'community service' program in advance to allow employees to go out in their neighborhoods and help closest school, church, clinic

__ CHALLENGES __

* There are issues of liability, HIPAA data, etc.
* NEED A ticket systems for assigning people are needed in order to avoid
  duplication of efforts, appropriately escalate, indicate resolution.

Needs for Success

  • Must work in low-bandwidth.
  • Must have non-internet or computer based resources (ex: laminated guides, etc).
  • Triage process that works for volunteer lay-people, non-technical to evaluate most urgent cases.

Event Workflow:

  • OUTBOUND: who needs help
  • OUTBOUND: who can help
  • incoming requests for aid
  • incoming offers to help
  • go through triage (below)

Triage Questions: Prioritization of Need

(Automate triage questions if possible, Twillio, etc, have option to talk to people)

  • Will lives be threatened if technology is not restored?
  • Power out? Internet out?
  • Damaged equipment? Type, how many, etc.
  • Building damaged/flooded/no access? Do you need to relocate?
  • Do you have other resources that can help you?
  • Are you the person normally in charge of this?
    • Is there an IT person?
    • Are they okay, can help?
    • Can you get in touch with them to assess your needs?

Considerations

  • This could be routed through tech industry orgs, building out their own versions of a disaster response program set up in advance of a crisis, and deploy technical employees to respond.
  • There are issues of liability, HIPAA data, etc.
  • Ticket systems for assigning people are needed in order to avoid duplication of efforts, appropriately escalate, indicate resolution.
  • Leverage existing frameworks and tools to achieve goals: A reworking of Facebook’s “I’m Safe feature, Google’s disaster/crisis maps, etc).