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 |
|
|---|---|---|---|---|---|---|
| 01856 | Eliminate DLMS 870s for TPFs | Materiel Management | Army: ASA(ALT) | Done | Change Request: Process Improvement
Description:
ASA(ALT) utilizes the Materiel Mgmt. module to perform Total Package Fieldings (TPFs). When a push customer requisition is entered / approved, DPAS will generate / send a DLMS 870S Supply Status along with a DLMS 527D Prepositioned Materiel Receipt to the recipient of the intended recipient of the materiel. The DLMS 527D is determined by the customer profile while the DLMS 870S is automatic as if the push order was a pull order with DPAS responding to the receipt of a DLMS 511R. Army is encountering an issue when the DLMS 527D is not transmitted (customer profile incorrectly established), or when the 527D is rejected by GCSS-Army. When the DLMS 527D is not received / processed and a DLMS 870S is received, GCSS-Army will establish a Due In and transmit a DLMS 511R to National for the purchase of the materiel that is to be provided by the PEO/PM.
Recommended:
Army is requesting that DPAS not generate DLMS 870S Supply Statues for TPF type orders. The Supply Status is not needed and results in the generation of an order when there isn't one desired. All TPF activity is supported by the DLMS 527D Prepositioned Materiel Receipt (PMR). Should the PM change the qty or cancel the order DPAS sends the change via an updated PMR (DLMS 527D).
Mission Critical:
This functionality is needed to prevent unwanted orders being generated to national when the DLMS 527D prepositioned receipt is not received / processed.
Benefits:
This change will eliminate unwanted orders being systematically generated by GCSS-Army.
Frequency: Daily
Users:
This feature will be utilized by the ASA(ALT) PMs in fielding of the next generation of equipment to the U.S. Army and by USSOCOM for push orders to their customers.
Completed – Release 2023.2.1 – 07 April 2023
|
|
| 01855 | DPAS Sub-Warehouse / Shop Code and DLMS | Warehouse | Leidos | Done | Change Request: Process Improvement
Currently each DPAS warehouse is required to have a unique RIC (Mandatory when external reporting is required) and / or DoDAAC. This value is used for routing DLMS transactional data between DPAS Warehouse Mgmt. and DPAS Materiel Management Mgmt. modules and to / from external systems. There are times where a DPAS Customer has an organization that has a requirement for multiple warehouses to manage different commodities that is not desired to have them commingled e.g. spare parts, tool crib, un-issued materiel with no avenue to acquire additional RICs. Note: The Department is running out of 3 character RICs with plans to replace the RIC with DoDAAC once logistics system are fully DLMS compliant (eliminate support for MILS format).
The proposed change will have DPAS implement the Planning / Maintenance Organization (Shop Service Center) name value as part of the warehouse business key. By including this value, DPAS will be able to use this value along with a RIC / DoDAAC to route DLMS transactions enabling an organization to have multiple warehouses without having each of them having a unique RIC / DoDAAC.
This change will enable an organization to have multiple DPAS warehouses which will enable them to have multiple Tool Cribs, Parts/Supply Rooms, Issuing locations, etc.
This SCR is identified as phase 1 of the DPAS effort to add flexibility to its Warehouse Mgmt. module. With this change DPAS customers will be better able to manage its different types of inventories / different physical locations within an organization. Additional efforts are planned to provide greater flexibility in configuring a DPAS warehouse.
Currently SPECWARCOM and the Air Force has multiple warehouse requirements within a organization.
Partially Completed – Release 2023.1.1 – 13 January 2023 Partially Completed – Release 2023.1.2 – 27 January 2023 Partially Completed – Release 2023.3.1 – 17 July 2023 Partially Completed – Release 2023.3.6 – 22 September 2023 Partially Completed – Release 2023.4.4 – 17 November 2023 Partially Completed – Release 2024.1.2 – 26 January 2024 Completed – Release 2024.1.4 – 23 February 2025 |
|
| 01854 | nformation Owner User Account Request Submission | Enterprise | Leidos | Done | Change Request: Process Improvement
DOD has issued an updated DD Form 2875 that requires changes to the DPAS validation / import process. With the increased number of users to manage, to have DPAS personnel preform the validation, then report the error(s) to the security POC delays a new user in receiving an account. The proposed improvement is to provide capability for Information Owners that have an active DPAS account to perform the validation enabling DPAS to provide immediate feedback to the information owner as to what needs to revised, and the change would enable the information owner to submit the validated DD Form 2875 for processing.
DOD has issued an updated DD Form 2875 that requires changes to the DPAS validation / import process. With the increased number of users to manage, to have DPAS personnel preform the validation, then report the error(s) to the security POC delays a new user in receiving an account. The proposed improvement is to provide capability for Information Owners that have an active DPAS account to perform the validation enabling DPAS to provide immediate feedback to the information owner as to what needs to revised, and the change would enable the information owner to submit the validated DD Form 2875 for processing.
DOD has issued an updated DD Form 2875 that requires changes to the DPAS validation / import process. With the increased number of users to manage, to have DPAS personnel preform the validation, then report the error(s) to the security POC delays a new user in receiving an account. The proposed improvement is to provide capability for Information Owners that have an active DPAS account to perform the validation enabling DPAS to provide immediate feedback to the information owner as to what needs to revised, and the change would enable the information owner to submit the validated DD Form 2875 for processing.
Allow more efficient account creation and modification for both customers and account management staff.
DPAS processes 1000s of DD Form 2875 yearly.
Partially Completed - Release 2023.1.2 Partially Completed - Release 2023.1.4 Partially Completed - Release 2023.1.5 Partially Completed - Release 2023.1.6 Partially Completed - Release 2023.2.1 Partially Completed - Release 2023.2.5 Partially Completed - Release 2023.2.6 |
|
| 01853 | Additional Details for FSM Auth On-Hand Report | FSM | AF: A4/HAF FH-AFHAF | Done | Change Request: New System process
Description:
Current FSM Auth On-hand report does not auto populate the the Master NSN in the NSN column when running a report with the Interchangeable or Substitute NSN. Additionally FSM Auth on-hand capability can only be submitted as report and limits filtering data elements to only being able to run a report one NSN at a time. The current 'work around' is to run a report at either the MAJCOM, AUIC, UIC level to see all the NSN. UIC selection requires the user to scroll to find the UIC they
Recommended:
Populate the Master NSN in NSN column, regardless if the inquiry is for the Interchangeable or Substitute NSN. Include in the Pop-up screen for the search stock number a notice if the NSN is a Interchangeable or Substitute to a Master NSN. Allow to run reports for multiple NSN, UICs, Auth-id etc. Include intelliSense capability for all search by data elements
Mission Critical:
Current process is limited and requires more robust capabilities
Benefits:
This will provide the DAF the capability to make data driven decisions for the management and oversight of Support Equipment.
Frequency: Hourly
Users: [blank]Completed – Release 2023.3.4 – 25 August 2023 |
|
| 01852 | Modification of LIMS-EV interface to support M&U changes | MU | Leidos | In Progress | Change Request: Process Improvement
Description:
With the modernization of M&U, in addition to asset linkage between PA and M&U, user can direct input asset into M&U and there will be an eventual asset linkage between WM and M&U. To support these changes along with supporting a micro-service framework, the linkage of the Maint. Asset Master / Work Orders are no longer a direct association to Asset Master. Reference DPAS Ticket Nbr - 78525
Recommended:
Modify the LIMS-EV interface to incorporate an Equipment Master view and modify the linkage between various other LIMMS-EV views to utilize the Equipment Master view.
Mission Critical:
DPAS change how Maintenance records are linked to their source.
Benefits:
This is considered a mandatory change in order to maintain data integrity within the LIMS-EV views.
Frequency: Hourly
All consumers of the LIMS-EV interface data. Currently this is AF Discovery and DoD Advana.
Partially Completed – Release 2023.4.4 – 17 November 2023 |
|
| 01851 | Impound Asset Manager | MU | USAF: AvSE | Done | Change Request: New Role Design
Description:
Problem: Not currently able to lock down an asset in DPAS M&U when asset is impounded as directed by DAFI 91-204, Safety Investigations and Reports. This inability allows for the potential of users to change/update asset information in the system while the asset is still under investigation, causing a major safety and records management issue.
Recommended:
Create a new Impound Official role within DPAS M&U and add a check box to the Maintenance Asset Master screen labeled as "Asset Impounded". Selection of this check box by an authorized person will "lock out" all other users and lock all asset history while the asset is impounded. Once asset is released from impound, an authorized user will unlock this asset and it will be available for normal use/maintenance. Limit use of the new Asset Impounded check box to only the newly created Impoundment Official role.
Mission Critical:
Mandated by DAFI 91-204, Safety Investigations and Reports, and DAFI 21-101, Aircraft and Equipment Maintenance Management.
Benefits:
The addition of this role will allow for proper control and integrity of asset historical data within DPAS M&U and will make DPAS M&U compliant with Aircraft/Equipment impoundment procedures. This additional role and ability will also address safety concerns, by not allowing use when an asset condition is questionable or under investigation.
Frequency: Monthly
Hard to measure, possibly several times a month.
Partially Completed - Release 2024.4.3 - 01 November 2024
Partially Completed - Release 2024.4.4
Partially Completed - Release 2024.4.5
Completed - Release 2025.1.3 |
|
| 01850 | Add SubWO Fields to WO Search Results Grid | MU | USAF: AvSE | New | Change Request: Process Improvement
Description:
Problem: Currently when users search Work Orders, the results that populate do not give specific enough information on what the Work Order is for.
Proposed Improvement: Addition of Sub-Work Order specific columns to Work Order search results grid. Recommended:
Add an additional option to display Sub-Work Orders for each Basic-Work Order. Include fields that display Requested Service and Work Order Description.
Mission Critical:
(Not Provided)
Benefits:
The addition of these fields will save users time and aggravation, as when they are searching for a specific Work Order they are searching for the narrative of the work to be accomplished (i.e., 6 Month Inspection). The average user will not know the Work Order Reason, Work Order State Code, or Work Plan Type Code. Therefore, if there are several open Work Orders on a single asset (a common occurrence), users will have to click on all the search results until they find the specific Work Order they are looking for, this proposed improvement will solve that issue.
Frequency: Hourly
This function will be used by all AvSE users in DPAS M&U thousands of times a day. |
|
| 01849 | Authorized On-Hand Qty | Warehouse | Navy: NECC | Done | Change Request: New Process
Description:
DPAS currently has high and low limits for stocking, but we would not want to affect those fields for inventory management purposes. NECC has a need for a data field that captures the allowance authorized per stock number / SKO at the Warehouse/ DoDAAC /UIC Level.
Recommended:
NECC would like to add a field in our Logistics Program that captures the Authorized Allowance Quantity (We might label the Field as "TOA" for simplicity for our Force) by Stock Number/SKO that we are able to edit at the LP Level only. The ability to set that and for it to appear on the ICN report would be a huge impact to our understanding of mission needs.
Mission Critical:
Multiple documents approved by OPNAV grant allowances for equipment to our commands based on Required Operating Capability and Projected Operating Environments (ROC/POE). These requirements build our Table of Allowance (TOA) and are a movable target as missions change and equipment gets refreshed.
Benefits:
The benefit is cost savings for identifying excess/shortages of materiel across our force and having better data for our leadership to make better risk and business decisions.
Frequency: Hourly
At this level we would expect the commodity managers at NECC to monitor and maintain these TOA levels in DPAS as well as the Property Book Office. Estimate 10 personnel would need access to monitor and maintain this field.
Partially Completed – Release 2023.2.5 – 02 June 2023
Completed – Release 2023.2.7 – 30 June 2023 |
|
| 01848 | Enable Kit Assembly Substitution Items | Warehouse | Army: ASA(ALT) | New | Change Request: Process Improvement
Description:
DPAS has the capability to manage configured kits, but currently does not provide for the capability to complete the kit using valid substitute items. The DPAS Kitting process should provide the capability to utilize substitute items to create managed kits.
Recommended:
1. Modify the SKO Catalog for managed kits to denote whether a substitute item is authorized to be used for the item in the kit.
2. Provide for the selection of substitute items for creating a kit when a substitute is authorized.
3. The completed kit form that lists the items in the kit should display the planned kit item with an annotation that the kit was assembled using the identified substitute Item.Mission Critical:
This functionality is needed as the planned item is not always available when a fielding occurs, thus the PM must utilize valid substitutes.
Benefits:
This change will enable kit fielding to occur of Kits when substitute items are used and inform the user that the kit was assembled using one or more substitute items.
Frequency: Weekly
This feature will be utilized by the ASA(ALT) PMs in fielding of the next generation of equipment to the U.S. Army. It is believed that other DPAS users that are managing kits would benefit by having this functionality as all Services support the concept of substitutes. |
|
| 01847 | Kit Assemble Enable Ad Hoc Items Addition | Warehouse | Army: ASA(ALT) | In Progress | Change Request: Process Improvement
Description:
There are times when there is a need to add addtional items to a managed kit. Today, DPAS provides the capability for managed kits to be considered a complete kit when items are missing, but DPAS does not provide the capability to add additional items to a managed kit. The DPAS Kitting process should provide the capability to add additional items (items not listed in the SKO catalog) to a managed kit.
Recommended:
1. Modify the SKO Catalog for managed kits to denote whether additional items are authorized to be included in the kit.
2. Provide for the selection of additional items during the Kit build/update phases when the kit authorizes additional items to be included.
3. The completed kit form that lists the items in the kit should display the additional items and denote that these items are additional items (not part of the standard kit configuration).Mission Critical:
This functionality is needed as often times the Army has are requirement to provide additional items in a kit.
Benefits:
This change will enable kits to be assembled with more items than the SKO catalog identities.
Frequency: Weekly
This feature will be utilized by the ASA(ALT) PMs in fielding of the next generation of equipment to the U.S. Army. It is believed that other DPAS users that are managing kits would benefit.
Partially Completed - Release 2024.4.3 - 01 November 2024 |
Disclaimer | Accessibility