(1) DPAS lacks a streamline process to request parts within M&U and transfer part details into warehouse (WH) when parts are not within stock number/stock item catalogs.  The inability of DPAS to provide a standard part-to-warehouse maintenance request prevents current and future vendor-to-maintenance activity efficiencies.  Currently, M&U and Warehouse personnel must physically verify or communicate outside of DPAS to ensure parts are stock number/stock item listed before requisition request
(6) Maintenance Issue receipt DD Form 1150 missing Asset ID (system needs to auto-populate) and form does not capture all parts issued by Asset ID/WO/Sub ID

 

1. Allow M&U part requisition(s) process to send request to Warehouse maintenance issue even if the part number is not present within stock number/stock item catalog
6. Exported Maintenance Issue receipt DD Form 1150 must capture all parts issued by Asset ID/VIN/Serial/Manufacture Model/Work Order/Sub ID and form auto-populates with corresponding DPAS data fields

N/A

 

Seamless communication between DPAS modules and the additional data fields and Inquiries benefit logistics enterprise saving countless hours performing data reconciliation and FIAR processes.

 

Frequency: Hourly

 

Add the ability to verify expiration dates and lot numbers when conducting Physical Inventory and Issued Inventory.

Add a column on the Condensed Physical Inventory and Issued Inventory DW20 Report to display "Expiration Dt" and "Mfr Lot Nbr".  Adding this column will also segregate bulk assets of the same stock number within the same location to each own line item and quantity by the expiration date and manufacturer lot number.

 

 

Audit requirement for verification of expiration dates and lot numbers during inventory. Will aid in inventories that this material is dependant, e.g., hazardous materials, medical material, CBRN.

Frequency: Quarterly

 

When conducting Unit Issues, the user has to initially create a Custodian profile for the member receiving the gear. It is a requirement to assign him to a reportable commodity vice having him be the Responsible Officer (RO) for ALL Reportable or Secure commodities OR the entire platoon/unit/command. NECC requires the RO to sign for a variety of gear, not just one specific Reportable Commodity. If a member wants to view what is issued to them via Member Site, or through Unit Issue Activity they will need numerous Custodian profiles built within DPAS WH to have visibility of the issued gear. In addition, we've come across the issue where members that want to create Unit transfers cannot do so being that the old RO's are only assigned to one Reportable Commodity, it doesn't pull the inventory list for the entire UIC. Proposed improvement would be to still have the capability to assign them to a specific Reportable Commodity as an Optional field when creating a Custodian OR being able to select ALL commodity types, OR adding a field that allows the issuing member to be able to assign that Custodian as the Responsible Officer for the entire UIC's gear. As well as altering the Unit Transfer function to be able to transfer all gear from the UIC without the Reportable Commodity restriction when applicable.

 

Adding the capability to be able to create a Custodian without the Reportable Commodity requirement, and having them be the Custodian for either ALL reportable commodity types OR being able to take custody of all the gear without the need for a Reportable commodity type. Possibly making the Reportable Commodity be an Optional field, allowing the member to be the custodian for all the gear, this would also apply to the Unit Transfer function, not limiting what needs to be transferred because of the reportable commodity if the Custodian has been assigned responsible for the entire UIC.

 

NECCINST 5200.45

 

This will give the issued members additional visibility for the gear issued to them. It also makes the unit issue process smoother by having one Custodian for all commodity types OR the entire UIC, vice having to create 20 different Custodian profiles for the different Reportable Commodities he'll be receiving gear from. Turnover from Custodian to Custodian will also be more efficient, without the limitations the Reportable Commodities have placed on the Unit Transfer functionality.

 

Frequency: Daily

 

Currently our medical supply warehouse uses the DPAS Warehouse unit issue request process to create pick tickets after selecting the details of our stock (expiration and lot numbers are heavily used on all of our items). The asset selection allows for us to monitor and select the next expiring assets (i.e. FIFO); however the picking ticket generated does not list the expiration or lot numbers for warehouse personnel to select the assets that need to be issued. Propose that the pick tickets display both expiration and lot numbers for items that have them.

 

Propose that the pick tickets display both expiration and lot numbers for items that have them. The asset selection process has that level of detail and thus should put a hard allocation against the assets to keep them from moving, so the pick ticket should be detailed to ensure those assets are pulled correctly when using manual processes in DPAS.

 

Local SOPs.

 

Just good business practice to keep inventory straight and practice "First in, first out" FIFO to ensure no stock loss due to expiration.

 

Frequency: Daily

 

When creating a Warehouse Replenishment request the remarks notes that are added to the request can not be seen once the request is moved to a warehouse transfer. The remarks field is there but it is empty. These remarks are needed when suppling equipment to the requester do to the fact it could have details such as serial numbers or specific instruction for the warehouse that is fulfilling the request.

