An official website of the United States government
A .mil website belongs to an official U.S. Department of Defense organization in the United States.
A lock (lock ) or https:// means you’ve safely connected to the .mil website. Share sensitive information only on official, secure websites.

Aug. 6, 2026

July Activities

DEDSO Activity Report July 2026
Volume 3 Issue 7

Top Priorities This Month (BLUF)

This month, the Defense Enterprise Data Standards Office (DEDSO) prioritized digital architecture alignment, financial audit readiness, and system interoperability to accelerate the Department of War's (DoW) logistics modernization and strengthen IT governance. Key achievements include spearheading the F-35 Autonomic Logistics Information System (ALIS) integration with core DLMS transaction sets to secure statutory financial audit readiness, launching a comprehensive cleanup of our public-facing technical baselines to eliminate legacy technical debt, and resolving critical financial data gaps with FedMall MOES to ensure seamless Treasury G-Invoicing. Additionally, DEDSO worked closely with Joint Service and Agency partners to standardize 940R Materiel Release Order validation protocols and decommission obsolete data elements, establishing a clean, AI-ready transaction baseline designed to sustain operational excellence across the Joint Logistics Enterprise (JLEnt).

Industry & Vendor Impact

Are you a software vendor, system integrator, or enterprise systems manager designing logistics, supply chain, or property platforms for the Department of War? Pay close attention to these transaction and validation updates to prevent integration failures, ensure strict audit compliance, and align with new F-35 sustainment and G-Invoicing transaction standards.

  • F-35 ALIS to DLMS Transition (FY 2022 NDAA Sec 142 Compliance):

    • Context: In compliance with Section 142 of the FY 2022 NDAA, F-35 program management and sustainment are transitioning from commercial contractor-led structures to the Military Services. To establish a financially auditable baseline and achieve Financial Improvement and Audit Readiness (FIAR) compliance, the Enterprise Logistics Management System (ELMS) has been designated as the official F-35 Accountable Property System of Record (APSR).

    • System Impact: This transition requires F-35 ALIS to align with eight core DLMS transaction sets. Systems must integrate mapped data elements and standard DLMS X12 qualifiers to enable direct, secure transactional pipelines to ELMS and Component architectures. Recent technical walkthroughs successfully validated the proposed DLMS data mapping on sample 511R Requisition transactions, demonstrating seamless system execution.

  • FedMall MOES G-Invoicing and Financial Data Gaps:

    • Context: FedMall Material Order Entry System (MOES) legacy infrastructure cannot transmit Treasury G-Invoicing data or send DLMS transactions. This breaks downstream invoicing, forcing DFAS to process accounting entries manually and preventing the creation of compliant 7600EZ invoices.

    • System Impact: To bypass legacy MOES limitations, systems must capture and transmit 8 critical financial data elements required by Treasury and 24 secondary data elements required to support front-end ordering systems. Joint working groups are currently engineering technical workarounds to restore automated end-to-end transaction fluidity.

  • 940R MRO XML Validation Mismatch:

    • Context: Modernized XML formats enforce rigid structural compliance with established Implementation Conventions (ICs), causing critical XML transactions to fail within DAAS due to strict schema validation policies, whereas legacy EDI X12 transactions operate under minimal validation rules.

    • System Impact: To prevent material release disruptions, DEDSO is establishing a standardized segment qualifier for both the Header and Detail sections of the 940R MRO transaction. This dual-compatible solution allows legacy X12 traffic to continue processing while enabling modernized platforms to transmit XML transactions successfully. Systems must prepare to ingest these updated 940R MRO IC schemas.

  • Modernizing DLM 4000.25 Chapter 16 and Decommissioning Obsolete Data Elements:

    • Context: Recent warehousing modernization within DLA has rendered several legacy data elements obsolete. Despite serving no valid operational purpose, they continue to be transmitted and maintained.

    • System Impact: In collaboration with DLA Disposition Services, J6 EBS, and WMS, DEDSO is updating Volume 2, Chapter 16 of DLM 4000.25 to omit these non-essential elements, eliminating unnecessary database overhead and building a clean, high-quality data foundation primed for advanced AI integration.

Future Initiatives & Pilots

  • Technical Baseline Alignment (ADC Evaluation and Reconciliation):

    • Scope: To eliminate legacy technical debt and improve IT audit readiness, DEDSO has initiated a comprehensive review of all public-facing Approved DLMS Changes (ADCs) to identify directives that are obsolete, superseded, or no longer operationally active.

    • Upcoming Modernization: DEDSO will collaborate with DAAS and participating Components to review current system logic, determining which approved changes remain active versus those that must be formally withdrawn. This will reduce unnecessary programming, accelerate software development, and yield enterprise cost savings.

  • MOES SMS Order Routing & Alternative Technical Pathways:

    • Scope: Resolving G-Invoicing pipeline breaks on legacy MOES infrastructure.

    • Upcoming Modernization: DEDSO and DAAS will analyze a requested two-week order pull to determine the exact percentage of orders routed to SMS to scale the integration workaround and finalize alternative technical pathways to bypass legacy MOES limitations.

