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.

Description:

Currently DPAS-WM does not generate a Due and Status File. So we are unable to see the Supply Status history and Estimated Shipping Dates for Requisitions. Currently we are having to use multiple websites to get this information.

 

Recommended:

Recommend that a Due and Status file report be created so we are able to all requisitioned document related transactions to include supply status, estimated shipping dates and supply status history. (Please see attached example of what the Due and Status file should look like). This should be a report that has parameters where it can be pulled at any tier with time dates that filter on requisition date. Report should be available to pull in CSV or Excel formats. This report should also be available in the Inventory Control Point module.

 

Mission Critical:

Yes, having this report will reduce time from having to search multiple websites for supply statuses and history. This would also increase audit readiness. Currently we have no way to see in DPAS the Unit price charges for each transaction, which is a USMC audit requirement.

 

Benefits:

This will help reduce time and improves the accuracy, audibility, and reporting of the requisition supply statuses.

 

Users:

All IIF & UIF

 

Description:

Currently the USMC is using a non-accredited software to do Optical Character Recognition (OCR). OCR uses a high resolution picture of of a numeric characters to 'recognize' the intended numbers without having to manually key them in. This is primarily being used to read serial numbers of weapons as part of the receiving process. The current process tries to match serial numbers through recognition against a known set of serial numbers. The software allows the user to set confidence thresholds and when an item does not meet that threshold, it asks the uses to confirm the suggested match. We believe that DPAS can provide a better product that seamlessly provides a better service and is fully accredited for the USMC environment. Recommend DPAS provide an OCR-like capability in certain warehouse/AIT processes to improve inventory accuracy, audit capability, and process time consumption.

 

Recommended:

Recommend adding OCR functionality during the receipt and picking processes. 1. Adding OCR capability during the receipt process will increase inventory accuracy during "birthing" process of the inventory into DPAS. Recommend adding an OCR capability during the verify portion during the receipt process. Should have the ability to add ICN to the verified grid or verify serial numbers that are already in the grid if the due in came with expected serial number. 2. Once receipt is completed, the OCR verified picture should be attached to the asset that is viewable. This way users can verify system serial number matches the OCR picture that was taken at the time. 3. The pick processes should allow you to add inventory to picks with an OCR capability. Once a pick plan is created, the use should be able to conduct picking actions with OCR capability and add the serial numbers to the pick. This will allow receipt stows and MRO pick to be conducted more accurately and efficiently. 4. There needs to be functionality to change the OCR picture that is attached to an asset. This is required in case the data plate or NSN is changed.

 

Mission Critical:

Yes, in order to do a weapons warehouse Proof of Principle (PoP) this functionality will be required in order to not lose current functionality. This functionality would benefit ALL DPAS customers.

 

Benefits:

Implementing an OCR capability will improve inventory accuracy, accountability, audibility, and increase warehouse efficiency.

 

Users:

This will affect all users of WM who are interested in using OCR capability with AIT devices

 

 

 

Removed per Norman Clark email on 5 June 2025

Description:

DD Form 1149 does not complete(populate) with all required data. Some data is in the wrong location. Recode locations for data fields on the DD Form 1149 to print correctly and accurately IAW with DOD instructions

 

Recommended:

See attachement (PPT) and DOD DD Form 1149 Instructions

 

Mission Critical:

Critical - in order to reduce man-hours to correct DD form 1149 prior to shipments/accuracy of Data. DD Form 1149's are the Document of Record for shipping and transferring Engineering Change kits to the Fleet. The 1149 must be correct and is verified by the Fleet (Regional Maintenance & Modernization Coordination Office (RMMCO)) to ensure all required material to complete the Engineering Change is provided and in acc

 

Benefits:

Reduced/time and cost. Accuracy of historical paperwork. Easier record keeping (10 year requirement)

 

Users:

Yes

Description:

Currently the DPAS-WM does not have an Issue and return capability that could be used from an individuals own phone vice having to go to issue counter to create a pick list and begin individual issue process.

 

Recommended:

