AFMAN23-110V2PT13CH3.pdf

CHAPTER 3

CUSTOMER REQUIREMENTS

Section 3A—CHAPTER OVERVIEW.

3.1. Chapter Overview. In this chapter, we discuss the policy, process, and procedures applicable to retail supply customer requests for supplies and equipment, management of customer backorders, and the creation and management of bench stock accounts. The remainder of this chapter is organized into three sections: Customer Requests, Backorder Management, and Bench Stock Management.

3.1.1. Section 3B. Customer Issue Requests. In this section we discuss the policy and processes applicable to customer requests for supply and equipment items. We explain how customer requests are prioritized and the process for requesting special/unique items from the Logistics Readiness Squadron (LRS)/supply activity. Lastly, we detail the submission methods for customer requests to the LRS/supply activity.

3.1.2. Section 3C. Customer Backorders. This section describes the processes and procedures asso-ciated with backorder management. We discuss the how a customer due-out is created in the retail supply system. Then, we discuss the due-out follow-up process. Finally, we explain the customer due-out validation process.

3.1.3. Section 3D. Bench Stock Management. This section provides an overview of the policies and processes underlying Bench Stock Management. We start with a general discussion of customer bench stock accounts. Then, we explain the policies and procedures for the establishment of bench stock accounts, the bench stock re-supply process, and the bench stock review process.

Section 3B—CUSTOMER ISSUE REQUESTS.

3.2. Section Overview . This section details the responsibilities and processes related to the placement of customer requests via the retail supply system. The retail supply system supports many different types of customer requests, for example—supplies, bench stock, supply point, equipment, Special Purpose Recoverable Authorized Maintenance (SPRAM), and special/ unique items. The priority assignment and submission of customer requests are also discussed in this section.

3.2.1. Types of Customer Issue Requests. Air Force policy requires that base customer requests for supplies and equipment items be submitted to the retail supply system. Refer to Attachment 3B-1 for an illustration of customer issue requests process flow in the retail supply system. Customers that need supplies from the retail supply system submit either expedite or routine issue requests. See Attachment 3B-2 for customer issue request submission methods. Normally, the AF Form 2005 is used to prepare customer issue requests. See Attachment 3B-3 for AF Form 2005 preparation details. Expedite requests represent an urgent need for an asset from Supply in order to prevent a work stoppage or other mission degradation situation. Routine requests are used for items that do not normally cause any type of work stoppage or mission degradation. Regardless of the type of cus-tomer request, Supply customers must identify specific data elements associated with a request, such as—the priority, force activity designator ((FAD)—see Attachment 3B-5), urgency justification code ((UJC)—see Attachment 3B-6), mark-for (see Attachment 3B-7), item identification, job order number, etc.

3.2.1.1. Expedite Customer Issue Requests. Expedite customer issue requests are used when materiel is required to satisfy mission requirements in a short period of time. Expedite customer 3–1

AFMAN 23-110 Volume 2 Part 13, Chapter 3 issue requests have an urgency of need designator (UND) code equal to ‘A’ or ‘B’ and are nor-mally assigned a supply response priority of 01 thru 04. Refer to Attachment 3B-5 for additional explanation about UND codes. Note high priority issue requests increase the overall costs of sup-ply support by increasing transporting and handling costs. To minimize these costs, make sure the UND assigned is consistent with the urgency of need (reference AFI 23-111 and AFI 16-301).

Misuse of priority designators adversely affects the integrity of the retail supply system, wastes resources, and degrades the overall supply support you receive.

3.2.1.1.1. Supply Response Priorities. The supply response priorities (determined by the cus-tomer) are used to indicate the maximum time that may elapse from the time the Logistics Readiness Squadron/supply activity receives the customer request until the customer physi-cally receives the materiel. Additionally, customers must specify an appropriate supply response priority for orders. The Supply response priorities (01 thru 07) denote the maximum time that may elapse before assets are delivered to the customer. Each installation/base may set-up local procedures to outline specific delivery routes and scheduled delivery times to meet customer supply response priorities. Refer to Attachment 3B-4 for an explanation of the supply response priorities.

3.2.1.1.2. Mission Capable (MICAP) Customer Requests. MICAP customer requests are the highest priority type of expedite request and are used to order parts required for the repair of mission essential equipment. The first position of the urgency justification code (UJC) equal to slash (/), one (1), or J denotes MICAP customer requests in the retail supply system.

Requests for items to satisfy MICAP conditions are processed in the retail supply system as “Fill” or “Kill”. If the requested item(s) are available in stock, they are issued to customer and no further action is required. However, if assets are not available, the supply customer must provide specific details about the order that alert the LRS/supply activity a MICAP condition exists. When a MICAP condition exists, the supply customer provides the appropriate MICAP UJC as part of the customer order verification process. The UJC identifies the requested item to a specific end item, mission or type of issue request. Refer to Attachment 3B-6 for list of authorized MICAP UJCs.

3.2.1.1.3. Awaiting Parts (AWP) Customer Requests. AWP customer requests identify mate-riel needed to repair other spares. Urgency justification code (UJC) ‘AR’ and ‘BR’ denote AWP requests in the retail supply system. AWP customer requests may be placed for expend-able (bit and piece) or shop replacement unit (SRU) items required to repair a line replace-ment unit (LRU). The end item application must be entered on AWP requests. When items required to satisfy AWP customer requirements are not available from retail supply system stocks, the requests are normally backordered.

