Team Development Arcs: Difference between revisions
From Portland NET Wiki
| Line 481: | Line 481: | ||
=== Neighborhood Unreinforced Masonry (URM) Building Inventory === | === Neighborhood Unreinforced Masonry (URM) Building Inventory === | ||
Learning Objective: | '''Learning Objective:''' | ||
Team members will learn how to identify and document unreinforced masonry (URM) buildings in their neighborhood as part of planning work to inventory seismic risks. | |||
'''Facilitation:''' | |||
Introduce the activity by explaining that URM buildings are among the most dangerous in earthquakes—they are prone to partial or total collapse, posing risks not only to occupants but also to responders and bystanders. Portland has thousands of URM buildings. | |||
Refer the group to the URM Building Survey Workflow Guidebook (CREW, 2025), which provides step-by-step guidance on how communities can plan, train, and execute URM sidewalk surveys. Stress that teams are not being asked to perform structural evaluations—that is work for engineers. Instead, NETs can conduct “sidewalk surveys”: exterior-only observations of suspected URM buildings, guided by a standard checklist and training. | |||
Steps: | |||
Practice Identification: If possible, walk the neighborhood and practice spotting URM indicators together. Use a simplified checklist from the guidebook and emphasize safety (stay on public sidewalks, do not enter private property). | # Overview & Context: Provide a short briefing on what URM buildings are and why they matter in earthquakes. Share photos or diagrams of common URM features (header courses, parapets, brick bond patterns). | ||
# Introduce the Workflow Guide: Explain that the full guidebook gives best practices for planning surveys, data collection, volunteer safety, and quality control. NET teams will use it as a reference. | |||
# Practice Identification: If possible, walk the neighborhood and practice spotting URM indicators together. Use a simplified checklist from the guidebook and emphasize safety (stay on public sidewalks, do not enter private property). | |||
# Documentation: Encourage teams to use simple forms, photos, or mapping apps to log suspected URM buildings. They don’t need to be perfect—data can later be reviewed by PBEM or subject matter experts. | |||
# Discussion: Afterward, reflect on what was found, challenges in identification, and how this data could support neighborhood-level planning efforts. | |||
'''Debrief Questions:''' | |||
* Where in our neighborhood do we see concentrations of URM buildings? | |||
* What risks do these pose (collapse, blocked streets, impacts to critical facilities)? | |||
* How confident are we in identifying URM features? What support or training would help? | |||
* How might this inventory connect with our other planning efforts (caches, neighborhood profile, VSFs)?<br> | |||
Where in our neighborhood do we see concentrations of URM buildings? | |||
What risks do these pose (collapse, blocked streets, impacts to critical facilities)? | |||
How confident are we in identifying URM features? What support or training would help? | |||
How might this inventory connect with our other planning efforts (caches, neighborhood profile, VSFs)? | |||
<br> | |||
<hr> | <hr> | ||
