Page 1 

Approved Addendum to ADC 316A 

USAF Requirements for Item Record Data and UIT using the Materiel Release (DS 940R) under 

Transportation and Supply Receipt and Acknowledgement Interchange 

1. ORIGINATOR: Department of the Air Force, 754th ELSG/ILSS, DSN 596-2012; Commercial 

(334) 416-2012 

2. FUNCTIONAL AREA: 

a. Primary: Supply/Transportation Interface [SBSS/CMOS] 

b. Secondary: Supply Chain Visibility and Accountability 

3. REFERENCES: 

a. DLMSO memorandum subject: Approved Defense Logistics Management System (DLMS) 

Change (ADC) 316, Retail Transportation and Supply Receipt and Acknowledgement Transactions 

(Transportation/Supply), (Staffed as PDC 324), dated February 19, 2009. 

b. DoD 4000.25-M, Defense Logistics Management System (DLMS), Volume 3, Chapters 1 and 

2 

c. DoD 4000.25-1-M, Military Standard Requisitioning and Issue Procedures 

(MILSTRIP), Chapters 2, 3, 4, and Appendixes 2.1, 2.12, 2.16, and 3.10 

d. AFMAN 23-110 Air Force Supply Manual 

4. BACKGROUND: 

a. Intent of the Transactions: 

(1) The purpose of this requested action is to enhance the Standard Base Supply System 

(SBSS) - Cargo Movement Operations System (CMOS) interface in association with 

implementation of the ADC 316 procedures for retail transportation and supply receipt and 

acknowledgement interchange. The change will allow SBSS to perpetuate selected item record 

(NSN) data and serialized control numbers/unique item identifiers (UII) in the 940R Material 

Release transaction. CMOS requires selected item record data for each shipment record that CMOS 

builds. This information, derived from the Federal Logistics Information System (FLIS), is not 

currently available to CMOS. This change provides for the inclusion of serial number and unique 

item identifiers for applicable items in support of an approved UIT program for Positive Inventory 

Control (PIC) Nuclear Weapon Related Materiel (NWRM) (UID Designator Code AAJ). 

(2) ILS-S/SBSS test and implementation schedule: 

 MAR 2009 ‐ Contracting action approved for ILS-S/SBSS to implement NWRM PIC requirement. 

‐ Added NWRM PIC requirement to on-going ILS-S/SBSS software development schedule. 

Current schedule is in the Functional Testing phase. The development phase has been 

completed. 

‐ Additional development time was inserted to accommodate the NWRM PIC development. 
Page 2 

This development time did not impact schedule since it runs concurrent with Functional 

Testing of the other functionality in the release. 

15 MAY 2009 Complete NWRM PIC Development 

3 JUN 2009 Complete NWRM PIC Testing 

30 JUN 2009 Complete Integration Zone Testing 

04 AUG 2009 Complete Pre-Production and Security & Accreditation Activities 

10 AUG 2009 Implement in production at limited bases for Lead Base Testing 

14 SEP 2009 Implement worldwide 

(3) CMOS plans to begin testing in September 2009 of CMOS version 7.3. This release will 

implement the requirements of this proposed addendum in September 2009. Fielding is tentatively 

scheduled between January and April 2010. 

(4) Currently the ILS-S/SBSS (AF Retail Supply) passes shipment data to CMOS via a system 

to system interface. The use of the 940R Material Release and 945A Material Release Advice 

transactions will replace the CMOS / SBSS interface. As an interim plan for implementation of 

ADC 316 pending full DLMS capability, CMOS will receive shipment data in a DLMS 940R-based 

User Defined file (UDF) resulting from DAAS conversion. CMOS will respond via a DLMS 

945A-based UDF and from there DAAS will create a 945A transaction and send this back to ILS-S 

to complete the data exchange process. 

(5) Clarification/Background concerning authoritative source/oversight for incorporating PIC 

NWRM. The 754th ELSG/ILSS has participated in numerous NWRM working groups since the 

Spring of 2008. During these sessions, it soon became evident that near real time access of asset 

movement data across the Air Force supply chain, including asset serial number was fundamental to 

the NWRM tracking requirement. As the group worked through the NWRM requirements for 

Positive Inventory Control (PIC), SBSS became aware of the concurrent ADC 316 to implement a 

standardized interchange between retail transportation and supply with the use of the Material 

Release (940R). Given the secondary objective of the ADC to provide “Supply chain visibility and 

accountability”, the NWRM working group viewed the ADC as an opportunity to enhance PIC 

capabilities via the inclusion of serial numbers in the DLMS shipment transactions. The inclusion 

of serial numbers of shipped assets in the 940R transactions would enable the developers of the 

LIMS-EV PIC fusion center capability to obtain information down to the serial number level, in 

near real time whenever SBSS outbound shipment events are reported to CMOS via DLMS 940R 

transactions passing through DAAS. Below we have detailed the events and participants for this 

