Description
DPAS does not send notifications to the PBO for catalog changes made at the FEDLOG level. 

Recommended
Send PBO emails of changes that were made to assets on Property Book due to FEDLOG updates.

Mission Critical
Mandated by AR 710-2, para 2-5o / AIS Manual PBUSE EUM

Benefits
Provides automated notification to PBO.

Users
All Army users

Description
DPAS hand receipt does not contain data elements required by Army, such as authorization LIN, and quantities

Recommended
Require hand receipt generation to include essential data elements required by AR 710-2. 
Hand receipt should sorted by Authorization Property Type Code - LIN-NSN/MCN. 
Essential Data Elements per AR 710-2, para 2-10g are: 

• "Hand receipt"
• "From"
• "To"
• "Hand receipt number"
• "LIN"
• "NSN/PN/MCN/"
• "Serial number/registration number/lot number"
• "Item description"
• "Hand receipt annex/component hand receipt number (if applicable)"
• "Controlled inventory item code (CIIC)"
• "Unit of issue"
• "Quantity authorized"
• "Signature, date, and grade/rank"
• "Quantity on hand"

Mission Critical
Mandated by Hand Receipt accountability required by AR 710-2, para 2-10g. 
Direct Responsibility for property required by AR 735-5, para 2-8a(3).  
Change document posting is required by AR 710-2, para 2-10c(5).

Benefits
Provides data elements required by Army.

Users
All Army users.

Completed – Release 7.1 – 26 July 2019

Description
DPAS does not currently permit editing of FLIS/FEDLOG catalog records.

Recommended
Require ability to maintain local catalog input and ability to change data elements for FEDLOG and AESIP catalog records. 
USASOC should be permitted to edit any catalog records or create records that are not on the Master catalogs.

Mission Critical
Mandated by AR 710-2, para 2-10i(1)

Benefits
Permits USASOC to control their catalog.

Users
All Army users.

Description
End Item and Component capabilities currently in DPAS are not robust or efficient to meet Army requirements.

Recommended
Require component management capability in PA module.
 Require LOGSA published SKO listings in DPAS PA module for P2 Army common equipment.

Mission Critical
Mandated by AR 710-2, para 2-10i(1)

Benefits
Provides SKO process required by Army.

Users
All Army users.

Description
When processing a Disposition / Disposal transaction (action code = DSPL and an address type - DE) a DD form 1348 DRMO Turn in document is generated from DPAS with the FSC  and nomenclature appearing in the stock number field when the stock number is an MCN. 
DLA Disposition Services will not accept the DPAS generated DD 1348 as it does not contain the DLA local stock number (LSN) which is selected from a DLA LSN Master List that is FSC driven.  
The DLA LSN is comprised of the FSC and a "material number".  
Proposed Solution: Provide a process to permit the stock number field on the DD 1348 to be populated with the DLA LSN when the asset uses a DPAS MCN stock number. 

Recommended
Several possible solutions exist: 

1. Create a drop down to select a DLA LSN supported by the DPAS asset FSC and nomenclature and add the DPAS MCN stock number to block 27 - additional data for historical cross reference purposes. 
2. Permit the DPAS user to manually enter the DLA LSN in the DD 1348 stock number field and the DPAS stock number to block 27 additional data prior to printing. 
3. Create a DLA Disposition Services interface with DPAS.   

A copy of the DLA Disposition Services LSN Master list accompanies this SCR. 

Mission Critical
Not mission critical. But is necessary to reduce the manpower effort to locally create a DD 1348 turn-in document that DLA will accept. 

Benefits
Reduces the time to create disposition documents to dispose of assets to Defense Logistics Agency.

Users
This will be very effective in processing disposal documents for all DOD components/Agencies.  

Description
In Master Data under Actbl UIC-/UIC is a field called "STATUS".  This field is either Active or Inactive.  Navy has many UIC's (Echelon IV commands) built as custodians under a UIC.   When these custodian UIC's are built in Master data they are built as INACTIVE.  Since there is no filter or field value equal to Status (ACTIVE or INACTIVE) Navy can not run a report to identify INACTIVE UIC address information.  Only Active UIC's are available via the Inquiry / Master Data / UIC module.

Recommended
Navy needs the "Status (Active and/or Inactive) field added as a filter to the Inquires/Master Data/UIC process and also add STATUS (Active / inactive) as a "field" selection so that it can be added to an exported file.

Mission Critical
Not mission critical.  But needed to support business practices related to UIC management.

Benefits
Provides capability to identify address information of a inactive UIC.

Users
I should think this would be of interest to other DoD components/Agencies.

Description
Approved Program Executive Offices (PEO) need an interim solution to field assets to GCSS-Army units while the Warehouse Module is being constructed and DLMS actions are being worked. Bulk fielding's will require GCSS-Army units to accept manual transactions.

Recommended
Automate process for XML upload from DPAS to GCSS-Army. Use ".xsd" file attached to execute transaction.

Mission Critical
Mission Critical - need automated process in order field material from DPAS to GCSS-Army while CR3607 is being worked.

Benefits
This automated process will reduce time/cost and improve accuracy/accountability by enabling PEO(s) to bring assets into an approved APSR and field without manual effort to GCSS-Army units.

Users
YES. It will affect all users who are required to field assets to units via GCSS-Army.

Description
Hand held Devices are already capturing whether a serial number was captured from IUID or from being typed into hand held for inventory.   Items not scanned are either missing their IUID tag, or the tag is damaged and not scan-able.  Either way, the IUID tag needs to be remade. 

Recommended
Export all inventory records that were no scanned from each inventory into an excel spreadsheet.   Option to export un-scanned IUID tagged items should be part of upload process and/or reconciliation process.  Items listed on spreadsheet can have IUID tags remade either locally or remotely.   Each Record should contain NSN or NIN, Serial Number, CAGE code and TAMCN if available.  

Mission Critical
MCO 4410.28 mandates use of IUID on all controlled items and items over $5000 in value.  Re-tagging of assets whose IUID tag has either been damaged or lost is therefore necessary. 

Benefits
Scanning of assets improves both speed and accuracy of counts.  Goal should be to have 100% of all serialized assets with IUID tags and each inventory should reduce the amount of assets requiring new tags.  

Users
All services utilize IUID technology so all will be able to utilize this functionality. 

Marked Done - Functionality exists through other updates per Rick McMillan 16 March 2023

Description
No Fuel Variance Report to identify potential utilization and fuel charges errors.

Recommended
DPAS will accept utilization and fuel data but if any transaction is outside of a designated variance (10%+/-) of the last utilization update or last fuel charge; DPAS will capture those assets and send to the Message of Day as an open action report. Example: Message of the Day>Asset>Meter Reading Variance Rpt or/and Utilization Variance Report (they could be one report if it's easier)  Once report appeared in the Maintenance Activity and the report was generated as a Message of the Day Rpt it would be up to the user at the M&U to verify and resolve. Agency policy would address how many days the M&U will have to resolve, i.e. 5 Days

Mission Critical
Mandated. It is mandated that AF Maintenance Activities capture and report complete and accurate utilization and fuel charges.

Benefits
Provides away for users to not accept potential erroneous data. Gives a visual alert to users to validate data to ensure 100% accuracy.

Users
Yes all AF users and other Services and Agencies

Combined with SCR #00628

Completed – Release 7.0 – 20 April 2019

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.