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
01202 Container Inspection Request Warehouse AF: AFERMS New

Description
We have sets in containers. we need the ability to sign off the inspections all at once instead of 120 individual inspections for containerized items. We also have individual container systems like mobility pallets that need inspections. We also would like to pick and choose Items with in the container to inspect or assign an inspection to. Aircraft as a container, has different equipment on it, we do post flight so that is one inspection. But all items within the container may have different dates.

Recommended
create an option to put an inspection against a container.  have that inspection apply to all items within the container. 

Mission Critical
highly important.  we have mobility bins that are containers and require inspections.

Benefits
time savings.

Users
all users.

01201 Provide SA/LW Registry Reporting to Warehouse Warehouse SOCOM New

Description
DPAS's Warehouse /  Materiel Mgmt modules currently do not report electronically to a Component or National SA/LW registry.  The Navy Registry located at CRANE, IN was not accepting electronic transactions, but is willing to consider an electronic feed based upon transactions that are processed.
  The DPAS PA Module currently interfaces with the Army Component / National Registry via it's UIT Interface with LOGSA, but it does not currently support the SA/LW accounted for within the Warehouse module.
With USSOCOM looking to utilize the Warehouse module for weapons inventory and with SPECWARCOM migrating its weapons accountability to the Warehouse module (from SWALIS), there is a need to automate the reporting / reconciliation process to reduce the level of effort to maintain the registry and improve the overall reporting and speed I.E. perform the reporting using the actual transactions processed within the inventory system vs. manual documents that are generated by hand often times.

