Description:

When completing a maintenance issue within DPAS Warehouse, the DD Form 1150 does not show asset ID or reflect correct unit price. Unit price corrections are made within maintenance issue pick process if necessary and remarks added. Asset ID display within asset ID block and correct unit price on form ensures proper documentation. Additionally, the DD1150 block 5 Request Number reflects the M&U Work Order Id and block 7 Document Number reflects the Parts Request number. These fields do not directly translate to data fields within the M&U and Warehouse module.

 

Recommended:

Update the DD1150 process to reflect the following: Block 9 (2) Asset Id – populate with the Asset Id from the M&U work order Block 9 (8) Unit Price – populate with the Unit Price adjustment during the pick process Block 5 Request Number – populate with the Part Request or Document Number from the Warehouse Maint Issue Block 7 Document Number – populate with the Work Order Id number from M&U requisition

 

Mission Critical:

It is critical to capture accurate data when documenting expenditures against assets within the M&U and Warehouse module. Agency sustainment budgets based on data within DPAS.

 

Benefits:

 

 Having the DD1150 capture accurate data improves budget auditing expenditures and asset life cycle sustainment cost documentation. Auditing ensures financial reporting accuracy and creditability for Department of the Air Force (DAF) budget requirements.

 

Users:

This affects all Agency's and we believe this function will benefit all.

Description:

DPAS Warehouse limits Location Condition Code for a stock number to one Location Id. When receiving multiple quantities of a stock number under a single document, all will default to the single location and then need dispersal to various locations. Each warehouse will have multiple locations that require the same stock number and have a single Due-in, Backorder, or Return created to replenish or restock the items.

 

Recommended:

Allow multiply Location Condition Codes for same stock number. Enables user to chose several locations by quantity they would like to receive/return stock numbers streamlining process.

 

Mission Critical:

This is not critical or mandated, however improving system efficiencies decreases time warfighter spends performing non-wartime tasks

 

Benefits:

Automation provides a time reduction searching commonly received stock numbers for warehouse location replenishments (e.g.,individual issues). Additionally, potential to eliminate or reduce misplaced items within warehouse. Allows warfighter to focus on critical mission tasks vs. assigning warehouse replenishment locations.

 

Users:

Yes

Description:

Asset custodians are required to be designated in writing and supporting documentation is also required to be uploaded to the APSR. Currently, DPAS does not allow attachments when adding or updating a Custodian. Having the ability to attach Custodian designation letters and Custodian turnover forms to a Custodian in DPAS would solve this issue.

 

Recommended:

Add the option to include an attachment when adding or updating a Custodian.

 

Mission Critical:

Yes, Custodians are required to be designated in writing and supporting documentation is required to be uploaded to the APSR.

 

Benefits:

existing policy. This will also improve auditability by making it easier to access the documentation remotely which will also reduce the time/effort required when this documentation is requested.

 

Users:

This affects all NAVY and DODEA users and likely other services that use the Property Accountability Module in DPAS.

Description:

For accounts that are suspended due to non-compliance of the Annual User Audit, we do not have a way to lock these accounts from being reset until is appropriate. When user accounts are suspended (active box unchecked) because the IO group has not provided a response for the Annual User Audit, there is nothing preventing Help Desk support from being able to reset the account unknowingly. I am proposing a lock feature or new status ability be given to assist Security Officers with audit compliance. The Help Desk should retain their currently ability to reset accounts; however, we also need a method that allows for Sec Officers to lock particular accounts that can only be unlocked by a Sec Officer.

 

Recommended:

Provide ability to lock certain user accts from being reset until IO completes Annual User Audit. Potentially a new status or lock feature that only Security officers could update those particular accounts back to active status when appropriate.

 

Mission Critical:

This functionality supports audit readiness.

 

Benefits:

The solution supports audit readiness and user review compliance so that users do not get access to their account before they should.

 

Users:

This change would impact internal support staff.

Description:

Current PA Module design does not allow for users to delete UIC's that were entered incorrectly, or to migrate/mass move UIC's from one Parent Structure and Accountable UIC to another.

 

Recommended:

Add capability in Property Management to perform UIC movement/migration, similar in concept to a Task Force Update process. This process will allow users with the proper roles to update/edit/delete/re-align UIC's. This will allow for organizations to transfer UIC's to a gaining organization without the need to laterally transfer items one at a time to the same unit that now falls under a different organization structure. Develop ability to delete UIC's entered incorrectly that have no assets assigned to them. Add capability to Update UIC assignment Major Command Codes

 

Mission Critical:

This is critical to using organizations such as the AFSOC community which has been re-organizing it's unit assignments.

 

Benefits:

