Frequently Asked Questions (FAQ) and Answers
Following are the FAQ topic areas. Click the topic to be taken to the questions and answers, below:
I can't open a Word file on the site, I just get a blank page. What's the problem?
We have found a couple of situations where people are unable to open documents created with Microsoft Office applications (e.g., Word) from our Website; the user gets a blank screen, even though the status indicates that the operation is "DONE". This problem appears to only impact users on WIN 7/Microsoft Office 2010 platforms.
When we researched the Microsoft Office 2010 Trust Center settings, we determined that the default setting (unchangeable by the user) is to block binary documents created in 2000, 97, and 95 versions of Microsoft applications. Binary documents created in 2003, 2007, 2010 are free to access. Of note, those users in older versions of Microsoft Office have different default trust settings that allow these older documents to be opened (e.g., not blocked).
- Rather than selecting "Open" when prompted by Internet Explorer, select "File" => "Save As".
- Save the document to your desktop.
- When the save is done, you will be automatically prompted to either "Open" the document or "Close" the window.
- Select "Open"
- The document should open. Once done, you can go back and move the document from your desktop to the recycle bin.
- I am looking for the Jump Start PMP. Where do I find it?
The latest version of the Project Management Plan (PMP) and other related Jump Start information can be found on the DLMS Implementation Home Page.
- What does "MILS" mean?
The term MILS, Military Standard(s), is used to describe legacy 80-column record position transactions embodied in the Military Standard Requisitioning and Issue Procedures (MILSTRIP), Military Standard Transaction Reporting and Accounting Procedures (MILSTRAP), and Military Standard Billing System (MILSBILLS) manuals. The overarching term is Defense Logistics Standard Systems (DLSS) which is a term that also refers to the MILS procedures. The DLSS are being replaced by Defense Logistics Management Standards (DLMS) manual which documents these procedures in a combined maual along with use of the DLMS replacement transactions, in American National Standards Institue (ANSI) Accredited Standards Committee (ASC) X12 format that contain unlimited record positions. The DLSS to DLMS cross reference can be found on the Defense Logistics Management Standards Office website at: DLMS Cross References.
- What is the reason for the migration to Defense Logitics Management System (DLMS)?
The MILS are impeding the Department of Defense (DoD) logistics business transformation goals. As the Under Secretary of Defense for Acquisition, Technology and Logsitics (USD (AT&L)) stated in his December 22, 2003, policy memorandum, Migration to DLMS and Eliminate Defense Logistics Standard Systems (DLSS)..." Rigid fixed length EDI formats are functionally constraining, technologically obsolete, and unique to DoD." In order for DoD to expand and improve its logistics business practices, the Department must move away from the MILS as the basis for information exchanges.
- Will DLMS migration be phased?
Yes. Phased migration began in 1998.
- What Extensible Markup Language (XML) standard will be followed?
Currently there is only one standard, DLMS XML, based on the Worldwide Web Consortium (W3C) tagging method and based on the electronic date interchange (EDI) structure. We will expand to other XML variants when such variants are recognized as DoD standard.
- Will we no longer receive an 80 card column data file on our status?
The direction is away from the 80 column DLSS/MILS to the more robust DLMS standard. This was mandated by a USD (AT&L) memorandum to the Component Secretaries on December 22, 2004. DLA Transaction Services will maintain customer profiles and furnish data to system based on the system profile.
- What will be the impact on Foreign Military Sales (FMS) customers?
We suspect that some time in the future FMS Customers will see an advantage to moving away from the MILS to the DLMS. Until that happens DLA Transaction Services and Defense Logistics Management Standards will provide the community services required to ensure full interoperability with our FMS Customers.
- How will MILS to DLMS the conversion work?
As within DoD, DLA Transaction Services will provide conversion services to translate between standards. MILS to X12/XML, X12 to MILS/XML, and XML to X12/MILS, as covered by each user customer profile including profiles for Security Assistance users.
- Will the Fund Code be used or replaced in DLMS?
The Fund Code is included in the DLMS and will be used to derive the appropriation and bill to activity Department of Defense Activity Address Code (DODAAC) using the same methodology and tables that are currently used in the MILSBILLS processes. The appropriation code is also a placeholder within the DLMS. The appropriation number (which is not a data element in MILS transactions), while provided for in the DLMS, will not be usable until systems exchange information using the DLMS.
- Where is the A4_ mapped in DLMS?
In DLMS, the A4_ (Referral Order/Lateral Redistributiuon Order) is mapped according to the functional process rather than by Document Identifier alone. Therefore, the A4_ representing a Lateral Distribution Order (identified by Distribution Code 2 or 3) is mapped to the 940, Material Release. The A4_ representing a Referral Order is mapped to the 511R.
- How are data files transmitted that are currently passed via Defense Automatic Addressing System Center Automatic Message Exchange System (DAMES) using a telnet connection?
Per the DLA Transaction Services, DAMES is designed for MILS transactions only and cannot currently accept ASC X12. If current DAMES users convert to X12 or XML, they should't need a DAMES account any more. DLA Transaction Services would set-up a file transfer protocol (FTP) or Secure Hypertext Transfer Protocol (HTTPS) account for them, as are currently used for other X12/XML customers. DLA Transaction Services will continue to support DAMES/MILS processing for as long as it takes DoD customers to convert away from MILS. They will not be arbitrarily cut off.
- Open records--will they still receive status until material is received? If not, will it be required to maintain two files until they are?
The cessation of the MILS/DLSS does not change logistics core business rules. Only the methods of transmission are changing. You will still receive status based on business rules currently in effect.
- What is the status of XML formatted document identifiers (DOCIDs)--how many are actually in use by a live system?
DLMS transactions are available in either the ASC X12 format or XML W3C format. XML is being used by the Air Force's Integrated Logistics System-Supply (ILS-S), and Navy's RSupply System. Also, there are plans by the Air Force to use the DLMS XML for their Expeditionary Combat Support System (ECSS) ERP implementation, but this is still in the planning phase.
- Will there be new hardware required to support the use of DLMS?
Required hardware/software will depend upon respective migration plans.
- Who is going to pay to upgrade legacy systems? Can we wait until we have the opportunity to POM for the necessary funds?
Upgrades are the responsibility of each Component/Agency. Users were required to submit migration plans to Defense Logistics Management Standards for forwarding to USD AT&L. All such issues should be addressed in those plans. Additionally, initial guidance to convert to DLMS was provided in 1998 leaving ample time to submit Program Objective Memorandum (POM) requests for this requirement.
- What additional information is available on commercial-off-the-shelf products to support X12 to XML translations?
DLA Transaction Services has implemented a full conversion process that converts between standards (MILS to X12/XML, X12 to MILS/XML, and XML to X12/MILS). There is no need for Components and Agencies to establish a duplicate process that is already available. Users need "one" trading partner and that is DLA Transaction Services. DLA Transaction Services maintains customer profiles for "all" users and can translate to any format needed by those users.
- Is there enough time to make this migration?
DLMS policy has been in effect since 1998. Based on DoD USD (AT&L) 22 December 2003 memorandum "Migration to the DLMS and Elimination of the MILS," this migration should have been completed by now. There is enough time because the work must be completed by all systems before full benefits can be realized.
- What are the requirements for DLMS?
DLM 4000.25 covers DLMS business requirements. Useful DLMS information is available on the Defense Logistics Management Standards Office website. The DLM 4000.25 and other Defense Logistics Management Standards Office administered publications are available at: DLMS Publications.
- What EDI formats can accommodate UID (unique identification)?
All X12/XML transactions are capable of carrying UID. However, UID is currently included in the following DLMS Implementation Conventions: 527D (Due-In/Advance Receipt Verification), 856 (Advance Shipment Notice), 856S (Shipment Status), and 861 (Acceptance Report). These are available at: DLMS IC Page.
- How will the Defense Automatic Addressing System (DAAS) ensure that MILSBILLS data fields are perpetuated into DLMS?
The cessation of the MILS/DLSS does not change logistics core business rules. Only the methods of transmission are changing. You will still receive status based on present business rules now in effect.
- Is DLMS training available?
Training is available at DLMS Training Page.
- What is the Department of Defense Activity Address Directory (DoDAAD)?
The Department of Defense Activity Address Directory (DoDAAD) is an interactive, relational database that contains numeric records that identify activities. It serves as the single authoritative source of identification, routing, and address information for authorized users, including all Departments and Agencies of the Federal Government (DoD Components and Federal Agencies), authorized contractors, and authorized State and local government users. See DLM 4000.25, volume 6, chapter2, paragraph 1.1.
- What is the DoDAAF?
The DoDAAF (Department of Defense Activity Address File) was the name used to identify the flat-file version of the DoDAAD that existed prior to the reengineering of the DoDAAD in 2005 from a flat-file into the dynamic database that exists today? It is an archaic term.
- Who “owns” the DoDAAD?
The Secretary of Defense, by Agreement with the General Services Administration, administers the DoDAAD on behalf of the DoD and Federal Government. The Under Secretary of Defense for Acquisition, Technology, and Logistics (USD AT&L) delegates this responsibility to the Deputy Assistant Secretary of Defense for Supply Chain Integration (DASD, SCI), through the Assistant Secretary of Defense for Logistics & Materiel Readiness (ASD L&MR). The Defense Logistics Management Standards Office (DLMSO) is chartered by DASD SCI to chair a Process Review Committee (PRC) for the Administration of the DoDAAD, with participation by all stakeholder DoD Components and Federal Agencies. While DLMSO administers the rules, procedures, formats and codes used to construct the DoDAAD, the DoDAAD as a system is actually maintained by DLA Transaction Services. It is part of the larger suite of applications that together comprise the Defense Automatic Addressing System (DAAS). See DODM 4140.01, Volume 8, enclosure 3, paragraph 2; DLM 4000.25, volume 6, chapter2; and DLM 4000.25-4.
- How old is the DoDAAD?
The DoDAAD has been in existence since roughly 1960, when it largely existed as a paper-based, directory file that was updated manually by unit-level users who submitted TA_ transactions to the Defense Automatic Addressing Systems Center (DAASC) via hard cards that were keypunched at local communication centers. The Directory was originally a File that DAASC maintained, and as such, it was referred to as the DoDAAF until 2005, when the File was automated into the modern database that it is today, now known as the DoDAAD.
- Is the DoDAAD a “legacy” system?
No. When the DoDAAD was reengineered in 2005 into an Oracle® database, it ceased to be “legacy” and is now scalable to meet the ever evolving requirements of a transforming Government information technology portfolio of systems. This is why the DoDAAD is a facilitator of business system transformation and process improvement.
- What is the DoDAAD PRC?
The DoDAAD Process Review Committee is the Governance forum for the DoDAAD and exists to provide the DoD Components, Federal Agencies, and other organizations represented in the DoDAAD the ability to participate in the development, expansion, improvement, maintenance, and administration of DoDAAD policy and procedures. The policy and procedures span the entire spectrum of functional business domain uses of the DoDAAD and thus the PRC contains stakeholders representing each of these functional domains, including, but not limited to Procurement/Acquisition, Supply & Property, Finance & Accounting, Transportation, Maintenance, Human Resources, etc. There are over 300,000 DoD Activity Address Codes (DoDAAC), which are used in approximately five billion business transactions per year, by the DoD, Federal Agencies, State and local agencies, and supporting contractors of the DoD and Federal Government. See DODM 4140.01, Volume 8, enclosure 3, paragraph 2.a.(3); and DLM 4000.25, volume 6, chapter2.
- Who owns the data in the DoDAAD?
Management of the DoDAAD as a system is the shared responsibility of DLMSO and DLA Transaction Services; however, management of the data in the DoDAAD is the responsibility of the Components and Agencies who actually own the activities who have DoDAACs (and RICs) in the DoDAAD, and thus the data entered therein for each. The Central Service Points (CSPs) are the caretakers charged to maintain this data on behalf of their respective Services/Agencies. Ultimately, though, each Service/Agency Chief/Director/Administrator owns the data in the DoDAAD for their Service/Agency.
- Why is the DoDAAD CUI FOUO?
The DoDAAD is considered Controlled Unclassified Information For Official Use Only because it has been determined by the Secretary of Defense to meet the criteria for categorization as Critical Infrastructure Security Information (CISI), which is defined by 10 U.S.C. § 130e, to include: ‘…sensitive but unclassified information that, if disclosed, would reveal vulnerabilities in Department of Defense critical infrastructure that, if exploited, would likely result in the significant disruption, destruction, or damage of or to Department of Defense operations, property, or facilities, including information regarding the securing and safeguarding of explosives, hazardous chemicals, or pipelines, related to critical infrastructure or protected systems owned or operated by or on behalf of the Department of Defense, including vulnerability assessments prepared by or on behalf of the Department of Defense, explosives safety information (including storage and handling), and other site-specific information on or relating to installation security.’ See DLM 4000.25, volume 6, chapter2; and DODM 5200.01, Volume 4.
- Is the DoDAAD just for DLA?
No. The DoDAAD is maintained by DLA but belongs to all of the Services and Agencies who use it. As a system, it is considered a DoD enterprise system and not a DLA system.
- Is the DoDAAD only for logistics?
No. The DoDAAD supports business application systems data and interoperability requirements of the DoD and Federal Agencies, including (but not limited to) procurement and acquisition, grants, supply chain, property, materiel management, distribution, transportation, maintenance, financial management, contracting, readiness, and human resource systems. See DLM 4000.25, volume 6, chapter2.
- Who or what is DLA Transaction Services?
DLA Transaction Services is the activity within the Defense Logistics Agency (DLA) that operates the Defense Automatic Addressing System (DAAS) and the International Logistics Communications System (ILCS). Neither 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. See DLM 4000.25-4.
- What is DAAS?
The Defense Automatic Addressing System or “DAAS” is an enterprise value-added business transaction processing hub which provides validation, translation, routing, achieving, inquiry, and reporting services to its customer base. Additionally, it hosts a wide range of enterprise reference repositories such as the DoDAAD, MAPAD, Project Code, Distribution Code, and Fund Code Tables. It also provides a host of applications which can query the entirety of the consortium of data that flows through DAAS in order to generate various reports and metrics on the data passing through it. See DLM 4000.25-4.
- What is a CSP?
Central Service Point. The person appointed by their respective Service/Agency as the principal custodian and manager of all of the records of that Service/Agency in the DoDAAD. They are responsible for updating and managing these records using the DoDAAD Update Application, and are usually involved in the DoDAAD PRC either as a member or participant. See DLM DLM 4000.25, volume 6, chapter2.
- What is a Monitor?
When situations arise whereby Services/Agencies determine that DoDAAD management be delegated below the CSP level, DoDAAD Monitors can be delegated by the CSP to allow for lower-level management within the service/agency. This is generally reserved for Services with large numbers of DoDAACs and/or frequent volatility of changes made to their DoDAACs. Monitor responsibilities are generally associated to a particular Major Command (MAJCOM). DoDAAD Monitors are responsible for maintaining DoDAACs/RICs delegated to them by their CSP. Like CSPs, DoDAAD Monitors are appointed in writing but by their CSP.
- What is the role of GSA when it comes to the DoDAAD?
GSA (Office of Supply Chain Management) serves as the CSP for all Federal Agencies. They represent the equities of the Federal Agencies at the DoDAAD PRC.
- What kind of records does the DoDAAD contain?
The DoDAAD is comprised of two types of records: Department of Defense Activity Address Code (DoDAAC) and Routing Identifier Code (RIC) identifiers.
- How is the DoDAAD constructed?
The DoDAAD consists of both 6-digit DoDAACs and 3-digit RICs which are used to identify activities. These activities are grouped by Series. A Series is the first, first and second, or first through third (or first and last) characters of the DoDAAC. Each Service or Agency who uses the DoDAAD is assigned one or several Series to use for creating records for their Service’s/Agency’s use. The DoDAAD Series Table lays out this structure. Subordinate to the Series is a second “tier” or subdivision of a Service/Agency known as the Major Command Code (MAJCOM -- a.k.a. Bureau Code). These 2-digit codes are not specific to a Series, but they are specific to a Service/Agency. For instance, the U.S. Navy has the Series of N, Q, R, and V DoDAACs. They have MAJCOMS that identify the subdivisions of the Navy. These MAJCOMs apply to all Navy DoDAACs, regardless of Series. So, for instance, a MAJCOM of “N0” (Naval Sea Systems Command) may be used for N, Q, R, and V DoDAACs as necessary. DoDAACs and RICS are comprised of various other data elements that form the pedigree of each type of record. See DLM 4000.25, volume 6, chapter2, DoDAAD Data Elements.
- What is the DoDAAD Series Table?
The DoDAAD Series Table identifies how the DoDAAD is subdivided by Series to the various stakeholder Services/Agencies who use the DoDAAD. Initial Series was limited to the first digit of the DoDAAD/RIC, using numbers to identify Federal Agencies, and letters to designate DoD. DoDAAC and RIC assignment is based on MILSTRIP Service and Agency (S/A) codes identified in DLM 4000.25-1, MILSTRIP, Appendix 2.2 - Service and Agency Codes; and DLM 4000.25 Volume 2, Appendix 7.2. Over time, expansion required developing Series logic beyond just the first character. To provide for expansion for additional agencies that require DoDAACs beyond those identified in MILSTRIP, the DoDAAD Series Table further stratifies S/A codes for use in creating additional DoDAAD Series for Services/Agencies. See DLM 4000.25, volume 6, chapter2, DoDAAD Series Table.
- What is a DoDAAC?
The Department of Defense Activity Address Code (DoDAAC) is a six-position code that uniquely identifies a unit, activity, or organization that has the authority to requisition, contract for, receive, have custody of, issue, or ship government-owned assets, or fund/pay bills for materials and/or services. The first positions of the code designate the particular Service/Agency element of ownership. These codes are particularly important for U.S. Government financial, contracting, and auditing records. The codes are used across the entire Federal Government when ordering supplies from the supply system using MILSTRIP, FEDSTRIP, or DLMS procedures; and for all contracts and orders. When assigned for activities outside the Department of Defense, the codes are often referred to as AACs. The code is comprised of different types of address information and other codes which are instrumental in facilitating business processes. See DLM 4000.25, volume 6, chapter2.
- What is a DoDAAC used for?
A DoDAAC is the business standard code used to identify an activity within DoD and Federal Agency business systems that span all functional domains of procurement/acquisition, financial management and accounting, supply, property, maintenance, transportation, readiness, human resources, etc. See DLM 4000.25, volume 6, Chapter 2.
- What is an AAC?
An Activity Address Code is a generic term used to identify any code used for addressing but that is not found within the DoDAAD. It is also a term commonly used to identify DoDAACs used by Federal Agencies.
- What is a RIC?
The RIC is a 3-character, alpha-numeric code that uniquely identifies a unit, activity, or organization that requires system ability to route transactions or receive transactions routed to it (e.g., a source of supply) within logistics and financial business systems using DLMS and legacy 80 record position format transactions. The RIC was originally conceived as an abbreviated form of a seven-character Communication Routing Identifier (COMMRI). The first position designates the particular service/agency ownership, the second and third characters are determined by the Central Service Point (CSP).
- What is a RIC used for?
The RIC was intended to be used for the routing of MILS transactions within a nodal system. The RIC was supposed to identify the specific node in this system to which transactions would be routed to/from. Each RIC, in turn, is supposed to associate to a DoDAAC which is what actually identifies the activity for which the RIC facilitates routing to/from the activity. The RIC is not intended to identify an activity or any functional use other than MILS routing.
- What’s the difference between a DoDAAC and a RIC?
A RIC only associates to a single DoDAAC, but a DoDAAC can be associated to one or several RICs. This is because the RIC is a routing mechanism, and does not necessarily convey identity of or as an activity. That is the purpose of the DoDAAC.
- What is a UIC?
The Unit Identification Code is a six-character code created by the DoD Components to identify an activity in manpower and readiness reporting systems. Prior to the advent of the DoDAAC (circa 1960), the UIC was a five-digit code used for financial resources, readiness, and manpower. To enable Joint Services interoperability, the code was changed to 6-characters; however, certain Services and systems maintained use of the 5-character construct (Navy). The Office of the Under Secretary of Defense for Personnel and Readiness (OUSD P&R) is the DoD “owner” of the UIC. The database that contains all DoD UICs is the Unit Identification Code Search System (UICSS) which is administered by the Defense Manpower Data Center (DMDC) of the Defense Human Resource Activity (DHRA). This system obtains data from the Components’ manpower systems. The Army uses the 6-digit UIC. Navy uses a 5-digit UIC and applies an “N” to the beginning of their codes. Air Force uses the Personnel Accounting System (PAS), and the Marine Corps uses the Reporting Unit Code (RUC) for personnel reporting, and the UIC for reporting of structure requirements. Currently, however, the Marine Corps system that provides data to UICSS is the Marine Corps Total Force System (MCTFS) which provides the RUC information. Depending on the Service’s internal business processes, this field should be populated with the appropriate UIC to which the DoDAAC is associated, as applicable.
- What is the difference between a DoDAAC and a UIC?
A DoDAAC facilitates business processes across all functional domains and is uniquely associated to the expenditure, distribution, and accounting of resources (i.e., property, goods, services, and funds); whereas, a UIC primarily serves as an identity code, specifically for use in manpower and personnel systems of the DoD.
- What is an activity?
An activity is any unit, office, organization, facility, or other entity which conducts business processes involving Government resources and for which a DoDAAC is necessary in order for that entity to have an identity in the systems used to facilitate these business processes.
- What is a unit?
- What is an office?
- What is a CAGE Code?
A Commercial and Government Entity (CAGE) Code is a 5-digit code used to identify either a Commercial or Government entity within the CAGE System for business processes associated with acquisition, primarily as a means of codifying certain aspects of acquisition lifecycle pedigree of a new acquisition program element in the cataloging process. Since the cataloging of an item requires identification of certain long-standing data (like original manufacturer or engineering drawings, etc.) the CAGE Code is used to identify these entities associated with this part of the acquisition process. The CAGE Code is not intended to be used as a code for conducting business processes that involving resources which are facilitated by the DoDAAC (i.e., addressing, billing, payment, shipping, receiving, supply and property, financial management and accounting, contracting, etc.).
- What is a DUNS Number?
The Dunn and Bradstreet Data Universal Numbering System (DUNS) Number is a nine-digit number created within the proprietary and privately-owned DUNS System to identify a business entity (private or public). Ordinarily, DUNS numbers are used by the private sector, but are also used by certain Federal entities as well. The DoD does not use DUNS Numbers, but instead uses the DoDAAC, and where a nine-digit construct is necessary in certain systems, a prefix of “DOD” is added to the DoDAAC to fulfill the nine-digit requirement of a DUNS. See BPN.
- What is a Business Partner Number?
The Business Partner Number (BPN) is a nine-digit number created by adding the prefix of “DOD” to a DoDAAC. This term is synonymous with Trading Partner Number.
- What is a Trading Partner Number?
- How do I tell the difference between a Federal activity, a DoD activity, a State activity, and a Contractor?
The Series of a DoDAAC identifies the various types of activities, and where necessary, the DoDAAC Assignment Logic is also instrumental in identifying additional characteristics of activities. For instance, any DoDAAC beginning with a number in the first two positions of the code is a Federal activity. Any DoDAAC beginning with a number and a letter in the first two positions is a State or local entity activity. Any DoDAAC beginning with a letter is a DoD activity, but DoD contractors are identified by only certain letters or letter combinations, as identified in the DoDAAD Series Table. Currently, there is no Series or construct for identifying Federal contractors.
- How are DoDAACs used?
DoDAACs are generally used to construct a business event transaction. The most common of these are the Procurement Instrument Identifier (PIID), the standard document number, the MILS document number, or the Transportation Control Number. All of these business event identifiers begin with a DoDAAC. DoDAACs are also used in systems to identify owners of property and/or classes of Supply. They are used to identify activities for billing and payment. Additionally, DoDAACs are used for identifying shippers and receivers across the distribution pipeline. In some instances, DoDAACs are used to identify readiness equities, equipment sets, employer identification, etc. The use of the DoDAAC is always expanding.
- How do I get a DoDAAC or update an existing one?
The Central Service Points (CSPs) are the only people authorized to create, update and/or assign a DoDAAC. Based on you organization type there are different means to obtain a DoDAAC:
- Military or Government Service/Agency employees, contact your Central Service Point (CSP) or local DoDAAC Monitor at your location to have a DoDAAC assigned. If a DoDAAC Monitor does not exist at your Service/Agency, you may look up the CSP for your Servcie/Agency: http://www.dla.mil/HQ/InformationOperations/DLMS/allpoc/. Requests for new DoDAAC or modification to an existing DoDAAC must allow for processing by the CSP in order to be implemented in time for its intended use (e.g. requisitioning, shipping, billing, etc.).
- Private organizations (e.g., contractors) contact the Service/Agency with whom you have a contract. That Service/Agency will determine if you are eligible and assign a DoDAAC (if eligibility requirements are met). Contractor DoDAACs are only issued for the length of the contract. When the contract expires, the DoDAAC will be deleted (inactivated). If you contract is extended, you must contact your contract officer. Only a warranted contracting officer can request a DoDAAC change.
- How do I look up a DoDAAC?
There are two methods of looking up a DoDAAC. If the DoDAAC is known, there is a public access site at: https://www.transactionservices.dla.mil/daasinq. There is also a search site available, but it requires a System Access Request (SAR) to use. The application name is eDAASINQ and the SAR can be made from DLA Transaction Services at: https://www.transactionservices.dla.mil/sar/.
- What are Authority Codes?
Authority codes have been established to restrict requisitioning, shipment, and billing by DoDAAC. DoDAAC authority codes are applicable to all Services. Initially, DLA Transaction Services will assign Authority Code "00" (full authority to requisition, ship-to and bill-to) to all DoDAACs, unless a more restrictive code is already known for a DoDAAC, based upon existing DAAS edits. Following initial implementation, CSPs will update DoDAAC authority codes, as appropriate, and will assign authority codes to all new DoDAACs. Types of authority codes are listed in DLM 4000.25, volume 6, chapter2 of the DLMS manual.
- How can I learn more about the DODAAD?
Go to: DLM 4000.25, volume 6, chapter2; and DLMS Training module #8, DODAAD.
- I am trying to access the DoDAAC Central Service Point (CSP) file on your website but am unable to open the file/document. How can I access or obtain a copy of the file/document?
The reason you are unable to access the file/document is probably because you do not have a DoD-approved Public Key Infrastructure (PKI) certificate or an Enterprise Certificate Authority (ECA) certificate issued by a source that the DLA information technology infrastructure accepts. If you are still unable to access the CSP file/document you should contact us via the website by clicking the aforementioned email link. To provide updates to this file, contact Defense Logistics Management Standards Office. For information on how to obtain a PKI certificate go to: DLMS PKI Page.
- Where can I find the Country Code listing on your website?
The list can be found on the DoDAAD Committee page.
- Why can't I fill in the Contractor fields for my DoDAAC?
Contractors DoDAACs can be assigned by setting the Contractor Flag in the DoDAAC to "Yes." If the DoDAAC is assigned to a Contractor, the Contract Information fields are all required. For all other DoDAACs these fields are disabled.
- How do you obtain an NSN to sell products to the DoD?
Contact the Defense Logistics Information Service at firstname.lastname@example.org, or 877-DLA-CALL. You may find this site helpful: https://www.logisticsinformationservice.dla.mil/.
- I see from your website that you have links to many publications. I am unable to find a publication I need for research or other business. Where can I find a copy of the authoritative source?
Our website hosts the DLM 4000.25 series publications; we do have links to publications that are referenced in those publications. Those links are to the authoritative source when possible. Most Department of Defense publications can be found at: http://www.dtic.mil/whs/directives/.
Web Supply Discrepancy Reporting (SDR)
- Who should I contact for trouble receiving responses to SDRs?
Your problem is most likely related to the DoD WebSDR application and it may be reported to the DLA Transaction Services Help Desk at DSN 986.3247, commercial (937)656.3247, or via email: email@example.com. However, DLA Transaction Services Help Desk does not provide functional SDR support. If your SDR was submitted to DLA you may contact the DLA Customer Interaction Center (CIC). It is available to take your call 24 hours a day, 7 days a week. You can also contact the CIC at 1.877.352.2255 (1.877.DLA.CALL) or DSN 331.7766, or email: firstname.lastname@example.org. Otherwise, contact the Military Service Source of Supply.
- How do I access the WebSDR application?
Go to the DLA Transaction Services web page <a href="https://www.transactionservices.dla.mil/daashome/services.asp" title="Defense Automatic Addressing Systems Center services, Web Supply Discrepancy Reporting" target="_blank">https://www.transactionservices.dla.mil/daashome/services.asp where you can request the location of the WebSDR application. Access to WebSDR requires submission of a system access request (SAR), which may be submitted at any time via DLA Transaction Services at https://www.transactionservices.dla.mil/daashome/.
- Is training available for Web SDR?
Yes. Training for Web SDR can be found on our website at: http://www.dla.mil/eApplications/Training/training.asp
- How does DoD Web SDR impact the manual SDR Process?
DoD WebSDR refers to both DLA Transaction Services-maintained web-entry application and the automated process that facilitates SDR information exchange using DLMS transactions, email, and interfaces with Component SDR systems. The procedures for processing SDRs under WebSDR are located in the DLMS Manual, Volume 2, Chapter 17.
- Where can I find a printer-friendly list of the codes with their explanation used in the SDR process?
All SDR-related codes used in the DLMS process are identified in the DED/D. In addition, a consolidated list is available on the SDR Committee page.
Logistics Data Resource Management System (LOGDRMS)
- What is the DoD Logistics Data Resource Management System (LOGDRMS)?
The LOGDRMS is a web-enabled automated data base which contains a dictionary/directory of all logistics data elements used in the DLMS, an abbreviated set of 67 DLMS Implementation Conventions (DS's), a separate Dictionary/Directory of reference tables (DLMS Qualifiers) used in the DLMS supplements , and a set of conversion/cross-reference tables from DLSS to DLMS (e.g., MILSTRIP A0_ to 511R Requisition).
- DLMS supply transactions employ many reference tables. Where can I find a list of the tables?
The DLMS reference tables (also known as DLMS Qualifiers) are published in the DLMS Manual (DLM 4000.25). They are also listed on the eApplications web page in qualifier code and alphabetic sequences. There are 197 tables used in the DLMS. All tables are available on the Defense Logistics Management Standards Office website and are linked to the specific location(s) within each DLMS Supplement (ANSI ASC X12 implementation convention). These tables can be found at: LOGDRMS tables.
- What is the DLMS Data Element Dictionary/Directory (DED/D) and what does it do?
The DED/D is the central repository for all DLMS-related data elements. It is designed to accommodate the current Logistics business rules and is fully attributed. It consists of a logistics enterprise DED/D (e.g., calendar date), a DED/D of DLMS data elements representing a specific use of an enterprise data element (e.g., calendar date of shipment), and the location(s) of each data element within each DLMS Supplement (DLMS IC) (X12 implementation convention). A link to any applicable reference table (DLMS qualifier) is also provided. The web-based query includes an application that enables system users to access data elements stored in the DED/D at enterprise or DLMS management levels. An added feature provides a query capability for all DLMS data elements by the DS's ANSI ASC X12 version release (e.g., 004010 511R) which then produces a report of all logistics business data elements contained in that DS, with each data element identified by location therein.
- Where can I find the DoD code values for "Unit of Issue/Measure" and matching ANSI ASC X12 codes?
Go to "QUICK LINKS" on the Defense Logistics Management Standards home page and click on DLMS/ANSI ASC Conversion Guides. Codes are presented in 3 sequences: clear text name; DoD Code; and ANSI ASC X12 Code.
- Where can I find a DoD Logistics Document Identifier (e.g., A01) to DLMS Supplement (Implementation Convention e.g., 511R) cross-reference table?
Go to "QUICK LINKS" on the Defense Logistics Management Standards home page and click on "DLSS/DoD Cross Reference Tables". Cross references are in 2 sequenced tables, DOCID and DLMS Supplement (IC).
- Who establishes the DLMS standards for transportation?
The United States Transportation Command is the Executive Agent for transportation data and transaction standards. The Defense Transportation Electronic Business (DTEB) Committee identifies and resolves issues and recommends management actions that support the accelerated implementation of the electronic exchange of business information. As the focal point for all defense transportation e-business development efforts, it coordinates e-business standards and requirements with defense and federal organization and commercial industry. The committee represents transportation interests at all levels of the federal government.
- Where do I find information on transportation DLMS?
The DTEB website is located at http://www.transcom.mil/cmd/associated/dteb/. Just sign in as "guest", then proceed to the DoD Transportation implementation conventions (ICs) hyperlink. The transportation regulation can be found at: http://www.transcom.mil/dtr/dtrp2.cfm.
- When did the Office of the Secretary of Defense mandate that systems interfacing with other systems use the Defense Logistics Military Standards (DLMS)?
(Note that none of the below policy issuances set a drop dead implementation date. The policy in each were effective upon signature with the presumption that DoD Components would implement expeditiously.)
- December 9, 1998: The DoD goal to adopt and implement commercially based transactional interfaces among DoD business systems was first stated in DoD Initiative Directive (DRID) #48 – “Adoption of Commercial EDI Standards for DoD Logistics Business Transactions,” signed December 9, 1998. DRID stated that the new information exchanges be based on the American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12 commercial electronic data interchange (EDI) standards in lieu of current proprietary DoD logistics information exchange standards.
- May 5, 2000: The goal established by DRID #48 was formally codified into DoD policy with the issuance of DOD Directive 8190.1, “DoD Logistics Use of Electronic Data Interchange (EDI) Standards.” The Directive stated that the DLMS is the basis for new, replacement, and major modifications to logistics business systems.
- January 5, 2015: DODD 8190.1 was updated retitled and reissued as DODD 8190.01E, “Defense Logistics Management Standards (DLMS).
The policy continues to state that:
- DLMS is the DoD standard for electronic data interchange (EDI) (transactional information exchanges) among the AISs that comprise assigned business processes of the global supply chain management system.
- The American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12 is the baseline standard that supports the DLMS transactional information exchanges.
- DoD Component heads shall support the DLMS change management process uniformly implement the DLMS in all AISs that perform business functions that support the global supply chain management, use the services of the DLMS global services providers, and use DLMS for ASC X12 transactions with contractors in accordance with the Federal Acquisition Regulation.
- What established December 31, 2019 as the DLMS implementation date?
- February 2013: The OSD Acquisition & Logistics Functional Business Strategy issued in February 2013 established 2019 as the target implementation date for the DLMS enterprise standard stating that “…most Logistics transactions use DLMS. Full compliance is required by 2019” in the required date column of page 38.
- The USD AT&L approved Acquisition & Logistics Functional Strategy was published as a FOUO PowerPoint presentation. The lack of a signature does not diminish its authority.
- Officials from the Deputy Assistant Secretary of Defense for Supply Chain Integration Office have on numerous occasion in several forums clarified the 2019 date to specifically be December 31, 2019. They further identified that full compliance means implementation of the approved DLMS changes (ADCs) that are essential to support the initiatives and goals identified within the A&L Functional Strategy.
- The A&L Functional Strategy is part of a process required by Title 10 U.S.C. Section 2222 which specifies the review and certification process that Defense Business Systems (DBSs) must undergo before funds can be obligated. To implement the review and certification process the Office of the Deputy Chief Management Officer published Guidance for Review and Certification of Defense Business Systems. The review and certification process begins with the DoD Strategic Management Plan (SMP) from which the business domains develop their respective Functional Strategy documents that identify their initiations to meet the goals of the SMP. The A&L Functional Strategy addresses the A&L initiatives supporting the SMP and the Components must develop and execute Organizational Execution Plans (OEPs) that support the functional strategy initiatives.
- Will DAAS stop supporting (accepting, translating and routing) the legacy 80 character MILS transactions after December 31, 2019?
- Absolutely not, Transactions Services will continue to ensure that every DoD system in the supply chain is able to continue to support its customers.
- There are also MILS transaction dependent systems outside of DoD (e.g., FMS country representatives) interfacing with DoD systems that will likely require continued Transactions Services translation and mapping support between the DLMS and legacy MILS.
- There seems to be a disconnect between DLMS and the FLIS. Is the FLIS system still used when it comes to NSNs with their unit of issue or is DLMS converting them to whatever? So is MILSTRIP no longer?
- The problem you point out is due to the fact that the information exchange standard that underpins the DLMS is the American National Standards Institute (ANSI) Accredited Standards Committee (ASC) X12. That standard requires that transactions transmitted between system must contain codes published by ANSI ASC X12 in three instances; Unit of Measure which is one you are concerned with, Mode of Transportation, and Unit Pack. In each of those three code structures the values that DoD uses internal to its systems (also used by GSA in its DLMS implementation and former FEDSTRIP) are different than those ANSI ASC X12 requires by used in its transaction sets. Therefore, in the case of unit of measure DoD's unit of issue code values are maintained within the FLIS as you said and those are the codes used within DoD and GSA systems. However, in order for DLMS transactions to process correctly a sending system needs to convert the DoD code values to the ANSI code values prior to sending; likewise on the inbound side DLMS transactions received by a system must convert the ANSI code values back to the DoD/FLIS values. This process is explained in charts 38 through 41 of the DLMS Module Training slides, note that the slide have notes. The DLMS Training slides can be found at DLMS Training Page The conversion tables that you need can be found at DLMS ANSI Conversion Guides