Activation Protocols: PBEM Initiated Deployments: Difference between revisions

From WikiNET
Jump to navigation Jump to search
(Added links)
m (Adjusted formatting)
 
Line 1: Line 1:
a.    A NET deployment may only be authorized by PBEM, except for the highly unusual circumstances described in 800.25 – Self Deployment or 800.30 – Standing Orders. NETs may not deploy under any other circumstances.
a. A NET deployment may only be authorized by PBEM, except for the highly unusual circumstances described in 800.25 – Self Deployment or 800.30 – Standing Orders. NETs may not deploy under any other circumstances.


b. The assumptions preceding a PBEM initiated deployment are that (1) an emergency or planned event is taking place, (2) NET assistance is needed, and (3) usual communication systems (phone and internet) are still functional. ONLY if communication systems are down should NETs consider the self deployment protocols described in [[Activation Protocols: Self-deployment]].
b. The assumptions preceding a PBEM initiated deployment are that (1) an emergency or planned event is taking place, (2) NET assistance is needed, and (3) usual communication systems (phone and internet) are still functional. ONLY if communication systems are down should NETs consider the self deployment protocols described in [[Activation Protocols: Self-deployment]].


c.    PBEM will use contact information in the NET database to send a deployment authorization message via any means available including phone call, text message (see text box on next page), email,or amateur radio. This message will be addressed to all NET Members or to a specific geographic area based on the nature of the incident. This message will include specific deployment authorization and instructions, or it may contain a request to stand by or stand down.
c. PBEM will use contact information in the NET database to send a deployment authorization message via any means available including phone call, text message (see text box on next page), email,or amateur radio. This message will be addressed to all NET Members or to a specific geographic area based on the nature of the incident. This message will include specific deployment authorization and instructions, or it may contain a request to stand by or stand down.


d.    If PBEM initiates a deployment, PBEM will also update a recorded status message accessible by calling the NET Emergency Activation telephone number (503-823-1410). The message will convey mission instructions, and may include: team(s) assigned, description of specific tasks, time of assignment and estimated completion, specific location or boundaries, how a task is to be accomplished (if appropriate), the purpose of the mission or desired end date. Over the course of the activation, the message will be updated twice daily at 0800 and 2000 hours.
d. If PBEM initiates a deployment, PBEM will also update a recorded status message accessible by calling the NET Emergency Activation telephone number (503-823-1410). The message will convey mission instructions, and may include: team(s) assigned, description of specific tasks, time of assignment and estimated completion, specific location or boundaries, how a task is to be accomplished (if appropriate), the purpose of the mission or desired end date. Over the course of the activation, the message will be updated twice daily at 0800 and 2000 hours.


e. Standard Deployment Protocol: Unless instructed differently by the deployment authorization issued by PBEM, Members:
e. ''Standard Deployment Protocol:'' Unless instructed differently by the deployment authorization issued by PBEM, Members:


* „„ Proceed to their NET Staging Area;
* „„ Proceed to their NET Staging Area;

Latest revision as of 21:34, 1 December 2023

a. A NET deployment may only be authorized by PBEM, except for the highly unusual circumstances described in 800.25 – Self Deployment or 800.30 – Standing Orders. NETs may not deploy under any other circumstances.

b. The assumptions preceding a PBEM initiated deployment are that (1) an emergency or planned event is taking place, (2) NET assistance is needed, and (3) usual communication systems (phone and internet) are still functional. ONLY if communication systems are down should NETs consider the self deployment protocols described in Activation Protocols: Self-deployment.

c. PBEM will use contact information in the NET database to send a deployment authorization message via any means available including phone call, text message (see text box on next page), email,or amateur radio. This message will be addressed to all NET Members or to a specific geographic area based on the nature of the incident. This message will include specific deployment authorization and instructions, or it may contain a request to stand by or stand down.

d. If PBEM initiates a deployment, PBEM will also update a recorded status message accessible by calling the NET Emergency Activation telephone number (503-823-1410). The message will convey mission instructions, and may include: team(s) assigned, description of specific tasks, time of assignment and estimated completion, specific location or boundaries, how a task is to be accomplished (if appropriate), the purpose of the mission or desired end date. Over the course of the activation, the message will be updated twice daily at 0800 and 2000 hours.

e. Standard Deployment Protocol: Unless instructed differently by the deployment authorization issued by PBEM, Members:

  • „„ Proceed to their NET Staging Area;
  • „„ While en route to the NET Staging Area, Members should note damage in the neighborhood and record assessments by using NET Form 1: Damage Assessment. This form will be turned in to the Incident Team Leader present at the NET Staging Area.
  • „„ Once at the NET Staging Area, Member should follow protocols described in 800.35 -
  • Onsite Management Protocols.
Retrieved from "https://volunteerpdx.net/index.php?title=Activation_Protocols:_PBEM_Initiated_Deployments&oldid=4949"