System Change Requests Header

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: This email address is being protected from spambots. You need JavaScript enabled to view it..

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.

Enter your SCR Number in the filter below, or click the column title header to sort by that column. You may also download an Excel file of the record data by selecting the blue Excel logo in the upper right corner of this page.

Filter 
SCR Number Title DPAS Module Reporting
Organization 		State Description
02211 DLMS Transaction Gaps Warehouse,Materiel Management USMC New
Change Request: Compliance Requirement 
Description: 
 
Acquire to Retire (Equipment): Planning for Equipment: Planning for Equipment (Material Weakness)
ELMS MM module currently supports only pull-based requisitioning, which prevents Inventory Control Points (ICPs) from proactively distributing materiel based on command direction, readiness requirements, or forecasted operational demand. This absence of a Push Fulfillment (ICP Directed MRO Issue) capability limits the USMC’s ability to preposition assets, re-balance inventory, and execute time-critical resupply actions – especially for MARCORSYSCOM and MARFORRES organizations.
Additionally, ELMS lacks the ability to automatically generate DLMS 527D/DWB Prepositioned Materiel Receipt (PMR) transactions when transferring ownership of assets between Primary Inventory Control Activities (PICAs) or ICPs through a third-party storage or distribution site. The current process requires manual, offline creation of these transactions, resulting in fragmented data flow, inconsistent audit trails, and potential discrepancies in custodial accountability and ownership records.
The combined absence of automated push fulfillment and system-driven 527D/DWB ownership transfer functionality forces reliance on manual workarounds that degrade visibility, increase processing time, and heighten the risk of data mismatches across warehouse, ICP, and financial systems. These deficiencies also impede full DLMS compliance, complicate reconciliation between issuing and gaining activities, and introduce audit vulnerabilities within FIAR and ELMS-aligned accountability frameworks.
Implementing an integrated ICP Directed MRO Issue process within ELMS—complete with automated generation of 940R, 945A, 856S, 870S, and 527D/DWB transactions—will ensure accurate, DLMS-compliant execution of directed shipments, ownership transfers, and audit-ready traceability. The absence of a system-driven, DLMS-compliant “ICP Directed MRO Issue” process introduces a significant materiel weakness. Manual workarounds—such as ad hoc issue documentation, offline tracking, or non-standard DLMS transactions—degrade audit compliance and complicate reconciliation between ICP, warehouse, and accounting systems. Additionally, the inability to incorporate serialized tracking, third-party consignee shipments, or automated PMR (527D/DWB) generation further constrains the Marine Corps’ ability to support distributed maritime and expeditionary operations.
 
 
Recommended: 
 
README: The following nine attachments are embedded within the GAP-109 Push Fulfillment (ICP Directed MRO Issue) BRD package to provide the complete set of supporting technical, functional, and design requirements required for implementation. Collectively, these attachments document the end-to-end process flow, user interface design, DLMS XML transaction mappings, and detailed requirements specifications for all five modified DLMS messages (940R, 527D, 945A, 856S, and 870S). Their inclusion ensures that ELMS developers, testers, and stakeholders possess authoritative references linking the business process to the technical configuration, thereby enabling DLMS-compliant system development, audit-ready validation, and seamless integration of the new Push Fulfillment capability within the Materiel Management (MM) module.
 
1 – GAP109_ELMS_Push_Fulfillment_Requirements_RTM_20251008.xlsx
 
This Excel workbook serves as the master Requirements Traceability Matrix (RTM) for the Push Fulfillment capability. It consolidates all functional and non-functional “shall” statements generated for GAP-109, cross-referencing each requirement to DLMS standards, transaction sets, and validation criteria. The file ensures end-to-end traceability from BRD objectives to development and test cases within ELMS MM.
 
1a – GAP 109_BRD_ELMS_USMC_MARCORLOGCOM_1.b ICP DIRECT MRO ISSUE Process Flow_v2.0 (20251006)
 
This process flow illustrates the end-to-end ICP Directed MRO Issue workflow within the ELMS Materiel Management (MM) module, depicting user roles, decision logic, validations, and DLMS transaction triggers (940R, 527D, 945A). It provides system developers and testers a visual baseline for how “Push Fulfillment” actions move from MRO creation through warehouse release and transaction generation. Included to serve as the primary business-process reference for implementing, testing, and verifying GAP-109 functionality
 