requirement: 

 Since March 2008 - the 754th ELSG/ILSS has been an integral member of the 

NWRM/PIC initiative, representing the supply community, since the initial Taiwan 

incident 

 September 2008 - AF/A4LM initiated discussion on this NWRM need via email with 

DLA (DLMSO). The NWRM group further envisioned that CMOS would perpetuate 

the 940R serial number data in subsequent DLMS transactions to report the physical 

shipment details; and that those CMOS DLMS transactions would also be visible to 

the PIC fusion center via DAAS. Finally, the NWRM working group envisioned that 

the CMOS data system would propagate the shipped asset serial number data through 

to the Global Transportation Network (GTN), thus enabling supply chain tracking via 

the GTN web service. 

 October 2008 - at the NWRM General Officer Steering Group, the participants 
Page 3 

emphasized the importance of prioritizing and completing the work the 754 ELSG 

would do in support of NWRM positive inventory control. 

 October 2008 -- March 2009 – Some initial shipment and serial number capabilities 

were implemented in ILS-S/SBSS in support of NWRM PIC, but did not include 

adding serial number to transactions and providing the data to the NWRM PIC Fusion 

or CMOS systems. 

 12 March 2009 – A meeting was held at 754th ELSG to establish a 754th ELSG 

Positive Inventory Control (PIC) Information Team (IT). This meeting was prompted 

by the Director of HQ 754th ELSG. The purpose of the meeting was to establish a 

team for positioning the group to support/execute enterprise PIC requirements, and 

organize/accelerate actions to implement NWRM PIC requirements. The ILSS 

requirement formalized during the meeting was to include serial number data in 

shipment transactions and make available for enterprise use, especially to the LIMSEV PIC Fusion and CMOS system. The source of the ILSS requirement is the PIC 

IPT Data Team, AF/A4/7 and A4LM. The ILT requirement formalized during the 

meeting was to include serial number data in transportation transactions. The source 

of the ILT requirement is AF/A4LM. 

(6) This standard exchange provides the ability to pre-position release order data in 

transportation, submit follow-up status messages to transportation requesting updated shipment 

status, submit cancellation requests to transportation for release orders already turned over to 

transportation for shipment planning and execution, provide supply status messages from 

transportation to supply, provide cancellation response messages from transportation to supply, and 

submit material release confirmation messages from transportation to supply when the material has 

shipped. 

(7) ILS-S will stop sending shipment notification data via the system to system exchange 

(SBSS/CMOS) known as Interactive Communications Interface (ICI). 

(8) Upon preliminary review of this PDC, DLMSO notified the Air Force that UIT by serial 

number is only authorized for approved UIT Programs and that even these are required to transition 

to use of DoD Item Unique Identification (IUID) procedures. The Air Force agreed to modify the 

planned implementation to use the DoD-required Unique Item Identifier (UII) when available. The 

serial number will be passed in addition to the UII. When legacy items are unmarked under DoD 

IUID procedures, the transaction will carry only the applicable serial number. Transactions may 

contain both a serial number and a UII. There are two separate and distinct fields that use different 

data qualifiers (SE-Serial Number and U3 for UII). Serial number may be used alone for legacy 

items when UII is not assigned, otherwise use two occurrences of this segment to identify both the 

serial number and the UII. 

(9) The LIMS-EV PIC Fusion system has an immediate need to include item data in the 940R 

in the interim until the transformation initiative to directly obtain item data from FLIS is realized. 

LIMS-EV PIC Fusion system prefers other systems provide the item data as well in the 940R if the 

system is architected to do so. 

(10) DLMSO requested that the Air Force coordinate with USTRANSOM for approval to track 

within transportation by serial number/UII using USTRANSCOM-managed transactions. DLMSO 

expressed concern about this requirement because it may not be consistent with the approach being 
Page 4 

advanced by OSD - Supply Chain Integration (SCI). Under the current concept of operation, UII 

(or serial number where UII is not available) will remain within the supply transaction exchange 

and not be perpetuated to transportation transactions. Instead, the transportation transactions will be 

associated with the supply transactions within visibility applications by linking on key identifiers, 

such as the Transportation Control Number and Document Number. The Air Force approach is 

that the 940R under this SBSS-CMOS interface will contain serial number/UII for the specified 

UIT program and USTRANSCOM will not retain this information downstream. The serial 

number/UII in the 940R that ILS-S sends to CMOS supports unique Air Force NWRM processing. 

It provides a temporary linkage between the serial number/UII and the document number to support 

asset visibility data fusion. In addition, it supports requirements to validate/verify package contents 

prior to TMO sealing the package. Serial number/UII discrepancies discovered by the TMO will be 

researched and/or resolved manually, off-line, with the retail supply warehouse. The longer term 

plan is to carry the serial number/UII in the DS 856S when Air Force legacy systems are replaced 

by the Expeditionary Combat Support System (ECSS). 

