Type Asset Code & Asset Category Code – These can be opened for edit in warehouse and PA as long as financial accounting is supported for OM&S and Fixed Assets.  

Shelf Life Code - Should allow adjusting between types I & II A job must first be put into place before we can convert to type 0 as this would constitute a bulk inventory roll-up, or the override flag cold automatically be set on the record to retain the shelf life expiration dates.

Currently SKO (Set Kit Outfit) processes are dedicated to the warehouse application. As part of DPAS modernization, the SKO processes are wanted in the Maintenance Module to enable maintenance personnel to manage the build / modification of a SKO using a Work Order.  In future updates, the DPAS SKO process could replace the End Item / Component process that exists in PA today.

 

Build a new, single SKO Management page - from which all management functions can be supported.
Build a new inventory selector to facilitate the addition/replacement of components.

 

The goal of the new UI is for it to be more user efficient, needing less clicks and built to support implementation to other areas of the application.

 

Changes are required to support SKO processing within a Maintenance Work Order. Without this modernization, the implementation of SKO into Maintenance is not possible. This change is part of the approved changes to provide ASA(ALT)  SKO functionality within a Work Order

 

Frequency: Daily

 

• Implement all existing functionality into the new, modernized architecture
• Allows for a more enterprise solution that can be implemented in any area within DPAS where SKO management is required
• Priority need - Build (assemble), Update and Delete functionality

Currently, it is difficult to provide a complete picture of job executions throughout the system.

 

Implement database history tables and triggers for the PA/M&U process queue and batch queue.  Adjust retention policies for job execution log and history database tables to 1 year.

 

 

 

Improved logging and retention of job executions will aid in investigation and debugging of system issues.  This additional information will also provide easier and more complete answers to auditors.

 

Frequency: Daily

 

Current DPAS does not have the capability to report Open Warehouse Actions for Expiring Items.

 

Build new functionality within the Open Warehouse actions to add a section for Expiring Items within 90, 60, 30 days and expired for items with expiration dates.

 

 

This will allow Users to increase their current operational level of support by reducing the time spent generating reports.

 

Frequency: Daily

 

Only two forms currently exist for printing out a completed warehouse issue: Pick List & 1149
Pick List is not a receipt and 1149 is only a shipping doc  

 

Add another form (ex. DD1150) that can be printed which can be used as a 'receipt' for expensing material via Warehouse Issue. Form will need at the minimum:

From Owning DoDAAC/Warehouse, To DoDAAC, Stock Nbr, Mfr Part Nbr, Nomen, Serial Nbr, Qty, ICN, Cost Center, Doc Nbr, Unit Price, Total Price, Signature Block, etc...

 

Since material is being expensed, a signed receipt is required to document inventory loss

 

Since material is being expensed, a signed receipt is required to document inventory loss.

Frequency: Hourly

 

During receipt of a transfer of asset with component(s), the Higher Assembly asset is received without needing to receive the components.  The component(s) are received in another transaction to remove it from the losing commands inventory and into the gaining commands inventory.

 

Add another tab for component's (auto-populate the component's) where the receiving user will validate(check/accept) during the receipt process of the Higher Assembly.  The receipt process will not be completed without validating all of the component's.

 

 

 

This will assist receipt personnel to identify that an asset awaiting transfer receipt has components that has to be verified before accepting the transfer.

 

Frequency: Daily

 

