Description
Currently, when a Warehouse Transfer is completed from an issue facility (ex. NCR IIF) to a different warehouse (ex. NCR DC) for an item that is not on hand at that warehouse there is no back order notice being created for the requesting warehouse. This means the requesting warehouse has no notification that there request will not be filled.

Recommended
Recommending to add function that notifies the requesting warehouse that the item that they are requesting from a different warehouse wont be filled until that warehouse has the items to fulfill the request. 

Mission Critical
This will help notify the requesting warehouse that they will not receive items because the warehouse they are requesting from has no items on hand.

Benefits
This will increase warehouse visibility of incoming warehouse transfers.

Users
All IIF & UIF

11 Mar 2021 – cancelled per Jack Sanders
No Longer Needed.

Description: Ability to accept a parts file from current and future contracted Internet-Based Parts Management Systems (IPMS). Recommended: Short term, add the ability to DPAS to import parts files from current and future contracted IPMS.? Long term strategy, build interface with contracted IPMS where parts information is requested by DPAS user or pushed daily by IPMS to DPAS. Mission Critical: Mandated.? The IPMS will provide integration and data sharing / data import and export capability with the government?s Defense Property Accountability System (DPAS). To capture key sustainment data. As well keep current contracted parts agreement in place to support war fighters in AOR.? Benefits: The benefits of implementing this solution would include reduced time, cost, accountability, and financial reporting. Also, the current contracted IPMS wouldn't have to alter how they provide the parts file that is currently accepted into OLVIMS generating a cost for the AF due to contract modification. Users: Yes.? This change will affect all Vehicle Management units across the Air Force.

21Feb2025 – cancelled per Luther Meitzner
.

Description: 
Currently, when a user returns a serialized item other than their own (i.e. what was issued to them), their original serial number on the members record disappears and has no way of being tracked.

Recommended: 
Recommend adding a Serialized Suspense File to keep track of serial numbers that have not been returned. When a member returns a serial number other than their own issued serial number the system should automatically move that serial number into a serialized suspense file. This file should be placed in the "Inquiries" tab and should have all the same search-able parameters that "stock  number inventory" has.

Mission Critical: 
Yes.  This will help keep track of all serialized items, regardless of who turned in.

Benefits:
This will increase visibility of all serialized assets.

Users:
All IIF & UIF functions.

11 Mar 2021 – cancelled per Jack Sanders
No Longer Needed.

Description
Need to capture electricity (kWh) consumption of Electric Vehicles for FAST Reporting via manual input or odometer reading computation during Dispatch or Maintenance Asset Utilization.
Work around is manual computation and loading to DPAS.

Recommended
For assets with Fuel Association of 'Electric' only, electricity (kWh) consumption computation should be the difference in beginning/ending meter reading divided by 3.
This is the kWh expended during the vehicle dispatch and needs to collected and transmitted to FAST at end of FY.

Mission Critical
Mission critical and federally mandated for Federal Fleet Reporting.

Benefits
Accurate kWh reporting, reduces time for manual computations

Users

Completed - Release 5.2 - 29 September 2017

Description
Inability to account for Air Force own/GSA fuel purchases on and off base along with tracking meter updates automatically.

Recommended
Import the Fuel Use Report from DLA Customer Sales Report Billing (see attachment) and/or GSA Reports Carryout (whichever report gives us the most information) into DPAS for Government Owned and GSA assets to capture transactional data by vehicle. Using VIN, TAG and Fuel Code to accurately account for fuel to vehicle.
We we would like for DPAS to capture and update all pertinent fields (i.e. Report date, current meter, on/off base M/H/K, fuel type, Qty, cost) within DPAS and pass all data to GCSS data services warehouse.
SCR to add additional fields will come later (i.e Plate/tail number, card number if applicable)

Mission Critical
Mission Critical and Mandated.
All Federal Agencies are required to accurately capture, track and report fuel consumption and utilization data.
This data is also critical to making timely and informed Fleet Management decision on the local and enterprise levels.

Benefits
Process to constant update multiple vehicle assets fuel and utilization manually will be a tremendous burden on the Fleet Management community.

Users
We believe that this will have a positive impact to the Air Force and other agencies as well. This effort will reduce steps resulting in considerable man-hour savings, ensure more accurate and up to date fuel consumption and utilization data.

Completed – Release 6.0 – 27 April 2018

Worked on with SCRs 00985, 00736, and 00735

