DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

April 04, 2018 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) AND 

JOINT PHYSICAL INVENTORY WORKING GROUP (JPIWG) MEMBERS

SUBJECT: Addendum to Approved Defense Logistics Management Standards (DLMS) 

Change (ADC) 1224A, Requirements for Air Force Government Furnished 

Property (GFP) Accountability including Identification of the Contractor Inventory 

Control Point (CICP), the Physical Location of Property, the Authorizing 

Procurement Instrument Identifier (PIID), Disposal Information in the Issue 

Transaction, and Enhanced Data Content in Inventory-Related Transactions

(Supply/Contract Administration) 

We are forwarding the attached addendum to DLM 4000.25, Defense Logistics 

Management Standards (DLMS), for implementation. This addendum replaces ADC 1224 in its 

entirety. The Enterprise Business Standards Office will post updated DLMS Implementation 

Conventions (IC) to the DLMS Web at 

http://www.dla.mil/HQ/InformationOperations/DLMS/elibrary/Transformats/140_997/, within 

10 days from the above date.

Addressees may direct questions to DLMSSupply@dla.mil. Others must contact their 

designated Supply PRC or JPIWG representative available at 

http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/. 

HEIDI M. DAVEREDE

Program Manager

Enterprise Business Standards Office

Attachment

As stated 

cc: 

ODASD (SCI)

OUSD DPAP (PDI) 

Air Force Finance PRC Representative
Attachment, Addendum to ADC 1224A

Page 1

Attachment to Addendum to ADC 1224A

Requirements for Air Force Government Furnished Property (GFP) 

Accountability Including Identification of the Contractor Inventory 

Control Point (CICP), the Physical Location of Property, the

Authorizing Procurement Instrument Identifier (PIID), Disposal 

Information in the Issue Transaction, and Enhanced Data Content 

in Inventory-Related Transactions

1. ORIGINAT ING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Mr. John “Jack” Dillon, HAF/A4PT; 937-904-0815; DSN: 674-

0815; or email: john.dillon.2.ctr@us.af.mil

b. Functional POC: Mr. Colquitt “Quitty” Lawrence, HAF/A4LR; 703-692-2348; 

DSN: 222-2348; or email: colquitt.lawrence.civ@mail.mil

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply/Contract Administration 

b. Primary/Secondary Functional Process: Government Furnished PropertyAccountability (GFP-A)

3. REFERENCES:

a. Office of the Under Secretary of Defense for Acquisition, Technology and Logistics 

(OUSD (AT&L)) Memo of January 11, 2010, Subject: Government Furnished Property (GFP), 

Describes the requirements for strengthening the accountability and management of personal 

property owned by the DOD when property is used on contracts.

b. Approved DLMS Change (ADC) 1161A, Update Uniform Procurement Instrument 

Identifier (PIID) Numbering System in the Federal/DLMS Implementation Conventions and 

DLMS Manuals, February 23, 2017

c. Proposed DLMS Change (PDC) 1225, Revise DLMS 527R Receipt Transaction for 

Intra-Air Force GFP Accountability to include Identification of the CICP, Addition of Moving 

Average Cost (MAC), and Authorization to use Latest Acquisition Cost (LAC) and Acceptance 

Date, December 12, 2016 (draft ADC under development)

d. PDC 1238, Revise DLMS 527R Materiel Receipt Acknowledgement (MRA) and 

Disposition Services Turn-In Receipt Acknowledgement (TRA) Transactions to Allow Air Force 

CICP to Forward Transaction Images in Support of Air Force Government Furnished Property

(GFP) Accountability, September 20, 2016 (draft ADC under development)

e. DODM 4140.01, DOD Supply Chain Materiel Management Procedures, Volume 5, 

Delivery of Materiel
Attachment, Addendum to ADC 1224A

Page 2

f. DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 2, Supply 

Standards and Procedures

g. DODI 5000.64, Accountability and Management of DoD Equipment and Other 

Accountable Property, May 19, 2011

h. DODI 4161.02, “Accountability and Management of Government Contract Property,”

April 27, 2012

4. APPROVED CHANGE(S): This addendum replaces ADC 1224 in its entirety. See yellow 

highlighting for corrections subsequent to the approval of the original ADC 1224. This 

addendum to ADC 1224 does not make any changes to the original updates. Note that references 

to Government-furnished materiel (GFM) are changed to GFP throughout, but are not 

highlighted.

a. Brief Overview of Change:

(1) This addendum makes additional changes to the implementation convention

tables not initially documented as intended under ADC 1224. All existing requirements 

documented in ADC 1224 will remain unchanged and implementation efforts must take place 

accordingly. 

(2) In order to establish Air Force GFP accountability, Air Force Contractor 

Inventory Control Points (CICPs) are required to share inventory accounting transactions with 

the Air Force accountable property system of record (APSR). The APSR will maintain the Air 

Force accountable property record for all Air Force-owned contractor managed and possessed 

property. This change revises multiple DLMS transactions that impact the Air Force owned 

inventory in possession of the CICP and impacts the financial statement for the Air Force. This 

change updates the DLMS 527R Materiel Receipt Acknowledgement (MRA) and Disposition 

Services Turn-in Receipt Acknowledgement (TRA), DLMS 846P Physical Inventory Request, 

846R Location Reconciliation Request, DLMS 945A Materiel Release Advice transactions, 

947I Inventory Adjustment, and 867I Issue transactions to enhance the visibility of GFP through 

logistics transactions and maintain required accountability as follows. 

(3) This change inserts DLMS notes (and codes as needed) to clarify 

identification of the CICP as the custodial activity for GFP accountability reporting and the Air 

Force program manager as the owner of the property. Additionally, because AF GFP-A 

transactions identify the CICP as the transaction submitter or recipient, this change authorizes 

separate inclusion of the DOD activity address code (DoDAAC) associated with the physical 

location of the property under the CICP’s responsibility. This DoDAAC may be the CICP’s, a

CICP-owned warehouse’s, or belong to a subcontractor facility.

(4) This change adds a data field for the DFARS procurement instrument 

identifier (PIID) (formerly contract number) authorizing the issue of GFP to the Air Force CICP. 

This change is required by the Office of the Under Secretary of Defense for Acquisition, 

Technology and Logistics (OUSD (AT&L)) memo (Reference 3.a) and ADC 1161 (Reference 

3.b.). This change also allows identification of legacy-formatted call/order numbers for CICP 

use pending implementation of the PIID-formatted contract number.
Attachment, Addendum to ADC 1224A

Page 3

(5) This change updates data content authorized for inclusion on the DLMS 867I 

Issue transaction to include the disposal-specific data elements, the date/time of the issue (i.e., 

the date/time associated with the custodial activity reducing the available for issue balance), and 

the mode of shipment. Mode of Shipment in the DLMS 867I or 945A will identify which 

issues/shipments are subject to intransit tracking. The Defense Property Accountability System 

