ADC 360 

Attachment Page 1 

ADC 360 

Procedures and Content Requirements for Catalog Data Support 

under Navy and Marine Corps BRAC 

1. ORIGINATOR: Defense Logistics Agency, DLA J-3, 

2. FUNCTIONAL AREA: Primary: Supply/ Logistics.

3. REFERENCES: 

a. Functional Requirements for DLA’s implementation of Navy BRAC Retail Supply, 

Storage, and Distribution (SS&D)/Inventory Management and Stock Positioning (IMSP) Spiral 2 

b. Functional Requirements Pre-Design for DLA’s implementation of Marine Corps BRAC 

Retail Storage and Distribution Interface (SDI). 

c. Approved DLMS Supplement 832N, Catalog Data Support, on the DLMS internet site 

eLibrary under DLMS Supplements to Federal Implementation Conventions - Transaction Sets, 

available at: http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp. 

d. DoD 4100.39-M, Federal Logistics Information System (FLIS) Procedures, available at: 

http://www.dlis.dla.mil/flis_procedures.asp. 

4. REQUESTED CHANGE: This change establishes the DLMS Supply, Storage and Distribution 

(SS&D) catalog data support procedures and transactional interface. This document consolidates the 

Navy and the Marine Corps (MC) BRAC usage which were staffed separately. The same transaction 

will serve both the Navy and MC interfaces, but procedures and data content will differ. Yellow 

highlighting identifies significant variations in procedures and data content from the previous staffing 

of this change. Component responses to staffing are shown at Enclosure 10.

a. Description of Change - Navy: This change establishes a new business process using 

DLMS transactions for communication of catalog data between DLA, the Distribution Depots 

operating under the Distribution Standard System, and Navy industrial activities. This change 

supports Naval Ship Yards (NSY) and Fleet Readiness Centers (FRCs) operating under the Navy-DLA 

BRAC 2005 SS&D concept of operations (CONOPS). The cataloging data support will allow 

information exchanges including: 

(1) Identification of non-National Stock Number (NSN) materiel by a Local Stock 

Number (LSN) so that the LSN may be recognized for requisitioning and distribution processing. 

(2) Communication of FLIS cataloging information to the NSY and FRC sites which 

lack a direct communication link with DLIS. 

(3) Identification of NSN materiel by a LSN so that the LSN may be used for storage 

and distribution of materiel identified at the unit of use (that is, less than the FLIS unit of issue). 

Staffing Notes: 

(a) This ADC incorporates additional requirements for identification for 
ADC 360 

Attachment Page 2 

specific Regional Hazardous Inventory Control System (RHICS) materiel using the RHICS data base 

for establishment of a uniquely formatted LSN. This new requirement will align EBS, Navy, and 

RHICS hazardous material to one specific material number beginning with “LLN” in the 13-digit NSN 

field. This will only be used on hazardous material that does not have an existing NSN in EBS or 

FLIS. 

(b) ADC 381 documents procedures associated with Navy requisitioning at the 

unit of use level. 

(c) ADC 398, Revise DLMS 846A Asset Reclassification, 947I Inventory 

Adjustment, and Associated Procedures to Support Marine Corps BRAC Storage and Distribution 

Interface, for additional clarification on the methodology used for conversion to unit of use. 

(4) Identification of a Service coordinated/approved substitute/interchangeable item as 

a result of DLA or other Service provided supply status to associate the substitute NSN with the 

primary NSN. 

b. Description of Change – Marine Corps: This change establishes the business process 

using the DLMS Catalog Data Support transaction for communication of catalog data between 

Distribution Depots operating under the Distribution Standard System, and the MC Maintenance 

Centers (MCMC). This change supports MCMCs operating under the MC-DLA BRAC 2005 SS&D 

concept of operations (CONOPS). The cataloging data support will allow information exchanges for 

identification of non-NSN materiel by a LSN so that the LSN may be recognized for distribution 

processing. Unlike the Navy implementation, the MC will not exchange catalog data support with the 

DLA EBS. Under the MC implementation, the 846A, Asset Reclassification, will be used to reidentify NSN items as unit of use under a LSN, in lieu of the 832N as used by the Navy. 

Additionally, the catalog data support transaction will be used by the DSS to provide specific FLIS 

updates to the MCMC (rather than EBS providing these updates as under the Navy process). 
ADC 360 

Attachment Page 3 

c. Background: 

(1) BRAC Concept – Navy. 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 Naval Shipyards (NSY) 

and Fleet Readiness Centers (FRCs). 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. In accordance with the signed CONOPS, DLA has agreed to provide SS&D/IMSP support 

to the FRC and NSY sites, including catalog data support. 

(2) BRAC Concept – Marine Corps. As a result of the 2005 BRAC decision, storage 

and distribution functions for Operating Material and Supplies associated infrastructure supporting the 

MCMC sites will transfer to DLA. The Marine Corps sites are Maintenance Center Albany (MCA) and 

Maintenance Center Barstow (MCB). 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. In accordance with the signed CONOPS, DLA has agreed to provide S&D support to the 

MC sites, including catalog data support. 

(3) Policy: On March 11, 2010, the Deputy Assistant Secretary of Defense for Supply 

Chain Integration, DASD(SCI), authorized DLA and Navy to proceed with development of 

procedures, including the cataloging data exchange, supporting requisitioning and materiel storage at 

less than the unit of issue and for requisitioning of non-NSN items using a local stock number for 

identification. Due to the policy implications of this change, the concept was presented to DASD(SCI) 

for approval subsequent to initial staffing. In response, the DASD(SCI) recommended a review of the 

unit of issue for materiel currently issued to the Navy at unit of use to ensure that unit of use is not the 

more accurate unit of issue for these items. Should FLIS cataloging updates result from the review, 

significant savings might be realized. DASD(SCI) also identified a requirement that an NSN must be 

assigned when the items have three or more demands in one year (applicable to Local Stock Numbers 

(LSNs) cataloged for non-NSN part-numbered materiel). Although approving the unit of use concept 

in order to meet the IMSP timeline, DASD(SCI) also requires exploration of an enterprise solution for 

future use. 

d. Detailed Procedures - Navy: 

(1) DLA will prepare and transmit the 832N, Catalog Data Support, and transmit to the 

Navy BRAC sites to provide catalog data (also referred to as the “materiel master”). The catalog data 

will be provided to both the FRCs and NSYs, as applicable. The DLA EBS will provide a copy of the 

832N to DSS when the item is identified as using a LSN. 

(a) The catalog data will be applicable to new item inductions, FLIS change notices 

for DLA items and non-DLA managed items, as well as Navy-assigned LSNs. Since DLA will be 

purchasing, storing, and selling these items to industrial activities, DLA will have this data resident in 

the EBS and will provide visibility to the Navy sites via this 832N transaction. 

(b) EBS will also maintain site-specific materiel master records for Depot Level 

Reparables (DLR), Navy program-managed material and nuclear consumable support materiel (which 

are not requisitioned through DLA). These records will reflect the same user unique data elements as 
ADC 360 

Attachment Page 4 

the consumable material masters, and will be built based on user input. The records may also be built 

based on a ‘copy’ of a requisition, status, or materiel obligation validation (MOV) transactions 

forwarded via the Defense Automatic Addressing System (DAAS) when a record does not exist in 

EBS (e.g. for nuclear materiel requisitioned directly from the source of supply (SoS) or for materiel 

requisitioned prior to Navy BRAC IMSP implementation). In all instances, an 832N will be generated 

as an ‘ADD’ record and sent to the specific NSY or FRC site. 

(2) Both FRC and NSY sites will have the capability to create new material masters or 

update user defined data elements to existing material masters directly into EBS through a user unique 

screen. This application within EBS will prompt users for mandatory fields and user-defined fields for 

new entries, which may be optional depending upon the site (FRC/NSY). This allows different values 

for site-specific data elements. 

(3) There will only be one LSN per CAGE and part number, but that one tab within SAP 

will be site specific to allow for the values of the same data elements to be unique per site. 

(4) When the screen entry is modifying an existing record, the user will be prompted to 

save changes. Upon saving of record, EBS will generate an 832N identified as a ‘CHANGE’ record. 

This record will contain all agreed to data elements to build a record within the NSY application, 

Material Access Technology (MAT), or FRC application, Manufacturing Resource Planning (MRP II). 

If the change is to an existing LSN record, a copy will be furnished to the applicable DSS site. 

(5) Subsequent to an EBS query, EBS will determine if a record exists for the NSN, 

LSN, or CAGE and part number and return the applicable response to the user. 

(a) When a record does exist for the queried materiel, EBS will extend the material 

master to the site and an 832N identified as an ‘ADD’ record containing all agreed to data elements to 

build a record in MAT or MRP II. For LSNs, a copy will also be provided to the applicable DSS site. 

(b) When the query is for an NSN or LSN and it does not exist, the user will be 

prompted to create a new record in EBS. An 832N identified as an ‘ADD’ record will contain all 

agreed to data elements to build a record in MAT or MRP II. For LSNs, a copy will also be furnished 

to the applicable DSS site. 

(c) When a record does not exist for the NSN or Cage/Part Number, EBS 

functionality will query FLIS. 

(d) If the FLIS response is negative, the user will be provided with a reply on the 

screen indicating no record was found. The user may at this point enter a response indicating the need 

to create a LSN. 

(e) The user will be prompted to enter all mandatory data elements to create a 

material master within EBS for a LSN record. Additional unique fields for new entries may be 

optional depending upon the site (FRC/NSY). 

