HAZUS Automap Capabilities
Breakout Group Summary Ideas and Rankings


Q1:  What seismological data should drive the HAZUS computations?
1)Ground motion (shake map output).  When do you use it?
2)Run predefined models on segments before event to be pulled up quickly after event
3)Short term:  use PGA and SA.  Long term:  discuss better measures with engineers
4)Identify areas where liquefaction probable
5)Need magnitude for liquefaction. Collect observed ground failure data and ground motion
6)Provide ground motion data as contours, rather than grid (faster computations)
7)Best single parameter is PGV (easy, fast, and a good measure of damage).  SA at 1Hz
8)Have time histories at selected sites
9)Need moment tensor info to parameterize mechanism
10)Duration of strong shaking
11)Directivity
12)Seismologists should tell HAZUS user what the shaking is
13)Time frame of map driven by new data, revised data, or new predictions
14)Clear communication of uncertainties of Shake Map output
15)Ground motion maps need to be far enough out to capture distant strong shaking (need a protocol to scale map for magnitude)



Q2:  How will the "data" be distributed?  To whom?  How many? By what means?
1)WWW
2)State OES
3)CDMG
4)Operational areas
5)FTP
6)Secure connection to hubs from data providers
7)Multiple hubs
8)Multiple data paths
9)Satellite
10)FEMA HQ + regions + proxies
11)Important users = hubs
12)Second class of users who get data from hubs via subscription
13)Work out delivery mechanism with Durham Tech (ftp, socket, etc.)
14)Subscription could be controlled
15)Other Fed agencies as high priority customers
16)Version # or time stand on product and authority (i.e., who made the map)
17)Pool site for media
18)Microwave
19)PSTN
20)TV cable
21)Simple for HAZUS user to implement
22)Workshops to consider value-added of customized HAZUS implementation
23)Packet radio
24)Allow "qualified" subscription
25)Push to a commercial subscription service


Q3:  How should HAZUS be modified in order to be driven in automap mode?
1)HAZUS needs to accept Shake Maps for automatic operation
2)Protocol to prioritize multiple events
3)Priority = take best available in queue (in multiple entries for the same event)
4)Make queuing configurable at the user site
5)Preprocess exposure inventory for real-time damage assessment
6)Establish the need/desire of the public for the automap capability (= marketing plan)
7)Provide "metadata" to ensure that only the best, most geographical appropriate file in queue gets processed
8)Establish whether Shake Map produces HAZUS input files or whether HAZUS reads Shake Map output
9)Include version stamp that gets passed through to HAZUS output
10)Pass-through of HAZUS licensing startup to identify who made the map
11)Make HAZUS automaps as configurable as HAZUS interactive runs
12)Focus on population dense areas (don't run HAZUS in the desert)
13)Interface with user maps working group (vis a vis appropriate products)