Description
Currently DPAS does not calculate an assets end of life (EOL) when its average annual sustainment cost first exceeds, or is projected to exceed, its depreciated value, or seven years after a depot rebuild, whichever comes later.

Recommended
See notes below.  This feature was developed by 441 VSCOS and added to LIMS-EV Transaction Request Tool. 

Mission Critical
Mission critical.  AFI 24-302 states "Use economical, reliable and up-to-date procedures to authorize, acquire, account for and maintain vehicles in a safe and serviceable condition throughout their lifecycle."  The EOL calculation helps determine the most economical time to replace an asset.

Benefits
The benefits of implementing this solution will enhance the annual vehicle purchase drill be pin pointing the most economical time to replace an aging asset.

Users
All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  

**NOTE** This SCR is in conjunction with SCR 01422 Vehicle Prioritization Model.

21Feb2025 – cancelled per Luther Meitzner

Description
Operator / Technician listing is very long and slows down the assignment process in Dispatch.  There is no quick way of finding an individual.

Recommended
Utilize the IntelliSense capability when assigning "Dispatched To" during the Dispatch A/U.

Mission Critical
Critical to the accurate and expedient assignment of personnel to equipment

Benefits
Reduces time and improves accuracy of asset assignment.

Users
Only personnel identified to accept material via M&U.

Description
The Agency has no way of monitoring user activity to ensure accounts stay active.

Recommended
Request adding to Accounts Status to the Inquiry of the IO, APO, M&U Officer and M&U Dispatch Officer roles.  Currently activities task DPAS Security to produce report for them.

Mission Critical
Critical to mission by ensuring accounts remain active especially for the National Guard and Reserve Units

Benefits
Ensure users with sporadic work schedules maintain active accounts and will not spend time reactivating them.

Users

Description
In PA, Cost Centers can be created for each asset.  It would be efficient to have that migrate to M&U for reimbursements for Work Orders and Dispatch

Recommended
If created in PA, use the Cost Center as the Flag for reimbursement.  This will give another level of identification for funding and will automatically be assigned to assets in M&U.

Mission Critical
No

Benefits
Improves the process of identifying costing source for WO and Dispatch.

Users

Description
Currently, DPAS cannot differentiate life expectancies for all assets to determine the appropriate replacement cycle necessary for programming purposes. The Vehicle Prioritization Model provides better justification for appropriations and is a proven business model that identifies vehicle requirements while connecting them with the mission they support.

Recommended
See notes below.  This feature was developed by 441 VSCOS and added to LIMS-EV Vehicle View.

Mission Critical
Mission critical.  AFI 24-302 states "Use economical, reliable and up-to-date procedures to authorize, acquire, account for and maintain vehicles in a safe and serviceable condition throughout their lifecycle."  The Vehicle Prioritization Model helps determine the most economical time to replace an asset.

Benefits
The benefits of implementing this solution will enhance the annual vehicle purchase drill by pin pointing which asset to replace at the most economical time.

Users
All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  

**NOTE** This SCR is in conjunction with SCR 01426 Calculate Asset End of Life

21Feb2025 – cancelled per Luther Meitzner

Description
When Wide Area Work Flow (WAWF) initially implemented an interface with APSRs, the intent was to provide Receiving Report data for New Procurements, and provide the capability for APSRs to track and confirm receipt of GFP/GFM shipments to contractors utilizing the "TS" functionality.  Utilizing the interface for transfers provided for an auto update of the IUID registry of transfers between the government and contractor. To support this activity, WAWF provided a pseudo DLMS 856S via GEX.  WAWF does not actually generate or receive the DLMS 856S, but rather used GEX's translation service to put the data into the 856S format or to extract the data from the 856S format.  During a recent WAWF Requirement meeting, it was discovered that WAWF has since implemented the DLMS 861 Transaction Set for materiel acceptances rather than using the DLMS 856S.  This was not known to DPAS as DPAS believed it was receiving acceptance notices via the DLMS 856S.  A review of the DLMS transactions DPAS received in 2017, it does appear that DPAS does in fact receive materiel acceptance via the 856S transaction set.  The WAWF Program believes DPAS should transition to the DLMS 861 for Acceptance.  During the review, it was discovered that DPAS is not capturing the "Acceptance Dt".  Everything is being driven by the Receipt Dt.   

Recommended
Review current WAWF processing and determine whether DPAS should transition to the DLMS 861 Transaction Set for materiel acceptance.  If it should, then make the necessary changes to provide for the receipt and procssing of the DLMS 861 Transaction Set.  Regardless of the outcome of the review (Implement the DLMS 861 or stay with the DLMS 856S), DPAS should be basing the Property Book  / Warehouse Receipt based upon the Acceptance Dt, not the Receipt Dt.  This change should be implemented regardless of the transaction set the Acceptance Dt is acquired from. 

