AMENDED INFORMATION:

Description
There is currently no capability to view attachments or add attachments to the electronic records of assets that have been removed from DPAS as a result of processing a Disposition and / or Transfer. This SCR is an update and replaces SCR Number 858 submitted July 2015.

Recommended
Provide functionality for attachments that exist on an asset to be viewed after the asset is removed as a result of a disposition and / or Transfer and the ability to add attachments to assets for the following:
- Assets deleted under Asset Management / Disposition
- Assets transferred under Asset Management / Transfer

Mission Critical
Yes. Navy FIAR control points require supporting disposition and transfer documentation be attached to asset records to include: key supporting documents (DD 1348/DD 1149) and key supplemental supporting documents.   Recent Ernst and Young Navy Audit notice of findings provide examples of assets dispositioned or transferred that do not have KSD to support those transactions.  No process exists to add KSDs or view KSDs that previously were attached to the asset record.

Benefits
This implementation will support accountability and auditability at all levels and for all services within DOD. 

Users
Affects all Navy Site ID's and UIC's.

You cannot add attachments to assets removed after processing a Disposition and Transfer action. Recommended solution: Provide functionality to add attachments to delete assets: 1. Multiple attachments to a single or multiple deleted asset record. 2. A single attachment to a single or multiple deleted asset records.

Added from Cancelled SCR 01384:

Description
You cannot add attachments to assets removed after processing a disposition transaction has taken place.  Often APO's forget to attach key supporting documents to asset records before the disposition transaction is processed.  

Recommended
Provide functionality to add attachments to delete assets:

1. Multiple attachments to a single or multiple deleted asset record.
2. A single attachment to a single or multiple deleted asset records.

Mission Critical
Navy FIAR control points require supporting disposition documentation be attached to asset records to include:  key supporting documents (DD 1348/DD 1149) and key supplemental supporting documents in support of audit reviews.

Benefits
Supports documentation for accountability and audit.

Users
All Navy Site ID's and UIC's.

Description
For GSA vehicles, monthly mileage is used to determine fuel cost. Meter readings are either captured at the pump from manual input from driver or agencies can transmit via a File Transfer Protocol (FTP). Desire is to use end meter readings from DPAS Dispatch as a more accurate utilization for transmitting to GSA for cost determination.

Recommended
Similar to AIRRS flight utilization reporting, transmit captured meter readings from DPAS Utilization, at a minimum, weekly to GSA via FTP. Make DPAS the authoritative source for GSA leased utilization reporting.

Mission Critical
This is mission critical and mandated for GSA vehicles IAW Drive-Thru’s FTP Monthly Mileage Upload Tool User Manual
(http://www.gsa.gov/portal/getMediaData?mediaId=208083)

Benefits
Improves accuracy in utilization reporting, eliminates the manual monthly reporting and uses DPAS as the authoritative source

Users
This is a Fleet Manager (M&U Officer) requirement to report asset level utilization and the Dispatch Officer/Specialist will capture at close of each Dispatch.

Combined with SCR #00990 and SCR #01142

Completed – Release 7.0 – 20 April 2019

Description
When exporting data from Defense Property Accountability System (DPAS) that contains more than 25,000 records, the users receive an error message that says the following:
Max Export Limit Reached
The maximum limit for exporting is 25,000 records.
This can affect users who are performing any type of analysis of mass records. It would be best to have no hard limit on an amount or records that can be exported.
I am requesting that we modify the maximum limit. My recommendations are below, in the preferred order (if option 1 can be achieved, then use that. If not, then see if we can use option 2...)

1. Unlimited
2. 1,000,000
3. 500,000
4. 250,000
5. 100,000

Please note that if any of the options are placed in effect, then the generic file format for Excel (.xls) needs to be changed to the following file extension: .xlsx. The current format, .xls, is limited to 65536 rows and 256 columns per sheet; however, the file extension of .xlsx allows 1,048,576 rows and 16,384 columns per sheet.

Recommended
I am recommending that we modify the maximum limit.
My recommendations are below, in the preferred order (if option 1 can be achieved, then use that.
If not, then see if we can use option 2...)

1. Unlimited
2. 1,000,000
3. 500,000
4. 250,000
5. 100,000

Please note that if any of the options are placed in effect, then the generic file format for Excel (.xls) needs to be changed to the following file extension: .xlsx.
The current format, .xls, is limited to 65536 rows and 256 columns per sheet; however, the file extension of .xlsx allows 1,048,576 rows and 16,384 columns per sheet.

Mission Critical
This is mission critical in that it does not allow any type of data mining within DPAS, transitively causing a critical deficiency in the process flow of tasks that require data mining or mass reconciliation.

Benefits

Users
Primarily Supply System Analysts

Tuesday, November 29, 2016:
Marked as included in 3.2 done at a later date and not included in the release letter.

LOGSA requests an enterprise level DPAS Unique item Tracking (UIT) reconciliation be initiated for the attached list of UIT and Asset reporting UIC values within DPAS. Capability to submit a reconciliation was carried over from legacy DPAS to WEBDPAS. ?This is normally requested bi-yearly via help desk ticket submission. Recommended solution:?The reconciliation is required on a monthly basis to support more real-time asset visibility in LOGSA tools in the Logistics Information Warehouse (LIW).

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

Description
There is a requirement to replace damaged and/or lost SKO components using the Inventory Update Manager and there is no (Issue to Assembly) Reason Code to be used for the issuing of replacement Components. Also need a Reason Code to remove components from a returned SKO which are damaged and place into inventory for DMRS processing (Dis-Assembly).

Recommended
It is recommended that an "Issue to Assembly" Reason Code be added so the Condition Code "G" SKO can be easily brought back to Condition Code "A" and ready for issue. Also needed is a Reason Code for Dis-Assembly of a SKO by component for lost or damaged SKO components.

Mission Critical
Yes this is critical so the correct Reason Code can be used with the underlying DLMS transaction captured in the transaction history.

Benefits
Component inventory can be better tracked as it is expended with the correct DLMS transaction be written to the transaction history.

Users
All IIF and UIF.

21Aug2017 – cancelled per James Grimes
We do have processes that will take care of this SCR: 00851 can be removed or deleted.

Currently within the Inquiries/Inventory/Stock Nbr Inventory menu there are a couple parameters missing that would enhance the reporting capabilities within DPAS-WM. Under the Search Criteria a Date range should be added. Also additional columns are needed in the Stock Nbr Qty results. Recommended solution: Recommend that a "From Date" and a "To Date" should be options under the Search Criteria. Also 3 columns should be added to the grid options in the Stock Nbr Qty results field. The columns to add would be "Returned Qty", "Lost Qty" and "Disposed Qty". ?Returned Qty would be the total return number (within provided date range - or all if no date given) for the specified stock number. The Lost Quantity would be the total number of items lost for the same date range. For Lost items the reason codes to be used would be KI (killed in action), LT (left in theater), MD (missing damaged), ?and N6 (NAVMC 6). The Disposed quantity would be the total number of items, by date range, that were Disposed of with either Local Disposal or Excess as the Disposition Type. These items would only be counted for once they have been completed and out of the inventory.

Removed per Norman Clark email on 5 June 2025