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
Global Appsettings 01869 Enterprise Leidos New
Change Request: Process Improvement

Description:
Currently DPAS stores enterprise settings by module.  Enterprise settings should be the same throughout the system.  By storing them by module it's time consuming to maintain when a change is required, and requires a reconciliation to determine which one is correct when they are not the same.
 
Recommended:
Create a global settings file that can be consumed into each module for settings that should remain constant across the enterprise.
 
Mission Critical:
This change will improve the reliability of the system and reduce the effort to maintain the system.
 
Benefits:
System settings such as logging configurations, API URLs, and other environment specific variables will remain uniform throughout the system.
 
Frequency: Hourly
 
Users:
This change will ensure reliability for all DPAS users.
DLMS Modernization of Inbound 846 01868 Materiel Management Leidos New
Change Request: Process Improvement

Description:
DPAS currently utilizes several methods to inbound and process DLMS transactions. These methods are commonly nested in close proximity to other DPAS processes, resulting in maintenance and enhancement efforts to be difficult and in some instances it adds more risk than there needs to be of breaking other processes when a change is introduced. To address these issues, DPAS is proposes to centralized the DLMS logic into a standalone service. This technical  change will standardized the DLMS processing and logic with increased use of schema XSDs.
 
Recommended:
Design / develop a standalone DLMS Micro Service with a dedicated Database that interfaces with DPAS modules that utilize DLMS transactions.  The initial DLMS Micro Service will support the inbounding of the DLMS 846D, 846P, 846R, and 846S. There will be future SCRs submitted to support additional DLMS transaction sets.
 
Mission Critical:
DPAS Tech Refresh - DLMS
 
Benefits:
Reduces the time/cost to implement DLMS changes.  This change will increase throughput.
 
Frequency: Hourly
 
Users:
The DLMS 846* was flagged by DPAS Functionals for the initial fielding.
Inbound Volume, as of 1/1/2019: 184801 (846P), 497904 (846R), and 2 (846S)
DLMS Modernization of 846 Outbound 01867 Materiel Management Leidos New
Change Request: Process Improvement

Description:
DPAS currently utilizes several methods to outbound DLMS transactions, these methods are commonly nested in close proximity to other DPAS processes. The objective of this DPAS Tech Refresh it to centralized DLMS processing and provide a standalone Micros Service for DLMS. This SCR is to implement the change to support the out bounding of the DLMS 846* transaction sets.
 
Recommended:
Usage of standalone DLMS Microservice, that interfaces with DPAS modules, and handles the outbounding of the 846P, 846R, 846S, and 846D. Iterative roll out and deprecation of legacy code.
 
Mission Critical:
DPAS Tech Refresh - DLMS
 
Benefits:
Reduces the Time/Cost for implementing DLMS changes and improves the overall processing efficiency for outbound DLMS traffic.
 
Frequency: Hourly
 
Users:
The 846 was flagged by DPAS Functionals for high volume of bugs.
Outbound Volume, as of 1/1/2019: 3 (846P) and 58,066 (846R)
Create job to run WCUSS47 [Active Assets and 60 Days Inactive Assets] in PA 01866 PA Leidos New
Change Request: Process Improvement
 
Description: 
DPAS has a custom extract that provides data to the Army monthly.  It's a listing of active assets and the last 2 months of assets that have been dropped from DPAS .  The DPAS PM runs the real-time report and provides the data to the Army.  The DPAS PM is requesting that the data be sent to Advana, thus removing the DPAS PM from having to run the extract and deliver the information contained in the real-time report to the Army POC. The real-time report is WCUSS47 - Army Active Assets and last 2 Months of Inactive Assets.
 
Recommended: 
Eliminates manual run and delivery of the data.
 
Mission Critical: 
Improves efficiency
Does not require the DPAS PM to run and distribute the output / notify another person to run the job when they are out of the office.
 
Benefits: 
Improves efficiency
Does not require the DPAS PM to run and distribute the output / notify another person to run the job when they are out of the office.
 