1b – GAP 109_BRD_ELMS_USMC_MARCORLOGCOM_1.b ICP DIRECTED MRO ISSUE Screen Layout (20251006)
 
This attachment presents the user-interface design and required input fields for the new “ICP Directed MRO Issue” entry screen, including header, body, and inventory-selection components with DoDAAC, RIC, PMR, TAC, and serial-number data entry rules. It provides developers with a precise UI blueprint and control-validation guide ensuring compliance with DoDAAF standards and proper capture of all requisition data elements during push fulfillment.
 
2 – GAP 109_BRD_ELMS_USMC_MARCORLOGCOM_1.b ICP DIRECTED MRO ISSUE _XML Transactions Mapping_v2 (20251009).xlsx
This multi-tab mapping workbook defines the DLMS XML schema field mapping for the five modified transactions (940R, 527D, 945A, 856S, 870S). Highlighted tan cells indicate missing segments to be added; red cells flag non-compliant elements requiring removal or correction. It is included to guide developers in achieving full DLMS Interface Convention alignment for each ELMS interface.
 
3 – GAP109_Push_Fulfillment_DLMS_XML_940R_Requirements_20251009v3.pdf
Specifies requirements for the DLMS 940R (Warehouse Shipping Order) message that initiates push-fulfillment actions from the ICP to RSAs or third-party consignees. It details data fields, validation logic, and message structure needed to automate directed materiel releases and ensure schema compliance with DLMS IC 940R.
 
4 – GAP109_Push_Fulfillment_DLMS_XML_527D_Requirements_20251009v1.pdf
Documents requirements for the DLMS 527D/DWB (Prepositioned Materiel Receipt) are used to record ownership transfer between PICAs/ICPs via third-party storage sites. It defines triggers, mandatory data elements, and audit-logging requirements replacing the current manual PMR process, ensuring automated, FIAR-compliant custody updates.
 
5 – GAP109_Push_Fulfillment_DLMS_XML_945A_Requirements_20251009v1.pdf
Outlines requirements for the DLMS 945A (Warehouse Shipping Advice) transaction confirming fulfillment of directed MROs. It captures shipment quantities, serial details, and consignee data, linking back to originating 940R orders. Included to formalize message generation and closure logic supporting audit-ready shipment verification.
 
6 – GAP109_Push_Fulfillment_DLMS_XML_856S_Requirements_20251009v1.pdf
Defines requirements for the DLMS 856S (Advance Ship Notice / Manifest) message used to communicate detailed shipment information—carrier, packaging, and serialized item content—to receiving and third-party sites. This file ensures ELMS can provide standardized, real-time shipment visibility aligned with DLMS IC 856S.
 
7 – GAP109_Push_Fulfillment_DLMS_XML_870S_Requirements_20251009v1.pdf
Describes the DLMS 870S (Supply Status) message requirements used to transmit real-time status updates throughout the push-fulfillment lifecycle. It specifies event codes, routing, and validation rules that synchronize ICP, RSA, and consignee systems, closing the DLMS transaction chain with complete audit traceability.
 
Mission Critical: 
ELMS is not currently fully compliant with DLMS transactional policy
 
 
Benefits: 
 
- Meets MARCORLOGCOM’s business model
- Assists in 100% accountability of assets.
- Complies with current audit controls.
 
 
Frequency: Daily
 
 
Users: 
- Material Managers
- ICP
02210 LESO - Identify Nbr of asset photos Warehouse LESO New
Change Request: Process Improvement
Description: 
 
ELMS provides for attachments by the user community, but it does not identify the number of photos that should be captured and attached to the item.  DLA LESO's policy requires law enforcement agencies that acquire excess DoD property to capture and attached x photos to the item's record based upon the type of item it is.  ELMS needs a method to identify the number of photos and provide that information to the user during Receiving and Updates of the item. The DLA LESO's agencies will utilize the warehouse management application for their property control record.
 
 
Recommended: 
DLA LESO is requesting: 1) ELMS provide the capability to identify the number of photos required to be captured for the item in inventory.  Possibly at the Stock Nbr or Commodity Type level. 2) Advise the user of the number of photos required during the receiving process. 3) Provide a method for validating the the photos are of the asset.
 
 
Mission Critical: 
Improvement for managing assets.
 
 
Benefits: 
 
