Description: 
ELMS M&U Module Work Order does not have a "Set ALL FMC" button with Data/Time selection for all sub work orders.  

Mission Critical: 

Benefits: 
Removes repetitive process and saves warfighter valuable time to execute higher priority functions instead of click buttons within ELMS.

 

Frequency: 

Hourly

Users: 
This process improvement benefits DoW Agencies and federal services utilizing M&U Work Order on a daily basis

Description: 
Site managers cannot view all DF-VEHS Helpdesk tickets within Property Accountability Module.

Mission Critical: 

Benefits: 
Allow any DF-VEHS (or any site owner) ELMS Teams ability to view and track all Helpdesk Tickets via Property Accountability Module.  Ensuring any personnel changeover streamlines Helpdesk tickets remain viewable to responsible office.

 

Frequency: 

Hourly

Users: 
This process improvement benefits DoW Agencies and federal services utilizing Property Accountability Module on a daily basis

Description: 
To meet DOW mandate for system-to-system interface, the Department of the Air Force requests an API link from DLA Energy to DLA ELMS to capture fuel utilization.  Eliminating the current manual upload DLA fuel data process.

Mission Critical: 

Benefits: 
Implementing system change greatly improves ELMS data accuracy for FAST, sustainment budgeting and financial reporting. Creating a automated data feed provides accurate data, increases the data input and reducing missing fuel purchases

 

Frequency: 

Daily

Users: 
Effects DoW and federal agencies utilizing DLA for fuel input requirements

Description: 
Currently Warehouse Stock Number Catalog cannot search by manufacture part number or cage code adding excessive work load for users.  System has this vital information but prevents warfighter accessing via system searches.

Mission Critical: 

Benefits: 
Streamlines warfighter tasks to execute Department of War missions. Additionally, provides uniformity in both locations for Stock Number search fields.

 

Frequency: 

Hourly

 

Users: 
This process improvement benefits DoW Agencies and Military Services utilizing Warehouse Module on a daily basis

Description: 
Currently several fields on the stock number catalog in ELMS are locked down for edit regardless of if the incoming change is from an external SoT such as FLIS or AESIP or user provided. This requires users to submit script requests for the team to process the updates. Any stock number update the ELMS team can support via data-script should be able to be applied through the system. These fields include: management code, manufacturer and meter requirements, shelf life code/ expiration months / override date, UI / stocking UI, TAC, ACC, ARC, and the stock number itself. In addition the system also allows the "realignment" of stock numbers to an external source, however, there is no way to un-align a stock number once the association is made. Example you cannot convert a FLIS manged stock number to locally managed.

Mission Critical: 

Benefits: 
Improved catalog management flexibility for the end-user and an overall reduction of data script / help ticket requests

 

Frequency: 

Weekly

 

Users: 
N/A

 

Description: 
ELMS M&U lacks the capability to assign sub work orders (jobs) outside of the asset's owning Main Activity. Scenarios occur where the specific sub work order (job) exceeds the capability of the assigned Maint Activity and requires work accomplished at another Maint Activity.  Ownership of the asset is not transfered, therefore the external Maint Activity does not have access to the originating work order.  Documentation of work must be taken against the originating work order, linking the sustainment history to the asset's property record.

Create a process to assign sub work orders to Maint Activities and Equipment Pools outside of the asset's owning UIC and assigned Maint Activity. Maint Asset Master (MAM) record and work order header would remain with the owning UIC and Maint Activity, and the servicing Main Activity will have access to the assigned sub work order with edit capabilities. The servicing activity should have read only access to the work order header for informational purposes only.
Under the sub work order, create a section where you can select the Maint Activity and Equipment Pool that will perform the work. Selectable options should be limited based on configuration set by the Maint Director role currently in production. Create a process under Master Data > Maint Activity where the Maint Director can identify what external Maint Activities provide support and should be available to assign sub work orders. Selectable Maint Activities should be open across the Site Id with search criteria options of Site Id, Maint Program, Maint Activity, and Equipment Pool allowing the Maint Director to drill down to the specific option.

Mission Critical: 

