DEFENSE LOGISTICS AGENCY

HEADQUARTERS

 8725 JOHN J. KINGMAN ROAD

FORT BELVOIR, VIRGINIA 22060-6221

July 13, 2018 

MEMORANDUM FOR SUPPLY PROCESS REVIEW COMMITTEE (PRC) MEMBERS

SUBJECT: Administrative Approved DLMS Change (ADC) 1265, Administrative Update to 

DLM 4000.25-4, Defense Automatic Addressing System (DAAS) to Include New 

Appendix 8 Non-Logistics Electronic Data Interchange (EDI) Support. 

The attached administrative change to DLM 4000.25-4, Defense Automatic 

Addressing System (DAAS) is approved effective upon publication of this ADC. 

Addressees may direct questions to Ms. Sylvia Williams, e-mail: 

sylvia.williams@dla.mil, or Mr. Frank Napoli, email: frank.napoli.ctr@dla.mil. 

HEIDI M. DAVEREDE

Director

Enterprise Business Standards Office

Attachment

As stated 

cc: 

DAAS
Attachment, ADC 1265

Page 1

Attachment to Administrative ADC 1265

Administrative Update to DLM 4000.25-4 DAAS to Include New 

Appendix 8 Non-Logistics Electronic Data Interchange (EDI) 

Support

1. ORIGINATING SERVICE/AGENCY AND POC INFORMATION:

a. Technical POC: Gary Wooddell, DLA Defense Automatic Addressing System 

(DAAS), gary.wooddell@dla.mil; 937-656-3830

b. Functional POC: Clarissa Elmore, DLA DAAS, clarissa.elmore@dla.mil; 937-656-

3770 

2. FUNCTIONAL AREA LOGISTICS AND TRANSACTION CHANGES: Defense 

Automatic Addressing System (DAAS).

a. Primary/Secondary Functional Area: Electronic Business (EBUS)

b. Primary/Secondary Functional Process: DOD Data Services (DDATA)

c. Logistics and Transaction Changes:

 Category  Category  Category

Billing Physical Inventory Contract Admin

Discrepancies / Deficiencies MILSTRAP DoDAAD

Serialization MILSTRIP MAPAD

Small Arms/Light Weapons MRA LMARS

pRFID Disposition X DLM Publications

GFP DOD BRAC

3. REFERENCES:

a. DLA General Order (GO) No. 12-17; Includes name change from “Transaction 

Services” to “Defense Automatic Addressing System (DAAS)”

b. DLM 4000.25-4, DAAS Manual
Attachment, ADC 1265

Page 2

4. REQUESTED CHANGE(S):

a. Brief Overview of Change: This is an administrative change only; there is no change 

to the current transaction processing. This change adds a new Appendix 8 to the DAAS Manual 

that describes the current, existing support of non-logistics EDI-based transactions. It also 

implements multiple administrative changes throughout the manual text to improve clarity, 

accuracy, and readability, with no substantive change to the meaning.

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

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

transactions since 1990. Electronic data interchange (EDI) is the exchange of routine business 

transactions from one computer system to another by standardized message formatting.

c. Approved Change in Detail: 

(1) Add Appendix 8 to DAAS Manual to document non-Logistics EDI 

transactions support through DAAS (see Enclosure 1). The Enterprise Business Standards 

Office/Defense Logistics Management Standards (DLMS) do not provide Implementation 

Conventions (ICs) for Financial1

, Transportation, and Procurement/Acquisition transactions 

since the Enterprise Business Standards Office (EBSO) does not have cognizance over these 

domains. The DAAS Electronic Business (EBUS) profile and EDI processing programs support 

these standards through the requirements received from customers.

(2) Update responsibilities in Chapter 1 to reflect organizational and name 

changes. 

(3) Remove references to Customer Wait Time (CWT). DAAS does not 

calculate CWT. The Components calculate CWT based on the Logistics Response Time (LRT) 

report data that DAAS provides to the Components. 

(4) Document the transition of the DLA Integrated Data Environment (IDE) that 

is on the Non Secure Internet Protocol Router Network (NIPRNet) into the DAAS infrastructure.

(5) Remove references to the use of the Postal Service to deliver logistics 

transactions, printed on GSA Mailers; DAAS no longer supports this service.

Staffing Note: Publication of this change formally withdraws Proposed DLMS Change (PDC) 

62. 

(6) Update the name of the “MQ Series” application to the current product name, 

“IBM Message Queuing (MQ)”, and remove the specific section of the manual describing IBM 

MQ since it is a supporting/infrastructure application.

 1 “Financial” in this context applies in the broadest sense of the term, encompassing the 

Accounting, Logistics, and Treasury domains. EBSO has cognizance over and provides DLMS 

procedures for Logistics financial exchanges in DLM 4000.25 Volume 4, Military Standard Billing 

System – Finance, and publishes the ICs (810L, 812L, 812R) that support those procedures.
Attachment, ADC 1265

Page 3

(7) Update clerical and administrative references to spell out acronyms for first 

time usage and minor administrative rewrites to sections for clarity and accuracy.

(8) Update URLs and hyperlinks throughout the manual.

d. Revisions to DLM 4000.25 Manuals: Adds new Appendix 8 to DLM 4000.25-4,

DAAS Manual (see Enclosure 1).

e. Transaction Flow: No Change

f. Alternatives: None

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

reflect changes found during the bi-annual review and add new Appendix 8, Non-logistics EDI 

Support.

6. ADVANTAGES AND DISADVANTAGES:

a. Advantages: Updates documentation to reflect all transactions flowing through the 

DAAS.

b. Disadvantages: None.

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

ADC.

8. ESTIMATED SAVINGS/COST AVOIDANCE ASSOCIATED WITH 

IMPLEMENTATION OF THIS CHANGE: None Identified

9. IMPACT:

a. New DLMS Data Elements: None

b. Changes to DLMS Data Elements: None

c. Automated Information Systems (AIS): None

d. Defense Automatic Addressing System (DAAS): No impact. DAAS is currently 

processing these type of transactions. This is an administrative change to document these 

transactions flowing through the DAAS.

e. Non-DLM 4000.25 Series Publications: None identified.
Enclosure 1, ADC 1265

Page 1

Enclosure 1

AP8. APPENDIX 8

NON LOGISTICS ELECTRONIC DATA INTERCHANGE 

(EDI) SUPPORT 

AP8.1. General. The Defense Automatic Addressing System (DAAS) has been 

supporting non-Logistics EDI-based transactions for the past 30 years. Electronic Data 

Interchange (EDI) is the exchange of routine business transactions from one computer 

system to another by standardized message formatting. DAAS’ primary business has 

been to accurately route electronic logistics data and provide an interoperable gateway 

to exchange logistics data in disparate data formats between various federal activities 

and commercial trading partners. However, the Electronic Business (EBUS) profile has 

grown over the years and spans much further than logistics processing. DAAS currently 

provides data translation and routing support for several non-logistics based transaction 

categories supporting Department of Defense (DoD) business, including: 

Transportation, Financial, and Procurement/Acquisition. The DAAS’ EBUS profile 

processes financial, transportation, and procurement/acquisition transactions in a 

variety of formats including: Accredited Standards Committee (ASC) X12 standards, 

eXtensible Markup Language (XML), User Defined Formats (UDF), Intermediate 

Document (IDOC), XML IDOC, Portable Document Format (PDF), and Comma 

Separated Values (CSV), depending on customer requirements. The Defense Logistics 

Management Standards (DLMS) do not provide implementation conventions (ICs) for 

financial1, transportation, and procurement/acquisition transactions since those domains 

are not governed by the DLMS Program Office. 

AP8.1.1. eBusiness System Description 

AP8.1.1.1. EDI Gateway System Process. EDI provides standard 

transaction formats for use in the automated, machine-to-machine, exchange of 

eBusiness transactions between the DoD Components/participating Agencies, and 

their commercial sector trading partners. The Global Exchange (GEX), IBM 

Transformation Extender (ITX), and Ab Initio applications provide a high volume, 

high capacity environment to meet the needs of their customers. DAAS currently 

processes over 10 million EDI transactions each day and supports a vast variety of 

capabilities based on customers’ requirements by providing routing and delivery of 

data, based on frequency and priority, performing translation of multiple formats 

 1 “Financial” in this context applies in the broadest sense of the term, encompassing the 

Accounting, Logistics, and Treasury domains. EBSO has cognizance over and provides DLMS 

procedures for Logistics financial exchanges in DLM 4000.25 Volume 4, Military Standard Billing 

System – Finance, and publishes the ICs (810L, 812L, 812R) that support those procedures.
Enclosure 1, ADC 1265

Page 2

(MILS, X12, XML, UDF, XML IDOC, PDF/CSV) if applicable, monitoring and alert 

notifications based on necessity, as well as data integrity. Protocols such as IBM 

Message Queuing (MQ), Secure File Transfer Protocol (SFTP), Hyper Text Transfer 

Protocol Secure (HTTPS), and Applicability Statement 2 (AS2) are supported. 

DAAS can provide encryption/decryption, compression/decompression, and special 

logic of data as needed. A vast number of reporting capabilities are available 

including traffic, communication, transaction type, data-quality, error, as well as 

customized customer-driven. The EDI team provides fast and reliable customer 

service 24/7. 

DAAS operates a centralized DoD eBusiness Communications Gateway capability 

that provides standard EDI and XML transaction routing, delivery, archiving, 

translation, and Value Added Network (VAN) delivery services through the following: 

AP8.1.1.2. DoD GEX Gateway. In providing EDI telecommunication 

services, DAAS utilizes the standard GEX software suite developed to support the 

DoD Electronic Commerce Infrastructure. The GEX application provides the 

capability to securely receive/send transactions via many different 

telecommunication protocols, sort/route the transactions, apply the appropriate 

translation/mapping utilities, provide decoding/validation of X12 syntax rules, log all 

activities, archive files, alert users of errors, and apply routing/distribution list 

processes. 

AP8.1.1.3. Transaction Translation. The COTS IBM ITX, and Ab Initio 

mapping and transformation software tool sets currently provide the translation 

capability to convert incoming transaction formats into the appropriate outgoing 

transaction formats, via business mapping rules. There are specific maps used to 

translate financial, procurement/acquisition, and transportation transactions that are 

outside of the DLMS logistics guidelines. Custom maps for data translation can be 

developed via approved DAAS methodologies. Utilizing approved methodologies 

ensures that the maps will integrate with the DAAS environment and are properly 

supported. Customers with questions can contact the Electronic Business Program 

Manager. Maps developed outside of core services are paid by customers, maps are 

determined by the inbound format to the outbound format. Some customers also have 

requirements for data encryption, validation, or special mapping. 

AP8.1.2. Financial / Transportation / Procurement Transactions. All EDI 

transactions are archived in accordance with DoD Instruction 5015.02 for audit 

purposes. Use of database and file lookups exist for data validation and routing 

purposes. 

TREASURY:

- Data exchanges with the Treasury supporting DoD Financial Management

- Single Line of Accounting (SLOA) data validation
Enclosure 1, ADC 1265

Page 3

PROCUREMENT:

- Procurement Data Standard

- Purchase Request Data Standard

- Wide Area Workflow (WAWF)/invoicing, Receipt, Acceptance, and Property 

Transfer (iRAPT) Support

- Clause Logic Support

TRANSPORTATION:

- Shipment information processing via EDI 210, 214, 315 transactions

AP8.1.3. Financial / Transportation / Procurement Regulations: DoD 

regulation documents include: 

Defense Logistics Management Standards (DLMS) for logistics transactions:

