FA8770-RFI-18-IMLCI_Ref_B)_AFMCMAN23-3_14_SEP_2010.pdf

BY ORDER OF THE COMMANDER

AIR FORCE MATERIEL COMMAND

AIR FORCE MATERIEL COMMAND

MANUAL 23-3

14 SEPTEMBER 2010

Material Management

CATALOGING AND STANDARDIZATION

COMPLIANCE WITH THIS PUBLICATION IS MANDATORY

ACCESSIBILITY: Publications is available on the e-Publishing Website at www.e-publishing.af.mil for downloading.

RELEASABILITY: There are no releasibility restrictions on this publication.

OPR: AFMC/A4RM

Supersedes: AFMCMAN23-3, 19 January 2007

Certified by: AFMC/A4R

(Col Harry Berry)

Pages: 170

This manual outlines the policies, procedures, and organizational roles and responsibilities pertinent to accomplishing materiel identification and standardization programs and projects. It applies to HQ Air Force Materiel Command (AFMC), Defense Logistics Agency (DLA) cataloging activity, DLIS-KF, Air Force cataloging agent; the Air Logistics Centers (ALCs); all

Contractor Inventory Control Points (ICPs); and those Air Force logistics organizations whose missions require cataloging and standardization functions. This publication does not apply to Air

National Guard (ANG) and the Air Force Reserve Command (AFRC) and their units. Refer recommended changes and questions about this publication to the Office of Primary

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

AF Forms 847 from the field through Major Command (MAJCOM) publications/forms managers. Ensure that all records created as a result of processes prescribed in this publication are maintained in accordance with AFMAN 33-363, Management of Records, and disposed of in accordance with Air Force Records Information Management System (AFRIMS) Records

Disposition Schedule (RDS) located at https://www.my.af.mil/gcss-af61a/afrims/afrims/. See

Attachment 1 for glossary of references and supporting information.

SUMMARY OF CHANGES

Updated office symbols, websites, and publication references throughout the manual. Clarified cataloging processes in paragraph 1.2.1. Defined DLIS responsibility in paragraph 1.2.2.9.

Removed ―issue‖ from paragraph 6.2.5 and further defined responsibilities in paragraph 6.4.

Changed Figure 7.1. to allow bases to use reason code ―9‖ for ERRC challenges. Added the requirement for the ALC/AFGLSC to support the AF Medical Operations Agency (AFMOA) when Base AF Forms 86 are received in paragraphs 7.3.4. to 7.3.4.4. Added paragraph 7.6.15.

http://www.e-publishing.af.mil/ http://www.e-publishing.af.mil/ https://www.my.af.mil/gcss-af61a/afrims/afrims

2 AFMCMAN23-3 14 SEPTEMBER 2010

through 7.6.15.2. to add ES responsibility to review and support technical decisions. Changed paragraphs 7.7.3.1.2.1. through 7.7.3.1.2.1.2. to clarify Requests for Cataloging Data/Action when another S/A is responsible for the action. Changed paragraph 7.7.3.1.2.2. to mandate completion of JLC Form 17 for nonconsumable items. Added IM responsibility to ensure provisioned items are coded and reviewed for shelf-life considerations and that the engineer/ES perform a criticality determination for each new item in paragraphs 8.3.1.3. and 8.3.1.4.

Changed/added paragraph 8.4.5. through 8.4.5.2. to modify local reassignment procedures.

Added paragraphs 8.5.1. through 8.5.1.2. for FSGs 83 and 84, and for FSCs 9420 or 9430.

Added time limits in paragraph 9.3.1.5. Added paragraph 9.3.1.6. in case a systemic error occurs. Added requirement to change AAC to ―V‖ prior to AAC ―Y‖ in paragraph 9.3.2.3.

Changed paragraph 9.3.3.1. to include procedures for transactions that the D143C does not allow. Added paragraphs 9.3.5. and 9.3.6 to allow batch requests of 25 NSNs or more. Added paragraph 9.5 for DEMIL challenges and 9.6 for misrouted DLA Form 339. Added the use of

ERRC ―C‖ to paragraph 9.8.1.1. Eliminated extraneous information from paragraph 10.2.1.

Added NWRM procedures in paragraph 10.4. Added the requirement for CIIC ―O‖ in Table

11.2. Added paragraph 13.4. for PSLC for other S/A managed items. Changed procedures for

Hazardous Materials Identification in Chapter 16. Added paragraph 18.2.4. to address CSWS items identified during provisioning. Added Moving Average Cost (MAC) data under IMCS data in paragraph 23.1.15. Revised Chapter 27 to reflect new GIRDER process in DLIS.

Transferred information in Table 30.2. and in paragraph 36.2. to new Attachment 1, Glossary of

References and Supportive Information. Added paragraph 36.5 to include ES‘s responsibilities.

PART 1

INTRODUCTION AND GENERAL INFORMATION

Chapter 1—CATALOGING AND STANDARDIZATION MISSIONS 11

1.1. Missions

1.2. Cataloging

1.3. Standardization

Chapter 2—RESPONSIBILITIES 13

2.1. General

2.2. Specific Areas of Responsibility

2.3. Cataloging and Standardization Maintenance Transactions

2.4. ALC/AFGLSC/Contractor ICP Responsibilities

Chapter 3—BASIC PRINCIPLES, METHODS, AND TOOLS 14

3.1. Introduction

3.2. Basic Principles

3.3. Federal Supply Classification (FSC) System

3.4. Procedures

AFMCMAN23-3 14 SEPTEMBER 2010 3

3.5. Federal Item Identification Guides (FIIG) Program

3.6. Special Rules Applicable to the Compilation and Publication of the Subsistence

