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.

Enter your SCR Number in the filter below, or click the column title header to sort by that column. You may also download an Excel file of the record data by selecting the blue Excel logo in the upper right corner of this page.

Filter 
SCR Number Title DPAS Module Reporting
Organization
State Description
01995 Add Issue DoDAAC and Mfr Part Data to Inquiries Warehouse New
Change Request: Process Improvement

Description:
Currently there is no "one" way to pull up a complete ICN Inventory or Inventory Activity  with all required data.    Currently have to use multiple reports and inquiries to obtain all contract required data and then blend it into one report.  Items not easily found are MFR Part # (ICN and Activity), Issue DODDAC (Activity).  Inquiries also allows to research multiple days of activity  were the Pre-canned reports only allows for a single day which require multiple reports and then have to compile the reports together.  Additionally, all MFR Part # and Model # is created for each Stock Number.  However there is NO inquiry or report that provides this data in relation to the warehouses activities.  Part # or Model # has to be hand typed into every report to show all data related to the activity. IF DPAS Stores this data, and WebFLIS, can provide this data or it is typed in by the user, why can't we use it for reports and inquiries?  Same applies to the Issuing DODAC.  Its part of the "activity" it should be selectable, not just the Owning DODDAC, which is already known as it is the warehouse creating the report
 
Recommended:
At a minimum the following data should be made available (selectable, not default) to the ICN Inventory or Inventory Activity inquiries:
MFR Part # (ICN and Activity)
Issue DODDAC (Activity)
Additionally the following fields would also be nice to have fro a higher clarification the inquiries
DODDAC Address 1 (Activity)
 
Mission Critical:
NAVSEA Contract N00024-22-C-5231
SECNAVINST 5200.44
 
Benefits:
Elimination of excess labor costs.
Concise reporting capability via DPAS.  
reduction of possible errors in reporting due to merging of data
 
Frequency: Daily
 
Users:
Est user: Unk (DPAS Wide).  within our DODDAC(s) - 12

 

01994 Components to End Items PA NSWC New
Change Request: Process Improvement

Description:
Users are not able to remove a cost or no cost component asset to become an end item
 
Recommended:
Enable a end user to covert a cost or no cost component back to a end item without Leidos intervention for both active assets and assets that have been archived.
 
Mission Critical:
 
 
Benefits:
This will allow users to remove a cost or no cost component and add it to the inventory as an end item without requiring to submit a help ticket to Leidos.
 
Frequency: Daily
 
Users:

All Users

01993 Warehouse Issue 1348 Warehouse NSWC New
Change Request: Process Improvement

Description:
when conducting a warehouse issue DD 1348 is required by NSW for record ,  only option avaliable is to print DD1149
 
Recommended:
Add ability to print a DD 1348 during the warehouse issue process, the following fields must be filled
Blocks 1-3,4-6,23-29,45-80, Total price, unit price, ship from/to, Doc date, Qty rec'd, item nomen, date received,
Doc number, NSN, RIC,
 
Mission Critical:
 
 
Benefits:
This will allow users to print a DD 1348 in accordance with NSW guidance
 
Frequency: Daily
 
Users:
All users
01992 Transshipment Qualifiers (ADC 1463) Enterprise DLA/ DPAS New
Change Request: Policy/ Regulatory

Description:
DEDSO is replacing the Distribution Code 111 functionality (Transportation Only Services ADC 316 functionality ) with specific qualifiers within the DLMS 940R and DLMS 945A transaction sets.  DPAS must implement this change to enable transportation requests / responses to be made systematically with DLA's Warehouse Management System (WMS), and Air Force's Cargo Movement Operations System (CMOS).  The ADC states this change will be implmented within 180 days of ADC issuance 12/22/2023.
 
Recommended:
Modify the DLMS Viewers and DLMS inbound/outbound processes to support the new transportation request qualifiers.
 
Mission Critical:
This change must be implemented to ensure communications with DoD's Transportation Management systems remains active.
 
Benefits:
Failure to implement this change in a timely manner will result in shipping requests  / status updates to be performed manually.
 
Frequency: Daily
 
Users:
For PA, this applies to Air Force users who request transportation support to move air force equipment.  For WM users, this change impacts all users who use a Transportation Manganese System to ship their materiel.
01991 Issued Warehouse Field DW20 Warehouse NSWC New
Change Request: Process Improvement

Description:
When running an issued inventory the DW20 form does not show the issued by warehouse while the issued inventory screen does.
 
Recommended:
Add a issued warehouse field on the DW20 form.
 
