Per ELMS PMO request, breaking out SCR requirement further. Currently the system is not capable of identifying which stock numbers require an authorization. Additionally a new role will need to be created to restrict User access for this new capability that will be centrally managed.

Create a new process that allows the DAF to identify which stock numbers require a FSM authorization. Additionally require a new user role to restrict user access to the capability as the responsibility for this new role will be managed by a centralized office. See attached document for additional information and specific details on how the new process should be executed.

Current policy in DAFMAN 23-300 identifies only certain stock numbers require an authorization. However,  how this requirement is determined is based on a DAF specific data element or the functional communities requirement.

Per ELMS PMO, resubmitting requirement to breakout SCR even further.  Currently the system does not have the capability to associate FSM authorizations to property records that is restricted by user role. The new process requirement to associate authorizations to a property record to enable the DAF to provide visibility of unit posture to help enable readiness reporting at the lowest level.  

Establish a new role to restrict user access for new process to associate FSM authorizations to the property record. Establish new process to associate authorizations to the property record for readiness reporting. Additional information regarding the new process and specific details for the process.

CJCSI 3401.01E, DAFMAN 23-300, and AFI 10-201

ELMS requires a compliant, integrated SDR capability to support the complete SDR lifecycle. The attached SDR requirements matrix and process flows identify required functionality for reportability determination, SDR case creation, discrepancy coding, requested action coding, mandatory field validation, attachments, DLMS 842A/W generation, DAAS transmission, WebSDR control-number capture, DLMS 842A/R response processing, follow-up processing, financial adjustment tracking, audit history, and final closure. Without this capability, SDR processing would rely on manual or external processes that do not provide complete lifecycle control, transaction traceability, or audit-ready evidence.
The attached SDR artifacts define three related process areas: SDR Generation, SDR Response, and SDR Follow-Up. The requirements matrix contains developer-ready SHALL statements mapped to DLM 4000.25, Volume 2, Chapter 17 and Appendix 7.28. The flowchart package depicts the operational sequence for determining reportability, creating and validating SDRs, transmitting 842A/W transactions through DAAS, receiving 842A/R responses, monitoring open cases, generating authorized follow-ups, and closing cases only after final adjudication and required actions are complete.

Implement ELMS SDR functionality to create, validate, transmit, track, respond to, follow up on, financially monitor, audit, and close SDRs. The expected outcome is an audit-ready SDR capability that preserves source transaction links, code selections, remarks, attachments, DAAS/WebSDR acknowledgments, response history, follow-up history, financial adjustment status, final disposition, and closure records throughout the SDR lifecycle.
Implement the complete ELMS SDR Generation capability. ELMS shall determine reportability; route non-reportable discrepancies to authorized local correction; create unique SDR cases; link source transactions; capture discrepancy details; support Chapter 17 and Appendix 7.28 code families; validate discrepancy, document type, and requested action codes; require Z1 and 1Z explanations when applicable; capture mandatory document, shipment, procurement, remarks, attachment, and code-dependent data; validate all mandatory fields before release; generate and transmit original DLMS 842A/W transactions through DAAS; process DAAS/WebSDR acknowledgments; preserve WebSDR control numbers; maintain open cases during research; enforce role-based access; preserve data; and maintain immutable audit history. See attached requirements matrix for complete SDR-GEN, SDR-RSP, SDR-FU requirements statements and acceptance.

N/A

 

The three ELMS Supply Discrepancy Report (SDR) process flows define the end-to-end lifecycle of an SDR after its submission. Collectively, they establish how ELMS receives and processes SDR responses, maintains accountability throughout the adjudication process, and manages follow-up activities until final resolution. The flows ensure that all inbound and outbound transactions are validated, matched to the correct SDR, processed in accordance with DLM 4000.25, Volume 2, Chapter 17, and retained with a complete audit trail.

 

A Warehouse that contains multiple Owning DoDAACs and multiple Replenishment Info will generate a Replenishment Review for each Owning DoDAAC. For requisitions sent to the ICP from DoDAAC's without a funding line, we do not have the ability to adjust the Owning DoDAAC to the DoDAAC that includes TAC3(Billing information).

