Operations General Protocols: Difference between revisions

From Portland NET Wiki
Jump to navigation Jump to search
Created page with "Understanding the policies and protocols governing operations for NETs is '''''critical''''' for volunteers to operate safely and effectively. In emergency management, "Operations" refers to the activities and actions carried out to respond to and manage an emergency or disaster. This phase involves implementing the plans and strategies developed during planning and preparation stages. Operations can include tasks such as search and rescue, providing medical care, distri..."
 
mNo edit summary
Line 21: Line 21:


Members should '''''never''''' call in to PBEM to inquire if they are being activated, but instead should follow the protocols in the sections that follow.
Members should '''''never''''' call in to PBEM to inquire if they are being activated, but instead should follow the protocols in the sections that follow.
== Self Determination to Deploy ==
Individual Members maintain personal discretion to deploy when requested by PBEM or under self deployment protocols discussed in 800.25. The decision to deploy following a disaster is a Member’s own, and a Member may never be coerced into deploying. A Member who chooses not to deploy will not be subject to any consequences related to his or her standing in the NET program.
== Activation Protocols: PBEM Initiated Deployments ==
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 Incident Command System (ICS) Forms#NET Form 1: Damage Assessment Form|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.
== Activation Protocols: Self-deployment ==
a.    A key factor for NET Members is the ability to spontaneously organize and activate themselves in the event of a major disaster. If there is a significant earthquake, phones and other communications channels may be interrupted. NET Members will know where to go, how to organize their efforts, and will get to work without any specific order being issued.
b. The assumption preceding a NET self-deployment is that:
# a large citywide emergency is taking place,
# communication systems (such as landlines and cell phones) are inoperative, and
# Members have not received instructions from PBEM and cannot reach the NET Emergency Activation recording.
NETs do not self deploy unless all three conditions are met.
c.  After addressing the responsibilities indicated in [[Responsibilities Prior to Deployment]], Members self deploy to the NET Staging Area following the ''Standard Deployment Protocol'' described in paragraph "e" of [[Activation Protocols: PBEM Initiated Deployments]].

Revision as of 15:09, 9 August 2025

Understanding the policies and protocols governing operations for NETs is critical for volunteers to operate safely and effectively. In emergency management, "Operations" refers to the activities and actions carried out to respond to and manage an emergency or disaster. This phase involves implementing the plans and strategies developed during planning and preparation stages. Operations can include tasks such as search and rescue, providing medical care, distributing essential supplies, helping to manage evacuation procedures, and coordinating with various response agencies and organizations.

Operations: Guiding Principles

In the course of any emergency deployment, NET volunteers must ensure that all chosen actions conform to the following guiding principles:

  1. Safety. A NET Member must never place themselves in an unsafe situation for any reason. Moreover, a NET Member must never be expected to place her or himself in a dangerous situation, or ask other volunteers to do so. NETs will never deploy without personal protective equipment.
  2. Do the greatest good for the greatest number of people in the shortest possible time. NETs are a limited resource. If deployed to an emergency they must carefully and thoughtfully perform the tasks they are assigned. In the event of self-deployment and limited guidance is available, NETs must prioritize where they respond based on considerations for their personal safety, as well as what decisions will preserve the greatest number of lives.
  3. Respond inside the scope of NET training. A NET Member must never undertake, or be asked or expected to undertake, any endeavor for which he or she has not received PBEM approved training. Engaging in activities that a NET Member has not trained for endangers the personal safety of that Member and others. Furthermore, the City’s indemnification policy only protects Members when they respond inside the parameters of PBEM approved training.
  4. Understand the role of NET in an emergency or disaster. NETs are not teams of professional first responders. NETs act as a volunteer extension of first responder services offering immediate help to victims until professional services arrive.
  5. Respect the chain of command. A recognized chain of command – both inside and outside of NET – helps ensure accountability and efficiency during a response.
  6. Document all activities. Documenting activities in an emergency may seem cumbersome and of relatively low priority compared to other responsibilities NETs have during a response. However, proper documentation helps protect NET Members against liability, improves accountability, and saves time (and therefore, lives) for professional emergency responders.

Responsibilities Prior to Deployment

Immediately following any citywide disaster or emergency, NET Members:

  1. Check themselves for injuries and ensure personal safety.
  2. Check in with household Members, ensure their safety, and treat any injuries.
  3. Follow team communication protocols if established.
  4. Put on PPE and retrieve NET kit.
  5. If the disaster is an earthquake, NETs follow appropriate deployment protocols designated by their team's Earthquake Response Framework.

Members should never call in to PBEM to inquire if they are being activated, but instead should follow the protocols in the sections that follow.

Self Determination to Deploy

Individual Members maintain personal discretion to deploy when requested by PBEM or under self deployment protocols discussed in 800.25. The decision to deploy following a disaster is a Member’s own, and a Member may never be coerced into deploying. A Member who chooses not to deploy will not be subject to any consequences related to his or her standing in the NET program.

Activation Protocols: PBEM Initiated Deployments

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.

Activation Protocols: Self-deployment

a.    A key factor for NET Members is the ability to spontaneously organize and activate themselves in the event of a major disaster. If there is a significant earthquake, phones and other communications channels may be interrupted. NET Members will know where to go, how to organize their efforts, and will get to work without any specific order being issued.

b. The assumption preceding a NET self-deployment is that:

  1. a large citywide emergency is taking place,
  2. communication systems (such as landlines and cell phones) are inoperative, and
  3. Members have not received instructions from PBEM and cannot reach the NET Emergency Activation recording.

NETs do not self deploy unless all three conditions are met.

c.  After addressing the responsibilities indicated in Responsibilities Prior to Deployment, Members self deploy to the NET Staging Area following the Standard Deployment Protocol described in paragraph "e" of Activation Protocols: PBEM Initiated Deployments.