HAZUS Automap Capabilities Breakout Group Tasks As presently implemented, HAZUS requires specific input to define the seismic hazard: ?magnitude ?peak ground velocity (PGV) ?peak ground acceleration (PGA) ?spectral acceleration (SA) at 0.3 ?spectral acceleration at 1.0 s All subsequent computations are based on these data. If the ground motion inputs (PGA, PGV, and SA) are unavailable, HAZUS will generate them, based on the information available and internal modules that predict shaking values. Therefore, the most direct implementation of seismic data products (e.g. Shake Maps) into HAZUS is through these 5 inputs. Although HAZUS can use ground motion data in normal operation, it cannot use these data in an automatic mode. The automatic capabilities of HAZUS are presently limited to using location and magnitude information. In this mode, HAZUS uses its internal modules to predict the required ground motions. At a minimum, the goal of automating HAZUS requires 1) generation of the required input data, 2) push of these data to critical recipients, and 3) modification of HAZUS to use these data. However, concern has been raised regarding reviewed versus unreviewed Shake Maps (e.g., there may be three successive Shake Maps issued within the first hour of an earthquake, followed by additional revisions after 4-6 hours), the area of Shake Map coverage, uncertainties in the Shake Map motions, and other related subjects. These are all complex issues that require more discussion and thought. In particular, the issue of when to run HAZUS (with respect to an evolving picture of the ground motions) makes the use of automation very tricky. In terms of resolving some of these issues related to Shake Map and HAZUS, it is important to differentiated between implementation issues, which may be resolved through the California Integrated Seismic Network (CISN), and development issues, which may be addressed through the Advanced National Seismic System (ANSS) Shake Map committee. Priority tasks for automating HAZUS: 1)Seismic networks need to produce the required input for HAZUS Shake Map version 2 (V2) produces the ground motion maps required by HAZUS. In southern California, Shake Map V2. is fully implemented and the required data are available. In northern California, efforts to install Shake Map V2 at the USGS are underway, although additional work to ensure computation of the necessary parameters is required. The implementation of Shake Map through the ANSS should see this capability extended nationwide. 2)Resolve format issues between Shake Map and HAZUS Details about format need to be resolved between the HAZUS and Shake Map software. Discussions between Durham Technology and Dr. David Wald, USGS representative of the ANSS Shake Map committee, are underway. Dr. John Evans of the USGS has volunteered to provide input regarding the tradeoffs between grids and contours. 3)Initiate "push" of Shake Maps to Cal OES and FEMA via multiple paths. In southern California, this task is underway. The TriNet group has been working with OES and maps are currently being pushed to Sacramento over the Internet. In northern California, this task will be addressed after the successful implementation of Shake Map V2. 4)Modify HAZUS to run automatically upon receipt of required ground motion data. As indicated above, HAZUS currently is automated using location and magnitude information. Use of ground motion data requires manual operation. Modification of the HAZUS software is required to use the ground motion data in automated operation. In order to facilitate this effort, HUG should propose to the FEMA Response and Recovery Directorate that the automap capabilities of HAZUS be expanded. A letter will be drafted by Jim Davis, a representative of OES, and a representative of FEMA prior to the next meeting of the HUG. Successful implementation of this capability within HAZUS will require careful consideration of configuration issues. The Automap group produced a number of recommendations on this subject. Secondary tasks for automating HAZUS 5)Make sure that the Shake Map results cover the entire area with a potential for slight or greater damage to weak structures. This issue involves a tradeoff between computation time and area of coverage. The Automap group will draft a letter to be sent to Dr. David Wald of the ANSS Shake Map committee. 6)Establish the form and protocols for "vetting stamps" for both Shake Maps and for HAZUS maps. These stamps should uniquely identify the map by source, time, and quality. The HAZUS maps should include the Shake Map stamps as well as their own. The Automap group will ask the ANSS Shake Map committee to address the question of vetting stamps. Dave Kehrlein of OES and Stuart Nishenko have volunteered to define the HAZUS vetting stamp. 7)Define how to include station information (locations and shaking values) in Shake Map outputs. The Automap group will ask the ANSS Shake Map committee to address the question of station information. 8)Define how to express uncertainties in Shake Map and HAZUS products The Automap group will ask the ANSS Shake Map committee to coordinate with FEMA to address this issue. Tertiary tasks for automating HAZUS 9)Design a robust method for distributing Shake Maps more broadly, using a hub and spoke topology. Identify essential participants 10)Define policies and protocols for broader distribution of Shake Maps and HAZUS products, beyond the essential "push" customers.