by order of the commander air force materiel …

BY ORDER OF THE COMMANDER

AIR FORCE MATERIEL COMMAND

AIR FORCE MATERIEL COMMAND

MANUAL 23-101 VOLUME 1

17 NOVEMBER 2016

Certified Current 12 January 2017Materiel Management

GENERAL D200A/N INFORMATION

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications and forms are available for downloading or ordering on the e-

publishing website at www.e-Publishing.af.mil

RELEASABILITY: There are no releasability restrictions on this publication

OPR: AFMC/A4RM

Supersedes: AFMCMAN 23-1,

12 June 2008

Certified by: AFMC/A4R

(Col Deirdre A. Mahon)

Pages: 146

This publication implements Air Force Instruction (AFI) 23-101, Air Force Materiel

Management. It prescribes guidance and procedural instructions for computing XD2, XB3, and

XF3 secondary item requirements. It applies to Secondary Item Requirements System

(SIRS)(D200A) and Central Secondary Item Stratification (CSIS)(D200N) users. This

publication does not apply to Air Force Reserve units and the Air National Guard (ANG). Refer

recommended changes and questions about this publication to the Office of Primary

Responsibility (OPR) using an AF Form 847, Recommendation for Change of Publication; route

AF Forms 847 from the field through the appropriate functional’s chain of command. This

publication may be supplemented at any level, but must be routed to the OPR for coordination

prior to certification and approval. The authorities to waive wing/unit level requirements in this

publication are identified with a Tier (“T-0, T-1, T-2, T-3”) number following the compliance

statement. Submit requests for waivers using AF Form 679, Air Force Publication Compliance

Item Waiver Request/Approval, through the chain of command to the appropriate Tier waiver

approval authority, or alternately, to the Publication OPR for non-tiered compliance items.

Request for waivers must be approved by the publication OPR prior to implementation. Ensure

that all records created as a result of processes prescribed in this publication are maintained In

Accordance With (IAW) Air Force Manual (AFMAN) 33-363, Management of Records, and

disposed of IAW Air Force Records Information Management System (AFRIMS) Records

Disposition Schedule (RDS). The use of the name or mark of any specific manufacturer,

commercial product, commodity, or service in this publication does not imply endorsement by

the Air Force

http://www.e-publishing.af.mil/

2 AFMCMAN23-101V1 17 NOVEMBER 2016

SUMMARY OF CHANGES

This publication has been substantially revised and must be completely reviewed. The previous

manual has been restructured into six separate volumes. Volume 1 incorporates previous

Chapter 1, 2, 7, and 33 respectively. Some of the more significant changes include: exclusion

requests for no compute coded items, Inventory Management Specialist/Materiel Manager roles

and responsibilities, electronic AFMC Form 318, termination reviews, signature requirements,

and the addition of system roles and responsibilities and access requirements.

Chapter 1— GENERAL 5

1.1. Applicability. .......................................................................................................... 5

1.2. Purpose.................................................................................................................... 5

1.3. Types of Items. ....................................................................................................... 7

1.4. Roles and Responsibilities. ..................................................................................... 10

1.5. Requirements Segments. ......................................................................................... 15

1.6. Categories of Requirements. ................................................................................... 15

1.7. Schedule. ................................................................................................................. 16

1.8. Computation Time Span. ........................................................................................ 16

1.9. Initial and Follow-On Spares. ................................................................................. 17

1.10. Stock Number Establishment. ................................................................................. 18

1.11. Review and Adjustment Actions. ........................................................................... 19

1.12. Life-of-Type (LOT) Buys. ...................................................................................... 23

1.13. Identifying Candidates and Requirements for Multiple Year Contracting. ............ 25

1.14. Item Contracting History Record. ........................................................................... 26

1.15. Documentation Requirements. ................................................................................ 26

Table 1.1. Item Purchases Were Initiated Destroy Documents and Products 2 Years After

Contract Closure IAW Paragraph 1 15 2. ................................................................ 27

Table 1.2. Destroy After 2 Years. ............................................................................................ 28

Table 1.3. Pushed Products Destroyed After 2 Years Unless Needed to Support Buy or

Terminations. ........................................................................................................... 28

Table 1.4. Destroy Initial D200A Product After Receipt of Final D200A Product Unless

Pen and Ink Documentation Required to Support Actions Taken. .......................... 29

AFMCMAN23-101V1 17 NOVEMBER 2016 3

Table 1.5. Destroy Final D200A Products After Receipt of Summary D200A Product

Unless Signature Document. .................................................................................... 30

Table 1.6. Destroy on Receipt of Next Cycle’s Products. ....................................................... 30

1.16. Performance-Based Logistics (PBL) Contracts. ..................................................... 31

1.17. “Dead Items” in D200A. ......................................................................................... 32

Chapter 2— USING RMS 33

2.1. Introduction. ............................................................................................................ 33

2.2. Roles and Responsibilities. ..................................................................................... 33

2.3. System Access. ....................................................................................................... 33

Table 2.1. Requestor Types Authorizations, and Approving Authorities. ............................... 34

Table 2.2. D200A N Unique SAAR Instructions. .................................................................... 35

2.4. RMS Applications Access. ..................................................................................... 36

2.5. SIRS GUI Navigation. ............................................................................................ 37

2.6. Organization of the SIRS Online Screens. .............................................................. 37

2.7. Display Screens. ...................................................................................................... 38

2.8. File Maintenance Screens. ...................................................................................... 45

2.9. Output Products Screens. ........................................................................................ 46

2.10. Source Reference Codes. ........................................................................................ 47

Chapter 3— QUALITY REVIEWS 48

3.1. General. ................................................................................................................... 48

Table 3.1. IMS MM PMS Quality Review Checklist For Items with ERRC Code “T”. ......... 50

Table 3.2. IMS MM Quality Review Checklist For Items with ERRC “N” or “P”. ................ 59

Table 3.3. AF Secondary Inventory Control Activity SICA) Nonconsumable Item Materiel

Support Code (NIMSC) 5 Checklist. ....................................................................... 66

Table 3.4. Factors and Usage Quality Review Checklist For Items with ERRC “T”. ............. 70

Table 3.5. Factors and Usage Quality Review Checklist For Items with ERRC “N” or “P”. . 77

Table 3.6. Repair Quality Checklist. ........................................................................................ 84

Table 3.7. Termination Review Checklist. .............................................................................. 89

Table 3.8. MISTR Repair and Repair Data Checklist Note Does not apply to AF SICA

NIMSC 5 items. ....................................................................................................... 91


Table 3.9. AFMC Review Summary. ...................................................................................... 94

Table 3.10. Depot Review Team Summary. .............................................................................. 95

Table 3.11. Review Package. ..................................................................................................... 96

Chapter 4— TERMINATION ACTIONS 98

4.1. Introduction. ............................................................................................................ 98

4.2. Overview. ................................................................................................................ 98

4.3. Procedures. .............................................................................................................. 100

4.4. Reporting and Analysis. .......................................................................................... 104

Table 4.1. Termination Codes. ................................................................................................. 106

Table 4.2. Required Electronic Termination (RIR) Log Fields. .............................................. 110

4.5. The SIRS Termination Model. ................................................................................ 111

Table 4.3. Termination Model Results – Recommendations. .................................................. 117

Attachment 1— GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION 118

Attachment 2— SIGNATURE REQUIREMENTS 144


Chapter 1

GENERAL

1.1. Applicability. This manual applies to HQ AFMC, AFSC and AFLCMC personnel

responsible for the development, adjustment, computation, review, and approval of requirements

for recoverable and consumable secondary items and management actions that result from those

requirements. Procedures contained in this manual apply primarily to Materiel Managers (MM),

Inventory Management Specialists (IMS), Equipment Specialists (ES), Production Management

Specialists (PMS) and AFSC management. NOTE: An MM performs the functions of a PMS

and is included in the responsibilities/actions whenever PMS is referenced in this volume.

1.2. Purpose. This manual provides basic guidelines for computing replenishment requirements

for secondary items, both recoverable and consumable items, using the Secondary Item

Requirements System (SIRS)(D200A). Requirements computed with these procedures reflect

the average materiel support requirements for Air Force (AF) operations.

1.2.1. Items computed in SIRS/D200A use data that is current on the last calendar day of

each calendar quarter (qtr). The purpose of SIRS is to determine what management actions

will be taken immediately to support operations, and to provide a baseline for budget

submission and analysis. SIRS provides all the input data for the Central Secondary Item

Stratification (CSIS) system. The purpose of the CSIS is to display budget and repair deficits

for each requirements segment by Fiscal Year (FY). The CSIS provides data on asset

distribution against requirements and is used as a baseline for inventory analysis. This

system has been assigned Data System Designator (DSD) D200N and will be referred to as

CSIS throughout this manual. SIRS and CSIS are part of the Requirements Management

System (RMS).

1.2.2. Procedures, forms, computation worksheets, and supporting data developed in this

process make up the official record to substantiate the acquisition program, budget

projections, and other logistics actions.

1.2.3. This manual provides descriptions of the various automated methodologies associated

with the requirements process, as well as policies and procedures that apply to those

processes.

1.2.4. Items covered by this manual are those assigned Expendability, Recoverability,

Reparability Category (ERRC) codes XD2 or “T,” XB3 or “N,” and XF3 or “P.” These are

usually secondary items installed in a higher assembly such as an aircraft, vehicle, piece of

equipment, or another recoverable secondary item. Upon failure, these items are removed

and replaced with serviceable assets. The unserviceable assets for recoverable items are

turned into a maintenance facility for repair and eventually reissued or condemned. Under

normal circumstances, any unserviceable assets for a consumable item are disposed.

1.2.5. Weighted Unit Repair Cost (URC) exceeding 75% of the replacement price - Forecast

Unit Price (FUP) for a reparable item (ERRC “T”).

1.2.5.1. When an item’s weighted repair cost exceeds 75% of the FUP, there are no

contracts for the item within the last 5 years, and the annual repair requirement for the

item is $1 million or more and the item can still be procured; the IMS/MM will request


Contracting obtain a unit price quote from the contractor. If the procuring activity

communicates a quote cannot be obtained due to the item being competitive or the

contractor will not provide without cost, then the IMS/MM is to document the AF Form

318 and follow directions in para 1.2.5.2 If the item is expected to have future

procurement, the IMS/MM will file maintain the unit price quoted as the actual unit price

and date of the quote as the Date of Last Procurement (DOLP) into SIRS. When the

IMS/MM does not expect to procure the item in the future, the information on new

procurement pricing is to be used in the Notepad to justify retaining the item as

recoverable while the price in D200A remains the last actual procurement cost/DOLP. If

after the receipt of the quote, the weighted repair cost still exceeds 75% of the quoted unit

price or the item was bought within the last 5 years and the weighted repair cost exceeds

75% of the FUP, the item management team will conduct an evaluation of procurement

and repair history to determine if the item will be retained as a recoverable item (ERRC

“T”) or be converted to a consumable item (ERRC “N” or “P”), and document their

rationale and how they arrived at their decision. The IMS/MM will document the

rationale in the D200A Notepad and maintain the documentation until 2 years after the

price has been superseded. If the analysis supports conversion to a consumable item, the

ES will initiate the cataloging action and follow guidance for factors forecasting for

ERRC change items. If unexpected circumstances later require procurement on an item

previously not expected to be procured, the IMS/MM will revert to the methods described

above (for items with expected future procurement) to arrive at a representative price and

DOLP.

1.2.5.2. If a quote cannot be obtained from a contractor as outlined in the preceding

paragraph or the annual repair requirement for the item is less than $1 million and a like

item has a unit price from a more recent purchase, use the FUP (unit price and DOLP)

from a like item to perform the comparison. If the weighted repair cost of the like item

also exceeds 75% of the FUP, the item management team will conduct an evaluation of

procurement and repair history to determine if the item must be retained as a recoverable

item (ERRC “T”) or be converted to a consumable item (ERRC “N” or “P”), document

their rationale and how they arrived at their decision. The IMS/MM will document the

rationale in the D200A Notepad and maintain the documentation until 2 years after the

price has been superseded. If the analysis supports conversion to a consumable item, the

ES will initiate the cataloging action and follow guidance for factors forecasting for

ERRC code change items.

1.2.5.3. Items still in use that are no longer procurable, but are reparable, will not be

converted from recoverable items to consumable items. If the weighted repair cost

exceeds 75% of the FUP for these items, the IMS/MM will document the fact that they

are no longer procurable in the D200A Notepad as rationale for keeping them as

recoverable items and retain the information as an audit trail.

1.2.5.4. For further information, see AFMAN 21-106, Joint Regulation Governing the

Use and Application of Uniform Source, Maintenance, and Recoverability Codes; AFH

23-123, Volume 1, Materiel Management Reference Information, and Volume 2, Part

Two, Integrated Logistics System-Supply (ILS-S), Standard Base Supply System

Operations; AFMCMAN 23-3, Cataloging and Standardization; AFMCI 23-112,

Management of Items Subject To Repair (MISTR); Technical Order (T.O.) 00-20-3,


Maintenance Processing of Reparable Property and The Repair Cycle Asset Control

System; and T.O. 00-25-195-WA-1, AF Technical Order System Source, Maintenance,

and Recoverability Coding of Air Force Weapons, Systems, and Equipments.

1.3. Types of Items. Time-phased computations are done for all Subgroup Master (SGM) stock

numbers that have been recorded in SIRS; Exceptions: obsolete items, Insurance (INS) items,

Numeric Stockage Objective (NSO) items, no compute coded items, and special items listed in

paragraph 1.3.6. SIRS produces the INS/NSO Item Status Listing for items coded INS or NSO.

See AFMCMAN 23-101, Volume 3, Computational Results (D200A, D200N), Chapter 5. A

CSIS is available in D200N for every item. Requirement computation worksheets are produced

for Acquisition Advice Code (AAC) “V” items (use until exhausted), and buy computations

could be generated which must be scrubbed.

1.3.1. Obsolete items (SGM and interchangeable). All reported assets are identified in

management reports and output to other systems as excess quantities available for disposal.

When the SGM stock number is coded obsolete, all stock numbers interchangeable with this

SGM stock number are considered obsolete and their assets are processed as excess. All

obsolete on-order assets are termination candidates.

1.3.2. Contingency items. These items do not have an application to a current system or

Next Higher Assembly (NHA), which is in use or planned to be in use. However, a decision

has been made to retain the items for military contingency plans that have not been finalized.

These items are identified by an “M” in the deferred disposal field on the front page of the

computation. See AFMCMAN 23-101, Volume 4, IMS/PMS/MM Data and Reports

(D200A, D200N), paragraph 1.3.1.8.5.4. Contingency items are computed by comparing

total assets to the deferred disposal level. If assets on hand exceed that level, the quantity

which exceeds the level is identified as excess, plus all on-order assets are candidates for

termination. If assets on hand are less than the level, the level is reduced to equal the assets,

since SIRS is programmed to ensure that no buy quantities are developed for contingency

items. If assets on hand are less than the level, but there are also on-order assets available,

the on-order quantity required to fill the level deficit is retained, and the balance of the on-

order assets are identified for termination. A zero level indicates that all assets, on hand and

on order, equal the requirement. Repair of contingency-coded assets is not authorized.

1.3.3. INS items. These items have been identified through cataloging as not subject to

normal failures, but are retained in SIRS to support losses which may occur as a result of

accidents or acts of nature. (See AFMCMAN 23-101, Volume 3, Chapter 5)

1.3.4. NSO items. These items are expected to fail as a result of normal use or operations;

however, such failures are expected to be low or sporadic. This NSO code is reviewed at

least annually to determine if the code must be deleted or retained. When usage increases

and the code is removed, the item becomes a normal active demand-based item and is

computed normally. (See AFMCMAN 23-101, Volume 3, Chapter 5)

1.3.5. No compute coded items. No compute items have missing key data or are obsolete.

When the item is assigned a compute code “B,” “N,” “P,” or “X,” or an active item is

assigned a compute code of “R,” SIRS will not compute requirements. The item’s assets are

used in preparing management reports. (See AFMCMAN 23-101, Volume 4, paragraph

1.14.3.)


1.3.6. Items Excluded From SIRS. The Requirements Item Identification Data (RIID)

system (D200E) assigns a value to the System Compute Code (SCC) for the National Stock

Number (NSN) that determines which other segments of D200 get sent information on that

NSN. A D200E SCC of “A” designates that SIRS will get data for that NSN. The current

exclusions from transmission in the RIID snapshot to D200A can be viewed on the SCCA

SYS COMP CD “A” EXCLUSIONS screen in RIID. The exclusions are based on Materiel

Management Aggregation Code (MMAC), Source Of Supply (SOS), cataloging Budget Code

(BC), program select code or AAC. National Item Identification Numbers (NIIN) beginning

with ND or K and NSNs assigned BC K are excluded. Exclusions cannot be input based on

an entire NSN or NIIN. Requests for exclusion will be sent to HQ AFMC/A4 for approval

prior to implementation. The justification for exclusion will include the rationale for the

exclusion and how requirements, budgeting, the CSIS, and the Supply System Inventory

Report (SSIR) will be accomplished when the items are excluded.

1.3.7. Quick Engine Change (QEC) Kits. A QEC kit is a group of stock listed Consolidated

Sustainment Activity Group-Supply (CSAG-S) and General Support Division (GSD)

accessory items required to attach an engine to an aircraft. Some QEC kits are assigned

NSNs rather than kit numbers. The QEC kit is stock fund exempt and must have a Budget

Program (BP) code of “1E” if it is in SIRS (see AFMCMAN 23-101, Volume 4).

Requirements for QEC kits are not computed in SIRS and the IMS/MM must delete all

reported assets and any offsetting requirements. It is the stock listed components of the QEC

kits on which requirements are based.

1.3.7.1. One QEC kit is authorized for each spare engine. The kits as a whole are

normally procured during the acquisition of the engines, not as follow-on spares. Once

the Initial complement of QEC kits are acquired, the only spares procurement required is

for the component parts.

1.3.7.2. While installed on the engine or aircraft, the kit loses its identity as an NSN.

Under the normal three-level maintenance concept, when the engine is prepared for

shipment to Engine Overhaul (EOH) repair, the QEC kit is removed and reported at the

base. QEC NSNs only appear in the reported asset data when separated from the engine.

The kits stay at the owning activity until the engine is returned and the kit is reinstalled.

Since the QEC is comprised of stock listed components which can be removed and

replaced at field level, they are virtually 100% base repaired. There is no programmed

depot repair for QEC kits.

1.3.7.3. Under a remove and replace concept of engine repair (Jet Engine Intermediate

Maintenance (JEIM) “A” and “I” jobs), the QECs are returned with the engine to the

depot. The depot job routes the QEC, never condemning a whole kit, resulting in no

demands on depot supply for the QEC NSN.

1.3.7.4. CSAG-S component items of the QEC kits. Because QEC kits come in attached

to engines under the remove and repair concept, demands on supply may occur (also

called depot reparable generations [Dep Rep Gen]) for CSAG-S recoverable component

items. In addition to appropriate Organizational and Intermediate Maintenance (OIM)

and Programmed Depot Maintenance (PDM) program(s), the appropriate applications

must be added to the item application record in the Applications, Programs, Indentures

(API) system (D200F) to cover any changes in the repair concept.


1.3.7.5. QECs may be shipped to the IMS/MM as extras when an engine is destroyed or

disposed. These kits are most often always in reparable condition, as the number of

component parts present or missing and their serviceability is unknown. The cost to

restore a reparable kit containing unserviceable and missing components with stock

funded serviceable assets would be prohibitive. Repair is rare and accomplished only on

AFMC Form 206, Temporary Work Request, funded with appropriate Program Office or

engine funds if a critical need is established by the Program Office or engine manager.

1.3.7.6. Serviceable kits at the depot usually only occur at the time of provisioning

awaiting shipment to the spare engine.

1.3.8. Afterburners are authorized for each spare engine and although base assets are

reported, the requirements are not computed in SIRS. The IMS/MM must delete all reported

assets and any offsetting requirements if the NSN for the afterburner appears in SIRS. It is

the stock listed components of the afterburners on which requirements are based.

1.3.9. An item with a shelf-life code will be bought on an Indefinite Delivery/Indefinite

Quantity (ID/IQ) contract unless contracting is unable to negotiate this type of contract with

the contractor. This will allow the IMS/MM to exercise options to put the parts on contract

as they are needed; reference AFMCI 20-102, Requirements Definition andictectPurchase

Instrument Development.

1.3.10. Calendar Time Change Items. AF bases send the IMS/MM the projection for

selected time change items on AFTO Form 223, Time Change Requirements Forecast

(reference T.O. 00-20-9-WA-1, Forecasting Replacement Requirements For Selected

Calendar And Hourly Time Change Items). The normal requirements are adequate in most

cases for peaking time change demands on the system. In other cases where peaks are offset

by levels, additive requirements are input to the requirements computation to compensate for

the deficiency. Intensified management must be applied to all time change items until either

random or predictable patterns can be established. Reviews must be made of these selected

items to make sure only valid additive requirements are input to adjust requirements

computations. For requirements to be computed automatically, the IMS/MM and ES prepare

the following data and input it to API and SIRS. A 5-digit Program Element Code (PEC)

will be assigned to each time change item. The IMS/MM or program monitor develops a

future program for each qtr. The time change removal dates from data submitted under T.O.

00-20-9-WA-1 must be obtained. Then the retention program is developed by multiplying

qtr 38 by 12. The new item code of “N” must be retained to prevent loss of estimated

demand rates in the item’s records. To retain this code, the application program begin date is

filed maintained to limit the past usage to less than 24 months. The application Program

Select Code (PSC) is 3000. The application Quantity Per Application (QPAPPL) is 1 and the

application percent is 100. Total OIM demand rate is 1.000. Base Not Reparable This

Station (NRTS) percent is 100, current and forecast. Base stock level days are zero. Depot

stock level days are zero. Depot Repair Cycle (DRC) reflects the time required to generate

economic repair lot quantities in addition to actual shop flow days. All other factors are

input as in normal processing of recoverable items. Additives are developed for Cartridge

Actuated Devices/Propellant Activated Devices (CAD/PAD) life support time change items.

Production quantities are qualified for delivery by expending a predetermined portion of each

lot. If this sample fails, the entire lot is rejected. Therefore, an additive requirement equal to


the greater of one lot size or 150 calendar days’ time change requirement is authorized. This

quantity is an additive requirement in the first qtr of the computation.

1.3.11. 100% Base Repair Recoverable Items. For recoverable ERRC code “T” items that

are always repaired at base level and never returned to the depot for repair, the IMS/MM

must file maintain any reported unserviceable assets to serviceable to prevent D200A from

erroneously projecting a depot level repair requirement. This includes reported unserviceable

base and unserviceable in-transit assets. This situation is unusual as most recoverable items

have depot level repair, but there are instances where the recoverable item is always

disassembled at base level and only the failed recoverable component(s) are returned to the

depot for repair. Prior to taking this action, the IMS/MM must verify with the ES that the

item is one that is always repaired at a base or Centralized Repair Facility (CRF) and never

returned to the depot for repair.

1.4. Roles and Responsibilities.

1.4.1. The Supply Requirements Branch (AFSC/LGPS) will:

1.4.1.1. Perform duties as the SIRS Functional OPR and Advocate.

1.4.1.2. Perform duties as the SIRS Termination OPR.

1.4.2. The IMS/MM will:

1.4.2.1. For the D200A products output to or pulled by them, review the data for

assigned items. Exception: The data the ES reviews and file maintains (see paragraph

1.4.3.1). This includes surveillance of data provided by interfacing systems, online file

maintenance, and review of SIRS output products. The IMS/MM will concentrate on

working the exceptions that have been generated for each item. When changing any data

element, the reason for the change will be documented using the D200A Notepad. (See

AFMCMAN 23-101, Volume 4 for details.)

1.4.2.2. Review/work asset reconciliation products output to them every qtr using the

Interactive Requirements Information Services (IRIS). The Item Review Listing (IRL)

pulls a personalized list of NSNs for review in order of importance.

1.4.2.3. Track the following throughout the qtr: condemnations, transfers to the Defense

Logistics Agency (DLA) Disposition Services, shipments to and receipts from

contractors, shipments from stock to Foreign Military Sales (FMS) customers and

shipments to non-reporting activities in order to facilitate the asset reconciliation process.

These actions can be tracked using: the Item Manager Wholesale Requisition Process

system (D035A)/Wholesale and Retail Receiving/Shipping system (D035K) transaction

registers, Distribution Standard System (DSS), Center of Parts Activity (COPA), and

TRACKER (D087T).

1.4.2.4. Review data elements with Source Reference Code (SRC) E on their products.

SRC "E" represents "Entered" and indicates that the data being shown have been received

through a file maintenance action. This review will ensure the file maintained data is still

current and valid.

1.4.2.5. Use the SGM Computation Worksheet Requirements as the signature, review,

and approval document for computing items. Note: The IMS/MM may use the

INS/NSO Item Status Listing as the signature, review, and approval document for


INS/NSO items. (Some organizations have developed a signature page that is attached

on top of the computation, recomputation or INS/NSO Item Status Listing. This product

may be used in lieu of the computation, recomputation or INS/NSO Item Status Listing

as long as the current date appearing on the D200A product appears on the signature

page.) A signature signifies that the IMS/MM has reviewed the information contained in

the SGM Computation Worksheet Requirements, recomputation or INS/NSO Item Status

Listing, that the IMS/MM worked the item (as needed) and that to the best of the

knowledge of the IMS/MM the information is correct. It also signifies that the indicated

management actions (with annotated adjustments, if required) are correct and will be

taken (see paragraph 1.4.2.9). If the signature cannot be easily read, the IMS/MM’s

printed name must be included on the documents. See paragraph 1.15 and

subparagraphs for documentation and product retention requirements.

1.4.2.6. Sign (literally or with signature stamp), date, and obtain required signatures per

Attachment 2 within 10 calendar days of print of the products anytime that the item

shows a termination.


Attachment 2 within 35 calendar days of print of the products anytime the item shows a

buy or repair requirement or the first time it computes excess or if the excess quantity is

greater than the previous cycle.


Attachment 2 within 60 calendar days of print of these documents if the computed

excess is equal to or less than the previous cycle’s excess or if the item is in an optimum

position, but requires review based on its Item Activity Code (IAC).

1.4.2.9. Initiates management actions indicated by SIRS outputs after coordinating with

the other members of the item management team and obtaining any other required

signatures specified in Attachment 2.

1.4.2.10. Initiates acquisitions in a timely manner to ensure that assets are available when

they are required. If any changes are made to the requirement in the computation, the

buy code must be annotated on the computation or INS/NSO Item Status Listing. The

buy code must be the same as the code used in the Automated Budget Compilation

System (ABCS) and a short explanation for the change must be made on the product as

well.

1.4.2.11. Annotate the dollar value of organic and contractor repair actions (Peacetime

Operating Stock (POS) + Readiness Spares Package (RSP)) for each year (Current Year

[CY], Apportionment Year [AY], Budget Year [BY] or Extended Year [EY]) on the

computation or INS/NSO Item Status Listing. If any changes are made to the repair

requirement in the computation, the repair code must be annotated on the computation,

recomputation or INS/NSO Item Status Listing. The repair code must be the same as the

code used on the Quarterly Projection Worksheet (ABCS B21 report) and in ABCS and a

short explanation of the change must be made on the product as well.

1.4.2.12. Review the SGM Computation Worksheet or the INS/NSO Item Status Listing

from the Final computation review to ensure that the data is correct. If the data is not

correct, the IMS/MM and ES will correct the erroneous data and request a For Real Item


Record (FRIR) recomputation. If the item is still in termination, the IMS/MM advises the

Contracting activity that an amendment may be forth coming to cancel or modify all

associated PR(s) or quantity(s), and contract award(s) should be delayed until after the

Summary SIRS computation or a What If Item Recomputation (WTIR) and term model

have been approved through the review process when a definite termination quantity will

be known.

1.4.2.13. The RCO will work and review all termination actions and decisions within 10

calendar days of the print date of the Summary products. The PR amendment or the

Termination Authority Template will be initiated within this 10-day working period when

the on-order quantities are no longer required for support and a decision is made to

reduce or terminate the quantity, and in order to recover funds. The appropriate

termination code (see Chapter 4) must be annotated on the computation/computation

signature coversheet, recomputation or INS/NSO Item Status Listing and must match the

code used in ABCS. A brief explanation or the reason for using the term code and any

actions taken must also be documented, and a notation of action made on the generic

Notepad for this item. Note: Termination codes and appropriate documentation are

required on all items that were in termination on the Summary computation even if a

recomputation or WTIR results in the item being removed from termination status

(Termination Quantity [Qty] = 0).

1.4.2.14. Document what they intend to do with the excess on the computation or

INS/NSO Item Status Listing.

1.4.2.15. File maintain the disposal or retention codes in the Reutilization and

Disposition System (RDS)(D035G) and ensure appropriate actions are taken for disposal

of assets excess to requirements.

1.4.3. The ES will:

1.4.3.1. For the D200A products output to or pulled by them, review each item’s usage,

factors, programs, application program designators/standard program designators,

application program begin dates, QPA, application percent, application Mission Item

Essentiality Codes (MIEC), application PSCs and Factor Indicator Codes (FIC) for

accuracy and completeness and must file maintain any needed corrections. This includes

surveillance of usage data and noting any trends, determination if historical data are

indicative of future activity, and computation of estimated factors. When changing any

data element, the reason for the change will be documented using the D200A Notepad.

See AFMCMAN 23-101, Volume 5, Equipment Specialist Data and Reports (D200A,

D200N), for details.

1.4.3.1.1. Perform an annual review of application PECs assigned to the items the ES

manages and associated program data. This review will evaluate: the continued need

for the application PEC and associated program data; the adequacy of documentation

explaining the rationale for the use of the application PEC; and the accuracy of the

application PEC program data for those PECs for which the ES is responsible. The

ES will perform online file maintenance of this data in D200F.

1.4.3.2. When changing any data element in SIRS, thoroughly and clearly document on

the D200A Notepad the rationale used to arrive at final decision. Each Notepad entry


will include the computation cycle, date change was made, what the change was, why it

was changed, and how it was verified so that a reviewer or auditor can easily understand

the file maintenance that was performed.

1.4.3.3. Provide the IMS/MM the changes made to the initial Factors/Usage Printouts

before the end of the file maintenance period passing along changes as they are made.

1.4.3.4. Document the Factors/Usage Printout with any changes made to data file

maintained on the Program Select screen in D200F including the rationale for the

changes.

1.4.3.5. Sign (literally or with signature stamp), date, and retain the original file copy of

Summary Factors/Usage Printouts within 35 calendar days of the printed product. The

ES will also sign and retain the original marked up copy of the ES Initial Factors/Usage

Printout for which changes were notated. If the signature cannot be easily read, the ES’s

printed name must be included on the documents. A signature on the Factor Printout

signifies the ES has reviewed the information contained in the Factors/Usage Printout,

the ES worked the item and that to the best of knowledge of the ES the information is

correct.

1.4.3.6. Also sign (literally or with signature stamp) and date all Summary computations,

recomputation or INS/NSO Item Status Listing within 10 calendar days of print of the

products for terminations, and within 35 calendar days of the print of the products for

buys, repair, and excess. Their signature on the computation products signifies that the

ES, as a member of the item management team, concurs with the indicated management

actions (e.g., this is the correct configuration for procurement, rationale for

retention/disposal is correct, etc.) and that they have provided all known relevant

technical information to the IMS/MM and PMS that would influence those decisions.

This information includes, but is not limited to, issues concerning interchangeability and

substitutability of NSNs, repair concepts, ERRC coding, and reliability. See paragraph

1.15 and subparagraphs for documentation and product retention requirements.

1.4.3.7. Sign (literally or with signature stamp) and date within 60 calendar days of print

of the products if the computed excess is equal to or less than the previous cycle’s excess

or if the item is in an optimum position.

1.4.4. The PMS:

1.4.4.1. Or MM will schedule repair of unserviceable recoverable assets through organic

or contractor facilities. Contract repair must be considered prior to procurement of new

parts when no organic repair capability is available.

1.4.4.2. For the D200A products output to or pulled by them, review each item’s

reported repair quantities and any condemnations and assets at all repair facilities

[organic, contract and Depot Maintenance Inter-Service Support Agreement [DMISA]),

repair costs, repair lead times, and Source Of Repair (SOR) percent for accuracy and

completeness and must file maintain any needed corrections on the MISTR Repair and

Repair Data (MRPR) screen.

1.4.4.3. Or MM, during surveillance of repair data, will note any trends that would affect

future repair support and spares requirement.


1.4.4.4. When changing any data element in SIRS, thoroughly and clearly document on

the D200A Notepad the rationale used to arrive at final decision. Each Notepad entry

will include the computation cycle, date change was made, what the change was, why it

was changed, and how it was verified so that a reviewer or auditor can easily understand

the file maintenance that was performed

1.4.4.5. Provide any changes to the reported repair quantities and assets to the IMS/MM

and will provide changes to reported condemnations (i.e., condemnations that occur at the

repair contractor that are not passed by CAV AF or D035A) to the IMS/MM and ES

before the end of the file maintenance period, passing along changes as they are made.

1.4.4.6. Sign (literally or with signature stamp) and date the PMS file copy of all

summary MISTR Repair and Repair Data (MRRD) reports within 35 calendar days of

print of the product. If the signature cannot be easily read, the PMS’s printed name must

be included on the documents. A signature signifies the PMS has reviewed the

information contained in the MRRD, the PMS worked the item (as needed) and that to

the best of knowledge of the PMS, the information is correct. When the IMS/MM brings

the computation products to the PMS for coordination, the PMS must also sign (literally

or with signature stamp) and date all computations, recomputations and INS/NSO Item

Status Listings within 35 calendar days of print of the products. Their signature on the

computation products signifies that the PMS, as a member of the item management team,

concurs with the indicated management actions (e.g., this is the correct configuration(s)

for repair, rationale for retention/disposal is correct, etc.) and that they have provided all

relevant information pertaining to depot level repair that would influence those decisions.

This information includes, but is not limited to, issues concerning potential change in

source(s) of repair and/or capacity, change in repair costs, and changes in future repair

lead times. See paragraph 1.15 and subparagraphs for documentation and product

retention requirements.

1.4.5. Management/Supervisors:

1.4.5.1. All levels are responsible for the overall integrity of computed requirements

within their area of responsibility. The authority to review and validate item

computations and to provide advice to senior managers may be delegated; however, it

