Slide 1:
Post-Disaster Redevelopment Planning with HAZUS-MH

Chris Zambito, CFM
Hillsborough County Hazard Mitigation
zambitoc@hillsboroughcounty.org



Slide 2:
Outline of Todays Rambling, Semi-Coherent Session



Slide 3:
Map Graphic



Slide 4:
Tampa Area Map Graphic



Slide 5:
Hazard Mitigation:

Limiting Vulnerability to Disasters



Slide 6:
Examples of Disasters from the 1980s to the Present


1985 New Coke is It!

1999 Jar Jar Binks 

2007 HAZUS is sooo hot 



Slide 7:
Sea Surface Representation from ESRI Map Book



Slide 8:
Hillsborough County Development Over Time




Slide 9:
Hillsborough County Coastal Vulnerability

Factors Considered in Risk Model:

Age of Structure
Vulnerability to Storm Surge
Vulnerability to Inland/Riverine     Flooding
Presence of Mobile Homes
Population >65
Population <5



Slide 10:
Critical Infrastructure

Ongoing Nightmare

Data capture started in 1998 under the State of Floridas "Local Mitigation Strategy" 
initiative 

Interns went out with GPS and cameras for approximately 2,000 facilities

Work through the Disaster Recovery Committee where approximately 80 agencies are 
represented (few, if any provide updated data)

Spatially corrected in 2005 and used to create debris management clearance routes

In 2007, updating list and working with electric utility, TECO, to create a list that syncs 
"Power Restoration" and "Community Recovery" priorities

Ongoing Quirks

HAZUS
Software incompatibility in first attempts in early 2000s
HAZUS Essential facilities vs Countys Critical Facility Inventory
State Database vs Study Region Data

Other Software
DHS Regional Domestic Security Task Force using a software called "SiteProfiler"
Different Facilities
Terrorism oriented although looking to integrate natural hazards in update

Conceptual Differences (ex. a "Site")
"Site" and "Asset" - SiteProfiler
"Thing" with a "Thing"  Ontology oriented
Single "Point" with related "Point of Entry" for relation to routing tools




Slide 11:
Post-Disaster Redevelopment Overview 
And
HAZUS-MH Implementation



Slide 12:
Post-Disaster Redevelopment Overview  Part 1



Slide 13:
Post-Disaster Redevelopment Overview  Part 2



Slide 14:
Post-Disaster Redevelopment Overview  Part 3




Slide 15:
Post-Disaster Redevelopment Exercise Scenario



Slide 16:
General Plan for Modeling Localized Event for Area Vulnerable to Storm Surge



Slide 17:
HAZUS-MH Flood Example



Slide 18:
HAZUS-MH Flood Example Coastal Flood Example



Slide 19:
HAZUS-MH Flood Example Coastal Flood Example



Slide 20:
HAZUS-MH Flood Example Coastal Flood



Slide 21:
The Day After Tomoorow Poster Graphic



Slide 22:
Where to Go From Here

Attend an intro class!

Look at output of 2 models by census block

Create multipliers for damages (trying to reduce double-counting damages)
Wind Multiplier
Water Multiplier

Compare loss of functions for essential facilities for each model and consider use of 
multipliers (or new ones as required)

Compare economic data outputs

Refine data and parameters
Housing stock
Essential facilities
Flood model transect data
Flood height data to coincide with potential surge effects in the flood model



Slide 23:
General HAZUS Gripes

What the heck am I doing?!

Complicated software with nuances between models and need for heavy investment in 
data generation/quality control for effective use

Easy to misuse or misrepresent output data

Wheres a SLOSH like tool to eliminate double counting effects/damages?

Why the secrecy?

Training is infrequent, in few locations, and virtually no basic documents or help via the 
web

Data protection and proprietary formulas should be guarded, but rest of the process 
should be as public as possible (no HAZUS 101, Data Management 101, etc. available 
online)

Are we using a sledgehammer to push a thumbtack in?

Most communities need general, quick, reliable data if using to assist in 
preparedness/response activitiesdata output is too general for this purpose or to 
arduous to collect in order to use appropriately

Who is the target audience?

Identified as a mitigation tool (planners), marketed at conferences as disaster tool 
(emergency managers), and model should be run/created as a technical tool 
(engineers).



Slide 24:
Any Other Concerns/Questions?

THANKS FOR YOUR TIME (and for keeping your snoring to a minimum)!