3.2.1.2. Routine Customer Issue Requests. Routine customer issue requests are assigned an urgency of need designator (UND) equal to “C” and normally have a supply response priority 05 or higher. Routine customer issue requests do not normally cause work stoppages or mission deg-radation. Examples of routine customer requests may include paint products, rags needed for rou-tine maintenance, furniture, pens, paper, and other assorted supplies and equipment. Bench stock issue requests are normally considered routine requests. Refer to section 3D for a discussion of the bench stock support process.

3.2.2. Requests for Special/Unique Items. There are times when supply customers need to order spe-cial/unique items in order to accomplish the mission. The following items are classified as special/ unique: Civil Engineer-managed assets, ammunition, local manufacturer, local purchase, Defense 3–2

Reutilization Marketing Office (DRMO) assets, continuous forms, hazardous materiel, and Govern-ment Purchase Card (GPC) purchases. The GPC process authorizes the customer to purchase autho-rized supplies, equipment, and non-personal services. The local LRS Commander/Chief of Supply may provide additional instructions for GPC purchases. Refer to AFI 64-117 for specific guidance on the use of the GPC (formerly known as the Air Force Government Purchase Card Program). Refer to Attachment 3B-8 for the procedures to request special/unique items. When requesting items that contain hazardous or potentially hazardous material, the Base Bioenvironmental Engineer must approve the item for use before you submit your request to the LRS/supply activity. See Attachment 3B-10 for the information used to identify hazardous materials.

3.2.3. Requests for Non-NSN/Local Purchase Items. Some expedite, routine, and local purchase customer requests are for non-stock listed items. That is, the item part number (if applicable) may not cross reference to a stock number. In these instances, supply customers submit a DD Form 1348-6 (non-NSN requisition, manual) to the LRS/supply activity. To ensure the correct item is ordered, sup-ply customers should make every effort to provide complete item descriptive information. Such information includes the price, allowable price tolerances, and suggested sources of supply. Refer to Attachment 3B-9 for DD Form 1348-6 preparation instructions.

3.2.4. Supply Point Customer Requests. Supply points are forward stockage locations managed by the LRS/Supply activity. Supply point customer issue requests are made to the retail supply system using basically the same process as described for expedite issue requests. The main differences are the transaction identifier code is MSI, the customer must enter specific information in the mark-for field on the issue requests to indicate which supply point detail record will satisfy (issue from) the customer request, and due to the physical location of the assets (within the maintenance organization), supply point issues are categorized as over the counter requests.

3.2.4.1. Advantages of Maintaining Supply Points. The purpose of supply points is to forward warehouse supply stocks, thus making the assets more readily available to using activities. Sup-ply points are set up via coordination between the LRS/supply activity and the applicable Mainte-nance Control Officers or other appropriate organizational managers. The supported organization is responsible for the overall management of the supply point assets within their possession. The management includes—assists supply personnel during the scheduled inventories, maintain sup-ply discipline when ordering assets from the supply point, ensuring assets placed on supply points are serviceable inventories, and must provide secure space and facilities to store supply point assets.

3.2.4.2. Supply Point Qualification. Items stocked in supply points are usually assets peculiar to the needs of the activity being supported; however, items common to more than one Maintenance function may be stocked in a supply point. Any item(s) of supply except equipment items (ERRCD NF, ND) are authorized for stockage in supply points. Prior approval from the LRS/sup-ply activity is required before stocking expendable items (ERRCD equal XB3) in supply points.

3.2.4.3. Supply Point Establishment Requests. Organizations requesting the establishment of a supply point must submit a list of desired items to the LRS/supply activity. This list shall include all assets to be stored in the supply point and include the following item information: stock num-ber, part number, nomenclature, end item application (i.e., weapon system, end item, or equip-ment), and identify if functional check is required for the assets.

3.2.4.4.Supply Point Adjusted Stock Level (ASL) Requests. Supply point assets are forward stock and must be supported by positive requisitioning objective. Therefore, there may be times when a 3–3 supply customer is asked by the LRS/supply activity personnel to prepare and submit an ASL request to establish and maintain a supply point stock level. Failure to submit the ASL could delay supply point support. See Chapter 19 for ASL request submission (AF Form 1996) instruc-tions.

Section 3C—CUSTOMER BACKORDERS.

3.3. Section Overview. This section describes how supply customers can monitor their backorders for supplies and equipment in the retail supply system. In this section, we discuss the customer due-out pro-cess, including the procedures for creating, modifying, and canceling customer backorders. We discuss the funding implications when due-outs are created and cancelled. We then explain the due-out follow-up process in the retail supply system. Lastly, we detail the customer due-out validation process.

3.3.1. Creating Customer Backorders (Due-Outs). Customer backorders (due-outs) are created in the retail supply system as necessary when customer requirements cannot be immediately satisfied from stock. Refer to Attachment 3C-1 for details about the customer backorder process flow in the retail supply system. To place a backorder, customers must provide specific information about their order request to ensure the backorder is correctly created in the retail supply system. The customer must ensure their organizational account has sufficient funds available to pay for the requested item, if nec-essary. Note for O&M funded items, the creation of a backorder commits the customer’s funds. In addition to providing basic order request information (stock number, required quantity, organization and shop code, etc.), customers must ensure the appropriate urgency justification code (UJC) is entered on the order requests. See Attachment 3B-6 for additional details about the UJC. Note some UJC(s) causes an automatic backorder in the retail supply system when no assets are available in the LRS/supply activity.

