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

Recommended
Currently no interface.
Data can be extracted from GSA Drive-Thru, VCSS in a .CVS.
Request load functionality.
Field requirement:

• Statement Nbr
• Statement Date
• Account Code
• Amount
• Vehicle Tag
• Vehicle Class
• Source Nbr
• Sales Code.

A Sales Code table is needed (attached) and codes mapped accordingly to Cost reportable to FAST.

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

Description
EO 13693 requires an interface between Agency FMIS and GSA systems for Fleet information exchange.? Leased vehicle mileage data in DPAS needs to be pushed to GSA at least monthly (Before the 20th)

Recommended
GSA uses a File Transfer Protocol (FTP) to receive mileage information (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

Combined with SCR #00855 and SCR #01142

Completed – Release 7.0 – 20 April 2019

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

Recommended
GSA uses a Application Programming Interface (API) to pull inventory data (attached) and a File Transfer Protocol (FTP) to receive mileage information (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 additional working from closed Help Desk Ticket 9505 since this will have to be modified to complete SCR

Please assist with the following problems within DPAS:

1) To meet EO 13693 VLD Reporting for Vehicle Type, please align the DPAS Vehicle Type Code table to the following values:
Low-speed Vehicle
Sedan/St Wgn Subcompact
Sedan/St Wgn Compact
Sedan/St Wgn Midsize
Sedan/St Wgn Large
Sedan Limousine
LD SUV 4x2
LD SUV 4x4
LD Minivan 4x2 (Passenger)
LD Minivan 4x2 (Cargo)
LD Minivan 4x4 (Passenger)
LD Minivan 4x4 (Cargo)
LD Van 4x2 (Passenger)
LD Van 4x2 (Cargo)
LD Van 4x4 (Passenger)
LD Van 4x4 (Cargo)
LD Pickup 4x2
LD Pickup 4x4
LD Other 4x2
MD SUV
MD Van (Passenger)
MD Van (Cargo)
MD Pickup
MD Bus
MD Other
Ambulance
HD
HD Bus

Is there a way to reset the Vehicle Type Cd to 'Select an Item' for all the current Van categories so FM can correctly identify assets as LD Minivan, LD Van and MD Van?

2) For every DPAS Vehicle Type Code, there should be an Owned and Leased Vehicle Group Code added.
Please add those new Group Codes to:
104 - HD E/ER
107 - LD Van 4x4 (Cargo)
108 - LD Van 4x4 (Passenger)
126 - Sedan Limousine

Very respectfully, Deric J. Sims DoD NTV Fleet Mgr/DPAS SME OUSD (AT&L), ARA Property & Equipment Policy Suffolk Building 5611 Columbia Pike, Rm 05C15 Falls Church, VA 22041 NIPR Email: ?This email address is being protected from spambots. You need JavaScript enabled to view it. SIPR Email: ?This email address is being protected from spambots. You need JavaScript enabled to view it. Office ?703-697-0659 BB ? ? ? 703-901-7882 DSN ? ? ? ? ? ?227-0659 Fax ? ? ?703-692-4557 TIcket 10438 Help Desk Please align the DPAS Vehicle Group and Vehicle Type Cd as directed in attachment. Very respectfully, Deric J. Sims DoD NTV Fleet Mgr/DPAS SME OUSD (AT&L), ARA Property & Equipment Policy Suffolk Building 5611 Columbia Pike, Rm 05C15 Falls Church, VA 22041 NIPR Email: ?This email address is being protected from spambots. You need JavaScript enabled to view it. SIPR Email: ?This email address is being protected from spambots. You need JavaScript enabled to view it. Office ?703-697-0659 BB ? ? ? 703-901-7882 DSN ? ? ? ? ? ?227-0659 Fax ? ? ?703-692-4557 OSD Fleet Management website: ?http://www.acq.osd.mil/pepolicy/fleet/fleet_main.html ? -Original Message ?- From: Hash, Curtis L CIV USARMY (US) Sent: Wednesday, July 13, 2016 13:52 To: Sims, Deric Javier CIV OSD OUSD ATL (US) This email address is being protected from spambots. You need JavaScript enabled to view it. Cc: Packer, Gregory W CIV USARMY CMA (US) This email address is being protected from spambots. You need JavaScript enabled to view it. Subject: FW: Profiling FAST Reportable Assets in DPAS (UNCLASSIFIED) CLASSIFICATION: UNCLASSIFIED Mr. Sims, I have quite a few vehicles that do not align properly with the Vehicle Type and Group Cd's set in DPAS and have attached a spreadsheet showing the issues. I noticed three different issues while profiling my FAST assets. 1. Some Vehicle Group Cd's (GSA Equipment Cd's) are listed under incorrect Vehicle Type Cd's according to the vehicle classifications and equipment codes provided on our GSA Vehicle Master List. 2. Some Vehicle Group Cd's (GSA Equipment Cd's) are not listed under any Vehicle Type Cd so I had to select a group code that most closely matched the vehicle. 3. Light Duty and Medium Duty Vans (both Passenger and Cargo) do not have separate Vehicle Type Cd's even though they are reported separately as either LD or MD for the FAST report. Thank you for your assistance with this matter and please let me know what I can do on my end. V/r Curtis L. Hash Transportation Operations Manager Pueblo Chemical Depot 719-549-4551 DSN: 749-4551 This email address is being protected from spambots. You need JavaScript enabled to view it.

Description
Monthly Depreciation Report (WPACR01M) runs monthly but only remains in the View Forms/Rpts menu for one month.
And is automatically removed when the next months monthly depreciation report is generated.
As an example the Jan 2016 monthly depreciation report auto deletes when the February 2016 monthly depreiciation report populates.

