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.

Completed – Release 2021.1.4 – 30 April 2021

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. 

Partially Completed – Release 2021.1 – 5 February 2021

Partially Completed – Release 2021.2.1 – 11 June 2021

Completed – Release 2021.2.2 – 02 July 2021

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

Completed – Release 2021.1 – 5 February 2021

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.

Completed - Proof of Principle

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.

Partially Completed – Release 2021.2.1 – 11 June 2021

Completed - Release 2021.2.1

Description
Provide single point, end user capability for managing/scheduling jobs as well as to receive critical production feedback on issues for analysis and resolution.

Recommended
The initial focus will be operations based – triage, research, issue identification and resolution.  Additional functionality will be submitted for monitoring and possible trend analysis in the form of a configurable dashboard.

Mission Critical
This was mandated as a requirement of Tech Refresh.

Benefits

• improved production support capability
• improved visibility to system and application status
• improved research, triage and error identification tools

Users
Prod Support Team

Partially Completed – Release 2022.3 – 04 November 2022

Partially Completed - Release 2022.3.1

Partially Completed - Release 2023.1.2

Partially Completed - Release 2023.1.3

Partially Completed - Release 2023.1.6

Partially Completed - Release 2023.2.3

Completed - Release 2023.2.7

Description
Establish a DPAS common asset model to support the DPAS Tech refresh work effort.

Recommended
DPAS will provide a centralized asset structure that is accessible to all DPAS processes and platforms.
This structure will contain a core set of attributes that are common to all DoD business processes. 
Process specific attributes will extended off of the Common Asset structure in a "hub and spoke" model.
The Common Asset structure will provide an enterprise wide method to uniquely identify each asset in DPAS and share those common attributes throughout the system.
Microservice API(s) will be established, use-able by all development teams to insert assets into the new asset structure. 
This SCR requires that the Common Asset structure support both the new model and the existing, disparate asset models in DPAS today.
The Common Asset structure should maintain an in-sync balance between old and new models until all processes have transitioned to the new Common Asset structure.
Reports and monitoring will be provided to monitor/ensure balance between the asset model and the legacy DPAS application as organizations/DPAS transitions to the tech refresh framework.

Mission Critical
This was mandated as a requirement of Tech Refresh.

Benefits
The separation of the common asset attributes and the extension tables by specific platform provides a more efficient application design which limits risk by isolating changes to the asset model to specific platforms and its related asset attributes. 
Provides full visibility of the full life cycle of the asset, regardless of activity or platform.

Users
All