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
00690 Automate process to request transportation movement by DLA Warehouse DFAS Columbus Done

Description
Current process for requesting transportation movement by the Defense Logistics Agency is manual and can be automated by leveraging Approved DLMS Change 316 (ADC316)--Approved Defense Logistics Management System (DLMS) Change (ADC) 316, Retail Transportation and Supply Receipt and Acknowledgment Transactions (Transportation/Supply), (Staffed as PDC 324). Utilize the standardized interchange for the Warehouse Shipping Order, 940R, and Warehouse Shipping Advice, 945A provided through DLA transaction services identified in ADC316. Mandates for data exchange is referenced in the DoDM 4140.01-V7 dated February 10, 2014.
This request also complies mandates for Unique Item Tracking.

Recommended
This capability will eliminate the user requirement of manually checking for shipment status using DLA MRO Tracker e-portal. The initial use of this capability will be with the Defense Logistics Agency’s (DLA) Distribution Standard System (DSS).

Mission Critical

Benefits

Users

Partially Completed - Release 4.1 - 29 July 2016

Partially Completed - Release 5.0 - 03 February 2017

Completed

00689 Individual Issue - allow the issue of assets less than condition code A Warehouse Other Removed

When issuing any item in the Warehouse Management module, it only allows the issuance of Condition Code of A for assets. An example of where this is not acceptable is when you issue a photography kit containing a camera, SD card, batteries, and a flash. You should be able to issue the kit if it is only missing the batteries. The team could buy the batteries in theater. Customer priority: 2

00688 Kilometer Meter Reading PA and M&U MU OSD Done

Description
OCONUS vehicles meter readings are in KM and maintenance is also dictated by the KM recorded.
Users have to convert KM to Miles before putting into DPAS which reduces meter accuracy.

Recommended
Have a means for DPAS to set meter to capture KM as a meter reading but convert to miles when sending Utilization to FAST.
Enter "in Kilometers."
Do we store it in "miles" or "kilometers"
Must be reported to FAST as "MILES"
Possible screen changes to MAM, WO, Scheduler, Dispatch, Inquiries, Reports, etc.
MAM may be where the decision is made to determine what type of mileage to enter (Miles or Kilometer)

Mission Critical
It is critical for all vehicles OCONUS because maintenance actions are driven my the meter reading and DPAS does not allow for KM readings. A lot is lost in the conversion.

Benefits
Reduces time in the varies conversions to meet utilization and maintenance actions. Improves accuracy of meter readings and utilization reporting.

Users
All users in M&U.

Completed - Release 3.2 - 06 January 2016

00687 Dual Labor Rates MU OSD Done

Description
Reserve and Guard technicians that are also Civilian employees will have dual labor rates. Instead of loading name twice with a different Opr/Tech ID, why not assign both rates under one name?

Recommended
M&U Operator/Technician A/U/D should have a field for Labor Rate (Civilian) and Labor Rate (Military) to capture dual rates. When assigning a Technician to a Sub Work, Labor Rate field should be a drop down to chose Civ or Mil rates to charge.

Mission Critical
Critical for personnel with dual labor rates to ensure accuracy of rate to charge regardless of employment status.

Benefits
Reduces time and improves accuracy of loading technician labor rates to a Maintenance Activity.

Users
Maintenance and Dispatch Officer.

Completed - Release 3.2 - 06 January 2016

00686 Improve User Delete for M/U personnel Enterprise DFAS Columbus Done

Description
When a user has access to M&U their DPAS account cannot be deleted until the M&U access is removed. Additionally, if the user is assigned as an Operator/Technician the M&U account cannot be removed until the Operator/Technician assignment is removed.
DIACAP control IAAAC 1-4 - Ensure that user IDs are removed and passwords disabled within 48 hours of notification that a user no longer requires system/network access.
When working with the site to remove the Operator/Technician access this may make the 48 requirement impossible.

Recommended
Requesting when an application Security Officer deletes a user account that it removes the access from M&U and the Operator/Technician areas of the application.

Mission Critical
DIACAP control IAAAC 1-4 states “Ensure that user IDs are removed and passwords disabled within 48 hours of notification that a user no longer requires system/network access.”
When working with the site to remove the Operator/Technician access this may make the 48 requirement impossible. USAF currently has 66 Maintenance Activities. All users at the HQ level have access to all the Maintenance Activities. When a deleted is requested this is going to take a lot of time. If the account could be deleted without the existing requirements it could be done in seconds.

Benefits
Ensure we are in compliance with the regulation to delete the user within the 48 hour timeframe. It would be a time saver for the Account Management team.

Users
Use would be limited to the agency requesting the deletion.

00685 Suitable Sub Association Warehouse New NSNs are outfitting requirements for deployed units, when linking 2 or more NSNs as suitable substitutes either should be able to fill the requirement of the other. In the attached PowerPoint, an inventory of each NSN was performed; one NSN shows a onhand quantity of "0" and the other, on hand quantities of 66 and 1. ?There is a column in the grid specifying an NSN which could be used to display the suitable sub but doesn't. Recommend programming true linking between suitable subs where either can be used to fill a requirement and where both can be visible under each others NSN heading. The system that reports unit readiness for NECC uses true suitable sub association to satisfy requirements. Requester - Mike Cockrill 15 August 2014
00684 Work Order Service End Dt MU DFAS Columbus Removed

