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: 1807 Result(s) Show:

Title
ELMS Module
Reporting Org
State
Description
Action
01564 Warehouse Receiving Improvements Warehouse Leidos New

Description
Users need a way to efficiently and quickly work with upwards of 4000 serial numbers in one receipt.

Recommended
This should be resolved in 2 phases.  The first phase is to allow batch upload of verified and accepted items in receiving via a spreadsheet.  The spreadsheet should be dynamically generated based on the stock number being received to minimize the possibility of user error.  The second phase would be to update the existing screens to allow users to just enter a list of serial numbers, while entering in any needed manufacturer or inspection information only once for that list of serial numbers.  Allow users to repeat that process as much as needed for different manufacturer/inspection information.

Mission Critical
Mission critical, because as it stands now, users cannot reliably or efficiently receipt for more than a hundred or so serialized items at one time.  New groups coming onto DPAS need to receipt for thousands of items at one time.

Benefits
The main benefit of this is reduced time and cost, and improved accuracy.

Users
All users

Partially Completed – Release 2020.1.1 – 27 March 2020

01563 Cancel Customer Requisition Materiel Management Army: ASA(ALT) Done

Description
When in the ICP module, the user is unable to cancel a customer requisition, they only have the option to refer or send status.  To cancel a customer requisition the user must generate a HDT to process the cancellation.

Recommended
Add the cancel option to the drop down menu under the ICP Module; customer requisition review action tab. This would allow the user the option to select cancel requisition once they find a discrepancies requiring the action be canceled. 

Mission Critical
This is mission critical, Army customers process hundreds of transactions daily in DPAS, without this process the customer must rely on the HDT process to clean up actions with their system. 

Benefits
Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would stream line items affecting Army logistics business processes.

Users
This would affect all the ASA ALT community -- users in DPAS (WM).

Part of SCR 01177.

Completed – Previous Release – 31 Aug 2020 – per Kristian Stennett's email

01562 Cost Center Drop Down in MRO Materiel Management Army: ASA(ALT) New

Description
When in the ICP module, the user is unable to choose from multiple cost centers (out of the fielding warehouse) to action various inventory.

Recommended
Have a drop down menu inside the ICP module of all cost centers to allow the user to pick from the cost center at time of MRO build - to select which Cost Center should be fielding it - or leave it blank.

Mission Critical
This is mission critical, Army customers processed hundreds of transactions daily in DPAS, without this process it allows the user to generates multiple MRO in a timely manner. 

Benefits
Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would stream line items affecting Army logistics business processes.

Users
This would affect all the ASA ALT community -- users in DPAS (WM).

01561 Field Lock for MROs Materiel Management Army: ASA(ALT) Removed

Description
When in the ICP module, under material management, creating a requisition, when saving the process, there is no fail safe to allow the user to complete the task with out manually exiting the process. The user is unaware after hitting save one the must exit out, if they continue to hit save it creates multiple MRO with suffixes that can only be reversed by submitting a HDT to DPAS.

Recommended
Have a internal control built into the system so once the MRO save button is hit by the user it locks the process down and move them into another menu to continue on with their additional functions. Or have a pop up to alert the user the document is being processed and not to hit the save button again as it will generate another MRO with a suffix.

Mission Critical
This is mission critical, Army customers processed hundreds of transactions daily in DPAS, without this process it allows the user to generates multiple MRO which cannot be adjusted without submitting a HDT to remove.

Benefits
Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would also reduce the backlog and stream line items affecting Army logistics business processes.

Users
This would affect all the ASA ALT community -- users in DPAS (WM).

 

Per request from Lawrence Walton, this Feature has been marked "Removed" 06/03/2020

01560 Mandatory Fields in Customer Profile Materiel Management Army: ASA(ALT) Done

Description
The requirement to add select items as mandatory when establishing the customer profile, is creating friction points for the Army customer. The mandatory fields for FAD, media status and conditional codes are should be applied when the customer requisition is built not at time of customer profile creation, theses codes fluctuate based on requirements at time of creation and are not universal like the other mandatory fields. 