Frequency: Monthly
 
 
Users: 
This is a business change in the delivery of the same data.  POC is Mr. Joseph Stossel.
Detail SKO ICN Report 01865 Warehouse Navy: NECC New
Change Request: New System Process

Description:
The ICN report does not provide the minimum amount of data fields to provide our NECC system (RCRP) with enough data fields to calculate readiness as the system is currently structured.
 
Recommended:
NECC requests the ability to extract known data from the ICN report, which would require an expansion of the fields currently available. The ICN report as it exists today can dive into the contents of SKO kits indicating that that data is already in the DPAS system. NECC is requesting a report that would show kit component stock#, Stock serial#, SKO#, SKO serial # and SKO secondary serial #
 
Mission Critical:
N/A
 
Benefits:
Provides line item data for readiness reporting.
 
Frequency:
Monthly
 
Users:
Minimum users at ECH III command when running the ICN report.
Add DoD Serial Number to WPMAR20R (report) 01864 MU USAF: AvSE New
Change Request: Process Improvement

Description:
DoD/Secondary Serial Number is the AF most commonly used equipment identifier within a maintenance shop.  Not having this identifier available on the report requires users to maintain a separate cross-reference sheet to convert DoD/Secondary Serial Number (not on the report) to asset Serial Number (on the report).    The Air Force uses the DoD Serial Number field for the legacy system identifier to ensure linkage to history in the legacy systems.  This number is also commonly stenciled or etched onto the equipment for easy visibility and identification.
 
Recommended:
Add DoD/Secondary Serial Number to the Upcoming Maintenance Schedule report (WPMAR20R).
 
Mission Critical:
AFI 21-101, Aircraft and Equipment Maintenance Management
 
Benefits:
More accurate maintenance documentation, quicker identification of equipment requiring inspection.  Easier and quicker leadership briefings on upcoming maintenance (a policy requirement).
 
Frequency: Daily
 
Users:
~10K users affected
DLMS ASC 1428 (856S Transaction Type Code AZ) 01863 Enterprise Leidos New
Change Request: Policy/ Regulatory

Description:
The DLMS Approved Standards Change (ASC) 1428 eliminates the use of the DLMS 856W and incorporates the functionality within the DLMS 856S Implementation Convention.  DPAS requires a change to the generation of the DLMS 856S Shipment Status to support the turn in of Hazardous Materiel that is identified with in DLMS ASC 1428.
 
Recommended:
Add new Transaction Type Code to the DLMS 856S generation process: AZ (Disposal Shipment Advice) - Use to indicate this transaction provides Hazardous Material/Hazardous Waste shipment status information for turn-in of material to DLA Disposition Services.  In addition to supporting the new Transaction Type Code, DPAS will need to incorporate the additional elements required for this transaction type within the DLMS 856S transaction.
 
Mission Critical:
 
Benefits:
Required for the submission / notification of a shipment of materiel to DLA Disposition Services.
 
Frequency: Daily
 
Users:
DPAS generates DLMS 856S from the following applications:  Property Accountability, Warehouse Management and Materiel Management.   No research has been conducted to determine how many user are turning in materiel that is classified as being Hazardous.
Add DLMS ADC 1422 to ICP 01862 Materiel Management AF: GFM-A New
Description:
DLMS ADC 1422 revises the DLMS 832N Catalog Data transaction and adds a new qualifier to identify the procurement instrument identifier (PIID) authorizing the contractor to perform work on behalf of the government.  
 
Recommended:
With DPAS current support, the Air Force CICP programs are required to record the authorizing contract when transmitting materiel master records via the DLMS 832N.  This qualifier mirrors the DLMS 947I, Inventory Adjustment Transaction to ensure consistency.  Recommended Solution - update the DPAS processing logic to accept, store and update the PIID transmitted by the DLMS 832N transaction.  In addition to updating the DPAS catalog, the processing logic should associate the new stock number to the AF CICP/GFM contract number.
 
Mission Critical:
Yes - This SCR requires implementation for inventory accountability and to accurately report the financial value of the inventory held by the contractor.  This SCR is being submitted to implement DLMS ADC 1422.
 