(http://www.dla.mil/HQ/InformationOperations/DLMS/)

Defense Transportation Electronic Business (DTEB) for transportation transactions:

(http://www.ustranscom.mil/cmd/associated/dteb/) 

Defense Procurement Acquisition Policy (DPAP) for procurement transactions:

(http://www.acq.osd.mil/dpap/pdi/eb/index.html)

Federal Acquisition Regulations (FAR), Defense Federal Acquisition Regulation 

Supplement (DFARS), and Procedures Guidance and Information (PGI) for 

acquisition transactions: 

(https://www.acquisition.gov/far/), 

(https://www.acquisition.gov/?q=Supplemental_Regulations), 

(http://www.acq.osd.mil/dpap/dars/about_dfarspgi.html)

The DAAS EBUS profile and EDI processing programs supports these standards 

through the requirements received from customers.
Enclosure 2, ADC 1265

Page 1

Enclosure 2

Administratively Updated1 (Existing) 

Chapters 1–5 and Appendices 1–7

C1. CHAPTER 1

GENERAL INFORMATION

C1.1. AUTHORITY

This manual is issued under authority of Department of Defense Instruction (DoDI) 

4140.01, Supply Chain Materiel Management Policy December 14, 2011. 

C1.2. PURPOSE

C1.2.1. This manual provides policy and establishes procedures for the use 

and operations of both the Defense Logistics Agency’s (DLA) Information 

Operations Enterprise Data Solutions (EDS) Defense Automatic Addressing 

System (DAAS) (formerly known as DLA Transaction Services) as well as those of 

the International Logistics Communications System (ILCS). The DAAS standards 

are administered by the Defense Logistics Management Standards (DLMS) 

Program Office (also known as the Enterprise Business Standards Office 

(EBSO) ) and are operated by DAAS at its two computer facilities in Dayton, Ohio 

and Tracy, California.

C1.2.2. Neither DAAS nor ILCS is a single system, but rather a collection of 

accredited Automated Information Systems (AISs) that receive, validate, edit, 

route, archive, and transmit DoD logistics traffic. Each DAAS AIS is categorized 

under one of three profiles: DoD Data Services (DDATA), DoD Gateway 

(DGATE), and the DoD eBusiness Gateway (EBUS). DDATA systems provide 

access to logistics data, reports, and data repositories; DGATE systems process 

transactions that are predominantly in the Defense Logistics Standard System 

(DLSS) (legacy 80 record position) format; and EBUS systems process 

transactions in the Defense Logistics Management Standards (DLMS) (X12 and 

extensible markup language (XML)) variable-length formats. These systems, 

working in conjunction, enable DAAS to function as a service organization 

providing customers continuous access to the DAAS, Telecommunications/ 

Automatic Data Processing (ADP) and programming capabilities. This manual 

provides a framework and updated procedures to move the DoD away from the 

use of DoD unique logistics data exchange standards (e.g., legacy 80 record 

 1 Changes/additions are marked in Bold/Italics font.
Enclosure 2, ADC 1265

Page 2

position) to Accredited Standards Committee (ASC) X12 standards, or other 

recognized standards (XML), as a first step in moving transactional-based logistics 

business processes towards international open data exchange standards. 

C1.3. APPLICABILITY

This manual applies to the Office of the Secretary of Defense, the Military 

Departments, the Joint Staff, the Combatant Commands, the Office of the DoD 

Inspector General, the Defense Agencies, the DoD Field Activities, and all other 

organizational entities within the Department of Defense (hereafter referred to as 

“DoD Components”). It also applies, by agreement, to other civilian organizations 

participating in the DLSS (legacy 80 record position) format or DLMS; including the 

General Services Administration (GSA), Federal Aviation Administration (FAA), 

United States Postal Service (USPS), many other federal non-defense 

organizations, and other state level government entities as well as any 

commercial entities wishing to utilize the DAAS. 

C1.4. POLICY 

DoD policy states that:

C1.4.1. DAAS procedures will be disseminated, as required, to the using 

levels of the DoD Components. Supplemental procedures issued by the DoD 

Components or other organizations are authorized when additional detailed 

instructions are required.

C1.4.2. DAAS corporate services will be used at all levels within each of the 

DoD Components. Exceptions for the intra-DoD Component technical services, 

when based on compelling operational or economic justification, will be considered 

under DoD Directive (DoDD) 8190.01E, Defense Logistics Management

Standards, January 9, 2015.

C1.4.3. The DoD Components will not duplicate the telecommunications 

support, archiving and storage, ASC X12 transaction translation, DLSS transaction 

transformation processes, or other transaction services being provided by DAAS.

C1.4.4. DAAS will be the logistics community’s authoritative source for endto-end system performance metrics.

C1.4.5. The DoD Components will program for and fund DAAS through their 

respective planning, programming, and budgeting system processes.

C1.5. RESPONSIBILITIES

C1.5.1. Under provisions of DoD Directive 8190.01E and DoD Manual 

4140.01, the Office of the Under Secretary of Defense for Acquisition and 

Sustainment (USD(A&S)) will oversee and direct the implementation of and 

compliance with this manual, as it relates to DAAS and its subordinate systems 
Enclosure 2, ADC 1265

Page 3

including the DAAS and the ILCS. In carrying out this responsibility, the 

(USD(A&S) will:

C1.5.1.1. Approve the development of new DAAS assignments or 

revisions to existing assignments.

C1.5.1.2. Provide the DLA Information Operations Program Executive 

Office (J62) with policy guidance concerning the design, development, 

documentation, and maintenance of DAAS’ procedures.

C1.5.1.3. Review and approve the DLA Information Operations 

Program Executive Office (J62) plans, priorities, and schedules for DAAS 

modernization.

C1.5.1.4. Endorse new systems, improvements, and expansion of 

DAAS.

C1.5.1.5. Approve or disapprove the DoD Component requests to use a 

system other than DAAS.

C1.5.1.6. Resolve issues submitted by the DLA Information Operations 

Program Executive Office (J62) concerning resources, policy, and requests for 

deviations or waivers from the use of DAAS. 

C1.5.1.7. Serve as Tri-chair of the Joint Business Management Services 

(JBMS) Strategic Operational Requirements Committee (ORC).

C1.5.2. The Program Executive Officer (PEO) of DAAS will designate a 

Program Manager for the DAAS, who in-turn will: 

C1.5.2.1. Perform analysis and design functions, in coordination with 

the DoD Components, to implement guidance and instructions provided by the 

ASD (L&MR) and to ensure the involvement of ADP/telecommunications planning 

in an integrated system design. 

C1.5.2.2. Recommend system improvements and additional policy, as 

required, during the development of procedures.

C1.5.2.3. Develop, publish, and maintain this manual in a current 

status. This includes the responsibility to: 

C1.5.2.3.1. Evaluate and coordinate proposed system revisions 

with the DoD Components, affected Federal Agencies, foreign governments, 

contractors, and industrial organizations. A copy of all revision proposals will be 

furnished to the ASD (L&MR).

C1.5.2.3.2. Resolve issues concerning procedural matters within 

90 days after receipt of all comments from the DoD Components. Issues affecting 
Enclosure 2, ADC 1265

Page 4

resources or policy will be referred, together with comments of the DoD 

Components and a recommendation of the appropriate system administrator, to 

the ASD (L&MR) for decision.

C1.5.2.3.3. Make available to the ASD (L&MR) and to the DoD 

Components a quarterly status review of all proposed revisions or changes to the 

DAAS that have not yet been approved or implemented.

C1.5.2.3.4. Ensure compatibility of proposed revisions or changes 

to assigned systems. Coordination will be effected, with appropriate DLMS 

Process Review Committees (PRCs), and with designated Service/Agency system 

administrators prior to implementation. 

C1.5.2.4. Ensure uniform implementation of this manual, consistent with 

DoD Instruction (DoDI) 4140.01 and DoD Directive (DoDD) 8190.01E by:

C1.5.2.4.1. Reviewing all supplemental procedures issued by the 

DoD Components to ensure continuing conformance of revisions with the 

approved system.

C1.5.2.4.2. Reviewing implementation plans and implementation 

dates of the DoD Components and making recommendations for improvements.

C1.5.2.4.3. Conducting periodic evaluations to determine 

effectiveness of the system.

C1.5.2.4.4. Conducting periodic staff assistance visits to the DoD 

Component activities to determine compliance with prescribed system 

requirements and to furnish clarification to ensure uniform interpretation of DAAS’ 

requirements.

C1.5.2.4.5. Report to the ASD (L&MR) and the Director, 

Enterprise Business Standards Office, the findings and recommendations of 

evaluations and staff assistance visits, along with comments or concerns from

DoD Components.

C1.5.2.5. Participate in DLMS PRC meetings to represent a DAAS 

position on issues that may affect DAAS.

C1.5.2.6. Review and evaluate curricula of DoD and other DLMS 

participant training schools offering courses related to the DAAS and make 

recommendations for improvements.

C1.5.3. The Program Manager of DAAS will:

C1.5.3.1. Develop, operate, and maintain DAAS.
Enclosure 2, ADC 1265

Page 5

C1.5.3.2. Refer to the Director, EBSO, any apparent violation or 

deviation of DLMS/DLSS procedures encountered during systems operations or 

requested by the DoD Components or Participating Agencies.

C1.5.3.3. Notify DLA Enterprise Infrastructure Services (J64) of any 

new or projected telecommunications/ADP hardware requirements and provide 

immediate notification of equipment outages to DLA IT Operations Center (J63).

C1.5.3.4. Maintain an archival repository2 of all transactions and files 

processed by the DAAS.

C1.5.3.5. Maintain a shipment status correlation system to process 

Military Standard (MILS) Transaction Reporting and Accountability Procedures 

(MILSTRAP), and Materiel Receipt Acknowledgements (MRA). Prepare and make 

available the MRA Management Information Report (electronically) as required by 

the MILSTRAP Manual (DLM 4000.25-2 and its successor DLMS, DLM 4000.25.).

C1.5.3.6. Provide a Military Billing System (MILSBILLS) interfund billing 

transaction repository Interfund bills are retained in a readily accessible 

format for: (365 calendar days for DoD and 730 calendar days for Foreign Military 

Sales [FMS]) to accommodate requests for recoveries and retransmissions. The 

preceding procedures will be followed in accordance with DoDI 5015.02, DoD 

Records Management Program.

C1.5.3.7. Develop, operate, and maintain an AIS to manage DoD Fund 

Code repository.

C1.5.3.8. Provide a Materiel Obligation Validation (MOV) transaction 

repository to accommodate requests for recoveries and retransmissions.

C1.5.3.9. Develop, operate, and maintain an AIS for the production of 

Logistics Metrics Analysis Reporting System (LMARS), Logistics Response Time (LRT), 

reports.

C1.5.3.10. Compile, maintain, publish, and distribute MILSTRIP Military 

Routing Identifier and Distribution Codes with address data in DLM 4000.25-1.

C1.5.3.11. Develop, operate, and maintain an AIS to sustain the DoD 

Activity Address Directory (DoDAAD), and the Military Assistance Program 

Address Directory (MAPAD) per DLM 4000.25, Volume 6.

 2 All internal DAAS systems that retain documents/transactions must comply with the retention guidance from 

the DLA Records Officer and the National Archives and Records Administration (NARA) General Record 

Schedules (GRS), See ADC 1151.
Enclosure 2, ADC 1265

Page 6

C1.5.3.12. Develop, operate, and maintain an AIS to disseminate DAAS 

statistical data and provide Logistics Information Data Services (LIDS) reports.

C1.5.3.13. Develop, operate, and maintain an AIS to support the DoD 

Component/Participating Agency level requisition, excess materiel, and passive 

RFID tag tracking capabilities (Logistics On-Line Tracking System (LOTS)).

C1.5.3.14. Develop, operate, and maintain a data warehouse to support 

DoD Component and Participating Agencies. Provide capabilities to query, 

extract, view, analyze, data mine and develop reports on data processed by DAAS 

Logistics Data Gateway (LDG).

C1.5.3.15. Designate a primary and alternate focal point representative 

to serve on DLMS PRCs.

C1.5.3.16. Provide/designate the Chair, DLMS Technical Review 

Committee (TRC), as required by Department of Defense Manual (DoDM)

4140.01.

C1.5.3.17. Delegate official change proposals to the appropriate DAAS’ 

system administrator who will evaluate the cost and expected benefits.

C1.5.3.18. Accomplish internal training to ensure timely and effective 

implementation and continued operation of DAAS. 

C1.5.3.19. Serve as the DAAS Secretariat for the JBMS ORC.

C1.5.4. The Heads of the DoD Components and Other Participating 

Agencies will designate an office of primary responsibility to serve as their 

representative to the DLMS TRC. Also, identify to the designated DAAS’ TRC 

Chairman, the name of a primary and an alternate focal point representative to:

C1.5.4.1. Serve on the DLMS TRC (The Army, Navy/Marines, and Air 

Force, and DLA will name subject matter experts to cover issues, if required).

C1.5.4.2. Provide the DoD Component or Participating Agency position 

on DLMS/DAAS matters and have the authority to make decisions regarding 

procedural aspects.

C1.5.4.3. Ensure continuous liaison with the appropriate DAAS’ system 

administrator, the DoD Components, and participating external organizations.

C1.5.4.4. Perform the initial evaluation of all suggestions originating 

within the DoD Component or Participating Agency. For suggestions, submit an 

appropriate change request to the DLMS TRC chair (as designated by the 

Program Manager of DAAS) for processing. The originator’s TRC 

representative will determine any awards using the DoD Component or 

Participating Agency procedures.
Enclosure 2, ADC 1265

Page 7

C1.5.4.5. Submit revision proposals to the DAAS’ designated TRC 

Chairman with justification and expected benefits.

C1.5.4.6. Develop and submit to the DAAS’ designated TRC Chairman 

a single coordinated position on all system revision proposals within the time limit 

specified.

C1.5.4.7. Participate in staff assistance visits through on-site visitations 

in coordination with the Director, EBSO or the DAAS designated TRC Chairman, 

as appropriate.

C1.5.4.8. Implement approved systems and revisions thereto and 

provide the Director, EBSO and the DAAS designated TRC Chairman with semiannual status information concerning implementation of approved system 

revisions. This information will be submitted within 15 working days, after the end 

of a designated semi-annual cycle, and will begin with the first cycle following 

publication of the approved system change.

C1.5.4.9. Accomplish internal training to ensure timely and effective 

implementation and continued operation of Component services.

C1.5.4.10. Provide representation to joint system design and 

development efforts and evaluations of the DLMS in coordination with the 

appropriate DAAS system administrator.

C1.5.4.11. Ensure that operating activities that support the DAAS 

functions comply with this manual.

C1.5.4.12. Furnish to the DAAS system administrators copies of 

supplemental and internal procedures, and changes thereto, related to the 

operation of DAAS.

C1.5.4.13. Report to the applicable DAAS system administrator problems, 

violations, and deviations that arise during system operations.

C1.5.5. The Office of the Deputy ASD for Supply Chain Integration (SCI), the 

Office of the Secretary of Defense (OSD) Comptroller Business Integration Office 

and OSD Defense Procurement Acquisition Policy (Program Development and 

Implementation) will designate Co-Chairs to the JBMS ORC. This committee will 

provide prioritization and oversight of functional requirements for business 

transaction management services identified by the procurement, financial 

management and logistics communities at the enterprise level in order to best

achieve efficiencies, and meet functional strategy objectives established by 

Office of the OSD.

C1.6. PUBLICATION AND DISTRIBUTION OF THE MANUAL
Enclosure 2, ADC 1265

Page 8

C1.6.1. DAAS Manual. This Manual is published electronically. Hardcopy 

documents are not available. The Manual is available from the EBSO Website, 

Publications page. Any further distribution will be accomplished within the DoD 

Components or Participating Agencies based upon approved distribution data 

generated through their internal publication channels.

C1.6.2. Changes to the Manual are published electronically and are 

available on the EBSO Website at the location of the individual manual.

C1.7. SYSTEM MAINTENANCE

C1.7.1. Revisions to DAAS result from release or revision of DoD 

instructions, directives, policy changes, changes to the DLMS Manual, and 

recommendations of the appropriate system administrators or DoD Components.

C1.7.2. Submitting proposed DLMS or systems changes:

The DoD Component and participating Agency TRC representatives, 

authorized in section C1.8, below, and the heads of DoD logistics task groups may 

submit proposed critical changes to DAAS’ TRC Chairman in accordance with the 

change proposal instructions in DLM 4000.25-M, Volume 1, Chapter 3, Change 

Management. The change proposal template and instructions are available from 

the EBSO Website, Proposed Changes page. To contact the EBSO, please click 

“Contact EBSO” on the EBSO Website. 

Detailed instructions and review procedures are available at the above site.

C1.7.3 Submitting proposed changes to DAAS’ systems or processing rules:

DoD Component representatives may submit proposed critical changes to DAAS’ 

systems or their Service/Agency transaction processing rules via e-mail at 

https://www.transactionservices.dla.mil/daashome/customerassistance.asp

C1.8. DLMS TRC AND ILCS PRC REPRESENTATIVES

C1.8.1. The following Components or Agencies have been designated as 

representatives to the DLMS TRC:

Table C1.T1. DLMS TRC Representatives

AF Deputy Chief of Staff

Installations and Logistics

U.S. Air Force

ATTN: ILGP

Washington, DC 20330-0001
Enclosure 2, ADC 1265

Page 9

Table C1.T1. DLMS TRC Representatives

ARMY Commander

U.S. Army Materiel Command

Attn: AMCLG-SM

5001 Eisenhower Avenue

Alexandria, VA 22333-0001

ENTERPRISE BUSINESS 

STANDARDS OFFICE

Director

Enterprise Business Standards Office 

(EBSO) 

ATTN: DLA J-67B

8725 John J. Kingman Road STOP 6205

Fort Belvoir, VA 22060-6217

DAAS TRC Chairman

DAAS

Attn: eBusiness Program Manager

5250 Pearson Rd, Area A

Bldg. #207

Wright-Patterson Air Force Base (AFB), OH 

45433-5328 

DEFENSE FINANCE AND 

ACCOUNTING SERVICE 

TBD

DEFENSE INFORMATION 

SYSTEMS AGENCY

Director, Defense Information Systems 

Agency

Attn: Code B651

Washington, DC 20305-0001 

DEFENSE LOGISTICS 

AGENCY

Director, Defense Logistics Agency

Attn: J3322

8725 John J. Kingman Road, Suite 4230

Fort Belvoir, VA 22060-6221

DEFENSE NUCLEAR 

AGENCY

Director, Defense Nuclear Agency

Attn: LETS

Washington, DC 20305-0003 

GSA General Services Administration

Federal Supply Service Attn: FCSI, Room 701

1941 Jefferson Davis Highway

Arlington, VA 22202-450

MARINE CORPS Commandant of the Marine Corps

Attn: LPS1

2 Navy Annex 

Arlington Annex

Washington, DC 20380-1775 
Enclosure 2, ADC 1265

Page 10

Table C1.T1. DLMS TRC Representatives

NAVY Commander, Naval Supply Systems 

Command

Attn: 4C2B6

5450 Carlisle Pike

Mechanicsburg, PA 17055-0791

C1.8.2. The following Component organizations have been designated 

as representatives for the ILCS on the DAAS ILCS PRC:

Table C1.T2. ILCS PRC Representatives

AF Commander Air Force Security Assistance Center 

(AFSAC)

Attn: AFSAC/XRXD

Wright-Patterson AFB, OH 45433-5000

ARMY Commander United States Army (USA) Security 

Assistance Center (USASAC)

Attn: USASAC-MP/R

Alexandria, VA 22333-0001

ENTERPRISE BUSINESS 

STANDARDS OFFICE

Director

Enterprise Business Standards Office (EBSO) 

ATTN: DLA J-67B

8725 John J. Kingman Road STOP 6205

Fort Belvoir, VA 22060-6217

DAAS Program Manager

DAAS

Attn: DAAS

5250 Pearson Rd, Area A

Wright-Patterson AFB, OH 45433-5328 

NAVY Chief of Naval Operations

Attn: OP-631 H

Washington, DC 20350-2000
Enclosure 2, ADC 1265

Page 11

C2. CHAPTER 2

DEFENSE AUTOMATIC ADDRESSING SYSTEM 

(DAAS) OPERATIONS

C2.1. OVERVIEW

C2.1.1. DAAS Automated Information Systems (AISs) are operated and 

maintained by DAAS, who designs, develops, and implements logistics solutions 

to improve its worldwide customers’ requisition processing and logistics 

management processes. DAAS has an operational mission that includes 

receiving, editing, validating, routing, and delivering logistics transactions for the 

Department of Defense (DoD) Components and participating Agencies. It, also, 

provides value-added services for the various computer-readable logistics 

transactions, such as network and data interoperability, logistics system activity, 

Component/DoD-level logistics information services; and report generation. DAAS 

operates as a central DoD translator, that allows the DoD Component supply 

systems to speak the same language, by receiving data (often non-standard), 

editing and validating the transactions; and forwarding the transactions, in the 

correct format, to the proper destination. DAAS maintains two sites that operate 

24 hours a day/seven days a week/365 days a year. Mission critical applications 

are operated in parallel at both sites.

C2.1.2. DAAS along with its partner, DLMS Program Office, are the 

facilitators through which diverse DoD Component/Participating Agency supply 

systems are able to function as a uniform DoD supply system. DAAS plays an 

important and direct role in the electronic communications and logistics systems of 

the U.S. Government, working closely with planners, field commands, and 

operational supply and distribution networks/offices around the world. DAAS has 

built an effective, efficient communications environment permitting the 

transmission of time-sensitive information between defense activities and users 

worldwide. All transactions and files processed by the DAAS are maintained in an 

archive file that contains data from September 1994 to present. This pool of 

archived data and the associated ‘stand-alone’ repositories provides a store of 

logistics information that can be used for forecasting requirements and performing 

trend analysis.

C2.1.3. Several ‘stand-alone’ DoD repositories, operated by DAAS, maintain 

support for the primary mission of receiving, editing, validating, routing, and 

delivering more than one thousand Defense Logistics Standard Systems (DLSS) 

80 record position legacy format transaction document identifier codes (DICs), and 

the numerous Defense Logistics Management Standards (DLMS), Accredited 

Standards Committee (ASC) X12, eXtensible Markup Language (XML), and User 
Enclosure 2, ADC 1265

Page 12

Defined File (UDF) formats. These repositories contain current up-to-date 

information that is used in direct support of the DoD, Defense Logistics Agency 

(DLA), and DAAS missions. DAAS provides customers with the ability to access 

various transaction reports, perform research, and provide tracking of requisitions 

as they flow through the DoD supply chain to generate standard monthly, 

quarterly, semi-annual, and ad-hoc reports for DLA and the DoD 

Components/Participating Agencies. Special ad-hoc reports, related to logistical 

transaction processing, are accommodated by special request. DLA is regularly 

requested, by various Defense Investigative Agencies, to provide copies of 

transactions for specific vendors and/or time periods.

C2.1.4. DAAS provides images of transactions to numerous activities to 

support DoD Component total asset visibility pipeline tracking initiatives. The 

DAAS also provides an eBusiness gateway (EBUS) for distribution of electronic 

business (eB) transactions between the DoD Components, participating Agencies, 

and private sector trading partners, via multiple commercial Value Added 

Networks (VANs). The exchange of ASC X12 transaction sets and the translation 

services to map between DLSS legacy 80 record position format transactions and 

DLMS X12/XML formats has become more important to the DoD logistics 

community as it continues to migrate, from its legacy-based transaction processes, 

to new systems utilizing commercial off-the-shelf (COTS) software Enterprise 

Resource Planning (ERP) products, and ASC X12 commercial transaction 

formats.

C2.2. BENEFITS AND FUNCTIONS

C2.2.1. Using the DAAS infrastructure provides the following benefits:

C2.2.1.1. It simplifies communication procedures by permitting 

customers to batch different type transactions, addressed to multiple activities, into 

one message, which is then transmitted via the DAAS. This precludes both the 

need to segregate transactions by type or destination, and to transmit multiple 

separate messages directly to each destination.

C2.2.1.2. Both batch and near real-time processing are supported 

based upon user requirements.

C2.2.1.3. Validation and routing of selected transactions to the correct 

source of supply (SoS) by using both requisitioning channel data provided by the 

DoD Components/Participating Agencies, and current cataloging data provided by 

the DLA Logistics Information Service.

C2.2.1.4. The ability to edit discrete logistics transaction data elements.

C2.2.1.5. Visibility and traceability of transactions transmitted to and 

from the DAAS.

C2.2.1.6. The ability to recover, retransmit, intercept, and divert 
Enclosure 2, ADC 1265

Page 13

transactions transmitted to and from the DAAS.

C2.2.1.7. The delivery of specific logistics transaction data to the DoD 

Components/Participating Agencies.

C2.2.1.8. The creation of archival/historical transaction repositories and 

maintenance of data warehouses to facilitate the DoD Component/Participating 

Agency research and analysis.

C2.2.1.9. Compilation of statistical data and reports.

C2.2.1.10. Support to DoD Component/Participating Agency unique 

processing requirements, as authorized by the DAAS/International Logistics 

Communications System (ILCS) Administrator.

C2.2.1.11. Accumulation and storage of data needed to support the 

Logistics Metrics Analysis Reporting System (LMARS), and Logistics Response 

Time (LRT) processes.

C2.2.2. DAAS facilitates the following functions:

C2.2.2.1. Communications (network and data) interoperability.

C2.2.2.2. Functional logistics support and assistance.

C2.2.2.3. Logistics information repository, warehouse/archive.

C2.2.2.4. Logistics information reporting and distribution.

C2.2.2.5. Receipt, validation, revision, routing/delivery of logistics data.

C2.2.2.6. Operation of a clearinghouse that provides value-added 

services and data delivery.

C2.2.2.7. Operation of logistical transaction gateway services and 

logistical support nodes at two sites.

C2.2.2.8. Data accumulation, analysis, and transformation.

C2.3. DAAS CORE AND CUSTOM SERVICES

C2.3.1. Functioning as a DoD utility, the DAAS mission comprises both core 

(costs that are covered under DAAS Annual Operating Budget) and custom (a feefor-service charge) services. At the present time, the only services provided on a 

fee-for-service basis are those costs incurred for developing new ASC X12/XML or 

UDF translation maps that are not part of the core services offered by DAAS, 

which do not currently exist or require modifications, and support for the ILCS 

program. Once a map has been developed and fielded it is available for use by all 

our customers at no charge. The ILCS program is funded by each country 
Enclosure 2, ADC 1265

Page 14

involved through formal agreements (cases) established by the State Department 

with the countries involved, which in-turn establishes an annual reimbursable limit. 

The following are provided as major services:

C2.3.1.1. Provide Customer Service Support (24X7X365/366) from two 

geographically separate operating locations to assist DAAS customers around the 

world. This support will include front-line phone support and system monitoring 

support.

C2.3.1.2. Reduction of customer workload by automation of manual 

processes.

C2.3.1.3. Operation of a DoD eBusiness Gateway (eBUS).

C2.3.1.4. Development and implementation of new ASC X12 and XML 

variable-length translation maps. (Custom – one time). 

C2.3.1.5 Facilitation of network and data interoperability in support of 

the DoD Component and participating Agency logistics systems.

C2.3.1.6. Operation of a Foreign Military Sales (FMS) Logistics 

Gateway. (Custom – Reimbursable).

C2.3.1.7. Improved logistics data accuracy based on application of the 

DoD Component’s/participating Agency’s business rules.

C2.3.1.8. Sharing of logistics data and web accessible applications.

C2.3.1.9. Reporting on LRT.

C2.3.1.10. Support of DoD Component/participating Agency 

contingency operations.

C2.3.1.11. Consultation on logistics functional problems.

C2.3.1.12. Software engineering and technical consultation.

C2.3.1.13. ILCS support, including provision of aid in the following 

areas (Appendix 2: ILCS):

C2.3.1.13.1. FMS services. (Custom – Reimbursable).

C2.3.1.13.2. Customer Service support. (Custom –

Reimbursable).

C2.3.1.13.3. eBusiness services. (Custom – one time).

C2.3.2. The value-added benefits in using DAAS systems to receive and 

transmit logistics transactions are:
Enclosure 2, ADC 1265

Page 15

C2.3.2.1. Send and receive to/from one destination connection 

(DAAS/ILCS) versus many.

C2.3.2.2. Elimination of data sorting.

C2.3.2.3. Elimination of maintenance of distribution lists and telecommunications customer profiles.

C2.3.2.4. Maintenance of a single support and agreement interface.

C2.3.2.5. Elimination of requirements for multiple telecommunications 

protocols, data formats, and a unique supporting infrastructure.

C2.3.2.6. Provision of a single entry point into the following 

telecommunications interoperability networks:

C2.3.2.6.1. Defense Integrated System Network (DISN) NonClassified Internet Protocol Routing Network (NIPRNET).

C2.3.2.6.2. Defense Message System (DMS) via the Automated 

Message Handling System (AMHS), which is now integrated within the DGATE 

architecture and is no longer a separate process. Note: The Defense Message 

Dissemination System (DMDS) has been replaced by the AMHS.

C2.3.2.6.3. Commercial, private sector VANs.

C2.3.3. The value-added benefits for DoD Components/Participating 

Agencies, in using DAAS systems to validate, edit, route, and deliver logistics 

transactions, are:

C2.3.3.1. Performance of DoD Component-unique validations by:

C2.3.3.1.1. National Stock Number (NSN),

C2.3.3.1.2. DoD Activity Address Code (DoDAAC)/Stock Record 

Account Number/Unit Identification Code (UIC),

C2.3.3.1.3. Funds Code, and 

C2.3.3.1.4. Government Furnished Materiel (GFM) code.

C2.3.3.2. Access to item identification conversion processes:

C2.3.3.2.1. National Geospatial – Intelligence Agency (NGA) map 

number to/from NSN and

C2.3.3.2.2. Distribution Standard System (DSS) Routing Identifier 

Code (RIC) conversion process.
Enclosure 2, ADC 1265

Page 16

C2.3.4. Transaction interception and diversion services by/due to:

C2.3.4.1. DoD directed or DoD Component/Participating Agency 

request, 

C2.3.4.2. natural disaster or other contingency situations and 

C2.3.4.3. special operations or emergency deployment activities.

C2.3.5. Transaction archiving, tracking, retrieval, and resubmission/ 

retransmission services:

C2.3.5.1. Use of DLSS legacy format transactions, eB transaction 

sets, messages, or files.

C2.3.5.2. Transaction archiving, indefinite retention3, and retrieval.

C2.3.5.3. Transaction retrieval, re-addressing, and resubmission.

C2.3.6. eB Transaction Processing:

C2.3.6.1. eB transaction translation/conversion services:

C2.3.6.1.1. DLSS legacy 80 record position format to DLMS.

C2.3.6.1.2. DLMS to DLSS legacy 80 record position MILS egacy 

format.

C2.3.6.1.3. UDF to DLSS legacy 80 record position MILS 

format/DLMS/XML.

C2.3.6.1.4. DLSS legacy 80 record position MILS format 

/DLMS/XML to UDF.

C2.3.6.1.5. XML to DLSS legacy 80 record position MILS 

format/DLMS/UDF.

C2.3.6.1.6. DLSS legacy 80 record position MILS format 

/DLMS/UDF to XML.

C2.3.6.1.7. XML to XML.

C2.3.6.1.8. Intermediate Document (IDOC) to DLMS/XML.

C2.3.6.1.9. DLMS/XML to IDOC.

 3 Refer to ADC 1151. 
Enclosure 2, ADC 1265

Page 17

C2.3.6.2. VAN mail-boxing services for eB partners/transactions.

C2.3.7. DAAS, as the DoD Central Service Point (CSP) for DLM 4000.25, 

Volume 6: DoD Logistics Systems Interoperability Support Services:

C2.3.7.1. Receives the DoD Component/Participating Agency DoDAAD 

changes, performs file maintenance, and distributes updated data (push/pull) from 

a single location.

C2.3.7.2. Carries-out system queries and downloads.

C2.3.7.3. Serves as the DLA DoDAAD Service Point (SP).

C2.3.8. DAAS, as DoD custodian for DLM 4000.25, Volume 6: DoD Logistics 

Systems Interoperability Support Services:

C2.3.8.1. Receives Military Assistance Program Address Directory 

(MAPAD) changes from FMS and the DoD Component representatives.

C2.3.8.2. Performs file maintenance and distributes updated data 

(push/pull) from a single location.

C2.3.8.3. Performs system queries and downloads.

C2.3.9. DAAS, as the custodian for MILSTRIP Routing Identifier and 

Distribution Codes:

C2.3.9.1. Receives the DoD Component and Participating Agency RIC 

and distribution code changes.

C2.3.9.2. Performs file maintenance and distributes updated data 

(push/pull) from a single location.

C2.3.9.3. Performs system queries and downloads.

C2.3.9.4. Serves as the DLA RIC Service Point (SP).

C2.3.10. DAAS, as custodian of Military Standard Billing System 

(MILSBILLS) fund codes:

C2.3.10.1. Receives the DoD Component fund code changes.

C2.3.10.2. Performs file maintenance/daily issue from a single location.

C2.3.10.3. Performs system queries and downloads.

C2.3.10.4. Sends changes to the DoD Component activities.

C2.3.11. MILSBILLS Interfund Billing Process responsibilities:
Enclosure 2, ADC 1265

Page 18

C2.3.11.1. Confirms extended dollar worth, batch integrity, and buyer 

DoDAAC.

C2.3.11.2. Routes from seller to buyer.

C2.3.11.3. Archives4 and maintains official repository for Interfund 

Bills. Interfund bills are retained in a readily accessible format for:

C2.3.11.3.1. One year for DoD Interfund bills.

C2.3.11.3.2. Two year for FMS bills.

C2.3.11.3.3. The preceding procedures will be followed in 

accordance with DoDI 5015.02, DoD Records Management Program. 

C2.3.11.4. Query, recovery and retransmission of bills.

C2.3.12. Materiel Obligation Validation (MOV) Process:

C2.3.12.1. Confirms batch integrity and DoDAAC.

C2.3.12.2. Archives and maintains official repository.

C2.3.12.3. Relays responses to inventory control points (ICPs) when 

requested.

C2.3.12.4. Query, recovery, and retransmission of MOV batches.

C2.3.13. DAAS web services:

C2.3.13.1. Receives/processes applications for system access.

C2.3.13.2. Allows interrogation of DAAS repository.

C2.3.13.3. Links to DoD repository for interrogation.

C2.3.13.4. DLMS requisitioning.

C2.3.13.5. Data file and software product downloads.

C2.3.13.6. Logistics information reporting.

C2.3.14. LMARS reports: Standard LRT.

C2.3.15. Data information distribution services/interfaces:

 4 Refer to ADC 1151. 
Enclosure 2, ADC 1265

Page 19

C2.3.15.1. Communications addressing information.

C2.3.15.2. Enterprise Business System (EBS) front-end interface.

C2.3.15.3. Standard Point Location Code (SPLC).

C2.3.15.4. DSS and Military Surface Deployment and Distribution 

Command (SDDC).

C2.3.15.5. Cargo Routing Information File (CRIF).

C2.3.15.6. DSS and Naval Supply Systems Command Fleet 

Logistics Centers.

C2.3.15.7. Automated Manifest System (AMS).

C2.3.15.8. Cargo Movement Operations System (CMOS).

C2.3.15.9. DLA Logistics Information Service (J6B) catalog updates.

C2.3.15.10. Defense Transportation Coordination Initiative (DTCI) 

cargo booking system data.

C2.3.16. Transaction Images created and delivered for:

C2.3.16.1. DLA.

C2.3.16.2. United States Coast Guard (USCG).

C2.3.16.3. United States Marine Corps (USMC).

C2.3.16.4. United States Navy (USN).

C2.3.16.5. United States Air Force (USAF) (TRACKER), Abbreviated 

Transportation Accounting Code (ATAC)-AF, Lean Logistics, and others.

C2.3.16.6. United States Army Logistics Information Warehouse (LIW).

C2.3.16.7. Federal Agencies.

C2.3.16.8. Defense Finance and Accounting Service (DFAS).

C2.3.16.9. Integrated Data Environment (IDE)/Global Transportation 

Network (GTN) Convergence (IGC).

C2.3.16.10. FMS (Foreign Liaison Offices (FLOs) / freight forwarders).

C2.3.16.11. Other DoD activities, as requested.
Enclosure 2, ADC 1265

Page 20

C2.3.17. Repository/Data Warehouse Interrogations available by:

C2.3.17.1. DoDAAC.

C2.3.17.2. RIC.

C2.3.17.3. Military Assistance Program Address Code (MAPAC).

C2.3.17.4. National Item Identification Number (NIIN).

C2.3.17.5. Communications Routing Indicator (CommRI).

C2.3.17.6. Plain Language Address Directory (PLAD).

C2.3.17.7. ZIP Code.

C2.3.17.8. Logistics On-line Tracking System (LOTS).

C2.3.17.9. LMARS.

C2.3.17.10. MILSBILLS.

C2.3.17.11. MOV.

C2.3.17.12. LDG.
Enclosure 2, ADC 1265

Page 21

C3. CHAPTER 3

CUSTOMER PROCEDURES

C3.1. GENERAL. The Defense Automatic Addressing System (DAAS)

processes are designed to effectively use the telecommunications services 

provided by the Defense Integrated System Network, (DISN) Defense Message 

System (DMS) and Commercial Value Added Networks (VANs). The Defense 

Data Network (DDN) format outlines the required file formatting to be used by 

DAAS customers when preparing transaction files for delivery to the DAAS. The 

systems use these services to receive and transmit logistics traffic, and to provide 

a variety of logistics-related services to its worldwide customer base. DAAS 

systems are designed to facilitate the integration of logistics and 

telecommunications processes thus providing a single interface to both private and 

commercial telecommunications networks. DAAS processing is a near ‘real-time’ 

transaction oriented system with direct interfaces to a variety of 

telecommunications networks. They are designed to receive, validate, process, 

and forward all logistics transactions, provided they are computer-readable and 

authorized for transmission off-station by the customer. DAAS operates coprocessing facilities at two sites with fully redundant connectivity to the 

aforementioned telecommunications networks. Each site has the capability to 

handle the entire DAAS’ workload should a contingency situation occur.

C3.2. DAAS COMPLIANCE. The Department of Defense (DoD) 

Component/Participating Agency that has the capability to transmit computerreadable logistics transactions, via the above-mentioned tele-communications 

networks, will use the procedures prescribed herein. Any eligible activity not now 

participating in the DAAS is requested to do so by contacting the appropriate 

DAAS focal point (See section C1.8) for initial guidance and determination of its 

designated primary DAAS support site.

C3.3. MESSAGE PREPARATION AND TRANSMISSION

C3.3.1. Preparation. Customer logistics transactions in (legacy 80 record 

position transaction formats), Defense Logistics Management Standards (DLMS) 

Accredited Standards Committee (ASCX12 / eXtensible Markup Language (XML)), 

or User Defined File (UDF) formats will be assembled into messages/ files suitable 

for electronic transmission, in accordance with the appropriate established 

telecommunications procedures. Also, the computer-readable logistics 

transactions or service-type narrative messages will be sent to the DAAS for 

recovery, retransmission, or tracer actions. Messages of this type should be 

prepared as prescribed in the appropriate communication procedures. Customers 

should only send ‘unclassified’ messages/data files to the DAAS for processing. 

Classified message/data files must be sent directly to the intended recipient via 

secure Secret Internet Protocol Router Network (SIPRNET) connections. DAAS
Enclosure 2, ADC 1265

Page 22

and its customers assemble various type transactions into appropriate message 

formats for electronic transmission. The messages are addressed to the 

DAASDLA Transaction Services facility designated to serve the customer, without 

regard to the individual addresses contained in the transactions within the 

message text.

Table C3.T1. Authorized Transaction Formats

FORMAT RULE

Joint Army/Navy Procedures 

(JANAP) Data formatted as data 

pattern

Narrative JANAP 128 messages

DAAS Defense Data Network (DDN) Data formatted in the DAAS DDN 

Format

DDN Segment Header Data formatted in the DAAS DDN 

format without the file header

eBusiness Data formatted in the DLSS, DLMS 

ASC X12, XML, or UDF formats

C3.3.2. Transmission. The DAAS receives and sends computer-readable 

logistics transactions via multiple networks and connection methodologies. Unless 

specifically authorized, all exchanges of logistics transactions and related reports 

will be in machine-readable format and forwarded via the DAAS using electronic 

means. The DISN/Secure File Transfer Protocol (SFTP)/IBM MQ provide long 

haul and area data communications and interconnectivity for DoD systems. Small 

volume customers can also connect to the DAAS using standard email and World 

Wide Web (WWW) (Internet) capabilities. Specific file naming conventions have 

been developed to ensure data integrity and to provide a method for identifying, 

tracking, and accounting for all transferred files and data. Customers are 

unencumbered from any transaction batching requirements, since different types 

of transactions destined for various activities can be combined into one message 

and transmitted to the DAAS. Upon receipt, the DAAS examines each transaction 

independently, determines its supply address, and prepares it for transmission to 

the appropriate destination in a timely or ‘near real-time’ mode.

C3.4. REJECTS

C3.4.1. Messages. The DAAS does a duplicate message check on all 

message headers received. On the first receipt of a message, specific header 

information, consisting of the Originating Station Routing Indicator (OSRI), Station 

Serial Number (SSN), and File Time (FT) are written to a header file. When a later 

message is received, a test for validation of the Originating Station Routing 

Indicator (OSRI), Station Serial Number (SSN), and File Time (FT) is made 
Enclosure 2, ADC 1265

Page 23

against the header file. If all three test responses come back as a ‘match’, the 

DAAS deletes the later message and generates a service message to the 

originating station. The duplicate service message states that the cited message 

has been deleted as a ‘duplicate’ and that the originating station should resubmit a 

new message with a new SSN if, in fact, the message is not an actual duplicate.

Sample of a DAAS duplicate service message:

RCTUZYVW RUQAZZA9100 0051500 MTMS-UUUU--RUAAAAA

ZNR UUUUU

BT

UNCLAS SVC 9100

MSG RUAAAAA9001 0051300 RECD AT 0051303 AND 0051310

THE LATTER MESSAGE HAS BEEN DELETED AS A DUPLICATE

PLEASE RESEND WITH A NEW SSN IF NOT AN ACTUAL DUPE

BT

RCTUZYVW RUQAZZA9100 0051500 0009-UUUU--NNNN

Files are validated for naming convention, size, and message formats. Messages 

are validated by message type and transport protocol. If necessary, the DAAS 

sends a service message to the originating station advising of any actions taken.

C3.4.2. Transactions. The DAAS input transaction processing requires that 

only certain data fields be interrogated, edited, or verified as valid for acceptance, 

in accordance with specific business rules provided by the DoD Components/ 

Participating Agencies or the DLMS. DAAS also examines certain input 

transaction data elements to find the addressee and to ensure the Routing 

Identifier Code (RIC) of the activity to receive response transactions is valid. 

Invalid data will cause the DAAS to reject transactions to the originator, 

accompanied with a narrative description giving the reason for rejection. 

Transactions will be returned to the originator for a variety of reasons and only 

rejected transactions should be processed and resent by the originator. Returned 

transactions and related narratives or codes are based upon the first discrepancy 

detected in processing, and other errors may exist in the same transactions that 

the DAAS narrative may not reference.

C3.5. ARCHIVING. An archive of all transactions processed by the DAAS system 

is kept on Storage Area Network (SAN) or disk storage devices for rapid access 

purposes, In Accordance With DoD Instruction 5015.02. After 90 days the 

history files are transferred to long term storage. These history files give the 

source data to Logistics Information Data Services (LIDS) for creating its monthly, 

quarterly, and semiannual reports; and to Logistics Online Tracking System 

(LOTS) and Logistics Data Gateway (LDG) for parsing transactions into their 

online database repositories. These are automated processes, but accessing the 

archived and parsed transactions for reporting, resubmission, and retransmission 
Enclosure 2, ADC 1265

Page 24

purposes by internal and external users is an interactive process that allows for 

locally developed processes and system utilities to be called for execution. 

Tracking of a requisition’s life cycle is available through the Web Visual Logistics 

Information Processing System (WebVLIPS).

C3.6. MESSAGE RETRIEVAL AND RESUBMISSION REQUESTS. Messages 

sent to the DAAS are sometimes received in a garbled or incomplete condition. 

The DAAS does not edit the total content of transactions being processed, but it 

does check the data elements required for deciding the correct addressee, as well 

as the data elements that indicate the DoD Component/ Participating Agency. 

Garbled or incomplete conditions on data elements that are not subject to editing 

are processed undetected by the DAAS. DAAS will retransmit or resubmit 

designated messages when requested by the customer. Requests must comply 

with established communications procedures to specify the message number and 

date/time field. Requests must identify the error(s) in the transmission.

C3.7. MESSAGE TRACER ACTION REQUESTS. Customers desiring an audit or 

trace of named messages should send an e-mail message citing the specific 

action being requested to the DAAS Customer Service Support Desk at 

daascustomersupport@dla.mil.

Requests will contain message header data of the customer output message for 

the transaction(s) in question; the specific document number(s) will also be cited. 

DAAS will do an input/output history trace and give the customer the DAAS output 

message(s) that contained the transactions being traced. The customer will so 

state in the service message if they want DAAS to verify the time of receipt of the 

DAAS output message by the destination activity. If not, DAAS will furnish the 

customer the DAAS output message data.

C3.8. POINTS OF CONTACT. DAAS may be contacted requesting assistance 

with particular areas at the POCs in Table C3.T2 below.

Table C3.T2. Points Of Contact

ORGANIZATION TELEPHONE FAX E-MAIL

General Customer 

Service Support Desk

(614) 692-6672 Option 2,

DSN: (312) 850-6672 

Option 2

(937) 656-3800,

DSN 986-3800 daascustomersupport@dla.mil

Logistics Support

(614) 692-6672 Option 2,

DSN: (312) 850-6672 

Option 2

(937) 656-3800,

DSN 986-3800 daascustomersupport@dla.mil
Enclosure 2, ADC 1265

Page 25

Table C3.T2. Points Of Contact

ORGANIZATION TELEPHONE FAX E-MAIL

Electronic Commerce 

(EC)/EDI 

Customer Service 

Support Desk

(614) 692-6672 Option 2,

DSN: (312) 850-6672 

Option 2

(937) 656-3800,

DSN 986-3800 daascustomersupport@dla.mil

Main Office (937) 343-8636

DSN (937) 392-8636

(937) 656-3900,

DSN 986-3900
Enclosure 2, ADC 1265

Page 26

C4. CHAPTER 4

Defense Automatic Addressing System (DAAS) 

PROCESSING

C4.1. GENERAL

The DAAS provides all the Department of Defense (DoD)

Components/Participating Agencies a single entry point into the DoD Logistics 

Supply System. This eliminates the need to maintain multiple communication 

protocol rules and records and the unique supporting infrastructure necessary to 

send and receive information to/from multiple trading partners. All logistics 

transactions can be sent to DAAS without regard to data content or ultimate 

destination of the information. Use of the DAAS infrastructure, also, eliminates 

any need for the customer to sort transactions by type or destination. DAAS 

maintains the necessary trading partner profiles to ensure data is delivered on 

time, in the correct format, and to the correct destination. An archive of all 

messages and transactions processed by DAAS infrastructure is kept on storage 

media for later user access. All output transactions are permanently archived for 

historical, retransmission, audit, and reporting purposes in accordance with DoD 

Instruction 5015.02. The DAAS can process all computer-readable logistics 

transactions with the exception of certain logistics transactions containing narrative 

exception/supplemental data. Input and output to/from the DAAS is done by 

receiving/sending formatted messages through a variety of communications 

gateways and networks. The DAAS uses the following indicators to process 

logistics transactions:

C4.1.1. Source of Supply (SoS). As recorded by the Integrated Materiel 

Manager (IMM), Air Force, Army, and Navy/Marine Corps for each National Item 

Identification Number (NIIN). Includes special Naval code.

C4.1.2. Department of Defense Activity Addressing Code (DoDAAC).

C4.1.3. Routing Identifier Code (RIC).

C4.1.4. Military Standard Requisitioning and Issue Procedures (MILSTRIP)

Distribution Code.

C4.1.5. Military Standard Billing System (MILSBILLS) Fund Code.

C4.1.6. Military Assistance Program Address Code (MAPAC).

C4.1.7. Project Code.
Enclosure 2, ADC 1265

Page 27

C4.2. MESSAGE PROCESSING

The DAAS message handling processes go through a number of steps which may 

include the following:

C4.2.1. Receipt. The DAAS receives Defense Logistics Standard System

(DLSS) legacy 80 record position transactions in the Military Standard (MILS)

record format, DLMS-based message data in either the Accredited Standards 

Committee (ASC) X12, eXtensible Markup Language (XML), or User Defined File 

(UDF) formats through various communication networks. Additionally, a message 

traffic ‘pass-through’ service is provided for those customers who have no direct 

data exchange communications link(s) with each other. A single input message 

normally has transactions that could be output in several output messages 

generated by the DAAS sub-systems. Multiple input messages from various 

customers may contain transactions that are combined into a single DAAS output 

message.

C4.2.2. Review. DAAS maintains 90 days of message header information in 

replicated tables for the purposes of performing a DUPLICATE MESSAGE check. 

The tables are queried by DAAS’ servers during the message receive process. 

Algorithms are used to determine which, if any, messages should be rejected due 

to a record of previous receipt. A communications service message will then be 

sent to the originating activity saying that the message was deleted and requesting 

that it be reviewed for determination as a possible duplication. If it is found to 

actually not be a duplicate, the transaction(s) need to be resent in a new message.

C4.2.3. Intercept. The DoD Components/Participating Agencies are 

responsible for providing their DAAS’ focal points with Service specific transactionprocessing rules. These activities can also ask for mission critical emergency 

changes to respond to a new mission or a changing world situation. Most of these 

type requests cause transactions to be rerouted to/from a different location than 

the normal SoS or destination address. Some of the requests are for DAAS to 

intercept selected transactions and either redirect/terminate them, or hold them for 

further directions on dispensation. For example, if a hurricane is moving toward 

Hawaii, transactions destined for DoD activities/installations in the affected area

can be intercepted and held at DAAS until the storm has passed and then 

released in the same sequence in which they were received. DAAS allows the 

input of the transactions into an activity’s application system(s) to maintain the 

records as if no interruption had occurred. As the single point of entry into the 

DoD Logistics Supply System for our customers, DAAS can intercept any data, 

make changes to the data content, edit shipping instructions, and support all the 

DOD Component/Participating Agency contingencies under the following 

conditions or emergency situations:

C4.2.3.1. A DoD-directed or customer request.

C4.2.3.2. Natural disasters or other similar situations. 
Enclosure 2, ADC 1265

Page 28

C4.2.3.3. Support for special operations and emergency deployments.

C4.2.4. Broadcast. DAAS serves as a gateway for logistics information and 

as a repository for numerous types of logistics data. As such, it provides data 

distribution services to the DoD Components/Participating Agencies for use in their 

local processing systems. DAAS receives data at a unique routing address that 

can trigger distribution of the data to a predetermined set of recipients. DAAS 

maintains the information necessary to deliver the data to multiple destinations 

and is able to effect system changes within a short timeframe. The originating 

systems rarely have to make any program changes to support these new 

distribution requirements. Some examples of existing data distribution 

information/codes available for use, by the DoD Components/Participating 

Agencies, are:

C4.2.4.1. Communications addressing information.

C4.2.4.2. Standard Point Location Code (SPLC) data.

C4.2.4.3. Distribution Standard System (DSS) support.

C4.2.4.4. Military Surface Deployment and Distribution Command

(SDDC) support.

C4.2.4.5. Cargo Routing Information File (CRIF) data.

C4.2.4.6. Fleet Logistics Center (FLC) support.

C4.2.4.7. Automated Manifest System (AMS) support.

C4.2.4.8. Cargo Movement Operations System (CMOS) support.

C4.2.4.9. Federal Logistics Information Services (FLIS) Portfolio

catalog updates.

C4.2.5 Transmission. The DAAS is designed for transmission of computerreadable logistics messages using secure telecommunications circuits. Our NonSecure Internet Protocol (IP) Router Network (NIPRNet) connection to the 

Defense Information System Network (DISN) provides the capability of sending 

data, using various secure transmission protocols like Secure File Transfer 

Protocol (SFTP), via Transmission Control Procedure/ Internet Protocol (TCP/IP), 

web-based forms, or HTTPS. In addition, DAAS uses IBM MQ, a guaranteed 

delivery transport from an IBM MQ origin to an IBM MQ configured destination. 

This supports customer needs for guaranteed delivery, 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 MQ and Virtual Private Network (VPN) 

connections to transport information in the ASC X12 and XML formats. Specific 
Enclosure 2, ADC 1265

Page 29

file naming conventions are used to ensure data integrity and provide a method for 

identifying, tracking, and accounting for all files and data transferred. Standard 

secure internet protocol provide connectivity for small volume customers, legacy email is also used but not recommended due to the deprecated communication 

protocol used. Acceptable data formats are depicted in Chapter 3: Table C3.T1. 

“Authorized Transaction Formats.”

C4.3 MILS LEGACY TRANSACTION PROCESSING

C4.3.1. Editing. When the DOD Components/participating Agencies send 

DLSS legacy 80 record position MILS format transactions to DAAS they are 

edited, validated, routed, and delivered to the appropriate destination. Edits 

performed include:

C4.3.1.1. DoDAAC or MAPAC. Validation of the DoDAAC or MAPAC. 

This is the first major edit done by the DAAS and is vital to mailing, shipping, and 

billing functions.

C4.3.1.2. NSN or SoS. The national stock number (NSN) describes the 

item of supply and is associated with the managing inventory control point (ICP) or 

SoS. DAAS uses the SoS and associated management data as part of its on-line 

processing records and is the designated repository for the last known SoS. If the 

transaction’s SoS code is incompatible with the NSN’s SoS code in the repository, 

the DAAS may change the SoS code in the transaction, sending it to the correct 

SoS, while sending the supply status information to the submitter in notification of 

the redirection.

C4.3.1.3. Fund Code. Fund codes are edited to ensure MILSBILLS 

compatibility. If an invalid code is used, the DAAS may either change the code or 

reject the transaction, as required by the DoD Component/Participating Agency’s 

processing rules.

C4.3.1.4. Project Codes and Priority Codes. These codes are edited to 

ensure activities are not abusing code assignments and are authorized to use 

certain codes. If an invalid code is used, the DAAS may change the code or reject 

the transaction, as required by the DoD Component/Participating Agency’s 

processing rules.

C4.3.2. Rejections. Representative examples of business rules that would 

cause a transaction to reject are depicted below:

C4.3.2.1. MILSTRIP Transactions Designated for Local Procurement. 

The DAAS will reject transactions to be routed by the IMM SoS record when that 

source is coded decentralized (D9_ or XDG). This procedure is limited in 

application to Continental United States (CONUS) requisitions that do not contain 

Advice Code 2A. An AE9 transaction with Status Code CP is returned to the 

originator of the transaction.
Enclosure 2, ADC 1265

Page 30

C4.3.2.2. Invalid MILSTRAP Transactions. The DAAS will validate all 

MILSTRAP Special Program Requirement (SPR) transactions. Invalid 

transactions are returned to the originator(s) using the appropriate reject advice 

code in card column positions 79-80 as follows:

C4.3.2.2.1. Reject Advice Code AD, the NIIN cannot be identified.

C4.3.2.2.2. Reject Advice Code AX, the correct SoS is GSA.

C4.3.2.3. MILSBILLS Transactions. The DAAS will confirm or reject 

MILSBILLS transactions as prescribed in DLM 4000.25, DLMS, Volume 4.

C4.3.2.4. Other. The DAAS confirms certain elements of input 

transactions to find the addressee and to ensure the RIC of the activity(s) to 

receive response transaction(s) are valid. Invalid data causes the DAAS to reject 

and return transactions to the originator, with an included narrative description to 

indicate the reason for rejection. The rejected transactions must be corrected by 

the originator and retransmitted to the DAAS in a new message. Transactions will

be returned for the following reasons:

C4.3.2.4.1. Garbled transactions. Transaction fields are shifted or 

unreadable.

C4.3.2.4.2. Invalid Document Identifier Code (DIC). The DAAS 

cannot read/identify the transaction; the transaction is not to be transmitted 

electronically; or the transaction is not authorized for transmission to the DAAS.

C4.3.2.4.3. Invalid Service Code. The DAAS cannot identify the 

service code entered in the transaction.

C4.3.2.4.4. Invalid DoDAAC. The code is not in the master DoD 

Activity Address File (DoDAAF).

C4.3.2.4.5. Invalid NIIN. The NIIN has alphabetic characters or 

blanks.

C4.3.2.4.6. Invalid MAPAC. The code is not in the master Military 

Assistance Program Address File (MAPAF).

C4.3.3. Routing and Rerouting. The DAAS edits, validates, routes, and 

delivers transactions based on agreed to business rules that have been supplied 

to DAAS by the DoD Components/Participating Agencies:

C4.3.3.1. Accepted Transactions. All processed transactions are 

delivered to the appropriate destination in the proper format and protocol based 

upon the customers’ requirements. After processing, all transactions are collected 

by destination, based on applicable message precedence and transaction priority, 

and a new message is prepared and sent through the appropriate communications 
Enclosure 2, ADC 1265

Page 31

network to the activity destination address. The message precedence and content 

identifier code (CIC) are assigned in accordance with the appropriate correlation 

table. 

C4.3.3.2. Item SoS Record. If the originator of the transaction is other 

than a United States Army (USA), United States Navy (USN), or United States, Air 

Force (USAF) activity, routing is determined by examining the IMM column of the 

SoS record. If a USA, USN, or USAF activity originated the transaction, the entry 

in the SoS column of the DoD Component parent is used to determine the routing 

as follows:

C4.3.3.2.1. If the SoS in the DoD Component record is an activity 

of that Component and an active SoS, the transaction is sent to the SoS in the 

DoD Component record.

C4.3.3.2.2. If the SoS in the DoD Component record is an inactive 

source or an IMM source, the transaction is sent to the SoS in the IMM record. If 

the IMM record is blank, the transaction is sent to the SoS in the DoD Component 

record.

C4.3.3.2.3. If the SoS in the DoD Component record is an activity 

of another DoD Component, the transaction is sent to the other Component. If the 

other DoD Component record is blank, coded as inactive, or contains an IMM 

source, the transaction is sent to the IMM SoS. However, if the IMM record is 

blank, the transaction is sent to the originating DoD Component. 

C4.3.3.2.4. If the SoS field in the DoD Component record is blank, 

the transaction is routed to the SoS in the IMM record. If the IMM record is blank, 

the transaction is passed to the Routing Identifier’s ‘To’ entry in positions 4 - 6 of 

the transaction.

C4.3.3.3. Coding Inactive Items. As prescribed by the Defense Inactive 

Item Program, the DAAS decides during requisition processing if the DoD 

Components/Participating Agencies’ IMM record, used for routing, is coded 

inactive. The DAAS inserts an ‘I’ in the demand code field of the transaction, to 

advise the sender that it pertains to an inactive item of supply. This procedure is 

applied by the DAAS for those requisitions routed in accordance with item SoS 

records.

C4.3.3.4. National Geospatial - Intelligence Agency (NGA). Military 

Assistance Program (MAP) Number Conversions are performed in the following 

cases:

C4.3.3.4.1. MAP number to and from NSN.

C4.3.3.4.2. RIC conversion process for MAP requisitions.
Enclosure 2, ADC 1265

Page 32

C4.3.3.5. Transaction Rerouting. The DAAS may reroute transactions 

under the following conditions:

C4.3.3.5.1. Destination Changes. Transactions routed by the 

DAAS may be sent to a destination other than that designated by the originator. 

When this is done, the DAAS notifies the originator of the change.

C4.3.3.5.2. Status for Rerouted MILSTRIP Transactions. When 

the DAAS reroutes a MILSTRIP requisition, a passing order, or a referral order, 

the notice to the originator is a standard ‘AE9’ MILSTRIP transaction with Status 

Code BM in positions 65 - 66 and the changed RIC in positions 67 - 69. The 

originator is notified in each instance when the DAAS changes the destination of 

an excess report DICs FTC, FTE, or FTF transaction. This notice is a DIC FTQ 

transaction with Status Code TZ (destination change Federal Supply Class 

change) in positions 65 - 66, the DAAS RIC in positions 4 - 6 and the changed RIC 

in positions 67 - 69 of the transaction.

C4.3.3.5.3. Status for Rerouted MILSTRAP Transactions. When 

the DAAS reroutes a MILSTRAP Special Requirement Program (SPR) transaction, 

the notice is a standard DIC DZ9 MILSTRAP transaction with MILSTRIP Status 

Code BM in positions 79 - 80 and the RIC of the correct SoS in positions 67 - 69 of 

the transaction.

C4.3.4. Images: During processing, the DAAS makes images of selected 

transactions, sends them to activities who may be monitoring a project, or the 

transactions may become part of a DoD Component/Participating Agency logistics 

database. Image making has become a major workload for DAAS with millions of 

images being produced each month. Frequently, multiple images are made of the 

same transaction and sent to different databases. For example, an image of a 

shipment status transaction will be sent to the Asset Visibility (AV) system, the US 

Transportation Command’s (USTRANSCOM) Integrated Data Environment/Global 

Transportation Network Convergence (IGC) System, the USAF TRACKER 

System, or the US Army’s Logistics Information Warehouse (LIW) System.

C4.3.4.1. DAAS currently makes transaction images for the following 

organizations:

C4.3.4.1.1. Defense Finance and Accounting Service (DFAS).

C4.3.4.1.2. Defense Logistics Agency (DLA).

C4.3.4.1.3. Federal Civil Agencies.

C4.3.4.1.4. USTRANSCOM/GTN. 

C4.3.4.1.5. Other DoD.

C4.3.4.1.6. USA (LIW and others).
Enclosure 2, ADC 1265

Page 33

C4.3.4.1.7. USAF (TRACKER, Lean Logistics, and others).

C4.3.4.1.8. USCG.

C4.3.4.1.9. USMC. 

C4.3.4.1.10. USN.

C4.3.5. Determining Destination Addresses. Transactions processed by the 

DAAS are categorized as traffic to either be routed or passed as follows:

C4.3.5.1. Routed Traffic. This is defined as those transactions for 

which the DAAS rules and records are used to find the addressee, regardless of 

the destination cited by the transaction originator. The DAAS rules and profiles for 

routing transactions are specifically tailored for the DoD Components/Participating 

Agencies. For example, a designated transaction may be routed by one rule/ 

profile for the USA and by a different rule/record for the USN or USAF. In addition, 

the DoD Component/Participating Agency will specify if the DAAS rules/profiles 

are to apply to all or only some of its activities (e.g., the DAAS routes USN 

requisition transactions in accordance with the item SoS record for certain USN 

activities). The DAAS applies two basic techniques to route transactions: (1) the 

use of the DoD Component/Participating Agency special processing rules and (2) 

the item SoS records. The former is checked first and, if no processing rule 

applies, the transactions are routed based on the SoS record.

C4.3.5.2 Passed Traffic. This is defined as those transactions that are 

routinely forwarded to the addressee designated by the transaction originator. 

Passed traffic includes supply/shipment status, materiel release orders, 

redistribution orders, most inventory management transactions, and includes some 

requisitions and referral orders.

C4.3.6. Batching. Transactions for a given destination may be batched with 

a new message being assembled and formatted for transmission through the 

appropriate communications network to the destination activity. Normally, DLMS 

transactions are collected/assembled for up to ten minutes for supply priorities 1 -

8 or for other transactions specifically designated as priority, and for up to 1 hour 

for all other transactions. Transmission time intervals are tailored to meet the 

destination activity’s requirements. 

C4.4. X12 AND XML TRANSACTION TRANSLATION AND CONVERSION

C4.4.1. Translation. DAAS has a specifically tailored COTS software suite 

that provides data translation capabilities to and serves as a central transformation 

processor for all of the DoD. The capability includes conversion services for DLSS 

legacy 80 record position MILS format transactions to DLMS, DLMS to DLSS 

transactions, XML to XML, DLSS/DLMS/XML to UDF, and UDF to 

DLSS/DLMS/XML formats. This allows for implementation of the DLMS as the 

DoD legacy systems evolve along their own timelines into new and redesigned 
Enclosure 2, ADC 1265

Page 34

Enterprise Resource Planning (ERP)-based logistics systems. This capability has 

been implemented by the Services for many logistics processes within the DoD 

Components/Participating Agencies.

C4.4.2. eBUS Gateway. DAAS supports the latest eBusiness (eB) methods 

and protocols for the DoD Components/Participating Agencies to use in sending 

and receiving DLMS ASC X12 /XML transaction sets. The eB gateway provides 

an interoperable gateway for DoD components to exchange data supporting a 

variety of business areas including by not limited to procurement, transportation, 

financial, logistics, and contracting data. Using this component of the DAAS 

allows DoD activities to send and receive from a single DoD focal point. This 

reduces the overhead of eB trading partners by making it unnecessary for the 

DAAS partners to maintain addressing and profile information on the DLMS 

implementation conventions being used by all their individual trading partners. 

The DAAS can receive and transmit transactions by using the intra-DoD 

communications protocols/networks or by using commercial VANs. For 

contingency and growth purposes, there are two functional eB distribution 

gateways, one at each DAAS site. These eB hubs receive ASC X12, XML or UDF 

transaction sets from the DoD Components and private-sector vendors conducting 

business with the DoD community. DAAS provides connectivity/mailboxing/reporting services between DoD/Government procurement, financial, 

transportation, and contracting activities and their private sector trading partners.

C4.4.3. VAN Services. In addition to providing connectivity to numerous 

commercial VANs, DAAS own eB VAN provides VAN services for our customer 

base. The DAAS eB VAN provides a central eBusiness communications gateway 

for translation, conversion, connectivity, mail-boxing, and reporting services 

between the DoD Components/Participating Agencies and their private industry 

partners.

C4.4.4 DoD eBusiness GEX Consolidation. DoD made a decision in 2011 to 

transfer the GEX program management responsibility from the Business Transformation 

Agency (BTA) to DLA , and to begin consolidation of all GEX functionality at DAAS’ two 

eBusiness Gateways. As a result, the process of moving all current eBUS customer 

connections from the two existing DISA GEX gateways to DAAS has begun. Once 

complete, all DoD eBusiness customers/transactions will be routed through the two 

DAAS’ GEX gateways.

C4.4.5. Customer Profiles/Trading Partners. DAAS currently maintains two 

sets of trading partner profiles, one for MILS customers, and one for DLMS X12 

and XML eB customers, as follows:

C4.4.5.1. DoD Gateway (DGate). DAAS maintains a MILS customer 

profile for each DLSS legacy 80 record position format transaction customer. 

The customer profile has information about a customer’s communication routes 

and formatting requirements. Profiles are stored in the DAAS processing system 
Enclosure 2, ADC 1265

Page 35

and their upkeep is considered a part of file maintenance. Profile changes and 

additions are constantly taking place as existing customers’ environments change.

C4.4.5.2. DoD eB Gateway. Trading partner agreements and profiles 

for each DLMS eB customer identify communication routes and formatting 

requirements for DoD Components/Participating Activities, along with information 

on their associated commercial trading partners. The Trading partner agreements 

are stored in the eB processing system and their upkeep is considered a part of 

file maintenance. Trading partner changes and additions are constantly taking 

place as new trading partners are identified and existing customers’ environments 

change.

C4.4.5.3. Future Vision. Transaction volumes in both the MILS and the 

eBusiness areas are expected to continue to increase, in part due to the 

consolidation of all GEX EDI traffic at DAAS . Current modernization plans call for 

DAAS to move towards establishment of only one type of customer or trading 

partner profile, which will cover all customers/partners regardless of transaction 

format(s) or end-system configurations. Finally, the DAAS processing of DLSS 

transactions and the DMLS X12 and XML transactions will, also, be consolidated 

through a single gateway employing common transmission and security protocols. 
Enclosure 2, ADC 1265

Page 36

C5. CHAPTER 5

COMMUNICATIONS

C5.1. INTRODUCTION

C5.1.1. General. This chapter outlines the communications methods to be 

used between the Defense Automatic Addressing System (DAAS) and its 

customers/trading partners for the exchange and processing of (DLMS) Defense 

Logistics Management Standards transactions.

C5.1.2. Defense Integrated System Network. The Defense Integrated 

System Network (DISN) will be the primary communications path to convey DLMS 

transactions between the DAAS’ Global Exchange (GEX) eBusiness Gateways 

and their DLMS users. In some cases, DLMS participants are commercial entities 

or foreign governments that do not have access to the Defense Integrated System 

Network (DISN). In these cases, DAAS will be responsible for conveying the 

DLMS transactions to the appropriate distribution point that can link to the specific 

DLMS trading partners (such as via a commercial Value-Added Network [VAN]). 

The GEX eBusiness Gateways are nodes on the DISN as are most of our 

Department of Defense (DoD) trading partners.

C5.1.2. Purpose. Within the general DISN requirements for transmitting 

data, the DLMS has additional specific data transmission capabilities and 

requirements. This chapter identifies and defines these requirements and 

capabilities.

C5.2. ENVELOPING

C5.2.1. General Information

C5.2.1.1. Transaction Sets. Electronic Data Interchange (EDI) 

transaction sets are transmitted within other data structures that provide 

telecommunication (rather than functional) information. For instance, several 

transaction sets (an X12 transaction5 set begins with "ST" [transaction set header] 

and ends with "SE" [transaction set trailer] segments) can be grouped together 

within a transmission standard structure (called an envelope). The rules governing 

such multiple packaging are: (1) only transactions in the same Functional Group 

(FG) may be bundled together; (2) the group envelope within which they appear 

must begin with a "GS" (group start) segment and end with a "GE" (group end) 

segment; and (3) one or more like transaction set(s) will be contained within the 

GS and GE segments. 

 5 Accredited Standards Committee (ASC) X12
Enclosure 2, ADC 1265

Page 37

C5.2.1.2. Transaction Groups. One or more transaction groups fit into 

a higher-level enveloping structure required for each EDI transmission. This 

structure always begins with an "ISA" (interchange start) segment and ends with 

an "IEA" (interchange end) segment. Contained within the ISA and IEA will be one 

or more group control set(s).

C5.2.2. Description of Use

C5.2.2.1. The interchange header and trailer segments (ISA/IEA) 

constitute the interchange control structure, i.e., an interchange envelope. 

Interchange control segments perform the following functions:

C5.2.2.1.1. Define data element separators and data segment 

terminators.

C5.2.2.1.2. Provide control information.

C5.2.2.1.3. Identify sender and receiver.

C5.2.2.1.4. Allow for authorization and security information.

C5.2.2.1.5. Tables defining the X12 Control Structures and 

Segment/Element Separators are included as Appendix 6 of this manual.

C5.2.2.2. Interchange Control Structure. The interchange control 

structure includes neither the group control structures nor the transaction control 

structures. The X12 Standard defines the latter two structures as application 

control structures, and even their version and release may differ from those of the 

interchange envelope. An interchange envelope may encompass one or more 

FGs (GS/GE) which, in turn, may enclose one or more related transaction sets 

(ST/SE). The DLMS Supplements (DS) to the Federal Implementation 

Conventions (ICs) illustrate the relationships for these structures.

C5.2.2.3. Purpose of FGs. Since the only purpose of the GS/GE FGs is 

to serve as an additional control envelope surrounding like transaction sets (within 

the ISA/IEA structure), DAAS considers their usage to be as interchange control 

segments. The DAAS does accept multiple transaction types if they are within the 

same FGs.

C5.2.2.4. Transaction Interchanges. The generic term “trading partner” 

has extensive use throughout the EDI community. It refers to each member of a 

sender/receiver pair in an interchange. In contrast to the arrangement between 

some commercial or industrial trading partners, the interchange of DLMS 

transactions employs the capabilities of a central communications hub which is a 

combination of the Defense Automatic Addressing System (DAAS) and the DoD 

Global Exchange (GEX) eBusiness Gateway. These systems perform several 

value-added functions before forwarding DLMS transactions to their ultimate 

receiver. Thus, DLMS interchanges occurring between DoD Components or 
Enclosure 2, ADC 1265

Page 38

between Components and commercial entities should always interface through 

this central hub. For clarity within this interchange control process, DAAS 

distinguishes between intermediate communication between site and central 

facility and the exchange of EDI transactions between end-to-end entities. DAAS 

characterizes the intermediate interchange between the DAAS/GEX hub and any 

DoD Component or commercial entity as occurring between communications 

partners. The term, trading partners in the interchange control process is defined 

as the end-to-end communicants in an interchange.

C5.2.2.5. Envelope Control Segments. Envelope control segments 

have few options and are identical for every EDI interchange between the same 

trading partners, except for minor tailoring. The tailoring involves the code values 

selected for the GS01 and GS08 elements. GS01 classifies the particular 

transaction set(s) within a FG and GS08 identifies their Accredited Standards 

Committee (ASC) X12 version and release (and the Implementation Convention 

([IC]) version itself). NOTE: The version and release identified in the ISA12 data 

element pertains to the control envelope and not to the transactions.

C5.2.3. Data Element, Data Segment (File), and Sub-Element Separation

C5.2.3.1. Data Element Separator

C5.2.3.1.1. Purpose. In Accredited Standards Committee ASC 

X12 documentation, the data element separator is typically displayed as an 

asterisk (*). The data element separator employed within the interchange 

envelope assigns the value for the entire interchange. The first occurrence of the 

data element separator is at the fourth byte of the interchange control header. The 

value appearing there prescribes the data element separator through the next 

interchange trailer.

C5.2.3.1.2. Rules. Any character can serve as a data element 

separator as long as: (1) it is disjointed (i.e. not used in any other instance) from 

every other data element within an interchange; and (2) it does not conflict with 

telecommunications protocols necessary for the transmission of the interchange. 

The American Standard Code for Information Interchange (ASCII) hexadecimal 

character 1D value recommended by ASC X12 will apply for use in the 

interchange of DLMS transactions.

C5.2.3.2. Data Segment Terminator

C5.2.3.2.1. Purpose. The interchange control header establishes 

the value to be used for segment termination within an interchange. ASC X12 

documentation represents this graphically by a new line. The first instance of 

segment termination immediately follows the ISA16 segment, where the data 

value occurring there sets the value for the interchange.

C5.2.3.2.2. Terminator Value. The segment terminator value must 

be disjointed from all other data values within an interchange and must not conflict 
Enclosure 2, ADC 1265

Page 39

with transmission protocols. ASC X12 recommends using the ASCII hexadecimal 

character “1C” (file separator) for the segment terminator character. To comply 

with this requirement, DLMS users will set the pertinent parameter in their 

translation software. In DLMS EDI documentation, the segment terminator is 

typically displayed as a tilde (~).

C5.2.3.3. Sub-Element Separator

C5.2.3.3.1. Purpose. Sub-element separators differ from other 

separators. The ISA segment provides a discrete element (ISA16) for defining the 

sub-element separator data value used to separate component data elements 

within a composite data structure. This value must be different from the data 

element separator and the segment terminator.

C5.2.3.3.2. Rules. The requirements for any separator value are 

(1) disjointedness and (2) lack of conflict with other protocols. DLMS users will set 

the applicable translation software parameter to employ the recommendation of 

ASC X12 for sub-element separation by using the ASCII hexadecimal character 

“1F” (unit separator). In DLMS EDI documentation, the back slash ( \ ) is typically 

used to graphically represent the sub-element separator.

C5.3. ARCHIVING AND SEMANTIC ERROR RECOVERY

C5.3.1. Archiving. EDI transactions will be retained on-line at DAAS for a 

period of 30 calendar days after receipt in accordance with DoDI) 5015.02 and 

can be accessed by the DAAS’ EDI Customer Service Support personnel. To 

obtain assistance, via e-mail, click on the following e-mail address: EDI@DLA.mil.

Due to the fact that some EDI transactions are considered to be legal documents, 

all such transactions are archived by DAAS’ GEX eBusiness Gateway and are 

retained in accordance with DoDI 5015.02. After successful processing, EDI 

transactions are, also, moved to the DAAS Logistics On-Line Tracking System 

(LOTS) archives. The DAAS central communications facility provides significant 

archiving and error recovery services for DLMS trading partners. To assist with 

historical research in legal issues or for error correction, DAAS maintains crossreferences between each customer’s original inbound transmissions and their 

subsequent (different) outbound transmissions, which are forwarded to a receiving 

trading partner. Without these services, each end of the communication link would 

have to provide for extended data storage and recovery procedures.

C5.3.2. Transaction (Semantic) Errors

C5.3.2.1. Purpose. Semantic errors involve EDI transaction data that 

have been correctly formatted, but whose meaning cannot be correctly interpreted 

by the receiving application/process. It is not possible to detect semantic type 

errors during either transmission or translation. As a result, detection of erroneous 

data occurring within a transaction is the responsibility of the receiving partner. 

Semantic errors must be determined either within the receiving application 
Enclosure 2, ADC 1265

Page 40

processes or by some error detection software whose editing rules are based on 

the receiving application. The DAAS’s GEX eBusiness Gateway will perform

certain levels of semantic/syntax error detection for DLMS transactions based on 

DoD standard rules in support of central communications facility users.

C5.3.2.2. Error Detection. If semantic errors are detected after 

transmission and translation, their correction normally falls outside the domain of 

either the translation or the transmission processes. Semantic errors can be 

corrected either within the originating application process, by error correction 

software whose editing rules are based on the originating application process, by 

error correction software whose editing rules are based on the originating 

application, or by default values agreed upon by both originator and receiver. At 

the request of central communications facility users, DAAS can perform various 

levels of semantic error correction based on computer processable editing rules.

C5.3.2.3. Administering Corrections. For the originating application 

process to administer correction measures, the application must be aware of the 

error’s existence and location. An error advice transaction must be generated by 

the receiving trading partner or by some error detection software outside the 

originating process. The DS to 824 Federal IC-Reject Advice, may be used to 

report transaction semantic errors.

C5.4. TRANSACTION ACKNOWLEDGEMENT / ENVELOPE ERROR 

REPORTING

C5.4.1. General Information

C5.4.1.1. Failure Levels. In addition to semantic errors, EDI formats 

are subject to failure at three levels: (1) transmission, (2) EDI control envelope, 

and/or (3) EDI transaction syntax. When successful processing is not possible 

due to problems within one of these levels, error recovery may be performed by 

the central communications facility.

C5.4.1.2. Transmission Integrity. For incoming traffic at DAAS, 

successful receipt of an electronic message means that the arriving transmission 

is the same as that which was sent. Thus, if transmission integrity is lacking, 

communication protocols will consider retransmission to have been 

unsuccessfully received at DAAS. Also, receipt of any transmission whose EDI 

control envelope has been corrupted will prompt the GEX eBusiness Gateway to 

return an appropriately coded acknowledgement to the sender. If the envelope is 

incorrect or lacking, the gateway will treat the faulty transmission as never having 

been received.

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 
Enclosure 2, ADC 1265

Page 41

acknowledgment transaction. (See C5.4.2 regarding the 997 Federal IC, 

Functional Acknowledgment (DLMS Appendix 1)). Transactions containing syntax 

errors are neither forwarded to the receiving trading partner nor retained at DAAS. 

They are "refused for delivery" until corrected. The GEX eBusiness Gateway does 

not utilize the 997 with the “Accepted with Error” code.

C5.4.1.4. Error Advice. The original sending trading partner will accept 

and respond to the error advice transaction (e.g., 997 IC), by correcting the error, 

and retransmitting the transaction.

C5.4.1.5. Trading Partner Transaction. For transmissions between 

DAAS and the destination trading partner, the roles for error recovery are 

reversed. Transmission acknowledgement, EDI control envelope error detection, 

and EDI syntax checking are all performed within the receiver's communications 

and EDI translation facilities; the GEX eBusiness Gateway responds only to 

communications protocol IC 997 advice messages.

C5.4.2. Federal Implementation Convention 997, Functional 

Acknowledgment

C5.4.2.1. Negative Functional Acknowledgment. Between DLMS 

communication partners, only a negative functional acknowledgement will be 

employed. The 997 IC will be transmitted for any interchange whose contents 

cannot be handled unambiguously by properly functioning EDI translation 

software. Note that "functional acknowledgement" might be a slight misnomer; the 

997 IC merely verifies (or challenges) the syntactical correctness of (ability to 

translate) transaction-level data within a FG. For DLMS interchanges, a 997 IC 

defining translation problems is exchanged not between trading partners, but

between communications hubs/partners (i.e., between the GEX eBusiness 

Gateway and either of the trading partners). Positive functional 

acknowledgements can be sent when requested.

C5.4.2.2. Outbound Syntax Errors. Outbound transaction sets that 

contain EDI syntax errors will cause an error condition at the receiving EDI 

gateway/translator (typically at DAAS). The receiving EDI translator will report the 

error back to the sender via an 997 IC. For inbound interchanges, errors in syntax 

discovered by the receiver during translation will result in the generation of a 997 

IC defining the syntactical discrepancies and the interchange will be returned to 

the sending EDI gateway/translator (typically DAAS) for correction and 

retransmission.

C5.4.2.3. Compliance with DLMS Supplements. The receiving 

translator (or application software if the translators do not detect the error) will

reject a transaction whenever segment(s) or data element(s) identified as either 

mandatory or required by the DS are not present. 

C5.5. ADDITIONAL COMMUNICATION ISSUES
Enclosure 2, ADC 1265

Page 42

C5.5.1. Control Numbers. ASC X12 standards provide for syntax control on 

three levels: (1) interchange, (2) group, and (3) transaction. Within each level, 

use of an identical control number exhibits a positive match between the header 

segment and its corresponding trailer (e.g., ISA/IEA, GS/GE, and ST/SE). The 

DLMS conventions specify assignment of these control numbers at each level as 

described in the following paragraphs.

C5.5.1.1. ISA/IEA Interchange Control Numbers (ISA13/IEA02)

C5.5.1.1.1. Assignment. The nine-digit interchange control 

number is assigned by the originator's translation software starting with 

000000001. This control number is incremented by one for each subsequent 

interchange. When the number in the sequence advances to 999999999, the next 

interchange envelope will restart the series at 000000001. Transaction control 

numbers may not be consecutive to a particular customer.

C5.5.1.1.2. Control Number Duplication. The duplication of a 

control number in both header and trailer segments provides the means to identify 

loss of data and easily recognize duplicates.

C5.5.1.2. ST/SE Transaction Set Control Numbers. The originator's 

translation software also assigns the transaction set control number. The number 

starts with 0001 and increments by one for each transaction set within a FG. 

(While a minimum of four digits are required, never transmit more digits than the 

least number needed.) The series restarts at 0001 with the next FG sent.

C5.5.1.3. GS/GE Data Interchange Control Numbers (GS06/GE02). 

This is a one-to-nine-digit number assigned by the originator's translation software. 

The group control number sequence begins with one and, in contrast to the ISA 

control number, is incremented by one for every FG (GS/GE) within an 

interchange. This number simply represents a count of the FGs in the 

interchange.

C5.5.1.4. Sender and Receiver Identifiers. A DoDAAC is the usual 

identifier used by the originators and receivers of DLMS EDI transactions, 

however, the Communications Routing Identifer (CommRI) code can sometimes 

be used. All DoD Component requisitioning Activities are assigned a DoDAAC. 

For non-government trading partners, the Commercial and Government Entity 

(CAGE) code, which identifies commercial contractors authorized to do business 

with the U.S. Government, can be used. Other DLMS trading partners without an 

assigned DoDAAC, CommRI, or CAGE code may be distinguished either by 

telephone number or data universal numbering system (DUNS) code, plus fourdigit telephone suffix, as coordinated through their VAN provider.

C5.5.2. Compression

C5.5.2.1. General. The most significant cost associated with the EDI 

interchange is the cost of communications. Therefore, it is cost effective to reduce 
Enclosure 2, ADC 1265

Page 43

transmitted data to a minimum. DLMS transactions (in EDI format) require roughly 

five times the number of data bytes as an equivalent amount of information 

conveyed using the legacy 80-character data formats. This is due to the 

separation of fields within variable-length records and identification of each 

segment within the transmission. Mandatory control segments also add slightly to 

the overhead. Increasing the number of transactions contained within an envelope 

helps to improve the overhead-to-data ratio, but provides only minor gains in 

efficiency.

C5.5.2.2. Standard Pattern Recognition. The most effective available 

means for reducing transmission size is data compression. This process uses 

standard pattern recognition algorithms that substitute single characters for 

frequently occurring patterns that the decompression process at the other end of 

the transmission line recognizes and replaces with the original patterns. Being 

inherently repetitious, EDI transactions are conducive to such data pattern 

substitutions and, such compression techniques, which can often result in a 40 to 

80 percent reduction in the data transmitted.

C5.5.2.3. Data Compression. Data compression is not a part of the EDI 

format standard. As a result, compression must occur after the EDI translation 

process, including generation of the control envelope, and prior to packaging the 

data for transmission. Some commercial VANs offer data compression as an 

optional service. 

C5.5.2.4. Error-Free Data Recovery. For error-free data recovery, it is 

essential that both sending and receiving software be compatible. Presently, 

DAAS supports multiple compression software packages. As the DLMS enterprise 

service provider, DAAS is responsible for coordinating use of compression 

software. As with version control for EDI conventions, DAAS will manage 

compression software version control through trading partner profile information.

C5.5.3. Encryption. DLMS transactions presently contain only unclassified 

data, but DoD security requirements mandate the use of some form of secure 

encryption technique, such as SFTP, or a secure data transmission method, such 

as Virtual Private Network (VPN), or IBM MQ. DoD policy will prescribe 

acceptable forms of data protection or encryption techniques, which will be 

coordinated between DAAS and its customers.

C5.5.4. Maximum Sizes

C5.5.4.1. Transaction Size Limit. There are no technical limitations on 

the size of EDI transactions. However, there are practical limits imposed by 

transmission duration, speed of the translation process, available storage, 

communications system processing capacities, and application systems 

limitations.
Enclosure 2, ADC 1265

Page 44

C5.5.4.2. Practical Limit. As a practical measure, DLMS transaction 

sets should be limited to not greater than one megabyte (1,000,000 bytes), 

uncompressed, for a single transmission envelope. Should the need arise for a 

larger envelope capacity, such requirement will be negotiated between the 

affected trading partner(s) and DAAS.

C5.5.4.3. Batch Size Restrictions. The restrictions on batch size for 

some requisitioning and billing documents will continue until all of DoD has 

implemented the DLMS. A batch size limit of 496 total documents will continue for 

the Materiel Obligation Validation (MOV) and Interfund Billing Documents. The 

ASC X12 ST/SE envelope size will, also, be restricted by these procedures. For 

EDI conventions, DAAS will manage compression software version control 

information through the trading partner profile.
Enclosure 2, ADC 1265

Page 45

AP1. APPENDIX 1

EDS Defense Automatic Addressing System 

(DAAS)’ PROFILES

AP1.1. Department of Defense (DoD) DATA SERVICES (DData) Profile

AP1.1.1. General. DData is the overarching profile that provides access to 

logistics data and various reports to support the Department of Defense, Federal 

Activities, Civilian Agencies, Commercial Suppliers, Foreign Military Sales (FMS) 

and Security Assistance Countries. DData captures and reports on logistics data 

processed through DAAS and maintains DoD level system repositories in support 

of the customer base of over 228,000 activities located around the world. The 

customers from these activities are able to query repositories, extract information, 

download reports, and are able to access an integrated DoD view of assorted 

data. All of the data repositories are managed by DoD direction and are 

maintained from a DoD perspective.

AP1.1.2. System Descriptions

AP1.1.2.1. Billing and Materiel Obligation Support System (BMOSS) 

Process. The BMOSS manages the Military Interfund Billing/Materiel Obligation 

Validation (MILSMOV) repository and provides query capability and recovery/ 

retransmission of bills and backorder validations. BMOSS provides the capability 

to maintain and distribute fund codes used in the DoD Interfund billing process 

through the following processes:

AP1.1.2.1.1. Military Standard Billing System (MILSBILLS). The 

Defense Automatic Addressing System (DAAS) receives, edits, routes and 

transmits MILSBILLS interfund transactions for the DoD. Each requisition 

processed into a shipping action results in the generation of a billing transaction. 

These interfund bills are archived by the DAAS and are available for retrieval and 

retransmission. The DoD bills data is stored In Accordance With (IAW) DoD 

Instruction (DoDI) 5015.02, while the DoD Foreign Military Sales (FMS) bills are 

stored IAW DoDI 5015.02. The DoD Components are required to submit 

automated inquiries to the DAAS to retrieve bills for their use or may direct that the 

bills be sent to another activity, which is not identified in the MILSBILLS document. 

DAAS maintains the MILSMOV inquiry system and provides the capability to 

interrogate the repository for recovery and retransmission of bills. See Appendix 

3.2.4.

AP1.1.2.1.2. MILSBILLS Fund Code. The MILSBILLS fund code 

is a two-character code used to identify the appropriate accounting data to be 

charged. DAAS maintains the fund codes and serves as the DoD focal point for 

receipt of all file revisions. The codes are updated monthly and posted to the 
Enclosure 2, ADC 1265

Page 46

DAAS web site for activities to download. The DAAS Micro Automated Routing 

System (DMARS) Automated Information System (AIS) uses the fund code 

repository for performing DoD Component requested edits against specific 

logistics transactions.

MILSBILLS Fund Codes can be accessed at

http://www.dla.mil/HQ/InformationOperations/DLMS/

AP1.1.2.1.3. MILSBILLS Inquiry (MILSINQ). This query system 

provides both local and remote users the capability to interrogate/display Interfund 

Bills (MILSBILLS) and Material Obligation Validation (MOV) batches, and 

generate/retransmit requests on-line.

AP1.1.2.1.4. Military Interfund Billing/Material Obligation 

Validation (MILSMOV). The DoD validates all backordered requisitions each 

quarter. These validations are scheduled as required by the business rules 

established in Defense Logistics Management Standards (DLMS). The 

validation process requires the recipient of the MOV to respond within 45 

calendar days or have their backorder cancelled. Since many backorders 

have been funded with prior year’s money, a cancellation of the requirement 

can be catastrophic and cause a considerable impact on the DoD 

Components/Participating Agencies. The DAAS processes the MOV, ensuring 

the batch contains all the individual transactions as determined by the 

transaction count in the header control document. DAAS receives 

approximately 4 - 7 million MOV transactions each quarter, maintaining the 

MILSMOV inquiry system and providing the capability to interrogate the 

repository for recovery and retransmission of MOV batches. The MOV system 

retains all MOV batches and batch acknowledgment receipt transactions sent 

during the current quarter. Thereafter, transactions should be maintained 

IAW DoDI 5015.02, DoD Records Management Program.

AP1.1.2.2. DAAS Master Routing System. Includes the following 

directories:

AP1.1.2.2.1. The DAAS Allied Communications Procedure 

(DAASACP). This environment encompasses both data pattern and narrative 

message routing information and holds the communications routing criteria for 

both data pattern and narrative message routing for the DAAS customer base.

AP1.1.2.2.2. The DAAS Inquiry System (DAASINQ) and Enhanced 

DAAS Inquiry system (eDAASINQ). DAASINQ provides information on 

Department of Defense Activity Address Directory (DoDAAD), National Item 

Identification Number (NIIN), Military Assistance Program Address Directory 

(MAPAD), and Routing Identifier Code (RIC) data elements to DAAS customers. 

eDAASINQ is a Common Access Card (CAC)-enabled version of DAASINQ that 

offers an enhanced capabilities over the DAASINQ application including options to 
Enclosure 2, ADC 1265

Page 47

query the Communication Routing Indicator (COMMRI) and Distribution Code. 

eDAASINQ also allows you to download the DoDAAD and MAPAD files. It 

provides additional queries and downloads by Service or "All" in "TA1" delimited 

format. eDAASINQ is Public Key Infrastructure (PKI)-enabled and access to the 

application may be requested by submitting a System Access Request (SAR) at

https://www.transactionservices.dla.mil/sar/sar_menu.asp.

AP1.1.2.2.3. Department of Defense Activity Address Directory 

(DoDAAD). The DoDAAD is one of the primary files used in the DMARS validation 

and verification processes. DMARS must verify that the DoD Activity Address 

Code (DoDAAC), contained in the DMARS processed transactions, is a valid 

requisitioning activity, based upon being resident in the DoDAAD. The DoDAAD 

has four different Type Address Codes (TACs) which provide an address for: (1) 

mail and small parcel shipments (TAC 1); (2) Outside Continental United States 

(OCONUS) and surface shipments (TAC 2); (3) the billing address for the DoD 

interfund bills (TAC 3); and (4) small parcel shipments (TAC 4). DAAS is the DoD 

Central Consolidation Point (CCP) for maintenance of this file and disseminates

updates (adds, changes, and deletions) to the DoD Components/Participating 

Agencies. See Appendix 3.2.1. for more information.

AP1.1.2.2.4. RIC and Distribution Code. The RIC serves multiple 

purposes in providing source-of-supply, intersystem routing, intra-system routing, 

and consigner (shipper) information. DAAS is the DoD-designated Central Service 

Point (CSP) for maintenance of the RIC, maintains the RIC file, and is the focal 

point for the receipt and dissemination of all file revisions. Distribution codes are 

assigned by the DoD Components, under the DLMS), to identify activities to be 

furnished 100 percent supply and shipment status on all priorities in addition to 

other given status. DAAS is, also, the central DoD repository for the distribution 

code file and the focal point for all file revisions. See Appendix 3.2.3. for more 

information.

AP1.1.2.2.5. Military Assistance Program Address Directory 

(MAPAD). DAAS is the DoD CSP for maintenance of the MAPAD and sends 

updates (adds, changes, and deletes) to the DoD Components/Participating 

Agencies to provide address information for their shipping of materiel and sending 

of documentation. There are nine TACs in the directory, containing addresses for 

various processes. As an example, the TAC 1 address is used for shipping 

unclassified materiel. The TAC 4 address is used to send supply status to the 

FMS country or their designated representative. They in-turn, submit changes to 

DAAS for incorporation into the directory. See Appendix 3.2.2, for more 

information.

AP1.1.2.2.6. Master Source of Supply (SoS) System. The DAAS 

NIIN/SoS File is maintained to ensure DLMS system transactions are routed to the 

correct SoS as required by the DoD Component/ Participating Agency’s business 

rules. Daily updates are obtained from the DLA Logistics Information Service to 

ensure the repository is current.
Enclosure 2, ADC 1265

Page 48

AP1.1.2.2.7. Plain Language Address Directory (PLAD). The 

DAAS PLAD capability provides a linkage between a DoDAAC and its associated 

Plain Language Address (PLA). The PLA is used in the ‘From:’ and ‘To:’ line of a 

narrative message. Users may address narrative messages to the DAAS PLA 

conversion process, and it will look up the DoDAAC(s) placed in the ‘From:’ and 

‘To:’ lines of the input message, replace the DoDAAC(s) with their appropriate 

PLAs, and, finally, send the messages to the appropriate destination. PLA 

information is integrated into the DAASINQ capability, and is displayed as part of 

the DoDAAC query response.

AP1.1.2.2.8. Standard Point Location Code (SPLC). The Military 

Surface Deployment and Distribution Command (SDDC)-Global Freight 

Management (GFM) is required to maintain accurate and current SPLC values in 

their DoDAAC-to-SPLC cross-reference file. The National Motor Freight Traffic 

Association maintains and publishes all valid SPLC assignments and updates 

newly assigned nine-digit values. DAAS administers the SPLC maintenance in the 

DoDAAF in support of the DoD transportation payment program. Maintenance of 

the SPLC values in the DoDAAF is done in accordance with the Logistics 

Management Institute Report, Generating Nine-Digit Standard Point Location 

Codes for the Defense Transportation Payment Program, June 1995, with 

changes submitted daily. DAAS ensures the accuracy and completeness of the 

SPLC data and generates changes when appropriate. SPLC is a critical element 

in support of the DoD transportation payment program.

AP1.1.2.3. Logistics Data Gateway (LDG). LDG is a comprehensive 

architecture that provides a set of business intelligence tools allowing a customer 

fast and easy online access to the vast amount of data processed and maintained 

in the DAAS data bases. This DoD-level data warehouse provides easy web 

access to current and historical data in an integrated form that flows through the 

DAAS. Data is available for operational research via the internet to support 

analysis, create reports, track requisitions, monitor trends, and project future 

needs based on the true demands of the customer. The customer is able to 

format output to fit their exact needs and save that output securely on the DAAS 

server, or distribute the results, as desired. Standard Commercial Off-The-Shelf 

(COTS) tools are used to allow users access to information and data resident at 

DAAS. These tools allow retrieval of needed data from multiple repositories within 

DAAS and the application of customer business rules to accomplish the translation 

and aggregation of DAAS managed data. The ultimate goal is to work more 

effectively with the war-fighter by: improving the capability to track the movement 

of critical spare parts; identify logistics bottlenecks; provide visibility of misdirected 

shipments, and facilitate the identification of processing errors using the data 

provided by the LDG. The LDG is a vital element in supplying logistics data from 

one source to support the total logistics reporting requirements throughout the 

DoD.

AP1.1.2.4. Logistics Information Data Systems. Includes the following 

information systems:
Enclosure 2, ADC 1265

Page 49

Logistics Information Data Services (LIDS). The LIDS is a report 

generation system providing standard monthly, quarterly, semiannual, and ad-hoc 

reports for DAAS and the DoD Components/Participating Agencies. The reports 

are stored on the DAAS’ web site for customer review. The data is compiled from 

historical files and later correlated into various sections of the LIDS report. Special 

ad hoc reports, related to logistical transactions, can be accommodated by special 

request on a ‘one-time’ or ‘temporary basis.’

AP1.1.2.5. Logistics Metrics Analysis Reporting System (LMARS). The 

LMARS tracks materiel as it moves through the logistics pipeline and reports the 

associated response times. LMARS has archived data IAW DoDI 5015.02 

LMARS uses information from DLMS transactions processed by the DAAS, 

Electronic Data Interchange (EDI) transaction feeds, off-line data feeds, and 

transportation data received from the Integrated Data Environment Global 

Transportation Network Convergence (IGC) to measure the logistic response time 

for wholesale-managed items. The data recorded in the Logistics On-line Tracking 

System (LOTS) repository regarding wholesale-managed items is used to produce 

transaction counts and average pipeline processing times, in days, for the 12 

segments comprising the life cycle of a logistics transaction. The measurement 

begins with the serial (i. e. birth) date of the requisition and ends with receipt by 

the DAAS of the Material Receipt Acknowledgement (MRA) transaction. Standard 

LMARS reports (See appendix 5.2.) are produced weekly and monthly. LMARS 

provides the DoD community with the capability to maintain, track, extract, and 

tailor logistics data to their needs and its supporting infrastructure through the lifecycle tracking of logistics transactions, further supporting command and control 

decisions, through an ad-hoc query capability that runs in seconds instead of 

weeks. This capability generates reports on DoD-wide Logistics Response Time 

(LRT) measurements and on the performance of the logistics pipeline. See 

appendix 3.2.7. and appendix 5.2, for more information. Components include:

AP1.1.2.5.1. Logistics Response Time (LRT). LRT measures the 

logistics processing time elapsed at the wholesale level. LRT begins with the 

requisition entry into the wholesale level by the originating Supply Support Activity 

(SSA), and ends with the receipt of the item at the wholesale level SSA. LRT does 

not include the elapsed time from the identification of the item need by the 

customer (mechanic, electrician) until the item is received by that customer. The 

DoD has identified LRT as a key performance measure to monitor supply chain 

effectiveness. Using data that is readily available from DAAS, the DoD performs 

analysis on the logistics response time of the pipeline processes. DAAS provides 

the LRT data to the DoD Components in a web-based environment for their use in 

preparing local LRT reports. Other categories of materiel, such as medical 

supplies and subsistence, were added to the LRT measure to show impact to their 

areas of supply. All transactions related to medical and subsistence do not flow 

through DAAS, but are provided through off-line feeds.

AP1.1.2.6. Logistics On-line Tracking System (LOTS). The LOTS is a 

DAAS managed repository providing enhanced capabilities for extracting pertinent 
Enclosure 2, ADC 1265

Page 50

logistics transaction information that flows through DAAS. This information 

supports logistics management, information query, transaction tracking, and 

reporting requirements. The LOTS is populated from images of transactions 

processed by the DAAS. Requisition related transactions or excess transactions 

are stored in the LOTS repository for research, tracking, production of reports, and 

management services. The LOTS repository can be accessed by DAAS produced 

tools (e.g. Web Visual Logistics Information Processing System (WebVLIPS) and 

Web Logistics On-Line Tracking System (WebLOTS) which allow tracking and 

retrieval of requisition, passive RFID, and excess life cycle information. 

WebVLIPS provides access to addressing and stock number information stored at 

DAAS, linking that information to the DLMS transactions stored in LOTS. LOTS 

shows the life cycle of logistics transactions, tracking requisitions from their 

release into the DoD pipeline until the materiel is posted to the accountable record 

at the destination activity. The LOTS provides tracking of excess transactions and 

the movement of those excesses to the destination depot or disposal site. It, also, 

provides two tables in support of passive RFID implementation: one to facilitate 

registration of passive RFID readers/portals and the other to record the actual 

passive RFID tag read by those readers/portals. WebLOTS provides the 

capability for external systems to utilize direct tailored system queries to access 

LOTS data. See appendix 3.2.6. for more information. LOTS can be accessed 

through the following two web-enabled systems:

AP1.1.2.6.1. Web Visual LIPS Query System (WebVLIPS). 

WebVLIPS is a web based query system that can be accessed from any internet 

attached personal computer using either the Internet Explorer or Firefox browser. 

WebVLIPS accesses data in the LOTS repository. The WebVLIPS customer can 

track a requisition throughout the logistics pipeline from the time the requisition is 

released into the DoD pipeline until the materiel is posted to the accountable 

records at the requisitioning activity. WebVLIPS has the capability to track reports 

of excess and the movement of those excesses either to the destination depot or 

to a disposal facility. WebVLIPS integrates information on DoDAAD, MILRI, SoS, 

project code, port code, status code, unit of issue code, signal code, hold code, 

advice code, condition code, and mode code to assist the customer in tracking the 

life cycle of the requisition. It also captures and visualizes the extended 

transportation data (e.g., secondary transportation tracking numbers, commercial 

carrier identification by Standard Carrier Alpha Code (SCAC), transportation 

priority, and origin shipper identification) in DLMS Supply Shipment Status 

messages. This is not otherwise available in Defense Logistics Standard System 

(DLSS) or Military Standard Requisitioning and Issue Procedures (MILSTRIP) 

legacy transaction shipment status transactions. WebVLIPS is typically used by 

the customer for single queries, which do not require the results to be input directly 

into their logistics systems. WebVLIPS returns query results to the customers in 

the form of a web page and provides a Distribution Standard System (DSS)

asset query (asset balance/due-in) for the Defense Logistics Agency (DLA)

supply centers, except for DLA Aviation.
Enclosure 2, ADC 1265

Page 51

AP1.1.2.6.2. Web Logistics On-line Tracking System (WebLOTS). 

WebLOTS is a system-to-system web interface which allows the customer’s 

system to query the LOTS database for the latest status for their requisitions. 

WebLOTS queries return requisition status data (such as National Stock Number 

(NSN), Quantity, Inventory Control Point (ICP), etc.). Prior to establishing a 

WebLOTS interface, users must complete a SAR and negotiate a Memorandum of 

Agreement (MOA) with the WebLOTS project manager. When completed, the 

user’s system can be setup to perform queries by document number, 

Transportation Control Number (TCN), unit of issue, and Julian date. The MOA 

will detail the type and number of queries being utilized by each customer. 

WebLOTS interfaces are typically utilized when the customer has a requirement 

for large amounts of logistics data to be input directly into their system(s) for 

processing.

AP1.2. DoD GATEWAY (DGATE) PROFILE

AP1.2.1. General. The DGATE profile represents the entry point for DLSS or 

MILSTRIP legacy transactions, and selected EDI transactions into the DAAS

infrastructure. DGATE is a key profile for DAAS, which provides a strategic 

gateway for processing and transmitting the received legacy logistics data to a 

myriad of activities that operate within the logistics community. The DGATE 

profile, also, provides for the network and data interoperability within these 

activities to facilitate the exchange of logistics data. It supports the interoperability 

of mission support functions, including the capturing of requirements, repository 

file maintenance, communications exchange, logistics data routing, and 

distribution.

AP1.2.2. Profile Component Description. DGATE is composed for the 

following systems:

AP1.2.2.1. DAAS Automated Message Exchange System (DAMES). 

DAMES is a locally written Personal Computer (PC) client software that provides a 

communications capability, allowing Foreign Military Sales (FMS) customers to 

exchange logistics data with the US Government and the DoD logistics 

community. DAMES PC based Software functions as an interface for the 

customer and provides the capability to communicate directly with DAAS, sending 

and receiving logistics transactions and narrative message traffic. The Microsoft© 

Windows version of DAMES communicates via Secure File Transfer Protocol 

(SFTP) over the internet. The DAAS’ Single Gateway manages the input and 

output files for those DAMES users that utilize SFTP as their method of 

exchanging logistics data with DAAS. As data is received, Service Oriented 

Messaging Architecture (SOMA) validates the format of the input message file for 

further processing. Transaction files, produced by end users’ programs, are built 

using standard Joint Army-Navy-Air Force Publication (JANAP) data pattern 

message format. Messages containing narrative text, MILSTRIP transactions and 

non-standard part number requisitions may also be built interactively through the 

DAMES software interface. Messages built for transmission are contained within a 
Enclosure 2, ADC 1265

Page 52

portion of a file in the software until the next communication connection. When a 

communication session has been established, all active messages are sent from 

the end users PC to DAAS, and then all messages stored at DAAS, addressed to 

the end user are transmitted back to the end user’s PC. Various menu options are 

available to process the receive file such as displaying, editing, printing, sorting, or 

saving to a disk file. See Appendix 2.2.2. for more information.

AP1.2.2.2. DAAS Logistics Gateway System (DLOGS). DLOGS is a 

collection of services and programs within DAAS, which provides an entry point 

and central communications node that enables DoD Components/Participating 

Agencies to communicate seamlessly over disparate networks and with each 

other. It accepts numerous formats including transactions in DLMS ASC X12 or 

eXtensible Markup Language (XML), and User Defined File (UDF) and then 

converts the non-standard formats to a DAAS internal message format (DIMF)

suitable for processing. The four major components within the DLOGS are the (1) 

DAAS Single Gateway (DSG), (2) SOMA, (3) DAAS Routing Control System 

(DRCS), and (4) DMARS. The DSG provides secure front-end communications 

services for the DAAS, utilizing communication protocols such as, SFTP, IBM 

Messaging Queue (MQ), Hyper Text Transfer Protocol Secure (HTTPS), Simple 

Mail Transfer Protocol (SMTP), etc. The DSG also provides initial authentication 

and login services. SOMA provides message validation, message transformation, 

back-end authentication and logging services, enterprise service bus functionality, 

and other services. The DMARS performs transaction level services, such as, 

validation, editing, routing, imaging and exception processing. DRCS provides 

batching, batch integrity, statistics, exception and reject handling, and special 

processing. The following major services are provided under the DLOGS 

umbrella:

AP1.2.2.2.1. DAAS Single Gateway (DSG). The majority of 

software and hardware components of the DSG reside in the DAAS Demilitarized 

Zone (DMZ) providing a secure front-end communications service for the DAAS; 

utilizing communication protocols, such as, SFTP, IBM MQ, HTTPS, SMTP, etc. 

Connections into the DSG are prevented from directly accessing the DAAS 

internal enclave. All communication attempts 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. SOMA primarily processes files and 

messages containing DLSS formatted transactions. Messages may contain one 

or more transactions. SOMA receives and transmits files and messages using 

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:

AP1.2.2.2.2.1. Receiving files outside of the DLSS 

transaction format and forwarding them to the appropriate internal applications 

based on the file's filename.
Enclosure 2, ADC 1265

Page 53

AP1.2.2.2.2.2. Performing duplicate header information 

checks.

AP1.2.2.2.2.3. Converting file formats to the DAAS Internal 

Message Format (DIMF).

AP1.2.2.2.2.4. Transformation of messages based upon the 

required delivery protocol and message format.

AP1.2.2.2.2.5. Transmission of output message information 

to the archive process for historical retransmission and reporting purposes.

AP1.2.2.2.3. DAAS Micro Automated Routing System. DMARS

receives messages containing one or more transactions from SOMA. It then 

performs transaction level services, such as, transaction validation, editing, 

routing, imaging, and exception processing based on customer supplied business 

rules. These business rules are routing, editing, and image instructions 

maintained within the DMARS program logic. Each DoD Component/Participating 

Agency has its own business rules relative to the routing and editing of its 

transactions. The DAAS Management Support Directorate, with input from DoD 

Component/Participating Agency Point of Contact (POC), dictates the application 

of business rules encoded in the DMARS. Once transactions have been 

validated, edited, and routed, they are sent to the DRCS for further processing.

AP1.2.2.2.4. DAAS Routing Control System DRCS). DRCS is 

responsible for receiving transactions from the DMARS and forwarding them to the 

SOMA for delivery. DRCS provides batching and batch integrity services for the 

routed transactions from DMARS and then forwards the transactions to SOMA for 

message creation and transmission. The DRCS is also responsible for statistical 

reporting, exception and reject handling, archiving all transactions, and performing 

special processing.

AP1.2.2.2.5. Web Requisitioning (WebREQ). Provides the DoD 

Components/Participating Agencies with the capability to build and submit 

transactions via HTTPS. These transactions are sent to DAAS for processing. 

This capability allows for submission of any DLSS or MILSTRIP legacy transaction

type. The supply status transactions can be returned back to the customer using 

this same methodology.

AP 1.2.2.2.6. DoD Web Supply Discrepancy Report (WebSDR). 

An application system that provides a web-based entry method for inputting 

Supply Discrepancy Reports (SDRs) attributable to shipping or packaging 

discrepancies, which supports DLMS transaction exchange requirements. The 

DoD WebSDR provides the capability to automate the SF 364 SDR paper-based 

form and transition the format to a Commercial EDI standard. The DoD WebSDR 

system facilitates communications and interoperability between U.S. Military, DoD, 

and Federal Agencies in order to determine the cause of such discrepancies, 
Enclosure 2, ADC 1265

Page 54

effect corrective action, and prevent recurrence of the discrepancy. It allows 

routing for web submissions and logistics transactions according to business rules, 

translation to standard DLMS transaction formats in X12 and XML, conversion to 

e-mail format, as needed, and, by exception, the Army pre-DLMS user-defined file 

format, which supports information exchange between the action office and the 

shipper. When requested by DoD Components/Participating Agencies, the 

WebSDR application supports business rules for information copy preparation and 

distribution to provide visibility of discrepancies to relevant organizations. DoD 

WebSDR captures the SDR and response management statistics to facilitate 

performance reviews and provides an automated process for tracking SDR 

response information. The Auto-fill feature uses the DAAS requisition history to 

populate the SDR. ICPs, Depots, and Action Agencies can initiate their responses 

via the DoD Component-sponsored SDR application for transmission via DLMS 

interface or use the DoD WebSDR on-line capability pending DLMS 

implementation. This allows for faster resolution of discrepancies and near-real 

time SDR reporting for immediate identification of discrepancies. It, also, reduces 

response delays resulting from misrouted SDRs or mailed documents. Automated 

edit and rejection capability enforces SDR procedure and transaction format 

compliance by returning inappropriate transmissions to the originator for 

correction, thereby, reducing Component receiving system errors. Web–based 

queries allow users to have immediate access to the DAAS historical data related 

to the discrepant shipments. DoD WebSDR provides the capability to upload 

documentation and pictures in support of the discrepancy claim. Queries and 

management reports make it possible to locate specific SDRs by various criteria 

and identify trends, establish volume and dollar values of SDRs, bring 

management attention to problems with shipping activities, measure compliance 

with SDR timeframes, and improve the requisitioning and distribution processes 

within logistics operations. The DoD WebSDR application moves the SDRs into 

an integrated transactional environment, providing an effective means to report, 

resolve, and measure discrepancies related to pipeline performance.

AP1.2.2.3. System Access Request (SAR). The SAR system provides 

a formal request mechanism for obtaining access to the various systems activities 

on the DAAS website.

AP1.3. DAAS ELECTRONIC BUSINESS (EBUS) PROFILE

AP1.3.1. General. The DAAS EBUS profile processes standard logistics 

transactions (Accredited Standards Committee (ASC) X12, or XML) covered by 

specific DLMS Implementation Conventions (ICs). As the DoD Components/ 

Participating Agencies implement the DLMS formats, the DAAS’ transaction 

processing workload is continuing to grow for both the DLMS and the DLSS

transactions. It is expected that, eventually, as most customers migrate from the 

DLSS, the DMLS ASC X12 or other variable-length transactions, such as XML, will 

eventually predominate. The DAAS architecture will ensure that all standard 

transaction formats, as authorized within the DLMS, are accommodated in the 

DAAS processing. DAAS has assumed program management responsibility for 
Enclosure 2, ADC 1265

Page 55

the GEX as part of the dissolution of the Business Transformation Agency (BTA) 

and is subsuming the two Defense Information Systems Agency (DISA) GEX sites 

by migrating all of their customers/connections to the two DLA GEX eB gateway 

sites.

AP1.3.2. eBusiness System Description. EDI Gateway System Process. 

EDI provides standard transaction formats for use in the automated, machine-tomachine, exchange of eB transactions between the DoD Components/ 

Participating Agencies, and their commercial sector trading partners. DAAS

operates a centralized DoD eBusiness Communications Gateway capability that 

provides standard EDI and XML transaction routing, delivery, archiving, 

translation, and Value Added Network (VAN) mail-boxing services through the 

following:

AP1.3.2.1. DoD Global Exchange (GEX) Gateway. In providing EDI 

telecommunication services, DAAS utilizes the standard GEX software suite 

developed to support the DoD Electronic Commerce Infrastructure. The GEX 

application provides the capability to securely receive/send transactions via many 

different telecommunication protocols, sort/route the transactions, apply the 

appropriate translation/mapping utilities, provide decoding/validation of X12 syntax 

rules, log all activities, archive files, alert users of errors, and apply 

routing/distribution list processes.

AP1.3.2.2. Transaction Translation. The COTS IBM Transformation 

Extender (ITX) (formerly Mercator) mapping and transformation software toolset 

currently provides the translation capability to convert incoming transaction 

formats into the appropriate outgoing transaction formats, via business mapping 

rules. DAAS is also utilizing a second commercial translation software product 

called Ab Initio that has been employed by the DISA GEXs for some of their 

customer mappings.

AP1.5. DLA INTEGRATED DATA ENVIRONMENT (IDE) PROFILE

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

have assumed responsibility for the sustainment of the DLA IDE.

AP1.5.2. System Description: The DLA IDE supports data and information 

sharing through a single point of access that supports the exchange of DLA data 

between systems, sharing of DLA corporate logistics information, and enhanced 

DoD Asset Visibility. Additionally, IDE provides assured access to supply chain 

management data, centrally managed metadata, authoritative data sources, and 

DoD logistics business rules. Additionally, IDE supports logistics (supply chain & 

distribution) Communities of Interest and reduces system-to-system interface 

costs through implementation of net-centric (webMethods) data strategy goals.
Enclosure 2, ADC 1265

Page 56

AP1.5.3. Discussion: Per the DLA IDE Transition Initiative the former IDE 

mission, services, and interfaces have been incorporated into and 

considered a part of the DAAS program, and is considered a part of the 

standard DAAS business through the use of its various AIS applications 

including the DSG, SOMA, and GEX.
Enclosure 2, ADC 1265

Page 57

AP2. APPENDIX 2

INTERNATIONAL LOGISTICS COMMUNICATIONS 

SYSTEM (ILCS)

AP2.1. GENERAL

The ILCS provides a logistics communications service for Foreign Military Sales 

(FMS) countries, FMS freight forwarders/contractors and other Department of 

Defense (DoD) Activities. This service provides a telecommunications capability 

that allows an FMS customer to exchange logistics related information with the 

U.S. Government and the DoD logistics community. FMS customers interested in 

acquiring ILCS services must notify the appropriate International Logistics Control 

Office (ILCO). The respective ILCO: Air Force Security Assistance Center 

(AFSAC), United States Army Security Assistance Command (USASAC), or Naval 

Supply Systems Command (NAVSUP), will interface with DAAS to acquire the 

required services via a new or existing FMS case. The ILCS utilizes (DAAS) 

Automated Message Exchange System (DAMES) software package, allowing the 

subscriber to interactively build requisitions and/or narrative messages in DAMES 

or upload data to DAMES from another system. Transmitting and receiving of 

these messages and/or data is accomplished via a Secure File Transfer Protocol 

(SFTP) connection, or an Async to Point to Point Protocol (PPP) dial up 

connection, linked to the DAAS:

AP2.1.1. Delivery. DAAS receives the ILCS message traffic for editing, 

validating, verifying, routing, and delivering the transactions to the appropriate 

destination. The ILCOs provide approval for Countries to receive various data. 

DAAS customizes the data according to each ILCO/Military request.

AP2.1.2. Routing. DAAS routes the ILCS message traffic in accordance with 

the ILCS subscriber destination Communications Routing Indicator (COMMRI) and 

any associated business rules.

AP2.1.3. Policy. Under existing policy, ILCS traffic addressed to the DAAS 

COMMRI must be sent via existing communications channels between DAAS and 

the appropriate ILCO management information system, where the logistics 

transactions are validated against established FMS cases. Military Standard 

Requisitioning and Issue Procedures (MILSTRIP) transactions will be processed 

individually and forwarded to the appropriate Military Service (Air Force – Security 

Assistance Management Information System (SAMIS), Army – Centralized 

Integrated System for International Logistics (CISIL), or Navy – Management 

System for International Logistics (MISIL)) for further service specific processing. 

After passing validation edits, requisitions will be sent to the appropriate Source of 

Supply (SOS).
Enclosure 2, ADC 1265

Page 58

AP2.1.3.1. The Security Cooperation Enterprise Solution (SCES) sponsored 

by the Defense Security Cooperation Agency (DSCA) is a tri-Service solution that will 

replace the aforementioned ILCO management information systems through staggered 

implementation. Upon completion of Service implementation, ILCS traffic will be 

forwarded to SCES based on the document number Service/Agency code (which 

equates to the Security Cooperation (SC) implementing agency code). The United 

States Navy is so far the only service to migrate into SCES. Pending completion, the 

legacy ILCO management systems will be responsible for ensuring that cases managed 

by SCES are forwarded to SCES by inserting the applicable Defense Security 

Cooperation Agency (DSCA) RIC, distribution code, and fund code values.

AP2.1.4. Non-DAAS CommRIs. ILCS traffic, with non-DAAS destination 

CommRIs, are relayed by DAAS, via the appropriate communications network, to 

the activities represented by the destination CommRIs. Examples are freight 

tracking transactions and/or narrative messages exchanged between an FMS 

subscriber and its freight forwarders/contractors.

AP2.2. SYSTEM DESCRIPTION 

The ILCS is an internet PC-based software communications system designed for 

the FMS community and DoD Services/Agencies with DAAS as the central 

interface point. The DAAS ILCS network consists of three automated systems: 

(1) the Service Oriented Messaging Architecture (SOMA), (2) the DAMES standalone PC application, and (3) the ILCS subscriber’s system. The normal mode of 

communication for the ILCS community is via the DAAS DAMES communications 

software package, although there are other communications methods available. 

DAMES users, connect via an Internet Service Provider (ISP), using SFTP or 

Async to PPP, which provides connectivity to the entire DISN customer base. 

Message traffic from an ILCS subscriber flows from their local system to the DAAS 

SOMA and then to the DoD logistics community via appropriate communications 

networks. Message traffic transmitted to an ILCS subscriber flows from SOMA 

directly to the subscriber’s DAMES system. The message traffic exchange path 

for the ILCS is described as follows:

AP2.2.1. SOMA. A highly reliable, high availability relational database 

environment that provides telecommunications interoperability and network 

connectivity. All logistics transactions received in messages from ILCS 

subscribers are processed by DAAS for the purpose of editing and applying the 

DoD Components’ business rules and procedures. SOMA can interface through a 

variety of communications networks using numerous worldwide standard 

protocols.

AP2.2.2. DAMES. The DAMES PC Software Package is a fully automated 

telecommunication software package designed for use on a PC system. The 

installed DAMES software provides the ILCS subscriber with a true ‘stand-alone’ 

telecommunications terminal or it can be designed to act as a ‘front-end processor’ 

to a subscriber’s existing telecommunications network. DAMES has been 
Enclosure 2, ADC 1265

Page 59

implemented on PC systems because of their relative low cost, small physical 

footprint, and proven reliability under a wide range of operating environments. 

DAMES communications are via the internet. through either a Value Added 

Network (VAN) or ISP, or via an Async to PPP connection.

AP2.3. ILCS SYSTEM OPTIONS. An ILCS connection may be provided for the 

subscriber in one of two ways:

AP2.3.1. Subscriber’s Use of an Existing PC System. The ILCS subscriber 

can use an existing PC system with communications capability. DAAS will provide 

the prospective subscriber with specifications and technical assistance to allow 

them to install the DAMES software package on their existing PC system.

AP2.3.2. DAAS Developed Turnkey PC System. This option is available to 

an ILCS subscriber within four to six months from signing a letter of agreement 

with their appropriate ILCO. The turnkey PC system provides the subscriber with 

everything needed to implement its ILCS connectivity, such as, hardware, 

software, training, and installation of the system at the subscriber’s designated 

location. The DAMES software package is menu driven and provides for easy 

system operation. An important feature of the software is the interactive message 

preparation function, where messages can be entered directly into the computer in 

an online mode, instead of preparing messages off-line. This feature eliminates 

the requirements for formatting, editing, and double keying of messages, since the 

operator only has to follow the instructions on the menu and insert the message 

text.

AP2.4. SYSTEM ORIENTATION AND TRAINING

When a subscriber procures the turnkey system, the complete system is installed 

at the DAAS facility for a period of up to 60 calendar days. During this period, the 

system undergoes a complete ‘hot-stage’ testing phase. After the ‘hot staging’ is 

completed, the system is de-installed and shipped to the subscriber’s designated 

receiving point. After the system has been received at the subscriber’s ILCS 

location, DAAS personnel are dispatched to perform the system installation and 

orientation training for the subscriber’s designated personnel. The orientation 

training consists of hardware familiarization, and DAMES software and system 

operations training. As FMS countries acquire more sophisticated and costly 

weapon systems, rapid communications of logistics data becomes more essential 

in obtaining an acceptable readiness posture. The ILCS provides a direct, rapid 

connection, between FMS subscribers and the U.S. logistics community. By 

reducing the time that logistics transactions are within the communications 

pipeline, improvements in the FMS subscriber’s readiness posture occur by 

ensuring earlier receipt of needed materials.
Enclosure 2, ADC 1265

Page 60

AP2.5. SYSTEM COSTS

The investment and recurring costs of the ILCS are reimbursed by the FMS 

country to the U.S. Government annually under an established FMS case.

AP2.6. WORLDWIDE CUSTOMER BASE

ILCS has been operational since 1979 and, since its inception, has been extended 

to over 40 countries and their associated FMS freight forwarders/contractors. 

Currently, there are more than 100 individual ILCS system connections operating 

throughout the world.
Enclosure 2, ADC 1265

Page 61

AP3. APPENDIX 3

DEPARTMENT OF DEFENSE (DoD) AND DEFENSE 

LOGISTICS AGENCY (DLA) REPOSITORY 

CUSTODIAN

AP3.1. GENERAL. When the Defense Logistics Standard System (DLSS) 80 

record position legacy transactions were developed in the early 1960s, it was 

recognized that the constraints of an 80-character punch card would necessitate 

the use of a large amount of coded data needed in identifying different activities. 

As an example, the six-character Department of Defense Activity Address Code 

(DoDAAC) was developed to show various levels of activity such as the 

requisitioner, ship to addresses, and addresses for sources of supply and activities 

storing materiel. Because there are fewer supply sources, distribution depots, and 

other activities that redistribute materiel, it was determined a three-character 

Routing Identifier Code (RIC) would be sufficient to satisfy the requirement for this 

code. The need for coded data to show the various addresses or other 

information within the 80-character transaction made it necessary for the Defense 

Automatic Addressing System (DAAS) to create and maintain repositories to 

facilitate support of the logistics processes.

AP3.2. REPOSITORY DESCRIPTIONS

AP3.2.1. Department of Defense Activity Address Directory (DoDAAD). 

DoDAAD contains the names and addresses of military organizations that 

requisition, receive, or ship materiel; Federal agency organizations that maintain 

logistics support arrangements with the DoD; and commercial organizations that 

enter into materiel and/or service contracts with the DoD. The DoDAAC is a sixcharacter code with the first character representing the DoD Component/ 

Participating Agency. DAAS performs the following services:

AP3.2.1.1. The DoD custodian for Defense Logistics Manuals (DLM), 

DLM 4000.25, Volume 6, Chapter 2.

AP3.2.1.2. Receives updates from the DoD Components/Participating 

Agencies.

AP3.2.1.3. Maintenance and dissemination of changes from a single 

location.

AP3.2.1.4. Provides capability for queries and downloads.

AP3.2.1.5. Executes Service Point functions for DLA and the DoD 

Components/Participating Agencies.
Enclosure 2, ADC 1265

Page 62

AP3.2.2. Military Assistance Program Address Directory (MAPAD). The 

MAPAD contains the names and addresses of country representatives, freight 

forwarders, embassy offices, and customers within a country for releasing Foreign 

Military Sales (FMS) and Military Assistance Program (MAP)/Grant Aid shipments 

and those addresses required for transmitting the related documentation. MAPAC 

is a six-character code with the first character representing the DoD Component 

and the country represented by the second and third characters. DAAS provides 

the following services:

AP3.2.2.1. The DoD custodian for DLM 4000.25, Volume 6, Chapter 3.

AP3.2.2.2. Processes updates received from the MAPAD Web-Update 

application.

AP3.2.2.3. Performs maintenance and disseminates changes from a 

single location.

AP3.2.2.4. The capability to perform queries and downloads.

AP3.2.3. RIC and Distribution Codes. This repository contains the names 

and addresses of supply sources, distribution depots, and other activities that 

redistribute materiel. RIC is a three-character code with the first character 

representing the DoD Component or other Participating Agency. The distribution 

code is a one-character code used to identify a monitoring activity to receive 

supply/shipment status relative to the processing of a requisition. DAAS provides 

the following services:

AP3.2.3.1. The DoD custodian for the RIC and Distribution Code 

appendixes in DLM 4000.25-1.

AP3.2.3.2. Receives updates from the DoD Components/Participating 

Agencies.

AP3.2.3.3. Performs maintenance from a single location.

AP3.2.3.4. Provides the capability for queries and downloads.

AP3.2.3.5. Performs the RIC Service Point (SP) functions for DLA.

AP3.2.4. Military Standard Billing System (MILSBILLS) Fund Codes. This 

repository contains a two-character code that can be used in lieu of the 

appropriation long line of accounting information as identified in the financial 

processing system. The fund code supplement to MILSBILLS correlates the twocharacter fund code to the appropriation accounting number for the DoD 

Components and Participating Agencies. DAAS provides the following services:

AP3.2.4.1. Acts as the DoD custodian for the fund code database.
Enclosure 2, ADC 1265

Page 63

AP3.2.4.2. Receives updates from the DoD Components/Participating 

Agencies.

AP3.2.4.3. Performs maintenance from a single location.

AP3.2.4.4. Provides the capability for queries and downloads.

AP3.2.4.5. Distributes changes to the DoD Components/Participating 

Agencies.

AP3.2.5. MILSBILLS Interfund Billing/Material Obligation Validation (MOV). 

This repository contains an image of all the MILSBILLS Interfund transactions and 

MOV transactions received and processed by the DAAS:

AP3.2.5.1. DAAS provides the following services for the MILSBILLS 

Interfund Billing:

AP3.2.5.1.1. Validates extended dollar value, batch integrity, and 

the buyer DoDAAC.

AP3.2.5.1.2. Routes Interfund bill transactions from seller to buyer.

AP3.2.5.1.3. Archives and maintains the official DoD repository.

AP3.2.5.1.4. Retains DoD Interfund Bills in a readily accessible 

format for one year.

AP3.2.5.1.5. Retains FMS Interfund bills in a readily accessible 

format for two years.

AP3.2.5.1.6. After these business rules have been satisfied, 

maintain records in accordance with DoD Instruction 5015.02, DoD Records 

Management Program.

 AP3.2.5.1.7. Provides the capability for query, recovery, and 

retransmission of Interfund bills.

AP3.2.5.2. DAAS provides the following services for the MOV 

transactions:

AP3.2.5.2.1. Validates batch integrity and the DoDAAC.

AP3.2.5.2.2. Routes and delivers MOV batches to the appropriate 

destination.

AP3.2.5.2.3. Archives and maintains the official MOV repository.

AP3.2.5.2.4. Generates responses to the Inventory Control Points 

(ICPs), as requested by the DoD Components/Participating Agencies.
Enclosure 2, ADC 1265

Page 64

AP3.2.5.2.5. Provides the capability for query, recovery, and 

retransmission of MOV batches.

AP3.2.6. Logistics On-line Tracking System (LOTS). LOTS provides the 

ability to maintain, track, extract, and tailor logistics data to the needs of the DoD 

community and its supporting infrastructure. On-line query of the LOTS provides 

life cycle tracking of logistics transactions supporting command and control 

decisions and a timely ad hoc query capability that provides user-specific 

information in near-real time. LOTS supports Government-wide information query, 

transaction tracking, and reporting requirements, thus aiding in logistics 

management. Information extracted from requisitions and requisition related 

transactions or excesses stored in LOTS can be accessed by Web Visual 

Logistics Information Processing System (WebVLIPS) and WebLOTS (System-toSystem), thereby allowing the DAAS’ customers to track requisitions and excesses 

throughout their life cycle. LOTS also captures the passive RFID registration and 

visibility transactions and makes the information available to AV for customer 

tracking. These tools can access addressing and stock number information to 

provide enhanced information to the customer.

AP3.2.7. Logistics Metrics Analysis Reporting System (LMARS). LMARS 

provides a capability to track materiel by pipeline segment as it flows through the 

logistics pipeline and reports the associated response times. LMARS is populated 

with information from the Defense Logistics Management Standards (DLMS) 

X12/eXtensible Markup Language (XML) or the DLSS transactions that flow 

through the DAAS. LMARS reports response times within any of the 13 nodes of 

the logistics pipeline. All reporting timeframes are in terms of days. LMARS 

contains data from its inception, February 1997, to present. Standard reports are 

available (via the web) on a weekly/monthly basis.
Enclosure 2, ADC 1265

Page 65

AP4. APPENDIX 4

SPECIAL PROCESSING RULES CONTACTS

AP4.1. GENERAL

For specific information on the Department of Defense (DoD)

Component/Participating Agency special processing rules, contact the Defense 

Automatic Addressing System (DAAS) Customer Service Support at:

DAAS – Logistics Support.

Phone: Commercial (614) 692-6672 Option 2 / DSN: (312) 850-6672 Option 2.

FAX: Commercial (937) 656-3800 / DSN 986.3800.

Customer Service Support: For assistance with DAAS application Issues, Logistics 

Support, or Electronic Data Interchange (EDI) Support please utilize the DAAS 

webpage at: https://www.transactionservices.dla.mil/daashome/customerassistance.asp

Or, e-mail may be sent directly to: daascustomersupport@dla.mil

General / Logistics - daascustomersupport@dla.mil

EDI - EDI@dla.mil
Enclosure 2, ADC 1265

Page 66

AP5. APPENDIX 5

LOGISTICS INFORMATION DATA SERVICES (LIDS)

AP5.1. GENERAL

The Logistics Information Data Services (LIDS) is a report generating system 

which produces information in support of the Department of Defense (DoD)

Components/Participating Agencies. The reports described below are controlled 

under Reports Control System (RCS): A&T (AR) 1113, established by Office of 

the Assistant Secretary of Defense (Logistics and Materiel Readiness) (ASD 

(L&MR)), and are produced by the Defense Automated Addressing System 

(DAAS) as required by the proponent and users of the data. Reports are posted to 

the DAAS website for viewing and downloading by the DoD 

Component/Participating Agency customers on the 10th day of each month.

AP5.2. REPORTS

The following reports are prepared and issued under the above RCS:

AP5.2.1. Unauthorized Priority Designator Assignment. This report identifies 

suspected abuse of priority designator assignment. It also gives visibility of 

requisitions automatically downgraded by the DAAS during requisition processing, 

as approved by the DoD Components/Participating Agencies. Requisition data 

shown in this report is chosen as part of the assignment process for deciding the 

correct priority designator based on the assigned Force Activity Designator (FAD), 

and the validation process for those activities using the FAD I assignment in error. 

The report is in six parts and is generated monthly. Summary sections (Parts I, II, 

IV, and V) are available both monthly:

AP5.2.1.1. Part I – Service/Agency Summary of Requisitions Submitted 

Through DAAS.

AP5.2.1.2. Part II – Department of Defense Activity Address Code 

(DoDAAC) Summary by Service/Agency of Requisitions Submitted Through 

DAAS.

AP5.2.1.3. Part III – Requisition Detail by DoDAAC of Requisitions 

Submitted Through DAAS.

AP5.2.1.4. Part IV – Service/Agency Summary of Requisitions NOT 

Submitted Through DAAS.

AP5.2.1.5. Part V – DoDAAC Summary by Service/Agency of 

Requisitions Not Submitted Through DAAS.
Enclosure 2, ADC 1265

Page 67

AP5.2.1.6. Part VI – Requisition Detail by DoDAAC of Requisitions Not 

Submitted Through DAAS.

AP5.2.2. Military Standard Billing System (MILSBILLS). The MILSBILLS 

process generates the following reports:

AP5.2.2.1. Billing Adjustments by Billing Office.

AP5.2.2.2. Interfund Bills by Billed Office (DoDAAC Sequence).

AP5.2.2.3. Interfund Bills by Billed Office (DoDAAC Within Service).

AP5.2.2.4. Interfund Bills by Billing Office (DoDAAC Within Service).

AP5.2.2.5. Interfund Bills by Billing Office (RIC Sequence).

AP5.2.2.6. Interfund Bills by Route To (COMMRI) Code (COMMRI

Sequence).

AP5.2.2.7. Interfund Bills Rejected by DAAS (RIC Sequence).

AP5.2.2.8. Interfund Bills Retransmission Requests.

AP5.2.2.9. In-storage Visibility Redistribution Credit Report – Lateral 

Redistribution.

AP5.2.2.10. Rejected Interfund Bills By Billed Office (Within Service).

AP5.2.3. Logistics Metrics Analysis Reporting System (LMARS). This report 

consists of two major sections as follows:

AP5.2.3.1 Logistics Response Time (LRT). The LRT section is 

available in eight parts as follows:

AP5.2.3.1.1. Total Pipeline by Requisition.

AP5.2.3.1.2. Total Pipeline Time and Pipeline Segments by Issue 

Priority Group.

AP5.2.3.1.3. Total Pipeline Time and Pipeline Segments by 

Country of Customer.

AP5.2.3.1.4. Total Pipeline Time and Pipeline Segments for 

Stocked Items versus Non-Stocked Items.

AP5.2.3.1.5. Total Pipeline Time and Pipeline Segments for 

Backordered Items.
Enclosure 2, ADC 1265

Page 68

AP5.2.3.1.6. Total Pipeline Time and Pipeline Segments for Direct 

Vendor Delivery (DVD) Items.

AP5.2.3.1.7. Total Pipeline Time and Pipeline Segments for Items 

with Weapon System Applications.

AP5.2.3.1.8. Total Pipeline Time and Pipeline Segments by Major 

Command, Major Claimant, and Major Subordinate Command or Customer.

AP5.2.4. DAAS Processing Volumes. This report captures information about 

transaction volumes as follows:

AP5.2.4.1. Transaction Volumes by Document Identifier Code (DIC). 

This shows the volume of transactions received from or sent to each DoD 

Component/Participating Agency. Volumes are provided by transaction series, 

which reflects transactions routed, passed, and rejected by the DAAS.

AP5.2.4.2. Transaction Volumes by Routing Identifier Code (RIC). This 

shows monthly volumes by RIC. It includes counts of requisitions, passing orders, 

referral orders, issue transactions, total demands, cancellations, AF_ follow-ups, 

AT_ follow-ups, and materiel release orders (A5_) by priorities and customer 

excess materiel.

AP5.2.5. High Action Items. This report supplements the ‘Item Action 

Frequency’ report, above, and shows items requisitioned greater than 100 times in 

one month. It is a monthly report by the DoD Component/Participating Agency, 

and shows the National Stock Number (NSN), quantity requisitioned, and Source 

of Supply (SoS).

AP5.2.6. Communications Pipeline. This report is prepared in three parts. 

Additionally, the report shows the total number of transactions received from and 

transmitted to each activity by precedence as follows:

AP5.2.6.1. Transaction Date Versus Message Header Date. This is 

prepared by the DoD Component/Participating Agency to show the number of 

requisitions by different time lapse frequency; the report is created by comparing 

transaction date to message date.

AP5.2.6.2. Transaction Date Versus DAAS Receipt Date. This part is 

created by comparing requisition date with date received by the DAAS.

AP5.2.6.3. Message Date/Time Versus DAAS Receipt Date/Time. This 

part is created to show the number of requisitions in different time lapse (0-1, 1-4 

hours, etc.) segments.
Enclosure 2, ADC 1265

Page 69

AP5.2.7. DAAS SoS Records. This report is produced in two parts:

AP5.2.7.1. DAAS SoS File Summary. This part contains statistical data 

pertaining to DAAS SoS records. It is prepared by the DoD Component/ 

Participating Agency and is sent to DAAS personnel who serve as members on 

the Supply Process Review Committee (PRC) when requested. 

AP5.2.7.2. DAAS Interim SoS File. This file contains a complete list of 

interim SoS records, and is only distributed upon request.

AP5.2.8. Inter-Service Visibility of Reparables and Lateral Redistribution 

Actions. These reports are produced in three sections to assist in the tracking of 

reparable assets and Defense Logistics Agency (DLA) directed lateral 

redistribution actions:

AP5.2.8.1. The Inter-Service Visibility of Reparables Action Summary 

Report. This section is displayed in the following three parts:

AP5.2.8.1.1. By the DoD Component/Participating Agency, 

managing Inventory Control Point (ICP), reporting RIC, and by priority of the 

number of reparable assets being reported (A4_ transactions), and the extended 

dollar value of the reparable. In addition, the report shows denials (AE_ 

transactions with CB status) and their extended dollar value.

AP5.2.8.1.2. By the DoD Component/Participating Agency, 

managing ICP, reporting DoDAAC, reparable assets being confirmed (AS6), and 

the extended dollar value of the reparable.

AP5.2.8.1.3. By grand total of the DoD Component/Participating 

Agency, the number of reparable assets being reported (A4_ transactions), and 

the extended dollar value of the reparable; the number of confirmations (AS6) and 

the extended dollar value of the confirmations; the number of denials (AE_/CB), 

and the extended dollar value of the denials.

AP5.2.8.2. DLA Asset Visibility Summary Report. This section of the 

report shows, by the DoD Component/Participating Agency and by Issue Priority 

Group, the number of referrals (A4_), confirmations (A6_), and denials (AE6/CB) 

that are in Report 1. It provides sub-totals by the DoD Component/Participating 

Agency and a grand total for the report.

AP5.2.8.3. DLA Retail Asset Visibility Credit Confirmation Report. This 

section measures the overall effectiveness of allowing DLA to fill backorders from 

retail assets, both above and below the reorder level by:

AP5.2.8.3.1. Matching the DoD Component/Participating Agency 

confirmations (AS6) to the billing transactions (FD2, FN2, and FQ2) by DoDAAC 

and providing a count for those that match and for those that do not match. After 
Enclosure 2, ADC 1265

Page 70

60 calendar days, confirmations that do not have a matching bill transaction are 

dropped. Statistics by DoDAAC are shown for dropped transactions.

AP5.2.8.3.2. A summary report by the DoD Component/ 

Participating Agency for the Credit Confirmation Report.

AP5.2.9. DLA Credit for Retail Asset Redistribution. This report measures 

directed returns and lateral redistribution for backorders filled from retail assets. 

The report shows the number of line items and dollar value for directed returns 

and lateral redistribution actions.

AP5.2.10. MRA Reports 

AP5.2.10.1. MRA reports show shipments and the percentage of 

shipments for which the DAAS receives and does not receive the associated MRA 

transactions. Qualifying Shipments included in the report are determined by the 

date released to carrier (recorded at DAAS) plus 25 calendar days to 

accommodate the 17 calendar days MRA reporting period and the 10 calendar 

days MRA follow-up response timeframes (if CONUS); or plus 43 calendar days to 

accommodate the 34 calendar days MRA reporting period and the 10 calendar 

days MRA follow-up response timeframe (if OCONUS – Transportation Category 1 

or 2); or plus 90 calendar days to accommodate the 81 calendar days MRA 

reporting period and the 10 calendar days MRA follow-up response timeframe (if 

OCONUS – Transportation Category 3).6 Security assistance program 

requisitions are not captured for inclusion in LMARS or MRA Reports based on the 

Security Cooperation Implementing Agency code in the first position of the 

document number.

AP5.2.10.2. To access these reports, a DAAS system access request 

(SAR) for SAR Title “Logistics Reports” must be completed at 

https://www.transactionservices.dla.mil/sar/sar_menu.asp.

AP5.2.10.3. Wholesale ICPs included in the MRA Report are identified 

in the LMARS and maintained by DAAS. The list of included wholesale ICPs (see 

Table D) is available at LMARS Output Report Specific Tables. New ICPs will be 

added as they are identified by the Supply PRC.

AP5.2.10.4. The MRA report is created at the end of each month to 

reflect the MRA transactions as received/not received in the preceding month. 

Receipt of an MRA citing Discrepancy Code B or F updates the Logistics 

Metrics Analysis Reporting System (LMARS) reports to reflect the current 

status of MRA transactions received. The MRA Reports are created monthly 

and reflect the MRA data at the end of the month and will not be adjusted 

 6 Per DLM 4000.25-2, Chapter 6, the reporting period is defined as 17 calendar days for Conus; and 34 calendar 

days for OCONUS Transportation Category 1 and 2 shipments; and 81 calendar days for OCONUS 

Transportation Category 3 shipments. The follow-up response timeframe for both is 10 days. Refer to ADC 

1114
Enclosure 2, ADC 1265

Page 71

retroactively when an MRA is submitted following receipt of materiel after an 

MRA citing Discrepancy Indicator Code B or F is received.7

AP5.2.10.5. Allotted Timeframe. The report uses shipment date 

released to carrier plus 60 calendar days if CONUS; or shipment date released to 

carrier plus 120 calendar days if OCONUS.

AP5.2.10.6. Categories. Categories contained in the report are:

AP5.2.10.6.1. Ammunition - FSG 13.

AP5.2.10.6.2. Contractor - Service Code C, E, L, Q, U, HG, SD, or Z0.

AP5.2.10.6.3. Army Total Package Fielding (TPF) - DoDAAC table.

AP5.2.10.6.4. General - Excludes above categories.

AP5.2.10.7. Exclusions.

8 Categories excluded are:

AP5.2.10.7.1. Shipments of fresh fruit and vegetables (FF&V). 

FF&V transactions are received by DAAS in a monthly data feed from DLA Troop 

Support and do not have shipment data.

AP5.2.10.7.2. Commodities excluded from requisitioning under 

MILSTRIP, except that receipt of forms and publications requisitioned under 

MILSTRIP will be acknowledged.

AP5.2.10.7.3. Shipments to foreign military sales and grant aid 

customers except when the shipment concerns an unconfirmed materiel release 

order (MRO) as described in MILSTRIP, Chapter 3 (Processing Follow-Ups). FMS 

documents beginning with B, D, I, P, K, and T.

AP5.2.10.7.4. DoDAAC indicating activity is GSA or FEDSTRIP.

AP5.2.10.7.5. DoDAAC beginning with HX.

AP5.2.10.7.6. Shipment status (AS3) with Distribution Code 9 

(DLA Distribution Services). Shipments to disposition services that are covered 

 7 Refer to ADC 1114. 8 (ADC 1088) Known MRA gaps include shipments associated with DLA Industrial Prime Vendor (IPV), and DLA 

Tailored Vendor Relationships (TVR) such as Medical Prime Vendor; Subsistence Prime Vendor; Maintenance 

Repair and Operations program; and Kentucky Logistics Operation Center (KYLOC). The MRA process 

requires a Shipment Status transaction; there is no shipment status in these processes. These processes are not 

excluded from MRA (except Fresh fruits and vegetables (FF&V)), and are identified as known process gaps that 

DLA is working to close. Another possible MRA gap exists for immediate issue scenarios (e.g., bearer walkthrough or “over the counter” issues) where shipment status /materiel release confirmation is provided and an 

MRA would typically be expected. DLA will submit a proposed DLMS changes to document this as an MRA 

exclusion.
Enclosure 2, ADC 1265

Page 72

under the MILSTRIP procedures for intransit control of shipments to DLA 

Disposition Services Field Offices.

AP5.2.10.7.7. Inter-Component lateral redistributions of retail stock 

not directed by the integrated materiel manager.

9

AP5.2.10.7.8. Shipments to state, civil, or Federal Agency 

activities. Special Program DoDAAC. Special Program DoDAACs are identified 

by numeric character in the first position followed by an alpha character in the 

second position. These identify entities that are neither DoD or other Federal 

entities and that are associated with a special program. Among other purposes, 

special programs include programs authorized by Congress for state and local 

entities to purchase materiel from Federal sources. The existing DAAS logic for 

extracting the LMARS database includes the exclusion for Special Program 

DoDAACs.

AP5.2.10.7.9. Exclude intra-Component shipments when the issuing 

wholesale ICP does not generate a Follow-Up for Delinquent MRA transaction within 

the required delinquent MRA Follow-up time limit. The rationale is that if the issuing 

wholesale ICP business process requires that the intra-Component reporting activity 

provide a Receipt transaction back to the issuing wholesale ICP, then it falls under the 

MRA exclusions and the issuing ICP would not generate a Follow-up for Delinquent 

MRA transaction. For the purpose of this exclusion logic, DAAS will use the MRA 

Follow-up timeframe plus one day. Under existing MRA Report logic, lookup will be 

done at the end of the month.

10

AP5.2.10.7.10. Receipts into DoD wholesale stock which are controlled 

under Chapter 4, including relocations/shipments to contractors, commercial, or 

industrial activities which are receipt reported to the owning ICP, when the owning ICP 

also issued the materiel. However, when ICPs requisition materiel from another ICP or 

the DLA Disposition Services and the receipt is reported under Chapter 4, the 

requisitioning ICP will acknowledge the receipt (ADC 1087).

 9

( ADC 1088) This is not a true “exclusion” from MRA because the MRA is only required for release of 

wholesale assets. When DAAS gets the passing order that has a RIC-TO of a non-wholesale ICP, they 

will flag the document number as not eligible for LMARS/MRA, but still be available for WEBVLIPS as 

history. Any subsequent transactions that come in under that document number (regardless of data 

content and indication of a wholesale ICP) automatically gets that flag. This is similar to what DAAS does 

for the requisition alert process. The one underlying assumption to this solution is that the passing order 

(DIC A3_) will be present so that the flag can be set at the document number level. This is a safe 

assumption, since ADC 1062 states that GCSS-A will not release the requisition image until they receive 

the passing order routed by DAAS. Note the DAAS check on the shipment status is just the presence of 

a shipment status for the document number that clears the first part of the MRA decision Tree. DAAS

feels this will eliminate a concern with LMARS picking up the transaction as a byproduct when the bill 

comes out of the wholesale ICP system (LMP) after the post-post issue is passed to that system (For 

Army GCSS-A to LMP). 10 ADC 1087. DAAS implementation for Air Force, Marine Corps, and DLA is projected for July 1, 2015; delayed 

implementation authorized for Army and Navy ICPs.
Enclosure 2, ADC 1265

Page 73

AP5.2.10.8. MRA Report Criteria. The criteria used to produce and 

align the MRA Reports are depicted/contained in the LMARS Reports’ Table H 

Service and/or Report Affiliation, as shown at LMARS Output Report Specific 

Tables.

AP5.2.10.9. Reports. Appendix 7 identifies the detailed business rules 

for generating the MRA Report. Appendix 7 also includes an MRA Decision Tree 

diagram to provide graphic representation of the MRA business rules to capture 

shipments out of wholesale assets that qualify for MRA reporting. Actual MRA 

reports produced are as follows:

AP5.2.10.9.1. MRA01 – MRA Service and Agency Summary. 

Shows shipments for all DoD Components/Participating Agencies and all 

categories by area of the ship-to DoDAAC and customer. The count of qualified 

shipments is matched against MRAs received/MRA not received, the percentage 

is computed and shown for MRAs received and MRAs not received:

Column 1 – Area Area of the ship-to DoDAAC

Column 2 – Customer DoD Component/Agency of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe 

Column 4 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified shipments in the allotted timeframe

Column 5 – MRA Not 

Received, Count

Count of qualified shipments for which no MRA was received in the 

allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)11

Column 6 – MRA Not 

Received, Value

Extended dollar value of the qualified shipments that did not receive 

an MRA in the allotted timeframe 

Column 7 – MRA Not 

Received, Percent

Percentage of the qualified shipments that did not receive an MRA in 

the allotted timeframe (column 5 divided by column 3) 

Column 8 – MRA RCVD, 

Count

Count of MRAs received in the given reporting period that matched a 

qualified shipment

Column 9 – MRA RCVD, 

Value

Extended dollar value of the qualified shipments that received an 

MRA in the given reporting period

Column 10 – MRA RCVD 

Percent

Percentage of the qualified shipments that receive an MRA in the 

given reporting period (column 8 divided by column 3)

AP5.2.10.9.2. MRA01d – MRA Service and Agency Detail. Shows 

shipments for all DoD Components/Participating Agencies and all categories by 

ship-to DoDAAC. The count of qualified shipments is matched against MRAs 

received/MRAs not received, the percentage is computed and shown for MRAs 

received and MRAs not received.

 11 Refer to ADC 1114. 25 calendar days CONUS, 43 calendar days OCONUS Transportation Category 1 or 2, or 

90 calendar days OCONUS Transportation Category 3.
Enclosure 2, ADC 1265

Page 74

Column 1 – Customer Ship-to DoDAAC 

Column 2 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe

Column 3 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified shipments in the allotted timeframe

Column 4 – MRA Not 

RCVD, Count

Count of qualified shipments for which no MRA was received in the 

allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)12

Column 5 – MRA Not 

RCVD, Value

Extended dollar value the qualified shipments that did not receive an 

MRA in the allotted timeframe

Column 6 – MRA Not 

RCVD, Percent

Percent of the qualified shipments that did not received an MRA in 

the allotted timeframe (column 4 divided by column 2)

Column 7 – MRA RCVD, 

Count

Count of MRAs received in the given reporting period that matched a 

qualified shipment

Column 8 – MRA RCVD, 

Value

Extended dollar value of the qualified shipments that received an 

MRA in the given reporting period

Column 9 – MRA RCVD, 

Percent

Percentage of the qualified shipments that received an MRA in the 

given reporting period (column 7 divided by column 2)

Clicking on a ship-to DoDAAC link provides the list of qualified requisitions (with WebVLIPS link) 

that require an MRA

AP5.2.10.9.3. MRA02 – Direct Vendor Delivery (DVD) MRA 

Summary. Shows DVD shipments for all DoD Components/Participating Agencies 

and all categories by area of the ship-to DoDAAC and customer. The count of 

qualified shipments is matched against MRA received/MRA not received, the 

percentage is computed and shown for MRAs received and MRAs not received. 

Direct Vendor Delivery (DVD) is identified one of two ways:

• DLMS 870S Supply Status beginning segment (1/BSR01/20 Code 5). 

This transaction provides the functionality of MILSTRIP legacy DIC AB1, 

AB2, AB3, and AB8.

• DLMS 870S Supply Status beginning segment (1/BSR01/20 Code 4 and 

logistics qualifier (2/LQ01/330 Code 81) citing Status Code BV or BZ. 

This transaction provides the functionality of MILSTRIP legacy DIC AE1, 

AE2, AE3, AE8, AE9, AEA, AEB, AED, and AEE

 12 Ibid.
Enclosure 2, ADC 1265

Page 75

Column 1 – Area Area of the ship-To DoDAAC 

Column 2 – Customer DoD Component/Agency of the ship-to DoDAAC

Column 3 – DVD Shipments 

Requiring MRA, Count

Count of qualified shipments that were filled via DVD in the allotted 

timeframe (See the DVD definition above).

Column 4 – DVD Shipments 

Requiring MRA, Value

Extended dollar value of all qualified DVD shipments in the allotted 

timeframe

Column 5 – MRA Not 

Received, Count

Count of qualified shipments for which no MRA was received in the 

allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)13

Column 6 – MRA Not 

Received, Percent

Percentage of the qualified shipments that did not receive an MRA 

in the allotted timeframe (column 5 divided by column 3)

Column 7 – MRA Not 

Received, Value

Extended dollar value of the qualified shipments that did not receive 

an MRA in the allotted timeframe 

Column 8 – MRA Not 

Received, Percent of Value

Percentage (by value) of the qualified shipments that did not receive 

an MRA in the allotted timeframe (column 7 divided by column 4)

AP5.2.10.9.4. MRA02d – DVD MRA Detail. Shows DVD shipments for 

all DoD Components/ Participating Agencies and all categories by ship-to DoDAAC and 

customer that do not show an MRA during the allotted timeframe. The count of qualified 

shipments is matched against MRAs received/MRAs not received and for MRAs not 

received, the percentage of the count and value is computed and shown. The detail 

report contains a listing of DoDAACs within the MRA02 Area and customer with a list of 

the individual requisitions that did not receive an MRA.

Column 1 – Ship-To 

DoDAAC 

Ship-to DoDAAC

Column 2 – DVD Shipments 

Requiring MRA, Count

Count of qualified shipments that were filled via DVD in the allotted 

timeframe (See AP5.2.12.5.3 for DVD Definition).

Column 3 – DVD Shipments 

Requiring MRA, Value

Extended dollar value of qualified DVD shipments

Column 4 – MRA Not 

Received, Count

Count of qualified shipments for which no MRA was received in the 

allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)14

Column 5 – MRA Not 

Received, Percent of Count

Percentage (by count) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 4 divided by 

column 2)

Column 6 – MRA Not 

Received, Value

Extended dollar value of the qualified shipments that did not receive 

an MRA in the allotted timeframe

Column 7 – MRA Not 

Received, Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 6 divided by 

column 3)

 13 Ibid. 14 Ibid.
