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 |
|
|---|---|---|---|---|---|---|
| 01976 | DPAS .NET 8 Update | Enterprise | Leidos | Done | Change Request: Policy/Regulatory
Description:
Microsoft has announced the end of life "EOL" for .NET 6 as 11-12-24. DPAS has applications that are using this .NET 6. These will need to be updated to .NET 8 (Latest LTS Version). .NET 8 has a scheduled EOL of 11/10/2026.
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core Recommended:
Update applications to .NET 8
Mission Critical:
DoD is not authorized to operate software that is EOL. Failure to complete the upgrade will result in DPAS not receiving security patch updates / support.
Benefits:
Maintain DPAS compliance
Frequency: Daily
Users:
All usersPartially Completed – Release 2024.2.3 – 03 May 2024
Partially Completed – Release 2024.3.2 – 26 July 2024
Partially Completed - Release 2024.3.4 - 23 August 2024
Partially Completed - Release 2024.3.5 - 06 September 2024
Partially Completed - Release 2024.3.6 - 20 September 2024
Partially Completed - Release 2024.4.1 - 04 October 2024
Partially Completed - Release 2024.4.2 - 18 October 2024
Partially Completed - Release 2024.4.3 - 01 November 2024
Completed - Release 2025.2.1 |
|
| 01975 | M&U Local Catalog | MU | AF: A4/HAF FH-AFHAF | New | Change Request: New System Process
Description:
Problem: We have assets that are standard across the enterprise and assets that are specific to a maint activity. We need the ability to maintain standard stock numbers for assets and give maint activities the flexability to add local stock numbers for assets that are only applicable to that maint activity
Recommended:
Give the option to have a maint group catalog and/or a maint activity catalog
When adding assets via MAM > add MU only asset, the stock nbr browse will have a drop menu to choose which catalog to search for a stock nbr.
The catalog menu will have a link for the group catalog, and a link to the maint activity catalog. You will only see both links if you have access to both catalogs
PA catalog will only be accessible via PA and no longer accessible via MU
Make the profile process part of the new cataloging processMission Critical:
Benefits:
This will allow Maint Activities to track maintenance and utilization on "non-accountable" assets that are not in the PA module.
Frequency: Daily
Users:
All users across the enterprise |
|
| 01974 | Allowable Special Characters | Warehouse | Leidos | Done | Change Request: Process Improvement
Description:
Update the DPAS Warehouse Module to allow special characters.
Warehouse AUD - Allow ( ) in the Warehouse Name
Commodity Type AUD - Allow & in the Commodity Type name.Recommended:
Allow above special characters in the proposed fields.
Mission Critical:
Benefits:
Allow better data for users.
Frequency: Weekly
Users:
All users.Completed – Release 2023.4.6 – 15 December 2023 |
|
| 01973 | Apply Multiple Force Elements to UIC | FSM | AF: A4/HAF FH-AFHAF | Removed | Change Request: New Process
Description:
Currently DPAS only allows for one Force Element to be applied to a UIC. This hinders the capability from creating more than one Force Element for the enterprise to utilize to posture authorizations
Recommended:
Enable the capability for a UIC have more than one Force Element management
Mission Critical:
Benefits:
As an enterprise we have determined establishing a separate Force Element to manage War Reserve Materiel (WRM) Support Equipment (SE), allowing for the Global Managers to manage all SE. This would include Commercial off the shelf (COTS) and centrally managed/centrally procured SE, this will allow the WRM Global Managers to establish authorizations and have a realistic picture of WRM requirements. In some cases a unit will have standard authorizations and WRM authorizations which are managed in separate Force Elements
Frequency: Daily
Users:
20 UICsRemoved Per Emily Escobedo 15 November 2024 |
|
| 01972 | Add Secondary Serial Number to Upcoming Maintenance Schedule Report (WPMAR20R) | MU | AF: A4/HAF FH-AFHAF | New | Change Request: Process Improvement
Description:
Users need the Secondary Serial field added to the Upcoming Maintenance Schedule (WPMAR20R) report located in Forms-Reports> Schedule Reports.
Recommended:
Add the Secondary Serial number field to the report.
Mission Critical:
Benefits:
Users will be able to ID the assets due for Scheduled Maintenance easier with the added field than bouncing ITM numbers off MAM to know the asset needed.
Frequency: Weekly
Users:
All users. |
|
| 01971 | Add Unique Item Designator to PA Asset Inquiry | PA | Leidos | New | Change Request: Process Improvement
Description:
User are not able to select assets using the Unique Item Designator. With the Air Force having 1000s of SA/LW in DPAS, there is a requirement for the program manager to be able to view what the AF has and where they are located (what Unit has what). The easiest solution would be to add the Unique Item Designator to the Asset Inquiry (filter and as a data element to view.
Recommended:
Add Unique Item Designator to the PA Asset Inquiry (filter and view).
Mission Critical:
DPAS added Unique Item Designator to the Stock Nbr record. We now need to be able to filter the asset inquiry using this value.
Benefits:
Provides for a timely report of SA/LW without having to extract the entire AF property book or submit help ticket to have DPAS run a 1 time extracts, which are obsolete when they received as SA/LW are constantly being received and turned in.
Frequency: Weekly
Users:
All users with weapons on their Hand Receipts (Custodian reports). |
|
| 01970 | Exclude Allocations from Available Inventory | Materiel Management | DLA | In Progress | Change Request: Process Improvement
Description:
Within Customer Requisition, Disposition Release Order, and Redistribution Release Order, the qty available for issue by warehouse does not take into account the qtys that allocated to previously approved CRs, DROs, RDOs which is resulting in the overstatement of available inventory. Thus it is allowing the release of orders to the warehouse that cannot be fulfilled.
Recommended:
Modify the viewer that contains the qty available to issue to subtract the allocated qty that was assigned to prior CRs, DROs, RDOs that have been approved that have not yet been issued.
Mission Critical:
The current process is not displaying the correct available qty when there are outstanding CRs, DROs, and or RDOs.
Benefits:
Eliminates denied shipments by the Warehouse. Provides an accurate view of inventory that is available for issue.
Frequency: Hourly
Users:
WIth USSOCOM and ASA(ALT) being large users of the Materiel Mgmt module this change will improve the user experience.Partially Completed - Release 2025.1.6 |
|
| 01969 | Asset Receiving for Previously Disposed Assets | PA | DLA | New | Change Request: Process Improvement
Description:
Currently when a user attempts to receipt for an asset that previously existed in the PA Module (current state is deleted), the prior owner must receipt for it, then transfer it to the gaining activity that now has it. This method is an inefficient process. When the prior owner turned the asset in, and it was subsequently reissued to a new UIC, the new UIC should be able to receipt for the asset without having to contact the prior owner, which no longer has responsibility for it.
Recommended:
Mission Critical:
Benefits:
This change will eliminate the new owner having to try to track down the previous owner to have them reverse the disposition which was the correct action for them at that time. It also enables the new owner to receipt without waiting for the reversal to occur.
Frequency: Weekly
Users:
With Air Force being the largest customer of the PA module, and the large quantities of equipment being returned to the wholesale level for storage/refurbish/re-issue, this SCR will be beneficial.
|
|
| 01968 | Decentralization of Work Plan Types & Work Order Reason Codes | MU | DLA | New | Change Request: Process Improvement
Description:
Currently Work Plan Types and Work Order Reason Codes are established at the DPAS enterprise level. While that sufficed for common/like Maintenance organizations that DPAS supported in the past, it no longer effective in supporting the diverse group of DPAS maintenance users that DPAS supports today. Given the diverse groups of users, there is a requirement to have unique work plan types / work order reason codes that are applicable to the type of equipment being supported, e.g. IT, Vehicles, Machine Tooling, Warehousing Systems, etc.
Recommended:
Replace the current enterprise management of work plan types and work order reason codes with collections that are assigned to the Maintenance Activity level, thus allowing each maintenance activity to have their own unique work plan types / work order reason codes, and /or share a common list that their parent command has established for their maintenance activities to use.
Mission Critical:
Benefits:
The enterprise wide management of these lookup values decreases productivity having to select the applicable type / reason from a large list which also leads to a greater chance of selecting the incorrect value. By having a targeted list applicable to the mission of the maintenance activity will reduce the time to create a work plan / work order in addition to providing for greater accuracy in the selection
Frequency: Hourly
Users:
There are currently in excess of 10K Maintenance users that use these processes throughout the day. |
|
| 01967 | Appropriation AUD Enhancements | Materiel Management | Leidos | Done | Change Request: Process Improvement
Description:
The Appropriation AUD screens and use of appropriations in the Materiel Management/ICP module require changes for future enterprise accounting in DPAS. Changes include using imported DAI POET data to associate with fund codes and assign to financial obligations; removing fields from this process that should not be on the appropriation AUD; and updating field labels to match current DOD SFIS, SLOA, and DLMS nomenclature, e.g., Main Account Code will replace Basic Symbol. Fields that will be removed from the Appropriation AUD will be used in other UI processes specific to those fields. For example, the cost center field will be removed and a cost center AUD process will be used for assigning cost centers to financial obligations (see SCR 01964).
Recommended:
Update the Appropriation AUD screens in the Materiel Management module to make necessary field changes and allow for imported DAI POET data association to fund codes in the Appropriation AUD process.
Mission Critical:
The data elements in DoD OUSD SFIS guidance, Standard Line of Accounting business practice, and DLMS implementation business rules use modern nomenclature currently not used in DPAS. In addition, DoD FMR 7000.14R requires certain data elements to be used in accounting processes that are currently incorrect on the appropriation screens in the MM module.
Benefits:
DAI imported POET data will be available in the MM module; the MM Appropriation AUD will have improved functionality and correct fields as well as updated nomenclature.
Frequency: Weekly
Users:
Data established in this process is used by Accounting users on a regular basis. This will impact enterprise accounting which will affect a growing number of users as more use the accounting processes in MM/ICP.Partially Completed – Release 2024.1.4 – 23 February 2024
Partially Completed – Release 2024.1.5 – 08 March 2024
Partially Completed - Release 2024.3.4 - 23 August 2024
Partially Completed - Release 2024.3.5 - 06 September 2024
Partially Completed - Release 2024.3.6 - 20 September 2024
Completed - Release 2024.4.3
|
Disclaimer | Accessibility