(DPAS) will not establish an intransit for DOD Mode of Shipment X (Bearer, walk-thru 

(customer pickup of material). DPAS will immediately drop the property from inventory and 

report the issue to financial. Mode of Shipment X will identify local disposal and local delivery 

within the CICP.

(6) This change authorizes multiple enhancements to the Physical Inventory 

Request, Location Reconciliation Request, and Inventory Adjustment to include use of a 

document number assigned by the Air Force program manager (using DPAS) to the inventory 

request that will be perpetuated to the responding inventory adjustment. This change also 

authorizes enhancements for use of a date/time for transaction generation, and the addition of an 

expected reply date for reporting on the requested physical inventory. 

b. Background:

(1) The term CICP represents a contractor assigned the primary responsibility for 

the property management of a group of items either for a particular Military Service or for the 

Department of Defense as a whole. In addition to Integrated Materiel Management (IMM) 

functions, a CICP may perform other logistics functions in support of a particular Military 

Service or for a particular end item (e.g., centralized computation of retail requirements levels 

and engineering tasks associated with weapon system components.) 

(2) For the purpose of DLMS logistics procedures, the term CICP also identifies

Contractor Operated and Maintained Base Supply (COMBS) contractors whose support includes 

supply of aircraft, engine and support equipment components, materiel, and consumables, as well 

as off-aircraft repair, overhaul, and replenishment. COMBS contractors are responsible for 

having parts on hand to perform off-aircraft maintenance and for repairing the parts turned in. 

COMBS contractors perform both wholesale and retail functions. 

(3) CICPs are required to maintain and report accountability for Air Force-owned 

contractor-managed and possessed property. However, Air Force accountability is incomplete 

for contractor-managed and possessed Air Force-owned property due to the Air Force inability to 

track end-to-end logistics and financial transactions, provide total asset visibility, and report 

property inventory values in an accurate and timely manner. DODM 4140.01 Volume 5

(Reference 3.b.), Enclosure 3, Subparagraph 2.b.(4)(e), requires services to “Take applicable 

actions necessary to ensure that the physical on-hand quantity and the total item property record 

quantity are in agreement for all DoD property that is not in the physical custody of DoD storage 

activities. For example, owning materiel managers will ensure accuracy for property records 

whereas contractors are responsible for the physical custody of government-owned inventory located 

at contractor facilities or DOD storage activities.”

(4) The Air Force chartered the Government Furnished Property - Accountability 

(GFP-A) Capability Initiative to provide property accountability/control of contractor managed 

and possessed Air Force-owned property (inclusive of materiel and equipment) through 

implementation of standard and integrated Air Force logistics and contractor processes to address 

a material weakness on the Air Force financial statements. This capability will establish and 
Attachment, Addendum to ADC 1224A

Page 4

maintain accountable inventory records for GFP that accurately reflect current quantity, status, 

location, condition and authorizing contract as well as establish an audit trail to update and track 

end-to-end logistics and financial transactions. This change is one of a series of DLMS changes 

supporting the Air Force GFP-A Capability Initiative (refer to References 3.c. and 3.d.).

(5) Contractor managed and possessed GFP is but one type of Government 

Furnished Property and is the sole focus of this capability initiative. The above problem 

statement does not apply to the other types of Government Furnished Property as the Air Force

has property solutions in place for the reporting of logistics and financial data. The GFP-A 

Capability Initiative is only applicable to Air Force-owned property reported in the Air Force

GFP-A APSR. Air Force CICPs often use commercially available inventory management 

systems (IMSs) to manage Air Force-owned property and the CICP’s record inventory,

impacting accounting transactions in these systems. The Air Force selected the DPAS as its 

APSR for contractor-managed and possessed Air Force-owned GFP. 

(6) Air Force CICPs, using their own IMS, will provide their transactions and 

images of their transactions, in DLMS formats, to DPAS via the Defense Automatic Addressing 

System (DAAS). Note that this is over and above the transmission of the applicable DLMS 

transactions for the various logistics processes discussed in this ADC that the CICP and the 

CICP’s warehouse or subcontractor exchange via external communication (outside the IMS). 

DPAS will be a mirror image of the CICP’s IMS and, in order to maintain accuracy, this DLMS 

change adds or authorizes the use of certain data elements within DLMS transactions.

(7) DPAS requires the PIID authorizing GFP issued to the CICP (if GFP is 

authorized on a PIID call/order (F in 9th position), the PIID call/order number will be included)

for accountability of the property. Inclusion of the location of the GFP held by the CICP 

(separate warehouse or subcontractor’s facility) ensures the Air Force program manager has full

visibility of the Air Force-owned property. DPAS will match the disposal authority code in the 

Issue transaction to verify the Air Force program manager approved the disposal in accordance 

with Air Force CICP contract terms. DPAS also requires enhancements to provide the document 

number and expected response date for the physical inventory request assigned by the requesting 

activity. DPAS will match physical inventory requests and CICP responses for Air Force 

program manager oversight. 

(8) Prior to submission of the proposed change, the DLMS Program Office 

identified a future requirement for transition from routing identifier codes (RIC) to DoDAACs. 

This transition will require DAAS to route and process DLMS transactions based upon the 

DoDAAC-To (rather than the current RIC-To) in the transaction and use the communication 

routing identifier (COMMRI) associated with the DoDAAC in the DoD Activity Address 

Directory (DoDAAD). While developing the proposed change, the DLMS Program Office 

attempted to authorize use of the DoDAAC-To on a limited basis to identify the Air Force

program manager account in DPAS. However, the DLMS Program Office subsequently

recognized the affected systems could not implement this change within the required timeline for 

implementation. The DLMS Program Office, DAAS, and the Air Force agreed on the alternate 

approach to facilitate immediate implementation. This alternate approach will accommodate the 

potential lack of available RICs within the required Air Force series as the Air Force establishes 

new program managers’ accounts in DPAS. Therefore, pending development of functionality for 

DoDAAC-based routing/processing, the Air Force will use RICs for identification of both CICPs 

and program managers. If the Air Force has insufficient RICs available to identify all program 
Attachment, Addendum to ADC 1224A

Page 5

managers, this ADC authorizes the Air Force to use a single generic RIC representing the Air 

Force APSR. DAAS will use this RIC/DoDAAC/COMMRI combination for transaction 

processing while DPAS will use the supplemental identification of the specific program manager 

DoDAAC required within each transaction. This ADC reflects the interim solution described. 

b. Approved Change in Detail:

(1) Revise DLMS 527R MRA and TRA, DLMS 846P Physical Inventory 

Request, 846R Location Reconciliation Request, 867I Issue, 945A Materiel Release Advice, and 

947I Inventory Adjustment transactions to add a data field for identification of the authorizing 

PIID (formerly contract number). Adding this field will allow the Air Force CICP to identify the

authorizing PIID, as applicable, in the listed transactions sent to the Air Force program 

manager’s APSR (DPAS). If GFP is authorized under a PIID call/order number (F in 9th 

position), the PIID call/order will be provided in the PIID field. Including the PIID will 

strengthen the accountability and management of government owned property when contractors 

possess the property. Additionally, add the legacy call/order number data field for use pending 

full transition to the PIID.

(2) Revise DLMS 846P Physical Inventory Request, 846R Location 

Reconciliation Request, 867I Issue, 945A Materiel Release Advice, and 947I Inventory 

Adjustment transactions as follows:

(a) Provide DLMS notes and new data fields as needed to clarify that the 

Air Force CICP and the Air Force program manager exchange these transactions for the purpose 

of GFP accountability. Because the CICP has custodial responsibility for the Governmentowned property, the CICP is mapped to the DLMS data field normally used by the storage 

activity/distribution center. The Air Force will assign each CICP to a program manager 

identified by a unique DoDAAC in DPAS. DAAS will use the COMMRI for the RIC associated 

with the program manager’s DoDAAC in the DoDAAD to route/direct the transaction to DPAS. 

Alternatively, if the Air Force has insufficient RICs available to identify the specific program 

manager in the transaction RIC-To, this change authorizes the Air Force CICP to identify the Air 

Force APSR by its generic RIC for DAAS routing/processing and separately include the CICP 

DoDAAC so DPAS can post the record to the appropriate program manager account.

(b) Add/authorize use of a data field to identify the physical location of 

the Air Force-owned contractor-managed assets. The CICP must use a DoDAAC to identify the 

location of property. This may be the CICP, a specific warehouse operated by the CICP, or a

sub-contractor location. Although policy does not require the CICP’s warehouse location in the 

APSR, this information will enhance the Air Force’s visibility of Air Force-owned assets.

(3) Revise DLMS, 867I Issue transaction to include additional required data 

content. The data elements listed under 3(a) are “authorized DLMS enhancements” and will be 

available for use by all Components without further coordination. Components may adopt the 

use of authorized DLMS enhancement data when applicable to their business process. 

Components should ensure that inclusion of this data in a DLMS transaction does not cause 

inappropriate rejection of the transaction.

(a) Revise to authorize use of DLMS enhancements associated with 

issues to DLA Disposition Services or in local disposal actions. The listed data elements 
Attachment, Addendum to ADC 1224A

Page 6

currently apply to the Disposal Release Order and Disposal Release Confirmation and were 

originally added to the Issue transaction as a future DLMS enhancement. 

1. Disposal Authority Code. This data element indicates that the 

owner is authorizing the transfer of the property to disposal.

2. Disposal Reason Code. This data element indicates the reason 

property is transferred to disposal.

3. Precious Metals Indicator Code. This data element indicates 

the precious metals content of the property transferred to disposal.

4. Automated Data Processing (ADP) Equipment Identification 

Code. This date element identifies ADP equipment transferred to disposal.

(b) Revise to authorize use of the DLMS enhancement for identification 

of the Issue Date and open a subordinate data field for inclusion of the Issue Time.

(c) Revise to authorize use of the DLMS enhancement for identification 

of the Transportation Method/Type Code (mode of shipment). 

(4) Revise the DLMS 846P Physical Inventory Request to include new content 

and authorize use of previously identified enhancements.

(a) Authorize use of the DLMS enhancement for inclusion of a document 

number for the physical inventory request assigned by the requesting activity. This data element 

will be available only to the Air Force GFP accountability process, and will require a separate 

PDC if other Components have a similar requirement. 

(b) Establish a new data element for identification of a Physical Inventory 

Reply Date allowing the Air Force program manager to request completion of a physical 

inventory and response by an identified date. Contractual terms between the contractor and the 

program office will identify the Physical Inventory Reply time standard. The Physical Inventory 

Reply date must be within the timeframe to conduct a physical inventory specified in the DLMS 

(MILSTRAP) procedures. 

(c) Authorize use of the DLMS enhancement for the beginning segment 

date and time for creation of the transaction. The date and time are authorized DLMS 

enhancements per standard DLMS modernization procedures to provide a systemic date/time 

stamp for all transactions. This date and time is not for functional use even though they may 

coincide with the date and time of a business process. 

(d) Establish two new data elements for the Physical Inventory Request 

Creation Time for use in conjunction with the existing Physical Inventory Request Creation 

Date. These data fields are applicable for functional use.

(5) Revise the DLMS 846R Location Reconciliation Request to include

applicable dates and times.
Attachment, Addendum to ADC 1224A

Page 7

(a) Authorize use of the DLMS enhancement for the beginning segment 

date and time for creation of the transaction. The standard DLMS modernization procedures 

authorize the use of date and time in the beginning segment as DLMS enhancements to provide a 

systemic date/time stamp for all transactions. This date and time is not for functional use even 

though they may coincide with the date and time of a business process.

(b) Establish a new data element for the Location Reconciliation 

Transaction Creation Date and Location Reconciliation Transaction Creation Time. These data 

fields are applicable for functional use.

(6) Revise the DLMS 9471 Inventory Adjustment to include a supporting 

document number field for perpetuation of the Physical Inventory Request Document Number to 

the resulting response contained in the Inventory Adjustment transaction.

d. Revisions to DLM 4000.25 Manuals: Revise DLMS 527R, 846P, 846R, 867I, 

945A and 947I implementation conventions (ICs) as shown in Enclosure 1.

e. Transaction Flow: See Enclosure 2 for transaction flow diagrams and narrative for 

all transactions associated with this change other than the DLMS 527R. Refer to ADC 1238 

(Reference 3.c.) for flow diagrams and narrative associated with the DLMS 527R supporting a 

new use for image transaction functionality.

f. Alternatives: Manual process to match the CICP’s PIID and DoDAAC with the 

transaction and enter in the Air Force GFP-A APSR. Manual processes to match 846P 

Physical Inventory Request with the result of the physical inventory provided by 947I 

Inventory Adjustment, could result in errors and delays in matching. 

5. REASON FOR CHANGE:

a. Supports compliance with DODI 5000.64 (Reference 3.g.) and DODI 4161.02

(Reference 3.h.), to trace transactions involving GFP electronically, and to cite the Air Force

CICP’s PIID.

b. Supports Air Force GFP-A Capability Initiative addressing a material weakness in 

Air Force financial statements and support Financial Improvement and Audit Readiness 

(FIAR). 

c. In Reference 3.a, OUSD (AT&L) identified specific goals to reinforce internal 

controls over the accountability for DOD property provided to contractors by DOD 

Components. A key requirement is to cite a PIID under which the contractor has the authority 

to receive property pushed to the contractor by DOD Components. This change will enable the 

Air Force CICP GFP PIID to be perpetuated on relevant transactions through the logistics 

pipeline. 

d. Inclusion of the disposal-specific data elements in the Issue transaction will allow 

greater visibility and validation by the property owner. 

e. Inclusion of the date/time of issue will allow the Air Force to properly record the 

transaction in the APSR and will assist in reconciliation processing.
Attachment, Addendum to ADC 1224A

Page 8

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: The Air Force CICP’s PIID and the DoDAAC identifying the physical 

location of the property data fields allow the Air Force to monitor GFP through enterprise 

visibility/accountability programs and comply with the expanded GFP tracking requirements.

Inclusion of the disposal-related data elements in the issue transaction provides visibility of 

required information to ensure proper disposal actions. Automated monitoring and notification 

of physical inventory requests and responses will enhance Air Force monitoring of GFP and 

prevent manual workload.

b. Disadvantages: Required resources for system modifications to accommodate and

perpetuate the Air Force’s CICP PIID on the identified transactions and adopt additional data 

content described in this change.

7. ADDITIONAL COMMENTS TO CONSIDER: Air Force GFP-A Capability Initiative 

relies on DLMS transactions from the Air Force CICPs to accurately record asset quantities and 

valuation. Without the ability to transmit transactions between the CICP and the program 

manger’s APSR with reference to the CICP’s PIID, the Air Force will need a manual 

workaround to record the applicable transactions and CICP’s PIID. This increases the risk of 

misreporting the Air Force contractor-managed and possessed Air Force-owned GFP assets on 

its financial statements.

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Target implementation 

date is April 2017. 

Note: At this time, DAAS will only route/process these transactions to the program manager 

RIC and associated COMMRI. The previously proposed routing/processing by program 

manager DODAAC/COMMRI is deferred pending further analysis.

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: Air Force is unable to estimate at this time; Air 

Force does not have adequate data to calculate cost of manual workaround. 

10. IMPACT:

a. New DLMS Data Elements: The following new data elements are new in this 

change; refer to Enclosure 1 for details.

(1) Physical Inventory Expected Reply Date

(2) Physical Inventory Request Creation Date and Physical Inventory Request 

Creation Time

(3) Location Reconciliation Transaction Creation Date and Location 

Reconciliation Transaction Creation Time

(4) Physical Inventory Request Document Number. This is the document 

number originally assigned for the Physical Inventory Request and perpetuated as a supporting 

document number in the Physical Inventory Adjustment response to the Physical Inventory 

Request.
Attachment, Addendum to ADC 1224A

Page 9

b. Changes to DLMS Data Elements: There are no revised data elements.

c. Automated Information Systems (AIS):

(1) Identified changes are applicable to DPAS and Air Force CICP IMS. 

(2) Other Component systems may implement those DLMS enhancements 

identified as “authorized DLMS enhancements” without further coordination by DLMS change.

d. DAAS: This change requires updates to DAAS mappings. Where the CICP 

identifies the Air Force program manager in the APSR by a RIC (N101 Code OW), DAAS 

maps should equate this value to the legacy data field traditionally used by the owning 

inventory control point. 

e. Non-DLM 4000.25 Series Publications:

(1) Air Force should take action necessary to update procedures documenting the 

requirements contained herein as needed for Air Force and for the DPAS. 

(2) OUSD(AT&L)/ARA, Property & Equipment Policy, is in the process of 

coordinating a revision to DODI 5000.64, Accountability and Management of DOD Equipment 

and Other Accountable Property (Reference 3.g.), to address use of the DLMS for equipment, 

among other updates. The proposed wording will recognize use of the DLMS for electronic 

interfaces between DOD supply systems and the APSR to facilitate accountable property 

management. By virtue of the contractual requirements levied by the Air Force on the CICP, 

the procedures discussed in this change for managing Government-owned equipment fall within 

the scope of the pending update to DoDI 5000.64 establishing authoritative guidance for use of 

the DLMS. 

11. PROPOSED DLMS CHANGE (PDC) 1224 STAFFING RESPONSE/COMMENT 

RESOLUTION: 

Originator Response/Comment Disposition

1. DLA No response

2. Navy Concur. Noted.

3. Air Force Concur. Noted.

4. Army No response

5. Marine Corps No response
Enclosure 1, Addendum to ADC 1224A

Page 1

Enclosure 1 – Addendum to ADC 1224A

Revise DLMS implementation conventions (ICs) as shown:

Table A – 527R

# Location Revisions to DLMS 527R

Materiel Receipt Acknowledgment and Turn-in 

Receipt Acknowledgment

Reason

1. DLMS Introductory 

Notes

Add ADC 1224 to the list of applicable DLMS 

changes included in the DLMS IC introductory notes: 

-ADC 1224, Requirements for Air Force 

Government Furnished Property (GFP) 

Accountability including Identification of the 

Contractor Inventory Control Point (CICP), the 

Physical Location of Property, the Authorizing 

Procurement Instrument Identifier (PIID), Disposal 

Information in the Issue Transaction, and 

Enhanced Data Content in Inventory-Related 

Transactions

Identifies DLMS 

changes included in 

the IC.

2. 2/N901/030 Revise to add new Codes 6L and DO and associated 

DLMS Notes:

6L Agent Contract Number

DLMS Note:

1. Use for Air Force GFP accountability when 

forwarding an MRA or TRA image transaction 

(identified by BR06 Code FI) to the APSR to identify 

the procurement instrument identifier (PIID) 

applicable to the contract authorizing Air Force 

CICP custody of GFP. Use the legacy procurement 

instrument identification number (PIIN) pending 

transition to the PIID.

2. If GFP is authorized under a PIID call/order 

number (F in 9th position), provide the PIID 

call/order number in the PIID field. 

3. Authorized DLMS enhancement. Refer to ADC

1224.

DO Delivery Order Number

DLMS Note: 

1. Use in conjunction with the PIIN (Code 6L) for 

GFP-related transactions to identify the legacy four 

position call/order number associated with the PIIN 

applicable to the contract authorizing the contractor 

to have custody of GFP.

2. Do not use for the PIID call/order number. The 

PIID call/order number is mapped to Code 6L.

3. Authorized DLMS enhancement. Refer to ADC

1224.

Supports GFP

accountability 

requirement for 

identification of the 

authorizing PIID.

Refer ADC 1238 for 

additional Air Force 

GFP-A updates 

supporting a new 

use for image 

transaction 

functionality.
Enclosure 1, Addendum to ADC 1224A

Page 2

Table B – 846P

# Location Revisions to DLMS 846P

Physical Inventory Request

Reason

1. DLMS Introductory 

Notes

Add ADC 1224 to the list of applicable DLMS 

changes included in the DLMS IC introductory notes: 

- ADC 1224, Requirements for Air Force 

Government Furnished Property (GFP) 

Accountability including Identification of the 

Contractor Inventory Control Point (CICP), the 

Physical Location of Property, the Authorizing 

Procurement Instrument Identifier (PIID), Disposal 

Information in the Issue Transaction, and 

Enhanced Data Content in Inventory-Related 

Transactions

Identifies DLMS 

changes included in 

the IC.

2. 1/BIA04/20 Move Federal note to DLMS note level. Revise 

DLMS notes for existing data element.

Date

Federal Note: This date is the date of the

transaction set preparation and

corresponds to the Universal Time

Coordinate (UTC).

DLMS Note:

1. This date is the date of the transaction set 

preparation and corresponds to the Universal Time 

Coordinate (UTC).

2. Authorized DLMS enhancement; see introductory 

DLMS note 4a 4g. on IC cover page.

Allows for use of 

the transaction set 

preparation date as 

an authorized 

DLMS 

enhancement.

This is not 

considered a 

“functional” date for 

a business process; 

instead, this date is 

associated with an 

enhancement that 

provides a systemic 

date/time for 

generation of all 

DLMS transactions.

3. 1/BIA05/20 Move Federal note to DLMS note level. Revise 

DLMS notes for existing data element.

Time

Federal Note: Express the originating activity's time 

of transaction set preparation in UTC.

DLMS Note: 

1. This is the time of the transaction set preparation 

and corresponds to the Universal Time Coordinate 

(UTC). Express time in a four-position (HHMM) 

format, except for CAV II. CAV II expresses time in 

an eight-position Format (HHMMSSDD).

2. Authorized DLMS enhancement; see introductory

DLMS note 2 4g. on IC cover page.

Allows for use of 

the transaction set 

preparation time as 

an authorized 

DLMS 

enhancement.

See above note.

4. 1/N101/80 Add DLMS notes for existing Codes SB and add new 

Code OW:

OW Owner of Property or Unit

Supports GFP

accountability 

transactions 

between the CICP 
Enclosure 1, Addendum to ADC 1224A

Page 3

# Location Revisions to DLMS 846P

Physical Inventory Request

Reason

DLMS Note:

For Air Force GFP accountability, use to identify 

the Air Force program manager in the accountable 

property system of record (APSR). Must identify the 

program manager by RIC. If the program manager 

DoDAAC does not have an assigned RIC, use the 

generic Air Force GFP APSR RIC with 2/N106=FR 

and provide the program manager DoDAAC at 

2/N101450 Code OW. Refer to ADC 1224.

SB Storage Area

DLMS Note:

1. Use to indicate the depot or storage activity.

2. For Air Force GFP accountability, use to identify 

the CICP as the responsible custodial activity. Refer 

to ADC 1224.

and the program 

manager using 

DPAS. 

2/DTM01/100 Add new Code 501 and associated DLMS notes:

501 Expected Reply

DLMS Note:

1. For Air Force GFP accountability, use to identify 

the due date established by the Air Force program 

manager for the CICP response to the requested 

physical inventory. Use in conjunction with 

document number assigned to this specific request

(REF01 Code TN). Refer to ADC 1224.

2. DLMS enhancement; See introductory DLMS 

note 4a.

Supports GFP

accountability 

requirement for 

identification of the 

expected response 

to the physical 

inventory request.

2/DTM03/100 Open DTM03 for use and add the associated DLMS 

notes:

Time

DLMS Note:

1. Use with Code 097 (Transaction Creation) to 

provide the time associated with preparation of the 

physical inventory request.

2. Express time in UTC using a four-position 

(HHMM) format.

3. Authorized DLMS enhancement; see introductory 

DLMS note 4.g.

Establishes a new 

DLMS 

enhancement for use 

as needed without 

further coordination 

at the DOD level.

Provided to support 

tracking of request 

and response.

2/REF01/140 Revise DLMS notes for existing Code TN and add 

new Codes 6L and DO and associated DLMS Notes:

6L Agent Contract Number

DLMS Note:

1. Use in GFP-related transactions to identify the 

procurement instrument identifier (PIID) applicable 

to the contract authorizing the contractor to have 

custody of GFP. Use the legacy procurement 

instrument identification number (PIIN) pending 

transition to the PIID.

Supports GFP

accountability 

requirement for 

identification of the 

authorizing PIID.
Enclosure 1, Addendum to ADC 1224A

Page 4

# Location Revisions to DLMS 846P

Physical Inventory Request

Reason

2. If GFP is authorized under a PIID call/order 

number (F in 9th position), provide the PIID 

call/order number in the PIID field. 

3. Required for Air Force GFP accountability to 

identify the CICP’s contract number. 

4. Authorized DLMS enhancement. Refer to ADC

1224.

DO Delivery Order Number

DLMS Note: 

1. Use in conjunction with the PIIN (Code 6L) for 

GFP-related transactions to identify the legacy four 

position call/order number associated with the PIIN 

applicable to the contract authorizing the contractor 

to have custody of GFP.

2. Do not use for the PIID call/order number. The 

PIID call/order number is mapped to Code 6L.

3. Authorized DLMS enhancement; see introductory 

DLMS note 4e. on IC cover page. Refer to ADC

1224.

TN Transaction Reference Number

DLMS Note:

1. For Air Force GFP accountability, use to identify 

the document number assigned by the Air Force 

program manager in the accountable property 

system of record (APSR). The CICP must 

perpetuate the document number to the response. 

Refer to ADC 1224.

2. DLMS enhancement; See introductory DLMS note 

4a.

2/N1/450 Remove Federal Note and add the following DLMS 

Note:

DLMS Note: Must use at least one iteration of this 

N1 segment to identify the organization to receive 

the transaction (N106 code TO with appropriate

N101 code). May use additional iterations to identify 

other organizations associated with the transaction.

Supports GFP 

accountability 

transactions 

between the CICP 

and the program 

manager using 

DPAS. 

8. 2/N101/450 Add new Code LG and OW and associated DLMS 

notes. Revise DLMS notes for existing Code SB:

LG Location of Goods

DLMS Note:

1. Use to identify the physical location of GFP while 

in CICP custody. The location may be the CICP, 

the CICP’s warehouse or subcontractor. This 

location must be identified by DoDAAC. 

2. Must use for Air Force GFP accountability. 

Refer to ADC 1224.

Supports GFP

accountability 

transactions 

between the CICP 

and the program 

manager (DPAS).
Enclosure 1, Addendum to ADC 1224A

Page 5

# Location Revisions to DLMS 846P

Physical Inventory Request

Reason

SB Storage Area

DLMS Note:

1. Use to indicate the depot or storage activity.

2. For Air Force GFP accountability, use to identify 

the CICP as the responsible custodial activity. Refer 

to ADC 1224.

OW Owner of Property or Unit

DLMS Note:

1. For Air Force GFP accountability, use to identify 

the Air Force program manager in the accountable 

property system of record (APSR). Refer to ADC 

1224

2. For transactions directed to the APSR, must

identify the program manager by RIC. If the 

program manager DoDAAC does not have an 

assigned RIC, use the generic Air Force GFP APSR 

RIC with 2/N106=TO and use a second iteration of 

the N1 loop (repeating Code OW without 

2/N106=TO) to provide the program manager 

DoDAAC. 

3. For transactions sent from the APSR using the 

generic Air Force GFP APSR RIC 1/N101/80 Code 

OW), use to identify the program manager 

