Description
While reviewing the system to assess the fit of the DPAS M&U Module to the DMC Business process, the DMC was unable to tell when transportation completes a move request to deliver the item to its maintenance/repair location within the system. In addition, the location data does not populate in the M&U Module with the location of an asset.

Recommended
Within the M&U Work Order, it is requested that DPAS add the State Cd of “Approved Awaiting Transportation” to the drop down menu. It is also requested that when the status of a WO is “Approved Awaiting Transportation” that the maintenance movement screen automatically open to prompt for the user to input the specific location to move assets to when the WO is updated. Once the item is delivered to the maintenance facility, it is requested that DPAS M&U update the location on the WO, and change the stats of the WO to reflect that the item is ready for maintenance to be started (Change of status and “bucket” within the DPAS Work order screen). This will trigger the M&U Supervisor to continue to the next step in the process.

Mission Critical
Yes. Due to the lack of notification it causes a delay and work to be done sits idle .

Benefits
The benefit is that the tasks or work to be done will be efficiently communicated.

Users
All

Completed - Release 3.0 - 15 May 2015

Description
During the DMC Business Process Fit Assessment, it was discovered that although custom search fields can be selected to create a custom view for the user, the user must select their custom search each time they enter screen. This is a minor annoyance; however, it is a step that will have to be taken each time the user enters the process.

Recommended
The DMC is requesting that when a Custom View is created within the M&U Module, that the M&U Module allows for that custom view to be set as the default view for the user. Each time the user logs the default view should be what is displayed, unless the user deletes their default view or changes it. It is desired that this look and feel similar to what the DPAS Warehouse Module is doing for custom & default views within each process/screen.

Mission Critical

Benefits
This process improvement would reduce time/cost and improve accuracy since the custom view has already been selected at a previous time.

Users
Anyone who uses Custom View will benefit with the ability to save what is first selected.

Completed - Release 3.0 - 15 May 2015

Description
System generated COSIS Quality Control Requests contain assets on multiple locations. They seem to be sorted by stock number only. This means that on a single QC Request, there could be a massive amount of assets of different condition codes and different locations. This will create a lot of lost time for the assigned inspector to find all of the assets on that request on multiple locations and multiple condition codes.

Recommended
System generated COSIS QC Request should be generated separately by like stock number and then by like location. Stock numbers with more than one location should be scheduled as different COSIS request. Mixed condition codes can be requested on the same request as long as the locations and stock numbers are the same.

Mission Critical
This is mission critical, this would prevent unnecessary man hours to be used traveling to multiple locations.

Benefits
The benefit is if these requests were scheduled by lot (location), this would reduce the man hours required to work each request. Therefore reducing costs and increasing productivity.

Users
All

Completed - Release 3.0 - 15 May 2015

11 Mar 2021 – cancelled per Jack Sanders
No Longer Needed.

During the receiving process, one must choose a container to place weapons into. This requirement is for the identification of the proper container and for a pick/materiel movement request to deliver the item to the container selected during the the receiving screen. The condition code and NSN of the items stowed within a container drive weather an item can be stowed with its like counterparts. It is recommended that DPAS display the NSN of items being stowed in a container, and the Condition Code of those items for the purpose of container recommendation/selection.

Within the Warehouse Management, Warehouse Replenishment, approval screen, there is no group update to approve all requisitions for the same project type at the same time. It is recommended that DPAS display a group approval option for all assets. ?This would ?approve all requisitions at the same time

Within Materiel Management Receiving, when processing a receipt, additions to the "Grid" can't be monitored to determine if all receipts have been added. Requesting a grid count is added above the grid to show a total count of items added. Add a grid count above the grid so the count can be monitored

During inventory accountability inspections and audits which NECC forces undergo; inventory counts are validated "by NSN" and "by location". ?Inspection teams request inventory reports by facility (or zone as applicable) with detail (exact locations with quantities and serial numbers as applicable) prior to arrival on the first day of inspection. ?Audit teams have requested full command inventory encompassing all facilities and locations prior to arrival and request specific inventory reports following arrival to validate against the data received earlier. ?The ?By NSN? validation requires reporting of all locations, including kits where a particular NSN exists in quantity or by individual serial numbers; it also includes reporting of issued NSNs/serial numbers and producing custody documentation. DPAS WM does not currently have the capability to produce detailed inventory reports at the facility, ?zone or ?parent? location level. Inventory inquiry by NSN displays numbers overall quantities on hand and issued but requires selecting a particular NSNs hyperlink for further details (serial, location) and does not display the serial number(s) for issued equipment and where it is issued. You must utilize multiple modules and queries within the system to piecemeal separate reports for issued equipment and multiple, lower level locations must be queried for inventory. ?Capability to produce inclusive inventory results exists in current, less sophisticated COTS programs such as ?WASP? using ad-hoc reporting features, therefore it is attainable in DPAS WM and a necessity for data calls and inspections. Ad-hoc reporting or modifications to the inquiry module enabling it to report: ?1. By individual NSN: ?in a single report, the quantities and serial #s for a given NSN, with location (including placement in kits) and if issued, ideally the UIC or individual issued to. ?2. By location: to comprehensively report inventory items (including serial numbers) at higher levels to include all sub locations. If a shelf is chosen for an inventory report then the contents of the containers on that shelf should also report.

Attachments to asset records can not be viewed by the losing activity when the asset is transferred via Asset Management/ Transfer process. ? ?Current logic is that the losing Command does not have access to the gaining Command UIC and therefore loses the capability to view the attachments on the asset record. ? Navy FIAR corrective action plans require document retention for audit purposes. ?Navy Commands are using the DPAS attachment process for receipt and disposition documentation to support FIAR audit requirements. The inability to view receipt and disposition documentation for assets transferred does not support current FIAR efforts. Permit attachments to be viewed and printed by losing command for assets transferred via Asset Management / Transfer process. ?These attachments would be accessed via the DPAS history inquiry module.