Description
The current DPAS architecture allows for assets to be reflected in the PA and Warehouse modules simultaneously.  This could result in duplicate counting of the asset.  There should be controls in place that prevent the same item (Asset Id, UII, etc.) from being recorded in both modules at the same time unless there is a valid reason (Loan where both the loaner and loanee are DPAS users).

Recommended
There should be controls in place to ensure there is no duplication of the same asset.  Issues from the warehouse module should flow through Pending Transactions.  Any receipt or update of key data (PA or Warehouse) should validate that the asset (Stock Nbr / Serial, UII, Asset Id) does not exist in any other accounts whether that account rests within the PA or Warehouse modules as both modules support Property Accountability in addition to assets that may be in warehouse for storage.

Mission Critical
This is considered a DPAS design flaw.

Benefits
Improves FIAR compliance in that it would ensure an asset is not be recorded in both modules simultaneously.

Users
This will impact every user of DPAS as this is requesting validation that the asset does not exist anywhere else in the system.

Description
The Army and USSOCOM is requesting that DPAS standardize the Army's data using the Army's Enterprise Materiel Master.  The import of the AEMM will provide for a complete list of attributes associated with a Stock Nbr, not just SB700-20 attributes - current Army Catalog import.  The solution must support Mfr Part Nbr Stock Nbrs that are > 15 characters.

Recommended
Create a process that will utilize the Army's AEMM Web Service to retrieve catalog data.  To ensure compliance, there must be methods within the application that prevents the Army user of the AEMM to not be able to create MCNs, Mfr Part Nbr, or be able to catalog an NSN Stock Nbr that does not exist in the AEMM.  For USSOCOM Catalogers, they need to be able to catalogs items that may not be in the AEMM and for USSOCOM, their catalogers must be able to utilize not only the AEMM Agency Catalog, but also their SOF MDR Catalog simultaneously. 

Mission Critical
Yes.  Army desires Total Asset Visibility within AESIP with all items being known by Stock Nbr / Nomenclature from the AEMM.

Benefits
Reduces the effort required to maintain catalog data, ensures common cataloging throughout the Army.

Users
Currently it is believed that the AEMM interface is limited to Army and USSOCOM users.

Completed – Release 7.0.00 – 20 April 2019

Description
The USSOCOM's SOF MDR has Authorization data for the SOCs and TSOCs.  This information is need by DPAS to allow the Units to know what they are authorized / required to what they have on hand, and to be able to validate requisitions.  The goal would be to create an Import and and associate the data with the Unit.

Recommended
Have SOF MDR present the data to DPAS.  DPAS would import the data and make it available to the Property Accountability Module's Authorization process, to the Warehouse's Authorization process and to the Materiel Mgmt's Customer Requisition process to assist in determining the validity of the requisition. 

Mission Critical
Improve / automate authorizations for the SOCs/TSOCs using DPAS.  Provide for validation of the Customer Requisition process.  Without this data being available within DPAS, this process is all manual and is thus subject to the data being inaccurate.

Benefits
Reduces the effort required to maintain authorization data.  Improves the validation of a customer Requisition.

Users
SOCs, TSOCs, and USSOCOM's Program Managers that are validating a customer requisition.

Description
DPAS does not permit the user to enter a UII in Asset Receiving.  The only way for DPAS to capture the UII is via a iRAPT transaction, DPAS HandHeld UII Assoc, or searching the IUID registry and associating it to the asset.

Recommended
Modify Asset Receiving and Asset Update to allow the input of the UII.  Any UII entered should be validated to the registry as a valid UII.

Mission Critical
Currently DoD IUID policy requires all assets that are subject to Property Accountability to have a UII.

Benefits
Reduces the effort required to associate a UII when it is not inserted via an iRAPT or Handheld process. 

Users
All users of the PA module could use this feature.

Completed – Release 6.2 – 31 August 2018

Description
DPAS does not permit the user to import data as part of their converting to DPAS.  Today, the user must complete Excel Spreadsheets and submit them to their DPAS Fielding Support team which reviews them for completeness, then forwards them to a DBA for processing.  The goal would be to provide the user with an Import feature within all processes.  This import feature would work similarly to the existing DPAS Member Profile (Warehouse) and the Fuel / Utilization Import (Maint/Util). 

Recommended
Allow the user to export a template for a specific process, complete it, then import it.  The system would validate the import and add all valid records to the system.  All failed records would be available for export for correction, and / or there would be a "Pending" button that the user could pull up each record that failed validation to be corrected within the Add Screen which would then allow the record to be processed.

Mission Critical
Currently the New User Fielding process is needed to support all new Customers converting to DPAS.  By providing a change is how it is accomplished will reduce the customer wait time and allow them to be in more control of when the data is actually loaded.

Benefits
Reduces the effort required to convert a new customer to DPAS. Provides greater capability to existing customers that may have a large import to perform.  Can be accomplished without Helpdesk and DBA support.

Users
All users of the PA, Warehousing, Materiel Mgmt, and Main/Util modules could use this feature as it becomes available.

Description
As the Android/Apple IOS platforms become more mainstream in the Department of Defense, there is a need for DPAS to upgrade it's handheld processing features to include these platforms.  These platforms may even replace the Windows Handheld platforms that DPAS currently has in use to perform receipt / QC and Physical Inventory functions in the future.

Recommended
Develop the capabilities to export Work Orders for completion on a tablet style device.  Today many service technicians show up at the customer site with the Work Order that is to be completed on an appliance in the home (Washer, Dryer, Refrigerator) and for mechanicals in a home such as (A/C, Heating, Electrical).   Given the state of the WM 6.5 platform, it may be necessary to port the existing DPAS handheld capabilities first.

