|
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.
Monthly
Users:
This change will be applicable to 15,000+ users assigned to Site FH-AFHAF
|
|
02191
|
Time Zone Update
|
MU |
AvSE |
|
Change Request: Process Improvement
Description:
Two to three times a year users overseas are experiencing issues related to Daylight Savings Time which causes them to have to insert dates as one day in advance to correctly show the correct date. This causes issues for inspection due dates, Asset Next Maint Dt, Asset Last Maint Dt, as well as reporting when closing maintenance work orders. A standard time that does not change would alleviate these issues.
Recommended:
Create a toggle, or feature flag, at the Maintenance Program level to give OPR(s) the ability to change the system to read Greenwich (Zulu) time. Once selected, the times recorded in ELMS will switch from the current time zones to Zulu time, which is a standard time zone for DoD personnel.
Mission Critical:
Benefits:
With the Time Zone as a single, non-changing time, this will standardize reporting across the Enterprise, or those whom choose to enact it, alleviating the constant recurring bug fix requests that get reported to ELMS Support.
Daily
Users:
All overseas users are affected by this.
|
|
02190
|
Maint Asset Activity Inquiry
|
MU |
AvSE |
New |
Change Request: Process Improvement
Description:
Within the M&U module, it is not possible to see asset history in as much detail as other modules. It is not possible to see who profiles an asset, or if an asset is re-profiled it is not possible to see when the change was made or by whom.
We have to ask the ELMS service desk to look back at keystrokes to see who made the change and when.
Recommended:
In inquiries add an Asset History option, the searchable fields should include date from, date to, asset id, Maint Activity, Last Updated By, Last Updated Date.
The selectable fields should include the same as the Searchable fields at a minimum, as well as all the fields available in the Maintenance Asset Master.
The results should highlight any changes made (like ELMS does in the Asset Activity inquiry in PA), who made the changes, and on what date.
Mission Critical:
DAFI 21-101, DAFI 21-103, AFTO 00-20-1, AFTO 00-20-2
Benefits:
This will allow users in the field to look up and see what changes were made to their assets on their own and will cut down on tickets submitted to the ELMS Help Desk for historical data in M&U. This will also allow the DAF ELMS FMO to better assist users without having to reach out to the ELMS Help Desk.
Weekly
Users:
All ELMS M&U users will be affected.
|
|
02189
|
Speed to Release
|
Warehouse,Materiel Management |
USMC |
New |
Change Request: Process Improvement
Description:
ELMS currently lacks the ability for Warehouse Managers to upload and mass process lists of required items for Materiel Release Orders (MROs). Each NSN and quantity must be entered and executed individually, creating an inefficient, error-prone process that delays materiel movement, increases manpower burden, and reduces responsiveness to urgent operational requirements. Without a Speed to Release capability, ELMS cannot meet the Marine Corps’ expectations for rapid, scalable, and accurate logistics support in a contested operating environment. Failure to implement this capability creates a significant deficiency in ELMS: the system cannot efficiently support large-scale deployments, surge requirements, or time-sensitive missions that demand immediate bulk materiel release. This gap undermines ELMS’s ability to achieve its core mission of improving end-to-end logistics readiness and risks stakeholder confidence in the program’s modernization efforts. By closing this gap, the Marine Corps will gain a faster, more reliable, and policy-compliant release process that enhances both operational readiness and long-term ELMS success.
Recommended:
To support the design, development, and validation of the proposed Speed to Release capability, a detailed requirements list has been prepared and is included as Attachment A to this Business Requirements Document. The file, titled "GAP 106_BRD_ELMS_USMC_MARCORLOGCOM_1.b Speed to Release Requirement Listing", provides a structured breakdown of all functional requirements aligned to PMI standards. Each requirement is organized by process category, description, step number, and requirement ID, and is written as a testable “shall” statement to ensure traceability, compliance, and clarity for developers, testers, and program managers. This attachment serves as the authoritative baseline for system design and future enhancements related to the Speed to Release functionality.
As the foundation for defining the Speed to Release capability, the business process flow titled GAP 106 _BRD_ELMS_USMC_MARCORLOGCOM_1.b Speed to Release_v1.2 20250903_Process Flow is included as Attachment B to this package. This document captures the step-by-step operational sequence for initiating, validating, and executing materiel release orders within the ELMS Warehouse Module. It provides the process logic that guided the identification of functional requirements and ensures that system development aligns with established Marine Corps logistics workflows, DLMS compliance, and the policy objectives outlined in MCO 4400.201 W/CH-3. The process flow will serve as a critical reference point for developers, testers, and program managers to validate that the new functionality supports accurate, efficient, and policy-compliant warehouse release operations.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
ADHOC
Users:
Materiel Managers
WH Managers
ICP
|
|
02188
|
SKO Exemption - Condition Code G
|
Warehouse,Materiel Management |
USMC |
New |
Change Request: Process Improvement
Description:
Acquire to Retire (Equipment): L1 Bring into APSR
The ELMS Warehouse Management (WM) model incorrectly reassigns the Condition Code of a Principal End Item (PEI) to “G” (Unserviceable – Incomplete) whenever a required Child NSN is not present in the Sets, Kits, and Outfits (SKO) configuration. While appropriate in some cases, this auto-reassignment creates systemic errors when applied to ICP-controlled warehouses, where assets must retain the Condition Code assigned by the accountable Warehouse DoDAAC. This misalignment disrupts key workflows: PEIs inducted into Depot Maintenance must remain in Condition Code “F,” and those exiting Depot rebuild must be issued as Condition Code “A” regardless of whether collateral Child NSNs are recorded. If not corrected, this defect will cause inaccurate inventory reporting, disrupt Depot Maintenance inductions, and undermine Marine Corps property accountability. Erroneous downgrades to Condition Code “G” risk misallocation of maintenance resources, reduce asset visibility accuracy, and introduces a Significant Deficiency within the ELMS system. Request all warehouse DoDAACs assigned to an ICP, by Owning DoDAAC, be exempted from the SKO auto reassignment of Condition Code “G” process.
Recommended:
GAP107-001 (Functional). The system shall exempt all Warehouse DoDAACs tied to an ICP Owning DoDAAC from automatic reassignment of Condition Code 'G' during SKO assembly/disassembly processes.
GAP107-002 (Functional). The system shall retain the Condition Code assigned by the Warehouse DoDAAC when the PEI is processed under an ICP-controlled structure.
GAP107-003 (Functional). The system shall allow Warehouse personnel to manage Condition Codes through normal receipting, COSIS, and condition reassignment processes without system override.
GAP107-004 (Functional). The system shall prevent auto-conversion of Condition Code 'F' PEIs being inducted into Depot Maintenance processes.
GAP107-005 (Functional). The system shall ensure all PEIs exiting the Depot rebuild process are assigned Condition Code 'A' regardless of missing or unrecorded Child NSNs.
GAP107-006 (Functional). The system shall continue to validate Child NSNs marked as 'Required' within the SKO catalog when not under ICP-controlled warehouses.
GAP107-007 (Functional). The system shall apply Condition Code 'G' reassignment only when the Warehouse DoDAAC is not linked to an ICP structure and the PEI is missing one or more Required Child NSNs.
GAP107-008 (Functional). The system shall provide configuration controls to distinguish between ICP-controlled DoDAACs and non-ICP warehouses.
GAP107-009 (Functional). The system shall enforce that all exemptions are logged and auditable to maintain FIAR compliance.
GAP107-010 (Functional). The system shall maintain compatibility with DLMS standards (DoD 4000.25) for Condition Code reporting and updates.
GAP107-011 (Technical). The system shall update the ELMS data model to include an attribute identifying Warehouse DoDAACs linked to an ICP Owning DoDAAC.
GAP107-012 (Technical). The system shall apply existing business logic to standard (non-ICP) warehouses without disruption.
GAP107-013 (Technical). The system shall generate error messages when ICP exemption logic fails (e.g., incorrect ICP assignment, missing configuration).
GAP107-014 (Technical). The system shall prevent reassignment of Condition Code 'G' if the DoDAAC-to-ICP linkage cannot be confirmed, defaulting to current assigned Condition Code until resolved.
GAP107-015 (Technical). The system shall log all Condition Code assignment or exemption actions for audit review.
GAP107-016 (Technical). The system shall enforce RBAC (Role-Based Access Control) ensuring only authorized warehouse personnel can update Condition Codes.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
Daily
Users:
Materiel Managers
WH Managers
ICP
|
|
02187
|
Exceptions Data - DLMS 940R(A5E)
|
Warehouse,Materiel Management |
USMC |
New |
Change Request: Process Improvement
Description:
ELMS does not currently ensure consistent capture and transmission of ad hoc shipping instructions using the NTE segment within DLMS 940R/A5E Materiel Release transactions. These instructions, which include special delivery notes (e.g., “SHIPMENT TO BE SENT 3RD PARTY”), must accompany the MRO and be visible on both the outbound transaction and the DD Form 1348 release document. Current limitations prevent full compliance with DLMS Implementation Convention (ADC 1472), reducing the system’s ability to support operational flexibility and accountability when exceptions arise. This gap is assessed as a Significant Deficiency. Without the ability to reliably include and propagate ad hoc shipping instructions through the NTE segment, ELMS risks misrouted or delayed shipments, improper handling or disposal of materiel, and incomplete audit trails. The absence of this capability undermines Marine Corps supply accountability, increases reliance on manual workarounds, and places ELMS at risk of failing to meet enterprise-wide DLMS compliance and operational readiness requirements.
Recommended:
GAP108-001. System shall provide users the ability to enter ad hoc shipping instructions in the DLMS 940R/A5E using the NTE segment with qualifier 'DEL'.
GAP108-002. System shall allow up to 12 repeats of the NTE segment, each supporting up to 30 characters, for a maximum of 360 characters of ad hoc shipping text.
GAP108-003. System shall map user-entered ad hoc instructions to the correct NTE segment in the DLMS 940R/A5E transaction and ensure compliance with X12 formatting rules.
GAP108-004. System shall make NTE segment ad hoc shipping instructions available for printing on the DD Form 1348 release document.
GAP108-005. System shall ensure NTE segment ad hoc shipping instructions are linked to the Materiel Release Order (MRO) record for traceability.
GAP108-006. System shall ensure all stakeholders (ICP, Storage Activity, Transportation) can view ad hoc shipping instructions transmitted via the NTE segment.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
Daily
Users:
Materiel Managers
WH Managers
ICP
|
|
02186
|
UIC & EDIPI added to reports for individual gear issues
|
Warehouse |
USMC |
New |
Change Request: Process Improvement
Description:
1. Lack of EDIPI in Data Export Gap: Inability to uniquely identify individual Marines receiving gear. Impact: Hinders traceability of gear usage, replacement, and destruction rates at the individual level. Business Risk: Commanders and program managers lack insight into per-Marine gear life cycle and accountability, impeding informed decision-making and audit readiness.
2. Missing or Incomplete UIC Field Gap: Inability to associate gear issuance and destruction data with specific units. Impact: Prevents MEF commanders from assessing gear distribution and attrition trends across units. Business Risk: Creates blind spots in unit-level readiness and undermines logistical planning, potentially leading to over- or under-supply scenarios.
3. Single "Size" Field Without Differentiation Gap: 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.
Recommended:
1. Unique Identification of Marines Requirement ID: ELMS-REQ-001Requirement:
ELMS shall include a mandatory EDIPI field in all gear issuance and gear destruction records to uniquely identify the individual Marine associated with the transaction.
2. Unit-Level Traceability Requirement ID: ELMS-REQ-002Requirement:
ELMS shall include and populate the UIC field in all gear issuance and destruction records to associate each transaction with the appropriate unit.
3. Gear Size Tracking Enhancements Requirement ID: ELMS-REQ-003aRequirement: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.
4. Data Export Schema Updates Requirement ID: ELMS-REQ-004Requirement:
ELMS shall include the EDIPI, UIC, Actual Size, and Issued Size fields in all relevant data exports and reports to support downstream analysis and performance audits.
5. Analytical Reporting Capability Requirement 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.
6. 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.
7. Data Security and Compliance Requirement ID: ELMS-REQ-007Requirement:
ELMS shall store EDIPI and other PII in compliance with DoD cybersecurity standards, including encryption at rest and in transit, audit logging, and role-based access control in accordance with NIST SP 800-53.
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.
Monthly
Users:
All USMC Users
|
|
02185
|
Modify the Stock Nbr Inventory Inquiry
|
Warehouse |
USCG |
New |
Change Request: Process Improvement
Description:
There is a Show Due In checkbox on this report, but it does not function in an ideal way. The default sort shows inventory successfully brought to record. We need to be able to run a report that shows what the cost value is of “unreceived” based on incomplete or yet-unfinished receiving documents.
Recommended:
We would like for only the due ins to be displayed when this checkbox is selected. We would then benefit from a column option that calculates the order cost of the assets not yet received – a simple multiplier of the unit price or order price and the due in qty.
Mission Critical:
Benefits:
The ability to see the cost value of inventory not yet received.
Monthly
Users:
The number of users that would be benefit from this change at this time is roughly 8, but it can increase as we continue implementation efforts with the Coast Guard.
|
|
02184
|
Update Member Sales Transaction Report Surcharge Visibility
|
Warehouse |
USCG |
New |
Change Request: Process Improvement
Description:
The current Member Sales Transaction report only displays the surcharge/tariff amount for a single item, regardless of the quantity issued. For example:
If a ball cap is issued for $20.08, the report shows a surcharge of 0.10.
However, if 3 ball caps are issued, the report still only shows $0.10 as the surcharge, requiring users to manually calculate the correct total surcharge ($.0.30 in this case)
This creates inefficiency and increases the likelihood of manual calculation errors.
Recommended:
Add a new column to the Member Sales Review transaction report that displays the total surcharge/tariff amount applied for the full quantity issued.
Make the surcharge column a default column instead of having to select it from the grid options
The report should automatically multiply the per- item surcharge by the total quantity issued.
The new column will reflect the total surcharge applied for the transaction line item.
Users will have a clear, accurate view of total surcharge values without needing to perform manual calculations.
Mission Critical:
Benefits:
Users will have a clear, accurate view of total surcharge values without needing to perform manual calculations which is important for audit-ability and accuracy.
Daily
Users:
The number of users that would be benefit from this change at this time is roughly 8, but it can increase as we continue implementation efforts with the Coast Guard.
|
|
02183
|
Cost of Inventory Report
|
Warehouse |
USCG |
New |
Change Request: Process Improvement
Description:
Uniform Distribution Center (UDC) needs a report to show the total value of all stock on hand for the entire warehouse like the one attached from their current Integra system. The Unit Cost should represent the 'cost' of the goods. The report needs to be made available within the Materiel Mgmt and Warehouse Mgmt applications.
Recommended:
The report should contain the following criteria filters: Grand Total by Type Asset Code and Grand total of all. Select specific Stock Nbr(s) to display in report. The report should provide for all warehouses, or for specific selected warehouses. For equipment, it should be the actual cost as the Unit Cost, and for OM&S, it should be the actual cost paid using the Moving Average Cost methodology to determine the current on hand cost. When displaying specific Stock Nbrs, the report should display Stock Nbr, Item Desc, Serial Nbr, Lot Nbr, Condition Cd, Qty, Unit Cost and Total Cost. Add a Stock Status Report to the Real-Time Reports tab in the system. When displaying specific Stock Nbrs, include Qty On Hand
Mission Critical:
USCG has a requirement to know the cost of their inventory for financial purposes.
Benefits:
This change would allow UDC to obtain a dollar value of the stock on hand.
Monthly
Users:
This report will not only benefit USCG, but all ELMS users.
|
|
02182
|
Improvement to Issue Receipt for Tariff
|
Warehouse |
USCG |
New |
Change Request: Process Improvement
Description:
Currently, tariffs/surcharges that are applied to items are not reflected on the Issue Receipt and are slightly misrepresented at the conclusion of an individual/unit issue – via the Member Sales Review detail grid. This creates confusion for members and staff when reviewing receipts, as the true breakdown of item cost versus surcharge is not transparent.
Recommended:
Update the Issue Receipt format to add the applied tariff/surcharge to the total transaction cost. For example, if the item cost is 100.00 and there is a 2% tariff. The total cost on the hand receipt should be $102.00.
When an item is issued, the receipt will clearly show:
Total transaction cost (item cost +tariff/surcharge). The tariff should only be seen by the Supply Unit, not the customer.
If multiple quantities are issued, the tariff line item should reflect the total surcharge amount for the full quantity.
For Individual Issue – on the header, there needs to be a tariff flag or a tariff percentage field so that the stated tariff placed against the stock item record is applied to the assets being issued – this should then be data available across any “issue activity” report or inquiry.
Mission Critical:
Benefits:
Elimates confusion for members reviewing receipts and shows the true breakdown of item cost versus surcharge.
Daily
Users:
Currently, this change would only impact roughly 8 users however the USCG is new to ELMS. This change has the potential to impact all USCG users and other agencies that use the tariff/surcharge function.
|
|
02181
|
Automation of DMR Capability
|
PA,MU,Warehouse |
USMC |
New |
Description:
The Enterprise Logistics Management System (ELMS) currently lacks the visibility, traceability, and audibility necessary to properly capture, validate, and certify Deferred Maintenance & Repairs (DM&R) data. This data is congressionally mandated and must be reported in accordance with Statement of Federal Financial Accounting Standards (SFFAS) 42, Office of Management and Budget (OMB) Circular A-136, and the DoD Financial Management Regulation (DoD 7000.14 R). DM&R figures are a required supplemental information (RSI) disclosure in the Department of Defense's (DoD) annual financial statements and directly impact the audibility of the DoD's end-of-year (EOY) reporting.
Recommended:
FR1: – The system shall provide a mechanism to auto-update Work Order (WO) State Code or indicator check block within each of the three areas: Property Accountability (PA), Maintenance & Utilization (M&U), or Warehouse. For COSIS, the indicator shall be in the Warehouse module. For DM&R, the indicator shall be in the M&U module. System shall allow a user to check a 'DMR' or 'COSIS' block when deferring work orders.
FR2: – ELMS shall create a dashboard entry for both DM&R and COSIS that consolidates data across modules and presents total outstanding deferred actions for leadership visibility.
FR3: – ELMS shall create a method to retrieve the total cost of deferred orders for BOTH hours (time) and materials (money). This should be system-generated and reconcilable to financial reporting outputs.
FR4: – ELMS shall establish a Maintenance & Utilization (M&U) role for Custodian-RO-RI to enable oversight and accountability of DM&R and COSIS identification, flagging, and reporting.
FR5: – ELMS shall, in the WO statuses automatically updated for deferred WO State Codes. This prevents deferred work from being prematurely closed or excluded from financial reporting.
Compliance Alignment
The proposed SCRs align ELMS functionality with federal financial management requirements:
- **SFFAS 42**: Requires disclosure of DM&R as part of Required Supplemental Information (RSI).
- **OMB Circular A-136**: Establishes reporting format and requirements for RSI, including DM&R.
- **DoD 7000.14-R, Volume 6B**: Prescribes financial reporting policies and procedures for RSI disclosures, requiring accurate and auditable reporting of DM&R.
Implementing these SCRs will ensure ELMS can support the accurate capture, validation, and reporting of DM&R and COSIS data, strengthening DoD audit readiness and meeting statutory reporting requirements.
In 2018, DM&R reporting across DoD systems was effectively zero dollars. By Q3 of FY2025, reported DM&R obligations and estimates exceeded $26 billion. This rapid growth underscores both the materiality of DM&R reporting and the heightened audit risks associated with inaccurate or incomplete capture of data. Without a systemic mechanism in ELMS to automatically identify, flag, and aggregate deferred work orders (WOs) and Care of Supplies in Storage (COSIS) requirements, the Department risks failing to comply with congressional mandates, audit findings, and statutory financial reporting requirements.
Key Facts
- DM&R is a congressionally mandated reporting requirement under SFFAS 42.
- OMB A-136 requires inclusion of DM&R as Required Supplemental Information (RSI) in agency financial statements.
- DoD 7000.14-R Volume 6B prescribes financial reporting requirements, including supplemental disclosures.
- From 2018 ($0 reported) to Q3 2025 (>$26B reported), DM&R grew significantly in scope and financial materiality.
- Current ELMS architecture does not provide sufficient mechanisms to automatically track, flag, and reconcile deferred maintenance and COSIS data.
PMCS Cost Capture
9,overall cost per month and year Individual repair parts used, Labor hours and rates, and Other material costs.
10. ELMS shall aggregate PMCS cost data by:Equipment type, Unit/DODAAC, and Fiscal period.
11. The cost data shall be available for reporting in both tabular and chart formats.
12. The cost tracking function shall integrate with the DMR dashboard for consolidated visibility.
Mission Critical:
SFFAS 42, OMB Circular A-136, and DoD 7000.14-R, Volume 6B
Benefits:
This will enable users to properly budget and quickly understand the readiness of its fleets.
Daily
Users:
All USMC users
|
|
02180
|
DoDAAC Inquiry TAC Type Field
|
PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW) |
SOCOM |
New |
Change Request: Process Improvement
Description:
DoDAAC Inquiry page under the 'TAC Type' field is confusing users on the Shipping Address. First line (TAC1) reads 'Std Address (Ship To / Bill To). Second line (TAC2 the Shipping Address) shows 'Freight / Bulk Item. Third line (if applicable) shows 'Bill To' which is correct, no change needed.
Recommended:Switch the TAC Type for the first & second line. Change the second line TAC Type to 'Ship To' for clarity.
Mission Critical:
Improves Accuracy and Accountability.
Benefits:
Better understand for all users when conducting a DoDAAC inquiry of where the materiel should be shipped to.
Daily
Users:
All USSOCOM Users.
|
|
02179
|
Merge Security and Admin Role Types
|
PA,MU,Warehouse,Materiel Management,FSM,Registry (SA/LW) |
Leidos |
New |
Change Request: Process Improvement
Description:
Base upon the last few year of EY audits, there is no need to separate Admin and Security roles since they are both elevated roles. Merge the Security and Admin roles types prior to start of next audit season.
Recommended:
Rename the Security role to 'System Management'. Move all roles currently assigned to the Administrator role to the new System Management role (3 to 2). Then drop the Administrator role (role key 3). Update documentation with the consolidated role name.
Mission Critical:
This will simplify managing elevated users, allows for easier promotion for temporary 'security' management without losing access to the admin screens, and standardizes our role types while keeping least privilege SOD.
Benefits:
Simplify role types for elevated users for ICAMS upgrade, simplify elevated user management in SIPR and Standalone environments with less personnel, reduce management overhead.
Quarterly
Users:
This will effect personnel whom manage user accounts.
|
|
02178
|
Additional ServiceNow Endpoints
|
PA |
DISA |
New |
Change Request: Process Improvement
Description:
DISA issues and maintains IT equipment to a large customer base that is required to be inventoried on a reoccurring basis. The majority of the customers do not have the personnel to conduct these inventories or the amount of IT equipment they manage is too large to complete in a timely manner. Additionally, by the time the inventory is completed, the fidelity of the data captured has deteriorated.
Recommended:
Develop additional endpoints to retrieve data to ELMS from ServiceNow.
Mission Critical:
Benefits:
By implementing this solution, each piece of IT equipment issued to the customers, captured in ServiceNow, would reflect in ELMS with an updated inventory date. Therefore, significantly reducing the resources required to conduct an inventory.
Daily
Users:
The estimated number of users is at around 100k.
|
|
02177
|
Reconfigure ELMS - LMP interfaces for Transaction Date
|
Enterprise |
Army |
New |
Change Request: Policy / Regulatory
Description:
SFIS Compliance Issue: During LMP's last SFIS compliance assessment from JITC, LMP was informed that the SFIS T5 attribute (transaction date) was not compliant because LMP was receiving it in a 5-character Julian Date from ELMS/DPAS.
Recommended:
JITC states that the interfaces from ELMS/DPAS to LMP should be modified/re-configured so that the SFIS T5 attribute is received in the SFIS compliant 8 character YYYYMMDD format.
Mission Critical:
This effort is to remediate a Joint Interoperability Test Command (JITC)-issued SFIS Compliance finding against the LMP - ELMS/DPAS interfaces:
JITC NFR LMP-INT-07: Change to inbound DPAS Interface INF00195 (Inbound DPAS Capital Asset Depreciation) ; and
JITC NFR LMP-INT-08: Change to inbound DPAS Interface INF00206 (Inbound SPS Post asset related transactions to the LMP System)
Benefits:
Implementing the proposed SFIS attribute T5 format change will remediate two JITC issued NFRs against the LMP - ELMS/DPAS interfaces, thus helping Army to downgrade the associated Material Weakness.
Monthly
Users:
This ELMS/DPAS SCR request is tied back the the LMP tickets: INC0632358 and INC0632372
|
|
02176
|
Capital Threshold Retroactive Change
|
PA |
US Navy |
New |
Change Request: Process Improvement
Description:
Due to the DoD 7000.14-R Vol 4 Ch 25 revision May 2019, "DoD Components should apply the applicable capitalization threshold to their entire population of general equipment retroactively, irrespective of the capitalization thresholds in effect for years prior to October 1, 2013." This will require a change to the logic in ELMS Capital Code of "A" to remove the criteria of the date and cost variables for all assets to only capitalize assets that are $1M or greater for General Fund assets and $250K for assets under Working Capital Funds.
Recommended:
ELMS would need to write a script to change capital code of "A"to reflect a greater than or equal to $1 million for General Fund assets and greater than or equal to $250K for Working Capital Fund assets; meaning all Capital assets under $1 million for General Fund assets and $250K for Working Capital Fund assets will no longer be capital . Once ELMS makes the update, If the effect is not instantaneous, Navy will need to go in and re-apply the capital code of "A" to remove the asset as capital.
Mission Critical:
DoD 7000.14-R Vol 4 Ch 25 revision May 2019, "DoD Components should apply the applicable capitalization threshold to their entire population of general equipment retroactively, irrespective of the capitalization thresholds in effect for years prior to October 1, 2013."
Benefits:
This will minimize the number of capital assets that the Navy owns and keeping in line with the DoD FMR with respect to the valid pricing of capital assets from here forward.
Daily
Users:
All Navy Users ~ 7,700 users
|
|
02175
|
Temporarily Restrict AFTO 244 Alignment
|
MU |
USAF |
Removed |
Change Request: Policy / Regulatory
Description:
The current automated version of the AFTO Form 244 does not fully comply with Air Force policy requiring accurate documentation of maintenance and inspections on aviation support equipment (ASE) as outlined in TO 00-20-1. Specifically, it does not allow for proper inclusion of status symbols or the documentation of partially mission capable (PMC) conditions, which are essential for tracking ASE readiness and serviceability.
Recommended:
LOCK/ restrict access to existing EMLS automated 244 Form until the automated form is realigned with the current DAF/AFTO form.
Mission Critical:
The requirement to utilize an AFTO 244 form is referenced in AvSE MIS Interim Guidance (update in progress) and is referenced in TO's 00-20-1, 00-20-2 and DAFI 21-101
Benefits:
Standardization of the form would improve accuracy and reduce the risk of documentation errors for field personnel utilizing the automated and official DAF AFTO 244 form, versus having two different forms with different processes.
Users:
8.5K personnel
7/7/2025 - Removed per Joe Stossel |
|
02174
|
AFTO 244 Alignment
|
MU |
USAF |
New |
Change Request: Policy / Regulatory
Description:
The current automated version of the AFTO Form 244 does not fully comply with Air Force policy requiring accurate documentation of maintenance and inspections on aviation support equipment (ASE) as outlined in TO 00-20-1. Specifically, it does not allow for proper inclusion of status symbols or the documentation of partially mission capable (PMC) conditions, which are essential for tracking ASE readiness and serviceability.
Recommended:
A SCR is underway to incorporate PMC status and additional capabilities into the automated AFTO 244. It would be beneficial to align the automated output with the AFTO 244 with the requirements set forth in TO 00-20-1, would improve accuracy and reduce the risk of documentation errors. Additionally, work plan description and work order data fields should be aligned to populate the AFTO 244 with the Service Requested as documented in the work order. This will provide a more detailed description of the discrepancy listed on the AFTO 244.
Mission Critical:
The requirement to utilize an AFTO 244 form is referenced in AvSE MIS Interim Guidance (update in progress) and is referenced in TO's 00-20-1, 00-20-2 and DAFI 21-101
Benefits:
Standardization of the form would improve accuracy and reduce the risk of documentation errors for field personnel utilizing the automated and official DAF AFTO 244 form, versus having two different forms with different processes.
Users:
8.5K personnel
|
|
02173
|
Electronic Weapon Record Book
|
PA,MU,Warehouse,Materiel Management |
USMC |
New |
Change Request: New Process
Description:
The USMC requires an enterprise-wide capability to automate the collection, entry, and reporting of PEI maintenance and operational data through an Electronic Weapon Record Book (EWRB). The absence of this capability will result in a critical data gap adversely impacting the Ordnance community’s ability to track and analyze key metrics such as round counts, effective full charge, pullover gauge measurements, maintenance costs, availability, and readiness for weapon systems. This data is essential to inform decision-making across strategic, operational, and tactical levels of command and to support life cycle management and resource allocation decisions. Additionally, the capability must extend beyond the Howitzer community to accommodate broader USMC ground equipment and weapons platforms, while incorporating role-based access control to safeguard data integrity. Without this integrated and customizable EWRB capability in ELMS, the Marine Corps risks losing visibility into critical performance metrics, reducing the effectiveness of sustainment planning and readiness reporting. The absence of this capability in ELMS represents a Significant Deficiency, as it limits USMC's ability to track and report maintenance and operational data for serialized ordnance assets. This impairs readiness reporting, life cycle decision-making, and auditability across weapon systems.
Recommended:
REQ-001 - Electronic Weapon Record Book Capability. ELMS shall provide an Electronic Weapon Record Book (EWRB) capability to collect, store, and report serialized ordnance data, including component configuration, inspection results, and firing data. Supports data-driven decision-making for life cycle management and readiness reporting of Marine Corps weapon systems. Users can enter, update, and report weapon-specific data (e.g., round count, component swaps, EFC) for serialized equipment.
REQ-002 - Parent-Child Quality Record Structure. ELMS shall implement a parent-child data structure for weapon records, allowing summary data roll-up from child entries (e.g., Gun Book Part I and II) to the parent weapon header. Enables accurate aggregation of inspection and firing metrics for each weapon system. Child entries (e.g., Pullover Gage, EFC) are reflected in summary fields on the parent record automatically upon save.
REQ-003 - Weapon Component Tracking and Swap Logging. ELMS shall allow tracking of major weapon components (e.g., tube, breech block, breech ring) with fields for serial number, install date, and configuration changes. Provides traceability and auditability for configuration changes and maintenance history. Users can log new components, track EFC baselines, and deactivate prior configurations.
REQ-004 - Charge and Round Entry with EFC Calculation. ELMS shall allow entry of charge and round types to automatically calculate Equivalent Full Charges (EFC) and update total EFC per component. Standardizes performance tracking and avoids manual errors in EFC computation. System auto-calculates EFC and updates roll-up fields upon entry of round count and charge type.
REQ-005 - Role-Based Access Control for Data Integrity. ELMS shall implement role-based access control for the EWRB functionality, including read, write, and update privileges aligned to user responsibilities (e.g., Maintenance Clerk, Officer). Ensures least privilege and protects data integrity in serialized weapon records. Users can only perform functions (view, edit, update) permitted by their assigned roles.
REQ-006 - Audit Trail and Administrative Overrides. ELMS shall provide an administrative override function for manual EFC entry and require justification comments for audit traceability. Supports rebaselining and audit compliance when non-standard updates are required. Administrative EFC updates prompt for reason code and are logged with timestamp and user ID.
REQ-007 - Inspection and Technical Measurement Fields. ELMS shall support data entry for maintenance metrics such as pullover gage readings, elevation/cant/azimuth, and borescope inspections. Captures critical maintenance data used to assess weapon condition and performance. Users can input and update required inspection metrics with validation and summary roll-up.
REQ-008 - Reporting and Data Export Capabilities. ELMS shall support advanced search and export functionality for EWRB records, including filters by SN, EFC %, inspection date, and other metrics. Enables strategic and tactical reporting for sustainment planning and audit readiness. Users can generate reports and export to Excel-compatible formats with full field sets and filters.
REQ-009 - Document Attachment and Multimedia Upload Capability. ELMS shall allow users to attach multimedia files (e.g., images, PDFs, inspection reports, modification instructions) to specific weapon or component records. Enhances record completeness, enables visual and documentation-based validation, and supports audit and technical inspection requirements. Users can upload and view attachments associated with weapon records and all attachments are stored and retrievable per record.
REQ-010 - Disconnected Field Data Entry and Sync Capability. ELMS shall support offline (disconnected) data entry for EWRB functionality, with synchronization to the central system upon reconnection to MCEN. Supports continued operations in field environments with limited or no connectivity, ensuring timely data capture and delayed sync. Users can enter and save EWRB data offline and synchronize it with the main system once a secure network connection is restored.
Mission Critical:
Benefits:
- Meets MARCORLOGCOM's business model
- Assists in 100% accountability of assets
- Complies with current audit controls
Daily
Users:
All USMC Users
|
|
|
Disclaimer | Accessibility
