Hazus Modernization Phase 2: A Walkthrough

Suman Biswas – sbiswas@niyamit.com

December 11, 2015

2

Hazus Tool – Our Key Objectives

1. A user friendly software – continuously improve User Experience (UE)

2. Flexible and Agile – Quickly adopt to business needs & changes

3. Improved overall performance of the tool

4. Lower maintenance cost – A GIS upg ade should ’t e a o ths p oje t

5. Transition Hazus from Desktop to Web-Based

Interesting Thought: HTTP vs FASP

3

Hazus 3.0 – Highlights

1. Have a foundation (C# .NET, SQL Server Migration) that can enable us for future

enhancements

1. Some rough numbers:

We had Approx. 290 Issues logged in our issue database related to Hazus Tool

Approx. 130 issues are closed once Rel 3.0 is out

There are still ~ 60 issues (we will look into this list in Rel 3.1 and 3.2)

Re ai i g ~ issues a e a tually e ha e e t e uests e’ e e ie i g those

3. Performance Improvements

4

Hazus Modernization Phase 2 – Release 3.1 and 3.2

Key Decisions

1.Release 3.1: Target March, 2016

2.Release 3.2: Target Nov, 2016

3.No longer support Windows 32-bit

OS

4.ArcGIS 10.4 support will be part of

Release 3.2

5.CDMS Web – We’ e o side i g it –

Need your help – Complete the Survey

5

Release 3.1 - 1. Convert VB6 to C#

Introduction

HAZUS-MH is a Windows desktop application which was built using Microsoft’s Component Object

Model (COM) written primarily in Visual C++.

Current Problem

VB6 is obsolete

Hazus Earthquake and Shell have VB6 dependency

Solution

• Re-architect and replace the VB6 source code and COM architecture using C#.NET

• Maintain the existing functionality currently available in the Hazus Shell, Earthquake Model

Solution Benefits (Why this solution)

Remove Hazus dependency on an obsolete technology

Provide a reliable foundation for future Hazus enhancements

6

Release 3.1 - 2. New Client Install

Introduction

Hazus 3.0 installs a SQL Server 2008 R2 instance

This instance (.\HAZUSPLUSSRVR) is used to host state and study region databases

Current Problem

Hazus installs silently SQL Server 2008 R2

Sometimes SQL Server 2008 R2 is not installed properly by Hazus, and

That leads to Hazus installation problems

Solution

Split the Hazus setup into two parts –

• Install the Hazus SQL Server instance

• Install the Hazus application. It will still check for the existence of the Hazus SQL Server instance

Solution Benefits (Why this solution)

Provide a clean Hazus install without SQL Server related installation problems.

Reduce the install time by focusing only on the Hazus binaries.

Future Considerations (if any)

Future study region preservation regardless of install/uninstall

7

Release 3.1 - 3. SQL Server 2014 Express Upgrade

Introduction

The current version of Hazus 3.0 utilizes SQL Server 2008 R2 for storing the state as well as the study

region databases

Current Problem

SQL Server 2008 R2 - Mainstream Support Ended – 7/8/2014

Solution

Upgrade Hazus 3.1 to SQL Server 2014 Express edition

Solution Benefits (Why this solution)

SQL Server 2014 has better features for handling Spatial data types with performance improvements

Future Considerations (if any)

Explore and utilize the SQL Server Spatial capabilities to a greater extent, thereby reducing client-side

code

8

Release 3.1 - 4. Replace MS Jet Engine (32 bit) with Access Database Engine (ACE)

Introduction

Hazus 3.0 currently uses Microsoft Jet Engine 4.0 to interact with MS Access and MS Excel

Current Problem

Microsoft Jet Engine 4.0 is considered a deprecated product

Microsoft does not support Jet Engine 4.0 in Windows 8

Solution

Microsoft recommends replacing Jet Engine 4.0 with ACE

Hazus 3.1 will be run on 64 bit OS only

Solution Benefits (Why this solution)

Replacing a deprecated Jet Engine product will improve performance utilizing ACE (64 bit)

9

Release 3.1 - 5. Replace Registry with Config File

Introduction

The current Hazus-MH application depends heavily on Registry keys for accessing database connection

strings and various locations – Inventory, Region

Microsoft is tightening Registry access for security reasons

Current Problem

Registry is a sensitive matter; it can corrupt the performance of the whole Windows OS

Solution

To move the registry keys to a configuration file (app.config)

Solution Benefits (Why this solution)

1) The built-in code to access an app.config from .NET is full-featured and easy to use

