Current format of Authorizations Paragraph Nbr is not large enough to meet USAF requirement to identify a specific organization within a specific Unit Identification Code (UIC). Recommended solution: Request Paragraph Nbr be extended to 8 alpha/numeric characters. Customer priority: 3

(SCR created on 3/3/2014) Ability to differentiate between high cost and low cost bench stock. Allow system to categorize bench stock based off price. 1) High cost ($60 and up) and low cost ($59.99 and below) parts are charged to two different Work Order number types in current legacy system. High cost bench-stock is charged? to H8888 and Low cost bench stock is charged to L9999.????????????????????????????????????????????????????????? **high cost bench items are required to be managed differently than "lower" cost item.

Vehicle utilization by other means recording not currently available. Need to add fields to capture number of passengers, number of pounds and idle time per Dispatch and cumulative. ?Fields should be available at Dispatch return and Maintenance Asset Utilization. Have utilization by other means factors available during profiling for selection. ?Could use check boxes or flags to identify factors required for an asset, so this data can be collected. Recommended solution:?When a vehicle is profiled in M&U for utilization or M&U, along with mileage and fuel, passengers, pounds and idle time fields should be available to capture data.

Further Request from Deric Sims, 8/3/2016: As we work SCR 644/859 to capture Other Utilization, we need to ensure the Equipt Utilization form printed out at Dispatch is updated too. When discussing with USA last week, the form needs to add a column for number of people so buses can capture per stoploading/unloading and instead of Nbr of bag, use tonnage or weight.

(SCR created on 4/29/2014) Army maintains a Comment section on each Work Order to capture notes generated for maintenance.? Note section is date/time stamped, lists the user and the comment, with? newest comment on top.? Comments remains with the Work Order. Maintain comments from Remarks section in DPAS on Work Order.

Description
When printing a work order, five extra lines under each tab (Task/Parts/Tools/Labor) are printing making the printed package large. Currently prints three pages with no information.
Only works per work order and slows down printing process.

Recommended
Only print information available in each tab. If no information is input, then do not print the tab. Also, allow user to choose what information they want printed vice printing entire W/O.

Mission Critical
Mission critical because it uses an unnecessarily amount of paper and takes too long to print.

Benefits
Reduces time and cost.

Users
Users of M&U Work Order

(SCR created on 4/28/2014) Army does not have in-house maintenance shops.? Vehicles are taken to local vendors to have work completed.? Need to track mileage of vehicle while in maintenance cycle. ADDED: - Mileage In field is not available to capture meter reading at time of delivery to Maintenance Shop nor is it pulled from Utilization table.? Customer requires accurate mileage while in maintenance cycle.? DPAS currently captures end of maintenance meter reading, just need starting meter reading. Add a Mileage In and Mileage Out field on Work Order.? Have Mileage In default to last mileage recorded but changeable.

Description
Recurring Dispatches are not reflected on Dispatch Calendar on M&U Dashboard.

Recommended
Reflect all Dispatch Codes and Dispatch Statuses on Dashboard Calendar for all days of the week.

Mission Critical
Mission critical because all dispatches are not visually available at a glance on the calendar.

Benefits
Reduces time and increases visibility of all dispatched assets on one calendar regardless of day of the week.

Users
M&U Dispatch

07Dec2018 – cancelled per Deric Sims
No longer needed due to past enhancements.

Description
Under Mass Data, desire a Customer/Unit ID field to identify a POC name, email address and telephone number.  (Not a Mandatory Field)  This will reduce the number of 'Dispatched To' names that show up during Dispatch.  Currently every operator loaded in DPAS appears making the search cumbersome.  This improvement will reflect operators from Customer ID or Cost Center only. 

Recommended
With Cust/Unit ID, we can associate customer for Recurring Dispatch, only pull operators associated with Customer ID during Dispatch and notify POC via email for Pending/Recall work orders.

Mission Critical
Streamlines Dispatch functionality for unit issuing.

Benefits
Reduces time for vehicle assignment and allows for a more accurate management and assignment of assets.

Users
M&U and Dispatch Officer

07Dec2018 – cancelled per Deric Sims
No longer needed due to past enhancements.

(SCR created on 3/3/2014) Inability to accept data that captures/charges supply and local vendor parts by way of flat file upload. 1) All parts from base supply are documented on a work-order.? Normally, a report (D22)is uploaded (flat file) into current legacy system and parts are charged through this process.???????????????????????????????????????????????????????? 2) All parts from vendors are documented on a work-order. For vendor parts either receipts are manually inputted into the legacy system or a vendor supplied flat file is uploaded into current legacy system and parts are charged through this process. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?