DPAS M&U lacks the ability to identify items as Critical Assets.  Some assets are of such high importance to the warfighting mission that they need to be labeled as Critical Assets. These items are vital to meeting DODD 4151.18 mandates that maintenance programs are structured to "meeting readiness and sustainability objectives (including mobilization and surge capabilities) of national defense strategic and contingency requirements. It is of significant importance for senior leaders to monitor availability of these assets on a real-time basis to detect and resolve shortages that impact readiness. Per DAFI 21-101 it is the Maintenance Group Commander's responsibility to "Establish Minimum Equipment Levels (MELs) for essential maintenance assets to include support equipment and vehicles.This capability was present in legacy systems prior to our transition to DPAS M&U and is now being accomplished manually via spreadsheet (daily updates required).

 

Add a new checkable attribute in the Maintenance Asset Master labeled Critical Asset. This attribute needs to be added as a field in the Maint Asset Inquiry; needs to be a search option in MAM; and needs to be added to the "additional attributes" section of the Work Order.

 

DODI 4151.18, AFI 10-2402; DAFI 21-101

 

This change will ensure senior leaders are able to assess and monitor the health of critical assets,  maintaining the ability to execute War Orders effectively IAW DoD and AF policy.

 

Frequency: Daily

 

Description:

Some DPAS Modernized Applications need updated to meet current development standards and incorporate new features.  These changes have already been designed and implemented for new services going forward, but existing services need to receive these updates.

 

Recommended:

Implement the list of architectural changes into existing services that do not yet have these changes.  This includes the following changes: DPAS Health Checks, Update NServiceBus, Remove LangVersion from Project Files, Set the Environment Exit Code to non-zero, Remove CreateErrorHostBuilder and related logic, Disable Swagger Endpoints in Production, Add generateAppSettings, Update Dpas.API & Versioning Configuration, Remove Metric Service and related code, Add Eastern DateTime Converter, Implement Dpas.SessionManagement package.

 

 

 

This will make all service implementations more consistent, reliable, reduce code, and incorporate new features that have been developed in other parts of the system.

 

Frequency: Daily

 

When the interface was established with DAI, it was determined that DAI was unable to receive x806, x813, and x814 transactions, so DPAS sends x805 transactions instead. This deviation of the crosswalk is causing DFAS to record any and all dispositions with a JV because the transaction code DPAS is sending to DAI is different from the transaction code being recorded within DPAS.

 

DPAS needs to revise their crosswalk for the DAI interface, so x806, x813, and x814 transactions are sent to DAI so we are in conformance with U.S. Treasury’s guidance for the disposition of an asset with a loss.

 

This is a mission critical function as it is causing journal vouchers to correct.

 

The benefits of this change will bring the interface into conformance with U.S. Treasury’s guidance for accounting for property losses. It will also eliminate the need for journal vouchers to be processed in DAI for the improper transaction code being sent today.

 

Currently there are no roles that limit a Warehouse User to downloading released physical inventories, conducting the physical inventory, then uploading completed physical inventories using the automated capabilities of DPAS

Create a new Warehouse role that is limited to downloading, conducting and uploading completed inventories along with any system changes that are needed to limit the user to conducting physical inventories only

 

There are users whose sole DPAS responsibility is to conduct and report the results of a physical inventory.

 

Ensure Separation of Duties are enforced.

 

Frequency: Weekly

CURRENT deferred workload is incorrect.  DPAS drops the connection between the Warehouse Parts order data and the M&U Work Order data once the part is received in

 

AF require DPAS to provide BLADE with ILS-S requisitions, DPAS Warehouse Maintenance Issue orders, and the parts that have been associated to a Work Order, and ensure the capability to defer a part does not cancel the part (It removes the WO Number from the order if there is one assigned, but keeps the part associated with the Task and Asset.).  Also insure that when a deferred task is added to a new WO, that the deferred task is closed.

 

The 441st VSCOS in the AF deem it as mission critical, as they need this data to sufficiently manage the vehicle maintenance workload.

 