3.3.2. Modifying Customer Backorders. There may be times when supply customers may need to change data on an existing backorder in the retail supply system. To request modification of a backo-rder, customers should contact the LRS/supply activity (Customer Service, Stock Control, or desig-nated OPR). The following elements may be changed on customer backorders: supplementary address, project code, force activity designator (FAD), urgency justification code (UJC), required delivery date (RDD), and mark-for. Once the requested changes are processed by Supply personnel, the retail supply system sends the appropriate transactions to update any applicable requisition for that backorder to the source of supply.

3.3.3. Canceling Customer Backorders. Customers may request cancellation of existing backorders when necessary. To request cancellation, customers submit request to the LRS/supply activity (e.g., Customer Service, Stock Control, or designated OPR). The cancellation requests may be submitted via written correspondence, telephone call, or identified for cancellation on one of the backorder review listings (daily document listing (D04), priority monitor report (D18), etc., The Cancellation requests shall include: 1) the stock number; 2) the due-out document number; 3) the cancellation quantity; 4) and the maintenance action taken code and net repair cycle days if item falls under DIFM control (refer to Part 13, Chapter 6).

3.3.3.1. Funding Implications for Backorder Cancellation. There are instances when customers are still charged for an item, even if a cancellation is requested. The charge to the supply cus-tomer is called a direct charge (Document identifier code = 1PU). When a direct charge is applied, it denotes the AF Stock fund incurred expenses that cannot be recovered, therefore, the customer still must be charged for the requested item. Refer to Attachment 3C-2 for details 3–4 about canceling customer backorders and the rules used by the retail supply system for granting credit.

3.3.3.2. Reversing Direct Charges from Customer Accounts. The LRS/supply activity’s Supply Management Activity Group (SMAG) manager is the approval authority for the reversal of direct charges from a customer’s account in the retail supply system. Once approval has been granted, the SMAG manager submits a written request (including the reasons for reversal and other rele-vant information) to the LRS/supply activity to take reversal actions in the retail supply system and credit the customer’s account. The following are some valid circumstances for requesting the reversal of a direct charge from a customer’s account.

3.3.3.2.1. Customer backorder erroneously canceled by Logistics Readiness Squadron/supply activity personnel.

3.3.3.2.2. Quantity errors made on the input of a backorder cancellation input by Logistics Readiness Squadron/supply activity resulting in cancellation and applying the direct charge.

3.3.3.2.3. Customer erroneously canceled a backorder that can be re-established or the can-celled item can be issued to the customer without penalty to the SMAG.

3.3.4. Backorder Review and Validation Process. Supply customers are responsible for periodically reviewing their backorders in the retail supply system to ensure all backordered items are still needed.

This review is vital, because it affects customer funds and the availability of applicable weapon sys-tems, end items, and equipment. The review is conducted between the LRS/supply activity and the supply customer. When backorder items are no longer required, cancellation should be requested.

Refer to Attachment 3C-3 for the procedures to accomplish the backorder review and validation pro-cess.

3.3.5. Backorder Follow-Up Process. Customers should contact the LRS/supply activity (designated OPR) to follow-up on the supply status of existing firm customer backorders when the expected delivery date is not satisfactory. Requests for follow-up may be submitted in writing or by telephone.

The requests must include the stock number, the document number (from the issue request), the quan-tity requested, the requisition number (if known), and a mission impact statement. The mission impact statement communicates the mission impacts attributable to the non-availability of the item on backorder. The LRS/supply activity determines the status of the backordered item, including what actions have been taken by the depot to satisfy the backorder requests, and provides a response to the customer.

3.3.6. Requesting Improved Status via Supply Difficulty Reporting. When deficiencies resulting from a delay in item support (outstanding requisition) cannot be corrected locally and will ultimately affect the operational capability of the base or unit, supply customers prepare and submit an AF Form 1667, Supply Difficulty Report. The requesting organization must fill out blocks 1 through 8 and for-ward the report to the LRS/supply activity (designated OPR). The LRS/supply activity will complete the form before submitting it to the source of supply. Refer to Part 13, Chapter 6 for further details about the supply difficulty report process.

Section 3D—BENCH STOCK MANAGEMENT.

3.4. Section Overview. Bench stocks are generally comprised of low cost, expendable items (assigned ERRCD = XB3), non-hazardous, high use items that are physically located and stored within the mainte-nance work area. The bench stock process was designed as an efficient and effective method for increas- 3–5 ing mission support. The main advantages of a customer bench stock account are 1) the ready availability of items when needed and 2) the reduced administrative burden (no paperwork) to customers using the assets. This section describes the processes for supply customers to manage their supply bench stock accounts. We detail the bench stock procedures for establishing and re-supplying organizational bench stocks, and the bench stock review process.

3.4.1. Set-Up of Bench Stock Account. Setting up a bench stock is a joint effort between the cus-tomer organization and LRS/supply activity. The supported organization must coordinate with the LRS/supply activity to communicate what types of items are authorized on bench stock, to set up a maximum dollar threshold, and to identify the bench stock location. The supported organization’s commander must submit a letter to the LRS/supply activity to request a maximum dollar threshold be established for the bench stock account. The threshold identifies a ceiling/cap on the unit price for an item on the bench stock account. The maximum dollar threshold may vary from organization to orga-nization and is at the discretion of the supported organizational commander. Some considerations for that decision should include: Proximity to the main supply warehouse where the stock is kept, cost of the items and the levels desired, frequency of the demand for the items, and mission impact if the items are not readily available. The retail supply system alerts the user when the bench stock account threshold is breeched. When a breech occurs, the LRS/supply activity (responsible OPR) notifies the bench stock organization to validate if they want to override the threshold or not. The applicable Group Commander’s approval is required in order to exceed the established maximum dollar thresh-old for any item. LRS/supply activity will maintain deviation approval letters in file as long as the dollar threshold for the items exceed the current approval maximum dollar threshold for that organi-zation. Refer to, Chapter 11 for an explanation of the bench stock process used in the LRS /supply activity.

