System Change Requests Header

System Change Requests (SCR's) are submitted by our Configuration Control Board (CCB). To learn more about the process, please visit our CCB Responsibility 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.

Use the filter features on the left to sort by Agency (Reporting Organization), Module, or State. Use the open filter text box (above black header) to find key words in the description, or specific SCR number. Use the column title header to sort by that column. You may also download an Excel file of the record data by selecting the green Excel logo in the upper right corner of this page.

Filter 
Title SCR Number DPAS Module Reporting
Organization
State Description
M & U Upload 01447 MU Army: LDAC New

Description
We need to be able to upload a spreadsheet in to M & U of monthly utilization for each asset that is in M & U.  We need to save some time when inputting monthly utilization.  As we have almost 965 assets.  Inputting each one is very time consuming.  We would like to make it where a spreadsheet is utilized the same as PA module, where you can upload 500 assets at one time.

Recommended
Capability in M & U to upload utilization for assets by a spreadsheet for monthly requirements.

Mission Critical
this is not mission critical. 

Benefits
Reduces time/ cost.  Also would improve accuracy, due to the fact that a human is not key punching all the numbers, less chance of errors.  Accountability is improved by less chance of error.

Users
We believe it would benefit all users.  It would save a lot of time and there is less chance of making a mistake.

Student Information System / Member Profile Interface 01446 Warehouse USAFA Done

Description
The U.S. Air Force Academy (USAFA) is migrating to DPAS. Due to frequent squadron and duty status changes for Cadets, information within DPAS Member Profiles should be constantly synced with the Student Information System. Duty Status changes can impact what a Cadet may be issued at any given time. Therefore, updates to the Member Profile should occur on a daily basis.

Recommended
A DAAS-GEX automated File Transfer process established wherein USAFA can push Member Profile update files to the DPAS Member Profile table

Mission Critical
Mission Critical: The USAFA business model relies upon updated, accurate tracking of cadets and their associated sales charges throughout the life cycle of the cadet, from In-Processing through graduation. Without timely updates, Cadets may be improperly issued material and equipment if incorrect information is located in the Member Profile tables.

Benefits
Allows for accurate and timely updates of USAFA Cadet Information throughout cadet life cycle, pay deductions for DFAS/FM, and accountability for issued/sold items.

Users
This functionality will affect all users within the USAFA agency.

Completed – Release 7.1 – 26 July 2019

UIT feed to include all assets from all DPAS modules 01445 Enterprise Army: LDAC New

Description
LDAC is not receiving all assets from DPAS in the current  DPAS to LDAC UIT automated interface.  Currently only reportable items within the Property Book module are being sent to LDAC through this interface which is based upon the RICC.  If the RICC is 0, DPAS does not send any equipment on hand quantities or serial numbers to LDAC for asset and UIT reporting.  LDAC is also missing asset data from the other modules within DPAS to include the warehouse module, as well as internal DPAS transactions and external DPAS transactions.

Recommended

  1. Remove the filtering of the RICC logic from the UIT interface so that DPAS can begin providing all assets within the property book module to LDAC regardless if they are coded in the catalog as being reportable
  2. Provide LDAC the asset on hand quantities, serial numbers and UIIs from the DPAS warehouse module.
  3. Provide the internal and external DPAS transactions to LDAC to support Asset Visibility, UIT and DST reporting.

Mission Critical
Mission critical -This causes a lack of visibility of assets and associated transactions and impacts both LDAC's high viability applications and data shared with trading partners.  Lack of visibility of all assets and transactions within all of DPAS's modules causes Department of Army to make decisions on Army authorizations and forecasting necessary future equipment purchases based on incomplete Equipment on hand data.  This issue also negatively impacts the Lead Materiel Integrator and equipment planners when making equipment moves to fill shortages and can cause unnecessary equipment moves, wasting both time and resources (Second Destination Transportation Costs). 

Benefits
Improves Accuracy, Accountability and Visibility of all assets and transactions. Provides a better asset picture to enable decision makers at all levels to make equipping decisions based on more accurate on hand numbers.

Users
Yes

SIS Interface 01444 Warehouse USAFA Done

Description
The U.S. Air Force Academy (USAFA) is migrating to DPAS for the tracking of supplies and materiel and for its Individual Issue of materiel to its cadets. Some specific required data fields do not currently exist in the DPAS Member Profile tables, and need to be added in order for USAFA to maintain the current business model and processes.

Recommended
DPAS be modified to add data fields to the Member Profile section. Exact fields to be provided to Leidos development team with character requirements.

Mission Critical
Mission Critical: The USAFA business model relies upon updated, accurate tracking of cadets and their associated sales charges throughout the life cycle of the cadet, from In-Processing through graduation. These data points are currently supported and need to be functional and updated in DPAS.

Benefits
Allows for accurate and timely updates of USAFA Cadet information throughout cadet life cycle, pay deductions for DFAS/FM, and accountability for issued/sold items.

Users
This functionality will affect all users within the USAFA agency.

Completed – Release 7.1 – 26 July 2019

LIN/TAMCN Column Addition 01443 Warehouse USMC: CSP New

Description
Currently there is no LIN/TAMCN Column in Manage Physical Inventories>grid Options>Columns.

Recommended
Recommend that the LIN/TAMCN Column in Manage Physical Inventories>grid Options>Columns be added.

Mission Critical
Yes, This will help us identify PIR for each TAMCN when we do multiple locations for each TAMCN in one or the same  warehouse module.

Benefits
Having this functionality will help from having to go through multiple steps to get the information we need for Audit Purposes.

Users
All IIF/UIF

Extract Info from DPAS to DRCED 01442 Enterprise OSD New

Description
Develop an automated capability (API, FTP, etc.) to extract and transmit detailed transaction data from the DPAS platform to the OUSD Universe of Transactions (UoT) Defense Repository for Common Enterprise Data (DRCED).

Recommended
Enhance the existing DPAS Accounting Transactions Report capability to include control totals required by DRCED.  Automatically generate this enhanced report, or data extract, and utilize the existing DPAS GEX channel to deliver this data set to the DRCED DISA SFG Relay.  

Mission Critical
Mandated per Revised Technical Solution for a Defense-wide Appropriations Universe of Transactions Memorandum, 16 Aug, 2016.  This is also a requirement of the DPAS Functional Proponent, DASD Log.

Benefits
Improves Accuracy/Accountability, Financial Reporting.

Users
All DPAS communities' data will be impacted. This is a DoD level requirement.  There will be no disruption to service; only the modified report from DPAS should need to be sent to DRCED.

Individual Issue Sales 01441 Warehouse AF: Other Done

Description
The U.S. Air Force Academy (USAFA) is migrating to DPAS for the tracking of supplies and materiel and for its Individual Issue of materiel to its cadets.  Some of the materiel that is issued to a cadet is chargeable to the cadet - either at time of issue, or at a later date in time that it is determined that the cadet is not going to return materiel.  In the past, these charges were exported from our system and sent to DFAS - who is responsible for deducting the applicable amount from the cadet's pay. The DPAS Warehouse application lacks the functionality to produce the appropriate list of charges for each member and to provide those charges to DFAS for gear issued to warehouse members that will not be returned to the warehouse.

Recommended

  1. DPAS be modified to allow for the identification of items that are chargeable to the cadet at time of issue or return. 
  2. The system should allow the USAFA to establish a cost that will be charged by Stock Number using the Moving Average Cost "MAC" of the Inventory or the Current Replacement Cost plus or minus a user controlled "tariff" as the basis that the cadet will reimburse the U.S Government. 
  3. Provide a process (Listing / Spreadsheet / Electronic Interface if DFAS supports - TBD) where the charges by cadet can be certified by the USAFA and sent to DFAS for collection.
  4. Provide a query/report that identifies the amount reimbursed by cadet in total or for a period of time by date issued and what reporting period it was sent to DFAS for collection / reimbursement.  The report should show the item being reimbursed, the date the transaction occurred, who applied the charge and the reason for the charge.

Mission Critical
Mission Critical: Reimbursement of issues to cadets is a primary function of the US Air Force Academy business model, and is currently a capability of the system being sunset in favor of DPAS.

Benefits
Allows for the proper recording and accounting of the cost of materiel not being returned to the warehouse - improving the accuracy of financial reporting.

Users
This functionality will affect all users within the USAFA agency. 

Completed – Release 7.1 – 26 July 2019

Inventory Sales 01440 Warehouse AF: Other Done

Description
USAFA routinely charges members for materiel they were issued from the warehouse that will not be returned. In the past, these charges were exported from our system to DFAS - who is responsible for deducting the applicable amount from members pay. The DPAS Warehouse application lacks the functionality to produce the appropriate list of charges for each member and to provide those charges to DFAS for gear issued to warehouse members that will not be returned to the warehouse.

Recommended
DFAS is responsible for deducting the cost of the materiel from the members pay. The cost deducted is computed using the Stock Number unit price plus or minus a pre-defined "tariff". Provide a means of computing the applicable cost and the ability to communicate these costs to DFAS for the materiel issued to warehouse members that are non-returnable/lost/damaged.

Mission Critical
Mission Critical: Inventory sale is a primary function of the US Air Force Academy business process and is currently accomplished in the system being shut off in favor of DPAS Warehouse.

Benefits
Allows for the proper recording and accounting of the cost of materiel not being returned to the warehouse - improving the accuracy of financial reporting.

Users
This functionality will affect all users within the USAFA agency

Completed – Release 7.1 – 26 July 2019

Loan Module Modification 01439 PA AF: Other New

Description
Loan module only works for serialized managed assets and not for bulk managed assets

Recommended
Modify Loan Module to include bulk managed assets

Mission Critical
This is mission critical and is crucial for GFE and overall tracking of loaned assets.   Currently we have no tracking capability for bulk assets out on Loan.

Benefits
Improved accountability of bulk assets out on loan.

Users
Yes, this will affect all users within our Agency

IUS - Funding Identification 01438 PA Navy Removed

Description
In the Asset Receiving Module, there is no ability to distinguish the type of funding for various Internal Use Software (IUS). This is critical as capitalization thresholds are different for the various types of IUS.
Currently, the Capitalization threshold for all IUS is $250K. However, the Capitalization threshold for Military Intelligence Program (MIP) and National Intelligence Program (NIP) IUS is $1M. As a result, DPAS will incorrectly capitalize MIP and NIP IUS below the $1M threshold and require the APO to manually change the capitalization code to "N" (Non capital, exceeds threshold) to stop the asset from depreciating.  

Recommended
Develop a programmatic process for DPAS to distinguish between the various types of software capital thresholds and to set the capitalization code for capital thresholds at the correct levels.

Mission Critical
Mission critical/mandated.  DoD 7000.14-R Vol 4, Ch 27 pg 27-18 states " The current IUS capitalization threshold for all DoD Components is $250,000, except for the Office of the Director of National Intelligence, for which the capitalization threshold is $1 million."

Benefits
Ensures that capitalization of IUS is correctly applied per DOD regulation

Users
All Agencies would be affected by this SCR.

14Feb2019 – cancelled per Kevin Callahan
At the request of the BSO (NL-CCAF).

IUS - Hosting Environment 01437 PA Navy New

Description
In the IUS Asset Receiving Module, the Hosting Environment Drop Down, on the Asset Entry Tab does not contain all possible scenarios including "Data Center" and "Network".

Recommended
Add Data Center and Network to the Hosting Environment Drop Down menu on the Asset Entry Tab. Recommend obtain input from DPAS User Community to identify other hosting scenarios not currently available.

Mission Critical
Mission critical. If all possible IUS hosting environments are not listed then inaccurate information will be entered into the database potentially causing an audit finding and trouble completing inventories.

Benefits
Increases accuracy of IUS data elements to ensure the hosting environments of the software are reported correctly.

Users
This will affect all agencies.

Scheduling Multiple Lane Types 01436 Warehouse USMC: CSP New

Description
Currently when using the scheduling functionality there isn't a way to assign more than one activity to one lane. We would like to have the option of selecting multiple options for one lane. This would allow us to group all issue or return types to that one lane.

Recommended
Recommend using a multiple select field for lane type assignment. This would allow us to select multiple lane types for one lane. This will be helpful in scheduling all issue and return types to separate lanes in larger warehouses if we choose too.

Mission Critical
This is mission critical because it will allow us to assign multiple lane types to one lane. This would help organize how we assign lanes and make it more efficient.

Benefits
Having the ability to assign multiple lane types would help increase efficiency of how each warehouse lane is used.

Users
This will affect all users who managing the scheduling of lane assignments. This will also affect CSP customers considering that scheduling lane types could change how often appointments are scheduled.

Inventory Activity Reason Code 01435 Warehouse USMC: CSP New

Description
Currently in Inventory Activity there is no ability to select multiple reason codes in the search grid. This becomes problematic when searching for Inventory gains and losses because there are multiple reason codes for these. The only way we are currently able to pull this data is ask the DPASSupport desk to pull the data, or pull all inventory activity data and then filter down. The latter method is time consuming and in most cases unsuccessful because of the amount of data pulled.

Recommended
Recommend that the Reason Code search option be a multi-select field. This would be similar to how the Location Type Code search field works on the Location AUD grid. This would allow for us to select all the inventory adjustments reason codes in one search.

Mission Critical
It has been mandated by LOGCOM leadership that the CSP has the ability to pull these reports and provide them to auditors on a quarterly basis at the very least. Currently, in most cases, the only way we are able to obtain these reports is through DPAS Help Desk request.

Benefits
Implementing these changes increases the accuracy of the data and improves the amount of time it takes to pull reports. It would also make CSP users more self sufficient when obtaining these reports since they will no longer request DPAS Help Desk assistance.

Users
This will affect all CPS users.

ICP Stock Item Add 01434 Materiel Management USMC: CSP Removed

Description
In the ICP there is currently no way to add stock number to the stock item AUD for multiple warehouses. To add the new stock number to the stock item AUD for the warehouses we have to do it individually for each warehouse. This is a time consuming process.

Recommended
CSP recommends creating functionality that will allow for user to add stock number to the a stock item AUD for multiple warehouse at a time. This will make it easier for users to add new stock number to the stock item AUD for all warehouses.

Mission Critical
Yes, this will allow for the CSP PMO to add the stock numbers to the stock item list for every warehouse when new stock numbers are introduced to the program.

Benefits
This reduces the time and increases the efficiency when adding stock numbers to the stock item AUD in the ICP.

Users
Yes, this has the potential to affect all CSP users.

14Jan2019 – cancelled per Joe Stossel
This is a duplicate of SCR 01374.

ICP CSP Inquiry Role 01433 Materiel Management USMC: CSP New

Description
Currently when DPAS warehouses are attached to a DPAS ICP they are unable to add stock items to the warehouse. We have tried to give users roles to the ICP in order to add stock items, but this becomes problematic because of the limited number of ICP roles. The current ICP roles give warehouse users too much functionality beyond adding stock numbers to the stock item list.

Recommended
CSP recommends creating a new role that can be granted to users that only has the ability to add stock numbers to the stock item grid. This will give CSP users the required functionality to add stock numbers to the stock item list, but will not let them view or transact elsewhere in the ICP.

Mission Critical
Yes, currently in the CSP program,  users must contact users who have ICP access in order to get stock numbers added. There are very limited number of users who have this access which could possible cause a work stoppage.

Benefits
The benefits of implementing this solution is that we could assign users in every warehouse this role. This would allow every warehouse to be self sufficient when adding stock numbers to their stock item list.

Users
Yes this will affect all ICP users who will be assigned this new role.

New Form in Unit Issue Request and Transfer Process 01432 Warehouse NAVAIR New

Description
The existing ST/STE database, eTIMS, generated a form called a "C-List" for every request created. The "C-List" contained: who created the request, who the list is addressed to (warehouse if a unit issue request, or vendor if an issue transfer), request number, date request created, aircraft, comments (remarks), ST/STE list, contract, UIC, expected return date, ship to (UIC and address), ship to contact (name and phone). The closest thing to this form in DPAS is the Issue Receipt form. This form does not have some information which used to be on the "C-List." Also, the Issue Receipt is only available once a UIR is Issued. NAVSUP WSS requires a form be generated upon the completion of a UIR on their end (once the UIR's status changed to PK-Picking). As of now, they have to take screen shots of the UIR page to provide to PCOs and vendors to show we have completed the request. A sample C-List from eTIMS and an example of what the new form should look like will be provided with the submittal of this SCR.

Recommended
Create a new form that includes all information as the provided C-List, or update the Issue Receipt to include this information.  The information that should be included on the form should be: Unit Issue Request Established By, Established Date/Time, To, Request or Transfer #, Reportable Commodity Type, Remarks (mainly for TAC information), Tooling List, UIC, Account Name, Expected Return Date, Ship to Address, and Contact Information of UIC Custodian.  Make this form available to view and print when the request is "In-Process" or "Pk-Picking" status. Also make this form available during the Unit Issue Transfer process.

Mission Critical
Mandated. Vendors and PCOs require some type of documentation to use as a receipt that the UIR has been started/completed. DCMA uses this documentation when inspection occurs, PCOs use this document when modifying their contracts.

Benefits
This solution will create a formal document that we can use as proof of completing a UIR. It will improve accountability and standardize the UIR process.

Users
This change will impact not only users of DPAS and the ST/STE community, but DLA, NAVSUP WSS, and NAVAIR PCOs/ACOs. Vendors also rely on a formal document as an inspection point that a UIR has been completed.

View Asset Additional Information in ICN Inventory 01431 Warehouse NAVAIR New

Description
Some users can add Additional Information to an ICN during receiving and in Inventory Update; however, there is no other place to view this information.  Not all users have or need access to Receiving or Inventory Update.  Additional Information needs to be available to view on the ICN Inventory Inquiry so that all users can read/review the Additional Information.

Recommended
Recommending the ability to view asset "Additional Information" as found in Inventory Update in ICN Inventory Grid Options.  Recommending this to also be a searchable field.

Mission Critical
Not mission critical or mandated.

Benefits
This will improve accuracy and accountability of the tools by being able to see relevant notes to specific tools that users have entered so other users with different roles can see.  The notes will also leave a history for the tool to further help in the case of tool history research.

Users
It will affect all users because notes for the specific tool will be seen by all.

Update Expected Return Date 01430 Warehouse NAVAIR New

Description
There are 3 categories of ST/STE requests:

  1. Warehouse requests (ST/STE is stored at a warehouse and is requested to be shipped to a location for usage),
  2. Contract Transfers (ST/STE is staying at the current location, but changing its contract accountability),
  3. Loan Extensions (ST/STE is staying at the current location and being used under the current contract, but the expected return date needs changing).

The Unit Issue Request process works well for warehouse requests. However, for Contract Transfer Requests, utilizing the existing Unit Transfer Request process does not give us the ability to update the expected return date. There also isn't a separate process to allow for updating return dates when processing Loan Extension requests.  Lastly, Open Warehouse Actions for Unit Returns are not updating when an expected return date is updated.
The work around we have been using in order to add return dates is to return ST/STE to the warehouse, then issue it back out with a Unit Issue Request with a return date. This is creating unnecessary rework and longer touch times and cycle times to complete requests.

Recommended
Incorporate the ability to add an expected return date to the Unit Transfer Request process and the ability to update the expected return date to ST/STE on loan (without transferring the contract). Accommodate the Contract Transfer and Loan Extension Requests described above.  Open Warehouse Actions for Unit Returns need to be updated when expected return dates are updated.

Mission Critical
Mission critical. ST/STE must have accurate expected return dates in order to have proper accountability and traceability.

Benefits
This implementation should reduce the cycle time to complete Unit Transfers and Loan Extensions by at least 67%.

Users
This change will impact not only users of DPAS and the ST/STE community, but it will improve fleet readiness by allowing us to complete requests much faster than we currently do.

Expanding Stock Number Field 01429 Enterprise NAVAIR New

Description
NAVAIR is responsible for managing Special Tooling/Special Tooling Equipment associated with various weapon systems/reportable commodity types.   Manufacturing numbers that are created by vendors are used for the stock numbers of the tools.  However, the vendors' manufactured numbers have been known to be 25+ long.  The length of these numbers are not standardized across vendors.  More than 15 characters are assigned to ST/STE to uniquely identify the tool.  As such the current solution prevents the use of the Stock Number field and the associated capability within the DPAS system.   The Special Tooling Identifier is part of the Stock Number Description Field along with the Noun.  In addition, this practice makes it difficult to utilize the Master List Capability to building Tool to Tool and Tool to Part relationships.
The conversion into DPAS utilized a unique identifier from the source systems primary key, but after conversion future entries will require the generation of a unique DPAS key.  Loading large numbers of ST/STE from OEM will be further complicated as the OEM assign the Tool ID and the current practice of using the Stock Number Description will not trap duplicate entries on the Catalog.

Recommended
Request the expansion of the current 15 character limit of the Stock Number field to 30 characters in the Warehouse Module to accommodate future Special Tooling and Special Tooling Equipment (ST/STE).

Mission Critical
Mission Critical.  Over time the management of ST/STE by NAVAIR will be hampered with duplicate Catalog entries due to the 15 Character limit in the Stock Number field.  Future assignment of Inventory to the catalog and asset reporting will be hindered.  Duplicate Stock Number entries (via a description) will challenge audit-ability of this data.

Benefits

  1. Tight control of the Tooling Catalog
  2. Reduce workload on finding tooling associated with weapon system BOMs
  3. Full benefit and reporting capability offered by the Stock Number Field
  4. Easier loading of future PPSA files
  5. Elimination of duplicate Catalog entries and association of Inventory to Catalog entries, removal of future audit findings.

Users
This change will impact current Navy ST/STE community and potentially the Air Force ST/STE community.  Additionally any future or current community for which the Stock Number field proves to be too short.

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

Joe Stossel comment, 8/10/2015: seems to be similar to SCR 636.  Do we need this if we modify Operator field to utilize Members.

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

Select Search Options

Reporting Organization

DPAS Module

State

DPAS Help Desk

Toll Free: 1-844-THE-DPAS or 1-844-843-3727 or alt: 1-888-759-4851
Email: DPASsupport@leidos.com

Training Calendar

«   October 2019   »
SuMoTuWeThFrSa
  1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
  

more ...