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.

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

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.

 

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.

 

 

MEMORANDUM FOR SENIOR PENTAGON LEADERSHIP COMMANDERS OF THE COMBATANT COMMANDS DEFENSE AGENCY AND DOD FIELD ACTIVITY DIRECTORS.
SUBJECT: Creating Data Advantage

 

 

 

 

Frequency: Daily

 

 

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.

 

 

DLM 4000.25 Vol 2
AFMAN 23-300

 

 

 

 

Frequency: Daily

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.

 

 

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.    

 

 

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.    

 

 

 

 

Frequency: Monthly

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.

 

 

FR1. ELMS shall establish a “Temporary Loan” transaction type that maintains MPF ship ownership while documenting the gaining unit’s custody.

Data Elements Required:
Audit Compliance: Creates traceable loan records to support inspections, audits, and financial accountability requirements.

 

 

 

 

-Meets MARCORLOGCOM’s business model

-Assists in 100% accountability of assets.

-Complies with current audit controls.

 

 

Frequency: Daily