commend that an issue and return capability be developed with the following requirements: 1. DPAS customer phone issue capability should be developed by using a QR code. 2. QR code should be developed to allow customer to select the correct master issue list. 3. Master Issue list should populate on customer's phone with the quantities and locations highlighted in red. 4. When an individual selects an item the red highlight will turn to green letting the individual know they have selected that item. 5. Individual should not be able to select more than the Master Issue list Quantity. 6. Once an issue is complete a barcode or QR should appear so it can be easily scanned into DPAS-WM issue screen so the items can be signed for by customer. 7. Customer phone return capability will need to use the same QR code created during the issue process. 8. Ability to mark and highlight items the individual is returning. 9. Once the return is complete a barcode or QR should appear so it can be easily scanned into DPAS-WM return screen all items that the individual chose to return should be checked so the items could be easily returned and turn in receipt generated for customer.

 

Mission Critical:

Yes, This will help alleviate individuals from having to wait in long lines to start the issue and return process and also help with service times.

 

Benefits:

Having this functionality will be extremely helpful in reducing wait and service times to the individuals.

 

Users:

All IIF

 

 

 

Description:

Currently there is no Stock Item Type Cd = 'L - Local' in the DPAS Catalog. Local Stock Numbers are currently cataloged as Type 'J - MCN', and for a Local Stock Number, the Type J business rules are ignored, allowing users to enter a stock number with a more flexible format. But they are still categorized as a Type J – MCN stock item type. DPAS users have expressed a desire for a true 'Local' Stock Item Type Code that can be used to format stock numbers to meet their individual agency business needs. Adding Type ‘L – Local’ stock

 

Recommended:

Add a Type ‘L – Local’ stock item type code that will appear as an option during stock number add process and stock number searches where applicable in DPAS (including browse modals and search criteria); Convert existing non-conforming Type J stock numbers to Type L stock numbers in DPAS catalog Stock Nbr table. Establish a single Regx value in all catalogs for the L type Stock Nbr at time of startup allowing agencies to request a change in the Regx value when they are ready.

 

Mission Critical:

 

 

 

Benefits:

The change enables the processing Stock Nbr data using defined DoD methodologies for defining the the different types of Stock Nbrs. As a result of this change it should improve user accuracy in categorization and formatting of the different DoD stock number types.

 

Users:

This change will primarily impact users who are involved with cataloging.

Description:

M&U presently sets a 30-day utilization reporting requirement for assets subject to utilization reporting. However, utilization reporting for most AF support equipment is only accomplished when the asset is brought in for maintenance, and this is often greater than every 30 days. Additionally, equipment in storage or WRM status may only be inspected annually. With ~100K AF SE assets in M&U, this drives an enormous manpower effort to simply reflect that there was no utilization during the 30 day period.

 

Recommended:

Add ability on MAM Update screen to designate assets as not requiring a specified utilization reporting period (no 30-day requirement). This would allow users to exempt applicable equipment from recurring utilization reporting requirement (30-days) presently required by M&U.

 

Mission Critical:

Not mission critical, but it is a significant, unnecessary manpower reqt. 100K assets x 2 minutes per asset to reflect no utilization = 3,300 manhours expended per month across the AF. Reporting utilization for SE is NOT mandated by any AF or DoD policy. Our interim solution is to ignore the Meter Util Not Rptd link, but that's not an acceptable long term solution.

 

Benefits:

Reduces time, manpower cost, and improves accuracy by allowing users to focus on documenting maintenance properly.

 

Users:

All AF SE M&U users.

Description:

User must select each location individually when performing an inventory by location. This could potentially require users to input hundreds of individual locations when inventorying multiple bin rows or cabinets.

 

Recommended:

Allow range of locations. For example, Starting Loc: 01A009A001, Ending Loc:01A011C003 Our warehouses are segregated into bin rows. Each bin row may have dozens of individual locations. Most of our warehouses schedule our inventories utilizing a range of locations.

 

Mission Critical:

 

 

Benefits:

Reduces time and mitigates manual errors of potentially having to select hundreds of individual locations.

 

Users:

All users

 

Description:

1) Lack of a location field in the Unit and Individual Returns sections on the LPWHR78 Warehouse Activity report.

 

Recommended:

Add a location field in the Unit and Individual Returns sections on the LPWHR78 Warehouse Activity report.

 

Mission Critical:

Mandated. This data greatly assists audit-ability of armory assets during combat systems inspections as well as providing the complete transactional details to be shown within this report.

 

Benefits:

Improves Accountability

 

Users:

This problem affects all current NSW users.