Operations General Protocols - Revision history

GlennDevitt: /* Responsibilities Prior to Deployment */ More formatting

2025-10-21T23:03:14Z

Responsibilities Prior to Deployment: More formatting

GlennDevitt: /* Activation Protocols: Standing Orders */ formatting

2025-10-21T17:12:23Z

Activation Protocols: Standing Orders: formatting

← Older revision		Revision as of 10:12, 21 October 2025
Line 26:		Line 26:

	== Activation Protocols: PBEM Initiated Deployments ==		== Activation Protocols: PBEM Initiated Deployments ==
	~~a. A NET deployment may only be authorized by PBEM, except for the highly unusual circumstances described in Self Deployment or 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]].		# A NET deployment may only be authorized by PBEM, except for the highly unusual circumstances described in Self Deployment or Standing Orders. NETs may not deploy under any other circumstances.
			# 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.		# 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.
			# ''Standard Deployment Protocol:'' Unless instructed differently by the deployment authorization issued by PBEM, Members:
	d. ''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.
	* Proceed to their NET Staging Area;		## Once at the NET Staging Area, Member should follow protocols described in 800.35 -
	* 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.		## Onsite Management Protocols.
	* Once at the NET Staging Area, Member should follow protocols described in 800.35 -
	* Onsite Management Protocols.

	== Activation Protocols: Self-deployment ==		== 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]].		# 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.
			# The assumption preceding a NET self-deployment is that:
			## a large citywide emergency is taking place,
			## communication systems (such as landlines, cell phones, and [https://app.betterimpact.com/Login/Login?returnUrl=/Volunteer/Main/GenericLogOut&agencyGuid=5c003f3a-8d04-4cdf-b8c0-41627fea7871 MIP]) are inoperative, and
			## Members have not received instructions from PBEM. '''NETs do not self deploy unless all three conditions are met.'''
			# 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]].

	== Activation Protocols: Standing Orders ==		== Activation Protocols: Standing Orders ==
Line 57:		Line 50:
	For example, cooling centers need the help of NET Members who have received relevant training. It is more efficient for the organization coordinating cooling centers to directly request NET assistance instead of routing it through PBEM. Standing orders will be approved by PBEM prior to any requests for NET assistance. PBEM will provide a PDF copy of the standing order to the requesting agency and to the NET Members affected by this order. This order will include:		For example, cooling centers need the help of NET Members who have received relevant training. It is more efficient for the organization coordinating cooling centers to directly request NET assistance instead of routing it through PBEM. Standing orders will be approved by PBEM prior to any requests for NET assistance. PBEM will provide a PDF copy of the standing order to the requesting agency and to the NET Members affected by this order. This order will include:

	* Standing Order Agency Name		* Standing Order Agency Name
	* Approved NET missions		* Approved NET missions
	* NET teams or NET Members affected by the order		* NET teams or NET Members affected by the order
	* Standing order expiration date		* Standing order expiration date

	b. When issued, the NET Coordinator will inform all Team Leaders of new standing orders, and will include a list of Members who are approved to deploy under the order.		b. When issued, the NET Coordinator will inform all Team Leaders of new standing orders, and will include a list of Members who are approved to deploy under the order.
Line 66:		Line 59:
	c. All requests for NET assistance via standing order will take place as follows:		c. All requests for NET assistance via standing order will take place as follows:

	* By phone, the requesting agency notifies the PBEM NET Coordinator of their intent to initiate a standing order.		* By phone, the requesting agency notifies the PBEM NET Coordinator of their intent to initiate a standing order.
	* Requesting agency then sends an email to NETs with information about where and when NETs should gather to provide assistance, and the NET Coordinator must be copied. This email MUST have a PDF copy of the valid and pre-approved standing order attached, or the request is not valid.		* Requesting agency then sends an email to NETs with information about where and when NETs should gather to provide assistance, and the NET Coordinator must be copied. This email MUST have a PDF copy of the valid and pre-approved standing order attached, or the request is not valid.
	* Requesting agency may then follow-up with volunteers by phone; but, not before the request is emailed as described in the above step.		* Requesting agency may then follow-up with volunteers by phone; but, not before the request is emailed as described in the above step.

