Unlike submitted Support help tickets, System Change Requests (SCR's) can only be submitted through your organization's appointed and authorized ELMS CCB member representatives, or otherwise if no CCB representatives have yet been appointed, your Primary Information Owner appointee. If you are unsure of who your organization's appointed ELMS CCB member representatives or Primary IO are, you may email the ELMS Support team to request that information:
To learn more about the process, please visit our CCB Responsibilities and Meetings page. Below you will find all SCR's that have been submitted, and what their status is. To download a blank form, you may visit our Reference Library and download the SCR Form.
Utilize the search filters below to narrow your results by keywords, module, or state. You may also request an Excel file of all the SCR data by contacting the Help Desk.
| Found: 1779 Result(s) | Show: |
| Title |
ELMS Module |
Reporting Org |
State |
Description |
Action |
|
|---|---|---|---|---|---|---|
| 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:
Mission Critical:
In accordance with NECC instruction 5200.45, all supporting documentation must be retained in a centralized repository (DPAS).
Benefits:
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:
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:
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:
Mission Critical:
NECCINST 5200.45
Benefits:
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:
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)
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
|
Disclaimer | Accessibility