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 |
|
|---|---|---|---|---|---|---|
| 01926 | Manual removal of downloaded files | FSM | AF: A4/HAF FH-AFHAF | Removed | Change Request: Process Improvement
Description:
DPAS FSM queue does not offer a manual removal process for downloaded files.
Recommended:
DPAS FSM queue automatically deletes files after a specified period (weekly) but also needs an option to manually remove files from the list. This will reduce errors when multiple files are queued and when errors are made in the download file.
Mission Critical:
-
Benefits:
Uncluttering of downloaded files from the queue.
Frequency: daily
Users:
200+Cancelled 09DEC2025 - per email submitted by Emily Escobedo |
|
| 01925 | Upcoming Maint Report (Utilization) and Overdue Maint Report | MU | AF: VSCOS | New | Change Request: New System Process
Description:
Upcoming Maintenance Schedule report (WPMAR20R) does not factor maintenance schedules tracked solely by utilization or provide a projection of when asset will come due by utilization in the future. Additionally, the report does not identify assets overdue if they’ve exceeded the Next Util Qty, only flagging as overdue if exceeding the Next Maint Date. Users attempting to project when assets are due by utilization must pull several inquiries such as asset utilization to determine upcoming maintenance. Further, users attempting to identify overdue maintenance must run a separate Upcoming Maintenance Schedule report using backdated Next Maint FROM and TO dates that have passed, i.e. From 1 January 2016 To current date. This process adds additional workload to the user and does not capitalize on system efficiencies.
Recommended:
Recommend updating the Upcoming Maintenance Report and creating a new Overdue Maintenance Report. The upcoming maintenance report should include all schedules whether tracked by date, utilization, or both. System should project a date when an asset will reach it’s Next Util Qty based on the average monthly utilization recorded for the asset. The overdue maintenance report should retrieve all assets with a Next Maint Dt exceeding current date and/or current meter reading exceeding Next Util Qty. Report should include all records regardless of work order status and should not drop a record until the Next Maint Dt and/or Next Util Qty are updated and current. Both reports should include data points relative to schedule maintenance allowing the user to easily identify maintenance requirement.
Mission Critical:
DAF Instruction 24-302 and Technical Order 36-1-191 establish serviceability standards and schedule maintenance intervals. It is critical for mission readiness to complete schedule maintenance on-time and maintain serviceability.
Benefits:
Implementing this change will ensure fleet manager have full visibility of requirements and greatly reduce past due requirements. Proper preventative maintenance will reduce sustainment costs and extend asset's service life.
Frequency: Monthly
Users:
Implementing this change will ensure fleet manager have full visibility of requirements and greatly reduce past due requirements. Proper preventative maintenance will reduce sustainment costs and extend asset's service life. |
|
| 01924 | Tier Selector Design Enhancements | Enterprise | Leidos | Done | Change Request: Process Improvement
Description:
The DPAS user community requested design enhancements to the recently-released React card-based tier selector. The enhancements include: faster methods to search for and select a Tier by auto-selection from the search results and double-clicking the card to select the Tier, enhanced the search to use 'contains' search capability, tier organization in the WM module to be grouped by Region, add number of Items per Page functionality to the footer, add diagnostics to determine how long requests and responses are taking, applying the new Tier selector across all DPAS pages and more.
Recommended:
All pages across DPAS will apply the new React card-based tier selector, the tier organization will include the second-level grouping (e.g., WM Region), where applicable, for improved organization of cards, a double-click action on a card will select the tier and close the modal, the footer will be enhanced for improved paging experience, diagnostics for requests and responses from the application will be added and the search functionality will be improved.
Mission Critical:
The new card-based tier selector is essential for the DPAS tech refresh, and provides improved functionality.
Benefits:
The Tier selector will provide a fast, easy way for users to locate and select the desired tier.
Frequency: Hourly
Users:
All modules - All usersPartially Completed – Release 2023.3.3 – 11 August 2023
Partially Completed – Release 2023.3.5 – 08 September 2023
Partially Completed – Release 2023.3.6 – 22 September 2023
Completed – Release 2023.4.3 – 03 November 2023 |
|
| 01923 | Integrate MRO Shipping with the FEDEX small parcel carrier | Warehouse | US Census Bureau | New | Change Request: New Process
Description:
DPAS does not provide shipping support for small parcel carriers such as USPS, FEDEX, and UPS. The Census Bureau ships to its field offices via small parcel carriers. By DPAS not having a shipping capability, this requires dual input several times to exchange information with the FEDEX website and DPAS management of the shipment.
Recommended:
Recommend DPAS develop a shipping process that will consolidate orders by shipping address (AAC) and integrate those shipments with FEDEX using the available FEDEX APIs.
Mission Critical:
This is a new system capability.
Benefits:
Reduces the level of effort to perform a shipment, and increases accuracy, and automates the tracking of shipments.
Frequency: Daily
Users:
This change would streamline small parcel shipments for Census Bureau and possibly other users of DPAS that preform similar shipments. |
|
| 01922 | Add AUIC to Agency PreDefined CFO | PA | AF | Done | Change Request: Process Improvement
Description:
Currently the Agency Pre-defined CFO Asset Detail extract under the Inquires tab does not include the AUIC on the report.
Recommended:
Include the AUIC as part of the Agency Pre-defined CFO Asset Detail Extract
Mission Critical:
-
Benefits:
Makes it easier for users to identify AUIC assets are managed under
Frequency: Monthly
Users: 200
Completed – Release 2023.2.7 – 30 June 2023
|
|
| 01921 | Print UII on Forms | Enterprise | DISA | New | Change Request: Process Improvement
Description:
The UII and serial number combination are only visible if running an asset inquiry. DPAS does not appear to
allow the user to search for the UII directly. Recommended:
We request the UII be printable on all forms (DD Form 1149, 1150, etc) and the printed bar codes
Mission Critical:
Per the DoD 8320.03 and Mil-STD-130N, the UII is to be made visible.
Benefits:
The benefit to this solution will be further standardization of government property, more productivity through
the time saved to research equipment, and more accuracy with property accountability. Frequency: Daily
Users:
The UII function is used daily by both contractors and government employees. |
|
| 01920 | Contract Number Sort Order | Enterprise | DISA | Done | Change Request: Process Improvement
Description:
When updating a loan code under the Asset Management-->Update-->Loan Update option, the "Cntr Nbr/Dlvry Ord Nbr" list every contract added under the Master Data-->Contract field. DISA has numerous contract numbers within this list and scrolling amid all the numbers is trying to find the proverbial needle in the haystack.
Recommended:
We recommend setting a parameter within DPAS that sorts the contract and/or delivery number, inputted under
Master Data-->Contract menu, to be sort in numerical order. Mission Critical:
DoD 8320.03 and Mil-STD-130N
Benefits:
The benefits of implementing this solution are increased productivity due to a time reduction in searching for
applicable contracts, better accuracy of contract information when the loan code is changed, which further leads
to update records in PIEE/WAWF, and improved property accountability during the contract closeout process.Frequency: Daily
Users:
The Contract/Delivery Order number option affects every DPAS user that has any involvement in the Government Furnished Property/Equipment program. Completed – Release 2024.3.1 – 12 July 2024 |
|
| 01919 | Cntr Nbr Dlvry Ord Nbr Inquiry Field | Enterprise | DISA | New | Change Request: Process Improvement
Description:
The "Cntr Nbr/Dlvry Ord Nbr" numbers are only visible under the Asset Management-->Update-->Loan Update menu. However this creates confusion when performing an inquiry between the "Cntr Nbr" and "Cntr/PO Nbr" fields and understanding which number correlates to the PWS contract.
YUP
Recommended:
Add an option to select the "Cntr Nbr/Dlvry Ord Nbr" should be a visible option to select when performing an
inquiry. Mission Critical:
DoD 8320.03 and Mil-STD-130N
Benefits:
The primary benefit of implementing this solution is data accuracy. As previously stated, currently there is some confusion between the "Cntr Nbr" and "Cntr/PO Nbr". This confusion interferes with both our government and contractor customers understanding the information and the solution would mitigate the risk of inaccurate information with our workarounds to overcome this obstacle.
Frequency: Daily
Users:
This action affects all DPAS users from the Accountable Property Officers and Property Administrators to the |
|
| 01918 | Expand Contract Types Configurations | Enterprise | DISA | New | Change Request: Process Improvement
Description:
Various contract number sequences cannot be properly added under the correct contract type within the "Master
Data/Contract" menu. The only way to input certain contract types (i.e. OTA) is to use erroneous types (i.e.
Non-DoD Non-FAR) because the character sequence of the contract does not match the DPAS default.Recommended:
We request that the fields be changed to accommodate the input of alphanumeric characters ranging from 10 -
13 different positions in all of the different contract types. We also request that all contract types be checked to
determine whether or not they correlate with the standard uniform contract format number.Mission Critical:
Per DFARS 204.7003, the contract alphanumeric sequence ties directly into the contract type. We cannot provide accurate information on our part without an update in this field which causes an error.
Benefits:
The benefit is an improved accuracy of GFP/GFE data within DPAS. In addition to this, the accuracy may
resolve any information transmission glitches between DPAS and the GFP Module of WAWF/PIEE. Frequency: Daily
Users:
This action affects all components of DISA that have active contracts. |
|
| 01917 | Shipment ID Inquiry Field | Enterprise | DISA | New | Change Request: Process Improvement
Description:
The Shipment ID that appears after a loan code has been changed from G to C under the Asset Management-->Update-->Loan Code menu, does not appear anywhere else within DPAS to include "Shipment ID" when performing an Inquiry. The incoming/outgoing shipment IDs appear in WAWF/PIEE but not in DPAS. Also, when a return shipment is performed in WAWF/PIEE, the Shipment ID is also not visible.
Recommended:
We recommend either changing the alogrithms to allow DPAS to display all inbound/outbound Shipment IDs
under the Inquiry->Asset->Fields menu/option or incorporate another inquiry option that allows users to search
for both Shipment IDs going to and returning from WAWF/PIEE.Mission Critical:
DoD 8320.03 and Mil-STD-130N
Benefits:
The benefits of implementing this solution is better accuracy of tracking shipments (providing corresponding
information from both systems) for both government and contractor employees, improved property
accountability, and more accurate reportable information.Frequency: Daily
Users:
The Shipment IDs affect every DPAS user that handles Government Furnished Property and Equipment. |
Disclaimer | Accessibility