(f) EBS will return an 832N identified as an ‘ADD’ record containing all agreed to 

data elements to build a record in MAT or MRP II. The non-NSN LSN identifier will be assigned by 

EBS. The first 4 positions of this LSN will be the FSC and EBS will assign the last 9 positions of the 

LSN sequentially. 
ADC 360 

Attachment Page 5 

(6) NSY sites will have the capability to create the 832N transactions identified as a 

query to determine if NSN or LSN exist in EBS data base when there is no existing record on the 

internal table within MAT. The same transactions may be used to determine if a LSN or NSN exists 

for a specific CAGE and part number combination within EBS. 

(7) In instances when the query is for a LSN or NSN: 

(a) If a material master is found, EBS will extend material to query site and return 

an 832N identified as an ‘ADD’ record containing all agreed to data elements to build a record in 

MAT. If there is no material master for a LSN, the 832N sent to MAT is identified as ‘no record 

exists,’ and MAT will output transactions for manual review. 

(b) If there is no material master within EBS for the inquired ‘NSN’, EBS will 

inquire FLIS, build a material master and return an 832N identified as an ‘ADD’ record containing all 

agreed to data elements to build a record in MAT. If the inquiry to FLIS is negative, the inbound 

832N will be returned to MAT and identified as ‘no record exists,’ and MAT will output transaction 

for manual review. 

(8) In instances when the query is for a CAGE and part number combination: 

(a) EBS will search existing data base to determine if there is an existing record for 

an NSN or LSN. When there is an existing material master, EBS will return an 832N identified as an 

‘ADD’ record containing all agreed to data elements to build a record in MAT. 

(b) EBS will query FLIS. If the response is negative, the 832N sent to MAT is 

identified as ‘no record exists,’ and MAT will output transactions for manual review. 

(9) In instances when a query is for a hazardous material under Regional Hazardous 

inventory Control System (RHICS) only RHICS cataloged or created LSNs beginning with “LLN” 

will be used. 

(a) EBS will search existing data base to determine if there is an existing record of 

the RHICS material beginning with LLN (first 3 digits). If there is an existing material master EBS 

will return an 832N identified as an “ADD” record containing all agreed to data elements to build a 

record in MAT and pass a copy to DSS. 

(b) If no material master for the RHICS hazardous material is found, the user will 

be prompted for mandatory fields and user defined fields for new entries using the RHICS data base 

elements. The key is that only one LSN representing the RHICS LLN number will be used for like 

material. Thereby, having only one LLN number per hazardous material for all users. When the query 

is for a LSN beginning with LLN, the 832N will be an output transaction to MAT and a copy will be 

furnished to the applicable DSS site. 

(10) Upon data conversion, DLA will build a material master record for all the current 

Navy local stock numbers, including RHICS LLN numbers and non-DLA NSN’s from the FRC and 

NSY systems into EBS. This will provide a base line for the materials currently used at all five sites. 

EBS will query FLIS for all NSN records to ensure all FLIS data elements are updated. An 832N 

record identified as an ‘ADD’ will be returned to the appropriate NSY/FRC site. For LSNs, a copy 

will be sent to the appropriate DSS site. 
ADC 360 

Attachment Page 6 

(11) One functionality to be added in support of 2005 BRAC decision at the NSY and 

FRC sites, is the ability to issue and store material at a quantity and unit of use less than the FLIS unit 

of issue. In these instances, EBS will apply unique logic to create a material master with a LSN. This 

record will reflect all applicable FLIS and user-unique data elements from the original NSN. The 

record will also reflect the NSN and the NSN record will reflect the unit of use LSN. 

(a) EBS will create a record for all NSN items identified with a unit of use upon 

data conversion as a base line. Anytime after conversion when a less than unit of use material number 

is created in EBS the 832N record will NOT be generated to the NSY/FRC sites, but will be forwarded 

to the applicable DSS site. 

(b) The 832N record will reflect the associated NSN and FLIS unit of issue. DSS 

will build an internal table cross referencing the NSN and the associated Local Stock Number (for unit 

of use), FLIS Unit of Issue and the Unit of Use. 

(12) EBS will provide catalog data reflecting substitute reference when the status update 

process from other than a DLA source response reflects a substitute is being supplied. 

(a) When EBS receives a supply status BH indicating DLA will be sent an item 

previously identified as a Navy suitable substitute for a DLA-funded requisition in support of Navy 

BRAC IMSP, the status will prompt EBS to format an 832N identified as a substituted item reflecting 

the prime NSN and reference the substitute NSN when a material master already exist in EBS. 

(b) When a material master for the substitute NSN does not exist in EBS, a record 

will be created. Any user unique data elements will be copied from the prime NSN. An 832N 

identified as substitute record reflecting the Prime NSN and referencing the substitute NSN will be 

forwarded to the applicable site. 

(c) EBS will not maintain a cross reference to other service managed NSNs 

pertaining to substitution. 

(d) An 832N identified for a substitute item reflecting the prime NSN and 

referencing the substitute NSN will be provided for DLA managed items when no stock under the 

prime NSN is available for immediate issue, the advice code does not indicate ‘do not substitute’ and a 

Navy approved substitute item is available for immediate issue. 

(13) The catalog data support transaction flow diagrams are shown at Enclosure 1. 

e. Detailed Procedures – Marine Corps

(1) MCMC systems will prepare and transmit the 832N, Catalog Data Support, to the 

DLA DSS operating the collocated DLA warehouse. The catalog data will be provided to the DLA 

DSS when a Maintenance Center LSN is established. 

(2) The catalog data will be applicable to MCMC-assigned LSNs. Since DLA will be 

storing and distributing these items to the industrial activities (IAs), this data must be resident in the 

DSS. As the MCMCs create LSNs, the MCMC systems will create the 832N transaction and transmit 

this to DSS. DSS will receive this transaction and create the DSS Item Data record containing the 

transmitted item characteristics. 
ADC 360 

Attachment Page 7 

(3) The MCMCs will have the capability to create new LSN material masters or update 

data elements to existing LSN material masters via the 832N transaction. This allows different values 

for site-specific data elements. 

(4) Creation of a LSN. When the MCMC systems identify the need to create a LSN, 

the 832N will be identified as an ‘ADD’ record containing all agreed to data elements to build a LSN 

record in DSS. The non-NSN LSN identified will be assigned by the MCMC systems. The first 4 

positions of the LSN will be the Federal Supply Class (FSC) and the MCMC systems will assign the 

last nine positions using the following construct. Albany uses 01A200001 thru 01A999999 for the 

NIIN portion of their Service-unique LSN. Barstow uses MCB000001 through MCB999999 for the 

NIIN portion of theirs. 

(a) The non-NSN LSN MRP II Assembly numbers are assigned by the MCMC 

systems. A default FSC of MRP2 is assigned with the NIIN portion of the LSN being assigned 

sequentially. Non-NSN LSN MRP II assembly numbers include Marine Corps Control Kits and 

Process Kits. 

1. A Control Kit consists of items going through the same refurbishment 

processes, and will be used at the same stage of the assembly process. The kits routed under the MRP 

number will be identical. This kit is required to be 100% complete when routed to Code B storage. 

Control Kits will be stored and issued as a kit under the MRP Number assigned to the kit. 

2. A Process Kit consists of items going through the same refurbishment 

processes, and will be used at various stages of the assembly process. The kits routed under the MRP 

number may vary from the 'standard' established on the Disassembly Disposition Record (DDR). A 

process kit is not required to be 100% complete when routed to Code B storage. A process kit will not 

to be stored as a kit; each part of the kit will be receipted into stock individually, and will be issued as 

needed to different assembly station picklists. 

(b) Part Numbered Materiel Identified by LSN. The MCMC is also authorized to 

use a LSN for part-numbered items if required for storage and distribution. 

(c) Unit of Use LSN for NSN Materiel. A catalog data support transaction will not 

be established by the MCMC to establish the unit of use LSN. Instead, the MC will send DSS an 

846A, Asset Reclassification, when they want to re-identify NSN material to a unit of use LSN. DSS 

will then establish the DSS Item Data Record using the core FLIS data content and the unit of use 

contained in the 846A. The MC construct will be similar to that used by the Navy for unit of use 

LSNs, but the Marine Corps will substitute an "A" (for Albany) or "B" (for Barstow), for example: 

5975-A0-000-1234 (rather than the “U” used by the Navy). Unlike the Navy, where there may only 

be one unit of use LSN per NSN, the MCMCs may assign a different unit of use for Barstow and 

Albany. The Marine Corps will pass the unit of use LSN in the 940R Materiel Release Order when 

they wish to issue at unit-of-use. Since DLA will not be performing supply functions for the MC their 

requisitioning process will remain the same as today, that is, materiel will be requisitioned under the 

NSN using the standard unit of issue. The MCMC will not store and issue an item of supply under 

both the NSN and the Unit of Use LSN. Accordingly, when DSS receives MCMC materiel shipped 

under the NSN, and a DSS Item Data Record exists for the associated Unit of Use LSN, DSS will 
ADC 360 

Attachment Page 8 

convert the NSN quantity to LSN quantity upon receipt.1

(d) Unit of Use LSN for non-NSN Materiel. The initial LSN for some new 

procurement non-NSN materiel will be created based upon the purchase unit. Subsequent to receipt, it 

may be necessary for the MCMC to re-identify these LSNs assigned for non-NSN materiel to a unit of 

use LSN. It is currently planned that this will be accomplished using the 846A, Asset Reclassification. 

