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 |
|
|---|---|---|---|---|---|---|
| 02086 | Catalog Data Script Reduction | PA,MU,Warehouse,Materiel Management,FSM | Leidos | New | Change Request: Process Improvement
Description: The DPAS Support team is spending a disproportionate time executing user requested catalog data updates due to DPAS not providing system functionality needed to enable the DPAS user to modify catalog attributes. These attributes often times have a financial impact when capital assets are being updated. The goal of this SCR is to enable users to perform the updates as needed with DPAS supporting the financial updates that are needed. Recommended: Review the business processes and determine when and where fields can be enabled for edit/change by the user(s), where obsolete data can be removed to avoid confusion and other opportunities to improve catalog data integrity instead of submitting help desk tickets or data script requests. Mission Critical: This SCR will incorporate additional user functionality within the catalog processes. The goal is to reduce customer support while providing the user with a more unified experience. Benefits: By enhancing the catalog in which users can manage their own stock nbr data, we will save time, improve accuracy and reduce data script requests. Frequency: Daily Users: All users who maintain catalog data. |
|
| 02085 | Historic Inventory Level Repository | Warehouse | USMC | New | Change Request: New System Process
Description: Currently, the system does not provide the ability to check the On-Hand Inventory status for previous dates. This is due to DPAS being a live system, where assets are constantly moving. As a result, researching inventory history, whether for routine inventory processes or resolving discrepancies, becomes impossible. To address this challenge, I propose the introduction of a Date Field to the Inquiry Screens for LIN/TAMCN, Stock Number, and ICN. This would allow users to pull inventory data for a specific location and view its status (e.g., quantity on hand) on any given date. Alternatively, another solution could be the implementation of a historical repository to capture and store inventory status at different points in time. This would provide a reliable way to track and query the inventory history as needed. The proposed enhancement will improve Users from ALL Agencies using DPAS ability to manage inventory discrepancies, streamline reporting processes, and ensure more accurate inventory auditing. Recommended: Recommendation 1: Add a Date Field to the Inquiry Screens Introduce a Date Field to the Inquiry Screens for LIN/TAMCN, Stock Number, and ICN. This enhancement would allow users to select a specific date and view inventory data as it appeared on that day, including the status of assets, quantities, and other relevant details. By enabling this functionality, it would be possible to track historical inventory movements, improving visibility and accountability. OR Recommendation 2: Implement a Historical Repository Develop a new historical repository that stores and tracks inventory data at specific points in time. This repository would allow users to pull detailed reports for previous dates to verify status information such as asset counts, quantities, contract IDs, and other key inventory details. By providing access to this historical data, it would become easier to resolve discrepancies and perform inventory audits efficiently. Both options aim to enhance inventory tracking and reporting capabilities, addressing the challenges of monitoring inventory history in a live system. Mission Critical: This process improvement will help immensely in the researching of discrepancies and researching for inventory accuracy. Benefits: This will help ALL agencies operating in DPAS as a whole to better manage and verify inventory accuracy and research any possible discrepancies. Frequency: Daily Users: Users across all agencies operating in DPAS. |
|
| 02084 | Received Date Additions | Warehouse | NSWC | New | Change Request: Process Improvement
Description:
The field "Receive Dt" is required on the Materiel Mgmt-->Receiving but we cannot view this field on asset inquiry. Received date is an audit requirement for General Equipment Assets.
Recommended:
Add a "Receive Dt" column in the Inventory Update Manager, ICN Inventory, and Inventory Activity. Add the ability to edit the "Receive Dt" field in the Inventory Update Manager.
Mission Critical:
Benefits:
DOD requirement.
Frequency: Hourly
Users:
All Users |
|
| 02083 | In Service Date Changes | Warehouse | NSWC | New | Change Request: Process Improvement
Description:
DoD Components are required to record and maintain data element "Date Placed in Service" in their respective APSRs as stated in DoDI 5000.64 and the USSOCOM Directive 700-2.
Recommended:
Add a "Date Placed in Service" required field during the receiving process. Add a "Date Placed in Service" column in the Inventory Update Manager, ICN Inventory, and Inventory Activity. Add the ability to edit the "Date Placed in Service" field in the Inventory Update Manager.
Mission Critical:
Benefits:
DOD requirement.
Frequency: Hourly
Users:
All Users |
|
| 02082 | FSM to Warehouse Interface | Warehouse,FSM | AF: A4/HAF FH-AFHAF | New | Change Request: New System Process
Description:
Currently the Force System Management Module only interfaces with the Property accountability module which is used to determine the DAF authorizations to build requirements. However, we require the capability to establish requirements for items that do not fall into the Class VII category and in some cases consumable materiel.
Recommended:
Establish the capability to create FSM authorizations for assets managed in the Warehouse module.
Mission Critical:
IAW AFI 23-101 The DAF is required to maintain Class II and Class IX materiel to support the wing's deployment requirements and report readiness capabilities. Establishing authorizations for materiel provides the DAF the capability to ensure the posture of materiel is appropriately aligned to and determine overages and shortfalls for future procurements or reposturing.
Benefits:
This would provide Senior leadership visibility of all DAF stockage/storage requirements and current posture to make strategic level decision.
Frequency: Daily
Users:
This requirement would be utilized at 224 bases to support enterprise requirements |
|
| 02081 | Custom Issued Inventory | Warehouse | USMC | New | Change Request:
Process Improvement Description:
According to SOCOM Directive 700-2 we are to conduct monthly inventory of All controlled, classified or sensitive Controlled Inventory Item Code (CIIC) items with codes 1-6, 8-9, P, Q, R, S, Y (including all Night Vision Devices and Navigational Devices) regardless of cost will be inventoried on a monthly basis.
Recommended:
Add additional selection parameters to the Issued Inventory under the Details section with the ability to select multiple Stock Numbers, CIIC codes, Commodity types, and Issued Warehouse. Enable the user to save selected stock numbers, CIIC codes, commodity types, and Issued Warehouse with the ability to name the saved selection. Enable the user to edit and delete saved selections. Enable the user to select a previously saved selection which will auto-populate Stock Number, CIIC , Commodity Types, and Issued Warehouse. Add a Select All UIC's under Select UIC to print all (multiple) issued inventory. The Stock Number, CIIC , and Commodity Type selection is default to all.
Mission Critical:
N/A
Benefits:
SOCOM requirement.
Frequency:
Hourly Users:
All UsersThis SCR was updated on 6/30/2026 at the request of Chia, Bernard |
|
| 02080 | Master Issue List for Individual Returns | Warehouse | USMC | New | Change Request: Process Improvement
Description:
The current problem is we have some members in DPAS that have multiple issues from different warehouses/locations. We need to be able to differential between the issues so we are able to return equipment to the proper warehouse/location, Proposed solution would be to have a way to designate the exact items from a particular warehouse/location. Possible Fix would be to add the Master Issue List(MIL) option on the individual return so you are able to pull the exact items the individual was issued from a particular warehouse/location.
Recommended:
Recommendation is to add a MIL option on the individual return so you are able to pull the exact items the individual was issued from a particular warehouse/location. Inserting the MIL, would allow the CSR to pull up the desired gear list to return.
Mission Critical:
Yes, because the Consolidated Storage Program (CSP) goal is to have an accurate inventory and with this functionality the customer service representatives (CSRs) will be able to conduct returns into the system with more truthful data.
Benefits:
Having this capability will help all warehouses improve on inventory accuracy across the enterprise.
Frequency: Daily
Users:
All IIF Facilities |
|
| 02079 | MAPAC Data Import | PA,Warehouse,Materiel Management | Leidos | New | Change Request: Process Improvement
Description:
DPAS continues to expand its customer base. As part of this expansion, there is a requirement to support shipments to foreign governments. These shipments are assigned a MAPAC (Military Assistance Program Address Code) which is equivalent to a DoDAAC. Today, DPAS permits the manual entry of a MAPAC, but there is no validation that what was entered is a valid MAPAC. DPAS provides a data feed of MAPACs similar to the DoDAAC data feed. This SCR is requesting DPAS add the MAPAC to its DLA DAAS agreement and provide for import / selection / validation of MAPACS from the master list of MAPACs.
Recommended:
Import MAPACs, provide the capability to select / validate a MAPAC that is entered to the master list of MAPACs. This change would apply to Materiel Mgmt, (Customer Requisition), Warehouse (Materiel Release Order). The requisition service would need a change to support MAPAC validate if it supports Military Assistance Program ordering. Asset Disposition in PA that utilizes the Address Directory will likely need to support Military Assistance issues.
Mission Critical:
This change improves / reduces the opportunity of error in the entry of a Military Assistance Program Address Code.
Benefits:
Improves the overall entry and validation of a Military Assistance Program Address Code.
Frequency: Weekly
Users:
This change would be used for all shipments for Military Assistance. It is not known how many organizations perform these types of shipments. The Army PEOs, USMC, and possibly USSOCOM would be the beneficiaries of this change. |
|
| 02078 | Notification of Change Contractor / Contract Data | Warehouse,Materiel Management | Army: ASA(ALT) | New | Change Request: Process Improvement
Description:
DPAS designed the Contractor / Contract processes for use with the Materiel Mgmt. and Warehouse Mgmt. applications to be enterprise. Once it is created, it is available for all to use. While this may be good (enter once / use by all), a user can also change the entries making them anything they want it to be not knowing the impact to other DPAS users. Providing an automated process that does not require Help desk support to correct incorrect data is good, but there can be negative consequences if not properly managed. The impact could result in be materiel on loan to a contractor be re-assigned to a different contract / contractor without the user knowing their data was changed.
Recommended:
It is recommended that DPAS review these processes for: 1) Restricting changes to those organizations that created them, 2) Notify the user who is making the update that the record they are updating is currently in use by other organizations, thus their change could impact the other organization's data and 3) notify all organizations that are using the record that was changed of the change. It is also recommended that there be consideration given to enabling an organization to identify contractor / contracts that they are using rather than having to see all contractors / contractors that have been entered. For example: A west coast organization that purchases materiel from LOWES has no need to see LOWES (CAGEs) that do not reside within their proximity. Having the ability to restrict the list to those an organization users will reduce the time required to enter a record (less data to review / select) and reduce the chance of selecting an incorrect value.
Mission Critical:
This SCR results from a change that occurred within DPAS production by one organization that was not aware that contractor / contract data was enterprise. They needed a new contractor and contract. Seeing ones they were not using, they modified them to be something completely different which impacted another organization's data that established the records and were in use. They didn't know their data was realigned to a different contractor / contract when the other organization hijacked their records. A change like this also impacts PIEE GFP reporting as the materiel is now assigned to an incorrect contract / contractor.
Benefits:
This solution enhances accuracy and may prevent an unwanted change that could take a significant amount of time to unravel and return the data to its correct state. The impact of an enterprise change by an unknowing user the size of DPAS with a diverse user base could have a catastrophic impact to another organization's data that could take a significant effort to undo.
Frequency: Daily
Users:
This solution would benefit all user utilizing the MM and WM applications. |
|
| 02077 | Custom Physical Inventory Selection Lists | Warehouse | NSWC | New | Change Request: Process Improvement
Description:
According to SOCOM Directive 700-2 we are to conduct monthly inventory of All controlled, classified or sensitive Controlled Inventory Item Code (CIIC) items with codes 1-6, 8-9, P, Q, R, S, Y (including all Night Vision Devices and Navigational Devices) regardless of cost will be inventoried on a monthly basis.
Recommended:
During the creation of physical inventory add an Inv Mode to create a custom inventory selection of multiple Stock Numbers, CIIC codes, and a Type Asset Codes. Enable the user to save selected stock numbers and CIIC codes with the ability to name the saved selection. Enable the user to edit and delete saved selections. Enable the user to select a previously saved selection which will auto-populate Stock Number, CIIC , and TAC.
Mission Critical:
Benefits:
SOCOM requirement.
Frequency: Hourly
Users:
All Users |
Disclaimer | Accessibility