There is not a way to track status of an inventory.

 

Create an Inventory Status report that shows locations that have been inventoried and those that have not been inventoried for a user selected date range.

 

 

 

Allows for a way to track inventoried and to be inventoried locations for a selected date range.

 

Frequency: Daily

 

Users: 100+ Users

Unable to determine the project POC from the Project table.  You can only view it by editing the project code.

 

Add the project POC information to the grid options of the project table.

 

 

 

Allows the user to view the project POC.

 

Frequency: Daily

 

Users: 100+ Users

Current field is only three characters. With the size of our structure we need to increase the number of characters from three to ten.

 

Increase the number of characters from three to ten.

 

Increasing the Project Code will prevent the duplications of project numbers.

 

Increasing the Project Code will prevent the duplications of project numbers.

 

Frequency: Daily

 

Users: 100+ Users

Current DPAS configuration limits the ability to assign assets to M&U at the UIC level.  Aviation maintenance units within FH-AFHAF have custodian accounts that are not required to use M&U but assigned assets are loaded against a Maint Group ID (MGID). This results in asset records being bridged over to M&U but are not actively managed.  

 

Provide capability to bridge/ unbridge by Custodian Number's. Adding MGID characteristic to Custodian Number's.

 

PAD 22-02 signed by the Chief of Staff of the Air Force (CSAF) directs the centralized management of CAvSE at the enterprise level, residing within the 440 SCOS Aviation Support Equipment Management Flight. This change will allow for future data mining actions, ensuring equipment accuracy.

 

This will enable the Air Force to achieve the desired effects in improving overall readiness and war-fighter support.

 

Frequency: Hourly

 

Users: This change will be applicable to 15,000+ users assigned to Site FH-AFHAF, as well as other agencies or departments that conduct maintenance on their support equipment.

The interface being constructed between TFSMS and ELMS was lacking key attributes that are essential in identifying and defining the LIN/TAMCN used by the Marine Corps.  Inventory Managers and Equipment Specialists throughout the Marine Corps rely on the additional data being requested to assist in their day to day management of Class VII inventory.  The data being asked for should be added to the Enterprise catalog.

 

 

TAMCN

NATIONAL_STOCK_NUMBER

STANDARDIZATION_CATEGORY_CODE

TAM_STATUS

TAM_STATUS_DATE

ITEM_EXIT_DATE

COLLOQUIAL_NAME

MODEL_NUMBER

DIMENSION_HEIGHT_IN_FEET

DIMENSION_WIDTH_IN_INCHES

DIMENSION_WIDTH_IN_FEET

DIMENSION_LENGTH_IN_FEET DIMENSION_LENGTH_IN_INCHES

DIMENSION_HEIGHT_IN_IN

STAND_PKG_CUBECHES

STD_PKG_LB_WT

 

1.1 Once the interface is established, the ELMS system shall include all identified attributes in the Enterprise level catalog for the Marine Corps. the primary key to link the information to the catalog is [National_Stock_Number].

 

1.2 Once the information is included in the Enterprise level catalog, ELMS will make that information available to sub-catalogs (ie, SKO, Stock Item, M&U, Material Management, PA)

 

1.3 The frequency of the update shall be dependent on the interface agree established between Marine Corps TFSMS system and ELMS.

 

2.0  NSN SUBSTITUTION: The ELMS system shall provide the inventory Manager, operating in the Material Management module, with the capability to substitute an NSN within a TAMCN group, taking into consideration STANDARDIZATION_CATEGORY_CODE from the TFSMS attributes, which will be added to the Enterprises Catalog.  

 

2.1  In the case where a denial is received at the Material Management module and the document is placed back into a backorder status.  ELMS shall provide the Inventory Manager with a capability to substitute and NSN only when the replacement NSN is with the like LIN\TAMCN group.  The criteria for the replacement will be strictly controlled by NSNs that have "In Service" (IS), "Plan Allowance" (PL), Disposal Plan (DP) assets available based on the  [TAM_STATUS] attribute in the catalog.  
2.3  ELMS shall be programed to conduct a virtual verification of the selection being made by the Inventory Manager ensuring the warehouse selected, the NSN, quantity, Condition Code and the Purpose Code and support the requested MRO.  If the asset is not available matching the specifications identified for the substitution, ELMS will provide the Inventory Manager with an alert and the process will be halted until the error is corrected.

 

 

 

 

• Meets MARCORLOGCOM's business model
• Assists in 100% accountability of assets
• Complies with current audit controls

 

Frequency: Daily

 

Users: Affects all USMC users

ELMS must enforce Serialized Item Management (SIM) for designated National Item Identification Numbers (NIINs) across various Enterprise Logistics Management System (ELMS) modules. Data exchanges with external trading partner systems via DLMS EDI/X12 transactions sometimes fail to include required serial numbers for serialized assets. This occurs primarily in, but not limited to:

Implement an automated edit-check mechanism within ELMS to identify inbound DLMS EDI transactions missing required serial numbers, route them to an error handling interface for user remediation, and support transaction reprocessing once corrected. This ensures serialized assets are tracked consistently across the enterprise.
    1.1.2 Enforcement Against Serialized NIIN Catalog. The system shall reference the ELMS NIIN Catalog or Master Item File to determine if an item requires serialized tracking before enforcing serial number validation.

 

    1.1.3. Transaction Error Flagging. Transactions missing required serial numbers shall not be ingested into ELMS records but instead flagged as “Unprocessed” and queued for user intervention in the Interface Queue Manager.
    1.1.5. Manual Update Interface. The dashboard shall support manual entry of missing serial numbers by the ELMS User after collection from the originating trading partner system.  

 

    1.1.6  Audit Trail Capture. The system shall capture all entries made manually to enhance the inbound EDI transactions:
   1.1.10. Configuration Flexibility. Administrators shall be able to update the list of NIINs subject to Serialized Item Management without requiring code changes, using an ELMS catalog or configuration table.    

 

 

 

