IN REPLY 

REFER TO 

DEFENSE LOGISTICS AGENCY 

HEADQUARTERS 

8725 JOHN J. KINGMAN ROAD 

FORT BELVOIR, VIRGINIA 22060-6221 

March 27, 2013 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS 

SUBJECT: Approved Defense Logistics Management System (DLMS) Change (ADC) 1055, 

Add Cargo Movement Operations System (CMOS) Transportation In-checker 

Identification Information to the DLMS 945A Materiel Release Advice in Support of 

the Retail Supply and Transportation Interchange (Supply/Transportation) 

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

Logistics Management System (DLMS), is approved for Air Force implementation in February 

2014. It is optional for all other systems that either have implemented an interface with CMOS 

or plan to do so in the future. The Air Force PRC member is required to monitor actively for 

implementation and provided updated implementation dates. For all other Supply PRC 

members, if your Component elects to implement tllis ADC, you are required to monitor actively 

for implementation of this ADC and provide implementation dates when they become available. 

The updated DLMS Supplement will be posted to the DLA Logistics Management 

Standards Office Web site at www.dla.mil/j-6/dlmso/elibrary/TransFormats/formats.asp within 

1 0 days from the above date. 

Addressees may direct questions to Ms. Ellen Hilert, DOD MILSTRIP 

Administrator, 703-767-0676 or DSN 427-0676, e-mail: ellen.hilert@dla.nlil or Ms. Heidi 

Daverede, DOD MILSTRIP Alternate, 703-767-5111; DSN 427-5111 , e-mail: 

heidi.daverede@dla.mil. Others may direct questions to their Service or Agency designated 

Supply PRC representative available at: www.dla.mil/j6/dlmso/CeitAccess/SvcPointsPOC/allpoc.asp. 

Attachment 

As stated 

cc: 

ODASD(SCI) 

d:!~~ Director 

DLA Logistics Management 

Standards Office 

Federal Recycling Program G Printed on Recycled Paper 
Page 1 Attachment, ADC 1055

Attachment to ADC 1055

Add Cargo Movement Operations System (CMOS) Transportation Inchecker Identification Information to the DLMS 945A Materiel Release 

Advice in Support of the Retail Supply and Transportation Interchange

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION: Department of the 

Air Force, AFPEO/ELS/HGGG, DSN 596-5187; Commercial (334) 416-5187

a. Technical POC: NTT DATA Federal Services, Inc.

b. Functional POC: AFMC AFLCMC/HIAR

2. FUNCTIONAL AREA:

a. Primary/Secondary Functional Area: Supply/Transportation

b. Primary/Secondary Functional Process: Supply Chain Visibility and 

Accountability

3. REFERENCES:

a. DLM 4000.25-M, DLMS, Volume 3, Chapter 2 

b. Approved DLMS Change (ADC) 316, Retail Transportation and Supply Receipt and 

Acknowledgement Transactions, dated February 19, 2009.

4. REQUESTED CHANGE(S):

a. Brief Overview of Change: The approved change adds a transportation in-checker 

code and the name of the in-checker to the DLMS 945A Supply Status transaction, when the 

storage and transportation activities are operating under the Retail Supply and Transportation 

Interchange procedures published in the DLM 4000.25, Volume 3, Chapter 2 (Reference 3.a.). 

This will improve visibility, accountability, and traceability of materiel delivered by a retail 

storage activity to a transportation office using Cargo Movement Operations System (CMOS).

b. Background: ADC 316 (Reference 3.b.) established a standardized interchange 

between retail transportation and supply through the use of EDI (Electronic Data Interchange) 

transactions, specifically the DLMS 940R Materiel Release and the DLMS 945A Materiel 

Release Advice. 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 materiel release confirmation messages from transportation to supply when the 

materiel has shipped. 
Page 2 Attachment, ADC 1055

c. Approved Change in Detail: [Significant changes based on staffing of the PDC are 

highlighted in blue].

(1) When CMOS in-checks materiel from a supply storage activity that has 

implemented the retail supply and transportation interchange as documented in the DLM 

4000.25, Volume 3, Chapter 2, CMOS will add the transportation in-checker’s full name, inchecker ID, and optional contact information (e.g., phone number) to the DLMS 945A In-Check 

status transaction. CMOS transmits the DLMS 945A to DLA Transaction Services for routing to 

the supply storage activity acknowledging receipt of the materiel for transportation planning and 

processing.

(2) The transportation in-checker’s full name will be formatted as First Name

Middle Initial Last Name with no special characters (e.g., periods, commas, apostrophes) to 

separate the components of the full name. For example, Johann K. Dippel transmits as <Johann 

K Dippel>. If there is no middle initial, insert NMN in the place of the middle initial.

(3) The transportation in-checker’s ID code is a three-position numeric value 

assigned by CMOS and is directly associated to the in-checker’s full name.

(4) Contact information may include phone numbers (e.g., commercial, DSN, 

international, and fax) and electronic mail. If more than three types of contact information are 

required, repeat the X12 PER segment, not to exceed two repetitions.

(5) CMOS will add these data elements to the DLMS 945A when the supply 

