The DPAS enterprise accounting module produces accounting transactions that currently are not reported from the accounting service and database. The existing Materiel Mgmt. CFO reports are generated from inventory transactions within Materiel Mgmt., and do not provide for start/end dates or other report filters that would be beneficial for accounting users. This SCR moves the CFO Reports that DPAS produces (Summary and Detail) to the Accounting Service. This will enable provide for a single location for producing CFO reports.

 

Generate new CFO Summary and Detail Reports for the Materiel Management module as well as the Property Accountability module when it is transitioned to using the accounting service. Reports will be generated using the new Accounting infrastructure and codes, such as the new CFO Codes, new action codes, and GLACs. Requirements include a set of Reporting DB tables and background processes that utilize the Accounting Transaction table in the Accounting Service,

 

DOD Accounting Policies including DOD FMR 7000.14 and SFFAS-Statement of Federal
Financial Accounting Standards

 

DPAS Accounting users will have meaningful, useful CFO reports generated from the enterprise DPAS accounting module that will support OM&S and Fixed Assets

 

Frequency: Weekly

 

Unit Return and Stock Nbr Inquiry does not have the option to select My Queries under Grid Options

 

Enable a end user to create and share frequently used query.

 

 

 

Eliminate the time consumption spent on selecting and moving columns within Unit Return and Stock Nbr Inquiry.

 

Frequency: Hourly

 

Requesting an agreement be setup between DPAS and the new FAMIS-GF system to mimic the FAMIS-WCF agreement with the exception of a new interface system code.

 

Requesting an agreement be setup between DPAS and the new FAMIS-GF system to mimic the FAMIS-WCF agreement with the exception of a new interface system code.

 

Interface needed in order to interface DISA General Fund Capital transactions from DPAS into the new FAMIS-GF accounting system.

 

Prevents the need of manual Journal Vouchers (JVs) to be completed every month.

 

Frequency: Monthly

 

If we have two end items in inventory under the same Custodian and the first end item needs be converted to a component to the second end item as the HA;  the first end Item asset can only be changed to a cost or no cost component via transfer to an HA in a different Custodian from the current Custodian then transfer back to the original Custodian to the intended HA.

 

Enable a end user to convert an end item to a cost or no cost component without making multiple transfers to different Custodians.

 

 

 

Eliminate the time consumption spent on transferring assets and coordinating with other custodian to receive and transfer the asset.

 

Frequency: Weekly

 

Problem:  PA currently links asset to Auth LIN/TAMCN Master Key and does not identify which asset belongs to which Authorization Document Number.  Assigning asset to Authorization Document Number only links asset to Auth LIN/TAMCN Master Key which connects to multiple Authorization Document Numbers.  Users must manually edit Authorization Document Number within Obligation Doc Number text field resulting with typing errors or copy/pasting inconsistencies within field(s).  This causes enterprise data integrity issues.  (Please reference Word Document attachment for specific details)

 

Suggested solutions:

 

Department of the Air Force Instruction 24-302 VEHICLE MANAGEMENT

 

1) Allows accurate asset accountability improving data integrity
3) Solves Unit Type Code mapping issues    

 

Frequency: Daily

 

The picking process in the Warehouse Module allows you to create a pick based on the unit issue process, which you can load a Master Issue List for a given order. We would like to preposition materials in containers using the Master Issue Lists without the unit issue process. These lists are much more user friendly than the SKO process, which has proven confusing and misleading on inventory.

 

Create an option from the Create Pick Plan menu to load a Master Issue List (MIL) template and/ or select a MIL to pick when building your pick plan.

 

 

 

This cuts out several steps for the end user in that we don't need to create multiple orders.

 

Frequency: Hourly

The User Review User Profile Inquiry report contains inaccurate and incomplete information. This makes it challenging for IO/AIO to effectively oversee user roles eliminate unnecessary roles and UICs and carry out a comprehensive annual user audit. The data provided in the report is not reliable which hinders the organization's ability to properly manage user profiles and ensure data accuracy. It is crucial for the accuracy and completeness of the report to be improved in order to support effective user management practices.  The inaccurate information hinders the ability to effectively manage user profiles and ensure the security of the system. It is crucial to address this issue in order to maintain the integrity and efficiency of the system.

 

