1 of 6

ADC 481

Att

ATTACHMENT TO ADC 481

Revise DLMS 846I Asset Status Report to Provide for a Transaction Count to Support 

Asset Status Report Transaction Reconciliation under DLA-Navy BRAC SS&D IMSP 

1. ORIGINATOR:

a. Service/Agency: Defense Logistics Agency

b. Originator: DLA J-331, 703-325-1924 (DSN 427)

2. FUNCTIONAL AREA: Primary: Supply/Logistics.

3. REFERENCE: DLMSO memorandum, June 24, 2010, subject: ADC 374, Revise DLMS 846I, 

Asset Status Report in Support of Navy BRAC SS&D/IMSP (Supply)

4. APPROVED CHANGE: 

a. Description of Change: In support of Base Realignment and Closure (BRAC) Retail Supply, 

Storage And Distribution (SS&D)/Inventory Management and Stock Positioning (IMSP), the DLMS 

846I Asset Status Report requires updates to allow the receiving system to reconcile whether all 

files/balances sent by the inventory manager have been received.

b. Background: As a result of the 2005 BRAC decision, retail supply, storage and distribution 

functions, and associated infrastructure supporting the Navy industrial/maintenance sites will transfer 

to DLA. The Navy sites consist of two Navy Shipyards (NSY) and three Fleet Readiness Centers 

(FRC). The intent of the directive is to significantly improve combat effectiveness while reducing 

costs by developing a world-class, cost-effective supply chain focused on readiness; taking every 

opportunity to eliminate waste, reduce touches, reduce cost, and improve readiness. DLA has the 

requirement to provide on-hand asset balances to both NSY and FRC systems, and the capability to 

provide these balances for both DLA-owned and local Navy-owned assets for informational purposes. 

EBS also requires Navy-owned on-hand asset balances at the NSY sites to facilitate the agreed upon 

attrition process. While the original intent was for DSS to provide a single looped 846I file of asset 

balances, both transaction and system limitations prevent this capability. These limitations result in the 

need for a means to reconcile 846I files to determine whether all files/balances have been received. 

c. Detailed Procedure:

NOTE: Refer to ADC 374 for full detailed procedures associated with use of 846I Asset Status 

transaction (MILSTRAP legacy DZA functionality) to provide asset balances under Navy BRAC SS&D 

IMSP. 

NOTE: As documented in ADC 374, SS&D IMSP use of the 846I Asset Status Report does not replace 

the DOD Physical Inventory Control Program (PICP) End of Day process1 whereby the storage activity 

submits the daily closing on-hand balance to each affected owner/manager using DLMS 846R 

(MILSTRAP legacy DZH) Location Reconciliation Request Transaction. The PICP end of day process 

would not provide Navy on-hand balance information for DLA owned assets. The PICP program does 

 1 Refer to DOD 4000.25-M, DLMS, Volume 2, Chapter 6, or DOD 4000.25-2-M, MILSTRAP, Chapter 7 for 

Physical Inventory Control procedures. Both DOD manuals are available at: 

http://www.dla.mil/j-6/dlmso/eLibrary/Manuals/dlmso_pubs.asp. 
2 of 6

ADC 481

Att

provide the on-hand balance information for Navy owned assets at DLA storage activities. 

1) DSS will prepare at least one DLMS 846I per owner Routing Identifier Code (RIC);

and provide up to 500 asset balances per DLMS 846I transaction set file (i.e., up to 500 LOOP IDLIN iterations per DLMS 846I transaction set). DSS will generate the DLMS 846I Asset Status 

transaction set multiple times per day in support of NSY sites; DSS will generate DLMS 846I once 

per day is support of FRCs.

2) In order to advise the receiving system of the number of asset balances and 846I 

transactions provided to a given owner RIC, two distinct approaches were discussed among the 

DLMS office, DLA IMSP lead, DSS, and Navy as follows:

a) LONG-TERM APPROACH: A new beginning segment Report Type Code 

(BIA02) be added to the 846I to identify a separate 846I transaction purpose, to provide the receiver 

with the number of 846I files sent per owner RIC, as well as the total number of LOOP ID-LIN 

iterations sent per owner RIC. 

NOTE: This approach is consistent with the approach used with 846R “Location Reconciliation 

Notification Transaction” (beginning segment (BIA02) Report Type Code X4 (MILSTRAP legacy DZN 

functionality)), which is used to convey the number (count) of Location Reconciliation Request transactions 

being forwarded to the receiving system.

b) INTERIM APPROACH: The DLA IMSP lead recommended a two-pronged 

approach with interim and long-term solutions. Under the interim approach for the near-term, the last

846I transaction for each owner RIC would contain the number of 846I transactions sent per owner 

RIC, as well as the total number of LOOP ID-LIN iterations sent per owner RIC. The interim

approach will be used until the long-term approach can be implemented.

