Description
We are in the need to the capability to Ghost (add in) data to the Issue List without issue the data.
The reason for this is that there are many situations where a member has been issued gear that is not in the system.
Across the CSP enterprise there are old lists that need to be added to a members issue list. ?This anomaly in the data significantly slows down the returns process.
In the case of a "Ghost In," the system should record a gain to the issue quantity against that warehouse, and not decrement the stock on hand. This is necessary for those old/manual issues that when the member returns partial/most of their equipment.
In this instance, the data has to be listed on the members return list.

Recommended
We are in the need to the capability to Ghost (add in) or change data on a members issue list without changing the inventory posture in the warehouse. The reason for this is that there are many situations where a member has been issued gear that is not in the system. Across the CSP enterprise there are old lists that need to be added to a members issue list. This anomaly in the data significantly slows down the returns process. In the case of a “Ghost In,” the system should record a gain to the issue quantity against that warehouse, and not decrement the stock on hand. This is necessary for those old/manual issues that when the member returns partial/most of their equipment. In this instance, the data has to be listed on the members return list. Likewise, a members record should be able to be changed in any way via the Ghost process. All changes to the record should transactional impact the warehouse the issue is recorded against.

Mission Critical
This is a mission critical requirement for implementation at Camp Lejeune and beyond. The thing that makes this type of record absolutely critical is when a member comes in whose record and issued data is not in DPAS. That member has some of the gear he/she is returning, but not all of it. In the current return process, we add in items that are not being returned. As a result, we cannot properly capture that the member who came in still has gear, and get that data into the system. In addition, it is critical that we have the ability to input issued items date to the system for previous issues. There is no manual process for this now.

Benefits
The ability to Ghost in data will improve processing times across the counter, and will also result in greater inventory accuracy as the CSP Enterprise will now have the capability to manually correct/load data that should be in the system.

Users
This will affect all DPAS-WM users, and would greatly aid users in standing up the DPAS-WM.

Description
USAF desires M&U Role for its Mechanics which will allow them to input time per Sub-Work Order (Job). The Role would have the basic concept of Custodian in PA. The Mechanic would only have access to Sub-Works assigned with limited functionality.

Recommended
Create Mechanic Role as outlined in Attachment

Mission Critical
No

Benefits
For National Guard and Reserve units with reduced manning, this will assist with improved accuracy of direct time and reduce the time to close opened Work Orders.

Users
Maintenance Activity Mechanics

Completed - Release 3.0 - 15 May 2015

Description
When an NSN/serial number asset is assigned to a kit its visibility is completely lost in WM inventory inquiries. 
Currently, the only means to locate NSNs/serial numbers within a kit is to utilize the Sets, Kits and Outfits Module and open each individual kit to locate specific serial numbers.
Impact:

1. Inability to query for specific serials/NSNs when they become due for maintenance required agency/service required programs.
   In one case we have 72 kits assembled containing 10 serialized line items 5 of which have mandated maintenance
2. Inability to query NSNs housed within kits to meet service/agency serial number validation requirements
3. Inability for query for SN's located within kits in response to safety related messages.

Recommended
Allow query of NSNs and serial numbers residing within SKOs

Mission Critical
Query and identification of serial numbered assets (wherever they may reside) is a critical function of any inventory management system.

Benefits
Essential for accountability of assets residing within kits.

Users
This affects ALL commands utilizing serial managed components SKOs.

29Aug2017 – cancelled per Mike Cockrill
Yes, please do remove the subject SCR and thank you.

In order for CSP or DMC to properly remark stock within the warehouse with the applicable TDMS changes, there must be output in DPAS that creates a log/suspense for the warehouse to take actions and new printed labels are required related to any TDMS change process if there is inventory on-hand, etc.(changes are Unit of Issue Changes, Nomenclature, FSC, and NSN changes (phase codes). Customer priority: 1

Description
No project code displays on the Intermec CN3 handheld during the receipt process.

Recommended
Project code must be displayed so assets can be identified at the time of receipt. Assets of the same stock number will be ordered on many different project codes and can't be identified without this information.

Mission Critical
Yes, Project codes can not be identified without the project listed on the grid.

Benefits
The benefit is this will be automated rather than writing it on each document.

Users
All

Completed - Release 3.0 - 15 May 2015

Description
Navy FIAR efforts require supporting documentation for acquisitions and dispositions.
Need capability to add multiple attachments to multiple assets at a single time.

Recommended
Create process during Asset Management / update to permit multiple attachments to be added to multiple assets.

Mission Critical
This is not mission critical or mandated but rather supports continuous process improvement regarding compliance with FIAR directives for document retention.

Benefits
Improves audit readiness by reducing the time spent to add documentation for to asset records.

Users
Yes to all Agencies.

Completed with SCR 00586.

Description
To meet the Air Force General Fund Trial Balance Report requirements, Critical Feeder systems provide proprietary general ledger data to the General Accounting and Finance System (GAFS). The Air Force Equipment Management System (AFEMS) provides a year-to-date reconciliation file for the Equipment and Accumulated Depreciation Accounts concurrently with a monthly detail file. The file will be used to reconcile the detail transaction to the yearly summary and identity processing problems.

Recommended
DPAS will construct interface to support Air Force.

Mission Critical
Mission critical to the success of the AF meeting CFO reporting requirements for Vehicles and potentially Equipment.

Benefits
Will reduce the number of systems maintained by the Defense Finance and Accounting Service–Denver and create a monthly Air Force General Funds Trial Balance report.

Users
All users within in AF Site DF-VEHS.

Customer priority: 1

Partially Completed - Release 5.1.3 - 11 August 2017

Completed - Release 5.2.00

Partially Completed - Release 5.2 - 29 September 2017

Description
The CSP Program frequently moves batches of 1500 serialized SAPI Plates between the NCR IIF and the Camp Lejuene X-Ray Facility. In addition, those SAPI plates are shipped back from Camp Lejuene to the NCR DC, and the DC will replenish the IIF as required. The problem we are having is in the time consuming nature of processing these shipments. in DPAS it takes between 2 and 5 seconds per serial number to process a shipment of serialized items. Given the 5 second worst case scenario, it will take NCR personnel over 2 hours of uninterrupted system time to complete a transfer or MRO of these items. In their previous system, LVI personnel could ship a container containing 1500 serial number in 2 minutes or less.

Recommended
It is requested that the DPAS-WM be updated to allow for the system to process containerized shipments of material for warehouse transfers, dispositions, and MRO's being shipped from the a warehouse to make serialized items easier to ship. If a container is chosen to ship, the system should automatically select all serialized and other material in the container and manifest that info on the 1348 for shipment to another facility or program (External system).

Mission Critical
This is a critical system change requirement, becuase the orginizational structure of the CSP Program is not currently staffed to dedicate the time needed to ship serialized items from the warehouse the way the system is currently designed. In addition, it is difficult for any user to commit the amount of uninterrupted system time needed to complete a serialized transfer, disposition, or MRO.

Benefits
The proposed fix will serve to make processing time of MRO's, dispositions, and transfers of serialized 60 times faster, and will be more in line with aid NCR in meeting its personnel staffing needs without having to hire more personnel to handle the arduous job of entering 1500+ serial numbers for shipment as the system is currently designed.

Users
Yes, this will impact all of CSP, DMC, and other system users across the enterprise.

Completed - Release 3.0 - 15 May 2015

Description

1. Each AF Air Crew facility contains approx. 3K Sq Ft of space
2. No plans to ever use handhelds (too expensive) for the Qty they require (250+ sites)
3. Currently in DPAS, Inspection / Maintenance Frequencies are set at the Stock Nbr level (Catalog).
   Each warehouse may have different requirements based upon the mission they are supporting.
   Proposal would be to add Inspection Fields to the Stock Item Record.
   They would override values set at the Stock Nbr level, when populated.
4. Need a method for managing stock with SEALs
   If sealed, the assumption is everything is in the kit.
   No need to inventory the individual pieces.
5. Receiving
   Would like to see the Document Nbr wizard's drop downs pre-populated.
   Would be a plus to have the Document Type and Sub Type defaulted to a preferred value rather than forcing them to select a value each time (90% of the stuff they purchase is a DLA requisition).
6. Physical Inventory
   Due to the fact that they won?t be using the Handhelds, they would like to see a bar code scanner reader within the Physical Inventory process so they could scan the items directly into the computer.
   They plan to have PCs next to the inventory and be able to scan them in using the PC itself.
7. Kitting
   Needs to be streamlined. They build "One Off" kits for each Air Crew member.
   They do not want to have to run the Pick Plan/Pick processes.
   These kits have a lot of shelf life and sized items.
   They could see using the MIL / Individual Issue Front End to design/build the kit.
8. Need to be able to define the Skill Levels for the "Personnel" in the warehouse.
   If the Skill Level is less than fully skilled, the Maintenance/Inspection performed by that person must be 100% QCd by another individual.
9. Need to have some of warehouse items 100% QCd e.g.
   Parachute packing has multiple QCs during the packing process.
   Need a way to define what these items are.
10. Need a way to calculate a 10% QC of items that have been worked (daily amount excluding those that are subject to 100%.
11. Need to separate Maintenance Actions from QC actions.
12. They need visibility of every Stock Nbr, Condition Cd, Shelf Life data, Qty to include what is in the kit (special query?)
    Readiness reporting
13. Need to know what items are expiring (item 11 above) in a budget format so they can determine their funding requirements are in the current years and future year (to be able to POM).
14. Need to be able to scan a kit to make an issue (no MIL is involved).
15. Want to be able to scan a kit on a return, and be able to disassemble it when the member is leaving (typically it would be returned as a kit).
16. Possibly want a streamline disposition process.
    When they remove items from kit due to expiration that can be trashed, they would like it to be mark the item as disposed as part of that process.
17. Need to be able to issue kits to a tail number (aircraft).
    No custodian is involved.
18. Need to be able to manage items as a Set e.g.
    They usually have 2 sets of masks to support an aircraft.
    One is on the aircraft and the other is being refurbished/in stock ready to replace the ones on the aircraft when they are ready for refurbishment.
19. Need to see items in kit and their shelf life data throughout the system (queries, Maintenance, Quality Control, etc.)
20. Need to setup work flow roles based upon dollar value of the item, or possibly ARC codes etc.
    Currently the Air Force approvals are based upon Stock Nbr and their dollar value. Stated ARC may work for them in lieu of Dollar value.

Jake's Additions/Supplements:

1. Kit Receiving/Set Kit Outfit
   currently SKO build requires them to create picks to get all the components of a kit into the same location before they build it. The AF will not need that step, in that, all of the components are already stored in the same location where they are built.
2. Individual Issue
   Their issue facilities work nothing like the marines. From what they showed us, they have their "issue facility" and that issue facility supports a fixed amount of members who all have a (warehouse specific) number. So when a member number 8 walks in the door to be issued a specific set of gear, each piece of that members gear is in an applicably marked location. So they would go through the facility to find each location marked with an 8, and pick up the gear that's there. What that means is that the issue facility could have 1 to X "Location 8's".
3. Individual Issue
   members do not sign for their gear. In fact, no one even monitors the issue process. The Issue Facility Personnel has a "Return Counter" where members come in each night and drop their gear. At the end of each day the Issue Facility personnel goes over to the return counter, grabs the gear and puts them back in the correct location. At the start of each day, they pull up a schedule of members that will be flying that day, and check their applicably numbered locations to make sure they are properly stocked with the right gear. Once they confirm that such is the case, they assume that gear will be issued that day. So member number 8 can come in at their leisure, walk around the facility to all the location 8s, grab all their gear and walk out the door without ever even talking to any of the issue facility personnel. At the end of the day, member 8 comes back into the issue facility and throws their gear on the return counter and walks out. In other words, on issue and return, the members are not signing a receipt indicating there has been an issue. Additionally, there is really no defined issue event that takes place. There is simply a flight schedule and an assumption that the gear associated with the members flying that day is issued.

Recommended

1. Be able to create a "Custom" kit for a member and be able to issue the kit w/o having to create master SKOs for each member.
2. Be able to associate the custom kit to the member while in inventory and be able to create a quick issue of that kit.
3. Monitor issued materiel for Shelf Life/Maintenance activity and produce Maintenance Actions on the materiel.
4. Product budget reports that depicts the amount (qty/$) of shelf life materiel stratified by the year the materiel will expire.
5. Capability to print ICNs on .5" by 1.5" labels.

Mission Critical

Benefits

Users

Completed - Release 3.0 - 15 May 2015