ELMS Support - SCRs

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: ELMSsupport@leidos.com.

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
02161 Depot Request for Induction Asset (511R_A0) Project Code 3AB Warehouse,Materiel Management USMC New
Change Request: Process Improvement

Description:
While conducting testing, MARCORLOGCOM encountered a problem where ELMS did not allow our Depot Remote Storage Activity (RSA) to call for inventory scheduled for induction, from the Inventory Control Point (ICP) using a (DLMS 511R/A0_) as prescribe in Approved DLMS Change (ADC) 1176.  Within the (DLMS 511R/A0_) a project code of “3AB” must be entered identifying the transaction as being part of a depot required induction.
 
Recommended:
 

1.0 This process starts with one of the Depots, Remote Storage Activities (RSAs), using the Warehouse Module (WM), under the ICP Owning RIC of “MPT”,  ELMS shall provide the mechanism for the RSA Depot warehouse to request for an asset for induction into depot repair.  This will be accomplished using a (DLMS 511R/A0_), with a signal code of “M”, and a Project Code of “3AB”.  The Owning RIC will be specified as “MPT”.  This is in accordance with Approved DLMS Change (ADC) 1176.

 
1.1 ELMS shall route the (511R/A0_) to the Material Management (MM)/ICP module of the specified “Owning RIC”, Inventory Control Point (ICP), Inventory Manager for release or cancellation consideration.
 
2.0 ELMS shall provide the Inventory Manager (IM), within the Material Management (MM)/ICP module, the ability to view all available asset for the specified National Stock Number (NSN) and Condition Code.  The asset viewed will be limited to the available RSA warehouses holding asset under the specified Owning RIC.
 
2.1 ELMS shall allow the Inventory Manager to reply with an (870S/AE_ Cancelation) or proceed to the Material Redistribution module, within the Material Management (MM)/ ICP module.  
 
2.2 If the Inventory Manager locates a NSN with the requested Condition Code, ELMS shall allow the Inventory Manager to create an MRO using the Material Redistribution function.
 
2.3 ELMS shall generate an (940R/A2_) Material Release Order (MRO) to be sent to the losing warehouse DoDAAC.  Note:  It is important to perpetuate the Project Code “3AB”
 
2.4 ELMS shall send the (527D/DW_) Pre-position Material Receipt (PMR)) transactions to the Depot, Remote Storage Activities (RSAs) that originally sent the induction (511R/A0) with Project Code “3AB”.
 
3.0 Using ELMS, the losing Warehouse DoDAAC will process the inbound induction MRO using the Warehouse Module (WM). The warehouse person will (pick, pack, and release) the asset requested for induction.
 
3.1 ELMS shall generate the (870S/AE_ “BA”) and the (856S/AS_) shipping status notifying the Depot, Remote Storage Activities (RSAs) that the asset is on it way. Project Code “3AB” should remain on all documents. The (856S/AS_) will be used as the trigger to reduce the available on hand balance moving the asset in the system to intransit.    
 
3.2 ELMS shall generate the (945A/AR0) and send it back to the ICP, in the Material Management (MM)/ICP module, reporting the asset is now intransit.
 
4.0 ELMS shall provide the Depot, Remote Storage Activities (RSAs) with a capability to receipt for the induction asset document.
 
4.1 ELMS shall upon receipt, and quality control verification produce a receipt (527R/D6_).
 
4.2 ELMS shall gain the asset to the Depot, Remote Storage Activities (RSAs) warehouse DoDAAC.
 
4.3 ELMS shall post the (527R/D6_) to the historical transactions activity log allowing for associated Key Supporting Documents (KSD) to be added later.
 
4.4 ELMS shall add the completed receipt’s (527R/D6_) quantity to the “on hand available “in Inventory Manager’s Material Management (MM)/ICP view and completing out the document.
Mission Critical:
Approved DLMS Change (ADC) 1176
 
Benefits:
 
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
 
Frequency: Daily
 
Users: 

All USMC WH Managers

02160 KSA Obtainment Enterprise Level Material Management Module PA,Warehouse,Materiel Management USMC New
Change Request: Process Improvement

