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
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.

Calculate Indirect Labor Rate 01428 MU AF: VSCOS New

Description
Currently, DPAS does not provide an indirect labor rate.  Indirect labor rate should include  all work performed by civilian and military personnel charged to the transportation function that cannot be identified to a particular NTV or group of NTVs. 

Recommended
Utilize work order reasons; "PORL - Parts Only Low Cost Bench Stock" and create a work order reason "INDR - Indirect Labor".  Calculate by dividing total indirect labor cost by total available direct cost.

Mission Critical
This mandated per DoD 4500.36, Appendix 2 Enclosure 4

Benefits
The benefits of this solution would be to solidify the correct indirect labor rate across all DoD functions.

Users
All DoD Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  

Asset Visibility Report 01427 Warehouse SPECWARCOM Done

Description
No ability to see asset visibility within our LP or Warehouse

Recommended
Create a new asset visibility real time report

Mission Critical
yes.

Benefits
 

Users

Completed – Release 6.3 – 21 December 2018

Calculate Asset End of Life 01426 MU AF: VSCOS New

Description
Currently DPAS does not calculate an assets end of life (EOL) when its average annual sustainment cost first exceeds, or is projected to exceed, its depreciated value, or seven years after a depot rebuild, whichever comes later.

Recommended
See notes below.  This feature was developed by 441 VSCOS and added to LIMS-EV Transaction Request Tool. 

Mission Critical
Mission critical.  AFI 24-302 states "Use economical, reliable and up-to-date procedures to authorize, acquire, account for and maintain vehicles in a safe and serviceable condition throughout their lifecycle."  The EOL calculation helps determine the most economical time to replace an asset.

Benefits
The benefits of implementing this solution will enhance the annual vehicle purchase drill be pin pointing the most economical time to replace an aging asset.

Users
All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  

**NOTE** This SCR is in conjunction with SCR 01422 Vehicle Prioritization Model.

IntelliSense for Operators 01425 MU OSD New

Description
Operator / Technician listing is very long and slows down the assignment process in Dispatch.  There is no quick way of finding an individual.

Recommended
Utilize the IntelliSense capability when assigning "Dispatched To" during the Dispatch A/U.

Mission Critical
Critical to the accurate and expedient assignment of personnel to equipment

Benefits
Reduces time and improves accuracy of asset assignment.

Users
Only personnel identified to accept material via M&U.

DPAS Account Status 01424 Enterprise OSD New

Description
The Agency has no way of monitoring user activity to ensure accounts stay active.

Recommended
Request adding to Accounts Status to the Inquiry of the IO, APO, M&U Officer and M&U Dispatch Officer roles.  Currently activities task DPAS Security to produce report for them.

Mission Critical
Critical to mission by ensuring accounts remain active especially for the National Guard and Reserve Units

Benefits
Ensure users with sporadic work schedules maintain active accounts and will not spend time reactivating them.

Users

Cost Center Use in M&U 01423 MU OSD New

Description
In PA, Cost Centers can be created for each asset.  It would be efficient to have that migrate to M&U for reimbursements for Work Orders and Dispatch

Recommended
If created in PA, use the Cost Center as the Flag for reimbursement.  This will give another level of identification for funding and will automatically be assigned to assets in M&U.

Mission Critical
No

Benefits
Improves the process of identifying costing source for WO and Dispatch.

Users

Vehicle Prioritization Model 01422 MU AF: VSCOS New

Description
Currently, DPAS cannot differentiate life expectancies for all assets to determine the appropriate replacement cycle necessary for programming purposes. The Vehicle Prioritization Model provides better justification for appropriations and is a proven business model that identifies vehicle requirements while connecting them with the mission they support.

Recommended
See notes below.  This feature was developed by 441 VSCOS and added to LIMS-EV Vehicle View.

Mission Critical
Mission critical.  AFI 24-302 states "Use economical, reliable and up-to-date procedures to authorize, acquire, account for and maintain vehicles in a safe and serviceable condition throughout their lifecycle."  The Vehicle Prioritization Model helps determine the most economical time to replace an asset.

