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
Modify DLMS Transaction to support the Product/Service ID Qualifier of "ZZ" 01244 Warehouse Leidos New

Description
DPAS is not current compliant with DLMS ADC 295 that was issued on Aug 06, 2008.  DLMS ADC 295 requests all systems that support DLMS transactions to accept a Product/Service ID Qualifier of "ZZ" - Mutually Defined. 

Recommended
Modify the applicable DLMS transaction processes to accept a Product/Service ID Qualifier of "ZZ".  When a DLMS transaction contains a "ZZ" qualifier, take the Product/Service ID associated with it and check the DPAS Catalog for that value.  The internal business logic would be the same as for Product/Service ID Qualifiers of FS - National Stock Nbr and SW - Stock Number.  Retain the Product/Service ID Qualifier as part of the transaction that is captured in DAPS, and use the Product/Service ID Qualifier of "ZZ" to report back to the submitter where applicable rather than the Product/Service ID Qualifier applicable to the DPAS Catalog record.

Mission Critical
Failure to recognize the "ZZ" Product/Service ID Qualifier could result in DLMS transactions being rejected / failed when they shouldn't be / DLMS ADC 295

Benefits
Insures DPAS is DLMS compliant, ensure DPAS does not fail or reject a valid transaction.

Users
This change would impact any user who has an external DLMS feed from an external ICP or an external Remote Storage Activity (Warehouse).

Due-Out / Pending Report Update 01243 PA SOCOM New

Description
Due-Out Inquiry or Pending Transaction Report do not include the Ship To Address info (Activity Name, DODAAC, POC, Address, City, St, ZIP) as well as Phone Nbr, and Email Address.

Recommended
To include the fields mentioned above in the Due-Out Inquiry or have the Pending Transaction Report include this data which would be preferred in excel.  I would believe the Due-Out Inquiry would be the preferred method.

Mission Critical
With the majority of our transfers being outside DPAS it is critical to be able to track pending dispositions in order to follow up on delinquencies.

Benefits
Reduces time/cost and improves accountability.

Users
This would benefit all users within our component and agency.

iRAPT / DPAS receipt process 01242 PA SOCOM New

Description
There is nothing in DPAS that documents that the Property Accountability receipt was the result of a Pending Transaction that was created by a iRAPT (WAWF) transaction.  Today, when an iRAPT receipt is processed through receiving, the "price" is disabled not allowing the user to modify the cost of the item, but once received, the user can modify the cost via Asset Update - Price Change.  The proposed change is to provide an audit trail back to the source of the Receipt (iRAPT). 

Recommended
Add a column to Asset Master that contains "Key" data from the iRAPT / Warehouse transaction that provides for the necessary audit trail.  This column will be non-editable by the user and would be a data element that the user can view and export to an inquiry/report.  Research of the customer iRAPT 856S transaction set is necessary to determine what attributes should make up the string of data to include in the column e.g Date, Price, Document Nbr, any unique identifiers that will enable an auditor to use this data to retrieve the iRAPT transaction to the Property Accountability / Warehouse receipt.

Mission Critical
FIAR compliance is mandated.  This change is considered a necessary feature to improve the audit trail to ensure FIAR compliance.

Benefits
Improves the audit trail.

Users
All users of iRAPT.

E Catalog 01241 Enterprise Leidos New

Description
The current architecture for DPAS is 2 master catalogs.  One for Property Accountability and a distinct / separate one for Materiel Mgt/Warehousing.  This requires the customer to manage 2 catalog which is time consuming and prone to error.  There is a need to combine the 2 catalogs into one that is shared between all modules of DPAS.

Recommended
Create a process where the customer only has one catalog to maintain and the external National Catalog (FLIS) and Agency specific catalogs (AEMM, TDMS, D043, SOF MDR, C-ICPs, etc.) are integrated as well.  The catalog must be flexible enough to support difference in property between a Property Accountability Organization and a Materiel Mgmt organization (Wholesale vs. Property Book).

Mission Critical
To reduce the overall maintenance of the application, the combining of like processes into a single process should accrue savings to the program.

