Problem: The current state of WPMAR10R-Equipment Utilization doesn't auto populate from the data input from previous screens.  

 

Solution is to auto populate the data from the previous screens. The TO and FROM dates and previous mileage should auto populate on the Equipment Utilization form.

 

The auto population of the form will prevent the dispatcher and operator from inputting the data. This will also keep the form and data clean.

 

The implementation of this process would benefit agencies that have vehicles and people dispersed in various locations and would also speed up the process.

 

Frequency: Daily

 

Problem: The current state of WPMAR10R-Equipment Utilization Checklist doesn't allow agency to modify checklist to meet the agency needs.  

 

Solution is to allow for the modification of the checklist.

 

This would benefit the agencies because the checklist has some checks that are irrevelant and some that's not listed depending on type equipment being checked.

 

The implementation of this process would benefit agencies that have a variety of vehicles in various locations and would also speed up the process.

 

Frequency: Daily

 

Problem: The current state of DPAS M&U lacks the ability to effectively allow the dispatch process to be automated. The agents in the field have to download a scanned dispatch and email to the dispatcher and that takes time that can be better utilized, such as dispatch/vehicle logs, receipts, and maintenance records for vehicles.

 

Solution is to implement an automated dispatch process that will upload dispatch form/vehicle logs to DPAS, with the option to export. This would be called a Driver mobile application which will streamline and simplify the dispatch process. The dispatch will be provided to the recipient via phone/computer. This process would upload all pertinent data such as date, beginning mileage, end mileage and locations. The solution should also allow drivers to scan fuel receipts and maintenance records via the app and attach to dispatch form/vehicle logs.

 

The automation of this process would eliminate time and effort of driver's no matter the location. Drivers can see a list of their current trips and record trip start times and odometer readings on the app which will integrate with the Fleet Management Information System (FMIS). Drivers can close dispatches after completion allowing the integrated information to be available in the FMIS. Dispatchers can assign vehicle to an employee as needed and dispatch the vehicles.LMP

 

The implementation of this process would benefit agencies that have vehicles and people dispersed in various locations and would also speed up the process. Drivers can view and complete trips on the go using the app. The app data will automatically integrate with the Fleet Management Information System (FMIS) and eliminate the need for paper dispatch forms and manual data entry.

Frequency: Daily

 

 

Users are not able generate inventory report that does not have a Inv Process Cd = "OIN" or "ODL" and generate reconciled report that does not have a Inv Process Cd = "OUA"

 

Enable a end user to generate inventory report and reconciled report of closed inventories.

 

 

This will allow users to print previously completed inventory for audit purpose IAW COMNAVPSECWARCOMINST 4460.1F without requiring to submit a help ticket to Leidos.

Frequency: Quarterly

 

Users are not able view currently inventory Type Asset Cd

 

Add Grid Option->Columns for Type Asset Cd on Inquiries->ICN Inventory and Materiel Mgmt->Inventory Update Manager.

 

 

This will allow users to view their current inventory type asset code without the need of exporting the inventory and WH catalog then executing a script to compare the two files.

Frequency: Daily

 

The current DPAS ICP roles do not fulfill the roles or structure for the Department of the Air Force(DAF) for Item Managers (IM) or centralized stock control functions.  

 

Create new roles that will provide the appropriate profiles for DAF IM and stock control managers that will provide them with the required system capabilities that allow them to accomplished their assigned tasks.

AFMCMAN23-501V1_AFMCGM2023-011 June 2023 Air Force Materiel Management para 5.8.5.2.

By creating a new roles for item manager (IM) and stock control functions this will align with the duty positions of personnel as outlined in DAF policy

Frequency: Daily

 

Currently reccuring tasks will only be scheduled and assigned a workorder number to equipment that has an asset id number; ie a work location with a mixture of accountable/non accountable equipment.

Allow for scheduling of equipment without an asset ID number to enure conitinutiy of mx scheduling through all equipment tracked in DPAS not just accountable equipment tracked in the PA module.

 

 

By allowing for mx schedules to be auto generated without asset ID's it will allow the user a better mx snapshot for upcoming mx requirements.

Frequency: Monthly

The DPAS Property Accountability (PA) and Maintenance and Utilization (M&U) modules have a database table (DPAS.appsec.user_tracking) and associated stored procedures and application code logic that is used to track user system navigation activity.  However, the table and associated objects have been superseded by other existing features that are implemented system-wide.  The contents of the appsec.user_tracking table are not currently monitored or used in any meaningful way.  Also, this table generates a lot of DML activity in the production environment and appears to be involved in some periods of reduced application performance.  At a minimum, the unnecessary DML activity against this table will generate excessively large transaction log backup files.

 

Drop the DPAS.appsec.user_tracking table and any associated database objects.  Remove the application code logic that called these database objects.

 

 

 

This change will provide better system performance and availability.

 

Frequency: Daily

 

The MRO Process in the WM is not very user friendly. The functionality of the process has not been improved since the original design of this functionality. There are many mandatory steps to get through the process that are not a requirement for the business, to include the Material Movement Plan and Pick Process. There is also no means to allow entire containers to be shipped.
This process is very antiquated and is very rarely used when another process will suffice in getting the gear issued (i.e. Warehouse Transfer or Warehouse Issue)

 

The MRO Process in the WM is not very user friendly. The functionality of the process has not been improved since the original design of this functionality. There are many mandatory steps to get through the process that are not a requirement for the business, to include the Material Movement Plan and Pick Process. There is also no means to allow entire containers to be shipped.
This process is very antiquated and is very rarely used when another process will suffice in getting the gear issued (i.e. Warehouse Transfer or Warehouse Issue)

 

 

Would improve the entire process of issuing gear to include reducing time required to issue gear, improved accuracy by using the process vice alternate processes.

 

Frequency: Daily

 

Currently there is no "one" way to pull up a complete ICN Inventory or Inventory Activity  with all required data.    Currently have to use multiple reports and inquiries to obtain all contract required data and then blend it into one report.  Items not easily found are MFR Part # (ICN and Activity), Issue DODDAC (Activity).  Inquiries also allows to research multiple days of activity  were the Pre-canned reports only allows for a single day which require multiple reports and then have to compile the reports together.  Additionally, all MFR Part # and Model # is created for each Stock Number.  However there is NO inquiry or report that provides this data in relation to the warehouses activities.  Part # or Model # has to be hand typed into every report to show all data related to the activity. IF DPAS Stores this data, and WebFLIS, can provide this data or it is typed in by the user, why can't we use it for reports and inquiries?  Same applies to the Issuing DODAC.  Its part of the "activity" it should be selectable, not just the Owning DODDAC, which is already known as it is the warehouse creating the report

 

At a minimum the following data should be made available (selectable, not default) to the ICN Inventory or Inventory Activity inquiries:
DODDAC Address 1 (Activity)

 

NAVSEA Contract N00024-22-C-5231
SECNAVINST 5200.44

 

Elimination of excess labor costs.
reduction of possible errors in reporting due to merging of data

 

Frequency: Daily

Est user: Unk (DPAS Wide).  within our DODDAC(s) - 12