Description
Currently the Service End Date is populated from the Work Order?s Estimated Service End Date. This would cause inaccurate dates if the Work Order was being completed prior to the last day of the Priority Code. Why is the Service End Date entered when the service has just begun?

Recommended
The Service End Date should populate when the Work Order State Cd is updated to a State which corresponds to a Closed or Pending Closed Status. This would auto-populate the field with data more likely to be correct.

Mission Critical
This is not mission critical but does

Benefits
Correct for mis-population of data and increases accuracy while decreasing time for data entry

Users
All Work Order Users across the Enterprise

Joe Stossel comment, 2/25/2015 -Work with SCR 680 to ensure they do not conflict with each other.

Joe Stossel comment, 8/10/2015 -work with SCR 680 and 706 to ensure they do not conflict

07Dec2018 – cancelled per Deric Sims
No longer needed due to past enhancements.

00683 Catalog Update (Colloquial Name, Catalog TAMCN, IDN) Warehouse USMC: CSP Done

Description
DPAS overwrites the TAMCN Description and Item Description for NSN items. As a result, the CSP Program has all NSN's flagged as Part Numbers due to the fact they have manipulated/changed Item Description names to better match what the item actually is. This is preventing automatic catalog updates, and creates false reports in the system. DPAS was designed around size category being driven by TAMCN. Our system catalog does not provide a TAMCN for all items, and the way we asked DPAS to design that process was incorrect. It is very important to the longevity and sustainment of our program. Currently, the only way we can get the system to work is to set all stock numbers to part numbers.

Recommended
For the CSP Enterprise Program, MARFORLOGCOM is requesting to add the following fields to the DPAS Stock Number Table:

  • Colloquial Name:
    The CSP Program has all NSN's flagged as Part Numbers due to the fact they have manipulated/changed Item Description names to better match what the item actually is. With a 'Colloquial Name' field the CSP Enterprise program could use this field for the Item Description and then allow the I-001 interface from MARCORLOGCOM's Tech Data Management System update daily. This will better support audibility once the NSN's have their flag changed from Part Number to NSN managed items. Should this change be accepted, please update Item Description to be a non-editable field within the system for NSN coming from the Agency Catalog. This field must perpetuate through all of the reports and grids options (processes) that contain asset information within the system.
  • Catalog TAMCN:
    Another reason that all NSN’s were set to part numbers is because our agency catalog does not have a TAMCN for all items. As a result, the interface for our agency catalog overwrites the TAMCN, when a TAMCN is needed for the individual issue process within the system. This field will be used to represent the Official TAMCN assigned from the Agency Catalog for all NSN’s within the system. This field must perpetuate through all of the reports and grids options (processes) that contain asset information within the system.
  • ID Number:
    ID Number is a unique identifier of different variants of items under a TAMCN. It is requested to add this field to the DPAS Stock Number Table and all associated reports and grid options (processes) in the system to support user identification of the different variants of an asset.

Applying these two changes to the system will better support audibility, as it will allow the CSP to change the NSN’s they have flagged as Part Number Managed to NSN managed items.

Mission Critical
This is a policy mandated system change, that will allow the CSP data to be reported IAW Marine Corps Cataloging Policy.

Benefits
Improves accuracy and accountability with respect to catalog data updates.

Users
This field could be used for all Agencies.

Completed - Release 3.0 - 15 May 2015

00682 Return Managed SKO as full kit Warehouse DFAS Columbus Done

Description
Unable to create a "component list" template because the system will not accept serial number tracked line items.
When attempting to save the template the system pops up code 2648.
There is no way to have visibility on sets that contain serial tracked items.

Recommended
The option to produce a DW Form 04 that shows the breakdown of the issued component so that it may be inventoried by the member signing for custody and by the issuing command when it is returned.

Mission Critical
Mission critical for most units under NECC who issue containerized "kits" of equipment; most kits are serialized. The current system used for reporting readiness (RCRP) has full kitting visibility via it's Equipment Set Management module.

Benefits
Major improvement in both accountability and accuracy.

Users
ALL commands under NECC would be affected and without this functionality, it is doubtful that DPAS WHM will be adopted by the force.

00681 Form DW04 - Provide content visibility for kits Warehouse DFAS Columbus Done

Description
Loss of visibility on serial items assigned to a kit when changing custody. DW Form 04 shows a single serialized kit number for the member to sign for but there is no content breakdown so if items are lost on return, there is no proof that the missing items were ever assigned.
Component lists cannot be used if any line items contained in the kit are serial number tracked.
Unable to view the kit contents once it has been issued where non-issued kit contents can be viewed using the update serial kit module under material management. Major issue with accountability as the kit contents virtually "disappear".
Kit content visibility should be a basic functionality in this program.

Recommended
The option to produce a DW Form 04 that shows the breakdown of the issued kit so that it may be inventoried by the member signing for custody and by the issuing command when it is returned.

Mission Critical
Mission critical for most units under NECC who issue containerized "kits" of equipment; most kits are serialized. The current system used for reporting readiness (RCRP) has full kitting visibility via it's Equipment Set Management module.

Benefits
Major improvement in both accountability and accuracy.

Users
ALL commands under NECC would be affected and without this functionality, it is doubtful that DPAS WHM will be adopted by the force.


×