DoDAAC.

2/N103/450 Revises DLMS notes for existing Code 10 

10 Department of Defense Activity Address Code 

(DODAAC)

DLMS Note:

DLMS Note:

1. DLMS enhancement; see introductory DLMS note 

5a.

2. Authorized DLMS enhancement for Inter-Service 

Ammunition use with N101 code CN to identify

consignee DODAAC (DIC BG1/BG2 rp 66-71). See 

introductory DLMS note 5f. (Refer to ADC 261 and

ADC 445.)

3. Authorized for use by Air Force CICP to identify 

other organizations associated with the transaction 

by DODAAC. (Refer to ADC 1224A).

Supports GFP 

accountability 

transactions 

between the CICP 

and the program 

manager using 

DPAS. 

2/N106/50 Revise segment element N106 Use attribute from 

“must use” to “use”: 

Supports GFP 

accountability 

transactions 

between the CICP 

and the program 

manager using 

DPAS. 
Enclosure 1, Addendum to ADC 1224A

Page 6

Table C – 846R

# Location Revisions to DLMS 846R

Location Reconciliation Request

Reason

1. DLMS Introductory 

Notes

Add ADC 1224 to the list of applicable DLMS 

changes included in the DLMS IC introductory notes:

- ADC 1224, Requirements for Air Force 

