Attachment, ADC 1118 

Page 1 

ATTACHMENT TO ADC 1118 

Project Code Management System (PCMS) Procedures 

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: 

a. Technical POC: DLA Transaction Services

b. Functional POC: Mr. Lou Madrigal, Primary MILSTRIP Project Code Support

2. FUNCTIONAL AREA: Project Code Management 

3. REFERENCE:

a. DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), Appendix 2.13, Project Codes 

b. Approved DLMS Change (ADC) 19, DAASC Requisition Edit for OSD/CJCS 

Invalid/Expired Project Codes, dated November 8, 1999 

4. APPROVED CHANGE(S):

a. Overview of Change: This PCMS change establishes the initial baseline 

requirements for a new web-based project code management system to be hosted at DLA 

Transaction Services and updates project code management procedures accordingly. 

Significant changes resulting from the staffing of PDC 1118 are highlighted in GREEN. 

b. Background: 

(1) Reference 3.a. documents the procedures for project codes. Category 

A & B project codes are Service specific and coordinated internally or among the 

relevant Services/Agencies (S/A) through designated S/A project code representatives. 

Category C & D are common use project codes for which MILSTRIP has a greater role 

helping to manage.

(2) Defense Logistics Management Standards Office (DLMSO) provides 

an administrative support role for the assignment and lifecycle management of Category 

C & D project codes. DLMSO staff track which Category C & D project codes are 

available for assignment, which are still active, changes to project code status, and which 

expired codes should not be assigned to avoid premature repurposing. DLMSO staff 

distribute project code updates to the DOD Enterprise and notify requestors when codes 

are about to expire.

(3) On occasion, DLMSO staff will conduct research to identify new 

monitors/coordinators to assess whether old project codes are still valid and update the 

contact information.
Attachment, ADC 1118 

Page 2 

(4) Due to the manual nature of managing project codes, DLMSO worked 

with the Office of the Chairman of the Joint Chiefs of Staff (CJCS) on processes to 

ensure CJCS can act as flexibly and quickly as possible to issue project codes without 

having to worry about back and forth communication with DLMSO.

(5) There have been discussions in prior years between DLMSO and DLA 

Transaction Services about options to develop a central Web-based application to enable 

accurate, timely, and efficient management of project codes. Due to resource constraints 

the parties were unable to move forward on this project. Now DLA Transaction Services 

has developed similar solutions to benefit management of DoDAACs and fund codes, 

and the experience and technical design from those solutions can be applied to a project 

code management system. DLA Transaction Services is also a stakeholder in project 

codes, as reference 3.b. established some of the Category D project code related edits 

already supported by DLA Transaction Services during the processing of requisitions.

(6) While the primary focus of this change is on Category C & D project 

codes, the intent is to develop a solution which, if desired by the Services in the future, 

can most easily be upgraded to support Category A & B project code management as 

well.

c. Approved Change in Detail:

(1) Revise MILSTRIP Appendix 2.13 procedures for requesting and 

maintaining Category C & D project codes using web-based application, Project Code 

Management System (PCMS). When officially stood-up, PCMS will be the authoritative 

source for Category C & D project codes. Replace manual generation of project code 

memoranda with a near real-time PCMS generated email as updates occur, and enable the 

Project Code Master List to be automatically generated on demand from PCMS. 

Reorganize procedures and apply latest administrative style guidance to improve the 

process flow for readability. 

(2) Adjust procedures for OSD/CJCS Category C & D project code 

assignments from a general statement that they are to be assigned “for a specified period 

of time”, to a more concrete requirement that they have a termination date no longer than 

two years from their creation. Prior to the project code expiring, the 

monitors/coordinators evaluate the necessity for extending the project code for up to an 

additional two years as well as update contact information. The two year cap for reevaluating project codes ensures the process is not too burdensome for renewing longrunning programs, and avoids project codes sticking around long past when they should 

have been closed or contact information goes stale. 

(3) Expand the requisition validation edit of MILSTRIP, Appendix 2.13 

(Old: AP2.13.4.4.4.4, New: AP2.13.9.2.), to include Category C project codes. 

(a) Reference 3.b. established the edit to requisition-related 

transactions (DLMS 511R / MILSTRIP legacy Document Identification Code (DIC) 

A0_/AM_, DLMS 869F / MILSTRIP DIC AT_, and DLMS 517M / MILSTRIP DIC 
Attachment, ADC 1118 

Page 3 

APR) to validate that an included Category D project code exists (e.g., is active) and has 

not expired. Extending the edit check to Category C codes validates the accuracy and 

legitimacy of the project codes in DLMS transactions, and any subsequent analysis 

dependent on the project codes. 

(b) With the enhanced data content available under PCMS, the 

validation/expiration edit of Category C & D project codes will be modified to compare 

the ordinal date from the requisition document number in the DLMS 511R (DIC 

A0_/AM_)/869F (AT_)/517M (APR) to the expiration date of the project code. If the 

ordinal date is between the project code start and expiration date, then the project code 

will be perpetuated, even if the project code subsequently expires during the order 

fulfillment process for the document number; if the ordinal date either precedes the 

project code start or succeeds the expiration date, then the project code will be blanked 

out. This will eliminate unnecessary blanking out of the project code on requisition 

modifications, follow-ups, and requisition reinstatements where the project code was 

valid and active when the original requisition was generated. 

(4) Develop PCMS to support the MILSTRIP procedures and include the 

data field requirements of Enclosure 1. To assist developers with identifying business 

rules to incorporate into PCMS based on MILSTRIP procedures, Enclosure 2 provides an 

initial set of rules traced to the procedures of this ADC. Additional functional 

capabilities based on user roles are captured in Enclosure 3. The specific design details 

for implementing PCMS will be worked out with DLA Transaction Services. 

(5) PCMS Reports and Subscriptions 

(a) DLA Transaction Services will include a means for users to access 

a web report of active and recently expired project codes. See Enclosure 4 for a mockup 

of the report template indicating how data from PCMS database would be used to 

populate the report. 

(b) DLA Transaction Services will provide a service for authorized 

users to subscribe for updates to project codes. MILSTRIP Appendix 1.1 is updated 

(Enclosure 5) to include new templates for messages to be sent by PCMS to subscribers 

for notification of new project codes, project code extensions, and expiration date reached 

or cancellations before planned termination date (Enclosure 6). DLA Transaction 

Services will detail the requirements and procedures for parties to subscribe to receive 

notifications of project code updates. 

(c) To support consideration of extending project codes, DLA 

Transaction Services is requested to identify a means to query an appropriate source of 

requisition data in order to identify the last time the project code was included in a 

requisition and how many requisitions included the project code over the past three years. 

(d) DLA Transaction Services is also requested to evaluate the 

possibility of PCMS interfacing with billing transaction data to generate a report for 

OSD/CJCS to summarize billed dollars associated with Category C & D project codes. 
Attachment, ADC 1118 

Page 4 

(6) DLA transaction Services will support a web service capability for 

Components systems to receive current project code data as new project codes are 

assigned and updates occur. The content of the web service will be based on the similar 

information distributed in the notifications to subscribers, but the exact content and 

format will be coordinated with DLA Transaction Services. 

(7) Since all Category C & D project codes have been centrally managed 

for some time, the assignment logic based on the second position to avoid more than one 

party assigning the same code is to be removed from the procedures. Category C project 

codes will be expanded to include numerics (i.e. 3/alphanumeric/alphanumeric) and there 

will no longer be reserved pools of codes for exercises (3E_), Joint Materiel Priorities 

and Allocation Board (3J_ and 3H_), and rapid deployment/reaction forces (3R_). 

Category D project codes will no longer be divided into pools for OSD 

(9/numeric/numeric), scarce resources (9/numeric/alpha), release of safety stocks and war 

reserves (9/alpha/numeric), and infrastructure visibility and support (9/alpha/alpha). 

d. Revisions to DLM 4000.25 Manuals: Update MILSTRIP Appendix 2.13 to 

reflect planned use of PCMS for Category C & D project code management (Enclosure 

7), including additional PCMS support procedures such as formalizing stakeholder 

designation of their project code representatives (Enclosure 8) and elimination of the 

breakdown by second position alpha/numeric format. Add validation of Category C 

project codes.

e. Alternatives: None.

5. REASON FOR CHANGE: This change automates the work of maintaining the list 

of valid project codes and enables authorized individuals to assign and update project 

codes less encumbered by the manual procedures currently in place. PCMS ensures an 

authoritative data source for project code management within the global DOD domain 

and facilitates DAAS edit of new requisitions to ensure that only currently authorized 

project codes are used.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Eliminates manual tracking of Category C & D CJCS Project 

Codes making it easier to issue and maintain project codes. Also, automates the 

management of the project code lifecycle to minimize potential for errors, eliminate 

redundant project code usage, and keep supply systems informed of updates. PCMS is to 

be built leveraging as much as possible from existing capabilities for similar systems 

hosted by DLA Transaction Services, such as the DoDAAD Update Application and the 

Web Fund Code Application. 

b. Disadvantage: None. 

7. ADDITIONAL FUNCTIONAL REQUIREMENTS: While this ADC and the 

initial PCMS focus on Category C & D project codes, some aspects of the design 

requirements for PCMS will attempt to anticipate support for Category A & B projects 

codes to minimize significant development impacts should interested stakeholder 
Attachment, ADC 1118 

Page 5 

Components later seek to incorporate management of their Category A & B codes in 

PCMS. For instance, the PCMS database requirements include fields for multiple owners 

of a Category B project code.

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Changes which are 

not reliant on PCMS implementation are approved for immediate implementation. Target 

implementation for PCMS is February 2016. Changes to MILSTRIP procedures 

provided in Enclosure 7 which are dependent on PCMS are footnoted regarding delayed 

implementation and any manual process to be performed in the interim.

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: DLMSO and DLA Transaction Services 

estimate a combined average 6.5 man-hours for each project code currently generated, 

which would no longer be necessary with the proposed PCMS. A combined potential 

savings of an additional 2 man-hours per project code may be possible if all Components 

establish automated updates through web services, to replace manual system updates. 

There are currently 83 active project codes.

10. IMPACT 

a. New/Changed DLMS Data Elements: Update LOGDRMS to identify PCMS 

as the authoritative source for Category C & D project codes. 

b. Automated Information Systems (AIS): 

(1) DLA Transaction Services will provide a web service to enable feeds 

to Component AIS using its web service infrastructure. Components wishing to make 

use of the web service capability will need to coordinate service agreements with DLA 

Transaction Services. 

(2) Upon implementation of the web service, recommend Components 

systems implement validation/expiration edit checks for Category C & D project codes. 

c. DLA Transaction Services: Expand the requisition validation edit of 

MILSTRIP, Appendix 2.13, to include Category C project codes, and adjust the edit for 

valid project codes to compare the ordinal date from the requisition document number to 

the expiration date of the project code to determine if the project code should be blanked 

out. DLA Transaction Services will develop PCMS and manage the System Access 

Request (SAR) process for granting accounts to designated S/A project code 

representatives. The initial lists of business rules and explanations for PCMS design 

consideration are included in Enclosures 3 and 4. Requested PCMS reports are described 

in 4.c.(5) above and Enclosure 4. 

d. Non-DLA Logistics Management Standards Publications: CJCS J4 may 

determine a need to update CJCSI 4110.01D. 
PROJECT CODE MASTER FILE LAYOUT 

As of 18 November 2014 

Enclosure 1, ADC 1118 

Page 1 

ENCLOSURE 1 TO ADC 1118 

Project Code Management System Master File Layout 

