Microsoft has announced the end of life "EOL" for .NET 6 as 11-12-24.  DPAS has applications that are using this .NET 6.  These will need to be updated to .NET 8 (Latest LTS Version).  .NET 8 has a scheduled EOL of 11/10/2026.
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core

 

Update applications to .NET 8

 

DoD is not authorized to operate software that is EOL.  Failure to complete the upgrade will result in DPAS not receiving security patch updates / support.

 

Maintain DPAS compliance

 

Frequency: Daily

 

Problem: We have assets that are standard across the enterprise and assets that are specific to a maint activity. We need the ability to maintain standard stock numbers for assets and give maint activities the flexability to add local stock numbers for assets that are only applicable to that maint activity

 

Give the option to have a maint group catalog and/or a maint activity catalog
Make the profile process part of the new cataloging process

 

 

 

This will allow Maint Activities to track maintenance and utilization on "non-accountable" assets that are not in the PA module.

 

Frequency: Daily

 

Update the DPAS Warehouse Module to allow special characters.
Commodity Type AUD - Allow & in the Commodity Type name.

 

Allow above special characters in the proposed fields.

 

 

 

Allow better data for users.

 

Frequency: Weekly

 

Currently DPAS only allows for one Force Element to be applied to a UIC. This hinders the capability from creating more than one Force Element for the enterprise to utilize to posture authorizations

 

Enable the capability for a UIC have more than one Force Element management

 

 

 

As an enterprise we have determined establishing a separate Force Element to manage War Reserve Materiel (WRM) Support Equipment (SE), allowing for the Global Managers to manage all SE. This would include Commercial off the shelf (COTS) and centrally managed/centrally procured SE, this will allow the WRM Global Managers to establish authorizations and have a realistic picture of WRM requirements. In some cases a unit will have standard authorizations and WRM authorizations which are managed in separate Force Elements

 

Frequency: Daily

 

Users need the Secondary Serial field added to the Upcoming Maintenance Schedule (WPMAR20R) report located in Forms-Reports> Schedule Reports.

 

Add the Secondary Serial number field to the report.

 

 

Users will be able to ID the assets due for Scheduled Maintenance easier with the added field than bouncing ITM numbers off MAM to know the asset needed.

 

Frequency: Weekly

 