Government Furnished Property (GFP) 

Accountability including Identification of the 

Contractor Inventory Control Point (CICP), the 

Physical Location of Property, the Authorizing 

Procurement Instrument Identifier (PIID), Disposal 

Information in the Issue Transaction, and 

Enhanced Data Content in Inventory-Related 

Transactions

Identifies DLMS 

changes included in the 

IC.

2. 1/BIA04/20 Move Federal note to DLMS note level. Revise 

DLMS notes for existing data element.

Date

Federal Note: This date is the date of the

transaction set preparation and

corresponds to the Universal Time

Coordinate (UTC).

DLMS Note:

1. This is the date of the transaction set preparation 

and corresponds to the Universal Time Coordinate 

(UTC).

2. Authorized DLMS enhancement; see

introductory DLMS note 4a 4g on IC cover page.

Allows for use of the 

transaction set 

preparation date as an 

authorized DLMS 

enhancement. This is 

not considered a 

“functional” date for a 

business process; 

instead, this date is 

associated with an 

enhancement that 

provides a systemic 

date/time for 

generation of all DLMS 

transactions.

3. 1/BIA05/20 Move Federal note to DLMS note level. Revise 

DLMS notes for existing data element.

Time

Federal Note: Express the originating activity's 

time of transaction set preparation in UTC.