Add a drop‑down or search‑field that allows users to select a managed Owning DoDAAC of the Warehouse before approving a replenishment. This field should: Validate entries against the DLA authoritative DoDAAC list. Block approval if the selected DoDAAC is not ICP‑managed. Write the updated DoDAAC into the requisition record before routing to ICP. Preserve auditability by logging both the original and the updated DoDAAC.

N/A

USCG requires a mechanism to override the MAC valuations, such that all stock within a defined group defaults to the same price during issuance.

The catalog LIN/TAMCN screen should be utilized to allow for a default price to be applied to all stock numbers under the associated LINTAMCN grouping. In the LIN/TAMCN add and edit process add a field to the draw for Average Price (feel free to update this). When issuing gear if the stock number is assigned to a LIN/TAMCN with this field set then the price reflected in the process to match this value. If none is provided then the annual MAC will be utilized when available, otherwise default to the unit price. To facilitate quicker turn around on establishing these groups and prices the LIN/TAMCN process should also be updated to allow for the selection of multiple stock numbers to be associated to the LIN/TAMCN during or after the time it is established. This will prevent the catalogers from needing to assign the LIN/TAMCN to each stock number one at a time through the Stock Number AUD.

N/A

ELMS, the USSOCOM Accountable Property System of Record, can retrieve catalog data from from FLIS and AESIP and is unable to pull catalog data including Non-Standard SOF Control Numbers from the USSOCOM Special Operations Logistics Management System (SOLMAN). The inability to automatically feed the catalog data into ELMS as part of a feed from SOLMAN requires USSOCOM Cataloger personnel to manually input catalog data records manually into ELMS PA, ELMS warehouse, and to provide a data update to NSW for their use in the NSW Warehouse Logistics Program  

Implement a system change for ELMS to automatically ingest and regularly synchronize with the authoritative USSOCOM catalog resident in the SOLMAN system. This data will load across the USSOCOM ELMS Enterprise. Provide a shared data feed to the NSW Logistics Program (LP). For NSW, provide the feed in the manner of the current FLIS capability, do not ingest the catalog to the NSW LP automatically.
This will allow the USSOCOM catalogers to build the master record once in SOLMAN, eliminating the requirement to then add the record again to ELMS. This also allows NSW to always match the USSOCOM master records which allows for accurate transactions between the two LP's. For NSW, this will give their ELMS users the ability to manually add the records as they need them.  

N/A

IAW OSW and Department of the Air Force, the capitalization threshold for financial statements of General Equipment (GE) that are General Fund (GF) has increased and requires an update to the Capitalization threshold in ELMS

As directed by the SAF/FMF, update the GF threshold from $1M to $10M, the new threshold will be applied retroactively and will apply to all DAF purchased records regardless of when the asset was purchased. New threshold needs to be applied for all the DAF PA module Site -ids FH-AFHAF, DF-CDMO, DF-VEHS, FF-GEIT, FF-CIOGE, FL-AFTAC, FS-MPEEA, SF-SDA and DF-RDTE

IAW the memo issued by OSW Comptroller and at the direction of the SAF/FMF Capitalization thresholds for financial statements have been increased.

Within NECC, we are unable to utilize the MM/ICP module of DPAS to order via MILSTRIP. This leads us to utilizing RSUPPLY to release all requisitions and having to backfill ELMS WM with all the Due-Ins. This is also the case with orders made through ECAT (DLA System). Unless there is some link to these other systems, which is doubtful, there should be a way to upload Due-Ins under Materiel Management, Receiving menu.

Create an "Upload" button that allows the function to use a spreadsheet template to quickly process due ins and remove the human error from manual entry.

N/A

When cataloging on DF-RDTE Site ID, we would like certain fields to auto populate with data, yet still have ability to change if needed.

Auto populate fields as suggested in attachment.

AFRLI 61-101

User sees a large volume of sub work order status and reason codes that do not apply to the user processes

