|
01434 |
ICP Stock Item Add |
Materiel Management |
USMC: CSP |
Removed |
Description In the ICP there is currently no way to add stock number to the stock item AUD for multiple warehouses. To add the new stock number to the stock item AUD for the warehouses we have to do it individually for each warehouse. This is a time consuming process.
Recommended CSP recommends creating functionality that will allow for user to add stock number to the a stock item AUD for multiple warehouse at a time. This will make it easier for users to add new stock number to the stock item AUD for all warehouses.
Mission Critical Yes, this will allow for the CSP PMO to add the stock numbers to the stock item list for every warehouse when new stock numbers are introduced to the program.
Benefits This reduces the time and increases the efficiency when adding stock numbers to the stock item AUD in the ICP.
Users Yes, this has the potential to affect all CSP users.
14Jan2019 – cancelled per Joe Stossel This is a duplicate of SCR 01374. |
|
|
01433 |
ICP CSP Inquiry Role |
Materiel Management |
USMC: CSP |
Done |
Description Currently when DPAS warehouses are attached to a DPAS ICP they are unable to add stock items to the warehouse. We have tried to give users roles to the ICP in order to add stock items, but this becomes problematic because of the limited number of ICP roles. The current ICP roles give warehouse users too much functionality beyond adding stock numbers to the stock item list.
Recommended CSP recommends creating a new role that can be granted to users that only has the ability to add stock numbers to the stock item grid. This will give CSP users the required functionality to add stock numbers to the stock item list, but will not let them view or transact elsewhere in the ICP.
Mission Critical Yes, currently in the CSP program, users must contact users who have ICP access in order to get stock numbers added. There are very limited number of users who have this access which could possible cause a work stoppage.
Benefits The benefits of implementing this solution is that we could assign users in every warehouse this role. This would allow every warehouse to be self sufficient when adding stock numbers to their stock item list.
Users Yes this will affect all ICP users who will be assigned this new role.
Completed - Release 2021.2.2 - 2 July 2021 |
|
|
01432 |
New Form in Unit Issue Request and Transfer Process |
Warehouse |
NAVAIR |
New |
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. |
|
|
01431 |
View Asset Additional Information in ICN Inventory |
Warehouse |
NAVAIR |
New |
Description Some users can add Additional Information to an ICN during receiving and in Inventory Update; however, there is no other place to view this information. Not all users have or need access to Receiving or Inventory Update. Additional Information needs to be available to view on the ICN Inventory Inquiry so that all users can read/review the Additional Information.
Recommended Recommending the ability to view asset "Additional Information" as found in Inventory Update in ICN Inventory Grid Options. Recommending this to also be a searchable field.
Mission Critical Not mission critical or mandated.
Benefits This will improve accuracy and accountability of the tools by being able to see relevant notes to specific tools that users have entered so other users with different roles can see. The notes will also leave a history for the tool to further help in the case of tool history research.
Users It will affect all users because notes for the specific tool will be seen by all. |
|
|
01430 |
Update Expected Return Date |
Warehouse |
NAVAIR |
New |
Description There are 3 categories of ST/STE requests:
- Warehouse requests (ST/STE is stored at a warehouse and is requested to be shipped to a location for usage),
- Contract Transfers (ST/STE is staying at the current location, but changing its contract accountability),
- 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. |
|
|
01429 |
Expanding Stock Number Field |
Enterprise |
NAVAIR |
New |
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
- Tight control of the Tooling Catalog
- Reduce workload on finding tooling associated with weapon system BOMs
- Full benefit and reporting capability offered by the Stock Number Field
- Easier loading of future PPSA files
- 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. |
|
|
01428 |
Calculate Indirect Labor Rate |
MU |
AF: VSCOS |
New |
Description Currently, DPAS does not provide an indirect labor rate. Indirect labor rate should include all work performed by civilian and military personnel charged to the transportation function that cannot be identified to a particular NTV or group of NTVs.
Recommended Utilize work order reasons; "PORL - Parts Only Low Cost Bench Stock" and create a work order reason "INDR - Indirect Labor". Calculate by dividing total indirect labor cost by total available direct cost.
Mission Critical This mandated per DoD 4500.36, Appendix 2 Enclosure 4
Benefits The benefits of this solution would be to solidify the correct indirect labor rate across all DoD functions.
Users All DoD Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes. |
|
|
01426 |
Calculate Asset End of Life |
MU |
AF: VSCOS |
Removed |
Description Currently DPAS does not calculate an assets end of life (EOL) when its average annual sustainment cost first exceeds, or is projected to exceed, its depreciated value, or seven years after a depot rebuild, whichever comes later.
Recommended See notes below. This feature was developed by 441 VSCOS and added to LIMS-EV Transaction Request Tool.
Mission Critical Mission critical. AFI 24-302 states "Use economical, reliable and up-to-date procedures to authorize, acquire, account for and maintain vehicles in a safe and serviceable condition throughout their lifecycle." The EOL calculation helps determine the most economical time to replace an asset.
Benefits The benefits of implementing this solution will enhance the annual vehicle purchase drill be pin pointing the most economical time to replace an aging asset.
Users All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.
**NOTE** This SCR is in conjunction with SCR 01422 Vehicle Prioritization Model.
21Feb2025 – cancelled per Luther Meitzner |
|
|
01425 |
IntelliSense for Operators |
MU |
OSD |
New |
Description Operator / Technician listing is very long and slows down the assignment process in Dispatch. There is no quick way of finding an individual.
Recommended Utilize the IntelliSense capability when assigning "Dispatched To" during the Dispatch A/U.
Mission Critical Critical to the accurate and expedient assignment of personnel to equipment
Benefits Reduces time and improves accuracy of asset assignment.
Users Only personnel identified to accept material via M&U. |
|