Description
In order to ensure transactions interface from DPAS to DAI, MDA reconciles reports from both systems.  Currently, DPAS Interface System Initiated report is only available in PDF format and makes it extremely difficult to validate transactions.  The process requires extensive steps in Exporting the PDF to Excel and utilizing formulas to attain necessary information. This is a timely process since Exporting PDF to MS Excel does not convert the same way each time.  Currently, it takes at least 4 man-hours to reconcile transactions between both systems; therefore, currently MDA only reconciles once a month.

Recommended
Converting the report from PDF to Excel will minimize the man-hours required to reconcile the DAI Accounting Interface Report and allow the users to perform the report on a more frequent basis.

Mission Critical
No: This action will allow for a more efficient work flow and minimize the man-hours required to reconcile the report. 

Benefits
All agencies that utilize the DPAS and DAI will benefit from the Excel format.  On average it will save at least 3 man-hours each time personnel reconciles reports between DAI and DPAS.   Additionally, reconciliation can be conducted on a more frequent basis (daily or weekly); therefore, any issues between DAI and DPAS will be identified in a timelier basis.

Users
This will affect the Accounting/Financial users of DPAS.

Description
When a production issue occurs with a suspended DLMS transaction, users with the DPAS Admin role are able to see such suspensions but lacks the ability to reprocess one. When conditions are corrected for a previously suspended DLMS transaction to process successfully, it is beneficial for the user with this role to be able to initiate the reprocessing of the transaction. This function is only available to Standard Users at this time, though few understand when and how to use it. In most cases, a DPAS Admin has to contact a user and ask them to go and reprocess a transaction(s) that are suspended. In some cases this has caused issues where the user chooses the wrong transaction to reprocess.

Recommended
Grant access to the DPAS Admin role(s) to enable the reprocessing of DLMS transactions that are suspended within the DLMS Transaction Review page of the ICP module.

Mission Critical
No, as Standard Users are able to perform this function today, the request would not be considered mission critical. This change will enhance Leidos' ability to provide quality support to it's customer base within DPAS.

Benefits
This reduces time for Leidos to resolve Production Issues and improves on the accuracy of those resolutions by removing the "middle man" who could cause further issues.

Users
This should only affect users with a DPAS Admin role within DPAS.

Description
Requesting that three additional data elements be fed to the Master Data Repository (MDR).
We would like the Catalog Inquiry, the Document Inquiry, and the DLMS Inquiry data be sent to the MDR. Ideally, all available columns from the Inquiry pages would be sent to the MDR.

Recommended
Adding these inquiries to the daily MDR feed.

Mission Critical
Yes, Adding these three inquiries would increase visibility of data to auditors. This would also create a historical archive of our catalogs which would assist in system analysis.

Benefits
Improves data reporting and accountability.

Users
All users in our agency who use the MDR on a daily basis.

Completed – Release 2022.2 – 26 August 2022

Description
Secondary Repairable Managers submit documents for repair or return assets to MCLB Albany for adjudication. They also request a replacement asset on the SAME DOCUMENT NUMBER to be returned to them. If the A5 document is worked in DPAS before the assets are picked up in Albany, it causes the receipt document to be PENDING until the A5 documents are shipped.  Once the shipping documents are processed completely, the receipt document can then be processed.
This is causing a backlog of documents to be processed and assets waiting to be adjudicated.

Recommended
Ability for DPAS to have same document for receipt and issue without being associated to each other.  Remove association between A5 and DW for same document number. 

Mission Critical
Mission Critical as it is delaying Secondary Repairable Operations. 

Benefits
Reduces document back up and assets are able to be stored.

Users
All users.

Removed per Norman Clark email on 5 June 2025

Description
Unit/Individual Reconciliation (Inventory Issued Assets): Posting the Platoon inventory is ALL or NONE. There should be an option to post a single or multiple serial number(s) and to “not post” any asset that is not accounted for (suspected missing or lost and being searched).

Recommended
Unit/Individual Reconciliation (Inventory Issued Assets): Posting the Platoon inventory is ALL or NONE. There should be an option to post a single or multiple serial number(s) and to “not post” any asset that is not accounted for (suspected missing or lost and being searched).

Mission Critical
Yes. Cannot complete/reconcile Platoon inventory if any item is unaccounted for or in suspected loss/under investigation status.

Benefits
Improves accuracy of issued items.

Users
Yes.

Completed – Release 2022.1.7 – 29 July 2022

