DPAS has no automated mechanism to log executions of SQL scripts for release deployments and ad-hoc data changes.  This information could roughly be formulated afterwards, but it would be manual and can be error-prone.

 

Implement enhancements to the system and database deployment procedures that will automatically log release and ad-hoc data change SQL script executions in a new set of database tables.

 

Provides an improved audit trail via the automation and provides additional compliance checks for the SSAE 18.

 

This capability would be very beneficial to support SSAE audit requirements, as well as provide valuable debugging information to the Leidos team for issue analysis and troubleshooting.

 

Frequency: Daily

 

Problem: Customers do not have the capability use M&U maintenance processes unless and asset is in the PA catalog/property book.  However, we also document periodic inspections and maintenance on non-accountable (primarily ERRC XB/XF) assets, many of which are safety critical or require periodic inspections to monitor serviceability.  Lack of capability to use M&U for these assets is driving the use of multiple other systems across the AF, in some cases this is the only reason the other system is being sustained for use.  We have functional communities desiring to use DPAS M&U, but are resistant without the ability to enter non-accountable assets.

 

Create a separate stand-alone M&U Catalog for the non-accountable assets. Assets will be visible only to the Maintenance Activity that created the record and no linkage with any other catalog is desired.  All identifying information will be entered manually by the user inputting the asset.  Asset ID assignment must be unique, recommend Asset ID prefix of "MUCAT".  Customers will need the ability to add/delete assets without affecting the other catalog(s).  

 

Department of the Air Force Instruction 21-101, Maintenance Management

 

The ability to track maintenance on non-accountable assets being used for maintenance of weapons and weapon system will increase accuracy and contribute to elimination of multiple systems presently used for this purpose.  It will also help capture an accurate picture of what is being used or consumed in maintaining AvSE.

 

Frequency: Daily

 

The work order mass close feature does not allow for users to input labor hours. To input labor hours, users must edit each Work Order individually, either before they close the Work Order or retroactively after they close the Work Order. This renders the mass close function ineffective, since users must individually update each Work Order.

 

On the mass close screen, add a line below each Work Order ID to allow for the input of labor hours.

 

 

The addition of the labor line on the mass close screen will enable a true mass close of Work Orders, as it will eliminate the need to update labor hours  individually by Work Order.

 

Frequency: Hourly

 

We require the ability to attach documents to the PA Asset Record from M&U to support retention of historical documents affecting configuration, repairability, and disposal determinations. This capability already exists, but only from the PA module.  The only way to add an attachment to an asset in M&U is to create a Work Order against said asset and add the attachment to the Work Order. The only way to view that attachment is either look in the Work Order. This process is not always warranted/practical, and the attachment is not readily available once the Work Order is closed.

Add an Attachments section within the Maintenance Asset Master edit screen that adds the attachment to the PA record while limiting the number of users within the PA module. Require the ability to access all attachments via the M&U MAM screen and via Maintenance Asset Inquiries.

 

Technical Order 35-1-24, GENERAL INSTR -- AIR FORCE ECONOMIC REPAIR/REPLACEMENT CRITERIA

This will improve auditability as users and equipment sustainment managers can better track, document, and access reasons for asset transfers, modifications, engineering determinations, turn-ins, and retirements. Improves auditability.  Allows users to track and upload prior historical data for maintenance history.

 

Frequency: Weekly

 

One of the key metrics that leadership needs to capture utilizing M&U is the consumption of repair parts.  The ILS-S interface was built to allow requisitioning from DPAS to support this metric.  We now need to add the data elements DPAS utilizes in the application to the Advana data feed to facilitate data mining/visualization.

 

Update the Advana data feed with the ILS-S data fields/elements as well as any interface control documents, Data Dictionaries, & MOU/MOA's with Advana. The fields we are requesting to be added to the interface exchange are as follows; Document Number, Status, Stock Number, Item Description, Qty Requested, Ordered By, Unit of Issue, Ordered Date, Unit Price, Demand Code, Document Type, Document Sub Type, Work order No, Base Supply DoDAAC, Org/Shop Code, Delivery Priority, UJC, Serial/ID No, Maintenance Unit ID code, Standard Reporting Designator, Est Delivery Date, Shipped Qty, Back Order Qty, Killed Qty, Qty Received.  

 

This supports FIAR initiatives and tracking repair parts consumption to the individual work-order/end item.

 

Supports giving leadership and program managers detailed information on repair parts consumption and the associated costs.

 

