System Change Requests Header

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: This email address is being protected from spambots. You need JavaScript enabled to view it..

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
01313 2x1 Labels for DPAS WM Enterprise PFPA Removed

Description
Currently 2x1 barcode labels, which PFPA uses for printing from the PA module, can not be printed by the Warehouse Module(WM). Also, labels printed from the WM do not include all information required to identify bulk assets.

Recommended
It is recommended that the option of printing 2x1 bar-code labels be added. This label should include the item description, size, and location.

Mission Critical

Benefits
This solution would enable PFPA to utilize the same size barcode labels as the WM and ensure that correct labels are placed on assets.

Users
This affects all WM users

**08/03/2018 - This is REPLACED by SCR 01314.**

01311 Update Equpt Util Form MU OSD New

Description
Updated form to add pertinent fields the "Dispatch To" would need to capture data. All new suggested information is in "Red".

Recommended
Added accessory issued field.  DPAS auto-populate Period of Utilization and Start Meter Reading.  Users wanted a Operators name printed field to go with signature.

Mission Critical
Information is mandated but currently listed on up to 5 different documents.  Looking to add to one form if possible.

Benefits
Paperwork and time reduction.  Can load one form to Dispatch AU for historical records.

Users
Only users that Dispatch.

01310 M&U Dispatched To Contact Information MU OSD New

Description
Expedite the closing of "Over Due Returns", it would be good to have Operators contact information available.

Recommended
When an asset is "Dispatched To" an Operator in the Dispatch AU, the Phone Nbr, Mobile Phone Nbr and Email Address pulled for the Operator/Technician AUD be available on Basic Tab.

Mission Critical
Mandated at Agency level to reduce unavailable vehicles due to lack of timely return.

Benefits
Reduces time of finding POC information. 

Users
Would benefit all users.

01309 Roles Administrator Enterprise SOCOM New

Description
Currently DPAS provides centralized account management when it comes to entering / maintaining DPAS User Accounts, to include what Sites/UICs, Logistics Programs/Warehouses, Maintenance Activities, and Materiel Mgmt. Programs/ICPs the user has access to.  The basis for this input is from Agency/Field appointed Information Officers IOs.
  The goal of this SCR is reduce the level of effort on the DPAS Account Mangers and the Information Owners while decreasing the time between when the action is initiated by the IO and the update is made in the system.  An example of this might be when a user is on leave, or only has drill once a month, and their account becomes suspended.  Not only are they behind in processing of their data from being away, but they must wait a day or so to have their account re-activated when the IO could accomplish the re-activation with minimal effort.   For Guard / Reserve personnel, they may not even get their account re-activated during that 2 day window.  There are other areas of a User's account that might be better severed by having the IO being able to perform the functions, such as the user requires a Commodity Type and or Role due to an employee being on emergency leave for a day that they might not otherwise have required. 

Recommended
Create a new user role in the DPAS Administration Module. The proposed role name is: Roles & Commodity Types Manager. The role will give the authorized user the ability to query user roles and account status, re-activate accounts that have been suspended, and allow the user to edit commodity types and roles by Tier (level) as needed by the Agency. The new role will not have ability to grant access to new users, re-activate deleted accounts,  or replicate any of the Account Managers responsibilities.  

Mission Critical
Mission critical to the on-going efforts to convert USSOCOM supported activities and units to DPAS. The new role gives USSOCOM ability to rapidly edit user commodity type access and in most case perform roles downgrades as required.

Benefits
Benefits all DPAS users that manage the system at the Agency or L/P levels. This new role will save time and eliminate the need to contact the help desk each time a minor change occurs in user status. With the growth of the DPAS system this change will allow the DPAS help desk to focus on system operating issues, and allow the Security team to focus on System Access requirements

Users
Impacts every user of DPAS. USSOCOM has only begun to implement WM and receives daily requests to modify user rights in PA and the WM module. This demand will grow as the system use expands.

01308 Program Manager Functions Enterprise AF: Other Removed

Description
The Air Force is migrating its equipment mgmt functions that are performed within AFEMS / ILS-S to DPAS. One of those functions within ILS-S/SCS is the capability to identify and manage what equipment needs to be acquired to accomplish the AF mission.  As with any organization, there must be a systematical process of determining what Equipment to purchase when.  This is based upon mission criticality,  available funding, what the AF can possibly re-distribute among its bases.  Currently DPAS does not provide a systematic process for comparing equipment shortages to the funding available and the critically of the equipment shortage that ultimately determines the what to order and the order in which to place those orders. 

Recommended
Incorporate a process into DPAS that will systematically interact with new DPAS Allocation process and DPAS's current Authorization process to determine what the program manager is to order based upon the funds that are available.  This process will enable the Program Manger to place the order with SCS and track the funds being expended to what is available based upon the priority established through this process. 

Mission Critical
Yes.  There is a requirement that is needed to replace the existing functionality within AFEMS / CERT / D200. 

Benefits
Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.

Users
This impact all AF organizations.  Depending upon the design of this process, these processes could benefit other organizations who are looking for a system to  provide this functionality to manage their TDA Equipment purchases. 

 

Removed Per Emily Escobedo 23 March 2023