In order to maintain security and data integrity it is important to display the "Last Login Dt" for each module and echelon associated with the roles. This helps to track the activity of users and ensure that only active roles are being utilized. Additionally roles should be suspended when the associated role/echelon is not accessed for 30 days. For example if a user has an APO role in AUIC FE 2345 and FE1234 but does not access FE1234 for 30 days that specific role would be suspended to prevent any unauthorized access.  This will apply to all Roles/Levels across all modules.

 

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 inaccurate information making it difficult to effectively perform these important functions.

 

Displaying correct data is a baseline expectation for a data system. The last login date for each user identification code (UIC) gives the information needed for the Information Officer or Authorizing Official to decide if the UICs are still in use by the user. This helps them figure out if the UIC is necessary for the user to carry out their responsibilities and allows them to remove any UICs that the user is no longer actively using. By monitoring the last login dates the IO/AIO can ensure that access to resources is only granted to those who need it enhancing security and efficiency.  To reduce the risk of unnecessary personal transactions within unassigned UICs it is important to deactivate them. When UICs are not actively assigned to individuals there is a higher chance of unauthorized access and misuse. By deactivating these UICs organizations can ensure that only authorized personnel have access to sensitive information and resources. This proactive approach helps in maintaining the security and integrity of the system ultimately reducing the potential risks associated with unassigned UICs.

 

Frequency: Daily

Role Request forms for all modules do not include a supervisor signature block. This means that without supervisor validation the Information Officer or Authorizing Official has no way to confirm that the user is truly authorized to request the role or Unit Identification Code (UIC). This lack of validation raises the risk of Segregation of Duties violations as well as the possibility of users gaining access to roles and locations that they should not have access to. It is important to ensure that proper authorization processes are in place to prevent these risks.  The Air Force is facing a challenge as it centralizes IO/AIO processes in the new DAF DPAS FMO. When it comes to initial access packages the DD2875 requires supervisor approval to proceed. However for Role Updates only the Role Request form is submitted leaving no clear method to show supervisor approval for the user to obtain the requested role/UIC. This lack of clarity in the approval process could potentially cause delays and confusion within the system.

 

In order for a user to possess the roles/UIC update requested it is necessary to add a Supervisor signature block for approval. This can be done on an AF-specific RR form and the supervisor information does not need to be included in the User Review Inquiry information. This step ensures that the appropriate authority has reviewed and approved the request before any changes are made.

 

Per DPAS IO Guide 2024 Responsibility of IOs/AIOs.  "You will verify that roles being assigned to the user do not conflict with other duties or actions in DPAS or other systems per Separation of Duties (SOD)."

In order to reduce the chances of Segregation of Duties violations it is important to make sure that users only have access to roles and locations that are appropriate for their responsibilities. This will help maintain data integrity within the Air Force communities using DPAS. By implementing these measures we can also improve the accuracy of the annual user audit ensuring that only authorized individuals have access to sensitive information.

 

Frequency: Daily

 

The User Review, User Profile Inquiry, produces a report with inaccurate data.  This inaccurate data restricts IO/AIO ability to accurately monitor user roles, remove unneeded roles, or perform the annual user audit.  Specifically:
3. The "Last Login Dt" reflects the same date/time for all roles and modules.  Require it to reflect the last login date/time for each module and the echelon associated with each role (i.e., Site, AUIC, UIC, MA, Warehouse, etc).  

 

1.  DIsplay the name of the IO/AIO that approved each role in the "Created IO" field.
3.  Display the "Last Login Dt" for each module and echelon associated with the roles.  Additionally, suspend roles when the associated role/echelon is not accessed for 30 days.  For instance, if a user has APO role in AUIC FE 2345 and FE1234, but does not access FE1234 for 30 days, that role would be suspended.

 

Each IO/AIO is tasked with performing an annual user audit and reporting completion to the DPAS PMO, and monitoring roles and user access (segregation of duties, access to unauthorized MAs or warehouses, etc.) is a critical function of each agency.  Presently, the system tools that enable this task display erroneous information.

 

Ensure all DPAS user agencies and IO/AIOs are able to perform the annual user audit, ensure segregation of duties, and remove roles that may be in conflict.

 

Frequency: Daily

 

Recently the DPAS project has utilized Checkmarx code scans to identify potential vulnerabilities and improvements to the DPAS code base. These scans have provided insight into areas of improvement in the application.

 

The DPAS application should be updated to address potential security enhancements flagged by Checkmarx, including additional input validation and deprecation of unused legacy AIT code.

 

Remove potential security risks.

 

Applying recommended updates from Checkmarx will enhance application security and reduce the size of the app through sunsetting of legacy code.

 

Frequency: Hourly