Enclosure 2, ADC 1265

Page 76

Clicking on the ship-to DoDAAC link provides a list of qualified requisitions (with WebVLIPS link) 

that did not receive an MRA in the allotted timeframe.

ADC 1088 changed column reference from alphabetic to numeric.

AP5.2.10.9.5. MRA36 – Stock Shipment. Shows stock shipments from 

wholesale inventory for all DoD Components/Participating Agencies and all categories 

by area of the ship-to DoDAAC and customer. The count of qualified shipments is 

matched against MRAs received/MRAs not received and for MRAs not received, the 

percentage of the count and value is computed and shown. 

Column 1 – Area Area of the ship-to DoDAAC 

Column 2 – Customer DoD Component/Agency of the ship-to DoDAAC

Column 3 – DVD Shipments 

Requiring MRA, Count

Count of qualified stock shipments from wholesale inventory that 

were filled the allotted timeframe

Column 4 – DVD Shipments 

Requiring MRA, Value

Extended dollar value of all qualified shipments in the allotted 

timeframe

Column 5 – MRA Not Received, 

Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)15

Column 6 – MRA Not Received, 

Percent

Percentage of the qualified shipments that did not receive an 

MRA in the allotted timeframe (column 5 divided by column 3)

Column 7 – MRA Not Received, 

Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 7 divided by 

