Army Pamphlet 708-3

24 June 2015

UNCLASSIFIED

Cataloging of Supplies and Equipment

Cataloging of Supplies and Equipment, Army Adopted Items of Materiel, and List of Reportable Items (SB 700-20)



SUMMARY of CHANGE

DA PAM 708-3
Cataloging of Supplies and Equipment, Army Adopted Items of Materiel, and List of Reportable Items (SB 700-20)

This major revision, dated 24 June 2015--

* Adds reportable item control code definition (para 3-18).

* Adds supply category of materiel definition (para 3-22).



Chapter 1
Introduction

1-1. Purpose

This pamphlet explains the procedures to prepare, update, and maintain SB 700-20. It also covers information concerning SB 700-20 line item number (LIN) actions affecting authorization documents; the preparation of data, including national stock numbers (NSNs) and nomenclatures required to support the Army type classification program; and the processing of commercial non-type classified items for NSN and LIN assignment.

1-2. References

See appendix A .

1-3. Explanation of abbreviations and terms

See glossary .

1-4. Concept

a. SB 700-20 is updated to provide a list of Army adopted items and other selected items and is used in conjunction with the following Department of the Army (DA) publications:

(1) AR 70-1 .

(2) AR 71-32 .

(3) AR 200-1 .

(4) AR 220-1

(5) AR 700-142 .

(6) AR 710-2 .

(7) AR 710-3 .

(8) DA PAM 708-2 .

(9) DA PAM 700-142 .

b. SB 700-20 also identifies items assigned reportable item control code (RICC) 2 and is the guide for all units, organizations, and installations responsible for furnishing reports as prescribed by AR 710-3 .

c. SB 700-20 is updated during the open period. A current SB-700 is released monthly on the first of the month. LIN data changes take effect the first day of each month. SB 700-20 is to be used in obtaining specific data relating to the Army Authorization Documents System (TAADS), the Army type classification program, and the Logistics Management Control Data, delineating the following information:

(1) LIN.

(2) Generic and NSN nomenclature.

(3) Type classification code and RICC. Except for the type classification code, these data elements are use to update the Army master data file (AMDF) contained in Federal Logistics Data on Portable Media (FED LOG) for compatibility with SB 700-20. The Army Enterprise Systems Integration Program (AESIP) is the source of FED LOG data, which is the primary source of AMDF information for Army customers worldwide.

d. In order to ensure that a request is published during the monthly SB 700-20 cycle, the U.S. Army Materiel Command (AMC) Logistics Support Activity (LOGSA) must receive the AESIP request for addition to SB 700-20 staffing action by the fifteenth of each month.

e. In SB 700-20, an asterisk preceding the LIN or NSN annotates additions or changes to LINs and NSNs.

