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
00638 Customer/Unit ID MU OSD Removed

Description
Under Mass Data, desire a Customer/Unit ID field to identify a POC name, email address and telephone number.  (Not a Mandatory Field)  This will reduce the number of 'Dispatched To' names that show up during Dispatch.  Currently every operator loaded in DPAS appears making the search cumbersome.  This improvement will reflect operators from Customer ID or Cost Center only. 

Recommended
With Cust/Unit ID, we can associate customer for Recurring Dispatch, only pull operators associated with Customer ID during Dispatch and notify POC via email for Pending/Recall work orders.

Mission Critical
Streamlines Dispatch functionality for unit issuing.

Benefits
Reduces time for vehicle assignment and allows for a more accurate management and assignment of assets.

Users
M&U and Dispatch Officer

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

00637 Parts Charging Supply and Vendors MU Air Force Removed

(SCR created on 3/3/2014) Inability to accept data that captures/charges supply and local vendor parts by way of flat file upload. 1) All parts from base supply are documented on a work-order.? Normally, a report (D22)is uploaded (flat file) into current legacy system and parts are charged through this process.???????????????????????????????????????????????????????? 2) All parts from vendors are documented on a work-order. For vendor parts either receipts are manually inputted into the legacy system or a vendor supplied flat file is uploaded into current legacy system and parts are charged through this process. ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?

00635 Dispatch Scheduler MU OSD Done

Description
A short to long range (> 6 months) planning tool for non-DPAS access personnel to request multiple assets to meet a mission, approve the request/plan for assets (reason, cost and nbr of assets) and then release to Dispatch/Warehouse for Asset Allocation/Pick, Issue/SKO assembly and return.

Recommended Solution
Enhance functionality to incorporate the Scheduler as part of the Request process for multiple assets within Dispatch and Warehouse.

Mission Critical
Mission critical to meet the over 300 commitments daily to move personnel throughout training bases, planned SKO assembly and Unit Individual Issue.

Benefits
Accurately allocate assets required to meet movement mission.  Early Resource/financial planning to ensure timely asset availability to meet mission.

Users
Scheduler could be utilized by users within the M&U and Warehouse.

Same as SCR 722.

Partially Completed - Release 2021.3 - 10 Sept 2021

Completed – Release 2021.3.1 – 24 September 2021

00634 Maint Asset Master Mass Update Enhancements - Fuel Assoc, Default Fuel Type Cd, Utilization Tab and Cert(s)/License(s) Tab MU OSD Done

Description
When profiling assets in mass, i.e. NSN/Equipt Pool/Dispatch Ctgry, Fuel Assoc, Default Fuel Type Cd, Utilization Tab and Cert(s)/License(s) Tab are not available.
Loaded 75 Ford Focus and had to individually profile same information for all.

Recommended
Have these fields available when mass loading.

Mission Critical
Mission critical when you look at the time it takes to individually profile like vehicles with all the same requirements.

Benefits
Reduces profile time for like vehicles.

Users
M&U Officer

Ties into dispatch reimbursable changes (see SCR 00625)

Completed - Release 3.2 - 06 January 2016

00632 Non-Mission Capable Supply (NMCS) MU Air Force Done

Description
Unable to capture Non-Mission Capable Supply (NMCS) and distinguish from Non-Mission Capable Maintenance (NMCM).

Recommended
Add drop down menu to move parent W/O to Parts awaiting status and have system auto document these days on sub work-order state code. Have Work Order State Cd (i.e, AAWP - Approved Awaiting Part) trigger Unavailable supply days and track the length of time until state changes back to AIPR-Approved-in progress (parts received awaiting repair).

Mission Critical
Mandated to capture vehicle out of commission time and be able to distinguish between NMCS and NMCM. System must be able to show total time out of commission while being able to separate the reason why.

Benefits
Improving in/out of commission reporting, accuracy of cost documentation, part accountability and financial reporting; while giving the Agency the ability to capture NMCS as well as NMCM.

Users
Yes

Completed – Release 6.2 – 31 August 2018

00630 Auto calculate unavailable days based off of work-order state codes MU Air Force Removed

(SCR created on 3/3/2014) Manual input of unavailable maintenance and supply days. Have system auto calculate unavailable days based off of Work Order State Codes. Have system auto document these days by using State Code.? Have sub Work Order State Cd (i.e. AAWP - Approved Awaiting Part) trigger unavailable supply days and track the length of time until the State Cd changes back to the Work Order Sate Code of AIPR - Approved - In Progress . These days will be auto calculated and kept in the background until the parent Work Order close out. At this time days awaiting supply and days awaiting maintenance will be auto calculated by system and added to appropriate fields. See Link for similar USMC issue.

00629 Asset Rcvg Download Template - Add Mfr Data PA OSD Removed

(SCR created on 4/28/2014) Loading assets like vehicles, will have different Mfr Yr in a batch.? Assigning all assets in a batch the same Mfr Yr will require updating records to correct Mfr Yr. Asset Receiving Download Template should include a column for Mfr Yr. ADDED 8/13/2014 "Not only add a Mfr Yr column, but also a Mfr Name and Mfr Model Nbr columns.? This will also mass loads to be performed by NSN and not restricted by Mfr Data." Notes: 1. Instructions tab on the template needs to be updated accordingly. 2. Fix row 18, columns B to ZZZ (remove copied info, if not necessary) 3. Change "an" to "than" on row 13.

00628 Dispatch Mileage Flag MU OSD Done

Description
DPAS to flag any dispatch exceeding 1000 miles. ADDED Each Agency has a mileage limit per dispatch in their policy.  To assist capture violators, DPAS will be able to exploit the utilization captured to alert leadership.  I also believe having this as a Master Data function, will allow the Agencies to set their own separate mileage limits.

Recommended
Either allow distance to be set under Master Data by user or set flag to show when total dispatch is 1000 or more miles.  Just flag in red above tabs.  Flag during Dispatch Return and on the Maintenance Action List would help

Mission Critical
Critical to agency and component level regulations

Benefits
Reduces time and improves accuracy of utilization.

Users

Combined with SCR #01214

Completed – Release 7.0 – 20 April 2019

00627 GSA - Pending Work Orders MU OSD Removed

(SCR created on 5/27/2014) GSA produces a report detailing pending maintenance required for GSA vehicles.? Fleet Managers would like to upload the EXCEL report into DPAS as a 'PENDING' work order for each vehicle.? Have 'Pending' reflect under Work Order on M&U Dashboard and notify the customer via email (Customer SCR for Mass Data). Upload EXCEL spreadsheet at UIC level and produce a 'PENDING' work order.? Vehicles are identified by tag number (DoD Serial Nbr), WO Reason will be GSAP - GSA Pending and put the PM Description in the History Remarks of the Work Order Basic tab. (ensure this is pointed at the correct progID - KOC)

00626 WO Calendar Tracker MU OSD Removed Army contracts off-site maintenance and has to capture date of every evolution. The dates required are: Date to Maintenance, Date to Vendor, Date Vendor?Complete, Date From Vendor, Date Unit Notified and Date Unit Accepted. Recommend six calendar driven fields for required dates captured. WO open = Date to Maintenance and WO Close = Date Unit Accepted.??Do not make these mandatory. WO Open and Close should still be driven by WO but can be override by using calendar. Customer priority: 2

×