Anonymous

2023-2024 NET Program Realignment: Difference between revisions

From WikiNET
m
Line 138: Line 138:


==== 1.) Team decides on a Team Service Area ====
==== 1.) Team decides on a Team Service Area ====
x
I've already drafted the policies that would govern how Team Service Area boundaries would be formed; '''you can read them at the [[Team Service Areas]] wiki page.'''
 
But, the gist here is that a team elects to respond to an area of the City they feel their team can handle after a major earthquake. A team ''can'' decide to stay with the boundaries of a neighborhood association, as we do now, but they will be challenged to explain how they plan to effectively respond inside such a large area.
 
It's important to note, also, that Service Areas are not permanent. A team can start small and grow over the years as their capacity improves and increases.
 
'''To make this idea work, we would need:'''
 
* A contract in place to manage online mapping. We already have a GIS tech in mind, and he's the same person who designed all of [https://pdx-net.maps.arcgis.com/home/index.html these NET maps].
* A date on the calendar by which all NETs who plan to develop a block scale earthquake response framework turn in their maps for review by PBEM and publication.
 
==== 2.) Initial community outreach ====
With boundaries decided, it's time to get all the neighbors together. PBEM will suggest an initial community meeting which we will offer technical assistance for (e.g. "how to" pages in the Wiki and helping with flyering or doing postcard drops, etc).
 
We'll recommend a series of progressive curriculum for NETs to use with their neighbors. The first meeting, for example, might be getting to know everyone and doing a brief preparedness presentation. The next couple meetings might be on specific preparedness topics, such as getting pets ready or storing water, and leading into curriculum like the Community Resilience Workbook. From there, the NET leader might begin assigning willing neighbors to VSF roles (such as medical or radio communications), and even getting a few into basic NET training.
 
Over the years, PBEM has been through and processed a LOT of preparedness materials for neighbors (seriously, [[Printed Community Handout Materials|check this out]] that I'm working on). The Wiki is going to make it easier to evaluate which materials make the most sense for your community, how to order it from us, and how to instruct it to your neighbors.
 
'''To make this idea work, we would need:'''
 
* To further develop the Wiki pages so that NETs can look up and evaluate the different community curriculum options they have access to;
* Develop the Wiki so NETs have access to "how to"s on making initial contact with neighbors and doing a neighborhood block party;
* Get the Speakers Bureau running, which will allow NETs to request a preparedness instructor for a neighborhood meeting;
 
==== 3.) Conduct a Capacity Assessment of the neighborhood ====
This is where we begin gettin' a little more technical.
 
When the NET leader decides the neighborhood is ready for it, their community moves into a Capacity Assessment for their earthquake response framework. Most likely, not every household in Service Area will participate, and that's OK. These next two phases move past "earthquake preparedness" and into "earthquake response".
 
The Capacity Assessment phase is where the NET leader works with their team to assess '''''how ready the neighborhood is to respond to an earthquake.''''' Critical to this will be an electronic worksheet which will prompt the team to explore questions such as: : How sturdy is the construction of the properties in our area? How many, and what severity, of injury should we prepare for? Should we be prepared to shelter pets? Do we know how we will communicate with the nearest BEECN if we need to? And so on. The overarching question here is: '''how much and what kind of damage do we expect an earthquake to cause in our service area, what resources do we ALREADY have to mitigate that impact?'''




== Notes and References ==
== Notes and References ==