This change enables law enforcement agencies to comply with DLA LESO regulations and provide the DLA LESO a method for validating that the agencies are complying with the regulation.
 
 
Frequency: Daily
 
 
Users: The primary users of this capability would be DLA LESO, USMC, and NSWC at this time.
02209 Law Enforcement Office Self Certification Phase 2 Warehouse LESO New
Change Request: New System Process
Description: 
DLA LESO submitted a SCR titled "LESO - Law Enforcement Office Self Certification" that described the the requirements that each Law Enforcement Office must perform as part of their annual certification.  That SCR did not request ELMS provide the capability to create / store the from used to perform the annual certification.
 
 
Recommended: 
   This SCR is requesting ELMS to provide the following: – Create a process that provides each law enforcement office "Station" the capability to download the application form, upload completed form and to provide workflow routing of the certification to the required LESO offices for review and signature. Once the last signoff is received as approved, ELMS will update the status of the Station to approved for the next period of performance E.G. (1 Year).  A view should be available to DLA LESO (Logistics Program) of the status of each law enforcement office identified by State (Region), County/City (SIte).
 
 
Mission Critical: 
This is a new requirement that provides for the review and tracking of stations (Warehouse) as to their certification to operate, for how long and when their next certification is due.
 
 
Benefits: 
This change enables law enforcement agencies to comply with DLA LESO regulations and provide the DLA LESO a method for validating that the agencies are complying with the regulation.
 
 
Frequency: Yearly
 
 
Users: The primary users of this capability would be DLA LESO.
02208 DLA LESO Program Compliance Review (PCR) Process Warehouse,Materiel Management LESO New
Change Request: New System Process
Description: 
DLA LESO has a Program Compliance Review "PCR" where they biannually review / validate each station's (ELMS Warehouse) for compliance to stated regulations.  This process validates the station is in compliance and can continue with the program should they indicate that they wish to.  ELMS does not have a defined process to support this.
 
 
Recommended: 
  This SCR is requesting ELMS to provide DLA LESO with a PCR process.  The process will provide DLA LESO with a list of stations, when they were last reviewed, their current status and when their next PCR is due to be completed.  Be able to attach planned and actual reuslts as well as provide the status of the review (Complete, Reviewed/Pending finalization/Planning, etc).,  The process must also show the proximity of each station in order to group stations into an audit group.  See attached for specifics.
 
 
Mission Critical: 
This change will provide a Program Compliance Review "PCR" process for DLA LESO personnel. The goal should be to design the process to support all ELMS users that conduct compliance reviews.  
 
 
Benefits: 
This change will provide DLA LESO and other ELMS the capability to manage compliance reviews using ELMS.  This change will enable ELMS users to track warehouse reviews planned, determine the scope of the PRC and track when it was conducted and the results of the review.  
 
 
Frequency: Weekly
 
 
Users: The primary users of this capability will initially be DLA LESO PCR personnel.
02207 DLA LESO Program Compliance Review (PCR) Process - Phase 2 Warehouse,Materiel Management LESO New
Change Request: New System Process
Description: 
DLA LESO has submitted a Program Compliance Review "PCR" SCR to provide processes to support the compliance review process. This SCR requests ELMS to automate the generation of the PCR document where the PCR criteria is configurable and customizable.
 
 
Recommended: 
 Automate the generation of the PCR to the state for each PCR to be conducted.
 
 
Mission Critical: 
This change will automate the Program Compliance Review "PCR" process form. The goal should be to design the process to support all ELMS users that conduct compliance reviews.    
 
 
Benefits: 
This change will provide DLA LESO and other ELMS the capability to manage compliance reviews using ELMS.  This change will enable reduce the effort required to notify and route planned PCR reviews.
 
 
Frequency: Weekly
 
 
Users: The primary users of this capability will initially be DLA LESO PCR personnel.
02206 LESO - Law Enforcement Office Self Certification Warehouse LESO New
Change Request: Process Improvement
Description: 
ELMS provides its warehouse mgmt. application users with a Physical Inventory (PI) process - manual and using AIT. The ELMS PI processes were designed to support the continuous conducting of physical inventories as a warehouse operation would operate.  WIth DLA LESO planning to have its civil law enforcement agencies utilize the ELMS warehouse mgmt application to track issued DLA property in their possession, LESO is requesting ELMS provide for a compliance report to be submitted by each law enforcement organization through its county/city (Site) to the State (Region) to DLA LESO (Logistics Program) that detail their physical inventory results and other self certifications that must be made.
 