Benefits
Reduces the effort required to maintain a catalog, and improves the accuracy of the data as it is only maintained in one place.  It reduces the cost the application maintenance.

Users
All users who catalog as well as the Software Development Staff now only one process for managing each Catalog type record.

Warehouse module and PA module have no linkage 01240 PA SOCOM New

Description
The current DPAS architecture allows for assets to be reflected in the PA and Warehouse modules simultaneously.  This could result in duplicate counting of the asset.  There should be controls in place that prevent the same item (Asset Id, UII, etc.) from being recorded in both modules at the same time unless there is a valid reason (Loan where both the loaner and loanee are DPAS users).

Recommended
There should be controls in place to ensure there is no duplication of the same asset.  Issues from the warehouse module should flow through Pending Transactions.  Any receipt or update of key data (PA or Warehouse) should validate that the asset (Stock Nbr / Serial, UII, Asset Id) does not exist in any other accounts whether that account rests within the PA or Warehouse modules as both modules support Property Accountability in addition to assets that may be in warehouse for storage.

Mission Critical
This is considered a DPAS design flaw.

Benefits
Improves FIAR compliance in that it would ensure an asset is not be recorded in both modules simultaneously.

Users
This will impact every user of DPAS as this is requesting validation that the asset does not exist anywhere else in the system.

AESIP Catalog Interface 01239 PA Army New

Description
The Army and USSOCOM is requesting that DPAS standardize the Army's data using the Army's Enterprise Materiel Master.  The import of the AEMM will provide for a complete list of attributes associated with a Stock Nbr, not just SB700-20 attributes - current Army Catalog import.  The solution must support Mfr Part Nbr Stock Nbrs that are > 15 characters.

Recommended
Create a process that will utilize the Army's AEMM Web Service to retrieve catalog data.  To ensure compliance, there must be methods within the application that prevents the Army user of the AEMM to not be able to create MCNs, Mfr Part Nbr, or be able to catalog an NSN Stock Nbr that does not exist in the AEMM.  For USSOCOM Catalogers, they need to be able to catalogs items that may not be in the AEMM and for USSOCOM, their catalogers must be able to utilize not only the AEMM Agency Catalog, but also their SOF MDR Catalog simultaneously. 

Mission Critical
Yes.  Army desires Total Asset Visibility within AESIP with all items being known by Stock Nbr / Nomenclature from the AEMM.

Benefits
Reduces the effort required to maintain catalog data, ensures common cataloging throughout the Army.

Users
Currently it is believed that the AEMM interface is limited to Army and USSOCOM users.

No Authorization linkage only manual process/SOLMAN 01238 PA SOCOM New

Description
The USSOCOM's SOF MDR has Authorization data for the SOCs and TSOCs.  This information is need by DPAS to allow the Units to know what they are authorized / required to what they have on hand, and to be able to validate requisitions.  The goal would be to create an Import and and associate the data with the Unit.

Recommended
Have SOF MDR present the data to DPAS.  DPAS would import the data and make it available to the Property Accountability Module's Authorization process, to the Warehouse's Authorization process and to the Materiel Mgmt's Customer Requisition process to assist in determining the validity of the requisition. 

Mission Critical
Improve / automate authorizations for the SOCs/TSOCs using DPAS.  Provide for validation of the Customer Requisition process.  Without this data being available within DPAS, this process is all manual and is thus subject to the data being inaccurate.

Benefits
Reduces the effort required to maintain authorization data.  Improves the validation of a customer Requisition.

Users
SOCs, TSOCs, and USSOCOM's Program Managers that are validating a customer requisition.

Adding an asset does not query the registry 01237 MU SOCOM New

Description
DPAS does not permit the user to enter a UII in Asset Receiving.  The only way for DPAS to capture the UII is via a iRAPT transaction, DPAS HandHeld UII Assoc, or searching the IUID registry and associating it to the asset.

Recommended
Modify Asset Receiving and Asset Update to allow the input of the UII.  Any UII entered should be validated to the registry as a valid UII.