Recommended
Do not make the FAD, media status, and condition code mandatory fields in the customer profile build, allow them to be static.  Make these codes mandatory in the customer requisition (already available and it pulls forward what was in the Customer Profile - can override them; however, there shouldn't be a default).

Mission Critical
This is mission critical, Army customers will process hundreds of customer requisitions daily in DPAS, without this process it hinders the ability for the customer in make adjustments in DPAS to execute and is causing delays with the fielding missions.  ASA(ALT) will prebuild all Army customers with static data - but the media code, condition code, etc. varies by fielding type - however, all PEOs conduct fielding's to the same units - so these codes need to be fluid by requisition.

Benefits
Adding the modification would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would also reduce the backlog and stream line items affecting Army logistics business processes.

Users
This would affect all the ASA ALT community -- users in DPAS (WM).

Completed – Release 2020.2 – 26 June 2020

01559 Bulk Assembly of SKOs Warehouse Army: ASA(ALT) Removed

Description
As a result of us trying to bulk assemble multiple kits that have serialized items.  There isn't a mechanism to plan an assembly for multiple kits that contain serialized components.

Recommended
When ordering the assembly of hundreds of kits that contain serial items, the assembly process should flag that there are serialized components and they have to individually assemble, you should be able to place one order for all their kits.  So instead of doing 800 individual orders for any one item, you could than do sets of 20/30/40 based on fielding schedule and have the locations do the assemblies the way they are.

Mission Critical
This is mission critical, Army customers processed hundreds of transactions daily in DPAS, without this process it hinders the ability for the customer in make adjustments in DPAS to execute the serialization and IUID process and is causing delays with the fielding missions.

Benefits
Adding the modification process to the assembly process would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would also reduce the backlog and stream line items affecting Army logistics business processes.

Users
This would affect all the ASA ALT community -- users in DPAS (WM).

09 Jan 2020 – cancelled per Lisa Kelly
DPAS currently possesses the functionality ASA(ALT) needs.

01558 WAWF GFP TS Improvements PA Leidos Done

Description
Currently DPAS WAWF GFP TS transactions do not include improvements made in ECP1138.  Additionally, there is some need to adjust previous efforts to allow GFP to transmit GFP TS transactions without UII.

Recommended
Implement changes made in ECP1138 allowing DPAS to transmit WAWF GFP TS transactions with Cage/Part Number, Model Number.  This will include changes to the XML generated by WPHRI02, the likely addition of Model Nbr to WPHRN51, modifications to WCGLX40 to accept new identifiers, and additional validations within WCGLX41. 

Mission Critical
Currently DPAS cannot successfully transmit most WAWF GFP TS transactions to PIEE

Benefits
Improvements to Accuracy, Accountability, Financial Reporting

Users
This is impacting all DPAS users trying to transmit WAWF GFP TS transactions

Completed – Release 2020.2 – 26 June 2020

01557 Customer Requisition Modification Warehouse Army: ASA(ALT) New

Description
When missing data attributes are required to be added to the Customer Profile in DPAS; if the customer due in has been generated there is NO WAY to take corrective action without a help-desk ticket. This is not effective in time management in achieving the capability of using an automatic system.

Recommended
Allow the customer to modify the due-in and reprocess the same transaction after taking correction action to address the Customer Profile errors. The Customer Profile items must be aligned to Army business rules, must be mandatory fields and have drop down fields with appropriate information to allow the customer to meet Army intent.

Mission Critical
This is mission critical, Army customers processed over 160 transactions (Due-in) in DPAS which currently are in a suspended state (ICP-DPAS). The customer profiles were not correctly processed with a Distribution Code (this is not a currently not a mandatory field in DPAS). This is causing delays with fielding missions in Europe.

Benefits
Adding the modification process to the customer requisition (due-in) would reduce reprocessing time, improve accuracy, and accountability aligned to audit.  This would also reduce the backlog and stream line items affecting Army logistics business processes.

Users
This would affect all the ASA ALT community -- users in DPAS (WM).

01556 DAI updates needed for CIP Process PA DISA New

Description
The DPAS CIP process was never set up to handle DAI fund codes.

Recommended
Validations for funding cost center and major command task ID were fixed. However, we are missing more information needed to pass later validations. It's currently failing on the procedure for  uspMajor_command_project_task_Sel because of a missing agency code and major command designation code.  There is likely additional fields that will be required to bring the CIP asset into the property book.

Mission Critical
Currently customers using DAI cannot access their fund codes, cost centers and more within CIP Project, and therefore cannot realize their CIP assets to book.

Benefits
Users can process CIP transactions with DAI cost centers, fund cds, etc.

Users
At this time, this likely is only affecting DISA users.  See TFS 46760 for additional information.

01555 Ammunition and Explosives Tracking Enterprise Army New

Description

  1. DPAS does not have a Net Explosive Weight (NEW) field for Ammunition and Explosives (A&E) material.
  2. DPAS does not have a Hazard Classification (HC) or Storage Compatibility Group (SCG) field for A&E material.
  3. Original Document Number is not a selectable category for creating reports.
  4. The Dept. of Defense Identification Code (DODIC) is not a selectable category for creating reports.
  5. Condition Code (CC) is not a selectable category for creating reports.
  6. DPAS does not have an A&E specific monthly inventory sheet.
  7. DPAS does not allow for decimals in the quantity field.
  8. Item Description gets cut off when pulling reports.

Recommended

  • Add the item NEW and HC/SCG to the Stock Number entry page.
  • Allow for a total NEW within reports function (Quantity x NEW).
  • Users should also have the ability to total the NEW for a specific storage location.
  • Make all of these fields accessible categories for creating reports.
  • Create a A&E specific monthly inventory sheet, with necessary information (Document Number, DODIC, NSN, Lot Number, Serial Number, Nomenclature, Condition Code, Quantity on Hand).
  • Add three required signature blocks to inventory sheet (Inventory Officer, Magazine Manager, and Supervisor).
  • Allow for decimal numbers to be entered into the quantity field.

Mission Critical
All A&E assets are required by DoD to be managed by NEW, HC/SCG.  Currently this is being done manually, which creates room for error.  The current inventories and reports within DPAS are geared towards assets other than A&E.  Quantities listed in DPAS often do not accurately reflect the actual quantity on hand.  A&E items require decimal numbers, to reflect true quantities.

Benefits
The benefits of implementing these solutions include all of the above, reduces time/cost and improve accuracy accountability by not having to keep a separate set of records due to quantity inaccuracies, NEW, hazard classification, and storage compatibility monitoring.  Also improves A&E safety and security by having a real-time view of storage location holdings.

Users
These issue affect all organizations/users managing A&E assets.


×