This document discusses disaster social computing and how crowds, clouds, and crisis information are managed. It describes how social media was used to coordinate relief efforts in Haiti after the 2010 earthquake. It also discusses challenges like information silos and security issues that arise from crowdsourced information. Additionally, it outlines how cloud computing can help scale systems to handle unpredictable demand during disasters and explains potential solutions like mechanical turks and translation frameworks.

1. Disaster Social Computing Crowds, Clouds and Crisis Gísli Ólafsson Disaster Management – Technical Advisor Microsoft Corporation Email: gislio@microsoft.com Blog:http://blogs.msdn.com/disaster/ Twitter: @gislio

2. Introduction The Crowds The Clouds Way Forward Agenda

3. Port-au-Prince Haiti – January 12, 2010

4. Social Media

5. Facebook – Hotel Montana

6. Open Street Maps

7. Project 4636

8. CrisisCamp Haiti

9. CrisisCamp Haiti

10. Information Management

11. Coordination on the ground

12. Information Management – on the ground

13. Big World – Small World

14. The Crowds

15. What are the issues and limitations? Information silos Time zone differences Organizational boundaries Information capture/persistence Lack of efficiency/delays Version control issues Security violations Access issues Etc. Consumersocialnetworks Phone How People Work Together Now E-mail Fax Face-to-face Messaging File shares Paper-based

16. Organizations 2.0

17. Mobilizing

18. Facilitated Knowledge Management Collaborative Workgroups Social Networks Evolution

19. Discussion Boards Comments Podcasting Shared Calendars Microblogging Versioning Profiles Document Libraries Team Sites Tags Blogs Task Lists Wikis Surveys Ratings EnterpriseCollaboration Capabilities SocialComputing Technologies DisasterCommunities The Need for Communities

21. Blogs, Wikis, Podcasts

23. Enterprise Wikis

24. Mobile Access

25. Rich Media Support

26. SharePoint Workspace Offline access

27. Team Sites

28. Outlook Synch & Social Connector

29. Ratings

30. External Access

31. Note Board

33. Ask Me About, Colleague & Expertise Suggestions

34. Microblogging Status Updates

35. People & Expertise Search

37. My Network, My Profile

38. Activity Feeds

39. Photos, Contact Card, Presence everywhere

42. Over provisioned capacity is wasted

43. Time to market can be cumbersome

44. Successful services needs to grow/scale

45. Keeping up w/growth is big IT challenge

47. Peaks due to periodic increased demand

48. IT complexity and wasted capacity

49. Unexpected/unplanned peak in demand

50. Sudden spike impacts performance

51. Can’t over provision for extreme cases “Unpredictable Bursting“ “Predictable Bursting“ Optimal Cloud Workload Patterns Compute Compute Average Usage Average Usage Time Time

52. Mechanical Turks

53. Translation Frameworks

54. Swift River

55. The Way Forward

56. The crowd and cloud based crisis informationmanagement has to be a joint effort wherewe combine multiple technologies to solve the issues ahead. A Common Cause

57. Grassroot Effort

58. Private Sector Support

59. International Community

60. Loss of Control

61. Loss of Personal Value

62. Confusion

63. Governance Policies

64. Legal, Compliance & Security

65. Breaking Convention

66. Phased Approach

68. @gislio

69. @DavidClinchNews

70. @poplifegirl

71. @patrickmeier

72. @whiteafrican

73. @edjez

74. @andrejverity

75. @crisismappers

76. @crisiscamp

78. http://crisiscamp.org/

79. http://www.rhok.org/

80. http://www.crisismappers.net/

81. http://ushahidi.orgFurther resources

82. Source: xkcd, http://xkcd.com/386/ And Finally...