(11) DLMSO initially non-concurred with the passing of data elements in the 940R, derived 

from Federal Logistics Information System (FLIS) as part of the SBSS-CMOS interface. DLMSO 

requested that the Air Force further explore alternatives. As currently documented in this 

addendum, the provision to provide FLIS data elements in the 940R to CMOS is limited to 

SBSS/ES-S; all other supply systems (e.g. DMLSS) will default to the original business rules from 

ADC 316. FLIS data will be passed on the DLMS 940R transaction on an interim basis for the 

SBSS-CMOS interface only. The next opportunity to introduce a FLIS interface into CMOS is in 

CMOS release version 7.5. Based upon the information provided, the earliest a FLIS/CMOS 

interface could be developed is August 2011. 

b. Scenario for which the transaction is used: 

(1) ILS-S will create a 940R DLMS transaction each time a Cargo Movement transaction 

occurs in the SBSS/ES-S. The following Air Force TRICs/DICs are considered Cargo movements: 

[A2(X), A4(X), A5(X), DOR*, FME, FTA, FTR, ISU*, MSI*, RAR, SHP, 1ET]. (Note: *Applies 

to off-base organizations only.) 

(2) ILS-S will create a 940R DLMS transaction each time a Cargo Movement transaction has 

been reverse posted in the SBSS or cancelled in ES-S. This 940R is a request for cancellation when 

received by CMOS. CMOS will respond with a 945A transaction. There are no changes (from 

ADC) for this transaction; no additional data is required. 

(3) ILS-S will create a 940R DLMS transaction each time a Cargo Movement transaction 

requires a follow up for status. CMOS will respond with a 945A transaction. There are no changes 

(from ADC) for this transaction; no additional data is required. 

c. Current data elements in use today: 

Today the SBSS and CMOS have a system to system interface. These transactions are system 

user defined files and these records are not passed to DAAS. The following table lists the SBSS 

data element titles that are passed today on the Advance Shipment Notification: 

SBSS EVENT RECORD FORMAT DTD: 6 APR 2009

Position Positions TITLE 

 

1 1 CMOS FLAG 
Page 5 

2-4 3 DOCUMENT-IDENTIFIER-CODE 

5 1 DEMILITARIZATION-CODE 

6-9 4 TRANSPORTATION ACCOUNT CODE (TAC) 

10 1 SECURITY-CLASSIFICATION-CODE 

11-24 14 DOCUMENT-NUMBER 

25 1 SUFFIX-CODE (is this part of the doc number) 

 

26-31 6 SHIP-FROM-SRAN 

32-37 6 SHIP-TO-SRAN 

38-40 3 SHIP-TO-RID 

41-55 15 NATIONAL-STOCK-NUMBER 

56-74 19 ITEM-NOMENCLATURE 

75-76 2 UNIT-OF-ISSUE 

77-81 5 QUANTITY-TO-BE-SHIP 

82-87 6 SUPP ADDRESS 

88-89 2 SYSTEM-DESIG 

90-91 2 PRIORITY 

92-115 24 SHIP-TO-NAME 

116-139 24 SHIP-TO-STREET-ADDRESS 

140-157 18 SHIP-INSTALLATIONS OR CITY 

158-162 5 STATE OR COUNTRY (ABBREVIATION) 

163-171 9 ZIP-CODE 

172-180 9 SPECIAL-PACKING-INSTRUCTION-NUMBER 

181-182 2 TYPE-CARGO-CODES 

183-188 6 NATIONAL MOTOR FREIGHT CLASSIFICATION CODE 

189-195 7 ORDNIAL-DATE 

196-205 10 SERVICEABLE-BALANCE 

206-215 10 UNIT-PRICE 

216-226 10 EXTENDED-COST 

227 1 PRECIOUS-METALS-CODE 

228-230 3 ERRCD 

231-233 3 RID 

234 1 CONDITION-CODE 

235-245 11 WAREHOUSE-LOCATION 

246-252 7 DATE-OF-LAST-TRANSACTION 

253-255 3 REQUIRED-DELIVERY-DATE 

256-258 3 PROJEC-CODE 

259 1 SERIALIZED-REPORT-CODE 

260-1159 15 SERIAL NUMBER (UP TO 60 ADDITIONAL SERIAL NUMBERS) 

 d. Current Document Identifier Codes and DLMS IC’s in use today: N/A - Today the 

SBSS and CMOS have a system to system interface. These transactions are system user defined files 

and these records are not passed to DAAS. The following Air Force TRICs/DICs are passed as part of 

the system to system User defined Files: [A2(X), A4(X), A5(X), DOR, FME, FTA, FTR, ISU, MSI, 

RAR, SHP, 1ET]. 

5. PROPOSED CHANGE(S): 

a. Description of Change: 

(1) ADC 316A is an addendum to ADC 316, Retail Transportation and Supply Receipt and 

Acknowledgement Transactions. This change will incorporate additional data content and procedures 

