5,025
edits
Line 7: | Line 7: | ||
* Ensure programming is structured logically to meet the challenges of both climate change/extreme weather events, '''''and''''' the threat of a Cascadia Subduction Zone earthquake; | * Ensure programming is structured logically to meet the challenges of both climate change/extreme weather events, '''''and''''' the threat of a Cascadia Subduction Zone earthquake; | ||
* Encourage the growth and development of block-scale neighborhood teams. | * Encourage the growth and development of block-scale neighborhood teams. | ||
== Summary == | |||
<br/> | <br/> | ||
__TOC__ | __TOC__ | ||
Line 29: | Line 31: | ||
=== Revisiting the purpose of a NET ''team'' === | === Revisiting the purpose of a NET ''team'' === | ||
Among the most significant change drivers, however, is a simple epiphany or two about NET. | Among the most significant change drivers, however, is a simple epiphany or two about NET and '''''why''''' they meet as teams. | ||
==== Centralized deployments and self deployments ==== | ==== 1.) Centralized deployments and self deployments ==== | ||
In its history, NETs have never self deployed. To review: a NET self deployment is OK'd by PBEM when two key conditions are met: 1.) a citywide disaster is taking place; and 2.) regular communication systems are not functional. When those conditions are met, the expectation is that NETs check themselves/family/immediate neighbors to make sure they're OK. If so, they deploy to their staging areas and commence their Team Operations Plans. | In its history, NETs have never self deployed. To review: a NET self deployment is OK'd by PBEM when two key conditions are met: 1.) a citywide disaster is taking place; and 2.) regular communication systems are not functional. When those conditions are met, the expectation is that NETs check themselves/family/immediate neighbors to make sure they're OK. If so, they deploy to their staging areas and commence their Team Operations Plans. | ||
'''Only an earthquake, therefore, would ever prompt NETs to self deploy.'''<ref>...or an electromagnetic pulse (EMP). But in this stage of the conversation, I don't think it's particularly helpful to explore the horrifying implications of that. https://www.economist.com/the-world-if/2017/07/13/the-disaster-that-could-follow-from-a-flash-in-the-sky</ref> All other NET | '''Only an earthquake, therefore, would ever prompt NETs to self deploy.'''<ref>...or an electromagnetic pulse (EMP). But in this stage of the conversation, I don't think it's particularly helpful to explore the horrifying implications of that. https://www.economist.com/the-world-if/2017/07/13/the-disaster-that-could-follow-from-a-flash-in-the-sky</ref> All other NET deployments have always been, and envisioned ever as, centralized through PBEM. In other words, when there is an emergency, PBEM decides: | ||
* ''Whether'' to deploy volunteers | |||
* ''Where'' they will deploy from or to | |||
* ''What'' responsibilities volunteers will take on | |||
* ''When'' the response period(s) will be | |||
* ''How'' volunteers will be kept reasonably safe | |||
In a self deployment, NETs propose answers to all of the above in their Operations Plans. But if NETs only self deploy for an earthquake, Operations Plans are, in fact, earthquake response plans. | |||
So: one reason NETs meet as a team is to plan their earthquake response and forward their <s>Operations Plans</s> earthquake response plans to PBEM. | |||
==== 2.) Training and socializing ==== | |||
But earthquake response planning is not the only reason we've heard from teams that they organize and meet with each other. They also meet to: | |||
* '''Train together.''' This is done on different scales...everywhere from tabletop exercises to full blown comprehensive search and rescue at Scenario Village. | |||
== Notes and References == | == Notes and References == |