DSS will establish the Item Data Record for these based upon the 846A rather than a new catalog data 

support action. In addition, this ADC will allow the 832N to provide cataloging support for 

establishment of a new unit of use LSN cross-referenced to a previously established LSN, should that 

functionally be required in the future. 

(5) Catalog Data Changes. When the MCMC systems identify the need to modify a 

LSN, the 832N will be identified as a ‘CHANGE’ record containing any of the agreed to data elements 

to modify a LSN record in DSS. 

(6) Catalog Data Deletions. When the MCMC systems identify the need to delete a 

LSN, the 832N will be identified as a ‘DELETE’ record. 

(7) FLIS Replacement NIIN changes: For a FLIS NSN change, DSS will change the 

NSN (and associated unit of use LSN as necessary) immediately. DSS will then send an 832N 

transaction to the MC Bridge for FLIS changes related to an NSN that is replaced/superseded or 

discontinued (Catalog Transaction Purpose Codes: RN, NSN Replaced; RS, Use NSN When 

Exhausted; SN, NSN Substituted; NS, NSN Superseded; DN, NSN Discontinued; no Replacement). 

The Marine Corps Bridge will interpret change until the Industrial Logistics Support Management 

Information System. (ILSMIS)/MRP II applications are updated to use the new NSN. 

(8) Upon data conversion, DSS will build a material master record for all the current 

MCMC local stock numbers and non-DLA NSNs from the MCMC sites. This will provide a base line 

for the materials currently used at MCMCs. 

(9) Catalog data support transaction flow diagrams for the MC are shown at 

Enclosure 2. 

f. Data Content. The table below identifies the data content to be captured in the 832N, 

Catalog Data Support. This is an updated copy of the table used in PDC 360A annotated to identify 

applicability for MCMC and Navy IA support. Refer to the DLMS Supplement 832N for specific 

mapping and syntax requirements. 

 

1

 Refer to PDC 419 Revisions to DLMS Supplement (DS) 527R, Receipt, and Associated Procedures Supporting Marine 

Corps BRAC SS&D, for additional procedures associated with this process. 
ADC 360 

Attachment Page 9 

DS 832N 

Data Content 

Usage Notes/ 

Cross-Reference to FLIS Data Record Number (DRN)2/ 

Definition for Unique or Non-Standard Data Elements 

Field 

Length 

Applicability:

MCMC (M) 

Navy IA (N) 

1. Catalog Purpose Code Identifies the purpose of the catalog as Catalog Data Support. 2 M/N 

2. Transaction Receiver 

(Activity To) 

Identifies the activity to receive the transaction. 

DODAAC only. 

MCMC: 

The intended recipients of MCMC-initiated catalog data 

support transactions are the DLA DSS. 

Navy: 

The intended recipients of DLA-initiated catalog data support 

transactions are Naval Ship Yards (NSY) or Fleet Readiness 

centers (FRCs). 

If prepared by the NSY, the intended recipient is DLA EBS. 

6 M/N 

3. Party to Receive Copy Identifies the activity to receive a copy of the transaction. 

DoDAAC only. When materiel identification using a LSN 

applies, there will be a second iteration of the N1 Loop to 

identify the co-located Distribution Depot to receive a copy. 

6 N 

4. Transaction Submitter 

(Activity From) 

Identifies the activity preparing this transaction. 

DoDAAC only. 

MCMC: 

The preparing activity is the MCMC. 

For FLIS updates, the preparing activity is the DSS depot. 

Navy: 

The preparing activity is the DLA EBS or the NSY. 

6 M/N 

5. Catalog Transaction 

Purpose Code 

Identifies the purpose of the catalog data transaction. 

Applicable codes are: 

Navy and MCMC: 

AA New Catalog Record Added. 

CC Catalog Record Changed. 

DD Catalog Record Deleted. 

NP No NSN or LSN Found for Part Number/CAGE 

 (NSY/MCMC) 

RN NSN Replaced 

RS Use NSN When Exhausted 

NS NSN Superseded 

2 

 

2

 Identification of the Data Record Number (DRN) denotes an established data element within FLIS. The value carried in 

the catalog data support transaction will equal that in FLIS. FLIS Procedures, Volume 12 identifies and describes all itemof-supply and management data element, terms, and acronyms in the FLIS that have been assigned a DRN. 
ADC 360 

Attachment Page 10 

DS 832N 

Data Content 

Usage Notes/ 

Cross-Reference to FLIS Data Record Number (DRN)2/ 

Definition for Unique or Non-Standard Data Elements 

Field 

Length 

Applicability:

MCMC (M) 

Navy IA (N) 

DN NSN Discontinued; no Replacement 

Navy Only: 

QU Site Query for Catalog Record (NSY) 

MN Multiple NSNs for Part Number/CAGE 

NN No record exists for NSN query (NSY) 

NL No record exists for LSN query (NSY) 

NP No NSN or LSN Found for Part Number/CAGE 

 (NSY) 

RN NSN Replaced 

RS Use NSN When Exhausted 

SN NSN Substituted 

NS NSN Superseded 

DN NSN Discontinued; no Replacement 

6. Materiel Identification 

(primary and 

secondary): 

Local Stock Number 

(LSN) 

or

National Stock 

Number (NSN) 

or

CAGE and 

Part Number 

The primary materiel identification is normally the number 

identification by which the materiel is to be stored. The 

secondary materiel identification is the cross reference 

information for interpretation or further description of the 

primary identification (for example, if the primary materiel 

identification is a LSN, the secondary/cross-reference 

information might be the CAGE and part number). 

For Add and Change records, the primary material ID will be 

either an NSN or LSN. 

Queries may reflect NSN, LSN, or CAGE and Part Number 

combination. 

NSN materiel identified by Unit of Use LSN must include the 

cross-reference NSN. 

Navy Only: 

Part Number also required as a cross-reference for materiel 

cataloged using a LSN. FLIS DRN 3270 

CAGE also required as a cross-reference for materiel 

cataloged using a LSN. FLIS DRN 9250. 

RHICS Hazardous Material number beginning with LLN 

LSN also required as a cross-reference for queries identifying 

the part number/CAGE as the primary value. 

13 

 

 13 

5 

32 

M/N 

7. Assembly Type Identifies the type of assembly as a cross-reference for the 

assigned LSN. 

C = Control Kit 

P = Process Kit 

O = Other 

1 M 

8. Commodity Name Nomenclature/description for the item. 48 M/N 

9. Replacement NSN Used to identify the value of the replacement NSN when 

replaced or when superseded by a FLIS catalog action. 

13 M/N 
ADC 360 

Attachment Page 11 

DS 832N 

Data Content 

Usage Notes/ 

Cross-Reference to FLIS Data Record Number (DRN)2/ 

Definition for Unique or Non-Standard Data Elements 

Field 

Length 

Applicability:

MCMC (M) 

Navy IA (N) 

10. Substitute NSN Used to identify the value of the substitute NSN when the 

Source of Supply has provided BH status indicating a Service 

coordinated/approved substitute/interchangeable item is used 

to satisfy a requisition. 

13 N 

11. Shelf-Life Code Code expressing period of time for which the material will 

keep in total, that is, from the date of production to the shelf 

life expiration date. For DLA this is the old Shelf Life Code 

expressed as months. FLIS DRN 2943 

1 M/N 

12. Shelf-Life Action 

Code 

Two digit code specifying the type of inspection test or 

restorative action to be taken when an item has reached its 

storage shelf life and of any extension of the shelf life time 

period after the test or restorative has been completed 

2 M/N 

13. Material Control Code Used to identify the Material Control Code (MCC) for special 

inventory reporting. Segregates inventory into manageable 

groups (i.e. fast, medium, or slow) or to relate to field 

activities special reporting or control requirements. 

FLIS data applicable to DLRs, FLIS DRN 2611. 

1 M/N 

14. Special Material 

Identification Code 

Used to categorize material on the basis of requirements for 

source or quality control, technical data or configuration 

control, procurement, stocking and issue control. 

FLIS DRN 2834 

2 M/N 

15. Cognizance Symbol Used to identify the material cognizance system (COG) of the 

item. 

FLIS DRN 2608 

2 N 

16. Collaboration Planner 

Code 

 

Code designating within the system a specific individual with 

the ability to plan work. Default = 99 

FRC and NSY data element 

Staffing Note: There is not an existing qualifier in X12 for 

this data element, so it will be mapped to the qualifier 18, 

Plan Number, for transmission. 

2 N 

17. Collaboration Buyer 

Code 

This code identifies the industrial site collaboration buyer that 

is responsible for the item by the individual’s role code. 

NSY and FRC derived data element. 

2 N 
ADC 360 

Attachment Page 12 

DS 832N 

Data Content 

Usage Notes/ 

Cross-Reference to FLIS Data Record Number (DRN)2/ 

Definition for Unique or Non-Standard Data Elements 

Field 

Length 

Applicability:

MCMC (M) 

Navy IA (N) 

18. Local Application 

Code 

Code indicating how the material is processed in shop stores. 

Recognized by the program to inhibit automatic 

replenishment. 

Z Inhibit replenishment assigned on a situation basis 

E Delete at zero balance 

R Repair item 

O Order on request 

S Seasonal 

U Substitute 

I Insurance item 

Staffing Note: There is not an existing qualifier in X12 for 

this data element, so it will be mapped to the qualifier 6M, 

Application Number, for transmission. 

1 N 

19. Source of Materiel Code identifying the source of materiel: 

S for Supply, 

P for Local Purchase, 

M for Local Manufacturing 

