Operations at BEECN Sites: Difference between revisions

From Portland NET Wiki
← Older editNewer edit →
VisualWikitext
Line 113: Line 113:


==== Shift One ====
==== Shift One ====
'''So when should a cohort ''first'' activate their BEECN?''' The first BEECN shift of an activation is called "Shift One". PBEM does not expect to activate the BEECN system from the EOC side for 24 to 48 hours after an earthquake. The BEECN cohort should activate inside that timeframe, but the starting point on the clock should either be 0600 or 1400. Therefore, in the Response Framework, BCs can choose when they plan to activate their BEECN from the following options:
'''So when should a cohort ''<u>first</u>'' activate their BEECN?''' The first BEECN shift of an activation is called "Shift One". PBEM does not expect to activate the BEECN system from the EOC side for 24 to 48 hours after an earthquake. The BEECN cohort should activate some time around that timeframe, but the starting point on the clock should either be 0600 or 1400. Therefore, in the Response Framework, BCs can choose when they plan to activate their BEECN from the following options:


* 24 hours post earthquake, rounded forward to 0600
* 24 hours post earthquake, rounded forward to 0600
Line 122: Line 122:
* 48 hours post earthquake, rounded forward to 1400
* 48 hours post earthquake, rounded forward to 1400


'''''For example:''''' let's say a cohort selects "36 hours post event rounded forward to 0600". Now suppose the earthquake hits at 0248 in the morning on March 15. That means the team should aim to have the BEECN deployed by 0600 on March 17.Shift A BEECN Volunteers must decide, as a team, two important things to begin the cycles of BEECN Operations:
'''''For example:''''' let's say a cohort selects "36 hours post event rounded forward to 0600". Now suppose the earthquake hits at 0248 in the morning on March 15. That means the team should aim to have the BEECN deployed by 0600 on March 17.
 
Shift One establishes the timeline and cadence for the incident going forward at that BEECN.
 
Shift One also requires planning considerations different from the other shifts:
 
# '''Shift One Meet Location:''' PBEM does not recommend that Shift One volunteers meet at the BEECN site. Presumably, Shift One volunteers will be the first volunteers on site. But, the earthquake may have rendered the site hazardous and/or the site may be crowded with people looking for help. In either case, it makes the most sense for BEECN volunteers to gather together at a predetermined location and then proceed to the site together for an initial assessment, followed by commencement of BEECN deployment and activation. An ideal meet location may be the home of a volunteer who lives closest to the site, or the Cache Storage Location (if it is offsite).
# '''Shift One FRS/GMRS Channel:''' If BEECN volunteers have access to FRS/GMRS radios, they could be used to speak amongst each other to check in before shift. If the cohort decides to take this route, they should choose an agreed FRS/GMRS channel to speak on.
 
==== Operational Cadence ====
The timing of Shift One establishes the operational cadence at the BEECN to follow. Provided there are no events that interrupt BEECN operations, a response timeline at the BEECN will look like this (in this example, Shift One begins at 0600:
{| class="wikitable"
|+
!Time
!Day
!Activity
|-
|0530
|Operational Period 1
|Shift One volunteers meet at predetermined meeting point and conduct BEECN site assessment to make sure hazards are clear.
|-
|0600
|Operational Period 1
|The Shift One volunteers move the cache from its secure location and set up to begin Shift A operations.
|-
|1330
|Operational Period 1
|Shift B volunteers arrive to relieve Shift A. Shift A turns over message logs and other important information to Shift B.
|-
|1400
|Operational Period 1
|Shift B volunteers commence operations.
|-
|2200
|Operational Period 1
|Shift B volunteers wrap up operations and secure the cache. BEECN operations have concluded for the day.
|-
|0600
|Operational Period 2
|Shift A volunteers arrive for Operational Period 2. They pull the cache from its storage and begin operations.
|-
|1330
|Operational Period 2
|Shift B volunteers arrive to relieve Shift A. Shift A turns over message logs and other important information to Shift B.
|-
|1400
|Operational Period 2
|Shift B volunteers commence operations.
|-
|2200
|Operational Period 2
|Shift B volunteers wrap up operations and secure the cache. BEECN operations have concluded for the day.
|-
| colspan="3" |...and this cycle continues until BEECNs are de-activated by PBEM or the BEECN cohort can no longer continue.
|}
 
 
Shift A BEECN Volunteers must decide, as a team, two important things to begin the cycles of BEECN Operations:


* '''The location they will meet at the beginning of the first shift.''' PBEM recommends that the location ''not'' be the BEECN Site, since it may be crowded with people who need immediate help. Instead, PBEM encourages the first shift to meet at a location out of view from the BEECN site (preferably the BEECN Cache Storage Location if it is a sufficient distance from the BEECN Site).
* '''The location they will meet at the beginning of the first shift.''' PBEM recommends that the location ''not'' be the BEECN Site, since it may be crowded with people who need immediate help. Instead, PBEM encourages the first shift to meet at a location out of view from the BEECN site (preferably the BEECN Cache Storage Location if it is a sufficient distance from the BEECN Site).
Retrieved from "https://volunteerpdx.net/index.php/Operations_at_BEECN_Sites"