for UIT where applicable for SBSS and CMOS system interfaces. Coupled with ADC 316, this 

change will implement a standardized interchange between retail transportation and supply through the 

use of EDI transactions, specifically the Material Release, 940R, and Material Release Advice 945A. 
Page 6 

(2) UIIs and/or serial numbers when applicable (up to 60 sets) will be included on the 940R 

transaction when the item falls under the Air Force PIC NWRM program. Additional data elements, 

primarily FLIS data associated with the NSN will also be included for all 940R transactions. This data, 

when present will be passed to DAAS from ILS-S on the DLMS transaction. DAAS receives and 

translates the 940R transaction into a CMOS UDF.

(3) CMOS will use a UDF to receive/communicate data. DAAS will perform the 

translation into/from the DLMS 940R and 945A transactions. CMOS is not currently resourced to 

provide EDI translation/conversion services. DAAS has provided data translation services as a cost 

effective solution. CMOS expects to become fully DLMS compliant sometime between FY 2012 and 

2014 when the system becomes web enabled.

b. Procedures: 

 (1) Refer to Enclosure 1 and 2 for DLMS manual procedures. 

 (2) Update the Materiel Release 940R as follows: 

# Location Revision to 4030 940R, Material Release Reason for Change 

/SBSS Notes 

1 DLMS 

Introductory 

Note

Add Approved Addendum to ADC 316A to DLMS Introductory 

note:

- Approved Addendum to ADC 316A, USAF Requirements for 

Item Record Data and Unique Item Tracking (UIT) using the 

Materiel Release (DS 940R) under Transportation and Supply 

Receipt and Acknowledgement Interchange. 

To identify changes in 

the DS. 

2 2/N901/1500 Add DLMS note 2 to existing code SE:

SE Serial Number 

DLMS Note: 

1. Use to identify the serial number. The serial number may not 

exceed 30 characters in accordance with IUID policy. 

2. Use when this transaction supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange SBSS 

interface with CMOS to provide the serial number under PIC 

NWRM UIT program. Serial number may be used alone for 

legacy items when UII is not assigned, otherwise use two 

occurrences of this segment to identify both the serial number 

and the UII. A maximum of 60 items may be identified for this 

interface.

To perpetuate serial 

numbers on shipment 

notifications. This allows 

for increased asset 

visibility. 

3 2/N901/1500 Add DLMS note 2 to existing code U3:

U3 Unique Supplier Identification Number (USIN) 

DLMS Note: 

1. Use to identify the UII. The UII may not exceed 50 characters 

in accordance with IUID policy. A data maintenance action was 

approved in version 5020. The approved code/name is "UII - 

Department of Defense Unique Item Identifier”. 

To perpetuate UIIs on 

shipment notifications. 

This allows for increased 

asset visibility. 
Page 7 

2. Use when this transaction supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange SBSS 

interface with CMOS to provide the UII under PIC NWRM UIT 

program. A maximum of 60 items may be identified for this 

interface. 

4 2/W0106/02

00 

Add DLMS note 2 to existing code CN:

CN Commodity Name 

DLMS Note: 

1. Use with W0104 code FT to identify the commodity name or 

description when citing the Federal Supply Classification. 

2. Use when this transaction supports the Retail Transportation 

and Supply Receipt and Acknowledgement SBSS interface with 

CMOS to provide the NSN nomenclature when FLIS item data 

is not otherwise available to CMOS. Field size for SBSS – 

CMOS is restricted to 19 positions. 

To perpetuate FLIS item 

record data onto the 

shipment notifications. 

Data is required by 

CMOS. 

SBSS Event Pos 56-74 

5 2/N901/0400 Add the following code KD with DLMS notes:

KD Special Instructions Number 

DLMS Note: Use only when this transaction supports the Retail 

Transportation and Supply Receipt and Acknowledgement 

Interchange SBSS interface with CMOS to provide Special 

Packing Instruction (SPI) Code/Reference Number when FLIS 

item data is not otherwise available to CMOS. Field size for 

SBSS – CMOS is restricted to a maximum of 9 positions 

(alpha/numeric). 

To perpetuate FLIS item 

record data onto the 

shipment notifications. 

Data is required by 

CMOS. 

SBSS Event Pos 172-180

6 2/LQ01/130

0 

Add DLMS note 2 to existing code FD:

FD Demilitarization Code 

DLMS Note: 

1. Use in disposal release orders and historical disposal release 

orders, to identify any demilitarization actions, which must take 

place prior to disposal. 

2. Use when this transaction supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange SBSS 

interface with CMOS when FLIS item data is not otherwise 

available to CMOS. 

To perpetuate FLIS item 

record data onto the 

shipment notifications. 

Data is required by 

CMOS. 

SBSS Event Pos 5 

CMOS requires this data 

for all MROs. 

7 2/LQ01/130

0 

Add the following code EQ with DLMS notes:

EQ Controlled Inventory Item Code 