Staffing Note: There is not an existing qualifier in X12 for 

this data element, so it will be mapped to the qualifier AS, 

Acceptable Source Supplier ID, for transmission. 

1 N 

20. NAVAIR Commodity 

Code 

 

 

A code identifying the commodity of material. NAVAIR 

codes to accumulate metric for repair on specific commodity. 

FRC unique requirement. 

This is a four position field, the first two positions have 

specific values, the second two are unique to FRC assignment 

within the MRP II used system to drill down information 

internally. Values for the first two positions are: 

AE ELECTRICAL WORK 

AF AIRFRAME STRUCTURE 

AO ARM/ORDNANCE 

AP AUX POWER UNITS (APU) 

AS AIRBORNE SUPPORT

AV AVIONICS

CA MECHANICAL CABLE ASSEMBLY

DC DYN COMPONENTS

EC ENGINE COMPONENTS

EL ELECTRICAL

FG FIBERGLASS

FW FABRIC WORK

GA GRAPHIC ARTS

GS GROUND SUPPORT

GT GAS TURBINE COMPRESSOR (GTC)

HA HOSE AND HOSE ASSEMBLY

HY HYDRAULIC COMPONENT

4 N 
ADC 360 

Attachment Page 13 

DS 832N 

Data Content 

Usage Notes/ 

Cross-Reference to FLIS Data Record Number (DRN)2/ 

Definition for Unique or Non-Standard Data Elements 

Field 

Length 

Applicability:

MCMC (M) 

Navy IA (N) 

HZ Hazmat

IN INSTRUMENTS

LG LANDING GEAR

MB Burden Material

MS MACHINE SHOP

MU Non-Burden Material

PB PBL Material

PN PNEUMATICS

PR PROPS

PS BONDED PANEL

PX Pre-Expended

RS RUBBER SHOP

SL SHELF LIFE

SM SHEETMETAL

SP Supply Material

TA TUBE AND TUBE ASSEMBLY

Staffing Note: There is not an existing qualifier in X12 for 

this data element, so it will be mapped to the qualifier LW, 

Location Within Equipment, for transmission. 

21. Critical Application 

Flag 

Code identifying Critical Safety Items. 

Values: Cite Y or N. 

1 M/N 

22. Inspection Required at 

Destination Flag 

Code identifying if inspection is required at destination upon 

receipt. 

Values: Cite Y or N. 

1 M/N 

23. Drawing Number Identifies the part drawing 32 N 

24. Detailed Drawing 

Piece Number 

Indicates the specific item within the drawing being 

referenced. NSY unique data element 

32 N 

25. Drawing Revision 

Number 

Code used to identify a specific revision number to a specific 

drawing when the requirement is for a lesser revision than is 

currently identified to the NSN. NSY unique data element. 

3 N 

26. Item Description Clear text description of the item. Nomenclature. Input as 10 

lines up to 80 characters each. 

10x 

80 

M/N 

27. Industrial Activity 

Lead Time 

Lead time (distribution or manufacturing) for providing an 

item to the IA, expressed in number of days. 

4 N 

28. Standard Unit Price The standard unit price which will be transmitted as 9 digits 

dollars, decimal point, and 2 digits cents. 

FLIS DRN 7075 

R9.2 M/N 
ADC 360 

Attachment Page 14 

DS 832N 

Data Content 

Usage Notes/ 

Cross-Reference to FLIS Data Record Number (DRN)2/ 

Definition for Unique or Non-Standard Data Elements 

Field 

Length 

Applicability:

MCMC (M) 

Navy IA (N) 

29. Unit of Use Price The unit of use price which will be transmitted as 9 digits 

dollars, decimal point, and 2 digits cents. This reflects the 

price of the item at less than the Standard Unit Price as 

calculated by the transaction originator. 

Note: For the Marine Corps, DSS will calculate the unit of 

use price on the DSS catalog records rather than it being sent 

on the 832N. 

R9.2 N 

30. Net Item Price Price for a repairable item that is unserviceable unit which has 

or will be turned in on an exchange basis. Also referred to as 

exchange price for depot level repairables. The net unit price 

which will be transmitted as 9 digits dollars, decimal point, 

and 2 digits cents. 

FLIS DRN 5235 

R9.2 N 

31. Unit of Issue Code indicating the terms/designations authorized for 

assignment to items of supply. Unit of issue will reflect the 

FLIS unit of issue for items identified as National Stock 

numbers. Local Stock Numbers will be the unit of issue as 

designated by the end user when a LSN is assigned. 

FLIS DRN 3050 

2 M/N 

32. Unit of Use 

Conversion Factor 

The factor by which the FLIS unit of issue quantity must be 

multiplied to convert to a unit of use. Value is expressed as 

R5.4. The decimal point is passed within the transaction; 

leading and trailing zeros are not transmitted. 

Navy Only: 

When an item is authorized for issue to the Navy at the unit of 

use, this identifies the conversion factor for calculation to the 

lowest authorized unit of use. 

R5. 4 N 

33. Unit of Use For cataloged items authorized for issue at the unit of use, this

identifies the less than standard unit of issue. 

Staffing Note: The code values for unit of use will be 

consistent with unit of issue, i.e., applications will use the 

applicable X12 value for transmission, while the DoD code is 

used internally. The DoD code set will be the same as for 

Unit of Issue under the DLMS Unit of Issue and Purchase 

Unit Conversion Table. 

2 N 

34. Source of Supply Code used to identify the activity (routing identifier code) that 

manages a given item. 

FLIS DRN 3690 

3 M/N 

35. Precious Metals 

Indicator Code 

Code used to identify items that have precious metals as part 

of their content. 

FLIS DRN 0802 

1 M/N 
ADC 360 

Attachment Page 15 

DS 832N 

Data Content 

Usage Notes/ 

Cross-Reference to FLIS Data Record Number (DRN)2/ 

Definition for Unique or Non-Standard Data Elements 

Field 

Length 

Applicability:

MCMC (M) 

Navy IA (N) 

36. Automated Data 

Processing Equipment 

Identification Code 

Code used to indicate if an item contains automated data 

processing equipment. 

FLIS DRN 0810 

1 M/N 

37. Acquisition Advice 

Code 

Code indicating how and under what restrictions an item will 

be acquired. 

FLIS DRN 2507 

1 M/N 

38. Acquisition Method 

Code 

Code describing the method of acquisition used in obtaining 

materiel

FLIS DRN 2871 

1 M/N 

39. Acquisition Method 

Suffix Code 

Code reflecting the Primary Inventory Control Activity 

(PICA) from planned procurement review. Used in 

conjunction with the Acquisition Method Code to delineate 

planned procurement action. 

FLIS DRN 2876 

1 M/N 

40. Controlled Inventory 

Item Code 

Code indicating the security classification or security risk or 

pilferage controls required for storage and transportation of 

DoD assets. 

FLIS DRN 2863 

1 M/N 

41. Demilitarization Code Code indicating to what degree an item must be destroyed or 

mutilated prior to disposal. FLIS DRN 0167 

1 M/N 

42. Special Material 

Content Code 

A code that indicates an item represents or contains peculiar 

material requiring special treatment, precautions or 

management control of the item. Applies to Navy Managed 

items only and is referred to as Haz Mat Indicator code within 

Navy system (MAT). FLIS DRN 0121 

1 N 

43. Packaging 

Requirement Code 

Level A 

Code designating Level A packaging. Container type, A= 

Wood, Plastic, or Steel. 

FLIS DRN 5170 

1 N 

44. Packaging 

Requirement Code 

Level B 

Code designating Level B packaging. Container Type 

Waterproof Fiberboard. 

FLIS DRN 5171 

1 N 

45. Packaging 

Requirement Code 

Minimal. 

Code designating Level C packaging. Container type 

cardboard. (Minimum commercial level). 

FLIS DRN 5172 

1 N 

46. Safety Level Identifies the safety stock level the industrial site suggests for 

induction of a new stock item. This code is site specific. 

Value is expressed as R7.2. (The decimal point is passed 

within the transaction; leading and trailing zeros are not 

transmitted.) 

R7.2 N 

5. REASON FOR CHANGE: As a result of BRAC 2005 CONOPS, EBS is required to send catalog 

information to the Navy Industrial site systems [MAT and Manufacturing Resource Planning (MRP) 

II] to ensure the same or better functionality exist after the implementation of BRAC 2005 as before. 
ADC 360 

Attachment Page 16 

Additionally, this catalog data exchange is required due Navy Nuclear Propulsion Information System 

(NNPI) firewall security, which prevents outside systems from pushing data into the NSY MAT 

system. Additionally, MCMC systems are required to send catalog information to the DLA DSS 

system to ensure the same or better functionality exists after the implementation of BRAC 2005 as 

before. 

6. ADVANTAGES AND DISADVANTAGES: 

a. Advantages: Supports BRAC CONOPS using DLMS transactional interface. 

b. Disadvantages: Duplicates some functionality available via FLIS interface which is the 

authoritative source for catalog data.

7. Impact

a. Defense Automatic Addressing System (DAAS): This is a new transaction with no MILS 

equivalent. 

b. Planned Implementation Date: 

(1) DLA and Navy: Testing is to begin March 2011 with DSS and April 2011 with Navy. 

Target Implementation is Aug 2011. 

(2) DLA and Marine Corps: Testing will begin January 2011. Target implementation is 

April 2, 2011. 

c. Publications: DLMS Manual update provided at Enclosure 4. Internal Service/Agency 

guidance as required. 

