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 |
|
|---|---|---|---|---|---|---|
| 02046 | NCE Fields Inquiry | MU | AF: VSCOS | New | Change Request: Process Improvement
Description:
1.) DPAS M&U lacks the ability to view and select NCE indicator fields within all Work Order/Sub Work Order inquiries and fields selection list
2.) DPAS M&U does not have "Mission Critical", "Reimbursable" or "Refundable" as fields within the inquiry search criteria Recommended:
1.) Add "Nuclear" and "Nuclear Restricted" NCE fields to Work Order inquiries to include Sub Work Order- Asset, Labor & Parts.
2.) Add "Mission Critical", "Reimbursable" and "Refundable" to all of the Sub Work Order Search Criteria and Available Fields. Mission Critical:
Department of the Air Force Instruction 24-302 VEHICLE MANAGEMENT
AFI 63-125 NUCLEAR CERTIFICATION PROGRAM Benefits:
Adding fields provide users a more consolidated report and alleviates multiple inquiries in the
process. Users will also have the ability to view specific mission essential information within all inquiries. Frequency: Daily
Users:
This process improvement benefits DOD agencies and military services on a daily basis. |
|
| 02045 | External ICP 846R without Project Code | Warehouse | USMC | Done | Change Request: Process Improvement
Description:
USMC is utilizing Navy ERP as its ICP with their Albany warehouse operation supported by DPAS. It's been reported that Navy ERP manages its inventory by RSA (Remote Storage Activity), Stock Nbr, and Condition Cd. The DLMS 846R End of Day (EOD) inventory balance file that DPAS produces includes "Project Code" as part of the reporting. Currently Navy ERP is not designed to summarize RSA generated DLMS 846R transaction sets to the level the inventory is managed by Navy ERP. Thus the inventory totals for items that do contain a project code that DPAS is reporting do not match the inventory totals that Navy ERP has. The proposed solution is for DPAS to generate its EOD inventory reporting balance without including the "Project Code" in the group by.
Recommended:
1) Create a version of the DLMS 846R EOD transaction set that does not include "Project Code" in the group by in the inventory count (RSA, Stock Nbr, and Condition Cd).
2) Add this DLMS 846R EOD option as a configuration setting for the warehouse similar to the setting that enables the Warehouse to generate a DLMS 867I Issue transaction set that is required by Navy ERP. Mission Critical:
This change would enable DPAS to generate the DLMS 846R EOD transaction set with inventory counts that will match the inventory balance of Navy ERP and other ICPs that may not manage inventory at Project Code level.
Benefits:
Providing this option enables systematically inventory balance reconciliation between the RSA and ICP via the the DLMS 846R EOD transaction set. Navy ERP adjusts its inventory using the Qty reported within the DLMS 846R EOD. Currently this is resulting in invalid inventory counts.
Frequency: Daily
Users:
Navy ERP is the only known external ICP where DPAS Warehouse is being used as the RSA.Completed - Release 2024.3.6 - 20 September 2024 |
|
| 02044 | Multi Search serial number | Warehouse | Army | New | Change Request: Process Improvement
Description:
DPAS lacks the capability to search for and select multiple serial numbers simultaneously. This capability needs to be added to the "Inventory Master Sector" across processes.
Recommended:
Create a field capability that enables users to paste multiple serial numbers into a single field. This enhancement will allow DPAS to search for and select all the serial numbers entered in the field simultaneously.
Mission Critical:
Yes, all DPAS users who currently handle a large number of serialized assets will have the capability to search for and select multiple serial numbers simultaneously, instead of one by one. This proposed modification aims to significantly reduce the man-hours required for searching and selecting serial numbers. These improvements will lead to overall cost savings for the U.S. government and streamline warehouse movements with greater control and accuracy.
Benefits:
This solution enhances accuracy for large scale serial number movements across the force and provides a total cost savings by reducing manhours and time-to-task required to accurately issue large scale amounts of serial numbered equipment ranging in the hundreds or thousands.
Frequency: Daily
Users:
This solution would benefit all user operating within WM, (or our community that is ~500 users. |
|
| 02043 | Checkmarx Code Updates | Enterprise | Leidos | Removed | Change Request: Process Improvement
Description:
Recently the DPAS project has utilized Checkmarx code scans to identify potential vulnerabilities and improvements to the DPAS code base. These scans have provided insight into areas of improvement in the application. This SCR is to provide for the review and for the implementation of code refinements where applicable.
Recommended:
The DPAS application should be updated to address potential security enhancements flagged by Checkmarx, including additional input validation and deprecation of unused legacy AIT code.
Mission Critical:
Benefits:
Applying recommended updates from Checkmarx will enhance application security and possibly the reduction in the app through sunsetting of legacy code.
Frequency: Hourly
Users:
Application Upgrade
Removed per Randall Reed; Duplicate of 02057 |
|
| 02042 | Stock Number Edit | PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW) | Leidos | New | Change Request: Process Improvement
Description:
Currently the Stock Number AUD (LPCTN01) disables fields for edit due to the stock number being externally sourced or having associations to assets or inventory control numbers. Not providing the ability to allow the user to modify as many fields as possible, limits their ability to make the change increases the time to get their data as well and places an effort on the Help Desk and Development Teams to make the change. The DPAS team should review the fields that are disabled to determine which can be activated. If the system requires a Mass Sock Nbr change feature to support external interfaces, as well and financial reporting, this could be a method to support enabling the user as well as supporting AESIP / FLIS changes that are not currently being processed.
Recommended:
As a minimum, the following fields should be opened up for edit on LPCTN01 Stock Nbr AUD
Type Asset Code & Asset Category Code – These can be opened for edit in warehouse and PA as long as financial accounting is supported for OM&S and Fixed Assets.
Shelf Life Code - Should allow adjusting between types I & II A job must first be put into place before we can convert to type 0 as this would constitute a bulk inventory roll-up, or the override flag cold automatically be set on the record to retain the shelf life expiration dates.
Accounting Requirements Code (ARC), DEMIL Code, CIICMission Critical:
Implementing the capability to allow for more attribute change via automation will assist with keeping the external catalogs feeds with DPAS data in sync through automation.
Benefits:
Allows the user more flexibility when performing stock number adjustments and removes the need to contact help desk when adjustments to key fields is required.
Frequency: Weekly
Users:
DPAS currently receives about 1-10 data scripts per week to address desired catalog updates. |
|
| 02041 | 832N Document Number and Transaction Date (ADC 1469) | Materiel Management | AF: GFM | In Progress | Change Request: Policy/ Regulatory
Description:
DLMS ADC 1469 provides new data fields to the DLMS 832N transaction - added are the document number (aka transaction reference number) and the transaction date and time. Need DPAS to add the new data fields from the 832N and include in DLMS transaction processing (including 824R reject transaction).
Recommended:
Make necessary changes in the ICP module process and correctly handle the document number and transaction date and time. Users will see new data in the DLMS transaction viewer and DPAS will include these new data elements in the DLMS 824R Reject notification process.
Mission Critical:
ADC 1469
Benefits:
The added data elements within the 832N will assist in processing the inbound 832N transaction and any subsequent 824R Reject notifications to AF CICPs.
Frequency: Daily
Users:
AF GFM-A users |
|
| 02040 | SKO for MU Work Order | MU,Warehouse | Leidos | New | Change Request: Process improvement
Description:
Currently SKO (Set Kit Outfit) processes are dedicated to the warehouse application. As part of DPAS modernization, the SKO processes are wanted in the Maintenance Module to enable maintenance personnel to manage the build / modification of a SKO using a Work Order. In future updates, the DPAS SKO process could replace the End Item / Component process that exists in PA today.
Recommended:
Build a new, single SKO Management page - from which all management functions can be supported.
Build a new SKO View, utilizing a tree view to support multiple layers of nested kits with functionality to add, update/replace components.
Build a new inventory selector to facilitate the addition/replacement of components.Mission Critical:
The goal of the new UI is for it to be more user efficient, needing less clicks and built to support implementation to other areas of the application.
Benefits:
Changes are required to support SKO processing within a Maintenance Work Order. Without this modernization, the implementation of SKO into Maintenance is not possible. This change is part of the approved changes to provide ASA(ALT) SKO functionality within a Work Order
Frequency: Daily
Users:
All organizations that utilize Set Kit and Outfit functionality.
|
|
| 02039 | Improve Job Execution Logging and Retention | PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW),Enterprise | Leidos | New | Change Request: Process Improvement
Description:
Currently, it is difficult to provide a complete picture of job executions throughout the system.
Recommended:
Implement database history tables and triggers for the PA/M&U process queue and batch queue. Adjust retention policies for job execution log and history database tables to 1 year.
Mission Critical:
Benefits:
Improved logging and retention of job executions will aid in investigation and debugging of system issues. This additional information will also provide easier and more complete answers to auditors.
Frequency: Daily
Users:
N/A - Infrastructural enhancements that wouldn't directly affect the users. |
|
| 02038 | Open Action Expiring Items | Warehouse | NSWC | New | Change Request: Process Improvement
Description:
Current DPAS does not have the capability to report Open Warehouse Actions for Expiring Items.
Recommended:
Build new functionality within the Open Warehouse actions to add a section for Expiring Items within 90, 60, 30 days and expired for items with expiration dates.
Mission Critical:
Benefits:
This will allow Users to increase their current operational level of support by reducing the time spent generating reports.
Frequency: Daily
Users:
This affects all users within NSW. All Units within NSW use this process. |
|
| 02037 | Warehouse Issue receipt | Warehouse | NSWC | New | Change Request: Process Improvement
Description:
Only two forms currently exist for printing out a completed warehouse issue: Pick List & 1149
Recommended:
Add another form (ex. DD1150) that can be printed which can be used as a 'receipt' for expensing material via Warehouse Issue. Form will need at the minimum:
From Owning DoDAAC/Warehouse, To DoDAAC, Stock Nbr, Mfr Part Nbr, Nomen, Serial Nbr, Qty, ICN, Cost Center, Doc Nbr, Unit Price, Total Price, Signature Block, etc...
Mission Critical:
Since material is being expensed, a signed receipt is required to document inventory loss
Benefits:
Since material is being expensed, a signed receipt is required to document inventory loss.
Frequency: Hourly
Users:
All users |
Disclaimer | Accessibility