Description
When in the Warehouse module,the user is unable to choose the appropriate Army condition code (Army Policy AR 725-50) to show the inventory control record the physical state of the materiel.

Recommended
Include the additional Army condition codes (see encl) in the drop down menu.

Mission Critical
This is mission critical, Army customers process hundreds of transactions daily in DPAS, without this process it hinders the ability for the customer to properly show the condiction of the materiel they are actioning; current state they are misapplying condition codes based on lack of Army condition codes.

Benefits
Adding the Army condition codes will allow us to appropriately validate the materiel while improving accuracy, and accountability aligned to audit. This would also improve internal controls and stream line items affecting Army logistics business processes.

Users
This would affect all the ASA ALT community -- users in DPAS (WM).

Description
DPAS's Handheld Terminal (HHT) executive software is no longer supported by the vendor, thus the devices can no longer be connected to the DoD network. This does not alleviate the functions of the DPAS programs, but rather results in performing these functions manually rather than using AIT automation. This SCR is proposing to transition the Ad Hoc move functionality that resides within the DPAS application to a web application enabling the user to use any approved device that is capable of hosting a DPAS session.

Recommended
Develop a web page(s) that provides the capability to move an asset from one location to another or from a location into a container, or from a container to a location by scanning of asset/materiel, location and container labels. Consideration should also be given to supporting pRFID as a read methodology, and supporting planned picks.

Mission Critical
Yes, without this capability, there is an increased manpower requirement that cannot be fulfilled.

Benefits
Reduced manpower through automated scans, and improves accuracy.

Users
All users who move inventory.

Description 
AF Support Equipment is physically identified by 5-character equipment IDs that are usually based on the serial number (but not always), and are stenciled, painted, etched, or otherwise attached to make the equipment readily identifiable from 10-15 feet away. In legacy systems, this equipment ID was also used as the asset ID or serial number. DPAS uses a system-generated asset ID and the actual serial number is recorded in the system. The actual serial number is typically too long to reasonably attach to the equipment, and remarking all equipment to accommodate the transition to DPAS is cost and manpower prohibitive. Propose using an agency definable field to allow recording of a locally determined equipment ID.

Recommended 
Utilized Agency Definable field to create capability to enter and record a locally determined equipment ID. Equipment ID is non-unique and can be changed. Require ability to search by equipment ID and require equipment ID to be reflected on work orders.

Mission Critical 
This is mission critical. Lack of ability to easily identify equipment will degrade mission effectiveness and increase the risk of damage to combat aircraft. Remarking all SE to reflect actual item serial numbers is cost and manpower prohibitive, and is not possible in many cases due to length of serial number and available space for marking.

Benefits 
Improves accountability, reduces manpower cost in marking equipment and identifying equipment for dispatch, inventory, or other purpose. Reduces risk to aircraft, munitions, and personnel through ready identification of correct, serviceable SE.

Users 
This affects all M&U module users within the United States Air Force.

Description
Property Administrators cannot change multiple asset location or sub-location within one transaction. This is not a master data issue. Locations are accurately listed in master data. If an asset is moved physically, the location and/or sub-location needs to be updated from where it is currently listed in DPAS. If there are multiple assets that need to be updated under a UIC, it requires multiple transactions instead of being able to update each asset within one transaction and under one DOC number. Create the capability for PAs to update a complete UIC's assets location and/or sub-location under one transaction.

Recommended
Create the capability for PAs to update a complete UIC's assets location and/or sub-location under one transaction. Maybe this can be done by simply adding a save option within the UPDATE under Asset Management. Once all asset updates are completed for that UIC, you click submit and it is all done under one transaction and DOC number. This feature is already in use and available when new assets are added.

Mission Critical
This is not mission critical at this time. However, it is extremely time consuming and inconvenient for the PA to make updates using separate transactions and under different DOC numbers.

Benefits
This solution will save huge amounts of time for PAs. Assets listed under all UICs within their assigned AUIC, must show accurate location and sub-location in order for their physical locations to be known. Accurate location and sub-location will increase accurate asset accountability and decrease asset loss.

Users
This will affect all PAs assigned to FF-GEIT.

Description
Currently DPAS does not allow user to add new location data on the asset update screen. Only preloaded locations within Master Data may be selected from. Propose allowing user to add locations from the asset update screen rather than having to add to master data every time a new location is needed.

Recommended
Add the capability to add location data on the asset update screen instead of updating through the master data function.

Mission Critical
This is not mission critical at this time. However, it is very time consuming and inconvenient for the PA to add location data on the master data screen and then go back to the asset update screen to select the location that was added.