Recommended
Automate the SA/LW reporting for warehouse actions to the Navy Component Registry (P64).
  All receipts, issues, gains, and losses will be reported via the DLMS140A transaction set.
  Inventory adjustments (Stock Nbr / Serial Nbr changes) will be reported via the DLMS 888A transaction set.
  The implementation must be accomplished in a way that DPAS can accept registry 'transaction rejects' from the component registry (transactions that were sent to the registry for processing which were not accepted.
  The design should permit the user take the  necessary corrective action, and resubmit the transaction along with simultaneously correcting the user record in DPAS.
  This SCR also includes the requirement to be able to conduct reconciliations with the component SA/LW registry, and respond to registry follow-ups.

Mission Critical
This SCR is considered critical for the successful implementation of DPAS.  With USSOCOM planning to use the Materiel Mgmt/Warehousing modules to manage the wholesale inventory of weapons and related accessories that are subject to registry reporting, the level of effort to perform this manually is cost and resource prohibitive.

Benefits
Automating this process will improve reporting accuracy, and reduce the cost of reporting to the federal government.  Utilizing standard DLMS transactions should enable this interface to be used to feed the other component registries (Army  & Air Force), assuming they accept DAAS style transactions.

Users
The affected users are likely Navy, Marine Corps, and USSOCOM and their associated organizations report their SA/LW reportable items via the Navy Registry.  With validation/testing, the use of this capability could be expanded to other Service Registries.

01200 Add Condition Code to Custodian Asset Report PA Navy Removed

Description
The asset condition code is not on the Custodian Asset Report.  Verification of the assets condition is a requirement for Navy FIAR inventory efforts.  It is also required to keep the condition code updated in the APSR per SECNAVINST 7320.10A.

Recommended
Add condition code to the Custodian Asset Report.
The condition code has been added to the custodian inventory report to support inventory requirements of DODI 5000.64 and SECNAVINST 7320.10a however recommend it also be added to the Custodian Asset Report.  After an inventory is conducted the Custodian Asset Report is provided to the custodian as documentation of assets in their custody.

Mission Critical
Not mission critical but a FIAR requirement, and SECNAVINST 7320.10A requires verification of condition code.

Benefits
Will improve custodian's ability to view the current condition of assets in DPAS to meet the SECNAVINST 7320.10A requirement.

Users
Yes to all Agencies

21 Aug 2019 – cancelled per Kevin Callahan
No Longer Required.

01199 TCTO (Time Compliance Technical Order) Warehouse AF: AFERMS Done

Description
We have one time inspections called TCTOs (Time Compliance Technical Orders) that are required to be accomplished on items.  these items have a completion date assigned that can range from immediately (which renders the item in-serviceable until it is accomplished), to next inspection cycle which allows the item to be used as is until the next scheduled inspection.

Recommended
create an inspection type of TCTO that can be assigned to an NSN.  give a field for compliance date.  if the inspection is not completed by the compliance date downgrade to condition "F". this inspection needs to be assigned to all items of the affected NSN to include items that are in kits and items that are issued.  we need to be able to sign off the inspection even if the item is in a kit without first having to remove the item from the kit.

Mission Critical
critical.  this involves safety of flight in some instances.

Benefits
we can auto-generate a TCTO inspection on items and mandate completion even if the item is kitted, signed out, or both.

Users
all AF users.

Partially Completed – Release 6.3 – 21 December 2018

Completed – Release 7.0 – 20 April 2019

01198 serviceable storage Warehouse AF: AFERMS Done

Description
We have equipment that is put into serviceable storage similar to WRM (war reserve material). This equipment has some inspections waived until put into full service. there is no way to currently handle this material.

Recommended
create a location type of "serviceable storage".  create check box that is selectable when assigning an inspection to an item to declare that this inspection is conducted when an item is placed into this location type. all other inspection types will be deactivated when placed in serviceable storage.

Mission Critical
highly important.  We cannot handle equipment that will soon be loaded into the system.  It will generate inspections that are not due.

Benefits
will have accurate inspection due list.

Users
AFERMS plus more users of WRM material

Completed – Release 7.0 – 20 April 2019

01197 MRO Due In Warehouse AF: AFERMS New

Description
We have testers that are sent off installation for contract calibration.  the MRO process allows us to release these items but we then have to create a due in to gain the items back.

Recommended
create a check box in the MRO to auto generate the due in for the MRO

Mission Critical
important.  reduces work and ensures the due in is created

Benefits
no loss of accountability of equipment

Users
all AFERMS users possibly all users

01196 IMDS (Integrated Mechanical Diagnostics System) Warehouse AF: AFERMS Removed

Description
IMDS (Integrated Mechanical Diagnostics System) is the source database for combat aircraft maintenance. we are required to use this database to track aircraft parts and components. the survival kits and parachutes we maintain for these aircraft are tracked in IMDS. we are double documenting if we track in DPAS and IMDS

Recommended
have DPAS talk to IMDS

Mission Critical
mandated. we have to use IMDS to track aircraft components

Benefits
updating one system instead of two

Users
all AFERMS users

01195 default completion time Warehouse AF: AFERMS New

Description
there is a function to track time to compete inspections.  we need default times assigned to NSNs. If time is greater than the default a justification narrative needs to be input.

Recommended
add field at the NSN level to input default inspection time. when an inspection is performed that has a default time, mandate a start time and auto-populate a stop time.  allow adjustment of the stop time.  if the stop time exceeds the default inspection time, require a justification narrative be input.

Mission Critical
mandated.  tracking time to perform inspections allows AFE to justify manpower positions

Benefits
manpower justified

Users
all AFERMS users

01194 GACP (global ammunition control point) Warehouse AF: AFERMS New

Description
GACP (global ammunition control point) is to munitions what JACKS is to CBRNE.  We need GACP to automatically update suspended munitions lots

Recommended
have DPAS talk to GACP

Mission Critical
important. eliminates human error

Benefits
eliminates human error in updating suspended munitions

Users
all users of munitions

01193 consumable components Warehouse AF: AFERMS Removed

Description
we have smaller components (nuts, bolts, zip-ties, etc) that we would like to track, but cannot add undue burden of adding and removing these components to kits. We need a component category of consumable

Recommended
add a check box to the SKO edit grid "consumable" to denote an item is a consumable. In add another column, that is required if this is selected, "default qty consumed". In the QC/Insp "manage" button grid. add a consumable components tab.  each consumable line should have a check box to take the default number and a qty picker to adjust it if necessary. when the inspection is completed the inventory levels should be adjusted down the amount consumed.

Mission Critical
required to track all stock in a warehouse

Benefits
we can use DPAS as the sole inventory system for all stock items in a warehouse

Users
all users

 

Marking for deletion per SMSgt Bowen (AFERMS) request 2019-05-15


×