NOTE FOR DLA AND NAVY: Use of interim and long-term approaches requires programming 

one method, then in the near future reprogramming for the more standardized approach for 

providing transaction counts. This programming change would move the detail segments related to

the file/transaction counts from the last 846I transaction to a separate DLMS 846I transaction with a 

distinct beginning segment Report Type Code for the count transaction.

d. DLMS 846I, Asset Status Report, Change Table [NOTE: text in gray highlight in 

846I Change Table is specific to the interim approach; DLA must propose update to DLMS 

846I to remove the text specific to the interim approach, once long-term approach is 

implemented]:

Item 

#

Location DLMS 846I Asset Status Report

Revision based on Approach One

Reason

1. DLMS 

introductory 

note

Add ADC 481 to DLMS introductory note 6:

- ADC 481, Revise DLMS 846I Asset Status Report to Provide 

for a Transaction Count to Support Asset Status Transaction 

Reconciliation under DLA-Navy BRAC SS&D IMSP (Supply)

Identifies PDCs/ADCs in DS.
3 of 6

ADC 481

Att

Item 

#

Location DLMS 846I Asset Status Report

Revision based on Approach One

Reason

2. 1/BIA02/

020

Add new beginning segment Report Type Code ‘QT’ with DLMS 

note:

QT Quality Summary

DLMS note: Use to identify an Asset Status Count Transaction. 

Authorized DLMS enhancement for use only with DLA Industrial 

Activity Support Agreement with Navy. Storage activity uses to 

provide the recipient a total file count which is cumulative for all 

of the 846I Asset Status Report files sent to the recipient per 

owner RIC; as well as the total 846I Asset Status Report 

Transaction count (LIN LOOPS) sent to the recipient per owner 

RIC. A single 846I transaction may have up to 500 LIN LOOPs. 

The Asset Status Count Transaction has no corresponding 

MILSTRAP transaction functionality. Refer to ADC 481.

Supports DLA-Navy BRAC 

IMSP requirement.

3. 2/LIN02/010 Add new DLMS data element Note 2 and renumber existing 2 as 

3:

DLMS Note: 1. Use only one of A1, A2, A4, FB, FS, MG, SW, 

YP or ZR to identify the item reported. Must use National Stock 

Number (NSN) when known except when appropriate brand 

name subsistence items are identified by the Subsistence 

Identification Number or when industrial activity materiel is 

identified by Local Stock Number or Material Control Tracking 

(MCT) Tag Number.

2. For 1/BIA02/020 code QT (Asset Status Count Transaction)

only use LIN02 code DS. Refer to ADC 481.

3. For DLMS use, only the following codes are authorized.

Supports DLA-Navy BRAC 

IMSP requirement

4. 2/LIN02/010 Add qualifier DS with DLMS Note:

DS Group ID

DLMS Note: Use with 1/BIA02/20 code QT (Asset Status Count 

Transaction) to comply with ANSI syntax requirement. Indicate 

ZZ in LIN03. Refer to ADC 481.

Supports DLA-Navy BRAC 

IMSP requirement

5. 2/QTY/

320

Add segment level DLMS note 2.

DLMS note 2: For DLA Industrial Support Agreements with 

Navy, use 2 iterations of the QTY LOOP with Asset Status Report 

Count Transactions (BIA02 code QT) to identify 846I file count 

and transaction (Loop ID LIN iterations) count. Also used 

during interim approach to provide Asset Status Report 

file/transaction counts under DLA Industrial Support Agreement 

with Navy. Refer to ADC 481.

Supports DLA-Navy BRAC 

IMSP requirement.
4 of 6

ADC 481

Att

Item 

#

Location DLMS 846I Asset Status Report

Revision based on Approach One

Reason

6. 2/QTY01/320 Add qualifier ‘46’ with DLMS note

46 Total Transactions

DLMS Note: 

1. Use with Asset Status Count Transaction (BIA02 QT) to 

identify the total number of 846I Asset Status Report files per 

owner RIC sent to the recipient. Authorized DLMS enhancement 

for use only with DLA Industrial Activity Support Agreement 

with Navy. Refer to ADC 481.

2. Also used during interim approach to provide Asset Status 

Report file/transaction counts under DLA Industrial Support 

Agreement with Navy. During interim approach, use with Asset 

Status Report (BIA02 TJ) to identify the total number of 846I 

Asset Status Report files per owner RIC sent to the recipient. 

Refer to ADC 481.

Supports DLA-Navy BRAC 

IMSP requirement.

7. 2/QTY01/320 Add qualifier ‘TO’ with DLMS note

TO Total

DLMS Note: 

1. Use with Asset Status Count Transaction (BIA02 QT) to 

identify the total number of 846I LIN LOOPs, which is 

cumulative for all of the 846I Asset Status Report files per owner 