DLMS Note: 

1. This is the time of the transaction set preparation 

and corresponds to the Universal Time Coordinate 

(UTC). Express time in a four-position (HHMM) 

format, except for CAV II. CAV II expresses time in 

an eight-position Format (HHMMSSDD).

2. Authorized DLMS enhancement; see introductory 

DLMS note 2 4g on IC cover page.

Allows for use of the 

transaction set 

preparation time as an 

authorized DLMS 

enhancement.

See above note.

4. 1/N101/80 Revise DLMS Notes for existing Codes OW and SB 

and add new Code LG with associated notes:

OW Owner of Property or Unit

DLMS Note:

1. Use to identify the owner of the property reported.

2. For Air Force GFP accountability, use to identify 

the Air Force program manager in the accountable 

property system of record (APSR). Must identify the 

Supports GFP

accountability 

transactions between 

the CICP and the 

program manager using 

DPAS. 
Enclosure 1, Addendum to ADC 1224A

Page 7

# Location Revisions to DLMS 846R

Location Reconciliation Request

Reason

program manager by RIC. If the program manager 

DoDAAC does not have an assigned RIC, use the 

generic Air Force GFP APSR RIC with 2/N106=TO 

and use a second iteration of the N1 loop (repeating 

Code OW without 2/N106=TO) to provide the 

program manager DoDAAC. Refer to ADC 1224.

SB Storage Area

DLMS Note:

1. Must use to identify the depot or storage activity.

2. For Air Force GFP accountability, use to identify 

the CICP as the responsible custodial activity. 

Refer to ADC 1224.

LG Location of Goods

DLMS Note:

1. Use to identify the physical location of GFP while 

in CICP custody. The location may be the CICP, 

the CICP’s warehouse or subcontractor. This 

location must be identified by DoDAAC. 

2. Must use for Air Force GFP accountability. 

Refer to ADC 1224.

5. N1 Segment Remove Federal Note and add the following DLMS 

Note:

DLMS Note: Must use at least one iteration of this 

N1 segment to identify the organization to receive 

the transaction (N106 code TO with appropriate

N101 code). May use additional iterations to 

identify other organizations associated with the 

transaction.

Supports GFP 

accountability 

transactions between 

the CICP and the 

program manager using 

DPAS. 

6. 2/N103/80 Revises DLMS notes for existing Code 10 

10 Department of Defense Activity Address Code 

(DODAAC)

DLMS Note:

DLMS Note:

1. DLMS enhancement; see introductory DLMS note 

5a.

2. Authorized DLMS enhancement for Inter-Service 

Ammunition use with N101 code CN to identify

consignee DODAAC (DIC BG1/BG2 rp 66-71). See 

introductory DLMS note 5f. (Refer to ADC 261 and

ADC 445.)

3. Authorized for use by Air Force CICP to identify 

other organizations associated with the transaction 

by DODAAC.

Supports GFP 

accountability 

transactions between 

the CICP and the 

program manager using 

DPAS. 

7. 2/N106/80 Revise segment element N106 Use attribute from 

“must use” to “use”: 

Supports GFP 

accountability 

transactions between 
Enclosure 1, Addendum to ADC 1224A

Page 8

# Location Revisions to DLMS 846R

Location Reconciliation Request

Reason

the CICP and the 

program manager using 

DPAS. 

8. 2/REF01/140 Add new Codes 6L and DO and associated DLMS 

Notes:

6L Agent Contract Number

DLMS Note:

1. Use in GFP-related transactions to identify the 

procurement instrument identifier (PIID) applicable 

to the contract authorizing the contractor to have 

custody of GFP. Use the legacy procurement 

instrument identification number (PIIN) pending 

transition to the PIID.

2. If GFP is authorized under a PIID call/order 

number (F in 9th position), provide the PIID 

call/order number in the PIID field.

3. Required for Air Force GFP accountability to 

identify the CICP’s contract number. 

4. Authorized DLMS enhancement. Refer to ADC

1224.

DO Delivery Order Number

DLMS Note: 

1. Use in conjunction with the PIIN (Code 6L) for 

GFP-related transactions to identify the legacy four 

position call/order number associated with the PIIN 

applicable to the contract authorizing the contractor 

to have custody of GFP.

2. Do not use for the PIID call/order number. The 

PIID call/order number is mapped to Code 6L.

3. Authorized DLMS enhancement; see introductory 

DLMS note 4e. on IC cover page. Refer to ADC

1224.

Supports GFP

accountability 

requirement for 

identification of the 

authorizing PIID.

Pending transition to 

PIID, allows 

identification of the 

PIIN and legacy 

call/order number.

9. 2/DTM03/100 Add new Code 097 and associated DLMS notes.

097 Transaction Creation

DLMS Note:

1. Use to identify the date the transaction was 

prepared.

2. Authorized DLMS enhancement; see introductory 

DLMS note 4.g. on IC cover page.

10. 2/DTM03/ 100 Open DTM03 for use and add the associated DLMS 

notes:

Time

DLMS Note:

1. Use with Code 097 (Transaction Creation) to 

provide the time associated with preparation of the 

physical inventory request.

Establishes a new 

DLMS enhancement 

for use as needed 

without further 

coordination at the 