Description:
ELMS currently does not provide the Material Manager / Inventory Manager with the ability to view and download Key Supporting Documents (KSD) associated to a specified NSN and or serial number present, Document Number, or ICN within any of the USMC identified Logistic Programs (LPs) within the Warehouse Module and the Property Accountability (PA) module.  This capability is currently missing from within Material Manager (ICP) module.  Where applicable, automate KSD retrieval requests to support analytical and audit tasking. Transactional audit trail retrieval and sequencing (e.g. Material Transaction history), by applied date is required, to include the ability to select a given transaction from the displayed listing and drill down to obtain any attached KSDs. This capability is required to support audit inquiries, and the day-to-day operational capabilities required for MARCORLOGCOM’s inventory manager to perform their tasking.   Transactional audit trail retrieval must include all transactions applied to any given Inventory Control Number (ICN) historically, to include all KSDs like (receipts, material movements, physical Inventories, Limited Technical Inspections, MROs, Maintenance, etc.).
 
Recommended:
 

1.0 ELMS shall provide the Inventory Manager, within the Material Management module, the capability to search historical and active records by a specific National Stock Number (NSN) and or Serial Number combination, Document Number or Inventory Control Number (ICN).

 
1.1 Within ELMS, the system shall provide the Inventory Manager with a choice to perform the search through:
 
        a.  All Logistic Programs (LPs) LPs within any of the USMC identified within the Warehouse Module and the Property Accountability (PA) modules or
 
b.  Only with historical and active records pertaining to the warehouse DoDAACs associated with the ICP.  
 
This capability is currently missing from within Material Manager (ICP) module.
 
1.2 ELMS shall display all requested results from the specified search through and online view.
 
1.3 ELMS shall, within the set of data being displayed from requirement 1.2 provide a mechanism to display and or download Key Supporting Documents (KSD).
 
like (receipts, material movements, physical Inventories, Limited Technical Inspections, MROs, Maintenance, etc.).  
 
 
Mission Critical:
 
 
Benefits:
 
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
 
 
Frequency: Daily

 

Users: 

All USMC WH Managers

02159 Denial Transaction (DLMS 945AA6_) Narrative Warehouse,Materiel Management USMC New
Change Request: Process Improvement

Description:
During the creation of a denial transaction (DLMS 945A/A6_), by the Warehouse Module (WM), no reason code or explanation is given to why the denial was produced.  This does not provide the Inventory Manager, working in the Material Management (MM) module enough information as to conduct follow-on action such as back-ordering, filling the requisition from an alternate RSA withing the ICP arena, or canceling the requisition.  It also does not appear that there is a means to search for a denial transactions associated to a specific document number.
 
Recommended:
1.0 ELMS, shall provide an ability for a warehouse person, working the Warehouse Module (WM), to enter a narrative to why a document received a denial during the 940R fulfillment and issue process.
 
1.1 ELMS shall associate the denial narrative directly to the document which it pertains to.
 
1.2 ELMS shall make the document number and the denial narrative available to be search for in the Warehouse Module (WM) and the Material Management (MM) module.
 
 2.0 Once the (DLMS 945A/A6_) has been produced by the Warehouse Module (WM) and sent to the Material Management (MM) module with the denial narrative, ELMS shall provide the Inventory Manage with three option to handle the inbound denial.
 
 a.  Back Order the customer requisition advancing the suffix code to the next available sequence.  In addition, ELMS shall transmit an (870S/AE_) back to the originator of the purchase order.  See attached document, "ME Sourcing Handbook 4.10.24.docx", page 30-33 for the approved USMC status codes authorized for use.
 
 b.  Cancel the customer requisition, ELMS shall transmit an (870S/AE_ ) back to the originator of the purchase order. See attached document, See attached document, "ME Sourcing Handbook 4.10.24.docx", page 30-33 for the approved USMC status codes authorized for use.
 
 c.  ELMS shall provide the Inventory Manager with the ability to attempt to release from another ICP location.  This will be done through the customer requisition mode in the Material Management (MM) module.
 
2.1 ELMS shall provide the Inventory Manager with the ability to select the appropriate backorder or cancellation status using the information provided in the attached document labeled, "ME Sourcing Handbook 4.10.24.docx", page 30-33 for the approved USMC status codes authorized for use.
 