Mission Critical:
 
 
Benefits:
This will allow users conducting inventories to to see which items they have issued and are responsible for inventorying. Currently to see which items they are responsible for users must print the DW20 form and compare the issued inventory screen results to the DW20 to see the what items they are responsible to inventory.
 
Frequency: Daily
 
Users:
All users
01990 Additional Trading Partner fields for DAI PA Leidos New
Change Request: Policy regulatory

Description:
DPAS controls display and edits of key accounting fields based upon the accounting interface system that is to receive the data.  The display/edits business rules are developed in concert with the accounting system and are documented in the interface control document.  Today, DAI is not receiving the Trading Partner Department Cd, Trading Partner Basic Symbol or the Trading Partner Subhead which MDA, and agency supported by DAI states are mandatory fields to feed DFAS's DDRS (Defense Departmental Reporting System).   As a result, they must gather this data for each transferred/disposed asset, correct their DDRS submission errors manually.
 
Recommended:
DAI and DPAS are modifying the Interface Control Document interface strategy documents to state these fields are required. This SCR is to document the change to the DPAS system.
 
Mission Critical:
DDRS / Standard Financial Information Structure (SFIS) reporting rules require these fields to be included in the DDRS submission.
 
Benefits:
Eliminates errors in the agency's report submission to DRRS which requires the agency to collect the data and manually update the submission when the data can be collected systematically as part of the transfers / disposition of the asset.  
 
Frequency: Daily
 
 
Users:

All agencies/users that are using DAI as their accounting system.

01989 Asset Status Code PA MDA New
Change Request: Process Improvement

Description:
When updating the Loan Code from 'G' to 'C', the Asset Status Code automatically reverts from 'T' to 'O'.  GFP assets have an Asset Status Code of 'T' - Out on Loan.  If the loaning address is WAWF enabled or if it contain a DoDAAC within DPAS, it always updates the Asset Status Cd to 'O' - Outbound in Transit.  
 
Recommended:
Recommend  the Asset Status Code automatic update function to change for GFP.
 
Mission Critical:
 
 
Benefits:
This action will allow for a more efficient work flow and minimize the redundancy in correcting the Asset Status Code of all GFP asset updates.
 
Frequency: Daily
 
Users:

DPAS wide

01988 Locate Last Accountable Serialized Item Entry (LLASIE) Enterprise DLA New
Change Request: Policy/ regulatory

Description:
OSD has changed how it supports information requests for Small Arms / Light Weapons (SAs/LWs).  Currently DoD requires components to report their SAs/LWs to a DoD service registry with that data being forwarded to the designated sponsoring service (Army) to create a DoD Registry.  When requests for information is received, the Army queries the registry for info, then responds to the request.  From an OSD perspective, this is the sole purpose of the SA/LW registries.  In 2022, they directed the Army to eliminate the SA/LW registries and to treat SAs/LWs just like any other supply item - i.e.  use logistics transactions to respond to the information requests.  As a result, the Army has developed Application Program Interfaces (APIs) referred to as "Locate Last Accountable Serialized Item Entry" (LLASIE).  Its design does not limit the requests for information to SAs/LWs.  The design provides for finding any item within the Department.  
 
Recommended:
An Army LDAC representative will input criteria into LLASIE.  LLASIE will contain a master list of Accountable Property Systems of Record (APSRs) which will be used to direct the request for information via an API.  When the APSR receives the request for information, it will interrogate its data using the criteria provided by LLASIE to prepare a response. When the data has been gathered, the APSR will transmit a response to LLASIE via an API.  The info that LLASIE may request may reside within DPAS's Property Accountability and Warehouse Management applications.   DPAS will need to create a repository that is capable of storing the  request and the response.   The system should be designed in a way that these requests/responses will be auto removed after x period of time (system level variable).  Visibility of the requests / responses should be made available to the DPAS User via a DPAS Role.  A separate SCR will be developed to remove the DPAS Registry application should it be determined that there is no reuse of it. Feeding data to / from the Registry application may cease when the Army has approved the DPAS implementation / fielding of this SCR and endorsed by the DPAS PM.  
 
Mission Critical:
OSD eliminated the DLMS SA/LW transactions sets / reporting, and replaced the SA/LW registries with LLASIE.
 
Benefits:
This changes eliminates the requirement for a SA/LW registry and implements DLMS change ADC 1244 and it amendments.
 
Frequency: Weekly
 
 
Users:
This change is an OSD directed change. It impact all customers.
01987 M&U Attachments MU DCSA New
Change Request: Policy/ Regulatory