Benefits:
The benefits of this SCR fix a material weakness resulting from inability to transmit and receive the authorizing contract via the DLMS 832N.  The authorizing contract is a data element required by DoDI 500.64 section 4.6.  
 
Users:
ALL AF GFM-A users of DPAS
DPAS Health Monitor 01861 Enterprise Leidos New
Change Request: Process Improvement
 
Description:
Current detection and notification of problems in the DPAS system is handled by code within the applications and users that may report problems they encounter.  We propose to augment these methods by adding an automated process that will routinely check the health of the applications in the DPAS system.
 
Recommended:
Create a health monitor that will regularly check the health of DPAS applications.  A UI will also be made available in non-production environments to allow DPAS developers to view the health of monitored applications and details of health checks.
 
Mission Critical:
Health monitoring is generally accepted best practice for web applications.  According to Microsoft: "If services cannot send some sort of "I'm alive" signal, either on demand or on a schedule, your application might face risks when you deploy updates, or it might just detect failures too late and not be able to stop cascading failures that can end up in major outages."  See full article: https://learn.microsoft.com/en-us/dotnet/architecture/microservices/implement-resilient-applications/monitor-app-health

 
Benefits:
Improved reliability.  The monitor will not be user facing, but it affects the DPAS modules the use by reducing the effects of slow-downs and service interruption.
 
Frequency: Hourly
 
Users:
The frequency of system health checks will be based upon the experience identified in its use. DPAS anticipates that if there if value that each service and web site may be checked every minute or couple of minutes depending on the check's efficiency and system performance. This tool is not a DPAS User Interface object.  It's intended user base are DPAS Support personnel.

DPAS to NAVAIR Data Interface 01860 Enterprise Navy: NAVAIR New
Change Request: Process Improvement

Description:
Currently NAVAIR (Command Property Office) receives a monthly file from DPAS and manually processes the data
 
Recommended:
We would like to either set up a direct data feed to DPAS where we can pull a weekly table of the requested data fields or set up a weekly file drop of the requested fields to our server so we can use our extraction tool to import the data into our data warehouse.
 
Mission Critical:
Our goal is to automate this data transfer for the Command Property Office at NAVAIR to minimize man hours and increase efficiency.
 
Benefits:
This will minimize man hours spent processing these files and improves accuracy when analyzing the data for the end user. The DPAS data is being used for monthly inventory scorecards. The value of inventory is being visualized in Qlik for monthly and yearly trend and is also used for POG Billings to PMAs by the CPO. It will also be used for our warehouse consolidation effort and COOPER storage locations updates.
 
Frequency: Weekly
 
Users:
 
20+ users but we hope for that to grow once the way we process this data becomes easier.
Maintenance Schedule/Work Plan System Update 01859 MU AF: AvSE New
Change Request: Process Improvement

Description:
Problem: When Work Orders are closed that are comprised of Work Plans that are shared across multiple Maintenance Schedules, DPAS does not know which Maintenance Schedule to update and therefore updates all. This in turn, will cause DPAS to not generate Work Orders on required inspections and reflect inspections as being accomplished that have not been accomplished.  This is a critical safety issue.
 
Recommended:
Create a switch or drop down menu at the Program (Maintenance Director) level to ensure only the maintenance schedule associated with a work order is updated when the work order is closed.  
 
Mission Critical:
None Provided
 
Benefits:
With the ability to only update Maintenance Schedules whose Work Orders that were generated from that Maintenance Schedule are completed, It ensures inspection integrity. This will also eliminate the issue users are having with duplicate Work Orders or Work Orders not generating at all. Finally, this will eliminate the major safety implication that are currently present.  
 
Frequency: Daily
 
Users:
Thousands of times a day across the enterprise.
Expand MU User Preferences 01858 MU AF: VSCOS New
Description:
DPAS work order processing can involve entering repetitive information across multiple sections or sub work orders. User can experience selecting the same option multiple times when adding, updating or closing a work order. Having to repeat the process adds task time and increases processing errors.
 