Recommended: 
 The attachment details the specific items the annual certification must check / confirm.  This list is subject to change and should be configurable.  Upon completion of the annual certification process, the system should be able to produce a report of items that have had a physical inventory conducted in the past year and identify those items that were not observed in the reporting period.
 
Mission Critical: 
Improvement for managing assets.  While several of the requirements may be specific to DLA LESO, ELMS should review the requirements and determine how they might be adaptable to the greater ELMS Customer Base.
 
 
Benefits: 
This change enables law enforcement agencies to comply with DLA LESO regulations and provide the DLA LESO a method for validating that the agencies are complying with the regulation.
 
 
Frequency: Yearly
 
Users: The primary users of this capability would be DLA LESO.
02205 Automate Supply Discrepancy Reporting with Receiving Functions PA,Warehouse,Materiel Management LESO New
Change Request: New System Process
Description: 
ELMS currently provides for the identification of a Supply Discrepancy (SD) within the Warehouse Receiving process.  It does not provide a dashboard of open discrepancies to enable management, nor does it transmit a Supply Discrepancy Report (SDR) to WebSDR.  Today, users must login to the WebSDR to report supply discrepancies.
 
Recommended: 
 DLA LESO is requesting: 1) ELMS provide for electronic reporting of SDRs to the Source of Supply via DLMS transactions (DLMS 842 A/W) and source of supply responses via DLMS 842 A/R), 2) Dashboard to display open Supply Discrepancies reported, Supply Discrepancy Responses, and action taken to close the SDRs.  
 
Mission Critical: 
Improvement for the management Supply Discrepancies.
Automates the reporting of Supply Discrepancies.
 
 
Benefits: 
This change improves how SDRs are managed within ELMS.  For organizations that utilize this capability, it will eliminate their use of WebSDR.
 
Frequency: Daily
 
Users: 

The primary users of this capability would be DLA LESO, USMC, and NSWC at this time.
02204 Improvements to 832N Processing Materiel Management USAF: GFM-A New
Change Request: Process Improvement
Description: 
DAF CICPs send 832N transactions to ELMS to establish new stock numbers and update existing stock numbers.  ELMS requires an existing stock number before processing any inventory affecting transactions.  The DAF has been experiencing a large volume of suspended inventory affecting DLMS transactions in the ICP module; many of these can be traced back to a suspended 832N transaction.  DAF offers recommendations to improve the processing of 832Ns that will ultimately lead to a reduction in suspended transactions.
 
Recommended: 
Recommend that ELMS ICP module implement the attached improvements to 832N processing.  These involve inserting the default values or FLIS data in order to process the 832N transaction.
 
Mission Critical: 
The improvements proposed for the DLMS 832N should also be considered for incorporation into the FLIS and Agency Catalog interfaces if they are not present. .
 
Benefits: 
The improvements to 832N processing will reduce the number of suspended transactions and reduce the amount of time the DAF and its CICPs spend on suspended transactions.  
 
Frequency: Daily
 
Users: This requirement improves the processing of 832N transactions for the 100+ DAF CICPs
02203 Interface with FAMIS PA FH-AFHAF New
Change Request: Process Improvement

Description:
The United States Space Force (USSF) has established a new Working Capital Fund that will be using the existing FAMIS solution for their FY26 accounting operations. They will be using the PA module of ELMS and require a monthly interface file to be sent from ELMS to FAMIS. The new monthly interface file for USSF should be created and extracted/sent to FAMIS.
 
Recommended:
Create new interface file to extract to FAMIS for USSF transactions.
 
Mission Critical:

 
Benefits:
Automated solution for USSF to post accounting transactions in FAMIS

Frequency: 
Monthly

Users:
ELMS currently already has an interface to FAMIS for the DISA Site-id, DISA is transferring program to USSF.
02202 Maint Asset & Asset Preventive Maint Schedule Inquiry fields MU VSCOS New
Change Request: Process Improvement

Description:
The Maintenance Asset Inquiry and Asset Preventative Maintenance Schedule Inquiry provides useful data but lacks critical information identifying requirements.  Therefore, we propose adding the following to Maintenance Asset Inquiry and Asset Preventative Maintenance Schedule Inquiry selection fields:
1. Established by
2. Established date
3. Last updated by
4. Last updated date
 
Recommended:
Add the following selection fields to Maintenance Asset Inquiry and Asset Preventative Maintenance Schedule Inquiry
1. Established by
2. Established date
3. Last updated by4. Last updated date
 
