2.8. DL: Damage and Loss

The Damage and Loss panel enables users to select a damage and loss methodology for estimating losses across a region. It supports various applications:

2.8.1. Pelicun Damage and Loss for Buildings

As depicted in Fig., the Pelicun Damage and Loss application offers these inputs:

  1. Damage and Loss Methodology: Choose a methodology from the following options:

    • Hazus MH EQ: For earthquake scenarios, requiring engineering demand parameters (EDPs) like peak inter-story drift ratio (PID), peak floor acceleration (PFA), peak roof drift (PRD), and peak floor displacement (PFD). Suitable for building response analysis.

    • Hazus MH EQ IM: A simpler option requiring only an intensity measure (IM), such as peak ground acceleration (PGA), for scenarios not involving building response analysis. Use this option when the Building Modeling type is set to None in the MOD tab and the Building Analysis Engine type to IMasEDP in the ANA tab.

    • Hazus MH HU: For the prediction of damage and loss to buildings subjected to hurricanes. This option requires a wind intensity measure (IM) as an input, e.g., peak wind speed (PWS).

    • User-provided Fragilities: Allows for custom fragility functions. Users must provide a script for auto-population and the path to a folder with the fragility functions, as shown in Fig. Refer to Example 9 in R2D examples for implementation.

    The HAZUS options utilize data from the Hazards U.S. Multi-Hazard project (HAZUS-MH), with Hazus MH EQ and Hazus MH EQ IM tailored for earthquakes, and Hazus MH HU for hurricanes.

  2. Event Time: Toggle ‘on’ to set the event time in YYYY-MM-DD:HH format, or ‘off’ to disable time-effects.

  3. Number of Realizations: Set the number of loss realizations for the analysis.

  4. Output Detailed Results: Enable to output detailed results.

  5. Create Log File: Enable to generate a log file of the analysis.

  6. Include Ground Failure: Checking this box will include ground failure in the analysis. If ground failure is included, fragility groups associated with ground failure are added in the auto-population phase. Note that such analysis requires peak ground displacement (PGD) values as inputs.

  7. Auto-populate Script: Path to a user-provided Python script for mapping assets to their respective fragility functions.

  8. User-defined Fragility Function Folder: Path to a folder containing user-defined fragility functions.


Fig. Pelicun Damage and Loss Input panel.

For more on Pelicun, including output descriptions, visit the Pelicun Documentation.

2.8.2. Pelicun Damage and Loss for Transportation Infrastructure

The interface for Transportation Infrastructure damage and loss in Pelicun mirrors that of buildings, as shown in Fig. Supported damage and loss methodology options include Hazus MH EQ IM and User-provided Fragilities.

Hazus MH EQ IM follows the damage and loss model from the Hazus Earthquake Model Technical Manual. For bridges, it requires SA_0.3 and SA_1.0 for ground shaking-induced damage assessment. Ground failure considerations require permanent ground deformation (PGD_h and PGD_v) inputs for bridges and roadways, while tunnels need peak ground acceleration (PGA) and permanent ground deformation (PGD_h and PGD_v).

The User-provided Fragilities option allows for custom fragility functions, necessitating an auto-populate script and a folder path for the fragility functions, as detailed in Fig. See Example 9 in R2D examples for an example.