CHAPTER 1 STANDARD SUPPLY CODES 1.1 ... - Air Force Link
CHAPTER 1 STANDARD SUPPLY CODES 1.1 ... - Air Force Link
CHAPTER 1 STANDARD SUPPLY CODES 1.1 ... - Air Force Link
You also want an ePaper? Increase the reach of your titles
YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.
ATTACHMENT 1A-17<br />
PROJECT <strong>CODES</strong><br />
(RECORD POSITION 57-59)<br />
1A17.1. Part I-General Guidelines when requesting a project code :<br />
1–34<br />
AFMAN 23-110 Volume 1<br />
Part 4, Chapter 1<br />
1A17.<strong>1.1</strong>. First obtain a nickname from your MAJCOM, if available; otherwise, contact HQ AFMC/<br />
A4LD, 4375 Chidlaw Rd, Rm B113, Wright-Patterson AFB OH 45433-5006 (DSN 787-5515) for an<br />
input form. If you need to obtain a project code number for your nickname, contact your AFMC System<br />
Control Officer (SCO) or product manager to process the request format located at https://<br />
www.afmc-mil.wpafb.af.mil/HQ-AFMC/A4/A4L/A4LD/milgov/project.htm.<br />
1A17.1.2. Nicknames. Nicknames should be available from your MAJCOM or HQ USAF.<br />
1A17.1.3. Project Codes. Project codes are used fo r the purpose of distinguishing requisitions and<br />
related documentation and shipments, as well as for the accumulation of intra-service performance<br />
and cost data related to exercises, maneuvers, and other distinct programs, projects, and operations<br />
(DOD Manual 4000.25-1, Appendix B13).<br />
1A17.1.3.1. Only approved project codes may be entered in record position (rp) 57-59 of requisitions<br />
and related transactions. The use of these positions for theater and regional purposes is prohibited.<br />
MAJCOMs and bases will not enter locally-assigned codes to highlight mission<br />
capability, special processing characteristics, etc., within the theater, MAJCOM, or base.<br />
1A17.1.3.2. JCS (9-series) project codes are ranked above other transactions within the same priority.<br />
Certain <strong>Air</strong> <strong>Force</strong> assigned codes have been authorized by HQ USAF/ILSP to be af forded<br />
expedite processing and expedite transportation. These HQ USAF/ILSP approved codes will have<br />
the required delivery date (RDD) designation of "777" programmatically assigned by the standard<br />
base-level computer (SBLC). Part III of this attachment outlines the procedures to be used in<br />
requesting the assignment of these project codes.<br />
1A17.1.3.3. Project codes will be effective for the duration of the need. They are assigned for a<br />
period of one or two years at which time they must be re-evaluated for deletion or renewal. Cancellation<br />
of a nickname automatically cancels the corresponding project code assigned.<br />
1A17.2. Project Code Announcements . Project code assignments and terminations are posted monthly<br />
on the project code web page https://www.afmc-mil.wpafb.af.mil/HQ-AFMC/LG/LGR/LGRD/<br />
milgov/project.htm, in two formats-Project Code Sequenc e and Alphabetic by Nickname sequence.<br />
Project Codes are assigned by two categories:<br />
1A17.2.1. Category A: Limited to contact points inside /within the <strong>Air</strong> <strong>Force</strong> (i.e., internal <strong>Air</strong> <strong>Force</strong><br />
inventory, transportation, and financial accounting activities).<br />
1A17.2.2. Category B: Includes both internal and external contact points, as other service/agency,<br />
DLA, and GSA inventory, transportation, and accounting. The other agencies make distribution to<br />
their concerned organizations/functions.