Mission Critical
This SCR is considered essential for DPAS compliance with DoD Policy.

Benefits
DPAS maintains its compliance with DoD Policy

Users
This SCR would affect any customer that utilizes the WAWF/IRAPT interface.

Description
Currently, there is no way to run a report or inquiry that identifies assets that are due scheduled maintenance with intervals by mileage.  Additionally, the self generated work order makes managing the scheduled work load cumbersome because of the possibility of several work orders being opened for the same asset ID.

Recommended
Update Upcoming Work Report to include a column and indicator that identifies an asset as within its scheduled maintenance window per the "Sched Before Util Qty" field.  The indicator would be the mileage difference between "Util Qty Frequency" and "Sched Before Util Qty".  If the asset has no scheduled maintenance intervals due, it will not display on the report.  Also, we need a feature to disable the system generated work order.  A check box; Auto Generate Work Order Y/N?   This will give the maintenance scheduler the ability to decide on how to assign/document scheduled maintenance actions.

Mission Critical
This is mission critical.  AFI 34-302 states "Scheduled maintenance includes PM&I and Special Inspections, at regular intervals to maintain a safe and serviceable vehicle fleet."

Benefits
The benefits of implementing this solution would be a more streamlined and user friendly scheduled maintenance program.

Users
All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  

Description
Currently, there is not a easy way to see what transactions in the M&U DPAS module that have been completed on a daily basis. So managers can review and make any edits as needed.

Recommended
DPAS the ability to produce a Prior Day Edit Report, when requested with the following perimeters in the fields:

• Work Order inputs (# open, # closed) with Work Order # and Asset #,
• Labor Hour inputs by Work Order # and Sub Work Order #,
• Work Plans associated.

Parts charged to include:

• work order #,
• cost,
• nomenclature & quantity,
• and warranty.

Parts ordered with:

• work order #,
• quantity,
• nomenclature,
• and est cost.

All Utilization updates and the data to go with the:

• Asset Id,
• Meter Reading inputted,
• Fuel Qty,
• Fuel Cost,
• Fuel State.

Mission Critical
This is critical.  Fleet managers count on viewing information to be able to make informed decisions to manage Air Force fleets around the globe. Also, per AFI 24-302, daily work orders and transactions need to be reviewed and corrections be made to, if needed.

Benefits
Having this Prior Day Report will enhance day to day operations for the Air Force fleet. Also, this will ensure UICs are compliant with AFI 24-302 on daily requirements.

Users
This SCR will affect the entire AF Agency, all Air Force fleet managers/maintenance controllers utilize this information for day to day fleet management operations.  

Description
During the past ICART Audit Readiness Inspection for the CSP it was noted that extra Columns are needed to be added to the Inventory Control Point>DLMS Transaction Inquiry Review area to make the CSP compliant with the current Marine Corps Audit Readiness policies. 

Recommended
In order for CSP to be compliant with the current Marine Corps Audit Readiness program we are requesting that the Below columns be added to the following area Inventory Control Point > DLMS Transaction Review:

• WAREHOUSE DODAAC
• USER ID (who created the Transaction)
• Serial Number

Mission Critical
Yes, without these columns the CSP is not in compliance with the current Marine Corps Audit Readiness Program.  DoD mandated audits are high visibility and compliance is critical to CSP success. 

Benefits
Having this functionality will help the CSP be in compliance with the current Marine Corps Audit Readiness Program.

Users
ICP MODULE

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

Description
The "Acquisition Date" field in DPAS is inconsistent with the definition of the term in DPAS, "The date of fund approval / obligation". As the field is titled, "Acquisition Date", most users record the date the asset was received or even ordered. Very few people inherently equate the acquisition date to be the fund obligation date. Because of the ambiguous nature of this term, and the fact that users typically do not use the DPAS glossary to find out what each field is actually requesting, it has resulted in multiple inconsistencies which have basically made this field misused from a data management perspective.

Recommended
Change the "Acquisition Date" field in DPAS to "Funds Obligation Date". This change would align the existing definition of the field to the name of the field and reduce confusion for users.

Mission Critical
No.

Benefits
Improves data accuracy of financial reporting and identifies the funds obligation date from the funding documents, showing auditors the true date when the government committed funds to the order. This would also provide a much clearer understanding for the users out in the field.

Users
This affects all DPAS PA module users.