DPAS SCR 00726 provided DPAS with MILSTRIP requisitioning capabilities within the Materiel Mgmt. module. All users wanting to place orders using DPAS must establish a Materiel Mgmt. presence with it being limited to use for Warehouse and Property Accountability orders.  With the Tech Refresh effort, DPAS is proposing to enable requisitioning within any of its 4 primary modules (Materiel Mgmt., Property Accountability, Warehouse Mgmt. and Maintenance Mgmt. The initial Tech Refresh effort will enable MILSTRIP requisitioning within Maintenance Mgmt. (Phase 1), followed by  Property Accountability (Phase 2), followed by replacing the current requisitions capabilities within Materiel Mgmt. (Phae3), with the final implementation being within Warehouse Mgmt (PHase 4) .  Each phase will be have its own DPAS SCR Nbr assgined.  

 

Requisition Phase 1
7. This feature includes the handling of shipment details and the ability to receive for that materiel, upon arrival.

 

FIAR compliance is mandated. This change is considered a necessary feature to improve the audit trail to ensure FIAR compliance.

 

Provides MILSTRIP requisitioning where it is needed.  
Provides financial reporting capabilities for billable orders.

 

Frequency: Daily

This SCR documents a requirement to implement a single DLMS Transaction Review process that will be available to all modules of DPAS. Currently in the DPAS application, DLMS inbound/outbound review is separate and only available for the MM, RG and WH modules. The creation of the DLMS service consolidates DLMS transactions which enables a common DLMS viewer in lieu of having a DLMS transaction viewer / module.

 

As DPAS modernizes it technical platform, a DLMS micro-service was identified as having value to the DPAS program. The new DLMS micro-service will support the processing of DLMS transactions for all DPAS modules. By consolidating DLMS transaction processing, it facilitates DPAS having a single DLMS Transaction Review process.

 

 

 

Benefits:

Reduces maintenance by eliminating multiple DLMS Transaction Review processes that currently reside within each module.

 

Frequency: Hourly

 

Requesting the integration of offline data synchronization. Technicians need to be able to update data while offline and synchronize it once reconnected to WiFi.

 

Create a synchronization queue to track inspection changes made while offline. When the device reconnects to WiFi, automatically synchronize the queued changes with the central database.

 

SecAF Operational Imperatives 5. Defining optimized resilient basing, sustainment, and communications in a contested environment; and 7. Readiness of the Department of the Air Force to transition to a wartime posture against a peer competitor.

 

By incorporating this solution, the integration of offline data synchronization can effectively enable technicians to update data while offline and synchronize it seamlessly once reconnected to WiFi. This will improve performance metrics related to accountability, such as equipment readiness rates, deployment readiness status, and compliance with policies.

 

Frequency: Hourly

 

Redesign the user interface to be more intuitive, user-friendly, and efficient by restructuring menus, simplifying navigation, and improving the layout of screens to reduce cognitive load and make it easier for users to find and access the information they need.

 

See attachment

 

HQUSAF 2030 Strategic Plan directs intuitive design improvements and reduction of training burdens for the DPAS platform.

 

By incorporating these design principles and features into the template, you can create an intuitive and user-friendly interface that allows for efficient task completion without the need for extensive training or learning new processes.

 

Frequency: Hourly

 

As part of the receipt process,the serial number is a mandatory input. However, there are instances were a serial number has not been assigned to the asset.  Currently the DAF manages the assignment of serial number on a local log that is managed in the the Equipment Accountability Element (EAE). However, the receipt is processed in the receiving section, which would require the receiving section to stop the receipt process until they get a serial number assigned. This could cause a backlog of frustrated cargo until serial numbers are assigned.

 

Build the capability to auto assign a serial number during the receipt process. Create a radio button that can be engaged to assign the next available serial number.

 

As outlined in Department of Defense Instruction (DODI) 5000.64 paragraph 4.6, one of the minimum data elements an APSR must include is a serial number. There are some instances were a serial number was not assigned by the manufacture, however DPAS requires a serial number on the property record as part of the receipt process.

 

By implementing an automated process this reduces the risk of assigning a duplicate serial number and also alleviates the need to maintain a off-line serial number assignment log at each of our Logistics Readiness Squadrons.

 

Frequency: Daily

 

Process Improvement:  When we use the DD Form 1150 in DPAS for equipment that is being turned in to the CCAD PBO warehouse that eventually will be turned into DRMS in San Antonio. The material handler has to initiate a DD Form 1348-1 for turn-in that needs the assets part number,Manufactures name and the model number to complete the required documentation.  (All fields)

 

Request that when we go into DPAS to initiate a DD Form 1150 Turn In - that DPAS automatically populates the model number, Manufactures name, and the Model number before printing. (All required fields)

 

The information mentioned in the recommendation is needed to meet all required information to correctly turn-in serviceable property and support property auditability and accountability.  

 

Auto-Fill DD Form 1150 TIN (Populate data from the system to the printable form).  
Manually going into DPAS to pull the required information and add it to the DD 1150 is time consuming/implementation will improve the accuracy and accountability of the information on the DD Form 1150 and satisfy audit requirements.    

 

Frequency: Daily

 

The DPAS system can receive a large number of database requests for static data causing a slow down on the database server.  A more optimized approach to retrieving this data will benefit the entire application.

 

Implement a Redis Caching Server in order to cache requests with heavy reads.  This will also assist with heavy writes of temporary data.  Implementing a caching server will greatly reduce the load on the database server and improve overall performance of DPAS.

 

 

Improved performance of the system.

 

Frequency: Daily

 

AF GFM-A Warehouse module users have requested the capability to enter the document number, associated with a requisition, they receive from AF ILS-S into the Warehouse Issue process.  Entering the document number would replace the DPAS generated document number for this transaction.

On the LPWHN73 screen, provide the user the option to enter the original ILS-S document number ILS-S in the Warehouse Issue transaction or allow DPAS to generate the document number.  This could be similar to the generate serial number option in the warehouse receiving process (LPWHN19 screen) for serially managed items.

 

 

Currently, DPAS generates its own document number for each warehouse issue transaction.  This solution would provide the AF CICP warehouse user with the ability to reconcile their warehouse issue transactions with the requisitions received from ILS-S via the document number.  

 

Frequency: Daily

We are looking to see if DPAS can have the scheduled reports emailed to a group mailbox in efforts to stream line processing depreciation and other reports. This will allow CCAD to establish automated process between DPAS and our system of record.  CCB Mbr Notes:  All user sites should have the capability to enter the site mailbox when selecting this option.  

 

Implementation of scheduled reports email capability.

 

ISO process of continues improvement, this would automate reconciliations between DPAS and LMP.

 

Automate reconciliation between DPAS and LMP,  end user will only have to validate the automated report instead of spending 4 hours pulling data to complete the reconciliation between the two systems.

 

Frequency: Daily

 

The audit community has identified a materiel weakness within the Army processes as to how it is managing Class 7 items being issued to foreign countries via a Presidential Directive (PD).  To eliminate the materiel weakness, DA plans to incorporate the issuance of the equipment into its Decision Support Tool (DST).  There are plans to establish consolidation points that will be managed using the LMP and or GCSS-Army software.  To support this effort, DPAS will need to incorporate a the DST PSD (Potential Source Document) within its Customer Requisition process along with including the value in the DLMS 527D and 856S transmissions.  Consideration should also include incorporating the PSD within the PA Asset Disposition Transfer process.

 

1. Incorporate PSD and FMS Case Number into Customer Requisition and DLMS transactions.
5. Conduct testing with LMP.

 

This change is to eliminate an Army Materiel Weakness in managing FMS issues as directed by a Presidential Directive

 

This change will eliminate the materiel weakness identified by the IG as well as improve the TPF process in supporting DST.

 

Frequency: Daily