Unlike submitted Support help tickets, System Change Requests (SCR's) can only be submitted through your organization's appointed and authorized ELMS CCB member representatives, or otherwise if no CCB representatives have yet been appointed, your Primary Information Owner appointee. If you are unsure of who your organization's appointed ELMS CCB member representatives or Primary IO are, you may email the ELMS Support team to request that information:
To learn more about the process, please visit our CCB Responsibilities and Meetings page. Below you will find all SCR's that have been submitted, and what their status is. To download a blank form, you may visit our Reference Library and download the SCR Form.
Utilize the search filters below to narrow your results by keywords, module, or state. You may also request an Excel file of all the SCR data by contacting the Help Desk.
| Found: 1817 Result(s) | Show: |
| Title |
ELMS Module |
Reporting Org |
State |
Description |
Action |
|
|---|---|---|---|---|---|---|
| 02374 | Inv Reconcile Detail Improvement | Warehouse | NSWC | New | Change Request:
Process Improvement
Description:
The 'Real Time Report = Inv Reconcile Detail' is currently missing critical tracking, auditing, and classification columns, which are essential for asset accountability. Specifically, users cannot view transaction metadata such as when it was established/modified, who performed the actions, or the commodity types. Furthermore, adding these columns as a flat table would clutter the interface and degrade the user experience.
Recommended:
Enhance the 'Real Time Report = Inv Reconcile Detail' by adding the following eight (8) columns: 1) Last Transaction Date/Time, 2) Last Transaction By, 3) Established Date/Time, 4) Established By, 5) Type Asset Code, 6) ACC, 7) Secure Commodity, and 8) Reportable Commodity. To maintain a clean and user-friendly interface, implement a collapsible/expandable drop-down sub-header mechanism similar to the design of the 'Warehouse Transfer Screen' so users can expand and view these detailed columns. Mission Critical:
N/A
Benefits:
Improved Auditability: 1) Provides clear and direct tracking of transaction without going through multiple screens or using tools outside of ELMS. 2) High Usability: The collapsible sub-header (similar to the Warehouse Transfer Screen) ensures the report remains clean and readable, displaying detailed columns only when needed. 3) Faster Reconciliation: Centralizes critical commodity and asset codes in one view, eliminating the need to cross-reference multiple screens. Frequency:
Hourly Users:
All Users |
|
| 02373 | Column additions to Real-Time Reports | Warehouse | USMC | New | Change Request:
Process Improvement
Description:
In Reports Manager/Real-Time Reports, the Inventory Reconcile Summary Report and Inventory Reconcile Detail Report do not identify whether reported on-hand and allocated quantities are displayed at the Unit Issue (UI) level or the Stocking Unit Issue (Stocking UI) level. Because UI and Stocking UI may differ, users cannot reliably interpret reported quantities, which can result in significant variances in total on-hand and allocated inventory.
Additionally, the reports do not display the associated inventory value, limiting users’ ability to assess the financial impact of the reported inventory balances. Recommended:
Enhance the Inventory Reconcile Summary Report and Inventory Reconcile Detail Report in Reports Manager/Real-Time Reports to clearly identify the unit-of-measure being reported for all reported on-hand and allocated quantities. At a minimum, each report should display whether quantities are reported in Unit Issue (UI) or Stocking Unit Issue (Stocking UI), including the applicable conversion factor when the two units differ. Additionally, add inventory value fields (whether it be Unit Price or Stocking Unit Price) that display the extended value of on-hand and allocated inventory using the applicable unit cost and the reported unit-of-measure basis. The reports should provide clear labels for quantity, unit of issue/stocking unit of issue, unit cost, and extended inventory value to ensure users can accurately reconcile balances, understand quantity variances, and assess the associated financial impact. Mission Critical:
N/A
Benefits:
Users that are utilizing these reports will be able to distinctly identify quantity of on hand inventory and it's value. Frequency:
Daily Users:
N/A |
|
| 02372 | MRP FTE Excess Materiel Declaration and Customer Asset Report Processing USMC | Warehouse,Materiel Management,Registry (SA/LW) | USMC | New | Change Request:
Policy / Regulatory
Description:
The identified capability gap is the absence of a single APSR-controlled process to identify retail materiel excess above authorized retention, complete required screening and approval, protect the offered quantity, and generate and track the required DLMS 180M Customer Asset Report through DAAS. Reliance on manual or disconnected processes increases the risk of inconsistent calculations, duplicate offers, incorrect routing, and incomplete transaction traceability.
USMC retail supply activities, supporting commands, ICP/PICA personnel, and interface-support organizations are affected. Without this capability, excess materiel may remain unavailable for enterprise redistribution, accountable balances may not reflect pending offers, DAAS or ICP responses may not be correlated to the original report, and policy compliance and auditability may be weakened.
he capability gap was identified while modeling the Level-4 retail excess process against DLM 4000.25, Volume 2, Chapter 11; MCO 4440.31E; and MCO 4400.201, Volume 6. The process occurs whenever a retail activity identifies serviceable or economically reparable NSN materiel above its authorized retention quantity. Historical transaction volume, rejection rates, and processing time require baseline collection during requirements decomposition.Recommended:
Implement an APSR workflow that calculates and validates reportable retail excess, performs configurable screening and approval, controls the offered quantity, derives ICP/PICA routing, generates and transmits the DLMS 180M through DAAS, processes transaction status and rejects, and supports cancellation and follow-up. The expected outcome is a controlled, traceable, policy-compliant retail excess reporting process. This SCR registers requirement to support the excess Customer Asset Report process. Key requirement features include; 1. Identify reportable excess using authoritative inventory, availability, retention, and open-offer data., 2. Validate NSN, unit of issue, condition, quantity, and Materiel Returns Program eligibility., 3. Complete required redistribution screening and approval., 4. Prevent duplicate commitment or disposition of offered quantities., 5. Derive the responsible ICP/PICA and transaction addressing.
6. Generate and transmit a compliant DLMS 180M/FT Customer Asset Report through DAAS., 7. Process routing status, rejects, cancellation, and follow-up transactions., and 8. Maintain complete transaction history, accountability, and management visibility. Additionally, DLM 4000.25 identifies the NSN-based Customer Asset Report as a DLMS 180M with Transaction Type Code FT, performing the functionality historically associated with the FTE transaction, and requires electronic transactions to be routed through DAAS. MCO 4440.31E requires serviceable or economically reparable assets above the retail retention limit to be reported to the wholesale manager in full unit-of-issue quantities. A detailed list of requirements are contained in the attached spreadsheet titled: MRP FTE Requirements 20260723v2.Mission Critical:
N/A
Benefits:
Retail activities may continue to rely on fragmented or manual processes that do not consistently identify excess, control offered quantities, validate ICP/PICA routing, or correlate DAAS and ICP status. This increases the risk of duplicate or inaccurate offers, delayed redistribution, excess retention and storage cost, transaction rejection, incomplete audit evidence, and noncompliance with established Materiel Returns Program procedures Key risks include incorrect retention-rule configuration, stale ICP/PICA routing data, incomplete DLMS implementation-convention mapping, inadequate quantity-control logic, unavailable partner test environments, interface certification delays, and insufficient user training. Frequency:
Daily Users:
N/A |
|
| 02371 | Convert transactional data from contractor systems to DLMS | Materiel Management | Joint Strike Fighter | New | Change Request:
New System Process
Description:
Current ICP import tool does not convert transactional data from contractor systems to DLMS for update of ELMS ICP
Recommended:
The F-35 Joint Program Office (JPO) requests a technical and cost proposal from Leidos to develop a capability within the ELMS Inventory Control Point (ICP) module to accept user-prepared CSV files containing the required data elements for DLMS transaction processing. The capability shall read each row sequentially, validate the required data elements, and process the identified DLMS transaction. A dashboard shall display the processing result for each row, indicating whether the transaction was successfully posted or rejected. Rejected rows shall include the reason for rejection to support correction and resubmission. The proposal shall describe the technical approach, supported DLMS transaction types, CSV formatting requirements, validation rules, audit trail, implementation schedule, testing approach, and associated costs. Mission Critical:
This change will enable JPO to collect daily transactional data from various contractor systems (e.g. LSEMS, ALIS, AMETS, MAXIMO, etc.) and update inventory records in ELMS ICP through DLMS processing.
Benefits:
This process will enable a direct audit trail to transaction in contractor's system. Contractor's daily transaction report will be kept on file as KSD to support ICP updates. Frequency:
Daily |
|
| 02370 | Commodity Type Improvements | PA,MU,Warehouse,Materiel Management | Leidos | New | Change Request:
Process Improvement
Description:
The ELMS Warehouse application was originally designed to support a specific user community with it having its own cataloging processes Subsequently ELMS has added a Materiel Management application and and has provided the Maintenance application with its own catalog capabilities. To streamline ELMS, ELMS combined its cataloging processes into a single set processes that all ELMS applications. It has also added catalog builds using the DLMS 832N cataloging transaction set. Recommended:
1. Retain Reportable Commodity Type within the Stock Nbr process and remove Security Commodity Type. 2. Provide the capability for users to add/update/delete Reportable Commodity Types wherever the catalog can be managed.
3. Add a new process to the Warehouse application to enable the creation of Inventory Management teams similar to how the MM application creates Item Manager teams
4. Relink the processes that use the Security Commodity Type to use the Inventory Management Team Id.
5. Stock Nbrs that are not associated to an Inventory Management Team will be shown in all teams so they are not hidden.
6. Recommendation is to not require Inventory Management Teams.Mission Critical:
N/A
Benefits:
- Lets each warehouse organize and restrict its own inventory without affecting other warehouses that share the catalog. - Removes security commodity type from the security data layer and puts it in control of warehouse personnel to enable them to assign staff easily
- Gives one consistent Commodity Type for categorization and reporting across all modules.Frequency:
Daily Users:
All |
|
| 02369 | ADC 1515 - 947I Dual Stock Nbr Update Transaction | PA,MU,Warehouse,Materiel Management | Leidos | New | Change Request:
ADC 1515 - 947I Dual Stock Nbr Update Transaction
Description:
When a product identifier (stock number) changes for a serially managed GFP item, ELMS cannot currently recognize it as a change to the same item. Existing DLMS 947I processing treats a product/service identifier change as a drop (delete) of the old record followed by an add of a new record. This breaks the continuity and history of the serially managed asset and makes stock number changes difficult to track accurately. DLMS ADC 1515 enables a dual transactions (loss and gain) within the same transaction set. Recommended:
Implement DLMS ADC 1515 (Multi-Change 947I Transaction Update, signed 31 Jul 2026) in ELMS. 1. Modify Warehouse inventory update to report updates using the dual transaction capability of the DLMS 947I.
2. Modify Materiel Mgmt. update to support a dual DLMS 947I for stock nbr changes as provided by ADC 1515.
3. Note: ELMS must continue to support one-sided Stock Nbr change transactions as it was not eliminated from the IC.Mission Critical:
Required to comply with Approved DLMS Change (ADC) 1515, Multi-Change 947I Transaction Update, signed 31 Jul 2026, which updates the DLMS 947I standard.
Benefits:
More accurately tracks stock number (product identifier) changes for serially managed GFP; preserves asset continuity and audit history instead of losing it through a drop/add cycle; aligns ELMS with the approved DLMS 947I standard (ADC 1515); and reduces manual reconciliation and the risk of orphaned or duplicated records when identifiers change. Failure to implement this ADC will result in DLMS 947I dual stock nbr transaction set suspending. Frequency:
Daily Users:
All ELMS users of DLMS Transactions. |
|
| 02368 | ADC 1491 - Create DLMS 867E Government Furnished Property Embed | PA,Warehouse,Materiel Management | Leidos | New | Change Request:
Policy / Regulatory
Description:
ELMS is a designated DoD Accountable Property System of Record (APSR, DoD IT Portfolio ID 3266) but currently has no automated means to be notified when serially managed Government Furnished Property (GFP) in a contractor's custody is embedded/incorporated into a higher-level component, assembly, or end item, or is otherwise consumed. Per DFARS 252.245-7005(b)(1)(iv), contractors must report these embed/consume events to the Government Furnished Property (GFP) Module of the Procurement Integrated Enterprise Environment (PIEE), but today those events are captured only via web UI or flat-file submission and are not pushed to the property systems tracking the item. Without this notification, ELMS cannot flag that an item is no longer severable, which weakens accountability and the DoD material audit posture for government property in the possession of contractors. Recommended:
Implement ADC 1491 by adding the new DLMS 867E (Government Furnished Property Embed) transaction to ELMS. ELMS will consume the 867E transmitted from the PIEE GFP Module - sent using code "M4 (RIC)" in 1/N103/80 with ELMS identified as the receiving property system via code "40 (Receiver)" in 1/N101/80. ELMS will read the Product Transfer Type Code (2/PTD01/10) to process each event type: piece embedded into a line item (BW), piece consumed (BX), piece embedded into an independent parent (BY), and piece embedded into a non-GFP/production item (BZ). Using the parent-item, serial number/UII, and supply condition code data carried in the transaction, ELMS will remove the items added to the kit from inventory and update the SKO to reflect the added items when the SKO is managed. Mission Critical:
Directed by the December 7, 2024 Secretary of Defense memorandum requiring DoD property systems to demonstrate progress interfacing with the PIEE GFP Module; ADC 1491 is one of the designated interfaces (target: 50% development progress by 30 September 2025).
Benefits:
Provides automated visibility of GFP embed/consumption events directly from the PIEE GFP Module, improving accountability of contractor-held government property. Enables ELMS to correctly identify items that are no longer severable, reduces manual reconciliation, and directly supports compliance with DFARS 252.245-7005, DoDI 4161.02, and the Secretary of Defense FY2025 Financial Statement Audit Remediation Priorities (Dec 7, 2024 memo) requiring DoD APSRs to integrate GFP data from the PIEE GFP Module via automated interface. Frequency:
Daily Users:
All users who have contractors building kits for them. The contractor is to generate the DLMS 867E to report items put into a kit. |
|
| 02367 | Inventory Detail Inquiry Cost & Depreciation Display | Materiel Management | Leidos | New | Change Request:
Process Improvement
Description:
The Inventory detail inquiry within the MM/ICP module does not currently display cost or depreciation information for bulk and fixed assets. Users reviewing inventory detail cannot see the associated cost and depreciation data without navigating to a separate screen or source, which slows research and reconciliation. Recommended:
Enhance the Inventory detail inquiry to display cost information and depreciation amounts for both bulk and fixed assets directly within the detail view. Values should include the Financial Cost, Total Cost (for bulk the qty * the financial cost, plus Accumulated Depreciation and Net Book Value for Capital Assets. Mission Critical:
Required for knowing the balance sheet value of the item.
Benefits:
Provides users with immediate visibility into asset cost and depreciation data during inventory research, reducing the need to cross-reference other screens, improving efficiency, and supporting more accurate inventory valuation and reconciliation. Frequency:
Daily Users:
All |
|
| 02366 | Query by Secondary Serial Number in Work Order Inquiry and Maint Asset Inquiry | MU | Navy: Wolf | New | Change Request:
Process Improvement
Description:
Currently, Secondary serial number is not an available search option within the field section of Work Order Inquiries/Maint Asset Inquiries. Recommended:
Add an option to query by Secondary Serial Number in Work Order Inquiry and Maint Asset Inquiry. Mission Critical:
This will improve the systems reporting capabilities.
Benefits:
This improvement would benefit users by allowing them the ability to better track and manage assets within the system. Frequency:
Weekly Users:
100-150 Users Cancelled 10/2/2026 - per email submitted by Jonathan Anlauf. The requirements of this SCR are already being covered by SCR 01724. |
|
| 02365 | LMS_EV Feed | NSWC | New | Change Request:
Process Improvement
Description:
The need and ability to obtain more data metrics with equipment associated with NSW. Recommended:
Receive a data feed similar to the Air Force with LMS_EV for NSW to add to channel. Mission Critical:
N/A
Benefits:
Ability to identify shortfalls and/or, patterns relating to equipment. Frequency:
Daily Users:
All users |
Disclaimer | Accessibility