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
01636	DPAS Tech Refresh - Background Process Manager / Pendulum (Job Scheduler)	Enterprise	Leidos	Done	Description Provide single point, end user capability for managing/scheduling jobs as well as to receive critical production feedback on issues for analysis and resolution. Recommended The initial focus will be operations based – triage, research, issue identification and resolution. Additional functionality will be submitted for monitoring and possible trend analysis in the form of a configurable dashboard. Mission Critical This was mandated as a requirement of Tech Refresh. Benefits improved production support capability improved visibility to system and application status improved research, triage and error identification tools Users Prod Support Team Partially Completed – Release 2022.3 – 04 November 2022 Partially Completed - Release 2022.3.1 Partially Completed - Release 2023.1.2 Partially Completed - Release 2023.1.3 Partially Completed - Release 2023.1.6 Partially Completed - Release 2023.2.3 Completed - Release 2023.2.7
01635	DPAS Tech Refresh - Common Asset Model	Enterprise	Leidos	New	Description Establish a DPAS common asset model to support the DPAS Tech refresh work effort. Recommended DPAS will provide a centralized asset structure that is accessible to all DPAS processes and platforms. This structure will contain a core set of attributes that are common to all DoD business processes. Process specific attributes will extended off of the Common Asset structure in a "hub and spoke" model. The Common Asset structure will provide an enterprise wide method to uniquely identify each asset in DPAS and share those common attributes throughout the system. Microservice API(s) will be established, use-able by all development teams to insert assets into the new asset structure. This SCR requires that the Common Asset structure support both the new model and the existing, disparate asset models in DPAS today. The Common Asset structure should maintain an in-sync balance between old and new models until all processes have transitioned to the new Common Asset structure. Reports and monitoring will be provided to monitor/ensure balance between the asset model and the legacy DPAS application as organizations/DPAS transitions to the tech refresh framework. Mission Critical This was mandated as a requirement of Tech Refresh. Benefits The separation of the common asset attributes and the extension tables by specific platform provides a more efficient application design which limits risk by isolating changes to the asset model to specific platforms and its related asset attributes. Provides full visibility of the full life cycle of the asset, regardless of activity or platform. Users All
01634	DPAS M&U Tech Refresh	MU	Leidos	Done	Description Update Maintenance and Utilization functionality to support the DPAS Tech refresh work effort. Recommended Update the GUI to have a more modernized look Update the back end to increase speed and user performance Mission Critical N/A Benefits Improved Customer experience for all DPAS Users Users ALL Partially completed -- Release 2021.2 - 28 May 2021 Partially completed -- Release 2021.3 - 10 Sept 2021 Partially Completed – Release 2021.4.1 – 07 January 2022 Partially Completed – Release 2022.1.1 – 22 April 2022 Partially Completed – Release 2022.2 – 26 August 2022 Partially Completed – Release 2022.2.1 – 09 September 2022 Partially Completed – Release 2023.1.2 – 27 January 2023 Partially Completed – Release 2023.3.1 – 14 July 2023 Completed - 2023.3.1
01633	DPAS Tech Refresh Catalog	Enterprise	Leidos	Done	Description Update the DPAS Catalog functionality to support the DPAS Tech Refresh work effort. Recommended DPAS will provide a centralized Catalog that is accessible for all DPAS processes and assets. The DPAS Catalog will provide a core set of attributes that are common to all features with extendable attributes sets that are required for specific platform and their features. Mission Critical N/A Benefits Improved customer experience for all DPAS Users. Users All Partially Completed -- Release 2021.2 - 28 May 2021 Partially Completed – Release 2022.1 – 08 April 2022 Partially Completed – Release 2023.2.1 – 07 April 2023 Partially Completed – Release 2023.2.2 – 08 April 2022 Completed – Release 2024.1.1 – 12 January 2024
01632	PA DLMS 856S/527D Changes	Enterprise	Leidos	Done	Description: When the 527D/856S DLMS process was added into PA, the MILS fields were hard-coded. AFSOC needs us to change how this process works to allow users to select values for those hard-coded fields, as well as make the RIC fields optional. Additionally, we need to fix the 527D/856S process to inbound correctly to the Warehouse module via the DLMS processor. Recommended: In PA, when the 527D/856S DLMS process is executed as Disposition>Transfer Out-Outside DPAS, the MILS fields should be available for users to select values, as well as make the RIC fields optional for the "from" and "to" addresses. Also, fix the 527D/856S process to inbound correctly to the Warehouse module via the DLMS processor, and fix the UIC DoDAAC/CAGE add/delete process to allow for DLMS fields to be added/changed when a DoDAAC/CAGE is re-added after it's been deleted. Mission Critical: Required by AFSOC Benefits: Improves the function of these DLMS processes out of PA Users: Certain users who utilize DLMS transactions out of PA Disposition Completed – Release 2020.3.1 – 23 October 2020
01631	Nuclear, Reimbursable, Mission Critical Indicator	MU	AF: VSCOS	Done	Description DPAS does not identify an asset as nuclear certified, reimbursable or mission critical when opening a work order. Fleet analysts and technicians need a simple, standard and repeatable solution to distinguish nuclear certified, reimbursable or mission critical assets to properly manage, direct actions or perform maintenance. Recommended Create Nuclear indicator (NCE), nuclear restricted indicator (NCE-R) and nuclear restricted remarks (i.e., Restricted Remarks) fields to reflect an asset as nuclear certified in 3 locations; the Custodian Asset Report (inventory), the MAM in M&U and on the asset work order (electronic and/or print). Add checkbox in the "fields" section of both PA and M&U inquiries allowing queries and quick identification of nuclear certified assets. Ideally, load the nuclear indicator against the NSN at the catalog level with a field indicating "NCE". However, the Air Force requires editing field because assets within a specific NSN become restricted and the ability to remove the NCE designator from a specific asset, switching to NCE-R. Recommend accompanying the NCE-R designator field with a "restricted comments box" with enough free text characters to easily input why restriction exists on a nuclear asset. Additionally, add two additional fields identifying Reimbursable and Mission Critical assets. Recommend drop down field selections with A/U/D on the MAM. Locate the fields on the Basic tab. Name the Fields and drop down selections: "Remb/Refd" with provisions to choose either "3" for reimbursable or "4" for refundable" and "Msn Crt" displays a "C" for mission critical. Blank Fields for the conditions not applicable. The field names Remb/Refd and Msn Crt must reflect on the basic work order (electronic and print) when processing a work order. Additionally, all fields (to include cost centers) must be easily identifiable when pulling a Maint Asset inquiry or a work order/sub work order inquiry. Mission Critical Critical. It is imperative Air Force managers and technicians know a nuclear certified asset's certification to handle special cargo. Nuclear certified assets follow additional rules governing maintenance; requiring the technician an easily identifiable indicator on the work order for compliance with AFI 63-125, Nuclear Certification Program. Furthermore, it is imperative an easily identifiable indicator and inquiry for refundable or reimbursable assets to manage sustainment funds as well as the ability to easily identify mission critical assets per AFI 24-302, Vehicle Management. Benefits Benefits of implementing change includes safety and movement of special weapons, proper accountability of nuclear support equipment mission sets, saving research time opening a work orders, potential improper maintenance actions on nuclear surety assets, and proper visual restriction of nuclear certified status. Additionally, save time identifying refundable and reimbursable assets as well as improve accuracy of financial reporting. Users All Air Force asset managers (i.e., vehicles and equipment) utilize this information for day-to-day management purposes. Partially Completed – Release 2023.2.4 – 19 May 2023 Partially Completed – Release 2023.2.7 – 30 June 2023 Partially Completed – Release 2023.3.3 – 11 August 2023 Completed - Release 2023.3.3
01630	Include Safety Stock % in LPWHR82 - Inventory Over Under Report Calculation	Warehouse	AF: AFERMS	Done	Description LPWHR82 - Inventory Over Under Report - does not include the safety stock percentage into stock number calculation Recommended Update Inventory Over/Under Report LPWHR82 to incorporate MIN/MAX safety stock percentage into stock number calculation. Mission Critical Benefits accuracy of report information Users ALL AFERMS Completed – Release 2021.1.1 – 26 February 2021
01629	MAINTENANCE ASSET UTILIZATION INQUIRY REPORT FOR DPAS - RRAD INQUIRY AND RFI	MU	Army	New	Description There is no way to divide the equipment out when running utilization report. By adding office id to this report we could sort by Cost Centers. RRAD Equip Control Clerk, Jose Arredondo (903-334-2115) asks, "Can the "Office ID" option found in the Dispatch Inquiry report be made available in the Maint Asset Utilization Inquiry report?" Recommended To add office ID (Cost Center) to utilization reports. RRAD states: "I am needing this information on the Maint Asset Utilization Inquiry report in order to separate or sort by Office ID." Mission Critical This is a critical to reporting to the users and the management for the depot to right size the fleet at RRAD. TACOM (MSC) concurs based on site visits for the Command Inspection Program that this would be very beneficial to their organization and for our analysis. Benefits Reduces time to look up each vehicle. With this added field we would be able to sort by office ID(Cost Center). As well, there becomes an ability to better manage fleet utilization. Again, as well, the MSC can track the subordinate organization for cost effectiveness in fleet management during VAM and CIP. Users This affects all users.
01628	DoDAAC	PA	AF: AFEMS	Done	Description When processing a Disposition or Transfer with the DAAS interface on the document number needs to change to reflect the gaining UICs DODAAC. Recommended When assigning the document number automatically default to the gaining DODAAC when interface is on. Mission Critical Mandated by system, error occurs if DODAAC in the document number isn't changed. Benefits Reduces time Users yes Completed – Release 2023.1.6 – 24 March 2023
01627	Mass UIC to UIC	PA	AF: AFEMS	In Progress	Description Property records on an existing UIC require a mass UIC to UIC transfer when a unit is re-designated and a new UIC is established. Recommended Propose that the system internally updates the master data file to reference the original UIC and move all custodian records to the new UIC. Mission Critical Mission critical, as a unit designation changes, the property records need to be reported against the correct UIC. Benefits Improves accountability and accuracy Users yes Partially Completed - Release 2024.4.1 - 04 October 2024

×

Home | Security Notice Official Defense Logistics Agency Logo

Disclaimer | Accessibility

Defense Logistics Agency (DLA)
Logistics Catalog and Data Solutions (LCDS)