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

Description
SAF/FM is constraining the CICP go-live dates in DPAS to the first day of a new quarter.  This places pressure on the CICPs, the GFM-A team and the DPAS implementation team into these four days each year.  In consultation with our DPAS support team, we have proposed establishing a transaction pilot period for each new ICP before DPAS enables the financial reporting to GAFS-R.  Currently, the DPAS reporting lever to GAFS-R is located at the Logistics Program level.  We propose lowering that reporting lever to the ICP level in DPAS.  This will enable us to implement new CICPs on any date without impacting financial reporting.  In addition, the GFM-A team needs the ability to change the beginning and ending dates on the reports in the ICP module (CFO Report, OM&S Trial Balance and Accounting Detail Report) to allow users to pull historical data including transactions for audits.

Recommended
The recommended solution is to move the GAFS-R reporting level in the ICP module from the Logistics Program level to the ICP level. ICP Officers within DPAS should be provided an interface that would allow them to turn the GAFS-R Reporting on or off for each ICP under their Logistics Program.  Remove the block from the beginning dates and ending dates from the financial reports in the ICP Module.

Mission Critical
This is critical to the implementation of the 100 AF CICPs; this removes constraints on all teams supporting the CICP implementations in DPAS.  Allows programs to provide transaction sets to auditors.

Benefits
This provides the ability to review CICP transactions for accuracy prior to sending financial data to GAFS-R.  It further provides the opportunity to correct any errors in the transactions.  Provides ability to provide transaction sets for reconciliation and audits.

Users
ALL AF GFM-A users

Completed – Release 2022.2 – 26 August 2022

Description
DLA is implementing DPAS Warehouse module to support receipt, storage, and issue of the Veterans Administration's PPE.
Currently there is no electronic communication of Requisitions / MROs. 
DLA does have a requirement to route the MRO to a TMO to have the materiel shipped (DLMS ADC 316 Functionality). 
It appears that the ADC 316 functionality within DPAS only works with external ICPs. 
The ADC 316 functionality is between the TMO and Warehouse and should not be dependent upon an ICP being associated to the Warehouse / Owning DoDAAC. 
There also appears to be an issue with the printing of Special Instructions. 
The allowable characters are insufficient, and it appears they only print when the continuation page is printed which is only printed when the MRO is for serialized assets and the Qty > 1. 
Special Instructions should print for all MROs when entered.
The TMO DLMS 945A needs to be reviewed to determine if all of the data is being extracted related to the shipment. 
This information needs to be extracted and included in the DLMS 945A to the ICP and 856S to the customer.

Recommended

1.   Review current ADC316 TMO functionality to ensure it functions with all MROs that contain a valid TMO RIC / Transportation Account Code (TAC).
2.   Validate what fields are required to generate a 940R to a TMO.  Add BRs for fields that are currently not marked as required when a TMO is present to make them required.
3. Increase the number of allowed characters for special instructions, and ensure they print when present (either add to main 1348 to the right of block 27, or always print the continuation page when special instructions are present). DLA desires the capability for 4 lines with each line having 25 characters.
4. Review the inbound DLMS 945A to ensure DPAS is extracting all of the shipping elements and including them in the DLMS 945A to the ICP as well as the 856S.

Mission Critical
Yes. Without this change, DLA will need to delay the implementation of DPAS for managing the Veterans Administration PPE.  Estimated Required Delivery date of this functionality is 12/1/2020.

Benefits
Accurate accounting and reporting for materiel is mandatory.

Users
These changes will improve Warehouse for all users who use this functionality. 

Completed – Release 2021.1 – 5 February 2021