Benefits
The benefits of implementing this solution will enhance the annual vehicle purchase drill by pin pointing which asset to replace at the most economical time.

Users
All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  

**NOTE** This SCR is in conjunction with SCR 01426 Calculate Asset End of Life

WAWF/IRAPT Updates 01421 Enterprise Leidos New

Description
When Wide Area Work Flow (WAWF) initially implemented an interface with APSRs, the intent was to provide Receiving Report data for New Procurements, and provide the capability for APSRs to track and confirm receipt of GFP/GFM shipments to contractors utilizing the "TS" functionality.  Utilizing the interface for transfers provided for an auto update of the IUID registry of transfers between the government and contractor. To support this activity, WAWF provided a pseudo DLMS 856S via GEX.  WAWF does not actually generate or receive the DLMS 856S, but rather used GEX's translation service to put the data into the 856S format or to extract the data from the 856S format.  During a recent WAWF Requirement meeting, it was discovered that WAWF has since implemented the DLMS 861 Transaction Set for materiel acceptances rather than using the DLMS 856S.  This was not known to DPAS as DPAS believed it was receiving acceptance notices via the DLMS 856S.  A review of the DLMS transactions DPAS received in 2017, it does appear that DPAS does in fact receive materiel acceptance via the 856S transaction set.  The WAWF Program believes DPAS should transition to the DLMS 861 for Acceptance.  During the review, it was discovered that DPAS is not capturing the "Acceptance Dt".  Everything is being driven by the Receipt Dt.   

Recommended
Review current WAWF processing and determine whether DPAS should transition to the DLMS 861 Transaction Set for materiel acceptance.  If it should, then make the necessary changes to provide for the receipt and procssing of the DLMS 861 Transaction Set.  Regardless of the outcome of the review (Implement the DLMS 861 or stay with the DLMS 856S), DPAS should be basing the Property Book  / Warehouse Receipt based upon the Acceptance Dt, not the Receipt Dt.  This change should be implemented regardless of the transaction set the Acceptance Dt is acquired from. 

Mission Critical
This SCR is considered essential for DPAS compliance with DoD Policy.

Benefits
DPAS maintains its compliance with DoD Policy

Users
This SCR would affect any customer that utilizes the WAWF/IRAPT interface.

Update Upcoming Maint Report to Include Miles/Make Self Generated Work Order Optional 01420 MU AF: VSCOS New

Description
Currently, there is no way to run a report or inquiry that identifies assets that are due scheduled maintenance with intervals by mileage.  Additionally, the self generated work order makes managing the scheduled work load cumbersome because of the possibility of several work orders being opened for the same asset ID.

Recommended
Update Upcoming Work Report to include a column and indicator that identifies an asset as within its scheduled maintenance window per the "Sched Before Util Qty" field.  The indicator would be the mileage difference between "Util Qty Frequency" and "Sched Before Util Qty".  If the asset has no scheduled maintenance intervals due, it will not display on the report.  Also, we need a feature to disable the system generated work order.  A check box; Auto Generate Work Order Y/N?   This will give the maintenance scheduler the ability to decide on how to assign/document scheduled maintenance actions.

Mission Critical
This is mission critical.  AFI 34-302 states "Scheduled maintenance includes PM&I and Special Inspections, at regular intervals to maintain a safe and serviceable vehicle fleet."

Benefits
The benefits of implementing this solution would be a more streamlined and user friendly scheduled maintenance program.

Users
All Air Force Fleet Managers/Maintenance controllers and Material specialists utilize this information for day to day fleet management purposes.  

Air Force Prior Day Report 01419 MU AF: VSCOS New

Description
Currently, there is not a easy way to see what transactions in the M&U DPAS module that have been completed on a daily basis. So managers can review and make any edits as needed.