Allow Maintenance Program specific sub work order status and reason codes

N/A

See attached "Description of Problem & Proposed Improvement"

See attached "ELMS DAF SCI Physical Inventory FY27Q1 Requirement (Revision 1) 2026 May 29" for solution provided by ELMS Program Manager, Mr. Joseph Stossel

Air Force Portfolio Board directed the SCI transformation effort performed within ELMS for
attached Tab 1 22 July 2025_A4 Portfolio Board Meeting Minutes, Section I, Minute Marker 1:19:26.

Supply Chain reliability by eliminating manual scheduling and execution of mandated cycle counts. The transformation will identify and

ELMS does not currently fully support the DLMS Mark-for Party when generating, modifying, or processing requisitions. Without full Mark-for support, ELMS may not consistently identify the intended end recipient within the ship-to location. This can create gaps in requisition processing, delivery routing, shipment documentation, supply and shipment status visibility, and downstream receipt processing.

ELMS should implement end-to-end support for the DLMS Mark-for Party across the requisition lifecycle. The solution should capture, validate, store, display, and perpetuate Mark-for information when it is provided, ensuring it remains separate from the ship-to address while identifying the intended recipient or destination within the ship-to location. This support should include applicable DLMS transactions such as 511R, 511M, 869F, 869A, 870S, 856S, 940R, 945A, and 527D where required.  The full Mark For should also be included in the printing of the DD Form 1348.

Ensures ELMS is compliant with DOW policy.

Materiel Management does not track inventory quantities by Batch/Lot well. This makes it difficult to determine how much bulk inventory exists within a specific Batch/Lot and limits visibility when inventory must be managed, researched, or reported at that level.

ELMS should move the Batch/Lot number to the same tier level as Owner, Stock Nbr, Project Cd, Purpose Cd, Condition Cd, and Bin Location within its Materiel Management application.  This will enable ELMS to accurately account for inventory within each Batch/Lot.

Improves the way in which ELMS manages bulk Items that are associated with a Batch/Lot Number

Current M&U system does not allow for temporary storage location of parts associated to a Job Order. Parts are expensed on issue from Warehouse to M&U without visibility of Parts on Hand in M&U.

Create a Job Order location when a Job Order requiring parts is opened in M&U. Parts issued from Warehouse against a Maintenance request will be received in M&U in a Job Order location/bin. The Job Order parts location can not be closed out until the parts are consumed in support of the work order.

N/A

Current process does not allow for recording or view of software configurations installed on assets and parts. Users require ability to view current versions of software configurations unique to each asset

Add a MAM attribute for software configurations. Include fields for System Title, Version, Version Date, Date Installed, Installed By, Remarks. Attribute data must be updated via Work Order and data needs to be accessible in M&U and Warehouse.

N/A

Require SKO Configuration Tabs in Warehouse Module to accommodate multiple configurations of the same stock number.

Add Configuration Tabs to the SKO Catalog Edit Page Components Panel. Each tab will allow variations of the same Kit. Require ability to set the configurations through Work Order in M&U and SKO Update process.

N/A

TCTO and Service Bulletins are currently only tracked at Work Order Level. Not viewable in Warehouse.

Record completed work order TCTO/Service Bulletins as an asset record portable with the asset viewable in all Modules where asset resides. Recommend a panel in MAM and in inquires and Inventory Update Manager in Warehouse

N/A

Currently can only add individual assets to Maintenance Schedule

Need ability to add a Stock Number to the Maintenance Schedule so assets will automatically have the schedule added when profiled in maintenance.

N/A

Current process does not allow for passing maintenance history of an asset across Maintenance Activities  

Adjust the work order in Maintenance Journal Inquiries to show all history regardless of Maintenance Activity.

N/A

Current process tracks Tasks time performance separately from Labor time performance data.

Add option at Maintenance Activity Level to toggle on Labor entry rolled up from Task Completion times and utilize the Team Member assigned for the labor entry which will be saved/edited on work order save. Enforce task labor entry. Allow manual labor entry if a sub work order has no tasks.  

N/A