column 4)

Column 8 – MRA Not Received, 

Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe

AP5.2.10.9.6. MRA36d – Stock Shipment Detail. Shows stock 

shipments from wholesale inventory for all DoD Components/Participating 

Agencies and all categories by ship-to DoDAAC. The count of qualified shipments 

is matched against MRAs received/MRAs not received and for MRAs not received, 

the percentage of the count and value is shown. The detail report contains a listing 

of DoDAACs within the MRA36 area and customer with a list of the requisitions 

that did not receive an MRA. 

Column 1 – Ship-To DoDAAC Ship-to DoDAAC

Column 2 – DVD Shipments 

Requiring MRA, Count

Count of qualified stock shipments from wholesale inventory 

that were filled in the allotted timeframe 

Column 3 – DVD Shipments 

Requiring MRA, Value

Extended dollar value of qualified shipments

 15 Ibid.
Enclosure 2, ADC 1265

Page 77

Column 4 – MRA Not Received, 

Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment

to accommodate the MRA reporting period plus the MRA 

follow-up response timeframe)16

Column 5 – MRA Not Received, 

Percent of Count

Percentage (by count) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 4 divided by 

column 2)

Column 6 – MRA Not Received, 

Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe

Column 7 – MRA Not Received, 

Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 6 divided by 

column 3)