3.4.2. Bench Stock Maintenance Responsibilities. Organizational customers and LRS/Supply per-sonnel must perform a variety of duties to effectively maintain a bench stock account. Refer to Attachment 3D-1 for an explanation of those specific responsibilities. Also, see, Chapter 11 for additional details about the bench stock process.

3.4.3. Organizational Initiation of Bench Stock Replenishments. There are instances when mainte-nance activities assume some the LRS/Supply responsibilities for initiating bench stock replenish-ments. When the customer assumes the responsibilities, they call in the replenishment needs to the LRS/supply activity. After making the call, they annotate the customer's AF Form 465, Bench Stock Inventory, with the date of the call and person contacted. This form is then filed in date sequence within the customer’s organization. The supported organization screens the Daily Document Register (D04) to make sure issue requests for bench stock replenishments are processed. Listed below are the instances that apply when the supported organization is authorized to maintain bench stock accounts in lieu of the LRS/supply activity.

3.4.3.1. Organizational Bench Stock Access Restrictions. When access restrictions apply (secure area, etc.) or when authorized by the Logistics Group Commander (or equivalent), the LRS/sup-ply activity commander may agree to allow the supported activity to assume LRS/supply activity replenishment initiation responsibilities. Refer to Attachment 3D-1 for a list of those responsi-bilities.

3.4.3.2. Off-Base Supported Organizations. Unless specifically included in a joint tenancy agree-ment, or some specific directive, the LRS/supply activity will not perform walk-thru, inventory, deliver or bin property bench stock assets to off-base organizations.

3–6

3.4.4. Bench Stock Review Process. Supply customers must periodically review their bench stocks to ensure they have the right mix of items to support their needs. The two review products used for the review are the Monthly Bench Stock Review (M04 List) and Semi-Annual Bench Stock Review (S04). See Chapter 11 for additional details about the monthly and semi-annual reviews.

3.4.4.1. Monthly M04 Review. Each month, LRS/supply activity personnel will provide the sup-ported bench stock organization with the M04 listing. The M04 listing contains bench stock rec-ommended adds/changes/and deletes. The customer should 1) review each add, change, and delete recommendation to determine if they accept the recommended changes to their bench stock account, 2) annotate the changes (if any) on the listing, and 3) sign and return the listing to the LRS/supply activity. If the customer does not want any of the recommended changes, then no action is required.

3.4.4.2. Semi-Annual S04 Review. The semi-annual bench stock review (S04) is also a listing of recommended adds/changes/and deletes. It differs from the monthly review in that it’s a formal review between the LRS/supply activity and the supported organization. Once the semi-annual review is completed, the supported organization signs the S04 listing to the LRS/Supply activity.

LRS/Supply personnel will make the necessary changes (if any) in the retail supply system.

3.4.4.3. Requesting Bench Stock Adds/Changes/Deletes. In addition to the scheduled reviews (monthly and semi-annul), supply customers may request additions, deletions, and changes to bench stocks by telephone, informal memo, or formal correspondence. Requests for bench stock additions, deletions, or changes do not require review, approval, or justifications. Special empha-sis should be placed on adding items to bench stocks that are normally used in a different quantity unit pack than the unit of issue (e.g., bolts, nuts, screws, rivets, wire, etc.).

3–7

ATTACHMENT 3A-1

RESERVED

3A1.1. Reserved for Future Use.

3–8

ATTACHMENT 3B-1

CUSTOMER ORDER REQUEST PROCESS FLOW

3B1.1. Purpose. To illustrate the customer order process flow in the retail supply system.

3–9

Figure 3B1.1. Customer Order Request Process.

3–10

ATTACHMENT 3B-2

SUBMISSION METHODS FOR CUSTOMER REQUESTS

3B2.1. Purpose. To explain the authorized methods of customer requests submission and call-in points for customer requests to the LRS/Supply Activity.

3–11

Table 3B2.1. Submission Methods & Call-In Locations.

Type of Request Submission Methods Call In Point Location (LRS/

Supply Activity) Expedite (Del Priority < 05)

MICAP/AWP

Supply Point

Radio, telephone, intercom, tele-type, mail, system interface (IMDS/G081), in person, or any medium available

Required submission form: AF Form 2005 (Issue/Turn-In Requests)

Demand Processing, Customer Service, Flight Service Center (Supply Point Requests Only)

Routine (Del Priority > 04) Radio, telephone, intercom, tele-type, mail, system interface (CAMS/G081), in person, or any medium available

Required submission form: AF Form 2005 (Issue/Turn-In Requests)

Demand Processing, Customer Service

Bench Stock Replenishments Bench Stock Support, Customer Service Equipment Refer to Part 13, Chapter 8 Equipment Management SPRAM Refer to Part 13, Chapter 8 Required submission form: AF Form 2005 (Issue/Turn-In Requests)

Equipment Management

Janitorial & Office Supplies (pens/ paper/etc), In Person Retail Sales, Base Service Store

Military Clothing (Individual Equip-ment Items)

In Person Individual Equipment Ele-ment 3–12