Mission Critical
Currently DoD IUID policy requires all assets that are subject to Property Accountability to have a UII.

Benefits
Reduces the effort required to associate a UII when it is not inserted via an iRAPT or Handheld process. 

Users
All users of the PA module could use this feature.

Data Conversion Enhancements 01236 Enterprise Leidos New

Description
DPAS does not permit the user to import data as part of their converting to DPAS.  Today, the user must complete Excel Spreadsheets and submit them to their DPAS Fielding Support team which reviews them for completeness, then forwards them to a DBA for processing.  The goal would be to provide the user with an Import feature within all processes.  This import feature would work similarly to the existing DPAS Member Profile (Warehouse) and the Fuel / Utilization Import (Maint/Util). 

Recommended
Allow the user to export a template for a specific process, complete it, then import it.  The system would validate the import and add all valid records to the system.  All failed records would be available for export for correction, and / or there would be a "Pending" button that the user could pull up each record that failed validation to be corrected within the Add Screen which would then allow the record to be processed.

Mission Critical
Currently the New User Fielding process is needed to support all new Customers converting to DPAS.  By providing a change is how it is accomplished will reduce the customer wait time and allow them to be in more control of when the data is actually loaded.

Benefits
Reduces the effort required to convert a new customer to DPAS. Provides greater capability to existing customers that may have a large import to perform.  Can be accomplished without Helpdesk and DBA support.

Users
All users of the PA, Warehousing, Materiel Mgmt, and Main/Util modules could use this feature as it becomes available.

DPAS Tablet/Phone App 01235 Enterprise Leidos New

Description
As the Android/Apple IOS platforms become more mainstream in the Department of Defense, there is a need for DPAS to upgrade it's handheld processing features to include these platforms.  These platforms may even replace the Windows Handheld platforms that DPAS currently has in use to perform receipt / QC and Physical Inventory functions in the future.

Recommended
Develop the capabilities to export Work Orders for completion on a tablet style device.  Today many service technicians show up at the customer site with the Work Order that is to be completed on an appliance in the home (Washer, Dryer, Refrigerator) and for mechanicals in a home such as (A/C, Heating, Electrical).   Given the state of the WM 6.5 platform, it may be necessary to port the existing DPAS handheld capabilities first.

Mission Critical
The immediate need/requirement is to ensure DPAS does not lose the capability to conduct Physical Inventories in an untethered / non-network mode.  DoD has issued noticed that the WM 6.5 Framework will no longer be able to be connected to the DOD Network as of July 2018.  This is an extension from the July 2017 original deadline. 

Benefits
Provides capabilities for the DPAS user to perform Logistics functions without having to be directly connected to DPAS. A lot of the Logistics functions associated with DPAS are not in the area where the actual work is being performed.  Thus, often times they must write down the data and take it back to the office where it must be typed into a terminal.  The retyping increases cost and increases the risk of error.  The Android/Apple IOS platforms tend to be less expensive that the existing WM 6.5 models, thus delivering DPAS detached capabilities to these style devices will reduce operational costs for the Department.

Users
All User of DPAS perform these functions that are currently available on the handheld.  Organizations that are small, may choose to perform some of the functions manually, and may not adopt the latest technology even though it could improve their business practices / reduce the cost of performing those functions.

Inventory Update Quantity Adjustment 01234 Warehouse USMC: CSP New

Description
There is a USMC requirement (Supply Order 4400-201, Chapter 9 and 13) to have a verification step during any quantity adjustments that occur in the DPAS application. Currently the only place that a quantity can be adjusted is in the inventory update manager.

Recommended
Recommend having a pop up that states "Are you sure you want to make this adjustment?" This is a generic enough statement to be used easily across the program, but will also meet the requirements that the Marine Corps requires. This will also reduce the amount of mistakes when adjusting inventory.

Mission Critical
This is mission critical due to the requirements of the Marine Corps to have this verification step.

Benefits
The benefits of implementing this solutions is that it would align all of the USMC Logistics Programs with Marines Corps requirements and the chance of improving inventory accuracy through verification during the quantity adjustment process. 