Recommended:
Expand default options under User Preferences:
1. Add preference search criteria for work plan browse within work order; use radio button for Other Activity Plans.  When selected the My Plans toggle will default to off (grayed out) when the user preforms a work plan browse to add or update work orders.
2.  Add preference for default Work Order State Code when adding a sub work order.  User would select a preference from drop-down menu listing available Work Order State Code options.  When the preference is set, the Work Order State Code pre-populates when adding a new sub work order. User can then change the Work Order State Code as needed if default does not apply to specific work order.
3.  Add preference for default Work Order State Code when closing a work order. User would select a preference from drop-down menu listing available Work Order State Code options. When the preference is set, all Work Order State Codes will default to the user preference when the Work Order Status Code is changed to C – Closed. User can then change the Work Order State Code as needed if default does not apply to specific work order.
 
Mission Critical:
Accurate work order processing is critical to data integrity and reporting to FAST, DRRS and other systems.  
 
Benefits:
This change will reduce task time, need for work order processing as well as increase data accuracy by reducing repetitive entry.  
 
Users:
This improvement will benefit the Department of the Air Force and all other DoD Agency's
Create Deferred Parts option with Open Maint Issue 01857 MU AF: VSCOS New
Description:
Department of the Air Force (DAF) vehicle enterprise's maintenance activities have a need to delay a sub-work order task and/or defer parts, but require the warehouse maintenance issue to remain open.  Although the part is deferred, the maintenance issue still must process and hold part(s) for future use (e.g., installation of vehicle).  Currently, the system will move the maintenance issue to DE-Deferred status when deferring the sub-work order.  This effectively cancels the maintenance issue as no further action is possible within DE-Deferred status.  This action eliminates the demand signal within the system and requires the maintenance technician to externally communicate with the warehouse to ensure the requisition is fulfilled for future use.
 
Recommended:
Create an option to cancel a work order requisition and defer the part(s) with an open maintenance issue.  When selecting this option the maintenance issue links to the work order, updates to DE-Deferred and creates a new maintenance issue linking to the asset id.  New maintenance issues unlinked to a work order would indicate the need to complete the pick process or create a backorder for installation after receipt.
 
Mission Critical:
This is critical to ensure fleet readiness by eliminating supply chain disruptions.  Delaying fulfillment of a maintenance issue compounds long lead times within part acquisition.  
 
Benefits:
This change will reduce task time, need for work order processing as well as increase data accuracy by reducing repetitive entry.  
 
Users:
This improvement will benefit the DAF and all other DoD Agency's
Eliminate DLMS 870s for TPFs 08156 Materiel Management Army: ASA(ALT) New
Change Request: Process Improvement

Description: 
ASA(ALT) utilizes the Materiel Mgmt. module to perform Total Package Fieldings (TPFs).  When a push customer requisition is entered / approved, DPAS will generate / send a DLMS 870S Supply Status along with a DLMS 527D  Prepositioned Materiel Receipt to the recipient of the intended recipient of the materiel.  The DLMS 527D is determined by the customer profile while the DLMS 870S is automatic as if the push order was a pull order with DPAS responding to the receipt of a DLMS 511R. Army is encountering an issue when the DLMS 527D is not transmitted (customer profile incorrectly established), or when the 527D is rejected by GCSS-Army. When the DLMS 527D is not received / processed and a DLMS 870S is received, GCSS-Army will establish a Due In and transmit a DLMS 511R to National for the purchase of the materiel that is to be provided by the PEO/PM.
 
Recommended:
Army is requesting that DPAS not generate DLMS 870S Supply Statues for TPF type orders.  The Supply Status is not needed and results in the generation of an order when there isn't one desired.  All TPF activity is supported by the DLMS 527D Prepositioned Materiel Receipt (PMR).  Should the PM change the qty or cancel the order DPAS sends the change via an updated PMR (DLMS 527D).
 
Mission Critical:
This functionality is needed to prevent unwanted orders being generated to national when the DLMS 527D prepositioned receipt is not received / processed.
 
Benefits:
This change will eliminate unwanted orders being systematically generated by GCSS-Army.
 
Frequency: Daily
 