Description:
Problem: The current state of DPAS M&U lacks the ability to effectively retrieve attachments for audit purposes, such as dispatch/vehicle logs, receipts, and maintenance records for vehicles. This function doesn't allow the agency to pull desired attachments that are attached within the M&U module for inspection or investigative purposes. The correction of this defect will ensure agencies are able to store documents for audit purposes and allow agencies to comply with the National Archives and Records Administration (NARA) requirements.
 
Recommended:
Solution is to implement the attachment process that's currently utilized by the PA module. Attachments are allowed to be added in the M&U module, but you're not able to see all attachments for the asset. Currently, each dispatch has to be referenced to view or retrieve all attachments relating to the asset.
 
Mission Critical:
General Records Schedule (GRS) 5-4-010 or File 207 (DAA-0064-2015-0003 item 1); GRS 5-4-110
 
Benefits:
Compliance with General Records Schedule (GRS) and National Archive Records Administration (NARA) requirements. General Records Schedules (GRS) are schedules issued by the Archivist of the United States that authorize, after specified periods of time, the destruction of temporary records or the transfer to the National Archives of the United States of permanent records that are common to several or all agencies.
 
Frequency: Daily
 
Users:
This will be used by all users multiple times a day, week or when required.
01986 Security Banner Classifications Enterprise Leidos New
Change Request: Policy/ Regulatory

Description:
DoD has replaced their security classification with new values  U//FOUO is a legacy marking used to indicate sensitivity based on agency policy or practice.  CUI is a marking that is used to indicate the presence of CUI basic information.  CUI markings are applied only to those information types/categories found on the CUI Registry and can be linked to laws, regulations, or Government-wide policies calling for protection or control of the information.
 
Recommended:
Add the new security classifications to DPAS and update the U//FOUO legacy markings to meet the new guidelines.
 
Mission Critical:
 
Benefits:
DPAS will display the appropriate classifications.
 
Frequency: Daily
 
Users:
About 25,000 affected users (All users of DPAS)
01985 DAI Accounting Interface Update PA MDA New
Change Request: Process Improvement

Description:
 DPAS is currently reporting unvalidated capital records to DAI.  The DPAS-DAI Accounting interface report contains records not yet validated.  
 
Recommended:
In order to ensure accurate accounting records, MDA requests an update to the DPAS-DAI interface report.  Currently the DPAS is reporting unvalidated assets (records) to DAI. MDA requests DPAS to NOT report to DAI when the Agency Define #2 is marked 'No', since those records are not validated (yet) and they are not considered financially reportable.
 
Mission Critical:
MDA Directorate of Finance Policy:  Capital assets classified as GE, IUS, and OM&S will be validated prior to being reported on Missile Defense Agency (MDA) financial statements.

 
Benefits:
This action will allow for a more efficient work flow and minimize the man-hours required to reconcile the interface report.  
 
Frequency: Daily
 
Users:
DPAS will be monitored on a weekly basis in order to identify new assets that are brought to record and that meet financial reporting requirements. (Note: Daily monitoring is required during the last few weeks of the quarter, as assets may be added daily during this time).
This will affect all MDA Property Accountability users of DPAS.
01984 Physical inventory for Asset ID in WM Warehouse Leidos New
Change Request: Process Improvement

Description:
CNIC does not have label printers available at their installations for the printing of an Inventory Control Number (ICN) label. As an alternative, they have purchase Asset Id labels that are affixed to the item at time of receipt.  DPAS WM provides for the capture of the Asset Id, pRFID, UII, Serial Nbr as well as generating an ICN as a method for identifying an item in inventory.  Their plan was to use the Asset Id label for conducting PIs.  The problem is DPAS WM doesn't currently support the scan of the Asset Id as PA does.  All of the other identifying options except for Asset Id are available in WM for identifying items in inventory.  This SCR is requesting DPAS include the Asset Id as an option for identifying an item when conducting and when reconciling a physical inventory in WM.  
 
Recommended:
Have the DPAS WM application include Asset Id as a method for identifying an item when conducting a physical inventory
 
Mission Critical:
 
 
Benefits:
 Provides a way to label items with "purchased" labels when no label printers are available to the organization.   Provides a standard method for conducting physical inventories between PA and WM.
 
Frequency: Daily
 
Users:
The SCR applies to all users of the DPAS WM application that do not have label printers to print identifying tags.  This provides them a way to label and asset and conduct PIs using the label.
01983 Tool Accountability MU AF: A4/HAF FH-AFHAF New
Change Request: New System Process

