Unlike submitted Support help tickets, System Change Requests (SCR's) can only be submitted through your organization's appointed and authorized ELMS CCB member representatives, or otherwise if no CCB representatives have yet been appointed, your Primary Information Owner appointee. If you are unsure of who your organization's appointed ELMS CCB member representatives or Primary IO are, you may email the ELMS Support team to request that information:
To learn more about the process, please visit our CCB Responsibilities and Meetings page. Below you will find all SCR's that have been submitted, and what their status is. To download a blank form, you may visit our Reference Library and download the SCR Form.
Utilize the search filters below to narrow your results by keywords, module, or state. You may also request an Excel file of all the SCR data by contacting the Help Desk.
| Found: 1779 Result(s) | Show: |
| Title |
ELMS Module |
Reporting Org |
State |
Description |
Action |
|
|---|---|---|---|---|---|---|
| 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
Mission Critical:
N/A
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.
Mission Critical:
N/A
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
Mission Critical:
N/A
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.
Mission Critical:
N/A
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.
Mission Critical:
N/A
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 The user (Escobedo, Emily) would like the requirements in SCR 02326 to replace the requirements in this SCR.
|
|
| 02298 | BLADE data feed update | PA,FSM | AF: A4/HAF FH-AFHAF | New | Change Request:
Process Improvement
Description:
The current BLADE data feed from ELMS will not have the new data elements and will need to be updated once the SCRs are completed to associate authorizations to the property records and identifying stock numbers that require an authorization. The aggregation of some data elements may change the security classification of the data table therefore adherence to the CJCSI 3401.02B must be referred to ensure data is not compromised or spillage does not occur.
Recommended:
Update BLADE data from ELMS when SCR is completed to associate property records to an authorization and identify stock numbers that require an authorization. The data feed needs to be part of feed that is sent every 4 hrs. Data elements include but are not limited to, associated Authorization ID, Platform Name, O.Auth Qty, F. Auth Qty, Multiplier, Unit Associated Authorization Review Date, Authorization Management Auth-Id Date Last Reviewed date, Auth Management Authorization Reviewer, Authorization Change Request tracking number, Excess/Excess In-place date, Overage Qty, Shortage Qty, LIN/TAMCN, System Id, Readiness Code, Due-In Qty, I&S NIIN, Master NSN.
Mission Critical:
OSW and DAF policy require the use of War Data Platform(WDP) to build Logistics Dashboards and reports to provide DAF the capability to make data informed decision based on data housed in APSR
Benefits:
OSW and DAF policy require the use of War Data Platform(WDP) to build Logistics (BLADE) Dashboards and reports to provide DAF the capability to make data informed decision based on data housed in APSR. This will limit the requirement to leverage Dashboard and reports development on ELMS PMO. Frequency:
Hourly
Users:
Data feed required at minimum daily every 4 hrs. All DAF Users ~1.4M auths/~1.2M property records/~1.1M stock numbers |
|
| 02297 | Associate authorization to property records and identify stock numbers that require auth | FSM | AF: A4/HAF FH-AFHAF | New | Change Request:
New System Process
Description:
Currently ELMS lacks the capability to associate a FSM authorization to the property record. Limiting the capability for the DAF to determine readiness capabilities and fill rates to support mission requirements. Additionally, not all stock numbers require an authorization which can cause issue with identifying excess, overages or local unit needs
Recommended:
Establish a new program to associate authorization to an asset that exists outside of the asset Life-cycle process. This new screen needs to have the flexibility to work in the future with authorization management in the warehouse module (DAF SCR 2082). Establish a new program that allows the user to identify stock numbers that require an authorization. This will provide data into the asset associated auth program.
Mission Critical:
CJCSI 3401-02B Enclosure C
DAFMAN 23-300 Benefits:
Provides the DAF the capability to see readiness posture and fill rates to support mission requirements. Provides the capability to identify stock numbers that require an authorization to determine if unit posture is sufficient to execute mission capabilities. Frequency:
Hourly
Users:
Currently ~1.4M authorizations and ~1.2M property records that require Monthly Readiness reporting The user (Escobedo, Emily) would like the requirements in SCR 02327 to replace the requirements in this SCR. |
Disclaimer | Accessibility