Benefits: 
This will enable the Air Force to achieve the desired effects in improving overall readiness and war-fighter support.

 

Frequency: 

Daily

 

 

Description: 
Maintenance Program, Maintenance Group Id, and Custodian Number are available data fields in the Maint Asset extract but are are not available as search criteria options.  Theses data fields are used to segregate assets by ownership and maintenance management practices and often require data analysis specific to their area.  Not having these as search criteria forces the user to retrieve and extract unnecessary data and use external tools such as Excel to filter the data set to the desired options.  

Add Maintenance Program, Maintenance Group Id, and Custodian Number as search criteria under the Maintenance Asset Inquiry extract.

Mission Critical: 

Benefits: 
This will enable the Air Force to achieve the desired effects in improving overall readiness and war-fighter support. Strengthens Air Force Enterprise visibility of Readiness posturing.

 

Frequency: 

Daily

 

 

Description: 
Per TO 00-20-1 and throughout the aircraft and equipment maintenance community utilizing red "X"; "-"  "/"  symbols on maintenance documents is to make system status instantly apparent. They indicate the condition, fitness of operation, servicing, inspection, and maintenance status of the aerospace vehicle or equipment. The Red X represents the most serious possible condition. This will also make the MIS consistent with AFTO 244 documentation requirements, IAW TO 00-20-1.  Non-use of symbols creates a safety issue as symbols inform operators of the condition of the equipment whereas FMC, NMC, & PMC are used to indicate a status to equipment owners/maintainers and higher level leaders for decision making and data mining.

Within the M&U module, add the following symbols in Red colored font: "X"; "-"  "/" documentation capability to indicate condition of equipment via work orders. Create a toggle at the Maintenance Program Level to select "Use of Symbols". Once selected, the ELMS 244 will not read FMC, PMC, or NMC, but X, /, - and an additional field will be populated in the Sub-Work Order for the symbol. Logic behind the symbols will need to be set at the Sub Work Order level: NMC of any variant = "X", PMC = "/" and FMC work orders need to have the option of "/" or "- " set by the user.

Mission Critical: 

Benefits: 
This will allow AFTO Form 244 documentation to meet current technical order 00-20-1 and AFI requirements and provide users the ability to immediately identify the condition of support equipment, mitigating the safety issue; aligns with the acft mx community's standardization of using symbols on maintenance documents to make important notations instantly apparent.

 

Frequency: 

Hourly

 

New System Process

N/A

 

Description: 
The existing workflow for securing digital signatures is labor-intensive: users must manually download documents as PDFs, insert signature blocks, facilitate individual signing, and then re-upload the finalized files to ELMS. This multi-step process creates significant administrative lag.

Enable secure digital signing for all issue and return forms (Individual, Unit, and Warehouse) using a DOD CAC reader for signing the transaction.  Similar to using a signature pad the digital signature will stay on the issue/return record.

Mission Critical: 

Benefits: 
This implementation will significantly streamline equipment processing times, accelerating the turnaround for Individual, Unit, and Warehouse transactions.

 

Frequency: 

Hourly

 

Users: 
All Users

Process Improvement

Description: 
The LESO requires a systematic research process to prevent the over-allocation of excess property to Law Enforcement Agencies (LEAs) in the DoW 1033 program. A lack of visibility into past and current property transfers creates a risk of improper allocation and inefficient resource management

 

Recommended: 
See Attachment (ELMS SCR - Allocation_Report.docx)

 

Mission Critical: 

Enhanced Accountability and Compliance; Improved Resource Management and Efficiency; Strengthened Program Integrity and Public Trust; Data-Driven Decision Making; Mitigation of Risk

 

Frequency: 

Daily

 

 

Description: 
The current automated version of the AFTO Form 244 does not fully comply with Air Force policy requiring accurate documentation of maintenance and inspections on aviation support equipment (ASE) as outlined in TO 00-20-1 and AvSE Interim Guidance. Current guidance requires the phase out ELMS auto-generated 244 and use of DAF AFTO 244 upon completion of inspection or requiring new DAF AFTO 244 whichever comes first.  Specifically, it does not allow for proper inclusion of status symbols or the documentation of partially mission capable (PMC) conditions, which are essential for tracking ASE readiness and serviceability.

 