Description:
Problem: The current state of DPAS M&U lacks a crucial feature that hinders effective tool accountability for units. The absence of a dedicated tool accountability mechanism creates challenges in tracking and managing tools within the system. This enhancement aims to streamline the process of tracking tools across units, ensuring better visibility, control, and overall efficiency in tool management within the DPAS M&U system.
 
Recommended:
Solution is to implement a mirroring of the Warehouse Module's tool accountability features into the M&U module. This involves replicating the robust tool tracking mechanisms present in the Warehouse Module and integrating them seamlessly into the M&U module.
 
Mission Critical:
AFI 21-101 CH 8.5 Tool Accountability and Serviceability. Flight CC/SUPT and Section NCOICs/Chiefs,
through CTK Custodians, are responsible for tool and equipment accountability and control
(knowing where tools are and who has responsibility for them). When a person signs for a tool or
piece of equipment, they are considered the user and accountable for the item until it is returned
to the tool room and accountability transfers back to the CTK Custodian (through a representative
or tool room employee).
 
Benefits:
Enhanced Accountability: Improved tracking reduces the risk of tool loss or misplacement.
Unified System: Standardized tool tracking practices promote cohesion across DPAS.
Streamlined Operations: Familiar functionalities minimize the learning curve and enhance efficiency.
Real-Time Visibility: Synchronization ensures up-to-date information on tool status and location.
Improved Reporting: Access to advanced reporting and analysis capabilities for better insights.
User Empowerment: Enriched features empower users in tool tracking and management.
Reduced Errors: Standardization minimizes data entry errors and duplications.
Adaptability: Scalable solution accommodates future changes in tool tracking requirements.
 
Frequency: Daily
 
Users:
This improvement will be used by all users,  hundreds of times a day.
01982 General Database Infrastructure Changes Enterprise Leidos New
Change Request: Process Improvement

Description:
In many application releases, the Leidos team needs to implement various database infrastructural changes and improvements.  These changes include, but are not limited to, index adjustments, configuration changes, and the implementation of database utility objects.  These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, correctness, and performance of the DPAS system.  I am requesting an SCR for calendar year 2024 to encompass this category of database changes.
 
Recommended:
Implementation of any database infrastructural changes and improvements deemed necessary by the Leidos Team.
 
Mission Critical:
 
 
Benefits:
These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, correctness, and performance of the DPAS system.
 
Frequency: Daily
 
Users:
N/A - Infrastructural enhancements that wouldn't directly affect the users.
01981 Dark Mode Enterprise AF: VSCOS New
Change Request: Process Improvement

Description:
Users complain the DPAS screens are too bright, causing eye fatigue, discomfort and headaches.
 
Recommended:
Provide a "dark mode" option to allow users to reduce the brightness of the DPAS screen. "Dark mode" option would inverse screen colors, turning the light background to black or dark shaded color.  Text color would be the minimal contrast to allow for readability while reducing eye strain.
 
Mission Critical:
N/A
 
Benefits:
Improved quality of life, eliminating eye strain for users sensitive to bright screens.
 
Frequency: Daily
 
Users:
4.5K users within DF-VEHS maintenance program, as well as potentially benefiting other agencies using DPAS.
01980 Update Legacy UII DoDAAC PA Leidos New
Change Request: Process Improvement

Description:
The DPAS UII assignment process utilizes NAVSUP BSC's DoDAAC for the standard DPAS application.  NAVSUP's BSC's DoDAAC was used due to the need to ensure uniqueness in the UII assignment process.  With DPAS having gotten their own DoDAAC, there is a requirement to use DPAS's as NAVSUP BSC is no longer involved withe DPAS, thus there is not a good way to ensure this DoDAAC isn't used used by another system to assign UIIs
 
Recommended:
1. Update the DPAS System Setting table in prod to utilize the DPAS DoDAAC of "SC0010" and reset the last serial nbr used to 1.  
2. Review DPAS processes to ensure there is nothing hard coded to use N00367 - uspAssetKeyValidation.sql, WPHRI01IUIDInterface.vb, AssetUpdate_LoanBL.vb,WPSAB15AssetTransfer.vb
3. Determine if an environment variable should be implemented to support standalone sites for the above processes so the correct DoDAAC is used in these programs.
 
Mission Critical:
This change updates the Agency DoDAAC used to assign the UII.
 
Benefits:
Standardizes the DoDAAC that DPAS uses for UII assignment rather than using an organization's DODAAC no longer supporting DPAS.
 