activity has requested the inclusion of this data in the in-check status transaction. Currently, 

Integrated Logistics Solution-Supply (ILS-S) supply activities with a RIC To = D(xx) have

requested the inclusion of this data.

d. Revisions to DLM 4000.25 Manuals:

(1) Revise DLMS Supplement 945A as shown in Enclosure 1.

(2) Add the following paragraph to the DLM 4000.25, DLMS, Volume 3, 

Chapter 2:

C2.3.3.1.3. When CMOS is the servicing transportation activity, the in-check status message 

will include the transportation in-checker identification code (three position numeric value) 

and the associated in-checker full name in the format of First Name Middle Initial Last 

Name, with no special characters (e.g., periods, commas) to separate the components of the 

full name. If there is no middle initial, then insert NMN (no middle name) in place of the 

middle initial. Optional contact information may include phone numbers (e.g., commercial, 

DSN, international, and fax) and electronic mail. If more than three types of contact 

information are required, repeat the X12 PER segment, not to exceed two repetitions..

e. Approved Transaction Flow: There is no change to the transaction flows for the 

DLMS 945A when the distribution code = 111 documenting a supply status transaction in 

support of the Retail Supply and Transportation Interchange.

f. Alternatives: Require ILS-S to access the Enterprise Data Collection Layer (EDCL) 

to retrieve the in-checker ID and full name. Although ILS-S (Retail Air Force Supply) uses the 
Page 3 Attachment, ADC 1055

EDCL for several processes, CMOS does not send transportation/shipment data to the EDCL. 

Thus, this alternative is not feasible at this time.

5. REASON FOR CHANGE: ILS-S cannot efficiently research late or missing outbound 

shipments. The in-checker code is a required data element on the ILS-S shipment suspense card 

(SSC) transaction. Today, ILS-S puts ‘ESS’ in the in-checker code field on the SSC input and 

requires off-line research to identify the in-checker. Having the CMOS transportation inchecker’s name and code will allow ILS-S users to more efficiently track late outbound 

shipments and provide definitive asset visibility information.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: The major advantage to this change is that it provides the ability for 

supply users to have the transportation in-checker full name and in-checker code for each 

shipment that originated in the retail supply system. This additional information will allow for a 

more efficient research of lost and late outgoing shipments from retail supply accounts.

b. Disadvantages: None noted.

7. ESTIMATED TIME LINE/IMPLEMENTATION TARGET:

a. CMOS target implementation and test dates for this requirement are:

(1) Projected testing – July 22, 2013 to October 3, 2013. This testing includes 

Component Validation and Integration (CV&I) and Qualification Evaluation Testing (QET).

(2) Worldwide fielding - Scheduled for February 2014.

b. ILS-S will develop their component and perform integration testing with CMOS 

during the July-October 2013 period.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None identified by Air Force.

9. IMPACT:

a. New DLMS Data Elements: Add transportation in-checker code and transportation 

in-checker name.

b. Changes to DLMS Data Elements: There are no changes to existing DLMS data 

elements.

c. Automated Information Systems (AIS):

(1) Air Force

(a) CMOS – add the transportation in-checker ID, full name, and contact 

information to the DLMS 945A in-check status for ILS-S activities.
Page 4 Attachment, ADC 1055

(b) ILS-S – be able to receive the transportation in-checker ID and full 

name from CMOS in the DLMS 945A.

(2) Other Component AIS - Implementation is optional for other systems that 

either have implemented an interface with CMOS or plan to do so in the future. Prior 

coordination with CMOS is required.

(3) Integrated Data Environment (IDE) Global Transportation Network (GTN) 

Convergence (IGC) and other DOD Enterprise Visibility systems – Implementation is optional.

d. DLA Transaction Services: When provided by CMOS in the DLMS 945A, pass the

transportation in-checker ID, full name, and optional contact information to the designated RICTo supply activity in the transaction.

e. Non-DLA Logistics Management Standards Publications: Air Force should 

update any local policies and procedures implementing this required change.
Page 1 Enclosure 1, ADC 1055

Enclosure 1, DLMS Supplement Revisions

Item 

#

Location DLMS 945A, Materiel Release Advice Reason

1. DLMS 

Introductory 

Notes

Add ADC 1055 to DLMS Introductory Note 6: 

- ADC 1055, Add Cargo Movement Operations System 

(CMOS) Transportation In-checker Identification 

Information to the DLMS 945A Materiel Release Advice 

in Support of the Retail Supply and Transportation 

Interchange

To identify DLMS 

changes included in the 

DLMS Supplement

2. 1/PER/080 Open PER Segment in Loop ID 0100:

DLMS Note:

1. Only use when this transaction supports the Retail 

Supply and Transportation Receipt and 

Acknowledgement Interchange (See DLM 4000.25, 

Volume 3, Chapter 2).

2. Used in conjunction with a distribution code = “111”.

3. May use up to two repetitions of the PER Segment to 

provide all applicable contact information. Repeat the 

PER01-PER02 in the second repetition to satisfy syntax

requirements.

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

5. See ADC 1055.

Open segment to enable 

