|
Add Fields to Inventory Activity Inquiry
|
01816
|
Warehouse |
USMC |
New |
Description:
Currently there is no requisition number, DTID, Disposition Reference Number, Warehouse Transfer Shipment Reference Number, and Warehouse Issue Request Number column in Inventory Activity.
Recommended:
For Audit purposes and causative research recommend that the requisition number, DTID, Disposition Reference Number, Warehouse Transfer Shipment Reference Number, and Warehouse Issue Request Number column be added to Grid Option columns in inventory activity.
Mission Critical:
Yes this will help with audit purposes and causative research to be able to show the requisition numbers for all stock numbers on a DD1149 instead of searching for document numbers for each stock number.
Benefits:
Having this functionality will help from having to go through multiple steps to get the information we need for Audit Purposes.
Users:
All IIF/UIF |
|
Custodian Attachment
|
01815
|
PA |
DoDEA |
New |
Description:
Asset custodians are required to be designated in writing and supporting documentation is encouraged by the DOD to be retained electronically. Currently, the DPAS Warehouse Module allows users to attach document to custodians, however, the Property Accountability module does not. Having the ability to attach Custodian designation letters and Custodian turnover forms to a Custodian in DPAS PA would ensure retention and allow for significantly easier remote audits and inspections.
Recommended:
Add the option to include an attachment when adding or updating a Custodian, similarly to what already exists in the Warehouse Module.
Mission Critical:
Custodians are required to be designated in writing and DOD encourages electronic storage of all Key Supporting Documents. Having the option to upload custodian letters to the applicable custodian would consolidate the documentation and meet any future electronic storage requirements.
Benefits:
This change will enable DoDEA, as well as other services, to efficiently retain the required custodian designation letters electronically in the same system as the relevant property record. This will also improve auditability by making it easier to access the documentation remotely reducing the time/effort required when this documentation is requested.
Users:
This affects all DOD users. |
|
DPAS FAST Updates 2022
|
01814
|
MU |
Leidos |
Done |
Description:
Recommended:
Review current FAST Vehicle-Level Data Business Rules Reference and perform the required updates to DPAS.
Mission Critical:
Mission Critical - The review / updates are necessary to ensure the DPAS edits are current to ensure successful reporting of FAST reportable assets for FY22.
Benefits:
Improves accuracy and accountability
Users:
ALL
Completed – Release 2022.3.1 – 18 November 2022 |
|
Add Attachment to Transfer Process
|
01813
|
PA |
DoDEA |
New |
Description:
Add a file upload feature during the transfer of equipment transaction. Unable to add/upload a file during transfer transactions.
Recommended:
Add the option to include an attachment when Transferring, adding or updating assets.
Mission Critical:
Yes. DOD encourages electronic storage of all Key Supporting Documents. Having the option to upload transfer documents would consolidate the documentation and meet any future electronic storage requirements.
Benefits:
This feature will improve transfer processing time. This will allow the PBO to upload the file during the transaction avoiding going back after transferred and do an asset update after transfer to upload the file.
This affects all DOD users. |
|
Mfr Part Nbr FAST Reportable Indicator
|
01812
|
MU |
Leidos |
Done |
Description:
During the 2022.2 customer maintenance demos, the customers expressed a desire to have FAST reporting defined corporately rather than allowing each Maintenance Activity have the capability to establish the determination. Today, the catalog team has a FAST indicator within the Mfr Part Nbr process. When set to Yes (system defaults to Yes when ACC = P, but user can override the setting) When the FAST Indicator is Yes, the system forces the user to select a FAST Mfr Name. Currently the indicator is not an attribute, thus there is no true positive confirmation that the asset is FAST reportable. Example: User could set it to No and then enter a Mfr Name such as "GM" which is a valid FAST Mfr value.
Recommended:
Add a FAST Indicator value to the Mfr Part Nbr table to identify assets associated with this mfr part nbr record, that the asset is FAST reportable. Update the process to populate the value, add to grid / inquires, reports. Sync Fast Indicator with M&U. Modify logic in M&U for determining FAST reportable assets.
Mission Critical:
This change will enable DPAS to validate the asset is FAST reportable at the Mfr Part Nbr level.
Benefits:
Improves accuracy for FAST Reportable assets. Eliminates Maintenance Activities being able to not report commercially designed vehicles.
Users:
Nearly All - Most components / agencies that utilize DPAS have commercially design vehicles that required FAST reporting.
Partially Completed – Release 2022.3.1 – 18 November 2022
Completed – Release 2023.1.1 – 13 January 2023 |
|
Multiple Location Condition Code per Stock Number
|
01811
|
Warehouse |
AF: DF-VEHS |
New |
Description:
DPAS Warehouse limits Location Condition Code for a stock number to one Location Id. When receiving multiple quantities of a stock number under a single document, all will default to the single location and then need dispersal to various locations. Each warehouse will have multiple locations that require the same stock number and have a single Due-in, Backorder, or Return created to replenish or restock the items.
Recommended:
Allow multiply Location Condition Codes for same stock number. Enables user to chose several locations by quantity they would like to receive/return stock numbers streamlining process.
Mission Critical:
This is not critical or mandated, however improving system efficiencies decreases time warfighter spends performing non-wartime tasks
Benefits:
Automation provides a time reduction searching commonly received stock numbers for warehouse location replenishments (e.g.,individual issues). Additionally, potential to eliminate or reduce misplaced items within warehouse. Allows warfighter to focus on critical mission tasks vs. assigning warehouse replenishment locations.
Users:
ALL Warehouse |
|
DBO Table Deprecation
|
01810
|
Enterprise |
Leidos |
New |
Description:
Currently DPAS duplicates catalog information across two separate database schemas which are kept in sync through the use of triggers. The planned improvement is to replace the triggers with views of the source tables to support catalog data within the PA / MU environments.
Recommended:
The catalog tables within the dbo schema will be removed and replaced with a synonym and view to allow the data to be accessed directly from the catalog schema within DPAS. This will ensure no data needs to be synced to the tables referenced by the PA/MU processes and they can function as they do today.
Mission Critical:
Mission Critical. DPAS should not be duplicating data in the system. Proposed changes will increase catalog process performance and ensure consistency of catalog data system wide.
Benefits:
DPAS will improve accuracy and accountability by ensuring consistency of data within the catalog
Users:
This change will impact/benefit all catalogers within DPAS |
|
Work Order Mass Edit
|
01809
|
MU |
Leidos |
In Progress |
Description:
The initial DPAS modernization of M&U limited Work order provided single work order update. DPAS needs to restore the mass Work Order Update.
Recommended:
Allow for the selection of multiple work orders and enable edit of the selected group of work orders as one transaction.
Mission Critical:
Mission Critical - users need the ability to make the same edit to multiple work orders at once to reduce error and increase productivity.
Benefits:
Reduces Time and Cost associated with making the same edit multiple times for different work orders
Users:
All
Partially Completed – Release 2022.3.2 – 02 December 2022
Partially Completed – Release 2023.1.1 – 13 January 2023
Partially Completed – Release 2023.1.2 – 27 January 2023
Partially Completed – Release 2023.1.3 – 10 February 2023
|
|
MAM Mass Edit
|
01808
|
MU |
Leidos |
In Progress |
Description:
The DPAS modernization initially provided for the user to input 3 parameters when mass profiling assets within the Maintenance Asset Master process. The capability to mass profile all fields that the previous version of the Maintenance Asset Master process had needs to be implemented. .
Recommended:
Add the remaining parameters to the mass update capability
Mission Critical:
Mission critical - DPAS users need the ability to update multiple records at one time beyond the three parameters currently available
Benefits:
Reduces time/cost associated with requiring individual edit on numerous MAM records
Users:
All
Partially Completed – Release 2022.3.3 – 16 December 2022
Partially Completed – Release 2023.1.3 – 10 February 2023
|
|
ServiceNow DPAS Interface
|
01807
|
Enterprise |
USAF FF-GEIT |
New |
Description:
The EITaaS IPO has asked our SAIC partners, as a part of our Risk Reduction Effort, to demonstrate that they can integrate with DPAS and leverage ServiceNow (Our approved system of record) to do asset management across the EITaaS portfolio.
Recommended:
The primary and preferred method to interface with DPAS is via REST (JSON payload) or SOAP (XML payload) over a secure HTTPs connection (TLS 1.1v or greater). A diagram has been provided/is attached with this SCR from the EITaaS SAIC team.
Mission Critical:
Development of this interface was mandated by the EITaaS IPO.
Benefits:
A ServiceNow input going to DPAS is requested to provide accurate records for asset management.
It also helps the Air Force by reducing our staffing needs for the asset management process.
Users:
Yes, this will be an interface to provide all data from the FF-GEIT site to ServiceNow.
|
|
Support for Warranty & Service to M&U Work Order
|
01806
|
MU |
Leidos |
In Progress |
Description:
Provide the ability to associate warranties, subscriptions, or service contracts to an asset and display the contracts within Work Order when the asset is used.
Recommended:
Create a Warranty/Subscriptions service that can be used to create a Warranty/Service/Subscription contract and then allow for the contracts to be associated to one or many asset ids within maintenance. When an asset id that has Warranty/Service/Subscription contracts associated is used for a Work Order display the contracts in a Warranty/Service/Subscription panel within the work order so the user can view the contract terms.
Mission Critical:
Mission Critical. Numerous assets fall under warranty/subscription/service contracts that effect the types of work that will be done within a specific work order. Having this information available within the work order process will ensure the proper maintenance of assets.
Benefits:
Enables user awareness to specific warranties/service/subscription contracts that may limit the scope of a work order and ensure proper maintenance of the assets within a Maintenance Activity.
Users:
ALL
Partially Complete - Release 2022.2.3 - 07 October 2022 |
|
Deferred Tasks/Parts
|
01805
|
MU |
Leidos |
In Progress |
Description:
Work Orders cannot be closed when it includes outstanding parts requests. Allow for a work order that includes outstanding parts requests to be closed, and maintain the requirement for the outstanding parts for the associated Asset for future work orders.
Recommended:
Allow the user the ability to defer a task and select the outstanding parts that are no longer needed as a result of the deferred task. Maintain a record for the Asset ID of the tasks/parts that were deferred and alert the user of these deferred tasks on future work orders where the same Asset ID is used and allow for them to be added for the new work order.
Mission Critical:
Mission Critical. Priority for specific parts requests can change after a work order has been created to request those parts even while the parts are still needed. Without the ability to defer parts request either the Work Order would need to remain open and inhibit use of the associated asset or it would need to be closed and the part requirement would be lost.
Benefits:
Improves the use of the Work Order process to accommodate changes in demand of Assets in relation to the priority of parts requests. This part of the DPAS modernization effort.
Users:
Maintenance & Utilization - Work Order
Warehouse Mgmt - Maintenance Issue
Requisition Partially Completed – Release 2022.3 – 04 November 2022
Partially Completed – Release 2023.1.3 – 10 February 2023 |
|
Add asset ID and corrected cost to DD Form 1150
|
01804
|
Warehouse |
USAF |
New |
Description:
When completing a maintenance issue within DPAS Warehouse, the DD Form 1150 does not show asset ID or reflect correct unit price. Unit price corrections are made within maintenance issue pick process if necessary and remarks added. Asset ID display within asset ID block and correct unit price on form ensures proper documentation. Additionally, the DD1150 block 5 Request Number reflects the M&U Work Order Id and block 7 Document Number reflects the Parts Request number. These fields do not directly translate to data fields within the M&U and Warehouse module.
Recommended:
Update the DD1150 process to reflect the following: Block 9 (2) Asset Id – populate with the Asset Id from the M&U work order Block 9 (8) Unit Price – populate with the Unit Price adjustment during the pick process Block 5 Request Number – populate with the Part Request or Document Number from the Warehouse Maint Issue Block 7 Document Number – populate with the Work Order Id number from M&U requisition
Mission Critical:
It is critical to capture accurate data when documenting expenditures against assets within the M&U and Warehouse module. Agency sustainment budgets based on data within DPAS.
Benefits:
Having the DD1150 capture accurate data improves budget auditing expenditures and asset life cycle sustainment cost documentation. Auditing ensures financial reporting accuracy and creditability for Department of the Air Force (DAF) budget requirements.
Users:
This affects all Agency's and we believe this function will benefit all. |
|
DLMS Quarantine AUD
|
01803
|
Enterprise |
Leidos |
New |
Description:
DPAS developed a DLMS Quarantine process that enables the DLMS processor to bypass specific DLMS transactions based upon the the Transaction Set Nbr and Sender. The quarantine process is currently managed through scripting. Scripting is a slow method to add / remove items to the quarantine list when the DLMS queue fills and requires immediate attention, and there is currently no visibility of what is in quarantine without executing a script. |
|
DPAS .NET Core 6.X updates
|
01801
|
Enterprise |
Leidos |
Done |
Description
Microsoft has announced the end of life "EOL" for 3.1 .NET Core as 12-13-22. DPAS has templates that are using this version that will need to be updated to the .6 NET Core version (current) .6 NET Core has a targeted end of life date of 11/12/2024.
Partially Completed – Release 2022.3.1 – 18 November 2022
Partially Completed – Release 2022.3.2 – 02 December 2022
Completed – Release 2023.1.3 – 10 February 2023 |
|
Custodian Attachment
|
01800
|
PA |
Navy |
New |
Description:
Asset custodians are required to be designated in writing and supporting documentation is also required to be uploaded to the APSR. Currently, DPAS does not allow attachments when adding or updating a Custodian. Having the ability to attach Custodian designation letters and Custodian turnover forms to a Custodian in DPAS would solve this issue.
Recommended:
Add the option to include an attachment when adding or updating a Custodian.
Mission Critical:
Yes, Custodians are required to be designated in writing and supporting documentation is required to be uploaded to the APSR.
Benefits:
existing policy. This will also improve auditability by making it easier to access the documentation remotely which will also reduce the time/effort required when this documentation is requested.
Users:
This affects all NAVY and DODEA users and likely other services that use the Property Accountability Module in DPAS. |
|
Data Request Timestamp Addition
|
01799
|
Enterprise |
USMC |
New |
Description:
After reviewing the DPAS tables within EGEM and the MDR, they are not the same as to what we are being provided. We are being provided an inventory file which contains all material that the Marine Corps owns within DPAS regardless of Program. We are requesting 2 additional Datasets that are being provided to the MDR ( DPAS_INVENTORY and DPAS_INV_ACTIVITY). As well as an activity report that coincides with the new DPAS ASSET dataset. |
|
DPAS Account lock ability for Annual User Audit
|
01798
|
Enterprise |
Leidos |
New |
Description:
For accounts that are suspended due to non-compliance of the Annual User Audit, we do not have a way to lock these accounts from being reset until is appropriate. When user accounts are suspended (active box unchecked) because the IO group has not provided a response for the Annual User Audit, there is nothing preventing Help Desk support from being able to reset the account unknowingly. I am proposing a lock feature or new status ability be given to assist Security Officers with audit compliance. The Help Desk should retain their currently ability to reset accounts; however, we also need a method that allows for Sec Officers to lock particular accounts that can only be unlocked by a Sec Officer.
Recommended:
Provide ability to lock certain user accts from being reset until IO completes Annual User Audit. Potentially a new status or lock feature that only Security officers could update those particular accounts back to active status when appropriate.
Mission Critical:
This functionality supports audit readiness.
Benefits:
The solution supports audit readiness and user review compliance so that users do not get access to their account before they should.
Users:
This change would impact internal support staff. |
|
UIC Update and Migration Request
|
01797
|
PA |
USSOCOM |
New |
Description:
Current PA Module design does not allow for users to delete UIC's that were entered incorrectly, or to migrate/mass move UIC's from one Parent Structure and Accountable UIC to another.
Recommended:
Add capability in Property Management to perform UIC movement/migration, similar in concept to a Task Force Update process. This process will allow users with the proper roles to update/edit/delete/re-align UIC's. This will allow for organizations to transfer UIC's to a gaining organization without the need to laterally transfer items one at a time to the same unit that now falls under a different organization structure. Develop ability to delete UIC's entered incorrectly that have no assets assigned to them. Add capability to Update UIC assignment Major Command Codes
Mission Critical:
This is critical to using organizations such as the AFSOC community which has been re-organizing it's unit assignments.
Benefits:
The benefit is a reduction of bad data (UIC data tables) in the PA structure and the ability to rapidly re-assign UIC's and migrate the equipment and custodial data over to a new APO with no data loss. This will enable units deploying on short notice to re-align rapidly as needed.
Users:
This will apply to all users in the DPAS community that use the existing PA Module to account for their unit assigned equipment. This SCR request is related to the existing USAF SCR 01627. SOCOM is requesting additional UIC update capabilities than the originally requested. This change will also benefit the USAF and any other users of the PA Module |
|
Time Stamp Addition
|
01796
|
PA |
USMC |
New |
Description:
The current dataset name requires our folks to do a lot more coding to place the correct date with each record as its ingested. Because of this when there are issues on our side and ingestion is delayed, then we have to have very specific code to put in the appropriate date, meaning it’s no longer automated.
Recommended:
Looking to add a File_date_timestamp to each record when DPAS produces the dataset, per line item within the dataset as the last column.
Mission Critical:
Critical. This would benefit various users across spectrum
Benefits:
The current dataset name requires our folks to do a lot more coding to place the correct date with each record as its ingested. Because of this when there are issues on our side and ingestion is delayed, then we have to have very specific code to put in the appropriate date, meaning it’s no longer automated. Additionally, this will provide a higher level of confidence in knowing what date the dataset was truly produced.
Users:
This affects all users |
DPAS Support
Defense Property Accountability System