DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

November 7, 2014 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

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

Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding 

DLMS 856N NOA and 870N NOA Reply (Supply/Transportation) 

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

Management System, and DLM 4000.25-1 , Military Standard Requisition and Issue Procedures 

(MILSTRIP) is approved for implementation. Phased/staggered implementation is authorized 

for these changes. Components are authorized to implement the DD Form 1348-5 enhancements 

as soon as their systems have been updated. Delayed implementation of the DLMS 856N/870N 

enhancements and routing to the ILCO is authorized until Security Cooperation Enterprise 

System (SCES) is fully fielded to all the ILCOs (estimated for January 2019). 

A<ldre::;::;ees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP Administrator, 703-

767-0676 or DSN 427-0676, e-mail: ellen.hilert@dla.mil, or Ms. Heidi Daverede, DOD 

MILS TRIP Alternate, 703-767-5111; DSN 427-5111, e-mail: heidi.daverede@dla.mil. Others 

may contact their Component designated Supply PRC representative available at: 

https://www2.dla.mil/j-6/dlmso/CertAccess/SvcPointsPOC/allpoc.asp. 

Attachment 

As stated 

cc: 

ODASD (SCI) 

7H~~Zft~~ DONALD C. PIPP 

Director 

Defense Logistics Management 

Standards Office 
Attachment, ADC 1098

Page 1

ADC 1098

Updates to DD Form 1348-5 Notice of Availability (NOA) 

and Corresponding DLMS 856N NOA and 870N NOA Reply

1. ORIGINATOR: 

a. Submitting Service/Agency: Defense Logistics Agency (DLA) J332, DSN 427-

1249/7941, Commercial 703-767-1249/7941

b. Technical POC: Heidi Daverede, DOD MILSTRIP Alternate, Defense Logistics 

Management Standards Office (DLMSO), e-mail: heidi.daverede@dla.mil 

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Security Assistance Program

b. Primary/Secondary Functional Process: NOA/Shipment

3. REFERENCES:

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

(MILSTRIP), Chapter 6, Security Assistance Program

b. DLM 4000.25, Defense Logistics Management System, Volume 2, Supply 

Procedures, Chapter 25, Security Assistance Program

c. DLM 4000.25, Defense Logistics Management System, Volume 6, Logistics 

Interoperability Support Services, Chapter 3, Military Assistance Program Address Directory

d. DTR 4500.9-R, Defense Transportation Regulation (DTR), Part II, Appendix E, 

Foreign Military Sales

4. APPROVED CHANGE(S):

a. Brief Overview of Change: Significant changes based on adjudication of comments 

received during staffing of PDC 1098 are highlighted in green.

(1) This change updates the DD Form 1348-5, Notice of Availability, to improve 

communication between the DOD and Security Cooperation (SC) customers on items requiring 

special receipt, export processing, and special storage procedures. 

(2) It also updates the DLMS 856N NOA and DLMS 870N NOA Reply to align 

with the hard copy data content of the DD Form 1348-5.
Attachment, ADC 1098

Page 2

(3) It establishes the foundation for a mechanized implementation for the NOA 

process to provide the International Logistics Control Office (ILCO) visibility, even if the NOAs 

are processed manually using the DD Form 1348-5.

(4) It updates procedures for ensuring timely replies to NOAs by actively 

engaging the ILCOs when there is no response to a follow-up NOA.

b. Background: 

(1) References 3.a., 3.b., 3.c., and 3.d. document procedures and conditions for 

notifying the designated freight forwarder/country representative (FF/CR) that materiel is ready 

for shipment. When an NOA is required and the shipment is hazardous, DOD/U.S. Government

origin shipping activities are responsible for certifying SC hazardous material shipments for 

overseas movement. The level of hazardous packaging and associated certification is based on 

the mode of transportation (e.g., air or surface) identified by the FF/CR in the NOA response. 

(2) The current DD Form 1348-5 and equivalent DLMS NOA transactions do not 

provide discrete data fields for communicating all the required information. Users of the manual 

NOA form are creating their own annotations/checkboxes to convey this information. Creating a 

special requirements section to the NOA form and modifying its current format will reduce 

errors and result in more precise communication between the DOD and the freight 

forwarder/country representative.

(3) Per DLM 4000.25-1, MILSTRIP, Chapter 6, the current definition for NOA 

Notice Number is that it will be the transportation control number (TCN) for the shipment. 

Since TCN is already a valid DLMS data element in the DLMS Dictionary and the transportation 

community uses the TCN as a key in their transportation planning processes, there is no need to 

have two different data elements conveying the same data content. 

(4) Updating the DLMS 856N and 870N with this additional information will 

enable those systems capable of electronic NOAs to transact this information systemically.

(5) Since the primary means of executing NOA procedures is manual through the 

use of the DD Form 1348-5, the ILCOs lack visibility to the NOA process. With the incremental 

fielding of Security Cooperation Enterprise System (SCES) underway, there is an opportunity to 

increase the mechanization of the NOA process by adding the ILCO to the NOA distribution by 

exchanging the DLMS 856N and 870N between the shipping activity and the ILCO, even if the 

manual DD Form 1348-5 is used.

(6) NOA Follow-up guidance requires strengthening when there is no response to 

an NOA Follow-up by actively engaging the ILCOs in the process.

c. Approved Change in Detail: 

(1) Update the DD Form 1348-5 as indicated below:

