|
01182 |
Address fields available in Inquiries, add an Address Inquiry |
MU |
AF: VSCOS |
New |
Description When doing inquiries on Equipment Pools, Maintenance Officers, and Destinations not all information inputted into these fields are viewable or search-able by using the fields tab when setting up an Inquiry. Addresses and remarks for example; the user cannot see what is current unless going to each one.
Recommended Add Address field information to be available to be searched in Inquiries. Create a Inquiry to be able to search for addresses of Equipment Pools, Maintenance Officers, and Destinations. Create a Address Inquiry in M&U like the one in PA
Mission Critical This is critical. Fleet managers count on viewing information to be able to make informed decisions to manage Air Force fleets around the globe.
Benefits Allowing addresses to be viewed in Inquiries will enhance reports and inquiries for all. Enabling user to be able to find any information on customers. This will aid in data integrity.
Users This SCR will affect the entire AF Agency, all Air Force fleet managers/maintenance controllers utilize this information for day to day fleet management purposes. |
|
|
01181 |
Catalog Stock Number Field |
Warehouse |
AF: VSCOS |
Removed |
Description The Add Stock Number field does not allow any special characters and it is limited to only 15 characters in length. Many vehicle manufacturers and commercial vendors utilize special characters in their part numbers. The current DPAS Warehouse add stock number field parameters make it very difficult for these vehicle part numbers (that are not NSNs) to be inputted into DPAS. When changes are made to make these part numbers fit such parameters, the entire part number is changed and no longer a valid manufacturer part number.
Recommended
- Open the add stock number field to accept as a minimum these special characters "-", ".", "/",
- Accept up to 25 characters in length.
Mission Critical It is mission critical to be able to find the correct part number for vehicles being maintained. If correct part numbers are not found/used this in turn could lead to wrong parts being ordered, used and ultimately could cause safety mishaps.
Benefits Allowing for special characters and increasing the length of the stock number will enable for more accurate parts research and decrease the chances of wrong parts being ordered and used. Utilizing the correct parts will save money and increase the safety and serviceability of vehicles.
Users This change will positively impact not only Air Force users but all DPAS Warehouse users as well.
25 January 2023– cancelled per Tim Thompson SCR fulfilled through SCR 01758 |
|
|
01180 |
Individual Return Queries |
Warehouse |
USMC: CSP |
Removed |
Description Currently DPAS-WM does not have the option to use My Queries during an Individual Return. Recommend that My Queries functionality be added to the Individual Return process.
Recommended Recommend that My Queries functionality be added to the Individual Return Process.
Mission Critical Yes, this will help increase the speed and proficiency during the Individual Return Process.
Benefits Having this functionality will help with the speed and proficiency during the individual return process. thus being able to get more members through the Individual return Process.
Users All IIF
11 Mar 2021 – cancelled per Jack Sanders No Longer Needed. |
|
|
01179 |
Add new CIP GLAC - 1516 - Operating Materiel & Supplies - In Development |
PA |
Leidos |
New |
Description Auditors have identified the need to have a Construction In Progress Account for Operating Materials and Supplies. The U.S. Treasury has added GLAC 1516. This GLAC will permit those agencies that "construct" OM&S items, such as a missile which may take several years for the delivery to occur.
Recommended Add new Asset Cd and GLAC to the CIP Project process and various DPAS Inquiries, CFO / Trial Balance reports. Coordinate change with financial systems to determine if they can accommodate the new Asset Cd. If they are not able to, identify the Asset Cd this account should be mapped to.
Mission Critical This is a policy change that DPAS needs to implement as it has customers that construct OM&S material.
Benefits No other known work around to identify OM&S in Construction.
Users This change is limited to those customers that construct OM&S which requires it to be managed through CIP. |
|
|
01178 |
Incorporate Materiel Returns Program into Materiel Mgmt, Warehouse, and PA modules |
Enterprise |
SOCOM |
In Progress |
Description USSOCOM is transitioning a number of its logistics processes from multiple systems, and in some instances manual processing to DPAS as it looks to integrate with its supported Service Special Operations Commands (SOCs). Several of the Army's PEOs is also looking to use DPAS to support the fielding of new equipment. These transitions will likely encompass the use of all modules of DPAS. One the processes that DPAS does not currently support is the DoD's Materiel Returns Program (MRP).
Recommended DPAS needs to incorporate the requesting / management of a Materiel Return into the PA and Warehouse modules. Within the Materiel Mgmt module, DPAS needs to incorporate the acceptance, determination and response of the request. Each Module should provide the user with the a viewer of the request along with the response provided. For "Accepted" materiel returns to the DPAS internal Materiel Mgmt module, the Materiel Mgmt module should generate and send a 527D (Due In) to the RSA (DPAS or an external RSA). This SCR encompasses the need for inquiries/reports to show the open items as well as closed actions with the actual disposition taken. Dashboards displaying open actions in the PA, Warehouse and Materiel Mgmt modules should be developed along with the capture of metric showing the number of approved/denied disposition of the MRP Request. Programs that can be executed by the user that identifies potential excess equipment and supplies is recommended utilizing Authorized to On Hand quantities for PA. For the Warehouse module, the system should utilize Program Exit Dates (item no longer used), Demand quantities (is stockage too high for the current demand), and should also look at the Unit's Authorized to Issue Qtys. For items considered excess, that are subject to return the ICP, the system will generate a DLMS 180M (Return Merchandise Authorization and Notification)transaction set to the Item Manager. Responses to the DLMS 180M will be via the DLMS 870M (Materiel Returns Supply Status) transaction Set. For additional guidance, refer to DLM 4000.25, Volume 2.
Mission Critical Yes. As DPAS increases its users base and expands the support of it Logistics Capabilities there is a requirement to support the DoD Materiel Returns Program for the Customer and for the Product Manager.
Benefits Improves the overall integration with DoD programs. Saves the Department $ as user may be more inclined to use the MRP, when the automation exists. This capability is considered mandatory for the Materiel Manager as well as the user.
Users As DPAS is used more within the Special Operating Forces environment, this capability will be used more an more. The requirement was also listed in the USMC DMC Requirements package to support parts within the kitting area.
Partially Completed – Release 2023.4.5 – 01 December 2023
Partially Completed – Release 2023.4.6 – 15 December 2023
Partially Completed – Release 2024.1.1 – 12 January 2024
Partially Completed – Release 2024.1.2 – 26 January 2024
Partially Completed – Release 2024.1.3 – 09 February 2024
Partially Completed – Release 2024.2.7 – 28 June 2024 |
|
|
01177 |
Modify DPAS to support the Receipt and Mgmt of Customer Requisitions |
Warehouse |
SOCOM |
In Progress |
Description USSOCOM is transitioning a number of its logistics processes from multiple systems, and in some instances manual processing to DPAS as it looks to integrate with its supported Service Special Operations Commands (SOCs). This transition will likely encompass the use of all modules of DPAS. One the processes that DPAS does not currently support is the receipt and management of Customer Requisitions (DLMS 511R), which is required as USSOCOM is a Source of Supply to the (SOCs) using the RIC of H9D. The majority of the spare parts consumed by the SOCs are ordered today using the DoD Standard Supply Requisitioning Process.
Recommended Incorporate the capability to accept a Customer Requisition (DLMS 511R) within the Materiel Management module of DPAS from a DAAS transmission. Provide the user with a screen to view and manage (Review, Accept, Deny, Modify, Refer, Monitor) Customer Requisitions. In addition to accepting the DLMS 511R, the system must be capable of supplying the customer with the status of their requisition via the DLMS 870S and to be able to accept modification, cancellation and status requests from the customer. The process must be able to generate and submit a DLMS 940R to the Remote Storage Activity (RSA) that the item manager desires to have fill the requisition, to include being able to request and accept statuses from the RSA. See attached document for additional information. Note: This SCR does not include the capability to accept and manage Customer Return Requests as outlined in DLM 4000.25 / DLMS 180M Transaction Set. Should this capability be required, a separate SCR will be submitted to request the incorporation of this functionality.
Mission Critical Yes. The SOCs order their consumables / repair parts using MILSTRIP procedures from USSCOM. In order to fully transition to DPAS, the capability to accept a customer requisition is required.
Benefits Provides for the reduction in the number of systems that USSCOM must use, thus improving the integrity of the information and reducing the total cost of operation.
Users This SCR will benefit all users who have a requirement to accept and manage Customer requisitions using DPAS. It may prove to be invaluable to the Air Force GFM-A effort, as they begin the transition of some of the CICPs to DPAS.
Partially Completed – Release 6.2 – 31 August 2018
Partially Completed -- Release 2021.2 - 28 May 2021
|
|
|
01176 |
FAST Reportable Inquiry |
MU |
OSD |
New |
Description Mr. Sims (DoD FAST Manager) has requested DPAS Leidos personnel to execute a data extract monthly. As such, it's only available when Leidos executes the database script. If these output products are a required product of DPAS, they should be added to the menu as a standard inquiry, report or an Agency Pre-defined report. The reports should have some filtering capability, thus the possibility of having these extracts as Agency Pre-defined may not be a viable solution. For example: the ECC for trailers falls under ACC = P, but trailers are not FAST Reportable 'yet'. I just want to ensure we all are on the same page on that. This means, I need to have ECC = VU/VW omitted from the pulls and ensure we do not send those to FAST 'yet'. Using the example, it appears that the reporting of trailers to FAST may be in the works, thus allowing the FAST Manager to include/exclude certain ECCs may be beneficial. Also, there are some scripts/pulls I will need at the Enterprise Level. Do I do a SCR to have it created so I can pull in DPAS? These are the monthly reports I need reflecting FYTD and month totals:
- FAST Reportable in PA and M&U
- Maint Mgmt Cd = NPD
- Maint Asset Util <= 0
- Fuel Util not Reported
- Cost <= 0
Recommended Migrate the current FAST database scripts from being limited to being executed by a Leidos person with Database Read Access to a menu selection allowing the user with the FAST Manager's role to request them as they require them.
Mission Critical Any report that is a user report should not require a DBA to execute them. The receipt of the reports is considered critical to the success of DPAS being able to accurately report to FAST.
Benefits Eliminates the need for the FAST Manager to contact Leidos to execute the extracts each time they require them, as well as it eliminates the repeated receipt and running of the extracts by DPAS Leidos personnel.
Users This report would be limited to user who are granted the FAST Reports. |
|
|
01175 |
Manage Shelf Life By Expiration Date |
Warehouse |
SOCOM |
New |
Description The DPAS Warehouse module manages items subject to Shelf Life by CAGE, Mfr Contract, Mfr Lot and/or Mfr Date. Medical items that are subject to Shelf Life are is often managed by Expiration Dt. DPAS does not current support this method of knowing when an Item is no longer usable
Recommended Recommend the Warehouse module's Shelf Life methodology include the capability to enter and manage by Expiration Date.
Mission Critical Yes. Without this capability, SPECWARCOM is unable to manage items that have a shelf life of an Expiration Dt.
Benefits Does not require a separate to manage shelf life items that are managed by Expiration Dt
Users All user and all organizations that have Shelf Life items that are supported by an Expiration Dt. |
|
|
01174 |
Provide the Capability to Export the Pending Transactions Report in Excel |
PA |
SOCOM |
Done |
Description Currently the only option for printing the DPAS Pending Transactions Report is in PDF format. USSOCOM would like to export this report in the excel format to allow for sorting to be better able to manage and reconcile the transactions.
Recommended Provide the Pending Transaction Report to be exported in Excel Format.
Mission Critical Mission critical to perform daily reconciliation of transactions performed.
Benefits Tracking transactions in a timely fashion. Improves accountability.
Users All users within Agency.
Completed – Release 6.3 – 21 December 2018 |
|
|
01173 |
Modify Document Nbr System Settings |
PA |
SOCOM |
Done |
Description Today DPAS sets the way Document Nbrs are managed at the Agency Level. With USSCOM being a joint command, it provides support to all Services, thus the individual Service components have different requirements for Document Nbr Management.
Recommended Modify the level in which Document Nbr mgmt is maintained, and / or allow it to be flexible to support Agencies that are Joint where the Document Nbr requirements vary.
Mission Critical Mandated
Benefits This is required for Army components.
Users This will affect Army Components under SOCOM Agency as well as give other components the option to produce document numbers for updates.
Completed – Release 6.3 – 21 December 2018 |
|