Recommended
The monthly depreciation report should not auto delete and should be available for extract at a minimum for the quarter.
Perhaps longer if possible.
Example:
Jan, Feb, and March 2016 report should be available until the April depreciation runs.

Mission Critical
Not mission critical or mandated but will support FIAR efforts to validate DPAS capital equipment against accounting systems.

Benefits
Financial reporting.

Users
Yes to all Agencies.

Completed - Release 4.0 - 29 April 2016

Description
We need a report that will show inventories due and inventories completed that can be run at any time.
Currently there is not one in DPAS or a way to query the information.

Recommended
A report needs to be developed showing which inventories are due and which have been completed broken down by custodian number.

Mission Critical
AMC has requested this information and I had to contact the programmers at the help desk in order to have them pull the data required.

Benefits
Improves accountability.
Makes it easier to monitor which inventories should be completed within the month.

Users
Certain users

Description
EO 13693 requires an interface between Agency FMIS and GSA systems for Fleet information exchange.
Leased vehicle inventory data at GSA needs to be pulled and leased mileage data in DPAS needs to be pushed to GSA at least monthly.

Recommended
GSA uses a Application Programming Interface (API) to pull inventory data (attached) and a File Transfer Protocol (FTP) to receive mileage information (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

Description
EO 13693 requires all newly acquired passenger and light duty vehicles use a telematic device to collect fleet operational data.
Data can be downloaded from the dashboard into a .CVS file.

Recommended
Create a universal Telematic Load process so Agencies can mass load data to DPAS via a conversion spreadsheet.
Attached is a proposed load spreadsheet.

Mission Critical
Mandated by EO 13693

Benefits
Reduces time and improves accuracy of manually loading.

Users
M&U users

Worked on with SCRs 00944, 00736, and 00735

Completed – Release 6.3 – 21 December 2018

Description
Defense Property Accountability System's (DPAS) current build, version 3.2.01, contains a data validation rule for Sets, Kits, & Outfits (SKO) assets that restrict the Condition Code (C/C) of the Master Stock Number (MSN) to the lowest C/C that exists within its components.
The MSN is commonly referred to as the Header. This disables the user's ability to change and manage the C/C of an asset strictly based off of the results from a Quality Control (QC) inspection. For example, if a component of the SKO is in C/C = 'F' and the QC technician determines the asset should be C/C = 'A', the data validation rule currently in place will prevent the user from assigning the correct C/C to the Header.
Furthermore, when inventory changes to SKO assets are made in DPAS, only the MSN attributes at its level are sent to Stock Control System (SCS), the Inventory Control Point's (ICP) inventory management system.
Consequently, if an MSN received as a Component is in C/C = "A" and a secondary Component is received in C/C = "F", the Header appears to be in C/C ?F? and is erroneously interfaced as such through Defense Logistics Agency (DLA) Transaction Services to SCS.

Recommended
Due to disparities in the business processes between each of DPAS's client organizations, this specific data validation rule does not pose a problem with all users.
It is recommended that Leidos develop a feature that gives users the ability to enable or disable this data validation rule at the Logistics Program level.
The preferred solution is the creation of a new check box for the MSN in the SKO Catalog.
The check box should be captioned: "Condition Code dependent on Components" (or something similar).
This would create a new field on the Collateral Item table in the DPAS database, CC_DEPENDENT_ON_COMP (or something similar).
If the CC_DEPENDENT_ON_COMP = True, then the current data validation rules would be in effect; however, in the case that the CC_DEPENDENT_ON_COMP = False, the MSN's C/C should no longer be affected by components within the Header's SKO configuration. The customer would also like to have the ability to indicate whether the MSN is complete or incomplete.
This would simply be a check box captioned "Complete Kit?" in the Receipt > Verification > Components area next to the Header record when receipting for the SKO asset.
This would create a new field on the Inventory table and the Inventory Update table to indicate if the MSN is complete "yes" or "no".? The default should be "no".
The other area the check box would be placed is in the Inventory Update > Manager > Edit (Update Inventory window) to allow the user to check or uncheck this box if any changes have been made.?

Mission Critical
This is mission critical due to the fact that inaccurate C/Cs are being reflected in DPAS and SCS.

Benefits
The implementation of this solution will greatly reduce the time taken to complete Q/C validations, which lower cost, in addition to improving the accuracy and accountability of Physical Inventory (PI) data.

Users
Though the data validation rule only specifically affects direct users in certain organization, the results with this issue affect all users by secondary and exponential implications to PI accuracy.

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

Description
EO 13693 requires the state where refueling takes place be record and reported for each vehicle.

Recommended
Add a field for 'Fuel State' that is a drop-down table of the 50 states plus DC, PR, OT and FO for the Maintenance Asset Utilization R/U/D and Dispatch Return Utilization tab.

Mission Critical
Mission critical and mandated to support EO 13693.

Benefits
Required reporting of VLD.

Users
M&U.

Completed - Release 5.2 - 29 September 2017

Description
Due to required Vehicle Level Data (VDL) reporting for FAST, many of the elements will be reflected in the Attribute 'Vehicles'.
I am requesting, when ACC = P in the catalog, the only Attribute available will be 'Vehicles'.

Recommended
For all current NSNs with ACC = P, make the Vehicles Attribute available and transfer any data from current Attribute table to the Vehicles Attribute.

Mission Critical
Mission critical and mandated to support EO 13693

Benefits
Required reporting of VLD

Users
M&U Officer

Completed - Release 5.2 - 29 September 2017