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 |
|
|---|---|---|---|---|---|---|
| 01806 | Support for Warranty & Service to M&U Work Order | MU | Leidos | New | Description:
Provide the ability to associate warranties, subscriptions, or service contracts to an asset and display the contracts within Work Order when the asset is used.
Recommended:
Create a Warranty/Subscriptions service that can be used to create a Warranty/Service/Subscription contract and then allow for the contracts to be associated to one or many asset ids within maintenance. When an asset id that has Warranty/Service/Subscription contracts associated is used for a Work Order display the contracts in a Warranty/Service/Subscription panel within the work order so the user can view the contract terms.
Mission Critical:
Mission Critical. Numerous assets fall under warranty/subscription/service contracts that effect the types of work that will be done within a specific work order. Having this information available within the work order process will ensure the proper maintenance of assets.
Benefits:
Enables user awareness to specific warranties/service/subscription contracts that may limit the scope of a work order and ensure proper maintenance of the assets within a Maintenance Activity.
Users:
ALL
Partially Complete - Release 2022.2.3 - 07 October 2022 |
|
| 01805 | Deferred Tasks/Parts | MU | Leidos | Done | Description:
Work Orders cannot be closed when it includes outstanding parts requests. Allow for a work order that includes outstanding parts requests to be closed, and maintain the requirement for the outstanding parts for the associated Asset for future work orders.
Recommended:
Allow the user the ability to defer a task and select the outstanding parts that are no longer needed as a result of the deferred task. Maintain a record for the Asset ID of the tasks/parts that were deferred and alert the user of these deferred tasks on future work orders where the same Asset ID is used and allow for them to be added for the new work order.
Mission Critical:
Mission Critical. Priority for specific parts requests can change after a work order has been created to request those parts even while the parts are still needed. Without the ability to defer parts request either the Work Order would need to remain open and inhibit use of the associated asset or it would need to be closed and the part requirement would be lost.
Benefits:
Improves the use of the Work Order process to accommodate changes in demand of Assets in relation to the priority of parts requests. This part of the DPAS modernization effort.
Users:
Maintenance & Utilization - Work Order
Warehouse Mgmt - Maintenance Issue
RequisitionPartially Completed – Release 2022.3 – 04 November 2022
Completed – Release 2023.1.3 – 10 February 2023 |
|
| 01804 | Add asset ID and corrected cost to DD Form 1150 | Warehouse | USAF | New | Description:
When completing a maintenance issue within DPAS Warehouse, the DD Form 1150 does not show asset ID or reflect correct unit price. Unit price corrections are made within maintenance issue pick process if necessary and remarks added. Asset ID display within asset ID block and correct unit price on form ensures proper documentation. Additionally, the DD1150 block 5 Request Number reflects the M&U Work Order Id and block 7 Document Number reflects the Parts Request number. These fields do not directly translate to data fields within the M&U and Warehouse module.
Recommended:
Update the DD1150 process to reflect the following: Block 9 (2) Asset Id – populate with the Asset Id from the M&U work order Block 9 (8) Unit Price – populate with the Unit Price adjustment during the pick process Block 5 Request Number – populate with the Part Request or Document Number from the Warehouse Maint Issue Block 7 Document Number – populate with the Work Order Id number from M&U requisition
Mission Critical:
It is critical to capture accurate data when documenting expenditures against assets within the M&U and Warehouse module. Agency sustainment budgets based on data within DPAS.
Benefits:
Having the DD1150 capture accurate data improves budget auditing expenditures and asset life cycle sustainment cost documentation. Auditing ensures financial reporting accuracy and creditability for Department of the Air Force (DAF) budget requirements.
Users:
This affects all Agency's and we believe this function will benefit all. |
|
| 01803 | DLMS Quarantine AUD | Enterprise | Leidos | New | Description: DPAS developed a DLMS Quarantine process that enables the DLMS processor to bypass specific DLMS transactions based upon the the Transaction Set Nbr and Sender. The quarantine process is currently managed through scripting. Scripting is a slow method to add / remove items to the quarantine list when the DLMS queue fills and requires immediate attention, and there is currently no visibility of what is in quarantine without executing a script. |
|
| 01802 | Location Condition Code Default | Warehouse | AF: DF-VEHS | New | Description:
DPAS Warehouse limits Location Condition Code for a stock number to one Location Id. When receiving multiple quantities of a stock number under a single document, all will default to the single location and then need dispersal to various locations. Each warehouse will have multiple locations that require the same stock number and have a single Due-in, Backorder, or Return created to replenish or restock the items.
Recommended:
Allow multiply Location Condition Codes for same stock number. Enables user to chose several locations by quantity they would like to receive/return stock numbers streamlining process.
Mission Critical:
This is not critical or mandated, however improving system efficiencies decreases time warfighter spends performing non-wartime tasks
Benefits:
Automation provides a time reduction searching commonly received stock numbers for warehouse location replenishments (e.g.,individual issues). Additionally, potential to eliminate or reduce misplaced items within warehouse. Allows warfighter to focus on critical mission tasks vs. assigning warehouse replenishment locations.
Users:
Yes |
|
| 01801 | DPAS .NET Core 6.X updates | Enterprise | Leidos | Done | Description Microsoft has announced the end of life "EOL" for 3.1 .NET Core as 12-13-22. DPAS has templates that are using this version that will need to be updated to the .6 NET Core version (current) .6 NET Core has a targeted end of life date of 11/12/2024.
Partially Completed – Release 2022.3.1 – 18 November 2022 Partially Completed – Release 2022.3.2 – 02 December 2022 Completed – Release 2023.1.3 – 10 February 2023 |
|
| 01800 | Custodian Attachment | PA | Navy | New | Description:
Asset custodians are required to be designated in writing and supporting documentation is also required to be uploaded to the APSR. Currently, DPAS does not allow attachments when adding or updating a Custodian. Having the ability to attach Custodian designation letters and Custodian turnover forms to a Custodian in DPAS would solve this issue.
Recommended:
Add the option to include an attachment when adding or updating a Custodian.
Mission Critical:
Yes, Custodians are required to be designated in writing and supporting documentation is required to be uploaded to the APSR.
Benefits:
existing policy. This will also improve auditability by making it easier to access the documentation remotely which will also reduce the time/effort required when this documentation is requested.
Users:
This affects all NAVY and DODEA users and likely other services that use the Property Accountability Module in DPAS. |
|
| 01799 | Data Request Timestamp Addition | Enterprise | USMC | Removed | Description: After reviewing the DPAS tables within EGEM and the MDR, they are not the same as to what we are being provided. We are being provided an inventory file which contains all material that the Marine Corps owns within DPAS regardless of Program. We are requesting 2 additional Datasets that are being provided to the MDR ( DPAS_INVENTORY and DPAS_INV_ACTIVITY). As well as an activity report that coincides with the new DPAS ASSET dataset.
Removed per Norman Clark email on 5 June 2025 |
|
| 01798 | DPAS Account lock ability for Annual User Audit | Enterprise | Leidos | New | Description:
For accounts that are suspended due to non-compliance of the Annual User Audit, we do not have a way to lock these accounts from being reset until is appropriate. When user accounts are suspended (active box unchecked) because the IO group has not provided a response for the Annual User Audit, there is nothing preventing Help Desk support from being able to reset the account unknowingly. I am proposing a lock feature or new status ability be given to assist Security Officers with audit compliance. The Help Desk should retain their currently ability to reset accounts; however, we also need a method that allows for Sec Officers to lock particular accounts that can only be unlocked by a Sec Officer.
Recommended:
Provide ability to lock certain user accts from being reset until IO completes Annual User Audit. Potentially a new status or lock feature that only Security officers could update those particular accounts back to active status when appropriate.
Mission Critical:
This functionality supports audit readiness.
Benefits:
The solution supports audit readiness and user review compliance so that users do not get access to their account before they should.
Users:
This change would impact internal support staff. |
|
| 01797 | UIC Update and Migration Request | PA | USSOCOM | New | Description:
Current PA Module design does not allow for users to delete UIC's that were entered incorrectly, or to migrate/mass move UIC's from one Parent Structure and Accountable UIC to another.
Recommended:
Add capability in Property Management to perform UIC movement/migration, similar in concept to a Task Force Update process. This process will allow users with the proper roles to update/edit/delete/re-align UIC's. This will allow for organizations to transfer UIC's to a gaining organization without the need to laterally transfer items one at a time to the same unit that now falls under a different organization structure. Develop ability to delete UIC's entered incorrectly that have no assets assigned to them. Add capability to Update UIC assignment Major Command Codes
Mission Critical:
This is critical to using organizations such as the AFSOC community which has been re-organizing it's unit assignments.
Benefits:
The benefit is a reduction of bad data (UIC data tables) in the PA structure and the ability to rapidly re-assign UIC's and migrate the equipment and custodial data over to a new APO with no data loss. This will enable units deploying on short notice to re-align rapidly as needed.
Users:
This will apply to all users in the DPAS community that use the existing PA Module to account for their unit assigned equipment. This SCR request is related to the existing USAF SCR 01627. SOCOM is requesting additional UIC update capabilities than the originally requested. This change will also benefit the USAF and any other users of the PA Module |
Disclaimer | Accessibility