Users:
This feature will be utilized by the ASA(ALT) PMs in fielding of the next generation of equipment to the U.S. Army and by USSOCOM for push orders to their customers.
DPAS Sub-Warehouse / Shop Code and DLMS 01855 Warehouse Leidos In Progress

Change Request: Process Improvement


Description:

Currently each DPAS warehouse is required to have a unique RIC (Mandatory when external reporting is required) and / or DoDAAC. This value is used for routing DLMS transactional data between DPAS Warehouse Mgmt. and DPAS Materiel Management Mgmt. modules and to / from external systems. There are times where a DPAS Customer has an organization that has a requirement for multiple warehouses to manage different commodities that is not desired to have them commingled e.g. spare parts, tool crib, un-issued materiel with no avenue to acquire additional RICs. Note: The Department is running out of 3 character RICs with plans to replace the RIC with DoDAAC once logistics system are fully DLMS compliant (eliminate support for MILS format).


Recommended:

The proposed change will have DPAS implement the Planning / Maintenance Organization (Shop Service Center) name value as part of the warehouse business key. By including this value, DPAS will be able to use this value along with a RIC / DoDAAC to route DLMS transactions enabling an organization to have multiple warehouses without having each of them having a unique RIC / DoDAAC.


Mission Critical:

This change will enable an organization to have multiple DPAS warehouses which will enable them to have multiple Tool Cribs, Parts/Supply Rooms, Issuing locations, etc.


Benefits:

This SCR is identified as phase 1 of the DPAS effort to add flexibility to its Warehouse Mgmt. module. With this change DPAS customers will be better able to manage its different types of inventories / different physical locations within an organization. Additional efforts are planned to provide greater flexibility in configuring a DPAS warehouse.


Frequency: Daily


Users:

Currently SPECWARCOM and the Air Force has multiple warehouse requirements within a organization.

 

 

Partially Completed – Release 2023.1.1 – 13 January 2023

Partially Completed – Release 2023.1.2 – 27 January 2023

nformation Owner User Account Request Submission 01854 Enterprise Leidos New

Change Request: Process Improvement


Description:

DOD has issued an updated DD Form 2875 that requires changes to the DPAS validation / import process. With the increased number of users to manage, to have DPAS personnel preform the validation, then report the error(s) to the security POC delays a new user in receiving an account. The proposed improvement is to provide capability for Information Owners that have an active DPAS account to perform the validation enabling DPAS to provide immediate feedback to the information owner as to what needs to revised, and the change would enable the information owner to submit the validated DD Form 2875 for processing.


Recommended:

DOD has issued an updated DD Form 2875 that requires changes to the DPAS validation / import process. With the increased number of users to manage, to have DPAS personnel preform the validation, then report the error(s) to the security POC delays a new user in receiving an account. The proposed improvement is to provide capability for Information Owners that have an active DPAS account to perform the validation enabling DPAS to provide immediate feedback to the information owner as to what needs to revised, and the change would enable the information owner to submit the validated DD Form 2875 for processing.


Mission Critical:

DOD has issued an updated DD Form 2875 that requires changes to the DPAS validation / import process. With the increased number of users to manage, to have DPAS personnel preform the validation, then report the error(s) to the security POC delays a new user in receiving an account. The proposed improvement is to provide capability for Information Owners that have an active DPAS account to perform the validation enabling DPAS to provide immediate feedback to the information owner as to what needs to revised, and the change would enable the information owner to submit the validated DD Form 2875 for processing.


Benefits:

Allow more efficient account creation and modification for both customers and account management staff.


Frequency: Daily


Users:

DPAS processes 1000s of DD Form 2875 yearly.

Additional Details for FSM Auth On-Hand Report 01853 FSM AF: A4/HAF FH-AFHAF New
Change Request: New System process

Description:
Current FSM Auth On-hand report does not auto populate the the Master NSN in the NSN column when running a report with the Interchangeable or Substitute NSN. Additionally FSM Auth on-hand capability can only be submitted as report and limits filtering data elements to only being able to run a report one NSN at a time. The current 'work around' is to run a report at either the MAJCOM, AUIC, UIC level to see all the NSN. UIC selection requires the user to scroll to find the UIC they
 