Table Layout Explanation. The Type column identifies the data type and, when 

applicable, the maximum number of characters in parentheses. For the Use column: 

M = Mandatory, O = Optional, and C = Conditional. 

Layout for Project Code Table. Table detailing reserved, active, and expired project 

codes. 

Field Name Type Use Definition Business Rule

PROJECT_CAT VARCHAR2

(1) 

M Project Category: Identifies 

the scope of the project code. 

 Values = A, B, C, D 

CODE_OWNER VARCHAR2

(2) 

M Code Owner: Identifies the 

primary Service/Agency 

monitoring/coordinating the 

project code.

 Default from user profile. 

 At least one of POC_ONE, 

POC_TWO, POC_THREE must 

have the same value for their 

SERVICE_AGENCY_ROLE. 

 Values: 

o D = DoD MILSTRIP 

Administrator 

o F = US Air Force 

o H = OSD 

o J = CJCS 

o M = US Marine Corps 

o N = US Navy 

o S = Defense Logistics Agency 

o W = US Army 

CODE_PARTNER

_1 

VARCHAR2

(1) 

C Code Partner: For Category 

B project codes, identifies the 

secondary Service/Agency 

partner implementing use of 

the code.

 If PROJECT_CAT is “A”, “C” or 

“D”, then must be null. 

 If PROJECT_CAT is “B” and 

LIFECYCLE is not “R”, then must 

not be null. 

 Must be different than 

CODE_OWNER. 

 Values: 

o F = US Air Force 

o M = US Marine Corps 

o N = US Navy 

o S = Defense Logistics Agency 

o W = US Army 

o O = Other1

 

1

 If PCMS is expanded to manage Category B project codes, Services/Agencies will need to 

identify the code partner(s), as required. 
PROJECT CODE MASTER FILE LAYOUT 

As of 18 November 2014 

Enclosure 1, ADC 1118 

Page 2 

Field Name Type Use Definition Business Rule

CODE_PARTNER

_22

VARCHAR2

(1) 

C Code Partner: For Category 

B project codes, identifies a 

third Service/Agency partner 

implementing use of the code.

 If PROJECT_CAT is “A”, “C” or 

“D”, then must be null. 

 CODE_PARTNER_1 must not 

be null. 

 Must be different than 

CODE_OWNER and 

CODE_PARTNER_1. 

 At least one of POC_ONE, 

POC_TWO, POC_THREE must 

have the same value for their 

SERVICE_AGENCY_ROLE. 

 Values: 

o F = US Air Force 

o M = US Marine Corps 

o N = US Navy 

o S = Defense Logistics Agency 

o W = US Army 

o O = Other 

PROJECT_CODE VARCHAR2

(3) 

M Project Code: Identifies 

requisitions and related 

documentation as to special 

programs, exercises, projects, 

operations or other purposes. 

 If PROJECT_CAT equals “C” or 

“D”, there may be multiple versions 

of the same PROJECT_CODE with 

different CREATION_DATE values, 

but only one instance of the 

PROJECT_CODE can have 

LIFECYCLE equal to either R, P, or 

A. A PROJECT_CODE cannot be 

reused until all prior uses have 

LIFECYCLE equal to X with 

ACTUAL_EXPIRED_DATE older 

than five years. 

 Default is oldest unused of the 

available codes. 

 If PROJECT_CAT is “D”, then 

PROJECT_CODE must be 3 

characters formatted as “9” + 

[alphanumeric] + [alphanumeric]. 

 If PROJECT_CAT is “C”, then 

PROJECT_CODE must be 3 

alphanumeric characters3

, where 

the first character must be “3” or an 

alphabetic character. 

 

2

 Procedures do not limit use of Category B project codes to just two Services/Agencies. If more 

than 3 Service/Agencies are involved, the project code should be Category C. 3

 General rule is for Category C project codes to be formatted as “3” + [alphanumeric] + 

[alphanumeric], but there are some longstanding exceptions to this rule which may be better 

enforced at the application instead of the database to avoid issues with those existing exceptions. 
PROJECT CODE MASTER FILE LAYOUT 

As of 18 November 2014 

Enclosure 1, ADC 1118 

Page 3 

Field Name Type Use Definition Business Rule

SVC_APP VARCHAR2

(16) 

O Service Applicability: 

Service/Agency codes 

identifying the inclusion, or 

exclusion, of users of the 

code. 

 PROJECT_CAT must equal “C”. 

DUR_BEGIN_ 

DATE 

DATE C Duration Begin Date: The 

first day the project code is 

eligible to be used. 

 If LIFECYCLE is not R, then 

must not be null. 

 Date must be equal to or later 

than CREATION_DATE minus 7 

days.4

DUR_ 

CONTINUOUS 

BOOLEAN M Duration Continuous: 

Indicator that a MILSTRIP 

Administrator assigned project 

code does not have a set 

expiration date. 

 Default is “False”. 

 CODE_OWNER must be D. 

 Must be “False” if 

DUR_END_DATE is not null. 

 If LIFECYCLE is not R, then 

either DUR_CONTINUOUS is 

“True” or DUR_END_DATE must 

not be null. 

DUR_END_DATE DATE C Duration Original End Date: 

The day the project code is 

set to expire as of the 

establishment of the project 

code. 

 Must be null if 

DUR_CONTINUOUS is “True”. 

 Must be later than 

DUR_BEGIN_DATE. 

 Must be less than or equal to two 

years past DUR_BEGIN_DATE. 

DUR_EXTENSION

_DATE 

DATE C Duration Extension End 

Date: A day beyond the 

original expiration date 

reflecting an authorized 

extension for using the project 

code until this new expiration 

date. May be superseded as 

necessary with additional 

extensions. 

 Must be null if 

DUR_CONTINUOUS is “True”. 

 Must be later than 

DUR_BEGIN_DATE. 

 Must be later than 

DUR_END_DATE. 

 May only be entered and edited 

when LIFECYCLE is A. 

ACTUAL_ 

EXPIRED_DATE 

DATE C Actual Expired Date: The 

date the project code is no 

longer an active project code. 

 When set, must be earlier than 

or equal to current date. 

 Must be later than 

DUR_BEGIN_DATE. 

 If DUR_END_DATE is not null 

and DUR_EXTENSION_DATE is 

null, then must be earlier than or 

equal to DUR_END_DATE. 

 If DUR_EXTENSION_DATE is 

not null, then must be earlier than or 

equal to DUR_EXTENSION_DATE 

PROJECT_CODE

_NAME 

VARCHAR2

(40) 

C Project Code Text Name: A 

short, unclassified name for 

referring to the project. 

 If LIFECYCLE is not R, then 

must not be null. 

 

4

 May decide to enforce at the application instead of the database to avoid issues during initial 

population of existing project codes. 
PROJECT CODE MASTER FILE LAYOUT 

As of 18 November 2014 

Enclosure 1, ADC 1118 

Page 4 

Field Name Type Use Definition Business Rule

PROJECT_USE VARCHAR2

(500) 

O Project Use: A clear-text 

statement defining the 

intended use of the code and 

indicating those to whom it 

applies (unless the use is 

classified). 

REFERENCE VARCHAR2

(255) 

O References: Cite inter-S/A 

agreements and other 

documents when establishing 

or specifying special controls 

for the project. 

POC_ONE VARCHAR2

(20) 

M Primary POC: Foreign key to 

a POC_ID on the Points of 

Contact Table for the one with 

primary 

monitoring/coordinating 

responsibility. 

 The POC’s 

SERVICE_AGENCY_ROLE on the 

Points of Contact Table must equal 

the Project Code’s CODE_OWNER.

POC_TWO VARCHAR2

(20) 

C Secondary POC: When a 

second POC has 

monitoring/coordinating 

responsibility, this is a Foreign 

key to a POC_ID on the 

Points of Contact Table. 

 POC_ONE must not be null. 

POC_THREE VARCHAR2

(20) 

C Tertiary POC: When a third 

POC has 

monitoring/coordinating 

responsibility, this is a Foreign 

key to a POC_ID on the 

Points of Contact Table. 

 POC_ONE and POC_TWO must 

not be null. 

ORIG_POC_ONE VARCHAR2

(20) 

M Primary POC: Foreign key to 

a POC_ID on the Points of 

Contact Table for the one with 

primary 

monitoring/coordinating 

responsibility. 

 Auto-populated with POC_ONE 

at the time the project code is made 

active and then made non-editable. 

SC_EXCLUDE_ 

IND 

BOOLEAN M SC Not Authorized: Indicates 

project code is not authorized 

for use by Security 

Cooperation Customers. 

 Default is “False” 

NATO_ONLY BOOLEAN M NATO Use Only: Indicates 

project code is only authorized 

for use by NATO member 

countries.

 Default is “False” 

AUTO_ACTIVATE

_DATE 

DATE C Auto-Activate Date: A date 

provided to preset the 

activation of a project code. 

 If LIFECYCLE is “R”, then must 

be null. 

 If LIFECYCLE is “P”, then must 

not be null. 

 If LIFECYCLE is “A” or “X”, then 

AUTO_ACTIVATE_DATE is not 

editable. 

 When established must be later 

than current date (i.e. the date the 

LIFECYCLE is set to P), and less 

than or equal to current date + 30 

days. 
PROJECT CODE MASTER FILE LAYOUT 

As of 18 November 2014 

Enclosure 1, ADC 1118 

Page 5 

Field Name Type Use Definition Business Rule

LIFECYCLE VARCHAR2

(1) 

M Lifecycle: System managed 

code indicating the current 

state of the record as it 

progresses through the 

workflow to become an active 

code and held five years 

beyond expiration before 

allowing the code to be 

reassigned. 

 Values: 

o R = Reserved/Draft 

o P = Pending Auto Activation 

o A = Active 

o X = Expired 

 Status “R” is valid for 

CREATE_DATE + 1 year, after 

which the record is deleted. 

 Status “A” is valid when the 

current date is later than the 

DUR_BEGIN_DATE and the 

DUR_END_DATE, or when not null, 

the DUR_EXTENSION_DATE 

 Status “X” is valid when 

ACTUAL_EXPIRED_DATE is not 

null and equal to or earlier than 

current date. 

ACTION_CODE VARCHAR2

(1) 

M Action Code. System 

maintained code indicating 

type of action last taken on a 

record. 

 Values: A, C, D (Add, Change, 

Delete) 

 Records can only be deleted 

when LIFECYCLE = “R” or “P”. 

CREATE_DATE DATE M Creation Date. System 

maintained date a record was 

created. 

LAST_UPDATE DATE M Last Update Date. System 

maintained date a record was 

last updated. 

CUSTOMER_ 

USERID 

VARCHAR2

(20) 

M Customer User Identifier. 

System maintained identifier 

of a system user who updated 

the record. 
PROJECT CODE MASTER FILE LAYOUT 

As of 18 November 2014 

Enclosure 1, ADC 1118 

Page 6 

Layout for Points of Contact Table. Table for contact information of the project code 

owners which can be associated with one or more project codes. 

Field Name Type Use Definition Business Rule

POC_ID VARCHAR2

(20) 

M POC Identifier. System 

maintained identifier to 

uniquely identify a POC 

record. The Project Code 

Table will reference this ID 

whenever a POC is associated 

as the monitor/coordinator for 

a project code. 

 System generated identifier to 

uniquely identify points of contact 

records. 

SERVICE_ 

AGENCY_ROLE 

VARCHAR2

(1) 

M Service Agency Role: 

Identifies the organizational 

role/scope of project codes the 

POC monitors/coordinates. 

 Values: 

