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: 1807 Result(s) | Show: |
| Title |
ELMS Module |
Reporting Org |
State |
Description |
Action |
|
|---|---|---|---|---|---|---|
| 02344 | Extract lifetime cost data for groups of assets or specific stock numbers | MU | Navy: Wolf | New | Change Request:
Process Improvement
Description:
Currently, the ability to extract labor and non-labor cost analytics from the M&U module is limited and requires enhancement to support more comprehensive reporting and analysis.
Recommended:
Develop a reporting and/or inquiry capability that enables users to extract lifetime cost data for groups of assets or specific stock numbers. Mission Critical:
This enhancement is needed to improve data accessibility and reporting capabilities, enabling users to gain deeper insights, identify trends more effectively, and make more informed, data-driven decisions.
Benefits:
This enhancement will improve data extraction capabilities and provide more robust analytics, enabling users to generate deeper insights and make more informed decisions. Frequency:
Weekly Users:
100-150 USERS |
|
| 02343 | History tracking for an asset’s Equipment Pool assignment | MU | Navy: Wolf | New | Change Request:
Process Improvement
Description:
There is currently no user-friendly method for viewing an asset’s Equipment Pool assignment history, including the date, time, and user associated with each change.
Recommended:
Add history tracking for an asset’s Equipment Pool assignment to provide visibility into the facilities, programs, or other organizational structures (based on the final Equipment Pool design) to which the asset has been assigned. The history should capture all assignment changes, including the date, time, and user responsible for each update. Mission Critical:
This enhancement is needed to improve asset accountability and visibility by providing a clear record of movement between Equipment Pools, enabling users to quickly identify discrepancies and maintain accurate asset assignments.
Benefits:
This enhancement would enable users to more effectively track an asset’s movement between Equipment Pools and provide greater visibility into assignment changes, helping to identify and resolve errors more efficiently. Frequency:
Weekly Users:
100-150 USERS |
|
| 02342 | Additional layer after Equipment Pool to allow for a more detailed asset breakdown | MU | Navy: Wolf | New | Change Request:
Process Improvement
Description:
The current Equipment Pool field structure constrains the accurate categorization of program assets. Because a single program may support multiple concurrent efforts, each effort requires separate identification and segregation to ensure proper asset management and reporting.
Recommended:
Add an additional layer after Equipment Pool to allow for a more detailed asset breakdown. Example: Maintenance Activity = Maintenance Facility, Equipment Pool = Program, third level = Program-specific project breakdown. We can add a Project Code field for the asset (similar to the warehouse module implementation). This would be modifiable in the Maintenance Asset Master screen. Mission Critical:
An additional layer would provide groups with a more detailed asset breakdown and enhance their ability to categorize and maintain assets effectively.
Benefits:
This enhancement will improve the accuracy of asset tracking and reporting by providing greater visibility into asset assignments and maintenance. Frequency:
Daily Users:
100-150 USERS |
|
| 02341 | Profiling of non-serialized assets | MU | Navy: Wolf | New | Change Request:
Process Improvement
Description:
Currently, the system does not allow for the profiling of non-serialized assets. Our team manages assets that require maintenance but do not have assigned serial numbers, limiting our ability to effectively maintain them within the system.
Recommended:
Provide the capability to profile/perform work orders on bulk/non-serialized assets within M&U. Mission Critical:
This improvement is necessary because our group manages a large number of non-serialized assets that require ongoing maintenance and support.
Benefits:
This would allow for a more robust and accurate maintenance tracking system. Frequency:
Daily Users:
100-150 USERS |
|
| 02340 | Viewing/working on sub-assemblies within a parent asset through sub-work orders | MU | Navy: Wolf | New | Change Request:
Process Improvement
Description:
Currently, users are unable to view or pull sub-assemblies from the primary asset on the work order into the sub-work order.
Recommended:
For work orders on SKO assets, enhance the hierarchy system to support viewing/working on sub-assemblies within a parent asset through sub-work orders, all within the same primary work order. Mission Critical:
This enhancement would significantly improve the system by making it more intuitive, efficient, and user-friendly.
Benefits:
This enhancement would reduce the number of steps required to locate an asset within an assembly and enable the system to more accurately represent the assembly hierarchy. Frequency:
Daily Users:
100-150 USERS |
|
| 02339 | Functionality in M&U to reference previously shipped deliverables | MU,Warehouse | Navy: Wolf | New | Change Request:
Process Improvement
Description:
Once an asset is delivered to a unit, it is no longer visible within NAWC WOLF's Warehouse and Maintenance (M&U) module. As a result, teams deployed to perform maintenance on that asset in the field are unable to create or manage work orders against it, since the asset is no longer accessible within the M&U module.
Recommended:
Add functionality within M&U to reference previously shipped deliverables, enabling maintenance activities to continue creating/managing work orders for these assets. This ensures the assets remain visible and manageable within the M&U instance. Potential additional functionality:
Enable the ability to browse assets across organizations and allow users to pull those assets into their Maintenance Activity for assignment in the MAM/work orders. This will allow for assets that originated outside our organization to be maintained within our instance of M&U.Mission Critical:
This is necessary as our group requires system visibility into customer-delivered assets to effectively perform ongoing maintenance and support activities.
Benefits:
This would enable assets delivered to units to be maintained while in the field, addressing a previous gap where those assets were not visible within the M&U system. Frequency:
Daily Users:
100-150 Users |
|
| 02338 | Automated Max/Min Stock Qty | Warehouse | NSWC | New | Change Request:
Process Improvement
Description:
Currently WM does not maintain the ability to automatically adjust the Maximum and Minimum Stock Quantity therefore requiring the user to manually review numerous records for demand data for a given time period and analyze usage for manual updates to stock record cards.
Recommended:
Add functionality where the user can set parameters for historical demand data, e.g., time period, usage rate, etc., that would automatically adjust property record Max and Min Stock Quantity data fields.
Mission Critical:
N/A
Benefits:
As we get closer to the implementation of the ELMS connection with DAI, commands will be looking to utilize requisitioning. A key cost-effective metric in requisitioning is ensuring the warehouses have optimal stock on hand. Currently, maintaining high/low limits, and reorder points require the user to run reports and manually update each stock item one at a time which. When warehouse have hundreds of stock items a auto-update feature like this would save countless number of man-hours. Frequency:
Daily Users:
All users utilizing high/low limits and reorder points. |
|
| 02337 | Source of Supply Inquiry | PA | SOCOM | New | Change Request:
Process Improvement
Description:
Currently, ELMS users face an administrative bottleneck requiring the manual consolidation of two separate reports to identify equipment sources. Within the Property Accountability (PA) module, the Asset Management inquiry lacks the option to include 'Source of Supply' (SOS) data in its output. Consequently, personnel are forced to generate a secondary Catalog Stock Number inquiry and utilize manual spreadsheet functions (e.g., VLOOKUP) to cross-reference the data, solely to determine whether an asset's SOS is 'H9D' or an alternative provider.
Recommended:
Update ELMS PA Module to include catalog data fields during Inquiry processes—specifically but not limited to 'Source of Supply'—as selectable data options within the Property Accountability module’s Asset Management inquiry screen.
Mission Critical:
Per USSOCOM DIR 700-2, Section II, para 17d. MFP-11 SO-P property is segregated from service provided equipment in APSR. USSOCOM IG J4 Checklist also attached ref. pg 1 under APSR #4.
Benefits:
This capability satisfies the USSOCOM directive by generating a single report that distinctly segregates MFP-11 property from Service-provided equipment. This unified reporting method eliminates the need to manually compile multiple documents, significantly reducing administrative burden and saving time. Frequency:
Daily Users:
All PA Users that manage equipment from various Major Program Sources of Funding for audit purposes. |
|
| 02336 | Inquiry Role | Materiel Management | JSF (Joint Strike Fighter) | New | Change Request:
New Role Design
Description:
JSF is using the ELMS C-ICP inventory visibility processes for its F35 program. The two primary vendors / suppliers are Lockheed Martin (LM) and Pratt & Whitney (P&W). These two vendors currently have 96K+ cataloged items. Their combined anticipated DLMS transaction activity is several million transactions a year. To support this volume of traffic / monitory reasons for transaction failure, JSF desires to provide the vendors read access to ELMS. In reviewing the current ELMS Materiel Mgmt roles, there is no 'inquiry' role that provides the level of access JSF desires to provide the vendors.
Recommended:
Request an inquiry role be developed for use by JSF as detailed in the attachment.
Mission Critical:
JSF plans to provide its C-ICP vendors inquiry access to ELMS. This access should be limited to information that is provided by them via DLM
Benefits:
1. Provides a method for the vendors to assist the JSF team in resolving DLMS transaction conflicts. 2. Eliminates the need to generate extracts to provide the vendors visibility of the data.
3. Provides real-time position.
4. Eliminates a third party web site / share site to store data needing to be shared.Frequency:
Daily Users:
At this time, there is an estimate of ten users although ELMS will have more than 100 C-ICP vendors sending data to ELMS when including the Air Force's C-ICPs. This role can be used by these C-ICPs as well as any ELMS warehouse operation that the government wishes to provide them with visibility of Materiel Mgmt. data. |
|
| 02335 | M&U MAM Remarks Attribute | MU | AF: A4/HAF FH-AFHAF | New | Change Request:
Process Improvement
Description:
The M&U system lacks a dedicated data field for users to input and store custom-defined attributes at the asset level, making it difficult to retrieve this information during asset record reviews. Users are unable to identify an asset's mission configuration when reviewing the Mx Asset Master (MAM) screen or during dispatching process.
Recommended:
The recommended solution is to add a "Remarks" field in the additional attribute section of the Mx Asset Master (MAM) data tab, enabling users to document interchangeable attributes, associated with assets. This information will be retained for future reference and use. Example: Software versions, cable configurations, transportation configurations, etc. Remarks field should be viewable in search results grid when searching an Asset Id. Further, remarks should populate in the ELMS Form 244, Section I, Block 8.
Mission Critical:
DAFI 21-103, EQUIPMENT INVENTORY STATUS AND UTILIZATION REPORTING requires documentation of an assets configuration and it's ability to perform an assigned mission.
Benefits:
This will enable the Air Force to achieve the desired effects in improving overall readiness and war-fighter support. Strengthens Air Force's enterprise visibility of asset posturing for mission execution. Frequency:
Daily Users:
This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that conduct maintenance on their support equipment. |
Disclaimer | Accessibility
Please be advised that ELMS will be unavailable beginning Friday, October 2nd at 9:00 pm EST for server maintenance. Estimated downtime is stated to last up to 60 minutes in length - please plan accordingly.