Clicking the ship-to DoDAAC link provides a list of qualified requisitions (with WebVLIPS link) that 

did not receive an MRA in the allotted timeframe

AP5.2.10.9.7. MRA37 – DVD and Stock Summary. Shows DVD and 

stock shipments from wholesale inventory for all DoD Components/Participating 

Agencies and all categories by area of the ship-to DoDAAC and customer. MRA37 

combines MRA02 (DVD) and MRA36 (Stock Shipment) Summary Reports.17 The 

count of qualified shipments is matched against MRAs received/MRAs not received, 

and for MRAs not received, the percentage of the count and value is computed and 

shown.

Column 1 – Area Area of the ship-to DoDAAC 

Column 2 – Customer DoD Component/Agency of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified DVD and stock shipments from wholesale 

inventory that were filled in the allotted timeframe

Column 4 – Shipments 

Requiring MRA, Value

Extended dollar value of all qualified shipments in the allotted 

timeframe

Column 5 – MRA Not Received, 

Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)18

Column 6 – MRA Not Received, 

Percent

Percentage of the qualified shipments that did not receive an 

MRA in the allotted timeframe (column 5 divided by column 3)

Column 7 – MRA Not Received, 

Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe 

Column 8 – MRA Not Received, 

Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 7 divided by 

column 4)