ATTACHMENT 3B-3

SAMPLE AF FORM 2005-ISSUE/TURN-IN REQUEST (SUBMISSION FORM)

3B3.1. Purpose. To list the AF Form 2005 as a sample and to provide instructions for preparing the form.

3–13

3–14

Figure 3B3.1. Sample copy of an AF Form 2005.

Table 3B3.1. Instructions for Preparing the AF Form 2005-Issue/Turn-In Request.

POSITION NUM-

BER

ENTRY

Block A Name of requesting individual and telephone number.

1-3 Transaction Identification Code (TRIC)

For expedite and routine issue requests, the TRIC is an ISU.

For issues from a supply point, the TRIC is an MSI. Note the MSI and ISU transactions require the same input data elements.

4-6 Delivery destination.

7 Issue Exception Code (IEX). Enter the IEX code on the issue requests if one exists on the input stock number. The IEX code identifies issue condition peculiar to an item (see chapter 3). Some of the following items may contain an IEX Code: Health hazardous, photographic, random length, etc., Refer to Chapter 11 for a complete listing of autho-rized IEX codes used in the retail supply system.

8-22 NSN. If a NSN is not available, then provide a DD Form 1348-6, DOD Single Line Item Requisition System Document (Refer to Attachment 3B-9 for preparation DD Form 1348-6 instructions). Note, use this field to enter the part number when applicable.

Block E Technical order, figure and index. Part number and the CAGE code.

23-24 Unit of issue.

25-29 Quantity required.

30 Activity Code:

X = Expedite Request

R = Routine

J = IMDS/G081

Note, if the customer is not sure, leave blank and the LRS/supply activity personnel will assist in determining the correct activity code.

31-33 Organization and shop code.

3–15

44 Demand code. The supply customer is responsible for providing the demand code during issue requests process. The following demand codes are authorized for use in the cus-tomer requests:

Code ‘C’ (Contractor): Used on requests from a contractor for items required in support of an authorized contract. DIFM control is not established on this code and should be used only when it is anticipated that a like item will not be turned in.

Code ‘I’ (Initial Issue): Used on issue requests submitted to satisfy an original shortage or installation or to replace an item that was originally installed, but was later lost. Examples are requests for items to be installed in bench test sets or mockups, or items lost in flight, fire, or crash. No turn-in of an unserviceable item is involved; nor is a DIFM control established. Note, Submit a letter of initial issue when requesting the initial issue of a repair cycle item (ERRCD XD2 or XF3).

Code ‘N’ (Non-recurring): This code is used for one-time requests for items for which no future need is expected. Nonrecurring requests include items issued to perform modifica-tion or retrofit, or to replace items in a kit with a newer item. DIFM control is established on repair cycle assets. It should be used when requesting unusually large one-time requirements that are out-of-phase with normal needs.

Code ‘R’ (Recurring): This is the most commonly used code. It applies to day-to-day issues to an organization for normal operations when it is anticipated the item will con-tinue to be required in the future. This code will establish DIFM control on repair cycle assets. It is normally used when replacing a like item that is suspected to be or actually is unserviceable or one that is condemned.

45-50 Work order number, if applicable 51 Transaction Exception Code, if applicable 53 FAD. Normally, left blank. The LRS/supply activity has already assigned the FAD you are authorized to your organization record, so the retail supply system will automatically assign the FAD to your issue request and the subsequent requisition. If the required item is in direct support of another organization with a higher FAD, enter that organization’s FAD as an override on that individual issue request. Do not use FAD override procedures for routine administrative or janitorial support.

57-59 Project code. Project codes are 3-digit characters assigned by the Joint Chief of Staff (JCS), DOD, and the Military Services for identifying special projects. The project code also allows logisticians to identify supply transactions associated with the project. The project code is s dual-purpose field. For AWP requests, enter the standard reporting des-ignator (SRD) in the project code field. This is necessary because the entire mark-for field (which is where the SRD would go in positions 74-76) is consumed by the 14-position end item AWP document number. See CHAPTER 3 for additional information about project codes.

60-61 Supply Response Priority Maintenance (formerly called delivery priority) (Refer to Attachment 3B-4).

62-64 Required Delivery Date, if applicable 65-66 UJC. Identified by two elements. The first position of the UJC is the Urgency of Need

Designator (UND). The second position of the UJC is the type of requirement. For MICAP requests, provide the appropriate MICAP UJC and list the type model, series, and serial number of end item, weapon system, or equipment. Refer to Attachment 3B-6 for a complete list of UND and UJC codes.

67-80 Mark-For. Use this field to identify the end item on which the requested item will be used.

For instance, if the item is required for an aircraft, enter the aircraft serial number, SRD, the work unit code, and the MAJCOM code in this field. Refer to Attachment 3B-7 for an explanation the data elements for the mark-for field.

3–16

Block J Nomenclature. Enter a meaningful nomenclature in this field 3–17

ATTACHMENT 3B-4

SUPPLY RESPONSE PRIORITY & MAINTENANCE REPAIR DESIGNATORS

3B4.1. Purpose. To provide a list of supply response priority and maintenance repair designators and the corresponding definitions for each designator.

3–18

T D 1 ons equipment, and CEM emergency requirements.

2 unitions equipment, and h, alert, or test flight, and AGE, munitions, muni-l and tactical support air-ission accomplishment.

impacting the mission by

3 itions, munitions equip-otherwise listed. Admin-uirements for nuclear mplishment, if not per-omplishment. Spares not Critical end-item and rep-ning simulators, other linquent routine TCTO GE when repair will not ary mission equipment.

