DPAS does not provide shipping support for small parcel carriers such as USPS, FEDEX, and UPS.  The Census Bureau ships to its field offices via small parcel carriers.  By DPAS not having a shipping capability, this requires dual input several times to exchange information with the FEDEX website and DPAS management of the shipment.  

 

Recommend DPAS develop a shipping process that will consolidate orders by shipping address (AAC) and integrate those shipments with FEDEX using the available FEDEX APIs.

 

This is a new system capability.

 

Reduces the level of effort to perform a shipment, and increases accuracy, and automates the tracking of shipments.

Frequency: Daily

 

Currently the Agency Pre-defined CFO Asset Detail extract under the Inquires tab does not include the AUIC on the report.

 

Include the AUIC as part of the Agency Pre-defined CFO Asset Detail Extract

-

 

Makes it easier for users to identify AUIC assets are managed under

 

Frequency: Monthly

 

Users: 200

The UII and serial number combination are only visible if running an asset inquiry. DPAS does not appear to
allow the user to search for the UII directly.  

 

We request the UII be printable on all forms (DD Form 1149, 1150, etc) and the printed bar codes

 

Per the DoD 8320.03 and Mil-STD-130N, the UII is to be made visible.

 

The benefit to this solution will be further standardization of government property, more productivity through
the time saved to research equipment, and more accuracy with property accountability.

 

Frequency: Daily

 

When updating a loan code under the Asset Management-->Update-->Loan Update option, the "Cntr Nbr/Dlvry Ord Nbr" list every contract added under the Master Data-->Contract field. DISA has numerous contract numbers within this list and scrolling amid all the numbers is trying to find the proverbial needle in the haystack.  

 

We recommend setting a parameter within DPAS that sorts the contract and/or delivery number, inputted under
Master Data-->Contract menu, to be sort in numerical order.

 

DoD 8320.03 and Mil-STD-130N

 

The benefits of implementing this solution are increased productivity due to a time reduction in searching for
to update records in PIEE/WAWF, and improved property accountability during the contract closeout process.

 

Frequency: Daily

The "Cntr Nbr/Dlvry Ord Nbr" numbers are only visible under the Asset Management-->Update-->Loan Update menu. However this creates confusion when performing an inquiry between the "Cntr Nbr" and "Cntr/PO Nbr" fields and understanding which number correlates to the PWS contract.

YUP

Add an option to select the "Cntr Nbr/Dlvry Ord Nbr" should be a visible option to select when performing an
inquiry.

 

DoD 8320.03 and Mil-STD-130N

 

The primary benefit of implementing this solution is data accuracy. As previously stated, currently there is some confusion between the "Cntr Nbr" and "Cntr/PO Nbr". This confusion interferes with both our government and contractor customers understanding the information and the solution would mitigate the risk of inaccurate information with our workarounds to overcome this obstacle.

Frequency: Daily

 

Various contract number sequences cannot be properly added under the correct contract type within the "Master
Non-DoD Non-FAR) because the character sequence of the contract does not match the DPAS default.

 

We request that the fields be changed to accommodate the input of alphanumeric characters ranging from 10 -
determine whether or not they correlate with the standard uniform contract format number.

 

Per DFARS 204.7003, the contract alphanumeric sequence ties directly into the contract type. We cannot provide accurate information on our part without an update in this field which causes an error.

 

The benefit is an improved accuracy of GFP/GFE data within DPAS. In addition to this, the accuracy may
resolve any information transmission glitches between DPAS and the GFP Module of WAWF/PIEE.

 

Frequency: Daily

 

The Shipment ID that appears after a loan code has been changed from G to C under the Asset Management-->Update-->Loan Code menu, does not appear anywhere else within DPAS to include "Shipment ID" when performing an Inquiry. The incoming/outgoing shipment IDs appear in WAWF/PIEE but not in DPAS. Also, when a return shipment is performed in WAWF/PIEE, the Shipment ID is also not visible.  

 

We recommend either changing the alogrithms to allow DPAS to display all inbound/outbound Shipment IDs
for both Shipment IDs going to and returning from WAWF/PIEE.

 

DoD 8320.03 and Mil-STD-130N

 

The benefits of implementing this solution is better accuracy of tracking shipments (providing corresponding
accountability, and more accurate reportable information.

 

Frequency: Daily

 

The DPAS PA Module does not have the capability of separating accountable and non-accountable assets when developing inventory reports.  Accountable Property Officers' must manually remove non-accountable assets when generating the report; we would like to mitigate possible errors during this process.  An option to create an inventory for accountable assets 'ONLY' would alleviate having non-accountable assets appear on inventory reports.

 

Recommended:

Establish an option to create inventory reports for accountable assets only.  

 

DODI 5000.64, 4.5 (Accountability Records). In an effort to provide a management system for Property Custodians to manage assets maintained in the PA Module, non-accountable assets will continue to be processed, but managed at the Property Custodian level.

 

Benefits:

It mitigates possible errors during the inventory report development process.  Having the option to create an inventory for accountable assets 'ONLY' would alleviate having non-accountable assets appear on inventory reports.

 

Frequency: Monthly

Currently ICP does not have the capability to identify the following: specific asset-id of replacement, end item or Next Higher Assembly component, or Unit Type Code (UTC) requirement

 

Develop additional data element that identifies, replacement asset-id, NHA, or UTC/Auth-id. Data element should be available on Local Due-in report.

 

DAFMAN 23-122_DAFGM2022-01, para 5.2.1.3.2.2.3 when supporting replacement requests, include DPAS Asset-id.

 

 

This will help enterprise ensure requirements are on order to support unit operational plans.

 

Frequency: Daily

1) Provide an option within M&U to cancel a requisition after issue, document the item as returned to stock and remove the entry from the sub work order. 