Frequency: Daily
 
Users:
This change impacts all customers that have a need to assign a UII to an asset within PA or WM.
01979 Labor Report MU AF: A4/HAF FH-AFHAF New
Change Request: Process Improvement

Description: 
Problem: There is no way to pull a Labor Report.
There are times when a Production Supervisor or likeness will need to pull a labor report for a specific period of time. There is no good way to do this currently in the system. The only way to do it now is to pull labor over a large period of time and then find the specific date within all of the data.
 
Recommended: 
1. Create a Labor Report that can be pulled from Forms-Reports.
2. Fillable Fields will include: Last transaction Dt/Time From & Last transaction Dt/Time To, Maintenance Activity which will be defaulted to the MA currently in, Equipment Pool defaulted to preferences if set-up and able to add multiple Equipment Pools, Labor Technician Drop-down able to add multiple, Maintenance Team able to add multiple.
3. Fields that the report will pull automatically: Maintenance Activity, Maintenance Team, Equipment Pool, Asset ID, Secondary Serial Number, Labor Technician, Actual labor Hours, Labor Category, Rate Type, Work Order Description, Requested Service, Service Performed, Last Transaction Date/Time, Work Order Status.
 
Mission Critical: 
Per T.O. 00-20-2 Paragraph 1.5.2.3, maintenance man-hours are used to determine repair times and cost to operate systems. Man-hours in maintenance data documentation systems are taken into consideration when determining manpower requirements.
 
Benefits: 
Adding a labor report to DPAS M&U would provide supervisors with a valuable tool to monitor daily time allocation, ensuring that work hours are efficiently utilized. This enhancement would also offer a more precise insight into the allocation of time for each work order, enhancing overall fleet management and resource planning.
 
Frequency:  Daily
 
Users: 
This improvement will be used by all users,  hundreds of times a day.
01978 Non-serialized WAWF AS receipts PA Leidos New
Change Request: Process Improvement

Description:
Currently the PIEE WAWF AS 856 (new procurement receipt) does not contain a serial nbr when there is no UII included by the vendor.  When DPAS initially developed the interface, the decision was made to not display WAWF AS Receipts that do not have a serial nbr.  This design has worked well for the DPAS customer base.  With increased use of DPAS, there are several customers that wish to see the WAWF receipts that do not contain a serial nbr within the property accountability application.  Note:  DPAS does display non-serizlied WAWF AS receipts within its Warehouse application.
 
Recommended:
Provide for PIEE new procurement receipts sent via the WAWF AS 856 transactions that do not contain the UII loop to be shown as a Due In within the DPAS PA application as an organizational option.  Recommend DPAS incorporate a UIC Setting that will provide the UIC the option to view / not view WAWF AS 856 receipts that do not contain a serial nbr.  This change will retain the current capability for the organizations that do not want to see WAWF AS 856 receipts that do not contain a serial nbr and will provide the capability for organizations that want to view all receipts (serial and non-serial).
 
Mission Critical:
 
 
Benefits:
Provide the DPAS customer with visibility of non-UII/non-serialized WAWF receipts.
Users will be able to receipt for a wider variety of assets into PA.  
 
Frequency: Daily
 
Users:
01977 Consumption Report Select All Warehouse NSWC-SPECWARCOM New
Change Request: Process Improvement

Description:
When running consumption report you must individually select stock numbers for this report.
 
Recommended:
Add a "select all" button to stock number browse screen, that also allows the ability to select all pages
 
Mission Critical:
 
 
Benefits:
This will allow users to run the consumption report for multiple stock numbers within a searched field (item description, size, color, reportable commodity type) without having to individually select each stock number.  Having the select all/all pages button will allow users to more efficiently select large amounts of stock numbers for the consumption report.
 
Frequency: Daily
 
Users:
All users
01976 DPAS .NET 8 Update Enterprise Leidos New
Change Request: Policy/Regulatory

Description:
Microsoft has announced the end of life "EOL" for .NET 6 as 11-12-24.  DPAS has applications that are using this .NET 6.  These will need to be updated to .NET 8 (Latest LTS Version).  .NET 8 has a scheduled EOL of 11/10/2026.
https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core
 
Recommended:
Update applications to .NET 8
 
Mission Critical:
DoD is not authorized to operate software that is EOL.  Failure to complete the upgrade will result in DPAS not receiving security patch updates / support.
 
Benefits:
Maintain DPAS compliance
 
Frequency: Daily
 
Users:
All users