The document describes a proposed disaster management portal for the San Francisco Bay Area. It presents the portal in phases, with phase 1 including a dashboard widget that provides an overview of events and a toolbar for common tasks. The portal would feature home pages for blogs, notebooks, task lists, calendars, member lists, folders, and news feeds. It would allow users to create content, search the portal, and view layers on a map. Feedback is requested on improving access to disaster risk information and increasing capacity for analyzing disaster trends. The presentation was given by representatives from Collaborate.org to the Stanford University Venture Lab.

1. SF Bay Area Disaster Mgmt. Portal
(Phase 1)
Presented by:
Collaborate.org team
Kevin Montgomery
Jeff Schaffzin
Scott Schiro
Technology Entrepreneurship
Stanford University Venture Lab
7 November 2012

2. SF Bay Area Disaster Mgmt. Portal
Feature: Dashboard Calendar widget:
Provides overview
of
Portal description events, milestones,
etc. for current Toolbar that
month provides
commonly used
tasks
Meeting status:
Provides user to
access
teleconference, vid
eoconference
NOTE: Other widgets can be placed on dashboard – e.g. News Feeds,
Comments, etc.

3. SF Bay Area Disaster Mgmt. Portal
Feature: Toolbar
Create Content: Options include: Blog, Event, Task, Project, Folder, Reader Feed
Membership:
Search: Search for <value> anywhere in portal
NOTE: Icons on right are shortcuts to pages with content
From left to right:
Blog: Blog home page – create, read, comment on blogs related to portal
Notebook:
Task List: To do list
Calendar: Track events, milestones, other dates
Member List: Organize members
Folders: Store information similar to “Dropbox”
News Feeds: RSS feeds, tweets, etc.
Layers: Use to define layers that can be presented on map

4. SF Bay Area Disaster Mgmt. Portal
Blog Home Page

5. SF Bay Area Disaster Mgmt. Portal
Book Home Page

6. SF Bay Area Disaster Mgmt. Portal
Task List Home Page

7. SF Bay Area Disaster Mgmt. Portal
Calendar Home Page

8. SF Bay Area Disaster Mgmt. Portal
Members Home Page

9. SF Bay Area Disaster Mgmt. Portal
Folders Home Page

10. SF Bay Area Disaster Mgmt. Portal
News Feeds Home Page

11. SF Bay Area Disaster Mgmt. Portal
Layers Home Page

12. FEEDBACK SECTION

13. Scott’s Contacts
The main objective is Improving access to information on disaster risk and disaster risk
management. This includes the following intended outputs:
1. National Disaster Risk Management Portal established and made functional:
a) Information on different aspects of Disaster Risk Management delivered to development
planners and Disaster Risk Management practitioners.
b) Improved/updated disaster risk management plans at national, provincial and local levels.
c) 600 number of users across sectors/administrative levels of this information portal to be
achieved.
d) Linkages with the ongoing development information systems to be established.
2. Increased capacity for analyzing disaster trends and their application in decision-
making.
a) A pool of experts in place with ability to maintain inventories.
b) Disaster loss inventories established within relevant government departments.
c) Regular reports on disaster trends produced and applied for decision-making.

14. Scott’s Contacts
Requirements:
• Integrate the process of planning, coordinating and implementing relief measures during disasters.
• Collect and consolidate existing information on disaster risks through the portal
• Links local, intermediate, national and international partners in risk reduction
• Provide methods for members of the community to communicate and get key info out to members
• Information should be immediate and easy to digest
Concerns/Negatives:
• Too much information – needs to be clear on what info is required to prepare for disasters and to
coordinate and mobile resources during a disaster
• - If you have to wait for batch jobs to run to get the info required
• - System is not stable
Links:
• http://www.undp.org.ir/drm/EN/National_Disaster_Portal.asp
• http://www.disaster.qld.gov.au/dmportal/default.htm
• http://www.techrepublic.com/whitepapers/the-rescue-disaster-portal-for-disasters-and-
emergency-response/2518865

15. Jeff’s Contacts
Value Proposition:
• For residents of the San Francisco Bay Area, who need a reliable
source for emergency information, the SF Bay Area Disaster
Management Portal is a product/service that provides a
consolidated real-time resource for gathering and
sharing information and instructions for use by individuals, first
responders and other emergency personnel in a regional (city,
county, state-wide) emergency situation.
• Unlike the broadcast media (radio, TV, newspapers), our service
provides our consumers information that is most relevant to them
from a geographic, therapeutic or other perspective.

16. Jeff’s Contacts
Positives:
• Value proposition is sound -- very useful for people who don't plan ahead or are not given warning about
impending incident
• Great that information is consolidated in one place instead of having to use different apps to find info.
Negatives / Concerns:
• Data privacy -- what if I want to share some info, but not everything with group (can I have sub groups?)
Private/Public is not enough granularity
• Data reliability -- what's to ensure that the data does not go "stale"
• Scalability - will platform be able to handle large #s of users using it at same time
• Hardware support - web site does not seem to work on PCs with lower end graphics cards
• End users need to demand this product -- can't assume that government will be able to get people to
provide info, use the system, etc
• Performance - Portal needs to provide updated information very quickly (even with direct connection to
Internet w/Ethernet cable it's extremely slow)
• Feasibility - Will we be able to obtain all of this info? (I would imagine the answer is yes, but since it was
mentioned twice, I wanted to make sure I listed it)
• Cost - Who will pay for this?
• Would not be interested in buying products from portal - distracted from main purpose of application

17. Jeff Sources
• Dave Candee -- VP Operations – SecureALL
• Rick Schaffzin -- CEO of -- SecureALL / lead adjunct professor @ OMIS Dept, Santa
Clara University

18. Kevin’s Contacts
Main Requirements/Needs:
• Ability for general public to access information (anonymously, but also login)
– Disseminate preparatory information before event
– Rapid dissemination of information during event
– Ability to opt-in for email/txt-based information push
– Ability to enter information from citizens
• Location and capabilities of emergency/first responder equipment and personnel
– Ability to upload KML/KMZ/other data on locations
– Integration with existing location tracking system
– Integration with multi-level law enforcement
• Other data integration:
– Creek/flood monitors, air quality, earthquake information
– Fire cameras, traffic/street cameras, Radio/tv
• Ability to rapidly identify location and extent of damage
– Citizen reporting beats ‘dashboard survey’ approach
• Communications- ability to function even when traditional infrastructure (cell) is down
– Ubiquity of access, multiple methods for access
• Ability to share data and collaborate with individuals at local, state, federal level, including partner agencies
• Stability, broad use, accessibility, secure
• Multiple roles- authoritative sources, first responders, citizens have different views/roles
• Low cost/free

19. Kevin Sources
Sources:
• Richard Patrick, Director, Medical First Responder Coordination, Dept of Homeland Security
• Kenneth Dueker, J.D., Director, Office of Emergency Services City of Palo Alto
• Jonathan Reichental, Ph.D. :: Chief Information Officer, City of Palo Alto
• Maj David Bozzo, USAF ANG 129 OSF/IN