|
02318
|
Sub Work Order Status and Reason Codes
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
User sees a large volume of sub work order status and reason codes that do not apply to the user processes
Recommended:
Allow Maintenance Program specific sub work order status and reason codes
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02317
|
Automate Cycle Counting
|
PA |
AF: A4/HAF FH-AFHAF |
New |
Change Request:
Process Improvement
Description:
See attached "Description of Problem & Proposed Improvement"
Recommended:
See attached "ELMS DAF SCI Physical Inventory FY27Q1 Requirement (Revision 1) 2026 May 29" for solution provided by ELMS Program Manager, Mr. Joseph Stossel
Mission Critical:
Air Force Portfolio Board directed the SCI transformation effort performed within ELMS for
this requirement be implemented. This request is in line with the vision detailed in the
attached Tab 1 22 July 2025_A4 Portfolio Board Meeting Minutes, Section I, Minute Marker 1:19:26.
Benefits:
The transformed Cycle Counting process will increase inventory control and accuracy of AF Accountable Equip items. The process will improve
Supply Chain reliability by eliminating manual scheduling and execution of mandated cycle counts. The transformation will identify and
eliminate sources of inventory inaccuracy by maximizing resources--reducing inventory prep man-hrs and root cause analysis activities.
Frequency: Daily
Users: See attached "ELMS DAF SCI Physical Inventory FY27Q1 Requirement (Revision 1) 2026 May 29" for number of Users
|
|
02316
|
Mark For Implementation
|
PA,Warehouse,Materiel Management |
Leidos |
New |
Change Request:
Policy / Regulatory
Description:
ELMS does not currently fully support the DLMS Mark-for Party when generating, modifying, or processing requisitions. Without full Mark-for support, ELMS may not consistently identify the intended end recipient within the ship-to location. This can create gaps in requisition processing, delivery routing, shipment documentation, supply and shipment status visibility, and downstream receipt processing.
Recommended:
ELMS should implement end-to-end support for the DLMS Mark-for Party across the requisition lifecycle. The solution should capture, validate, store, display, and perpetuate Mark-for information when it is provided, ensuring it remains separate from the ship-to address while identifying the intended recipient or destination within the ship-to location. This support should include applicable DLMS transactions such as 511R, 511M, 869F, 869A, 870S, 856S, 940R, 945A, and 527D where required. The full Mark For should also be included in the printing of the DD Form 1348.
Mission Critical:
Ensures ELMS is compliant with DOW policy.
Benefits: Supports Mark For which is required for shipping sensitive items.
Frequency: Daily
Users: All users who use the Mark For
|
|
02315
|
Tracking Batch/Lot Quantities
|
Materiel Management |
Leidos |
New |
Change Request:
Process Improvement
Description:
Materiel Management does not track inventory quantities by Batch/Lot well. This makes it difficult to determine how much bulk inventory exists within a specific Batch/Lot and limits visibility when inventory must be managed, researched, or reported at that level.
Recommended:
ELMS should move the Batch/Lot number to the same tier level as Owner, Stock Nbr, Project Cd, Purpose Cd, Condition Cd, and Bin Location within its Materiel Management application. This will enable ELMS to accurately account for inventory within each Batch/Lot.
Mission Critical:
Improves the way in which ELMS manages bulk Items that are associated with a Batch/Lot Number
Benefits: Resolves discrepancies with reporting inventory by Batch / Lot.
Frequency: Daily
Users: All users of Materiel Mgmt.
|
|
02314
|
Work Order Parts Location
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
Current M&U system does not allow for temporary storage location of parts associated to a Job Order. Parts are expensed on issue from Warehouse to M&U without visibility of Parts on Hand in M&U.
Recommended:
Create a Job Order location when a Job Order requiring parts is opened in M&U. Parts issued from Warehouse against a Maintenance request will be received in M&U in a Job Order location/bin. The Job Order parts location can not be closed out until the parts are consumed in support of the work order.
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02313
|
Software Configuration Record
|
MU,Warehouse |
SOCOM |
New |
Change Request:
Process Improvement
Description:
Current process does not allow for recording or view of software configurations installed on assets and parts. Users require ability to view current versions of software configurations unique to each asset
Recommended:
Add a MAM attribute for software configurations. Include fields for System Title, Version, Version Date, Date Installed, Installed By, Remarks. Attribute data must be updated via Work Order and data needs to be accessible in M&U and Warehouse.
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02312
|
SKO Configuration
|
MU,Warehouse |
SOCOM |
New |
Change Request:
Process Improvement
Description:
Require SKO Configuration Tabs in Warehouse Module to accommodate multiple configurations of the same stock number.
Recommended:
Add Configuration Tabs to the SKO Catalog Edit Page Components Panel. Each tab will allow variations of the same Kit. Require ability to set the configurations through Work Order in M&U and SKO Update process.
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
Cancelled 6/22/2026 - per email submitted by Reed, Randall This SCR is the same as SCR 02040 |
|
02311
|
Permanent Record At Asset Level for TCTO/Service Bulletins
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
TCTO and Service Bulletins are currently only tracked at Work Order Level. Not viewable in Warehouse.
Recommended:
Record completed work order TCTO/Service Bulletins as an asset record portable with the asset viewable in all Modules where asset resides. Recommend a panel in MAM and in inquires and Inventory Update Manager in Warehouse
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02310
|
Maintenance Schedule at Stock Number Level
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
Currently can only add individual assets to Maintenance Schedule
Recommended:
Need ability to add a Stock Number to the Maintenance Schedule so assets will automatically have the schedule added when profiled in maintenance.
Benefits: Insures that all required schedules are assigned to assets, eliminating input errors.
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02309
|
Maintenance History
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
Current process does not allow for passing maintenance history of an asset across Maintenance Activities
Recommended:
Adjust the work order in Maintenance Journal Inquiries to show all history regardless of Maintenance Activity.
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
Cancelled 6/22/2026 - per email submitted by Reed, Randall This SCR is covered by SCRs 01877, 01205 and 00928
|
|
02308
|
Labor Hours from Tasks
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
Current process tracks Tasks time performance separately from Labor time performance data.
Recommended:
Add option at Maintenance Activity Level to toggle on Labor entry rolled up from Task Completion times and utilize the Team Member assigned for the labor entry which will be saved/edited on work order save. Enforce task labor entry. Allow manual labor entry if a sub work order has no tasks.
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02307
|
Enforce Labor Entry on Work Order
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
Current process does not enforce requirement to enter Labor Data on Work order.
Recommended:
Create a toggle option at the Maintenance Activity to enforce the mandatory use of Labor Data/Hours on work order close process.
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02306
|
Maintenance Technician III Role
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
NSW and USSOCOM new a role Maintenance Technician III - propose modification of Maint Tech I Role - make approval date on Work Order read only on add. Add ability to requisition parts, lock sub-work tasks with exception of actual result and actual hours. Add ability to add Labor entries.
Recommended:
Creation of new Role - Maintenance Technician III
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02305
|
Maintenance Director with Attributes Role
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
M&U users require ability to modify Attributes in M&U Catalog without ability to change the Catalog.
Recommended:
Create a new Role - Maintenance Director with Attributes Role. Use the existing Maintenance Director Role ELMS 8005 granting Maintenance Director with Attributes Role access to the Catalog Menu, Catalog Sub Menu WPMAN51 Maintenance Attribute Management with add/edit/delete rights.
Benefits: This change provides M&U users the ability to manage the maintenance attributes of an asset in M&U without making changes to the master catalog record. This benefits organizations that centrally manage catalogs.
Frequency: Daily
Users:
This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels. |
|
02304
|
Configuration Fields in MAM
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
M&U Configurations should be read only in the MAM, the configurations should only be editable in the Work Order process.
Recommended:
Lock the fields for configurations in the MAM making them read only. Add the configuration update process to Work Orders
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02303
|
Display Asset Condition Code in MAM
|
MU |
SOCOM |
New |
Change Request:
Process Improvement
Description:
Current MAM data does not display Condition Code of Asset
Recommended:
Display Condition Code of the Asset in the MAM.
Benefits: Implementing this solution meets the mission needs of NSW
Frequency: Daily
Users: This change will allow Naval Special Warfare and USSOCOM to implement M&U across the commands at all levels.
|
|
02302
|
ELMS to GAFS-R OM&S Interface - Add Condition Code
|
|
Leidos |
New |
Change Request:
Process Improvement
Description:
The ELMS / GAFS-R OM&S interface does not currently include the condition code in its reporting to GAFS-R. The current mapping has the field left blank. The proposed improvement is to add the Condition Cd to the ELMS / GAFS-R interface.
Recommended:
The current ELMS to GAFS-R interface layout contains the condition code field which today is listed as "blank". In order to ensure correct posting of OM&S within GAFS-R there is a requirement to include the Condition Cd within the interface. See attachment for OM&S USSGL to Condition Code logic.
Mission Critical:
Modifies the methodology for General Ledger posting of OM&S.
Benefits: Enables use of the Condition Code to determine General Ledger posting of OM&S which limits the number of Bid Numbers required to support the interface.
Frequency: Daily
Users: This change impacts users of the GAFS-R Operating Materials and Supplies (OM&S) interface which is primarily the Air Force C-ICP organizations that have a requirement to report the cost of OM&S
|
|
02301
|
Automated Ingestion of AF- Approved Product Catalogs into ELMS
|
PA |
AF: A4/HAF FH-AFHAF |
New |
Change Request:
New System Process
Description:
ELMS, the DAF's Accountable Property System of Record, inject catalogs from FLIS and AESIP and is critically disconnected from the mandatory IT procurement sources. Official product lists, such as the Client Computing Solutions (CCS-3), Land Mobile Radio (LMR-SE), and Digital Printing & Imaging (DPI) catalogs managed by the 771st ESS, are not integrated into the ELMS catalog. Current Process & Impact:Per DAFMAN 17-1203 and the DAFECO's "Catalog Update Request" guide, when a unit receives a new, officially procured asset, the Equipment Control Officer (ECO) must manually submit a ticket to have the item added to the ELMS catalog if it is not found. This manual process is inefficient, places a significant administrative burden on thousands of ECO's enterprise-wide, and is the direct cause of major data integrity issues. These issues include data entry failures, inaccurate inventory reports, and the proliferation of placeholder data (e.g., assets valued at "$1.00"), which erodes trust in ELMS. Proposed Improvement: This SCR proposes the development of a permanent, automated solution to integrate these disparate systems.
Recommended:
Implement a system change for ELMS to automatically ingest and regularly synchronize with the authoritative Air Force product catalogs (e.g., CCS-3 QEB, RPB, LMRSE).
This will ensure that when assets are procured through mandatory sources, their correct data—Manufacturer, Model, Part Number, CAGE Code, and Price—is
already loaded and available for selection in ELMS. This change would eliminate the current manual workaround and ensure data accuracy from the point of asset
receipt.
Mission Critical:
This change is required to align ELMS with DAFMAN 17-1203, which mandates the use of approved enterprise purchasing programs. Currently, the system of record is disconnected from the very sources the DAF requires units to use, including: Client Computing Solutions (CCS-3) (Mandated by para 2.5.1.4), AF GSA Advantage, Digital Printing and Imaging (DPI), (new) IT Storefront, Land Mobile Radio (LMR-SE). The current manual catalog update process creates a massive functional gap between mandated procurement and mandated accountability. Automating the ingestion of data from these official sources into ELMS is a foundational requirement for maintaining an accurate and reliable APSR, supporting audit readiness, and enabling efficient lifecycle asset management across the enterprise.
Benefits:
1. Ensures Data Integrity and Auditability: Asset data will be correct from the point of entry, providing an accurate audit trail and eliminating placeholder data.
2. Increases Mission Efficiency: Frees thousands of ECOs and property custodians from the current inefficient, manual catalog update process, allowing them to focus on their primary duties.
3. Improves Property Accountability: Enables timely and accurate tracking and reporting of all DAF IT assets, fulfilling a core ITAM program requirement.
4. Strengthens User Trust: Provides a reliable and accurate system of record, increasing user confidence and reducing frustration.
Frequency: Daily
Users: This issue affects all ITAM and Property Accountability personnel across the entire Department of the Air Force, including every Equipment Control Officer (ECO), Property Custodian (PC), and APO at every installation worldwide (thousands of users). This SCR serves as the formal vehicle to get this critical requirement funded and resolved.
|
|
02300
|
Update SOS
|
Warehouse |
NSWC |
New |
Change Request:
Process Improvement
Description:
Source of Supply RIC is Locked / Uneditable when Stock Item Cd is A - NSN and Interface System Cd is CL - FLIS. Requesting a system modification to allow manual updates to the Source of Supply RIC. Disrupted routing for NSN items where SOCOM is the actual source of supply. Additionally, request an interface toggle to enable/disable active FLIS synchronization to prevent automated FLIS updates from overriding custom local SOS RIC configurations.
Recommended:
OCOM acts as the primary Source of Supply for specific NSN stocked items. The system must allow users to configure the SOS RIC to route these requisitions correctly. Automated FLIS overwrites destroy local data integrity. Providing a toggle to disconnect the FLIS interface ensures local configurations remain persistent.
Benefits: Implementing this change will significantly reduce administrative overhead and eliminate requisition routing errors caused by inaccurate Source of Supply data.
Frequency: Hourly
Users: ALL USERS
|
|
02299
|
New Roles for Associated auths and Auth required
|
FSM |
AF: A4/HAF FH-AFHAF |
New |
Change Request:
New System Process
Description:
Currently system does not have roles to accommodate for the new process requirements for authorization association and stock number authorization requirement. Within the DAF Authorization Management at the UIC level is managed in our centralized office and not at the base level. The capability to apply authorizations cannot be included in the Property Admin Role as this gives all users with the Prop Admin role the capability to apply authorizations which will void the segregation of duties outlined by DAF policy. Additionally we require new role to manage stock numbers that require a FSM managed authorizations, the user will not be the same user as the Associated Auth Manager, as they are in different centralized organizations.
Recommended:
Develop two new roles, one to manage stock numbers that require an authorization. Include the AF Budget code for FLIS Managed stock numbers. The second role is for a user to associate authorization to the property records. Both processes will be managed under different centralized organizations. See attached Associated Auth SCR Requirements document for specific details of the requirement.
Mission Critical:
CJCSI 3401-02B Enclosure C DAFMAN 23-300
Benefits: New roles will comply with DAF segregation of duties and roles and responsibilities
Frequency:
Hourly
Users: 150-250 Users will manage ~1.4M auths/~1.2M property records/~1.1M stock numbers
|
|
|