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