Mission Critical:
 
 
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% accountability of assets
Complies with current audit controls
 
Frequency: Daily
 
Users:
Affects USMC Materiel Managers, WH Managers and ICP
02158 MCPIC Speed to Count Inventory Warehouse USMC New
Change Request: Process Improvement

Description:
MARCORLOGCOM has a requirement to continue what is known as the MCPIC speed-to-count inventory process.  This is a key, “MUST HAVE” capability that was previously missed in the WG3 end-to-end evaluation. The process being addressed has been documented in the attached business process map.  This process differs from the Consolidate Support Program (CSP) containerization MCPIC support interface.  This process used key robotic functionality to optimize the successful execution of an inventory in a significantly reduced time frame.  This process has been a key success point in ensuring we stay audit compliant.
 
Recommended:
 
To ensure all elements of the inventory process is documented and expectation clearly articulated, the following requirements are submitted.  We know that ELMS is currently coded with a robust inventory process that was previously designed to support how the Stock Control System (SCS) required transactional execution.  We ask that all steps and requirements be evaluated within ELMS to ensure stakeholder expectations are met.
 
1.0 During the execution of an inventory, ELMS using the Warehouse Management (WM) module shall provide a mechanism for the warehouse person to select between a MCPIC managed inventory and a manually schedule execution of a location driven cycle count.  
 
Note: A MCPIC managed inventory is one that use automation capability to receive and transfer data automatically.  The physical inventory is conducted using robotics.
 
1.1 After a “MCPIC managed inventory” is selected, ELMS shall conduct a verification to ensure a location cycle count for that same NSN and site has not already been scheduled.
 
1.2 If a “MCPIC managed inventory” already exists, ELMS shall provide a notification and direct the user to the already scheduled location cycle count to begin execution.  Move to 2.3 in the diagram
 
2.0 ELMS shall allow the warehouse person to generate an inventory cycle count.  
 
2.0.1  ELMS shall auto generate a unique cycle count.  
 
2.1 ELMS shall provide a mechanism to the warehouse person to select the type of MCPIC inventory, (Container, NSN, or Location).
Note:  Marine Corps Force Storage Command primary conducts inventory by (site, NSN, and location).
 
2.2 ELMS shall provide a mechanism to the warehouse person to identify if the inventory is part of a plan cyclic inventory or unscheduled inventory (also known as a spot inventory).
 
2.3 ELMS shall freeze all transactional movement of the NSNs that has been identified by the location selected.
 
2.4 ELMS using the agreed upon XML data exchange format, shall generate the required file for transmission to MCPIC.

2.5 ELMS shall transmit, via an API, the XML file staged for transmission.
 
2.5.1 ELMS shall establish a means to verify the transmission was received in its entirety by MCPIC.  
Note:  Steps 2.6 – 2.8 is executed by MCPIC
 
2.9 ELMS shall code the system to accept a reply from MCPIC, via an API where the agreed upon XML formatted is met, that represents the completed results of a cycle inventory count.
 
2.10 ELMS Shall verify all incoming results from a MCPIC inventory for a specified cycle count.  If the balance from the inventory count matches what ELMS has a record for (serial number), then update ELMS with the date inventoried. As part of verification, ELMS will not accept a MCPIC inventory for a date outside the parameter specified in the request to inventory.
 
3.0 ELMS shall provide a mechanism for the warehouse manager to display the results of the, “MCPIC managed inventory”.  
3.0.1 If the results of the inventory indicate an item has been move to a different location, ELMS will conduct a location move to match the MCPIC reported location.
Note:  It is, however, the overall responsibility of the Accountable Officer to conduct causative research when there is an imbalance between what is being reported in ELMS and what was reported by MCPIC.
3.1 ELMS shall provide the Accountable Officer with means to accept the inventory results producing the required DLMS 947I (Inventory adjustment transactions D9A/D8A) when applicable.
Note:  The Accountable Officer must complete the required Financial Liability Investigation of Property Loss (FLIPL) process as prescribe by MARCORLOGCOM policy prior to submitting any adjustment.  This is an administrative item outside of ELMS.
3.2 ELMS shall produce a Money Value Gain and Loss (MVGL) notification statement.  Based on the threshold, the Accountable Property Officer (APO) may be allowed to sign vice the Accountable Officer.
3.2.1 ELMS shall provide the Inventory Certifying Officer with the capability to acknowledge that all MVGLs and FLIPLs have been completed prior to certifying the inventory.  
3.3 After the Inventory Certifying Officer has, within ELMS completed the certification, ELMS shall process all directed adjustments within the system.
3.4 – 4.0  ELMS, coordinating with MCPIC shall develop an automatic way of reconciling location records to ensure synchronization is occurring and maintained.
 