2) Hazus will not be solely relying on the registry entries

3) No need for access permissions to the registry

10

Release 3.1 - 6. Enhance User Defined Facility Import, Analysis and Reporting in

Hazus Flood

Introduction

Build on Phase I:

•UDF structure tables are now available in state databases

•UDF is now included as part of the study region aggregation process

Current Problem

Risk MAP community feedback has shown low interest in aggregated AAL results versus site-specific

building loss results.

Require and provide resources for risk assessments for Risk MAP studies that change the requirement

from providing national AAL results to site-specific AAL assessments

11

Release 3.1 - 6. Enhance User Defined Facility Import, Analysis and Reporting in

Hazus Flood (Contd.)

Solution

Modify the Hazus Flood AAL GUI from command to a submenu that now includes GBS and UDF

commands

Adapt the Hazus Flood GBS AAL analysis to work with UDF point data

Modify the Hazus Flood Result GUI menu to include UDF AAL results command

Create a new UDF data browser AAL results dialog

Modify the Hazus Flood Results / Report dialog to include UDF AAL report

Create a new UDF AAL report, including views, and stored procedures

Solution Benefits (Why this solution)

Improved UDF Import, Analysis, Reporting

Added UDF AAL analysis

Future Considerations (if any)

CDMS functionality can be enhanced to allow users to import and format UDF site-specific information

as an alternative to aggregating the data to the census block

Make it easier to bring in UDF site specific data in CDMS

12

Release 3.2 - 1. Minimize Impacts on ArcGIS Version Change

Current Problem

• Esri releases annually new versions of its ArcGIS Desktop software, in which Hazus

operates as an extension

• Currently Hazus 3.0 uses ArcGIS Desktop version 10.2.2, although 10.3 has been available

since January 2015

• Hazus releases trail Esri releases by a significant time lapse

• Hazus users are impacted by having to remain a version (or 2) behind thus having to

maintain a separate workstation

• Hazus users are sometimes forced into not using it at all

13

Release 3.2 - 1. Minimize Impacts on ArcGIS Version Change (Contd.)

Solution

Replace the current ArcObjects-based APIs in the Hazus Flood hazard code base with calls

to the Esri’s Geoprocessing (GP) Tools APIs

Move client-side spatial code to the server-side utilizing SQL Server Spatial

Solution Benefits (Why this solution)

Esri sees ArcGIS Pro as the future

Hazus is based on ArcGIS Desktop

GP Tools are available in ArcGIS Desktop, and ArcGIS Pro

Limited ArcGIS 10.3 holistic testing of the Hazus Flood model, demonstrated that the

aggregation and loss estimation were not impacted, however, the Hazus Flood hazard,

based on ArcObjects 10.2 was impacted

14

Release 3.2 - 2. Hazus EQ Model Integration of USGS Shake Map

Introduction

Hazus Earthquake Model needs hazard information to model probabilistic or historic earthquake

events

USGS ShakeMap provides readily available hazard input to Hazus EQ Model

Current Problem

Hazus has a way to bring in ShakeMap, but it is cumbersome involving a number of manual steps

Solution

A more sophisticated approach would be to

Create an interface that points directly to USGS XML grid

Include a magnitude, and location filter and

Use more refined ground motions than the currently used contour ShakeMap

15

Release 3.2- 2. Hazus EQ Model Integration of USGS Shake Map (contd.)

Solution Benefits (Why this solution)

Automate browse, select, download, and import a ShakeMap to Hazus EQ Model