does not release them from their overall responsibility.

1.4.5.2. To ensure management oversight on decisions regarding excess, the IMS/MM’s

supervisor must review and coordinate on the retention and disposal decisions made in

the RDS.

1.4.6. The IMS/MM, PMS, and ES will:

1.4.6.1. Work every item managed by them during the file maintenance cycle that

requires review. The following review priority sequence is recommended for working

every item during the file maintenance window:

1.4.6.1.1. Termination items must be worked first as they are time sensitive.

1.4.6.1.2. Buy items

1.4.6.1.3. Repair items

1.4.6.1.4. No compute items


1.4.6.1.5. Excess.

1.4.6.1.6. Other items based on their IAC.

1.4.6.2. Work down the IRIS IRL, working every item during the March, June,

September, and December cycles.

1.5. Requirements Segments. SIRS uses historical failure and program data to determine a

failure rate to be applied to a future program. Refer to AFMCMAN 23-101, Volume 3, Chapter

1 for a detailed description of the computation methodology and procedures. Historical pipeline

and lead time data are also recorded and applied to future activity. Requirements are broken

down into the following segments, each of which is computed separately:

1.5.1. Operating requirement - to ensure that all assets removed due to failure will be

replaced at the time of removal.

1.5.2. Condemnations - to replace assets that cannot be repaired.

1.5.3. Lead times - to ensure that a supply of assets is available to replace condemnations

during the time required to order and receive replenishment spares.

1.5.4. Pipeline requirements - to cover the times assets may be unavailable for issue while

they are in-transit between using and maintenance activities.

1.5.5. Repair cycle requirements - to cover the time required to restore unserviceable

recoverable assets to a serviceable condition in a maintenance facility.

1.5.6. Safety level - to cover unexpected fluctuations in demands or variations in pipeline

times. This is the only segment of the computation that does not represent a firm

requirement. It is set according to support and backorder reduction goals determined by HQ

USAF.

1.5.7. Additive requirements - to support special projects, programs, or any other

requirement that do not fit into one of the above categories (see AFMCMAN 23-101,

Volume 4, Chapter 5).

1.5.8. War Reserve Materiel (WRM) requirements and RSP requirements - to support

contingencies and scenarios established by USAF wartime planning documents. SIRS

receives some of this data from interfacing systems and computes the remaining

requirements separately from the above requirements segments.

1.6. Categories of Requirements. SIRS compares computed requirements with available assets

and determines what actions are required to ensure support for future operations. SIRS

determines the most economical use of the existing inventory and provides visibility of quantities

for which there is no anticipated need. SIRS computes the following requirements categories,

also referred to as management actions.

1.6.1. Repair. The quantity of unserviceable recoverable assets to be repaired to ensure that

serviceable assets will be available to replace projected failures.

1.6.2. Buy. The quantity to be considered for acquisition to ensure continued support lead

time from the latest quarterly computation asset cutoff date.


1.6.3. Termination. When available assets are more than sufficient to support computed

requirements, SIRS recommends that all or part of a Purchase Request (PR) or an

undelivered contract quantity of new acquisition be considered for cancellation.

1.6.4. Excess. When SIRS determines that available assets are more than sufficient to

support computed requirements through the foreseeable future, it will display a quantity to be

considered for disposal.

1.7. Schedule. SIRS has four quarterly cycles a year that are keyed to computation asset cutoff

dates of 31 December, 31 March, 30 June, and 30 September. Data from interfacing systems are

input to SIRS after the computation asset cutoff date and at the start of the Initial computation.

Three computations are ran each qtr for SIRS: Initial, Final, and Summary. The IMS/MM,

PMS, and ES will attempt to do all their D200A file maintenance during the D200A file

maintenance cycle (four weeks), which starts after the Initial computation is completed and ends

with the start of the Final computation. There may be a week for file maintenance after the Final

computation is completed and before the start of the Summary computation, but the Summary

computation must be ran as soon as the Final computation is run. The Initial and Summary

computed requirements are sent to the sites for printing. The SIRS online database is file

maintained real time and reflects the latest data from interfacing systems or file maintained data,

whichever was input last. After the Summary computation, neither the SIRS database nor the

CSIS can be updated for that qtr. The SIRS file maintenance screens are closed from the start of

the Summary computation until after the next cycle’s Initial computation is completed. They

are available for the current and previous three consecutive qtrs and for the Mar and Sep cycles

for the 2 years prior to that. The Final and Summary computation run produces the output files

to D200N (CSIS). The Summary computation produces the output files to other interfacing

systems.

1.8. Computation Time Span. To support the budget function, SIRS projects requirements by

FY. Requirements are computed on a quarterly cycle. The computation process includes a

peacetime computation and an Other War Reserve Materiel (OWRM) computation (see

AFMCMAN 23-101, Volume 3, Chapter 4). Both peacetime and OWRM requirements are

computed three times during each quarterly processing cycle. The computations are

programmed to run as Initial requirements computation, Final requirements computation, and

Summary computation.

1.8.1. Cutoff Dates. Requirements are computed on a time-phased basis for a maximum

span of 38 qtrs. The starting point of each quarterly peacetime requirements computation is

the first qtr following the computation asset cutoff date. Once a year, during the 31 March

cycle, the data headings in the computation and the FYs are shifted to the left, and the

various pick-off points for buy, termination, retention, and stratification are established for

that year. On the 30 September cycle, factors are shifted. The time periods described below

are identified in the computation for applying assets and additive requirements, for selecting

data for print, and for determining summary positions. There are periods of the computation

and segments of the computation. The three periods are: buy, termination, and retention.

These are displayed on the computation worksheet and include requirements from the

computation asset cutoff date through a point in time. Segments are discrete blocks of time

not necessarily starting as of the computation asset cutoff date.


1.8.2. CY. The requirement for the CY that is computed on the 31 March cycle includes

data for two qtrs (31 March and 30 June). The requirement for the CY that is computed on

the 30 June cycle includes data only for that qtr that ends on 30 September. There is no CY

requirement developed during the 30 September and 31 December cycles.

1.8.3. AY. Requirements are computed for the full year during the 31 March, 30 June, and

30 September cycles. On the 31 December cycle, three qtrs of data are computed for the AY.

1.8.4. BY. BY identifies the requirements computed for the FY following the AY.

1.8.5. EY. EY identifies the requirements computed for the FY following the BY.

1.8.6. Buy period. This period includes all the requirements computed from the computation

asset cutoff date of the computation through the CY and the AY, plus the Procurement Lead

Time (PCLT). The PCLT may vary from a minimum of one month to the maximum system

capability of 72 months.

1.8.7. BY buy point. This point is selected 12 months beyond the buy period and is used to

determine the computed requirements that would require a BY projection of funds. Another

method for determining this point is that it is PCLT beyond the end of the BY. It is used for

planning purposes.

1.8.8. EY buy point. This point is selected 12 months beyond the BY buy point and is used

to determine the computed requirements that would require a second BY or EY projection of

funds. Another method for determining this point is that it is PCLT beyond the end of the

EY. It is also used for planning purposes.

1.8.9. Termination period. This period identifies the requirements computed from the

computation asset cutoff through the 12 months immediately following the buy period.

1.8.10. Retention period. This period identifies the requirements computed from the

computation asset cutoff date through 3 years beyond the 38th qtr. The retention program is

a single quantity of program that contains 12 qtrs of data based on the projected life of the

weapon and support system.

1.8.11. Retention segment. SIRS computes requirements through the computation program

span of 38 qtrs.

1.9. Initial and Follow-On Spares. SIRS is a replenishment spares computation system. SIRS

normally does not compute the initial spares requirements. Its purpose is to compute follow-on

spares requirements for established items that apply to active systems. Follow-on spares support

normally involves replenishment of assets that have been lost due to condemnations. During the

weapon system provisioning process, the Initial Requirements Determination (IRD) system

(D200H) computes minimum spares requirements to support a weapon system through a

program forecast period, which is the PCLT plus three months past a weapon system’s

preliminary operating capability. These minimum requirements include condemnations through

the procurement lead time, pipeline requirements, and other levels that must be in place to

support newly fielded systems. The Program Office places spares quantities computed in the

IRD against the provisioning contract. The contracting function reports these quantities in the

Acquisition and Due-in System (J018R), which in turn passes them to SIRS as on-order assets.

The IMS/MM ensures these quantities are included in the asset reconciliation. Even though the

IRD computes spares to support pipeline and other initial requirements, SIRS also computes


these requirements once the Non-Cataloged (NC) numbers or NSNs are fed to it, which the on-

order assets will offset.

1.10. Stock Number Establishment. Each item will have an assigned NSN. In some cases,

RIID/D200E will identify two or more NSNs that may be used interchangeably and these items

will be categorized into subgroups. When there is a single subgroup, the most preferred item is

designated the SGM stock number and is also called the family master stock number. When

there is more than one subgroup within an Interchangeable and Substitutable Group (I&SG), then

the most desirable item of the I&SG is the family master stock number. An interchangeable

stock number is an item that is completely (two-way) interchangeable with the SGM stock

number. The Current Stock Number (CSN) or actual NSN is the most CSN assigned to an item;

it may be either a SGM or an interchangeable stock number. The reference stock number is a

stock number that was previously assigned to a CSN. A bachelor stock number is the SGM and

family master stock number for an item that does not have any interchangeable NSNs. A one-

way interchangeable stock number is an item that is related but not exactly a fit. SIRS treats a

one-way interchangeable NSN as a bachelor item, since SIRS operates on SGM NSNs and their

two-way interchangeable NSNs only. A separate computation is made for each completely (two-

way) interchangeable subgroup within an I&SG.

1.10.1. SIRS computes requirements at SGM level including INS and NSO items. After

these SGM requirements have been computed, SIRS performs an additional series of

computations for items that are in an Interchangeability and Substitutability (I&S) family

with more than one SGM. It begins with the least preferred SGM and if it has a buy deficit

(3rd Short) in any qtr of the computation time span, it passes that deficit up to the next

preferred SGM. This is done in the form of a non-recurring “additive” requirement divided

into peacetime, RSP, and OWRM values. SIRS then recomputes the requirements including

repair of the next preferred SGM. This process continues until each SGM in the I&S family

has been recomputed. This ensures that repair is accomplished at the lowest level possible

while at the same time ensuring that only the latest configuration (I&S master) is bought.

The buy deficits on lesser-preferred items are passed to the CSIS (D200N) as a “Buy Not

Required.” SIRS must be allowed to automatically compute the I&S requirement unless: the

item is in an approved forced attrition or forced generation and replacement program (see

AFMCMAN 23-101, Volume 5, paragraph 2.2.3.); all replacement parts have already been

delivered; sufficient assets have been bought to cover the spare requirements; or repair

procedures have been established for the replacement item. Note: If any of the

aforementioned take place, the scheduled replacements have successfully begun, and all the

applications for the item are part of the approved forced attrition or forced generation and

replacement program, the IMS/MM must zero out any minimum depot stock level, additives

and special levels for the lesser preferred item(s) in D200A and zero the repair requirements

from the lesser preferred item(s) on the B21. The ES must zero the application percentage

associated with the lesser preferred item(s). These actions will keep the lesser preferred

item(s) from computing requirements. The ES also must initiate all necessary cataloging

actions; reference AFMCMAN 23-3 and DoD 4100.39-M, Federal Logistics Information

System (FLIS) Procedures Manual.

1.10.2. The RIID file is the sole source for establishing, changing, and deleting NSNs in

SIRS. RIID receives cataloging information from the Item Management Control System

(IMCS)(D043). NSNs cannot be established or deleted in SIRS through file maintenance. A


record is established in the SIRS file when the catalog management data file from RIID

contains a master or current NSN that has not been previously established in SIRS. Each

new master NSN in the RIID file results in a skeleton record in SIRS that contains data from

RIID (see AFMCMAN 23-101, Volume 2, System Level Data and OPR Reports (D200A,

D200N), paragraph 1.8.) pertinent to the master NSN. Each new current NSN in the RIID

file results in a skeleton record in SIRS that contains data from RIID pertinent to that current

NSN. Stock number or catalog changes in the RIID file result in changes to the current or

master NSNs in SIRS.

1.10.3. IMS/MM, also called Manager Designator Codes (MDC), and ES codes are

established and changed in the D035A using the Item Data File Maintenance (MIRB) screen.

D035A passes these codes (using Document Identifier Code [DIC] ZAB) toD043, which

passes the data to RIID, which passes the codes to SIRS.

1.10.4. For a new NSN, SIRS assigns standard default values to some data elements that are

variables for calculating certain requirements segments. In order for SIRS to compute

requirements for an item, the IMS/MM and ES must ensure that the unit cost, BP/System

Management Code (SMC) and at least one application PSC are not blank. These actions will

cause SIRS to assign a compute code Y.

1.10.5. When SIRS computes requirements it will consider failure data for all items in the

subgroup. All computed requirements will be aggregated to the SGM NSN and rolled by

SIRS to the I&S SGM NSN. This allows acquisition of the most preferred I&S SGM NSN to

replenish all NSNs in the subgroup. Customer refusal to use standard interchangeable items

instead of the preferred item is not sufficient grounds for acquiring the preferred item if

assets of interchangeable items are available. Maintenance engineering must resolve the

problems of unacceptable substitution to establish that available assets are unsuitable and will

not be used before any acquisition actions are initiated or adjusted. If an item is determined

to be an unsuitable substitute for all applications, initiate cataloging action to code the item

for disposal (see AFMCMAN 23-3). The ES must also ensure that repair requirements are

not projected on the unsuitable item. If the item has not been removed from all NHAs in use,

the ES must file maintain the forecast MISTR condemnation percents to 100%.

1.11. Review and Adjustment Actions. When any of the following cases apply, repair and

acquisition actions must be adjusted. If applicable, budget requirements projected by SIRS must

also be adjusted before submission to higher headquarters.

1.11.1. First and second replenishment acquisitions.

1.11.1.1. When SIRS computes an acquisition action for an item for the first time, the

safety level and projected condemnations can be budgeted. These requirements are not

acquired until actual failures are reported. However, if condemnations can be completely

justified (engineering analysis, like items with significant condemnation rates, etc.), and

staffed through appropriate Supply Chain Management Group (SCMG) budget offices at

the site (include Funds Management at the site for non-CSAG-S items), prudent

management dictates that acquisition may occur. If actual failures or condemnations are

reported, the base and depot level requirements are based on the percentage of actual data

used in computing the total demand rate.


1.11.1.2. Acquisition of safety levels may be considered when determining provisioning

integrated with production quantities. Initial lay-in issues are not considered failures for

this purpose.

1.11.1.3. When buy quantities are deferred due to the above guidance, the subsequent

year (BY) quantities on the budget CSIS Item Deficit Listing must be increased by the

same quantity to ensure that funds are projected in the proper fiscal period.

1.11.1.4. Repeated deferral of buys for the same items is not allowed. If an item does

not exhibit a demand pattern indicated by the provisioning factors, a reevaluation of the

item factors by the engineering function must be initiated. If after this reevaluation, it is

determined that the factors are accurate, then the item deficit must be deferred outside the

budget window (beyond the EY).

1.11.2. Authorized RSP requirements are budgeted and acquired in the first replenishment

acquisition unless HQ AFMC/A4RM directs deferred acquisition.

1.11.3. Restrictions on uneconomical acquisitions. Acquisition action is not initiated if the

net buy is less than 5% of the annual operating requirement (known as the buy operating

level), unless deferment will cause supply support problems. When the net buy quantity is

less than 5% of the buy operating level, an asterisk appears in the dollar value field of the

Index of Actions printout. Budget submissions will defer uneconomical buys to the

following FY.

1.11.4. Screening Assets. Since SIRS computes worldwide requirements, all available assets

in the Department of Defense (DoD) must be considered to fill those requirements to

preclude unnecessary acquisitions and repairs. Before an acquisition or a repair action is

initiated, the IMS/MM must determine that assets cannot be obtained from any of the below

sources or if use of these sources are not in the best interest of the Government due to shelf-

life, safety, cost/benefit analysis, etc. One example of cost/benefit analysis is: which is less

expensive, repair of the item or using a temporary work request to pull the item from a NHA

that is excess and having the item condition checked Documentation explaining the decision

reached must be retained in the IMS/MM folder for 2 years after the delivery of assets IAW

AFRIMS.

1.11.4.1. Modification. This may include modification of excess inventories, assembly

of excess components, or assets removed as a result of modification programs.

1.11.4.2. NHA assets stratifying to OWRM or Long Supply (Economic Retention,

Contingency or Potential DoD Excess). NHA OWRM or long supply assets may be used

to support lower assembly requirements when there are not or will not be sufficient assets

of the lower assembly to fill the requirement. One of the methods in the following

subparagraphs will be used to determine if the NHA has OWRM or long supply assets

available. Work with the NHA IMS/MM to determine this. If NHA OWRM or long

supply assets are available, conduct a cost-benefit analysis comparing the acquisition cost

of the component item to the cost of removing the component item from the NHA,

conducting a condition check and, if necessary, repairing the component item to

determine whether it is economically feasible to obtain component items using this

method. An attempt will be made to obtain lower assembly assets from NHA

unserviceable assets prior to attempting to obtain then from NHA serviceable assets. The


lower assembly items requested will not exceed the number installed within the NHA

NSN quantity reported as OWRM and long supply.

1.11.4.2.1. For computing NHA items, the Buy Operating Breakout section of the

SGM Comp Worksheet is used (see AFMCMAN 23-101, Volume 3, Computational

Results). Using the data in the EY PD column (EY buy period; procurement lead

time beyond the EY), the OWRM Requirement is subtracted from the Total Buy

Operating Level. The difference provides the POS and RSP requirement. Then, the

Serviceable Assets, Serviceable Due-In Assets, and Net Depot Unserviceable Assets

are added together from the same EY PD column to arrive at the total assets. The

POS and RSP requirement is subtracted from the total assets. If the result is positive,

it equals the OWRM and long supply assets potentially available; if the result is

negative, no assets are available. Note: Serviceable due-in assets can be the result of

a negative asset variance and may not actually be available.

1.11.4.2.2. For INS/NSO NHA items, the Buy/Retention Detail section of the

INS/NSO Item Status Listing is used. Using data in the EY column, the serviceable

assets and assets available from depot repair are added together. Next, the

Buy/Retention Level quantity in the EY are subtracted from the assets. If the result is

positive, it equals the long supply assets potentially available; if the result is negative,

no assets are available. Note: Serviceable due-in assets can be the result of a

negative asset variance and may not actually be available.

1.11.4.2.3. If it is determined that OWRM and long supply assets are available and

the cost benefit analysis says that it is feasible, reclamation of the NHA will be

conducted removing all required components. The ES can request a Full Range List

for the NHA. This will provide a list of the components that could possibly be

reclaimed from the breakdown of the NHA item. Sufficient components may be

reclaimed to cover deficits and economic retention requirements for the component

NSNs. The remainder of the NHA item will be disposed after demilitarization.

1.11.4.3. Reclamation. Sources of reclamation may include:

1.11.4.3.1. Equipment being considered for disposal, or damaged aircraft or

equipment at the 309th Aerospace Maintenance and Regeneration Group.

1.11.4.3.2. Assets being held by other Services and excess to their needs.

1.11.4.3.3. Assets on loan to contractors or other Government agencies and

scheduled to be returned.

1.11.4.3.4. Assets that may be bought back from FMS customers. Reference

AFMCMAN 20-2, Security Assistance Program (SAP) Logistics Procedures, for

additional information.

1.11.4.3.5. Contract repair of unserviceable assets when no organic repair is

available.

1.11.5. Economic Procurement Quantities. Consideration must be given to a vendor’s

minimum quantity or value requirements, which, if ignored, can result in excessive unit

costs. Requirements computations, while reflecting specific quantities to be acquired, cannot

determine the most economical buy in terms of minimum quantities or the most cost effective


method of acquisition. The IMS/MM decides this, based on documentation that contracting

personnel furnish. In addition, Title 10 USC § 2306b requires that each spare part

acquisition action be considered for Multiple Year Procurement (MYP), which allows

acquisition of more than one year's requirement with a single acquisition action. Paragraph

1.13. provides MYP guidance as it pertains to recoverable spares. Reference Title 10 USC §

2210 and 2213 also prohibit the IMS/MM from initiating procurement of CSAG-S items (BC

8) that when added to the inventory would cause the inventory to exceed 2 years of operating

stocks (excluding war reserves). The head of the procuring activity may approve the

procurement of inventory that would not exceed 3 years of operating stocks (excluding war

reserves) if certain exceptions delineated in the USC are met. The head of the procuring

activity is HQ AFMC/CC or as designated by that office. For CSAG-S items, the IMS/MM

must not move out year requirements forward.

1.11.6. Management Review Actions. The AFSC staff will conduct periodic item level

reviews of computed requirements.

1.11.7. All items with a peacetime and/or RSP CY and/or AY buy requirement that also

have a positive asset reconciliation variance may be subject to a complete or partial buy

deferral. A positive asset reconciliation variance indicates that there are more reported on-

hand assets than the known accountable balance of worldwide spares. The buy quantity, up

to the amount of that variance, will be considered for possible deferral until it can be

determined if these additional assets truly exist. If the variance could not be resolved through

research and corrective file maintenance, the buy quantity will be reduced by the amount of

the variance quantity in the ABCS using Code 02W with a corresponding increase in the BY.

1.11.7.1. If the variance quantity is equal to or larger than the combined peacetime/RSP

buy quantity, the entire buy will be deferred to the BY.

1.11.7.2. If the combined peacetime/RSP buy quantity is greater than the variance

quantity, the buy quantity will be reduced by the amount of the variance, beginning with

the peacetime portion of the buy. The variance quantity will be deferred to the BY.

1.11.7.3. Exceptions: To the above guidance are:

1.11.7.3.1. If the positive variance percent is less than or equal to 5%, the dollar

value of the variance is less than or equal to $10,000, and the IMS/MM has

determined that deferral of the buy would significantly affect their ability to support

the customer, they can document the SGM Comp Worksheet with their rationale and

proceed with the buy action after obtaining flight leader approval.

1.11.7.3.2. If the positive variance percent is greater than 5% and/or the dollar value

of the variance is greater than $10,000 and the IMS/MM has determined that deferral

of the buy would significantly affect their ability to support the customer, they must

document the SGM Comp Worksheet with their rationale and obtain squadron level

signature concurring with that decision prior to proceeding with the buy action.

1.11.8. All items with a negative asset reconciliation variance may be automatically

subjected to a complete or partial buy deferral by the internal calculation done within

D200A. A negative asset reconciliation variance indicates that there are less reported on-

hand assets than the net accountable balance of worldwide spares. The computed buy

quantity, up to the amount of that variance, is offset by the serviceable due ins automatically


added by D200A for items with a negative variance. If the variance could not be resolved

through research and corrective file maintenance, any potential buy quantity is reduced by

the amount of the variance quantity.

1.11.8.1. If the absolute value of the negative variance percent is less than or equal to 5%

and the absolute dollar value of the variance is less than or equal to $10,000, and the

IMS/MM has determined that not reducing the assets to the reported quantity would

significantly affect their ability to support the customer, they can document the SGM

Computation Worksheet with their rationale and proceed with the buy/repair action after

obtaining flight leader approval.

1.11.8.2. If the absolute value of the negative variance percent is greater than 5%, and/or

the absolute dollar value of the variance is greater than $10,000, and the IMS/MM has

determined that not reducing the assets to the reported quantity would significantly affect

their ability to support the customer, they must document the SGM Computation

Worksheet with their rationale and obtain squadron level signature concurring with that

decision prior to proceeding with a buy/repair action.

1.12. Life-of-Type (LOT) Buys.

1.12.1. This paragraph describes the process and procedures to be used by the IMS/MM, ES,

and the site Director of Financial Management for LOT buys. Prior to making a LOT buy,

other manufacturing source alternatives addressed in DoDM 4140.01, Volume 3, DoD

Supply Chain Materiel Management Procedures: Materiel Sourcing, paragraph 6e must be

considered. When a LOT buy is necessary, procurement must occur as close as possible to

one PCLT away. AFMCI 23-103, Diminishing Manufacturing Sources and Materiel

Shortages (DMSMS) Program, paragraph 2.3. and AFMCI 23-106, Initial Requirements

Determination, paragraph 1.10.7. authorize the acquisition of spare parts to cover the

anticipated operational life of a weapon system under certain conditions. A LOT buy is

authorized in cases where such actions can be economically justified. A LOT buy is

normally initiated at the end of a production run for initial spares when reestablishment of

production capability for follow-on spares would not be economically feasible or when an

item has been identified as having diminishing manufacturing sources.

1.12.2. Procedures. The decision to apply LOT buy procedures requires evaluation of

support consideration, cost and benefits, and alternative acquisition actions. For new

systems, requirements for items bought under LOT buy provisions will be computed using

the IRD/D200H. If access to IRD is not available, they may be manually computed on

AFMC Form 614, Recoverable Item Initial Requirements Computation Worksheet, per initial

requirements instructions found in AFMCI 23-106. For items already in D200A, a “what if”

re-computation can be run using the weapons system life field on the Basic Management

Data (BMD) screen (see AFMCMAN 23-101, Volume 4, paragraph 1.13.).

1.12.2.1. The following types of items are excluded from LOT buy consideration.

1.12.2.1.1. Items subject to design change or technical obsolescence, except when

dealing with diminishing manufacturing sources and DoDM 4140.01, Volume 3,

paragraph 6e provides no viable cost effective alternatives and the system on which

the item is used will not be phased out near the time of delivery of spares.


1.12.2.1.2. Items that are assigned Acquisition Method Codes (AMC) that indicate

they are to be acquired competitively.

1.12.2.1.3. Items that exhibit an unstable demand history, or with a demand history

that is insufficient to predict long-range demands.

1.12.2.1.4. Items that may be subsequently acquired from the prime contractor at a

price substantially less than the current standard unit cost.

1.12.2.1.5. Items subject to shelf-life deterioration.

1.12.2.2. When a LOT buy is considered for programs that involve other Services or

FMS, the concurrence of the agency or country being supported is required.

1.12.2.3. The following must be taken into account when considering a LOT buy:

1.12.2.3.1. Assets that may be available from reclamation.

1.12.2.3.2. Related costs, such as those for hardware and technical data, and

administrative costs.

1.12.2.3.3. The cost to retain production tooling and test equipment, production start-

up costs, and spares costs.

1.12.2.3.4. The cost of future acquisitions of spares, using the FUP.

1.12.2.3.5. The effects that the costs in paragraphs 1.12.2.3.2., 1.12.2.3.3., and

1.12.2.3.4 may have on spares support.

1.12.2.3.6. The costs to administer and manage excess stocks that would result from

a LOT buy.

1.12.3. Responsibilities for LOT buy.

1.12.3.1. The IMS/MM will:

1.12.3.1.1. Validate the cost effectiveness of a proposed LOT buy, taking into

account the cost considerations in paragraph 1.12.2.3 and its subparagraphs above.

1.12.3.1.2. Obtain the concurrence of other services and FMS customers, if

applicable.

1.12.3.1.3. Prepare a letter containing the justification for the LOT buy, unit cost,

repair cost, quantity on-hand (serviceable and unserviceable), years of usage,

summary of quantities previously purchased and yearly repaired quantities,

recommended quantity to buy, and justification for sole source. The notice from the

contractor is an attachment to this letter.

1.12.3.2. The ES will validate:

1.12.3.2.1. That none of the exclusions in paragraph 1.12.2.1 and its subparagraphs

apply. 1.12.3.2.2. The weapon system’s projected lifespan program projection.

1.12.3.3. The SIRS site OPR and appropriate site financial manager will coordinate on

LOT buys. The 448th Supply Chain Management Wing (SCMW) commander, or

equivalent for non-AFSC managed items, retains final approval for all LOT buys except

as noted in the last sentence of this paragraph. If approved, the 448 SCMW commander


or equivalent must sign and return the LOT buy letter. The signed LOT buy letter

notifies the IMS/MM that the IMS/MM can file maintain the weapons system life field on

the BMD screen (see AFMCMAN 23-101, Volume 4, paragraph 1.13.). If the item is a

CSAG-S item, see additional higher signature level requirements in paragraph 1.11.5.

1.12.4. LOT buys in the Requirements Computation. To preclude approved LOT buy

quantities that have not been delivered from computing into termination, the weapon system

life needs to be file maintained on the BMD screen (see AFMCMAN 23-101, Volume 4,

paragraph 1.13.). If a quantity that has been acquired as part of an approved LOT buy

computes into termination, it must be assigned termination code 07 due to the failure to file

maintain the weapon system life. Do not terminate.

1.13. Identifying Candidates and Requirements for Multiple Year Contracting.

1.13.1. Introduction. Title 10 USC § 2306b authorizes the DoD to enter into multiyear

contracts in order to achieve economic-lot purchases. When appropriate, the IMS/MM’s first

choice must be the use of a Multiple Year Contract (MYC). The MYP program is one way

to satisfy several years’ requirements for spare parts with a single contract. The primary

purpose of the MYP program is to reduce unit cost and lead time. Other potential benefits

include: reduced administrative workload for the IMS/MM, Contracting personnel, and the

PR/MIPR control function; reduced paperwork, better prices and discounts due to larger

quantities; ensured production continuity; and contractor incentive for investment in capital

equipment and facilities. Reference AFMCI 20-102 for additional information. Squadrons

managing spare parts must conduct periodic (at least annual) reviews of multiple year

candidate items. The reviews must determine how well multiple year guidance is being

implemented and identify potential problems with existing guidance. Multiple year

contracting must be a budget requirements review area of interest.

1.13.2. Item Selection. To be considered for the MYP program, an item must meet all of the

following conditions:

1.13.2.1. The item program must be forecastable. A forecastable program is one which

can be determined with a reasonable degree of certainty. Most SIRS items have

forecastable programs.

1.13.2.2. The item must compute into a deficit buy position in the AY and the BY, as

indicated on the CSIS Deficit Listing. Items may also compute deficits beyond the BY

and still be eligible for the MYC. However, they must compute into a deficit in the AY

and the BY.

1.13.2.3. For an item to be considered for a 3-year multi-year contract, the item must be

in a buy position in the apportionment, budget, and extended years on the CSIS listing.

RSP and OWRM (if OWRM funds are available) deficits may be included as part of the

first year’s buy.

1.13.2.4. For 4 or 5-year buys, consider items that compute condemnations (base, depot

overhaul, and Job Routed JR]) greater than 10% of the computed OIM operating

requirement plus the total Depot Level Maintenance (DLM) program. The quantities to

be procured in the fourth and fifth years must never exceed the forecasted condemnations

(condemnation percent times forecasted reparable generations). In addition, the item


must be of stable design and configuration. It will not be scheduled for replacement or

for a modification that would affect the failure rate.

1.14. Item Contracting History Record. For reference purposes, the IMS/MM will keep a

record of significant acquisition process events for their items using an AFMC Form 318, Item

Contracting History Record. Mandatory item contracting history records will be retained

utilizing AFMC Form 318 (paper or electronic) or the E-318 in J018R; documentation will be

maintained in a location readily available for audits/inspections. The IMS/MM will review the

AFMC Form 318 header information annually for accuracy and currency, and update if

necessary.

1.15. Documentation Requirements.

1.15.1. The IMS/MM will retain an item folder. This requirement includes all AFMC Forms

318 and Asset Reconciliation reports. For D200A Asset Reconciliations, retain March

Summary only - Final if Summary is not printed. Copies of the D200A Asset

Reconciliations for June, September, and December may be thrown away upon receipt of the

products for the following March Computation Cycle. If the June, September or December

products have documentation for actions taken that are not on the March Asset

Reconciliation Notepad, that documentation must also be retained and attached to the Asset

Reconciliation. Retain historical AFMC Form 247, Asset Reconciliation - Investment Items,

and historical AFLC Form 47, Asset Reconciliation - Investment Items, as long as the item is

in the AF inventory. If the Summary computation is not printed, keep the products from the

Final computation. Reference Table 1.1 for when item purchases were initiated.


Table 1.1. Item Purchases Were Initiated Destroy Documents and Products 2 Years After

Contract Closure IAW Paragraph 1.15.2.

Product D200 Product Number

1 Copy of contract (or electronic file copy of the contract

-- must be readily accessible and easily readable and

printable by anyone needing the information)

2 PR/MIPRs (attach to the PR/MIPR a copy of the

computation, recomputation, or INS/NSO Item Status

Listing on which the PR/MIPR is based)

3 D220 Provisioning Documents

4 Provisioning Item Order (PIO)

All supporting documentation such as:

5 IRD Item Worksheet AD200.H40108ZP

6 IRD Programming Checklist AD200.H60108ZP

D200A Products:

7 Initial MISTR Repair and Repair Data (IMS/MM) ** AD200.AFCA#8IH

8 Initial MISTR Repair and Repair Data (PMS) ** having

annotations

9 Initial Factors/Usage Printout having annotations (see

paragraph 1.15.10.)

AD200.AFDA#85U

(Keep the summary products listed below, or final products if summary products are

not available, containing approval signatures)

10 SGM Computation Worksheet Requirements AD200.AIDA#88I

11 Consolidated Assets and Additive Requirements AD200.AHBA#87B

12 Adjusted Level Verification Worksheet AD200.ACKA#8BO

13 MISTR Repair and Repair Data (IMS/MM) ** AD200.AFCA#8IH

14 MISTR Repair and Repair Data (PMS) **

15 Factors/Usage Printout A-D200.AFDA#85U

16 SGM OWRM Computation Worksheet AD200.AIPA#88K

17 INS/NSO Item Status Listing AD200.ANBAX82B

18 Entire signed “What If” Item Recomputation (if

applicable)

Note: ** MISTR Repair and Repair Data reports are

not required to be retained for AF SICA NIMSC 5 items

since the AF doesn’t perform depot level repair.

1.15.2. Destroy documentation supporting terminations after 2 years or after termination is

closed, whichever is greater. Documentation includes: all cataloging data and source

material, documentation supporting applications, and termination model.

1.15.3. Destroy documentation 2 years after data is superseded or obsolete in D200A.

Documentation includes: all cataloging data and source material and documentation

supporting applications.

1.15.4. Destroy after 2 years. Reference Table 1.2


Table 1.2. Destroy After 2 Years.

Document or Product Product Number

1 Backorder List (if used as basis for validating and/or

changing requirement in D200A or ABCS Repair)

2 Cooperative Logistics Supply Support Arrangement

(CLSSA) Requirements Listing

U-W001.-GBK product

