This amendment to DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 1, May 19, 2014, is being posted at the direction of the Deputy Assistant Secretary of Defense for Logistics under the authority of DoD Instruction (DoDI DoD Supply Chain Materiel Management Policy, December 14, 2011. This change to DLM 4000.25, Defense Logistics Management Standards (DLMS), Volume 1, May 2014, is being published at the direction of the Deputy Assistant Secretary of Defense for Logistics under the authority of DoD Instruction (DoDI DoD Supply Chain Equipment Management Policy,” December 14, 2011.
DEFENSE LOGISTICS MANAGEMENT SYSTEM
CONCEPTS AND PROCEDURES
CONCEPTS AND PROCEDURES PROCESS CHANGE HISTORY
Corrected the DLMS Unit of Material Measure (Unit of Issue/Purchase Unit) Conversion Guide name descriptions for Fahrenheit, Kelvin, Us,. Update the DLMS unit of materiel measure (unit of issue/unit of purchase) conversion guide to add actual tons and the corresponding X12 code 51 and DOD code 51.
Implementation of New DLMS 841W Hazardous Material/Hazardous
CONCEPTS AND PROCEDURES
C1. CHAPTER 1
INTRODUCTION
Ensure ongoing liaison with the DLMS PRC Chair and with other DoD components and participating external organizations. Conduct the initial evaluation of all beneficial proposals to the DLMS originating within the DoD component or participating external organization.
C2. CHAPTER 2
BUSINESS CONCEPTS AND ENVIRONMENTS
DLMS Code Lists/Qualifiers used to identify DoD functional data elements in the DLMS ICs are described in Appendix 6. Transaction set syntax and content will conform to ANSI ASC X12.6 standards and the DLMS implementation conventions defined therein.
C3. CHAPTER 3
CHANGE MANAGEMENT
Once the Proposing Organization and the DLMS PRC Chair agree on the PDC content, the PRC Chair will release the PDC to the DoD Component PRC Members for coordination. If the PRC approves the PDC, the PRC Chair will set an implementation date by consensus.
C4. CHAPTER 4
FUNCTIONAL APPLICATION ERRORS
DAAS uses DLMS 824R, Advice Rejection Transaction, to report the error to the originating activity, which must correct and retransmit the transaction. The activity that receives a transaction from DAAS uses DLMS 824R to report an error back to DAAS. Instead, DAAS will route transaction DLMS 824R to the identified Message-To addressee without further processing.
The DR Direct Action Code in data element 1/BGN08/020 of Transaction DLMS 824R Reject Advice identifies this rejection process. Action Code 80 Reconciliation in data element 1/BGN08/020 of DLMS Advice Rejection Transaction 824R identifies this planned improvement. If a DoD Component application program cannot process a received transaction, it will send a transaction DLMS 824R, Reject advice back to the send activity.
C5. CHAPTER 5
DLMS DATA MANAGEMENT
Approved data element changes are presented in LOGDRMS on the implementation date identified in the ADC. The Office of Enterprise Business Standards is the DoD Executive Agent for logistics data exchange and is responsible for change management concerns and technical issues related to the implementation of DLMS Data Elements and information exchanges as defined by the Manual of Defense Logistics (DLM) 4000.25. Some DLMS data elements have explicit business rules and/or code values that specify their use in a business transaction.
Although it is preferable for DLMS data elements to use terms commonly used by subject matter experts, reuse of an existing DLMS element with the same semantic meaning may be preferred in the interest of interoperability. The creation of a core data element occurs when an Approved DLMS-ADC adds a new DLMS data element that does not represent a context-specific version of an existing core element. When ADCs include mapping of DLMS elements to X12 structures in the DLMS ICs, LOGDRMS is updated to reflect the use of X12 data elements.
C6. CHAPTER 6
STANDARDS AND CONVENTIONS
The Transaction Set Identifier Code (ST01) is the first data element of the transaction set header segment. Optional (O) The designation of optional means that there is no syntactic requirement for the presence of the data element within the segment or composite data structure. If any specified data element is present, all the specified data elements must be present.
However, any or all data elements not specified as the first in the condition may occur when the first is not present. If the first specified data element is present, then at least one of the remaining specified data elements must be present. DoD has identified a number of special characters as valid for use in specific DoD data values, (eg hyphen (-) and forward slash (/) are valid in a unique item identifier).
C7. CHAPTER 7
DEFENSE LOGISTICS MANAGEMENT STANDARDS USE OF ACCREDITED STANDARDS COMMITTEE X12
Sometimes the ASC X12 data element or code value name bears little resemblance to the commonly used DoD name for a piece of information. In addition, an ASC X12 data element or code value can be used as a migration code (C7.4.1.3) or local code (C7.4.1.4) to transfer DLMS-required data not otherwise specified by the standard. A "local code" is a code value that is not present in the current version/release and has not been fixed in a higher ASC X12 version/release.
A data maintenance action is being performed with ASC X12 to determine the code in a higher version/release. When a borrowed code is identified for DLMS use, Enterprise Business Standards Office will file an ASC X12 Data Maintenance (DM) action to establish a new qualification to be approved for use in a higher (future) ASC X12 version/release. Qualification values are selected from codes approved for use by ASC X12 in the version/release applicable to the DLMS IC.
C8. CHAPTER 8
MILITARY STANDARD SYSTEMS/DEFENSE
LOGISTICS MANAGEMENT STANDARDS MAPPING
Record position defines the start and end position of the data value in the data structure. The translation describes the conditions for mapping data between the MILS and DLMS formats. The DLMS section of the data map consists of three parts: DLMS data element, table, and update information.
The DLMS data element refers to the MILS field name (if any) and the MILS record position. In many cases the MILS record position will be "none" because the DLMS transaction is an extended/enhanced version of the old MILS transaction with 80 record positions. Components migrating to the DLMS must find the MILS format in the DLSS/DLMS cross-reference table.
C9. CHAPTER 9
LOGISTICS DATA RESOURCE MANAGEMENT SYSTEM
The core data element page (Figure C9.F3) will display the applicable core data element, associated DLMS data elements, and applicable domain data (data codes). For example, the basic data element “DoDAAC (DoD Address Code)” (Figure C9.F3.) shows the basic definition that underlies the use of DoDAAC with DLMS and related DLMS data elements (e.g., the results of a DLMS query will display a list of IC of DLMS in which the DLMS data element is used (Figure C9.F5.).
In Figure C9.F7. the DLMS Qualification page provides a way to browse or search for the DLMS managed code lists used in the DLMS-IC. Once a user clicks on "View" link in Figure C9.F14. click (eg "Commodity Code Qualifier"), the DLMS Simple Data Element Specifications will be displayed (Figure C9.F15.). Once a user clicks on "View" link in Figure C9.F16. click (eg "Composite Unit of Measure"), the DLMS Composite Data Element Specifications will be displayed (Figure C9.F17.).
AP1. APPENDIX 1
Document
Army Materiel Command Regulation (AMC-R) 700-99/Naval Supply Systems Command Instruction (NAVSUPINST) 4790.7/Air Force Logistics Command Regulation (AFLCR) 400-21/Marine Corps Order (MCO) ) P4410Goles.22, the Foreign Assistance Act of 1961, as amended, and the Arms Export Control Act of 1976, as amended.
AP2. APPENDIX 2
TERMS AND DEFINITIONS
Statement of amounts owed for the transfer or sale of material and for the provision of services related to the transfer. Clear ship-to address and/or activity designation identified by Military Assistance Program Address Code (MAPAC). At this account level, material billings are identified by a transaction number.
That portion of United States security assistance authorized by the Foreign Assistance Act of 1961, as amended, and the. A subgrouping of the total number of items in storage for physical inventory or record reconciliation purposes. A subgrouping of the total number of items in storage for physical inventory or record reconciliation purposes.
A DoD component, DoD activity, or non-DoD activity, if participating by special agreement (eg, Coast Guard), designated to receive, verify, and validate requests initiated by the Military Service and contractor-initiated for direct delivery to contractors of material sourced from the bulk supply system to support contracts or DD requirements. Specific examples of UII type are: Vehicle Identification Number (VIN), UII Construct I (UII 1), UII Construct 2 (UII 2).
AP3. APPENDIX 3
ACRONYMS AND ABBREVIATIONS
CONUS Continental United States COSIS Care of supplies in storage COTS Commercial-off-the-shelf. DIPEC Defense Industrial Plant Equipment Center DISA Data Interchange Standards Association DISA Defense Information Systems Agency DISN Defense Information Systems Network DLA Defense Logistics Agency. Defense Logistics Agency Instruction DLAI Defense Logistics Agency Regulation DLAR DLIS Defense Logistics Information Service Defense Logistics Manual DLM.
DoDAAC Department of Defense Activity Address Code DoDAAD Department of Defense Activity Address Directory DoDAAF Department of Defense Activity Address File DoDD Department of Defense Directive. Procurement Data Standards PDS Production Equipment Code PIC PIC Positive Inventory Control (USAF) PICA Primary Inventory Control Activity PICD Physical Inventory Cutoff Dates PICP Physical Inventory Control Program PICP Procurement Instrument Identifier PIID. USAMMA United States Army Medical Materiel Agency USASAC United States Army Security Assistance Center USCG United States Coast Guard.
AP4. APPENDIX 4
AP5. APPENDIX 5
DLMS TO DLSS CROSS-REFERENCE TABLES
AP6. APPENDIX 6
DEFENSE LOGISTICS MANAGEMENT STANDARDS CODE LISTS/QUALIFIERS
AP7. APPENDIX 7
DEFENSE LOGISTICS MANAGEMENT STANDARDS TRANSACTION FORMATS
AP8. APPENDIX 8
TRANSACTION SET 997 IMPLEMENTATION
CONVENTION – FUNCTIONAL ACKNOWLEDGEMENT
AP9. APPENDIX 9
DLMS CHANGE PROCESS FLOW CHART
AP10. APPENDIX 10
DEFENSE LOGISTICS MANAGEMENT STANDARDS COMPLIANCE
Requires the DoD components to implement the DLMS in all AISs performing business functions covered by the DLM 4000.25 series. The DLMS are included in the DoD BEA as a mandatory operating standard of the target operating environment of the DoD architecture. If the DLMS do not apply to the functional processes supported by the assessed system, there is no DLMS compliance.
Systems that are within the DLMS functional scope are those that support business functions covered by the DLM 4000.25 series of manuals. The system under audit may identify DLMS applicability for all or selected individual business processes supported by the DLMS. A review of the DLM 4000.25 series manuals "Tables of Contents" is a quick way to identify the specific business processes supported by the DLMS.
AP11. APPENDIX 11
OFFICIAL LETTER OF APPOINTMENT and SAMPLE OFFICIAL PDC RESPONSE MEMORANDUM
Official Letter of Appointment
XXXXXX
SAMPLE OFFICIAL PDC RESPONSE MEMORANDUM
DEFENSE LOGISTICS MANAGEMENT SYSTEM
SUPPLY STANDARDS AND PROCEDURES
June 13, 2012
Converts the four federal EDI Implementation Conventions (ICs) to DLMS ICs and republishes them in the DLMS IC section of the EBSO website. Adds purpose and ownership codes to the DLMS 180M Materiel Returns Reporting Implementation Convention (IC) to support the Navy's requirement to include this information for Security Risk Category (SRC) I and II requirements. Adds a project code data element to the DLMS 846R location reconciliation request transaction to provide stratification.
Updates the DLA and component distribution processes to allow the SDR process to be used to request a reversal of receipt in response to an acknowledgment of receipt and associated SDR submitted to the wrong owner. On 18 April 2017, the SCESC agreed to transfer the chairmanship of the JSA/LWCG from the Enterprise Business Standards Office to the Army. There are no additional changes to DLMS procedures or transactions defined in ADC 1161, which updated DLMS procedures to accommodate the PIID numbering system.