Description
DPAS maintains master listings of DoD DoDAACs and RICs within the DPAS FED_LOG database.  DPAS receives a daily DoDDAAC file via DAAS GEX that provides new and updates to existing DoDAACs. DPAS processes the file and updates the DoDAAC Master table. The RIC Master table is not systematically updated.  Today, the DPAS team must take action to update it periodically, thus the RIC Master table is not as current as it could be which can result in processing / validation delays.

Recommended
It has been determined that the RIC data is also included in the daily DODAAC file that is received via DAAS GEX.  RICs are identified within the file as a DODAAC that begin with 'ZZZ'.   For example, a record with a DoDAAC value of 'ZZZA4J' contains the data for RIC 'A4J'.  DPAS needs to develop a process to extract the RIC data from the daily DODDAAC file received via DAAS GEX, and update the RIC Master table.

Mission Critical
Mission Critical, Newly added ICPs are not able to transmit DLMS transactions through DAAS to external trading partners because a it does not pass the RIC validation until DPAS manually updates the RIC Master table with the RIC data.

Benefits
Reduces time and effort/cost  for DPAS (Analyst/DBA analysis) and for the trading Partner (business interruption/analysis).

Users
Newly added ICPs cannot be used until Support updates the RIC Master table with the new RIC(s).  DLMS 527Ds (PMRs/Due In) records are send RIC to RIC.  These transactions require the RIC Master table to be current in order to allow processing to occur.  As more users implement these features, it is imperative that RIC Master table is current.

Completed - Release 2021.1

Description
Army has a requirement for Asset data for Army owned assets managed using the DoD's  Defense Property Accountability System "DPAS" beyond the data currently provided by the UIT interface.  This data will be used to populate the Army Vantage program to expand Army Vantage's mission set for assets and serials information.

Recommended
DPAS provide the Asset Extract feed for PA and Warehouse with the exception of the Real Property extracts.  The files will be made available through DAAS GEX.  It is requested the file be created daily.

Mission Critical
Mission Critical as per guidance for Army Vantage program

Benefits
Improves Army Vantage's ability to accomplish the mission

Users
All

Completed - Release 2021.2 -- 28 May 2021

Description
Property Administrators are required to attach documentation to each transaction within DPAS. At this time, they are unable to attach supporting documentation when performing transfers.

Recommended
Add the ability to upload attachments to affected asset records which are a part of transfer transactions.

Mission Critical
Yes. Per FIAR/FAR guidance, key supporting documents must be attached to each transaction within the APSR.

Benefits
This change would allow for better tracking of accountability, in that the associated documentation would be directly attached to the transfer transaction.

Users
Yes

Description
The DPAS Individual Issue process does not currently support issue by pRFID number. pRFID numbers are unique. By scanning the pRFID that is related to inventory, the issue can be made efficiently and accurately. The DPAS PM has requested that DPAS be able to provide a proof of principle (POP) to the U.S Coast Guard for their cadet clothing issues.

Recommended
The POP will consist primarily of bulk clothing, which could be hundreds/thousands of identical items being received. To support this POP, 1) DPAS will need a method to efficiently capture and associate the pRFIDs with the inventory during the receiving phase, or possibly have a separate pRFID process that could augment receiving, and 2) the goal would be to modify the existing Individual Issue process to enable the scan/capture of the pRFIDs that are attached to the items being issue displaying the Stock Nbr / Qty in the issue process. For the POP, it is not necessary to have DPAS create a process to assign pRFIDs to bulk materiel, or to implement pRFID into the Individual Return process. These modifications would only be needed should issue by pRFID become a core DPAS process.

Mission Critical
This is a DPAS PM requirement.

Benefits
Reduced manpower through automated scans, and improve accuracy

Users
All users who perform Individual Issues and have items tagged with a pRFID

Partially Completed – Release 2022.1 – 08 April 2022

Completed – Release 2022.1.2 – 20 May 2022

Description
There is a need to catalog local stock numbers outside of the standard NSN, MCN and part number formats.

Recommended
This involves creating a new stock item type code of 'L - LSN' and updating the catalog interface to allow the entry of the stock number - max length 15 characters with the validation:  alphanumeric with supported special characters $, -, /, \#, &, ;, (, ), comma, period, and space.  Impact to DLMS transaction processing will be minimized and addressed.

Mission Critical
mission critical

Benefits
Allows DPAS to support individual agency's cataloging policy requirements

Users
all users

Completed – Release 2020.3.3 – 4 December 2020