|
02264
|
LTS Web Service interface for TAC
|
PA,Warehouse,Materiel Management |
USAF - FH-AFHAF |
New |
Change Request:
Policy / Regulatory
Description:
Currently the application of a Transportation Account Code (TAC) as part of the transfer, disposition or shipment within ELMS is a manual input. Additionally the system does not provide a report capability that provides status of a pending shipment that might have a shipment hold code assigned due to validation error.
Recommended:
Establish web service connection with the Logistics Tool Suite (LTS) tool to perform a pre-shipment funding validation where proper TAC assignment is determined and then applied to the shipping document. Request notification to the TAC owner, Item Manager and Shipping activity if the validation results in an error. Additionally establish a Shipment hold code 'S' as outlined in ADC 1206, issued on 27 Jul 2016. Produce a report of pending, suspended or frustrated shipments that include the Shipment document number, Transportation Control Number, Shipment hold code, Stock number, and shipping activity. Report tier filter options at all levels, Agency, Site, AUIC, and UIC.
Mission Critical:
IAW DLM 4000.25 DLMS Vol 3 Transportation, Chap 2 Retail Supply Transportation Interchange; ADC 1206 Transpportation Account Code (TAC) Validation in Retail Supply and IAW DTR 4500.9-R Defense Transportation Regulation(DTR) Part II, Cargo Movement, Appendix V, TAC procedures
Benefits:
This interface helps in mitigating erroneous TAC assignments ensuring proper funding is applied.
Frequency:
Daily
Users:
All DAF users that ship materiel from ELMS.
|
|
02263
|
Auto Cataloging of Manufacturer Part Numbers
|
PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW) |
Leidos |
New |
Change Request:
Process Improvement
Description:
Manufacturer part number information is not automatically cataloged when its associated stock number is locally cataloged from an external system, requiring catalog managers manually load all desired part number information.
Recommended:
When a stock number from an external system i.e. AEMM/FLIS/SOLMAN is cataloged locally within ELMS the system will automatically query and catalog any manufacturer part number records provided by the external source associated to the cataloged stock number.
Mission Critical:
The ELMS Property Accountability application requires Mfr data to be associated with each Asset. By systematically adding the mfr data, this improves user experience and reduces the level of effort to maintain catalog data.
Benefits:
Automates the cataloging of external manufacturer part number information.
Frequency:
Hourly
Users:
Having Mfr data available improves the experience for all users. More specific, it reduces the effort of those that are responsible for cataloging items as they will no longer need to manually enter Mfr data when it is provided through an external catalog interface.
|
|
02262
|
LESO Automatic Stock Item Addition
|
MU,Warehouse,Materiel Management |
DLA - LESO |
New |
Change Request:
Process Improvement
Description:
ELMS users are required to manually assign stock items at the warehouse/DoDAAC level each time a new stock number is loaded into the system. This is required prior to any receipts being made for assets of that associated stock number.
Recommended:
Option A. Add a configuration at the Logistics Program level within ELMS to enable automatic stock item assignment. When checked stock items will automatically be applied to all warehouses across the enterprise. (For LESO warehouses will each have only one DoDAAC)
Option B. Update the receiving process to remove stock item validation preventing receipts.
Benefits:
Saves time for the end users needing to assign new NSNs to their warehouses. for example March 1 to Apr 1 LESO had 62 new NIINs to manage/add.
Frequency:
Daily
Users:
Adding new NIINs is limited to a few users with the applicable role
|
|
02261
|
Capital Asset Accounting Additions to the Capital Asset Service
|
Warehouse,Materiel Management |
DLA |
New |
Change Request:
Process Improvement
Description:
Following release of Capital Asset Accounting in ELMS Enterprise Accounting, additional required functionality is needed for completeness and optimal user experience for financial reporting. System enhancements include 1) Adding support for KSD attachments / View during FDU process, 2) Adding support for Heritage assets if they are received into a Warehouse/ICP to display their total cost in MM inquiries as well as displaying the total cost for other fixed assets, 3) Adding support for Mass Update within FDU that will provide for multiple assets to be profiled at the same time), 4) implementing DAI Interface business rules on transfers and dispositions, 5) Adding Fixed Asset counts to the MM Dashboard, and 6) other requirements that may be identified/requested by the ELMS PMO.
Recommended:
1) Allow the addition of attachments to Assets from the Accounting Financial Data Update page; 2) Add the Acquisition 'Total Cost' to MM Inventory Inquiries for Fixed Assets and allow Heritage Assets to be updated in the Financial Data Update page and display the total cost on the Inquiries; 3) Implement the ability for 'mass' update of assets on the FDU page when document number is the same; 4) Add DAI logic/handling for transferred and disposed assets on the Capital Asset Transfer page; 5) Update the MM Dashboard to include Fixed Asset records for Accounting processes
Mission Critical:
This change provides for the completion of phase 2 items related to the ELMS Capital Asset Service.
Benefits:
Required system updates for Capital Asset Accounting that will benefit all users who use the system for financial reporting of capital assets.
Frequency:
Daily
Users:
All users who use the system for financial reporting
|
|
02260
|
DLMS Returns Adjustments
|
Warehouse,Materiel Management |
Leidos |
New |
Change Request:
Policy / Regulatory
Description:
When completing an Individual Return/Reconciliation or Unit Return/Reconciliation and selecting reason code GA - FLIPL DD-FORM 200/Govt Authorized or GR - FLIPL DD-FORM 200/Govt Reimbursed, the system is recording the reason as an Issue to self (DLMS 867I / D7A) in lieu of recording the reason as a Loss (DLMS 947I (D9A).
Recommended:
Returns conducted through Individual, Item, or Unit Returns as well as similar reconciliation processes which utilize a not returned reason code of CA, GA, GR, HA, KI, LT, MD, N6, PD, or RD should send one or more 9471I DLMS transactions to manage the gain/loss of equipment.
Benefits:
The system is not outputting the preferred DLMS transaction. This change will enable ELMS to more accurately reflect the reason for the drop inventory. When an loss, it should be reflected as a DLMS 947I/D9_ and when an issue with on required return, it should be reflected as an Issue DLMS 867I (D7A).
Frequency:
Hourly
Users:
N/A
|
|
02259
|
Outstanding Unit Issue Rpt / Alternate Custodian
|
Warehouse |
Navy - NBG-2 |
New |
Change Request:
Process Improvement
Description:
ELMS Warehouse module does not produce a report linking outstanding Unit Issues to the Alternate Custodian whom assets are issued; all current reports and inquiries link outstanding Unit Issues only to the relevant Primary Custodian.
Recommended:
Inquiries > Unit Issue > Outstanding Items: add column for Alternate Custodian. Users can include optional column and export PDF report. Another option is to include relevant Alternate Custodians on Outstanding Item reports DW05UA and/or DW05UC.
Mission Critical:
Organizational policy requires maintenance activities to establish a tool control program to prevent Foreign Object Damage (FOD) of Landing Craft Air Cushion (LCAC). ACU4INST 5530.14L section 5.a.(3): Tools that have not been returned by 1600 to Tool Issue will be considered delinquent unless signed out overnight.
Benefits:
A wayward tool poses grave danger to the craft as well as it's personnel, and craft are essentially non-operational until the tool is located. Promptly associating an asset, in this case a tool, to the Custodian whom the asset was issued is a critical tool control practice to prevent Foreign Object Damage (FOD) of craft or injury to personnel.
Frequency:
Daily
Users:
All ELMS WH Users performing Unit Issues
|
|
02258
|
Provide the capability for the user to modify the Dispatch Checklist
|
MU |
Leidos |
New |
Change Request:
Process Improvement
Description:
ELMS does not provide the capability for the user to modify the dispatch checklist which can be different for each maint. activity. When an update is required, the user must submit a request via the help-desk and then wait for a script to be developed to update the checklist . Provide the capability for the user to manage the checklist without requiring a help ticket.
Recommended:
Develop a user process where they can view and edit the checklist.
Benefits:
Eliminates a help-desk ticket, reduces the time to have the update made, eliminates the need for the system developers to create and run the script which reduces the number of touch points and tracking required to accomplish the task.
Frequency:
Monthly
Users:
ELMS has 20 agencies with dispatch-able assets.
Cancelled 4/16/2026 - per request from Jonathan Anlauf
|
|
02257
|
LESO Warehouse Roles
|
Warehouse |
LESO |
New |
Change Request:
Process Improvement
Description:
The current warehouse module utilizes a role structure that does not adequately support the distinct operational needs of the various user groups involved in the Law Enforcement Support Office (LESO) 1033 program.
Recommended:
See attachment, (Roles attachment will be updated based on upcoming roles meetings)
Mission Critical:
LESO MOU; EO14288; DODIG-2020-129 (Project No. D2020-D000AT-0021.000);
Benefits:
• Enhanced User Experience: A user-friendly interface tailored to the needs of each role will lead to increased user satisfaction, reduced training time, and fewer user errors. Enhanced Security and Control: A granular RBAC model will ensure that users only have access to the information and functions necessary for their roles, reducing the risk of unauthorized actions. • Streamlined and Efficient Workflows: The new roles will align the system with the actual business processes of the 1033 program, automating tasks, reducing manual effort, and improving overall efficiency
Frequency:
Daily
Users:
This is a high-volume function utilized multiple times per day. The exact frequency is dependent on the daily number users that need to be in the system. Number of users will depend on the number of users at the Site and LP levels.
|
|
02256
|
WH to M&U Connection
|
MU,Warehouse |
NSWC |
New |
Change Request:
Process Improvement
Description:
Currently maintenance asset records are not created in M&U when receiving assets into warehouse. Equipment that isn’t on a property book could have the need to have an M&U maintenance record. In other words, the PA module doesn’t house all classes of supply and warehouse needs the ability to create maintenance records in M&U without using PA. In addition, the maintenance scheduling feature in MU is more robust than inspections in WH, and cannot be used without a Maintenance Asset record.
Recommended:
At the stock Item level within warehouse, add a check box to the stock items tab that will require a maintenance record be generated upon receiving. (Adding here will prevent it from being an LP requirement). When the asset is accepted within the receiving process, generate maintenance asset record. There also needs to be a process in place when the maintenance record exists to inactivate the record once the asset is disposed, transferred or MRO’d. A future consideration should be that when a record is transferred/MOR’d that a copy of the maintenance record should be transferred with the item.
Mission Critical:
Align warehouse with ability that PA currently has. Starts bringing together modules to work toward an end goal of a complete system in one program.
Benefits:
Improves warehousing capabilities while reducing customer requirements.
Frequency:
Daily
|
|
02255
|
LSEMS Equipment Reporting to ELMS Materiel Mgmt.
|
Materiel Management |
Leidos |
New |
Change Request:
Process Improvement
Description:
The Joint Strike Fighter program is developing DLMS transactions to report the receipt, issue, transfer, updates and disposal of activity for equipment managed within Lightning II Support Equipment Management System (LSEMS) to the Enterprise Logistics Management System (ELMS). This SCR is to provide ELMS DLMS support and testing support.
Recommended:
1. Provide DLMS support to LSEMS development personnel.
2. Provide ELMS testing support to the LSEMS program support team.
Mission Critical:
Today, users analyze the LSEM activity report to determine the activity that occurred, then manually inputs the activity into ELMS PA. This SCR that provides analysis and testing will automate the reporting to the ELMS Materiel Mgmt. application.
Benefits:
This SCR will improve the quality of the reporting, reduce the effort to report allowing for data analysis to occur.
Frequency:
Daily
Users:
This process improvement affects all users of the LSEMS data once the effort has been completed.
|
|
02254
|
Access Report to Include FAR and DFAR Requirement
|
Warehouse |
NAVSEA |
New |
Change Request:
New System Process
Description:
ELMS does not have an ADHOC report available with required data elements of FAR 52.245-1 and DFARS 252.245-7005 information. Reports are required to be submitted during DCMA government inspections and Leidos auditing evolutions. All required information is located on ELMS, however, cannot be extracted on one inquiry.
Recommended:
Create ADHOC report under the Inquiries tab to include all information required under the FAR/DFAR instructions for dates indicated. Second option would be to add missing Columns Fields under Inquiries>Inventory activity. Column Fields required for report: Item Desc, NSN, Part Nbr, Model Nbr, Serial Nbr, Qty Rcd, Qty Iss, On Hand Qty, Stock UI, CAGE Cd, Location, Disposition, Document Nbr, In Service Dt, Cond Cd, Unit Price.
Mission Critical:
FAR 52.245-1
DFARS 252.245-7005
Benefits:
This change would allow agency and other users to provide required documentation to auditors/inspectors without manually inputting required information for property accountability.
Frequency:
Quarterly
Users:
Number of Users would be for all who manage government owned Operating Materials and Supplies OM&S.
|
|
02253
|
Set ALL FMC button with date/time
|
MU |
USAF - VSCOS |
New |
Change Request:
Process Improvement
Description: ELMS M&U Module Work Order does not have a "Set ALL FMC" button with Data/Time selection for all sub work orders.
Warfighters waste time navigating into each sub work order adjusting FMC status for a high percentage of work orders.
Recommended:
Add "Set ALL FMC" button with Data/Time selection to main Work Order Page next to MC Status.
Allows warfighters to set ALL sub work orders to FMC with same date/time set on main Work Order streamlining system to execute missions.
Mission Critical:
DAFI24-302 23 JANUARY 2026
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
|
|
02252
|
DF-VEHS site view for all HD tickets
|
PA |
USAF - VSCOS |
New |
Change Request:
New Role Design
Description:
Site managers cannot view all DF-VEHS Helpdesk tickets within Property Accountability Module.
Recommended:
Allow DF-VEHS site level view of all ELMS Helpdesk tickets regardless of who submitted ticket. Develop "New role" at site level to view all Helpdesk tickets allowing responsible office access to critical information
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
|
|
02251
|
DLA Fuel Report API
|
MU |
USAF - VSCOS |
New |
Change Request:
Process Improvement
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.
Recommended:
- Establish an API from DLA Energy to ELMS. Transfer the following data daily: Asset ID, Fuel quantity, fuel type/product code, transaction date, customer state, and unit cost
- Function must have a validation tool/process to eliminate duplicate transactions using the same Asset ID, Transaction Date, and Fuel Quantity
- Function musty have an error report for any transactions that did not properly process
Mission Critical:
DAFI 24-302
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
|
|
02250
|
Warehouse Stock Number Catalog Search Fields
|
Warehouse |
USAF - VSCOS |
New |
Change Request:
Process Improvement
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.
Recommended:
Add manufacture part number and Cage code to Stock Number Catalog search criteria. Match Stock Number Catalog search (Catalog Mgmt > Stock Nbr) criteria and Inquires Stock Number Inquiries (Inquires > Stock Nbr Inquiry).
Mission Critical:
DAFI24-302 23 JANUARY 2026
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
|
|
02249
|
Stock Number Update Enhancements
|
PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW) |
Leidos |
New |
Change Request:
Process Improvement
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.
Recommended:
ELMS will allow edits to the described fields. Because these updates may update inventory in the system the update to these fields will be delayed. The user will be prompted that their update has been queued for overnight processing. An un-alignment from an external source to local management will be applied immediately and allow edits to fields formerly disabled due to its association to an external feed.
Benefits:
Improved catalog management flexibility for the end-user and an overall reduction of data script / help ticket requests
Frequency:
Weekly
Users:
N/A
|
|
02248
|
Transfer Sub Work Orders between MA & MP
|
MU |
USAF - FH-AFHAF |
New |
Change Request:
Process Improvement
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.
Recommended:
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:
PAD 22-02 signed by the Chief of Staff of the Air Force (CSAF) directs the centralized management of CAvSE at the enterprise level, residing within the 440 SCOS Aviation Support Equipment Management Flight. This change will allow for future data mining actions, ensuring equipment accuracy.
Benefits:
This will enable the Air Force to achieve the desired effects in improving overall readiness and war-fighter support.
Frequency:
Daily
Users:
This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that conduct maintenance on their support equipment.
|
|
02247
|
Maint Asset Inquiry Additional Search Criteria
|
MU |
USAF - FH-AFHAF |
New |
Change Request:
Process Improvement
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.
Recommended:
Add Maintenance Program, Maintenance Group Id, and Custodian Number as search criteria under the Maintenance Asset Inquiry extract.
Mission Critical:
PAD 22-02 signed by the Chief of Staff of the Air Force (CSAF) directs the centralized management of CAvSE at the enterprise level, residing within the 440 SCOS Aviation Support Equipment Management Flight. This change will allow for future data mining actions, ensuring equipment accuracy.
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
Users:
This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that conduct maintenance on their support equipment.
|
|
02246
|
"X", "/" & "-" Symbol Use
|
MU |
USAF - FH-AFHAF |
New |
Change Request:
Policy / Regulatory
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.
Recommended:
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:
DAFI 21-101, AFTO 00-20-1
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
Users: Approximately 12K ELMS M&U users and maintenance personnel utilizing equipment within the AvSE functional community will be affected. The total number of work orders/transactions is dynamic (open/closing work orders).
|
|
02245
|
MRO Pending Allocation
|
Materiel Management |
NSWC |
New |
Change Request:
New System Process
Description: When you process a Customer Requisition that comes into the ICP during the RSA selection process, you are only given the available quantity. Users are unable to determine if previous MRO's have been sent over for the same stock number and for the same RSA to determine if there will be enough available quantity to fill that customer requisition.
Recommended:
Provide an additional column in the RSA selection process that would include something called "Pending Allocation" for example. This quantity would be provided from the total "Expected Qty" located in the MRO grid of that RSA for that stock number.
Benefits:
This implementation will streamline a process where the user currently has to go back over to the WH module, review their MRO results grid, query a stock number and add up the expected quantity already sent over to be filled. Then either refer to their inventory in the WH or got back to the ICP, into the customer requisition. select the RSA once again to see what the available quantity is. This new data field would allow the user to make the determination whether to have a warehouse fill the requisition or refer it off station immediately.
Frequency:
Hourly
Users:
All ICP Users |
|
|
Disclaimer | Accessibility