ADC 76

Air Force Unique Management Coding for NMCS/MICAP

1. ORIGINATOR: 

a. Service/Agency: U.S. Air Force, HQ AFMC/LGIA, Wright-Patterson AFB OH 

45433-5006

b. Originator: Mrs. Bobbie Ziolek

2. FUNCTIONAL AREA: Supply

3. REQUESTED CHANGE:

a. Title: Air Force Unique Management Coding for NMCS/MICAP

b. Description of Change: The Air Force will require the use of a new data element

to support legacy system requirements to adequately process supply transactions using 

EC/EDI processes. This data element will be used within our supply system to provide 

information/justification related to a NMCS/MICAP that is currently identified in the 

Required Delivery Date field (rp 62-64). When RDD coding identifies a NMCS condition 

(rp 62=N), a unique AF NMCS/MICAP justification code is reflected in rp 63-64. The 

two data elements work together. The N in rp 62 is already programmed in Special 

Requirements Code, but the new AF unique data element is requested for the DLMS in 

order to perpetuate the data in rp 63-64 required by our legacy systems. A separate 1270 

qualifier is being requested so that the AF will continue to maintain control over this 

unique code list. Other Services/Agencies using DLMS should take no action concerning 

this code, merely perpetuate it for AF continued use. Per SPRC 02-2 recommendation, 

DLMSO has included in this proposal a comparable description of the NMCS/MICAP 

justification coding for publication in MILSTRIP.

c. Procedures: 

(1) DoD. Modify MILSTRIP Appendix AP2.14, Priority Designators, Standard and 

Required Delivery Dates (Record Positions 60-61 and 62-64) to add new subparagraph:

AP2.14.12.1. USAF requisitioning activities may submit justification for 

identification of a NIMCS or Mission Impaired Capability Awaiting Parts(MICAP)

situation in accordance with USAF guidance. Unique USAF justification coding will be 

contained in rp 63-64 when rp 62 is N. Other Components will perpetuate justification 

data with no action.

(2) Air Force. The MICAP information (within the RDD field when rp 62 is N) is 

currently defined in the Air Force Manual (AFMAN) 23-110, Volume I, Part 4, Chapter 1, 

and Volume II, Part 2, Chapter 11 (refer to http://afpubs.hq.af.mil/pubfiles/af/23/afman23-

110/PUBS/AF/23/23011002/020211/020211.pdf).
4. REASON FOR CHANGE: This data is a unique data element for Air Force requisition 

processing that will continue to be used until a standard DoD weapon system coding 

methodology has been established to which the Air Force will have successfully 

reprogrammed.

5. ADVANTAGES AND DISADVANTAGES:

a. Advantages: The advantages are to Air Force legacy system requirements based 

upon the current operating software program logic. The transition from the current legacy 

management data to a standard weapons system coding structure will be a massive 

cataloging effort for the Air Force. This requested change provides a logical interim step 

towards a planned transition to a standard weapon system coding structure and will ensure an 

uninterrupted flow of the requisition processing capability with Air Force legacy systems.

b. Disadvantages: None known.

6. IMPACT:

Transaction Set(s): Request code additions to Version 4010 of the following ICs:

511M Requisition Modification

511R Requisition

846L Logistics Asset Support

869A Requisition Inquiry and Supply Assistance

869F Requisition Follow-Up

940R Material Release (4030 Version)

945A Materiel Release Advice

7. Segment(s): LQ

8. Data Elements: Versions 4010 and 4030 (as identified in paragraph 6, above), DE 1270 

Code List Qualifier Codes. Request addition of a separate AF unique qualifier under LQ 

Industry Code, DE 1270, and the associated code value implementation note to ICs/DSs

referenced under paragraph 6, above. Until the new ANSI code is assigned, use an interim

substitute code as indicated below:
RC Requirement Code

Federal Note: Use to identify the Air Force Urgency Justification Code indicating the 

urgency of need and type of requirement (justification) related to a Not Mission Capable 

Supply/Mission Impaired Capability Awaiting Parts (NMCS/MICAP) condition.

DLMS Note: Use in conjunction with Special Requirements Code N (2/LQ01/Code AL 

or perpetuated from DLSS Required Delivery Date field). This is an Air Force-unique 

data element, meaningful to the Air Force only. Non-Air Force Components perpetuate 

without action. An ANSI data maintenance request has been prepared to request a new 

data element 1270 code qualifier assignment for the Urgency Justification Code. The 

code source is identified as the Air Force Manual (AFMAN) 23-110, Volumes 1 and 2.

In addition, include the following clarifying DLMS note 3 in applicable DSs (2/LQ01/Code 

AL):

AL Special Requirements Code

Federal Note: Use to identify precedence, special handling, and processing 

requirements.

DLMS Note :

1. Under DLSS this is carried in the Required Delivery Date field. 

2. DLMS enhancement, see introductory DLMS note __. 

3. Use in conjunction with 2/LQ01/Code RC, Requirement Code, to complete the 

Air Force unique NMCS/MICAP data requirement.