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: 1779 Result(s) | Show: |
| Title |
ELMS Module |
Reporting Org |
State |
Description |
Action |
|
|---|---|---|---|---|---|---|
| 02316 | Mark For Implementation | PA,Warehouse,Materiel Management | Leidos | New | Change Request:
Policy / Regulatory
Description:
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.
Recommended:
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.
Mission Critical:
Ensures ELMS is compliant with DOW policy.
Benefits:
Supports Mark For which is required for shipping sensitive items. Frequency:
Daily Users:
All users who use the Mark For |
|
| 02315 | Tracking Batch/Lot Quantities | Materiel Management | Leidos | New | Change Request:
Process Improvement
Description:
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.
Recommended:
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.
Mission Critical:
Improves the way in which ELMS manages bulk Items that are associated with a Batch/Lot Number
Benefits:
Resolves discrepancies with reporting inventory by Batch / Lot. Frequency:
Daily Users:
All users of Materiel Mgmt. |
|
| 02314 | Work Order Parts Location | MU | SOCOM | New | Change Request:
Process Improvement
Description:
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.
Recommended:
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.
Mission Critical:
N/A
Benefits:
Implementing this solution meets the mission needs of NSW Frequency:
Daily Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels. |
|
| 02313 | Software Configuration Record | MU,Warehouse | SOCOM | New | Change Request:
Process Improvement
Description:
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
Recommended:
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.
Mission Critical:
N/A
Benefits:
Implementing this solution meets the mission needs of NSW Frequency:
Daily Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels. |
|
| 02312 | SKO Configuration | MU,Warehouse | SOCOM | New | Change Request:
Process Improvement
Description:
Require SKO Configuration Tabs in Warehouse Module to accommodate multiple configurations of the same stock number.
Recommended:
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.
Mission Critical:
N/A
Benefits:
Implementing this solution meets the mission needs of NSW Frequency:
Daily Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
Cancelled 6/22/2026 - per email submitted by Reed, Randall This SCR is the same as SCR 02040 |
|
| 02311 | Permanent Record At Asset Level for TCTO/Service Bulletins | MU | SOCOM | New | Change Request:
Process Improvement
Description:
TCTO and Service Bulletins are currently only tracked at Work Order Level. Not viewable in Warehouse.
Recommended:
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
Mission Critical:
N/A
Benefits:
Implementing this solution meets the mission needs of NSW Frequency:
Daily Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels. |
|
| 02310 | Maintenance Schedule at Stock Number Level | MU | SOCOM | New | Change Request:
Process Improvement
Description:
Currently can only add individual assets to Maintenance Schedule
Recommended:
Need ability to add a Stock Number to the Maintenance Schedule so assets will automatically have the schedule added when profiled in maintenance.
Mission Critical:
N/A
Benefits:
Insures that all required schedules are assigned to assets, eliminating input errors. Frequency:
Daily Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels. |
|
| 02309 | Maintenance History | MU | SOCOM | New | Change Request:
Process Improvement
Description:
Current process does not allow for passing maintenance history of an asset across Maintenance Activities
Recommended:
Adjust the work order in Maintenance Journal Inquiries to show all history regardless of Maintenance Activity.
Mission Critical:
N/A
Benefits:
Implementing this solution meets the mission needs of NSW Frequency:
Daily Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels. Cancelled 6/22/2026 - per email submitted by Reed, Randall This SCR is covered by SCRs 01877, 01205 and 00928 |
|
| 02308 | Labor Hours from Tasks | MU | SOCOM | New | Change Request:
Process Improvement
Description:
Current process tracks Tasks time performance separately from Labor time performance data.
Recommended:
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.
Mission Critical:
N/A
Benefits:
Implementing this solution meets the mission needs of NSW Frequency:
Daily Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels. |
|
| 02307 | Enforce Labor Entry on Work Order | MU | SOCOM | New | Change Request:
Process Improvement
Description:
Current process does not enforce requirement to enter Labor Data on Work order.
Recommended:
Create a toggle option at the Maintenance Activity to enforce the mandatory use of Labor Data/Hours on work order close process.
Mission Critical:
N/A
Benefits:
Implementing this solution meets the mission needs of NSW Frequency:
Daily Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels. |
Disclaimer | Accessibility