Description: 

Mission Critical: 

Benefits: 
This change implements ADC 1415 for ELMS. CASCOM has implemented this change in GCSS-A, once enabled in ELMS, USSOCOM will have ability to transmit the  complete set of 16 APSR data elements, including the Value/Acquisition Cost, Depreciation Value, Useful life, and Acquisition Date (or Date Placed in Service) to the gaining GCSS-A organization.

Frequency: 
Daily

Users: 
This process is required to support the US Army Special Operations Command elements that currently leverage the GCSS-A System.  

Cancelled 8/13/2026 – per email submitted by Reed, Randall.
This SCR was determined to be a duplicate of SCR 01957.

SOF ELMS Warehouse users require the ability to manually enter a Document Number during the Warehouse Issue process. The manually entered document number is required for Warehouse Issues where the requesting organization is submitting requests using a stand alone system. Warehouse personnel enter the requesting document number to create an audit trail between the off line request and the issue transaction  

Modify the existing SCR 02037 Submitted by NSW to generate a DD Form 1150 for Warehouse Issues. Add the option during the Issue Process to manually input a Document Number. This will allow Warehouses to match document numbers submitted by units using system that work off line such as the SPEAR application. This solution will create a matching transaction in ELMS and off-line manual systems creating an audit trail.

This is related to existing SCR 02037

During the three stages of receipt of property process in ELMS (Receipt, Verification, and Acceptance) the Acceptance stage overrides previous transaction data (Receipt and Verification). Screenshot attached. Under Document Inquiry it should display Received By: User ID / Received On: Date and Time Stamp. Verified By: User ID / Verified On: Date and Time Stamp. Accepted By: User ID / Accepted On: Date and Time Stamp.

We need ELMS to track the full lifecycle of property intake rather than just the latest action. Update the Receiving process to display and retain the date, time, and User ID for all three stages—Received, Verified, and Accepted—so we have a complete and accurate historical record. Add a Transaction Date/Time stamp within the details box (screenshot attached).

N/A

Need the ability to "Group By" Location when printing the DW 28 - Inspections Due Report. This would allow the user to be provided a report that lists out the assets by location so they will not need to jump around from location to location when going through the list.

Add Location as a selection in the Group By dropdown selector.

N/A

Executive Order 14347, titled "Restoring the United States Department of War" provided for the use of DOW (Department of War) in lieu of DOD (Department of Defense). Directs all federal executive department and agencies to recognize and accommodate these secondary titles.

Modify ELMS Department Cd data to recognize DOW.  

Implements Executive Order 14347

Pearl Detachment Guam (PDG) owned assets are being input into ELMS, but they are not being pushed to the xml files used by the ELMS->eFEM interface, leading to PDG asset records not being created in eFEM.

Request DLA create a new data feed of just the entries for PDG UIC N6697H and add this to the automated job that creates the xml files used by the ELMS->eFEM Interface.

This is an expansion of the ELMS->eFEM Interface data feed.

As part of the SCR to support the association of authorizations to the property record for the AF/A4LR requirement, we also need to include the associations for LIN/TAMCN authorization that will be utilized by the A4LR VSCOS community, currently they have SCR 2062 open. Per ELMS PMO Authorization Management was scheduled to move to FSM as part of the ELMS PA tech refresh, pending auth management process to move to FSM for the below.

Include LIN/TAMCN data elements to the new FSM Associated auth process. Mapping of specific LIN/TAMCN process  in FSM on going. Once completed require the capability to associate the property record to the FSM authorization.

CJCSI 3401.01E, DAFI 24-302, and AFI 10-201

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.