Benefits
This solution will save time and prevent an unneeded step for PAs. This solution will allow locations to be added on the same screen where they need to be selected rather than adding in master data and then going back to the asset update screen to select.

Users
This will affect all PAs assigned to FF-GEIT.

Description  
Need the ability in member site to allow members to select an equipment item off a list and type a narrative for feedback on that equipment item.  Within warehouse, need the ability to pull an inquiry of provided feedback.

Recommended  
Add an area within the member site for feedback.  Within feedback area have a dropdown for equipment to select from and then a narrative block for members to type into.  Add an inquiry within warehouse to pull feedback given.  Inquiry needs to have roll-up feature.

Mission Critical  
highly desired

Benefits  
time savings, data accuracy and staying within one system.

Users  
All

Description  
Need the ability to have an inquiry that will pull all repair data by component stock number and have a roll-up feature. In theory, if 20 of one component are repaired in different kits it would show one grid line for each component stock number (not kit ICN) and have a qty of 20.

Recommended  
Add an area under Inquiries to include this data with a roll-up option.

Mission Critical  
highly desired

Benefits  
time savings, data accuracy and staying within one system.

Users  
All

Description  
ASA(ALT) community would like to customize roles for its users in support of the mission objectives of the Program Managers.

Recommended  
Modify the DPAS roles to custom ALT roles in support of Army business process; create the ALT roles on the attached spreadsheet aligned to business functions required.

Mission Critical  
This is mission critical because ASA(ALT) PMs operate in a slightly different manner than a traditional warehouse.  We also need to have super users available to support each organization.

Benefits  
ASA(ALT) PMs will be able to utilize and execute DPAS in accordance with their mission objectives.

Users  
Yes

Description  
Each Program Office/Commodity Type has a responsibility to maintain a complete inventory of all government owned ST/STE property. Periodically, complete Physical Inventories are conducted at each storage location. This inventory is managed in excel documents, identifying the tool id, condition, and physical storage location. The Program Office manages tens of thousands of production ST/STE for each weapon system, it would be physically impossible and costly to manually update the DPAS database with the current condition and physical storage location for each item after a physical inventory. An automated solution is needed to mass update lists of ST/STE in a timely, cost effective manner.

Recommended  
Need to create an import program to upload the Physical Inventories and update the condition and physical location of each tool.

Mission Critical  
Mission Critical. In order to be FIAR audit compliant, the program office must be able to reconcile their inventories within DPAS.

Benefits  
This correction will reduce Time/Cost for updating physical inventory lists and ensures/improves Accuracy and Accountability of DoD owned ST/STE. It is mandated that the complete list of all DoD owned ST/STE property be managed in DPAS. Currently, it is cost prohibitive to manually update the location and condition of all tooling located at a storage facility after a physical inventory. 

Users  
All users, it is vital to know where tooling is stored to support the maintainability of the weapon system.

Description
Each Program Office/Commodity Type has a responsibility to maintain a complete inventory of all government owned ST/STE property. Through the eTIMS system, the Program Office receives a listing of any new ST/STE that has been created to support the weapon system. This information needs to be inserted into the DPAS database, so the Program Office has a complete inventory of all government owned ST/STE.

Recommended
Create an import to add new ST/STE into DPAS.

Mission Critical
Mission Critical. In order to be FIAR audit compliant, the program office must be able to reconcile/manage their inventories within DPAS.

Benefits
This correction will reduce Time/Cost for adding new ST/STE and ensures Accuracy and Accountability of DoD owned ST/STE. It is mandated that the complete list of all DoD owned ST/STE property be managed in DPAS. Currently, it is cost prohibitive to manually add large numbers of new ST/STE through the on-line DPAS system.

Users
All users, it is vital to know all ST/STE owned by the DoD to support the weapon system. The users need to know what ST/STE is available to maintain the weapon system.

Description
Warehouse Individual Issue provides an auto-pick capability when a Stock Item Individual Issue Location is set for a stock item. It doesn't allow use of a Container as the Individual Issue Location.

Recommended
Allow setting a Stock Item Individual Issue Location at the Container level so an issue transaction can auto-pick required quantities.

Mission Critical
This is a time and resource saving change.

Benefits
Reduce time (clicks) to process an Issue transaction.

Users
Warehouse users performing Issue transactions.

Description
Enhance existing DPAS CIP to support USMC NAF requirements.

Recommended
Develop the functionality to support tracking CIP costs by Development Phase. Add logic to display fields based on Project Phase and Project Type. Add approximately 10 new fields (operational category, POET, Funding Purpose, etc). Develop functionality to calculate ROI based on customer's calculation.  Add functionality to track CIP Funding by RPUID. Develop ability to track CIP Projects over 5 phases (Bid, Design, Construction, etc). Add logic to display fields based on Project Phase and Project Type. Adjust current CIP Real Property to allow users to create CIP shell with fewer required fields.  Create a Facility Condition Report.

Mission Critical
Currently DPAS does not support this functionality.  This would be necessary to support USMC NAF's requirements.

Benefits
Improvements to Accuracy, Accountability, Financial Reporting.

Users
This would provide additional functionality to all DPAS Real Property users.

Description
Build a Work Order tool to support USMC NAF maintenance and repairs.

Recommended
Develop a tool to log, track, and support building maintenance and support and associated tasks and work orders. The tool will include the ability to schedule preventative maintenance on a recurring basis (e.g. Annual Check/Maintenance of the HVAC system).  tab within the RP asset that allows the user to view all of the Work Orders associated to that RP asset. Provide sufficient summary information to know what the WO was for with a hyper link to display the specific Work Order in a new Browser window. Store record of work orders performed on asset, populated from work order tool and ability to enter records.

Mission Critical
Currently DPAS does not support this functionality.  This would be necessary to support USMC NAF's requirements.

Benefits
Improvements to Accuracy, Accountability, Financial Reporting.

Users
This would provide additional functionality to all DPAS Real Property users.

Description
The current Real Property functionality in DPAS needs enhanced to support USMC NAF Real Property needs.

Recommended
Develop a means to realize RP CIP to the property book, develop ability to setup and manage a RP Improvement. Build a new tab to track Facility maintenance. Build a new tab to track CIP Improvements and projects associated with the Real Property asset. Build functionality to track funding for the Real Property asset. Develop tests to track facility maintenance spend and facility condition.

Mission Critical
Currently DPAS does not support this functionality. This would be necessary to support USMC NAF's requirements.

Benefits
Improvements to Accuracy, Accountability, Financial Reporting.

Users
T his would provide additional functionality to all DPAS Real Property users.

Description
Build a Project Planning tool within CIP to support USMC NAF Real Property life cycle management.

Recommended
Build a minimum viable product project planning tool.  The tool will include:  Additional fields to support different phases; ability to track through submitted / approved / design / construction; ability to pull in projects from Microsoft project; ability to build projects with associated funding fields, category types, calendars with alerts; Single Use Projects and Multi Use Projects; Project sub types: Capital Improvement and Maint.

Mission Critical
Currently DPAS does not support this functionality. This would be necessary to support USMC NAF's requirements.

Benefits
Improvements to Accuracy, Accountability, Financial Reporting.

Users
This would provide additional functionality to all DPAS Real Property users.

Description
Enhance existing DPAS CIP Funding to support USMC NAF requirements.

Recommended
Develop the functionality to support multiple Funding sources to support development phase. Add ability to decrement funding based on funding phases and costs. Build a grid display to show all funding documents and the totals for all funding documents. Automation of USMC funding docs via GEX interface. Fix Source Desc Display.

Mission Critical
Currently DPAS does not support this functionality. This would be necessary to support USMC NAF's requirements.

Benefits
Improvements to Accuracy, Accountability, Financial Reporting.

Users
This would provide additional functionality to all DPAS Real Property users.

Description
The existing ST/STE database, eTIMS, generated a form called a "C-List" for every request created. The "C-List" contained: who created the request, who the list is addressed to (warehouse if a unit issue request, or vendor if an issue transfer), request number, date request created, aircraft, comments (remarks), ST/STE list, contract, UIC, expected return date, ship to (UIC and address), ship to contact (name and phone). The closest thing to this form in DPAS is the Issue Receipt form. This form does not have some information which used to be on the "C-List." Also, the Issue Receipt is only available once a UIR is Issued. NAVSUP WSS requires a form be generated upon the completion of a UIR on their end (once the UIR's status changed to PK-Picking). As of now, they have to take screen shots of the UIR page to provide to PCOs and vendors to show we have completed the request. A sample C-List from eTIMS and an example of what the new form should look like will be provided with the submittal of this SCR.

Recommended
Create a new form that includes all information as the provided C-List, or update the Issue Receipt to include this information.  The information that should be included on the form should be: Unit Issue Request Established By, Established Date/Time, To, Request or Transfer #, Reportable Commodity Type, Remarks (mainly for TAC information), Tooling List, UIC, Account Name, Expected Return Date, Ship to Address, and Contact Information of UIC Custodian.  Make this form available to view and print when the request is "In-Process" or "Pk-Picking" status. Also make this form available during the Unit Issue Transfer process.

Mission Critical
Mandated. Vendors and PCOs require some type of documentation to use as a receipt that the UIR has been started/completed. DCMA uses this documentation when inspection occurs, PCOs use this document when modifying their contracts.

Benefits
This solution will create a formal document that we can use as proof of completing a UIR. It will improve accountability and standardize the UIR process.

Users
This change will impact not only users of DPAS and the ST/STE community, but DLA, NAVSUP WSS, and NAVAIR PCOs/ACOs. Vendors also rely on a formal document as an inspection point that a UIR has been completed.

Description
There are 3 categories of ST/STE requests:

1. Warehouse Requests (ST/STE is stored at a warehouse and is requested to be shipped to a location for usage)
2. Contract Transfers (ST/STE is staying at the current location, but changing its contract accountability)
3. Loan Extensions (ST/STE is staying at the current location and being used under the current contract, but the expected return date needs changing).

The Unit Issue Request process works well for warehouse requests. However, for Contract Transfer Requests, utilizing the existing Unit Transfer Request process does not give us the ability to update the expected return date. There also isn't a separate process to allow for updating return dates when processing Loan Extension requests.  Lastly, Open Warehouse Actions for Unit Returns are not updating when an expected return date is updated.
The work around we have been using in order to add return dates is to return ST/STE to the warehouse, then issue it back out with a Unit Issue Request with a return date. This is creating unnecessary rework and longer touch times and cycle times to complete requests.

Recommended
Incorporate the ability to add an expected return date to the Unit Transfer Request process and the ability to update the expected return date to ST/STE on loan (without transferring the contract). Accommodate the Contract Transfer and Loan Extension Requests described above.  Open Warehouse Actions for Unit Returns need to be updated when expected return dates are updated.

Mission Critical
Mission critical. ST/STE must have accurate expected return dates in order to have proper accountability and traceability.

Benefits
This implementation should reduce the cycle time to complete Unit Transfers and Loan Extensions by at least 67%.

Users
This change will impact not only users of DPAS and the ST/STE community, but it will improve fleet readiness by allowing us to complete requests much faster than we currently do.

Description
Each Program Office/Commodity Type has a responsibility to do a wall-to-wall inventories of all government owned property.  When conducting physical inventories within DPAS, often multiple commodity types will show up in one location.  This is a problem because DPAS will not let one commodity type to reconcile their inventory when another commodity type is in the same location. 

Recommended
Recommending that when conducting physical inventories, let each commodity type reconcile the ST/STE inventory they own within that location.   

Mission Critical
Mission critical.  In order to be FIAR audit compliant, the program offices must be able to reconcile their inventories within DPAS.

Benefits
This correction would all for all commodities to complete physical inventory reconciliations and be in FIAR audit compliance.

Users
This change will impact not only users of DPAS and the ST/STE community, but it will improve fleet readiness by allowing us to insure that the ST/STE inventory is 100% accurate.

Description
NAVAIR is responsible for managing Special Tooling/Special Tooling Equipment associated with various weapon systems/reportable commodity types.   Manufacturing numbers that are created by vendors are used for the stock numbers of the tools.  However, the vendors' manufactured numbers have been known to be 25+ long.  The length of these numbers are not standardized across vendors.  More than 15 characters are assigned to ST/STE to uniquely identify the tool.  As such the current solution prevents the use of the Stock Number field and the associated capability within the DPAS system.   The Special Tooling Identifier is part of the Stock Number Description Field along with the Noun.  In addition, this practice makes it difficult to utilize the Master List Capability to building Tool to Tool and Tool to Part relationships.
The conversion into DPAS utilized a unique identifier from the source systems primary key, but after conversion future entries will require the generation of a unique DPAS key.  Loading large numbers of ST/STE from OEM will be further complicated as the OEM assign the Tool ID and the current practice of using the Stock Number Description will not trap duplicate entries on the Catalog.

Recommended
Request the expansion of the current 15 character limit of the Stock Number field to 30 characters in the Warehouse Module to accommodate future Special Tooling and Special Tooling Equipment (ST/STE).

Mission Critical
Mission Critical.  Over time the management of ST/STE by NAVAIR will be hampered with duplicate Catalog entries due to the 15 Character limit in the Stock Number field.  Future assignment of Inventory to the catalog and asset reporting will be hindered.  Duplicate Stock Number entries (via a description) will challenge audit-ability of this data.

Benefits

1. Tight control of the Tooling Catalog
2. Reduce workload on finding tooling associated with weapon system BOMs
3. Full benefit and reporting capability offered by the Stock Number Field
4. Easier loading of future PPSA files
5. Elimination of duplicate Catalog entries and association of Inventory to Catalog entries, removal of future audit findings.

Users
This change will impact current Navy ST/STE community and potentially the Air Force ST/STE community.  Additionally any future or current community for which the Stock Number field proves to be too short.