Description
Within the CSP Enterprise is is a common occurrence to send degraded/obsolete serialized items to DRMO. In the system today, this shipment of serialized items must be conducted one at a time. The process takes approximately 5 seconds per serial number to complete.

Recommended
It is requested that DPAS be updated to select all material within a container (serialized or otherwise) and quick and easy processing during a Disposition Transaction. This is separate from the Containerized Shipment request for MRO, Issue, and Receiving Processes but is equally important. These processes must all be updated to allow for a container with serialized equipment to be selected for a particular shipment, and when that container is selected that all equipment in the containership and are removed/transferred from the system.

Mission Critical
This is a mission critical requirement to facilitate the ease of movement/disposition of assets across the CSP Enterprise.

Benefits
This change will result in a significant time savings when personnel are conducting serialized actions in DPAS.

Users
Yes, this change make the process easier and more time efficient for all users of the DPAS-WM.

Completed - Release 3.0 - 15 May 2015

Description
While implementing the DPAS-WM at the NCR we observed on many occasions where a member decided that the sizing on the item they were issued was wrong and they returned to the WH to exchange the item that they were issued. Within the DPAS-WM as it is currently designed, an exchange is a very time consuming process that involves going through the member entire list, returning the item being exchanged and then a subsequent issue of the new size. There is simply too much time and labor involved in the process.

Recommended
We need the capability to exchange equipment in the system. Our vision behind this is that we will see the following options under the Individual and Unit menus of Material Management:

Individual:

• Issue
• Exchange
• Temp Loan
• Return

Unit:

• Issue
• Approve
• Exchange
• Return