hment. Reparable spares ing vehicles, alert vehi-

4 e aircraft undergoing tems due maintenance or f aircrew or missile train-munitions and munitions heduled repairs on PME ange items. Primary mis-epair of other CEM sys-enance or inspection.

equipment and related epairs on PME not listed ng vehicles.

3–19 able 3B4.1. Supply Response Designator Codes and Definitions.

ESIGNATOR DEFINITION

Aerospace vehicles on alert status, war plan or national emergency missions, including related AGE, muniti equipment. CEM systems or equipment including associated AGE supporting alert, war plans, or national Primary mission air vehicles, missile support aircraft, air launched missiles, and related AGE, munitions, m

CEM equipment for the first8 hours after landing or start of recovery or within 6 hours of a scheduled launc during simulated generations. Air evacuation, rescue, and weather mission aerospace vehicles and related tions equipment, and CEM equipment. All transient tactical and tactical support aircraft. Transient tactica craft. Primary mission CEM systems or equipment, including associated AGE, when repair is impacting m Flight or missile crew training simulator or other training equipment related AGE requiring repair, which is preventing or delaying student training.

Primary mission air vehicles, missile support aircraft, engines, air launched missiles and related AGE mun ment, and CEM equipment undergoing scheduled or unscheduled maintenance. Transient air vehicles not istrative aircraft within 8 hours of scheduled flight or on alert status with standby crews. Time change req weapons. Scheduled and unscheduled maintenance of munitions that would prevent or delay mission acco formed. PME requiring emergency repair or calibration, the lack of which will prevent or delay mission acc available in the LRS/supply activity. (Applies to selection of Maintenance repair priority designator only.)

arable spares or supply designated "priority repair" spares. Routine maintenance of aircrew or missile trai training devices, or related AGE sites. Overdue scheduled maintenance to include periodic inspections, de and MCL, and other time change items. Primary mission CEM systems or equipment including associated A impact mission accomplishment. Alternate equipment provided to ensure uninterrupted operation of prim AGE requiring emergency repair or calibration, the lack of which will delay or prevent mission accomplis when like serviceable spares are not available in Supply. All base emergency vehicles, aircraft fuels servic cles, 463L-loading vehicles, and crash or fire vehicles deadlined for parts conditions.

Routine or extensive repair of primary air mission and related AGE and repair cycle assets. Administrativ scheduled or unscheduled maintenance. Routine maintenance of AGE, not otherwise listed above. WRM i inspection. Inspection, maintenance, and TCTO compliance of MSK or MRSP materiel. Extensive repair o ing simulators, other training devices, or related AGE. Inspection, maintenance, and TCTO compliance of equipment, excluding spares excess to base requirements not listed above. Scheduled calibration and unsc not listed above. Scheduled maintenance to include periodic inspections, routine TCTO, MCL, and time ch sion CEM systems or equipment including associated AGE undergoing extensive repair or modification. R tems or equipment including associated AGE. Repair of CEM repair cycle assets. WRM items due maint Repair and calibration of AGE not included above. Routine or extensive repair or modification of training AGE not scheduled for instructional use within the next 8 hours. Scheduled calibration and unscheduled r above. Base vehicles. All VDP conditions except for ambulances, crash or fire trucks, and aircraft refueli onautical items not carrying e requirements not listed EM systems or equipment, pancies on training equip-ent requirements.

3–20

5 Non-tactical or non-primary-mission aircraft undergoing extensive repair. Fabrication and repair of aer a higher priority. Bench stock requirements. Extensive repair of aircrew training devices. Time chang above. Routine repair of missiles, AGE, and RPIE, including repair cycle assets. Alternate and other C including associated AGE undergoing extensive repair or modification. Clearing routine delayed discre ment or AGE, and routine maintenance that will not impair or affect mission accomplishment. Equipm

6 Fabrication and repair of non-aeronautical items.

7 Spares excess to base requirements.

ATTACHMENT 3B-5

URGENCY OF NEED (UND)/FORCE ACTIVITY DESIGNATOR (FAD) MATRIX

3B5.1. Purpose. To list and explain the elements of the UND and FAD. Illustrate how the retail supply system uses the UND and FAD to determine the off base UMMIPS requisitioning priority.

3B5.2. UND Identification and Relative Information. The UND is a one-position alpha/numeric value used to express varying degrees of urgency operational mission capability is jeopardized due to assets non-availability. It’s also a factor used to help calculate the requisition priority for the customer’s backo-rder requests.

3–21

Table 3B5.1. Und Codes and Definitions.

3B5.3. Force Activity Designator (FAD). The FAD is a one-position numeric character that may be entered on customer issue requests. The authorized FAD codes are one (1) thru five (5). The FAD signi-fies the relative order of importance of a supported organization requesting supplies and equipment items.

Additionally, the retail supply system uses the FAD, in conjunction with the Urgency of Need Designator (UND), to determine the priority designator assigned to output requisition transactions used for customer backorders. The HQ USAF Program Document (short title PD) is the authority for FAD assignment for Air Force organizations, sections/elements, activities, and/or projects.

3B5.3.1. FAD Override. When mission dictates, the supply customer may override the existing FAD that already exists on the organization’s account record within the retail supply system. However, extreme caution shall be used to prevent priority abuse when exercising the FAD override option.

UND CODE ASSIGNMENT AND USE

