View source for The temporary issue of equipment from one member to another

=== Step 1: Choose Initiator ===
The person initiating the transaction must be logged into the Rapid Equipment Tracker using their personal CAPID.

The Rapid Equipment Tracker allows members to temporarily assign equipment using either a two-party model or a three-party model. This documentation will cover all scenarios.

==== Two-party model: ====
A member wishes to temporarily issue equipment to another member, and the transaction does not involve a third member like a Commander, Logistics Section Chief or a Logistics Officer. Either the origin or destination member will initiate the temporary issue process.

==== Three-party model: ====
If equipment is issued from one member to another by a third party, like a Commander, Logistics Section Chief, or Logistics Officer. In this scenario, the third party initiates the temporary issue on behalf of the origin or destination member.

=== Step 2: Enter Equipment asset tag ID ===
The member wishing initiate the process must logs in to the Rapid Equipment Tracker app and [[Rapid Equipment Tracker Scan Function|enter]] the [[equipment asset tag ID]] of the equipment to be temporarily issued. The Rapid Equipment Tracker will look for the asset tag ID in O.R.M.S. and, if found, a screen will present some information about the equipment. The member initiating the temporary issue must verify the correctness of the equipment record and, if correct, enter the origin of the equipment.

Examples of asset tag IDs (images needed):

* Foil Asset Tag ID
* Comm Asset Tag ID

=== Step 3: Enter the Origin and Destination of the Equipment ===
The equipment origin can either be a locker (or other central bank of equipment) or a member:

* if the origin is a unit, the initiating member is expected to enter some identifying information about the origin unit. You can enter:
** Full or partial charter in the format REG-WG-XXX, like RMR-CO-136
** Full or partial unit name
** Example: If you're looking for RMR-CO-136 Jefferson County Senior Squadron
*** These phrases would show the unit in search results: Jefferson, Jefferson County, 136, CO-136, RMR-CO-136
*** These phrases would not show the unit in search results: Jeffco, CO136
* If the origin is a member, the initiating member is expected to enter at least some identifying information about the origin member. You can enter:
** Full or partial CAPID
** Full or partial name
** Example: If you're looking for Stephen J. Hughes:
*** These phrases would show the member in search results: Stephen, Steph, Hughes, Hugh, Stephen J Hughes
*** These phrases would <u>not</u> show the member in search results: Steven, Steve, Stephen Hughes, Stephen J. Hughes (because it has a period)

=== Step 4: Choose Start and End Date ===
Choose the start date and end date of the equipment temporary issue.

The default start date is today, and the default end date is seven days after the start date.

=== Step 5: Review and Certify ===
The initiator reviews the transaction and enters their CAPID again (even though they are already logged in) to re-certify they are logged in and they wish to initiate the temporary issue.

=== Step 6: Destination chooses Accept or Reject ===
When the transaction is certified by the initiator in Step 5, notifications are sent as follows:

==== Destination Notifications ====

* If the destination is a member:
** The destination member receives an email prompting the destination member to accept or reject the temporary issue
** The destination member will see pending equipment on the home screen of the Rapid Equipment Tracker
* If the destination is a locker/unit:
** The destination unit does not receive an email
** Any of the unit's (or the unit's higher echelons) commanders, logistics officers, supply officers, or communications officers will see an 'accept' or 'reject' label ''<u>if</u>'' they log in to the Rapid Equipment Tracker and look at the "LG Home" screen

==== Origin Notifications ====

* If the origin is a member:
** If the origin is the same as the initiator: No notification is made to the origin member
** If the origin is different than the initiator: The origin member receives an email notification indicating that a temporary issue was initiated, and it must either be rejected or accepted by the Destination to be considered final
* If the origin is a unit:
** No notification is made to the origin