3 FMS Retention Levels U-W001.-RAA product

4 J018R Category I and IIR Requirement Data Report A-J018R.-5YB-M5-850

product

5 Processing Master Record Quarterly Asset Listing A-D035B-1LX-Q7-GAE

product

6 Contract Repair Reports

1.15.5. Destroy the following pushed products after 2 years (unless needed to support buy or

terminations, per paragraph 1.15.2 and paragraph 1.15.3). (See Table 1.3)

Table 1.3. Pushed Products Destroyed After 2 Years Unless Needed to Support Buy or

Terminations.

Product Product Number

1 Initial MISTR Repair and Repair Data (IMS/MM) ** AD200.AFCA#85V

2 Initial MISTR Repair and Repair Data (PMS) ** having

annotations

3 Initial Factors/Usage Printout having annotations (see

paragraph 1.15.10.)

AD200.AFDA#85U

(Keep the summary products listed below, or final products if summary products are

not available, containing approval signatures.)


5 Consolidated Assets and Additive Requirements AD200.AHBA#87B

6 Adjusted Level Verification Worksheet AD200.ACKA#8BO

7 MISTR Repair and Repair Data (IMS/MM) ** AD200.AFCA#85V


9 Factors/Usage Printout AD200.AFDA#85U

10 Item Future Peace Program AD200.AEBA#8AC


12 INS/NSO Item Status Listing AD200.ANBA#82B

13 Entire Signed “What If” Item Re-computation (if

applicable)

14 All Final Indices of Action for Term ***

15 All Final Indices of Action for Excess ***

16 All Final Indices of Action for Buy ***

17 All Final Indices of Action for Repair ***

18 Any executive management summary reports

19 Any reports documenting repair of D200A items

20 ABCSB21 Quarterly Projection Worksheet


21 Any reports documenting excess D200A items

22 Quarterly Base Repair Cycle Time report

23 Quarterly Order and Shipping Times report

24 Quarterly Reparable Item Transportation Time report

25 ES Review List AD200.AKEA#8ES

26 IMS/MM Review List AD200.AKBA#8DS

Note 1: *** According to AFSC local guidance

Note 2: ** MISTR Repair and Repair Data reports are not required to be retained for

AF SICA NIMSC 5 items since the AF doesn’t perform depot level repair.

1.15.6. Destroy Initial D200A product after receipt of Final D200A product unless they

contain pen and ink documentation required to support actions taken (*** According to local

guidance). Reference Table 1.4

Table 1.4. Destroy Initial D200A Product After Receipt of Final D200A Product Unless

Pen and Ink Documentation Required to Support Actions Taken.



2 INS/NSO Item Status Listing AD200.ANBA#82B

3 MISTR Repair and Repair Data (ES) ** AD200.AFBA#85V

4 Factors/Usage Printout AD200.AFDA#85U


6 Asset Reconciliation – Investment Items AD200.AKAA#8AK

7 Item Past Program AD200.AE3A#8AA


9 Predictive Logistics (PRELOG) Equations AD200.ADSA#86E

10 All Indices of Action for Term ***

11 All Indices of Action for Excess ***

12 All Indices of Action for Buy ***

13 All Indices of Action for Repair ***

Note 1: *** According to AFSC local guidance.

Note 2: ** MISTR Repair and Repair Data reports are not required to be retained for

AF SICA NIMSC 5 items since the AF doesn’t perform depot level repair.

1.15.7. Destroy Final D200A products after receipt of Summary D200A product (unless

signature document). Reference Table 1.5


Table 1.5. Destroy Final D200A Products After Receipt of Summary D200A Product

Unless Signature Document.


1 *SGM Computation Worksheet Requirements AD200.AIDA#88I

2 *INS/NSO Item Status Listing AD200.ANBA#82B

3 *Factors/Usage Printout AD200.AFDA#85U

4 MISTR Repair and Repair Data (ES) ** AD200.AFBA#85V

5 MISTR Repair and Repair Data (IMS/MM) ** AD200.AFCA#85V



8 Asset Reconciliation – Investment Items AD200.AKAA#8AK

9 Item Past Program AD200.AE3A#8AA


11 PRELOG Plots AD200.AFVA#86B

12 All Indices of Action for Term ***

13 All Indices of Action for Excess ***

14 All Indices of Action for Buy ***

15 All Indices of Action for Repair ***

Note 1: *If used for the signature document, follow rules

for paragraphs 1.15.2., 1.15.3. or 1.15.6. as applicable.

Note 2: ***According to AFSC local guidance.

Note 3: ** MISTR Repair and Repair Data reports are not

required to be retained for AF SICA NIMSC 5 items since

the AF doesn’t perform depot level repair.

1.15.8. Destroy on receipt of next cycle’s products (see Table 1.6 ).

Table 1.6. Destroy on Receipt of Next Cycle’s Products.


1 Job Order Production Master System (G004L) Exception

Notice

2 Final Item Past Program AD200.AE3A#8AA

3 Final Item Future Peace Program AD200.AEBA#8AC

4 Final PRELOG Equations AD200.ADSA#86E

5 Summary PRELOG Plots AD200.AFVA#86B

6 Exception Report for Quarterly Repair Input Data

(IMS/MM) AD200.AANAC87@

7 Exception Report for Quarterly Repair Input Data

(IMS/MM) AD200.AAPAC88@

1.15.9. All documentation for estimated factors, rates, and percents including studies,

methodology, and calculations used to arrive at them and documentation of key assumptions,

facts, specific details, decision makers’ names and signatures, and dates of decisions will be

retained for 2 years after any resultant buy quantities are delivered or for 2 years after any

resultant termination action has been completed. If no buy or termination resulted, the

documentation will be retained for 2 years after repair actions resulting from them have been


completed. Before the ES discards products, the ES will check with the IMS/MM to

determine if buy, repair or termination actions were taken based on the products and if so

when the products can be discarded based on the preceding information.

1.15.10. The ES will retain information provided by the PMS or IMS/MM that the ES uses

for a basis of file maintenance for 2 years after delivery of assets or termination of contract.

If no buy, repair, or termination action resulted from the ES file maintenance of the

information provided by the PMS or IMS/MM, the information may be destroyed after 2

years. Before the ES discards products, the ES will check with the IMS/MM to determine if

buy, repair or termination actions were taken based on the products and if so when the

products can be discarded based on the preceding information.

1.15.11. The IMS/MM will retain information provided by the PMS or ES that the IMS/MM

uses for a basis of file maintenance for 2 years after delivery of assets or termination of

contract. If no buy, repair, or termination action resulted from the IMS/MM file maintenance

of the information provided by the PMS or ES, the information may be destroyed after 2

years.

1.15.12. Before the PMS discards products, the PMS will check with the IMS/MM to

determine if buy, repair, or termination actions were taken based on the products and if so

when the products can be discarded based on the preceding information.

1.16. Performance-Based Logistics (PBL) Contracts.

1.16.1. When a PBL contractor is required by the contract to do all the demand and supply

planning, including requirements calculation for the items, and is using its own data systems

to fulfill the obligation, the PBL contractor and depot IMS/MM, ES, and PMS are not

required to check within D200A/F the inputs of Government systems overlaying to D200A/F

for those items covered by the PBL contract. The personnel responsible for inputting the

data into the input systems are responsible for the accuracy of the data provided. The

IMS/MM will ensure that the appropriate PBL BP code “Px” and the appropriate PBL SMC

are file maintained into D200A (see AFMCMAN 23-101, Volume 4, Chapter 1). The PBL

contract will require the PBL contractor to provide the following for each of the NSNs on the

contract: Government assets by Supply Condition Code (SCC) at the contractor facility,

units repaired, condemnations, repair shop flow time, Administrative Lead Time (ALT),

Production Lead Time (PLT), URC, and unit purchase costs for the NSNs on the contract to

the existing AF systems.

1.16.2. The AFSC/LG will ensure the PBL contract arrangement fulfills DoDM 4140.0,

Volume 10, DoD Supply Chain Materiel Management Procedures: Metrics and Inventory

Stratification Reporting, mandates for a CSIS on every item and the SSIR covering all items

regardless of funding. This provides for the general accounting requirement in 50 USC §

412. For the SSIR, variances on NSNs for which a PBL contractor is responsible, the site

SSIR OPR must use the explanation: “Item is managed by a PBL contractor.”

1.16.3. The site must incorporate in the PBL contract, stipulations requiring the PBL

contractor to comply with 10 USC § 2213 when stock funds are used to procure assets (see

paragraph 1.11.5).


1.16.4. The site must incorporate in the PBL contract, stipulations requiring the PBL

contractor to accept and respond to Air Force Audit Agency and US Government

Accountability Office audits on the items they are managing under the PBL contract.

1.17. “Dead Items” in D200A.

1.17.1. A dead item meets all of the following criteria:

1.17.1.1. No usage in the past 3 years.

1.17.1.2. No assets reported during the last 8 qtrs.

1.17.1.3. Does not have new item code N.

1.17.1.4. No non-recurring additives.

1.17.1.5. No Requirements Data Exchange (RDE) recurring additives.

1.17.1.6. No special levels.

1.17.1.7. No minimum depot safety level.

1.17.1.8. No estimated rates and percents.

1.17.1.9. Does not have a program begin date within the last 7 years.

1.17.1.10. Item PSC is all zeroes.

1.17.1.11. Application percent is zero.

1.17.1.12. Quantity per assembly is zero.

1.17.1.13. Federal Supply Classification (FSC) does not begin with 814.

1.17.2. The IMS/MM must review the “dead items.” The “dead item” NSN must be

assigned a “not stocked” AAC, or AAC Y. If the “dead item” NSN has other Service users,

it must be requested that they assume management for the item. If it is decided to retain the

“dead item” without taking one of these actions, such action must be approved by the center

commander or his/her delegated representative.


Chapter 2

USING RMS

2.1. Introduction. The RMS operates on a computer at Hill Air Force Base (AFB), Utah.

Access to view data and file maintain data can be done using Personal Computers (PCs) at any

site.

2.2. Roles and Responsibilities.

2.2.1. The SIRS Functional Advocate and Site Functional Advocates at Hill, Robins, and

Tinker AFBs will serve as the Information Owner/OPRs for their applicable subsystems.

The SIRS Functional Advocate performs the same functions as the Information Owner/OPRs

when the personnel requiring access are not assigned to Hill, Robins, or Tinker AFBs.

2.2.2. Site Functional Advocates approve AFMC ICP D200A/N access requests for locally

assigned DoD Component personnel and DoD contractors at their site location.

2.2.3. The SIRS Functional OPR approves D200A/N access for DoD Components, AF

Major Commands (MAJCOM), AFSC Logistics Directorate (LG), Air Force Life Cycle

Management Center (AFLCMC) Program Office, DoD contractors, and Site Functional

Advocates.

2.3. System Access.

2.3.1. Authorization to access D200A/N is determined by the requestor’s government

affiliation and security clearance, and is controlled by a User Identification (USERID).

2.3.1.1. Potential D200A/N users are DoD employees (military, civilian, or Advisory &

Assistance Service [A&AS] Contractors). Table 2.1 identifies requestors that may/may

not gain system access.


Table 2.1. Requestor Types Authorizations, and Approving Authorities.

Requestors Authorized

Access

Approving Authority

Other Service/Agency Yes SIRS Functional OPR

MAJCOMs

HQ AFMC Yes HQ AFMC/A4RM

AFSC/LG Yes SIRS Functional OPR.

Note: Site Functional

Advocates at Hill, Robins,

and Tinker Air Force Bases

may approve locally

assigned AFMC, DoD

services personnel, and

contractors at their sites.

635th Supply Chain Operations Wing (SCOW) and

subordinate units Yes

448 SCMW and subordinate units Yes

AFMC Inventory Control Points (ICP) Yes

AFLCMC Program Office Yes

Air Force Audit Agency (AFAA) Yes

A&AS Contractors Yes

Foreign Nationals No

Government Furnished Equipment

(GFE)/Government Furnished Material (GFM)

Repair and Production Contractors

No

Contractor ICPs and PBL Contractors (Level III) No

2.3.1.2. IAW DoD 5200.2-R, Personnel Security Program, subsystem access is limited

to those individuals determined trustworthy as a result of the favorable completion of a

National Agency Check (NAC) or Entrance NAC (ENTNAC) or who are under the

escort of cleared personnel. Where escorting such persons is not feasible, a NAC shall be

conducted and favorably reviewed by an appropriate DoD Component Agency or activity

prior to permitting system access. Requestors pending security clearance must complete

and provide a Letter of Responsibility (LOR) along with the SAAR. The LOR must be

signed by the requestor’s government supervisor and maintained by the applicable

system’s Functional Advocate.

2.3.2. Authorized personnel gain access to D200A/N by submitting a DD Form 2875, System

Authorization Access Request (SAAR), along with a LOR (if applicable) to the SIRS

Functional Advocate.

2.3.2.1. Individuals requiring access to more than one RMS subsystem must document

each subsystem required on the DD Form 2875.

2.3.2.2. A&AS contractors must submit Sponsor and Non-Disclosure Letters (signed by

their government supervisor or representative) along with the SAAR and LOR (if

applicable) to gain system access. See Table 2.1 for D200A/N approval authorities.

Note: Contractors must reaccomplish SAAR and associated letters prior to contract

expiration date.

2.3.2.3. Requestors will complete DD Form 2875 IAW instructions provided on page

three of form template and Table 2.2


Table 2.2. D200A/N Unique SAAR Instructions.

Block Field Name Input Value

N/A Location “Hill AFB” (this is the location

where the database resides – not the

requestor’s duty location)

13 Justification for Access 1. Narrative explaining how

requestor will use access and/or why

access is required.

2. Provide the applicable type access

required (i.e., Read Only or File

Maintenance capability for

IMS/MM, ES, or PMS; site

Functional Advocate or AFMC

Functional Advocate) and the

applicable domain(s) required (i.e.,

production, test or training region).

Data Query for certain personnel.

Note: This requirement may not

apply to all subsystems.

14 Type of Access Required Place an “X” in the “Authorized”

box

Note: Privileged access is reserved

for individuals responsible to amend

or change system configuration,

parameters or settings.

27 Optional Information Provide a four-digit (all numeric)

Personal Identification Number

(PIN) to be used for verification

when requesting password reset

from the Defense Information

Systems Agency (DISA). Note:

The Functional Advocate will assign

PINs for SAARs submitted without

them.

2.3.2.4. Once the supervisor, Security Manager, and Information Assurance Officer

(IAO) have completed their blocks and digitally signed the DD Form 2875, the form is

returned to the requestor.

2.3.2.5. The requestor sends the DD Form 2875 and associated documents via electronic

mail (E-mail) to the appropriate system Functional Advocate (Information Owner/OPR).

2.3.2.6. The Functional Advocate E-mails the digitally-signed DD Form 2875 to Ogden

DISA POC to obtain the requestor’s USERID.

2.3.2.7. Upon return of the requestor’s credentials from DISA:

2.3.2.7.1. The D200A/N program office establishes the profile parameters within

D200A/N.


2.3.2.7.2. The Functional Advocate annotates user credentials on the DD Form 2875,

saves the form, and returns it and the instructions for obtaining a temporary password

to the requestor, requestor supervisor, or unit access request OPR.

2.3.3. DD Form 2875 Maintenance. The D200A/N program office will maintain DD Forms

2875 for every active user of D200A/N. The SIRS and Site Functional Advocates will

maintain DD Forms 2875 for those active D200A/N users they granted access approval. The

IAO will have access to these files as needed.

2.3.4. Annual D200A/N Access Authorization Reconciliation.

2.3.4.1. October of each year, the SIRS Functional Advocate will perform a system

reconciliation by providing a list of all current D200A/N system user accounts to Site

Functional Advocates.

2.3.4.2. SIRS and Site Functional Advocates will use this list to:

2.3.4.2.1. Identify unauthorized users and request account deletion actions by

submitting the DD Form 2875 directly to Ogden DISA. All accounts for users who

have been reassigned, terminated, separated from the government, or who no longer

require system access will be deleted.

2.3.4.2.2. Validate the roles of remaining authorized users. User roles may have to

be adjusted depending on nature of requestor’s assigned duties. DD Forms 2875 with

modified user roles will be submitted to the appropriate D200A/N Functional

Advocate, and will follow the same procedures as required for initial access.

2.4. RMS Applications Access. The procedures to access the RMS applications differ

depending on the communications package used and whether or not the mainframe or Graphic

User Interface (GUI) is selected. The CSIS is available via both methods, but due to screen

width requirements, the mainframe is the preferred method of access. The other applications are

available via mainframe or GUI which are described below.

2.4.1. Access to RMS via the Mainframe. One method to access the mainframe is via the

DISA Multi-Host Internet Access Portal (MIAP) https://miap.csd.disa.mil/. Users follow

the account registration and MIAP Login instructions on the main MIAP page. Informational

links to include Online Support and the MIAP User’s Manual are located on the home page.

A MIAP account may be created if the user has a Common Access Card (CAC). The user

will still be issued a USERID, but login is allowed with a CAC and Personal Identification

Number (PIN). When setting up an account, select Ogden as the Community of Interest.

Once registered and logged in, the user will be asked to select from a list of links they are

authorized to use. For RMS, double click on OGD MODEL5. At the Enter logon prompt,

the user will enter their RMS USERID and password. At the RMS Main Menu, type an “X”

in the blank before IOE (Initial Operating Environment) or type “IOE” at the Command

(CMD) line to get to the CSIS; see AFMCMAN 23-101, Volume 6, Central Secondary Item

Stratification (D200A, D200N). To reach the other RMS applications, type an “X” in the

blank before FOE (Final Operating Environment) or type “FOE” at the CMD line. The FOE

screen appears and depending on USERID permissions, users can access DIS (Display) and

may be able to also access DQ (Data Query), FM (File Maintenance), OP (Output Products),

and TRND (Trend Analysis). Typing in DIS brings up the DISPLAY screen, which provides

access to the following systems: AI – Application/Indenture portion of Applications,

https://miap.csd.disa.mil/


Programs, Indentures (API) (D200F), EQP – Equipment (EQP) (Equipment Item Process

[EIP], D200C), PRGM – Programs (PRGM) portion of API (D200F), SIRS –D200A, and

RIID –D200E.

2.4.1.1. To access SIRS, type an “X” in the blank before SIRS or type in SIRS at the

CMD line. For function keys see paragraph 2.7. The entire command string (e.g., DIS

SIRS Stock Number Data [SND] War Data [WARD]) can be typed in followed by a

period even if the typing goes over the F1 and F10 data displayed.

2.4.1.2. To log off of SIRS, users can back out, screen by screen, using either the F10 or

F11 key, or type DONE on the CMD line. Log off the RMS using local procedures.

2.4.2. Access to RMS Using GUI. The most common and easiest method is to access RMS

with the GUI. The GUI capability serves as a screen template over the basic RMS to provide

a Windows environment with mouse “point and click” access to RMS screens and data

elements. The screen shots and screen access instructions in this manual are based on the

GUI access method.

2.4.3. To access RMS using GUI, the GUI software must be loaded onto the user’s PC.

Instructions can be accessed via the RMS GUI Help link on the D200A web page.

2.4.4. Once logged on, the Display News screen appears. Users may also access an

application by double clicking on it at the top of the screen. RMS can be navigated using the

drop down menus (paragraph 2.5.1) or screen by screen (paragraph 2.5.3). OP-REVIEW

allows users to check on the status of their output print product job.

2.5. SIRS GUI Navigation.

2.5.1. GUI Navigation Using Drop Down Menus. Users, who know their final screen

destination, will find the SIRS drop down menus to be a quick and convenient form of

navigation. From the RMS Main Menu, select SIRS from the menu selections across the

very top of the screen by pointing and clicking on “SIRS”.

2.5.2. After selecting SIRS, additional levels of screen menus will appear that will allow

users to select the mode and type of data desired. The arrow to the right of the menu

selection indicates that there are additional menu levels available. Hold the left mouse key

down to navigate through the menu selections. Once the desired selection is highlighted,

release the mouse button, and the selected screen will appear. When viewing most SIRS

data, “DIS” is selected at the first level menu; “SND” is at the second or mid-level, and the

menu for accessing the lowest level screens is displayed.

2.5.3. GUI Navigation Screen By Screen. Users who do not know their final screen

destination may navigate screen by screen. Navigation is intuitive and acronyms are spelled

out. From the RMS Main Menu, select “FOE Final Operating Environment.” On the next

screen, select the desired mode, such as “DIS Display” or “FM File Maintenance,” then

select “SIRS Secondary Item Requirements System.” The next screen will list the same

menu selections offered by the multiple levels drop down menu, but the acronyms are spelled

out. Point and double click at the selection and that screen will appear, with the acronyms

again spelled out.

2.6. Organization of the SIRS Online Screens. After logging onto the RMS, the first screen

offers a choice of FOE or IOE. The CSIS or D200N is the only system under the IOE (see


AFMCMAN 23-101, Volume 6, Chapter 7). Selecting the FOE screen gives the user a menu

with five choices: DIS, DQ, FM, OP, and TRND. The DIS menu is explained in paragraph

2.7. DQ is only available to the AFSC OPR and is not covered in this manual. The FM menu is

explained in paragraph 2.10. The OP menu is explained in paragraph 2.11. The TRND

selection is only for the weapon systems program data of the API (D200F) which is explained in

AFMCMAN 23-101, Volume 2, paragraph 6.2.

2.7. Display Screens. The user must have a valid USERID and password for each RMS system

to view the data on the DIS screens. To view SIRS data from the DIS main menu, select the

SIRS menu.

2.7.1. Interrogation information is available as of the computation asset cutoff date, which is

displayed in the upper right corner of each screen. The online interrogation screens also

provide a 2-digit code to indicate the segment of the quarterly SIRS computer run. The first

position indicates the segment of the qtr: “I” for Initial, “F” for Final, and “S” for Summary.

The second position indicates the number of times the item has been re-computed for that

computation cycle. Individual data element file maintenance changes are updated

immediately on the display screens upon the successful input of file maintenance actions.

However, the use of the updated data values in the computation is not reflected on the display

screens until either a FRIR screen computation is run (see paragraph 2.10.5), or a Final

computation or Summary computation is run. For example, the revised quantity that resulted

from the file maintenance of an additive requirement would be reflected on the Display

Additive Requirements (ADRQ) screen, but the revised quantity would not appear on the

Display Subgroup Master Computation Worksheet (SMCW) screen until either the For Real,

Final or Summary computations were run.

2.7.2. The following display screens are available to view SIRS data. The screen string

commands required to access the data are also listed. Using GUI, the user can point and

click on the “drop down” boxes to select the desired Display screen. Note: The screen

strings displayed below are the commands to be used with the mainframe and with the GUI

menus. With the GUI “drop down” boxes, the sequence for the “DIS” and “SIRS” is

reversed. The Product Format Information (PFI) selection brings up only one screen, the IRL

selection screen.

2.7.3. The following are summaries about the data on each display screen.

2.7.3.1. The AAMD (reference AFMCMAN 23-101, Volume 3) menu provides access to

the five screens displaying data from the Aircraft Availability Model (AAM)

computation. The SIRS Functional OPR uses this data.

2.7.3.2. The CW menu has three selections.

2.7.3.2.1. The INIS Listing displays the computational results for INS and NSO

items. It provides computed buy, repair, termination, and excess results by FY (CY,

AY, BY, EY), and retention. The screen has four pages: 1) Basic Management Data

- buy and repair requirements, termination and excess quantities; 2) Repair detail; 3)

Buy/retention detail; and 4) Interchangeable and substitutable grouping (see

AFMCMAN 23-101, Volume 3, Chapter 5).

2.7.3.2.2. SMCW displays the computational results for all computing items. It

provides computed buy, repair, termination, and excess results by selected future


“pick-off points” that follow the computation asset cutoff date. The selected pick-off

points are the 1st qtr (the immediate qtr following the computation asset cutoff date),

the PCLT (the future qtr that is PCLT beyond the computation asset cutoff date), CY

PD (the future qtr that is PCLT beyond the end of the CY), AY PD (the future qtr that

is PCLT beyond the end of the AY), BY PD (the future qtr that is PCLT beyond the

end of the BY), EY PD (the future qtr that is PCLT beyond the end of the EY), and

RETN (the Retention segment of the computation). The 15 screens are described in

AFMCMAN 23-101, Volume 3, Chapter 1.

2.7.3.2.3. SOCW displays the computational results of the SGM OWRM

computation. The screen has three pages: 1) Basic Management Data; 2) War and

peace rates and percents used in the OWRM computation; and 3) OWRM

computation lines for months 1, 2, 3, 6, 9, and 12. See AFMCMAN 23-101, Volume

3, Chapter 4.

2.7.3.3. The Data Type Interrogations (DTI) menu has two frequently used selections.

2.7.3.3.1. In Service Asset (ISA) SRAN Assets displays the base asset balances,

levels, and Due-Out to Maintenance (DOTM) by CSN, account code, and individual

Stock Record Account Number (SRAN). The data is displayed on left and right

screens. The right screen displays SCC X assets as an informational entry (see

AFMCMAN 23-101, Volume 4, paragraph 6.5.14.

2.7.3.3.2. SUD displays the base and depot usage data by CSN, account code, and

individual SRAN and provides the gains and losses data used in the asset

reconciliation process. The data is displayed on left and right screens (see

AFMCMAN 23-101, Volume 5, paragraph 1.2.).

2.7.3.4. The Factors/Usage Data (FUD) menu has 11 selections.

2.7.3.4.1. The FAD displays the application data for the item that was input to the

API system and then passed to SIRS. The application data reflected is the application

designator (called the Standard Program Designator in API), application PSC, MIEC,

program begin date, QPA, and the application percent. This is page 7 of seven

screens that shows the data reflected on the Factors/Usage Printout (see AFMCMAN

23-101, Volume 5, paragraph 2.23.).

2.7.3.4.2. FBD (see AFMCMAN 23-101, Volume 5, paragraph 2.19.) displays Basic

Management Data (manager codes, item PSC, Interim Contractor Support

(ICS)/Reliability Improvement Warranty (RIW) code and expiration date, base

Reparable This Station (RTS) exclusion indicator, safety level exclusion code, FIC,

SOR percents, unit price, and URC, and SCC X assets). This screen also displays the

part number, Contractor And Government Entity (CAGE) code and can be accessed

by either the SGM stock number or by part number and CAGE. FBD is the first of

seven screens that display the data on the Factors/Usage Printout (see Volume 5).

These seven screens are linked and can be accessed from any of the seven screens by

pointing and clicking to the page number at the bottom of each screen. The seven

screens and their applicable page numbers are: 1) FBD 2) Rates and percents; 3)

Forecast rates and percents; 4) Usage History; (5), Total SGM Usage History; (6),

Past Factors; (7), and FAD (7).


2.7.3.4.3. FRAP displays the current, 1st, 2nd, 3rd, 4th, and 5th forecasted values for

the 16 rates and percents and Mean Time Between Demands (MTBD) used in the

SIRS computation. This is page 3 of the seven screens that show the data reflected on

the Factors/Usage Printout (see AFMCMAN 23-101, Volume 5, paragraph 2.21.).

2.7.3.4.4. MRPR displays the past 12 qtrs of overhaul MISTR repair quantities by

SOR, production/contract number, Contract Line Item Number (CLIN), and the

associated URC, supply to maintenance days, shop flow days, and serviceable turn-in

days. Qtrs 1-8 are displayed on the left screen, where qtr 1 is the most recent past qtr,

and qtrs 9-12 are displayed on the right screen (see AFMCMAN 23-101, Volume 4,

paragraph 8.5.).

2.7.3.4.5. PE PRELOG Equations displays the equations used by PRELOG.

PRELOG is one of the five methods in SIRS for computing the Total Organizational

and Intermediate Maintenance Demand Rate (TOIMDR) used for computing

requirements. The ES and OPR use this data (see AFMCMAN 23-101, Volume 5,

paragraph 4.5.).

2.7.3.4.6. PF displays the past factor computed values for the past 2 years (eight qtrs)

for all of the rates and percents. Also the Moving Average History (MAH) and the

individual qtr values are displayed on two vertical pages (top and bottom). The first

PF screen is page 6 of the seven screens that show the data reflected on the

Factors/Usage Printout (reference AFMCMAN 23-101, Volume 5, paragraph 2.22.).

2.7.3.4.7. PP displays a plot for an SGM. PRELOG is one of the five methods in

SIRS for computing the TOIMDR used for computing requirements. The ESs and

OPRs use this data (see AFMCMAN 23-101, Volume 5, paragraph 4.4.).

2.7.3.4.8. PPH is the first of three screens that displays PRELOG data and allows the

user to view a single plot header for a specific SGM. The three screens are linked and

can be accessed from any of the three screens by pointing and clicking to the page

numbers at the bottom of each screen. The three screens and their applicable page

numbers are: 1) PPHs; 2) PPs; and 3) PRELOG Equations (see AFMCMAN 23-101,

Volume 5, paragraph 4.3.).

2.7.3.4.9. RAP displays the 16 rates and percents used in the computation, plus the

MTBD. The last used, 24-month, 12-month, PRELOG, and exponential smoothing

computed values for each of the 16 rates and percents and MTBD are displayed. This

is page 2 of the seven screens that show the data reflected on the Factors/Usage

Printout (see AFMCMAN 23-101, Volume 5, paragraph 2.20.).

2.7.3.4.10. TSUH displays the past 12-qtr base period of usage data totaled for the

SGM. This screen displays the total SGM usage data used in the computation of

SIRS rates and percents, and includes file maintained data, if applicable. The two

screens also display the past installed program for OIM, PDM, EOH, and MISTR.

The left screen displays the latest eight qtrs (qtrs 1-8) of total usage history and

program. It also displays the “Quarter of Last Demand” from D035, which is the last

qtr a requisition was received for the item. The ES and IMS/MM use this data to

determine how active the item is. The right screen displays the oldest four qtrs (qtrs


9-12) of usage data. This is page 5 of the seven screens that show the data reflected

on the Factors/Usage Printout (see AFMCMAN 23-101, Volume 5, paragraph 1.3.3.).

2.7.3.4.11. UH displays the past 12-qtr base period of usage data, which includes

base RTS, base NRTS, base condemnations, base reparable generations, Dep Rep

Gens, MISTR repairs, MISTR condemnations, and total depot condemnations, by

current and SGM stock number. The UH screen has a left and right screen and

vertically scrolls between top and bottom. The left screen displays the latest eight

qtrs (qtrs 1-8) of usage history, and the right screen displays the oldest four qtrs (qtr

9-12) of usage data. The screen shows both the actual data received from interfacing

systems and data file maintained by the ES. This is page 4 of the seven screens that

show the data reflected on the Factors/Usage Printout (see AFMCMAN 23-101,

Volume 5, paragraph 1.3.2.).

2.7.3.5. The Index of Actions (IOA)(INDX) selection screen has 11 selections. The

screen allows the user to select the display of buy, termination, excess, and repair

quantities by various sites (or ALC), BP, SMC, MMAC, FSC, division, IMS/MM, and

ES sequences and summaries (see AFMCMAN 23-101, Volume 3, Chapter 6.).

2.7.3.6. The Miscellaneous (MISC) menu has three selections.

2.7.3.6.1. ISID displays the dates when each interfacing system file was received for

input to the SIRS database. The system OPRs primarily use this data (see

AFMCMAN 23-101, Volume 2, paragraph 5.1.1.).

2.7.3.6.2. Interface System Multiple Input Dates (ISIM) displays the dates when

interfacing system files were received for input to the SIRS database for the Initial,

Final, and Summary computations, if applicable. The system OPRs primarily use this

data.

2.7.3.6.3. The OSTD screen displays the comparison between the past RDE demands

provided by the Wholesale management Efficiency Reports System

(WMER)(D035B) and the RDE future requirements projected by the other Services.

The past 8 qtrs of data and 20 qtrs of future RDE requirements are displayed. The

Service (Army, Navy, Marines, or Other) must be selected to view the comparison

data (see AFMCMAN 23-101, Volume 4, paragraph 9.3.7.).

2.7.3.7. The PD PRELOG Data menu has three selections. Reference AFMCMAN 23-

101, Volume 5, Chapter 4.

2.7.3.7.1. PEL displays PRELOG error data. Data can be accessed by site ID; site

and division; or by site, division, and ES code (see AFMCMAN 23-101, Volume 5,

paragraph 4.7.).

2.7.3.7.2. PES displays summary PRELOG error data. Data can be accessed by site

ID, site and division, or by site, division and ES code (see AFMCMAN 23-101,

Volume 5, paragraph 4.8.).

2.7.3.7.3. PSI displays information about the SGMs that were selected for PRELOG

screening. Data can be accessed by site ID, division, or ES code (see AFMCMAN



2.7.3.8. Selecting PFI from the SIRS menu displays the IRL menu (reference

AFMCMAN 23-101, Volume 4, paragraph 12.2.). The IRL menu provides the

capability to select stock numbers that need to be reviewed by site, division, IMS code,

and ES code. The user must select “no computes,” terminations, buys, excesses, or

repairs. The screen will re-appear with the selected data and any informational messages

to identify possible discrepancies in the data elements.

2.7.3.9. Selecting Repair Products (RPR) from the SIRS menu displays data if there is a

JR item and the item has more serviceable assets than are currently required, and the

assets could be issued to the JR line to save money and time.

2.7.3.10. The Safety Level Table Data (SLTD) menu has six selections. The BSBS

BP/SMC/BSO table lists the BP and SMC combinations used by SIRS. The Mission

Design Goal/Floor Factor Table (MGFT) lists the aircraft target/goals. The IMS/MM and

ESs use these tables. The D200A OPRs use the other tables (see AFMCMAN 23-101,

Volume 2, Chapter 3, paragraph 3.2.1.).

2.7.3.10.1. BKBV BSO KEY/BSO Value Results Table looks like the file

maintenance BVRT table (see AFMCMAN 23-101, Volume 2, paragraph 3.5.) and

displays the Budget Support Objective (BSO) values and results that are used in the

AAM computation.

2.7.3.10.2. The BSBS BP/SMC/BSO Table looks like the file maintenance BSBT

table and displays all BPs and SMCs along with the BSO for each BP-SMC

combination. The BSBT table contains the additional field Start Comp (see


2.7.3.10.3. The BSMD BP/SMC/Pseudo MD screen looks like the file maintenance

BSMD screen (see Volume 2) and displays the BPs and SMCs along with a 7-

position alphanumeric value for the Mission Design (MD).

2.7.3.10.4. The BSTF BP/SMC Target Fill Rate Table looks like the file maintenance

BTRT table (reference AFMCMAN 23-101, Volume 2, paragraph 3.4.) and displays

the target fill rates for each BP-SMC combination.

2.7.3.10.5. The MAMD Aircraft Availability Model MDS/MD screen looks like the

file maintenance MAMD table (reference AFMCMAN 23-101, Volume 2, paragraph

3.7.) and displays data sorted by Mission Design Series (MDS), then by MD within

an MDS.

2.7.3.10.6. The MGFT looks like the file maintenance MGFT table (see AFMCMAN

23-101, Volume 2, paragraph 3.8.) and displays data used by the Aircraft Availability

computation.

2.7.3.11. The SND menu has 18 selections.

2.7.3.11.1. ADRQ Additive Requirements displays all time-phased additive

requirements that have been input for the CSN. The additives are listed two per page

until all applicable additives are displayed. The Forward key is used to scroll through

all of the additives that have been input for a selected stock number (see AFMCMAN



2.7.3.11.2. ALVW displays the time-phased adjusted levels by SRAN for all SRANs

with adjusted levels. It is used to identify all of the SRANs with adjusted levels or to

access a specific SRAN. The Forward key is used to scroll through all of the adjusted

levels (see AFMCMAN 23-101, Volume 4, paragraph 4.5.2.).

2.7.3.11.3. ARCR displays the A-R computational results of using data from the

previous screens. The ARCR is page 3 of the A-R series of display screens (see


2.7.3.11.4. ARD displays the past four qtrs of Asset Reconciliation data and provides

the total acquired and starting asset position. The ARD is page 1 of six screens that

display A-R data. The six screens of the Asset Reconciliation and their applicable

page numbers are: 1) ARD, 2) Asset Reconciliation Losses and Gains, (ARLG), 3)

ARCR, 4) Asset Reconciliation On-Order Assets (AROO) 5), Asset Reconciliation

