Description
Report Manager - In the event of an aircraft accident we need a method at the region level to take a snapshot of a warehouse inventory, as well as all it's current and historical inspection "QC" data.

Recommended
Add an unalterable, date and time stamped report named "site snapshot". the report needs to contain a list of the warehouses in a selected site, the inventory in those warehouses with all? the same information available that is in inventory update manager, "QC" inspections associated with those items(current and historical), and personnel in the warehouse

Mission Critical
Critical. This data is used in accident investigations and safety boards. we need the ability to freeze this data and ensure it is unaltered while still allowing the mission to continue.

Benefits
Prevents evidence tampering in the event of an accident investigation

Users
All AFERMS users

16May2016 – cancelled
DUPLICATE – SCR 00898 is original entry.

Description
We have no means to view expiring items at a logistics program level under inquiries.

Recommended
Add: inquiry, inventory, "expiring items" - have allow search by NSN or LIN/TAMCN. As a search feature, include a date picker with "items expiring before this date". ensure DOM DOI and DOE columns are viewable. Add a button "AFTO223" that populates and generates the attached form. The AFTO223 is a time change forecast. it has three years broke out by quarter and four additional years. this is not calendar year based, it is fiscal years and quarters. The first quarter of a year starts 1 October. Allow multiple stock numbers to be selected for addition to the form and allow the starting FY(fiscal year) to be selected before generating form.

Mission Critical
This is why we got into DPAS. we cannot accurately forecast with the current inquiries.

Benefits
reduces manpower and human error in time change forecasting

Users
all users

16May2016 – cancelled
DUPLICATE – SCR 00889 is original entry.

Description
MDA is a Research, Development & Test organization supporting all of the US Military Service Branches. Assets are often transferred to the Military not knowing if those same assets will return to MDA for an upgrade, refurbishment or even re use. MDA would like to have the ability to reuse the same National Stock Number, Serial Number and Asset ID as previously sent to another organization.

Recommended
MDA request the ability to receive an asset back into DPAS without having to change the National Stock Number, the original Asset ID and/or the Serial Number. All the information will remain the same even after the asset has been sent to an outside agency.

Mission Critical
This is mission critical. MDA should be allow to use the same National Stock Number, Serial Number as well as the Asset ID. The same assets are being sent back to MDA with the same fields as the asset was sent to the services or outside location.

Benefits
It would save everyone time having the ability to return assets to DPAS with the original fields. It would also insure depreciation, history and the overall uniqueness of the assets remains the same.

Users
This would affect all users within our component and agency. This would affect all users within our component and agency.

Description
MDA has opted to use actual historical cost for MDA missiles and spares recorded in DPAS, instead of moving average cost. Moving average cost is usually used for inventory items with frequent turnover, and minimal change in cost from acquisition to acquisition to replenish inventory. MDA's missiles and spares can have a significant variance in acquisition cost per Contract/CLIN acquiring the items, low consumption rate, and are managed by serial number. Many of the missiles are destined for transfer to a Service, and MDA would prefer to keep the valuation of the missiles as actual historical cost. At this time DPAS does not have a way to track OM&S at actual historical cost and MDA is requesting a system change to allow for this option.

Recommended
MDA would like a new Type Asset Code in the DPAS Catalog called OM&S. This new Type Asset Code would be for Missiles, Rockets, Rocket Stages, Rocket Motors, etc. It would allow MDA to report the total number of OM&S and value whenever needed.

Mission Critical
This is mission critical. MDA must know how many Missiles, Rocket and Rocket Parts are currently on hand in DPAS with the total cost for each asset.

Benefits
A report would keep the financial group from going through every asset file to report the number of missiles as well as the actual cost of each.

Users
This would affect all users within our component and agency.

Completed - Release 5.1 - 28 April 2017

Description
Currently the DPAS user can not complete a Pending Transaction, disposition outside of DPAS, using the document number. Assets in a Pending transaction must be removed by like stock numbers. DPAS allows the user to print the DD1150 with all assets associated but the assets must be moved out of DPAS by stock number. This can be a long process.

Recommended
Please allow Pending Transactions that were dispositioned outside of DPAS to another organization, to be complete by using the Document Number as well as being able to reject assets if needed.

Mission Critical
It's critical when you have several hundred assets with different stock numbers, transferring out of DPAS, that must be completed through a Pending Transaction.

Benefits
This would reduce time, cost and accountability.

Users
Yes, this affects all users within our component.

Completed – Release 6.2 – 31 August 2018

