The MRO Process in the WM is not very user friendly. The functionality of the process has not been improved since the original design of this functionality. There are many mandatory steps to get through the process that are not a requirement for the business, to include the Material Movement Plan and Pick Process. There is also no means to allow entire containers to be shipped.
This process is very antiquated and is very rarely used when another process will suffice in getting the gear issued (i.e. Warehouse Transfer or Warehouse Issue)

 

The MRO Process in the WM is not very user friendly. The functionality of the process has not been improved since the original design of this functionality. There are many mandatory steps to get through the process that are not a requirement for the business, to include the Material Movement Plan and Pick Process. There is also no means to allow entire containers to be shipped.
This process is very antiquated and is very rarely used when another process will suffice in getting the gear issued (i.e. Warehouse Transfer or Warehouse Issue)

 

 

Would improve the entire process of issuing gear to include reducing time required to issue gear, improved accuracy by using the process vice alternate processes.

 

Frequency: Daily

 

Currently there is no "one" way to pull up a complete ICN Inventory or Inventory Activity  with all required data.    Currently have to use multiple reports and inquiries to obtain all contract required data and then blend it into one report.  Items not easily found are MFR Part # (ICN and Activity), Issue DODDAC (Activity).  Inquiries also allows to research multiple days of activity  were the Pre-canned reports only allows for a single day which require multiple reports and then have to compile the reports together.  Additionally, all MFR Part # and Model # is created for each Stock Number.  However there is NO inquiry or report that provides this data in relation to the warehouses activities.  Part # or Model # has to be hand typed into every report to show all data related to the activity. IF DPAS Stores this data, and WebFLIS, can provide this data or it is typed in by the user, why can't we use it for reports and inquiries?  Same applies to the Issuing DODAC.  Its part of the "activity" it should be selectable, not just the Owning DODDAC, which is already known as it is the warehouse creating the report

 

At a minimum the following data should be made available (selectable, not default) to the ICN Inventory or Inventory Activity inquiries:
DODDAC Address 1 (Activity)

 

NAVSEA Contract N00024-22-C-5231
SECNAVINST 5200.44

 

Elimination of excess labor costs.
reduction of possible errors in reporting due to merging of data

 

Frequency: Daily

Est user: Unk (DPAS Wide).  within our DODDAC(s) - 12

Users are not able to remove a cost or no cost component asset to become an end item

 

Enable a end user to covert a cost or no cost component back to a end item without Leidos intervention for both active assets and assets that have been archived.

 

 

 

This will allow users to remove a cost or no cost component and add it to the inventory as an end item without requiring to submit a help ticket to Leidos.

 

Frequency: Daily

 

when conducting a warehouse issue DD 1348 is required by NSW for record ,  only option avaliable is to print DD1149

 

Add ability to print a DD 1348 during the warehouse issue process, the following fields must be filled
Doc number, NSN, RIC,

 

 

 

This will allow users to print a DD 1348 in accordance with NSW guidance

 

Frequency: Daily

 

DEDSO is replacing the Distribution Code 111 functionality (Transportation Only Services ADC 316 functionality ) with specific qualifiers within the DLMS 940R and DLMS 945A transaction sets.  DPAS must implement this change to enable transportation requests / responses to be made systematically with DLA's Warehouse Management System (WMS), and Air Force's Cargo Movement Operations System (CMOS).  The ADC states this change will be implmented within 180 days of ADC issuance 12/22/2023.

 

Modify the DLMS Viewers and DLMS inbound/outbound processes to support the new transportation request qualifiers.

 

This change must be implemented to ensure communications with DoD's Transportation Management systems remains active.

Failure to implement this change in a timely manner will result in shipping requests  / status updates to be performed manually.

Frequency: Daily

 

When running an issued inventory the DW20 form does not show the issued by warehouse while the issued inventory screen does.

 

Add a issued warehouse field on the DW20 form.

 

 

 

This will allow users conducting inventories to to see which items they have issued and are responsible for inventorying. Currently to see which items they are responsible for users must print the DW20 form and compare the issued inventory screen results to the DW20 to see the what items they are responsible to inventory.

Frequency: Daily

 

DPAS controls display and edits of key accounting fields based upon the accounting interface system that is to receive the data.  The display/edits business rules are developed in concert with the accounting system and are documented in the interface control document.  Today, DAI is not receiving the Trading Partner Department Cd, Trading Partner Basic Symbol or the Trading Partner Subhead which MDA, and agency supported by DAI states are mandatory fields to feed DFAS's DDRS (Defense Departmental Reporting System).   As a result, they must gather this data for each transferred/disposed asset, correct their DDRS submission errors manually.

DAI and DPAS are modifying the Interface Control Document interface strategy documents to state these fields are required. This SCR is to document the change to the DPAS system.

 

DDRS / Standard Financial Information Structure (SFIS) reporting rules require these fields to be included in the DDRS submission.

 

Eliminates errors in the agency's report submission to DRRS which requires the agency to collect the data and manually update the submission when the data can be collected systematically as part of the transfers / disposition of the asset.  

 

Frequency: Daily

 

 

When updating the Loan Code from 'G' to 'C', the Asset Status Code automatically reverts from 'T' to 'O'.  GFP assets have an Asset Status Code of 'T' - Out on Loan.  If the loaning address is WAWF enabled or if it contain a DoDAAC within DPAS, it always updates the Asset Status Cd to 'O' - Outbound in Transit.  

 

Recommend  the Asset Status Code automatic update function to change for GFP.

 

 

This action will allow for a more efficient work flow and minimize the redundancy in correcting the Asset Status Code of all GFP asset updates.

Frequency: Daily

 

OSD has changed how it supports information requests for Small Arms / Light Weapons (SAs/LWs).  Currently DoD requires components to report their SAs/LWs to a DoD service registry with that data being forwarded to the designated sponsoring service (Army) to create a DoD Registry.  When requests for information is received, the Army queries the registry for info, then responds to the request.  From an OSD perspective, this is the sole purpose of the SA/LW registries.  In 2022, they directed the Army to eliminate the SA/LW registries and to treat SAs/LWs just like any other supply item - i.e.  use logistics transactions to respond to the information requests.  As a result, the Army has developed Application Program Interfaces (APIs) referred to as "Locate Last Accountable Serialized Item Entry" (LLASIE).  Its design does not limit the requests for information to SAs/LWs.  The design provides for finding any item within the Department.  

 

An Army LDAC representative will input criteria into LLASIE.  LLASIE will contain a master list of Accountable Property Systems of Record (APSRs) which will be used to direct the request for information via an API.  When the APSR receives the request for information, it will interrogate its data using the criteria provided by LLASIE to prepare a response. When the data has been gathered, the APSR will transmit a response to LLASIE via an API.  The info that LLASIE may request may reside within DPAS's Property Accountability and Warehouse Management applications.   DPAS will need to create a repository that is capable of storing the  request and the response.   The system should be designed in a way that these requests/responses will be auto removed after x period of time (system level variable).  Visibility of the requests / responses should be made available to the DPAS User via a DPAS Role.  A separate SCR will be developed to remove the DPAS Registry application should it be determined that there is no reuse of it. Feeding data to / from the Registry application may cease when the Army has approved the DPAS implementation / fielding of this SCR and endorsed by the DPAS PM.  

OSD eliminated the DLMS SA/LW transactions sets / reporting, and replaced the SA/LW registries with LLASIE.

 

This changes eliminates the requirement for a SA/LW registry and implements DLMS change ADC 1244 and it amendments.

 

Frequency: Weekly

 

 

Problem: The current state of DPAS M&U lacks the ability to effectively retrieve attachments for audit purposes, such as dispatch/vehicle logs, receipts, and maintenance records for vehicles. This function doesn't allow the agency to pull desired attachments that are attached within the M&U module for inspection or investigative purposes. The correction of this defect will ensure agencies are able to store documents for audit purposes and allow agencies to comply with the National Archives and Records Administration (NARA) requirements.

 

Solution is to implement the attachment process that's currently utilized by the PA module. Attachments are allowed to be added in the M&U module, but you're not able to see all attachments for the asset. Currently, each dispatch has to be referenced to view or retrieve all attachments relating to the asset.

 

General Records Schedule (GRS) 5-4-010 or File 207 (DAA-0064-2015-0003 item 1); GRS 5-4-110

 

Compliance with General Records Schedule (GRS) and National Archive Records Administration (NARA) requirements. General Records Schedules (GRS) are schedules issued by the Archivist of the United States that authorize, after specified periods of time, the destruction of temporary records or the transfer to the National Archives of the United States of permanent records that are common to several or all agencies.

 

Frequency: Daily