DOD level.

Provided to support 

tracking of request and 

response.
Enclosure 1, Addendum to ADC 1224A

Page 9

# Location Revisions to DLMS 846R

Location Reconciliation Request

Reason

2. Express time in UTC using a four-position 

(HHMM) format.

3. Authorized DLMS enhancement; see introductory 

DLMS note 4.g. on IC cover page.

Table D – 867I

# Location Revisions to DLMS 867I

Issue

Reason

1. DLMS Introductory 

Notes

Add ADC 1224 to the list of applicable DLMS changes 

included in the DLMS IC introductory notes:

- ADC 1224, Requirements for Air Force Government 

Furnished Property (GFP) Accountability including 

Identification of the Contractor Inventory Control Point 

(CICP), the Physical Location of Property, the 

Authorizing Procurement Instrument Identifier (PIID), 

Disposal Information in the Issue Transaction, and 

Enhanced Data Content in Inventory-Related

Transactions

Identifies DLMS 

changes included 

in the IC

2. 1/N101/80 Revise DLMS notes for existing Code SB.

SB Storage Area

DLMS Note:

1. Use to identify the depot or storage activity. Use the 

Routing Identifier Code (RIC) for the activity unless 

otherwise authorized.

2. For Air Force GFP accountability, use to identify the 

CICP as the responsible custodial activity. Refer to ADC

1224.

Additional notes 

provided for 

clarification.

3. 2/DTM01/20 Revise DLMS notes for existing Code 102:

102 Issue

DLMS Note:

1. Must Use to identify the materiel issue date (date 

materiel was dropped from the accountable custodial

record “available-for-issue” balance).

2. Authorized DLMS enhancement; see introductory 

DLMS note 5a 5e. on IC cover page.

Authorizes use of 

DLMS 

enhancement data 

content as needed 

without further 

coordination at the 

DOD level.

Provided to 

support 

reconciliation of 

GFP.

4. 2/DTM03/20 Open DTM03 for use and add the associated DLMS notes:

Time

DLMS Note:

1. Use with Code 102 (Issue) to provide the time of issue.

2. Express time in UTC using a four-position (HHMM) 

format.

3. Authorized DLMS enhancement; see introductory 

DLMS note 5e. on IC cover page.

Establishes a new 

DLMS 

enhancement for 

use as needed 

without further 

coordination at the 

DOD level.

Provided to 

support 
Enclosure 1, Addendum to ADC 1224A

Page 10

# Location Revisions to DLMS 867I

Issue

Reason

reconciliation of 

GFP.

5. 2/REF01/30 Revise DLMS notes for existing Code CT and add new 

Codes 6L an DO and associated DLMS Notes:

CT Contract Number

DLMS Note:

1. Must Use in GFP-related transactions.

2. Use to provide contract information associated with the 

authorizing for shipments of GFP to the contractor.

32. Use to identify the procurement instrument identifier 

(PIID). Use the legacy procurement instrument 

identification number (PIIN) pending transition to the PIID. 

When GFP is authorized under a PIID call/order number (F 

in 9th position), provide the value in the PIID field.

43. Use for issue of contractor shipments of GFP into DoD 

inventory.

5. Authorized DLMS enhancement. Refer to ADC 1014

and ADC 1224.

6L Agent Contract Number

DLMS Note:

1. Use in GFP-related transactions to identify the 

procurement instrument identifier (PIID) applicable to 

the contract authorizing the contractor to have custody of 

GFP. Use the legacy procurement instrument 

identification number (PIIN) pending transition to the 

PIID.

2. If GFP is authorized under a PIID call/order number 

(F in 9th position), provide the PIID call/order number in 

the PIID field.

3. Required for Air Force GFP accountability to identify 

the CICP’s contract number.

4. Authorized DLMS enhancement; see introductory 

DLMS note 5e on IC cover page. Refer to ADC 1224.

DO Delivery Order Number

DLMS Note: 

1. Use in conjunction with the PIIN (Code 6L) for GFPrelated transactions to identify the legacy four position 

call/order number associated with the PIIN applicable to 

the contract authorizing the contractor to have custody of 

GFP.

2. Do not use for the PIID call/order number. The PIID 

call/order number is mapped to Code 6L.

3. Authorized DLMS enhancement; see introductory 

DLMS note 4e. on IC cover page. Refer to ADC 1224.

Supports GFP

accountability 

requirement for 

identification of 

the authorizing 

PIID.

Clarifies use of 

existing data field 

for the PIID. The 

inclusion of two 

separate data 

fields will allow 

for identification 

of two distinct 

PIIDs: Code CT 

for the PIID 

supporting the 

ship-to contractor 

and the new Code 

6L added for the 

CICP contract. 

Pending transition 

to PIID, allows 

identification of 

the PIIN and 

legacy call/order 

number.

6. 2/N101/50 Add new Code LG and OW and associated notes. 

LG Location of Goods

DLMS Note:

Supports required 

functionality.
Enclosure 1, Addendum to ADC 1224A

Page 11

# Location Revisions to DLMS 867I

Issue

Reason

1. Use to identify the physical location of GFP while in 

CICP custody. The location may be the CICP, the 

CICP’s warehouse or subcontractor. This location must 

be identified by DoDAAC. 

2. Must use for Air Force GFP accountability. Refer to 

ADC 1224.

OW Owner of Property or Unit

DLMS Note:

For Air Force GFP accountability, use to identify the Air 

Force program manager in the accountable property 

system of record (APSR). Must identify the program 

manager by RIC. If the program manager DoDAAC does 

not have an assigned RIC, use the generic Air Force GFP 

APSR RIC with 2/N106=TO and use a second iteration of 

the N1 loop (repeating Code OW without 2/N106=TO) to 

provide the program manager DoDAAC. Refer to ADC 

1224.

Documenting way 

ahead should there 

be insufficient 

RICs for GFP-A 

use in the future.

7 2/N103/50 Revises DLMS notes for existing Code 10. 

10 Department of Defense Activity Address Code 

(DODAAC)

DLMS Note:

DLMS Note:

1. DLMS enhancement; see introductory DLMS note 5a.

2. Authorized DLMS enhancement for Inter-Service 

Ammunition use with N101 code CN to identify

consignee DODAAC (DIC BG1/BG2 rp 66-71). See 

introductory DLMS note 5f. (Refer to ADC 261 and

ADC 445.)

3. Authorized for use by Air Force CICP to identify other 

organizations associated with the transaction by 

DODAAC.

Supports GFP 

accountability 

transactions 

between the CICP 

and the program 

manager using 

DPAS. 

8 2/N106/50 Remove Federal Note and revise segment element N106 

Use attribute from “must use” to “use”: 

Supports GFP 

accountability 

transactions 

between the CICP 

and the program 

manager using 

DPAS. 

9. 2/LQ01/270 Revise DLMS Notes for existing Codes 88, 90, 91, and 92 

and add new code 39,

39 Transportation Mode or Method Code

DLMS Note: 

1. Use as needed to identify the mode of shipment. DLMS 

users see the Transportation Mode of Shipment 

Conversion Table for available codes.

2. Authorized DLMS enhancement; see introductory 

DLMS note 5e. on IC cover page

Authorizes use of 

DLMS 

enhancement data 

content as needed 

without further 

coordination at the 

DOD level.

The Air Force 

GFP-A Capability 

Initiative has 
Enclosure 1, Addendum to ADC 1224A

Page 12

# Location Revisions to DLMS 867I

Issue

Reason

88 Disposal Authority Code

DLMS Note:

1. Use only for DRMO disposal issue transactions to 

identify that items being transferred to disposal are 

authorized for transfer by the proper authority.

2. Authorized DLMS enhancement; see introductory 

DLMS note 5a 5e. on IC cover page

90 Precious Metals Indicator Code

DLMS Note:

1. Use only for DRMO disposal issue transactions to 

identify the precious metals content of materiel being 

transferred to disposal.

2. Authorized DLMS enhancement; see introductory 

DLMS note 5a 5e. on IC cover page

91 Automated Data Processing Equipment 

Identification Code

DLMS Note:

1. Use only for DRMO disposal issue transactions to 

identify ADP equipment that is being transferred to 

disposal.

2. Authorized DLMS enhancement; see introductory 

DLMS note 5a 5e. on IC cover page.

92 Reason for Disposal Code

DLMS Note:

1. Use only for DRMO disposal issue transactions to 

identify the reason that an item is being transferred to 

disposal.