Due-In (ARDI) Assets, and 6) Asset Reconciliation On-Hand (AROH) Assets. Any

of the six screens can be accessed from any of the other Asset Reconciliation screens

by pointing and clicking to the page numbers at the bottom of the screens (see


2.7.3.11.5. ARDI Assets displays the due-in asset quantities that were reported and

updated for the past four qtrs. The ARDI is page 5 of the Asset Reconciliation series

of display screens (see AFMCMAN 23-101, Volume 4, paragraph 7.8.).

2.7.3.11.6. ARLG displays the past four qtrs of asset gains and losses by individual

category. The ARLG is page 2 of the A-R series of display screens (see AFMCMAN


2.7.3.11.7. AROH Assets displays the on-hand asset quantities that were reported

and updated for the past four qtrs. Use the scroll feature to see additional lines of

data. The AROH is page 6 of the asset reconciliation series of display screens (see


2.7.3.11.8. AROO Assets displays the on-order quantities that were reported and

updated for the past four qtrs. The AROO is page 4 of the A-R series of display

screens (see AFMCMAN 23-101, Volume 4, paragraph 7.7.).

2.7.3.11.9. BMD displays the BMD assigned to an individual CSN. Data elements

are site code, IMS code, ES code, item name, ERRC, item PSC, budget code, SMC,

item category, comp code, safety level exclusion indicator, unit price, FUP, ICS/RIW

code and expiration date, Deferred Disposal Code (DDC) and level, weapon system

life code, Other War Reserve Materiel Exclusion (OWRM EXCL) indicator, FIC,

new item code, and lot size quantity (see AFMCMAN 23-101, Volume 4, Chapter

1).

2.7.3.11.10. The CARD screen displays the asset position, by category and “pick-off

point,” of the item by CSN. The screen contains five pages, which can be accessed

by pointing and clicking to the page numbers at the bottom of the screen. SCC X

assets are displayed on page 1 (see AFMCMAN 23-101, Volume 4, paragraph 6.11.)

The five pages of the CARD screen are: 1) Non time-phased assets for serviceable

and unserviceable assets, 2) Time-phased assets by pick-off points, 3) Total asset


quantities by pick-off points, 4) Total asset quantities at the buy point, and 5)

Obsolete CSNs.

2.7.3.11.11. IPD displays the past and future peacetime item installed programs and

future wartime item installed programs by application, type, and service. The data

can be accessed by all or individual applications, types, or Service codes (see


2.7.3.11.12. NTPD displays the serviceable, unserviceable, and Technical Order

Compliance (TOC) assets by individual asset category and CSN. Also, it provides

SCC X assets (see AFMCMAN 23-101, Volume 4, paragraph 6.7.).

2.7.3.11.13. PLD displays the pipeline days, and the lead times (administrative and

production) in both days and months. The pipeline days included are the base Order

and Shipping Time (O&ST) days, base repair cycle days, JR stock level days, Non-

Job-Routed (NJR) stock level days, and the five elements of the DRC days. The

time-phased DRC days, along with the time-phased effective date, are also displayed

(see AFMCMAN 23-101, Volume 4, Chapter 3).

2.7.3.11.14. RDEO to Other Services displays four qtrs of projected RDE recurring

and non-recurring demands, and unserviceable returns that have been forwarded to

another Service as the AF requirement (see AFMCMAN 23-101, Volume 4,

paragraph 9.2.).

2.7.3.11.15. The SNIC screen consists of two pages. Page 1 displays the site gains

and changes for stock numbers where the FSC, MMAC, AF Manager, or ERRC have

changed. Page 2 displays the losing data for items that have been replaced by or

consolidated with another stock number. Either page may be accessed by pointing

and clicking to the page numbers at the bottom of the screen (see AFMCMAN 23-

101, Volume 4, paragraph 12.4.2.).

2.7.3.11.16. TPAD displays the due-in and on-order assets, by category, by CSN,

that are used in the computation (see AFMCMAN 23-101, Volume 4, paragraph

6.10.).

2.7.3.11.17. TRND displays the past four qtrs of data element values that were

resident in the history files for the Summary computations, for the SGM, to indicate

trends over time. There are seven pages of trend data that can be accessed by

pointing and clicking to the page number at the bottom of the screen. The type of

trend data is available on the following pages: page 1 – BMD, page 2 – PLD, page 3

– computed requirements at the buy point, page 4 – assets used in the computation at

the buy point, page 5 – MISTR input requirements, page 6 – MISTR output

requirements and page 7 – factors (rates and percents) used in the computation (see

AFMCMAN 23-101, Volume 2, Chapter 6).

2.7.3.11.18. WARD displays the rates, percents, pipelines, and number of users

values that were used in the OWRM computation (see AFMCMAN 23-101, Volume

3).

2.7.3.12. The Table Data (TBLD) menu has 16 selections. The Inflation Index (INI)

table lists the inflation factors used to compute the FUPs. The OWRM table lists the


values used by the OWRM computation. The three standard data tables contain data used

as default values in the SIRS computation. The IMs and ESs use these tables. The OPRs

use the other tables (see AFMCMAN 23-101, Volume 2, Chapter 3).

2.8. File Maintenance Screens. From the File Maintenance Main menu, select the SIRS

“menu.” The SIRS File Maintenance menu has seven selections. The IMS/MM and ES will use

the SND selection to do most of their file maintenance (see paragraph 2.10.6).

2.8.1. The user must have a valid USERID and password to file maintain SIRS data. The

SIRS Functional OPR user profile allows access to all SIRS file maintenance screens,

including the only access to the Group Recomputation screen and to the Table Data (see

AFMCMAN 23-101, Volume 2, paragraph 2.10.). The site OPR and IMS/MMs’ user

profiles allow access to most SIRS file maintenance screens. The ES’s user profile allows

access to a few of the SIRS file maintenance screens. The ES also requires a USERID and

password that allows access to the API system’s AI and PRGM file maintenance screens.

The ES file maintains applications and program data (see AFMCMAN 23-101, Volume 5,

paragraphs 3.19., 3.20., and 3.26.). In SIRS, if the IMS/MM or ES can access a screen,

access is granted for any stock number. If file maintenance is done, the USERID for the

person will be recorded on the Notepad.

2.8.2. The SIRS file maintenance screens can only be accessed after the Initial computation

is done and before the Final computation has started, and after the Final computation is done

and before the Summary computation has started. When using GUI, spaces will not be input

in the numeric fields. Users will enter the number and SIRS will right justify it. If not using

GUI, file maintenance of numeric fields can be done three ways: fill the numeric field with

numbers; space over to the first column that requires a number and enter the number; or enter

the number in the first position and space out the rest of the field.

2.8.3. Notepad. The Notepad is not a word processor. For each data element, SIRS can

store 10 lines of 79 characters each. The user must use the Tab key to move from line to line.

Notepad text can be altered in several different ways. If the user chooses not to input text, a

confirmation message appears stating that the file maintenance action will be disregarded. If

text exists, the user can type over existing lines, add, or delete data. Text cannot be totally

blanked out if a file maintained value exists for this cycle. Only those lines with non-blank

text are retained on the database. The Notepad displays the old value (as of the last

computation) along with the SRC and the new value. SIRS will not accept file maintenance

without an explanation on a Notepad, for the data element. The documentation will remain

in SIRS until it is removed or changed during the current processing cycle. The Notepad

documentation is printed at the end of some products. After the Summary computation is

run, the documentation stays with the history file and cannot be changed.

2.8.3.1. There are three generic Notepads in SIRS. File maintenance is not required to

update them. They can be used for general information that will be noted for the item or

when an item level Notepad is not available. For example, the SIRS user may want to

explain why a record was deleted, or why an unusual actual data value was not changed.

Element level Notepads do not exist in these cases, and the generic Notepad can be used

in their place. The generic Notepads are located on the Factor Data screen (menu

selection SIRS FM SND FACD), on the Asset Reconciliation Data screen (menu

selection SIRS FM SND ARD), and on the SGM Comp Worksheet Rqmts screen (menu


selection SIRS FM CW). (Note: The generic Notepad is not available on the SIRS FM

CW screen for INS and NSO items.)

2.8.4. SMCW. Selecting the CW option, takes the user to page 1 of the SMCW file

maintenance screen (see AFMCMAN 23-101, Volume 3, paragraph 1.16.1.). The IMS/MM

can file maintain the FMS RQMT and FMS PR QTY. The IMS/MM will select “PUSH

RDE TO PICA” when they want to send revised Projected Recurring Demands to the

Primary Inventory Control Activity (PICA) from the March, June or December cycles (see


2.8.5. FRIR. OPRs, IMS/MMs, and ESs with valid SIRS file maintenance USERIDs and

passwords can initiate a computation on an individual item. This is done after data has been

file maintained in SIRS. Therefore, when the SIRS file maintenance screens are closed, a

“For Real” recomputation cannot be done. The “For Real” updates the computation results

that can be viewed online in the SIRS. This recomputation does not change data sent to

interfacing systems including CSIS. Only data resulting from a SIRS computation (Initial,

Final, and Summary) are used to update CSIS (see AFMCMAN 23-101, Volume 3,

paragraph 2.2.).

2.8.6. SND. The IMS/MM and ES use the file maintenance screens to file maintain SIRS

data. Using GUI, the user can point and click on the “drop down” boxes to select the desired

file maintenance screen. Without GUI, the command string must be entered in the CMD line

at the bottom left hand side of the screen. Note: The screen strings displayed below are the

commands to be used without the GUI capability. With GUI, the access sequence for the

“FM” and “SIRS” is reversed on the “drop down” boxes.

2.8.7. Table Data. The SIRS Functional OPR file maintains the table data used by SIRS (see

AFMCMAN 23-101, Volume 2, Chapter 3.)

2.8.8. What If Item Recomputation (WTIR). OPRs, IMS/MMs, and ESs with valid SIRS

file maintenance USERIDs and passwords can initiate a “simulation” computation on an

individual item. The “What If” is used to temporarily change data elements on the

simulation database and produce results that can only be seen on a hard copy product. The

“WTIR does not permanently change any SIRS data element, nor is the data used to update

CSIS. The “What If” can be run any time the database is available, and when the SIRS file

maintenance screens are closed. When an error is not corrected during the file maintenance

process prior to the SIRS Summary computation or when the user wants to see the impact of

a management decision on the item, the user can request a “What If” recomputation to

simulate the computational results with the corrected or projected data elements (see


2.9. Output Products Screens. Users must have valid USERIDs and passwords to obtain

output products from SIRS. Select OP from the RMS-FOE menu, then select SJR, then select

SIRS to get the Output Products Submit Job Request SIRS menu.

2.9.1. The AAM reports are selected from the SIRS Secondary Item Requirements Product

Selection screen. These reports are described in AFMCMAN 23-101, Volume 3, paragraphs

3.2.7. - 3.2.12. The SIRS Functional OPR uses these reports.

2.9.2. The ES Report (EPSS) screen allows the user to select the factors/usage printout, the

PRELOG Equations product, the PRELOG plots, the MISTR RPR and Repair Data product


or the SRAN Usage product by SGM, or by part number, or by site, division, and ES code

(see AFMCMAN 23-101, Volume 5, paragraph 5.4.).

2.9.3. The IPD product screen allows the user to select past peacetime, future peacetime, or

future wartime item installed programs. It is possible to limit the product by selecting an

application or a program type (see AFMCMAN 23-101, Volume 5, paragraph 3.5.1.).

2.9.4. The Input System Data (ISD) Product Selection screen allows an OPR to request ISD

reports for a site, one report at a time. These reports provide summary information about the

data received from interfacing system (see AFMCMAN 23-101, Volume 2, paragraph 4.4.).

2.9.5. The Major Command (MAJCOM) Usage reports selection screen allows an OPR to

request hard copies of the Spares Requirements Review Board (SRRB) MAJCOM usage data

that is reported via the Base Consumption Data Report Format (7SC transaction); reference

AFH 23-123, Volume 2, Part 1, Integrated Logistics System-Supply (ILS-S), Materiel

Management Operations. There are two types of products that can be printed: MAJCOM

usage history and MAJCOM breakout percentage (see AFMCMAN 23-101, Volume 5,

paragraph 1.14.).

2.9.6. The OPR Reports (OPSS) menu allows the OPR to select a product by SGM; site and

division; site, division and IMS code; or by site, division and ES code. The products are

SGM CW, SGM OWRM CW, A-R, Consolidated Assets, INS/NSO Item Status Listing,

Factors/Usage Printout, Adjusted Level Verification worksheet, SRAN Assets, SRAN Usage,

PRELOG Equations, PRELOG Plots, PRELOG Selected Information, and PRELOG Error

List and Summary (see AFMCMAN 23-101, Volume 2, paragraph 4.2.).

2.9.7. The IMS Reports screen allows the user to select any of the following products, by

SGM, or by site, division, and IMS code: Asset Reconciliation, SGM CW, SGM OWRM

CW, Consolidated Assets, Factors/Usage Printout, Adjusted Level Verification, MISTR RPR

and Repair Data, INS/NSO Status Listing, SRAN Assets and SRAN Usage Product (see


2.9.8. The Quality Control Checklist Selection screen allows the site SIRS OPR to get a list

of items with various conditions (i.e., all items coded INS). See AFMCMAN 23-101,

Volume 2, paragraph 4.3.

2.9.9. Changing the default printer: The users’ default printer can be changed in D200 at the

User Function Keys screen. This screen can be reached by selecting Main, UDV, FM,

UVFK from the RMS GUI software (FM UDV UVFK). Note: It is not recommended the

user change any of the user function keys on the screen. More information on how to print

can be found on the D200A web site.

2.10. Source Reference Codes. Many data elements in SIRS have an SRC. SRCs are system

generated and cannot be file maintained.


Chapter 3

QUALITY REVIEWS

3.1. General.

3.1.1. These procedures apply to personnel responsible for developing, adjusting and

reviewing SIRS requirements data. The site management will ensure adherence to these

procedures and take action as deemed necessary in response to the quality review team’s

reports and recommendations.

3.1.2. As part of an on-going process, the site SIRS quality review teams will:

3.1.2.1. After the summary, review the items comprising the top 10% of the total a) buy

dollar requirement and b) repair dollar requirement (POS plus RSP requirements) using

the highest dollar value in the CY + AY at each site starting with the largest dollar

requirements and working down the list before any budget submission. This review may

be conducted as part of the signature cycle.

3.1.2.2. Each cycle, the review team will conduct a quality review on the million dollar

terminations and the million dollar buys within 35 calendar days of the print date of the

Summary computation. Each budget cycle, the review team will conduct a quality

review on the million dollar repairs within 60 calendar days of the print date of the

Summary computation. Based on the IAC, the review team will conduct a quality review

on the million dollar Potential DoD Excess (from the CSIS Approved Force Acquisition

Objective and Retention Position line 21, sum of columns 3, 4 and 5) within 90 calendar

days of the print date of the Final/Summary computation. This review may be conducted

as part of the signature cycle.

3.1.2.3. Review a random selection of items twice a year at each site to include buy,

termination (including termination requests), excess (including the retention and disposal

decisions on excess assets), repair, DDCs, modification, demand forecast accuracy, one-

way interchangeable items and other items of interest such as items with

estimated/median factors. Items may be selected from the IOA listings, CSIS or ABCS.

3.1.2.4. Use the Quality Review Checklist, shown in Table 3.1 through Table 3.11 for

reviewing items and reporting errors.

3.1.2.5. Involve the item management team in the review process. When necessary,

personnel from other functions (e.g., engineering, contracting and manufacturing, etc.)

will be involved.

3.1.2.6. Report review findings in writing to first line supervisors.

3.1.2.7. Retain Review Checklist and management briefing for at least one year.

3.1.2.8. Take corrective action as appropriate.

3.1.2.9. Summarize review results and present to wing management; indicate error

trends, recurring errors, type (data element) errors, or any other error category that can be

used as a baseline for improving the effectiveness of the SIRS.

3.1.2.10. Refer SIRS and/or SIRS User Manual deficiencies to the AFMC SIRS OPR.


3.1.3. The IMS/MMs, ESs, and PMSs will:

3.1.3.1. Make available to the SIRS quality review team, on an item basis, all data

necessary for review, analysis, and evaluation. The documentation must contain a

detailed audit trail of all actions affecting an item’s position.

3.1.3.2. Upon request, participate in reviews.

3.1.3.3. Correct reported errors as soon as possible.

3.1.3.4. Comply with this manual regarding retention and retirement of documentation.

3.1.4. Sites are not required to use the checklists in this chapter to conduct reviews on PBL

contract items in which the contractor is required to perform all the demand and supply

planning for the items.

3.1.5. Each squadron responsible for working items in D200A will conduct internal reviews.

A review will be conducted on the items comprising the top 10% of the total:

3.1.5.1. Termination dollars for the items within their squadron starting with the largest

dollar value and working down the list prior to the computation asset cutoff date for

coding the terminations in ABCS after the Summary computation.

3.1.5.2. Buy dollar requirement (POS plus RSP requirements) for the items within their

squadron using the highest dollar value in the CY + AY, BY or EY starting with the

largest dollar requirements and working down the list prior to the beginning of the next

D200A quarterly cycle after the Summary computation on budget cycles.

3.1.5.3. Repair dollar requirement (POS plus RSP requirements) for the items within

their squadron using the highest dollar value in the CY, AY, BY or EY starting with the

largest dollar requirements and working down the list prior to the beginning of the next

D200A quarterly cycle after the Summary computation on budget cycles.

3.1.5.4. Excess dollars for the items within their squadron starting with the largest dollar

value and working down the list prior to the beginning of the next D200A quarterly cycle

after the Summary computation on non-budget cycles. This review may be conducted as

part of the signature cycle.


Table 3.1. IMS/MM/PMS Quality Review Checklist For Items with ERRC Code “T”.

NSN IMS/MM Computation

Cycle

Impacting Errors Non-Impacting

Errors

Reason

for

Review

Buy

Repair

Terminat

ion Other

ERRC Item Category Dollar Value Impact Recomputation

Required?

Element OK Error Nature of Error Comments/

Recommended

Corrective

Action

1. Budget Code A. BP does not reflect

the item ERRC code and

applications.

B. SMC does not reflect

applicable weapon

system(s) shown as

applications in the item

future programs.

2. Unit Price A. Latest price not

used.

B. Price is not

documented by AFMC

Form 318, or historical

AFMC Form 339, Due-

In Assets Status Record.

C. Estimated price is

not documented.

3. DOLP A. AFMC Form 318 or

339 does not verify

DOLP.

B. DOLP does not

match unit price

contract award date.

C. No documentation

for not using latest AF


4. ALT A. ALT does not come

from AFMC Form 318,

339 or PR and contract

and equal time from

initiation of latest PR to

contract award plus 7


calendar days.

B. No documentation

for using default or file

maintained data.

C. Did not use actual or

estimated.

D. Acquisition and

Due-In System (J018R)

code 65 awaiting funds

delay not deducted.

E. In error.

5. PLT A. Actual PLT did not

come from AFMC Form

318, 339 or contract and

equal time from contract

line item award to 10%

delivery. RIID adds 15

calendar days for items

that have not obtained

10% delivery.

B. No documentation

for using default or file

maintained data.

C. In error.

6. OWRM EXCL No documentation for

use of this code.

7. Safety Level

Exclusion

Indicator (SFTY

LVL EXCL

IND)

No documentation for

use of this code.

****N/A to

INS/NSO****

8. Item Category

Code (ICC)

A. Item has too many

demands to remain

NSO.

B. NSO code not

correctly used for low

demand item.

C. LOT code L

incorrect.

D. Demand pattern

indicates “I” incorrect.

Cataloging action not

submitted to change

AAC.

9. Activity Code Not representative of

item’s demands.


10. ICS/ RIW A. Not coded/correct in

D200A.

B. Not coded/correct in

ABCS.

11. ICS/RIW

EXPIR DATE

A. Not present with

ICS/RIW Indicator.

B. Not correct.

12. DDC/Level Documentation to

support IMS/MM-

assigned DDC F, G, M

or R inadequate or

missing.

13. O&ST Days No explanation for file

maintained data.

****N/A to

INS/NSO****

14. Overhaul Stock

Level Job-

Routed

(JR)/NJR

A. Blank.

B. No documentation

for using other than

defaults.

****N/A to

INS/NSO****

15. Base Repair

Cycle Days

Using other than actual

or default without

documentation. No

explanation for file

maintained data.

****N/A to

INS/NSO****

16. Base Processing

Days

No explanation for file

maintained data.

****N/A to

INS/NSO****

17. Reparable

Intransit Days

No explanation for file

maintained data.

****N/A to

INS/NSO****

18. Supply To

Maintenance

Days

Shop Flow Days

Serviceable

Turn-In Days

A. Supply to

Maintenance Days -

other than default value

without documentation.

B. Shop Flow Days

1) Weighted average

incorrect due to errors

contained in the Report -

MISTR Repair and


Repair Data:

a) Actual shop flow

days incorrect on

production number or

CLIN level.

b) Production incorrect.

2) Incorrectly used

default when actual data

available.

3) Did not use default

when no actual data was

available.

C. Serviceable Turn-in

Days - other than 1 day

used without

documentation.

****N/A to

INS/NSO****

19. Time -Phased

Days

DRC Effective

Date

When changing from

organic to contract or

vice versa, time-phased

DRC times/date were

not used.

****N/A to

INS/NSO****

20. URC/Latest

Repair Cost

(LRC)

A. Not correct for

CSIS/Customer Pricing/

Materiel Cost Recovery

(MCR) development

1) Weighted average

incorrect due to errors

contained in the Report -

MISTR Repair and

Repair Data:

a) Actual URC in error

on production number

or CLIN level.

b) Production incorrect.

2) Incorrectly used

default when actual data

available.

3) No justification for

using other than actual

or default.

B. Does not match

ABCS weighted price


due to file maintenance

difference between

D200A and ABCS.

21. On-Order Assets A. On-order quantities

do not concur with

AFMC Forms 339.

B. PR funded is not

correct.

C. PR unfunded is not

correct.

D. Inadequate

documentation of on-

order assets.

22. Due-In Assets A. In error IAW

supporting

documentation.

B. Not documented

properly.

23. On-Hand

Assets/Asset

Reconciliation

A. No documentation

for why reported assets

were adjusted.

B. Inadequate

documentation for

adjustments to starting

position.

C. Incorrect adjustment

to starting position.

D. Inadequate

documentation for

losses/gains.

E. Losses/gains

incorrect.

F. Condemnations on

Asset Reconciliation

Report do not match

Factor Printout and ES

has not removed any

condemnations not

caused by “fair/wear”.

H. Variance greater

than allowed without

research or correction.

I. Third consecutive

variance not taken or

taken without adequate

justification/research.


24. OIM/DLM

Program

A. First digit of PSC

not zero, but OIM

program missing.

B. Digits 2, 3 or 4 of

PSC not zero, but DLM

program missing.

25. Special Levels A. No

documentation/justificat

ion for IMS/MM file

maintained information.

B. Adjusted Level

Verification Worksheet

for the special level is

missing and/or

supporting documents

are missing (i.e.,

Adjusted Stock Level

Master Summary, AF

Form 1996, Adjusted

Stock Level).

26. WRM A. No documentation/

justification for

IMS/MM file


B.

Requirements/Execution

Availability Logistics

Module (REALM)

(D087H) Prime Item

Print to support RSP

requirement is missing.

27. Additives A. No documentation/

justification for

IMS/MM file


B. Additive is missing,

incorrect, or not in

compliance with policy.

C. Copy of annual

validation or supporting

documentation missing.

D. FMS H-coded

backorder additive in

error. Backorders not

documented or attached.

E. No documentation


when RDE requirements

do not match RDE

Generations.

F. I&S additive

requirement passed from

sub NSN:

1) Computation not

provided for review.

2) Errors in the sub

computation result in

additive error.

G. DOTM in error.

28. Number Of

Users/Time-

Phased Users

A. Number of users do

not match ISA screen.

B. There is no

documentation for any

variance.

C. Time-phased users

are missing or incorrect.

D. No Adjusted Level


for users greater than

ISA screen.

****N/A to

INS/NSO****

29. One-Way

Interchangeable

Item meets criteria in

paragraph 1.10.1. and

additives, special levels,

minimum depot stock

level and/or B21 have

not been zeroed.

30. Lot Size Lot size not 1. No

documentation for

change.

31. Computation

Other (applies

after Summary

computation is

run)

A. “What If”

recomputation required,

but is missing.

B. All corrections not

made during file

maintenance.

C. Manual corrections

incomplete/incorrect.

D. Change to factors on

recomputation not made

to OWRM computation.

32. Signatures and A. Signatures are not


Documentation

(applies after

Summary

computation is

run)

IAW Attachment 2.

B. Previous signature is

no longer valid. (Good

for 1 year if dollar

threshold is not

breached.)

C. For Terminations:

1) Termination code

and a narrative

explanation are not

annotated on the

computation.

2) No Termination

Model.

3) Decision not to

terminate on-order

assets is not adequately

justified.

D. For Unfunded PR/

MIPRs - Justification

for not

reducing/canceling or

note indicating date of

amendment to

reduce/cancel is not on

the computation.

E. For Excess Assets -

Retention/disposal

quantity with

appropriate coding is

not annotated on

computation. Disposal

document number is not

on the computation and

Asset Reconciliation

Report nor added to

Notepad on Asset

Reconciliation next

cycle. Have not been

coded in RDS.

For Repair – CY, AY,

BY, and/or EY repair

dollar not annotated on

computation.

33. Standard Buy

Format (applies

A. Is not filled out

completely.


after Summary

computation is

run)

B. Deferrals are not

scrubbed and /or not

documented.

C. With adequate file

maintenance, not in buy.

D. Mathematical error

in buy.

34. ABCS (applies

after Summary

computation is

run and ABCS

worked)

A. ABCS does not

match D200A Summary

or “What If”

recomputation.

B. ABCS changed

without documentation.

C. ABCS FUP is in

error.

Additional Comments

Reviewer

Office Symbol Date


Table 3.2. IMS/MM Quality Review Checklist For Items with ERRC “N” or “P”.


Cycle


Errors

Reason

for

Review

Buy

Repair

Termin

ation

Other

ERRC Item Category Dollar Value Impact Recomputation

Required?


Recommended

Corrective

Action

1. Budget Code A. BP does not reflect

the item ERRC code

and applications.

B. SMC does not

reflect applicable

weapon system(s)

shown as applications

in the item future

programs.

2. Unit Price A. Latest price not

used.

B. Price is not

documented by AFMC

Form 318 or 339.

C. Estimated price is

not documented.

3. DOLP A. AFMC Form 318

or 339 does not verify

DOLP.

B. DOLP does not

match unit price


C. No documentation

for not using latest AF


4. ALT A. ALT did not come

from AFMC Form

318, 339 or PR and

contract and equal

time from initiation of

latest PR to contract


award plus 7 calendar

days.

B. No documentation

for using default or

file maintained data.

C. Did not use actual

or estimated.

D. J018R code 65

awaiting funds delay

not deducted.

E. In error.

5. PLT A. Actual PLT did not

come from AFMC

Form 318, 339 or

contract and equal

time from contract line

item award to 10%

delivery. RIID adds

15 calendar days for

items that have not

obtained 10%

delivery.

B. No documentation

for using default or


C. In error.

6. OWRM EXCL No documentation for

use of this code.

7. SFTY LVL

EXCL IND

No Documentation for

use of this code.

***N/A to

INS/NSO***

8. ICC A. Item has too many

demands to remain

NSO.

B. NSO code not

correctly used for low

demand item.

C. LOT code L

incorrect.

D. Demand pattern

indicates “I” incorrect.

Cataloging action not

initiated to change

AAC.

9. Activity Code Not representative of


item’s demands.

10. ICS/RIW A. Not coded/correct

in D200A.

B. Not coded/correct

in ABCS.


support IMS/MM -

assigned DDCs of “F,”

“G,” “M” or “R”

inadequate or missing.

12. O&ST Days A. No explanation for


***N/A to

INS/NSO***

13. Overhaul Stock

Level JR/NJR

A. Blank.

B. No documentation

for using other than

defaults.

***N/A to

INS/NSO***

14. Base Repair

Cycle Days

A. Only applicable to

ERRC “P” NSNs.

B. Using other than

actual or default

without

documentation. No


maintained data.

***N/A to

INS/NSO***

15. On-Order

Assets

A. On-order

quantities do not

concur with AFMC

Forms 339.

B. PR funded not

correct.

C. PR unfunded is not

correct.

D. Inadequate

documentation of on-

order assets.

16. Due-In Assets A. In error IAW

supporting

documentation.

B. Not documented

properly.


17. On-Hand

Assets/Asset

Reconciliation

A. No documentation

for why reported

assets were adjusted.

B. Reparables not

sent to disposal or no

documentation for

retaining

unserviceable assets.

18. OIM/DLM

Program

A. First digit of PSC

not zero, but OIM

program missing.


PSC not zero, but

DLM program

missing.

19. Special Levels A. No documentation/

justification for

IMS/MM file

maintained

information.

B. Adjusted Level

Verification

Worksheet for the

special level is

missing and/or

supporting documents

are missing (i.e.,

Adjusted Stock Level

Master Summary, AF

Form 1996).

20. Prepositioned

Requirement

(RSP)

No documentation/

justification for

IMS/MM file

maintained

information.

21. Additives A. No documentation/

justification for

IMS/MM file

maintained

information.

B. Additive is

missing, incorrect, or

not in compliance with

policy.

C. Copy of annual


validation or

supporting

documentation

missing.

D. FMS H-coded

backorder additive in

error. Backorders not

documented or

attached.

E. Security Assistance

Management

Information System

(SAMIS)(W001) not

provided for backup.

F. I&S Additive

requirement passed

from sub NSN:

1) Computation not

provided for review.

2) Errors in the sub

computation result in

additive error.

G. Unauthorized

backorders used.

H. Backorders not

documented or

attached.

22. Number Of

Users/Time-

Phased Users

A. Number of users

do not match ISA

screen, or ISA data not

provided to verify.

B. There is no

documentation for any

variance.

C. Time-phased users

are missing or

incorrect.

D. No Adjusted Level

Verification

Worksheet for users

greater than ISA

screen.

****N/A to

INS/NSO****

23. One-Way

Interchangeable


paragraph 1.10.1.


and additives, special

levels and/or

minimum depot stock

level not zeroed.

24. Signatures and

Documentation

(applies after

Summary

computation is

run)

A. Signatures are not

IAW Attachment 2.

B. Previous signature

is no longer valid.

(Good for 1 year if

dollar threshold is not

breached.)

C. For Terminations -

1) Termination code

and a narrative

explanation are not

annotated on the

computation.

2) No Termination

Model.

3) Decision not to

terminate on-order

assets is not

adequately justified.

D. For Unfunded

PR/MIPRS -

Justification for not



amendment to


the computation.

E. For excess assets-

retention/disposal

quantity with

appropriate coding is

not annotated on the

computation.

Disposal document

number is not on

computation. Has not

been coded in RDS.

25. Standard Buy

Format (applies

after Summary

computation is

run)


completely.


scrubbed and/or not

documented.


C. With adequate file

maintenance, not in

buy.

D. Mathematical error

in buy.

26. ABCS (applies

after Summary

computation is

run and ABCS

worked)

A. ABCS does not

match D200A

Summary or “What If”

recomputation.

B. ABCS changed

without

documentation.

C. ABCS FUP is in

error.

27. Other (applies

after Summary

computation is

run)

A. Computes an

erroneous

Management of Items

Subject To Repair

(MISTR) requirement

for consumable item.

B. What If

recomputation is

required, but is

missing.

C. Manual corrections

incomplete/incorrect.

Additional Comments

Reviewer Office Symbol Date


Table 3.3. AF Secondary Inventory Control Activity (SICA) Nonconsumable Item

Materiel Support Code (NIMSC) 5 Checklist.


Cycle


Errors

Reason

for

Review

Buy

Repair

Termina

tion

Other

ERRC Item

Category

Dollar Value Impact Recomputation

Required?


Recommended

Corrective

Action

1. Budget Code A. Does not have budget

code NIM5.

B. AF SICA, but

NIMSC is not 5. Item

must not have NIM5 in

the budget code.

2. Unit Price D043 price not used and

backup documentation

missing.

3. DOLP Julian date is not 00000.

4. SFTY LVL

EXCL IND

No documentation for

use of this code.

**N/A to INS/NSO**

5. Number Of

Users/ Time-

phased Users

A. Number of users does

not match on ISA screen

and there is no

documentation for the

variance.

B. Time-phased users

are missing or incorrect.

C. No Adjusted Level


for users greater than ISA

screen.