• Meets MARCORLOGCOM's business model
• Assists in 100% accountability of assets
• Complies with current audit controls

 

Frequency: Daily

 

ELMS currently does not possess the ability to attach Key Supporting Documents (KSA) (ie. LTI's, signed 1348s, 1149) to a document that is in a closed status.  This was discussed during the on site visit to the ELMS LEIDO's facility in early March 2025.  This will impact MARCORLOGCOM's ability to answer audit related inquires if not resolved.

 

1.0  Inventory Managers, using the Material Management (MM) module, shall be provided with the capability to upload an attached Key Supporting Documentation (KSDs) to documents considered closed in ELMS.  This is to facility the requirement to extract supporting documentation during an audit evaluation.
3.1 ELMS shall provide personnel using the Property Accountability (PA) module with a capability retrieve attachments associated to the account which they are assigned to.

 

 

 

• Meets MARCORLOGCOM's business model
• Assists in 100% accountability of assets
• Complies with current audit controls

 

Frequency: Daily

 

Users: This change impacts all USMC users

MDA has a requirement to manage operating materiel and supplies "OM&S" that are currently being managed using MS Excel spreadsheets.  In addition, MDA is requesting DPAS system enhancements to support “actual cost” accounting for OM&S within the warehouse module.   On occasion, MDA may have assets (non-capital and capital) that are awaiting transfer / disposition that it would like to have stored in a warehouse.  DPAS does not currently support fixed asset accounting or OM&S accounting by actual cost for items that are accounted for in the warehouse.  The proposed solution is for DPAS to configure to manage fixed assets within the warehouse module or through integration with a fixed asset module and to be able to electronically report those items to the MDA financial statements supported by Defense Agencies Initiative (DAI).    

 

• By Stock Nbr, permit the user to determine how they want to financially account for the $ value of OM&S (MAC, LAC, ACT).  Note: MAC = Moving Average Cost, LAC = Latest Acquisition Cost and ACT = Actual Cost.  Actual cost would be limited to serialized OM&S.
• Enable fixed assets and OM&S to transfer between DPAS modules along with their cost and depreciation. Items transferred between organizations with different catalogs will need to have the valuation set based upon the receiving entity's catalog.

 

The implementation of this SCR is in support of customers of the Warehouse / Materiel Mgmt. modules in support of financial accounting of fixed capital assets and OM&S. Methodologies must be DoD 7000.14R / FASAB / US. Treasury USSGL compliant to support an agency's Financial Improvement Audit Readiness "FIAR".

 

Supports financial compliance for all assets / supplies accounted for using DPAS regardless of module.

 

Frequency: Daily

 

Users: This change impacts all users of the Warehouse module.

Recommended: 

 

1.1  The ELMS system shall intake all incoming 180M MRP transitions, from DAAS, and route them to the appropriate Owning-RIC also known as the Primary Issue Control Activity (PICA) within the Material Management (MM) module.

 

1.1.1  Once the 180M transaction has been inbound within the proper ICP management area, in Material Management, the system shall assigned the work to the appropriated Inventory Manager designated by the association of the NSN to the [Program Name].

 

1.1.2  The system shall provide the Inventory Manager with the capability to respond back to the 180M with the appropriate 870M/FTR transactional response. (see attachment for appropriate response codes)

 

1.1.3  The system shall provide the Inventory Manager with a set of values representing the FTR response statuses for selection during the 870M transaction build. (See MRP Process Flow attachment)

 

1.1.3.1 If the Inventory Manager responds with any Status codes begin with "S" (Rejected) the system will created and respond back to the originator via DAAS with an (870M, LQ*0*FTR, LQ*81*S_) noting the selected Status code.

 

1.1.3.1.2 If the Inventory Manager responds with any Status codes begin with "S" (Rejected), following the transmission of the 870M response, the system will mark the transaction as closed, no further action required. (example of DLMS X12 870M transactions attached)

 

1.1.3.2 If the Inventory Manager responds with Status codes [TA, TB, TH, TJ] the system will created and respond back to the originator, via DAAS with an (870M, LQ*0*FTR, LQ*81*T_) noting the selected Status code. The 870M will remain open until the equipment is received or the 180M cancellation is received by the originator.  

 

 

1.1.4  If the system receives a 180M / FTC (Cancellation Request) the original document will be marked closed and retired in ELMS.

 

2.0  The Warehouse Module (WM) will be prepared to receive the inbound due-in transactions as directed by the 527D PMR.

 

2.1  The system shall possess the capability to receive 870M/FTL and 856R/FTM transactions coming for the  originator via DAAS as directed in the aforementioned 870M/FTR response.

 

2.1.1 The system shall provide the Inventory Manager, using the Material Management (ICP) module and the receiving warehouse person using the Warehouse Module (WM) with the ability to see all transactions relating to MRP.

 

2.1.2 The system shall provide the receiving warehouse with a capability to receipt for the inbound shipment using the designated 870M/ FTZ transactions with the appropriate status codes. (See MRP Process Flow attachment)

 

2.1.2.1 If the shipment is received and all assets are accounted for, the WM module will produce the 870M/FTZ transactions that will be transmitted back to the Owning RIC/ICP via DAAS.