A SCR is underway to incorporate PMC status and additional capabilities into the automated AFTO 244.  It would be beneficial to align the automated output with the AFTO 244 with the requirements set forth in TO 00-20-1, would improve accuracy and reduce the risk of documentation errors.  Additionally, work plan description and work order data fields should be aligned to populate the AFTO 244 with the Service Requested as documented in the work order.  This will provide a more detailed description of the discrepancy listed on the AFTO 244. See attached examples

Mission Critical: 

Standardization of the form would improve accuracy and reduce the risk of documentation errors for field personnel utilizing the automated and official DAF AFTO 244 form, AvSE MIS Interim Guidance requires use of DAF AFTO 244 and phase out of auto-generated ELMS 244.

 

Frequency: 

Hourly

 

Users: 
8.5K personnel utilizing maintenance information system, leadership w/in Quality Assurance positions inspecting proper/compliant usage, and form is reviewed prior to utilizing Form 244's respective equipment.

 

The Uniform Distribution Center (UDC) users rely on the Inventory Transaction Inquiry on the ICP side to support end of month inventory reporting. Currently, this inquiry only displays the Unit Price, which does not always reflect the actual document unit price used at the time of the transaction. As a result, UDC personnel must navigate to Warehouse module ro locate the document unit price and do manual calculations, creating inefficiencies and increasing the risk of reporting discrepencies.
For example, in the UDC ICP (USCG) - Stock Nbr - BCPL. The Unit Price is $9.94,  but the document unit price is $8.57.

Add Document Unit Price as a selectable grid option within the Inventory Transaction Inquiry.

Mission Critical: 

Implementing this solution would eliminate the need to cross reference the warehouse module and provide a single authoritative source for reporting.

 

Frequency: 

Weekly

 

Users: 
USCG users

 

The registry currently does not have the capability to manually close out  In-Transit Registry Assets. This is required as there are many in-transits shipments that are not being auto-closed. Presently, SOCOM Registry does not reflect an accurate status of Small Arms/Light Weapons serial number data at the USSOCOM Registry.

System should allow capability to manually update in-transits for shipments that are already received by the gaining unit and verified by the designated SOCOM user. SOCOM requests a Manual Close-out capability in Registry similar to the manual update function at ICP with the ability to attach supporting transaction documents.

Mission Critical: 
To follow DLMS 4000-25, Volume 2, Chapter 30

-This change will enable ability to reconcile assets status at USSOCOM Registry
-USSOCOM Registry will serve as one stop module for weapons FOIA inquiries request

 

Frequency: 

Daily

 

Users: 
Recommend change to Registry Agency Manager Level Role to enable manual closeout process for In Transit Weapons transactions that USSOCOM has confirmed receipt of by either gaining customer, or the gaining Warehouse activity.

 

Expansion of data fields from ELMS available to ADVANA, the current USSOCOM data feed is limited to the On Hand/Asset Visibility Data

 

Provide data elements as indicated on attached Excel Document. This will expand the ELMS data available to ADVANA for USSOCOM Data Dashboards and decision making

Mission Critical: 
Supports USSOCOM ability  to meet its Title X, U.S.C. Sec. 164 & 167 responsibilities. Supports USSOCOM compliance of DoDD 8190.01E, DLM 4000.25, DoDI 4140.01, DoDI 5000.64, DoDM 4140.01 V8, DoDM 4140.01 V11, DoDI 4161.02, FMR 7000.14, FAR & DFARS, and FIAR initiatives.

 

Enables USSOCOM to meet its Title X, U.S.C. Sec. 164 & 167 responsibilities.

 

Frequency: 

Daily

 

Users: 
All ADVANA users of the USSOCOM SPARTA enclave

 

DLMS ADC 1510 provides new data fields for the DLMS 832N transaction - added are the reportable method for OM&S and the weapon system variant. Need ELMS to add the new data fields to the catalog and to the 832N and include in DLMS transaction processing (including 824R reject transaction).

 

