amage Assessment Workshop Background & Introductions Background Retiring IVSS Previous Discussions and Demos – Jan-Feb 2013 Final Direction Esri Damage Assessment Team Ivan Konermann Kevin Armstrong David Crosby 8/23/2013 1
Damage Assessment Workshop Background & Introductions Background Retiring IVSS Previous Discussions and Demos – Jan-Feb 2013 Final Direction
Damage Assessment Workshop Background & Introductions
Background Retiring IVSS Previous Discussions and Demos Jan-Feb
2013 Final Direction Esri Damage Assessment Team Ivan Konermann
Kevin Armstrong David Crosby 8/23/20131
Slide 2
Damage Assessment Workshop Background & Introductions, Cont
Damage Assessment Core Team BDRS - David Howdeshell*# EMA - Sally
Bishop*, Joe Borries# PAO - Curt Nielsen*# Risk Mgt - Ginny
Holscher*#, Denise Payne PSS - Michael Erickson*# REM - Paul Sacco*
DEI Dawn Lindgren*# Attended Day 1*, Day 2# BTS Damage Assessment
Team Art Stadlin, PM Steve Clark, GIS Software Development Christy
Kretschmann, Business Analysis 8/23/20132
Damage Assessment Workshop High Level Scope Considerations
Funding No budget dollars at this time Timeline - October 2013 -
April 2014 Time Constraints Retire existing solution (iVss) by end
2013 Go Live with replacement prior to 2014 hurricane season
8/23/20136
Slide 7
Damage Assessment Workshop High Level Scope Considerations eGIS
Guiding Principles Use Esri COTS Leverage Out-Of-The-Box
Capabilities Focus on the critical requirements Stakeholder
Engagement Requirements Solution Decision Build & Test Train
& Rollout 8/23/20137
Slide 8
Damage Assessment Workshop Workshop Agenda THU 8/22 TimeTopic
a.m.Introduction High-Level Scope Validation Business Requirements
CONSENSUS ON REQUIREMENTS p.m.Demonstrations FRI 8/23 TimeTopic
a.m.Pros/Cons Requirements Priorities KNOW WHAT IS TO BE DECIDED ON
p.m.Consensus on Solution Direction Next Steps 8/23/20138
Slide 9
Damage Assessment Workshop DAY 1 A.M. 8/22/2013 8/23/20139
Slide 10
Damage Assessment Workshop Wants / Hopes - 1 Risk: FEMA. Bring
wide-spread damage info together into one document; System should
capture all the data (to get off Excel). Risk: Property Insurance.
Provide documentation to substantiate damages / losses ($) to
insurance companies; Need the property values as a basis to
calculate the cost of the damages. PAO: Property Values. Properties
having sustained damage need to be flagged (and maybe a photo) so
that PAO may follow-up after the storm to re-assess the property.
eGIS Sponsor: Desire to have a solution design that may be rapidly
developed and easily supportable. DEI: WebEOC. Separate project.
DEI: Utilities Assets. Ability to use various field devices to
capture damages to DEIs assets. EMA: Field Devices. Support all
devices types. EMA: Disaster/FEMA Declaration: Needs to be fast,
and data categorized as the Federal government needs it; Ability to
rapidly assess the situation in order to declare an emergency. EMA:
Damage Assessment Teams. Know where to assign teams to gather
detailed assessments; where to canvas to gather damage data,
especially on the smaller disasters. Need to know the damage level
in order to prioritize where to deploy the teams. EMA: Situational
Awareness. Damage assessment solution needs to have a connection to
the Situational Awareness system. EMA: Assessments. Need to be able
to quantify quickly at first (initial, preliminary damage
assessment); then make a second round to provide more detail.
8/23/201310
Slide 11
Damage Assessment Workshop Wants / Hopes - 2 EMA: Agency
Inclusion. Have fast, reliable data to inform and include agencies
that have not always been included. EMA: Storm Impressions. Need to
have both tools, to enable initial assessments (broad brush) and
then more comprehensive damage assessments. EMA: Housing. Need to
assess habitability to determine the level of impact on the
citizens. EMA: PA (Public Assistance). Need the system to support
processes that will enable request for qualification for PA. EMA:
Economic Impacts. Need to be able to calculate the percent of
damage by parcel, times the parcels tax assessment, yields a
quantification of economic damage. REM: Facilities Status. Need to
be able to have County buildings pre-loaded, so staff knows which
assets to inspect. Need to know and report which properties are
available to house people if other buildings are damaged. REM: Work
Orders. Nice to have an interface to Maximo, which tracks history.
Risk: Mold. Need to have insights during triage to prioritize which
buildings to work on saving, versus not to bother. EMA: Enterprise
Asset Management. Need to bridge damage assessment solution to
asset management solution to work-order solution. EMA: Operational
Continuity. The damage assessment system informs operational
continuity. 8/23/201311
Slide 12
Damage Assessment Workshop Wants / Hopes - 3 Economic Dev:
Businesses & Industry. Need to consider businesses and
industries in damage assessment. Economic Dev: Small Businesses.
Need to set up collection points to gather damage information and
also to inform on whats available. EMA: See-Click-Fix. A citizen
tool on the web. Would be nice to incorporate that information into
the damage assessment report. (Communications Dept. monitors the
citizen submittals, and farms them out to the proper department for
review.) Esri: Focus. Putting too much data into the geospatial
tool crosses the point of diminishing returns. Need to keep the
data highly relevant in a mission-critical app. (Another view is
that data storage is cheap, so why not put it all in the database,
and rely on the app to only present the data fields that are useful
for the purpose at hand.) EMA: 911 Data. Would like to have 911
data also imported into the damage assessment system. Manual import
as needed is sufficient. DEI: Damage Assessment Checklist: Having a
checklist with pre-defined categories for the data needed will aid
in more quickly capturing damage assessment, and ensuring that
aspects of the assessment are not missed during inspection. This
could be on paper or a portable device or laptop. 8/23/201312
Slide 13
Damage Assessment Workshop Requirements Considerations /
Discussion Forms: User friendlier for forms and screens to have
similar layout, look. Form Scanning: Would be nice if forms could
be scanned in, and text automatically recognized, instead of having
to be re-keyed. Training: Need the solution to be intuitive and
usable without significant training. Field Devices: Desire to
support all platforms. Expecting to use laptops in the field for
data capture, mostly. Need to consider smaller cities may have
Android or other devices. If we cant handle that, we may be back to
paper forms. Damage Levels: Workflow requires that the levels of
damage will vary depending on when the assessments are done, from
high-level first, to more granular. Windshield capture (initial),
is the start of the process. Continuum: Need to decided how the
solution will be used during the phases of the disaster or
emergency. Types: Residential, Public, Business/Industrial
8/23/201313
Damage Assessment Workshop DAY 1 P.M. 8/22/2013
8/23/201315
Slide 16
Damage Assessment Workshop Demonstrations - 1 Storm Impressions
(Gail Tyburski) Proof-of-concept for windshield assessments
Presentation layer in HTML5 (works on any device) Accessible only
on 911 network Displays 911 calls and fire truck data entries on
same map Data stored as comma-delimited format Data may be shared
outside 911 in multiple ways 8/23/201316
Slide 17
Damage Assessment Workshop Conceptual Architecture (Kevin
Armstrong) 8/23/201317 APP 1 GIS APP 2 APP 3 Data Presentation
& User Interface Data Store Reports Report 1 Report 2 Report
3
Slide 18
Damage Assessment Workshop Apps Approaches 8/23/201318 One
Does-All App Complicated to Learn & Use Individual Apps Simple
& Easy to Learn & Use Both Interface with GIS Database
Slide 19
Damage Assessment Workshop Apps Approaches Recommendation:
Limit the functions in an app to be appropriate for the role of the
user. For example, windshield assessment role has different needs
than detailed building inspection role. One-app-fits-all approach
would frustrate all users with feature complexity they will never
use. 8/23/201319 Damage Assessment
Slide 20
Damage Assessment Workshop Demonstrations - 2 Esri (Kevin
Armstrong) ArcGIS Online app built quickly (late last night)
Connected / Collector feature not available yet; expecting 2013-Q4
or 2014-Q1 (release date not yet announced) Data entry via smart
phone or other devices Dashboard with tabulations built in
Dashboard is made up of widget; There is a widget library Batch
select of parcels is possible, but not out-of-box Licensing is not
a concern for agencies not in Countys Esri ELA if we adopt an
ArcGIS Online solution, for both connected and disconnected
8/23/201320
Damage Assessment Workshop DAY 2 A.M. 8/23/2013 22
Slide 23
Damage Assessment Workshop Recap of Day 1 Disconnected Feature
Concern about agencies that do not have ability to connect. Concern
about we will give partner agencies, and what we will explain to
them about how it operates, and what costs they must bare, if any.
Proposed Architecture Ivan provided this diagram (solution
alternative 1): 8/23/201323 AGOL Web Map Collector GIS Dashboard
Browser Pads, Phones & Tablets ETA for Disconnected Capability
is TBD Data may include photos LAN/WAN Laptops
Slide 24
Damage Assessment Workshop Recap of Day 1 Proposed Architecture
Ivan provided this diagram (solution alternative 2): 8/23/201324
GIS Data may include photos LAN/WAN Mobile Device
Slide 25
Damage Assessment Workshop Recap of Day 1 Proposed Architecture
Solution alternative 2 would be to construct a new solution that
works disconnected, using an approach similar to iVss (thumb
drives). We would need to build this as a fall-back in the event
Esris Disconnected feature is not available before 2014 hurricane
season. This could involve ArcGIS Mobile, with creative means to
handle licensing restrictions before and during an emergency.
Failsafe Regardless of availability of Esris Disconnected feature,
we would be wise to build an alternative solution, at least for the
first year, to fall back on if there are unforeseen glitches with
the favored solution. Roadmap Consensus on solutions
implementations: 2014: Implement solution 1, and assume
availability of Disconnected mode. As back-up (regardless of
Disconnected mode in solution 1), implement solution 2 based on
ArcGIS Mobile. 2015: If solution 1 performed well in 2014, retire
solution 2. 8/23/201325
Slide 26
Damage Assessment Workshop Needs / Solutioning Data Model Can
use the Esri damage assessment model, or design our own. Suggestion
made to use the Esri data model, and extend it if we need to.
Collector It is a free app for Android and Apple. Link for Android:
https://play.google.com/store/apps/details?id=com.esri.arcgis.collector
https://play.google.com/store/apps/details?id=com.esri.arcgis.collector
Activities in Sequence The phases of an emergency influence the
level of detail needed, who collects it, what analysis is
performed, and what reporting is done. Initial Damage Assessment
(within 24-hours) Detailed Damage Assessment (soon after the
initial assessment) Building / Property Risk Assessment
8/23/201326
Slide 27
Damage Assessment Workshop Next Steps - 1 Activity 1 Esri will
compile a report with recommendations eGIS SC will review/approve
the recommendations Jason will champion the governance to get this
approved for work in 2013-Q4 eGIS program Validate license
arrangements to support both solutions Activity 2 Esri to support
the configuration Configuration lead is BTS (Steve Clark) Will need
to elaborate the design, data model (Steve Clark) iVss data models
to be sent to Steve from Curt. May be shared w/Esri Will need to
elaborate two solutions: 1 & 2 Achieve a checkpoint to have
beta solutions (1 & 2) by 1/1/14 Iterations toward finalized
solutions in early 2014 User training in late 2014-Q1 and early
2014-Q2 Back Office Calculations & Reporting Need to design the
reports & formats needed Need to design the connectivity &
calculations needed to deliver the reports needed Jason and Art to
discuss who could lead the design & build of the back-office
capabilities 8/23/201327
Slide 28
Damage Assessment Workshop Next Steps - 2 Storm Impressions
Pinellas needed to provide a service to the data to Esri so that
the demo may include the data. Team Approach This team will remain
active throughout the design, build, test, and deployment process
for the two solutions and the back-end processing and reporting.
8/23/201328
