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 |
|
|---|---|---|---|---|---|---|
| 01794 | Due And Status File Report | Warehouse | USMC | Done | Description:
Currently DPAS-WM does not generate a Due and Status File. So we are unable to see the Supply Status history and Estimated Shipping Dates for Requisitions. Currently we are having to use multiple websites to get this information.
Recommended:
Recommend that a Due and Status file report be created so we are able to all requisitioned document related transactions to include supply status, estimated shipping dates and supply status history. (Please see attached example of what the Due and Status file should look like). This should be a report that has parameters where it can be pulled at any tier with time dates that filter on requisition date. Report should be available to pull in CSV or Excel formats. This report should also be available in the Inventory Control Point module.
Mission Critical:
Yes, having this report will reduce time from having to search multiple websites for supply statuses and history. This would also increase audit readiness. Currently we have no way to see in DPAS the Unit price charges for each transaction, which is a USMC audit requirement.
Benefits:
This will help reduce time and improves the accuracy, audibility, and reporting of the requisition supply statuses.
Users:
All IIF & UIF
Marked Done - Change Request satisfied via other system updates per Rick McMillan 16 March 2023 |
|
| 01793 | Optical Character Recognition | Warehouse | USMC | Removed | Description:
Currently the USMC is using a non-accredited software to do Optical Character Recognition (OCR). OCR uses a high resolution picture of of a numeric characters to 'recognize' the intended numbers without having to manually key them in. This is primarily being used to read serial numbers of weapons as part of the receiving process. The current process tries to match serial numbers through recognition against a known set of serial numbers. The software allows the user to set confidence thresholds and when an item does not meet that threshold, it asks the uses to confirm the suggested match. We believe that DPAS can provide a better product that seamlessly provides a better service and is fully accredited for the USMC environment. Recommend DPAS provide an OCR-like capability in certain warehouse/AIT processes to improve inventory accuracy, audit capability, and process time consumption.
Recommended:
Recommend adding OCR functionality during the receipt and picking processes. 1. Adding OCR capability during the receipt process will increase inventory accuracy during "birthing" process of the inventory into DPAS. Recommend adding an OCR capability during the verify portion during the receipt process. Should have the ability to add ICN to the verified grid or verify serial numbers that are already in the grid if the due in came with expected serial number. 2. Once receipt is completed, the OCR verified picture should be attached to the asset that is viewable. This way users can verify system serial number matches the OCR picture that was taken at the time. 3. The pick processes should allow you to add inventory to picks with an OCR capability. Once a pick plan is created, the use should be able to conduct picking actions with OCR capability and add the serial numbers to the pick. This will allow receipt stows and MRO pick to be conducted more accurately and efficiently. 4. There needs to be functionality to change the OCR picture that is attached to an asset. This is required in case the data plate or NSN is changed.
Mission Critical:
Yes, in order to do a weapons warehouse Proof of Principle (PoP) this functionality will be required in order to not lose current functionality. This functionality would benefit ALL DPAS customers.
Benefits:
Implementing an OCR capability will improve inventory accuracy, accountability, audibility, and increase warehouse efficiency.
Users:
This will affect all users of WM who are interested in using OCR capability with AIT devices
Removed per Norman Clark email on 5 June 2025 |
|
| 01792 | DD Form 1149 Corrections | Warehouse | Leidos/NAVSEA | New | Description:
DD Form 1149 does not complete(populate) with all required data. Some data is in the wrong location. Recode locations for data fields on the DD Form 1149 to print correctly and accurately IAW with DOD instructions
Recommended:
See attachement (PPT) and DOD DD Form 1149 Instructions
Mission Critical:
Critical - in order to reduce man-hours to correct DD form 1149 prior to shipments/accuracy of Data. DD Form 1149's are the Document of Record for shipping and transferring Engineering Change kits to the Fleet. The 1149 must be correct and is verified by the Fleet (Regional Maintenance & Modernization Coordination Office (RMMCO)) to ensure all required material to complete the Engineering Change is provided and in acc
Benefits:
Reduced/time and cost. Accuracy of historical paperwork. Easier record keeping (10 year requirement)
Users:
Yes |
|
| 01791 | Mobile Individual Issue-Return Capability | Warehouse | USMC | Done | Description:
Currently the DPAS-WM does not have an Issue and return capability that could be used from an individuals own phone vice having to go to issue counter to create a pick list and begin individual issue process.
Recommended:
commend that an issue and return capability be developed with the following requirements: 1. DPAS customer phone issue capability should be developed by using a QR code. 2. QR code should be developed to allow customer to select the correct master issue list. 3. Master Issue list should populate on customer's phone with the quantities and locations highlighted in red. 4. When an individual selects an item the red highlight will turn to green letting the individual know they have selected that item. 5. Individual should not be able to select more than the Master Issue list Quantity. 6. Once an issue is complete a barcode or QR should appear so it can be easily scanned into DPAS-WM issue screen so the items can be signed for by customer. 7. Customer phone return capability will need to use the same QR code created during the issue process. 8. Ability to mark and highlight items the individual is returning. 9. Once the return is complete a barcode or QR should appear so it can be easily scanned into DPAS-WM return screen all items that the individual chose to return should be checked so the items could be easily returned and turn in receipt generated for customer.
Mission Critical:
Yes, This will help alleviate individuals from having to wait in long lines to start the issue and return process and also help with service times.
Benefits:
Having this functionality will be extremely helpful in reducing wait and service times to the individuals.
Users:
All IIF
Partially Completed – Release 2023.2.4 – 19 May 2023
Partially Completed – Release 2023.2.6 – 06 June 2023
Partially Completed – Release 2023.3.3 – 11 August 2023
Norman Clark email on 5 June 2025 to remove this SCR. Since we already deployed some code change towards this SCR so we cannot remove it; just close it.
|
|
| 01790 | Add Type L Stock Item Type | Enterprise | Leidos | Done | Description:
Currently there is no Stock Item Type Cd = 'L - Local' in the DPAS Catalog. Local Stock Numbers are currently cataloged as Type 'J - MCN', and for a Local Stock Number, the Type J business rules are ignored, allowing users to enter a stock number with a more flexible format. But they are still categorized as a Type J – MCN stock item type. DPAS users have expressed a desire for a true 'Local' Stock Item Type Code that can be used to format stock numbers to meet their individual agency business needs. Adding Type ‘L – Local’ stock
Recommended:
Add a Type ‘L – Local’ stock item type code that will appear as an option during stock number add process and stock number searches where applicable in DPAS (including browse modals and search criteria); Convert existing non-conforming Type J stock numbers to Type L stock numbers in DPAS catalog Stock Nbr table. Establish a single Regx value in all catalogs for the L type Stock Nbr at time of startup allowing agencies to request a change in the Regx value when they are ready.
Mission Critical:
The DLMS change in DPAS Release 2022 that enables DPAS to support the CAGE/Mfr Part Nbr type Stock Nbrs in excess of 15 characters also includes the capability to support the Local Stock Nbr type. Benefits:
The change enables the processing Stock Nbr data using defined DoD methodologies for defining the the different types of Stock Nbrs. As a result of this change it should improve user accuracy in categorization and formatting of the different DoD stock number types.
Users:
This change will primarily impact users who are involved with cataloging.
Completed – Release 2022.3 – 04 November 2022 |
|
| 01789 | Modification to utilization reporting requirement | MU | USAF | New | Description:
M&U presently sets a 30-day utilization reporting requirement for assets subject to utilization reporting. However, utilization reporting for most AF support equipment is only accomplished when the asset is brought in for maintenance, and this is often greater than every 30 days. Additionally, equipment in storage or WRM status may only be inspected annually. With ~100K AF SE assets in M&U, this drives an enormous manpower effort to simply reflect that there was no utilization during the 30 day period.
Recommended:
Add ability on MAM Update screen to designate assets as not requiring a specified utilization reporting period (no 30-day requirement). This would allow users to exempt applicable equipment from recurring utilization reporting requirement (30-days) presently required by M&U.
Mission Critical:
Not mission critical, but it is a significant, unnecessary manpower reqt. 100K assets x 2 minutes per asset to reflect no utilization = 3,300 manhours expended per month across the AF. Reporting utilization for SE is NOT mandated by any AF or DoD policy. Our interim solution is to ignore the Meter Util Not Rptd link, but that's not an acceptable long term solution.
Benefits:
Reduces time, manpower cost, and improves accuracy by allowing users to focus on documenting maintenance properly.
Users:
All AF SE M&U users. |
|
| 01788 | Inventory location parameters | Warehouse | USAF | Done | Description:
User must select each location individually when performing an inventory by location. This could potentially require users to input hundreds of individual locations when inventorying multiple bin rows or cabinets.
Recommended:
Allow range of locations. For example, Starting Loc: 01A009A001, Ending Loc:01A011C003 Our warehouses are segregated into bin rows. Each bin row may have dozens of individual locations. Most of our warehouses schedule our inventories utilizing a range of locations.
Mission Critical:
Benefits:
Reduces time and mitigates manual errors of potentially having to select hundreds of individual locations.
Users:
All users
Completed – Release 2023.1.5 – 10 March 2023 |
|
| 01787 | Add Return Location To Wh Activity Report | Warehouse | SOCOM | New | Description:
1) Lack of a location field in the Unit and Individual Returns sections on the LPWHR78 Warehouse Activity report.
Recommended:
Add a location field in the Unit and Individual Returns sections on the LPWHR78 Warehouse Activity report.
Mission Critical:
Mandated. This data greatly assists audit-ability of armory assets during combat systems inspections as well as providing the complete transactional details to be shown within this report.
Benefits:
Improves Accountability
Users:
This problem affects all current NSW users. |
|
| 01786 | Failed Event Monitoring | Enterprise | Leidos | Done | Description:
DPAS currently tracks failed Events within the DPAS Administration module. When DPAS Admin personnel review the failed event, there currently is no capability to record that the failed event has been reviewed, or what action(s) are being taken / have been taken to resolve the issue.
Recommended:
For audit and management purposes there is a need for the capability to record what action(s) are being / have been taken to resolve the failed event, and to be able to associate the Work Item(s) that have been created to correct the issue.
Mission Critical:
It is critical for DPAS admins to track and resolve DPAS failed events to ensure the system is operating as designed.
Benefits:
It is critical for DPAS admins be able to monitor failed events through resolution to ensure processing is complete.
Users:
This SCR is applicable to DPAS Administration personnel
Completed - Release 2022.2.1 - 9 September 2022
|
|
| 01785 | Add Loan Return Date | Warehouse | Socom | New | Description:
No easy way to pull a query/report to display the "Loan Return Date" for a specific UIC.
Recommended:
Add the 'Loan Return Date' field to INQUIRIES --> ISSUE/RETURN ACTIVITY
Mission Critical:
Yes... No way to determine what CBRN gear needs to be returned in order to support the war fighter down range.
Benefits:
Allows commands to plan resource re-allocation for deploying units
Users:
YES... All people will benefit from this. Especially AFRMS and MARCORLOGCOM |

Please be advised that Navy Property Accountability module users will be unable to access ELMS during the period beginning 3pm EST on Tuesday September 29th, until 8am EST on Friday October 2nd due to the annual EOFY lockout period. If you have questions, please direct them to the Navy PP&E Management Support Office via their centralized email inbox, which is
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.