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.
1A17.4. Part II – Format for requesting a Project Code.<br />
1–36<br />
AFMAN 23-110 Volume 1<br />
Part 4, Chapter 1<br />
Use automated input at: https://www.afmc-mil.wpafb.af.mil/HQ-AFMC/LG/LGR/LGRD/milgov/<br />
project.htm or format below.<br />
Date:____________<br />
Subject: Request for a Project Code Designator<br />
TO: HQ AFMC/LGRD<br />
1. Nickname (already) assigned (see Part I):<br />
___________________________________ _____________________________<br />
(Nickname) (MAJCOM assigning nickname)<br />
Project code category (circle one):<br />
<strong>Air</strong> <strong>Force</strong> recognition/processing only, Category A.<br />
Internal/external AF recognition, Category B.<br />
Service code (circle one) based on kind of requisition indicated by the first position of the DODAAC (rp<br />
30-35 of MILSTRIP transactions):<br />
"F" for FB, FE, FX, etc., accounts/requisitions.<br />
"E" for contractor (GFM) requisitions.<br />
"D" military assistance requisitions.<br />
HQ AFMC or AFSAC monitor’s name/symbol/telephone<br />
________________________________________________<br />
Alternate (ALC, MAJCOM) name/symbol/telephone:<br />
________________________________________________<br />
Announcement date desired:(may be left blank)<br />
Termination/review date not to exceed two years subsequent to announcement:<br />
Related meaning: [In 25 words or less describe the purpose for which the project code is assigned.]<br />
__________________________________________________<br />
Division Level Signature<br />
Title, Office Symbol