Add the MFR part number(s), MFR name(s), and MFR CAGE(s) as optional data fields to be added to each grid search, grid data view and the reports such as the ICN report that relate to inventory information. These data fields should be optional and should be available for export when saving out a report.

Provides the CAGE and Part Nbr of the actual item (real identifiers) to the user whereas the AESIP Stock Nbr represents the AESIP database row ky which has no relationship to the item.  It also provides more informed information when the Mfr Part Nbr data is more than 15 characters (Stock Nbr max length).

All users of the DPAS Warehouse Mgmt application.

Please remove the words "LOCAL DELIVERY" from the DD 1149 that is generated when performing a warehouse to warehouse transfer.
Provide an additional warehouse to warehouser transfer page (or shipping detail page) containing the following DD 1149 data elements: Ship to - Marked For, Appropriations Data,Requisition Num, Priority, Authority or Purpose, Voucher Number &Date (a and b), Date Shipped, Mode of Shipment, Bill of Lading Number, Air Movement Designator or port reference no. along with the option to populate the container type information with description, size and weight.

This request is mandatory to help the PEO be audit ready. This information should be easily accessible within the APSR. The users should not have to maintain addition shipping details information outside the application being used to document the shipping (transfer) transaction.

All DPAS users of the Warehouse Transfer process.

1. When processing the MRO denial from the RSA, systematically schedule a physical inventory request to the RSA using the key data from the CR/DRO/RDO - Stock Nbr, Condition Code, Purpose Code, and Project Code.
2. Transmit the inventory request via a DLMS 846P.

Provides all DPAS MM customers with the systematic generation of a Physical Inventory request for a MRO denial.   The PI, once conducted will result in the warehouse locating the materiel or making the needed inventory adjustment(s).

This change impacts all customers of Materiel Mgmt. and those users of the MRO within Warehouse Mgmt.

Create a reversal process for receipts that will also allow for the stock number/serial number combination to be utilized when reprocessing the receipt with the correct 'Local Due- In'.

This will limit the additional workload of manually closing out a requisition and rejecting the 'Local Due-in'. This will also ensure that the audit trail can be traced from the initial requirement to the receipt acknowledgment (527R TH) back to the SOS to close out the requisition.

All DAF activities processing receipts for ICP requisitions.

By improving the unit issue appointments process, it alleviates undue stress on custodians who currently receive email notification their appointments have been canceled. It also provides the service center with accurate appointment information for planning and staffing purposes.

All members that use Unit Issue Request for Appointment processes.

This change impacts all customers of Materiel Mgmt. and those users of the MRO within Warehouse Mgmt.

This process improvement benefits DOD agencies and military services on a daily basis.

Significantly increase data accuracy and streamline user experience with work order creation process.

This process improvement benefits DOD agencies and military services on a daily basis.

Significantly increase data accuracy and streamline user experience with work order creation process.

This process improvement benefits DOD agencies and military services on a daily basis.

20

All users FH-AFHAF Site-id

Change Request: Process Improvement

Description: DPAS is in need of an inquiry system that provides clear visibility into user access history for both current and past role assignments. This data is essential for IO’s and AIO’s as it helps them verify whether users have the appropriate roles and access levels. Without this information it becomes challenging to assess compliance and ensure that users are not over-privileged or under privileged. Therefore, implementing such a system is crucial for maintaining proper access control.

Recommended: Creating an Access History Inquiry is essential for monitoring user permissions. This inquiry will provide clear records of when a user's tier and role access were added or removed. It will display both current and historical information showing the exact date and time of each change. By organizing this data administrators can easily track adjustments and ensure users have the correct access levels. Overall, this tool will help maintain security and accountability within the system.

Mission Critical: Each year IO/AIO is responsible for conducting a user audit and informing the DPAS PMO once it is completed. Monitoring roles and user access such as ensuring there is a separation of duties and preventing unauthorized access to MAs or warehouses is crucial for every agency. Unfortunately the current system tools used for this task are displaying incomplete information making it difficult to effectively perform these important functions.