Approved DLMS Changes (ADCs) & Required Actions

  • Change: ADC 1492 - Mandatory Use of Advanced Shipment Notice (Supply/SDR) (Signed 7/30/2026)

    • Who is Impacted: Inventory Control Points (ICPs), shipping activities, storage activities (distribution centers), and systems processing shipment and receipt transactions (including ELMS, EBS, DSS/WMS, and Component APSRs).

    • Action Required / What Changed: Mandates the use of Advanced Shipment Notices (ASNs) and Pre-Positioned Materiel Receipts (PMRs) prior to physical delivery to remediate tracking deficiencies identified under NFR FIN-2023-WCF-082. Under the new policy, missing ASNs or PMRs will trigger Supply Discrepancy Reports (SDRs) and cause stock to be suspended at goods receipt. This change also integrates new "Owner" (OW) and "SDR Control Number" (NN) qualifiers across core DLMS transactions to secure end-to-end traceibility. Full implementation is required within five years.

    • Points of Contact: Dr. Gail Fuller and Corbin Austin at DEDSO.Supply@dla.mil.

  • Change: ADC 1531 - Quarterly Memorandum for Record Administrative Updates (Signed 7/31/2026)

    • Who is Impacted: All DLMS users, particularly cataloging, warehousing, and transactional system developers.

    • Action Required / What Changed: Implements routine administrative updates, clarifications, and corrections to the DLM 4000.25 manuals and DLMS ICs (including updates to 832N, 856P, 888M/N, 940R, and 945A). Key updates include standardizing terminology to "Advanced Shipment Notice" and clarifying DEDSO's policy to maintain only the most current version of DLMS ICs on its official website. This change is effective immediately and requires no action from Components.

    • Point of Contact: Bao Nguyen at DEDSOData@dla.mil.

Recent Engagements & Working Groups

  • 940R MRO Interoperability Resolution Meeting: DEDSO, DAAS, the U.S. Army, and Lockheed Martin convened to resolve critical system interoperability failures within the 940R Materiel Release Order (MRO) transaction and historical data exchanges, establishing the dual-compatible Header/Detail segment qualifier.

  • Supply & Finance Joint Working Groups: DEDSO Finance and Supply launched joint working groups with DLA J8, FedMall MOES, and DAAS to resolve G-Invoicing transmission failures on legacy MOES infrastructure.

  • DLM 4000.25 Chapter 16 Modernization Working Group: DEDSO Supply Team, DLA Disposition Services, J6 EBS, and WMS established a working group to review data usage and decommission obsolete data elements from Volume 2, Chapter 16 of DLM 4000.25.

  • F-35 G-ICP Integration Technical Walkthrough: On June 26, DEDSO and OUSD conducted a joint technical walkthrough with Navy and Air Force lead representatives to evaluate a sample 511R Requisition transaction and validate standard DLMS data mapping.

Upcoming Engagements & Training

  • Upcoming DLMS Training Events:

    • Scope: Interactive training sessions on DLMS basics, audit compliance, and transaction structure are scheduled regularly.

    • Action: See the full 2026 schedule, download materials, and register for upcoming sessions here or contact coordinators at DEDSO.Website@dla.mil.

  • Committee Meetings & Process Review Breakouts:

    • Scope: Stay informed about process review committees and technical collaboration spaces.

    • Action: Access schedules and contact details here.

  • Proposed DLMS Changes (PDCs):

    • Scope: Review and comment on PDCs currently in development or coordination.

    • Action: Track active process changes and submit feedback here.

Rationale for Data Exclusions

The following highly detailed, technical data rows from the source documents were deliberately excluded from this scaled-back version of the newsletter to ensure the content remains readable, high-level, and perfectly suited for a general newsletter format:

  • Suspension & Discrepancy Matrix Tables (Tables 1, 2, C17.T1, C17.T2 from ADC 1492): Highly technical tables mapping out exact SDR discrepancy codes (Z3, U15, Z9, N/A) against specific combinations of serial and non-serially managed items were synthesized into a concise narrative.

  • Transaction segment details (from both ADC 1492 and ADC 1531): Deep technical mapping specifications (such as 2/N901/30, 2/N101/1100, 2/LQ01/3400 qualifiers, and specific data repository numbers like DRN 08010810) were omitted to prioritize reader comprehension over raw programming details.

  • Component-by-Component list of impacted systems: A multi-page list identifying dozens of individual automated information systems (AIS) and their respective DoD IT Portfolio repository numbers (e.g., eRMS, NERP, ORCAS, TICMS, etc.) was summarized as "all DoW Components and systems processing shipment/receipt transactions."