A Lack of the requested item prevents mission accomplishment.Depending on the FAD of the requesting organization, a priority 01, 02, 03, 07, or 08 off-base requisition results if the requested item is not available in Supply. When using this code, justify its use.

1 Lack of the requested item prevents mission accomplishment because the end item is not operationally ready, out-of-commission, or inoperative. Depending on the FAD of the requesting organization, a priority of 01, 02, 03, 07, or 08 off-base requisition results if the requested item is not available in Supply. This code is assigned by the LRS/sup-ply activity if the item is needed to repair a MICAP reportable end-item (see notes 1 and 2).

B Lack of the requested item impairs mission accomplishment by decreasing effectiveness and efficiency. Depending on the FAD of the requesting organization, a priority 04, 05, 06, 09, or 10 off-base requisition results if the requested item is not available in Supply.

When using this code, justify its use.

C This code is used for stock replenishment, initial stockage of parts for new end-items, or other routine requirements that do not qualify for assignment of a higher UND. UND C is automatically assigned to all requests when a higher urgency of need is not specified.

When this code is used, priority 11, 12, 12, 14, or 15 is assigned to the off-base requisi-tion.

J Lack of the requested item impairs mission accomplishment because the end-item is not fully equipped or is operating in a limited or restricted capacity. This code is assigned by the LRS/supply activity if the item is needed to repair a MICAP reportable end-item.

Depending on the FAD of the requesting organization, a priority 01, 02, 03, 07, or 08 off-base requisition results if the requested item is not available in Supply (see note 2).

/ (slash) Lack of the requested item creates a reportable battle damage condition. This code relates to UJC AA and is used for UND A requirements when the MICAP condition was caused by hostile action. Use of this code generates a MICAP condition code M (see note 2).

Notes for UND codes:

1 Refer to the SRD Table in CAMS/REMIS to determine which end-times are MICAP reportable and for their related SRD 2 AF Standard UJC’s are used for all non-MICAP requirements. The following applies for verified MICAP issue requests--the first position of the s Air Force UJC is replaced by the MICAP UND indicator 1, J, or / (slash). These MICAP UND indicators are used by the retail supply system to generate a MICAP condition code and report. Refer to Attachment 3B-6 for the authorized combinations of for MICAP UND to UJC.

3–22

Table 3B5.2. UND/FAD Matrix for Requisitioning Priority Assignment.

FAD Urgency Of Need Designator

A, 1, J,/ (Slash) B C Requisitioning Priority for Backorder:

I 1 4 11

II 2 5 12

III 3 6 13

IV 7 9 14

V 8 10 15 3–23

ATTACHMENT 3B-6

URGENCY JUSTIFICATION CODES (UJC) MATRIX

3B6.1. Purpose. To explain the two-position alpha/numeric code used on customer order requests to determine the urgency of need and type of requirement (justification) as described below. Use AF stan-dard UJC’s for all non-MICAP order requests. The first position of the USAF standard UJC code will be replaced by the SBSS MICAP UND indicator 1 or J for verified MICAP reportable end item issue requests. These MICAP/UND indicators are used to generate a MICAP condition. The corresponding MICAP condition codes generated are listed below.

3–24

T

C ARD

on-MICAP)

NOTE

N --

P

B --

R C CC

R C CC

N D CD

N D CD

C n

E CE

C n

E CE

V F CF

P F CF

A s

G CG

A s

G CG

E H CH

M -- W K -- Note 1 3–25 able 3B6.1. UJC Table Matrix.

ONDITION DESCRIPTION MICAP UND/UJC

FLAG

MICAP CONDI-

TION CODE

STAND