Mission Critical:
 
 
Benefits:
 
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
 
 
Frequency: Daily

 

Users: 

All USMC WH Managers

02157 Physical Inventory at the Enterprise Level Warehouse NECC New
Change Request: Process Improvement

Description:
We are requesting the addition of functionality within the Inventory process to enable users to conduct inventories by Reportable Commodities at the Enterprise level. This enhancement would allow users to schedule inventories for an entire commodity type across a specified Region or Site, thereby improving inventory management efficiency and ensuring timely accountability for assets across broader organizational scopes.
 
Recommended:
 
During the Inventory process, users with the appropriate Region/Site access should be able to select an optional Region/Site on the same interface where they can choose specific Reportable Commodities for inventory. Additionally, an Enterprise Rollup selection feature could be included, enabling users to select an entire Region/Site for inventory at once, streamlining the process and enhancing inventory management capabilities.
 
Mission Critical:
NECCINST 5200.45
 
Benefits:
 
The addition of this capability would empower users to conduct inventories across multiple warehouses or an entire Region/Site simultaneously, significantly enhancing the efficiency and speed of the inventory process.
 
 
Frequency: Daily

 

Users: 

All users who utilize multiple warehouses and the Physical Inventory function.

02156 Adding Attachments to Multiple Records Warehouse NECC New
Change Request: Process Improvement

Description:
We are requesting the implementation of functionality within DPAS Warehouse that allows users to add a single attachment to multiple records simultaneously. Currently, attachments must be added individually to each record, which is highly time-consuming—particularly in scenarios such as uploading identical birth documents to a large number of serialized assets. Enabling batch attachment functionality would greatly enhance efficiency and reduce administrative workload.
 
Recommended:
 
Requesting an enhancement to the current functionality that would allow users to apply the same attachment to multiple records within the Selected Inventory tab under the Inventory Update Manager/User function. This improvement would streamline the process of associating common documentation—such as birth documents—with multiple inventory records, thereby increasing efficiency and reducing administrative burden within asset management workflows.
 
Mission Critical:
In accordance with NECC instruction 5200.45, all supporting documentation must be retained in a centralized repository (DPAS).
 
Benefits:
 
Having this capability will reduce the man hours associated with adding Key Support Documentation to all assets within the NECC Logistics Program, streamline the process and enhance efficiency when managing multiple records that require the same documentation.
 
 
Frequency: Daily

 

Users: 

This functionality would be utilized by the majority of NECC DPAS users who perform receiving, transfer, and issuance operations for all assets required to be recorded in DPAS.

02155 Adding Manage SKO to Inventory Update Manager Warehouse NECC New
Change Request: Process Improvement

Description:
We are requesting enhanced functionality within DPAS to allow for the replacement of SKO components or the modification of their condition codes in a more timely and efficient manner. At present, users are limited to two options: either route the SKO through the QA/QC process or fully disassemble the SKO, update condition codes or replace components, and then reassemble it. This process is time-consuming and introduces unnecessary operational delays.
 
Recommended:
 
Integrating the existing Manage SKO functionality, currently utilized within the QA/QC process, into the Inventory Update Manager would streamline workflows and reduce processing time for users when performing component swaps or updating condition codes.
 
Mission Critical:
In accordance with NECC instruction 5200.45, all SKO assemblies need to be updated regularly to maintain inventory accuracy and material readiness status
 
Benefits:
 
