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: 1807 Result(s) | Show: |
| Title |
ELMS Module |
Reporting Org |
State |
Description |
Action |
|
|---|---|---|---|---|---|---|
| 01814 | DPAS FAST Updates 2022 | MU | Leidos | Done | Description:
A review of the Federal Automotive Statistical Tool Vehicle - Level Data Business Rules Reference for 2022 is required with updates to DPAS as needed. eg. Manufacturer Names, Fuel Configuration data.
Recommended:
Review current FAST Vehicle-Level Data Business Rules Reference and perform the required updates to DPAS.
Mission Critical:
Mission Critical - The review / updates are necessary to ensure the DPAS edits are current to ensure successful reporting of FAST reportable assets for FY22.
Benefits:
Improves accuracy and accountability
ALL
Completed – Release 2022.3.1 – 18 November 2022 |
|
| 01813 | Add Attachment to Transfer Process | PA | DoDEA | New | Description:
Add a file upload feature during the transfer of equipment transaction. Unable to add/upload a file during transfer transactions.
Recommended:
Add the option to include an attachment when Transferring, adding or updating assets.
Mission Critical:
Yes. DOD encourages electronic storage of all Key Supporting Documents. Having the option to upload transfer documents would consolidate the documentation and meet any future electronic storage requirements.
Benefits:
This feature will improve transfer processing time. This will allow the PBO to upload the file during the transaction avoiding going back after transferred and do an asset update after transfer to upload the file.
Users:This affects all DOD users. |
|
| 01812 | Mfr Part Nbr FAST Reportable Indicator | MU | Leidos | Done | Description:
During the 2022.2 customer maintenance demos, the customers expressed a desire to have FAST reporting defined corporately rather than allowing each Maintenance Activity have the capability to establish the determination. Today, the catalog team has a FAST indicator within the Mfr Part Nbr process. When set to Yes (system defaults to Yes when ACC = P, but user can override the setting) When the FAST Indicator is Yes, the system forces the user to select a FAST Mfr Name. Currently the indicator is not an attribute, thus there is no true positive confirmation that the asset is FAST reportable. Example: User could set it to No and then enter a Mfr Name such as "GM" which is a valid FAST Mfr value.
Recommended:
Add a FAST Indicator value to the Mfr Part Nbr table to identify assets associated with this mfr part nbr record, that the asset is FAST reportable. Update the process to populate the value, add to grid / inquires, reports. Sync Fast Indicator with M&U. Modify logic in M&U for determining FAST reportable assets.
Mission Critical:
This change will enable DPAS to validate the asset is FAST reportable at the Mfr Part Nbr level.
Benefits:
Improves accuracy for FAST Reportable assets. Eliminates Maintenance Activities being able to not report commercially designed vehicles.
Nearly All - Most components / agencies that utilize DPAS have commercially design vehicles that required FAST reporting.
Partially Completed – Release 2022.3.1 – 18 November 2022
Completed – Release 2023.1.1 – 13 January 2023 |
|
| 01811 | Multiple Location Condition Code per Stock Number | Warehouse | AF: DF-VEHS | New | Description:
DPAS Warehouse limits Location Condition Code for a stock number to one Location Id. When receiving multiple quantities of a stock number under a single document, all will default to the single location and then need dispersal to various locations. Each warehouse will have multiple locations that require the same stock number and have a single Due-in, Backorder, or Return created to replenish or restock the items.
Recommended:
Allow multiply Location Condition Codes for same stock number. Enables user to chose several locations by quantity they would like to receive/return stock numbers streamlining process.
Mission Critical:
This is not critical or mandated, however improving system efficiencies decreases time warfighter spends performing non-wartime tasks
Benefits:
Automation provides a time reduction searching commonly received stock numbers for warehouse location replenishments (e.g.,individual issues). Additionally, potential to eliminate or reduce misplaced items within warehouse. Allows warfighter to focus on critical mission tasks vs. assigning warehouse replenishment locations.
ALL Warehouse |
|
| 01810 | DBO Table Deprecation | Enterprise | Leidos | Done | Description:
Currently DPAS duplicates catalog information across two separate database schemas which are kept in sync through the use of triggers. The planned improvement is to replace the triggers with views of the source tables to support catalog data within the PA / MU environments.
Recommended:
The catalog tables within the dbo schema will be removed and replaced with a synonym and view to allow the data to be accessed directly from the catalog schema within DPAS. This will ensure no data needs to be synced to the tables referenced by the PA/MU processes and they can function as they do today.
Mission Critical:
Mission Critical. DPAS should not be duplicating data in the system. Proposed changes will increase catalog process performance and ensure consistency of catalog data system wide.
Benefits:
DPAS will improve accuracy and accountability by ensuring consistency of data within the catalog
This change will impact/benefit all catalogers within DPAS
Partially Completed - Release 2022.3 - 04 November 2022
Partially Completed - Release 2023.1.2
Completed - Release 2023.1.4 |
|
| 01809 | Work Order Mass Edit | MU | Leidos | Done | Description: The initial DPAS modernization of M&U limited Work order provided single work order update. DPAS needs to restore the mass Work Order Update.
Recommended:
Allow for the selection of multiple work orders and enable edit of the selected group of work orders as one transaction.
Mission Critical:
Mission Critical - users need the ability to make the same edit to multiple work orders at once to reduce error and increase productivity.
Benefits:
Reduces Time and Cost associated with making the same edit multiple times for different work orders
Users:
All
Partially Completed – Release 2022.3.2 – 02 December 2022
Partially Completed – Release 2023.1.1 – 13 January 2023
Partially Completed – Release 2023.1.2 – 27 January 2023
Partially Completed – Release 2023.1.3 – 10 February 2023
Partially Completed – Release 2023.2.1 – 07 April 2023
Partially Completed – Release 2023.2.2 – 21 April 2023
Partially Completed – Release 2023.2.3 – 05 May 2023
Partially Completed – Release 2023.2.7 – 30 June 2023
Completed – Release 2023.3.3 – 11 August 2023
|
|
| 01808 | MAM Mass Edit | MU | Leidos | Done | Description:
The DPAS modernization initially provided for the user to input 3 parameters when mass profiling assets within the Maintenance Asset Master process. The capability to mass profile all fields that the previous version of the Maintenance Asset Master process had needs to be implemented. .
Recommended:
Add the remaining parameters to the mass update capability
Mission Critical:
Mission critical - DPAS users need the ability to update multiple records at one time beyond the three parameters currently available
Benefits:
Reduces time/cost associated with requiring individual edit on numerous MAM records
Users:
All
Partially Completed – Release 2022.3.3 – 16 December 2022 Partially Completed – Release 2023.1.3 – 10 February 2023 Completed 2023.2.1 |
|
| 01807 | ServiceNow DPAS Interface | Enterprise | USAF FF-GEIT | New | Description:
The EITaaS IPO has asked our SAIC partners, as a part of our Risk Reduction Effort, to demonstrate that they can integrate with DPAS and leverage ServiceNow (Our approved system of record) to do asset management across the EITaaS portfolio.
Recommended:
The primary and preferred method to interface with DPAS is via REST (JSON payload) or SOAP (XML payload) over a secure HTTPs connection (TLS 1.1v or greater). A diagram has been provided/is attached with this SCR from the EITaaS SAIC team.
Mission Critical:
Development of this interface was mandated by the EITaaS IPO.
Benefits:
A ServiceNow input going to DPAS is requested to provide accurate records for asset management.
Users:
Yes, this will be an interface to provide all data from the FF-GEIT site to ServiceNow.
|
|
| 01806 | Support for Warranty & Service to M&U Work Order | MU | Leidos | New | Description:
Provide the ability to associate warranties, subscriptions, or service contracts to an asset and display the contracts within Work Order when the asset is used.
Recommended:
Create a Warranty/Subscriptions service that can be used to create a Warranty/Service/Subscription contract and then allow for the contracts to be associated to one or many asset ids within maintenance. When an asset id that has Warranty/Service/Subscription contracts associated is used for a Work Order display the contracts in a Warranty/Service/Subscription panel within the work order so the user can view the contract terms.
Mission Critical:
Mission Critical. Numerous assets fall under warranty/subscription/service contracts that effect the types of work that will be done within a specific work order. Having this information available within the work order process will ensure the proper maintenance of assets.
Benefits:
Enables user awareness to specific warranties/service/subscription contracts that may limit the scope of a work order and ensure proper maintenance of the assets within a Maintenance Activity.
Users:
ALL
Partially Complete - Release 2022.2.3 - 07 October 2022 |
|
| 01805 | Deferred Tasks/Parts | MU | Leidos | Done | Description:
Work Orders cannot be closed when it includes outstanding parts requests. Allow for a work order that includes outstanding parts requests to be closed, and maintain the requirement for the outstanding parts for the associated Asset for future work orders.
Recommended:
Allow the user the ability to defer a task and select the outstanding parts that are no longer needed as a result of the deferred task. Maintain a record for the Asset ID of the tasks/parts that were deferred and alert the user of these deferred tasks on future work orders where the same Asset ID is used and allow for them to be added for the new work order.
Mission Critical:
Mission Critical. Priority for specific parts requests can change after a work order has been created to request those parts even while the parts are still needed. Without the ability to defer parts request either the Work Order would need to remain open and inhibit use of the associated asset or it would need to be closed and the part requirement would be lost.
Benefits:
Improves the use of the Work Order process to accommodate changes in demand of Assets in relation to the priority of parts requests. This part of the DPAS modernization effort.
Users:
Maintenance & Utilization - Work Order
Warehouse Mgmt - Maintenance Issue
RequisitionPartially Completed – Release 2022.3 – 04 November 2022
Completed – Release 2023.1.3 – 10 February 2023 |
Disclaimer | Accessibility
Please be advised that Navy Property Accountability module users will be unable to access ELMS during the period beginning 3pm EST on Tuesday September 29th, until 8am EST on Friday October 2nd due to the annual EOFY lockout period. If you have questions, please direct them to the Navy PP&E Management Support Office via their centralized email inbox, which is
Please be advised that ELMS will be unavailable beginning Friday, October 2nd at 9:00 pm EST for server maintenance. Estimated downtime is stated to last up to 60 minutes in length - please plan accordingly.