System Change Requests

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: This email address is being protected from spambots. You need JavaScript enabled to view it..

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:

Scr Number	Title	ELMS Module 7,5,4,2,8,1,6,3 1,1,1,1,1,1,1,1	Reporting Org	State	Description
02106	FAST Disposition Reason	MU	AF: VSCOS	New	Change Request: Process Improvement Description: Process disconnect within UIC to UIC transfers for FAST Reportable vehicles. System requires FAST Disposition Reason input during transfer, however, the PA and M&U transactions prevent the gaining and losing Maintenance Activity (MA) to complete action. The gaining MA can profile a transferred asset if there is not a work order open for the asset. Normal process is the gaining MA profiles and opens a work order processing asset into new UIC. However, this actions prevents the losing MA inputting a FAST Disposition Reason to drop the asset from losing MA causing asset to remain within AWD status in the losing MA. This presents data integrity issue during FAST reporting as MA cannot input FAST disposition reason. Recommended: Completing PA UIC to UIC transfers within specific site generates an automatic system action (i.e., M&U) to remove AWD status from losing Maintenance Activity (MA). System must automatically clear the FAST Disposition Reason with ‘N/A – Not Applicable; vehicle is not disposed’ and generate an Open Action (e.g., Homepage display) notifying losing MA asset is no longer within MA and system transferred asset to gaining MA is complete. Additionally, system must generate an Open Action to clear any FAST Disposition Reason for all FAST Reportable assets disposition within PA. Finally, add a column to M&U MAM Search Results for AWD status. This allows another search tool identifying assets are ready for FAST Disposition Reason after PA disposition other than UIC to UIC as this is automatic as recommended above. Mission Critical: Department of the Air Force Instruction 24-302 VEHICLE MANAGEMENT, Section 8.4 Annual FAST Report Benefits: Streamline UIC to UIC transfer process by automating some of the steps, while ensuring accurate FAST Reporting by informing maintenance activity that FAST Disposition Reasons are ready/require action. Frequency: Daily Users: This process improvement benefits DOD agencies and military services on a daily basis.
02105	Work Plan Site Restriction	MU	AF	New	Change Request: Process Improvement Description: DPAS flexibility searching and selecting Work Plans causes data integrity issues within DF-VEHS site. Currently, DPAS does not limit search results to within specific site(s) and wide-open searches present all DPAS Work Plans allowing user to select incorrect plan. While Work Plan may look similar, the differences drive data inconsistencies easily preventable with site specific work plans. Recommended: Limit Work Plans (public work plans) to owning site (i.e., DF-VEHS), or an option within Master Data/Maintenance Program restricting system to site specific Work Plans (e.g., toggle). A toggle or restriction will resolve data integrity isse with reference to Work Plans and eliminate Work Plan selection confusion for all sites utilizing DPAS M&U. Mission Critical: Department of the Air Force Instruction 24-302 VEHICLE MANAGEMENT, Section 7C Vehicle & Equipment Work Order Benefits: Significantly increase data accuracy and streamline user experience with work order creation process. Frequency: Daily Users: This process improvement benefits DOD agencies and military services on a daily basis.
02104	Incorporate "Mark For" capabilities within Materiel and Warehouse Mgmt. applications	Warehouse,Materiel Management	Leidos	In Progress	Change Request: Process Improvement Description: USMC requires the capability to enter a "Mark For" Address. Currently DPAS does not support the "Mark For". The proposed solution is to incorporate the entry/selection of a Mark For (RIC/DoDAAC/MAPAD/Text) within CR, DRO and RDO within Materiel Mgmt and within MRO within Warehouse Mgmt. Recommended: 1. Modify CR, DRO, RDO to allow for the entry of the "Mark For". The "Mark For" will be transmitted to the RSA via the DLMS 940R. 2. The Warehouse Mgmt. application will inbound the DLMS 940R and include the Mark For" data in the MRO. When present in the DLMS 940R, do not permit change by warehouse personnel. When absent, allow warehouse personnel to enter a Mark For. 3. Include the "Mark For" data in the Transshipment DLMS 940R request that is transmitted to the TMS for inclusion in the print of the Shipping Label. 4. Incorporate the applicable "Mark For" data in the print of the DD Form 1348. Mission Critical: Supports MIL-STD-129P Supports DLM 4000.25 Supports DLMS 940R IC Benefits: Provides all DPAS customers that utilize Materiel Mgmt., and MRO within Warehouse Mgmt. with the capability to utilize "Mark For". Frequency: Hourly Users: This change impacts all customers of Materiel Mgmt. and those users of the MRO within Warehouse Mgmt.
02103	Delinquent Temp Loan Report	Warehouse	NBG-2	New	Change Request: Process Improvement Description: Organizational Tool Issue requires daily report of all temp loaned tools that are delinquent in their return; DPAS does not provide a report or inquiry with this parameter Recommended: Inquiries > Issue / Return Activity: Include Inquiry Type "Temp Loaned with Return Details", and engage the "Only Outstanding Items" to only show items currently outstanding Mission Critical: ACU4INST 5530.14L section 5.a.(3). Tools that have not been returned by 1600 to Tool Issue will be considered delinquent unless signed out overnight. The Commanding Officer of Assault Craft Unit Four mandates that an email be sent to all E-7 and above listing all delinquent tools each day. Benefits: Allows organizations to monitor temporary loaned assets that are delinquent in an concise report for distribution to leadership and all relevant personnel Frequency: Daily Users: 20
02102	Receipt Reversal	PA,Materiel Management	AF: A4/HAF FH-AFHAF	New	Change Request: Policy/Regulatory Description: Currently the only transaction that has a reversal process is the 'Disposal' process. In order for the ICP requisition to close out the 'Local Due-in' needs to be processed in PA for the 527R DLMS to be sent from the ICP to the SOS Materiel Receipt Acknowledgment (MRA) to close the requisition. However there have been instances where a receipt was processed in error, which has caused the ICP requisition to remain open. This has caused additional work, that requires DPAS to manually close out the requisition in ICP, and remove the 'Local Due-in' in PA, which neither process sends out the 527R TH MRA. Additionally the SOS also needs to manually close out the requisition on their end, all causing a break in the audit trail. Recommended: Create a reversal process for receipts that will also allow for the stock number/serial number combination to be utilized when reprocessing the receipt with the correct 'Local Due- In'. Mission Critical: DLMS 4000.25 Vol 2 Chap 10 Benefits: This will limit the additional workload of manually closing out a requisition and rejecting the 'Local Due-in'. This will also ensure that the audit trail can be traced from the initial requirement to the receipt acknowledgment (527R TH) back to the SOS to close out the requisition. Frequency: Daily Users: All DAF activities processing receipts for ICP requisitions.
02101	Document Control role for attachments on pending transactions	PA	FH-AFHAF	New	Change Request: Process Improvement Description: Currently once an asset is in pending transfer or disposal the property record is frozen and the user is not able to attach any documentation to the property record Recommended: Create a new role that will allow for attachments to be uploaded while the property record in pending status ( ie. Receiving, Transfer, Dispositions) Mission Critical: In order to track physical possession of an asset, the losing Logistics Readiness Squadron (LRS) requires signature to establish positive control of assets as they are moved to losing outbound cargo section or gaining LRS. The DAF requires signatures for acceptance of the property in transit. Benefits: This meets FIAR compliance to ensure property Key Supporting Document (KSD)s are maintained and part of the property record from cradle to grave. Frequency: Daily Users: All users FH-AFHAF Site-id
02100	Add TAC address to Customer Requisition/RDO/DRO	Warehouse,Materiel Management	Leidos	In Progress	Change Request: Process Improvement Description: USMC requires the capability for the LOGCOM Item Managers to be able to assign the transportation account code to be used with the shipment of the (CR,DRO,RDO). Currently DPAS has the TAC the assignment within the Warehouse MRO process. USMC has requirement to allow the Item Managers to select specific assets (Serial Nbr / UII) for shipment. Currently DPAS provides for this information to be entered within the instruction area. Recommended: 1. Modify CR, DRO, RDO to allow for the entry of a TAC. The TAC will be transmitted to the RSA via the DLMS 940R. TAC will be optional as not all issue actions require transportation services. When the TAC is absent, allow the warehouse to enter it. When entered by the Item Manager, do not allow the warehouse to modify the value. 2. Modify CR, DRO, RDO to allow for the selection of specific assets by Serial Nbr / UII. When selected, this information will be transmitted to the RSA via the DLMS 940R. Within the MRO process of the DPAS warehouse application, feed the serial nbrs/uii into the inventory selector along with Stock Nbr, Condition Cd, Purpose Cd, and Project Cd. Should the RSA not able to pick / ship the specific item, deny the issue request via the DLMS 945A. Mission Critical: These changes implement Defense Logistics Management Standards Changes 1462B (Serial Nbr / UII addition), and 1206 (Transportation Account Code) Benefits: Provides USMC the capabilities required to communicate systematically with RSA systems. Frequency: Daily Users: This change impacts all customers of Materiel Mgmt. Partially Completed - Release - 2025.1.6
02099	Access History Inquiry	Enterprise	VSCOS	New	Change Request: Process Improvement Description: DPAS is in need of an inquiry system that provides clear visibility into user access history for both current and past role assignments. This data is essential for IO’s and AIO’s as it helps them verify whether users have the appropriate roles and access levels. Without this information it becomes challenging to assess compliance and ensure that users are not over-privileged or under privileged. Therefore, implementing such a system is crucial for maintaining proper access control. The challenge of meeting organization audit requirements significantly affects the ability to conduct a thorough DPAS annual user access review. This situation makes it difficult to ensure that only authorized individuals have access to sensitive information. Additionally, the ongoing monitoring of user access becomes less effective leading to potential security risks. Without proper oversight the organization may struggle to identify unauthorized users or detect unusual activities. As a result maintaining a secure environment becomes increasingly challenging. Having clear visibility into data management processes is crucial for DPAS Security and Support personnel. This transparency reduces the need for Database Administrators (DBAs) to run scripts just to collect necessary information for organizations and audit Program Control Boards (PCBs). With easier access to data support teams can respond to user inquiries more quickly and effectively. This improvement not only benefits the users but also helps Information Owners manage their data better. Overall enhancing visibility streamlines operations and increases efficiency across the board. Recommended: Creating an Access History Inquiry is essential for monitoring user permissions. This inquiry will provide clear records of when a user's tier and role access were added or removed. It will display both current and historical information showing the exact date and time of each change. By organizing this data administrators can easily track adjustments and ensure users have the correct access levels. Overall, this tool will help maintain security and accountability within the system. Mission Critical: Each year IO/AIO is responsible for conducting a user audit and informing the DPAS PMO once it is completed. Monitoring roles and user access such as ensuring there is a separation of duties and preventing unauthorized access to MAs or warehouses is crucial for every agency. Unfortunately the current system tools used for this task are displaying incomplete information making it difficult to effectively perform these important functions. Benefits: By providing an history Inquiry for UIC and Maintenance Activity the IO/AIOs will have a clearer understanding of the UIC and Maintenance activity required for each user. This will help in determining whether these UIC or Mx Activity are essential for the user to effectively utilize the system. Having this history will streamline the process of assigning UIC and Mx Activity ensuring that each user has the necessary permissions and access rights. This will ultimately lead to a more organized and efficient system for all users involved. Frequency: Daily Users: Unsure how many Agencies and IO/AIOs are in DPAS, but this will impact all of them.
02098	Enterprise Appropriation Tech Refresh	PA	Leidos	In Progress	Change Request: Process Improvement Description: The Appropriation AUD screens in DPAS PA and MM modules do not employ modern technical solutions, and the fields in PA and MM Appropriation are not equivalent, containing different fields. This SCR is to Tech Refresh the Appropriation AUD to enable it to be deployed as part of the enterprise accounting service for use with all DPAS applications. The appropriation attributes will be updated to use the Standard Financial Information Structure (SFIS) attribute names. Recommended: Modernize the Appropriation AUD process for DPAS Accounting and match the PA Appropriation fields to the modernized Appropriation fields. Mission Critical: The data elements in DoD OUSD SFIS guidance, Standard Line of Accounting business practice, and DLMS implementation business rules use modern nomenclature currently not used in PA Appropriation AUD. In addition, DoD FMR 7000.14R requires certain data elements to be used in accounting processes. Benefits: Modernized functionality and similar fields across DPAS modules within Appropriation AUD processes. This will also better prepare Accounting to handle Fixed Asset accounting transactions. Frequency: Daily Users: Data established in this process is used by Accounting users on a regular basis. This will impact enterprise accounting which will affect a growing number of users as more use the accounting processes.
02097	Adding MAJCOM filter to Inquiry	MU	AvSE	New	Change Request: Process Improvement Description: Currently, the DPAS Maintenance & Utilization (M&U) module does not allow users to filter or sort inquiries by MAJCOM (Major Command). This limitation complicates the ability to quickly locate and analyze data specific to a particular MAJCOM, resulting in inefficiencies in reporting and decision-making processes. Users must manually sift through extensive datasets to isolate MAJCOM-specific information, which increases the risk of error and reduces productivity. Recommended: Enhance the inquiry search functionality to include a dropdown menu or selection box for MAJCOM as a filter criterion. This would allow users to limit inquiry results to a specific MAJCOM. Mission Critical: MAJCOM A4 leaders are not able to pull single, all-encompassing report for their respective MAJCOM maintenance activities at this time. They do not have access to PA, only the M&U module, so it is imperative that they are able to over high-level oversight of their AvSE fleet health. Benefits: Reduces time spent searching and analyzing MAJCOM-specific data, Increases accuracy by eliminating manual data isolation errors, Streamlines reporting and decision-making with faster, targeted insights, Improves user experience by simplifying searches and enhancing system usability, Aligns with organizational goals for data-driven decisions and efficient resource management. Frequency: Daily Users: The inquiry process is used by 100s of users multiple times a day.