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.

When equipment is fielded to the tactical Army via a DPAS TPF function the inventory is decreased prior to the GCSS-A user bringing it to record in their system. The PM must have a way to validate that all equipment they have issued to the GCSS-A customer is brought to record. For ASA ALT to do that today DPAS must pull a report from the back end of DPAS to provide the data to ASA ALT.  DPAS provides viewers within MM that show the status of the various phases of a TPF (PMRs, Issues, ACK/NCK status, intransit status, etc.), but there is no consolidated view.  Having to run a series of queries, then combine the data to determine the status of the TPFs is time consuming that exceeds resource availability.  ASA ALT personnel need to be able to easily determine the status so any issue can be quickly resolved.  The PA module provides no method for viewing the status of a TPF.

 

It is requested DPAS produce a report that a DPAS User can request that provides a summary view by Document Nbr for each TPF for a given period of time (date range) and be able to select All, Open, Closed.  The report should be produced by ICP for Materiel Management Fieldings and by Accountable UIC for Property Accountability Fieldings. There should be an option to request the details by document nbr (Lot, UII and Serial Nbr) that were issued.  The report should mirror the current extracts that DPAS is providing ASA(ALT).    An enterprise report "ASA(ALT) level" would also be beneficial.  An enterprise report (PA and MM) would enable management to have metrics related to the TPF program without expending resources to running numerous reports, then combining the data.

 

ASA(ALT) utilizes DPAS to manage fieldings.  The DPAS user must be dependent and have access to all data required to ensure TPF transactions are closed out in a timely manner.  Expecting DPAS personnel to pull the report from them daily is unreasonable.

 

The DPAS user can track TPF transactions in real-time and take corrective action immediately resolve.

 

Frequency: Daily

 

Currently we do not have way to determine how a piece of equipment will be postured to support War Reserve Materiel (WRM) requirements on the property record.

 

Create a new data element on the property record that is up to 32 alpha/numeric characters. This data element will be manged by a central office and will require a new role to limit edit capabilities.

 

AFI 23-101 Section 1B para 1.4.1. The AF groups PWRC in force generation sets to provide mission oriented operational capability packages or force modules aligned with the air and space expeditionary task force modules described in AFI 10-401, Air Force Operations Planning and Execution, and this instruction.
1.4.2. Force Generation Sets. Force generation sets provide aerospace ground equipment, vehicles (general and special purpose), and munitions support equipment to support initial combat operations. Force generation sets are composed of multiple UTCs that provide a specific operational capability. (Establish the Base, Generate the Mission, and Operate the Base)

 

This will provide the DAF the capability to report readiness posture to support Combatant Commanders to make data driven decisions

 

Frequency: Daily

As apart of AMC's Data Anomalies remediation effort, McAlester Army Ammunition Plant (MCAAP) attempted to update the depreciation period for fire trucks and locomotives. However, MCAAP continuously received error messages and was not able to update the depreciation period for nine equipment assets. We obtained approval from ASA(FM&C) and coordinated required action with Mr. Joe Stossel. On 10 July 2023, per DPAS Help Desk, a system configuration request is required to address this issue.

 

DPAS modification to allow depreciation period adjustments up to 20 years.

Army Regulation 58-1, paragraph 12-2 and Table 12-1
AWCF GE Fire Truck and Locomotives Useful Lives Guidance

 

Implementation and validation of AMC's Data Anomalies Corrective Action Plan, resulting in progress towards General Equipment auditability and Material Weakness downgrade.

 

Frequency: One-time

 

One time data anomalies clean up effort.

NECC has requested a data field that Leidos created to capture the allowance/ authorized quantity and required quantity per stock number at the Warehouse Level. The SAT environment demonstrated the ability to run reports within a warehouse, but not select tiers (e.g LP, Region, Site) as with the ICN Report. The condition code is also of interest in this reporting if we could filter what condition codes we want for each inquiry. (e.g. We select A, B, C, and D to indicate the materiel/equipment can be issued vice Not Mission Capable materiel/equipment).

 

