5,013
edits
2023-2024 NET Program Changes: Difference between revisions
From WikiNET
m
→Why make changes?
(Created page with "This is a "read ahead" page for NET volunteers and others reviewing proposed changes to the Portland NET program. A feedback survey link will be posted to this page after the presentation on November 8, 2023. == Why make changes? == The NET program has a few long standing creaky problems that should be addressed, '''''and''''' changes are happening (at both the PBEM bureau level and the City government level) that open opportunities and create change factors we should m...") |
|||
| Line 5: | Line 5: | ||
# '''ISSUE:''' '''Not all 2,100 volunteers listed as "active" are actually active;''' we estimate only around 800 volunteers are active. This creates a problem because it inflates our planned response capacity, demoralizes Team Leaders who wonder why nobody is showing up to meetings, and skews any program planning directly related or adjacent to Portland NET. | # '''ISSUE:''' '''Not all 2,100 volunteers listed as "active" are actually active;''' we estimate only around 800 volunteers are active. This creates a problem because it inflates our planned response capacity, demoralizes Team Leaders who wonder why nobody is showing up to meetings, and skews any program planning directly related or adjacent to Portland NET. | ||
<p><span style="color:#ffffff">...</span></p> | |||
# '''ISSUE: NETs need clearer guidance and templates on Operations Planning.''' PBEM began requiring NETs to assemble Ops Plans in 2013, but a lack of clarity has led to products that are inconsistent in what they address and leave teams asking questions about their missions that PBEM has not sufficiently responded to. | # '''ISSUE: NETs need clearer guidance and templates on Operations Planning.''' PBEM began requiring NETs to assemble Ops Plans in 2013, but a lack of clarity has led to products that are inconsistent in what they address and leave teams asking questions about their missions that PBEM has not sufficiently responded to. | ||
<p><span style="color:#ffffff">...</span></p> | |||
#* '''Related problem:''' '''Service area boundaries make no sense.''' For years now, a NET's service area boundaries conform to neighborhood association boundaries. However, those boundaries do not fit with the post-earthquake response capacity available to most teams of NETs. | #* '''Related problem:''' '''Service area boundaries make no sense.''' For years now, a NET's service area boundaries conform to neighborhood association boundaries. However, those boundaries do not fit with the post-earthquake response capacity available to most teams of NETs. | ||
<p><span style="color:#ffffff">...</span></p> | |||
# '''ISSUE: NETs have only ever been deployed through PBEM-managed centralized deployments.''' Since NET started in 1994, there has ''never'' been an emergency for which NETs self-deployed and activated a team ops plan. And in fact, ''every'' deployment has been PBEM directing NETs on where to go and what to do (even if that response was on a small neighborhood scale, such as putting up a perimeter around a down power line). And in fact, the only kind of disaster imaginable that would prompt NETs to self deploy and use an ops plan is a catastrophic city-scale disaster that brought down communications...in other words, an earthquake. | # '''ISSUE: NETs have only ever been deployed through PBEM-managed centralized deployments.''' Since NET started in 1994, there has ''never'' been an emergency for which NETs self-deployed and activated a team ops plan. And in fact, ''every'' deployment has been PBEM directing NETs on where to go and what to do (even if that response was on a small neighborhood scale, such as putting up a perimeter around a down power line). And in fact, the only kind of disaster imaginable that would prompt NETs to self deploy and use an ops plan is a catastrophic city-scale disaster that brought down communications...in other words, an earthquake. | ||