Line 96:		Line 89:
	a. During an emergency deployment, all NET Members must abide by reasonable and safe direction given from any emergency response personnel (such as police, fire, or EMS personnel) regardless of their jurisdiction of origin; Members of the military; emergency managers associated with a City of Portland bureau (e.g. the Portland Water Bureau); or staff from PBEM.		a. During an emergency deployment, all NET Members must abide by reasonable and safe direction given from any emergency response personnel (such as police, fire, or EMS personnel) regardless of their jurisdiction of origin; Members of the military; emergency managers associated with a City of Portland bureau (e.g. the Portland Water Bureau); or staff from PBEM.

	b. Team Members take direction from Incident Team Leaders, and follow a line of authority that proceeds to Members with authority delegated by the Incident Team Leader (such as Assistant Team Leaders). See Figure 5 below.		b. Team Members take direction from Incident Team Leaders, and follow a line of authority that proceeds to Members with authority delegated by the Incident Team Leader (such as Assistant Team Leaders). See Figure 5 below. The first NET Member at the NET Staging Area will act as Incident Team Leader until the Member most qualified to act as Incident Team Leader arrives on stage.
	c. The first NET Member at the NET Staging Area will act as Incident Team Leader until the Member most qualified to act as Incident Team Leader arrives on stage.

	d. Incident Team Leaders take direction from emergency responders working under the direction of an Incident/Unified Commander (IC).		d. Incident Team Leaders take direction from emergency responders working under the direction of an Incident/Unified Commander (IC).

GlennDevitt: /* Activation Protocols: PBEM Initiated Deployments */

2025-10-21T17:02:22Z

Activation Protocols: PBEM Initiated Deployments

← Older revision		Revision as of 10:02, 21 October 2025
Line 26:		Line 26:

	== Activation Protocols: PBEM Initiated Deployments ==		== 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.		a. A NET deployment may only be authorized by PBEM, except for the highly unusual circumstances described in Self Deployment or 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]].

GlennDevitt: /* Activation Protocols: PBEM Initiated Deployments */ Removed activation line phone number

2025-10-21T16:59:56Z

Activation Protocols: PBEM Initiated Deployments: Removed activation line phone number

← Older revision		Revision as of 09:59, 21 October 2025
Line 32:		Line 32:
	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. ''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;
			* 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.
	* Proceed to their NET Staging Area;		* Once at the NET Staging Area, Member should follow protocols described in 800.35 -
	* 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.		* Onsite Management Protocols.

	== Activation Protocols: Self-deployment ==		== 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.		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:		b. The assumption preceding a NET self-deployment is that:

Net@portlandoregon.gov at 23:17, 9 August 2025

2025-08-09T23:17:09Z

← Older revision		Revision as of 16:17, 9 August 2025
Line 106:		Line 106:

	[[File:Figure 5 Typical Onsite Chain of Command in a NET.png\|400px]].		[[File:Figure 5 Typical Onsite Chain of Command in a NET.png\|400px]].

			== Indemnification ==
			Subject to the conditions and limitations of the Oregon Constitution and Oregon Tort Claims Act, ORS 30.260 through 30.300, the City shall indemnify, defend and hold harmless a NET Member for any tort claim arising out of a NET Member’s act or omission within the course and scope of the NET Member’s duties while the NET Member is performing emergency service activities under the direction of PBEM in connection with a state of emergency declared under ORS 401.309, or during a state of public health emergency proclaimed under ORS 433.441, or while the NET Member is engaged in training being conducted or approved by PBEM for the purpose of preparing the NET Member to perform emergency services, or while a NET Member is participating in non-emergency deployment activities with PBEM’s prior approval.

			To interpret in plainer language: NET volunteers are protected from liability by the City of Portland when deployed under the conditions of these Guidelines and are engaging in activities for which they have received PBEM approved training.

			== Media Requests ==
			All requests from the media to speak on the record about an emergency must be relayed to the PBEM NET Coordinator for approval. Unless authorized by PBEM, NET Members may not interview with media representatives or answer media questions about the emergency.

			== Volunteer Deployment Outside Portland City Limits ==
			Effective July 18 2023, NET volunteer indemnification is preserved both inside and outside of Portland city limits (under older policy, indemnification was preserved only inside Portland city limits).<ref>https://hcpaw.portlandoregon.gov/u/y6G8LiIhvAXZobwt/72e79110-8465-4655-a45c-0208208e03b3?l</ref> ''However'', other conditions of indemnification still apply: volunteers still have to be deployed by PBEM (or under self deployment policy) and they must be taking action PBEM them trained them to do.

Net@portlandoregon.gov: /* General Onsite Management Protocols */

2025-08-09T23:13:45Z

General Onsite Management Protocols

← Older revision		Revision as of 16:13, 9 August 2025
Line 73:		Line 73:


	=== General Onsite Management Protocols ===
			== General Onsite Management Protocols ==
	a. The presumption following these Onsite Management Protocols is that NETs have arrived at the NET Staging Area after following the Standard Deployment Protocol (800.20.e).		a. The presumption following these Onsite Management Protocols is that NETs have arrived at the NET Staging Area after following the Standard Deployment Protocol (800.20.e).

Net@portlandoregon.gov at 23:11, 9 August 2025

2025-08-09T23:11:45Z

@@ Line 73: / Line 73: @@
-== General Onsite Management Protocols ==
+=== General Onsite Management Protocols ===
 a.  The presumption following these Onsite Management Protocols is that NETs have arrived at the NET Staging Area after following the Standard Deployment Protocol (800.20.e).