2. Authorized DLMS enhancement; see introductory 

DLMS note 5a 5e. on IC cover page.

identified a 

requirement for 

the disposal 

authority code and 

the reason for 

disposal code. 

The additional 

disposal-related 

data elements are 

added 

administratively 

for uniform 

harmonization 

between the 

materiel release 

confirmation and 

the issue 

transaction. 

Table E – 945A

#

Location Revisions to DLMS 945A

Materiel Release Advice

(Changes applicable to Version 4010 and 4030)

Staffing Note: The Air Force must use Version 4030 since the 

long term goal is to support IUID.

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1224 to the list of applicable DLMS changes included

in the DLMS IC introductory notes:

- ADC 1224, Requirements for Air Force Government 

Furnished Property (GFP) Accountability including 

Identification of the Contractor Inventory Control Point 

(CICP), the Physical Location of Property, the Authorizing 

Procurement Instrument Identifier (PIID), Disposal 

Identifies DLMS 

changes included in 

the IC.
Enclosure 1, Addendum to ADC 1224A

Page 13

#

Location Revisions to DLMS 945A

Materiel Release Advice

(Changes applicable to Version 4010 and 4030)

Staffing Note: The Air Force must use Version 4030 since the 

long term goal is to support IUID.

Reason

Information in the Issue Transaction, and Enhanced Data 

Content in Inventory-Related Transactions

2. 1/N101/0400 Revise DLMS note for existing Code SB.

SB Storage Area

DLMS Note:

1. Use to identify the activity originating the transaction set. 

2. For Air Force GFP accountability, use to identify the CICP 

as the responsible custodial activity. Refer to ADC 1224.

Use of the CICP RIC 

as the transaction 

originator maintains 

legacy compatibility. 

3. 2/N901/0400 Add new Codes 6L and DO and associated DLMS Notes:

6L Agent Contract Number

DLMS Note:

1. Use in GFP-related transactions to identify the procurement 

instrument identifier (PIID) applicable to the contract 

authorizing the contractor to have custody of GFP. Use the 

legacy procurement instrument identification number (PIIN) 

pending transition to the PIID.

2. If GFP is authorized under a PIID call/order number (F in 

9th position), provide the PIID call/order number in the PIID 

field.

3. Required for Air Force GFP accountability to identify the 

CICP’s contract number.

4. Authorized DLMS enhancement; see introductory DLMS 

note 4e. on IC cover page. Refer to ADC 1224.

DO Delivery Order Number

DLMS Note: 

1. Use in conjunction with the PIIN (Code 6L) for GFPrelated transactions to identify the legacy four position 

call/order number associated with the PIIN applicable to the 

contract authorizing the contractor to have custody of GFP.

2. Do not use for the PIID call/order number. The PIID 

call/order number is mapped to Code 6L.

3. Authorized DLMS enhancement; see introductory DLMS 

note 4e. on IC cover page. Refer to ADC 1224.

Supports GFP

accountability 

requirement for 

identification of the 

authorizing PIID.

Pending transition to 

PIID, allows 

identification of the 

PIIN and legacy 

call/order number.

4. 2/N901/0400 Revise DLMS note for existing Code CT:

CT Contract Number

DLMS Note:

Use to identify the procurement instrument identifier (PIID) on 

shipments of GFP to the a contractor. When GFP is authorized 

under a PIID call/order number (F in 9th position), provide the 

value in the PIID field. This is the PIID authorizing shipment 

of GFP to the contractor perpetuated from the release order 

(e.g., the PIID under which the property was requisitioned).

Administrative update 

for clarification.
Enclosure 1, Addendum to ADC 1224A

Page 14

#

Location Revisions to DLMS 945A

Materiel Release Advice

(Changes applicable to Version 4010 and 4030)

Staffing Note: The Air Force must use Version 4030 since the 

long term goal is to support IUID.

Reason

5. 2/N101/ 0800 Revise DLMS note for existing Code LG and add new code 

OW:

LG Location of Goods

DLMS Note:

1. Use for LRO advice to identify the alternative supply source 

when different from the originator of the transaction.

2. Use to identify the physical location of GFP while in CICP 

custody. The location may be the CICP, the CICP’s 

warehouse or subcontractor. This location must be identified 

by DoDAAC. Must use for Air Force GFP accountability. 

Refer to ADC 1224.

OW Owner of Property or Unit

DLMS Note:

1. Use to identify the property owner to receive this transaction 

when not otherwise identified.

2. For Air Force GFP accountability, use to identify the Air 

Force program manager in the accountable property system of 

record (APSR). Must identify the program manager by RIC. 

If the program manager DoDAAC does not have an assigned 

RIC, use the generic Air Force GFP APSR RIC with 

2/N106=TO and use a second iteration of the N1 loop 

(repeating Code OW without 2/N106=TO) to provide the 

program manager DoDAAC. Refer to ADC 1224.

Physical location of 

property provides 

added visibility to the 

program manager.

Identifies the 

Government program 

manager that owns the 

property.

6. 2/N103/0800 Add new DLMS Note 2 for existing Code 10. 

10 Department of Defense Activity Address Code 

(DODAAC)

DLMS Note:

1. DLMS enhancement; see introductory DLMS note 4a.

2. Authorized for use by Air Force CICP to identify other 

organizations associated with the transaction by DODAAC.

Supports GFP 

accountability 

transactions between 

the CICP and the 

program manager 

using DPAS.
Enclosure 1, Addendum to ADC 1224A

Page 15

Table F – 947I

# Location Revisions to DLMS 947I

Inventory Adjustment

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1224 to the list of applicable DLMS changes 

included in the DLMS IC introductory notes:

- ADC 1224, Requirements for Air Force Government 

Furnished Property (GFP) Accountability including 

Identification of the Contractor Inventory Control Point 

(CICP), the Physical Location of Property, the Authorizing 

Procurement Instrument Identifier (PIID), Disposal 

Information in the Issue Transaction, and Enhanced Data 

Content in Inventory-Related Transactions

Identifies DLMS 

changes included in the 

IC.

2. 1/N101/0400 Revise DLMS notes for existing Code SB:

SB Storage Area

DLMS Note:

1. Use to identify the depot or storage activity.

2. For Air Force GFP accountability, use to identify the CICP 

as the responsible custodial activity. Refer to ADC 1224.

Supports GFP

accountability 

transactions between the 

CICP and the program 

manager using DPAS. 

3. 2/N901/0400 Add new Codes 6L, 43, and DO with associated DLMS Notes:

6L Agent Contract Number

DLMS Note:

1. Use in GFP-related transactions to identify the 

procurement instrument identifier (PIID) applicable to the 

contract authorizing the contractor to have custody of GFP.

Use the legacy procurement instrument identification number 

(PIIN) pending transition to the PIID. 

2. If GFP is authorized under a PIID call/order number (F in 

9th position), provide the PIID call/order number in the PIID 

field. 

3. Required for Air Force GFP accountability to identify the 

CICP’s contract number.

4. Authorized DLMS enhancement; see introductory DLMS 

note 4.e. on the IC cover page. Refer to ADC 1224.

43 Supporting Document Number

1. For Air Force GFP accountability, the CICP must use to 

perpetuate the document number assigned by the Air Force 

program manager in the Physical Inventory Request. 

2. DLMS enhancement; see introductory DLMS note 4e. on 

the IC cover page. Refer to ADC 1224.

DO Delivery Order Number

DLMS Note: 

1. Use in conjunction with the PIIN (Code 6L) for GFPrelated transactions to identify the legacy four position 

call/order number associated with the PIIN applicable to the 

contract authorizing the contractor to have custody of GFP.

2. Do not use for the PIID call/order number. The PIID 

call/order number is mapped to Code 6L.

Supports GFP

accountability 

requirement for 

identification of the 

authorizing PIID. 

Pending transition to 

PIID, allows 

identification of the 

PIIN and legacy 

call/order number.
Enclosure 1, Addendum to ADC 1224A

Page 16

# Location Revisions to DLMS 947I

Inventory Adjustment

Reason

3. Authorized DLMS enhancement; see introductory DLMS 

note 4e. on IC cover page. Refer to ADC 1224.

4. 2/N101/1100 Add new Code LG and OW and associated DLMS notes.

LG Location of Goods

DLMS Note:

1. Use in logistics transfer inventory adjustments to identify the 

materiel storage location.

2. Use to identify the physical location of GFP while in CICP 

custody. The location may be the CICP, the CICP’s 

