Community Preparedness Team Strategic Plan: Difference between revisions
From Portland NET Wiki
| Line 88: | Line 88: | ||
:''For background on the BEECN program, please visit the [[Basic Earthquake Emergency Communications Nodes (BEECN)#BEECN Program Introduction|BEECN Program Introduction article]].'' | :''For background on the BEECN program, please visit the [[Basic Earthquake Emergency Communications Nodes (BEECN)#BEECN Program Introduction|BEECN Program Introduction article]].'' | ||
==== Goal #1: Pull the BEECN Readiness Score to a consistent 50% quarterly average ==== | ==== BEECN Goal #1: Pull the BEECN Readiness Score to a consistent 50% quarterly average ==== | ||
'''Background:''' The [https://app.smartsheet.com/b/publish?EQBCT=9094103decb2475885daa0b03ac13496 BEECN Readiness Score] is an aggregate score reflecting key deployment readiness factors for each individual BEECN resource and the program as a whole. The Readiness Score in and of itself is not important, but it assesses the viability of elements that make a BEECN resource work, such as volunteers assigned, radio signal strength, deployment status, and more. A low score for a BEECN resource indicates that deploying it in the aftermath of an earthquake is less likely to be successful as there are more points of prospective failure. | '''Background:''' The [https://app.smartsheet.com/b/publish?EQBCT=9094103decb2475885daa0b03ac13496 BEECN Readiness Score] is an aggregate score reflecting key deployment readiness factors for each individual BEECN resource and the program as a whole. The Readiness Score in and of itself is not important, but it assesses the viability of elements that make a BEECN resource work, such as volunteers assigned, radio signal strength, deployment status, and more. A low score for a BEECN resource indicates that deploying it in the aftermath of an earthquake is less likely to be successful as there are more points of prospective failure. | ||
| Line 179: | Line 179: | ||
|} | |} | ||
==== Goal #2: Expand BEECN to include communication nodal points with community based organizations ==== | ==== BEECN Goal #2: Expand BEECN to include communication nodal points with community based organizations ==== | ||
[[File:BEECN COAD merge.jpg|thumb|''Sketching out how PBEM might overlap COADs and BEECNs. The prospective communication chain would run CBO → BEECN → FS → EOC.'']] | [[File:BEECN COAD merge.jpg|thumb|''Sketching out how PBEM might overlap COADs and BEECNs. The prospective communication chain would run CBO → BEECN → FS → EOC.'']] | ||
'''Background:''' Some COAD partner organizations could be developed as BEECN "nodal points"; community locations that report up to BEECN locations. By developing a COAD partner in this way, the communities served by the COAD partner will have improved access to information and other resources in the aftermath of a catastrophic earthquake. | '''Background:''' Some COAD partner organizations could be developed as BEECN "nodal points"; community locations that report up to BEECN locations. By developing a COAD partner in this way, the communities served by the COAD partner will have improved access to information and other resources in the aftermath of a catastrophic earthquake. | ||
{| class="wikitable" style="width:65%" | {| class="wikitable" style="width:65%" | ||
|+ | |+ | ||
! | !ID | ||
!Priority | !Priority | ||
!Objective | !Objective | ||
| Line 213: | Line 213: | ||
|} | |} | ||
==== Goal #3: Improve the resilience of the BEECN program ==== | ==== BEECN Goal #3: Improve the resilience of the BEECN program ==== | ||
'''Background:''' The objectives that follow are not targeted to increase the overall [https://app.smartsheet.com/b/publish?EQBCT=9094103decb2475885daa0b03ac13496 BEECN Readiness Score], but will increase the quality of BEECN programming and ultimately improve service to Portlanders. | '''Background:''' The objectives that follow are not targeted to increase the overall [https://app.smartsheet.com/b/publish?EQBCT=9094103decb2475885daa0b03ac13496 BEECN Readiness Score], but will increase the quality of BEECN programming and ultimately improve service to Portlanders. | ||
{| class="wikitable" style="width:65%" | {| class="wikitable" style="width:65%" | ||
|+ | |+ | ||
! | !ID | ||
!Priority | !Priority | ||
!Objective | !Objective | ||
| Line 275: | Line 275: | ||
The Portland-area '''Community Organizations Active in Disaster (COAD)''' is a network of community-based organizations, nonprofits, small businesses, faith groups, and neighborhood partners working together to strengthen our region’s readiness and response to emergencies. COAD brings people and organizations together ''before'' disasters happen—helping us communicate better, coordinate smarter, and ensure that every community has the support it needs during and after a crisis. | The Portland-area '''Community Organizations Active in Disaster (COAD)''' is a network of community-based organizations, nonprofits, small businesses, faith groups, and neighborhood partners working together to strengthen our region’s readiness and response to emergencies. COAD brings people and organizations together ''before'' disasters happen—helping us communicate better, coordinate smarter, and ensure that every community has the support it needs during and after a crisis. | ||
'''Why COAD Matters''' | |||
When emergencies strike, trusted local organizations are often the first to see emerging needs in their communities. COAD helps prepare partners by providing: | |||
* Stronger coordination during disasters | |||
* Faster, clearer communication between agencies and community groups | |||
* Shared training and resources that build local capacity | |||
* Equitable, community-centered response that reflects local priorities | |||
Together, we can make sure our communities receive timely information, resources, and support—especially those most impacted by emergencies. | |||
==== COAD Goal #1: Build and strengthen cross-sector coordination for disaster preparedness and response ==== | |||
'''Background:''' | |||
{| class="wikitable" style="width:65%" | {| class="wikitable" style="width:65%" | ||
|+ | |+ | ||
! | ! | ||
!Priority | |||
!Objective | !Objective | ||
!Narrative | !Narrative | ||
| Line 284: | Line 299: | ||
|- | |- | ||
| style="width: 5%; text-align:center" |'''<big>COAD 1A</big>''' | | style="width: 5%; text-align:center" |'''<big>COAD 1A</big>''' | ||
| style="width: 20%" | | | | ||
| style="width: 20%" |Establish a formal COAD governance structure with clear roles, decision-making processes, and communication protocols. | |||
'''''Tactical notes''''' | |||
| | | | ||
| | | | ||
| Line 290: | Line 307: | ||
|- | |- | ||
| style="width: 5%; text-align:center" |'''<big>COAD 1B</big>''' | | style="width: 5%; text-align:center" |'''<big>COAD 1B</big>''' | ||
| | |||
| | | | ||
| | | | ||
| Line 296: | Line 314: | ||
|- | |- | ||
| style="width: 5%; text-align:center" |'''<big>COAD 1C</big>''' | | style="width: 5%; text-align:center" |'''<big>COAD 1C</big>''' | ||
| | |||
| | | | ||
| | | | ||
| Line 302: | Line 321: | ||
|- | |- | ||
| style="width: 5%; text-align:center" |'''<big>COAD 1D</big>''' | | style="width: 5%; text-align:center" |'''<big>COAD 1D</big>''' | ||
| | |||
| | | | ||
| | | | ||
| Line 308: | Line 328: | ||
|- | |- | ||
| style="width: 5%; text-align:center" |'''<big>COAD 1E</big>''' | | style="width: 5%; text-align:center" |'''<big>COAD 1E</big>''' | ||
| | |||
| | | | ||
| | | | ||
| Line 314: | Line 335: | ||
|- | |- | ||
| style="width: 5%; text-align:center" |'''<big>COAD 1F</big>''' | | style="width: 5%; text-align:center" |'''<big>COAD 1F</big>''' | ||
| | |||
| | | | ||
| | | | ||