AP5.2.10.9.8. MRA37d – DVD and Stock Detail. Shows DVD and 

stock shipments from wholesale inventory for all DoD Components/ Participating 

 16 Ibid. 17 The values in this report mirror those found in MRA01 with the only difference being the columns displayed. 18 Refer to ADC 1114. 25 calendar days CONUS, 43 calendar days OCONUS Transportation Category 1 or 2, or 

90 calendar days OCONUS Transportation Category 3.
Enclosure 2, ADC 1265

Page 78

Agencies and all categories by ship-to DoDAAC. The count of qualified shipments 

is matched against MRAs received/MRAs not received, and for MRAs not 

received, the percentage of the count and value is computed and shown. The 

detail report contains a listing of DoDAACs within the MRA37 Area and customer 

with a list of the requisitions that did not receive an MRA.

Column 1 – Ship-To DoDAAC Ship-to DoDAAC

Column 2 – Shipments 

Requiring MRA, Count

Count of qualified DVD and stock shipments from wholesale 

inventory that were filled in the allotted timeframe 

Column 3 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified shipments

Column 4 – MRA Not Received, 

Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)19

Column 5 – MRA Not Received, 

Percent of Count

Percentage (by count) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 4 divided by 

column 2)

Column 6 – MRA Not Received, 

Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe

Column 7 – MRA Not Received, 

Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 6 divided by 

column 3)

Clicking on the ship-to DoDAAC link provides a list of qualified requisitions (with WebVLIPS link) 

that did not receive an MRA in the allotted timeframe

AP5.2.10.9.9. MRA32s – Percent of Delinquents (Ammunition) 

Summary. Shows ammunition shipments for all DoD Components/ Participating 

Agencies and all categories by area of the ship-to DoDAAC and customer. The 

count of qualified shipments is matched against MRAs received/MRAs not 

received, the percentage is computed and shown for MRAs received:

Column 1 – Area Area of the Ship-to DoDAAC

Column 2 – Customer DoD Component/Agency of the Ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe

Column 4 – MRA Received 

Count

Count of MRAs received in the given reporting period that 

matched a qualified shipment

Column 5 – MRA Received 

Percentage

Percentage of qualified shipments that received an MRA (column 

4 divided by column 3)

Column 6 – MRA Not 

Received Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 20calendar days of shipment

to accommodate the MRA reporting period plus the MRA followup response timeframe)

 19 Ibid 20 Ibid.
Enclosure 2, ADC 1265

Page 79

AP5.2.10.9.10. MRA32d Percent of Delinquents (Ammunition)

Detail. Shows ammunition shipments for all DoD Components/Participating 

Agencies and all categories by ship-to DoDAAC. The count of qualified shipments 

is matched against MRAs received/MRAs not received, the percentage is 

computed and shown for MRAs received. The detail report contains a listing of 

DoDAACs within the MRA32 Area and customer with a list of the qualified 

requisitions that require an MRA:

Column 1 – Ship-To DoDAAC Ship-to DoDAAC

Column 2 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe 

Column 3 – MRA Received, 

Count

Count of MRAs received in the given reporting period that 

matched a qualified shipment 

Column 4 – MRA Received, 

Percentage

Percentage of qualified shipments that received an MRA 

(column 3 divided by column 2)

Column 5 – No MRA, Count Count of qualified shipments for which no MRA was received 

in the allotted timeframe (within 25/90 calendar days of 

shipment to accommodate the MRA reporting period plus the 

MRA follow-up response timeframe) 21

Clicking on a ship-to DoDAAC link provides the list of qualified requisitions (with WebVLIPS link) 

that require an MRA

AP5.2.10.9.11. MRA33s Percent of Delinquents (Contractor) –

Summary. Shows contractor shipments for all DoD Components/ Participating 

Agencies and all categories by area of the ship-to DoDAAC. The count of 

qualified shipments is matched against MRAs received/MRAs not received, the 

percentage is computed and shown for MRAs received:

Column 1 – Area Area of the ship-to DoDAAC

Column 2 – Customer DoD Component/Agency of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe

Column 4 – MRA Received, 

Count

Count of MRAs received in the given reporting period that 

matched a qualified shipment

Column 5 – MRA Received, 

Percentage

Percentage of qualified shipments that received an MRA 

(column 4 divided by column 3)

Column 6 – No MRA Received, 

Count

Count of qualified shipments for which no MRA was received 

in the allotted timeframe (within 25/90 calendar days of 

shipment to accommodate the MRA reporting period plus the 

MRA follow-up response timeframe)22

AP5.2.10.9.12. MRA33d Percent of Delinquents (Contractor) –

Detail. Shows contractor shipments for all DoD Components/Participating 

 21 Ibid. 22 Ibid.
Enclosure 2, ADC 1265

Page 80

Agencies and all categories by ship-to DoDAAC. The count of qualified shipments 

is matched against MRAs received/MRAs not received, the percentage is 

computed and shown for MRAs received. The detail report contains a listing of 

DoDAACs within the MRA33 Area and customer with a list of the qualified 

requisitions that require an MRA:

Column 1 – Ship-To DoDAAC Ship-to DoDAAC 

Column 2 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe 

Column 3 – MRA Received, 

Count

Count of MRAs received in the given reporting period that 

matched a qualified shipment 

Column 4 – MRA Received, 

Percentage

Column 5 is the percentage of qualified shipments that 

received an MRA (column 3 divided by column 2) 

Column 5 – No MRA, Count Count of qualified shipments for which no MRA was received 

in the allotted timeframe (within 25/90 calendar days of 

shipment to accommodate the MRA reporting period plus the 

MRA follow-up response timeframe)23

Clicking on a ship-to DoDAAC link provides the list of qualified requisitions (with WebVLIPS 

link) that require an MRA

AP5.2.10.9.13. MRA34s – Percent of Delinquents (Army Total 

Package Fielding (TPF)) Summary. Shows Army TPF shipments for all DoD 

Components/Participating Agencies and all categories by area of the ship-to 

DoDAAC. The count of qualified shipments is matched against MRAs received/ 

MRAs not received, the percentage is computed and shown for MRAs received:

Column 1 – Area Area of the ship-to DoDAAC

Column 2 – Customer DoD Component/Agency of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe

Column 4 – MRA Received, 

Count

Count of MRAs received in the given reporting period that 

matched a qualified shipment

Column 5 – MRA Received, 

Percentage

Percentage of qualified shipments that received an MRA (column 

4 divided by column 3)

Column 6 – No MRA 

Received, Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)24

AP5.2.10.9.14. MRA34d – Percent of Delinquents (Army TPF) 

Detail. Shows Army TPF shipments for all DoD Components/Participating 

Agencies and all categories by ship-to DoDAAC. The count of qualified shipments 

is matched against MRAs received/MRAs not received, and a percentage for 

 23 Ibid 24 Ibid
Enclosure 2, ADC 1265

Page 81

MRAs received is shown. The detail report contains a listing of DoDAACs within 

the MRA34 Area and customer with a list of the individual requisitions:

Column 1 – Ship-To DoDAAC Ship-to DoDAAC 

Column 2 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe 

Column 3 – MRA Received, 

Count

Count of MRAs received in the given reporting period that 

matched a qualified shipment 

Column 4 – MRA Received, 

Percentage

Percentage of qualified shipments that received an MRA (column 

3 divided by column 2) 

Column 5 – No MRA, Count Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)25

Clicking on a “ship-to DoDAAC” link provides the list of qualified requisitions (with WebVLIPS link) 

that require an MRA

AP5.2.10.9.15. MRA35s – Percent of Delinquents (General) 

Summary. Shows General shipments for all DoD components/Participating 

Agencies and all categories (except for Ammunition, Contractor, and Army TPF) 

by area of the ship-to DoDAAC. The count of qualified shipments is matched 

against MRAs received/MRAs not received, the percentage is computed and 

shown for MRAs received:

Column 1 – Area Area of the ship-to DoDAAC

Column 2 – Customer DoD Component/Agency of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe

Column 4 – No MRA 

Received, Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)26

Column 5 – MRA Received, 

Count

Count of MRAs received in the given reporting period that 

matched a qualified shipment

Column 6 – MRA Received, 

Percentage

Percentage of qualified shipments that received an MRA (column 

4 divided by column 3)

AP5.2.10.4.16. MRA35d – Percent of Delinquents (General) Detail. 

Shows general shipments by for all DoD components/Participating Agencies and all 

categories (except for Ammunition, Contractor and Army TPF) by ship-to DoDAAC. The 

count of qualified shipments is matched against MRAs received/not received and a 

percentage for MRAs received is shown. The detail report contains a listing of 

 25 Ibid. 26 Ibid.
Enclosure 2, ADC 1265

Page 82

DoDAACs within the MRA35 Area and customer with a list of the qualified requisitions 

that require an MRA:

Column 1 – Ship-To DoDAAC Ship-to DoDAAC 

Column 2 – Shipments 

Requiring MRA, Count

Count of qualified shipments in the allotted timeframe 

Column 3 – MRA Received, 

Count

Count of MRAs received in the given reporting period that matched 

a qualified shipment 

Column 4 – MRA Received, 

Percentage

Percentage of qualified shipments that received an MRA (column 3 

divided by column 2) 

Column 5 – No MRA, Count Count of qualified shipments for which no MRA was received in the 

allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)27

Clicking on a ship-to DoDAAC link provides the list of qualified requisitions (with WebVLIPS link) 

that require an MRA

AP5.2.10.9.17. MRA38 – Source of Supply MRA Stock Summary. 

Shows stock shipments from wholesale inventory for all DoD 

Components/Participating Agencies and all categories by the wholesale ICP 

(Source of Supply) directing the shipment, and by receiving Component. The 

count of qualified shipments is matched against MRA received/MRA not received, 

and for MRAs not received, the percentage of the count and value is computed 

and shown:

Column 1 – Source of Supply Identifies the DoD Component of the “RIC To” for qualifying 

requisitions and the “RIC From” for qualifying materiel release 

order transactions

Column 2 – Receiving 

Component

DoD Component of the ship-to DoDAAC

Column 3 – Shipments Requiring 

MRA, Count

Count of qualified stock shipments from wholesale inventory 

that were filled in the allotted timeframe

Column 4 – Shipments Requiring 

MRA, Value

Extended dollar value of all qualified shipments in the allotted 

timeframe

Column 5 – MRA Not Received, 

Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment 

to accommodate the MRA reporting period plus the MRA followup response timeframe)28

Column 6 – MRA Not Received, 

Percent of Count

Percentage (by count) of the qualified shipments for which no 

MRA was received in the allotted timeframe (column 5 divided 

by column 3)

Column 7 – MRA Not Received, 

Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe

 27 Ibid. 28 Ibid.
Enclosure 2, ADC 1265

Page 83

Column 8 – MRA Not Received, 

Percent of Value

Percentage (by value) of the dollar value for qualified shipments 

that did not receive an MRA in the allotted timeframe (column 7 

divided by column 4)

AP5.2.10.9.17.1. MRA38d – Source of Supply MRA Stock 

Detail. Shows stock shipments from wholesale inventory for all DoD 

Components/Participating Agencies and all categories by the wholesale ICP 

directing the shipment, and by receiving Component. The count of qualified 

shipments is matched against MRAs received/MRAs not received, and for MRAs 

not received, the percentage of the count and value is computed and shown:

Column 1 – Source of Supply RIC for the DoD Component selected in the Summary Report for 

qualifying requisitions and the “RIC From” for qualifying materiel 

release order transactions

Column 2 – Receiving 

Component

DoD Component of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified shipments from wholesale inventory that were 

filled in the allotted timeframe

Column 4 – Shipments 

Requiring MRA, Value

Extended dollar value of all qualified shipments in the allotted 

timeframe

Column 5 – MRA Not 

Received, Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)29

Column 6 – MRA Not 

Received, Percent of Count

Percentage (by count) of the qualified shipments for which no 

MRA was received in the allotted timeframe (column 5 divided by 

column 3)

Column 7 – MRA Not 

Received, Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe

Column 8 – MRA Not 

Received, Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 7 divided by 

column 4)

AP5.2.10.9.17.2. MRA38dd – Source of Supply DoDAAC 

MRA Stock Detail. Selecting a source of supply in the previous MRA 38d, Source 

of Supply DoDAAC MRA Stock Detail Report will show stock shipments for ship-to 

DoDAACs with qualifying shipments. The count of qualified shipments is matched 

against MRAs received/MRAs not received, and for MRAs not received, the 

percentage of the count and value is computed and shown:

Column 1 – Ship-To DoDAAC Ship-to DoDAACs for the wholesale ICP RIC selected from the 

Detail Report

Column 2 – Shipments 

Requiring MRA, Count

Count of qualified stock shipments from wholesale inventory that 

were filled in the allotted timeframe

Column 3 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified shipments in the allotted 

timeframe

 29 Ibid.
Enclosure 2, ADC 1265

Page 84

Column 4 – MRA Not 

Received, Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)30

Column 5 – MRA Not 

Received, Percent of Count

Percentage (by count) of the qualified shipments for which no 

MRA was received in the allotted timeframe (column 4 divided by 

column 2)

Column 6 – MRA Not 

Received, Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe.

Column 7 – MRA Not 

Received, Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 6 divided by 

column 3)

AP5.2.10.9.18. MRA39 – Source of Supply MRA DVD Summary. 

Shows DVD31 shipments from wholesale inventory for all DoD 

Components/Participating Agencies and all categories by the wholesale ICP 

(Source of Supply) directing the shipment, and by receiving Component. The 

count of qualified shipments is matched against MRAs received/MRAs not 

received, and for MRAs not received, the percentage of the count and value is 

computed and shown:

Column 1 – Source of Supply Identifies the DoD Component of the “RIC To” for qualifying 

requisitions and the “RIC From” for qualifying materiel release order 

transactions

Column 2 – Receiving 

Component

DoD Component of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified shipments that were filled via DVD in the allotted 

timeframe

Column 4 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified DVD shipments in the allotted 

timeframe

Column 5 – MRA Not 

Received, Count

Count of qualified shipments for which no MRA was received in the 

allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)32

Column 6 – MRA Not 

Received, Percent of Count

Percentage of the qualified shipments that did not receive an MRA 

in the allotted timeframe (column 5 divided by column 3)

Column 7 – MRA Not 

Received, Value

Extended dollar value of the qualified shipments that did not receive 

an MRA in the allotted timeframe

 30 Ibid. 31 DVD is identified by the DLMS 870S (Supply Status), (1/BSR01/20), Status Report Code 5 (Notice of Response 

to Direct Vendor Delivery)/MILSTRIP legacy Document Identifier Code (DIC) AB_ Direct Delivery Notice; or 

Status Report Code 4, (Response to Requisition (Supply Status))/MILSTRIP legacy DIC AE_ Supply Status, 

with Supply Status Code:

BV – Requisition or requisition alert item procured and on contract for direct shipment to consignee, or

BZ – Requisition or requisition alert is being processed for direct delivery procurement. 32 Refer to ADC 1114. 25 calendar days CONUS, 43 calendar days OCONUS Transportation Category 1 or 2, or 

90 calendar days OCONUS Transportation Category 3.
Enclosure 2, ADC 1265

Page 85

Column 8 – MRA Not 

Received, Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 7 divided by 

column 4)

AP5.2.10.9.18.1. MRA39d – Source of Supply MRA DVD 

Detail. Shows DVD shipments from wholesale inventory for all DoD 

Components/Participating Agencies and all categories by the wholesale ICP 

directing the shipment, and by receiving Component. The count of qualified DVD 

shipments is matched against MRAs received/MRAs not received, and for MRAs 

not received, the percentage of the count and value is computed and shown:

Column 1 – Source of Supply RIC for the DoD Component selected in the Summary Report for 

qualifying requisitions and the “RIC From” for qualifying materiel 

release order transactions

Column 2 – Receiving 

Component

DoD Component of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified shipments that were filled via DVD in the allotted 

timeframe

Column 4 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified DVD shipments in the allotted 

timeframe

Column 5 – MRA Not 

Received, Count

Count of qualified shipments for which no MRA was received in 

the allotted timeframe (within 25/90 calendar days of shipment to 

accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)33

Column 6 – MRA Not 

Received, Percent of Count

Percentage (by count) of the qualified shipments for which no 

MRA was received in the allotted timeframe (column 5 divided by 

column 3)

Column 7 – MRA Not 

Received, Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe

Column 8 – MRA Not 

Received, Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 7 divided by 

column 4)

AP5.2.10.9.18.2. MRA39dd – Source of Supply DoDAAC 

MRA DVD Detail. Selecting a source of supply in the previous MRA39d, Source of 

Supply DVD Detail Report will show DVD shipments for ship-to DoDAACs with 

qualifying shipments. The count of qualified shipments is matched against MRAs 

received/MRAs not received, and for MRAs not received, the percentage of the 

count and value is computed and shown:

Column 1 – Ship to DoDAAC Ship-to DoDAACs for the wholesale ICP RIC selected from the 

Detail Report

Column 2 – Shipments 

Requiring MRA, Count

Count of qualified shipments that were filled via DVD in the allotted 

timeframe

Column 3 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified DVD shipments in the allotted 

timeframe

 33 Ibid.
Enclosure 2, ADC 1265

Page 86

Column 4 – MRA Not 

Received, Count

Count of qualified DVD shipments for which no MRA was received 

in the allotted timeframe (within 25/90 calendar days of shipment 

to accommodate the MRA reporting period plus the MRA follow-up 

response timeframe)34

Column 5 – MRA Not 

Received, Percent of Count

Percentage (by count) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 4 divided by 

column 2)

Column 6 – MRA Not 

Received, Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe

Column 7 – MRA Not 

Received, Percent of Value

Percentage (by value) of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 6 divided by 

column 3)

AP5.2.10.9.19. MRA40 – Source of Supply Stock and DVD Summary. 

Shows Stock and DVD shipments from wholesale inventory for all DoD Components/ 

Participating Agencies and all categories by the wholesale ICP (Source of Supply) 

directing the shipment, and by receiving Component. MRA40 combines MRA38 (Stock 

Shipment) and MRA39 (DVD Shipment) Summary Reports. The count of qualified 

shipments is matched against MRAs received/MRAs not received, and for MRAs not 

received, the percentage of the count and value is computed and shown: 

Column 1 – Source of Supply Identifies the DoD Component of the “RIC To” for qualifying 

requisitions and the “RIC From” for qualifying materiel release order 

transactions

Column 2 – Receiving 

Component

DoD Component of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified Stock and DVD shipments from wholesale 

inventory that were filled in the allotted timeframe

Column 4 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified Stock and DVD shipments in the 

allotted timeframe

Column 5 – MRA Not 

Received, Count

Count of qualified Stock and DVD shipments for which no MRA was 

received in the allotted timeframe (within 25/90 calendar days of 

shipment to accommodate the MRA reporting period plus the MRA 

follow-up response timeframe)35

Column 6 – MRA Not 

Received, Percent of Count

Percentage (by count) of the qualified Stock and DVD shipments 

that did not receive an MRA in the allotted timeframe (column 5 

divided by column 3)

Column 7 – MRA Not 

Received, Value

Extended dollar value of the qualified Stock and DVD shipments 

that did not receive an MRA in the allotted timeframe

Column 8 – MRA Not 

Received, Percent of Value

Percentage (by value) of the qualified Stock and DVD shipments 

that did not receive an MRA in the allotted timeframe (column 7 

divided by column 4)

 34 Ibid. 35 Ibid.
Enclosure 2, ADC 1265

Page 87

AP5.2.10.9.19.1. MRA40d – Source of Supply Stock and 

DVD Detail. Shows Stock and DVD shipments from wholesale inventory for all 

DoD Components/ Participating Agencies and all categories by the wholesale ICP 

directing the shipment, and by receiving Component. The count of qualified 

shipments is matched against MRAs received/MRAs not received, and for MRAs 

not received, the percentage of the count and value is computed and shown:

Column 1 – Source of Supply RIC for the DoD Component selected in the Summary Report for 

qualifying requisitions and the “RIC From” for qualifying materiel 

release order transactions

Column 2 – Receiving 

Component

DoD Component of the ship-to DoDAAC

Column 3 – Shipments 

Requiring MRA, Count

Count of qualified Stock and DVD shipments from wholesale 

inventory that were filled in the allotted timeframe

Column 4 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified Stock and DVD shipments in 

the allotted timeframe

Column 5 – MRA Not Received, 

Count

Count of qualified Stock and DVD shipments for which no MRA 

was received in the allotted timeframe (within 25/90 calendar 

days of shipment to accommodate the MRA reporting period plus 

the MRA follow-up response timeframe)36

Column 6 – MRA Not Received, 

Percent of Count

Percentage (by count) of the qualified Stock and DVD shipments 

for which no MRA was received in the allotted timeframe (column 

5 divided by column 3)

Column 7 – MRA Not Received, 

Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe

Column 8 – MRA Not Received, 

Percent of Value

Extended dollar value of the qualified shipments that did not 

receive an MRA in the allotted timeframe (column 7 divided by 

column 4)

AP5.2.10.9.19.2. MRA40dd – Source of Supply DoDAAC 

MRA Stock and DVD Detail. Selecting a source of supply in the previous 

MRA40d, Source of Supply Stock and DVD – Detail Report will show Stock and 

DVD shipments for ship-to DoDAACs with qualifying shipments. The count of 

qualified Stock and DVD shipments is matched against MRAs received/MRAs not 

received, and for MRAs not received, the percentage of the count and value is 

computed and shown:

Column 1 – Ship-To DoDAAC Ship-to DoDAACs for the wholesale ICP RIC selected from the 

Detail Report

Column 2 – Shipments 

Requiring MRA, Count

Count of qualified Stock and DVD shipments from wholesale 

inventory that were filled in the allotted timeframe

Column 3 – Shipments 

Requiring MRA, Value

Extended dollar value of qualified Stock and DVD shipments in the 

allotted timeframe

 36 Ibid.