It should be set so that there is an exchange tab on the individual issue options. When exchange is selected, the member’s current issued equipment should display on the screen. The clerk must then be able to select the item(s) being exchanged, and then swap either change the size or NSN of the item the exchange is being requested for. When an item is exchanged, the system should pull the exchanged item from the individual issue location, and return the returned item to the appropriate return location. For items that are exchanged for the same like item (due to damage or something along those lines, the clerk must be able to input the reason for the exchange.

Mission Critical
This is a Mission Critical Requirement due to the time consuming nature of the exchange process as it is currently designed. Not having the ability to rapidly exchange equipment impacts around 10% of the business at the NCR.

Benefits
The benefit of updating this process will be a method for the DPAS-WM to record exchanged equipment and time savings at the counter.

Users
This will impact all DPAS-WM Unit and Individual Issue Process users.

Completed - Release 3.0 - 15 May 2015

Description
During operations within the NCR there are numerous metrics requested out from the CSP PMO that come from the issue/return activity report (how many issues per week, how many returns per week, number of items issued, etc…). To get that data today, the NCR area manager is forced to log in to each of her warehouses to create a consolidated report. Because we have to go through each WH, and pull the data separately creates the possibility for errors in the report.

Recommended
It is requested that the DPAS-WM be updated to include enterprise roll-up capability for the issue return activity in the DPAS-WM.

Mission Critical
Due to the high frequency requirement for the NCR Area manager to provide details about her operations, this requirement is mission critical for implementation at Beaufort, SC and rollout to Camp Lejeuene.

Benefits

Users

Completed - Release 3.0 - 15 May 2015

Description
In production we discovered the requirement for the system to be able to disassembly material into it’s piece part components. The Disassembly process should work as follows:
For serviceable condition codes – Disassembly all parts on the SKO into the location the disassembly is selected for. If all components are consumed, the main item should be issued to assembly, and the parts should be received from assembly per DLMS policy.
For unserviceable components – Disassembly should allow the clerk to select the condition code for each component, to ensure the serviceable and unserviceable items can be separated.
For incomplete items – The disassembly should allow the clerk to choose the quantity of SKO headers to disassembly, and then should default to the total quantity of components for the quantity of headers being disassembled with the ability to then change the quantity, condition code, and location of items being disassembled. Need the ability to disassemble certain components vice the whole kit if needed (EX, TBS IMTV has several components not issued). This material should be brought into stock not as a receipt, but as a disassembly. 100 removable belts, 100 side sapis holder, 100 inner cumber buns. Coupled with exclusion of kitted items at WH level." During the NCR Implementation we found that the CSP PMO does some interesting things with assemblies and disassembly's. At the NCR as items are moved through the enterprise, they are moved as whole kits. At the time an item is being prepped for issue from the system, the item is disassembled into it's piece part components for issue. Once issued, the item goes through it's lifecycle of being issued, used, and returned as a component, and not as a complete kit. Once the items are all received back from the customer, they are reassembled in stock, until they are put back on the issue line. What we get then, is a mix of assembled and disassembled kits that manifest in different ways in the system. Given that the CSP Enterprise does not consistently issue the same kits, we will need to likewise be able to issue components. To support the issuance of components in some sites (TBS, OCS, SOI, Etc.), we need to ability to dissemble whole items to their components to be issued in different configurations.

Recommended
The Disassembly process should work as follows:
For serviceable condition codes – Disassembly all parts on the SKO into the location the disassembly is selected for. If all components are consumed, the main item should be issued to assembly, and the parts should be received from assembly per DLMS policy.
For unserviceable components – Disassembly should allow the clerk to select the condition code for each component, to ensure the serviceable and unserviceable items can be separated.
For incomplete items – The disassembly should allow the clerk to choose the quantity of SKO headers to disassembly, and then should default to the total quantity of components for the quantity of headers being disassembled with the ability to then change the quantity, condition code, and location of items being disassembled. Need the ability to disassemble certain components vice the whole kit if needed (EX, TBS IMTV has several components not issued). This material should be brought into stock not as a receipt, but as a disassembly. 100 removable belts, 100 side sapis holder, 100 inner cumber buns. Coupled with exclusion of kitted items at WH level.

Mission Critical
This is an urgent requirement, because we are going to need to be able to conduct disassembly's in the system prior to going to Camp Lejeune, where the process will occur much more frequently than what we have at NCR.

Benefits
This will be a time saving benefit to fulfilling this requirement. If a disassembly capability is put in place, the user will simply need to select the NSN, Loc, and qty to disassemble and the system will do the rest. Otherwise, the user has to drop the NSN of the main Kit and then receipt or update (Inventory update manager) the NSN of the component items. Given a large kit, this can be quite time consuming.

Users
This change requirement will benefit all DPAS-WM users.

Description
When the manual sign is selected, it is requested that the system work with a signature pad to capture an image of the signature and record that signature on the issue receipt vice printing a unsigned form. The current signature pad used by LVI is the Topaz Systems Inc 1x5 pad Model Number T-S261-PLB-R. Exacerbated by the fact that many CSP Customers do not have access to the system. At the CSP NCR Pilot Implementation site it has been discovered that e-sign capability in the system is both inconsistent, and that USMC members do not always know their CAC PIN. Many of NCR Customers are new to the Marine Corps and have yet to establish and use DOD E-Mail accounts, let alone DOD computers. As a result, many students do not know their PIN's and Cannot e-sign.

Recommended
It is requested that the DPAS-WM be update to use an electronic signature pad for all manual sign transactions completed in DPAS. The signature pad used by LVI today is the Topaz Systems Inc 1x5 pad Model Number T-S261-PLB-R. Once a signature is captured in this manner it should electronically display on the members issue/return/temp loan/exchange/CMR Reconciliation forms for future audits.

Mission Critical
This is mission critical for a few reasons:

1. Due to e-sign and user issues with their PIN numbers, we need the ability to capture proof that a member signed for his gear in the system. This can be audited for future reconciliations as needed.
2. This capability is needed to reduce the time it takes to print, sign, and upload receipts to the system.

Benefits
The benefits of implementing the electronic signature pad are that, if e-sign capability is down, users can still sign with an auditable signature that will show up in the system. In addition, this will save us time and aid in record accuracy long term.

Users
This impacts all DPAS-WM users.

Completed - Release 3.0 - 15 May 2015

Description
The requirement exists for platoon sergeants, platoon commanders, and other sections to pull/view their Marines issue lists. It is requested that the member site to update to allow for anyone with a valid CAC to log In to the system, and to then be given a screen where they can select a member's EDIPI and last name.
Once the EDI PI and last name are selected the commander should be able to view the members Outstanding Returnable Issues, Temp Loans, and Unit Issues.

Recommended
It is recommended that the current member site be updated to allow anyone with a valid CAC to log In to the system, and to then be given a screen where they can select a member’s EDIPI and last name. Once a member is entered then that individual would be able to access any Outstanding Returnable Issues, Temp Loans, and Unit Issues.

Mission Critical
This is a critical function for the Fleet Marine Force. Commanders and Platoon Sergeants need visibility when it comes to their Marines and this includes the equipment issued to those individual Marines.

Benefits
Implementing this change request will benefit unit readiness and improve overall customer accountability.

Users
This change will affect all DPAS WS customers.

Completed - Release 3.2 - 06 January 2016

Description
We are in need of a temp loan capability under the individual menu as temp loans are given to individuals. Temp loans require MCS approval, and as such we need the ability to load an attachment to the Temp Loan once it is complete. The current system functionality only provides an individual issue or unit issue functionality, and there is no temp loan capability in the system.

Recommended
It is recommended that a temporary loan process be developed within the DPAS Warehouse module. The temp loan process should work the same as the individual issue process, but should record a due date that indicates when the loan should be returned. When the due date has expired, we need a report to notify the warehouse manager that the temp loan has expired. Additionally, the system should also send a notification to the individual the loan was given to that his loan has expired and he should return the items or request an extension. A temp loan return must also include the capability to quickly and efficiently handle serialized returns. If a temp loan is done for 300 gas masks (for example), then the loaning official needs to be able to quickly verify all parts and all serial number as we are requesting the unit issue process be able to do.

Mission Critical
Having a temporary loan function is a critical cog in the everyday business in the Fleet Marine Force. There are numerous instances where the Issue facility will do a temporary loan in lieu of other types of loans. Standard operating procedures dictate this but the core functionality must be built within the DPAS WS.

Benefits
Implementing this change will increase the Enterprise's response time to their customer's demand. There is a constant demand for temporary loans and without a temporary loan function then other non system procedures will be adopted and inventory posture could suffer.

Users
This will affect all users involved in individual and unit issues.

Description
The current design of the Unit Issue request is aimed at issuing gear for a Unit, but to a specific person.
The Unit Issue request show up on all outstanding returnable items lists throughout the system, and is recorded against the Primary Unit Custodian.
In addition, each unit can have secondary custodian's that draw gear on behalf of the unit but charged to the individual.
When a custodian is changed all equipment goes with that person, but the only way you can tell what equipment a Unit has issued against it is to go into the Issue Return Activity Report and to pull that unit up. That gear then gets mixed with the gear that is individually issued in the system.
The requirement exists in the Marine Corps for Unit Issued Equipment to be issued from the Unit Issue Facility and to be placed on a Consolidated Memorandum Receipt (CMR).
There is no such capability within the DPAS-WM. A CMR is based on the Unit and does not really care who the Primary (Responsible Officer)or Alternate Custodians (Delegated Person) are.
Once gear is issued, all equipment that is issued to a Unit should show up on the units CMR weather it is the primary or alternate custodian that signed for the issued equipment.

Recommended
It is requested that the DPAS-WM be updated to include Consolidated Memorandum Receipt (CMR) Functionality for Unit Issued Equipment. A CMR is based on the Unit and does not really care who the Primary (Responsible Officer) or Alternate Custodians (Delegated Person) are. Once gear is issued, all equipment that is issued to a unit should show up on the units CMR weather it is the primary or alternate custodian that signed for the issued equipment. Each custodian who draws gear must be associated with that UIC and will impact the quantity drawn by the Primary CMR. Unit issues should not be charged against that individual or show up on that individual issue or temp loan accounts. The Consolidated Memorandum Receipt is a requirements based document that shows all equipment that an UIC has been issued and should include the following categories:

1. Requirement – The sum total required items requested by the Responsible Officer
2. Authorized – The total authorized by the Approving Authority for the RO to draw
3. Issued – The total items issued to that RO
4. Shortages/Overages – The quantity of overage or shortage that RO has been issued for a particular TAMCN or NSN (if no TAMCN exists).
5. TAMCN
6. NSN
7. NOMEN
8. UI
9. UP
10. TP
11. UIC Name
12. Primary and Alternate Custodian Names and Contact Info.

The CMR, once created is a living breathing document that is driven off of a unit’s requirement. It must be able to be reconciled on a quarterly basis. The preference for quarterly reconciliation of a CMR, is for the RO to be able to verify his CMR via the member site using his CAC Card. In addition to member site verification, the RO must also be able to go into the unit issue facility and reconcile the CMR in person. On site signature of the CMR must be supported by both eSign and signature pad functionality. CMR’s must be reconciled once every quarter per MCO 4400.15 as follows:

• Jan – Mar
• Apr – June
• Jul – Sep
• Oct – Dec

At the beginning of each quarter, the RO should be notified via e-mail that his reconciliation is due NLT the last day of the quarter, and give directions on how to get to the recon screen.

The Unit Issue Clerk/WH Officer must be able to work the CMR. This means that he can and update/exchange the CMR quantities within a TAMCN Family to give the RO what he needs (ex. The RO has 50 sets of sz 12 boots, but needs 40 of another size. In addition, we need to be able to zero out a requirement and add items to the CMR within CMR Work Screen based on user role. (Perhaps clerks cannot update a CMR item to a different NSN (within the same TAMCN Family), but the site manager and WH Officer can).

Access to the Units Current CMR is what should come up in the unit CMR Menu when Unit CMR is selected. Below the current CMR should be a list of all issue and return receipts, as well as all reconciled CMR's for that unit. This is the audit trail/history of what happens with units CMR and should stay with the system for 6 years for financial auditability. The view capability should include the capability to print whichever item is selected. On the CMR Browse Screen there must be the ability to select a return receipt, issue receipt, exchange receipt, or CMR reconciliation form and print it for the RO if need be.

Mission Critical
Having a temporary loan function is a critical cog in the everyday business in the Fleet Marine Force. There are numerous instances where the Issue facility will do a temporary loan in lieu of other types of loans. Standard operating procedures dictate this but the core functionality must be built within the DPAS WS.

Benefits
This is a mission critical requirement for implementation at any USMC Unit Issue Facilities. The current process/design does not properly support the Unit Issue Process.

Users
This change will impact/benefit all users of the DPAS-WM Unit Issue Process.

Description
The return of serialized kits in the DPAS-WM is a painful process, often taking over 5-10 seconds per item that needs to be verified. This process needs to be updated to provide a verify all capability. Within the DPAS-WM, when a serialized item is being returned, the system does not have the capability to "verify all" parts coming across the counter. The important thing to remember here is that the verification of parts is simply in the system to work if exception exist and should not serve as the real check. The check is a site verification from experienced clerks. Given that, the clerks need a quick way to verify all parts during a receipt. Without the verify all capability we are often finding the clerks spending 5 seconds per item on the list to complete asset verification. For a Gas Mask, that is over 3 minutes verifying parts for one serialized item, not to mention is there are others. The main thing that is needed here is velocity. Transactions should be able to be processed quickly, rather than the tedious process that serialized parts verification is.

Recommended
It is requested that the verify all capability that is in place for bulk kits be made available to serialized items within the system as well. The verification is happening at the time of receipts via sight verification and action at the counter, and we do not need a tedious process to go through.

Mission Critical
This is a mission critical requirement because the return of serialized kits is unsustainable as it is currently designed. The example we have been seeing at the NCR are those Marines who have NBC gear. For those Marines, the verification of equipment is taking significantly longer than bulk only returns. The process is quite painful, and is even nastier on the Unit Issue side of the house.

Benefits
The benefit of developing this capability will be a time reduction in processing serialized kit returns.

Users
This impact will benefit all DPAS_WM users who issue//return serialized kits.

Completed - Release 3.0 - 15 May 2015