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
02006 Add Warehouse Role Warehouse NSWC New
Change Request: Process Improvement

Description:
Users with Warehouse Officer roles are not able to create a Warehouse.
 
Recommended:
Enable users with Warehouse Officer roles to create a Warehouse.
 
Mission Critical:
 
 
Benefits:
This will allow Warehouse Officers to create a Warehouse without the need to contact Leidos to create a Warehouse.  This will eliminate undue burden on users to create additional documents when receiving assets.  IAW COMNAVSPECWARCOMINST 4460.1F the command APO or AAPO shall receive and validate accountable property and completely entered into the APSR within seven working days of physical receipt.
 
Frequency: Quarterly
 
Users:
All Users
02005 Backorder Inquiry Warehouse USMC New
Change Request: Process Improvement

Description:
Currently to find out what a member has on Backorder is a very time consuming process.  You have to go back into the members issue to see the item that is backorder when you have over 800 backorder's this could become a full time job.  
 
Recommended:
Recommend either the item that is on backorder be visible in the backorder details tab along with the members email and phone number or a backorder inquiry be built with the following columns:
Issue Nbr
members name
member email
members phone number
UIC
backorder Items (Nomenclature and Qty)
Backorder established date
 
Also within the Backorder Inquiry page, there needs to be functionality to "Delete" existing Backorders that are no longer needed or are created in error.
 
Mission Critical:
Yes, Because of the amount of time it is taking to look up all these members, members are not getting the items in a timely fashion and it is taking the clerks time that they could be doing other functions.
 
Benefits:
Having this capability will hep get members backorder's in the possession allot quicker and will free up time for warehouse workers to perform other duties.
 
Frequency: Daily
 
Users:
All IIF & UIF
02000 Type Asset Cd for Inventory Update and ICN Inquiry Warehouse NSWC New
Change Request: Process Improvement

Description:
Users are not able view currently inventory Type Asset Cd
 
Recommended:
Add Grid Option->Columns for Type Asset Cd on Inquiries->ICN Inventory and Materiel Mgmt->Inventory Update Manager.
 
Mission Critical:
 
 
Benefits:
This will allow users to view their current inventory type asset code without the need of exporting the inventory and WH catalog then executing a script to compare the two files.
 
Frequency: Daily
 
Users:
All Users
02004 Equipment Utilization Auto Populate MU DCSA New
Change Request: Process Improvement

Description:
Problem: The current state of WPMAR10R-Equipment Utilization doesn't auto populate from the data input from previous screens.  
 
Recommended:
Solution is to auto populate the data from the previous screens. The TO and FROM dates and previous mileage should auto populate on the Equipment Utilization form.
 
Mission Critical:
The auto population of the form will prevent the dispatcher and operator from inputting the data. This will also keep the form and data clean.
 
Benefits:
The implementation of this process would benefit agencies that have vehicles and people dispersed in various locations and would also speed up the process.
 
Frequency: Daily
 
Users:

This will be used by all users multiple times a day, week or when required.

02003 Equipment Utilization Checklist Customization MU DCSA New
Change Request: Process Improvement

Description:
Problem: The current state of WPMAR10R-Equipment Utilization Checklist doesn't allow agency to modify checklist to meet the agency needs.  
 
Recommended:
Solution is to allow for the modification of the checklist.
 
Mission Critical:
This would benefit the agencies because the checklist has some checks that are irrevelant and some that's not listed depending on type equipment being checked.
 
Benefits:
The implementation of this process would benefit agencies that have a variety of vehicles in various locations and would also speed up the process.
 
Frequency: Daily
 
Users:

This will be used by all users multiple times a day, week or when required.

02002 Dispatch Automation MU DCSA New
Change Request: Process Improvement

Description:
Problem: The current state of DPAS M&U lacks the ability to effectively allow the dispatch process to be automated. The agents in the field have to download a scanned dispatch and email to the dispatcher and that takes time that can be better utilized, such as dispatch/vehicle logs, receipts, and maintenance records for vehicles.
 
Recommended:
Solution is to implement an automated dispatch process that will upload dispatch form/vehicle logs to DPAS, with the option to export. This would be called a Driver mobile application which will streamline and simplify the dispatch process. The dispatch will be provided to the recipient via phone/computer. This process would upload all pertinent data such as date, beginning mileage, end mileage and locations. The solution should also allow drivers to scan fuel receipts and maintenance records via the app and attach to dispatch form/vehicle logs.
 
Mission Critical:
The automation of this process would eliminate time and effort of driver's no matter the location. Drivers can see a list of their current trips and record trip start times and odometer readings on the app which will integrate with the Fleet Management Information System (FMIS). Drivers can close dispatches after completion allowing the integrated information to be available in the FMIS. Dispatchers can assign vehicle to an employee as needed and dispatch the vehicles.LMP
 