User are not able to select assets using the Unique Item Designator.  With the Air Force having 1000s of SA/LW in DPAS, there is a requirement for the program manager to be able to view what the AF has and where they are located (what Unit has what).  The easiest solution would be to add the Unique Item Designator to the Asset Inquiry (filter and as a data element to view.

 

Add Unique Item Designator to the PA Asset Inquiry (filter and view).

 

DPAS added Unique Item Designator to the Stock Nbr record.  We now need to be able to filter the asset inquiry using this value.

Provides for a timely report of SA/LW without having to extract the entire AF property book or submit help ticket to have DPAS run a 1 time extracts, which are obsolete when they received as SA/LW are constantly being received and turned in.

 

Frequency: Weekly

 

Within Customer Requisition, Disposition Release Order, and Redistribution Release Order, the qty available for issue by warehouse does not take into account the qtys that allocated to previously approved CRs, DROs, RDOs which is resulting in the overstatement of available inventory. Thus it is allowing the release of orders to the warehouse that cannot be fulfilled.

 

Modify the viewer that contains the qty available to issue to subtract the allocated qty that was assigned to prior CRs, DROs, RDOs that have been approved that have not yet been issued.

 

The current process is not displaying the correct available qty when there are outstanding CRs, DROs, and or RDOs.

 

Eliminates denied shipments by the Warehouse.  Provides an accurate view of inventory that is available for issue.

 

Frequency: Hourly

 

Currently when a user attempts to receipt for an asset that previously existed in the PA Module (current state is deleted), the prior owner must receipt for it, then transfer it to the gaining activity that now has it.  This method is an inefficient process. When the prior owner turned the asset in, and it was subsequently reissued to a new UIC, the new UIC should be able to receipt for the asset without having to contact the prior owner, which no longer has responsibility for it.

 

 

 

 

 

This change will eliminate the new owner having to try to track down the previous owner to have them reverse the disposition which was the correct action for them at that time. It also enables the new owner to receipt without waiting for the reversal to occur.

 

Frequency: Weekly

 

With Air Force being the largest customer of the PA module, and the large quantities of equipment being returned to the wholesale level for storage/refurbish/re-issue, this SCR will be beneficial.

Currently Work Plan Types and Work Order Reason Codes are established at the DPAS enterprise level.  While that sufficed for common/like Maintenance organizations that DPAS supported in the past, it no longer effective in supporting the diverse group of DPAS maintenance users that DPAS supports today.  Given the diverse groups of users, there is a requirement to have unique work plan types / work order reason codes that are applicable to the  type of equipment being supported, e.g. IT, Vehicles, Machine Tooling, Warehousing Systems, etc.    

Replace the current enterprise management of work plan types and work order reason codes with collections that are assigned to the Maintenance Activity level, thus allowing each maintenance activity to have their own unique work plan types / work order reason codes, and /or share a common list that their parent command has established for their maintenance activities to use.

 

 

The enterprise wide management of these lookup values decreases productivity having to select the applicable type / reason from a large list which also leads to a greater chance of selecting the incorrect value.  By having a targeted list applicable to the mission of the maintenance activity will reduce the time to create a work plan / work order in addition to providing for greater accuracy in the selection

 

Frequency: Hourly

 

The Appropriation AUD screens and use of appropriations in the Materiel Management/ICP module require changes for future enterprise accounting in DPAS. Changes include using imported DAI POET data to associate with fund codes and assign to financial obligations; removing fields from this process that should not be on the appropriation AUD; and updating field labels to match current DOD SFIS, SLOA, and DLMS nomenclature, e.g., Main Account Code will replace Basic Symbol. Fields that will be removed from the Appropriation AUD will be used in other UI processes specific to those fields. For example, the cost center field will be removed and a cost center AUD process will be used for assigning cost centers to financial obligations (see SCR 01964).

 

Update the Appropriation AUD screens in the Materiel Management module to make necessary field changes and allow for imported DAI POET data association to fund codes in the Appropriation AUD process.

 

The data elements in DoD OUSD SFIS guidance, Standard Line of Accounting business practice, and DLMS implementation business rules use modern nomenclature currently not used in DPAS. In addition, DoD FMR 7000.14R requires certain data elements to be used in accounting processes that are currently incorrect on the appropriation screens in the MM module.

DAI imported POET data will be available in the MM module; the MM Appropriation AUD will have improved functionality and correct fields as well as updated nomenclature.

Frequency: Weekly

 

 In DPAS today, the Materiel Management module does not currently have a cost center AUD process nor does the Requisition process. For enterprise accounting, cost centers must be available for agencies to apply a designated cost center to each accounting transaction as needed. To make cost centers available, we will implement a cost center AUD process in the Materiel Management as well as remove the cost center field from the MM appropriation screen and make it available within the Requisition Order processes.   The balance of the effort is to develop the new Cost Center processes for use with any module of DPAS that requires Cost Center data.

 

Implement cost center AUD screens using modern technical solutions, employing the accounting microservice and new data tables. The data solution will utilize cost center "collections" to which organizations will be associated. Cost centers will be added/updated/deleted at the ICP tier level from the master data menu. Imported DAI cost centers will also be available for any agency that uses DAI for its accounting management.

 

Per DoD FMR 7000.14 and SFFAS 4, cost centers are required for tracking and reporting accumulated costs.  This change is part of the DPAS technical refresh of the accounting services that DPAS provides as a feeder system to financial systems.

 

DPAS users will be able to add, update and delete cost centers, and associate cost centers to their accounting transactions.

 

Frequency: Daily

 

Problem: When users are using the Search Filters in the Work Order - Open (WPSEN01) screen, there is no ability to filter via Maintenance Activity. Instead users have to try and filter by using the Equipment Pool. Since all of our users have Site level access for Data Inquiry, and this function is an extension of the Inquiry ability, they have to search all 800+ Equipment Pools to find their own.

 

Add the ability to select Maintenance Activity as a search filter option. Also, make it a cascading effect to where only the Equipment Pools from the selected Maintenance Activity populate for users ease

 

 

 

By adding this additional search filter will greatly improve and streamline users abilities to search for open Work Orders by Maintenance Activity and Equipment Pool.

Frequency: Daily

Validation of Capital Assets required for all Army capital assets receipt and accepted through WAWF. Monitoring controls via workflow for completeness and accuracy of GE Valuation data elements with ability to add additional intended use costs including WAWF unit price for each capital asset. Proper identification (UII, material number, NSN, serial number) of capital assets. Ability to capture total capital assets receipt and accepted in WAWF required to be recorded to DPAS following PEO/PM and ASA(ALT) validation.  Remediation effort for many audit findings regarding GE Valuation for 10 Notice of Finding and Recommendations

 

WAWF connects to CAV-GE workflow for each capital asset record disseminated to the appropriate PEO/PM by ship to DoDAAC. Each record is validated by the PEOs/PMs and ASA(ALT) ARD in CAV-GE with an audit trail with formal approvals and reference to supporting documentation. Users within CAV-GE can update specific fields for additional cost and validate the required Dod 5000.64 and accounting standard data elements from the WAWF Receiving Report to DPAS in an automated workflow.

 

Statement of Federal Financial Accounting Standard 6

 

Validated asset records for accurate property accounting and property accountability. Ability to enforce compliance and monitor for completeness, accuracy and timeliness of asset records. Better Army decision making with proper valuation, asset identification and date placed in service

 

Frequency: Daily

 

The current interface control document does not ask for the data related to the Work_Order_Header_ NMC  as well as the Work_Order_Header_NMC_Total header tables.  These tables track the time and reason work orders are placed in a NMC status (including NMCS & NMCM).  Without these tables it is difficult to calculate the amount of time a piece of equipment was down for each status, either total lifecycle downtime or relative to a specific work order.

 

Add all the data elements from these tables to the ADVANA data feed.  Furthermore, the ADVANA Interface Control Document (ICD) will need to be updated to capture the additional data elements and the associated formats.  In addition, any keys necessary to join to the work order header table will need to be included.

 

ADVANA dashboards are needed to support data analytics from DPAS M&U.

 

Allows the ability to capture metrics on how long equipment was down due to supply or maintenance issues.  Attaining lifecycle sustainment data on aviation support equipment was the entire reason for our transition to DPAS M&U.  This is a further step to making that data available to leadership, sustainment orgs, and users across the AF enterprise.

 

Frequency: Daily

 

Create a GUI front-end for the script that can be incorporated into a DPAS admin role that will enable the running of the Warehouse / ICP Re-balance script from a menu selection.

 

This change is considered mission critical in providing improved support to the customer. Today it could take 4-5 days to make the customer whole after the research determines that a re-balance is required. This change will not eliminate the research, but it will eliminate the time required to develop a script, obtain sign-offs and having it executed.

 

Reduces time and cost for the DPAS sustainment team.  Reduces the time the user is out of commission.

 

DoD issued DLMS change 1434 data Sep 5, 2023 that provides for a new Condition Code "U".  Condition Code "U - Limited Remaining Life Before Failure" is to be used in conjunction with serviceable components that were removed based upon Condition-Based Maintenance that is defined in DODI 4151.22.

Add Condition Code "U = Limited Remaining Life Before Failure" ot the DPAS Warehouse / Materiel management applications.   Customers will need to be contacted to determine which customers desire to have this condition code added to their list of valid condition codes as not all organizations are using DPAS to manage components used in conjunction with maintenance.

 

This change is considered mission critical to those customers using DPAS warehouse to manage maintenance parts/assemblies.

 

The benefit of adding Condition Code U is: 1) provides DoD compliance and 2) provides for more accurate accounting of materiel stowed in the warehouse, and 3) enables ICPs that manage reparables to accurately account for the items in inventory.  

 

In many application releases, the Leidos team needs to implement various database infrastructural changes and improvements.  These changes include, but are not limited to, index adjustments, configuration changes, and the implementation of database utility objects.  These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, correctness, and performance of the DPAS system.  I am requesting an SCR for calendar year 2023 to encompass this category of database changes.

 

Implementation of any database infrastructural changes and improvements deemed necessary by the Leidos Team.

 

 

These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, correctness, and performance of the DPAS system.

 

Frequency: Daily

 

In many application releases, the Leidos team needs to implement various database infrastructural changes and improvements.  These changes include, but are not limited to, index adjustments, configuration changes, and the implementation of database utility objects.  These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, correctness, and performance of the DPAS system.  I am requesting an SCR for calendar year 2023 to encompass this category of database changes.

 

Implementation of any database infrastructural changes and improvements deemed necessary by the Leidos Team.

 

 

These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, correctness, and performance of the DPAS system.

 

Frequency: Daily