Make necessary changes in the ICP module process and correctly handle the reportable method of OM&S and the weapon system variant.  Users will see new data in the DLMS transaction viewer and ELMS will include these new data elements in the DLMS 824R Reject notification process.

Mission Critical: 
ADC 1510 signed 2/5/2026

 

The added data elements within the 832N will allow the services to determine their reportable methodology for OM&S and any subsequent 824R Reject notifications to AF CICPs.

 

Frequency: 

Weekly

 

In the current Warehouse module, there is no functionality to add stock numbers that were not originally designated as Kits to the SKO Catalog. The existing rule set dictates that if any verified transactions—regardless of their state (open or closed)—exist for a stock number where it was treated as a normal end item, that stock number cannot later be designated as an SKO Header in the SKO Catalog.
This restriction applies to all transaction types, including receiving transactions. For example, if assets were ever received into the Logistics Point (LP) under a stock number as normal end items, the act of receiving those assets permanently prevents that stock number from being converted into an SKO Header in the SKO Catalog, even if the inventory associated with that stock number is subsequently removed. This limitation ensures consistency in the system but may require additional planning when managing stock numbers intended for SKO use.

 

 

Enable the capability to utilize previously used stock numbers, even those with historical records as assets categorized as end items, as SKO Headers within the SKO Catalog. This functionality would provide greater flexibility in managing stock numbers, allowing them to be repurposed for kitting processes while maintaining consistency and traceability in the system.

 

Army Regulation (AR) 700-18: Covers logistics and supply chain management, including kitting processes.
MIL-STD-973: Establishes standards for configuration management across DoD programs.

Reducing this limitation enhances system flexibility while maintaining consistency, allowing users to fully meet the intent of various kitting functionalities. This improvement supports diverse configurations within the SKO process, enabling more efficient management and adaptation to evolving operational requirements.

 

Frequency: Daily

 

 

Users: All

When navigating to Inquiries and then Issue/Return Activity, issue, return, and charge transactions are not visible by default and require expanding the arrow for each transaction to view the details.

 

 Configure the Issue/Return Activity screen to display issue, return, and charge transactions by default, eliminating the need to expand the arrow for each transaction. The current Issue with Return Details view is close to the desired outcome; however, the goal is to display all transactions line by line without requiring users to expand each entry to view returns, issues, or charges. All existing columns—such as cost, issuer, item, and related details—are already correct and should remain unchanged.

 

 

 

Frequency: Daily

 

Users: This system is used daily to review and manage issue, return, and charge transactions as part of regular operational workflows. Users rely on it to quickly access complete transaction details, verify accuracy, resolve discrepancies, and support timely decision-making. Because the system is a routine part of daily work, clear visibility of all transaction types is essential to ensure efficient reviews, reduce delays, and maintain accuracy across ongoing operations.

ELMS sends Property Accountability and Warehouse materiel / assets to Advana as part of its Asset Feed each Saturday and the first of the month.  It does not send materiel / assets that are managed by Contractor Operated Inventory Control Points (C-ICPs) or materiel managed by External Remote Storage Activities e.g. DLA, Army, Navy, etc. that are being reported to the ELMS Materiel Mgmt. application.  Including this materiel in the data feed will provide full visibility to the owners.

 

1. Add materiel / assets to the ELMS Advana Asset Feed that are not managed within ELMS, but are reported to ELMS Materiel Mgmt.  Client Cd 'C', 'E' and 'R' apply.
2. Make the same extract available to other entities that utilize the same feed e.g. Vantage, LDS/MDR, SOLMAN, NSWC, etc. should they wish to receive this data as part of the ELMS feed.  

 

 

 

 

Frequency: Weekly

Users: Agencies that will use this informations include: ASA(ALT), JSF, AF GFM-A, USSOCOM, USMC, etc.

 

Update ELMS Capital Threshold table for Navy General Fund to $15 Million effective Oct 1, 2025 (FY26).

 

Provides updated capital thresholds for the Department of Navy

 

 

Frequency: Hourly

Users: All Navy users with capital assets.