DEFENSE LOGISTICS AGENCY

 HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

 FORT BELVOIR, VIRGINIA 22060-6221

October 27, 2020

MEMORANDUM FOR THE RECORD

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

DAAS Manual Biennial Administrative Update

The attached approved administrative change to DLM 4000.25, Defense Logistics 

Management Standards is effective immediately. This administrative change does not change or 

eliminate any existing procedures, or add any new procedures.

Point of contact is Ms. Rita Williams, EBSO Publications lead,

email: Rita.Williams@dla.mil.

THOMAS A. DELANEY 

Director, Enterprise Business Standards Office

Attachment
Attachment, ADC 1380

Page 1

ADC 1380 

DAAS Manual BiennialAdministrative Update

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Jerry Caudill (937-228-2667, Jerry.Caudill.ctr@dla.mil), Michael 

Scott (937-228-2667, Michael.Scott.ctr@dla.mil)

b. Functional POC: Clarissa Elmore, Defense Automatic Addressing System (DAAS)

(937-343-8438, Clarissa.Elmore@dla.mil) 

2. FUNCTIONAL AREA LOGISTICS AND TRANSACTION CHANGES: Enterprise 

Data Solutions (EDS) Portfolio, DAAS

a. Primary/Secondary Functional Area: DLA Enterprise Data Solutions (EDS) 

Portfolio, Defense Automatic Addressing System (DAAS)

b. Primary/Secondary Functional Process: Update to DLM Publication DLM 

4000.25-4 Defense Automatic Addressing System (DAAS) Manual

3. REFERENCE: DLM 4000.25-4, Defense Automatic Addressing System (DAAS) 

4. APPROVED CHANGE(S):

a. Brief Overview of Change: Administrative changes to DLM Publication 4000.25-4,

Defense Automatic Addressing System (DAAS) Manual. These are administrative updates to 

the publication only; this change contains no substantive changes to standards, business rules, or 

transaction processing. 

b. Background: This is an administrative change to the transactions referenced in the 

DAAS Manual (see: 3. Reference). DAAS has been supporting non-logistics EDI-based 

transactions for the past 30 years. EDI is the exchange of routine business transactions from one 

computer system to another by standardized message formatting.

c. Approved Change in Detail: This Administrative change updates the following files 

in Defense Logistics Manual (DLM) 4000.25-4 Defense Automatic Addressing System (DAAS). 

(1) Update Chapter 3 - Customer Procedures, to reflect new communication 

protocols used. 

C3.3.2. (preceding text not shown) The DISN/Secure File Transfer Protocol 

(SFTP)/AS2/HTTPS/SMTP/IBM WebSphere MQ provide long haul and area data 

communications and interconnectivity for DoD systems.

(2) Update Chapter 4 - DAAS Processing, to reflect new communication 

protocols used.

C4.2.5. (preceding text not shown) In addition, DAAS uses AS2 Protocol, SMTP, and IBM

Websphere MQ, a guaranteed delivery transport from an IBM Websphere MQ origin to an IBM

Websphere MQ configured destination. This supports customer needs for guaranteed delivery, 
Attachment, ADC 1380

Page 2

while continuing to support existing data formats, such as Joint Army-/Navy-Air Force 

Publication (JANAP) messages and modified DDN file formats. DAAS electronic data 

interchange (EDI) applications also make use of IBM Websphere MQ and Virtual Private 

Network (VPN) connections to transport information in the ANSI ASC X12 and XML formats. 

(3) Update Chapter 5 Communications, to reflect administrative 

changes. 

C5.4.1.3. Translation. After receiving a correct EDI envelope control structure, the GEX 

eBusiness Gateway will attempt to translate the EDI format. When the translation process 

identifies inconsistencies with agreed upon syntactical standards, the gateway will return to 

the sender a coded error acknowledgment transaction. (See DAAS Manual C5.4.2.

regarding the DLMS 997 Functional Acknowledgment IC—DLM 4000.25, DLMS 

Volume 1, Appendix 1.) 

(intervening text not shown) 

C5.4.2. DLMS IC Implementation Convention 997, Functional Acknowledgment (all 

subsequent references are such as “the 997 IC”). 