01307 Allocation Standards Mgmt Enterprise AF: Other Done

Description
The Air Force is migrating its equipment mgmt functions that are performed within AFEMS / ILS-S to DPAS. One of those functions within AFEMS is the capability to create and maintain Allocation / Allowance Standards. These standards form the basis of what equipment and the amount each organization in the AF requires to perform its mission.  DPAS does not current provide this functionality that is required to sunset AFEMS.

Recommended
Incorporate an Allocation / Allowance process to DPAS that will systematically interact with DPAS's Authorization process.  It should be noted that Out Year data used to formulate the actual authorization for out years carries a Secret / Top Secret classification, thus some of the processes may required to be executed and maintained in a secure environment with only current information residing on the Non-Class side of DPAS. 

Mission Critical
Yes.  There is a requirement that is needed to replace the existing functionality within AFEMS. 

Benefits
Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.

Users
This impact all AF organizations.  Depending upon the design of this process, these processes could benefit the USMC, and possibly other organizations who are looking for a system to  provide this functionality to manage their TDA Equipment. 

Completed – Release 7.0 – 20 April 2019

01306 Editable Service Life Expiration Warehouse AF: AFERMS Done

Description
Currently we have to forecast certain shelf life/service life items using individual memorandums and the expiration information showing on the DW01 is inaccurate and showing items as expired when they are not.  This is huge delay for forecasting and makes it impossible for leadership to track time change data. 

Recommended
We can extend the shelf life under inventory update manager, but we need the ability to extend the service life for items that have both.  When we extend the shelf life it doesn't change the overall expiration because the service life expiration currently can't be changed.  This makes it impossible to forecast and have accurate DW01s for our time change items that have extensions.  Please add the ability to extend service life, as show in the screenshot, under inventory update manager, re-identification.

Mission Critical
Critical, the system doesn't forecast correctly at this time, so the system isn't working for what it is intended to work.

Benefits
time savings and accurate data reporting.

Users
all

Completed – Release 6.2.2 – 21 September 2018

01305 CMOS support as a TMO for the PA User PA AF: Other Done

Description
The Air Force is migrating its equipment management functions that are performed within AFEMS / ILS-S to DPAS. One of those functions is the ability to communicate with CMOS transportation requirements for moving equipment among custodians and to DLA Disposition Services. DPAS needs to interface with CMOS for Asset Transfers and Asset Dispositions actions within the PA module as it does with the Warehouse module.

Recommended
Incorporate the use of CMOS within the Asset Transfer and Disposition processes for the movement of equipment. 

Mission Critical
Yes.  There is a requirement that is needed to replace the existing functionality within ILS-S that the AF user uses today to move equipment from Base to Base and to DLA Disposition Services. 

Benefits
Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.

Users
This impact all AF organizations, and possibly other organizations that use CMOS as their TMO system.

Completed – Release 7.1 – 26 July 2019

01304 Create / Manage a Requisition that will create a Due In in the PA module Enterprise AF: Other Done

Description
The Air Force is migrating its equipment management functions that are performed within AFEMS / ILS-S to DPAS. One of those functions is the ability to order equipment. The current Requisitioning capability within DPAS is limited orders being placed for a Warehouse.  The system should provide for the placement of an order for a Warehouse, a Property Equipment account record, and also provide for an order to be placed that is to be shipped to a Non-DPAS User.

Recommended
Modify the current Requisition process that resides within the Materiel Mgmt module to permit the placement of an order for PA, Warehouse, or a Non-DPAS User.  The process must be able to support Fund Targets by Quarter/Fiscal Year by Fund Code/ASN.

Mission Critical
Yes.  There is a requirement that is needed to replace the existing functionality within ILS-S that the AF user uses today to acquire the equipment they require to perform their mission. 

Benefits
Enables the Air Force to migrate the equipment accounts from ILS-S to DPAS and sunset AFEMS.

Users
This change could impact a large group of DPAS, both AF and other.

Completed – Release 7.0 – 20 April 2019

01303 SA/LW Registry Capability Enterprise AF: Other Done

Description
The Air Force is migrating its equipment management functions that are performed within AFEMS to DPAS. One of those functions is the Small Arms / Light Weapons (SA/LW) Registry for the Air Force.  The DPAS does not currently have this functionality as part of its core system.

Recommended
Create the capability to communicate with Service Registries (Navy and Army) Transfers of SA/LWs (tracking of the Due In/Due Out), support for capturing SA/LW data for un-issued SAs and ancillary equipment located in warehouses, such as the Anniston Army Depot, providing registry reconciliation tools, along with the monthly reporting to the National SA/LW registry IAW with DLM 4000.25-2 and other DoD policies and procedures as it pertains to SA/LW.

Mission Critical
Yes.  There is a requirement to provide special handling / reporting for SA/LW.  This function must be subsumed by DPAS as AFEMS is sunset. 

Benefits
Enables the Air Force to sunset AFEMS, and provides benefits to the DPAS users who are currently reporting their SA/LW to the Navy Registry by automating the reporting of those weapons.

Users
All users who are involved with managing SA/LWs.

Completed – Release 7.0 – 20 April 2019


×