Benefits: By providing an history Inquiry for UIC and Maintenance Activity the IO/AIOs will have a clearer understanding of the UIC and Maintenance activity required for each user. This will help in determining whether these UIC or Mx Activity are essential for the user to effectively utilize the system. Having this history will streamline the process of assigning UIC and Mx Activity  ensuring that each user has the necessary permissions and access rights. This will ultimately lead to a more organized and efficient system for all users involved.

Frequency: Daily

Users: Unsure how many Agencies and IO/AIOs are in DPAS, but this will impact all of them.

Change Request: Process Improvement

Description: The Appropriation AUD screens in DPAS PA and MM modules do not employ modern technical solutions, and the fields in PA and MM Appropriation are not  equivalent, containing different fields. This SCR is to Tech Refresh the Appropriation AUD to enable it to be deployed as part of the enterprise accounting service for use with all DPAS applications. The appropriation attributes will be updated to use the Standard Financial Information Structure (SFIS) attribute names.

Recommended: Modernize the Appropriation AUD process for DPAS Accounting and match the PA Appropriation fields to the modernized Appropriation fields.

Mission Critical: 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 PA Appropriation AUD. In addition, DoD FMR 7000.14R requires certain data elements to be used in accounting processes.

Benefits: Modernized functionality and similar fields across DPAS modules within Appropriation AUD processes. This will also better prepare Accounting to handle Fixed Asset accounting transactions.

Frequency: Daily

Users: Data established in this process is used by Accounting users on a regular basis. This will impact enterprise accounting which will affect a growing number of users as more use the accounting processes.

Change Request: Process Improvement

Description: Currently, the DPAS Maintenance & Utilization (M&U) module does not allow users to filter or sort inquiries by MAJCOM (Major Command). This limitation complicates the ability to quickly locate and analyze data specific to a particular MAJCOM, resulting in inefficiencies in reporting and decision-making processes. Users must manually sift through extensive datasets to isolate MAJCOM-specific information, which increases the risk of error and reduces productivity.

Recommended: Enhance the inquiry search functionality to include a dropdown menu or selection box for MAJCOM as a filter criterion. This would allow users to limit inquiry results to a specific MAJCOM.

Mission Critical: MAJCOM A4 leaders are not able to pull single, all-encompassing report for their respective MAJCOM maintenance activities at this time. They do not have access to PA, only the M&U module, so it is imperative that they are able to over high-level oversight of their AvSE fleet health.

Benefits: Reduces time spent searching and analyzing MAJCOM-specific data, Increases accuracy by eliminating manual data isolation errors, Streamlines reporting and decision-making with faster, targeted insights, Improves user experience by simplifying searches and enhancing system usability, Aligns with organizational goals for data-driven decisions and efficient resource management.

Frequency: Daily

Users: The inquiry process is used by 100s of users multiple times a day.  

Change Request: Process Improvement

Description: Currently we are unable to upload supporting documentation to a close MRO's only if the MRO has not been released or shipped. When processing an MRO in DPAS we must mark the MRO as shipped for the DLMS transaction to be pushed to G-Army. When the MRO is shipped the transaction is closed. However, at that time we may not have the signed receiving documentation such as DD1348, 1149, or DA3161 because the Property Book Office (PBO) is waiting to see the transaction show up in G-Army. Once the PBO can see and verify the transaction in G-Army they sign the receiving documentation. For auditability we should be able to upload this signed document into DPAS as supporting documentation for the MRO.

Recommended: All the option to upload documentation to any MRO record even it if is in a released, shipped/closed status.

Mission Critical: To improve MRO in supporting KSDs

Benefits: By allow the user the option to upload supporting documentation to the MRO transaction within DPAS even when the transaction is closed it will provide better accountability and auditability of government property.

Frequency: Weekly

Users: All user trying to maintain auditability for government property within DPAS.