(4) Update Appendix 1 – Defense Logistics Agency Transaction 

Services Profiles, to reflect new communication protocols used and IDE processing 

moved to DAAS. 

AP1.2.2.2.1. DAAS Single Gateway (DSG). As an integral part of the overall SOMA 

System, the majority of the communication gateway components of DSG are deployed in 

the Demilitarized Zone (DMZ) while MQ and SMTP gateways are deployed in the BLZ 

(Business Logic Zone) servers software and hardware components of the DSG reside in 

the DAAS Demilitarized Zone (DMZ) providing a custom-developed, multi-tiered secure 

front-end communications service for the DAAS; utilizing communication protocols, such 

as, SFTP, IBM MQ, AS2, HTTPS, SMTP, etc. Connections into the DSG are prevented 

from directly accessing the DAAS internal enclave utilizing custom developed Proxy 

servers. All DSG communication attempts, addresses, interactions, and data exchanges

are authenticated and logged. 

AP1.2.2.2.2. Service Oriented Messaging Architecture (SOMA). SOMA provides 

message validation, message transformation, back-end authentication, and logging 

services, and transmission services. SOMA, as a primary routing services, processes 

DLSS, EDI, UDF formatted messages. primarily processes files and messages containing 

DLSS formatted transactions.Messages may contain one or more transactions. SOMA 

receives and transmits files and messages using wide array of transmission protocols 

including IBM WebSphere MQ, HTTPS, AS2, SMTP, and SFTP. Single messages are 

also transmitted and received using the IBM MQ transport. Messages with multiple 

transactions may be sent and received using SMTP. SOMA performs a number of other 

functions, including: 

(intervening text not shown) 

AP1.5.1. General. DAAS, along with the DLA Logistics Information Service, have 

assumed responsibility for the sustainment of the DLA IDE. DLA IDE function within 
Attachment, ADC 1380

Page 3

the DAAS environment is embedded within the SOMA/DSG operational parameters. 

(intervening text not shown) 

AP1.5.3. Discussion: Per the DLA HQ IDE Transition Initiative, DAAS has migrated 

and integrated all IDE interfaces from DISA into the existing DAAS architecture 

(SOMA/DSG). Since its completion, the existing IDE mission, services, and interfaces 

have been incorporated and considered part of DAAS proper, at which time the IDE 

profile has ceased to exist and be considered a part of the standard DAAS business through 

the use of its various AIS applications, including but not limited to the DSG, SOMA, and 

GEX. Currently the entirety of the Non Secure Internet Protocol Router Network 

(NIPRNet) and the Secure Internet Protocol Router Network (SIPRNet) portions of IDE 

environment have been transitioned into the DAAS infrastructure. The Secure Internet 

Protocol Router Network (SIPRNet) portion of IDE is slated to complete transition at the 

end of 2017. 

(5) Update Appendix 2 – International Logistics Communication 

System (ILCS) to reflect updated software communication systems and multi-tiered 

logistics routing system.

AP2.2. SYSTEM DESCRIPTION 

The ILCS is an internet PC and UNIX based software communications system... 

(intervening text not shown) 

AP2.2.1. SOMA. A highly reliable, high availability multi-tiered logistics routing 

system utilizing Oracle relational database environment that provides... 

d. Revisions to Defense Logistics Manuals: Administrative changes to DLM 

Publication 4000.25-4 DAAS Manual

e. Proposed Transaction Flow: No Change

5. REASON FOR CHANGE: This is an administrative update to DLM 4000.25-4, DAAS to 

reflect changes resulting from the biennial review.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Updates documentation based on standard biennial review cycle.

b. Disadvantages: None

7. ASSUMPTIONS USED OR WILL BE USED IN THE CHANGE OR NEW 

DEVELOPMENT: None

8. ESTIMATED TIME LINE/IMPLEMENTATION TARGET: Upon publication of this 

ADC 

9. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None Identified. 
Attachment, ADC 1380

Page 4

10. IMPACT: 

a. New/Changes to DLMS Data Elements: None

b. Automated Information Systems (AIS): None

c. Defense Automatic Addressing System (DAAS): No impact—administrative 

updates to DLM 4000.25-4 DAAS Manual only 

d. Non-DLM Publications: No changes