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
02136	Changes to SKO Screens - 1b	Warehouse,Materiel Management	USMC	New	Change Request: Compliance Requirement Description: During MARCORLOGCOM's evaluation of the Set, Kit, and Outfit (SKO) capability, it was observed that in several location in the process the LIN/TAMCN and or National Stock Number (NSN) of the Parent were missing in search grids and component grids. In addition, the Marine Corps is requesting the ability to add a component type when adding associations for the parent to its components. Recommended: 1.0 "ICN Inventory Update Inquiry" when selecting the components of a Parent NSN, the system does not display the Parent NSN nor Parent LIN/TAMCN in the SKO summary view. The following requirements are required to gain the required functionality associated with WSMC business processes. 1.1 On the "Inventory Update Inquiry", after selecting a specific serial number known to have a TAMCN, the component Grid did not contain the Parent LIN/TAMCM or the Parent NSN. The system shall be modified to display the Parent LIN/TAMCM and the Parent NSN on the SKO summary view. (see attachment) 1.2 The system shall add ‘Component Type’ drop down containing the below value set on the ‘Component’ tab of the "SKO" Add screen. (see attachment) a. SSRI (child) b. SL3 c. SL4 d. DLR e. Collateral Material 1.2.1 The system shall add the "Component Type" to all search criteria associated to SKO. 1.3 The system shall provide the end user with a capability to search by LIN/TAMCN, This functionality is currently missing from the SKO Add screen. (see attachment) 1.4 The system shall add a criteria for the end user to be able to search by LIN/TAMCN on the “SKO Catalog Landing Page” 1.5 The system shall add a criteria for the end user to be able to search by LIN/TAMCN on the “SKO Catalog Landing Page” Options selection. 1.6 In the “ICN Inquiry” add ‘Component Type’ drop down containing the below value set as a ‘Search Criteria’ Field to the ICN Inquiry Landing Page: a. SSRI (child) b. SL3 c. SL4 d. DLR e. Collateral Material 1.7 On the “SKO Assembly Process Screen”, the system shall add LIN/TAMCN as a default grid option and a search criteria option. (see attachment) 1.8 On the "Kit Assemble" screen, when selecting serial number in the search criteria, the system shall be modified to display the Parent LIN/TAMCN. 1.9 On the "Kit Assemble" screen, when selecting serial number in the search criteria, the system shall be modified to display the Parent LIN/TAMCN in the Kit Details area. Mission Critical: This is a critical 1.b requirement that must be satisfied prior to MARCORLOGCOM's implementation. Benefits: Meets MARCORLOGCOM's business model Assists in 100% accountability of assets Complies with current audit controls Frequency: Daily Users:
02135	Assignment of Orphan Status and Shipping Translations - 1b	Warehouse,Materiel Management	USMC	New	Change Request: Process Improvement Description: Currently, it has been observed in ELMS that when Status and Shipping notifications (870S, 856S, 870M/FTL, and 856R/FTM) DLMS transactions are received and there is no due-in present, the intended ICP nor warehouse has the inbound shipment recorded in the system as due in to their location. In short, the transaction exceptions out and no further action is done in ELMS to allow visibility of these transactions without manually hunting them down. This lends itself to frustrated shipments. Recommended: 1.0 Requirements for dealing with intransit transactions transmitted by DAAS where there are missing due-in leading header transactions records. 1.1 When and inbound transactions indicates an Owning-RIC tied to and ICP within ELMS (MPT) or is intended for one of the Remote Storage Locations (RSAs) connected to an ICP, ELMS shall automatically generate a 527D/DWZ (Preposition Material Receipt (PMR)) record for all inbound DLMS transactions (870S, 856S, 870M/FTL, and 856R/FTM) That does not have a due-in resident in ELMS. 1.1.1 If the inbound transactions has a REF/SE or REF/U3 segment populated identifying serial numbers or IUID. the ELMS system shall record that information as part of the due-in record. 1.1.2 The newly established due-in and follow-on status should be recorded at the Material Management (ICP) level and on the document control records of the intended receiving warehouse as an intransit due-in. 1.1.3 If the NSN identified on the inbound transactions is not loaded to the Stock Item catalog of the RSA where the asset has been shipped to, and the NSN resides on the Enterprise LP catalog, ELMS will automatically load the NSN to the Stock Item catalog for that RSA. 1.2 Upon receipt, ELMS shall record the document as a 527R/D6Z showing that the document was receipted for from a document that had NO due-in recorded. 1.2.1 ELMS shall allow all KSDs to be attached to the document in support of audit requirements. 1.2.2 ELMS shall provide a capability to access and retrieve the completed document both from the Material Management (MM) module and the Warehouse Module (WM). 1.2.3 At the same time ELMS produces the 527R/D6Z DLMS transactions it shall also produce the required 527R/DRA and transmit it back to the originator of the shipment. 2.0 If a 527R/D6_ is received from an external storage point, the system shall build the corresponding 527D/DW_ (Preposition Material Receipt (PMR)) record and allow for the posting of the receipt under the Material Management (MM) module under the associated ICP. Mission Critical: Benefits: Meets MARCORLOGCOM's business model Assists in 100% accountability of assets Complies with current audit controls Frequency: Daily Users: All users with Material Managers, WH Managers, and ICP users
02134	Filtering Process for PIEE WAWF Receipt Transactions	PA,Warehouse,Materiel Management	Leidos	New	Change Request: New System Process Description: The setup of PIEE WAWF for the ELMS user must be performed within PIEE. 1) Often times the APO doesn't know who their WAWF coordinator is, 2) the setup isn't specific enough to prevent non-property book receipts from passing to ELMS causing review / deletion of unwanted Due Ins, and/or 3) it requires constant WAWF configuration maintenance between the Accountable Property Officer (APO), and their WAWF coordinator to tweak the WAWF setting in an attempt to receive the desired receipts. Recommended: Create a WAWF filter process on the ELMS side that will provide the APO a filtering process to filter in / out receipts they want to see as Due Ins in PA and/or Warehouse. Once in place, ELMS will enable 100% of the organization's WAWF receipts to flow to ELMS using the ELMS WAWF filtering rules established by the APO to determine which receipts will become a Due In. ELMS will also provide the APO with a view of those receipts that were filtered out and allowing the user select ones that should have created a Due In to be processed into a Due In. Mission Critical: This change incorporates additional PIEE WAWF functionality within ELMS. Benefits: This change will provide improved integration between PIEE GFP and ELMS (APSR). Frequency: Daily Users: All ELMS users that use the PIEE WAWF interface.
02133	PIEE GFP Business Process Improvements	PA,Warehouse,Materiel Management	Leidos	New	Change Request: New System Process Description: PIEE GFP is adding functionality that will enable it to report to the material owner's Accountable Property System of Record (APSR) such as condition code changes and disposition actions via the DLMS 947I Inventory Adjustment Transaction Set. See DEDSO's website for the DLMS 947I Implementation Convention. Recommended: Modify ELMS to accept the DLMS 947I from PIEE GFP and update / remove the material from DPAS. This change will require locating the item in ELMS (PA, WM or MM) and performing the action plus all sub actions to include reporting the financial change should item be financially reportable. Mission Critical: This change incorporates the additional PIEE GFP functionality within ELMS. Benefits: This change will provide improved integration between PIEE GFP and ELMS (APSR). Frequency: Daily Users: All ELMS user with GFP.
02132	Intransit Document Review and Verification - 1b	Materiel Management	USMC	New	Change Request: Process Improvement Description: Current ELMS processes do not provide the end user with serial number detail within the In-Transit Review process to search for and close intransit shipments with an approval process. When documents are sent to an outside entity that cannot reply transactionally confirming receipt of a shipment, it is the responsibility of the Inventory Manager, when Material Management (ICP) module is being utilized, to close out the intransit record once the Key Supporting Document (KSD) is supplied. The in-transit review process will need to have serial number detail to facilitate the processing and closeout of shipments. Serial number level details are specifically needed for instances where the confirmation quantity does not match the shipment information (Either with KSD or Responses that are short). Recommended: The ELMS system shall be enhanced to include a serial number search capability within the “Intransit Review” screen, allowing users to locate and verify specific intransit records. Upon selection of a shipment, all associated serial numbers will be displayed, automatically checked upon first entry. Users will have the ability to uncheck serial numbers not verified as received based on the Key Supporting Document (KSD). A new Stage Code “DS – Discrepant Shipment” is requested to flag and clearly display discrepant serial numbers or quantities. This is a critical enhancement, as current functionality lacks the capability to drill down by serial number for intransit shipment verification and closeout. This feature is necessary to enable Inventory Managers using the ICP module to validate and close shipments when transactional confirmation is not available, ensuring compliance with audit standards. Refer to the attached USMC BRD for additional detail. Mission Critical: This process allows the user to properly adjudicate and confirm in transit shipments, when the receiving agency does not confirm receipt, or confirms receipt with errors or discrepant quantities. Benefits: -Meets MARCORLOGCOM’s business model. -Ensures the accurate closeout of in-transit shipments based on Key Supporting Documents received at external RSA's, DLA-DS, or other entities that do not respond appropriately via DLMS Transactions. Frequency: Daily Users: This SCR will support all users of DPAS Material Management, and clean up an issue with the validation of serialized assets when the quantities do not match between what was shipped and the KSD Received.
02131	TAC Code AUD Table - 1b	PA,Warehouse,Materiel Management,Enterprise	USMC	New	Change Request: Process Improvement Description: ELMS currently does not allow for Transportation Account Codes (TAC) value set to be added to, updated, or values deleted from within the Material Management (MM) module. Inventory Manager (IMs) are often provided TAC codes to be used when redistributing inventory to other services or other entities from within the Marine Corps. The ability to add, update, and delete TAC codes is inherently the responsibility of the IMs using the Material Management module. Recommended: The ELMS Material Management (ICP) module shall enable Inventory Managers to Add, Update, and Delete Transportation Account Codes (TACs) within a controlled value set. Once valid TACs are available, managers can select a TAC when generating a 940R Material Release, which will be embedded in the transaction (segment N9, code "TH") and transmitted to the appropriate Remote Storage Activity (RSA) for further distribution. TAC control remains with the ICP when warehouses are linked. Refer to the attached BRD for additional details. Mission Critical: This process improvement is to allow for the USMC Enterprise Help Desk to make quick updates to the TAC Code to support emerging mission requirements. The DPAS Support help desk ticket to add a TAC Code has been determined pose risks to MARCORLOGCOM Weapon System Managers meeting mission timelines, and hence a User Update Process for this field is required. Benefits: -Meets MARCORLOGCOM’s business model. -Ensures timely processing of shipments in support of Global Force Management and Contingency requirements, that require the quick update of TAC Codes. -Ensures Accuracy of TAC Code Submissions to support interface with DLA Transportation Systems. Frequency: Daily Users: All MARCORLOGCOM Material Managers, and other DPAS Users who will use this process.
02130	ELMS Synchronization of Disconnected Environments	PA,MU,Warehouse,Materiel Management	Leidos	New	Change Request: New System Process Description: Disconnected ELMS instances currently lack a scalable and reliable method to exchange data with the enterprise system. This limits both the reporting of maintenance activity and the visibility of asset data at the enterprise level, which is critical for decision-making and readiness tracking. Recommended: Recommend implementing a Data Warehousing layer to act as a central hub for integrating and synchronizing data from both connected and disconnected ELMS instances. This would be supported by a synchronization process to export, encrypt, and transmit data from a disconnected ELMS instance, then decrypt, validate, and apply updates to an Enterprise ELMS instance. The same process would support downstream updates, such as catalog changes, to disconnected environments. Mission Critical: This is a new system process involving architecture enhancements, data synchronization routines, and visualization/dashboard capabilities for enterprise-wide maintenance and asset visibility. Note: This SCR is to develop a prototype for 2-way communication between the ELMS enterprise and disconnected copies of ELMS running in their environment. The success of the prototype will determine whether the functionality will become an operational element of the ELMS environment. Benefits: The proposed solution supports disconnected operations while enabling timely, secure, and controlled data exchange with the enterprise system. It provides a foundation for enhanced visibility, cross-service analytics, and future expansion while simplifying system-to-system communication and improving the scalability of ELMS architecture.. Frequency: Daily Users: This SCR should it go to production could impact all users of ELMS.
02129	Updating Corrosion Scoring Fields	MU	USAF	New	Change Request: Process Improvement Description: TO 35-1-3 CORROSION PREVENTION AND CONTROL, CLEANING, PAINTING, AND MARKING OF USAF SUPPORTEQUIPMENT (SE), Chapter 3 requires new paint and paint scoring to be documented. The current system issue e run into is that DPAS M&U only provides four predefined paint color options for corrosion scoring, which limits flexibility when tracking non-standard coatings. Additionally, the field units are getting confused on scoring documentation with only a Last Painted Date field available. This confusion and lack of documentation makes it difficult to track the most recent corrosion assessment separately from the last painting event. Proposed Improvement: Add an "Other" option to the corrosion scoring paint color selection, allowing users to account for additional coatings not covered by the existing four options. Change "Last Paint Date" field to read "Last Scoring Date" to reduce confusion for the field and accurately record the most recent corrosion assessment, improving tracking and maintenance scheduling. Recommended: Add an "Other" option to the corrosion scoring paint color selection, allowing users to account for additional coatings not covered by the existing four options. Change "Last Paint Date" field to read "Last Scoring Date" to reduce confusion for the field and accurately record the most recent corrosion assessment, improving tracking and maintenance scheduling. Mission Critical: The current DPAS M&U system only provides four predefined paint color options for corrosion scoring, which does not accommodate all possible coatings. We have received multiple requests to expand these options since the existing selections do not cover all use cases. Adding an "Other" option will allow users to input coatings that do not fit within the preset choices, improving accuracy in tracking corrosion treatments. Additionally, the field units are getting confused on scoring documentation with only a Last Painted Date field available. This confusion and lack of documentation makes it difficult to track the most recent corrosion assessment separately from the last painting event. Changing "Last Paint Date" field to read "Last Scoring Date" to reduce confusion for the field and accurately record the most recent corrosion assessment, improving tracking and maintenance scheduling. These changes will ine up DPAS M&U documentation with requirements in TO 35-1-3 CORROSION PREVENTION AND CONTROL, CLEANING, PAINTING, AND MARKING OF USAF SUPPORTEQUIPMENT (SE), Chapter 3, requiring new paint and paint scoring to be documented and repainting of SE for purely cosmetic reasons is prohibited Benefits: Improved Data Accuracy – Adding an "Other" option for paint colors ensures that all corrosion coatings can be properly documented, preventing inaccurate or incomplete entries. Enhanced Maintenance Tracking – The "Last Scoring Date" field will allow for better differentiation between corrosion assessments and painting events, leading to more precise tracking of maintenance history. Better Decision-Making – More accurate corrosion data helps maintenance personnel make informed decisions on when additional treatment or repainting is necessary, improving asset longevity. Increased Flexibility – Expanding paint color options prevents users from being forced into selecting an inaccurate color, making the system more adaptable to real-world scenarios. Compliance and Readiness – Proper documentation of corrosion assessments supports preventative maintenance efforts, ensuring assets remain in operational condition and reducing unexpected failures. Frequency: Daily Users: The inquiry process is used by 100s of users multiple times a day.
02128	Update DRRS Report File to include MU Data	MU	USAF	New	Change Request: Policy/Regulatory Description: Current DPAS data push to DRRS is limited to data from PA and FSM modules, providing on hand and authorized quantities(S ratings). FMC and NMC data is not being fed to DRRS, resulting in inaccurate data for R ratings. Manual data is being entered due to the information not feeding into DRRS. Recommended: Update report to incorporate M&U feed for FMC/PMC/NMC rates. Rates should be a roll-up of UIC and Stock Number. Asset data should reflect total number of FMC/PMC/NMC status based on Stock Number and UIC. Mission Critical: Per CJCSI 3401_02B, page C-11, section c. Equipment Condition (R-Level), it states units will report the lowest equipment condition level between designated combat-essential equipment and designated support equipment. (Requirement also IAW DAFI's 10-201 & 10-401) Benefits: Supports mandatory DRRS reporting and eliminates disparity from users manually entering FMC/NMC data. Strengthens Air Force Enterprise visibility of Readiness posturing. Frequency: Weekly Users: This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that utilize Support Equipment assets in DRRS.
02127	WRM Maintenance Attribute	MU	USAF	New	Change Request: Process Improvement Description: MU assets that are in War Readiness Materiel (WRM) status are not identified and segregated from the standard mission support assets. Air Force policy requires WRM assets to be maintained separately and sustained using WRM funds, not O&M funds used to maintain the regular equipment fleet. MU does not provide an indicator alerting users to the assets WRM status, nor the ability to search assets in that status. Recommended: Create a maintenance attribute for WRM, similar to the Mission Critical and Nuclear Certified attribute currently available in the Maint Asset Master. WRM attribute indicator should be visible on the work order alerting the user to the assets status. Additionally, the attribute should be available as search criteria in the Maint Asset and Work Order inquiries, as well as be included in the Advana (LIMS/BLADE) data feed. Mission Critical: Per DAFI 25-101, War Readiness Materiel, WRM support equipment will be managed in the AF Maint Information System (AvSE MIS), maintained separately from the base support equipment, repaired and maintained using WRM funds. Benefits: The change will allow the Air Force to effectively manage it's WRM fleet, ensuring correct maintenance actions and proper expenditure of funds. With the delineation of assets within the AvSE MIS, the ultimate impact will be strengthening war readiness posturing and eliminating the risk of misappropriation of funds. Frequency: Daily Users: This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that manage WRM assets.