DEFENSE LOGISTICS AGENCY

HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

FORT BELVOIR, VIRGINIA 22060-6221

 December 06, 2018 

MEMORANDUM FOR DEPARTMENT OF DEFENSE ACTIVITY ADDRESS DIRECTORY 

(DoDAAD) PROCESS REVIEW COMMITTEE (PRC) AND SUPPLY PRC MEMBERS 

SUBJECT: Approved Defense Logistics Management Standards (DLMS) Change (ADC) 1311,

for Implementation of DoDAAC Purpose Flags in the DoDAAD from PIEE

(DoDAAD)

The attached change to Defense Logistics Manual (DLM) 4000.25, Defense Logistics 

Management Standards (DLMS), Volume 6, Chapter 2, Department of Defense Activity Address 

Directory is approved for immediate implementation. 

The Offices of Deputy Assistant Secretary of Defense, Logistics and Office of the

Under Secretary of Defense, Defense Pricing and Contracting, directed immediate

implementation of changes identified herein, which was completed on August 28, 2018. 

EBSO amended and highlighted this ADC with adjudication of Component comments. 

Addressees may direct questions to Tad DeLaney, DoDAAD PRC Chair, at 

571-767-6885, DSN 427-6885, or e-mail: EBSO.DODAAD@dla.mil. Others must contact their 

Component designated representative. 

HEIDI M. DAVEREDE 

Director 

Enterprise Business Standards Office

Attachment

As stated

cc:

ODASD (Logistics)

OUSD DPC
Attachment, ADC 1311

Page 1

ADC 1311

Purpose Flags from PIEE

(DoDAAD)

1. REQUIREMENTS ORIGINATOR POC INFORMATION:

a. Defense Pricing and Contracting (DPC), Product Development and Implementation 

(PDI), Lisa Romney, at 703-697-4396, email: Janice.l.romney.civ@mail.mil.

b. Enterprise Business Standards Office (EBSO), DoDAAD PRC Chair, Tad DeLaney, 

at 571-767-6885, e-mail: EBSO.DODAAD@dla.mil. 

2. FUNCTIONAL AREA:

a. Primary: DoDAAD

b. Secondary: Procurement / Payment

c. Tertiary: Supply / Distribution

 Category  Category  Category

Billing Physical Inventory Contract Admin

Discrepancies / Deficiencies MILSTRAP  DoDAAD

Serialization MILSTRIP MAPAD

Small Arms/Light Weapons MRA LMARS

pRFID Disposition DLM Publications

GFP DOD BRAC

3. REFERENCES:

a. DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 6, 

Chapter 2, Department of Defense Activity Address Directory

b. CFR 48, Federal Acquisition Regulations System (FAR), Subpart 46.503

c. Defense Federal Acquisitions Regulation Supplement (DFARS) Procedures, Guidance 

and Instruction (PGI) 204.7103
Attachment, ADC 1311

Page 2

4. APPROVED CHANGE(S):

a. Brief Overview of Change: This change establishes the Contract Administration 

Office (CAO) flag in the DoDAAD and enables the setting of all Procurement-related Purpose 

flags (Procurement Authority, Grant Authority, and CAO) to be set in the DoDAAD, directly 

from the Procurement Integrated Enterprise Environment (PIEE). 

b. Background: PIEE is the hosting environment for functional procurement 

capabilities (e.g., WAWF, CAGE, FEDMALL). The purpose of PIEE is to consolidate 

procurement functionality for multiple applications into one integrated environment. The 

Procurement Authority and Grant Authority flags already exist in the DoDAAD, the CAO flag 

will be created by this change. The responsible entity for their maintenance is DPAP. This 

interface will allow PIEE to create an XML file, which will be passed to DAAS and directly 

update the DoDAAD database. The maintenance of these flags is handled manually today.

c. Approved Change in Detail:

(1) DAAS: Defense Automatic Addressing System (DAAS) DAAS shall 

implement the following in support of this change. These changes shall be made to the 

DoDAAD, DAASINQ/ eDAASINQ (eDoDAAD), DoDAAD Update Application, XML file 

schemas supporting DoDAAD, and all DoDAAD output (e.g., Replication, web services, SFTP, 

downloads, etc.): 

(a) New element required: CAO_FLAG, CHAR(1)

(b) DAAS office will need to create a new XML interface to allow direct 

processing of the purpose flags XML file maintenance. In the near term, this XML file will be 

emailed from PIEE to the DoDAAD Central Service Point (CSP) for submission into the 

DoDAAD. DAAS will need to remove the edit restriction that currently limits updating these 

purpose fields (i.e., Procurement, Grant and CAO) only by the DoDAAD Administrators. The 