Mission Critical:
AFI 24-302 VEHICLE MANAGEMENT
 
Benefits:
Ability to clearly identify who and when Maintenance Asset and Asset Preventative Maintenance Schedule established and/or updated aiding troubleshooting.  This system change will allow ELMS users to provide in-depth research to programmers aiding determination if an error is user established/updated, system established/updated or a potential system bug.

Frequency: 
Daily

Users: This process improvement benefits DOD agencies on a daily basis.
02201 ELMS CCB Member Tracking Tool Leidos New
Change Request: New System Process

Description:
The ELMS program office currently maintains the list of CCB members in MS Word. The review / list has been subject to review as part of the SSAE 18 audit of ELMS. The proposed improvement is to manage the list within ELMS allowing it to have checks and balances to the list of Department / Agencies using ELMS and to provide a history of the changes to the CCB member list. The create / update / delete must be role based and available to the ELMS admin staff.    
 
Recommended:
1. Provide a CRUD process that will enable the establishment / maintenance of  a CCB member.
2. Provide the capability to associate the CCB member to a Department, Agency, and to agency programs they support (Optional).
3. Link a CCB member to an ELMS users when they are a user of ELMS allowing for the sharing of email., phone number, etc. .
4. Provide search capability to identify agencies and/or agency programs that are not supported by a CCB Member.
5. Provide an inquiry  / report of CCB Members by Department / Agency / Program.

6. Provide a view to the ELMS user of their CCB Member(s) / contact info.

 
Mission Critical:
Improvement in the management of the CCB Member list (supports SSAE 18 Audit)
 
Benefits:
Improves the maintenance of the CCB list for audit.  Provides the ELMS user with their CCB member(s) should they need to contract them.

Frequency: 
Daily

Users: 
This change when implemented will impact all ELMS users (currently 30K+) along with the ELMS program management staff.
02200 Stock Item Import Function Warehouse VSCOS New
Change Request: Process Improvement

Description:
The warehouse module Stock Item catalog lacks a user stock number import function similar to the new excel SKO catalog import.  The current manual process requires many hours for inputting thousands of stock numbers into Stock Item catalog.  DF-VEHS validates and submits multiple files for Program Management Office (PMO) validation and upload into production.  Incorporating the new excel SKO catalog import function within Stock Item catalog for stock numbers will streamline PMO and site-level user's workloads.
 
Recommended:
Incorporate the new excel SKO catalog import function within Stock Item catalog for stock numbers.  Recommend including stock number, DODACC, and Inventory Segment ID.  The process needs the ability to identify errors (e.g., No stock number created) or a similar function.
 
Mission Critical:
DAFI 24-302 VEHICLE MANAGEMENT
 
Benefits:
Streamlines stock number load processes for the PMO and site-level user's workloads.

Frequency: 
Hourly

Users: 
This process improvement benefits DOD agencies on a daily basis
02199 Message of the Day Temp Loan Additions Warehouse VSCOS New
Change Request: Process Improvement

Description:
The 'Message Of The Day' (MOD) tab is a powerful tool to assist managing many warehouse functions.  However, the Individual Temp Loans within MOD screen does not display Stock Number, Item Description, and Serial Number of an item.  This prevents the WH users from clearly identifying items issued.  The MOD's other options (e.g., Inspection, QC, etc.) display Stock Number, Item Description, and Serial Number and we believe this is an oversight for individual Temp Loans.   Therefore, propose adding Stock Number, Item Description, and Serial Number to Details page under MOD Individual Temp Loans.  
 
Recommended:
Add Stock Number, Item Description, and Serial Number to MOD Details page under Individual Temp Loans similar to other options (i.e., Inspection, QC, etc).  See Message of the Day attachment
 
Mission Critical:
DAFI 24-302 VEHICLE MANAGEMENT
 
Benefits:
1) Allows quick recognition for items issued to members
2) Saves time returning items issued to members
3) Streamlines item issued processes with ability to easily identify by Stock Number, Item Description, and Serial Number

Frequency: 
Hourly

Users: 
This process improvement benefits DOD agencies on a daily basis
02198 Add ZONE to search WM inventory Warehouse VSCOS New
Change Request: Process Improvement

Description:
The warehouse module provides a useful search function, however, ZONE is not part of the current Warehouse Management tier search tool.  Propose adding ZONE search function throughout warehouse module to improve accountability and management of inventory.
 
