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 |
|
|---|---|---|---|---|---|---|
| 01844 | Ad Hoc Kit | Warehouse | Army: ASA(ALT) | New | Change Request: New System process
Description:
Add the capability to have a Set, Kit, Outfit / End Item->Component relationship with having to catalog a SKO.
Recommended:
ASA(ALT) utilizes DPAS to manage fieldings. Items are often purchased separately and fielded as a kit that is not 100% standard. It could be a kit that is assembled for evaluation / testing that is sent off. There could be multiple variations in order to conduct the valuation needed to determine what the final configuration will be.
Mission Critical: ASA(ALT) utilizes DPAS to manage fieldings. Items are often purchased separately and fielded as a kit that is not 100% standard. It could be a kit that is assembled for evaluation / testing that is sent off. There could be multiple variations in order to conduct the valuation needed to determine what the final configuration will be.
Benefits:
Having the capability to create an ad hoc kit if needed. It will save countless hours of developing Catalog SKOs that will likely never be used in fielding.
Frequency: Monthly
All ASA(ALT) programs will use this capability |
|
| 01843 | Form requests for MRO process | Warehouse | Army: ASA(ALT) | New | Change Request: Process Improvement
Description:
DPAS currently offers the DD Form 1348 for its Materiel Release Order (MRO) process. This form is normally used with wholesale issues / returns. ASA(ALT) utilizes the MRO process for Total Package Fieldings (TPFs). To support TFPs, the use of the DA 2602, DD Form 1149 and or DA Form 3161 forms or their DoD equivalents is more appropriate.
Recommended:
Add the following options for forms within the Materiel Release Order process
a. Add DA Form 3161 REQUEST FOR ISSUE OR TURN-IN or the DD form equivalent
b. Add DD Form 1149 REQUISITION AND INVOICE SHIPPING DOCUMENT
c. Add DA Form 2602 HAND RECEIPT/ANNEX NUMBER or the DD form equivalentMission Critical:
The use of these forms are more appropriate for the U.S. Army fielding of new equipment. See AR 710-2 SUPPLY POLICY BELOW THE NATIONAL LEVEL.
Benefits:
This change reduces ambiguity to the receiver of the items, and enhances user acceptance.
Frequency:
Daily
ASA(ALT) performs thousands of fieldings / year. |
|
| 01842 | Materiel Movement pFRID Capabilities | Warehouse | Leidos | New | Change Request: Process Improvement
Currently, the materiel movement processes with DPAS Warehouse do not support the identification of assets, container and locations utilizing passive RFID (pRFID) technologies. DPAS also does not support unique pRFID tag ids for bulk items in all modules as it should.
Provide the ability to identify and select assets and containers, for inventory relocation functions, using pRFID scanning technology.
Linear (barcode), 2D (data matrix) and Optical Character Recognition (OCR) scanning technologies require a direct line of sight in order to read the identification markings. RFID allows for the detection of one or more tags within an adjustable vicinity or read range without having to physically touch or move the asset or container. In most cases, RFID formats can determine the type of asset identified - location, container or asset.
Accuracy, efficiency and time savings. Provide consistently throughout the DPAS processes and conform to pRFID industry standard.
All warehouse, inventory managers can benefit from using this functionality.
Partially Completed – Release 2023.1.5 – 10 March 2023 |
|
| 01841 | Appointment Scheduler Updates | Warehouse | Leidos on Behalf of USMC | Done | Change Request: Process Improvement
Description: Currently, members arriving at the centers for an update to their unit assignments causes disruption to the flow of members seeking to receive or return their gear. This is administrative work and currently there is no method to channel them to a single lane, dedicated to making updates to the member's profile. Additionally, the Appointment Queue, used to display a prioritized list of members who have checked in and awaiting service, only displays 3 columns of scheduled and 1 column of walk-in appointments, each column holding 9 member appointments. As there are no appointments being scheduled at this time, this only allows (at most) 9 'walk-in' members on a single display page before rolling to the next page. Using a 70" display monitor, it should be able to display more than 36 total or 9 walk-in appointments. Recommended: Add a new appointment type - Permanent Change of Assignment (PCA).
Provides improved member visibility of where they are in the queue for obtaining / returning gear.
Better information, visible to the facility, in order to staff according to the member traffic within the center throughout the day. Eliminates members sitting around idle, waiting for their selected service to begin.
All issue and return facilities within the USMC, varies by facilities; typically 50 to 200+ members per day.
Partially Completed – Release 2022.3.2 – 02 December 2022 Completed – Release 2023.1.1 – 13 January 2023 |
|
| 01840 | DPAS Generate Equipment Status Report AFTO Form 244 | MU | USAF: SE | Done | Description:
There is presently no M&U Report or Form that produces something similar to the AFTO Form 244. The AFTO form 244 is the AF-mandated hard-copy/manual means to track and document maintenance discrepancies and inspections for equipment and is maintained on the equipment at all times to allow ready validation of serviceability, or to document discrepancies discovered during use. Require the ability to print pre-filled forms with data from M&U. This allows maintainers and personnel to quickly identify the serviceability of the asset.
Recommended:
Using Data in DPAS, create a Report or Form that provides the data contained in the AFTO Form 244 with field names changed to match DPAS M&U field names.
Mission Critical:
Mandated and critical. If an asset is dispatchable an AFTO Form 244 must be affixed to, and accompany the asset at all times. This form is the only way a user on the flightline can determine if a piece of equipment is serviceable and safe for use.
Benefits:
Ensures equipment is in a safe condition prior to use. Reduces time and improves accountability. It is a safety issue as the AFTO Form 244 is the conduit to communicate discrepancies or status of the asset to operators of the equipment. Policy impacted - AFI 21-101 and 21-103.
Users:
Affects Maintainers, Users of the Equipment, QA personnel. Currently there are 160,000 pieces of equipment bridged to our maintenance group LM. Estimate 60% of the assets in M&U (FH-AFHAF) require hard-copy AFTO Form 244's accompany the equipment at all times.
Partially Completed – Release 2023.3.3 – 11 August 2023
Completed – Release 2023.3.4 – 25 August 2023 |
|
| 01839 | DISA FAMIS-CS Interface Update | PA | DISA | Done | Change Request: Process Improvement
Description:
Update DISA's FAMIS-CS Interface to be the same as the FAMIS-WCF. Please use the FAMIS-WCF file layout specifications starting on page 21 for the FAMIS-CS file layout specifications starting on page 23 on the attached word file.
Recommended:
Update DISA's FAMIS-CS Interface to be the same as the FAMIS-WCF
Mission Critical:
Currently we are having to manually manipulate the interface every month for FAMIS to read/accept. This can lead to errors due to human intervention.
Benefits:
With DISA’s WCF moving to a OneFund (no split between the TSEAS & CS), we need the interfaces to be the same in order for FAMIS to read/accept both interface files.
Frequency: Monthly
All financial records and users managing this action DISA wide.
Partially Completed – Release 2023.1.2 – 27 January 2023
Completed – Release 2023.1.3 – 10 February 2023
|
|
| 01838 | Receive TCN data for ITV capability | Materiel Management | USAF AFHAF | New | Change Request: Policy/ Regulatory
Description:
As part of DOD mandated In-transit Visibility (ITV) the Air Force Distribution team assigns a Transportation control number upon receipt and acceptance of materiel being transfered off the installation. Currently, CMOS does not provide the TCN for assets being shipped via DPAS
Recommended:
Interface with source system to have this data element populated as part of the movement transaction, also include TCN for in-bound cargo
Mission Critical:
IAW Defense Transportation Regulation Part II Appendix L, Transportation Control Number (TCN) and Chap 202 Paragraph G Proof of Shipment, proof of delivery, and DOD In-Transit Visibility (ITV) Requirements
Benefits:
Compliance with DOD policy and regulations
Frequency:
Hourly
All |
|
| 01837 | Time Compliance Technical order (TCTO) Work Plan Modification | MU | USAF: AvSE | Done | Description:
Currently, there are no specific field names to be populated for TCTO work plan addition. This lack of specific TCTO field names is causing users to incorrectly input information into the wrong DPAS fields which makes traceability impossible for compliance tracking/monitoring. Lack of ability to ensure TCTOs are complied with prior to using equipment causes risk to aircraft, equipment, and personnel.
Recommended:
Recommend specific DPAS Field Names be created under Maintenance Work Plans - Plan Modify Work Plan Type Code "TCTO" to allow mandated TCTO information to be input for work plan creation. Specific fields for "TCTO Number", "TCTO Title", "TCTO Data code", "Est Labor Hours", "Est Hours to Perform", "TCTO Rescission Date (MM/DD/YY)". This Work Plan Type code will be utilized by sustaining Program Offices in conjunction with the Centralized Work Plan capability.
Mission Critical:
Mission critical and mandated. DoD MIL-DTL-33804, Technical Order 00-5-15, and Air Force policy outline requirements for TCTO processes. Currently, TCTO compliance cannot be accurately tracked/measured due to incorrect/inconsistent entries into the work plans. These inconsistencies prevent utilizing the report feature to track compliance through filtered excel reports.
Benefits:
By allowing for these specific DPAS Field Names to be created and utilized for work plan generation you instantly make reporting accurate and viable, as well as ensure the necessary information is correctly input into the archive system. Also ensures compliance with DoD MIL-DTL-33804, Technical Order 00-5-15, and DoD and Air Force policy.
Partially Completed – Release 2024.2.7 – 28 June 2024
Users:
This SCR would be a global benefit for any and all M&U users of who input and document TCTOs.
Partially Completed – Release 2024.2.4 – 17 May 2024
Completed - Release 2024.2.7 |
|
| 01836 | Maintenance Attribute Management | MU | Leidos | Done | Change Request: New System process
Description:
The DPAS diverse customer base results in DPAS having attribute requirements that do not apply to every DPAS customer's mission. To require every customer to managed attributes/functionality that does not apply to them results in unwanted / unnecessary overhead on the part of the customer. Recently DPAS received unique attribute requirements for the maintenance of aircraft parts and unique attribute requirements for the maintenance of boats. The objective of this SCR is to provide a method for the customer to self-mange unique attribute requirements by Stock Number.
Recommended:
Create a new process that will reside within the M&U module to enable maintenance personnel to identify the 'extra' attributes that are required to manage a specific type of assets (Stock Nbr level). The process will reside within the Catalog menu tree within M&U with the entries being available for use by all maintenance activities that are associated to the same Maintenance Program. The data will be stored by Stock Nbr for NSN and CAGE/Part Nbrs to enable the values to be applied to all like Stock Nbrs regardless of which catalog the Stock Nbr originated.
Mission Critical:
This SCR addresses how the specific attributes will be associated to a type of asset. This capability will be used to support the completion of the following SCRs:
1. SCR 01711 - M&U Corrosion Score and Coating Fields for Work Order Forms
2. SCR 01631 - Nuclear, Reimbursable, Mission Critical Indicator
3. SCR 01330 - Nuclear, Reimbursable, Mission Critical Indicator Reflect on Basic Work Order
4. SCR 01744 - UTIL Modification for Boat Engine Hours
5. SCR 01766 - MU Data Field Suppression for Boats/Craft
6. SCR 01767 - MU Data Field Additions for Boats/CraftBenefits:
This process will allow for numerous customizations within the application to increase accuracy as well as to create efficiencies within the processes that are customized
Frequency:
Daily
All customers that utilize the M&U module will benefit by the implementation of this SCR as it will reduce the number of attributes they will need to manage if it were not implemented with the completion of the SCRs identified in Type of Change section.
Partially Completed – Release 2023.1.6 – 24 March 2023
Completed – Release 2023.2.1 – 07 April 2023 |
|
| 01835 | Limit CICP data visibility by Commodity DoDAAC or Contract | Materiel Management | USAF GFM-A | New | Description:
The DPAS Catalog is established at the Logistics Program level today. Current AF CICP users have access to the entire catalog and stock item list under the AF CMP GFP Logistics Program. There are no access controls on the DPAS catalog other than role-based controls. DPAS should limit CICP access to only their data, as designated by commodity types, DoDAAC and/or contract number.
Recommended:
Create a sub-catalog for each AF CICP; to record stock number entries at the ICP and Materiel Mgt Program levels. Make use of the commodity types, DoDAACs and/or contract numbers in DPAS to limit use and viewing at the contract level. This will prevent everyone from seeing every stock number and standard price in DPAS warehouse.
Mission Critical:
The problem leaves the DPAS catalog open to all users. It is mission critical that CICPs cannot have access to other CICP data including stock numbers and standard prices.
Benefits:
Implementing this solution will prevent all users from seeing every stock number and standard price in the DPAS catalog and DPAS warehouse receiving process.
Users:
All AF GFM-A users of DPAS |

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.