d. Policy: Requires update to supply chain management policy to recognize requisitioning and 

storage using unit of use in support of SDI. Requires update to supply chain management policy to 

recognize the requisitioning of part numbered items cataloged to a local stock number (vice 

submission of part numbered requisitions). 

e. Integrated Data Environment (IDE)/Global Transportation Network (GTN) Convergence 

(IGC). This change is a new business process and impact must be assessed by developers. 

f. Asset Visibility Application (DLA Logistics Information System). Assets identified by nonstandard material identification types will not be recognized by third parties in AV unless the crossreferences established by the DLMS 832N, Catalog Data Support, transaction are known to AV. 

g. New Data Content. The DLMS 832N, Catalog Data Support, is a new transaction supporting 

both Navy and Marine Corps BRAC implementation. It introduces multiple new data elements and 

new code values to the DLMS dictionary. The applicable definition, characteristics, and code values 

are shown above. Some data elements established via the DLMS 832N have subsequently been used 

on other DLMS transactions and so may no longer be considered “new” elements, however the list is 

included here for information. 

Catalog Purpose Code 

Catalog Transaction Purpose Code 

Assembly Type 
ADC 360 

Attachment Page 17 

Shelf-Life Action Code 

Collaboration Planner Code 

Collaboration Buyer Code 

Local Application Code 

Source of Materiel Code

NAVAIR Commodity Code 

Critical Application Flag 

Inspection Required at Destination Flag 

Detailed Drawing Piece Number 

Industrial Activity Lead Time 

Unit of Use Conversion Factor 

Unit of Use Indicator 

Unit of Use Price 

Local Stock Number 

Hazardous Material Indicator Code (HMIC) 
ADC 360 

Enclosure 1, Page 1 

Enclosure 1, Catalog Data Support Flow Diagram - Navy 

1a/1b. (FRC/NSY) User queries EBS using NIIN or Part Number and CAGE code. EBS responds to queries directly to the 

screen with data required to establish the MM or JML. -> 1a1, 1b1 

1a1/1b1. EBS provides LSN/NSN information if available. If no NSN, EBS initiates a query (1c) and provides the 

response to user. If no LSN, then EBS tells user ‘no existing LSN’. ->1c 

1c. (DLA) EBS will query DLIS and retrieve FLIS data for NSNs not established in EBS ->2a 

1a2/1b2. EBS will provide response to the query which will specify NSN/LSN established in EBS or acquired from FLIS in 

1c. The response will include DLR and Nuclear items. ->1a3/1b3 

1a3/1b3. User accepts the NSN/LSN data in response to EBS. ->2a 

2a EBS adds a record for users plant in EBS- SAP (if required). ->2b 

2b EBS initiates 832N transactions to DAASC for all ->3a. 

3a. DAASC will receive, validate and route the 832N (NSN/LSN) transaction to IF 1a for FRC ->4a and 3c 

3b. DAASC will receive, validate and route the 832N (NSN/LSN) transaction to Proxy Server In/ Out Folder (PS I/O F) 

for NSY ->4b and 3c 

3c. DAASC receive, validate and route the LSN 832N transaction to DSS IA Worksite. -> 3c1 

3c1: DSS will update Stock Item Record -> END 

4a. IF 1a creates item MASTER in MRP II ->END 

4b. The PS I/O F receives DAASC transactions (832N) for IF 1b retrieval.-> 4c 

4c. Interface 1b pulls in transactions from the PS I/O F in folder for SYMMR Table update in MAT -> END 
ADC 360 

Enclosure 1, Page 2 

1. NSY engineers complete JML order data and pass to MAT. ->2 

2. MAT queries the SYMMR to determine existing NSN/LSN. If yes, MAT has determined that a NSN or LSN is 

established in SYMMR, and it will release the demand signal/issue order. ->Demand Signal or Issue Order Process. If no, 

LSN/NSN is not found in SYMMR, MAT will suspend the JML. ->3 

3. MAT will generate an 832N request for stock number assignment and forwards to PSIOF. ->4 

4. PSI/OF pushes transaction to DAASC for processing. ->5 

5. DAASC will receive, validate, and route the 832N to EBS. ->6 

6. EBS will receive the 832N and query for LSN/NSN. If found, an 832N with NSN or LSN will be returned through 

DAASC to MAT. If not found, EBS will inquire FLIS for NSN not currently established in EBS. ->7a or 7b 

7a. EBS formats 832N with NSN or LSN and exits to DAASC. ->8 

7b. If inquiry of FLIS returns no NSN, EBS will establish LSN and format the 832N and exit to DAASC. ->8 

DAASC receives, validates, and routes the 832N to the NSY Hold Queue and routes LSN 832N to DSS. ->8a, 9 

8a. DSS receives LSN 832N and updates Stock Item Records -> END 

9.PSI/OF pulls the transaction and passes it to MAT. ->10 

10. MAT updates the JML, the shipyard material master file (SYMMR) and MRQT. The updated JML will result in an 

outgoing demand signal or issue order. ->Demand Signal/Issue Order Process 
ADC 360 

Enclosure 1, Page 3 

1a. DLIS will push FLIS owned data element updates for DLA Managed and specified non DLA Managed Items (NSNs) to 

EBS.->2a 

1b. DLIS will push any NSN Material updates to DSS IA Worksite.->4c 

2a. Inbound data from DLIS or EBS is received and systemically updates EBS SAP (MM).->3a/3b 

2b. EBS User manually updates SAP/Unique Table data elements (MM) or programmatically updates based on data fields 

such as safety level, lead time, etc.->3a/3b 

3a. EBS generates 832N transaction for outbound MMR change data and sends to DAASC -> 4a 

3b. EBS generates LSN 832N transaction for outbound MMR change data and sends to DAASC for DSS IA Worksite. -

>4b 

4a. DAASC receives and validates the 832N (NSN/LSN) transactions from EBS. ->4a1, 4a2 

4a1. DAASC routes the 832N (NSN/LSN) transactions to IF 1a for update of MRP II. ->5a 

4a2. DAASC places 832N (NSN/LSN) transactions in the NSY hold queue for NSY PS I/O F to pull 832Ns for MAT 

update.->5b 

4b. DAASC will pass the LSN 832N transaction to DSS IA Worksite. -> 4c 

4c. DSS IA Worksite processes any NSN/LSN Material updates.->END 

5a. IF 1a receives, processes and sends MMR Change Data to MRP II ->END 

5b. PS I/O F pulls 832Ns and passes for MAT SYMMR Table update ->5b1 

5b1. IF 1b receives transactions from the PS I/O F in folder and updates the MAT SYMMR Table. -> EN
ADC 360 

Enclosure 2, Page 1 

Enclosure 2, Catalog Data Support Flow Diagram – Marine Corps 

This diagram dipicts DLMS 832N transaction flo between, MRP II, ILSMIS, through the Marine 

Corps Bridge and DAAS to DSS. 

 
ADC 360 

Enclosure 2, Page 2 

Non-Unit of Use LSN 

1. User Creates MRP II part number in MRP II. The following data will be passed to DSS 

to create the new MRP II number: Stock number (FSC & NIIN), unit of issue (vendor 

unit of issue), unit of measure (MC unit of use), stock room number (translating to 

owner RIC in DSS), CIIC default (U), DEMIL code default (A), unit price default (0), 

nomenclature. 

1.1. Eng-1 passed to Marine Corps Bridge for the new MRP II number 

1.2. Marine Corps Bridge passes new catalog records through DAAS to DSS as a 

(832N) transaction. 

2. ILSMIS creates a new LSN. The following data will be passed to DSS to create the 

new LSN: Stock number (FSC & NIIN), unit of issue (vendor unit of issue), unit of 

measure (MC unit of use), manager RIC, CIIC, DEMIL code, unit price, nomenclature, 

COG, SOS, etc. 

2.1. Catalog record passed to Marine Corps Bridge for all new LSNs. Inventory record 

passed to the Marine Corps Bridge for DSS file designator new LSN. NOTE: MRP 

II catalog records will be created via Nightly Sync from ILSMIS – due to fields 

that are required in MRP II that are not loaded to ILSMIS. 

2.2. Marine Corps Bridge passes the new LSN through DAAS to DSS as a (832N) 

transaction 

3. MRP II changes/updates an MRP II number and passes the changes to the Marine Corps 

Bridge. Changes could include: FSC, unit of use, nomenclature, manufacture part 

number and cage (Catalog record), and unit of issue. 

3.1. INV-3 passed to Marine Corps Bridge to change existing MRP II number 

3.2. Marine Corps Bridge passes the changes to the MRP II number through DAAS to 

DSS as a (832N) transaction 

4. ILSMIS changes/updates a LSN number and passes the changes to the Marine Corps 

Bridge. Changes could include: FSC, standard unit of issue, nomenclature, and 

manufacture part number and cage (Catalog record). NOTE: Local unit of issue is 

covered in File Maintenance section. 

4.1. Marine Corps Bridge passes the changes to the LSN number through DAAS to 

DSS as a (832N) transaction 

5. MRP II deletes an existing MRP II number and sends deletion request to Marine Corps 

Bridge 

5.1. Marine Corps Bridge sends 832N deletion request through DAAS to DSS 

6. ILSMIS deletes a LSN Number; generate an 832N through DAAS to DSS. 

6.1. Marine Corps Bridge sends 832N deletion request through DAAS to DSS 
ADC 360 

Enclosure 2, Page 3 

MC FLIS Replacement NIIN changes:

1 DSS will send (832N) transaction to Marine Corps bridge for all FLIS changes related 