CSP will be responsible for making changes to the purpose flags, based on input from PIEE once 

this change is implemented. In the future, DAAS will need to develop a web service to allow 

DPAP to submit changes directly to the DoDAAD with no requirement for manual intervention

by the CSP (this enhancement will be submitted as a separate change request). The elements for 

the purpose flags XML are:

1. DoDAAC. This is required, because purpose flags can only be 

changed, but cannot be created by this XML file. 

2. Purpose flags. The XML must have the ability to turn flags 

both on and off, so each flag will have three values: Y = on, N = off and null means no change. 

At least one of the following values (i.e., Y or N) MUST be present or the transaction will be 

rejected: 

a. Procurement flag (1 character) – Y, N or null
Attachment, ADC 1311

Page 3

b. Grant flag (1 character) – Y, N or null

c. CAO flag (1 character) – Y, N or null

3. Org Type Code (1 character) - F or D

4. Sub Tier Code (4 characters). Sub Tier is a one-to-one 

relationship (e.g., M series is 1700), except for Federal DoDAAC series and DoD forth estate

(e.g., HB is 97CY – USCYBERCOM). The field is required in all cases and a separate table will 

be provided to DPAP for validation of this element.

5. CGAC (3 characters). CGAC is a one-to-one for all DoD 

DoDAACs (e.g., M series is 017). Federal DoDAACs will require PIEE to set the CGAC based 

on the Agency within the Department (e.g., 48 series can be 283 (Legislative Branch Boards and 

Commissions) or 309 (Appalachian Regional Commission) or 377 (Other Commissions and 

Boards)). The field is required in all cases and a separate table will be provided to DPAP for 

validation of this element.

(c) Enclosure 1 contains a layout of the XML schema file to support this 

change. The functionality should dovetail with ADC 1197. The processing will require the CSP 

to upload the XML file, verify the change and accept the change. This change is separate from 

ADC 1197 because the purpose flags can only be changed by a CSP if the source of the request 

is PIEE. 

(2) Wide Area Workflow Program Office. Utilize the XML file schema in the 

Enclosure in support of WAWF ECP 1163. 

(3) Federal Logistics Information System (FLIS) Portfolio Data Warehouse 

(FPDW) Program Office. Ensure these changes get implemented in all syndication of 

DoDAAD data from FPDW. 

d. Revisions to DLM 4000.25 Manuals: The following changes need to be made to the 

DLM 4000.25 Manuals:

(1) DLM 4000.25, Volume 6, Chapter 2. Insert the following:

C2.4.4.7.4. Contract Administration Office (CAO). The CAO flag 

indicates that the office identified by the DoDAAC has the authority and capability 

to perform contract post-award (FAR 42.3) functions. The CSP should only make 

this change based on input from PIEE. The CAO flag can be marked in 

association with any other existing Purpose Code (i.e., it is not mutually exclusive 

with Procurement or Grants). When this flag is set, it will make the Sub Tier Code 

and CGAC mandatory field entries. This flag can only be set if the Org Type code 

is “F” or “D.”

(2) DoDAAD Update Application Standard Operating Procedures. Changes 

contained herein must be incorporated into the DoDAAD Update Application SOP and all 

supporting documents. 
Attachment, ADC 1311

Page 4

5. REASON FOR CHANGE: The CAO Flag is required to support Procurement processes. 

Currently, the purpose flags are manually set based on an email from DPAP. This change 

automates the process and gives DPAP full control of these purpose flags from within PIEE.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Replaces the manual process of maintaining the Procurement, Grant 

and CAO flags with an automated process and adds the much needed ability to track the 

DoDAAC’s contract administration office.

b. Disadvantages: None noted.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Authorized for immediate 

implementation. DAAS has already implemented the changes to the DoDAAD. Changes 

required by other Components should be completed within 60 days from the publication of this 

ADC.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None.

9. IMPACTS:

a. New DLMS Data Elements: None

b. Changes to DLMS Data Elements: None

c. Automated Information Systems (AIS):

(1) This change supports Procurement requirements. Procurement systems 

impacted by this change are being addressed via separate change documents for PIEE. 

(2) This change will also impact any and all Supply Chain systems involved in 

the processing of transactions related to contracts involving Government Furnished Property. 

(3) All DoDAAD repositories (Army, Air Force, GSA) and systems containing 

DoDAAD tables (FLIS Portfolio Data Warehouse, DLA Enterprise Business System, SAP ERPs, 

etc.) must implement these changes. 

d. Army and Air Force. Army and Air Force expected to make the necessary changes 

to their respective DoDAAC applications to mirror these changes to the DoDAAD.

