CrisisCamp is June 12-14th in Washington, DC

CrisisCamp is an unconference to bring together domain experts, hackers, makers, developers, and first responders to improve technology and practice for humanitarian crisis management and disaster relief. This is the first event in what I hope will become a movement, and it's happening on June 12 - 14, 2009 in Washington, DC.

Across the world, everyday people can find themselves in crisis. Whether for a day, a month or a continued state of social distress, citizens across the world have common needs for communication. We want to connect with our loved ones to let them know that we are okay (or that we need help) and we crave information by which we make decisions within that time or place of crisis. We want to let people know they they are not alone, that people across the world care and seek to act act altruistically to provide resources to aid in the crisis recovery.

CrisisCamp seeks to break down the bifurcation between international and domestic humanitarian relief agencies and unite their efforts to share lessons learned, response tools, and expertise to encourage citizen engagement and use of information communications technologies (ICTs) to aid in crisis recovery, wherever people need help. We have great hopes that with a successful CrisisCamp, we can inspire a global effort to mitigate the potential impact of times or places of crisis on the human condition.

Crisis Camp seeks participation by anyone who wishes to help. We are especially interested in the use of ICTs in developing countries, especially in the areas of access, usability, and innovation. We seek to learn from academic findings on citizen participation, needs and problem solving efforts. In addition, we seek to understand global information needs through a consumer approach, because people will use what is available and familiar if a crisis event occurs. And finally, we want to know how ICTs, in all their uses, can help citizens of all abilities, recover during a time or place of crisis.

CrisisCamp Ignite! Session Kick Off

Time: Friday, June 12, 2009 from 7:30-9PM
Location: The World Bank,1818 H St., NW Washington D.C.
Participate: Sign up at CrisisCampIgnite (separate registration required for World Bank entry)

CrisisCamp - Saturday, June 13 & Sunday, June 14th

Start Time: 9:00am both days
Location: The Institute for Politics Democracy & the Internet @ George Washington University Participate: Sign up at CrisisCamp

DisasterTech: "Decisions for Heroes"

One of the most interesting DisasterTech projects I've been following is "Decisions for Heroes" led by developer and Irish Coast Guard volunteer Robin Blandford.

Decisions is like Basecamp for volunteer Search & Rescue teams. The focus is on providing "just enough" process to compliment the real-world workflow of a rescue team, without unnecessary complexity. One of Robin's design goals is that:

User requirements are nil. Nobody likes reading manuals - if we have to write one, we've gotten too complicated.

This is the winning approach for building systems that "serve those that serve others", and is echoed by InSTEDD's design philosophy and the Sahana disaster management system.

Teams begin by entering their responses to incidents and training exercises. They then tag them with things like the weather conditions, the tools and skills required, and who from the team was deployed.

As a team's incident database grows this information can be used to show heatmaps, and provide powerful insight on the locations, weather conditions, and times of year that various incidents occur. Over time this kind of data could be analyzed in aggregate across multiple teams and regions and create an incredibly powerful resource for Emergency Managers. This is very similar to what Wesabe does for consumers with financial transaction data today (disclosure: OATV investment).

Rescue team members enter training dates and levels. The system tracks certification expiration dates and prompts team members & leaders to plan classes and remain current. This is a huge issue for volunteers who have to manage professional-level training requirements with the demands of a regular career.

As more incidents are entered into the system, it compares the skills required for each of the rescues with the team training exercises. This allows teams to identify areas to focus, train, and develop new skills.

Today's ETech Hack is Tomorrow's Critical Infrastructure...

My friend Jordan Schwartz just gave me the perfect example of how quickly a cool hack can turn into Critical Infrastructure.  Jordan wrote "How to build an SMS Service" and created SwaggleSMS as a demonstration of how to do group chat with SMS.  It's a hack that he created as an experiment (it's super-useful for conference afterparty coordination).

Jordan and I were talking about some of the interesting ways that Twitter is being used by mainstream emergency management (see: FactoryJoe, Radar post).  Jordan then showed me a message he discovered while checking logs after an upgrade:

"Tom1132 to OurTownFD: Possible drowning in bay"

If it's not obvious... this is fire department who has apparently been using the service for a while.  It's a perfect example of how quickly a hack can become critical infrastructure without the creator knowing, let alone being prepared for it.  The picture to the right is the "Swaggleplex"... fully operational.

Mikel Maron and I are presenting at ETech on Disaster Tech: What's Working, What's next and we'll be diving into this and other examples of just how quickly the world is changing.