to changing or replacing a NIIN, Marine Corps bridge will interpret change until 

ILSMIS/MRP II are updated to use new NSN 

1.1 If NSN doesn’t match the 527D, DSS should stop transaction and contact Marine 

Corps to update 527D 

1.1.1 For a FLIS NSN change DSS will change the NSN immediately (to include 

corresponding unit of use LSN). 

1.1.2 DSS should send e-mail to Marine Corps distribution list at time change 

occurs. 

1.1.3 Marine Corps will research impact of NSN change and update records as 

required. 
ADC 360 

Enclosure 3, Page 1 

Enclosure 3, DLMS Manual Guidance 

 DoD 4000.25-M, Volume 2 

C25. CHAPTER 25

Catalog Data Support 

C25.1 GENERAL 

C25.1.1 Purpose. This chapter provides general information regarding procedures and data 

exchange requirements for the communication of the DLMS Catalog Data Support. 

C25.1.2 Transactions. This chapter addresses procedures applicable to the following ASC X12 

transaction functions identified by the transaction set number and beginning segment Catalog Purpose 

Code (1/BCT01/0200). There is no MILS equivalent. See the DLMSO website for available DLMS 

formats: http://www.dla.mil/j-6/dlmso/elibrary/TransFormats/140_997.asp. 

 C25.1.2.1 DLMS Supplement to Federal IC 832N, Catalog Data Support, is used for the 

following transaction functions identified by the beginning segment Transaction Purpose Code: 

 C25.1.2.1.1 Industrial activity (IA) catalog data support authorized by agreement with DLA 

is identified by Transaction Purpose Code RC. This transaction is referred to as the “Supply, Storage, 

and Distribution (SS&D) Catalog Data Support” transactions. 

 C25.1.2.1.2 Reserved. (This is a placeholder for other Catalog Data Support transactions that 

will be identified by different Transaction Purpose Codes.) 

C25.2 INDUSTRIAL ACTIVITY (IA) CATALOG DATA SUPPORT 

 C25.2.1 Navy 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. DLA will be the material provider for all consumable items in support of the 

maintenance mission at these sites. In order to effectively manage materials at these sites, DLA will 

maintain material master records identifying the materiel identification and associated characteristics 

for all DLA managed, non-DLA managed, and local stock number materials that are used by the Navy. 

Prior to the BRAC decision, Enterprise Business System (EBS) maintained material master records for 

all DLA managed items and some non-DLA Managed items; with this new requirement the DLA EBS 

establishes materiel master records for any non-DLA managed item requested by the Navy Fleet 

Readiness Centers (FRCs) and the Naval Shipyards (NSYs). 

 C25.2.2 Marine Corps Background. As a result of the 2005 BRAC decision, operating material 

and supplies storage and distribution functions and associated infrastructure supporting the Marine 
ADC 360 

Enclosure 3, Page 2 

Corps Maintenance Centers (MCMC) industrial/maintenance sites will transfer to DLA. DLA will be 

the storage and distribution provider for most consumable items in support of the maintenance mission 

at these sites. In order to effectively manage materials at these sites, DLA Distribution Standard 

System (DSS) will maintain item data records containing the materiel identification and associated 

characteristics for all materials that are used by the MCMC. Prior to the BRAC decision, DSS 

maintained item data records for all DLA managed items and most non-DLA-managed items; with this 

new requirement the DLA DSS will establish item data records for any item assigned a Local Stock 

Number (LSN) by the MCMC. 

 C25.2.3 The catalog data exchange supports the following functions. Specific implementation 

varies by Service: 

 C25.2.3.1 Communication of FLIS and user unique data associated information for newly 

cataloged National Stock Number (NSN) materiel. 

 C25.2.3.2 Identification of non-National Stock Number (NSN) materiel by a Local Stock 

Number (LSN) so that the LSN may be recognized for requisitioning, storage, and receipt processing. 

 C25.2.3.3 Communication of FLIS catalog change notices to the Navy NSY and FRC sites. 

DLA will send change notices whenever an active material master record is updated in the form of IA 

Catalog Data Support (832N) transactions. EBS will send notices for changes resulting from manual/ 

programmatic updates (within EBS) and from systemic updates (from FLIS). FLIS changes include 

communication of replacement, superseded, and discontinued NSNs. 

 C25.2.3.4 Identification of NSN materiel by a LSN so that the LSN may be used for storage and 

distribution of materiel identified at the unit of use (that is, a unit of measure that is less than the FLIS 

unit of issue). 

 C25.2.3.5 Identification of MCMC LSNs to a unit of use LSN. 

 C25.2.3.6 Communication of a Service coordinated/approved substitute/ interchangeable item as 

a result of DLA or other Service provided supply status to associate the substitute NSN with the 

primary NSN. 

 C25.2.3.7 Shipyard prepared queries to identify available DLA EBS materiel master matches on 

NSN, LSN, or part number/CAGE. This action may trigger EBS query against FLIS. EBS responses 

will be returned in an IA Catalog Data Support (832N) transaction. 

C25.3 PROCEDURES – NAVY INTERFACE 

 C25.3.1 Upon data conversion, all the current local stock numbers and non-DLA managed material 

masters from the FRC and NSY systems will be migrated to EBS. This will provide a base line for the 

materials currently used at all five BRAC sites. 
ADC 360 

Enclosure 3, Page 3 

 C25.3.2 The catalog data will be applicable to new item inductions, FLIS change notices for DLA 

items and non-DLA managed items, as well as Navy-assigned LSNs. Since DLA will be purchasing, 

storing, and selling these items to industrial activities (IAs), DLA will have this data resident in the 

EBS and will provide visibility and updates to the Navy systems via the SS&D Catalog Data Support 

(832N) transaction. 

 C25.3.3 EBS will also maintain site specific material master records for Depot Level Repairable, 

Nuclear Support Consumables, or Program Owned Material (even COG) items to provide updates 

pertaining to FLIS data or user unique data elements to the FRC or NSY sites. SS&D Catalog Data 

Support (832N) change transactions will be provided to applicable sites based on FLIS updates or end 

user changes to user defined data elements for these items. 

C25.3.4 Web-based Query. When new items are needed by any of these sites, the capability to 

create new material masters or update user defined data elements to existing material masters directly 

into EBS through a user unique screen. This application within EBS will prompt users for mandatory 

fields and user defined fields for new entries, which may be optional depending upon the site 

(FRC/NSY). The screen will allow the user to query the current EBS data base and determine if an 

NSN or LSN already exist within EBS. 

C25.3.5 If an existing record is found, and EBS does not currently reflect the material master is 

extended to the user site, based on user response the material will be extended to the user site and an 

SS&D Catalog Data Support (832N) transaction will be sent to user site and identified as an ‘ADD’ 

record. 

 C25.3.6 When no record is found within EBS, the system will query FLIS Reference Master Data 

Environment (RMDE) to identify any associated National Stock Number. Once the materiel master is 

created in EBS, an SS&D Catalog Data Support (832N) will be sent to the applicable FRC or NSY 

site. If found, the user will have the option to build a material master, record will be created with FLIS 

data and any mandatory user unique data elements in EBS based on user response/input. EBS would 

then format an SS&D Catalog Data Support (832N) transaction. This SS&D Catalog Data Support 

(832N) transaction will be identified as an ‘ADD’ and will be sent to the appropriate NSY/FRC site 

via DAASC. 

C25.3.7 If no NSN is found in FLIS, the user will have the option to add a materiel master 

identified by an EBS assigned Local Stock Number (LSN). EBS has logic which will default specific 

mandatory FLIS data elements, and prompt user for those for which a default cannot be determined. 

EBS will then format an SS&D Catalog Data Support (832N) transaction and send to the site identified 

by the user and also furnish a copy to the instance of DSS at the same site. 

 C25.3.8 Materiel Identification. Cataloging data will be categorized by two methods of materiel 

identification

 C25.3.8.1 Items identified by NSN. For these, DLA will relay FLIS catalog information in the 

absence of a Navy-FLIS interface. DLA will also incorporate additional DLA/Navy unique content.
ADC 360 

Enclosure 3, Page 4 

 C25.3.8.2 Items identified by LSN. There will be three four configurations of LSN material 

numbers within EBS. 

 C25.3.8.2 .1 Items cataloged with an NSN, but which will be issued to the Navy in a unit of 

use, which is less than the FLIS unit of issue. EBS will assign a unique LSN using the existing data 

associated with the original NSN. All transactions for this item will be recorded within EBS under the 

LSN. There will be a cross-reference on the material master from the LSN to the NSN, and on the 

NSN to the LSN. LSNs in this category will use the following construct: 5975-U0-000-1234.

 C25.3.8.2.2 Items currently identified within a Navy system (MAT or MRP II) as a LSN will 

be migrated into EBS. EBS will continue to process transactions against these numbers and 

modification will be done through user unique screen application by end users. Updates will be sent to 

applicable sites based on these updates. LSNs in this category will use the following construct: 5315- 

LL-00-9876. 

 C25.3.8.2.3 Items for which a material master is needed to request material but there is no 

current LSN or NSN assigned to the Cage and Part Number combination within EBS or FLIS. EBS 

will allow end users to create a material master for these items via the user unique screen application 

and systemically assign a LSN. Updates will be sent to applicable sites based on the initial creation 

and any subsequent updates based on end user input. These LSN’s will be established based on FSC 

with a serial number range of NL00000000001 through NL99999999999. 

 C25.3.8.2.4 Items for which a materiel master is needed to identify hazardous material under 