NECC would like to add reporting similar to the ICN Report that includes all tiers and can be filtered by multiple condition codes that includes at a minimum: Stock number, Item Name, QTY on-hand, QTY issued, Total Quantity, Total Price, Reportable Commodity Type.

 

Multiple documents approved by OPNAV grant allowances for equipment to our commands based on Required Operating Capability and Projected Operating Environments (ROC/POE). These requirements build our Table of Allowance (TOA) and are a movable target as missions change and equipment gets refreshed. Need to compare on-hand against allowance to make better business decisions.

 

The benefit is cost savings for identifying excess/shortages of materiel across our force and having better data for our leadership to make better risk and business decisions.

 

Frequency: Hourly

 

User often incorrectly identifies Federal Automotive Statistical Tool (FAST) reportable data within the Vehicle Characteristics.  Although, the vehicle enterprise provides standardized procedures and guidance for Maint Activity users, many times they utilize their own judgment when profiling assets.  This leads to data variances between assets with the same stock number and common characteristics.  Correcting variances must be done at the asset level and creates additional workload on critical FAST reporting requirements within a short timeline.

Allow users with PA catalog role to program Vehicle Characteristics at the Stock Nbr/Manufacture Part Nbr level.  Similar to current process of setting the Stock Nbr/Manufacture Part Nbr as FAST Reportable, when identified (toggled green) additional fields would generate to program the characteristics. This should include the following: Vehicle Type Code, GVWR, EISA Acquisition Code, Vehicle Armor, Emergency Response Vehicle, and Law Enforcement Vehicle.  Correctly programed the Maint Asset Master (MAM) would default to these values and blocked editing.

 

Agencies must report vehicle fleet data using Federal Automotive Statistical Tool (FAST) as required by 41 CFR 102-34 Motor Vehicle Management.  Further, Department of the Air Force Instruction 24-302 Vehicle Management identifies DPAS as the agencies Fleet Management Information System and source for FAST reporting.  Accurate data is critical to meeting congressional fleet management mandates.

 

Strengthens agency's data integrity and improve FAST reporting accuracy.  Reduces data errors and time needed to correct errors.

Frequency: Daily

In order to ensure that cargo is properly handled, the transportation community must be cognizant of the combination of the Controlled Inventory Item Code (CIIC) and Demilitarization (DEMIL) code to determine if the cargo requires additional measures when transporting property and materiel

Populate the CIIC and DEMIL code in the additional data field Block 27 in order for the transportation functional community to determine if additional precautions should be taken.

 

ACDC 0004 Standardization of Controlled Inventory Item Codes and Valid Demilitarization (DEMIL) Code and CIIC combinations

 

Provides additional information about cargo to ensure property is appropriately safe guarded

 

Frequency: Hourly

 

The current WPHRI09 extract currently exports at the Agency level.  With NSWC having several of their organizations embedded in a Logistics Program that is aligned with USSOCOM, there is a need to modify WPHRI09 to extract all NWWC organizations.  In addition, NSWC is requesting several additional data elements.

 

Create a new extract "WPHRI13" that mirrors WPHRI09 with additional filtering criteria and additional fields.

 

Required to provide the data elements and the data for all NSWC organizations.

 

Will consolidate NSWC asset reporting and eliminate 2 existing NSWC extracts that are not providing all of the required data.

 

Frequency: Daily

 

"Only Remaining Items" toggle is not present during a blind AIT inventory. The toggle would be beneficial to work with the stock number value versus the inventory qty value in order for members to view the assets that still require inventory within a specific location

 

Integrate "Only Remaining Items" toggle into AIT Physical Inventory- blind to work with stock number or asset ID versus quantity like currently available for AIT Physical Inventory- visible.

 

-

 

Members will be able to get a visual of what is left to inventory within the defined locations versus having to search down a list of possibly hundreds of line items in order to determine what items are missed before completing the physical inventory.

 