f. The Headquarters, Department of the Army (HQDA) authorized portal database, Standard Study Number-Line Item Number Automated Management & Integrating System (SLAMIS) ( https://www.slamis.army.mil ), is the HQDA authorized request entry point for all SB 700-20 updates to AMC LOGSA.

(1) The only items that are deleted are those that do not have requirements and authorizations listed in the latest

(a) Army Materiel Plan (AMP).

(b) Total Army Equipment Distribution Program.

(c) Structure and Composition System output.

(d) Common table of allowances (CTA).

(e) TAADS.

(f) Basis of issue plan (BOIP).

(g) Table of organization and equipment (TOE).

(2) If a LIN is to be deleted and it appears in TAADS, TOE, BOIP, CTA, modified table of organization and equipment (MTOE), table of distribution and allowances (TDA), and the Joint table of allowances (JTA), the following apply:

(a) The responsible LIN proponent (materiel developer) interacts with the requirement and authorization document proponent to have the LIN removed from the document. If BOIP has been established, coordination action is taken with the U.S. Army Training and Doctrine Command, as well as with AMC and the U.S. Army Force Management Support Agency (USAFMSA).

(b) If the requirement/capability still exists, a suitable replacement item is determined. The replacement LIN appears in an active chapter of SB 700-20. The deleted LIN, with its replacement LIN, is added to appendix E . Conversion to the replacement(s) can then be made in all affected TOE, BOIP, MTOE, TDA, JTA, and CTA documents.

(3) Delete type classified items by reclassifying the items as obsolete or terminating the type classification.

(4) AMC LOGSA coordinates with USAFMSA before any NSN or LIN is deleted from SB 700-20, chapter 6.

(5) HQDA approval is required before the last NSN under a generic LIN is deleted because this action requires removing the LIN.

g. All changes to the following SB 700-20 data elements are derived from automated processing of SB 700-20 maintenance transactions from authorized data originators:

(1) LIN.

(2) RICC.

(3) Controlled item code (CIC).

(4) Generic nomenclature.

(5) NSN nomenclature.

(6) Logistics control code (LCC).

(7) Army type classification code.

(8) Materiel status committee record (MSCR) number.

(9) Material Status Record Reference data.

(10) Commodity manager code (CMC).

(11) Type fuel consumption code.

(12) Procurement appropriation commercial item (PCI) code.

(13) Substitute line item number (SUB-LIN).

h. The SB 700-20 LIN, RICC, generic nomenclature, NSN nomenclature, and LCC will be used to update the Army Central Logistics Data Bank (ACLDB) (Army Enterprise Material Master (AEMM)). See table 1-1 for a list of authorized SB 700-20 data submitters.

i. All SB 700-20 updates to the following data elements are obtained from the AEMM:

(1) NSN.

(2) Unit of issue (UI).

(3) Appropriation and budget activity (ABA) account code (position 2 of the materiel category structure code) (see AR 710-1 or DA Pam 708-2 ).

(4) Supply category of materiel (SCM) code.

(5) Unit price.

j. These procedures ensure that data for Army managed and/or Army used items included in SB 700-20 are compatible with the data recorded for the NSN in the AEMM. There must be an active item data segment in the AEMM for any national item identification number (NIIN) being added to SB 700-20; otherwise, the transaction will be rejected.

k. An NSN can be listed in SB 700-20 under only one LIN. When a BOIP is established for a type classified item combined with other items, the combination of these items is treated as an assemblage. This combination is assigned its own LIN, generic nomenclature, and NSN.

l. Conversely, a new LIN, NSN, and generic nomenclature are assigned to assemblages that have had major procurement appropriation items removed. Major procurement appropriation support items removed from assemblages are assigned a separate LIN and are authorized and documented separately in TAADS and documented separately in TOE.

m. All items shown in SB 700-20 under a separate LIN represent separate end items that are or may be separately authorized. They cannot be deleted solely on the basis that they are also a component of a set or assemblage.

n. For type classified materiel

(1) Items requiring a separate BOIP are listed in SB 700-20, chapter 2.

(2) LINs not requiring Army type classification are listed in SB 700-20, chapter 6.

(3) Equipment authorized by CTA is listed in SB 700-20, chapter 8.

(4) Developmental (research, development, test, and evaluation (RDTE) by the Army) and nondevelopmental (no expenditure of Army RDTE funds) items awaiting type classification decision are included in SB 700-20, chapter 4.

(5) Items reclassified as obsolete or items for which type classification has been terminated are shown in SB 700-20, appendix E, prior to being moved to the SB 700-20 history file.

(6) NSNs are retained in SB 700-20, appendix E, for 1 year; LINs for 3 years.

o. The AEMM 3.2 non-standard line item number capability solution is now the production portal link, https://www.aesip.army.mil/irj/portal , on the AESIP portal.

Table 1-1. Authorized SB 700-20 data originators
Originator code Routing identifier code Commodity manager code Management activity
AJ A12 B U.S. Army Soldier and Biological Chemical Command
AM B69 C U.S. Army Medical Materiel Agency
AT BAM X U.S. Army Simulation Training and Instrumentation Command
AZ AKZ K U.S. Army Tank-Automotive and Armaments Command Life Cycle Management Command
BD B64 L U.S. Army Aviation and Missile Command
BF B14 M, D U.S. Army Tank-Automotive and Armaments Command Life Cycle Management Command
CA AP5 F,S U.S. Army Troop Support Activity, Philadelphia
CD A35 E, J, Q, R, T U.S. Army Petroleum Center
CL B16 G U.S. Army Communications-Electronics Command
CT B17 H U.S. Army Aviation and Missile Command
BS F56 W U.S. Special Operations Forces Activity
BS H9D W U.S. Special Operations Command

Chapter 2
Content and Format of SB 700-20

2-1. Overview

This chapter provides an outline of SB 700-20, with explanations of each of its chapter's contents. Chapters 3, 5, and 7 of SB 700-20 have been deleted.

2-2. SB 700-20, Chapter 1, Introduction

As a minimum, chapter 1 should contain the following paragraphs:

a. Purpose.

b. General information.

c. Explanation of

(1) Terms.

(2) Column headings.

(3) Note references.

d. Note reference numbers.

e. Special equipment reporting instructions.

f. Abbreviations.

g. Authorization.

h. Use.

i. Inquiries about update.

j. Statistical summary data. This paragraph will contain summary counts for items listed in all chapters of the particular edition as follows:

(1) The total number of LINs by CMC.

(2) The total number of NSNs by RICC within ABA.

(3) The total for procurement appropriation funded items in SB 700-20 (that is, the sum of all items assigned A through Q in position 2 of the materiel category structure codes listed in AR 710-1 ).

(4) The total operation and maintenance, Army funded items (that is, the sum of the items assigned codes 3 or 5).

(5) The total for stock-funded items (that is, the sum of the items assigned code 2).

2-3. SB 700-20, Chapter 2, Army adopted items of materiel and information technology

Chapter 2 lists all items that have a separate basis of issue and have been separately type classified under AR 70-1 to be included in TOE, TDA, MTOE, or JTA. The only exceptions are items with type classification designation N, meaning that an item is exempt. LCC is used in SB 700-20 in addition to the type classification designation. LCC provides the basis for logistical support decisions, such as procurement, overhaul, repair parts provisioning, and requisitioning determination. Items in this chapter are listed in the ascending LIN sequence. Refer to AR 700-142 . Chapter 2 consists of the following data:

a. LIN.

b. SCM.

c. CIC. (C indicates HQDA controlled for TDA and JTA authorization purposes; 0 indicates not controlled).

d. RICC (must be 2 if reportable or 0 if not reportable).

e. Generic nomenclature.

f. UI.

g. ABA. These codes are listed in AR 710-1 .

h. CMC.

i. Routing identifier code (RIC).

j. LCC representing the type classification code.

k. Type classification designation (type class).

l. NSN.

m. NSN nomenclature.

n. Unit price.

o. Reference data. This column may list any remarks considered proper by the SB 700-20 data originator activities. Lengthy remarks or notes are explained in SB 700-20, chapter 1; only the note reference number is to be included in this column. A note reference consists of the RIC of the responsible data originator activity, a dash, and a serial number starting with 1. For example, B64-1 indicates a note that applies to a U.S. Army Aviation and Missile Command item.

2-4. SB 700-20, Chapter 4, Developmental and nondevelopmental items

Chapter 4 lists all developmental items and nondevelopmental items, as well as nondevelopmental items assigned developmental line item numbers (Z-LINs). Items in this chapter are listed in the ascending order of their Z-LINs. Under each LIN, NSNs identifying items pertaining to the LIN are listed in ascending NSN sequence. This chapter consists of the following column data:

a. LIN.

b. CIC (will always be C).

c. Generic nomenclature.

d. CMC.

e. RIC.

f. RICC (will be 0 when there are no related NIINs or 2 when the LIN has associated NIINs).

g. The following data will be included if the LIN has a related NSN:

(1) NSN.

(2) NSN nomenclature.

(3) SCM.

(4) Unit price.

(5) UI.

(6) ABA (see para 2-3g ).

(7) Reference data (see para 2-3o ).

2-5. SB 700-20, Chapter 6, Table of distribution and allowances items not requiring type classification

Chapter 6 contains nondevelopmental, nonexpendable TDA or JTA items. It also identifies all items in this category that qualify as base-level commercial equipment (BCE). BCE has been designated as investment end items costing $100,000 or more that are not Army centrally managed or purchased. The type item column of this chapter will reflect BCE Army command (ACOM) approved for those BCE items that can be approved by the TDA and JTA proponent, and BCE for those items that must be approved by HQDA. Items in this chapter are listed in the ascending LIN sequence. Under each LIN, NSNs identifying items pertaining to the LIN are listed in the ascending order of the NSN. The following column data will appear in this chapter:

a. LIN.

b. SCM.

c. CIC.

d. RICC (must be 2 if reportable or 0 if not reportable.

e. Generic nomenclature.

f. UI.

g. ABA (see para 2-3 g ).

h. CMC.

i. RIC.

j. NSN.

k. NSN nomenclature.

l. Unit price.

m. LCC (must always be N).

n. Type item.

o. Reference data (see para 2-3 o ).

2-6. SB 700-20, Chapter 8, Common table of allowances items

Chapter 8 lists items authorized by CTA (see AR 71-32 for the definition of CTA and CTA items). LCC is also shown in this chapter. The column data is the same as that established for chapter 2. However, the reference data field may contain codes identifying the CTA in which the LIN is listed.

2-7. SB 700-20, Appendix A, Cross-reference Army type designator to line item number

Appendix A provides a cross-reference from type or model numbers to the LIN under which the items are listed in chapters 2, 4, 6, 8, and appendix E. Items in this appendix will be listed in type or model number order, with an identifying description. Appendix A consists of the following column data:

a. Type designator (limited to 22 positions).

b. Item identification (limited to 26 positions).

c. LIN (in alphabetic and numeric sequence).

2-8. SB 700-20, Appendix B, Cross-reference national stock number to line item number with reportable item control code

Appendix B provides a cross-reference from NSN to the LIN under which the items are listed in chapters 2, 4, 6, 8, and appendix E and the applicable RICC. Items in appendix B are listed in NIIN order. Appendix B consists of the following column data:

a. NSN.

b. LIN.

c. RICC.

2-9. SB 700-20, Appendix C, Cross-reference generic nomenclature to line item number

Appendix C provides a list, in alphabetical order, of chapters 2, 4, 6, and 8 generic nomenclatures cross-referenced to the LIN and the chapter in which they are listed. Appendix C consists of the following column data:

a. Generic nomenclature.

b. LIN.

c. Chapter in which the LIN and nomenclature are listed.

2-10. SB 700-20, Appendix D, Summary of changes to reportable items

Appendix D lists all additions, deletions, and changes made in SB 700-20 (since the preceding revision was published) that affect equipment status reporting under AR 220-1 , AR 710-2 , and AR 710-3 . Items in this appendix are listed in ascending LIN order. Under each LIN, NSNs that identify items pertaining to the LIN are listed in ascending NSN order. Appendix D is a ready reference for the user to identify changes and consists of the following column data:

a. LIN.

b. NSN.

c. RICC.

d. Chapter in which the LIN and NSN are listed.

e. Type of action (add, delete, change).

2-11. SB 700-20, Appendix E, Deletions and replacement of line item number or national stock number

Appendix E provides a record of LINs or NSNs (3 years for LINs and 1 year for NSNs) that have been deleted from chapters 2, 4, 6, and 8 of SB 700-20. Appendix E consists of the following column data:

a. LIN entries.

(1) Former LIN. This is the LIN being deleted or replaced.

(2) CMC.

(3) Deleted, obsolete, or replaced statement.

(4) New LINs. New LINs are required when the deleted statement indicates a replacement action. If a replacement action is not indicated the word "none" will appear in this column.

(5) Ratio for replacement. The ratio of the replacing item (new LIN) to the replaced item (former LIN) must be shown for each replacement action. If the word "none" appears, this column will be blank. If the new LIN replaces more than one former LIN and the correct ratio cannot be shown, an explanation of the ratio will be included in SB 700-20, chapter 1.

(6) And/Or. If the former LIN is replaced by more than one new LIN, "and/or" will be shown on all but the last or highest replacing LIN.

(7) Date entered in appendix E. This date is used to determine when an inactive LIN will be removed from appendix E (3 years) and placed in the AMC LOGSA SB 700-20 history file.

(8) Chapter. The chapter number is that in which the new LIN is listed. A blank signifies there is no new LIN.

b. NSN entries.

(1) Former LIN. This is the LIN to which the deleted or changed NSN was related.

(2) CMC.

(3) Deleted or changed NSN.

(4) Reason for deletion or change with replacing LIN or NSN.

(5) Date entered in appendix E. This date is used to determine when an inactive NSN will be removed from appendix E (1 year) and placed in the AMC LOGSA history file.

(6) Type classification data (type class). The record of items reclassified as obsolete shows type class 0 and the type classified agenda or the MSCR number that recorded reclassification of the item as obsolete.

(7) Chapter. The chapter number is that in which the replacing NSN is listed. Leave blank if there is no replacing action.

2-12. SB 700-20, Appendix F, Summary of additions, deletions, and changes to chapters 2, 4, 6, and 8 line item numbers

Appendix F lists all LINs added to or deleted from chapters 2, 4, 6, and 8, as well as LINs which have changed chapters since the preceding revision was published. Items in appendix F will be listed in ascending LIN order. Appendix F consists of the following column data:

a. LIN.

b. Type of action (add, delete, or change). Change, as used in this appendix, means that the chapter in which the LIN is located has changed since the preceding revision of SB 700-20. Corrections to LINs are shown as a delete of the incorrect LIN. The disposition of the LIN for all delete actions may be determined by referring to appendix E.

c. Chapter. The chapter shows the chapter number (or E if appendix E) to which the LIN was added or deleted, or where presently listed if the action is a change.

2-13. SB 700-20, Appendix G, Cross-reference new line item number to former line item number

Appendix G provides a cross-reference of new LIN to former LIN. Items in this appendix are listed in new (replacing) LIN order. This appendix will consist of the following column data:

a. New LIN.

b. Former LIN.

2-14. SB 700-20, Appendix H, Authorized and substitute line item number

Appendix H contains the official Army list of substitutions for class VII (major end items) and class VIII (medical materiel) LINs. Part 1 is sequenced by authorized line item number (AUTH-LIN) cross-referenced to SUB-LIN and the SUB-LIN generic nomenclature. Part 2 is sequenced by SUB-LIN cross-referenced to AUTH-LIN and the AUTH-LIN generic nomenclature. Refer to SB 700-20, chapter 2, to obtain additional management data for the substitute items. Refer to AR 220-1 for additional information regarding use, reporting, and determination of SUB-LINs. Appendix H consists of the following column data:

a. Part 1.

(1) AUTH-LIN.

(2) SUB-LIN.

(3) Generic nomenclature (applies to SUB-LIN).

b. Part 2.

(1) SUB-LIN.

(2) AUTH-LIN.

(3) Generic nomenclature (applies to AUTH-LIN).

2-15. SB 700-20, Appendix I, Cross-reference line item number to SB 700-20 chapter and appendix E

Appendix I serves as an intermediate index to locate the LIN in SB 700-20. This appendix will be in LIN order and consist of the following column data:

a. LIN.

b. Chapter/appendix E. This shows the chapter number (or E for appendix E) in which the LIN is listed.

2-16. SB 700-20, Appendix J, Line item number to processing Army prepositioned stocks equipment sets code

Appendix J contains a list by LIN of all MTOE and TOE equipment categories. Definitive categories are explained under the Army prepositioned stocks (APS) equipment sets code in this pamphlet. This appendix will be in ascending LIN sequence and consist of the following column data:

a. LIN.

b. APS equipment sets code.

Chapter 3
Data Elements

3-1. Overview

This chapter explains the data elements that apply to SB 700-20 records.

3-2. Appropriation and budget activity account code

The ABA account code is a one-digit funding code that occupies the second position of the Army materiel category structure. The ABA account code can be alphabetic or numeric, excluding the letters I and O and the numbers 0, 1, 4, 6, 7, and 8. Changes to ABA account codes are extracted from the AMDF for update in SB 700-20. Valid ABA account codes are listed in AR 710-1 .

3-3. Army type designator

This code is a unique combination of letters and numbers assigned to an approved national item name to serve as a series designator. It distinguishes among items that have the same Federal item name (that is, it distinguishes military or commercial make and model or type designators-including electronic and photographic type numbers and Army aircraft model numbers-from commercial manufacturers' model numbers).

3-4. Commodity manager code

The CMC is an alphabetic code, which designates the materiel categories of principal and secondary items. Each CMC is identified to the AMC subordinate command or activity that has Army management responsibility as the

a. Primary inventory control activity for Army managed items.

b. Secondary inventory control activity for Army used items that are managed by another Service.

3-5. Controlled item code

The CIC is used to designate those military or commercial items that are managed through centralized requirements and authorizations approval because of their funding, excessive cost, or other selected criteria.

a. C is used to denote controlled items and includes the following:

(1) Developmental and nondevelopmental items pending type classification (Z-LIN, SB 700-20, chapter 4).

(2) All procurement appropriation procured materiel listed in SB 700-20, chapters 2 and 8.

(3) Procurement Appropriation, Army procured materiel, which cost $100,000 or more (listed in SB 700-20, chapter 6).

(4) Commercial industrial weapons, except nonexplosive propellant weapons listed in SB 700-20, chapter 6.

(5) Printing, binding, or related auxiliary equipment of the type requiring Army Publishing Directorate and/or Joint Committee on Printing approval (see AR 25-1 and SB 700-20, Chapter 6).

(6) Military police working dogs (SB 700-20, chapter 2).

(7) Test measurement and diagnostic equipment (see AR 750-43 and SB 700-20, chapters 2 and 6).

(8) Postage metering systems (see AR 25-51 and SB 700-20, chapter 6).

b. 0 (numeric) indicates the item is not controlled.

3-6. Common table of allowances code

The alphabetic code on the generic line of the reference data field (see SB 700-20) identifies the CTA in which that LIN is listed. The CTA codes and the associated CTAs are listed as follows:

a. CTA code A; CTA 50-900.

b. CTA code B; CTA 50-909.

c. CTA code C; CTA 50-970.

(1) The above CTAs are listed in DA Pam 25-30 .

(2) All inquiries pertaining to CTA data may be directed to the Director, Army Capabilities Integration Center, U.S. Army Training and Doctrine Command, Fort Eustis, VA 23604-5761.

3-7. Date entered in SB 700-20, appendix E

The date of entry in appendix E is used to determine when a LIN or NSN is to be removed from appendix E and placed in the SB 700-20 history file. (LINs are retained for 3 years, NSNs for 1 year.)

3-8. Department of Defense Ammunition Code

The Department of Defense Ammunition Code is an eight-character number divided into two parts separated by a hyphen. The first part consists of four numerals, such as 1320, which form the Federal supply classification (FSC) code number assigned to items covered by the ammunition generic description. The second part-the Department of Defense identification code (DODIC)-consists of one letter and three numerals or two letters and two numerals. These characters are assigned to an ammunition generic description within the FSC class; that is, D548, assigned to projectile, 155 millimeter M116 SMOKE HC BE F. HOWS M1 M1A1 M46. (The DODIC for ammunition items is shown on the NSN lines in SB 700-20, chapters 2, 4, and 8, in the reference data column.)

3-9. Federal item identification

The Federal item identification (FII) identifies an NSN and consists of the Federal item name and the minimum data adequate to establish the essential characteristics of the item, which give it its unique character and differentiates it from every other item in the supply system.

3-10. Generic nomenclature

Generic nomenclature is the family name of an item or of a group of items, whose physical characteristics and functional capabilities are sufficiently common to satisfy the same operational requirements, which are treated collectively in supply operations. Generic nomenclature is restricted to 64 characters for listing in authorization documents, the AMDF, SB 700-20, as well as other publications and reports prepared from these files. It consists of the Federal item name, followed by a colon, and only that additional descriptive information (extracted from the applicable FII) required to express functional capability and to distinguish between items that are not functionally interchangeable.

a. Generic nomenclatures for the following may only include basic model or type designators:

(1) AN/ GRC 26, not AN/ GRC 26A, and M17, not M17A1, M17E1, XM17, or M17E1.

(2) Aircraft, electronic, and photographic equipment identified by Department of Defense established type designators.

(3) Ammunition items, if model designator is essential in distinguishing between items not functionally interchangeable.

(4) Items described in part by a designator or code to avoid disclosure of classified information.

(5) Items assigned Z-LINs.

b. The words "less power or Army" following the generic nomenclature indicate that one or more major procurement appropriation components have been removed from the assemblage. These removed components may be used with, but are no longer considered as a part of, the assemblage and are to be authorized as separate items of issue under their own generic nomenclature and associated LIN, if required. When a LIN is deleted from chapters 2, 4, 6, or 8 of SB 700-20, the generic nomenclature will be replaced by one of the following deletion reason statements:

(1) DEL (delete). This remark is used in section 1 of the SB 700-20 file maintenance transaction. It is also shown in SB 700-20, appendix E, when a LIN and related NIIN are deleted from chapters 2, 4, 6, and 8 of SB 700-20 and are not replaced for reasons other than reclassified to obsolete, but for which authorizations continue. This remark is not complete in itself but must also direct the authorization document proponent to the new authorization source, such as section 1 of CTAs, SC 6545-9-CL series, or component of a LIN; that is, A12345.

(2) DEL-DEVELOPMENT TERMINATED. This remark is used in section 1 of the SB 700-20 file maintenance transaction. It is also shown in SB 700-20, appendix E, when a Z-LIN (and its related NIIN, if applicable) is deleted from SB 700-20, chapter 4, because development has stopped and there is no replacing LIN. However, no item will be deleted with this statement if there is an Army requirement and authorization in the Structure and Composition System file.

(3) DEL-NO REPLACEMENT. This remark is used in section 1 of the SB 700-20 file maintenance transaction. It is also shown in SB 700-20, appendix E, when a LIN and its related NIIN are deleted from SB 700-20, chapters 2, 4, 6, or 8, and not replaced for any reason other than reclassified to obsolete. This remark will be used only if the item is not listed in any authorization document.

(4) OBSOLETE NOT REPLACED. This remark is used in section 1 of the SB 700-20 file transaction. It is also shown in SB 700-20, appendix E, when a LIN listed in chapters 2 or 8 or of SB 700-20 is reclassified to obsolete, and the LIN is not replaced by an SB 700-20 chapter 2 or 8 LIN.

(5) OBSOLETE REPLACED BY. This remark is used in section 1 of the SB 700-20 file maintenance transaction. It is also shown in SB 700-20, appendix E, when all items identified by a current LIN listed in chapters 2 or 8 or of SB 700-20 are reclassified to obsolete and replaced by items identified by a replacing LIN in SB 700-20, chapters 2 or 8.

(6) REPLACED BY. This remark is used in section 1 of the SB 700-20 file maintenance transaction. It is also shown in SB 700-20, appendix E, when a LIN is deleted from chapters 2, 4, 6, or 8 of SB 700-20 and is replaced by another LIN for reasons other than reclassified to obsolete.

3-11. Line item number

The LIN is a six-character alphanumeric identification of generic nomenclature. It pertains to the line on which the generic nomenclature is listed in those bulletins and in Army equipment authorization documents. The LIN is used to treat all NSN items possessing the functional capability expressed by the generic nomenclature collectively. LINs consist of one letter and five numerals and range from A00001 through Z99998. LINs between A00001 and Y99989, except those starting with 0, are assigned to items included in SB 700-20, chapters, 2, 6, or 8. Z-LINs are assigned to development type items for inclusion in required operational capability and in authorization documents prior to type classification, as well as for use in special studies for development data required for type classification (see chapter 4 of this pamphlet).

3-12. Logistics control code

The LCC is assigned to each type classified item by the type classified approval authority. LCCs designate the level of logistics support to be provided (refer to AR 700-142 ).

3-13. Materiel status committee record

a. Assigned by the materiel status office (MSO), the MSCR is shown with the type classification symbol of an item. The MSCR is a record of the decisions and actions reported by materiel developers. It is comprised of the meeting number, calendar year, appropriate section of the MSCR, and the sequence number of a particular item. The MSCR was previously known as the technical committee data. Also shown with type classification actions are identification symbols, which are explained below.

(1) NONE-AMC.

(2) C or CML-Chemical Corps.

(3) E or ENG-Corps of Engineers.

(4) M or MED-Army Medical Service.

(5) O or ORD-Ordnance Corps.

(6) Q or QM-Quartermaster Corps.

(7) S or SIG-Signal Corps.

(8) T or TC-Transportation Corps.

b. When transactions in the reference data column in chapters 2 or 8 of SB 700-20 reflect 0000000, this represents an interim MSCR assigned by AMC LOGSA for the purpose of processing a commodity manager's transaction that was approved by HQDA without a mandatory MSCR number assigned.

3-14. National stock number

The NSN is a 13-digit number assigned by the Defense Logistics Information Service to an item of materiel used, stocked, and distributed within the Federal Government and identified in the Federal Catalog System.

3-15. National stock number nomenclature

NSN nomenclature is a condensed form of the FII, restricted to 21 characters, used for listing NSN items or military standard type and class in the ACLDB, SB 700-20, and other publications and reports prepared from these files. NSN nomenclature contains the basic noun and identifies make, model, size, and related information applicable to each NSN to distinguish between national stock numbered items or types and classes of vehicles associated with the same generic nomenclature. When a NIIN is deleted from SB 700-20, chapters 2, 4, 6, or 8, one of the following deletion reason statements will replace the NSN nomenclature:

a. DEL-NO REQUIREMENT. This remark is used in section 2 of the SB 700-20 file maintenance transaction and shown in SB 700-20, appendix E, when a NIIN is

(1) Reclassified to obsolete and asset reporting is not required.

(2) Deleted because of incorrect listing or because there is no Army authorization.

b. NOW LIN. This remark is used in section 2 of the SB 700-20 file maintenance transaction. It is also shown in SB 700-20, appendix E, when a LIN is to be deleted from chapters 2, 4, 6, or 8 of SB 700-20 and replaced by another LIN for a reason other than declassified to obsolete, and the associated NIIN is being added to the replacing LIN.

c. RP-BY (replaced by). This remark is used in section 2 of the SB 700-20 file maintenance transaction. It is also shown in SB 700-20, appendix E, when the NIIN previously listed in one of the chapters of SB 700-20 is replaced by another NIIN.

d. CH-TO (changed to). This remark is used in the SB 700-20 section 2 file maintenance transaction. It is also shown in SB 700-20, appendix E, when the NIIN previously listed in one of the chapters of SB 700-20 for the same item of supply is changed to a different NIIN to correct an error or to consolidate identical or completely interchangeable items under a preferred NIIN.

3-16. Army prepositioned stocks equipment sets code

The APS equipment sets code is a one-position alphabetic code that identifies by LIN all the MTOE or TOE equipment authorized for each APS equipment set and indicates the appropriate equipment categories as follows:

a. APS Code P-prepositioned materiel. This category includes MTOE or TOE items authorized to be stored in APS unit equipment and activity sets.

b. APS Code N-not authorized for prepositioning. This category includes MTOE or TOE items excluded from prepositioning that must be moved with the deploying unit.

c. APS Code T-to accompany troops. This category includes MTOE or TOE and non-MTOE or non-TOE items excluded from prepositioning that accompany the deploying troops, such as individual weapons, protective masks, and so on.

d. APS Code D-not authorized prepositioning-deferred. This category includes MTOE or TOE items excluded from prepositioning that are not required in-theater prior to 30 days beforehand. These items will not be deployed by air with the units but will be moved at a later date, as transportation becomes available.

3-17. Procurement appropriation commercial item code

The PCI code is a one-position numeric code used to designate those investment end items that may be purchased with BCE funds. The PCI code is entered only for SB 700-20, chapter 6, items.

a. A PCI code of 1 is used for BCE items, which may be approved at the ACOM level. The term "BCE ACOM approved" appears in the type class field in SB 700-20, chapter 6. These items are listed in AR 71-32 .

b. A PCI code of 2 is used for BCE items, which must be approved by HQDA. The acronym "BCE" appears in the type class field in SB 700-20, chapter 6.

c. A PCI code of 3 is used for SB 700-20, chapter 6, items that do not qualify as BCE.

3-18. Reportable item control code

The RICC is a one-digit numeric code assigned to reportable items for which asset reporting is required under the provisions of AR 710-3 and AR 220-1 . RICCs used in SB 700-20 are defined as follows:

a. RICC code 2-selected TOE, MTOE, TDA, modification table of distribution allowances, CTA, and JTA authorized items (including all NSNs of a generic family), as well as nonauthorized and obsolete items designated by commodity managers. This category includes major items on which data is required for the AMP and selected secondary items and repair parts, which require special control by commodity managers due to their importance and criticality. This also includes all equipment readiness code A LINs unless specifically excluded by HQDA (Deputy Chief of Staff, G-4 (DALO-SMD)).

b. RICC code 3-deleted. Reporting for the U.S. Army Reserve was discontinued as of 1 September 1988. Items formerly coded RICC 3 are now designated as RICC 2/0.

c. RICC code 0 (numeric)-not reportable.

3-19. Routing identifier code

The RIC identifies the Army inventory control point (primary inventory control activity or secondary inventory control activity) having Army item management responsibility for an item. The RICs are included in table 1-1 .

3-20. Reference data

Reference data is established by citing the reference number of a publication, which provides lists of components for sets, kits, assemblages, and references to technical manuals (TMs). The preferred references are components lists (CLs) supply manuals. CL numbers that are too long for publication have been abbreviated by eliminating dashes (that is, if the CL number is SC-5180-90-CL-N36, the abbreviated number will be SC518090-CL-N36).

a. In the absence of a CL, other reference documents are indicated (for example, TMs, SBs, specifications, drawings, and so on). TM numbers, which are too long for publication in this column, have been abbreviated by eliminating the letters TM and FSC. Given the abbreviated number and in order to determine the complete number, it is necessary to add the prefix TM, and also the FSC (first four digits of the NSN of the related item) after the first dash in the abbreviated number (that is, if the abbreviated number is 9-250-35P/10/1 and the NSN of the related item is 1430-00-123-4560, the complete number is TM 9-1430-250-35P/10/1 ).

b. Remarks too lengthy to be included on one line in this column are indicated by note numbers consisting of the submitter's RIC followed by a dash (-) and a one-position serial number (for example, B64-1). The complete note is given in SB 700-20, paragraphs 1-4. This column may list any remarks considered appropriate by the SB 700-20 supporting agencies. For SB 700-20 chapter 8 items, this column will reflect on the generic line the appropriate CTA code assigned by USAFMSA that identifies the CTAs in which the LIN is listed.

3-21. Type fuel consumption code

The type fuel consumption code is a one-position alphabetic code, which indicates an item consumes bulk fuel, the type of fuel consumed, and the capability to consume more than one type of fuel. This data element will be used in computing Army bulk fuel requirements. The following codes are applicable:

a. A-aviation fuel.

b. D-diesel fuel.

c. G-gasohol.

d. J-jet fuel.

e. K-kerosene.

f. M- leaded MO-GAS (motor vehicle).

g. P-propane.

h. U- unleaded MO-GAS.

i. X-multi-application.

3-22. Supply category of materiel

The SCM consists of the class and subclass of supply to which the item is assigned. Classes and subclasses of supply are listed and defined in DA Pam 708-2 .

3-23. Type class

The type classification is assigned per AR 700-142 . It is used to identify the life-cycle status of an item and to record the status of the item. This is a guide for authorization, procurement, logistical support, and asset and readiness reporting. Valid Army type classification codes are as follows:

a. Standard (S). This is a materiel item determined to be acceptable for the mission intended, supportable in its intended environment, and acceptable for introduction into the Army inventory, or capable of being made acceptable without further developmental effort during production. This designation includes items that have been or are being replaced by new standard items but that are still acceptable for the intended missions.

b. Obsolete (O). This is a materiel item that is no longer required or acceptable for U.S. Army use.

c. Limited procurement (LP). This is an additional type classification available for use under exceptional circumstances and is applicable only to developmental items. It is used when a materiel item is required for special use for a limited time, where a specified limited quantity will be procured without further intent of additional procurement of the item under this classification. Items designated for LP type classification are those that do not qualify for adoption as standard. These items are required to

(1) Meet urgent operational requirements, which cannot be satisfied by an item type classified standard.

(2) Obtain production items for test by establishment of a pilot production line, when the materiel acquisition decision process decision authority approves conduct of additional tests as a prerequisite to type classification standard.

3-24. Substitute line item numbers

AUTH-LIN substitutions for class of supply VII items are contained in SB 700-20, appendix H. They are used for substituting an item of one LIN for an item of another LIN. Units of all Army components will be equipped in Department of the Army Master Priority List sequence, with the prescribed LIN authorized in the authorization documents unless otherwise directed by USAFMSA (MOFI-TED-E). The approved SUB-LIN must provide the next best item that allows the unit to accomplish its mission in terms of the following:

a. Being compatible with associated items of equipment in the units.

b. Performing the same function and purpose as the AUTH-LIN. For communication-electronics equipment, the item must be interoperable with the existing network.

c. Having petroleum, oil, and lubricants requirements compatible with the unit's petroleum, oil, and lubricants requirements.

d. Having ammunition available for substituted weapons.

e. Being able to move at approximately the same speed (possess the same type of mobility) as the AUTH-LIN.

f. Having the same air transportability characteristics as the AUTH-LIN.

g. Being supportable by maintenance personnel authorized on the MTOE and TDA.

h. Having repair parts, tools, and diagnostic and test equipment for the repair of the SUB-LIN available to the unit.

Chapter 4
Data Maintenance Procedures

4-1. Data maintenance

SB 700-20 is updated monthly to reflect the most current logistics management data (see para 1-4 c ). This chapter delineates the data that will be updated.

4-2. Procedures to establish and maintain line item numbers and national stock numbers

a. Processing updates to SB 700-20, chapters 2, 4, 6, and 8 and appendix E.

b. Changes to active SB 700-20, chapters 2, 4, 6, and 8, are submitted by automated transaction to AMC LOGSA unless otherwise stated in this chapter or approved by Headquarters, AMC.

c. Changes to SB 700-20, appendix E, are generated by the automated SB 700-20 system as a result of processing the changes to the active chapters.

d. The restrictions pertaining to updating SB 700-20, chapters 2, 4, 6, and 8 and appendix E, are listed in table 4-1 and are further explained in this chapter.

e. Input LIN and NSN maintenance transactions are identified by document identifier code (DIC). The list of acceptable codes and combinations is provided in table 4-2 .

f. Input transactions are edited and validated by AMC LOGSA, which provides the originator with either a notification of valid transaction pending approval by headquarters or a transaction reject notification. Valid transactions are forwarded to the appropriate approval authority as follows:

(1) SB 700-20 chapter 4 maintenance actions are forwarded to USAFMSA (MOFI-TED-E), which in turn accomplishes internal HQDA staffing and provides final approval or disapproval notification to AMC LOGSA.

(2) (1) SB 700-20 chapter 6 LIN and NSN maintenance transactions are sent through USAFMSA (MOFI-TED-E), which will furnish the final approval or disapproval notification to AMC LOGSA.

(3) All SB 700-20 chapters 2 and 8 and maintenance transactions are sent to the Headquarters, AMC MSO for review and Headquarters, AMC approval. The MSO furnishes Headquarters, AMC approval or disapproval to AMC LOGSA. Transactions approved by Headquarters, AMC are forwarded to USAFMSA (MOFI-TED-E), which coordinates HQDA staffing actions and provides final approval or disapproval notification to AMC LOGSA.

g. Upon receipt of notification of disapproval from USAFMSA (MOFI-TED-E), AMC LOGSA purges the transaction from the SB 700-20 files and generates a return transaction containing the appropriate disapproval code to the originator.

h. Upon receipt of final approval notification from USAFMSA (MOFI-TED-E), AMC LOGSA updates SB 700-20 files using the approved data. AMC LOGSA furnishes the originator with a return transaction containing the notification and approved data.

4-3. Processing updates to major item line item number substitution data in SB 700-20, appendix H

a. Data originators add and delete SUB-LIN data by submitting the appropriate transactions to AMC LOGSA.

b. AMC LOGSA edits and validates the SUB-LIN data, providing the originator with either a reject notification or notification of approval. Approved data is used to update SB 700-20 master files.

4-4. Processing Army prepositioned stocks equipment sets updates to SB 700-20, appendix J

AMC LOGSA edits and validates data and provides reject notifications to HQDA (Deputy Chief of Staff, G-4 (DALO-SMW)). Valid data is incorporated into appendix J.

4-5. Transaction formats for SB 700-20 input, reject codes, disapproval codes, edit and validation criteria, and other processing instructions

This information is supplied to authorized SB 700-20 data originators in a separate SB 700-20 operating instruction. See table 1-1 for a list of authorized SB 700-20 data submitters.

4-6. Assignment of line item numbers

a. LINs are assigned by AMC LOGSA only for items to be listed in SB 700-20 active chapters. LINs are normally assigned upon receipt of an automated file maintenance transaction from an authorized SB 700-20 data submitter. When an urgent requirement exists, AMC LOGSA honors telephonic requests for Z-LINs. To justify establishing a separate LIN and generic nomenclature, the item must possess a functional capability different from existent SB 700-20 generic nomenclatures. A separate LIN will be assigned to models having different capabilities and when there are changes in associated support items of equipment or changes in supporting personnel. BOIP and qualitative and quantitative personnel requirements information are developed and approved, and the equipment then requires type classification per AR 71-32 and AR 700-142 .

b. The LINs between A00001 and Y99989 are assigned only to

(1) Generic nomenclatures identifying items that are type classified for Army use.

(2) Items exempt from type classification according to AR 700-142 .

c. Z-LINs are assigned to all developmental acquisition programs.

4-7. Notice of newly assigned line item numbers

To reduce the chance of unauthorized premature use of newly assigned LINs, AMC LOGSA provides notification of newly assigned or approved LINs as follows:

a. When a valid request for a SB 700-20 chapters 2, 4, 6, or 8 LIN is received and processed, AMC LOGSA sends a notification of valid transaction pending headquarters approval containing the interim LIN to the transaction originator. These notifications do not constitute an approval action.

b. When an interim LIN assignment is approved by USAFMSA, AMC LOGSA forwards an approval notification to the submitter.

4-8. Restrictions on the use of newly assigned line item numbers

a. Newly assigned LINs are not authorized for official use until the effective date of SB 700-20.

b. These newly assigned LINs may be used in planning for actions that will become effective on or after the effective date. These actions include preparation

(1) For updating data files to include the ACLDB master data record.

(2) For changing property records on or after the effective date.

(3) Of changes to TOE, TAADS, CTA, or new authorization documents to be submitted by proponents to HQDA on or after the effective date.

c. As an exception to the above, the restrictions below apply to the assignment and use of Z-LINs. Z-LINs

(1) Are not used in BOIP unless the responsible commodity command has been determined and an appropriate generic nomenclature has been established and provided to AMC LOGSA.

(2) Are assigned only in response to requests received from the commodity commands that are authorized submitters of SB 700-20 data.

(3) May be used at once, regardless of the effective date, for requirements planning purposes, such as BOIP or AMP. However, they must be replaced by appropriate standard LINs after the item is type classified or be immediately deleted if the BOIP or development project is stopped or disapproved.

(4) May not be listed in TOE, MTOE, TDA, JTA, or CTA authorization documents without prior written approval by HQDA.

d. LINs are cancelled only after

(1) They are inactive in the ACLDB and SB 700-20.

(2) The data originator activity, together with AMC LOGSA and the Deputy Chief of Staff, G-3/5/7 (DCS, G-3/5/7), determine that the last item related to the LIN has been phased out of the supply system.

(3) The LIN and generic nomenclature have been removed from all current TOE and authorization documents. In addition, LINs shown in SB 700-20, chapter 6, are not processed for cancellation until the LINs have been out of TAADS for at least 3 years.

(4) Assets identified by the LIN have been removed from using units and are being held by the life cycle management command for disposition as required by AR 70-1 .

e. LINs are made inactive by

(1) Removing the generic nomenclature and related NSN from all active SB 700-20 chapters.

(2) Listing the inactive LIN; related NSNs, when applicable; and the reason for deletion or replacement in SB 700-20, appendix E.

f. Inactive LINs are listed in SB 700-20, appendix E, for 3 years before they are deleted and transferred to the AMC LOGSA SB 700-20 data history file. Inactive LINs may be reinstated only after coordination with DCS, G-3/5/7. Inactive NIINs are listed in SB 700-20, appendix E, for 1 year; then they are deleted and transferred to the AMC LOGSA SB 700-20 data history file.

g. Z-LINs are deleted from SB 700-20 when the standard line item number (SLIN) is assigned or when the requirement for the materiel no longer exists. Z-LIN deleted requests are submitted by the materiel developer in SLAMIS and will go through the appropriate process before being deleted. Z-LINs that become type classified and receive an SLIN will also go through the SLAMIS coordination process. This ensures that the combat developer

(1) Submits a request to cancel the requirement document.

(2) Requests BOIP be transferred to the history file, together with approval of the LIN deletion.

Table 4-1. Exceptions to processing additions, deletions, or changes to SB 700-20
Data elements For chapters 2 and 8 and (see notes) For chapter 4 (see notes) For chapter 6 (see notes)
LIN 1, 10 3, 4, 10 10, 17, 18
CIC 5 5, 7 16
RICC 11 9 11
Generic nomenclature 2, 4 4 2
CMC 8 8 8
Procurement appropriated N/A N/A 20
Commercial item code NIIN 14, 17 6, 14 16
NIIN nomenclature 1 1 16
Type classification 1 N/A N/A
LCC 1, 15 12 13
Chapter 19 N/A 19

Notes:
1. May be added, changed, or deleted only by submitting SB 700-20 automated transactions to HQDA through AMC LOGSA and the Headquarters, AMC MSO. Automated transactions will be submitted to AMC LOGSA only after the documentation required by
AR 70-1 has been submitted directly to the MSO (AMCDE-PA).
2. May be added or deleted by submitting SB 70-20 automated transactions only when the complete item is being added or deleted.
3. Will normally be added by submitting SB 700-20 automated transactions to AMC LOGSA. (SB 700-20 chapter 4 LINs may also be added telephonically through AMC LOGSA when urgency warrants.)
4. May be changed or deleted only by submitting SB 700-20 automated transactions through AMC LOGSA to HQDA.
5. May be added, deleted, or changed only by submitting SB 700-20 automated transactions through AMC LOGSA to HQDA.
6. May be changed or deleted only by submitting SB 700-20 automated transactions though AMC LOGSA to HQDA.
7. May only be C.
8. AMC LOGSA will automatically change the CMC when all NSNs associated with a LIN have been logistically transferred to a different manager. When a partial logistics reassignment occurs, the CMC will be changed only by submitting SB 700-20 automated transactions to AMC LOGSA.
9. Z-LINs without NSNs must be coded RICC 0; Z-LINs with NSNs must be coded RICC 2.
10. May not be changed despite generic nomenclature change.
11. Data will be entered by AMC LOGSA as directed by HQDA and Headquarters, AMC to properly designate RICC 2/0 items in SB 700-20. Any corrections made by AMC LOGSA will be distributed to the life cycle management commands through normal file maintenance procedures. The RICC will be perpetuated in the ACLDB from SB 700-20.
12. May be only D.
13. May be only N.
14. NIIN may be deleted by submitting SB 700-20 automated transactions to AMC LOGSA for: (a) clothing sizes that conform to the generic nomenclature of items already type classified and (b) ammunition items that conform to the generic nomenclature of items already type classified. However, ammunition items are managed under separate stock numbers as separate items of supply due to minor modifications, production deviations, or packaging differences that do not change the functional capability; the exception is the last NIIN under a given LIN this must be submitted through AMC LOGSA to HQDA.
15. Changes to the LCC not affecting type classification will be submitted directly to AMC LOGSA.
16. May be added, changed, or deleted only by submitting SB 700-20 automated transactions through AMC LOGSA to USAFMSA.
17. May be added or changed only by submitting SB 700-20 automated transactions through AMC LOGSA to HQDA.
18. May be deleted only by submitting SB 700-20 automated transactions through AMC LOGSA to HQDA or USAFMSA. Items will not be deleted until the LIN has been out of TAADS for 3 years.
19. May be changed only by submitting SB 700-20 automated transactions through AMC LOGSA to HQDA. SB 700-20 chapter changes involving SB 700-20 chapter 4 items are not permitted.
20. PCI code applies to SB 700-20 chapter 6 transactions only. May be added, changed, or deleted only by submitting automated transactions through AMC LOGSA to USAFMSA. Must be a 1 if ACOM approval is required for BCE item. Must be a 2 if HQDA approval is required for BCE item. Must be 3 if item does not qualify as BCE.


Table 4-2. Acceptable document identifier code combinations
DIC Combination: CM1
Description: A transaction containing one or two records with this DIC is a request for assignment of a Z-LIN
DIC Combination: CM4
Description: A transaction containing one or more records with this DIC is a request to delete a LIN for reasons other than obsolescence with replacement. Use of this DIC by itself is limited to Z-LINs. If the deleted LIN has multiple replacements, the transaction must contain one record for each replacing LIN. Replacement LIN/LINs must be resident in SB 700-20.
DIC Combination: CM5
Description: A transaction containing a record with this DIC is a request to delete a LIN for reasons other than obsolescence without replacement. Use of this DIC by itself is limited to Z-LINs.
DIC Combination: CM6
Description: A transaction containing one or two records with this DIC is a request to change the data recorded against the LIN without a concurrent change to the NIIN data (includes SB 700-20 chapter changes).
DIC Combination: CM8
Description: A transaction containing one record with this DIC is a request to change the CMC. This DIC can only be used in a single record transaction. A change to the CMC is usually the result of a logistics reassignment.
DIC Combination: CG1
Description: A transaction containing one or more records with this DIC is a request to add NIINs to an established LIN.
DIC Combination: CG2
Description: A transaction containing one or more records with this DIC is a request to delete NIINs from an active LIN because the items represented by the NIINs are obsolete and are not to be replaced. The last NIIN assigned to a LIN cannot be deleted by this transaction.
DIC Combination: CG3
Description: A transaction containing one or more records with this DIC is a request to delete NIINs from an active LIN because the items represented by the NIINs are obsolete and are to be replaced. The last NIIN assigned to a LIN cannot be deleted by this transaction. The replacing NIINs identified in the delete statement must be active in the ACLDB and must be currently associated with a LIN in SB 700-20.
DIC Combination: CG4
Description: A transaction containing one or more records with this DIC is a request to delete NIINs from an active LIN because the items represented by NIINs are being deleted for reasons other than obsolescence and are to be replaced. The last NIIN assigned to a LIN cannot be deleted by this transaction. The replacing NIINs identified in the delete statement must be active in the ACLDB and must be currently associated with a LIN in SB 700-20.
DIC Combination: CG5
Description: A transaction containing one or more records with this DIC is a request to delete NIINs from an active LIN because the items represented by the NIINs are being deleted for reasons other than obsolescence and are not being replaced. The last NIIN assigned to a LIN cannot be deleted by this transaction.
DIC Combination: CG6
Description: A transaction containing one or more records with this DIC is a request to change the data recorded against the NIIN or NIINs associated with a LIN without a concurrent change to the LIN data.
DIC Combination: CM1, CM4
Description: A transaction containing this combination of DICs is a LIN delete with replacement; the deleted LIN is not obsolete. The CM4 record deletes the current LIN and the CM1 establishes the replacement LIN. As this combination is applicable only to LINs without associated NIINs, use of this combination is limited to deletion of an identifies automatic data processing equipment line item number (I-LIN) or a Z-LIN. For commodity command standard system activities, use of this combination is limited to deletion of a Z-LIN replaced by a Z-LIN. As a LIN may have multiple replacements, this combination may include multiple CM4 records; however, the transaction must contain a CM1 for each CM4.
DIC Combination: CM1, CG1
Description: A transaction containing this combination of DICs is a request to establish a LIN and its associated NIINs.
DIC Combination: CM2, CG2
Description: A transaction containing this combination of DICs is a request to delete a LIN and its associated NIINs because of obsolescence without replacement. The transaction must contain a CG2 record for every NIIN associated with the LIN.
DIC Combination: CM3, CG3
Description: A transaction containing this combination of DICs is a request to delete a LIN and its associated NIINs because of obsolescence with replacement. The replacement LIN is already established in SB 700-20. The transaction must contain a CG3 record for every NIIN associated with the LIN. As a LIN may have multiple replacements, this combination may include multiple CM3 records; however, at least one CG3 record must be associated with each CM3 record.
DIC Combination: CM4, CG4
Description: A transaction containing this combination of DICs is a request to delete a LIN and its associated NIINs for reasons other than obsolescence with replacement. The replacement LIN is already established in SB 700-20. The transaction must contain a CG4 record for every NIIN associated with the LIN. As a LIN may have multiple replacements, this combination may include multiple CM4 records; however,at least one CG4 record must be associated with each CM4 record.
DIC Combination: CM5, CG5
Description: A transaction containing this combination of DICs is a request to delete a LIN and its associated NIINs for reasons other than obsolescence without replacement. The transaction must contain a CG5 record for every NIIN associated with the LIN.
DIC Combination: CM6, CG6
Description: A transaction containing this combination of DICs is a request to change data (other than LIN/NIIN) recorded against a LIN and its associated NIINs. This includes SB 700-20 chapter changes. When a SB 700-20 chapter change is indicated, the transaction should contain a CG6 record for each associated NIIN so that the NIIN data is changed to be compatible with the SB 700-20 chapter.
DIC Combination: CG1, CG3
Description: A transaction containing this combination of DICs is a request to delete a NIIN, because the item represented by the NIIN is obsolete, with replacement and to establish the replacing NIIN. A transaction containing this combination of DICs can delete more than one NIIN and/or establish more than one NIIN. Every NIIN associated with the LIN cannot be involved in a transaction of this type. The replacing NIINs identified in the delete statement must be active in the ACLDB and must either be currently associated with a LIN in SB 700-20 or be included in a CG1 record within this transaction.
DIC Combination: CG1, CG4
Description: A transaction containing this combination of DICs is a request to delete a NIIN, for reasons other than obsolescence, with replacement and to establish a replacing NIIN record. A transaction containing this combination of DICs can delete more than one NIIN and/or establish more than one NIIN. Every NIIN associated with the LIN cannot be involved in a transaction of this type. The replacing NIINs identified in the delete statement must be active in the ACLDB and must either be currently associated with a LIN in SB 700-20 or be included in a CG1 record within this transaction. This combination of DICs can also be used to transfer a NIIN from one LIN to another. In this case, the delete statement of the CG4 record identifies the new LIN, and the CG1 record requests that the NIIN be added to that LIN.
DIC Combination: CG2, CG3
Description: A transaction containing this combination of DICs is a request to delete NIINs from an active LIN because the items represented by NIINs are obsolete. In this combination, some NIINs are replaced and some are not. The last NIIN assigned to a LIN cannot be deleted with this transaction. The replacing NIINs recorded in the delete statement of the CG3 records must be active in the ACLDB and must be currently associated with a LIN in SB 700-20.
DIC Combination: CG4, CG5
Description: A transaction containing this combination of DICs is a request to delete NIINs from an active LIN because the items represented by the NIINs are being deleted for reasons other than obsolescence. In this combination, some NIINs are replaced and some are not. The last NIIN assigned to a LIN cannot be deleted by this transaction. The replacing NIINs recorded in the delete statement of the CG4 records must be active in the ACLDB and must be currently associated with a LIN in SB 700-20.
DIC Combination: CM1, CM3, CG1
Description: A transaction containing this combination of DICs is a request to delete a LIN, because it is obsolete, with replacement and to establish the replacing LIN. In this case, as the deleted LIN does not have associated NIINs, the LIN being deleted is an I-LIN. The replacing LIN is a normal LIN with associated NIINs. This combination is not applicable to commodity command standard system activities.
DIC Combination: CM1, CM4, CG1
Description: A transaction containing this combination of DICs is a request to delete a LIN, for reasons other than obsolescence, with replacement and to establish the replacing LIN. In this case, as the deleted LIN does not have associated NIINs, the LIN being deleted is an I-LIN or a Z-LIN. The replacing LIN is a normal LIN with associated NIINs. As a LIN may have multiple replacements, this combination may include CM4 records. If the deleted LIN does have multiple replacements, the transaction contains a CM1/CG1 combination for each replacing LIN, and/or the replacing LIN is already established in SB 700-20. The transaction must contain at least one CG1 record for each CM1 record.
DIC Combination: CM1, CG1, CG4
Description: A transaction containing this combination of DICs is a request to delete a NIIN, for reasons other than obsolescence, with replacement; however, the replacement requires establishment of a new generic nomenclature or the transaction is a request to transfer a NIIN from one LIN to a new LIN to be established. More than one NIIN may be deleted or transferred from the same LIN with this transaction, and multiple replacing LINs may be required. The last NIIN associated with a LIN cannot be deleted with this transaction. There must be at least one CG4 record associated with each generic nomenclature (CM1). There must also be at least one CG1 record associated with each generic nomenclature. If the transaction is transferring NIINs from one LIN to new LINs, it must contain a CG1 record and a CG4 record for each NIIN being transferred.
DIC Combination: CM3, CG2, CG3
Description: A transaction containing this combination of DICs is a request to delete a LIN, because it is obsolete, with replacement. The replacement LIN is already established in SB 700-20. This combination is used if every associated NIIN is not involved in the replacement action. The transaction contains a CG3 record for every associated NIIN involved in the replacement action and a CG2 record for every associated NIIN not involved in the replacement action. The transaction must contain a CG2 or a CG3 record for every NIIN associated with the LIN. As a LIN may have multiple replacements, this combination may contain multiple CM3 records; however, at least one CG3 record must be associated with each CM3 record.
DIC Combination: CM4, CG4, CG5
Description: A transaction containing this combination of DICs is a request to delete a LIN, for reasons other than obsolescence, with replacements. The replacement LIN is already established in SB 700-20. This combination is used if every associated NIIN is not involved in the replacement action. The transaction contains a CG4 record for every associated NIIN involved in the replacement action and a CG5 record for every associated NIIN not involved in the replacement action. The transaction must contain a CG4 or CG5 record for every NIIN associated with the LIN. As a LIN may have multiple replacements, this combination may contain multiple CM4 records; however, at least one CG4 record must be associated with each CM4 record.
DIC Combination: CM1, CM3, CG1, CG3
Description: A transaction containing this combination of DICs is a request to delete a LIN, because it is obsolete, with replacement and to establish the replacing LIN. This combination is used if every associated NIIN is involved in the replacement action. The transaction must contain a CG3 record for every NIIN associated with the deleted LIN. As a LIN may have multiple replacements, this combination may contain multiple CM3 records; however, at least one CG3 record must be associated with each CM3 record. In this combination, if the transaction contains multiple CM3 records, it may contain multiple CM1 records. The replacing LINs recorded in the CM3 records must be currently active in SB 700-20 or be included on an associated CM1 record in this transaction. The transaction must contain at least one CG1 record associated with each CM1 record.
DIC Combination: CM1, CM4, CG1, CG4
Description: A transaction containing this combination of DICs is a request to delete a LIN, for reasons other than obsolescence, with replacement and to establish the replacing LIN or to delete a LIN and transfer its associated NIINs to a LIN or LINs to be established by this transaction. This combination is used if every associated NIIN is involved in the replacement or transfer action. The transaction must contain a CG4 record for every NIIN associated with the deleted LIN. As a LIN may have multiple replacements, this combination may contain multiple CM4 records; however, at least one CG4 record must be associated with each CM4 record. In this combination, if the transaction contains multiple CM4 records, it may contain multiple CM1 records. The replacing LINs recorded in the CM4 records must be currently active in SB 700-20 or be included on an associated CM1 record in this transaction. The transaction must contain at least one CG1 record associated with each CM1 record. If one or more delete statements contained in the CG4 records indicate that the NIINs are being transferred to LINs being established by this transaction, the transaction must contain an associated CM1 record and an associated CG1 record for the same NIIN.
DIC Combination: CM1, CM3, CG1, CG2, CG3
Description: A transaction containing this combination of DICs is a request to delete a LIN, because it is obsolete, with replacement and to establish the replacing LIN. This combination is used if all associated NIINs are not involved in the replacement action. The transaction contains a CG3 record for every associated NIIN involved in the replacement action and a CG2 record for every associated NIIN not involved in the replacement action. The transaction must contain a CG2 or a CG3 record for every NIIN associated with the LIN. As a LIN may have multiple replacements, this combination may contain multiple CM3 records; however, at least one CG3 record must be associated with each CM3 record. In this combination, if the transaction contains multiple CM3 records, it may contain multiple CM1 records. The replacing LINs recorded in the CM3 records must be currently active in SB 700-20 or be included on an associated CM1 record in this transaction. The transaction must contain at least one CG1 record associated with each CM1 record.
DIC Combination: CM1, CM4, CG1, CG4, CG5
Description: A transaction containing this combination of DICs is a request to delete a LIN, for reasons other than obsolescence, with replacement and to establish the replacing LIN or to delete a LIN and transfer its associated NIINs to a LIN or LINs to be established by this transaction. This combination is used if not all associated NIINs are involved in the replacement action. The transaction contains a CG4 record for every associated NIIN involved in the replacement action and a CG5 record for every associated NIIN not involved in the replacement action. The transaction must contain a CG4 or CG5 record for every NIIN associated with the LIN. As a LIN may have multiple replacements, this combination may contain multiple CM4 records; however, at least one CG4 record must be associated with each CM4 record. In this combination, if the transaction contains multiple CM4 records, it may contain multiple CM1 records. The replacing LINs recorded in the CM4 records must be currently active in SB 700-20 or be included on an associated CM1 record in this transaction. The transaction must contain at least one CG1 record associated with each CM1 record. If one or more CG4 records indicate that the NIINs are being transferred to LINs being established by this transaction, the transaction must contain an associated CM1 record and an associated CG1 record for the same NIIN.

Appendix A
References

The Official Army Publications Web Sites.

Publication Section I
Required Publications

AR 70-1. Army Acquisition Policy (Cited in para 1-4a(1) .)

AR 71-32. Force Development and Documentation (Cited in para 1-4a(2) .)

AR 200-1. Environmental Protection and Enhancement (Cited in para 1-4a(3) .)

AR 220-1. Army Unit Status Reporting and Force Registration - Consolidated Policies (Cited in para 1-4a(4) .)

AR 700-142. Type Classification, Materiel Release, Fielding, and Transfer (Cited in para 1-4a(5) .)

AR 710-3. Inventory Management Asset and Transaction Reporting System (Cited in para 1-4b .)

DA Pam 708-2. Cataloging and Supply Management Data Procedures for the Army Central Logistics Data Bank (Cited in para 1-4a(8) .)

Publication Section II
Related Publications

A related publication is a source of additional information. The user does not have to read it to understand this publication.

AR 25-1. Army Information Technology

AR 25-30. Army Publishing Program

AR 25-51. Official Mail and Distribution Management

AR 708-1. Logistics Management Data and Cataloging Procedures for Army Supplies and Equipment

AR 710-1. Centralized Inventory Management of the Army Supply System

AR 710-2. Supply Policy Below the National Level

AR 750-43. Army Test, Measurement, and Diagnostic Equipment

CTA 50-900. Clothing and Individual Equipment (Available at http://armypubs.army.mil/doctrine/CTA_1.html .)

CTA 50-909. Field and Garrison Furnishings and Equipment (Available at http://armypubs.army.mil/doctrine/CTA_1.html .)

CTA 50-970. Expendable/Durable Items (Except Medical, Class V, Repair Parts, and Heraldic Items) (Available at http://armypubs.army.mil/doctrine/CTA_1.html .)

DA Pam 25-30. Consolidated Index of Army Publications and Blank Forms

DA Pam 700-142. Instructions for Type Classification, Materiel Release, Fielding, and Transfer

Publication Section III
Prescribed Forms

This section contains no entries.

Publication Section IV
Referenced Forms

Unless otherwise indicated, DA forms are available on the Army Publishing Directorate Web site ( www.apd.army.mil ).

DA Form 2028. Recommended Changes to Publications and Blank Forms

Glossary

Section I

Abbreviations

ABA

appropriation and budget activity

ACLDB

Army Central Logistics Data Bank

ACOM

Army command

AEMM

Army Enterprise Material Master

AESIP

Army Enterprise Systems Integration Program

AMC

U.S. Army Materiel Command

AMDF

Army master data file

AMP

Army Materiel Plan

APS

Army prepositioned stocks

AR

Army regulation

AUTH-LIN

authorized line item number

BCE

base-level commercial equipment

BOIP

basis of issue plan

CIC

controlled item code

CL

components list

CMC

commodity manager code

CTA

common table of allowances

DA

Department of the Army

DA Pam

Department of the Army pamphlet

DCS, G-3/5/7

Deputy Chief of Staff, G-3/5/7

DEL

delete

DIC

document identifier code

DODIC

Department of Defense identification code

FED LOG

Federal Logistics Data on Portable Media

FII

Federal item identification

FSC

Federal supply classification

HQDA

Headquarters, Department of the Army

I-LIN

identifies automatic data processing equipment line item number

JTA

Joint table of allowances

LCC

logistics control code

LIN

line item number

LOGSA

Logistics Support Activity

LP

limited procurement

MSCR

materiel status committee record

MSO

materiel status office

MTOE

modified table of organization and equipment

NIIN

national item identification number

NSN

national stock number

PCI

procurement appropriation commercial item

RDTE

research, development, test, and evaluation

RIC

routing identifier code

RICC

reportable item control code

SB

supply bulletin

SC

supply catalog

SCM

supply category of materiel

SLAMIS

Standard Study Number-Line Item Number Automated Management & Integrating System

SLIN

standard line item number

SUB-LIN

substitute line item number

TAADS

The Army Authorization Documents System

TDA

table of distribution and allowances

TM

technical manual

TOE

table of organization and equipment

UI

unit of issue

USAFMSA

U.S. Army Force Management Support Agency

Z-LIN

developmental line item number

Section II

Terms

Commercial items

Items which may be procured from commercial sources, either off-the-shelf or modified to meet Army requirements, without research and development effort, either by the commercial source or the Army.

Data originator

An Army activity having National Inventory Control Point or Service Item Control Center materiel management responsibilities that prepares and submits SB 700-20 transactions to AMC LOGSA.

Developmental item

An item that is under development or that was developed by the Army.

Federal item identification

A specific item description identified by an NSN and consisting of

a. Item description. (The minimum identification data, restricted to 21 spaces, required to list items in chapters 2, 6, and 8 of SB 700-20. It consists of the national item name or its abbreviation and enough additional data to distinguish between items identified by the same national item name.)

b. Nondevelopmental item. (Those items available for procurement to satisfy an approved materiel requirement with no expenditure of RDTE funds for development, modification, or improvement.)

c. Primary inventory control activity. (A single activity responsible for procuring, establishing, and controlling stock item accountability, cataloging, depot maintenance, and item disposal.)

d. Secondary inventory control activity. (A supply control activity responsible for controlling stock levels and maintaining item accountability when supply support is furnished by a different service or agency.)

Developmental line item number

A temporary number assigned by the AMC catalog data activity for planning purposes to a developmental or nondevelopmental item before type classified and replacement with an SLIN ( AR 708-1 and AR 70-1 ).

Section III

Special Terms

This section contains no entries.