Description
Currently when receiving Real Property, you have to complete the entire receiving process, then perform an update before you can attach a document. MDA request the ability to add attachments to assets when receiving Real Property this will eliminate several steps in the Real Property receiving process.

Recommended
When receiving Real Property, the capability to add the attachment during the receiving process under the Basic Tab will eliminate having to perform an update to attach a document to the record.

Mission Critical
Critical. Currently, MDA is in the process of updating records and closing in on being audit ready by FY 17. By streamlining the process this will greatly reduce the time and simplify the process. This will not only benefit MDA, but all DPAS users as a whole.

Benefits
Implementing this change will reduce time and streamline the process when receiving Real Property. Having to complete the receipt process and perform an update just to add an attachment could be eliminated, this will improve time an accuracy.

Users
This will affect certain users within program/Central Property Office in the Missile Defense Agency.

Description
Currently SKO Catalog does not provide for the ability to export or import SKO Catalog configurations.
The current process is time consuming.
Sometimes these kit configuration can be found in other systems or within documents where the data could be readily copied/pasted into an Excel spreadsheet.

Recommended
The desire is for DPAS to be allow for the authorized user to export current SKO Catalog configurations to an Excel spreadsheet, allowing them to be modified and then imported by DPAS to update the configuration as well as adding new configurations.

Mission Critical
Not considered mission critical.
The SCR is based upon observations by the DPAS PM (Stossel) and the author during a site visit to DMC Albany. This SCR is being submitted at their request.

Benefits
By allowing for SKO Catalog to be maintained similarly to Unit Issues, etc, it will reduce time and improve the overall accuracy of hte data.

Users
This would improve the use of SKO Catalog for all users of this process, which the primary users are the USAF and USMC.

Description: Currently, there is no functionality to be able to associate an Responsible Officer (UNIT CUSTODIAN) to multiple UICs which we are now discovering to be a problem when RO's are attached to exercises.? We need to be able to associate an RO ( UNIT CUSTODIAN) to multiple UICs and 'Account Names' - Example (I.E. M11110, M11110-ITX, M11110-SPMAGTF 16.2).? See SCR submitted for 'Account Name' Field creation. Recommended: Recommend that we be able to associate RO's (Unit Custodian) to multiple UICs to be able to meet exercise requirements for Unit's and RO's according to message distributed by I MEF G4.? Message attached. Mission Critical: Yes. This will keep the Unit CMR's from being rolled up under one UIC and speed up the process for reconciling CMR's for specific UIC's. Benefits: Having this functionality will keep the Unit CMR's from being rolled up under one UIC.? Also it will give us better item visibility and reduce confusion in regard to what gear was issued to the unit and what exercise an issue was for. We will need the Functionality prior to Implementing Miramar UIF on 8 June. Users: All UIFs.

Completed – Release 5.0.00 – 03 February 2017

Description
Currently, there is no identifying field for an Account Name. Having this additional field would help associate a Responsible Officer to a UIC.

Recommended
Recommend that an 'Account Name' field (25 varchar length) be created to identify when an RO has multiple CMRs from the SAME UIC. The 'Account Name' would optional (null values accepted) and grouped with the UIC and RO to determine unique issues under the issuing Warehouse DoDAAC.

Mission Critical
Yes. This will keep the Unit CMR's from being rolled up under one UIC/Warehouse DoDAAC and speed up the process for reconciling CMR's for specific UICs and Responsible Officers. Also mandated by CG I MEF message, accompanied with this SCR.

Benefits
Provides better accountability and reduces the confusion as to what gear was issued to the unit and what equipment was issued for a particular exercise. This functionality will be required prior to Implementing Miramar UIF on 8 June.

Users
All UIFs

Completed - Release 5.0 - 03 February 2017

Description
EO 13693 requires an interface between Agency FMIS and GSA systems for Fleet information exchange. Leased vehicle fuel use data at GSA needs to be pulled at least monthly.

Recommended
Currently no interface. Data can be extracted from GSA Drive-Thru, Reports Carryout, Fuel Use in a .CVS file. Request load functionality. User will request Summary Fuel Data by Vehicle for upload into DPAS. Fields required:

• VIN
• Region
• Start Date
• End Date
• Purchased Fuel Type
• Natural Units

(See attached)

Mission Critical
EO 13693 required to meet Vehicle Level Data Reporting to FAST

Benefits
Reduces time and improves accuracy of information.

Users
M&U

Partially Completed - Release 4.1 - 29 July 2016