**N/A to INS/NSO**

6. Activity Code A. Code does not meet

usage/dollar criteria.

B. Code does not ensure

that item will be

reviewed as a minimum


in the September cycle.


support IMS/MM-

assigned DDC F, G, M or

R inadequate or missing.

8. O&ST Days A. Actual exceeds

default by more than 10

calendar days without

documentation.

B. No explanation for


9. Overhaul Stock

Level JR/NJR

Days

JR values are not zero or

NJR missing. (AF depot

repair is not authorized

for AF SICA NIMSC 5

items.)

10. Base Repair

Cycle Days

A. Actual exceeds

default by more than 10

calendar days without

documentation.

B. Using other than

actual or default without

documentation. No


maintained data.

C. Days are not zero for

100% NRTS items.

11. Assets A. Asset reconciliation

NOT required.

B. Disposition

instructions needed for

assets in computation.

12. OIM/DLM

Program

A. First digit of PSC not

zero, but OIM program

missing.


PSC not zero, but DLM

program missing.

13. Special Levels A. No

documentation/justificati

on for IMS/MM file


B. Adjusted Level


for the special levels is

missing and/or


supporting documents are

missing (i.e., Special

Level Master Summary,

AF Form 1996).

14. WRM A. No documentation/

justification for IMS/MM

file maintained

information.

B. D087H product to

support computation RSP

requirement is missing.

15. Additive

Requirements

A. No documentation/

justification for IMS/MM

file maintained

information.

B. Additive is missing or

incorrect.

C. Copy of annual

validation missing.

16. One-Way

Interchangeable


paragraph 1.10.1. and

additives, special levels,

and/or minimum depot

stock level not zeroed.

17. Signatures and

Documentation

(applies after

Summary

computation is

run)

A. Signatures are not

IAW Attachment 2.

B. Previous signature is

not still valid. (Good for

1 year if dollar threshold

of next signature level

not breached.)

C. For Terminations -

1) Termination code

and a narrative

explanation are not

annotated on the

computation.

2) No Termination

Model.

D. For Unfunded

PR/MIPRS - Justification

for not



amendment to



computation.

E. For Excess -

Retention/disposal

quantity with appropriate

coding is not annotated

on computation. (Has

request for disposition

instructions been sent to

the PICA for the excess

assets? Will not dispose

of items on which AF is

SICA without written

direction or concurrence

from the PICA.)

Disposal document

number is not annotated

on the computation.

18. Standard Buy

Format (applies

after Summary

computation is

run)


completely.


scrubbed and/or

documented.

19. ABCS (applies

after Summary

computation is

run and ABCS

is worked)

A. ABCS in error.

B. ABCS does not match

computation.

20. Computation

(applies after

Summary

computation is

run)

A. A re-computation is

needed, but there is not

one.

B. A “What If” re-

computation was used on

Sep cycle after the

summary computation,

but no documentation

that PICA notified to

amend RDE List.

Additional Comments

Reviewer Office Symbol Date


Table 3.4. Factors and Usage Quality Review Checklist For Items with ERRC “T”.

NSN ES Computatio

n Cycle

Non-Impacting

Errors

Impacting

Errors

FIC ERRC RTS

Exclusion

ECS/RIW Item Category


Recommended

Corrective

Action

1. Item PSC Not compatible with

usage.

2. Application Data

A. Application

1) Application is

missing.

2) Erroneous

applications present.

B. PGM SEL 1) Active program

missing from PSC.

2) Erroneous PSC

used.

3) No OIM program

when OIM usage

reported.

4) No DLM program

requested, yet DLM

usage reported.

C. PGM DEV Field is other than

blank and not

documented.

D. Program Begin

Date

1) Application is

time- phased and

skips qtrs where

application data is

changing.

2) Program begin

date is too old; NSN

or subs not cataloged

at that time.

3) Is less than 2

years back and usage

has reported in qtr

prior to the begin

date.

E. QPA QPA records not

compatible with rest

of application data.


F. Application

Percent

1) Application

percent is incorrect.

2) Application

percent is not zero

and item meets

criteria in paragraph

1.10.1.

G. Documentation Inadequate

documentation/

justification.

3. Usage

A. Base RTS

1) File maintained

usage is inaccurate or

not adequately

documented.

2) File maintenance

actions inconsistent

from qtr-to-qtr.

3) Other.

B. Base NRTS 1) File maintained

usage inaccurate or

not adequately

documented.

2) File maintenance


from qtr-to-qtr.

3) Other.

C. Base

Condemnations

1) Condemnations(s)

are sporadic and have

not been moved to

base NRTS, MISTR

condemnations and

total depot

condemnations.

2) Condemnation(s)

are of non-recurring

nature and have not

been removed.

3) File maintenance

changes not

adequately

documented.

4) Other.

D. Dep Rep Gens 1) No DLM program

identified in PSC.

2) PDM

replacements for


cause have not been

moved to base NRTS.

3) File maintained

usage inaccurate or

not adequately

documented.

4) File maintenance


from qtr-to-qtr.

5) Other.

E. MISTR Repair 1) File maintained

usage inaccurate or

not adequately

documented at

production number or

CLIN level.

2) File maintenance


from qtr-to-qtr.

3) Other.

F. MISTR

Condemnations

1) File maintained

usage inaccurate or

not adequately

documented.

2) File maintenance


from qtr-to-qtr.

3) Other.

G. Depot

Condemnation

Total

1) Less than MISTR

condemnations.

2) Item is NJR DLM

only and total

condemnation

(CNDM) not equal to

MISTR CNDM.

3) File maintained

usage inaccurate or

not adequately

documented.

4) File maintenance


from qtr-to-qtr.

5) Other.

4. OIM Factors

A. Total OIM

Demand Rate

1) Trend in demand

rate is more than

normal, but was


considered/used.

2) Current rate not

reflective of current

usage.

3) Estimated rates

are considerably

higher or lower than

computed rates, are

not based on any

segment of recent

past history, and are

straight-lined rather

than time-phased.

4) File maintained

usage was not

considered in

estimated rates.

5) Estimates not

adequately

documented.

6) Other.

B. NRTS Percent 1) Does not match

time frame used for

total OIM demand

rate.

2) Equal to zero,

change of ERRC

code not considered/

documented.

3) File maintained

usage was not

considered in

estimated rates.

4) Estimates not

adequately

documented.

C. Base

Condemnation

Percent

1) Not reflective of

actual usage; not file

maintained IAW

AFMCMAN 23-101,

Volume 5, paragraph

2.26.

2) File maintained

usage was not

considered in

estimated rates.


3) Estimates not

adequately

documented.

D. Base RTS

Exclusion

1) Used but not

documented.

2) Used erroneously

in lieu of research

into erroneous

reporting.

5. MISTR

Condemnation

Percent

A. 100%

condemnation with

no forecasted lower

rate on recoverable

item without change

of ERRC

documentation

provided.

B. Estimates not

adequately

documented.

C. Estimate

considerably higher

than past history,

indicating possible

item replacement

without approved

Improved Item

Replacement

Program (IIRP) or

modification.

D. Other.

6. DLM Factors

A. PDM

1) JR

Condemnation

Percent

2) NJR

Replacement

Percent

3) NJR Program

Percent

a) Invalid split of JR

and NJR for a single

SOR.

b) Trend in depot

usage is more than

nominal, but was not

considered/used.

c) Estimated rates

are considerably


computed rates, are

not based on any

segment of recent




than time-phased.

d) File maintained

usage was not

considered in

estimated rates.

e) Estimated rates

are not adequately

documented.

f) Rate over 100%

not documented.

B. Engine

Overhaul (EOH)

1) JR

Condemnation

Percent

2) NJR

Replacement

Percent

3) NJR Program

Percent


and NJR.

b) Trend in depot

usage is more than

nominal, but was not

considered/used.

c) Estimated rates

are considerably


computed rates, are

not based on any

segment of recent



than time-phased.

d) File maintained

usage was not

considered in

estimated rates.

e) Estimated rates

are not adequately

documented.

f) Rate over 100%

not documented.

C. Nest Higher

Assembly (NHA)

MISTR

1) JR

Condemnation

Percent

2) NJR

Replacement

Percent

3) NJR Program

Percent


and NJR for single

SOR.

b) Trend in depot

usage was not

considered.

c) Estimated rates

are considerably


computed rates, are

not based on any

segment of recent




than time-phased.

d) File maintained

usage was not

considered in

estimated rates.

e) Estimated rates

are not adequately

documented.

f) Rate over 100%

not documented.

7. FIC A. Does the FIC

indicate the

consideration of

usage trends, e.g., 4

qtrs vs. 8 qtrs? (N)

for No.

B. Documentation is

incorrect/incomplete.

8. Signature A. Printout has not

been signed/dated by

the ES.

B. ES has not

signed/dated the

computation,

recomputation,

INS/NSO Item Status

Listing for an item

computing buy or

repair in CY, AY, BY

or EY or termination

or excess.

ADDITIONAL COMMENTS

REVIEWER DATE


Table 3.5. Factors and Usage Quality Review Checklist For Items with ERRC “N” or “P”.

NSN ES Computatio

n Cycle

Non-Impacting

Errors

Impacting Errors

FIC ERRC RTS

Exclusion

ECS/RIW Item Category


Recommended

Corrective Action

1. Item PSC Not compatible

with usage.

2. Application Data

A. Application

1) Application is

missing.

2) Erroneous

applications

present.

B. PGM SEL 1) Active program

missing from PSC.

2) Erroneous PSC

used.

3) No OIM

program when

OIM usage

reported.

4) No DLM

program requested,

yet DLM usage

reported.

C. PGM DEV Field is other than

blank not

documented.

D. Program Begin

Date

1) Application is

time-phased and

skips qtrs where

application data is

changing.

2) Program begin

date is too old,

NSN or subs not

cataloged at that

time.

3) Is less than 2

years back and

usage has reported

in the qtr prior to

the begin date.

E. QPA QPA records not


compatible with

rest of application

data.

F. Application

Percent

1) Application

Percent is

incorrect.

2) Application

Percent is not zero

and item meets

criteria in

paragraph 1.10.1.

G. Documentation Inadequate

documentation/

justification.

3. Usage

A. Base RTS

1) RTS on ERRC

“N” not removed.

2) File

maintenance

actions

inconsistent from

qtr-to-qtr.

B. Base NRTS NRTS left in

consumable item

usage history. No

NRTS authorized

for ERRC “N” or

“P.”

C. Base

Condemnations

File maintenance

changes not

adequately

documented.

D. Dep Rep Gens 1) Do not match

JR condemnations.

2) Erroneous NJR

replacements not

removed.

E. Depot

Condemnation

(Note: by NSN)

1) Not equal to

Dep Rep Gens.

2) File maintained

usage inaccurate or

not adequately

documented.

3) File

maintenance

actions

inconsistent from


qtr-to-qtr.

F. MISTR Repair Erroneous

reporting not

researched or

corrected.

No MISTR repairs

allowed for ERRC

“N” or “P.”

G. MISTR

Condemnations

Erroneous

reporting not

researched or

corrected.

H. Depot

Condemnation

Total

Not equal to Dep

Rep Gens.

I. FIC 1) Does the FIC

show the

consideration of

usage data trends

(e.g., 4 qtrs vs. 8

qtrs)?

2) Documentation

is incorrect/

incomplete.

4. OIM Factors

A. Total OIM

Demand Rate

1) Trend in

demand rate is

more than normal,

but was

considered/used/

documented.

2) Current rate not

reflective of

current usage.

3) Estimated rates

are considerably

higher or lower

than computed

rates, are not based

on any segment of

recent past history,

and are straight-

lined rather than

time-phased.

4) File maintained

usage was not

considered in


estimated rates.

5) Estimates not

adequately

documented.

B. NRTS Percent Other than zero,

not corrected by

ES (correct usage

or change ERRC

code).

C. Base

Condemnation

Percent

1) Not reflective

of actual.

2) File maintained

usage was not

considered in

estimated rates.

3) Estimates not

adequately

documented.

4) Other than

100%

condemnations for

ERRC “N.”

5) Higher than

100% without

justification.

6) File

maintenance

actions

inconsistent from

qtr-to-0qtr.

D. Base RTS

Exclusion

Used for ERRC

code “N” & “P.”

5. MISTR

Condemnation

Percent

1) Other than

100% (ERRC code

“N”).

2) Other than

100% without

justification

(ERRC code “P”).

6. DLM Factors

A. PDM

1) JR

Condemnation

Percent

2) NJR

Replacement

a) NJR program

or replacement

percent other than

zero.

b) Trend in depot

usage is more than

nominal, but was


Percent

3) NJR Program

Percent

not

considered/used.

c) Estimated rates

are considerably

higher or lower

than computed


on any segment of


and are straight-

lined rather than

time-phased.

d) File maintained

usage was not

considered in

estimated rates.

e) Estimated rates

are not adequately

documented.

f) Rate over 100%

not documented.

g) Inadequate

documentation

(N).

h) Other.

B. EOH

1) JR

Condemnation

Percent

2) NJR

Replacement

Percent

3) NJR Program

Percent

a) NJR program

or replacement

percent other than

zero.

b) Trend in depot

usage is more than

nominal, but was

not

considered/used.

c) Estimated rates

are considerably

higher or lower

than computed


on any segment of


and are straight-

lined rather than

time-phased.

d) File maintained

usage was not


considered in

estimated rates.

e) Estimated rates

are not adequately

documented.

f) Rate over 100%

not documented

(without

justification).

g) Inadequate

documentation

(N).

h) Other.

C. NHA MISTR

JR

1) NJR program

or replacement

percent other than

zero.

2) Trend in depot

usage is more than

nominal, but was

not

considered/used.

3) Estimated rates

are considerably

higher or lower

than computed


on any segment of


and are straight-

lined rather than

time-phased.

4) File maintained

usage was not

considered in

estimated rates.

5) Estimated rates

are not adequately

documented.

6) Rate over

100% not

documented.

7) Inadequate

documentation

(N).

8) Other.


7. FIC A. Does the FIC

indicate the

consideration of

usage trends, e.g.,

4 qtrs vs. 8 qtrs?

(N)

B. Documentation

is

incorrect/incomple

te.

8. Signature A. Printout has

not been

signed/dated by

the ES.

B. ES has not

signed/dated the

computation,

recomputation,

INS/NSO Item

Status Listing for

an item computing

buy in CY, AY,

BY or EY or

termination or

excess.

ADDITIONAL COMMENTS

REVIEWER DATE


Table 3.6. Repair Quality Checklist.

SGM NSN IMS/MM Site AFMC

Impacting Impacting

Non-Impacting Non-Impacting

URC: PMS: ES:

Element Site

OK

HQ

OK

Nature of Error Comment/ Recommended

Corrective Action

1. PMS Code A. If organic repair, no

buyer PMS code

assigned.

B. If contract repair, no

seller/buyer PMS code

assigned.

C. If dual

organic/contract, both

buyer/seller PMS not

assigned.

2. SOR/PCN A. Product Control

Number (PCN) not

assigned to current

SOR.

B. SOR on ABCS.B21

which is not doing

repair of item.

C. D200A, Depot

Maintenance

Consolidated

Operational Database

System (Q302)

Contractor Visibility

List do not all agree.

3. Repair Cost A. URC incorrect

weighted improperly or

in error.

B. URC changed but no

documentation.

C. URC is > 75% of

FUP without

justification.

D. Does not agree with

ABCS.

E. Does not agree with

Factors Printout.

F. Does not agree with


Q302/Commercial Asset

Visibility System Air

Force (CAV

AF).

4. ABCS URC

SOR 1 ____%

SOR 2 ____%

SOR 3 ____%

SOR 4 ____%

A. URC incorrect.

B. URC changed but no

documentation.

C. URC is 75% of FUP

without justification.

D. If unweighted, does

not agree with D200A.

E. If unweighted, does

not agree with Factors

Printout.

F. Does not agree with

Q302/CAV AF.

5. Family

Stratified

Repair

Requirement -

Input

A. Changes not per re-

computation or other

supporting

documentation.

B. Changes not

documented on MISTR

lines of computation.

C. Wrong/no

adjustment reason code

for change.

D. Does not agree with

ABCS.

E. Error in calculating

lump sum adjustment

6. Family

Stratified

Repair

Requirement -

Output

A. Changes not per re-

computation or other

supporting

documentation.

B. Changes not

documented on MISTR

lines of computation.

C. Errors on

computation/ Factors

Printout caused

erroneous requirement.

D. Changes not on a

“one-for-one” basis with

input.

E. Error in calculating

lump sum adjustment.


7. Family Repair

Update - Input

A. Not updated with

contract/ICS update

sheet or other

documentation.

B. Not accurately

manually updated.

C. AFMC Form 804,

Renegotiation And

Drive Adjustment

Record, not documented

or processed.

D. Current negotiation

changed, not justified.

E. Contract carryover in

error/missing.

8. Family Repair

Update -

Output

A. Not updated with

contract/ICS update

sheet or other

documentation.

B. Not accurately

manually updated.

C. Current negotiation

changed, not justified.

D. AFMC Form 206

repairs will be used in

updating.

9. Budget

Documentation

Signatures

A. AY budget not

documented on

computation.

B. AY budget

documentation

incorrect.

C. Repair included in

both column C & I.

D. Not signed by

IMS/MM.

10. Lump Sum

Adjustment

A. Delayed discrepancy

(YBQ or YBG)

backorder requisition

number not documented

on the ABCS B21.

B. H-Coded backorder

requisition number

received after

computation asset cutoff

not documented/error on


the ABCS B21

computation.

C. Contingency vs. buy

RSP requirement not

documented or in error

on the ABCS B21

computation.

D. Exceeds total

available for repair.

E. Reason for re-

computation not

documented.

F. On Work Order

(OWO)/ Due In From

Overhaul (DIOH)

adjustment incorrect/not

made.

G. Adjustment reason

code missing or in error.

H. RDE adjustment in

error/not made on B21.

11. Over/Under

Induction

A. Over-induction used

in ABCS not authorized.

B. Under-induction

used in ABCS not

authorized.

C. Over/under-

induction should have

been in ABCS.

12. Impact to

Supply

Maintenance

Budget

Authority

(SMBA)

Budget

A. Over-budgeted.

B. Under-budgeted.

13. Possible

Impact to

(Depot

Maintenance

Budget

Authority)

DMBA

A. Over-budgeted.

B. Under-budgeted.

14. Using

EXPRESS

Not accurately

displaying EXecution

and Prioritization of


REpair Support System

(EXPRESS)

requirement.

15. Signatures A. No

IMS/MM/supervisor

signature/title on B21.

B. No PMS signature

on B21.

Additional Comments


Table 3.7. Termination Review Checklist.

SGM NSN NOUN COMP DATE

Original Quantity For Review Original Dollars for Review Correct

Quantity

Correct

Dollars

ES IMS/MM Repeat Termination

Yes No

Element Correct

or N/A

Reason For Error

and Remarks (Circle

letter if error and/or

write comments.)

HQ Comments

1. Termination Status A. With accurate file

maintenance, item

would not have been

in termination.

2. Termination Processing A. Not worked within

10 calendar days of

print of computation.

B. Failure to work

termination.

3. Signatures A. Not obtained IAW

Attachment 2.

B. Not signed by

appropriate level.

4. Termination Model A. Not used when

applicable.

B. Used incorrectly.

C. Recommendations

not followed.

D. Not completed

within 10 calendar

days of print of

computation.

E. Termination costs

input when there was

no written

documentation from

PK.

5. Termination Coding A. Termination code

not assigned.

B. Code incorrect.

C. Back-up

documentation doesn’t

substantiate

termination code.


D. Management

decision code

shouldn’t have been

used.

6. PR Cancellation/Reduction A. Not initiated.

B. Not submitted to

PK within 10 calendar

days of print of

computation.

C. Excessive delays

from PK, not followed

- up by IMS/MM.

7. Termination Log A. Termination Log

not maintained.

B. Weekly follow-up

not accomplished

8. Termination Requests A. Not initiated.

B. Follow-ups not

being done weekly

(See Table 4.2.).

Comments

Reviewer Date


Table 3.8. MISTR Repair and Repair Data Checklist. Note. Does not apply to AF/SICA

NIMSC 5 items.

SGM NSN Computat

ion Cycle

Non-impacting Errors Impacting Errors

Noun PMS

Buyer

PMS Seller ES: IMS/ MM:

D200A Weighted Values

Repair Cost Shop Flow SVC Turn In

Element Site

OK

HQ

OK

Nature of Error Comment or

Recommended

Corrective Action

1. SOR Percent A. SOR percent not

against record(s)

indicative of future.

B. Iterative List not

considered.

C. Minor/major repair

not considered.

D. Dual repair not

considered.

E. SOR percent on

“T” (Temporary Job

Request) number with

MISTR and/or contract

record.

F. Inadequate or

missing documentation.

G. Other (see

comments).

2. Repair Cost A. Valid price is not

against record with

SOR percent.

B. Iterative List not

considered.

C. Price not indicative

of future.

D. Organic price not

IAW upcoming FY

CSAG-Maintenance

(CSAG-M)

spreadsheet.

E. Dual repair not

considered.

F. Management fees


(e.g., data) not

considered for contract

repair where applicable

and/or not spread

across all items.

G. Minor/major repair

not considered.

H. Contract/DMISA

does not substantiate

cost used.

I. Inadequate or

missing documentation.

J. Other (see

comments).

3. Repair History A. Repair history

contains invalid repair

data (i.e., inspection,

packaging condition

check, FMS, etc.).

B. Production does not

match G004L/I and or

Temporary job (T-job)

list and no

documentation.

C. Contractor

production reports do

not support repair

history on MRPR.

D. Documentation not

adequate or missing.

E. Other (see

comments).

4. Shop Flow A. Valid Shop Flow

Days not against record

with SOR percent.

B. Not indicative of

future.

C. File maintained and

no documentation to

support.

D. Contract/DMISA

does not support days

used.

E. Major/minor repair

not considered.

F. Documentation not



G. Other (see

comments).

5. Service Turn-In

(SVC T-I)

Valid data not against

record with SOR

percent.

6. SOR A. SOR not indicative

of future.

B. Time phased data

was not furnished to the

IM/MM.

C. Documentation not


D. Other (see

comments).

7. Contract

Condemnations

A. Condemnations (by

qtr) not annotated on

MRPR.

B. Condemnations do

not match contractor

reports.

C. Other (see

comments).

Additional Comments


Table 3.9. AFMC Review Summary.

NSN Computation Cycle

IMS/M

M

ES PMS Buy Repair Terminat

ion

Excess

1. IMS/MM

Submitted Buy

Budget

AY$ BY$ EY$

2. AFMC Validated

Buy Budget

AY$ BY$ EY$

3. Buy Budget

Difference

AY$ BY$ EY$

4. IMS/MM

Submitted Repair

Budget

AY$ BY$ EY$

5. AFMC Validated

Repair Budget

AY$ BY$ EY$

6. Repair Budget

Difference

AY$ BY$ EY$

7. IMS/MM

Submitted

Termination

$ IMS/MM

Submitted Excess

$

8. AFMC Validated

Termination

$ AFMC Validated

Excess

$

9. Difference Term $ Difference excess $

Comments/Recommendations

Name Office Symbol Date


Table 3.10. Depot Review Team Summary.

NSN Computation Cycle

IMS/M

M

ES PMS Buy Repair Terminat

ion

Excess

1. IMS/MM

Submitted Buy

Budget

AY$ BY$ EY$

2. Site Validated

Buy Budget

AY$ BY$ EY$

3. Buy Budget

Difference

AY$ BY$ EY$

4. IMS/MM

Submitted Repair

Budget

AY$ BY$ EY$

5. Site Validated

Repair Budget

AY$ BY$ EY$

6. Repair Budget

Difference

AY$ BY$ EY$

7. IMS/MM

Submitted

Termination

$ IMS/MM

Submitted Excess

$

8. Site Validated

Termination

$ Site Validated

Excess

$

9. Difference

Termination

$ Difference Excess $

Comments/Recommendations

Name Office Symbol Date


Table 3.11. Review Package.

REVIEW PACKAGE

DOCUMENTATION REQUIREMENTS REVIEW

NSN IMS/MM

Folders prepared for the Budget Requirement Review must contain all documentation

necessary to support the recommended action. As a minimum, the following documents

must be included (if applicable) in the review folder. Attach this cover sheet to each folder

and indicate which documents are included by marking the form with an “X.”

Documentation Enclosed Not Applicable

1. Summary D200A computation

2. What if recomputation

3. Consolidated Assets and Requirements

(include initial for consumable items)

4. All AFMC Forms 318 or copies of all

historical AFMC Forms 339 and other

documentation to support assets, ALT, PLT,

and unit prices

5. Historical AFMC Form 339 for any due-in

assets

6. Asset reconciliations (2 years)

7. SRAN Assets and Usage Reports

8. D087H products for RSP and HPMSK

9. Adjusted Level Verification Worksheet

10. D035E Special Levels Master Summary

11. RDE backup

12. Copies of justification for all additives (such

as):

A. End of qtr backorder listing

B. CLSSA listing

C. FMS retention listing

13. MISTR IM Projected Workload Report

(G004L.-23) as of computation asset cutoff

dates in Sep and Dec

14. Reportable Asset Management Process

(RAMP) products that validate pipelines

15. B21 (PMS copy with negotiated QTY)

16. Backup for out-year URC changes in ABCS

17. Summary MISTR Repair and Repair Data

18. Summary Factor Printout (include sub items if

usage moved)

19. All documentation to support ES file

maintenance and estimated rates

20. Budget Item Detail (S01) for buys, excess,


terminations

21. INS/NSO Item Status Listing

22. Documentation for DDCs (except C and P) and

levels

23. ABCS item interrogation buys and

terminations

24. Print of D043 summary screen

25. Print of BMD screen for INS/NSO items


Chapter 4

TERMINATION ACTIONS

4.1. Introduction. Mission changes or adjustment to item requirements sometimes reduce or

eliminate the need to commit funds for or accept delivery of spare parts that the AF has already

ordered. Consequently, these quantities must be considered for reduction and, if necessary,

contract termination. The decision to reduce or terminate a quantity on contract is not automatic;

it involves evaluation of economic and mission related factors. This is because termination often

involves a considerable cost to the government to compensate vendors for resources they have

committed to the contract. In many cases it is more advantageous for the government to accept

delivery of the assets rather than pay termination costs. This chapter provides IMS/MMs, PMSs,

Program Offices, RCOs, requirements analysts, site SIRS termination analysts, budget analysts,

AFMC, and site SIRS analysts with the procedures and tools to make a decision to terminate a

contract or to accept delivery of on-order assets.

4.1.1. Items considered for reduction or termination actions are items on production

contracts; items on PRs/MIPRs, but not yet on firm contract; TOC kit spare parts; and

acquisitions from other government agencies.

4.1.2. Items excluded from consideration for reduction or termination are complete aircraft

and missile engines; items on AFMC Form 326, Provisioned Item Order, that are being

processed to establish, confirm, or change contractor interim release actions; and items

ordered to support provisioning integrated with production, unless the items will become

obsolete. Interim release is authorization given a contractor to release support items to

production or procurement simultaneously with production requirements for like items prior

to submission of a PIO.

4.2. Overview.

4.2.1. Every computation cycle, the IMS/MM will review and work all their items

computing in termination starting their review with the highest termination dollar valued

items and work down the IRL in IRIS list of NSNs for review in order of importance. This

requirement ensures that efforts to avoid unnecessary costs to the government focus on items

with the highest termination value most likely to provide the largest recovery of dollars if

terminated first. Lower value termination quantities, more likely to be found uneconomical

to terminate by the termination model, are reviewed next.

4.2.2. The IMS/MM will review all PR quantities for AF spares not yet on contract,

regardless of dollar value at the beginning of the Initial computation cycle. The IMS/MM

will initiate an amendment to the PR to reduce those quantities if they would put the item in

termination if they were included in the requirements computation. Note: An item can have

a termination quantity and have items on PR and items on contract. The IMS/MM will

reduce the PR first and then initiate termination on the contract quantities

4.2.3. Terminations are time sensitive. Delay of even a single day can significantly increase

the cost to terminate. Therefore, management efforts must emphasize early identification of

potential excess on-order quantities. The Initial requirements computation cycle is the

logical starting point to review items with on-order quantities that may exceed AF needs and


is the first opportunity to recover or avoid spending limited procurement funds. The

IMS/MM must respond to and take action on any changes in AF missions, programmed

objectives, consumption factors, authorizations, etc., that reduce requirements.

Consideration for termination action begins as soon as the IMS/MM becomes aware of

information that may make on-order quantities excess to immediate needs. The IMS/MM

will not wait until the item computes in the next quarterly cycle. This chapter and the

Federal Acquisition Regulation (FAR), Part 49, Termination of Contracts, provides policy

guidance to affect timely termination actions. The term “termination” will be used to refer to

termination actions and to PR reduction and cancellation actions except when the policy or

procedures apply exclusively to PR reductions.

4.2.4. The IMS/MM determines if termination action is to be taken. The IMS/MM who

decides not to terminate will prepare documentation to certify and explain the reasons for

accepting the assets. The documentation will include a statement of facts, considerations,

sources of information, and the logic used to arrive at the decision. The originating activity

keeps the documentation for AFMC and inspection agency review. The following

circumstances will be considered when deciding to terminate, defer a termination decision, or

accept delivery of on-order assets that compute into termination:

4.2.4.1. Technical complexity that may require costly reprocurement.

4.2.4.2. Increasing operating programs or escalating condemnation rates not already

included in the requirements computation that would necessitate a buy in the foreseeable

future.

4.2.4.3. Known increases to FMS requirements. These quantities will be integrated into

the SIRS computation to account for the requirements if they were not already included

in the feed to D200A. (Note: The Arms Export Act prohibits inclusion of non-

programmed FMS requirements in the D200A computation for which the FMS customer

has not established an FMS FMS01 case level or Materiel Repair Requirements List

(MRRL).)

4.2.4.4. New applications that were not considered in the most recent SIRS computation.

These would justify deferral of a termination decision until a later cycle when the new

applications would be integrated into the computation.

4.2.4.5. Projected increases or decreases in demands in the near future that are not yet

reflected in the SIRS computation. These would justify deferral of a termination decision

until a later cycle when the demand projection would be integrated into the computation.

4.2.4.6. Items with a short shelf-life.

4.2.4.7. Items that apply to recently fielded systems and still use estimated demand rates.

This would authorize deferral of a termination decision until a later cycle when the

demand projection is based on mature rates.

4.2.4.8. The termination model concludes that termination is not in the best interests of

the government.

4.2.4.9. Any of the following factors are grounds for termination without regard to

economic considerations:


4.2.4.9.1. The item has declining programs and no reprocurement predicted in the

SIRS computation (i.e., no third short position through the retention period).

4.2.4.9.2. The item has declining programs and no projected condemnations.

4.2.4.9.3. An engineering change proposal or modification enhances the item’s

reliability or availability.

4.2.4.9.4. The item and/or its NHA is, or will soon be, obsolete.

4.2.4.9.5. The item’s mandatory removal time recently increased or was eliminated.

4.2.4.9.6. The contractor was unable to perform, default termination is possible, and

another source is preferred.

4.2.4.9.7. Organic manufacturing or repair capability is preferred.

4.2.4.9.8. Interchangeable items have been found in the AF inventory that were not

linked in D200A. This may result in an adjustment to the computation that would

reflect the availability of these assets.

4.2.4.9.9. This item is available from other Service/Agencies (S/A) or through DLA

Disposition Services.

4.3. Procedures.

4.3.1. When the ES reviews the summary ES Review Listing from the previous cycle before

the initial cycle they must focus first on items that have compute code “R” (“no-compute”

items) with on-order quantities. The ES will add values to the critical element(s) in D200F to

ensure the system produces a computation worksheet in the Initial computation (see

AFMCMAN 23-101, Volume 4, paragraph 1.14.3. and subparagraphs). The ES file

maintenance period in D200F is open almost continuously except when snapshots are being

made. The ES Review Listing (see AFMCMAN 23-101, Volume 5, paragraph 5.2.) is

displayed on the SIRS DIS.

4.3.1.1. When reviewing the initial IMS/MM Review Listing on the initial cycle, the

IMS/MM will focus first on items that have compute code “B,” “P,” (“no compute”

items) with on-order quantities. The IMS/MM will add values to the critical elements

after the initial cycle to ensure the system produces a computation worksheet on the Final

computation (see AFMCMAN 23-101, Volume 4, paragraph 1.14.3. and subparagraphs).

The IMS Review Listing (see AFMCMAN 23-101, Volume 4, paragraph 12.2.) is

displayed on the SIRS DIS PFI.

4.3.2. The IMS/MM must review the IOA from the Initial computation and determine if any

of the “no compute” items fell into termination. The IMS Review Listing and the ES Review

Listing display items in termination, which are also displayed on the IRL IMS/ES Review

List screen (SIRS DIS PFI IRL). The IMS/MM will determine if the item has a DLM

program (“X” in position “2,” “3,” or “4” of the item PSC), has Dep Rep Gens, or has depot

condemnations that exceed MISTR condemnations.

4.3.3. If the item does not have a DLM program, the IMS/MM will notify the ES that the

item is in termination and enter corrections online. The ES enters any corrections and

notifies the IM after review and corrections are complete. The IMS/MM requests an item

recomputation. “For Real” recomputation, reference AFMCMAN 23-101, Volume 3,


Chapter 2. If the item is still in termination the IMS/MM advises the contracting activity that

an amendment may be forthcoming to reduce or cancel the PR quantity and requests the

delay of contract award until after the Summary SIRS computation when a definite

termination quantity will be known.

4.3.4. If the item has a NHA MISTR program (“X” in the fourth position of the item PSC),

the IMS/MM will advise the item ES and the IMS/MMs and ESs responsible for each NHA

that the item is in termination.

4.3.4.1. If the NHA is a secondary item managed in SIRS, the IMS/MM and NHA

IMS/MMs will review the SGM Computation Worksheets or the INS/NSO Item Status

Listings from the Initial SIRS computation to ensure that the repair projection is correct.

The ES and NHA ESs will review the Factors/Usage Printouts to ensure the data is

correct.

4.3.4.2. If the NHA is a primary item managed in the D200C system, the NHA IMS/MM

and ES will verify the NHA overhaul program and the inventory data.

4.3.4.3. If the Initial computation data is not correct, the IMS/MM, NHA IMS/MMs, ES,

and NHA ESs will correct the elements for which they have responsibility during the

