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 |
|
|---|---|---|---|---|---|---|
| 01766 | MU Data Field Suppression for Boats/Craft | MU | NSWC-SPECWARCOM | Done | Description:
Many of the data fields displayed in MU Work Order/Sub Work Order screens are not used by NSW for recording boat/craft maintenance actions. The presence, and in some cases required entry, for unused data fields results in numerous additional man-hours for NSW MU users to record boat/craft maintenance.
Recommended:
Recommend suppression of data fields listed in attached excel file or creation of separate MU "Boats/Craft" view that only includes NSW required data fields.
Mission Critical:
Implementation of this SCR is mission critical in improving the efficiency of MU for use with NSW boats/crafts in order to permit full implementation.
Benefits:
Reduces man-hours required for entry of boat/craft maintenance actions.
Users:
All current NSW MU users.
Partially Completed – Release 2023.3.2 – 28 July 2023
Partially Completed – Release 2023.4.5 – 01 December 2023 |
|
| 01765 | SKO Inventory Display Order | MU | Air Force | New | Description:
The DPAS warehouse module does not allow SKO inventory displays in a logical order. User must maintain tool (item) accountability via preforming inventory reviews. Displaying proper order or toolbox drawer sequence is necessary for streamlining time and maintaining accurate inspections.
Recommended:
Add grid option for display order within the warehouse inventory.
Mission Critical:
Air Force policy requires maintenance activities to establish tool accountability programs to prevent Foreign Object Damage (FOD) on our multi-billion-dollar aircraft. The Tool Crib custodian conducts joint inspections with receiving members during initial issue and annual thereafter or as needed. Additionally, members must conduct daily reviews and weekly spot checks. Lost tool identification is critical to preventing FOD and protecting our ability to fly, fight and win.
Benefits:
Display order reduces time to preform an inspection. Improves accuracy identifying drawer location with reference to tool.
Users
This affects all Agency's and we believe this function will benefit all. |
|
| 01764 | GSA Fuel Upload | MU | Air Force | New | Description:
The M&U module currently blocks GSA Fleet upload file transactions when an asset’s mileage exceeds a 20% variance from the last reported utilization. This generates a large number of manual utilization updates into smaller input increment to correct records within the variance and allowing GSA Fleet file upload. Additionally, system does not provide clarity with reference to validation errors. Users must sift through 1,000s of line-items before pinpointing flagged fields, only to update a separate Excel file for reload.
Recommended:
Update the utilization GSA Fleet upload file process. At what we reference as Step 5 (Update Step) of the upload process, system flags errors for 20% mileage variance. However, update allowing users to continue file upload after reviewing and accepting. We call this a soft stop with a continue button. This is similar to current single utilization update process. Additionally, all other data issue flags (i.e., not 20% variance), highlight rows containing errors and allow corrections within what we reference as Step 4 (File Validation) step. This streamlines utilization upload process and reduces user frustration searching, correcting and updating 1,000s of line items.
Mission Critical:
Critical. Properly capturing accurate utilization is an OSD mandate for FAST reporting and influence executive-level decision making. Agencies used data to develop procurement and sustainment budgets across the DoD. Streamlining interface allows users to focus on data accuracy vs. fighting system.
Benefits:
Implementing these process improvements dramatically improves overall GSA asset utilization accuracy. Increasing the success rate of file upload reduces user manual updates thus reducing workload and saving time.
Users
Improvement benefits all DoD Agencies |
|
| 01763 | Mass Template-Void Option | MU | Air Force | Removed | Description:
The M&U module prevents users from VOIDing work orders within Mass Template function. Incorporating VOID function option within Mass Template allows users to streamline DPAS workload into a single screen view work process. Current work order VOID process is a one work order at a time process and extremely time-consuming. The system auto-generates inaccurate or erroneous work orders at an exponential rate outside of user error. Additionally, system does not allow ease-of-use removing the 1,000s of line items cluttering the the user's interface. A Mass Template VOID option aids reducing system generated workload on the users.
Recommended:
Add VOID option to Work Order Status Cd within Mass Template.
Mission Critical:
Critical. The ability to properly manage an agency's fleet management information system is paramount to executing daily fleet actions. Cluttering system with unnecessary work orders as open actions reduces ability to effectively control workload production and report mission capability.
Benefits:
Adding VOID option within Mass Template reduces user's task-time 75%. Current process takes ~20 minutes to execute, Mass Template reduces timeline under 5 minutes.
Users:
Affects all Component/Agency users
25 January 2023 – cancelled per Tim Thompson |
|
| 01762 | Provide support for multiple Customer Profiles | Enterprise | Leidos | Done | Description:
The current Customer Profile process in Materiel Mgmt. support a single profile / customer. There is a requirement to support multiple profiles based upon the type of materiel being pushed. For example: Equipment Fielding requires a different Distribution Code than Operating Materiel and Supplies. The Customer Profile process is also difficult to manage given that the Customer Profile records must be created for each ICP. For the Army PEIO ICPS, they are all the same.
Recommended:
1. Add a Customer Profile Type "dropdown" to the customer profile process and to the Customer Requisition Add process to enable the user to select the profile required to support the requisition. Initial drop down should be populated with: PPE - Plant Property & Equipment and OM&S - Operating Materiel & Supplies. Consider creating customer profiles by "Collection" with each ICP being able to define the "Collection" of Customer Profiles they wish to use, thus enable each ICP to have their own collection, or allow the Army PEOs to use a single collection (similar to how catalogs are aligned at the PA Site level).
Mission Critical:
GCSS-Army is to implement a change in Aug 2022 to enable fielding of OM&S. The user will be able to modify/update the Distribution Code in the requisition screen, but the chance of error to not input or update it to the correct value is high.
Benefits:
Ideally this change would improve the fielding process for ASA(ALT) allowing them to store/select multiple profiles / Customer (DoDAAC), thus reduce input and chance of error.
Users:
All uses who perform push requisitions will benefit by this change.
Completed – Release 2023.3.3 – 11 August 2023 |
|
| 01761 | Deferred Parts Deletion | Warehouse | Air Force | New | Description:
Current system process prevents user from deleting part request within Warehouse when deferred part is no longer needed. After disassociating the record in MU, the Maint issue for deferred part is still visible to user within Warehouse module. Fully deleting deferred request from the system requires a Helpdesk ticket submission for backend script execution.
Recommended:
Enable user-level delete function after disassociating all records from the deferred allows users to select "Delete" clearing warehouse and ensures accurate warehouse management and proper user visibility.
Mission Critical:
The ability to delete part request removes excessive workload within Maint issue, eliminates user confusion on assets pending part and provides mission enhancement within the Warehouse module
Benefits:
Improves accuracy and accountability of Warehouse operations, streamlines Maint issue and prevents erroneously issuing part to asset.
Users:
Affects ALL users within our Component/Agency. |
|
| 01760 | Annual user audit functionality added to DPAS | Enterprise | Leidos | New | Description:
DPAS does not currently have the ability to internally track the annual user audit conducted each year by the Information Owners (IOs) and their Alternates (AIOs).
Recommended:
Provide ability within DPAS for IOs/AIOs to complete their Annual user audit that meets all SSAE requirements. Allow for a way to track that their Org has run their necessary user listings (SCR 01731 in process for user listing functionality across all modules) but also provide them a checklist they can complete and certify that includes verifying: users completion of DoD CA training, user roles and tier access is correct or has been updated accordingly, any personnel removals have been completed, all inactive or terminated accounts have processed correctly, and all risk for incompatible duties within DPAS operations have been mitigated. Internal DPAS Security Officers will need the ability to run a report that shows status of the Annual User Audit to assist us with whom has and has not completed the audit so that we can reach out to assist and well as know which groups may need accounts put into suspense if there is no completion.
Mission Critical:
Yes, this is mission critical to assist with the annual requirement to monitor, review and audit users and their access. This supports our SSAE audit readiness.
Benefits:
Reduce time spent on manual tracking of Annual user audit. Improve the accountability and tracking of the audit process and supports the SSAE.
Users:
All users are affected by the Annual user audit. |
|
| 01759 | Adding Information Owner (IO) tracking into DPAS | Enterprise | Leidos | New | Description:
Currently Information Owners (IOs) and their Alternates (AIOs) are tracked manually in a spreadsheet which is stored on SharePoint. The spreadsheet is then loaded into a stand alone database for IO validation during review of user packets. To provide a more sound and efficient process as well as help to support our SSAE, IO tracking needs to be moved into the DPAS System. (We will have to look at how to still be able to have up-to-date validation during user account processing)
Recommended:
Add IO table to DPAS that can track all pertinent information currently tracked on manual spreadsheet with ability to run IO queries and reports from the system. Create a way to make the appointment processing more efficient and automated vs. current manually intensive process.
Mission Critical:
Yes, this is mission critical to assist Commands being able to efficiently process their Information Owner and Alternate appointments, give query and reporting ability as well as help us to support our SSAE audit readiness.
Benefits:
Reduce time spent on manual processing, maintenance and update of IO listing, Improve the accountability of our IO Listings for SSAE. Give query/reporting ability to assist DPAS Security, DPAS Support and help us overall provide better support our customers in a more organized, efficient and data safe process.
Users:
This affects the tracking of all Information Owners and their Alternates across all services that are appointed for DPAS. |
|
| 01758 | Manufacturer Part Nbr on Stock Number AUD, and MPN Tech Refresh | Enterprise | Leidos | Done | Description:
When DPAS Stock Numbers that are type B-Part Number are used in DLMS transactions,the CAGE and Manufacturer Part Number are required in the DLMS transaction. Currently, multiple manufacturer records are allowed to be associated to these stock numbers, making the DLMS transactions unable to discern the correct manufacturer record to apply to the transaction. In addition, the manufacturer part number AUD screens will be upgraded as part of the DPAS tech refresh effort. The proposed improvements include these: 1) add the necessary manufacturer fields to the stock number add/update screens when stock number is type B-Part Nbr 2) enforce a 1:1 association between stock number and manufacturer part number records when the stock number is a type B-part number 3) Update existing data records that are currently type B-Part Number with > 1 associated manufacturer to type J-MCN as local stock numbers (with approval from affected users) and clean up manufacturer data that will not fit into the 1:1 association, or assign stock numbers and assets to one associated manufacturer 4) Add manufacturer search fields to the Internal Stock Number browse so users may search for a stock number by the associated manufacturer data
Recommended:
1) add the necessary manufacturer fields to the stock number add/update screens when stock number is type B-Part Nbr 2) enforce a 1:1 association between stock number and manufacturer part number records when the stock number is a type B-part number 3) Update existing data records that are currently type B-Part Number with > 1 associated manufacturer to type J-MCN as local stock numbers (with approval from affected users) and clean up manufacturer data that will not fit into the 1:1 association, or assign stock numbers and assets to one associated manufacturer 4) Add manufacturer search fields to the Internal Stock Number browse so users may search for a stock number by the associated manufacturer data 5) This SCR does not cover the DLMS integration /changes. Refer to the DLMS Part Nbr Integration SCR for details of that effort.
Mission Critical:
Mission Critical. DLMS transactions must be able to send the correct manufacturer data for type B-part number stock numbers. In addition, the manufacturer AUD capability is an essential component of the DPAS application.
Benefits:
Improves capability of DLMS transactions for stock numbers that are type B-Part Numbers; Reduces time by having manufacturer data entered during stock number add/edit process; streamlines the manufacturer AUD process by having a single manufacturer service for the application.
Users:
This effort streamlines the cataloging of a Part Nbr Stock Nbr and provides a means to support DLMS transactions that are for Part Nbr Stock Nbrs.
Partially Completed – Release 2022.2 – 26 August 2022 Completed – Release 2022.3 – 04 November 2022 |
|
| 01757 | Email members notification of inspection due signed | Warehouse | USAF | New | Description:
Member need e-mail notification of overdue inspection of their issued or assigned equipment.
Recommended:
Use the same concept as we do for warehouse transfers. Once the equipment has reached the next inspection date, and e-mail reminder should be sent daily to the e-mail address on file for the member.
Mission Critical:
Important
Benefits:
time savings, and tracking made easier, members who have equipment that is due an inspection will be notified that the equipment needs to be inspected.
Users:
All AFERMS users |