Mission Critical
The immediate need/requirement is to ensure DPAS does not lose the capability to conduct Physical Inventories in an untethered / non-network mode.  DoD has issued noticed that the WM 6.5 Framework will no longer be able to be connected to the DOD Network as of July 2018.  This is an extension from the July 2017 original deadline. 

Benefits
Provides capabilities for the DPAS user to perform Logistics functions without having to be directly connected to DPAS. A lot of the Logistics functions associated with DPAS are not in the area where the actual work is being performed.  Thus, often times they must write down the data and take it back to the office where it must be typed into a terminal.  The retyping increases cost and increases the risk of error.  The Android/Apple IOS platforms tend to be less expensive that the existing WM 6.5 models, thus delivering DPAS detached capabilities to these style devices will reduce operational costs for the Department.

Users
All User of DPAS perform these functions that are currently available on the handheld.  Organizations that are small, may choose to perform some of the functions manually, and may not adopt the latest technology even though it could improve their business practices / reduce the cost of performing those functions.

Completed – Release 7.0 – 20 April 2019

Description
There is a USMC requirement (Supply Order 4400-201, Chapter 9 and 13) to have a verification step during any quantity adjustments that occur in the DPAS application. Currently the only place that a quantity can be adjusted is in the inventory update manager.

Recommended
Recommend having a pop up that states "Are you sure you want to make this adjustment?" This is a generic enough statement to be used easily across the program, but will also meet the requirements that the Marine Corps requires. This will also reduce the amount of mistakes when adjusting inventory.

Mission Critical
This is mission critical due to the requirements of the Marine Corps to have this verification step.

Benefits
The benefits of implementing this solutions is that it would align all of the USMC Logistics Programs with Marines Corps requirements and the chance of improving inventory accuracy through verification during the quantity adjustment process. 

Users
This will affect all users who use the inventory update manager process to make inventory adjustments.

Removed per Norman Clark email on 5 June 2025

Description
Vehicle Management Material controls require to orders 90 percent of all parts against an asset. Currently, Warehouse does not offer asset id visibility in any of the grids.

Recommended
We would like to request Asset ID information to be added to the Maintenance Issue Grid, Warehouse Replenishment Grid, Warehouse Replenishment Approval screen, Due-In Message of the Day screen, and the Material Mgmt Accept/Receive process.

Mission Critical
Not mandated but critical.  Air Force Material Control sections need a very detailed process to track, account and issue vehicle parts, equipment and tools against specific Assets to track expenditures and control budgets.

Benefits
Adding Asset Id information to the above grids will enable material control sections to improve order and inventory management by enabling warehouse technicians and managers to have direct access to this critical information. Asset Id information allows managers to approve or disapprove requisitions based on priorities assigned to those assets. Asset Id information is also used to track orders/requisitions and it is used to capture and calculate Non Mission Capable Supply (NMCS) as well as Deferred maintenance.

Users
All Material controllers Air Force wide will benefit form the addition of Asset Id information to the grids above. This will enhance parts tracking and management which in turn will improve inventory management and cut costs related to miss-assigned parts and erroneous orders.

Completed – Release 6.0 – 27 April 2018

Description
Background: On October 20, 2017 the DPAS/DAI interface for 12 Capitalization of Purchased Assets (X819) were identified on the DAI Unhandled Report due incomplete information from DPAS.  The reason the 12 transactions were in the DAI unhandled report was due to  blank fields: BUDGET_FISCAL_YEAR, BA_BSA_BLI, DAI_PROJECT_NUMBER, and DAI_TASK_NUMBER.  The root problem was due to blank information in DPAS two fields (1) Task Cd (DAI Project Number) and (2) Job Order Nbr (DAI Task) in Asset Management; therefore,  interfaced to DAI as blank information.

Recommended
Make (1) Task Cd (DAI Project Number) and (2) Job Order Nbr (DAI Task) mandatory fields, this will fix the transactions due to incomplete information. 

Mission Critical
Mission Critical.  Reporting of incomplete financial data to the general ledger can give a false narrative of the data provided and could cause major issue for financial audit of the Agency Capital Assets.

Benefits
By making the two fields REQUIRED in DPAS, (1) Task Cd (DAI Project Number) and (2) Job Order Nbr (DAI Task), it will the eliminate and correct the process in both DPAS and DAI.

Users
This will affect all Property Accountability users of DPAS.

04Dec2017 – removed per Randy Reed
Recreating this SCR as a bug.

Description
There are  an estimated 1,865 legacy assets in DPAS with the default fund code of 'Y1'.  In 2016, new acquired assets were established with fund code procedure that allows DPAS and DAI interface; therefore, the property system of record, DPAS, transfers information to the MDA financial system of record, DAI.   

Recommended
Change all Legacy Capital Assets with Y1 as the default Fund Code to reflect fund codes submitted by CPO.

Mission Critical
Mission Critical.  At this time, with the amount of legacy assets in DPAS not in DAI, this remains a significant audit risk and finding that needs to be corrected.

Benefits
By allowing the CCA to receive a DPAS flat file of the legacy fund codes, CCA can process only one manual JV (versus thousands)  and provide a corrected file to DPAS to update the legacy fund codes.  This will not require CPO to manual update the estimated 1,865 legacy assets in DPAS; therefore, saving an estimated 3,000 man-hours.

Users
This will affect all Property Accountability users of DPAS.

05Dec2017 – removed per Ryan Steele
Recreating this SCR as a bug.