Users
This will affect all users who use the inventory update manager process to make inventory adjustments.

Add Asset Id Info to Warehouse Grids 01233 Warehouse AF: VSCOS New

Description
Vehicle Management Material controls require to orders 90 percent of all parts against an asset. Currently, Warehouse does not offer asset id visibility in any of the grids.

Recommended
We would like to request Asset ID information to be added to the Maintenance Issue Grid, Warehouse Replenishment Grid, Warehouse Replenishment Approval screen, Due-In Message of the Day screen, and the Material Mgmt Accept/Receive process.

Mission Critical
Not mandated but critical.  Air Force Material Control sections need a very detailed process to track, account and issue vehicle parts, equipment and tools against specific Assets to track expenditures and control budgets.

Benefits
Adding Asset Id information to the above grids will enable material control sections to improve order and inventory management by enabling warehouse technicians and managers to have direct access to this critical information. Asset Id information allows managers to approve or disapprove requisitions based on priorities assigned to those assets. Asset Id information is also used to track orders/requisitions and it is used to capture and calculate Non Mission Capable Supply (NMCS) as well as Deferred maintenance.

Users
All Material controllers Air Force wide will benefit form the addition of Asset Id information to the grids above. This will enhance parts tracking and management which in turn will improve inventory management and cut costs related to miss-assigned parts and erroneous orders.

Add 2 Fields Under Asset Management 01232 PA MDA Removed

Description
Background: On October 20, 2017 the DPAS/DAI interface for 12 Capitalization of Purchased Assets (X819) were identified on the DAI Unhandled Report due incomplete information from DPAS.  The reason the 12 transactions were in the DAI unhandled report was due to  blank fields: BUDGET_FISCAL_YEAR, BA_BSA_BLI, DAI_PROJECT_NUMBER, and DAI_TASK_NUMBER.  The root problem was due to blank information in DPAS two fields (1) Task Cd (DAI Project Number) and (2) Job Order Nbr (DAI Task) in Asset Management; therefore,  interfaced to DAI as blank information.

Recommended
Make (1) Task Cd (DAI Project Number) and (2) Job Order Nbr (DAI Task) mandatory fields, this will fix the transactions due to incomplete information. 

Mission Critical
Mission Critical.  Reporting of incomplete financial data to the general ledger can give a false narrative of the data provided and could cause major issue for financial audit of the Agency Capital Assets.

Benefits
By making the two fields REQUIRED in DPAS, (1) Task Cd (DAI Project Number) and (2) Job Order Nbr (DAI Task), it will the eliminate and correct the process in both DPAS and DAI.

Users
This will affect all Property Accountability users of DPAS.

04Dec2017 – removed per Joe Stossel and Randy Reed
Recreating this SCR as a bug.

Change Legacy Asset Y1 Fund Code to DAI Interface Fund Codes 01231 PA MDA Removed

Description
There are  an estimated 1,865 legacy assets in DPAS with the default fund code of 'Y1'.  In 2016, new acquired assets were established with fund code procedure that allows DPAS and DAI interface; therefore, the property system of record, DPAS, transfers information to the MDA financial system of record, DAI.   

Recommended
Change all Legacy Capital Assets with Y1 as the default Fund Code to reflect fund codes submitted by CPO.

Mission Critical
Mission Critical.  At this time, with the amount of legacy assets in DPAS not in DAI, this remains a significant audit risk and finding that needs to be corrected.

Benefits
By allowing the CCA to receive a DPAS flat file of the legacy fund codes, CCA can process only one manual JV (versus thousands)  and provide a corrected file to DPAS to update the legacy fund codes.  This will not require CPO to manual update the estimated 1,865 legacy assets in DPAS; therefore, saving an estimated 3,000 man-hours.

Users
This will affect all Property Accountability users of DPAS.

05Dec2017 – removed per Ryan Steele
Recreating this SCR as a bug.

Add drop-down for OM&S Improvement Cost 01230 PA MDA New

Description
Currently, DPAS - Asset code "O" for OM&S does not allow improvement costs to be added. 