2) Provide a Maint Issue reversal within the Warehouse module, receiving item back to original warehouse-picked location and remove request from the sub work order. 

3) Provide an option to edit unit cost within sub work order after the request enters "IS-Issued" status. Unit cost correction should allow the user to adjust the Unit Cost within the Sub Work Order Parts section updating the work order's non-labor costs.

 

Department of the Air Force policy dictates documentation of sustainment expenditures and proper management of warehouse inventory.  This change is critical to accurate financial records, strengthening the department's Financial Improvement and Audit Remediation (FIAR) efforts.

 

Eliminates work-a-round required to remove issued parts for the work order and return items to stock. Improves Department of the Air Force’s accuracy of sustainment costs and financial records.

 

Add Current Meter Reading as a available field when performing Asset Preventative Maintenance Schedule Inquiry.

 

Critical to completing schedule maintenance on-time and not degrading mission capabilities.

 

Change will improve data accuracy and user experience.

 

Add Non-Mission Capable (NMC) as a Maint Program configuration option. When option is selected all new work order will open with NMC=Yes as the default with an error message if the asset has an open NMC work order. Open NMC work order "error message" will trigger users to close the current NMC work order or edit new work order to reflect NMC=No.  This would function exactly the same as the current user preference, but give the Maint Director option to implement this default across the Maint Program and affect all work orders.

 

Critical to accurately capturing fleet readiness and meet Department of the Air Force policy mandates.

 

Change will improve NMC data accuracy and fleet readiness reporting.

 

Support for the MS Excel xls format is being phased out.  DPAS needs to updates it import processes to utilize the Ms Excel XLSX format

 

Modify the DPAS import processes to utilize the MS Excel xlsx for the import template, and enable the import to process the updated format file.

 

Microsoft has phased out the use of the xls format

 

Eliminates security concerns and standardizes the process to use current Excel formats.

 

Frequency: Daily

 

As part of the FLIS Transformation and Cataloging Modernization efforts at DLA, FPDW has partnered with DLA’s Defense Automated Address System (DAAS) to provide NSN item data. FPDW web services will no longer be available after 30 November 2023.

 

DPAS jobs currently accessing the FLIS webservice must be updated to pull and parse the IPV8 flat-files from GEX for NSN additions and updates.

 

This is both mission critical and mandated. Updates must be in place for the November 2023 cut off to ensure DPAS continues to receive data from FLIS.

 

This update is required to ensure updates from WebFLIS are reflected in DPAS to ensure NSN data is properly reflected in the system ensuring accuracy and maintaining accountability of data correctness.

 

Frequency: Daily

 

There are several requests from various agencies regarding the expansion of SKO catalog functionality to allow enhanced import/export capabilities, automatic generation of SKO catalogs during the build process, support for multiple nested kits, as well as requirements to support other hierarchical item associations outside the scope of the kitting process. To spearhead these updates a tech refresh of the SKO Catalog process should be preformed to migrate the logic to the new tech stack providing new UI, and preventing migration of newly added functionality  

 

To spearhead proposed updates to the DPAS kitting processes, a tech refresh of the SKO Catalog process should be preformed to migrate the current functionality to the new tech stack thus paving the way to implement user requested system changes to the SKO Catalog process.    

 

Mission critical. Kits continue to be highly utilized by various agencies within the system. Allowing us to build on top of current functionality is pivotal to continue providing additions to support user functionality.

 

Refreshing the SKO catalog process will reduce the time required to apply future updates to the kitting logic by ensuring new functionality is included under the new tech stack, removing the need to migrate logic in the future.

 

Frequency: Daily

 

DPAS M&U lacks the ability to identify items as Critical Assets.  Some assets are of such high importance to the warfighting mission that they need to be labeled as Critical Assets. These items are vital to meeting DODD 4151.18 mandates that maintenance programs are structured to "meeting readiness and sustainability objectives (including mobilization and surge capabilities) of national defense strategic and contingency requirements. It is of significant importance for senior leaders to monitor availability of these assets on a real-time basis to detect and resolve shortages that impact readiness. Per DAFI 21-101 it is the Maintenance Group Commander's responsibility to "Establish Minimum Equipment Levels (MELs) for essential maintenance assets to include support equipment and vehicles.This capability was present in legacy systems prior to our transition to DPAS M&U and is now being accomplished manually via spreadsheet (daily updates required).

 

Add a new checkable attribute in the Maintenance Asset Master labeled Critical Asset. This attribute needs to be added as a field in the Maint Asset Inquiry; needs to be a search option in MAM; and needs to be added to the "additional attributes" section of the Work Order.

 

DODI 4151.18, AFI 10-2402; DAFI 21-101

 

This change will ensure senior leaders are able to assess and monitor the health of critical assets,  maintaining the ability to execute War Orders effectively IAW DoD and AF policy.

 

Frequency: Daily

 

Propose ability in DPAS for IOs/AIOs to be able to query and generate valid Tier names for their group.  This will assist with requesting access for their users as to the 'exact' tier names to request and for the groups to be able to track when tier names have changed.

Mission Critical: n/a

 

 

This will assist with requesting access for their users as to the 'exact' tier names to request and for the groups to be able to track when tier names have changed. Tiers names can be updated (changed) by the functional users is some modules, thus it's important that the IOs be able to obtain the current tier names for requesting user access.

 

DPAS IOs AIOs