Crowds, Clouds and Crisis

586 views

Published on

A presentation given in Taiwan to the Association of Digital Culture (www.adct.org.tw) about how social computing is changing the way disaster information management will be done.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
586
On SlideShare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
12
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

Crowds, Clouds and Crisis

  1. 1. Disaster Social Computing<br />Crowds, Clouds and Crisis<br />Gísli Ólafsson<br />Disaster Management – Technical Advisor<br />Microsoft Corporation<br />Email: gislio@microsoft.com<br />Blog:http://blogs.msdn.com/disaster/<br />Twitter: @gislio<br />
  2. 2. Introduction<br />The Crowds<br />The Clouds<br />Way Forward<br />Agenda<br />
  3. 3. Port-au-Prince<br />Haiti – January 12, 2010<br />
  4. 4. Social Media<br />
  5. 5. Facebook – Hotel Montana<br />
  6. 6. Open Street Maps<br />
  7. 7. Project 4636<br />
  8. 8. CrisisCamp Haiti<br />
  9. 9. CrisisCamp Haiti<br />
  10. 10. Information Management<br />
  11. 11. Coordination on the ground<br />
  12. 12. Information Management – on the ground<br />
  13. 13. Big World – Small World<br />
  14. 14. The Crowds<br />
  15. 15. What are the issues and limitations?<br />Information silos<br />Time zone differences<br />Organizational boundaries<br />Information capture/persistence<br />Lack of efficiency/delays<br />Version control issues<br />Security violations<br />Access issues<br />Etc.<br />Consumersocialnetworks<br />Phone<br />How People Work Together Now<br />E-mail<br />Fax<br />Face-to-face<br />Messaging<br />File shares<br />Paper-based<br />
  16. 16. Organizations 2.0<br />
  17. 17. Mobilizing<br />
  18. 18. Facilitated<br />Knowledge Management<br />Collaborative<br />Workgroups<br />Social<br />Networks<br />Evolution<br />
  19. 19. Discussion Boards<br />Comments<br />Podcasting<br />Shared Calendars<br />Microblogging<br />Versioning<br />Profiles<br />Document Libraries<br />Team Sites<br />Tags<br />Blogs<br />Task Lists<br />Wikis<br />Surveys<br />Ratings<br />EnterpriseCollaboration<br />Capabilities<br />SocialComputing<br />Technologies<br />DisasterCommunities<br />The Need for Communities<br />
  20. 20. <ul><li>Team Sites
  21. 21. Blogs, Wikis, Podcasts
  22. 22. Tag Profile Pages</li></ul>SHARE<br />CREATE<br /><ul><li>Office Client Co-Authoring
  23. 23. Enterprise Wikis
  24. 24. Mobile Access
  25. 25. Rich Media Support
  26. 26. SharePoint Workspace Offline access
  27. 27. Team Sites
  28. 28. Outlook Synch & Social Connector
  29. 29. Ratings
  30. 30. External Access
  31. 31. Note Board
  32. 32. Office Web Apps</li></ul>SharePoint 2010 Communities Platform<br /><ul><li>Social Bookmarks
  33. 33. Ask Me About, Colleague & Expertise Suggestions
  34. 34. Microblogging Status Updates
  35. 35. People & Expertise Search
  36. 36. Organization Browser</li></ul>NETWORK<br />FIND<br /><ul><li>Social & Taxonomy Tags
  37. 37. My Network, My Profile
  38. 38. Activity Feeds
  39. 39. Photos, Contact Card, Presence everywhere
  40. 40. Notifications & Alerts</li></li></ul><li>The Cloud<br />
  41. 41. <ul><li>On and off workloads (e.g. batch job)
  42. 42. Over provisioned capacity is wasted
  43. 43. Time to market can be cumbersome
  44. 44. Successful services needs to grow/scale
  45. 45. Keeping up w/growth is big IT challenge
  46. 46. Complex lead time for deployment</li></ul>“On and Off “<br />“Growing Fast“ <br />Inactivity<br />Period <br />Compute <br />Compute <br />Average Usage<br />Usage<br />Average<br />Time <br />Time <br /><ul><li>Services with micro seasonality trends
  47. 47. Peaks due to periodic increased demand
  48. 48. IT complexity and wasted capacity
  49. 49. Unexpected/unplanned peak in demand
  50. 50. Sudden spike impacts performance
  51. 51. Can’t over provision for extreme cases </li></ul>“Unpredictable Bursting“ <br />“Predictable Bursting“ <br />Optimal Cloud Workload Patterns<br />Compute <br />Compute <br />Average Usage<br />Average Usage<br />Time <br />Time <br />
  52. 52. Mechanical Turks<br />
  53. 53. Translation Frameworks<br />
  54. 54. Swift River<br />
  55. 55. The Way Forward<br />
  56. 56. The crowd and cloud based crisis informationmanagement has to be a joint effort wherewe combine multiple technologies to solve the issues ahead.<br />A Common Cause<br />
  57. 57. Grassroot Effort<br />
  58. 58. Private Sector Support<br />
  59. 59. International Community<br />
  60. 60. Loss of Control<br />
  61. 61. Loss of Personal Value<br />
  62. 62. Confusion<br />
  63. 63. Governance Policies<br />
  64. 64. Legal, Compliance & Security<br />
  65. 65. Breaking Convention<br />
  66. 66. Phased Approach<br />
  67. 67. <ul><li>Twitter:
  68. 68. @gislio
  69. 69. @DavidClinchNews
  70. 70. @poplifegirl
  71. 71. @patrickmeier
  72. 72. @whiteafrican
  73. 73. @edjez
  74. 74. @andrejverity
  75. 75. @crisismappers
  76. 76. @crisiscamp
  77. 77. @ushahidi</li></ul>Websites/Blogs:<br /><ul><li>http://blogs.msdn.com/disaster
  78. 78. http://crisiscamp.org/
  79. 79. http://www.rhok.org/
  80. 80. http://www.crisismappers.net/
  81. 81. http://ushahidi.org</li></ul>Further resources<br />
  82. 82. Source: xkcd, http://xkcd.com/386/<br />And Finally...<br />

×