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 |
|
|---|---|---|---|---|---|---|
| 01836 | Maintenance Attribute Management | MU | Leidos | Done | Change Request: New System process
Description:
The DPAS diverse customer base results in DPAS having attribute requirements that do not apply to every DPAS customer's mission. To require every customer to managed attributes/functionality that does not apply to them results in unwanted / unnecessary overhead on the part of the customer. Recently DPAS received unique attribute requirements for the maintenance of aircraft parts and unique attribute requirements for the maintenance of boats. The objective of this SCR is to provide a method for the customer to self-mange unique attribute requirements by Stock Number.
Recommended:
Create a new process that will reside within the M&U module to enable maintenance personnel to identify the 'extra' attributes that are required to manage a specific type of assets (Stock Nbr level). The process will reside within the Catalog menu tree within M&U with the entries being available for use by all maintenance activities that are associated to the same Maintenance Program. The data will be stored by Stock Nbr for NSN and CAGE/Part Nbrs to enable the values to be applied to all like Stock Nbrs regardless of which catalog the Stock Nbr originated.
Mission Critical:
This SCR addresses how the specific attributes will be associated to a type of asset. This capability will be used to support the completion of the following SCRs:
1. SCR 01711 - M&U Corrosion Score and Coating Fields for Work Order Forms
2. SCR 01631 - Nuclear, Reimbursable, Mission Critical Indicator
3. SCR 01330 - Nuclear, Reimbursable, Mission Critical Indicator Reflect on Basic Work Order
4. SCR 01744 - UTIL Modification for Boat Engine Hours
5. SCR 01766 - MU Data Field Suppression for Boats/Craft
6. SCR 01767 - MU Data Field Additions for Boats/CraftBenefits:
This process will allow for numerous customizations within the application to increase accuracy as well as to create efficiencies within the processes that are customized
Frequency:
Daily
All customers that utilize the M&U module will benefit by the implementation of this SCR as it will reduce the number of attributes they will need to manage if it were not implemented with the completion of the SCRs identified in Type of Change section.
Partially Completed – Release 2023.1.6 – 24 March 2023
Completed – Release 2023.2.1 – 07 April 2023 |
|
| 01835 | Limit CICP data visibility by Commodity DoDAAC or Contract | Materiel Management | USAF GFM-A | New | Description:
The DPAS Catalog is established at the Logistics Program level today. Current AF CICP users have access to the entire catalog and stock item list under the AF CMP GFP Logistics Program. There are no access controls on the DPAS catalog other than role-based controls. DPAS should limit CICP access to only their data, as designated by commodity types, DoDAAC and/or contract number.
Recommended:
Create a sub-catalog for each AF CICP; to record stock number entries at the ICP and Materiel Mgt Program levels. Make use of the commodity types, DoDAACs and/or contract numbers in DPAS to limit use and viewing at the contract level. This will prevent everyone from seeing every stock number and standard price in DPAS warehouse.
Mission Critical:
The problem leaves the DPAS catalog open to all users. It is mission critical that CICPs cannot have access to other CICP data including stock numbers and standard prices.
Benefits:
Implementing this solution will prevent all users from seeing every stock number and standard price in the DPAS catalog and DPAS warehouse receiving process.
Users:
All AF GFM-A users of DPAS |
|
| 01834 | Latest Acquisition Cost Inventory Inquiry | Materiel Management | USAF GFM-A | New | Description:
AF is reconciling the quarterly CFO reports submitted by the contractors with the transactional data the contractors enter into/interface to DPAS. The purpose of the reconciliation is to determine if the data contained in DPAS is complete and accurate prior to enabling the automated financial reporting capability. AF is having difficulty reconciling the asset values submitted by the contractors with those in DPAS. The contractors’ quarterly reports are valued at latest acquisition cost while DPAS provides moving average cost on its reports and queries. AF needs a query or report that provides asset values at latest acquisition cost for each contractor.
Recommended:
Recommend that DPAS ICP module add the LAC and LAC Extended Price as an attribute(s) to the inventory inquiry screen. DPAS would utilize the last submitted asset value for each item on this inquiry.
Mission Critical:
This is a critical step to verify the completeness and valuation of the contractor’s assets prior to enabling the automated financial reporting. This will provide the AF the supporting documentation necessary to complete the reconciliation
Benefits:
This provides the ability to review CICP transactions and asset valuations for accuracy prior to sending financial data to GAFS-R. Provides an apples-to-apples comparison of asset values for the reconciliation.
Users:
ALL AF GFM-A users of DPAS |
|
| 01833 | Sort capability for Asset Management | PA | AF: A4/HAF FH-AFHAF | Done | Change Request: Process Improvement
Description:
DPAS PA – Asset Management does not list serial numbers in Alpha/Numerical sequence in the Serial Number column. This causes extensive research for EAE, CEMF, and/or MAJCOMs to find and select multiple serial numbers identified by the user (customer) and flagged for processing.
Recommended:
Enable capability to sort Asset management Transfer, Update, Excess, UII, transactions by serial number, stock number, custodian number, location ect.
Mission Critical:
Currently sort capability is limited to dispositions and limited data elements
Benefits:
Providing this simple fix would make searching, finding, selecting, and processing serialized SE much more effective and efficient.
Frequency: Daily
Users:
~2000
Completed – Release 2023.2.6 – 06 June 2023 |
|
| 01832 | New DD1150 Form | Enterprise | DDD/ DoD | New | Change Request: Policy/ Regulatory
Description:
DPAS is currently using an old version of the DD1150, Request for issue/transfer/ turnin. A new version was published Aug 2022
Recommended:
Replace the older version of DD1150 for the new version dated Aug 2022
Mission Critical:
DoD update to the DD1150 published
Benefits:
DPAS will have the most current version of the DD1150 in use.
Frequency:
Hourly
Across DoD |
|
| 01831 | Automate O.Auth qty with FSM multiplier | FSM | AF: A4/HAF FH-AFHAF | Done | Change Request Type:
New System process
Description:
Currently, O. Auth quantities are a manual input. Authorization managers calculate the O. Auth by multiplying the F_Req by the O_Req = O_Auth
Recommended:
Utilize the O.Req quantity as the multiplier to F.Req quantity which will auto populate the O. Auth as the product (F.Req x O.Req= O.Auth). F.Req/F. Auth match flag must be turned on to use the O. Req as the multiplier.
Mission Critical:
This is a mission critical requirement, as part of the readiness reporting and requirements buy, authorizations must be established in order for units to identify their requirements and the AF Sustainment Center can POM for current and future procurements for fielding
Benefits:
Improves accuracy of organizational authorizations and eliminates the potential of human error.
Frequency:
Daily
Users:
AF Enterprise
Completed – Release 2024.1.1 – 12 January 2024 |
|
| 01830 | Add DD1149 to MRO | Warehouse | NAVY NBG-2 | New | Description:
Material Release Order does not produce a DD Form 1149
Recommended:
Offer option to produce and print a DD Form 1149 from relevant Material Release Order, similar to those from Warehouse Transfer and Warehouse Issue
Mission Critical:
Critical - DD Form 1149's are the Document of Record for shipping and transferring material, and we currently have to produce them manually.
Benefits:
Property accountability; reduced/time and cost; accuracy of historical paperwork.
Yes |
|
| 01829 | DD1149 Address Block Additions | Warehouse | Navy NBG-2 | New | Description:
DD Form 1149 does not complete (populate) with all required data. Address of sending and receiving organizations do not populate, even though the associated addresses have been loaded (Master Data Mgmt > Warehouse; select Warehouse > Edit > POC Info)
Recommended:
Have relevant address populate in FROM: (Block 1) and TO: (Block 2)
Mission Critical:
Critical - in order to reduce man-hours to correct DD Form 1149 prior to shipments/accuracy of Data. DD Form 1149's are the Document of Record for shipping and transferring material, and thus must be accurate
Benefits:
Property accountability; reduced/time and cost; accuracy of historical paperwork.
Yes |
|
| 01828 | Service Microservice | Enterprise | Leidos | Done | Signed SCR attached
Description:
During the initial Feature Flag implementation in DPAS, the architecture team recognized that a new microservice would be required to properly manage and access services like the Feature Flag. This requirement is in support of the DPAS modernization effort.
Recommended Solution:
Implement a Service Management microservice. While the microservice will be usable for additional processes later, the initial use will be for the Feature Flag. We will create API endpoints to retrieve feature flags from the feature_flag table and synchronously retrieve enabled features associated to its microservice on start-up. We will also develop a UI for users with a certain role (e.g., Feature Flag Manager) to turn the feature flag on/off via toggle switch. When a change is made, an event will fire to log/notify the subscriber that the feature flag change occurred.
Mission Critical or Mandated:
It is critical for DPAS standard system functionality to implement a microservice for service management.
Benefits:
The recommended solutions will improve service management.
Partially Completed – Release 2022.3.2 – 02 December 2022
Completed - Release 2023.2.3 - 05 May 2023
|
|
| 01827 | DD Form 1348 for WM Issue | Warehouse | DISA | New | Description:
The warehouse module doesn't currently create DD1348 for warehouse Issue. We would like to use the DD1348 as issuing document. Using the DD1348 will create a separate document for each like item only. This will make it easier to keep accountability of items being issue.
Recommended:
Add DD1348 to the Warehouse Module for item issue to the customer during the Warehouse Issue.
Mission Critical:
Accessibility of the DD1348 enable DISA users to have better accountability of items being issued.
Benefits:
Workforce Service Directorate (WSD) is responsible for managing all DISA warehouses and would like to transition warehouse operations from DPAS property module to DPAS warehouse module.
Yes, this action affects all user within the Agency. |