DPAS SCR: 01213

• SCR Number
  01213
• Title
  Asset Warranty Coverage
• DPAS Module
  MU
• Reporting Organization
  AF: VSCOS
• State
  New
• History
  Submitted: 08/10/2017
• Description

  Description
  Problem: Current DPAS method of tracking warranties at the asset level requires the warranty to be established at the contractor/contract/warranty terms/warranty asset association levels. Current capability is time consuming and requires several steps to identify basic/extended/corrosion/emissions warranties to assets managed in M&U. It also does not allow establishing separate warranty start/end dates at the asset level. i.e., one contract may  procure 10 assets, 5 received in Jan and 5 received in Jun, currently the warranty Clause start date would be Jan for all assets received under this contract. The system needs to identify different warranty start/end dates for contracts supporting assets received over a period of time to capture warranty association at the asset level not the contract level.
  Proposed Improvement: Vehicles are procured from various manufacturers under contracts which may include different warranty clauses start/end dates which are subject to change based on contract year or date asset was receipted into inventory. Warranty association should be linked at the asset level not the contractor/contract/warranty terms/warranty asset association levels, this will allow users to manage warranty clauses for multiple assets received under the same contract within different time frames throughout the year without having to load numerous contracts to cover warranty asset associations. 

  Recommended
  Solution #1: Clause Start Date and End Date should be moved to the Asset Association > Create a Add/Delete function. Once the asset reaches its warranty expiration the warranty date would be automatically dropped from the system. Fields to identify the warranty clause/terms can remain the same but at the asset level. This will allow the warranty start/end dates to be assigned at the Asset Level not the contract Level. The AF centrally procures vehicle assets and some of these contracts are active for many years procuring hundreds of assets annually with differing delivery dates. Current DPAS capabilities mandates the same contract # be loaded with differing CLIN or RPN if on GSA schedule to associate each asset warranty start/end date to separate buys under the same contract.
  Solution #2: Do not link warranty association to any contractor/contract information. Warranty terms are established at the asset record in M&U establishing start date and end dates to track warranty term. Once the asset reaches its warranty expiration the warranty date would be automatically dropped from the system. Fields to identify the warranty clause/terms can remain the same but at the asset level. Both solutions would eliminate the requirement associate the asset warranty to contractor/contract.    

  Mission Critical
  Yes, AFI 24-302, para 4.5. mandates the review of all repairs to determine if covered by a new vehicle warranty or a previous contract, COPARS or other parts warranty. TO 36-1-191 establishes procedures for identifying, reporting, and tracking deficiencies and warranties on AF motor vehicles/equipment. The AF uses the FMIS to manage and track vehicle and part warranties linked to assets.

  Benefits
  Solutions will reduce steps required to load warranty information at the asset level for tracking and display within the MAM. It will also improve the accuracy of inputting and updating warranty terms and conditions based on vehicle receipt date into inventory.

  Users
  This will directly effect ALL users with DPAS who are now mandated to use DPAS as the FMIS to manage all NTV along with the AF who manages all AF owned vehicle assets in DPAS.