Recommended
Update system to allow improvement cost to OM&S assets, currently there is no way to add improvement cost to OM&S. DPAS - Asset code "O" code for OM&S does not allow multiple lines of accounting.  The multiple lines allow improvement costs to be added.  MDA Capital assets are funded by multiple lines of accounting; therefore, creating interface issues between DPAS and DAI.

Mission Critical
Yes: DPAS - Asset code "O" code for OM&S does not allow multiple lines of accounting.  The multiple lines allow improvement costs to be added.  MDA Capital assets are funded by multiple lines of accounting; therefore, creating interface issues between DPAS and DAI.

Benefits
Benefit:  Once the DPAS - Asset code "O" code for OM&S has the ability to have the improvement tab, which allows multiple lines of accounting,  will discontinue interface issues between DPAS and DAI concerning Asset code "O" for OM&S does and improvement costs to be added . 

Users
This will affect all Property Accountability users of DPAS.

Individual Issue Verify All Button 01229 Warehouse AF: VSCOS New

Description
Component verification during issue and return processes is too long. Add a 'Verify All' button to the verification process to provide option to verify all items at once.

Recommended
Add a 'Verify All' button to the verification process to provide option to verify all items at once. Current process ties up excessive amount of man-hours if item being issued is a kit that contains hundreds of items. This process needs to be accelerated and the addition of a 'Verify All' button will alleviate this issue.

Mission Critical
Non-mission critical nor mandated but current process will hinder technician overall productivity by utilizing excessive man-hours in one single process.

Benefits
This will exponentially reduce time and improve personnel productivity.

Users
This improvement will benefit all users across all services currently using Warehouse.

Inactive/Removed User Report 00598 Warehouse DFAS Columbus Done

Description
This change is being requested for the DPAS Warehouse. In accordance with FISMA control IAAC-1. We need the ability to see inactive/cancelled user accounts.

Recommended
On the PA side this report is automatically generated overnight. The fields include: User Name, User Id, Estbd Dt, Last Login Dt, Last Site Accessed (this will need changed to Last Warehouse Accessed), Email Address, Phone Nbr & History Remarks. When the user is inactivated or cancelled the History Remarks on the user record is updated with the appropriate action completed. For example Inactivated 30-44 days Inactive; email sent to user. A report from the Property Accountability side is being included with the SCR.
We will be developing a new role called Admin Reports. This role will not have any training associated with it. This report needs to be available to Security Officers and to anyone who is assigned the Admin Reports role.

Mission Critical
This is required to be in compliance with the control.

Benefits
The ability to take the item off of the POA&M.

Users
No, this will only be used by the DPAS Account Management and anyone assigned to the Admin role.

Joe Stossel comment, 2/24/2015 - SCR is associated with one from the PA side, SCR 00505

History Inquiries 00776 Enterprise DFAS Columbus Done

Description
We need to generate history transaction reports for Account Management, users and system generated in-activations and deletes. These items must be reviewed by the Information System Security Manager. This will ensure we are in compliance with the DIACAP control ECTP-1 and NIST Publication 800-53 AC-6-Least privilege.