Display the remarks fields of the warehouse replenishment request on the warehouse transfer page of the warehouse fulfilling the request.

 

Support Audit Readiness

 

These remarks are needed when suppling equipment to the requester do to the fact it could have details such as serial numbers or specific instruction for the warehouse that is fulfilling the request. If the users can not see the information it takes more time to contact the request or go back into the requesting warehouse just to find the warehouse replenishment request remarks. This add additional time to the transaction.

Frequency: Daily

When creating a customer profile the DPAS user must input the below data elements - Media & Status code, distribution code, PMR RIC and PMR Required must be checked.  Prepopulating these fields will reduce errors.  Additionally, only allowing the user to use GCSS-A TUC 920 DODAACs from a drop down list will reduce errors also.

 

Provide a drop down of all GCSS-A approved TUC 920 DODAACs and prepopulate mandated data elements that stay the same for all fielding transactions.

 

The SCR is tied to audit improvement and readiness for transparency.

 

Reduce time DPAS users spend on researching and validating DODAAC's and reduce key strokes by having mandated fields prepopulated.

Frequency: Daily

 

On Inquiries-->Asset Activity the Asset Activity Inquiry screen does not display the type of transaction.  The user must click on a selectable item to continue to the Asset Activity History Detail because it does not display the type of transaction.  The user must then select each item in the History Table to figure out what transaction was completed.

 

Update the Asset Activity Inquiry --> Asset Activity History Detail to display the transaction type similar to the Warehouse Module Inventory Activity screen "Source of Change" column.

 

 

This will save time and manpower that is currently required to parse through the asset history of an asset.

 

Frequency: Hourly

 

Users are able to manipulate a Unit Issue in an Issued Status.  This does not return the item to inventory and is still issued status via ICN inventory.  When editing Header it removes it from Unit Issue Activity, Issue Receipt, and Issue Inventory.  When editing Details its removes it from Issue Receipt but does not remove from Issue Activity and Issue Inventory.

 

Disable the Delete button on the Unit Request - Edit Header and Edit Details

 

 

This will prevent users from manipulating Unit Issue in an Issued Status.

 

Frequency: Quarterly

Add the ability to enter a LIN/TAMCN to be able to enter stock numbers (Catalog Mgmt-->Stock Item) to the ICP using the LIN/TAMCN that was created in the Warehouse Module.

 

Add a LIN/TAMCN field to the Add Stock Item popup.  The stock number required field grayed out when a LIN/TAMCN is entered and vice versa.  All stock numbers associated with that LIN/TAMCN will then be loaded to the selected RSA when entering a LIN/TAMCN.

 

 

This will save time and manpower when entering multiple stock numbers to the ICP.

Frequency: Daily

 

DPAS currently receives updates from multiple external cataloging systems to include AESIP(AEMM). When DPAS performs a validation of the data to determine which fields are be updated, there are instances where DPAS does not perform the required update. For example: One of the fields that is sometimes modified is the Management Code (bulk vs. serially managed).  For this to occur within DPAS, e.g. serial to bulk, the user will lose all of the serial nbr / uii data that is present in DPAS.  If it is updated from bulk to serial, then the user must provide serial nbrs (minimum value of data) for the entire asset qty on hand prior to DPAS being able to process the request.  This poses issues when the cataloging system made a mistake with that update.  If it was going from serial to bulk, then when the cataloging system changes it back, the DPAS user would need to provide all of the Srial Nbrs / UIIs.  DPAS doesn't know which assets were issued during the interim. This is no small feat given there could be thousands of assets involved.  BLUF: DPAS needs to maintain synchronization with an external feeder system in a prudent manner.  

To enable the user to validate changes in master catalog data prior to implementing the change that could result in a catastrophic mistake caused by the external cataloging system, DPAS should incorporate a process to display the pending update to their catalog and the reasons why DPAS did not systematically process the update upon receipt.  This will enable the DPAS user to see the impact and if they non-concur to consult with their external catalog team to confirm the change is correct.  If there is concurrence, then enable the user to apply the update to all asset records that the catalog is associated to.  If the catalog team was incorrect with change when they processed the update, DPAS user can deny the update.  If correct, then allow for the user to accept the update with DPAS providing the necessary screens to enable the update to occur.  In the end, every update received from an external cataloging system must be able to be processed by DPAS.

 

DPAS must be in sync with the authoritative source. In this instance AEMM.

 

Implementing this solution will provide users greater visibility to the updates coming in from the external catalogs and ensure they have a way to correctly align their catalogs to what is defined by the Source of Truth. Ensuring this alignment will increase data integrity when interfacing with other external sources whom also pull data from FEDLOG

 

Frequency: Daily