Unlike submitted Support help tickets, System Change Requests (SCR's) can only be submitted through your organization's appointed and authorized ELMS CCB member representatives, or otherwise if no CCB representatives have yet been appointed, your Primary Information Owner appointee. If you are unsure of who your organization's appointed ELMS CCB member representatives or Primary IO are, you may email the ELMS Support team to request that information:
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.
Utilize the search filters below to narrow your results by keywords, module, or state. You may also request an Excel file of all the SCR data by contacting the Help Desk.
| Found: 1779 Result(s) | Show: |
| Title |
ELMS Module |
Reporting Org |
State |
Description |
Action |
|
|---|---|---|---|---|---|---|
| 01876 | Add My Queries to Grid Options for Inventory Activity Inquiry | Warehouse | NSWC: WARCOM | New | Change Request: Process Improvement
Description:
Lack of ability to tailor the Inventory Activity Inquiry data based on user preference.
Recommended:
Add "My Queries" in the Grid Options on the Inventory Activity Inquiry.
Mission Critical:
Allow the user to quickly retrieve the needed information based on their preference.
Benefits:
This improvement would improve time/cost on the user. This would eliminate the need to remove and add columns every day so they user can review the activity in their needed format.
Frequency: Daily
Users:
This problem affects all current users. |
|
| 01875 | Include Inspections for Issued Assets in WH Activity Report | Warehouse | NSWC: WARCOM | New | Change Request: Process Improvement
Description:
Adding completed Assessments of Issued out assets to the Warehouse Activity report.
Recommended:
Include assessments of issued out assets in the Warehouse Activity report.
Mission Critical:
The ideology of the Warehouse Activity report should be to include all completed actions to include actions completed on assets issued out as they still have the Owning DoDAAC of the warehouse.
Benefits:
This will improve accountability of assets for reporting purposes.
Frequency: Daily
Users:
This problem affects all current users.
|
|
| 01874 | Inspection Search Criteria Population | Warehouse | NSWC: WARCOM | New | Change Request: Process Improvement
Description:
Lock in the parameters within Inspection screen. Once you complete an inspection on selected inventory and go back to the available inventory, the filters set in place are reset. This requires you to input your filters/parameters after each inspection which greatly affects the time it takes to complete all the required inspections for that period.
Recommended:
Implement the same functionality to the inspection screen which is used on the Inventory Update screen. When updates are done on the selected inventory the available inventory does not remove previously set filters.
Mission Critical:
This functionality would greatly reduce the time it takes for users to complete their inspections by removing the need to repeatedly set their filters after each inspection.
Benefits:
Drastically reduces Time/Cost
Frequency: Daily
Users:
This problem affects all current users. |
|
| 01873 | Mass Assessment and Repair | Warehouse | NSWC: WARCOM | New | Change Request: Process Improvement
Description:
When completing assessments on hundreds of assets the lack of ability to assess multiple assets at once if they all receive the same type of repair.
Recommended:
Give the ability to select more than one asset at a time during the assessment process when completing a repair.
Mission Critical:
Without this, the smaller armories are still able to accurately complete their assessments but the larger armories have trouble doing so without being able to assign the same repair to multiple assets at once.
Benefits:
This improvement would reduce the time/cost of individuals as well as increase accountability since some armories currently forgo this process because of the time it takes completing assessments.
Frequency: Daily
Users:
This problem affects all current users. |
|
| 01872 | Upgrade Kendo and React Frameworks | Enterprise | Leidos | In Progress | Change Request: Process Improvement
Description:
The DPAS applications utilize Kendo and React JavaScript frameworks that are in need of upgrading to the latest versions.
Recommended:
Upgrade the Kendo and React frameworks used by the DPAS application to the latest compatible and stable versions.
Mission Critical:
The upgrade of frameworks often introduces improvements to development capabilities which enable developers to deliver higher quality and more reliable software. It also prevents DPAS from operating on unsupported software that is a security violation.
Benefits:
The Kendo and React frameworks need to be regularly kept current to introduce new features, resolve bugs, and to eliminate any potential security vulnerabilities identified in the frameworks. These frameworks often come with improve development capabilities. These upgrades should add stability and reliability to the DPAS application.
Frequency: Hourly
Users:
These frameworks are continually evaluated and are used daily in most modules of the DPAS application. Approximate total users affected are 17K.
Partially Completed – Release 2023.3.2 – 28 July 2023
Partially Completed – Release 2023.3.4 – 25 August 2023
Partially Completed – Release 2024.1.6 – 22 March 2024
Partially Completed - Release 2024.4.1 - 04 October 2024
Partially Completed - Release 2024.4.2 - 18 October 2024
|
|
| 01871 | Improve DPAS login Process | Enterprise | Leidos | Done | Change Request: Process Improvement
Description:
Currently the DPAS application relies on a Login process that is only compatible with non-modernized modules. This requires modernized modules to be launched after first navigating through existing non-modernized modules. This limits the ability for newer modernized modules to run standalone and can be frustrating for users wanting to bookmark the modern DAPS modules. Through the modernization of DPAS the number of non-modernized modules that can be used to launch these newer modules will continue to be reduced and eventually eliminated.
Recommended:
Improve the DPAS Login Process to remove the requirement of using a non-modernized modules to access newer modules and have the new modules initiate authentication themselves. To the extent possible, eliminate use of the non-modernized Login Process in favor of a single DPAS Login Process.
Mission Critical:
These changes will improve the user login and authentication process in DPAS for all DPAS modules.
Benefits:
The added run-ability of modernized DPAS modules will enhance the users' experience by allowing them to bookmark and authenticate directly to modernized DPAS modules. This will additionally help reduce development complexities when testing code changes as non-modernized applications will no longer be a requirement to a functioning test case.
Frequency: Daily
Users:
These changes will enhance the sign-on process for all 17K users.
Partially Completed – Release 2023.3.4 – 25 August 2023
Partially Completed – Release 2023.3.5 – 08 September 2023
Partially Completed – Release 2023.4.4 – 17 November 2023
Completed - Release 2023.4.4
|
|
| 01870 | Remove Unnecessary NSerivceBus Endpoints | Enterprise | Leidos | Done | Change Request: Process Improvement
Description:
Two endpoints were setup for each of our modernized applications. In most cases it is only necessary to setup a single endpoint for each application. Our service agreement with NServiceBus indicates that we are billed for each endpoint. Having unnecessary endpoints increases the program's costs while not adding value to the program
Recommended:
Remove the extra, unneeded, endpoints in our API Layer and move the request tracking logic to the Service Layer of the DPAS modernized applications. This will reduce the overall number of endpoints consumed and reduce the associated costs.
Mission Critical:
Removing unnecessary endpoints will reduce costs and removing unnecessary code will improve maintenance and development speed.
Benefits:
Reducing the additional costs of endpoint usage.
Removing unnecessary code, reducing complexity, and saving future development time. Frequency: -
Users:
The majority of our modernized applications will be affected. Approximate total users that use these systems are 17K.
Completed - Release 2023.2.3 |
|
| 01869 | Global Appsettings | Enterprise | Leidos | Done | 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.Completed - Release 2023.2.2 - 21 April 2023 |
|
| 01868 | DLMS Modernization of Inbound 846 | 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) Partially Completed – Release 2023.2.1 – 07 April 2023
|
|
| 01867 | DLMS Modernization of 846 Outbound | 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) |
Disclaimer | Accessibility