Recommended
DPAS the ability to produce a Prior Day Edit Report, when requested with the following perimeters in the fields:

  • Work Order inputs (# open, # closed) with Work Order # and Asset #,
  • Labor Hour inputs by Work Order # and Sub Work Order #,
  • Work Plans associated.

Parts charged to include:

  • work order #,
  • cost,
  • nomenclature & quantity,
  • and warranty.

Parts ordered with:

  • work order #,
  • quantity,
  • nomenclature,
  • and est cost.

All Utilization updates and the data to go with the:

  • Asset Id,
  • Meter Reading inputted,
  • Fuel Qty,
  • Fuel Cost,
  • Fuel State.

Mission Critical
This is critical.  Fleet managers count on viewing information to be able to make informed decisions to manage Air Force fleets around the globe. Also, per AFI 24-302, daily work orders and transactions need to be reviewed and corrections be made to, if needed.

Benefits
Having this Prior Day Report will enhance day to day operations for the Air Force fleet. Also, this will ensure UICs are compliant with AFI 24-302 on daily requirements.

Users
This SCR will affect the entire AF Agency, all Air Force fleet managers/maintenance controllers utilize this information for day to day fleet management operations.  

ICP ADDED COLUMNS 01418 Materiel Management USMC: CSP New

Description
During the past ICART Audit Readiness Inspection for the CSP it was noted that extra Columns are needed to be added to the Inventory Control Point>DLMS Transaction Inquiry Review area to make the CSP compliant with the current Marine Corps Audit Readiness policies. 

Recommended
In order for CSP to be compliant with the current Marine Corps Audit Readiness program we are requesting that the Below columns be added to the following area Inventory Control Point > DLMS Transaction Review:

  • WAREHOUSE DODAAC
  • USER ID (who created the Transaction)
  • Serial Number

Mission Critical
Yes, without these columns the CSP is not in compliance with the current Marine Corps Audit Readiness Program.  DoD mandated audits are high visibility and compliance is critical to CSP success. 

Benefits
Having this functionality will help the CSP be in compliance with the current Marine Corps Audit Readiness Program.

Users
ICP MODULE

Change Acq Dt to Funds Obligation DT 01417 PA Navy New

Description
The "Acquisition Date" field in DPAS is inconsistent with the definition of the term in DPAS, "The date of fund approval / obligation". As the field is titled, "Acquisition Date", most users record the date the asset was received or even ordered. Very few people inherently equate the acquisition date to be the fund obligation date. Because of the ambiguous nature of this term, and the fact that users typically do not use the DPAS glossary to find out what each field is actually requesting, it has resulted in multiple inconsistencies which have basically made this field misused from a data management perspective.

Recommended
Change the "Acquisition Date" field in DPAS to "Funds Obligation Date". This change would align the existing definition of the field to the name of the field and reduce confusion for users.

Mission Critical
No.

Benefits
Improves data accuracy of financial reporting and identifies the funds obligation date from the funding documents, showing auditors the true date when the government committed funds to the order. This would also provide a much clearer understanding for the users out in the field.

Users
This affects all DPAS PA module users.

33A - RFID 01416 Enterprise Army: ASA(ALT) New

Description
33A = The Army requires the capability for RFID integration for shipping and receiving (store, field, inv) with TCN per MIL STD 129 requirements for passive tags.

Recommended
Collect TCN/Expand current RFID Capability

Mission Critical

Benefits

Users
ALL

32A - DOUBLE 01415 Enterprise Army: ASA(ALT) New

Description
32A = GENERATE A MONTHLY REPORT OF "DOUBLE" COUNT ITEMS - EQUIPMENT IN DPAS VS GCSS-A/LMP

Recommended

Mission Critical

Benefits
Improves Accuracy
Increases Accountability
Decreases time

Users
ALL

31A - MNTC HIST 01414 Enterprise Army: ASA(ALT) New

Description
31A = ASA(ALT) requires the ability to be able to track and transfer maintenance record history to the receiving unit.

Recommended
requires an Army enterprise wide CR as well

Mission Critical

Benefits
Improves Accuracy
Increases Accountability
Decreases time

Users
ALL

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

«   July 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 ...