RIC, sent to the recipient. Refer to ADC 481.

2. Also used during interim approach to provide Asset Status 

Report file/transaction counts under DLA Industrial Support 

Agreement with Navy. During interim approach, use with Asset 

Status Report (BIA02 TJ) to identify the total number of 846I 

LIN LOOPs, which is cumulative for all of the 846I Asset Status 

Report files per owner RIC, sent to the recipient. Refer to ADC 

481.

Supports DLA-Navy BRAC 

IMSP requirement.

5. REASON FOR CHANGE: As a result of BRAC 2005 SS&D, EBS will be purchasing, storing 

and issuing all consumable items in support of the Navy Industrial sites. Without a way to determine 

when all asset balances have been received, erroneous planning and fulfillment decisions may be 

made which would result in over procurement and excess inventory.

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Enterprise Business System (EBS), Material Access Technology (MAT), 

Material Resource Planning (MRP) II and DLA’s Distribution Standard System (DSS), will be able 

to comply with DLMS standards for the BRAC IMSP Spiral 2 process

b. Disadvantages: None identified.
5 of 6

ADC 481

Att

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: DLA and Navy implementation 

of the interim approach was January 2012. DLA Supply PRC representatives must actively monitor 

for implementation of the long term approach, and advise DLA Logistics Management Standards

office of the implementation date when known, and provide necessary updates to the DLMS 846I.

8. IMPACT:

a. Publications:

1) Requires update to DLMS Supplement 846I

2) Requires update to DOD 4000.25-M, DLMS, to add procedures for the BRAC SS&D/ 

IMSP process described by this and other BRAC related ADCs . The DLA J33 Supply PRC 

representatives are responsible for coordination with the appropriate DLA, Navy, and Marine 

Corps offices for development and submission of the DLMS procedures associated with BRAC, 

for the DLMS manual. With the recent implementation of the BRAC associated changes, it is 

required that the DLMS procedural guidance be provided as soon as possible, but no later than 

May 17, 2012. Request DLA J33 provide the Navy BRAC IMSP SS&D and Marine Corps BRAC 

Storage and Distribution Interface (SDI) procedures as a separate chapter for the DLMS manual, 

Volume 2, Supply, with cross-references identified for placement within the related functional 

area guidance. The requirement to provide the procedures no later than May 17, 2012, was previously 

documented in ADC 401.

b. Automated Information Systems (AIS): This change impacts only DLA Enterprise 

Business System (EBS), DLA Distribution Standard System (DSS), Navy Material Access 

Technology (MAT), and Navy Material Resource Planning (MRP) II systems.

c. DLA Transaction Services Mapping. Update DLA Transaction Services maps to allow new 

data to pass any applicable edits.

d. New DLMS Data:

1) New Beginning segment Report Type Code QT for Asset Status Count Transaction

2) Quantity Asset Reports Sent, Quantity field for count of the total number of 846I files 

provided per owner RIC. Used with DLA Industrial Support Agreement with Navy.

3) Quantity Asset Balances Sent, Quantity field for count of the total number of 846I LIN 

Loops provided per owner RIC. Used with DLA Industrial Support Agreement with Navy. 
6 of 6

ADC 481

Att

9. PDC 504 RESPONSES/COMMENTS:

# Organization PDC Response/Comment Disposition

1 DLA Concurs with comment. 

What is trigger and timeframe for 

long-term solution? Is there a suspense 

or projected date for the long term 

solution?

DLA Originator’s Response to DLA comment:

EBS and DSS both have future releases to support 

the FRCs that we could plan to have the long term 

solution ready for (we can validate with DSS if 

they could be ready on this timeline).

The date is somewhat flexible because it depends 

on whether the Puget NSY rolls out in May and the 

FRC testing progress... but it should be somewhere 

between the beginning of May and Jul.

2 Navy Concurs as written and submits no 

additional changes or amendments.

Navy Question: what two shipyards 

are addressed in this change?

DLA Response: 

Norfolk Naval Shipyard (NNSY) and 

Puget Sound Naval Shipyard (PSNS) 

3 DLA Logistics 

Management 

Standards 

office

1. DLA J33 Supply PRC 

representatives must actively monitor 

for implementation of the long term 

approach, and advise DLA Logistics 

Management Standards office of the 

implementation date when known, and 

provide necessary updates to DLMS 

846I.

2. The DLA J33 Supply PRC 

representatives are responsible for 

coordination with the appropriate 

DLA, Navy, and Marine Corps offices 

for development and submission of the 

DLMS procedures associated with 

BRAC, for the DLMS manual.

Submit procedures as soon as possible 

but no later than May 17, 2012.

4 Army Army concurs with the PDC as 

written; there is no requirement for

implementation with Army AIS. 

Noted.

5 Air Force Concurs without Comments. Noted.

6 USTRANSCOM Abstains Noted.