@@ Line 93: / Line 93: @@
 j. At all other times when possible, NETs should make appropriate documentation of all activities. See [[NET Incident Command System (ICS) Forms|ICS Forms]] or copies of forms to use and instructions.

Net@portlandoregon.gov: /* Activation Protocols: Standing Orders */

2025-08-09T23:11:24Z

Activation Protocols: Standing Orders

← Older revision		Revision as of 16:11, 9 August 2025
Line 71:		Line 71:
	* Requesting agency then sends an email to NETs with information about where and when NETs should gather to provide assistance, and the NET Coordinator must be copied. This email MUST have a PDF copy of the valid and pre-approved standing order attached, or the request is not valid.		* Requesting agency then sends an email to NETs with information about where and when NETs should gather to provide assistance, and the NET Coordinator must be copied. This email MUST have a PDF copy of the valid and pre-approved standing order attached, or the request is not valid.
	* Requesting agency may then follow-up with volunteers by phone; but, not before the request is emailed as described in the above step.		* Requesting agency may then follow-up with volunteers by phone; but, not before the request is emailed as described in the above step.


			== General Onsite Management Protocols ==
			a. The presumption following these Onsite Management Protocols is that NETs have arrived at the NET Staging Area after following the Standard Deployment Protocol (800.20.e).

			b. Upon arrival at the NET Staging Area, Members should integrate with the present chain of command. If no chain of command has been established, NETs on the scene should designate an Incident Team Leader and develop a chain of command as prescribed in the NET’s [[NET Operations Plans\|Operations Plan]].

			c. NET Members will turn in their damage assessment form to the Incident Team Leader. The Incident Team Leader will work with Team Members to prioritize incidents and assign tasks.

			d. The Amateur Radio Operator (ARO) will attempt to reach the Multnomah County ARES Resource Net and the PBEM NET Coordinator. Refer to Section 900 for communications protocols.

			e. Team Members deploy to assignments. Once an assignment is completed, Team Members will return to the NET Staging Area to debrief and receive further instructions.

			f. Members are NEVER deployed to assignments alone. Members work in functional teams that consist of no fewer than two volunteers.

			g. The Incident Team Leader (or designee) should develop a relief plan. No NET Member should work more than a 12 hour shift in a 24 hour period. Incident Team Leaders should receive guidance on the length of relief schedules from the ECC if possible.

			h. If emergency responders arrive on scene or communication is established with the ECC through radio or other means, the Incident Team Leader will report activities and request instructions.

			i. NETs may receive, and must abide by, a “stand-down” order from any emergency response personnel (such as police, fire, or EMS personnel) regardless of their jurisdiction of origin; Members of the military; emergency managers associated with a City of Portland bureau (e.g. the Portland Water Bureau); or staff from PBEM.

			j. At all other times when possible, NETs should make appropriate documentation of all activities. See [[NET Incident Command System (ICS) Forms\|ICS Forms]] or copies of forms to use and instructions.

Net@portlandoregon.gov: /* Activation Protocols: Self-deployment */

2025-08-09T23:10:22Z

Activation Protocols: Self-deployment

← Older revision		Revision as of 16:10, 9 August 2025
Line 53:		Line 53:

	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]].		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]].

			== Activation Protocols: Standing Orders ==
			a. PBEM may, in rare circumstances, authorize an outside agency or organization to directly contact and deploy NETs or NET Members. This is called a standing order. Standing orders are used when PBEM is not involved in the emergency incident; however, there is a clear and pre-approved mission for NET assistance.

			For example, cooling centers need the help of NET Members who have received relevant training. It is more efficient for the organization coordinating cooling centers to directly request NET assistance instead of routing it through PBEM. Standing orders will be approved by PBEM prior to any requests for NET assistance. PBEM will provide a PDF copy of the standing order to the requesting agency and to the NET Members affected by this order. This order will include:

			* Standing Order Agency Name
			* Approved NET missions
			* NET teams or NET Members affected by the order
			* Standing order expiration date

			b. When issued, the NET Coordinator will inform all Team Leaders of new standing orders, and will include a list of Members who are approved to deploy under the order.

			c. All requests for NET assistance via standing order will take place as follows:

			* By phone, the requesting agency notifies the PBEM NET Coordinator of their intent to initiate a standing order.
			* Requesting agency then sends an email to NETs with information about where and when NETs should gather to provide assistance, and the NET Coordinator must be copied. This email MUST have a PDF copy of the valid and pre-approved standing order attached, or the request is not valid.
			* Requesting agency may then follow-up with volunteers by phone; but, not before the request is emailed as described in the above step.

Net@portlandoregon.gov at 23:09, 9 August 2025

2025-08-09T23:09:47Z

← Older revision		Revision as of 16:09, 9 August 2025
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]].