UJC (N

MCS Aerospace vehicle not mission capable supply(includes

ICBM)

1A G AA --

MCS Aerospace vehicle partial mission capable supply(includes

ICBM)

JA F AA

D Battle damage /A M AA -- OCP Radar out of com- mission for parts(equipment out of com-mission)

1C K AC B

OLP Radar out of com- mission for parts(equipment operating in limited or restricted capacity)

JC L AC B

AIOP Navigational aids in-operational(equipment out of commis-sion)

1D K AD B

AILP Navigational aids in-operational for parts (equipment operat-ing in a limited or restricted capacity)

JD L AD B

CMEIPCommu-ications

1E crypto/meteorological equipment inoperative for parts (includes L systems) (equipment out of com- mission)

K AE B

CMEIPCommu-ications/

JE crypto/meteorological equipment inoperative for parts(includes L systems)(equipment operative in limited or restricted capacity)

L AE B

DP Vehicle dead-lined (in-operative) for parts 1F V AF B MCS P-15 fire fighting vehicle partial mission capable supply JF N AF B GEOCP Aero-pace ground 1G equipment out of commission for parts (includes an inop-erative test station segment if required to repair an essential asset listed in the command Miss- ion Essential Spares List-ing

W AG B

GEOLP Aero-pace ground

JG equipment out of commission for parts (equipment operat-ing in limited or restricted capacity)

R AG B

CM Electronic warfare pod inoperative or missile or drone not mission capable supply (excludes ICBM)

1H E AH B

UNITIONS Aerospace munitions not mission capable supply -- AJ BJ S Industrial/production in repair or manufacture of primary weapons, equipment, or supplies having a work stop- page due to the lack of materiel

-- AK B

BL CL

BM CM

BN CN

BO CO

BO CO

BO CO

BP CP

BP CP

Q CQ

BR --

S CS

T CT Note 2

BU CU

BV CV Note 3

BW CW

- CX

3–26

VRP Vital base real property facility inoperative (includes missile RPIE, fuels laboratory and servicing facilities)

-- -- AL

ENG NMCS Aerospace engine(applies to MICAP reportable and MICAP non-reportable engines) is not mission capable supply

1M E AM

RDTP Space research/ development/test engineering project stopped for supplies

-- -- AN

PMEL Part required for repair of non-MICAP reportable items by precision measurement equipment laboratories

-- -- AO

NMCS MICAP reportable precision measurement equipment inoper-ative for parts(equipment out of commission)

1O W AO

PMCS MICAP reportable precision measurement equipment inoper-ative for parts (equipment operating in a limited or restricted capacity)

JO R AO

TDIOP Training equipment--trainer cannot be used to perform any degree of it designated training objective

1P G AP

TDILP Training equipment--trainer can be used but is not capable of performing all of the command training objectives due to one or more designed capabilities being inoperative

JP F AP

DD Delayed discrepancy entry records -- -- -- B AWP Materiel required to repair unserviceable recoverable assets in the repair cycle that need parts to return them to a serviceable condition

-- -- AR

HWM Materiel required to maintain health, welfare, morale, or sup-port personnel

-- -- -- B

WRM Mobility kit, mobility equipment shortages, war consumables inviolate level, Harvest Eagle re-placement requirements, LOGDET mobility requirements

-- -- -- B

TCTO Materiel required to comply with time change/time compli-ance technical orders

-- -- AU

MEE Initial/replacement of controlled mission equipment (includ-ing SPRAM requirements) and station set and housekeeping set items

-- -- AV

WOR Workorder requirement not otherwise described -- -- AW EAID Initial/replacement of EAID shortages not otherwise described

N Y --

P Y --

H --

I Z CZ

D -- Note 4

E --

N 1 e 20 or 23 series except 2300.

2 If an overriding operational

3 riority requisitioning to obtain

4 BZ will create a priority 06 3–27

AIRS MICAP reportable airborne image recording and support equipment

1Y P AY B

MCS MICAP reportable image recording and support equipment partial mission capable

JY F AY B

PMSK Initial or replacement requirements in support of high priority mission support kits (MRSP de tails containing type WRM spares code F) This UJC will be assigned under program con-trol as appropriate

-- -- BT --

JC All requirements not otherwise described -- -- AZ B C Disease or calamity medical disaster relief supplies or equip-ment to prolong life in case of critical injury, fatal disease, or calamity.

-- -- -- AZ

IC Organizational clothing to provide a minimum of essential clothing to an individual.

-- -- -- BZ

otes for UJC Matrix:

Urgency justification code AK and BK are used only by AFMC activities with SRAN 7048 or 2180, or any SRAN within th Submit requests for new or increased pre-positioned war reserve materiel requirements using UND C as the normal method.

situation justifies immediate support, the using major command may authorize the use of UND B.

Use urgency justification codes AV and BV when circumstances such as unit activation, deployments, etc., dictate the use of p equipment and when the lack of which would prevent or impair the accomplishment of the unit's mission.

Establish a FAD 3 due-out for DC condition order requests. UJC AZ will create a priority 03 requisition and a due-out; UJC requisition and a due-out.

ATTACHMENT 3B-7

MARK-FOR DATA

3B7.1. Purpose. To list mark-for field attributes used on the customer issue requests.

3B7.2. Mark-For Information. The mark-for is used to identify specific information (e.g., aircraft serial number, standard reporting designator (a.k.a. weapon system identifier), work unit code, major command (MAJCOM), end item document number for AWP requests, detail number (relative for assets that main-tained on detail records), and miscellaneous information about the customer’s order requests. For a detailed list of all mark-for data edits used by the retail supply system on customer issue requests, refer to Chapter 11.

SRD Assignment. The importance of assigning the correct SRD to customer order requests cannot be overemphasized. In no case, should an individual arbitrarily assign SRD codes. Please use/assign the correct SRD that denotes the weapon system, end item, or equipment that you have deemed inoperable and requires supply support.

3B7.2.1. When no other SRD is available, and the requested part is not in support of a weapon sys-tem, end item, or equipment, use one of the following SRD’s—RSA, RSB, RSC, RSD, and ZZZ.

3–28

Table 3B7.1. Mark-For Format and Relevant Information about the Mark-For Attributes.

Mark For Data Field Positions Why it’s Important Aircraft Tail Number, End Item Serial Number

67 - 73 Identifies the specific aircraft tail number or serial number for which the item has been deemed inoperable

Standard Reporting Desig-nator (SRD)

74 - 76 Identifies the specific end item, weapon system, or equipment that is inoperable.

The retail supply system uses the SRD to record consumption against the weapon system, end item, or equipment. The con-sumption data can be used to allocate more or less assets to sup-port the mission for a given base/MAJCOM/or the overall Air Force. Failure to use the appropriate SRD on customer requests can skew the consumption data.

The SRD is a factor that is used to report metrics to higher level AF leadership that indicates how well the base’s LRS/supply activity is supporting the various weapon systems.

Work Unit Code 77 - 78 Identifies the first two position of the work unit code that corre-lates to an end item, weapon system, or equipment.

MAJCOM Code 79 - 80 Identifies the specific MAJCOM code.

End Item Document Num-ber

67 - 80 Required by the retail supply system on awaiting parts requests (identified by UJC equal to ‘AR’ or ‘BR’) to record the end item document number for which the bit and piece will be ordered against.

Detail Record Document Number

67 - 80 Required by the retail supply…