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.

DAF CICPs send 846P and 846R transactions into ELMS each day and month for a two-part reconciliation.  First part consists of 846P transactions providing an end of day transaction count.  The second part consists of 846R transactions providing an end of day inventory report.  If either part fails reconciliation, ELMS flags with a red indicator.  The reconciliation depends on users to trigger follow-up actions to correct situations causing the failure.  DAF recommends automating those follow-up actions to enable a system-to-system reconciliation that removes user intervention.  This will enable more accurate and complete inventory balances and their supporting transactions in ELMS.  This will improve financial reporting accuracy for the DAF.

 

Recommend that ELMS ICP module adds automated follow-up actions for reconciliation failures.  For the end of day transaction counts: if the reconciliation fails, ELMS should send a transaction history request to the CICP’s system for the failed transaction set.  The CICP’s system will return all the transactions for the failed transaction set for that day (marked with W1 in the appropriate action code field).  ELMS will identify the missing transaction(s) and process those as if they were received that day.  This will clear the reconciliation failure and potentially reduce the number of end of day/end of month inventory balance mismatches.  For the end of day/end of month inventory balances: if the reconciliation fails, ELMS will send inventory request transaction(s) to the CICP’S system for the mismatched stock numbers.  The CICP’s system will return the end of day/end of month inventory position by stock number.  ELMS will use those inventory balances to create 947I Inventory Adjustment transactions to update the balances to match the CICP’s system balance.  

 

 

Frequency: Daily

 

Users: This requirement improves the end of day/end of month reconciliation for the 100+ DAF CICPs

 

• 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.

 

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.

 

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.

 

 

Frequency: Hourly

 

Users: This process is performed multiple times throughout the day, often repeatedly during normal operations, especially during peak issue and return periods.

 

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.

 

See Attached supporting file

 

This initiative enables the PEO community to achieve compliance with policy and audit requirements by ensuring transparency and effective life-cycle management of inventory.

 

 

 

 

Frequency: Daily

Users: ~450 users

 

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.

 

See Attached supporting file

 

This initiative enables the PEO community to achieve compliance with policy and audit requirements by ensuring transparency and effective life-cycle management of inventory.

 

 

 

 

Frequency: Daily

Users: ~450 users

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.

 

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

 

This initiative enables the PEO community to achieve compliance with policy and audit requirements by ensuring transparency and effective life-cycle management of inventory

 

 

 

Frequency: Daily

Users: ~450 users

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.

 

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.

 

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.

 

 

 

Frequency: Weekly

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.

 

Modify the data feed to incorporate the newly identified data element.

 

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.

 

 

Frequency: Hourly

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.

 

Modify the data feed to incorporate the newly identified data elements not highlighted in attached spreadsheet.

 

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.

 

 

Frequency: Hourly

 

 

 

Implementation of any database infrastructural changes and improvements deemed necessary by the Leidos Team.

 

 

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