Frequency: Monthly

 

Not being able to export the displayed results from Authorization Management, Authorization Detail and Apply Authorization screens to excel at any operational view

 

Create an inquiry to export Authorization Management and Authorization Details data

 

-

 

Ability to obtain current data results and the ability to sort/filter from the Authorization Management, Authorization Detail and Apply Authorization screens.

 

Frequency: Daily

Users: 200+

Currently there isn't an authorization change request (ACR) process for customers to submit for review/approval. Today, the AF Form 601 is manually populated and forwarded to the Authorization Managers via a SharePoint

 

Add an automated ACR process that will incorporate the AF Form 601 requirements into DPAS.

 

DAFMAN23-122_DAFGM2022-01/5.4.34.1.

This would allow for an archive of all add, change and delete ACR requests submitted by customers in DPAS, to enhance the search process and researching of past AF Form 601s both approved/disapproved as part of confirming current requests.

 

Frequency: Daily

 

Users: 200+

DPAS FSM queue does not offer a manual removal process for downloaded files.

 

DPAS FSM queue automatically deletes files after a specified period (weekly) but also needs an option to manually remove files from the list.  This will reduce errors when multiple files are queued and when errors are made in the download file.

 

-

 

Uncluttering of dowloaded files from the queue.

 

Frequency: daily

Upcoming Maintenance Schedule report (WPMAR20R) does not factor maintenance schedules tracked solely by utilization or provide a projection of when asset will come due by utilization in the future. Additionally, the report does not identify assets overdue if they’ve exceeded the Next Util Qty, only flagging as overdue if exceeding the Next Maint Date.  Users attempting to project when assets are due by utilization must pull several inquiries such as asset utilization to determine upcoming maintenance.  Further, users attempting to identify overdue maintenance must run a separate Upcoming Maintenance Schedule report using backdated Next Maint FROM and TO dates that have passed, i.e. From 1 January 2016 To current date. This process adds additional workload to the user and does not capitalize on system efficiencies.

 

Recommend updating the Upcoming Maintenance Report and creating a new Overdue Maintenance Report. The upcoming maintenance report should include all schedules whether tracked by date, utilization, or both. System should project a date when an asset will reach it’s Next Util Qty based on the average monthly utilization recorded for the asset. The overdue maintenance report should retrieve all assets with a Next Maint Dt exceeding current date and/or current meter reading exceeding Next Util Qty.  Report should include all records regardless of work order status and should not drop a record until the Next Maint Dt and/or Next Util Qty are updated and current. Both reports should include data points relative to schedule maintenance allowing the user to easily identify maintenance requirement.

 

DAF Instruction 24-302 and Technical Order 36-1-191 establish serviceability standards and schedule maintenance intervals.  It is critical for mission readiness to complete schedule maintenance on-time and maintain serviceability.  

 

Implementing this change will ensure fleet manager have full visibility of requirements and greatly reduce past due requirements.  Proper preventative maintenance will reduce sustainment costs and extend asset's service life.  

 

Frequency: Monthly

 

The DPAS user community requested design enhancements to the recently-released React card-based tier selector. The enhancements include: faster methods to search for and select a Tier by auto-selection from the search results and double-clicking the card to select the Tier, enhanced the search to use 'contains' search capability, tier organization in the WM module to be grouped by Region, add number of Items per Page functionality to the footer, add diagnostics to determine how long requests and responses are taking, applying the new Tier selector across all DPAS pages and more.

 

All pages across DPAS will apply the new React card-based tier selector, the tier organization will include the second-level grouping (e.g., WM Region), where applicable, for improved organization of cards, a double-click action on a card will select the tier and close the modal, the footer will be enhanced for improved paging experience, diagnostics for requests and responses from the application will be added and the search functionality will be improved.

 

The new card-based tier selector is essential for the DPAS tech refresh, and provides improved functionality.

 

The Tier selector will provide a fast, easy way for users to locate and select the desired tier.

 

Frequency: Hourly

 

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