Recommended:
1. Add ZONE to Inventory Update Manager Search Criteria
2. Add ZONE to Inventory Update Manager Grid Options > Columns
3. Add ZONE to Inspections Grid Options > Columns
4. Add ZONE to ICN Inventory Search Criteria
5. Add ZONE to ICN Inventory Grid Options > Columns
 
Mission Critical:
DAFI 24-302 VEHICLE MANAGEMENT
 
Benefits:
Streamline identification and management of inventory via ZONE.  This enhances capabilities providing definitive search results between large, medium and small areas versus limiting this powerful function.

Frequency: 
Hourly

Users: 
This process improvement benefits DOD agencies on a daily basis.
02197 Add Column to ELMS 244 MU VSCOS New
Change Request: Policy / Regulatory

Description:
The ELMS 244 does not include “due by utilization” column.  Assets are due by date and/or utilization.  Include “due by utilization” column on ELMS 244.
 
Recommended:
Add “due by utilization” column to ELMS 244
 
Mission Critical:
DAFI63-125_AFGSCSUP_AFGSCGM2025-01 ATTACHMENT 1 Guidance Changes: 2.10.7.4.5. (AFGSC) When an NCE work center monitor does not have access to the maintenance information system (MIS) of the supporting agency responsible for recurring maintenance on NCE assets (e.g.., vehicles and equipment), the supporting agency must provide a list of all completed preventative maintenance and inspection (PM&I) actions. The purpose of this maintenance record is for the NCE users to be able to verify all PM&I actions are up to date (no PM&I actions are overdue) prior to use. This can be done by providing a printout from the MIS [such as the Enterprise Logistics Management System (ELMS) 244]], an AF Form 1800, or a memorandum for record. (T-3) Records (physically or digitally) must be kept for three years to ensure the required maintenance is being performed on a routine basis.
 
Benefits:
Incorporate the different "due by" information within the ELMS 244 documentation

Frequency: 
Hourly

Users: 
This process improvement benefits DOD agencies on a daily basis.
02196 Gear Size Tracking Enhancements Warehouse USMC New
Change Request: Process Improvement

Description:
 
Single "Size" Field Without DifferentiationGap: Conflation of actual fitted size and issued size.Impact: Prevents accurate analysis of gear fitment and effectiveness of the sizing process.Business Risk: Leads to inaccurate forecasting, increased returns, and unnecessary reorders—resulting in higher costs and reduced Marine satisfaction. This field is in Advana interface.
 
Recommended:

1. Gear Size Tracking EnhancementsRequirement ID: ELMS-REQ-003a

Requirement:ELMS shall include a new field labeled “Actual Size” to record the size determined through physical fitting or self-assessment at the time of gear allocation.Requirement ID: ELMS-REQ-003bRequirement:
 
ELMS shall retain or create a separate field labeled “Issued Size” to capture the actual gear size provided to the Marine, regardless of fitting outcome.
 
2. Data Export Schema UpdatesRequirement ID: ELMS-REQ-004Requirement:
 
ELMS shall include the Actual Size, and Issued Size fields in all relevant data exports and reports to support downstream analysis and performance audits.
 
3. Analytical Reporting CapabilityRequirement ID: ELMS-REQ-005Requirement:
 
ELMS shall support reporting functions that display gear issuance and destruction trends by EDIPI and UIC, and highlight discrepancies between Actual Size and Issued Size to enable gear fitment analysis and improve forecasting accuracy.
 
4. Data Integrity and Validation Requirement ID: ELMS-REQ-006Requirement:
 
ELMS shall enforce validation on the EDIPI, UIC, Actual Size, and Issued Size fields to ensure compliance with format standards and controlled vocabularies, and shall reject incomplete or improperly formatted entries.
 
Mission Critical:
 
Benefits:
  • Data will enable better modeling of demand leading to  more satisfied customers
  • Better modeling of demand from both usage and sizing will unlock significant savings in an organization this large
 
Frequency: 
Monthly

Users: 
Materiel Managers
WH Managers
ICP

 
02195 Add Remarks Field to Individual Issue Warehouse USCG New
Change Request: Process Improvement
 
Description:
There is not a Remarks field available during the Individual Issue process.
 
Recommended:
Add Remarks field to issue details grid for Individual Issue. Also map the remarks field to the Member Sales Financial Report grid so that the remarks are visible when the user runs the member sales report.
 
