Chapter 8 FOREIGN MILITARY SALES (FMS) CASE PERFORMANCE Para Title Page

Section 8AFMS CASE IMPLEMENTATION 8.1. Purpose ........................................................................................................................................................ 8-4 8.2. General ........................................................................................................................................................ 8-4 8.3. FMS Case Types ......................................................................................................................................... 8-5 8.4. AFMC Implemntation of FMS Cases............................................................................................................ 8-6 8.5. Types of Support. ........................................................................................................................................ 8-6 8.6. Thru 8.10. (Unused.) ................................................................................................................................... 8-7 Section 8BACQUISITION FOR FMS 8.11. Sole Source Acquisition of Items .................................................................................................................. 8-7 8.12. Special Purchase Requirements .................................................................................................................. 8-12 8.13. Thru 8.17. (Unused.) .................................................................................................................................. 8-14 Section 8CPROCESSING FMS REQUISITIONS 8.18. Purpose ...................................................................................................................................................... 8-14 8.19. Defined-Order (D/O) Case Requisition Processing...................................................................................... 8-14 8.20. Preparation and Processing of Requisitions Against Follow-on E and B/O Cases .................................... 8-14 8.21. Submission of Requisitions, Follow-ups, Cancellations and Reqisition Modifiers........................................ 8-15 8.22. Federal Aviation Administration (FAA) Requisition Processing ................................................................. 8-18 8.23. Requisition Process for Shelf-Life Items ..................................................................................................... 8-18 8.24. US Navy Processing of Air Force FMS Requisitions ................................................................................... 8-19 8.25. Processing Materiel Release Orders (MRO) and Redistribution Orders (RDO) to Support FMS Requirements ....................................................................................................................... 8-19 8.26. Preparation and distribution of DD form 1348-1, DoD Single Line Item Release/ Receipt Document..................................................................................................................................... 8-19 8.27. FMS Customer-Generated Requisitions ...................................................................................................... 8-20 8.28. Hydrazine-Water (H-70) Support for F-16 Aircraft..................................................................................... 8-22 8.29. PROS Standard Item Policy........................................................................................................................ 8-23 8.30. Thru 8.33. (Unused) ................................................................................................................................... 8-26 Section 8DCOMMITMENTS 8.34. Bulk Commitments .................................................................................................................................... 8-26 8.35. Custom Commitments................................................................................................................................ 8-26 8.36. Thrus 8.40. (Unused.)................................................................................................................................. 8-28 Section 8EAIR FORCE MATERIEL COMMAND (AFMC) SYSTEM SALES 8.41. Communication/Electronic (CE) Systems and Equipment D Case Processing.......................................... 8-28 8.42. Weapon Systems S Case Processing ........................................................................................................ 8-30 8.43. Weapon Systems Y Case Processing ....................................................................................................... 8.31 8.44. Weapon Systems Q Case Processing ....................................................................................................... 8.31 8.45. Preparation and distribution of DD form 1348-1, DoD Single Line Item Release/ Receipt Document ...................................................................................................................................... 8-31 8.46. Thru 8.50. (Unsed.).................................................................................................................................... 8-31 Section 8FFMS CASES OTHER THAN D, Q, S, AND Y 8.51. General ...................................................................................................................................................... 8-31 8.52. A Cases - Defnined-Order (D/O) Cases for Munitions ............................................................................ 8-31 8.53. B Cases - Reserved.................................................................................................................................. 8-32 8.54. C Cases - Blanket-Order (B/O) Cases for Cartridge Actuated Devices/Propellant Actuated Devices (CAD/PAD).................................................................................................................... 8-32 8.55. E Cases - B/O Cases for Support Equipment and Supplies ...................................................................... 8-32 8.56. F Cases - Reserved .................................................................................................................................. 8-33 8.57. G Cases - D/O or B/O Services Cases...................................................................................................... 8-33

8.58. H Cases - D/O Cases for Transportation Services ................................................................................... 8-35 8.59. J Cases - Reserved (Formerly Ferry Services, Now Written as G Cases ............................................... 8-35 8.60. K Cases - CLSSA................................................................................................................................... 8-36 8.61. L Cases - D/O Cases for Equipment ........................................................................................................ 8-36 8.62. M Cases - D/O and B/O Cases for Depot Level Maintenance .................................................................. 8-36 8.63. N Cases - Special Support ...................................................................................................................... 8-36 8.64. O Cases - B/O and D/O Cases for Communication Security (COMSEC) ............................................... 8-36 8.65. P Cases - D/O and B/O Cases for Publications ....................................................................................... 8-36 8.66. R Cases - B/O Spare-Parts Cases............................................................................................................ 8-36 8.67. T Cases - Training .................................................................................................................................. 8-36 8.68. U Cases - Military Assistance Program (MAP)........................................................................................ 8-36 8.69. V Cases - B/O and D/O Cases for Class IV Modification ....................................................................... 8-37 8.70. W Cases - D/O Cases for Class V Modifications ................................................................................... 8-37 8.71. X Cases - Holding Accounts and Financial Projects ............................................................................... 8-37 8.72. Z Case - Special Management (Non-FMS) ............................................................................................. 8-37 8.73. Thru 8.50. (Unused.) .................................................................................................................................. 8-37 Section 8GCOOPERATIVE LOGISTICS SUPPLY SUPPORT ARRANGMENTS (CLSSA) 8.78. Background................................................................................................................................................ 8-37 8.79. CLSSA Overview ...................................................................................................................................... 8-38 8.80. The FMSO I Stock-Level Case ................................................................................................................... 8-38 8.81. FMSO I Case Development Overview ........................................................................................................ 8-39 8.82. FMSO I Initial and Major-Add Program Processing ................................................................................... 8-40 8.83. FMSO I Computations ............................................................................................................................... 8-42 8.84. FMSO I Item Management......................................................................................................................... 8-43 8.85. FMSO I Levels in the Buy-Computation Systems ....................................................................................... 8-44 8.86. FMSO I Liability Management................................................................................................................... 8-44 8.87. FMSO I Financial Management ................................................................................................................. 8-46 8.88. FMSO II Requisition Case.......................................................................................................................... 8-47 8.89. The Quality of Storage, Maintenance, and Modifications............................................................................ 8-49 8.90. CLSSA Funding......................................................................................................................................... 8-49 8.91. Termination .............................................................................................................................................. 8-50 8.92. Thru 8.100. (Unused.) ............................................................................................................................... 8-50 Section 8HPUBLICATIONS FOR SECURITY ASSISTANCE (SA) CUSTOMERS UNDER THE FMS PROGRAM 8.101. Purpose ...................................................................................................................................................... 8-50 8.102. Scope ........................................................................................................................................................ 8-50 8.103. Authorized Publications by Category, Focal Point, Supply Source, and Referenced Management Paragraph ................................................................................................................................................ 8-50 8.104. Responsibilities .......................................................................................................................................... 8-50 8.105. Negotiation Procedures............................................................................................................................... 8-51 8.106. Implementation Procedures ........................................................................................................................ 8-51 8.107. Submission of Customer Requests .............................................................................................................. 8-52 8.108. Management Procedures............................................................................................................................. 8-52 8.109. Case Closure for Publications ..................................................................................................................... 8-58 8.110. Pricing for Publications .............................................................................................................................. 8-58 8.111. Packing, Crating, Handling, and Transportation......................................................................................... 8-58 8.112. Thru 8.116. (Unused.) ................................................................................................................................ 8-58 Section 8IREQUIRED AVAILABILITY DATE (RAD) MANAGEMENT PROGRAM 8.117. Policy ......................................................................................................................................................... 8-58 8.118. Definition and Application of RADs........................................................................................................... 8-58 8.119. Purpose of a RAD .................................................................................................................................... 8-59 8.120. Scope ......................................................................................................................................................... 8-59 8.121. Administrative ........................................................................................................................................... 8-59 8.122. Categories Exluded from RAD Assignments .............................................................................................. 8-59

8.123. Conditions Impacting RAD Assignments ................................................................................................... 8-59 8.124. RAD Assignment Responsibilities .............................................................................................................. 8-59 8.125. RAD Review Responsibilities ..................................................................................................................... 8-59 8.126. Management Actions to Meet an Assigned RAD ........................................................................................ 8-60 8.127. RAD Management Responsibilities ............................................................................................................ 8-60 8.128. RAD Adjustments - Why............................................................................................................................ 8-60 8.129. RAD Adjustments - Who............................................................................................................................ 8-60 8.130. RAD Adjustments - How ........................................................................................................................... 8-60 8.131. Items Controlled by MILSTRIP Procedures ............................................................................................. 8-60 8.132. Items Not Controlled by MILSTRIP Procedures (Slippage Will Exceed 90 Days) ....................................... 8-61 8.133. IMS Computer Support System (D035A).................................................................................................... 8-61 8.134. SPD and Case Managers Support System ................................................................................................. 8-61 8.135. Thru 8.139. (Unused.). ............................................................................................................................... 8-61 Section 8JTRANSPORTATION 8.140. Ferrying of Aircraft .................................................................................................................................... 8-61 8.141. Packaging and Marking ............................................................................................................................. 8-61 8.142. Preparation and Distribution of DD Form 1348-1A, DoD Single Line Item Release/Receipt Document... 8-62 8.1.43. Thru 8.147. (Unused.) ................................................................................................................................ 8-62 Section 8KPROCESSING FMS SUPPLY DISCREPANCY REPORTS (SDR) 8.148. Purpose ...................................................................................................................................................... 8-62 8.149. Related Discrepancy Reporting................................................................................................................... 8-62 8.150. Scope ......................................................................................................................................................... 8-62 8.151. Policy ......................................................................................................................................................... 8-62 8.152. Responsibilities .......................................................................................................................................... 8-63 8.153. Submission Procedures............................................................................................................................... 8-63 8.154. General Processing Procedures ................................................................................................................... 8-65 8.155. Types of Discrepancy ................................................................................................................................ 8-66 8.156. Processing SF 364 by SDR Category .......................................................................................................... 8-67 8.157. Returning FMS SDR Materiel to US Government Control.......................................................................... 8-69 8.158. Reconsideration/Contested SDRs ............................................................................................................... 8-71 8.159. Thru 8.163. (Unused.) ................................................................................................................................ 8-71 Section 8LNOT-MISSION-CAPABLE SUPPLY (NMCS) DETERMINATION/REQUISITION CRITERIA 8.164. General ...................................................................................................................................................... 8-71 8.165. Determining an NMCS Condition .............................................................................................................. 8-72 8.166. Customers Materiel Availability ............................................................................................................... 8-72 8.167. Upgrading Existing Requisition.................................................................................................................. 8-72 8.168. Requisitioning............................................................................................................................................ 8-72 8.169. Requisitio Managers Follow-up/Tracking Management............................................................................. 8-72 8.170. Customer Management Tips ...................................................................................................................... 8-73 8.171. Thru 8.175. (Unused.). ............................................................................................................................... 8-74 Attachments 8C1. Commerical-Type Items ............................................................................................................................. 7-75 8C2. Recommended Research Products............................................................................................................... 7-78 8C3. FAD/UND/Priority Matrix ......................................................................................................................... 7-79 8C4. FMS Requisition Formats........................................................................................................................... 7-80 8C5. Requisition Checklist ................................................................................................................................. 7-88 8C6. Customer Requisition Format ..................................................................................................................... 7-90 8C7. FMS Routing Media Process Code (RP 71) Code Explanation ................................................................... 7-91 8C8. .....Serial Number Assignments ....................................................................................................................... 7-92 8C9. Request for Information Form .................................................................................................................... 7-93 8C10. AMARC Process Depiction ........................................................................................................................ 7-94 8D1. Routing Identifier Codes for Custom Commitments.................................................................................... 7-95 8D2. Air Force Appropriation Codes................................................................................................................... 7-96 8F1. Worksheet for Financial Analysis............................................................................................................... 7-97

8F2. 8F3. 8F4. 8F5. 8F6. 8G1. 8G2. 8G3. 8G4. 8G5. 8G6. 8G7. 8G8. 8G9. 8G10. 8G11. 8G12. 8G13. 8G14. 8H1. 8H2. 8H3. 8K1. 8K2. 8K3. 8K4. 8K5. 8L1. 8L2. 8L3.

Financial Analysis A - Defined Order Case/Line..................................................................................... 7-98 Materiel Support Division (MSD) Price and Cost Definitions and How They are Used for FMS ............... 7-100 Nonrecurring Cost Recoupment Charges Summary .................................................................................. 7-101 Five-Year Munitions Projection Survey .................................................................................................... 7-102 Task Work Specification .......................................................................................................................... 7-103 Ineligible CLSSA FMSO Items ................................................................................................................ 7-106 XD2-3 Format ......................................................................................................................................... 7-107 XD3-3, XD3-6, XD3-7 Format................................................................................................................. 7-108 SAMIS SLQ Computation Example ......................................................................................................... 7-110 Liability File Processing Example ............................................................................................................ 7-111 Absorption Review and Drawdown Requisition Processing....................................................................... 7-113 SAMIS Processing of the Absorption Request Forms................................................................................ 7-115 XD5-7, XD5-8 Format ............................................................................................................................. 7-116 Eligible and Ineligible FMSO II Items...................................................................................................... 7-118 Programmed/Nonprogrammed Codes Used in SAMIS Products ............................................................... 7-119 Asset Release Process ............................................................................................................................... 7-120 How to Identify an FMS Requisition......................................................................................................... 8-122 Types of FMS Requisition ........................................................................................................................ 7-125 FMS Requisition Fund Codes Description ................................................................................................ 7-126 Publications for Security Assistance ......................................................................................................... 7-128 Customer Information Matrix .................................................................................................................. 7-130 Guide for Publications Pricing (per Copy) (Other than Technical Orders)................................................. 7-131 Standard Form 364, Report of Discrepancy (ROD) ............................................................................... 7-132 DD Form 1348-1A, Issue Release/Receipt Document............................................................................. 7-134 DD Form 250, Material Inspection and Receiving Report......................................................................... 7-135 DD Form 1149, Requisition and Invoice/Shipping Document................................................................ 7-136 Reply Codes to Customer Requests for Adjustments or Billings ............................................................... 7-138 FAD/UND/Priority Matrix ....................................................................................................................... 7-140 Urgency Justification Codes (UJC) ........................................................................................................... 7-141 Urgency of Need Designator (UND) Defined ............................................................................................ 7-142

(AFMC forms and publications referred to this chapter are for AFMC use only and are not available for general Air Force use.) Section 8AFM CASE IMPLEMENTATION 8.1. Purpose. 8.1.1. This section gives guidance for processing FMS materiel requirements. 8.1.2. Air Force policies for managing FMS are in AFMAN 16-101. This section is applicable to all Air Force people with FMS responsibilities. AFMAN 16-101 gives responsibilities of major commands, Air Force sections of security assistance organizations (SAO), Air Force missions, US defense attach offices (USDAO), offices of defense cooperation (ODC), and foreign governments in support of FMS. Except to explain the policies and procedures in AFMAN 16-101, and to further clarify responsibilities of major commands, the provisions of AFMAN 16-101 will not be repeated herein. 8.2. General. 8.2.1. Purchasers may obtain materiel and services through FMS in one of three ways: 8.2.1.1. Defined-order cases are set up to buy specific quantities of defined items or services. These cases usually entail pricing studies. 8.2.1.2. Blanket-order (B/O) cases are used to buy a specific category of articles or services. There is no definitive listing of items or services on the Letter of Offer and Acceptance (LOA). Pricing studies usually are not needed. The purchaser usually estimates requirements and asks for an appropriate case value. The Security Assistance Management Manual (SAMM) has lists of items that are eligible for B/O cases.

8.2.1.3. Cooperative logistics supply support arrangements (CLSSA) allow for follow-on spares support. CLSSA allows the purchaser to stock prefunded requirements in the Air Force inventory. Each CLSSA program has two parts: 8.2.1.3.1. The foreign military sales order I (FMSO I) is a stock-level case by which requirements are forecasted, funded, and stocked in the Air Force inventory. 8.2.1.3.2. The FMSO II is an annual blanket-order case against which the CLSSA customer places requisitions. This case can be used to requisition items listed on the FMSO I and spares not listed. 8.2.2. Each FMS case identifier is composed of three elements: 8.2.2.1. A two-digit country or international-organization code which identifies the purchaser. 8.2.2.2. A one-digit service code, which identifies the Department of Defense (DoD) case-managing service (D is Air Force, B is Army, P is Navy). 8.2.2.3. A three-digit case designator. The first digit shows the category of materiel or service supplied. The last two digits distinguish cases in the same category. For example: AT-D-AAB. 8.2.3. Billing of FMS customers is a function of the Defense Financial Accounting Services (DFAS), Denver CO 80279. 8.3. FMS Case Types. 8.3.1. FMS cases are set up by each military service (Army, Air Force, Navy) for items and services for FMS customers. Case identifiers are used to help in the management, identification, accounting, and billing of FMS requirements. 8.3.2. Correspondence on a specific customer's requirements should give the FMS case (such as AT-DAAA) in the subject. The FMS customer and case are identified in Military Standard Requisitioning and Issue Procedures (MILSTRIP) transactions in card RP 31 32 and 48-50 respectively. The first position of the case designator shows the commodity or service covered by the case (such as A for munitions). 8.3.2.1. A list of first-position case designators is shown below: 8.3.2.1.1. A Munitions cases. 8.3.2.1.2. B Reserved. (Formerly defined-order (D/O) spare cases.) 8.3.2.1.3. C Cartridge actuated/propellant actuated device (CAD/PAD) cases. 8.3.2.1.4. D Communications/Electronics Systems (CE) cases. 8.3.2.1.5. E Blanket-order for support equipment and supply items cases. 8.3.2.1.6. F Reserved. (Formerly training films and audiovisual cases.) 8.3.2.1.7. G D/O or blanket-order (B/O) services cases, including technical assistance cases. 8.3.2.1.8. H Reserved. 8.3.2.1.9 J Reserved. 8.3.2.1.10. K FMSO I (Follow-on spares to be maintained on-hand/on-order) and FMSO II (CLSSA B/O spares cases). 8.3.2.1.11. L Reserved. (Formerly AFMC D/O equipment cases.) 8.3.2.1.12. M Maintenance cases. 8.3.2.1.13. N Special support/services cases. 8.3.2.1.14. O Information security (INFOSEC) cases. 8.3.2.1.15. P Publication cases. 8.3.2.1.16. Q Consolidated sustainment support cases. 8.3.2.1.17. R B/O spare parts cases. 8.3.2.1.18. S Major aircraft system sales cases. 8.3.2.1.19. T Training cases. 8.3.2.1.20. U Pseudo-cases used for tracking Section 506 drawdowns and similar non-FMS SA Grant-Aid transactions. 8.3.2.1.21. V Class IV modification cases. 8.3.2.1.22. W Reserved. 8.3.2.1.23. X Reserved for DFAS Denver. 8.3.2.1.24. Y Missile systems cases. 8.3.2.1.25. Z Special management cases (leases). 8.3.2.2. These cases are used to provide many types of materiel and services to foreign customers, for both initial and follow-on support requirements.

8.4. AFMC Implementation of FMS Cases. 8.4.1. The Air Force Security Assistance Center (AFSAC) will prepare an international program directive (IPD) for all system sales cases (D, S, Y, and Q cases) and defined-order cases (A, G, H, M, N O, and P cases). B/O cases utilize country notifications in lieu of IPDs. These notifications provide the country with notification regarding when they can begin submitting orders against a case. The IPD will include both general and specific guidance to make sure all required actions of the FMS case are implemented as negotiated. This IPD will include a statement of obligation authority (OA) issued by DFAS by fiscal year noting that the current year OA is not to be exceeded. The AFSAC will send the IPD to the prime Air Logistics Center (ALC) focal point or other appropriate activity for action. The IPD is the command-guiding document and is to be followed by all recipients in the case implementation process. 8.5. Types of Support. 8.5.1. Two basic types of support, initial and follow-on, are available to FMS customers. Some general characteristics of initial versus follow-on support programs for FMS customers are as follows: TYPE OF SUPPORT INITIAL FOLLOW-ON Multiple One (usually) Yes Occasionally SAF AFSAC Extensive Limited

CHARACTERISTICS Number of Cases Complex Negotiated by Contractor(s) Interface

8.5.2. Initial support is the introduction of concurrent spares, support equipment and services, etc., for major systems or major items. 8.5.2.1. There are four FMS case designators that show initial support of system sales programs. 8.5.2.1.1. D CE system sales cases. 8.5.2.1.2. Q Consolidated sustainment support cases. 8.5.2.1.3. S Major Aircraft system sales cases. 8.5.2.1.4. Y Missile systems cases. 8.5.2.2. For these programs there will be separate case/lines assigned within the basic LOA for the various parts of the program. A representative LOA could have the following individual case/lines. 8.5.2.2.1. 001 Aircraft. 8.5.2.2.2. 002 Spare engines. 8.5.2.2.3. 003 Initial spares. 8.5.2.2.4. 004 Support equipment (common). 8.5.2.2.5. 005 Weapon System Logistics Officer (WSLO) 8.5.2.2.6. 006 Technical assistance (contractor). 8.5.2.2.7. 007 Munitions. 8.5.2.2.8. 008 Aircrew training. 8.5.2.2.9. 009 Aircraft delivery services. 8.5.2.3. System sales programs are usually complex, involve several major commands and contractors, and are often negotiated at high levels with early delivery dates which affect our ability to give the best logistics support. 8.5.3. Follow-on support is the recurring support needed to maintain the operational capability of the system/major item (spares, support equipment, services, etc.) 8.5.3.1. There are many FMS cases for follow-on support programs which can be put into four groups. 8.5.3.1.1. Defined-order materiel cases. For these cases the customer provides a definitized list of items. A line item pricing study is done by the inventory management specialist (IMS). These cases are managed on a line-item basis to watch over both price and delivery performance. Examples of these types of cases are: 8.5.3.1.1.1. A Munitions. 8.5.3.1.1.2. C CAD/PAD. 8.5.3.1.2. D/O service cases. These cases have characteristics like D/O materiel cases (for example, a pricing study is done and the case is usually managed on a line item basis). Examples are: 8.5.3.1.2.1. G Services cases, including technical assistance cases. 8.5.3.1.2.2. M Maintenance.

8.5.3.1.2.3. N Special support/services cases. 8.5.3.1.3. Blanket-order cases. These cases do not have definitized requirements but are negotiated for a specific dollar value. The customer requisitions or orders the materiel/service. Usually these cases are for only one year and are replaced annually by another case. Examples are: 8.5.3.1.3.1. E B/O for support equipment and supply items cases. 8.5.3.1.3.2. P Publications. 8.5.3.1.3.3. R B/O spare parts cases. 8.5.3.1.3.4. V Class IV modifications (may also be a defined-order case). 8.5.3.1.4. CLSSA. This is a follow-on support program that allows customers to invest and take part in the Air Force supply system. The objective of the CLSSA program is to set follow-on support requirements so customers' financial investments can be used to make sure materiel is on hand or on order before actually entering a requisition in the Air Force supply system. Customers taking part in the CLSSA are treated as part of the Air Force supply system. The CLSSA program is made up of two cases, both having a K designator. 8.5.3.1.4.1. K FMSO I. This case defines the customer's recurring spares requirements and is usually renegotiated every six months. 8.5.3.1.4.2. K FMSO II. This case is setup on an annual basis to allow the customers to requisition spares and repair parts to support their weapon systems. 8.6. Thru 8.10. (Unused.) Section 8BACQUISITION FOR FMS 8.11. Sole-Source Acquisition of Items. 8.11.1. It is Air Force policy to purchase spares, spare parts, initial support, and follow-on support competitively unless a sole-source purchase meets certain statutory exemptions. However, FMS customers may request this type of acquisition in getting such support. Sole-source procedures for FMS customers to follow when requesting it and for DoD to follow during the review and approval phase of the request can be found in chapter 7, section A, paragraph 7.7 of this manual. Subsequent to sole-source approval being granted and the LOA implemented, the following procedures are to be followed when procuring those materiel requirements identified in the LOA. 8.11.1.2. Sole-source acquisition of materiel may be used to buy the following items: Air Force managed primary inventory control activity (PICA) and nonstandard equipment items (including support equipment); reparable items where the Air Force is the PICA; reparable items where the Air Force is the secondary inventory control activity (SICA) (source of supply (SOS) routing identifier code (RIC) equals AF); or Air Force-managed (PICA) and nonstandard consumable items. 8.11.1.3. Sole-source acquisition cannot be used by the Air Force to buy the following items: equipment items managed by other services or agencies (e.g., Army, Navy, DLA, GSA, etc.); reparable items managed by other services or agencies (i.e., the PICA/SICA is not the Air Force); reparable items where the Air Force is the SICA but the requisition is supported directly through the PICA (SOS RIC is other than Air Force); or consumable items managed by other services or agencies. 8.11.1.4. Those requirements unsuitable for sole-source acquisition will be requisitioned through normal supply channels using established MILSTRIPs. 8.11.2. Limitations and restrictions. 8.11.2.1. Refer to paragraph 8.11.1.2 for a listing of those items authorized for sole-source acquisition and those items excluded from sole-source acquisition. 8.11.2.2. Other service- or agency-managed items will not be bought directly by the Air Force through sole-source acquisition except when the Air Force is the SICA and the materiel requirements will be supported through the Air Force. Requirements for other service- or agency-managed items exempt from sole-source procurement are passed to the service or agency having item management responsibility either through a military interdepartmental purchase request (MIPR) or passing referral action (i.e., MILSTRIP). Requisitions for other services or agencies will be rejected and placed on controlled exception (CEX). Prior to releasing the CEX to the other service or agency, the ALC product management office (PMO) needs to ensure no internal contractual actions have begun. If contractual actions have been initiated, the ALC PMO needs to ensure these actions are ceased immediately (providing termination charges do not apply). Subsequently, the ALC PMO needs to release the requisition on CEX for support through normal DoD channels. 8.11.3. Procedures. These procedures cover the different scenarios the FMS customer may have been authorized by the LOA for how the initial lay-in or follow-on support of spares and support equipment will be supported: single-

vendor integrity (SVI) materiel is to be purchased directly from the prime and subcontractors (see paragraph 8.11.3.3); materiel provided is to be new and unused (see paragraph 8.11.3.4); materiel provided is to be supported through normal DoD supply channels when the Item Manager (IM) can supply the materiel within the required availability date (RAD) reflected on the LOA to include the procedures for how to handle the situations when normal supply channels cannot meet the RAD (see paragraph 8.11.3.5); and support of part-numbered and nonstandard items (see paragraph 8.11.3.6). 8.11.3.1. During system definitization, the ALC PMO, AFSAC command country or case manager, and the FMS customer representatives will list initial support requirements. The requisitions will be processed through the Security Assistance Management Information System (SAMIS) using one or more of the options. 8.11.3.2. Sole-source requisitions can only be input to SAMIS on a case that includes authorization for sole-source procurement. This means the case must be associated and supported with an appropriate sole-source authorization letter and LOA with the necessary terms, conditions, clauses, and annexes. In addition, if SVI is authorized for an FMS customer, then that authority must be explicitly stated in the LOA. Also, when SVI is used, the national stock number, or manufacturer's part number with the federal supply code for manufacture for items requiring SVI, must be provided in the item list maintained in the case file but not part of the LOA. 8.11.3.3. SVI: An FMS customer is granted authority for sole-source acquisition to ensure SVI so that the new item is the same as items already in the customers inventory, installed in the customers unique configurations, and kept in a specific way in the customers own shops. The procedures beginning at paragraph 8.11.3.3.1 or 8.11.3.3.2 must be followed when the FMS customer wants to ensure SVI. 8.11.3.3.1. The SVI process can be accomplished through one of two methods. Method one is to be followed when the ALC PMO prefers ALC IM support requirements through normal procurement procedures by referencing, citing, and using the referenced contract. Method two is to be followed when the ALC PMO decides to accomplish the procurement internally within the Weapon System program directorate. Paragraph 8.11.1 lists those items that are authorized sole-source acquisition and can be bought under SVI procedures and those items that are not authorized sole-source acquisition and cannot be bought under SVI procedures. 8.11.3.3.2. Method one: 8.11.3.3.2.1. The ALC PMO will ensure that an appropriate contracting instrument has been set up with the contractor designated in the LOA. Provisions must be in the contract to allow not only the Air Force but also other services (i.e., Army, Navy, etc.) to reference the contract when needed. 8.11.3.3.2.2. The ALC PMO will submit a sole-source acquisition authorization letter to the ALC IM division focal point having primary inventory control activity (PICA) or secondary inventory control activity (SICA) item management responsibility and the requirements will be supported through the Air Force. The sole-source acquisition authorization letter must reflect the designated contractor source, the logistics reference number (LRN) and commercial and government entity (CAGE) code of the contractor, the country code, and the case designator. 8.11.3.3.2.3. The authorization to buy items sole-source directly by the Air Force applies to those items listed in paragraph 8.11.1. The Air Force SICA IM for other services or agencies reparable items will forward requirements to the managing service via a MIPR. The MIPR must include all contract information to facilitate the acquisition (see AFMAN 23-110, Volume 3, part 3, chapters 3 and 9). 8.11.3.3.2.4. The ALC PMO will submit requisitions as follows: 8.11.3.3.2.4.1. Requisitions for Air Force or other service- or agency-managed items for reparable items where the SICA is Air Force are input with advice code 6V and process code D. These requisitions will generate a 6V exception to the ALC PICA or SICA IM. 8.11.3.3.2.4.2. Requisitions for other service-managed or agency-managed items are input using normal MILSTRIP procedures. These requirements will be supported through normal channels. SAMIS will have edits in place to ensure compliance. SAMIS will reject requirements on CEX that are not in compliance. Before releasing the CEX to the other service/agency, the ALC PMO needs to ensure no internal contractual actions have begun. If contractual actions have been initiated, the ALC PMO needs to ensure these actions are ceased immediately (providing termination charges do not apply). Subsequently, the ALC PMO needs to release the CEX for support through normal DoD channels. 8.11.3.3.2.5. The IM will upon receipt of the 6V exception: 8.11.3.3.2.5.1. Obtain from the division focal point the sole-source-acquisition authorization letter and initiate procurement action as directed by instructions in the letter.

8.11.3.3.2.5.2. The IM will prepare the PR and forward the PR package to contracting or prepare the MIPR and forward the MIPR package to the other service/agency PICA IM. For a PR, the Air Force PICA IM will ensure a record is established in the acquisition asset due-in system (J041) and record the BV status in the stock control system (D035A). For a MIPR, the Air Force SICA IM will record the BV status in the D035A and follow up for procurement status on the MIPR with the PICA IM and ensure the shipment and billing data is received and processed in the D035A and SAMIS. 8.11.3.3.3. Method two: 8.11.3.3.3.1. The ALC PMO will make sure an appropriate contracting instrument has been established with the contractor designated in the LOA. In addition, a Memorandum of Agreement (MOA) will need to be executed among AFSAC/SDID, ALC PMO, Security Assistance Program Manager (SAPM), HQ AFMC/LG, the FMS customer, and any other parties deemed appropriate by the ALC PMO. 8.11.3.3.3.2. The authorization to buy items sole-source by or through the Air Force applies to Air Force-managed and SICA items. Other service/agency items must be requisitioned using normal supply procedures. 8.11.3.3.3.3. The ALC PMO will: 8.11.3.3.3.3.1. Provide a list of required items by electronic media to AFSAC/SDID to process the definitized requirements in SAMIS or manually input the requirements into SAMIS. If the ERRC of the item is C, T, S, or U, and the SOS/RIC is Air Force, the ALC PMO will request SAMIS process the requisition with advice code of BV and a process code of S, overlay SVIC in RP 77-80, and pass it to the prime ALC or manually process the requisition with advice code of BV and a process code of S. If the ERRC is other than C, T, S, or U (i.e., N and P), the ALC PMO will request SAMIS process the requisition with advice code of 2J indicating fill or kill and pass it to the prime ALC D035A or manually process the requisition with advice code 2J. Upon receipt of an AE transaction with status code of CB by SAMIS, the ALC PMO will submit/ generate a new requisition with BV advice code, S process code, and overlay SVIC in RP 77-80. 8.11.3.3.3.3.2. Requisitions for other service/agencies managed items are input using normal MILSTRIP procedures. These requirements will be supported through normal channels. SAMIS will have edits in place to ensure compliance. SAMIS will reject requirements on CEX that are not in compliance. Before releasing the CEX to the other service/agency, the ALC PMO needs to ensure no internal contractual actions have begun. If contractual actions have been initiated, the ALC PMO needs to ensure these actions are ceased immediately (providing termination charges dont apply). Subsequently, the ALC PMO needs to release the CEX for support through normal DoD channels. 8.11.3.3.3.3.3. Research/resubmit rejections. 8.11.3.3.3.3.4. Prepare a PR for Air Force PICA and SICA items and ensure that the PR is established in J041. The PR must cite type PR code 61 to allow the passing of non-prime items to J041 at the prime ALC. 8.11.3.3.3.3.5. For Air Force managed items and Air Force SICA items ensure shipment and billing information is received and appropriately processed in J041, SAMIS, and D035A. 8.11.3.3.3.3.6. Normally, the IM will not act on backorders. However, if necessary, the ALC PMO or SAPM will request assistance from the IM at the prime ALC to take manual action on the requisitions when problems can only be resolved through assistance by the IM. Note that the ALC PMO is responsible for contacting the prime ALC IM to take necessary action even when the IM resides at another ALC. 8.11.3.3.3.4. AFSAC/SDI will: 8.11.3.3.3.4.1. Screen the NSNs against the catalog contained in SAMIS to determine the DoD source of supply (SOS). 8.11.3.3.3.4.2. Provide rejects to the ALC PMO for research and resubmission. 8.11.3.3.3.4.3. If the SAMIS catalog reveals the SOS/RIC is other services/agencies and the materiel will be supplied through the Air Force, SAMIS will assign the requisition number and reject the requisition to the ALC PMO. The rejected transaction will include the appropriate service/agency in the RIC and will reflect a 2L advice code. 8.11.3.3.3.4.4. If the SAMIS catalog indicates the SOS/RIC is the Air Force, SAMIS will generate a requisition with advice of BV and a process code of S, overlay SVIC in card RP 77-80, and pass it to the prime ALC D035A. 8.11.3.3.3.5. D035A will: 8.11.3.3.3.5.1. Check inventory records to see if stock exists (for requisitions with an advice code of 2J). If stock is available, D035A will process a drop from inventory transaction so the materiel will ship. If no inventory is

available, D035A will provide an AE transaction to SAMIS with CB status killing or, in effect, canceling the requisition. 8.11.3.3.3.5.2. For requisitions with advice code BV, process code of S, and SVIC in RP 77-80, D035A will automatically establish a BV backorder. 8.11.3.3.3.6. Prime ALC IM will: 8.11.3.3.3.6.1. Assist the ALC PMO or SAPM to resolve all SVI requisitioning issues if requested. 8.11.3.4. New and Unused Process: 8.11.3.4.1. When the FMS customer has stated that sole-source acquisition is authorized and new and unused material is to be supplied, then initial lay-in procedures stated in 8.11.3.3, and either 8.11.3.3.1 (SVI method one) or 8.11.3.3.2. (SVI method two) can be utilized. 8.11.3.4.2. In addition, when sole-source authorization is included or added to a follow-on support case and new and unused is to be supplied, the procedures contained in paragraph 8.11.3.3 (method one) are applicable with the following modifications. Method two procedures cannot be used. 8.11.3.4.2.1. In paragraph 8.11.3.3.1.1, the ALC PMO needs to be replaced with the AFSAC case manager. The AFSAC case manager will use AFSAC/PK to select or establish a contracting instrument and ensure a copy of the contract is provided to ALC IM divisional focal point. 8.11.3.4.2.2. In paragraph 8.11.3.3.1.2, the ALC PMO needs to be replaced with AFSAC case manager. The AFSAC case manager must provide the ALC divisional focal point with the requisite sole-source letter containing the designated contractor source, the LRN, CAGE, country code, and the case designator. 8.11.3.4.2.3. Paragraph 8.11.3.3.1.3 requires no changes. However, the ALC IM should be informed the contract information originated from a contract that was not negotiated at the prime ALC. 8.11.3.4.2.4. Paragraphs 8.11.3.3.1.4 and 8.11.3.3.1.4.2, the ALC PMO needs to be replaced with AFSAC case manager. 8.11.3.4.2.5. Paragraphs 8.11.3.3.1.4.1, 8.11.3.3.1.5, 8.11.3.3.1.5.1, and 8.11.3.3.1.5.2 require no changes. However, AFSAC/PK must ensure that the case manager is provided with procurement status and shipping information. The AFSAC case manager must ensure the shipping status is provided to the prime ALC IM. The ALC IM must ensure the shipping information is overlaid in J041 and D035A. 8.11.3.5. Support provided through normal supply channels. 8.11.3.5.1. Initial support procedures. When an FMS customer authorizes the use of sole-source acquisition to get items shown in initial activation cases for which the RAD cannot be met through normal supply or acquisition channels, the following procedures will apply: 8.11.3.5.1.1. The ALC PMO will make sure a contract exists with the prime contractor (as designated in the LOA). Provisions must be included in the contract to allow not only the Air Force, but other services/agencies (i.e., Army, Navy, etc.) to reference this contract to acquire items when needed. The contract can then be used by the IMs of all services to obtain items that cannot be supplied within the RAD through normal supply or acquisition channels. 8.11.3.5.1.2. The ALC PMO will submit a sole-source-acquisition-authorization letter (SSAL) to the ALC focal point having PICA or SICA responsibility for reparables that will be supported through the Air Force. The SSAL must reflect the designated contractor source, the LRN, and the contractor CAGE code, the country code, and the case designator. Additionally, the following statement will be addressed: 8.11.3.5.1.2.1. Item(s) associated with the case will be supplied through normal supply or acquisition channels, if such methods permit delivery of the item(s) within the RAD. 8.11.3.5.1.3. The authorization to buy items sole-source directly by the Air Force applies to those items listed in paragraph 8.11.1. 8.11.3.5.1.4. Items for which the Air Force is the PICA, and which cannot be provided through normal supply or acquisition channels within the RAD, may be purchased by the IM sole-source through the prime contractor by referencing the contract number. 8.11.3.5.1.5. Requirements for other-service-managed items, where the Air Force is the SICA, are sent to the managing service on a reimbursement-funded requisition when the item can be supplied by the PICA within the RAD. If the managing service cannot provide the item within the RAD through normal supply or purchase channels, the use of a MIPR is needed. The MIPR will contain all applicable contract information to facilitate the purchase process for the PICA IM. (See AFMAN 23-110, Volume 3, part 3.) 8.11.3.5.1.6. The ALC PMO will submit requisitions with advice code 6W and process code D.

8.11.3.5.1.6.1. Requisitions for Air Force-managed items, and Air Force SICA items for which the requirements will be supported through the Air Force, are input with advice code 6W and process code D. This allows requisitions to fill automatically from stock above the control level. If stock is below the control level, a 6V exception is sent to the IM. 8.11.3.5.1.6.2. Requisitions for other service-managed or agency-managed items are input using normal MILSTRIP procedures. These requirements will be supported through normal channels. SAMIS will have edits in place to ensure compliance. SAMIS will reject requirements on a control exception (CEX) that are not in compliance. Before releasing the CEX to the other service/agency, the ALC PMO needs to ensure that no internal contractual actions have begun. If contractual actions have been initiated, the ALC PMO needs to ensure these actions are ceased immediately (providing termination charges do not apply). Subsequently, the ALC PMO needs to release the CEX for support through normal DoD channels. 8.11.3.5.1.7. The ALC IM should note that the contract information included in the MIPR package may come from a contract that was not negotiated at the prime ALC. The IM will, upon receipt of the 6V exception: 8.11.3.5.1.7.1. Procure Air Force-managed items through normal supply or acquisition channels if the item can be provided by the RAD. 8.11.3.5.1.7.2. Prepare a purchase request (PR), including the sole-source-acquisition request, and send it to contracting, citing the contract in the sole-source-acquisition-authorization letter, if normal supply or acquisition channels will not allow Air Force-managed items to be provided within the RAD. Furnish the information to contracting, ensure a record is established in J041, and process the BV in D035A, etc. 8.11.3.5.1.7.3. For items with an Air Force SICA but which are requisitioned through the PICA, the IM will contact the other-service or -agency IM to determine the type of document (reimbursable-funded requisition or MIPR) needed to acquire the item within the RAD. If a MIPR is requested by the managing service or agency, include the applicable contract information on the MIPR for the PICA IM to cite in procuring and satisfying the requirement. (See AFMAN 23-110, Volume 3, part 3.) 8.11.3.5.1.7.4. The IM will prepare the MIPR, furnish the information to the PICA IM, ensure status is updated in the D035A system, etc. 8.11.3.5.2. Follow-on Support Procedures. When an FMS customer authorizes the use of sole-source acquisition to ensure items are received within the RAD, the following procedures will apply: 8.11.3.5.2.1. The AFSAC case manager will make sure a contract exists with the prime contractor (as designated in the LOA). Provisions must include allowance for not only the Air Force, but other services/agencies (i.e., Army, Navy, etc.) to reference this contract to acquire items when needed. The contract can then be used by the IMs of all services to obtain items that cannot be supplied within the RAD through normal supply or acquisition channels. The AFSAC case manager will use AFSAC/PK to select or establish the contract and to ensure that a copy is provided to the ALC IM divisional focal point. 8.11.3.5.2.2. The AFSAC case manager will submit a SSAL to the ALC focal point having PICA or SICA responsibility for reparables that will be supported through the Air Force. The SSAL must reflect the designated contractor source, the LRN, and the contractor CAGE code, the country code, and the case designator. The AFSAC case manager must provide the ALC divisional focal point with the requisite sole-source letter containing the designated contractor source, LRN, CAGE, country code, and case designator. Additionally, the following statement will be addressed: 8.11.3.5.2.2.1. Item(s) associated with the case will be supplied through normal supply or acquisition channels, if such methods permit delivery of the item(s) within the RAD. 8.11.3.5.2.3. The authorization to buy items sole-source directly by the Air Force applies to those items listed in paragraph 8.11.1. 8.11.3.5.2.4. Items for which the Air Force is the PICA, and which cannot be provided through normal supply or acquisition channels within the RAD, may be purchased by the IM sole-source through the prime contractor by referencing the contract number. 8.11.3.5.2.5. Requirements for other-service-managed items, where the Air Force is the SICA, are sent to the managing service on a reimbursement-funded requisition when the item can be supplied by the PICA within the RAD. If the managing service cannot provide the item within the RAD through normal supply or purchase channels, the use of a MIPR is needed. The MIPR will contain all applicable contract information to facilitate the purchase process for the PICA IM. (See AFMAN 23-110, Volume 3.) 8.11.3.5.2.6. The AFSAC case manager will submit requisitions with advice code 6W and process code D.

8.11.3.5.2.6.1. Requisitions for Air Force-managed items, and Air Force SICA items for which the requirements will be supported through the Air Force, are input with advice code 6W and process code D. This allows requisitions to fill automatically from stock above the control level. If stock is below the control level, a 6V exception is sent to the IM. 8.11.3.5.2.6.2. Requisitions for other service-managed or agency-managed items are input using normal MILSTRIP procedures. These requirements will be supported through normal channels. SAMIS will have edits in place to ensure compliance. SAMIS will reject requirements on a CEX that are not in compliance. Before releasing the CEX to the other service/agency, the ALC PMO needs to ensure that no internal contractual actions have begun. If contractual actions have been initiated, the ALC PMO needs to ensure these actions are ceased immediately (providing termination charges do not apply). Subsequently, the ALC PMO needs to release the CEX for support through normal DoD channels. 8.11.3.5.2.7. The IM will, upon receipt of the 6V exception: 8.11.3.5.2.7.1. Procure Air Force-managed items through normal supply or acquisition channels if the item can be provided by the required availability date (RAD). 8.11.3.5.2.7.2. Prepare a purchase request (PR), including the sole-source-acquisition request, and send it to contracting, citing the contract in the sole-source-acquisition-authorization letter, if normal supply or acquisition channels will not allow Air Force-managed items to be provided within the RAD. Furnish the information to contracting, ensure a record is established in J041, and process the BV in D035A, etc. 8.11.3.5.2.7.3. For items with an Air Force SICA but which are requisitioned through the PICA, the IM will contact the other-service or agency IM to determine the type of document (reimbursable-funded requisition or MIPR) needed to acquire the item within the RAD. If a MIPR is requested by the managing service or agency, include the applicable contract information on the MIPR for the PICA IM to cite in procuring and satisfying the requirement. (See AFMAN 23-110, Volume 3.) 8.11.3.5.2.7.4. The AFSAC case manager must ensure the shipping status is passed to the prime ALC IM. The IM then ensures the status is overlaid into the D035A. The IM will also prepare the MIPR and furnish the information to the PICA IM, etc. 8.11.3.6. Nonstandard Item Support Process: When an FMS customer's authorization of sole-source acquisition has nonstandard items or part-numbered items that are not cross-referenced to an NSN, the following procedures will apply. (NOTE: This process encompasses all of the scenarios outlined above.) 8.11.3.6.1. The ALC PMO on initial activation cases and the AFSAC case manager for follow-on support cases will interrogate D043 and DLIS total item record to determine if NSNs or NC (temporary stock number) management control numbers have already been established for the desired part numbers. 8.11.3.6.2. The ALC PMO on initial activation cases may either submit the part numbered requisition through SAMIS to the AFSACs nonstandard contractor or initiate cataloging action to have a NC stock number assigned. ND number assignment will not be accomplished. 8.11.3.6.3. The ALC PMO on initial activation cases will follow the procedures outlined in paragraph 8.11.3, option 1, 2, or 3 when requisitioning either nonstandard NSNs or NC stock numbered items. Part-numbered requisitions will be processed through the AFSAC nonstandard support contractor in accordance with these instructions: 8.11.3.6.3.1. The AFSAC case manager for follow-on support cases will establish document numbers to requisition the desired item with the LRN and CAGE. 8.11.3.6.3.2. The AFSAC case manager for follow-on support cases will check that all LRN requests with no record of an NSN or NC number are submitted to SAMIS as part-numbered requisitions and passed to the AFSACs nonstandard contractor. 8.11.3.6.3.3. The AFSAC case manager will submit the sole-source acquisition authorization letter to the AFSAC nonstandard support contractor. The sole-source acquisition authorization letter must specify the guidelines that the contractor is to follow in supporting the materiel requirements. 8.12. Special Purchase Requirements. 8.12.1. Local purchase/local manufacture (LP/LM) and commercial-type items. LP/LM or commercial-type items are bought from local or common commercial sources. Usually, these items are not authorized for sale through FMS channels. However, LP/LM items may be bought through FMS cases, if items cannot be found in the requesting country. Specific supply groups and federal supply classifications of commercial-type items are in the DoD 5105.38 (SAMM).

8.12.1.1. For defined-order cases, the FMS customer must state on the pricing study the items or services which are not available from in-country commercial sources. 8.12.1.2. On blanket-order cases, a customer-prepared requisition with advice code 3B or 2A is the customer's claim that the item is not available from in-country commercial sources. Advice code 3B is used for commercialtype items. Advice code 2A is used for LP/LM items. 8.12.1.3. Regardless of the type of case, AFSAC should transfer all cases with SAMIS commercial consumable code 7 (defined as ineligible for LP/LM/commercial-type requisitions) to D035A. D035A edits all LP/LM or commercial-type item requisitions and rejects them if advice codes 3B or 2A haven't been used. On definedorder cases, the case manager is responsible for using the correct advice code. 8.12.2. First-Article-Testing Requirements. First Article Testing (FAT) will be funded as follows. 8.12.2.1. For a combined USAF/FMS buy. 8.12.2.1.1. Materiel Support Division (MSD). For a combined USAF/FMS buy using MSD OA, the MSD will pay for the first article item, report, and testing. The approved first article item will be placed in Air Force stock, if not destroyed in testing. MSD costs are automatically pro-rated to all customers through the MSD Operational Cost Recovery elements. No special action is required. 8.12.2.1.2. Non-MSD. For a combined USAF/FMS buy, informational sublines will be used on the contract to prorate the contractor first article costs. 8.12.2.1.2.1. If the first article item is to be destroyed in testing, the contractor FAT costs are to be prorated among the USAF and the FMS customers. The prorate is to be based on the quantity of materiel ordered and defined in the PR and on the contract. 8.12.2.1.2.2. If the first article item is not to be destroyed in testing, the USAF portion of the prorate will include the item cost plus part of the other contractor FAT cost. The FMS portion will not include the item cost. Upon completion of the test, the first article item will be placed in USAF stock. 8.12.2.1.2.3. Using the contract information, the ALC DFAS will bill accordingly. The billing against the FMS case should be identified as FAT costs. 8.12.2.2. For a single-country FMS buy using FMS funds, case funds will be used to pay for the contractor FAT costs. The approved first-article item will be returned to the contractor, if not destroyed in testing, for shipment with the production items direct to the customer. 8.12.3. For a multiple-country FMS buy using FMS funds, information sublines will be used on the contract to prorate the contractor FAT costs. 8.12.3.1. If the first-article item is to be destroyed in testing, the contractor FAT costs are to be prorated among all the FMS customers. The prorate is to be based on the quantity of materiel ordered and defined in the PR and on the contract. 8.12.3.2. If the first-article item is not to be destroyed in testing, the item costs are not to be prorated, but the other contract FAT costs are. Upon completion of the test, the first article item is to be returned to the contractor for shipment with the production items to the FMS customers. 8.12.3.3. Using the contract information, the DFAS operating location will bill accordingly. The billing against the FMS case should be identified as FAT costs. 8.12.4. FAT costs include the item cost (if destroyed in testing), the actual testing costs, and the test report cost. In the paragraphs above, the term contractor FAT costs refers to those FAT cost elements that are included in the contract. If the Air Force does the actual testing, it will not be included in the contract. If the Air Force does the testing and the testing costs can be identified, they should be prorated to the FMS customers accordingly. 8.12.5. To ensure that sufficient case funds are available, the initial pricing of the item to the FMS customer must include all costs, including FAT. If required, normal price increase approval procedures apply. 8.12.6. If FAT is required, and an Air Force-funded buy is scheduled in the near future, the AFSAC case manager should be queried by the IM as to whether a separate FMS-funded buy should be pursued. Consolidating the buys could save money for both the Air Force and the FMS customer. 8.12.7. The IM should identify the need to prorate FAT costs by placing the statement Prorate any First-Article Costs in the Note to Buyer section of an automated PR, or block 12 of a manual PR. 8.12.8. The contract must have provisions for transportation to and from the testing facility, which are to be the responsibility of the contractor. 8.12.9. All situations involving the first-article process are not covered here. Unique situations must be handled appropriately as they occur.

8.13. Thru 8.17. (Unused.) Section 8CPROCESSING FMS REQUISITIONS 8.18. Purpose. 8.18.1. This section provides guidance for processing FMS requisitions. These procedures supplement DoD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures (MILSTRIP) requirements. 8.18.2. These procedures do not apply to the types of materiel identified in Chapter 25, Section B, Part 1, Volume I. These are: 8.18.2.1. Bulk petroleum. 8.18.2.2. Inter- and intra-departmental buying operations. 8.18.2.3. Forms and publications. (However, requirements for these items placed on General Services Administration (GSA) and Navy are submitted in MILSTRIP requisition format.) 8.18.2.4. Information security (INFOSEC) equipment; INFOSEC aids (keying materiel); cryptological items that have classified parts; repair parts that are classified and designated cryptological, or which are usually handled through cryptological channels. 8.18.2.5. Coal and coke. 8.19. Defined-Order Case Requisition Processing. 8.19.1. Defined-order cases are requested by the FMS customer to buy specified quantities of specific items. These cases are written and implemented by the Air Force Security Assistance Center (AFSAC) and are assigned to a case manager in the AFSAC. 8.19.2. Requisitions are input to the SAMIS by the AFSAC case manager/supply technician in MILSTRIP or custom order format as shown in attachment 8C4. 8.19.3. The following products will be output from SAMIS: 8.19.3.1. The referral orders (A4) and passing orders (A3) are made up and sent according to the criteria set up by the process code (see attachment 8C7). 8.19.3.2. AFSAC sends a BU or BW status, which acts as a duplicate of the requisition input, to the FMS customer's representative. 8.19.3.3. The supply and shipment status reports/documents are sent to the FMS customer representative (CR)/freight forwarder (FF) address (from the freight forwarder code (RP 47)) set up in the Letter of Offer and Acceptance and case directive. This is identified by the media and status code RP 7. The FMS CR/FF addresses to which supply and shipment status reports/documents are sent are shown in the Military Assistance Program Address Directory (MAPAD), by FF code, under type of address code 4. 8.19.3.4. BU, BW, BM, and other status codes give the FMS CR the capability of relating supply/shipment status to the case and item, and should be used to monitor the FMS case through supply completion. The BU code gives the first input to the FMS customer master due-in records. 8.19.4. SAMIS validates requisitions before passing them to the supply point. 8.20. Preparation and Processing of Requisitions Against Follow-on E and Blanket-Order Cases. 8.20.1. E cases are set up to order support-equipment-related supply items of US origin that are frequently used by the customer. A blanket-order case sets up a dollar value for buying items that may be needed during the case requisitioning period. The requisition period is usually for one year with a maximum of two years. 8.20.2. R cases are set up to order spare parts of US origin. This case sets the dollar value for items that the customer requisitions for the period of the case (usually one year, with a maximum of two years). As a rule, only one R case is needed for each customer. 8.20.3. Requisitions for E and R cases are input by the FMS customers and must be in MILSTRIP format per DoD 4000.25-1-M. Items requisitioned under these procedures are usually from USAF catalogs, technical orders, parts listings, and other publications associated with the end-item. These publications are used to get stock number data. Requests for ALC identification help are sent to the AFSAC. The FMS customers (or the AFSAC) requisition a quantity of materiel that has a minimum value of $10 per line item. This policy is necessary because of the cost of processing and shipping low-dollar-value items. These cases will not be used to supply items to contractors or commercial agents involved in direct contracts unless they were set up as a representative of the customer and were approved by SAF/IA. 8.20.4. The AFSAC case managers will negotiate the LOAs and set up the appropriate types of cases. These cases have the following characteristics:

8.20.4.1. Each case is usually for one year, but may be for as long as two years, and set up according to the customer's fiscal or calendar year. 8.20.4.2. The first digit of the case designator is E or R for these cases. 8.20.4.3. Priority designators are given by the requisitioners using the force activity designator (FAD) related to the urgency-of-need designator (UND) as shown in attachment 8A3, Chapter 24, Part 1, Volume I. The FAD is found in the LOA. 8.20.4.4. Each case has an estimated cash dollar value for control purposes. The dollar value can be adjusted as necessary. 8.20.4.5. Requisitions are usually filled or stay on backorder until filled, except when advice code 2C causes the requisition to either be filled by the required delivery date (RDD) or be cancelled (referred to as fill or kill). 8.20.5. Requisitions are sent by mail, DAAS, message traffic, or other means. The rules for submitting requisitions and preparing messages (Chapter 25, Part 1, Volume I) apply to FMS requisitioning. 8.20.6. Requisitions are sent by mail via disc format or transmitted via e-mail. Postal mailings are addressed as follows: AFSAC, 1822 Van Patton Drive, Wright Patterson AFB OH 45433-5337. Containers/envelopes will be marked, FMS MILSTRIP Requisitions. 8.20.7. Customer initiated requisitions will go through initial processing by SAMIS. Initial processing includes editing, validating, pricing, and recording the commitment in the case master record. 8.20.8. Requisitions are released by SAMIS through referral orders to the inventory management specialist (IMS) at the appropriate ALC. SAMIS sends requisitions for items managed by Defense Logistics Agency (DLA)/GSA to the appropriate DLA/GSA activity for supply action. 8.20.9. Upon release of the referral-/passing-order, SAMIS will send the supply status (code BW) to the appropriate recipient as designated in the MAPAD. 8.20.10. The AFSAC monitors the FMS blanket-order requisition case(s), and is responsible for the following related actions: 8.20.10.1. Acting as point of contact for authorized foreign government representatives for processing requisition type cases. 8.20.10.2. Setting up and keeping the case administrative file during the active life of the case. The file will contain copies of all correspondence and reports related to the case. 8.20.10.3. Informing the ALC(s) of the case termination date to ensure proper and timely closing of cases. 8.20.11. Customer requisitions are prepared on DD Form 1348m or 1348, DoD Single Line Item Requisition System Document (Mechanical) or (Manual), or other means in accordance with Chapter 25, Part 1, Volume I. See attachment 8C4. 8.21. Submission of Requisitions, Follow-ups, Cancellations, and Requisition Modifiers. 8.21.1. The following countries may route all generated MILSTRIP traffic to the proper Defense Messaging System (DMS) station shown below for processing: COUNTRY Australia Belgium Canada Denmark Germany Greece NATO Netherlands Norway Philippines South Korea Spain Taiwan Thailand United Kingdom STATION Tracy Dayton Dayton Dayton Dayton Dayton Dayton Dayton Dayton Tracy Tracy Dayton Tracy Tracy Dayton

NOTE: DMS routine indicator for Tracy is RUWJZZA and for Dayton the routing indicator is RUEDZZA. 8.21.1.1. DMS messages with MILSTRIP transactions for DAAS processing should always have a constantcontent-indicator code of IAZZ. 8.21.1.2. DMS has a program which is used to process security assistance (SA) program transactions and route requisitions directly to SAMIS by inserting FNH in RP 4-6. Without this program, DAAS would merely pass these transactions to the routing identifier entered by the originator. 8.21.2. MILSTRIP Follow-up. 8.21.2.1. FMS customers will submit follow-ups by DMS or mail in MILSTRIP card format to the 88th Air Base Wing (ABW), routing identifier FNH. Follow-ups are prepared and input per Chapter 25, Part 1, Volume I. AFMC recommends that FMS customers input AFC (card or letter) transactions instead of messages when asking for better estimated shipping dates (ESD) on their priority 1-8 requisitions. The use of message traffic is discouraged as a general way of following up. FMS customers may submit follow-ups under document identifier codes AF___/____ or AT___/____ series and are processed as follows: 8.21.2.1.1. By Mail (Card Form). 8.21.2.1.1.1. After getting an AF___/___ or AT___/___ MILSTRIP follow-up transaction through the mail, AFSAC will input it to SAMIS for referral to the source of supply. When processing AT___/___ transactions, if no record of a requisition exists and the document number date is not older than 120 days, SAMIS will create an open requisition and pass the AT___/___ to the source of supply. 8.21.2.1.1.2. If the document number date is older than 120 days and matches an open requisition, the AT___/___ is changed to a follow-up and sent to the source of supply. 8.21.2.1.1.3. If the follow up is on an LRN requisition less than 30 days old, an AF___/___ transaction is sent to the source of supply. Processing to SAMIS is done next when status is received from the source of supply. 8.21.2.1.2. By Message or Letter. 8.21.2.1.2.1. AFSAC determines if the correspondence is a routine MILSTRIP follow up. If it is a routine followup, AFSAC prepares an AF___/___ transaction and inputs it to SAMIS. Status is sent to the FMS customer through usual channels. 8.21.2.2. If the materiel was shipped, inform the FMS customer, give correct shipping information and suggest tracer action through the freight forwarder. If the method of shipment is the defense transportation system (DTS), check with the shipping ALCDST/DFS office. If an item shipped but delivery was not reported, request a 165D interrogation and contact Defense Finance and Accounting Service (DFAS-AIA/DY). 8.21.2.3. If the requisition was cancelled, take action depending on the type of case used as follows: 8.21.2.3.1. If the cancellation is for a country-input requisition (serial numbers in RP 40-43 less than 5000), tell the FMS customer the cancellation code, the reason (if available), date, and source. 8.21.2.3.2. If the cancellation is for a system sales case requisition (serial number 5000 or higher (excluding 80008999) with S, D, or Y case designator), the follow-up will be sent to the SPM for an explanation, with an informational copy to the IMS and the FMS customer. 8.21.2.3.3. If the cancellation is for a defined-order case requisition (serial numbers 7600-7899), action is taken by AFSAC to have the IMS reinstate the requisition for supply action since there is little justification for canceling a defined-order case requirement. 8.21.2.4. If the SAMIS interrogation is negative (no record) and the date of the document is within 120 days, establish the requisition in SAMIS with a D process code to make sure computer passing action of the referral order occurs. 8.21.2.5. If the above possibilities do not apply, send correspondence to the last known source of supply for action and inform the FMS customer. 8.21.2.6. After getting AF___/___ transactions through the mail from the FMS customer, the ALC focal point will input these transactions into the D035a system. The latest status is sent automatically to the customer through SAMIS, by DAAS, to update records. 8.21.2.7. After getting a follow-up message or letter from either AFSAC or the FMS customer, the ALC focal point will: 8.21.2.7.1. Suspense the correspondence for a reply. 8.21.2.7.2. Interrogate D035a for new status. 8.21.2.7.3. Tell the FMS customer and send an informational copy to AFSAC.

8.21.2.8. After getting SA program action cards with C-type cancellations and BF status, the IMS focal point will process them according to Chapters 5 And 6, Part Three, Volume III. The IMS division focal point will coordinate with the SPM, or S case requisitioner, when deciding appropriate action. 8.21.2.9. Replies to follow-ups that include supply status are made with document identifiers in the AE__/__ series. 8.21.3. CA Requisition Cancellations. Cancellation of FMS customer requisitions is governed by MILSTRIP (DoD 4000.25-1-M) and Chapter 19, Part Three, Volume III. Cancellations are grouped into two broad types: computer generated, which is assigned a self-explanatory code; and CA, which is manually assigned a code by the IMS, which must be explained. These procedures explain CA cancellation. 8.21.3.1. The IMS or equipment specialist will: 8.21.3.1.1. Get approval of the IMSs international logistics program (ILP) focal point and first-line supervisor for all FMS CA cancellations. 8.21.3.1.2. Tell the FMS customer by message for priority 1-8 and by form letter or OF 27 (2-way memo) for routine (priority 9-15) cancellations. Requisitions with serial numbers less than 5000 are for a country-submitted requisition. FMS customers' addresses for receipt of supply status should come from DoD 4100.25-8-M (MAPAD). 8.21.3.1.3. Not cancel Army- or Navy-managed items for which the Air Force is a user, but will fund and pass the requisition to the inventory control point (ICP) shown in RP 74-76 of the A41 referral order. The ICP identity may also be obtained from a Defense Logistics Supply Center (DLSC) interrogation. 8.21.3.1.4. Not cancel requisitions for the following reasons. 8.21.3.1.4.1. High or excessive quantities. 8.21.3.1.4.2. Stocks not available. 8.21.3.1.4.3. Excessive lead-time. 8.21.3.1.4.4. Acquisition needed. 8.21.3.1.4.5. Item applicable to a weapon system not in country. 8.21.3.1.4.6. Quantity less than the vendor's minimum sale/minimum buy quantity (MBQ). 8.21.3.1.4.7. Lack of funding. NOTE: These conditions should be brought to the attention of the ILP requisitioning focal point. 8.21.3.1.5. Not cancel any FMS defined-order requisition without prior approval of the AFSAC case manager. 8.21.3.1.6. Not cancel any FMS initial activation case (S, D, Y) requisition without approval of the SPM/end article IMS. The ALC SPM can be determined from the document serial number contained in RP 40-43. 8.21.3.1.7. Send the AFSAC case manager an informational copy of all cancellation correspondence on which AFSAC is not an action addressee. 8.21.3.1.8. Ask the AFSAC case manager for help with unresolved problems. 8.21.3.1.9. Reinstate CA erroneously entered cancellations. 8.21.3.1.10. Not cancel H (RP 40) FMS reparable-return-coded requisitions. Problems are resolved in coordination with the AFSAC case manager. 8.21.3.1.11. Check with procurement for termination liability. 8.21.3.2. The AFSAC case manager will: 8.21.3.2.1. Review all CA correspondence on defined-order case requisitions. 8.21.3.2.2. Help the IMS/SPM as requested. 8.21.3.2.3. Make sure that CA cancellations are processed through SAMIS. The case manager will start action as needed when a CA cancellation notice does not have a matching entry on the Cancellation Report (UW001.-HBK). 8.21.3.3. The SPM/end-item IMS will: 8.21.3.3.1. Review all CA correspondence on S case requisitions. 8.21.3.3.1.1. Reply to the IMS indicating approval if the reason for the CA is valid. 8.21.3.3.1.2. Disapprove the IMS request if the reason for the CA is not valid. Include an explanation for the disapproval in correspondence to the IMS. 8.21.3.3.2. Help the IMS as requested. 8.21.3.3.3. Send a copy of the CA correspondence to the AFSAC case manager. 8.21.4. Requisitioner Modifier Action. Country-submitted requisitions, previously input to SAMIS, are modified to change priority designators and required delivery dates with the conditions given in Chapter 24, Part One, Volume I. Full-mission-capable requisitions are downgraded by the input of document identifiers AM___ with RP 62-64

left blank. NMCS requisitions are upgraded as necessary by AM___/___ document identifiers with the NMCS indicator in RP 62-64. 8.22. Federal Aviation Administration (FAA) Requisition Processing. 8.22.1. To process exception code 1C LRN requisitions for FAA managed items: 8.22.1.1. The AFSAC case manager (CM) will process them the same as any other MILSTRIP requisition. If edits occur at this level, the AFSAC CM will take appropriate action to correct. 8.22.1.2. The ALC, after getting the requisitions, gets a DLSC P/N screen and, if FAA-managed, does the following: 8.22.1.2.1. Clears the exception using status code BM (RP 65-66) to F6N (routing identifier code, RP 67-69), and changes the document identifier code to A05 (RP 1-3) to stop mechanical passing action. 8.22.1.2.2. Mails the controlled exception (D035) and DLSC screening results to OC-ALC/LIZA. 8.22.2. To process exception code 3A, (NSN requisition exceptions for FAA-managed items), take the following action: 8.22.2.1. The ALC edits and returns the requisition to AFSAC. The AFSAC CM: 8.22.2.1.1. Re-inputs the completed requisition into SAMIS for funds commitment with the following information added/overlaid: 8.22.2.1.1.1. RP 4-6 FNH. 8.22.2.1.1.2. RP 54 N. 8.22.2.1.1.3. RP 55-56 Last two positions of line item number. 8.22.2.1.1.4. RP 57-59 Y26. 8.22.2.1.1.5. RP 71 X. 8.22.2.2. Sends the requisition data to OC-ALC/LIZA for further processing. SAMIS output product, Passing/Referral Order and A05 Acceptance List, is the best way to transmit. Message forms are used for urgent requirements. 8.22.3. OC-ALC/LIZA processes either of the above as follows: 8.22.3.1. Changes the FAA requisition in MILSTRIP format to the special FAA format using the correct OCALC/LIZA fund citation. 8.22.3.2. Submits the requirement to the FAA depot at Oklahoma City for supply action. 8.22.3.3. Processes status actions in MILSTRIP format by DMS to AFSAC for input into SAMIS (RP 54 -N) using AE3/ AS3. 8.22.3.4. Receives SF 1080, Voucher for Transfers Between Appropriations and/or Funds, billing from the FAA depot at Oklahoma City for payment and later delivery reporting on the FMS Detailed Delivery Report. 8.22.4. The AFSAC CM issues the FMS Notice of Supply/Services Completion Report after completing all delivery reporting actions. 8.23. Requisition Process for Shelf-Life Items. 8.23.1. DoD shelf-life-management policy is given in DoDI 4140.27, DoD Shelf-Life Management Policy, and DoD 4140.27-M. Air Force guidance is in Chapter 10, Section Q, Part One, Volume I. 8.23.2. Requisitioning of critical end-use sealants and adhesives in FSC 8030-8040 for FMS customers involves the following: 8.23.2.1. Critical end-use sealants and adhesives, FSC 8030-8040, are usually unavailable in condition code A. Condition-code-A materials must have at least a remaining shelf life of 180 days and will be provided for priority 09-15 requisitions unless the customer agrees to accept materiel with a lesser shelf life. 8.23.2.2. FMS requisitions for critical materiel in the FSC 8030-8040, are filled using the freshest material available, usually with condition code B. Condition code B, critical materials, must have at least 90 days of shelf life remaining and will use priority 01-08 unless the customer agrees to accept material with a lesser shelf life. 8.23.2.3. FMS customers who requisition all critical shelf-life items should make sure that timely transportation is available. This can be done by FMS customers telling their freight forwarder not to hold or store critical shelf-life items, but to speed up these items on a shipped-when-received basis. 8.23.3. Reports of discrepancy will not be approved for expired shelf life on critical sealants and adhesives, FSC 8030-8040 items.

8.24. US Navy Processing of Air Force FMS Requisitions. 8.24.1. Requisitions for Air Force items managed by the US Navy are passed from SAMIS and/or the ALC (D035A system) to the Navy ICP with an NL (reimbursable) fund code. 8.24.2. After the Navy gets the requisition, the ICP will: 8.24.2.1. Get the item from current stock or due-ins, ship to the FMS customer, and send an interfund bill to DFAS Denver for reimbursement or, 8.24.2.2. Change the NL fund code to 4F (direct-cite), and give BV status by message to DFAS-AIA/DY in MILSTRIP format. DFAS-AIA/DY will then prepare AE3 status for input to SAMIS and process a commitment in H069. 8.24.3. After changing the fund code and giving the necessary data, the Navy can enter and contract for a not-toexceed price, the standard price plus ten percent. When the contract is finalized, a copy is sent to DFAS-AIA/DY with an informational copy to the AFSAC geographic offices. 8.24.4. When the proposed contractor quote to meet the requirement exceeds the standard price plus ten percent, the Navy ICP will tell DFAS-AIA/DY by telephone and request obligation authority to enter into a contract. DFAS-AIA/DY (with AFSAC coordination) will confirm or deny the request by message or telephone within five workdays after getting the request from the Navy ICP. All confirmations by telephone to the Navy will be confirmed by message within 48 hours. 8.24.5. All contracts written by Navy procurement should cite AD SN 503000 as the paying station on the contract. The Navy will not make payments to contractors for items bought under these procedures. Payments are made by DFAS-AIA/DY. Materiel/receipt documents (DD Forms 250, Material Inspection and Receiving Report) are provided to DFAS-AIA/DY by the administrative contracting office (ACO). 8.25. Processing Materiel Release Orders (MRO) and Redistribution Orders (RDO) to Support FMS Requirements. 8.25.1. The procedures in Chapter 15, Part Three, Volume III, apply to FMS MRO and RDO as follows: 8.25.1.1. MROs. It is the responsibility of the directorate of distribution (DS) of the storage and distribution point (SDP) to decide rules for shipment with the type of option code and freight forwarder code in RP 46-47, DD Form 1348-1, DoD Single Line Item Release/Receipt Document. The freight forwarder codes and related addresses are listed in DoD 4000.25-8-M. 8.25.1.2. Redistribution Orders. The use of RDOs for FMS will be used only in those instances when other processes are not available to supply materiel. 8.25.1.2.1. RDOs are issued only to Air Force bases for priority designators 01-08 (or to AFMC depot supply activities for priority designators 01-15) when FMS requirements cannot be filled from IMS stocks, and when the availability of the materiel has been set as described in Chapter 6, Part One, Volume III. 8.25.1.2.2. Such RDOs to Air Force bases will direct shipment of the materiel to the IMS (or when more economical, to the nearest ALC) for inspection, repackaging, and shipment. The FMS offer/release procedures show that priority designators 01-08 are shipped automatically. Therefore, Air Force bases are given in-the-clear shipping and mark for instructions. 8.25.1.2.3. The DD Form 1348-1 used to move the materiel from the Air Force base to the ALC will have a statement in blocks FF and GG, saying that the materiel is to be inspected and repacked by the receiving ALC before shipment to the CR/FF. The in-the-clear shipping and mark-for instructions will also be stated. 8.25.1.2.4. DD Forms 1348-1, initiated as a result of RDOs to the ALC depot supply activities, are processed in the same way as requisitions released by the IMS stock control and distribution (SC&D) system. 8.25.1.3. RDOs against overseas Air Force bases are held to a minimum. This type of transaction must also have special shipping and transportation billing instructions to allow direct shipment to the customer, and must be processed in message format. The local Air Force inspector must inspect each item before shipment. The initiator of the RDO is told of the condition of the materiel when the items are in used condition but still serviceable. The customer is asked to accept the materiel, and if approved, the overseas Air Force base will preserve and package the item for shipment to the FMS customer. 8.26. Preparation and Distribution of DD Form 1348-1, DoD Single Line Item Release/Receipt Document. 8.26.1. Two sets of release/receipt documents, DD Forms 1348-1, are prepared as shown in Chapter 5, Part One, Volume I. Both sets are completed, showing all data needed in RP 1-80, item nomenclature (in block X), and weight, and cube. The second set of documents, if not already sent with the notice of availability, along with the number 5 copy of the first set and a copy of the bill of lading, are sent to the freight forwarder. These documents

act as advance information and are sent the same day, or not later than the next scheduled working day after shipments are made. 8.26.2. The preceding distribution procedures are applicable to the DD Form 1149, Requisition and Invoice/Shipping Document. 8.27. FMS Customer-Generated Requisitions. 8.27.1. General. FMS customer materiel requisitions are input into SAMIS. System edits/checks requisitions for proper codes, entries or combinations of entries, which allow routing, and processing of the requisitions. Requisitions that do not pass these edits are rejected as CEX errors. These errors, mechanically suspended by SAMIS, are manually researched and corrected by AFSAC personnel. Often requisitions are returned to the FMS customer for further action or are held awaiting more information from the FMS customer. The purpose of this paragraph is to give the FMS customer detailed instructions for making valid inputs for SAMIS processing. By following these instructions, errors are reduced and logistic support is improved for FMS customers. 8.27.2. Responsibilities by case type. 8.27.2.1. AFSAC personnel will input requisitions on follow-on cases for spares or equipment items. 8.27.2.2. The IMS/SPM will input requisitions on systems cases D, Q, S, and Y, as required. 8.27.2.3. AFSAC personnel will input requisitions for modification kits based on FMS customer's request. 8.27.2.4. The FMS customer will usually input requisitions on follow-on blanket-order cases, except Class IV/V mod cases. The FMS customer inputs requisitions on follow-on blanket-order cases: 8.27.2.4.1. Standard Equipment (E) Case. This type of case applies to standard equipment items that are expendability, recoverability, reparability category (ERRC) code S or U in the supply catalogs. 8.27.2.4.2. Nonstandard Equipment E__ Case. This type of case applies to nonstandard equipment items (ERRC S or U). A nonstandard item is an item that is not stocked, stored, or issued for Department of Defense (DoD) use. 8.27.2.4.3. Cooperative Logistics Supply Support Arrangement (CLSSA) Foreign Military Sales Order (FMSO) II Case. This type of case is for standard spares (ERRC other than S or U). 8.27.2.4.4. Standard Spares (R) Case. This type of case is for standard spares (ERRC other than S or U). 8.27.2.4.5. Nonstandard Spares (R___) Case. This type of case is for nonstandard spares (ERRC other than S or U). NOTE: Nonstandard items (support equipment/spares) are those items, with or without a national stock number (NSN), which the DoD does not manage for its own use, but are needed to support a system or end-item previously supplied on an Air Force FMS case. Nonstandard items cannot be supplied from stock or be obtained through normal acquisition. Procurement will be consolidated to the maximum extent practical. Requisitions should be held 90 days to accommodate multiple submissions and requests for small quantity buys that are strictly to support FMS. This does not apply to valid NMCS, other high priority requests, or requests for improved delivery schedule. Nonstandard items in support of a system or end-item furnished by another military service are requisitioned from and furnished by that service. If a nonstandard system or end-item is obtained commercially, the nonstandard equipment/spares to support it should also be obtained commercially (direct from the contractor). Exceptions to this policy must have approval from the Defense Security Cooperation Agency (DSCA). FMS customer requests for this type of FMS support are sent through channels to DSCA. 8.27.3. Restrictions. There are certain restrictions as to what type of items are requisitioned by the FMS customer on blanket-order cases. Unless otherwise specified these restrictions include: 8.27.3.1. All blanket-order (E, KB, R, and nonstandard E and R) cases: 8.27.3.1.1. Single-vender integrity or sole-source items are obtained on a defined-order case. 8.27.3.1.2. Classified items must usually move through the defense transportation system (DTS). 8.27.3.1.3. New and unused (advice code 6P) items are bought on a defined-order case or blanket-order case. NOTE: This rule does not apply to E cases. 8.27.3.1.4. Significant military equipment (SME) items are bought on a defined-order case. 8.27.3.1.5. Commercial-type items (Attachment 8C1) are bought through local (in-country) sources. If these items are not present locally and they are bought through FMS, use advice code 3B in RP 65-66 of the requisition. 8.27.3.1.6. Explosive ordnance items in Federal Stock Group (FSG), 13 are bought on a defined-order A or C (FSC 1377) case or a system sales case. 8.27.3.1.7. Excess defense articles are bought on a defined-order case.

8.27.3.1.8. Modification kits are usually shown by a K in the fifth position of the (NSN). Class IV mod kits are usually placed on a blanket-order V case, but they can also be placed on a defined-order V case. In both instances, the requisitions are input by AFSAC personnel. Class V mod kits are always placed on a defined-order Q, W, or Y case and requisitions are usually input by the IMS/SPM/AFSAC, not by the FMS customer. 8.27.3.1.9. Local manufacture (LM) or local purchase (LP) items are coded LM or LP in the supply catalogs. If these items cannot be locally purchased or manufactured and they are bought through FMS, use advice code 2A in RP 65-66 of the requisition. 8.27.3.1.10. Munitions/munitions related items with MMAC MN or AQ. These items are bought on a definedorder A, B, or C case or a system sales case. 8.27.3.1.11. Cryptologic/COMSEC equipment/items in FSC 5810 and 5811 and/or MMAC CA, CI, or CS are bought on a defined-order or blanket-order O case and selected system sales cases. 8.27.3.2. E Cases (standard equipment). All restrictions in paragraph 8.27.3.1 apply. In addition, the following restrictions apply: 8.27.3.2.1. Spares. Only equipment items with ERRC S or U are requisitioned on this type of case. Spares with ERRC other than S or U are requisitioned on a KB or R case. 8.27.3.2.2. Nonstandard Items. These type of items are usually MMAC coded XA XL, XT XV, ''XW, XX, ''XY, ''XZ, EX, or PU. These items are requisitioned on a nonstandard E (equipment) or R (spares) case or bought on a defined-order or system-sales case. 8.27.3.2.3. Advice code 6P (new and unused) is used if authorized in the LOA. 8.27.3.3. Nonstandard Equipment Case. All restrictions in paragraph 8.27.3.1 apply. In addition, the following restrictions apply: 8.27.3.3.1. Spares. Same as paragraph 8.27.3.2.1. 8.27.3.3.2. Standard Items. Standard equipment items (ERRC S or U) are requisitioned on an E___ case and standard spares on a KB__ or R__ case. 8.27.3.4. K___ (other than KA) CLSSA (FMSO II) Spares Case. All restrictions in paragraph 8.27.3.1 apply. In addition, the following restrictions apply: 8.27.3.4.1. Equipment Items (ERRC S or U). These items are requisitioned on an E standard or nonstandard case. 8.27.3.4.2. Nonstandard Items. Same as paragraph 8.27.3.2.2. 8.27.3.5. R Spare Case. All restrictions in paragraphs 8.27.3.1 and 8.27.3.3 apply. 8.27.3.6. RN Nonstandard Spares Case. All restrictions in paragraph 8.27.3.1 apply. In addition, the following restrictions apply: 8.27.3.6.1. Equipment Items. Same as paragraph 8.27.3.4.1. 8.27.3.6.2. Standard Items. Same as paragraph 8.27.3.3.2. 8.27.4. Research Products. 8.27.4.1. There are several microfiche products available to FMS customers. These products are useful when: 8.27.4.1.1. Converting LRNs to NSN(s). 8.27.4.1.2. Converting NSN to LRN. 8.27.4.1.3. Identifying/verifying LRN(s): 8.27.4.1.3.1. Name to code. 8.27.4.1.3.2. Code to name. 8.27.4.1.4. Obtaining supply management data: 8.27.4.1.4.1. Source of supply (SOS). 8.27.4.1.4.2. Unit of issue. 8.27.4.1.4.3. Quantity unit pack (QUP). 8.27.4.1.4.4. Substitute/interchangeable items using phrase codes. 8.27.4.1.4.5. Item name. 8.27.4.1.4.6. Other valuable data. 8.27.4.2. These products are used to find out what type of requisition (A01, A02, A04, or A05) is needed. Other data is used in the preparation of the requisition. For example, if an item has QUP of other than 0 to 1, the quantity (RP 25-29) ordered is in increments of the QUP. The unit of issue is checked to prevent rejection of requisition from the SOS.

8.27.4.3. The products we recommend using are in attachment 8C2. Estimated costs are used for budgetary purposes only. These products are bought on present blanket-order publication (P) cases for DoD supply catalogs, or they are requested on defined-order publication cases. 8.27.4.4. In addition, FMS customers can get management data from the Stock Number User Directory (D071) data system. Various types of management data are available to FMS customers based on stock number and type of data registration set up by the user. Details of this no-cost service are in AFMAN 23-110, Chapter 9, Part 1, Volume II. Customers wanting to join in the D071 data system will ask for authorization from HQ AFMC/LSO/LGIS. 8.27.5. Types of Requisitions. There are four types of requisition that a customer may input: 8.27.5.1. A01: 8.27.5.1.1. Use. If an item has a valid active NSN assigned, the A01 requisition should be used. Verify the NSN in the Management Listing Consolidated (ML-C). 8.27.5.1.2. Preparation (see attachment 8C4). 8.27.5.1.3. Transmission: 8.27.5.1.3.1. Usually by DMS or other available communications system. 8.27.5.1.3.2. Under unusual circumstances and when the priority warrants, a message is used. This method of transmission is held to a minimum. 8.27.5.2. A02: 8.27.5.2.1. Use. Use only if the item has a valid: 8.27.5.2.1.1. LRN. Verify in the FEDLOG that a valid NSN does not exist. 8.27.5.2.1.2. CAGE. Verify in the FEDLOG. 8.27.5.2.1.3. Technical Order (TO) Number Use only valid Air Force TO numbers. Take from TO NOTE: If one or more of the above is not available, use the A05. 8.27.5.2.2. Preparation. 8.27.5.2.3. Transmission. Same as paragraph 8.27.5.1.3.1. 8.27.5.3. A04: 8.27.5.3.1. Use. Use only for NC or ND (temporary stock number) (RP 12-13) items. AFSAC personnel can also use the A04 format when inputting Class IV mod kit requisitions on a V case. If the NC or ND number is not in the FEDLOG, use the A02 or A05 format. 8.27.5.3.2. Preparation (see attachment 8C4). 8.27.5.3.3. Transmission. Same as paragraph 8.27.5.1.3. 8.27.5.4. A05: 8.27.5.4.1. Use. Use for items which do not qualify for ''A01, ''A02, A04. 8.27.5.4.2. Preparation. 8.27.5.4.3. Transmission: 8.27.5.4.3.1. These requisitions cannot be sent through a communications network because of the added information required (i.e., TO, figure/index number, CAGE, etc.). 8.27.5.4.3.2. Usually, DD Forms 1348 with the added information are mailed to AFSAC. 8.27.5.4.3.3. Same as paragraph 8.27.5.1.3. NOTE: The added remarks section must have the system or end-item identity (type/model/series) on which the item is used. In the case of nonstandard items, the FMS customer gives the FMS case on which the nonstandard system or end-item was bought. 8.28. Hydrazine-Water (H-70) Support for F-16 Aircraft. 8.28.1. In the Air Force, missile fuels are managed by the Director of Energy Management, Detachment 3, WRALC/SF. A list of the fuels they manage is shown in AFMAN 23-110, Chapter 4, Part 3, Volume I. In the past, FMS demand has been limited to about three of the WR-ALC/SE managed fuels. The best known of these is hydrazine-water (H-70). WR-ALC/SE is not serviced by D035, so FMS requisitions for missile fuels must be established in SAMIS and then mailed to Detachment 3, WR-ALC/SFSC. WR-ALC/SES will fill the requisition and submit a bill. 8.28.2. H-70 (NSN 9135-01-049-9592) is a fuel used in the F-16. Due to a limited production schedule, FMS requirements are consolidated using a call letter. The H-70 call letter is published annually in order to: 8.28.2.1. Consolidate FMS customer requirements. 8.28.2.2. Identify empty H-70 drums the customer wants to return for refill.

8.28.2.3. Identify the customer's future requirements. 8.28.3. WR-ALC/SFS is the IMS for all hydrazine. In support of FMS H-70 requirements, WR-ALC/SFS: 8.28.3.1. Sends the estimated costs for H-70, H-70 drums, and contractor handling to AFSAC/GB by 1 March of each year for inclusion in the call letter, which is published by 1 April of each year. 8.28.3.2. Gets customers' requisitions (by mail) from AFSAC and fills the requisitions. 8.28.3.3. Gives approval/disapproval for return of empty H-70 drums to the AFSAC Command Country Manager. 8.28.3.4. Sends the ship-to address for return of empty H-70 drums to the AFSAC Command Country Manager. 8.28.3.5. Monitors the return of empty H-70 drums and tells the customer through AFSAC when empty H-70 drums are received or when H-70 drums are not received within 90 days of shipment from the FMS customer. 8.28.3.6. Makes sure requisitions are completely and accurately billed in a timely manner. 8.28.4. The AFSAC Command Country Manager: 8.28.4.1. Provides overall case management. 8.28.4.2. Gets the customer's requirements and provides the necessary information to AFSAC/COSC. AFSAC/COSC enters requisitions into SAMIS. The Command Country Manager mails this information to Detachment 3 WR-ALC/SFS by 1 June of each year. Detachment 3 WR-ALC/SFS is not serviced by D035. Because of the usually small requirement for H-70, blanket-order (K and R) cases may be used. 8.28.4.3. Tells the customer of the approval/disapproval to return empty H-70 drums and, if appropriate, the ship to address. 8.28.5. The FMS customer is responsible for: 8.28.5.1. Answering the call letter by 15 May of each year. Negative replies, when warranted, are necessary. 8.28.5.2. Preparing and shipping empty H-70 drums in accordance with TO 42B1-1-18 and any special instructions provided by AFSAC. 8.29. PROS Standard Item Policy. 8.29.1. Nonprogrammed non-H-coded requisitions. 8.29.1.1. The PROS contract incorporates supply and repair of standard items when the managing activity does not have organic capability or contractual support that meets the needs of the FMS customer. The item manager together with the Air Logistics Center (ALC) supply management team is best qualified to determine the appropriate course of action to fill a requisition. 8.29.1.2. Each facility may determine its own internal guidelines. These guidelines must ensure that each item meets PROS eligibility and that status has been checked to ensure there will be no duplication of support. 8.29.1.3. The item manager will provide the current AFMC Form 761, AMC/AMSC Screening Analysis Workshop, data package to the PROS ALC FMS focal point with the accompanying paperwork on all items affected by Operational Safety, Suitability, and Effectiveness. The focal point will retain copies of the coordination and approval form and mail the package to the PROS Program Management Office (PMO). Upon receipt of the technical data package, the PMO will validate the completeness of the information provided by the item manager. 8.29.1.4. No country approval is needed to pass a nonprogrammed standard item to PROS once the managing activity determines it to be the best source of supply. NOTE: Normal blocker edits still apply. 8.29.1.5. The vehicle for passing the standard item request between the Air Logistics Centers and the PROS PMO is the Security Assistance Management Information System Quick Access Identifier (SAMIS QAID) 427. 8.29.1.6. Procedures: 8.29.1.6.1. ALC as initiator: 8.29.1.6.1.1. ALC identifies candidate. 8.29.1.6.1.2. The item manager will obtain the appropriate supply management chain approval for passage to PROS. The Acquisition Method Code/Acquisition Method Suffix Code (AMC/AMSC) must be identified and formal coordination obtained from the single managers chief or lead engineer, who will determine if the 761 package is current and whether it should be forwarded with the requisition. 8.29.1.6.1.3. The item manager will forward the appropriate technical data package and the approved request form to the ALC focal point. 8.29.1.6.1.4. The ALC focal point inputs and sends SAMIS QAID 427 (request form) to PROS PMO electronically, and will forward the necessary technical data package by mail. 8.29.1.6.1.5. PMO reviews the 427 for completeness and requests Command Country Manager coordination if required. If the Command Country Manager agrees with the asset not being supported by the ALC, the Command

Country Manager will concur and return the package to the PMO to be forwarded to the PROS contractor. PMO releases the SAMIS-generated automated request for cancellation (AC). 8.29.1.6.1.6. Once AC_ transaction is released, SAMIS posts automated narrative. The appropriate response to the AC transaction is a BQ that will create a passing action (SAMIS converts the BQ to a CB) to the PROS contractor. NOTE: Normal blocker edits still apply. 8.29.1.6.1.7. If disapproved or if the Command Country Manager wants the asset supported by the ALC, the Command Country Manager will non-concur and return the package to the PMO for action. The PMO will then delete the AC transaction in SAMIS to allow the ALC to continue fill actions on the existing requisition. A narrative will then be posted in SAMIS and an e-mail sent to the ALC focal point. 8.29.1.6.2. AFSAC Command Country Manager as initiator: 8.29.1.6.2.1. Identifies candidate, after obtaining appropriate ALC concurrence/approval, to the PMO via e-mail.. 8.29.1.6.2.2. PMO forwards e-mail to the appropriate ALC focal point and initiates 427 in SAMIS. 8.29.1.6.2.3. Item manager will obtain the appropriate coordination with the single managers chief or lead engineer and determine if the 761 package is current and required for the requisition based on the AMC/AMSC code. 8.29.1.6.2.4. Focal point will provide the item managers 761 technical data package to the PMO by mail. The PMO will forward the technical package to the PROS contractor. 8.29.1.5.6.5. PMO releases SAMIS generated automated AC_ transaction from QAID 514. 8.29.1.5.6.6. Once AC_ transaction is released, SAMIS posts automated narrative. 8.29.1.7. Although these steps are not necessarily all-inclusive, and may vary from focal point office to focal point office, they do illustrate the processes and the people who should be involved in them. 8.29.2. Programmed and Repair-and-Replace (H-Coded) Requisitions. 8.29.2.1. For FMS programmed and H-Coded requisitions, AFMC and DLA have committed to provide more timely support using on-hand and on-order stocks and via the MISTR repair process. Every effort must be taken to honor this commitment and provide timely support for these requisitions. 8.29.2.2. Policy: It is recognized that there will occasionally be supply support problems that prevent the timely support of FMS programmed and H-Coded requisitions. These problem requisitions should be identified as PROS candidates. Country review and approval of PROS candidates is necessary prior to forwarding to the PROS contractor. This approval is necessary because we are changing the method of support. We are changing from support using on-hand/on-order stocks to support lead-time away. We are changing the method of maintenance from repair and replace at average repair cost to repair and return at actual repair cost. 8.29.2.3. Identification Process: 8.29.2.3.1. The ALC FMS Focal Points will identify Programmed and H-Coded PROS candidate requisitions to the AFSAC case manager via the normal communication channels. 8.29.2.3.2 To aid in making the decision on whether or not to send the FMS Programmed or H-Coded requisition to PROS, the ALCs are requested to provide the following information when identifying PROS candidates: Document number, quantity, NSN, case and line, SC, SPC, IGWD, ESD, and CAC. 8.29.2.4. Data transmission codes: To aid in the transmission of the above data the following codes should be used: 8.29.2.4.1. Situation code (SC). What is the current support status for the item? 8.29.2.4.1.1. Critical Support Problem: Support of this item by the ALC is not possible. PROS support is the only FMS option. Removing this item from the CLSSA program is recommended. 8.29.2.4.1.2. Lead-time Support Problem: Supply support problems prevent timely support of this requisition. Support of this item within the procurement lead-time, or within 1 year of H-coded requisitions, is currently not possible. PROS support is recommended. Normal support for the item will resume when the supply support problem is resolved see the Item Get-Well Date and the requisition ESD. 8.29.2.4.1.3. Short Term Support Problem: Support is available, but most likely will be delayed. To improve the timeliness of support, PROS should be considered. The short term support problem will be fixed and normal ALC support is expected to resume in the future see Item Get Well Date. Limited support of individual requisitions will occur as assets become available see ESD. 8.29.2.4.2. Support problem codes (SPC). Why cant the requisition be filled in a timely manner? 8.29.2.4.2.1. Unusually high demand. 8.29.2.4.2.2. First Article Testing problems.

8.29.2.4.2.3. Contractor poor performance. 8.29.2.4.2.4. Procurement contract award problems. 8.29.2.4.2.5. Repair contract award problems. 8.29.2.4.2.6. Insufficient carcasses for repair. 8.29.2.4.2.7. No bit- and piece-parts for repair. 8.29.2.4.2.8. Other specify. 8.29.2.4.3. Item get-well-date (IGWD). Month/Year, or U for unknown. 8.29.2.4.4. Estimated ship date (ESD) of the requisition. Month/Year, or U for unknown. 8.29.2.4.5. Carcass availability code (CAC). For use with H-coded requisitions. 8.29.2.4.5.1. Countrys item carcass is identifiable and available for shipment to the PROS contractor. 8.29.2.4.5.2. Countrys item carcass is not identifiable, and an available carcass will be shipped to the PROS contractor. 8.29.2.5. Customer Approval Process: The AFSAC case manager will provide the PROS candidate items to the appropriate country personnel and request a decision as to whether to send the requisition to PROS or to leave it with the AFMC SOS. If the customer rejects support via PROS, the case manger will send a courtesy notification to the ALC FMS Focal Point Office. 8.29.2.6. PROS PMO Notification: 8.29.2.6.1. Programmed Non H-coded Requisition Processing: For programmed non H-coded requisitions approved for PROS by the customer, the AFSAC CM will identify the candidate item to the PROS PMO via email. Procedures identified in paragraph 8.29.1.5.2. apply. Programmed Non H-coded requisitions redirected to PROS will be supported by contractual action with asset delivery normally lead-time away. 8.29.2.6.2. H-coded Requisition Processing. For H-coded requisitions approved by the customer for PROS, the AFSAC case manager will provide the PROS PMO a copy of the ALC recommendation for PROS support along with a written statement of approval from the country or case manager. The H-coded requisition will then be canceled by the source of supply and the unserviceable carcass shipped to PROS. Maintenance is accomplished by repair and return. 8.29.3. AMARC Non-standard Requisition Process. 8.29.3.1. The following is a summary of the procedures adopted for nonstandard assets (they are built around the procedures for standard asset removal). 8.29.3.2. When the PROS contractor has determined a nonstandard part is not readily available on the commercial market, and possibly is available at AMARC, he will send a request for information form (see attachment 8C9) to the applicable SPD. The applicable SPD will determine if they are in a position to use the AMARC asset to fill their requisition. If the SPD agrees, they will forward the request to AMARC who will reply to the PROS contractor with info to the SPD. 8.29.3.3. If the item is available, the PROS contractor will provide pertinent information to the FMS customer for the country to decide if it wants an Air Force asset from AMARC. The PROS contractor will advise the country that the SPD has reason to believe the asset is at AMARC, that a reasonable number of aircraft/locations will be searched for the item, and that it is not possible to guarantee beforehand that the item will be located and/or in the condition code desired. If the country specifies that the item must be serviceable (condition code A), the requisition will be killed if a reasonable number of searches fail to result in a serviceable asset, or any asset. If the country is willing to accept an asset in either unknown (condition code R) or unserviceable (condition code F) and assume cost of inspection/repair, the Air Force will forward the unknown/unserviceable item to the PROS contractor for inspection/repair. An estimate or ROM projection of costs for inspection/repair will be provided to the country by the PROS contractor at the time it advises the country of the possible availability of assets at AMARC. 8.29.3.4. If the country agrees to use AMARC, the AFSAC PROS program manager will modify and forward the requisition to the applicable SPD, who will then forward the requirement to AMARC. AMARC will then attempt to acquire the asset and ship it in accordance with the instructions of the request. If the item is determined by AMARC to be either reparable (condition code F) or of unknown condition (code R), the asset will be shipped to the PROS contractor to be repaired on a second requisition number that will have been provided to the contractor by a COR action initiated by the AFSAC PROS office. A flow diagram of this process is provided in attachment 8C10.

8.29.3.5. The pricing of the assets will be in accordance with current policies and regulations at the time as contained in DoD Financial Management Regulation (DoD) 7000.14-R, Financial Management Regulation, Vol. 15, Security Assistance Policy and Procedures. 8.30. Thru 8.33. (Unused.) Section 8DCOMMITMENTS 8.34. Bulk Commitments. 8.34.1. Purpose and Scope. The purpose of the bulk commitment transaction is to control case funds at the case/line item level. Bulk commitments are used only on a limited basis for nonrequisition cases when it is not practical to use custom commitments. Bulk commitments do not provide sufficient tracking of status and deliveries against cases/line items. 8.34.2. Establishment. When a Letter of Offer and Acceptance (LOA) is countersigned/coordinated by Defense Security Cooperation Agency and returned to the Air Force Security Assistance Center (AFSAC), it must be sent to the customer for signature, and the case must be established in SAMIS. SAF-negotiated case/line items are established in SAMIS upon receipt of the courtesy copy. Additional information can be found in the SAMIS help screen that explains the data elements and bulk commitment transaction. 8.34.3. Processing. The AFSAC case manager processes bulk commitments through the SAMIS terminal using the quick access identification (QAID) COM. 8.34.4. Updating Bulk Commitments. Committed values will be updated by entering transactions with the available bulk commitment codes. These transactions determine if the case/line item committed values increase or decrease. SAMIS maintains a history of all document identifier COM transactions. 8.35. Custom Commitments. 8.35.1. Custom Commitment (C05). Custom commitments allow definitization and commitment of funds for nonrequisition-type requirements on a case/line item. The document identifier C05 denotes a custom commitment. In addition, an open custom commitment master record is established and updated with custom commitment status, custom commitment shipment status, and deliveries. Committed value on case/line items having type commitment code C can only be updated using custom commitment action. In special situations (for example, Air Force technical orders) it may be necessary to use custom commitments against case/line items having a type commitment code R. 8.35.2. Custom Commitment Status (CE5). Custom commitment status (CE5) transactions update information on the open C05. The CE5 transaction allows updates to routing identifier and reporting activity codes, AF appropriations, quantities, commitment descriptions, control reasons, control dates, and total-committed value. 8.35.3. Custom Commitment Shipment Status (CS5). Custom commitment shipment status (CS5) transactions update information on the shipment of materiel requirements shown by the open C05. 8.35.4. Freight Forwarder Transactions (XDA and XDB). Freight forwarder transactions (XDA and XDB) give the customer information about the status of the items on the custom commitment. The XDA transaction tells the customer the Air Force has received the items and gives the customer an estimated shipping date. The XDB transaction tells the customer the Air Force is shipping the item back. These transactions will usually be used for repair/return items. 8.35.5. Establish Open Custom Commitment. Open custom commitments are established by a custom commitment (C05) transaction. You should use bypass code R if reopening a completed C05. All C-5 transactions are input using an interactive remote display station. The input screen QAID is CC. When a C05 transaction is entered, SAMIS will do a series of cursory edits on form and content. When filling the routing identifier code (RIC) use the RIC of the activity responsible for performing the service of the custom commitment. When filling the reporting activity code (RAC), use the RAC of the activity responsible for billing the custom commitment. If you need a freight forwarder transaction (XDA) enter a Y on the question line. The remaining elements on the input screen will then be edited by SAMIS. ELEMENT EDIT ESTIMATED SHIPPING DATE MUST BE VALID JULIAN DATE REPAIR SOURCE CODE MUST BE A, C, F, G, H, L, or P (See attachment E-49, chapter 15).

Screen elements not given above have no on-screen edits. When all edits are passed, the C05 transaction will be staged as SAMIS input to be processed during the daily batch cycle. This is also true of the XDA transactions when requested. 8.35.6. Updates to Open C05. Updates to an open C05 are done with CES, CS5, and delivery transactions. All CES and CS5 transactions are input using an interactive remote display station. The input screen QAID is CCST. The first screen has two elements: document identifier and document number. Enter on this screen either CE5 or CS5 and an open C05 document number. The second screen is the CES or CS5 transaction input screen. Screen elements filled from the open C05 data elements are: routing identifier code, reporting activity code, AF appropriation code, quantity, document number, supplementary address, LOA line item code, commitment description, and project code. These elements will be referred to as the filled elements. When a CES or CS5 transaction is entered, SAMIS will do a series of cursory edits on form and content. 8.35.6.1. For CE5 transactions, the edits are based on the CE5 transaction status code. See chapter 15 for a list of status codes and their explanations. 8.35.6.1.1. For status code MA, the only filled element that may be changed is quantity. All other filled elements must stay the same for the transaction to be staged into SAMIS. 8.35.6.1.2. For status codes MC and MZ the only filled elements that may be changed are quantity and commitment description. For status MC, the total committed value must be greater than the remaining committed value. For status MZ, the total committed value must be less than the remaining committed value. Status code MZ with a total committed value of zero will complete the open C05. 8.35.6.1.3. For status code MH, the filled elements that may be changed are routing identifier, reporting activity, and AF appropriation codes, and the commitment description. 8.35.6.1.4. For status codes M1 through M6, only control reason and control date may be changed. Control reasons are used by the user to provide internal messages to the user. Control reason 6 is the commitmentdescription-continued field and provides information to the billing office. Control dates may be used to have SAMIS produce a follow-up notice for the user. This notice will be produced when the control date is reached. To delete a control-reason and date, the status code modifier (*) must be entered. 8.35.6.2. If you need a freight forwarder transaction (XDA), enter a Y on the question line. The remaining elements on the input screen will then be edited by SAMIS. ELEMENT ESTIMATED SHIPPING DATE REPAIR SOURCE CODE EDIT MUST BE VALID JULIAN DATE MUST BE A, C, F, G, H, L, or P

Screen elements not given above have no on-screen edits. When all edits are passed, the CES transaction will be staged as SAMIS input to be processed during the daily batch cycle. This is also true of the XDA transaction. 8.35.6.3. For a CS5 transaction none of the filled elements may be changed except quantity. SAMIS automatically stages XDB transactions when a CS5 transaction is staged. The unfilled elements are edited as follows: ELEMENT SUFFIX CODE TRANSPORTATION BILL CODE DATE SHIPPED MODE OF SHIPMENT REPAIR SOURCE CODE EDIT MUST BE ALPHA/NUMERIC OR BLANK MUST BE A THROUGH H, J THROUGH N, P THROUGH S, U, V, X, Y, OR BLANK MUST BE VALID JULIAN DATE MUST BE A THROUGH Z, 2 THROUGH 9, OR BLANK MUST BE A, C, F, G, H, L, or P

8.35.6.4. Delivery transactions update the delivered dollar value and committed value on an open C05 by the dollar value of the delivery record. There will be no controlled exceptions due to unit of issue or quantity variances. A delivery record will not update the quantity on an open C05. If the dollar value of the delivery record exceeds the committed value, the open C05 will be completed.

8.35.7. Reopen a Completed C05. If a C05 is completed and additional deliveries are anticipated, the C05 should be reopened. To do this, reinput the C05, use bypass code R, and commit the dollar amount of the anticipated deliveries. 8.35.8. Interrogation of Open C05. To interrogate for an open C05, use QAID 168. This interrogation gives a list of all open CO5s. Interrogation can be by Routing Identifier Code (RIC) or Routing Activity Code (RAC). SAMIS also produces a weekly list of open CO5s by RAC. Each RIC will receive a list of their open CO5s. The product control number for this weekly product is U-WOO1.-HDR. The billing offices should use this product to determine the document number to use when delivery reporting custom commitments. 8.36. Thru 8.40. (Unused.) Section 8EAIR FORCE MATERIEL COMMAND (AFMC) SYSTEM SALES 8.41. Communication/Electronic (CE) Systems and Equipment D Case Processing. 8.41.1. A preliminary technical survey report (PTSR) and/or an engineering requirement plan (ERP) may be required for CE sales before making up price and availability LOA data. The PTSR consists of a requirement statement, an operational concept, a statement of the customer's capabilities, and other supporting information. The ERP is more detailed than the PTSR. The security assistance office and the FMS customer make up both of these documents, with help from the Air Force as necessary. This information comes from the site survey. 8.41.2. The Air Force Security Assistance Center (AFSAC) will: 8.41.2.1. Process request for P&A data from the FMS customer in anticipation of a buy of CE materiel or services. 8.41.2.2. Review request from the FMS customer for P&A data. 8.41.2.3. Send P&A request to the Air Logistics Center (ALC/LP) FMS focal point (informational copy to the system program manager (SPM)) and include a request for general availability and potential impact statements. 8.41.2.4. Obtain P&A data from the international logistics program (ILP) focal point. The AFSAC will review it for accuracy and completeness and send it to the FMS customer. 8.41.2.5. Obtain the request for Letter of Offer and Acceptance (LOA) data (LOAD) from the FMS customer and send the request to the ALC/LP focal point (informational copy to the SPM); to SMC/CZUF for Global Positioning Systems; to the Air Force Materiel Command transportation office for Department of Defense (DoD) transportation services; to AGMC for calibration services and calibration and repair of precision measurement equipment (PME) equipment; and to the ALC propulsion directorate for technical orders. 8.41.2.6. Contact AFSAC/IAS for Security Assistance Program Manager (SAPM) assignment if necessary. 8.41.2.7. Obtain a project name and code, if necessary. 8.41.2.8. Obtain and review LOAD. Data usually includes: 8.41.2.8.1. Any support required for computer hardware or software. 8.41.2.8.2. Special requirements (long lead-time, sole-source acquisition, single-vendor integrity, Air Force supply directive (AFSD), etc.). 8.41.2.8.3. Estimated cost, implementing agency, availability and lead time, generic code, and military articles and services list line number for each requested line item or substitute item. The base cost is given along with any additives for safety and inflation factors. For items coming from stock, the ALC must show one of the following inventory sources: 8.41.2.8.3.1. Excess inventory. 8.41.2.8.3.2. Inventory (without replacement). 8.41.2.8.3.3. Inventory (replacement with same item). 8.41.2.8.3.4. Inventory (replacement with improved item). 8.41.2.8.4. Cost elements, consisting of: 8.41.2.8.4.1. Nonrecurring research, development, test, and evaluation, and production charges. 8.41.2.8.4.2. Asset-use charges. 8.41.2.8.4.3. Contract audit services. 8.41.2.8.4.4. Government-furnished equipment and materiel. 8.41.2.8.4.5. Government-furnished technical documentation. 8.41.2.8.4.6. Government-furnished transportation (specify mode) including first destination transportation charges when aggregating. 8.41.2.8.4.7. Estimated costs for an initial cooperative logistics supply support arrangement, or a major additive. 8.41.2.8.4.8. Statement that the materiel being priced has been reviewed and has been determined releasable by the local Foreign Disclosure Office.

8.41.2.8.5. A list of items and services that are standard to the DoD inventory, but nonstandard to the Air Force; a list of items and services that are nonstandard to the DoD inventory; and a list of long-lead-time items. 8.41.2.8.6. A list of items and services not included in the request but considered essential or desired. 8.41.2.8.7. A statement of applicable agents fees by the name of the firm and the amount. If the contractor plans to ask for reimbursement, make sure SF 119, Statement of Contingent or Other Fees, documentation is prepared. This documentation is part of the LOAD package, along with the contracting officer's recommendations as to whether all or part of each fee is proper under the Federal Acquisition Regulation. 8.41.2.8.8. Costs for a management case to include travel, per diem, salaries, etc., associated directly with the system sales program. If a manpower line is cited on the LOAD, then an MRP, signed and approved by the local manpower office, must be provided AFSAC at the time the LOAD is provided (or shortly thereafter). 8.41.2.9. Obtain inputs from the various sources prepare the LOA for negotiation with the FMS customer. AFSAC will ensure proper coordination in accordance with local instructions. 8.41.2.10. Ensure implementation of the case occurs in a timely manner. 8.41.2.11. Make up an international program directive (IPD) in accordance with local instructions. The AFSAC will send the IPD to the ALC ILP focal point (informational copy to the SPM), and to the other organizations involved, including HQ AFMC transportation office for transportation services (do the same for amendments). 8.41.2.12. Take part in the site survey if necessary. The AFSAC will make sure maintenance concepts are developed for each system or subsystem and support equipment. 8.41.2.13. Take part in sales negotiations with the FMS customer. NOTE: LOA negotiators should not discuss program requirements which are not part of the LOA, even if these added requirements are part of or derived from the program being discussed. Such added requirements are presented to the US government through channels and discussion of them is put off until then. 8.41.2.14. Maintain surveillance over the financial and logistical condition of the case throughout the performance of the case. 8.41.2.15. Take part in configuration/definitization/provisioning conferences chaired by the SPD or SAF/IA. The SPD, FMS customer, and inventory manager list concurrent support requirements for HQ AFMC. The AFSAC helps in making up an FMS customers integrated logistics support plan. 8.41.2.16. Obtain a copy of the final definitized listings from the SPM and will make sure that proper shipping addresses are in the Military Assistance Program Address Directory (MAPAD). 8.41.2.17. Make sure all requisitions are input to the (SAMIS for supply action. AFSAC will send copies of the A41 requisition referral listings to the SPM. 8.41.2.18. Serve as the focal point for case management. AFSAC will maintain surveillance over the performance of the case and notify the customer of requirements to modify or amend as required, and will make sure that all materiel is shipped, services performed, and billing completed. 8.41.2.19. Request notice of supply/service completion reports be issued by the SPM when all materiel and services have been shipped or completed. 8.41.2.20. Make sure all cancelled requisitions are identified to the SPM to ensure that re-requisitioning can be done, if necessary. 8.41.3. The ALC FMS focal point will: 8.41.3.1. Obtain P&A or LOAD requests from the AFSAC case manager and send it to the proper SPM or endarticle IMS. 8.41.3.2. Obtain P&A data or LOAD from the SPM or end-article IMS, review it for completeness, and send it to the AFSAC case manager. 8.41.3.3. Obtain LOAD request from Defense Security Assistance Management System (DSAMS) and send it to the SPM or end-article IMS. 8.41.3.4. Obtain LOAD from the SPM or end-article IMS, and renew and send it to the AFSAC case manager. 8.41.3.5. Obtain the IPD from the AFSAC case manager, add instructions as needed, and send it to the SPM or end-article IMS. 8.41.3.6. Serve as the liaison office for AFSAC case managers and the SPM or end-article IMS divisions. 8.41.3.7. Make special procedures as necessary. NOTE: The procedures in Chapter 2, Part 3, Volume 3, apply to SPM actions. 8.41.4. The ALC will:

8.41.4.1. The SPM will check with the ASC system program office to get a general availability statement and a statement of likely impact on Air Force and other FMS programs. The SPM will show any added information the FMS customer must give to allow for the establishment of a P&A or LOAD package. 8.41.4.2. Send the completed P&A or LOAD package to the ILP focal point. The P&A data or LOAD is based on the type of system used, source of supply, system complexity, FMS customer mission requirements, and methods of support. P&A data or LOAD is not suitable for inclusion in an LOA. Standard factors are used (such as a percentage of the system cost for an initial spares estimate). Contractor price and delivery estimates are not necessary. 8.41.4.3. Get the P&A or LOAD request from the ILP focal point and check with the System Program Office (SPO) when creating pricing data. The SPM will check with AGMC when forming the FMS customers PMEL requirements and will check with the ALC manpower evaluation team when forming added manpower requirements (such as task teams, in-country program manager, Weapon System Logistics Officers (WSLO), etc.). The SPM will check with OC-ALC/LP when setting up the first TO requirements and make sure of releasability to the customer through the applicable Foreign Disclosure Policy Office (FDPO). 8.41.4.4. After obtaining a releasability statement from the local FDPO, give completed P&A or LOAD package to the ILP focal point, who will send it to the AFSAC case manager. 8.41.4.5. Take part in the site survey and, as necessary, in the sales negotiations. 8.41.4.6. Schedule, arrange, and chair configuration/definitization/provisioning conferences, ensuring that all required documentation (initial spares support list, provisioning parts breakdown, replenishment spare parts list, etc.) is available for the definitization conference. The SPM will give the AFSAC case manager a copy of the final definitized listing of items, prepare the minutes, and follow up on action items. 8.41.4.7. Take the lead in making the AFMC part of the system support plan. 8.41.4.8. Decide required availability dates (RAD) based on the system activation dates. 8.41.4.9. Apply any special requisition procedures shown in the LOA and international program directive (such as AFSD, sole-source, single-vendor integrity, new and unused, etc.). The SPM will check with all proper organizations. 8.41.4.10. Requisition all required items and stop requisition input 90 days after the delivery of the last system. 8.41.4.11. Work with OC-ALC/LP to give initial lay-in of technical publications to the FMS customer, including Time Compliance Technical Order (TCTO) distribution. The SPM will give a list of all publications to the customer and the AFSAC case manager. 8.41.4.12. Check on program review dates proposed by the AFSAC case manager, and prepare all system- and item-related data for program renewal. 8.41.4.13. Maintain overall surveillance of IMS actions necessary to support the system delivery and activation dates, including workarounds if RADs cannot be met. 8.41.4.14. Issue notice of supply and service completion (NSSC) report when all materiel has shipped or services performed. NOTE: When there is not an SPM, the IMS division assumes the responsibilities shown below: 8.41.5. The ALC will: 8.41.5.1. Receive, review, and process all applicable requisitions in a timely manner. 8.41.5.2. Get RAD reports and start necessary actions to meet the RAD, or justify the reason for delivery slippage. 8.42. Weapon Systems S Case Processing. 8.42.1. The procedures in paragraph 8.41 on D cases apply to S cases. The following information also applies: 8.42.1.1. S cases are for the sale of aircraft systems, from either new production or inventory. This includes the aircraft, spare engines, spare parts, support equipment, services, delivery, and training. 8.42.1.2. The AFSAC case manager must ask for LOAD from ASC/LP for in-production engines, from OCALC/LP through OC-ALC/LGMRC for other engines, from OO-ALC/LP for cartridge actuated devices and propellant actuated devices (CAD/PAD) requirements, and from HQ AFMC transportation office for C-5/C-141 airlift or surface delivery of aircraft. 8.42.1.3. The AFSAC case manager must ensure inclusion of costs associated for participating in the applicable component improvement program (CIP) on new production sales (or International Engine Management Program (IEMP) on sales from inventory), the aircraft structural integrity program (ASIP), and the technical coordinating group (TCG).

8.43. Selected Systems Y Case Processing. 8.43.1. The procedures in paragraph 8.41 on D cases apply to Y cases. The following additional information also applies: 8.43.1.1. Y cases are for the sale of systems on other than D and S cases. Included in these type of cases are missiles, pods, special-purpose vehicles, and complex technical assistance programs. 8.43.1.2. When there is no SPM, the IMS division assumes the SPM responsibilities. 8.43.1.3. Not all Y cases require a site survey or the development of an ILSP. Contact the Command Country Manager for direction. 8.44. Selected Systems Q Case Processing. 8.44.1. The procedures in paragraph 8.41 on D cases apply to Q cases. The following information also applies: 8.44.1.1. Q cases are for the sale of systems other than those sold under D, S, and Y cases. AFSAC negotiates these cases including all supporting materiel and services. 8.44.1.2. Most Q cases do not need a site survey or the development of an ILSP. Contact the Command Country Manager for direction. 8.44.1.3. AFSAC negotiates other package sales that combine different AFSAC-negotiated cases on a single LOA, when the cases are related to a single program. These package sales are negotiated in accordance with guidelines for the individual cases. For example, an LOA, which includes a blanket-order equipment case, a line item for a blanket-order spare parts case, a line item for services, repair/return, etc. 8.45. Air Force Inventory Systems - Aircraft. 8.45.1. When aircraft are sold, leased, or loaned out of Air Force inventory, the shelf/service life remaining on installed (CAD/PAD) items must be considered. The LOA should include a separate dollar line to cover CAD/PAD replacement support for the first 36 months of ownership. The SPM checks with OO-ALC/LIW as the AFMC office of primary responsibility (OPR) for CAD/PAD items. OO-ALC/LIW determines the replacement status of installed CAD/PAD items based on install dates and current production lead times. Items needing replacement, before their availability from production, are added as unprogrammed requirements on the next CAD/PAD buy. Early awareness increases OO-ALCs capability to get assets from inventory or existing production where possible. 8.45.2. Determining the condition of aircraft and installed items is according to AFR 400-6. 8.46. Thru 8.50. (Unused.) Section 8FFMS CASES OTHER THAN D, Q, S, and Y. 8.51. General. 8.51.1. These cases provide follow-on support for FMS customers. A brief description of the purpose of each case is given for both blanket-order and defined-order cases. See attachment 8F2 for additional guidance. 8.51.2. The case manager is both logistically and financially responsible for his/her cases. Each case is reviewed on a periodic basis. This helps prevent reconciliation problems at case closure. All correspondence should reference case designator and document number. 8.52. A CasesDefined-Order (D/O) Cases for Munitions. 8.52.1. Munitions, including conventional munitions. 8.52.2. Air Force policy on munitions issues from stock is: 8.52.2.1. If a munitions item on-hand exceeds the inventory objective, the excess is releasable. The inventory objective is the planned war reserve materiel (WRM) requirement as determined by the nonnuclear consumables annual analysis, and defense guidance, plus peacetime objective requirements. 8.52.2.2. If the on-hand level of an item is below the inventory objective but above the procurement objective, HQ USAF concurrence is necessary before release for FMS. The procurement objective is the level of items wanted within the fiscal year's available dollars. All these objectives are determined at HQ USAF level or higher. 8.52.2.3. If on hand stocks of a munitions item are below the procurement level, or are being used to compensate for shortages or other munitions below the procurement level, routine sales from stock are denied. 8.52.2.4. Air Force or Office of the Secretary of Defense (OSD) officials consider exceptions to this policy for high priority security assistance (SA) programs that are in the national interest. 8.52.3. The single manager for conventional ammunition (SMCA) buys most of the munitions received from procurement. 8.52.3.1. SAF/IA LOAD requests are sent to the Ogden Air Logistics Center (OO-ALC).

8.52.3.2. OO-ALC refers only items needing procurement to the SMCA for LOAD action. OO-ALC will inform the US Army Armament, Munitions, and Chemical Command (AMCCOM) by telephone and confirm the conversation with a message or a letter. If the information is not needed, OO-ALC will also inform AMCCOM so any action started for the development of LOAD is stopped. A request to the SMCA is not necessary if available data is less than 91 days old (based on the date of the document); and the requested quantity does not vary from the old by 15 percent. 8.52.3.3. When the SMCA gets new requests for LOAD data, the SMCA sends the requests directly to the Deputy Under Secretary of the Air Force for International Affairs (SAF/IA) with an informational copy to AFSAC and OO-ALC. If delays in issuing the data exceed thirty days, the notification procedure is in the preceding paragraph. 8.52.3.4. When the LOAD request does not involve the SMCA, but contracting is necessary, a quote is not required for each request. If the latest contract price or contractor's estimate is less than five years old, and the quantity of the new request is within 15 percent of the estimate already available, then the available data is used (include appropriate escalation factors). Each LOAD request must have all information necessary to complete a financial analysis worksheet. Financial analysis worksheets are in attachments F-1 through F-3. 8.52.3.5. If a lengthy delay in getting LOAD for particular items is expected, the customer is asked to resubmit the requirement separately. The item is added later as an amendment. 8.52.3.6. Any LOAD requirement for transportation of munitions will be coordinated with AFMC/DRR and AFMC/LGT before sending the data to SAF/IA. 8.52.4. There are additional guidelines for the sale and repair of nuclear-related munition assets (formerly known as nuclear ordnance commodity managed (NOCM) material). These items are identified with materielmanagement-aggregation code CM, or Federal Supply Group II. 8.52.4.1. When nuclear-related munition assets items are part of an initial sale, the request is coordinated with both AFMC/DRR and OO-ALC/WM. 8.52.4.2. All follow-on sales of nuclear-related munition assets materiel are A cases. This action allows for the same control provided for nonnuclear munitions sales cases. 8.52.4.3. Repair procedures for nuclear-related munition assets materiel are in chapter 14. 8.52.5. Explosive ordnance disposal (EOD), technical orders (TO), and EOD storage TOs needed are identified in the LOR. Requests for EOD TOs are sent to SAF/IAPX for release authority. 8.53. B CasesReserved. B cases were formerly defined-order (D/O) cases for spare parts. These cases are no longer written and the B designation is now reserved. 8.54. C CasesBlanket-Order (B/O) Cases for Cartridge Actuated Devices/Propellant Actuated Devices (CAD/PAD). CAD/PAD items are subject to specific shelf or service life and it is not economically possible for the Air Force to buy these items except on a phased procurement basis. To support this at an acceptable economic level, the Air Force usually buys CAD/PAD items once each year using annual requirements computations. Out-ofcycle requirements are placed on procurement by OO-ALC on an as-required basis. Customer requirements made outside the annual buy program are subject to increased prices and extended delivery lead times. 8.54.1. In the first week of July, OO-ALC/WMJ drafts an annual CAD/PAD call letter and sends it to AFSAC. The draft call letter includes the following: 8.54.1.1. Time constraints for processing CAD/PAD cases from the start of the call letter through the LOAD process, case acceptance, implementation, and contract negotiations for the Air Force annual buy program. 8.54.1.2. An attached list of CAD/PAD items by aircraft with national stock number, noun, logistics reference number (LRN) current shelf/service life, lead-time, quantity per aircraft, etc. 8.54.2. After getting the draft call letter, AFSAC completes and sends it to the FMS customer. The final version of the letter gives specific timeframes in which the FMS customers must respond with a Letter of Request (LOR) for their requirements to be considered in the annual buy. 8.54.3. When an LOR is received, AFSAC asks for LOAD from OO-ALC. The LOAD request identifies the FMS customer's requirement as an emergency, when appropriate. OO-ALC prepares the LOAD study and identifies the class of explosive, whether the item is exempt or inert, and if shelf/service life (when applicable). The LOAD is given in a format good enough for the AFSAC case manager to perform a financial analysis (when applicable). This analysis includes identifying the last procurement price and the inflation factors used to develop the price. OO-ALC/LIW gives the LOAD to AFSAC for preparation of an LOA to send to the customer.

8.54.4. The LOA resulting from the customer's response to the call letter may include a separate line item for nondefinitized emergency requirements (see para 8.54.1.2). If the customer accepts the LOA, AFSAC prepares a implementing program directive (IPD) after receiving obligation authority. 8.54.5. AFSAC inputs requisitions into SAMIS for subsequent referral to D034 (see section C). 8.54.6. The terms of delivery of the LOA must have, as a minimum, a statement that sensitive and hazardous materiel are delivered FOB vessel/aircraft, CONUS port of exit, under the conditions of delivery term code (DTC) 8, which must have an offer/release code (ORC) Z. Special transportation conditions or procedures, if required, are defined in the LOA. 8.55. E CasesBlanket-Order (B/O) Cases for Support Equipment and Supplies. 8.55.1. E cases are used to buy items such as support equipment, vehicles, tools, shop equipment, test equipment, and similar supply items of US origin that are frequently used by the customer. Equipment items have an S or U expendability, recoverability, reparability category (ERRC) code. The B/O case sets up a value for buying items until funds are exhausted. The FMS country will submit a LOR signed by the appropriate signature level to AFSAC/CM. The LOR will state the type of equipment and dollar value of the proposed case if the customer desires. AFSAC will input and control the requisition for these items if the FMS country desires. 8.55.2. For case-funded equipment, the organization for which the equipment was purchased is responsible for the protection and accountability of the equipment. The equipment should be inventoried annually by the using organization. At the end of the program, the case-funded equipment should be offered to the customer. If the customer does not want the equipment, it may continue to be used in support of other security assistance programs; turned into the local disposal office and processed as abandoned, excess, or surplus equipment; or turned into the Worldwide Warehouse Redistribution Service (WWRS), managed by AFSAC, for resale. 8.56. F CasesReserved. F cases were formerly used for training films, filmstrips, and other audiovisual media. These products are provided on P cases and the F designation is now reserved. 8.57. G CasesDefined-Order (D/O) or B/O Services Cases. 8.57.1. Introduction. A G case provides AFMC technical assistance, including the following services. 8.57.1.1. Contractor Engineering and Technical Services (CETS). 8.57.1.2. International Engine Management Program (IEMP). 8.57.1.3. Technical Coordination Program (TCP). 8.57.1.4. Electronic Combat International Security Assistance Program (ECISAP). 8.57.1.5. Foreign Liaison Officer (FLO) administrative support. 8.57.1.6. International Logistics Communication System (ILCS). 8.57.1.7. Aircraft Ferry Services. 8.57.2. The purchaser's request must describe the services and scope of assistance needed, the time frame for desired assistance, and the type of case requested (either D/O or blanket-order (B/O)). If the purchaser asks for a blanket-order case, the request should show the dollar value desired. Separate requests should be made for each type or category of technical assistance. 8.57.3. CETSs. 8.57.3.1. CETSs are described in Chapter 14 of this manual. 8.57.4. IEMP Cases. 8.57.4.1. IEMP cases provide follow-on technical and logistics services for participating countries. The Component Improvement Program (CIP) is a United States (US) Government managed program which develops improved parts and maintenance techniques. CIP benefits are available only to IEMP participants. 8.57.4.2. Request Letter of Offer and Acceptance Data (LOAD) from the office listed above. If writing a follow-on case, request LOAD at least seven months before the expiration of current coverage. 8.57.4.3. Follow-on cases are prepared, processed, accepted, and implemented no later than two months before the effective period of the program. IEMP managers will provide the LOAD no later than seven months before the start of the program period. The IEMP manager will provide the FMS purchaser's share of each year's pro rata cost and travel requirements no later than 30 days from requested date. 8.57.4.4. Offer expiration date (OED) extensions will be limited to one and only if it does not affect the period of performance. 8.57.4.5. IEMP cases are written for a three-year period unless the purchaser has requested in writing a one- or two-year period. No LOA will be written for less than one year. 8.57.5. TCP Cases.

8.57.5.1. The TCP is a follow-on support effort to continue improving systems serviceability, maintainability, and reliability (improved parts, maintenance techniques, increased inspection and overhaul intervals, modifications, etc.). The systems Technical Coordination Group (TCG) serves as the single point of contact (POC) for follow-on technical and engineering support to member countries for modification, maintenance, and operation of their systems, with the exception of aircraft engines. (The engine manager at the designated Air Logistics Center (ALC) is responsible for managing each respective engine and its IEMP.) 8.57.5.2. Request LOAD from the office listed above. If requested by the customer, the TCG will include LOAD for an engineering drawing line. If writing a follow-on case, request LOAD at least seven months before the expiration of the current coverage. Follow-on cases are prepared, processed, accepted and implemented no later than two months before the effective period of such program. LOAD must be sent to the AFSAC geographic offices by the respective TCP managers no later than seven months before the start of the program period. The TCG manager will provide the FMS purchaser's share of each year's pro rata cost and travel requirements. 8.57.5.3. TCG cases are written for a three-year period unless the purchaser requests, in writing, a one- or twoyear period. No LOA will be written for less than one year. 8.57.6. FLO. The only service required on a FLO case is office space; all other services have to be requested by the customer on the LOR (i.e., secretarial support, communication services, delivery services, etc.). Services available under a FLO case include the following. 8.57.6.1. Office Space/Utilities. 8.57.6.1.1. Prior to the beginning of each period of performance, the AFSAC Financial Resources Branch (AFSAC/SDFB) will provide each CM with the total annual cost of the FLO's office space/utilities maintenance. 8.57.6.1.2. For the POP, the CM will set up a custom commitment of 4E (reimbursable) funds in SAMIS. 8.57.6.1.3. Each month, when the Human Resource Division (AFSAC/SDH) receives the AFSAC base utilities billing, a breakout of the applicable G case fund cites and monthly payment amounts along with the AFSAC administrative fund cite and amount will be provided to DFAS Denver. 8.57.6.2. Secretarial Support. 8.57.6.2.1. These procedures only apply to those FLO cases which have a line item for secretarial support on the LOA. AFSAC/SDFB will process and implement the line item for secretarial support. 8.57.6.3. Commercial Express Delivery Services. FLOs have the capability to use commercial express delivery services that can be billed directly to the FLO support G case. Steps are as follows. 8.57.6.3.1. AFSAC geographic office sends a cover letter to the appropriate branch within Aeronautical Systems Center listing individuals authorized to send and receive express packages on the requested contract. 8.57.6.3.1.1. Attachment 1: Fill out a purchase request. If the request goes to the Logistics Support Contracting Branch (ASC/PKWT), use AFMC Form 36, Purchase Request. If the request goes to the Operational Support Contracting Branch (ASC/PKWO) or the Logistics Support Contracting Branch (PKWR), use AF Form 9, Request for Purchase. The CM will input a custom commitment of 4F funds in the SAMIS for the total amount of service. 8.57.6.3.1.2. Attachment 2: Statement of work (SOW). 8.57.6.3.2. After the contract is awarded, the bills will come directly to the CM for certification. Invoice will be stamped with coordination information, including office information, name, and date. 8.57.6.3.3. The Invoice is attached to a two-way memo (Optional Form 27 or equivalent) to DFAS Denver requesting billing, with a copy to ASC/PKWO, PKWR, or PKWT, as appropriate. Included on the two-way memo will be the invoice number, amount of the invoice, billing date, and a case designator and document number that the billing should be processed against. 8.57.6.4. International Merchant Purchase Authorization Card (IMPAC). The IMPAC allows the FLO to purchase from various sources as long as they accept the IMPAC. The maximum purchase is $2,500, unless the item(s) being purchased are Government Service Agency (GSA) priced. 8.57.6.5. Preparation of LOAD. When requesting LOAD, the Case Manager will directly request the information from the AFSAC Financial Resources Branch (AFSAC/SDFB) and/or the AFSAC Facilities Branch (AFSAC/CVB). 8.57.7. Electronic Combat International Security Assistance Program (ECISAP) Cases. 8.57.7.1. Introduction. The ECISAP case is managed by the Deputy Under Secretary of the Air Force, International Affairs, Systems Division with the executive office at Warner Robins ALC, International Electronic Warfare Division (WR-ALC/LNI). The ECISAP provides total system engineering and technical services support to FMS users of software reprogrammable electronic combat (EC) systems throughout their lifecycles. The ECISAP

serves as the single point of contact for EC reprogrammable system development and follow-on support, as well as a forum for the exchange of technical information that is common to all ECISAP country participants. 8.57.7.2. For new customers there is a one-time facility buy-in charge. 8.57.7.3. Preparation of LOAD. In response to a customer LOR for ECISAP support of a system, the CM will develop a three-part request for LOAD. Part I is for WR-ALC/LNI, Part II for Headquarters Air Combat Command, Flight Operations Division, Security Assistance Branch (HQ ACC/DOTS), and Part III for HQ USAF/INXFJ. (Break-out details for the LOAD are provided below.) All three organizations should receive copies of the entire request. 8.57.7.3.1. The respective LOAD sources should specify costs (for each requested system) as follows (along with the costs, the LOAD sources should provide descriptive details of services and deliverables as appropriate). 8.57.7.3.1.1. WR-ALC/LNI for the following. 8.57.7.3.1.1.1. One-time facility buy-in. 8.57.7.3.1.2.2. ECISAP services to include those in producing ECISAP deliverables. 8.57.7.3.1.1.3. ECISAP deliverables (software, tapes, operating and programming handbooks). 8.57.7.3.1.1.4. Studies and surveys (to include travel). 8.57.7.3.1.1.5. ECISAP related Country Standard Technical Orders (CSTO). 8.57.7.3.1.2. HQ ACC/DOTS for efforts to be worked by AWC/36 ETS (36 ETS). 8.57.7.3.1.2.1. One time facility buy-in. 8.57.7.3.1.2.2. ECISAP services to include those in producing ECISAP deliverables. 8.57.7.3.1.2.3. ECISAP deliverables (software, tapes, operating and programming handbooks). 8.57.7.3.1.2.4. Studies and surveys (to include travel). 8.57.7.3.1.2.5. ECISAP related CSTOs. 8.57.7.3.1.3. HQ USAF/INXFJ. 8.57.7.3.1.3.1. Electronic Warfare Integrated Reprogramming Data Base (EWIRB) support. (Data is passed to WR-ALC and 36 ETS.) 8.57.7.3.1.3.2. Studies and surveys (to include travel) for EWIRB support. 8.57.7.6. Preparation of LOA and Acceptance. 8.57.7.6.1. In preparing an ECISAP case, it is important to develop case lines using the appropriate line manager code (LMC), operating agency code (OAC), and Military Articles and Services List (MASL) as specified below. 8.57.7.6.1.1. For LOAD provided by WR-ALC/LNI, establish case lines with LMC of C7 and OAC of 47. 8.57.7.6.1.2. For LOAD provided by ACC/DOTS, establish case lines with LMC of F1 and OAC of 78. 8.57.7.6.1.3. For LOAD provided by HQ USAF/INXFJ establish case lines with LMC of B1 or B2 and OAC of 47. HQ USAF/INX has requested that AFSAC manage its ECISAP case lines. 8.57.7.6.1.4. Use MASLs as indicated below for the case lines: 8.57.7.6.1.4.1. MASL (R9A)0791000EC1SAP for ECISAP related services. 8.57.7.6.1.4.2. MASL (J7J)709Z00DATPROC for ECISAP software product related deliverables. 8.57.7.6.1.4.3. MASL (J8A)768ZB00KSPUBS for ECISAP related CSTOs. 8.57.7.6.1.4.4. MASL (R4A)0074000STDSRVY(N) for Studies and Surveys to include travel. 8.57.8. Travel and management cases are described in AFMAN 16-101. 8.57.9. International Logistics Communication System (ILCS) Cases. 8.57.9.1. Introduction. The ILCS is developed and managed by the AFSAC as a Q case; follow-on support is to be written as a G case or Q case. 8.57.9.2. Preparation of Letter of Offer and Acceptance Data. Upon receipt of a security assistance (SA) country initial requirement for ILCS telecommunications, the AFSAC Case Manger (CM) will request LOAD from DAASC with an information copy of the request to AFSAC Information Technology Division (AFSAC/SD). Please note that the LOAD Coordinator located in the LOA Preparation Branch (AFSAC/COMW) does not task DAASC for this information. 8.57.10. Aircraft ferry services. 8.58. H CasesD/O Cases for Transportation Services. H cases provide transportation services (except ferry services) to move articles through the defense transportation system (DTS) from the point of origin or entry into US/DoD custody to a designated location. B/O cases are not appropriate for transportation cases. Additional guidance is in chapter 7, AFMAN 16-101. 8.59. J CasesReserved (Formerly Ferry Services, Now Written as G cases).

8.60. K CasesCLSSA. K cases are described in Chapter 8, Section G. 8.61. L CasesD/O Cases for Equipment. L cases, formerly used for D/O equipment cases, are now written as E B/O cases with the individual items listed in the notes section of the LOA when specified in the LOR. 8.62. M CasesD/O and B/O Cases for Depot Level Maintenance. Guidelines for processing maintenance cases are in chapter 14. 8.63. N CasesSpecial Support. N Cases are for multicommand and/or special services. These cases include complex technical assistance, complex training, intelligence programs, exercises, aircraft ferry, etc. New requirements for N Cases will be written and managed by AFSAC as Q Cases (for materiel/services) or G Cases (for services only). 8.63.1. AFSAC: 8.63.1.1. Gets the LOR from the customer for setting up the LOA. 8.63.1.2. Prepares the LOA, and sends the LOA to the customer for signature. 8.63.1.3. Gets a signed copy of the LOA and makes sure OA is issued. 8.63.1.4. Forwards IPD to responsible line manager(s). 8.64. O CasesB/O and D/O Cases for Communication Security (COMSEC). 8.64.1. O cases include all types of actions involving COMSEC or cryptological items, except those items included in a major system sale. Basic guidance is in the DoD 5105.38-M (SAMM), NACSI 6001(C), Foreign Military Sales of Communications Security and Services to Foreign Governments and International Organizations and AFMAN 16-101. Requests for major end-items are sent to the National Security Agency. 8.64.2. The customer sends the LOR to SAF/IA for items within the scope of annexes B and C of NACSI 6001(C). Requests for items within the scope of annex A are sent to USASAC. 8.64.3. Pricing studies are sent to Cryptological Systems Groups (CSG) with an information copy for AFSAC. CSG sends the pricing studies data back to AFSAC. 8.64.4. AFSAC prepares the LOA and forwards it to AFCSC. 8.64.5. AFSAC will: 8.64.5.1. Input the case in SAMIS. 8.64.5.2. Send an IPD to CSG telling them that obligation authority is available. 8.64.5.3. Input, if necessary, requisitions and send referral orders to CSG. 8.64.6. The majority of the cases are B/O with the FMS customer submitting the requisitions. Some cases are D/O and the AFSAC case manager inputs requisitions. 8.64.7. Maintenance cases are custom committed. The funds document control number notices are sent to CSG. More information on custom commitment transactions is in section D. 8.65. P CasesD/O and B/O Cases for Publications. P cases are fully described in section H. 8.66. R CasesB/O Spare-Parts Cases. 8.66.1. R cases are usually set up to order spare parts of US origin and may have an ordering period of up to two years. This case sets the dollar value for items that the customer requisitions during the period of the case. Usually, only one R case is necessary for each customer. The Air Force encourages the customer to use CLSSA for followon spares support. 8.66.2. AFSAC: 8.66.2.1. Receives the LOR from the customer with the requested dollar-value for setting up the LOA. 8.66.2.2. Prepares the LOA, establishes a case record in SAMIS, and sends the LOA to the customer for signature. 8.66.2.3. Receives a signed copy of the LOA and makes sure OA is issued. 8.66.2.4. Notifies the customer by message that requisitioning can start. 8.67. T CasesTraining. T cases apply to all types of training, including formal courses, familiarization or qualification training, aircrew training, professional training, mobile training teams, engineering technical services, and other technical or specialists training. More information is in Chapters 7 and 10, AFMAN 16-101. 8.68. U CasesMilitary Assistance Program (MAP). 8.68.1. U cases are reserved by the Air Force to track Section 506 drawdowns and similar non-FMS security assistance Grant-Aid transactions. 8.68.2. U case designators are used to control new grant aid record control numbers received on a Military Assistance Program order and 506A-drawdown action. They are used for internal SAMIS processing and identification. More information on processing is found in Chapter 11 of this volume.

8.69. V CasesBlanket-Order and Defined-Order Cases for Class IV Modifications. 8.69.1. Class IV modifications include safety of flight, mission essential, and logistics type modifications. V cases can also include USAF or contractor services (installation); however, installation is best done through an M case. 8.69.2. The USAF encourages the use of blanket order cases to reduce administrative processing and speed delivery. The customer may ask for a defined order case, but increased processing time and possible increase in costs may result. For safety of flight modifications, the delayed receipt of kits may cause hazardous operating conditions. 8.69.3. Pricing guidelines are in chapter 7 and DoD 7000.14-R, Vol. 15. Pricing studies are not necessary for blanket order V cases; however, if installation by the USAF is needed, a manpower availability study is made. 8.69.4. Approved Class IV A (safety) modification requirements which have an application to FMS systems and equipment are sent immediately by message to all affected FMS customer air attaches or designated representative for review and acquisition through established channels. 8.69.5. Class IV B (mission essential) and Class IV C (logistics) modifications for FMS modification requirements are sent within five days after configuration control board approval. 8.69.6. According to DoDI 5000-2_AFSUPI, all Class IV (safety, reliability, or maintainability) modifications and updating changes to standard USAF equipment are documented by a TCTO. Section F of DoDI 5000-2_AFSUPI gives a detailed explanation of security assistance modification-management procedures. 8.69.7. DODI 5000-2_AFSUPI states: 8.69.7.1. The customer must respond quickly for Class IV and V Modifications. Delayed replies may result in program delays and increased costs. The SAO (or equivalent) should speed up the customer's replies when possible. 8.69.7.2. If customers do not reply by the specified date, the Air Force assumes they are not interested and proceeds with the modification. If customers later want to take part in the modification, they must pay all added costs resulting from the delayed response. 8.69.8. Upon receipt of FMS customer acceptance and fund authorization for Class IV modification kits, the AFSAC case manager makes sure requisitions are prepared and input into SAMIS. The unit price and the RAD for the requisition come from the AFMC kit monitor. The criteria for processing Class IV modification kit requisitions is based on the following: 8.69.8.1. Requisitions with a valid kit stock number are input to SAMIS with a D process code which generates a SAMIS passing/referral order listing (PCN: U-WOO1.-HAA). SAMIS assign the routing identifier and the referral order is sent to the source of supply. 8.69.8.2. Requisitions that do not have a valid kit stock number are input into SAMIS with process code X. Routing of the requisition is assigned by AFSAC to the applicable ALC kit monitor for input into the D035 system and necessary supply action. 8.70. W CasesDefined-Order Cases for Class V Modifications. W cases were formerly used for definedorder (D/O) cases for Class V modifications. These modifications are now provided under V cases and the W designation is reserved. 8.71. X CasesHolding Accounts and Financial Projects. An X case is used only by DFAS for management purposes with SAF/IA approval. No LOA is prepared (see DoD Financial Management Regulation, Vol. 15. 8.72. Z CaseSpecial Management (Non-FMS). A Z case is used for management control of leases under the Arms Export Control Act (AECA), Chapter 6, or for actions not governed by the AECA but for which similar procedures and controls are desirable (such as leases under Title 10 USC, Section 2667) (see chapter 12). 8.73. Thru 8.77. (Unused.) Section 8GCOOPERATIVE LOGISTICS SUPPLY SUPPORT ARRANGEMENTS (CLSSA) 8.78. Background. 8.78.1. The Air Force provides FMS spares support to eligible countries through initial support packages and follow-on support cases. (The term spares refers to reparable and consumable spares and repair parts.) 8.78.1.1. An initial spares package is used to establish in-country operating stocks. Operating stocks are depot and base stocks used to maintain the weapon system on a day-to-day basis. Initial support is provided through an LOA that includes the weapon system (e.g., F-16, C-130) and the support necessary (e.g., spares, support equipment,

technical assistance, training, TOs, other publications) to establish an in-country operational capability. Initial support LOAs are identified by D, S, Y, or Q case designators. 8.78.1.2. Follow-on support begins with the operation of the weapon system. Follow-on support is necessary to replenish operating stocks as they are used to maintain the weapon system. As items become unserviceable through use, they may be repaired or replaced. This requires both repair and procurement actions. There are three different types of FMS follow-on spares cases. All three can be for both repair or procurement: 8.78.1.2.1. D/O Case: A D/O case is written for specific items and quantities. The materiel is normally lead-time away. 8.78.1.2.2. B/O Case: A B/O case is written for a dollar value. Requisitions can be submitted up to the dollar value of the case. The materiel is normally lead-time away. 8.78.1.2.3. CLSSA: The CLSSA program is a method for customer countries to become a partner in the U.S. logistics system, and to obtain spares support in a timely mannerin less than lead-time. 8.79. Cooperative Logistics Supply Support Arrangement (CLSSA) Overview. 8.79.1. Definition: CLSSA is an agreement between USAF and a foreign military service or organization that sets forth the terms and conditions for providing timely follow-on spares support. The CLSSA program can provide timely follow-on spares support because the CLSSA participant becomes a partner in the USAF and Defense Logistics Agency (DLA) supply systems. As a partner: 8.79.1.1. The CLSSA participant's spares requirements are forecast in advance. 8.79.1.2. The CLSSA participant invests in the USAF and DLA supply systems to allow the forecasted requirements to be bought in anticipation of future requisitions. 8.79.1.3. The CLSSA participant's requisitions are then eligible to be filled from a combined pool of US and CLSSA assets. 8.79.2. To make the CLSSA program work requires two FMS cases the Stock-Level Case and the Requisition Case. 8.79.2.1. Stock-Level Case or Foreign Military Sales Order I (FMSO I). The customer's spares requirements, financial liability, and financial investment in the USAF and DLA supply systems are defined in the FMSO I case. The customer is financially liable for all of the FMSO I defined requirements. Its financial investment, however, is 5/17th of the total liability. It is the customer's financial liability and 5/17th investment that gives the USAF and DLA the authority to buy and store assets in anticipation of the CLSSA customer's future requisitions. 8.79.2.2. Requisition Case or Foreign Military Sales Order II (FMSO II). The customer's requisitions for the FMSO I requirements are submitted on the FMSO II case. Requisitions for eligible FMSO I items will receive support equal to the USAF in priority. (Other than FMSO I items may be requisitioned on the FMSO II case, but they are not eligible for preferred treatment.) 8.79.3. CLSSA requisitions are entitled to equal support in priority with USAF requisitions. The CLSSA program does not guarantee that all eligible CLSSA requisitions will be filled immediately from depot stocks. Not all USAF requisitions are filled immediately from depot stocks. The Air Force Security Assistance Center (AFSAC) continually monitors the quality of support provided by the supply system. Statistics that show the quality of support CLSSA requisitions receive are available from the AFSAC FMSO I case managers. 8.79.4. CLSSA is for US-depot-to-country-depot support. It is not intended to provide direct support for on-line operational aircraft. To achieve the best weapon system operational rate, in-country depot and base operating stocks should be maintained. 8.79.5. All costs associated with FMS customer use of the DoD supply systems must be recovered by the US Air Force. 8.79.6. One-time DCSA approval is required for an FMS customer to participate in CLSSA. Once approval is given, all aspects of a countrys CLSSA program are managed by AFSAC. 8.79.7. Losses to stored stocks in USAF facilities from natural disaster or enemy action will be assessed proportionately against the US and the FMS customer. 8.80. The FMSO I Stock-Level Case. 8.80.1. The FMSO I Case: 8.80.1.1. Defines the customer's follow-on spares requirements to be held on-hand or on-order by the USAF and DLA. Materiel is bought to support the customer's CLSSA requirements and it becomes an integral part of the U.S. inventory. It is not physically segregated nor accounted for separately from other US stocks.

8.80.1.2. Provides the USAF and DLA the authority to buy and store materiel in anticipation of the CLSSA customer's requisitions. 8.80.1.3. Provides the AFSAC Security Assistance Management Information System (SAMIS) the capability to determine which requisitions are eligible to be filled from depot stocks. Requisitions for items and quantities forecast on the FMSO I are coded programmed eligible for support from depot stocks. Requisitions for items or quantities not forecast on the FMSO I are coded non-programmed not eligible for support from depot stock. 8.80.1.4. Serves as the basis for the customer's financial investment in the U.S. supply system. 8.80.2. FMSO I Item Eligibility and Exclusions. 8.80.2.1. Only spares and repair parts stocked by the USAF and DLA are eligible for inclusion on the FMSO I stock-level case. The types of spares are: 8.80.2.1.1. USAF-managed investment (reparable) items (ERRC C & T). 8.80.2.1.2. USAF-managed expense (consumable) items (ERRC N and P). 8.80.2.1.3. DLA-managed expense (consumable) items (ERRC N and P). 8.80.2.2. Some spares are ineligible for the FMSO I because they require special management or special handling. See attachment 8G1. 8.80.3. FMSO I Management Categories. For management purposes, the FMSO I spares requirements are grouped into different categories. They are: 8.80.3.1. USAF Investment (Reparable) Items Procurement. 8.80.3.1.1. When an item is removed from a weapon system in country, it can either be fixed or replaced. To replace an item, the customer submits a requisition for the item. This action is called procurement. 8.80.3.1.2. SAMIS will compute FMSO I Investment Item Procurement stock levels based on FMSO II cases recurring, nonrepair and replace requisitions received in the past four years. (A ttachment 8G13 provides a description of the different types of FMS requisitions) 8.80.3.2. USAF Investment (Reparable) Items Repair. 8.80.3.2.1. When an item is removed from a weapon system in country, it can either be fixed or replaced. To fix an item, repair and replace (R&R) may be used. Upon return of an approved carcass, SAMIS creates a replacement requisition (H-coded). 8.80.3.2.2. SAMIS will compute FMSO I Investment Item Repair stock levels based on FMSO II cases H-coded requisitions processed in the past four years. 8.80.3.3. USAF Expense Items. SAMIS will compute FMSO I USAF Expense Item stock levels based on FMSO II cases recurring requisitions received in the past four years. 8.80.3.4. DLA Expense Items. SAMIS will compute FMSO I DLA Expense Item stock levels based on FMSO II cases recurring requisitions received in the past four years. 8.80.3.5. Liability File Items. SAMIS recomputes FMSO I stock levels quarterly. Excess FMSO I stock levels, for which there is recurring demand by an FMS customer (and, therefore, a stock level), are moved to the Liability File. The purpose of the Liability File is to identify and clear excess FMSO I items, and their respective liability. Both investment and expense items are processed through the Liability File. 8.80.3.6. Termination File Items. Excess FMSO I items, for which there is no recurring demand by an FMS customer (and, therefore, no stock level), are moved to the Termination File. The purpose of the Termination File is to identify and clear excess FMSO I items, their respective liability. Both investment and expense items are processed through the Termination File. 8.80.4. Interchangeability and Substitution (I&S). 8.80.4.1. When two or more items functional and physical characteristics are equal in performance and durability, and they are capable of being exchanged for one another without alteration, they are managed within an I&S group. The most preferred item of the I&S group is called the master item. The items in the group are called the I&S family members. 8.80.4.2. The FMSO I stock levels are maintained under the I&S master NSN. SAMIS automatically updates the I&S master when there is a change. 8.81. FMSO I Case Development Overview. 8.81.1. The FMSO I stock levels can be established in four ways: 8.81.1.1. Recurring Requisitions. Primarily, FMSO I stock levels are based on customer FMSO II cases recurring requisitions (R in pos 44 of the requisition). Recurring FMSO II case requisitions:

8.81.1.1.1. Are eligible to be coded programmed. (Programmed requisitions are eligible for support from depot stocks.) 8.81.1.1.2. Are used to compute the FMSO I stock levels. 8.81.1.1.2.1. SAMIS will compute FMSO I Repair Stock Levels based on Repair and Replace (H-coded) requisitions that process on the FMSO II case. All H-coded requisitions on FMSO II cases are coded recurring. NOTE: The repair stock level is not for repair; it is to augment AFMC stocks to support the repair pipeline. Also, it is to allow the IM to buy stocks in advance of receiving H-coded requisitions, so the requisitions can be filled in a timely manner. (See attachment 8G13 for a description of the different types of FMS requisitions.) 8.81.1.1.2.2. SAMIS will compute FMSO I Procurement Stock Levels based on recurring nonrepair and replace (non-H-coded) requisitions that process on the FMSO II case. (These are normal A01 requisitions submitted by the customer.) SAMIS will compute procurement stock levels for both investment and expense items. 8.81.1.2. Initial CLSSA Program Overview. When a customer first joins CLSSA, there is no demand history for SAMIS to use to compute stock levels, so the following process is used: 8.81.1.2.1. The customer provides the AFSAC manager with the operational and maintenance data for the weapon system to be supported through CLSSA. The USAF System Manager identifies the appropriate NSNs and quantities, and provides them to AFSAC through SAMIS. 8.81.1.2.2. AFSAC sends the CLSSA Recommended Item Listing to the customer for modification and/or approval. The customer reviews the listing and makes any desired changes. The changes are returned to AFSAC and are used to produce an updated listing. The updated listing becomes the customer's FMSO I stock levels. 8.81.1.2.3. The FMSO I LOA is written using the values from the updated listing. 8.81.1.3. Major Add Overview. 8.81.1.3.1. A Major Add is the addition of a new weapon system to an existing FMSO I. It can also be an increase to an existing FMSO I weapon system. (For example: a country buys 12 F-16s and they already own 24 F16s.) In both instances, for the additional requirement, there is no demand history for SAMIS to use to compute stock levels, so the process described above is used. 8.81.1.3.2. An Amendment to the FMSO I LOA is prepared to add the new system and requirements to FMSO I. 8.81.1.4. Manual Adjustments. The customer may notify AFSAC of significant increases (a dramatic increase in weapon system operations) or decreases (deactivation of a weapon system) in future demand. In these instances demand history and, therefore, stock levels will be manually adjusted. Normal liability file processing will occur. Because this is an intensive, complicated, and totally manual process, its use is restricted to significant situations and limited to a minimum number of items. 8.82. FMSO I Initial and Major-Add Program Processing. 8.82.1. Overview. When a customer first joins CLSSA, the requirements it adds to the CLSSA program are called its initial program. The addition of requirements for a new weapon system, or the addition of requirements for more of an existing weapon system, to an established FMSO I is called a major add. There are two different ways to develop an initial or major add CLSSA program: 1) an Air Logistics Center (ALC) System Program Director (SPD) recommendation; or 2) a recommendation based on customer-provided data. Usually an SPD recommendation is used. 8.82.2. If the SPD recommendation method is used, the following applies: 8.82.2.1. The FMS customer identifies (to the AFSAC FMSO I manager) the weapon system to be supported by mission, design, and series (MDS) (e.g., F-16), the number of aircraft (e.g., 12), flying-hour program (e.g., 15 per month), number of operating sites (e.g., two main operating bases, one forward operating base), installed equipment, and the maintenance concept (e.g., Organizational and Intermediate (O&I) maintenance in-country). If the end-item is equipment such as a radio set, the customer will give the number of operating hours and number of sites for ground sets, or the number of aircraft and flying-hour program for airborne sets. Requests for engine spares will include engine operating hours. 8.82.2.2. The AFSAC case manager will send the customer-provided operational and maintenance requirements to the ALC/SPD and ask for the following in XD2-3 format (attachment 8G2): 8.82.2.2.1. A 24-month investment (ERRC C and T) item procurement range and depth spares recommendation. This recommendation is to be based on the condemnation rate of the spares. 8.82.2.2.2. A 24-month investment (ERRC C and T) item repair range and depth spares recommendation. This recommendation is to be based on the Not Reparable This Station (NRTS) rate of the spares.

8.82.2.2.3. A 24-month expense item (ERRC N & P) range and depth spares recommendation. This recommendation is to be based on the condemnation rate of the spares. 8.82.2.3. The SPD will produce the CLSSA recommendation. 8.82.2.3.1. Items applicable to the weapon system(s), subsystem(s), end article(s), etc., are to be considered for inclusion in the recommendation. 8.82.2.3.2. The SPD recommendation should be conservative. This is to preclude establishing stock-level requirements that may never be needed. Once the conservative stock level is established on the FMSO I, it will be automatically adjusted based on actual customer demand patterns. 8.82.2.3.3. The following are possible sources that may be used in compiling a recommendation. All sources of information available, however, should be considered. 8.82.2.3.3.1. Application files from the D200A Secondary Item Requirements System. 8.82.2.3.3.2. Initial spares support lists (ISSL). 8.82.2.3.3.3. Preliminary group assembly parts lists. 8.82.2.3.3.4. Materiel requirements lists (MRL). 8.82.2.3.3.5. Recoverable item breakdown. 8.82.2.3.3.6. International Weapon Item Projection System (IWIPS). 8.82.2.3.4. The recommendation data is to be provided in XD2-3 format (see attachment 8G2). The ALC/SPD recommendation can be returned to AFSAC on 3.5 disk with a corresponding materiel listings sent to AFSAC case manager. The cover letter accompanying the data should include information important for the recommendation. 8.82.2.4. AFSAC will use SAMIS to process the recommendation data. 8.82.2.4.1. SAMIS will produce the CLSSA Recommendation Listing (U-W001.GAC/GAD). The CLSSA Recommendation Listing will show eligible CLSSA items. 8.82.2.4.2. The CLSSA Recommendation Listing will include stock level recommended quantities computed using the formula: average monthly demand (AMD) times the actual lead-time of the item. The AMD is computed using the 24-month SPD recommendation. If necessary, SAMIS will adjust the recommended quantities to be consistent with the worldwide stock levels. That is, on an item-by-item basis, SAMIS will not allow the recommended quantities to be out of proportion with existing stock levels for all the other CLSSA customers. 8.82.2.4.3. AFSAC will then send the two listings through the Security Assistance Organization (SAO), Office of Defense Cooperation (ODC), or attach/purchasing mission, as appropriate, to the FMS customer air force. 8.82.2.5. After getting the CLSSA Recommendation Listing, the CLSSA customer makes an item-by-item review of the investment item procurement and repair recommendations. The customer marks the listing with desired adjustments. For each adjustment, the FMS customer should prepare an appropriate adjustment transaction. A transaction with document identifier XD3-3 is prepared when an item is to be added to the recommendation. An XD3-6 is prepared when the quantity of a recommended item is to be increased. An XD37 is prepared when the quantity of a recommended item is to be decreased. An XD3-8 is prepared when an item is to be deleted from the recommendation. After completion of the review, one copy of the annotated listing along with the XD3-3/6/7/8 adjustments are returned to AFSAC. The XD3 transactions may be returned to AFSAC manager on 3.5 disk. The XD3 record formats are shown in attachment 8G3. Usually adjustments are made only to the investment-item levels. Expense-item levels, however, can also be adjusted. 8.82.2.6. When the AFSAC case manager gets the annotated list and the XD3 adjustment transactions from the CLSSA customer, they will review them to insure the adjustments are properly formatted, and then they will be input to SAMIS. SAMIS will process the adjustments and produce the CLSSA Stock Level Requirements Listing (U-W001.GAF/GAG). 8.82.2.7. The AFSAC case manager will prepare a FMSO I LOA using values from the CLSSA Stock Level Requirements Listing. An Amendment to the LOA is used for a major add. 8.82.2.8. The AFSAC case manager will send the FMSO I LOA/Amendment to the FMS customer (through appropriate channels). The AFSAC case manager will also send three copies of the CLSSA Stock Level Requirements Listing to the customer. This report represents the stock-level case. It shows all selected eligible items in NSN sequence and dollar totals for all categories of items. 8.82.2.9. After the LOA/Amendment has been accepted by the FMS customer and Obligation Authority (OA) received, the AFSAC case manager will enter the FMSO I case in SAMIS. SAMIS will add the new requirements

to the FMSO I and automatically send the FMSO I stock level requirements to AFMC and DLA for inclusion in their requirements computation systems. (See paragraph 8.85 for additional information on this process.) 8.82.3. If the customer asks, the CLSSA Recommendation Listing can be prepared using customer provided data. No ALC/SPD involvement is necessary in this process. The customer provided data is entered in SAMIS using the XD2 format and from then the process is the same as for an SPD recommendation. 8.83. FMSO I Computations. 8.83.1. The FMSO I is a demand based process. SAMIS automatically computes Stock Level Quantity (SLQ), Stock Level Values, and Eligible-to-be-Programmed Quantities (EPQ) based on customer recurring FMSO II demand. 8.83.1.1. The FMSO I SLQ is the customers total FMSO I requirement for an NSN. 8.83.1.2. The EPQ is that portion of the SLQ that SAMIS uses to code requisitions as programmed (eligible for support from depot stocks). 8.83.2. FMSO I SLQ Computation. The FMSO I stock levels and case values are based on four factors: 1) the average FMSO II case monthly demand, 2) the lead-time of the item, 3) any initial/major-add quantities, and 4) the current FMSO I price. 8.83.2.1. Definitions: 8.83.2.1.1. The AMD is calculated by SAMIS based on the quantity of FMSO II recurring requisitions over a four-year demand-history period. In computing the AMD, SAMIS weights older requisitions less than newer requisitions. The SAMIS Demand History File is available on the CLSSA Stock Level Item Query Report (456). Data is available on-line, on disk. 8.83.2.1.2. The lead-time used by SAMIS is either the procurement lead-time (PLT) or the repair lead-time for the item. Lead-times are included in the CLSSA Stock Level Item List (GCB) Report, and the CLSSA Stock Level Item Query Report. For SAMIS users, lead-times are also available on screen 283. (When using the repair leadtime on the 283 screen, add 182 days to arrive at the CLSSA repair lead-time.) 8.83.2.1.3. The FMSO I Procurement and Repair stock levels are valued using the current FMSO I price. 8.83.2.2. SLQ Computation. The CLSSA stock levels are computed by SAMIS. 8.83.2.2.1. For the Repair Stock Level, the formula is: Average Daily Demand for Repair and Replace (H-coded) requisitions times the repair lead-time of the item, in days. (See attachment 8.G-2 for a description of the different types of FMS requisitions.) 8.83.2.2.2. For Investment Procurement-, and Expense-Item stock levels, the formula is: AMD times the PLT of the item (in months). The PLT will range from 1 to 60 months. Attachment 8G4 is a detailed example of the SLQ computation process. 8.83.2.2.3. Initial/Major-Add Program Processing. SAMIS will maintain initial and major add program quantities for a two-year (normally) maturity period computed from the date the NSN/quantities are established in SAMIS. During these two years, the SLQ will be computed as described above and added to the program initial/major-add quantities. At the conclusion of the maturity period, SAMIS will delete the initial/major-add program records, and in their place create pseudo-demand history records that will result in a stock level that equals the program initial/major-add quantities. Once this occurs, normal stock level, liability and termination file processing occurs. 8.83.3. FMSO I Stock Level Value Computation. The stock-level value is computed as the SLQ times the FMSO I price. 8.83.4. EPQ Computation. 8.83.4.1. The Worldwide EPQ is used by SAMIS in coding recurring FMSO II case Investment Item requisitions as programmed (eligible for support from depot stock). SAMIS will code eligible Investment Item requisitions as programmed if the requisition quantity is less than or equal to the Worldwide EPQ. 8.83.4.2. There is only one worldwide repair EPQ, and one worldwide procurement EPQ for each Investment Item NSN. CLSSA customers do not have their own EPQ. (SAMIS computes individual country EPQ amounts and then adds them together to determine the Worldwide EPQ.) 8.83.4.3. SAMIS recomputes SLQ and Worldwide EPQ every quarter. There will probably be more EPQ available on the first of the quarter than at the end of the quarter. As a result, requisitions submitted early in the quarter will have a better chance to be coded programmed. 8.83.4.4. The EPQ is computed by SAMIS as one quarters demand plus any unused EPQ from previous quarters up to the total SLQ. For example: EPQ COMPUTATION EXAMPLES

EXAMPLE 1 2

DMD/MO 1 1

PLT 24MO 24MO

SLQ 24 24

DMD/QTR 3 3

UNUSED EPQ 0 2

EPQ 3 5

8.83.4.4.1. Example 1: In example 1, one quarters demand is equal to three. Since there is no unused EPQ from the previous quarter, SAMIS can code requisitions programmed up to a quantity of three. 8.83.4.4.2. Example 2: Example 2 is the following quarter. SAMIS computes one quarters demand of three. In the previous quarter, SAMIS only received one recurring requisition for quantity one and only used one EPQ, leaving two unused. As a result, the current quarters EPQ is 5 (3+2). SAMIS can code requisitions programmed up to a quantity of five. 8.83.4.5. Requisitions for quantities in excess of the worldwide EPQ will be coded nonprogrammed. 8.83.4.6. The worldwide EPQ is not visible to the CLSSA customer. The customer can use their SLQ as a guide when submitting requisitions. In order to maximize the number of requisition coded programmed, individual requisition quantities should be less than or equal to the customers SLQ. 8.83.4.7. Any eligible FMSO II cases recurring investment item requisition may be coded programmed by SAMIS if there is sufficient worldwide EPQ. This allows customers that do not have an SLQ to get programmed support for their recurring requisitions. It also allows customers to requisition amounts exceeding their SLQ and get programmed support. In both of these circumstances, the customer should requisition small quantities to take advantage of available worldwide EPQ. In both instances, SAMIS will compute/adjust the SLQ based on the customers recurring requisitions. 8.83.4.8. Because of the worldwide EPQ concept, the IM may receive programmed requisitions from unexpected countries. The IM should not try to second-guess the programmed/nonprogrammed code in the requisition. IMs should support all programmed requisitions in the appropriate manner. 8.84. FMSO I Item Management. 8.84.1. Background: The purpose of CLSSA is to identify future FMS customer requirements and to augment US depots stocks so that FMS requisitions can be supported with on-hand/on-order assets. The CLSSA customers are financially liable for forecasted requirements that are in the supply pipeline. 8.84.2. SAMIS Item Management. SAMIS uses three files to project the CLSSA customers future requirements, and to manage the CLSSA customer's liability for the projected requirements. The three files are: The Stock Level File, The Liability File, and The Termination File. The CLSSA participant is financially liable for all FMSO I items included in these three files. 8.84.2.1. The Stock Level File. This file includes active repair and procurement stock levels for both reparable and consumable items. SAMIS computes stock levels for reparable and consumable items based on the FMS customer's recurring requisitions and actual lead-times. 8.84.2. The Liability File. See paragraph 8.86 for more detailed information. 8.84.2.1. This file is used to identify excess FMSO I reparable and consumable item requirements and to clear them from the FMSO I. When the repair or procurement stock levels decrease, the amount of decrease is moved to the Liability File for processing. 8.84.2.2. An item can be removed from the Liability File in one of three ways: 8.84.2.2.1. Based on NIIN, FMS non-H-coded (nonrepair and replace) requisitions that process through SAMIS will be used to remove items/quantities from the Liability and Termination Files, thereby, clearing the CLSSA customer's liability. There is an exception to this process: Requisitions with advice codes 6P (New and Unused), BV, 6V, 6W (Sole-Source), and 2C, 2J, 22, 31, 32, 33 (Do Not Substitute) are not used to clear liability. This is because these codes do not allow the IM to consider all assets when filling the requisition. See attachment 8G5 for a detailed example of this process. (Attachment 8G13 is a description of the different types of FMS requisitions.) 8.84.2.2.2. Based on NIIN, any increase in a stock level will remove a corresponding item/quantity from the Liability File. The increased stock level accounts for the liability for the removed item. 8.84.2.2.3. When there is no stock level for an item for any FMS country, any remaining levels are moved to the Termination File. Generally this will occur. 8.84.2.3. The Termination File. See paragraph 86 for more detailed information. 8.84.2.3.1. The Termination File is used to track and clear excess FMSO I items and quantities when there is no FMSO I stock level for any country. The Termination File is also used when an NSN becomes ineligible for the

FMSO I. Items that become ineligible for the FMSO I due to catalog changes are moved to the Termination File, and normal Termination File processing occurs. 8.84.2.3.2. An item/quantity may remain in the Termination File for up to two years. Every six months during that two years, SAMIS will route CLSSA Termination Absorption Request forms (U-W001.-GAV) to the Inventory Managers via the ALC FMS Focal Point Office. The IMs will complete the forms using D200A and backorder information. If this data indicates absorption is possible, SAMIS will remove the NSN/quantity from the Termination File and clear customer liability. 8.84.2.3.3. After two years, Drawdown Requisitions will be used to remove the unabsorbed items/quantities from the Termination File. Customer liability will then be resolved through normal Drawdown Requisition processing. 8.85. FMSO I Levels in the Buy-Computation Systems. 8.85.1. The CLSSA FMSO I Stock Level, Liability File and Termination File items are all accounted for in the buy computations. 8.85.1.1. D200A: 8.85.1.1.1. SAMIS passes the USAF managed FMSO I Stock Level items and quantities to D200A quarterly. D200A is used for both investment and expense spares (ERRC C, T, N, and P). The CLSSA Stock Levels are additive to the computed USAF stock levels. The CLSSA levels are shown in D200A under the heading FMS. 8.85.1.1.2. Quarterly, SAMIS passes a detailed listing of CLSSA D200A Stock Levels (CLSSA Requirements Listing report W001.-GBK) to each ALC FMS Focal Point office for distribution to the IMs. 8.85.1.1.3. Liability and Termination File items are included in the quarterly FMS Retention Listing passed to the IMs. 8.85.1.1.3.1. When an item/quantity is moved from the Stock Level File to the Liability/Termination File, it is no longer passed to D200A via the CLSSA pass, but it is added to the FMS Retention Listing. (SAMIS calculates the Retention Level as the current yearly FMS demand rate times 18.5 years minus the CLSSA SLQ plus the Liability and Termination File quantities. The Retention Level will vary due to changes in the yearly demand rate and changes in the Liability and Termination File quantities.) 8.85.1.1.3.2. The IMs use this listing in manually adjusting their retention levels. The Liability and Termination File items are included in the FMS Retention Listing because they are excess FMSO I requirements. The IM should not buy any more to support these requirements, but should not throw any assets away either until the CLSSA customer's liability for the items is resolved. 8.85.1.1.3.3. When the items/quantities are removed from the CLSSA pass, the D200A requirements will decrease (assuming no other changes). If this results in long supply stocks, they would show above the Control Level and be available to any FMS requisition. If long supply assets did not result, the assets would be required for other D200A requirements. (This concept is the basis for SAMIS using FMS requisitions to clear customer liability. (See Paragraph 8.86 for additional detail.) 8.85.1.2. DLA: 8.85.1.2.1. The DLA-buy-computation system is a demand-based system. Both DoD and CLSSA K case recurring demands are used to compute the buys. 8.85.1.2.2. Since SAMIS and the DLA-buy-computation system are both demand-driven, SAMIS will mirror DLAs system for the FMS requirements. Both SAMIS and the DLA system will recognize decreasing demand. The DLA system will adjust its requirements level accordingly. SAMIS will lower its consumable-item stock levels accordingly. 8.86. FMSO I Liability Management. 8.86.1. Clearing FMSO I Liability. The CLSSA customer's liability must be addressed when an item/quantity is moved from the Stock Level File into the Liability or Termination File, or when removed from the Liability or Termination Files. The following processes apply to reparable and consumable items. 8.86.2. Clearing Liability through Liability File Processing. 8.86.2.1. FMS non-H-coded (nonrepair and replace) requisitions that process through SAMIS will be used to remove items/quantities from the Liability and Termination Files, thereby, clearing the CLSSA customer's liability. There is an exception to this process: Requisitions with advice codes 6P (New and Unused), BV, 6V, 6W (Sole Source), and 2C, 2J, 22, 31, 32, 33 (Do Not Substitute) are not used to clear liability. This is because these codes do not allow the IM to consider all assets when filling the requisition. Attachment 8G5 is a detailed example of Liability File processing. (Attachment 8G13 is a description of the different types of FMS requisitions.)

8.86.2.2. SAMIS will use both programmed and nonprogrammed non-H-coded requisitions to remove items/quantities from the Liability and Termination Files. 8.86.2.2.1. The programmed requisitions are entitled to support using on-hand/on-order stock. Filling these requisitions removes assets from the supply system. Clearing FMSO I liability and removing the assets from the supply system results in the supply system being in balance. 8.86.2.2.2. Nonprogrammed non-H-coded requisitions that are used by SAMIS to remove items from the Liability/Termination Files will be uniquely coded with an NU Fund Code and a Program Code of 2. This coding automatically causes the IM to consider filling the requisition with available on-hand/on-order stocks. If there are insufficient stocks to fill the requisition, the IM may change the Fund Code to 4F and obtain the item with FMS Direct Cite Funds. This process gives the IM the opportunity to review stocks and use them, if available, to fill requisitions that are used to clear FMSO I liability. If stocks are not available to fill the requisition, it verifies that there are no assets for which the CLSSA customer is liable. 8.86.2.3. Based on NIIN, any increase in a stock level will remove a corresponding item/quantity from the Liability File. The increased stock level accounts for the liability for the item. 8.86.2.4. When there is no stock level for any FMS country, the item is moved to the Termination File. Generally this will occur. 8.86.3. Clearing Liability through Termination File Processing. 8.86.3.1. The Termination File is used to track and clear excess FMSO I items and quantities when there has been no FMS recurring demand for the NSN in four years. The Termination File is also used when an NSN becomes ineligible for the FMSO I. Items that become ineligible for the FMSO I due to catalog changes are moved to the Termination File, and normal Termination File processing occurs. 8.86.3.2. Every six months (January & July) SAMIS will produce CLSSA Termination Absorption Request forms for those items in the Termination File and route them to the IM via the ALC FMS Focal Point Office. The IM need only fill in the blanks with the appropriate information and return them to the FMS Focal Point who will input the data to SAMIS. See attachment 8G6 for instruction on processing the request forms. 8.86.3.3. SAMIS will use the data to determine if absorption is possible or not. If possible, the item/quantity will be removed from the Termination File and customer liability cleared. If not possible, a record of the review will be made, and the item/quantity reviewed again six months later. See attachment 8G7 for the SAMIS processing logic. 8.86.3.4. An item/quantity may remain in the Termination File for two years. If not absorbed within the two years, the item/quantity will be placed on a Drawdown Requisition and routed to the IM for resolution. D035A will place the Drawdown Requisition on 9P exception. Normal Drawdown Requisition processing applies. 8.86.4. Clearing Liability Using Drawdown Requisitions. 8.86.4.1. The primary means of clearing CLSSA customer FMSO I liability is through Liability and Termination File processing. Drawdown Requisitions are used to remove items/quantities from the Termination File both during and at the end of the two-year absorption review period. 8.86.4.1.1. A customer may remove an item/quantity from the Termination File at any time using a file maintenance transaction. An XD5-7 transaction will remove a partial quantity from the Termination File. An XD5-8 transaction will remove the entire quantity of an item from the Termination File. Both transactions will result in a Drawdown Requisition. The XD5-7/8 formats are shown in attachment 8G8. Drawdown Requisitions are only created by SAMIS when items are removed from the FMSO I and may not be input directly. 8.86.4.1.2. At the conclusion of the absorption review period (normally two years), SAMIS will remove the items from the Termination File and create Skeleton Drawdown Requisitions. They are called Skeleton Drawdown Requisitions because they are missing the document number, supplementary address, and disposition code. The AFSAC FMSO I manager will request the missing information from the country. If not received in 30 days, the FMSO I manager will follow-up; if no response in 60 days, the FMSO I manager will complete the requisition using Disposition Code C and allow it to process. 8.86.4.2. Drawdown Requisitions are identified by a V in position 11 of the Document Number. The IM will see them as D035A 9P exceptions. Drawdown Requisitions process in accordance with the Disposition Code which appears in the management code block on the D035A DoDA screen. The Disposition Codes are: 8.86.4.2.1. A Request USAF absorb the item. If IM is unable to absorb the item, deliver it in existing condition, either serviceable or unserviceable. 8.86.4.2.2. B Request USAF absorb the item. If the IM is unable to absorb the item, deliver it in serviceable condition. Restore unserviceables to serviceable condition.

8.86.4.2.3. C Request USAF absorb the item. If the IM is unable to absorb the item, deliver it in serviceable condition or dispose of unserviceables. 8.86.4.2.4. D Request USAF absorb the item. If the IM is unable to absorb the item, dispose of regardless of condition. NOTE: For disposition code B, unserviceable assets must be made serviceable before shipment. 8.86.4.3. New procurement is not authorized for Drawdown Requisitions. 8.86.4.4. The following actions are to be taken by the IM based upon the Disposition Code and the absorption criteria. (The absorption criteria are described below.) 8.86.4.4.1. Any quantity that can be absorbed will be canceled with a CA action. The CA notification criteria in Chapter 8, Section C applies. The AFSAC case manager must receive a copy of all cancellation correspondence. 8.86.4.4.2. Any quantity needing delivery to the FMS customer will be processed for shipment. If an unserviceable item is shipped, the IM notifies the DFAS billing office that an unserviceable item has been shipped to liquidate a CLSSA FMSO I liability, and that the stock-fund Unserviceable Asset Price (UAP) is to be billed. (For a non-stock fund item, the standard price less the repair price should be billed.) 8.86.4.4.3. If the quantity cannot be absorbed and the customer requested disposal action, the following applies: 8.86.4.4.3.1. Cancel the requisition with a CA and provide CA notification. The CA notification should state that disposal action will be taken. 8.86.4.4.3.2. If the asset was in serviceable condition, notify the DFAS billing office to bill the asset at the standard price and credit disposal value. If the asset was in unserviceable condition, notify DFAS to bill the asset at the stock fund Carcass Cost and credit disposal value. 8.86.4.4.3.3. No special disposal action is to be initiated for assets that the IM cannot absorb when using Disposition Codes C or D. Subsequent computations will consider the reduced FMS requirement, and these assets will be considered for disposal at that time using established procedures. 8.86.4.5. Drawdown Requisition Absorption Criteria: 8.86.4.5.1. If the asset position is OPTIMUM or SHORT (third short at the termination) the Drawdown Requisition quantity is to be absorbed. 8.86.4.5.2. If the asset position is OVER, subtract the unfunded Other War Reserve Materiel (OWRM) and the NON-PROGRAMMED NON-H-CODED FMS Backorders (B/O), that will be filled from on-hand/on-order stocks, from the OVER quantity to determine an Adjusted Over Quantity (AOQ). 8.86.4.5.2.1. If the AOQ is less than or equal to zero (in other words short or optimum) the Drawdown Requisition quantity is to be absorbed. The IM should cancel (CA) the requisition. 8.86.4.5.2.2. If the AOQ is greater than zero and less than the Drawdown Requisition quantity, the difference between the Drawdown quantity and the AOQ is to be absorbed. The IM should CA the absorbed quantity. 8.86.4.5.2.3. If the AOQ is greater than or equal to the Drawdown Requisition quantity, absorption is not possible. 8.86.4.5.3. See attachment 8G6 for information on processing FMS Non-programmed Non-H-Coded Backorders, Insurance/NSO Items, and items with no D200A Computation. 8.86.4.6. All decisions regarding Drawdown Requisition processing must be documented on the requirement computation sheet used to make decisions. 8.87. FMSO I Financial Management. 8.87.1. Customer Financial Liability. The CLSSA customer is financially liable for all items on their FMSO I Stock Level Case. This includes Repair and Procurement Stock Levels, and items in the Liability and Termination Files. 8.87.1. FMSO I Update. 8.87.1.1. On a quarterly basis: 8.87.1.1.1. SAMIS updates the FMSO I stock levels and adjusts the Liability and Termination Files. The stock levels are automatically computed by SAMIS. Once computed, they may not be manually adjusted. 8.87.1.1.2. A quarterly financial report showing the revised FMSO I Stock Level, Termination and Liability File values is provided to each customer (CLSSA Quarterly Financial Report GBL). 8.87.1.1.3. A line item listing report that shows stock levels and Termination and Liability File items and quantities is available upon request from the AFSAC case manager (CLSSA Stock Level Item List GCB). 8.87.1.2. On an as-required basis, the FMSO I will be financially updated. The CLSSA customer will be notified if the total of the FMSO I requirements exceed the FMSO I case value and will be told that an LOA Modification will

be processed in one year to increase the case value. The purpose of the one-year period is to allow the customer time to budget for the additional funds. 8.87.1.3. Close management attention by the CLSSA customer will minimize the need for additional FMSO I case funds. If the customer sees that the FMSO I requirements may exceed the FMSO I case value, they may adjust their demand pattern to lower the requirements value, or budget funds to cover the increased case value. 8.87.1.4. The AFSAC/FMSO I case manager is responsible for the financial update of the FMSO I case. 8.88. FMSO II Requisition Case. 8.88.1. Introduction. 8.88.1.1. The FMSO II case is a blanket-order case that is used by the customer to requisition spares. (Attachment 8G13 is a description of the different types of FMS requisitions.) 8.88.1.2. Only spares and repair parts (ERRC C, T, N and P) may be requisitioned on the FMSO II case. 8.88.1.3. Both FMSO I and non FMSO I items may be requisitioned on the FMSO II. Attachment 8G9 is a list of eligible and ineligible FMSO II items. 8.88.2. Requisition Submission. The customer may submit FMSO II requisitions directly to SAMIS by DAMES/DDN, STARR/PC, or by sending requisitions to the AFSAC case manager by mail or message. Countrysubmitted FMSO II requisitions: 8.88.2.1. Must have a priority which is assigned by the customer based on the Force Activity Designator and the urgency of need. It is important to submit requisitions for stock replenishment in a timely manner to minimize the need for priority requisitioning. 8.88.2.2. Must have a V Type of Assistance Code (pos 35). 8.88.2.3. Must be submitted in accordance with US Military Standard Requisitioning and Issue Procedures (MILSTRIP) and the Uniform Materiel Movement and Issue Procedures (UMMIPS). (See AFMAN 23-110, Vol. IX, Chapter 8, Section C.) 8.88.2.4. Must have a demand code in pos 44. The demand code is very important. It is the customer's means of obtaining programmed support, and of controlling their FMSO I stock levels and their FMSO I case value. 8.88.3. SAMIS Requisition Processing. Upon receipt of the customer's FMSO II case requisitions, SAMIS performs the following actions: 8.88.3.1. The requisition format is checked for accuracy. 8.88.3.2. FMSO II case dollars are committed for the standard price, or repair price for H-coded requisitions. 8.88.3.3. Recurring requisitions for ineligible FMSO I items are recoded as nonrecurring (N in pos 44). 8.88.3.4. Requisitions with a Blank demand code (Pos 44) are recoded as nonrecurring (N in pos 44). 8.88.3.5. The requisitions are assigned a programmed or nonprogrammed code. This code applies to the requisitions throughout their lives. See attachment 8G10 for an explanation of the codes used in SAMIS products. In the A41 referral order to the Source of Supply (SOS), and in the AE- BU/BW status the customer country, a 1 indicates programmed, a 2 indicates nonprogrammed. In D035 products, the program code is called the management code. 8.88.3.5.1. For expense items (ERRC N and P), SAMIS codes recurring (R in pos 44) requisitions for eligible FMSO I items as programmed. Nonrecurring requisitions are coded nonprogrammed. 8.88.3.5.2. For Investment Items (ERRC C and T), SAMIS assigns the programmed, nonprogrammed code as follows: 8.88.3.5.2.1. If the requisition has a recurring demand code (R in pos 44), SAMIS will code the requisition programmed within available worldwide Eligible-to-be Programmed Quantity (EPQ). If the requisition quantity is less than or equal to the EPQ, it is coded programmed; if it is greater than the EPQ, it is coded nonprogrammed. A consistent and steady demand pattern by the country will increase the number of requisitions coded programmed. SAMIS will not split a requisition and code part programmed and part nonprogrammed. 8.88.3.5.2.2. If a customer participates in CLSSA for just selected NSNs, SAMIS will code recurring requisitions for the selected NSNs as programmed within the available EPQ. Recurring requisitions for nonselected NSNs are recoded as nonrecurring, and therefore, nonprogrammed. 8.88.3.5.2.3. All repair and replace (H-coded) requisitions processed on FMSO II cases will be coded as recurring demand, will be coded programmed within the available Worldwide EPQ, and will be used to compute FMSO I repair stock levels. H-coded requisitions processed on Maintenance M Cases are considered nonrecurring, nonprogrammed, and are not used to compute FMSO I repair stock levels.

8.88.3.5.2.4. Nonrecurring (N in pos 44) requisitions will be automatically coded nonprogrammed. All requisitions that process on other than a FMSO II case are considered nonrecurring and nonprogrammed. 8.88.3.5.2.5. SAMIS maintains the FMSO I SLQs using the I&S master. Requisitions for I&S family members will be coded programmed or nonprogrammed based on the worldwide EPQ for the master NSN. 8.88.3.6. The requisitions are then passed to the source of supply. 8.88.3.7. Recurring FMSO II case requisitions are recorded in a SAMIS demand history file for the purpose of determining the AMD, the SLQ, and the FMSO I case value. (The demand history file is shown in the CLSSA Stock Level Item Query Report.) 8.88.4. D035/IM Requisition Processing: 8.88.4.1. Items are shipped from stock, or are placed on order for the country. The decision to ship from stock depends on the number of assets available, the control level and support level, the priority of the requisition, and whether or not the requisition is programmed. 8.88.4.2. Programmed requisitions: 8.88.4.2.1. With priorities 9-15 are eligible to be supported from stock down to the support level. 8.88.4.2.2. With priorities 4-8 are eligible to be supported from stock down to the critical support level. 8.88.4.2.3. With priorities 1-3 and programmed NMCS requisitions are eligible to be filled from stock down to the zero stock level. 8.88.4.2.4. Backordered programmed requisitions are to be released for shipment based on UMMIPS as assets are received. Attachment 8G11 is a graphic description of this process. 8.88.4.2.5. Support for programmed requisitions using stocks under IM control (on-hand, due-in-fromprocurement, due-in-from-maintenance) is preferred. If this is not possible, new procurement by the IM, or support via the Part And Repair Ordering Systems (PROS) contractor is an option. Programmed requisitions and Repair and Replace (H-coded) requisitions may not be sent to PROS without country approval since they prefer AFMC support, and may not provide this approval. 8.88.4.3. Nonprogrammed Requisitions: All non-programmed requisitions will be automatically processed by D035A until the asset position reaches the control level. When the asset position is below the control level, nonprogrammed requisitions will be backordered by D035A and output to the IM for review. 8.88.4.3.1. Usually, shipments from stock below the control level will be made only when support for programmed requirements (USG and CLSSA) will not be affected. Shipment of nonprogrammed requisitions from stock from below the control level is accepted by DoD as a valid means of support, if such issues do not affect support of US forces and FMS programmed requisitions. 8.88.4.3.2. The decision to fill nonprogrammed requisitions from stock must be made with care. To emphasize this, approval from the first level supervisor must be obtained before filling nonprogrammed FMS requisitions using assets below the control level. 8.88.4.4. If the IM determines that an FMS nonprogrammed non-h-coded requisition cannot be supported from available stock, action must be taken to make sure support is available within procurement lead-time. Three options are available: 8.88.4.4.1. The item may be placed on contract for direct delivery. Direct Cite (4F) funds will be used. 8.88.4.4.2. The item may be placed on backorder if enough assets are on order, or due-in from repair to meet the requirement. If not, new procurement with 4F funds should be used. Backordered requisitions will be given a nonprogrammed suspense date (NPSD). The NPSD assigned by the IM should be a realistic estimate of availability, not necessarily a restatement of the lead-time. If stock becomes available before the expiration of the NPSD, and the asset position goes above the control level, release-for-shipment will be made. If not filled by the expiration of the NPSD, the requisition will be treated as programmed and filled based on priority. 8.88.4.4.3. The requisition may be routed to PROS. 8.88.4.5. D035A automatically assigns a 90 day NPSD to nonprogrammed repair and replace (H-coded) requisition backorders. New procurement with FMS 4F funds is not authorized for repair and replace requisitions. 8.88.4.6. FMS Nonprogrammed, Non-H-coded Requisitions with NU Fund Codes. 8.88.4.6.1. Normally nonprogrammed, Non-H-coded requisitions will have a 4F fund-code and processing is as described above. 8.88.4.6.2. Nonprogrammed, Non-H-coded requisitions may also have an NU fund code. An NU fund code in a nonprogrammed, non-H-coded requisition indicates that SAMIS used the requisition to clear customer CLSSA

liability for the requisition quantity. The NU means that at one time there was a CLSSA stock level for this quantity, and assets may have been bought by the IM to support the requirement. As a result, the IM should examine their asset-to-requirements position and consider supporting the requisition with on-hand/on-order stock, or from repair. If on-hand/on-order stocks and due-in-from-repair are insufficient to meet projected future needs, the IM may change the fund code to 4F and place the requirement on contract, or route it to PROS. 8.88.4.7. Attachment 8G12 is an IM Desk Guide that describes how to identify an FMS requisition and how to support an FMS requisition. Attachment 8G13 is a description of the different types of FMS requisitions. Attachment 8G14 is a description of the fund codes used on FMS requisitions. 8.88.5. Amended shipping instructions as described in Chapter 10, Part 1, Volume III may be used to support FMS backorders. 8.88.6. Approved suitable substitutes will be provided through the Interchangeability and Substitution (I&S) program. 8.88.7. Programmed requisitions are subject to maximum-release-quantity edits. 8.88.8. FMSO II Costs include: 8.88.8.1. The cost of the materiel shipped. 8.88.8.2. A 2.5% administrative charge. This fee funds DoD costs involved in negotiating, implementing, and managing the case. 8.88.8.3. For non-stock-fund shipments, the Logistics Support Charge (3.1%); Packing, Crating and Handling (PC&H) charge (3.5%); and Inland CONUS Transportation charge (3.75%) are applied when applicable. 8.88.9. Depot shipments of stock-fund items and shipment of items from stock-fund contracts are considered stock-fund sales. Stock-fund sales help the ALCs meet their sales goals and their unit cost targets. FMS requisitions placed on direct cite (4F) procurement or routed to PROS are not stock-fund sales. 8.89. The Quality of Storage, Maintenance, and Modifications. 8.89.1. The quality of items furnished by the DoD to the CLSSA customer will be the same in all respects to that furnished to USAF. Items identified by the FMS customer on the FMSO I, will be stored, maintained or modified, as the case may be, in the same way as identical items for the USAF. USAF isn't required to modify items previously shipped; however, the FMS customer may order modification kits/materiel in accordance with FMS procedures. If the FMS customer doesn't want to buy modifications when such modifications are determined to be necessary by USAF, the FMS customer will withdraw the undelivered quantity of the items affected, and USAF will cease to have responsibility for these items and their support. (The term undelivered quantity means the quantity that the USAF has on-hand and on-order for the purchaser according to the CLSSA agreement.) 8.90. CLSSA Funding. 8.90.1. FMSO I: 8.90.1.1. The FMSO I case is divided into two parts: Part A, the on-hand portion and Part B, the on-order dependable undertaking which provides the OA necessary to award the contracts needed to support the CLSSA customer through the administrative and procurement lead times. 8.90.1.1.1. Cash paid on acceptance of the FMSO I is equal to 5/17 of the total case value. As the case increases, the 5/17 investment increases. This is a refundable charge. 8.90.1.1.2. A nonrefundable administrative surcharge of five percent will be charged on the 5/17 portion of the FMSO I case, and on any amendments/modifications which increase the value of the case. No administrative surcharge will be charged on the 12/17 portion of the FMSO I case. 8.90.1.2. The payment for the on-order portion isn't usually collected. However, the FMS customer is financially liable for all FMSO I materiel when the stock level case is terminated or reduced if the materiel isn't needed by the USAF or another FMS customer. 8.90.1.3. Increases or decreases in the FMSO I stock level requirements may need additional funds from, or a refund to a CLSSA customer. The dollar value increase or decrease will be shown on an LOA Amendment or Modification prepared by the AFSAC case manager. 8.90.2. FMSO II: 8.90.2.1. The FMSO II LOA will include the estimated total materiel cost and the following additional charges: 8.90.2.1.1. A prescribed percentage of the materiel value for packing, crating, and handling for nonstock fund shipments from DoD inventory. Currently this is three and one half percent. 8.90.2.1.2. An appropriate transportation charge for nonstock-fund shipments. 8.90.2.1.3. A prescribed administrative charge. Currently this is 2.5 percent.

8.90.2.2. The customer will make an initial deposit with the Defense Finance and Accounting Service (DFAS) in cash for the amount stated on the face of the FMSO II LOA. Quarterly payments will be made to DFAS by the FMS customer in accordance with the LOA payment schedule. 8.91. Termination. 8.91.1. Termination is the cancellation of the CLSSA program in its entirety or the elimination of one or more weapons or other major systems from the CLSSA program. 8.91.2. Upon issuing or receiving notice of a request to end CLSSA support, the AFSAC case manager must determine FMSO I customer liability to the USAF. The AFSAC case manager will arrange for the FMSO I items to be placed in the Termination File. Normal Termination File and Drawdown Requisition processing will then occur. The Termination File processing time period can be shortened, if necessary, to expedite closure. 8.91.3. When the Termination File process is complete, the case manager will prepare an LOA Modification to reduce the FMSO I case by an appropriate amount. When the case is reduced, the corresponding 5/17th investment can then be returned to the country. The case manager must send a letter to DFAS-AIA/DY to tell them to process the appropriate forms to cause the return of the 5/17th cash. 8.92. Thru 8.100. (Unused.) Section 8HPUBLICATIONS FOR SECURITY ASSISTANCE (SA) CUSTOMERS UNDER THE FMS PROGRAM 8.101. Purpose. This section sets procedures for the negotiation, implementation, and management of follow on support for publications and forms needed by FMS customers under the FMS program. It gives the responsibilities of HQ Air Force, AFMC, the AFSAC, Air Education Training Command (AETC), Air University (AU), and the Air Force element of the overseas security assistance organization (SAO) or other US government representatives authorized to act for security assistance customers. 8.102. Scope. 8.102.1. These procedures cover the publications and forms provided to FMS customers by the Department of the Air Force under the FMS program. Initial publications are usually provided to the FMS customer under a system sale. These instructions are for follow on support. 8.102.2. The following publications are excluded from the procedures in this section: 8.102.2.1. Items in the USAF inventory at standard prices under supplies or appropriation accounts. 8.102.2.2. Standard documents in the DoD Index of Specifications and Standards. 8.102.2.3. Military standards and specifications. 8.102.2.4. Welfare and morale publications. 8.102.2.5. Commercial books and periodicals, for example: medical books, fiction and nonfiction books, etc. 8.102.2.6. Publications managed and issued by operational major commands. 8.102.3. The FLOs can use the DD Form 1149, Requisition and Invoice/Shipping Document, to order authorized USAF publications from the Air Force Security Assistance Publications office. The FLOs will use the instructions in paragraph 8.107.3 in order to fill out the DD Form 1149. The FLOs will order only those publications that are needed in the operation of their business. 8.103. Authorized Publications, by Category, Focal Point, Supply Source, and Referenced Management Paragraph. Attachment 1 lists by category the publications covered by these procedures which are authorized for FMS customers. The control activity for requirements, the source of supply, and the references in this section are included. 8.104. Responsibilities. 8.104.1. The SAF/IA will: 8.104.1.1. Set policy guidance for FMS publications in AFMAN 16-101. 8.104.1.2. Coordinate all disclosure policy and issues with SAF/IAPD. 8.104.2. SAF/IAPD will: 8.104.2.1. Delegate release authority to AFSAC/IA (FDPO) for publications. 8.104.2.2. Process requests from AFSAC/IA (FDPO) for final release determination, when releasability of a document exceeds AFSAC/IA (FDPO) review authority. 8.104.2.3. Route requests from embassies or SAOs to the proper request receiving activity in attachment 8H1. 8.104.3. AFSAC/IA (FDPO): 8.104.3.1. Is the release authority for all publications and documents managed by HQ AFMC-owned Air Force activities.

8.104.3.2. Delegates release authority to appropriate field Foreign Disclosure Offices (FDO). 8.104.4. AFMC will: 8.104.4.1. Provide authorized publications stocked and issued by its activities for approved and funded FMS programs. 8.104.4.2. Process requests for publication distribution office (PDO) assignments to ship standard publications. 8.104.4.3. Set up and/or implement policy/procedure to process publications. 8.104.5. AETC will: 8.104.5.1. Get the international program directive from the AFSAC case manager; and ensure items are delivery reported. 8.104.5.2. Provide authorized training publications stocked and issued by its activities for an approved and funded FMS program. 8.104.5.3. Tell customer when training documents are not releasable. 8.104.5.4. Give program management and reporting requirements for the FMS training program. 8.104.6. AU will: 8.104.6.1. Provide authorized professional military education (PME) correspondence courses for approved and funded SA requirements in accordance with procedures outlined in AFI 36-2301, Professional Military Education. 8.104.6.2. Tell the customer and the AFSAC case manager when courses are not releasable. 8.104.6.3. Provide delivery reporting for course materials supplied to the FMS customer. 8.104.7. AFSAC will: 8.104.7.1. Get requests for engineering drawings and related publications from FMS customers. 8.104.7.2. Act as point of contact and control for categories of publications shown in attachment 8H1. 8.104.7.3. Process authorized request for data to the source of supply. 8.104.7.4. Make sure an approved and funded FMS program exists and authorized foreign disclosure approval has been granted before approving requests for publications or engineering drawings. 8.104.7.5. Process billing documents with supporting data, and provide them to DFAS for processing. 8.104.7.6. Tell the customer or SAO when requests are not releasable. 8.104.7.7. Negotiate all P cases with FMS customers. 8.104.7.8. Write and implement all P cases for FMS customer. 8.104.7.9. Start and/or process all LOAD requests for publication requirements to the source of supply when necessary. 8.104.8. The Air Force element of the SAO will: 8.104.8.1. Act as the Air Force approving authority for technical data package requests. 8.104.8.2. Send LOAD requests, when applicable, to the proper major command or agency. 8.104.8.3. Assure the customer's PDO has secure facilities and control procedures to properly safeguard classified and other sensitive data. 8.104.8.4. Tell FMS customer when requests are not releasable. 8.105. Negotiation Procedures. 8.105.1. A separate case/case line is necessary for each category of publication as shown in attachment 8H1, except as follows: 8.105.1.1. Category F is included in a technical order case if no separate case is asked for by the customer. 8.105.1.2. Category G is processed under the category for unclassified. 8.105.2. The USAF element of the SAO or other authorized approving official will: 8.105.2.1. Send a LOR to AFSAC Wright-Patterson AFB Ohio 45433, to set up the appropriate case. 8.105.3. The AFSAC case manager will: 8.105.3.1. Get the LOR from the customer. 8.105.3.2. Ask for LOAD from the source when necessary. 8.105.3.3. Get the LOAD response. 8.105.3.4. Prepare the proper P case LOA. 8.105.3.5. Process the LOA. 8.106. Implementation Procedures. 8.106.1. The AFSAC country manager will: 8.106.1.1. Get the signed letter of acceptance from the customer. 8.106.2. The AFSAC Publications Case Manager will:

8.106.2.1. Prepare a international program directive to the control activity after the case and OA are input to SAMIS for Technical Order (TO) and TCG CSTO Cases.. 8.106.2.2. Get OA from DFAS Denver. 8.106.2.3. Review for accuracy and completeness. 8.106.2.4. Input the case into SAMIS. 8.106.3. The source of supply will: 8.106.3.1. Process requests and make shipment by traceable means in accordance with paragraph 8.111 and DoDM 5105.38-M (SAMM). 8.106.3.2. Submit billing documents as explained in this section, including the date, mode, and document control number of the shipment. 8.107. Submission of Customer Requests. 8.107.1. All requests for LOAD studies are sent to AFSAC. The following procedures apply to submitting requisitions and setting up automatic distribution requirements. 8.107.2. FMS customer requests are submitted based on the type of publication requirement (see attachment 8H2). The request forms are prepared in accordance with the following instruction. All requisitions must have the 14digit MILSTRIP requisition number. Letters of justification are sent with requests for automatic distribution of certain parts of AFMAN 23-110 (see attachment 8H2). 8.107.3. The FMS customer prepares requisitions on DD Form 1149 as follows. 8.107.3.1. The FMS customer sends the DD Form 1149 to the control activity listed in attachment 8H1. When automatic distribution is required, then the words Request for automatic distribution should be entered on the DD 1149. 8.107.3.2. Block 1. Enter the supply source shown in attachment 8H1. 8.107.3.3. Block 2. Enter the customer's PDO account number (clear text address) and the continental United States (CONUS) freight forwarder address. 8.107.3.4. Block 3. Enter the in-country mark for address. 8.107.3.5. Block 4. Enter the proper case and line. 8.107.3.6. Block 4b. Enter the Publication Number and Title. 8.107.3.7. Block 4c. Enter the Unit of Issue. 8.107.3.8. Block 4d. Enter the Quantity. 8.107.3.9. Block 4h. Enter the Unit Cost, if known. If unknown, leave blank. 8.107.3.10. Block 4I. Enter the total Cost, if known. If unknown, leave blank. 8.107.3.11. Block 5. Enter the date prepared. 8.107.3.12. Block 6. Enter the 14-digit country MILSTRIP requisition number. 8.107.3.13. Block 10. The signature and title of an authorized country official is acceptable. 8.107.3.14. Blocks 11 through 20 are not used by the requisitioner. 8.107.4. The FMS customer submits requirements for USAF technical orders on AFTO Form 187, Technical Order Publications Request, or AFTO Form 276, Special Requisition for Air Force Technical Order/CPIN, in accordance with instruction in TO 00-5-19. AFTO Form 187 also is used to set up automatic distribution of changes, revisions and supplements to TOs. To delete, increase, or decrease requirements, a new AFTO Form 187 is submitted. AFTO Form 187 does not need the signature of the Air Force approving official (SAO or other designated agency) and may be sent by the International Logistics Communications System using the procedures of TO 00-5-19, section 13. 8.108. Management Procedures. 8.108.1. Category A: 8.108.1.1. Requisitioning of AFMAN 23-110. AFMAN 23-110 includes procedures for requesting or receiving logistics support through the USAF FMS program. FMS customers may requisition new or additional copies of the entire AFMAN 23-110 on CD-ROM by sending a DD Form 1149 to AFSAC. AFSAC reviews the requisition for accuracy and checks that the FMS case is valid. If the case and the ordering period are valid, the DD Form 1149 is processed. 8.108.1.2. Automatic Distribution of AFMAN 23-110. The FMS customer asks for automatic distribution or changes on the DD 1149 sent to AFSAC. See attachment 8H2 for parts that must have a separate letter of justification. If the case and the ordering period are valid on a current P case for standard publications, the AFSAC case manager will approve the requirement. For each amendment, change or addition, AFPDC Baltimore

MD will make distribution. The DD Form 1149 with a 14-digit country MILSTRIP document number is sent to the AFSAC case manager who will verify the cost and send it to DFAS for billing action. 8.108.1.2. Other Standard Publications and Forms (attachment 8H1). 8.108.1.2.1. The customer first checks the AFPDC Baltimore MD website (http://afpubs.hq.af.mil) for online availability as a downloadable document, free of charge. The customer must acquire the document online if it is available online. If the document is not available online, the customer sends requisitions and requirements on DD Form 1149 to AFSAC in accordance with attachment 8H2. 8.108.1.2.2. The AFSAC case manager will get customer requirements, review for accuracy and validity, and make sure funds are available. If enough funds are available, and the request is valid, the requirement is sent to the Air Force Publication Distribution Office (AFPDO) or other supply source for positive action. 8.108.1.2.3. The AFSAC case manager will get billing data from AFDPO or any other supply source, ensure money is committed in SAMIS, and send it to DFAS for reimbursement. 8.108.1.3. USAF stocklists, federal supply catalog and related cataloging publications. 8.108.1.3.1. The FMS customer will send requirements to AFSAC in accordance with attachment 8H2. 8.108.1.3.2. AFSAC will get FMS customer requirements, review for accuracy and validity and make sure enough funds are available. If funds are available and the request is valid, send the requirement to HQ AFMC/LGISA for action. 8.108.1.4. Decals: 8.108.1.4.1. The FMS customer will send requirements to AFSAC in accordance with attachment 8H2. Automatic distribution of decals is not authorized. Each request must have the technical order, figure and index, item identification and description, end-item and prime ALC. If the decal cannot be identified to a technical order, or is not standard to the USAF, a sample of the decal or a detailed drawing must be attached to the DD Form 1149. 8.108.1.4.2. AFSAC will get the FMS customer's request, review for accuracy and validity, and make sure enough funds are available. If funds are available and the request is valid, the case manager will clearly mark the requisition FMS on all copies and send it to the air base group source of supply at the managing ALC for the technical order. 8.108.1.4.3. The source of supply will process the requirement to the customer by traceable means and annotate the DD Form 1149 with the number and unit cost of the decals shipped, total cost, and the date, mode, and document control number of the shipment. Actual or actual average costs, based on the unit of issue (each, package, kit) will be used as the basis for the total cost, plus a processing charge of $3.20 for each DD Form 1149 or line item request. 8.108.1.4.4. When the TO reference is a country standard TO (CSTO) and the item identification and description do not match the corresponding USAF TO reference, the requisition will be processed to the applicable Technical Coordination Group (TCG) or system program director (SPD) at the ALC to provide the proper cross reference for the decal. 8.108.1.4.5. The ALC source of supply will review the billing document (DD Form 1149) for completeness and accuracy, and return two copies to the AFSAC case manager for billing action. 8.108.1.4.6. The AFSAC case manager will get the billing documents, clear the suspense file, and send them to DFAS for delivery reporting. 8.108.1.4.7. DFAS will get the billing document and process the manual delivery. 8.108.1.5. Table of Allowance (TA). 8.108.1.5.1. The FMS customer will send requirements to AFSAC in accordance with attachment 8H2. 8.108.1.5.2. AFSAC will get the FMS customer request, review for accuracy and validity and make sure enough funds are available. If a funded case does not exist, or sufficient case funds are not available, the AFSAC Command Country Manager is told, and the requirement placed in suspense until funds are available. If funds are available and the request is valid, obtain AFSAC/IAD release approval and send the requirement to the AFPDO for action. 8.108.2. Category B: 8.108.2.1. Automated Data Products. 8.108.2.1.1. The FMS customer will send requests to AFSAC by letter or message in accordance with attachment 8H2. 8.108.2.1.2. AFSAC will get the request, make sure funds are available, and take action to supply the requirement. Pricing table is listed below:

1-100 pages 101-200 pages 201-300 pages 301-400 pages 401-500 pages over 500 pages

$5.00 11.00 19.00 27.00 34.00 34.00 plus $7.00 per 100 pages over 500

8.108.2.1.3. Additional copies $.03 per page. 8.108.2.2. Microfiche Listing. 8.108.2.2.1. First Copy. 101-200 frames 201-300 frames 301-400 frames 401-500 frames over 500 frames 11.00 19.00 27.00 34.00 34.00 plus $7.00 per 100 frames over 500

8.108.2.2.2. Additional copies $.05 per fiche plate. NOTE: There are 270 frames for a full microfiche plate. 8.108.2.3. 9-Track Tape 6250 BPI. 101-200 feet 201-300 feet 301-400 feet 401-500 feet over 500 feet 11.00 19.00 27.00 34.00 34.00 plus $7.00 per 100 feet over 500

NOTE: There is a minimum charge of $15.00 for a tape. 8.108.2.4. After shipment of the requested publication, the AFSAC case manager will determine the cost of products shipped and send the bill to DFAS for delivery reporting. 8.108.2.5. DFAS will get the billing document and process a manual delivery. 8.108.3. Category C: 8.108.3.1. TO Publications Cases. TOs are provided in accordance with policies in TO 00-5-19, AFI 16-201, and AFMAN 16-101. The FDO will provide release authority for all technical orders and follow on changes, supplements, and revisions. Initial requirements for technical orders, including country peculiar requirements, are usually provided to FMS customers under a systems sales case. These instructions are for follow on requirements. 8.108.3.1.1. AFSAC will issue the IPD for follow on TO support to OC-ALC/TILU. 8.108.3.1.2. OC-ALC/TILU will: 8.108.3.1.2.1. Implement the TO case in the Security Assistance TO Data System (SATODS) and assign technical order distribution office (TODO) codes for unclassified and classified TO requirements. If the case is a replacement case for existing TO requirements, the expired case designator and case value is replaced with the new case designator and case value. TODO codes and existing initial distribution requirements aren't affected. Follow on support of these requirements is subject to continuous approval of the FDPO. 8.108.3.1.2.2. Provide new FMS customers at no charge a start up kit of one copy of XX0-1-CD-1, USAF Technical Order Catalog for FMS; 00-1-CD-1, Methods and Procedures TOs; and several copies of AFTO Forms 187, Technical Order Publications Request. This kit will provide instructions for ordering TOs, time compliance technical orders (TCTO), and CPINs. 8.108.3.1.2.3. Process the FMS customer's request for TO requirements in security assistance technical order data system (SATODS) and provide the FMS customer's AFTO Forms 215, Notification, and SATODS letters for status of backorders, AFTO Form 187 request errors, and/or foreign disclosure review denials.

8.108.3.1.2.4. Give, on a monthly basis, detailed billing data (SATODS W002-A14-M09-PS) to HQ AELC/LMSC/SBFA for delivery reporting on the FMS Detailed Delivery Report and give on a monthly basis detailed billing data (SATODS W002A-12-M09-FS) to DFAS Field Site for items not reported to HQ AFMC for direct billing action on cases managed by other commands or services. 8.108.3.1.2.5. Send to each respective customers country the following SATODS reports on a monthly basis: 8.108.3.1.2.5.1. Monthly FMS History Report (W002-CO1-M09-PA). 8.108.3.1.2.5.2. Monthly FMS Billing Suspense (W002-CO2-M09-PA). 8.108.3.1.2.5.3. FDO Release Review List (W002-CO3-M09-PS). 8.108.3.1.2.5.4. Backordered TOs (W002-CO7-M09-PA). 8.108.3.1.2.5.5. Unpublished TOs with Established ID (W002-C15-M09-PS). 8.108.3.1.2.5.6. Case Expiration/Funds Utilization (W002-CO6-M09-FS). 8.108.3.1.2.6. Prepare and send a letter to AFSAC informing them that all SATODS billing actions have been completed. 8.108.3.2. Requests from contractors to buy USAF publications for resale or release to a foreign customer will be processed in accordance with TO 00-5-19. This will make sure nonrecurring costs are recouped as required by DoDI 2140.2 and DoD 7000.14-R, Vol. 15. 8.108.3.3. Interim Technical Orders (ITO). 8.108.3.3.1. ITO Definition. An ITO is a message or letter sent by a system program manager/item management specialist to all users of the system/ item (including all FMS customers) to tell them of a condition which is hazardous, or will reduce operational efficiency, and to tell them of what to do (such as inspection, updating change, or modification per DoDI 5000-2_AFSUPI). If the ITO is an interim TCTO, then according to TO 00-519, countries are asked if AFSC/AFMC assistance is required pertaining to the TCTO. An ITO is labeled as one of the following: 8.108.3.3.1.1. Interim Time Compliance Technical Order (ITCTO) For immediate action, urgent action, or for record. A TCTO (interim or formal) is the Air Force-authorized way for directing and providing instructions for modifying Air Force equipment and performing one-time inspection (TO 00-5-15, AF TCTO System). These are released to FMS customers in accordance with TO 00-5-19 and DODI 5000-2 AFSUPI. 8.108.3.3.1.2. Interim Supplement to a Basic TO Safety or operational. 8.108.3.3.2. Formal TCTO and Supplement Distribution. Each ITO is replaced by a formal TCTO or a formal supplement within the times stated in TO 00-5-19. These formal printed TCTOs and supplements (with diagrams, full details, etc.) are issued to the FMS customers having an FMS technical publications P case and who have set up a TO distribution code account with OC-ALC/TILU (see TO 00-5-19) and: 8.108.3.3.2.1. For TCTOs and TCTO Supplements. The FMS customer must be on initial distribution for the TCTO series for the weapon system, engine, ground support equipment item, or munition as listed in the TO index. A TCTO series is preceded by an S symbol, and is titled TCTO SERIES. 8.108.3.3.2.2. For TO Supplements. The FMS customer must be on initial distribution for the basic TO. 8.108.3.3.3. The FMS customers must, upon receipt of an ITO: 8.108.3.3.3.1. Make sure they are on initial distribution for both the basic TO referred to in the ITO and for the system/item TCTOs SERIES. 8.108.3.3.3.2. Requisition kits, using the TCTO instructions and proper modification case, if needed to do the inspection/modification. If a modification case is not set up, but kits are needed, send a request for letter of acceptance to set up a modification case for purchase of the kits. 8.108.3.3.3.3. Do the work required by an ITO, hire a contractor, or send a request for a letter of acceptance for the work to be done or contracted by the USAF, if desired. 8.108.4. Category D. 8.108.4.1. Engineering Drawings and Related Engineering Documents. 8.108.4.1.1. AFSAC will act as the central point of contact and control for supporting FMS customer requests for engineering drawings. 8.108.4.1.2. The FMS customer will send requisitions and automatic distribution requirements on a DD Form 1149 with a letter of justification attached. The customer sends requests to AFSAC. (see attachment 8H1). 8.108.4.1.3. AFSAC will review the requirement for validity and accuracy, verify a funded case exists, and determine the ALC engineering drawing support center (EDSC) to support the request for the engineering drawings. If a funded case does not exist, or sufficient case funds are not available, the AFSAC Command Country

Manager is told, and the requirement placed in suspense until funds are available. All other requests are sent to the ALC EDSC by cover letter. The cover letter will instruct the EDSC to provide a cost estimate by telephone before processing the request. The AFSAC case manager verifies funds are available and reserves the amount. 8.108.4.1.4. The EDSC will identify all the data to the request (including all details when specified) and determine a cost estimate (see attachment 8H3). The AFSAC case manager is told of the cost estimate by telephone. If funds are available the EDSC office will send the request to the FDO for a disclosure review. Data approved for release by the FDPO is packaged by the EDSC and shipped by traceable means to the FMS customer address on the request. The requisition form is annotated to show the date and method of shipment, the shipping document control number, and the actual cost, or the reason for denying release of the data. Two copies of the annotated form are sent to the AFSAC case manager for billing action. 8.108.4.1.5. The EDSC, before making any automatic distribution of data, will contact the AFSAC case manager by telephone to make sure that funds are available. Data that has been approved for release by the FDPOs is packaged by the EDSC and shipped by traceable means to the FMS customer address on the request. The requisition form is annotated to show the date and method of shipment, the shipping document control number, and the actual cost, or the reason for denying release of the data. Two copies of the annotated form are sent to the AFSAC case manager for billing action. 8.108.4.1.6. The AFSAC case manager will make appropriate adjustments to the case balance, keep a record copy of the requisition form and send the original to DFAS for billing. If the data is denied for release to a customer, the AFSAC case manager will tell the Command Country Manager of the denial and the reason for denial. 8.108.4.2. Technical Documents. 8.108.4.2.1. Definition. A technical document is a document with technical information, such as test documentation, process layouts, performance data, and equipment specifications for use in making technical evaluations. This data is not used in the general maintenance or operation of equipment and is not technical orders or engineering drawings. Technical documents governed by this procedure are those kept by the office having technical responsibility for a weapon system or major end-item. 8.108.4.2.2. The customer or its embassy can ask for technical documents on a DD Form 1149 sent to AFSAC. These documents are charged to the customer's case for engineering drawing support. When requisitions are to be shipped directly to an embassy, the embassy's address will be listed in block 3 of the DD Form 1149, instead of the Mark-For address of the customer's freight forwarder. 8.108.4.2.3. AFSAC will review the request for validity and accuracy and verify a funded case exists. If a funded case does not exist, or the case does not have enough money on it, the Command Country Manager is advised and the requirement placed in suspense until funds are available. 8.108.4.2.4. When a funded case exists, the AFSAC case manager determines the management ALC and sends the requisition to the ALC-FDO by cover letter. The cover letter will tell the ALC to provide a cost estimate by telephone before shipping the documents. 8.108.4.2.5. The ALC-FDO determines the technical area responsible for the equipment. The requisition and cover letter will be sent to the responsible office along with a request that the documents and a recommendation of releasability be sent to the FDO. The technician will choose the appropriate publications, determine the cost of the documents, and call the AFSAC case manager to make sure case funds are available. After its been verified that adequate funds are available, the documents will be sent to the FDO for a release decision. 8.108.4.2.6. The FDPO will return the documents to the technical office with the approval or disapproval for release to the customer annotated on the DD Form 1149. The technical office will package and ship releasable documents to the address listed in block 3 of the 1149 to show the date and method of shipment, the shipping document control number, and the actual cost for the documents. If release is denied, a reason for denial will be entered. Two copies of the completed DD Form 1149 are sent to the AFSAC case manager for billing, and one copy returned to the ALC FDPO. 8.108.5. Category E. 8.108.5.1. Training Materiel. 8.108.5.1.1. AFSAC will implement P cases for the following training aids and publications directly to HQ AETC/LGTI, Randolph AFB Texas 78148. 8.108.5.1.1.1. Aircraft training publications. 8.108.5.1.1.2. Standard AETC publications and forms if not available on the AFPDC Baltimore MD web site, http://afpubs.hq.af.mil. If the requirement is available online the customer must download it here free of charge.

8.108.5.1.1.3. Flying, training publications and training aids. 8.108.5.1.1.4. Technical training publications and training aids. 8.108.5.1.1.5. Navigation training publications and training aids. 8.108.5.1.1.6. Survival training publications and training aids. 8.108.5.1.1.7. Training equipment and supplies. 8.108.5.1.2. The customer will send all requests for training material to HQ AETC/LGTI 8.108.5.1.3. HQ AETC/LGTI will act as the focal point within AETC to determine releasability of the material and send approved requirements to the office of responsibility for supply action. 8.108.5.1.4. HQ AETC/LGTI will tell the customer and AFSAC case manager of all requested material that is not releasable. 8.108.5.1.5. AETC will make sure supply action is taken within the authorized case value. 8.108.5.1.6. AETC sends billing documents with shipping information (includes the transportation bill code) to DFAS and a costed copy of the DD Form 1149 to the AFSAC case manager. 8.108.5.1.7. DFAS will get billing data for delivery processing. 8.108.5.2. Professional Military Education (PME) Correspondence Courses. 8.108.5.2.1. The customer will send all requests with appropriate justification for correspondence courses in accordance with AFI 36-2301. 8.108.5.2.2. AFSAT/TOA will send approval notification to AFSAC to apply charges against the applicable FMS publications case. 8.108.5.2.3. The source of supply will ship the materiel to the FMS customer and give complete shipping information (include transportation bill code) to DFAS for billing and provide a costed-copy of the DD Form 1149 to the AFSAC case manager. 8.108.5.2.4. DFAS will get billing documents for delivery processing. 8.108.5.3. Defense Language Institute Material. 8.108.5.3.1. The customer will send a DD Form 1149 directly to AFSAC with the 14-digit country MILSTRIP requisition numbers in block 6. Items are identified with unit costs in the Defense Language Institute English Language Center (DLIELC) Catalog. 8.108.5.3.2. AFSAC will review the request for accuracy and availability of funds and forward the request to DLIELC program managers for review. Once DLIELC program managers verify that the materiel ordered is valid, AFSAC will forward the request (including cover letter and fund cite) to the DLIELC warehouse. Completed copies of Standard Form 1080, Voucher for Transfers Between Appropriations and/or Funds, and two costed copies of the DD Form 1149 are sent back to the AFSAC case manager. 8.108.6. Category F Joint Technical Coordinating Group for Munitions Effectiveness (JTCG/ME). 8.108.6.1. The AFSAC case manager will implement the case to USAMSAA/AMXSY-J for management. 8.108.6.2. The FMS customers will send requirements to USAMSAA/AMXSY-J, 392 Hopkins Road, Aberdeen Proving Ground MD 21005-5071. 8.108.6.3. USAMSAA/AMXSY-J will make a release determination on a document-by-document basis. 8.108.7. Category G. Classified Publications. 8.108.7.1. The process is the same as for unclassified publications in the categories above. 8.108.7.2. SAF/IAPD will delegate release authority to AFSAC/IPD or other authorized FDPO reviewing authorities as appropriate. 8.108.7.3. Packaging, shipment, and document control will be in accordance with AFI 31-401, Information Security Program Management. 8.108.7.4. The authorized FDO reviewing officials will. 8.108.7.4.1. Determine releasability of publications within the authority delegated to them. 8.108.7.4.2. Send requests for classified publications that exceed their release authority to SAF/IAPD for final release approval (see AFMAN 16-101). 8.108.7.5. The appropriate activity for the category of publication will: 8.108.7.5.1. Make sure funds are available on the correct FMS case. 8.108.7.5.2. Process releasable documents in accordance with the criteria for that type or category of publication. 8.108.7.5.3. Get a copy of the receipt for the document and process proper billing data to DFAS. 8.108.7.5.4. DFAS reviews complete shipping information and document receipt and processes delivery.

8.109. Case Closure for Publications. 8.109.1. Ninety days before case expiration, the AFSAC case manager will tell the country manager to request and get approval for a replacement case, or to take necessary action to extend the current case ordering period if funds are available. 8.109.2. The AFSAC case manager will not begin closure on technical order cases until the case manager receives SATODS closure notification from OC-ALC/TILUF. 8.109.3. The AFSAC case manager and/or other control activities to which publication cases are implemented will review closure candidate cases until all requirements are supply complete. When the case is supply-complete, the publications case manager will send a notice of supply and services complete (NSSC) letter to the country, informing it that case closure procedures have been started. 8.110. Pricing for Publications. Attachment 8H3 gives the publications pricing guide. This is an extract of pricing procedures in section 716. DoD 7000.14-R, Vol. 15. For decals, see paragraph 8.108.1.4. 8.111. Packing, Crating, Handling, and Transportation. 8.111.1. An external packing list is placed on the outside of both large and small shipping containers if possible. This packing list should clearly state the contents of each container to avoid the reopening of the container and possible loss of contents. The freight forwarder uses the packing list to identify the material to the FMS customer without opening the containers. An advance notification of shipment letter, with a copy of the packing list and costing information, are sent by the source of supply to the FMS customer and to the freight forwarder. 8.111.2. United Parcel Service (UPS) and other commercial small parcel carriers provide evidence of shipment from the supply source and proof of delivery to the CONUS consignee, and is the first choice for sending small parcel shipments within the CONUS. When exceptional circumstances require the use of United States Parcel Service (USPS), the shipment is certified, registered, or insured to provide a traceable means of shipment. Shipments exceeding the small parcel carrier weight/size limitations are shipped to the freight forwarder on a collect commercial bill of lading. 8.111.3. Suppliers will keep shipping documentation for a minimum period of two years following the shipment 8.111.4. The shipping activity will prepare a second set of the DD Form 1149 for freight forwarder distribution, and send it to the designated freight forwarder by the fastest means, as advance information, the same day or not later than the next scheduled working day after the shipment is made. Entered on the shipping document will be the date of shipment, the UPS or small carrier shipping number, the USPS registration number, or the bill of lading number, and a copy of the bill of lading attached, if applicable. 8.111.5. Transportation policy and procedures for the FMS program are in AFMAN 16-101. 8.111.6. Classified publications or documents will be packaged and shipped in accordance with AFI 31-401. 8.111.7. Instructions for the packing, crating and handling of selected items of supply are in TO 00-85B-3 and TO 00-85-37. 8.112. Thru 8.116. (Unused.) Section 8IREQUIRED AVAILABILITY DATE (RAD) MANAGEMENT PROGRAM 8.117. Policy. The Air Force RAD management program is implemented by the procedures in this section. The RAD is used to help the US Air Force meet its delivery commitments found in the accepted and funded LOA. 8.118. Definition and Application of RADs. 8.118.1. The RAD is a two-position numeric code. It shows the number of months from the date of the requisition that the requested item(s) are needed to be available for release to the FMS customer. NOTE: Numeric codes in number of months do not necessarily mean the corresponding calendar month. Example: If the date on a requisition is June, and the RAD assigned is 10 months, the 10 is not the calendar month of October. It is April of the following year. 8.118.2. The RAD is in RP 63-64 of the DD Form 1348, DoD Single Line Item Requisition System Document (Manual), or 1348M, DoD Single Line Item Requisition System Document (Mechanical), requisition. It is preceded by an alpha code A in column 62. 8.118.3. Changes to a RAD are usually directed by the system program director (SPD) (for activation case) and country/case manager (defined order case) if the activation date or need date changes. The RAD is not necessarily the same as the estimated shipping date (ESD). 8.118.4. The ESD is the date the item(s) is scheduled for shipment to the FMS customer It includes procurement (administrative and production) lead time and other factors affecting production schedules. Changes in the ESD will not result in a RAD change.

8.119. Purpose of a RAD. 8.119.1. RADs show delivery commitments for major weapons systems, end-items, concurrent spares/repair parts, and equipment type items bought under FMS cases and/or grant aid program lines. 8.119.2. RADs show when extra action is needed to improve ESDs (see paragraph 10). 8.119.3. RADs will not be used to delay or suspense shipment of items in long supply. 8.120. Scope. 8.120.1. This section tells who sets up RADs for requisitions supporting initial activation, defined order cases, and grant aid program lines. 8.120.2. This section gives policy and procedural guidance to HQ AFMC, the ALC, and AFSAC organizations responsible for providing logistical support to foreign countries participating in the international logistics program. 8.121. Administrative. 8.121.1. If you find conflicting policy or procedural guidance between this section and other publications, tell AFSAC/IA as soon as possible. State the conflict and include suggested corrective action. 8.121.2. Recommended changes to this section are sent in writing, to AFSAC/IA. Tell why the change is necessary. 8.121.3. All correspondence on RAD adjustments is kept as part of the total case or record control number (RCN) file and retired with the complete file. 8.122. Categories Excluded from RAD Assignment. 8.122.1. FMS. RAD control procedures do not apply to blanket order cases, open end, or cooperative logistics requisitions submitted by the FMS customer. 8.122.2. Military Assistance Program. RAD control procedures do not apply to requisitions sent by the FMS customer for follow on spares and other program lines specifically excluded from RAD control. 8.123. Conditions Impacting RAD Assignments. 8.123.1. The following conditions impact RAD assignments. These conditions are used by all individuals authorized to set up and/or assign RADs. 8.123.1.1. Weapon system activation date. 8.123.1.2. Item is needed before the activation date for training, facilities, delivery support, etc. 8.123.1.3. Item is available from in-country stocks. 8.123.1.4. Customer has asked for a specific delivery date. 8.124. RAD Assignment Responsibilities. 8.124.1. Initial Activation Cases. 8.124.1.1. The SPD is responsible for assigning RADs to all initial activation case requisitions with case designators ''D,'' Q, S, W, or Y. 8.124.1.2. The SPD assigned RAD will be 15 days before the in-country activation date of the aircraft, weapons system, major end-item, etc., as shown in the LOA. Exceptions are, such as when the FMS customer asks for a specific date and the requested date is in the approved LOA or approved by the SAF country director. When this occurs, the requested date is put on the requisition as the RAD. Another exception would be when a partial delivery for spares is provided and the remaining items will be supplied by the next need date. The new RAD will be entered. 8.124.2. Follow-on Support Cases. 8.124.2.1. AFSAC case managers are responsible for assigning RADs to requisitions for A, C, Q, and V cases. These RADs are based on lead times shown in the LOA data (provided by the ALC FMS focal point) unless the FMS customer asks for a specific RAD and it is in the LOA with the agreement of the IMS. 8.124.2.2. Military Assistance. 8.124.2.2.1. The case managers will assign RADs to all requisitions for end-items, initial support equipment, concurrent spares, and spare parts applicable to major end-items and weapon systems. 8.124.2.2.2. These RADs can be set up for 15 days before the in-country activation date of the weapon system or major end-item, or as a country specified RAD when they are in the LOA. 8.125. RAD Review Responsibilities. 8.125.1. The IMS will review the D035A computer systems generated management products to check on the RADs assigned. 8.125.2. The SPD will review SAMIS product PCN: U-W001.-HBB, Open Requisitions: Status Code Interrogation, U-W001.-HBC, Comprehensive Requisition/Custom Commitment Data (RCS: MTC-

IA(AR)8407), or U-W00l.-HCC (product 20), ESD Exceeds RAD Notice, to check the status of requisitioned items. 8.125.3. The case managers will review the SAMIS product PCN: U-W001.-HBB, to check the overall status of items supporting their cases. This product can serve as a basis for starting follow-up actions with the IMS/SPD when it seems a problem has or could develop. 8.126. Management Actions to Meet an Assigned RAD. 8.126.1. IMSs are expected to take extra actions to fill requisitions before RAD expiration. These include: 8.126.1.1. Accelerating manufacture and/or repair when acceleration charges are approved. 8.126.1.2. Amending shipping instructions. 8.126.1.3. Shipping partial quantities from stock. 8.126.1.4. Buying the item on a basic ordering agreement (BOA). 8.126.1.5. Telling an SPD to buy the item on a provisioned item order. 8.126.2. SPDs must monitor assigned weapon system activation programs to make sure IMSs take action to ship at least a partial quantity of all requisitioned initial spares, repair parts, and support equipment before the RAD. 8.127. RAD Management Responsibilities. 8.127.1. The IMS will: 8.127.1.1. Prepare ZFY file maintenance transactions and process them to D035 when a RAD is adjusted by the SPD or case manager. 8.127.1.2. Review computer generated management products to check on RADs assigned/adjusted. 8.127.2. The SPD will: 8.127.2.1. Direct a RAD change if initial activation date is changed. 8.127.2.2. Check computer generated management products to review RADs assigned to requisitions supporting weapon systems activation. 8.127.2.3. Answer requests for help or guidance from the IMS, case manager, or the FMS customer. 8.127.3. AFSAC case managers will: 8.127.3.1. Check computer generated management products for RADs assigned to FMS cases or grant aid program lines they manage. 8.127.3.2. Make follow up actions to the IMS/SPD to make sure every effort is made to meet the RAD. 8.128. RAD AdjustmentsWhy. RADs are adjusted if: 8.128.1. The FMS customer asks for an adjustment in the delivery schedule on a defined order case (SAF approved). 8.128.2. A partial delivery is made to provide short term support, and the balance is not needed in country until a later date to maintain full term support. 8.128.3. The delivery schedule for initial support on an activation program is changed. NOTE: RADs will not be changed just because of a slippage in the estimated shipping date. 8.129. RAD AdjustmentWho. 8.129.1. The SPD or case manager will direct the IMS in maintaining/adjusting RADs. The IMS will prepare file maintenance transactions to adjust RADs with direction from the SPD or case manager. 8.129.2. If there is no IMS, the SPD/case manager sends an AF Form 923 to the ALC international logistics focal point for input. 8.130. RAD AdjustmentHow. 8.130.1. For Items Managed by D035. Upon direction of the SPD or case manager, the IMS will prepare and send to D035, a ZFY file maintenance transaction (chapter 13, part three, volume III). 8.130.2. For Items Not Managed by D035 (Such As Services). RADs are not assigned to these items. Custom commitment controls are usually used. 8.131. Items Controlled by MILSTRIP Procedures. 8.131.1. Customer Notification. When the IMS inputs a ZFY transaction to D035, a B3 MILSTRIP status is produced. It is the official FMS customer notification of an RAD update. Further action is not necessary unless the FMS customer can justify asking for a written notification. The customer must depend on our mechanized status reporting. Written notification will be given by the SPD or the case manager. 8.131.2. Case Manager Notification. After updating the D035 data base, notice of the RAD update is passed through different data systems to SAMIS. SAMIS produces the following RAD status products (refer to the SAMIS online users guide for more information):

8.131.2.1. RAD Change Notice (PCN: U-W001.-HCB). 8.131.2.2. ESD Exceed RAD Notice (PCN: U-W001.HCC). 8.131.2.3. RAD Has Passed (PCN: U-W001.-HCD). NOTE: Case managers will send these products to the SPD when the products are not available through local terminals. 8.131.3. IMS Notification. A D035 system management product is sent monthly to the IMS. This product is AD032.1L2-MB-GBZ, Grant Aid/FMS Backorder Listing (Manager Designator Sequence). It is used for management research and corrective action to solve delinquent delivery schedules for materiel. 8.132. Items Not Controlled by MILSTRIP Procedures (Slippage Will Exceed 90 Days). 8.132.1. IMS actions. 8.132.1.1. IMS actions are necessary when an ESD slippage will exceed 90 days. The IMS must tell the case manager of the slippage in writing. 8.132.1.2. This correspondence will provide a new ESD. 8.132.1.3. This correspondence will also explain why the slippage occurred. Sufficient documentation to support this slippage is included in the letter. Any corrective actions that are being taken, or being considered, are also included. 8.132.2. Case Manager's action. 8.132.2.1. After receiving written notice of the slippage, the case manager will tell (by letter, message, or telephone) the agency/activity that processed the LOA.. That activity will prepare notification of modification of offer and acceptance. 8.132.2.2. The notification of modification of offer and acceptance is sent to the FMS customer Since these slippages are not MILSTRIP military standard requisitioning and issues procedures controlled, this form is official notification to the customer of an ESD slipping more than 90 days. 8.132.2.3. The case manager will keep all correspondence in the case file until the case is completed. After the case is completed, all correspondence is retired as part of the whole case file. 8.133. IMS Computer Support System (D035A). 8.133.1. To help the IMSs meet their RAD assignment responsibilities, D035A is programmed to routinely provide a specialized RAD management product. 8.133.2. Product control number (PCN) A-D035.4L2-MB-GBZ is the D035 system monthly product that gives the status of all ESDs that exceed the RAD or will exceed the RAD in the next 45 days. This product prints in manager designator sequence, as of the 10th of each month. 8.133.3. Copies of PCN A-D035.-1L2-MB-GBZ are sent to the IMS through the division control point. This product is reviewed to identify items needing extra management actions to meet the RAD (paragraph 126). The listing is annotated to show actions to be taken. The original product is kept by the IMS. Copy number one is given to the immediate supervisor. 8.134. SPD and Case Managers' Support System (SAMIS). To help the SPD and the case managers to meet their RAD management responsibilities, SAMIS will provide specialized RAD management reports. These reports are available to the SPD and ALC materiel managers through local SAMIS terminals. When the SPD or case manager directs a RAD change, the ZFY file maintenance data transaction is input to the D035 system by the IMS. 8.135. Thru 8.139. (Unused.) Section 8JTRANSPORTATION 8.140. Ferrying of Aircraft. When ferrying of aircraft is involved, it is the responsibility of the FMS customer to negotiate with AFSAC on a case-by-case basis for flight delivery of aircraft bought under the FMS program. All costs involved are paid by the recipient customer as documented on the applicable LOA. NOTE: Security assistance materiel will be transported according to the policy and procedures in DoD 4500.9R, Volume II, Cargo Movement. 8.141. Packaging and Marking. FMS material shall be packaged in accordance with the latest revision of MILSTD-2073-1, DoD Standard Practice for Military Packaging. Military preservation and Level B packing per MILSTD 2073-1 is required for overseas air shipments. Military preservation and Level A packing per MIL-STD2073-1 is required for overseas surface shipment. All FMS shipments shall be marked in accordance with the latest revision of MIL-STD-129, DoD Standard Practice for Military Marking. 8.141.1. Required markings shall also include the following items.

8.141.1.1. FMS case identifier. 8.141.1.2. Transportation Control Number (TCN). 8.141.1.3. Transportation priority. 8.141.1.4. Project Code, if applicable. 8.141.1.5. Ship-From address. 8.141.1.6. Ship-To address. 8.141.1.7. Ultimate consignee/Mark-For address (MAPAC address code and clear text address if applicable). 8.141.2. Consolidation policy is governed by MILSTRIP, DoD 4000.25-1-M, Chapter 6, Paragraph M. Consolidations of FMS material may be made when the following criteria are met. 8.141.2.1. Same U.S. sponsoring service. 8.141.2.2. Same FMS case designator. 8.141.2.3. Same Mark For location. 8.141.2.4. Same Ship To freight forwarder location. 8.141.2.5. The same priority designator materials with priority designators 01-08 may be consolidated but are not mixed with materiel of lower priorities. 8.141.3. Consolidation is not done when the physical configuration of an item is incompatible with other items shipped to the same destination. Items designated as explosives are not consolidated with other items destined to the same consignee. Hazardous materials may be consolidated unless prohibited by the loading and storage instructions of Title 49, Code of Federal Regulations. 8.141.4. When FMS material is shipped to a freight forwarder (other than XX, RP 46-46) and a specific code (other than a numeric zero) is in column 33, clear text in-country destination addresses are marked on shipping containers. Ship-to and Mark-for codes and related clear text address information is contained in DoD 4000.25-8-M (MAPAD). 8.142. Preparation and Distribution of DD Form 1348-1A. 8.142.1. One set of the release/receipt documents, DD Forms 1348-1A, is prepared and distributed in accordance with DoD 4000.25-1-M, MILSTRIP, Chapter 5. The DD Form 1348-1A consists of a three copy set. Copy number 1 will be retained by the shipper; Copy number 2 will be secured to the outside of the shipping container in a waterproof envelope; and, Copy number 3 will be placed inside the shipping container. If items are consolidated for shipment, a copy of the DD Form 1348-1A for each item will be placed inside the waterproof envelope and affixed to the outside of the shipping container. 8.142.2. The preceding distribution procedures are applicable to the DD Form 1149, Requisition and Invoice/Shipping Document. 8.143. Thru 8.147. (Unused.) Section 8KPROCESSING FMS SUPPLY DISCREPANCY REPORTS (SDR) 8.148. Purpose. This section sets policy, responsibilities and procedures for submitting and processing Air Force SDR (formerly referred to as Reports of Discrepancy (ROD)) against FMS shipments. The term Supply Discrepancy Report (SDR) identifies all forms and formats of discrepancy reports that have evolved from Standard Form (SF) 364, Report of Discrepancy. NOTE: The FMS customer submits SDRs via a SF 364 hardcopy or an authorized electronic or automated equivalent to get possible financial adjustment, disposition instructions for discrepant materiel, or for information only. Defense Security Cooperation Agency (DSCA) (formerly DSCA) memorandum dated April 30, 1998 approved the elimination of the signature requirement for an electronic/automated SF 364 submission and reply. As a general rule, the SDR is not submitted for replacement of materiel; the replacement/repair option remains available to the DoD Inventory Control Point/Integrated Material Manager (ICP/IMM) or contractor when this is the most reasonable solution. Samples of related forms are in attachments 8K1 through 8K5. 8.149. Related Discrepancy Reporting. Not included in this section are the responsibilities and procedures for submitting and processing the following. 8.149.1. Transportation discrepancies for FMS materiel moved in the Defense Transportation System (DTS), processed under Defense Transportation Regulation (DTR), DoD 4500.9-R, Part II, Chapter 210. 8.149.2. Deficiencies, such as those identified in TO 00-35D-54, Chapter 5, which are reported only for analysis, repair, replacement, or information, but have no possibility of obtaining financial reimbursement. 8.150. Scope. This section applies to Air Force agencies that provide security assistance (SA) materiel from stock and procurement to FMS customers through an LOA.

8.151. Policy. 8.151.1. AFSAC is the designated Air Force FMS SDR International Logistics Control Office (ILCO) found in AFJMAN 23-215. AFSAC and the term ILCO are used interchangeably in this section. 8.151.2. The SF 364 is the form on which FMS customers report shipping, packaging, services, and billing discrepancies and product quality deficiencies in SA shipments. An SF 364 and SDR are used interchangeably in this section. 8.151.3. FMS customers submit SFs 364 (by hardcopy, electronically, or by automated system) to the ILCO for processing. The FMS customer will submit all SA SDRs directly to the ILCO for initial screening and processing in accordance with AFJMAN 23-215, Enclosure 7. All correspondence to and from FMS customers for SDR processing is directed to and from the ILCO. 8.151.4. Credits or debits, as a result of processing SDRs are applied to the proper FMS case or to the FMS customer's trust fund, if the case is closed. 8.152. Responsibilities. 8.152.1. The ILCO (AFSAC). 8.152.1.1. Acts as the Air Force FMS SDR processing office. 8.152.1.2. Receives all Air Force SDRs (SFs 364) from the FMS customers. 8.152.1.3. Provides an acknowledgement of receipt and SDR Monthly Status Report to the FMS customer. 8.152.1.4. Returns SDRs to the FMS customers that do not meet submission requirements with an explanation for rejecting the SDR. 8.152.1.5. Processes SDRs according to AFJMAN 23-215 and this section. 8.152.1.6. Controls/tracks and adjudicates the customers' claims by approving or disapproving SDR decisions given by the commands or agencies. HQ AFMC centers, other Air Force MAJCOMs, and their subordinate organizations make decisions on SDRs based on information available to them, but the final approval or disapproval of these decisions rests with the ILCO. 8.152.1.7. Is the only office to communicate with the FMS customer on SDRs. 8.152.1.8. Submits the FMS SDR Management Report to SAF according to AFJMAN 23-215. 8.152.1.9. Obtain Air Force legal opinions from HQ AFMC/JA for SDRs submitted to SAF for resolution. 8.152.2. SAF. 8.152.2.1. Acts as the Air Force focal point for AFJMAN 23-215. 8.152.2.2. Receives recommended changes to AFJMAN 23-215 and submits those changes to the Defense Logistics Management Standards Office (DLMSO) as a coordinated Air Force position and recommendation. 8.152.2.3. Receives unresolved (contested) SDRs from the ILCO and other politically sensitive SDRs. Determines the final Air Force position on contested SDRs, and advises the ILCO accordingly. 8.152.2.4. Receives SDRs valued in excess of $10,000, with all supporting documents, from the ILCO under the following conditions: 8.152.2.4.1. The SDR is against materiel shipped from a contractor/procurement source, and 8.152.2.4.2. It is determined, through a research investigation, that the US government is legally liable for the discrepancy. 8.152.2.5. Receives the Air Force legal opinion from SAF/GC and submits SDRs valued in excess of $50,000 to DSCA for approval and funding from FMS administrative funds. SAF provides the ILCO with the final determination. 8.152.2.6. Gives support and assistance to the Air Force FMS SDR office to solve problems involving major Air Force commands and DoD activities and civilian agencies. 8.152.3. HQ AFMC. 8.152.3.1. AFSAC/IA designates (with appropriate HQ AFMC coordination) the SDR control office at AFMC centers that get SDRs from the ILCO. 8.152.3.2. Other HQ AFMC organizations will assist the ILCO in solving FMS SDR issues as appropriate. 8.152.4. Air Force MAJCOMs. 8.152.4.1. Other Air Force MAJCOMs designate the SDR control office within their command that receive SDRs from the ILCO and help their subordinate organizations to conduct the research investigation and solve SDR issues. 8.152.5. The designated SDR control offices: 8.152.5.1. Get SDRs from the ILCO for processing according to this section.

8.152.5.2. Send the SDR to the proper organization (depending on the SDR category) for the research investigation. 8.152.5.3. Evaluate investigating organization response to ensure compliance with regulatory requirements. 8.152.5.4. Give accurate and timely SDR responses (55 calendar days from the date of receipt by the SDR control office) to the ILCO on all SDRs. 8.153. Submission Procedures. 8.153.1. SDRs against FMS shipments must be received in the ILCO in accordance with the time limit specified in the LOA Standard Terms and Conditions. Claims received after the one-year time limit are disallowed unless the ILCO determines that unusual and compelling circumstances exist, the most common involving latent defects. A latent defect is defined as a quality deficiency in the design, materiel specification, manufacture, and workmanship of an article which effects the operability and is not normally detected by examination or routine test, but which was present at time of manufacturer. A latent defect must be substantiated with evidence that a receipt inspection was performed and the defect could not be detected at that time and that the defect is present for reasons other than deterioration or damage incurred during storage or handling. NOTE 1: FMS countries submitting an SF 364 (SDR) for deficient materiel under the product quality deficiency category (discrepancy code Q1) which may be a safety-of-flight deficiency should refer to TO 00-35D-54, Chapter 5. NOTE 2: For suspected defective materiel problems which do not meet the SDR submission criteria (do not submit an SDR): Technical Coordinating Program (TCP)/International Engine Management Program (IEMP) member countries should notify the Technical Coordinating Group (TCG) in accordance with TO 00-35D-54, Chapter 5. Non-TCP/IEMP member countries should notify their respective AFSAC country manager. 8.153.2. SDRs for billing discrepancies are submitted no later than one year from the date the billing transaction that caused the discrepancy first appeared on the FMS customer's Quarterly Billing Statement (DD Form 645). 8.153.3. SDRs for financial discrepancies (administrative and/or below-the-line accessorial charges) will be submitted to the ILCO and forwarded to the Defense Finance and Accounting Service (DFAS) Denver for processing. 8.153.4. SDRs valued at $200.00 or less will not be processed for overages, shortages, damages, non-receipt or non-performance. All other SDRs will be processed. 8.153.5. The FMS customer or his authorized representative prepares and submits an SF 364 to the ILCO in accordance with the procedures in AFJMAN 23-215 as implemented by this section. The SF 364 is submitted to AFSAC/COSD, 5490 Pearson Rd, Wright Patterson AFB, Ohio 45433-5332, for Air Force requisitions only. The SF 364 can be obtained through an FMS publication case. The procedures for requisitioning standard forms and publications are in section H of this chapter. 8.153.6. The original and five copies (front and back) of the SF 364 hard copy (attachment 8K1) must be submitted along with an attached copy of the applicable release/receipt document which accompanied the materiel and any supporting documents. For electronic/automated SDRs one copy of the SF 364 and applicable documentation is required. Examples of such documents are DD Form 1348-1A Issue Release/Receipt Document (attachment 8K2), DD Form 250, Materiel Inspection and Receiving Report (attachment 8K3), or DD Form 1149, Requisition and Invoice/Shipping Document (attachment 8K4). 8.153.7. The following are some general guidelines for numbering and preparing the SF 364. 8.153.7.1. Do not duplicate a report number under the same master and line item case designator, i.e., KBD/001. 8.153.7.2. Avoid the use of the letter R in the report number. The letter R is reserved for ILCO use only to correct any report numbers that are found to be duplicated. 8.153.7.3. Enter in block 5b the number and date of the vendor's invoice or shipper's bill number, not the quarterly billing statement number. Attach a copy of the invoice to SF 364. 8.153.7.4. Enter in block 7a the shipment number (when more than one shipment is made under a contract requisition) and contract/contract line item number/document number (e.g., contract or purchase order). Include the shipment date to distinguish multiple shipments from a contractor source. 8.153.7.4.1. A separate SDR must be submitted for each shipment when multiple shipments occur on a requisition. 8.153.7.5. Enter in block 9c the quantity shown on the applicable release/receipt document as being shipped and billed.

8.153.7.6. Block 12-Remarks - This block should be used for any supplemental information when the combination of discrepancy codes and action codes need clarification or when a discrepancy needs an explanation. 8.153.7.6.1. Enter FMS. 8.153.7.6.2. On SDRs involving shortages, the FMS customer should cite whether all containers shown as shipped on the issue release/receipt document were received. 8.153.7.6.3. On SDRs involving nonreceipt, the FMS customer must attach a written statement from their freight forwarder confirming that the shipment has not been received on the requisition and Transportation Control Numbers (TCN) that apply. 8.153.7.6.4. On SDRs involving damaged materiel, the FMS customer must provide evidence that the damage existed before shipment from the source of supply or that the damage was caused by a packaging deficiency. 8.153.7.6.5. When reporting product quality deficiencies or damaged materiel, detailed deficiency data must be included for investigation purposes. In addition to photographs, test data, and related documentation, the following information must be included, if available: 8.153.7.6.5.1. The date deficiency was discovered. 8.153.7.6.5.2. The name of the manufacturer or overhaul activity and Commercial and Government Entity (CAGE) code, if available. 8.153.7.6.5.3. The lot, batch, or serial number. 8.153.7.6.5.4. The contract/purchase order number. 8.153.7.6.5.5. The item condition: new, repaired or overhauled. 8.153.7.6.5.6. The date of manufacture, date cured, date assembled, date packed (apply one as appropriate), and expiration date for Type I (nonextendible) shelf-life items and inspection or test date for Type II (extendible) shelflife items. Include the date of repair or overhaul, if pertinent. 8.153.7.6.5.7. Operating time at failure. 8.153.7.6.5.8. The end-item the deficient item works on or with. 8.153.7.6.5.9. Estimated cost of repair. 8.153.7.6.5.10. Nature of complaint stating in detail why the materiel is unsatisfactory. 8.153.7.6.5.11. The location of materiel. 8.153.7.6.5.12. Point of contact name, address and telephone number. 8.153.7.6.5.13. Identify the weapon system, if a TCG member, or indicate non-TCG member. 8.153.7.6.5.14. Provide a copy of the serviceable tag, if applicable. NOTE: FMS customers not participating in a TCP/IEMP can submit an SDR for a CAT 1 (safety-of-flight) deficiency in accordance with TO 00-35D-54, Chapter 5. For deficiencies known or suspected to be the result of mishaps caused by design, malfunctions, materiel, quality, software or a deficiency with High Accident Potential (HAP) in accordance with AFI 91-204, Safety Investigations and Reports, the FMS customer shall notify the SPD within 72 hours of detection by message or letter. Two copies of the letter or message sent to the SPD must accompany the SDR. The FMS customer must hold the deficient materiel pending disposition instructions from the ILCO. 8.154. General Processing Procedures. 8.154.1. The ILCO will send five copies of the SF 364 hardcopy along with back-up data to the appropriate SDR control office for processing. For electronic/automated SDRs only one copy of the SF 364 and applicable back-up data is provided. 8.154.2. Within five days of receipt, the SDR control office will send the SDR along with the applicable supporting documentation to the organization(s) responsible for investigation and resolution of the SDR. The purpose of the investigation is to: 8.154.2.1. Determine the validity of the materiel deficiency reported by the FMS customer. 8.154.2.2. Determine, and support by facts and documented evidence, the cause of the materiel deficiency. 8.154.2.3. Determine the corrective measures necessary to prevent repeated discrepancies. 8.154.3. The investigating organization(s) must give enough details to substantiate their recommendation. The investigation results, which include the cause of the materiel deficiency, corrective action and recommendation must be documented, signed, dated and returned to the SDR control office. The investigation results must be provided with the reply to the FMS customer for SDRs reporting quality deficiencies. Neither FMS administrative funds nor US government funds and assets are used to absorb the cost of an SDR transaction unless the USG is legally determined to be liable for resolution of the SDR.

8.154.3.1. When it is determined that USG action/inaction caused a discrepant contractor shipment (direct cite funded 4F), a request for credit from administrative funds with justification is provided with the investigation results and recommendation to the SDR control office. 8.154.3.2. If item management responsibility for an item has transferred to another component after the date of shipment, the Losing Item Manager (LIM) will involve the Gaining Item Manager (GIM) in the investigation to validate the item deficiency, obtain disposition instructions and purge DoD inventory of any deficient items, if required. All action initiated between the LIM and GIM will be provided with the investigation results and recommendation to the SDR control office. 8.154.4. The SDR control office will, based upon the investigating organization's recommendation (including the cause and corrective action for a quality deficiency), take one of the following actions: 8.154.4.1. Reply, using the comments received and guidance for corrective action, and provide the investigation results to the ILCO with the proper adjustment allowance code in block 23 (Remarks) on the reverse side of the SF 364 hard copy. The electronic/automated reply will include, at a minimum, the requisition number, SDR report number (item 2 of SF 364), point of contact, pertinent information from the data blocks on the SF 364 or equivalent codes listed in AFJMAN 23-215 (Enclosures 4, 5, and 6) and investigation results. Reply codes for an SF 364 are identified in attachment 8K5. 8.154.4.2. Prepare a detailed request explaining what additional information is required to process the SF 364, if necessary. The request is sent to the ILCO. The ILCO will review the request and, if appropriate, forward the request to the FMS customer. The SDR is closed and reopened after getting the requested information from the customer. 8.154.4.3. Process credits against shipments from stock using the same funds as used in the original debit. All direct cite (4F) credits, except delivery reporting errors or contract adjustments, are sent to the ILCO with a request from the SDR control office for credit from administrative funds with proper justification to be reviewed and processed, unless the materiel is returned to Air Force inventory. When materiel is returned to Air Force inventory the credit will be accomplished using Air Force appropriated funds. 8.154.4.3.1. A delivery reporting transaction processed as a result of SDR action must have the SDR number in the NSN field with the appropriate adjustment allowance codes and all requirements of DoD 7000.14-R, Vol. 1. 8.154.5. The SDR control office will distribute the reply to the SF 364 as follows: 8.154.5.1. The original and one copy of the SF 364 hardcopy with all substantiating documentation are sent to the ILCO. The electronic/automated response will include the requisition number, SDR report number (item 2 of SF 364), point of contact, pertinent information from the data blocks on the SF 364 or equivalent codes listed in AFJMAN 23-215 (Enclosures 4, 5, and 6) and all substantiating documentation. Reply codes for a SF 364 are identified in attachment 8K5. 8.154.5.2. One copy is kept in the administrative file at the SDR control office for at least one year after financial completion. 8.154.6. The ILCO will set up a 55-day suspense file for getting replies from the SDR control office. After 55 days, a follow-up is sent to the SDR control office on a monthly basis until an adequate reply is received. The first two follow-up letters are addressed to the SDR control office. Any follow-up thereafter is progressively elevated until completion of the SDR is accomplished. 8.155. Types of Discrepancy. The following types of discrepancies are reported on the SF 364. 8.155.1. Overage - An overage is a quantity that is physically received in excess of the quantity ordered or shown on the shipping document. This does not include requisition quantities which are adjusted by the source of supply to conform to standard unit pack quantities or minimum buy contracts. 8.155.2. Duplicate Shipment - A duplicate shipment is the shipment of identical materiel in the same quantity, and under the same requisition number as the shipment previously received, but was not requisitioned by the FMS customer. The shipment should correspond exactly to a previous shipment. 8.155.3. Wrong Item - A wrong item is not an intended interchangeable/substitute item or an item received in lieu of the item requisitioned because of a shipper error. 8.155.4. Misdirected Shipment - A misdirected shipment is materiel improperly addressed and/or shipped to the wrong destination. NOTE: This type of discrepancy may also be reported by message, letter or the freight forwarder can contact the shipper (depot) to obtain disposition to move the misdirected shipment to the correct destination.

8.155.5. Nonreceipt - Nonreceipt exists when billings are received but no record can be found indicating receipt of the materiel by the freight forwarder or at the final in-country destination. 8.155.6. Shortage - A concealed shortage exists when the physically received quantity is less than the quantity ordered, billed or shown on the shipping document. 8.155.7. Quality Deficiency - A quality deficiency is a defect or nonconforming condition that limits or prohibits the product from meeting its intended purpose. Included are deficiencies in design, specification, materiel, manufacturing and workmanship. 8.155.8. Damaged - Partial or total marring of the appearance or usability of the materiel for its intended purpose. A condition creating impaired item functionality. NOTE: Container damage must be annotated on the carrier's bill of lading at the time it is received by the freight forwarder. This will substantiate a claim against the carrier if the carriers mishandling damaged the materiel. 8.155.9. Improperly Packed Shipment - Materiel is received in a damaged condition (e.g., corrosion, broken, parts missing) as a result of improper preservation, packing, marking, loading, handling or storage while in US government custody. 8.155.10. Insufficient Shelf Life - Insufficient shelf life is when deteriorative or unstable characteristics exist that limit the time during which an item can be satisfactorily stored before its use. 8.155.11. Billing Discrepancies - Billing discrepancies exist when materiel is received as ordered (and with proper accompanying documentation) but the billings per individual shipment are incorrectly reflected, omitted or duplicated on the FMS Billing Statement (DD Form 645A) and/or supporting FMS Delivery Listing issued quarterly by DFAS Denver to the FMS customers. 8.156. Processing SF 364 by SDR Category. 8.156.1. Overage or Duplicate Shipment: 8.156.1.1. If the FMS customer decides to keep the materiel and the FMS customer has been billed, approval must be obtained from the ICP/IMM. 8.156.1.1.1. If the ICP/IMM approves retention, financial adjustment is not necessary. The reply approving retention is sent through the ILCO to the FMS customer. 8.156.1.1.2. If the ICP/IMM disapproves retention, complete disposition instructions are provided through the ILCO to the FMS customer. Upon the return of materiel to US government custody, credit is processed. 8.156.1.2. If the FMS customer decides to keep the materiel that has not been billed, approval is obtained from the ICP/IMM. 8.156.1.2.1. If the ICP/IMM approves retention, a debit transaction is processed for the materiel. The reply approving retention is sent through the ILCO to the FMS customer. 8.156.1.2.2. If the ICP/IMM disapproves retention, complete disposition instructions are provided through the ILCO to the FMS customer. If the materiel is not returned within 180 days, the ILCO may request a debit transaction, if appropriate. An amended reply is sent to the FMS customer stating that the materiel has not been received and a debit for the materiel has processed. 8.156.1.3. If the FMS customer does not want to keep the materiel, complete disposition instructions are provided through the ILCO to the FMS customer. 8.156.1.3.1. If the materiel is returned within 180 days and the materiel was initially billed, credit will be processed. 8.156.1.3.2. If the materiel is not returned to US government custody within 180 days, a debit transaction will be processed, when applicable, to insure the FMS customer is charged appropriately for the materiel that was not returned. 8.156.2. Shortage - Reports of shortage are investigated by using available documentation, which is matched to the quantity shipped for the concealed shortage. Examples of such documentation are those that contain, but are not limited to, size, total weight, and cube accepted by the carrier. Credit is denied if the documentation, in conjunction with the individual item unit weight and cube, supports shipment of the total quantity billed. Otherwise, appropriate credit for the difference is required. 8.156.3. Wrong Item. 8.156.3.1. If the FMS customer asks for retention of a wrong item, the SDR control office will: 8.156.3.1.1. Get approval from the ICP/IMM for retention. 8.156.3.1.2. Verify the cost of the item(s) requisitioned and received.

8.156.3.1.3. Process a debit transaction, if retention is approved, for the materiel received and process a credit transaction for the materiel requisitioned, if applicable. 8.156.3.2. If the FMS customer does not want to keep the materiel, the ICP/IMM gives disposition instructions for the materiel through the ILCO to the FMS customer as follows: 8.156.3.2.1. May authorize local disposal for materiel valued at $250 or less, except in the case of hazardous materiel. Local disposal of hazardous materiel is not authorized. 8.156.3.2.2. Must direct return of materiel to US government custody if value is more than $250 except in unusual circumstances where the ICP/IMM determines there is no scrap value, or items are unsuitable for transporting, as in the case of unstable ammunition. 8.156.3.3. A credit transaction is processed for the item requisitioned upon return of wrong item. 8.156.3.4. The following action is taken if the materiel is not returned as directed. 8.156.3.4.1. If the value of the wrong item exceeds the value of the requisitioned item, the wrong item is debited and the requisitioned item is credited. 8.156.3.4.2. If the value of the wrong item does not exceed the value of the requisitioned item, no financial adjustment is necessary. 8.156.4. Misdirected Shipments. 8.156.4.1. When a misdirected shipment is reported, the customer or freight forwarder that got the materiel is provided disposition instructions through the ILCO. 8.156.4.1.1. If the shipment can be rerouted to the requisitioning customer; no financial adjustment is necessary. 8.156.4.1.2. If the shipment is directed to be returned to a designated turn-in point, a DD Form 1348-1A is provided for the return shipment. 8.156.4.2. If the materiel is not returned within 180 days, the customer that got the shipment is billed and credit is processed for the initial requisition. 8.156.5. Nonreceipt. To deny an SDR for non-receipt of materiel, evidence of shipment is provided. Evidence of shipment is a signed carrier's receipt and a DD Form 1348-1A or DD Form 250 that identifies the materiel in question. These documents must cross-reference each other. Such documents usually show the quantity, national stock number (NSN), bill of lading number, parcel post insured or registered number, name of shipper or carrier. 8.156.6. Quality Deficiency. 8.156.6.1. If as a result of the research investigation, there is an indication that the contractor caused the deficiency, the contracting office must pursue satisfaction from the contractor on behalf of the FMS customer under the provisions of the Federal Acquisition Regulation (FAR). The SDR is not finalized until all recourse against the contractor is completed. Credit from Air Force appropriated funds or administrative funds are not authorized for a deficient contractor shipment (direct cite funded 4F) unless it is determined that US Government error caused the deficiency. 8.156.6.2. When it is determined that the US government is liable for a quality deficiency (stock shipment) and the FMS customer wants to repair the item(s) and submits cost of labor and materiel to make item(s) serviceable, the cost of labor and materiel is credited by the approving ICP/IMM. The cost of repair by the FMS customer cannot exceed the cost of repair if the item were repaired by the USG. Credit for repair of materiel shipped from a contractor (direct cite funded 4F) must meet the criteria for approval of administrative funds through the ILCO. If the FMS customer wants to return the unserviceable materiel for credit, the ICP/IMM must verify the complaint and give disposition instructions for the materiel. The ICP/IMM must provide an Air Force fund cite with disposition instructions when directing a contractor shipment (direct cite funded 4F) back to Air Force inventory (buy-back) for credit. If an exhibit is necessary for analysis to determine if the complaint is valid, the exhibit is requested through the SDR control office. When an exhibit is returned to a contractor facility written concurrence from the contractor approving the return must support the disposition instructions to the SDR control office. The SDR control office will forward the disposition and supporting documentation to the ILCO. The ILCO will send the request for an exhibit to the FMS customer and close the SDR waiting for receipt of the exhibit. Once the exhibit is received, the ILCO is notified and the SDR is reopened pending results of the investigation. Investigation results are sent to the SDR control office and forwarded through the ILCO to the FMS customer. 8.156.7. Damaged or Improperly Packed Shipment. When it is determined that the damage was the fault of the shipping activity, the ICP/IMM will give complete disposition instructions. If it is determined that the damage was not the fault of the shipping activity and was possibly caused by carrier mishandling, the FMS customer is told to file a claim with the carrier.

NOTE: Container damage must be annotated on the carrier's bill of lading at the time it is received by the freight forwarder. To substantiate a claim against the shipping activity the damage must be annotated on the carrier's bill of lading at the time the materiel was released to the carrier. 8.156.8. Insufficient Shelf Life. If sufficient shelf life (in accordance with directives) remained at the time of issue, the SDR is denied with appropriate documentation/information. When it is determined that the materiel was issued with insufficient shelf life, the ICP/IMM will give disposition instructions and credit, if applicable. 8.157. Returning FMS SDR Materiel to US Government Control. The ICP/IMM is responsible for providing the return shipping instructions to the SDR control office. The SDR control office forwards the disposition and investigation results to the ILCO. Materiel is directed for return by the most economical means available via a DD Form 1348-1A prepared by the ILCO. NOTE: An inspection of the shipment is accomplished by the final destination when the SDR materiel is received. If there is a discrepancy in the returned shipment, the ILCO (AFSAC/COSD) is advised. The ILCO will tell the FMS customer and instruct the SDR control office as to what action should be taken. 8.157.1. The following procedure applies for the return of approved FMS SDR materiel: 8.157.1.1. The ILCO after getting disposition instructions from the SDR control office will prepare a DD Form 1348-1A via the SAMIS Quick Access ID (QAID) 356 and set up a 180 day return suspense date for receipt of the materiel into US government custody. 8.157.1.1.1. Block 2. (First Destination Address) - Designate the US/DoD activity that will receive the return shipment from the FMS customer first. When determining the US/DoD activity consideration is given to: 8.157.1.1.1.1. The location of the materiel, e.g., in country, freight forwarder, CONUS activity (generally provided in item 12, Remarks, of SF 364). 8.157.1.1.1.2. The nearest US/DoD activity to the materiel that has the capability to receive, store and transport the discrepant materiel. 8.157.1.1.1.3. Cost and modes of transportation available. 8.157.1.1.1.4. Recommendation by the FMS customer. NOTE: When there is not a DoD activity in the FMS customer country that has the capability to receive, store and transport the discrepant materiel, the FMS customer will be told to return the materiel prepaid by the most economical means to the final destination. The FMS customer can ask for reimbursement for a prepaid shipment by submitting receipted bills to the ILCO and designating where payment should be made. 8.157.1.1.2. Block 4. - Enter the SDR report number (item 2 of SF 364). 8.157.1.1.3. Block 8. (Ship To) - Enter the address of the ultimate destination. 8.157.1.1.4. Block 24. Document Number (RP 30-43) - Enter the FMS document number of the original requisition, as shown on the SF 364. 8.157.1.1.5. Block 27. (Additional Data) - Identify the FMS country code, case and line item to be credited, e.g., credit FMS case: CN-RDT/001. 8.157.1.1.6. Block 27. (Additional Data) - For FMS return shipments, enter the transportation account code DIII and appropriate fund cite 97-11X8242 L009 8401**DIII GBL S843000. Where ** appears, enter the two position FMS country code. 8.157.1.2. When the shipment is received at the first destination address, the transportation office will sign, indicate the organization/location and date on a legible copy of the DD Form 1348-1A. The transportation office will provide two copies of the signed/dated DD Form 1348-1A to the FMS customer when requested. The FMS customer must send a copy of the signed/dated DD Form 1348-1A or an equivalent transportation document, e.g., DD Form 1149, DD Form 1384, to the ILCO as evidence the materiel was returned to USG custody. When a shipment is returned by commercial means the FMS customer will provide the ILCO proof of delivery evidencing the materiel was received at the final destination. 8.157.1.3. The ILCO will provide a copy of the materiel return documentation the to the SDR control office. When SAMIS reflects a D6E a copy of the unsigned/dated DD Form 1348-1A with either the SAMIS requisition history reflecting the D6E transaction or the D6E return receipt interrogation (QAID 269) will be provided to the SDR control office requesting credit for the returned SDR materiel, if applicable. Either of these documents will be used as proof that the FMS customer has turned the materiel into USG custody. A financial adjustment is processed, if necessary. The adjustment is granted only when the FMS customer has placed the materiel in transit within 180 days from the return suspense date established when the ILCO prepared the DD Form 1348-1A shipping instructions.

8.157.1.4. When the ILCO does not get a receipted DD Form 1348-1A or equivalent transportation document from the FMS customer within 120 days, the ILCO will tell the FMS customer by letter that materiel has not been received and there are 60 days remaining to make sure the materiel is returned. After 180 days, if there is no evidence of the materiel being returned or in transit, the FMS customer is told by letter that if the materiel was returned or is in transit to provide a signed DD Form 1348-1A as evidence to the ILCO. After 210 days, if no evidence is received that shows that the materiel was returned, a letter is sent to the FMS customer with a copy to the appropriate SDR control office to advise that the time has passed for returning the materiel and request a financial adjustment, if required. 8.157.2. The following procedure applies when FMS SDR materiel is returned as an exhibit for analysis and determination of liability: 8.157.2.1. The investigating organization notifies the SDR control office in writing of the complete Ship To and Mark For address when an exhibit is required. The SDR control office provides the disposition to the ILCO to prepare a DD Form 1348-1A for return of the exhibit (attachment 8K7). The DD Form 1348-1A is clearly marked FMS EXHIBIT and will have the name and extension of an individual in the investigating organization to be contacted upon receipt of the exhibit, if provided. If the exhibit is being returned to a contractor, the DD Form 1348-1A will reflect the words OPEN IN THE PRESENCE OF A U.S. GOVERNMENT REPRESENTATIVE. Preparation of the DD Form 1348-1A must have: 8.157.2.1.1. Block 2. (First Destination Address) - Designate the US/DoD activity that is to get the return shipment from the FMS customer first. When determining the US/DoD activity consideration is given to: 8.157.2.1.1.1. The location of the materiel, e.g., in-country, freight forwarder, CONUS activity (generally provided in item 12, Remarks, of SF 364). 8.157.2.1.1.2. The nearest US/DoD activity to the materiel that has the capability to receive, store and transport the discrepant materiel. 8.157.2.1.1.3. Cost and modes of transportation available. 8.157.2.1.1.4. Recommendation by the FMS customer. NOTE: When there is not a DoD activity in the FMS customer country that has the capability to receive, store and transport the discrepant materiel the FMS customer will be told to return the materiel prepaid by the most economical means to the final destination. The FMS customer can ask for reimbursement for a prepaid shipment by submitting receipted bills to the ILCO and designating where payment should be made. 8.157.2.1.2. Block 4. - Enter the SDR report number (item 2 of SF 364). 8.157.2.1.3. Block 8. (Ship To) - Enter the address of the ultimate destination. 8.157.2.1.4. Block 24. Document Number (RP 30-43) - Enter the FMS document number of the original requisition, as shown on the SF 364. 8.157.2.1.5. Block 27. (Additional Data) - FMS EXHIBIT - OPEN IN THE PRESENCE OF A USG REPRESENTATIVE. Give the name and telephone number of the person to be contacted upon receipt of exhibit, if available. 8.157.2.1.6. Block 27. (Additional Data) - For FMS return shipments, enter the transportation account code DIII and appropriate fund cite 97-11X8242 L009 8401**DIII GBL S843000. Where **appears, enter the two-position FMS country code. 8.157.2.2. The investigating organization will conduct an analysis at no cost to the US government. An exhibit will be adequately protected and controlled in accordance with FAR Part 45. Contractor assistance that may result in costs to the US government or the FMS customer must have prior approval from the ILCO. 8.157.2.3. The SDR control office will send the disposition instructions and other information to the ILCO with the reply for the SDR. The ILCO will prepare the DD Form 1348-1A for return of the exhibit via SAMIS QAID 356. 8.157.2.4. The ILCO forwards the DD Form 1348-1A, reply and any other important information to the FMS customer. 8.157.2.5. The SDR is closed pending receipt of exhibit from the FMS customer. The FMS customer has 90 days (unless told otherwise) to have the exhibit in transit to the designated facility for analysis. 8.157.2.6. The FMS customer will notify the ILCO upon release of the exhibit to the US government and ensure that a copy of the receipted DD Form 1348-1A or equivalent transportation document is provided to the ILCO. If prior ILCO notification of the exhibit return has not been received by the investigating agency, that activity will inform the ILCO that the exhibit has been received.

8.157.2.7. After receipt of the documentation evidencing return of the exhibit to USG custody, the ILCO will reopen the SDR pending results of the investigation and final action. The ILCO will inform the SDR control office of the exhibit return and provide evidence of return and disposition for shipment of the exhibit back to the FMS customer when the analysis and determination of liability is completed. 8.157.2.8. The investigating organization will coordinate scheduling the analysis and tracking the materiel once it has been received to make sure the materiel is not lost. Investigating organizations must make sure FMS returned exhibits are not posted to Air Force inventory. Exhibits should be handled as non-accountable materiel. 8.157.2.9. The ILCO will set up a suspense and follow-up to the SDR control office every 35 days after the SDR is reopened, pending receipt of final action taken. 8.157.2.10. The results of the analysis are sent to the SDR control office for review and to ensure the response is in compliance with regulatory requirements. 8.157.2.10.1. If the analysis confirms the reported deficiency, the SDR is approved and updated to show what corrective action is being taken. The customer is entitled to reimbursement of transportation charges for returning the exhibit for analysis, if requested. 8.157.2.10.2. If the analysis does not confirm the reported deficiency and the US government contractor accepts liability, or there is no US government/contractor liability for the deficiency, the SDR is denied and a detailed report is sent to the FMS customer through the ILCO. If costs were incurred to perform the exhibit analysis or the FMS customer authorized repair of the exhibit at their expense, action should be taken to make sure that expenses for the analysis or repair are charged to the customer's maintenance or services case. 8.157.3. When a freight forwarder received misdirected or incorrect shipments, and has incurred charges for his efforts, he should contact either the shipper (depot) or ILCO to get disposition instructions and reimbursement of costs. This type of discrepancy can be reported by message, letter or the freight forwarder can contact the shipper (depot). The ILCO can be contacted at toll free number 1-800-448-036l. 8.158. Reconsideration/Contested SDRs. 8.158.1. If the FMS customer disagrees with the initial SDR reply, or if any action occurs which justifies additional consideration, the FMS customer must send a written request (e.g., letter, message) to reach the ILCO (AFSAC/COSD) within 90 calendar days from the date of the ILCO reply to the customer. The written request must include the SDR report number (item 2 of the SF 364), requisition number, and any additional information or an explanation concerning the settlement of the discrepancy. The ILCO will reopen the SDR and review the information. If the request for reconsideration is not received within the allowable timeframe, the resubmittal request is denied. If the resubmittal timeframe is met, the SDR is processed through normal SDR channels with the new information provided by the customer. This information and any added comments are furnished to the SDR control office within 30 days of receiving the request for reconsideration from the customer. When extenuating circumstances do not allow the ILCO to submit the reconsideration claim to the SDR control office within the allowable timeframe, the ILCO will notify the SDR control office of the delay. Upon receipt of the SDR reconsideration request, the SDR control office has 60 days to provide a response to the ILCO. 8.158.2. If the FMS customer disagrees with a second denial decision, the SDR is considered contested. FMS customers must send contested SDRs to the ILCO within 90 days of the second denial with sufficient justification to support their request for reconsideration. 8.158.2.1. The ILCO forwards contested SDRs, with all related correspondence and documents, to SAF for review and final Air Force determination within 15 days from the date that the contested SDR was received by the ILCO. 8.158.2.2. SAF provides the final Air Force determination to the ILCO with information for processing credit, repair, replacement, or denial as appropriate within 60 days from the date the contested SDR package was received by SAF. 8.158.2.3. The ILCO notifies the FMS customer of the final Air Force determination. 8.159. Thru 8.163. (Unused.) Section 8LNOT-MISSION-CAPABLE SUPPLY (NMCS) DETERMINATION/REQUISITIONING CRITERIA. 8.164. General. Priorities are set up to ensure that those demands having the most serious impact on mission capability receive priority processing. Everyone must share the responsibility for an effective and credible priority system. Additional policy guidance for submission criteria, initiation, and processing of NMCS requisitions can be found in AFMAN 23-110 in the following references: 8.164.1. Chapters 2 and 24, part 1, volume 1.

8.164.2. Attachment 40, chapter 1, part 4; volume 1. 8.164.3. Chapter 2, part 1, volume 3. 8.164.4. Chapter 3, part 3, volume 3. 8.165. Determining a NMCS Condition. The customer must first determine when an actual NMCS condition exists that is, when a system or end-item cannot perform any of its assigned missions due to a lack of parts. The fact that a given weapon system is inoperative due to the lack of an item is not enough to justify the use of urgency of need designator (UND)-A. UND-A may be used only when lack of an item, required for immediate end-use, prevents an activity from performing its combat or support missions or tasks, or when such a condition is about to occur or such a condition will occur within 20 days of the date of the requisition. This should not be confused with mission impairment (UND-B), or stock replenishments and routine shortages (UND-C). 8.165.1. An anticipated NMCS is a condition identified in anticipation of mission-critical equipment becoming unserviceable due to a lack of parts, the aircraft going out of service for parts, engines going out of service for parts, etc. 8.166. Customers Materiel Availability. The customer should make sure that all possible in-country resources for locating materiel are checked before sending in new NMCS requisitions or upgrading existing requisitions. The recommended steps are to: 8.166.1. Identify all interchangeability and substitution (I&S) and national stock numbers (NSN). This may be done by reviewing the I&S data on commercially-available electronic research tools that can be ordered on an active publications (P) case. 8.166.2. Review applicable technical orders (TO) to identify the next-higher assembly (NHA) and any NHA I&S applications. 8.166.3. Do a physical inventory of local, other in-country base, or depot assets for the needed item(s), including NHA. 8.166.4. Determine if cannibalization is possible and practical. 8.166.5. Determine if the item(s) can be locally purchased or locally manufactured. 8.167. Upgrading Existing Requisition. After all resources have been considered and it is determined that there are no available assets, the customer should determine if there are any active requisitions, including I&S and NHA NSNs, that can be upgraded to the appropriate Not Mission Capable Supply (NMCS) priority. If so, send an AM__ transaction with the applicable document number. Upgrade only the exact quantity needed to meet the mission capable (NMCS) condition and send a new requisition for remaining routine requirements. 8.168. Requisitioning. If there are no active requisitions that can be upgraded, then a new NMCS requisition must be sent. Requisitions should be in military standard requisition and issue procedures format. 8.168.1. There are certain restrictions on customer-generated requisitions and emphasis is placed on certain NMCS requisition data elements (paragraph 8.110.). Restrictions are placed on the types of item that can be requisitioned by the customer on blanket order (E, FMSO II, R, and nonstandard E and R) cases. For NMCS situations, these restricted items should be asked for by priority message, fax, or e-mail to the AFSAC case manager, who will take the necessary action to enter requisitions into the system. Restrictions include: 8.168.1.1. Single-vendor integrity or sole-source items. 8.168.1.2. Certain classified items. 8.168.1.3. New and unused items (advice code 6P). 8.168.1.4. Major defense equipment. 8.168.1.5. Explosive ordnance items (federal supply group 13). 8.168.1.6. Commercial-type items (advice code 3B). 8.168.1.7. Modification kits. 8.168.1.8. Excess defense articles. 8.168.1.9. Munitions and munitions-related items (material management aggregation code MN and AQ). 8.168.1.10. Local-manufacture or local-purchase items. 8.168.1.11. Cases or lines needing Air Force Security Assistance Center (AFSAC) case manager consideration or action, such as: 8.168.1.11.1. C (for cartridge-actuated devices/propellant-activated devices (CAD/PAD) NMCS). 8.168.1.11.2. V or W (for modification kits or related items). 8.168.1.11.3. System-sales cases (D, Q, S, or Y). 8.168.2. Special emphasis should be placed on specific requisition data elements as follows:

8.168.2.1. Quantity (RP 25-29). Only requisition or upgrade the exact quantity needed to meet the NMCS condition. 8.168.2.2. Priority (RP 60-61). The priority of the requisition is determined using the customers authorized force activity designator (FAD) along with the urgency of need designator (UND). The UND is always A for NMCS requirements. Attachment 8L1 gives the FAD/UND matrix for determining the priority. 8.168.2.3. Required Delivery Date (RDD) (RP 62-64). This data element is made up of the following: 8.168.2.3.1. RP 62 always N for NMCS condition. 8.168.2.3.2. RP 63 always A (UND). 8.168.2.3.3. RP 64 urgency justification codes (attachment 8L2). 8.168.2.3.4. The use of Expedited Handling Signal 999 in requisition RP 62-64, Required Delivery Date (RDD), is not authorized. 8.168.3. NMCS requisitions are input to the system by: 8.168.3.1. The customer transmits the data through the Defense Automatic Address System using the Defense Message System (DMS) or by priority message, fax, or e-mail to the AFSAC case manager. 8.168.3.2. The AFSAC case manager or ALC system program manager for items received by priority message, fax, or e-mail (i.e., A05, items restricted from country requisition, etc.). 8.169. Requisition Managers Follow-up/Tracking Management. 8.169.1. The AFSAC requisition manager gets a SAMIS product, Open Requisitions/Custom Commitments with ESD and Latest Status, RCS: MTC-IA(AR)8406 (PCN. U-WOOI.-HAW), which lists all open (unshipped) NMCS requisitions for review each month. This product is releasable to the customer upon request and will be billed to the appropriate P case. Another SAMIS product (PCN: U-W001-HFD) is the NMCS Statistics Report, which shows the quantity of requisitions shipped, the quantity of open requisitions by age group, and programmed/nonprogrammed within the report month for each customer. 8.169.2. Corrective actions are taken for errors on the listing. Follow-up action is initiated to the customer for verification of all NMCS requisitions over 90 days old (not having a positive supply status) before making a followup to the source of supply (SOS). 8.169.3. The customer is asked to review the request for verification and identify possible candidates to downgrade, which are no longer NMCS requirements. After getting verification from the customer, the requisition manager starts follow-up action to the SOS, and sends a copy to the customer. 8.169.4. The customers NMCS requisition gets special handling under this management idea and better support for a valid high priority requirement. 8.169.5. Cooperative Logistics Supply Support Arrangement (CLSSA) foreign military sales order (FMSO II) programmed requisitions get priority treatment over non-programmed requisitions. Non-programmed requisitions, including NMCS, are not usually supplied using USAF/CLSSA on hand-on order stocks. 8.170. Customer Management Tips. 8.170.1. The customer can help to make sure he or she receives good logistics support for his or her NMCS requisitions by developing and enforcing in-country procedures such as: 8.170.1.1. Making sure all possible sources for locating materiel in country are used before sending or upgrading NMCS requisitions (see paragraph 8.111.). 8.170.1.2. Making sure the assignment of NMCS coding is appropriate for NMCS conditions (see attachment 8L2). 8.170.1.3. Sending in critical requirements as quickly as possible. This applies to both NMCS and anticipated NMCS conditions. 8.170.1.4. Forecasting requirements for expense and investment items on FMSO I case for programmed support. 8.170.1.5. Telling AFSAC immediately of changes in NMCS, if no longer needed, or submitting an AM__ to downgrade the requisition. 8.170.1.6. Giving verification data to AFSAC to justify the NMCS requirement, if asked. 8.170.1.7. Making sure requisitions are correctly submitted. Programmed requisition support is more aggressively managed than non-programmed supported requisitions. The CLSSA participants should complete their FMSO II case requisitions correctly in order for them to be coded programmed. 8.170.1.7.1. Expense-item requisitions (ERRC N and P) will be coded programmed by SAMIS if they have a recurring demand code (R or blank in column 44). 8.170.1.7.2. Investment-item requisitions will be coded programmed by SAMIS if:

8.170.1.7.2.1. The item is on the FMSO I. 8.170.1.7.2.2. The requisition is a recurring demand (R or blank in RP 44). 8.170.1.7.2.3. The requisition quantity is less than or equal to the eligible-to-be-programmed quantity (EPQ). The current EPQ is provided to the CLSSA participant on the Monthly CLSSA EPQ Forecast Notice (GBJ). 8.170.2. The key to reducing the number of NMCS requisitions is to get and maintain a well-balanced stock position and ensure that stock-replenishment requisitions are submitted in a timely manner. Continued emphasis on stock replenishment will reduce the necessity for priority requisitioning. 8.170.3. Abuse of the MILSTRIP priority system creates many high-priority requisitions, which could overload the system. If this happens, priority requisitions could then be treated as routine. Customer cooperation in the correct use of the priority system is essential. 8.171. Thru 8.175. (Unused.)

Attachment 8C1 COMMERCIAL-TYPE ITEMS Group 26 26 26 31 31 31 34 35 35 37 39 40 40 40 41 41 45 47 47 47 51 51 51 51 51 51 51 53 53 53 53 53 53 53 53 53 53 53 53 55 56 59 59 59 59 Classification 10 30 40 10 20 30 39 50 90 ALL 90 10 20 30 20 41 ALL 10 20 30 10 20 30 33 36 40 80 05 06 07 10 15 20 25 30 35 40 45 50 ALL ALL 25 30 35 40 Description Tires and Tubes, Pneumatic Tires, Solid and Cushioned Tire Rebuild, and Tire and Tube Repair Material Bearings, Anti-Friction, Unmounted Bearings, Plain, Unmounted Bearings, Mounted Misc. Welding, Soldering and Brazing Supplies and Accessories Vending and Coin Operated Machines Misc. Service and Trade Equipment Agricultural Machinery and Equipment Misc. Materiel Handling Equipment Chain and Wire Rope Fiber Rope, Cordage and Twine Fittings for Rope, Cable and Chain Air Conditioning Equipment Fans Air Circulators and Blower Equipment Plumbing, Heating and Sanitary Equipment Pipe and Tube Hose and Tube Flexible Fittings and Specialties: Hose/Pipe/Tube Hand Tools, Edged, Nonpowered Hand Tools, Nonedged, Nonpowered Hand Tools, Power Driven Drill Bits, Counter-bores, and Counter Sinks: Hand and Machine Taps, Dies, and Collets: Hand and Machine Tool and Hardware Boxes Sets, Kits and Outfits of Hand Tools Screws Bolts Studs Nuts and Washers Nails, Keys and Pins Rivets Fastening Devices Packing and Gasket Material Metal Screening Misc. Hardware Disk and Stones, Abrasives Abrasive Materials Lumber, Millwork, Plywood and Veneer Construction and Building Materials Circuit Breakers Switches Connectors, Electrical Lugs, Terminals and Terminal Strips

59 59 61 61 61 62 62 62 62 62 65 65 65 65 65 65 65 65 65 65 66 66 66 67 67 67 67 67 68 71 72 74 75 Except 77 78 79 Except 80 Except Except 81 81 81 83 84 85 87 88 89

70 75 35 40 45 10 30 40 50 60 05 08 10 15 20 25 30 32 40 45 40 45 50 10 20 30 40 50 ALL ALL ALL ALL ALL 7540 ALL ALL ALL 7930 ALL 8030 8040 05 15 35 ALL ALL ALL ALL ALL ALL

Electrical Insulators and Insulation Materials Electrical Hardware and Supplies Batteries, Primary Batteries, Secondary Wire and Cable, Electrical Indoor and Outdoor Electrical Lighting Fixtures Electric Hand and Portable Lighting Equipment Electric Lamps Ballasts, Lamp Holders and Starters Nonelectric Lighting Fixtures Drugs, Biological and Official Reagents Medicated Cosmetics and Toiletries Surgical Dressing Materials Medical and Surgical Instruments Dental Instruments, Equipment and Supplies X-Ray Equipment and Supplies, Medical, Dental and Veterinary Hospital Furniture, Equipment, Utensils and Supplies Hospital and Surgical Clothing and Textile Special Purpose Items Opticians' Instruments, Equipment and Supplies Medical Sets, Kits and Outfits Laboratory Equipment and Supplies Time Measuring Instruments Optical Instruments Cameras, Motion Picture Cameras, Still Picture Photographic Projection Equipment Photo Developing and Finishing Equipment Photographic Supplies Chemicals and Chemical Products Furniture Household, Commercial Furnishings and Appliances Office Machines, Visible Record Equipment and Data Processing Equipment Office Supplies and Devices Standard Forms Musical Instruments, Phonographs and Home-type Radios Recreational and Athletic Equipment Cleaning Equipment and Supplies Cleaning and Polishing Compounds and Preparations Brushes, Paints, Sealers and Adhesives Preservatives and Sealing Compounds Adhesives Bags and Sacks Boxes, Cartons and Crates Packaging and Packing Bulk Material Textiles Only Clothing Only Toiletries Agricultural Supplies Live Animals Subsistence

Except 8970 Composite Food Packages 91* ALL Fuels, Lubricants, Oils 93 10 Paper and Paperboard 93 20 Rubber Fabricated Materials 93 30 Plastic Fabricated Materials 93 40 Glass Fabricated Materials 93 50 Refractors and Fire Surfacing Materials 93 90 Misc. Fabricated Nonmetallic Materials 94 ALL Nonmetallic Crude Materials 94 05 Wire, Nonelectrical, Iron and Steel 95 10 Bars and Rods, Iron and Steel 95 20 Structural Shapes, Iron and Steel 95 25 Wire, Nonelectrical, Nonferrous Base Metal 95 30 Bars and Rods, Nonferrous Base Metal 95 35 Plate, Sheet, Strip and Foil: Nonferrous Base Metal 95 40 Structural Shapes, Nonferrous Base Metal 95 45 Plate, Sheet, Strip, Foil and Wire: Precious Metal 96 ALL Ores, Minerals and Their Primary Products 99 ALL Miscellaneous Except 9930 Materials Cemetery and Mortuary Equipment and Supplies NOTE: * Exclusions do not apply to foreign sales made for drop-in support at airbases and naval installations, or to international agreements for use of POL facilities.

Attachment 8C2 RECOMMENDED RESEARCH PRODUCTS 8C2. The following products are available to FMS customers through FMS publications (P) cases. These case values are at least $100.00. These products are useful tools when deciding what type of requisition is initiated and what other entries are valid (i.e., NSN, NC or ND, TO, LRN, etc.). We recommend FMS customers buy, as a minimum, the following microfiche products: 8C2.1. MCRL-1. 8C2.1.1. Title: Logistics Reference Number to National Stock Numbers (NSN). 8C2.1.2. Description: An alphanumeric sequenced listing of LRN to assigned NSN(s). Used to find the NSN(s) assigned when only a part or reference number is available. (Also see MCRL3.) 8C2.1.3. Frequency: Issued two times a year with no supplements. 8C2.1.4. Estimated Costs: Has about 375 fiche. Based on the current fiche distribution, each copy costs about $19. 8C2.1.5. Availability: Can be bought on an active blanket-order publications (P) case for DoD supply catalogs or requested on a defined-order case. 8C2.2. MCRL-2. 8C2.2.1. Title: NIIN to Logistics Reference Number. 8C2.2.2. Description: A numerical sequenced listing of NIINs referenced to their applicable LRN(s). Used to find the part or reference number(s) associated with a specific NSN. 8C2.2.3. Frequency: Issued two times a year with no supplements. 8C2.2.4. Estimated Costs: Has about 325 fiche. Each copy costs about $16. 8C2.3. MCRL-3. 8C2.3.1. Title: Federal Supply Code for Manufacturer's (FSCM) and Logistics Reference Number to National Stock Number (NSN). 8C2.3.2. Description: An alphanumeric listing of LRN to NSN. Used to find out if an NSN is assigned when the MFR code and reference (part) number is known. 8C2.3.3. Frequency: Issued every three months (1 January, 1 April, 1 July, and 1 October). No change bulk items issued. 8C2.3.4. Estimated Costs: Has about 288 fiche. Each copy costs about $14. 8C2.4. ML-C. 8C2.4.1. Title: Consolidated Management Data List ML-C Basic. 8C2.4.2. Description: A numerical sequenced listing of all active NSNs with associated supply management data (i.e., source of supply (SOS), quantity unit pack (QUP), unit of issue, unit price, item name, etc.). 8C2.4.3. Frequency: For Air Force, quarterly. Can also be obtained monthly or semiannually. 8C2.4.4. Estimate Costs: Has about 585 fiche. Each copy costs about $29. 8C2.5. H-4/H-8 Series. 8C2.5.1. Title: Commercial and Government Entity (CAGE). 8C2.5.1.1. Part 1: Name to code. 8C2.5.1.2. Part 2: Code to name. 8C2.5.2. Description: 8C2.5.2.1. Part 1: An alphabetical listing of the names of US and Canadian manufacturers to assigned five-digit numeric codes (FSCM). 8C2.5.2.2. Part 2: A numerical listing of five-digit FSCM codes to the applicable manufacturer. 8C2.5.2.3. Frequency: Every two months. 8C2.5.2.4. Estimated Costs: Has 26 fiche (11 each part). Each copy (both parts) costs about $3. NOTE: The above costs are only estimates and do not constitute an agreement between the US government and the FMS customer. This attachment is not a US government commitment to provide these products. The costs shown are for planning purposes only. Microfiche costs are updated periodically and are subject to change without notice.

Attachment 8C3 FAD/UND/PRIORITY MATRIX URGENCY-OF-NEED DESIGNATOR A B C REQUISITION PRIORITY DESIGNATOR 01 04 11 02 05 12 03 06 13 07 09 14 08 10 15

FORCE/ACTIVITY DESIGNATOR I II III IV V

NOTE: Under these criteria, not more than three requisition priority designators are available to any one activity. Depending on FAD assigned, FMS NMCS requisitions must always be priority 3, 7, or 8. Priority designators are in RP 60-61 and must be numeric. If left blank, SAMIS will force a priority 15.

Attachment 8C4 FMS REQUISITION FORMATS PART IFMS REQUISITION FORMAT A01 Routing Positions (RP) Element Name Entry 1-3 Document Identifier (Doc ID)Must be A01. Use only for items with a valid NSN (verify in ML-C). 4-6 Routing Identifier (R/l) Must be either FNH (AFMC, WPAFB, Ohio) or FWX (PROS). 7 Media Status Code Must be: S DMS status to requisitioner. U DMS status to supplementary address (RP 45~50). V status by mail. W status by telex/dataphone. 0 no status to requisitioner or supplementary address. If left blank, system will force a V. 8-22 National Stock Number NOTE: See restrictions in para 17c, sec C. (NSN) 8-11 Federal Supply Class (FSC) Must be four numbers. 1. FSCs not authorized for country requisitioning -1000 SRS (complete guns), 1100 SRS (nuclear), 1300 SRS (munitions and CAD/PAD). 2. FSC in appendix B (commercial-type) enter 3B in RP 65-66. 12-13 NCB National codification bureau code. 2 numerics. 14-20 NIIN National item identification number. 7 numerics. 21-22 MMAC Materiel management aggregation code. 2 alphas. 1. Codes not authorized for any country requisitions AQ, MN. 2. Not authorized on K__ case EX, PU, XA, XL, XT, XV, XW, XX, XY, or XZ. Must be requisitioned on nonstandard or obtained on a defined-order nonstandard B or L case. 23-24 Unit of Issue (U/I) Two alphas. Enter appropriate code from the ML-C. 25-29 Quantity (QTY) Five numbers. Right-justify and prefix with zeros. Must be greater than zero. If item has QUP adjust quantity (upward) in multiples of QUP. This quantity multiplied by the unit price should be at least $10. If not, increase quantity accordingly. 30-43 Document Number 30 Service Code Must be D, signifying Air Force case. 31-32 Geopolitical Code (country) The country/activity codes are obtained from Table D-5, SAMM. 33 Mark for Code Enter code from block (33), Letter of Offer and Acceptance or latest modification. NOTE: This code must be in the MAPAD (DoD 5105.38D).

34

35

36-39

40-43

44

45-50 45

46

47

48-50

51 52-53 54-56 54 55-56

57-59 60-61

Delivery Term Code (DTC) Enter code from block (20), Letter of Offer and Acceptance or latest amendment, (block 21) or Modification, if changed. Usually 4 (freight forwarder). Must be a 2 if RP 46-47 = XW. Type Assistance (TA) Code Enter code from block (18), Letter of Offer and Acceptance or latest amendment (block 19) or modification (block 18) if changed. Usually 4 for R and E (RP 48) cases, 5 for nonstandard R and E cases (RP 48-49) and always V for FMSO II and K__ (RP 4&49) cases. Other valid codes (when authorized) include 3 (DoD stock), 6 (DoD stock, payment on delivery) or Z (credit). Document Date Enter the numeric Julian date the requisition is released for transmittal to the Air Force source of supply. Must be current or prior date not more than one year old when received. It cannot be greater than date processed into SAMIS. Serial Number See attachment 8C8, Serial Number Assignments. NOTE: Do not duplicate RP 36~43 on any other requisition (AOI A02, A04, or A05). Demand Code If Ill (RP 48-49) case, demand code can be R (recurring) or N (nonrecurring). All other country requisitions must be N. A blank is treated as an R or P. Supplemental Address In-country Service Code Enter code from block (35), Letter of Offer and Acceptance or latest Amendment or modification, if changed. Usually D (Air Force). Other valid codes (when authorized) are B (Army), P (Navy), or K (Marine) since these are the only addresses published in the MAPAD. Option Offer Release Code Entry code from block (19), Letter of Offer and Acceptance or latest amendment (block 20) or modification if changed. Usually A (automatic release to freight forwarder (FF) in RP 47). Other valid codes (when authorized) are X (DTS), Y (notice of availability (NOA) to FF ship after 15 days) or Z (NOA to FF hold for disposition). Freight Forwarder (FF) Code Enter code from block (34), Letter of Offer and Acceptance or latest amendment or modification if changed. NOTE: This code must be in the MAPAD (DoD 4000.25-8M). Case Designator Enter master case designator from block (3), Letter of Offer and Acceptance or latest amendment block (4) or modification block (4). Signal Code Leave blank (mechanically assigned). Fund Code Leave blank (mechanically assigned). Distribution Distribution Code Leave blank (system forces N). Line Item Number Code Enter the last two digits of subcase/line item number from Letter of Offer and Acceptance block (12), Amendment block (13), or modification block (12). Project Code Leave blank unless authorized by Air Force (e.g., 7BB is authorized for PACER PHANTOM F-4 post production requisitions). Priority Enter numeric issue priority based on force activity designator (FAD) and urgency-of-need designator (UND). See attachment 8C3.

62-64

Required Delivery Date (RDD) Advice Code

65-66

67-69 70 71 72 73-80

Date of Receipt Bypass Code Process Code Method of Transmission Unit Price

Leave blank unless NMCS (N in RP 62). RP 63-64 must be alpha NMCS code. NOTE: if blank, SAMIS automatically assigns a RAD for DLA managed items. Enter applicable MILSTRIP advice code or leave blank. 1. If commercial-type (Attachment 8C1) enter 3B. 2. If commercially available, LM or LP enter 2A. 3. Do not use 6P (new/unused) unless authorized on LOA. 4. Fill or kill, enter 2C. 5. Do not substitute, enter 2B. Leave blank. System forces the three-position Julian date the transaction is processed into SAMIS. RP 36-39 cannot be greater than this date. Leave blank. Leave blank. Must be A (DMS), M (mail), or (teletype). Leave blank. Stock list price assigned mechanically.

PART IIFMS REQUISITION FORMAT A02 Routing Element Name Positions (RP) 1-3 Document Identifier (Doc ID) Entry

Must be A02. Use only when:

4-6 7

8-22 8-12

1. Manufacturer's part numbers 10 positions or less (RP 13-22) and; 2. A valid manufacturer's code (RP 8-12) is available, and; 3. A valid technical order (TO) number is entered in RP 67-80. NOTE: If one or more are not available use A05. Routing Identifier (R/I) Must be FNH. This shows AFMC, WPAFB, OH. Media Status Code Must be: S DMS status to requisitioner U DMS status to supplementary address (RP 45-50). V status by mail W status by telex/dataphone 0 no status to requisitioner or supplementary address. If left blank, system will force a V. Item Identification NOTE: See restrictions in para 17c. Commercial and Must be a valid 5-digit numeric (ref H-4/H-8 series cataloging handbook). Government Entity (CAGE) Manufacturers Part Number (P/N) Left justify, suffix with blanks: Do not use spaces (blanks) or special characters (i.e., /, #, etc.). Dashes omitted except between numerics. Sample: Enter F/G-1456-2 as FG1456-2. Two alphas. Use the code assigned to a similar cataloged item since the part number is not in the ML-C. 5 numerics. Right-justify and prefix with zeros. Must be greater than zero. Must be D signifying Air Force case.

13-22

23-24 25-29 3-43 30

Unit of Issue (U/I) Quantity (QTY) Document Number Service Code

31-32 33 35

Geopolitical (country) Code Mark for Code Assistance (TA) Code

36-39

Document Date

40-43 44 45-50 45

Serial Number

46

47

48-50 51 52-53 54 55-56 57-59 60-61 62-64 65-66 67-80

Demand Code Supplemental Address In-country Service Code Enter from block (35), Letter of Offer and Acceptance or latest amendment or modification, if changed. Usually D (Air Force). Other valid codes (when authorized) are B (Army), P (Navy), or K (Marines) since these are the only addresses published in the MAPAD. Option/Offer Release Enter the code from block (19), Letter of Offer and Acceptance or latest Code amendment (block 20) or modification if changed. Usually A (automatic release to freight forwarder (FF) in RP 47). Other valid codes (when authorized) are X (DTS), Y (notice of availability (NOA) to FF ship after 15 days) or Z (NOA to FF hold for disposition). Freight Forwarder (FF) Enter code from block (34), Letter of Offer and Acceptance or latest Code amendment or modification, if changed. NOTE: This code must be in the MAPAD (DoD 4000.25-8M). Case Designator Enter master case designator from block (3), Letter of Offer and Acceptance or latest amendment block (4) or modification block (4). Signal Code Leave blank (mechanically assigned). Fund Code Leave blank (mechanically assigned). Distribution Code Leave blank. SAMIS forces N. Line Item Number Code Enter the last two digits of subcase/line item number from Letter of Offer and Acceptance block (12), amendment block (13) oblock (12). Project Code Leave blank unless authorized by Air Force (e.g., 7BB is authorized for PACER PHANTOM-F-4 Post Production requisition). Priority Enter numeric issue priority based on FAD/UND. See attachment 8C3. Required Delivery Date Leave blank unless NMCS (N in RP 62). RP 63-64 must be alpha NMCS (RDD) code. Advice Code Enter applicable MILSTRIP advice code. Do not use 3B. Normally 2A. Technical Order (TO) Enter technical order number, left justified. Must be a valid Air Force TO Number number extracted directly from applicable TO.

The country/activity code can be obtained from SAMM, appendix D, table D-5. Enter code from block (33), Letter of Offer and Acceptance or latest amendment or modification if changed. Usually 4 (freight forwarder). Enter code from block (18), Letter of Offer and Acceptance or latest Amendment (block 19) or modification (block 18) if changed. Normally 4 for R and E (RP 48) cases, 5 for nonstandard R and E (RP 48-49) cases, and always V for K (RP 48-49) cases. Enter the numeric Julian date the requisition is released for transmittal to AFMC, WPAFB, OH. Must be current or prior date not more than one year old when processed into SAMIS. Cannot be greater than the date processed into SAMIS. See attachment 8C8, Serial Number Assignments. NOTE: Do not duplicate RP 36-43 on any other requisition AO1, A02, A04, or A05). Must be N (nonrecurring).

PART III FMS REQUISITION FORMAT A04 Routing Element Name Entry Positions (RP) 1-3 Document Identifier (Doc Must be A04. Use only for NC or ND (RP 12-13) number requisitions. ID) Modification kit (K in RP 12) requisitions are input by the AFSAC case manager based on country furnished requirements.

4-6 7

Routing Identifier (R/I) Media Status Code

8-22 8-11 12-13

Item Identification Federal Supply Class (FSC) Designator

14-19 20

Serial Number Assigning Activity

21-22

MMAC

23-24 25-29 30-43 30 31-32 33

Unit of Issue (U/I) Quantity (Qty) Document Number Service Code Geopolitical (country) Code Mark for Code

Must be FNH. This shows AFMC, WPAFB, OH. Must be: S DMS status to requisitioner. U DMS status to supplementary address (RP 45-50). V status by mail. W status by telex/dataphone. O no status to requisitioner or supplementary address. If left blank, SAMIS will force a V. Important See restrictions in para 17c. Must be numeric. Do not use, FSC 1100 SRS (nuclear), 1300 (munitions and CAD/PAD). If FSC is in attachment 8C1, enter 3B, RP 65-66. Must be NC or ND. NC (noncataloged) item awaiting NSN assignment. ND (nondefinitive) number assigned by SPM/IMS for a one-time buy. NOTE: Do not submit requisitions with K (modifications) in RP 12. Must be six-digit numeric. Must be alpha. Shows ALC assigning NC or ND number. F = SM-ALC (closed due to BRAC) G = OO-ALC H = OC-ALC L = WR-ALC P = SA-ALC (closed due to BRAC) Materiel management aggregation code. Usually filled (2 alphas) but can be blank. AQ and MN codes are not authorized for any country requisitions. EX, PU, XA, XT, XV, XW, XX, XY, or XZ can be input for nonstandard items. Two alphas. Enter appropriate code from ML-C. 5 numerals. Right-justify and prefix with zeros. Must be greater than zero. Adjust upwards in increments of QUP. Must be D signifying Air Force case. The country/activity code is obtained from SAMM, appendix 5, table D-5. Enter code from block (33), Letter of Offer and Acceptance or latest amendment or modification, if changed. NOTE: This code must be in the MAPAD (DoD 4000.25-8M). Enter code from block (20), Letter of Offer and Acceptance or latest amendment or modification, if changed. Usually 4 (freight forwarder). Enter code from block (18), Letter of Offer and Acceptance or latest Amendment (block 19) or modification (block 18), if changed. Normally 4 for R and E (rp 48) cases. Always V for K (RP 48-49) cases. Usually 5 for E and R cases. Enter the numeric Julian date the requisition is released for transmittal to the Air Force source of supply. Must be current or prior date not more than one year old when received by SAMIS. Cannot be greater than date processed into SAMIS. See attachment 8C8, Serial Number Assignments. NOTE: Do not duplicate RP 36-43 on any other requisition (A01, A02, A04, or A05). If K (RP 48) case, demand code can be R (recurring) or N (nonrecurring). All other requisitions must be N.

34 35

Delivery Term Code (DTC) Type Assistance (TA) Code

36-39

Document Date

40-43 44 45-50

Serial Number Demand Code Supplemental Address

45

46

47

48-50

51 52-53 54-56 54 55-56

57-59 60-61 62-64 65-66

67-69 70 71 72 73-80

In-country Service Code Enter code from block (35), Letter of Offer and Acceptance or latest amendment or modification, if changed. Usually D (Air Force), can be B (Army), P (Navy), or K (Marines), if authorized on the LOA. Option/Offer Release Enter the code from block (19), Letter of Offer and Acceptance or latest Code amendment or modification, if changed. Usually A (automatic release to freight forwarder (Fl) in RP 47). Other valid codes (when authorized) are X (DTS), Y (notice of availability (NOA) to FF ship after 15 days) or Z (NOA to FF hold for disposition). Freight Forwarder (FF) Enter code from block (34), Letter of Offer and Acceptance or latest Code amendment or modification, if changed. NOTE: This code must be in the MAPAD (DoD 5105.38D). Case Designator Enter master case designator from block (34), Letter of Offer and Acceptance or latest amendment (block 4) or modification (block 4). Signal Code Leave blank (mechanically assigned). Fund Code Leave blank (mechanically assigned). Distribution Distribution Code Leave blank. System forces N. Line Item Number Code Enter the last two digits of subcase/line item number from Letter of Offer and Acceptance (Block 12), amendment (Block 13) or modification (block 12). Project Code Leave blank unless authorized by Air Force (e.g., 7BB is authorized for PACER PHANTOM F-4 Post Production requisitions). Priority Enter numeric priority based on FAD/UND. See attachment 8C3. Required Delivery Date Leave blank unless NMCS (N in RP 62). RP 63-64 must be alpha NMCS (RDD) code. Advice Code Enter applicable MILSTRIP advice code or leave blank. If commercial-type (Attachment 8C1) enter 3B. Do not use 6P (new/unused) unless authorized on LOA. Fill-or-kill, enter 2C. Date of Receipt Leave blank. System will force the Julian date the transaction is processed into SAMIS. RP 36-39 cannot be greater than this date. Bypass Code Leave blank. Process Code Leave blank. Method of Transmission Must be A (DMS), M (mail) or T (teletype). Unit Price Leave blank.

PART IVFMS REQUISITION FORMAT A05 Routing Element Name Positions (RP) 1-3 Document Identifier 4-6 7 Routing Identifier (R/I) Media Status Code Entry

8-22

Item Identification

23-24 25-29 30-43 30 31-32 33

Unit of Issue (U/I) Quantity (Qty) Document Number Service Code Geopolitical (country) Code Mark for Code

Must be A05. Use only if item does not qualify for A01, A02, orA04. Must be either FNH (AFMC, WPAFB, OH), FWX (PROS), or FXA (PROS II). Must be: S DMS status to requisitioner. U DMS status to supplementary address (RP 45-50). V status by mail. W status by telex/dataphone. O no status to requisitioner or supplementary address. If left blank, system will force a V. NOTE: See restrictions in para 17c. Entries in these RP are optional. Options include: FSC (RP 8-11) and part number (RP 12-22). FSCM (RP 8-12) and part number (RP 13-22). Part number (RP 8-22). Blank The preferred method is part number. Enter appropriate unit of issue for a like stock numbered item. Five numerics. Right-justify and prefix with zeros. Must be greater than zero. Must be D signifying Air Force case. The country/activity code can be obtained from SAMM, appendix D, table D-5. Enter code from block (33), Letter of Offer and Acceptance or latest amendment or modification if changed. NOTE: This code must appear in the MAPAD (DoD 4000.25-8M). Enter code from block (20), Letter of Offer and Acceptance or latest amendment or modification, if changed. Usually 4. Enter code from block (18), Letter of Offer and Acceptance or latest amendment (block 19) or modification (block 18), if changed. Usually 4 for R and E cases, 5 for nonstandard E or R cases, and always V for K cases. Enter the numeric Julian date the requisition is released for transmittal to the Air Force source of supply. Must be current or prior date not more than one year old when received by SAMIS. Cannot be greater than date processed into SAMIS. See attachment 8C8, Serial Number Assignments. NOTE: Do not duplicate RP 36-43 on any other requisition (A01, A02, A04, or A05). If KB case (RP 48-49), use R (recurring) or N (nonrecurring). All other requisitions must be N. Enter code from block (35), Letter of Offer and Acceptance or latest amendment or modification, if changed. Normally D (Air Force), can be B (Army), P (Navy), or K (Marines), if authorized on the LOA.

34 35

Delivery Term Code (DTC) Type Assistance (TA) Code

36-39

Document Date

40-43

Serial Number

44 45-50 45

Demand Code Supplemental Address In-country Service Code

46

47

48-50 51 52-53 54-56 54 55-56

57-59 60-61 62-64 65-66 67-71 72 73-80

Option/Offer Release Code Enter the code from block (19), Letter of Offer and Acceptance or latest amendment or modification, if changed. Usually A (automatic release to freight forwarder). Freight Forwarder (FF) Enter code from block (34), Letter of Offer and Acceptance or latest Code amendment or modification, if changed. NOTE: This code must appear in the MAPAD (DoD 4000.25-8M). Case Designator Enter the designator from block (3), Letter of Offer and Acceptance or the latest amendment 1 (block 4) or modification (block 4). Signal Code Leave blank (mechanically assigned). Fund Code Leave blank (mechanically assigned). Distribution Distribution Code Leave blank. System forces N. Line Item Number Code Enter the last two digits of subcase/line item number from Letter of Offer and Acceptance (block 12), amendment (block 13) or modification (block 12). Project Code Leave blank unless authorized by Air Force (e.g., 7BB is authorized for PACER PHANTOM F-4 Post Production requisitions). Priority Enter numeric priority based on FAD/UND. See attachment 8C3. Required Delivery Date Leave blank unless NMCS (N, RP 62). RP 63-64 must be alpha. (RDD) Advice Code Must be 2A. Leave blank. Method of Transmission Must be M (mail) or T (teletype). Leave blank.

Remarks Field: Furnish DD Form 1348. 1. Technical order number 2. Figure/index number 3. Page number 4. CAGE 5. LRN 6. Estimated unit cost 7. System/end-item application

Attachment 8C5 REQUISITION CHECKLIST Routing Position(s) (RP) 1-3 Element Name Document Identifier (Doc ID) Applicable to: A02 A04 X X X 4-6 7 8-22 Routing Identifier (R/I) Media/Status Item Identification X X X X X X X X X

A01 X

A05

Entries A01 if valid NSN. A02 if valid CAGE, part number, and TO. A04 if NC or ND. A05 if none of the above. Always FNH. Must be S, U, V, W, or O. See restrictions paragraph 3, Section A. Valid NSN. FSCM and part number. NC or ND stock number. Optional: FSC and part number FSCM and part number Part number (preferred) Blank U/I from ML-C. U/I of like-stock numbered item. 5 numerics, right-justified, pre-fixed with zeros. Must be greater than zero. Use increments of QUP from ML-C.

X X X

23-24 25-29

Unit of Issue (U/I) Quantity (QTY)

X X X X

X X X X

30-43 30 30-31 33 34

Document Number Service Code Country Code Mark-for Code Delivery Term Code (DTC) Type Assistance Code (TA)

X X X X X X

X X X X X

X X X X X X

X X X X X Always D (Air Force). Valid country/activity (geopolitical) code. Take from latest Letter of Offer and Acceptance, Amendment or Modification. Usually 5. Take from latest Letter of Offer and Acceptance, Amendment or Modification. Usually: 4 for R and E cases, 5 for non-standard R and E cases; always V for K__ cases and FMSO II cases. Usually todays Julian date. Can be prior, not more than one year old when processed by SAMIS.

35

36-39

Document Date

40-43

Serial Number

44

Demand Code

Must be numeric between 0001 and 4999. Do not duplicate RPs 36-43 on any other requisition (A01, A02, A04, or A05). If K__ (RP 48-49) case, can be R (recurring), N (nonrecurring), or P (drawdown). All others must be N. If K__ case, can be R or N; all others must be N. NOTE: All blanks treated as R.

45-50 45

Supplemental Address In-country Service Code

X X

X X

X X

X X Usually D (Air Force). Take from latest Letter of Offer and Acceptance, Amendment or Modification. Can be B (Army), P (Navy), or K (Marines), if authorized on the LOA. Usually A (automatic release to FF). Take from latest Letter of Offer and Acceptance, Amendment or Modification. Take from latest Letter of Offer and Acceptance, Amendment or Modification. Must be in MAPAD (DoD 5105.38D). Use master case designator (block 3 or 4 of latest Letter of Offer and Acceptance, Amendment or Modification. Always blank (mechanically assigned). Always blank (mechanically assigned). Enter the last two digits of subcase/line item number from block 12 of Letter of Offer and Acceptance, block 13 of Amendment, or block 12 of Modification. Use only Air Force-authorized codes (e.g., 7BB, F-4 postproduction); otherwise leave blank. See attachment 8C3. Leave blank unless NMCS (N in RP 63) and RPs 63-64 must be alpha. If commercial-type (Attachment 8C1) use 3B. If LM/LP use 2A. Do not use 6P. Fill or kill, use 2C. use 2A. Always blank. Enter valid TO number. Must be A (DMS), M (mail), or T teletype/mess-age). Cannot be A. Can be M or T. Leave blank (system- or AFSACassigned).

46

Option/Offer Release Code Freight Forwarder (FF) Case Designator Signal Code Fund Code Line Item Number Code

47

48-50

51 52-54 55-56

X X X

X X X

X X X

X X X

57-59

Project Code

60-61 62-64

65-66

Priority Required Delivery Date (RDD) Advice Code

X X

X X

X X

X X

X X

X X X X X X X X X

67-68 67-80 72

X TO Number Method of Transmission Unit Price X

73-80

Attachment 8C6 CUSTOMER REQUISITION FORMAT

Attachment 8C7 FMS ROUTING MEDIA PROCESS CODE (RP 71) CODE EXPLANATION CODE A B C D E F G K M N R S EXPLANATION Routing identifier code (RIC) is assigned by SAMIS based on FSC or MMAC. Referral order and status is forwarded. Referral order listing is provided. Not valid for A05 or A35 requisitions. RIC is assigned by SAMIS. Referral or passing order is forwarded. No status is provided. Referral order listing is provided. Not valid for A05, A35, or A04 requisitions. AFSAC assigns RIC. No referral or passing order is forwarded. No referral order listing is provided. SAMIS assigns RIC. Referral or passing order is forwarded. Referral order listing and status are provided. Not valid for A05, A35, or A04 requisitions. SAMIS assigns RIC. No referral or passing order is forwarded. Referral order listing and status are provided. AFSAC assigns RIC. No referral or passing order is provided. No status is provided. Referral order listing is provided. AFSAC assigns RIC. No referral or passing order is forwarded. No referral order listing or status is provided. The requisition is to be rejected to the customer SAMIS assigns RIC. No referral or passing order is forwarded. Referral order listing and status is provided. Not valid for A04. PROS requisitions (RIC FWX or FXA). AFSAC assigns RIC (no edit on RIC). Referral or passing order is forwarded. Referral order listing and status is provided. Not valid for A05 or A35 requisitions. SAMIS assigns RIC based on FSC or MMAC. Used to indicate single vendor integrity coded requisitions. Referral order is forwarded. Referral order listing and status is provided. Not valid for A05 or A35 requisitions. AFSAC assigns RIC. Applies to A05 and A35 manual requisitions. No referral or passing order is forwarded. Referral order listing and status is provided. AFSAC assigns RIC. No referral or passing order is forwarded. Status and referral order listing with referral order card is provided SAMIS assigns RIC. Referral or passing order is forwarded. Status is provided. No referral order listing is provided. Not valid for A05 or A35 requisitions.

T X Blank

Attachment 8C8 SERIAL NUMBER ASSIGNMENTS SERIAL NUMBER Less than 5000 5000-5799 5800-6599 6600-7399 7400-7499 7500-7599 7600-7999 8000-8999 8000-8099 8200-8299 9000-9999 A000-B499 A000-A999 B000-B999 C000-C999 C000-C999 D000-D999 E000-E199 H000-H199 H200-H399 H400-H599 H600-H799 H800-H999 VOOO-V999 * Deleted due to BRAC closure. USER Customer submitted OO-ALC SA-ALC* WR-ALC OC-ALC SM-ALC* AFSAC Grant aid Reparable return WR-ALC (IS; F-15) WR-ALC (SR; F-15) AF Supply Directives (reserved) OC-ALC (SR; E3A) OC-ALC (BE; F-16) OC-ALC (DE; F-16) OC-ALC (NE; F-16) SM-ALC (SR; PEACE SHIELD)* OC-ALC (NO; F-16) AFMATCAL-DET-1/MLSS WR-ALC (repair/replace requisition) SA-ALC (repair/replace requisition)* SM-ALC (repair/replace requisition)* OC-ALC (repair/replace requisition) OO-ALC (repair/replace requisition) Drawdown requisitions

Attachment 8C9 REQUEST FOR INFORMATION FORM

Attachment 8C10 AMARC PROCESS DEPICTION

START PROS Cancel (D.3) to SAMIS

FMS Non-Standard Requisition

IM Receives Requisition

PROS PMO Force-Routes Requisition to SPD

Yes Item in Stock? No SAMIS Transfers Requisition to PROS

SPD Fill Ship FMS Non-Standard Requisition C0R

SAMIS Passes Requisition to SPD

PMO Drops Requisition to PROS for Repair (New Requisition)

SPD Passes Requisition to AMARC

Requisition Received/ Processed by PROS Buy / Make

AMARC Pulls Asset and Determines Condition

Buy / Make, or Not-Available N/A SPM Determine Requisition Eligibility for AMARC

PROS Fill Ship FMS Non-Standard Requisition

Condition Code A, R, or F? Code R or F AMARC Ship to PROS Repair

Code A

AMARC Fill Ship FMS Non-Standard Requisition

No

AMARC Eligible? Yes

PROS Fill Ship Repaired FMS Non-Standard Requisition

No

AMARC Available Yes PROS Message to Country For Appoval

No

Country Approval? Yes

Attachment 8D1 ROUTING IDENTIFIER CODES FOR CUSTOM COMMITMENTS CODE FA3 FGZ FHZ FLZ FMS FNZ FXA DZJ EXPLANATION AFMATCAL-DET-1/MLSS OO-ALC performed service OC-ALC performed service WR-ALC performed service NIPARS performed service WPAFB performed service PROs performed service (CORs, COPs, and COSs only) ASQNV-JVIA-T-AS

Attachment 8D2 AIR FORCE APPROPRIATION CODES CODE A B C D E F G H 7 Blank EXPLANATION 3010 Aircraft Procurement 3020 Missile Procurement 3080 Other Procurement 3400 Operations and Maintenance 3041 Receipt Account 4922 Industrial Fund 3500 Military Personnel 4116 Special Defense Acquisition Fund Direct Cite Other Reimbursable

Attachment 8F1 WORKSHEET FOR FINANCIAL ANALYSIS

Attachment 8F2 FINANCIAL ANALYSIS A - DEFINED ORDER CASE/LINE

CASE IDENTIFIER:

-D-

MAIN SYSTEM/ITEM/SERVICE: CASE LINE ITEM: (Sub-case) DESCRIPTION: QTY: AVAILABILITY:

PREPARED BY: (Name)/(Org/Symbol/Phone Ext) APPROVED BY: (Name)(Org/Symbol/Date) DATE APPROVED: NSN, IF APPLICABLE STANDARD/NONSTANDARD: SOURCE OF SUPPLY: (S, P, X, R, or E) PRICING TECHNIQUE

A. SOURCE OF ITEM: (1) EXCESS INVENTORY (2) INVENTORY (WITHOUT REPLACEMENT) INVENTORY REPLACEMENT WITH SAME ITEM) (3) (4) INVENTORY (REPLACEMENT WITH IMPROVED ITEM) (5) PRODUCTION (6) OTHER B. SOURCE OF PRICE (Check one or more) (1) PRIME CONTRACTOR (2) PRIME AND GFE CONTRACTOR STANDARD PRICE (4) MAJOR SUBORDINATE COMMAND (3) ESTIMATE (5) OTHER (explain) C. UNIT PRICE: D. ADJUSTED PRICE (Explain source and computations in Remarks) (1) AGENTS FEES OR COMMISSIONS (2) NONRECURRING COSTS (RDT&E) (3) NONRECURRING COSTS (PRODUCTION) REPLACEMENT COSTS (4) (5) ADJUSTED FOR INFLATION (6) ASSET USE CHARGE (if included in end item) (7) UNFUNDED COSTS (explain) (8) RECURRING SUPPORT COSTS CONTRACT GOVERNMENT (9) FIRST DESTINATION TRANSPORTATION (if included in end item) (10) CAS/AUDIT (1.5% of costs of P source of supply unless waived. If waived, explain). See para N if overseas CAS is in proposed LOA. (11) OTHER (explain) TOTAL ADJUSTMENT (12) E. ADJUSTED UNIT PRICE F. APPLICABLE ACCESSORIAL CHARGES PC&H : Asset Use of S/X ; Transp ; Staging G. Budgeted or ongoing service procurement price and source (explain if significantly different from proposed sale price)

Attachment 8F2 (Continued)

H. Comparison with current USAF cost Contract Stock (if G is not applicable) I. Comparison with other cases (12 months) CASE UNIT PRICE RATIONALE FOR DEVIATION -D(1) -D(2) J. Source of Schedule of Payments (if payment schedule requested in P&A tasking) (1) PRIME CONTRACTOR (2) PRIME AND GFE CONTRACTOR (3) MAJOR SUBORDINATE COMMAND ESTIMATE OTHER (explain) (4) K. Remarks and other information (use continuation sheets, as necessary). L. other backup required by AFMAN 16-101: (List here and attach) (e.g., paragraph 7-9 Manpower). (3) (1) (4) (2) M. Financial Analysis Form C is not attached. N. If overseas CAS is included in LOA, also include following information: (1) Reasons for overseas CAS. (2) General function. (3) Why it cannot be reimbursed from normal CAS fund at SAAC. (4) Describe duties of personnel. (5) Cost breakout to include: Salary, acceleration factors, travel, housing, dependent travel, etc. (6) Other pertinent information. NOTES: (1) You may handscribe this analysis, but write legibly. (2) Fill in all blanks with appropriate information or N/A.

Attachment 8F3 FINANCIAL ANALYSIS B BLANKET ORDER CASE/LINE

CASE IDENTIFIER MAIN SYSTEM/ITEM/SERVICE DESCRIPTION SOURCE OF SUPPLY

PREPARED BY (Name)/(Org/Symbol) DATE PREPARED APPROVED BY (Name)(Org/Symbol/Date)

(S, P, or X) CEILING PRICING TECHNIQUE a. SOURCE (check one or more) Purchasers Request (1) (2) Historical Data (3) Previous Case (4) Requisitions Against Previous Case Other (explain) (5) b. Explain why ceiling price is other than requested c. Comparison with other cases (12 months) CASE UNIT PRICE RATIONALE FOR DEVIATION -D(1) (2) -Dd. Remarks and other information (use continuation sheets, as necessary). e. Other backup required by AFMAN 16-101: (List here and attach) (1) (3) (2) (4) NOTES: (1) You may handscribe this analysis, but write legibly. (2) Fill in all blanks with appropriate information or N/A.

Attachment 8F4 NONRECURRING COST RECOUPMENT CHARGES SUMMARY

Attachment 8F5 FIVE-YEAR MUNITIONS PROJECTION SURVEY

Attachment 8F6 TASK WORK SPECIFICATION

1. 2. 4. 5. 5. 6.

USING ACTIVITY: CONTRACTOR: EQUIPMENT/SYSTEMS: NUMBER OF PERSONNEL REQUIRED: LINE ITEM: GENERAL: The primary purpose of Contractor Engineering and Technical Services (CETS) is to provide on-site advice, liaison and informal training in the installation, operation and maintenance of equipment and systems related to the equipment/systems identified above. The object of the Contractor Engineering and Technical Services (CETS) is to elevate the technical skills and abilities of the personnel responsible for the operation and maintenance of the above equipment/systems to a level of self-sufficiency. WORK SPECIFICATION: The contractor shall provide the Contract Field Services to accomplish the purpose and objective specified in paragraph 6 above. Specific delineation of tasks is to include but not necessarily be limited to the following: a. Provide on-site/on-equipment informal unit training to the component personnel on installation, maintenance and operating techniques pertaining to the adjustment, calibration, trouble-shooting, bench check, routine maintenance, inspection and repair of the prime equipment/system. Provide advice in the identification of and instruction on the use of special tools, handling equipment, aerospace ground equipment (AGE) and test equipment associated with and related to paragraph 3. Devise local informal training programs and provide advice in identifying needed training programs. Emphasize safety precautions to be taken in all training provided. Demonstrate best methods of installing modifications and retrofit kits. Render technical advice to resolve difficult and unusual maintenance problems. Provide consistent analysis of maintenance difficulties. Provide advice on the establishment of maintenance, inspection and training programs designed to improve the quality of maintenance, recommending changes as applicable. Provide liaison through which information related to maintenance and operational problems, available in the manufacturers plant can be quickly disseminated to operations and maintenance personnel. Provide training on the use and interpretation of applicable technical orders.

7.

b. c. d. e. f. g.

h. i.

Attachment 8F6 (Continued)

j. 8.

Provide advice as requested to assist in accident investigation and preparing failure data reports and unsatisfactory reports.

REQUIRED QUALIFICATIONS OF CONTRACTOR PERSONNEL: a. b. c. d. Knowledge of the learning process and how to transfer knowledge to less qualified personnel, including the ability to express thought in both oral and written communications. (Instructor Training Ability) Possess the ability to work independently without technical guidance to perform all tasks outlined in the work specifications. Be experienced in theory, maintenance and repair of all aspects of the Equipment/Systems of paragraph 3. Possess a high degree of tact, diplomacy and the ability to work and cooperate harmoniously with military and civilian personnel.

9.

ADMINISTRATIVE INFORMATION: a. b. c. d. e. f. g. h. Duration of Services?: TDY Anticipated?: Security Clearance Required? (If so, what level?): Private vehicle required or transportation furnished by country?: Will the country provide a driver if private vehicle is required?: Will CETS representatives be exempt from import and export duties if private vehicle is required?: Will CETS representatives be exempt from personal income taxes? (if not, What rate of taxation applies?): Will US logistics support be provided to include: Base Exchange, Class VI, Dry Cleaning and Laundry Services Commissary Banking to include Check Cashing privileges Vehicle Registration Gas and Oil Mail and Electronic Communications Emergency medical and dental services Recreational facilities Adequate working space at no charge General Base privileges CETS in bachelor status will not be granted dependents school, but CETS in accompanied status may use dependents schools charged at a rate set by the schools operator. 12. CETS dependents may use the overseas base theaters with MAJCOM approval 1. 2. 3. 4. 5. 6. 7. 8. 9. 10. 11.

Attachment 8F6 (Continued)

i. j. k. l.

Are Government Quarters available? (if not, what is the average cost of commercial quarters and meals): Distance from operating location to suitable quarters?: Duty Hours observed?: Work week observed?:

m. Overtime Anticipated?: n. o. p. q. Holidays observed by the CETS Representative?: Report to Instructions?: Certifying Official or Designee?: The CETS representative shall report to the Unit Security Manager and must have a valid favorable National Agency Check (NAC).

Attachment 8G1 INELIGIBLE CLSSA FMSO I ITEMS 8G1.1. Nonstandard items. Items which the U.S. does not manage for its own use. Nonstandard items are identified by the following MMCs: EX, PU, XA, XG, XL, XT, XU, XV, XW, XX, XY, XZ. 8G1.2. Part numbered items where no National Stock Number (NSN) exists. 8G1.3. NC, ND, and K numbered items. 8G1.4. Commercial Consumable Items. 8G1.5. Local purchase and local manufacture items. 8G1.6. Item with Physical Security Codes other than U, J, and 7. 8G1.7. Items with ineligible Acquisition Advice Codes (AAC) or Phrase Codes: 8G1.7.1. AACs A, F, G, H, I, J, L, N, O, P, R, S, T, U, V, X, Y. 8G1.7.2. Phrase Codes C, M, N, P, Q, T, V, 5, 6 and 9 8G1.8. Munitions and munitions related items: 8G1.8.1. All items in: FSG 13 (Ammunition), FSG 11 (Nuclear Ordinance) and FSC 4925 (Ammunition Maintenance and Repair Shop Specialized Equipment). 8G1.8.2. AQ MMC items (Ammunition and Explosives), MN MMC items (Complete Round Components), and JB MMC items (AGM-65 Maverick Missile). 8G1.9. Major Missile Components and subsystems (specific NSNs). 8G1.10. Support Equipment (ERRC S and U). 8G1.11. Other U.S. military service managed items. 8G1.12. Communications Security (COMSEC) itemsFSC 5810 and 5811, and MMC CA, CI, CS. 8G1.13. DLA managed items with an AAC other than D, H, or Z. 8G1.14. Investment items not stocked by the USAFNIMSC 5.

Attachment 8G2 XD2-3 FORMAT 8G2.1. This transaction is used for CLSSA Initial and Major Add Program Recommendations. The recommendation data is provided by the SPD in the XD2-3 format. SAMIS processes the XD2-3 transactions and produces listing of eligible and ineligible CLSSA items for country review and approval. XD2-3 FORMAT Record Position Data Entry 1-3 XD2-3 4-6 FNH 7 3 8-20 NSN 21-22 MMC 23-24 Unit of Issue 25-30 Quantity (prefix with zeroes) 31-32 Country Code 33-35 FMSO I Case Designator 36-40 Blank 41-43 (See below.) CLSSA Data Identifier Code 8G2.2. The CLSSA Data Identifier Code is a unique three position identifier and is required to distinguish reparable item procurement and consumable item levels (N) from the reparable repair levels (H). The third position of the identifier code must be an N or an H.

Attachment 8G3 XD3-3, XD3-6, XD3-7 FORMAT 8G3.1. XD3-3 Format. 8G3.1.1 This transaction is used by the CLSSA customer or AFSAC case manager to add an item to the original FMSO I recommendation. Position 1-3 4-6 7 8-22 23-24 25-30 31-32 33-35 36-40 41-43 Data Entry XD3 FNH 3 Stock Number Unit of Issue Quantity (prefix with zeroes) Country Code FMSO I Case Identifier Blank CLSSA Data Identifier Code (see below)

8G3.1.2. The CLSSA Data Identifier Code must match the code shown in the CLSSA Recommendation Listing Report. Multiple CLSSA Identifier Codes may be in use at one time, so be sure the correct code is used. 8G3.2. XD3-6 format. 8G3.2.1. This transaction is used by the CLSSA customer or AFSAC case manager to increase the quantity of an item on the original FMSO I recommendation. 8G3.2.2. The CLSSA Data Identifier Code must match the code shown in the CLSSA Recommendation Listing Report. Multiple CLSSA Identifier Codes may be in use at one time, so be sure the correct code is used. XD3-6 FORMAT Data Entry XD3 FNH 6 Stock Number Unit of Issue Quantity (show quantity of increase) (prefix with zeroes) Country Code FMSO I Case Identifier Blank CLSSA Data Identifier Code (see below)

Position 1-3 4-6 7 8-22 23-24 25-30 31-32 33-35 36-40 41-43

8G3.3. XD3-7 Format. 8G3.3.1. This transaction is used by the CLSSA customer or AFSAC case manager to decrease the quantity of an item on the original FMSO I recommendation.

Position 1-3 4-6 7 8-22 23-24 25-30 31-32 33-35 36-40 41-43

XD3-7 FORMAT Data Entry XD3 FNH 7 Stock Number Unit of Issue Quantity (show quantity of decrease) (prefix with zeroes) Country Code FMSO I Case Identifier Blank CLSSA Data Identifier Code (see below)

8G3.3.2. The CLSSA Data Identifier Code must match the code shown in the CLSSA Recommendation Listing Report. Multiple CLSSA Identifier Codes may be in use at one time, so be sure the correct code is used. 8G3.4. XD3-8 format. 8G3.4.1. This transaction is used by the CLSSA customer or AFSAC case manager to delete an item on the original FMSO I recommendation. XD3-8 FORMAT Data Entry XD3 FNH 8 Stock Number Blank Blank Country Code FMSO I Case Identifier Blank CLSSA Data Identifier Code (see below)

Position 1-3 4-6 7 8-22 23-24 25-30 31-32 33-35 36-40 41-43

8G3.4.2. The CLSSA Data Identifier Code must match the code shown in the CLSSA Recommendation Listing Report. Multiple CLSSA Identifier Codes may be in use at one time, so be sure the correct code is used.

Attachment 8G4 SAMIS SLQ COMPUTATION EXAMPLE 8G4.1. On the first day of each quarter SAMIS will get the past four years of FMSO II case recurring demand for each NSN for each country. The demands are divided into 16 quarters. 8G4.2. Using the 16 quarters demand, SAMIS will compute the AMD. In the computation, older requisitions are weighted less than newer requisitions when there are breaks in the quarterly requisition pattern. SAMIS applies a weighting factor to each of the quarter amounts. The weighting factor starts at 100% and is reduced by 6.25% (100%/16 quarters = 6.25%) each time there is a zero quantity for a quarter. In this example quarter one is the most recent. SAMIS SLQ COMPUTATION EXAMPLE REQUISITION WEIGHTING FACTOR WEIGHTED REQUISITION QUANTITY QUANTITY 2 100.00 2.0000 1 100.00 1.0000 0 93.75 0.0000 0 87.50 0.0000 2 87.50 1.7500 2 87.50 1.7500 1 87.50 0.8750 1 87.50 0.8750 0 81.25 0.0000 0 75.00 0.0000 0 68.75 0.0000 1 68.75 0.6875 0 62.50 0.0000 0 56.25 0.0000 0 50.00 0.0000 1 50.00 0.5000 11 9.4375

QUARTER 1 2 3 4 5 6 7 8 9 0 11 12 13 14 15 16 TOTAL

8G4.3. SAMIS then divides the total weighted requisition quantity (9.4375) by 48 months to determine the AMD. In this example 9.4375/48 equals 0.1966. The weighted quantity (9.4375) will normally be less than the non weighted requisition quantity (11). 8G4.4. The AMD is multiplied by the procurement lead-time to determine the procurement SLQ. If the SLQ computes to less than one, it is rounded to one. If the SLQ is above one, the 0.5 rule is used (less than 0.5 is rounded down, 0.5 and greater is rounded up.) Procurement SLQ example: 0.1966 x 24MO PLT = 4.7 = 5. 8G4.5. This same logic is used for the Repair SLQ but SAMIS uses days instead of months because the repair time in the catalog is in days and not months. 8G4.6. The CLSSA Stock Level Item Query report (QA 456) shows the 16 quarter demand history data, the procurement and repair lead-times, and the unrounded and rounded SLQ. (The AMD can be computed as the unrounded SLQ divided by the lead time.)

Attachment 8G5 LIABILITY FILE PROCESSING EXAMPLE 8G5.1. Whenever the SLQ is reduced, the reduced quantity is moved to the Liability File for processing. In the following example for one country, the SLQ is decreasing over four quarters. In each quarter the amount of the reduction moves into the Liability File for processing. Each entry will be identified by country and date. SINGLE COUNTRY LIABILITY FILE PROCESSING EXAMPLE SLQ COUNTRY LIABILITY FILE LIABILITY FILE ENTRY DATE QUANTITY 10 8 UT January 2 7 UT January 2 UT April 1 4 UT January 2 UT April 1 UT July 3

QUARTER 1 2 3 4

8G5.2. Once in the Liability File, an item can be removed in three ways: 8G5.2.1. First: 8G5.2.1.1. FMS Non-H-coded (non-repair and replace) requisitions that process through SAMIS will be used to remove items from the Liability File. When an item is removed from the Liability File (and not moved to the customers Stock Level or Termination File), the customer's liability for that NSN/quantity is cleared. The customer is no longer liable for it. (Exceptions: Requisitions with advice codes 6P (New and Unused), BV, 6V, 6W (Sole Source), and 2C, 2J, 22, 31, 32, 33 (Do Not Substitute) are not used to clear liability. This is because these codes do not allow the IM to consider all assets when filling the requisition, and therefore, cant be used to clear Liability File items.) 8G5.2.1.2. Quantities will be removed from the Liability File first for the country that input the transaction, and then on a first-in first-out alphabetical basis by the date the NSN entered the Liability File. 8G5.2.1.3. Example. The following example shows a Liability File with multiple countries and multiple entry dates. NSNs/quantities are placed in the Liability File on the first day of the quarter, so it is possible for multiple countries to have entries with the same date. To simplify the example, actual dates arent used, instead date 1 is the oldest entry, date 3 is the newest entry. MULTIPLE COUNTRY LIABILITY FILE PROCESSING EXAMPLE RECORD NUMBER COUNTRY LIABILITY FILE DATE LIABILITY FILE QUANTITY 1 DD DATE 1 2 2 EE DATE 1 2 3 AA DATE 2 1 4 CC DATE 2 2 5 DD DATE 2 1 6 EE DATE 2 1 7 FF DATE 2 1 8 BB DATE 3 2 9 CC DATE 3 1 10 DD DATE 3 3

8G5.2.1.3.1. Example 1: If a requisition is received from country CC for quantity 9, records 4, 9, 1, 2, 3, and 5 will be cleared. Records 4 and 9 are for country CC, the first-in first-out alphabetical rule applies for the other records. 8G5.2.1.3.2. Example 2: If a requisition is received from country GG for quantity 9,.records 1, 2, 3, 4, 5, and 6 will be cleared based on the first-in first-out alphabetical rule since country GG has no Liability File entries. 8G5.2.1.3.3. Example 3: If a requisition is received from country CC for quantity 4,.records 4 and 9 will be cleared and record 1 will be reduced by 1. Records 3 and 4 are for country CC, the first-in first-out alphabetical rule applies for the other record. 8G5.2.2. Second: If the SLQ increases, a corresponding quantity will be removed from the Liability File. The liability for the removed items will be accounted for by the increased stock level. Quantities will be removed from the Liability File by country first and then on a first-in first-out alphabetical basis by date. Example: If the stock level for country AA increases, SAMIS will remove Liability File NSN/quantities for country AA, if it exists. If there is no country AA liability, SAMIS will remove NSN/quantities from the Liability File using the first-in firstout alphabetical rule. 8G5.2.3. Third: If there has been no recurring demand by any FMS customer for an NSN in four years, the NSN/quantity will be moved to the Termination File.

Attachment 8G6 ABSORPTION REVIEW AND DRAWDOWN REQUISITION PROCESSING 8G6.1. Description of the Absorption Request Form: The CLSSA Termination Absorption Request: (U-W001.GAV) is divided into three parts: 8G6.1.1. Part one shows cataloging data, NSN, etc, and the quantity for which absorption is requested. 8G6.1.2. Part two provides a brief description of the reason for the absorption request. 8G6.1.3. Part three is for the IM to enter data. It looks like this: ABSORPTION REQUEST FORM REVIEW THE LAST FINAL REQUIREMENTS COMP. INDICATE WHETHER THE ITEM IS OVER, OPTIMUM, OR SHORT AT THE 3RD-TERM POINT OVER.......________ INDICATE OVER QUANTITY......_______ OPTIMUM....________ SHORT......________ INDICATE SHORT QUANTITY....._______ INDICATE UNFUNDED OWRM QUANTITY: _________ INDICATE NONPROGRAMMED FMS BACKORDER QUANTITY: _________ D200A COMPUTATION DATE: _________ ITEM MANAGER SIGNATURE: ______________________________ DATE:________ 8G6.2. Instructions for Completing the Form: 8G6.2.1. The form is self explanatory, for the most part. The following paragraphs provide additional detail and instructions for two special circumstances. 8G6.2.2. FMS Non-programmed Backorder Quantity: In this field show the total of FMS NP,BB,B4 AND B5 FMS non-programmed non-H-coded backorders that you don't intend to buy using FMS case funds. In other words, don't count non-programmed non-H-coded requisitions with BZ or BV status, or those backorders that will get BZ or BV status. 8G6.2.3. Insurance/Numeric Stockage Objective (NSO) Items. These items require special attention. Use the following process to determine the values to enter in the form: 8G6.2.3.1. Step 1: 8G6.2.3.1.1. If the REQUEST QUANTITY is included in the retention quantity, compute an Adjusted Retention quantity using the formula: Retention quantity minus the REQUEST QUANTITY. 8G6.2.3.1.2. If the REQUEST QUANTITY is not part of the retention quantity, no adjustment is necessary: 8G6.2.3.2. Step 2: Use the formula Asset Level minus the Retention (Adjusted Retention) Level to determine the OVER (positive number), SHORT (negative number) or OPTIMUM (zero) position. For example: ADJUSTED RETENTION QUANTITY EXAMPLE EX 1 EX 2 EX 3 Asset Level: 15 20 25 Retention (Adjusted) Level: -20 -20 -20 - 5 (Short) 0 (Optimum) + 5 (Over) 8G6.2.4. Multiple Absorption Requests and the Asset Position is OVER 8G6.2.4.1. If the asset position is OVER and there are absorption requests for multiple FMS countries for the same NSN, the OVER, OWRM, and NON-PROGRAMMED BACKORDER amounts must be allocated among all the absorption requests. Here's how: 8G6.2.4.1.1. Step 1: Compute the relative percentage for each country:

RELATIVE PERCENTAGE EXAMPLE COUNTRY REQUEST QUANTITY PERCENT BA 2 2/12=.17 GR 4 4/12=.33 AT 6 6/12=.50 TOTAL 12 1.00 8G6.2.4.1.2. Step 2: Apply the percent to the OVER, OWRM, and NON-PROGRAMMED BACKORDER (NONP) QTY and enter the rounded (.5 up) result in the appropriate place on the absorption form. See the following tables for examples: PERCENTAGE EXAMPLE 1 CTY OVER TIMES EQUALS ROUNDED BA 10 .17 1.7 2 GR 10 .33 3.3 3 AT 10 .50 5 5 PERCENTAGE EXAMPLE 2 OWRM TIMES EQUALS 8 .17 1.4 8 .33 2.6 8 .50 4 PERCENTAGE EXAMPLE 3 NONP TIMES EQUALS 15 .17 2.5 15 .33 5.0 15 .50 7.5

CTY BA GR AT

ROUNDED 1 3 4

CTY BA GR AT

ROUNDED 3 5 8

8G6.2.4.2. The Absorption sheets would show the following information: ABSORPTION SHEET EXAMPLE OWRM QTY: 1, NONPROG BACKORDERS: 3 OWRM QTY: 3, NONPROG BACKORDERS: 5 OWRM QTY: 4, NONPROG BACKORDERS: 8

COUNTRY: BA COUNTRY: GR COUNTRY: AT

OVER: 2, OVER: 3, OVER: 5,

8G6.2.4.2.1. (NOTE 1: If there are multiple absorption requests and the asset position is SHORT or OPTIMUM, it is not necessary to compute percentages and allocate the various amounts.) 8G6.2.4.2.2. (NOTE 2: If there are multiple absorption requests and the total of the OVER quantity minus the OWRM minus the NON-PROGRAMMED BACKORDER QTY is greater than the total requested absorption quantity, put the computed total on all the forms. Nothing can be absorbed.) 8G6.2.5. NSNs with No D200A Computation. When an NSN does not have a D200A Computation, the Consolidated Assets and Requirements (A-D200A-EJ1-F9-29E) should be used. The IM, in coordination with their immediate supervisor, should use their best judgment to evaluate existing stocks and future requirements. If existing stocks will be needed to meet future requirements, an optimum position should be indicated on the Absorption Request form. This will result in the item being removed from the Termination File and liability cleared.

AFMAN 23-110 DISCUSSION DOCUMENT, Vol. IX, Chapter 8 / 12 March 2001 / page 114

Attachment 8G7 SAMIS PROCESSING OF THE ABSORPTION REQUEST FORMS 8G7.1. If the asset position is OPTIMUM or SHORT, the REQUESTED QUANTITY will be absorbed. The item/quantity will be removed from the Termination File and the customer's liability will be cleared. 8G7.2. If the asset position is OVER, SAMIS will subtract the OWRM and the NON-PROGRAMMED FMS BOs from the OVER quantity to determine an Adjusted Over Quantity (AOQ). 8G7.2.1. If the AOQ is less than or equal to zero (in other words short or optimum) the REQUEST QUANTITY will be absorbed. The item/quantity will be removed from the Termination File and the customer's liability will be cleared. 8G7.2.2. If the AOQ is greater than zero and less than the REQUEST QUANTITY, the difference between the REQUEST QUANTITY and the AOQ will be absorbed. The absorbed quantity will be removed from the Termination File and the customer's liability will be cleared. 8G7.2.3. If the AOQ is greater than or equal to the REQUEST QUANTITY, no absorption is possible.

AFMAN 23-110 DISCUSSION DOCUMENT, Vol. IX, Chapter 8 / 12 March 2001 / page 115

Attachment 8G8 XD5-7, XD5-8 FORMAT 8G8.1. XD5-7 Format. 8G8.1.1. This transaction is used to decrease the quantity of an item in the Termination File. It results in a Drawdown Requisition. XD5-7 FORMAT Data Entry XD5 FNH 7 NSN UNIT OF ISSUE QUANTITY TO BE REMOVED (PREFIX WITH ZEROS) COUNTRY CODE FMSO I CASE DESIGNATOR JULIAN DATE OF PREPARATION DOCUMENT NUMBER (SEE NOTES 1 AND 2) SUPPLEMENTARY ADDRESS (FIRST THREE POSITIONS) DISPOSITION CODE SUBMITTER IDENTIFICATION (SEE NOTE 3) FMSO II LINE FMSO II CASE

Position 1-3 4-6 7 8-22 23-24 25-30 31-32 33-35 36-40 41-51 52-54 55 56-61 62-64 65-67

8G8.1.2. Notes: 8G8.1.2.1. Omit the service code and the country code from the document number. 8G8.1.2.2. Position 48 must be a V. 8G8.1.2.3. This field may have any alpha/numeric entry to identify the submitter. This field must have at least a one digit entry or the transaction will reject. 8G8.2. XD5-8 Format. 8G8.2.1. This transaction deletes an item from the Termination File, and results in a Drawdown Requisition. XD5-8 FORMAT Data Entry XD5 FNH 8 NSN BLANK BLANK COUNTRY CODE FMSO I CASE DESIGNATOR JULIAN DATE OF PREPARATION DOCUMENT NUMBER (SEE NOTES 1 AND 2) SUPPLEMENTARY ADDRESS (FIRST THREE POSITIONS) DISPOSITION CODE SUBMITTER IDENTIFICATION (SEE NOTE 3) FMSO II LINE FMSO II CASE

Position 13 46 7 8 22 23 24 25 30 31 32 33 35 36 40 41 51 52 54 55 56 61 62 64 65 67

Air Force Manual 23-110, Vol. IX / page 116

8G8.2.2. Notes. 8G8.2.2.1. Omit the service code and the country code from the document number. 8G8.2.2.2. Position 48 must be a V. 8G8.2.2.3. This field may have any alpha/numeric entry to identify the submitter. This field must have at least a one digit entry or the transaction will reject.

Air Force Manual 23-110, Vol. IX / page 117

Attachment 8G9 ELIGIBLE AND INELIGIBLE FMSO II ITEMS 8G9.1. Both FMSO I and non-FMSO I items may be requisitioned on the FMSO II case. The following items are ineligible for the FMSO I, but may be requisitioned on the FMSO II, as nonprogrammed requisitions: 8G9.1.1. US Army-, US Navy-, and GSA-managed items. 8G9.1.2. Nonstandard items. This includes AAC P items, NSNs with nonstandard MMCs, and nonstocklisted items with NC, ND and K numbers and part numbers. 8G9.1.3. Local purchase and local manufacture items. 8G9.1.4. Obsolete/Disposal coded items. 8G9.1.5. Items in FSC 4925. 8G9.1.6. Classified items. 8G9.1.7. Other than DLA managed AAC D, H, or Z items. 8G9.2. The following items cannot be requisitioned on FMSO II cases because they require special management and handling: 8G9.2.1. Equipment Items (ERRC S and U). 8G9.2.2. Munitions and munitions related items: 8G9.2.2.1. FSG 13 items. 8G9.2.2.2. FSG 11 items. 8G9.2.2.3. MMC AQ, JB, and MN items. 8G9.2.2.4. New and unused items (Advice Code 6P) 8G9.2.2.5. Single Vendor Integrity Items. 8G9.2.2.6. Communications Security (COMSEC) items FSC 5810 and 5811, and MMC CA, CI, CS.

Attachment 8G10 PROGRAMMED/NONPROGRAMMED CODES USED IN SAMIS PRODUCTS 8G10.1. The SAMIS products use the following codes to indicate the programmed or nonprogrammed status of the requisition. 8G10.1.1. For requisitions received by SAMIS after 1 Oct 94, the following codes are used: POST-1-OCT-1994 PROGRAMMED/NONPROGRAMMED CODES Programmed. External Code. The requisition is eligible for support from depot stocks. Nonprogrammed. External Code. The requisition is only eligible for support from excess assets or from new procurement and can be lead time away from being filled. Programmed Expense Item Requisition Programmed Repair and Replace Requisition Nonprogrammed Ineligible for CLSSA Programmed Non-Repair/Replace Investment Item Requisition Nonprogrammed Requisition was nonrecurring. Nonprogrammed No Worldwide FMSO I stock level. Nonprogrammed Requisition quantity exceeded Worldwide EPQ. (The codes 8 and 9 are now used for investment items only. From 1 Oct 94 through May 95 they were used for investment and expense item requisitions.)

1 2 3 4 5 6 7 8 9

8G10.1.2. For requisitions received by SAMIS before 1 October 94, the following codes were used: PRE 10-1-94 PROGRAMMED/NONPROGRAMMED CODES Programmed Expense Item Requisition Nonprogrammed Expense Item Requisition Nonprogrammed Ineligible FMSO I Item Requisition Programmed USAF Managed Investment Item Requisition Nonprogrammed Requisition was nonrecurring Nonprogrammed Item not on the countrys FMSO I Nonprogrammed Requisition quantity exceeded countrys EPQ. (The codes 7, 8, and 9 are used for investment item requisitions only.)

3 4 5 6 7 8 9

Air Force Manual 23-110, Vol. IX / page 119

Attachment 8G11 ASSET RELEASE PROCESS

ASSET RELEASE CRITERIA

PROGRAM ED M

NON-PROGRAM ED M ALLREQNS

CONTROLLEVEL

PRIORITY 9-15 PRIORITY 4- 8 PRIORITY 1- 3 AND NM S C

SUPPORT LEVEL CRITICAL SPTLVL ZERO ASSETS

Air Force Manual 23-110, Vol. IX / page 121

8G11.1. Programmed requisitions with priorities 9 15 are eligible to be filled from depot stock down to the support level. 8G11.2. Programmed requisitions with priorities 4 8 are eligible to be supported from depot stock down to the critical support level. 8G11.3. Programmed requisitions with priorities 1 3, and Not Mission Capable Supply (NMCS) requisitions are eligible to be supported from depot stock down to the zero asset level. 8G11.4. Nonprogrammed requisitions will be filled from depot stocks if assets are in long supply (above the control level). The IMs only obligation for a nonprogrammed requisition is to place it on contract lead time away.

Air Force Manual 23-110, Vol. IX / page 122

Attachment 8G12

Air Force Manual 23-110, Vol. IX / page 123

Air Force Manual 23-110, Vol. IX / page 124 HOW TO IDENTIFY AN FMS REQUISITION

Air Force Manual 23-110, Vol. IX / page 125

Attachment 8G13 TYPES OF FMS REQUISITION 8G13.1. Introduction: Throughout Section G, references are made to different types of FMS requisitions. To aid in understanding, the different types are explained here. 8G13.2. There are two types of FMS requisitions: 8G13.2.1. Repair and Replace (H-coded) requisitions. 8G13.2.1.1. These are commonly referred to as H-coded requisitions because they contain an H in the first position of the document serial number. For example: DUT0445365H001. 8G13.2.1.2. H-coded requisitions are created by SAMIS when the FMS customer returns an unserviceable carcass to the ALC depot under the Repair and Replace program. 8G13.2.2. Non-Repair-and-Replace (non-H-coded) requisitions. 8G13.2.2.1. These are normal requisitions for serviceable items. These requisitions are submitted to establish initial operating stocks, and to replace operating stocks that are condemned when no longer serviceable or reparable. 8G13.2.2.2. These requisitions are called non-H-coded requisitions to distinguish them from H-coded requisitions. They have an all numeric document serial number. For example: DUT04453610002. 8G13.3. FMS requisitions can be programmed or nonprogrammed. 8G13.3.1. Requisitions for items/quantities that have been forecast on the CLSSA FMSO I case are programmed, that is, eligible for support from on-hand/on-order stocks based on the priority of the requisition. 8G13.3.2. Requisitions for items/quantities that have not been forecast on the CLSSA FMSO I case are nonprogrammed, that is, eligible for support lead-time away. 8G13.4. The following combinations are possible: 8G13.4.1. Programmed H-coded requisition 8G13.4.2. Nonprogrammed H-coded requisition 8G13.4.3. Programmed non-H-coded requisition 8G13.4.4. Nonprogrammed non-H-coded requisition

Air Force Manual 23-110, Vol. IX / page 126

Attachment 8G14 FMS REQUISITION FUND CODES DESCRIPTION 8G14.1. SAMIS assigns a fund code to all FMS requisitions to indicate the type of funds that are to be used. 8G14.1.1. An NU fund code indicates that AFMC funds are to be used in support of the requisition with later reimbursement from country funds. NU indicates reimbursable funding. 8G14.1.2. A 4F fund code indicates that country funds are to be directly cited in support of the requirement. AFMC funds are not used. 4F indicates direct cite funding. 8G14.2. SAMIS assigns the fund code to requisitions using the following logic: 8G14.2.1. Requisitions that meet the CLSSA Foreign Military Sales Order (FMSO) I criteria are coded programmed, and an NU fund code is assigned. 8G14.2.2. All repair and replace, H-coded requisitions, whether programmed or nonprogrammed, are assigned an NU fund code. 8G14.2.3. Nonprogrammed requisitions (other than H-coded) may be assigned either an NU or 4F fund code. 8G14.2.3.1. An NU fund code will be assigned if the NSN/quantity was used to clear CLSSA FMSO I liability. 8G14.2.3.2. A 4F fund code will be assigned if the NSN/quantity was not used to clear CLSSA FMSO I liability. 8G14.3. As a rule, once assigned, requisition fund codes should not be changed. However, there are times when it is prudent to change the fund code to improve the quality of support. 8G14.3.1. Nonprogrammed Non-H-coded Requisitions with NU Fund Code: Blanket authority is given to the IM to change the fund code for nonprogrammed non-H-coded requisitions from NU to 4F. The purpose of coding nonprogrammed non-H-coded requisitions with an NU fund code is to advise the IM to consider using available stocks or repair when filling the requisition. This is done because the NSN/quantity was once a CLSSA stock level, and stocks may have been procured by the IM to support it. This gives the IM the opportunity to use on-hand/on-order stocks or repair action to clear out these assets. If stocks arent available, the IM is authorized to change the fund code to 4F and procure the items or to route the requisition to PROS. 8G14.3.2. Programmed (Non-H-coded) Requisitions: For programmed (non-H-coded) requisitions with an NU fund code, the AFSAC managers and the ALC focal points may authorize a fund code change if it will improve support. Each situation will have to be evaluated on its own merits. A fund code change should be considered an action of last resort. The fund code on an H-coded requisition may never be changed. 8G14.4. Programmed support is a special commitment by AFMC to support that requirement. To change a programmed non-H-Coded requisition from NU to 4F in effect relieves AFMC of that commitment. 4F implies procurement action. Unlimited changes to 4F: 8G14.4.1. Could give the impression that we are not serious about expecting support for programmed FMS requisitions from AFMC on-hand/on-order stocks. 8G14.4.2. Could give the IM the impression that they don't have to support programmed requisitions, and all they have to do is get a fund code change and put the requirement on contract. 8G14.5. When evaluating a request for a fund code change to a programmed requisition, keep the following in mind: 8G14.5.1. Requests for a fund code change generally come from an IM. The AFSAC manager/ALC focal point needs to verify with the IM that reimbursable funds are absolutely not available, and confirm that support will be improved by using direct cite funds. 8G14.5.2. Use of direct cite funds will most often result in a separate FMS procurement. For expense items especially, the AFSAC manager/ALC FMS focal point must ensure that a separate procurement action is cost effective. The advantage of improved fill time could be offset by a higher cost due to a low quantity buy. 8G14.6. Remember that authorizing a programmed non-H-Coded requisition fund code change is an action of last resort, and that the fund code on H-coded requisitions may never be changed. 8G14.7. When evaluating a request from an IM for a programmed non-H-Coded requisition fund code change to 4F, ask the following questions: 8G14.7.1. Are there stocks on-hand? If yes, the programmed requisition is entitled to support using these stocks based on the priority of the requisition. 8G14.7.2. Are there stocks on-order/due in? If yes, the programmed requisition is entitled to support using these stocks based on the priority of the requisition.

Air Force Manual 23-110, Vol. IX / page 127

8G14.7.3. Are USAF reimbursable funds, Budget Program (BP) 15 or Materiel Support Division (MSD), available to support the requisition? If yes, they should be used and no fund code change is necessary. 8G14.7.4. If the answer to all three questions is no, a fund code change may be considered.

Air Force Manual 23-110, Vol. IX / page 128

Attachment 8H1 PUBLICATIONS FOR SECURITY ASSISTANCE CUSTOMERS Description Category A a. AFMAN 23-110 Submit Rqmt to (Control Acty) *AFSAC Focal Point & Supply Source Paragraph

b. Standard publications (Manuals, *AFSAC regulations and pamphlets) listed in AFIND Indexes (except AFMAN 23-110) c. Forms required for use, by prescribing *AFSAC directives. d. US Air Force S2A-1 (Index of US Air *AFSAC Force and DoD Federal Supply Catalogs), related cataloging publications e. Decals. *AFSAC f. Table of Allowance (TA) AFR 0-10 *AFSAC (Management Control Authorization Program of Allowance Source Codes for USAF Activities) Category B a. Automated Data Products AFSAC Category C a. Air Force Technical Orders TO 00-5-19 OC-ALC/TILU Security Assistance Technical Order Program (SATOP) b. Interim Technical Orders (ITO) IMS/SPD ALC Category D a. Engineering Drawings, and Related *AFSAC Documents (Engineering Data Distribution and Control) b. Technical Documents. *AFSAC Category E a. Training materiel (study and orientation AETC/LGTI literature, plans of instruction, syllabi, course standards, film, slides, recordings, tapes and other related training literature and classroom items) b. Professional Military Education (PME) AFSAC Correspondence Courses c. Defense Language Institute (DLI) *AFSAC Materiel Category F Joint Technical Coordinating Group for (approved) Munitions Effectiveness USAMSAA/AMXSY-J (JTCG/ME) (unapproved) DIA

AFPDC Baltimore 8.108.1 MD AFPDC Baltimore 8.108.2 MD AFPDC Baltimore 8.108.2 MD HQ AFMC/LGISA 8.108.1.3 Battle Creek, MI MGT ALC 8.108.1.4 AFPDC Baltimore 8.108.1.5 MD

AFSAC ALCs/TILU

8.108.2.1 8.108.3.1

IMS/SPD ALC ALC/TILU

8.108.3.1 8.108.4.1

ALC-FDO to IMS/SPD AETC/LGTI

8.108.4.2

8.108.5.1

Air University

8.108.5.2

DLIELC/LERW 8.108.5.3 Lackland AFB TX USAMSAA/AMX 8.108.6 SY-J, 392 Hopkins Road, Aberdeen Proving Ground MD 21005-5071

Air Force Manual 23-110, Vol. IX / page 129

Category G Classified publications when releasable By category under AFI 16-201 (Disclosure of Classifieddefined above Military Information to Foreign Governments and International Organizations), and in accordance with the Procedures for Publications P Cases in AFMAN 16-101 (FMS) and paragraph 4b

By category defined above

8.108.7

Air Force Manual 23-110, Vol. IX / page 130

Attachment 8H2 CUSTOMER INFORMATION MATRIX

Air Force Manual 23-110, Vol. IX / page 131

Attachment 8H3 GUIDE FOR PUBLICATIONS PRICING (PER COPY) (OTHER THAN TECHNICAL ORDERS)
______________________________________________________________________________________________ ________ PRICE PER COPY (See Note 2) ______________________________________________________________________________________________ ________ Number of Units (note 1) CATEGORIES OF PUBLICATION ______________________________________________________________________________________________ ________ TECH TRNG ADMIN SUPPLY OTHER (note 3) 1-100 $16.00 $10.00 $ 5.00 $ 5.00 101-200 $38.00 $22.00 $11.00 $11.00 201-300 $66.00 $38.00 $19.00 $19.00 301-400 $91.00 $54.00 $27.00 $27.00 401-500 $117.00 $67.00 $34.00 $34.00 ______________________________________________________________________________________________ ________ Engineering Drawings All Categories: Aperture or copy cards @ .88 per copy Hard copy $3.20 per copy ______________________________________________________________________________________________ ________ Letter Type Bulletins All Categories: and Directives $3.20 per copy ______________________________________________________________________________________________ _______ Forms All Categories: $.08 per copy with a minimum charge of $3.20. If standard inventory price available, use standard price. ______________________________________________________________________________________________ ________ Decals Actual cost or $.54 each (average cost), plus a processing charge of $3.20 per line item request. ______________________________________________________________________________________________ ________ NOTES: 1. Unit: A page, a role of microfilm, a microfiche frame, or a running foot of tape or motion picture film. 2. An additional charge of 20% is added for classified items. 3. Other Selected categories of publications, such as audiovisual products, decals, etc.

Air Force Manual 23-110, Vol. IX / page 132

Attachment 8K1 STANDARD FORM 364, REPORT OF DISCREPANCY (ROD)

Air Force Manual 23-110, Vol. IX / page 133

Attachment 8K1 (Continued) STANDARD FORM 364, REPORT OF DISCREPANCY (Back)

Air Force Manual 23-110, Vol. IX / page 134

Attachment 8K2 DD FORM 1348-1A, ISSUE RELEASE/RECEIPT DOCUMENT

Air Force Manual 23-110, Vol. IX / page 135

Attachment 8K3 DD FORM 250, MATERIAL INSPECTION AND RECEIVING REPORT

Air Force Manual 23-110, Vol. IX / page 136

Attachment 8K4 DD FORM 1149, REQUISITION AND INVOICE/SHIPPING DOCUMENT

Air Force Manual 23-110, Vol. IX / page 137

DD FORM 1149C, REQUISITION AND INVOICE/SHIPPING DOCUMENT (CONTINUATION SHEET)

Air Force Manual 23-110, Vol. IX / page 138

Attachment 8K5 REPLY CODES TO CUSTOMER REQUESTS FOR ADJUSTMENTS OR BILLINGS 8K5.1. Request denied. Code Explanation AA Duplicate billing and/or shipment resulted from receipt of duplicate requisition and duplicate supply action. AB Bill reflected correct unit or extended price of materiel shipped. AE Supplier adjusted to unit pack since requisition did not prohibit this action; or, shipment made in accordance with instructions in requisitions. AF Authorized substitute in latest supply manual. Requisition did not prohibit substitutions. AG Claim less than $100.00. Loss or gain to be absorbed by customer. AI Records indicate prior reversal of duplicate credit. AJ Credit was granted as result of prior request. AK Shipment made by commercial bill of lading: US Government not responsible for damaged shipments. AL Copies of shipping document evidencing proof of shipment/acceptance are attached. AN Claim less than $100.00 loss or gain to be absorbed by FMS customer. AO Request cannot be granted since discrepancy report was not received within allowable time frame. AP Request cannot be granted because item was procured specifically for FMS customer. General condition A2, as set forth in Annex A of the LOA, applies. 8K5.2. Request granted and advice on materiel disposition. Code Explanation BA Retain or dispose of materiel locally. BB Materiel to be returned to activity. BC Hold unacceptable shipment quantity pending disposition instructions by separate communication. CA Requested debit adjustment will be made and bill issued. No supply action required. CB Requested credit adjustment will be made and amended bill issued. No supply action required. CF Request granted for financial adjustment not directly related to materiel shipments, i.e., repair costs. CW Credit adjustment granted on accessorial charges - FHF cards only. CX Credit adjustment granted on administrative charges - FKD cards only. CY Debit adjustment granted administrative charges - FKC cards only. CZ Debit adjustment granted on accessorial charges - FKE cards only. 8K5.3. Advisory replies not requiring billing or supply action. Code Explanation DA Request previously processed and credit granted. DB Request previously processed and credit not granted. DD Billing previously rendered. DG Duplicate billing will be furnished. DI Letter or explanation follows. DJ No record of previous request. Resubmit. DK Copies of shipping documents evidencing proof of shipment and acceptance are attached.

Air Force Manual 23-110, Vol. IX / page 139

DM DX

Reply delayed 30 days. Matter being investigated. Request for SDR cancellation approved.

8K5.4. Codes for requesting additional data from country. Code Explanation EB Document number incomplete; resubmit. EC Bill number incomplete; resubmit (note) EF Records do not indicate duplicate shipment and/or billing on bill number cited. If duplication occurred on another bill, resubmit citing both bill numbers (note). EI Claim should be supported by appropriate documentation; please submit. EJ Claim should be supported by confirmation of cancellation; please submit. NOTE: Adjustment codes are not restricted to AFAFC use.

Air Force Manual 23-110, Vol. IX / page 140

Attachment 8L1 FAD/UND/PRIORITY MATRIX URGENCY OF NEED DESIGNATOR A B C FORCE/ACTIVITY DESIGNATOR REQUISITION PRIORITY DESIGNATOR I 01 04 11 II 02 05 12 III 03 06 13 IV 07 09 14 V 08 10 15 NOTE: Under this criteria, not more than three requisition priority designators are available to any one activity. Depending on FAD assigned, FMS NMCS requisitions must always be priority 03, 07, or 08. Priority designators are in RP 60-61 and must be numeric. If left blank, SAMIS will force a priority 15.

Air Force Manual 23-110, Vol. IX / page 141

Attachment 8L2 URGENCY JUSTIFICATION CODES (UJC)

Air Force Manual 23-110, Vol. IX / page 142

Attachment 8L3 URGENCY OF NEED DESIGNATOR (UND) DEFINED 8L3.1. The UND is used for different degrees of urgency when operational mission capability is affected because of materiel nonavailability. DESIGNATOR A B

Justified only when materiel shortages needed for immediate end use prevent an activity from performing assigned operational missions (NMCS). Justified only when materiel shortages needed for immediate end use and without which the capability of the activity to perform assigned missions is impaired. Required for on-schedule repair/maintenance/manufacture of all equipment for long range projects/programs, or for routine stock replenishment and other routine shortages which do not meet the criteria for use of UND A or B.

Air Force Manual 23-110, Vol. IX / page 143