Make Shakemap-based EQ Scenario creation similar to Hazus Hurricane Model Hurrevac user

experience

Future Considerations (if any)

Include the ShakeMap Atlas as well as web interface for new, near-real-time scenarios and events

(FEMA will coordinate with USGS on this)

16

Release 3.2- 3. Reports Modernization

Introduction

Hazus currently lets users view results of the analysis in three formats:

Tabular (using Hazus data browsers)

Thematic maps (using ArcGIS)

Reports (using Crystal Reports)

Current Problem, Proposed Enhancements

The reports currently do not offer:

Toggle on/off reports in the tabular format

Toggle on/off maps

Pie graphs/charts

17

Release 3.2- 3. Reports Modernization (contd.)

Possible Solution(s)

Multiple routes can be taken to include the new changes proposed:

Using Crystal Reports (CR) add the new features discussed

Using Microsoft SQL Server Reporting Services (SSRS)

Using Dashboards

Solution Benefits (Why this solution)

Integrated charts and graphs add a new level of data visualization using CR

CR provide the user better customization options (Toggle reports and/or graphs on/off)

CR has benefits of time as the technology is already tested and in use

Helping users apply Hazus results to risk assessments and mitigation plans

Helping users communicate risk better (using the charts/graphs)

Note: Dashboards – require major architectural changes

18

Release 3.2 - 4. Web Based CDMS – Inventory Management

Introduction

Web CDMS (Comprehensive Data Management System) will streamline and automate raw

data processing and allow users to share their data sets with other users

Web CDMS will continue to use desktop CDMS to update and manage statewide datasets

locally

Current Problem

Currently, desktop CDMS does not allow users to share the more detailed datasets with

other users of HAZUS

Updates to State Repository data sets get stored locally

User efforts are duplicated nation wide due to non-sharing

19

Release 3.2- 4. Web Based CDMS – Inventory Management (contd.)

Solution

Enable data sharing

Utilize power of communities level users to provide data

Allow users to submit dataset to be integrated with FEMA state datasets

Allow users to Download dataset using CDMS

Solution Benefits (Why this solution)

Local community/users have access to more accurate data

This solution gives user flexibility to update FEMA state datasets for accurate data

Provides access to the most up to date information to the users, thus they will not have to

wait for official release of State Data to get most recent data

20

Release 3.2- 5. ArcGIS 10.4 Upgrade

Introduction

The objective of this task is to upgrade to ArcGIS 10.4 with the Hazus 3.2 release scheduled for

November 2016

Current Problem

Hazus 3.0 released November 2015 uses ArcGIS 10.2.2

ArcGIS 10.3 was released January 2015

ArcGIS 10.4 scheduled for February 2016

Solution

Upgrade Hazus to the latest version of ArcGIS – Hazus users get access to the latest ArcGIS fixes &

functionality

Solution Benefits (Why this solution)

Hazus will be in-line with latest ArcGIS stable version

21

Release 3.2- 6. Replace Arc Objects Calls with Stored Procedures

Introduction

Current Hazus 3.0 uses extensively ArcObjects to process data on the front-end.

Current Problem

Hazus 3.0

•Brings data to the front-end from the back-end SQL Sever databases,

•Processes it on the front-end, and

•Updates the back-end

Which impacts the overall Hazus performance.

Solution

To re-architect the logic of processing the data on the front-end and take advantage of the fact that all the data is

under the same SQL Server database and that we can use Spatial SQL operators, and queries to process the spatial

data on the back-end

Solution Benefits (Why this solution)

Esri is moving away from ArcObjects.

Improve performance while bringing only the needed data.

Future Considerations (if any)

Remove dependency on ArcObjects makes easier to maintain Hazus in the future.

22

Additional Considerations

Latent Defects and Other Enhancements

We will have some capacity to address a few latent defects and implement a few enhancements

Major Consideration

Tsunami Model – Implement Tsunami Model for Hazus

Would like to hear from you

Send email to sbiswas@niyamit.com

THANK YOU