Form 37 Rapid Equipment Tracker Event Management - Revision history

RGamber46: Tgamber moved page Form 37 Rapid Equipment Tracker Bulk checkout to Form 37 Rapid Equipment Tracker Event Management: Page rename; we realized the name Bulk Checkout was misleading. It's more about associating equipment with an event.

2025-04-11T20:23:28Z

Tgamber moved page Form 37 Rapid Equipment Tracker Bulk checkout to Form 37 Rapid Equipment Tracker Event Management: Page rename; we realized the name Bulk Checkout was misleading. It's more about associating equipment with an event.

← Older revision	Revision as of 16:23, 11 April 2025
(No difference)

GLawson23: /* Event stand-up */ added event dashboard screenshot

2025-04-11T14:31:10Z

Event stand-up: added event dashboard screenshot

← Older revision		Revision as of 10:31, 11 April 2025
Line 3:		Line 3:

	=== Event stand-up ===		=== Event stand-up ===
	Events allow a person to track equipment which was associated with that event at the time the event began. For example, imagine you're the person in charge of tracking 10 radios for a small Search and Rescue Exercise ("SAREX"). At the conclusion of the event, you want to make sure everyone has either accepted responsibility for the equipment or returned the equipment to you. Here's the basic workflow in the Rapid Equipment Tracker:		Events allow a person to track equipment which was associated with that event at the time the event began. For example, imagine you're the person in charge of tracking 10 radios for a small Search and Rescue Exercise ("SAREX"). At the conclusion of the event, you want to make sure everyone has either accepted responsibility for the equipment or returned the equipment to you. Here's the basic workflow in the Rapid Equipment Tracker:[[File:EventStandUp.png\|thumb]]

	# Create an Event in the Rapid Equipment Tracker app		# Create an Event in the Rapid Equipment Tracker app
	# Associate all 10 equipment IDs of the equipment with the Event		# Associate all 10 equipment IDs of the equipment with the Event
	# Begin recording temporary equipment issues from the Event screen		# Begin recording temporary equipment issues from the Event screen
	~~[[File:EventStandUp.png\|thumb]]~~

	=== Accountability during events ===		=== Accountability during events ===
	At the time a temporary issues are recorded during event stand-up, emails are sent to the recipient asking them to electronically accept or reject the equipment. But, until the recipient accepts or rejects, the equipment is in an ambiguous state: what happens if the equipment is lost? Is it the responsibility of the originator or the recipient?		At the time a temporary issues are recorded during event stand-up, emails are sent to the recipient asking them to electronically accept or reject the equipment. But, until the recipient accepts or rejects, the equipment is in an ambiguous state: what happens if the equipment is lost? Is it the responsibility of the originator or the recipient?
			[[File:EventDashboard.png\|thumb]]

	Following up on these 'loose ends' is critical to ensuring equipment is in positive control at all times. The Rapid Equipment Tracker aids in tying up these loose ends using the event closeout functionality.		Following up on these 'loose ends' is critical to ensuring equipment is in positive control at all times. The Rapid Equipment Tracker aids in tying up these loose ends using the event closeout functionality.

	=== Event stand-down ===		=== Event stand-down ===

GLawson23: /* Event stand-up */ added screenshot

2025-04-11T14:28:37Z

Event stand-up: added screenshot

← Older revision		Revision as of 10:28, 11 April 2025
Line 8:		Line 8:
	# Associate all 10 equipment IDs of the equipment with the Event		# Associate all 10 equipment IDs of the equipment with the Event
	# Begin recording temporary equipment issues from the Event screen		# Begin recording temporary equipment issues from the Event screen
			[[File:EventStandUp.png\|thumb]]

	=== Accountability during events ===		=== Accountability during events ===

NickTest at 00:00, 30 March 2025

2025-03-30T00:00:21Z

← Older revision		Revision as of 20:00, 29 March 2025
Line 21:		Line 21:

	The Logistics manager at the next echelon must then approve the event stand-down.		The Logistics manager at the next echelon must then approve the event stand-down.

	~~[Test edit]~~

NickTest: Testing page editing

2025-03-30T00:00:09Z

Testing page editing

← Older revision		Revision as of 20:00, 29 March 2025
Line 21:		Line 21:

	The Logistics manager at the next echelon must then approve the event stand-down.		The Logistics manager at the next echelon must then approve the event stand-down.

			[Test edit]

RGamber46: Added Familiarization instructions for Bulk Checkout

2025-03-28T21:58:58Z

Added Familiarization instructions for Bulk Checkout

New page

= Purpose =
The Form 37 application was originally designed for temporary equipment issue of individual pieces of equipment. But, events (like Encampments, Wing Conferences, etc.) often involve temporarily issuing dozens of pieces of equipment. It becomes difficult to track individual issues unless the equipment is associated with the event in addition to the originating and destination parties.

=== Event stand-up ===
Events allow a person to track equipment which was associated with that event at the time the event began. For example, imagine you're the person in charge of tracking 10 radios for a small Search and Rescue Exercise ("SAREX"). At the conclusion of the event, you want to make sure everyone has either accepted responsibility for the equipment or returned the equipment to you. Here's the basic workflow in the Rapid Equipment Tracker:

# Create an Event in the Rapid Equipment Tracker app
# Associate all 10 equipment IDs of the equipment with the Event
# Begin recording temporary equipment issues from the Event screen

=== Accountability during events ===
At the time a temporary issues are recorded during event stand-up, emails are sent to the recipient asking them to electronically accept or reject the equipment. But, until the recipient accepts or rejects, the equipment is in an ambiguous state: what happens if the equipment is lost? Is it the responsibility of the originator or the recipient?

Following up on these 'loose ends' is critical to ensuring equipment is in positive control at all times. The Rapid Equipment Tracker aids in tying up these loose ends using the event closeout functionality.

=== Event stand-down ===
As the person in charge of equipment for this event, you must close out the event. Any temporary equipment issues which have not been accepted must be resolved prior to closeout. Here's what the closeout process looks like:

# Viewing the Event status screen in the Rapid Equipment Tracker will show the temporary issue status of all equipment associated with the event. Each piece of equipment associated with the event is listed along with it's Form 37 status.
# When all Forms 37 are moved to 'accepted' or 'rejected' status, the equipment manager initiates event stand-down

The Logistics manager at the next echelon must then approve the event stand-down.