Implementing this capability will significantly reduce the man-hours required to replace SKO components or update their condition codes, thereby increasing overall efficiency and minimizing resource expenditure.
 
 
Frequency: Daily

 

Users: 

This functionality would be utilized by the majority of NECC DPAS users who perform receiving, transfer, and issuance operations for all assets required to be recorded in DPAS.

02154 Allocation Mgmt - Add Location field NECC New
Change Request: Process Improvement

Description:
At present, the Allocation Management Search Criteria functionality allows users to search for various types of allocations associated with specific assets. However, users have expressed the need for enhanced search capabilities, specifically the inclusion of a Location field. This addition would enable users to filter and identify items that are allocated within a designated location, thereby improving the efficiency and accuracy of allocation searches.
 
Recommended:
 
Add a Location field to the Search Criteria within the Allocation Management functionality to allow users to filter results based on specific allocation locations.
 
Mission Critical:
NECCINST 5200.45
 
Benefits:
 
Adding this search field will help in searching for allocations within a specific location.
 
 
Frequency: Daily

 

Users: 

This functionality would be utilized by the majority of NECC DPAS users who perform receiving, transfer, and issuance operations for all assets required to be recorded in DPAS.

02153 Commodity Type Field Add in SKO Catalog Warehouse NECC New
Change Request: Process Improvement

Description:
When accessing assets within the SKO Catalog, users are currently unable to directly verify the appropriate reportable commodity associated with each item. As a result, users must first navigate to Catalog Management > Stock Number to obtain the necessary commodity information. Once the appropriate commodity has been identified, users must then return to the SKO Catalog to update the assembly accordingly—completing this process on a line-item-by-line-item basis. This additional step ensures that all entries are accurately aligned with their respective commodity classifications.
 
Recommended:
Implement the addition of the appropriate reportable commodity type for each component within the SKO. This information can be integrated either as an additional column in the existing layout or as an optional field within the grid options.
 
Mission Critical:
COMNECC/COMNECCPACINST 5200.45.
 
Benefits:
 
Incorporating this enhancement will streamline the process of verifying and updating assemblies, reducing the need for cross-referencing within the WH module.
 
 
Frequency: Daily

 

Users: 

All users required to verify the components of the SKOs within their respective inventories to ensure accuracy and compliance.

02152 Refactor ICP Report Requirement Materiel Management USMC New
Change Request: Process Improvement

Description:
LIN/TAMCN, Stock Number, and ICN Reports are not available within the Material Management Module. Duplicate and modify the ICN enterprise view, currently in the Warehouse Module, into the Material Management (ICP) module. Material Managers need the ability to select an NSN and or serial number. The return results should display a complete enterprise view of all specified required information. Returned selection should have at a minimum, the following key elements. (TAMCN, NSN, Warehouse DoDAAC, Condition Code, Purpose Code, Available to Issue, allocated (by Type Allocated), In Maintenance quantity, Intransit quantity, quantity in an exception status), due in quantity.
 
Recommended:
1.0. ELMS, from within Material Management (ICP) module, using the MM Inventory inquiry process, shall provide an Inventory Manager (IM) the ability to search by the addition data elements of LIN/TAMCN and Serial Number.
 
1.1.  ELMS, from within Material Management (ICP) module, using the MM Inventory inquiry process, shall provide an Inventory Manager (IM) with the ability to select from the options grid the following elements to be displayed at a minimum:
 
    a.  LIN\TAMCN (currently present)               i.  Inventory Total Qty (currently present)
    b.  NSN  (currently present)                          j.  Inventory Available Qty (currently present)
    c.  RSA DoDAAC (currently present)           k.  Allocated to MRO Qty (new required element)
    d.  RSA RIC  (currently present)                   l.  Intransit Due-In qty (new required element)
    d. Condition Code (currently present)          m.  Serial Number (new required element)
    e. Purpose Code (currently present)
    f.  Project Code(currently present)
    g.  Stocking UI Price (currently present)
    h.   Extended Price (currently not calculating)
 
Mission Critical:
 
 
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
 
Frequency: Daily

 

Users: 
02151 Material Redistribution (MM) Process Corrections Materiel Management USMC New
Change Request: Process Improvement

