2023-2024 NET Program Realignment: Difference between revisions

I'll take this apart step by step:

==== 1.) Team decides on a Team Service Area ====

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.'''

* 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 ====

* Get the Speakers Bureau running, which will allow NETs to request a preparedness instructor for a neighborhood meeting;

* Create a guide on how to hold hybrid meetings for volunteers.

==== 3.) Conduct a Capacity Assessment of the neighborhood ====

* To design the Capacity Assessment worksheet and guidance for NETs on how to use it.

'''From the Capacity Assessment comes two products:'''

==== 4a.) Capacity Plan ====

* To design an input system that would extract Capacity Planning data and post it as a dashboard;

* The dashboard, designed similarly to the BEECN dashboard.

==== 4b.) Neighborhood Earthquake Response Frameworks (not NERFs?) ====

* Automate linking Capacity Plans to a Response Framework template (should be easy to do with the software PBEM has access to).

=== A Two Year Cycle ===