Initial computation review cycle. After the NHA IMS/MMs, ESs and NHA ESs have

reviewed their items and made corrections, they will notify the component IMS/MM.

The IMS/MM requests an item recomputation. “For Real” recomputation, reference

AFMCMAN 23-101, Volume 3, Chapter 2. If the item is still in termination, the

IMS/MM advises the contracting activity that an amendment may be forthcoming to

reduce or cancel the PR quantity and that contract award needs to be delayed until after

the Summary SIRS computation when a definite termination quantity will be known.

4.3.5. Immediately after receiving the IOA from the Final SIRS computation, the IMS/MM

will review the listing for any items that are in termination. The IMS/MM will review the

SGM Computation Worksheet or the INS/NSO Item Status Listing from the Final

computation to ensure that the data is correct. If the data is not correct, the IMS/MM and ES

will correct the erroneous data and request an item recomputation (“For Real”

recomputation). If the item is still in termination, the IMS/MM will advise the contracting

activity that an amendment may be forthcoming to reduce or cancel the PR quantity and that

contract award should be delayed until after the Summary SIRS computation when a definite

termination quantity will be known.

4.3.5.1. If the on-order excess quantity is not yet on contract, the IMS/MM initiates an

amendment to reduce or cancel the PR.

4.3.5.2. If the on-order excess quantity is on a firm contract, the IMS/MM will run the

termination model. If the termination model recommends termination, the IMS/MM

must submit a Termination Authority Template or fully justify the decision not to

terminate and obtain management approval for not initiating action to terminate the

computed termination quantity.

4.3.5.2.1. The purpose of the Termination Authority Template is to provide an

auditable record of the request of the initiating organization to terminate on-order

asset quantities and the contracting activity’s response to that request. See the Air

Force Federal Acquisition Supplement (AFFARS) 5349.102 for a tailorable


Termination Authority Template. Also reference AFMC Contracting Mandatory

Procedure (MP) Part 5349 for additional acquisition requirements.

4.3.5.2.2. Within 10 calendar days after the SGM Computation Worksheet or the

INS/NSO Item Status Listing from the Final computation print date, the IMS/MM

will ensure that the computation, INS/NSO Item Status Listing, Factors/Usage

Printout and MISTR Repair and Repair Data are correct, run the termination model,

make the decision of whether or not to reduce/cancel PRs or submit contract

termination/reduction requests to Contracting, sign their product and submit any PR

amendment to reduce/cancel PR and/or contract termination/reduction request to

Contracting. If the decision and PR amendment or Termination Authority Template

(if appropriate) cannot be completed within 10 calendar days, the IMS/MM must

explain why on the final SGM Requirements Worksheet or the INS/NSO Item Status

Listing and on the general Notepad for the item.

4.3.6. IMS/MMs will follow these steps when deciding to terminate or reduce on-order

quantities:

4.3.6.1. Validate all data elements in the SIRS computation that could affect the

termination quantity. If erroneous data caused a termination, make corrections during the

Initial computation cycle or request a “What If” recomputation after the Summary

computation. Analyze the quantity that remains in termination to determine the causes of

termination.

4.3.6.2. Determine if some or all of the on-order quantity was delivered after the asset

cutoff date. If so, decrease the on-order quantity and increase the on hand assets during

the Initial computation cycle or request a “What If” recomputation after the summary

computation.

4.3.6.3. If a contract quantity was terminated, but the computation still includes on-order

assets, the IMS/MM will remove them from the SIRS computation.

4.3.6.3.1. The IMS/MM will research the item to determine if the quantity was in

termination during a prior cycle and what action was taken. If termination action is in

progress, reduce or remove the on-order quantity. The IMS/MM will annotate the

Notepad and the SGM Computation Worksheet or the INS/NSO Item Status Listing

to indicate the reduction. Also, the IMS/MM will ensure that the total acquired and

the starting position on the Asset Reconciliation screen (see AFMCMAN 23-101,

Volume 4, Chapter 7) have been reduced to reflect the anticipated termination. If a

Termination Authority Template was sent to the contracting activity and the

termination was determined to be uneconomical, the IMS/MM will document this in

the Notepad before the end of file maintenance for the Summary computation cycle

and on the SGM Computation Worksheet or INS/NSO Item Status Listing.

4.3.6.3.2. If a decision was made not to terminate during a previous cycle, the

IMS/MM will research the item to determine if the justification is still valid. If so,

the IMS/MM will annotate the Notepad before the end of file maintenance for the

Summary computation cycle and the SGM Computation Worksheet or INS/NSO Item

Status Listing with the date and computation cycle of the previous decision.


4.3.6.4. Run the termination model if termination is appropriate (see paragraph 4.3.14).

If the model indicates that termination is uneconomical, annotate the SGM Computation

Worksheet or INS/NSO Item Status Listing accordingly and cite the termination model.

If the termination model recommends termination, a Termination Authority Template

will be submitted to the Contracting officer with an attached copy of the termination

model. A copy of the model PDF file will be retained for 2 years or until after the

termination is completed, whichever is longer. The SGM Computation Worksheet or the

INS/NSO Item Status Listing used as a basis for the termination model will be retained

for the same period.

4.3.6.5. Initiate termination action if obsolete items are involved or if a “no cost”

termination settlement can be obtained. To facilitate processing, the IMS/MM will

indicate the reason delivery is not desired on the Termination Authority Template.

4.3.6.6. Request termination without regard to termination costs and without consulting

the termination model if the factors listed in paragraph 4.2.4.9. are present. In such

cases, a Termination Authority Template will be sent to the procuring office with the

reason annotated (e.g., “declining program”) and request termination regardless of cost.

4.3.6.7. Utilizing the same logic, take immediate action to cancel or reduce on-order PR

quantities for these quantities. An item could have a termination quantity and have items

on PR and items on contract. The PR will be reduced first and then termination initiated

on the contract quantities.

4.3.7. Under exceptional circumstances, it may not be in the best interest of the government

to terminate some quantities of items with declining programs. In these cases, the group

commander (or equivalent) has the authority to deviate from the above guidance. The

documentation must include a copy of the termination model and clear, auditable evidence

from an engineering activity or program office that the assets will have a specific need after

delivery. The purpose of this requirement is to allow for the use of good judgment in

exceptional situations and to prevent actions that could waste public funds. If feasible, the

SIRS computation will be adjusted to display the future need.

4.3.8. In some cases, a Procurement Contracting Officer (PCO) or a Termination

Contracting Officer may receive a Termination Authority Template and determine that

termination costs are significantly higher than first estimated. In such cases, the IMS/MM

will conduct an economic re-evaluation upon request from the Contracting Officer.

4.3.9. Any quantities for which termination action has been requested via a Termination

Authority Template will be removed from the Initial SIRS computation. This action will be

taken as soon as the Termination Authority Template has been submitted and before the

Summary computation. Partial termination quantities from the on-order assets at the end of

the projected delivery schedule will be removed. Also, the IMS/MM will ensure that the

total acquired and the starting position on the Asset Reconciliation screen (see AFMCMAN

23-101, Volume 4, Chapter 7) have been reduced to reflect the anticipated termination.

4.3.10. If the contracting officer returns the Termination Authority Template without action

after the IMS/MM has taken the above actions, the IMS/MM must reinstate the assets in the

computation and make corresponding adjustments to the Asset Reconciliation Worksheet.


These actions must be clearly annotated on the AFMC Form 318. The Termination

Authority Template will be kept available for audit or inspection.

4.3.11. If an amendment was initiated to reduce or cancel a PR quantity, the assets will be

removed from SIRS. Also, the IMS/MM will ensure that the total acquired and the starting

position on the Asset Reconciliation screen (see AFMCMAN 23-101, Volume 4, Chapter 7)

have been reduced to reflect the anticipated termination. If termination quantities were

delivered after the current cycle computation asset cutoff date, the on-order quantities will be

removed and the assets shown as on hand.

4.3.12. The on-order quantity will be removed during the Initial computation cycle if assets

are diverted to other uses in lieu of termination. The asset reconciliation will require

correction. The documentation will be attached to the SGM Computation Worksheet or

INS/NSO Item Status Listing substantiating the diversion and identifying the customer.

4.3.13. Items that compute termination quantities and their stock listed NHAs must be

worked each cycle.

4.3.14. The termination model must be used on all terminations except:

4.3.14.1. When information in the SIRS computation is adjusted or corrected in a way

that eliminates the termination quantity.

4.3.14.2. When a termination decision is deferred pending research because of suspect

data in SIRS, HQ AFMC/A4RM directive, expected new applications, or an anticipated

program increase that is not yet reflected in the latest USAF program authority document.

4.4. Reporting and Analysis.

4.4.1. ABCS – Terminations (ABCS Terms) is a tool to evaluate on-order excess items.

IM/MMs, RCOs, division analysts, site SIRS termination analysts, and budget analysts will

perform the following procedures:

4.4.1.1. The IMS/MM determines the appropriate 2-digit ABCS termination code(s) to

assign to each item that computes a termination quantity in the Summary computation.

The termination code(s) will be annotated on the SGM Computation

Worksheet/computation signature coversheet or on the INS/NSO Item Status Listing

from the Summary computation or the latest “What If” recomputation.

4.4.1.1.1. The termination code will also be annotated on the ABCS – Uncoded

Terms List product distributed to the IMS/MM. More than one code can apply to an

item, in which case, each code will be broken down by quantity.

4.4.1.1.2. For terminations with a value of $1 million or more, the RCO or division

analyst requests an ABCS – Terminations On-Order Excess Format 4 Report for each

termination with a value of $1 million or more and passes it to the IMS/MM. The

IMS/MM adds a narrative that explains the reasons the item computed into

termination and the termination decision for every termination with code “04,” “05,”

“06,” “11,” and “12.” See Table 4.1 for code definitions.

4.4.1.2. RCOs or division analysts will verify termination codes reflect the situation.

They will also enter the codes into ABCS – Terminations. Site personnel will code

ABCS – Terminations every cycle. RCOs or division analysts will also provide


IMS/MMs with Format 4 reports for all items over $1 million for the addition of a

narrative. Annotated copies of item level Format 4 reports with codes “04,” “05,” “06,”

“11,” and “12” will be forwarded to the site SIRS termination analysts.

4.4.1.3. Site SIRS termination analysts or budget analysts are responsible for providing

narratives by BP and SMCs (see AFMCMAN 23-101, Volume 4, paragraph 1.2.) at each

site when directed by AFSC/LGPS. These reports, including item level reports, will be

forwarded to the SIRS Functional OPR. Site SIRS termination analysts and budget

analysts will maintain the proper SMCs on items placed in the FM (pseudo code) division

account within ABCS.

4.4.2. The termination quantity in ABCS is from the CSIS that is updated from the Summary

SIRS computation and includes terminations and “no compute” items with on-order assets.

Termination quantities stratify as On-Order Contract assets (Column 7) in Potential DoD

Excess (Line 21) in the Budget Item Detail Approved Acquisition Objective (AAO) position.

4.4.3. If the code indicates that a reduction or termination action has been or will be taken

(code “02” or “03”), the RIR log number (paragraph 4.4.6) will be noted in the

documentation.

4.4.4. Termination Codes. Table 4.1 lists the termination codes and the definitions explain

the reason for making a termination decision. Use of several codes per item is allowed. As a

minimum, all non-termination decisions except for termination codes 02, 03, and 13 must be

signed by both the IMS/MM and supervisor. Assistance in coding terminations that are not

covered by the following codes, contact the SIRS Termination OPR.


Table 4.1. Termination Codes.

Code Explanation

02 Contract Eligible for Termination: A quantity on contract is eligible for

termination action, the termination model has been run, and a Termination

Authority Template has been submitted. The item appears in ABCS because the

on-order quantity could not be adjusted before the Summary computation. The

AFSC will supplement this manual to designate signature level approval

requirements for the SGM Computation Worksheet, the “What If”

recomputation, or the INS/NSO Item Status Listing. Delinquent contracts that

can be terminated for default - all assets on contract are in termination will be

included. See code “17” for contracts that must be terminated for the

convenience of the government.

03 PR Eligible for Reduction or Cancellation: PR quantity is eligible for reduction

or cancellation, the termination model has been run, and a PR amendment has

been submitted. The item appears in ABCS because the on-order quantity could

not be adjusted before the Summary computation. The AFSC will supplement

this manual to designate signature level approval requirements for the SGM

Computation Worksheet, the “What If” recomputation, or the INS/NSO Item

Status Listing.

04 Will Not Terminate Due to AFSC/LGPS Direction: Item is not eligible for

reduction or termination action.

1. Attach a copy of the AFSC/LGPS direction to the SGM Computation

Worksheet, the INS/NSO Item Status Listing from the Summary computation, or

the latest “What If” recomputation. The AFSC will supplement this manual to

designate signature level policy approval requirements for the SGM

Computation Worksheet, the “What If” recomputation, or the INS/NSO Item

Status Listing. Repeat terminations require same signature level on budget

cycles.

2. This code also applies to consumable items for which the effective date of

transfer to DLA falls within a computation cycle--between the RIID snapshot

and the running of the Summary computation if the termination model results

say to terminate or cancel.

3. This code will be used for items on PBL contracts on which the contractor is

doing all the demand and supply planning for the items.

4. This code also applies to items for which the effective date of transfer to

another S/A falls within a computation cycle -- between the RIID snapshot and

the running of the Summary computation if the termination model results are not

uneconomical to terminate.

05 Will Not Terminate – Provisioning Integrated with Production: Termination

model has been run. (If the termination model determined it was uneconomical

to terminate, use codes 08, 09, or 10 as applicable). The Program Office-

approved production of spare parts to be concurrent with production of parts to

support production of the end item. Although this may result in production of

spare parts that exceed the requirement projected through the apportionment

year, there is a considerable price advantage for doing this. The IMS/MM and

supervisor will sign the SGM Computation Worksheet, the INS/NSO Item


Status Listing from the Summary computation, or the latest “What If”

recomputation. Repeat terminations require same signature level on budget

cycles.

06 Will Not Terminate, Additional Application Anticipated: Termination action

will not be taken because additional applications not reflected in the most recent

SIRS computation will be added. This code allows a termination decision to be

deferred for one cycle. Group-level approval is required on the SGM

Computation Worksheet, the INS/NSO Item Status Listing from the Summary

computation, or the latest “What If” recomputation.

07 Data Error Adjustments: Item does not require reduction or termination when

data is corrected. Corrections in the Summary SIRS computation could not be

done during the file maintenance cycle. If the data were not corrected before the

Summary SIRS computation and code 07 was entered after the summary CSIS,

code 07 remains in ABCS to explain on-order excess quantities in the CSIS. An

explanation of the error must be annotated on the SGM Computation Worksheet,

the INS/NSO Item Status Listing from the Summary computation, or the latest

“What If” recomputation. The IMS/MM must run a recomputation to show the

item is no longer in termination when the data is corrected. The IMS/MM and

supervisor signature is required for use of this code.

08 Termination Uneconomical – Reprocurement Anticipated: The termination

model has been run, termination was found to be uneconomical, and

reprocurement is anticipated. The SIRS computation displays a third short

quantity between termination point and the retention period. The AFSC will

supplement this manual to designate signature level approval requirements for

the SGM Computation Worksheet, the INS/ NSO Item Status Listing from the

Summary computation, or the latest “What If” recomputation and dollar

threshold for authorizing a decision not to terminate. Repeat terminations

require same signature level on budget cycles. The termination model is run on

repeat terminations every cycle.

09 Termination Uneconomical – No Reprocurement Anticipated: Termination

model has been run and it found termination to be uneconomical. No

reprocurement is anticipated (i.e., the SIRS computation displays a third over

quantity in at least one of the 38 future qtrs). The AFSC will supplement this

manual to designate signature level approval requirements for the SGM

Computation Worksheet, the INS/ NSO Item Status Listing from the Summary

computation, or the latest “What If” recomputation and dollar thresholds for

authorizing non-termination decision. Repeat terminations require same

signature level on budget cycles. The termination model is run on repeat

terminations every cycle.

10 Termination Uneconomical – Initial Provisioning Funding Used: The

termination model was run, termination was found to be uneconomical, and

initial provisioning funds were used to procure assets. The AFSC will

Supplement this manual to designate signature level approval requirements for

the SGM Computation Worksheet, the INS/NSO Item Status Listing from the

Summary computation, or the latest “What If” recomputation and dollar

threshold for authorizing non-termination decision. Repeat terminations require


same signature level on budget cycle. The termination model is run on repeat


11 Will Not Terminate, Data Suspect Pending Research: Use when the Summary

computation could not be adjusted. Limited to the following data elements:

programs, RSP, or contractor data. This code allows a termination decision to

be deferred for one cycle. Group-level approval is required on the SGM

Computation Worksheet, the INS/NSO Item Status Listing from the Summary

computation, or the latest “What If” recomputation.

12 Other, Will Not Terminate: This code is used when a decision not to terminate

does not fall under termination codes 02 - 11 or 13 - 15. The termination model

has been run. The decision not to reduce or terminate an item must be explained

and justified. The explanation must include the recommendation of the

termination model and why the recommendation should not be followed.

Group-level approval is required on the SGM Computation Worksheet, the

INS/NSO Item Status Listing from the Summary computation, or the latest

“What If” recomputation. The AFSC/CC will approve decisions not to

terminate actions with a value greater $1,000,000. Repeat terminations require

review and approval at the same signature level as the initial termination.

13 Computation–CSIS Variance: This code is used when (1) the Summary SIRS

computation does not compute a termination, but the CSIS displays a

termination quantity in the Budget Item Detail (S01), AAO position, column 7,

line 21, or (2) the quantity in the S01, AAO position, column 7, line 21 is larger

than the computed termination quantity in SIRS. The quantity and dollar

amount from the CSIS will be included under this code. The IMS/MM must

sign the SGM Computation Worksheet, the INS/NSO Item Status Listing from

the Summary computation or the latest “What If” recomputation. The IMS/MM

must also attach a copy of the CSIS S01 or a print screen of the AFAO and

retention position, Line 21 from the CSIS that shows the difference.

14 Economic Order, Will Not Terminate: This code is used for purchases on which

contractor will only bid on a minimum quantity or on which the contractor bid a

quantity discount price and for which the purchase was approved at squadron

level or higher (see paragraph 1.11.5.). The termination model was run and it

recommended termination. If the termination model recommended “do not

terminate,” termination codes 08, 09, or 10 will be used. The squadron-level

signature is required for use of this code. Repeat terminations require same

signature level on budget cycle. Termination model is run on repeat


15 Variable Safety Level Change on Summary: This code is used when the

variable safety level is different on the Summary computation than it was on the

Initial computation and the fluctuation in variable safety level put the item into

termination on the Summary computation. When annotating the ABCS

Uncoded Terminations List, the quantity and dollar value attributable to this will

be indicated on the product. The AFSC will supplement this manual to establish

signature level approval requirements for the SGM Computation Worksheet, the

INS/NSO Item Status Listing from the Summary computation, or the latest

“What If” recomputation.


16 Delivered After Asset Cutoff Date: This code includes contract deliveries that

occur after the computation asset cutoff date. The IMS/MM was not aware of

the delivery until after the Summary computation processed. The IMS/MM

must run a recomputation showing the item is no longer in termination when the

data is corrected. The IMS/MM and supervisor signature is required for use of

this code.

17 Delinquent Contract Eligible for Termination: This code is used when the

delinquent contract cannot be terminated for default. A quantity on contract is

eligible for termination action and the termination model has been run; however,

the computed termination quantity is less than the total quantity on contract.

Therefore, the contract cannot be terminated for default and has to be terminated

for the convenience of the government. Procurement cannot legally terminate a

delinquent contract for the convenience of the government. Procurement has to

extend the delinquent contract first prior to terminating it. Therefore, in cases

where the IMS/MM wants to terminate a delinquent contract for the convenience

of the government, the IMS/MM must first request in writing for procurement to

do an amendment to the contract extending the delivery schedule on the contract

before submitting the Termination Authority Template. The AFSC will

supplement this manual to designate signature level approval requirements for

the SGM Computation Worksheet, the “What If” recomputation, or the

INS/NSO Item Status Listing.

18 Not Term - Approved IIRP Spares: Termination model has been run. (If the

termination model determined it was uneconomical to terminate, use code “08,”

code “09,” or code “10” as applicable). The spares were approved as part of the

IIRP package. Although this may result in production of spare parts that exceed

the requirement projected through the budget year, there is a considerable price

advantage for doing this. Use AFMCMAN 23-101 for signature level

requirements for signing, but as a minimum, the IMS/MM, RCO and supervisor

will sign the SGM Computation Worksheet, the INS/NSO Item Status Listing

from the Summary computation, or the latest “What If” recomputation. Repeat

terminations require same signature level on budget cycles.

49 Unit Cost Change. This code is used when the unit price was not corrected prior

to the end of the file maintenance cycle.

4.4.5. Repeat terminations. The date, code, and computation cycle on which the decision

was made not to terminate will be annotated. With the exception of code 12, it is not

necessary to resubmit documentation as long as the conditions, code, quantity, and dollar

value do not change. Code 12 requires full documentation every cycle.

4.4.6. Electronic Termination (RIR) Log. Each site will maintain an electronic termination

log and will assign a termination monitor in the SCMG to oversee RIR log number

assignment and review the status weekly of each termination. The supervisor of the

termination monitor will periodically check to ensure the items were worked and/or proper

follow-up action was taken by looking at a sample of the items.

4.4.6.1. The log will have separate fields for the items listed in Table 4.2


Table 4.2. Required Electronic Termination (RIR) Log Fields.

Item RIR Log Fields

1 RIR log number

2 NSN

3 Contract number

4 CLIN

5 Computation cycle (on which termination is based, i.e., Sep 13)

6 The print date of the requirements computation or INS/NSO Item Status Listing

7 Termination quantity

8 Termination value

9 Date the RIR number is issued

10 MDC or other manager identification.

11 Date termination request was submitted to Contracting

12 Date Contracting received the termination request

13 Date of each weekly follow-up conversation with Contracting by the termination

monitor (until closed)

14 Synopsis of each weekly follow-up conversation with Contracting by the termination

monitor including POC (until closed)

15 Date of review of the RIR log by the supervisor of the termination monitor

16 Date termination action is completed by the contracting activity

17 The date the contracting activity determined termination to be uneconomical, if

applicable. This information is annotated on the returned Termination Authority

Template.

18 For contracts actually terminated by the contractor, termination cost.

19 For contracts actually terminated by the contractor, settlement cost.

20 For contract actually terminated by the contractor, cost savings to Government.

4.4.6.2. The RIR log number includes the FSC, FY, and a numeric sequence number

(i.e., RIR-1560-13-001). The IMS/MM annotates the RIR number in the remarks block

of the Termination Authority Template.

4.4.7. Procedures for assets acquired as follow-on spares. If the computed termination

quantity meets the criteria in paragraph 4.2.4.9 and/or the termination model recommends

termination, the IMS/MM will initiate RIR action within one working day and send the

Termination Authority Template to the contracting activity. Electronic transmission via E-

mail is highly encouraged. This RIR is sufficient to initiate termination action.

4.4.8. Procedures for assets acquired as initial spares. The IMS/MM reviews the IOA, the

IRD computation, the SIRS computation, and all other pertinent documents to validate the

termination quantity. Then the IMS/MM runs the termination model to determine if

termination is economical. If so, the IMS/MM initiates the RIR and annotates the RIR

number on AFMC Form 326 within one working day. The RIR is forwarded to the

provisioning activity at the End Article Item Manager’s (EAIM) or Program Office’s site.

The EAIM or Program Office notifies the Administrative Contracting Officer (ACO) of the

RIR via electronic means within one working day of receipt, providing information copies to


the Provisioning Procurement Contracting Officer (PPCO) and PCO. The confirming AFMC

Form 326 will be sent to the PPCO as soon as possible. The IMS/MM will pull the adjusted

asset quantity from J018R to indicate completion of termination.

4.4.9. Procedures for termination and reduction of contract repair workload. The IMS/MM

will hold a joint contract review with the PMS to determine necessary action. The IMS/MM

and the PMS will mutually agree on the termination decision. The PMS prepares the

Termination Authority Template or the PR or MIPR amendment. If workload acquired

through a MIPR is to be terminated or reduced, use the Termination Authority Template to

initiate RIR action with a confirming MIPR amendment.

4.4.10. Procedure for termination and reduction of quantities acquired to support FMS

customers. “FMS Case Termination” will be annotated in the remarks section of the RIR.

FMS termination costs will be reported to AFSC/LGPS.

4.5. The SIRS Termination Model.

4.5.1. The SIRS termination model is an online tool to help the IMS/MM determine if

termination of a specific item is economically feasible and to make a decision to proceed

with a termination action. The recommendation is a recommendation only and extenuating

circumstances may justify another course of action regarding a particular termination

decision. These exceptions could involve situations where termination would not be in the

best interest of the government, regardless of cost. The model provides the IMS/MM pre-

loaded essential item information with which to make a termination decision. The model is

available via IRIS.

4.5.2. The SIRS termination model is an interactive web-based application. It has five tabs:

Home, Find Termination Items, Worksheet, Results, and Rates/Storage. The Requirements

Integration Process Improvement Team (RIPIT) updates the data at each point in the

computation cycle (Initial, Mid (Final), and Summary) and daily during the file maintenance

period.

4.5.3. The “Home” tab. This tab includes instructions, along with information about

transportation costs and file maintenance.

4.5.4. The “Find Termination Items” tab. Users begin by selecting this tab and selecting a

SGM NIIN hyperlink from the list or using the filters at the top to select a list by FSC, SGM

NIIN, MMAC, site code, IMS, ERRC, Item Category, or BP Code and then selecting a

specific SGM NIIN. The resulting list is sorted in descending termination quantity dollars

order. When users modify the default settings, their filters are saved for future use. Click the

“Reset” button to return to the default view.

4.5.4.1. During D200A File Maintenance (F/M) periods (Initial or Final computation),

the termination model captures updates that are usually posted daily. (Note: The impact

to the termination quantity in D200A can only be captured if a For Real Computation is

run after changes to other data elements are made.) On the “Find Termination Items” tab,

users may check the “Use D200A F/M values” option to view the latest termination

items. Otherwise, information will be displayed as of the beginning of the file

maintenance period. In order to view the file maintained information on the “Worksheet”

tab, users must click the “Update” button to populate the worksheet with the latest

D200A file maintained values. These values can also be reset to the original values as of


the beginning of the file maintenance period by clicking the “Reset” button. Note: ALL

user-entered stock number information and computational entries will be overwritten

when the worksheet is updated for file maintenance. Contract and transportation

information is updated quarterly.

4.5.5. The “Worksheet” tab. Selecting a SGM NIIN hyperlink takes the user to this tab. The

Worksheet tab contains the elements the IMS/MM needs to review and/or add to complete

the termination model and displays the recommendation. It has four sections. The top

section of the tab includes item data, ALT, PLT, dimensions, weight, and computation entries

such as storage and termination costs. The middle section of the tab includes the contract

information. The bottom section of the tab includes information from the D200A Comp

Worksheet or INS/NSO Status Listing as appropriate based on the ICC. The very top right of

the tab includes the termination recommendation or error messages regarding required

information to complete the calculation. Color-coding shows where users may input values

or make a selection from the drop down menu; these are the asterisked cells with yellow

backgrounds.

4.5.5.1. Stock Number Information. This section is pre-populated with the following

data elements: NSN, site code, ICC, ERRC, Repair Cost, ALT and PLT (in months), and

new unit costs (Unit Price) as seen on page 1 of the SGM Comp Worksheet or INS/NSO

Item Status Listing. The Termination Quantity is populated from the SGM Comp

Worksheet for active items or the INS/NSO Item Status Listing for insurance and NSO

items. The IM name is populated from D043 on a quarterly basis. Quantity Unit Pack

(QUP), unit pack length (in), unit pack width (in), unit pack depth (in), unit pack weight

(lbs) are fed from the D035T PTIA screen on a quarterly basis. Any manual changes to

this data will be documented and retained for audit purposes. The remaining five items

are not pre-populated and are discussed in the following paragraphs.

4.5.5.2. Settlement Costs and Termination Costs (asterisked with yellow backgrounds)

are defaulted to $0.00 and are not required entries. They must only be input if the

contracting activity returned a Termination Authority Template or other written

communication with the information. Termination costs will only refer to the costs to

cancel the termination quantity.

4.5.5.3. Type of Storage, Bundled Shipping, and Hazardous Material (HAZMAT) (also

asterisked with yellow backgrounds) must be completed in order for the model to

compute. These blocks are completed by selecting the appropriate answer from the drop

down menus. For Type of Storage, the possible answers are Covered, Open, or

HAZMAT. For Bundled Shipping, Yes or No. For Hazardous Material, Yes or No.

4.5.5.4. Termination Model Contract Entries. The contract data is pre-populated

quarterly from J018R and does not update during file maintenance. These data elements

include the PR/contract number, PR unfunded quantity, PR funded quantity, undelivered

quantity, delivered quantity, total quantity, contract unit price, and Free-On-Board (FOB)

information. The FOB field will only accept “Origin” or “Destination” as indicated in

the dropdown menu. (The FOB information appears on contracts and may appear on

PRs.). The FOB data is pre-populated based on the code in the J018R data. If the code is

B, C, E, F, H, J, K, L, M, R, or S, then FOB will equal origin; otherwise, FOB will equal

destination.


4.5.5.4.1. Additional contracts may be entered with the “Add” button. For each

additional contract or PR line, the IMS/MM is expected to enter the following:

PR/contract number, PR unfunded quantity, PR funded quantity, undelivered

quantity, delivered quantity, total quantity, contract unit price, and FOB information.

4.5.5.4.2. The Undelivered Balance. This is a calculated field based on the sum of

the Undelivered quantity times the Contract Unit Price.

4.5.5.4.3. Weighted Average (Avg) Unit Price. This is a calculated field based on

the sum of the undelivered and delivered quantities times the contract unit price

divided by the total Undelivered and Delivered quantities.

4.5.5.5. Computation Entries – Active Items. This portion of the “Worksheet” tab

includes information from the SGM Computation Worksheet. It is pre-populated and

updated daily during file maintenance and with each computation cycle (Initial, mid

[Final], and Summary). Manual changes of these entries will be supported by a copy of a

computation or recomputation. Entries are mandatory in all fields -- no cell can be blank.

If the computation worksheet displays no value, enter zero in the corresponding cell in

the model. The third short cells cannot have negative values. If data is changed, it will

be retained unless the “Reset” button is pushed.

4.5.5.5.1. Serviceable (SVC) On Order. This line represents the on-order assets from

J018R. This will include the POS, RSP, and OWRM quantities for the PR funded,

and contract on-order categories. The assets that are input are projected on a

quarterly time-phased basis through the span of the computation. The accumulated

quantities are shown on the worksheet.

4.5.5.5.2. Total Available from Depot Repair (Tot Avail Dep Rpr). This entry

represents the total unserviceable assets available for output within the qtr. It will be

the quarterly sum of the TOC assets, net depot unserviceable, OIM generations

available from repair, RDE generations available from repair, NJR generations

available from repair, and due in available from repair assets.

4.5.5.5.3. Third Over. The third over position equals the difference between the sum

of the total serviceable assets, base repairs, and total available depot repair assets, and

the total gross requirement, when the assets exceed the requirements.

4.5.5.5.4. Third Short. The third short position equals the difference between the

sum of the total serviceable assets, base repairs, and total available depot repair

assets, and the total gross requirement, when the gross requirement exceed the assets.

4.5.5.6. Computation Entries – Insurance/NSO Items. This portion of the “Worksheet”

tab is pre-populated from the INS/NSO Status Listing. It is pre-populated and updated

daily during file maintenance and with each computation cycle (Initial, mid [Final], and

Summary). Any manual changes of these entries will be supported by a copy of an

INS/NSO Item Status Listing. Entries are mandatory in all fields -- no cell can be blank.

If the computation worksheet displays no value, enter zero in the corresponding cell in

the model. The third short cells cannot have negative values. If changed, data will be

retained unless the “Reset” button is pushed.


4.5.5.6.1. Delivery Schedule. This data is pre-populated from the TPAD screen. If

done manually, monthly delivery schedule info (historical AFMC Form 339) will be

used. Aggregate monthly data into qtrs and enter quarterly data in the appropriate

cells.

4.5.5.6.2. Buy or Retention Level. Data is pre-populated from the Buy/Retention

Level, Buy/Retention Detail, and INS/NSO Status Listing (Page 3) (display screen or

printout).

4.5.5.6.3. Serviceable Assets. Data is pre-populated from the Serviceable Assets,

Buy/Retention Detail, and INS/NSO Status Listing (Page 3) (display screen or

printout).

4.5.5.6.4. Total Available Depot Repair (Tot Avail Dep Rpr). Data is pre-populated

from the Assets Avail For Repair, Repair Detail, and INS/NSO Status Listing (Page

3) (display screen or printout).

4.5.5.6.5. Total On Order. Data is pre-populated from the Asset Totals, CARD

screen (Page 3).

4.5.5.6.6. Third Over/Short. Data is pre-populated and calculated as follows:

Serviceable Assets plus Total Available for Repair minus– Buy/Retention Level.

4.5.6. Termination Recommendation. This block, at the top right of the “Worksheet” tab,

provides a termination recommendation based on the calculation of the model. It also

provides messages indicating that additional user action is required for the model to run; e.g.,

N/A - Termination Model needs the following updated: Select Type of Storage; Select

Bundled Shipping; Select Hazardous Material; or Termination Qty cannot exceed the sum of

the PR Unfunded, PR Funded, and Undelivered quantities. If the recommendation is

provided, the user can move to the “Results” tab to see the details of the model results and

the Cost Benefit Analysis (CBA).

4.5.7. The “Results” tab. This tab displays the results of the termination model and the

CBA. It is broken into four parts and includes the costs associated with continuing the

contract and the costs associated with terminating the contract and possibly buying again in

the future. Basic item information such as NSN, IM Name, ERRC, site code, ICC, and Date

Last Updated are also displayed on the page.

4.5.7.1. Termination Request Information. This section lists information that can be

annotated on the Termination Authority Template.

4.5.7.1.1. Undelivered Balance. This is the total dollar value on contract that has not

yet been delivered.

4.5.7.1.2. Total Dollar Value to be Terminated. This is the weighted average unit

price multiplied by the termination quantity in the Termination Model Contract and

Warehousing Entries block. If there is only one contract or if several contracts have

the same unit price, this will be the total dollar value to be terminated. If there are