Regional Hazardous inventory Control System (RHICS). For these only, a LSN identifying the 

RHICS cataloged or created “LLN” numbers will be used if no NSN is assigned. 

 C25.3.8.2.4.1 EBS will search existing data base to determine if there is an existing 

record of the RHICS material beginning with LLN (first 3 digits). When there is an existing material 

master EBS will return an 832N identified as an “ADD” record containing all agreed to data elements 

to build a record in MAT and pass a copy to DSS. 

 C25.3.8.2.4.2 If no material master for the RHICS hazardous material, the user will be 

prompted for mandatory fields and user defined fields for new entries using the RHICS data base 

elements. The key is that only one RHICS LLN numbers will be used for like material. Thereby 

having only one LLN number per hazardous material for all users. When the query is for an LLN, the 

832N will be an output transaction to MAT and a copy will be furnished to the applicable DSS site. 

 C25.3.8.3 New Records. Upon creation of new materiel identification content applicable to this 

process, EBS will build the material master, apply the catalog data to the identified sites (extend to the 

user sites), and format an SS&D Catalog Data Support (832N) transaction citing Catalog Purpose 

Code AA, New Catalog Record Added, which will be sent to the appropriate NSY/FRC site via 

DAASC. EBS will provide a copy of SS&D Catalog Data Support (832N) transactions for items 

identified as Local Stock Numbers to the applicable Distribution Depot site. 

C25.3.8.4 Modified Records. When the user entry modifies an existing record via the user 

unique screen application, the user will be prompted to save changes. This will trigger EBS to 
ADC 360 

Enclosure 3, Page 5 

generate an 832N citing Catalog Purpose Code CC, Catalog Record Changed. This record will contain 

all applicable data elements to build a record within Navy systems (allowing overlay, vice 

transmission of only the modified content). If the change is to an existing LSN record previously 

provided to a Distribution Depot, a copy of the change will also be furnished. 

C25.3.8.5 Transaction Query. NSY sites will have the additional capability to inquire EBS 

material master records using an SS&D Catalog Data Support (832N) citing Catalog Purpose Code 

QU, Site Query for Catalog Record, to determine if NSN or LSN or CAGE Code and Part Number 

combination exists in the EBS data base when there is no existing record on the internal table within 

the NSY Navy system. 

 C25.3.8.5.1 If there is an existing material master within EBS for the inquired ‘NSN’, EBS 

will extend the material master to the inquiry site and return an SS&D Catalog Data Support (832N) 

citing Catalog Purpose Code AA, New Catalog Record Added, containing all mandatory data 

elements to build a record in MAT system. 

 C25.3.8.5.2 If there is no material master within EBS for the inquired NSN, EBS will inquire 

FLIS. When the response is positive EBS build a material master and return an SS&D Catalog Data 

Support (832N) citing Catalog Purpose Code AA, New Catalog Record Added, containing all 

mandatory data elements to build a record in MAT system. 

 C25.3.8.5.3 If the response from FLIS for the inquired NSN is negative EBS will return an 

SS&D Catalog Data Support (832N) citing Catalog Purpose Code NN, No record exists for NSN 

query. MAT will output for manual review. 

 C25.3.8.5.4 If there is an existing material master within EBS for the inquired ‘LSN’, EBS 

will extend the material master to the inquiry site and return an SS&D Catalog Data Support (832N) 

citing Catalog Purpose Code AA, New Catalog Record Added, containing all mandatory data 

elements to build a record in MAT system. 

 C25.3.8.5.5 If the response for the inquired LSN is negative EBS will return an SS&D 

Catalog Data Support (832N) citing Catalog Purpose Code NL, No record exits for LSN query. MAT 

will output for manual review. The user may at this point enter data into the EBS user unique entry 

screen indicating the need to create a record. 

 C25.3.8.5.6 If there is an existing material master within EBS for the inquired ‘Part 

Number/CAGE’, EBS will extend the material master to the inquiry site and return an SS&D Catalog 

Data Support (832N) citing Catalog Purpose Code AA, New Catalog Record Added, containing all 

mandatory data elements to build a record in MAT system. 

 C25.3.8.5.7 If there is NO existing material master within EBS for the inquired ‘Part 

Number/CAGE’, EBS will invoke query to FLIS. 
ADC 360 

Enclosure 3, Page 6 

 C25.3.8.5.7.1 When the FLIS response is positive and only one NSN is returned, EBS will 

build the material master to the inquiry site and return an SS&D Catalog Data Support (832N) citing 

Catalog Purpose Code AA, New Catalog Record Added, containing all mandatory data elements to 

build a record in MAT system. 

 C25.3.8.5.7.2 When the FLIS response is positive and multiple NSNs are returned, EBS 

will return an SS&D Catalog Data Support (832N) citing Catalog Purpose Code MN: Multiple NSNs 

for Part Number/CAGE. MAT will output record for manual review. The user will determine which 

NSN is applicable for their use and will have the option to inquiry against the specific NSN or build 

the record through the EBS on-line input. 

 C25.3.8.5.7.3 When the FLIS response is negative, EBS return an SS&D Catalog Data 

Support (832N) citing Catalog Purpose Code NP, No NSN or LSN Found for Part Number/CAGE, to 

MAT for manual review. 

 C25.3.9 Unit of Use. Unique functionality to be added in support of 2005 BRAC decision at the 

NSY and FRC sites is the ability to issue and store material at a quantity and unit of use less than the 

FLIS unit of issue. In these instances EBS will apply unique logic to create a material master with a 

LSN. This record will contain all applicable FLIS and user unique data elements copied from the 

original NSN. The EBS material master records for both the LSN and NSN will reference each other. 

 C25.3.9.1 EBS will create a LSN record for all NSN items identified with a unit of use upon 

data conversion as a base line. After initial conversion these records will be based on either a 

requisition alert or funded requisition from any NSY or FRC site identifying a unit of use requirement. 

An SS&D Catalog Data Support (832N) record will NOT be generated to the NSY/FRC sites, but will 

be forwarded to the applicable DSS site. 

 C25.3.9.2 The SS&D Catalog Data Support (832N) record will reflect the assigned LSN and 

Unit of Use as well as the associated NSN and FLIS unit of issue. DSS will build an internal table 

cross-referencing the NSN and the associated Unit of Use LSN, FLIS Unit of Issue and the Unit of 

Use. 

 C25.3.10 Substitute Cross Reference. EBS will provide catalog data reflecting substitute reference 

during the status process. This will occur for both DLA managed substitutions and for other Service 

managed substitutions. 

 C25.3.10 .1 When EBS processes a request from either NSY or FRC and determines Prime 

Number is not available but an approved substitute is available. EBS will provide ‘BH’ status and 

format an SS&D Catalog Data Support (832N) identified as a substitute record reflecting the Prime 

NSN and reference the substitute NSN. 

 C25.3.10 .2 When EBS receives a ‘BH’ indicating DLA will be sent an item previously 

identified as a Navy suitable substitute for a DLA funded requisition, the status will prompt EBS to 

format an SS&D Catalog Data Support (832N) citing Catalog Purpose Code SN, NSN Substituted, 
ADC 360 

Enclosure 3, Page 7 

reflecting the Prime NSN and reference the substitute NSN when a material master already exist in 

EBS. 

 C25.3.10 .3 When a material master for the substitute NSN does not exist in EBS, a material 

master record will be created. Any user unique data elements will be copied from the Prime NSN 

specific to that site. An SS&D Catalog Data Support (832N) citing Catalog Purpose Code SN, NSN 

Substituted, reflecting the Prime NSN and reference the substitute NSN will be forwarded to the 

applicable site for updating of Navy systems. 

 C25.3.10 .4 EBS will not maintain a cross reference to other service managed NSNs pertaining 

to Substitution. 

 C25.3.11 FLIS Change Notices. EBS will be responsible for providing all ‘change notices’ to the 

Navy BRAC 2005 SS&D sites. These change notices will be generated as a result of FLIS data 

changes. Anytime a FLIS recorded data element in EBS is modified an SS&D Catalog Data Support 

(832N) citing Catalog Purpose Code CC, Catalog Record Changed, will be sent to all FRC/NSY sites 

which the material has been extended to within EBS. The changed data element will not be 

specifically identified. Each FRC/NSY system will update internal records accordingly. 

 C25.3.11.1 NSN Replacement. When an NSN is specifically identified as a ‘REPLACED BY’ 

the SS&D Catalog Data Support (832N) citing Catalog Purpose Code RN, NSN Replaced, and both 

the former and new NSN will be identified. MAT and MRP II will update system as applicable for 

these records. 

 C25.3.11.2 When an NSN is specifically identified as ‘DISCONTINUED’ the SS&D Catalog 

Data Support (832N) citing Catalog Purpose Code DN, NSN Discontinued; no Replacement. If a 

subsequent NSN is identified from the FLIS update, the SS&D Catalog Data Support (832N) citing 

Catalog Purpose Code NS, NSN Superseded, will contain both the former and new NSN. MAT and 

MRP II will update system as applicable for these records. 

 C25.3.11.3 When an NSN is specifically identified as ‘When Exhausted use’ the SS&D Catalog 

Data Support (832N) citing Catalog Purpose Code RS, Use NSN When Exhaused, and both the 

former and new NSN will be identified on the SS&D Catalog Data Support (832N) transactions. 

MAT and MRP II will update system as applicable for these records. 

C25.4 PROCEDURES – MARINE CORPS INTERFACE. 

C25.4.1 Upon data conversion, all the current local stock numbers and non-DLA managed 

