Key points are not available for this paper at this time.
ABSTRACT This study develops a high‐resolution regional seismic loss assessment framework for reinforced concrete (RC) bridges, focusing on direct losses due to bridge repair and replacement. Indirect losses tied to traffic downtime, business disruption, delayed recovery, etc., can also be attributed to bridge damage but are considered outside the current scope. While previous studies have made relevant attempts on regional bridge seismic loss assessment, most relied on limited hazard simulations, simplified fragility models, and generic repair cost ratios. In contrast, the current study bears its novel contribution to conduct high‐resolution assessment that directly aggregates loss contributions from individual bridge components. Using 1152 RC bridges in the City of Los Angeles as a case study, the framework integrates crucial steps that (1) generate numerous seismic intensity maps, (2) classify the inventory into 26 bridge groups, (3) assign each bridge group with second‐generation seismic fragility models, and (4) develop a stochastic loss function for each bridge through component‐level cost estimations. The high‐resolution assessment enables new insights for more in‐depth loss disaggregation analysis across varying return periods, individual bridges, bridge components, and repair actions. Research findings for LA bridges indicate that early‐designed, multi‐span bridges contribute disproportionately to the overall regional losses. The framework also supports detailed sensitivity analysis toward explicit loss uncertainty quantification. Overall, the proposed high‐resolution assessment framework enhances the fidelity, interpretability, and actionability of regional loss results, offering a transferable and scalable methodology for more effective seismic loss mitigation and post‐earthquake recovery planning.
Chen et al. (Thu,) studied this question.
Synapse has enriched 5 closely related papers on similar clinical questions. Consider them for comparative context: