System Change Requests Header

System Change Requests (SCR's) are submitted by our Configuration Control Board (CCB). To learn more about the process, please visit our CCB Responsibilities and Meetings page. Below you will find all SCR's that have been submitted, and what their status is. To download a blank form, you may visit our Reference Library and download the SCR Form.

Use the filter features on the left to sort by Agency (Reporting Organization), Module, or State. Use the open filter text box (above black header) to find key words in the description, or specific SCR number. Use the column title header to sort by that column. You may also download an Excel file of the record data by selecting the green Excel logo in the upper right corner of this page.

Filter 
Title SCR Number DPAS Module Reporting
Organization
State Description
Add Multi Year Maintenance Schedule Options 01820 MU USAF: AvSE New
Description:
Maintenance Schedules do not have an option to accommodate 2-year, 3-year, etc., inspection requirements.

Recommended:
Recommend creating a new Yearly type of recurring method for Maintenance Schedules, it could be Selected Month by Year. Recommend adding to account for inspection requirements of 2, 3, 5, and 10 years. Recommend the ability to select the day and the month and the interval of years for the Maintenance Schedule (i.e., 1 January every 2 years).
 
Mission Critical:
Mandated, There are several inspections required by manufacturers of equipment that are beyond a year. Many assets require a 2, 3, 5, or 10 year inspection to be completed.
 
Benefits:
There are several inspections that are on a biannual, 3 year, 5 year, or in some cases 10 year basis. It would greatly benefit the enterprise if Work Orders for these inspections were guaranteed to generate on the required day, regardless of when the last inspection was completed. This ability would ensure assets do not inadvertently fall off their inspection cycle. Currently the only way to create a Maintenance Schedule for more than one year it to use the Every X Days recurring method. This method does not guarantee a Work Order will generate on the same day every time it is due, as it generates the next Work Order based of when the previous Work Order was Completed. While it is possible to have Maintenance Schedules generate Work Orders before the Asset Next Maintenance Date, that still does not guarantee that a Work Order will generate on the first of the month that it would be due.  
 
Users:
This will affect all Aviation Support Equipment (AvSE) users within the Maintenance and Utilization (M&U) module.  It may affect users in other Site IDs if they have inspections based on yearly increments.
DPAS Depreciation Period FMR 7000.14R Review 01819 PA Leidos New
Description:
This SCR is for DPAS to review the FMR 7000.14R and compare the depreciation periods to what DPAS has, then update the depreciation periods in DPAS as required, except where a component has received an approval for a deviation from the value contained within the FMR.

Recommended:
Ensure DPAS depreciation periods are in agreement with the FMR.
 
Mission Critical:
Yes.  DPAS deprecation periods must be in alignment with the FMR.
 
Benefits:
Provides for accurate computation of depreciation.
 
Users:
Components / Agencies with capital assets
Retroactive User Activity 01818 Enterprise Leidos Done
Description:
Control activity 2.7 states “DLA Information Operations conducts an annual review of individuals with privileged operating system and database access and DPAS application security and admin user type access. The results of these annual reviews are documented, retained, and inappropriate access is removed. User Account Activity Logs are reviewed for accounts found to have inappropriate access, which is addressed in CA 2.10.”
• DPAS management does not retain evidence that demonstrates that the data used in the performance of the annual review of security and admin users is complete and accurate (i.e., screenshots of parameters/query used to produce the listing its entirety prior to execution within the query tool itself, screenshots of the row count within the query tool prior to extraction to demonstrate data wasn't lost or modified in transfer, etc.). Therefore, EY was unable to determine whether the data that was used in the performance of the annual access review of security and admin user types was complete and accurate. DPAS management is also not properly monitoring that all security and admin type users are properly reviewed. For users identified as requiring access to be removed during the annual review of privileged operating system and database access, as well as DPAS application security and admin user type access, DPAS management has not established a process to:
• Identify the length of time users had access but did not require it commensurate with their job responsibilities; and
• Analyze the activity for these users for that length of time, depending on the nature and risk of the roles held by the users (privileged, elevated-risk roles as identified by management.
 
Control activity 2.8 states: “DPAS PMO requires all IO/AIOs to submit an annual user review report. DPAS PMO performs user account maintenance based on this report. If no report is received by DPAS PMO by the designated due date, all accounts associated with the IO/AIO are deactivated.”
• DPAS management is not properly monitoring the user entity-performed access reviews. Specifically, Management is not verifying the completeness and accuracy of the user listings that are used in the performance of the reviews. Also, DPAS management does not perform a comprehensive retroactive review of activity for users identified with inappropriate access during each application user access review performed by Management or the user entity. Further, in their access reviews, Management has not established a process to:
• Identify the length of time users had access but did not require it commensurate with their job responsibilities; and
• Analyze the activity for these users for that length of time, depending on the nature and risk of the roles held by the users (privileged, elevated-risk roles as identified by management)
• DPAS management also does not have a process in place to properly monitor that the user entities are ensuring that all users that have access are properly reviewed.

Recommended:
Develop a stored procedure that can be used by DBAs to support retroactive user activity requests from IO/AIOs.
 
Mission Critical:
Mandated - This SCR is required to resolve a NFR in the FY22 SSAE audit.  
 
Benefits:
Passing the next SSAE audit.  
 
Users:
This process will be used mainly by the DBAs to support IO/AIOs requests.  
 
 

Completed – Release 2022.2.2 – 23 September 2022

Database Backup Monitoring 01817 Enterprise Leidos Done
Description:
Control activity 5.4 states: “DLA Information Operations personnel monitor the successful completion of database backup and document the results in a monthly MFR.”
• From October 2021 through May 2022 DPAS did not actively monitor the successful completion of database backups. DPAS researched database backup failures if they were notified of any through an automated notification process. DPAS was also unable to provide evidence demonstrating this control since database backup logs or database backup notifications were not retained.

Recommended:
Add a new table, Stored Procedure, and SQL Agent job to support the monitoring.
 
Mission Critical:
Mandated - This SCR is required to resolve a NFR in the FY22 SSAE audit.  
 
Benefits:
Passing the next SSAE audit.  
 
Users:
This process will be used mainly by the DBAs.  
 
 

Completed – Release 2022.2.2 – 23 September 2022

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 New
Description:
A review of the Federal Automotive Statistical Tool Vehicle - Level Data Business Rules Reference for 2022 is required with updates to DPAS as needed. eg. Manufacturer Names, Fuel Configuration data.
 
https://fastweb.inl.gov/files/static/vld/fast-vld%20business%20rules%20reference-v17-20220324.pdf

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
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.
 
Users:
This affects all DOD users.
Mfr Part Nbr FAST Reportable Indicator 01812 MU Leidos New
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.
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 New

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
MAM Mass Edit 01808 MU Leidos New
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
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 New
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
Deferred Tasks/Parts 01805 MU Leidos New
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
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 New

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.  

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.

Select Search Options

Reporting Organization

DPAS Module

State