material masters from the MCMC systems will be migrated to DSS. This will provide a base line for 

the materials currently used at all MCMC sites. 

C25.4.2 The catalog data will be applicable to MCMC-assigned LSNs. Since DLA will be 

storing and distributing these items to industrial activities (IAs), DLA will have this data resident in 
ADC 360 

Enclosure 3, Page 8 

the DSS and the MCMC will provide visibility and updates to these LSNs via the SDI Catalog Data 

Support (832N) transaction. 

C25.4.3 Web-based Query. When new items are needed by any of these sites, the capability to 

create new material masters or update user defined data elements to existing material masters directly 

into MCMC systems through a user unique screen. This application within the MCMC systems will 

prompt users for mandatory fields and user defined fields for new entries, which may be optional 

depending upon the site application. The screen will allow the user to query the current MCMC data 

base and determine if an NSN or LSN already exists. 

C25.4.4 If no NSN or LSN exists in the MCMC systems, the user will have the option to add 

a materiel master identified by a MCMC assigned Local Stock Number (LSN). MCMC systems have 

logic which will default specific mandatory data elements, and prompt user for those for which a 

default cannot be determined. MCMC systems will then format a Catalog Data Support (832N) 

transaction and send to the site identified by the user. 

C25.4.5 Materiel Identification. Cataloging data will be categorized by items identified by 

Local Stock Number where no NSN is assigned. 

C25.4.5.1 Items currently identified within MCMC systems [Industrial Logistics 

Support Management Information System (ILSMIS), and Material Resource Planning (MRP) II] as a 

LSN will be migrated into DSS. DSS will continue to process transactions against these LSNs and 

modification will be done through user unique screen application maintained by the MCMC systems. 

Updates will be sent to applicable sites based on these updates. 

C25.4.5.2 Items Identified by CAGE and Part Number Combination (with no LSN or 

NSN Assigned) within MCMC systems. MCMC systems will allow end users to create a material 

master for these items via the user unique screen application and systemically assign a LSN. Updates 

will be sent to applicable sites based on the initial creation and any subsequent updates based on end 

user input. These LSNs will be established based on the Federal Supply Class (FSC) with a 

sequentially assigned number in the LSN NIIN. 

C25.4.5.3 A cataloging action is not required to establish unit of use LSNs for NSN 

materiel or for non-NSN materiel previously assigned a LSN. An asset reclassification (846A) action 

will be used to re-identify the materiel and trigger the creation of an item data record under the new 

LSN within DSS. 

C25.4.6 New Records. Upon creation of new materiel identification content applicable to this 

process, MCMC systems will build the material master, apply the catalog data to the identified sites 

(extend to the user sites), and format a Catalog Data Support (832N) transaction citing Catalog 

Purpose Code AA, New Catalog Record Added, which will be sent to the DSS via DAASC. 

C25.4.7 Modified Records. When the user entry modifies an existing record via the user 

unique screen application, the user will be prompted to save changes. This will trigger the MCMC 
ADC 360 

Enclosure 3, Page 9 

system to generate an 832N citing Catalog Purpose Code CC, Catalog Record Changed. This record 

will contain all applicable data elements to build a record within the DSS system (allowing overlay, 

vice transmission) of only the modified content 

C25.4.8. Deleted Records. When the user entry deletes an existing record via the user unique 

screen application, the user will be prompted to save changes. This will trigger the MCMC system to 

generate an 832N citing Catalog Purpose Code DD, Catalog Record Delete. This record will contain 

all applicable data elements to delete a record within the DSS system 

C25.4.9. FLIS Change Notices. DSS will be responsible for providing change notice 

information via catalog data support transactions to MCMC sites for changes related to the NSN itself. 

MCMC systems will be updated as applicable for these records. 

 C25.4.9.1 NSN Replacement. When an NSN is specifically identified as a 

‘REPLACED BY,’ the SS&D Catalog Data Support (832N) citing Catalog Purpose Code RN, NSN 

Replaced, including the former and new NSN will be identified. 

 C25.4.9.2 When an NSN is specifically identified as ‘DISCONTINUED’ the SS&D 

Catalog Data Support (832N) citing Catalog Purpose Code DN, NSN Discontinued; no Replacement, 

will be provided. If a subsequent NSN is identified from the FLIS update, the SS&D Catalog Data 

Support (832N) citing Catalog Purpose Code NS, NSN Superseded, will be provided containing both 

the former and new NSN. 

 C25.4.9.3 When an NSN is specifically identified as ‘When Exhausted use’ the SS&D 

Catalog Data Support (832N) citing Catalog Purpose Code RS, Use NSN When Exhaused, will be 

provided including both the former and new NSN. 
ADC 360 

Enclosure 4, Page 1 

Enclosure 4, PDC Comment Resolution 

# Submitter Comment Response 

1. USMC PDC 360B: Concur 

PDC 360A: Nonconcur: 

1. The proposal is to establish a methodology 

to allow data exchange between DLA, 

Distribution Depots using DSS and Navy IA. 

However this proposal recommends 

identification of NSN material be identified by 

a NSN to allow storage at the consumption/use 

level versus the procurement level. The 832 

transaction requires the creation of several 

FLIS DRNS that have not been vetted through 

the FCC. The FCC serves as the authoritative 

body for the establishment of new codes in the 

catalog. Recommend this proposal be vetted to 

the FCC. 

2. How will LSN stock be turned in to DRMO? 

If by LSN how will the services requisition 

from DRMO? 

3. Para 4.c. (a) states that DLA will store data 

for items and non-DLA managed items in EBS 

since they will be purchasing, storing and 

selling these items to Industrial HQMC Sites. 

DLA should not be in the business of “reselling” other service/agency managed stock. 

This is in violation of the integrated materiel 

management rules. 

4. Paragraph 4.a. (1) states that the LSN may 

be recognized for requisitioning and 

distribution processing. The Marine Corps does 

not expect to receive a requisition from the 

Navy with a LSN. 

Recommendation: 

1. When a non-definitive unit of issue (box, 

package, reel, etc) exists, DSS can build a 

cross-reference conversion table that will break 

the non-definitive UI to a unit of consumption/ 

use. A conversion table is available in the FLIS 

manuals. 

2. Federally assigned NSNs should be 

None required. 

Noted. 

1. The value used to identify NSN materiel at 

the unit of use level will be recognized as a 

local stock number (not as another NSN). The 

DRNS applied in FLIS for the NSN will be 

carried in the 832 for the associated LSN. New 

DRNS will not be established. 

The PDC was provided to DLA Logistics 

Information Services (to members of the 

Federal Logistics Information System (FLIS) 

Transformation Branch). It is not known if it 

was disseminated to Component members of the 

FCC. 

2. The unit of use materiel will continue to be 

identified by NSN for requisitioning from 

DRMO, (unless that process is specifically 

modified by another DLMS change under 

DLA’s RBI initiative). 

3. Understood, but the policy deviation as 

identified in this ADC has been approved by 

Mr. Peters, Deputy Assistant Secretary of 

Defense for Supply Chain Integration. 

4. The requirement to recognize requisitioning 

at the unit of use level (by NSN with a unit of 

use indicator) is only applicable to the NavyDLA interface by agreement. If the Navy 

requires MC-managed materiel, DLA will 

submit a requisition using the FLIS unit of issue 

and upon receipt, convert and re-sell the desired 

quantity to the Navy under unit of use. 

Recommendations: 

1. DLA indicated that current DSS design could 

not employ any technique other than separate 

materiel identification values. 

2. Understood, but the policy deviation as 

identified in this ADC has been approved by 

Mr. Peters, Deputy Assistant Secretary of 
ADC 360 

Enclosure 4, Page 2 

employed whenever possible, due to the fact 

that locally assigned NSNs create challenges 

and confusion when introduced into official 

policy or SOPs. 

Defense for Supply Chain Integration. 

2. DLA PDC 360 B: Concur: 

Requires update to address Regional 

Hazardous Inventory Control System (RHICS) 

for Material Masters for Hazardous Material. 

PDC 360A: Concur 

Added 

3. USN PDC 360B: Concur 

PDC 360A: Concur 

None required. 

4. USAF PDC 360B: Concur 

PDC 360A: Concur 

None required. 

5. USTRANSCOM PDC 360B: Concur None required. 

6. IGC Comment: 

Is the reason for adding IGC to this the use of 

the 832N, the resulting impact of this change to 

their reference data feeds, or some other 

reason? 

IGC does not process the 832N, but wants to 

ensure that they accurately assess any potential 

impact before approving or abstaining. 

One of the impacts to IGC is the new data 

elements, unit of use and LSN in support of unit 

of use. It will appear in the 940R and 527R 

DLMS transactions, which IGC gets. While the 

832N is the means by which the unit of use LSN 

is established and maintained, these data 

elements will be employed in various 

MILSTRIP/ MILSTRAP transactions. IGC will 

need to be able to accommodate this kind of 

material identification, as well as accommodate 

for a unit of use, which is different from a unit 

of issue. The unit of use conversion factor tells 

you how the unit of issue converts to unit of use. 

Also, IGC may want to look at the impact to AV 

to see if there is a related impact to the IGC 

information model, since the 832N is the means 

by which the LSN, unit of use, and unit of use 

conversion factor are established/ maintained 

for a particular item. 

7. DMLSS Program, 

JMFLDC 

PDC 360B: Concur 

PDC 360A: Concur 

None required. 

8. USA PDC 360B: Concur 

PDC 360A: Concur 

None required.