o D = DoD MILSTRIP 

Administrator 

o F = US Air Force 

o H = OSD 

o J = CJCS 

o M = US Marine Corps 

o N = US Navy 

o S = Defense Logistics Agency 

o W = US Army 

o X = SOCOM 

o O = Other 

POC_ORG VARCHAR2

(50) 

M Organization: Organization 

code and/or name as 

appropriate. 

POC_FIRST_ 

NAME 

VARCHAR2

(50) 

M POC Name: Given name of 

person designated as the point 

of contact for a project code. 

POC_LAST_ 

NAME 

VARCHAR2

(50) 

M POC Name: Surname of 

person designated as the point 

of contact for a project code. 

POC_COMM NUMERIC 

(10) 

O Commercial Telephone: A 

commercial telephone number 

for a POC. 

 Minimum 10 digits, maximum 10 

digits. 

POC_DSN NUMERIC 

(10) 

O DSN: A defense switched 

network number for a POC. 

 Minimum 7 digits, maximum 10 

digits. 

POC_EMAIL VARCHAR2

(50) 

O Email: An email address for a 

POC. 

 Must be a .mil domain 

ACTION_CODE VARCHAR2

(1) 

M Action Code. System 

maintained code indicating 

type of action last taken on a 

record. 

 Values: A, C, D (Add, Change, 

Delete) 

CREATE_DATE DATE M Creation Date. System 

maintained date a record was 

created. 

LAST_UPDATE DATE M Last Update Date. System 

maintained date a record was 

last updated. 

CUSTOMER_ 

USERID 

VARCHAR2

(20) 

M Customer User Identifier. 

System maintained identifier of 

a system user who updated 

the record. 
Enclosure 2, ADC 1118 

Page 1 

ENCLOSURE 2 TO ADC 1118 

Initial PCMS Business Rules 

This table provides a recommended initial set of business rules to assist with DLA Transaction 

Services development of PCMS. It is provided in the ADC for information of design aspects to 

be coordinated with DLA Transaction Services. The cited MILSTRIP justifications are based on 

the procedures in Enclosure 7 below. 

No. PROPOSED DESIGN RULE REASON 

1. User Roles will be established for: 

 OSD 

 CJCS 

 DoD MILSTRIP Administrator (Includes designated alternates to the 

Administrator) 

 Project Code / SPRC Representative (Read only access) 

MILSTRIP 

AP2.13.4.3. 

AP2.13.4.4. 

AP2.13.9.1.2. 

2. OSD/CJCS users are allowed to reserve, create, update, and terminate: 

 Category D project codes 

 Category C project codes formatted as (3/alphanumeric/alphanumeric) 

MILSTRIP 

AP2.13.4.3. 

AP2.13.4.4. 

3. DoD MILSTRIP Administrator users are allowed to reserve, create, update, and 

terminate Category C project codes formatted as (3/alphanumeric/alphanumeric), 

as well as codes CYK, JZC, JZM, JZO, and RBB. 

MILSTRIP 

AP2.13.4.3. 

AP2.13.4.3.2. 

4. Category C project codes are formatted (3/alphanumeric/alphanumeric) with 

exceptions to allow for CYK, JZC, JZM, JZO, and RBB. 

MILSTRIP 

AP2.13.4.3. 

AP2.13.4.3.2. 

5. Category D project codes are formatted (9/alphanumeric/alphanumeric) MILSTRIP 

AP2.13.4.4. 

6. Category C project codes must have a termination date no later than two years 

from their creation date, which may be extended prior to expiration for two years 

from the time of extension. MILSTRIP allows an exception to this rule for 

project codes designated for ongoing MILSTRIP procedures. 

MILSTRIP 

AP2.13.4.3. 

AP2.13.7. 

7. Category D project codes must have a termination date no later than two years 

from their creation date, which may be extended prior to expiration for two years 

from the time of extension. 

MILSTRIP 

AP2.13.4.4. 

AP2.13.7. 

8. DoD MILSTRIP Administrator users are the only ones allowed to set Category C 

project code as continuous for project codes for ongoing MILSTRIP procedures. 

MILSTRIP 

AP2.13.6.3. 
Enclosure 2, ADC 1118 

Page 2 

No. PROPOSED DESIGN RULE REASON 

9. When project codes are activated, extended, manually cancelled, or expire before 

the set termination date, a notification will be disseminated systemically by the 

Project Code Management System (PCMS) to: 

 the project code POC(s) (i.e., Monitor(s)/Coordinator(s)), 

 PCMS subscribers for project code updates. 

MILSTRIP 

AP2.13.6. 

AP2.13.6.2.2. 

AP2.13.6.3.1. 

AP2.13.6.3.2. 

AP2.13.6.3.3. 

10. When project codes are activated, extended, manually cancelled, or expire before 

the set termination date, a web service will disseminate the information to 

systems that have established agreements with DLA Transaction Services to 

receive updates. 

MILSTRIP 

AP2.13.6. 

AP2.13.6.2.2. 

11. Users will be able to produce reports (on demand or pre-generated) containing all 

active Category C & D project codes and those expired in the past six months, 

with exceptions where prohibited by security classification (See Enclosure 4 

below). An encrypted version of the report with FOUO information will be 

available to CAC/PKI verified users. 

MILSTRIP 

AP2.13.6.4.1. 

PII Policy 

12. Users will be able to perform ad hoc queries of project code data. Types of 

queries allowed will be coordinated with DLA Transaction Services. 

MILSTRIP 

AP2.13.6.4.2. 

13. DAAS can validate that a Category C or D project code in a DLMS transaction is 

valid and active in PCMS. 

MILSTRIP 

AP2.13.9.2. 

14. A project code can be reserved to be completed later. Within a year of being 

reserved the project code must be activated, or at least set to be activated, 

otherwise the reservation will be cancelled and the project code made available 

for another assignment. The reservation may be manually cancelled by the 

owning user role (e.g., only another CJCS user can cancel a reservation 

established by a CJCS user) and revert to an available code. 

MILSTRIP 

AP2.13.9.3.1. 

15. A project code can be set to become active on a specific date up to 30 days in the 

future. If prior to becoming active the pre-set activation is cancelled by a user of 

the controlling role (e.g., OSD), the project code will revert to reserved status, 

unless it must be cancelled due to already being reserved for more than one year. 

MILSTRIP 

AP2.13.9.3.2. 

16. Expired project codes cannot be reused until at least five years after the project 

code expired. 

MILSTRIP 

AP2.13.9.3.3. 

17. When presenting the next available project code for a new project code, PCMS 

will offer the code that has gone the longest since being expired. 

MILSTRIP 

AP2.13.9.3.3. 
Enclosure 3, ADC 1118 

Page 1 

ENCLOSURE 3 

User Role Functional Capabilities 

No. Functional Capability OSD/CJCS MILSTRIP 

Admin. 

Read-Only 

Access 

1. Update information for POCs. Yes Yes N/A 

2. Ability to check if a desired project code, 

other than the next available, is available 

for reservation/assignment. 

Cat. C & D Cat. C N/A 

3. Ability to reserve an available project 

code for up to one year. If not set to be 

active (or at least scheduled to be active) 

within the year, the reservation is 

removed and the project code is made 

available for use again. A reminder 

should be sent 30 days out from the one 

year mark. 

Cat. C & D Cat. C N/A 

4. Ability to schedule a reserved/draft 

project code to automatically become 

active on a specific future date within the 

next 30 days. 

Cat. C & D Cat. C N/A 

5. Proactive notification to POCs of project 

codes expiring within the next 30 days. Cat. C & D Cat. C N/A 

6. Proactive notification if the pool of 

available project codes for a category 

drops below twenty. [Need to validate the 

parameters for each pool of project 

codes.] 

Cat. C & D Cat. C & D N/A 

7. Subscribe to receive notifications of new, 

extended, and expired project codes. 

Automatic 

with account 

Automatic 

with account Yes 

8. Download FOUO Project Code report Yes Yes Yes 

9. Download Non-FOUO Project Code 

report Yes Yes Yes 

10. Perform ad hoc queries Yes Yes Yes 
Enclosure 4, ADC 1118 

Page 1 

ENCLOSURE 4 TO ADC 1118 

Project Code Report Template 

In the following report template purple highlight indicates content that will only be generated on the 

FOUO version of the report, yellow highlight indicates pseudo-code logic to generate standard report 

content based on system data, and grey highlight is for example data. Braces “{...}” encapsulate logic 

expressions, and brackets “[...]” contain PCMS data fields to populate the report, and parentheses “(...)” 

identify data formatting to be applied. 

For Official Use Only 

Effective: [REPORT_EFFECTIVE_DATE (DD Month YYYY)]

Project codes are used for the purpose of distinguishing requisitions and related documentation and 

shipments, as well as for the accumulation of intra-Service performance and cost data related to 

exercises, maneuvers, and other distinct programs, projects, and operations. Category D Project Codes 

are assigned for use by the Office of the Secretary of Defense/Chief, Joint Chiefs of Staff, while 

Category C Project Codes are common purpose Project Codes for use by all or specified Components. A 

complete set of rules and procedures is contained in DLM 4000.25-1, Military Standard Requisitioning 

and Issue Procedures (MILSTRIP), Appendix 2.13, which is available at www.dla.mil/j6/dlmso/eLibrary/Manuals/MILSTRIP/Default.asp

CATEGORY D 

9-SERIES, OFFICE OF THE SECRETARY OF DEFENSE/ 

CHIEF, JOINT CHIEFS OF STAFF, PROJECT CODES 

CODE DURATION USE/REFERENCE MONITOR/COORDINATOR 

{Include 

[PROJECT_

CODE] 

where 

[LIFECYCL

E] = A.} 

[DUR_BEGIN_DATE (Month DD, YYYY)] + 

{If DUR_EXTENSION_DATE is not null, 

Then “ Extended to” + 

[DUR_EXTENSION_DATE] (Month DD, 

YYYY), Or If DUR_END_DATE is null, 

Then “ to Continuing”, 

Else “ to ” [DUR_END_DATE] (Month DD, 

YYYY) } 

Examples: 

1) April 08, 2008 Extended to July 31, 2014 

2) October 13, 1976 to Continuing 

3) August 29, 2013 to August 31, 2014 

[PROJECT_CODE_NAME] + 

[PROJECT_CODE_DESC] 