Description:
During MARCORLOGCOM’s review of current ELMS processes within the Material Management (ICP) module, it was discovered that system is incorrect selecting and displaying inventory records not within the scope of the redistribution request. This process of incorrect selecting and displaying data lends itself to the Inventory Manager selecting invalid data resulting in inventory mismatches and transactional denials.  This also created unnecessary denials leading to inventory requests.
 
Recommended:
1.0 In the Material Management (ICP) module, when an Inventory Manager is creating a new “Redistribution Order”, ELMS shall not automatically create the 527D/DW_ transactions until after the Inventory Manager completes the MRO 940R/A5_ request. (see attached document)
 
1.2 Currently, during the creation of the “Redistribution Order” the system returns the user first to the main results gridline.  This forces the Inventory Manager to locate and select the document being worked prior to completing the 940R/A5_ process.  Much like the “Customer Requestion” process in ELMS, the system shall proceed directly to the 940R/A5_ entry screen without returning first to the main results gridline. (see attached document, image 1.1 and 1.2)
 
1.3.  When initiating a “New Redistribution Order” in the Material Management (ICP) module, if a Condition Code is selected and there is no on hand available assets to issue anywhere in the associated ICP, the system shall provide a popup alert to the Inventory Manager stopping the process and allowing the Inventory Manager to select a Condition Code that is appropriate to support the redistribution.  (see attached document, image 1.0)
 
2.0 Currently, when creating the Material Redistribution order 940R/A5_, all Condition Codes and Purpose Codes are populated and displayed in the selection grid.  When creating a 940R/A5_ Material Redistribution release order, in the Material Management (ICP) module, the system shall only display the Condition Code, associated Purpose Codes, and inventory with on hand available quantities matching the original Condition Code and Purpose Code selected.  (see attached document, image 1.5)
 
Mission Critical:
 
 
Benefits:
Meets MARCORLOGCOM's business model
Assists in 100% Accountability of assets
Complies with current audit controls
 
Frequency: Daily

 

Users: Materiel Managers and ICP users affected
02150 Include PSD Id in TPF Transactions PA,Materiel Management ASA-ALT New
Change Request: Process Improvement

Description:
The Army's Decision Support Tool (DST) is the system that tracks new equipment fielding and when they are to occur.  Each fielding is assigned a PSD Id to each each equipment fielding.  Currently the PSD Id is not included in the DLMS transaction to denote why the equipment is being sent to a Unit.  The proposed improvement is to have ELMS provide for the input of the PSD Id into the PA Disposition Transfer Out and into the MM Customer Requisition processes enabling the value to be included in the DLMS transactions.  See also ELMS SCR 01938
 
Recommended:
1. Modify MM Customer Requisition to provide for input of the PSD Id.
2. Modify PA Disposition to provide for the input of the PSD Id.
3. Include the PSD Id in the DLMS 527D (PMR) and DLMS 856S (Shipment Status) transactions sets within the Reference Identification loop using the PWC qualifier.
 
Mission Critical:
Provides 100% confirmation to DST that the fielding has occurred.
 
Benefits:
Provides visibility that a fielding is being planned via the 527D.
Provides 100% validation that the planned fielding occurred enabling DST to be able to close the fielding systematically.  
 
Frequency: Daily
 
Users: All users that issue/transfer materiel to users of GCSS-Army.
02149 Option to print DD 1348 before disposal is approved Warehouse ASA-ALT New
Change Request: Process Improvement

Description:
When creating a disposal action within the DPAS WM module a DD 1348 can't be printed until the disposal is approved by the "Warehouse Manager and the "COR". For the COR to approve a disposal action they should verify that all signed documentation is uploaded in DPAS before approving the action. Since the DD 1348 can't be printed until after the COR approves the disposal the users are having to create the DD 1348's outside of DPAS. This can cause issues with data accurate since the users can't allow the system to generate the information. This also increases the time it takes to complete the transaction.  
 
Recommended:
Allow the DD 1348 to be printed before the COR has to approve the transaction but after the "warehouse manager" has given the first approval.
 
Mission Critical:
The process must be flexible to support the business.  This change will enable greater flexibility.
 
