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 |
|
|---|---|---|---|---|---|---|
| 01716 | Maint Group ID Grid Column Option - Stock Number Inquiry | PA | NAVSUP | New | Description:
In Property Accountability, the newer "Stock Number Inquiry" (Inquiries - Catalog - Stock Number Inquiry) that was implemented with eCatalog functionality is missing a grid column option to select and add the Maintenance Group ID field value for inquiry searches/extract output that the legacy/original PA "Stock Number" labeled inquiry provides as a field option. Navy needs to move to using the newer inquiry due to the nature of the old inquiry pulling additional catalog data from the old NSWC PA Site ID (NW-SWC) which still resides in Navy's PA agency hierarchy, but is tied to the JO-SOCOM catalog. The newer "Stock Number Inquiry" is more efficient and does not appear to exhibit this behavior, but is missing the referenced and required grid column option being requested.
Recommended:
Add "Maint Group ID" selectable option (Grid Options - Columns) in the newer "Stock Number Inquiry" in Property Accountability.
Mission Critical:
Yes - Navy has a DPAS interface with external maintenance systems in our 4 Naval Shipyards. Assets are added or removed from DPAS report to that interface daily. Thus, we need access to the Maint Grp ID field to review/identify all applicable stock numbers set to interface and those stock numbers that are set to interface for corrective action necessary to keep the DPAS assets reporting to the external maintenance programs at the shipyards.
Benefits:
Other organizations aside from Navy may benefit from the addition of this additional grid column option in the newer Stock Number Inquiry as well.
Users:
This would provide additional data to all users within our agency although a large, but limited number of personnel would require it. |
|
| 01715 | DPAS - MCPIC Interface | Warehouse | USMC | Done | Description:
Interface between DPAS-WM and MCPIC.
Recommended:
Interface should accomplish the following:
1. Automated moves between MCPIC and DPAS-WM. When MCPIC picks up a location change for an item, it converts it from GPS to a DPAS-WM location and then passes that new location to DPAS-WM. DPAS-WM automatically does the move transaction to place the identified asset in the location identified by MCPIC.
2. Tags can be printed in either system but it is recommended that MCPIC generate all pRFID tag numbers. This is prevent identical numbers being generated using the the DoD 96 bit EPC structure.
3. MCPIC will pass information to DPAS in any format approved by DPAS PMO. This will include direct data exchange, MILS, or DLMS.
4. MCPIC will utilize asset data found in DPAS-WM Catalog when tagging assets in order to minimize any exception errors.
Mission Critical:
Mission critical.
Benefits:
Eliminates 'lost' containers due to moves not properly recorded in DPAS. Improves inventory location accuracy.
Users:
This affects USMC only, however the synergy between DPAS and MCPIC would be very useful to other services.
Partially Completed - Release 2023.3.3
Partially Completed - Release 2023.3.4
Partially Completed - Release 2023.3.5
Partially Completed - Release 2023.4.1
Partially Completed - Release 2023.4.2
Completed - Release 2023.4.5 |
|
| 01714 | CFO Threshold Change | PA | USAF | Done | Description:
System is depreciating Air Force CFO assets utilizing the old threshold standard for units with an acquisition cost of $100K or more with an acquisition date prior to November 2013
Recommended:
Modify systems internal algorithm to comply with $1M threshold retroactively as mandated by DoD 7000.14 Vol 4 Ch 25.
Mission Critical:
Mandated per DoD 7000.14-R Vol 4 Ch 25.
Benefits:
Needed to avert erroneous financial reporting
Users:
This change will affect all users within the Department of the Air Force (DAF)
|
|
| 01713 | Data Access by Owning DoDAAC | Warehouse | Army: ASA/ALT | New | Description:
PEO Missile & Space (M&S) has multiple warehouse and facility locations that support multiple programs. Most programs have a some like items (Stock Nbrs). Given that there can be like items across programs, the current DPAS Commodity Security does not provide the access control that is required. We need an option to restrict the actions of users to specific programs that are stored in the same warehouse. Currently the Owning DoDAAC is used to identify the materiel owner / program within the warehouse.
Recommended:
Given that that the Owning DoDAAC is currently used to identify the program/owner of the materiel, it logical that if DPAS were to control data access by Owning DoDAAC, this will provide the capability needed.
Mission Critical:
Given the sensitivity / pilfer-able nature of some of the items that PEO M&S has, this change is considered critical.
Benefits:
Implementing this type of data access will improve control of the materiel in the warehouse which will result in better data accuracy, which in turn will reduce the number of reconciliations resulting from warehouse workers personnel performing actions they are not otherwise authorized to perform.
Users:
This change is limited to warehouse operations. Program restrictions will apply to a subset of warehouse personnel assigned to the warehouse. Some warehouse personnel will have the authorization to work multiple programs. |
|
| 01712 | Warehouse Receiving Due In Role | Warehouse | SOCOM | Done | Description:
USSOCOM does not pass requisitions forward using ICP Module since USSOCOM is it's own Source Of Supply. USSOCOM takes contract information and manually builds all of the due-ins for the warehouses by using the Warehouse Module Receiving process. The PEO's of USSOCOM need their contractor Logistics Managers (LMA's) located at the SOFSA Warehouse to be able to perform the manual build of due -ins, but not perform the remaining steps/processes of the Receiving Process (Receive, Verify, Accept). This is a separate responsibility from our contracted workforce that conducts receive and verify processes.
Recommended:
Create a new role in Warehouse Module that limits the User Role to perform the Material Management Functions - LPWNH19 and LPWNH19D process in Receiving. This will enable a select group of contractors to build the due-ins for the warehouses as the PEO representative but block them from performing other receiving actions to maintain separation of duties
Mission Critical:
This is to streamline processes for the SOCOM PEO's that are responsible for inputting their purchase orders into DPAS as Due-Ins but have no means to do so.
Benefits:
Benefit is this will improve accuracy and speed up the Receiving Process at the USSOCOM Warehouses. This change will allow due-ins to be be pre-built by the contract workforce identified by the PEO's. These PEO/Program LMA's will be focused on their contract data, and input that data into the Warehouse. This process improvement will free up personnel tasked with ICP management that are currently performing manual due-in builds
Users:
This impacts only USSOCOM Agency users since USSOCOM is it's own Source of Supply. Our only option currently is to manually build our Due-ins by leveraging people that should not be conducting those transactions.
Completed - Release 2021.2.3 - 23 July 2021 |
|
| 01711 | M&U Corrosion Score and Coating Fields for Work Order Forms | MU | USAF | Done | Description:
DPAS M&U does not have a data field specifically for Corrosion Scores, Paint Stack-ups or the Date an item was Last Painted as mandated by service policy. The proposed improvement is adding these fields to the work order form. This will allow for documentation and historical record keeping of this required information at the enterprise level.
Recommended:
Add (to M&U) Four drop-down menus, one for Corrosion Scores (5 options), one for Primers, one for Topcoats, and one for Color. Adding a date selection box for Date Last Painted.
Mission Critical:
Recording of corrosion scores is mandated by Air Force Policy and this change would allow accurately documenting condition and enterprise wide viewing of those records, which is currently impossible.
Benefits:
This solution would allow for support equipment and vehicle flights to have all the information they need about equipment corrosion status to be accessible at the enterprise level. Having records of corrosion scores allows for prioritizing for corrosion maintenance and assessment of fleet corrosion health/readiness. Recording the coating records allows the flights to be prepared for coating refurbishment activities by ensuring they have the required coatings before tearing down the equipment. This also improves accountability and tracking as certain primers and coatings are currently being phased out. This allows for equipment with these coatings to be easily identified so that resources can be allocated for repainting.
Users:
ALL users - The benefits of having this capability would apply to every user of Support Equipment or Vehicles, especially any users documenting maintenance the equipment, including maintainers, fabrication flights, MAJCOM Corrosion and Fabrication Functional Managers, as well as personnel within AFLCMC/WNZ and AFLCMC/EZP-CPCO who are responsible for the SE&V, as well as any commanders needing to identify readiness issues.
Partially Completed – Release 2023.2.2 – 21 April 2023
Partially Completed – Release 2023.2.6 – 06 June 2023
Partially Completed – Release 2023.2.7 – 30 June 2023
Completed - Release 2023.2.7 |
|
| 01710 | ICP MRO Multiple Upload | Materiel Management | DLA | New | Description:
Request a file upload function and template for the ICP (aka Materiel Management) in the Customer Requisition Process to mass upload multiple MROs (Customer Requisitions) in an excel spreadsheet. Once uploaded, have the function in ICP module to validate each MRO qty and location (aka RSA) - currently exists and is the process to release each MRO to the Warehouse.
Recommended:
Update DPAS logic to allow for mass MRO entry via a file upload. See above. At this time, the following Data elements would be provided in the Mass Upload Template: Ordered By (DoDAAC/RIC), Ship To (DoDAAC/RIC), Owning ICP (DoDAAC/RIC), Stock Number (aka LSN), Qty, RDD, Priority Designator, demand code, media status code, fund code, signal code, POC Name, POC Phone #...
Mission Critical:
No, but would significantly improve MRO process.
Benefits:
Reduce the manpower to enter multiple MRO requests from external to DPAS
Users:
Yes (affects all users within Component/Agency) |
|
| 01709 | Warehouse User Listing | Warehouse | USAF/DH-VEHS | Removed | Description:
Excessive time required requesting DPAS Warehouse access data from DPAS security.
Recommended:
Propose system update allowing agency level users to generate inquiry for DPAS Warehouse UICs, User Roles, Access Level, Assigned Roles and Certified Training CBTs. DPAS PA has similar inquiry and request same or similar function within Warehouse. Process will streamline and standardize inquiry for modules minimizing contact with DPAS security. Additionally, update a searchable option for DoD ID number allowing easier filtering data mining.
Mission Critical:
Air Force Instruction 24-302, Vehicle Management requires accurate records on user level access into the Fleet Management Information System (FMIS). Providing a streamlined and standardized inquiry for modules will meet requirement.
Benefits:
Process will streamline and standardize inquiry for modules minimizing contact with DPAS security. Additionally, an updated searchable option for DoD ID number will allow easier filtering data mining. Effort reduces touch point time from DPAS security and allows agency better accountability on trained personnel within DPAS. Provides leadership accurate, accountable and timely responses to data inquiries vs. days waiting on an outside agency generating information and emailing results to requesting agency.
Users:
Yes, affects all users within warehouse.
21Feb2025 – cancelled per Luther Meitzner |
|
| 01708 | Defaults of GFP Master Data | PA | Leidos | Done | Description:
Currently Users must take action to set up WAWF User ID, WAWF flag set to Yes for Contracting Loan Address and WAWF set to Yes for DODAAC to execute GFP file transactions to PIEE.
Recommended:
On behalf of Joe Stossel and Daryl Hanchock change master data processes to default so that when an asset is placed on loan to contract all data is set up to execute the outbound file to PIEE.
Mission Critical:
Yes
Benefits:
Better reporting of GFP to PIEE
Users:
Yes (all users within Component/Agency)
Completed – Release 2021.3.2 – 15 October 2021 |
|
| 01707 | Data feed to SCORE | PA | AF: A4/HAF FH-AFHAF | Removed | Description:
AF has manually tracked and recorded Controlled Cryptographic Items (CCI) device location/details on spreadsheets gathered from multiple systems. Request an automated report with specific data elements is sent to the HQ CCC centralized repository Recommended:
Push automated report to HQ CCC centralized repository on a recurring basis. Mission Critical:
IAW CNSSI 4001 the Departments are required to track and manage all COMSEC/CCI assets Benefits:
Reduces time for individuals to process and pull a report, improves accuracy and accountability Users:
Removed Per Emily Escobedo 23 March 2023 |
Disclaimer | Accessibility