Electronic Catalogs (Foodnet (C8900-SL), NAPA, SPVIA, LSN, and Market Ready

Catalogs

Chapter 4—FEDERAL LOGISTICS INFORMATION SYSTEM (FLIS) PROBLEM

REPORTING AND SYSTEM CHANGE REQUESTS (SCR) 17

4.1. Purpose

4.2. SCR Reference:

4.3. Contact Points

4.4. Submittal of FLIS Problem Reports

4.5. SCR Procedures

Table 4.1. System Change Request Processing Timeframes

Chapter 5—PREPARATION OF FEDERAL CATALOGING SUBMITTALS 20

5.1. General

5.2. Guidelines for Preparing and Submitting Item Identifications (II) and Revisions. 20

5.3. Forms

5.4. Preparation of Cataloging Actions for Transmittal to the FLIS

5.5. Obtaining Commercial and Government Entity (CAGE) Codes

5.6. Request for Special Processing of Federal Cataloging Submittals

Chapter 6—NON-DEFINITIVE (ND) NUMBER AND KITS ―K‖ PROCESSING 22

6.1. Purpose

6.2. Definition and Use of Non-Definitive (ND) Control Numbers

6.3. HQ AFMC ND Policy

6.4. Air Logistics Centers (ALCs)/AF Global Logistics Support Center (AFGLSC) and

Contractor Supported Weapon Systems (CSWS) Programs will:

6.5. ND Item Manager will:

6.6. D143C Process and Control of NDs

6.7. The ND Waiver Process

Table 6.1. NDWA

6.8. Assignment of Kit or ―K‖ Stock Numbers

6.9. Definition and Use of ―K‖ Stock Numbers

Figure 6.1. ―K‖ Stock Number Format

6.10. Responsibilities Concerning Kit or ―K‖ Stock Numbers

4 AFMCMAN23-3 14 SEPTEMBER 2010

Chapter 7—BASE INITIATED REQUEST FOR CATALOGING DATA/ACTION 30

7.1. Purpose

7.2. Definition and Use

Table 7.1. Reason Codes and Definitions

7.3. Determination of Responsible ALC

7.4. Control of Request for Cataloging Data/Action:

7.5. Groups/Squadrons Responsibilities

7.6. ES/IM Responsibilities

7.7. The Provisioning Support Office/Cataloging Manager (PSO/CATM) Responsibilities. 36

7.8. AF Cataloging Agent Responsibilities

7.9. Base Responsibilities

7.10. Follow-up for Base Requests

Chapter 8—NEW ITEM REQUESTS 41

8.1. Purpose

8.2. Control Number Structure

8.3. IM and/or ES Responsibilities

8.4. AFGLSC Provisioning Support Office (PSO/CATM) Responsibilities

8.5. When the provisioning office identifies a requirement for an item assigned to FSG 83, 84, FSCs 9420 or 9430 process as follows

8.6. Cataloging Agents in DLIS

8.7. Canceling an NC Number

8.8. Substitute NSNs for New Item Requests

Table 8.1. ALC/AFGLSC/CSWS Activity/SIASCN Codes

Table 8.2. NC Return Code Matrix

Table 8.3. Cataloging Agent‘s Return Codes

Table 8.4. ALC/AFGLSC/CATM Instruction Codes

Table 8.5. ALC/AFGLSC/ES Reply Codes

Chapter 9—CATALOGING REVISION REQUESTS 52

9.1. Introduction

9.2. Director/Materiel Management (DMM) Responsibilities

9.3. IM and ES Responsibilities

9.4. Provisioning Support Office (PSO/CATM (Cataloging Manager)) Responsibilities. 55

9.5. DEMIL Challenges

AFMCMAN23-3 14 SEPTEMBER 2010 5

9.6. Catalog Actions for DLA-Managed Items

9.7. Cataloging Activity Responsibilities

9.8. HQ AFMC ERRC Code Policy for Non-Weapon Related DLA or GSA-Managed NSNs.56

Figure 9.1. ALC/CSWS Revision Control Number Format

Table 9.1. ALC/CSWS Revision Codes

Table 9.2. Messages for NIINs. Full Text Messages for Use by Cataloging Agents Only: ... 59

Table 9.3. Messages for NIINs. Messages for Use by ALCs/CSWS:

Table 9.4. Messages for Prepositioned CMD Processing. Messages from Cataloging Agent: 60

Chapter 10—CATALOGING AND STANDARDIZATION PROCESSES AT SPECIAL

ACTIVITIES 61

10.1. Introduction

10.2. General

Table 10.1. Mission Unique Cataloging and Standardization Functions

Table 10.2. AF Special Activity Cataloging

10.3. D143C Processing Procedures

10.4. Nuclear Cataloging Requests

Table 10.3. Serialized Report Codes

Table 10.4. NWRM Indicator Codes

Chapter 11—SECURITY CLASSIFIED CATALOG DATA/CRYPTOLOGICAL ITEMS 66

11.1. Methods of Physical Security Classification

Table 11.1. DOD Controlled Inventory Item Codes (CIIC)

Table 11.2. CIICs for Nuclear Ordnance Items

Table 11.3. CIICs for Cryptologic Items

11.2. Procedures

Chapter 12—DD FORM 1685 AND JLC FORMS 17 AND 19

COLLABORATION/COORDINATION 68

12.1. General

12.2. Processing DD Forms 1685

12.3. Processing JLC Forms 17 and 19

12.4. The AF Cataloging Agent Responsibilities

12.5. Intra-Air Force Logistics Reassignment for Air Force SICA NSNs

Chapter 13—PRIORITY SYSTEM FOR OBTAINING NATIONAL STOCK NUMBERS (NSN)

AND PRIORITY STOCKLIST CHANGES (PSLC) OF AF-MANAGED ITEMS. 70

6 AFMCMAN23-3 14 SEPTEMBER 2010

13.1. Priority FLIS Processing

13.2. Priority System for Obtaining NSNs

13.3. PSLC of AF-Managed Items

13.4. PSLC for Other S/A-Managed Items

Table 13.1. Priority Stock list Change Monitor/Focal Points

Chapter 14—NSN ASSIGNMENT BEFORE ACCEPTING DELIVERY & SHIPMENT

WITHOUT NSN 72

14.1. Purpose

14.2. Policy

Chapter 15—FOREIGN MILITARY SALES (FMS) 73

15.1. Purpose

15.2. Applicability

15.3. Impacted Data Systems

15.4. Policy and Procedures

Table 15.1. NC Number Assignment to Nonstandard Items

Chapter 16—REQUEST FOR HAZARDOUS MATERIALS (HAZMAT) IDENTIFICATION 80

16.1. Hazardous Materials (HAZMAT) Identification

16.2. Publication of Hazard Classification Data

16.3. Hazardous Materials Indicator Code (HMIC), which is based upon the Materiel Safety

Data Sheet (MSDS) is derived from the (HMIRS)

16.4. Responsibility

Chapter 17—USAF IMPLEMENTATION OF THE FEDERAL SUPPLY CLASSIFICATION

(FSC) AND USAF MATERIEL MANAGEMENT AGGREGATION

CODIFICATION (MMAC) 81

17.1. Purpose and Scope of the FSC and MMAC

17.2. Responsibilities

17.3. Procedures Applicable to New Items Requiring NSN Assignment

17.4. Procedures Applicable to New Items Submitted for NSN Assignment Which Match

Existing NSNs in an FSC Other Than the Requested FSC

17.5. Undelivered Contract Balances

17.6. FSC and MMAC Changes to Existing NSNs

17.7. Processing of FSC Change

Chapter 18—UNITED STATES AIR FORCE (USAF) MATERIEL IDENTIFICATION AND

PROVISIONING RELATIONSHIP 84

AFMCMAN23-3 14 SEPTEMBER 2010 7

18.1. Relationship

18.2. Responsibilities

18.3. Pre-proposal and Provisioning Guidance Conferences

18.4. PTD/SDFP/PSR Processing by the Air Force Provisioning Agent in DLIS:

Chapter 19—PRELIMINARY ITEM ENTRY CONTROL (IEC) SYSTEM (D155) 87

19.1. Purpose and Scope

19.2. General

19.3. Responsibilities

19.4. Interfaces

19.5. Edits

Chapter 20—OVERPRICING PROGRAM 89

20.1. Reference AFMAN 23-110, V7, P4 for overpricing program policy

Chapter 21—AUTOMATED DATA SYSTEMS IN SUPPORT OF USAF MATERIEL

IDENTIFICATION PROGRAMS AND OPERATIONS 90

21.1. The functions in D036 will be assumed in the Expeditionary Combat Sustainment System

(ECSS)

Chapter 22—D043 ITEM MANAGEMENT CONTROL SYSTEM (IMCS) 91

22.1. Purpose and Scope

22.2. Responsibilities

22.3. Types of Data

22.4. Data Increments

Table 22.1. IMCS Data by Increment

22.5. Data Validation and Compatibility Edits

Table 22.2. D043 Error Codes

22.6. Extract Data Retrieval

Chapter 23—D043A MASTER ITEM IDENTIFICATION DATABASE (MIIDB) 98

23.1. Purpose and Scope

23.2. Responsibility

23.3. User Registration

23.4. Databases

23.5. Types of Interrogation

23.6. FLIS Pass-through

23.7. Points of Contact (POC)

8 AFMCMAN23-3 14 SEPTEMBER 2010

Chapter 24—FLIS EDIT AND ROUTING SYSTEM (FERS OR D143C) 101

24.1. Purpose and Scope

24.2. General

24.3. Responsibilities

24.4. Edits

24.5. System Access

Chapter 25—TIME COMPLIANCE TECHNICAL ORDERS (TCTOS) 103

25.1. TCTO

Chapter 26—GOVERNMENT INDUSTRY DATA EXCHANGE PROGRAM (GIDEP) 104

26.1. GIDEP Background

26.2. Participating Activities

26.3. GIDEP Data Interchanges

26.4. Products

26.5. Responsibilities

Chapter 27—GOVERNMENT AND INDUSTRY REFERENCE DATA EDIT AND REVIEW

(GIRDER) PROCESSING 108

27.1. Background

27.2. General

27.3. Responsibilities

Chapter 28—MIL-HDBK-300/STANDARDIZED TECHNICAL INFORMATION FILE (TIF) OF

SUPPORT EQUIPMENT (SE) 110

28.1. Background

28.2. General

28.3. Definition of SE

28.4. Guidelines

28.5. SE Exclusions

28.6. Responsibilities

Chapter 29—SUPPORT EQUIPMENT RECOMMENDATION DATA (SERD) AND AF FORM

601, EQUIPMENT ACTION REQUESTS 112

29.1. Introduction

29.2. Background

29.3. SERD Responsibilities

29.4. AF Form 601, Equipment Action Request

AFMCMAN23-3 14 SEPTEMBER 2010 9

Chapter 30—AFMC PARTICIPATION IN THE DEFENSE STANDARDIZATION PROGRAM

(DSP) 117

30.1. Responsibilities

30.2. AFMC Organization for Standardization

Table 30.1. Standardization Directives and Publications Inclusions

Chapter 31—PROCESSING STANDARDIZATION DOCUMENTS 120

31.1. Initial Actions

31.2. Document Research

31.3. Acquisition of Commercial Products

31.4. Coordination of Standardization Documents

31.5. Quality Control Review

Chapter 32—STANDARDIZATION DOCUMENT RELATED ACTIONS 127

32.1. Safety Review of Standardization Documents

32.2. Standardization Document Identifier Numbers

32.3. PA Listings

32.4. Transfer of Standardization Documents

32.5. Overage Document Review

32.6. Canceled Standardization Documents

Chapter 33—OTHER STANDARDIZATION DOCUMENT SUBJECTS 130

33.1. Data Item Descriptions (DIDs)

33.2. Qualified Products List (QPLs)

33.3. Non-Government Standards (NGSs)

33.4. Non-ASSIST Documents

Table 33.1. Document Identifiers for Purchase Descriptions

33.5. ASSIST

33.6. Acquisition Streamlining and Standardization Information System (ASSIST)

33.7. SD-1

33.8. SD-4

Chapter 34—ITEM REDUCTION PROGRAM 136

34.1. Item Reduction Studies (IRS) Responsibilities

34.2. Procedures and Study Format

34.3. 401 SCMS and the AFGLSC/ALC Coordination

Table 34.1. Item Standardization Codes (ISC)

10 AFMCMAN23-3 14 SEPTEMBER 2010

Chapter 35—INTERNATIONAL MILITARY STANDARDIZATION AGREEMENTS 138

35.1. Responsibility for Participation

35.2. Standardization Agreements and Publications

35.3. Program Implementation

35.4. Publication Annotation Procedures

35.5. Agreement Deviations

Chapter 36—INTERCHANGEABILITY AND SUBSTITUTABILITY (I&S) PROGRAM 141

36.1. Purpose

Table 36.1. D043A Selected Data Screen ―I/S IND‖ Codes

Table 36.2. D043A X-File Relationship Code Table Code Explanation

Table 36.3. D043A X-File Incompatibility Code Table

36.2. Policy

36.3. Responsibility

Table 36.4. I&S Responsibilities

36.4. Research and Determinations

36.5. Records and Files

36.6. Processing of Inquiries and Resolution of Controversies

36.7. Generic NSN Management

36.8. Establishing an I&S Relationship

36.9. Examples of I&S Relationships

Figure 36.1. D043 J Increment

Figure 36.2. Interchangeable Relationship

Figure 36.3. Substitutable Relationship

Figure 36.4. Substitutable Relationship with JTC

Figure 36.5. NPPC 4

Figure 36.6. NPPC 9

Figure 36.7. Generic Relationship

Figure 36.8. Combination of Interchangeable and Substitutable Items

Figure 36.9. Combination of Interchangeable and Substitutable Items

37. Prescribed Forms

37.2. Adopted Forms:

Attachment 1—GLOSSARY OF REFERENCES AND SUPPORTIVE INFORMATION 158

AFMCMAN23-3 14 SEPTEMBER 2010 11

Chapter 1

CATALOGING AND STANDARDIZATION MISSIONS

1.1. Missions. The cataloging and standardization missions are essential elements of the overall

Air Force (AF) logistics system. While satisfying AF requirements, these missions are conducted in compliance with various Congressional mandates and Department of Defense

(DOD) manuals, e.g., the Federal Logistics Information System (FLIS) Procedures Manual, DOD 4100.39-M; the Defense Standardization Program Policies and Procedures Manual, DOD

4120.24-M; the Defense Integrated Materiel Management Manual for Consumable Items, DOD

4140.26-M, and DOD 4140.1-R DOD Supply Chain Materiel Management Regulation, aimed at providing for and operating an efficient military supply system.

1.2. Cataloging. AF cataloging operations are conducted within the framework of the Federal

Catalog Program (FCP). Under this program AF, together with the other military services and civilian agencies of the United States (US) Government, is required to maintain and use a single uniform cataloging system. For the DOD, the Defense Logistics Agency (DLA) is the administrator of the FCP and ensures required participation. The Defense Logistics Information

Service (DLIS) is the central operating point for the FCP. DLIS is responsible for releasing FCP publications and for the processing of item identifications with the related management data.

This includes assignment of all National Stock Numbers (NSNs) and maintenance of a complete central cataloging file (data bank). This file is identified as part of the Federal Logistics

Information System or the FLIS database, which is resident at the Defense Supply Center

(DSCC) in Columbus, OH. The computerized Federal Catalog System (FCS) is referred to as

―FLIS,‖ and includes item identification and supply information on items repetitively procured by the Federal Government. DLIS-K is the cataloging agent for the AF and is located in Battle

Creek MI.

1.2.1. Cataloging Processes. Cataloging of new items and maintenance transactions undertaken by Services and Agencies (S/A) result in the comprehensive logistics data Total

Item Record (TIR) required to identify, requisition, ship, store, dispose, or make other logistics decisions related to an item of supply during its lifecycle. This document represents internal AF processes that prepare an item for maintenance or initial cataloging. The transactional processes listed below were transferred to DLA. While DLA is responsible for these processes, the AF is responsible for the technical accuracy of the assignment and to challenge erroneously coded or items named incorrectly.

1.2.2. The Air Logistics Centers (ALC) , the Air Force Nuclear Weapons Center (AFNWC), and the Air Force Global Logistics Support Center (AFGLSC) are responsible for the following cataloging processes:

1.2.2.1. Item Entry Control (IEC). Item entry control is a process where the cataloging agent examines potential items for inclusion in the FCP. A determination is made by screening the part number (PN) of the candidate item with existing items to see if a previously existing item can used in its place. The previously existing item will be coordinated with the AF Equipment Specialist (ES) for acceptance.

1.2.2.2. Technical Data Validation. The process by which the quality of the available technical data is confirmed for purposes of Item Name assignment, Federal Supply

12 AFMCMAN23-3 14 SEPTEMBER 2010

Classification (FSC) determination, Item Entry Control (IEC), special characteristics, and the item identification (II).

1.2.2.3. Provisioning Screening Review and Support. Those actions taken to facilitate the best selection, procurement, and cataloging of items of supply required to sustain weapons systems and other government requirements (e.g., technical data validation, data calls, provisioning, guidance conferences, Logistics Support Analysis conferences, etc.).

1.2.2.4. Data Entry and Maintenance Transactions. Those actions necessary to ensure complete, accurate and current logistics data records (excluding item characteristics data) for an item of supply. Cataloging changes may be required because of an item manager

(IM) or equipment specialist decision/need to establish interchangeability and substitutability (I&S) relationships, Item Reduction Study (IRS) decisions, major item maintenance, Service catalog management data (CMD) updates, logistics reassignments, Base Realignment and Closure Commission (BRAC) actions, Defense Inactive Item

Program (DIIP), see DOD 4140.32-M at http://www.dtic.mil/whs/directives/corres/pdf/414032m.pdf; or disposal actions.

1.2.2.5. Cataloging Tools. The process of initiating and enhancing documents and procedures required to research, record, and organize logistics information.

1.2.2.6. Item Management Coding (IMC). The process of determining whether items of supply qualify for management by the military Services, rather than by DLA or General

Services Administration (GSA), according to DOD 4140.26-M, Defense Integrated

Material Management Manual for Consumable Items at http://www.dtic.mil/whs/directives/corres/html/414026m.htm.

1.2.2.7. Supply Support Request (SSR) processing. A request by a S/A making them a user of a consumable/field repairable item managed by another S/A. These actions are outlined in the AFMAN 23-110, USAF Base Supply Manual, at http://www.e-publishing.af.mil/shared/media/epubs/afman23-110.pdf.

1.2.2.8. Data Dissemination. Various products and events provide logistics information to customers at every level of the supply system.

1.2.2.9. Item Name Assignment. Designation of a noun or noun phrase to an item of supply that answers the question ―what is it?‖ Based upon subsequently available technical data and ongoing tool development, an item name may be refined after stock list action. DLIS is ultimately responsible for ensuring the FSC and item name is assigned in accordance with DOD 4100.39-M, Volume 3.

1.3. Standardization. AF standardization operations are conducted primarily within the framework of the Defense Standardization Program (DSP) and in accordance with DOD

4120.24-M, DOD Defense Standardization Program Policies and Procedures Manual. The main objectives are to achieve and maintain the highest practicable degree of standardization for items, materiel, practices, procedures, and terminology by preparing standardization documents.

In addition to participating in the DSP, the AF standardization mission entails the conduct of, and participation in, various other related programs and projects, including International

Standardization Programs, Non-Government Standards (NGS) Bodies, Parts Control Programs, and Overpricing Programs.

http://www.dtic.mil/whs/directives/corres/pdf/414032m.pdf http://www.dtic.mil/whs/directives/corres/html/414026m.htm http://www.e-publishing.af.mil/shared/media/epubs/afman23-110.pdf http://www.e-publishing.af.mil/shared/media/epubs/afman23-110.pdf

AFMCMAN23-3 14 SEPTEMBER 2010 13

Chapter 2

RESPONSIBILITIES

2.1. General. All AF activities and their personnel, including contracted agents/entities, are responsible for ensuring that:

2.1.1. The policies and procedures outlined herein are implemented and enforced.

2.1.2. Data in the Item Management Control System (IMCS) and FLIS is current, accurate, and complete. Authorized official AF CMD resides in IMCS. Other AF systems may hold or display such data, but those systems are not recognized as the legitimate, authoritative source for AF CMD.

2.1.3. The IMCS (e.g., D043, D043A, D043B, and D143C) is the only officially sanctioned source of entry and storage for AF cataloging and certain other logistics management information. The IMCS records logistics data in the FLIS.

2.2. Specific Areas of Responsibility.

2.2.1. The AFGLSC‘s 401 SCMS will manage AF requirements pertaining to FCS publications and will assign a Federal Cataloging Committee (FCC) member to represent the

AFGLSC.

2.2.2. Headquarters (HQ) United States Air Force (USAF)/A4L Supply Division serves as the Air Staff channel for the FCP as well as I&S issues when there is interaction between HQ

AFMC and the Secretary of the AF or Secretary of Defense offices.

2.2.3. HQ AFMC/A4R will develop policies for the IMCS and standardization mission;

whereas, the AFGLSC will implement the policy and provide staff direction and control.

2.2.4. HQ AFMC/A6 and 754

th

Electronics Logistics Systems Group (ELSG) will develop and maintain data automation and telecommunication support for AF participation in, interface with, and supplementation of the FCP and standardization programs.

2.2.5. The Program Offices, which acquire and modify systems, will provide the oversight for contractors performing materiel management responsibilities to ensure the Federal

Catalog Program actions are accomplished and the contractor is in compliance with Public

Law (PL) 436, Title 10, United States Code, and Section 487, Title 40, United States Code.

2.3. Cataloging and Standardization Maintenance Transactions. The cataloging agents in

DLIS-K, the DLA activity contracted to perform AF cataloging and standardization transactions are located in Battle Creek, MI. Other mission-unique AF activities perform cataloging and standardization functions and submit transactions as outlined in Chapter 10.

2.4. ALC/AFGLSC/Contractor ICP Responsibilities. The ALC, AFGLSC item management/system management organizations, and contractor ICPs are responsible for performing logistics support services and item management functions for specific items, FSCs, subsystems, equipment, assemblies, and components as assigned by HQ AFMC.

Responsibilities require that the ALC/AFGLSC/Contractor ICPs provide current focal points and phone numbers for the IMCS.

14 AFMCMAN23-3 14 SEPTEMBER 2010

PART 2

FEDERAL CATALOGING PROGRAM (FCP)

Chapter 3

BASIC PRINCIPLES, METHODS, AND TOOLS

3.1. Introduction. The FCP was established in 1952 by Public Law 82-436 (Title 10, US Code, Chapter 145) to provide complete, accurate, and current item of supply information to support

DOD operational readiness. This chapter provides information on the applicable FCP principles and concepts, the data system that supports the FCP, and the availability of FCP information.

3.1.1. The FCP:

3.1.1.1. Provides a uniform system of II.

3.1.1.2. Improves the operational effectiveness of DOD components.

3.1.1.3. Provides a means for monitoring the minimum number of items essential to support military operations.

3.1.1.4. Assembles and maintains a central catalog file.

3.1.1.5. Prevents duplication of items of supply.

3.1.1.6. Supports standardization.

3.1.1.7. Records I&S decisions.

3.1.1.8. Furnishes supply catalog publications to logistics users.

3.1.1.9. Promotes optimum interchange of FCP data.

3.1.1.10. Assists in assuring the highest practical level of systems capability, interface, and integration.

3.1.2. The FCP expanded, from the basic function of establishing II, to include other logistics data that supports the disciplines of supply chain management, FSC, and DOD logistics management. The AF is a full participant in the FCP and subscribes to its principles and concepts.

3.2. Basic Principles.

3.2.1. Item Identifications (II). Under the FCP, the concept of each item of supply is described by an II. The II is made up of data sufficient to establish the essential characteristics of the item, which gives it its unique character, makes it what it is, and differentiates it from every other item of supply used by the Federal Government.

3.2.2. Principles of Item Identification. Each II is applicable to one, and only one, item of supply. Each item of supply is applicable to one, and only one, II.

3.2.3. Item of Production and Item of Supply. An item of production consists of one or more pieces or objects produced by a manufacturer, which must conform to the same engineering drawing or specification. The item of production is assigned a PN by the manufacturer and is sold by the manufacturer. On the other hand, the item of supply is purchased by the

AFMCMAN23-3 14 SEPTEMBER 2010 15

government, cataloged by the government, assigned an NSN by the government and supplied to government users. An item of supply may be:

3.2.3.1. A single item of production.

3.2.3.2. Two or more items of production that are identical in terms of form, fit, and function.

3.2.3.3. A more precise quality-controlled item than a normal item of production.

3.2.3.4. A modification of a normal item of production.

3.2.4. The FCP is based upon an item of supply concept, which is government controlled as opposed to an item of production concept, which is manufacturer controlled.

3.3. Federal Supply Classification (FSC) System. The FSC System is sufficiently comprehensive in scope to permit the classification of all items of personal property. In order to accomplish this, groups and classes have been established for the universe of commodities, with emphasis on the items known to be in the supply system of the federal government. This classification system, with its present structure of groups and classes, represents those groupings and relationships that are based on current, as well as anticipated future, management needs. The

FSC structure of groups and classes is defined in the Cataloging Handbook H2-1, Federal Supply

Classification, Groups and Classes, and H6, Federal Item Name Directory. The H6 includes

Approved Item Names (AIN), colloquial names, FSCs, Condition Codes, Federal Item

Identification Guides (FIIGs), and definitions.

3.4. Procedures.

3.4.1. The AFGLSC‘s 401 SCMS is the OPR for processing and reviewing all AF initiated

DD Forms 180, Item Name Collaboration Action Request, and other military S/A initiated

DD Forms 180 received from the DLIS for coordination.

3.4.2. Initiating activities will submit a letter requesting the establishment or revision of cataloging tools to the AFGLSC‘s 401 SCMS. Supporting data, such as drawings, specifications, manufacturer‘s catalogs, etc., will be attached to the letter to assist in the revision or development of the cataloging tools. The letter will specify whether the request is required for identifying new items of supply or for the revision of existing IIs and provide justification for the proposal.

3.4.2.1. If applicable, the DD Forms 180 will be forwarded to the appropriate AF center for their review and input.

3.4.2.2. Comments and recommendations received from the ALC/AFGLSC will be consolidated by the AFGLSC‘s OPR in the 401 SCMS and forwarded to DLIS.

3.4.3. The AFGLSC‘s 401 SCMS functional OPRs will review each request for new or revised cataloging tools, forward copies of the proposed cataloging tools to DLIS, or return them to the initiating activity with full justification and what action to take in identifying the item of supply involved.

16 AFMCMAN23-3 14 SEPTEMBER 2010

3.5. Federal Item Identification Guides (FIIG) Program.

3.5.1. Objectives: To establish guidelines for use in developing a single identification record, in a machine-readable format, for multiple logistics purposes and to provide a means for instant retrieval of the data.

3.5.2. Responsibilities:

3.5.2.1. The AFGLSC‘s 401 SCMS will:

3.5.2.1.1. Provide input to HQ AFMC/A4R on policy/procedural guidance for overall program implementation and control within the AF.

3.5.2.1.2. Serve as the USAF monitor for resolution of problems relative to Item

Name assignment, FSC assignment and the FIIG program in conjunction with other

S/A HQ elements.

3.5.2.1.3. Serve as the USAF POC for System Change Requests received from the

DLIS in support of the FLIS.

3.5.3. Procedures: DOD 4100.39-M, Volume 3 Development and Maintenance of Item

Logistics Data Tools, and Volume 4 Item Identification, prescribe specific detailed procedures for implementing the FIIG program. DOD and AF manuals and instructions are supplemented by detailed operating instructions at each ALC, and the cataloging agent for the AF depending upon individual requirements.

3.6. Special Rules Applicable to the Compilation and Publication of the Subsistence

Electronic Catalogs (Foodnet (C8900-SL), NAPA, SPVIA, LSN, and Market Ready

Catalogs.

3.6.1. The Commander, Defense Personnel Support Center (DPSC), is responsible for the compilation, maintenance, and printing of this publication and bulk distribution to the military services.

3.6.2. AF Clothing and Textile Office (AFC&TO/DSCP-QPAC) is responsible for AF additions, deletions, and changes to this publication.

AFMCMAN23-3 14 SEPTEMBER 2010 17

Chapter 4

FEDERAL LOGISTICS INFORMATION SYSTEM (FLIS) PROBLEM REPORTING

AND SYSTEM CHANGE REQUESTS (SCR)

4.1. Purpose. This chapter provides the procedures to report and submit FLIS Problem Reports and SCRs for all AF activities. Only one responsible AF contact point is recognized by the DLA and DLIS. All FLIS Problem Reports and SCRs must be submitted through the AF designated contact point.

4.2. SCR Reference: DOD 4100.39-M, Volume 1, Chapter 5, FLIS Change Procedures at http://www.dlis.dla.mil/flis_procedures.asp.

4.3. Contact Points. All AF submittals (e.g., DD Form 2029, Defense Integrated Data System

(DIDS) Problem Report and DD Form 2021 and DD Form 2021-1, DIDS Change Requests) must be made through a local activity focal point prior to submission to the AF FLIS contact point. Note: Referenced DD Forms 2029, 2021, and 2021-1 are electronic forms.

4.3.1. The designated AF FLIS contact point: AFGLSC‘s 401 SCMS.

4.3.2. Each of the following activities must appoint a local FLIS focal point:

4.3.2.1. Air Force and DeCA Integrated Customer Team, DSCP/QPAC.

4.3.2.2. Cryptologic Systems Group (CPSG/LGLP).

4.3.2.3. AF Civil Engineering Support Agency (AFCESA/CEO).

4.3.2.4. AF Medical Operations Agency, Medical Logistics Division (AFMOA/SGAL).

4.3.2.5. AF Pentagon (USAF/A4L).

4.3.2.6. Brooks AFB (USAFSAM/OEMB).

4.3.2.7. Maxwell AFB, Gunter Annex (754

th

ELSG).

4.3.2.8. Each AFGLSC location:

4.3.2.8.1. 418 SCMS at Ogden AFB, UT (OO-ALC).

4.3.2.8.2. 420 SCMS at Tinker AFB, OK (OC-ALC).

4.3.2.8.3. 406 SCMS at Warner Robins AFB, GA (WR-ALC).

4.3.2.8.4. Each Contractor Supported Weapon System (CSWS) OPR

4.3.2.9. All other activities will submit through the office responsible for cataloging and standardization functions.

4.3.3. HQ AFMC or other MAJOMs may have a need to submit problem reports or SCRs.

These activities may submit their requirements directly to the AFGLSC‘s 401 SCMS.

4.4. Submittal of FLIS Problem Reports.

4.4.1. Upon identification of a problem or a potential for one, and prior to submission to the

AF FLIS contact point, the reporting activity will perform thorough research and analysis to try to resolve the problem at the local level.

http://www.dlis.dla.mil/flis_procedures.asp

18 AFMCMAN23-3 14 SEPTEMBER 2010

4.4.2. If, after all areas of research have been exhausted and the problem still exists, the AF activity will report the problem to the AFGLSC‘s 401 SCMS. The AFGLSC‘s 401 SCMS focal point will document the problem and forward to DLIS.

4.4.3. The following data is required for the FLIS Problem Report:

4.4.3.1. Transaction Document Control Numbers, as applicable.

4.4.3.2. NSNs, NIINs, permanent system control numbers (PSCN), or system control numbers (SCN), as applicable.

4.4.3.3. Input or output DICs, as applicable.

4.4.3.4. Date transactions transmitted to (from) the cataloging agent for the AF.

4.4.3.5. Problem Description. Describe, in detail, all information relating to the problem.

Supplement with any internal research data or recommendations. Include examples of input and output transactions when available.

4.4.4. The AFGLSC‘s 401 SCMS will provide the initiator with periodic status reports and notification of problem resolution.

4.5. SCR Procedures.

4.5.1. AF Initiated SCRs:

4.5.1.1. Proposed changes to FLIS must be submitted through your local activity focal point to the AFGLSC‘s 401 SCMS by letter, E-mail or telephone and should include:

4.5.1.1.1. Brief description of the requirements or problem;

4.5.1.1.2. Impact and urgency;

4.5.1.1.3. Recommended change;

4.5.1.1.4. General and specific objectives the change should meet;

4.5.1.1.5. Scope of interest to other customers;

4.5.1.1.6. Anticipated benefits--both tangible (dollar savings) and intangible

(improved support);

4.5.1.1.7. Focal point, initiator, or person having technical background to answer questions and be able to recommend a solution; and

4.5.1.1.8. Initiators must follow-up telephone requests with written documentation.

4.5.1.2. Local activity focal point will:

4.5.1.2.1. Screen proposed SCRs.

4.5.1.2.2. Forward valid proposals to the AFGLSC 401 SCMS.

4.5.1.3. The AFGLSC‘s 401 SCMS will:

4.5.1.3.1. Assign an AF control number.

4.5.1.3.2. Coordinate with other AF activities affected by the proposal.

AFMCMAN23-3 14 SEPTEMBER 2010 19

4.5.1.3.3. Develop an AF position and approve or disapprove further SCR processing.

4.5.1.3.4. Return disapproved SCRs to initiator with justification.

4.5.1.3.5. Forward approved SCRs to other S/A for coordination.

4.5.1.3.6. Forward approved SCRs to DLIS-S for further processing.

4.5.1.3.7. Provide guidance when the SCR affects current policy or establishes new policy.

4.5.2. Other S/A initiated SCRs:

4.5.2.1. The AFGLSC‘s 401 SCMS will:

4.5.2.1.1. Receive SCRs for review.

4.5.2.1.2. Request comments, cost, and benefit data from the local activity focal points, other interested AF activities, and AF Data Systems OPRs whose systems may be affected by the change.

4.5.2.1.3. Develop an AF position, resolving any conflicts.

4.5.2.1.4. Forward DD Form 2021 and DD Form 2021-1 to DLIS stating the AF position.

4.5.2.1.5. Notify focal points and data system OPRs of scheduled implementation dates when SCR is approved for implementation (see Table 4.1).

4.5.2.2. Local activity focal point and data systems OPR will review the SCR and provide comments and cost benefit data to the FLIS monitor by the requested suspense date. Suspense dates will vary. Allow a minimum of 30 days for routine processing.

Emergency and expedite processing will be E-mailed when possible. If a response is not received by the suspense date, the FLIS contact point will assume no interest and no further notification will be sent to that activity.

Table 4.1. System Change Request Processing Timeframes.

SCR Priority Minimum Number of Days to Implement

Emergency No minimum, 30 days maximum

Expedite 198 days

Routine *475-575 days

*Note: SCRs affecting only one S /A can often be implemented within a year. Controversial

SCRs may take several years to implement.

20 AFMCMAN23-3 14 SEPTEMBER 2010

PART 3

PREPARATION AND PROCESSING OF ITEM IDENTIFICATIONS (IIS) AND

RELATED DATA

Chapter 5

PREPARATION OF FEDERAL CATALOGING SUBMITTALS

5.1. General. Cataloging actions are processed by the Federal FLIS as a result of inputs prepared via the D143C or special project and released by the AF cataloging agent, Contractor

ICP‘s, or AFMC data systems. The DOD 4100.39-M, FLIS Procedures Manual, contains specific formats for each input transaction. FCP transactions fall into two categories:

5.1.1. Requests to FLIS for NSN assignment on new items of supply entering the inventory.

5.1.2. Revisions to update data elements and item identifications within FLIS for existing

NSNs.

5.2. Guidelines for Preparing and Submitting Item Identifications (II) and Revisions.

5.2.1. The procedures outlined in DOD 4100.39-M, FLIS Procedures Manual are used for preparing all new item entries, revisions, and Item Identification Improvements (III), a revision to upgrade management data and characteristics information.

5.2.2. All weapon system and technology group related items will be identified with a

Materiel Management Aggregation Code (MMAC); a two-position alphabetic code (AA to

ZZ) authorized to identify specific systems, programs, aggregations of equipment, or an activity providing engineering support authority (ESA). See https://d086.wpafb.af.mil/ for more information.

5.2.3. Forward requests for suggested changes to DOD 4100.39-M, special processing of data, and other actions not covered by existing procedures to the AFGLSC‘s 401 SCMS.

Forward requests for revisions to, or establishment of, a new FIIG, a change in FSC, reference drawing groups, and item names to the AFGLSC. (See also Chapter 3 of this manual.)

5.3. Forms. The following forms apply to various cataloging actions by AF activities:

5.3.1. AF Forms 86, Requests for Cataloging Data/Action. A hard copy form is used, for a small number of AF cataloging requests, when the requested cataloging actions cannot yet adequately be identified by submission of a request using the D143C System. While hard copy AF Forms 86 are allowed, they are highly discouraged because after they are input into the D143C system, the initiator will not get system generated notifications of status (i.e.

concurrence, non-concurrence, etc.). The preferred electronic method of submitting AF

Forms 86 into the D143C System will provide automated status of the request to the initiator.

Special projects may be initiated for mass changes by contacting the AFGLSC‘s 401 SCMS through your local cataloging focal point.

5.3.2. DD Form 1685, Data Exchange and/or Proposed Revision of Catalog Data. This form provides a mechanism for requesting cataloging actions between all S/As. S/A‘s cataloging agent may use this form to initiate a NSN item identification or CMD data review of an item managed by another S/A. This form is not used by, or to collaborate between the https://d086.wpafb.af.mil/

AFMCMAN23-3 14 SEPTEMBER 2010 21

ALCs, Contractor ICPs, or any forward Operating Location (OL) within the AF which is detached from the submitter geographically.

5.4. Preparation of Cataloging Actions for Transmittal to the FLIS.

5.4.1. Federal cataloging submittals are prepared by the responsible cataloging activities, as applicable, based on DOD 4100.39-M, FLIS Procedures Manual requirements. D143C is programmed to format submittals in the manner prescribed by the FLIS manual.

5.4.2. Transactions may be input to FLIS by the AF‘s Cataloging Agent through the D143C on –line process.

5.5. Obtaining Commercial and Government Entity (CAGE) Codes. Parts 204, 212, and

252 of the Defense Federal Acquisition Regulation Supplement (DFARS) have been amended to require contractor registration in the DOD Central Contractor Registration (CCR) database prior to award of any contract, basic agreement, blanket ordering agreement or blanket purchasing agreement. Just having a CAGE Code alone no longer suffices to qualify a contractor to do business with DOD.

5.6. Request for Special Processing of Federal Cataloging Submittals. In the event a significant volume of similar cataloging actions are required, the nature of which warrants control, group identification, or both, a request submitted to the attention of the AFGLSC‘s 401

SCMS special projects monitor will ensure efficient, timely processing of those cataloging actions through the D143C data system.

22 AFMCMAN23-3 14 SEPTEMBER 2010

Chapter 6

NON-DEFINITIVE (ND) NUMBER AND KITS ―K‖ PROCESSING

6.1. Purpose. This chapter provides guidance and direction for the assignment of ND numbers and kits. It defines what ND numbers and kits are and when they are to be used. It defines when

ND numbers must be deleted or stock list action initiated for NSN assignment. The IMCS

D043A/D143C, are the only official, sanctioned sources of entry and storage for AF ND and K numbers. This chapter assigns responsibilities to the ALCs, AFGLSC, Contractor Supported

Weapon System (CSWS) Programs, 401 SCMS and D143C.

6.2. Definition and Use of Non-Definitive (ND) Control Numbers.

6.2.1. ND control numbers are assigned by the D143C as the result of an ALC, AFGLSC or

CSWS activity IM or ES action to:

6.2.1.1. Identify items considered to be non-logical spares

(Expendability/Recoverability/ Reparability/Category Code (ERRC Code) ―N‖ only).

These items are procured on a one-time basis for shipment of assets to support a part number requisition (PNR), manufacture, cannibalization, or to show custody in support of an operational requirement.

6.2.1.2. Establish controls within AF systems for one-time buys.

6.2.1.3. Support special projects authorized by the Non-Definitive Waiver Authority

(NDWA).

6.2.1.4. Support non-standard one-time buys in support of a Foreign Military Sales

(FMS) requirement.

6.2.2. ND numbers are temporary control numbers, not to exceed one year, and are used for asset accountability and visibility. They do not replace NSNs.

6.2.3. ND numbers cannot be assigned to existing stock listed items.

6.2.4. ND numbers cannot be included in an Interchangeability and Substitutability Group

(I&SG) nor can a group be created using ND numbers.

6.2.5. ND numbers cannot be stocked and stored at the wholesale level, except for local manufactured items to support depot maintenance or parts cannibalized from a condemned or over-assembled next higher assembly (NHA).

6.2.5.1. Retail can temporarily stock, store and issue ND numbered items as bench stock to support depot maintenance.

6.2.5.2. If a requirement changes, and an ND numbered item needs to be stocked, stored, and issued from supply on a regular basis, the ND one-time buy status will be deleted and the appropriate action taken to obtain an NSN for the item.

6.2.6. An ND number requiring follow-on support will be assigned a NSN, including FMS non-standard ND items.

AFMCMAN23-3 14 SEPTEMBER 2010 23

6.2.7. The ERRC code "N" is the only authorized ERRC code allowed on ND numbers. If an ND transitions to an NSN, the ERRC code will be assessed and applied at the time of the request for NSN assignment.

6.2.8. Budget Code ―9‖ is not authorized for use on an ND number. The Budget Code should be assigned in accordance with the D043A Data Element Edit Table (DEETS). CSWS will continue to assign Budget Code S.

6.2.9. ND numbers cannot be assigned to Support Equipment (SE). SE must be identified by

NSNs. Exception: An Air Staff or HQ AFMC downward directed program to procure unique SE.

6.2.10. Retail excess ND-number-identified materiel will be disposed of at the local level unless the AF ND Item Manager (NDIM) authorizes shipment to a depot or another location with a requirement meeting one of the conditions of paragraph 6.2.1.1

6.3. HQ AFMC ND Policy. HQ AFMC/A4R will establish and maintain ND Number policy and the ND Unit Check Inspection (UCI).

6.4. Air Logistics Centers (ALCs)/AF Global Logistics Support Center (AFGLSC) and

Contractor Supported Weapon Systems (CSWS) Programs will:

6.4.1. Assign ND focal points NDFP/NDWA to approve and fully justify assignment of all

ND numbers resident in the D143C footprint with release authority, as well as act as the

NDWA. Note: The NDFP may also act as the NDWA, but the NDIM will never act as the

NDFP or NDWA.

6.4.2. Use D143C to establish and control all ND Numbers.

6.4.3. Authorize assignment of ND numbers to all special projects

6.4.4. Exercise waiver authority, i.e., respond to a request for a single, longer period - more than two 180 day periods – before ND termination or transition to NSN.

6.4.5. Receive all waiver requests consisting of a written statement documenting the need for a waiver to be assigned to an ND number or related group of ND numbers in support of a special project. The request must be in writing to the NDWA. The waiver request will contain:

6.4.5.1. All nouns (approved and non-approved item names), CAGE codes, PNs associated with the ND number.

6.4.5.2. A sound justification for requesting the waiver.

6.4.5.3. The date for completion of the special project and/or expiration date of the waiver.

Note: A request without a completion date or stating an ―indeterminate time‖ will be returned to the requestor and the ND number will be deleted unless the requestor can provide a definitive date.

6.4.6. Implement internal control procedures to assure only qualified ND items are assigned and retained.

24 AFMCMAN23-3 14 SEPTEMBER 2010

6.4.7. The assigned NDIM will review all ND numbers present on their D143C workbench, on or about the 165-day point and identify, prior to the end of the 180-day cycle, those items for:

6.4.7.1. Possible NSN assignment and the deletion of the ND number.

6.4.7.2. Extension for an additional 180-day cycle.

6.4.8. At the time of the first 180 and second 180-day review, NDIM will check D035A for open procurement, which is a backorder, asset or requisition. If D035A reflects an open procurement during the first 180-day review, the NDIM will direct the users to maintain or wavier the ND number. If during the second 180-day review D035A reflects an open procurement, the NDIM will proceed with either a request for NSN assignment or an extension to the ND by requesting a waiver.

6.4.9. If a second 180-day cycle is requested, the NDIM will receive notification by the

D143C to review ND numbers for stock list action. Once notified, the NDIM is required to extend, delete or request an NSN for the ND number. This decision is required prior to the end of the second 180-day cycle. Failure will result in the deletion of the ND number.

6.5. ND Item Manager will:

6.5.1. Authorize shipment of retail excess ND number-identified materiel to a depot or another location with a requirement meeting one of the conditions of paragraph 6.2.1.1 in lieu of disposal at local level. Request NSN assignment using D143C to all ND numbers having follow-on support conditions including FMS nonstandard ND items or when the requirement for the item is such that it will remain though the failure/demand rate is infrequent.

6.5.2. Review CMD for correct ERRC code while providing NC screen mandatory data.

6.5.3. Apply corresponding IMC. ERRC codes N and P in this situation may carry IMC L.

CSWS will continue to apply IMC B.

Note: The NDIM may request NSN assignment or ND termination at any time during the ND process.

6.6. D143C Process and Control of NDs. D143C is the ―gatekeeper‖ for ND process.

6.6.1. Prior to ND number assignment, D143C will screen the CAGE/PN to ensure the item is not stock listed (NSL) or an ND/NC was not previously assigned.

6.6.1.1. If the CAGE code and PN is not identified to another ND, NC, or NSN, D143C will continue with the ND process.

6.6.1.2. If the CAGE code and PN is identified to an ND, the D143C will move/forward the NDIM to the NC screen to request NSN assignment (based on two different needs being made known).

6.6.1.3. If the CAGE code and PN is identified to an existing NC or NSN, do not assign

ND.

6.6.2. D143C will track the ND number and place it on the NDIM's workbench at the 165-day mark, prior to first 180 days expiration for review and decision (see paragraph 6.4.7).

AFMCMAN23-3 14 SEPTEMBER 2010 25

6.6.2.1. D143C will respond to the NDIM's decision by:

6.6.2.1.1. Canceling the ND number and notifying the NDFP.

6.6.2.1.2. Directing the NDIM to the NC processing screens.

6.6.2.1.3. Forwarding the…