multiple contracts with different unit prices, this will approximate the total dollar

value to be terminated. Annotate this entry on the Termination Authority Template.

4.5.7.1.3. Max Economical Termination Cost. It would be uneconomical to

terminate a contract when the termination costs exceed this value. If this value is


negative, it is uneconomical to terminate the contract. This entry on the Termination

Authority Template will be annotated if the termination model recommends

termination of all or part of a contract quantity. The remarks will be annotated with

this statement: “If the sum of the termination costs and settlement costs exceed the

maximum economical termination cost of _________ dollars, do not terminate.”

4.5.7.2. Costs to Continue. This part determines the cost to continue the contract, the

storage costs, and the transportation costs.

4.5.7.2.1. Contract Payment Costs. This is the termination quantity cost (termination

quantity times the contract unit price). The cost is discounted to show approximately

when it will be paid. This is based on the assumption that the contractor is paid when

the assets are delivered. (Refer to the Rate/Storage Tab for current rates included in

the termination model.)

4.5.7.2.2. Storage Costs. This is the cost to store the assets in the warehouse. It is

based on the maximum floor space required to store the assets times the cost per

square foot for storage. The model calculates the cost to store quantities on contract

that are excess to the projected need of the item and then discounts the costs. The

storage cost per square foot is inflated according the inflation indices.

4.5.7.2.3. Transportation Costs. This represents the total cost to transport the assets

from the contractor plant to the depot or other designated site. It is based on the

average weight per asset times the cost per pound to transport. If the item has a FOB

“destination,” the cost is zero since the cost of transportation is already included in

the contract unit price. The cost used is discounted to show approximately when it

will be incurred, based on the projected delivery schedule of the termination quantity.

The transportation cost per pound is inflated in accordance with the inflation indices.

4.5.7.2.4. Total Cost to Continue. Total cost to continue is the sum of the storage

costs and the transportation costs.

4.5.7.3. Costs to Terminate and Reprocure.

4.5.7.3.1. Contract Costs. This is the maximum contractor termination cost. The

cost has been discounted by one year to represent approximately when this would be

paid.

4.5.7.3.2. Termination Settlement Costs. This is the maximum settlement cost to

terminate the contract. The cost has been discounted by one year to represent

approximately when this would be paid.

4.5.7.3.3. Increased AF Unit Price Costs. These are the additional dollars that will be

paid for the remaining assets on contract. If the new unit cost for the item is greater

than the weighted average unit price, then this is equal to the PRs and undelivered

balance quantities times the difference between the new unit cost and the weighted

average unit Price. Since this is a rare occurrence, discounting is not applied.

4.5.7.3.4. AF Administrative Termination Costs. These are the costs to process the

paperwork to terminate. This cost is relatively low and determining when the bulk of

this money is expended is very difficult. Therefore, this cost is not discounted.


4.5.7.3.5. AF Administrative PR Costs. This is the average cost to process the

paperwork for a PR quantity being reduced or canceled or a PR quantity that has been

awarded and is being considered for termination. This value is not increased for

multiple PRs or contracts. If SIRS does not project reprocurement (i.e., no third short

quantity beyond the end of the BY) this value is $500. If SIRS projects

reprocurement then $1000 is added to the cover part of the costs to initiate a new PR.

Therefore, the minimum AF administrative PR cost is $500 and the maximum is

$1000. This cost is relatively low and determining when the bulk of this money is

expended is very difficult. Therefore, this cost is not discounted.

4.5.7.3.6. Reprocurement Costs. If the reprocurement quantity is greater than zero,

this value is equal to the reprocurement quantity times the inflation factor at the

reprocurement point, times the present value at the reprocurement point, times the

weighted unit price for the item. This entry is zero if there is no reprocurement.

4.5.7.3.7. Reprocurement Transportation Costs. If the reprocurement quantity is

greater than zero, this value is equal to the transportation cost, times the

reprocurement quantity, times the inflation factor at the reprocurement point, times

the present value at the reprocurement point. If the reprocurement quantity equals

zero, the reprocurement costs equal zero. This entry is also zero if the FOB is

“destination.”

4.5.7.3.8. Repair Costs. This is the one-time projected cost to repair available

unserviceable assets if the contract is terminated. It is the result of the repair cost

times the projected repair quantity (the amount necessary if the termination quantity

were not delivered). The cost is discounted to the qtr when these costs will be

incurred and is based on the projected delivery schedule of the termination quantity.

The repair cost is inflated according to the inflation indices.

4.5.7.3.9. Total Cost to Terminate. Total is the sum of the contract costs, termination

settlement costs, increased AF unit price costs, AF administrative termination costs,

AF administrative PR costs, reprocurement costs, reprocurement transportation costs,

and repair costs.

4.5.7.4. Final Recommendation.

4.5.7.4.1. Total Cost to Continue. This is the sum of the contract payment costs,

storage costs, and transportation costs.

4.5.7.4.2. Total Cost to Terminate. This is the negative value of the total cost to

terminate (paragraph 4.5.7.3.9).

4.5.7.4.3. Cost/Benefit. Cost/Benefit is the total cost to continue plus the cost to

terminate.

4.5.7.4.4. Termination Model Recommendation. The recommendation is based on

the information input and formulas within the model, see Table 4.3


Table 4.3. Termination Model Results – Recommendations.

Definition

1 Do not take termination or cancellation action.

2 Cancel all PRs up to termination quantity. Do not terminate items on contract.

3 Cancel PR. Do not terminate items on contract.

4 Check local guidance.

5 Cancel all PRs up to termination quantity.

6 Cancel PRs, then check local guidance.

7 Take termination action on contract items.

8

Cancel PRs, then fill out a termination request. Send this form to procurement,

requesting the total value of the termination actions not exceed the maximum

economical termination cost of the item.

9 Cancel PRs, then terminate items until termination quantity is satisfied.

10 Cancel unfunded PRs up to termination quantity.

11 Cancel funded PRs up to termination quantity.

12 Cancel all PRs up to termination quantity.

13 Undelivered balance less than $5K - Do not terminate contract items (reference FAR

Subpart 49.101, para C).

4.5.7.5. Print or save the results. Open or save the PDF icon to the user’s PC and select

print from the menu in the PDF document.

4.5.8. The “Rates/Storage” tab. This tab displays the storage costs, transportation costs, and

discount rates used in the termination model. It also provides guidance on the INS/NSO

delivery schedule entries.

4.5.8.1. Discount Rates. Discount rates reflect the degree to which both costs and

benefits in the future are less valuable than costs or benefits today. Discount rates are

measured in terms of the value in currency today of a good versus the delivery of that

good at some time in the future. The discount rate measures the relative value of a good

over time measured in current year dollars. The termination model applies the discount

rate to compute the present value of a future reprocurement.

DONALD E. KIRKLAND

Brigadier General, USAF

Director, Logistics, Civil Engineering, and Force

Protection


Attachment 1

GLOSSARY OF REFERENCES AND SUPPORTING INFORMATION

References

AFFARS 5349.102, Air Force Federal Acquisition Regulation Supplement, 6 April 2015

AFH 23-123, Volume 1, Materiel Management Reference Information, 8 August 2013

AFH 23-123, Volume 2, Part 1, Integrated Logistics System-Supply (ILS-S), Materiel

Management Operations, 8 August 2013

AFH 23-123, Volume 2, Part Two, Integrated Logistics System-Supply (ILS-S), Standard Base

Supply System Operations, 8 August 2013

AFI 20-115, Propulsion Management For Aerial Vehicles, 12 February 2014

AFI 23-101, Air Force Materiel Management, 29 January 2016

AFMAN 21-106, Joint Regulation Governing the Use and Application of Uniform Source

Maintenance, and Recoverability Codes, 29 August 2014

AFMAN 33-363, Management of Records, 1 March 2008

AFMC MP Part 5349, Contracting Mandatory Procedure – Termination of Contracts, January

2014

AFMCI 20-102, Requirements Definition and Purchase Instrument Development, 11 July 2013

AFMCI 23-103, Diminishing Manufacturing Sources and Materiel Shortages (DMSMS)

Program, 13 October 2000

AFMCI 23-106, Initial Requirements Determination, 3 February 1997

AFMCI 23-112, Management of Items Subject to Repair (MISTR), 7 March 2006

AFMCMAN 20-2, Security Assistance Program (SAP) Logistics Procedures, 16 January 2014

AFMCMAN 23-101, Volume 2, System Level Data and OPR Reports (D200A, D200N), TBD

AFMCMAN 23-101, Volume 3, Computational Results (D200A, D200N), TBD

AFMCMAN 23-101, Volume 4, IMS/PMS/MM Data and Reports (D200A, D200N), TBD

AFMCMAN 23-101, Volume 5, Equipment Specialist Data and Reports (D200A, D200N), TBD

AFMCMAN 23-101, Volume 6, Central Secondary Item Stratification (D200A, D200N), TBD

AFMCMAN 23-3, Cataloging and Standardization, 14 September 2010

DoD 4100.39-M, Federal Logistics Information System (FLIS) Procedures Manual, varies by

volume.

DoD 4140.01, Volume 3, DoD Supply Chain Materiel Management Procedures: Materiel

Sourcing, 23 May 2003

DoDM 4140.01, Volume 10, DoD Supply Chain Materiel Management Procedures: Metrics

and Inventory Stratification Reporting, 10 February 2014


DoD 5200.2-R, Personnel Security Program, 1 January 1987

Federal Acquisition Regulation (FAR) Part 49, current edition

Public Law 111-84, National Defense Authorization Act for Fiscal Year 2010, Division A, Title

III, Section 328, 28 October 2009

Title 10 United States Code Section 2210


Title 10 United States Code Section 2306b


T.O. 00-20-3, Maintenance Processing of Reparable Property and The Repair Cycle Asset

Control System, 15 August 2015

T.O. 00-20-9-WA-1, Forecasting Repl Requirements For Selected Calendar And Hourly Time

Change Items, 15 January 2014

T.O. 00-25-195-WA-1, AF Technical Order System Source, Maintenance, and Recoverability

Coding of Air Force Weapons, Systems, and Equipments, 1 October 2012

Prescribed Forms

AFMC Form 318, Item Contracting History Record

Forms Adopted

AF Form 1996, Adjusted Stock Level

AFLC Form 47, Asset Reconciliation - Investment Items, (Historical Form)

AFMC Form 206, Temporary Work Request

AFMC Form 247, Asset Reconciliation - Investment Items, (Historical Form)

AFMC Form 326, Provisioned Item Order

AFMC Form 339, Due-In Assets Status Record, (Historical Form)

AFMC Form 614, Recoverable Item Initial Requirements Computation Worksheet

AFMC Form 804, Renegotiation And Drive Adjustment Record

AFTO Form 223, Time Change Requirements Forecast

DD Form 2875, System Authorization Access Request (SAAR)Termination Authority Template

Abbreviations and Acronyms

A&AS— Advisory & Assistance Service

A-R—Asset Reconciliation

AAC—Acquisition Advice Code

AAM—Aircraft Availability Model

AAMD—Aircraft Availability Model Data


AAO—Approved Acquisition Objective

ABCS—Automated Budget Compilation System

ADRQ—Display Additive Requirements

AF—Air Force

AFAA—Air Force Audit Agency

AFAO—Approved Force Acquisition Objective

AFB—Air Force Base

AFFARS—Air Force Federal Acquisition Regulation Supplement

AFMC—Air Force Materiel Command

AFSC—Air Force Sustainment Center

AI—Application/Indenture

ALC—Air Logistics Complex

ALT—Administrative Lead Time

ALVW—Adjusted level Verification Worksheet

AMC—Acquisition Method Code

API—Applications, Programs, Indentures

ARCR—Asset Reconciliation Computational Results

ARD—Asset Reconciliation Data

ARLG—Asset Reconciliation Losses and Gains

AROO—Asset Reconciliation On Order

AVG—Average

AY—Apportionment Year

BLSS—Base Level Self-sufficiency Spares

BMD—Basic Management Data

BP—Budget Program

BSO—Budget Support Objective

BY—Budget Year

CAC—Common Access Card

CAD/PAD—Cartridge Actuated Devices/Propellant Activated Devices

CAGE—Contractor and Government Entity

CARD—Consolidated Assets and Requirement

CAV AF—Commercial Asset Visibility-Air Force


CBA—Cost Benefit Analysis

CLIN—Contract Line Item Number

CLSSA—Cooperative Logistics Supply Support Arrangement

CMD—Command

CNDM—Condemnation

COPA—Center OF Parts Activity

CREP—Contract Repair Enhancement Program

CRF—Centralized Repair Facility

CSAG-M—Consolidated Sustainment Activity Group-Maintenance

CSAG-S—Consolidated Sustainment Activity Group-Supply

CSIS—Central Secondary Item Stratification

CSN—Current Stock Number

CW—Computation Worksheet

CY—Current Year

DDC—Deferred Disposal Code

DIC—Document Identifier Code

DIOH—Due In From Overhaul

DIS—Display

DISA—Defense Information Systems Agency

DLA—Defense Logistics Agency

DLM—Defense Logistics Manual or Depot Level Maintenance

DMBA—Depot Maintenance Budget Authority

DMISA—Depot Maintenance Inter-Service Support Agreement

DoD—Department of Defense

DOLP—Date of Last Procurement

DOTM—Due-Out To Maintenance

DQ—Data Query

DRC—Depot Repair Cycle

DSD—Data System Designator

DSS—Distribution Standard System

DTI—Data Type Interrogation

E-mail—electronic mail


EAIM—End Article Item Manager

ENTNAC—Entrance National Agency Check

EOH—Engine Overhaul

EPSS—Equipment Specialist (ES) Report (Output Products)

EQP—Equipment

ERRC—Expendability, Recoverability, Reparability Category

ES—Equipment Specialist

EXPRESS—EXecution and Prioritization of REpair Support System

EY—Extended Year

FAD—Factors Application Data

FBD—Factors Basic Data

FIC—Factor Indicator Code

FM or F/M—File Maintenance

FMS—Foreign Military Sales

FOB—Free-On-Board

FOE—Final Operating Environment

FRAP—Forecast Rates And Percents

FRIR—For Real Item Record

FSC—Federal Supply Classification

FUD—Factor/Usage Data

FUP—Forecast Unit Price

FY—Fiscal Year

GFE—Government-Furnished Equipment

GFM—Government-Furnished Material

GSD—General Support Division

GUI—Graphic User Interface

I&S—Interchangeability and Substitutability

I&SG—Interchangeable and Substitutable Group

IAC—Item Activity Code

IAO—Information Assurance Officer

ICC—Item Category Code

ICP—Inventory Control Point


ICS—Interim Contractor Support

ID/IQ—Indefinite Delivery/Indefinite Quantity

IIRP—Improved Item Replacement Program

IM—Item Manager

IMCS—Item Management Control System (D043)

IMS—Inventory Management Specialist

INDX—Index

INI—Inflation Index

INIS—Insurance/Numeric Stockage Objective Item Status

INS—Insurance

IOA—Index of Actions

IOE—Initial Operating Environment

IPD—Item Program Data

IRD—Initial Requirements Determination

IRIS—Interactive Requirements Information Services

IRL—Item Review Listing

ISA—In Service Asset

ISD—Input System Data

ISID—Interface System Input Dates

JEIM—Jet Engine Intermediate Maintenance

JR—Job Routed

LG—Logistics Directorate

LOR—Letter of Responsibility

LOT—Life-of-Type

LRC—Latest Repair Cost

MAH—Moving Average History

MAJCOM—Major Command

MCR—Materiel Cost Recovery

MD—Mission Design

MDC—Manager Designator Code

MDS—Mission Design Series

MGFT—Mission Design Goal/Floor Factor Table


MIAP—Multi-Host Internet Access Portal

MIEC—Mission Item Essentiality Code

MIPR—Military Interdepartmental Purchase Request

MISC—Miscellaneous

MISTR—Management of Items Subject to Repair

MM—Materiel Manager

MMAC—Materiel Management Aggregation Code

MP—Mandatory Procedures

MRRD—MISTR Repair and Repair Data

MRRL—Materiel Repair Requirements List

MRPR—MISTR Repair and Repair Data

MTBD—Mean Time Between Demands

MYC—Multiple Year Contract

MYP—Multiple Year Procurement

NAC—National Agency Check

NC—Non-Catalog

NHA—Next Higher Assembly

NIIN—National Item Identification Number

NIMSC—Nonconsumable Item Materiel Support Code

NJR—Non–Job-Routed

NRTS—Not Reparable This Station

NSN—National Stock Number

NSO—Numeric Stockage Objective

NTPD—Non-Time Phased Asset Data

O&ST—Order and Shipping Time

OIM—Organizational and Intermediate Maintenance

OP—Output Products

OPR—Office of Primary Responsibility

OPSS—Office of Primary Responsibility (OPR) Reports

OSTD—Other Service Total Demands and Requirements

OWO—On Work Order

OWRM—Other War Reserve Materiel


OWRM EXCL—Other War Reserve Materiel Exclusion

PBL—Performance-Based Logistics

PC—Personal Computer

PCLT—Procurement Lead Time

PCN—Product Control Number

PCO—Procurement Contracting Officer

PDM—Programmed Depot Maintenance

PEC—Program Element Code

PEL—PRELOG Error List

PES—PRELOG Error Summary

PF—Past Factors

PFI—Product Format Information

PGRM—Program

PICA—Primary Inventory Control Activity

PIN—Personal Identification Number

PIO—Provisioned Item Order

PL—Public Law

PLD—Pipeline Data

PLT—Production Lead Time

PMO—Production Management Officer

PMS—Production Management Specialist

POC—Point of Contact

POS—Peacetime Operating Stock

PP—PRELOG Plots

PPCO—Provisioning Procurement Contracting Officer

PPH—PRELOG Plot Headers

PR—Purchase Request

PRELOG—Predictive Logistics

PRGM—Program

PSC—Program Select Code

PSI—PRELOG Selected Information

QEC—Quick Engine Change


QPAPPL—Quantity Per Application

QPA—Quantity Per Assembly

qtr—Quarter

QTY—Quantity

QUP—Quantity Unit Pack

RAMP—Reportable Asset Management Process

RAP—Rates And Percents

RCO—Requirements Control Officer

RDE—Requirements Data Exchange

RDEO—Requirements Data Exchange Output

RDS—Reutilization and Disposition System

REALM—Requirements/Execution Availability Logistics Module (D087H)

RIID—Requirements Item Identification Data

RIR—Reduction in Requirement

RIW—Reliability Improvement Warranty

RMS—Requirements Management System

RPR—Repair Products

RSP—Readiness Spares Package

RTS—Reparable This Station

S/A—Service/Agency

SAAR—System Authorization Access Request

SAMIS—Security Assistance Management Information System

SCC—Supply Condition Code or System Compute Code

SCMG—Supply Chain Management Group

SCMW—Supply Chain Management Wing

SCOW—Supply Chain Operations Wing

SFTY LVL EXCL IND—Safety Level Exclusion Indicator

SGM—Subgroup Master

SICA—Secondary Inventory Control Activity

SIRS—Secondary Item Requirements System

SL—Safety Level

SMBA—Supply Maintenance Budget Authority


SMC—System Management Code

SMCW—Subgroup Master Computation Worksheet

SND—Stock Number Data

SNIC—Stock Number Identity Cross Reference

SOCW—Subgroup Master Other War Reserve Materiel Computation Worksheet

SOR—Source of Repair

SRAN—Stock Record Account Number

SRC—Source Reference Code

SRRB—Spares Requirements Review Board

SSIR—Supply System Inventory Report

SUD—Stock Record Account Number Usage Data

SVC—Service

SVC T-I—Service Turn-In

T.O— Technical Order

TBLD—Table Data

Term—Termination

TOC—Technical Order Compliance

TOIMDR—Total Organizational and Intermediate Maintenance Demand Rate

TPAD—Time-Phased Asset Data

TRND—Trend Analysis

TSUH—Total Subgroup Master Usage History

UH—Usage History

URC—Unit Repair Cost

USC—United States Code

USERID—User Identification

WARD—War Data

WRM—War Reserve Materiel

WTIR—What If Item Recomputation

Terms

Acquisition— Obtaining logistics support, supplies, or services under an acquisition agreement

or under a cross-servicing agreement. This includes purchasing (whether for payment in

currency, replacement-in-kind, or by exchange for equal value), renting, leasing, or any method


of temporarily obtaining logistics support, supplies, or services. Reference DoDM 4140.01,

Volume 1, DoD Supply Chain Materiel Management Procedures: Operational Requirements.

Acquisition Advice Code (AAC)—Codes indicating how (as distinguished from where) and

under what restrictions an item will be acquired. Reference DoD 4100.39-M, Volume 10, Table

58.

Activity— A unit, organization, or installation performing a function or mission, (e.g., reception

center, redistribution center, naval station, naval shipyard). Reference Joint Publication 1-02,

DoD Dictionary of Military Terms.

Additive Requirement—Requirements that are supported by projected requirements

(e.g.,modifications) rather than past demand experience. Requirements computed outside

therecoverable computation. Reference AFI 23-101.

Adjustments (Physical Inventory)— The accounting transaction that corrects a book balance to

agree with the quantity of the item in storage. Such adjustments may result from (1) physical

inventory, (2) a potential discrepancy revealed by a materiel release denial or location

survey/reconciliation, (3) capitalization/decapitalization actions, (4) reidentification of stock, (5)

type of pack changes, (6) catalog data changes, (7) supply condition and purpose code changes,

etc. Reference DLM 4000.25, Defense Logistics Management Standards.

Administrative Lead Time (ALT)— The time interval between initiation of a purchase request

and the date of signature of a contract. Reference DoDM 4140.01, Volume 2, DoD Supply

Chain Materiel Management Procedures: Demand and Supply Planning.

Apportionment Year (AY)— The second Fiscal Year (31 March and 30 June cycle) or first

Fiscal Year (30 September and 31 December). It is also known as the operating year.

Approved Acquisition Objective (AAO)— The quantity of an item authorized for peace time

and war time requirements to equip and sustain U.S. and allied forces, according to current DoD

policies and plans. That quantity shall be sufficient to support other U.S. Government agencies,

as applicable. Reference DoDM 4140.01, Volume 6, DoD Supply Chain Materiel Management

Procedures: Materiel Returns, Retention, and Disposition.

Assembly— In logistics, an item forming a portion of equipment that can be provisioned and

replaced as an entity and which normally incorporates replaceable parts or groups of parts.

Reference DoDM 4140.01, Volume 2.

Automated Budget Compilation System (ABCS)—An online, real-time mainframe system that

resides on the Logistics and Sustainment Management Data Bank (LMDB)(D075). It is used to

prepare budget submissions for both buy and repair of AFMC- managed reparables and

consumables. Reference AFMCI 23-112, Management of Items Subject to Repair (MISTR).

Base Condemnation Rate—The number of base condemnations divided by the sum base RTS

and base condemnations. Reference AFI 23-101.

Budget— A planned program for a fiscal period in terms of estimated costs, obligations, and

expenditures. Reference AFMAN 65-604, Appropriation Symbols and Budget Codes.

Budget Code— A one-position alphanumeric code employed by the Air Force to identify

investment items to budget programs from which procurement of the particular items is funded,


or to identify expense items to the various divisions of the Air Force Stock Fund. Reference

DoD 4100.39-M, Volume 10, Table 67.

Budget Cycle— That time necessary to formulate, review, present, and secure approval of the

fiscal program for a specified ensuing period. Reference AFMAN 65-604.

Budget Year (BY)— The fiscal year covered by the budget estimate. A budget year begins 1

October and ends 30 September of the following calendar year. It is used by the federal

government for accounting purposes, and is frequently referred to as "BY." Reference AFMAN

65-604.

Cancellation Request— A transaction that allows a requisitioner or other authorized activity to

request cancellation of all or a portion of the quantity of materiel ordered in a previously

submitted requisition. Reference DoDM 4140.01, Volume 5, DoD Supply Chain Materiel

Management Procedures: Delivery of Materiel.

Cataloging— The process of uniformly identifying, describing, classifying, numbering, and

publishing in the Federal Catalog System all items of personal property (items of supply)

repetitively procured, stored, issued, or used by federal agencies. Reference DoDM 4140.01,

Volume 8, DoD Supply Chain Materiel Management Procedures: Materiel Data Management

and Exchange.

Center Of Parts Activity (COPA)—An AF information technology system that requires human

intervention in the supply chain to assure materiel is made available to the mechanics/technicians

when required to produce aircraft and repair commodities needed by the warfighter.

Central Secondary Item Stratification (CSIS)— An automated capability that applies to

wholesale and retail asset and requirements data. The CSIS shall uniformly display the materiel

requirements and associated asset status of individual secondary items and generate summaries

of essential information. If a methodology other than stratification is used as a foundation, an

audit trail to the applicable stratification table shall be submitted to the USD(L&MR). Secondary

item assets shall be stratified at least semiannually. One stratification shall be as of September 30

(for inventory reporting and funding reviews), and the other shall be as of March 31 (for budget

preparation). Reference AFI 23-101.

Commercial and Government Entity (CAGE) Code— A five character data element assigned

to establishments which are manufacturers or have design control of items of supply procured by

the Federal Government. Reference DoD 4100.39-M, Glossary.

Component— In logistics, a part or combination of parts having a specific function, which can

be installed or replaced only as an entity. Reference DoDM 4140.01, Volume 6.

Computation Asset Cutoff Date—The last calendar day of each calendar quarter (31

December, 31 March, 30 June, and 30 September). The Secondary Item Requirements System

(SIRS)(D200A) computes items using data that are current on these dates.

Compute Code—One-digit alpha code assigned to all subgroup master items in SIRS that tells

D200A to perform or not perform a computation. SIRS generates the compute code; it cannot be

file maintained.

Consolidated Sustainment Activity Group–Supply Division (CSAG-Supply)— The CSAG-

Supply provides policy, guidance, and resources to meet the needs of the Air Force for spare

parts, in war and peace. The CSAG-Supply manages weapons system spare parts, fuels,


equipment, and items used for non-weapon system applications. Reference AFI 65-601, Volume

1, Budget Guidance and Procedures.

Consumable Item— An item of supply or an individual item (except explosive ordnance and

major end items of equipment) that is normally expended or used up beyond recovery in the use

for which it is designed or intended. Reference DoDM 4140.01, Volume 2.

Contract— A mutually binding legal relationship obligating the seller to furnish the supplies or

services (including construction) and the buyer to pay for them. It includes all types of

commitments that obligate the Government to an expenditure of appropriated funds and that,

except as otherwise authorized, are in writing. In addition to bilateral instruments, contracts

include (but are not limited to) awards and notices of awards; job orders or task letters issued

under basic ordering agreements; letter contracts; orders, such as purchase orders, under which

the contract becomes effective by written acceptance or performance; and bilateral contract

modifications. Contracts do not include grants and cooperative agreements covered by 31

U.S.C. 6301, et seq. Reference FAR, Subpart 2.1.

Contract Line Item— An item of supply or service on a contractual document usually identified

by a contract line item number (CLIN). Reference DFARS 204.7103.

Contract Termination—- The cessation or cancellation, in whole or in part, of work under a

prime contractor a subcontract for the convenience of, or at the option of, the government, or due

to failure of the contractor to perform in accordance with the terms of the contract. Reference

AFI 23-101.

Contracting— Purchasing, renting, leasing, or otherwise obtaining supplies or services from

nonfederal sources. Contracting includes description (but not determination) of supplies and

services required, selection and solicitation of sources, preparation and award of contracts, and

all phases of contract administration. It does not include making grants or cooperative

agreements. Reference FAR, Subpart 2.1.

Contracting Activity— An element of an agency designated by the agency head and delegated

broad authority regarding acquisition functions. Reference FAR, Subpart 2.1.

Contracting Office— An office that awards or executes a contract for supplies or services and

performs post-award functions not assigned to a contract administration office (except for use in

Part 48, see also 48.001). Reference FAR, Subpart 2.1.

Contracting Officer— A person with the authority to enter into, administer, and/or terminate

contracts and make related determinations and findings. The term includes certain authorized

representatives of the contracting officer acting within the limits of their authority as delegated

by the contracting officer. Reference FAR, Subpart 2.1.

Contractor—An authorized Air Force contractor that occupies the facilities of, or receives

support from, another Air Force, Air Force Reserve, or Air National Guard unit. Reference AFI

65-601, Volume 1.

Coordination—- The necessary action to ensure adequate exchange of information to integrate,

synchronize, and deconflict operations between separate organizations. Coordination is not

necessarily a process of gaining approval but is most often used for mutual exchange of

information. Reference AFI 23-101.


Current Year (CY)— The first Fiscal Year covering the time period from the computation asset

cutoff date to the first calendar day of the next FY (1 October).

Customer— The individual or activity requesting or ordering a material asset at any

organizational level. Reference DoDM 4140.01, Volume 5.

Data Element— A basic unit of information in a business transaction. Reference DLM

4000.25.

Demand— An indication of a requirement, a requisition, or similar request for an item of supply

or individual item. Demands are categorized as either recurring or non-recurring. Reference

DoDM 4140.01, Volume 1.

Depot Maintenance Inter-Service Support Agreement (DMISA)— A formalized agreement

similar to a contract whereby one Service (the Agent) obligates itself to provide depot

maintenance support for another Service (the Principal). (Source: OPNAVINST 4790.14A, et.al)

For the purpose of this manual, DMISA also covers depot maintenance provided for under inter-

Service support agreements not covered by the referenced joint regulation. Reference DLM

4000.25.

Depot Repair Cycle (DRC)—Begins when a maintenance activity determines that an

unserviceable item can be repaired and end when the unserviceable item is restored to

serviceable condition and is recorded as such on supply records. Include all time between the

beginning and end of the repair cycle in computing repair-cycle requirements, except avoidable

time, such as time expended due to the lack of a repair requirement or inefficiency. Beginning

and ending points of each segment of the total repair cycle are described in Appendix 4 of this

enclosure. Do not include increases to the repair cycle time due to awaiting parts in computing

repair cycle. Reference DoDM 4140.01, Volume 2.

Depot Stock Levels—Depot stock levels represent those levels that are required in support of

depot overhaul requirements. These are subdivided into two categories, job-routed (JR) and non

job-routed (NJR) stock levels. JR items are those items that are repaired as part of a higher

assembly repair. The stock level in support of JR overhaul requirements represents the amount

of stock required to prevent delay of programmed overhauls during the subassembly O&ST. NJR

items are those items that are removed during an overhaul and turned into supply. The NJR

stock level requirement represents the quantity of stock required to support the overhaul line

during subassembly O&ST. Reference AFI 23-101.

Distribution Standard System—A DLA information technology system that creates a paperless

environment for the distribution business area and provides automated support tools needed to

implement process control and uniformity. It is the means for DLA to provide tailored logistics

support.

Document Number— A unique reference number assigned to a requisition or a release/receipt

document in order to identify the transaction throughout the logistics system and for the life of

the transaction unto; its retirement is authorized in official audit reports. The first six positions

are the DoDAAC of the reporting activity; the next four positions are the year and three position

numerical day of the year; the next position is the utilization code; and the last three positions are

the activity serial number. Reference DLM 4000.25-1.


Effective Date (ED)— The year and Julian day denoting the date that a predetermined condition

or action becomes effective in the defense logistics system. (e.g., 04122 is 1 May 2004).

Reference DoD 4100.39-M, Glossary.

End Item— A final combination of end products, component parts, or materials that is ready for

its intended use, e.g., ship, tank, mobile machine shop, or aircraft. Reference DoDM 4140.01,

Volume 2.

Equipment— In logistics, all nonexpendable items needed to outfit or equip an individual or

organization. Reference DoDM 4140.01, Volume 5.

Equipment Specialist (ES)—- Individual who collects, analyzes, interprets and develops

specialized data about specific pieces of equipment and/or systems. Provides information and

advisory service to other functions involved in the design, test, production, procurement, supply,

operation, repair, or disposal of equipment. This advice includes, but is not limited to, issues

concerning interchangeability and substitutability of NSNs, repair concepts, ERRC coding and

reliability. Assists an acquisition team during the development/production phase of a

system/equipment. Responsible for the technical management of a system, subsystem or

commodity during the sustainment phase of a program. Maintains documentation supporting

factors, including those based on initial provisioning data, applications and any other file

maintained data. Makes decisions for technical orders and AFTO Forms 22, Technical Manual

(TM) Change Recommendation and Reply.

Essential Item— A support item or a repair part whose absence renders the supported system or

end item inoperable. Reference DoDM 4140.01, Volume 2.

Essentiality Code— Weapon system or end item designation used to indicate the measure of an

item’s military worth in terms of how its failure (if a replacement is not immediately available)

would affect the ability of a weapon system, end item, or organization to perform its intended

functions. In stockage models, it is the number by which the shortage cost parameter is

multiplied to reflect the differences in military worth among items. Reference DoDM 4140.01,

Volume 2.

Estimated Termination Costs—- An informal estimate of costs to terminate all or part of a

contract. The contracting activity provides this estimate to the IMS/MM who submits the

request for termination to contracting, usually without contacting the contractor, as an initial

assessment of the benefits of terminating a contract.

Excess— Materiel at a retail supply activity that is excess to that activity’s requirements and is

subject to return to the wholesale materiel manager, redistribution within the DoD supply chain,

or to disposal by Defense Logistics Agency Disposition Services. Reference DoDM 4140.01,

Volume 1.

Expendability, Recoverability, Reparability, Category (ERRC) Code— A code employed by

the Air Force to categorize AF inventory into various management groupings. The three position

ERRC Designator and the one-position ERRC Code are completely interchangeable. Generally,

the three position is used in correspondence and publications and the one position in automatic

data processing programs (space premium). Reference DoD 4100.39-M, Volume 10, Table 69.

Extended Year (EY)— The Fiscal Year that follows the Budget Year.


Failure— The event, or inoperable state, in which any item or part of an item does not, or would

not, perform as previously specified. AFI 20-106 (IP), Management of Aviation Critical Safety

Items.

Federal Supply Classification (FSC)— A series of four numbers at the beginning of the

national stock number (NSN) that designates the general commodity grouping of the item of

supply (e.g., Class 5130 designates hand tools, power driven). Reference DoDM 4140.01,

Volume 3.

File Maintenance—The act or method of making changes, deletions, or additions to elements of

data on an established computer file.

Fiscal Year (FY)— The 12 month period which begins 1 October of one year and ends 30

September of the next. Reference AFMAN 65-604.

Forecast Unit Price (FUP)—A nine-position numeric element that is determined by multiplying