DLMS Note: Only use when this transaction supports the Retail 

Transportation and Supply Receipt and Acknowledgement 

SBSS interface with CMOS when FLIS item data is not 

otherwise available to CMOS. 

To perpetuate FLIS item 

record data onto the 

shipment notifications. 

Data is required by 

CMOS. 

SBSS Event Pos 10 

8 2/LQ01/130

0 

Add the following code NT with DLMS notes:

NT Type of Cargo Code 

DLMS Note: Only use when this transaction supports the Retail 

Transportation and Supply Receipt and Acknowledgement 

Interchange SBSS interface with CMOS. Use a maximum of 

This requirement will 

continue after CMOS 

FLIS Interface. 

SBSS Event Pos 181-182
Page 8 

repetitions to identify two cargo codes. 

9 2/LQ01/130

0 

Add the following code NK with DLMS notes:

 

NK National Motor Freight Classification (NMFC) Code 

DLMS Note: Only use when this transaction supports the Retail 

Transportation and Supply Receipt and Acknowledgement 

Interchange SBSS interface with CMOS. 

To perpetuate Air Force 

item record data onto the 

shipment notifications. 

Data is required by 

CMOS. 

SBSS Event Position 

183-188 

10 2/AMT01/08

00 

Add the DLMS note 4 to existing code LI:

LI Line Item Unit Price 

DLMS Note: 1. Use with material release order transactions to 

indicate the unit price. 

2. A field size exceeding 7 positions (5 digits dollars and 2 digits 

cents) may not be received or understood by the recipient’s 

automated processing system. 

3. Under DLMS, the unit price will be expressed as R9.2. 

Authorized DLMS migration enhancement; see introductory 

DLMS 4f. 

4. The DLMS field length is authorized when this transaction 

supports the Retail Transportation and Supply Receipt and 

Acknowledgement Interchange SBSS interface with CMOS. 

SBSS Event Pos 206-215 

Requires formatting to 

match DLMS R9.2 from 

original SBSS 10 pos 

numeric 

11 2/LQ01/130

0 

Add DLMS note 2 to existing code 90:

90 Precious Metals Indicator Code 

DLMS Note: 

1. Use in disposal release orders and historical disposal release 

orders, to identify the precious metal content of the specified 

material. 

2. Use when this transaction supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange SBSS 

interface with CMOS when FLIS item data is not otherwise 

available to CMOS. 

Clarifies required SBSSCMOS use. SBSS Event 

Pos 227 

CMOS requires this data 

for all MROs. 

12 2/N901/0400 Add the following code BY with DLMS notes:

BY Repair Category Number 

DLMS Note: Use only when this transaction supports the Retail 

Transportation and Supply Receipt and Acknowledgement 

Interchange SBSS interface with CMOS to provide the Air 

Force Expendability-Recoverability-Reparability Category Code 

(ERRCD) when FLIS item data is not otherwise available to 

CMOS. Code list is available at FLIS Table 69. 

To perpetuate FLIS item 

record data onto the 

shipment notifications. 

Data is required by 

CMOS. 

SBSS Event Pos 228-230

13 2/N101/1100 Add the following code SUS with DLMS notes:

SUS Supply Source 

DLMS Note: Use only when this transaction supports the Retail 

Transportation and Supply Receipt and Acknowledgement 

Interchange SBSS interface with CMOS to provide the Routing 

Identifier Code of the Source of Supply when FLIS item data is 

SBSS Event Pos 231-233 
Page 9 

not otherwise available to CMOS. 

15 2/N901/0400 Add the following code TH with DLMS notes:

TH Transportation Account Code (TAC) 

DLMS Note: Only use when this transaction supports the Retail 

Transportation and Supply Receipt and Acknowledgement 

Interchange SBSS interface with CMOS. 

SBSS Event Pos 6-9 

This data currently 

resides in a SBSS table. 

At this time, there is no 

effort to obtain this data 

from its source. 

16 2/N101/1100 Add DLMS note 4 to existing code DS:

DA Delivery Address 

DLMS Note: 

1. Use with 2/N2/1101, 2/N3/1102, and 2/N4/1103 to identify 

fully in-the-clear exception ship-to address information under 

authorized conditions. 

2. Use for MRO Exception Data Transaction to indicate the shipto clear-text exception address is a MRO Type Address Code 

(TAC) 2 (ship-to) freight address. 

3. DLMS enhancement; see introductory DLMS notes 4a and 4e. 

4. Use when this transaction supports the Retail Transportation 

and Supply Receipt and Acknowledgement Interchange SBSS 

interface with CMOS to provide the shipping address when not 

associated with a DoDAAC. 

80 pos, SBSS Event Pos 

92-171 

6. REASON FOR CHANGE: 

 The changes are proposed to standardize a retail transportation and supply electronic interface in 

order to provide intransit visibility and accountability of all government assets being shipped within 