Completed – Release 6.3 – 21 December 2018

Description:
In DPAS version 3.2, when maintenance is completed on an asset, a Quality Control (QC) Inspection Form is created and sent to QC.  The current QC Inspection Form does not have a dedicated space to enter what maintenance was conducted on the asset.  This creates a work stoppage for QC personnel since they must then use an off-line process to find out what maintenance was conducted along with what should have been inspected. The first page has excess space and the second page has a relatively small amount of data.  A necessary revision of this form should expand current data fields while incorporating additional areas necessary to fully execute the form.  This will enable all information, including an additional field for listing the maintenance conducted, to be captured and printed on a single piece of paper.

Recommended:
It is recommended that Leidos add an additional field titled 'Required Maintenance' on the QC Inspection Form for the maintenance team to describe the maintenance conducted.  It is also recommended that Leidos reformat the current form in order to align all fields to fit on a single page.  A Microsoft Word document is attached that shows the current layout and the envisioned format that should optimize the functionality of this form.

Mission Critical:
This is mission critical since the lack of information impedes work flow in QC.

Benefits:
Revising this form will streamline the processes necessary for QC to complete an inspection report.  This change will also be beneficial by reducing the time to complete this task which consequently reduces direct labor cost and additionally decreases use of office supplies. 

Users:
This affects all QC inspectors.

11 Mar 2021 – cancelled per Jack Sanders
No Longer Needed.

Description
Currently DPAS only allow attaching file size of 2MB for an individual attachment, MDA is requesting increase size to 10MB per attachment.

Recommended
Increase file attachment size from 2MB to 10 MB to minimize redundancy of attachment of multiple files. Currently if you add 5 attachments at 2MB its gives you 10MG, if you add 1 attachment at 10MG you have 1 attachments versus 5 attachments. This will also eliminate at least 20 processes from completing the action.

Mission Critical
Mission Critical.? MDA is mandated by Congress to be audit ready by FY 17. MDA currently has over 178,000 assets in account AAUZ00, each assets requires source documentation attached to each asset, some assets has multiple attachments which take an excessive amount of time to complete the action.

Benefits
This update would Reduce Time and Improve accuracy/accountability of all MDA assets.

Users
This will affect all Property Accountability users of DPAS.

NOTE
The original SCR request was for PA, but, per Ryan Steele, the setting should be consistent throughout all modules (including WH).

Completed - Release 5.2 - 29 September 2017

Description: Per MCO 8300.1.D, paragraph 4.b.5.c, all USMC shipments on DD1348-1s for weapons are required to list Serial Numbers (SNs) in numerical sequence. Currently DPAS does not provide the user the option to list the SNs in sequence nor the option to sort by sequence prior to printing the DD1348-1. Recommend: Provide the DPAS user the ability to sort SNs by numerical order prior to printing the DD1348-1. Mission Critical: Yes. It is directed by MCO 8300.1.D paragraph 4.b.5.c Benefits: The benefit is this process is compliance with USMC Directives, reduce time in verifying SNs at time of shipment, then receipt, verifying and accepting at destination and eliminating possible errors in duplicate inventory numbers. Users: This effects ALL users within the USMC.

Completed – Release 2022.1 – 08 April 2022

Description
DPAS Excel exports are currently only available in compact form. This format prevents relative data from being displayed horizontally next to related fields, which are indented to show a nested relationship with the data directly below.? It is imperative for users to have the ability to export Excel files in an automated manner into tabular form so that all related records are viewable in a linear style.

Recommended
Users should have the option to choose whether they want DPAS Excel exports in compact or tabular format. Both formats are useful and needed by different parties and requires a mutually exclusive option to be available for each individual export. It is vital that there be an option to automatically export data to Excel in either format.

Mission Critical
This is mission critical for users. The current compact format is rendering the users unable to compute required metrics and to perform analysis of inventory and transactional records in a fast and accurate manner.

Benefits
This solution will greatly reduce the time to prepare exports of data which consequentially results in a significant reduction in labor cost and allows users to complete tasks more efficiently. Most importantly, a solution directly from the software system itself will improve the accuracy of the exported information in report creation, computing, and analysis of data to effectively eliminate the possibility of user error as this can occur when manually converting records from a compact format to tabular format.

Users
This affects all Systems Analysts and 20% of Warehouse Management users.

Removed per Norman Clark email on 5 June 2025