the unit price by the appropriate inflation factors in D200A. Valid entries are in dollar and cents

format with two decimal places.

Foreign Military Sales (FMS)— That portion of the United States security assistance

authorized by the Foreign Assistance Act of 1961, as amended, and the Arms Export Control Act

of 1976, as amended. This assistance differs from the International Military Education and

Training Program in that the recipient provides reimbursement for defense articles and services

transferred. Also called FMS. (See Joint Publication 1-02.) Reference DLM 4000.25.

Free-On-Board— Term used in conjunction with a physical point to determine—(1) The

responsibility and basis for payment of freight charges; and (2) Unless otherwise agreed, the

point where title for goods passes to the buyer or consignee. “F.o.b. destination” means free on

board. Reference FAR, Subpart 2.1.

Free-On-Board (FOB) Destination— Product is accepted at destination by the Government.

Shipper provides transportation. Reference DLM 4000.25.

Free-On-Board (FOB) Origin— Product is accepted at origin (source) by the Government.

Government provides transportation with commercial carriers. Reference DLM 4000.25.

Future Program— The number of time changes required by quarter over the 10-year period.

Hazardous Materiel (Dangerous Goods)— A substance of materiel that has been determined

to be capable of posing an unreasonable risk to health, safety, and property when transported.

This materiel includes explosives, gasses (compressed, liquefied, or dissolved under pressure),

flammable liquids, flammable solids or substances, oxidizing substances, poisonous and

infectious substances, radioactive substances, corrosives, and miscellaneous dangerous

substances presenting real or potential hazards to life and property. Procedures for handling this

materiel are specified in applicable publications of the Department of Transportation, the

Interstate Commerce Commission, Federal Aviation Agency, U.S. Coast Guard, U.S. Agriculture

Department, U.S. Public Health Service, Intergovernmental Maritime Consultative Organization,

the International Civil Aviation Organization, and in federal or military documents. Dangerous

goods is the term applied to hazardous materiel in international movement. Reference DLM

4000.25.

Individual Item— A single instance of a stock-numbered item, a single assembly, or a single

subassembly. Reference DoDM 4140.01, Volume 2.


Initial Requirements Determination (IRD)(D200H)—Information Technology system that

computes recoverable and consumable item requirements. It is the preferred method for initial

spares computation, accumulating multiple weapons and includes a simulation capability.

Reference AFMCI 23-106, Initial Requirements Determination.

Initial Spares— Spares stocked to support a newly fielded weapon system or a modification of a

weapon system. Reference DoDM 4140.01, Volume 2.

Insurance Item— A non-demand-based, stocked, essential item for which no failure is predicted

through normal usage. However, if a failure were to be experienced or a loss should occur

through accident, abnormal equipment or system failure, or other unexpected occurrence, lack of

replacement item will seriously hamper the operational capability of a weapon system.


Interchangeability and Substitutability (I&S)— Conditions which permit the exchange of one

item for another without affecting design or performance beyond acceptable limits. Reference

DoD 4100.39-M, Glossary.

Interchangeable Item— An item which possesses such functional and physical characteristics

as to be equivalent in performance, reliability, and maintainability, to another item of similar or

identical purposes, and is capable of being exchanged for the other item without selection for fit

or performance and without alteration of the items themselves or adjoining items, except for

adjustment. Reference DoD 4100.39-M, Glossary.

Interchangeable and Substitution Group (I&SG)— Set of items that have similar physical

and functional characteristics to the extent that the items can provide comparable functional

performance against a given requirement. Reference AFI 23-101.

Inventory— Materiel, titled to the U.S. Government, held for sale or issue, held for repair, or

held pending transfer to disposal. This definition covers the same population of items as the

definition for inventory in Chapter 4 of Volume 4 of DoD 7000.14-R (Reference (f)). Inventory

does not include tangible personal property to be consumed in normal operations, operating

materials, and supplies as defined in DoD 7000.14-R. Reference DoDM 4140.01, Volume 1.

Inventory Control Point (ICP)— An organizational unit or activity within the DoD supply

system assigned the primary responsibility for the materiel management of a group of items

either for a particular Military Department or for the DoD as a whole. In addition to materiel

management functions, an ICP may perform other logistics functions in support of a particular

Military Department or for a particular end item (e.g., centralized computation of retail

requirements levels and engineering tasks associated with weapon system components).


Inventory Management Specialist—Individual who performs analytical work in managing,

regulating, coordinating, or otherwise exercising control over supplies, equipment, or other

materiel. The work includes one or more phases of materiel management including initial

planning, provisioning and requirements determination, acquisition and distribution,

accountability, and ultimate issue for consumption, retention, or disposal. The work requires

knowledge of acquisition processes, automated records and control systems, materiel substitution

criteria, and storage, issue, and disposal processes.


Item— An item is a single hardware article or a unit formed by a grouping of subassemblies,

components or constituent parts. In the DoD, an item is any article produced, stocked, stored,

issued, or used; or any product, including systems, materiel, parts, subassemblies, sets and

accessories. Reference DLM 4000.25.

Item Activity Code (IAC)—One-position code used in SIRS to identify the cycle or cycles that

an item must be reviewed.

Item Identification— A collection and compilation of data to establish the essential

characteristics of an item that give the item its unique character and differentiate it from other

supply items. Reference DoDM 4140.01, Volume 3.

Item Management Control System (IMCS)(D043)—Information technology system that

provides for AF participation in the Federal Cataloging Program, as set forth by DoD 4100.39M.

D043 interfaces with FLIS and numerous other databases, and is the central repository of Federal

and AF logistics data for over two million AF-used items of supply. Reference AFMCMAN 23-

3.

Item Management Team—Functional group consisting of IMS/MM, ES, PMS, Logistics

Management Specialist, and Engineer.

Item Manager Wholesale Requisition Process (IMWRP)(D035A)—An information

technology system that provides worldwide property accounting, inventory control, and

distribution/redistribution of materiel at the wholesale level (reference AFMCMAN 23-5,

Volume 1, D035A, D035B, RAMP and WHSL Module Data Subsystems).

Item Review Listing (IRL)— Web-based tool designed for the IMS/MM and PMS to use

during file maintenance. It presents the list of NSNs for the IMS/MM/PMS and ES in the order

of most important to review, down to least important to review. It also provides the capability to

document which items they have reviewed/worked. The IRL in IRIS also provides the ability for

IMS/MM, PMS, and ES supervisors to monitor the progress of their personnel during the

review/file maintenance window(s).

Job Routed Repair—When a recoverable component is found to be unserviceable during the

overhaul, the item is removed, repaired/reconditioned, and reinstalled on the same end item.

Reference AFI 21-101, Aircraft and Equipment Maintenance Management, AFMC Supplement

Kits— Assembled repair parts and components required for maintenance support of an end item.

Reference DoDM 4140.01, Volume 4, DoD Supply Chain Materiel Management Procedures:

Make and Maintain Materiel.

Life-of-Type (LOT) Buy— A one-time procurement, when all cost effective and prudent

alternatives have been exhausted, for the total future requirement of an item that is no longer

expected to be produced. The procurement quantity is based upon demand or engineering

estimates of wear out rates or item malfunction or failure sufficient to support the applicable

equipment until phased out. Reference DoDM 4140.01, Volume 2.

Maintenance (Materiel)— All action taken to retain materiel in a serviceable condition or to

restore it to serviceability. It includes inspection, testing, servicing, classification as to

serviceability, repair, rebuilding, and reclamation. (Source: Joint Publication 1-02).

Maintenance, used generically in this manual, also includes evaluation, assembly, disassembly,

conversion, and modification. Reference DLM 4000.25.


Master Item— The item/NSN in an I&S Family which is commonly regarded by the managing

and using Services/Agencies as a suitable substitute for all other items in the family as the

preferred item for procurement purposes. Reference DoD 4100.39-M, Glossary.

Materiel— All items necessary to equip, operate, maintain, and support military activities

without distinction as to its application for administrative or combat purposes, excluding real

property, installations, and utilities. Materiel is either serviceable (i.e., in an issuable condition)

or unserviceable (i.e., in need of repair to make it serviceable). Reference DoDM 4140.01,

Volume 1.

Materiel Condition— A classification of materiel that reflects its readiness for issue and use or

to identify the action underway to change the status of materiel. Reference DLM 4000.25.

Materiel Management— That phase of military logistics that includes managing, cataloging,

demand and supply planning, requirements determinations, procurement, distribution, overhaul,

and disposal of materiel. Reference DoDM 4140.01, Volume 1.

Materiel Management Aggregation Code (MMAC)— A two-position alphabetic code (AA

thru ZZ) authorized to identify specific items (National Stock Numbers) to be managed by a

specific manager at one of the Air Logistics Centers (ALCs), Contractor Inventory Control

Points (**) or Special Cataloging Activities. The ** identifies a MMAC designated for use by a

Contractor ICP. Reference DoD 4100.39-M, Volume 10, Table 66.

Materiel Manager— Any DoD activity or Defense Agency that has been assigned materiel

management responsibilities for the DoD and participating federal agencies. The term includes

responsibilities performed by either wholesale materiel managers or retail materiel managers:

managing, cataloging, demand and supply planning, requirements determination and definition,

procurement, distribution, overhaul and repair of reparable materiel, and disposal of materiel.


Military Interdepartmental Purchase Request (MIPR)— The primary document used by the

Department of Defense to order goods or services from other DoD Services or Components, as

well as other Government activities outside the DoD. The goods or services may be provided

from in-house resources or may be procured from commercial sources. The Air Force uses the

AF Form 616 for orders between Air Force units. Reference AFI 65-116, Air Force Purchases

Using Military Interdepartmental Purchase Requests (MIPRS).

Mission Item Essentiality Code (MIEC)—Three-position alpha/numeric code that designates

the level of criticality of an asset to the mission. This code is broken down into: position 1 =

System Essentiality, position 2 = Item Essentiality, and position 3 = Organization Essentiality.

This code is provided to the bases by the major commands. Reference AFH 23-123, Volume 1.

Modification— A U.S. Government-approved change in the configuration of a part or item that

offers a benefit to the U.S. Government by correcting deficiencies, satisfying a change in

operational or logistic support requirements, or effecting a life-cycle cost savings. Reference


Multi—Year Contract – A contracting method that procures items or services over more than

one year, but not more than five years, without establishing options. Reference AFMCI 20-102,

Requirements Definition and Purchase Instrument Development.


Multiple Year Contract (MYC)—A one-year contract with option years spanning up to a total

of five years for an item that can be reasonably forecasted over several years. Reference AFMCI

20-102, Requirements Definition and Purchase Instrument Development.

Multiple Year Procurement (MYP)—Contracts used primarily for large weapon system

acquisitions. These contracts must specify quantities, prices, and delivery schedules, and usually

a substantial cancellation penalty applies if the government wants to cancel the buy. MYPs are

generally appropriate only for major system buys managed by AFMC Product Centers.

Reference AFMCI 20-102, Requirements Definition and Purchase Instrument Development.

National Item Identification Number (NIIN)— The last 9 digits of the NSN that differentiates

each individual supply item from all other supply items. The first 2 digits signify the National

Codification Bureau that assigned the NIIN, while the last 7 digits are not significant and are

sequentially assigned by the FLIS. All U.S. manufactured items have a National Codification

Bureau Code of “00” (cataloged before 1975) or “01” (cataloged in 1975 or later). Reference

DoDM 4140.01, Volume 9, DoD Supply Chain Materiel Management Procedures: Materiel

Programs.

National Stock Number (NSN)— The 13-digit stock number replacing the 11-digit federal

stock number. It consists of the 4-digit federal supply classification code and the 9-digit national

item identification number. The national item identification number consists of a 2-digit National

Codification Bureau number designating the central cataloging office (whether North Atlantic

Treaty Organization or other friendly country) that assigned the number and a 7-digit (xxx-xxxx)

nonsignificant number. Arrange the number as follows: 9999-00-999-9999. Reference DoDM

4140.01, Volume 2.

Next Higher Assembly (NHA)— The next higher assembly on or with which the item is used as

a subassembly, part, attachment, or accessory. Also, the classification of the higher assembly is

indicated specifically in Groups and Classes of the Federal Supply Classification (Cataloging

Handbook H2). May actually include components, subassemblies, assemblies and end items or

systems. Reference DoD 4100.39-M.

Non-Consumable Item Materiel Support Code (NIMSC)— Alphanumeric codes assigned to

non-consumable items, which indicates the degree of materiel support (numeric) or repair

responsibility (alpha). Reference DoDM 4140.01, Volume 2.

Non Job Routed Repair—When an unserviceable item is removed and replaced with a

serviceable item from supply. This process is strictly a remove and replace operation. Reference

AFI 21-101, Aircraft and Equipment Maintenance Management, AFMC Supplement.

Not Reparable This Station (NRTS)— Term used to characterize the process of returning

items that cannot be successfully repaired by a base maintenance repair shop to a repair activity

designated by the wholesale item manager. Reference AFI 23-101.

Numeric Stockage Objective (NSO)—Essential items with low or sporadic demands or

forecasts of failure. These items are stocked in minimum quantities. Reference AFI 23-101.

On-Order Excess— Assets on an unfunded PR that exceed the SIRS worldwide buy operating

level, or assets on contract or funded PR that exceed the SIRS worldwide termination level.


Operating Level (OL)— The quantities of materiel or operating stocks required to sustain

operations in the interval between replenishment shipments. Reference DoDM 4140.01, Volume

2.

Operating Requirement— Ensures that all assets removed due to failure will be replaced at the

time of removal. It is computed by multiplying the organizational/intermediate demand rate by

the operating program. Reference AFI 23-101.

Optimum Position— Indicated by items not computing in a buy, repair, termination or excess

position.

Order and Shipping Time (O&ST)— Average number of days between the initiation and

receipt of stock replenishment requisitions assuming sufficient stock is available on the depot

shelf to satisfy the requisition at the time the requisition is received. Reference AFI 23-101.

Organic— The capability of a Military Service or a Defense Agency to sustain logistics

operations through U.S. Government organizational structures. Reference DoDM 4140.01,

Volume 1.

Organizational Intermediate Maintenance (OIM)—That maintenance which is the

responsibility of and performed by a using organization on its assigned equipment. These

responsibilities normally include the inspection, service, lubrication, adjustment and replacement

of parts, minor assemblies, and subassemblies. Reference AFI 23-101.

Other War Reserve Materiel (OWRM)— Consumable and reparable items required to sustain

forces after the RSP support period. Reference AFI 25-101, War Reserve Materiel (WRM)

Program Guidance and Procedures.

Overhaul— The process of disassembly sufficient to inspect all the operating components and

the basic end article. It includes the repair, replacement, or servicing as necessary, followed by

the reassembly and bench check or flight test. Upon completion of the overhaul process, the

component or end article will be capable of performing its intended service life or service tour.

Reference AFI 20-106 (IP).

Performance-Based Logistics (PBL)— Logistics that delineate outcome performance goals of

weapon systems, ensure that responsibilities are assigned, provide incentives for attaining these

goals, and facilitate the overall life-cycle management of system reliability, supportability, and

total ownership costs. Reference DoDM 4140.01, Volume 2.

Preferred Item— An item of supply which has functional or physical characteristics which

render it a higher order of preference for use than that accorded to another similar item of supply.

Reference DoD 4100.39-M.

Primary Inventory Control Activity (PICA)— The service or agency ICP designated as the

single activity within the DoD responsible for providing materiel support. Reference DoDM

4140.01, Volume 2.

Procurement Lead Time (PCLT)— The sum of the ALT and PLT. Procurement lead time is

the lead time for acquisition of secondary items. Reference DoDM 4140.01, Volume 2.

Production Lead Time (PLT)— The interval between the date of signature of a contract and

the receipt of the first significant delivery of the purchased materiel into the supply system.



Production Management Officer (PMO)— Individual within an SCM group that provides staff

surveillance, procedural guidance and management controls for file maintenance of recoverable

items by the PMSs in D200A to apply production management experience in analyzing and

evaluating issues, directing, coordinating and implementing improvements/enhancements that

will improve the accuracy and quality of computed repair requirements.

Production Management Specialist (PMS)— An individual assigned by the contracting

activity to act as liaison for production, supply and transportation issues.

Program Element Code (PEC)—A description of a mission by the identification of the

organizational entities and resources needed to perform the assigned mission. Resources consist

of forces, manpower, materiel quantities, and costs, as applicable. The program element is the

basic building block of the Future Years Defense Program. Reference AFMAN 65-604.

Program Office—An office created by the Component Acquisition Executive to complete the

necessary actions associated with planning of an acquisition program. Reference DoDI 5000.02,

Operation of the Defense Acquisition System.

Program Select Code (PSC)—A four-position code that determines the type(s) of item

program(s) to be developed. It is assigned to each component that is expected to be removed

from a higher assembly and replaced. The four-position PSC in D200A translates to a two-

position PSC in D200F. Reference AFMCI 23-109.

Programmed Depot Maintenance (PDM)—- Inspection and correction of defects that require

skills, equipment or facilities not normally possessed by operating locations. Reference T.O. 00-

25-4, Depot Maintenance of Aerospace Vehicles and Training Equipment.

Property Loss— Unintended, unforeseen, or accidental loss, damage or destruction to

Government property that reduces the Government’s expected economic benefits of the property.

Loss does not include purposeful destructive testing, obsolescence, normal wear and tear, or

manufacturing defects. Loss includes, but is not limited to: items that cannot be found after a

reasonable search; theft; damage resulting in unexpected harm to property requiring repair to

restore the item to usable condition; or destruction resulting from incidents that render the item

useless for its intended purpose or beyond economical repair. Reference DoDI 5000.64.

Provisioning— The management process of determining and acquiring the range and quantity of

support items necessary to operate and maintain an end item of materiel for an initial period of

service. Reference DoDM 4140.01, Volume 2.

Purchase Request (PR)—The initial request prepared for future procurement action used for the

central procurement of AF requirements.

Quantity—- Shows the number of units applicable to a particular transaction (rp 25-29).

Reference DLM 4000.25-1, Appendix 2.6.

Quantity Per Application (QPAPPL)—The number of components that are installed in a

higher assembly that is also the component’s application. The application and the next higher

assembly may or may not be the same assembly. Reference AFMCI 23-109, Applications,

Programs, and Indentures.

Quantity Per Assembly (QPA)— The number of components that are installed in that

component’s Next Higher Assembly (NHA). Reference AFMCI 23-109.


Readiness Spares Package (RSP)— A kit consisting of selected spares and repair parts required

sustaining operations (without resupply) at a base, a deployed location, or a dispersed location

for the first month of conventional activity as projected in USAF war plans. Reference AFH 23-

123, Volume 1.

Receipt— A transmission or other acknowledgment made by a receiving entity to indicate that a

message, good, or service has been satisfactorily received. Receipt is often denoted by signing a

situation specific form, such as DD Form 250, “Material Inspection and Receiving Report,” DD

Form 1149, “Requisition and Invoice/Shipping Document,” or DD Form 1348-1a, “Issue

Release/Receipt Document.” Reference DoDI 5000.64.

Reclamation— The process of reclaiming required serviceable and economically reparable

components and material from excess or surplus property for return to the proper supply activity,

whereas the residue is processed as disposable property. Reference DoDM 4140.01, Volume 2.

Reconciliation— The process of aligning the physical count with the quantity posted to the

accountable property records, researching discrepancies, and determining inventory accuracy,

i.e., calculation of loss or overage rates. Reference DoDI 5000.64.

Reduction—(As it refers to termination actions) An action to reduce or cancel quantities that

have been requested for purchase on a PR or MIPR, but are not yet on a firm contract or priced

exhibit. A reduction is accomplished with an amendment to the PR or MIPR.

Reduction In Requirements (RIR)— (As it refers to termination actions) An official request

from the IMS asking the contracting activity to terminate quantities that are on a firm contract.

Reliability Improvement Warranty (RIW) Item—An item that is under manufacturer

warranty. When RIW-coded items fail, the retail supply system keys on RIMCS data to initiate

shipment to a contractor using project code 390 and project name PACER WARRANT.

Repair Cycle Days—- A 3-position numeric field used to compute demand levels for repair

cycle items. The average repair cycle days are computed using data from all quarters contained

on the repair cycle record. The computed figure is the Repair Cycle Time (RCT). Reference

AFH 23-123, Volume 1.

Reparable Item— An item of supply subject to economical repair and for which the repair (at

either depot or field level) is considered in satisfying computed requirements at any inventory

level. Reference DoDM 4140.01, Volume 10.

Replenishment— Actions to resupply an inventory when it reaches the ROP. Reference DoDM

4140.01, Volume 2.

Requirements Computation— Any mathematical calculation performed to support

requirements determination functions. Reference DoDM 4140.01, Volume 2.

Requirements Control Officer (RCO)— Individuals within the IMS groups that disseminate

guidance, assist IMSs with SIRS issues and to help them understand secondary item processes

and tasks. RCOs also consolidate and submit the data inputs for reports required by the site’s

D200A OPRs.

Requirements Item Identification Data (RIID)(D200E)—An information technology system

that receives feeds from the Master Item Identification Control System (MIICS) (D043). It


provides cataloging data and stock list changes. Reference AFMCI 23-109, Applications,

Programs and Indentures.

Requisition— An order for materiel initiated by an established, authorized organization (i.e., a

DoD or non-DoD organization that has been assigned a DoD activity address code) that is

transmitted either electronically, by mail, or telephoned to a supply source within the DoD or

external to the DoD (the General Services Administration, the Federal Aviation Administration,

or other organizations assigned management responsibility for categories of materiel), according

to procedures specified in Reference (a) and DLM 4000.25-1-M (Reference (u)). Reference


Research (Physical Inventory)— An investigation of potential or actual discrepancies between

physical count and recorded balances. The purpose of research is to determine the correct

balance and determine the cause of discrepancies. Reference DLM 4000.25.

Safety Level (SL)— The quantity of materiel required to be on-hand to permit continued

operation in the event of a minor interruption of normal replenishment or a fluctuation in

demand. Reference DoDM 4140.01, Volume 2.

Secondary Inventory Control Activity (SICA)— The service or agency inventory control

point receiving materiel support from the PICA for selected logistics functions. Reference


Secondary Item— An item of supply that is not defined as a principal item and includes

reparable components, subsystems, and assemblies, consumable repair parts, bulk items and

material, subsistence, and expendable end items, including clothing and other personal gear.


Secondary Item Requirements System (SIRS)—- A wholesale information technology system

aligned under the Requirements Management System (RMS). It computes the Air Force’s

secondary item requirements on an aggregate basis, and applies available worldwide assets to

those requirements. It is assigned Data System Designator (DSD) D200A.

Security Assistance (SA)—- A group of programs authorized by the Foreign Assistance Act

(FAA) of 1961, as amended and the Arms Export Control Act (AECA) of 1976, as amended, or

other related statutes by which the United States provides defense articles, military training and

other defense related services, by grant, loan, cash sale, or lease, in furtherance of national

policies and objectives. Reference Joint Publication 1-02.

Service Code—One-digit alpha code that signifies the first position of the MAPAC and

identifies the customer service. Reference DLM 4000.25, Appendix 2.2 and DLM 4000.25-1,

Appendix 2.2.

Shelf-Life Item— An item of supply possessing deteriorative or unstable characteristics to the

degree that a storage time period is assigned to ensure that it performs satisfactorily in service.

Reference DoD 4140.27-M, Shelf-Life Management Manual.

Shipment— Movement of materiel from point of origin to destination by any mode. Reference

DLM 4000.25.

Shop Flow Days (SFD)—The number of calendar days required to process an end item,

measured from the time the item is placed in work to the day of serviceable turn-in. Reference

AFMCI 21-105, Depot Maintenance Work Measurement.


Source of Repair (SOR)— An industrial complex (organic, commercial contract, or inter-

service facility) with required technical capabilities to accomplish depot repair, overhaul

modification, or restoration of specific types of military hardware or software. Reference T.O.

00-25-4.

Source Of Supply— Any Federal Government organization exercising control of materiel and

to which requisitions are directed. Reference DLM 4000.25.

Source Reference Code (SRC)—A system-generated code used to indicate the origin of the unit

data.

Stock Fund— Revolving fund established to finance the costs of inventories of supplies. It is

authorized by specific provision of law to finance a continuing cycle of operations.

Reimbursements and collections derived from such operations are available for use by the fund

without further action by the Congress. Reference AFI 23-101.

Stock Level—Demand level or an adjusted level. Reference AFI 23-101.

Storage Costs— The variable costs of storing materiel. A storage cost factor is not variable (and

therefore not considered) if the factor would remain the same after eliminating 50 percent of the

stored materiel. Use one percent of the annual average value of the relevant inventory for storage

costs unless actual variable storage costs are available. Reference DoDM 4140.01, Volume 2.

Subgroup—A range of items within a family group which are interchangeable with each other.

Items which have no interchangeable relationships with any other items are the sole members of

their subgroup. Items which are not interchangeable are assigned different subgroup code values.

DoD 4100.39-M.

Substitute Item— An item which possesses such functional and physical characteristics as to be

capable of being exchanged for another only under specified conditions or for particular

applications and without alteration of the items themselves or of adjoining items. This term is

synonymous with the phrase "one way interchangeability", such as item B can be interchanged in

all applications for item A, but item A cannot be used in all applications requiring item B.

Reference DoD 4100.39-M, Glossary.

Supply—- The procurement, distribution, maintenance while in storage and salvage of supplies,

including the determination of kind and quantity of supplies. Reference Joint Publication 1-02.

Supply Condition Code (SCC)—A one-position alphabetic code used to classify materiel in

terms of readiness for issue and use or to identify action underway to change the status of

materiel. Reference DLM 4000.25-2, Military Standard Transaction Reporting and

Accountability Procedures, Appendix 2.5.

Termination— An action to reduce or cancel an undelivered quantity of assets that are on a firm

contract.

Termination Authority Template— Instrument that the IMS/MM uses to request the

contracting activity to initiate termination action. Reference AFFARS 5349.102.

Termination Code—A 2-digit code used in the Automated Budget Compilation System

(ABCS) to describe the status and cause of a termination.

Termination Model—A tool that helps determine if termination is economical. The model is

available via IRIS.


Total OIM Demand Rate— The rate at which an item has failed. It is developed by dividing the

sum of the base repaired this station (RTS), base not reparable this station (NRTS), and the base

condemnations by the item past program for the period. Reference AFI 23-101.

Transportation Costs— Costs paid to common carriers or Government activities to move

materiel within the transportation system. Reference DLM 4000.25.

Unit Price—Indicates the cost or value of one unit of issue of an item. Reference AFH 23-123,

Volume 1.

User— An individual, organization, or accounting entity that receives services. A user may be

internal or external to the DoD Component. Reference DoD 7000.14-R, Glossary.

War Reserve Materiel— Consists of enterprise managed, dynamically positioned equipment

and consumables that contribute to initial operations and provide initial support cross the full

range of military operations. It enhances Agile Combat Support capability to reduce the time

required to achieve an operational capability and/or produce an operational effect. Reference

AFI 23-101.

Wholesale— The highest level of organized DoD supply that procures, repairs, and maintains

stocks to resupply the retail levels of supply. Synonymous with wholesale supply, wholesale

level of supply, wholesale echelon, and national inventory. DoDM 4140.01, Volume 1.

Worldwide Buy Operating Level— The basic operating requirement (condemnations,

replacements, and additive requirements) at the buy point in the requirements computation. For

additional information, see AFMCMAN 23-101, Volume 3.

Worldwide Termination Level— Result of a comparison of basic operating requirement at the

AY buy point and the BY termination point in the computation. For additional information, see

AFMCMAN 23-101, Volume 3.


Attachment 2

SIGNATURE REQUIREMENTS

A2.1. Table A2 1. identifies the signature levels required for items that computed in

termination on the Summary computation.

Table A2.1. Signature-Level Requirements for Terminations.

A2.1.1. The IMS/MM, ES, PMS, Leads (IMS, PMS, and ES), RCO, TCO, and Production

Management Officer (PMO) will sign all terminations. Exceptions are identified below for

organizations that do not have the level(s) designated; go to the next higher level for signature.

Exceptions:

PMS, PMS Lead and PMO Do not sign ERRC “N” or “P” or AF SICA NIMSC 5

ERRC “T” items

IMS/MM supervisor Signs all termination codes except 02, 03, & 13

IMS/MM and ES Signatures required for requirements with termination

code 13 assigned

Group $999,999.00/Center > $1 million Term code 12

Squadron Term code 14

IMS/MM supervisor Will coordinate on all computations/INS/NSO Item

Status Listings after validating that additive

requirements are accurate and adequately supported

A2.1.2. Below are the required approval levels required for terminations based upon dollar

thresholds:

Threshold Minimum Approval Level *

$1 - $999,999.99 Element/Unit

$1,000,000 - $2,000,000 Section

$2,000,000.01 - $5,000,000 Flight/Branch

$5,000,000.01 - $50,000,000 Squadron/Division

$50,000,000.01 - $150,000,000 Group/Directorate

$150,000,000.01 - $500,000,000 Wing

* Note: If the organization does not have the approval level identified, then the approval will be

elevated to the next level of approval in the chain of command (i.e., no section, then elevate to

flight/branch).

A2.2. Table A2 2. identifies the signature levels required for items that computed a POS and/or

RSP buy (CY plus AY), a POS and/or RSP repair (CY plus AY), or in excess on the Summary or

recomputation after the Summary computation.


Table A2.2. Signature-Level Requirements for Buy, Repair, and Excess.

A2.2.1. The IMS/MM, ES and PMS will sign Summary computations for items computing buy,

repair and excess. Exceptions are identified below for organizations that do not have the level(s)

designated; go to the next higher level for signature. See Notes 1 and 2.

Exceptions:

Annual signature Unless quantity breaches next level

Program Office coordinates Buy and/or repair with additives and items on which the

application program is phasing in or out to determine if the

schedule is still valid.

PMS, PMS Lead and PMO Do not sign ERRC “N” or P” or AF SICA NIMSC 5 ERRC

“T” items

Paragraph 1.11.7. POS or RSP with positive asset reconciliation variance or

when buying more than the computed POS/RSP requirement

Paragraph 1.12.1. LOT buy

Paragraph 1.11.5. Economic procurement

IMS/MM supervisor Will coordinate on all computations/INS/NSO Item Status

Listings that have file maintained additives after validating

that additive requirements are accurate and adequately

supported

Note 1: The IMS/MM, PMS and ES will sign the computation, recomputation or INS/NSO Item

Status Listing based on the IAC.

Note 2: For buy, repair or excess, higher signatures are only required once a year beginning with

the March computation cycle as long as the buy, repair, or excess quantity does not increase or

the item does not breach the next signature level. The IMS/MM will attach the signature page

from that cycle or annotate on the computation or INS/NSO Item Status Listing which cycle was

last used for higher level signatures, the quantity on that cycle, and the dollar value on that cycle.

A2.2.2. Below are the required approval levels required for buy, repair, and excess based upon

dollar thresholds (see Notes 3 - 5):

Threshold Minimum Approval Level

$1 million - $3 million RCO, TCO, PMO, leads (IMS, ES and PMS), and Element

$3,000,000.01 - $5,000,000 Section

$5,000,000.01 - $20,000,000 Flight/Branch

$20,000,000.01 - $50,000,000 Squadron/Division

$50,000,000.01 - $150,000,000 Group/Directorate

$150,000,000.01 - $500,000,000 Wing

$500,000,000.01 - up Center

Note 3: For buys, signature level will be determined by which FY has the highest total POS plus

RSP dollar value - CY plus AY. For repair, signature level will be determined by which FY has

the highest total POS plus RSP dollar value - CY plus AY.

Note 4: If the POS and/or RSP for buy and repair in the CY or AY does not breach $1,000,000,

but the POS and/or RSP for buy or repair in the BY or EY breaches $5,000,000 or above, the

RCO, TCO, PMO, Lead and the lowest level of supervision must review and sign for the item

with the remainder of the signature policy above still in force.

Note 5: If the organization does not have the approval level identified, then the approval will be

elevated to the next level of approval in the chain of command (i.e., no section, then elevate to


flight/branch).

A2.3. Table A2 3. provides a ready reference on timeframe requirements for obtaining the

required signatures. All timeframes are based upon printout date of the products and are

calculated in calendar days.

Table A2.3. Signature Timeframes.

Responsibility Requirement Timeframe

IM / ES Termination computations 10 calendar days

IM Buy or repair requirements or 1st occurrence of excess or if

excess quantity is greater than previous cycle

35 calendar days

IM /ES Excess is equal to or less than previous cycle’s excess or if

in an optimum position

60 calendar days

ES Summary Factors/Usage 35 calendar days

ES Products for buys, repair, and excess 35 calendar days

PMS Summary MRRD reports 35 calendar days

PMS Computations, recomputations and INS/NSO Item Status

Listings with repair requirements

35 calendar days

A2.4. Title 10 United States Code (USC) Title 2458 and Public Law 111-84, National Defense

Authorization Act for Fiscal Year 2010, Division A, Title III, Section 328 requires: “a plan for a

comprehensive assessment of inventory items on-hand that have no recurring demands, including

the development of metrics to track years of no demand for items in stock; and procedures for

ensuring the systemic review of such items for potential reutilization or disposal.” Therefore,

NSNs having assets with no recurring demands in over 5 years will be reviewed annually to

determine whether the assets/quantity of assets still need to be retained. The review will be

conducted based on the IAC of the NSN. The IMS/MM, with the assistance of the PMS, ES and

the Program Office, will determine if the system(s) on which the item is a component is still

being used by the AF, another Service/Agency (S/A), or FMS customer(s). A statement will be

placed on the computation or INS/NSO Item stating that this review was completed as well as

the determination of the review—how many assets will be disposed or retained and why. The

IMS/MM, their supervisor, and ES will sign and date the documents with this review statement

and the squadron commander must approve.

A2.5. Each site may establish signature level requirements for the entire site for computations,

INS/NSO Item Status Listings and Factors/Usage Printouts. These signature levels must ensure

that high dollar actions (i.e., buy, repair, excess, and termination) receive review by other

person(s) in addition to the IMS/MM, PMS, and ES. Signature of the computation products

indicates that management has reviewed and concurred with the indicated actions. In cases

where HQ AFMC has established a minimum signature level in this manual, the site may require

higher signature level requirements. Title or function will be included with signatures (i.e., IMS

or flight chief). Site unique signature level requirements will be codified in an official

supplement to this manual IAW AFI 33-360.