the Defense Transportation System (DTS). In addition, the transactions will provide end-users an 

electronic method of obtaining shipment data and status codes on specific line items upon inquiry. 

7. ADVANTAGES AND DISADVANTAGES: 

 a. Advantages: This interface will provide a bi-directional exchange of shipment data transactions 

between retail transportation and supply systems. Adding these capabilities to the transaction sets will 

improve asset visibility throughout the transportation processing and movement cycle while decreasing 

cargo movement processing times. The changes will also allow the transportation and supply activities 

to communicate in the clear status information electronically on each line item. The proposed changes 

to the supplements enable DLMS compliant systems to use extended DLMS enhancements that would 

not otherwise be available in a MILS environment; while MILS-based supply systems will be able to 

interface with transportation, through transformation of data by DAASC. 

 b. Disadvantages: Programming to support the additional FLIS data content in the 940R is a 

temporary requirement to meet Air Force implementation schedules and will not be necessary once the 

FLIS interface for CMOS is established; target date is August 2011. The addition of UII/serial number 

information into the 940R is not standard under the IUID business rules being developed by the Joint 

IUID working group, chaired by OSD-SCI. This requirement will be carried in the 940R pending DS 

856S implementation by the Air Force ERP system, ECSS. 

8. ALTERNATIVES: 
Page 10 

a. Alternate methods of obtaining item record data has been pursued/considered and currently 

do not meet the technical or implementation schedule requirements (e.g. use of a CD ROM containing 

catalog data). CMOS plans to pursue a FLIS (catalog data) interface to receive item record data in a 

future release. 

 b. The plan is for ILS-S and CMOS to eventually transition to UII tracking using IUID 

business rules. In the interim, the 940R will accommodate both the serial number and the UII when 

available. 

9. IMPACT: 

 a. ILS-S to implement DLMS transactions – Material Release, 940R, and Material Release 

Advice, 945A. 

 b. HQ USAF coordinated with USTRANSCOM concerning the perpetuation of the serial 

number/UII into transportation business processes. USTRANSCOM stated that there is no plan to 

carry the IUID information in transportation transactions; that information will be “fused” through the 

use of the DS 856S, Shipment Status message. 

 c. The implementation of this UIT requirement is not dependent upon the further perpetuation 

of the 940R serial number/UII. 

 

 d. Sensitivity of Data Content – The lead AF catalog manager (HQ AFMC/401 

SCMS/GUMB) has verified that all of the item record data that AF will be passing in the DLMS 

transaction is NOT restricted in any manner and that the passing of this data in a single transaction 

does not present a risk to the data. 

 

e. See ADC 316 for additional impacts. 

10. COST SAVINGS/AVOIDANCE/TANGIBLE BENEFITS: 

 a. Cost Savings/Avoidance: 

- There may be a cost savings within DISA associated with eliminating the CMOS system to 

system interface. At this time, Air Force has not done an analysis to determine any cost 

savings. 

 

 b. Tangible Benefits: 

 - Provides near real time shipment status of SBSS shipments to CMOS, DAAS, PIC Fusion 

 Center – and supports NWRM control. 

- Standardizes data transaction sets for CMOS interfaces. 

- See also “Advantages” listed in paragraph 7 above. 
Page 1 

Enclosure 1, DoD 4000.25-1-M, Volume 3

Addendum to ADC 316A revisions are identified in bold italics:

C2. CHAPTER 2

RETAIL TRANSPORTATION AND SUPPLY INTERCHANGE

(STOCK AND NON-STOCK SHIPMENTS)

 C2.3.2. RETAIL SUPPLY ACTIVITY. This section provides general procedures for retail 

supply activities related to the delivery of items to the servicing transportation activity for further 

shipment. 

 C.2.3.2.1 Pre-positioned Release Order. For designated supply trading partners, 

DAAS shall transmit copies of the Material Release Order/Disposal Release 

Order/Redistribution Order 940R (A2_/A5_/A5J/A4_) transactions to the designated 

transportation system to be pre-positioned awaiting actual arrival of cargo from the supply 

warehouse. 

 C.2.3.2.1.1 For designated supply trading partners (currently limited to the 

SBSS - CMOS interface) the Materiel Release 940R will be used to pass Federal Logistics 

Information System (FLIS) NSN item data (as identified in the 940R) that is not otherwise 

available to CMOS. This is an interim measure pending establishment of a FLIS interface. 

 C.2.3.2.1.2 For designated supply trading partners (currently limited to the 

SBSS - CMOS interface) the Materiel Release 940R will be used to support the unique item 

tracking (UIT) program for Positive Inventory Control (PIC) Nuclear Weapon Related 

Materiel (NWRM). Unique item identifiers (UIIs) and the associated serial number will be 

passed in the 940R for each item meeting the PIC NWRM program criteria. For legacy items 

where the UII has not been marked in accordance with Item Unique Identification (IUID) 

policy, the serial number alone will be passed. This is an interim measure pending transition 