Enclosure 2, ADC 1265

Page 88

Column 4 – MRA Not 

Received, Count

Count of qualified Stock and DVD shipments for which no MRA 

was received in the allotted timeframe (within 25/90 calendar days 

of shipment to accommodate the MRA reporting period plus the 

MRA follow-up response timeframe)37

Column 5 – MRA Not 

Received, Percent of Count

Percentage (by count) of the qualified Stock and DVD shipments 

that did not receive an MRA in the allotted timeframe (column 4 

divided by column 2)

Column 6 – MRA Not 

Received, Value

Extended dollar value of the qualified Stock and DVD shipments 

that did not receive an MRA in the allotted timeframe

Column 7 – MRA Not 

Received, Percent of Value

Percentage (by value) of the qualified Stock and DVD shipments 

that did not receive an MRA in the allotted timeframe (column 6 

divided by column 3)

 37 Ibid.
Enclosure 2, ADC 1265

Page 89

AP6. APPENDIX 6

X12 CONTROL STRUCTURES AND SEPARATORS

AP6.1. GENERAL

As noted in Chapter 5, X12 Control Structures and Segment/Element Separators 

are defined in the following tables:

AP6.1.1. X12 Control Structures. The approved Defense Logistics Management 

Standards (DLMS) Accredited Standards Committee (ASC) X12 Control Structures 

are defined in Table A6.T1.

Table A6.T1. X12 Control Structures

Data

Element

Min/

Max Definition Value Notes

ISA01 2/2 Authorization 

Qualifier

00 – No Authorization

Present

05 – DoD Communication ID

06 – Fed. Communication ID

ISA02 10/10 Authorization

ID

Trading Partner Specific Use Blank for 

DLMS

ISA03 2/2 Security Info. 

Qualifier

00 – No Security Info

01 – Password

Use ‘00’ for DLMS

ISA04 10/10 Security Info. Trading Partner Specific Use Blank for 

DLMS

ISA05 2/2 Interchange

Sender ID

Qualifier

01 – DUNS Number

02 – SCAC

04 – IATA

08 – UCC EDI

09 – X.121

10 – DoDAAC

16 – DUNS + 4

ZZ – Mutually Defined
Enclosure 2, ADC 1265

Page 90

Table A6.T1. X12 Control Structures

Data

Element

Min/

Max Definition Value Notes

ISA06 15/15 Interchange

Sender ID

Trading Partner Specific Most Commercial

VANs use either

DTDN or GOVDP

qualified with ZZ to

identify DAAS as 

the trading partner.

DLMS trading

partners use 

S36121 qualified 

with 10 to identify 

DAAS EBUS. 

ISA07 2/2 Interchange 

Receiver ID

Qualifier

01 – DUNS Number

02 – SCAC

04 – IATA

08 – UCC EDI

09 – X.121

10 – DoDAAC

16 – DUNS + 4

ZZ – Mutually Defined

ISA08 15/15 Interchange

Receiver ID

Trading Partner Specific See ISA06

ISA09 6/6 Interchange

Date

YYMMDD Use UTC (GMT)

ISA10 4/4 Interchange

Time

HHMM Use UTC (GMT)

ISA11 1/1 <4030 -

Interchange

Control 

Standards ID

>4030 -

Repetition 

Separator

U – US EDI Community

Hex 1E or ‘

For version prior to

4030 this was a

constant “U”, for

4030 and above

this is any of the

recognized Element

Separators as long

as it does not 

duplicate one that 

is already used.38

 38 Refer to ADC 1275 for detailed guidance on X12 delimiters.
Enclosure 2, ADC 1265

Page 91

Table A6.T1. X12 Control Structures

Data

Element

Min/

Max Definition Value Notes

ISA12 5/5 Interchange

Control 

Version

Number

Trading Partner specific, 

dependent upon 

implementation Convention 

used.

Expressed as , for 

example; 04030

ISA13 9/9 Interchange

Control 

Number

Must uniquely identify the

ISA envelope over an

extended period of time.(one 

year)

ISA14 1/1 Acknowledgement 

Requested

0 - None This refers to TA1

acknowledgements, 

NOT 997

ISA15 1/1 Test Indicator T - Test

P - Production

ISA16 1/1 Composite

Element

Separator

Trading partner specific Hex 1F is

recommended, “\” 

can be used as the

printable version39

GS01 2/2 Functional ID Transaction Set specific See the 

Implementation 

Convention

GS02 2/12 Application

Sender Code

Trading Partner Specific Use S36121 to

identify DAAS

Processing.

GS03 2/12 Application

Receiver

Code

Trading Partner Specific

GS04 8/8 Date CCYYMMDD

GS05 4/4 Time HHMM

GS06 1/9 Group Control 

Number

Must uniquely identify the

group envelope over an

extended period of time.

(one year)

GS07 1/1 Responsible

Agency Code

X – ASC X12 Committee

 39 Ibid
Enclosure 2, ADC 1265

Page 92

Table A6.T1. X12 Control Structures

Data

Element

Min/

Max Definition Value Notes

GS08 6/12 Version/

Release No.

Trading Partner Specific -

dependent upon

Implementation Convention 

used, must be the same 

version as the ISA

Can include

additional 

information 

regarding the 

specific release. 

example BSM 

instance carries 

Implementation 

Convention 

information; 

004030-940R 

AP6.1.2. Segment/Element Separators. The approved DLMS X12 Separators are 

defined in A6.T2:40

Table A6.T2. X12 Segment/Element Separators

Name Recommended

(Non-printable)

Printable (data in viewable format) EXAMPLES 

ONLY

Data Element Separator Hex 1D *

Segment Terminator Hex 1C ~

Composite Element Sep. Hex 1F \

Repetition Separator41 Hex 1E ‘

 40 Ibid 41 Element Repetition is only supported in ASC X12 versions 4030 and higher.
Enclosure 2, ADC 1265

Page 93

AP7. APPENDIX 7

MATERIEL RECEIPT ACKNOWLEDGMENT (MRA)

REPORT BUSINESS RULES

AP7.1. Materiel Receipt Acknowledgement Report – Business Rules

AP7.2. Background. 

AP7.2.1. MRA reports show shipments and the percentage of shipments for 

which the Defense Automatic Addressing System (DAAS) receives and does not 

receive the associated MRA transactions. Qualifying Shipments included in the report 

are determined by the date released to carrier (recorded at DAAS) plus 25 calendar 

days to accommodate the 17 calendar days MRA reporting period and the 10 calendar 

days MRA follow-up response timeframes (if Continental United States (CONUS)); 

or plus 43 calendar days to accommodate the 34 calendar days MRA reporting period 

and the 10 calendar days MRA follow-up response timeframe (if OCONUS –

Transportation Category 1 or 2); or plus 90 calendar days to accommodate the 81

calendar days MRA reporting period and the 10 calendar days MRA follow-up 

response timeframe (if OCONUS – Transportation Category 3).42 Security assistance 

program requisitions are not captured for inclusion in Logistics Metrics Analysis 

Reporting System (LMARS) or MRA Reports based on the Security Cooperation 

Implementing Agency code in the first position of the document number.

AP7.2.2. The MRA report is created at the end of each month to reflect the 

MRA transactions as received/not received in the preceding month. Receipt of an 

MRA citing Discrepancy Code B or F updates the LMARS reports to reflect the 

current status of MRA transactions received. The MRA Reports are created monthly 

and reflect the MRA data at the end of the month and will not be adjusted 

retroactively when an MRA is submitted following receipt of materiel after an MRA 

citing Discrepancy Indicator Code B or F is received.

AP7.3. TRANSACTIONS

AP7.3.1. Transactions identified in the MRA Business Rules by Defense 

Logistics Management Standards (DLMS) Transaction and Legacy Document 

Identifier Code (DIC)

AP7.3.1.1. The Requisition transaction is identified by the DLMS 511R by 

beginning segment (1/BR02/020 Code A0). This transaction provides the 

functionality of Department of Defense (DoD) Military Standard Requisitioning and 

 42 Per DLM 4000.25, Chapter 10, the reporting period is defined as 17 calendar days for CONUS; 34 

calendar days for OCONUS Transportation Category 1 and 2 shipments; and 81 calendar days for 

OCONUS Transportation Category 3 shipments. The follow-up response timeframe for both is 10

days. Refer to ADC 1114.
Enclosure 2, ADC 1265

Page 94

Issue Procedures (MILSTRIP) legacy Document Identifier Codes (DIC) A01, A02, 

A04, A05, A07, A0A, A0B, A0D, and A0E.

AP7.3.1.2. The Requisition Follow-up transaction (process as requisition 

if original requisition not received) is identified by the DLMS 869F by the beginning 

segment (1/BSI08/020 Code IN). This transaction provides the functionality of 

MILSTRIP legacy DIC AT1, AT2, AT4, AT5, AT7, ATA, ATB, ATD and ATE.

AP7.3.1.3. The Requisition Modification transaction (process as requisition if 

original document not received) is identified by the DLMS 511M by beginning segment 

(1/BR02/020 Code AM). This transaction provides the functionality of MILSTRIP legacy 

DIC AM1, AM2, AM4, AM5, AMA, AMB, AMD, and AME.

AP7.3.1.4. The Passing Order transaction is identified by the DLMS 511R by 

beginning segment (1/BR02/020 Code BM). This transaction provides the functionality 

of MILSTRIP legacy DIC A31, A32, A34, A35, A37, A3A, A3B, A3D, and A3E.

AP7.3.1.5. The Referral Order transaction is identified by the DLMS 511R 

by beginning segment (1/BR02/020 Code BN). This transaction provides the 

functionality of MILSTRIP legacy DIC A41, A42, A44, A45, A47, A4A, A4B, A4D, and 

A4E. The exception is where Distribution Code 2 or 3 is present to indicate the 

transaction is; 2 – lateral redistribution of consumable, or 3 – reparable assets.

AP7.3.2. Service Specific Transactions

AP7.3.2.1. The Requisition Image transaction is identified by the DLMS 

511R by beginning segment (1/BR02/020 Code A0 or BN and 1/BR06/020 Code FI). 

This transaction provides the functionality of The Defense Logistics Agency (DLA), 

Air Force, and General Services Administration (GSA) unique legacy DIC CH1 

and CHA. This transaction is used where the original transaction has bypassed the 

normal DAAS transaction flow.

AP7.3.2.2. The DLA post-post issue from forward stock at recruit training 

centers is identified by the DLMS 867I by beginning segment (1/BPT04/20 Code 01). 

This transaction provides the functionality of Military Standard Transaction 

Reporting and Accountability Procedures (MILSTRAP) legacy DIC D7_.

AP7.3.2.3. The Image of an Activated Prepositioned Requisition (Army) is 

identified by the DLMS 511R by beginning segment (1/BR02/020 Code A0 and 

1/BR06/020 Code FI). This transaction provides the functionality of Army unique 

transaction DIC BE9 (Image of an Activated Pre–Positioned Requisition). This 

transaction is created by the Army National Inventory Control Point/Service Item 

Control Center (NICP/SICC) at the same time a pre-positioned requisition in support 

of Operation Plans, or mobilization station/training base installation requirements is 

released. The transaction is forwarded to the requisitioner (routed by DAAS), and is 
Enclosure 2, ADC 1265

Page 95

used by the requisitioner to establish a due-in record for receipt processing of 

materiel issued by the NICP/SICC from processing of a pre-positioned requisition.43

AP7.3.3. Original Source Transaction is an equivalent A5_Materiel Release 

Order (MRO)

AP7.3.3.1. The MRO is identified by the DLMS 940R by the shipping 

order identification segment (1/W0506/0200 Code NA). This transaction provides 

the functionality of MILSTRIP legacy DIC A51, A52, A54, A55, A57, A5A, A5B A5D, 

and A5E.

AP7.3.3.2. The Lateral Redistribution Order is identified by the DLMS 

940R by the shipping order identification segment (1/W0506/0200 Code NI and 

1/W0507/0200 Code RG). This transaction provides the functionality of MILSTRIP 

legacy DIC A41, A42, A44, A45, A47, A4A, A4B, A4D, and A4E with Distribution 

Code 2 or 3 present to indicate the transaction is a lateral redistribution of 

consumable or repair assets.

AP7.3.3.3. The DLA Post-Post Directed Material Release Order (MRO) 

(Requisition) is identified by the DLMS 511R by beginning segment (1/BR02/020 

Code A0 and 1/BR06/020 Code J). This transaction provides the functionality of the 

DLA unique transaction C0A/C01). 

AP7.3.3.4. The DLA Post-Post Directed MRO (Referral) is identified by the 

DLMS 511R by beginning segment (1/BR02/020 Code BN and 1/BR06/020 Code J). 

This transaction provides the functionality of the DLA unique transaction CQA/CQ1).

AP7.3.3.5. The Army Offline MRO Image is identified by the DLMS 940R 

by the beginning segment (1/W0506/0200 Code NA, and 1/W0507/0200 Code FI). 

This transaction provides the functionality of the Army unique transaction B99. 

AP7.3.3.6. Intra Navy Issue (MRO) is identified by the DLMS 940R by the 

beginning segment (1/W0506/0200 Code NA). This transaction provides the 

functionality of the Intra Navy use of MILSTRIP DIC A4. The Intra Navy A4_ does not 

have a Distribution Code of 2 or 344 however it is treated as an MRO. The other 

transaction used in the Navy Issue (MRO) scenario is identified by the DLMS 867I by 

the beginning segment (1/BPT04/20 Code 01). This transaction provides the 

functionality of the Intra Navy use of MILSTRIP legacy DIC D7_. These two 

 43 The Army advised that with the transition to Army LMP, this functionality is not currently in use, but the 

DAAS processing rules should be retained for potential future use.

44 Standard A4_ transaction with a Distribution Code = 2 or 3 is treated as a lateral redistribution order. 

Navy A4_ is treating this A4_ as an MRO and not a requisition, thus a special rule is required so LOTS 

can flag appropriately. The internal rule in LOTS for categorizing these D7s is: If there is no other 

requisition DIC equivalent as defined in decision blocks 2 and 3, then flag the D7 as a requisition 

equivalent; if there is a requisition equivalent, but no traditional MRO, then treat the D7 as an MRO; if 

there is a requisition equivalent and MRO equivalent, but no shipment status, then treat the D7 as 

shipment. Summary: Navy – No Shipment; D7_ is a shipment; No MRO, D7_ is an MRO; No Reqn, D7_ 

is a Requisition.
Enclosure 2, ADC 1265

Page 96

transactions are primarily from Navy Enterprise Resources Planning (ERP) to 

Commercial Asset Visibility (CAV) sites to issue A condition materiel from a CAV site.

AP7.3.3.7. Air Force Redistribution Order (RDO) is identified by the DLMS 

940R by the beginning segment (1/W0506/0200 Code NI). This transaction provides 

the functionally of the MILSTRIP legacy A2_. This Air Force RDO is generated only 

for Air Force wholesale (owned) assets that are being shipped to another 

Distribution Standard System (DSS) storage site or being sent to an Air Force site 

for storage. If no record of the RDO (no shipment suspense or RDO/Referral 

suspense record then the Air Force will use an RDO Follow-Up identified by the 

DLMS 940R by the beginning segment (1/W0506/0200 Code NI and 1/W0507/0200 

Code 82). This transaction provides the functionality of the Air Force Unique BF7 

transaction. The Air Force system will reformat BF7 as an A2_ and either ship or 

create a B7_ (Denial). For issues to depot maintenance, the A5_ is sent to DSS.45

AP7.4. MRA Business Rules derived from the MRA Decision Tree. The following list 

identifies the decision blocks and key transactions and business rules used to identify 

the presence of a requisition or MRO type transactions to determine MRA Report 

eligibility. The decision blocks identify transactions unique to Component specific 

processes. Figure AP7.F1. is a graphical version of the MRA Decision Tree.

Decision Block 1. Is the Source of Supply a wholesale Inventory Control Point 

(ICP)? There must be a Wholesale ICP in the To_RIC of the Requisition or the 

From_RIC of the MRO.46 The authoritative list of wholesale ICPs is found at 

LMARS Output Report Specific Tables.

a. If No, terminate MRA decision tree (No MRA Required)

b. If Yes, proceed to Decision Block 2 

Decision Block 2. Is the original source transaction a requisition, requisition 

modification, or requisition follow-up transaction? This business rule applies to all 

Services/Agencies. 

a. If Yes, proceed to Decision Block 6 to determine if there is an associated 

shipment status from a wholesale ICP. Note: If there is no associated shipment status, 

there is no MRA tracking for that transaction.

b. If No, proceed to Decision Block 3

 45 Some of the Air Force A2_, BF7 process was identified in ADC 405 to support ECSS development.

46 DAAS records the ICP (To RIC) for requisition type transaction, passing, referral and redistribution 

order transactions. When an MRO type transaction is received, the ICP is re-recorded and the From RIC 

is used. If and MRO is received by DAAS, unless they receive a denial, the recorded ICP is never 

changed. A denial and new MRO will change the ICP.
Enclosure 2, ADC 1265

Page 97

Decision Block 3. Is the original source transaction a passing order or referral order, 

where the Distribution Code does not equal 2 or 3 in the first position?47 This business 

rule applies to all Services/Agencies.

a. If Yes, proceed to Decision Block 6 to determine if there is an associated 

shipment status from a wholesale ICP

b. If No, proceed to Decision Block 4

Decision Block 4. Is the original source transaction one of the following 

Service/Agency-specific transaction types? These transactions are functioning similar 

to a requisition.

a. Army: Activated Prepositioned Requisition citing Service/Agency Code A, C 

or W in the first position of the document number

b. DLA: Requisition Image CONUS or Outside Continental United States 

(OCONUS)?

c. DLA: Post-Post issues (D7_) from forward stock at recruit training centers?

d. GSA: CH1, CHA (image transactions)?

i. If Yes, proceed to Decision Block 6 to determine if there is an 

associated shipment status from a wholesale ICP

ii. If No, proceed to Decision Block 5

Decision Block 5. Is the original source transaction an MRO or equivalent 

transaction?

a. All Services/Agencies: MRO or Lateral Redistribution Order citing Distribution 

Code 2 or 3 in the first position 

b. DLA ICPs: Post-Post Directed MRO (Requisition)48

c. Army: Offline MRO Image 

d. Navy: Intra-Navy Issue (MRO)

 47 Distribution Code: 

2 – For use by IMMs to identify transactions associated with lateral redistribution of DoD consumable 

assets.

3 – For use by IMMs to identify transactions associated with lateral redistribution of DoD reparable 

assets.

48 DLA will not generate an A5_ unless it is for a customer requisition.
Enclosure 2, ADC 1265

Page 98

e. Air Force: RDO and RDO Follow-Up 49

i. If Yes, proceed to Decision Block 6 to determine if there is an 

associated shipment status from a wholesale ICP

ii. If No, terminate MRA decision tree (No MRA Required)

Decision Block 6. Is there a shipment status from a Wholesale ICP? The 

authoritative list of wholesale ICPs is found on the LMARS master data record at 

LMARS Output Report Specific Tables.

a. If No, terminate MRA decision tree (No MRA Required)

b. If Yes, proceed to Decision Block 7 to determine if any additional MRA 

exclusions apply

Decision Block 7. Do any of the following exclusions apply? 

a. Requisition Department of Defense Activity Address Code (DoDAAC)

or the ship-to DoDAAC is GSA or Federal/Military Standard 

Requisitioning and Issue Procedures (FEDSTRIP)

b. Security Cooperation Implementing Agency code B, D, I, K, P or T in the 

first position of the document number

c. DoDAAC in document number begins with HX

d. Distribution Code is 9 in first position indicating the requirement is for DLA 

Disposition Services

e. Non-ICP/IMM Directed Inter-Service Lateral Redistributions. ADC 1062 

established procedures to support Non-ICP/IMM Directed Inter-Service Lateral 

Redistributions.50

i. If No, proceed to Decision Block 8 to determine if a follow-up for 

delinquent MRA was sent by the wholesale ICP

ii. If Yes, terminate MRA decision tree (No MRA Required)

Decision Block 8. Did the ICP generate a follow-up for delinquent MRA transaction 

(DRF) within the required time limit?51

 49 Air Force BF7 was only used between D035A and SBSS (ILS-S and base retail). It is an RDO follow-up 

to the shipping activity. Air Force plans to continue using A2_ and has no plan to convert to A5_. 50 See ADC 1062 – Non-Inventory Control Point/Integrated Materiel Manager (ICP/IMM)-Directed InterService Lateral Support via Retail Level Passing Order. 51 See ADC 1087 – Revise Materiel Receipt Acknowledgement (MRA) Report Selection Criteria to Reflect 

the MRA Process Exclusion for Receipt Transaction Reporting.
Enclosure 2, ADC 1265

Page 99

a. If Yes, track for Receipt of MRA Transaction

b. If No, No MRA Tracking required

AP7.5. Requirements for Generating MRA Reports

AP7.5.1. Data Included in Reports

AP7.5.1.1. The initial rule for reports that must be met is the document 

numbers that yielded the requirement for MRA Tracking are based on the business 

rules identified in the MRA Decision tree Figure AP7.F1.

AP7.5.1.2. If Signal Code = J, K, L or M, then the Supplementary Address 

(SUPPADD) is considered the Ship-To DoDAAC. If signal Code = A, B, C, or D, 

then the activity address code in the document number is the Ship-To DoDAAC.

AP7.5.1.3. Parsing the data by Service/Agency is determined by the 

Service/Agency code in the first position of the document number. 

Source: LMARS Table H – Service and/or Report Affiliation at LMARS Output 

Report Specific Tables.

AP7.4.1.4. Location (CONUS/OCONUS) is determined by the Ship-To 

DoDAAC. The CONUS/OCONUS is obtained from the Combatant Command 

(COCOM) designation in the DoDAAC file and stored in the LMARS/Logistics 

Response Time (LRT) file.

AP7.5.1.5. Direct Vendor Delivery (DVD). DVD is identified one of two ways:

AP7.5.1.5.1. Supply Status DLMS 870S beginning segment 

(1/BSR01/20 Code 5). This transaction provides the functionality of MILSTRIP 

legacy DIC AB1, AB2, AB3, and AB8. 

AP7.5.1.5.2. Supply Status DLMS 870S beginning segment 

(1/BSR01/20 Code 4 and logistics qualifier (2/LQ01/330 Code 81) citing Status Code 

BV or BZ. This transaction provides the functionality of MILSTRIP legacy DIC AE1, 

AE2, AE3, AE8, AE9, AEA, AEB, AED, and AEE.

AP7.5.1.6. Dollar Value is determined by multiplying the unit price on the 

Source of Supply field by the quantity in the requisition.

AP7.5.1.7. Suffixed document numbers are treated as individual 

requisitions and MRA is applied using the 15 position document number, if present. 

If no match, a match is made on the 14-position document number and quantity. 

AP7.5.1.8. Split/Partial Shipments

AP7.5.1.8.1. Existing Business Rule. Split Shipments at the 

distribution center (multiple TCNs), the first receipt will be counted as the receipt. 
Enclosure 2, ADC 1265

Page 100

AP7.5.1.8.2. Revised Business Rule. DLM 4000.25, Volume 2, 

C10.2.6. Acknowledgement of Split or Partial Shipments. When a shipped line item 

(requisition document number and suffix code) is consigned as a split or partial 

shipment, submit an MRA for the shipment segments as they are received. The split 

or partial shipment codes are part of the transportation control number (TCN) 

structure in accordance with Defense Transportation Regulation (DTR) 4500.9-R,. 

Accordingly, reporting activities must include the TCN in the MRA transaction when 

it is available (ADC 247). If the total quantity for the shipped line item is not received 

by the due-in date, report the missing quantity, citing Discrepancy Indicator Code F, 

in accordance with the guidance in the MRA transaction.

AP7.5.2. Categories of Reports. Existing DAAS documentation requires 

update to remove descriptions for reports that were removed by previous ADCs. 

(MRA04 (ADC 1086 (Reference 3.h.)), MRA05, MRA06, and MRA31 (ADC 482).

AP7.5.3. Invalid, Y-Series, or clear-text exception Ship-To. Existing DAAS 

edits should prevent successful processing of transactions containing invalid or YSeries ship-to values. However, if successfully processed, these shipments will be 

counted against the requisitioner’s DoDAAC (ADC 482).52 If no ship-to DoDAAC is 

associated with the exception address, these shipments will be counted against the 

requisitioner’s DoDAAC.

AP7.6. Figure AP7.F1. shows a graphic representation of the MRA Report 

business rules identified in the previous sections.

 52 Existing requisition edits are addressed in MILSTRIP Chapter 3, Table C3.T2, Requisition Processing 

and Related Actions, and the DoDAAC authority code edits identified in MILSTRIP C.2.28.11, Table 

C2.T1. DoDAAC Authority Codes.
Enclosure 2, ADC 1265

Page 101

Figure AP7.F1. MRA Report Business Rules 

1

SoS = 

Wholesale ICP?

(Refer to master 

list)

Capture Shipments out of Wholesale Assets that Qualify for MRA Reporting

Update MRA Business Rules/Report Logic to require the presence of a requisition or MRO type document to determine MRA report eligibility1

2

All:

Is the initial supply 

transaction a

requisition?

A0_, AT_ or

AM_ 

5

Is the 

Initial supply transaction 

an equivalent A5_MRO?

All: A5_ (except A5J) and 

A4_ with 2 or 3 in RP54

DLA ICPs: C0_, CQ_

Intra Navy: A4_, D7_ 4

Air Force: A2_, BF7

Army: B99

No

4

Service Specific: 

Is the initial supply

transaction one of the following?

Army: BE9, (RP30 = A, C, W)

DLA: CH1, CHA, D7_

2

Air Force: CH1, CHA

GSA: CH1, CHA

Yes

Track for 

Receipt of MRA 

Transaction

Yes

No MRA 

tracking

LMARS processes first to 

look for a valid SoS in either 

the Requisition or MRO.

7

Do any of the Following 

Exclusions Apply?

3

Reqn or Ship-To DoDAAC = GSA or 

FEDSTRIP 

FMS docs start w/B, D, I, K, P or T

Shipment to state, civil or Federal Agencies 

Shipments of FF&V 

DoDAAC4 begins with HX 

Distribution Code = 9_

No

8

Did the ICP 

Generate a Follow-Up 

For Delinquent MRA transaction 

(DRF) within the require time limit?

(Intra-Component 

shipments) 

PDC1087

Yes

No

No

6

Is there Shipment 

Status (from a 

Wholesale ICP)?

(DIC AS_) 

No

Yes

Yes

No

1 This will eliminate redistribution orders from being included in MRA Reports

2 DLA post-post issues (D7_) from forward stock at recruit training centers 3 Exclusions noted in DLA Transaction Services Business rules from 2/2003 

and clarified in PDC 1088 4 AF uses A2_ as an equivalent MRO, no plans to change to A5_.

Key: Blue text = Proposed new selection criteria.

A2 – Redistribution Order (RDO), A3 – Passing Order, A4 – Referral Order, Lateral Redistribution Order (LRO), 

A5 – Materiel Release Order (MRO), A5J – Materiel Release Order, Image Transactions – (CH_), Post Post (CO_, CQ_ ). 

Revised: October 31, 2014 (Corrected text in Step 7 to add “Reqn or Ship-To DoDAAC and remove associated footnote).

Gaps

Offline DLA processes for Subsistence, Medical; and 

Maintenance Repair and Operations. These are known 

MRA gaps because no shipment status is created.

Yes

3

All: 

Is the initial supply 

transaction an A3_ or 

A4_? 

(and not 2 or 3

in RP54)

Yes

Yes No

No MRA 

tracking