6. Requirements

The purpose of presenting these requirements is to inform the community on the present capabilities of the PBE application and features that could be added. The original set of requirements have come from a set of grand challenge reports, GC. These original requirements have been broken into a smaller set of deliverable features by the senior faculty associated with the project, SP. Additional requirements have come from users through the User Forum, UF. See section Feature Requests if you have additional features you would like to see.

6.1. General Requirements

Table 6.1.1 PBE Requirements - General

#

Description

Source

Priority

Status

Implementation

PBE

Integrate fully coupled multi-model computations from hazard source through structure response, to compute reliable estimates of financial loss, business interruption, and casualties

GC

M

InProgress

Application

PBE.1

Ability to determine damage and loss for multiple different hazards

PBE.1.1

Damage and Loss due to ground shaking from Earthquake

GC

M

Implemented

Example 1

PBE.1.2

Damage and Loss due to Wind Loading

GC

M

InProgress

1.1.3.5.1

PBE.1.3

Damage and Loss due to water damage from Tsunami or Coastal Inundation

GC

M

InProgress

1.1.3.5.2

PBE.2

Ability to Select from Different Hazard Options

PBE.2.1

Ability to select from all EE-UQ Event Options listed in EE-UQ

SP

M

Implemented

Example 2

PBE.2.2

Ability to select from all WE-UQ Event Options listed in WE-UQ

SP

M

InProgress

1.1.3.5.1

PBE.2.3

Ability to select from all HydroUQ Event Options listed in Hydro-UQ

SP

M

InProgress

1.1.3.5.2

PBE.3

Ability to use different Model Generation Tools

PBE.3.1

Ability to Select All Building Model Generators in EE-UQ

SP

M

Implemented

Example 2

PBE.3.2

Ability to Select All Building Model Generators in WE-UQ

SP

M

InProgress

1.1.3.5.1

PBE.3.3

Ability to Select All Building Model Generators in HydroUQ

SP

M

InProgress

1.1.3.5.2

PBE.4

Ability to use Various UQ Methods and Variable Options

PBE.4.1

Ability to use all forward propagation methods available in EE-UQ, WE-UQ and HydroUQ

SP

M

Implemented

Example 2

PBE.4.2

Ability to use all random variable distributions in EE-UQ, WE-UQ and HydroUQ

SP

M

Implemented

Example 2

PBE.4.3

Ability to use train surrogate models using the methods from quoFEM

SP

D

InProgress

1.1.2.2.1, 1.1.2.2.2, 1.1.2.2.4

PBE.5

Ability to determine damage and loss utilizing different methods

PBE.5.1

Interface with pelicun to make available its suite of methods for damage and loss assessment for buildings

SP

M

Implemented

Example 1

PBE.6

Miscelleneous User Requests

PBE.6.1

Ability to Process own Output Parameters

UF

D

PBE.6.2

Add to Standard Earthquake a variable indicating analysis failure

UF

D

PBE.6.3

Allow users to provide their own set of EDPs for the analysis.

UF

D

Implemented

Example 1

PBE.6.4

Simplify run local and run remote by removing workdir locations. Move to preferences

UF

D

Implemented

Preferences

PBE.6.5

Add to EDP a variable indicating analysis failure

UF

D

PBE.6.6

Enable saving and loading Performance Models in CSV files

UF

D

Implemented

Example 1

PBE.7

General Software Requirements

PBE.7.1

Application to Provide Common SimCenter Research Application Requirements listed in CR

GC

M

InProgress

RTM

PBE.7.2

Ability to use new vizualization tools for viewing large datasets generated by PBE

GC

M

Implemented

Results Documentation

Key:
Source: GC=Needed for Grand Challenges, SP=Senior Personnel, UF=User Feedback
Priority: M=Mandatory, D=Desirable, P=Possible Future
Status: Implemented, InProgress, and Blank (i.e. not started)
Implementation: UM=User Manual, DM=Developer Manual, SC=Source Code

Note

The general requirements refer a lot to the capabilities existing in other SimCenter tools, EE-UQ, WE-UQ and in-development HydroUQ*. These requirements can be viewed in their online documentation: EE-UQ Documentation and WE-UQ Documentation.

6.2. Damage & Loss Requirements

Table 6.2.1 PBE Requirements - Damage & Loss

#

Description

Source

Priority

Status

Implementation

DL

Damage & Loss (DL) Predictions

DL.1

Ability to use open-source version of Hazus

GC

M

Implemented

DL.2

Ability to incorporate improved damage and fragility models for buildings and lifelines

GC

M

InProgress

DL.3

Ability to perform time-based assessment

GC

M

DL.4

Methods for DL Prediction for Buildings for Various Hazards

SP

M

DL.4.1

Incorporate PACT application for earthquake hazard

SP

D

DL.4.2

Ability to perform downtime estimation using the REDi methodology for earthquakes.

UF

D

DL.4.3

Incorporate Various Methods from PELICUN

SP

M

InProgress

DL.4.3.1

Incorporate the scenario-based assessment from FEMA-P58, item P6.1.1

SP

M

Implemented

DL.4.3.2

Incorporate the time-based assessment from FEMA-P58, item P1.1.2

SP

D

DL.4.3.3

Incorporate high-resolution assessment of buildings under wind hazards, item P1.1.3

SP

M

DL.4.3.4

Incorporate high-resolution assessment of buildings under water hazards, item P1.1.4

SP

M

DL.4.3.5

Incorporate high-resolution assessment of transportation networks, item P1.1.5

SP

M

DL.4.3.6

Incorporate high-resolution assessment of buried pipelines, item P1.1.6

SP

M

DL.4.3.7

Incorporate the assessment of buildings under earthquake hazard from HAZUS, P1.2.1

SP

M

Implemented

DL.4.3.8

Incorporate the assessment of buildings under hurricane wind hazard from HAZUS, item P1.2.2

SP

M

Implemented

DL.4.3.9

Incorporate the assessment of buildings under storm surge hazard from HAZUS, item P1.2.3

SP

M

Implemented

DL.4.3.10

Incorporate the assessment of buried pipelines under earthquake hazard from HAZUS, item P1.2.4

SP

M

DL.4.3.11

Incorporate the assessment of transportation networks under earthquake hazard from HAZUS, item P1.2.5

SP

M

DL.4.3.12

Incorporate the assessment of power networks under earthquake hazard from HAZUS, item P1.2.6

SP

M

Key:
Source: GC=Needed for Grand Challenges, SP=Senior Personnel, UF=User Feedback
Priority: M=Mandatory, D=Desirable, P=Possible Future
Status: Implemented, InProgress, and Blank (i.e. not started)
Implementation: UM=User Manual, DM=Developer Manual, SC=Source Code