Recommended:
Populate the Master NSN in NSN column, regardless if the inquiry is for the Interchangeable or Substitute NSN. Include in the Pop-up screen for the search stock number a notice if the NSN is a Interchangeable or Substitute to a Master NSN. Allow to run reports for multiple NSN, UICs, Auth-id etc.  Include intelliSense capability for all search by data elements
 
Mission Critical:
Current process is limited and requires more robust capabilities
 
Benefits:
This will provide the DAF the capability to make data driven decisions for the management and oversight of Support Equipment.
 
Frequency: Hourly
Users: [blank]
Modification of LIMS-EV interface to support M&U changes 01852 MU Leidos New
Change Request: Process Improvement

Description:
With the modernization of M&U, in addition to asset linkage between PA and M&U, user can direct input asset into M&U and there will be an eventual asset linkage between WM and M&U.  To support these changes along with supporting a micro-service framework, the linkage of the Maint. Asset Master / Work Orders are no longer a direct association to Asset Master.  Reference DPAS Ticket Nbr - 78525  
 
Recommended:
Modify the LIMS-EV interface to incorporate an Equipment Master view and modify the linkage between various other LIMMS-EV views to utilize the Equipment Master view.
 
Mission Critical:
DPAS change how Maintenance records are linked to their source.
 
Benefits:
This is considered a mandatory change in order to maintain data integrity within the LIMS-EV views.
 
Frequency: Hourly
 
Users:
All consumers of the LIMS-EV interface data.  Currently this is AF Discovery and DoD Advana.
Impound Asset Manager 01851 MU USAF: AvSE New
Change Request: New Role Design

Description:
Problem: Not currently able to lock down an asset in DPAS M&U when asset is impounded as directed by DAFI 91-204, Safety Investigations and Reports. This inability allows for the potential of users to change/update asset information in the system while the asset is still under investigation, causing a major safety and records management issue.
 
Recommended:
Create a new Impound Official role within DPAS M&U and add a check box to the Maintenance Asset Master screen labeled as "Asset Impounded".   Selection of this check box by an authorized person will "lock out" all other users and lock all asset history while the asset is impounded. Once asset is released from impound, an authorized user will unlock this asset and it will be available for normal use/maintenance. Limit use of the new Asset Impounded check box to only the newly created Impoundment Official role.
 
Mission Critical:
Mandated by DAFI 91-204, Safety Investigations and Reports, and DAFI 21-101, Aircraft and Equipment Maintenance Management.
 
Benefits:
The addition of this role will allow for proper control and integrity of asset historical data within DPAS M&U and will make DPAS M&U compliant with Aircraft/Equipment impoundment procedures. This additional role and ability will also address safety concerns, by not allowing use when an asset condition is questionable or under investigation.
 
Frequency: Monthly
 
Users:
Hard to measure, possibly several times a month.
Add SubWO Fields to WO Search Results Grid 01850 MU USAF: AvSE New
Change Request: Process Improvement
 
Description:
Problem: Currently when users search Work Orders, the results that populate do not give specific enough information on what the Work Order is for.
Proposed Improvement: Addition of Sub-Work Order specific columns to Work Order search results grid.  
 
Recommended:
Add an additional option to display Sub-Work Orders for each Basic-Work Order. Include fields that display Requested Service and Work Order Description.
 
Mission Critical:
(Not Provided)
 
Benefits:
The addition of these fields will save users time and aggravation, as when they are searching for a specific Work Order they are searching for the narrative of the work to be accomplished (i.e., 6 Month Inspection). The average user will not know the Work Order Reason, Work Order State Code, or Work Plan Type Code. Therefore, if there are several open Work Orders on a single asset (a common occurrence), users will have to click on all the search results until they find the specific Work Order they are looking for, this proposed improvement will solve that issue.
 
Frequency: Hourly
 
Users:
This function will be used by all AvSE users in DPAS M&U thousands of times a day.

Select Search Options

Reporting Organization

DPAS Module

State