Anonymous

2023-2024 NET Program Changes: Difference between revisions

From WikiNET
m
Line 69: Line 69:
# '''Not started:''' Change NET Guidelines to reflect a clear distinction between Centralized Deployments and Earthquake Deployments
# '''Not started:''' Change NET Guidelines to reflect a clear distinction between Centralized Deployments and Earthquake Deployments


=== Phase 2 (a period of major change in NET): ===
=== Phase 2 (a period of major change in NET, will take 3 - 6 months): ===


# '''Not started:''' PBEM requests neighborhood Training Centers from the NET community.
# '''Not started:''' '''Develop NET Training Centers'''
# '''Not started:''' PBEM publishes list of NET trainers and requesting system.
#* PBEM requests neighborhood NET Training Centers from the NET community.
# '''Not started:''' Formally request Team Leaders submit their NERF Service Areas.
#* PBEM releases NET training schedule (including Basic NET).
#* PBEM publishes directory of NET Training Centers.
#* PBEM publishes citywide training calendar (either through MIP or through Smart Sheet, and through the Bulletin).
#* PBEM works with FPN to publish training "recipes" to the Wiki.
# '''Not started:''' '''Develop the NERFs'''
#* PBEM/FPN work on development arc for block-scale NETs. Milestones will/may include:
#** Service area boundaries
#** Decide on radio frequencies
#**Capacity assessment
#**Capacity planning (which VSFs and how many)
#**Neighborhood outreach
#***PBEM develops solid plans around curriculum)
#***Many curriculum options, including the Community Resilience Workbook, PocketPrep, Speakers Bureau, [https://coolblock.org/ Cool Blocks], Map Your Neighborhood, Pearl District Curriculum, postcard drops/neighborhood block parties..
#**Assembling a roster (which includes NETs, neighbors, ATVs)
#* Block-scale NETs declare intent to have a NERF, submit their service area boundaries


=== Phase 3 (long term projects/ongoing program maintenance): ===
=== Phase 3 (long term projects/ongoing program maintenance): ===


 
* Emphasize development of most important VSFs: 02, 06, 08, 09, and 15.  
 
#
#Dispense with the term "Operations Plans" and call them "Earthquake Plans" to reflect what the plan is actually for and to help put NETs in the mindset of forming a plan around earthquake response.
#Using GIS, allow Teams to decide on service area boundaries that reflect the [[Team Service Areas|response area]] they want to/feel comfortable responding inside of after an earthquake.
#Give NET volunteers the option of participating in earthquake planning in their neighborhoods (assembling and maintaining a NERF) if they choose to; active NETs do not have to, and all NETs can still participate in centralized deployments.
#*NERF teams can meet in person (preferred) or through online meetings.
#* NERF teams can bring in non-NETs (ATVs)
#*There will be a series of planning milestones for NERFs, for example:
#**Decide on (and get approval for) service area boundaries and have them published to the NET map
#**Decide on radio frequencies
#**Capacity assessment
#**Capacity planning (which VSFs and how many)
#**Neighborhood outreach
#**Assembling a roster
# Two types of teams: an earthquake planning team (which includes non-NETs in the service area) and broader scale teams that meet for socializing/community outreach/training events...these will be "NET Training Centers", and PBEM will also be one of these NET Training Centers.
#* Use the wiki to host team exercise "recipes" which FPN, PBEM, and individual NETs develop.
Emphasize development of most important VSFs: 02, 06, 08, 09, and 15. They conform with what we train in Basic, best suited to volunteers, already doing a lot of that stuff anyway.


== Notes ==
== Notes ==