to tracking by UII and associated IUID business rules/transactions. DLMS Vol II, Chapter 

19, UIT procedures apply (with exceptions as noted). 

 C2.3.2.2. Delivery and Incheck. The supply activity will make local deliveries of the 

items to be shipped to the servicing transportation activity. The line items shall be inchecked by 

the transportation activity based on the cargo and the documentation received from the supply 

activity. 

 C2.3.2.3. Shipment Documentation. The material for shipment will be delivered to 

the servicing transportation activity by the retail supply activity accompanied by a DD Form 

1348-1A, Issue Release/Receipt Document (IRRD). DoD 4000.25-1-M, Military Standard 

Requisitioning And Issue Procedures (MILSTRIP) Manual, Chapter 5, Release and Receipt of 

Materiel, documents procedures for the use and generation of the IRRD. 

 C2.3.2.4. Follow-up Requests. The supply system will initiate a Material Release 
Page 2 

Inquiry/Disposal Release Inquiry 940R (AF6/AFJ) message for follow-up requests. Based upon 

elapsed time from either the initial release of the material release order/disposal release 

order/redistribution order or the estimated shipping date from the material release 

advice/disposal shipment advice, the supply system will initiate the inquiry using normal followup procedures as documented in DoD 4000.25-1-M, Chapter 2, paragraph C2.13; the only 

exceptions relate to multi-packs (see DoD 4000.25-M, Volume 3, Chapter 2, paragraph C2.3.6) 

and assemblages, e.g., medical (see DoD 4000.25-M, Volume 3, Chapter 2, paragraph C2.3.7). 

 C2.3.2.5. Cancellation Requests. The supply system will initiate a Material Release 

Cancellation/Disposal Release Cancellation 940R (AC6/ACJ) message for cancellation requests. 

DoD 4000.25-1-M, Chapter 2, paragraph C2.17 prevails; the only exceptions relate to multipacks (see DoD 4000.25-M, Volume 3, Chapter 2, paragraph C2.3.6) and assemblages, e.g., 

medical (see DoD 4000.25-M, Volume 3, Chapter 2, paragraph C2.3.7). 

 C2.3.2.6. Shipment Status Message. When the retail supply activity receives the 

material release confirmation for a multi-pack, they shall associate it with all the document 

numbers that were contained in the initial material release order, generate the required Shipment 

Advice 856S (AS_) shipment status transactions for the multi-pack and transmit to DAAS for 

distribution per existing procedures and trading partner profiles. When the retail supply activity 

receives the material release confirmation for an assemblage (e.g., medical), they shall generate 

the required Shipment Advice 856S shipment status transaction at the Assemblage Identification 

Number (AIN) level. For all material release confirmations, the retail supply activity shall insert 

the original distribution code assigned to the material release order/disposal release 

order/redistribution order, in lieu of the special distribution code used to denote the Retail 

Transportation and Supply Interchange, when generating the shipment status transactions. 
Page 1 

Enclosure 2, DoD 4000.25-1-M, Volume 2 

Addendum to ADC 316A revisions are identified in bold italics: 

C19. CHAPTER 19

UNIQUE ITEM TRACKING

C19.17. MATERIAL REDISTRIBUTION AND RELEASE. 

C19.17.1 The shipping activity shall release the appropriate number and condition code 

of UII(s) items without regard to the UII(s) selected. Also applies to DRO. There is currently no 

documented requirement for an owner to direct release of a specific UII(s). 

C19.17.2 DLMS Retail Transportation and Supply Receipt And Acknowledgement 

Interchange. (See DoD 4000.25-M, Volume 3, Chapter 2) For designated supply trading 