(a) Header Information – Add data fields for Origin (Routing Identifier 

Code (RIC), Origin Phone, Origin Email, Origin Fax, Origin Point of Contact (full name), NOA 
Attachment, ADC 1098

Page 3

Date, Ship-To Military Assistance Program Address Code (MAPAC), Mark-For MAPAC, 

Transportation Control Number, Delivery Term Code, Export Release Indicator (Yes or No), 

Freight Nomenclature, Water Commodity Code/Type Cargo/Special Handling, Air Commodity 

Code/Special handling/Air Dimension, Transportation Priority, Project Code, and Total 

Shipment Value (USD)

(b) Special Requirements Information – Add data fields for Hazardous 

Material Indicator (Yes or No), Explosive Indicator (Yes or No), United Nations/North 

American (UN/NA) Identification Number, Proper Shipping Name, Primary Hazard 

Class/Division, Packing Group, Department of Defense Identification Code 

(DoDIC)/International Maritime Organization (IMO) Designation, Net Explosive Weight

(NEW), Controlled Inventory Item Code (CIIC), Special Approval Number (e.g., Department of 

Transportation (DOT), Competent Authority Approval (CAA), Certification of Equivalency 

(COE))

(c) Consignee Information – Add data fields for Telephone, Country

(Geopolitical Entity, Name, and Code (GENC) and Full Name), Postal Code, Port of 

Embarkation, Port of Debarkation, Ship Mode to Final Destination (Air or Surface)

(d) Modify the following fields on the DD Form 1348-5:

1. “From” modified to “Origin Information”

2. “Notice Number” to “NOA Notice Number”

3. “Addressee” to “NOA Addressee MAPAC”

4. “Case No.” modified to “FMS Case Designator”

5. Over-dimensional measurements “Feet” modified to “Inches”

6. “Name” to “Point of Contact Name”

7. “Street” to “Street Address”

8. “State (include Zip Code)” to “State”

9. “Other Information” to “Comments/Remarks”

(e) Delete the following data fields on the DD Form 1348-5: Security 

Classification and Ammunition/Explosives Class.

(2) Use the TCN as the key controlling number for the NOA and NOA Reply. 

The NOA Notice Number is repurposed to reflect the number of times the NOA has been sent to 

the FF/CR. 
Attachment, ADC 1098

Page 4

(3) The DLMS 856N and 870N will be updated to reflect the data field 

enhancements made to the DD Form 1348-5. Upgrade the DLMS 856N to X12 Version/Release 

4030.

(4) With the fielding of SCES, a DLMS-compliant ILCO system, an opportunity 

exists to provide the ILCO visibility to the NOA process using DLMS transactions. To this end, 

shipping activities will send a DLMS 856N to the ILCO, even if a DD Form 1348-5 was sent to 

the designated notice recipient (e.g., FF/CR). To accomplish this, the ILCO (SCES) will be 

identified as a party to receive copy in the N1 segment of the DLMS 856N in Table 2 at position 

2200. The ILCO will be identified by the SC Implementing Agency Code in the first position of 

the document number. Authorized SC Implementing Agency codes are restricted to those 

identified in DLM 4000.25-1, MILSTRIP, Appendix 2.2. See sample N1 mapping below.

N101 = X6

N103 = LC

N104 = [SC Implementing Agency Code]

N106 = PK

When the ILCO is identified as a party to receive copy, DLA Transaction Services will route a 

copy of the DLMS 856N to SCES. SCES will then have the ability to associate NOA 

information with the applicable ILCO and FMS Case Designator.

(5) When a shipping activity has determined that a shipment requires a high 

degree of protection or control or the FMS Offer Release Option code is Z, the shipment must be 

held pending receipt of release and shipping instructions from the FF/CR in the form of an NOA 

Reply, either manually on the DD Form 1348-5 or mechanically using the DLMS 870N as 

documented in this ADC. 

(6) If a NOA response is not received within 15 calendar days of the NOA date, 

the shipping activity will send a follow-up to the designated NOA recipient using the same 

TCN. The follow-up will be sent either manually on the DD Form 1348-5 or mechanically using 

the DLMS 856N. The duplicate NOA will be annotated with the number 2 in the NOA Notice 

Number data field to indicate that release has been delayed due to non-response to the original 

NOA.

(a) DD Form 1348-5:

NOA Notice Number = 2 (2

nd transmission of NOA, i.e., a follow-up)

(b) DLMS 856N:

1/BSN07/0200 = D50 (Delayed)

2/REF01/1500 = K1 (NOA Notice Number)

2/REF02/1500 = 2 (first follow-up)

2/N1012200 = X6

2/N103/2200 = LC

2/N104/2200 = [SC Implementing Agency Code]

2/N106/2200 = PK
Attachment, ADC 1098

Page 5

When sending a DLMS 856N indicating a follow-up, the ILCO will be identified as a party to 

receive copy on the follow-up. For manual follow-ups using the DD Form 1348-5, two copies of 

the annotated DD Form 1348-5 (Notice of Availability/Shipment), together with the applicable 

DD Form(s) 1348-1A, DD Form(s) 250, or DD Form(s) 1149 will be held as a record of the nonresponse to the original NOA. If no response is received within 15 calendar days of the followup NOA, another follow-up either manually or using the DLMS 856N will be sent with the 

number 3 in the NOA Notice Number field to indicate that release continues to be delayed due to 

non-response to the original and follow-up NOAs. File copies will be updated to reflect the nonresponse and submission of a second follow-up. Simultaneous with the third transmission of the 

NOA (second follow-up), the appropriate ILCO will also be contacted (offline) for assistance 

and follow-up action to obtain the NOA response. Upon receipt of the third transmission of the 

DLMS 856N (second follow-up) indicating a delay and/or an offline contact from the shipping 

activity, the ILCO must intervene, on behalf of the shipping activity, to obtain a response to the 

NOA so the open shipment action can be closed. NOTE: This follow-up procedure does not 

apply to Delivery Term Code (DTC) 8 releases. DTC 8 releases involve materiel, usually 

Sensitive Arms, Ammunition and Explosives, which follow special export procedures that 

require more time to process than can be encompassed by the above follow-up procedure. 

d. Revisions to DOD 4000.25 Manuals:

(1) Update DLM 4000.25-1, MILSTRIP, Chapter 6. Refer to Enclosure 1.

(2) Update DLM 4000.25, Volume 2, Chapter 25. Refer to Enclosure 2.

(3) Update DLM 4000.25-1, MILSTRIP, Appendix 1.4, DD Form 1348-5, Notice of 

Availability/Shipment with new form layout and content. Comparable update will be made to 

DLM 4000.25, Volume 2, Appendix 6.4. Refer to Enclosure 3.

(4) Update DLM 4000.25-1, MILSTRIP, Appendices 3.30, 3.31, and 3.32. 

Comparable update will be made to DLM 4000.25, Volume 2, Appendices 8.30, 8.31, and 8.32. 

Refer to Enclosures 4 through 6.

(5) Update DLMS 856N to X12 Version 4030 and remove Version 4010 as 

authorized DLMS Implementation Conventions. Refer to Enclosure 7.

(6) Update DLMS 870N. Refer to Enclosure 7.

(7) Update DLM 4000.25, Volume 1, Appendix 2, Terms and Definitions as follows:

FOREIGN MILITARY SALES (FMS) NOTICE OF AVAILABILITY (NOA) NOTICE 

NUMBER. A unique number reflecting the number of times the NOA has been sent to the 

Freight Forwarder/Country Representative assigned to control the shipment between the 

shipper and the consignee. Each repetitive communication of the NOA will be interpreted as a 

follow-up.

e. Approved Transaction Flow: See Enclosure 8 for both manual and mechanized 

flows for the NOA process.
Attachment, ADC 1098

Page 6

f. Alternatives: None identified.

g. Proposed DLMS Change (PDC) 1098 Staffing Response/Comment Resolution:

Originator Response/Comment Disposition

DLA J5 

(7/23/2014)

Complete the DD Form 67 once coordination 

received on PDC 1098 and the DD 1348-5 is 

finalized. Provide Component, name, and 

date of concurrence and adjudication of 

comments.

Upon release of ADC 

1098, the DD Form 67 

will be submitted to DLA 

J5 with requested 

information, at which 

time DLA J5 take actions 

to formally update the 

DD 1348-5 in the DOD 

Forms Library.

Navy ILCO 

(8/12/2014)

Nonconcur. 

1. The subject change would impact the 

future SCES system and not the Navy FMS 

MISIL system. Although it sounds like a 

useful change, it is dependent on freight 

forwarder participation which can involve 

lead time and expense and close coordination 

with the customer country. In discussions of 

the SCES design, we have heard of no design 

for these DLMS transaction variants. Brent 

Pearlstein may have better information.

2. Do not agree with being the action 

activity for classified shipments.

1. If the freight forwarder 

can process these DLMS 

transactions that is a 

benefit; however, the 

procedures are written 

such that the DD Form 

1348-5 will continue to 

be used as it is today, 

albeit the form has been 

updated with additional 

data content.

2. Paragraph 4.c (4) 

rewritten to show SCES 

as a party to receive 

copy. No action required

by ILCO; provided for 

visibility purposes. 

Paragraph 7 was added 

for ILCO/SCES to 

consider a future 

enhancement wherein the 

DLMS transactions can 

be leveraged with 

country representatives, 

possibly through a 

portal/proxy server with 

SCES.
Attachment, ADC 1098

Page 7

Originator Response/Comment Disposition

Navy ILCO 

(10/27/2014)

Concur with comment based on satisfactory 

resolution of prior non-concurrence.

Noted.

Army ILCO 

(8/12/2014)

Nonconcur. Our transportation office 

consulted with the other ILCOs and is 

disagreement with the paragraph 

C25.11.1.5.3. ILCOs are not an action 

activity, nor does the ILCO respond for the 

customer.

Paragraph 4.c (4) 

rewritten to show SCES 

as a party to receive 

copy. No action required

by ILCO; provided for 

visibility purposes. 

Paragraph 7 was added 

for ILCO/SCES to 

consider a future 

enhancement wherein the 

DLMS transactions can 

be leveraged with 

country representatives, 

possibly through a 

portal/proxy server with 

SCES.

Army ILCO 

(9/26/2014)

Concur with comment. 1. The mentioning of 

SDDC when an ETRR is requested; SDDC 

ignores the ETRR request even though it is 

still in the DTR, What value does this add 

and why is SDDC shown in the NOA 

process flow? C6.11.2.3, C25.11.2.3, 

Enclosure 8.

2. Enclosure 3 -- Why/What is the Export 

Release Required on the form?

1. DLMSO is not 

authorized to modify 

published DTR 

procedures. If the ETRR 

process is no longer 

required, request that 

DSCA and the ILCOs 

send a request to 

USTRANSCOM to 

modify the DTR. When 

that change is made in 

the DTR, then DLMSO 

will update its manuals 

accordingly. 

2. The Export Release 

Required on the DD 

1348-5 is a Y/N 

indicator. If published 

DTR procedures require 

an ETRR, then indicate 

Y, otherwise, indicate N.

1.
Attachment, ADC 1098

Page 8

Originator Response/Comment Disposition

Army ILCO 

(9/26/2014)

3. They do not mention the requirement for 

material moving through Germany as 

identified in the DTR Part V; Chapter 510.7.

4. What happens if SCES goes away?

3. DLMS procedures do 

not override established 

DTR procedures. It is 

the responsibility of 

concerned parties to 

ensure compliance with 

DTR Part V.

4. Whatever system(s) 

replace SCES is (are) 

required to be DLMS 

compliant by 2019 per 

the OSD Acquisition and 

Logistics Functional 

Strategy. Components 

are required to submit 

Organization Execution 

Plans to OSD A&L 

identifying their DLMS 

migration plans. 

Air Force ILCO 

(8/12/2014)

Nonconcur. Do not agree with being the 

action activity for classified shipments.

Paragraph 4.c (4) 

rewritten to show SCES 

as a party to receive 

copy. No action required

by ILCO; provided for 

visibility purposes. 

Paragraph 7 was added 

for ILCO/SCES to 

consider a future 

enhancement wherein the 

DLMS transactions can 

be leveraged with 

country representatives, 

possibly through a 

portal/proxy server with 

SCES.
Attachment, ADC 1098

Page 9

Originator Response/Comment Disposition

Air Force ILCO 

(10/8/2014)

Concur with comment. 1. Need to ensure 

that all the impacted regulations are updated 

to reflect the same process and timeframes

for follow-ups to NOAs.

2. The ILCO's should NOT be an action 

office for answering any NOA, whether it's 

for hazardous material, over-sized material 

or classified material. The ILCO's should 

only be an INFO copy recipient for any 

NOA. The ILCO's only get involved in the 

NOA process when the FF/CR is not 

providing a timely response to the 

shipping/NOA originating organization.

3. Modify follow-up timeframe from seven 

days to 15 days.

4. Modify C25.11.1.5.3 as follows: “For 

those systems not capable of sending a 

mechanized NOA, the ILCO will be notified 

via offline methods (e.g., phone, fax, 

email).”, send a info copy NOA to the ILCO 

via offline methods (e.g., phone, fax, email).”

1. DLM 4000.25 Volume 

2, Chapter 26, Volume 6, 

Chapter 3, and DLM 

4000.25-1, Chapter 6 will 

be updated to have the 

same processing 

timeframes for followups. See Enclosures 1, 2 

and 3 for updates.

2. Paragraph 4.c (4) 

rewritten to show SCES 

as a party to receive 

copy. No action required

by ILCO; provided for 

visibility purposes. 

Paragraph 7 was added 

for ILCO/SCES to 

consider a future 

enhancement wherein the 

DLMS transactions can 

be leveraged with 

country representatives, 

possibly through a 

portal/proxy server with 

SCES. Under this 

concept the ILCO would 

still get visibility, but the 

intent is for the country 

representative to take 

action.

3. Updates made 

throughout ADC and the 

manuals.

4. Change made.
Attachment, ADC 1098

Page 10

Originator Response/Comment Disposition

Marine Corps

(8/13/2014)

Concur without comment. Noted.

Air Force 

(8/14/2014)

Concur with comment: "Recommend adding 

a POC (Full Name) to the DD FORM 1348-5 

NOTICE OF AVAILABILITY/SHIPMENT 

in the "ORIGIN INFORMATION" This will 

help to identify who to speak to if needed." 

This may be relevant given that most 

shipment actions are short term in nature. 

Added “Name:” to the 

ORIGIN INFORMATION

block of the DD 1348-5. 

See Enclosure 3.

Added a DLMS note to the 

2/PER02/2700 in the 856N 

to clarify the requirement to 

provide the full name. See 

Enclosure 7.

DLA 

(8/15/2014)

Concur without comment. Noted.

Army 

(8/25/2014)

Concur without comment. Noted.

Navy 

(9/18/2014)

Concur without comment. Noted.

USTRANSCOM

(9/23/2014)

Concur without comment. Noted.

DSCA SCES 

PMO

(10/7/2014)

Concur with comment. Regarding the role of 

the FMS/SC Transportation Plans associated 

with FMS cases in the NOA Process, the 

Transportation Plans dictate the role of the 

shipper and the country agent for receiving 

regarding the processing of NOAs for 

hazardous and classified shipments. The 

transportation plans should be reviewed for 

potential impact. It makes no sense to issue 

the DLMS change unless the Transportation 

Plans are or can be written to permit/support 

the proposed automated DLMS process.

DLMSO concurs that the 

transportation plans

should align with this 

DLMS change. In the 

interim the current 

manual NOA process can 

continue to be used, until 

such time as trading 

partners can implement 

the DLMS. 

DSCA 

(10/27/2014)

Concur with comment.

DSCA (STR/SPI) has no issues with the 

ADC as long as the Service ILCO comments 

have been satisfied.

Noted.

The Service ILCO 

questions have been 

adjudicated as indicated 

in this table.
Attachment, ADC 1098

Page 11

5. REASON FOR CHANGE: 

a. The current DD Form 1348-5 lacks discrete data fields for effective communication of 

all required information between the DOD and the SC customer. Excessive use of handwritten 

marks and annotations on the DD Form 1348-5 can lead to errors in data interpretation. 

Hazardous/explosive shipments have legal reporting requirements that are being hand scribed 

freely on the DD Form 1348-5 leading to potential critical errors in handling of these sensitive 

shipments. Block 27 of the DD Form 1348-1A is filled with data that could be moved to the 

NOA, thereby freeing it up for other information designated for that block (e.g., barcodes). 

Enhancing the DD Form 1348-5 will go a long ways to improving the data quality.

b. There is a lack of implementation of mechanized NOAs, either MILSTRIP legacy or 

DLMS, due to mechanized limitations of many FF/CRs; also the ILCOs lack visibility to the 

NOA process, as current communications are limited to the shipping activity and the FF/CR. By 

adding the ILCO to the NOA process through the use of the DLMS 856N/870N, mechanization 

of the NOA process can be expanded. This provides the ILCO visibility and automates NOA 

processing in the shipping system.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: These modifications will ensure the DOD is providing appropriate 

information to freight forwarders and country representatives to make informed decisions about 

the onward movement of their cargo and allow DOD to effectively prepare its shipments and 

accompanying documentation for movement.

b. Disadvantages: The enhancements identified for the DD Form 1348-5 and the 

DLMS 856N/870N are not compatible with the MILSTRIP Legacy NOA transactions. 

However, due to the limited implementation of the mechanized MILSTRIP Legacy NOA 

transactions, this is not a significant concern.

7. ADDITIONAL COMMENTS TO CONSIDER: As SCES continues its modernization 

efforts, a future opportunity exists to implement DLMS transaction processing between SCES,

operating as a data broker via portal/proxy server, and country representatives. If this 

opportunity comes to fruition, then in the situation where the NOA is going to a country 

representative, SCES would be identified as the action activity in the N1 segment of the DLMS 

856N in Table 2 at position 2200. The construct of the N1 segment is similar to the party to 

receive copy, with the exception of the N106 which must cite “TO” to indicate routing to SCES.

N101 = X6

N103 = LC

N104 = [SC Implementing Agency Code]

N106 = TO 

This would enable SCES to make the requirement available to the country representative for 

action, while simultaneously providing the ILCO visibility of the requirement. When the 

country representative responds in SCES with the release and shipping instructions, then SCES, 

on behalf of the country representative, can send the DLMS 870N to the shipping 
Attachment, ADC 1098

Page 12

activity/originator of the NOA. This will provide an electronic transaction to the shipper to then 

systemically process the shipment, minimizing manual entry of the paper DD Form 1348-5 

release and shipping instructions.

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Phased/staggered 

implementation is authorized for these changes. Components are authorized to implement the 

DD Form 1348-5 enhancements as soon as their systems have been updated. Delayed 

implementation of the DLMS 856N/870N enhancements and routing to the ILCO is authorized 

until SCES is fully fielded to all the ILCOs (estimated for January 2019).

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE:

a. Reduces manual annotations by the Services, Defense Agencies, and Security 

Cooperation Customers.

b. Reduces hazardous material documentation errors/reprints.

10. IMPACT:

a. New and Modified DLMS Data Elements: See Enclosure 9.

b. Automated Information Systems (AIS):

(1) Component AIS’ should be updated to produce the enhance DD Form 1348-

5, transmit the DLMS 856N, and receive the DLMS 870N.

(2) SCES should be updated to receive the DLMS 856N and transmit the DLMS 

870N. 

c. DLA Transaction Services: 

(1) DLMS 856N Mapping

(a) Upgrade from X12 Version/Release 4010 to 4030.

(b) Update map to reflect new data elements added by this DLMS 

change. Of particular note, the TCN (2/REF01/1500 Code TG) will map to rp 61-77 of the 

MILSTRIP Legacy DIC AD1, AD2, AD3, AD4, ADR. Due to a definition change documented 

by this DLMS change, what was formerly the FMS Notice Number ( rp 61-77) is renamed to the 

NOA Notice Number (2/REF01/1500 Code K1) and is a DLMS enhancement with no legacy 

mapping.

(2) DLMS 870N Mapping

(a) The IC will remain at X12 Version/Release 4010.

(b) Update map to reflect new data elements added by this DLMS 

change. 
Attachment, ADC 1098

Page 13

d. Non-DLA Logistics Management Standards Publications: 

(1) USTRANSCOM should update the DTR 4500.9R, Part II Cargo Movement, 

Appendix E, as necessary to reflect the NOA process and transaction changes documented in this 

DLMS change.

(2) Defense Security Cooperation Agency (DSCA) should update the DSCA 

5105.38-M, Security Assistance Management Manual, as necessary to align with revised NOA 

procedures.

(3) Components should update any local instructions to align with the revised 

NOA procedures. 
Enclosure 1, ADC 1098

Page 1

Enclosure 1, DLMS/MILSTRIP Manual Revision

Revise DLM 4000.25-1 MILSTRIP, Volume 2 Chapter 6 as show below (significant changes

are identified by red bold italics and double strikethrough). 

C6.11. RELEASE OF FOREIGN MILITARY SALES SHIPMENTS1

C6.11.1. General. U.S. shipping activities use the NOA to notify the designated FF/CR 

addressee and the International Logistics Control Office (ILCO) (identified by the SC 

Implementing Agency) that materiel is ready for shipment.

[Intervening text not shown]

C6.11.1.3. U.S. shipping activities use the NOA to notify the designated FF/CR 

addressee that materiel is ready for shipment. A manual NOA will be prepared for all FMS 

purchases except those customers specifically requesting mechanized NOAs such as the Federal 

Republic of Germany. Countries desiring to receive the mechanized NOA will submit a request 

to the Director, Defense Logistics Management Standards Office. All purchasers requesting the 

mechanized NOA will be identified in this paragraph. Procedures for NOA preparation are 

contained in Paragraphs C6.11.2. and C6.11.3.

C.6.11.1.4. The NOA will identify the TCN assigned to the shipment, which will be 

created in accordance with guidance in DTR 4500.9-R, Appendix L. The manual or 

mechanized NOA document will be assigned an NOA notice number to reflect the number of 

times the NOA has been sent to the FF/CR.

____________________________

1 Refer to (ADC) 1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding DLMS 

856N NOA and 870N NOA Reply.
Enclosure 1, ADC 1098

Page 2

C6.11.2. Manual Notice of Availability

C6.11.2.1. DD Form 1348-5, Notice of Availability/Shipment, will serve as a cover 

document for individual copies of DD Form 1348-1A, DD Form 250, or DD Form 1149

applicable to each line item in a shipment unit. Together, these documents will comprise the 

original NOA. The data to be entered on DD Form 1348-5 (See Appendix 1.4) are those that 

describe the shipment unit, while the supporting copies of the DD Form 1348-1A provide 

individual item data. All blocks of the DD Form 1348-5 from the top of the form to the portion 

captioned “TO BE COMPLETED BY ADDRESSEE” “CONSIGNEE INFORMATION” will 

be completed by initiating activities when the applicable shipment units are consolidated. In 

instances of single-line item shipment units, the following data are not mandatory entries on the 

DD Form 1348-5 if they are contained in the accompanying copies of the DD Form 1348-1A: 

type pack, pieces, weight, and cube. All data blocks are self-explanatory, except that the NOA 

date (the date the notice is transmitted) will be entered in the block titled “Notice of 

Availability/Shipment.” The “NOA Notice Number” reflects the number of times the NOA has 

been sent to the FF/CR. The TCN block contains represents the transportation control number, 

which is the TCN assigned to track the shipment. When an export release is required from the 

SDDC, DD Form 1348-5 will be annotated or stamped “EXPORT RELEASE REQUIRED” in 

the lower left corner. The shipping activity will also must annotate or stamp brief notes 

applicable to complete the “SPECIAL REQUIREMENTS” section for materiel discussed in 

Paragraph C6.11.1.1.3. when appropriate. The manual NOA will be mailed to the notice 

recipient specified in the MAPAD, except that the NOAs covering classified shipments will be 

forwarded to the country representative. Distribution of DD Form 1348-5 is as follows:

COPY NO. USAGE

1 Retained by the shipping activity pending receipt of shipment release 

instructions.

2, 3 Furnished to the appropriate FF/CR address (as designated in the MAPAD 

to receive the NOA) with copies of DD Form 1348-1A for insertion of 

shipment release instructions on the third copy and return to the shipping 

activity. The second copy will be retained by the FF/CR. Copies of the DD 

Form 1348-1A, DD Form 250, or DD Form 1149 will accompany the DD 

Form 1348-5.

[Intervening text not shown]

C6.11.2.3. In instances where the shipment does not require an export release or the 

shipping activity determines that there is no requirement for a high degree of protection or 

control and the FMS offer release option Y is indicated for the materiel, the shipment will be 

released to the FF/CR on the 15th calendar day after the NOA date, unless alternate shipping 

instructions are received. When an export release is required, the shipment will be held pending 

receipt of release and shipping instructions from the SDDC releasing authority, and if such 

instructions are not received within 15 calendar days after the NOA date, follow-up only to both

SDDC and the ILCO in lieu of transmitting a duplicate NOA. In instances where the shipping 

activity has determined a need for a high degree of protection or control or FMS offer release 
Enclosure 1, ADC 1098

Page 3

option Z is indicated, the shipment must be held pending receipt of release and shipping 

instructions from the FF/CR. If an NOA response is not received within 15 calendar days of 

the NOA date, the shipping activity will send a follow-up to the designated NOA recipient 

using the same TCN. The duplicate NOA will be annotated with the number 2 in the NOA 

Notice Number field to indicate that release has been delayed due to non-response to the 

original NOA. Two copies of the annotated DD Form 1348-5 (Notice of Availability/ 

Shipment), together with the applicable DD Form(s) 1348-1A, DD Form(s) 250, or DD 

Form(s) 1149 will be held as a record of the non-response to the original NOA. If no response 

is received within 15 calendar days of the follow-up NOA, another follow-up will be sent with 

the number 3 in the NOA Notice Number field to indicate that release continues to be delayed 

due to non-response to the original and follow-up NOAs. File copies will be updated to reflect 

the non-response and submission of a second follow-up. Simultaneous with the second 

follow-up, the appropriate ILCO will be contacted (offline) for assistance and follow-up action 

to obtain the NOA response. Upon receipt of the offline contact from the shipping activity, the 

ILCO must intervene, on behalf of the shipping activity, to obtain a response to the NOA so 

the open shipment action can be closed. NOTE: This follow-up procedure does not apply to 

Delivery Term Code (DTC) 8 releases. DTC 8 releases involve materiel, usually Sensitive 

Arms, Ammunition and Explosives, which follow special export procedures that require more 

time to process than can be encompassed by the above follow-up procedure. Should such 

instructions not be received within 15 calendar days after the NOA date, a duplicate of the NOA 

will be sent to the designated notice recipient, with the same shipment unit number assigned. 

This duplicate NOA will be annotated to indicate that the shipment delay is caused by the FF/CR 

failure to furnish release and shipping instructions. Two copies of DD Form 1348-5, Notice of 

Availability/Shipment, together with DD Form 1348-1A, constitute the delay NOA. The Service 

focal point will be advised of the problem for Army and Air Force sponsored shipments; the 

Navy freight forwarder assistance office will be advised for Navy and Marine Corps sponsored 

shipments.
Enclosure 2, ADC 1098

Page 1

Enclosure 2

Revise DLM 4000.25 Defense Logistics Management System, Chapter 25 as show below 

(significant changes are identified by red bold italics and double strikethrough). 

C25.11. RELEASE OF FOREIGN MILITARY SALES SHIPMENTS1

C25.11.1. General. U.S. shipping activities use the NOA to notify the designated FF/CR 

addressee and the International Logistics Control Office (ILCO) (identified by the SC 

Implementing Agency) that materiel is ready for shipment. 

[Intervening text not shown]

C25.11.1.3. U.S. shipping activities use the NOA to notify both the designated 

FF/CR addressee and the ILCO that materiel is ready for shipment. A manual NOA will be 

prepared for all FMS purchases except those customers specifically requesting mechanized 

NOAs such as the Federal Republic of Germany. Countries desiring to receive the mechanized 

NOA will submit a request to the Director, Defense Logistics Management Standards Office. 

All purchasers requesting the mechanized NOA will be identified in this paragraph. Procedures 

for NOA preparation are contained in Paragraphs C25.11.2. and C25.11.3.

C.25.11.1.4. The NOA will identify the TCN assigned to the shipment, which will 

be created in accordance with guidance in DTR 4500.9-R, Appendix L. The manual or 

mechanized NOA document will be assigned an NOA notice number to reflect the number of 

times the NOA has been sent to the FF/CR.

C25.11.1.5. ILCO Notifications.

C25.11.1.5.1. To provide the ILCO visibility to NOAs, shipping activities will 

send a DLMS 856N (No MILSTRIP Legacy DIC equivalent for this notification process) to 

the ILCO, even if a manual DD Form 1348-5 was sent to the FF/CR. 

C25.11.1.5.2. The ILCO will be identified as a party to receive copy in the 

DLMS 856N. The ILCO will be identified by the SC Implementing Agency Code in the first 

position of the document number. Authorized SC Implementing Agency codes are restricted 

to those identified in Appendix 7.2. When the ILCO is identified as a party to receive copy, 

DLA Transaction Services will route a copy of the DLMS 856N to the Security Cooperation 

Enterprise System (SCES). SCES will then have the ability to associate NOA information with 

the applicable ILCO and FMS Case Designator.

____________________

1 Refer to ADC1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding DLMS 856N 

NOA and 870N NOA Reply. DLMS implementation for SCES may be delayed until fully fielded to all the ILCOs 

(estimated for January 2019)
Enclosure 2, ADC 1098

Page 2

C25.11.1.5.3. For those systems not capable of sending a mechanized NOA, 

send an information copy of the NOA to the ILCO via offline methods (e.g., phone, fax, 

email).

C25.11.2. Manual Notice of Availability

C25.11.2.1. DD Form 1348-5, Notice of Availability/Shipment, will serve as a cover 

document for individual copies of DD Form 1348-1A, DD Form 250, or DD Form 1149

applicable to each line item in a shipment unit. Together, these documents comprise the original 

NOA. The data to be entered on DD Form 1348-5 (See Appendix 6.4) are those that describe the 

shipment unit, while the supporting copies of the DD Form 1348-1A provide individual item 

data. All blocks of the DD Form 1348-5 from the top of the form to the portion captioned “TO 

BE COMPLETED BY ADDRESSEE” “CONSIGNEE INFORMATION” will be completed by 

initiating activities when the applicable shipment units are consolidated. In instances of singleline item shipment units, the following data are not mandatory entries on the DD Form 1348-5 if 

they are contained in the accompanying copies of the DD Form 1348-1A: type pack, pieces, 

weight, and cube. All data blocks are self-explanatory, except that the NOA date (the date the 

notice is transmitted) will be entered in the block titled “Notice of Availability/Shipment.” The 

“NOA Notice Number” reflects the number of times the NOA has been sent to the FF/CR. The 

TCN block contains represents the transportation control number, which is the TCN assigned to 

track the shipment. When an export release is required from SDDC, DD Form 1348-5 will be 

annotated or stamped “EXPORT RELEASE REQUIRED” in the lower left corner. The shipping 

activity will also must annotate or stamp brief notes applicable to complete the “SPECIAL 

REQUIREMENTS” section for materiel discussed in Paragraph C25.11.1.1.3. when 

appropriate. The manual NOA will be mailed to the notice recipient specified in the MAPAD, 

except that the NOAs covering classified shipments will be forwarded to the country 

representative. Distribution of DD Form 1348-5 is as follows:

COPY NO. USAGE

1 Retained by the shipping activity pending receipt of shipment release 

instructions.

2, 3 Furnished to the appropriate FF/CR address (as designated in the MAPAD 

to receive the NOA) with copies of DD Form 1348-1A, for insertion of 

shipment release instructions on the third copy and return to the shipping 

activity. The second copy will be retained by the FF/CR. Copies of the DD 

Form 1348-1A, DD Form 250, or DD Form 1149 will accompany the DD 

Form 1348-5.

[Intervening text not shown]

C25.11.2.3. In instances where the shipment does not require an export release or the 

shipping activity determines that there is no requirement for a high degree of protection or 

control and the FMS offer release option Y is indicated for the materiel, the shipment will be 

released to the FF/CR on the 15th calendar day after the NOA date, unless alternate shipping 

instructions are received. When an export release is required, the shipment will be held pending 
Enclosure 2, ADC 1098

Page 3

receipt of release and shipping instructions from the SDDC releasing authority, and if such 

instructions are not received within 15 calendar days after the NOA date, follow-up only to both

SDDC and the ILCO in lieu of transmitting a duplicate NOA. In instances where the shipping 

activity has determined a need for a high degree of protection or control or FMS offer release 

option Z is indicated, the shipment must be held pending receipt of release and shipping 

instructions from the FF/CR. If an NOA response is not received within 15 calendar days of 

the NOA date, the shipping activity will send a follow-up to the designated NOA recipient 

using the same TCN. The duplicate NOA will be annotated with the number 2 in the NOA 

Notice Number field to denote the second communication of the NOA and to indicate that 

release has been delayed due to non-response to the original NOA. Two copies of the 

annotated DD Form 1348-5 (Notice of Availability/ Shipment), together with the applicable 

DD Form(s) 1348-1A, DD Form(s) 250, or DD Form(s) 1149 will be held as a record of the 

non-response to the original NOA. If no response is received within 15 calendar days of the 

follow-up NOA, another follow-up will be sent with the number 3 in the NOA Notice Number 

field to indicate that release continues to be delayed due to non-response to the original and 

follow-up NOAs. File copies will be updated to reflect the non-response and submission of a 

second follow-up. Simultaneous with the second follow-up, the appropriate ILCO will be 

contacted (offline) for assistance and follow-up action to obtain the NOA response. Upon 

receipt of the offline contact from the shipping activity, the ILCO must intervene, on behalf of 

the shipping activity, to obtain a response to the NOA so the open shipment action can be 

closed. NOTE: This follow-up procedure does not apply to Delivery Term Code (DTC) 8 

releases. DTC 8 releases involve materiel, usually Sensitive Arms, Ammunition and 

Explosives, which follow special export procedures that require more time to process than can 

be encompassed by the above follow-up procedure. Should such instructions not be received 

within 15 calendar days after the NOA date, a duplicate of the NOA will be sent to the 

designated notice recipient, with the same shipment unit number assigned. This duplicate NOA 

will be annotated to indicate that the shipment delay is caused by the FF/CR failure to furnish 

release and shipping instructions. Two copies of DD Form 1348-5, Notice of 

Availability/Shipment, together with DD Form 1348-1A, constitute the delay NOA. The Service 

focal point will be advised of the problem for Army and Air Force sponsored shipments; the 

Navy freight forwarder assistance office will be advised for Navy and Marine Corps sponsored 

shipments.
Enclosure 3, ADC 1098

Page 1

Enclosure 3

Revise DLM 4000.25 Defense Logistics Management System, Volume 6, Chapter 3 as show 

below (significant changes are identified by red bold italics and double strikethrough). 

(NOTE: The paragraph numbering is based on the MAPAD update being staffed under PDC 

1053).

C3.17.4. When the FMS Offer/Release Code Option is Z, an NOA will be forwarded to the 

TAC 3 address, or country representative if the shipment is classified. However, the shipment 

must not be released until a response from the proper NOA addressee is received. If no response 

has been received in 15 calendar days, a follow up must be sent. If no response is received 

within 15 calendar days of the follow-up, a second follow-up must be sent and assistance must 

be requested from the appropriate DoD Component Security Assistance/Cooperation Agency. If 

an NOA response is not received within 15 calendar days of the NOA date, the shipping 

activity will send a follow-up to the designated NOA recipient using the same TCN. The 

duplicate NOA will be annotated with the number 2 in the NOA Notice Number field to denote 

the second communication of the NOA and to indicate that release has been delayed due to 

non-response to the original NOA. Two copies of the annotated DD Form 1348-5 (Notice of 

Availability/ Shipment), together with the applicable DD Form(s) 1348-1A, DD Form(s) 250, 

or DD Form(s) 1149 will be held as a record of the non-response to the original NOA. If no 

response is received within 15 calendar days of the follow-up NOA, another follow-up will be 

sent with the number 3 in the NOA Notice Number field to indicate that release continues to 

be delayed due to non-response to the original and follow-up NOAs. File copies will be 

updated to reflect the non-response and submission of a second follow-up. Simultaneous with 

the second follow-up, the appropriate ILCO will be contacted (offline) for assistance and 

follow-up action to obtain the NOA response. Upon receipt of the offline contact from the 

shipping activity, the ILCO must intervene, on behalf of the shipping activity, to obtain a 

response to the NOA so the open shipment action can be closed. NOTE: This follow-up 

procedure does not apply to Delivery Term Code (DTC) 8 releases. DTC 8 releases involve 

materiel, usually Sensitive Arms, Ammunition and Explosives, which follow special export 

procedures that require more time to process than can be encompassed by the above follow-up 

procedure. Note that Option Release Code Z procedures must be followed if any unusual 

transportation factors apply. This includes oversize or overweight shipments, hazardous materiel 

shipments, classified shipments, sensitive shipments and ammunition, arms and explosives 

shipments, or any other factor that mandates coordinated release procedures (this does include 

Canada).

 
Enclosure 4, ADC 1098

Page 1

Enclosure 4

Replace DLM 4000.25-1 MILSTRIP, Appendix 1.4 and DLM 4000.25, Volume 2, Appendix 

6.4 with new form below. 

DD FORM 1348-5,

NOTICE OF AVAILABILITY/SHIPMENT

NOTICE OF

AVAILABILITY/SHIPMENT

ORIGIN INFORMATION

RIC:

PHONE:

NAME:

RETURN COMPLETED FORM TO

EMAIL: 

FAX:

NOA DATE

NOA NOTICE NUMBER

NOA ADDRESSEE MAPAC SHIP TO MAPAC MARK FOR MAPAC SECURITY COOPERATION 

CUSTOMER CODE

TRANSPORTATION CONTROL NUMBER # OF LINE ITEMS (DD 1348-1/DD 250) DELIVERY TERM 

CODE

FMS CASE

DESIGNATOR

EXPORT RELEASE REQUIRED 

(Y OR N)

FREIGHT NOMENCLATURE WATER COMMODITY DATA

COMMODITY CODE:

TYPE CARGO CODE:

SPECIAL HANDLING CODE:

AIR COMMODITY DATA

COMMODITY CODE:

SPECIAL HANDLING CODE:

AIR DIMENSION CODE:

TRANSPORTATION 

PRIORITY

PROJECT CODE TYPE PACK PIECES WEIGHT 

(POUNDS)

CUBE

(CUBIC FT)

TOTAL SHIPMENT VALUE (USD)

OVER-DIMENSIONAL INFORMATION:

LENGTH (INCHES) WIDTH (INCHES) HEIGHT (INCHES) WEIGHT (POUNDS)

SPECIAL REQUIREMENTS:

HAZMAT (Y OR N) EXPLOSIVE (Y OR N) UN/NA ID NUMBER

PROPER SHIPPING NAME PRIMAY HAZARD CLASS / DIVISION PACKING GROUP

DODIC NET EXPLOSIVE WEIGHT (POUNDS) SPECIAL APPROVAL NUMBER 

(DOT/CAA/COE)

CONTROLLED INVENTORY ITEM 

CODE

CONSIGNEE INFORMATION:

(To be completed by the Freight Forwarder/Security Cooperation Representative)

POINT OF CONTACT NAME STREET ADDRESS TELEPHONE

CITY STATE COUNTRY (GENC AND FULL NAME) POSTAL CODE

PORT OF EMBARKATION 

(POE)

PORT OF DEBARKATION 

(POD)

SHIP MODE TO FINAL DESTINATION 

(AIR OR SURFACE)

COMMENTS/REMARKS
Enclosure 5, ADC 1098

Page 1

Enclosure 5

Revise DLM 4000.25-1 MILSTRIP, Appendix 3.30 and DLM 4000.25, Volume 2, Appendix 8.30. 

Changes are annotated in red, bold italics; deletions are indicated by a double strike-through.

FOREIGN MILITARY SALES NOTICE OF 

AVAILABILITY KEY DOCUMENT

AP3.30.1. The mechanized foreign military sales (FMS) notice of availability (NOA) is 

provided to customers Freight Forwarders/Country Representatives having a need to receive 

mechanized data for FMS shipments when FMS offer release option Y or Z is entered in rp 46 of 

requisitions. This FMS NOA Key document will accompany the FMS NOA detail documents.

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier 

Code

1-3 a. Enter DIC AD1 for the initial key NOA document 

when an export release is not required.

b. Enter DIC ADR for the initial key NOA document 

when an export release is required.

c. Enter DIC AD3 for the delay key NOA document.

Routing Identifier Code 4-6 Enter the RIC of the activity transmitting the NOA.

Number of Line Items 7-10 Enter the number of line items included in the 

shipment unit as represented by NOA detail documents 

transmitted with the NOA key document.

Commodity/Cargo 

Exception/Special 

Handling

11-17 a. Rp 11-15 will always contain the appropriate water 

commodity and cargo exception code to be used to 

describe the predominant commodity within the 

shipment unit for ocean manifesting. (See DTR 

4500.9-R, “Defense Transportation Regulation”) 

b. Rp 16-17 will always contain the appropriate air 

commodity and special handling code to be used for all 

shipments via air. Identifies materiel for manifesting 

and customs requirements and denotes cargo requiring 

special handling or reporting (see DTR 4500.9-R).

Air Dimension 18 Identifies dimensional characteristics of air shipments 

by relating the dimensions of the largest piece to the 

minimum size cargo door opening of an aircraft (see 

DTR 4500.9-R).

Security Cooperation 

Customer Code

19-20 Enter SC Customer Code.

Blank 21-22 Leave blank.
Enclosure 5, ADC 1098

Page 2

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Mode of Shipment 23 Identifies the intended mode to be used from shipping 

activity to designated consignee.1

Type of Pack 24-25 Identifies the type of pack code used for the shipment 

unit2.

Pieces 26-29 Enter total pieces in shipment unit.

Weight 30-35 Enter total weight of shipment unit. This entry will be 

rounded to the next whole number.

Cube 36-39 Enter total cubic feet of shipment unit. This entry will 

be rounded to the next whole number.

Blank 40-44 Leave blank.

Supplementary Address 45-50 Enter data same as the issue release/receipt document 

(MRO, DD Form 1348-1A, DD Form 1348-2, etc).

Blank 51-52 Leave blank.

Transportation Priority 53 See DTR 4500.9-R.

Blank 54-56 Enter data same as the issue release/receipt document 

(materiel release order (MRO), DD Form 1348-1A, 

DD Form 1348-2, etc).

Project Code 57-59 Enter the same project code as the issue release/receipt 

document (MRO, DD Form 1348-1A, DD Form 1348-

2, etc).

Blank 60 Leave blank.

FMS Notice

Transportation Control

Number3

61-77 Identifies the number assigned to the shipment that 

controls the shipment from shipper to consignee. See 

DLM 4000.25-1, Chapter 6, Paragraph C6.11.

Date of Offer 78-80 a. For DICs AD1, ADR, and AD3 documents, enter 

the ordinal day the initial NOA is transmitted.

b. When new NOAs are prepared, because the original 

NOA contained items that were rejected, the date of 

offer will be the transmission date of the NOA.

 

1 Refer to the TRDM for available code list at https://trdm.c2.amc.af.mil/trdm/index.jsp (DTR Data).

2

Ibid.

3 Refer to (ADC) 1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding DLMS 

856N NOA and 870N NOA Reply. 
Enclosure 6, ADC 1098

Page 1

Enclosure 6

Revise DLM 4000.25-1 MILSTRIP, Appendix 3.31 and DLM 4000.25, Volume 2, Appendix 8.31. 

Changes are annotated in red, bold italics; deletions are indicated by a double strike-through.

FOREIGN MILITARY SALES NOTICE OF 

AVAILABILITY DETAIL DOCUMENT

AP3.31.1. The mechanized foreign military sales (FMS) notice of availability (NOA) detail 

document will be prepared from the issue release/receipt documents (materiel release order 

(MRO), DD Form 1348-1A, and DD Form 1348-2) contained in the shipment unit and shall 

accompany the FMS NOA key document.

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier Code 1-3 a. Enter DIC AD2 for the initial detail NOA 

document.

b. Enter DIC AD4 for the delay detail NOA 

document.

Routing Identifier Code 4-6 Enter the RIC of the activity transmitting the NOA.

Media and Status 7 Enter the same M&S code as the issue release/receipt 

document (MRO, DD Form 1348-1A, DD Form 

1348-2).

Stock or Part Number 8-22 Enter the stock or part number of the item supplied.

Unit of Issue 23-24 Enter data same as the issue release/receipt document 

(MRO, DD Form 1348-1A, DD Form 1348-2).

Quantity 25-29 a. Enter data same as the issue release/receipt 

documents (MRO, DD Form 1348-1A, DD Form 

1348-2).

b. For ammunition and ammunition related items 

only (items in Federal Supply Group (FSG) 13 and for 

Federal Supply classification (FSC) 1410, 1420, 1427, 

1440, 5330, 5865, 6810 or 8140), enter an “M” in rp 

29 to express in thousands any quantity exceeding 

99,999. Example: Express a quantity of 1,950,000 as 

1950M (1950 in rp 25-28 and an “M” in rp 29).

Document Number 30-43 Enter data same as the issue release/receipt document 

(MRO, DD Form 1348-1A, DD Form 1348-2).

Suffix 44 Enter data same as the issue release/receipt document 

(MRO, DD Form 1348-1A, DD Form 1348-2).
Enclosure 6, ADC 1098

Page 2

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Supplementary Address 45-50 Enter data same as the issue release/receipt document 

(MRO, DD Form 1348-1A, DD Form 1348-2).

Blank 51-53 Leave blank.

Required Delivery 

Date/Required 

Availability Date

54-56 Enter data same as the issue release/receipt document 

(MRO, DD Form 1348-1A, DD Form 1348-2).

Project 57-59 Enter data same as the issue release/receipt document 

(MRO, DD Form 1348-1A, DD Form 1348-2).

Blank 60 Leave blank.

Foreign Military Sales 

Notice Transportation 

Control Number1

61-77 Enter data same as rp 61-77 of the initial FMS NOA 

key document.

Date of Offer 78-80 a. For DIC AD2 and DIC AD4 documents, enter the 

ordinal day the initial NOA is transmitted.

b. When new NOAs are prepared because the original 

NOA contained items that were rejected, the date of 

offer shall be the transmission date of the new NOA. 

_____________________

1 Refer to (ADC) 1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding DLMS 

856N NOA and 870N NOA Reply.
Enclosure 7, ADC 1098

Page 1

Enclosure 7

Revise DLM 4000.25-1 MILSTRIP, Appendix 3.32 and DLM 4000.25, Volume 2, Appendix 8.32. 

Changes are annotated in red, bold italics; deletions are indicated by a double strike-through.

FOREIGN MILITARY SALES NOTICE OF 

AVAILABILITY REPLY DOCUMENT

AP3.32.1. The mechanized foreign military sales (FMS) notice of availability (NOA) reply document 

is always be used when replying to a mechanized NOA. When shipment release is to be made to the 

addresses identified by coded entries in the requisition and the DLM 4000.25 Volume 6, Chapter 3 

(Military Assistance Program Address Directory (MAPAD)), the DIC AD5 shall contain the shipment 

release code (SRC) R in rp 60. When shipment release is to be made to an address that is not coded 

or contained in the MAPAD, the DI AD5 shall contain SRC E in rp 60.

FIELD LEGEND

RECORD

POSITION(S) ENTRY AND INSTRUCTIONS

Document Identifier Code 1-3 Enter DIC AD5.

Routing Identifier Code through 

Cube

4-39 Enter data same as rp 4-39 of initial or delay 

FMS NOA key document.

Customer Transportation Order 

Number

40-44 When customer (CR/FF) assigns a number for 

internal control of shipments, the number shall 

be entered in these columns.

Other Fields 45-59 Enter data same as rp 45-59 of initial or delay 

FMS NOA key document.

Shipment Release 60 Enter codes as follows:

a. Enter R when shipment to be released to 

appropriate ship-to address contained in the 

MAPAD as identified by address codes in the 

FMS requisition.

b. Enter E when release instructions are being 

mailed under separate cover on the date of this 

reply.

FMS Notice Transportation 

Control Number1

61-77 Enter data same as rp 61-77 of initial or delay 

FMS NOA key document.

Date of Reply 78-80 Enter ordinal day reply to NOA is transmitted.

_____________________

1 Refer to (ADC) 1098, Updates to DD Form 1348-5 Notice of Availability (NOA) and Corresponding DLMS 

856N NOA and 870N NOA Reply.
Enclosure 8, ADC 1098

Page 1

Enclosure 8, DLMS Implementation Convention (IC) Revisions

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1098 to DLMS Introductory Note 5:

- ADC 1098, Updates to DD Form 1348-5 Notice of Availability 

(NOA) and Corresponding DLMS 856N NOA and 870N NOA 

Reply

Identifies DLMS

Changes included in the

DLMS IC.

2. DLMS 

Introductory 

Notes

Modify DLMS Introductory Note 3:

3. Users operating under the Defense Logistics Management 

Standards (DLMS) must reference the Unit of Issue and Purchase 

Unit Conversion Table, Transportation Mode of Shipment 

Conversion Table, and the Accounting Classification Appendix,

which can be found on the Defense Logistics Management 

Standards Office Web site at http://www.dla.mil/j-6/dlmso.

Add reference to 

Transportation Mode 

of Shipment 

Conversion Table

3. DLMS 

Introductory 

Notes

Add new DLMS Introductory Note 4e:

4e. Data associated with a DLMS enhancement authorized for 

implementation by modernized systems under DLMS migration. 

This data (including expanded field sizes) should be adopted 

during, or subsequent, to modernization when applicable to the 

Component’s business process. Prior coordination is not required. 

Components should ensure that inclusion of this data in a DLMS 

transaction does not cause inappropriate rejection of the 

transaction.

Add authorization for 

modernized systems to 

implement.

4. 1/ST02/0100 Move Federal Note to DLMS Note: Administrative update.

5. 1/BSN02/0200 Move Federal Note to DLMS Note: Administrative update.

6. 1/BSN03/0200 Move Federal Note to DLMS Note: Administrative update.

7. 1/BSN04/0200 Move Federal Note to DLMS Note: Administrative update.

8. 1/BSN07/0200 Move Federal Note to DLMS Note: Administrative update.

9. 2/HL/0100 Move Federal Note to DLMS Note, renumber, and revise:

Federal DLMS Note:

1. The transaction set hierarchical data structure is address

information, followed by overall shipment attributes, followed by 

shipment line item detail.

2. Use the first 2/HL/0100 loop iteration to provide transaction set 

address information.

DLMS Note:

3. Use the second a single or multiple 2/HL/0100 shipment loop 

iteration to identify shipment information associated with the

attributes associated with a single FMS notice transportation 

control number (TCN) assigned to control the shipment.

4. Use a single or multiple 2/HL/0100 line item loop iterations to 

identify the line item detail associated with each shipment.

Administrative update 

to move Federal notes 

to DLMS notes.

TCN has been added 

as a discrete data 

element to the NOA 

and therefore is the 

control number for the 

shipment.
Enclosure 8, ADC 1098

Page 2

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

10. 2/HL01/0100 Move Federal Note to DLMS Note:

Federal DLMS Note: In the first 2/HL/0100 loop iteration, cite 

numeric 1. In each subsequent loop iteration, increase incrementally 

by 1.

Administrative update.

11. 2/HL02/0100 Move Federal Note to DLMS Note:

Federal DLMS Note: 

1. Use for each 2/HL/0100 line item loop iteration to identify the

shipment loop associated with each line item.

2. Data element content is the sequential number assigned to the 

2/HL/0100 shipment loop iteration and serves as the cross-reference 

between the shipment and all line items contained in the shipment.

Administrative update.

12. 2/LIN/0200 Move Federal Note to DLMS Note:

Federal DLMS Note: 

Must use only in 2/HL/0100 line item loops to identify the materiel 

included in the shipment.

Administrative update.

13. 2/LIN02/0200 Delete Federal Note: Administrative update.

14. 2/SN1/0300 Move Federal Note to DLMS Note:

Federal DLMS Note

Must use only in 2/HL/0100 line item loops to identify the number 

of units associated with each transaction.

Administrative update.

15. 2/SN102/0300 Move Federal Note to DLMS Note: Administrative update.

16. 2/SN103/0300 Move Federal Note to DLMS Note and renumber:

Unit or Basis for Measurement Code

Federal DLMS Note:

1. Use to identify the unit of issue for the materiel.

DLMS Note:

2. DLMS users see the Unit of Issue and Purchase Unit Conversion 

Table.

All valid standard codes are used.

Administrative update.

Only codes listed in the 

Unit of Issue and 

Purchase Unit 

Conversion Table are 

authorized for use.

17. 2/MEA/0800 Move Federal Note to DLMS Note and Revise:

DLMS Note:

1. Use only in 2/HL/0100 shipment loops. Use two repetitions to 

identify shipment, weight and cube.

2. If the shipment is over-dimensional, use three additional 

repetitions to identify the physical dimensions (height, length and 

width) of the shipment. 

3. If the shipment is explosive, use an additional repetition to 

identify the Net Explosive Weight in pounds.

4. Use of the MEA segment to identify dimensions for overdimensional shipments and Net Explosive Weight are an 

authorized DLMS enhancement; see DLMS Introductory Note 4e. 

Refer to ADC 1098.

Add business rules for 

identifying information 

related to overdimensional and/or 

explosive shipments.
Enclosure 8, ADC 1098

Page 3

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

18. 2/MEA01/0800 Open MEA01, add Qualifier NX and PD and associated DLMS 

Notes:

NX Net Explosive Weight

DLMS Note: For explosive shipments, use to identify the Net 

Explosive Weight in the MEA03 and MEA04-01 Code LB. 

PD Physical Dimensions

DLMS Note: For over-dimensional shipments, use to identify the 

physical dimensions (height, length, and width) of the shipment in 

the MEA02, MEA03, and MEA04-01 Code IN.

Support identification 

of measurements 

associated with overdimensional and 

explosive shipments.

19. 2/MEA02/0800 Add Qualifiers LN, WD, and HT with associated DLMS Note:

HT Height

DLMS Note: Use to identify the height in inches of an overdimensional shipment.

LN Length

DLMS Note: Use to identify the length in inches of an overdimensional shipment.

WD Width

DLMS Note: Use to identify the width in inches of an overdimensional shipment.

Support identification 

of measurements 

associated with overdimensional 

shipments.

20. 2/MEA03/0800 Move Federal Note to DLMS Note and Revise:

Measurement Value

Federal DLMS Note: Use to identify the actual number of pounds,

inches, pieces, or cubic feet, associated with the shipment based on 

the coding in MEA02 and MEA04-01.

Administrative update.

21. 2/MEA04-

01/0800

Add Data Element Level DLMS Note and Qualifier IN with code 

level DLMS Note:

DLMS Note: For DLMS use, only the following codes are 

authorized.

IN Inch

DLMS Note: Use with MEA01 Code PD and MEA02 Codes HT, 

LN, and WD.

Support identification 

of measurements 

associated with overdimensional 

shipments.

22. 2/MEA04-

01/0800

Modify DLMS Note for Qualifier LB:

LB Pound

DLMS Note:

1. Use with code A in MEA02 to indicate that the shipment weight 

is expressed as pounds.

2. Use with code NX in MEA01 to indicate that the shipment net 

explosive weight is expressed in pounds.

Support identification 

of measurements 

associated with 

explosive shipments.
Enclosure 8, ADC 1098

Page 4

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

23. 2/TD1/1100 Move Federal Note to DLMS Note:

Federal DLMS Note: Use only in 2/HL/0100 shipment loops.

Administrative

24. 2/TD102/1100 Move Federal Note to DLMS Note Administrative

25. 2/TD105/1100 Open TD105 and add DLMS Note:

Lading Description

DLMS Note: Use to identify the freight nomenclature. 

Authorized DLMS enhancement; see DLMS Introductory Note 4e. 

Refer to ADC 1098.

Add capability to pass 

the freight 

nomenclature.

26. 2/TD5/1200 Move Federal Note to DLMS Note:

Federal DLMS Note: Use only in 2/HL/0100 shipment loops to 

identify the intended mode of shipment between the shipping 

activity and designated consignee.

Administrative

27. 2/TD504/1200 Move Federal Note to DLMS Note and renumber: Administrative

28. 2/REF/1500 Revise DLMS Note 1:

1. Use in 2/HL/0100 shipment loops to indicate the number of line

items included in the shipment and the FMS Notice Transportation 

Control Number identification number controlling the shipment.

TCN is added as a 

discrete data element 

to the NOA and 

therefore is the control 

number for the 

shipment.

29. 2/REF01/1500 Delete Federal Note Administrative

30. 2/REF01/1500 Modify DLMS Note for Qualifier K1:

K1 Foreign Military Sales Notice Number

DLMS Note:

Must use only in 2/HL/0100 shipment loops to identify the NOA 

Notice Number, which reflects the number of times the NOA has 

been sent to the Freight Forwarder/Country Representative

identify the number assigned to control the shipment between the 

shipper and consignee. Second and subsequent transmissions may 

be interpreted as follow-ups. Authorized DLMS enhancement; see 

DLMS Introductory Note 4e. Refer to ADC 1098.

TCN was already in 

the NOA, but was 

identified as the NOA 

Notice Number. With 

this DLMS change the 

NOA Notice Number 

is redefined to reflect 

the number of times 

the NOA has been sent 

to the FF/CR. The 

TCN is separately 

identified in another 

REF segment with 

Qualifier TG.

31. 2/REF01/1500 Add Qualifier TG and DLMS Note:

TG Transportation Control Number (TCN)

DLMS Note: Must use only in 2/HL/0100 shipment loops to 

identify the number assigned to control the shipment between the 

shipper and consignee.

TCN is added as a 

discrete data element 

to the NOA and 

therefore is the control 

number for the 

shipment.
Enclosure 8, ADC 1098

Page 5

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

32. 2/LH1/1520 Open LH1 Loop and add DLMS Note:

DLMS Note: Use only in 2/HL/0100 shipment loops for 

hazardous/explosive shipments. Use the LH1 loop to identify the 

hazardous characteristics of the shipment. Repeat the LH1 loop 

as required identifying the hazardous characteristics associated 

with the quantity of pieces of the lading commodity. Authorized 

DLMS enhancement; see DLMS Introductory Note 4e. Refer to 

ADC 1098.

Add capability to 

identify the hazardous 

characteristics 

associated with the 

shipment.

33. 2/LH101/1520 Open LH101 and add DLMS Note:

Unit or Basis for Measurement Code

DLMS Note:

1. Use to identify the type of packaging related to the quantity in 

the LH102.

2. DLMS users see the Unit of Issue and Purchase Unit 

Conversion Table.

34. 2/LH102/1520 Open LH102 and add DLMS Note:

Lading Quantity

DLMS Note: Use to identify the number of pieces of the lading 

commodity that is hazardous in the shipment.

35. 2/LH103/1520 Open LH103 and add DLMS Note:

UN/NA Identification Code

DLMS Note: Use to identify the United Nations/North America 

hazardous material identification number as required by 49 CFR.

36. 2/LH110/1520 Open LH110 and add DLMS Note:

Packing Group Code

DLMS Note: Indicate the required packing group using Roman 

Numeral I, II, or III to indicate the degree of danger. Source is 49 

CFR Table 172.101.

37. 2/LH2/1530 Open the LH2 and add Segment Level DLMS Note:

DLMS Note: Authorized DLMS enhancement; see DLMS 

Introductory Note 4e. Refer to ADC 1098.

38. 2/LH201/1530 Open the LH201 and add DLMS Note:

Hazardous Classification

DLMS Note: Use to identify the primary hazard class or division 

for the hazardous material as shown in column 3 of 49 CFR Table 

172.101. If there is no hazard class or division, use the code in 

that column, such as ORM-D (Other Regulated Material), 

reference 49 CFR 173.2. 
Enclosure 8, ADC 1098

Page 6

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

39. 2/LH3/1540 Open the LH3 and add Segment level DLMS Note:

DLMS Note: 

1. Mandatory for all hazardous material shipments, including 

ammunition and explosives.

2. Create additional LH3 segment(s) for the remainder of the 

Proper Shipping Name exceeding 25 characters in the LH301.

3. Authorized DLMS enhancement; see DLMS Introductory Note 

4e. Refer to ADC 1098.

40. 2/LH301/1540 Open the LH301 and add DLMS Note:

Hazardous Material Shipping Name

DLMS Note: Use to identify the Proper Shipping Name.

41. 2/LH302/1540 Open the LH302 and add Qualifiers C, D, and I and data element 

level DLMS Note:

Hazardous Material Shipping Name Qualifier

DLMS Note: Use one of the following codes to describe the Proper 

Shipping Name.

C Canadian Shipping Name

D Domestic (United States) Shipping Name

I International Shipping Name

42. 2/LHR/1590 Open LHR and add Segment Level DLMS Note:

DLMS Note:

1. Use this segment to identify applicable transportation approval 

authorities for hazardous/explosives shipments.

2. Use this segment to identify the DODIC for 

ammunition/explosive shipments.

3. Authorized DLMS enhancement; see DLMS Introductory Note 

4e. Refer to ADC 1098.
Enclosure 8, ADC 1098

Page 7

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

43. 2/LHR01/1590 Open LHR01, add Qualifiers 1I, HA, HE, and HN and associated 

DLMS Notes:

1I Department of Defense Identification Code (DODIC)

DLMS Note: Use to identify the DODIC of the ammunition or 

explosive.

HA Competent Authority

DLMS Note: 

1. Use to identify the Competent Authority Approval Number

(CAA) issued by the Department of Transportation.

2. The approval number format is CA-YYNNNNA, where YY=last 

two positions of year, N=approval number within that year, and 

A=optional alphanumeric designator.

3. This is only applicable when DoD requires an exception to the 

international performance oriented packaging rules.

HE Hazardous Exemption Number

DLMS Note: 

1. Use to identify the Department of Transportation Exemption 

(DOT-E) Number.

2. This identifies the DOT-E exemption to any of the 49 CFR 

regulations for hazardous materials.

3. Normally used for domestic shipments. Can be used for 

international shipments, but is not guaranteed to be accepted by 

international customs.

HN Hazardous Certification Number

DLMS Note: 

1. Use to identify the Certification of Equivalency (COE).

2. This identifies the DoD approval when packaging design differs 

from the prescribed regulations in 49 CFR. It certifies that the 

proposed packaging design equals or exceeds the comparable 

requirements of 49 CFR for the commodity being shipped.

44. 2/LHR02/1590 Open LHR02:

Reference Identification

45. 2/DTM/2000 Move Federal Note to DLMS Note

Federal DLMS Note: Use in 2/HL/0100 shipment and line item 

loops to identify dates associated with the NOA.

Administrative
Enclosure 8, ADC 1098

Page 8

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

46. 2/N1/2200 Move Federal Note to DLMS Note and Revise:

DLMS Note:

1. Use the 2/N1/2200 loop in the 2/HL/010 address loop to identify 

the organization originating the transaction set and the organization 

to receive the transaction set.

2. Use additional repetitions of the 2/N1/2200 loop to identify the 

consignor, ship-to, and mark-for activities. Authorized DLMS 

enhancement; see DLMS Introductory Note 4e. Refer to ADC 

1098.

Add capability to 

separately identify the 

consignor, ship to, and 

mark for activities.

47. 2/N101/2200 Delete Federal Note and revise DLMS note 1:

DLMS Note: 

1. Use only one of codes 98 IF or CY.

Administrative

48. 2/N101/2200 Change Qualifier 98 to IF:

98 Freight Management Facilitator

IF International Freight Forwarder

DLMS Note:

Use to identify the designated FF to receive the transaction set.

49. 2/N101/2200 Revise DLMS note with existing Qualifier CI:

CI Consignor

DLMS Note:

1. Use as needed to identify the shipping activity.

2. In the PER segment, provide the consignor contact information.

50. 2/N101/2200 Add Qualifiers ST, X6, and Z7 with DLMS Notes:

ST Ship To

DLMS Note: Use to identify the Ship-To MAPAC. Authorized 

DLMS enhancement; see DLMS Introductory Note 4e. Refer to 

ADC 1098.

X6 International Organization

DLMS Note: Use to identify the International Logistics Control 

Office (ILCO) serving as the SC Implementing Agency for the 

shipment. The ILCO is identified by the SC Implementing 

Agency Code in the first position of the document number; 

authorized values are restricted to those identified in DLM 

4000.25, Volume 2 Appendix 7.2. Authorized DLMS 

enhancement; see DLMS Introductory Note 4e. Refer to ADC 

1098.

Z7 Mark-For Party

DLMS Note: Use to identify the Mark for MAPAC. Authorized 

DLMS enhancement; see DLMS Introductory Note 4e. Refer to 

ADC 1098.
Enclosure 8, ADC 1098

Page 9

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

51. 2/N103/2200 Revise DLMS note for Qualifier A2 and add Qualifier LC and 

associated DLMS note:

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to indicate the SA Security Assistance structured address data 

which that identifies the CR/FF to receive the NOA, the Ship To, 

and the Mark For. Interpretation of this data may require 

additional codes cited elsewhere in the transaction.

LC Agency Location Code (US Government)

DLMS Note:

Use to identify the International Logistics Control Office (ILCO) 

SC Implementing Agency Code. Authorized values are restricted 

to those identified in DLM 4000.25, Volume 2 Appendix 7.2. 

Authorized DLMS enhancement; see DLMS Introductory Note 

4e. Refer to ADC 1098.

52. 2/N106/2200 Add Qualifier PK with DLMS Note:

PK Party to Receive Copy

DLMS Note: Use with 2/N101/2200 Code X6 when the 

organization cited in N104 is receiving an information copy of the 

transaction set.

53. 2/N106/2200 Move Federal Note to DLMS Note for Qualifiers FR and TO and 

Revise DLMS Note for Qualifier TO:

FR Message From

Federal DLMS Note:

Must use with 2/N101/2200 code CI to indicate that the 

organization cited in N104 is originating the transaction set.

TO Message To

Federal DLMS Note:

Must Use with 2/N101/2200 codes CY, IF, and X6 as applicable

and 98 to indicate that when the organization cited in N104 is 

receiving the transaction set.

Administrative

54. 2/PER/2700 Open the PER Segment and add Segment level DLMS note:

DLMS Note:

1. Use to provide point of contact information. Use only in the N1 

loop identifying the consignor. Authorized DLMS enhancement; 

see DLMS Introductory Note 4e. Refer to ADC 1098.

Add capability to 

provide consignor point 

of contact information to 

support NOA processing 

by freight 

forwarder/country 

representative.

55. 2/PER01/2700 Open PER01, add Code IC and DLMS Note:

IC Information Contact

DLMS Note:

1. Use to identify the point of contact.
Enclosure 8, ADC 1098

Page 10

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

56. 2/PER02/2700 Open PER02 and add DLMS Note:

Name

DLMS Note:

1. Use to provide the full name of the point of contact.

57. 2/PER03/2700 Open PER03, add Code TE and DLMS Note:

Communication Number Qualifier

TE Telephone

DLMS Note: Use to identify the commercial phone number.

58. 2/PER04/2700 Open PER04:

Communication Number

59. 2/PER05/2700 Open PER05 and add Code EM:

Communication Number Qualifier

EM Electronic Mail

60. 2/PER06/2700 Open PER06:

Communication Number

61. 2/PER07/2700 Open PER07, add Code FX and DLMS Note:

Communication Number Qualifier

FX Facsimile

DLMS Note: Use to identify the commercial fax number.

62. 2/PER08/2700 Open PER08:

Communication Number

63. 2/SAC/3200 Open the SAC loop and add DLMS Note:

DLMS Note: Use the SAC loop in the 2/HL/0100 shipment loop. 

Authorized DLMS enhancement; see DLMS Introductory Note 

4e. Refer to ADC 1098.

Open the SAC loop to 

enable the inclusion of 

the shipment value in 

US Dollars.

64. 2/SAC01/3200 Open SAC01, add Qualifier C and associated DLMS Note:

Allowance or Charge Indicator

C Charge

DLMS Note: Use for X12 syntax compliance.
Enclosure 8, ADC 1098

Page 11

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

65. 2/SAC02/3200 Open SAC02, add Qualifier C675 and associated DLMS Note:

Service, Promotion, Allowance, or Charge Code

C675 Entered Value

DLMS Note: Use to identify the total shipment value.

66. 2/SAC05/3200 Open SAC05

Amount

DLMS Note: Enter total shipment value in US Dollars and Cents.

67. 2/YNQ/3350 Open YNQ and add Segment level DLMS Note:

DLMS Note: Use in 2/HL/0100 shipment loop to indicate if the 

shipment contains hazardous materials or explosives. Authorized 

DLMS enhancement; see DLMS Introductory Note 4e. Refer to 

ADC 1098.

Add a Yes/No indicator 

to clearly identify if the 

shipment contains 

explosives and/or 

hazardous items. This 

serves as a verification 

to ensure the appropriate 

LH1 loop information 

was provided.

68. 2/YNQ01/3350 Open YNQ01, add Qualifiers QQ and C8 with associated DLMS 

Notes:

C8 Special Servicing Required

DLMS Note: Use to indicate if the shipment contains explosives.

QQ Item is a Hazardous Item

DLMS Note: Use to indicate if the shipment contains hazardous 

materials.

69. 2/YNQ02/3350 Open YNQ02, add DLMS Note and Qualifiers N and Y

Yes/No Condition or Response Code

DLMS Note: Use one of the following codes in response to the 

YNQ01.

N No

Y Yes

70. 2/LM/3400 Move Federal Note to DLMS Note:

Federal DLMS Note: Must use this 2/LM/3400 loop to identify 

coded information maintained in department or agency 

documentation.

Administrative

71. 2/LQ/3500 Move Federal Note to DLMS Note Administrative

72. 2/LQ01/3500 Delete Federal Note Administrative
Enclosure 8, ADC 1098

Page 12

Item 

#

Location 4030 DLMS 856N

Notice of Availability

Reason

73. 2/LQ01/3500 Add Qualifiers A3, NT, and EQ and associated DLMS Notes:

DLMS Note: 1. Use codes 33, 34, 35, 40, and 69, A3, and NT only 

in 2/HL/0100 shipment loops.

2. Use codes 0, 71, 78, 85, 95, A4, A5, A6, A9, AJ, BD, and DF, 

EQ, COG, IMC, MCC, and SMI only in 2/HL/0100 line item 

loops.

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

A3 Delivery Term Code

DLMS Note: Use to identify the Delivery Term Code for the 

shipment. Authorized DLMS enhancement; see DLMS 

Introductory Note 4e. Refer to ADC 1098.

EQ Controlled Inventory Item Code

DLMS Note: Use to identify the Controlled Inventory Item Code 

for the item. Authorized DLMS enhancement; see DLMS 

Introductory Note 4e. Refer to ADC 1098.

NT Type of Cargo Code

DLMS Note: Use for water shipments to identify the predominate 

type of cargo code within the shipment unit for ocean manifesting. 

Used in conjunction with the water commodity and special 

handling code identified in the 2/LQ01/3500 Code 34. Authorized 

DLMS enhancement; see DLMS Introductory Note 4e. Refer to 

ADC 1098.

Add Delivery Term 

Code, Controlled 

Inventory Item Code, 

and Type of Cargo Code 

associated with the 

shipment.

74. 2/LQ01/3500 Update DLMS Notes for Qualifiers AJ and AL:

AJ Utilization Code

DLMS Note:

1. Under Legacy MILSTRIP DLSS, this is the first position of the 

document serial number.

2. Authorized DLMS enhancement; see DLMS Introductory Note 

4e. Refer to ADC 1098.

AL Special Requirements Code

Federal Note:

Use to identify the precedence, special handling, and processing 

requirements.

DLMS Note:

1. Use to identify the precedence, special handling, and 

processing requirements.

2. Under Legacy MILSTRIP DLSS, this is carried in the required 

delivery date field.

3. Authorized DLMS enhancement; see DLMS Introductory Note 

4e. Refer to ADC 1098.

Administrative update to 

authorize 

implementation of the 

utilization code and 

special requirements 

code as discrete data 

elements. In MILSTRIP 

legacy transactions, the 

utilization code will 

continue to be identified 

as the first position of 

the serial number in the 

document number and 

the special requirements 

code will be carried in 

the RDD field.

75. 3/SE02/0200 Move Federal Note to DLMS Note Administrative
Enclosure 8, ADC 1098

Page 13

Item 

#

Location 4010 DLMS 870N

Notice of Availability Reply

Reason

1. DLMS 

Introductory 

Notes

Add ADC 1098 to DLMS Introductory Note 4:

- ADC 1098, Updates to DD Form 1348-5 Notice of Availability 

(NOA) and Corresponding DLMS 856N NOA and 870N NOA 

Reply

Identifies DLMS

Changes included in the

DLMS IC.

2. DLMS 

Introductory 

Notes

Delete Federal Notes Administrative.

3. DLMS 

Introductory 

Notes

Modify DLMS Introductory Note 2:

2. Users operating under the Defense Logistics Management

System Standards (DLMS) must reference the Unit of Issue and 

Purchase Unit Conversion Table, Transportation Mode of 

Shipment Conversion Table, and the Accounting Classification 

Appendix which can be found on the DLA Defense Logistics

Management Standards Office Web site at http://www.dla.mil/j6/dlmso.

Add reference to 

Transportation Mode 

of Shipment 

Conversion Table

4. DLMS 

Introductory 

Notes

Add new DLMS Introductory Note 3e:

3e. Data associated with a DLMS enhancement authorized for 

implementation by modernized systems under DLMS migration. 

This data (including expanded field sizes) should be adopted 

during, or subsequent to, modernization when applicable to the 

Component’s business process. Prior coordination is not required. 

Components should ensure that inclusion of this data in a DLMS 

transaction does not cause inappropriate rejection of the 

transaction.

Add authorization for 

modernized systems to 

implement.

5. DLMS 

Introductory 

Notes

Add new DLMS Introductory Note 4 and Renumber remaining 

notes:

4. Effective April 1, 2014, refer to ADC 1075. Users must 

reference the GENC Standard for country codes 

(https://nsgreg.nga.mil/genc/discovery) for a listing of authorized 

values. Under DLMS, use the GENC Digraph (two-character).

Add requirement to use 

GENC Standard for 

geographical country 

code identification.

6. 1/ST02/010 Move Federal Note to DLMS Note Administrative

7. 1/BSR03/020 Move Federal Note to DLMS Note Administrative

8. 1/BSR04/020 Move Federal Note to DLMS Note Administrative

9. 1/BSR07/020 Move Federal Note to DLMS Note Administrative
Enclosure 8, ADC 1098

Page 14

Item 

#

Location 4010 DLMS 870N

Notice of Availability Reply

Reason

10. 1/TD5/044 Open Segment TD5 and add DLMS Note:

Carrier Details (Routing Sequence/Transit Time)

DLMS Note:

Use to identify the ship mode (air or surface) to the final 

destination, the port of embarkation and the port of debarkation. 

Authorized DLMS enhancement; see DLMS Introductory Note 

3e. Refer to ADC 1098.

Add capability to 

identify the port of 

embarkation and port 

of debarkation. To 

distinguish between air 

and surface port codes, 

the ship mode to the 

final destination is 

added.

11. 1/TD502/044 Open TD502, add Qualifier 7 and associated DLMS Note:

Identification Code Qualifier

7 Loading Dock

DLMS Note: Use to identify the Port of Embarkation (DOD 

Code) associated with the ship mode (air or surface) to final 

destination.

12. 1/TD503/044 Open TD503:

Identification Code

13. 1/TD504/044 Open TD504 and add DLMS Note:

Transportation Method/Type Code

DLMS Note: DLMS users see the Transportation Mode of 

Shipment Conversion Table for available codes. Refer to DLMS 

Introductory Note 2.

14. 1/TD507/044 Open TD507, add Qualifier PB and associated DLMS Note:

Location Qualifier 

PB Port of Discharge

DLMS Note:

Use to identify the Port of Debarkation (DOD Code) associated 

with the ship mode (air or surface) to final destination.

15. 1/TD508/044 Open TD508:

Location Identifier

16. 1/N1/050 Move Federal Note to DLMS Note Administrative
Enclosure 8, ADC 1098

Page 15

Item 

#

Location 4010 DLMS 870N

Notice of Availability Reply

Reason

17. 1/N101/050 Delete Federal Note, Delete DLMS Note 2 and Renumber; Revise 

DLMS Note 3:

DLMS Note: 

1. Use only one of code 98 IF or CY.

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

2. For conversion between MILS and DLMS formats, the 

transaction originator will always be identified by Qualifier CY

using the SC Customer Code MILSTRIP Country Code.

3. Identification of the Freight Forwarder (FF) or Country

Representative (CR) are identified as an Authorized DLMS 

enhancement; see DLMS Introductory Note 3e. Refer to ADC 

1098.DLMS enhancement; see introductory DLMS note 3a. Use of 

this enhancement requires a second iteration of the N1 loop (refer 

to ADC 309).

Administrative

18. 2/N101/050 Change Qualifier 98 to IF and Revise DLMS Note:

98 Freight Management Facilitator

IF International Freight Forwarder

DLMS Note:

This is a DLMS enhancement Use to identify the designated FF to 

receive the transaction set. Authorized DLMS enhancement; see 

DLMS Introductory Note 3e. Refer to ADC 1098.

19. 1/N101/050 Revise DLMS Note for Qualifier CY

CY Country

DLMS Note:

1. Use to identify the SC Customer Code FMS country associated 

with the NOA reply.

2. Use as a DLMS enhancement to identify the CR originating the 

transaction set. Authorized DLMS enhancement; see DLMS 

Introductory Note 3e. Refer to ADC 1098.
Enclosure 8, ADC 1098

Page 16

Item 

#

Location 4010 DLMS 870N

Notice of Availability Reply

Reason

20. 1/N103/050 Revise DLMS note for existing Qualifier 38 and Add Qualifier LC 

with Associated DLMS note:

38 Country Code

DLMS Note:

Use with N101 Qualifier CY to identify the FMS country code 

(MILSTRIP) Security Cooperation Customer Code applicable to 

the NOA reply. (Must be consistent with the NOA and original 

requisition content). Use to identify the Security Cooperation 

Customer Code.

LC Agency Location Code (US Government)

DLMS Note:

Use to identify the International Logistics Control Office (ILCO) 

SC Implementing Agency Code. Authorized values are restricted 

to those identified in DLM 4000.25, Volume 2 Appendix 7.2. 

Authorized DLMS enhancement; see DLMS Introductory Note 

4e. Refer to ADC 1098.

Change the reference 

to FMS country code 

(MILSTRIP) to 

Security Cooperation 

Customer Code. This 

code list is no longer 

maintained by 

MILSTRIP; it is 

maintained by DSCA. 

21. 1/N106/050 Move Federal Note to DLMS Note for Qualifier FR Administrative

22. 2/HL/010 Revise DLMS Note:

DLMS Note:

1. The transaction set hierarchical data structure is address 

information, followed by overall shipment information.

2. Use the first 2/HL/010 loop iteration to provide transaction set 

address information.

3. Use the second 2/HL/010 shipment unit only as loop iteration to

identify identified by the shipment information associated with the 

FMS notice transportation control number assigned to control the

shipment.

TCN has been added 

as a discrete data 

element to the NOA 

and therefore is the 

control number for the 

shipment.

23. 2/HL01/010 Move Federal Note to DLMS Note Administrative

24. 2/HL03/010 Add Qualifier V with Associated DLMS Notes

V Address Information

DLMS Note:

Use address loop to identify the consignor (shipping activity 

initiating the NOA) and the ship-to when the ship-to instructions 

are different than those provided originally.

25. 2/DTM01/080 Move Federal Note to DLMS Note Administrative

26. 2/REF01/087 Delete Federal Note Administrative
Enclosure 8, ADC 1098

Page 17

Item 

#

Location 4010 DLMS 870N

Notice of Availability Reply

Reason

27. 2/REF01/087 Modify DLMS Note for Qualifier K1:

K1 Foreign Military Sales Notice Number

DLMS Note:

Must use only in 2/HL/010 shipment loops to identify the FMS

NOA Notice number, which reflects the number of times the NOA 

has been sent to the Freight Forwarder/Country Representative 

assigned to the shipment. Authorized DLMS enhancement; see 

DLMS Introductory Note 3e. Refer to ADC 1098.

TCN is added as a 

discrete data element 

to the NOA and 

therefore is the control 

number for the 

shipment. The FMS 

Notice Number is 

redefined to reflect the 

number of times the 

NOA has been sent to 

the FF/CR.

28. 2/REF01/087 Add Qualifier TG and DLMS Note:

TG Transportation Control Number (TCN)

DLMS Note: Must use only in 2/HL/010 shipment loops to 

identify the number assigned to control the shipment between the 

shipper and consignee.

TCN is added as a 

discrete data element 

to the NOA and 

therefore is the control 

number for the 

shipment.

29. 2/N1/090 Move Federal Note to DLMS Note Administrative

30. 2/N101/090 Delete Federal Note Administrative

31. 2/N101/090 Revise DLMS note 3 for existing Qualifier ST:

ST Ship To

DLMS Note:

Use to identify the ship to address clear text address with or 

without the MAPAC when the ship to instructions are address is 

different than those provided originally what is contained in the 

MAPAD as originally identified by the address codes in the 

requisition.

Clarification.

32. 2/N103/090 Add Qualifier A2 and DLMS Note:

A2 Military Assistance Program Address Code (MAPAC)

DLMS Note:

Use to identify Security Assistance structured address data for the 

Ship To. Interpretation of this data may require additional codes 

cited elsewhere in the transaction. Authorized DLMS 

enhancement; see DLMS Introductory Note 3e. Refer to ADC 

1098.

Add MAPAC as a 

qualifier to support 

identification of the 

Ship-To location.

33. 2/N106/090 Move Federal Note to DLMS Note for Qualifier TO Administrative

34. 2/N2/100 Open Segment N2 and add DLMS Note:

DLMS Note:

Use with 2/N101/90 Code ST to identify in-the-clear exception 

ship-to name information if different than what is contained in 

the MAPAD as originally identified by the address codes in the 

requisition. Authorized DLMS enhancement; see DLMS 

Introductory Note 3e. Refer to ADC 1098.
Enclosure 8, ADC 1098

Page 18

Item 

#

Location 4010 DLMS 870N

Notice of Availability Reply

Reason

35. 2/N201/100 Open N201:

Name

36. 2/N202/100 Open N202:

Name

37. 2/N3/110 Open Segment N3 and add DLMS Note:

DLMS Note:

Use with 2/N101/90 Code ST to identify in-the-clear exception 

ship-to address information if different than what is contained in 

the MAPAD as originally identified by the address codes in the 

requisition. Authorized DLMS enhancement; see DLMS 

Introductory Note 3e. Refer to ADC 1098.

38. 2/N301/110 Open N301:

Address Information

39. 2/N302/110 Open N302:

Address Information

40. 2/N4/120 Open Segment N4:

DLMS Note:

Use with 2/N101/90 Code ST to identify in-the-clear exception 

ship-to geographical location information if different than what is 

contained in the MAPAD as originally identified by the address 

codes in the requisition. Authorized DLMS enhancement; see 

DLMS Introductory Note 3e. Refer to ADC 1098.

41. 2/N401/120 Open N401:

City Name

42. 2/N402/120 Open N402:

State or Province Code

43. 2/N403/120 Open N403:

Postal Code

44. 2/N404/120 Open N404 and add DLMS Note:

Country Code

DLMS Note:

Use to identify the GENC country code. See DLMS introductory 

note 4 (Refer to ADC 1075 for implementation).
Enclosure 8, ADC 1098

Page 19

Item 

#

Location 4010 DLMS 870N

Notice of Availability Reply

Reason

45. 2/PER/140 Open the PER Segment and add Segment level DLMS note:

DLMS Note:

Use to provide point of contact information. Use only in the N1 

loop identifying the ship to. Authorized DLMS enhancement; see 

DLMS Introductory Note 3e. Refer to ADC 1098.

Add capability to pass 

ship to point of contact 

information.

46. 2/PER01/140 Open PER01, add Qualifier IC and DLMS Note:

IC Information Contact

DLMS Note:

Use to identify the point of contact.

47. 2/PER02/140 Open PER02:

Name

48. 2/PER03/140 Open PER03, add Qualifier TE and DLMS Note:

Communication Number Qualifier

TE Telephone

DLMS Note: Use to identify the commercial phone number.

49. 2/PER04/140 Open PER04:

Communication Number

50. 2/PER05/140 Open PER05, add Qualifier EM and DLMS Note:

Communication Number Qualifier

EM Electronic Mail

DLMS Note: Use to identify the e-mail address.

51. 2/PER06/140 Open PER06:

Communication Number

52. 2/LM/144 Move Federal Note to DLMS Note Administrative

53. 2/LQ/145 Move Federal Note to DLMS Note Administrative

54. 2/LQ01/145 Delete Federal Note Administrative

55. 2/LQ01/145 Revise DLMS Note for Qualifier AJ:

AJ Utilization Code

DLMS Note:

1. Under Legacy MILSTRIP DLSS, this is the first position of the 

document serial number.

2. Authorized DLMS enhancement; see DLMS Introductory Note 

3e. Refer to ADC 1098. DLMS enhancement; see introductory 

DLMS note 3a.
Enclosure 8, ADC 1098

Page 20

Item 

#

Location 4010 DLMS 870N

Notice of Availability Reply

Reason

56. 2/LQ01/145 Move Federal Note to DLMS Note for Qualifier AL, Renumber 

and Revise:

AL Special Requirements Code

Federal DLMS Note:

1. Use to identify the precedence, special handling, and processing 

requirements.

DLMS Note:

2. Under Legacy MILSTRIP DLSS, this is carried in the required 

delivery date field.

3. Authorized DLMS enhancement; see DLMS Introductory Note 

3e. Refer to ADC 1098.DLMS enhancement; see introductory 

DLMS note 3a.

Administrative

57. 3/SE02/020 Move Federal Note to DLMS Note Administrative
Enclosure 9, ADC 1098

Page 1

Enclosure 9, Transaction and Document Flows

1. Manual NOA Flow

Shipping Activity

FF/CR

SDDC

(1a) 

Export Release Request

(if applicable)

(1b) 

Export

Release Request

(if applicable)

(3) 

DD 1348-5

(1) 

DD 1348-5/1348-1A

(2) 

DD 1348-5/1348-1A

(Delayed)

2. Mechanized NOA Flow 

Shipping Activity

FF/CR

SDDC

(1a) 

Export Release Request

(if applicable)

(1b) 

Export

Release Request

(if applicable)

(3) 

870N (AD5)

DD 1348-5

(1) 

856N (AD1/2/R)

DD 1348-5/1348-1A

ILCO

(2) 

856N (AD3/4)

DD 1348-5/1348-1A

(if applicable)

(1) 

856N (AD1/2/R)

(info only)

(2) 

856N (AD3/4)

(info only)
Enclosure 10, ADC 1098

Page 1

Enclosure 10, Updates to DLMS Data Element Dictionary

Add (A)/

Mod (M)

Data Element Definition Location Qualifier Data 

Type

Min/

Max

A Certification of 

Equivalency 

(COE)

A certification that the proposed 

packaging equals or exceeds the 

requirements of 49 Code of Federal 

Regulations Parts 100-199 

856N – 2/LHR02/1590 HN AN 1/50

M City Name A named geographic location within a 

state, province, or county.

870N – 2/N401/120 --- AN 2/30

A Component 

Authority 

Approval 

(CAA) Number

An approval issued by a national 

agency responsible under its national 

law for the regulation of hazardous 

materials transportation. These may 

also be referred to as “Special 

Approvals.” The United States 

Competent Authority is the United 

States Department of Transportation. 

856N – 2/LHR02/1590 HA AN 1/50

A Consignor The person or activity that is the 

supplier or shipper of a product. 

856N – 2/N104/2200 CI AN 6/6

M Controlled 

Inventory Item 

Code

Code designating items as having 

characteristics which require that they 

be identified, accounted for, secured, 

segregated, or handled in a special 

manner to ensure their safeguard or 

integrity. Items are categorized as 

classified, pilferable, sensitive, or 

unclassified.

856N – 2/LQ02/3500 EQ AN 1/1

M Country Code Identifies the Geopolitical Entities, 

Names, and Codes (GENC) standard. 

The GENC standard is the U.S. 

government profile of ISO 3166 (Parts 

1 and 2) names and code elements, 

with modifications only where 

necessary to comply with U.S. law and 

U.S. government recognition policy. 

The authoritative source for GENC is 

the Geopolitical Entities, Names, and 

Codes (GENC) Registry. Country 

used for distribution and the physical 

location used for clear text addressing 

under DLMS.

870N – 2/N404/120 --- ID 2/2
Enclosure 10, ADC 1098

Page 2

Add (A)/

Mod (M)

Data Element Definition Location Qualifier Data 

Type

Min/

Max

M Foreign 

Military Sales 

(FMS) 

Delivery Term 

Code

A code (prescribed in Foreign 

Military Sales cases) identifying the 

point at which the responsibility for 

moving an Foreign Military Sales 

shipment passes from the United 

States Department of Defense to the 

purchasing nation or international 

organization. 

856N – 2/LQ02/3500 A3 AN 1/1

M Department of 

Defense 

Identification 

Code

Code assigned to items of supply in 

Federal Supply Groups 13 

(ammunition/explosives) and 14 

(guided missiles). 

856N – 2/LHR02/1590 1I AN 4/4

A Department of 

Transportation 

Exemption 

(DOT-E) 

Number

A permit that gives the authority to 

deviate from specific requirements of 

Title 49 Code of Federal Regulations 

without further testing of the 

packaging.

856N – 2/LHR02/1590 HE AN 1/50

M Electronic Mail

Address

A unique address by which to send a 

message from one individual to 

another via telecommunications links 

between computers or terminals.

856N – 2/PER06/2700 EM AN 1/256

A Explosives 

Indicator

A Yes/No indicator that identifies the 

shipment as containing explosives.

856N – 2/YNQ02/3350 C8 ID 1/1

M Fax Number A unique telephone number enabling 

the telephonic transmission of 

scanned printed material normally to 

a telephone number connected to a 

printer or other output device.

856N – 2/PER08/2700 FX AN 1/256

M Freight 

Forwarder

A firm other than a railroad, motor, 

water, or air carrier that represents 

itself as a common carrier and 

undertakes to assemble and 

consolidate shipments or provide for 

assembling and consolidating and 

performing or providing for the 

performance of break-bulk and 

distributing. It assumes responsibility 

for the transportation of such property 

from point of receipt to point of 

destination; and uses the services of 

carriers subject to the governing 

bodies. 

856N – 2/N104/2200

870N – 2/N104/050

IF AN 6/6

A Freight 

Nomenclature

General description of the type of 

freight in the shipment unit.

856N – 2/TD105/1100 --- AN 1/50
Enclosure 10, ADC 1098

Page 3

Add (A)/

Mod (M)

Data Element Definition Location Qualifier Data 

Type

Min/

Max

A Hazardous 

Material 

Indicator

A Yes/No indicator that identifies the 

shipment as containing hazardous 

material.

856N – 2/YNQ02/3350 QQ ID 1/1

M International 

Logistics 

Coordination 

Office

The central U.S. Military Service 

control point in CONUS that monitors 

requisitions and related transactions 

for FMS and Military Sales and 

Grant Aid (GA).

856N – 2/N104/2200

870N – 2/N104/050

X6 AN 6/6

A Height Vertical dimension of a shipment unit. 856N – 2/MEA03/0800 HT R 1/20

M Information 

Contact

Identifies a point of contact. 856N – 2/PER02/2700

870N – 2/PER02/140

IC AN 1/60

A Lading 

Quantity

The number of freight pieces for the 

total shipment.

856N – 2/LH102/1520 --- N0 1/7

A Length Horizontal dimension of a shipment 

unit.

856N – 2/MEA03/0800 LN R 1/20

M Mark For Party Use to identify an entity located within 

the ship-to address that is to actually 

receive the materiel.

856N – 2/N104/2200 Z7 AN 6/6

A Net Explosive 

Weight

The actual weight in pounds of 

explosive mixtures or compounds, 

including the trinitrotoluene 

equivalent of energetic material, that 

is used in determination of explosive 

limits and explosive quantity data 

arcs. 

856N - 2/MEA03/0800 NX R 1/20

A Notice of 

Availability 

Notice Number

Reflects the number of times the NOA 

has been sent to the Freight 

Forwarder/Country Representative

856N – 2/REF02/1500

870N – 2/REF02/087

K1 AN 1/50

M Organization 

Street Address

A delivery address other than a 

general delivery address, Post Office 

Box address, or simplified address.

870N – 2/N301/100

870N – 2/N302/100

--- AN 1/110

M Organization 

Name

Identification of the activity. 870N – 2/N201/100

870N – 2/N202/100

--- AN 1/120

A Packing Group 

Code

Use Roman Numerals I, II, or III to 

indicate the degree of danger for the 

hazardous materiel

856N – 2/LH110/1520 --- ID 1/3

M Party to 

Receive Copy

Use to send an information copy to a

designated activity.

856N – 2/N106/2200 PK ID 2/2
Enclosure 10, ADC 1098

Page 4

Add (A)/

Mod (M)

Data Element Definition Location Qualifier Data 

Type

Min/

Max

A Port of 

Debarkation

The geographic point at which cargo 

or personnel are discharged. This may 

be a seaport or aerial port of 

debarkation; for unit requirements; it 

may or may not coincide with the 

destination. 

870N – 2/TD508/044 PB AN 3/3

A Port of 

Embarkation

The geographic point in a routing 

scheme from which cargo or 

personnel depart.

870N – 2/TD503/044 7 AN 3/3

M Postal Code Unique code assigned to a geographic 

location.

870N – 2/N403/120 --- ID 3/15

A Primary 

Hazard 

Class/Division

Defines the type of risk a hazardous 

material poses. Title 49 of the Code of 

Federal Regulations Part 173.2 

defines the class and division 

definitions. 

856N – 2/LH201/1530 --- ID 1/30

A Proper 

Shipping 

Name

The name of a hazardous material as 

shown in 49 Code of Federal 

Regulations and related or similar 

publications.

856N – 2/LH301/1540 --- AN 1/200

M Ship To Identifies the organization to receive 

the materiel.

856N – 2/N104/2200 ST AN 6/6

M State or 

Province Code

Two position alpha code of the 

State/APO/Province in the mailing 

address. 

870N – 2/N402/120 --- ID 2/2

M Telephone 

Number

A sequence of digits assigned to a 

fixed-line telephone subscriber station 

connected to a telephone line or to a 

wireless electronic telephony device, 

such as a radio telephone or a mobile 

telephone, or to other devices for data 

transmission via the public switched 

telephone network (PSTN) or other 

private networks. It serves as an 

address for switching telephone calls 

using a system of destination routing.

856N – 2/PER04/2700

856N – 2/PER04/140

TE AN 1/256

A Total Shipment 

Value

Total cost of the shipment contents. 856N – 2/SAC05/2300 C675 N2 1/15

M Transportation 

Control 

Number

A value assigned to control a 

shipment throughout the 

transportation cycle of the Defense 

Transportation System. 

856N – 2/REF02/1500

870N – 2/REF02/087

TG AN 17/17
Enclosure 10, ADC 1098

Page 5

Add (A)/

Mod (M)

Data Element Definition Location Qualifier Data 

Type

Min/

Max

M Transportation 

Method/Type 

Code

A manner of transportation movement 

(e.g., truckload, rail, commercial air).

870N – 2/TD504/044 --- ID 1/2

A Type of Cargo 

Code

A categorization scheme that 

describes certain characteristics of a 

shipment unit transported by water.

856N – 2/LQ02/3500 NT AN 1/1

A United Nations 

(UN)/North 

American (NA)

Identification 

Code

UN codes identify hazardous material 

and articles (such as explosives, 

flammable liquids, toxic substances, 

etc.) in the framework of international 

transport. North American codes are 

also known as DOT codes and are 

issued by the Department of 

Transportation; they are identical to 

UN codes, except that some 

substances without a UN number may 

have an NA number.

856N – 2/LH103/1520 --- ID 6/6

A Width The breadth of a shipment unit. 856N – 2/MEA03/0800 WD R 1/20