Operations at BEECN Sites: Difference between revisions

From Portland NET Wiki
Line 139: Line 139:
!Activity
!Activity
|-
|-
|0530
|0530 - 0600
|Operational Period 1
|Operational Period 1
|Shift One volunteers meet at predetermined meeting point and conduct BEECN site assessment to make sure hazards are clear.
|Shift One volunteers meet at predetermined meeting point and conduct BEECN site assessment to make sure hazards are clear.
|-
|-
|0600
|0600 - 1400
|Operational Period 1
|Operational Period 1
|The Shift One volunteers move the cache from its secure location and set up to begin Shift A operations.
|The Shift One volunteers move the cache from its secure location and set up to begin Shift A operations.
|-
|-
|1330
|1330 - 1400
|Operational Period 1
|Operational Period 1
|Shift B volunteers arrive to relieve Shift A. Shift A turns over message logs and other important information to Shift B.
|Shift B volunteers arrive to relieve Shift A. Shift A turns over message logs and other important information to Shift B.
|-
|-
|1400
|1400 - 2130
|Operational Period 1
|Operational Period 1
|Shift B volunteers commence operations.
|Shift B volunteers commence operations.
|-
|-
|2200
|2130 - 2200
|Operational Period 1
|Operational Period 1
|Shift B volunteers wrap up operations and secure the cache. BEECN operations have concluded for the day.
|Shift B volunteers wrap up operations and secure the cache. BEECN operations have concluded for the day.
|-
|-
|0600
|2200 - 0600
|Operational Period 1
|No activity.
|-
|0600 - 1400
|Operational Period 2
|Operational Period 2
|Shift A volunteers arrive for Operational Period 2. They pull the cache from its storage and begin operations.
|Shift A volunteers arrive for Operational Period 2. They pull the cache from its storage and begin operations.
|-
|-
|1330
|1330 - 1400
|Operational Period 2
|Operational Period 2
|Shift B volunteers arrive to relieve Shift A. Shift A turns over message logs and other important information to Shift B.
|Shift B volunteers arrive to relieve Shift A. Shift A turns over message logs and other important information to Shift B.
|-
|-
|1400
|1400 - 2130
|Operational Period 2
|Operational Period 2
|Shift B volunteers commence operations.
|Shift B volunteers commence operations.
|-
|-
|2200
|2130 - 2200
|Operational Period 2
|Operational Period 2
|Shift B volunteers wrap up operations and secure the cache. BEECN operations have concluded for the day.
|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.
| colspan="3" |...and the 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).


=== Deployment Protocols ===
== Deployment Protocols ==
The radio network for BEECNs is activated 24 to 48 hours following a catastrophic earthquake that has shut down communications systems such as cell phones and landlines. Therefore, BEECN volunteers must expect to self deploy without a direct request from PBEM or other government authority. Volunteers should self-deploy to the BEECN cache and set up at the BEECN site if, and only if, the following conditions are met:
The radio network for BEECNs is activated 24 to 48 hours following a catastrophic earthquake that has shut down communications systems such as cell phones and landlines. Therefore, BEECN volunteers must expect to self deploy without a direct request from PBEM or other government authority. Volunteers should self-deploy to the BEECN cache and set up at the BEECN site if, and only if, the following conditions are met: