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.

Description
Requesting that three additional data elements be fed to the Master Data Repository (MDR).
We would like the Catalog Inquiry, the Document Inquiry, and the DLMS Inquiry data be sent to the MDR. Ideally, all available columns from the Inquiry pages would be sent to the MDR.

Recommended
Adding these inquiries to the daily MDR feed.

Mission Critical
Yes, Adding these three inquiries would increase visibility of data to auditors. This would also create a historical archive of our catalogs which would assist in system analysis.

Benefits
Improves data reporting and accountability.

Users
All users in our agency who use the MDR on a daily basis.

Description
Secondary Repairable Managers submit documents for repair or return assets to MCLB Albany for adjudication. They also request a replacement asset on the SAME DOCUMENT NUMBER to be returned to them. If the A5 document is worked in DPAS before the assets are picked up in Albany, it causes the receipt document to be PENDING until the A5 documents are shipped.  Once the shipping documents are processed completely, the receipt document can then be processed.
This is causing a backlog of documents to be processed and assets waiting to be adjudicated.

Recommended
Ability for DPAS to have same document for receipt and issue without being associated to each other.  Remove association between A5 and DW for same document number. 

Mission Critical
Mission Critical as it is delaying Secondary Repairable Operations. 

Benefits
Reduces document back up and assets are able to be stored.

Users
All users.

Description
Unit/Individual Reconciliation (Inventory Issued Assets): Posting the Platoon inventory is ALL or NONE. There should be an option to post a single or multiple serial number(s) and to “not post” any asset that is not accounted for (suspected missing or lost and being searched).

Recommended
Unit/Individual Reconciliation (Inventory Issued Assets): Posting the Platoon inventory is ALL or NONE. There should be an option to post a single or multiple serial number(s) and to “not post” any asset that is not accounted for (suspected missing or lost and being searched).

Mission Critical
Yes. Cannot complete/reconcile Platoon inventory if any item is unaccounted for or in suspected loss/under investigation status.

Benefits
Improves accuracy of issued items.

Users
Yes.

Description
DPAS maintains master listings of DoD DoDAACs and RICs within the DPAS FED_LOG database.  DPAS receives a daily DoDDAAC file via DAAS GEX that provides new and updates to existing DoDAACs. DPAS processes the file and updates the DoDAAC Master table. The RIC Master table is not systematically updated.  Today, the DPAS team must take action to update it periodically, thus the RIC Master table is not as current as it could be which can result in processing / validation delays.

Recommended
It has been determined that the RIC data is also included in the daily DODAAC file that is received via DAAS GEX.  RICs are identified within the file as a DODAAC that begin with 'ZZZ'.   For example, a record with a DoDAAC value of 'ZZZA4J' contains the data for RIC 'A4J'.  DPAS needs to develop a process to extract the RIC data from the daily DODDAAC file received via DAAS GEX, and update the RIC Master table.

Mission Critical
Mission Critical, Newly added ICPs are not able to transmit DLMS transactions through DAAS to external trading partners because a it does not pass the RIC validation until DPAS manually updates the RIC Master table with the RIC data.

Benefits
Reduces time and effort/cost  for DPAS (Analyst/DBA analysis) and for the trading Partner (business interruption/analysis).

Users
Newly added ICPs cannot be used until Support updates the RIC Master table with the new RIC(s).  DLMS 527Ds (PMRs/Due In) records are send RIC to RIC.  These transactions require the RIC Master table to be current in order to allow processing to occur.  As more users implement these features, it is imperative that RIC Master table is current.

Description
Army has a requirement for Asset data for Army owned assets managed using the DoD's  Defense Property Accountability System "DPAS" beyond the data currently provided by the UIT interface.  This data will be used to populate the Army Vantage program to expand Army Vantage's mission set for assets and serials information.

Recommended
DPAS provide the Asset Extract feed for PA and Warehouse with the exception of the Real Property extracts.  The files will be made available through DAAS GEX.  It is requested the file be created daily.

Mission Critical
Mission Critical as per guidance for Army Vantage program

Benefits
Improves Army Vantage's ability to accomplish the mission

Users
All

Description
Property Administrators are required to attach documentation to each transaction within DPAS. At this time, they are unable to attach supporting documentation when performing transfers.

Recommended
Add the ability to upload attachments to affected asset records which are a part of transfer transactions.

Mission Critical
Yes. Per FIAR/FAR guidance, key supporting documents must be attached to each transaction within the APSR.

Benefits
This change would allow for better tracking of accountability, in that the associated documentation would be directly attached to the transfer transaction.

Users
Yes

Description
The DPAS Individual Issue process does not currently support issue by pRFID number. pRFID numbers are unique. By scanning the pRFID that is related to inventory, the issue can be made efficiently and accurately. The DPAS PM has requested that DPAS be able to provide a proof of principle (POP) to the U.S Coast Guard for their cadet clothing issues.

Recommended
The POP will consist primarily of bulk clothing, which could be hundreds/thousands of identical items being received. To support this POP, 1) DPAS will need a method to efficiently capture and associate the pRFIDs with the inventory during the receiving phase, or possibly have a separate pRFID process that could augment receiving, and 2) the goal would be to modify the existing Individual Issue process to enable the scan/capture of the pRFIDs that are attached to the items being issue displaying the Stock Nbr / Qty in the issue process. For the POP, it is not necessary to have DPAS create a process to assign pRFIDs to bulk materiel, or to implement pRFID into the Individual Return process. These modifications would only be needed should issue by pRFID become a core DPAS process.

Mission Critical
This is a DPAS PM requirement.

Benefits
Reduced manpower through automated scans, and improve accuracy

Users
All users who perform Individual Issues and have items tagged with a pRFID

Description
There is a need to catalog local stock numbers outside of the standard NSN, MCN and part number formats.

Recommended
This involves creating a new stock item type code of 'L - LSN' and updating the catalog interface to allow the entry of the stock number - max length 15 characters with the validation:  alphanumeric with supported special characters $, -, /, \#, &, ;, (, ), comma, period, and space.  Impact to DLMS transaction processing will be minimized and addressed.

Mission Critical
mission critical

Benefits
Allows DPAS to support individual agency's cataloging policy requirements

Users
all users

Completed – Release 2020.3.3 – 4 December 2020

Description
SAF/FM is constraining the CICP go-live dates in DPAS to the first day of a new quarter.  This places pressure on the CICPs, the GFM-A team and the DPAS implementation team into these four days each year.  In consultation with our DPAS support team, we have proposed establishing a transaction pilot period for each new ICP before DPAS enables the financial reporting to GAFS-R.  Currently, the DPAS reporting lever to GAFS-R is located at the Logistics Program level.  We propose lowering that reporting lever to the ICP level in DPAS.  This will enable us to implement new CICPs on any date without impacting financial reporting.  In addition, the GFM-A team needs the ability to change the beginning and ending dates on the reports in the ICP module (CFO Report, OM&S Trial Balance and Accounting Detail Report) to allow users to pull historical data including transactions for audits.

Recommended
The recommended solution is to move the GAFS-R reporting level in the ICP module from the Logistics Program level to the ICP level. ICP Officers within DPAS should be provided an interface that would allow them to turn the GAFS-R Reporting on or off for each ICP under their Logistics Program.  Remove the block from the beginning dates and ending dates from the financial reports in the ICP Module.

Mission Critical
This is critical to the implementation of the 100 AF CICPs; this removes constraints on all teams supporting the CICP implementations in DPAS.  Allows programs to provide transaction sets to auditors.

Benefits
This provides the ability to review CICP transactions for accuracy prior to sending financial data to GAFS-R.  It further provides the opportunity to correct any errors in the transactions.  Provides ability to provide transaction sets for reconciliation and audits.

Users
ALL AF GFM-A users

Description
DLA is implementing DPAS Warehouse module to support receipt, storage, and issue of the Veterans Administration's PPE.
Currently there is no electronic communication of Requisitions / MROs. 
DLA does have a requirement to route the MRO to a TMO to have the materiel shipped (DLMS ADC 316 Functionality). 
It appears that the ADC 316 functionality within DPAS only works with external ICPs. 
The ADC 316 functionality is between the TMO and Warehouse and should not be dependent upon an ICP being associated to the Warehouse / Owning DoDAAC. 
There also appears to be an issue with the printing of Special Instructions. 
The allowable characters are insufficient, and it appears they only print when the continuation page is printed which is only printed when the MRO is for serialized assets and the Qty > 1. 
Special Instructions should print for all MROs when entered.
The TMO DLMS 945A needs to be reviewed to determine if all of the data is being extracted related to the shipment. 
This information needs to be extracted and included in the DLMS 945A to the ICP and 856S to the customer.

Recommended

1.   Review current ADC316 TMO functionality to ensure it functions with all MROs that contain a valid TMO RIC / Transportation Account Code (TAC).
2.   Validate what fields are required to generate a 940R to a TMO.  Add BRs for fields that are currently not marked as required when a TMO is present to make them required.
3. Increase the number of allowed characters for special instructions, and ensure they print when present (either add to main 1348 to the right of block 27, or always print the continuation page when special instructions are present). DLA desires the capability for 4 lines with each line having 25 characters.
4. Review the inbound DLMS 945A to ensure DPAS is extracting all of the shipping elements and including them in the DLMS 945A to the ICP as well as the 856S.

Mission Critical
Yes. Without this change, DLA will need to delay the implementation of DPAS for managing the Veterans Administration PPE.  Estimated Required Delivery date of this functionality is 12/1/2020.

Benefits
Accurate accounting and reporting for materiel is mandatory.

Users
These changes will improve Warehouse for all users who use this functionality. 

Description
USAFA contacted DPAS to seek improvements in the Individual Issue process.  Overall, they are very pleased with what DPAS has provided, but when they have fielding day, they struggle to be able to service all of the cadets in a single day.  That perspective alone, they have identified several items that if DPAS were modified, they believe they would be able to service the cadets.

Recommended

1. Display of Member Profile data at the commencement of the issue.  They are not currently using MILs and believe if they could bypass this step, they could achieve more throughput
   •  Add to the Warehouse AUD a check box (bit_flg) to indicate whether to display the Member Profile upon entering the II process.
   •  Modify Individual Issue to read display switch and act accordingly.
2. Scanning of Bar Codes should increment Qtys.  This would streamline the issue.
   •  Improve the scan feature to support Qty updates.  Either scan will increase Qty or a Scan of a bulk asset will pop up a Qty box for the user to input the qty.
3. Manual Sign - When the issue is complete, DPAS displays the quick print window.  They do not print a completed from.  They want this not to display to streamline the process and increase the throughput.
   •  Add to the Warehouse AUD a check box (bit_flg) to indicate whether to display the print window. Need to determine at what phase they want to stop the sign/print step. May require more than 1 check box or a drop down of options.
   • Modify Individual Issue to read display switch and act accordingly.
4. Once they complete an issue and want to start the next issue, they indicated they must select the Back Arrow.  They are looking for a faster / easier to start the next Issue.
   •  Add a "New" Button to Screen to return the user to page 1 of the issue process to start the selection of the next member.
 

Mission Critical
Critical:  USAFA must process individual  issues to 1000 incoming cadets in a single day.

Benefits
Reduces the Time/Cost of large scale Individual Issues.

Users
All WH users could benefit from the streamlining of the individual issue process outlined above.

Description
USMC LOGCOM is transitioning from the Air Force Stock Control System (SCS) to Navy Enterprise Resource Planning System (NERP) for inventory management of the wholesale inventory that is managed within DPAS warehouses.  Communication between NERP and DPAS will be DLMS transactions.  With the change in inventory control system, NERP requires the Warehouse system to generate a DLMS 867I (Issue) as part of the Materiel Release Advice shipment report (DLMS 945A).

Recommended

1. Incorporate a flg within the Owning DoDAAC profile to indicate whether the system needs to generate a Issue (867I).
2. Modify LPWNH35 (MRO) to generate a DLMS 867I when flg is true for the Owning DoDAAC.
3. Incorporate business rules provided by NERP/USMC to determine the Product Transfer Type Code (To be provided later).
4. Consideration should be given to adding a flg for the generation of the DLMS 856S transaction as this is currently dedicated to SCS. 
   NERP will likely require DPAS to generate the DLMS 856S along with other systems as it is not configured to account for materiel at the serial nbr/batch level.
5. Modify LPWHN35 to check for 856S flg.  When present, generate the Shipment Status (DLMS 856S); otherwise, do not generate the Shipment Status.

Mission Critical
Yes. Without this change, USMC cannot transition to NERP.

Benefits
Provides USMC with a modern Materiel Mgmt system and enable USMC to become compliant with Navy policy

Users
The impact to the user is negligible as this will be limited to background processing with the exception of the setup of the Owning DoDAAC's profile. 

Description
While conducting a annual review the ASA(ALT) DPAS established customized roles, we realized that some roles need more allocations to perform their functions and daily operations. ASA(ALT) proposes giving certain DPAS positions more capabilities by requesting a change to provide them with more control over their process in DPAS.

Recommended
Requesting to modify current ASA ALT DPAS Warehouse user role functionalities to support DPAS work functions.  Attached is the functionality change modification request, highlighted in yellow, and place the functionalities needed in the block. Also attached is the current ASA ALT DPAS Warehouse roles description and functionalities.

Mission Critical
This role improvement will give the users more accessibility to their assets in their prescriptive roles in DPAS aligned to Army internal controls and audit readiness.

Benefits
These changes will give the user more functionality in their roles in DPAS. These changes will help them complete their process promptly. It will also provide the users with the capability to complete every function needed without reaching to higher commands to run any functionality.

Users
Yes it will affect all users within ASA(ALT).

Description
While conducting a annual review the ASA(ALT) DPAS established customized roles, we realized that some roles need more allocations to perform their functions and daily operations. ASA(ALT) proposes giving certain DPAS positions more capabilities by requesting a change to provide them with more control over their process in DPAS.

Recommended
Requesting to modify current ASA ALT DPAS ICP user role functionalities to support DPAS work functions.  Attached is the functionality change modification request, highlighted in yellow, and place the functionalities needed in the block. Also attached is the current ASA ALT DPAS ICP roles description and functionalities.

Mission Critical
This role improvement will give the users more accessibility to their assets in their prescriptive roles in DPAS aligned to Army internal controls and audit readiness.

Benefits
These changes will give the user more functionality in their roles in DPAS. These changes will help them complete their process promptly. It will also provide the users with the capability to complete every function needed without reaching to higher commands to run any functionality.

Users
Yes it will affect all users within ASA(ALT).

Description
Right now to make the Help page sensitive, there needs to be a link between each page of the DPAS application and the matching Help Topic. To accomplish this, the Technical Writer and developers must create those links within the DPAS application.

Recommended
Create a page where a non-programmer (such as the Technical Writer) can enter the unique Help IDs and have them automatically link to the correct DPAS application pages. (If a identifier is necessary for the DPAS page, make it something like the CI or something easily found.)

Mission Critical
It is necessary for the help to be linked properly to the DPAS application in a timely manner.

Benefits
Reduces time, improves effectiveness.

Users
Technical Writers, All Developers within DPAS.

Description
Need to lock down the ability to group name; attribute name and type under the members Attributes under member profile. This should only be able to edited by Warehouse officer. Currently Warehouse technician can edit and add new.

Recommended
Under Member Profile, under Member Attributes lock down ability to add any new group names or attribute names.

Mission Critical
YES! Warehouse technicians are adding all types of information, spelling wrong, wrong kind of sizes, so when we run reports we have all kinds of misinformation for sizes.

Benefits
data accuracy.

Users
All

Description
The DPAS Individual Issue process does not currently support issue by pRFID number.  pRFID numbers are unique.  By scanning the pRFID that is related to inventory, the issue can be made efficiently and accurately.  The DPAS PM has requested that DPAS be able to provide a proof of principle (POP) to the U.S Coast Guard for their cadet clothing issues.

Recommended
The POP will consist primarily of bulk clothing, which could be hundreds/thousands of identical items being received. To support this POP:

• DPAS will need a method to efficiently capture and associate the pRFIDs with the inventory during the receiving phase, or possibly have a separate pRFID process that could augment receiving.
• the goal would be to modify the existing Individual Issue process to enable the scan/capture of the pRFIDs that are attached to the items being issue displaying the Stock Nbr / Qty in the issue process.

For the POP, it is not necessary to have DPAS create a process to assign pRFIDs to bulk materiel, or to implement pRFID into the Individual Return process. These modifications would only be needed should issue by pRFID become a core DPAS process.

Mission Critical
This is a DPAS PM requirement.

Benefits
Reduced manpower through automated scans, and improve accuracy.

Users
All users who perform Individual Issues and have items tagged with a pRFID.

Description
The initial fielding of the DPAS warehouse module included Planned Picking on a HHT.  With the sunset of the original HHTs, there is a requirement to reconstitute the Planned Pick process in a disconnected mode that functions with the currently supported DPAS AIT.

Recommended
Provide the capability to view, pick and deliver planned picks via an AIT terminal that is compatible with DPAS. The solution will be able to export planned picks for disconnected operation, and be able to import them when the terminal is reconnected.  All of the business processes related to confirming the pick is to be completed by this SCR to include updating the MRO to Picked/Ready for Release and generate a QC action when applicable.  When operating connected, the process should receive new picks and post completed picks real-time.

Mission Critical
Yes.  Reconstitution of existing functionality for use with currently approved AIT devices.

Benefits
Reduced manpower through automated scans, and improve accuracy.

Users
All users who utilize the planned pick process.