{If SC_EXCLUDE_IND is 

True, Then “This project 

code may not be used by 

foreign countries.” 

{If NATO_ONLY is True, 

Then “This project code is 

for NATO use only.” 

[REFERENCE]

{For POC_ONE, complete from Point 

of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

{If POC_TWO is not null, complete 

from Point of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

{ If POC_THREE is not null, complete 

from Point of Contact Table: 

[ORGANIZATION] 
Enclosure 4, ADC 1118 

Page 2 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

The following Category D project codes have expired in the past six months 

CODE DURATION USE/REFERENCE MONITOR/COORDINATOR 

{Include 

[PROJECT_

CODE] 

where 

[ACTUAL_ 

EXPIRED_ 

DATE] = 

current date 

- 180 days.} 

[DUR_BEGIN_DATE (Month DD, YYYY)] + 

{If DUR_EXTENSION_DATE is not null, 

Then “ Extended to” + 

[DUR_EXTENSION_DATE] (Month DD, 

YYYY), Or If DUR_END_DATE is null, 

Then “ to Continuing”, 

Else “ to ” [DUR_END_DATE] (Month DD, 

YYYY) } 

“Expired on” 

[ACTUAL_EXPIRED_DATE] (Month DD, 

YYYY) 

Examples: 

1) April 08, 2008 Extended to July 31, 2014 

Expired on 

July 31, 2014

2) October 13, 1976 to Continuing 

Expired on 

October 25, 2013

3) August 29, 2013 to August 31, 2014 

Expired on 

August 31, 2014

[PROJECT_CODE_NAME] + 

[PROJECT_CODE_DESC] 

{If SC_EXCLUDE_IND is 

True, Then “This project 

code may not be used by 

foreign countries.” 

{If NATO_ONLY is True, 

Then “This project code is 

for NATO use only.” 

[REFERENCE]

{For POC_ONE, complete from Point 

of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

{If POC_TWO is not null, complete 

from Point of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

{ If POC_THREE is not null, complete 

from Point of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

For Official Use Only 

{Insert page break between Category D and C project code reports.}
Enclosure 4, ADC 1118 

Page 3 

For Official Use Only

CATEGORY C 

3-SERIES, COMMON USE, PROJECT CODES

CODE DURATION USE/REFERENCE MONITOR/COORDINATOR 

{Include 

[PROJECT_

CODE] 

where 

[LIFECYCL

E] = A.} 

Service 

Codes: 

[SVC_APP] 

[DUR_BEGIN_DATE (Month DD, YYYY)] + 

{If DUR_EXTENSION_DATE is not null, 

Then “ Extended to” + 

[DUR_EXTENSION_DATE] (Month DD, 

YYYY), Or If DUR_END_DATE is null, 

Then “ to Continuing”, 

Else “ to ” [DUR_END_DATE] (Month DD, 

YYYY) } 

Examples: 

1) April 08, 2008 Extended to July 31, 2014 

2) October 13, 1976 to Continuing 

3) August 29, 2013 to August 31, 2014 

[PROJECT_CODE_NAME] + 

[PROJECT_CODE_DESC] 

{If SC_EXCLUDE_IND is 

True, Then “This project 

code may not be used by 

foreign countries.” 

{If NATO_ONLY is True, 

Then “This project code is 

for NATO use only.” 

[REFERENCE]

{For POC_ONE, complete from Point 

of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

{If POC_TWO is not null, complete 

from Point of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

{ If POC_THREE is not null, complete 

from Point of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

The following Category C project codes have expired in the past six months 

CODE DURATION USE/REFERENCE MONITOR/COORDINATOR 

{Include 

[PROJECT_

CODE] 

where 

[ACTUAL_ 

EXPIRED_ 

DATE] = 

current date 

- 180 days.} 

Service 

Codes: 

[SVC_APP] 

[DUR_BEGIN_DATE (Month DD, YYYY)] + 

{If DUR_EXTENSION_DATE is not null, 

Then “ Extended to” + 

[DUR_EXTENSION_DATE] (Month DD, 

YYYY), Or If DUR_END_DATE is null, 

Then “ to Continuing”, 

Else “ to ” [DUR_END_DATE] (Month DD, 

YYYY) } 

“Expired on” 

[ACTUAL_EXPIRED_DATE] (Month DD, 

YYYY) 

Examples: 

1) April 08, 2008 Extended to July 31, 2014 

Expired on 

July 31, 2014

[PROJECT_CODE_NAME] + 

[PROJECT_CODE_DESC] 

{If SC_EXCLUDE_IND is 

True, Then “This project 

code may not be used by 

foreign countries.” 

{If NATO_ONLY is True, 

Then “This project code is 

for NATO use only.” 

[REFERENCE]

{For POC_ONE, complete from Point 

of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

{If POC_TWO is not null, complete 

from Point of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 
Enclosure 4, ADC 1118 

Page 4 

2) October 13, 1976 to Continuing 

Expired on 

October 25, 2013

3) August 29, 2013 to August 31, 2014 

Expired on 

August 31, 2014

{ If POC_THREE is not null, complete 

from Point of Contact Table: 

[ORGANIZATION] 

[POC_NAME] 

“Comm: ” + [POC_COMM] (###-###-

####) 

“DSN: ” + [POC_DSN] (###-###-####) 

“Email: ” [POC_EMAIL] } 

For Official Use Only
Enclosure 5, ADC 1118 

Page 1 

ENCLOSURE 5 

AP1. APPENDIX 1 

FORMS/MESSAGE FORMATS INDEX 

Number Title 

AP1. FORMS/MESSAGE FORMATS INDEX 

AP1.1. FORMS/MESSAGE FORMATS INTRODUCTION 

AP1.2. DD FORM 1348, DOD SINGLE LINE ITEM REQUISITION SYSTEM DOCUMENT (MANUAL) 

AP1.3. DD FORM 1348M, DOD SINGLE LINE ITEM REQUISITION SYSTEM DOCUMENT 

(MECHANICAL) 

AP1.4. DD FORM 1348-5, NOTICE OF AVAILABILITY/SHIPMENT 

AP1.5. STANDARD FORM 344, MULTIUSE STANDARD REQUISITIONING/ISSUE SYSTEM 

DOCUMENT 

AP1.6. DD FORM 1348-6, DOD SINGLE LINE ITEM REQUISITION SYSTEM DOCUMENT 

(MANUAL-LONG FORM) 

AP1.7. RESERVED 

AP1.8. MILSTRIP MESSAGE REQUISITION 

AP1.9. MILSTRIP MESSAGE FOLLOW-UP 

AP1.10. MILSTRIP MESSAGE SUPPLY ASSISTANCE REQUEST 

AP1.11. ABBREVIATED MILSTRIP MESSAGE SUPPLY STATUS 

AP1.12. ABBREVIATED MILSTRIP MESSAGE SHIPMENT STATUS 

AP1.13. MILSTRIP PART NUMBER/NON-NSN MESSAGE REQUISITION 

AP1.14. RESERVED 

AP1.15. MESSAGE REQUEST FOR SPECIAL MATERIEL OBLIGATION VALIDATION 

AP1.16. MESSAGE REPLY TO SPECIAL MATERIEL OBLIGATION VALIDATION REQUEST 

AP1.17. REQUEST FOR VALIDATION OF MATERIEL OBLIGATIONS (FMS AND GRANT AID 

TRANSACTIONS) (FROM SOURCE OF SUPPLY TO ILCO) 

AP1.18. FOLLOW-UP REQUEST FOR VALIDATION OF MATERIEL OBLIGATIONS (FMS AND 

GRANT AID TRANSACTIONS) (FROM SOURCE OF SUPPLY TO ILCO) 
Enclosure 5, ADC 1118 

Page 2 

Number Title 

AP1.19. REQUEST FOR VALIDATION OF MATERIEL OBLIGATIONS (FMS AND GRANT AID 

TRANSACTIONS) (FROM ILCO TO SAOs) 

AP1.20. FOLLOW-UP REQUEST FOR VALIDATION OF MATERIEL OBLIGATIONS (FMS AND 

GRANT AID TRANSACTIONS) (FROM ILCO TO SAOs) 

AP1.21. REPORT OF VALIDATION OF MATERIEL OBLIGATIONS 

AP1.22. ABBREVIATED MESSAGE ASSET REPORT, ETC. (MATERIEL RETURNS PROGRAM) 

AP1.23. MASS OR UNIVERSAL CANCELLATION MESSAGE 

AP1.24. DEFENSE LOGISTICS MANAGEMENT SYSTEM/LEGACY MILSTRIP REVISION 

IMPLEMENTATION REPORT 

AP1.25. ISSUE RELEASE/RECEIPT DOCUMENT LASER PRINTED FORM WITH LOGMARS BAR 

CODING 

AP1.26. RESERVED 

AP1.27. ISSUE RELEASE/RECEIPT DOCUMENT PREPRINTED FORM WITHOUT LOGMARS BAR 

CODING DATA 

AP1.28. RESERVED 

AP1.29. ISSUE RELEASE/RECEIPT DOCUMENT LASER PRINTED FORM WITH LOGMARS BAR 

CODING FOREIGN MILITARY SALES 

AP1.30. RESERVED 

AP1.31. ISSUE RELEASE/RECEIPT DOCUMENT WITH ADDRESS LABEL 

AP1.32. MESSAGE REQUEST FORM DEFENSE AUTOMATIC ADDRESSING SYSTEM MATERIEL 

OBLIGATION VALIDATION RESPONSE 

AP1.33. QUARTERLY INTRANSIT TO DLA DISPOSITION SERVICES FIELD OFFICE REPORT 

AP1.34. UNAUTHORIZED PRIORITY DESIGNATOR ASSIGNMENT REPORT 

AP1.35. ISSUE RELEASE/RECEIPT DOCUMENT (IRRD) (DD FORM 1348-1A) WITH CODE 39 

(THREE OF NINE) BAR CODES AND PDF417 TWO-DIMENSIONAL (2D) BAR CODE

AP1.36 ISSUE RELEASE/RECEIPT DOCUMENT (IRRD) (DD FORM 1348-1A or DD Form 1348-2) 

CONTINUATION PAGE 

AP1.37 TEMPLATES FOR PROJECT CODE MANAGEMENT SYSTEM GENERATED PROJECT 

CODE DISSEMINATION NOTICES 

AP1.38 APPOINTMENT LETTER TEMPLATE FOR SERVICE/AGENCY PROJECT CODE 

REPRESENTATIVE 
Enclosure 6, ADC 1118 

Page 1 

ENCLOSURE 6 TO ADC 1118 

AP1.37. APPENDIX 1.37 

Templates For Project Code Management System 

Generated Project Code Dissemination Notices 

AP 1.37.1. The message templates of this appendix support the procedures of MILSTRIP 

Appendix 2.13, Project Codes. 

 AP 1.37.1.1 The notices are automatically generated by the Project Code Management 

System (PCMS) and distributed to subscribers to announce new project codes, note when the 

termination date is extended, or project code(s) close either by reaching the current termination 

date or by intent to close the project code earlier than the last announced termination date. 

 AP 1.37.1.2 In the following templates yellow highlight indicates pseudo-code logic to 

generate the notice content based on system data and grey highlight is for example data. Within 

the highlighted areas, braces “{...}” encapsulate logic expressions, brackets “[...]” contain 

PCMS data fields to populate the report, and parentheses “(...)” identify data formatting to be 

applied. 
Enclosure 6, ADC 1118 

Page 2 

AP 1.37.2. New Project Code Notice. This template is used by PCMS to generate notifications 

of new project codes. 

 {Notice generation date (Month DD, YYYY)} 

TO: MILSTRIP PROJECT CODE CONTACTS 

SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Project Code [PROJECT_CODE], [PROJECT_CODE_NAME] 

This notice promulgates Project Code [PROJECT_CODE]. New Project Code 

[PROJECT_CODE] is assigned by the {Full name for [CODE_OWNER]} for use by the 

Military Services and DOD Agencies in support of [PROJECT_CODE_NAME]. 

Policy and procedures for project codes are contained in DLM 4000.25-1, Military 

Standard Requisition Issue Procedures (MILSTRIP) Appendix 2.13. A listing of Category C and 

D Project Codes may be accessed from the Project Code Management System maintained at 

DLA Transaction Services or : 

https://www.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/ProjCodes/CD_ProjCd.docx (For 

Official Use Only (FOUO) version, including point of contact information), or 

www.dla.mil/j-6/dlmso/eLibrary/ServicePoints/CD_ProjCd_nopoc.docx (general access).

Project Code [PROJECT_CODE] is assigned as follows: 

Code Duration Use/Reference Monitor/Coordinator 

[PRO

JECT

_COD

E]

[DUR_BEGIN_DATE 

(Month DD, YYYY)] + 

{If DUR_END_DATE is 

null, 

Then “ to Continuing”, 

Else “ to ” 

[DUR_END_DATE] (Month 

DD, YYYY) } 

Examples: 

1) October 13, 1976 to 

Continuing 

2) August 29, 2013 to 

August 31, 2014

[PROJECT_CODE_NAME] + 

[PROJECT_CODE_DESC] 

{If SC_EXCLUDE_IND is True, Then “This 

project code may not be used by foreign 

countries.” 

{If NATO_ONLY is True, Then “This project 

code is for NATO use only.” 

[REFERENCE]

[ORGANIZATION] 

 “Comm: “ + 

[POC_COMM] (###-###-

####) 

“DSN: “ + [POC_DSN] 

(###-###-####) 

Addressees may direct their questions to the DOD MILSTRIP Administrator. All others 

please contact your Component Supply PRC Representative. 
Enclosure 6, ADC 1118 

Page 3 

AP 1.38.3. Project Code Extension Notice. This template is used by PCMS to generate 

notifications when the project code(s) owner extends the termination date. 

{Notice generation date (Month DD, YYYY)} 

TO: MILSTRIP PROJECT CODE CONTACTS 

SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Project Codes C and D Updates 

 

This notice promulgates the extension of Project Code [PROJECT_CODE]. 

Policy and procedures for project codes are contained in DLM 4000.25-1, Military 

Standard Requisition Issue Procedures (MILSTRIP) Appendix 2.13. A listing of Category C and 

D Project Codes may be accessed from the Project Code Management System maintained at 

DLA Transaction Services: 

https://www.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/ProjCodes/CD_ProjCd.docx (For 

Official Use Only (FOUO) version, including point of contact information), or 

www.dla.mil/j-6/dlmso/eLibrary/ServicePoints/CD_ProjCd_nopoc.docx (general access).

Project Code [PROJECT_CODE] is updated as follows: 

Code Duration Use/Reference Monitor/Coordinator 

PROJ

ECT_C

ODE] 

[DUR_BEGIN_DAT

E (Month DD, 

YYYY)] + 

“ Extended to” + 

[DUR_EXTENSION

_DATE] (Month 

DD, YYYY) 

Example: 

April 08, 2008 

Extended to July 

31, 2014

[PROJECT_CODE_NAME] + 

[PROJECT_CODE_DESC] 

{If SC_EXCLUDE_IND is True, Then “This 

project code may not be used by foreign countries.” 

{If NATO_ONLY is True, Then “This project 

code is for NATO use only.” 

[REFERENCE]

[ORGANIZATION] 

 “Comm: “ + 

[POC_COMM] (###-###-

####) 

“DSN: “ + [POC_DSN] 

(###-###-####) 

Addressees may direct their questions to the DOD MILSTRIP Administrator. All others 

please contact your Component Supply PRC Representative. 
Enclosure 6, ADC 1118 

Page 4 

AP 1.37.4. Closing of a Project Code Notice. This template is used by PCMS to generate 

notifications when the project code(s) reach the current termination date or the project code 

owner decides to closes use of the code earlier than the last announced termination date. There is 

no notification sent when a project code closes on the published termination date. 

{Notice generation date (Month DD, YYYY)} 

TO: MILSTRIP PROJECT CODE CONTACTS 

SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Project Codes C and D Updates 

 

This notice promulgates the expiration of Project Code [PROJECT_CODE]. 

Policy and procedures for project codes are contained in DLM 4000.25-1, Military 

Standard Requisition Issue Procedures (MILSTRIP) Appendix 2.13. A listing of Category C and 

D Project Codes may be accessed from the Project Code Management System maintained at 

DLA Transaction Services: 

https://www.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/ProjCodes/CD_ProjCd.docx (For 

Official Use Only (FOUO) version, including point of contact information), or 

www.dla.mil/j-6/dlmso/eLibrary/ServicePoints/CD_ProjCd_nopoc.docx (general access).

Project Code [PROJECT_CODE] is updated as follows: 

Code Duration Use/Reference Monitor/Coordinator 

PROJ

ECT_C

ODE] 

[DUR_BEGIN_DAT

E (Month DD, 

YYYY)] + 

{If 

DUR_EXTENSION_

DATE is not null, 

Then “- Extended to” 

+ 

[DUR_EXTENSION

_DATE] (Month DD, 

YYYY), Or If 

DUR_END_DATE is 

null, 

Then “ to 

Continuing”, 

Else “ to ” 

[DUR_END_DATE] 

(Month DD, YYYY) } 

Expired on 

[ACTUAL_EXPIRED

_DATE] (Month DD, 

YYYY) 

Examples: 

1) April 08, 2008 

Extended to July 31, 

[PROJECT_CODE_NAME] + 

[PROJECT_CODE_DESC] 

{If SC_EXCLUDE_IND is True, Then “This 

project code may not be used by foreign countries.” 

{If NATO_ONLY is True, Then “This project 

code is for NATO use only.” 

[REFERENCE]

[ORGANIZATION] 

 “Comm: “ + 

[POC_COMM] (###-###-

####) 

“DSN: “ + [POC_DSN] 

(###-###-####) 
Enclosure 6, ADC 1118 

Page 5 

2014 

Expired on 

October 25, 2013

2) October 13, 1976 

to Continuing 

Expired on 

October 25, 2013

3) August 29, 2013 

to August 31, 2014 

Expired on 

October 25, 2013

Addressees may direct their questions to the DOD MILSTRIP Administrator. All others 

please contact your Component Supply PRC Representative. 
Enclosure 7, ADC 1118 

Page 1 

ENCLOSURE 7 TO ADC 1118 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

AP2.13. APPENDIX 2.13 

PROJECT CODES 

NUMBER OF CHARACTERS: Three. 

TYPE OF CODE: Alpha/Numeric. 

EXPLANATION: Identifies requisitions and related 

 documentation as to special programs, 

 exercises, projects, operations, or other 

 purposes. 

LEGACY RECORD POSITION(S): 57-59. 

DLMS SEGMENT/QUALIFIER: LQ Segment, LQ01 Qualifier 781

AP2.13.1. Project codes are used to distinguish requisitions and related 

documentation and shipments, and to accumulate Service/Agency (S/A) 

performance and cost data related to exercises, maneuvers, and other distinct 

programs, projects, and operations. The project code shall be entered in rp 57-

59. If no project code is applicable, rp 57-59 shall be left leave blank in the 

applicable transaction.

Distinguish legacy 

and DLMS uses of 

project codes. 

Remove 

duplicative 

information about 

the legacy record 

positions. 

AP2.13.2. Project codes, other than Office of the Secretary of Defense 

(OSD)/Chairman of the Joint Chiefs of Staff (CJCS) assigned codes, do not 

provide nor imply any priority or precedence for requisition processing or supply 

decisions. Project codes are not related to priority in any respect and, when 

used, do not alter nor override the priority assigned to a requisition or shipment. 

Requisitions containing project codes and shipments related thereto willshall be 

processed strictly under the assigned priority designator and implied/requested 

preferential treatment to the contrary willshall be disregarded. 

Administrative 

edits. 

AP2.13.3. Project codes willshall be perpetuated in all related documentation 

and willshall appear as a part of shipping container markings. Recognition of 

project codes by suppliers in another Services/Agency (S/A) and the resultant 

special handling afforded requisitions and shipments willshall be limited to: 

Administrative 

edits. 

 

1

 ADC 1043 added the Standard Line of Accounting (SLOA) requirement for a project code element 

in the FA2 segment, but also noted that the SLOA project code may or may not be the same as the 

supply project code. 
Enclosure 7, ADC 1118 

Page 2 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.3.1. Shipment Consolidation. Criteria for consolidation of project 

code materiel is published in DTR 4500.9-R. 

 AP2.13.3.2. Container Marking. Shipments willshall be marked as 

prescribed in MIL-STD-129, as amended. 

Administrative 

edit. 

 AP2.13.3.3. Shipment Release/Movement Control. At the time of project 

announcement for contingencies and similar rapid response situations, the 

initiating S/A willshall provide the instructions as to procedures to be followed on 

requisitions which must arrive at destinations within specified time periods. 

Administrative 

edit. 

AP2.13.4. Project codes are categorized into four groups and the authority to 

assign project codes varies by category. The following paragraphs provide the 

definitions of each category of project codes and identify the S/A which is 

authorized to assign each category of project code. The authoritative source 

for each category of project codes is either maintained with the Services or 

the Project Code Management System (PCMS) as part of DLA Transaction 

Services logistics transaction processing infrastructure.2

Clarification of the 

authoritative 

source for project 

codes after PCMS 

is initially stood 

up. 

 AP2.13.4.1. Category A. For use when no meaning of the code willshall be 

perpetuated outside the originating S/A. The code willshall be perpetuated in all 

related documentation and willshall appear as a part of the shipping container 

markings. Project codes in cCategory A may be assigned by those S/As 

identified in Appendix 2.2 by a distinct S/A code, Federal Standard Requisitioning 

and Issue Procedures (FEDSTRIP) activity address code (AAC), and by those 

Agencies using the multiuse Service Code H. Category A project codes are 

managed by the Services and are not included in the PCMS.3

Administrative 

edits. Explain that 

Category A project 

codes are 

managed by the 

individual Services 

outside PCMS. 

 

2

 ADC 1118 initiated the development of PCMS. Until PCMS is implemented, the authoritative 

source for Category C & D project codes is MILSTRIP Appendix 2.13, posted to the DLMSO 

website: www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp 3

 Addition of Category A and/or B project codes may be addressed as a future enhancement to 

PCMS based on S/A requirements. 
Enclosure 7, ADC 1118 

Page 3 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.4.2. Category B. For use when recognition and exceptional 

processing actions have been prearranged between specified S/As. Category B 

project codes willshall be announced by the managing S/A only to participating 

S/As, with the information described in the format provided below in 

AP2.13.6.3. Assignment authority is the same as for cCategory A. Category B 

project codes are managed by the Services and are not included in PCMS.4

Clarified where 

the information of 

the announcement 

is detailed and 

made clear that 

Category B project 

codes are 

managed by the 

individual Services 

outside PCMS. 

 AP2.13.4.3. Category C (3/alphanumeric/alphanumeric). Assigned for 

common purpose use by all or specified S/As. Category C project code(s) are 

assigned for a specified period of time, not to exceed two years initially, 

with an exception for project codes assigned to ongoing MILSTRIP 

procedures. The project code monitor/coordinator will evaluate the need to 

extend and update Category C project codes prior to expiration. Approved 

category C project codes shall be disseminated electronically to the designated 

project code contact points and Supply Process Review Committee (SPRC) 

members. All cCategory C codes are managed in PCMS by OSD, Office of 

CJCS, or the DoD Military Standard Requisition and Issue Procedures 

(MILSTRIP) Administrator.5 published on the DLA Logistics Management 

Standards Website unless prohibited by security classification. 

www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/milstrip_pubs.asp. 

Expands pool of 

codes to include 

numerics. Clarifies 

that Category C 

project codes are 

to have a defined 

termination date of 

no more than two 

years out, to 

ensure the project 

codes are reevaluated and 

updated. Exception 

for project codes 

related to ongoing 

procedures. 

Dissemination 

rules consolidated 

in AP2.13.6. 

 AP2.13.4.3.1. Assignment of cCategory C project codes may be 

requested by OSD/CJCS or by S/As. S/A requests willshall be forwarded by the 

Supply Process Review Committee (SPRC) representative to the DoD Military 

Standard Requisition and Issue Procedures (MILSTRIP) Administrator by the 

designated S/A project code contact points. Such requests mustshall: 

Administrative 

edits. 

 AP2.13.4.3.1.1. Include a statement of the intended use. 

 

4

 Ibid. 

5 ADC 1118 initiated the development of PCMS. Until PCMS is implemented, the authoritative 

source for Category C & D project codes is MILSTRIP Appendix 2.13, posted to the DLMSO 

website: www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp 
Enclosure 7, ADC 1118 

Page 4 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.4.3.1.2. Indicate the S/As which willshall be involved 

(including designator of applicable S/A codes). 

Administrative 

edit. 

 AP2.13.4.3.1.3. Provide the effective date and termination date of 

the code. 

 AP2.13.4.3.1.4. Identify at least one monitor/coordinator. Consolidated from 

AP2.13.4.4.4.1.1. 

removed below.

 AP2.13.4.3.1.5. Note any references. Consolidated from 

AP2.13.4.4.4.1.1. 

removed below.

 AP2.13.4.3.2. The following special assignments are in effect: Eliminated as only 

one exception 

assignment rule 

will remain. 

 AP2.13.4.3.2.1. Project Codes CYK, JZC, JZM, JZO, and RBB are 

designated as cCategory C and are authorized exceptions to the normal 

cCategory C 3/alphanumeric/alphanumeric structure. 

Add existing CYK 

and JZO as format 

exceptions. 

 AP2.13.4.3.2.2. Project codes in the 3E_ series are reserved for 

assignment for exercises (e.g., military/mobilization exercises). 

Removed to open 

up the series as 

available for any 

Category C code 

assignment. 

 AP2.13.4.3.2.3. Project codes in the 3J_ and 3H_ series are 

reserved for assignment by the Joint Materiel Priorities and Allocation Board 

(JMPAB). 

 AP2.13.4.3.2.4. Project codes in the 3R_ series are reserved for 

assignment in support of rapid deployment/reaction forces responding to 

contingencies. 
Enclosure 7, ADC 1118 

Page 5 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.4.4. Category D (9/alphanumeric/alphanumeric). OSD/CJCS 

project codes. Requisitions and materiel releases with cCategory D project codes 

willshall be ranked above all other requisitions with the same priority designators 

for processing purposes. All category D project codes are in the 9_ series. 

Authorization for use of Category D project code(s) will be for a specified 

period of time, not to exceed two years initially. OSD/CJCS will evaluate the 

need to extend and update Category D project codes prior to expiration. All 

Category D codes are managed in PCMS by OSD and CJCS.6

 The following 

definitions of specific series apply: 

Administrative 

edit. Clarifies that 

Category D 

project codes are 

to have a defined 

termination date of 

no more than two 

years out, to 

ensure the project 

codes are reevaluated and 

updated. 

 AP2.13.4.4.1. 9/numeric/numeric - reserved for assignment by OSD. 

Specific use of the code is to be determined by OSD. Such codes shall be 

monitored by DASD (L&MR) SCI in coordination with the DoD MILSTRIP 

Administrator. 

Removed to open 

up the 9 series as 

available for any 

Category D code 

assignment. 

 AP2.13.4.4.2. 9/numeric/alpha - identifies allocation at the level of the 

Chairman, Joint Chiefs of Staff of significant materiel or equipment items that are 

on hand or are becoming available for issue when resources are not sufficient to 

meet all requirements. (This series of project codes is used for scarce resource 

allocation.) 

 AP2.13.4.4.3. 9/alpha/numeric - identifies the establishment and 

subsequent release, at the level of the Chairman, Joint Chiefs of Staff, of 

emergency, reserve, or specified purpose stocks which are on hand or are 

becoming available. (This series of project codes is used as authority to release 

resources which are being held for contingencies; for example, safety stocks and 

war reserves.) 

 AP2.13.4.4.4. 9/alpha/alpha - identifies a project, operation, program 

force, or activity sanctioned by the Chairman, Joint Chiefs of Staff acting on 

behalf of the Joint Chiefs of Staff, or by the Chairman acting on behalf of the 

Secretary of Defense which requires heightened logistic infrastructure visibility 

and support. 

 

6

 Ibid. 
Enclosure 7, ADC 1118 

Page 6 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.4.54.4.1. OSD and CJCS Assignment Requests Subsections 

reorganized out 

from Category D 

and applied 

specifically to 

OSD and CJCS. 

 AP2.13.4.4.4.1.1. S/A requestors of project codes shall 

provide Service Code(s),. Use/References, Monitor/Coordinator, Effective Date, 

and Termination Date. This information is necessary for to produce the project 

code announcement required by paragraph AP2.13.5., below. 

Consolidated into 

AP2.13.4.3.1. 

above 

 AP2.13.4.5.14.4.1.2. OSD project codes will be assigned only to 

projects and programs clearly of direct interest to the Secretary of Defense 

(SECDEF). Requests for assignment of OSD project code(s) willshall be 

submitted to the DASD (L&MR) SCI. An information copy of the request willshall 

be provided to the DoD MILSTRIP Administrator. The DoD MILSTRIP 

Administrator shall assign the appropriate project code uUpon approval of the 

request by the DASD (L&MR) SCI, OSD will complete assignment of the 

project code in PCMS, or may request CJCS record the project code in 

PCMS on behalf of OSD7. 

Consolidated from 

AP2.13.4.4.4.2.1. 

below. OSD is to 

assign the project 

code using PCMS, 

but the rarity of 

OSD project code 

assignments 

requires that OSD 

be able to request 

CJCS record the 

project code on 

OSD’s behalf in 

cases should the 

OSD account(s) 

lapse. 

 

7

 Ibid. 
Enclosure 7, ADC 1118 

Page 7 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.4.5.2.4.4.1.3. CJCS project codes will be assigned only to 

projects and programs clearly of direct interest to the CJCS acting on 

behalf of the SECDEF. The Force/Activity Designators (F/AD) to be used in 

conjunction with the CJCS project code should be designated in the 

authorization. Requests for assignment of CJCS project code(s) willshall be 

submitted to the JMPAB, an agency of the Chairman, Joint Chiefs of Staff, and 

approved through the appropriate office listed below to authorize CJCS to 

complete assignment of the project code in PCMS8

: 

Reorganizes 

special CJCS 

assignment rules 

out from under 

Category D to 

apply to both C & 

D. Additions 

consolidated from 

AP2.13.4.4.4.2.2. 

removed below. 

Clarify that the 

CJCS will assign 

the project code 

using PCMS. 

 AP2.13.4.5.2.4.4.1.3.1. Service Headquarters. Renumbered due 

to reorganization 

of parent 

procedure. 

 AP2.13.4.5.2.4.4.1.3.2. Unified or Service Command 

Headquarters. 

 AP2.13.4.5.2.4.4.1.3.3. The Joint Staff. 

 AP2.13.4.5.2.4.4.1.3.4. OSD. 

 AP2.13.4.4.4.2. Assignment Constraints Subsections 

reorganized. 

 AP2.13.4.4.4.2.1. OSD project codes shall be assigned only 

to projects and programs clearly of direct interest to the Secretary of Defense 

(SECDEF). Authorization for use of OSD project code(s) shall be for a specified 

period of time. 

Consolidated into 

AP2.13.4.5.1. 

above 

 AP2.13.4.4.4.2.2. CJCS project codes shall be assigned 

only to projects and programs clearly of direct interest to the CJCS acting on 

behalf of the SECDEF. Authorization for use of a CJCS project code shall be for 

a specified period of time, and the Force/Activity Designators (F/AD) to be used in 

conjunction with the CJCS project code should be designated in the authorization. 

Consolidated into 

AP2.13.4.5. above 

 

8

 Ibid. 
Enclosure 7, ADC 1118 

Page 8 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

AP2.13.64.4.4.3. Dissemination. When Category C & D project codes are 

initially assigned, extended, or cancelled prior to the current expiration 

date, PCMS will distribute announcements to the listed 

monitor(s)/coordinator(s) for the project code and all those subscribed to 

receive project code announcements.9

Reorganizes out 

from under 

Category D to 

make consolidated 

dissemination 

procedures for 

Category C & D 

codes. 

 AP2.13.6.1. The following are required to subscribe in PCMS to receive 

project code updates10: 

New procedure to 

ensure known 

Category C & D 

project code 

stakeholders are 

notified of project 

code assignments, 

updates, and early 

terminations. 

 AP2.13.6.1.1. Designated OSD project code representatives, 

 AP2.13.6.1.2. Designated CJCS project code representatives, 

 AP2.13.6.1.3. DoD MILSTRIP Administrators, 

 AP2.13.6.1.4. Designated S/A project code representatives, 

 AP2.13.6.1.5. S/A representatives of the Supply Process Review 

Committee. 

AP2.13.6.2. Initial dissemination of CJCS- assigned cCategory C and D 

project codes willshall be accomplished in multiple steps, as follows: 

Renumbered as 

part of 

reorganization of 

dissemination 

procedures. 

Administrative 

edit. 

 

9 ADC 1118 initiated the development of PCMS. Until PCMS is implemented, DoD MILSTRIP 

Project Code Support will disseminate project code notices to the representatives listed under 

AP2.13.6.1. and other interested parties.

10 ADC 1118 initiated the development of PCMS. The subscription capability is a planned 

enhancement of PCMS. Until PCMS is implemented, DoD MILSTRIP Project Code Support will 

disseminate project code notices to the representatives listed under AP2.13.6.1.
Enclosure 7, ADC 1118 

Page 9 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.6.24.4.4.3.1. For OSD/CJCS project codes, OSD/CJCS are 

responsible for electronically disseminatinge the applicable authorizing project 

code message (or the Execute Order containing project code assignment) to S/A 

Headquarters and other activities as appropriate. 

Renumbered as 

part of 

reorganization of 

dissemination 

procedures. Since 

no longer under 

Category D, 

clarified as the 

authorizing 

message 

distributed by OSD 

and CJCS. 

 AP2.13.4.4.4.3.2 OSD/CJCS electronically forwards 

unclassified notification of Category D project code only assignment to the DLA 

Transactions Services. 

Removed as not 

relevant when 

PCMS is stood up. 

 AP2.13.4.4.4.3.3. OSD/CJCS electronically forwards 

unclassified notification of Category C or D project code assignment to DoD 

MILSTRIP Administrator. 

Removed as not 

relevant when 

PCMS is stood up. 

 AP2.13.6.24.4.4.3.4.2. DoD MILSTRIP Administrator The approved 

project code is finalized and made active in PCMS, which electronically 

forwards an unclassified project code assignment letter to subscribers the 

designated S/A project code contact points11 and Supply PRC members. Also, 

PCMS will push notification of the new code to eligible systems.12

PCMS will take 

over dissemination 

of C & D project 

codes. Include web 

service capability. 

 AP2.13.6.24.4.4.3.5.3. S/A project code representativescontact points 

electronically disseminate the project code noticeletter or message to all involved 

S/A activities. 

Administrative 

edits. 

 

11 www.dla.mil/j-6/dlmso/eLibrary/Restricted/SvcPointsPOC/default.asp (select Svc Pt for project codes) 12 ADC 1118 initiated the development of PCMS. Until PCMS is implemented, the authoritative 

source for Category C & D project codes is MILSTRIP Appendix 2.13, posted to the DLMSO 

website: www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp. The MILSTRIP Project Code 

Support will disseminate project code notices based on the formats of MILSTRIP Appendix 1.37. 

Push notifications to Component systems is a planned enhancement of PCMS.
Enclosure 7, ADC 1118 

Page 10 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.4.4.4.4. Validation. The DLA Transaction Services shall 

edit all requisitions and related transactions (Document Identification Code (DIC) 

A0_, AM_, AT_, and APR) for invalid/expired OSD/CJCS category D project 

codes. If an invalid/expired code is present, DLA Transaction Services shall 

blank the project code, forward the requisition for processing, and report this 

action back to the requisitioner in an AE9 transaction with BK status. To 

accomplish this, DLA Transaction Services shall establish and maintain an edit 

table based upon OSD/CJCS message, or communication from the MILSTRIP 

Administrator identifying additions, deletions, or corrections to project code 

information. 

The Validation 

procedure is 

reorganized to 

AP2.13.9.2. so as 

to not interrupt the 

flow of 

dissemination 

procedures and 

maintenance. 

 AP2.13.6.35. Announcements of project code assignments, updates and 

terminations shall be under procedures and conditions specified in paragraph 

AP2.13.4.6., above, and willshall provide the information listed below:

Reorganized to be 

a part of 

dissemination 

procedures. 

TITLE EXPLANATION 

Project Code Code assigned under the provisions of this manual. 

Effective Date Indicate the date when supply sources should 

commence required action relative to the code. 

Termination Date Identify the last calendar day that the project code 

or Continuing will be active, or indicate that the project code is 

continuing indefinitely for project codes integrated 

with ongoing MILSTRIP processes. WhenAfter a 

specified termination date is reachedpassed, inter-S/A 

recognition of the code willshall stop and categories C 

and D project codes willshall be removeddeleted from 

the active project code listing. Unfilled requisitions 

(which have not been canceled) containing an

terminateddeleted project code (cCategory B, C, or D) 

willshall be processed in the same manner that 

requisitions with cCategory A project codes are 

processed. No mass cancellation of CJCS project 

coded requisitions is authorized without prior approval of 

the JMPAB. 

Clarify project 

codes expire at the 

end of the 

termination date, 

rather than at the 

beginning of the 

day. Reinforce that 

only MILSTRIP 

procedural project 

codes may be 

ongoing (i.e. lack 

a termination 

date). 

Administrative 

edits. 
Enclosure 7, ADC 1118 

Page 11 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

Service Code(s) All or specified S/A code(s) which willshall be used in 

conjunction with the project code. This information is to 

be included as part of the Project Code Description field 

of PCMS. 

Administrative 

edit. In PCMS this 

information has to 

be included as part 

of the Project 

Code Description 

field. 

Use/References 1. Use - Use a clear-text statement defining the intended 

use of the code and indicating those to whom it applies 

(unless the use is classified). Also, if applicable, provide 

an abbreviated project name. 

 2. References - Cite inter-S/A agreements and other 

documents when establishing or specifying special 

controls for the project. The S/A establishing the project 

is responsible for ensuring that suppliers are provided 

copies of these documents, if not available on an interS/A basis. If a joint regulation is cited, all S/A numbers 

willshall be included in the project code announcement. 

An assembly point for shipment may be designated in 

this column by use of the DoDAAC for the assembly 

point. The DoDAAC of the assembly point willshall be 

entered in requisitions by requisitioners as the ship-to 

address. Shipping activities are not required to use 

project code announcements to determine the ship-to 

address unless inter-S/A agreements are negotiated for 

special routing of shipments. Only one assembly point 

per project code may be assigned. 

Administrative 

edits. 

Monitor/Coordinator Identify the activity within the S/A or OSD/CJCS which is 

monitoring or coordinating the project, point of contact, 

telephone number (DSN and commercial, as 

applicable), and email address. 

 AP2.13.6.3.1. As per AP2.13.6.2.2. above, PCMS will distribute 

project code announcements when a new project code is activated.13 Refer 

to Appendix 1.37 for the format of the generated announcement. 

New sections to 

explain the 

scenarios and 

 

13 ADC 1118 initiated the development of PCMS. Until PCMS is implemented, the MILSTRIP 

Project Code Support will disseminate project code notices based on the formats of MILSTRIP 

Appendix 1.37.
Enclosure 7, ADC 1118 

Page 12 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.6.3.2. When an active project code is extended, PCMS will 

distribute a project code update announcement indicating the new 

termination date.14 Refer to Appendix 1.37 for the format of the generated 

announcement. 

notice format type. 

 AP2.13.6.3.3. When an active project code is being cancelled early 

(i.e., before the currently published termination date) or reaches its 

termination date PCMS will distribute a project code cancellation 

announcement.15 The prior termination date is to be crossed out and the 

actual expiration date distinctly displayed. Refer to Appendix 1.37 for the 

format of the generated announcement. There is no notification distributed 

when a project code automatically cancels on the published termination 

date. 

AP2.13.6.4. Following the initial dissemination of the project code 

assignment, PCMS will include the code in reports and relevant queries of 

active project codes.16

Introduces the 

various ways new 

and expired 

project codes are 

discoverable. 

 AP2.13.4.4.4.3.6.4.1. Following this initial dissemination of the 

category C and D project code assignment, For those without PCMS accounts, 

reports containing all Category C and D codes will be published electronically 

on the DefenseLA Logistics Management Standards Office Website 

www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/milstrip_pubs.asp unless prohibited 

by security classification. The report includes active project codes and those 

that have expired in the six months prior of the report generation date.

Move section to 

better fit flow and 

describe the new 

way the report is 

produced. 

Administrative 

edits. 

 AP2.13.6.4.2. Those with access to PCMS can access system 

generated reports and perform ad hoc queries. See AP2.13.9.1. below for 

information on who, and how, individuals obtain PCMS accounts.17

Establishes ad hoc 

query capability. 

 

14 Ibid. 

15 Ibid. 

16 ADC 1118 initiated the development of PCMS. Until PCMS is implemented, reports of Category 

C & D project codes can be accessed as described in AP2.13.6.4.1..

17 Ibid. 
Enclosure 7, ADC 1118 

Page 13 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

AP2.13.76. Maintenance of Project Code Assignments. The Component 

designated S/A project code representativescontact point (and the initiator or 

requestor of the project code, if different from the S/A project code 

representativescontact point list referenced under paragraph AP2.13.87., below) 

willshall ensure that the status of the project code remains current. In addition to 

the requirements identified in AP2.13.5., tThe initiator or requestor of a project 

code willshall provide the current information of the monitor/coordinator and 

requests for extension up to two years to the OSD/CJCS or DoD MILSTRIP 

Administrator as appropriate. AsWhen informed of project code assignment 

changes occur, the appropriate PCMS user will record the changes in 

PCMS,DoD MILSTRIP Administrator which in turn willshall notify all 

subscribers as referenced in AP2.13.6.3 aboveinterested parties; such as, the 

project code contact point, the requestor or initiator (if different from the project 

code contact point), and the monitor/coordinator. The project code contact point 

and the initiator or requestor of the project code (if different from the project code 

contact point) shall also notify all interested parties of changes in project code 

assignments.18

Administrative 

edits. Since 

Category C & D 

project codes can 

only be updated in 

PCMS by OSD, 

CJCS, or the 

MILSTRIP 

Administrator, 

updates must be 

routed through the 

appropriate PCMS 

user. PCMS will 

notify subscribers 

as described in the 

dissemination 

section above. 

AP2.13.87. Service/Agency MILSTRIP Project Code RepresentativesContact 

Points. 

Administrative 

edit. 

 AP2.13.8.1. OSD/CJCS, Services, and DLA will formally designate a 

primary representative, and may designate up to three alternates. 

Appointment letters adding or removing individuals as representatives are 

to be signed by the designating OSD/CJCS/Component governing authority 

for project codes and sent to the MILSTRIP Project Code Support at 

Defense Logistics Management Standards Office and to the DLA 

Transaction Services PCMS Administrator.19 Refer to Appendix 1.38 for an 

appointment letter template. 

New requirement 

to formalize the 

designation of 

project code 

representatives. 

 AP2.13.8.2. The S/A designated project code representativescontact 

points are published electronically on the DLA Defense Logistics Management 

Standards Office Website https://www2.dla.mil/j6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp (CAC required). 

Administrative 

edits.

 

18 ADC 1118 initiated the development of PCMS. Until PCMS is operational, the authoritative 

source for Category C & D project codes is MILSTRIP Appendix 2.13, posted to the DLMSO 

website: www.dla.mil/j-6/dlmso/elibrary/manuals/dlm/dlm_pubs.asp. MILSTRIP Project Code 

Support will disseminate project code notices based on the formats of MILSTRIP Appendix 1.37. 19 ADC 1118 initiated the development of PCMS. Until PCMS is operational, a copy of the 

appointment letter does not need to be sent to the DLA Transaction Services PCMS Administrator.
Enclosure 7, ADC 1118 

Page 14 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

AP2.13.9. Project Code Management System. New Section on 

PCMS. 

 AP2.13.9.1. System Administration.20 New requirement 

establishing DLA 

Transaction 

Services to develop 

and maintain 

PCMS, and the 

process to 

grant/manage 

access to those 

users which will 

maintain the 

Category C & D 

project codes and 

read-only access 

to authorized users 

for ad hoc queries.

 AP2.13.9.1.1. DLA Transaction Services maintains the PCMS 

application for updating Category C & D project code data.21 It facilitates 

project code lifecycle management, automated notification to designated 

recipients, and real-time project code validation for supply transactions 

processed through DLA Transaction Services. Access to the PCMS 

application is controlled in accordance with DoD Public Key Infrastructure 

(PKI)/Common Access Card (CAC) requirements and requires an 

appointment letter submitted to the MILSTRIP Administrator, and a System 

Access Request (SAR) submitted to DLA Transaction Services at

https://www.transactionservices.dla.mil/daashome/customerassistance.asp. 

 AP2.13.9.1.2. DLA Transaction Services deactivates accounts 

when an account holder is no longer authorized or when the account has 

not experienced activity for a period of time determined by DLA Transaction 

Services. OSD/CJCS and MILSTRIP Administrator accounts are restricted 

through access controls to project code categories appropriate to their role 

authorized in their appointment letter. S/A Project Code Representatives 

and SPRC representatives may submit a SAR to obtain a read-only access 

account to perform ad hoc queries. 

 

20 ADC 1118 initiated the development of PCMS. Until PCMS is operational, procedures of 

AP2.13.9.1. are on hold.

21 Addition of Category A and/or B project codes may be addressed as a future enhancement to 

PCMS based on S/A requirements. 
Enclosure 7, ADC 1118 

Page 15 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.9.24.4.4.4. Validation. Using project code data in PCMS, DLA 

Transaction Services will edit all requisitions and related transactions (DLMS 

511R / MILSTRIP Document Identification Code (DIC) A0_, AM_, DLMS 869F / 

MILSTRIP DIC AT_, and DLMS 517M / MILSTRIP DIC APR) for invalid/expired 

cCategory C & D project codes.22

Reorganized and 

modified from 

AP2.13.4.4.4.4. 

removed above. 

Designates PCMS 

as the source for 

validation. 

Expands project 

code validation to 

Category C codes. 

Identifies DLMS in 

addition to legacy 

transactions. 

 AP2.13.9.2.1. The edit check for valid project codes compares the 

project code in the transaction to the project codes recorded in PCMS and 

verifies the project code is present and currently active.

Clarifies that 

PCMS will be able 

to perform the 

validation based 

on the existence of 

a project code, but 

must also check 

the project code’s 

status since PCMS 

will allow for 

reserved and 

pending project 

codes, as well as 

retain historical 

project code data. 

 

22 ADC 1118 initiated the development of PCMS. Until PCMS is operational, DLA Transaction 

Services will maintain the current validation/expiration edit check for Category D project codes.
Enclosure 7, ADC 1118 

Page 16 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.9.2.2. If the edit check determines the project code exists 

but has expired, PCMS compares the ordinal date from the requisition 

document number in the transaction to the beginning date and actual 

expiration date of the project code in PCMS to determine if the project code 

was active at the time of the original requisition.

By comparing 

against the 

requisition date 

embedded in the 

document number, 

follow-on 

requisition related 

transactions will 

not strip the 

project code if it 

was valid at the 

time of the original 

requisition. 

 AP2.13.9.2.3. If an invalid/expired code is present or a project code 

is used on a requisition issued outside the active period for the project 

code, DLA Transaction Services will blank the project code, forward the 

requisition for processing, and report this action back to the requisitioner in a 

supply status transaction (DLMS 870S / MILSTRIP DIC AE9) with BK status. 

 AP2.13.9.3. PCMS will track which project codes are reserved, pending 

active, and expired.23

Key function of 

PCMS. 

 AP2.13.9.3.1. PCMS users may reserve a project code within their 

authority to assign for up to one year. If the project code is not made active 

or given a pending date to become active within the year it was reserved, 

then PCMS will no longer reserve the project code. During the time that a 

project code is reserved, it is only discoverable within PCMS by other users 

who could have been assigned the same code. 

One year 

reservation based 

on most extreme 

historical 

scenario. Request 

comment if 

insufficient. Would 

recommend 

considering limits 

on the number of 

codes a user can 

reserve and for a 

shorter time, if 

possible, to avoid 

running out of 

available codes. 

 

23 ADC 1118 initiated the development of PCMS. Until PCMS is operational, procedures of 

AP2.13.9.3. are on hold and MILSTRIP Project Code Support will continue to track and 

disseminate project codes.
Enclosure 7, ADC 1118 

Page 17 

REVISED APPENDIX 2.13 TEXT EXPLANATION 

 AP2.13.9.3.2. PCMS users can set a project code to automatically 

become active on a date up to 30 days in the future. In order to set a 

project code for future activation, the project code must have the required 

information for disseminating the project code as called for in AP2.13.6.3.. 

During the time that a project code is pending activation, it is only 

discoverable within PCMS by other users who could have assigned the 

same code. 

Thirty day window 

based on most 

extreme scenario 

of past experience. 

Request comment 

if insufficient. 

 AP2.13.9.3.3. PCMS will not offer a previously expired project 

code to be reused for another purpose until at least five years after the 

project code expired. When a user requests to create a new project code, 

PCMS will first offer the project code that has gone the longest since being 

used. The user be able to request a specific project, so long as it is not 

already active or within five years since expiring. 

Allow sufficient 

time for any old 

requisitions with 

expired project 

codes to clear out 

of the supply 

chain. 
Enclosure 8, ADC 1118 

Page 1 

ENCLOSURE 8 TO ADC 1118 

AP1.38. APPENDIX 1.38 

Template for Service/Agency Project Code 

Representative Appointment Letter 

[AGENCY LETTERHEAD] 

MEMORANDUM FOR: Defense Logistics Management Standards Office, 

 DLA Transaction Services PCMS Administrator 

SUBJECT: Service/Agency Project Code Representative Letter of Appointment

REFERENCES: (a) DLM 4000.25-1, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), Appendix 2.13 

 

In accordance with reference (a), Primary and Alternate Service/Agency Project Code 

Representatives are appointed on behalf of the OSD/CJCS/Service/Agency as follows: 

Primary Project Code Representative: 

Ms. XXXXX XXXX 

 Email: XXXXXX.XXXX@ 

 Comm: 703-607-XXXX 

 DSN: 327 

Alternate Project Code Representative: 

Mr. XXXXXXX XXXXXX, 

 Email: XXXXXXX.XXXXXX@ 

 Comm: 703-607-XXXX 

 DSN: 327 

These representatives are responsible for the currency and accuracy of our project codes and for 

maintaining records to support the assignment, modification or deletion of each project code. 

If there are any additional questions or concerns, please contact me at XXX-XXX-XXXX. 

 

XXXXX X. XXXXXX 

Authorized Agency Representative 
Enclosure 8, ADC 1118 

Page 2 

Instructions/Information 

1. Service/Agency Project Code Service Representative may not appoint themselves. 

2. Send your letter as a PDF attachment to a digitally signed email to MILSTRIP Project 

Code Support at ??TBD??@dla.mil. 

3. A new letter listing all Service/Agency Project Code Service Representative is required 

promptly for any additions or deletions. 

4. Service/Agency Project Code Representatives are shown at: https://www2.dla.mil/j6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

Additional Requirements for PCMS Users ( Required for: OSD/CJCS representatives 

and DoD MILSTRIP Administrator; Optional for: Project Code Service Representative 

read only access): 

5. Send a copy of your digitally signed appointment letter to DLA Transaction Services at 

??TBD??@dla.mil. 

6. To submit a Systems Access Request to the DLA Transaction Services PCMS application 

following appointment visit https://www.daas.dla.mil/sar/sar_menu.html.

7. Deleted Service/Agency Project Code Representative accounts for the PCMS at DLA 

Transaction Services will be immediately deactivated. 
Enclosure 9, ADC 1118 

Page 1 

ENCLOSURE 9 TO ADC 1118 

Proposed DLMS Change (PDC) 1118 Response Table:

Component Response Resolution 

1. Army Concur. Noted. 

2. Air Force This change should make the DLA Transaction 

Services the Authoritative Data Source (ADS) 

for DoD Project Codes. We understand the 

current ADS is the DLMSO Authorized 

Transaction Repository. Will the ADS be redesignated? We recommend the follow-on 

ADC address the appropriate ADS so all 

consumers know appropriate data source. 

Agree. ADC now states 

that when PCMS is stood 

up at DLA Transaction 

Services, it will assume the 

role of the ADS for 

Category C & D project 

codes to be used with 

DLMS qualifier 78. 

3. DLA 

Transaction 

Services 

Completion by DLA Transactions Services 

Solutions to complete the following objectives 

is dependent upon any future requirements to 

provide Audit programming support as 

directed by the Transactions Services Director, 

Brad Lantz. 

Noted. 

4. We have many comments and/or questions 

concerning the logic and details within the 

Enclosures that could affect our stated 

timelines below, such as Enc. 2, P2, Items 9-10 

- emailing of Project Code statuses. Our 

applications do not generate email notifications 

to customers. However, such details should not 

prevent the overall development of a basic 

Project Code web application. 

Noted. Will discuss viable 

approaches to addressing 

functionality for status 

notifications, if cannot be 

performed according to the 

initial requirements of this 

ADC. 

5. Our experiences from the recent FUNDCODE 

development, testing (internal and external), 

and HQ Front Door approval process, suggests 

that once the application is submitted to the 

Front Door staff, approval can take 30 – 60 

days. While the application is being reviewed 

for approval, internal use can begin 

immediately once all testing is complete. Once 

approval is granted, the application will be 

deployed to the production environment after 

any required training, which will be 

determined by DLMSO and Transactions 

Services personnel. 

Noted. 
Enclosure 9, ADC 1118 

Page 2 

Component Response Resolution 

6. DLA 

Transaction 

Services 

(cont.) 

Section 4.b.5 and 6 

Agree to develop a web application as 

described; estimated completion of 

development for testing is Jul 31, 2015. 

Completion date is dependent upon 

modifications to the Project Code and Points of 

Contact database table by the Database 

Administrators IAW Enclosures 1 and 2. 

The User Role functionality (reference 

Enclosure 3), is not clear as it relates to the 

web application. Roles must be defined to 

restrict or allow functions for normal 

application usage, but the level of restriction 

should not be too limited within an application. 

What may or may not be feasible must be 

discussed for clear understanding for all 

involved and to accommodate internal 

application dependencies. 

Noted. It is understood 

that during development 

there may be a need to 

discuss alternatives, 

adjusting the development 

schedule, or holding off on 

some less important 

functionality in order to get 

a quality core product 

stood up. 

7. Section 4.c.5.a 

Agree to develop report IAW or similar to the 

description in Enclosure 4, by Sep 30, 2015. 

The logic displayed must be discussed for 

precise development. Placement of the report 

link must be determined (Project Codes or 

Logistics Reports). 

Noted. 

8. Section 4.c.6 

Agree to provide a web service for customers 

to receive Project Codes data to be limited to 

the agreed release of database table elements, 

in relation to customer requirements. 

Noted. 
Enclosure 9, ADC 1118 

Page 3 

Component Response Resolution 

9. Marine Corps 1. Headquarters Marine Corps has reviewed 

reference (a) and concurs with the PDC. No 

problems have been identified related to 

changing alpha numeric assignment rules as 

described in the PDC. 

Noted. 

10. 2. The following suggestions are provided for 

potential future expansion to include A and B 

project codes. 

a. Field Name: Purpose. Type: VARCHAR2 

(50). Use: O. Definition: To identify the reason 

for the project code. i.e. special programs, 

exercises, projects, operations or other 

purposes. Business Rule: Optional Freeform 

entry. 

b. Field Name: Element. Type: VARCHAR2 

(3). Use: C. Definition: To identify which 

element of the MAGTF is expected to use the 

Project Code. Business Rule: If Code Owner = 

M than must not be null. Multiple selections 

are allowed. Values A=HQ, B=ACE, C=LCE, 

D=GCE, E=SE. 

c. Field Name: Assigned_by. Type: 

VARCHAR2 (10). Use: C. Definition: To 

identify the office responsible for assigning 

and managing the project code. Business Rule: 

If Code Owner = M than must not be null. 

Values: A=CMC/SYSCOM, B=LOGCOM, 

C=I&L, D=Other. 

Noted. These will be fed 

into Phase II requirements 

to be coordinated with the 

interested Components, 

should there be interest in 

PCMS storing Category A 

& C project codes. 

11. Navy Concur. Noted. 

12. SOCOM Concur. Noted. 

13. USTRANSCOM Concur. Noted. 

14. CJCS Concur. Noted. 

15. OSD. Concur Noted. 
Enclosure 9, ADC 1118 

Page 4 

Component Response Resolution 

16. DLMSO In view of the enhanced data content available 

under PCMS, DoD MILSTRIP Administrators 

recommend modifying the 

validation/expiration of Category C & D 

project codes to compare the ordinal date from 

the Document number to the expiration date of 

the project code. This will eliminate blanking 

out project code on requisition modifications, 

follow-ups, and requisition reinstatements 

where the project code was valid and active 

when the original requisition was generated. 

As part of modifying the edit to account for 

enhanced date verification, as well as inclusion 

of the Web Service capability, the Components 

should enable up front edits in their supply 

systems to check project codes are both valid 

and active. 

Modified in ADC above to 

include the modification of 

the requisition edit and 

impact to DLA Transaction 

Services and Components. 

17. During the staffing of PDC 1118 the Joint Staff 

requested that the duration for project codes be 

removed from the non-FOUO version of the 

report. 

Enclosure 4 updated to 

indicate the duration 

column to be printed on the 

FOUO version only. 

18. While finalizing the ADC, discussions with 

CJCS noted the value of having PCMS have 

access to supply transaction data for canned 

queries to examine recent use of the project 

code. Such data enables more informed 

consideration of extending project codes. 

Updated ADC with new 

4.c.(5)(c) and 4.c.(5)(d) to 

request DLA Transaction 

Services identify a 

workable source for such a 

capability.