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
02216	Additional Job Statuses needed	MU,Warehouse	USMC	New	Change Request: Process Improvement Description: The current ELMS system uses an overly simplified and outdated set of job statuses that does not reflect the full range of actions and stages in Marine Corps maintenance workflowsBRD JOB STATUES. This limited framework creates several operational and reporting issues:Units lose visibility of their equipment once it is evacuated to higher echelon maintenance, preventing accurate readiness reporting.Lack of granular statuses disrupts communication between organizational levels and reduces transparency of maintenance progress.There is no real-time visibility for using units, which hinders operational planning.Readiness reporting is compromised, particularly when equipment is in intermediate maintenance activities but only shows as a generic “in maintenance” status. Identified Material Weakness: The absence of sufficient job status categories and transitions creates a material weakness in reporting and accountability, leading to inaccurate readiness visibility, poor auditability, and delays in decision-making. Recommended: Job Status Framework Enhancements 1.1 Expanded Job Status List FR1.1.1: The system shall support a configurable and extensible list of maintenance job statuses that accurately represent each phase of the maintenance lifecycle. FR1.1.2: The new status list shall include, but not be limited to: (list here) FR1.1.3: Each job status shall be associated with a standardized definition and criteria for transitioning to/from other statuses. FR1.2.1: The system shall support controlled status transitions based on workflow logic or user roles. FR1.2.2: Users shall be prompted with a reason code or comments field when skipping or overriding standard status flows. FR2.1.1: The maintenance job form shall display an updated drop-down menu or status selection tool that reflects the full status list. FR2.1.2: Status changes shall be logged with user ID, timestamp, and optional notes. FR2.2.1: Each job status shall be color-coded in dashboards and reports to enhance visual identification (e.g., red for “Awaiting Parts,” green for “Repair Complete”). FR3.1.1: Users shall be able to filter maintenance job reports based on any job status or combination of statuses. FR3.1.2: Reports shall include job status progression history for auditing and analysis.3.2 Performance Metrics FR3.2.1: The system shall generate performance metrics based on time spent in each job status. FR3.2.2: Metrics shall include Mean Time to Repair (MTTR), parts wait time, and overall repair cycle time. FR4.1.1: System administrators shall be able to add, remove, rename, or reorder job statuses via a configuration panel. FR4.1.2: Changes to the status list shall be logged and version-controlled.4.2 Role-Based AccessFR4. Mission Critical: ELMS does not provide currently. Benefits: -Meets MARCORLOGCOM’s business model -Assists in 100% accountability of assets. -Complies with current audit controls. Frequency: Daily Users: -Material Managers -WH Managers -All USMC Users
02215	Intermediate Calibrations LAB Requirements	MU	USMC	New	Change Request: Compliance Requirement Description: Marine Corps Calibration Laboratories (TMDE shops) lack an integrated system to record and report calibration transactions directly to the owning unit’s equipment records. Current processes require manual or duplicated data entry across disconnected systems, resulting in inconsistent updates, delayed visibility of calibrated assets, and inaccurate readiness reporting. The Marine Corps requires ELMS to provide an integrated calibration management capability that enables calibration labs to execute, record, and transmit calibration results seamlessly to the system of record. This capability must ensure real-time synchronization of calibration data with unit-level equipment records, maintain complete maintenance history, and enhance readiness visibility and accountability across the enterprise. Recommended: FR1. ELMS shall allow calibration laboratories to receive equipment through an automated acceptance transaction tied to the owning unit’s equipment records. FR2. ELMS shall enable creation of calibration work orders containing mandatory data fields such as Serial Number, Calibration Interval, Due Date, and Calibration Standard Used. FR3. ELMS shall record calibration results including Pass/Fail status, Adjusted, Unserviceable, and Next Due Date. FR4. ELMS shall generate and attach digital calibration certificates to equipment records upon completion of calibration. FR5. ELMS shall automatically update the owning unit’s equipment record to reflect calibration completion, results, and next due date. FR6. ELMS shall display calibration status within readiness and asset reports using standard codes (e.g., Full Cal, Special Cal, Cal Not Required, Inactive). FR7. ELMS shall enable transaction capability to return calibrated equipment to the owning unit, maintaining an auditable trail of the calibration performed. FR8. ELMS shall allow calibration technicians to record detailed calibration data, including parts used, labor hours, and technician EDIPI. FR9. ELMS shall enable batch data entry for bulk calibration of grouped assets such as gauges, tool sets, or test equipment families. FR10. ELMS shall support barcode and RFID scanning for check-in and check-out of items processed through calibration labs. FR11. ELMS shall notify owning units when calibration is complete and the item is ready for pickup or return shipment. FR12. ELMS shall provide automated alerts to units when calibration due dates are approaching or overdue, based on defined time thresholds. FR13. ELMS shall maintain a permanent calibration history record for each serialized item, accessible for inspection or audit. Data Elements Required: NIIN / NSN TAMCN / Equipment Description Serial Number Owning Unit DODAAC Calibration Lab DODAAC Work Order Number Calibration Technician (EDIPI/Name) Calibration Interval (Days/Months) Calibration Standard Used (ID/Serial) Calibration Result (Pass/Fail/Adjusted/Unserviceable) Calibration Certificate (Attachment ID) Next Calibration Due Date Transaction Date/TimeFunding Line (if cost captured) Mission Critical: Current GCSS functionality Benefits: -Assists in 100% accountability of assets. -Complies with current audit controls. Frequency: Daily Users: All USMC Users
02214	Automatic Equipment Transfers	PA,Warehouse	USMC	New	Change Request: Process Improvement Description: IThe current Enterprise Logistics Management System (ELMS) lacks a standardized capability to execute and track Mass Equipment Transfers across units, DODAACs, or custodial records. In the legacy GCSS-MC system, the Equipment Asset Transfer Order (EATO) process enables the Marine Corps to transfer property accountability between organizations while maintaining equipment history and audit traceability. However, ELMS currently does not replicate or enhance this essential function.Without a Mass Equipment Transfer capability, units encounter significant challenges in maintaining accurate property accountability, reconciling equipment custody, and preserving visibility of assets as they move between commands, operational areas, or deployment task forces. During large-scale or individual transfers, critical equipment data—such as modifications, PMCS records, calibration history, open work orders, parent/child relationships, and open requisitions—does not follow the equipment to its new owner, resulting in fragmented data continuity and audit risk.The Marine Corps requires an integrated, auditable Mass Equipment Transfer process within ELMS that allows authorized users to initiate, approve, track, and complete transfers across organizational boundaries. This process must preserve full equipment history, ensure compliance with financial and accountability regulations, and provide commanders with real-time asset visibility to support readiness reporting, deployment operations, and enterprise-level decision-making. Recommended: FR1. ELMS shall allow authorized users to create an Enterprise Accountable Transfer Order (EATO) request that captures all required data fields: Gaining DODAAC, Losing DODAAC, NSN, NIIN, Serial Number, TAMCN, Quantity, and Condition Code. FR2. ELMS shall automatically generate a unique mass equipment transfer document number for each transfer request to ensure traceability and auditability. FR3. ELMS shall route the mass equipment transfer request to the appropriate approving authority (e.g., Supply Officer, Commanding Officer, or delegated approver) based on established routing logic and user roles. FR4. ELMS shall allow digital signatures by authorized personnel using authenticated CAC/EDIPI credentials and maintain a full audit trail of all signatures and approvals. FR5. ELMS shall validate that equipment being transferred is serviceable, not tied to an open Work Order, and not restricted by funding or custody conditions, and shall display user alerts for validation failures. FR6. ELMS shall automatically update property records to reflect the transfer of accountability from the losing unit/DODAAC to the gaining unit/DODAAC upon approval. FR7. ELMS shall ensure all equipment history data (maintenance, readiness, warranty, calibration, etc.) remains intact and linked to the item record upon transfer to the gaining unit. FR8. ELMS shall notify both the losing and gaining organizations via system notifications and/or email at each stage of the transfer (submission, approval, completion). FR9. ELMS shall provide a dashboard or report interface displaying all open, pending, and completed EATO actions with sortable and filterable fields (e.g., status, date, DODAAC). FR10. ELMS shall maintain a permanent audit record of all mass equipment transactions, including initiator, approver, timestamps, and data changes. FR11. ELMS shall support user queries by asset, Equipment document number, DODAAC, NSN, NIIN, or date range, and allow export of query results to standard report formats (CSV, PDF, Excel). FR12. ELMS shall support mass transfer functionality to process multiple equipment items under a single EATO document for deployment, redeployment, or large-scale realignment operations. FR13. ELMS shall allow users to upload or import bulk equipment lists (e.g., CSV or Excel format) containing NSN, NIIN, Serial Number, and Quantity for batch EATO creation FR14. ELMS shall validate each item in a bulk EATO against property records to ensure data accuracy, completeness, and non-duplication prior to submission. FR15. ELMS shall allow authorized users to group items by TAMCN, Subset, or Functional Area to streamline transfer requests during deployments. FR16. ELMS shall generate an Mass equipment transfer Summary Report consolidating all items transferred under a mass movement event, showing losing and gaining DODAACs, quantities, serials, and approval timestamps. FR17. ELMS shall interface with other Marine Corps logistics systems (e.g., GCSS-MC, TFSMS, ELMS) to synchronize accountability updates following mass transfer execution. FR18. ELMS shall provide an automated deployment transfer template that pre-fills gaining unit and ship DODAACs, based on operation plans or TFSMS tasking, to accelerate processing. FR19. ELMS shall allow authorized users to reverse or cancel pending Mass Equipment Transfers prior to final approval and document all reversal actions in the audit trail. FR20. ELMS shall generate automated alerts for assets remaining in “pending transfer” status beyond a command-defined threshold (e.g., 30 days) to prevent orphaned transactions. Mission Critical: Response to Audit Finding - Accountability of capital assets, P2P, E&C Compliance Requirement - MCO 4400.201, MCO 4790.2, NAVMC 3500 Benefits: -Meets MARCORLOGCOM’s business model -Assists in 100% accountability of assets. - Complies with current audit controls. Frequency: Daily Users: -Material Managers -All USMC Users
02213	ELMS .NET 10 Update	PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW)	Leidos	New	Change Request: Policy / Regulatory Description: Microsoft has announced the end of life "EOL" for .NET 8 as 11-10-2026. ELMS has applications that are using .NET 8. These will need to be updated to .NET 10 (Latest LTS Version). .NET 10 has a scheduled EOL of 11/14/2028. https://dotnet.microsoft.com/en-us/platform/support/policy/dotnet-core Recommended: Update applications to .NET 10. Mission Critical: DoD is not authorized to operate software that is EOL. Failure to complete the upgrade will result in ELMS not receiving security patch updates/support. Benefits: Maintain ELMS compliance. Frequency: Daily Users: All Users
02212	Upgrade FLIS to IDV9	PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW)	DLA	New	Change Request: Process Improvement Description: ELMS maintains its FLIS Catalog data via the consumption of XML files that are received via DAAS GEX. These files currently adhere to J62FPDW's IDV8 format for data segmentation. FPDW is being modernized to coincide with changes occurring as part of FLIS' ongoing cataloging transformation and are reflected in their new IDV9 format. Recommended: The processes within ELMS responsible for the consumption and subsequent processing of the FLIS data files will need to be updated to coincide with the provided changes, including database updates. Data elements 4130 & 4131 are being combined into a single field to represent NIIN, 2994 & 3996 are being combined to represent FSC, 25 fields are being removed, and 3 are being added along with other renames of existing elements. Mission Critical: See FPDW IDV9 Documentation sent 04Nov2025. This SCR is updating the current FLIS interface to the IDV9 format. Benefits: This is a mandatory change required to maintain the FLIS data feed to ELMS to ensure consistency between our systems and the integrity of catalog data within ELMS. Frequency: Daily Users: This change affects all users who's agency is configured to access the FLIS catalog
02211	DLMS Transaction Gaps	Warehouse,Materiel Management	USMC	New	Change Request: Compliance Requirement Description: Acquire to Retire (Equipment): Planning for Equipment: Planning for Equipment (Material Weakness) ELMS MM module currently supports only pull-based requisitioning, which prevents Inventory Control Points (ICPs) from proactively distributing materiel based on command direction, readiness requirements, or forecasted operational demand. This absence of a Push Fulfillment (ICP Directed MRO Issue) capability limits the USMC’s ability to preposition assets, re-balance inventory, and execute time-critical resupply actions – especially for MARCORSYSCOM and MARFORRES organizations. Additionally, ELMS lacks the ability to automatically generate DLMS 527D/DWB Prepositioned Materiel Receipt (PMR) transactions when transferring ownership of assets between Primary Inventory Control Activities (PICAs) or ICPs through a third-party storage or distribution site. The current process requires manual, offline creation of these transactions, resulting in fragmented data flow, inconsistent audit trails, and potential discrepancies in custodial accountability and ownership records. The combined absence of automated push fulfillment and system-driven 527D/DWB ownership transfer functionality forces reliance on manual workarounds that degrade visibility, increase processing time, and heighten the risk of data mismatches across warehouse, ICP, and financial systems. These deficiencies also impede full DLMS compliance, complicate reconciliation between issuing and gaining activities, and introduce audit vulnerabilities within FIAR and ELMS-aligned accountability frameworks. Implementing an integrated ICP Directed MRO Issue process within ELMS—complete with automated generation of 940R, 945A, 856S, 870S, and 527D/DWB transactions—will ensure accurate, DLMS-compliant execution of directed shipments, ownership transfers, and audit-ready traceability. The absence of a system-driven, DLMS-compliant “ICP Directed MRO Issue” process introduces a significant materiel weakness. Manual workarounds—such as ad hoc issue documentation, offline tracking, or non-standard DLMS transactions—degrade audit compliance and complicate reconciliation between ICP, warehouse, and accounting systems. Additionally, the inability to incorporate serialized tracking, third-party consignee shipments, or automated PMR (527D/DWB) generation further constrains the Marine Corps’ ability to support distributed maritime and expeditionary operations. Recommended: README: The following nine attachments are embedded within the GAP-109 Push Fulfillment (ICP Directed MRO Issue) BRD package to provide the complete set of supporting technical, functional, and design requirements required for implementation. Collectively, these attachments document the end-to-end process flow, user interface design, DLMS XML transaction mappings, and detailed requirements specifications for all five modified DLMS messages (940R, 527D, 945A, 856S, and 870S). Their inclusion ensures that ELMS developers, testers, and stakeholders possess authoritative references linking the business process to the technical configuration, thereby enabling DLMS-compliant system development, audit-ready validation, and seamless integration of the new Push Fulfillment capability within the Materiel Management (MM) module. 1 – GAP109_ELMS_Push_Fulfillment_Requirements_RTM_20251008.xlsx This Excel workbook serves as the master Requirements Traceability Matrix (RTM) for the Push Fulfillment capability. It consolidates all functional and non-functional “shall” statements generated for GAP-109, cross-referencing each requirement to DLMS standards, transaction sets, and validation criteria. The file ensures end-to-end traceability from BRD objectives to development and test cases within ELMS MM. 1a – GAP 109_BRD_ELMS_USMC_MARCORLOGCOM_1.b ICP DIRECT MRO ISSUE Process Flow_v2.0 (20251006) This process flow illustrates the end-to-end ICP Directed MRO Issue workflow within the ELMS Materiel Management (MM) module, depicting user roles, decision logic, validations, and DLMS transaction triggers (940R, 527D, 945A). It provides system developers and testers a visual baseline for how “Push Fulfillment” actions move from MRO creation through warehouse release and transaction generation. Included to serve as the primary business-process reference for implementing, testing, and verifying GAP-109 functionality 1b – GAP 109_BRD_ELMS_USMC_MARCORLOGCOM_1.b ICP DIRECTED MRO ISSUE Screen Layout (20251006) This attachment presents the user-interface design and required input fields for the new “ICP Directed MRO Issue” entry screen, including header, body, and inventory-selection components with DoDAAC, RIC, PMR, TAC, and serial-number data entry rules. It provides developers with a precise UI blueprint and control-validation guide ensuring compliance with DoDAAF standards and proper capture of all requisition data elements during push fulfillment. 2 – GAP 109_BRD_ELMS_USMC_MARCORLOGCOM_1.b ICP DIRECTED MRO ISSUE _XML Transactions Mapping_v2 (20251009).xlsx This multi-tab mapping workbook defines the DLMS XML schema field mapping for the five modified transactions (940R, 527D, 945A, 856S, 870S). Highlighted tan cells indicate missing segments to be added; red cells flag non-compliant elements requiring removal or correction. It is included to guide developers in achieving full DLMS Interface Convention alignment for each ELMS interface. 3 – GAP109_Push_Fulfillment_DLMS_XML_940R_Requirements_20251009v3.pdf Specifies requirements for the DLMS 940R (Warehouse Shipping Order) message that initiates push-fulfillment actions from the ICP to RSAs or third-party consignees. It details data fields, validation logic, and message structure needed to automate directed materiel releases and ensure schema compliance with DLMS IC 940R. 4 – GAP109_Push_Fulfillment_DLMS_XML_527D_Requirements_20251009v1.pdf Documents requirements for the DLMS 527D/DWB (Prepositioned Materiel Receipt) are used to record ownership transfer between PICAs/ICPs via third-party storage sites. It defines triggers, mandatory data elements, and audit-logging requirements replacing the current manual PMR process, ensuring automated, FIAR-compliant custody updates. 5 – GAP109_Push_Fulfillment_DLMS_XML_945A_Requirements_20251009v1.pdf Outlines requirements for the DLMS 945A (Warehouse Shipping Advice) transaction confirming fulfillment of directed MROs. It captures shipment quantities, serial details, and consignee data, linking back to originating 940R orders. Included to formalize message generation and closure logic supporting audit-ready shipment verification. 6 – GAP109_Push_Fulfillment_DLMS_XML_856S_Requirements_20251009v1.pdf Defines requirements for the DLMS 856S (Advance Ship Notice / Manifest) message used to communicate detailed shipment information—carrier, packaging, and serialized item content—to receiving and third-party sites. This file ensures ELMS can provide standardized, real-time shipment visibility aligned with DLMS IC 856S. 7 – GAP109_Push_Fulfillment_DLMS_XML_870S_Requirements_20251009v1.pdf Describes the DLMS 870S (Supply Status) message requirements used to transmit real-time status updates throughout the push-fulfillment lifecycle. It specifies event codes, routing, and validation rules that synchronize ICP, RSA, and consignee systems, closing the DLMS transaction chain with complete audit traceability. Mission Critical: ELMS is not currently fully compliant with DLMS transactional policy Benefits: - Meets MARCORLOGCOM’s business model - Assists in 100% accountability of assets. - Complies with current audit controls. Frequency: Daily Users: - Material Managers - ICP
02210	LESO - Identify Nbr of asset photos	Warehouse	LESO	New	Change Request: Process Improvement Description: ELMS provides for attachments by the user community, but it does not identify the number of photos that should be captured and attached to the item. DLA LESO's policy requires law enforcement agencies that acquire excess DoD property to capture and attached x photos to the item's record based upon the type of item it is. ELMS needs a method to identify the number of photos and provide that information to the user during Receiving and Updates of the item. The DLA LESO's agencies will utilize the warehouse management application for their property control record. Recommended: DLA LESO is requesting: 1) ELMS provide the capability to identify the number of photos required to be captured for the item in inventory. Possibly at the Stock Nbr or Commodity Type level. 2) Advise the user of the number of photos required during the receiving process. 3) Provide a method for validating the the photos are of the asset. Mission Critical: Improvement for managing assets. Benefits: This change enables law enforcement agencies to comply with DLA LESO regulations and provide the DLA LESO a method for validating that the agencies are complying with the regulation. Frequency: Daily Users: The primary users of this capability would be DLA LESO, USMC, and NSWC at this time.
02209	Law Enforcement Office Self Certification Phase 2	Warehouse	LESO	New	Change Request: New System Process Description: DLA LESO submitted a SCR titled "LESO - Law Enforcement Office Self Certification" that described the the requirements that each Law Enforcement Office must perform as part of their annual certification. That SCR did not request ELMS provide the capability to create / store the from used to perform the annual certification. Recommended: This SCR is requesting ELMS to provide the following: – Create a process that provides each law enforcement office "Station" the capability to download the application form, upload completed form and to provide workflow routing of the certification to the required LESO offices for review and signature. Once the last signoff is received as approved, ELMS will update the status of the Station to approved for the next period of performance E.G. (1 Year). A view should be available to DLA LESO (Logistics Program) of the status of each law enforcement office identified by State (Region), County/City (SIte). Mission Critical: This is a new requirement that provides for the review and tracking of stations (Warehouse) as to their certification to operate, for how long and when their next certification is due. Benefits: This change enables law enforcement agencies to comply with DLA LESO regulations and provide the DLA LESO a method for validating that the agencies are complying with the regulation. Frequency: Yearly Users: The primary users of this capability would be DLA LESO.
02208	DLA LESO Program Compliance Review (PCR) Process	Warehouse,Materiel Management	LESO	New	Change Request: New System Process Description: DLA LESO has a Program Compliance Review "PCR" where they biannually review / validate each station's (ELMS Warehouse) for compliance to stated regulations. This process validates the station is in compliance and can continue with the program should they indicate that they wish to. ELMS does not have a defined process to support this. Recommended: This SCR is requesting ELMS to provide DLA LESO with a PCR process. The process will provide DLA LESO with a list of stations, when they were last reviewed, their current status and when their next PCR is due to be completed. Be able to attach planned and actual reuslts as well as provide the status of the review (Complete, Reviewed/Pending finalization/Planning, etc)., The process must also show the proximity of each station in order to group stations into an audit group. See attached for specifics. Mission Critical: This change will provide a Program Compliance Review "PCR" process for DLA LESO personnel. The goal should be to design the process to support all ELMS users that conduct compliance reviews. Benefits: This change will provide DLA LESO and other ELMS the capability to manage compliance reviews using ELMS. This change will enable ELMS users to track warehouse reviews planned, determine the scope of the PRC and track when it was conducted and the results of the review. Frequency: Weekly Users: The primary users of this capability will initially be DLA LESO PCR personnel.
02207	DLA LESO Program Compliance Review (PCR) Process - Phase 2	Warehouse,Materiel Management	LESO	New	Change Request: New System Process Description: DLA LESO has submitted a Program Compliance Review "PCR" SCR to provide processes to support the compliance review process. This SCR requests ELMS to automate the generation of the PCR document where the PCR criteria is configurable and customizable. Recommended: Automate the generation of the PCR to the state for each PCR to be conducted. Mission Critical: This change will automate the Program Compliance Review "PCR" process form. The goal should be to design the process to support all ELMS users that conduct compliance reviews. Benefits: This change will provide DLA LESO and other ELMS the capability to manage compliance reviews using ELMS. This change will enable reduce the effort required to notify and route planned PCR reviews. Frequency: Weekly Users: The primary users of this capability will initially be DLA LESO PCR personnel.