Frequency: Hourly

 

Current label only has minimal information.

 

Add the quantity, unit of issue, location and project code to the label.

 

 

 

Having the additional information on the labels will make it easier when shelving and pulling material.  This will ensure we are pulling the correct material and also to ensure that the material is being shelved correctly  

 

Frequency: Daily

 

The act of bringing something to book (supply items / accountable property) have a lot of common attributes.  Often times an accountable asset is receipted for / accepted by a Supply Support Activity (SSA) prior to being entered into the organization's Accountable Property System of Record (APSR). The governments PIEE WAWF makes no distinction of what is being received/accepted.  As a result of DPAS's review of its current receiving  processes, DPAS is proposing to develop a single receiving process that would be used within the Property Accountability, Warehouse and Maintenance applications.  

 

Create a single receiving process that is able to receive materiel/assets for any DPAS application.  To support, DPAS will create a structure to communicate the receipt to the applicable DPAS applications through system integration.  The process will create a common identifier so that other services can associate attributes e.g. Utilization to the master record from any DPAS application furthering a unified approach across the enterprise.

 

This SCR is part of the DPAS modernization effort.

 

This will provide a consistent interface for users performing a receipt across the enterprise.  In addition, this should allow new functionality to be more easily adapted for any DPAS application, leading towards a more unified DPAS.

 

Frequency: Daily

 

The goal of the Army is to utilize DPAS for Total Package Fieldings (TPFs). This change provides the Army with an end to end process with the exception of the start of the process which  occurs within the U.S. Army's Decision Support Tool (DST).  Incorporation of a download of data from DST would reduce the PMs effort to plan a fielding.  The incorporation of the DST field tracking number into the DLMS transaction (may require an ADC) would also improve traceability back to the fielding plan.  In addition, there are several improvements that DPAS could implement that would significantly streamline the TPF planning and issue phases for the user community

 

Materiel Mgmt. - 1. Create a TPF Planning tool screen in Materiel Mgmt.  2. Develop an import for DST data. 3.  Enable the user to review/modify the data imported, and select multiple rows into a fielding plan.  4. Assign a number to the fielding plan.  5.  The TPF Planning tool should provide a number of statuses e.g. (new, planning, approved, scheduled for release, released, etc.). When the plan is approved, DPAS will provide the user with the option to generate orders to the stocking warehouse, or allow for manual coordination with the warehouse.  When the user selects the Requisition option, DPAS will consolidate the qty by Ship To and generate a 511R to the stocking location. It will also generate a 527D to the fielding warehouse, and generate 940R MROs for each Unit by Stock Nbr and qty they are to receive.
There should be a single view /report (Enterprise (MP) PEO (MD), ICP that depicts the status of TPF. Search criteria should include Date Range, Fielding Number, Fielding Team Warehouse.  

 

This change will significantly reduce the fielding time. With thousands of fielding occurring a year, ROI can be achieved in less than a year.

 

The proposed change will enhance and streamline the TPF process.  

Frequency: Daily

 

There are over 100 PMs that will utilize this capability daily.

In the new enterprise accounting, a number of failure points are possible in the processing of accounting transactions. To handle these failures, we need to capture the failed transactions and handle various scenarios that could cause the failure. This includes a procedure for "auto-reprocessing" of transactions that initially failed processing; adding a "GUID" column to the Inventory Transaction table to store a unique transaction identifier for the inventory event; creating a Pendulum job from the accounting microservice to capture GUIDs added,  compare and find missing transactions on a schedule (e.g., every 15 minutes); store GUID with validation message; and create a user interface in the DPAS Administration module for Admin user to resolve the issues and reprocess transactions to complete.

 

DPAS will handle accounting transaction errors and failures, providing a procedure for auto-reprocessing as well as providing a method for capturing and handling failed transactions, as well as create a user interface for manual resolution for transactions that are unsuccessful.

 

Per DoD FMR 7000.14, the DoD Components must account for assets. Per FIAR, they must have audit ready financial statements. Failed transactions that are not processed or reconciled will prevent these agencies from meeting their financial reporting requirements in a timely manner.

 

Significantly reduce, with potential to eliminate, out of balance accounts.  This SCR is in support of the DPAS modernization effort as it relates to the accounting and reporting of capital assets costs and depreciation.

 

Frequency: Hourly

 

Accounting users. This will impact enterprise accounting which will affect a growing number of users as more use the accounting processes in MM/ICP.