Improves accountability.

 

Frequency: Daily

 

All users

When a requisition for a quantity greater than 1EA in ICP the system then sends multiple'local Due-in' to PA for receipt processing using the same document number that was initiated. Foe example processing a requisition for 10 EA, 9mm weapons, in PA 10 individual local Due-in are established. Additionally the system will not allow for the quantity to be updated when processing the receipt, requiring each due-in to be processed individually.

 

Establish the local Due-in in PA for the same quantity that was initiated in ICP. Allow for multiple serialized assets to be received under the same document number.

 

 

 

Reduces processing time by eliminating multiple individual transactions.

 

Frequency: Daily 

 

The modernization of the Maintenance and Utilization (M&U) module requires the 2-way communication between the Warehouse Mgmt. Quality Control processes and M&U work order processes to be reworked.

 

Update Warehouse Mgmt. to utilize the Maintenance and Utilization mico services that have been fielded for M&U.
6 Process continues to recycle until WM QC signs off that the work requested has been completed.

 

This is the technical solution only, to modernize the technical communication between the modules.  Any functional redesign of the user process will be handled through the modernization of WM as priority dictates.

 

Provides users of the Warehouse Mgmt. module to request services of the M&U module user in support of: prep for ship, prep for stow, and COSIS.

Frequency: Daily

 

There is currently no tie to the DLA medical logistics systems as there is with WEBFLIS/FEDLOG. Propose that there be an option to feed the DPAS catalog with data from the below sites to ensure current NSN data is populated in the catalog:  
https://www.medical.dla.mil/SSO/consent

 

Create a linkage between the medical supply information systems to the DPAS catalog.  

 

Prevents users from looking in multiple DLA systems for information to manually update the catalog.

 

Time savings with automated updates to the catalog. Centralizing would benefit all 4 branches of the DoD.

 

Frequency: Daily

 

Currently when loading a new UIC in PA, the user is also required to ensure the client RSA is established in ICP in order to requisition property. Additionally, the current process to manually load a new Client RSA is to submit a trouble ticket to the Help Desk which has taken several week to accomplish

 

Establish an automated process where the Client RSA is also established when a UIC is loaded into the Master Data file in PA.

 

By design DPAS requires an ICP Client RSA to be established in order to requisition property.

 

This eliminates the requirement to submit a trouble ticket every time a new client RSA needs to manually loaded in ICP when a new UIC is established.  

 

Frequency: Monthly

 

Request for DPAS-WM to provide the ability to search items have been gained and lost from the warehouse, for a specified date range and enterprise level, and be used to generate a Money Value Gain Loss Notice (MVGL/N). The date range capability is to permit the user to able to create an inventory adjustment report that spans multiple business days.  Having the capability to include multiple days of activity in a single report will streamline the review and certification requirement.

 

Create or modify an existing inquiry to allow the ability to select the date range, required adjustment codes and columns necessary for the notice.  The inquiry allows an enterprise view, based on user security access.  The inquiry will provide the ability to export the results to an MVGL/notice which is required to include the following statement: "I have reviewed the documents on this notice and verify that required documents have been properly certified." - to be certified by  the CO/Accountable Officer or acting CO/Accountable Officer.  The notice will be emailed out for digital signature and a repository, within DPAS, will be provided for upload and archive for up to 2 years.  The notice must contain at minimum, the following fields:  DODAAC, DIC or DLMS Identifier, NSN, UI, Document Number, and Condition Code.  The data needs to be able to be exported with a signature block for command signature.

 

This change is requested to facilitate USMC in adhering to MCO 4400.150 in regards to MVGLs. All appropriate inventory gains and losses must be signed by an accountable officer before they are processed. The current DPAS MVGL process does not provide the functionality requested by USMC.  

 

This change will provide a simpler way of accounting for loss and gain transactions. As it stands now this process is accomplished by means outside of the system. Incorporating this within the warehouse module will save time and help eliminate human error.

 

Frequency: Daily