Description
Create a admin page that will allow Leidos personnel to monitor failed events, review the failed event details, and re-queue the failed events from the GUI. Currently this involves database queries to determine a failed event and then a script from each team to re-queue the events.

Recommended
Add a screen to the admin module to allow Leidos personnel to monitor and re-queue failed events.

Mission Critical
Yes. Will help to quickly turn around failed events.

Benefits
Reduces time on writing scripts for failed events.

Users
Yes.

Completed - Release 2021.1.2 - 19 March 2021

Description
Organizations within DISA are re-organizing and assets are required to be transferred to the appropriate UIC/Custodian Account using Asset Management transfer. We would like the option to transfer sub-custodian user hand-receipts along with sub-accounts. Parent child relationship.

Recommended
Request Property Custodian (PC) the capabilities to transfer all sub custodian number hand receipts when these assets are transferred to newly created hand receipt. This will eliminate the requirement for the PC to re-create new sub custodian hand receipts if remain the same.

Mission Critical
Adding this option is not mission critical or mandated, just makes it more efficient.

Benefits
This will reduce man-hours and cost due to rekeying information. The Property Custodian (PC) will be given the option to maintain same user hand receipt without re-creating new sub custodian hand receipts due to re-organization of directorate assets.

Users
Yes, this action affects all users within the Agency.

Description
DISA is requesting the Defense Property Accountability System (DPAS) Program Management Office (PMO) to modify the DPAS application to interoperate with other DISA and DOD systems that use location and other enumerations from the Cyber Operational Attribute Management System (COAMS).  Once modifications are made, DISA will be able to use data from DPAS to update other systems, and data from other systems to update DPAS eliminating both duplication of effort and inconsistent data between systems.

Recommended
Integrate DPAS with COAMS so that users can create new sub-organizations and sub-locations in COAMS via DPAS by using a DPAS-COAMS interface. Similar to the Real Property Identification interfacing located under the Master data/location. See attach COAMs Integration Levels.

Mission Critical
This action is critical to enhance DISAs asset location in support of audit.

Benefits
Enable external systems to query DPAS using a web service to recover owning organization and locations for IT Assets using the affected Fully Qualified Domain Name (FQDN) or Serial Number (SN).  It centralizes data and improves accuracy of asset location to minimize rekeying errors.

Users

Description
USMC is modernizing their Master Data Repository (MDR). They have a requirement for additional asset / history information from DPAS. Given that DPAS has commenced several initiatives relating to how assets will be managed, DPAS is not able to provide a "To Be" at this time.  For starters, USMC has agreed to accept the 5 Asset Extracts that DPAS currently has with a re look of what can be provided in the future should there be an additional requirement. 

Recommended
DPAS provide the 5 Asset Extract feeds for PA and Warehouse (exclude Real Property extracts as they will not contain any data) to USMC.  The files will be made available through DAAS GEX.  It is requested the file be created daily.

Mission Critical
This is mission critical as per guidance for USMC LDS program.

Benefits
Improves USMC asset visibility to accomplish the USMC mission.  Is a Std DPAS extract that is available that have access to DAAS GEX.

Users
This SCR will support the USMC.

Completed -- Release 2021.2 - 28 May 2021

Description
DLA is implementing DPAS for supplies that are managed by COCOs.  The COCOs could have materiel that is warehoused with more than 1 owner.  DLA needs a way to determine warehouse utilization by owner.  To be effective, customer must be diligent in accurately reporting the Unit Cube(ft) of the Unit Of Issue Qty.

Recommended
Add Cu Ft to the Stock Nbr inquiry, and/or develop a real-time report that depicts the following attributes:

• warehouse name,
• stock nbr,
• item desc,
• owning dodaac,
• total on hand qty for Stock Nbr/Owning DoDAAC,
• unit cube,
• sum(qty) x unit cube.

Mission Critical
This is considered essential for managing warehouse utilization.  While nothing is perfect due to how materiel must be stored in the warehouse efficiently and effectively, it does provide a measure of utilization within a warehouse.

Benefits
It provides the customer with a way of looking at Warehouse Utilization / Space Utilization and in determining a cost allocation of the warehouse operations for COCO operations.

Users
This change is considered beneficial for all customers / users of the Warehouse module.

Description
Currently when a user adds a new NSN record either by Catalog A/U/D or insert from conversion that does not exist on the DPAS Fedlog tables there is no current process to go to FLIS / FEDLOG to update the record with proper FLIS values or verify if indeed the stock number added is an NSN. I&S and other data may remain incomplete or wrong if user entered incorrectly.

Recommended
Create DPAS to webflis file feed that allows to request records from FLIS to be updated or inserted to DPAS Fedlog tables.  All 13 digit numbers catalog as B should be sent.  If FLIS finds a match and responds with data, data should be inserted to Fedlog tables.  Background process should then update Stock Number types of B to A then update to fedlog values including I&S data.  All 13 digit Stock Number types of A that do not have Fedlog records should be updated in the same fashion.  Additional step in the background process would be to retrieve I&S stock numbers not in DPAS Fedlog tables.  Records that have Parents or children with no Fedlog record should be processes with rules above or set in a holding table to request data from FLIS.  Alternative would be to use FEDLOG disks to do a monthly reconciliation if FLIS interface cannot facilitate requests for data.

Mission Critical
Yes currently many customers have incomplete data as well as records that are indeed NSNs that does not have current Fedlog data or wrong data.

Benefits
Customers have valid data from FLIS/DLA centralized source for NSNs.

Users
Yes all users are affected.  Tech Refresh is dependent to deliver better requisition and reporting capabilities future state.

Partially Completed - Release 2021.3 - 10 Sept 2021

Partially Completed – Release 2023.1.5 – 10 March 2023

Partially Completed – Release 2023.1.6 – 24 March 2023

Completed - Release 2023.1.6

Description
Provide DPAS functionality to allow the system to generate document numbers with an Alpha Character in the 11th position:

• DoDM 4160.21-V1, October 2, 2019 provides guidance to agencies to process turn-in documents in the DLA Disposition Services web-based Electronic Turn-in Document (ETID) System.  The ETID system generates the document number with alpha character “T” in the 11th position of the document number.
• DoDEA is required to use this system, to process 1348-1A in order for the DLA Disposition Services (DLA DS) contracted transportation to pick up turn-in property; per the guidance there is no way for DLA DS or DoDEA to track the property if the 1348-1A isn’t generated in their system.
• The DPAS system does not support document numbers with an Alpha Character in the 11th position.  This has become issue with DoDEA, turn-in documents due to inability to generate identical turn-in document numbers sequence in order to match the document numbers for transaction recondition for audit review/readiness, and the tracking of turn-in documents. DoDEA requires DPAS system to support incorporating the Alpha Character in the 11th position of the document number.

Recommended
Provide system functionality to auto generate or manually process document numbers with the ability to populate the 11th position with Alpha character. Consider inter-face with DPAS and DLA Disposition Services.

Mission Critical
This request is functionality mission critical for the tracking and reconciliation of turn-in documents number. The DoDM 4160.21-V1 guidance doesn't mandates agencies to use DLA Disposition Services web-based Electronic Turn-in Document (ETID) System to process/generate the 1348-1A document. DoDEA is using the ETID system because when contracted transportation pick up property, there is no way for DLA DS to track the property if is not in their system.

Benefits
The benefit of adding this feature will allow the user to track the transaction with identical data document numbers. It will provide accurate documentation, provide reconciliation/audit trail and allow the user to reduce the amount of time generating additional documents outside of DPAS to explain the circumstance of discrepancy between documents numbers for same transaction.

Users
Yes: This issue affects 100% of all DoDEA's property accountability functional users require to utilize the DLA Disposition Services for the disposal /turn-in process.

Description
The DPAS DLMS Outbound processor checks to see if the DLMS transaction is to be routed internally based upon the RIC or DoDAAC To.  When the RIC or DoDAAC To exists within DPAS, the DLMS transaction is move to the DLMS Inbound folder rather than being placed in the DLMS Outbound folder. With DLA planning to use the DPAS Warehouse module for the management of VA PPE, there is a requirement to feed Transportation Request transactions to VSM which will have the same RIC as the DPAS warehouse (same organization operating VSM and DPAS).

Recommended
Modify the DPAS DLMS Outbound processor to check outbound generated DLMS 940R transactions for a Distribution Code (Industry Code = AK) of '111'.  When true, place transaction in the DLMS Outbound folder for DAAS to pickup.

Mission Critical
Yes.  Without this change, DPAS is unable to route Transportation Request transactions (DLMS 940Rs) to the transportation system when they utilize a RIC that exists within DPAS. This SCR is being submitted in support of the DLA VA PPE project.

Benefits
Enables transaction to be electronically sent to a Transportation Management System.  Without this change, it is not possible when the systems share the same RIC.

Users
This change will only impact customers of the Warehouse module that also operation a separate transportation system that requires the use of the same RIC as the Warehouse. It will have no affect on any other customer.

Description
In order to ensure transactions interface from DPAS to DAI, MDA reconciles reports from both systems.  Currently, DPAS Interface System Initiated report is only available in PDF format and makes it extremely difficult to validate transactions.  The process requires extensive steps in Exporting the PDF to Excel and utilizing formulas to attain necessary information. This is a timely process since Exporting PDF to MS Excel does not convert the same way each time.  Currently, it takes at least 4 man-hours to reconcile transactions between both systems; therefore, currently MDA only reconciles once a month.

Recommended
Converting the report from PDF to Excel will minimize the man-hours required to reconcile the DAI Accounting Interface Report and allow the users to perform the report on a more frequent basis.

Mission Critical
No: This action will allow for a more efficient work flow and minimize the man-hours required to reconcile the report. 

Benefits
All agencies that utilize the DPAS and DAI will benefit from the Excel format.  On average it will save at least 3 man-hours each time personnel reconciles reports between DAI and DPAS.   Additionally, reconciliation can be conducted on a more frequent basis (daily or weekly); therefore, any issues between DAI and DPAS will be identified in a timelier basis.

Users
This will affect the Accounting/Financial users of DPAS.

Description
When a production issue occurs with a suspended DLMS transaction, users with the DPAS Admin role are able to see such suspensions but lacks the ability to reprocess one. When conditions are corrected for a previously suspended DLMS transaction to process successfully, it is beneficial for the user with this role to be able to initiate the reprocessing of the transaction. This function is only available to Standard Users at this time, though few understand when and how to use it. In most cases, a DPAS Admin has to contact a user and ask them to go and reprocess a transaction(s) that are suspended. In some cases this has caused issues where the user chooses the wrong transaction to reprocess.

Recommended
Grant access to the DPAS Admin role(s) to enable the reprocessing of DLMS transactions that are suspended within the DLMS Transaction Review page of the ICP module.

Mission Critical
No, as Standard Users are able to perform this function today, the request would not be considered mission critical. This change will enhance Leidos' ability to provide quality support to it's customer base within DPAS.

Benefits
This reduces time for Leidos to resolve Production Issues and improves on the accuracy of those resolutions by removing the "middle man" who could cause further issues.

Users
This should only affect users with a DPAS Admin role within DPAS.