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 |
|
|---|---|---|---|---|---|---|
| 02226 | BLADE Requests ELMS Data | PA | AF | New | Change Request: Process Improvement
Description:
The Advana/BLADE data feed currently lacks all ELMS data. BLADE has a sub-set of the data available in the ELMS system.
Recommended:
Modify the data feed to incorporate the newly identified data elements not highlighted in attached spreadsheet.
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.
Sending the remaining ELMS data to BLADE will eliminate re-work to add individual data elements requested by users. Benefits:
This data field would be beneficial to all user groups using ELMS data.
Frequency: Hourly
Users: All Advana/BLADE users of ELMS Data
|
|
| 02225 | General Database Infrastructural Changes - CY 2026 | Leidos | New | Change Request: Process Improvement
Description:
In many application releases, the Leidos team needs to implement various database infrastructural changes and improvements. These changes include, but are not limited to, index adjustments, configuration changes, and the implementation of database utility objects. These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, correctness, and performance of the DPAS system. I am requesting an SCR for calendar year 2026 to encompass this category of database changes.Recommended:
Implementation of any database infrastructural changes and improvements deemed necessary by the Leidos Team.
Benefits:
These changes and capabilities can not be invoked directly through the application but are nonetheless necessary for the availability, integrity, and performance of the DPAS system.
Frequency: Daily
Users: N/A - Infrastructural enhancements that wouldn't directly affect the users.
|
||
| 02224 | Expansion of ELMS and Jupiter data sharing agreement | Warehouse | Navy | New | Change Request: Process Improvement
Description:
OPNAV N834 and its expeditionary enterprise, comprising of TYCOM (NECC, CNSF, BUMED, WARCOM) and supporting SYSCOMs (NAVAIR, NAVFAC, NAVWAR, MARCOR, and NAVSEA) stakeholders, cannot easily access data that supports collaboration, planning and risk-based assessments, and the PPBE (Planning, Programing, Budgeting, and Execution) process. The disparate enterprise data sources have led to time intensive manual data collection efforts, inconsistencies in products being developed for decision making, and have caused unnecessary spending of field assets. This hinders the Navy’s ability to ensure that naval forces are prepared for expeditionary operations, which involve deploying and operating in various environments away from established bases. OPNAV N834 is seeking an expansion of the ELMS/Jupiter Data Sharing Agreement to enhance the current expeditionary enterprise's data capabilities.
Recommended:
OPNAV N834 seeks an ELMS/Jupiter Data Sharing Agreement expansion. Jupiter is currently receiving the ELMS Asset table, reflecting a subset of the ICN Report and the Over / Under Report. OPNAV N834 seeks a full ICN report to include the “Is a Kit” field that provides the expeditionary enterprise the ability to track inventory at the assembly level. Providing logic or code used to produce the field 'Is A Kit' would help drive comparisons capabilities in the current subset of data available within Jupiter. OPNAV N834 additional seeks a full Over / Under to include the "On Hand Qty", "Total Price", "Size Category", "Kitted Qty", "Unkitted Qty", "Due In Qty", "Issued Qty", "Total Qty", "Min Stock Qty", "Max Stock Qty", and "Shortage/Overage Qty" fields to support the tracking of personnel gear on hand to understand each central issuing facility's health in comparison to requirements, thus enhancing the expeditionary community's ability to quantify supply readiness and remedy identified shortfalls.
Mission Critical:
MEMORANDUM FOR SENIOR PENTAGON LEADERSHIP COMMANDERS OF THE COMBATANT COMMANDS DEFENSE AGENCY AND DOD FIELD ACTIVITY DIRECTORS.
SUBJECT: Creating Data Advantage Benefits:
By leveraging the Department of the Navy’s Jupiter enterprise data environment, OPNAV N834 and its expeditionary enterprise can expand technical capabilities by ensuring access to a centralized data environment; where users can retrieve readiness dashboards comparisons of EXMIS requirements data and ELMS inventory data. The N834 dashboards and analytic products will improve compliance and risk management, enhance equipment and supply lifecycle projections and reduce cost, grow analytic capability, and support the expeditionary enterprise decision makers at all levels on pertinent information.Frequency: Daily
Users:
There are approximately 250 users in the expeditionary enterprise that are working on comparing equipment requirements to inventory. In order to provide status updates to the executive director, each SYSCOM is manually comparing requirements to inventory data resulting in a lot of man-hours to product executive level view. Overall, this will enhance Readiness across the expeditionary enterprise and allow prioritization of filling equipment gaps.
|
|
| 02223 | Excess MRO PA/ICP process | PA,Materiel Management | FH-AFHAF | New | Change Request: Process Improvement
Description:
Throughout the Air Force we have excess or mal-postioned equipment that requires redistribution. However we require the capability to identify the property records in question, and ability to fill an open Requisition, with assets that have been identified as excess or mal-positioned.Recommended:
Leverage the MRO process within ELMS to fill open requisitions where an overage has been identified for redistribution. Additionally provide the capability to determine if a pending authorization request is in work, include a workflow approved/disapprove process with comments when a disapproval occurs.
Mission Critical:
DLM 4000.25 Vol 2
AFMAN 23-300 Benefits:
Alleviates the manual process we currently undergo to identify excess/mal-postion assets and provides the capability for Item Managers to fill viable requisitions with assets available fro redistribution. Frequency: Daily
Users: All DAF Property Admin and Centralized functions ~2K users
|
|
| 02222 | ELMS change to support FMR changes | PA,Materiel Management | DLA | New | Change Request: Process Improvement
Description:
The DoD 7000.14R Financial Management Regulation "FMR" contains changes regarding support for asset valuation and depreciable useful life. 1. The most significant update is authorizing the organization to establish a depreciable useful life that is greater than than the useful life value defined within the FMR as long as the organization has documentation to support a different depreciable useful life. ELMS does permit the user to modify the value downward, but not above the FMR value.
2. ELMS does not systemically extend the base asset's or any of its improvements depreciable useful life value to the new improvement life when the capital improvement extends the useful life of the asset. ELMS has no indicator to show the improvement extended the useful life.Recommended:
1. ELMS should provide the user with the capability to enter a depreciable useful life above the values identified in the FMR table of useful life values. When this occurs, the system should provide the capability to attach the necessary documentation that authorizes the value entered.
2. ELMS should systematically extend the Useful life of the asset when an improvement extends the asset's life. To accomplish this, the improvement should have an indicator that the asset's life has been extended. When the indicator is set to TRUE, the system should review the asset and all of the improvements associated with the asset using the greatest useful life value in determining what the depreciable useful life value should be. Using that date, a determination should be made whether the asset and or any of its improvement should have a Baseline set for current accumulated deprecation with a new depreciation schedule determined for the remaining dollar amount using the new depreciable useful life end data value in calculating future depreciation amounts. Mission Critical:
This change will enable ELMS to be aligned with DoD FMR policy regarding depreciable useful life and support the change in the depreciation schedule when an improvement extends the asset's useful life beyond its current date.
Benefits:
This change will enable ELMS to be compliant with current DOD 700.14R FMR policy regarding depreciable useful lives. Note: This change will impact all organizations that utilize ELMS as their APSR. Consideration should be given when implementing this SCR that not all customers of ELMS are affiliated with the DoD / follow the DoD 7000.14R FMR for their financial guidance. As such it may require changes to how ELMS manages depreciable useful life from establishing tables by Department (Agency) in addition to having Department level flogs whether they permit something other than the values (below or above) the depreciable useful life values managed by the system. Frequency: Monthly
Users: There are 3 departments using ELMS with most having one or more capital assets.
|
|
| 02221 | Warehouse Temp Loan | MU,Warehouse | USMC | New | Change Request: Process Improvement
Description:
The current Enterprise Logistics Management System (ELMS) lacks functionality to manage equipment temporarily loaned from Maritime Prepositioning Force (MPF) ships to exercising units. When MPF equipment is issued on temporary loan, property accountability must remain with the MPF; however, gaining units often need to perform maintenance and charge costs to their own funding lines. Presently, ELMS cannot track or differentiate “temporary loaned” assets, nor can it enable non-MPF units—especially those without ELMS access—to record maintenance activities.
Recommended:
FR1. ELMS shall establish a “Temporary Loan” transaction type that maintains MPF ship ownership while documenting the gaining unit’s custody.
FR2. ELMS shall generate a loan record capturing start date, end date, MPF DODAAC, gaining unit identifier, and serialized equipment list.
FR3. ELMS shall allow reconciliation and closure of Temporary Loans upon return of equipment to the MPF ship.
FR4. ELMS shall enable gaining units to open and record maintenance work orders against temporarily loaned equipment.
FR5. ELMS shall attribute all parts, labor, and maintenance costs incurred during the Temporary Loan to the gaining unit’s funding line while retaining MPF ownership.
FR6. ELMS shall synchronize all completed maintenance actions performed by the gaining unit back into the permanent equipment record under the MPF ship account.
FR7. ELMS shall provide an interface or simplified entry method for gaining units not directly on ELMS (e.g., web portal or limited access module) to record maintenance actions.
FR8. ELMS shall allow upload or import of supporting maintenance documentation (e.g., service reports, inspection sheets, photos) to ensure continuity of records.
FR9. ELMS shall maintain a complete audit trail of all Temporary Loan actions, including initiation, extensions, maintenance, and return activities.
FR10. ELMS shall generate commander-level reports showing Temporary Loan status, current location, maintenance performed, and pending returns.
FR11. ELMS shall enable users to query Temporary Loan records by equipment serial number, loan status, MPF DODAAC, or gaining unit.
Data Elements Required:
Equipment Serial Number / NIIN / TAMCN
MPF Ship DODAAC (owning account)
Gaining Unit Identifier (DODAAC or temp loan code)
Loan Start Date / End Date
Custody Status (Active Loan, Returned, Overdue)
Maintenance Work Order Number(s)
Funding Line (MPF vs Gaining Unit)
Maintenance History Updates (parts, labor, costs)
Approver EDIPI / Authority for Loan
Expected Benefits
Continuous Accountability: Preserves MPF ownership records while tracking custody at the exercising unit.
Maintenance Continuity: Ensures no gaps in equipment history when maintenance occurs outside of MPF
custody.
Funding Flexibility: Allows gaining unit to apply their funding lines for maintenance performed during exercises or missions.
Operational Readiness: Provides commanders full visibility of MPF assets, including maintenance status, while on temporary loan.
Audit Compliance: Creates traceable loan records to support inspections, audits, and financial accountability requirements.Mission Critical:
Compliance Requirement Benefits:
-Meets MARCORLOGCOM’s business model
-Assists in 100% accountability of assets.
-Complies with current audit controls.
Frequency: Daily
Users:
USMC users utilizing temporary loans in Warehouse and Maintenance |
|
| 02220 | SL-3 Inventory Accountability | PA,MU,Warehouse | USMC | New | Change Request: Process Improvement
Description:
The current Enterprise Logistics Management System (ELMS) lacks an integrated capability to conduct, record, and track SL-3 component inventories in alignment with Marine Corps policy and readiness standards. As a result, units are forced to rely on manual or locally developed processes that vary across commands and lack standardization, auditability, and automated linkage to maintenance and supply corrective actions.This deficiency creates compliance gaps with established Marine Corps doctrine—specifically MCO 4400.201 (Supply Administration Manual), MCO 4790.2 (Integrated Maintenance Management System Procedures Manual), and MCO 3000.18B (Total Force Readiness Process)—which require commanders to maintain accurate SL-3 accountability, document shortages, and ensure timely corrective action reporting.Without an electronic SL-3 inventory mechanism, ELMS cannot provide commanders and higher headquarters with real-time visibility of shortages or readiness impacts, nor can it meet internal control and audit readiness standards outlined in DoDI 5000.64 and the Standards for Internal Control in the Federal Government. This gap increases administrative workload, elevates the risk of human error, delays the reporting of unfunded deficiencies, and ultimately degrades equipment readiness and accountability across the Marine Corps.
Recommended:
FR1. ELMS shall provide a dedicated SL-3 Inventory Module located under the Equipment Records tab to support electronic SL-3 inventory management in accordance with MCO 4400.201 and MCO 4790.2.
FR2. ELMS shall restrict access to the SL-3 Inventory Module based on user roles (e.g., Maintainer, Supply Clerk, Inspector, Approving Official) to ensure only authorized personnel can initiate, certify, and approve SL-3 inventories.
FR3. ELMS shall allow users to conduct, record, and certify SL-3 inventories electronically at prescribed intervals (acceptance, cyclic, change of custody, and directed inventories).
FR4. ELMS shall associate each SL-3 inventory with a parent end item’s serial number, TAMCN, and DODAAC to ensure full traceability of component accountability.
FR5. ELMS shall require digital certification of completed SL-3 inventories using authenticated user credentials (CAC/EDIPI), creating a permanent audit log entry of the certifying official.
FR6. ELMS shall archive all completed SL-3 inventories and allow users to retrieve historical inventory data by end item, date, unit, or certifying official for audit and review.
FR7. ELMS shall automatically generate maintenance or supply Work Orders for all shortages or unserviceable SL-3 items identified during inventory certification, in accordance with DoDI 5000.64 and DLMS.
FR8. ELMS shall maintain a shortage log linked to each SL-3 inventory, showing open deficiencies, corrective actions, and closure status.
FR9. ELMS shall allow users to reclassify missing or unserviceable SL-3 components as Unfunded Deficiencies, and automatically report these to readiness tracking systems per MCO 3000.18B.
FR10. ELMS shall interface with readiness reporting systems (e.g., DRRS-MC, MCTFS, GCSS-MC) to update equipment readiness status based on SL-3 deficiencies or corrective actions.
FR12. ELMS shall allow users to upload supporting documentation (e.g., inventory checklists, photos, shortage letters, or certification memos) and link them to the SL-3 record for full audit traceability.
FR13. ELMS shall record all user actions within the SL-3 Inventory Module (create, modify, certify, approve, or close) with time, date, and user EDIPI to satisfy RMF and GAO internal control standards.
FR14. ELMS shall generate an automated traceability matrix linking SL-3 inventory results, Work Orders, corrective actions, and readiness impacts to provide commanders with visibility and compliance evidence.
FR15. ELMS shall provide configurable reports showing SL-3 inventory status, shortages by unit or TAMCN, aging of open deficiencies, and overall compliance rate with inventory cycles.
FR16. ELMS shall trigger mandatory SL-3 inventories upon events such as:Equipment induction or acceptance,Change of custody or unit assignment,Cyclic interval expiration (as defined in MCO 4400.201), orDirected inventory per command policy.
FR17. ELMS shall enforce validation rules to prevent certification of incomplete or unsigned inventories, ensuring all items are accounted for before submission.
FR18. ELMS shall link each SL-3 inventory to the corresponding Equipment Record to ensure any shortages or repairs are reflected in the parent equipment’s maintenance and supply data.
FR19. ELMS shall provide a dashboard view summarizing SL-3 inventory compliance, open deficiencies, and readiness impacts across all assigned equipment for commander-level oversight.
Mission Critical:
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 |
|
| 02219 | Maintenance Records | PA,MU,Warehouse | USMC | New | Change Request: Process Improvement
Description:
A material weakness exists in the Marine Corps’ ability to maintain complete, lifecycle maintenance records by serial number for all Military Equipment (ME), including Class VII, Class IX SAC II Secondary Reparables (SECREPS), and Calibration/TMDE assets. Current systems do not provide an integrated record within ELMS that captures end-to-end maintenance history, configuration data, and sustainment attributes across the asset’s lifecycle.
The Marine Corps requires ELMS to serve as the authoritative system of record (APSR) for maintenance, enabling a comprehensive, serial-number-based maintenance record that virtually represents each physical asset. This capability must ensure traceable maintenance history, sustainment data integrity, and automated reporting to support readiness assessments, sustainment health metrics, and compliance with DoD and Service-level maintenance directives.
Recommended:
FR 1. ELMS shall make all maintenance records queryable and viewable from the Property Accountability (PA), Maintenance (MU), and Warehouse Management (WM) modules.
FR 2. ELMS shall organize maintenance data as one Maintenance Record per unique serial number for all Class VII, Class IX SAC II SECREPS, and TMDE assets.
FR 3. ELMS shall list all current, active, and historical Work Orders (WO) associated with the equipment in accordance with MCO 4790.25.
FR 4. ELMS shall display Preventive Maintenance Checks and Services (PMCS) schedules and completion dates per MCO 4790.25.
FR 5. ELMS shall record calibration status, type, and schedule information in accordance with MCO 4790.25.
FR 6. ELMS shall list applicable Modification Instructions (MIs) including due dates, type, and completion status per MCO 4790.25.
FR 7. ELMS shall display core equipment characteristics including Serial Number, NSN, Nomenclature, ID Number, TAMCN, Model Number, and OTC per MCO 4790.25 and MCO 4400.201.
FR 8. ELMS shall identify equipment owner and location by unit name and UIC, and show loan status when applicable.
FR 9. ELMS shall maintain complete equipment custody history per MCO 4790.25 and MCO 4400.201.
FR 10. ELMS shall display editable equipment configuration showing parent/child relationships among Class VII, Class IX SAC II SECREPS, and TMDE items.
FR 11. ELMS shall include an inventory control function to track all published stock list items associated with maintenance activities.
FR 12. ELMS shall include a photograph field at the TAMCN level for all Class VII, SECREPS, and TMDE items.
FR 14. ELMS shall track and display equipment readiness status (MC, PMC, NMCS, NMCM) with timestamps and historical changes in accordance with MCO 3110.05 and MCO 4790.25.
FR 15. ELMS shall record warranty information and status per MCO 4105.2.
FR 16. ELMS shall record Corrosion Prevention and Control (CPAC) status and date per MCO 4790.25.
FR 17. ELMS shall track equipment usage counters such as hours, days, rounds, and miles per MCO 4790.25.
FR 18. ELMS shall record total maintenance cost by cumulative labor hours and material cost in accordance with MCO 3110.05.
FR 19. ELMS shall maintain current condition code and date assigned per MCO 4400.201.
FR 20. ELMS shall record Care of Supplies in Storage (COSIS) status, condition, and inspection dates per NFR 2021-0032-FIN-GFMC.
FR 21. ELMS shall allow recording of multiple load test types and dates per MCO 11262.
FR 22. ELMS shall provide document upload capability for attaching files to the maintenance record.
FR 23. ELMS shall auto-populate maintenance record data fields based on actions performed in the PA, MU, and WM modules.
FR 24. ELMS shall allow user editing of maintenance record data fields only when information is not automatically populated from other modules.
FR 25. ELMS shall prohibit free-text entry for all structured data fields, requiring use of drop-down menus, radio buttons, or linked query lists to ensure data uniformity.
Mission Critical:
Response to Audit Finding - NFR 2018-FIN-059 (DM&R), 2021-0032-FIN-GFMC (COSIS)Compliance Requirement - 117, 4323, 4324 of Title10, U.S.C. & DoDI 4151.18, 3110.05
Benefits:
-Meets MARCORLOGCOM’s business model
-Assists in 100% accountability of assets.
-Complies with current audit controls.
Frequency: Daily
Users:
-All USMC Users |
|
| 02218 | Linking of Work Orders | MU,Warehouse | USMC | New | Change Request: Process Improvement
Description:
Recommended:
Work Order Linking and Traceability
• FR1.2.1: The system shall support virtual linking of related work orders, even if they are executed by different maintenance activities.
• FR1.2.2: Linked work orders shall be viewable as part of a unified maintenance trail, showing actions across multiple units or echelons.
• FR1.2.3: Users shall be able to drill down into individual work orders from the summary view.
Daily Maintenance Production Reporting
• FR1.3.1: The system shall generate daily production reports summarizing maintenance activity for each unit.
• FR1.3.2: Reports shall include key metrics such as equipment job statues, problem codes, priority, parts ordered, etc….
• FR1.3.3: Users shall be able to export reports in PDF and Excel formats.
Automated Notifications for Work Order Closure
• FR1.4.1: The system shall automatically notify the using unit or work group via email when a work order is closed by a higher-echelon maintenance activity (e.g., IMA).
• FR1.4.2: Notifications shall include details such as equipment ID, work performed, and date/time of closure.
System Usability
• NFR2.1.1: The user interface shall be designed for ease of use by Marines in logistics, maintenance, and command roles.
• NFR2.1.2: Key functions shall be accessible within three clicks from the home screen.
Performance
• NFR2.2.1: The system shall respond to user queries (e.g., viewing maintenance status) in under 2 seconds during normal operations.
• NFR2.2.2: Report generation shall complete within 10 seconds for units with up to 500 assets.Scalability
• NFR2.3.1: The system shall support simultaneous use by all active-duty and Reserve Marine Corps units.
• NFR2.3.2: The system shall be capable of scaling to manage maintenance records for over 1 million serialized assets.
Availability
• NFR2.5.1: The system shall maintain 99.9% uptime during standard operational hours (0600–2200, local unit time).
• NFR2.5.2: The system shall support offline data entry for field use, with synchronization upon reconnection.
Custom Report Generation
• Users shall be able to create custom reports based on filters like unit, maintenance echelon, date range, and equipment type.
Trend Analysis
• The system shall provide visual analytics (charts, graphs) showing trends in equipment readiness, repair turnaround times, and maintenance bottlenecks.
Role-Specific Dashboards
• Commanders, maintainers, and logistics officers shall each have tailored dashboards showing relevant KPIs and action items.
Mission Critical:
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 |
|
| 02217 | Layette Management | MU,Warehouse | USMC | New | Change Request: Process Improvement
Description:
Current warehouse management processes within legacy systems such as GCSS-MC do not fully support the operational needs of Marine Corps maintenance shops. While warehouses manage stockage, storage, and issue functions, they operate independently from maintenance work order execution, tool control, and material tracking. This lack of integration results in delayed parts availability, limited visibility of consumables and controlled items, and reduced readiness insight due to disconnected supply and maintenance data.Recommended:
FR1. ELMS shall establish and manage shop stock lists (including bench stock, kits, and authorized allowances) linked to specific maintenance activities.
FR2.ELMS shall automatically allocate and reserve material for all open and approved maintenance work orders based on stock availability.
FR3. ELMS shall display real-time visibility of material availability at the shop-floor level, including statuses: available, reserved, or on-order.
FR4. ELMS shall enable warehouse personnel to generate requisitions for maintenance material shortages when on-hand balances are insufficient.
FR5. ELMS shall allow direct material issue to maintenance work orders or shop stock accounts with system-generated electronic documentation equivalent to DD Form 1348.
FR6. ELMS shall provide real-time tracking of all materials issued to a specific maintenance action.
FR7. ELMS shall enable the return of unused or excess parts from maintenance shops into warehouse stock for reissue or credit.
FR8. ELMS shall process and track recoverable items (D-level repairables) including turn-in actions against the original requisition or work order.
FR9. ELMS shall manage excess shop stock by enabling transfers back to warehouse inventory or redistribution to other maintenance activities.
FR10. ELMS shall track controlled tools, TMDE, and serialized shop equipment checked in and out by maintenance personnel.
FR11. ELMS shall maintain calibration records and next due dates for all TMDE and controlled tooling stored in warehouse or tool rooms.
FR12. ELMS shall prevent issuance of uncalibrated or overdue tools to maintenance shops.
FR13. ELMS shall provide dashboards and reports displaying open work orders with associated material availability and fulfillment status.
FR14. ELMS shall synchronize all warehouse inventory transactions with the Maintenance Module to support accurate readiness reporting.
5. Data Elements Required:
Work Order Number (linked to warehouse transaction)
DODAAC / Shop ID
NSN / NIIN
TAMCN / Part Description
Serial Number (if serialized)
Quantity (issued/returned)
Tool/Calibration ID (if applicable)
Warehouse Location / Bin
Issuer EDIPI / Receiver EDIPI
Date/Time Stamp
Condition Code
Requisition Number (if external sourcing needed)
Expected Benefits
Operational Readiness: Ensures maintenance shops have required parts and tools on hand to execute repairs on time.
Efficiency: Reduces downtime due to material shortages by integrating shop requirements with warehouse operations.
Accountability: Maintains visibility of issued items, tools, and recoverable, preventing loss or misuse.
Transparency: Provides commanders and supply officers with real-time data on material support to maintenance.
Mission Critical:
Compliance Requirement - 4000.201 Vol. 3 sub inventory management. MCO 4790.2Benefits:
-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 |
Disclaimer | Accessibility