Recommended
Develop history reports to capture any account related transactions. On the PA side the following history reports are being used:

  1. Deleted User History – This shows every user that has been deleted by Account Manager or the system when the account reached 45 days of inactivity. – The fields on this report are:
    • DPAS User Id,
    • User First Name,
    • User Last Name,
    • Agency Cd,
    • Agency Name,
    • Site-Id,
    • Last Updated By,
    • Last Tran Dt,
    • History Remarks
  2. User Actbl UIC History could be replaced with User Region History. – This shows every user’s Actbl UIC access that was added, updated or deleted by Account Management or by the system when the account was deleted at 45 days of inactivity. – The fields on this report are:
    • User Id,
    • First Name,
    • Last Name,
    • Site-Id,
    • Actbl UC,
    • Tran Cd,
    • Last Updated By,
    • Start Date,
    • History Remarks
  3. Users History – The results for this inquiry are very large. We need filters to remove some of the unwanted results. – The fields on this report are:
    • User Id,
    • First Name,
    • Last Name,
    • Site-Id,
    • Tran Cd,
    • Status Cd,
    • Status,
    • Last Updtd By,
    • Last Tran Dt
    • History Remarks
    The report shows:
    • Every normal login made by the user.
    • Every account created or updated by Account Management.
    • All normal user logins.
    • Every time a user changes Site-Id and Actbl UICs.
    • The system generated email sent at 15 days of inactivity.
    • The system generated emails sent to every user at 30 days of inactivity.
    • The system generated email sent at 45 days when the account is deleted.
  4. User Property Custodian History – This shows every Account Management add, update and delete. When a user’s UIC is deleted by Account Management it shows every system delete transaction for each custodians being deleted from that user’s account. It also shows if a custodian is added, deleted or modified by any user on the application. This also is a very large inquiry and filters are needed to reduce the data results. – The fields on this inquiry are:
    • User Id,
    • First Name,
    • Last Name,
    • Site-id,
    • UIC,
    • Custodian Nbr,
    • Sub Custodian Nbr,
    • Tran Cd,
    • Last Updated By,
    • Start Date,
    • History Remarks.
  5. User Role History – This shows every role added, updated or deleted from the users account. This shows the system deleted the account at 45 days of inactivity. A 2nd email is sent cancelling the user. I’m not sure what the difference is between system deletes and system canceled but it includes both. – The fields on this inquiry are:
    • User Id,
    • First Name,
    • Last Name,
    • Site-Id,
    • Role Name,
    • Tran Cd, Status,
    • Last Updated By,
    • Start Date,
    • History Remarks.
  6. User Site History – This shows every normal login. This shows every time a user switches a Site-Id or Actbl UIC. This shows every site added, updated or deleted by DPAS Account Management. It shows when an account is cancelled and the email sent. – The fields on this inquiry are:
    • User Id,
    • First Name,
    • Last Name,
    • Site-Id,
    • Tran Cd,
    • Site Last Login Dt,
    • Last Updated By,
    • Start Date
    • History Remarks.
  7. Users UIC History – This shows every UIC added, updated or deleted by DPAS Account Management. It also shows the systems deletes and the system cancellations. It also shows every UIC added or deleted by a user. – The fields on the inquiry are:
    • User Id,
    • First Name,
    • Last Name,
    • Site-Id,
    • Actbl UIC,
    • UIC,
    • Tran Cd,
    • Last Updtd By,
    • Start Date
    • History Remarks.

Mission Critical
Yes, it is required to pass the upcoming SSAE 16 audit in June.

Benefits
We will be able to provide the appropriate information for the audit.

Users
This SCR is to be incompliance of required controls so we can pass the SSAE 16 audit.

Completed - Release 3.0.01 - 02 June 2015

Mechanic Role 00749 MU OSD Done

Description
USAF desires M&U Role for its Mechanics which will allow them to input time per Sub-Work Order (Job). The Role would have the basic concept of Custodian in PA. The Mechanic would only have access to Sub-Works assigned with limited functionality.

Recommended
Create Mechanic Role as outlined in Attachment

Mission Critical
No

Benefits
For National Guard and Reserve units with reduced manning, this will assist with improved accuracy of direct time and reduce the time to close opened Work Orders.

Users
Maintenance Activity Mechanics

Completed - Release 3.0 - 15 May 2015

USAF-Email Customer 00717 MU OSD Done

Description
Email customer of vehicle for pick-up when Work Order is closed.

Recommended
Utilize the Customer E-mail information recorded in the M&U>Maintenance>Work Order>Customer tab to send the initial email when the Work Order Status Cd is C-Closed for vehicle.

Mission Critical
Improves material readiness by contacting customer immediately upon completion of all work and Work Order is Closed to reduce time available assets in not dispatched.

Benefits
Reduces unavailable time between WO close and customer pick-up.

Users
M&U Officers and Specialist

Completed - Release 3.0 - 15 May 2015

Select Search Options

Reporting Organization

DPAS Module

State

Training Calendar

«   January 2018   »
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 ...