partners (currently limited to the Standard Base Supply System (SBSS) - Cargo Movement 

Operations System (CMOS) interface, the Materiel Release 940R will be used to support the 

unique item tracking (UIT) program for Positive Inventory Control (PIC) Nuclear Weapon 

Related Materiel (NWRM). Unique item identifiers (UIIs) and the associated serial number 

will be passed in the 940R for each item meeting the PIC NWRM program criteria. For legacy 

items where the UII has not been marked in accordance with Item Unique Identification 

(IUID) policy, the serial number alone will be passed. This is an interim measure pending 

transition to tracking by UII and associated IUID business rules/transactions. 

C19.18. CANCELLED MRO/DRO SUPPORTING UII MATERIAL RELEASE. 

 C19.18.1. The storage activity shall confirm MRO or DRO cancellation to the owner, 

including UII(s). The storage activity shall confirm MRO or DRO cancellations in accordance 

with DS 945A (material release cancellation advice or disposal release cancellation advice) in 

accordance with Chapter 4. 

 C19.18.2. The owner shall confirm MRO cancellation with Status Code BQ using DS 

870S, via DAAS to eligible status recipients. Data are entered in the eligible status recipient’s 

AIS. 

C19.19. MATERIAL RELEASE CONFIRMATION (MRC). 

 C19.19.1 For all UIT programs, with the exception noted below for the retail 

transportation and supply receipt and acknowledgement interchange, the shipping activity 

shall confirm material release to the owner and report UII(s) shipped. The storage activity shall 

submit MRC, including UII(s), using DS 945A, processed in accordance with Chapter 4. 

 C19.19.2 DLMS Retail Transportation and Supply Receipt And Acknowledgement 

Interchange. (See DoD 4000.25-M, Volume 3, Chapter 2). Transportation activities do not 

currently have a requirement to perform unique item tracking. As a result, the Materiel 

Release Advice (945A) does not currently authorize inclusion of UII (or serial number). 
Page 2 

(text not shown) 

Table C19.T1. DLMS Transactions with UIT Capability

DS # TITLE 

Process IAW 

(DLMS Volume, Chapter) 

140A1 Small Arms Reporting Vol 2, Chapter 18 

140B RESERVED. No documented business 

case/requirement (Unique Item Tracking 

Report) 

180M Material Returns Reporting Vol 2, Chapter 11 

511M Requisition Modification Vol 2, Chapter 4 

511R Requisition Vol 2, Chapter 4 

527D Due-in/Advance Receipt/Due Verification Vol 2, Chapter 12 

527R Receipt, Inquiry, Response and MRA Vol 2, Chapter 13 

810L Logistics Bill Vol 5, Chapter 2 

842A/W SDR Follow-up, Correction, Cancellation, 

& Reconsideration Request 

Vol 2, Chapter 17 

842S/Q Storage Quality Control Report Vol 2, Chapter 21 

842S/R Storage Quality Control Report Reply Vol 2, Chapter 21 

846A Asset Reclassification Vol 2, Chapter 7 

846F Ammunition Freeze/Unfreeze Vol 2, Chapter 14 

846I Asset Status Inquiry/Report Vol 2, Chapter 5 

856 Advance Shipment Notice Vol 2, Chapter 19 

856R Shipment Status Material Returns Vol 2 Chapter 11 

856S Shipment Status Vol 2, Chapter 5 

861 Acceptance Report Vol 2, Chapter 19 

(WAWF) 

867I Issue Vol 2, Chapter 14 

 

1

 DS 140A is specific to use for Small Arms tracking under the DoDSASP. 
Page 3 

870M Material Returns Supply Status Vol 2, Chapter 11 

888A2 Small Arms Data Change Vol 2, Chapter 18 

888B RESERVED. No documented business 

case/requirement (Unique Item Data 

Change) 

940R Material Release Vol 2, Chapter 4 

940R Materiel Release for retail transportation 

and supply receipt and acknowledgement 

interchange 

Vol 3, Chapter 3 

945A Material Release Advice Vol 2, Chapter 4 

947I Inventory Adjustment Vol 2, Chapter 7 

(text not shown) 

Table C19.T2. UIT Designator Codes

UITDC EXPLANATION 

AAA DoD Small Arms Serialization Program (DODSASP) 

AAB Security Risk Category I Non-Nuclear missiles and Rockets 

AAC Radiation Testing and Tracking System (RATTS) Program 

AAD Navy Depot Level Reparables (NDLR) Program 

AAE Army Maintenance Management System (TAMMS) Equipment Data Base 

(TEDB) 

AAF Aviation Component Tracking Program 

AAG Tritium Unique Item Tracking Program 

AAH Controlled Cryptographic Items (CCI) 

AAJ Positive Inventory Control (PIC) Nuclear Weapon Related Materiel (NWRM).3

UID Assets which meet DoD IUID criteria for marking, but which are not subject to 

DoD UIT program/tracking requirements.4

 

2

 DS 888A is specific to use for Small Arms tracking under the DoDSASP. 3

 ADC 316A documenting PIC NWRM requirements.

4

 See http://www.acq.osd.mil/dpap/pdi/uid/index.html for UID policy and criteria for assigning IUID to 

material. 
Page 1 

Enclosure 3, Comment Resolution 

Item # Received From Comments Resolution 

1. OSD-SCI Is this temporary until you migrate to 

ECSS? What will you do for 

implementing serial number and UII in 

the future? 

AF will add serial number 

and UII to the 856S during 

implementation of ECSS. 

2. Air Force Use of FLIS data elements in 940R 

will be limited to SBSS/ILS-S only. 

DLMSO concurs in this 

temporary, limited use. 

3. USTC Serial number/UII not needed for use 

in transportation systems. 

None required. 

4. Air Force/SBSS The aggregation of shipment and 

catalog information together in a 

single transaction poses no security 

risks per AFMC and AF. 

None required. 

 5. Air Force/SBSS Transactions may contain both a 

serial number and a UII. There are 

two separate and distinct fields that 

use different data qualifiers (SE-Serial 

Number and U3 for UII). See Items 2 

and 3 in the DLMS Mapping Table, 

this document 

Concur.