|
02232
|
Enhance Issue and Return Functionality
|
Warehouse |
AF: USAFA |
New |
Change Request: Process Improvement
Description:
• Issue and Return processes are separated into different tabs.
• To verify a cadet’s account history prior to issuing an item, staff must navigate to the Return screen, then switch back to the Issue screen.
• Item cost and charge information is not visible during the issue/return process and must be accessed through other systems or screens.
• These steps add approximately one minute per cadet and significantly slow down operations during high-volume periods.
Recommended:
The requested functionality includes creating a single unified Issue and Return screen that combines both processes into one interface, allowing staff to remain in Issue or Return mode—or perform issuing, returning, and charging simultaneously—after scanning a cadet’s CAC card, eliminating the need to switch tabs. Upon scanning, the system should immediately display the cadet’s full issue and return history on the same screen, including currently issued items and prior transactions, enabling staff to prevent duplicate issues such as issuing a second ruck when one is already on record. The interface should also provide item cost and potential charge transparency by displaying pricing information as each item is scanned, recording those costs in the cadet’s history for audit and accountability purposes, and reducing confusion or disputes over replacement or loss charges. Overall operational efficiency should be improved by enabling account verification, pricing review, and item issuing or returning from a single screen, reducing processing time per cadet. Additionally, the system should reintroduce an account lock or alert feature similar to the legacy system, with prominent red warnings for locked accounts (ex, “Lost saber – replacement already issued”) and the ability for staff to add notes to cadet accounts, helping prevent duplicate issues, conflicts, and frustration for both staff and cadets.
Mission Critical:
The process of improvement focuses on streamlining and enhancing the Issue and Return workflow by consolidating functionality into a single, unified screen. By combining issuing, returning, and charging actions within one interface, staff can complete all related tasks without switching tabs, reducing complexity and errors. Immediate visibility of a cadet’s full issue and return history upon CAC scan improves decision-making and prevents duplicate item issuance. Displaying item costs and potential charges at the time of scanning increases transparency, strengthens accountability, and minimizes disputes related to lost or replacement items. Operational efficiency is further improved by enabling account verification, pricing review, and transactions from a single screen, reducing processing time per cadet and increasing throughput. Reintroducing an account lock and alert mechanism with prominent warnings and staff notes enhances control, prevents repeat issues, and supports consistent enforcement of policies, resulting in a more efficient, accurate, and user-friendly system overall.
Benefits:
Introducing this functionality provides significant benefits by improving accuracy, transparency, and efficiency across the Issue and Return process. A single unified screen reduces staff workload and training complexity while minimizing errors caused by switching between tabs or systems. Immediate access to a cadet’s complete issue and return history helps prevent duplicate issuances and ensures better accountability for equipment. Real-time visibility of item costs and potential charges increases transparency for both staff and cadets, reducing confusion, disputes, and time spent resolving billing issues. Enhanced operational efficiency shortens processing time per cadet, improves throughput during peak periods, and allows staff to focus on customer service rather than system navigation. The reintroduction of account locks, alerts, and notes strengthens oversight, prevents repeat losses or improper reissues, and promotes consistent policy enforcement, ultimately resulting in a more reliable, user-friendly, and trusted system.
Frequency: Hourly
Users: This process is performed multiple times throughout the day, often repeatedly during normal operations, especially during peak issue and return periods.
|
|
02231
|
Work Order Serviced by External (Warranties) – Warehouse Issue DD1149
|
MU,Warehouse |
Army ASA(ALT) |
New |
Change Request: Process Improvement
Description:
When an asset comes in for routine or non-routine maintenance and the asset is under warranty current capability within work order provides the ability to mark the work order as being “Serviced By” external organizations. However, the current capability is limited to only marking that the asset is being serviced by an external organization and does not accommodate the ability to show the asset as being shipped to the external organization and print the DD1149 for shipment. It also leaves the associated WM Inventory record in WM Inventory even though the ICN is no longer on hand but is instead shipped to the servicer.
Recommended:
See Attached supporting file
Mission Critical:
This initiative enables the PEO community to achieve compliance with policy and audit requirements by ensuring transparency and effective life-cycle management of inventory.
Benefits:
It provides the necessary framework for PEOs to maintain accountability and oversight of assets within their purview, supporting operational readiness and aligning with enterprise-level objectives.
Frequency: Daily
Users: ~450 users
|
|
02230
|
Modify Warehouse SKO components in Work Order – Modification Work Order
|
MU,Warehouse |
Army ASA(ALT) |
New |
Change Request: Process Improvement
Description:
ASA(ALT) current applications provide functionality specifically for Inventory/Asset Modifications for both Kits as well as for end items (un-kitted). These Modification work orders provides for the ability to make modifications to numerous end items which may or may not result in a re-identification of the stock number associated to the end item. DPAS does provide re-identification functionality within Warehouse, but this functionality is manual and can only take place on a one-at-a-time basis. There is also no functionality within DPAS that manages the progress of these MWO projects.
Recommended:
See Attached supporting file
Mission Critical:
This initiative enables the PEO community to achieve compliance with policy and audit requirements by ensuring transparency and effective life-cycle management of inventory.
Benefits:
It provides the necessary framework for PEOs to maintain accountability and oversight of assets within their purview, supporting operational readiness and aligning with enterprise-level objectives.
Frequency: Daily
Users: ~450 users
|
|
02229
|
Master Asset Records - Create
|
MU,Warehouse |
Army ASA(ALT) |
New |
Change Request: Process Improvement
Description:
Currently there is no representation of warehouse inventory within associated M&U Maintenance Activities. These assets are needed in M&U in order to accommodate the creation of ad hoc work orders as well as to schedule preventative maintenance and work plans.
Recommended:
Proposed Solution (M&U and Warehouse): Provide a method in Warehouse to specify when a MAM record should be created in M&U for existing ICN’s and during Receipt. M&U should use the ICN as the Asset ID. M&U needs to also add the standard Condition Codes to MAM and use the Condition Code from warehouse. In the case when the MAM record represents a Kit in Warehouse, M&U will need to include the ability to display the component inventory of the kit (component inventory would not be a MAM record). Warehouse should continue to trigger updates to M&U as ICN information changes- Warehouse should continue to trigger updates to M&U as ICN information changes: 1Stock Number. 2 Condition Code. 3. Any other shared parameters. Proposed Solution (Warehouse Only): Use the Warehouse Inspection Action process as a means to schedule preventative maintenance. Modify the warehouse Inspection process to auto generate a Quality Control request. Add functionality to the Inspection Action process to accommodate the addition of work plan steps Utilize the Warehouse Inspection Assessment functionality within QC as a means for the users to order parts when required
Mission Critical:
This initiative enables the PEO community to achieve compliance with policy and audit requirements by ensuring transparency and effective life-cycle management of inventory
Benefits:
It provides the necessary framework for PEOs to maintain accountability and oversight of assets within their purview, supporting operational readiness and aligning with enterprise-level objectives.
Frequency: Daily
Users: ~450 users
|
|
02228
|
Physical Inventory Owner
|
Warehouse |
Army ASA(ALT) |
New |
Change Request: Process Improvement
Description:
Currently when generating a physical inventory in the ELMS Warehouse module you cannot select the following filters when using all inventory mode’s location, Condition Codes, Owning DoDAAC, Project Code, or Purpose Code. If a single warehouse has locations with multiple Condition Codes, Owning DoDAAC, Project Code, or Purpose Code the user can’t generate the physical inventory for each property owner. This is a big issue for property accountability. Each property owner should be able to sign for their property and only their property.
Recommended:
Add the following data elements to the generation of a physical inventory when using the inventory mode location.
Condition Codes, Owning DoDAAC, Project Code, or Purpose Code.
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:
All each property owner should be able to sign for their property and only their property. These data elements will allow the users to generate the physical inventories to account for specific asset and not include assets that are not needed for the inventory being generated.
Frequency: Weekly
Users: All
|
|
02227
|
Add Maint Group ID Field to Catalog Base
|
PA |
AF |
New |
Change Request: Process Improvement
Description:
Requesting the Maintenance Group Identifier (MGID) data field to be added to dbo_catalog_base file for both vehicles and equipment. MGID is a data field captured in the ELMS catalog but is currently not available in the Advana/BLADE data feed. MGID groups stock numbers based on their maintenance requirements and is used to segregate asset records when analyzing maintenance data and building metrics.
Recommended:
Modify the data feed to incorporate the newly identified data element.
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:
This data field would be beneficial to all user groups using ELMS data.
Frequency: Hourly
Users: All Advana/BLADE users of ELMS Data
|
|
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.
The required fields are listed in the attached Excel file. See tab 2 of attached Catalog Data (WPHRI08) LIMS-EV spreadsheet. Rows that are not highlighted are not being sent to BLADE today.
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.
This limitation creates a significant visibility and accountability gap. Maintenance performed during the loan period may not be captured in the MPF asset record, leading to incomplete equipment histories, inaccurate readiness reporting, and potential audit discrepancies. The Marine Corps requires ELMS to implement a controlled temporary loan capability that maintains MPF ownership while allowing gaining units to execute and record maintenance actions, ensuring full traceability of costs, maintenance history, and accountability throughout the loan lifecycle.
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.
FR11. ELMS shall send automated notifications to responsible personnel (e.g., Supply Officer, Maintenance Chief, Commander) when shortages or unserviceable SL-3 items are identified, assigned, or resolved.
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.
FR20. ELMS shall enable export of SL-3 inventory data and audit logs into standard formats (CSV, PDF, Excel) for inspection, higher-headquarters reporting, or external audit review.
Mission Critical:
Without SL-3 traceability, audit and accountability requirements (security of controlled items) are at risk. This is not a cybersecurity flaw, but a compliance/security of materiel records issue.
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 13. ELMS shall record deferred maintenance status, dates, and location by unit name and UIC in compliance with NFR 2018-FIN-059.
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.
FR 26. ELMS shall include one free-text data field labeled “Notes” for user comments not otherwise captured in structured data.
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:
The current maintenance management processes within ELMS lack full transparency and real-time visibility across all echelons of maintenance, creating operational inefficiencies and delays in decision-making for using units. Maintenance actions performed at higher echelons—such as Intermediate Maintenance Activities (IMAs)—often occur with limited visibility for the originating unit, resulting in communication gaps, tracking challenges, and uncertainty in equipment readiness status.Furthermore, the absence of a centralized system to virtually link related work orders prevents seamless end-to-end tracking of maintenance activities, making it difficult to assess equipment history, identify bottlenecks, or generate comprehensive production reports. Using units would have to rely on fragmented systems or manual updates, which can lead to outdated reporting, misaligned expectations, and reduced readiness.There is a clear need for an integrated, user-friendly Equipment Logistics Management System (ELMS) that enables real-time tracking of equipment maintenance regardless of echelon, allows virtual linking of work orders, automates daily production reporting, and provides timely notifications upon the completion of higher-echelon repairs.
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:
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 |
|
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.
To close these gaps, ELMS must deliver an integrated Warehouse Management capability that aligns inventory management directly with Maintenance Shop operations. The system must enable real-time synchronization between warehouse stock, open work orders, tool sets, kits, and material requirements—ensuring maintenance personnel have the correct parts and tools at the point of need while maintaining accountability and auditability across the enterprise.
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.
FR15. ELMS shall maintain an auditable transaction history of all shop-related warehouse issues, returns, recoverable turn-ins, and tool control actions.
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.
Audit Compliance: Ensures all warehouse-to-shop transactions are documented and retrievable.
Mission Critical:
Compliance Requirement - 4000.201 Vol. 3 sub inventory management. MCO 4790.2
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 |
|
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
|
|
|
Disclaimer | Accessibility