Benefits:
The implementation of this process would benefit agencies that have vehicles and people dispersed in various locations and would also speed up the process. Drivers can view and complete trips on the go using the app. The app data will automatically integrate with the Fleet Management Information System (FMIS) and eliminate the need for paper dispatch forms and manual data entry.
 
Frequency: Daily
 
 
Users:

This will be used by all users multiple times a day, week or when required.

02001 Generate Reports for Closed Inventories PA NSWC New
Change Request: Process Improvement

Description:
Users are not able generate inventory report that does not have a Inv Process Cd = "OIN" or "ODL" and generate reconciled report that does not have a Inv Process Cd = "OUA"
 
Recommended:
Enable a end user to generate inventory report and reconciled report of closed inventories.
 
Mission Critical:
 
 
Benefits:
This will allow users to print previously completed inventory for audit purpose IAW COMNAVPSECWARCOMINST 4460.1F without requiring to submit a help ticket to Leidos.
 
Frequency: Quarterly
 
Users:

All Users

01999 DAF Item Manager and stock control Role Materiel Management AF: A4/HAF FH-AFHAF New
Change Request: New Role Design

Description:
The current DPAS ICP roles do not fulfill the roles or structure for the Department of the Air Force(DAF) for Item Managers (IM) or centralized stock control functions.  
 
Recommended:
Create new roles that will provide the appropriate profiles for DAF IM and stock control managers that will provide them with the required system capabilities that allow them to accomplished their assigned tasks.
 
Mission Critical:
AFMCMAN23-501V1_AFMCGM2023-011 June 2023 Air Force Materiel Management para 5.8.5.2.
 
Benefits:
By creating a new roles for item manager (IM) and stock control functions this will align with the duty positions of personnel as outlined in DAF policy
 
Frequency: Daily
 
 
Users:
01998 PM scheduling without Asset ID MU AF: FL-AFTAC New
Change Request: Process Improvement

Description:
Currently reccuring tasks will only be scheduled and assigned a workorder number to equipment that has an asset id number; ie a work location with a mixture of accountable/non accountable equipment.
 
Recommended:
Allow for scheduling of equipment without an asset ID number to enure conitinutiy of mx scheduling through all equipment tracked in DPAS not just accountable equipment tracked in the PA module.
 
Mission Critical:
 
 
Benefits:
By allowing for mx schedules to be auto generated without asset ID's it will allow the user a better mx snapshot for upcoming mx requirements.
 
Frequency: Monthly
 
 
Users:
01997 Remove PA/M&U User Tracking Logic Enterprise Leidos New
Change Request: Process Improvement

Description:
The DPAS Property Accountability (PA) and Maintenance and Utilization (M&U) modules have a database table (DPAS.appsec.user_tracking) and associated stored procedures and application code logic that is used to track user system navigation activity.  However, the table and associated objects have been superseded by other existing features that are implemented system-wide.  The contents of the appsec.user_tracking table are not currently monitored or used in any meaningful way.  Also, this table generates a lot of DML activity in the production environment and appears to be involved in some periods of reduced application performance.  At a minimum, the unnecessary DML activity against this table will generate excessively large transaction log backup files.
 
Recommended:
Drop the DPAS.appsec.user_tracking table and any associated database objects.  Remove the application code logic that called these database objects.
 
Mission Critical:
 
 
Benefits:
This change will provide better system performance and availability.
 
Frequency: Daily
 
Users:
N/A - Infrastructural enhancements that wouldn't directly affect the users.
01996 MRO Redesign Warehouse USMC New
Change Request: Process Improvement

Description:
The MRO Process in the WM is not very user friendly. The functionality of the process has not been improved since the original design of this functionality. There are many mandatory steps to get through the process that are not a requirement for the business, to include the Material Movement Plan and Pick Process. There is also no means to allow entire containers to be shipped.
This process is very antiquated and is very rarely used when another process will suffice in getting the gear issued (i.e. Warehouse Transfer or Warehouse Issue)
 
Recommended:
The MRO Process in the WM is not very user friendly. The functionality of the process has not been improved since the original design of this functionality. There are many mandatory steps to get through the process that are not a requirement for the business, to include the Material Movement Plan and Pick Process. There is also no means to allow entire containers to be shipped.
This process is very antiquated and is very rarely used when another process will suffice in getting the gear issued (i.e. Warehouse Transfer or Warehouse Issue)
 
Mission Critical:
 
 
Benefits:
Would improve the entire process of issuing gear to include reducing time required to issue gear, improved accuracy by using the process vice alternate processes.
 
Frequency: Daily
 
Users:
This change would affect all DPAS users who use MRO process, but these requirements have been designed
specifically for USMC and NSW.
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.