Mission Critical:
 
 
Benefits:
Having a remarks field could benefit all users utilizing ELMS because it would allow users to capture additional non standard data during the Individual Issue process. Specifically, UDC would like to use this field in order to enter Company data for the companies that are visiting the distribution center for issuing.

Frequency: 
Weekly

Users: 
This change could benefit all ELMS users that do individual issuing.
02194 Update GFM-A Account Manager Role Warehouse USAF New
Change Request: New Role Design

Description:
AF GFM-A Account Manager role users are unable to access the ICN Inquiry screen from the Inventory Inquiry screen in ELMS Warehouse Module.  When the users click on the stock number link, they receive an error message.  Recommend adding Read access to ICN Inquiry screen to the GFM-A Account Manager role to 1) view the ICN Inquiry screen and 2) prevent the user from receiving the error message.
 
Recommended:
Add Read access to ICN Inquiry screen to the GFM-A Account Manager role
 
Mission Critical:
Not a new role design, but a modification to the existing GFM-A Account Manager role.
 
Benefits:
This provides the ability to financially report DAF CICP OM&S assets to GAFS-R using the DAF approved valuation methodology.

Frequency: 
Weekly

Users: 
All current and future users of the Warehouse module in support of AF GFM-A CICP effort.
02193 OM&S Financial Reporting using LAC Materiel Management USAF New
Change Request: Process Improvement

Description:
DAF CICPs need ELMS to enable OM&S financial reporting using the Latest Acquisition Cost (LAC) methodology.  This is the valuation method selected by the DAF for CICP managed OM&S spare parts.  LAC should replace the current Moving Average Cost (MAC) valuation method sent to GAFS-R from the ELMS ICP module.  Each ELMS catalog entry will contain a data element identifying the valuation methodology.  PDC 1510 will add a data element to the 832N transaction for the valuation methodology.  ELMS will need to update their 832N processing for PDC 1510 once its approved.   For the existing stock numbers, ELMS will need to update all type asset code = ‘O’ stock numbers in the AF CMP GFP catalog to add the new data element from PDC 1510.  ELMS will need to add support for a new Accounting Transaction that will be used to report the revaluation of existing inventory to the LAC. For DAF, this will need to be translated into a Bid Number (new one to be assigned) for GAFS-R  reporting.  Solution needs to be in place to turn on financial reporting in FY26.
 
Recommended:
Recommend that ELMS Materiel Mgmt., Catalog, and  Accounting services to support the add the LAC valuation methodology to enable financial reporting (replacing MAC), add a data element to the catalog to identify the valuation methodology of OM&S, update the 832N processing for compliance with ADC 1510, update AF CMP GFP catalog with new data element to enable financial reporting, update accounting to support the accounting of OM&S using LAC and for the revaluation of existing inventory to LAC, and implement new bid code GAFS-R.
 
Mission Critical:
DoD 7000.14-R Volume 4, Chapter 4  2.4.2.3 / SAFFAS 3. Latest Acquisition Cost (LAC). LAC assumes the latest acquisition
inventory cost for all existing stock of the same product, regardless of older purchase prices. When
applying the LAC valuation, management periodically revalues the inventory and establishes an
allowance account for the unrealized holding gains and losses associated with ending inventory.
 
Benefits:
This provides the ability to financially report DAF CICP OM&S assets to GAFS-R using the DAF approved valuation methodology.

Frequency: 
Daily

Users: 
This requirement enables the automation of financial reporting for the 100+ DAF CICPs to GAFS-R in addition to providing ELMS users with the option to report OM&S at the Latest Acquisition Cost.
02192 M&U Cannibalization MU AvSE New
Change Request: New System Process

Description:
When an ordered part from ILS-S is delayed, maintainers may cannibalize a part from another asset to meet mission requirements. However, there's currently no way in ELMS to transfer the document number for the ordered part to a different Work Order.
 
Recommended:
Please add a new Cannibalization screen to enable the transfer of a document number between Work Orders. Enforce remarks section to properly document the approved action.
 
Mission Critical:
Department of the Air Force Instruction (DAFI) 21-101 Para 11.13
 
Benefits:
To properly satisfy an existing supply requisition and to meet priority mission requirements.

Frequency: 
Monthly

Users: 
This change will be applicable to 15,000+ users assigned to Site FH-AFHAF

 

Home  |  Security Notice    Official Defense Logistics Agency Logo    Disclaimer  |  Accessibility
 
Defense Logistics Agency (DLA)
Logistics Catalog and Data Solutions (LCDS)