warehouse or subcontractor. This location must be identified 

by DoDAAC. Must use for Air Force GFP accountability. 

Refer to ADC 1224.

OW Owner of Property or Unit

DLMS Note:

1. Use to identify the property owner to receive this 

transaction when not otherwise identified.

2. For Air Force GFP accountability, use to identify the Air 

Force program manager in the accountable property system 

of record (APSR). Must identify the program manager by 

RIC. If the program manager DoDAAC does not have an 

assigned RIC, use the generic Air Force GFP APSR RIC with 

2/N106=TO and use a second iteration of the N1 loop 

(repeating Code OW without 2/N106=TO) to provide the 

program manager DoDAAC. Refer to ADC 1224.

Supports GFP

accountability 

transactions between the 

CICP and the program 

manager using DPAS. 

5. 2/N103/1100 Add new DLMS Note 2 for existing Code 10. 

10 Department of Defense Activity Address Code 

(DODAAC)

DLMS Note:

1. DLMS enhancement; see introductory DLMS note 4a.

2. Authorized for use by Air Force CICP to identify other 

organizations associated with the transaction by DODAAC.

Supports GFP 

accountability 

transactions between 

the CICP and the 

program manager 

using DPAS.
Enclosure 2, Addendum to ADC 1224A

Page 1

Enclosure 2 GFP-A End of Day / Month Transaction Flow Diagram
Enclosure 2, Addendum to ADC 1224A

Page 2

Enclosure 2 GFP-A End of Day / Month Transaction Narrative

Activity Description

1 Report Reconciliation Asset 

Information

Contractor Inventory Control Report (CICP) reports End of Day (EOD) transaction count 

information via Defense Logistics Managements Standards (DLMS) 846P EOD Transaction Count

and inventory balances via DLMS 846R Location Reconciliation Request transaction to Air Force 

Government Furnished Property (GFP) Accountable Property System of Record (APSR) via 

DAAS. 

2 Route GFP transactions and balances DAAS receives DLMS 846P EOD transaction count and DLMS 846R Location Reconciliation 

transaction inventory balances from contractor and routes it to Air Force GFP APSR.

3 Compare Air Force GFP and 

contractor asset management 

information counts and inventory 

balances

Air Force GFP APSR compares GFP information with contractor asset management information 

provided via DLMS 846P and DLMS 846R to determine if there is a mismatch between the two. 

The Program Manager (via the Air Force APSR) will request transaction history from the CICP via 

a DLMS 846P Inventory History Transaction when mismatches are identified to ensure the Air 

Force APSR received all transactions. If issues still cannot be resolved, mismatches will be 

reported to the CICP directly and to the Air Force Program Manager via the APSR Daily Task List 

for resolution.
Enclosure 2, Addendum to ADC 1224A

Page 3

Enclosure 2 GFP-A Issue or Disposal Transaction Flow Diagram
Enclosure 2, Addendum to ADC 1224A

Page 4

Enclosure 2 GFP-A Issue or Disposal Transaction Narrative

Activity Description

1 Update asset management 

position to reflect property 

issuance

Contractor Inventory Control Point (CICP) receives request to issue item on 

site or is given permission to dispose of an item on site. Contractor processes 

an issue/disposal on location and enters issue/disposal information in their IT 

system. Contractor will provide asset management information Defense 

Logistics Management Standard (DLMS) 867I, including DoDAAC, through 

DAAS to Air Force Government Furnished Property (GFP) Accountable 

Property System of Record (APSR). 

2 Route GFP asset issuance 

information

DAAS receives asset management update DLMS 867I, including DoDAAC, 

from contractor and routes it to Air Force GFP APSR. 

3 Update GFP asset 

management position

Receive issue/disposal information in the form of a DLMS 867I, including 

DoDAAC, from DAAS, record transaction and update the GFP balance. Air 

Force GFP APSR provides Air Force financial statements updated inventory 

balances and valuation.
Enclosure 2, Addendum to ADC 1224A

Page 5

Enclosure 2 GFP-A Materiel Release Confirmation Transaction Flow
Enclosure 2, Addendum to ADC 1224A

Page 6

Enclosure 2 GFP-A Materiel Release Confirmation Transaction Narrative

Activity Description

1

Update asset management 

position reflect property 

shipment.

Contractor Inventory Control Point (CICP) ships item to customer or sends asset to disposal. 

Contractor processes the shipment and enters shipment information in their IT system. Property 

is placed in in-transit status. Contractor will provide asset management information Defense 

Logistics Management Standard (DLMS) 945A, including Air Force CICP Government 

Furnished Property (GFP) PIID and DoDAAC, through DAAS to Air Force Government 

Furnished Property (GFP) Accountable Property System of Record (APSR).

2

Route GFP asset shipment 

information

DAAS receives asset management update DLMS 945A, including Air Force CICP Government 

Furnished Property (GFP) PIID and DoDAAC from contractor and routes it to Air Force GFP

APSR.

3

Update GFP asset management 

position

Receive issue information in the form of a DLMS 945A, including Air Force CICP Government 

Furnished Property (GFP) PIID and DoDAAC from DAAS, record transaction and update the 

GFP balance to indicate the property is in-transit. Air Force GFP APSR provides Air Force 

financial statements updated inventory balances and valuation.
Enclosure 2, Addendum to ADC 1224A

Page 7

Enclosure 2 GFP-A Physical Inventory Transaction Flow
Enclosure 2, Addendum to ADC 1224A

Page 8

Enclosure 2 GFP-A Physical Inventory Transaction Narrative

Activity Description

1 Direct Physical 

Inventory

Defense Logistics Management Standard (DLMS) 846P Physical Inventory Request transaction is sent from Air 

Force Government Furnished Property (GFP) Accountable Property System of Record (APSR) to DAAS to route 

to Contractor Inventory Control Point (CICP) to direct a physical inventory be performed. DLMS 846P contains 

Air Force CICP GFP PIID and Department of Defense Activity Code (DoDAAC)

2 Route Request to 

Conduct Physical 

Inventory

DAAS receives physical inventory request DLMS 846P including Air Force CICP GFP PIID and DoDAAC from 

Air Force GFP APSR and routes it to CICP. 

3 Conduct Physical 

Inventory

Contractor receives DLMS 846P from DAAS. Contractor goes to location and conducts physical inventory. Count 

floor to book and book to floor for existence and completeness. Contractor records the inventory results in 

contractor inventory system including Date of Last Inventory (DOLI). 

4 Update Date of Last 

Inventory and any 

inventory change

Report DOLI and any required adjustments using the DLMS 947I transaction including Document Numbers from 

the original request, PIID and DoDAAC to Air Force GFP APSR via DAAS. 

When the physical inventory response does not include asset balances (zero balance), the Air Force CICP will 

transmit a DLMS 846P Physical Inventory Request with the appropriate physical inventory transaction 

Management Code R, S, or Y as applicable. 

5 Route Date of Last 

GFP Inventory 

Position

DAAS receives asset management update DLMS 947I or DLMS 846P including the Air Force CICP GFP PIID 

and DoDAAC from contractor and routes it to Air Force GFP APSR.

6 Update GFP

Inventory Position

Receive DLMS 947I or DLMS 846P from DAAS, record transaction and update Date of Last Inventory (DOLI).

Notify the PM the physical inventory has been performed via the Air Force GFP APSR Daily Task List. Report 

inventory balances and valuation to Air Force Financial Statements.
Enclosure 2, Addendum to ADC 1224A

Page 9

Enclosure 2 GFP-A Inventory Adjustment Transaction Flow
Enclosure 2, Addendum to ADC 1224A

Page 10

Enclosure 2 GFP-A Inventory Adjustment Transaction Narrative

Activity Description

1

Update asset management 

position

Contractor performs an inventory adjustment. This could be the result of a condition code 

change, physical inventory, logistics reassignment, etc. Contractor transmits inventory 

adjustment Defense Logistics Management Standard (DLMS) 947I, including DoDAAC, 

through DAAS to Air Force Government Furnished Property (GFP) Accountable Property 

System of Record (APSR). 

2

Route GFP asset position 

information

DAAS receives DLMS 947I, including DoDAAC, and routes it to the Air Force GFP APSR.

3

Update GFP asset management 

position

Receive inventory adjustment DLMS 947I that includes DoDAAC from DAAS, record 

transaction and update the GFP balance to reflect the inventory adjustment. Air Force GFP

APSR provides Air Force financial statements updated inventory balances and valuation.