e. Non-Defense Logistics Management Standards Publications: The changes 

identified herein will need to be incorporated into the relevant Service/Agency-level DoDAAD 

management publications, including (but not limited to) the following: 

(1) U.S. Army: AR 725-50 

(2) U.S. Air Force: AFI 24-230

(3) U.S. Marine Corps: MCO 4400.201
Attachment, ADC 1311

Page 5 

(4) U.S. Coast Guard: COMDTINST M4000.2

(5) Defense Information Systems Agency: DISA Instruction 270-50-10

(6) Federal Management Regulations (CFR 41)

10. APPROVED DLMS CHANGE (ADC) 1311 RESPONSE/COMMENT

RESOLUTION:

Originator Response/Comment 1 Disposition

1. USAF Concur with comment Noted

2. DLA Concur without comment Noted

3. US Navy Concur with comment Noted

4. DCMA Concur without comment Noted

5. DAAS Concur with comment Noted

6. DFAS Concur without comment Noted

7. USSOCOM Concur with comment Noted

1 No issue with the change, but there was an issue with the policy (specifically purpose flags to be maintained by 

DPC). 
Enclosure 1, ADC 1311

Page 1

Purpose Flag Request XML Schema

The following is the schema developed for the Enterprise DoDAAD website Automated Request 

Tool, and shall be used by PIEE to send purpose codes changes to the DoDAAD.

<?xml version="1.0"?>

<xsd:schema xmlns:xsd="http://www.w3.org/2001/XMLSchema" elementFormDefault="unqualified" 

attributeFormDefault="unqualified">

 <xsd:element name="ROWSET">

 <xsd:complexType>

 <xsd:sequence>

 <xsd:element name="ROW">

 <xsd:complexType>

 <xsd:sequence>

 <xsd:element name="REQUEST" minOccurs="1" maxOccurs="unbounded">

 <xsd:element name="DODAAC_INFO" minOccurs="1" maxOccurs="1">

 <xsd:complexType>

 <xsd:sequence>

 <xsd:element name="DODAAC" minOccurs="0" maxOccurs="1">

 <xsd:simpleType>

 <xsd:restriction base="xsd:string">

 <xsd:maxLength value="6"/>

 </xsd:restriction>

 </xsd:simpleType>

 </xsd:element>

 <xsd:element name="ORGTYPE_CODE" minOccurs="0" maxOccurs="1">

 <xsd:simpleType>

 <xsd:restriction base="xsd:string">

 <xsd:maxLength value="1"/>

 <xsd:pattern value="D|F|S|X"/>

 </xsd:restriction>

 </xsd:simpleType>

 </xsd:element>

 <xsd:element name="PROCUREMENT_AUTHORITY" minOccurs="0" maxOccurs="1">

 <xsd:simpleType>

 <xsd:restriction base="xsd:string">

 <xsd:maxLength value="1"/>

 <xsd:pattern value=" Y|N| "/>

 </xsd:restriction>

 </xsd:simpleType>

 </xsd:element>

 <xsd:element name="GRANT_AUTHORITY" minOccurs="0" maxOccurs="1">

 <xsd:simpleType>

 <xsd:restriction base="xsd:string">

 <xsd:maxLength value="1"/>

 <xsd:pattern value=" Y|N| "/>

 </xsd:restriction>

 </xsd:simpleType>
Enclosure 1, ADC 1311

Page 2

 </xsd:element>

 <xsd:element name="CONTRACT_ADMIN_OFFICE" minOccurs="0" maxOccurs="1">

 <xsd:simpleType>

 <xsd:restriction base="xsd:string">

 <xsd:maxLength value="1"/>

 <xsd:pattern value="Y|N| "/>

 </xsd:restriction>

 </xsd:simpleType>

 </xsd:element>

 <xsd:element name="CGAC" minOccurs="0" maxOccurs="1">

 <xsd:simpleType>

 <xsd:restriction base="xsd:string">

 <xsd:maxLength value="3"/>

 </xsd:restriction>

 </xsd:simpleType>

 </xsd:element>

 <xsd:element name="SUB_TIER_CODE" minOccurs="0" maxOccurs="1">

 <xsd:simpleType>

 <xsd:restriction base="xsd:string">

 <xsd:maxLength value="4"/>

 </xsd:restriction>

 </xsd:simpleType>

 </xsd:element>

 </xsd:sequence>

 </xsd:complexType>

 </xsd:element>

 </xsd:element>

 </xsd:sequence>

 </xsd:complexType>

 </xsd:element>

 </xsd:sequence>

 </xsd:complexType>

 </xsd:element>

</xsd:schema>