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: 1779 Result(s) | Show: |
| Title |
ELMS Module |
Reporting Org |
State |
Description |
Action |
|
|---|---|---|---|---|---|---|
| 02166 | Update BLADE Feed with Additional Required Data | PA | AF | New | Change Request: Process Improvement
Description:
Recommended:
Modify the data feed to incorporate the newly identified data elements. The objective is to create a report within Advana/BLADE that mirrors the pending due-out/due-in report native to the ELMS application. This enhanced report in Advana/BLADE will enable users to view all assets due in and due out at the enterprise level. In addition this data will be utilized for other data analytics eg ESCAPE. Mission Critical:
Air Force Leadership has directed that all data analytics be performed within Advana/BLADE. This request is in line with the vision detailed in the attached decision memorandum.
Benefits:
Frequency:
Hourly
Users:
All Advana/BLADE users of ELMS Data |
|
| 02165 | ICAM Implementation within ELMS | PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW) | Leidos | New | Change Request: Policy / Regulatory
Description:
As the Department of Defense (DoD) moves toward enterprise-wide identity and access management, it is increasingly important for systems like ELMS (formerly DPAS) to align with these efforts to ensure consistency and audit readiness. Currently, multiple DoD systems independently manage personnel identity assignments, leading to a fragmented approach across the department. While ELMS has its own effective account tracking mechanisms, broader alignment with authoritative identity services supports a more unified and verifiable accountability structure. A consolidated identity framework would help standardize practices across all services and components.
Recommended:
Integrate ELMS with the Identity, Credential and Access Management (ICAM) to support a DoD-wide authoritative approach to access management. This integration would allow ELMS to reference trusted identity data directly from ICAM. Leveraging ICAM ensures that personnel data and role verification are consistent across systems. It also streamlines reporting and improves coordination with other systems adopting the same authoritative source. This solution aligns with DoD’s strategic goals for digital modernization and interoperability.
Mission Critical:
DoD policies such as DoDI 5000.76 and DoDI 8320.07 emphasize the use of authoritative data sources and the need for accurate, standardized accountability of government property. ICAM is the designated enterprise service for identity and access management and provides a common framework for personnel verification. Integrating with ICAM enhances ELMS’s ability to support these policies while aligning with the DoD’s broader data and cybersecurity strategies. https://dodcio.defense.gov/Portals/0/Documents/Cyber/DoD_Enterprise_ICAM_Reference_Design.pdf
Benefits:
1) This integration strengthens ELMS’s ability to support enterprise audit readiness by ensuring accounts and roles are validated against a DoD approved source. 2) It provides a systematic process for ELMS's Account Mgmt. services that is currently a combination of manual and automated tools. 3) It provides greater accountability to manage source records and reduces the redundancy in personnel management across systems.
Frequency:
Users:
All ELMS users and account managers |
|
| 02164 | Implement ADC 1466 Report Missing PMR Receiving Discrepancy | PA,MU,Warehouse,Materiel Management | Leidos | New | Change Request: Policy / Regulatory
Description:
DEDSO implemented a change to the DLMS 527R (TH) to enable the receiving entity to report within the receipt acknowledgement transaction an issue they experienced in performing the receipt / ADC 1466. 1. ELMS needs to display the descrepancy cd and description to the entity that receives the materiel receipt acknowledgment. 2. WIthin Receiving, ELMS needs to allow the user performing the receipt to enter a decrepancy reason cd which will be included in the 527R (TH).
Recommended:
1. Modify Receiving to enable the input of a discrepancy reason they want to report to the issuance party via the 527R. 2. Modify the inbounding of a DLMS 527R to extract and displays the discrepancy cd and description to the owner of the materiel that shipped the materiel to the gaining organization. 3. Generate and transmit an information DLMS 842 A/W to report the issue when no PMR was received.
Mission Critical:
Ensure DLMS compliance (ADC 1466)
Benefits:
Provide for reporting of receiving issues to the to the product manager.
1.Receipt Acknowledgment Discrepancy Code (Y) - No PMR. Receipt processed with documentation. Informational Supply Discrepancy Report (if this is the only discrepancy) required.
2.Receipt Acknowledgment Discrepancy Code (Z) - No PMR. Receipt processed without documentation. Informational Supply Discrepancy Report (if this is the only discrepancy) required.
Frequency:
Users:
While receipts are processed all day long, it is not known how many of those receipts may have a descepancy that should be reported. |
|
| 02163 | F35 Interim Solution for accounting of SPARES | Materiel Management | Leidos | New | Change Request: New System Process
Description:
Currently the JPO does not have financial accountability of its inventory. The proposed interim solution is for the contractors to provide 3 files (Catalog, Asset and Physical Inventory Results) in MS Excel format with ELMS providing a method to import the files.
Recommended:
To support creating a financial accountability record, ELMS needs to provide an import capability that a user can use to maintain inventory balances with in the Materiel Mgmt. application. The 3 imports are as follows:
A. Catalog Stock Nbr Import
B. Materiel / Asset Import
C. Date Of Last Inventory Process
Upon import, the system will validate and process the data. Errors will be output a spreadsheet for review, correction and re-import. Records that are successfully processed will produce accounting transactions with the results reflected in the ELMS accounting reports. Mission Critical:
This is an overlay upload entered into ELMS to account for F35 repair spares / parts and associated cost.
Benefits:
F35 inventory in the hands of a contractor are visible to DoD.
Frequency: Monthly
Users: |
|
| 02162 | Warehouse Category Addition | Warehouse | NSWC | New | Change Request: Process Improvement
Description:
Warehouses that contain only Operating Material and Supplies are required to create a negative inventory report for General and Sensitive Equipment.
Recommended:
Additional Warehouse Category to annotate that it is an OMS warehouse to show auditors that the warehouse does not have general equipment and sensitive items. Suggested Name = "OMS - Consumable Warehouse"
Mission Critical:
Benefits:
Exempt the associated warehouse that has this Warehouse Category from generating negative inventories.
Frequency: Monthly
Users:
All Users |
|
| 02161 | Depot Request for Induction Asset (511R_A0) Project Code 3AB | Warehouse,Materiel Management | USMC | New | Change Request: Process Improvement
Description:
While conducting testing, MARCORLOGCOM encountered a problem where ELMS did not allow our Depot Remote Storage Activity (RSA) to call for inventory scheduled for induction, from the Inventory Control Point (ICP) using a (DLMS 511R/A0_) as prescribe in Approved DLMS Change (ADC) 1176. Within the (DLMS 511R/A0_) a project code of “3AB” must be entered identifying the transaction as being part of a depot required induction.
Recommended:
1.0 This process starts with one of the Depots, Remote Storage Activities (RSAs), using the Warehouse Module (WM), under the ICP Owning RIC of “MPT”, ELMS shall provide the mechanism for the RSA Depot warehouse to request for an asset for induction into depot repair. This will be accomplished using a (DLMS 511R/A0_), with a signal code of “M”, and a Project Code of “3AB”. The Owning RIC will be specified as “MPT”. This is in accordance with Approved DLMS Change (ADC) 1176. 1.1 ELMS shall route the (511R/A0_) to the Material Management (MM)/ICP module of the specified “Owning RIC”, Inventory Control Point (ICP), Inventory Manager for release or cancellation consideration.
2.0 ELMS shall provide the Inventory Manager (IM), within the Material Management (MM)/ICP module, the ability to view all available asset for the specified National Stock Number (NSN) and Condition Code. The asset viewed will be limited to the available RSA warehouses holding asset under the specified Owning RIC.
2.1 ELMS shall allow the Inventory Manager to reply with an (870S/AE_ Cancelation) or proceed to the Material Redistribution module, within the Material Management (MM)/ ICP module.
2.2 If the Inventory Manager locates a NSN with the requested Condition Code, ELMS shall allow the Inventory Manager to create an MRO using the Material Redistribution function.
2.3 ELMS shall generate an (940R/A2_) Material Release Order (MRO) to be sent to the losing warehouse DoDAAC. Note: It is important to perpetuate the Project Code “3AB”
2.4 ELMS shall send the (527D/DW_) Pre-position Material Receipt (PMR)) transactions to the Depot, Remote Storage Activities (RSAs) that originally sent the induction (511R/A0) with Project Code “3AB”.
3.0 Using ELMS, the losing Warehouse DoDAAC will process the inbound induction MRO using the Warehouse Module (WM). The warehouse person will (pick, pack, and release) the asset requested for induction.
3.2 ELMS shall generate the (945A/AR0) and send it back to the ICP, in the Material Management (MM)/ICP module, reporting the asset is now intransit.
4.0 ELMS shall provide the Depot, Remote Storage Activities (RSAs) with a capability to receipt for the induction asset document.
4.1 ELMS shall upon receipt, and quality control verification produce a receipt (527R/D6_).
4.2 ELMS shall gain the asset to the Depot, Remote Storage Activities (RSAs) warehouse DoDAAC.
4.3 ELMS shall post the (527R/D6_) to the historical transactions activity log allowing for associated Key Supporting Documents (KSD) to be added later.
4.4 ELMS shall add the completed receipt’s (527R/D6_) quantity to the “on hand available “in Inventory Manager’s Material Management (MM)/ICP view and completing out the document.
Mission Critical:
Approved DLMS Change (ADC) 1176
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
Frequency: Daily
Users:
All USMC WH Managers |
|
| 02160 | KSA Obtainment Enterprise Level Material Management Module | PA,Warehouse,Materiel Management | USMC | New | Change Request: Process Improvement
Description:
ELMS currently does not provide the Material Manager / Inventory Manager with the ability to view and download Key Supporting Documents (KSD) associated to a specified NSN and or serial number present, Document Number, or ICN within any of the USMC identified Logistic Programs (LPs) within the Warehouse Module and the Property Accountability (PA) module. This capability is currently missing from within Material Manager (ICP) module. Where applicable, automate KSD retrieval requests to support analytical and audit tasking. Transactional audit trail retrieval and sequencing (e.g. Material Transaction history), by applied date is required, to include the ability to select a given transaction from the displayed listing and drill down to obtain any attached KSDs. This capability is required to support audit inquiries, and the day-to-day operational capabilities required for MARCORLOGCOM’s inventory manager to perform their tasking. Transactional audit trail retrieval must include all transactions applied to any given Inventory Control Number (ICN) historically, to include all KSDs like (receipts, material movements, physical Inventories, Limited Technical Inspections, MROs, Maintenance, etc.).
Recommended:
1.0 ELMS shall provide the Inventory Manager, within the Material Management module, the capability to search historical and active records by a specific National Stock Number (NSN) and or Serial Number combination, Document Number or Inventory Control Number (ICN). 1.1 Within ELMS, the system shall provide the Inventory Manager with a choice to perform the search through:
a. All Logistic Programs (LPs) LPs within any of the USMC identified within the Warehouse Module and the Property Accountability (PA) modules or
b. Only with historical and active records pertaining to the warehouse DoDAACs associated with the ICP.
This capability is currently missing from within Material Manager (ICP) module.
1.2 ELMS shall display all requested results from the specified search through and online view.
1.3 ELMS shall, within the set of data being displayed from requirement 1.2 provide a mechanism to display and or download Key Supporting Documents (KSD).
like (receipts, material movements, physical Inventories, Limited Technical Inspections, MROs, Maintenance, etc.).
Mission Critical:
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
Frequency: Daily
Users:
All USMC WH Managers |
|
| 02159 | Denial Transaction (DLMS 945AA6_) Narrative | Warehouse,Materiel Management | USMC | New | Change Request: Process Improvement
Description:
During the creation of a denial transaction (DLMS 945A/A6_), by the Warehouse Module (WM), no reason code or explanation is given to why the denial was produced. This does not provide the Inventory Manager, working in the Material Management (MM) module enough information as to conduct follow-on action such as back-ordering, filling the requisition from an alternate RSA withing the ICP arena, or canceling the requisition. It also does not appear that there is a means to search for a denial transactions associated to a specific document number.
Recommended:
1.0 ELMS, shall provide an ability for a warehouse person, working the Warehouse Module (WM), to enter a narrative to why a document received a denial during the 940R fulfillment and issue process.
1.1 ELMS shall associate the denial narrative directly to the document which it pertains to.
1.2 ELMS shall make the document number and the denial narrative available to be search for in the Warehouse Module (WM) and the Material Management (MM) module.
2.0 Once the (DLMS 945A/A6_) has been produced by the Warehouse Module (WM) and sent to the Material Management (MM) module with the denial narrative, ELMS shall provide the Inventory Manage with three option to handle the inbound denial.
a. Back Order the customer requisition advancing the suffix code to the next available sequence. In addition, ELMS shall transmit an (870S/AE_) back to the originator of the purchase order. See attached document, "ME Sourcing Handbook 4.10.24.docx", page 30-33 for the approved USMC status codes authorized for use.
c. ELMS shall provide the Inventory Manager with the ability to attempt to release from another ICP location. This will be done through the customer requisition mode in the Material Management (MM) module.
2.1 ELMS shall provide the Inventory Manager with the ability to select the appropriate backorder or cancellation status using the information provided in the attached document labeled, "ME Sourcing Handbook 4.10.24.docx", page 30-33 for the approved USMC status codes authorized for use.
Mission Critical:
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% accountability of assets
Complies with current audit controls
Frequency: Daily
Users:
Affects USMC Materiel Managers, WH Managers and ICP |
|
| 02158 | MCPIC Speed to Count Inventory | Warehouse | USMC | New | Change Request: Process Improvement
Description:
MARCORLOGCOM has a requirement to continue what is known as the MCPIC speed-to-count inventory process. This is a key, “MUST HAVE” capability that was previously missed in the WG3 end-to-end evaluation. The process being addressed has been documented in the attached business process map. This process differs from the Consolidate Support Program (CSP) containerization MCPIC support interface. This process used key robotic functionality to optimize the successful execution of an inventory in a significantly reduced time frame. This process has been a key success point in ensuring we stay audit compliant.
Recommended:
1.0 During the execution of an inventory, ELMS using the Warehouse Management (WM) module shall provide a mechanism for the warehouse person to select between a MCPIC managed inventory and a manually schedule execution of a location driven cycle count.
Note: A MCPIC managed inventory is one that use automation capability to receive and transfer data automatically. The physical inventory is conducted using robotics.
1.1 After a “MCPIC managed inventory” is selected, ELMS shall conduct a verification to ensure a location cycle count for that same NSN and site has not already been scheduled.
2.0 ELMS shall allow the warehouse person to generate an inventory cycle count.
2.0.1 ELMS shall auto generate a unique cycle count.
2.1 ELMS shall provide a mechanism to the warehouse person to select the type of MCPIC inventory, (Container, NSN, or Location).
Note: Marine Corps Force Storage Command primary conducts inventory by (site, NSN, and location).
2.2 ELMS shall provide a mechanism to the warehouse person to identify if the inventory is part of a plan cyclic inventory or unscheduled inventory (also known as a spot inventory).
2.3 ELMS shall freeze all transactional movement of the NSNs that has been identified by the location selected.
2.4 ELMS using the agreed upon XML data exchange format, shall generate the required file for transmission to MCPIC.
2.5 ELMS shall transmit, via an API, the XML file staged for transmission.
2.5.1 ELMS shall establish a means to verify the transmission was received in its entirety by MCPIC.
Note: Steps 2.6 – 2.8 is executed by MCPIC
2.9 ELMS shall code the system to accept a reply from MCPIC, via an API where the agreed upon XML formatted is met, that represents the completed results of a cycle inventory count.
2.10 ELMS Shall verify all incoming results from a MCPIC inventory for a specified cycle count. If the balance from the inventory count matches what ELMS has a record for (serial number), then update ELMS with the date inventoried. As part of verification, ELMS will not accept a MCPIC inventory for a date outside the parameter specified in the request to inventory.
3.0 ELMS shall provide a mechanism for the warehouse manager to display the results of the, “MCPIC managed inventory”.
3.0.1 If the results of the inventory indicate an item has been move to a different location, ELMS will conduct a location move to match the MCPIC reported location.
Note: It is, however, the overall responsibility of the Accountable Officer to conduct causative research when there is an imbalance between what is being reported in ELMS and what was reported by MCPIC.
3.1 ELMS shall provide the Accountable Officer with means to accept the inventory results producing the required DLMS 947I (Inventory adjustment transactions D9A/D8A) when applicable.
Note: The Accountable Officer must complete the required Financial Liability Investigation of Property Loss (FLIPL) process as prescribe by MARCORLOGCOM policy prior to submitting any adjustment. This is an administrative item outside of ELMS.3.2 ELMS shall produce a Money Value Gain and Loss (MVGL) notification statement. Based on the threshold, the Accountable Property Officer (APO) may be allowed to sign vice the Accountable Officer.
3.2.1 ELMS shall provide the Inventory Certifying Officer with the capability to acknowledge that all MVGLs and FLIPLs have been completed prior to certifying the inventory.
3.3 After the Inventory Certifying Officer has, within ELMS completed the certification, ELMS shall process all directed adjustments within the system.
3.4 – 4.0 ELMS, coordinating with MCPIC shall develop an automatic way of reconciling location records to ensure synchronization is occurring and maintained.Mission Critical:
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
Frequency: Daily
Users:
All USMC WH Managers |
|
| 02157 | Physical Inventory at the Enterprise Level | Warehouse | NECC | New | Change Request: Process Improvement
Description:
We are requesting the addition of functionality within the Inventory process to enable users to conduct inventories by Reportable Commodities at the Enterprise level. This enhancement would allow users to schedule inventories for an entire commodity type across a specified Region or Site, thereby improving inventory management efficiency and ensuring timely accountability for assets across broader organizational scopes.
Recommended:
Mission Critical:
NECCINST 5200.45
Benefits:
Frequency: Daily
Users:
All users who utilize multiple warehouses and the Physical Inventory function. |
Disclaimer | Accessibility