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 |
|
|---|---|---|---|---|---|---|
| 02096 | General Database Infrastructural Changes - CY 2025 | Leidos | In Progress | Change Request: Process Improvement
Description: In many application releases, the Leidos team needs to implement various database infrastructural changes and improvements. These changes include, but are not limited to, index adjustments, configuration changes, and the implementation of database utility objects. These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, correctness, and performance of the DPAS system. I am requesting an SCR for calendar year 2025 to encompass this category of database changes. Recommended: Implementation of any database infrastructural changes and improvements deemed necessary by the Leidos Team. Mission Critical: Benefits: These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, integrity, and performance of the DPAS system. Frequency: Daily Users: N/A - Infrastructural enhancements that wouldn't directly affect the users. Partially Completed - Release 2025.1.3 |
||
| 02095 | Modify when attachments can be added to a MRO | Warehouse | ASAALT | New | Change Request: Process Improvement
Description: Currently we are unable to upload supporting documentation to a close MRO's only if the MRO has not been released or shipped. When processing an MRO in DPAS we must mark the MRO as shipped for the DLMS transaction to be pushed to G-Army. When the MRO is shipped the transaction is closed. However, at that time we may not have the signed receiving documentation such as DD1348, 1149, or DA3161 because the Property Book Office (PBO) is waiting to see the transaction show up in G-Army. Once the PBO can see and verify the transaction in G-Army they sign the receiving documentation. For auditability we should be able to upload this signed document into DPAS as supporting documentation for the MRO. Recommended: All the option to upload documentation to any MRO record even it if is in a released, shipped/closed status. Mission Critical: To improve MRO in supporting KSDs Benefits: By allow the user the option to upload supporting documentation to the MRO transaction within DPAS even when the transaction is closed it will provide better accountability and auditability of government property. Frequency: Weekly Users: All user trying to maintain auditability for government property within DPAS. |
|
| 02094 | Add SKO Component List to Inventory Reports | Warehouse | NECC | New | Change Request: Process Improvement
Description: When inventorying a SKO'd item, the only stock number that populates is that of the actual SKO, and not the components attached to the SKO. Recommended: Add the ability to view the list of components attached to the SKO for all physical inventory reports. Mission Critical: NECC 5200.45 Benefits: This will give the users who utilize SKO's visibility of what components they need to verify and inventory for. Makes it easier for the end user to inventory when the SKO stock nbr is different than the main component item. Frequency: Daily Users: NECC-wide |
|
| 02093 | Active/Reserve Component Add | Warehouse | NECC | New | Change Request: Process Improvement
Description: There was a recent request to be able to distinguish between Active and Reserve individuals that are issued gear here at NECC. Currently, there's no way that we're able to track who's Active or Reserve in any reporting tool and would like to add that capability within DPAS WH. Recommended: This would have to start when the users are creating the Member Profiles, and allowing the user to select from a drop down whether the issued user is Active or Reserve. We noticed there is a field for Duty Status, however there's no way to be able to input that information. Once the gear has been issued, the user should be able to see this on the DW Issued Receipt form, in addition to all the Issued Inquiry reports where one can either filter this option or export it onto excel and filter as needed. This capability should be added to both the Individual Issue as well as the Unit Issue functions. Mission Critical: NECCINST 5200.45 Benefits: Having this capability would provide the user with the ability to separate between Active and Reserve members and fully give them visibility when generating reports in DPAS WH. Frequency: Daily Users: All users who utilize the Individual/Unit Issue functions. |
|
| 02092 | Reason Code Field For Individual Return | Warehouse | NECC | New | Change Request: Process Improvement
Description: We've received a request to create an additional (optional) field to the Individual Return process to allow them to specify a return reason/code to ALL issued items within an individual record that are being returned (i.e. transfer, separation, gear refresh, damaged gear, etc.). In result, it would give them the ability to view the return reason code when generating individual return reports. Recommended: During the Individual Return Process, the user should be able to select an optional return reason/code drop-down box similar to a Not Ret. Reason Code that currently exists. Once the return is complete, they should be able to view the return reason/code in a return report as an optional column within Grid Options. Mission Critical: NECCINST 5200.45 Benefits: Having this capability would provide the users with the ability to see the reason an item was returned, track reasons for return, and forecast future issues. Frequency: Daily Users: All users who utilize the Individual Issue function. |
|
| 02091 | Split inventory seg code inventories by facilities | Warehouse | ASAALT | New | Change Request: Process Improvement
Description: Unable to split physical inventory by facility names when using the inventory segment code inventory mode. Recommended: Provide the option to select or split a physical inventory by Facility name and /or location id when using the inventory segment code as the inventory mode. Mission Critical: Army Regulation 740–26 - Physical Inventory Control Army Regulation 735–5 - Property Accountability Policies
Improves the conducting of a PI when materiel is located in different facilities.Benefits: When using multiple facilities, location id and multiple owning DoDAACs within a warehouse the inventory teams could conduct an inventory more efficiently if the physically inventories that are based on the inventory segment code could be split between each selected facility and location id. Currently this type of feature is not available when using the inventory segment code as the inventory mode therefore some of our physical inventory that are generally are very large due to the fact the report is being ran across multiple facilities for one owning DoDAAC. This can lead to an increase in inventory time since the report cannot be split by facility. If the inventory is split by facility one physical inventory can be generated for one inventory segment code and a single owning DoDAAC. The report would be split by facility and provide to each facility manger. Therefore, the inventory team(s) can conduct the inventories in a timelier manner. Frequency: This will be used monthly and in some cases weekly.
Users: All users who use physical inventory |
|
| 02090 | Add Facility Name to PI report and PI downloads | Warehouse | ASAALT | New | Change Request: Process Improvement
Description: Currently the physical inventory report and the inventory export file within the DPAS Warehouse module do not show the facility name in which the asset is currently located. If a single warehouse has more than one facility name, it can become hard to know which facility to look in when conducting an inventory. Recommended: Add the facility name to each line item on the physical inventory report and the inventory export file. Mission Critical: Provides visibility where the item is located. Benefits: By adding the facility name to the inventory report and the inventory export file the user will know exactly which facility the asset is in when conducting the inventory. This will save time by not having to revisit DPAS to determine the facility name in which the asset is located. Frequency: Daily
Users: All users using the physical inventory reports to conduct a physical inventory. |
|
| 02089 | Add Inventory Segment Code to Inventory and ICN inquiries | Warehouse | ASAALT | New | Change Request: Process Improvement
Description: Currently the stock number inventory segment code is not available on the inventory grids or the ICN reports. This makes it difficult for the user to view when the item will be scheduled for a physical inventory. Our warehouses are connected to an ICP, thus the catalog is managed by the ICP. It is not known how the ICP is establishing segment codes. Recommended: Add the inventory segment code value as a grid option on the inventory grids and the ICN inventory reports. This will provide the WM users with visibility of what inventory the item is a part of without executing multiple reports and merging of data. Mission Critical: Provides visibility of which inventory the item will be a part of without having to run multiple queries and mergeing of the data. Benefits: Having the Inventory Segment Code as a grid option would allow better management of materials within the warehouse. Frequency: Daily Users: All DPAS users of WM |
|
| 02088 | Add Negative Report to Reconciliation Reports | Warehouse | NSWC | New | Change Request: Process Improvement
Description: DODIG/IPA Audit FY23 resulted in a Notice of Findings and Recommendations to NSW due to not being able to submit negative inventories to prove active warehouses that did not contain assets during required inventory periodicities. Recommended: Add the statement "Negative Report" to show the Warehouse Physical Inventory Reconciliation Report Detail and Warehouse Physical Inventory Reconciliation Report Summary when a physical inventory is conducted on a Warehouse does not have inventory in the Warehouse. Mission Critical: Benefits: DODIG/IPA Audit requirement to create and retain negative report inventory. Frequency: Monthly Users: All Users |
|
| 02087 | Add Purpose Code to ICP and Warehouse | Warehouse,Materiel Management | Leidos | In Progress | Change Request: Policy/Regulatory
Description: DPAS does not currently support segregating materiel in its ICP or Warehouse applications by Purpose Code. DPAS was designed to use Owning DoDAAC and Project Code to support the USMC CSP and Storage Command operations. At that time, USMC stated they did not use Purpose Code. Post the initial implementation, USMC requested Purpose Code. To support the immediate need, USMC requested with DPAS agreeing to open / use the Secondary Serial Nbr to identify the purpose. This capability does not allow for systematically segregation / selection of assets by purpose code, thus DPAS needs to add Purpose Code to its ICP and Warehouse applications to bring the system into compliance with DoDM 4140. Recommended: The recommended solution is to add a Purpose Code field to the DPAS ICP and Warehouse application and to update the DLMS traffic to support it. This change may necessitate changes to the inventory row business key, user processes, inquiries, reports, and interfaces. The change that are implement should ensure that DPAS aligns to DoD regulations, including the restriction against using alpha Purpose Code O. DLMS transactions will be updated to include Purpose Code. With purpose codes being agency specific, DPAS will need to provide the capability for different codes / descriptions / agency. Mission Critical: DLM 4000.25, Volume 2, September 15, 2024AP2.4. APPENDIX 2.4 - PURPOSE CODES https://view.officeapps.live.com/op/view.aspx?src=https%3A%2f%2fwww.dla.mil%2fPortals%2f104%2fDocuments%2fDLMS%2fManuals%2fDLM%2fV2%2f0202.04-v2a2.04.docx&wdOrigin=BROWSELINK Benefits: Adding Purpose Code functionality will improve inventory management by allowing better categorization of assets. It will enhance regulatory compliance, improve reporting accuracy, and provide operational clarity by reducing ambiguities in inventory records. This change also positions DPAS for future scalability and system enhancements. Frequency: Daily Users: All DPAS users. Approximately 27,000 users. Partially Completed - 2025.1.4
Partially Completed - 2025.1.5
Partially Completed - 2025.1.6 |
Disclaimer | Accessibility