addition of in-checker 

information.

3. 1/PER01/080 Open PER01 and add qualifier SH and DLMS Note:

SH Shipper Contact

DLMS Note:

1. Use to identify the transportation in-checker.

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

3. See ADC 1055.

Establish code to 

identify the 

transportation inchecker function and 

limit use to the supplytransportation retail 

interface with CMOS.

4. 1/PER02/080 Open PER02 and add DLMS Note

DLMS Note: 

1. Identify transportation in-checker full name in First 

Name Middle Initial Last Name sequence, without any 

special characters (e.g., period, commas, and apostrophe). 

If there is no middle initial, insert NMN in place of the 

middle initial.

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

3. See ADC 1055.

Provide business rules 

for constructing full 

name.
Page 2 Enclosure 1 to ADC 1055

Item 

#

Location DLMS 945A, Materiel Release Advice Reason

5. 1/PER03/080 Open PER03 and add DLMS Note

DLMS Note:

1. Use to identify the preferred method of communication 

in the first repetition. If necessary, use PER05/6 and 

PER07/8 to identify additional communication numbers. 

If necessary, use an additional repetition of the PER 

segment to identify the email address and fax numbers

(commercial and DSN).

2. Do not include blank spaces, dashes or parentheses 

between numbers.

3. DLMS enhancement; see introductory DLMS note 4e.

4. See ADC 1055.

TE Telephone

DLMS Note: Use to identify the commercial telephone. 

Include the area code, number and extension, if 

applicable.

EM Electronic Mail

DLMS Note: Use in second repetition of the PER to 

identify the applicable email address.

Provide ability to pass 

additional contact

information.

6. 1/PER04/080 Open PER04 Provide ability to pass 

additional contact 

information.

7. 1/PER05/080 Open PER 05 and add DLMS Note

DLMS Note:

1. Use to identify an alternate, or secondary, 

communication number that can be used to contact the

specified POC. If not used, leave blank.

2. Do not include blank spaces, dashes, or parentheses 

between numbers.

3. DLMS enhancement; see introductory DLMS note 4e.

4. See ADC 1055.

AU Defense Switched Network

DLMS Note: Use to identify the DSN telephone number

and extension, if applicable.

FX Facsimile

DLMS Note: Use in second repetition of the PER to 

identify the applicable commercial FAX number.

Provide ability to pass 

additional contact 

information.

8. 1/PER06/080 Open PER06 Provide ability to pass 

additional contact 

information.
Page 3 Enclosure 1 to ADC 1055

Item 

#

Location DLMS 945A, Materiel Release Advice Reason

9. 1/PER07/080 Open PER07 and add DLMS Note

DLMS Note:

1. Use to identify an alternate, or secondary, 

communication number that can be used to contact the

specified POC. If not use, leave blank.

2. Do not include blank spaces, dashes, or parentheses 

between numbers.

3. DLMS enhancement; see introductory DLMS note 4e.

4. See ADC 1055.

IT International Telephone

DLMS Note: Include country and city code.

WF Work Facsimile Number

DLMS Note:

Use in second repetition of the PER to identify the 

applicable DSN FAX number.

Provide ability to pass 

additional contact 

information.

10. 1/PER08/080 Open PER08 Provide ability to pass 

additional contact 

information.

11. 1/PER09/080 Open PER09 and add DLMS Note:

DLMS Note:

1. Identify the transportation in-checker identification 

code with the appropriate three position numeric value.

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

3. See ADC 1055.

Provide business rules 

for inclusion of inchecker ID code and 

limit to three-position 

numeric value.
Page 1 Enclosure 2, ADC 1055

Enclosure 2, PDC 1055 Comment Resolution

Submitter Response/Comment Resolution

1. DLA DLA concurs w/o comment. Noted.

2. Army Concurs. Noted.

3. Navy The Navy concurs with PDC 1055 as written 

and requests no changes.

Noted.

4. Air Force AF concurs. Noted.

5. Marine Corps Headquarters Marine Corps has reviewed the 

subject PDC and concurs with the following 

comment: In addition to adding the Incheckers name, adding the phone number 

would be beneficial.

DLMS 945A and DLM 4000.25 

Volume 3 language updated to 

also include contact information, 

such as phone numbers.

6. DLA 

Transaction 

Services

Not convinced that PII is a real issue here 

and it seems the PDC says it is not. "There 

appears to be no clear violation of any PII 

rules with adding the two pieces of inchecker data."

DLA Transaction Services does not 

normally modify content of transaction 

copies furnished to these systems. 

PII discussion deleted from ADC.

DAAS requirement to filter the 

data on outbound transactions is 

deleted.

Cover letter and impact 

assessment modified to state that 

implementation of the ADC is 

optional for downstream systems. 

Basically, this allows DAAS to 

just process the transactions per 

standard business rules, and leave 

it up to the downstream/

consuming AIS' to decide if they 

want to store the data or just drop 

it on the floor, while still 

providing the Air Force their 

internal requirement to identify 

the in-checker.

7. USTRANSCOM USTRANSCOM votes 'approve' on the 

attached PDC.

Noted.