The benefit is a reduction of bad data (UIC data tables) in the PA structure and the ability to rapidly re-assign UIC's and migrate the equipment and custodial data over to a new APO with no data loss. This will enable units deploying on short notice to re-align rapidly as needed.

 

Users:

This will apply to all users in the DPAS community that use the existing PA Module to account for their unit assigned equipment. This SCR request is related to the existing USAF SCR 01627. SOCOM is requesting additional UIC update capabilities than the originally requested. This change will also benefit the USAF and any other users of the PA Module

Description:

The current dataset name requires our folks to do a lot more coding to place the correct date with each record as its ingested. Because of this when there are issues on our side and ingestion is delayed, then we have to have very specific code to put in the appropriate date, meaning it’s no longer automated.

 

Recommended:

Looking to add a File_date_timestamp to each record when DPAS produces the dataset, per line item within the dataset as the last column.

 

Mission Critical:

Critical. This would benefit various users across spectrum

 

Benefits:

The current dataset name requires our folks to do a lot more coding to place the correct date with each record as its ingested. Because of this when there are issues on our side and ingestion is delayed, then we have to have very specific code to put in the appropriate date, meaning it’s no longer automated. Additionally, this will provide a higher level of confidence in knowing what date the dataset was truly produced.

 

Users:

This affects all users

 

 

 

Removed per Norman Clark email on 5 June 2025

Description:

DPAS (Warehouse Module) currently does not allow for any type of Inventory Inquiry by part # when it is associated with an NSN. Only the inventory of the NSN is searchable. Request the ability to search and view inventory via the Part #. Part # is manually added against an NSN ( though it should be imported via WebFLIS) but then the user has no means to use this data for Inventory control or Metric collection.

 

Recommended:

Add Part # fields to the Inquiry menu (Stock # or ICN) or show inventory via the Manufacturer Part Number Screen in the Warehouse Module

 

Mission Critical:

The issue we are coming across is the ability of DPAS to recognize or function via an assets Part Number and not the NSN. Facilities working with DOD for repair parts typically catalog assets by their NSN and FPN (Functional Part #/ Manufactures Part #). This is due to DOD technicians (Sailors and Soldiers) using Part Numbers that are associated with their Technical Manuals which lists assets by their Part #. WEBFLIS lists both the NSN and the PN# for this very reason, but DPAS does not have a part # functionality (From WEBLIS) unless manually entered or a search functionality unless the Stock Number(NSN) is known 1. Speaking just on the Navy side, Almost all technicians in the fleet maintain equipment via training and their technical manual. This training and their manuals operate solely on a Part Number system. Then then use this part number to cross reference it to a NSN when they pass the request onto their Supply Department to order or ask for assistance from their supply department to cross reference it. They may also reach out top a local Maintenance center or NAVY311 for technical assistance. When working the technical assistance side they will speak almost exclusively by Part # when referencing the failure as this is all the technicians know how to reference the part. If NAVSUP does not have the parts in stock and they have to reach out to other entities to see if the material may be available via another means, again they would ask for the material via Part #. To put it plainly only the Supply Corp uses NSN’s for part movement and ordering, the actual users and repair technicians and their documentation is based solely on Part # 2. DPAS has interaction with WEBFLIS via interface. WEBFLIS contains all data as it relates to a part including NSN and Part #. However, when adding assets to the DPAS database Parts Catalog , the Part # information from WEBFLIS is not migrated into the DPAS Parts catalog, only the NSN data. Any Part# Data has to be entered manually after the NSN is created in the Parts Catalog and then “tied” to the NSN. this also creates another issue for NSNs that have Multiple possible Part #s (due to Form Fit Function) as DPAS only allows one Part# top be created against and NSN, even though WEBFLIS may show as many as 10-20 in some cases. 3. Another issue/concern with DPAS and Part #’s is usability after the data is entered. Currently, at least none that I or our instructor can find, is an ability within the DPAS Warehouse Management Module to “search” for an asset via the Part #. All the data has been manually entered and crossed to the NSN in the Parts Catalog, but there is no functionality to do an inventory search (inquiry) via the Part #. We can do location, warehouse, NSN, etc. but not by Part #. So trying to help Navy fleet technicians with parts support is compounded by the fact we have to go to the actual WEBFLIS site, call up the part number information, copy the NSN from WEBFLIS and then copy that to DPAS to check our stock even though DPAS has all the information in the parts catalog already via manual entries.

 

Benefits:

Reduces Time/Cost (common inquires for material are via a Part# not an NSN), Improves/Accuracy/ Accountability (allows correct verification of inventory via 2 methods , NSN and Navy Part #), Financial Reporting (Contract Material BOMs and RFPs are by DOD and/or System Part # and not NSN since most material is purchased commercially before being accepted into inventory)

 

Users:

I do believe this will benefit all Non-DOD supply facilities and Repair facilities of DOD material.