Benefits:
The DD 1348 will no longer have to be created outside of DPAS therefore the time to complete the action will decrease and the data on the DD 1348 will be in sync with the information that has been stored in the DPAS WM module.
 
Frequency: Daily
 
Users: All
02148 DCAPES interface for FSM FSM DAF New
Change Request: Process Improvement

Description:
Currently Authorization managers must input readiness code 'A' authorizations into FSM either via Mass update or manual input. In some cases the Unit Type Code (UTC)s and Auth details in FSM do not match the UTCs in the authoritative system which causes mismatches between the systems and requires manual intervention.
 
Recommended:
Establish an interface to the authoritative system Deliberate and Crisis Action Planning and Execution System (DCAPES) to limit or eliminate manual intervention. The DCAPES PMO also has a requirement for their system to accommodate this requirement
 
Mission Critical:
Removes the manual process of establishing readiness code 'A' requirements. Additionally this will resolve a recent AFAA audit finding, that identified mismatches in FSM from the authoritative database with regard to UTC requirements
 
Benefits:
By leveraging the direct interface we remove the manual process and remove the requirement to reconcile the data from both systems.
 
Frequency: Daily
 
Users: Existing UTCs are validated biennially, currently there are over 160K UTC tasked authorizations
02147 NSN COG Information Warehouse Navy New
Change Request: Process Improvement

Description:
Currently the COG information does not import from FLIS nor is there a field for the COG.
 
Recommended:
Allow the COG to import from FLIS and add that field to DPAS records.
 
Mission Critical:
 
 
Benefits:
We track the COG for our equipment for reporting purposes.  It will allow us to continue that process.
 
Frequency: Daily
 
Users: 100+ Users
02146 Inventory Status Warehouse Navy New
Change Request: Process Improvement

Description:
There is not a way to track status of an inventory.
 
Recommended:
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.
 
Mission Critical:
 
 
Benefits:
Allows for a way to track inventoried and to be inventoried locations for a selected date range.
 
Frequency: Daily
 
Users: 100+ Users
02145 PROJECT POC Warehouse Navy New
Change Request: Process Improvement

Description:
Unable to determine the project POC from the Project table.  You can only view it by editing the project code.
 
Recommended:
Add the project POC information to the grid options of the project table.
 
Mission Critical:
 
 
Benefits:
Allows the user to view the project POC.
 
Frequency: Daily
 
Users: 100+ Users

 

02144 Project Field Character Increase Warehouse Navy New
Change Request: Process Improvement

Description:
Current field is only three characters. With the size of our structure we need to increase the number of characters from three to ten.
 
Recommended:
Increase the number of characters from three to ten.
 
Mission Critical:
Increasing the Project Code will prevent the duplications of project numbers.
 
Benefits:
Increasing the Project Code will prevent the duplications of project numbers.
 
Frequency: Daily
 
Users: 100+ Users
 
 
Removed 04/29/2025 - per email from Justin Smeltzer - Project Code is a DoD Standard Element
02143 Maint Mgmt Assignment by Custodian Nbr PA,Materiel Management USAF New
Change Request: Process Improvement

Description:
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.  
 
Recommended:
Provide capability to bridge/ unbridge by Custodian Number's. Adding MGID characteristic to Custodian Number's.
 
Mission Critical:
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.
 
Benefits:
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.
02142 Inclusion of TFSMS Attribute Data in the Enterprise Catalog PA,MU,Warehouse,Materiel Management USMC New
Change Request: New System Process

Description:
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.
 
Recommended:
 
1.0  The ELMS system shall include in it interface with the Marine Corps TFSMS system the following key attributes used to minimally assist in identification and defining controlled Class VII inventory:
 
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.1.1 At no time shall the system provide the Inventory Manager with the ability to select and alternate asset that is in Achieve (AR) status.
 
2.2  At the time of substitution, the Inventory Manager shall be provided with the capability to chose a replacement NSN with a different Condition Code and Purpose Code availability.  
 
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.
 
 
Mission Critical:
 
 
Benefits:
  • Meets MARCORLOGCOM's business model
  • Assists in 100% accountability of assets
  • Complies with current audit controls
 
Frequency: Daily
 
Users: Affects all USMC users